-
-
Notifications
You must be signed in to change notification settings - Fork 2k
change repo urls of some of our existing libraries #4512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Hi @einspunktnull. If you intended to submit a library, please check the instructions and update your pull request if necessary: |
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/voltmeter:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/timeout-callback:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/simple-serial-protocol-arduino:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/average-value:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/interval-callback:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @einspunktnull. I am confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will merge this pull request when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the libraries via their dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager
Hi @einspunktnull. If you intended to submit a library, please check the instructions and update your pull request if necessary: |
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/timeout-callback:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/simple-serial-protocol-arduino:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/average-value:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/interval-callback:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/voltmeter:
|
Hi @einspunktnull. If you intended to submit a library, please check the instructions and update your pull request if necessary: |
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/average-value:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/interval-callback:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/simple-serial-protocol-arduino:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/timeout-callback:
|
Arduino Lint has suggestions for possible improvements to https://github.com/yesbotics/voltmeter:
|
Hello @einspunktnull @per1234, I'm reporting the following errors:
|
@MatteoPologruto I performed an investigation into the unexpected failure of the CauseThe cause of the problem is a change in the behavior of libraries-repository-engine that I inadvertently introduced in arduino/libraries-repository-engine@d0f3044. Prior to arduino/libraries-repository-engine@d0f3044, archives were stored under a folder structure named according to the final two components of the parent of the repository URL. After the change, the name format was changed to For a GitHub repository, or a GitLab repository under a personal account or in the root of a group, the two different approaches to determining the archive folder structure are equivalent. For example, For example, prior to arduino/libraries-repository-engine@d0f3044 release archives for This only affected maintenance operations because the "DB" is stored persistently, so the generated libraries index had the correct So the fault you encountered only occurs when a
I did a survey to determine the full scope of the impact of the regression and found that it happens the libraries that are the subject of this request were the only ones affected by the regression. Even though the change in behavior is a regression for this specific scenario, it was actually an improvement going forward because an archive path like You might have noticed that there is still a bug in how the archive paths are determined for GitLab subgroup repos, since the correct archive folder structure should have a form like SolutionHere is an overview of the sequence of operations that will resolve this must perform to :
1. Move Archive FilesThis operation is performed solely in order to allow the next step to succeed ( Please run the following commands on the "backend" machine:
2. Remove LibrariesPlease perform a library removal operation on the backend machine. The reason for doing this is that, even though the previous operation moved the library release archive files to the modern paths, the "DB" entries for those library releases still have Although this could be resolved by manually updating the data in the "DB", I think it is easier to just remove the libraries, which will result in the correct entries being automatically generated on the next run of the So please perform the standard library removal procedure (i.e.,
3. Merge PRsNext, please merge the URL change PRs here in the
This will result in the next 4. SyncThis is the standard This will index the libraries once again, generating the DB entries with the correct No manual action is required for this operation as it will happen as a matter of course via the scheduled job. |
No description provided.