Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document stabilization attempts #596

Closed
tripleee opened this issue Feb 20, 2019 · 2 comments
Closed

Document stabilization attempts #596

tripleee opened this issue Feb 20, 2019 · 2 comments
Labels
area: infrastructure Servers, software, versions, deployments, all of the Stuff that is teward's purview as sysadmin. type: discussion Something that requires discussion among the team.

Comments

@tripleee
Copy link
Member

I could find no ticket which describes what has been done to attempt to make Metasmoke more stable. Could we please have a ticket (such as, I dunno, this one?) where these tweaks are documented for visibility and followed up on?

I know the regex route in the API has been turned off experimentally and I see a bunch of commits which have "OOM" in the title, but this text should probably be replaced by something written by someone who knows about what was done and why.

@tripleee
Copy link
Member Author

Sorry if this is a duplicate; I searched for an existing ticket but I might have missed it, or looked in completely the wrong places.

@angussidney angussidney added type: discussion Something that requires discussion among the team. area: infrastructure Servers, software, versions, deployments, all of the Stuff that is teward's purview as sysadmin. labels Mar 3, 2019
@thesecretmaster
Copy link
Member

Gonna close this since I believe MS has been pretty stable recently -- the past instability was introduced by some changes I was making, but it should all be good now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: infrastructure Servers, software, versions, deployments, all of the Stuff that is teward's purview as sysadmin. type: discussion Something that requires discussion among the team.
Development

No branches or pull requests

3 participants