Caleb Collins-Parks
Caleb Collins-Parks
We have consistently experienced lengthy delays in coverage reports. Every once in a while we get 504's too. Because of this we are considering just running coveralls on our main...
@afinetooth I want to emphasize how consistent these issues are. We always have slowness in reporting, not just when there's an incident. For example our last three PR's, all opened...
``` $ find . -name node_modules -prune -o -name '*.py' -and -not -path './sandbox/*' -and -not -path './squads_sandbox/*' -print | wc -l 4962 ``` .... so close :sweat_smile: Thanks for...
As a workaround you can pin the version of pyparsing to a earlier version: `pyparsing==2.4.7`
@jamengual Yeah, that should be possible. But either way the PR will still have a breaking change with the db instance id param. I'm going to wait for a maintainer...
Sorry for the delay on responding to the PR review, I've created a ticket so I remember to get to it eventually. It might be a while. Thanks for the...
@macnibblet yes, but it may take a while :see_no_evil: I have the email starred in my inbox along with 30 others.
@zxpower I saw that you commented about this, I just opened up a issue for it FYI
Agreed, If you have multiple microservices listening on different ports on your machine, this could be useful to identify which microservice is being called. Most of the time you can...