reduced_length_tweets.txt - cannot write, file in use!

[bitcoin]

(thanks for the updates here though!)

Code: Select all

Posting: 1 images
Post: C:\Users\Bad Robot\OneDrive\TwitterDub\DATA\CIF\WhitePaper Promo Mostly\Images\infographic-blockchain-tech-financial-markets-accenture.png
Process image: C:\Users\Bad Robot\OneDrive\TwitterDub\DATA\CIF\WhitePaper Promo Mostly\Images\infographic-blockchain-tech-financial-markets-accenture.png
Preprocess image: infographic-blockchain-tech-financial-markets-accenture.png
Add image to tweet: infographic-blockchain-tech-financial-markets-accenture.png using tmp path: C:\Users\Bad Robot\AppData\Local\Temp\NKiAoRBgt2SBv0a.png
Added image to tweet: infographic-blockchain-tech-financial-markets-accenture.png
PreTokens: Right now #businesses see no incentive to adopt #cryptocurrency by hedging risk and charging exorbitant fees<br><br>$CIF ((bitly-rand)https://goo.gl/qJs4y6)
PostTokens: Right now #businesses see no incentive to adopt #cryptocurrency by hedging risk and charging exorbitant fees<br><br>$CIF http://btc.みんな/2ywZIdm
Too long: 160
Snipped to: (137): Right now #businesses see no incentive to adopt #cryptocurrency by hedging risk and charging exorbitant fees

$CIF http://btc.みんな/2ywZIdm
* ERROR: TwitterErrorLog: The process cannot access the file 'C:\Users\Bad Robot\AppData\Roaming\rootjazz\Twitterdub\saved_data\reduced_length_tweets.txt' because it is being used by another process.
* FAILED: TweetPostId: 175655983 to ICO_PCA
Pausing for: 17029

(and why does it say the tweet is too long? Is that because of the <br> statements? I don't think I can spot any other differences...?)

PS: when I checked, the tweet indeed wasn't posted... https://twitter.com/search?f=tweets&q=% ... e&src=typd - I made a separate post for that. HERE the question is just a remark to you: FILE IN USE :)

[martin@rootjazz]

should not be possible as the file gets a wait lock but it is instance local. Are you running multiple instances on teh same db by any chance?

[martin@rootjazz]

http://btc.みんな/2ywZIdm

ffs, who knows how that is handled!!

A-Z 0-9 only please

The program is using a 3rd party call to check tweet length as I wipe my hands of it for all the edge cases, I have no idea how they handle unicode, but each charactoer is probably something like \u001 so is 4 chars, I don't know how twitter handles it either. If you want to use that, then you need to accept legnth is going to be strange and not push to the 140 limit, keep to 120 or whaterver to allow for some play

or use a-z 0-9

[bitcoin]

http://btc.みんな/2ywZIdm

ffs, who knows how that is handled!!

A-Z 0-9 only please

The program is using a 3rd party call to check tweet length as I wipe my hands of it for all the edge cases, I have no idea how they handle unicode, but each charactoer is probably something like \u001 so is 4 chars, I don't know how twitter handles it either. If you want to use that, then you need to accept legnth is going to be strange and not push to the 140 limit, keep to 120 or whaterver to allow for some play

or use a-z 0-9

You're not rid of this one that easily... The URL is not a problem. Twitter detects it just fine and your parser does too once it goes through your algorithm. Check it. So the question remains: it's *not* the URL here.

[bitcoin]

should not be possible as the file gets a wait lock but it is instance local. Are you running multiple instances on teh same db by any chance?

No I wasn't. Maybe a notepad somewhere. I'll repost here if I know more... And again the PS: Japanese domain URLs work just fine with your 3rd party tool ;-)

[martin@rootjazz]

notepad doesn't put a lock on.

excel / office programs would, but notepad does not.


strange. I'll ensure it is handled better for future.


As to the chars being too long, that is what the response is, I guess they don't handle unicode well.

[martin@rootjazz]

https://rootjazz.com/twitterdub/updatetesting.html


locking improvement

[bitcoin]

https://rootjazz.com/twitterdub/updatetesting.html


locking improvement

thanks