Ecosyste.ms: Timeline
Browse the timeline of events for every public repo on GitHub. Data updated hourly from GH Archive.
cpsievert created a review comment on a pull request on posit-dev/py-shiny
No, I don't think we want to support that since, if there are multiple user sessions, they would be mutating the same object
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- More aggressively update scrollable element. Add test for obtaining streaming result 6b1e24d
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Have the stream task return the accumulated string result 5089b99
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Allow for auto-scrolling to be disabled 9d459ce
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Refactor MarkdownStream logic 7c0a536
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Committed file by mistake 570335c
cpsievert created a comment on an issue on posit-dev/chatlas
That's a good point that we should make a point to use `stream_async()` in Shiny apps. That said, from just a little bit of testing with a just small number of concurrent "users", even `.stream(...
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Update playwright test 7c82077
cpsievert created a comment on a pull request on posit-dev/py-shiny
Ughh, I also forgot that, in order to have a non-blocking stream, the websocket messages need to be asyncronous. This is precisely why `chat.append_message_stream()` is async. I could maybe be t...
cpsievert created a review comment on a pull request on posit-dev/py-shiny
[3b4a5a4](https://github.com/posit-dev/py-shiny/pull/1782/commits/3b4a5a4f7e70ffcd028a5f8229779496bc66ff2b) does this renaming
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Make stream() async so is non-blocking cf36d18
cpsievert created a comment on an issue on posit-dev/chatlas
I'm pretty sure this is just an oversight that should get fixed. In case it helps, in the meantime, you can also change this line: ```python response = await chat_session.stream_async(user_input,...
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Add height/width params; rename to markdown_stream_ui() 3b4a5a4
cpsievert pushed 1 commit to markdown-stream-component posit-dev/py-shiny
- Add height/width params; rename to markdown_stream_ui() 7d8217d
cpsievert created a review comment on a pull request on posit-dev/py-shiny
Is this getting used anywhere?
cpsievert created a review comment on a pull request on posit-dev/py-shiny
And to help clarify, I'm not saying I want it removed right now, but if we commit to it here, let's commit to it wherever it makes sense?
cpsievert created a review comment on a pull request on posit-dev/py-shiny
This does seem nice, but also one of those things that would ideally be done across the entire codebase in one dedicated PR
cpsievert created a review comment on a pull request on posit-dev/py-shiny
Why do these have `T` at the end? It makes me think its a `Generic`
cpsievert created a review comment on a pull request on posit-dev/py-shiny
FWIW, I feel a bit torn on whether this should be `output_markdown_stream()` or `markdown_stream_ui()`