-
Notifications
You must be signed in to change notification settings - Fork 9
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
Working version for validate
command CLI
#152
Conversation
…review comments
…ucture. Eventually fixes issue i-am-bee#132
What poetry issues do you have? @maximilien
|
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.
See comments above.
You WILL have poetry issues if using v1, make sure you have v2 installed (it is on homebrew) To add additional dependencies:
Hopefully this will allow you to get code working. When merged I can open a subsequent PR to refactor & create a new module definition (in essence this would just add another directory alongside bee_hive, perhaps called bee_cli, perhaps bee_tools - but to have it 'under' where the pyproject.toml is) |
OK. Will be trying this today,. Thanks for the tips Nigel. Heading to the office and I have a different machine so will try a clean setup there and see how far I get. |
…ow run CLI with: poetry run ./beeAI -h You can run the validate command with: poetry run ./beeAI validate ../tools/workflow_schema.json ../test/schema/simple_workflow.yml
validate
command CLIvalidate
command CLI
@planetf1 this works now. Please check and give a review. Only thing missing are some tests but you can try the poetry run ./beeAI validate ../tools/workflow_schema.json ../test/schema/simple_workflow.yml Assuming you are in the Thanks for your suggestions and reviews. |
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.
Needs a rebase
Also, I got a number of syntax warnings for invalid escape sequence
:
/.../python3.12/site-packages/docopt.py:165: SyntaxWarning: invalid escape sequence '\S'
name = re.findall('(<\S*?>)', source)[0]
/.../python3.12/site-packages/docopt.py:166: SyntaxWarning: invalid escape sequence '\['
value = re.findall('\[default: (.*)\]', source, flags=re.I)
/.../python3.12/site-packages/docopt.py:207: SyntaxWarning: invalid escape sequence '\['
matched = re.findall('\[default: (.*)\]', description, flags=re.I)
/.../python3.12/site-packages/docopt.py:456: SyntaxWarning: invalid escape sequence '\S'
@maximilien same comments as Paul - rebase + also get invalid escape sequences. |
/.../python3.12/site-packages/docopt.py:165: SyntaxWarning: invalid escape sequence '\S'
name = re.findall('(<\S*?>)', source)[0]
... I saw as well. I think this are issues with the |
@@ -105,7 +105,7 @@ ipython_config.py | |||
# This is especially recommended for binary packages to ensure reproducibility, and is more | |||
# commonly ignored for libraries. | |||
# https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control | |||
#poetry.lock |
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.
this shouldn't make any difference (as per https://git-scm.com/docs/gitignore). A filename will apply at any level below. The file also appears lower down (which may be a dup)
bee-hive/pyproject.toml
Outdated
@@ -11,6 +11,8 @@ python = ">= 3.11, < 3.13" | |||
pyyaml = "^6.0.2" | |||
openai = "^1.56.2" | |||
python-dotenv = "^1.0.1" | |||
docopt = "^0.6.2" |
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.
See #160 - optional to do here in in a new PR (fix is to use docopt-ng)
bee-hive/poetry.lock
Outdated
@@ -0,0 +1,780 @@ | |||
# This file is automatically @generated by Poetry 2.0.1 and should not be changed by hand. |
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 recommend removing this file from the PR. This needs to be explicit since it already forms part of the PR. Including means running poetry lock
often & impacting CI tests (including it helps with reproducible builds, but I don't feel that's needed at this point)
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.
this will fix the test failure - other comments can be handled in additional issues/prs as needed
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.
git rm bee-hive/bee-hive/poetry.lock
but otherwise LGTM
Check now. |
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.
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.
Works fine for me now. thanks!
@psschwei I don't see there's any further removal needed now |
@@ -0,0 +1 @@ | |||
3.12.8 |
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.
is this needed
(optional to tidy up - or can be later PR)
Comes from pyenv?
Ok let's merge. I was referring to: bee-hive/.python-version |
Ah right, in that case, yes in another pr will need to remove, as well as add to .gitignore (can be just .python-version) |
This PR when complete will fix issue #132
validate
commandQuick test is:
TODO
validate
commandCC: @psschwei and @akihikokuroda if you can take a look. I'll keep looking at how to resolve poetry