-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
GEOS-11607 Bugfix - KML WMS GetMap is performing a heavy database load query #8035
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
Conversation
Tests are failing. We'll take a look. |
@aaime , the KMLTest "testRasterLayer" is failing after our change, on this assertion: assertXpathEvaluatesTo("1", "count(//kml:GroundOverlay)", dom);
I'm not familiar with the GroundOverlay attribute, and if it makes sense the changed result value. Can you take a look please? Thanks |
I am bad at reading any code, but I try. By https://github.com/geoserver/geoserver/pull/8035/files Maybe because of this the count is 0 instead of the expected 1? I do not know why "4.00243024094668" is expected to be included, but perhaps it is due to the Earth curvature. Sorry if my suggestions do not make sense. |
@tiago-s-vieira-alb when running against a raster layer context.getCurrentFeatureCollection returns null, a NPE occurs, and the test fails. Something like this should address the issue (untested): Layer currentLayer = context.getCurrentLayer();
Envelope bounds;
if (currentLayer instanceof FeatureLayer) {
bounds = context.getCurrentFeatureCollection().getBounds();
} else {
bounds = currentLayer.getBounds();
} |
It works! |
…d query fix format
Hi, The pipeline "Linux JDK GitHub CI / build (21, temurin, ubuntu-22.04)" is failing because:
How can I launch it again? |
that problem seems to be fixed in the main branch (as of #8063), if you rebase your branch it should pass. for now I've restarted the failing build |
Same error, but now in the "Assembly GitHub CI / build (ubuntu-22.04, 11, temurin)" |
All green! :) |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.25.x 2.25.x
# Navigate to the new working tree
cd .worktrees/backport-2.25.x
# Create a new branch
git switch --create backport-8035-to-2.25.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 624d243860d5ecd3d234b3f225a7e615a4b417a2,958b11a0082ada209c81fe6a5eab17f0e7a0d487,f13c63b022b2725e10826b53d10e25963cab30a1,2881042e6616b4d45b0f366da2be58010708b3a3
# Push it to GitHub
git push --set-upstream origin backport-8035-to-2.25.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.25.x Then, create a pull request where the |
The backport to
stderr
stdout
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.26.x 2.26.x
# Navigate to the new working tree
cd .worktrees/backport-2.26.x
# Create a new branch
git switch --create backport-8035-to-2.26.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick 624d243860d5ecd3d234b3f225a7e615a4b417a2,958b11a0082ada209c81fe6a5eab17f0e7a0d487,f13c63b022b2725e10826b53d10e25963cab30a1,2881042e6616b4d45b0f366da2be58010708b3a3
# Push it to GitHub
git push --set-upstream origin backport-8035-to-2.26.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.26.x Then, create a pull request where the |
Merged. |
We can wait for the main release (27.x). |
JIRA ISSUE:
https://osgeo-org.atlassian.net/browse/GEOS-11607
Checklist
main
branch (backports managed later; ignore for branch specific issues).For core and extension modules:
[GEOS-XYZWV] Title of the Jira ticket
.