chouette-core/app/services, branch docker Chouette manage transport static data Hotfix API Controller < ActionController::Base 2017-12-04T11:36:36+00:00 Robert 2017-12-04T11:36:36+00:00 614db1d28c8c8b8963a286cc0ffebf81b3acc8f2 






Hotfix for missing token in HTTPService when called from WorkbenchImportWorker
2017-12-01T14:25:48+00:00

Robert

2017-12-01T14:25:48+00:00

2792336f98056f3f7df8d02a3b2da968e97bfbe1












Refs: #4633@0.5h;
2017-10-24T13:28:44+00:00

Robert

2017-10-19T16:22:44+00:00

7f3b2aa1a1c4a2e051e1b2d3d3b57ab646b01a44

Speced and implemented ZipService to return additional directories
in the entry's `spurious` field.





Speced and implemented ZipService to return additional directories
in the entry's `spurious` field.







Remove `RetryService`
2017-08-25T10:14:29+00:00

Teddy Wing

2017-08-25T10:14:29+00:00

166b53305e41c51f4b401514a5ec2d828788a2cd

This is no longer being used as the `WorkbenchImportWorker` was
refactored and it was decided that we don't want to enable retries for
imports.

For example, imagine you have an hour-long import that fails after 50
minutes. We retry three times and now we've wasted 2.5 hours of your
time just to tell you that the import failed.

Thus the decision was to remove it.





This is no longer being used as the `WorkbenchImportWorker` was
refactored and it was decided that we don't want to enable retries for
imports.

For example, imagine you have an hour-long import that fails after 50
minutes. We retry three times and now we've wasted 2.5 hours of your
time just to tell you that the import failed.

Thus the decision was to remove it.







Refs: 4273@5h; Still debugging zip file upload inside post to Rails api; Retry removed (but not the deadcode yet) [amend me]
2017-08-22T16:07:13+00:00

Robert

2017-08-22T16:07:13+00:00

038710b22ccf3dd2421ec8d07fae45ef05a47ada












Refs: #4273@3h;
2017-08-22T07:37:30+00:00

Robert

2017-08-21T18:24:50+00:00

61c4a303183284fc107325aeeef5ace7a3e68c0c

Debugging Java Integration (ZipService -> HTTPService -> Object Creation)

   - Created an ErrorFormat concern to see what went wrong in the HTTP call
     as so many things can go wrong due to:

      * Timeout Issues
      * Illegal database setup or cleaning before tests





Debugging Java Integration (ZipService -> HTTPService -> Object Creation)

   - Created an ErrorFormat concern to see what went wrong in the HTTP call
     as so many things can go wrong due to:

      * Timeout Issues
      * Illegal database setup or cleaning before tests







Refs: #4273@20h;  Reverse Engeneeiring RubyZip fixed ZipService
2017-08-21T03:26:55+00:00

Robert

2017-08-21T03:13:11+00:00

327b1ec771a056451b0635ba80cc346fa1765299

        - Replzed Lazy Enum over get_next_entry and group by with explicit looping and yielding to an instance level enumerator
          that yields streams per subdir (wich represents a referential).

        - Fixtures and Specs that use a REAL usecase.

        Next: Get rid of metadata kludge (should fix failing specs)





        - Replzed Lazy Enum over get_next_entry and group by with explicit looping and yielding to an instance level enumerator
          that yields streams per subdir (wich represents a referential).

        - Fixtures and Specs that use a REAL usecase.

        Next: Get rid of metadata kludge (should fix failing specs)







initial
2017-08-11T07:57:55+00:00

Robert

2017-08-11T07:57:55+00:00

8eaa9249825f6eb6d667291fd9aa26bbde1ac7e3












Merge branch '1726-WorkbenchImport-for-multi-Netex-import'
2017-08-03T13:08:06+00:00

Robert

2017-08-03T13:08:06+00:00

09b0d438c50c7cd9ec9c18d1d90c16877b07d9a9












ParentImportNotifier: Use `Import.finished_statuses`
2017-08-02T10:36:16+00:00

Teddy Wing

2017-08-02T10:36:16+00:00

533804ec2755ba6564122cb4d43a7f8769d9d1ee

Instead of manually defining the finished statuses, use the method
that's already defined on `Import` to get them.

The only unfortunate part is that we now had to muss up our `Import`
code and convert those methods to class methods in order for them to be
accessible to `ParentImportNotifier` as well as its instance methods.

Refs #3511





Instead of manually defining the finished statuses, use the method
that's already defined on `Import` to get them.

The only unfortunate part is that we now had to muss up our `Import`
code and convert those methods to class methods in order for them to be
accessible to `ParentImportNotifier` as well as its instance methods.

Refs #3511