Flash Players not displaying video past 360p quality

The Flash players Within YT2009 do not seem to be rendering videos past 360p. The options will be available in the player after enabling h264 playback, but they will not display video in the selected quality (for ex. I select 480p but the flash player still renders the video in 360p) Im wondering if this is an issue aware to the developer or if this needs fixing on my own. Thanks.

The Flash players Within YT2009 do not seem to be rendering videos past 360p. The options will be available in the player after enabling h264 playback, but they will not display video in the selected quality (for ex. I select 480p but the flash player still renders the video in 360p) Im wondering if this is an issue aware to the developer or if this needs fixing on my own. Thanks.

and when i try to press hd
it wont load an hd video it will refuse only can play HQ at max

what flash player? default? some alt one?

what flash player? default? some alt one?

mines default watch.swf

what flash player? default? some alt one?

this also affects cps2 the dark player with a video quality chooser anything above 360p is not letting it play

what flash player? default? some alt one?

All of the Players, Default and the ones in alt-swf

Also I would like to add that the 2010 and 2012 players do not have Quality options whatsoever when they clearly have the code to have quality options (and the 2012 player has code to allow rendering up to 1080p)
The entire settings button is missing on both of those players, 2010 and 2012 as well.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

I'm not sure if this is related, but it seems that YT2009 flash player is not working on Windows 9X (didn't tested personally). Try to test in Windows 98/me, Firefox 2.0/Netscape/Retrozilla and see if that's related.
https://msfn.org/board/topic/185941-new-2009-youtube-frontend-does-it-work-well-on-windows-9x-systems/

i've just tested yt2009.giabs.ovh on ie5 on windows 98 and it worked there.
the forum posts:

are dated (yt2009.giabs.ovh has seen flash player changes since then)
don't mention /toggle_f which is required to enable flash (otherwise the html5 player is used which won't work for old browsers)

flash players are not something that just works out of the box as soon as you setup yt2009 (needs additional patch work as mentioned in the README) and some public instances just tend not to do that.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

Yea It could be because I only patched the base_url and Security domains on those players, are you able to give me a full list of everything i need to patch on all the players? thanks.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

Yea It could be because I only patched the base_url and Security domains on those players, are you able to give me a full list of everything i need to patch on all the players? thanks.

and what about the supposed 2013 player in the flashpoint database when i tried patching it the guided way it just says movie not loaded while all the other players load just fine

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

Yea It could be because I only patched the base_url and Security domains on those players, are you able to give me a full list of everything i need to patch on all the players? thanks.

and what about the supposed 2013 player in the flashpoint database when i tried patching it the guided way it just says movie not loaded while all the other players load just fine

This is Because no player is the same when it comes to patching them, Each player has different things you must do to patch them (for ex. i got ahold of the 2013 players from archive.org and patching base_url just leaves the video with a black screen)

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

Do you know how i can patch the quality url?

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

Do you know how i can patch the quality url?

If you know JS you could attempt it, however when I was patching late 2012 player I noticed that certain get_video_info files (mainly one I found from 2017/2018) with urls specified seemed to work at getting the settings button to show up.
Example of one of the files I found that works :

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

Do you know how i can patch the quality url?

If you know JS you could attempt it, however when I was patching late 2012 player I noticed that certain get_video_info files (mainly one I found from 2017/2018) with urls specified seemed to work at getting the settings button to show up. Example of one of the files I found that works :

Ill Give it a shot when i get some free time as i just do not have that right now, lowkey thanks for the insight as it could be used to fully patch other players

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

Do you know how i can patch the quality url?

If you know JS you could attempt it, however when I was patching late 2012 player I noticed that certain get_video_info files (mainly one I found from 2017/2018) with urls specified seemed to work at getting the settings button to show up. Example of one of the files I found that works :

Do you know where i could get those get_video_info files and give me some tips on how to patch it fully?

yt2009's implementation of get_video_info shows 360p/480p/720p depending on which ones are available. i'm able to recreate that on my dev instance and the public ones. are you sure video cache isn't messing with that in your case?
you can rename/remove back/cache_dir/video_cache.json to reset your video cache. then try testing get_video_info.

yt2009's implementation of get_video_info shows 360p/480p/720p depending on which ones are available. i'm able to recreate that on my dev instance and the public ones. are you sure video cache isn't messing with that in your case?
you can rename/remove back/cache_dir/video_cache.json to reset your video cache. then try testing get_video_info.

I've concluded that the 2012 player yt2009 has looks for a specific url property in get_video_info for the settings button to show as the one I have from november 2012 shows the settings button shows up just fine with the get_video_info file I give it.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

I've concluded that either the 2012 player yt2009 is indeed bugged, or the 2012 player is looking for a specific url name in get_video_info which fails and causes the button to be removed, because i have a 2012 player from december 6th 2012 that works just fine on yt2009 without any problems.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

I've concluded that either the 2012 player yt2009 is indeed bugged, or the 2012 player is looking for a specific url name in get_video_info which causes it to fail as it doesn't exist and causes the button to be removed. I only came to this conclusion because I have a 2012 player from december 6th 2012 that works just fine on yt2009 without any problems or modifications to the frontend (other then adding the swf file).

So I decided to patch watch_as3-vflJogbdx.swf, the same unmodified version 2012.swf uses and the settings button shows up fine. It leads me to believe that when the file was originally patched something happened along the process that made the settings button not work as intended.

flash qualities are supported within yt2009 when the players are patched and everything. other than the 2012 player being bugged and not doing that correctly, the 2010 for example should be fine. are you sure it's actually rendering 360p and the videos themselves are not poor quality in overall? some music videos tend to do that for example

2012 player isn't bugged, the settings button doesn't show because there is no quality url specified in get_video_info so it gets removed by default.

I've concluded that either the 2012 player yt2009 is indeed bugged, or the 2012 player is looking for a specific url name in get_video_info which causes it to fail as it doesn't exist and causes the button to be removed. I only came to this conclusion because I have a 2012 player from december 6th 2012 that works just fine on yt2009 without any problems or modifications to the frontend (other then adding the swf file).

So I got curious and decided to patch the original unmodified file 2012.swf uses (watch_as3-vflJogbdx.swf), and I found that the settings button does indeed work fine on my patch. It leads me to suspect that when the original 2012.swf file for yt2009 was modified, that something happened or got corrupted (but not to the point that the file stops working) along the process in which caused the settings button to not work as intended and not show up.

Can you give me a detailed list of how to patch the unmodified 2012 player like you did?

My list goes like this (made so you can follow the directory pathing inside the swf file) :
watch_as3-vflJogbdx.swf

scripts

com.google.youtube.model

YouTubeEnvironment

**LIVE_BASE_URL**
UrlValidator
isEmbedLoadingDomain

**_loc2** => **"youtube.com"**
isTrustedDomain
**_loc2** => **"youtube.com"**

Or if that's to confusing for you or you're worried about messing things up, I made a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit).
https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

NockTwelve

