TK Soh

> Here's a version that allows you to put a wildcard (*) at the end of the trigger URL. > > https://chrome.google.com/webstore/detail/staying-alive-with-wildca/lkdnaojfhnjkophgbnmfaciclaghffpe > > Any chance we can get this...

Just to share that I am eagerly awaiting this feature to be supported soon too, as it has impacted my apps. Right now I am forced to reduce the cache...

> Can you try `puro rm master` and then `puro create stable`? Sorry I'm slightly confused. Did you mean `puro create master`? If so, then I already did that, but...

Just found out that puro gave the error when running in git bash (my apology for failing to mention this earlier). When running in cmd.exe, things seem to work fine...

Just to update that I don't see the same error in PowerShell. So this issue seems to be specific to git bash.

Here are the output of `puro --verbose` in git-bash and PowerShell for comparison. PowerShell: ``` PS C:\Users\teeka> puro --verbose -e master flutter --version [V] Started waiting for lock on C:\Users\teeka\.puro\prefs.json...

@pingbird as requested ``` $ puro --log-level=4 -e master flutter --version [D] envPuroRoot: C:\Users\teeka\.puro [D] binPuroRoot: null [D] firstRun: false [D] legacyPubCache: null [V] Started waiting for lock on C:\Users\teeka\.puro\prefs.json...

This seems to affect some flutter releases only. Any update on the fix? BTW, the temp fix is not working for me.