Skip to content
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

Cryptic error thrown when "_" included in repository name #57208

Closed
alex-s-gardner opened this issue Mar 24, 2022 · 1 comment
Closed

Cryptic error thrown when "_" included in repository name #57208

alex-s-gardner opened this issue Mar 24, 2022 · 1 comment

Comments

@alex-s-gardner
Copy link

Registering my first package I got the following cryptic error thrown by AutoMerge.run:

Error: Some registries failed to update:
│     — `/tmp/jl_Mc2e8U/registries/General` — registry dirty
└ @ Pkg.Registry /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.7/Pkg/src/Registry/Registry.jl:450

After a bunch of searching and digging I realized that my package name was non-conforming and included an underscore ("_") in the package name.

I realize that the correct naming convention is detailed here: https://juliaregistries.github.io/RegistryCI.jl/stable/guidelines/#Automatic-merging-guidelines

But I missed the only "alphanumeric characters" in my first skim of the document

I wonder if a check could be added for basics things like conforming package names and that a [compat] list is included in the .toml file... this would make it easier for non-observant people like me to trace issues with first-time package registration... then again, maybe it's good to have a bit of a barrier to keep lazy readers like me from registering a package ;-)

@DilumAluthge
Copy link
Member

DilumAluthge commented Mar 24, 2022

I wonder if a check could be added for basics things like conforming package names and that a [compat] list is included in the .toml file

All of these checks already exist, and the list of failed checks is posted in the AutoMerge comment, e.g. #57187 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants