flask-debug-3933: update to set debug explicitly to False

[keithkroeger]

Description

Change so that flask does not run in debug mode.

Fixes #3933

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Executed test suite

[xrmx]

@keithkroeger please fix conflict and next time please leave enabled the ability for maintainers to update your pr. Thanks!

[xrmx]

@keithkroeger ping, let's get this merged

[keithkroeger]

@keithkroeger ping, let's get this merged

I'm not authorized to merge but appreciate it if you can
Thank you for the ping...resolved conflict on changelog

[lzchen]

@keithkroeger

Unfortunately everytime a different change is merged in, you will have to rebase and resolve any conflicts. If you change the pr to allow for one of the maintainers to fix the conflicts for you, you won't have to come back everytime for you to get this merged. I advise changing the permissions or creating a new PR, we can't hold off merging other prs.

[keithkroeger]

@keithkroeger

Unfortunately everytime a different change is merged in, you will have to rebase and resolve any conflicts. If you change the pr to allow for one of the maintainers to fix the conflicts for you, you won't have to come back everytime for you to get this merged. I advise changing the permissions or creating a new PR, we can't hold off merging other prs.

Thank you.
I don't see where I can grant that permission for the PR nor do I see somewhere to grant contributors on this PR.
I wonder if this is due to privs on my fork

Is there any way to allow auto merge?

[ocelotl]

@keithkroeger
Unfortunately everytime a different change is merged in, you will have to rebase and resolve any conflicts. If you change the pr to allow for one of the maintainers to fix the conflicts for you, you won't have to come back everytime for you to get this merged. I advise changing the permissions or creating a new PR, we can't hold off merging other prs.

Thank you. I don't see where I can grant that permission for the PR nor do I see somewhere to grant contributors on this PR. I wonder if this is due to privs on my fork

Is there any way to allow auto merge?

I have enabled auto merge, I'm not sure if this will merge this PR automatically, because I have seen it disable itself as tests are being run. Does this help?

[xrmx]

@keithkroeger I don't think closing and reopening is helpful

[keithkroeger]

@keithkroeger I don't think closing and reopening is helpful
I'm sorry, @xrmx
I was trying to open a new one to see if there was some way to enable committers to update.
But that option isn't available to me even on new PR.
I'm sorry for the spamming, if some occurred

[brianwarner]

Hi @xrmx, @lzchen, and @ocelotl, thanks for your help merging this. I think I can help with some context on the request to allow maintainers to edit.

Unfortunately that setting is only available for personal forks, and it isn't available when a repo is forked into an org (as is the case with our contributions). It means the responsibility will be on our contributors to keep things as up-to-date as possible.

I'm sorry if it created difficulties here. We'll do our best to be responsive about keeping branches updated while they're in flight.