Unable to install dev fixtures on new or existing instance

[jaalfaro]

When attempting to "paver install_dev_fixtures", I get the following error

DeserializationError: Problem installing fixture '/usr/src/geoq/geoq/maps/fixtures/initial_data.json': [u'Enter valid JSON']

This appears to be related to the checkin on Jun 8, but can't seem to see an issue in the JSON.

[jaycrossler]

What db version do you have? I think that checkin forced the use of the latest Postgres/postgis.

On Thu, Jun 12, 2014 at 3:25 PM, John Alfaro notifications@github.com wrote:

When attempting to "paver install_dev_fixtures", I get the following error

DeserializationError: Problem installing fixture '/usr/src/geoq/geoq/maps/fixtures/initial_data.json': [u'Enter valid JSON']

This appears to be related to the checkin on Jun 8, but can't seem to see an issue in the JSON.

Reply to this email directly or view it on GitHub: https://github.com/ngageoint/geoq/issues/103

[jaalfaro]

PostgreSQL 9.3.2 POSTGIS="2.1.1 r12113" GEOS="3.4.1-CAPI-1.8.0 r3892" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.2, released 2012/10/08" LIBXML="2.7.6" LIBJSON="UNKNOWN" TO POLOGY RASTER

[jackiekazil]

I am having the same issue & am I also running 9.3.2.

Jacqueline Kazil | @jackiekazil

On Thu, Jun 12, 2014 at 3:46 PM, John Alfaro notifications@github.com wrote:

PostgreSQL 9.3.2 POSTGIS="2.1.1 r12113" GEOS="3.4.1-CAPI-1.8.0 r3892" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.2, released 2012/10/08" LIBXML="2.7.6" LIBJSON="UNKNOWN" TO POLOGY RASTER

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-45939099.

[jackiekazil]

We need to freeze and standardize on one version for stability. John -- what version was a our testing done on?

Jacqueline Kazil | @jackiekazil

On Thu, Jun 12, 2014 at 4:08 PM, Jacqueline Kazil jackiekazil@gmail.com wrote:

I am having the same issue & am I also running 9.3.2.

Jacqueline Kazil | @jackiekazil

On Thu, Jun 12, 2014 at 3:46 PM, John Alfaro notifications@github.com wrote:

PostgreSQL 9.3.2 POSTGIS="2.1.1 r12113" GEOS="3.4.1-CAPI-1.8.0 r3892" PROJ="Rel. 4.8.0, 6 March 2012" GDAL="GDAL 1.9.2, released 2012/10/08" LIBXML="2.7.6" LIBJSON="UNKNOWN" TO POLOGY RASTER

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-45939099.

[jaalfaro]

So, just to be sure, I saw that 8.4 was on there and thought, maybe the wrong libraries were being used, so I built a version with only 9.3, and get the same issue.

[jaalfaro]

Testing was done on 9.3. At this point, I'm not convinced its a version issue. But I could be wrong.

[jaycrossler]

It worked for me after upgrading to 9.3 though it might be another issue as you describe

--Jay

On Thu, Jun 12, 2014 at 4:34 PM, John Alfaro notifications@github.com wrote:

Testing was done on 9.3. At this point, I'm not convinced its a version issue. But I could be wrong.

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-45944335.

[jackiekazil]

I looked into this evening to get it out of the way. I believe that the json was looking for new fields that were added to the model, but not to the json dump.

New fields added that were not a part of the errored json: https://github.com/ngageoint/geoq/commit/8e2ff79c26bfa70b88e7df5ced8a46a27675f5bb#diff-7b943248ba969252e547ee0eefb2c401R95

So, the migrations 0006 & 0007 were adding the fields, then the data w/o the fields was trying to loaded.

@jaalfaro & @jaycrossler - can you check new maps json I check in and confirm that it works for both of you. It now works for me, but I always appreciate a second set of eyes. Please reopen the ticket if it doesn't.

[jaalfaro]

This morning I'm able to install dev features, but now I get errors viewing work cells (AOIs) along with, not completely sure its related, layers are not loading (NexRad and National Map)

At first I thought it was just NexRad, so removed that layer from the Map, but then National Map failed, so I think its something else.

Uncaught TypeError: Cannot set property '5' of undefined aoi_feature_edit.js:26 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (min-resolution: 144dpi) 7237:123 GET http://geoq/users/geoq/projects//badges 404 (NOT FOUND) 524e82f7a98c.js:1 Uncaught TypeError: Cannot read property '5' of undefined aoi_feature_edit.js:618 GET http://raster.nationalmap.gov/ArcGIS/rest/services/TNM_Large_Scale_Imagery/…0037508.342789244,-20037508.342780735,20037508.342789244,20037508.34278071 500 (Internal Server Error) leaflet-src.js:2958

