Ticket #596 (closed defect: fixed)

Opened 8 months ago

Last modified 3 weeks ago

RSS & Atom failure with "Request did not return a string"

Reported by: ddunbar Owned by:
Priority: major Milestone: 0.8.0
Version: 0.7.12 Keywords:
Cc: cdadhemar@…

Description

When attempting to access the RSS and atom feeds, twistd fails with: -- Request did not return a string

Request:

<GET /atom HTTP/1.1>

Resource: <buildbot.status.web.feeds.Atom10StatusResource instance at 0x101ac8b48>

Value: --

I think the problem is that Atom10StatusResource.item is returning a unicode string. I'm not sure of the correct fix, but returning str(data) instead seems to solve the problem.

Attachments

rss_failure.txt Download (70.9 KB) - added by cdadhemar 5 weeks ago.
Rss failure error report

Change History

  Changed 8 months ago by dustin

  • status changed from new to closed
  • resolution set to fixed
  • milestone changed from undecided to 0.7.12

Changed 5 weeks ago by cdadhemar

Rss failure error report

  Changed 5 weeks ago by cdadhemar

  • cc cdadhemar@… added
  • status changed from closed to reopened
  • version changed from 0.7.11 to 0.7.12
  • resolution fixed deleted
  • milestone changed from 0.7.12 to undecided

Hello,

I reopen the bug : I have still this issue using Buildbot 0.7.12 (I verified that the patch mentioned above was correctly applied).

Note that in the failure report of my step their are some c++/valgrind and home made test suites output that might produce some characters not filtered by twisted's html.escape method.

However for reporting the errors in the html/waterfall view I use : from xml.sax.saxutils import escape Which works great.

I hope it helped ! Cheers, Chicha

  Changed 5 weeks ago by marcusl

FWIW, for 0.8 we use jinja to generate rss feeds, so this error should be fix there.

For 0.7.x series, we should encode it to utf-8 and this should be stated in the heading of the xml document.

  Changed 4 weeks ago by dustin

  • status changed from reopened to closed
  • resolution set to fixed

marcusl: even better -- we're just not doing 0.7.x anymore :)

Marking as fixed, since it's fixed in the new code.

  Changed 4 weeks ago by cdadhemar

Hi dustin,

Do you mean that this is fixed in 0.8 (the dev branch) and that the next release will be the 0.8 branch (no more 0.7.x releases) ?

This sounds like a great news :-) Thanks !

follow-up: ↓ 7   Changed 4 weeks ago by dustin

  • milestone changed from undecided to 0.8.0

cdadhemar: yes to both.

I'm still reserving the option to do another 0.7.* release if 0.8.0 doesn't pan out as well as I'd like, but with luck we'll jump straight to 0.8.0 and be done with it.

in reply to: ↑ 6   Changed 3 weeks ago by cdadhemar

Thanks a lot !

Note: See TracTickets for help on using tickets.