Nevermind false alarm, it was not working because I forgot to add the port in live base URL

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012?
(I've been trying to patch 2010 to play videos but to no avail)

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears basically so.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I just now got it to work with quality options and everything, which was because i used the player striaght from the swfbin and i patched everything in P-CODE instead of Actionscript. Thanks for the help along the way, The Issues with players originally were because i was patching Actionscript instead of P-CODE.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I just now got it to work with quality options and everything, which was because i used the player striaght from the swfbin and i patched everything in P-CODE instead of Actionscript. Thanks for the help along the way, The Issues with players originally were because i was patching Actionscript instead of P-CODE.

ya I used to use actionscript but since it has a chance of corrupting my work a round (as you see in video) was to use P-Code so it doesn't corrupt itself.

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I just now got it to work with quality options and everything, which was because i used the player striaght from the swfbin and i patched everything in P-CODE instead of Actionscript. Thanks for the help along the way, The Issues with players originally were because i was patching Actionscript instead of P-CODE.

ya I used to use actionscript but since it has a chance of corrupting my work a round (as you see in video) was to use P-Code so it doesn't corrupt itself.

are you having an issue where the cps2.swf player (the dark mode one) is not rendering video above 360p?

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I just now got it to work with quality options and everything, which was because i used the player striaght from the swfbin and i patched everything in P-CODE instead of Actionscript. Thanks for the help along the way, The Issues with players originally were because i was patching Actionscript instead of P-CODE.

ya I used to use actionscript but since it has a chance of corrupting my work a round (as you see in video) was to use P-Code so it doesn't corrupt itself.

are you having an issue where the cps2.swf player (the dark mode one) is not rendering video above 360p?

No

I suck at explaining things so here's a video (with no audio) on how I patched it (Apology for going super fast, I had to due to githubs 10 meg limit). https://github.com/ftde0/yt2009/assets/52929976/1cdb3a77-5467-4487-96c6-7ecc06ca0a7a

I got 2012 and 2013 to work with quality options, however I am still stuck with 2010 not showing quality options. Do you know how to fix it in the case of 2010?

I'll look into that right now.

Thanks, and on my part i will look into fixing fullscreen on 2006-08 players.

Yes it appears the same issue as the 2012 is also happening as I patched the swf file 2010 uses and the quality button appears fine.

Is the way to patch 2010 the same as 2012? (I've been trying to patch 2010 to play videos but to no avail)

it appears so, however 2010 has one extra base url in YouTubeEnvironment.

I'll try one more time to patch it but this time I'm using the raw 2010 player

I hope best of luck, if you are having issues I can record another video about it.

I just now got it to work with quality options and everything, which was because i used the player striaght from the swfbin and i patched everything in P-CODE instead of Actionscript. Thanks for the help along the way, The Issues with players originally were because i was patching Actionscript instead of P-CODE.

ya I used to use actionscript but since it has a chance of corrupting my work a round (as you see in video) was to use P-Code so it doesn't corrupt itself.

are you having an issue where the cps2.swf player (the dark mode one) is not rendering video above 360p?

No

i probably need to repatch it on my end because selecting 720p on my end doesnt do anything and renders the video in 360p

(might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) on it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.
Yea because actionscript 3 editing was experimental at the time of v 15.1.1's release and could cause corruptions (like with the quality button)

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

On public instances watch.swf and cps2.swf will both display 720p and HD video just fine respectively, so there
is a possible fix

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

On public instances watch.swf and cps2.swf will both display 720p and HD video just fine respectively, so there is a possible fix

I'll see if repatching the original cps2 file will change anything (I doubt but I guess why not?).

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

On public instances watch.swf and cps2.swf will both display 720p and HD video just fine respectively, so there is a possible fix

I'll see if repatching the original cps2 file will change anything (I doubt but I guess why not?).

Yeah I suppose it's worth a try, if that method does not work it's probably a get_video_info thing.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

On public instances watch.swf and cps2.swf will both display 720p and HD video just fine respectively, so there is a possible fix

I'll see if repatching the original cps2 file will change anything (I doubt but I guess why not?).

Yeah I suppose it's worth a try, if that method does not work it's probably a get_video_info thing.

Sorry for the hours delay, I was trying to find the original unpatched cps swf file on wayback but eventually gave up.

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head.
if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

Im currently looking through get_video_info and other codes to find out whats wrong, I know i patched it completely with P-Code and did not touch actionscript

I only use P - Code if I know the player is in ActionScript 3 or if the ActionScript button also has a (Experimental) next to it.

 (might be hard to tell for you, but there was no change in the quality of the video after selecting 720p)

I see what you mean, I'm not sure if it's the players fault or get_video_info but it looks like it doesn't request the quality you choose but defaults to the lowest it can load.

On public instances watch.swf and cps2.swf will both display 720p and HD video just fine respectively, so there is a possible fix

I'll see if repatching the original cps2 file will change anything (I doubt but I guess why not?).

Yeah I suppose it's worth a try, if that method does not work it's probably a get_video_info thing.

Sorry for the hours delay, I was trying to find the original unpatched cps swf file on wayback but eventually gave up.

Ill try to look for it and see if i can find it

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did look through before your post however I was unable to find the same dark theme playlist player in the same layout (I found some playlist players but they where the light theme and had the playlist on the right side).

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did take a look prior to your post however as I said earlier I was not successful into finding the same dark theme playlist player, will try looking again in a bit.
Edit: I did find a dark theme player but it's just cps.swf but dark theme.

Anyway to fix default player not displaying? (ive repatched the raw .swf multiple times and still no result)

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did take a look prior to your post however as I said earlier I was not successful into finding the same dark theme playlist player, will try looking again in a bit.
Edit: I did find a dark theme player but it's just cps.swf but dark theme.

 Anyway to fix default player not displaying? (ive repatched the raw .swf multiple times and still no result)

It only shows up white if it cannot find the file, if the field is blank in toggle_f make sure your file name is also watch.swf.

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did take a look prior to your post however as I said earlier I was not successful into finding the same dark theme playlist player, will try looking again in a bit.
Edit: I did find a dark theme player but it's just cps.swf but dark theme.

 Anyway to fix default player not displaying? (ive repatched the raw .swf multiple times and still no result)

Make sure the default player your patching is named watch.swf.

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did take a look prior to your post however as I said earlier I was not successful into finding the same dark theme playlist player, will try looking again in a bit.
Edit: I did find a dark theme player but it's just cps.swf but dark theme.

 Anyway to fix default player not displaying? (ive repatched the raw .swf multiple times and still no result)

Make sure the default player you're patching is named watch.swf.

Yea i got it fixed a few hours ago after i realized i was trying to use the watch_v8(etc) .swf player instead of watch.swf

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

I did take a look prior to your post however as I said earlier I was not successful into finding the same dark theme playlist player, will try looking again in a bit.
Edit: I did find a dark theme player but it's just cps.swf but dark theme.

 Anyway to fix default player not displaying? (ive repatched the raw .swf multiple times and still no result)

Make sure the default player you're patching is named watch.swf.

where is the conclusion to this right now

noticed the title change, thought this was a new issue.
watch.swf, the 2009 default player, uses a different method of showing qualities than post-2010, where the formats are defined in the params instead of a separate get_video_info request. specifically, fmt_url_map and fmt_map params are set.
however, those are only set when the default player is used and is at /watch.swf. otherwise it is treated as an alt player and won't have those.
cps players are barely maintained so it's hard to tell from the top of my head. if you're looking for original cps/cpb players, open this url - https://web.archive.org/web/*/http://s.ytimg.com/yt/swfbin/* and once the list loads do a search for "cps" to find those. that's also mentioned in /alt-swf/readme.md.

this is most likely what you're looking for when it comes to higher qualities.


Internal Server Error when running any fastlane commands

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Command executed

Complete output when running fastlane, including the stack trace and command used

I run any fastlane commands and got to this error, This wasnt appearing yesterday just now. But when im running it through bitrise locally it works well.

Environment

 [REPLACE THIS WITH YOUR INFORMATION]

https://user-images.githubusercontent.com/20021423/97985813-ba13be00-1e13-11eb-8f9c-76c003bceafd.png

Please provide the environment info as requested above.
Also, if nothing's changed in your environment between a successful execution and a failed one, it might be a legit issue on Apple's end.

✅ fastlane environment ✅
Stack

Key
Value

OS
10.15.7

Ruby
2.7.2

Bundler?
false

Git
git version 2.29.2

Installation Source
/usr/local/Cellar/fastlane/2.166.0/libexec/bin/fastlane

Host
Mac OS X 10.15.7 (19H15)

Ruby Lib Dir
/usr/local/Cellar/ruby/2.7.2/lib

OpenSSL Version
OpenSSL 1.1.1g  21 Apr 2020

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
12.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane
default_platform(:android)

before_all do
end

platform :android do
  desc "Runs all the tests"
  jsonResponse = JSON.parse(app_upload_response)

  lane :splash_dl do
    Dir.chdir('..') do
      sh("curl -o ./assets/bootsplash #{jsonResponse['launchScreen']['url']} " )
      begin
        sh("find . -name bootsplash -exec mogrify -format png {} +;")
      rescue => exception
        UI.error(ex)
      ensure
        sh('cd assets && rm bootsplash')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-hdpi')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-ldpi')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-mdpi')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-xhdpi')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-xxhdpi')
        sh('cd assets && cp -v -R  bootsplash.png ../android/app/src/main/res/drawable-xxxhdpi')
      end

    end
  end

  desc "Submit a new Beta Build to Crashlytics Beta"
  lane :beta do
    gradle(task: "clean assembleRelease")
    crashlytics
    # sh "your_script.sh"
    # You can also use other beta testing services here
  end

  desc "Deploy a new version to the Google Play"
  lane :deploy do
    gradle(task: "clean assembleRelease")
    upload_to_play_store
  end

