Ilya Priven

When overriding `exclude_lines` e.g. to exclude `pytest.fail` or `...`, we often include the existing `DEFAULT_EXCLUDE` pattern (currently `\#\s*(pragma|PRAGMA)[:\s]?\s*(no|NO)\s*(cover|COVER)`) to maintain the effect of existing "pragma: no cover"s. This is cumbersome...

implement InvalidateNode/InvalidateEntry

1

Implement `fuse_lowlevel_notify_inval_inode`. This should allow user space processes to trigger eviction of the kernel's inode cache, and in turn getting the "ForgetInodeOp" to evict its own data. Context: https://sourceforge.net/p/fuse/mailman/message/30057855/

It seems like libfuse initializes the dir entry's inode to this value (-1), rather than zero.

This is useful for users on Ubuntu LTS.

Support for SQS DelaySeconds

4

SQS has a built-in "DelaySeconds" feature that could support Celery's ETA/Countdown feature for up to 15 minutes. https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-send-message-with-timer.html

Add must_get_event_loop

1

We'll use `must_get_event_loop` where we assume a non-`None` hub in the following code.

Instrumenting SQS ApproximateReceiveCount

3

In its response to [ReceiveMessage](https://docs.aws.amazon.com/AWSSimpleQueueService/latest/APIReference/API_ReceiveMessage.html), SQS can provide an (optional) attribute called `ApproximateReceiveCount`. This attribute allows for rudimentary diagnostics of retries resulting from worker termination (assuming late ACKs). Can it...

docs: use ParamSpec in "Declaring decorators"

1

Resolves #12983.

Syntax nits to make IntelliJ happy

3

- `React.Props` type is deprecated - Rewrite comma expression

cocoapods.org point to missing 0.9.13 release

2

https://cocoapods.org/?q=tsmessages Clicking on "see podspec" leads to 404: https://github.com/CocoaPods/Specs/blob/master/Specs/TSMessages/0.9.13/TSMessages.podspec.json Maybe it could be fixed by: a) submitting the missing 0.9.13 podspec b) tagging the 0.9.13 release on the github.com/KrauseFx/TSMessages repo