Short status update

[Ariel Nunez]

Hello people,

I have been doing a few changes in the riab tree without properly
updating the community on the progress.

Here is a short version of what I have been up to:

#1 Better error handling (no more Django debug pages wrapped in a very
small window)
#2 Caption reporting after successful activation
#3 Id numbers on test output, the --with-id parameter can be used to
run only one test, or a few:
risiko-test risiko impact --with-id 5
#4 GeoNode merge with latest master, the main reason we are using
GFDRR's branch of GeoNode is to inherit the start, stop and clean
management commands. This caused a small incompatibility in names
(with or without dashes) that I hope to fix by aliasing risiko-start
to "risiko start", that way our own loved risiko-* commands would work
and we would still have the option to do "risiko syncdb", "risiko
createsuperuser", "risiko shell_plus" and "risiko validate" if we are
advanced users.
#5 We have been experiencing some test failures related to two main problems:
a) Uploaded layers are not immediately available
b) The first test in the suite that tries to perform an upload
gets a GeoServer error related to a login timeout, I have added a
first dummy test that tries to do an upload as a workaround but still
do not know the main cause.

My short term plan (next couple of days) has only two points:
i) Make sure there are no test failures again and/or "weird bugs"
are properly isolated.
ii) Play more with Andrea's new branch and help clean rough edges
(if any) in the backend (riab and geonode).

[Ole Nielsen]

Hi Ariel
Thanks heaps for the work and the update

#1 Better error handling (no more Django debug pages wrapped in a very small window)

Extremely ecstatic about this. Hopefully, that'll migrate through to other applications too.
 

#2 Caption reporting after successful activation

Nice
 

#3 Id numbers on test output, the --with-id parameter can be used to
run only one test, or a few:
   risiko-test risiko impact --with-id 5

Sounds good, but not sure how to use it. Do you give test cases an ID through a decorator or something like that?
 

#4 GeoNode merge with latest master, the main reason we are using
GFDRR's branch of GeoNode is to inherit the start, stop and clean
management commands. This caused a small incompatibility in names
(with or without dashes) that I hope to fix by aliasing risiko-start
to "risiko start", that way our own loved risiko-* commands would work
and we would still have the option to do "risiko syncdb", "risiko
createsuperuser", "risiko shell_plus" and "risiko validate" if we are
advanced users.

Sounds good. As mentioned in issue:105 it'd be nice to have a simple high level CLI plus a lower level with all the Django bells in it.

 

#5 We have been experiencing some test failures related to two main problems:
   a) Uploaded layers are not immediately available

Do you think this is a manifestation of what was reported in issue:98 ?
 

   b) The first test in the suite that tries to perform an upload
gets a GeoServer error related to a login timeout, I have added a
first dummy test that tries to do an upload as a workaround but still
do not know the main cause.

My short term plan (next couple of days) has only two points:
  i) Make sure there are no test failures again and/or "weird bugs"
are properly isolated.

OK - as of today there are 3 failures. One is issue:114, the other two are tests that stopped working some time in mid to late July. They don't appear to be related to timing, though.

 

  ii) Play more with Andrea's new branch and help clean rough edges
(if any) in the backend (riab and geonode).

Love it

Cheers
Ole