Audio raw (2).webm/2024-11-26
Speaker A: Hey, Ahmed. Hey, Isa.
Speaker B: Hello.
Speaker C: Hey, council. Hey.
Speaker A: Let's see. I was just wrapping up something with one delay, so let's see if he joins. But we should just get started. Hopefully the week is going well for everybody. Let's see. Sebastian, do you want to go first?
Speaker D: Yeah, sure. So since the last meeting I was working mostly on Google Google Calendar integration. So it's already covered, I think. But I would need to verify that with the read credentials to see if everything is working correctly because right now I'm basing on the mocks quite hard to catch any bugs there. So. Yeah, so you would need to wait for credentials. Also some small book bug fixes that I did in the last week. So. Yeah, right. To the, to the email feeds and a few other things. And yesterday I fixed the issue with the, with the email feed category that wasn't returning the items and also spent some time to verify draft streaming and mostly that's it.
Speaker A: Okay, good progress on all of those for Google Calendar integration. Are the endpoints ready for AMAND or not yet?
Speaker D: It's not pushed to the development environment. I can try to push it with some mocked data and. Yeah, and it can try to start with the mocked data.
Speaker A: Yeah, that would probably be handy. So like you can just like start doing it and then we'll get like actual data in once we get the credentials and the scope approved. Okay, then what was the issue with the email feed? Why was that erroring out?
Speaker D: Like, I made some changes when I was refactoring the feed like in the, in the previous week during like. Yeah, because of this, because of this database issues. And I changed database schema a bit and like our query had a problem to fetch the email that had some field set as a null and I just needed to change one thing in the database.
Speaker A: Okay, okay, so that sounds good. And is the issue with draft streaming? Is that fixed as well or not yet?
Speaker D: I sent a message like a comment in the task of streaming because from the back end perspective seems to work correctly. And yeah, I'm not sure how to, how to verify that. They asked Amit if that's the front end issue, but yeah, Amit, Amit said that it's being returned by the backend in one chunk. But as you can see on this, on the recording of the, in the, in the attachment, it's not returned by the bucket in one chunk. So I'm not sure what's the issue there. Yeah, and it's quite hard to guess what's. What's going on there because Amit did you try to, to run the comment that I sent to you like the curl in the.
Speaker C: No, this was the regular streaming code that has not been changed in a very long time. So it has been untouched for a really long time. And if you open the console, the whatever gets streamed is also logged to console so you can debug it what is being received by the front end as is. And that was how a lot of previous issues were debugged by esa. And even in that it is coming like one big chunk after you can see the this network. Also like it isn't coming from bit by bit. It's the entire thing is, you know, it's coming up in one big chunk.
Speaker D: Yeah but if you, if you run the comment that I've sent you, you will notice that it's not sent in there like it's not returned in one chunk. And Kenzo, you can open up the, the recording in the, in the attachment and it's being returned correctly. So Above. Above. No, no, no, no. There's a video in the attachments. Not sure if you can open it.
Speaker A: But no, no, it opens in my like video player so we can't easily share that.
Speaker D: Yeah, but yeah.
Speaker A: Oh I see it in the video where it screens and yeah and it.
Speaker D: Looks like bucket is returning it correctly and same case here. Like it wasn't changed in the very long time. So.
Speaker A: Yeah.
Speaker D: Yes. I'm not sure what's the issue here?
Speaker A: Is it. Well, I don't know, like it wouldn't be like OpenAI thing right? Like where they change the streaming.
Speaker D: No, no, no. Yeah, like yeah, because as you can see on the video it works fine.
Speaker A: Yeah.
Speaker D: The issue is between connection of the, of the front end and backend for sure.
Speaker A: So Aman, did you try this like the curl here?
Speaker C: Not this query exactly. No.
Speaker A: Okay, let's try this and see if this like actually works on your end because then we can figure out like where this is going wrong.
Speaker C: Okay.
Speaker D: Yeah. Also I thought that this might be an issue with the, with the zones like from like request from us goes back to Poland in like 1 second or something like that. But I think like time for India is pretty much the same so it should work correctly also. Yeah.
Speaker A: Okay, let's try that curl, see if that works on your end and then let's try to debug this and see if we, if we can figure out what's going on because it's a bit weird right? The code hasn't changed. I spotted it last week probably after the latest web release. That we did or maybe prod release. So like somewhere in between the two, like something happened. So I'm not sure what. Okay, Amit.
Speaker C: I mostly worked on the UI of the calendar and it's mostly done. I could probably give you a demo.
Speaker A: Oh yeah, sure.
Speaker C: Is it visible?
Speaker A: I think it's coming. I think it's coming up now. Yes.
Speaker C: Okay. Okay, so this is the main layout. This design has been updated and for Agenda, the main thing here is the minimizing. And it works like this. And once you get below a certain resolution, it's 1200 right now. So what happens is this is floating right now and when you do this it floats over that. And the new meeting has also been updated and Control F will make this come up and then. Okay, so this is how a calendar event would actually look like. The agenda would all be there, but I'll wire it all up when B is finally ready so I can deal with the actual data. So this is the actual individual event and this is all hard coded. So this is the expanded details if you may. And from here you create the topic. And in this event there's three states. This is the normal one and this is how it looks for a previous meeting. If the meeting is already done, it was in the past, then it looks like this. And if the meeting is upcoming, it looks like this. This would be fixed when I. This truncating will be fixed when I put it in the absolute container this for demo. But yeah, and yeah, this is done. So I just need the data and we can wire it all up. And one more thing is the notifications. I'll also do that once I get the data. So it would basically display a small box here at the time of meeting. So that's the other thing. So basically the meeting UI is done and there were a couple of bugs I investigated and fixed that is 1141 is one and.
Speaker A: Right. Let me just pull up my screen.
Speaker C: Okay, so 111-14-1141 and 1139 and I also debug the another thing. Let me see. Yeah, 1142. 1142 is BE. Basically it is returning a completely different feed ID when the create API is called, but when it is being listed it is returning another id. If you open the screenshots in my comment, not in my comment. Okay, so this is the. Sorry, you. Can you open the next.
Speaker A: Yeah.
Speaker C: Okay, so this is the response from ve when a field is created, not the ID of this. It ends with F50 and okay, you can open the next image and this Is the subsequent list all field API. And in this, the same tech crunch, startup and technology use the same thing, but the ID is completely different. So this is why in memory, the first one is also there. And after the field gets updated, there are two versions of the same thing. So that is why there is. There are duplicates. But when you refresh it, the in memory, that is the first one, sorry, the 2416 goes away because that was, you know, in memory and that was wrongly being written by me. And it goes away and works well from then on. So this is the bug.
Speaker A: Sebastian, could this be related to the like feed optimization that you did last week?
Speaker D: Yeah, and I already have a fix for that, but it's not yet pushed to the environment. But I will do that like in an hour after the meeting.
Speaker A: Okay, sounds good. So let me just assign this to you, and then once it's in the Issa can validate and then hopefully this will be fixed. Okay. Amit, anything else?
Speaker C: No, that's it.
Speaker A: Okay. How much work do you have left for Calendar?
Speaker C: Completely depends on backend right now.
Speaker A: Okay. Okay, so that sounds good. Isa.
Speaker B: I have done a check on production and reported a few issues that were discussed. Now most are fixed and two remaining ones were also discussed. Streaming of draft content and feeds being displayed twice validated. Some mobile tasks, including recording when the app is in the background and left feedback on some other validated debug button on custom templates and the switch of the audio transcription service.
Speaker A: Okay. Okay. Yep, good progress there. I think this one is also live. What else did we have here? Oh, did you debug these issues, Isaac?
Speaker B: These are the issues that I couldn't reproduce.
Speaker A: Okay, so all of these I should just move to validated or like, at least. Yeah. Okay, I'll go through this and then do that. Okay. Okay. Wand.
Speaker D: Last week I worked on. I worked on finishing that and then a few updates on the website and then I started Bash Desktop Helper app. I am currently waiting for feedback on some of the concerts and screens that I have, and then I'll be iterating that and this week.
Speaker A: Yeah, okay. Yeah, good progress there. I was going through the. Through the different concepts right before this meeting. Probably makes sense to quickly discuss them because I think there's at least one step missing based on the implementation. That one that Ahmed and I discussed prior to you and I talking on today. So, Amit, the way we were going to implement this was electron based on the web code base. Right. But then we needed to have a separate binary to record System audio. Like that's. That is the tldr, right?
Speaker C: Yes. The Electron would be multiplatform single code base and it would. It will. It would be built from scratch because it does not. It's a whole new thing. Right. It's not going to be. Yeah. So it will be built from scratch because the features are very less and so.
Speaker A: Yeah.
Speaker C: And the actual recording itself will be very minimal and there should not be any UI there. All the UI should concern itself with the Electron only.
Speaker A: Yeah. And the Electron based app or the Electron app would still feel platform native. Right. So we would be able to do things like system like status bar icon, similar to how we have it for Rock. And like it would just feel like a native app.
Speaker C: Yeah, yeah. Rock itself is Electron. Right.
Speaker A: So exactly. Okay. So yeah, so one delay, like there needs to be a step somewhere, I think from an install flow. Ahmed. Like, and I'm just simplifying this for Mac, we would have assigned Binary. Assigned dmg. You download it directly from the website or the app Store as part of the install. There needs to be a separate action to install that System Audio Recorder. Right.
Speaker C: Yeah. I was thinking like the user would just download the Electron app and from the Electron app there could be a page within that where we also link the next. The Mac binary, if that is a good option. Otherwise I'm not sure if you have another thing in mind where installing one would automatically install the other if that is what you have.
Speaker A: Yeah, that's ideal. Right. Like it should just be one action as opposed to, oh, you download one app to download another app. Right. So like if we can do it in a way where it's just like one flow where you say install and it installs Electrum app and the System Audio Recorder, I think. And it does it transparent. Like. Yeah, I don't know. We need to figure out like how that flow actually works and if there's an additional confirmation that you need to give for that System Audio Recorder.
Speaker C: Yeah, I think the DMG usually works by you click on it and there's a file inside it and you have to manually drag that into the applications folder. Right. So what might work is we might have those two apps right there and those two can then be dragged by the user themselves into the application. But I don't know the specifics of this. That's something we have to explore. But the Binary app will have its own permission sets and it will ask it when it is being opened.
Speaker A: Yep.
Speaker C: And yeah.
Speaker A: Okay. So yeah, so we need to do some research on that first. Okay, so we should pencil in something here. One delay in terms of install flow, because I think that's going to be a bit non standard. Then let's see. One delay. Conceptually, I think it makes sense. Yeah. I think you were looking for some guidance on flows and implementation. Yeah. I haven't seen anything here that stands out as something that wouldn't be doable with Electron. But Ahmed, we can quickly go through this and see if you spot anything that you don't think will be doable.
Speaker C: This is an app, right? Like it's an actual app. It looks like something out of a native Mac app right now. Doesn't look like Electron desktop app.
Speaker A: Yeah. So are there any specific UI elements that we can use for Electron or how does that. What should we use?
Speaker C: Electron is basically. It's just web. Right. It's what is being designed for web. It will look like just a browser. Just remove the top search bar and brand it with the rock and you have the electron. Sorry, not rock. And that's basically what an Electron app is. So. But the designs here feel more like it is something that Apple themselves designed and put it in macOS.
Speaker A: Yeah. Okay. So, yeah, so direction wise, I think that probably means we need to make some revisions here. But then the size of that app window. Amit. Right, like, I assume we can make that like any size that we want. Right?
Speaker C: Like we can, but we should probably stick to a minimum width and height and so it would stay responsive from that size and above.
Speaker A: Yeah. Okay. Okay. So that means we have a bunch of limitations in terms of ui. When? Today. Okay, let's think about that. Let me go through the flows and the wireframes and then we can revise things based on. Based on that. Okay. Okay, let's see. Anything else? Is there any major bugs that like we should focus on?
Speaker B: No, I think this draft streaming is the only thing.
Speaker A: Okay, so that sounds good. Yeah. So draft streaming. Okay. Okay, then I think that's. I think that's mostly it. I think it's Sebastian, if you can get the calendar endpoints into dev, so Ahmed can pick those up and plug those into front end to start running on mock data, I think that would be helpful. Then fixing that bug with multiple feeds showing up, I think would be good. And then Amit, if you can look into that streaming bug, see if that curl actually works on your end and see if we can improve that, I think that would also be helpful. Then let's see. Okay. Yeah, I'll check out Perplexity. Okay. Yeah, I was actually playing around with it earlier today. Yeah. Yep. So I think let's get those things. So those two things Sebastian in dev. So Ahmed can pick those up and then let's see if we can fix that streaming bug and then hopefully we can get calendar working and like validated by end of this week so we can do a production release, let's say Thursday, Friday. Ish, if that makes sense. Does that sound good, Ahmed? Sebastian Isa.
Speaker D: Yes.
Speaker C: Yeah, I'll look into that bug and try to get it working by tomorrow.
Speaker A: Okay.
Speaker D: Yeah.
Speaker A: Yes, sounds good. Amit, do you use Perplexity for anything?
Speaker C: No, I. When the hype was an alterming, I just checked it out, but I don't really specific.
Speaker A: Yeah, Perplexity is an interesting product. I think it's very complementary to what we're doing and I think the way they present search results and also how they build product is super interesting. Okay, I think that's a plan for the next couple of days and then we'll check in over rock and see where we are by Thursday. But ideally we get Calendar Life at least this week so we can. So we can get going on on that. Anga was sick last weekend, so I think he started picking up things again this week. And hopefully you'll be able to get started on. On meetings for, for the mobile app soon and then catch up on that and then hopefully by that time also like start working on calendar. Okay, I think that's it. Did anyone have anything else?
Speaker C: I was. I just wanted to ask Sebastian if the calendar was implemented in a way that multiple calendars are currently available or is it just one.
Speaker D: Multiple? You can list all the calendars that are connected to the account and then fetch all the events from single Calendar.
Speaker C: Also, would there be a API for getting all the events of all the calendars or would we get it from the individual calendar API aps?
Speaker D: Like I can add an endpoint that fetches all events. Currently there is. There's only endpoint to fetch events for single calendar. But yeah, that's. That's a quick change.
Speaker C: Okay, sure.
Speaker A: Okay. Okay, thanks everybody. Have a good evening and good night and we'll. We'll connect later.
Speaker D: Thank you. Bye.
Speaker A: Okay, bye.
Project Development Meeting Minutes
Attendees
Kenzo
Iza
Amit
Sebastian
Wandile
Agenda Items
Integration and Testing of Google Calendar
Email Feed Error Troubleshooting
Draft Streaming Issue Investigation
UI Progress for the Calendar Feature
Backend and Frontend Development Coordination
Addressing Bug Reports and Fixes
Summary
The meeting focused on ongoing development tasks and issues. Sebastian discussed work on Google Calendar integration and email feed bug fixing. The team explored ongoing issues with draft streaming. Amit showcased progress on the calendar UI for the project. Coordination between backend and frontend development was emphasized for smoother workflow. The attendees also addressed specific bugs and the steps required to fix them.
Outline
Google Calendar Integration
Sebastian noted progress on Google Calendar integration.
Credentials are needed to verify the work with real data.
The endpoints are ready for mock data testing.
Email Feed Bug Troubleshooting
Draft Content Streaming Issue
Investigated the issue concerning backend data streaming.
Disagreement on data chunk size between frontend and backend.
An external test using curl was suggested to verify the data flow.
Calendar UI Progress
Amit completed the primary UI for the calendar.
The design adapts to different resolutions and reflects meeting statuses.
AWAITING data connection for full functionality.
Bug Reports and Resolutions
Install Flow for Desktop App:
Discussion on installation complexities for a new desktop app.
Electron app with a separate binary for the system audio noted.
Research needed for seamless integration during installation.
Action Items
Push Google Calendar endpoints to development for mock data testing - Sebastian (by end of day)
Fix duplicate feed ID bug - Sebastian (within the next hour)
Investigate and resolve streaming issue via verified backend check - Amit (by tomorrow)
Coordinate on desktop app installation flow - Amit and Wand (ongoing)
Plan a production release for the Calendar by end of the week - Amit and Sebastian (Friday)