pathspec 1.0 was released on Jan 5 but we have never seen this issue. https://rubygems.org/gems/pathspec.
As Alex pointed out, the problem is not consistent and I guess this is a temporal issue caused by unstable connection to rubygems.
pathspec 1.0 was released on Jan 5 but we have never seen this issue. /rubygems. org/gems/ pathspec.
https:/
As Alex pointed out, the problem is not consistent and I guess this is a temporal issue caused by unstable connection to rubygems.