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

[Fixes #4959] By using UPLOADER=geonode.rest we are facing a timing i… #4960

Merged
merged 1 commit into from Sep 30, 2019

Conversation

afabiani
Copy link
Member

…ssues on signals

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

  • Confirm you have read the contribution guidelines
  • You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in documentation)
  • Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

  • There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemptions is, changes not visible to end users)
  • The issue connected to the PR must have Labels and Milestone assigned
  • PR for bug fixes and small new features are presented as a single commit
  • Commit message must be in the form "[Fixes #<issue_number>] Title of the Issue"
  • New unit tests have been added covering the changes, unless there are explanation on why the tests are not necessary/implemented
  • This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
  • This PR passes the QA checks: flake8 geonode
  • Commits changing the settings, UI, existing user workflows, or adding new functionality, need to include documentation updates

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

@cla-bot cla-bot bot added the cla-signed CLA Bot: community license agreement signed label Sep 27, 2019
@afabiani afabiani force-pushed the ISSUE_4959 branch 2 times, most recently from e88c65a to 275fc30 Compare September 30, 2019 08:37
@codecov
Copy link

codecov bot commented Sep 30, 2019

Codecov Report

Merging #4960 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #4960   +/-   ##
=======================================
  Coverage   59.88%   59.88%           
=======================================
  Files         231      231           
  Lines       12418    12418           
  Branches     1797     1797           
=======================================
  Hits         7437     7437           
  Misses       4366     4366           
  Partials      615      615

Copy link
Member

@capooti capooti left a comment

Choose a reason for hiding this comment

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

Great work @afabiani it seems all good to me!
I am going to merge this and will test it on two different instances which have a large number of layers and let you know

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed CLA Bot: community license agreement signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants