Skip to content
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

Coinflip agent deployment #64

Merged
merged 13 commits into from
Apr 11, 2024
Merged

Coinflip agent deployment #64

merged 13 commits into from
Apr 11, 2024

Conversation

kongzii
Copy link
Contributor

@kongzii kongzii commented Apr 10, 2024

No description provided.

Copy link
Contributor

coderabbitai bot commented Apr 10, 2024

Walkthrough

This set of updates introduces a new Docker setup and updates tooling for deploying non-predicting agents in prediction markets. Changes include Docker and script configurations for efficient builds and deployments, updates to version control ignores, and an enhancement in the project's dependency management.

Changes

File(s) Change Summary
.dockerignore, Dockerfile Introduced Docker configurations for optimized image building and size.
.gitignore Updated to include .env, .agents_workspace, .cache and exclude requirements.txt, .venv.
build.sh Added a script for building and pushing Docker images to a registry.
pyproject.toml Updated dependency prediction-market-agent-tooling to version ^0.10.0.
.../coinflip_agent/coinflip_agent.py, deploy.py Added DeployableCoinFlipAgent class for deploying non-predicting agents in prediction markets.

Possibly related issues


Recent Review Details

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between 45973f2 and fc07332.
Files selected for processing (1)
  • prediction_market_agent/run_agent.py (1 hunks)
Files skipped from review as they are similar to previous changes (1)
  • prediction_market_agent/run_agent.py

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

build.sh Show resolved Hide resolved
@kongzii kongzii marked this pull request as draft April 10, 2024 13:25
@kongzii kongzii marked this pull request as ready for review April 11, 2024 09:21

COPY prediction_market_agent ./prediction_market_agent

ENV PYTHONPATH=/app
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a CMD/ENTRYPOINT here or is that done in the Kubernetes config? I guess if we're building this in CI then we want to test running it too?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question, command is easily changeable and I put it into Terraform https://github.com/gnosis/gnosisai-infrastructure/pull/3/files#diff-fa25fb4ef6fa67ec2382f07d26b9039099ce7a314a7e98517370a8439a0d0365R42

But if I put it here, it's easier to change it without the need for updating Terraform 🤔 I'll give it a try!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would also support @evangriffiths suggestion, the Entrypoint seems to me something that should be part of the image definition.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep works fine, updated 🙏

return random.sample(markets, 1)

def answer_binary_market(self, market: AgentMarket) -> bool | None:
return random.choice([True, False])
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make it a convention to have:

  1. prediction_market_agent/agents/<agent_name>/<agent_name>.py: core code
  2. prediction_market_agent/agents/<agent_name>/deploy.py: subclassing DeployableAgent

?

I guess that would mean just renaming this file delploy.py

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see known_outcome_agent already uses (2), so I changed it to that one. Didn't notice it before, sorry!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

@kongzii kongzii merged commit 0b1b213 into main Apr 11, 2024
6 checks passed
@kongzii kongzii deleted the peter/deployment branch April 11, 2024 12:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants