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

Umbrella Phase 1 Requirements #31

Closed
16 of 19 tasks
elijahbenizzy opened this issue Feb 23, 2024 · 2 comments
Closed
16 of 19 tasks

Umbrella Phase 1 Requirements #31

elijahbenizzy opened this issue Feb 23, 2024 · 2 comments
Labels
release umbrella Group of issues together

Comments

@elijahbenizzy
Copy link
Contributor

elijahbenizzy commented Feb 23, 2024

For V1 release. Goal is March 1. In addition to: #29, we have:

  • Example apps with tracking server
    • Chatbot
  • Add more complex example (simple chatbot) in getting started in docs
  • Get video intro for those who want to watch
  • Roadmap in README
  • (stretch) Static server hosted online
  • Streamed output Streamed output #19
  • (stretch, with feedback) -- handling exceptions (Add exception transitions #30)
  • State persistence in a clean way
  • (directly post-release) Logging metadata -- Add metadata capture #46
  • Telemetry/tracking on posthog (with opt-out, same as hamilton)(Telemetry for Burr #58)
  • Figure out what slack to link to
  • Add comparison matrix in README Update README + fixes startup #76
    • Langgraph
    • Temporal
    • langchain
    • hamilton
    • superagent.sh (burr is not agent specific, host/run wherever python runs)
  • Change README gif to be of actual chatbot API
@skrawcz
Copy link
Contributor

skrawcz commented Feb 23, 2024

Need to add telemetry.

elijahbenizzy added a commit that referenced this issue Feb 25, 2024
We weren't respecting it before. This handles that. This just measures
the delete operations and reapplies it. That said, this is not the best
way of doing things -- see #33 for a more involved approach.
elijahbenizzy added a commit that referenced this issue Feb 25, 2024
We weren't respecting it before. This handles that. This just measures
the delete operations and reapplies it. That said, this is not the best
way of doing things -- see #33 for a more involved approach.

Note we've also relaxed the restrictions on modifications for
delete/write -- this is necessary for the current workaround.
elijahbenizzy added a commit that referenced this issue Feb 25, 2024
We weren't respecting it before. This handles that. This just measures
the delete operations and reapplies it. That said, this is not the best
way of doing things -- see #33 for a more involved approach.

Note we've also relaxed the restrictions on modifications for
delete/write -- this is necessary for the current workaround.
elijahbenizzy added a commit that referenced this issue Feb 26, 2024
We weren't respecting it before. This handles that. This just measures
the delete operations and reapplies it. That said, this is not the best
way of doing things -- see #33 for a more involved approach.

Note we've also relaxed the restrictions on modifications for
delete/write -- this is necessary for the current workaround.
elijahbenizzy added a commit that referenced this issue Feb 26, 2024
We weren't respecting it before. This handles that. This just measures
the delete operations and reapplies it. That said, this is not the best
way of doing things -- see #33 for a more involved approach.

Note we've also relaxed the restrictions on modifications for
delete/write -- this is necessary for the current workaround.
@elijahbenizzy elijahbenizzy changed the title Umbrella V1 Requirements Umbrella Phase 1 Requirements Mar 29, 2024
@elijahbenizzy elijahbenizzy added the umbrella Group of issues together label Mar 29, 2024
@elijahbenizzy
Copy link
Contributor Author

This is complete

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release umbrella Group of issues together
Projects
None yet
Development

No branches or pull requests

2 participants