end

`./fastlane/Appfile`
json_key_file("./android/app/taply-dev.json") # Path to the json secret file - Follow https://docs.fastlane.tools/actions/supply/#setup to get one
package_name(ENV["ANDROID_APPLICATION_ID"]) # e.g. com.krausefx.app

fastlane gems

Gem
Version
Update-Status

fastlane
2.166.0
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-increment_version_code
0.4.3
✅ Up-To-Date

fastlane-plugin-appicon
0.15.0
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.4.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.2

claide
1.0.3

colored2
3.1.2

nanaimo
0.3.0

xcodeproj
1.19.0

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.7.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
4.0.6

addressable
2.7.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

babosa
1.0.4

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.78.0

ruby2_keywords
0.0.2

faraday
1.1.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

http-cookie
1.0.3

faraday-cookie_jar
0.0.7

faraday_middleware
1.0.0

fastimage
2.2.0

gh_inspector
1.1.3

json
2.3.0

mini_magick
4.10.1

rubyzip
2.3.0

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.6

bundler
2.1.4

naturally
2.2.0

simctl
1.6.8

jwt
2.2.2

uber
0.1.0

declarative
0.0.20

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mini_mime
1.0.2

multi_json
1.15.0

signet
0.14.0

memoist
0.16.2

os
1.1.1

googleauth
0.14.0

httpclient
2.8.3

google-api-client
0.38.0

google-cloud-env
1.4.0

google-cloud-errors
1.0.1

google-cloud-core
1.5.0

rake
13.0.1

digest-crc
0.6.1

google-cloud-storage
1.29.1

emoji_regex
3.2.1

jmespath
1.4.0

aws-partitions
1.388.0

aws-eventstream
1.1.0

aws-sigv4
1.2.2

aws-sdk-core
3.109.1

aws-sdk-kms
1.39.0

aws-sdk-s3
1.83.1

uri
0.10.0

forwardable
1.3.1

logger
1.4.2

cgi
0.1.0

timeout
0.1.0

stringio
0.1.0

ipaddr
1.2.2

openssl
2.1.2

ostruct
0.2.0

strscan
1.0.3

date
3.0.0

delegate
0.1.0

fileutils
1.4.1

io-console
0.5.6

zlib
1.1.0

singleton
0.1.0

rexml
3.2.3

open3
0.1.0

yaml
0.1.0

psych
3.1.0

mutex_m
0.1.0

webrick
1.6.0

fastlane-plugin-increment_version_code
0.4.3

fastlane-plugin-appicon
0.15.0

benchmark
0.1.0

generated on: 2020-11-09

Uploaded my env, I did just remove some of private use

If it works locally, did you see if Bitrise change anything on their end? Maybe they upgraded the machine's OS, dependencies or something else 🤔 ? Have you tried resetting any cache that might exist in the CI?

@rogerluan , in Bitrise locally it works when using Fastlane, but when I'm using Fastlane directly it doesn't work and the error above shows. I've already reinstall many times my fastlane.
Note:
my fastlane locally is 2.166 the on above while the bitrise locally uses 2.153

I'm confused with the terminology 😅 Are there these 3 options?
bitrise - unknown ❓
bitrise local (?) - Fastlane 2.166 - doesn't work ❌
your machine - Fastlane 2.153 - works ✅
Is that right?

I'm confused with the terminology 😅 Are there these 3 options?
bitrise server - unknown ❓
bitrise local (?) - Fastlane 2.166 - doesn't work ❌
your machine - Fastlane 2.153 - works ✅
Is that right?

bitrise server - works
bitrise local - Fastlane 2.153 works
fastlane local pc - Fastlane 2.166 - doesn't work ❌

it's now fixed, I've discovered that the error originates from my environment variables, Fastlane is not the fault

@gelodgreat Great!! 🎉
Mind sharing what was the issue? 😃 This might help other users solve the same problem in the future 🤗


Compatibility of Signing & Verification with V2 Component Descriptors

Description
We have to check whether the OCM-based signing and verification process works also with V2 ("CNUDIE") Component Descriptors. Background is that we need to support the V2 CDs with the OCM Toolset, so that we can safely exchange the "non-OCM Toolset" with the OCM Toolset in existing scenarios.
Done Criteria

[ ] It has been verified that V2-CD can be signed and verified using the OCM Toolset

Signing with ocm and verifying with component-cli is not compatible:
ocm sign component -s jens -K $KEY ghcr.io/jensh007//github.com/acme/simpleserver

component-cli ca signatures verify rsa ghcr.io/jensh007 github.com/acme/simpleserver 1.0.0 --signature-name jens --public-key /Users/d058463/Documents/SAP-Dev/Kubernetes/ocm/getting-started/acme.pub

unable to create rsa verifier: unable to parse public key: asn1: structure error: tags don't match (6 vs {class:2 tag:0 length:3 isCompound:true}) {optional:false explicit:false application:false private:false defaultValue:<nil> tag:<nil> stringType:0 timeType:0 set:false omitEmpty:false} ObjectIdentifier @2

There are more incompatibilities:
component-cli ca signatures sign rsa ghcr.io/jensh007 github.com/acme/simpleserver 0.1.0 --upload-base-url ghcr.io/jensh007/signed --recursive --signature-name jens2 --private-key private-key.pem
unable to to fetch component descriptor github.com/acme/simpleserver:0.1.0: unknown component config type 'application/vnd.ocm.software.component.config.v1+json' expected 'application/vnd.gardener.cloud.cnudie.component.config.v1+json'

component-cli ca remote push gen/ca
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x104c182a8]

goroutine 1 [running]:
github.com/gardener/component-spec/bindings-go/apis/v2.FromUnstructuredObject(0x10530fc58, 0x140001c3780, 0x0, 0x10530fbb8, 0x140001df0e0, 0x0, 0x0)
	/go/src/github.com/gardener/component-cli/vendor/github.com/gardener/component-spec/bindings-go/apis/v2/codecs.go:195 +0x28
github.com/gardener/component-spec/bindings-go/apis/v2.(*UnstructuredTypedObject).DecodeInto(...)
	/go/src/github.com/gardener/component-cli/vendor/github.com/gardener/component-spec/bindings-go/apis/v2/unstructured.go:118
github.com/gardener/component-cli/pkg/components.GetOCIRepositoryContext(0x10530fc30, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x1400003ceb0, 0x47)
	/go/src/github.com/gardener/component-cli/pkg/components/localcache.go:118 +0x244
github.com/gardener/component-cli/pkg/components.OCIRef(0x10530fc30, 0x0, 0x14000039db8, 0x16, 0x14000690a90, 0x5, 0x10532cb68, 0x140000f5180, 0x10531b790, 0x140001a3700)
	/go/src/github.com/gardener/component-cli/pkg/components/localcache.go:103 +0x3c
github.com/gardener/component-cli/pkg/commands/componentarchive/remote.(*PushOptions).Run(0x140006cc4d0, 0x105321f68, 0x140003c7e60, 0x1053266a0, 0x140001c2da0, 0x0, 0x105332208, 0x10590e030, 0x105321f68, 0x104fd264a)
	/go/src/github.com/gardener/component-cli/pkg/commands/componentarchive/remote/push.go:98 +0x278
