Date   

Re: Add-On Updater: random auto update failures?

Brian's Mail list account
 

I had a spate of connectivity issues last week where web sites were there, then timed out and then there again. nobody seems to know why, but it was affecting normal browsing as well as downloads.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Friday, April 09, 2021 2:02 AM
Subject: Re: [nvda-addons] Add-On Updater: random auto update failures?


Hi,
I guess a remote server was down (probably GitHub or somewhere).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Thursday, April 8, 2021 4:39 PM
To: nvda-addons@groups.io
Subject: [nvda-addons] Add-On Updater: random auto update failures?

Hello

Out of nowhere, I got some NVDA error sounds. Upon checking the log, I saw
that Add-On Updater had tried to get updates, and failed.

After copying the trace, I manually ran updater and updated one add-on just
fine.

Could it be that some automatic updates are failing for some reason when
manual updates at the same time would succeed?
I know I did not lose internet access at any point during this, though it is
possible some remote server was down.

Info follows:

NVDA: installed, alpha-22260,62eaba52
Windows: 20H2 (OS Build 19042.867)
Add-on Updater: 21.03
Log:
DEBUG -
external:globalPlugins.addonUpdater.addonHandlerEx._currentCommunityAddons
(19:26:39.268) - Thread-6 (8132):
nvda3208: errors occurred while retrieving community add-ons Traceback (most
recent call last):
File "urllib\request.pyc", line 1350, in do_open
File "http\client.pyc", line 1255, in request
File "http\client.pyc", line 1301, in _send_request
File "http\client.pyc", line 1250, in endheaders
File "http\client.pyc", line 1010, in _send_output
File "http\client.pyc", line 950, in send
File "http\client.pyc", line 1417, in connect
File "http\client.pyc", line 921, in connect
File "socket.pyc", line 787, in create_connection
File "socket.pyc", line 918, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 197, in _currentCommunityAddons
res =
urlopen("https://addons.nvda-project.org/files/get.php?addonslist")
File "urllib\request.pyc", line 222, in urlopen
File "urllib\request.pyc", line 525, in open
File "urllib\request.pyc", line 542, in _open
File "urllib\request.pyc", line 502, in _call_chain
File "urllib\request.pyc", line 1393, in https_open
File "urllib\request.pyc", line 1353, in do_open
urllib.error.URLError: <urlopen error [Errno 11001] getaddrinfo failed>
ERROR - stderr (19:26:39.268) - Thread-5 (8368):
Exception in thread
ERROR - stderr (19:26:39.283) - Thread-5 (8368):
Thread-5
ERROR - stderr (19:26:39.314) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.328) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.348) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 257, in checkForAddonUpdates ERROR - stderr
(19:26:39.364) - Thread-5 (8368):
info = checkForAddonUpdate(curAddons)
ERROR - stderr (19:26:39.374) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 218, in checkForAddonUpdate ERROR - stderr
(19:26:39.403) - Thread-5 (8368):
raise RuntimeError("Failed to retrieve community add-ons") ERROR - stderr
(19:26:39.423) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.453) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.478) - Thread-5 (8368):
Failed to retrieve community add-ons
ERROR - stderr (19:26:39.508) - Thread-5 (8368):

During handling of the above exception, another exception occurred:
ERROR - stderr (19:26:39.538) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.558) - Thread-5 (8368):
File "threading.pyc", line 932, in _bootstrap_inner ERROR - stderr
(19:26:39.568) - Thread-5 (8368):
File "threading.pyc", line 870, in run ERROR - stderr (19:26:39.598) -
Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 290, in _showAddonUpdateUI ERROR - stderr
(19:26:39.618) - Thread-5 (8368):
info = checkForAddonUpdates()
ERROR - stderr (19:26:39.638) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 260, in checkForAddonUpdates ERROR - stderr
(19:26:39.658) - Thread-5 (8368):
raise RuntimeError("Cannot check for community add-on updates") ERROR -
stderr (19:26:39.678) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.698) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.718) - Thread-5 (8368):
Cannot check for community add-on updates









Re: Add-On Updater: random auto update failures?

 

