Report render process manager v2.0
This commit is contained in:
@@ -26,15 +26,12 @@ ISSUE: reporting failing on linux under load
|
|||||||
zombie processes?
|
zombie processes?
|
||||||
https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
|
https://developers.google.com/web/tools/puppeteer/troubleshooting#running_puppeteer_in_docker
|
||||||
|
|
||||||
todo: Test my killing process thing on Linux and ensure no more than one process of chrome is there at a time and the test can't kill the server
|
|
||||||
make sure it works before proceeding
|
|
||||||
Also there was that no single process setting change to check into as well
|
|
||||||
|
|
||||||
|
todo: rejig render stuck process killer to be thread safe and have a configurable number of allowed running simultaneous headless browser pdf processors
|
||||||
todo:
|
|
||||||
ideally it should allow at least two or three instances at once and track all and return a server busy response to try again if no free slot available
|
ideally it should allow at least two or three instances at once and track all and return a server busy response to try again if no free slot available
|
||||||
so it will need a list of instances with age and process id
|
so it will need a list of instances with age and process id
|
||||||
Report rendering at client must respond back with the too busy message and try again
|
Report rendering at client must respond back with the too busy message and try again
|
||||||
|
503 Service Unavailable
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
@@ -264,6 +261,8 @@ function ayGroupByTag(reportDataArray, tagContains) {
|
|||||||
\_____|______|_____|______|_| \_| |_|
|
\_____|______|_____|______|_| \_| |_|
|
||||||
|
|
||||||
|
|
||||||
|
- 1 todo: server settings ops page is not showing new report rendering settings, it appears to have static items it expects and displays :(
|
||||||
|
|
||||||
- 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925
|
- 1 todo: firefox schedule fix: https://github.com/vuetifyjs/vuetify/issues/14243#issuecomment-944907925
|
||||||
- 1 todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated
|
- 1 todo: admin-history page showing http://localhost:8080/adm-history LT:Global but other things are properly translated
|
||||||
|
|
||||||
@@ -289,7 +288,9 @@ function ayGroupByTag(reportDataArray, tagContains) {
|
|||||||
https://stackoverflow.blog/2021/10/06/best-practices-for-authentication-and-authorization-for-rest-apis/?utm_source=Iterable&utm_medium=email&utm_campaign=the_overflow_newsletter
|
https://stackoverflow.blog/2021/10/06/best-practices-for-authentication-and-authorization-for-rest-apis/?utm_source=Iterable&utm_medium=email&utm_campaign=the_overflow_newsletter
|
||||||
|
|
||||||
|
|
||||||
|
- 2 metrics ops page should show the little dots so know where to position the mouse to see the reading at that point
|
||||||
|
also, there needs to be more "dots", it's too few to get proper idea
|
||||||
|
also todo under server that metrics isn't really capturing the whole server metrics only the ayanova process metrics as far as I can tell
|
||||||
|
|
||||||
-2 hyperlinks in memos sb clickable to open in new tab or window or whatever
|
-2 hyperlinks in memos sb clickable to open in new tab or window or whatever
|
||||||
this supports help links in migrate and also user links like "take a look at workorder 55" with a link to it in the UI
|
this supports help links in migrate and also user links like "take a look at workorder 55" with a link to it in the UI
|
||||||
|
|||||||
Reference in New Issue
Block a user