github.com/gardener/component-cli/pkg/commands/componentarchive/remote.NewPushCommand.func1(0x1400001cb00, 0x1400009ca20, 0x1, 0x1)
	/go/src/github.com/gardener/component-cli/pkg/commands/componentarchive/remote/push.go:64 +0xbc
github.com/spf13/cobra.(*Command).execute(0x1400001cb00, 0x1400009ca00, 0x1, 0x1, 0x1400001cb00, 0x1400009ca00)
	/go/src/github.com/gardener/component-cli/vendor/github.com/spf13/cobra/command.go:863 +0x1d0
github.com/spf13/cobra.(*Command).ExecuteC(0x140001c9080, 0x1400018e000, 0x140001c9080, 0x104773e84)
	/go/src/github.com/gardener/component-cli/vendor/github.com/spf13/cobra/command.go:977 +0x264
github.com/spf13/cobra.(*Command).Execute(...)
	/go/src/github.com/gardener/component-cli/vendor/github.com/spf13/cobra/command.go:905
main.main()
	/go/src/github.com/gardener/component-cli/cmd/component-cli/main.go:20 +0x70

Looking at both examples above, I wonder whether we have to support scenarios where the component-cli is used on OCM generated artifacts (first example is signing with OCM and verifying with component-cli, second example is signing an OCM-generated CD with the component-cli).
Wouldn't it be enough if we focus on using the OCM on artifacts created with the component-cli, and not vice versa ? The OCM-CLI being able to work with existing V2-CDs would enable all stakeholders to move to the new tooling. Why should stakeholders need to use the V2-Toolset ("component-cli") on V3 CDs (created via OCM-CLI) ?

As per our discussion:

Existing and signed V2 (component-cli based) components must be verifiable with OCM-CLI

Status Update:

Performed several tests with ocm and component-cli to verify Gardener components:
Two issues identified and fixed

Issue: component-cli adds in normalized cd the field "extraIdentity":null even if this field is not present in the source
Needs an update of ocm to handle this.
Fix tested with test component successfully (sign with component-cli, verify with ocm)

couple of fixes applied:

successfully verified Gardener BoM now
successfully resigned Gardener BoM with ocm and verified it again.
PR and merge outstanding

Can this be closed ? Are all currently known compatibility-related things fixed ?


Nested list items with indent size of 4

Describe the bug
Nested list items are rendered at the same level of the parent if the indent size is 4. Perhaps the levels are calculated assuming an indent size of 2 spaces.
Are you using a distro?
No

[!NOTE]
Distros can sometimes cause unusual behavior due to changing various options.

To Reproduce
Steps to reproduce the behavior:

Install markview.nvim.
Open a markdown document.
Write a list item, followed by a child list item nested with 4 spaces.

Expected behavior
The child list items should be rendered with a deeper level (i.e., starting on a higher column number) than the parent.
Actual behavior
The parent and child list items are displayed on the same level. Additional child items are indented more than necessary.
Screenshots

Neovim version
0.10.0
Additional context
N/A.

Trees-sitter was responsible for this bug(due to showing different ranges for different list items).
Hopefully, now this issue shouldn't occur anymore.


Drop language in Travis CI config

The latest build failure https://travis-ci.org/snowleopard/hadrian/jobs/255299317 is probably caused by this. Adding this line makes the build status list clearer since there is not a non-relavent "Ruby", but I should anticipate that it might introduce some unwanted effects.

So, we're stuck with this "Ruby" thing? Oh well.
I'll wait for the green light from Travis.

So, we're stuck with this "Ruby" thing? Oh well.

Shrug ... I think there is insufficient doc on how the text is composed.

OK, merged now. Thanks @izgzhen!


Module for pulling random quotes

Sample queries:
generate quote, quote, quote please, can i have a quote, random quote
Right now uses a API with only programming/CS related quotes.

Fastest new module I ever merged! :smile:

Thanks @AChelikani! :+1:


[Do not merge] Uptest PR

Description of your changes

Fixes #
I have:

[ ] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/timestreamwrite/database.yaml"

/test-examples="examples/timestreamwrite/database.yaml"

/test-examples="examples/timestreamwrite/database.yaml"


Fix style guide examples formatting and ellipsis

The ... dots are not transformed to unicode ellipsis character … when building docs. To have correct ellipsis characters it must be right in the .md source.
Why:
The Style guide should show examples formatted correctly.
What's being changed (if available, include any code snippets, screenshots, or gifs):
In Style guide:

occurrences of dots instead of ellipsis symbol replaced
stray whitespace in product var fixed
incorrect backticks in examples removed

prod/prev.:

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@janbrasna Thanks so much for opening a PR with these fixes! You've been on a streak 🔥 and we appreciate your help! I'll update the branch and get this merged once tests are passing 🍏

@nguyenalex836 Anytime;) Needed to look up some best practice, found discrepancies, and before fixing those ran into many more issues just reading through the page. So fixing those first one by one as they come;D
Good job keeping the community in the loop and opening up the site thru docs-as-code for collaboration ❤

@janbrasna We're grateful for the keen eyes 💛 ✨ Thank you for that feedback! I'll relay this to the rest of the team 🥳


Make Optional26 Packageable

I attempted to add Optional26 to the Conan local recipe index I am finishing up in https://github.com/beman-project/beman/pull/21.
Two problems (so far):

[ ] Optional26 needs tarball and/or zip releases.
[ ] Optional26 uses CMakeLists.txt that assumes dependencies, at least googletest are vendored into the repo via git submodule workflows

The first issue can be fairly trivially resolved by clicking using the release feature in the github.com web UI and cutting a release. Of course, an established process and even CI for this task would be great, including developing patterns and CI scripts that other beman projects could benefit from.
The second issue could be a matter of making the relevant add_subdirectory conditional somehow, using find_package workflows instead and adding googletest as a package dependency in Conan to ensure it's available to build against. It's also possible that using FetchContent instead of git-submodules would make the packaging "work", but Conan is designed such that it does source code indexing and fetching, so I would prefer to adhere to that design when using Conan.

Hello @bretbrownjr !

The first issue can be fairly trivially resolved by clicking using the release feature in the github.com web UI and cutting a release. Of course, an established process and even CI for this task would be great, including developing patterns and CI scripts that other beman projects could benefit from.

I propose to discuss on Monday in the Beman sync. I think we should have an unified approach (including scripts, CI jobs) for releases.

The second issue could be a matter of making the relevant add_subdirectory conditional somehow, using find_package workflows instead and adding googletest as a package dependency in Conan to ensure it's available to build against. It's also possible that using FetchContent instead of git-submodules would make the packaging "work", but Conan is designed such that it does source code indexing and fetching, so I would prefer to adhere to that design when using Conan.

I created  #29 29. Does this help as an intial step?

@bretbrownjr , #29 was merged. I think we need to update the issue description.


Not able to run this blueprint

when i try to run the command  "jhipster --blueprints quarkus" i get the following error.

INFO! Using bundled JHipster
INFO! No custom sharedOptions found within blueprint: generator-jhipster-quarkus at C:/Users/ig06152/AppData/Roaming/nvm/v16.19.1/node_modules/generator-jhipster-quarkus
INFO! No custom commands found within blueprint: generator-jhipster-quarkus at C:/Users/ig06152/AppData/Roaming/nvm/v16.19.1/node_modules/generator-jhipster-quarkus
(node:3556) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./lib/util/" in the "exports" field module resolution of the package at C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\node_modules\yeoman-environment\package.json.
Update this package.json to use a subpath pattern like "./lib/util/*".
(Use node --trace-deprecation ... to show where the warning was created)
ERROR! This is a JHipster blueprint and should be used only like jhipster --blueprint quarkus
Error: This is a JHipster blueprint and should be used only like jhipster --blueprint quarkus
at module.exports.error (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster-quarkus\node_modules\generator-jhipster\generators\generator-base.js:1590:15)
at new module.exports (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster-quarkus\generators\app\index.js:13:18)
at Environment.instantiate (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\node_modules\yeoman-environment\lib\environment.js:806:23)
at Environment.create (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\node_modules\yeoman-environment\lib\environment.js:778:17)
at C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\cli\program.js:190:58
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Promise.all (index 0)
at async JHipsterCommand._lazyBuildCommandCallBack (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\cli\program.js:180:13)
at async JHipsterCommand._parseCommand (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\cli\jhipster-command.js:79:7)
at async JHipsterCommand.parseAsync (C:\Users\ig06152\AppData\Roaming\nvm\v16.19.1\node_modules\generator-jhipster\node_modules\commander\lib\command.js:917:5)

node version is 16.9.1
npm version 8.19.3
java version 11.0.18
i think that this is the same issue as #246 but it was supposedly fixed with the merge of #247. I am still having the same issues
@vishal423 send help

@ivanatdevoteam, can you please try against the main branch?

@vishal423 i installed the blueprint with the given command in the readme, im assuming it is using the main branch

@ivanatdevoteam , you have to follow instructions listed under this section of readme document. Let me know if that doesn't work.

@ivanatdevoteam , Can you please try against recently published version v2.0.0? I will keep the ticket open for your confirmation.

Closing the ticket as there is no response from the reporter. Feel free to comment if the issue is still reproducible.


Add response variable name for ParsePkgFn

Add response variable name for ParsePkgFn
Signed-off-by: blue-troy<EMAIL_ADDRESS>

Seems like this PR has not been finished yet and I can't get why this PR is necessary. Could you please describe the motivation for what you want to change? Maybe you should open an issue so that we can talk about it.

#382

It seems as a case for evolution of function.


Rename accessor to pix

Fixes #26

Codecov Report
Patch coverage: 80.64% and project coverage change: -0.03 :warning:

Comparison is base (7aeb046) 76.68% compared to head (b7a76ee) 76.66%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #27      +/-   ##
==========================================
- Coverage   76.68%   76.66%   -0.03%
==========================================
  Files           9        9
  Lines         592      617      +25
  Branches      141      150       +9
==========================================
+ Hits          454      473      +19
- Misses        112      118       +6
  Partials       26       26

Impacted Files
Coverage Δ

src/pandas_indexing/core.py
81.93% <37.50%> (-1.55%)
:arrow_down:

src/pandas_indexing/accessors.py
85.54% <95.65%> (+2.20%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Diagrams/cartoons for figures

@jclagarde you can update us here.

Figures Final.pdf

Closed with #412


Exclude associations from autoFetch

autoFetch is a really cool feature. But it can prove to be unpractical when returning far too much data, that is actually not needed.
Imagine having users and messages grouped into conversations with other participating users. Writing
user.getConversations({ autoFetch: true }, function (err, conversations) {
    // conersation.participants
    // conversation.messages
});

is really convenient, but it will return all messages for all conversations, even when they are not needed to display a overview of available conversations.
I would like to propose the following syntax:
user.getConversations({ autoFetch: [ 'participants' ] }, function (err, conversations) {
    // conversation.participants
});

The autoFetch will only include the associations given. If autoFetch is set to true, then just fetch all associations. If it is an array, only fetch the ones specified.

+1

+1


more checkpoints

I have two questions about pretraining LLaMA-2 13B with litGPT:
Configuration for epoch, max_tokens, and max_steps: In the litgpt/config_hub/pretrain/config.yaml, I see options for epoch, max_tokens, and max_steps. I have a value set for max_tokens, but not for epoch or max_steps. Whenever I try to set either of those, I get errors. Could someone help me understand how I should configure these values?
Checkpoint Saving: Right now, there’s only one checkpoint saved at the end of training. Is there a way to save checkpoints more frequently, like after each epoch or based on max_tokens?
Thank you in advance for any guidance! question here.

Hi there. These are good points, the settings for epochs and max_steps are there but not supported yet. So, right now, it's limited to setting the token number.

Checkpoint Saving: Right now, there’s only one checkpoint saved at the end of training. Is there a way to save checkpoints more frequently, like after each epoch or based on max_tokens?

I think you can do this via the train.save_interval setting.

Thank you very much for your quick response!
I have a follow-up question: how can I measure the time taken for each train.save_interval? Specifically, I’d like to log the cumulative training time at each checkpoint like  the training time at the final checkpoint.
Thank you!

Good question. That's currently not supported/implemented. You'd have to modify that in the training code here:
https://github.com/Lightning-AI/litgpt/blob/ec020646b961f281b1062ce87b714266400cf2fd/litgpt/pretrain.py#L384
The easiest way would be to move the training time computation, which is basically just
    train_time = time.perf_counter()
    fit(fabric, devices, state, train_dataloader, val_dataloader, out_dir, tokenizer_dir, train, eval)

    # Save final checkpoint
    save_checkpoint(fabric, state, tokenizer_dir, out_dir / "final" / "lit_model.pth")

    total_tokens = state["iter_num"] * train.micro_batch_size * model.max_seq_length * fabric.world_size

    # Print formatted output
    separator = "-" * 40
    fabric.print(separator)
    fabric.print("| Performance")
    fabric.print(f"| - Total tokens  : {total_tokens:,}")
    fabric.print(f"| - Training Time : {(time.perf_counter()-train_time):.2f} s")

up into the fit function

Thanks again for your prompt answer.
you mean:

Yes, that looks correct. I would set train.max_tokens to sth like 1000 and train.save_interval to sth like 250 to try it out before doing a larger run.

Thanks again for your help.
I added that to the code but still can not see any timing results. Attached are my cmd code, , an image of the added code, and a part of the result.

Hm, that's weird. Not sure why this is happening.
Did you install LitGPT with the pip development mode  (-e) so updates are reflected in general?
pip install -e ".[all]"

Otherwise, I am not sure, maybe the timing needs to be moved to a different place.

Arg, sorry ...  it's Friday afternoon and my brain is probably already in weekend mode. Actually, the train.save_interval is not based on max tokens but on steps. So it's probably never triggered. It should be a much smaller number. Maybe try 10 or so.

yup that works. Thank you so much

Just one more question: how can I calculate the relationship between steps and the number of tokens?

Just one more question: how can I calculate the relationship between steps and the number of tokens?

If the microbatch size is equal to the global batch size, I think it should be the following relationship:
max tokens = max_steps * batch_size * max_seq_length
(I think that's it, but I would verify this with a small example run)

Thank you

Hi Sebastian,
if I use the above code for big models such as llama3-70b or llama2-70b, I will get a NCCL communication error. is there anyway to modify this?
[rank31]:[E1114 18:35:13.955775341 ProcessGroupNCCL.cpp:607] [Rank 31] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=2603, OpType=ALLREDUCE, NumelIn=1, NumelOut=1, Timeout(ms)=1800000) ran for 1800007 milliseconds before timing out.
[rank31]:[E1114 18:35:13.956086452 ProcessGroupNCCL.cpp:1664] [PG 0 (default_pg) Rank 31] Exception (either an error or timeout) detected by watchdog at work: 2603, last enqueued NCCL work: 2603, last completed NCCL work: 2602.
[rank23]:[E1114 18:35:13.374590778 ProcessGroupNCCL.cpp:607] [Rank 23] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=2603, OpType=ALLREDUCE, NumelIn=1, NumelOut=1, Timeout(ms)=1800000) ran for 1800008 milliseconds before timing out.
[rank31]:[E1114 18:35:13.956122222 ProcessGroupNCCL.cpp:1709] [PG 0 (default_pg) Rank 31] Timeout at NCCL work: 2603, last enqueued NCCL work: 2603, last completed NCCL work: 2602.
[rank23]:[E1114 18:35:13.374876780 ProcessGroupNCCL.cpp:1664] [PG 0 (default_pg) Rank 23] Exception (either an error or timeout) detected by watchdog at work: 2603, last enqueued NCCL work: 2603, last completed NCCL work: 2602.
[rank31]:[E1114 18:35:13.956150272 ProcessGroupNCCL.cpp:621] [Rank 31] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[rank23]:[E1114 18:35:13.374912098 ProcessGroupNCCL.cpp:1709] [PG 0 (default_pg) Rank 23] Timeout at NCCL work: 2603, last enqueued NCCL work: 2603, last completed NCCL work: 2602.
[rank31]:[E1114 18:35:13.956188982 ProcessGroupNCCL.cpp:627] [Rank 31] To avoid data inconsistency, we are taking the entire process down.
[rank23]:[E1114 18:35:13.374938592 ProcessGroupNCCL.cpp:621] [Rank 23] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data.
[rank31]:[E1114 18:35:13.957892994 ProcessGroupNCCL.cpp:1515] [PG 0 (default_pg) Rank 31] Process group watchdog thread terminated with exception: [Rank 31] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=2603, OpType=ALLREDUCE, NumelIn=1, NumelOut=1, Timeout(ms)=1800000) ran for 1800007 milliseconds before timing out.
Exception raised from checkTimeout at ../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:609 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x96 (0x7fc7780cbf86 in /home/ubuntu/.local/lib/python3.10/site-packages/torch/lib/libc10.so)
frame #1: c10d::ProcessGroupNCCL::WorkNCCL::checkTimeout(std::optional<std::chrono::duration<long, std::ratio<1l, 1000l> > >) + 0x1d2 (0x7fc72a7f2f62 in /home/ubuntu/.local/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #2: c10d::ProcessGroupNCCL::watchdogHandler() + 0x233 (0x7fc72a7f99a3 in /home/ubuntu/.local/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
[rank23]:[E1114 18:35:13.374977809 ProcessGroupNCCL.cpp:627] [Rank 23] To avoid data inconsistency, we are taking the entire process down.
frame #3: c10d::ProcessGroupNCCL::ncclCommWatchdog() + 0x10c (0x7fc72a7fbd8c in /home/ubuntu/.local/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so)
frame #4:  + 0xdc253 (0x7fc7778b0253 in /lib/x86_64-linux-gnu/libstdc++.so.6)
frame #5:  + 0x94ac3 (0x7fc77c9e7ac3 in /lib/x86_64-linux-gnu/libc.so.6)
frame #6:  + 0x126850 (0x7fc77ca79850 in /lib/x86_64-linux-gnu/libc.so.6)


