I have a problem with Aggregate 1.0 rev. 3. I tried to upload a new
form from Aggregate, which failed, I think because there was already
an existing form with the same name (although the build id is
different). Now, when I login using my Google id the screen loops
between the main page and the submissions filter page several times
until a window appears: “Unable to retrieve users from server: 0”.
When I click ok or close it, it starts looping again. Therefore, I
cannot delete the duplicate form. The anonymous user login only has
permission to collect, and there are no other user-ids assigned to the
appspot.
Why does this happen and how can I fix it? I assumed that, since the
upload failed, the file would not have uploaded and no conflict
occurred (if this is the problem).
Go to the appengine management page (https://appengine.google.com/ ), click
on your appengine instance, and click on the Logs link on the left of the
page. There should be an error showing up there. Please copy it into a
file and send it as an attachment.
Mitch
···
On Mon, Aug 29, 2011 at 12:15 AM, Glyn Alcock wrote:
Dear all,
I have a problem with Aggregate 1.0 rev. 3. I tried to upload a new
form from Aggregate, which failed, I think because there was already
an existing form with the same name (although the build id is
different). Now, when I login using my Google id the screen loops
between the main page and the submissions filter page several times
until a window appears: “Unable to retrieve users from server: 0”.
When I click ok or close it, it starts looping again. Therefore, I
cannot delete the duplicate form. The anonymous user login only has
permission to collect, and there are no other user-ids assigned to the
appspot.
Why does this happen and how can I fix it? I assumed that, since the
upload failed, the file would not have uploaded and no conflict
occurred (if this is the problem).
There is a long list of errors. I've copied and attached the first
(Critical) and the second (Error). The others are similar or the same. I had
fieldworkers piloting our survey yesterday, so many of these errors might be
when they tried to submit completed forms.
I appreciate you help with this. Sorry for the inconvenience, but I guess
these things can happen.
Regards,
Glyn
Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
and will be pushing beta 4 as soon as an openID error is solved that
is blocking the release. Hopefully the upcoming release will solve
most of your issues.
We appreciate everyone helping to test the betas as it's difficult for
the ODK team to catch everything. It is really helpful for users to
file issue reports on our google code site so we can track bugs in the
system so nothing gets lost. I create issue 311 and attached the logs
to the issue http://code.google.com/p/opendatakit/issues/detail?id=311
Cheers,
Waylon
···
On Mon, Aug 29, 2011 at 9:49 PM, wrote:
> Hi Mitch,
> There is a long list of errors. I've copied and attached the first
> (Critical) and the second (Error). The others are similar or the same. I had
> fieldworkers piloting our survey yesterday, so many of these errors might be
> when they tried to submit completed forms.
> I appreciate you help with this. Sorry for the inconvenience, but I guess
> these things can happen.
> Regards,
> Glyn
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
>
Thank you for reporting this issue. It was a regression. I think I fixed
all the edge cases for this in beta 4.
Beta 4 (just released) has a significant number of bug fixes and stability
fixes for GAE. I encourage you to upgrade.
Note that the upgrade path is harsh -- you have to either start fresh with a
new appspot instance or
manually delete all tables in the appspot instance you're reusing (you
should disable writes during this process).
If for some reason you need the data in this instance, go to https://appengine.google.com , choose your instance, and then choose
Administration Permissions and invite me (mitchellsundt@gmail.com) to
collaborate as an Owner. And also, tell me the form id of the form that
failed to load.
As a reminder, Betas should not be trusted for production data.
Mitch
···
On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette wrote:
Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
and will be pushing beta 4 as soon as an openID error is solved that
is blocking the release. Hopefully the upcoming release will solve
most of your issues.
We appreciate everyone helping to test the betas as it's difficult for
the ODK team to catch everything. It is really helpful for users to
file issue reports on our google code site so we can track bugs in the
system so nothing gets lost. I create issue 311 and attached the logs
to the issue http://code.google.com/p/opendatakit/issues/detail?id=311
Hi Mitch,
There is a long list of errors. I've copied and attached the first
(Critical) and the second (Error). The others are similar or the same. I
had
fieldworkers piloting our survey yesterday, so many of these errors might
be
when they tried to submit completed forms.
I appreciate you help with this. Sorry for the inconvenience, but I guess
these things can happen.
Regards,
Glyn
I am experiencing a repeat of a same problem as I had before (regression).
I was running Aggregate 1.0.3. I had a form with a couple of thousand
records in, which I exported and deleted so that I could upload an updated
form with the same name. Clearly I didn't wait long enough for the old form
to be completely removed before uploading the new one. When I tried to
upload the new form, I got an error message saying that the old form had
not been deleted. Before trying again, I upgraded to v 1.0.4. Now, when I
sign into my appspot, it gets stuck in a loop where it continuously
refreshes the screen. I am unable to do any operations on it.
···
On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
>
> Hi Glyn,
>
> Thank you for reporting this issue. It was a regression. I think I fixed
> all the edge cases for this in beta 4.
>
> Beta 4 (just released) has a significant number of bug fixes and stability
> fixes for GAE. I encourage you to upgrade.
>
> Note that the upgrade path is harsh -- you have to either start fresh with
> a new appspot instance or
> manually delete all tables in the appspot instance you're reusing (you
> should disable writes during this process).
>
> If for some reason you need the data in this instance, go to
> https://appengine.google.com , choose your instance, and then choose
> Administration Permissions and invite me (mitchellsundt@gmail.com) to
> collaborate as an Owner. And also, tell me the form id of the form that
> failed to load.
>
> As a reminder, Betas should not be trusted for production data.
>
> Mitch
>
> On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette wrote:
>
>> Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
>> and will be pushing beta 4 as soon as an openID error is solved that
>> is blocking the release. Hopefully the upcoming release will solve
>> most of your issues.
>>
>> We appreciate everyone helping to test the betas as it's difficult for
>> the ODK team to catch everything. It is really helpful for users to
>> file issue reports on our google code site so we can track bugs in the
>> system so nothing gets lost. I create issue 311 and attached the logs
>> to the issue
>> http://code.google.com/p/opendatakit/issues/detail?id=311
>>
>> Cheers,
>> Waylon
>>
>> On Mon, Aug 29, 2011 at 9:49 PM, wrote:
>> > Hi Mitch,
>> > There is a long list of errors. I've copied and attached the first
>> > (Critical) and the second (Error). The others are similar or the same.
>> I had
>> > fieldworkers piloting our survey yesterday, so many of these errors
>> might be
>> > when they tried to submit completed forms.
>> > I appreciate you help with this. Sorry for the inconvenience, but I
>> guess
>> > these things can happen.
>> > Regards,
>> > Glyn
>> >
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options: http://groups.google.com/group/opendatakit?hl=en
>> >
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> http://www.OpenDataKit.org
> University of Washington
> mitchellsundt@gmail.com
>
I should be able to resolve the issue by manually deleting a couple
extraneous rows from a table.
Mitch
···
On Mon, Mar 12, 2012 at 11:42 PM, Glyn wrote:
Hi Mitch,
I am experiencing a repeat of a same problem as I had before (regression).
I was running Aggregate 1.0.3. I had a form with a couple of thousand
records in, which I exported and deleted so that I could upload an updated
form with the same name. Clearly I didn't wait long enough for the old form
to be completely removed before uploading the new one. When I tried to
upload the new form, I got an error message saying that the old form had
not been deleted. Before trying again, I upgraded to v 1.0.4. Now, when I
sign into my appspot, it gets stuck in a loop where it continuously
refreshes the screen. I am unable to do any operations on it.
Attached are the error logs.
Please advise.
Thanks,
Glyn
On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
Hi Glyn,
Thank you for reporting this issue. It was a regression. I think I
fixed all the edge cases for this in beta 4.
Beta 4 (just released) has a significant number of bug fixes and
stability fixes for GAE. I encourage you to upgrade.
Note that the upgrade path is harsh -- you have to either start fresh
with a new appspot instance or
manually delete all tables in the appspot instance you're reusing (you
should disable writes during this process).
If for some reason you need the data in this instance, go to https://appengine.google.com , choose your instance, and then choose
Administration Permissions and invite me (mitchellsundt@gmail.com) to
collaborate as an Owner. And also, tell me the form id of the form that
failed to load.
As a reminder, Betas should not be trusted for production data.
Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
and will be pushing beta 4 as soon as an openID error is solved that
is blocking the release. Hopefully the upcoming release will solve
most of your issues.
Hi Mitch,
There is a long list of errors. I've copied and attached the first
(Critical) and the second (Error). The others are similar or the same.
I had
fieldworkers piloting our survey yesterday, so many of these errors
might be
when they tried to submit completed forms.
I appreciate you help with this. Sorry for the inconvenience, but I
guess
these things can happen.
Regards,
Glyn
Thank you very much for your help in solving this problem. I uploaded both
of our forms to Aggregate (strangely, I had to delete one before the other
would upload - it said it still existed) and our enumerators were able to
go to the field to start phase II of our large baseline. For your
information, we finished phase I last week, which involved completing a
pretty big questionnaire with 6000+ households in Mumbai slum areas. We did
everything with ODK with no prior experience of electronic data collection.
A big thanks to you all for your efforts and ingenuity!
Regards,
Glyn
···
On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
>
> Hi Glyn,
>
> This isn't the same issue as earlier, though it has the same
> manifestation. The actual issue you're having is either open issue 505 or
> 506.
>
> Can you invite me ( mitchellsundt@gmail.com ) as a Developer to your
> appengine instance (and send me-mail with the instance name, so I can
> correlate the invite with your issue). See
> http://code.google.com/p/opendatakit/wiki/AppEngineTroubleshooting
>
> I should be able to resolve the issue by manually deleting a couple
> extraneous rows from a table.
>
> Mitch
>
> On Mon, Mar 12, 2012 at 11:42 PM, Glyn wrote:
>
>> Hi Mitch,
>>
>> I am experiencing a repeat of a same problem as I had before
>> (regression). I was running Aggregate 1.0.3. I had a form with a couple of
>> thousand records in, which I exported and deleted so that I could upload an
>> updated form with the same name. Clearly I didn't wait long enough for the
>> old form to be completely removed before uploading the new one. When I
>> tried to upload the new form, I got an error message saying that the old
>> form had not been deleted. Before trying again, I upgraded to v 1.0.4. Now,
>> when I sign into my appspot, it gets stuck in a loop where it continuously
>> refreshes the screen. I am unable to do any operations on it.
>>
>> Attached are the error logs.
>>
>> Please advise.
>> Thanks,
>> Glyn
>>
>>
>> On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
>>>
>>> Hi Glyn,
>>>
>>> Thank you for reporting this issue. It was a regression. I think I
>>> fixed all the edge cases for this in beta 4.
>>>
>>> Beta 4 (just released) has a significant number of bug fixes and
>>> stability fixes for GAE. I encourage you to upgrade.
>>>
>>> Note that the upgrade path is harsh -- you have to either start fresh
>>> with a new appspot instance or
>>> manually delete all tables in the appspot instance you're reusing (you
>>> should disable writes during this process).
>>>
>>> If for some reason you need the data in this instance, go to
>>> https://appengine.google.com , choose your instance, and then choose
>>> Administration Permissions and invite me (mitchellsundt@gmail.com) to
>>> collaborate as an Owner. And also, tell me the form id of the form that
>>> failed to load.
>>>
>>> As a reminder, Betas should not be trusted for production data.
>>>
>>> Mitch
>>>
>>> On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette wrote:
>>>
>>>> Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
>>>> and will be pushing beta 4 as soon as an openID error is solved that
>>>> is blocking the release. Hopefully the upcoming release will solve
>>>> most of your issues.
>>>>
>>>> We appreciate everyone helping to test the betas as it's difficult for
>>>> the ODK team to catch everything. It is really helpful for users to
>>>> file issue reports on our google code site so we can track bugs in the
>>>> system so nothing gets lost. I create issue 311 and attached the logs
>>>> to the issue
>>>> http://code.google.com/p/**opendatakit/issues/detail?id=**311
>>>>
>>>> Cheers,
>>>> Waylon
>>>>
>>>> On Mon, Aug 29, 2011 at 9:49 PM, wrote:
>>>> > Hi Mitch,
>>>> > There is a long list of errors. I've copied and attached the first
>>>> > (Critical) and the second (Error). The others are similar or the
>>>> same. I had
>>>> > fieldworkers piloting our survey yesterday, so many of these errors
>>>> might be
>>>> > when they tried to submit completed forms.
>>>> > I appreciate you help with this. Sorry for the inconvenience, but I
>>>> guess
>>>> > these things can happen.
>>>> > Regards,
>>>> > Glyn
>>>> >
>>>> > --
>>>> > Post: opendatakit@googlegroups.com
>>>> > Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> > Options: http://groups.google.com/**group/opendatakit?hl=en
>>>> >
>>>>
>>>> --
>>>> Post: opendatakit@googlegroups.com
>>>> Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>>
>>>
>>>
>>>
>>> --
>>> Mitch Sundt
>>> Software Engineer
>>> http://www.OpenDataKit.org
>>> University of Washington
>>> mitchellsundt@gmail.com
>>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
Congrats on finishing your Phase 1! If you'd like to share your
experiences in a blog post on the ODK website, just let us know. I
think others could learn from how you managed to survey that many
households.
Yaw
···
On Wed, Mar 14, 2012 at 11:03, Glyn wrote:
> Hi Mitch
>
> Thank you very much for your help in solving this problem. I uploaded both
> of our forms to Aggregate (strangely, I had to delete one before the other
> would upload - it said it still existed) and our enumerators were able to go
> to the field to start phase II of our large baseline. For your information,
> we finished phase I last week, which involved completing a pretty big
> questionnaire with 6000+ households in Mumbai slum areas. We did everything
> with ODK with no prior experience of electronic data collection. A big
> thanks to you all for your efforts and ingenuity!
>
> Regards,
> Glyn
>
>
> On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
>>
>> Hi Glyn,
>>
>> This isn't the same issue as earlier, though it has the same
>> manifestation. The actual issue you're having is either open issue 505 or
>> 506.
>>
>> Can you invite me ( mitchellsundt@gmail.com ) as a Developer to your
>> appengine instance (and send me-mail with the instance name, so I can
>> correlate the invite with your issue). See
>> http://code.google.com/p/opendatakit/wiki/AppEngineTroubleshooting
>>
>> I should be able to resolve the issue by manually deleting a couple
>> extraneous rows from a table.
>>
>> Mitch
>>
>> On Mon, Mar 12, 2012 at 11:42 PM, Glyn wrote:
>>>
>>> Hi Mitch,
>>>
>>> I am experiencing a repeat of a same problem as I had before
>>> (regression). I was running Aggregate 1.0.3. I had a form with a couple of
>>> thousand records in, which I exported and deleted so that I could upload an
>>> updated form with the same name. Clearly I didn't wait long enough for the
>>> old form to be completely removed before uploading the new one. When I tried
>>> to upload the new form, I got an error message saying that the old form had
>>> not been deleted. Before trying again, I upgraded to v 1.0.4. Now, when I
>>> sign into my appspot, it gets stuck in a loop where it continuously
>>> refreshes the screen. I am unable to do any operations on it.
>>>
>>> Attached are the error logs.
>>>
>>> Please advise.
>>> Thanks,
>>> Glyn
>>>
>>>
>>> On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
>>>>
>>>> Hi Glyn,
>>>>
>>>> Thank you for reporting this issue. It was a regression. I think I
>>>> fixed all the edge cases for this in beta 4.
>>>>
>>>> Beta 4 (just released) has a significant number of bug fixes and
>>>> stability fixes for GAE. I encourage you to upgrade.
>>>>
>>>> Note that the upgrade path is harsh -- you have to either start fresh
>>>> with a new appspot instance or
>>>> manually delete all tables in the appspot instance you're reusing (you
>>>> should disable writes during this process).
>>>>
>>>> If for some reason you need the data in this instance, go to
>>>> https://appengine.google.com , choose your instance, and then choose
>>>> Administration Permissions and invite me (mitchellsundt@gmail.com) to
>>>> collaborate as an Owner. And also, tell me the form id of the form that
>>>> failed to load.
>>>>
>>>> As a reminder, Betas should not be trusted for production data.
>>>>
>>>> Mitch
>>>>
>>>> On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette wrote:
>>>>>
>>>>> Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
>>>>> and will be pushing beta 4 as soon as an openID error is solved that
>>>>> is blocking the release. Hopefully the upcoming release will solve
>>>>> most of your issues.
>>>>>
>>>>> We appreciate everyone helping to test the betas as it's difficult for
>>>>> the ODK team to catch everything. It is really helpful for users to
>>>>> file issue reports on our google code site so we can track bugs in the
>>>>> system so nothing gets lost. I create issue 311 and attached the logs
>>>>> to the issue
>>>>> http://code.google.com/p/opendatakit/issues/detail?id=311
>>>>>
>>>>> Cheers,
>>>>> Waylon
>>>>>
>>>>> On Mon, Aug 29, 2011 at 9:49 PM, wrote:
>>>>> > Hi Mitch,
>>>>> > There is a long list of errors. I've copied and attached the first
>>>>> > (Critical) and the second (Error). The others are similar or the
>>>>> > same. I had
>>>>> > fieldworkers piloting our survey yesterday, so many of these errors
>>>>> > might be
>>>>> > when they tried to submit completed forms.
>>>>> > I appreciate you help with this. Sorry for the inconvenience, but I
>>>>> > guess
>>>>> > these things can happen.
>>>>> > Regards,
>>>>> > Glyn
>>>>> >
>>>>> > --
>>>>> > Post: opendatakit@googlegroups.com
>>>>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>>>> >
>>>>>
>>>>> --
>>>>> Post: opendatakit@googlegroups.com
>>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Mitch Sundt
>>>> Software Engineer
>>>> http://www.OpenDataKit.org
>>>> University of Washington
>>>> mitchellsundt@gmail.com
>>>
>>> --
>>> Post: opendatakit@googlegroups.com
>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitchellsundt@gmail.com
>
> --
> Post: opendatakit@googlegroups.com
> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
> Options: http://groups.google.com/group/opendatakit?hl=en
Were you using the instance I unstuck? And was it running 1.0.4 during the
survey?
If so, could I share general billing stats with the community?
I would like to provide guidance as to real-world billing charges for large
surveys.
Mitch
···
On Wed, Mar 14, 2012 at 8:18 AM, Yaw Anokwa wrote:
Glyn,
Congrats on finishing your Phase 1! If you'd like to share your
experiences in a blog post on the ODK website, just let us know. I
think others could learn from how you managed to survey that many
households.
Thank you very much for your help in solving this problem. I uploaded
both
of our forms to Aggregate (strangely, I had to delete one before the
other
would upload - it said it still existed) and our enumerators were able
to go
to the field to start phase II of our large baseline. For your
information,
we finished phase I last week, which involved completing a pretty big
questionnaire with 6000+ households in Mumbai slum areas. We did
everything
with ODK with no prior experience of electronic data collection. A big
thanks to you all for your efforts and ingenuity!
Regards,
Glyn
On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
Hi Glyn,
This isn't the same issue as earlier, though it has the same
manifestation. The actual issue you're having is either open issue 505
or
506.
I am experiencing a repeat of a same problem as I had before
(regression). I was running Aggregate 1.0.3. I had a form with a
couple of
thousand records in, which I exported and deleted so that I could
upload an
updated form with the same name. Clearly I didn't wait long enough for
the
old form to be completely removed before uploading the new one. When I
tried
to upload the new form, I got an error message saying that the old
form had
not been deleted. Before trying again, I upgraded to v 1.0.4. Now,
when I
sign into my appspot, it gets stuck in a loop where it continuously
refreshes the screen. I am unable to do any operations on it.
Attached are the error logs.
Please advise.
Thanks,
Glyn
On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
Hi Glyn,
Thank you for reporting this issue. It was a regression. I think I
fixed all the edge cases for this in beta 4.
Beta 4 (just released) has a significant number of bug fixes and
stability fixes for GAE. I encourage you to upgrade.
Note that the upgrade path is harsh -- you have to either start fresh
with a new appspot instance or
manually delete all tables in the appspot instance you're reusing (you
should disable writes during this process).
If for some reason you need the data in this instance, go to https://appengine.google.com , choose your instance, and then choose
Administration Permissions and invite me (mitchellsundt@gmail.com) to
collaborate as an Owner. And also, tell me the form id of the form
that
failed to load.
As a reminder, Betas should not be trusted for production data.
Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
and will be pushing beta 4 as soon as an openID error is solved that
is blocking the release. Hopefully the upcoming release will solve
most of your issues.
We appreciate everyone helping to test the betas as it's difficult
for
the ODK team to catch everything. It is really helpful for users to
file issue reports on our google code site so we can track bugs in
the
system so nothing gets lost. I create issue 311 and attached the logs
to the issue http://code.google.com/p/opendatakit/issues/detail?id=311
Hi Mitch,
There is a long list of errors. I've copied and attached the first
(Critical) and the second (Error). The others are similar or the
same. I had
fieldworkers piloting our survey yesterday, so many of these errors
might be
when they tried to submit completed forms.
I appreciate you help with this. Sorry for the inconvenience, but I
guess
these things can happen.
Regards,
Glyn
Yes, it was the same instance that you unstuck. We use 2 forms: a baseline
and a child anthropometry one. I got the original error when I deleted the
existing baseline (there were probably 2000+ records in it ) and tried to
upload the new one. The anthro form did not return an error. After you
fixed it, the baseline had gone but the anthro was there. I could not
upload the baseline until I removed the anthro (it returned an error, "form
already exists", even though it was different).
Yes, you can share billing stats with the community as long as everything
is confidential. I assume you still need the permissions I set up for you
to do this? When done, please let me know so that I can reset them.
Yaw, at some point yes, it would be good for us to share our experiences of
setting up a large survey with ODK.
Regards,
Glyn
···
On Wednesday, March 14, 2012 10:28:58 PM UTC+5:30, Mitch wrote:
>
> Were you using the instance I unstuck? And was it running 1.0.4 during
> the survey?
>
> If so, could I share general billing stats with the community?
>
> I would like to provide guidance as to real-world billing charges for
> large surveys.
>
> Mitch
>
> On Wed, Mar 14, 2012 at 8:18 AM, Yaw Anokwa wrote:
>
>> Glyn,
>>
>> Congrats on finishing your Phase 1! If you'd like to share your
>> experiences in a blog post on the ODK website, just let us know. I
>> think others could learn from how you managed to survey that many
>> households.
>>
>> Yaw
>>
>> On Wed, Mar 14, 2012 at 11:03, Glyn wrote:
>> > Hi Mitch
>> >
>> > Thank you very much for your help in solving this problem. I uploaded
>> both
>> > of our forms to Aggregate (strangely, I had to delete one before the
>> other
>> > would upload - it said it still existed) and our enumerators were able
>> to go
>> > to the field to start phase II of our large baseline. For your
>> information,
>> > we finished phase I last week, which involved completing a pretty big
>> > questionnaire with 6000+ households in Mumbai slum areas. We did
>> everything
>> > with ODK with no prior experience of electronic data collection. A big
>> > thanks to you all for your efforts and ingenuity!
>> >
>> > Regards,
>> > Glyn
>> >
>> >
>> > On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
>> >>
>> >> Hi Glyn,
>> >>
>> >> This isn't the same issue as earlier, though it has the same
>> >> manifestation. The actual issue you're having is either open issue
>> 505 or
>> >> 506.
>> >>
>> >> Can you invite me ( mitchellsundt@gmail.com ) as a Developer to your
>> >> appengine instance (and send me-mail with the instance name, so I can
>> >> correlate the invite with your issue). See
>> >> http://code.google.com/p/opendatakit/wiki/AppEngineTroubleshooting
>> >>
>> >> I should be able to resolve the issue by manually deleting a couple
>> >> extraneous rows from a table.
>> >>
>> >> Mitch
>> >>
>> >> On Mon, Mar 12, 2012 at 11:42 PM, Glyn wrote:
>> >>>
>> >>> Hi Mitch,
>> >>>
>> >>> I am experiencing a repeat of a same problem as I had before
>> >>> (regression). I was running Aggregate 1.0.3. I had a form with a
>> couple of
>> >>> thousand records in, which I exported and deleted so that I could
>> upload an
>> >>> updated form with the same name. Clearly I didn't wait long enough
>> for the
>> >>> old form to be completely removed before uploading the new one. When
>> I tried
>> >>> to upload the new form, I got an error message saying that the old
>> form had
>> >>> not been deleted. Before trying again, I upgraded to v 1.0.4. Now,
>> when I
>> >>> sign into my appspot, it gets stuck in a loop where it continuously
>> >>> refreshes the screen. I am unable to do any operations on it.
>> >>>
>> >>> Attached are the error logs.
>> >>>
>> >>> Please advise.
>> >>> Thanks,
>> >>> Glyn
>> >>>
>> >>>
>> >>> On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
>> >>>>
>> >>>> Hi Glyn,
>> >>>>
>> >>>> Thank you for reporting this issue. It was a regression. I think I
>> >>>> fixed all the edge cases for this in beta 4.
>> >>>>
>> >>>> Beta 4 (just released) has a significant number of bug fixes and
>> >>>> stability fixes for GAE. I encourage you to upgrade.
>> >>>>
>> >>>> Note that the upgrade path is harsh -- you have to either start fresh
>> >>>> with a new appspot instance or
>> >>>> manually delete all tables in the appspot instance you're reusing
>> (you
>> >>>> should disable writes during this process).
>> >>>>
>> >>>> If for some reason you need the data in this instance, go to
>> >>>> https://appengine.google.com , choose your instance, and then choose
>> >>>> Administration Permissions and invite me (mitchellsundt@gmail.com)
>> to
>> >>>> collaborate as an Owner. And also, tell me the form id of the form
>> that
>> >>>> failed to load.
>> >>>>
>> >>>> As a reminder, Betas should not be trusted for production data.
>> >>>>
>> >>>> Mitch
>> >>>>
>> >>>> On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette wrote:
>> >>>>>
>> >>>>> Overall, the ODK team is aware of a list of bugs in Aggregate beta 3
>> >>>>> and will be pushing beta 4 as soon as an openID error is solved that
>> >>>>> is blocking the release. Hopefully the upcoming release will solve
>> >>>>> most of your issues.
>> >>>>>
>> >>>>> We appreciate everyone helping to test the betas as it's difficult
>> for
>> >>>>> the ODK team to catch everything. It is really helpful for users to
>> >>>>> file issue reports on our google code site so we can track bugs in
>> the
>> >>>>> system so nothing gets lost. I create issue 311 and attached the
>> logs
>> >>>>> to the issue
>> >>>>> http://code.google.com/p/opendatakit/issues/detail?id=311
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Waylon
>> >>>>>
>> >>>>> On Mon, Aug 29, 2011 at 9:49 PM, wrote:
>> >>>>> > Hi Mitch,
>> >>>>> > There is a long list of errors. I've copied and attached the first
>> >>>>> > (Critical) and the second (Error). The others are similar or the
>> >>>>> > same. I had
>> >>>>> > fieldworkers piloting our survey yesterday, so many of these
>> errors
>> >>>>> > might be
>> >>>>> > when they tried to submit completed forms.
>> >>>>> > I appreciate you help with this. Sorry for the inconvenience, but
>> I
>> >>>>> > guess
>> >>>>> > these things can happen.
>> >>>>> > Regards,
>> >>>>> > Glyn
>> >>>>> >
>> >>>>> > --
>> >>>>> > Post: opendatakit@googlegroups.com
>> >>>>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>>>> > Options: http://groups.google.com/group/opendatakit?hl=en
>> >>>>> >
>> >>>>>
>> >>>>> --
>> >>>>> Post: opendatakit@googlegroups.com
>> >>>>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>>>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Mitch Sundt
>> >>>> Software Engineer
>> >>>> http://www.OpenDataKit.org
>> >>>> University of Washington
>> >>>> mitchellsundt@gmail.com
>> >>>
>> >>> --
>> >>> Post: opendatakit@googlegroups.com
>> >>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> >>> Options: http://groups.google.com/group/opendatakit?hl=en
>> >>
>> >>
>> >>
>> >>
>> >> --
>> >> Mitch Sundt
>> >> Software Engineer
>> >> University of Washington
>> >> mitchellsundt@gmail.com
>> >
>> > --
>> > Post: opendatakit@googlegroups.com
>> > Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> > Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>
Yes, it was the same instance that you unstuck. We use 2 forms: a baseline
and a child anthropometry one. I got the original error when I deleted the
existing baseline (there were probably 2000+ records in it ) and tried to
upload the new one. The anthro form did not return an error. After you
fixed it, the baseline had gone but the anthro was there. I could not
upload the baseline until I removed the anthro (it returned an error, "form
already exists", even though it was different).
Yes, you can share billing stats with the community as long as everything
is confidential. I assume you still need the permissions I set up for you
to do this? When done, please let me know so that I can reset them.
Yaw, at some point yes, it would be good for us to share our experiences
of setting up a large survey with ODK.
Regards,
Glyn
On Wednesday, March 14, 2012 10:28:58 PM UTC+5:30, Mitch wrote:
Were you using the instance I unstuck? And was it running 1.0.4 during
the survey?
If so, could I share general billing stats with the community?
I would like to provide guidance as to real-world billing charges for
large surveys.
Mitch
On Wed, Mar 14, 2012 at 8:18 AM, Yaw Anokwa yanokwa@gmail.com wrote:
Glyn,
Congrats on finishing your Phase 1! If you'd like to share your
experiences in a blog post on the ODK website, just let us know. I
think others could learn from how you managed to survey that many
households.
Thank you very much for your help in solving this problem. I uploaded
both
of our forms to Aggregate (strangely, I had to delete one before the
other
would upload - it said it still existed) and our enumerators were able
to go
to the field to start phase II of our large baseline. For your
information,
we finished phase I last week, which involved completing a pretty big
questionnaire with 6000+ households in Mumbai slum areas. We did
everything
with ODK with no prior experience of electronic data collection. A big
thanks to you all for your efforts and ingenuity!
Regards,
Glyn
On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
Hi Glyn,
This isn't the same issue as earlier, though it has the same
manifestation. The actual issue you're having is either open issue
505 or
506.
I am experiencing a repeat of a same problem as I had before
(regression). I was running Aggregate 1.0.3. I had a form with a
couple of
thousand records in, which I exported and deleted so that I could
upload an
updated form with the same name. Clearly I didn't wait long enough
for the
old form to be completely removed before uploading the new one. When
I tried
to upload the new form, I got an error message saying that the old
form had
not been deleted. Before trying again, I upgraded to v 1.0.4. Now,
when I
sign into my appspot, it gets stuck in a loop where it continuously
refreshes the screen. I am unable to do any operations on it.
Attached are the error logs.
Please advise.
Thanks,
Glyn
On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
Hi Glyn,
Thank you for reporting this issue. It was a regression. I think I
fixed all the edge cases for this in beta 4.
Beta 4 (just released) has a significant number of bug fixes and
stability fixes for GAE. I encourage you to upgrade.
Note that the upgrade path is harsh -- you have to either start
fresh
with a new appspot instance or
manually delete all tables in the appspot instance you're reusing
(you
should disable writes during this process).
If for some reason you need the data in this instance, go to https://appengine.google.com , choose your instance, and then
choose
Administration Permissions and invite me (mitchellsundt@gmail.com)
to
collaborate as an Owner. And also, tell me the form id of the form
that
failed to load.
As a reminder, Betas should not be trusted for production data.
Overall, the ODK team is aware of a list of bugs in Aggregate beta
3
and will be pushing beta 4 as soon as an openID error is solved
that
is blocking the release. Hopefully the upcoming release will solve
most of your issues.
Hi Mitch,
There is a long list of errors. I've copied and attached the
first
(Critical) and the second (Error). The others are similar or the
same. I had
fieldworkers piloting our survey yesterday, so many of these
errors
might be
when they tried to submit completed forms.
I appreciate you help with this. Sorry for the inconvenience,
but I
guess
these things can happen.
Regards,
Glyn
We started data collection on 01 September 2011 and completed about 6000 hh
at the end of Feb 2012
Glyn
···
On Thursday, March 15, 2012 9:13:52 PM UTC+5:30, Mitch wrote:
>
> When did the study begin & end?
>
> Mitch
>
> On Wed, Mar 14, 2012 at 9:37 PM, Glyn wrote:
>
>> Hi Mitch,
>>
>> Yes, it was the same instance that you unstuck. We use 2 forms: a
>> baseline and a child anthropometry one. I got the original error when I
>> deleted the existing baseline (there were probably 2000+ records in it )
>> and tried to upload the new one. The anthro form did not return an error.
>> After you fixed it, the baseline had gone but the anthro was there. I could
>> not upload the baseline until I removed the anthro (it returned an error,
>> "form already exists", even though it was different).
>>
>> Yes, you can share billing stats with the community as long as everything
>> is confidential. I assume you still need the permissions I set up for you
>> to do this? When done, please let me know so that I can reset them.
>>
>> Yaw, at some point yes, it would be good for us to share our experiences
>> of setting up a large survey with ODK.
>>
>> Regards,
>> Glyn
>>
>>
>> On Wednesday, March 14, 2012 10:28:58 PM UTC+5:30, Mitch wrote:
>>>
>>> Were you using the instance I unstuck? And was it running 1.0.4 during
>>> the survey?
>>>
>>> If so, could I share general billing stats with the community?
>>>
>>> I would like to provide guidance as to real-world billing charges for
>>> large surveys.
>>>
>>> Mitch
>>>
>>> On Wed, Mar 14, 2012 at 8:18 AM, Yaw Anokwa wrote:
>>>
>>>> Glyn,
>>>>
>>>> Congrats on finishing your Phase 1! If you'd like to share your
>>>> experiences in a blog post on the ODK website, just let us know. I
>>>> think others could learn from how you managed to survey that many
>>>> households.
>>>>
>>>> Yaw
>>>>
>>>> On Wed, Mar 14, 2012 at 11:03, Glyn wrote:
>>>> > Hi Mitch
>>>> >
>>>> > Thank you very much for your help in solving this problem. I uploaded
>>>> both
>>>> > of our forms to Aggregate (strangely, I had to delete one before the
>>>> other
>>>> > would upload - it said it still existed) and our enumerators were
>>>> able to go
>>>> > to the field to start phase II of our large baseline. For your
>>>> information,
>>>> > we finished phase I last week, which involved completing a pretty big
>>>> > questionnaire with 6000+ households in Mumbai slum areas. We did
>>>> everything
>>>> > with ODK with no prior experience of electronic data collection. A big
>>>> > thanks to you all for your efforts and ingenuity!
>>>> >
>>>> > Regards,
>>>> > Glyn
>>>> >
>>>> >
>>>> > On Tuesday, March 13, 2012 9:16:28 PM UTC+5:30, Mitch wrote:
>>>> >>
>>>> >> Hi Glyn,
>>>> >>
>>>> >> This isn't the same issue as earlier, though it has the same
>>>> >> manifestation. The actual issue you're having is either open issue
>>>> 505 or
>>>> >> 506.
>>>> >>
>>>> >> Can you invite me ( mitchellsundt@gmail.com ) as a Developer to your
>>>> >> appengine instance (and send me-mail with the instance name, so I can
>>>> >> correlate the invite with your issue). See
>>>> >> http://code.google.com/p/**opendatakit/wiki/**
>>>> AppEngineTroubleshooting
>>>> >>
>>>> >> I should be able to resolve the issue by manually deleting a couple
>>>> >> extraneous rows from a table.
>>>> >>
>>>> >> Mitch
>>>> >>
>>>> >> On Mon, Mar 12, 2012 at 11:42 PM, Glyn wrote:
>>>> >>>
>>>> >>> Hi Mitch,
>>>> >>>
>>>> >>> I am experiencing a repeat of a same problem as I had before
>>>> >>> (regression). I was running Aggregate 1.0.3. I had a form with a
>>>> couple of
>>>> >>> thousand records in, which I exported and deleted so that I could
>>>> upload an
>>>> >>> updated form with the same name. Clearly I didn't wait long enough
>>>> for the
>>>> >>> old form to be completely removed before uploading the new one.
>>>> When I tried
>>>> >>> to upload the new form, I got an error message saying that the old
>>>> form had
>>>> >>> not been deleted. Before trying again, I upgraded to v 1.0.4. Now,
>>>> when I
>>>> >>> sign into my appspot, it gets stuck in a loop where it continuously
>>>> >>> refreshes the screen. I am unable to do any operations on it.
>>>> >>>
>>>> >>> Attached are the error logs.
>>>> >>>
>>>> >>> Please advise.
>>>> >>> Thanks,
>>>> >>> Glyn
>>>> >>>
>>>> >>>
>>>> >>> On Wednesday, August 31, 2011 5:24:37 AM UTC+5:30, Mitch Sundt wrote:
>>>> >>>>
>>>> >>>> Hi Glyn,
>>>> >>>>
>>>> >>>> Thank you for reporting this issue. It was a regression. I think
>>>> I
>>>> >>>> fixed all the edge cases for this in beta 4.
>>>> >>>>
>>>> >>>> Beta 4 (just released) has a significant number of bug fixes and
>>>> >>>> stability fixes for GAE. I encourage you to upgrade.
>>>> >>>>
>>>> >>>> Note that the upgrade path is harsh -- you have to either start
>>>> fresh
>>>> >>>> with a new appspot instance or
>>>> >>>> manually delete all tables in the appspot instance you're reusing
>>>> (you
>>>> >>>> should disable writes during this process).
>>>> >>>>
>>>> >>>> If for some reason you need the data in this instance, go to
>>>> >>>> https://appengine.google.com , choose your instance, and then
>>>> choose
>>>> >>>> Administration Permissions and invite me (mitchellsundt@gmail.com)
>>>> to
>>>> >>>> collaborate as an Owner. And also, tell me the form id of the
>>>> form that
>>>> >>>> failed to load.
>>>> >>>>
>>>> >>>> As a reminder, Betas should not be trusted for production data.
>>>> >>>>
>>>> >>>> Mitch
>>>> >>>>
>>>> >>>> On Mon, Aug 29, 2011 at 10:34 PM, W. Brunette >>> >>>>>
>>>> >>>>> Overall, the ODK team is aware of a list of bugs in Aggregate
>>>> beta 3
>>>> >>>>> and will be pushing beta 4 as soon as an openID error is solved
>>>> that
>>>> >>>>> is blocking the release. Hopefully the upcoming release will solve
>>>> >>>>> most of your issues.
>>>> >>>>>
>>>> >>>>> We appreciate everyone helping to test the betas as it's
>>>> difficult for
>>>> >>>>> the ODK team to catch everything. It is really helpful for users
>>>> to
>>>> >>>>> file issue reports on our google code site so we can track bugs
>>>> in the
>>>> >>>>> system so nothing gets lost. I create issue 311 and attached the
>>>> logs
>>>> >>>>> to the issue
>>>> >>>>> http://code.google.com/p/**opendatakit/issues/detail?id=**311
>>>> >>>>>
>>>> >>>>> Cheers,
>>>> >>>>> Waylon
>>>> >>>>>
>>>> >>>>> On Mon, Aug 29, 2011 at 9:49 PM, wrote:
>>>> >>>>> > Hi Mitch,
>>>> >>>>> > There is a long list of errors. I've copied and attached the
>>>> first
>>>> >>>>> > (Critical) and the second (Error). The others are similar or the
>>>> >>>>> > same. I had
>>>> >>>>> > fieldworkers piloting our survey yesterday, so many of these
>>>> errors
>>>> >>>>> > might be
>>>> >>>>> > when they tried to submit completed forms.
>>>> >>>>> > I appreciate you help with this. Sorry for the inconvenience,
>>>> but I
>>>> >>>>> > guess
>>>> >>>>> > these things can happen.
>>>> >>>>> > Regards,
>>>> >>>>> > Glyn
>>>> >>>>> >
>>>> >>>>> > --
>>>> >>>>> > Post: opendatakit@googlegroups.com
>>>> >>>>> > Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> >>>>> > Options: http://groups.google.com/**group/opendatakit?hl=en
>>>> >>>>> >
>>>> >>>>>
>>>> >>>>> --
>>>> >>>>> Post: opendatakit@googlegroups.com
>>>> >>>>> Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> >>>>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>>
>>>> >>>> --
>>>> >>>> Mitch Sundt
>>>> >>>> Software Engineer
>>>> >>>> http://www.OpenDataKit.org
>>>> >>>> University of Washington
>>>> >>>> mitchellsundt@gmail.com
>>>> >>>
>>>> >>> --
>>>> >>> Post: opendatakit@googlegroups.com
>>>> >>> Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> >>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>> >>
>>>> >>
>>>> >>
>>>> >>
>>>> >> --
>>>> >> Mitch Sundt
>>>> >> Software Engineer
>>>> >> University of Washington
>>>> >> mitchellsundt@gmail.com
>>>> >
>>>> > --
>>>> > Post: opendatakit@googlegroups.com
>>>> > Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> > Options: http://groups.google.com/**group/opendatakit?hl=en
>>>>
>>>> --
>>>> Post: opendatakit@googlegroups.com
>>>> Unsubscribe: opendatakit+unsubscribe@**googlegroups.com
>>>> Options: http://groups.google.com/**group/opendatakit?hl=en
>>>>
>>>
>>>
>>>
>>> --
>>> Mitch Sundt
>>> Software Engineer
>>> University of Washington
>>> mitchellsundt@gmail.com
>>>
>> --
>> Post: opendatakit@googlegroups.com
>> Unsubscribe: opendatakit+unsubscribe@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>
>
>
> --
> Mitch Sundt
> Software Engineer
> University of Washington
> mitchellsundt@gmail.com
>