Update installation manual #2229
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merge stable to develop
Merge stable into develop
* Tests added for remote sensing widget * Fixed flake8 * Flake8 fixed * Updated authors * AUTHORS updated * Fixed pytest errors * Issues resolved * Import order updated * Changes made * Update test_remotesensing.py * Data reorganized * Update test_remotesensing.py
Merge stable to develop
* added stuff * keyring tidy up * fixed some testcases * fixed keyring * added method to 'clear' keyring * split connect tests and added a '401' one for authorization denied case * adapted to comments * adapted to comments * renamed http_auth to mss_auth * removed misplaced http_basic_auth statment * updated keyring related documentation * updated status messages. * update * update
* fill mswms_settings with default values. * update
* preparing migration of json data to next major * flake8 * further changes * type fixed * new test for new migration * sample files updated * test improved * syntax fixe in sample
* individual imports better lookup by IDEs removed globals * flake8
* update super() calls to modern python * removed class ...(object)
* enable tests for GSOC branches * added a new testing action based on develop for gsoc * undo blank * var changed * name changed * removed unexpected value
…in mswms_settings.py (Open-MSS#1821)
* Make colorbar ticks format in generics plot configurable Fix Open-MSS#1828 * make vsec consistent with hsec * fix * fix
* introduction of group management * comment updated
…spatch (Open-MSS#2196) * Fix scheduled test to trigger testing-stable workflow using workflow_dispatch * updated workflow_dispatch devlop * requested changes regarding space
The removed QMessageBox mocks are unnecessary since there is a check in tests.fixtures that makes sure no open message boxes remain after each test and many of these mocks are actually detrimental since they mock all types of message boxes but only check for one.
This option is, to my knowledge, unused and it does not work anymore since the configuration is reset before each test.
…-MSS#2216) * enables to see from any operations user the creator * test and changes to allow for any operations member to get the creators name * improved
* extracted from index.py * refactored index.py, moved server dependent parts to theire modules * updated
Open-MSS#2214) * catch exception * improved * Update mslib/mscolab/server.py Co-authored-by: Matthias Riße <[email protected]> --------- Co-authored-by: Matthias Riße <[email protected]>
This configuration will check the GitHub Actions workflows for outdated versions of actions and will open update PRs for those every week on Monday (the current default for a weekly schedule).
* 15/02/2024 22:14 * 16/02/2024 14:34 * 16/02/2024 18:06 * 16/02/2024 18:06 * 16/02/2024 20:13 * 16/02/2024 20:13 * 16/02/2024 21:59 * 16/02/2024 22:53 * 20/02/2024 11:39 * 20/02/2024 14:01
Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5. - [Release notes](https://github.com/actions/setup-python/releases) - [Commits](actions/setup-python@v4...v5) --- updated-dependencies: - dependency-name: actions/setup-python dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
use always tz=datetime.timezone.utc
|
Kindly review the PR. @ReimarBauer |
Signed-off-by: Myrausman <[email protected]>
ReimarBauer
reviewed
Feb 23, 2024
| Install MSS | ||
| ~~~~~~~~~~~ | ||
|
|
||
| You must install mss into a new environment to ensure the most recent | ||
| versions for dependencies. :: | ||
|
|
||
| $ conda install -n base conda-libmamba-solver |
There was a problem hiding this comment.
Thanks .I think I am facing some issues with the forked repository .I will open a new pull request for this issue soon.
|
that's wrong, please only from a fork from stable into stable. We later merge from stable to develop. |
|
ok @ReimarBauer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of PR?:
update the "Manual" installation instruction on stable
Fixes #2200
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:
<type>: <subject>