Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#315 Run in -async mode, the logs sequence mess

open
nobody
5
2012-07-15
2012-07-15
YFdyh000
No

In asynchronous mode, recommended to wait for the same page update details full output, then insert other information.
"Updating links on page [[xx:XXX]]" should not be inserted into the middle of the Continuous log.
The "Changes to be made​​:" of Same page should be with a continuous output.

Discussion

  • YFdyh000
    YFdyh000
    2012-07-15

     
    Attachments
  • That does not make any sense to me. If we have to wait for the update so we can have the output from the script and from the async save routine in the same place, the entire advantage of async saving is gone!

     
  • YFdyh000
    YFdyh000
    2012-07-15

    Oh. The following idea feasible?

    Suppose a situation:
    # max_queue_size = 10
    ...
    # The current waiting put queue is 9
    Getting 60 pages from wikipedia:en...
    # Add 10+ pages to the put queue at same time
    # The current waiting put queue is 19+
    ======Post-processing [[en:xxx]]======
    "Updating links on page [[en:xxx]]." 10+
    ...
    "Updating page [[en:xxx]] via API" 10+
    "Getting 60 pages from wikipedia:de..."
    ......

     
  • What you want is not really clear to me, but I suppose you want to let the bot stall when there are 10 pages waiting to be saved?

    What would be the use case for that?

     
  • YFdyh000
    YFdyh000
    2012-07-15

    I mean is all associated pages of a page as a unit to output and updates, rather than each page as a unit.