918 karma · joined July 23, 2018
Agreed that alerting is important! We alert on job failures, plus we integrate with observability tools like Sentry.
For DLQs, you're right that they have value. We aren't killing DLQs but rather rethinking them with better ergonomics. Instead of having a dumping ground for unacked messages, we're developing a "replay" feature that lets you retry failed jobs over a period of time. Our planned replay feature will run failures in a separate queue, which can be cancelled at any time. The replay itself can be retried as well if there's still a problem
If you run this code:
import dataclasses
@dataclasses.dataclass
class Base:
a: int
b: int = 1
@dataclasses.dataclass
class Child(Base):
c: int
Then you'll get this error: TypeError: non-default argument 'c' follows default argumentHe said he's tried to find others to maintain the project and no one will help. Dunno why it'd be any different if there was a fork.
> ... not expect every installer to give you a dollar.
He isn't asking for every installer to pay. He's asking for enough financial support to work on core-js full-time, which seems reasonable given how depended-on the library is.
But one nice thing is that consumption is less verbose than Python. In Python you write “greet(name=name)” but in TS you write “greet({name})”
Then it’s even worse when there’s also an “allow_raise” param, where the return type will not be None if allow_raise=True. Now you need to write 4 overloaded signatures to account for the 2 polymorphic params