Hi,
This is a bit complicated as Add-on Updater uses threads to connect and
retrieve add-on files database simply because urllib.request.urlopen takes
quite a "long time" (as in a few seconds) to respond, eating up main thread
resources (that is, causes NVDA to appear to not respond when in fact it is
working).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Thursday, April 8, 2021 7:50 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Add-On Updater: random auto update failures?

This is just a thought, not a criticism, but might it be better to catch
this and put something more brief in the log instead of a chain of
tracebacks?

A down server, or similar condition, is a failure of a different kind than a
bug.

Luke

On Thu, 8 Apr 2021, Joseph Lee wrote:

I guess a remote server was down (probably GitHub or somewhere).


Re: Add-On Updater: random auto update failures?

Luke Davis
 

This is just a thought, not a criticism, but might it be better to catch this and put something more brief in the log instead of a chain of tracebacks?

A down server, or similar condition, is a failure of a different kind than a bug.

Luke

On Thu, 8 Apr 2021, Joseph Lee wrote:

I guess a remote server was down (probably GitHub or somewhere).


Re: Add-On Updater: random auto update failures?

 

Hi,
I guess a remote server was down (probably GitHub or somewhere).
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io>
On Behalf Of Luke Davis
Sent: Thursday, April 8, 2021 4:39 PM
To: nvda-addons@groups.io
Subject: [nvda-addons] Add-On Updater: random auto update failures?

Hello

Out of nowhere, I got some NVDA error sounds. Upon checking the log, I saw
that Add-On Updater had tried to get updates, and failed.

After copying the trace, I manually ran updater and updated one add-on just
fine.

Could it be that some automatic updates are failing for some reason when
manual updates at the same time would succeed?
I know I did not lose internet access at any point during this, though it is
possible some remote server was down.

Info follows:

NVDA: installed, alpha-22260,62eaba52
Windows: 20H2 (OS Build 19042.867)
Add-on Updater: 21.03
Log:
DEBUG -
external:globalPlugins.addonUpdater.addonHandlerEx._currentCommunityAddons
(19:26:39.268) - Thread-6 (8132):
nvda3208: errors occurred while retrieving community add-ons Traceback (most
recent call last):
File "urllib\request.pyc", line 1350, in do_open
File "http\client.pyc", line 1255, in request
File "http\client.pyc", line 1301, in _send_request
File "http\client.pyc", line 1250, in endheaders
File "http\client.pyc", line 1010, in _send_output
File "http\client.pyc", line 950, in send
File "http\client.pyc", line 1417, in connect
File "http\client.pyc", line 921, in connect
File "socket.pyc", line 787, in create_connection
File "socket.pyc", line 918, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 197, in _currentCommunityAddons
res =
urlopen("https://addons.nvda-project.org/files/get.php?addonslist")
File "urllib\request.pyc", line 222, in urlopen
File "urllib\request.pyc", line 525, in open
File "urllib\request.pyc", line 542, in _open
File "urllib\request.pyc", line 502, in _call_chain
File "urllib\request.pyc", line 1393, in https_open
File "urllib\request.pyc", line 1353, in do_open
urllib.error.URLError: <urlopen error [Errno 11001] getaddrinfo failed>
ERROR - stderr (19:26:39.268) - Thread-5 (8368):
Exception in thread
ERROR - stderr (19:26:39.283) - Thread-5 (8368):
Thread-5
ERROR - stderr (19:26:39.314) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.328) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.348) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 257, in checkForAddonUpdates ERROR - stderr
(19:26:39.364) - Thread-5 (8368):
info = checkForAddonUpdate(curAddons)
ERROR - stderr (19:26:39.374) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 218, in checkForAddonUpdate ERROR - stderr
(19:26:39.403) - Thread-5 (8368):
raise RuntimeError("Failed to retrieve community add-ons") ERROR - stderr
(19:26:39.423) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.453) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.478) - Thread-5 (8368):
Failed to retrieve community add-ons
ERROR - stderr (19:26:39.508) - Thread-5 (8368):

During handling of the above exception, another exception occurred:
ERROR - stderr (19:26:39.538) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.558) - Thread-5 (8368):
File "threading.pyc", line 932, in _bootstrap_inner ERROR - stderr
(19:26:39.568) - Thread-5 (8368):
File "threading.pyc", line 870, in run ERROR - stderr (19:26:39.598) -
Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 290, in _showAddonUpdateUI ERROR - stderr
(19:26:39.618) - Thread-5 (8368):
info = checkForAddonUpdates()
ERROR - stderr (19:26:39.638) - Thread-5 (8368):
File
"C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonU
pdater\addonHandlerEx.py", line 260, in checkForAddonUpdates ERROR - stderr
(19:26:39.658) - Thread-5 (8368):
raise RuntimeError("Cannot check for community add-on updates") ERROR -
stderr (19:26:39.678) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.698) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.718) - Thread-5 (8368):
Cannot check for community add-on updates


Add-On Updater: random auto update failures?

Luke Davis
 

Hello

Out of nowhere, I got some NVDA error sounds. Upon checking the log, I saw that Add-On Updater had tried to get updates, and failed.

After copying the trace, I manually ran updater and updated one add-on just fine.

Could it be that some automatic updates are failing for some reason when manual updates at the same time would succeed?
I know I did not lose internet access at any point during this, though it is possible some remote server was down.

Info follows:

NVDA: installed, alpha-22260,62eaba52
Windows: 20H2 (OS Build 19042.867)
Add-on Updater: 21.03
Log:
DEBUG - external:globalPlugins.addonUpdater.addonHandlerEx._currentCommunityAddons (19:26:39.268) - Thread-6 (8132):
nvda3208: errors occurred while retrieving community add-ons
Traceback (most recent call last):
File "urllib\request.pyc", line 1350, in do_open
File "http\client.pyc", line 1255, in request
File "http\client.pyc", line 1301, in _send_request
File "http\client.pyc", line 1250, in endheaders
File "http\client.pyc", line 1010, in _send_output
File "http\client.pyc", line 950, in send
File "http\client.pyc", line 1417, in connect
File "http\client.pyc", line 921, in connect
File "socket.pyc", line 787, in create_connection
File "socket.pyc", line 918, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonUpdater\addonHandlerEx.py", line 197, in _currentCommunityAddons
res = urlopen("https://addons.nvda-project.org/files/get.php?addonslist")
File "urllib\request.pyc", line 222, in urlopen
File "urllib\request.pyc", line 525, in open
File "urllib\request.pyc", line 542, in _open
File "urllib\request.pyc", line 502, in _call_chain
File "urllib\request.pyc", line 1393, in https_open
File "urllib\request.pyc", line 1353, in do_open
urllib.error.URLError: <urlopen error [Errno 11001] getaddrinfo failed>
ERROR - stderr (19:26:39.268) - Thread-5 (8368):
Exception in thread
ERROR - stderr (19:26:39.283) - Thread-5 (8368):
Thread-5
ERROR - stderr (19:26:39.314) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.328) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.348) - Thread-5 (8368):
File "C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonUpdater\addonHandlerEx.py", line 257, in checkForAddonUpdates
ERROR - stderr (19:26:39.364) - Thread-5 (8368):
info = checkForAddonUpdate(curAddons)
ERROR - stderr (19:26:39.374) - Thread-5 (8368):
File "C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonUpdater\addonHandlerEx.py", line 218, in checkForAddonUpdate
ERROR - stderr (19:26:39.403) - Thread-5 (8368):
raise RuntimeError("Failed to retrieve community add-ons")
ERROR - stderr (19:26:39.423) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.453) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.478) - Thread-5 (8368):
Failed to retrieve community add-ons
ERROR - stderr (19:26:39.508) - Thread-5 (8368):

