search

NOAA-ORR-ERD / WebGnomeClient

Javascript client that uses the WebGnomeAPI to create and run py_gnome models.
3 stars 9 forks source link

Weathering/Trajectory buttons inactive after New Model #3

Closed daf closed 8 years ago

daf commented 8 years ago

Selecting Model -> New from the menu, the Weathering/Trajectory/W+T buttons no longer respond to clicks.

daf commented 8 years ago

and doing Model -> New a second time adds a second configuration panel:

2015-09-30-15 22 39

daf commented 8 years ago

This can happen across sessions as well - close and reload the browser, you'll see "rewound model" in the log messages, and this behavior occurs.

NaomiWilkins-NOAA commented 8 years ago

Could you post your browser's javascript console when this occures? Most likely a javascript error, that won't show up in the logging panel.

If you're unfamiliar with what I mean: https://developers.google.com/web/tools/javascript/console/console-ui

daf commented 8 years ago

Nothing out of the ordinary - these flot errors happen on every New Model:

2015-09-30-15 41 16

NaomiWilkins-NOAA commented 8 years ago

Is this always happening? Are you on 0b264d655782b23625f85d7c9959c8f5ab63beae?

daf commented 8 years ago

Yes, that commit is in my branch's history (I have some local, specific purpose commits as well). I just did an npm install / grunt install again just in case, same errors there.

NaomiWilkins-NOAA commented 8 years ago

py_gnome and webgnomeapi are at their latest and the tests pass?

daf commented 8 years ago

I was a few commits behind on both, but updated now. py_gnome tests pass, not sure how to run WebGnomeAPI's. (py.test fails with a ConftestImportError)

NaomiWilkins-NOAA commented 8 years ago

py.test should run the webgnomeapi's tests. Want to post the stack trace for the conftest import error in a gist?

daf commented 8 years ago

Sure, https://gist.github.com/daf/031eeb7b94e92e1d86f4

Although I'm not sure it's related. I'll bisect the front-end and see if i can find it.

daf commented 8 years ago

Ugh, now I can't reproduce this bug at all! Perhaps I had some out of date results of less compilation or similar. I'm sorry for the goose chase!