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

update GSoC2024 projects in docs #2565

Open
wants to merge 30 commits into
base: stable
Choose a base branch
from

Conversation

sarthakvyas16
Copy link

@sarthakvyas16 sarthakvyas16 commented Oct 12, 2024

  • Further refactoring of mscolab

  • Move (most) communication with server to ConnectionManager class to have
    consistent calls and error handling (e.g. timeout).

  • More consistently use json() method of response.

  • Removed single letter variables.

  • Update mscolab_exceptions.py

update copyright string


Co-authored-by: ReimarBauer rb.proj@gmail.com

Purpose of PR?:

Fixes #2516

Purpose of PR?:
Updated development.rst to reflect recent changes in mscolab.

Changes Made:

Added three lines in development.rst to clarify recent updates regarding the refactoring and use of the ConnectionManager class.
Does this PR introduce a breaking change?
No.

Checklist:

ReimarBauer and others added 30 commits May 24, 2024 09:09
…n-MSS#2431)

Enhancing the functionality of the MSColab server to allow users to upload small images which would replace generic initials as identifiers during login. This feature personalizes user accounts and significantly enhances the visual aspect of user identification and interaction within the MSColab platform.

Co-authored-by: Aryan Gupta <work.aryangupta@gmail.com>
With this flask-migrate is used on application setup to automatically
migrate the configured database to the latest revision shipped with
MSColab. This will make manual migrations in production environments
unnecessary in the future.

Also included is an upgrade path from databases which were previously
manually managed. This entails generating a new database and copying
over all data.
Bumps [benc-uk/workflow-dispatch](https://github.com/benc-uk/workflow-dispatch) from 1.2.3 to 1.2.4.
- [Release notes](https://github.com/benc-uk/workflow-dispatch/releases)
- [Commits](benc-uk/workflow-dispatch@v1.2.3...v1.2.4)

---
updated-dependencies:
- dependency-name: benc-uk/workflow-dispatch
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
When inserting rows into PostgreSQL tables and explicitly setting values
for e.g. auto-increment columns, like the IDs, the associated sequences
aren't automatically updated. This means that without explicitly fixing
the sequences PostgreSQL would try to insert new rows with existing
values for the IDs, failing in the process due to unique constraints.

This issue doesn't affect MariaDB nor SQLite. The former automatically
updates auto-increment counters on insert, the latter simply uses the
last rows ID as a starting point.

This change also extends the tests to try adding a new user after the
migration, which should catch this kind of issue.
Created enum types should also be dropped on downgrade. Dropping tables
must be committed to become visible.
* removing pinned xmlschema (Open-MSS#2117)

* Stop ignoring some test files (Open-MSS#2291)

* Reconfigured tutorial videos for RTFD (Open-MSS#2458)

* changed to videos/

* use mss style on rtfd

* fix urls and text (Open-MSS#2460)

* Bump benc-uk/workflow-dispatch from 1.2.3 to 1.2.4 (Open-MSS#2450)

Bumps [benc-uk/workflow-dispatch](https://github.com/benc-uk/workflow-dispatch) from 1.2.3 to 1.2.4.
- [Release notes](https://github.com/benc-uk/workflow-dispatch/releases)
- [Commits](benc-uk/workflow-dispatch@v1.2.3...v1.2.4)

---
updated-dependencies:
- dependency-name: benc-uk/workflow-dispatch
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Limit video width to the containing block's width (Open-MSS#2463)

* pinning of libtiff is not needed but blocks a more recent libxml2 and others (Open-MSS#2469)

* fixed the model.Message description and tests now using op_id (Open-MSS#2470)

* bug fix for incomplete xml imports (Open-MSS#2468)

validate xml content

* prepare v9.2.0 (Open-MSS#2481)

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Matthias Riße <9308656+matrss@users.noreply.github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Enhancing the functionality of the MSColab server to allow users to upload small images which would replace generic initials as identifiers during login. This feature personalizes user accounts and significantly enhances the visual aspect of user identification and interaction within the MSColab platform.

This includes real-time tracking of active users per operation, enhancing the chat window, seeing who performed what changes and separating system message from user messages.


---------

Co-authored-by: Aryan Gupta <work.aryangupta@gmail.com>
Show in About a new version available.


---------

Co-authored-by: Matthias Riße <9308656+matrss@users.noreply.github.com>
removed the xmlsec binary selector based on CONDA_PREFIX
provided separate config for msidp
separate dir for mscolab server data and work asynchronously by msolab ui


---------

Co-authored-by: Matthias Riße <9308656+matrss@users.noreply.github.com>
* Further refactoring to simplify control flow

Fewer LOC to make things more maintanable.
Also Fix Open-MSS#2514

* Handle Exceptions at the outer level, so no unforeseen errors occur.
Also catch uncaught SocketIO-Exceptions to handle them gracefully.

* better solution
…S#2528)

* option to enable flask debug added

* remove mscolab start from batch

* similiar dir as for the ui

* new module for mscolab restart

* linting satisfied
* join for recording

* fixes Open-MSS#2539

* spelling
* Further refactoring of mscolab

* Move (most) communication with server to ConnectionManager class to have
  consistent calls and error handling (e.g. timeout).
* More consistently use json() method of response.
* Removed single letter variables.

* Update mscolab_exceptions.py

update copyright string

---------

Co-authored-by: ReimarBauer <rb.proj@gmail.com>
* Further refactoring of mscolab

* Move (most) communication with server to ConnectionManager class to have
  consistent calls and error handling (e.g. timeout).
* More consistently use json() method of response.
* Removed single letter variables.

* Update mscolab_exceptions.py

update copyright string

---------

Co-authored-by: ReimarBauer <rb.proj@gmail.com>

**Purpose of PR?**:

Fixes #

**Does this PR introduce a breaking change?**

**If the changes in this PR are manually verified, list down the scenarios covered:**:

**Additional information for reviewer?** :
_Mention if this PR is part of any design or a continuation of previous PRs_

**Does this PR results in some Documentation changes?**
_If yes, include the list of Documentation changes_

**Checklist:**
- [ ] Bug fix. Fixes #<issue number>
- [ ] New feature (Non-API breaking changes that adds functionality)
- [ ] PR Title follows the convention of  `<type>: <subject>`
- [ ] Commit has unit tests

<!--

The PR title message must follow convention:
`<type>: <subject>`.

Where: <br />
- `type` is to define what type of PR is this.
  Most common types are:
    - `feat`      - for new features, not a new feature for build script
    - `fix`       - for bug fixes or improvements, not a fix for build script
    - `chore`     - changes not related to production code
    - `docs`      - changes related to documentation
    - `style`     - formatting, missing semi colons, linting fix etc; no significant production code changes
    - `test`      - adding missing tests, refactoring tests; no production code change
    - `refactor`  - refactoring production code, eg. renaming a variable or function name, there should not be any significant production code changes

- `subject` is a single line brief description of the changes made in the pull request.

-->
@ReimarBauer
Copy link
Member

ReimarBauer commented Oct 12, 2024

Hi @sarthakvyas16 please can you send this change to our stable branch. We want this in the next minor or patch level release. The next major will need some more time.

Please also use a meaningful name for the PR string.

@sarthakvyas16
Copy link
Author

Hi @ReimarBauer

I’ll go ahead and send this change to the stable branch. I’ll also come up with a meaningful name for the PR string.

Thanks for the update.

@sarthakvyas16 sarthakvyas16 changed the base branch from develop to GSOC2024-AryanGupta October 13, 2024 08:50
@sarthakvyas16 sarthakvyas16 changed the base branch from GSOC2024-AryanGupta to develop October 13, 2024 08:50
@sarthakvyas16 sarthakvyas16 changed the base branch from develop to stable October 13, 2024 08:53
@sarthakvyas16 sarthakvyas16 changed the title Develop update GSoC2024 projects in docs Oct 13, 2024
@sarthakvyas16
Copy link
Author

Any other changes??

Copy link
Member

@ReimarBauer ReimarBauer left a comment

Choose a reason for hiding this comment

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

This looks like a merge request from develop to stable.

You need to cherry pick your change and add it to a PR to stable

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.

update GSoC projects in our docs
4 participants