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

upstream changes until 2.16.0 #58

Merged
merged 439 commits into from
Feb 26, 2024
Merged

upstream changes until 2.16.0 #58

merged 439 commits into from
Feb 26, 2024

Conversation

dtnaughton
Copy link

@dtnaughton dtnaughton commented Jan 22, 2024

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:

  • My pull request follows the guidelines in the Contributing guide?
  • My pull request does not duplicate any other open Pull Requests for the same update/change?
  • My commits are related to the pull request and do not amend unrelated code or documentation.
  • My code follows a similar style to existing code.
  • I have added appropriate tests.
  • I have updated or added relevant documentation.

References

iainsproat and others added 30 commits July 12, 2023 00:40
* 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
…isy logging (specklesystems#1703)

* fix(fileimport): reduce noisiness of logging
* fix(fileimport): return timeout error message to server
gjedlicska and others added 22 commits September 12, 2023 18:12
* 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
@dtnaughton dtnaughton self-assigned this Jan 22, 2024
@dtnaughton
Copy link
Author

@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:

  • Server now allows guest mode (captured within this commit that contains most changes) 469e7b4. This will be toggled off by default on our servers (set in admin settings)

  • A server vulnerability was highlighted by Speckle Systems that:

  • Authorized apps with a token scope 'token write' were able to create a new token in excess of the privileges granted by the original token. Therefore a malicious actor could generated further tokens with other privileges the user held. This was due to the server not verifying that privileges granted to the new token were not in excess of those granted to the requesting token.

  • I've pulled down the relevant changes to patch this issue in ef57c69 and 51333df

@dtnaughton dtnaughton marked this pull request as ready for review January 24, 2024 14:04
@dtnaughton
Copy link
Author

@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.

Copy link
Collaborator

@Exilliar Exilliar left a 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

@dtnaughton dtnaughton merged commit 57624fb into main Feb 26, 2024
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.