STM32H503: enabling RTC causes startup crashes and UB

Been banging my head against a wall about this for a while now.
I have the NUCLEO-H503RB. If I take the stm32h5 blinky example and make minimal changes:

change the chip to the H503RB
change task arena to 16384 or lower (to fit in the small memory of the H503)
change the blinky pin to PA5 to match the board

... then I get a hard fault somewhere during RCC init, sometimes; other times, I get corruption on the stack.
By default, RTC is enabled by default and is set to source from the LSI. If I change the example main as follows:
    let mut config = Config::default();
    config.rcc.ls = LsConfig::off();
    let peris = embassy_stm32::init(config);

then everything appears to be okay again.
The same thing happens if I use LsConfig::default_lse() (which should work, the Nucleo has an external crystal for LS on board).
I see there's a notice in the code that there's a similar issue with L5. Wonder if it's the same thing.

I've narrowed it down to these lines.
https://github.com/embassy-rs/embassy/blob/26fc17e8a7db0957896db28cb2299ab9cf89aea5/embassy-stm32/src/rcc/bd.rs#L206
Forcing a backup domain reset followed by immediate writes to RCC_BDCR is clearly problematic

I can't reproduce this on my NUCLEO-H503RB. Can you provide exact code (a branch on a fork for example) and exact cargo run command to reproduce? thanks!

I can't reproduce this on my NUCLEO-H503RB. Can you provide exact code (a branch on a fork for example) and exact cargo run command to reproduce? thanks!

Sorry, didn't see this until now, I'll provide something soon
I'm hoping I haven't damaged all my boards in some weird specific way...

@Dirbaio
https://github.com/tcbennun/nucleo-h503rb-minimal-rs

okay, I was able to reproduce the issue with your repo. thank you! :)
Turns out the issue is this gem of an errata. If I set memory.x to only use SRAM1 the corruption no longer happens.

I'm ... not sure how to workaround that.

Thank you so much for digging and finding that!
I'll need to work around it somehow, pretty mission critical. I reckon I can hack my use case so nothing critical is in SRAM2 at the point of backup domain reset (should only be during init). We shall see...


additional_bone_ids is None when loading .vrm models

Issue: When loading .vrm models additional_bone_ids is not initialized causing the program to crash on BasicModel.gd Line 117 .
Proposed solution: Call parent function BasicModel.scan_mapped_bones() from VRMModel.scan_mapped_bones(). This will enable VRMModel.scan_mapped_bones() to extend the original functionality of its parent while also setting additional_bone_ids.
Additional Notes: Thank you so much for all your great work on this project! Its truly great to see how well this project has come together!

Haven't tested this myself but this looks logical. Thanks for the PR!
By the way, assuming you were interested in testing out the .vrm functionality, the build that's in the Github releases section should be more or less stable. No automatic A-posing, that's only in the master branch, but the model can be A-posed manually using the LMB/RMB/scroll wheel


single positional indexer is out-of-bounds when init the futures

i get these messages when i run the  auto_trader
2024-04-24 11:07:15.391 | WARNING  | importlib._bootstrap:_call_with_frames_removed:241 - Optional: pip install shioaji[speed] for better performance.
WARNING:root:Run trader without holiday data.
WARNING:root:Cannot import test scripts from package.
2024-04-24 Wed 11:07:16.459|INFO: ————————————————————————————————————————————————————————————————————————————————————————————————————
2024-04-24 Wed 11:07:16.460|INFO: Current trader version is 1.12.23
FileNotFoundError: ./lib/ckey/sinopac_private.pem. Texts will not be decrypted.
2024-04-24 Wed 11:07:16.480|DEBUG: Starting new HTTPS connection (1): ws.api.cnyes.com:443
2024-04-24 Wed 11:07:16.529|DEBUG: https://ws.api.cnyes.com:443 "GET /ws/api/v1/charting/history?resolution=D&symbol=GI:DJI:INDEX&from=1713916800&to=1711324800 HTTP/1.1" 200 None
2024-04-24 Wed 11:07:16.531|WARNING: ==========put_call_ratio.csv不存在，無前一交易日的Put/Call Ratio==========
Response Code: 0 | Event Code: 0 | Info: host '<IP_ADDRESS>:80', hostname '<IP_ADDRESS>:80' IP <IP_ADDRESS>:80 (host 1 of 1) (host connection attempt 1 of 1) (total connection attempt 1 of 1) | Event: Session up
2024-04-24 Wed 11:07:16.645|DEBUG: Attempting to acquire lock<PHONE_NUMBER> on /Users/kyjita/.shioaji/contracts-1.2.3.pkl.lock
2024-04-24 Wed 11:07:16.646|DEBUG: Lock<PHONE_NUMBER> acquired on /Users/kyjita/.shioaji/contracts-1.2.3.pkl.lock
2024-04-24 Wed 11:07:16.975|DEBUG: Attempting to release lock<PHONE_NUMBER> on /Users/kyjita/.shioaji/contracts-1.2.3.pkl.lock
2024-04-24 Wed 11:07:16.975|DEBUG: Lock<PHONE_NUMBER> released on /Users/kyjita/.shioaji/contracts-1.2.3.pkl.lock
2024-04-24 Wed 11:07:17.030|INFO: 【kyjita_1】log-in successful!
2024-04-24 Wed 11:07:17.030|INFO: Stock account ID: 0326483
2024-04-24 Wed 11:07:17.030|DEBUG: Set Futures_Code_List
2024-04-24 Wed 11:07:17.032|INFO: Futures account ID: 1262319
Empty DataFrame
Columns: [name, Time, Open, High, Low, Close, Volume, Amount]
Index: []
2024-04-24 Wed 11:07:17.042|INFO: 權益總值: xxxx
2024-04-24 Wed 11:07:17.042|INFO: Margin available = 50000 (limit: 50000)
2024-04-24 Wed 11:07:17.043|ERROR: Catch an exception:
Traceback (most recent call last):
  File "/Users/kyjita/codebase/AutoTradingPlatform/trader/tasker.py", line 97, in runAutoTrader
    se.run()
  File "/Users/kyjita/codebase/AutoTradingPlatform/trader/executor.py", line 1353, in run
    all_futures = self.init_futures()
  File "/Users/kyjita/codebase/AutoTradingPlatform/trader/executor.py", line 582, in init_futures
    self.margin_table = self.get_margin_table().原始保證金.to_dict()
  File "/Users/kyjita/codebase/AutoTradingPlatform/trader/executor.py", line 1023, in get_margin_table
    df.columns = list(df.iloc[0, :])
  File "/Users/kyjita/.pyenv/versions/3.10.0/lib/python3.10/site-packages/pandas/core/indexing.py", line 1147, in __getitem__
    return self._getitem_tuple(key)
  File "/Users/kyjita/.pyenv/versions/3.10.0/lib/python3.10/site-packages/pandas/core/indexing.py", line 1652, in _getitem_tuple
    tup = self._validate_tuple_indexer(tup)
  File "/Users/kyjita/.pyenv/versions/3.10.0/lib/python3.10/site-packages/pandas/core/indexing.py", line 940, in _validate_tuple_indexer
    self._validate_key(k, i)
  File "/Users/kyjita/.pyenv/versions/3.10.0/lib/python3.10/site-packages/pandas/core/indexing.py", line 1554, in _validate_key
    self._validate_integer(key, axis)
  File "/Users/kyjita/.pyenv/versions/3.10.0/lib/python3.10/site-packages/pandas/core/indexing.py", line 1647, in _validate_integer
    raise IndexError("single positional indexer is out-of-bounds")
