-
-
Notifications
You must be signed in to change notification settings - Fork 127
Open
Labels
Description
I am trying to build a bosh release for gemstash.
However, I am running into the following issue when I try to push gem to gem stash private registry
<tr>
<td>sinatra.error</td>
<td class="code"><div>#<NameError: uninitialized constant Gemstash::DB::Authorization
Did you mean? Gemstash::Authorization></div></td>
</tr>
<tr>
<td>sinatra.route</td>
<td class="code"><div>POST /api/v1/gems</div></td>
</tr>
</table>
<div class="clear"></div>
</div> <!-- /RACK ENV -->
<p id="explanation">You're seeing this error because you have
enabled the <code>show_exceptions</code> setting.</p>
</div> <!-- /WRAP -->
</body>
</html>
If I bosh ssh into the server and start gem stash manually with "./gemstash start", the issue would not occur at all.
I am trying to look for where "Gemstash::Authorization" and "Gemstash::DB::Authorization" are being referred to in the source code. They seem to be at:
ruby-registry/8be6df83-5351-43d2-8a3c-d81da4ba6653:/var/vcap/packages/ruby-registry/bin# grep -r "Gemstash::DB::Authorization" /
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/authorization.rb: Gemstash::DB::Authorization.insert_or_update(auth_key, permissions)
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/authorization.rb: record = Gemstash::DB::Authorization[auth_key: auth_key]
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/authorization.rb: record = Gemstash::DB::Authorization[auth_key: auth_key]
ruby-registry/8be6df83-5351-43d2-8a3c-d81da4ba6653:/var/vcap/packages/ruby-registry/bin# grep -r "Gemstash::Authorization" /
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/api_key_authorization.rb: # Authorize actions via an API key and Gemstash::Authorization.
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/api_key_authorization.rb: Gemstash::Authorization.check(@key, permission)
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/cli/authorize.rb: Gemstash::Authorization.remove(auth_key(false))
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/cli/authorize.rb: unless Gemstash::Authorization::VALID_PERMISSIONS.include?(arg)
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/cli/authorize.rb: valid = Gemstash::Authorization::VALID_PERMISSIONS.join(", ")
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/cli/authorize.rb: Gemstash::Authorization.authorize(auth_key, permissions)
/var/vcap/data/packages/ruby-registry/d2beb2b654958527c2fcec06b2cbaeb6396a273a/lib/ruby/gems/2.5.0/gems/gemstash-1.1.0/lib/gemstash/cli/authorize.rb: key = SecureRandom.hex(16) while Gemstash::Authorization[key]
DO you have any idea what could have cause gemstash to behave differently when being started with bosh as opposed to being started manually?