Closed kipcole9 closed 4 years ago
It shows up for me when running mix hex.info text_corpus_uhdr
. Do you have any custom configuration to other repositories? What does mix hex.config
show?
I think something is wrong, because mix hex.info text_corpus_uhdr
was erroring for me before, but now it is OK. However, this errors:
% mix hex.package fetch text_corpus_udhr 0.1.0
Failed to fetch record for 'hexpm/text_corpus_udhr' from registry (using cache instead)
** (Mix) Downloading https://repo.hex.pm/tarballs/text_corpus_udhr-0.1.0.tar failed:
Request failed (403)
This could be because the package does not exist, it was spelled incorrectly or you don't have permissions to it
The tarball is created in memory so it's also strange that you have a package tarball in your local directory after publishing. What does mix hex.info
show?
@ericmj I created the tarball with mix hex.build
and also checked it with mix hex.build --unpack -o some_dir
. Sorry for the confusion.
The output of mix hex.info
is above and reproduced here:
kip@Kips-iMac-Pro text_corpus_udhr % mix hex.info text_corpus_udhr
No package with name text_corpus_udhr
Output of mix hex.info
:
kip@Kips-iMac-Pro text_corpus_udhr % mix hex.info
Hex: 0.20.5
Elixir: 1.10.3
OTP: 23.0.2
Built with: Elixir 1.10.0 and OTP 21.3
And mix hex.config
. Noting that this is the same config for all my libs, none of which exhibit this strange issue.
kip@Kips-iMac-Pro text_corpus_udhr % mix hex.config
api_key: nil (default)
api_url: "https://hex.pm/api" (default)
cacerts_path: nil (default)
diff_command: "git diff --no-index __PATH1__ __PATH2__" (default)
home: "/Users/kip/.hex" (default)
http_concurrency: 8 (default)
http_proxy: nil (default)
http_timeout: nil (default)
https_proxy: nil (default)
mirror_url: nil (default)
no_verify_repo_origin: false (default)
offline: false (default)
repos_key: nil (default)
resolve_verbose: false (default)
unsafe_https: false (default)
unsafe_registry: false (default)
Just a couple of notes in case it helps:
mix hex.info text_corpus_udhr
return a successful resultYou are spelling the package wrong: text_corpus_udhr
vs text_corpus_uhdr
.
Thats really really embarrassing Eric, sorry for bothering you. I actually spelled the name in mix.exs
incorrectly.
No worries, I do the same thing all the time. Glad we didn't have a very weird bug :)
I published a new library with what appears to be success (including the confirming email) but the package does not appear in the index.
Current behaviour
Package is reported published but is not in the index.
Expected result
If success is reported the package should be in the index, otherwise an error should be returned.
Full output