How long update Arduino libraries list

Hi,

do you know how long it takes for the Arduino lib list to update?

I posted a lib 4-5 days ago which was validated and since then I renamed it and created a second one.

When I test on the IDE it's the old lib that is offered but not the new ones when I can see it in the github list

library-registry/repositories.txt at main · arduino/library-registry · GitHub 4

Thank you !

Hi @leresteux.

The Library Manager indexer system runs hourly. This is the source of the logs you will see on the dedicated logs page for each library:

https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

The indexer scans the repositories of all libraries in the registry for new releases. If it finds a new release, it checks it against some requirements. If the release is found to be compliant with all those requirements, it is added to the index. If it is not compliant, the index is rejected and will not ever become available for installation via the Arduino Library Manager index.

Even after you see from the logs that the indexer has added a new release to the Library Manager index file, there may still be some delay before that release becomes available for installation in the Arduino IDE Library Manager. The reason is there is a local and CDN cache and the updates to the index file must work their way through the cache. For this reason we give a conservative estimate of availability within one days time after a release is indexed.

If you tell me the exact libraries you are referring to, I will be able to provide you with a specific explanation.

Lacking that information, I can only tell you two things:

  • The most common cause of releases not being available is that it does not meet the requirements. You will see the error in the logs.
  • Although submissions and releases are completely automated, other maintenance requests such as the name and URL change request you submitted are handled manually and may take up to two weeks.

hi @ptillisch ,

thank you for all this informations

the old one is dunogeon v0.1
and the new libraries are

and

There are multiple problems that are causing the releases of these libraries to be rejected:

Name does not match registered name

The name field value in library.properties was changed from the name the libraries had at the time of the registration:

https://github.com/leresteux/DunogeonENG/commit/a483d09bd84d22ff577256a06174122749241209#diff-f267f9ae2f5d5d56a1dbb305e95d40d4408d9ee7f71357f1f67fb18c29b7f082L1

- name=Dunogeon
+ name=DunogeonENG

https://github.com/leresteux/DunogeonFR/commit/515c98963595a9aa8ff1b8e103cc1d5bdf9576a0#diff-f267f9ae2f5d5d56a1dbb305e95d40d4408d9ee7f71357f1f67fb18c29b7f082L1

- name=Dunogeon
+ name=DunogeonFR

As I mentioned above, the indexer rejects any release that doesn't meet the requirements. One of those requirements is that the name value must match the registered library name.

The registration data for the libraries will be updated according to your requests:

but this requires a manual change to the backend database so we must wait for the person with access to the database to find time to do it. Once that is done, the libraries will be listed under the new names in Library Manager and the releases made under those new names will be available.

Duplicate registered library names

The name field value in the library.properties metadata file of both libraries was set to Dunogeon at the time the libraries were submitted to the registry.

Even though the automated system checks for name collisions with previously registered libraries, unfortunately it does not have a check for name collisions between multiple libraries submitted at the same time. We were aware of this deficiency in the checks and intend to eventually resolve it, but since the condition of a name collision within a multiple library submission is very rare, that work has not been given priority.

The lack of a check for this problem in submissions allowed the invalid submission to be accepted by the automated system resulting in both libraries being registered with the same name: "Dunogeon".

The library name is the sole unique identifier used by the Arduino Library Manager system, so the two libraries cannot coexist in the system with the same name.

This problem will be resolved as soon as the library names are updated by the database maintainer to the new unique values "DunogeonENG" and "DunogeonFR".

1 Like

hi,
thank you for your answer and to have checked.
It s my mistake I was too enthusiastic to post this project.
I should have taken more time.

No worries. The problem is partly our fault because ideally the automated submission check system should detect any possible problem with a submission and clearly communicate about it to the library maintainer.

The good news is that the fixes are already queued up and the only thing left to do is wait.

Please let me know if you have any other questions or concerns. Thanks for sharing your libraries with the Arduino community!

Per

I have do some updates and tests, everything is ok (with IDE 2.0.3).

Now just waiting

and ... MERRY XMAS!*

  • but pay attention "winter is coming" tomorrow

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.