Skip to content

Shared project concurrency (frontend) #1591

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

Conversation

odeimaiz
Copy link
Member

@odeimaiz odeimaiz commented Jul 1, 2020

What do these changes do?

This PR brings the frontend functionalities for the Shared project concurrency #1576.

  • Study cards show lock and tooltip when study is being used somewhere else
  • Optimized backend calls for getting Orgs and orgMembers

lockViaSocket

Related issue number

related to ITISFoundation/osparc-issues#22

How to test

Checklist

  • Did you change any service's API? Then make sure to bundle document and upgrade version (make openapi-specs, git commit ... and then make version-*)
  • Unit tests for the changes exist
  • Runs in the swarm
  • Documentation reflects the changes
  • New module? Add your github username to .github/CODEOWNERS

@odeimaiz odeimaiz changed the title WIP: Shared project concurrency Shared project concurrency (frontend) Jul 2, 2020
@odeimaiz odeimaiz requested review from sanderegg, ignapas, GitHK and pcrespov and removed request for sanderegg July 2, 2020 09:10
Copy link
Contributor

@GitHK GitHK left a comment

Choose a reason for hiding this comment

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

👍 I just don't like the mouse pointer, but that's just me.

ignapas
ignapas previously requested changes Jul 2, 2020
Copy link
Contributor

@ignapas ignapas left a comment

Choose a reason for hiding this comment

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

I could open the study in both windows by quickly clicking on the buttons. Then both users can modify the study at the same time with no error. And it is possible on only one window, to go back to the dashboard and inside the study again (no blocking even if the other window still has the study opened)

@odeimaiz
Copy link
Member Author

odeimaiz commented Jul 2, 2020

I could open the study in both windows by quickly clicking on the buttons. Then both users can modify the study at the same time with no error. And it is possible on only one window, to go back to the dashboard and inside the study again (no blocking even if the other window still has the study opened)

Yep, good catch! I was also able to reproduce it.

Unfortunately, this is a bug in the backend and this PR only provides the frontend for the existing backend. Could you please crate a bug case and assign it to @sanderegg ?

@odeimaiz odeimaiz requested review from pcrespov and ignapas July 2, 2020 13:28
@GitHK
Copy link
Contributor

GitHK commented Jul 2, 2020

I could open the study in both windows by quickly clicking on the buttons. Then both users can modify the study at the same time with no error. And it is possible on only one window, to go back to the dashboard and inside the study again (no blocking even if the other window still has the study opened)

Yep, good catch! I was also able to reproduce it.

Unfortunately, this is a bug in the backend and this PR only provides the frontend for the existing backend. Could you please crate a bug case and assign it to @sanderegg ?

Also please tag me in the discussion I might know what happened.

Copy link
Contributor

@ignapas ignapas left a comment

Choose a reason for hiding this comment

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

🆗 client part... with some concerns: #1596

@odeimaiz odeimaiz merged commit cb0094b into ITISFoundation:master Jul 2, 2020
@odeimaiz odeimaiz deleted the sanderegg-is/shared_project_concurrency2 branch July 17, 2020 15:45
@odeimaiz odeimaiz mentioned this pull request Aug 4, 2020
odeimaiz added a commit that referenced this pull request Aug 4, 2020
- UI/UX improvements (#1657)
- Bump yarl from 1.4.2 to 1.5.1 in /packages/postgres-database (#1665)
- Bump ujson from 3.0.0 to 3.1.0 in /packages/service-library (#1664)
- Bump pytest-docker from 0.7.2 to 0.8.0 in /packages/service-library (#1647)
- Improving storage performance (#1659)
- Bump aiozipkin from 0.6.0 to 0.7.0 in /packages/service-library (#1642)
- Theming (#1656)
- Platform stability:  (#1645)
- is1594 fix and re-activate e2e testing (#1620)
- 2 bugs fixed + Some improvements (#1634)
- Fixes default (#1640)
- Bump lodash from 4.17.15 to 4.17.19 (#1639)
- Is1585/cleanup storage (#1586)
- Fixes on publish studies handling (#1632)
- Some enhancements and bug fixes (#1608)
- Improve e2e  (#1631)
- filter studies by name before deleting them (#1629)
- Maintenance/upgrades test tools (#1628)
- Bugfix/concurent opening projects (#1598)
- Bugfix/allow reading groups anonymous user (#1615)
- Bump docker from 4.2.1 to 4.2.2 in /packages/postgres-database (#1605)
- fix testing if node has gpu support (#1604)
- [bugfix] Invalidate cache before starting a study (#1602)
- Feature/fix e2e 2 (#1600)
- fix deploy not needing e2e testing since it is disabled
- reduce cardinality of metrics (#1593)
- Excudes e2e stage from include until fixed (#1595)
- Shared project concurrency (frontend) (#1591)
- Homogenize studies and services (#1569)
- [feature] UI Fine grained access - project locking and notification
- Bugfix/apiserver does not need sslheaders (#1564)
- Cleanup catalog service (#1582)
- Maintenance/cleanup api server (#1578)
- Adds support for GPU scheduling of computational services (#1553)
- Maintenance/upgrades and tooling (#1546)
- Is1570/study fails 500 (#1572)
- Bump faker from 4.1.0 to 4.1.1 in /packages/postgres-database (#1573)
- maintenance fix codecov reports (#1568)
- Manage groups, Share studies (#1512)
- Is/add notebook migration script (#1565)
- Is1269/api-server upgrade (#1475)
- added simcore_webserver_service in pytest simcore package (#1563)
- add traefik endpoint to api-gateway (#1555)
@sanderegg sanderegg mentioned this pull request Aug 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:frontend issue affecting the front-end (area group)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants