[raptor2003]

Originally Posted by Jiaz

@raptor: YYYY (Week year) is something complete different than yyyy(Year)
see docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html
you have to use yyyy in your pattern, then it works fine
see also errorprone.info/bugpattern/MisusedWeekYear

Oh yes it works !

Makes sense that it was happening for videos starting 28/12 then.

Thank you.

[Jiaz]

You're welcome

[atik]

versuche mehrere YT Playlisten mit JD zu laden, aber es werden nicht alle Videos hinzugefügt.
Beispel, hier werden von 2800 nur 100 hinzugefügt.
**External links are only visible to Support Staff****External links are only visible to Support Staff**

log:
02.01.21 20.05.09 <--> 02.01.21 20.34.00 jdlog://4279525302851/

[johno4566]

that problem is knowed and is getting worked on as we speak

[Onktebong]

So far JDownloader was amazing for downloading from Youtube. Never had no problems.
Now ...
When I copy a Youtube URL it parses and only finds one offline link.
When I start a download from Youtube that has been parsed previously I get a "Too many requests" error.
Is this just a temporary thing, or can I fix it?
Windows 10 64 bit.
Thank you.

[Onktebong]

OK, everything is back to normal. Without a reboot.
So I guess Youtube either didn't work or has temporarily blocked my IP.

[Jiaz]

This message shows up when you've hit crawling limit and been *blocked*. Still can work fine in browser because of different session/cookies.... Either wait some time or try a fres IP/reconnect.

[pspzockerscene]

Merged YT threads.

-psp-

[Evox]

Originally Posted by Jiaz

@Evox
Most likely the playlist contains dupes (are not added multiple times). If you want we can check but we need link

Thanks for the reply here is the link to the channel i am trying to back up. **External links are only visible to Support Staff****External links are only visible to Support Staff** just tried again and it still stops at 399

[enjikari]

I have far less a technical question: is there a way to know what is fixed when the updates come, so we can browse and see if our issues have been fixed?

For example, I'm still having the "only grabs 100 links" issue, and every time I update JD2 I just try and grab more than 100 links to see if it's been fixed yet. Where could I find if that (or any particular) issue has been fixed in an update?

[jeffr]

Originally Posted by enjikari

I have far less a technical question: is there a way to know what is fixed when the updates come, so we can browse and see if our issues have been fixed?

For example, I'm still having the "only grabs 100 links" issue, and every time I update JD2 I just try and grab more than 100 links to see if it's been fixed yet. Where could I find if that (or any particular) issue has been fixed in an update?

I have the same question, I'm still waiting on the probably related "won't grab more than a few hundred links for YouTube playlists" bug (I know they are aware but there's no public roadmap for this actually quite serious bug). Some issues in the forum seem to be marked as "solved" when there haven't been fixes rolled out, so it would be nice. I understand that it would be more work though and it probably isn't needed, so not a huge deal. Might save the devs and admins from having the reply to a few repeat questions though, I don't know.

[pspzockerscene]

Originally Posted by enjikari

I have far less a technical question: is there a way to know what is fixed when the updates come, so we can browse and see if our issues have been fixed?

No - we do not have a changelog anymore.
You can only see it based on the forum answers.

Originally Posted by jeffr

Some issues in the forum seem to be marked as "solved" when there haven't been fixes rolled out, so it would be nice.

That is just wrong.
Short explanation:
JDownloader parses a lot of websites.
Websites can change -> That can stop our plugins from working at any given time which means forum "Solved" tags on old plugin related bugreports may lose their meaning over time

-psp-

[enjikari]

Originally Posted by pspzockerscene

No - we do not have a changelog anymore.
You can only see it based on the forum answers.

Zero complaints from me, now I know where to look and follow. As always, thank you for your hard work, dedication, and community feedback!!!

[pspzockerscene]

Thanks for your feedback too

-psp-

[Jiaz]

Sorry for long delay :(

[pranjal3029]

Originally Posted by Jiaz

Sorry for long delay :(

Is the issue solved now?

[Jiaz]

@pranjal3029: not yet

[jeffr]

I'm not complaining, take your time, I am however expressing my surprise that it's been this long due to the severity and reproducibility, especially after one of the devs saying he had hoped to have it done near Christmas. Are there any logs or anything I can provide to help? I'm assuming not since this seems to be a 100 percent reproducible issue, but if there is a way I can help, please let me know. I have significantly changed some of my archival project schedules around because I rely on JD2 so it would be nice to have a very rough ETA so that I could make plans. Thanks!

Another bit of feedback: maybe assign IDs to bugs and at least have a database that you dump those into (no need to add status, although this could be crowdsourced via a voting system with a threshold, users could vote if they think a bug has been fixed and once it passes the threshold, it would be marked as "marked as fixed by community") so that when people ask "is it solved" others will know too, and people can refer to the database for the bug ID. The reason why I think that this isn't an unfair thing to ask for is because it could be mostly automated, basically an admin copy and pasting some text for each new bug.

[pspzockerscene]

Originally Posted by jeffr

Another bit of feedback: maybe assign IDs to bugs and at least have a database that you dump those into (no need to add status, although this could be crowdsourced via a voting system with a threshold, users could vote if they think a bug has been fixed and once it passes the threshold, it would be marked as "marked as fixed by community") so that when people ask "is it solved" others will know too, and people can refer to the database for the bug ID. The reason why I think that this isn't an unfair thing to ask for is because it could be mostly automated, basically an admin copy and pasting some text for each new bug.

We do have that and it was linked.
We also told you that we do not need more logs to solve this issue.
Here is the ticket again:


-psp-

[Jiaz]

@jeffr: I'm still working on this, I hope to have this working soon