Uploading trouble; File already exists.....

22 views
Skip to first unread message

Planetary Paul

unread,
Oct 30, 2016, 5:36:10 AM10/30/16
to Safecast Device Discussions and Support
I'm in the process of uploading and submitting my latest batch and with the second file I hit a snag. 

The system reports: "File '27251024.LOG' already exists"

When I go to see it, I get: "Bgeigie Import #10831128.LOG", "Title: bGeigie Import #23594" from fellow volunteer Bordois Valéry.

I tried several times, rebooted my browser, deleted caches, renamed the file to "27251024b.LOG", renamed the file to "27251023.LOG", but nothing goes. 

The next file imports without a hitch.

Any solution to this? I'd hate to have to ditch my data. It also might indicate a bug that maybe could bite someone else in the future......

Kalin KOZHUHAROV (Safecast)

unread,
Oct 30, 2016, 9:34:00 AM10/30/16
to Planetary Paul, Safecast Device Discussions and Support
Hello,

On Sun, Oct 30, 2016 at 6:36 PM, Planetary Paul
<planeten...@mac.com> wrote:
> I'm in the process of uploading and submitting my latest batch and with the
> second file I hit a snag.
>
> The system reports: "File '27251024.LOG' already exists"
>
> When I go to see it, I get: "Bgeigie Import #10831128.LOG", "Title: bGeigie
> Import #23594" from fellow volunteer Bordois Valéry.
>
> I tried several times, rebooted my browser, deleted caches, renamed the file
> to "27251024b.LOG", renamed the file to "27251023.LOG", but nothing goes.
>
I am not really sure what is going on, please send me (not to the
list) the file, and the link you are given, so I can check.

Just FIY, the system checks the contents of the file, so renaming it
has no meaning.
Here is the relevant code AFAIK,
https://github.com/Safecast/safecastapi/blob/2af8da3a32d1c6549c31ba1d793db3eafee3fa32/app/views/bgeigie_imports/new.html.erb#L7

You can trick the system by adding a new line (to change the contents
=> MD5), but then you'll hit next check when each record is being
MD5sum-ed and your file will have 0 records.

Kalin.

Sean Bonner, Safecast

unread,
Oct 30, 2016, 2:34:38 PM10/30/16
to Planetary Paul, Safecast Device Discussions and Support
Hi Paul-

That error is used when the data in a log is already in the system, the naming convention isn’t used and in fact renaming it and uploading it again just compounds the issue since you keep uploading the same file again and again. The two likely options are either you (or someone else) uploaded it previously and it just got mixed up in a batch, or it’s sitting in your “processed” logs waiting for you to add metadata and submit, definitely check your account logs and see if there is anything in holding there…

-s


Sean Bonner

Co-Founder, Director of Global Operations

Safecast.org | pgp key

signature.asc

Planetary Paul

unread,
Oct 30, 2016, 5:07:57 PM10/30/16
to Safecast Device Discussions and Support, planeten...@mac.com
I just noticed the size of the file is way too small, 43 bytes, and it has only three lines in it:

# NEW LOG
# format=1.3.4nano
# deadtime=on

So it's a dud and I assume that's what caused the confusion at upload.

Next time I'll check sizes before raising flags ;-).

Kalin KOZHUHAROV (Safecast)

unread,
Oct 30, 2016, 8:50:44 PM10/30/16
to Planetary Paul, Safecast Device Discussions and Support
On Mon, Oct 31, 2016 at 6:07 AM, Planetary Paul
<planeten...@mac.com> wrote:
> I just noticed the size of the file is way too small, 43 bytes, and it has
> only three lines in it:
>
> # NEW LOG
> # format=1.3.4nano
> # deadtime=on
>
> So it's a dud and I assume that's what caused the confusion at upload.
>
Yep that explains why it was rejected - someone has tried to upload
blank file before :-)

Kalin.
Reply all
Reply to author
Forward
0 new messages