3 ms·
I followed the link because I was curious and it still said processing, so I navigated to the homepage and clicked "Try a popular repo" leading to <https://app.
by mdaniel 3y ago
I followed the link because I was curious and it still said processing, so I navigated to the homepage and clicked "Try a popular repo" leading to <https://app.greptile.com/chat/3t4qpefuh9eqckcdt0b8i?repo=postgres%2Fpostgres https://app.greptile.com/chat/3t4qpefuh9eqckcdt0b8i?repo=pos...> which then said "We couldn't access this repo." It seems the actual syntax is app.greptile.com/chat/github/postgres/postgres -> https://app.greptile.com/chat/lfbc034nkj7w03v2kb5zp?repo=github%3A%3Apostgres%2Fpostgres https://app.greptile.com/chat/lfbc034nkj7w03v2kb5zp?repo=git... so wherever that list of "popular repos" is coming from needs to be updated to avoid other people having bad first experiences
It also appears that the vote buttons do nothing if one is not logged in, so I'd recommend eliding them unless logged in since it's just frustrating to wonder if some JS error ate the vote or what
- vaishant 3y agoHey, looking into this now. I believe the vote buttons actually do always send us feedback, but the UI could probably be better there.
- mdaniel 3y agoUnless you are batching them up and hiding them in the upteen bazillion posthog POST requests, no, they do not I shudder to think how much you must be spending on compute asking for that /api/poll/batch once a second, each one saying it is a Miss from cloudfront. It's especially mysterious since there's nothing on the UI that the user would see about the .filesProcessed increasing that justifies DDoSing yourself like that, IMHO
- dakshgupta 3y agoThese are all great points, we should probably audit the polling.