12:03 <aakashjain> p12tic: tardyp: is it possible for someone to further look into https://github.com/buildbot/buildbot/issues/5933 (or guide me towards a fix)

12:36 <aakashjain> p12tic: tardyp: I think i found the fix. After changing file open mode from 'r' to 'rb' at the sending side (in buildbot try), the next error was coming from receiving side.

12:37 <aakashjain> receiving side was trying to convert the patch to unicode

12:37 <aakashjain> p12tic: tardyp: here is the fix which seems to work for me, can you please check if that looks good: https://bpa.st/YXYA

13:09 <tardyp> looks good to me, can we discuss that in a PR?

13:09 <tardyp> so that we can see if the test do agree it is good

13:17 <aakashjain> tardyp: sure, will create the PR.

13:18 <shurdeek> hello. What approach do you recommend when using buildbot to deploy the results of build to production?

13:18 <shurdeek> At the moment the simplest approach seems to be to use a buildstep to copy the file over network to a production machine.

14:25 <p12tic> shurdeek: Answered yesterday

16:00 <aakashjain> tardyp: Created https://github.com/buildbot/buildbot/pull/6001

16:51 <tardyp> aakashjain: looks good. its not fully baked by unit tests, but I think if this works for you end to end thats fine by my. We can wait for p12tic to see if he agrees.

16:53 <aakashjain> tardyp: Yeah, I deployed on my buildbot instance and it seems to works fine. The patches which couldn't be processed earlier, are now working fine.

17:13 <shurdeek_> p12tic: ok let me look up the logs

17:18 <shurdeek_> p12tic: can't find anything about it in my logs, maybe I was offline during that time? Only found this:

17:19 <shurdeek_> 18:23 < MattJ> Put the results somewhere and have a production machine pull them

19:22 <MattJ> shurdeek, and that wasn't an answer? :)

19:22 <MattJ> If not, please elaborate on your requirements

19:32 <aakashjain> tardyp: p12tic: I just filed https://github.com/buildbot/buildbot/issues/6002 , this issue is currently happening with this bot: https://ews-build.webkit.org/#/workers/19

19:34 <aakashjain> twistd.log shows: 2021-04-27 16:47:09-0700 [-] ews153 has been put in quarantine for 20s " probably after https://ews-build.webkit.org/#/builders/3/builds/46829

19:40 <sphet> Hello does anyone have any experience using VIsual Studio Code to debug a buildmaster running on a remove server? Or even running locally on Windows 10?

19:41 <sphet> tardyp what debugger do you use with buildmaster?

19:52 <p12tic> shurdeek: Ok, will copy paste.

19:52 <p12tic> shurdeek: What method to use for deployment is more of a question of what operational complexity you want.

19:53 <p12tic> files/archives is one option

19:53 <p12tic> docker containers via a private docker registry is another

19:54 <p12tic> some people have elaborate setups that eventually are fancy zip archive managers when containers aren't an option (I've seen that in HFT finance)

19:54 <p12tic> plenty of possibilities

19:54 <p12tic> Buildbot can do pretty much anything here

20:13 <sphet> Keep getting disconnected.

21:36 <shurdeek> MattJ: well, it is a very general answer. I was looking for something like an example, something more spcific, perhaps a suite

21:40 <shurdeek> p12tic: yea so it looks like what I suspected, you're supposed to use a separate solution or DIY

21:41 <shurdeek> I plan to use a mix of approaches depending on where it is deployed (docker images, git releases, ansible), but wanted something quick and dirty to start small

22:31 <Mansoor> good evening. i was wondering if anyone had any suggestions on passing parameters for a bash script, when using forced builds through the UI. right now, I am using util.Interpolate on the "reason" field on the build properties form, but it is not working as i want it to.

22:31 <Mansoor> I have a string like `-b branch_name -c client_name -e environment_name` in the reason field, and pass the interpolated object into ShellCommand step, but it passes in the parameters as a single string, and not three separate ones, causing the bash script to fail.