[jackiekazil]

That looks like a separate issue and new ticket to me.

[jaycrossler]

I noticed all the national map layers stopped working for me yesterday when accessed from our web server. They can be accessed directly, so I think they might have added some usage-reduction mechanism.

The 'property 5 of undefined' is an issue, will examine.

On Fri, Jun 13, 2014 at 7:41 AM, John Alfaro notifications@github.com wrote:

This morning I'm able to install dev features, but now I get errors viewing work cells (AOIs) along with, not completely sure its related, layers are not loading (NexRad and National Map) At first I thought it was just NexRad, so removed that layer from the Map, but then National Map failed, so I think its something else.
Uncaught TypeError: Cannot set property '5' of undefined aoi_feature_edit.js:26 Consider using 'dppx' units, as in CSS 'dpi' means dots-per-CSS-inch, not dots-per-physical-inch, so does not correspond to the actual 'dpi' of a screen. In media query expression: only screen and (-webkit-min-device-pixel-ratio: 1.5), only screen and (min-resolution: 144dpi) 7237:123 GET http://geoq/users/geoq/projects//badges 404 (NOT FOUND) 524e82f7a98c.js:1 Uncaught TypeError: Cannot read property '5' of undefined aoi_feature_edit.js:618

GET http://raster.nationalmap.gov/ArcGIS/rest/services/TNM_Large_Scale_Imagery/…0037508.342789244,-20037508.342780735,20037508.342789244,20037508.34278071 500 (Internal Server Error) leaflet-src.js:2958

Reply to this email directly or view it on GitHub: https://github.com/ngageoint/geoq/issues/103#issuecomment-46001724

[stephenrjones]

I know I was in that area of the code yesterday and had to merge in some different fixes, so that might have caused an issue. I've pushed my latest code which seems stable here -- it's not complete, but should fix the error seen

[jaalfaro]

Those last changes seemed to have fixed the issue. For the layers, nexrad is working, but NationalMap is not, but looking around, the layers we were using are missing from the server, so I don't think thats our problem, well, maybe it is, but not ours fix. I think you can close this now.

[jaycrossler]

Steve, thanks. That fixed it on the dev server too. Though, I'm noticing that Icons are no longer showing on the bar on the left.

--Jay

On Fri, Jun 13, 2014 at 9:15 AM, John Alfaro notifications@github.com wrote:

Those last changes seemed to have fixed the issue. For the layers, nexrad is working, but NationalMap is not, but looking around, the layers we were using are missing from the server, so I don't think thats our problem, well, maybe it is, but not ours fix. I think you can close this now.

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-46009366.

[stephenrjones]

Are the buttons on the toolbar blank for points? I'm seeing the icons, but haven't worked out the mouse-over description yet

[jaycrossler]

Was this checked in: /static/images/markers/images/question.png

--Jay

On Fri, Jun 13, 2014 at 9:34 AM, Stephen Jones notifications@github.com wrote:

Are the buttons on the toolbar blank for points? I'm seeing the icons, but haven't worked out the mouse-over description yet

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-46011330.

[jaycrossler]

It looks like this line in edit.html is causing issues: 64) aoi_feature_edit.static_root = "{{ STATIC_URL }}" + "images/markers/";

--Jay

On Fri, Jun 13, 2014 at 9:36 AM, Jay Crossler jay.crossler@gmail.com wrote:

Was this checked in: /static/images/markers/images/question.png

--Jay

On Fri, Jun 13, 2014 at 9:34 AM, Stephen Jones notifications@github.com wrote:

Are the buttons on the toolbar blank for points? I'm seeing the icons, but haven't worked out the mouse-over description yet

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-46011330.

[stephenrjones]

Not sure why that would cause an issue, though we can probably take that line out as I changed from storing the Maki icons locally to using their service api

[jaycrossler]

I'm debugging now. It looks that because the title of the icon isn't set, it's not matching the proper lookup/swap code to show the icons in the left box. Will figure it out.

--Jay

On Fri, Jun 13, 2014 at 9:47 AM, Stephen Jones notifications@github.com wrote:

Not sure why that would cause an issue, though we can probably take that line out as I changed from storing the Maki icons locally to using their service api

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/geoq/issues/103#issuecomment-46012687.

[jaalfaro]

I added to my normal update "python manage.py collectstatic" that helped resolve some of those issue.