IndexError: single positional indexer is out-of-bounds
2024-04-24 Wed 11:07:17.046|DEBUG: futures_to_monitor: {}
2024-04-24 Wed 11:07:18.064|INFO: 登出系統: True
2024-04-24 Wed 11:07:18.064|DEBUG: End of tasker

how do i solve these

It looks like you don't have the 'indexMarging.csv' in your ./lib
I have solved this issue recently. You have to pull the latest version and execute the runCrawlIndexMargin() which is in the following file:
https://github.com/chrisli-kw/AutoTradingPlatform/blob/e508f900cffb5632150ee185a9ffafd347e60cdc/trader/tasker.py#L227
Then there should be a indexMarging.csv file in your lib folder.

It looks like you don't have the 'indexMarging.csv' in your ./lib I have solved this issue recently. You have to pull the latest version and execute the runCrawlIndexMargin() which is in the following file: https://github.com/chrisli-kw/AutoTradingPlatform/blob/e508f900cffb5632150ee185a9ffafd347e60cdc/trader/tasker.py#L227
Then there should be a indexMarging.csv file in your lib folder.

You can also execute python run.py -TASK crawl_index_margin


Cypress fails to connect to devTools after first test

Hello team :)
This issue started to occur yesterday. We test using firefox and yesterday firefox 124 was released, so maybe this is related. Locally everything works fine with firefox 124.
I think this is the most important line of the log below:

There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.

I hope this report is useful.

Done in 1.01s.
/opt/hostedtoolcache/node/18.19.1/x64/bin/npx cypress cache list
┌─────────┬──────────────┐
│ version │ last used    │
├─────────┼──────────────┤
│ 12.17.4 │ a minute ago │
└─────────┴──────────────┘
start server command "yarn fixtures:use"
current working directory "/home/ubuntu/actions-runner/_work/library/library/packages/e2e-system"
waiting on "http://localhost:8666/src/components/base-data" with timeout of 60 seconds
/usr/local/bin/yarn fixtures:use
yarn run v1.22.22
$ yarn concurrently -k -s first 'yarn preview --host' 'yarn server'
$ /home/ubuntu/actions-runner/_work/library/library/node_modules/.bin/concurrently -k -s first 'yarn preview --host' 'yarn server'
[1] $ node ./server/index.js
[0] $ vite preview --host
[1] :  Listening!
[0]   ➜  Local:   http://localhost:8666/
[0]   ➜  Network: [http://<IP_ADDRESS>:](http://<IP_ADDRESS>/)8666/

DevTools listening on ws://<IP_ADDRESS>:37065/devtools/browser/c2eda6b3-70d0-4cd1-a47a-94618d689951
[2111:0320/063143.494726:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
(node:2130) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:2130) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.

====================================================================================================

  (Run Starting)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        12.17.4                                                                        │
  │ Browser:        Firefox 124 (headless)                                                         │
  │ Node Version:   v16.20.1 (/home/ubuntu/actions-runner/externals/node16/bin/node)               │
  │ Specs:          165 found (alert-badge.cy.ts, alert-history-list.cy.ts, alert-notifications.cy │
  │                 .ts, alert-trigger-controls.cy.ts, alert-trigger-toggle.cy.ts, alert-triggers- │
  │                 list.cy.ts, analysts-sentiment.cy.ts, arbitrage-list.cy.ts, assets-list.cy.ts, │
  │                  base-data.cy.ts, bond-b...)                                                   │
  │ Searched:       cypress/e2e/**/*.cy.{js,jsx,ts,tsx}                                            │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  alert-badge.cy.ts                                                             (1 of 165)
Still waiting to connect to Firefox, retrying in 1 second (attempt 18/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 18/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 19/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 19/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 20/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 20/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 21/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 21/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 22/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 22/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 23/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 23/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 24/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 24/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 25/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 25/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 26/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 26/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 27/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 27/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 28/62)
Still waiting to connect to Firefox, retrying in 1 second (attempt 28/62)

  test
    ✓ compares the screenshot (4422ms)

  1 passing (4s)

  (Results)

  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Tests:        1                                                                                │
  │ Passing:      1                                                                                │
  │ Failing:      0                                                                                │
  │ Pending:      0                                                                                │
  │ Skipped:      0                                                                                │
  │ Screenshots:  1                                                                                │
  │ Video:        false                                                                            │
  │ Duration:     4 seconds                                                                        │
  │ Spec Ran:     alert-badge.cy.ts                                                                │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

  (Screenshots)

  -  /home/ubuntu/actions-runner/_work/library/library/packages/e2e-system/cypress/sc     (1280x720)
     reenshots/alert-badge.cy.ts/alert-badge.cy.ts-page.png

────────────────────────────────────────────────────────────────────────────────────────────────────

  Running:  alert-history-list.cy.ts                                                      (2 of 165)
There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.

Error: connect ECONNREFUSED <IP_ADDRESS>:41601
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)
Test run failed, code 1
More information might be available above
Cypress module has returned the following error message:
Could not find Cypress test run results
Error: Could not find Cypress test run results

Cypress: 12.7.4
Github action version: cypress-io/github-action@v5
I tried upgrading to the latest of both, but then I get another error. Also, the combination above worked up to yesterday.
Greetings from Switzerland!

@sawmurai
If the issue is due to Firefox 124, then you may be able to work around the issue by using a Cypress Docker image. You can lock your workflow for instance to Firefox 123 with cypress/browsers:node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1.
Your log shows you are using Ubuntu, however I could not see which GitHub runner version you are using. There is currently a roll-out of ubuntu-22.04 taking place (see https://github.com/actions/runner-images/pull/9532) which updates Firefox from 123 to 124. This version is not available everywhere at the moment and is in status "Deployment". The example https://github.com/cypress-io/github-action/actions/workflows/example-firefox.yml workflow is not showing any issue at this time, however this is still running on Firefox 123.
Node.js 16 reached end-of-life on Sep 11, 2023. Since cypress-io/github-action@v5 uses Node.js 16, it is no longer supported. cypress-io/github-action@v6 is the only currently supported version of the action. The error you are seeing

There was an error reconnecting to the Chrome DevTools protocol. Please restart the browser.
Error: connect ECONNREFUSED <IP_ADDRESS>:41601
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16)

is however unlikely to be caused the action.

@sawmurai
I can't reproduce any issue with Firefox 124 and Cypress 13.7.0 locally on Ubuntu 22.04 or Windows 11. I have however seen CircleCI hanging with Firefox 124.
There may be a compatibility issue between Firefox 124 and Cypress. If that is a general issue, then it would need to be logged to  https://github.com/cypress-io/cypress/issues. So far nobody else has reported any similar issue.

@MikeMcC399
Thank you for the quick response! I tried using the docker image you recommended, but strangely Cypress complained about firefox not being installed:
Output of cypress run step
Run cypress-io/github-action@v5
  with:
    browser: firefox
    working-directory: packages/e2e-system
    start: yarn fixtures:use
    wait-on: http://localhost:8666/src/components/base-data
    record: false
    publish-summary: true
    component: false
  env:
    VITE_APP_GENERATE_TOKEN_URL_SERVER: http://localhost:8080/token
    VITE_APP_GENERATE_TOKEN_URL: http://localhost:8080/token
    PROXY_PORT: 8080
    VITE_PORT: 8666
    PROXY_HOST: localhost
    CI: 1
    FRONTGATE_HOST: wss://<>/ws
/usr/bin/docker exec  eb16d3401dc4b49e8a0ab779c819ff7f2c2944ef3f0a0a9f0a5d54d95e2e4ef6 sh -c "cat /etc/*release | grep ^ID"
Cache Size: ~172 MB (180493164 B)
/bin/tar -xf /__w/_temp/dbd12bfb-4384-423b-bb4f-f71fe65c52e8/cache.tgz -P -C /__w/library/library -z
Cache restored successfully
/usr/local/bin/yarn --frozen-lockfile
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.91s.
/__t/node/18.19.1/x64/bin/npx cypress cache list
┌─────────┬───────────────────┐
│ version │ last used         │
├─────────┼───────────────────┤
│ 12.17.4 │ a few seconds ago │
└─────────┴───────────────────┘
/__t/node/18.19.1/x64/bin/npx cypress verify
[STARTED] Task without title.
[SUCCESS] Task without title.
Saving npm cache error: Path Validation Error: Path(s) specified in the action for caching do(es) not exist, hence no cache is being saved.
/bin/tar --posix -cf cache.tgz --exclude cache.tgz -P -C /__w/library/library --files-from manifest.txt -z
Failed to save: Unable to reserve cache with key cypress-linux-x64-0309b95e3436eda3ba9ba25d52a00622f91d163f7e8205e98e637ff6828f480b46df2053409a019a5d28b33f251526513be027ab5b0042c04c7a3e9cea4e9d21, another job may be creating this cache. More details: Cache already exists. Scope: refs/pull/4584/merge, Key: cypress-linux-x64-0309b95e3436eda3ba9ba25d52a00622f91d163f7e8205e98e637ff6828f480b46df2053409a019a5d28b33f251526513be027ab5b0042c04c7a3e9cea4e9d21, Version: f505cd510c21b306bf40fa93afa2c89cd39c4f64b1484f6c4510c045f410733e
start server command "yarn fixtures:use"
current working directory "/__w/library/library/packages/e2e-system"
waiting on "http://localhost:8666/src/components/base-data" with timeout of 60 seconds
/usr/local/bin/yarn fixtures:use
yarn run v1.22.19
$ yarn concurrently -k -s first 'yarn preview --host' 'yarn server'
$ /__w/library/library/node_modules/.bin/concurrently -k -s first 'yarn preview --host' 'yarn server'
[1] $ node ./server/index.js
[0] $ vite preview --host
[1] :  Listening!
[0]   ➜  Local:   http://localhost:8666/
[0]   ➜  Network: [http://<IP_ADDRESS>:](http://<IP_ADDRESS>/)8666/
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[976:0320/091640.550635:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

DevTools listening on ws://<IP_ADDRESS>:42727/devtools/browser/0cee565d-d734-43f7-880b-04c2405bb3ac
(node:996) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:996) ExperimentalWarning: The Node.js specifier resolution flag is experimental. It could change or be removed at any time.
Can't run because you've entered an invalid browser name.

Browser: firefox was not found on your system or is not supported by Cypress.

Cypress supports the following browsers:
 - electron
 - chrome
 - chromium
 - chrome:canary
 - edge
 - firefox

You can also use a custom browser: https://on.cypress.io/customize-browsers

Available browsers found on your system are:
 - chrome
 - edge
 - electron
Can't run because you've entered an invalid browser name.

Browser: firefox was not found on your system or is not supported by Cypress.

Cypress supports the following browsers:
 - electron
 - chrome
 - chromium
 - chrome:canary
 - edge
 - firefox

You can also use a custom browser: https://on.cypress.io/customize-browsers

Available browsers found on your system are:
 - chrome
 - edge
 - electron
Test run failed, code 1
More information might be available above
Cypress module has returned the following error message:
Could not find Cypress test run results
Error: Could not find Cypress test run results

Not sure if I did something wrong, but I used it like so in the workflow file:
...

jobs:
  test:
    timeout-minutes: 60
    runs-on: ubuntu-latest
    container:
      image: cypress/browsers:node-20.11.0-chrome-121.0.6167.184-1-ff-123.0-edge-121.0.2277.128-1
    steps:
...

Should I then just go ahead and raise this issue again in the cypress repo?

@sawmurai

Thank you for the quick response! I tried using the docker image you recommended, but strangely Cypress complained about firefox not being installed:

That is a known issue, see https://github.com/cypress-io/cypress/issues/27121, also Firefox not found

You need to follow the documentation Docker image and add options: --user 1001 to your workflow. Firefox has security which prevents it from running as root.

Should I then just go ahead and raise this issue again in the cypress repo?

In the meantime the deployment has included this repo, so I could test with Firefox 124 and the test is passing. This means that Firefox 124 with Cypress is not completely broken.
My advice would be to first add the missing options: --user 1001 and check if your tests run, before deciding on any other next steps.

@sawmurai
There is a reproducible issue using the full set of Cypress examples, so I will log a new issue for this and link it back here. Stand by!

Now logged under https://github.com/cypress-io/cypress/issues/29172

@sawmurai

I suggest to close this issue as it is now covered by https://github.com/cypress-io/cypress/issues/29172

Closing as suggested. Thank you! :)

See<EMAIL_ADDRESS>for a fix for this issue.

Hi @MikeMcC399, been tracking this issue as currently you can't use this action with firefox without pinning a specific browser container version. Are you planning to make a release of this action in the near future that uses 13.7.1? Thanks

@ml-evs

Are you planning to make a release of this action in the near future that uses 13.7.1?

There is a misconception in your question. The action has no version of Cypress hard-coded in it. To use a specific version of
Cypress with the action you would install the version as a dependency. For example, if you are using npm as package manager
npm install<EMAIL_ADDRESS>--save-dev

This will put<EMAIL_ADDRESS>into your package.json and package-lock.json files. The action then uses package-lock.json to install your configured dependencies. See Installation .
So no, there are no plans to release the action to use 13.7.1, because a release is not necessary for this. The examples in this repo are already using 13.7.2 and will soon be updated to use 13.7.3.
If you need help from the Cypress technical community on using Cypress and / or this Cypress JavaScript GitHub Action, you are free to join the  (click on button).

Ahhh, gotcha, thanks for the help. I was confused by the commit that updated to 13.7.1 in this repo but that makes sense now.

@ml-evs

Ahhh, gotcha, thanks for the help. I was confused by the commit that updated to 13.7.1 in this repo but that makes sense now.

It's a little confusing because this repo contains the action AND examples for the action. The examples are used to test the action with current versions of Cypress and they serve as learning tools for anybody who would like to fork the repo and run the example workflows themselves.
I've just submitted a PR to update the examples once again. This time it is to update to Cypress 13.7.3 which was released yesterday.