Fabrizio Ferrai

@joprice can you link to the branch you mention?

I see! My maintenance of this repo is limited to merging PRs, so if you'd like to upgrade I'd happily merge that. It should be enough to run the scripts...

This is another downstream consequence of the whole "lockfiles make spago not hit the network": we used to always pull the registry _and_ refresh the database, but we don't do...

Had a little digging: - every time we pull the Registry we update the package set entries in the DB, so - as you verified - these are always up...

> Is there a reason not to fully update the database (ie. including metadata) every time we pull the registry? "Fully update the database" in this case would mean reading...

I wonder if this logic is at fault? https://github.com/purescript/spago/blob/82d99ab015e3852e25ab9f8ae36bbce2bf338cdd/src/Spago/Registry.purs#L195-L207 The important bit is that `not fetchingFreshRegistry`: if we have cached a metadata file, we only go read it if we...

@Zelenya this is a related issue, but a different bug 🙂 It is the same issue as #1212, and the fix for that (#1214) was too ad-hoc and missed the...

Released in [0.93.35](https://www.npmjs.com/package/spago/v/0.93.35)

> something that's been bothering me about bleeding spago is that it walks gitignored dirs looking for workspace members, including node_modules and errors when there are .gitignored read-protected dirs (ex....

Thanks for the ping! I was waiting for CI to be done then forgot to check on it, sorry 🥲