Add a check prior to activate the sentry configuration
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 31 2022
@vlorentz fixed another error directly within the model to deal with old versioned objects out of the model.
This meant a new release for swh.model and swh.indexer.Unfortunately, now the indexer debian build is broken due to the objstorage debian build being broken...
objstorage build unstuck [1]
Triggered back the build for indexer.
@vlorentz fixed another error directly within the model to deal with old versioned objects out of the model.
This meant a new release for swh.model and swh.indexer.Unfortunately, now the indexer debian build is broken due to the objstorage debian build being broken...
@vlorentz fixed another error directly within the model to deal with old versioned objects.
This meant a new release for swh.model and swh.indexer.
Rebase
Aug 30 2022
Drop the debian constraint on python3-rdflib. Trigger a rebuild and upgraded the package
again. Added the unconditional dependency on python3-rdflib-jsonld dependency (which on
latest debian release is not useful but without being a blocker).
Workers refuse to upgrade to the actual 2.4.3 version [1]. I did not realize my previous
upgrade from yesterday stopped at the v2.3.0.
Adapt according to suggestion
Consumer lag is steadily increasing since yesterday [1]. I believe workers are hit by [2] issue.
I've opened [3] to try and unstuck it.
closing as T4459 will take care of this
Aug 29 2022
Amend commit message
Aug 26 2022
Amend commit message
Adapt configuration to use a backends key which reference the possible graphql backends
Update deps accordingly after releasing a new graphql release
looks like swh.graphql==0.0.2.post2 is an old grapqhl release ?