Alex Ullrich

I was seeing this error with an older version as well but it stopped on update. I am getting invalid mocks generated now (imports "github.com/nats-io/") but I think it is...

Cool good idea I think that should work. Would the change to the cli / web UI just be to indicate unlimited when we have a negative number @hibiken ?...

Incidentally I used max int64 in the meantime and noticed it overflowed to -1 in our telemetry stuff. It was a sign.

Aha saved me a step :) I wonder if it makes sense to base the option off int32 as part of this change.

example output from asynq task list w/ unlimited retries (-1) on a task: ``` ➜ asynq git:(master) ✗ asynq task list --state=retry --queue=default --db 8 ID Type Payload Next Retry...

Sorry @hibiken I have been underwater for a bit. I think this seems OK going to start looking at any asynqmon changes needed when I get a chance.

I think the best way to tackle this in v2 is probably to keep the sequence and add a new string column for UUID. Its easy to backfill with UUIDs...

https://github.com/ThreeDotsLabs/watermill offers a nice pattern for the "webhook to message" adapter - you basically can use their HTTP middleware as the receiver and output to any supported back end. Here...

I think the upstream PR got lost in gerrit-land on this one, I can try to resubmit but any concern about defining an endpoint internally in the interim if this...

This PR will enable defining provider-specific signing keys as part of the configured credentials and should unblock future work here https://github.com/keratin/authn-server/pull/236