qianli_cs

9 ms·

1. 91.▲
   4.5M Suspected Fake Stars in GitHub(arxiv.org)

   236 points by qianli_cs 2y ago|212 comments
2. 92.▲
   by qianli_cs 2y ago

   Chuck's light show is absolutely amazing! If you want to see more displays from him, check out: https://merryoncherry.org/
3. 93.▲
   A large-scale deployment of DCTCP(usenix.org)

   3 points by qianli_cs 2y ago|0 comments
4. 94.▲
   by qianli_cs 2y ago

   Good article. I think it can emphasize a bit more on supporting human interactions in agentic workflows. While composing workflows isn't new, involving human-in-the-loop introduces huge complexity, especially for long-running, async pr
5. 95.▲
   DSQL Vignette: Transactions and Durability(brooker.co.za)

   13 points by qianli_cs 2y ago|0 comments
6. 96.▲
   by qianli_cs 2y ago

   Thanks for sharing. This new feature is neat! It might sound a bit out there, but here's a thought: could you enable assigning unique IP addresses to different serverless instances? For certain use cases, like web scraping, it's h
7. 97.▲
   by qianli_cs 2y ago

   Looks so cool! Will this be extensible to supporting transactions across logical DBs/tenants?
8. 98.▲
   by qianli_cs 2y ago

   Happy to answer any questions here! I wrote a tutorial for the durable refund agent as well: https://docs.dbos.dev/python/examples/reliable-ai-agent
9. 99.▲
   by qianli_cs 2y ago

   I'm not sure if JavaScript supports it, but some Python libraries allow you to choose whether to install a more optimized binary version or the pure Python implementation. For example, if you install psycopg you'll get a pure Pyth
10. 100.▲
    by qianli_cs 2y ago

    Hello! Happy to answer any questions :)
11. 101.▲
    by qianli_cs 2y ago

    I used to be their big fan. I bought many 2set T-shirts and put their stickers on my violin case. But recently I found their video quality dropped so I stopped following… Anyways, their videos helped me through the dark times of the pandemi
12. 102.▲
    LLM-Informed Tooling for Detecting Retry Bugs [pdf](microsoft.com)

    1 points by qianli_cs 2y ago|0 comments
13. 103.▲
    by qianli_cs 2y ago

    Yeah, the sequel is a great read as well!
14. 104.▲
    by qianli_cs 2y ago

    Great summary! I also recommend the "What Goes Around Comes Around" paper written by Mike Stonebraker and Joe Hellerstein: https://people.cs.umass.edu/~yanlei/courses/CS691LL-f06/pape... It was writ
15. 105.▲
    Automatic async to sync code conversion (psycopg)(psycopg.org)

    1 points by qianli_cs 2y ago|0 comments
16. 106.▲
    by qianli_cs 2y ago

    What's your use case for system-versioned tables? You could use some extensions like Periods that support bi-temporal tables: https://wiki.postgresql.org/wiki/Temporal_Extensions Or you could use triggers to build
17. 107.▲
    A foundation model for clinician-centered drug repurposing(nature.com)

    1 points by qianli_cs 2y ago|0 comments
18. 108.▲
    Resource Management in Aurora Serverless(brooker.co.za)

    1 points by qianli_cs 2y ago|0 comments
19. 109.▲
    by qianli_cs 2y ago

    Interesting post but the format is broken on mobile devices. It cuts off sentences on the right.
20. 110.▲
    Fixing slow PostgreSQL queries: How to make a smart optimizer more stupid(bohanzhang.me)

    2 points by qianli_cs 2y ago|0 comments
21. 111.▲
    by qianli_cs 2y ago

    Hello! DBOS co-founder here. We actually use your app’s database (Postgres) as the state store.
22. 112.▲
    by qianli_cs 2y ago

    The issue with a long running server is that if your traffic is low, you’re paying for idle time all the time. So I’d prefer a serverless solution.
23. 113.▲
    by qianli_cs 2y ago

    If it doesn't need a database, then how does it manage inventory? For example, what happens if multiple people try to buy the same products but you don't have enough inventory?
24. 114.▲
    by qianli_cs 2y ago

    Thanks for your kind words! We're focusing on Postgres because an important scenario for durable execution is serverless computing, which won't work with an embedded database.
25. 115.▲
    by qianli_cs 2y ago

    Yeah! Under the hood, DBOS wraps each function (step) to log its output in the database. This ensures that workflows can be safely re-executed if they're interrupted, guaranteeing durability. More info here: https://docs.dbo
26. 116.▲
    by qianli_cs 2y ago

    Co-founder here! No current plans to support SQLite. We picked Postgres because of its huge ecosystem--you can use DBOS with any PostgreSQL-compatible database (Supabase, Neon, Aurora, Cockroach...) and with any Postgres extension (here&#x2
27. 117.▲
    by qianli_cs 2y ago

    Hello! I’m here to answer any questions. I’d love to hear your feedback, comments, and anything!
28. 118.▲
    by qianli_cs 2y ago

    "We suspect the impact is due to a database infrastructure related change that we are working on rolling back."
29. 119.▲
    by qianli_cs 3y ago

    Both the academic vision and the commercial product are built around the same core idea: store as much application and system state as possible (ultimately, much of the state of the OS) in the database. This idea enables many of our platfor
30. 120.▲
    by qianli_cs 3y ago

    Thanks for your interest in DBOS! We talk more about how things work on this docs page: https://docs.dbos.dev/explanations/how-workflows-work For functions doing database transactions, we record execution information i