**I can't believe I have to type this out.** Read the CHANGELOG before posting; your issue was fixed in v4.3.0 and you're clearly running an outdated build. If that doesn't help, search the forum — someone already posted a workaround three

Opening thread commentary.

Oh great. Another thread where I have to do the user's homework for them. Read the CHANGELOG before posting — your issue was explicitly fixed in v4.3.0, which means you're clearly running an outdated build and haven't checked anything since 20

I can't believe I have to type this out. Read the CHANGELOG before posting; your issue was fixed in v4.3.0 and you're clearly running an outdated build. If that doesn't help, search the forum — someone already posted a workaround three years

I can't believe I have to type this out. Read the CHANGELOG before posting; your issue was fixed in v4.3.0 and you're clearly running an outdated build. If that doesn't help, search the forum — someone already posted a workaround three years

sorry i didn't read the changelog -- my company has like 50 different internal versions of this and idk which one we use so it's hard to tell if i'm on a newer build or something

but yeah that sounds right for what i was getting. does anyone know why v4.3 changed that specific flag though? i have some old scripts using the old behavior and im not sure if theyll break with the update or if the new version backwards-compatible

Look at your version string in the footer of the CLI output and then look at the CHANGELOG on the releases page. You're running 4.1.6, which has this bug documented as 'fixed in v4.3.0.' So either update to a build from

okay i dont understand this thread... is v4.3.0 out? google says that version has some bugs so maybe it isnt fixed. can u just tell me what to type in my config file instead of making me read a changelog?? im literally staring at the screen and nothing works. help pls

Read the CHANGELOG before posting; your issue was fixed in v4.3.0 and you're clearly running an outdated build. If that doesn't help, search the forum — someone already posted a workaround three years ago and it works for exactly this use case.

Ah dang it. My bad -- just updated to 4.3 now and it's