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

Potential fix for #289 and #295 #304

Merged
merged 2 commits into from
Nov 10, 2018
Merged

Potential fix for #289 and #295 #304

merged 2 commits into from
Nov 10, 2018

Conversation

kensoh
Copy link
Member

@kensoh kensoh commented Nov 2, 2018

#289 - enclose wait step with casper.then() in order to make dynamic wait delay in scope for access

#295 - PHP 7 issues warning message which is not observed with PHP 5. this change removes the warning by avoiding an empty $repo_data[0]. ie increment repo_count only if there is already data in the array, otherwise discard header and start filling from $repo_data[0]. For the datatable (custom_csv_file portion), don't drop header as there is a dummy [iteration] header to let users reference current datatable iteration number.

#289 - enclose wait step with casper.then() in order to make dynamic wait delay in scope for access

#295 - PHP 7 issues warning message which is not observed with PHP 5. this change avoids an empty $repo_data[0], by removing the increment step that start filling elements from $repo_data[1]
#289 - enclose wait step with casper.then() in order to make dynamic wait delay in scope for access

#295 - PHP 7 issues warning message which is not observed with PHP 5. this change removes the warning by avoiding an empty $repo_data[0]. ie increment repo_count only if there is already data in the array, otherwise discard header and start filling from $repo_data[0].
@Aussiroth
Copy link
Contributor

Thanks Ken! I'll take a look though it. I was doing some automation stuff recently when I found a case where there might be issue with the new wait, want to recheck in case.

@kensoh
Copy link
Member Author

kensoh commented Nov 5, 2018

No probs Alvin! If you would like me to have a look, free feel to email me on your replication use case which isn't working with the updated wait implementation.

For the PHP notice issue, thought it would be good to resolve as older PHP 5 gets phased out, more users would receive the warning message. So I went ahead to have a look and made above PR.

Copy link
Contributor

@Aussiroth Aussiroth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Checked it out and it works fine on that wait case after all.
Overall the changes looks good to me to commit.

@kensoh
Copy link
Member Author

kensoh commented Nov 6, 2018

Oh nice... Thanks Alvin, copying Ryzal @ryzalk for committing to master branch -

@kensoh kensoh requested review from Aussiroth and removed request for Aussiroth November 6, 2018 07:30
@ryzalk ryzalk merged commit fb24db0 into master Nov 10, 2018
@kensoh kensoh deleted the patch-289-295 branch November 10, 2018 16:57
@kensoh kensoh restored the patch-289-295 branch November 12, 2018 09:45
@kensoh kensoh deleted the patch-289-295 branch November 12, 2018 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants