Steve Manuel

@diced - thanks for the report. are you able to use `wrangler dev` instead?

@tillkruss - would you mind sharing the full `wrangler dev` command you're using, including all the args/params (ensuring nothing private/secret is exposed) Thanks!

Yea, that's not ideal. Can you think of any reason why one _wouldn't_ want those build values inherited between environments? cc/ @Electroid @xortive

Hey all - we're currently looking into this issue & have some questions if anyone can share details on the following: 1. which version of wrangler are you running? `wrangler...

@timhaak, re: > From my side, it worked once I created the following folder. > mkdir -p ~/.wrangler/config/ Did the CLI show any permission error indicating that it couldn't write...

@Yrlish - thank you! > Just because you wanted me to test, wrangler doesn't seem to get stuck as described in #1883. 😄 haha that seems to be the way...

Hi @YaseenAlk - > From reading the wiki, it's my understanding that the preferred way to add more rules is to implement them in a plugin, which takes as input...

Hi @sidtaduri - thanks for this proposal. I don't have a strong opinion about the use of a configuration file, but I'd be interested to know what kind of things...

@rodaine - I see how these errors being reported adds some confusion.. they're not _really_ errors, but the tool is demonstrating expected behavior IMO. In order to provide the tool...

I see, thanks for the additional details 🙂 To me, it seems that you'd want to run `protolock commit --force` to re-declare the "locked" state of your proto files after...