-
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
#468: update master from develop v1.0.1 #466
Conversation
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.
+1
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.
It looks like someone has probably been merging PRs that do not pass all checks, because I see stuff on develop now causing the checks for this PR to fail. Choices like this could complicate all our processes down the road (this accidentally happened in the vt repo and has been a nightmare ever since).
This PR should not "fix" a closed issue. A new issue should be created.
Bumps [pygments](https://github.com/pygments/pygments) from 2.13.0 to 2.15.0. - [Release notes](https://github.com/pygments/pygments/releases) - [Changelog](https://github.com/pygments/pygments/blob/master/CHANGES) - [Commits](pygments/pygments@2.13.0...2.15.0) --- updated-dependencies: - dependency-name: pygments dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…465) * #464: optimized transfer swapping logic and improved instrumentation and stata * #464: fixed incorrect cherry-picking between branches * #464: restored inadvertently deleted constructor parameter * #464: fixed typo * #464: restored timers that got lost in cherry picking * #464: reintegrated missing code * #464: revert more changes --------- Co-authored-by: Caleb Schilly <cwschilly@gmail.com>
@nlslatt @ppebay @lifflander This should be ready to go now; the only remaining failure is because the branch name is not formatted correctly |
I was going to ask if we updated the version number in the |
I have created a VERSION file in PR #473 |
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.
THanks for additional change
* #446: Restored instrumentation that had been removed due to conflicts with 1.0.1 * #446: whitespace cleanup * #446: simplified subclustering and further improved instrumentation * #446: final improvement of the subclustering subsampling logic * #446: whitespace cleanup * #446: EOL cleanup * #446: fix variable name * #446: fixed incorrect random selection of target/criterion in non deterministic mode * #446: fixed debug hack use to prevent division by zero error when skipping swaps --------- Co-authored-by: Caleb Schilly <cwschilly@gmail.com>
@ppebay @nlslatt @lifflander We've now merged all relevant PRs to v1.0.1 -- once we merge this PR I can go ahead with the release |
I think only either @lifflander or @nlslatt can merge this PR |
* #469: introduce new visualization parameter and create script for updating configuration files * #469: use ruamel.yaml to read/write config files * #469: update all files in tests/unit/config * #469: update remaining files * #469: clean up and comment code * #469: remove extraneous code * #469: replace instances of LBAF_Viz throughout code * #469: fix string typo * #469: move script to proper directory; add error message for missing import * #469: remove requirement to install package
Fixes #468