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

Chromium #563

Open
wants to merge 723 commits into
base: py25
Choose a base branch
from
Open

Chromium #563

wants to merge 723 commits into from

Conversation

Dulow187
Copy link

No description provided.

maruel and others added 30 commits October 16, 2013 15:33
In 789205957e84 I had temporarily put the new imports at the top of the
file so it was simpler to reapply the patch on top of the chromium branch
for manual testing.

I forgot to move the lines back to their respective place before committing
so fix this here.

[email protected]
The fact the new /restricted urls in 789205957e8442952d5fb03feaf14512492e7ad7
wasn't in under the restricted section was an error.

Google bot is on a spree crawling all random searches, which causes a fair
amount of NeedIndexError errors, but Google bot doesn't care and continues.

These pages do not need to be harvested anyhow to disable the whole /search
section.

[email protected]

Review: https://codereview.appspot.com/14761043/
Use logging.error() instead of assert, so that the processing goes on but that
the error is not completely silently dropped.

The problem is that calculating the latency twice resulted in different values.
This can happen when the way latency is calculated is changed.

Review: https://codereview.appspot.com/14771043/
auto_current_user_add doesn't work correctly in the /<issue>/try/<patchset>
handler.

Author: [email protected]

Review: https://codereview.appspot.com/14774045/
….py.

This is in preparation for the upload rewrite planned here:
https://docs.google.com/a/chromium.org/document/d/1XNucijypKyfiUUMIrHn9Bxvz-mFHUhTqgddIirUl73Y/edit#

This change should have no semantic effect on the behavior of Rietveld.

[email protected]

Review URL: https://codereview.appspot.com/17780043/
This should fix the navigation discrepancy between the main patchset ordering
and the per-diff ordering.

[email protected]
BUG=chromium:313078

Review URL: https://codereview.appspot.com/19610043/
Conservatively utilizes the new json_response behavior. For apis which claim
to respond with JSON, we should always respond with JSON. However, I know that
some of the non-JSON responses may be expected by clients, so I don't correct
everything that I could correct.

[email protected]
BUG=

Review URL: https://codereview.appspot.com/17890043/
Chromium counterpart to https://codereview.appspot.com/17910043/

I also took the liberty of adding a decorators_chromium.py

Conflicts:
  codereview/views.py

[email protected]
BUG=

Review URL: https://codereview.appspot.com/19690043/
Doesn't remove as much cruft as I had hoped, but it's still less cruft.

[email protected]
BUG=

Review URL: https://codereview.appspot.com/20120043/
jrobbins-at-chromium and others added 29 commits August 12, 2014 10:37
…rated.

In the GAE datastore, booleans are actually tristate: true, false, and missing.
So, queries have to take that into account.

Review URL: https://codereview.appspot.com/137090043/
Copy link

@perrystan1489 perrystan1489 left a comment

Choose a reason for hiding this comment

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

There's a lot of changes here

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.