Opened 9 years ago
Closed 8 years ago
#5343 closed defect (invalid)
Incorrect activity actor in API
| Reported by: | ayleph | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | programming | Keywords: | api, feed, pump |
| Cc: | tsyesika, sapienTech | Parent Tickets: |
Description
sapienTech's testing shows an incorrect activity actor.
In [1]: activity = pump.me.inbox.major[0] In [2]: print pump.me sapientech@pump.goblinrefuge.com In [3]: print activity.actor otyugh@pump.goblinrefuge.com In [4]: print pump.me.outbox[0] sapientech posted Testing pump.io on goblinrefuge In [5]: print activity.actor.outbox[0] sapientech posted Testing pump.io on goblinrefuge
Change History (2)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Cc: | added |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
I don't know how to reproduce this issue, and there's been no activity for months. I'm going to go ahead and tentatively close this. SapienTech, please re-open if you see this again.
Note:
See TracTickets
for help on using tickets.
I've had a brief look in the code, it seems that the correct actor is being set on the activity (the same actor which is set on the MediaEntry). The content which I presume has been generated by Mediagoblin as you seem to be using PyPump is generated based on what is set on activity.actor.
Can you provide steps on what you did to get this to happen so I can debug more? (not sure how the photo was uploaded, etc.)