Hacker News new | past | comments | ask | show | jobs | submit login

I tried asking a question about Porter and I see the error:

> Oops

> We couldn't access this repo.

> You may need to log in to view this repository, or it might not exist.




Hey looked into this error, Porter was not processed by us yet, it does take a while for a repo to be processed initially but this link should give you the progress report + you can chat with it when its done:

https://app.greptile.com/chat/github/porter-dev/porter


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=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=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


Hey, looking into this now. I believe the vote buttons actually do always send us feedback, but the UI could probably be better there.


Unless 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


These are all great points, we should probably audit the polling.


Ah sorry looking into it now




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: