This is once again a huge commit, but its mostly performance improvements along with some bug fixes and refactoring. It also includes changes to the theming systems. I'm still not 100% happy with the theming system, but its better than before. Model fetching has been dramatically improved! Nearly all the important computation and pre-processing has been moved to the server. This has also somehow fixed the way model details are loaded, which was causing many models to be missing their details despite models.dev having them. The markdown renderer has once again been changed, but I'm mostly certain that this is the last time major changes will be made to it. The renderer is not spamming components, bloating memory usage, and its not using a bug prone custom written chunking system. There's also a lot more that I haven't mentioned and honestly forgot. I need to get better commit hygiene tbh.
1.5 KiB
Known Bugs
-
Occasionally, once in maybe 10 runs, triplit will make TWO connections to the backend. I'm not entire sure why, I think its a race condition, but I'm not sure. I do not think that triplit-nuxt is the culprit, but I'm not sure.
-
The logic to handle hovering over the sidebar is half-baked at best. On the agents route, the back arrow sometimes stays full sized
-
If you open the theme switcher on the sidenav then close it and re-open it without moving your mouse off of the sidenav, the agent button/dropdown trigger will slowly crawl to the right (likely related to #2).
-
When navigating to different topics, or making a new topic, the page sort of freezes but its not completely frozen? I think this was because of page transitions
-
If you navigate from "/" to an agent, then navigate to topics, none of the topic data is loaded. This was a bug in the triplit-nuxt plugin.
-
Stop button showing when no generation
-
Sidenavs keep the overflow even if the lists are collapsed
-
Sometimes the sidebar wont change views until you move your mouse off of the sidenav?
-
Sometimes on first page load, the message send button is on the left?If input was typed into the chat input before hydation the message send button will be on the left. THIS WAS BECAUSE OF GRAMMARLY. I HATE YOU GRAMMARLY. -
Multiple markdown blocks might be edited with the same content at the same time