During handling of the above exception, another exception occurred:
ERROR - stderr (19:26:39.538) - Thread-5 (8368):
Traceback (most recent call last):
ERROR - stderr (19:26:39.558) - Thread-5 (8368):
File "threading.pyc", line 932, in _bootstrap_inner
ERROR - stderr (19:26:39.568) - Thread-5 (8368):
File "threading.pyc", line 870, in run
ERROR - stderr (19:26:39.598) - Thread-5 (8368):
File "C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonUpdater\addonHandlerEx.py", line 290, in _showAddonUpdateUI
ERROR - stderr (19:26:39.618) - Thread-5 (8368):
info = checkForAddonUpdates()
ERROR - stderr (19:26:39.638) - Thread-5 (8368):
File "C:\Users\luke\AppData\Roaming\nvda\addons\addonUpdater\globalPlugins\addonUpdater\addonHandlerEx.py", line 260, in checkForAddonUpdates
ERROR - stderr (19:26:39.658) - Thread-5 (8368):
raise RuntimeError("Cannot check for community add-on updates")
ERROR - stderr (19:26:39.678) - Thread-5 (8368):
RuntimeError
ERROR - stderr (19:26:39.698) - Thread-5 (8368):
:
ERROR - stderr (19:26:39.718) - Thread-5 (8368):
Cannot check for community add-on updates


How to find the position of a format change on a text line

bering.p
 

Hello.
I come to you to help me find a solution to find the exact position where a format or attribute change occurs on a line of text.
I did this by looping through the characters in the line and using getFormatField for each character, but it takes a long time if the line of text is too long.
Can you think of a faster solution?
How  can we know the position of a field return by getFormatField ?
Thank you.

Best regards.
Paul.
-- 

Paul.


Add-ons with translation updates

Noelia Ruiz
 

Hello: the following add-ons have been updated on the community
website. They contain translation updates. Thanks contributors,
authors, translators, users and Reef (NV Access) for making this
possible:

- clipContentsDesigner 13.1
- emoticons 13.3
- placeMarkers 15.2
- readFeeds 10.2
- reportSymbols 5.2


Updated GitHub Actions mentioned in NVDAAddons wiki

Noelia Ruiz
 

Hello:

In case it's useful, the Create Release Action, previously maintained
at GitHub by developers, is available but archived. Currently they
mention four actions related to releases that are maintained. You can
see more info at

https://github.com/actions/create-release

So, I've updated the actions mentioned in the NVDA Addons organization
wiki. In particular, I have 2 actions to release add-ons: one to
create a release when I push a tag, and another one to create
automatic releases, always named latest replacing the previous one
created in this way, when I send code to master. This maybe useful for
testing. The wiki article is at

https://github.com/nvdaaddons/nvdaaddons.github.io/wiki/GitHubActions

Cheers


Re: Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

Hi,

Never mind about fifteen minutes notice – it’s not showing up either despite committing these add-ons to Subversion.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Monday, April 5, 2021 1:32 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

Hi,

I was waiting for the community add-ons site to return before posting final bits. The newly registered add-ons will show up within the next fifteen minutes.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, April 5, 2021 1:31 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

I still don't see these add-ons on the official website. Or is there a separate process now to get them to official website?

On 4/4/2021 9:17 PM, Joseph Lee wrote:

HI all,

Took a few days to verify, but I'm delighted to announce that the add-ons mentioned in this thread are now part of community add-ons website. Add-on Updater 21.05 (May) will be told to check for updates to these add-ons.

Cheers,

Joseph


Re: Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

Hi,

I was waiting for the community add-ons site to return before posting final bits. The newly registered add-ons will show up within the next fifteen minutes.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Tony Malykh
Sent: Monday, April 5, 2021 1:31 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

I still don't see these add-ons on the official website. Or is there a separate process now to get them to official website?

On 4/4/2021 9:17 PM, Joseph Lee wrote:

HI all,

Took a few days to verify, but I'm delighted to announce that the add-ons mentioned in this thread are now part of community add-ons website. Add-on Updater 21.05 (May) will be told to check for updates to these add-ons.

Cheers,

Joseph


Re: Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

Tony Malykh
 

I still don't see these add-ons on the official website. Or is there a separate process now to get them to official website?

On 4/4/2021 9:17 PM, Joseph Lee wrote:

HI all,

Took a few days to verify, but I'm delighted to announce that the add-ons mentioned in this thread are now part of community add-ons website. Add-on Updater 21.05 (May) will be told to check for updates to these add-ons.

Cheers,

Joseph


Re: Next round of community add-on registrations: Word Nav, WinWizard, Console Toolkit

 

HI all,

Took a few days to verify, but I'm delighted to announce that the add-ons mentioned in this thread are now part of community add-ons website. Add-on Updater 21.05 (May) will be told to check for updates to these add-ons.

Cheers,

Joseph


Re: Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements

Brian's Mail list account
 

Sounds clear, and of course we must not forget that at the end of the year python itself makes Windows 7 obsolete so windows 10 will be the only game in town for newer versions of nvda one supposes.

It might also be worth mentioning the elephant in the room here. Narrator. A number of friends are telling me that this has improved greatly recently, so one might consider concentrating nvda on doing things Narrator is bad at to keep it in peoples radars so to speak.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal E-mail to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.
Newsgroup monitored: alt.comp.blind-users

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@gmail.com>
To: <nvda-addons@nvda-addons.groups.io>
Sent: Thursday, April 01, 2021 6:51 PM
Subject: [nvda-addons] Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements


Hi all,

After receiving comments on Add-on Updater 21.03 release, I figured it would
be best to make some announcements about upcoming add-on releases:

* Future add-ons will require NVDA 2020.4 or later: Add-on Updater
21.03 is the first add-on to require NVDA 2020.4. This requirement will be
in effect for the next release of Resource Monitor and StationPlaylist
(scheduled for next week at the earliest) due to changes introduced in this
NVDA release that add-ons will take advantage of (clipboard announcement in
Resource Monitor, fixes required to support track column announcements in
StationPlaylist).
* Add-on Updater offers older releases of some add-ons: don't worry
about this, as it is not the fault of Add-on Updater. I expect this issue
will be resolved once updates to affected add-ons are released.
* No May 2021 release for Windows 10 App Essentials: usually I release
updates to this add-on on a monthly basis. But I'm skipping May release
(21.05) in order to assist with NVDA 2021.1 testing.
* StationPlaylist add-on maintenance is slowly coming to a close:
version 21.04 of this add-on (coming as early as next week) will be one of
the last releases of SPL add-on from me. After this release, only
localization and critical bug fixes will be released until early fall. I
will maintain SPL add-on until December 31, 2021, and I hope the community
can maintain it after that point.
* ObjPad 21.04 emergency update: although I stopped maintaining this
add-on for a while, upon request from community members, I'll release an
emergency version of ObjPad add-on to make it compatible with upcoming NVDA
2021.1.
* NVDA 2021.1 will be required at least 60 days after its release: due
to massive changes introduced in upcoming NVDA 2021.1, most of my add-ons
will require this NVDA release. This won't take effect until at least 60
days after NVDA 2021.1 is released in order to give you time to check other
add-ons and upgrade to NVDA 2021.1.



Thanks.

Cheers,

Joseph






Re: Add-on Updater 21.03 released #addonrelease

 

Hi,

That’s okay.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Sergio Gómez
Sent: Thursday, April 1, 2021 1:37 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Sorry. Yes he gives the error when he has problems, it was I who did not try calmly.

It was because I activated the airplane mode of Windows 10, but since I have it connected to the internet by cable, it only deactivated the Wi-Fi and Bluetooth apparently… Now I have disconnected the cable manually and I have deactivated the Wi-Fi, and I could see reporting with an error.

 

I repeat, sorry, sorry for the inconvenience.

 

Thanks

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 22:25
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

It should give you an error if connection issues occur, although I need a log to verify that what I did is indeed working.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Sergio Gómez
Sent: Thursday, April 1, 2021 1:13 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi Joseph

 

I remind you about, if possible, that addonUpdater notifies you if there are connection problems when searching for add-ons. I thought it would be included in this version, but it seems that not…

 

Thanks

 

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 10:16
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

The update check error will be shown during manual update checks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Robert Hänggi

Sent: Thursday, April 1, 2021 1:13 AM

To: nvda-addons@nvda-addons.groups.io

Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

On 01/04/2021, Joseph Lee <joseph.lee22590@...> wrote:

> Hi all,

