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

Implement pdo: getForUrl(), getPercentileForUrl(), getAll() #436

Merged
merged 1 commit into from
Nov 10, 2021

Conversation

fengqi
Copy link
Contributor

@fengqi fengqi commented Nov 5, 2021

@glensc
Copy link
Contributor

glensc commented Nov 5, 2021

@fengqi something wrong here. I've seen already these commits. also, try to make PR title more descriptive. also use Draft if the PR is not ready for merge, as it seems you have same commits here that are in the previous PR, so the previous one needs to be merged first so this can be rebased.

@fengqi fengqi marked this pull request as draft November 8, 2021 03:17
@fengqi fengqi force-pushed the implement-pdo branch 4 times, most recently from 3843a92 to 96350cf Compare November 8, 2021 04:37
src/Db/PdoRepository.php Outdated Show resolved Hide resolved
src/Db/PdoRepository.php Outdated Show resolved Hide resolved
src/Db/PdoRepository.php Outdated Show resolved Hide resolved
src/Searcher/PdoSearcher.php Outdated Show resolved Hide resolved
@fengqi fengqi force-pushed the implement-pdo branch 3 times, most recently from 63b24f0 to da031e0 Compare November 10, 2021 04:12
@fengqi fengqi changed the title Implement pdo Implement pdo: getForUrl(), getPercentileForUrl(), getAll() Nov 10, 2021
@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

@fengqi please don't force push during review. use git fixup, otherwise I do not see differences with the previous changes, and have to do review from scratch.

you can rebase and force push after you've pushed fixup commit

also, leave note of each fix if it's part of the discussion, like:

  • "fixed in COMMIT_HASH_OF_FIXUP_COMMIT"

@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

Also, be nice and respond when asked, for example, you never responded to this note anything:

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

please don't force push during review. use git fixup, otherwise I do not see differences with the previous changes, and have to do review from scratch.

you can rebase and force push after you've pushed fixup commit

also, leave note of each fix if it's part of the discussion, like:

ok

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

Also, be nice and respond when asked, for example, you never responded to this note anything:

ok

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

The recent commit are to fix the CS-Fixer error😂

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

@glensc Thank you for your reminder, I rarely contribute code publicly on Github, so many rules are not understood.
I have learned a lot by contributing code this time

@fengqi fengqi marked this pull request as ready for review November 10, 2021 07:17
@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

@fengqi I think you've finished here (CI passes), so you can do the final rebase. or do you have anything else in todo?

@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

also, while rebasing, update branch from origin:

This branch is out-of-date with the base branch
Merge the latest changes from 0.19.x into this branch.

GitHub suggests creating a merge commit, but in this repo, we prefer to rebase.

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

@glensc There is nothing todo, the rebase is complete

@glensc glensc added this to the 0.19.1 milestone Nov 10, 2021
@glensc glensc merged commit 5635164 into perftools:0.19.x Nov 10, 2021
@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

There are few more ✗'s in #320, if that's what you were attempting to solve here:

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

There are few more ✗'s in #320, if that's what you were attempting to solve here:

Searcher::getAll(direction) should already solved, others are used internally in our low frequency, i will solve it in my free time.

@glensc
Copy link
Contributor

glensc commented Nov 10, 2021

Updated the table, marked that hardcoded direction (#337) was solved via #436

@fengqi
Copy link
Contributor Author

fengqi commented Nov 10, 2021

Updated the table, marked that hardcoded direction (#337) was solved via #436

ok

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.

None yet

2 participants