-
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
DB state catchup in version control #12
Draft
olsonadr
wants to merge
71
commits into
responsible-ai-collaborative:main
Choose a base branch
from
olsonadr:db-state-catchup
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
DB state catchup in version control #12
olsonadr
wants to merge
71
commits into
responsible-ai-collaborative:main
from
olsonadr:db-state-catchup
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
…bdas into 5-testing-suite
…bdas into 5-testing-suite
Co-authored-by: Nick Olson <olsonnick10@yahoo.com>
…bdas into 5-testing-suite
Co-authored-by: Nick Olson <olsonnick10@yahoo.com>
…bdas into 5-testing-suite
…ting in similar.py. Updated state.csv, and renamed old one for testing purposes.
…y, cleaned up testrun.py and formatted apitest.py
Co-authored-by: Nick Olson <olsonnick10@yahoo.com>
…purposes of testing with the updated state.
…er of incorrect inferences out of the total, and intervals outputs detailed info about guesses. If using, remember to point the data and state docs to the right files.
5 testing suite
test_accuracy.py and test_intervals.py were being caught by pytest
…olsonadr/nlp-lambdas into 4-reduce-size-of-incident_clspt
Added MONGODB_CONNECTION_STRING to the workflow environment for db_state
4 reduce size of incident clspt
Where it was in a subdir of the inference dir, it was being picked up as a lambda specification
Moved state_update.py to project root, updated README
…ine model max length, and thus truncate abnormally long tensors of tokens, solving an indexing error encountered while updating incident 195. Removed manual truncation in similar.py. Refactored the names of a couple constants in similar.py.
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.
This is a WIP PR that should include finalized changes from #11 .
The only difference between #11 and this should be that state_update.py has been run and that change has been committed into version control so less DB state checking needs to occur each time.
It's worth talking about potentially having this committing happen on a regular basis in a workflow, although I'd guess that long-long-term, this maintenance of embedding state would be held in the DB as opposed to this generated file