•   
  • 1
  • 138
  • 139
  • 140(current)
  • 141
  • 142
  • 154
  •   
[RELEASE] trakt.tv tv/movie scrobbler
(2015-02-20, 04:37)abmoraz Wrote:
(2015-02-20, 04:28)lysin Wrote:
(2015-02-20, 04:24)abmoraz Wrote: Ok, definitely using 3.0.0. Had to re-enter all my settings (And I noticed some of the settings changed), but I am still getting 503 errors constantly. My log is below:

21:21:22 T:140654993434368 NOTICE: -->Python Interpreter Initialized<--
21:22:14 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:19 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 1
21:22:19 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:24 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 2
21:22:24 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:29 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 3
21:22:30 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:35 T:140654993434368 WARNING: [script.trakt] trakt.interfaces.base: request failed: Service Unavailable - "server overloaded" (code: 503)
21:22:40 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:45 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 1
21:22:45 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:50 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 2
21:22:50 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:55 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 3
21:22:55 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:23:00 T:140654993434368 WARNING: [script.trakt] trakt.interfaces.base: request failed: Service Unavailable - "server overloaded" (code: 503)

I'm getting the same issue on a fresh plugin install.

Maybe a trakt api issue?

The odd thing is that I have retries set to 10, yet it is quitting after 3.

Forgot to remove that setting. Retrying won't help you if the server is not responding at all.

(2015-02-20, 05:00)abmoraz Wrote:
(2015-02-20, 04:39)S7eele Wrote: i will check the sources i know to verify and ill check my log to see if im seeing same but it sure looks like an api issue to me, wouldnt get too worried yet lol

update - i havent seen anything on twitter, forum or elsewhere yet but it failed on manual sync where it has been working flawlessly before, i dont think its a coincidence we are all seeing it at the same time, i suspect it is an api issue

not sure why it happened but upon restarting after capturing a logfile to examine i got a username/password error, im not concerned about it as i figure its an anomaly but will capture a log jic


I got the username/password error once, but it went away. I also got an OAuth error in the log at one point, too. But again, it went away. Looks like the API is borked.

Do you have an proof or log? We're not using oauth so that should no happen, I'm not even sure if there is any error message that has oauth in it.

(2015-02-20, 05:23)S7eele Wrote:
(2015-02-20, 04:39)S7eele Wrote:
(2015-02-20, 04:24)abmoraz Wrote: Ok, definitely using 3.0.0. Had to re-enter all my settings (And I noticed some of the settings changed), but I am still getting 503 errors constantly. My log is below:

21:21:22 T:140654993434368 NOTICE: -->Python Interpreter Initialized<--
21:22:14 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:19 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 1
21:22:19 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:24 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 2
21:22:24 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:29 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 3
21:22:30 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:35 T:140654993434368 WARNING: [script.trakt] trakt.interfaces.base: request failed: Service Unavailable - "server overloaded" (code: 503)
21:22:40 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:45 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 1
21:22:45 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:50 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 2
21:22:50 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:22:55 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Retry # 3
21:22:55 T:140654993434368 WARNING: [script.trakt] trakt.core.http: Continue retry since status is 503, waiting 5 seconds
21:23:00 T:140654993434368 WARNING: [script.trakt] trakt.interfaces.base: request failed: Service Unavailable - "server overloaded" (code: 503)
(2015-02-20, 04:28)lysin Wrote: I'm getting the same issue on a fresh plugin install.

Maybe a trakt api issue?

i will check the sources i know to verify and ill check my log to see if im seeing same but it sure looks like an api issue to me, wouldnt get too worried yet lol

update - i havent seen anything on twitter, forum or elsewhere yet but it failed on manual sync where it has been working flawlessly before, i dont think its a coincidence we are all seeing it at the same time, i suspect it is an api issue

not sure why it happened but upon restarting after capturing a logfile to examine i got a username/password error, im not concerned about it as i figure its an anomaly but will capture a log jic
related to current issue ^^^:

wanted to update to report that the second time i restarted kodi i received the 'cannot connect to trakt' error which i assume is the intended message, not sure why it displayed 'incorrect username/password' on first restart and 'cannot connect to trakt' on second restart and not sure it matters but being my overcautious self i captured the logs for both, @Razze if u have any interest in the logs let me know, if not no reply necessary

Get me the incorrect username/password case should only happen if the server returns but doesn't return with a token, so thats pretty weird.

(2015-02-20, 06:20)abmoraz Wrote:
(2015-02-20, 06:00)S7eele Wrote: manual sync appeared to work although quite a bit slower atm, i believe that is tbe as im still assuming the api hiccuped, timeouts/slow response as it gets back to normal, i am encountering occassional errors still, waiting for things to stabilize



Ok, new error:

3:18:43 T:140337855035136 FATAL: [script.trakt] traktapi: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
- NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
Error Type: <type 'ReadTimeout'>
Error Contents: (ReadTimeoutError("HTTPSConnectionPool(host='api-v2launch.trakt.tv', port=443): Read timed out. (read timeout=24)",),)
Traceback (most recent call last):
File "/home/abmoraz/.kodi/addons/script.trakt-dev/traktapi.py", line 60, in getToken
auth = Trakt['auth'].login(getSetting('username'), getSetting('password'))
File "/home/abmoraz/.kodi/addons/script.trakt-dev/trakt/interfaces/auth.py", line 10, in login
'password': password
File "/home/abmoraz/.kodi/addons/script.trakt-dev/trakt/core/http.py", line 89, in post
return self.request('POST', path, params, data, **kwargs)
File "/home/abmoraz/.kodi/addons/script.trakt-dev/trakt/core/http.py", line 66, in request
response = self.session.send(prepared, timeout=timeout)
File "/home/abmoraz/.kodi/addons/script.module.requests/lib/requests/sessions.py", line 569, in send
r = adapter.send(request, **kwargs)
File "/home/abmoraz/.kodi/addons/script.module.requests/lib/requests/adapters.py", line 422, in send
raise ReadTimeout(e, request=request)
ReadTimeout: HTTPSConnectionPool(host='api-v2launch.trakt.tv', port=443): Read timed out. (read timeout=24)
-->End of Python script error report<--

Thats just a timeout, when the server is not responding. You should get a "can not connect to trakt" error message in your ui.
Hi, tried master branch since 4 days on RaspPI 2 on the last Openelec, everything is working fine : counters and watched status
Currently using your latest dev-version on KODIbuntu 14.1, Kodi 14.1 on Mac and Kodi 14.1 on jailbroken iPad Air. Everything works like a charm, syncing and scrobbling without issues.
Running Kodi on:
Linux, Windows, iOS and OSX
Streaming 16TB from 4 NAS servers (4 x 4TB) over 5GHz WiFi-AC + gigabit ethernet.
Image
Is the issue with italian translation fixed?
I'm using the master branch.. Is a pull sufficient?
@Razze

not working here and getting this in log:

Code:
16:21:43 T:140226481886976 WARNING: [script.trakt] trakt.interfaces.base: request failed: Unauthorized - "OAuth must be provided" (code: 401)
Image
How long has trakt been working on v2? Just curious if it is a long time or not. If not, I am fine with waiting for it to be fixed, if it is a long time, I worry if they wouldn't be better off going back.
Why would they be better going back? is there something that doesnt work with API v2?

The new API ismost likely faster, hasnew features, easier on their servers, and i would say it gives them much more powerful control over things. I don't know for sure but the only thing they are losing is (full) backwards compatability with old apps. Lots of apps have already been changed over, most android and ios apps are using V2 and it wont be long till this script has full support.

@Razze is there any loss of feature or anything that is worse in v2.
it just seems that we are all having a ton of trouble.

I only installed trakt 3 days ago, so I have no idea as to how long it has not worked properly. Whether it is an issue with the add-on or their server I am not sure, but as you state v2 is easier on their server, then what causes the connection failures? I have no clue if it is on our end or theirs, but I can tell you that my stuff does not update properly. When I watch a show it shows up, fine, working, but I have shows marked as watched that are not being updated. This to me means there is an issue. However, at the same time I made note of not knowing how long it has been that v2 has had issue. If it is a week or 2 keep working it, but if it is 6 months, then whats the point.

Thats all I was saying. If it has been forever and not getting better, maybe go back. If there is constant progress, I am good with staying on v2 and working the bugs and issues.
Does .strm scrobbling work? i haven't tried myself just wanna be sure... it worked in the former ver2.xx
Yeah, Me, Myself, and I, The Three Musketeers
Image
there has definitely been constant progress, the change happened right around the new year, for the level of effort involved i feel they are doing pretty well, falling back has never really been an option, the previous infrastructure was overloaded and at the point of failure, it could no longer keep up with the traffic being generated

thats a very broad overview and i dont claim to be an expert on the matter, i can certainly try to find one of the posts on the trakt vip forum in which trakt developers address the same subject or razze could certainly add more detail but not sure its a good use of anybodys time, just fyi, i understand your good with the current situation

p.s. - i mentioned the trakt vip forum above and thought i should take the opportunity to explain that access to the forum is just one of the benefits you get with the very reasonably priced vip subscription to trakt, there is a lot of good info and communication with the developers on the forum and you also have the ability to influence where trakt goes in the future, if you want to contribute to the trakt efforts thats a good way of doing it
(2015-02-20, 21:05)TerrorKeed Wrote: Does .strm scrobbling work? i haven't tried myself just wanna be sure... it worked in the former ver2.xx
yes, it has been working well for a while now
OK, so I'll just keep using it in the current state and accept it. It half works for me anyway so that's fine, better than nothing. 2 months is good progress for me, things take time....
thanks bro... been tad busy with learning python and coding addons so haven't had time to watch movies/use XBMC until today been a while Smile
Yeah, Me, Myself, and I, The Three Musketeers
Image
(2015-02-20, 21:15)smakovits Wrote: OK, so I'll just keep using it in the current state and accept it. It half works for me anyway so that's fine, better than nothing. 2 months is good progress for me, things take time....

You might need to post a log. I am sure it is better than "half works". I am quite pleased with the way it works. IMO it is ready (or damned near) for a final/stable release.
I marked an episode on trakt website as watched with an specific date in the past, the episode has not been marked as watched in kodi. I enable the option to sync from trakt to kodi. The episode got marked as watch in kodi, but with the date and time of the sync. Is that the current behavior or is it a bug?
  •   
  • 1
  • 138
  • 139
  • 140(current)
  • 141
  • 142
  • 154
  •   



Logout Mark Read Team Forum Stats Members Help
[RELEASE] trakt.tv tv/movie scrobbler13
This forum uses Lukasz Tkacz MyBB addons.