Closed
Bug 551199
Opened 15 years ago
Closed 15 years ago
"datetime_format_inbound" not found when calling Bug.search()
Categories
(Bugzilla :: WebService, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.6
People
(Reporter: LpSolit, Assigned: mkanat)
Details
(Keywords: regression)
Attachments
(1 file)
|
567 bytes,
patch
|
dkl
:
review+
|
Details | Diff | Splinter Review |
When testing mkanat's patch from http://landfill.bugzilla.org/bugzillaqa/show_bug.cgi?id=3153, I get:
# Application failed during request deserialization: Can't locate object method "datetime_format_inbound" via package "Bugzilla::XMLRPC::Deserializer" at Bugzilla/WebService/Server/XMLRPC.pm line 114.
Flags: blocking3.6+
| Reporter | ||
Comment 1•15 years ago
|
||
Hum, this is a regression. I cannot reproduce on 3.4.6.
Keywords: regression
| Assignee | ||
Comment 2•15 years ago
|
||
Okay, we keep getting into trouble because of the confusion between how the XML-RPC WebService class structure works, and how the JSON-RPC WebService class structure works. So for head, I'm going to simplify all of this, but for the 3.6 branch, I'll just do a quick fix.
| Assignee | ||
Comment 3•15 years ago
|
||
Simple fix. datetime_format_inbound was being called in ::Serializer, but using $self.
Comment 4•15 years ago
|
||
Comment on attachment 431635 [details] [diff] [review]
v1
Looks and works good. Passes the t/webservice_bug_search.t for me for me as well. Apologize for not running that before with my first review. r=dkl
Attachment #431635 -
Flags: review?(dkl) → review+
Updated•15 years ago
|
Flags: approval3.6?
| Assignee | ||
Updated•15 years ago
|
Flags: approval3.6?
Flags: approval3.6+
Flags: approval+
| Assignee | ||
Comment 5•15 years ago
|
||
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/trunk/
modified Bugzilla/WebService/Server/XMLRPC.pm
Committed revision 7061.
Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/3.6/
modified Bugzilla/WebService/Server/XMLRPC.pm
Committed revision 7030.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•