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

Mismatch between search criteria and data shown #48

Closed
huard opened this issue May 10, 2018 · 6 comments
Closed

Mismatch between search criteria and data shown #48

huard opened this issue May 10, 2018 · 6 comments
Assignees

Comments

@huard
Copy link
Contributor

huard commented May 10, 2018

To reproduce on pavics.ouranos.ca
Search Datasets

  • Project: ClimEx
  • Frequency: day
  • Variable: tas

First weird thing is that the Variable drop down menu now displays: poids, tasmax and tasmin. It's not clear why these variables would show up. There are 10 results, whose name suggest they store tasmin and tasmax. I would be expecting tas only.

For all of these datasets, the interface displays:
Variable: valeur des poids utilises pour faire la statistique

Selecting a dataset and "Add selection" raises an error. (Failed to fetch).

If I then select tasmax in addition to tas, the dashboard says Found 8700 total files in 5 results but displays no search result.

If I click on X to remove tasmax, the dropdown menus for all the search facets die.

@Renaud009
Copy link

So there a couple things to investigate here:
1- search return facets that shouldn't be returned: Ouranosinc/PAVICS-frontend#65
2- I noticed too a week ago that on borea 'height' was now 'poids' (!?)
3- Frontend shows only first variable returned in variables 'array' which is 'poids'
4- project-api returns in fact POST https://pavics.ouranos.ca/project-api/api/Projects/13/datasets 413 (Request Entity Too Large) which is weird. Could be a limitation of the nodejs server and/or nginx. If the datasets contains 1740 files, JSON object might big indeed

@ldperron
Copy link

@Renaud009 Can you give me the exact URL that triggered the 413 Too Large error? It's most likely a configuration issue with nginx, since the default is 1MB.

@Renaud009
Copy link

Renaud009 commented May 11, 2018

The URL I provided on Step 4 with a relatively big json body. Manipulating any dataset (PUT, POST, GET) on boreas containing 1700+ files will probably trigger such error.

@ldperron
Copy link

Corrected by hand on Boreas.

@ldperron
Copy link

Nginx config (fixes 413 Request Entity Too Large): https://github.com/Ouranosinc/PAVICS/commit/431604ed0b65283af51f380b065a0d60fdbf1dc9

@ldperron
Copy link

project-api config (fixes 413 Payload Too Large): Ouranosinc/PAVICS-project-api@c1af88a

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

No branches or pull requests

4 participants