Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EZP-20957: Removed misplaced semicolon which breaks the flow #651

Conversation

jeromegamez
Copy link
Contributor

The semicolon causes the method to always return true at this place.

if ( isset( $row[0] ) and $row[0] == $generatingFileMtime );
{
    return true;
}

See https://jira.ez.no/browse/EZP-20957

@gggeek
Copy link
Contributor

gggeek commented May 31, 2013

well spotted!!!

@andrerom
Copy link
Contributor

This should be reported as issue, might be it is causing issues that just haven't been reported..

@jeromegamez
Copy link
Contributor Author

I have created a JIRA issue and updated the name of the pull request.

@andrerom
Copy link
Contributor

+1

@crevillo
Copy link
Contributor

crevillo commented Jun 3, 2013

Btw, we can change that and for && (CS)

@tharkun
Copy link
Contributor

tharkun commented Jul 10, 2013

Nice

+1

@yannickroger
Copy link
Contributor

+1

@bdunogier
Copy link
Member

Good catch, +1. But we indeed need an issue for it.

@jeromegamez
Copy link
Contributor Author

@bdunogier The issue is here https://jira.ez.no/browse/EZP-20957 - or do you mean a real world issue that is caused by the misplaced semicolon?

@yannickroger
Copy link
Contributor

Thanks for the PR.
I rebased it in a single commit and merged it in master : dca49de

@jeromegamez jeromegamez deleted the eZDFSFileHandlerMySQLiBackend_semicolon branch July 11, 2013 09:40
@peterkeung
Copy link
Contributor

What is the problem / test case here? Is it that in some situations the "generating" file is prematurely considered timed out? Context for my questions: we occasionally experience odd issues with the cluster and would love to know whether our problem cases match the identified problem cases. That way we can know which patches to apply.

@jeromegamez
Copy link
Contributor Author

@peterkeung I have no actual test case for this, but I think your assumption is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
8 participants