Feat/ofv merged #247
Merged
Feat/ofv merged #247
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
…olver # Conflicts: # packages/gnosis/customs/ofv_market_resolver/ofv_market_resolver.py # packages/gnosis/customs/omen_tools/component.yaml # packages/jhehemann/customs/prediction_sum_url_content/component.yaml # packages/napthaai/customs/prediction_request_rag/component.yaml # packages/napthaai/customs/prediction_request_rag_cohere/component.yaml # packages/napthaai/customs/prediction_request_reasoning/component.yaml # packages/napthaai/customs/prediction_url_cot/component.yaml # packages/napthaai/customs/resolve_market_reasoning/component.yaml # packages/nickcom007/customs/prediction_request_sme/component.yaml # packages/nickcom007/customs/prediction_request_sme_lite/component.yaml # packages/nickcom007/customs/sme_generation_request/component.yaml # packages/packages.json # packages/polywrap/customs/prediction_with_research_report/component.yaml # packages/psouranis/customs/optimization_by_prompting/component.yaml # packages/valory/agents/mech/aea-config.yaml # packages/valory/customs/native_transfer_request/component.yaml # packages/valory/customs/openai_request/component.yaml # packages/valory/customs/prediction_langchain/component.yaml # packages/valory/customs/prediction_request/component.yaml # packages/valory/customs/prediction_request_embedding/component.yaml # packages/valory/customs/prepare_tx/component.yaml # packages/valory/customs/resolve_market/component.yaml # packages/valory/customs/stability_ai_request/component.yaml # packages/valory/services/mech/service.yaml # packages/valory/skills/task_execution/skill.yaml # poetry.lock # pyproject.toml # tests/test_tools.py
|
@kongzii @victorpolisetty Can you take a look a this PR? |
|
lgtm! I ran it with my own openai and serper api key and it worked well. 
|
victorpolisetty
approved these changes
Aug 8, 2024
victorpolisetty
approved these changes
Aug 8, 2024
packages/gnosis/customs/ofv_market_resolver/ofv_market_resolver.py
Outdated
Show resolved
Hide resolved
|
Looks good; dependency changes were already merged in separate PR, so that's fine. And if you are going to merge this PR as it is now, then #244 can be closed, as this PR contains these changes. |
kongzii
reviewed
Aug 8, 2024
dvilelaf
approved these changes
Aug 8, 2024
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.
Proposed changes
This PR adds the OFV Market Resolver tool introduced in #225.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an
xin the box that appliesChecklist
Put an
xin the boxes that apply.mainbranch (left side). Also you should start your branch off ourmain.