-
Notifications
You must be signed in to change notification settings - Fork 0
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
October 2024 release #339
October 2024 release #339
Conversation
Does a few things @korikuzma noticed that the README description of copying build files had an incorrect path. However, this instruction is actually unnecessary (and impractical tbh). In development you'd be better off letting yarn start handle service of client files because it has hot-reloading on changes. I removed it. Rather than requiring client files to be present, catches + logs their absence if they're not there. This is better for development. Originally I added this code in the big VRS update PR but it should've been a separate issue. I would like to see us reexamine our logging initialization/setup in another issue, because it could be bad if it's not working properly. Adds some additional description of why the client service code is there + what it needs.
* build!: updating to vrs 2.0 models * update pydantic-to-ts2 and update models * wip: updating models, making variable casing consistent, converting descriptors * fix: utilities requests * fix: response model casing * wip: updating models * bug fixes * updating models and fixing validation * pass around formatted fusion to reduce repeated code * fixing demo data * specifying fusion type since null param gets dropped and fusor can't infer the type * fixing tests and updating data with new models, bug fixes * bug fixes for input elements * pin latest fusor * update dependencies * fix clientification of demos * fix formatting in docstrings * fix type handling of failed lookup * fix up gene lookup api * fix tx utils bug * fix bug where region and strand were incorrect in templated sequence, fix regulatory element missing field, pin pydantic version * removing console logs * fix: bug where error messages no longer displayed on summary page * fixing tests and adjusting variable casing * add reusable function for checking valid sequence locations * add reusable function for checking valid sequence locations * fixing nomenclature bugs * fixing nomenclature bugs * DOn't bother w/ semver checks (out of control of this app) and use proper fixture mode * add assertion notes * stash changes * stash * fix a few fixtures * sequence util fixes * minor rearrange * fix int/str problem * commit this * catch static files error * validation tests * fix reg element URL * remove todos * review comments --------- Co-authored-by: James Stevenson <[email protected]>
…nt (#276) Bumps [webpack-dev-middleware](https://github.com/webpack/webpack-dev-middleware) from 5.3.3 to 5.3.4. - [Release notes](https://github.com/webpack/webpack-dev-middleware/releases) - [Changelog](https://github.com/webpack/webpack-dev-middleware/blob/v5.3.4/CHANGELOG.md) - [Commits](webpack/webpack-dev-middleware@v5.3.3...v5.3.4) --- updated-dependencies: - dependency-name: webpack-dev-middleware dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
requirements.txt
Outdated
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.
I think we want to use the versions from staging
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.
agreed, ugh this is so weird. I regenerated this file with the command, so I'm not sure why the versions are different from staging
fixing merge conflicts from main to staging