Added --forceflush (-ff) option#307
Conversation
…fer whenever content is written, closes CCExtractor#306
nikofil
changed the title
|
@ccx-testerbot runtests master |
|
I'm sorry, but I cannot allow you to issue commands, as this repository is ran locally. Please ask a trusted contributor to run the tests for you instead. |
|
@ccx-testerbot runtests master @Aesmade I'll run them for you :) |
|
Thank you for the request. It has been added to the queue (id: 178). To see the progress you can go to the status page. Please note that depending on the current queue, it could take a while before any results will be visible. In each case I will report back here once the tests are done. |
|
The test suite finished running the test files. Below is a summary of the test results:
It seems that not all tests were passed completely. This is an indication that the output of some files is not as expected (but might be according to you). Please check the results page, and verify those files. If you have a question about this report, please contact @canihavesomecoffee. |
|
you are changing the default behaviour of ccextractor, now we only force the buffer if -ff option is passed. you are trying to make it optional, may I know the use case, where you find force buffer is not useful and create problem for you. |
|
@anshul1912: It was requested by @cfsmp3, because when he added it it slows down CCExtractor (or at least the bot test run) with 100%, hence his request in #306 to make it optional again @Aesmade Tests are good, didn't break anything 👍 |
Skipped functions with specific decorators (e.g `@template_renderer()`)
4 participants
Added option for forcing a flush on the output buffer whenever content is written