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

Uploaded module not appearing #121

Open
FCO opened this issue Nov 16, 2024 · 4 comments
Open

Uploaded module not appearing #121

FCO opened this issue Nov 16, 2024 · 4 comments

Comments

@FCO
Copy link

FCO commented Nov 16, 2024

I tried uploading my module (ASTQuery) last week (0.0.1) and today(0.0.2) with success, but it is now showing anywhere.

here is the last upload message:

https://irclogs.raku.org/raku/2024-11-16.html#19:33

@mustafaaydn
Copy link

mustafaaydn commented Dec 13, 2024

Hi,
Similar issue here: fez uploaded a module a week ago (~December 7th), it did say

>>= Resources ok
>>= Hey! You did it! Your dist will be indexed shortly.

but it's not visible (in 360.zef.pm, raku.land). An email was received titled "Error processing: ???" whose content is "Error reading META from your last upload", but I'm not sure what it really implies. Thanks for your work on fez.

Versions: fez 55, Rakudo 2024.10

Lastly, there seems to be another (unrelated) bug: last two lines in the .gitignore was resulting in a compile-time error when, e.g., fez-reviewing it; the lines are

\#*\#
.\#*

and the fez review output is

===SORRY!===
Regex not terminated.
at /path/to/IterAble/EVAL_4:1
------> anon regex {  \\#<-[/]>*\\#}⏏<EOL>
Malformed regex
at /path/to/IterAble/EVAL_4:1
------> anon regex {  \\#<-[/]>*\\#}⏏<EOL>
    expecting any of:
        infix stopper

So I didn't include those last 2 lines in .gitignore, then I was able to upload it successfully, so that's a reproduction step if you wanted.

@FCO
Copy link
Author

FCO commented Jan 4, 2025

I just released 3 more distro (and another version of one of them yesterday), and none seems to have worked. The distros were Red, Cromponent, and CSS::Nested (this one is a new one).

Red:

❯ mi6 release --yes
==> Release distribution to Zef ecosystem

  There are 13 steps:
   * Step 1. CheckAuth - Make sure 'auth' in META6.json is 'zef:xxx'
   * Step 2. CheckChanges - Make sure 'Changes' file has the next release description
   * Step 3. CheckOrigin
   * Step 4. CheckUntrackedFiles
   * Step 5. BumpVersion - Bump version for modules (eg: 0.0.1 -> 0.0.2)
   * Step 6. RegenerateFiles
   * Step 7. DistTest
   * Step 8. MakeDist
   * Step 9. UploadToZef
   * Step10. RewriteChanges
   * Step11. GitCommit - Git commit, and push it to remote
   * Step12. CreateGitTag - Create git tag, and push it to remote
   * Step13. CleanDist

==> Step 1. CheckAuth
==> Step 2. CheckChanges
==> Step 3. CheckOrigin
==> Step 4. CheckUntrackedFiles
==> Step 5. BumpVersion
Use next release version 0.1.74
==> Step 6. RegenerateFiles
==> Step 7. DistTest
t/00-meta.rakutest ........................... ok
t/01-tdd.rakutest ............................ ok
t/02-sqlite.rakutest ......................... ok
t/03-blog.rakutest ........................... ok
t/04-ticket.rakutest ......................... ok
t/05-better-map.rakutest ..................... ok
t/06-optimizer.rakutest ...................... ok
t/07-best-tree.rakutest ...................... ok
t/08-alternate-relation.rakutest ............. ok
t/09-alternate-relation-modules.rakutest ..... ok
t/10-join.rakutest ........................... ok
t/11-types.rakutest .......................... ok
t/12-roles.rakutest .......................... ok
t/13-result-seq-update.rakutest .............. ok
t/14-union.rakutest .......................... ok
t/15-result-seq-bool.rakutest ................ ok
t/16-create-related-pars.rakutest ............ ok
t/17-pp.rakutest ............................. ok
t/18-phasers.rakutest ........................ ok
t/19-in-sql.rakutest ......................... ok
t/20-new-with-id.rakutest .................... ok
t/21-red-do.rakutest ......................... ok
t/22-edit-id.rakutest ........................ ok
t/23-metamodel-model.rakutest ................ ok
t/24-grep-no-AND-OR.rakutest ................. ok
t/25-is-rw.rakutest .......................... ok
t/26-classify.rakutest ....................... ok
t/27-LPW-2019.rakutest ....................... ok
t/28-events.rakutest ......................... ok
t/29-result-seq-pick.rakutest ................ ok
t/30-update.rakutest ......................... ok
t/31-join.rakutest ........................... ok
t/32-join.rakutest ........................... ok
t/33-join.rakutest ........................... ok
t/34-ast-generic.rakutest .................... ok
t/35-create.rakutest ......................... ok
t/36-default-deflate.rakutest ................ ok
t/37-json.rakutest ........................... ok
t/38-equal.rakutest .......................... ok
t/39-xmas.rakutest ........................... ok
t/40-relationship-multiple-columns.rakutest .. ok
t/41-fallback.rakutest ....................... ok
t/42-create-table.rakutest ................... ok
t/43-prefetch.rakutest ....................... ok
t/44-error-without-id.rakutest ............... ok
t/45-is-handling.rakutest .................... ok
t/46-rw.rakutest ............................. ok
t/47-rypervenche.rakutest .................... ok
t/48-source-source-id.rakutest ............... ok
t/49-experimental-formater.rakutest .......... ok
t/50-experimental-name.rakutest .............. ok
t/51-pre-create-or-update.rakutest ........... ok
t/52-schema.rakutest ......................... ok
t/53-unique.rakutest ......................... ok
t/54-hand-made-many-to-many.rakutest ......... ok
t/55-no-optimization.rakutest ................ ok
t/56-refreshable.rakutest .................... ok
t/57-experimental.rakutest ................... ok
t/58-nm-relationship.rakutest ................ ok
t/59-tomgraceys-schema.rakutest .............. ok
t/60-runtime-role.rakutest ................... ok
t/61-model-as-type.rakutest .................. ok
t/62-date-coercion.rakutest .................. ok
t/63-inflate-deflate.rakutest ................ ok
t/64-create-on-defined-obj.rakutest .......... ok
t/65-patrickb.rakutest ....................... ok
t/66-join-model.rakutest ..................... ok
t/67-enums.rakutest .......................... ok
t/68-red-config.rakutest ..................... ok
t/69-array-columns.rakutest .................. ok
t/70-submodel.rakutest ....................... ok
t/71-conflicting-column-attribute.rakutest ... ok
t/72-agg-methods.rakutest .................... ok
t/73-red-defaults-from-module.rakutest ....... ok
t/74-enum-reassign.rakutest .................. ok
t/75-patrick-operators.rakutest .............. ok
t/76-view.rakutest ........................... ok
t/77-red-type.rakutest ....................... ok
t/78-datetime-function.rakutest .............. ok
t/79-group-sort.rakutest ..................... ok
t/80-date-operator.rakutest .................. ok
t/81-resultset-skip-locked.rakutest .......... ok
t/82-emakei.rakutest ......................... ok
All tests successful.

Test Summary Report
-------------------
Files=83, Tests=1097,  83 wallclock secs
Result: PASS
==> Step 8. MakeDist
==> Step 9. UploadToZef
Executing /Users/fernando/.rakubrew/versions/moar-blead/install/bin/rakudo -e use Fez::CLI --file=Red-0.1.74.tar.gz upload
>>= Hey! You did it! Your dist will be indexed shortly.
It will appear in https://360.zef.pm/
==> Step10. RewriteChanges
==> Step11. GitCommit
[master 958d452] 0.1.74
 1 file changed, 2 insertions(+)
Enumerating objects: 5, done.
Counting objects: 100% (5/5), done.
Delta compression using up to 8 threads
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 321 bytes | 321.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To github.com:FCO/Red.git
   f51be68..958d452  master -> master
==> Step12. CreateGitTag
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To github.com:FCO/Red.git
 * [new tag]         0.1.74 -> 0.1.74
==> Step13. CleanDist

CSS::Nested:

❯ mi6 release
==> Release distribution to Zef ecosystem

  There are 13 steps:
   * Step 1. CheckAuth - Make sure 'auth' in META6.json is 'zef:xxx'
   * Step 2. CheckChanges - Make sure 'Changes' file has the next release description
   * Step 3. CheckOrigin
   * Step 4. CheckUntrackedFiles
   * Step 5. BumpVersion - Bump version for modules (eg: 0.0.1 -> 0.0.2)
   * Step 6. RegenerateFiles
   * Step 7. DistTest
   * Step 8. MakeDist
   * Step 9. UploadToZef
   * Step10. RewriteChanges
   * Step11. GitCommit - Git commit, and push it to remote
   * Step12. CreateGitTag - Create git tag, and push it to remote
   * Step13. CleanDist

==> Step 1. CheckAuth
==> Step 2. CheckChanges
==> Step 3. CheckOrigin
==> Step 4. CheckUntrackedFiles
==> Step 5. BumpVersion
Next release version? [0.0.1]:
==> Step 6. RegenerateFiles
==> Step 7. DistTest
t/01-basic.rakutest .. ok
All tests successful.
Files=1, Tests=1,  0 wallclock secs
Result: PASS
==> Step 8. MakeDist
==> Step 9. UploadToZef
Are you sure you want to upload CSS-Nested-0.0.1.tar.gz to Zef ecosystem? (y/N) y
Executing /Users/fernando/.rakubrew/versions/moar-blead/install/bin/rakudo -e use Fez::CLI --file=CSS-Nested-0.0.1.tar.gz upload
>>= Hey! You did it! Your dist will be indexed shortly.
It will appear in https://360.zef.pm/
==> Step10. RewriteChanges
==> Step11. GitCommit
[main 256f204] 0.0.1
 1 file changed, 2 insertions(+)
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 8 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (9/9), 933 bytes | 186.00 KiB/s, done.
Total 9 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (4/4), completed with 3 local objects.
To github.com:FCO/CSS-Nested.git
   23da264..256f204  main -> main
==> Step12. CreateGitTag
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To github.com:FCO/CSS-Nested.git
 * [new tag]         0.0.1 -> 0.0.1
==> Step13. CleanDist

and Cromponent:

❯ mi6 release
==> Release distribution to Zef ecosystem

  There are 13 steps:
   * Step 1. CheckAuth - Make sure 'auth' in META6.json is 'zef:xxx'
   * Step 2. CheckChanges - Make sure 'Changes' file has the next release description
   * Step 3. CheckOrigin
   * Step 4. CheckUntrackedFiles
   * Step 5. BumpVersion - Bump version for modules (eg: 0.0.1 -> 0.0.2)
   * Step 6. RegenerateFiles
   * Step 7. DistTest
   * Step 8. MakeDist
   * Step 9. UploadToZef
   * Step10. RewriteChanges
   * Step11. GitCommit - Git commit, and push it to remote
   * Step12. CreateGitTag - Create git tag, and push it to remote
   * Step13. CleanDist

==> Step 1. CheckAuth
==> Step 2. CheckChanges
==> Step 3. CheckOrigin
==> Step 4. CheckUntrackedFiles
==> Step 5. BumpVersion
Next release version? [0.0.3]:
==> Step 6. RegenerateFiles
==> Step 7. DistTest
t/01-basic.rakutest .. ok
All tests successful.
Files=1, Tests=1,  1 wallclock secs
Result: PASS
==> Step 8. MakeDist
==> Step 9. UploadToZef
Are you sure you want to upload Cromponent-0.0.3.tar.gz to Zef ecosystem? (y/N) y
Executing /Users/fernando/.rakubrew/versions/moar-blead/install/bin/rakudo -e use Fez::CLI --file=Cromponent-0.0.3.tar.gz upload
>>= Hey! You did it! Your dist will be indexed shortly.
It will appear in https://360.zef.pm/
==> Step10. RewriteChanges
==> Step11. GitCommit
[main 5831daf] 0.0.3
 2 files changed, 3 insertions(+), 1 deletion(-)
Enumerating objects: 11, done.
Counting objects: 100% (11/11), done.
Delta compression using up to 8 threads
Compressing objects: 100% (8/8), done.
Writing objects: 100% (8/8), 750 bytes | 750.00 KiB/s, done.
Total 8 (delta 6), reused 0 (delta 0), pack-reused 0
remote: Resolving deltas: 100% (6/6), completed with 3 local objects.
To github.com:FCO/Cromponent.git
   d038a4b..5831daf  main -> main
==> Step12. CreateGitTag
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To github.com:FCO/Cromponent.git
 * [new tag]         0.0.3 -> 0.0.3
==> Step13. CleanDist

Does anyone have any idea of what I'm doing wrong?

@coke
Copy link

coke commented Jan 4, 2025

@tony-o - is there a way for raku devops to check logs to see if any errors are associated with these uploads?

@FCO
Copy link
Author

FCO commented Jan 5, 2025

My 3 releases just showed up on raku.land. It seems it was just a delay. Thanks!

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

3 participants