-
Notifications
You must be signed in to change notification settings - Fork 2
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
upstream changes until 2.16.0 #58
Conversation
* feat(fe-2): improved logging * yarn lock update * attempted speckle/shared build fix * helm updates * Updates documentation for helm chart --------- Co-authored-by: Iain Sproat <[email protected]>
…ct size (specklesystems#1685) * test(objects upload): adds a test for large object * print object too large messages in response * allows object maximum size to be configured
* WIP seq-logging * nuxt plugin + infra adjustments
…stems#1695) * fix(helm): only deploy frontend-2 if enabled in helm chart * Do not deploy frontend if frontend-2 is enabled
* Quote values
…st duration metrics (specklesystems#1591) * replaces expressMonitoring.js
… debug (specklesystems#1702) - log as info, not debug level
…isy logging (specklesystems#1703) * fix(fileimport): reduce noisiness of logging * fix(fileimport): return timeout error message to server
* feat(server): change default name of a server * Update 000-core.js
* fix: preparing automation backend for use in FE * minor migration adjustment * modelId only * more CR fixes * improved validation * WIP model automation status (specklesystems#1791) * additional run status insert validations * model card dialog * show view automation btn * story mock fixes * version card dialog --------- Co-authored-by: Gergő Jedlicska <[email protected]>
* fe subscriptions working * minor adjustment
* With Fabian's help we changed the way the default textures are loaded. They are now embeded using another rollup plugin as base64 directly into the js module * Embedded textures * Yarn lock stuff
…rrays as display values. It ignores them and logs a warning message (specklesystems#1795)
…klesystems#1901) * test DX improvements + tests for token:write scope * protecting against scope elevation
@Exilliar - this PR contains a lot of changes the branch is based on #57 which was not merged into main, but is the branch in which our production servers are based on. This PR contains a lot of changes for DUI3/frontend-2 (neither of which we utilize currently) and we have not deviated from upstream, so generally there are no issues with receiving this code down. A couple of key things to review and get a second set of eyes on to check if there are any concerns:
|
@Exilliar - I've also added a change to take our Americas server out of the github actions for our staging environment. Previously, this server would be deployed when the production or staging environment is deployed. At the request of Jeroen, this server is ready for production and therefore should be kept at par with prod code only, and not staging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good!
Tested pushing up a test stream to staging from Rhion (haven't done Revit or Grasshopper, figured that would be overkill)
Also done the token creating test myself and it worked as expected
Description & motivation
Changes:
This PR contains a lot of changes the branch is based on #57 which was not merged into main, but is the branch in which our production servers are based on.
To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References