Zoltan Fedor

Hi @shrekris-anyscale, @edoakes, I don't believe this is fully fixed, or something might be wrong somewhere. The PR has only removed the two example metrics (`serve_backend_queuing_latency_ms` and `serve_replica_queued_queries`) I have...

This is the node placement of my test cluster. I have connected to all nodes manually and verified that none of them contain the missing metrics. 

It is hard to create a reproducible example for this if I never managed to reproduce the way how it is supposed to work. So I can't tell what is...

Okey, so here is a small reproduce-able example. Matter of fact I couldn't make those metrics to show up at all. 1. Deploy Ray cluster v2.0.0rc0 (Py39) (in our case...

Ok, I have figured out what is happening. A handful of the Ray Serve metrics are ONLY collected when the HTTP request is used to query and not when queried...

Hi @shrekris-anyscale , Sure, I am happy to raise the two tickets and also make a PR for #1. My only concern with the PR, that actually I haven't yet...

+1

I have the exact same concern. Using `JIRA.search_issues()` having all issues loaded into a list is a memory hog and limits the maximum number of issues you can process by...

I was struggling with this too. My solution ended up being to dynamically overwrite the login_manager.request_loader and returning the user I want to be authenticated when calling the protected endpoint....

Yes, and I keep getting this at different points in the sync. See the same error below at a later point in the sync compared to the one above. ```...