Billy Keyes

Sorry that you're having reliability issues with Bulldozer. We're also running Bulldozer 1.13.2 with GitHub Enterprise 3.1.1 and are not seeing the behavior you describe, so I don't think this...

If you are encountering rate limits, you should see messages like this in the logs: ``` { "level": "error", "rid": "c35j7irt535deut1lk60", "github_event_type": "status", "github_delivery_id": "4a768d8a-cf60-11eb-98bd-2f28b1d0cb41", "error": "failed to determine open...

After reviewing the logs, it might be that this is an issue with GitHub or with Bulldozer's caching. I've seen problems before where events that normally appear synchronous are actually...

> Will Bulldozer logs filtered to the given PR do, or shall we send over full Bulldozer logs? Logs filtered to a PR should be enough. There are a few...

The `.github` repository must be public, but otherwise, I don't believe there are any extra settings or permissions required. If you have access to the server configuration and logs, try...

I'm working on the same project @jchien14 was working on, so I'll try to investigate this next week and provide a fix.

I reproduced the first issue using a 262120 byte buffer, OpenSSH 5.9p1 and the latest develop branch of SSHJ. This was the smallest buffer that triggered this behavior. The root...

The second issue is a deadlock that appears as a result of the first issue: 1. The message is too large, causing the `sftp-server` command to exit 2. Meanwhile, enough...

Thanks for the continued work on this. I'm pretty sure #1492 will fix the problem I ran into with `DownloadMode`, but I don't remember if there were other "required, but...

My understanding is that this is a known consequence of how Go modules work (specifically, the fact that the major version appears in the import path and the import path...