| commit | 0ae79a7eff83d52080fbcfd788be860cc25cfd11 | [log] [tgz] |
|---|---|---|
| author | Adrià Vilanova MartÃnez <me@avm99963.com> | Fri Jan 26 21:14:10 2024 +0100 |
| committer | gerritbot <gerritbot@avm99963.com> | Fri Jan 26 21:39:55 2024 +0100 |
| tree | 8a02743be6369af38ebca0b0c6c57117c5e2150a | |
| parent | f19ea43ad9f5ebbfe77e0f2bc717b6bf6b74a9e0 [diff] |
Fix hangs when loading issues Before we merged the code which upgraded the instance to Python 3 we had hangs when loading issues because the instance would be teared down due to reaching the memory limit. After this upgrade, we saw these hangs more consistently (the app wouldn't list issues in the first request but it would in the second one) and we saw 500 errors very rarely. We tried to fix the memory limit error by decreasing the limit of objects which can be cached in memory. However, that did not fix the issue. As tested locally, I saw that when configuring 1 worker, the app wouldn't load issues, but by configuring 2 workers, it would (maybe when it is servicing one request it cannot service another the internal one made to the search endpoints?). Thus, this is a temptative fix for this issue. GitOrigin-RevId: 16cccd88263ba494f9f3093b83fbcac2bfe8ed58
This repo is a fork of the open-source Monorail issue tracker designed to run at bugs.avm99963.com. I've made the code public so it can inspire other developers to host relatively cheap Monorail instances.
Monorail development should generally be contributed upstream, this repo will only accept changes specific to small and relatively cheap instances.
The original README.md file is here below (slightly modified where applicable):
Monorail is the Issue Tracker used by the Chromium project and other related projects. It is hosted at bugs.chromium.org.
If you wish to file a bug against Monorail itself, please do so in our self-hosting tracker. We also discuss development of Monorail at infra-dev@chromium.org.
For Googlers: Monorail's codebase is open source and can be installed locally on your workstation of choice.
For local development on Linux, see Linux development instructions For local development on MacOS and Debian, see MacOs development instructions
Instructions for deploying Monorail to an existing instance or setting up a new instance are here.
See also: Common Development Problems
make pytest
To run a single test:
vpython3 test.py services/test/issue_svc_test.py::IssueServiceTest::testUpdateIssues_Normal
make jstest
If you want to skip the coverage for karma, run:
make karma_debug
To run only one test or a subset of tests, you can add .only to the test function you want to isolate:
// Run one test. it.only(() => { ... }); // Run a subset of tests. describe.only(() => { ... });
Just remember to remove them before you upload your CL.
Monorail supports all browsers defined in the Chrome Ops guidelines.
File a browser compatability bug here.
See: Monorail Frontend Code Practices
See: Monorail Triage Guide.
See: Monorail Deployment
For information on how to use Monorail, see the Monorail User Guide.