issues
search
planetary-social
/
nos-event-service
A service which collects various events to pass them to other Nos services e.g. the notification service.
Mozilla Public License 2.0
1
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Bump event limits
#93
dcadenas
closed
3 weeks ago
0
Try goroutines for metrics
#92
dcadenas
closed
3 months ago
0
Simplify backpressure handling
#91
dcadenas
closed
3 months ago
0
Add jitter timeout, fixes and use lock
#90
dcadenas
closed
3 months ago
1
Load shedding for event service
#89
dcadenas
closed
3 months ago
4
Load shedding instead of disconnection under backpressure
#88
dcadenas
closed
4 months ago
0
Backpressure signal and ReadOnly tx
#87
dcadenas
closed
5 months ago
0
Remove nostr.band
#86
dcadenas
closed
5 months ago
0
[Notifications] Investigate adding follows as a notification to the notifications service
#85
setch-l
closed
3 months ago
1
Deal with events service queue size
#84
dcadenas
opened
7 months ago
2
Add metrics for rate limits
#83
dcadenas
closed
7 months ago
0
Correctly identify CLOSED messages and rate limit on them too
#82
dcadenas
closed
7 months ago
0
Shared rate limiter for multiple conns
#81
dcadenas
closed
7 months ago
1
Rate limit from notice warnings
#80
dcadenas
closed
7 months ago
0
More validations and check it before push to queue
#79
dcadenas
closed
8 months ago
0
Add more granular info for Grafana dashboard for event service
#78
dcadenas
closed
7 months ago
1
[Event Service] Evict items in events service queue that have been there for too long
#77
dcadenas
closed
5 months ago
3
[Event Service] Understand & briefly document how the event and notification services work today
#76
setch-l
closed
5 months ago
6
Increase timeout
#75
dcadenas
closed
8 months ago
0
Handle closed messages
#74
dcadenas
closed
8 months ago
0
Add more comments
#73
dcadenas
closed
8 months ago
0
Add flake for local development
#72
cooldracula
closed
9 months ago
0
Add _health endpoint
#71
cooldracula
closed
9 months ago
0
Add deployment to readme
#70
cooldracula
closed
9 months ago
0
Add internal pubsub description
#69
boreq
closed
9 months ago
0
Sometimes we fail to push events to the relay and the queue length goes up
#68
boreq
closed
7 months ago
4
Fix all generators getting the same parameters
#67
boreq
closed
9 months ago
0
Incorrect context
#66
boreq
closed
9 months ago
0
Refactor task tracker
#65
boreq
closed
9 months ago
0
Optimize memory usage
#64
boreq
closed
9 months ago
0
Clearly log when runners terminate
#63
boreq
closed
9 months ago
0
Less aggressive task scheduling
#62
boreq
closed
9 months ago
0
Less logging
#61
boreq
closed
9 months ago
0
Time window based replication
#60
boreq
closed
9 months ago
0
Add pyroscope metrics
#59
boreq
closed
9 months ago
3
Add uploading pyroscope metrics
#58
boreq
closed
10 months ago
0
Download p tags
#57
boreq
closed
10 months ago
0
Allow transactions to timeout
#56
boreq
closed
10 months ago
0
Optimize downloader
#55
boreq
closed
10 months ago
0
Reduce memory usage and number of goroutines when sending events
#54
boreq
closed
10 months ago
0
[Event Service] Replicate events from Discovery tab recommended users.
#53
boreq
closed
5 months ago
1
[Event Service] Intermittent high CPU usage
#52
boreq
closed
9 months ago
4
Lower timeout when pushing events to relay.nos.social
#51
boreq
closed
10 months ago
0
Add a program that uploads all events to a relay
#50
boreq
closed
10 months ago
0
Add an endpoint for listing events
#49
boreq
closed
10 months ago
0
Also replicate events which include public keys to monitor as p tags
#48
boreq
closed
10 months ago
0
Public key info
#47
boreq
closed
10 months ago
0
Registration: allow empty relays, check event kind
#46
boreq
closed
10 months ago
0
Verify events as late as possible
#45
boreq
closed
10 months ago
0
Avoid loading events for no reason
#44
boreq
closed
10 months ago
0
Next