> Add-on Updater 21.03 is now available. I expect this will be first of

> a series of add-on updates this week. In addition to requiring NVDA

> 2020.4, Add-on Updater 21.03 now presents an error message if it

> cannot check for add-on updates due to loss of Internet connection.

I hope this will only pop up on manual check.

 

Regarding settings:

It is weird that those are specific to the current profile. I have for instance plenty of problems excluding an add-on from being updated since it might still be allowed in the profile I change to in the course of the day.

 

Best

Robert

 

 

> As always, you can check

> for Add-on Updater updates through Add-on Updater itself.

> Cheers,

> Joseph

>

 

 

 

 

 

 

 

 

 

 

 


Re: Add-on Updater 21.03 released #addonrelease

Sergio Gómez <gomez.sergio.3110@...>
 

Sorry. Yes he gives the error when he has problems, it was I who did not try calmly.

It was because I activated the airplane mode of Windows 10, but since I have it connected to the internet by cable, it only deactivated the Wi-Fi and Bluetooth apparently… Now I have disconnected the cable manually and I have deactivated the Wi-Fi, and I could see reporting with an error.

 

I repeat, sorry, sorry for the inconvenience.

 

Thanks

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 22:25
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

It should give you an error if connection issues occur, although I need a log to verify that what I did is indeed working.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Sergio Gómez
Sent: Thursday, April 1, 2021 1:13 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi Joseph

 

I remind you about, if possible, that addonUpdater notifies you if there are connection problems when searching for add-ons. I thought it would be included in this version, but it seems that not…

 

Thanks

 

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 10:16
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

The update check error will be shown during manual update checks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Robert Hänggi

Sent: Thursday, April 1, 2021 1:13 AM

To: nvda-addons@nvda-addons.groups.io

Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

On 01/04/2021, Joseph Lee <joseph.lee22590@...> wrote:

> Hi all,

> Add-on Updater 21.03 is now available. I expect this will be first of

> a series of add-on updates this week. In addition to requiring NVDA

> 2020.4, Add-on Updater 21.03 now presents an error message if it

> cannot check for add-on updates due to loss of Internet connection.

I hope this will only pop up on manual check.

 

Regarding settings:

It is weird that those are specific to the current profile. I have for instance plenty of problems excluding an add-on from being updated since it might still be allowed in the profile I change to in the course of the day.

 

Best

Robert

 

 

> As always, you can check

> for Add-on Updater updates through Add-on Updater itself.

> Cheers,

> Joseph

>

 

 

 

 

 

 

 

 

 

 

 


Re: Add-on Updater 21.03 released #addonrelease

 

Hi,

It should give you an error if connection issues occur, although I need a log to verify that what I did is indeed working.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Sergio Gómez
Sent: Thursday, April 1, 2021 1:13 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi Joseph

 

I remind you about, if possible, that addonUpdater notifies you if there are connection problems when searching for add-ons. I thought it would be included in this version, but it seems that not…

 

Thanks

 

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 10:16
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

The update check error will be shown during manual update checks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Robert Hänggi

Sent: Thursday, April 1, 2021 1:13 AM

To: nvda-addons@nvda-addons.groups.io

Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

On 01/04/2021, Joseph Lee <joseph.lee22590@...> wrote:

> Hi all,

> Add-on Updater 21.03 is now available. I expect this will be first of

> a series of add-on updates this week. In addition to requiring NVDA

> 2020.4, Add-on Updater 21.03 now presents an error message if it

> cannot check for add-on updates due to loss of Internet connection.

I hope this will only pop up on manual check.

 

Regarding settings:

It is weird that those are specific to the current profile. I have for instance plenty of problems excluding an add-on from being updated since it might still be allowed in the profile I change to in the course of the day.

 

Best

Robert

 

 

> As always, you can check

> for Add-on Updater updates through Add-on Updater itself.

> Cheers,

> Joseph

>

 

 

 

 

 

 

 

 

 

 


Re: Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements

 

Hi,
I might refine exclusions list in a future release.
As for the name of the add-on: it is intentional as Add-on Updater is really meant to test add-on update capability in NVDA Core. The add-on itself will be discontinued once that functionality becomes part of NVDA.
Cheers,
Joseph

