Error when `hit extend` the duration

[yunshiuan]

I tried to extend the duration of a hit but encountered an error. hit extend <HITid> --expiration 60

Response(Operation: extend_hit | Status: error | Exception: 'AmtServicesSuccessResponse' object has no attribute 'getitem')

Note that hit extend <HITid> --assignment 10 works fine.

I am using psiTurk version 2.3.8 with python 2.7.17.

[deargle]

Thanks for the report. I think the first call actually worked, btw. Just an error in the feedback.

On Wed, May 20, 2020, 5:53 AM Chuang, Yun-Shiuan notifications@github.com wrote:

I tried to extend the duration of a hit but encountered an error. hit extend --expiration 60 Response(Operation: extend_hit | Status: error | Exception: 'AmtServicesSuccessResponse' object has no attribute 'getitem')

Note that hit extend --assignment 10 works fine.

I am using psiTurk version 2.3.8 with python 2.7.17.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NYUCCL/psiTurk/issues/421, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI6Y7MHGUYYIGHRTPSLQTTRSPADFANCNFSM4NF3TGLA .

[yunshiuan]

That doesn't work for me though. The HIT duration does not increase after I run hit extend <HITid> --expiration 60. That dost not work for both expired and unexpired hit.

[yunshiuan]

So before this problem is solved, I wonder if I could just create another hit with the same ad_group string, and safely assume that workers would not repeat in participation? That is, workers that have already taken one of the hits in the same ad_group, would not be able to take another hit in the same ad_group. Is that right?

[deargle]

Yes, they would be blocked. ad group doesn't have anything to do with it -- they would be blocked from retaking. Your local database is consulted.

On Wed, May 20, 2020 at 8:56 PM Chuang, Yun-Shiuan notifications@github.com wrote:

So before this problem is solved, I wonder if I could just create another hit with the same ad_group string, and safely assume that workers would not repeat in participation? That is, workers that have already taken one of the hits in the same ad_group, would not be able to take another hit in the same ad_group. Is that right?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NYUCCL/psiTurk/issues/421#issuecomment-631848872, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI6Y7NS4LW3MGP7YO3T4HLRSSJ6XANCNFSM4NF3TGLA .

[deargle]

v2.3.9 should be on pip in a few minutes, with a fix for this. Thanks again for reporting.

[yunshiuan]

Thank you! It seems like it only works for unexpired hit (even though it prints Response(Operation: extend_hit | Status: success)). Is that correct? Is there a way to makes an expired hit unexpired again?

Additionally, if I just create another new hit (with the same codeverion), will the counterbalancing process continues? Or if it will start over the counterbalancing process (just like reseting the codeversion parameter)?

[deargle]

You know, I'm not sure, I've never tried that. I always just create a flood of micro hits, creating new ones if the old ones expire if I need more data.

On Fri, May 22, 2020, 7:29 AM Chuang, Yun-Shiuan notifications@github.com wrote:

Thank you! It seems like it only works for unexpired hit. Is that correct? Is there a way to makes an expired hit unexpired again?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/NYUCCL/psiTurk/issues/421#issuecomment-632691048, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAI6Y7LC5L6XVX5BUFW2BK3RSZ44NANCNFSM4NF3TGLA .