- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Nov 23 2021
In D6395#173428, @ardumont wrote:Heads up, I was correct and that'd be D6666 for the fix.
It's a type issue unrelated to your diff, the master build must be broken as well. Since
nothing changed on the lister for a while, I guess a new mypy release (with some
internal change) make that type now break.Don't worry about it, I'll have a look to fix master, push and then you can rebase so
your build gets green again.
Thanks for the update.
Hi there,
Hum. I don't understand why the tests fail on the sourceforge lister when it's not listed in my diff. Any idea please?
Build has FAILED
- maven-lister: Add maven lister with review D6133.
- maven-lister: Add statefulness
- maven-lister: Fix README, 88 chars, minor typos
- maven-lister: Split parsing and processing
- maven-lister: Fix groupId bug, add tests.
- maven-loader: fix last_update
Build is green
- maven-loader: fix tests for snapshot-append
Build has FAILED
- maven-loader: fix last_update
Nov 22 2021
Build has FAILED
- maven-loader: various fixes for vlorentz' review
- maven-loader: remove snapshot_append carryover
- maven-loader: final udpate after vlorentz review
diff --git a/swh/scheduler/journal_client.py b/swh/scheduler/journal_client.py index c001a48..e2a18ad 100644 --- a/swh/scheduler/journal_client.py +++ b/swh/scheduler/journal_client.py @@ -4,7 +4,7 @@ # See top-level LICENSE file for more information
I had hot-patched this to clamp dates to datetime.datetime.max, if an overflow was detected. Of course I never actually committed the change. D'oh.
The stacktrace error is the same but in the end, it's the current position (/ default_queue_position)
of the queue (so per visit type) which are too far ahead in the future... [1]
Hence adding any offset creates the overflow problem.
lgtm
Thanks.
We haven't had the capacity of making the azure infrastructure perform as well as the in-house one, to the point where the web frontend wasn't really useable.
I had another round.
I've added suggestions about docs, fixing log instructions, etc...
There is no azure kafka cluster anymore...
@borisbaldassari I've renamed T1724 and gave a rather succinct summary