search

ccseer / Seer

Seer bug report
http://1218.io
451 stars 45 forks source link

Using Seer seems to lead to permission errors when re-writing files. #233

Closed ChrisSorrellBSD closed 4 years ago

ChrisSorrellBSD commented 4 years ago

As a developer I like to use Seer to view text log files and the like. ...But when I do I almost always regret it because next time that log is written I tend to see a permission error: it seems like Seer must somehow leave a file lock on (some?) of the files it opens?

ccseer commented 4 years ago

Hi If the text file is very very large, then it cannot be deleted or something like that. It is because Seer is still reading.

BTW, when content is fully loaded, pressing F5 can reload the file and see the new content.

On Tue, Oct 22, 2019 at 8:04 AM ChrisSorrellBSD notifications@github.com wrote:

As a developer I like to use Seer to view text log files and the like. ...But when I do I almost always regret it because next time that log is written I tend to see a permission error: it seems like Seer must somehow leave a file lock on (some?) of the files it opens?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ccseer/Seer/issues/233?email_source=notifications&email_token=ADZZIHX3FB57AEV2W3LPB53QPY7RXA5CNFSM4JDIXL2KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HTLPUTQ, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZZIHRWXSYSNGZFW7BJ3ETQPY7RXANCNFSM4JDIXL2A .

ChrisSorrellBSD commented 4 years ago

I see this with very small files - e.g. 10-100 lines of json text.

ccseer commented 4 years ago

Which version are you using? the last version is Seer-2.3.0

On Wed, Oct 23, 2019 at 6:22 AM ChrisSorrellBSD notifications@github.com wrote:

I see this with very small files - e.g. 10-100 lines of json text.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/ccseer/Seer/issues/233?email_source=notifications&email_token=ADZZIHX2JVJVNVN62IQFHFTQP54K3A5CNFSM4JDIXL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEB7M6GQ#issuecomment-545181466, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZZIHT56XVCIZWCETBOJDDQP54K3ANCNFSM4JDIXL2A .

ChrisSorrellBSD commented 4 years ago

I'm using 2.3.0.

I just tried - and failed - to create a simple repro of the problem :( ...So I'll try and pay closer attention next time I see it occur and hopefully then I'll be able to offer up more information.

ChrisSorrellBSD commented 4 years ago

I just ran into this issue again. I think whether or not the file becomes locked depends upon its path. So if I just make a file on my desktop, view it using Seer and then delete it - fine! BUT in my problem cases the file are present under /AppData/LocalLow/ and in these cases the files become locked after looking at them with Seer every time.

ChrisSorrellBSD commented 4 years ago

Hmm, for some reason parts of my example path were removed by Git when I hit Post... I was trying to express that the problem path is (user)/AppData/LocalLocal/(sub-folder)...

I hope this helps.

ccseer commented 4 years ago

Wood, thank you for the details. They are really helpful. I will take a look into it and get back to you next week. On Sun, 1 Dec 2019 at 10:42 AM, ChrisSorrellBSD notifications@github.com wrote:

Hmm, for some reason parts of my example path were removed by Git when I hit Post... I was trying to express that the problem path is (user)/AppData/LocalLocal/(sub-folder)...

I hope this helps.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/ccseer/Seer/issues/233?email_source=notifications&email_token=ADZZIHVVNMM5B3KBU7PTBKLQWMQADA5CNFSM4JDIXL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQZLDI#issuecomment-560043405, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZZIHSZYB6R2R75TRZDMF3QWMQADANCNFSM4JDIXL2A .

ccseer commented 4 years ago

It says the file is using by the "System", not Seer. Even if without the preview window of Seer, it's still been used.

On Sun, Dec 1, 2019 at 9:09 PM Corey Chan cc.seer@gmail.com wrote:

Wood, thank you for the details. They are really helpful. I will take a look into it and get back to you next week. On Sun, 1 Dec 2019 at 10:42 AM, ChrisSorrellBSD notifications@github.com wrote:

Hmm, for some reason parts of my example path were removed by Git when I hit Post... I was trying to express that the problem path is (user)/AppData/LocalLocal/(sub-folder)...

I hope this helps.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/ccseer/Seer/issues/233?email_source=notifications&email_token=ADZZIHVVNMM5B3KBU7PTBKLQWMQADA5CNFSM4JDIXL2KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFQZLDI#issuecomment-560043405, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADZZIHSZYB6R2R75TRZDMF3QWMQADANCNFSM4JDIXL2A .

ChrisSorrellBSD commented 4 years ago

Well yes, true. But from a user's perspective I don't tend to distinguish between an app bug and an OS bug resulting directly from usage of an app.

I think if there are types of folder that lead to file locks then at the very least I think Seer shouldn't allow you to 'quick look' on them because file locks are massively frustrating to resolve! (To the extent that I hesitate to use Seer these days just in case I get one).

ccseer commented 4 years ago

2.5.4 added an option: run as administrator