-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Robert Hänggi
Sent: Thursday, April 1, 2021 1:22 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements

Another quick notice.
Could you please refine the add-ons exclusion list so that only those are listed that are really supported through the AU database.
PS. The add-on name should actually reflect the fact that only add-ons from the community website are updatable.
In other words, it should be named something like Community Add-Ons updater.
The current name and the fact that all installed add-ons are listed is deceiving and suggests that any other add-on resources are included as well.
Thanks
Robert

On 01/04/2021, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi all,

After receiving comments on Add-on Updater 21.03 release, I figured it
would be best to make some announcements about upcoming add-on
releases:

* Future add-ons will require NVDA 2020.4 or later: Add-on Updater
21.03 is the first add-on to require NVDA 2020.4. This requirement
will be in effect for the next release of Resource Monitor and
StationPlaylist (scheduled for next week at the earliest) due to
changes introduced in this NVDA release that add-ons will take
advantage of (clipboard announcement in Resource Monitor, fixes
required to support track column announcements in StationPlaylist).
* Add-on Updater offers older releases of some add-ons: don't worry
about this, as it is not the fault of Add-on Updater. I expect this
issue will be resolved once updates to affected add-ons are released.
* No May 2021 release for Windows 10 App Essentials: usually I release
updates to this add-on on a monthly basis. But I'm skipping May
release
(21.05) in order to assist with NVDA 2021.1 testing.
* StationPlaylist add-on maintenance is slowly coming to a close:
version 21.04 of this add-on (coming as early as next week) will be
one of the last releases of SPL add-on from me. After this release,
only localization and critical bug fixes will be released until early
fall. I will maintain SPL add-on until December 31, 2021, and I hope
the community can maintain it after that point.
* ObjPad 21.04 emergency update: although I stopped maintaining this
add-on for a while, upon request from community members, I'll release
an emergency version of ObjPad add-on to make it compatible with
upcoming NVDA 2021.1.
* NVDA 2021.1 will be required at least 60 days after its release: due
to massive changes introduced in upcoming NVDA 2021.1, most of my
add-ons will require this NVDA release. This won't take effect until
at least 60 days after NVDA 2021.1 is released in order to give you
time to check other add-ons and upgrade to NVDA 2021.1.



Thanks.

Cheers,

Joseph







Re: Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements

Robert Hänggi
 

Another quick notice.
Could you please refine the add-ons exclusion list so that only those
are listed that are really supported through the AU database.
PS. The add-on name should actually reflect the fact that only
add-ons from the community website are updatable.
In other words, it should be named something like
Community Add-Ons updater.
The current name and the fact that all installed add-ons are listed is
deceiving and suggests that any other add-on resources are included as
well.
Thanks
Robert

On 01/04/2021, Joseph Lee <joseph.lee22590@gmail.com> wrote:
Hi all,

After receiving comments on Add-on Updater 21.03 release, I figured it
would
be best to make some announcements about upcoming add-on releases:

* Future add-ons will require NVDA 2020.4 or later: Add-on Updater
21.03 is the first add-on to require NVDA 2020.4. This requirement will be
in effect for the next release of Resource Monitor and StationPlaylist
(scheduled for next week at the earliest) due to changes introduced in this
NVDA release that add-ons will take advantage of (clipboard announcement in
Resource Monitor, fixes required to support track column announcements in
StationPlaylist).
* Add-on Updater offers older releases of some add-ons: don't worry
about this, as it is not the fault of Add-on Updater. I expect this issue
will be resolved once updates to affected add-ons are released.
* No May 2021 release for Windows 10 App Essentials: usually I release
updates to this add-on on a monthly basis. But I'm skipping May release
(21.05) in order to assist with NVDA 2021.1 testing.
* StationPlaylist add-on maintenance is slowly coming to a close:
version 21.04 of this add-on (coming as early as next week) will be one of
the last releases of SPL add-on from me. After this release, only
localization and critical bug fixes will be released until early fall. I
will maintain SPL add-on until December 31, 2021, and I hope the community
can maintain it after that point.
* ObjPad 21.04 emergency update: although I stopped maintaining this
add-on for a while, upon request from community members, I'll release an
emergency version of ObjPad add-on to make it compatible with upcoming NVDA
2021.1.
* NVDA 2021.1 will be required at least 60 days after its release: due
to massive changes introduced in upcoming NVDA 2021.1, most of my add-ons
will require this NVDA release. This won't take effect until at least 60
days after NVDA 2021.1 is released in order to give you time to check other
add-ons and upgrade to NVDA 2021.1.



