Add the GET "/api/v4/projects/27/packages/rubygems/quick/Marshal.4.8/test_gem-1.0.0.gemspec.rz route. 2
Notes
This route serves the .gemspec file. The .gemspec file is saved as an associated package file during the metadata extraction, but is not in the .rz format. So it can be accessed through that file, or the specification object can be accessed through the original .gem file, using Gem::Package.new(gem_file).spec.
According to the command reference ".rz files are compressed with the inflate algorithm".
The inflate algorithm is in the base Gem module, also some notes located here in the source code.
Hi @renehernandez! You are very welcome to contribute here! Let me know if you have any questions about the issues in the RubyGems epic or contributing to GitLab in general. You can feel free to @ ping me directly in issues or MRs with questions or for code reviews.
Here is a quick summary of the various issues in the epic:
If I recall, this issue and #299267 are the two issues we need to be able to install gems with gem install and bundle install.
We discovered in some testing that we will need to expand some database constraints to allow for storing some longer values that come from the gemspec file. That update is captured in #333607.
Before we are able to enable the feature on GitLab.com, we need to work through #339301 which is a small performance optimization.
Hey @renehernandez! I was able to open a new workspace for gitlab-org/gitlab without any issues. FWIW, I occasionally run into this issue, but simply reloading or going to / resolves the issue. Could you try?
@sabrams@trizzi I am switching priorities for a bit. We are starting to expand our usage of the GitLab Terraform Registry and I noticed that there are some issues left to solve that I want to help solve first, since it is going to impact us as we depend more on it.
I'll come back to the RubyGems milestone once I've finish my contributions in the TF milestone
OK cool @renehernandez. Please feel free to tag me on the Terraform issues as well as the Package group is likely to take ownership of that feature in the coming months.
Knowing very little about the GitLab architecture, I would think the first thing to do would be to create this in the CreateGemspecService alongside the .gemspec file: