Jordan Petridis df302ad517 Pipeline: Do not terminate the stream upon errors ... Stream::for_each terminated the stream upon the first error. This was causing feeds to not update if any one returned a non-200ish result. To work around this, we create a succesfull result for every entry regardless at the end. While we are at it, aslo switch from FuturesOrdered stream to FuturesUnordered. There is no reason to use Ordered, this was a typo initially.		2018-10-04 18:48:11 +03:00
..
models	Source: Refactor the clear_etags method api	2018-10-04 16:46:04 +03:00
database.rs	Refactor the tests to use ? operator	2018-08-18 17:02:31 +03:00
dbqueries.rs	Refactor the tests to use ? operator	2018-08-18 17:02:31 +03:00
errors.rs	Pipeline: Complete the move to Tokio Runtime	2018-09-29 13:35:45 +03:00
feed.rs	Pipeline: Complete the move to Tokio Runtime	2018-09-29 13:35:45 +03:00
lib.rs	Pipeline: Complete the move to Tokio Runtime	2018-09-29 13:35:45 +03:00
opml.rs	Refactor the tests to use ? operator	2018-08-18 17:02:31 +03:00
parser.rs	Initial massive renaming.	2018-07-25 03:26:35 +03:00
pipeline.rs	Pipeline: Do not terminate the stream upon errors	2018-10-04 18:48:11 +03:00
schema.patch	Initial massive renaming.	2018-07-25 03:26:35 +03:00
schema.rs	Initial massive renaming.	2018-07-25 03:26:35 +03:00
utils.rs	Refactor the tests to use ? operator	2018-08-18 17:02:31 +03:00