Thanks.

Cheers,

Joseph







Re: Add-on Updater 21.03 released #addonrelease

Sergio Gómez <gomez.sergio.3110@...>
 

Hi Joseph

 

I remind you about, if possible, that addonUpdater notifies you if there are connection problems when searching for add-ons. I thought it would be included in this version, but it seems that not…

 

Thanks

 

De: Joseph Lee
Enviado: jueves, 1 de abril de 2021 10:16
Para: nvda-addons@nvda-addons.groups.io
Asunto: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

Hi,

The update check error will be shown during manual update checks.

Cheers,

Joseph

 

-----Original Message-----

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Robert Hänggi

Sent: Thursday, April 1, 2021 1:13 AM

To: nvda-addons@nvda-addons.groups.io

Subject: Re: [nvda-addons] Add-on Updater 21.03 released #AddonRelease

 

On 01/04/2021, Joseph Lee <joseph.lee22590@...> wrote:

> Hi all,

> Add-on Updater 21.03 is now available. I expect this will be first of

> a series of add-on updates this week. In addition to requiring NVDA

> 2020.4, Add-on Updater 21.03 now presents an error message if it

> cannot check for add-on updates due to loss of Internet connection.

I hope this will only pop up on manual check.

 

Regarding settings:

It is weird that those are specific to the current profile. I have for instance plenty of problems excluding an add-on from being updated since it might still be allowed in the profile I change to in the course of the day.

 

Best

Robert

 

 

> As always, you can check

> for Add-on Updater updates through Add-on Updater itself.

> Cheers,

> Joseph

>

 

 

 

 

 

 

 

 

 

 


Important notices on upcoming add-on releases from Joseph Lee: NVDA 2020.4 requirement and other announcements

 

Hi all,

After receiving comments on Add-on Updater 21.03 release, I figured it would be best to make some announcements about upcoming add-on releases:

  • Future add-ons will require NVDA 2020.4 or later: Add-on Updater 21.03 is the first add-on to require NVDA 2020.4. This requirement will be in effect for the next release of Resource Monitor and StationPlaylist (scheduled for next week at the earliest) due to changes introduced in this NVDA release that add-ons will take advantage of (clipboard announcement in Resource Monitor, fixes required to support track column announcements in StationPlaylist).
  • Add-on Updater offers older releases of some add-ons: don’t worry about this, as it is not the fault of Add-on Updater. I expect this issue will be resolved once updates to affected add-ons are released.
  • No May 2021 release for Windows 10 App Essentials: usually I release updates to this add-on on a monthly basis. But I’m skipping May release (21.05) in order to assist with NVDA 2021.1 testing.
  • StationPlaylist add-on maintenance is slowly coming to a close: version 21.04 of this add-on (coming as early as next week) will be one of the last releases of SPL add-on from me. After this release, only localization and critical bug fixes will be released until early fall. I will maintain SPL add-on until December 31, 2021, and I hope the community can maintain it after that point.
  • ObjPad 21.04 emergency update: although I stopped maintaining this add-on for a while, upon request from community members, I’ll release an emergency version of ObjPad add-on to make it compatible with upcoming NVDA 2021.1.
  • NVDA 2021.1 will be required at least 60 days after its release: due to massive changes introduced in upcoming NVDA 2021.1, most of my add-ons will require this NVDA release. This won’t take effect until at least 60 days after NVDA 2021.1 is released in order to give you time to check other add-ons and upgrade to NVDA 2021.1.

 

Thanks.

Cheers,

Joseph

821 - 840 of 15666