Skip to content

Conversation

@davidhagan
Copy link
Collaborator

This brings an alternate history backend (sql driver with an apache db commons threadpool) to save checkresults, so that we can build a service health dashboard with historical data, and it also brings an update to lift, scala and some of the libraries.

build.sbt Outdated
"com.sun.mail" % "javax.mail" % "1.6.2",
"com.hacklanta" %% "lift-formality_3.3" % "1.2.0",
"io.github.classgraph" % "classgraph" % "4.6.18",
"com.sksamuel.scrimage" % "scrimage-core_2.12" % "3.0.0-alpha4",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need alpha dependencies?

@@ -0,0 +1,359 @@
/*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you hack this from the original version? (Why copy into the project?)

@davidhagan
Copy link
Collaborator Author

davidhagan commented Aug 6, 2020 via email

@davidhagan
Copy link
Collaborator Author

davidhagan commented Aug 6, 2020 via email

dave-low-priv and others added 30 commits April 13, 2021 10:14
… should be MUCH lighter on the client because it's not doing constant re-renders
…, and also added two more endpoints to return history for entire servers or for entire services
Setting the default login page to /simple
…eHandler to handle cookies which start with . but are willing to accept undotted uris, so that https://a.b.c uses a cookie which requires .a.b.c, which is now handled by browsers.
…'re subscribed to a level of severity. Tuned many debug statements down to trace. Reduced default apache.http packages down in log visibility. Shifted default .sbt mode to production so that notifiers work and can be tested. No change on frontend.
…ing use of it to use the apache 5.1 async client. The existing synchronous client is still accessible, just in case there's any weirdness which is discovered later. Both script checks and normal checks have been upgraded to support full async behaviour, and this has been tested against our existing set of checks.
…tp client. This means that we should now be able to move quacker to using the new branch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants