ERROR: NO MEMORY

Hi,
I just finished assembling the MSX Unit on the Enhance backplane (Yellow 80 pins)
I have the following boards:
-Stock RC2014 Processor and Clock (Both tested to work under RomWBW)
-Video: V9958 (Having trouble with ODB GBS-C where the picture is flickering, getting an OSSC)
-Audio V1.9:  Does not work with the SST chip installed even though slt 3-1 is shorted. Problem for another day.
-Game Port
-Memory
When I turn the system on with the ODB GBS-C, I get flickering picture, a blue background and a one liner  error message:  ERROR: MEMORY NOT FOUND
I doubled check all the solder points etc., I cannot seem to find a smoking gun, I appreciate any insights you might have troubleshooting this, thank you.

Hi mate,
Sorry to hear you having some issues getting the MSX software to boot up.
You don't mention in your list of boards, the PPI/Keyboard module.  The PPI drives the keyboard, also drives the slot selections for RAM/ROM.  Is it installed?
And are the SLT LOW and SLT HIGH jumpers shorted on both the PPI and Memory Modules?
Dean.

I apologize for overlooking to mention the PPI and the keyboard.  They are both installed.  I attached a picture.
I shorted the SLT LOW and SLT HIGH but I get no video post as configured (Unless I am doing something silly which is probably the case).
I do get a Video Post with ERROR: NO MEMORY if the music card SST ship is removed and if the SLT short cable is not installed.

Cool.
A couple things first:

Just remove the MUSIC Module from the backplane until we get a good boot up.  It should boot up without the MUSIC module.
Since you are using the Yellow MSX backplane, you dont need to do the jumper wire between the PPI and Memory.  Just short across of the jumper pairs - and use the backplane's lines.  It may not resolve the issue - but it will simplify things a little.

I can send you a picture later to confirm.
The NO MEMORY message indicates that the ROM code is starting, but when it attempts to scan for RAM it fails.  This can be due for a few reason - eg the RAM not installed. But it can also be due to the bank switching not working.  So first thing is to check that the slot select signals are going from source (the PPI chip) to the Memory Module.  Have a look at the schematic and follow the SLT LOW/HIGH signals and with a millimetre tracing through and see if you have a good path between the points.  But also check they are isolated from other connections.

I do get a Video Post with ERROR: NO MEMORY if the music card SST ship is removed and if the SLT short cable is not installed.

This is a bit odd - and indicates something is getting crossed.  the MUSIC card should not have any impact during initial boot up.  Seems to indicate a cross connection or perhaps a short of something - and its kind of giving you a false positive.  Certainty focus on getting a working boot with it fully removed.
If you have a digital probe (and or an oscilloscope), I would monitoring the RAM CS select signals during boot - do they toggle during bootup?  Same with SLT-HIGH/LOW - do they toggle - check at both the bus lanes - but also at the input to the specific chips (again have a look at the schematics to identify the correct pins to inspect)

Thank you so much!, I do have an Oscilloscope, i will start the signal
tracking as per your directions.
I appreciate sending a picture to confirm the shorts pattern. Thank you.
On Tue, Sep 24, 2024 at 12:37 AM Dean Netherton @.***>
wrote:

Cool.
A couple things first:

Just remove the MUSIC Module from the backplane until we get a good
boot up. It should boot up without the MUSIC module.
Since you are using the Yellow MSX backplane, you dont need to do
the jumper wire between the PPI and Memory. Just short across of the jumper
pairs - and use the backplane's lines. It may not resolve the issue - but
it will simplify things a little.

I can send you a picture later to confirm.
The NO MEMORY message indicates that the ROM code is starting, but when it
attempts to scan for RAM it fails. This can be due for a few reason - eg
the RAM not installed. But it can also be due to the bank switching not
working. So first thing is to check that the slot select signals are going
from source (the PPI chip) to the Memory Module. Have a look at the
schematic and follow the SLT LOW/HIGH signals and with a millimetre tracing
through and see if you have a good path between the points. But also check
they are isolated from other connections.
I do get a Video Post with ERROR: NO MEMORY if the music card SST ship is
removed and if the SLT short cable is not installed.
This is a bit odd - and indicates something is getting crossed. the MUSIC
card should not have any impact during initial boot up. Seems to indicate a
cross connection or perhaps a short of something - and its kind of giving
you a false positive. Certainty focus on getting a working boot with it
fully removed.
If you have a digital probe (and or an oscilloscope), I would monitoring
the RAM CS select signals during boot - do they toggle during bootup? Same
with SLT-HIGH/LOW - do they toggle - check at both the bus lanes - but also
at the input to the specific chips (again have a look at the schematics to
identify the correct pins to inspect)
—
Reply to this email directly, view it on GitHub
https://github.com/dinoboards/yellow-msx-series-for-rc2014/issues/16#issuecomment-2370135292,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFRLDSTBCYNMN7GZEXE5NDZYDUAXAVCNFSM6AAAAABOXAS5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZQGEZTKMRZGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

I finally have a post! :)
Current error is :  ERROR: CALLED NON EXISTING BIOS

That's great to see.  What have you done resolve the previous errors?
I am not quite sure what the current state you have.  You state your current error is:
Current error is : ERROR: CALLED NON EXISTING BIOS
Did you by chance mean: CALLED NON EXISTING BASIC?
The screenshot shows CBIOS booting, then stopping with Cannot execute a BASIC ROM
Also I am unsure, are you using the Compact Flash Module?  If so, recommend removing that and attempting to boot just using the onboard ROM.
It does appear that the issue now is that the BIOS code has loaded, found some RAM - but then its not able to find/start Nextor (which it should as its embedded on the onboard ROM).  But if Nextor fails to initialise itself, then the bios will go hunting from another startup - since CBIOS does not include BASIC - you can get this error.
Why Nextor would not load though, I am not sure.  (Certaintly remove the Compact Flash if that is installed and give that a go)
If you have access to a programmer for the ROM (eg: a TL866 programmer) - then you can try download a ROM with basic included - ROM images can be downloaded from this repo's releases section (https://github.com/dinoboards/yellow-msx-series-for-rc2014/releases)

In regards to the pictures - sounds like you have it resolved.  My images attached here, should just using a short wire to jumper the user bus lines.  You can perhaps mount a shunt on each of the connector to achieve the same outcome

The error was indeed: Called non existing Basic.  sorry about that.
The issue previously was the jumpers between SLA_HIGH and SLA_LOW were not making good contact so that was that.  Thank you for pointing me to the source of the issue.
The jerkiness of the display was related to the ODV-GDS-C , I swapped  few VGA cable, one of them gave me stability thankfully.
I could not get basic to load no matter what with or without CF reader.  I followed your advise and uploaded another ROM with basic support(msxsyssrc-rc2014-usa-without-rtc.rom), the system does boot into MSX Basic now at last :)
Last hurdle now before I hit the sound card is The system is seeing ghost keyboard input contentiously scrolling through the screen even when the Keyboard is not attached to the PPI.  I will spend few cycles attempting to see if I wired anything incorrectly on the keyboard/PPI side.
I know at least that Shift works (menu is cycling) , Enter, up/down/left/right but pressing regular characters give me symbol letters, interesting fun :)

Sounds like you making some good progress.
You defiantly should be getting Nexor to boot though.  The keyboard issue might be related - as the PPI does drive bank switching, if the switching is not fully working - the bios may not be able to switch over to the Nextor bank.  That's my only guess at this stage.
So double check all your solder points and traces on the PPI and then the memory board.  And continue to avoid using Compact Flash module until you get the keyboard and Nextor booting.
Good luck

I think the system is in a better place now.  The sound card is detected, Keyboard appears to work and the system boots fully to the A> prompt.   I traced it to one bad capacitor (May be I killed it during soldering) and got more stability after I washed the boards with Alcohol.
Keyboard is not 100 % yet, I do get proper keys now instead of random scrolling garbage.  few keys are not working well which I am working through.

Thank you.
The machine works now, boots into MSX-DOS reliably, can load programs etc. including graphic etc.   That was truly insane! :)
I am still struggling a bit with the keyboard.  All keys are working reliably now and no longer printing multiple characters short of "r" which is consistently printing "mr" instead.  I will re-re-do all the solder points on the keyboard trying to find the culprit.  I appreciate any tips on how to diagnose these type of issues if you can.
Thank you once more for your support.
Regards,
Karim

The machine works now, boots into MSX-DOS reliably, can load programs etc. including graphic etc.  That was truly insane! :)

Fantastic news.  So glad to hear about your delight - I know the feeling.  Its so cool!

... multiple characters short of "r" which is consistently printing "mr" instead

Hmm. I tried to 'reason' the logic flow in the matrix of keys and diodes that might cause your specific issue -- its a challenge.  Almost certainly a short somewhere - perhaps a diode or switch etc.
First thing - as you state, check and reflow all the solder joints around the affected keys - consider the schematic (https://github.com/dinoboards/yellow-msx-series-for-rc2014/blob/main/keyboard/schematic.png)
If it the issue persists, then only advice I can give -- Disconnect keyboard.  Get your multimeter out.  and test, test and test again.
Have a look at the schematic and consider how the keyboard scanning happens.  The various ROWx lines are typically HIGH.  'Scanning' happens by:

Changing one of the 9 ROWx at a time, from HIGH to LOW.
As each specific row goes LOW, then the 8 COLUMNx lines are read

The corresponding column for the specific key should go LOW - and only that line.  M and R share the same row.  There may be a short somewhere that's allowing the column for M to activate when R is pressed.
The COLUMN lines are pulled HIGH by default (R4 bus resistor).  So they should all read HIGH, until a key is pressed and its ROW is currently LOW.  When its ROW is LOW, then its corresponding COLUMN (and only its COLUMN) should go LOW.
What happens when M is pressed?
Now there are a lots of diodes, so you need to make sure you have your multimeter polarity such that it will flow correctly.  (from positive column to negative row).
Check your measuring with some of the working keys first.  Then try to zoom into the fault.
If you do see the 2 COLUMNS going LOW in response to one key - you still have the challenge to figure out why.  I feel it must be a short across a diode or switch.  Since its only that one key giving you grief - it implies the other rows are good.  So not a logic chip issue - otherwise you would see other keys giving you issues.  Well maybe - sometimes things can be really weird... So no assumptions....
Have fun!

Thanks, this will be fun. I am already grateful all other keys are working now.
m and all other keys works fine.    I will keep you updated.
Best regards,
Karim

Hi Dean,
The keyboard is working perfectly finally.  I confess I have almost gave up few times.  I could not find a physical fault with it after a second soldering pass and a lengthy verification session with a Multimeter.  I cleaned it up thoroughly with Alcohol one more time and that somehow did it.  Oh well.  I am not complaining especially that I learned more about PPI/Keyboard logical design that I ever thought possible.
I think this build is now complete (honestly, against many odds :) especially my poor soldering skills and initially a severe lacking understanding of PPI/memory bank switching logic).
I really appreciate your patient coaching as I was working through completing this project.
I have purchased a cartridge slot extension kit to see if I can get my old MSX cartdridges to work once again. (F1 Spirit, Ping Pong, Salamander etc.) , see if my MSX disk drive still has some life in it and eventually built a wood case for the machine and the keyboard.
As a background, I grew up in Tunisia before migrating to the US. My first computer in the eighties was a Sakhr MSX1 AS-370 that I still own to this day and fire up at least once a year.  I learned Basic programming on it and to some extent English (Needed to translate the programming book from English to French) , wrote few titles back then like MSX-Draw and few office tools like inventory management, invoicing and crude flyers/catalogue creation tools that my dad used to run his factory for over a decade thus this project really meant a lot to me :)
Best regards,
Karim Benayed

I was never able to perfectly fix the initial keyboard.  there were always 2 keys that would not work well, R and right key.  I messed up with that keyboard initially and had to unsolder something, I may have damaged the board somehow, no matter for now, the new keyboard and controller are working perfectly.
I have a display question though.  Although initially Dos and Games are working perfectly, when on dos mode, the text returned from command like dir are garbled a bit.  I have to go to basic, issue screen 2 for example , call system then dir "a:" would return correct text.    I am curious if you have seen that.
Thank you.

Hi,  a correction, I noticed that the text gets corrupted in msx-dos only when the text reaches the end of the screen and scrolling starts. once the lines start to scroll up then the display gets corrupted. I appreciate any hints if you can think of any.
Thank you.

Hi Mate,
sorry for the late reply.
Your current issue sounds a bit odd.
Nothing immediately comes to mind as to cause.
Typically when i have an issue like this, its usually related to software - the code is driving the VDP too fast - causing corruptions.  I doubt this is your issue though
Have you tried running any other graphics programs?
Try to minimise the build configuration - eg: remove the Music and Sio/2 module - and any other optional modules.
Also, if possible, try with a new ROM image downloaded from this repo's releases.
Dean

absolutely no worries, after some fiddling, I decided to check the clock speed which was actually the culprit, I accidentally had set it to 3.6.   setting it back to 2.45 solved the issue.  I somehow completely missed that.
Thank you again for your support.  The build is now complete, I will share some pictures soon.
Regards,
Karim

Good to hear its working - but it should work find at the 3.6Mhz setting - in fact for the CBIOS ROM image, I had patched the code to enable operating the VDP with the CPU running at 7Mhz.
Its possible something regressed in my software.  I will need to reconfigure my rig and reproduce your setup and see if I can reproduce.
Typically the MSX operate at around the 3.5/3.6Mhz range - so everything should and needs to work at that frequency.
Cheers
Dean

I managed to build the  kernel locally.  the yellow-msx-ntsc/pal-rc2-14.rom was produced and is working well.
The Country-with/without-rtc generates a -main.rom , -opt.rom and -subrom.rom.  it does not generate a file with just ...rtc.rom.
Did I miss a step somehow ?  I apologize if this is a silly question and that I missed a documentation section.
Regards,
Karim

Hi Karim
No need to apologise.
Not sure what process you have followed - as that is a file name that doesn't seem right to me.  Did you use the docker wrapper command/process - or try to build directly?
Unless you want to modify the code or change configuration, you can download pre-built images.  There a lots of images  available in the Release section of this repo.
In particular: https://github.com/dinoboards/yellow-msx-series-for-rc2014/releases/tag/24-09-08
Download the msx-rc2014-24-09-08.zip  - there you will find various builds for different countries with/without RTC support.
Dean

i take it all back.  I was looking at files like:  usa-with-rtc-main.rom   and missed the fact that I needed to look at:  msxsyssrc-rc2014-usa-with-rtc.rom type files.   I apologize.  Docker is building just fine

It seems the new build does not have the scrolling text corruption. My testing was interrupted unfortunately as the repeated removal and putting back of the ROM IC damaged the IC socket pins.  Tried to unsolder it and solder a new one the board became instable. I ordered a new one for now while troubleshooting with direct wirings

That's great news.  Well done.  It's always possible!
I have yet to send your new kit.  I am not sure if I can manage refund in
tindie.  Happy to try if U want.  Otherwise I will parcel it up tonight my
time
On Wed, Nov 6, 2024, 9:28 AM kbenayed @.***> wrote:

Hey, I fixed the card! I managed to trace the wires and zero on the
culprit! I am no longer having scroll issues or boot problems. I cannot
believe I managed to fix it after what I had it go through!. I know I order
the additional card which is fine I guess, it may not be stable in the long
run. I am very happy at the moment :)
—
Reply to this email directly, view it on GitHub
https://github.com/dinoboards/yellow-msx-series-for-rc2014/issues/16#issuecomment-2458266533,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDRG3PSIZXTTDSQPXSYCP4TZ7FA7HAVCNFSM6AAAAABOXAS5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJYGI3DMNJTGM
.
You are receiving this because you commented.Message ID:
@.***>

Thank you for the option,  I appreciate shipping it still.  You never know especially that I am still experimenting with Rom code and all at the moment. It is always good knowing I have a backup as I am very active on this system.  Really thank you for designing it and building it.  It is an amazing learning experiment.
Regards,
Karim

Hi,
I confirm that while using the Turbo CPU board
Turbo: 7.3
Clock1: 3.6
Clock2: 0.3
and Turbo switch set to:
Position 1 (lower to ground) :  MSX-DOS/Basic,  no text corruption
Position 2:  (Middle) MSX-DOS/Basic, no corruption.
Position 3: (Top from ground)  MSX-DOS/Basic:  Same corruption I see with RC2014 Stock CPU and Clock at 3.5
I hope that help.   I have a fully functional system now and the Rom Board is fully stable.  Thank you again so much!   I am up to try enabling networking now.
Best regards,
Karim

I also had the text corruption issues (as well as the compatibility issues). I ended up replacing the main oscillator on Turbo board with a 7.15909MHz crystal. That fixed all of the corruption and most of the compatibility issues I had. There is a proper clock signal coming out of pin 9 of the V9958 that can be wired to the upper leg of the 47ohm resistor(R5) to give the CPU, as long as you remove the original 7.3728MHz oscillator. That will interfere with overclocking, though. Replacing it with the slightly slower one will still allow overclocking to work.
Here are the ones I ordered;
https://www.aliexpress.com/item/3256804928269823.html?spm=a2g0o.order_list.order_list_main.23.21ef1802YcVzSA

Sorry to hear of the issues.
There should be no video corruption during scrolling of the standard 80
column or 40 column text screen modes, at any cpu frequency, using the
msxdos or cbios rom images.
It's not something I have observed on my test rigs.  I have tested with
various VDPs .
Very strange.  Something odd happening here.  I need to investigate this a
bit more to see if I can reproduce
Dean
On Sun, Nov 10, 2024, 5:30 PM zomgugoff @.***> wrote:

I also had the text corruption issues (as well as the compatibility
issues). I ended up replacing the main oscillator on Turbo board with a
7.15909MHz crystal. That fixed all of the corruption and most of the
compatibility issues I had. There is a proper clock signal coming out of
pin 9 of the V9958 that can be wired to the upper leg of the 47ohm
resistor(R5) to give the CPU, as long as you remove the original 7.3728MHz
oscillator. That will interfere with overclocking, though. Replacing it
with the slightly slower one will still allow overclocking to work.
Here are the ones I ordered;
https://www.aliexpress.com/item/3256804928269823.html?spm=a2g0o.order_list.order_list_main.23.21ef1802YcVzSA
—
Reply to this email directly, view it on GitHub
https://github.com/dinoboards/yellow-msx-series-for-rc2014/issues/16#issuecomment-2466608161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADIL7VCLIEUI5EZ7GZBVBTZ734R7AVCNFSM6AAAAABOXAS5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGYYDQMJWGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Ok - done some testing
I had completely forgotten about the need to ensure that the 1 CPU Wait State is enabled for MSX software.  This is enabled via the PPI module (short the jumper).  The Turbo CPU will generate the required wait state as needed, so the jumper on the PPI is not needed for the PPI module when using the Turbo CPU.
RC2014 stock CPU with Stock Clock Module

Tested with Clock @7.3728Mhz and @3.6864Mhz
Ensure the Jumper is shorted on the PPI module (this generates the required CPU Wait State)*
The CBIOS image (NTSC) scroll just fine in text 80 mode just fine
Corruption will happen if the wait state is not enabled.
The MSX-DOS image only works at the 3.6864Mhz Freq
without the wait state enabled - scroll corruption will be observed.
On boot up - the boot text should indicate the correct speed of the CPU, with M1 stated if the wait state is being generated. eg: CPU: 3.5Mhz (M1)

* The PPI must have the wait state jumper enabled, or corruption may happen and some programs may have compatibility issues.
Turbo CPU (20Mhz Turbo Clock and 7.3728Mhz secondary crystal

Clk 1 shorted for 3.6864Mhz (2nd junction one from top)
Slow clock jumper shorted J1
Turbo shorted to fast (top junction)
Boot up reports 3.5Mhz (M1) if slider at top
Boot up reports 20Mhz (M3) if slider in middle
Boot up reports 20Mhz (M1) if slider at bottom
No text corruption observed during scrolling for both MSX-DOS and CBIOS rom images.

I tested with ROM images from release 24-09-08
I don't recommend enabling the M1 junction on the PPI when using the Turbo CPU.  I did not observe corruptions when doing this, but it does 'conflict' a bit with the calculations for CPU frequency.
Can you please advise what revision of the Turbo CPU you have - in case there is some regression specific to a particular revision.
Dean

I'm assuming this wasn't aimed at me, but I got to looking at my PPI board because I was confused about the wait state jumper you mentioned. I apparently installed a disc capacitor in J2 when I built the card! I haven't had any issues since replacing the crystal, but I guess I need to put a pin header in J2.

Hi zomgugoff,
Thank you, I will keep that in mind.

I also had the text corruption issues (as well as the compatibility issues). I ended up replacing the main oscillator on Turbo board with a 7.15909MHz crystal. That fixed all of the corruption and most of the compatibility issues I had. There is a proper clock signal coming out of pin 8 of the V9958 that can be wired to the upper leg of the 47ohm resistor(R5) to give the CPU, as long as you remove the original 7.3728MHz oscillator. That will interfere with overclocking, though. Replacing it with the slightly slower one will still allow overclocking to work.
Here are the ones I ordered: https://www.aliexpress.com/item/3256804928269823.html?spm=a2g0o.order_list.order_list_main.23.21ef1802YcVzSA

@kbenayed - thanks for the images.
I do not know how, but your boot up image showing a CPU speed with no M1 wait state is not what should be seen.
In all configurations, we need the M1 wait state enabled.  There are 2 ways to enable this wait state:

By shorting the jumper on the PPI module (which from your image I can see is applied)
By using the Turbo CPU, which includes the wait state generator on board.

Its not recommended to have both generators enabled - so I recommend you remove the jumper from the PPI module.
I did test with the jumper shorted and using the Turbo CPU - and I still see on my rig, the M1 wait state reported on boot up.  So I am very confused as to how your system reports no wait state at all.
Maybe try a few things for me:

Using the Turbo CPU, and removing the jumper from the PPI - boot up with the turbo's slider in each of the position - and note done what CPU frequency and wait states are reported - you should see: { 3.5Mhz (M1), 20Mhz (M3) and 20Mhz (M1) }
If you still have your stock RC2014 CPU and clock module, swap the Turbo CPU for those and re-insert the jumper into the PPI module - and note its reported CPU speed on boot.

Dean

I tested all requested used cased, I still have no M1.  I tried the older PPI card I had (the older keyboard that had few issues) and the M1 is there!   I swear I have soldered the new card really well, I will troubleshoot it later.  at the moment with this setup , I have no corruption at all!!!
So the issue was the new PPI card all along somehow. I will try to troubleshooted more tonight an confirm.
Thank you for the information that the PPI J2 setting is the key issue here.  I will get to the bottom of it.
Regards,
Karim

Ok.  So that's is interesting.  I need to think about this and review my
schematics
It seems like that maybe the wait state is being held/forced high all the
time
But there is still something not quite adding up to me here.
A bit to walkthrough.  I am afk at the moment.  When I get a chance I will
send some more analysis of what I think might be going on here.
Dean
On Tue, Nov 12, 2024, 6:51 AM kbenayed @.***> wrote:

I tested all requested used cased, I still have no M1. I tried the older
PPI card I had (the older keyboard that had few issues) and the M1 is
there! I swear I have soldered the new card really well, I will
troubleshoot it later. at the moment with this setup , I have no corruption
at all!!!
So the issue was the new PPI card all along somehow. I will try to
troubleshooted more tonight an confirm.
Thank you for the information that the PPI J2 setting is the key issue
here. I will get to the bottom of it.
Regards,
Karim
—
Reply to this email directly, view it on GitHub
https://github.com/dinoboards/yellow-msx-series-for-rc2014/issues/16#issuecomment-2468916531,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDRG3PXE3OVSS5AVQI2R75L2AEDEJAVCNFSM6AAAAABOXAS5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRYHEYTMNJTGE
.
You are receiving this because you commented.Message ID:
@.***>

Hi Dean,
I am hoping for one more guidance opportunity from you.  I got the Wifi module built, connected to Wifi and modified with both resistors as you recommended and connected to RTS.
I am kinda stuck on how it is meant to be interacted with from MSX concept wise.  I think I need to install UNAPI Serial:

run driver.com  (strangely lands me on basic then have to call system)
run inl I to install the unapi driver which seems to load

I am not sure how is this supposed to go from here as I am not getting an IP address via DHCP on the MSX side and could not figure out how to establish a serial connection from Telnet.
I appreciate your guidance ont the concepts here if you have a moment as my internet searches confused me a bit. Thank you.
Regards,
Karim

Hi there
Sorry, I am overseas at the moment on holiday.  It's a little difficult to
write up a good reply for u.  I will be home from Jan 1.  So will try and
give you a some hints/guidance then.
Cheers Dean
On Tue, 24 Dec 2024, 1:21 pm kbenayed, @.***> wrote:

Hi Dean,
I am hoping for one more guidance opportunity from you. I got the Wifi
module built, connected to Wifi and modified with both resistors as you
recommended and connected to RTS.
I am kinda stuck on how it is meant to be interacted with from MSX concept
wise. I think I need to install UNAPI Serial:

run driver.com (strangely lands me on basic then have to call
system)
run inl I to install the unapi driver which seems to load

I am not sure how is this supposed to go from here as I am not getting an
IP address via DHCP on the MSX side and could not figure out how to
establish a serial connection from Telnet.
I appreciate your guidance ont the concepts here if you have a moment as
my internet searches confused me a bit. Thank you.
Regards,
Karim
—
Reply to this email directly, view it on GitHub
https://github.com/dinoboards/yellow-msx-series-for-rc2014/issues/16#issuecomment-2560668219,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDRG3PV6OQB7CFVMKNPCBMT2HDVONAVCNFSM6AAAAABOXAS5BGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRQGY3DQMRRHE
.
You are receiving this because you commented.Message ID:
@.***>


The function does work after deployed.

Hi @tongueroo
Thanks for your great work.
I have deployed rails app on aws lambda using jets deploy command.
It worked on locally but after deployed without any issues it does work and when I call the function, it shows this error message.
{
    "message": "Internal server error"
}

I have checked Cloudwatch logs and I found this log.
18:19:39
RubyError: Errno::EAFNOSUPPORT: Failed to open TCP connection to localhost:9292 (Address family not supported by protocol - socket(2) for "localhost" port 9292)
RubyError: Errno::EAFNOSUPPORT: Failed to open TCP connection to localhost:9292 (Address family not supported by protocol - socket(2) for "localhost" port 9292)

18:19:39
/var/lang/lib/ruby/2.5.0/net/http.rb:939:in `rescue in block in connect'

Could you please fix this issue for me?
Thank you.
/var/lang/lib/ruby/2.5.0/net/http.rb:939:in `rescue in block in connect'

I am using the latest Jets version.

I saw your work on https://github.com/tongueroo/jets/pull/247.
But on my side, it does show.

Hi,
It seems your rails app are trying to connect to the localhost:9292 via TCP. Of course, you are getting the error because lambda function cannot access localhost.
What service are you using at 9292 port?
I think you have to change your env variables for deployment

Hi @galetahub
Thanks for reaching me.
Here, localhost:9292 means 9292 port on AWS which Jets provide as a default.
Am I sth wrong?

Anyway, I have fixed this issue.
The original issue was -
/opt/ruby/gems/2.5.0/gems/execjs-2.7.0/lib/execjs/runtimes.rb:58:in autodetect': Could not find a JavaScript runtime. See https://github.com/rails/execjs for a list of available runtimes. (ExecJS::RuntimeUnavailable)`
I have moved the uglifier and coffee-rails gems in the development group.
This helped me. :)

Ah, now I see.


chore: add cargo:rustc-check-cfg for __abi-embed-checked feature in near-sdk-macros build.rs

Thank you for looking into it! ❤
I will merge it as is since main branch CI fails anyway
@race-of-sloths include

@dj8yfo Thank you for your contribution! Your pull request is now a part of the Race of Sloths!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

🔄 The PR has been merged.

[!IMPORTANT]
This pull request is a part of the Race of Sloths and has not been scored yet. Scoring will close in 24 hours! 🕰

✅ PR is finalized!
Your contribution is much appreciated with a final score of 2!
You have received 20 Sloth points for this contribution


remove {en:original} from RARBG queries

I discovered that querying RARBG with "{title:en:original} {year}" doesn't return results in some cases.
removing en & original mitigates the issue and RARBG returns results just fine.
for example "A Quiet Place Part II", you can try for yourself.
thanks.

@ShlomiD83
this seems to be unlikely.
original means to use untranslated title, but for this movies it is the same as en.
and en means to use translated to en title, which again the same.
also since this tracker has "languages": "en", - we do not remove accents for en. and we never remove accents for original.

the issue with this movie is that tmdb has year as 2021 and rarbg has it as 2020 (from imdb, i guess) - so it gives no results for main query.
also in this case you fall into
        "movie_extra_fallback": "search_imdb",
        "movie_keywords_fallback": "{imdb_id}",

that uses imdb number so it finds this movie.
also note that sometimes rarbg simply does not return results - that's why sometimes all queries (including fallback) fail - so you do not have results.

Before removing en and original it searched in french and returned 0 results.

my bad, please disregard.

Before removing en and original it searched in french and returned 0 results.

this is strange. with rarbg burst should not use any other languages except en and original (for this movie - also en).

Before removing en and original it searched in french and returned 0 results.

this is strange. with rarbg burst should not use any other languages except en and original (for this movie - also en).

I think I was mistaken, please disregard.

ok.
anyway, just remember that sometimes rarbg simply does not return results - so you have to search again after small timeout.
happens often to me.

ok.
anyway, just remember that sometimes rarbg simply does not return results - so you have to search again after small timeout.
happens often to me.

Yeah, I know. It's a limitation of the API.


The Auth Server generates a Failed Initialization of the InMemoryReactiveClientRegistrationRepository on the oauth2-client side when combined with Reverse Proxy. Wrong issuer

The bug
As many of the people that decided to use this library i started by following the baeldung tutorial https://www.baeldung.com/spring-cloud-gateway-bff-oauth2.
Initial Setup 3 modules:

Spring Gateway
Spring Oauth2 Authorization Server
Spring Oauth2 Resource

Current Setup:

Spring Gateway with Spring addons dependency
Spring Oauth2 Authorization Server
Spring Oauth2 Resource
Nginx Reverse Proxy in a docker container

From here everything was working fine, then i added a nginx reverse proxy. The issue happens when the /auth/.well-known/oauth-authorization-server endpoint get accessed via the reverse proxy. The issuer is equal to http://localhost instead of this pattern: {scheme}://{reverse-proxy-uri}/auth. I assume there is some kind of issuer validation. Before adding the reverse proxy the gateway was accessing the auth server resulting into the issuer value matching on both sides.

Code sample
The Nginx config:
`
events {
worker_connections 1024;
}
http {
map $external_ip $external_ip {
    default "$EXTERNAL_IP";
}

server {
    listen 80;

    # Route for any path that starts with /auth (e.g., /auth, /auth/login, /auth/*)
    location /auth/ {
        rewrite ^/auth(/.*)$ $1 break;
        proxy_pass http://host.docker.internal:8484;
        proxy_set_header Host $host:${external_ip}/auth;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    location = /auth {
        rewrite ^/auth$ / break;
        proxy_pass http://host.docker.internal:8484;
    }

    location ~ ^((/bff(/.*)?)|(/login(/.*)?)|(/oauth2(/.*)?)|(/logout)|(/login-options))$ {
        proxy_pass http://host.docker.internal:8080;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

}
`
The Gateway configuration:
`
gateway-port: 8080
server:
port: ${gateway-port}
client-id: authorization-code-client
client-secret:
client-name: gateway-code-consent-flow
scheme: http
hostname: localhost
reverse-proxy-port: 7080
reverse-proxy-uri: ${scheme}://${hostname}:${reverse-proxy-port}
auth-server-prefix: /auth
issuer-uri: ${reverse-proxy-uri}${auth-server-prefix}
spring:
application:
name: ms_gateway
security:
oauth2:
client:
registration:
spring:
client-id: ${client-id}
client-secret: ${client-secret}
client-name: ${client-name}
provider: spring
scope:
- openid
- profile
- user.read
redirect-uri: "{baseUrl}/login/oauth2/code/{registrationId}"
client-authentication-method: "client_secret_basic"
authorization-grant-type: authorization_code
provider:
spring:
issuer-uri: ${issuer-uri}
com:
c4-soft:
springaddons:
oidc:
ops:
- iss: ${issuer-uri}
authorities:
- path: ${authorities-json-path}
aud: ${audience}
client:
client-uri: ${reverse-proxy-uri}${gateway-prefix}
security-matchers: ${client-security-matchers}
permit-all: ${client-permit-all}
csrf: cookie-accessible-from-js
oauth2-redirections:
rp-initiated-logout: ACCEPTED
resourceserver:
permit-all: ${resource-server-permit-all}
`
What would make the authorization server returns http://localhost as the issuer field value intead of the full proxy uri?

Thanks for getting in touch, but it feels like this is a question that would be better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add a minimal sample that reproduces this issue if you feel this is a genuine bug.
@rodrigosomoza This appears to be an environment related misconfiguration with nginx and Spring Authorization Server instead of a bug. I'm going to close this but please refer to my comment above.
Also, as an FYI, you might want to look at the latest SPA sample that was added in 1.4.


[bug]: Custom Themes not working

Describe the bug
I am trying to implement theme switching into my Next js 13.5.6 project. When i implement the basic light/dark mode it works fine, but as soon as i try to copy&paste shadcn's custom theme presets from their site, it doesn't work properly, seems like some parts still work but some don't (i think the parts that should be different color stop working). I am currently testing on a simple page with just shadcn's card and button components.
Here is the screenshot of the light&dark mode with default values when i run shadcn's npm install next-themes and i choose:

And here is after i copy and paste for example Yellow theme CSS file from https://ui.shadcn.com/themes to my globals.css:

Here are my current versions:
{   "name": "kickmyass",   "version": "0.1.0",   "private": true,   "scripts": {     "dev": "next dev",     "build": "next build",     "start": "next start",     "lint": "next lint"   },   "dependencies": {     "@clerk/nextjs": "^4.29.9",     "@doist/todoist-api-typescript": "^3.0.2",     "@hookform/resolvers": "^3.3.4",     "@radix-ui/react-dropdown-menu": "^2.0.6",     "@radix-ui/react-icons": "^1.3.0",     "@radix-ui/react-label": "^2.0.2",     "@radix-ui/react-select": "^2.0.0",     "@radix-ui/react-slot": "^1.0.2",     "@types/cookie": "^0.6.0",     "@uploadthing/react": "^6.4.0",     "class-variance-authority": "^0.7.0",     "clsx": "^2.1.0",     "encoding": "^0.1.13",     "libphonenumber-js": "^1.10.60",     "lucide-react": "^0.364.0",     "mongoose": "^8.2.2",     "next": "13.5.6",     "next-themes": "^0.3.0",     "openai": "^4.29.2",     "react": "^18",     "react-dom": "^18",     "react-hook-form": "^7.51.2",     "react-hot-toast": "^2.4.1",     "react-phone-number-input": "^3.3.12",     "supports-color": "^9.4.0",     "tailwind-merge": "^2.2.2",     "tailwindcss-animate": "^1.0.7",     "twilio": "^5.0.2",     "uploadthing": "^6.6.0",     "zod": "^3.22.4"   },   "devDependencies": {     "@types/node": "^20",     "@types/react": "^18",     "@types/react-dom": "^18",     "autoprefixer": "^10",     "postcss": "^8",     "tailwindcss": "^3",     "typescript": "^5"   } }
This is my simple layout.tsx:

And this is globals.css:
`@tailwind base;
@tailwind components;
@tailwind utilities;
@layer base {
:root {
--background: 0 0% 100%;
--foreground: 20 14.3% 4.1%;
--card: 0 0% 100%;
--card-foreground: 20 14.3% 4.1%;
--popover: 0 0% 100%;
--popover-foreground: 20 14.3% 4.1%;
--primary: 47.9 95.8% 53.1%;
--primary-foreground: 26 83.3% 14.1%;
--secondary: 60 4.8% 95.9%;
--secondary-foreground: 24 9.8% 10%;
--muted: 60 4.8% 95.9%;
--muted-foreground: 25 5.3% 44.7%;
--accent: 60 4.8% 95.9%;
--accent-foreground: 24 9.8% 10%;
--destructive: 0 84.2% 60.2%;
--destructive-foreground: 60 9.1% 97.8%;
--border: 20 5.9% 90%;
--input: 20 5.9% 90%;
--ring: 20 14.3% 4.1%;
--radius: 0.5rem;
}
.dark {
--background: 20 14.3% 4.1%;
--foreground: 60 9.1% 97.8%;
--card: 20 14.3% 4.1%;
--card-foreground: 60 9.1% 97.8%;
--popover: 20 14.3% 4.1%;
--popover-foreground: 60 9.1% 97.8%;
--primary: 47.9 95.8% 53.1%;
--primary-foreground: 26 83.3% 14.1%;
--secondary: 12 6.5% 15.1%;
--secondary-foreground: 60 9.1% 97.8%;
--muted: 12 6.5% 15.1%;
--muted-foreground: 24 5.4% 63.9%;
--accent: 12 6.5% 15.1%;
--accent-foreground: 60 9.1% 97.8%;
--destructive: 0 62.8% 30.6%;
--destructive-foreground: 60 9.1% 97.8%;
--border: 12 6.5% 15.1%;
--input: 12 6.5% 15.1%;
--ring: 35.5 91.7% 32.9%;
}
}
@layer base {
* {
@apply border-border;
}
body {
@apply bg-background text-foreground;
}
}`
Affected component/components
Everything
How to reproduce
Don't have to do anything as i am trying from a blank page with a simple shadcn component. Just searching what's the reason.
Codesandbox/StackBlitz link
No response
Logs
No response
System Info
OS - MacOS
Browser - Chrome/Safari - same problem

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

I tried everything, in the end the solution for my specific case was to reinstall components as well. So the steps were:

delete node_modules + package-lock
npm install
delete components/ui (basically all of shadcn's components from before)
npx shadcn-ui@latest init
reinstall every shadcn component you need/use
npm install next-themes
add custom themes to globals.css

That's it, and it fixed the problem for me

I tried everything, in the end the solution for my specific case was to reinstall components as well. So the steps were:

delete node_modules + package-lock
npm install
delete components/ui (basically all of shadcn's components from before)
npx shadcn-ui@latest init
reinstall every shadcn component you need/use
npm install next-themes
add custom themes to globals.css

That's it, and it fixed the problem for me

Thanks, I faced the same problem and it worked for me. I was working on a new project and simply did rm -rf <project_directory>. and used a new name for the project. Something related to npm cache perhaps as I messed up the installation a bit the first time.


Bugfix: unsafe precondition(s) violated: slice::from_raw_parts requir…

…es the pointer to be aligned and non-null, and the total size of the slice not to exceed isize::MAX
https://github.com/OSSystems/compress-tools-rs/issues/128

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.826%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
341

Relevant Lines:
402

💛  - Coveralls

The proposed change looks great. However that is a couple of points that need to be improved prior to merging:

A test to confirm that the issue is fixed
A changelog entry

Is it possible for it to take a look at those items?


Uncaught Error: Cannot read property 'object' of undefinedTypeError: Cannot read property 'objec...

[Enter steps to reproduce:]

...
...

Atom: 1.17.0 x64
Electron: 1.3.15
OS: Microsoft Windows 10 Home
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (C:\Users\mike\AppData\Local\atom\app-1.17.0\resources\electron.asar\browser\objects-registry.js:41:28)
at EventEmitter. (C:\Users\mike\AppData\Local\atom\app-1.17.0\resources\electron.asar\browser\rpc-server.js:306:31)
at emitMany (events.js:127:13)
at EventEmitter.emit (events.js:201:7)
at WebContents. (C:\Users\mike\AppData\Local\atom\app-1.17.0\resources\electron.asar\browser\api\web-contents.js:222:13)
at emitTwo (events.js:106:13)
at WebContents.emit (events.js:191:7)
At C:\Users\mike\AppData\Local\atom\app-1.17.0\resources\electron.asar\renderer\api\remote.js:217

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (~/AppData/Local/atom/app-1.17.0/resources/electron.asar/browser/objects-registry.js:41:28)
    at EventEmitter.<anonymous> (~/AppData/Local/atom/app-1.17.0/resources/electron.asar/browser/rpc-server.js:306:31)
    at emitMany (events.js:127:13)
    at EventEmitter.emit (events.js:201:7)
    at WebContents.<anonymous> (~/AppData/Local/atom/app-1.17.0/resources/electron.asar/browser/api/web-contents.js:222:13)
    at emitTwo (events.js:106:13)
    at WebContents.emit (events.js:191:7)
    at metaToValue (~/AppData/Local/atom/app-1.17.0/resources/electron.asar/renderer/api/remote.js:217:13)
    at undefined.remoteMemberFunction (~/AppData/Local/atom/app-1.17.0/resources/electron.asar/renderer/api/remote.js:113:18)
    at AtomEnvironment.module.exports.AtomEnvironment.getWindowDimensions (~/AppData/Local/atom/app-1.17.0/resources/app/src/atom-environment.js:663:1)
    at AtomEnvironment.module.exports.AtomEnvironment.storeWindowDimensions (~/AppData/Local/atom/app-1.17.0/resources/app/src/atom-environment.js:697:1)
    at WindowEventHandler.module.exports.WindowEventHandler.handleWindowBlur (~/AppData/Local/atom/app-1.17.0/resources/app/src/window-event-handler.js:184:1)
    at ~/AppData/Local/atom/app-1.17.0/resources/app/src/window-event-handler.js:3:1

Commands
     -1:57.6.0 editor:move-to-end-of-screen-line (input.hidden-input)
 20x -1:56.7.0 core:move-left (input.hidden-input)
     -1:53.4.0 core:backspace (input.hidden-input)
     -1:50.7.0 core:copy (input.hidden-input)
     -1:49.1.0 core:paste (input.hidden-input)
     -1:35.8.0 core:move-right (input.hidden-input)
     -1:35.3.0 core:paste (input.hidden-input)
     -1:34.3.0 editor:move-to-end-of-screen-line (input.hidden-input)
  2x -1:33.9.0 core:move-left (input.hidden-input)
  2x -1:31.9.0 core:save (input.hidden-input)
  2x -1:17 core:copy (input.hidden-input)
     -1:06.8.0 core:paste (input.hidden-input)
     -1:05.5.0 core:save (input.hidden-input)
     -0:33 editor:newline (input.hidden-input)
     -0:31.3.0 core:backspace (input.hidden-input)
     -0:30.3.0 core:save (input.hidden-input)

Non-Core Packages
atom-beautify 0.29.14
atom-material-ui 1.3.8

Duplicate of #11692 again?

Thanks for taking the time to contribute!
We noticed that this is a duplicate of #11692. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Cross-Attention maps

How to visualize Cross-Attention Maps for text prompts in fig1 (b)?
Hi, I would like to ask how to visualize prompts for a given picture using VPD, could you please help me with it?

Hi, the visualization code is from Prompt-to-Prompt, please refer to their repo for detailed instructions.
Please also feel free to ask here if there is still any trouble.

@wl-zhao Hi, could you please specify which file/line it is?

See here


[WIP] Dynamic favicon w/counter

Adds a events / clients / stashes counter to the favicon dynamically. Currently a bit buggy of an implementation; may be within the favicon.js library itself.
Fixes #227

Closing this for now. Will copy the work over and reopen against https://github.com/sensu/uchiwa-web.


how to subscribe a collection many times with difference parameters ?

Let say, when app first start, I do this subscribe
[_subscriptionLoader addSubscriptionWithName:@"myCollection"];
it will return just a limited information.
And in next time, I want to get full information, I do this subscribe
[_subscriptionLoader addSubscriptionWithName:@"myCollection" parameters:@[_id]];
how can I force core data to update with new results ? It keeps showing results from the first run.

Core Data will update automatically, you can subscribe to the same publication as many times as you like with different parameters. If you are not seeing new results the problem is not with Core Data but with the way you are accessing the data or listening for updates.

I checked my server code, it returned correct results I want. Do I need to do anything else to tell the core data to update new results ? or it will update automatically ?


how to register or add the admin account?

hello, like your book, but how to register or add the administrator account?
can you give some advises?

You need to set the environment variable FLASKY_ADMIN to the email address of the administrator. When a user with that email signs up, they will be assigned the admin role.

In addition:
Notice miguel said 'When a user with that email signs up', that means u can only register an new account as administrator.
Because the operations setting role for a user were defined in User.init().
U can't set an existed user account to administrator, unless u change through  sqlite database immidiately.

@miguelgrinberg @AdamWangDoggie sorry to reply later. thanks million.


Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark errors on hot restart/hot reload

https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/44/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/57/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/27/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/23/overview
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/12/overview
 [2024-01-26 05:50:06.761587] [STDOUT] stdout: [        ] Performing hot restart...
 [2024-01-26 05:50:06.771117] [STDOUT] stdout: [   +9 ms] Scanned through 728 files in 8ms
 [2024-01-26 05:50:06.771208] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone...
 [2024-01-26 05:50:06.772572] [STDOUT] stdout: [   +1 ms] <- reset
 [2024-01-26 05:50:06.772621] [STDOUT] stdout: [        ] Compiling dart to kernel with 1 updated files
 [2024-01-26 05:50:06.772657] [STDOUT] stdout: [        ] Processing bundle.
 [2024-01-26 05:50:06.772754] [STDOUT] stdout: [        ] <- recompile package:flutter_gallery/main.dart 369c601b-9e95-46fa-8539-43fbf355cd80
 [2024-01-26 05:50:06.772840] [STDOUT] stdout: [        ] file:///opt/s/w/ir/x/t/edited_flutter_gallery/.dart_tool/flutter_build/dart_plugin_registrant.dart
 [2024-01-26 05:50:06.772854] [STDOUT] stdout: [        ] <- 369c601b-9e95-46fa-8539-43fbf355cd80
 [2024-01-26 05:50:06.774174] [STDOUT] stdout: [   +1 ms] Bundle processing done.
 [2024-01-26 05:50:06.804430] [STDOUT] stdout: [  +30 ms] Updating files.
 [2024-01-26 05:50:07.164176] [STDOUT] stderr: ERROR - 2024-01-26 05:50:07.163999
 [2024-01-26 05:50:07.164218] [STDOUT] stderr: PUT /cvAGasOHVbU=/
 [2024-01-26 05:50:07.164229] [STDOUT] stderr: Error thrown by handler.
 [2024-01-26 05:50:07.164237] [STDOUT] stderr: Connection reset by peer
 [2024-01-26 05:50:07.167345] [STDOUT] stderr: package:shelf/shelf_io.dart 138:16  handleRequest
 [2024-01-26 05:50:07.167363] [STDOUT] stderr:
 [2024-01-26 05:50:07.169786] [STDOUT] stdout: [ +365 ms] DevFS: Sync finished
 [2024-01-26 05:50:07.169830] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone... (completed in 398ms)
 [2024-01-26 05:50:07.169927] [STDOUT] stdout: [        ] Synced 40.5MB.
 [2024-01-26 05:50:07.170006] [STDOUT] stdout: [        ] <- accept
 [2024-01-26 05:50:07.200064] [STDOUT] stdout: [  +30 ms] [ERROR:flutter/shell/common/shell.cc(117)] Dart Error: Can't load Kernel binary: Invalid kernel binary: Indicated size is invalid.
 [2024-01-26 05:50:07.200129] [STDOUT] stdout: [        ] [ERROR:flutter/runtime/dart_isolate.cc(144)] Could not prepare isolate.
 [2024-01-26 05:50:07.202566] [STDOUT] stdout: [   +2 ms] Performing hot restart... (completed in 440ms)
 [2024-01-26 05:50:07.202612] [STDOUT] stdout: [        ] Restarted application in 507ms.
 [2024-01-26 05:50:07.223161] [STDOUT] stdout: [  +20 ms] [ERROR:flutter/runtime/runtime_controller.cc(462)] Could not create root isolate.
 [2024-01-26 05:50:17.207130] [STDOUT] stdout: [+9983 ms] Benchmarking hot reload
 [2024-01-26 05:50:17.209449] [STDOUT] stdout: [   +2 ms] Skipping target: gen_localizations
 [2024-01-26 05:50:17.210670] [STDOUT] stdout: [   +1 ms] Skipping target: gen_dart_plugin_registrant
 [2024-01-26 05:50:17.210843] [STDOUT] stdout: [        ] Skipping target: _composite
 [2024-01-26 05:50:17.210992] [STDOUT] stdout: [        ] complete
 [2024-01-26 05:50:17.212366] [STDOUT] stdout: [   +1 ms] Performing hot reload...
 [2024-01-26 05:50:17.239280] [STDOUT] stdout: [  +26 ms] Scanned through 728 files in 18ms
 [2024-01-26 05:50:17.239584] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone...
 [2024-01-26 05:50:17.243269] [STDOUT] stdout: [   +3 ms] Compiling dart to kernel with 0 updated files
 [2024-01-26 05:50:17.243387] [STDOUT] stdout: [        ] Processing bundle.
 [2024-01-26 05:50:17.243587] [STDOUT] stdout: [        ] <- recompile package:flutter_gallery/main.dart 03b92394-653e-4781-9d77-a8ea64667fb4
 [2024-01-26 05:50:17.243665] [STDOUT] stdout: [        ] <- 03b92394-653e-4781-9d77-a8ea64667fb4
 [2024-01-26 05:50:17.246260] [STDOUT] stdout: [   +2 ms] Bundle processing done.
 [2024-01-26 05:50:17.257259] [STDOUT] stdout: [  +10 ms] Updating files.
 [2024-01-26 05:50:17.294994] [STDOUT] stdout: [  +37 ms] DevFS: Sync finished
 [2024-01-26 05:50:17.295093] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone... (completed in 55ms)
 [2024-01-26 05:50:17.295126] [STDOUT] stdout: [        ] Synced 0.0MB.
 [2024-01-26 05:50:17.299998] [STDOUT] stdout: [   +4 ms] Reassembling application
 [2024-01-26 05:50:17.302670] [STDOUT] stderr: [   +2 ms] Reassembling main.dart$main-7718724522450007 failed: [Sentinel kind: Collected, valueAsString: <collected>] from ext.flutter.reassemble()
 [2024-01-26 05:50:17.302699] [STDOUT] stderr:            #0      new _OutstandingRequest (package:vm_service/src/vm_service.dart:265:34)
 [2024-01-26 05:50:17.302722] [STDOUT] stderr:            #1      VmService._call.<anonymous closure> (package:vm_service/src/vm_service.dart:1771:25)
 [2024-01-26 05:50:17.302741] [STDOUT] stderr:            #2      VmService._call (package:vm_service/src/vm_service.dart:1783:8)
 [2024-01-26 05:50:17.302759] [STDOUT] stderr:            #3      VmService.callServiceExtension (package:vm_service/src/vm_service.dart:1733:14)
 [2024-01-26 05:50:17.302777] [STDOUT] stderr:            #4      FlutterVmService._checkedCallServiceExtension (package:flutter_tools/src/vmservice.dart:868:28)
 [2024-01-26 05:50:17.302796] [STDOUT] stderr:            #5      FlutterVmService.invokeFlutterExtensionRpcRaw (package:flutter_tools/src/vmservice.dart:887:49)
 [2024-01-26 05:50:17.302814] [STDOUT] stderr:            #6      FlutterVmService.flutterReassemble (package:flutter_tools/src/vmservice.dart:728:12)
 [2024-01-26 05:50:17.302833] [STDOUT] stderr:            #7      _defaultReassembleHelper (package:flutter_tools/src/run_hot.dart:1450:63)
 [2024-01-26 05:50:17.302851] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.302869] [STDOUT] stderr:            #8      HotRunner._reloadSources (package:flutter_tools/src/run_hot.dart:1060:47)
 [2024-01-26 05:50:17.302886] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.302904] [STDOUT] stderr:            #9      HotRunner._hotReloadHelper (package:flutter_tools/src/run_hot.dart:928:16)
 [2024-01-26 05:50:17.302921] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.302938] [STDOUT] stderr:            #10     HotRunner.restart (package:flutter_tools/src/run_hot.dart:802:36)
 [2024-01-26 05:50:17.302955] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.302973] [STDOUT] stderr:            #11     HotRunner.attach (package:flutter_tools/src/run_hot.dart:345:7)
 [2024-01-26 05:50:17.302990] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303007] [STDOUT] stderr:            #12     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:806:27)
 [2024-01-26 05:50:17.303025] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303043] [STDOUT] stderr:            #13     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1398:27)
 [2024-01-26 05:50:17.303061] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303078] [STDOUT] stderr:            #14     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-01-26 05:50:17.303097] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303115] [STDOUT] stderr:            #15     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
 [2024-01-26 05:50:17.303132] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303151] [STDOUT] stderr:            #16     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:355:9)
 [2024-01-26 05:50:17.303169] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303186] [STDOUT] stderr:            #17     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-01-26 05:50:17.303204] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303222] [STDOUT] stderr:            #18     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:295:5)
 [2024-01-26 05:50:17.303240] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303257] [STDOUT] stderr:            #19     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
 [2024-01-26 05:50:17.303274] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303292] [STDOUT] stderr:            #20     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-01-26 05:50:17.303310] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303327] [STDOUT] stderr:            #21     main (package:flutter_tools/executable.dart:90:3)
 [2024-01-26 05:50:17.303344] [STDOUT] stderr:            <asynchronous suspension>
 [2024-01-26 05:50:17.303361] [STDOUT] stderr:
 [2024-01-26 05:50:17.303389] [STDOUT] stdout: [        ] Hot reload performed in 82ms.
 [2024-01-26 05:50:17.303408] [STDOUT] stdout: [        ] Performing hot reload... (completed in 90ms)
 [2024-01-26 05:59:11.109378] [STDOUT] stdout: [+533817 ms] mDNS query failed. Checking for an interface with a ipv4 link local address.
 [2024-01-26 05:59:11.112165] [STDOUT] stdout: [   +3 ms] Found interface "en8":
 [2024-01-26 05:59:11.112512] [STDOUT] stdout: [        ] 	Bound address: "<IP_ADDRESS>" link local
 [2024-01-26 05:59:11.112573] [STDOUT] stdout: [        ] Found interface "en0":
 [2024-01-26 05:59:11.112633] [STDOUT] stdout: [        ] 	Bound address: "<IP_ADDRESS>"
 [2024-01-26 05:59:11.112829] [STDOUT] stdout: [        ] An interface with an ipv4 link local address was found.

Mac_x64_ios hot_mode_dev_cycle_ios__benchmark does not appear to be having this problem.

fyi @godofredoc This is one of the tests you added to run on arm64 (it was previously only running on x64).

@bkonyi I was told you might have some insight into this or would know who might have insight into this

I'm not 100% sure without digging into the code, but it looks like we're trying to invoke a service extension on an isolate that no longer exists (that would result in a Collected Sentinel response).

@vashworth looks like this could potentially be an issue with the test, can you or somebody from the Flutter team investigate and confirm that.

@vashworth looks like this could potentially be an issue with the test, can you or somebody from the Flutter team investigate and confirm that.

I don't believe this is an issue with the test. The same test runs successfully on other platforms such as linux, windows, android. It also runs successfully on iOS devices on x86 mac bots. It only seems to fail on iOS device on arm64 bots.

//cc @bkonyi we probably need to investigate further

@vashworth is it possible to get a local reproduction of this on an iOS arm64 device so we can debug the issue.

Unfortunately it does not happen consistently - seems to happen 1-2 times every 50 builds. If you want to run the test locally, you can run
cd flutter/dev/devicelab
dart bin/test_runner.dart test -t hot_mode_dev_cycle_ios__benchmark -d [physical-ios-device-id]

If you're wanting specific logs or information, perhaps we can get it uploaded through CI - let me know

So I'm not sure I'll be able to reproduce this since I'm still using an Intel MacBook. However, there's a couple of things in the logs that are concerning.
First of all, there's this output on stderr:
 [2024-01-26 05:50:07.164176] [STDOUT] stderr: ERROR - 2024-01-26 05:50:07.163999
 [2024-01-26 05:50:07.164218] [STDOUT] stderr: PUT /cvAGasOHVbU=/
 [2024-01-26 05:50:07.164229] [STDOUT] stderr: Error thrown by handler.
 [2024-01-26 05:50:07.164237] [STDOUT] stderr: Connection reset by peer
 [2024-01-26 05:50:07.167345] [STDOUT] stderr: package:shelf/shelf_io.dart 138:16  handleRequest

This happens between Updating files and DevFS: Sync finished. I'm not sure where this shelf handler error is coming from, but I'm guessing it's related to the failure.
Afterwards, we accept the compilation and attempt to create the new isolate, where we see the following errors from the engine:
 [2024-01-26 05:50:07.200064] [STDOUT] stdout: [  +30 ms] [ERROR:flutter/shell/common/shell.cc(117)] Dart Error: Can't load Kernel binary: Invalid kernel binary: Indicated size is invalid.
 [2024-01-26 05:50:07.200129] [STDOUT] stdout: [        ] [ERROR:flutter/runtime/dart_isolate.cc(144)] Could not prepare isolate.
 [2024-01-26 05:50:07.202566] [STDOUT] stdout: [   +2 ms] Performing hot restart... (completed in 440ms)
 [2024-01-26 05:50:07.202612] [STDOUT] stdout: [        ] Restarted application in 507ms.
 [2024-01-26 05:50:07.223161] [STDOUT] stdout: [  +20 ms] [ERROR:flutter/runtime/runtime_controller.cc(462)] Could not create root isolate.

It looks like the kernel that was sent to the device is invalid, since "Indicated size is invalid" is reported when the kernel loader finds a program file start index that's less than 0. This results in us being unable to start the new isolate with the updated kernel. We then see the stack trace from package:vm_service since the isolate we were communicating with has been destroyed as part of the hot restart, which will cause a collected sentinel to be returned for any request made against the old isolate's ID.
I think we need to identify where the shelf error is being output to figure out what's going on here. My gut tells me that something's corrupting the kernel being generated by the compilation server, but I'm not 100% sure.

@vashworth can you try passing --no-dds to the flutter run command for the benchmark and see if that resolves the failure? I'm not sure why DDS would be encountering a Connection reset by peer exception in this case, but it's the only in the tool that hosts a Shelf server that I can see. If that fixes the issue, we'll need to add additional logging in DDS to get a better idea of which connection is failing.

@vashworth can you try passing --no-dds to the flutter run command for the benchmark and see if that resolves the failure? I'm not sure why DDS would be encountering a Connection reset by peer exception in this case, but it's the only in the tool that hosts a Shelf server that I can see. If that fixes the issue, we'll need to add additional logging in DDS to get a better idea of which connection is failing.

Sorry for the delay, I added the --no-dds flag (https://github.com/flutter/flutter/pull/145335). I'll monitor the test (https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark) and see if it fixes

Sounds good. If that fixes the crash, we'll want to add some logging in DDS to try and figure out why we're seeing this.

Looks like it's still crashing, but the error is a little different
https://ci.chromium.org/ui/p/flutter/builders/staging/Mac_arm64_ios hot_mode_dev_cycle_ios__benchmark/1037/overview
[2024-03-22 03:09:30.251677] [STDOUT] stdout: [+9815 ms] Running in benchmark mode.
 [2024-03-22 03:09:30.251762] [STDOUT] stdout: [        ] Benchmarking hot restart
 [2024-03-22 03:09:30.257736] [STDOUT] stdout: [   +6 ms] Skipping target: gen_localizations
 [2024-03-22 03:09:30.259289] [STDOUT] stdout: [   +1 ms] Skipping target: gen_dart_plugin_registrant
 [2024-03-22 03:09:30.259454] [STDOUT] stdout: [        ] Skipping target: _composite
 [2024-03-22 03:09:30.259814] [STDOUT] stdout: [        ] complete
 [2024-03-22 03:09:30.261683] [STDOUT] stdout: [   +1 ms] Performing hot restart...
 [2024-03-22 03:09:30.288549] [STDOUT] stdout: [  +26 ms] Scanned through 729 files in 24ms
 [2024-03-22 03:09:30.288735] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone...
 [2024-03-22 03:09:30.292401] [STDOUT] stdout: [   +3 ms] <- reset
 [2024-03-22 03:09:30.292428] [STDOUT] stdout: [        ] Compiling dart to kernel with 0 updated files
 [2024-03-22 03:09:30.292564] [STDOUT] stdout: [        ] Processing bundle.
 [2024-03-22 03:09:30.292803] [STDOUT] stdout: [        ] <- recompile package:flutter_gallery/main.dart f277623b-5f53-4ffa-99d6-47cfb801cefa
 [2024-03-22 03:09:30.292818] [STDOUT] stdout: [        ] <- f277623b-5f53-4ffa-99d6-47cfb801cefa
 [2024-03-22 03:09:30.295306] [STDOUT] stdout: [   +2 ms] Bundle processing done.
 [2024-03-22 03:09:30.324914] [STDOUT] stdout: [  +29 ms] Updating files.
 [2024-03-22 03:09:30.667895] [STDOUT] stdout: [ +343 ms] Error writing "main.dart.dill" to DevFS: SocketException: Write failed (OS Error: Broken pipe, errno = 32), address = <IP_ADDRESS>, port = 51551
 [2024-03-22 03:09:30.667914] [STDOUT] stdout: [        ] trying again in a few - 9 more attempts left
 [2024-03-22 03:09:31.550653] [STDOUT] stdout: [ +882 ms] DevFS: Sync finished
 [2024-03-22 03:09:31.550671] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone... (completed in 1,261ms)
 [2024-03-22 03:09:31.550773] [STDOUT] stdout: [        ] Synced 40.9MB.
 [2024-03-22 03:09:31.550892] [STDOUT] stdout: [        ] <- accept
 [2024-03-22 03:09:31.551951] [STDOUT] stdout: [   +1 ms] error: HttpException: Connection closed while receiving data, uri = http://<IP_ADDRESS>:51545/vMxhdoVfvrI=/
 [2024-03-22 03:09:31.576207] [STDOUT] stdout: [  +24 ms] [ERROR:flutter/shell/common/shell.cc(117)] Dart Error: Can't load Kernel binary: Invalid kernel binary: Indicated size is invalid.
 [2024-03-22 03:09:31.577914] [STDOUT] stdout: [   +1 ms] Performing hot restart... (completed in 1,316ms)
 [2024-03-22 03:09:31.577990] [STDOUT] stdout: [        ] Restarted application in 1,324ms.
 [2024-03-22 03:09:31.578357] [STDOUT] stdout: [        ] [ERROR:flutter/runtime/dart_isolate.cc(146)] Could not prepare isolate.
 [2024-03-22 03:09:31.578365] [STDOUT] stdout: [        ] [ERROR:flutter/runtime/runtime_controller.cc(487)] Could not create root isolate.
 [2024-03-22 03:09:41.582706] [STDOUT] stdout: [+10003 ms] Benchmarking hot reload
 [2024-03-22 03:09:41.584988] [STDOUT] stdout: [   +2 ms] Skipping target: gen_localizations
 [2024-03-22 03:09:41.586311] [STDOUT] stdout: [   +1 ms] Skipping target: gen_dart_plugin_registrant
 [2024-03-22 03:09:41.586501] [STDOUT] stdout: [        ] Skipping target: _composite
 [2024-03-22 03:09:41.586708] [STDOUT] stdout: [        ] complete
 [2024-03-22 03:09:41.588299] [STDOUT] stdout: [   +1 ms] Performing hot reload...
 [2024-03-22 03:09:41.618005] [STDOUT] stdout: [  +29 ms] Scanned through 729 files in 21ms
 [2024-03-22 03:09:41.618301] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone...
 [2024-03-22 03:09:41.622259] [STDOUT] stdout: [   +4 ms] Compiling dart to kernel with 0 updated files
 [2024-03-22 03:09:41.622393] [STDOUT] stdout: [        ] Processing bundle.
 [2024-03-22 03:09:41.622768] [STDOUT] stdout: [        ] <- recompile package:flutter_gallery/main.dart ffae8438-ab1a-486e-b3f6-2327551534ea
 [2024-03-22 03:09:41.622787] [STDOUT] stdout: [        ] <- ffae8438-ab1a-486e-b3f6-2327551534ea
 [2024-03-22 03:09:41.625152] [STDOUT] stdout: [   +2 ms] Bundle processing done.
 [2024-03-22 03:09:41.633529] [STDOUT] stdout: [   +8 ms] Updating files.
 [2024-03-22 03:09:41.664667] [STDOUT] stdout: [  +31 ms] DevFS: Sync finished
 [2024-03-22 03:09:41.664871] [STDOUT] stdout: [        ] Syncing files to device swarming’s iPhone... (completed in 46ms)
 [2024-03-22 03:09:41.664890] [STDOUT] stdout: [        ] Synced 0.0MB.
 [2024-03-22 03:09:41.669500] [STDOUT] stdout: [   +4 ms] Reassembling application
 [2024-03-22 03:09:41.671454] [STDOUT] stderr: [   +1 ms] Reassembling main.dart$main-8751169646345199 failed: [Sentinel kind: Collected, valueAsString: <collected>] from ext.flutter.reassemble()
 [2024-03-22 03:09:41.671472] [STDOUT] stderr:            #0      new _OutstandingRequest (package:vm_service/src/vm_service.dart:265:34)
 [2024-03-22 03:09:41.671482] [STDOUT] stderr:            #1      VmService._call.<anonymous closure> (package:vm_service/src/vm_service.dart:1772:25)
 [2024-03-22 03:09:41.671492] [STDOUT] stderr:            #2      VmService._call (package:vm_service/src/vm_service.dart:1784:8)
 [2024-03-22 03:09:41.671502] [STDOUT] stderr:            #3      VmService.callServiceExtension (package:vm_service/src/vm_service.dart:1733:14)
 [2024-03-22 03:09:41.671512] [STDOUT] stderr:            #4      FlutterVmService._checkedCallServiceExtension (package:flutter_tools/src/vmservice.dart:868:28)
 [2024-03-22 03:09:41.671522] [STDOUT] stderr:            #5      FlutterVmService.invokeFlutterExtensionRpcRaw (package:flutter_tools/src/vmservice.dart:887:49)
 [2024-03-22 03:09:41.671532] [STDOUT] stderr:            #6      FlutterVmService.flutterReassemble (package:flutter_tools/src/vmservice.dart:728:12)
 [2024-03-22 03:09:41.671542] [STDOUT] stderr:            #7      _defaultReassembleHelper (package:flutter_tools/src/run_hot.dart:1435:63)
 [2024-03-22 03:09:41.671551] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671578] [STDOUT] stderr:            #8      HotRunner._reloadSources (package:flutter_tools/src/run_hot.dart:1045:47)
 [2024-03-22 03:09:41.671588] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671598] [STDOUT] stderr:            #9      HotRunner._hotReloadHelper (package:flutter_tools/src/run_hot.dart:913:16)
 [2024-03-22 03:09:41.671607] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671616] [STDOUT] stderr:            #10     HotRunner.restart (package:flutter_tools/src/run_hot.dart:787:36)
 [2024-03-22 03:09:41.671625] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671635] [STDOUT] stderr:            #11     HotRunner.attach (package:flutter_tools/src/run_hot.dart:338:7)
 [2024-03-22 03:09:41.671644] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671654] [STDOUT] stderr:            #12     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:833:27)
 [2024-03-22 03:09:41.671664] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671673] [STDOUT] stderr:            #13     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1394:27)
 [2024-03-22 03:09:41.671682] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671707] [STDOUT] stderr:            #14     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-03-22 03:09:41.671719] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671729] [STDOUT] stderr:            #15     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
 [2024-03-22 03:09:41.671738] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671748] [STDOUT] stderr:            #16     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:360:9)
 [2024-03-22 03:09:41.671758] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671768] [STDOUT] stderr:            #17     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-03-22 03:09:41.671778] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671787] [STDOUT] stderr:            #18     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:300:5)
 [2024-03-22 03:09:41.671797] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671806] [STDOUT] stderr:            #19     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:119:9)
 [2024-03-22 03:09:41.671815] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671824] [STDOUT] stderr:            #20     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:153:19)
 [2024-03-22 03:09:41.671834] [STDOUT] stderr:            <asynchronous suspension>
 [2024-03-22 03:09:41.671843] [STDOUT] stderr:            #21     main (package:flutter_tools/executable.dart:94:3)
 [2024-03-22 03:09:41.671852] [STDOUT] stderr:            <asynchronous suspension>

Thanks for the update, it's good to know this isn't being caused by weirdness in DDS.
Digging through DevFS code in flutter_tools I found an issue referenced that might be related: https://github.com/dart-lang/sdk/issues/43525. It appears we've had issues with PUT requests on iOS before, but it was also impossible to reproduce. I think there's a chance this is the cause of the issue we're encountering, or at the very least related. If we're uploading an invalid dill file, the engine will fail to load it correctly and won't be able to spawn an isolate with the new code.
Maybe @brianquinlan will have some idea as to how we can try and reproduce this?

//cc @brianquinlan

I don't think that there is enough information here to diagnose this. @vashworth is it possible to add additional diagnostics to flutter_tools ?

Some of the error logs implicate this code:
This snippet, in particular, seems a bit suspicious to me:
          final HttpClientResponse response = await request.close().timeout(
            const Duration(seconds: 60));
          response.listen((_) {},
            onError: (dynamic error) {
              _logger.printTrace('error: $error');
            },
            cancelOnError: true,
          );

So we are:

not checking the HTTP response code
silently discarding errors
not waiting for the listener to complete (is the desired semantic: await response.drain().catchError((_) {})?)

In the logs on https://github.com/flutter/flutter/issues/142305#issuecomment-2015274692, we have:
error: HttpException: Connection closed while receiving data, uri = http://<IP_ADDRESS>:51545/vMxhdoVfvrI=/

So we are print an error because we disconnected to the remote but we discard the error, which means that the retry logic is not invoked.
Maybe the response handling code should look like:
          final HttpClientResponse response = await request.close().timeout(
            const Duration(seconds: 60));
          if (response.statusCode != 200) {
            throw new Exception('Excepted 200 response from DevFS, got ${response.statusCode}');
          }
         await response.drain();

It is possible that the remote isn't doing the right thing if a disconnect happens before the entire response body is transmitted.

//cc @christopherfujino

Any updates on this ?

Any updates on this ?

Removed dependency: dart, as it looks like this is a tool bug. This is not currently assigned, however we will probably need to fix this eventually--when we do, we should try the change proposed in: https://github.com/flutter/flutter/issues/142305#issuecomment-2026233076


Fixes version stamping. Closes #4194

Fixes version stamping. Closes #4194

Merged manually, thank you very much!


Otterize network-mapper invalid URL escape

We're trying to use otterize network-mapper with rancher based cluster, which has cluster:server field in kubeconfig that looks like this
clusters:
- cluster:
    server: https://RANCHER_URL/k8s/clusters/CLUSTER_NAME
  name: CLUSTER_NAME

However when running otterize network-mapper list we're getting the below error
Error: error upgrading connection: error creating request: parse "https://<RANCHER_URL>%2Fk8s%2Fclusters%2FCLUSTER_NAME/api/v1/namespaces/otterize-system/pods/otterize-network-mapper-65b5b9c654-tkgvq/portforward": invalid URL escape "%2F"

We use cli in version 1.0.1
otterize version -> Version: v1.0.1

Hi @jonaszlasut, looking at this now, and seem to be unable to reproduce with the same configuration, however I have an idea of what might be the cause anyway. Can I ask you to join us on Slack at https://joinslack.otterize.com and have you try a binary from a branch?

Hi @orishoshan , I've joined the slack. How can I contact you?

H @orishoshan I've sent you a slack message

It worked for @jonaszlasut - published in v1.0.2.


Add some API_LEVEL property to history objects

Given e.g. changes to the semantics around listen (rather than full-fledge API changes that could be sniffed through duck-typing), it would be nice if we tagged created history objects with some sort of API_LEVEL (e.g. 30 for history v3).
Especially if we go ahead with #322, and let people do withBasename(history, basename), it'd give us a good way to prevent subtle bugs arising from using incompatible enhancers and history objects.
Right now, in React Router, we sniff history.getCurrentLocation to detect v3 histories (which React Router v2 doesn't support), but it might be nice to have a more explicit way to do this: https://github.com/reactjs/react-router/blob/v2.5.2/modules/Router.js#L18-L21

On second thought, I've come to terms with sniffing for getCurrentLocation for now.


Let user specify uncons

It's useful, for example, for using the library with Text or Vector, but introduces no new dependencies.

ping

Oh, also I'm not sure about the naming — just having a prime at the end is not very descriptive. Perhaps ...With or ...WithUncons?

Sorry, forgot about it.
Mostly looks good, apart from some minor comments.
Also, have you checked if List.uncons gets inlined and the resulting core looks the same as it did before?

All relevant functions (including List.uncons) have unfoldings in the interface file, so they should be expanded inline. I also benchmarked before and after and the performance is the same.


RPM created with distRpm does not install on RedHat 7.x

Using
./gradle ./gradlew distRpm
cp distributions/anet-2.1.33~133~g529c3de10-2.x86_64.rpm /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm

[root@test-ansible-redhat76-01 ~]# yum localinstall /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm
Loaded plugins: langpacks, product-id, search-disabled-repos
Examining /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm: anet-2.1.33~133~g529c3de10-2.x86_64
Marking /opt/ansible/anet/anet-2.1.33-133-g529c3de10-2.x86_64.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package anet.x86_64 0:2.1.33~133~g529c3de10-2 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================================================================================================================
 Package                               Arch                                    Version                                                  Repository                                                             Size
====================================================================================================================================================================================================================
Installing:
 anet                                  x86_64                                  2.1.33~133~g529c3de10-2                                  /anet-2.1.33-133-g529c3de10-2.x86_64                                  115 M

Transaction Summary
====================================================================================================================================================================================================================
Install  1 Package

Total size: 115 M
Installed size: 115 M
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test

Transaction check error:
  file /etc/systemd from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64
  file /etc/systemd/system from install of anet-0:2.1.33~133~g529c3de10-2.x86_64 conflicts with file from package systemd-219-62.el7_6.16.x86_64

Error Summary
-------------

Probably caused because the RPM tries to create folders like: /etc/systemd & /etc/systemd.
Source: https://serverfault.com/questions/775647/installing-rpm-package-to-systemd/775653

Installation is fixed, remaining issue is: #3323


Remove IE11 warning message in Wagtail admin

Is your proposal related to a problem?
We still have our "Wagtail has removed support for IE11" warning message in the admin UI, even though Wagtail no longer supports IE11 since a few versions ago. I think it would be nice to remove it now.
Describe the solution you'd like
We need to remove the block from the template: https://github.com/wagtail/wagtail/blob/main/wagtail/admin/templates/wagtailadmin/skeleton.html#L79-L85
And also remove the initIE11Warning files, as well as the IS_IE11 constant in our configuration.

Hello , can I work on this issue?


How to Implement OAuth for a Bot-Based Message Extension App in Microsoft Teams for Graph API?

I have created a bot-based message extension app using the Teams Toolkit and need to call the Microsoft Graph API, which requires OAuth implementation. So far, I have created the app in the Teams Developer Portal, registered the app in Azure App registration, and registered the bot in the Bot Framework Developer Portal (dev.botframework.com). However, I am unclear about the OAuth flow and the specific configurations required.
Can someone provide a detailed guide on how the OAuth flow works for a bot-based message extension in Microsoft Teams, the specific configurations needed in the Azure app registration, how to configure permissions and consent for accessing the Microsoft Graph API, and any additional settings required in the Teams Developer Portal or Bot Framework Developer Portal?
Any guidance, code examples, or references to detailed documentation would be highly beneficial.

Hi @purvasanap2001 - Thanks for raising the query.
We will look into it and let you know the updates.


Does this action work for branches protected by merge queues?

This is not tested, in theory it should work - it's a matter of testing and ensuring the required status checks are run.


Add "extern c" for cpp use

Thank you for the library, works out of the box !
I will try to help to add some parameters and maybe interruptions

Please keep linter fine :)

Oops, sorry. Corrected

Thanks for the pull request. Merging now.

@Oliv4945 BTW, do you have any thought about how to wrap this module into c++ class?
After wrapping it into class, it's possible to add proper automatic testing and examples of great code with hardware abstractions.

I depend if you want to maintain both C and C++ interface. In my opinion it is cleaner to provide only C++ code but has we discuss about embedded code you will find lot of points of views :)
First step is obviously a wrapper, I might do one one day but I have other "functional" PR to do before

@Oliv4945 Thing is I am not so experienced in embedded development, but for stm32 it's tricky to add C++ implementation of the class. I think C implementation is first priority, and C++ can be added as a separate code.
Also, do you have any ideas about how to make a package from this code in C or C++? In Rust there is cargo tool to build and manage dependencies. Any ideas about it?

Agreed, having a complete C implementation is better than partial C and C++ :) That is why I am working on a PR to save calibration values, it will avoid re-calibration every power-on.
C and C++ are old languages which have not been designed for dependency management; you have to use third party tools.  This article introduction is a nice summary: difficult to do as their is so many tools :) However CMake is doing a nice job for that


Backport? (copy) the applicable parts of "New Tower credential types"

https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/9
This was revealed by a test failure on the Network Credential in https://github.com/ManageIQ/manageiq/pull/15594 and took forever to debug.
I don't know what else may be missing, but that should be it for https://github.com/ManageIQ/manageiq-providers-ansible_tower/pull/9
This is yet another reason to merge https://github.com/ManageIQ/manageiq/pull/15594 since the part that is tested would have been exposed much earlier on.
cc @carbonin @Fryguy @jrafanie

@bdunne I have one already there waiting https://github.com/ManageIQ/manageiq/pull/15558 😄

@jameswnl They should be two PR's since they're unrelated

@miq-bot add_labels fine/yes

@miq-bot remove_label bug
@miq-bot add_labels enhancement
Correcting the label: this is a planned feature enhancement to support more credential types

Backported to Fine via https://github.com/ManageIQ/manageiq/pull/15780


Leading Whitespace in watch expression still causes parse error

I found an issue with leading whitespace - https://github.com/kasperlewau/angular-bind-notifier/issues/28 does not fix the issue. The expression now passes the regex check here https://github.com/kasperlewau/angular-bind-notifier/blob/master/src/bindNotifier.js#L112 but the parts variable declared here https://github.com/kasperlewau/angular-bind-notifier/blob/master/src/bindNotifier.js#L116 a " " in index 0 which means it passes the "not falsey" check a few lines below.
This problem can be solved by doing a whitespace-only regex check along with the "not falsey" check - line 121 now is
if (part && /^(\w+\S+)$/.test(part)) {

That regex logic is incorrect, here's the right line:
if (part && /^\s*$/.test(part) == false) {

Or alternatively you could just trim the whitespace from the expression? http://www.w3schools.com/jsref/jsref_trim_string.asp

I'm having the same problem here.

I just had this problem and I can confirm that @lrajlich's fix works for me.
I have a slight bias towards using .trim() instead of regex because it would seem to be faster, but since I don't actually have data to back that up, I'm not saying this very strongly.
@lrajlich, if you can add a test for this, perhaps we can get this merged? If you're no longer interested in working on this, I will take this over and add the test.

So, ran some rough jsperf tests on regex vs trim.
https://jsperf.com/regex-vs-trim-for-bind-notifier/1
Trim comes out about 5% faster. Difference is not big, but since these expressions tend to be in performance critical sections, it might be important.

That's my pull request with a test.

Merged. I've been given control over this project and merged the PR. This will go into the 1.1.9 release.


Enhance User Experience for Home page download buttons

We have same button for same purpose in same place.
Feedback from discord

Replace the one in hero with something like 'Get started'
Use different color
Make the button bigger
Let the download in the menu go to the list of releases (general download page) and make the download button on the main page a "Download latest" button that leads directly to the latest version

Also make it blue

Also including feedback from community:


Azure Storage Core: Added ?Sized on impl

Tentatively fixes #307.

Thank you for your help @cswinter! Merging and publishing now!


Add additional information in info, closes #193

Add additonal information in info command
global:

cache dir size
auth store location

project:

dependency count
cache size
lock file last updated
target platforms

also reformats the output of tasks and adds help string in info command

Nice improvements! I have just one problem with it, it takes 10 seconds the first time I run it and it is still slow after that. Please remove the slow parts for now.
Or a few options that would give it a better UX:

Add a --extended flag and only then add the slow parts. Plus some spinner while it is loading.
Use a dynamic print where there is a spinner in the place of the parts that are not fetched yet.

Nice improvements! I have just one problem with it, it takes 10 seconds the first time I run it and it is still slow after that. Please remove the slow parts for now. Or a few options that would give it a better UX:

Add a --extended flag and only then add the slow parts. Plus some spinner while it is loading.
Use a dynamic print where there is a spinner in the place of the parts that are not fetched yet.

I think the culprit for the slow response time is the cache and environment size, will move these 2 in the extended flag behind a spinner.


Invalid Joint Indices/Broken Animation

Hello!
So I have no idea whether the problem is here, in tinygltf, or in Blender's exporter, so sorry.
But if you take say CesiumMan from the sample models repo and import him to Blender and re-export, the joint indices stored in Vertex::joint0 go way out of bounds and the animation dies horribly.

The console output is the Vertex::joint0 values.
Blender can re-import its own gltf models just fine and throwing them through a gltf validator doesn't give off any issues.
I don't know much about animation in general, tinygltf or the gltf spec, so I'm hoping somebody has some insight. I don't think I can figure this out.

I think I figured it out, sort of. Blender exports joints with componentType 5121 or "unsigned byte", but the code just seems to assume the joints are in uint16_t format: https://github.com/SaschaWillems/Vulkan-glTF-PBR/blob/master/base/VulkanglTFModel.cpp#L484
I don't think this is the only problem. Because when I import the Blender exported version, the camera is off-center from the object.

I'll investigate some more, but I'd be a lot more comfortable if somebody who actually knows what they're doing fixed this.

Alright, I can't verify for sure, but I think the off-center issue may be Blender's fault. I noticed re-exporting cesium man is changing bone roll on one of the bones. But I've got joint indices/animation working fine now as far as I know.
So I guess I'll do a pull request. Sorry for potentially two messages at once. lol

Fixed with #48


Add fetchOnServer option to config

I don't know if you are interested on adding this feature to the library.
There are some case where is interesting to decide what to fetch on the server
setup() {
    const { data: post } = useSWRV('post1', () => fetchPostById(1));
    const { data: comments } = useSWRV(
       'post1comments',
       () => fetchPostCommentsById(1), { fetchOnServer: false }
    );
    return { post, comments }
}

It is something similar to the fetchOnServer option on nuxt https://nuxtjs.org/api/pages-fetch/
I know this is a deviation from the original swr api, but I think that they already have the granular control with the initialData prop.

Thanks @axelhzf, I like it! Maybe we should make it a Boolean|Function<Boolean> since that’s would align with the nuxt api. Can you add and also add property to the README.md? We also have an ssr test suite if you wanted to try to add a new test there.

I updated the type, the readme, and included a new test case.
About the test case, do you know how to combine server and client tests? To be sure that if you use fetchOnServer: false, the fetch is actually done when the client is loaded.

I was thinking, what would be the use case for passing a function?
In the case of nuxt I think that makes sense if you want to access to this
export default {
  computed: {
      myFancyCondition() {
         return true;
      }
  },
  fetchOnServer() {
     return this.myFancyCondition
  }
}

But in this case, you could just access the condition before calling swrv
setup() {
   const myFancyCondition = true;
   useSWRV("key", fetcher, { fetchOnServer: myFancyCondition })
}

@axelhzf we could pass the keyRef value as well, though I'm not sure it will be available during the calculation. Would need to experiment but could be a nice feature:
setup(props) {
  function myFancyCondition (key) {
    return /\/users\/\w\/\w/.test(key')
  }

  useSWRV("/api/user/1", fetcher, { fetchOnServer: myFancyCondition }) // would fetch
  useSWRV("/api/users/comments", fetcher, { fetchOnServer: myFancyCondition }) // would not fetch
}

If it's not straightforward we can leave it as a strict boolean.

I believe this is now fixed by https://github.com/Kong/swrv/pull/49 which gives the option to only serve from cache when a function is falsy:
setup() {
    const { data: post } = useSWRV('post1', () => fetchPostById(1));
    const { data: comments } = useSWRV('post1comments',
       typeof window !== 'undefined' && () => fetchPostCommentsById(1)
    );
    return { post, comments }
}


Support for secret passing

@cdoron
Some Airbyte connectors, like S3, will require that secrets be passed to them.  Currently, the only way this could be done is to put the secret keyword and value in the Asset yaml where they will eventually end up in a mounted file (/etc/conf/conf.yaml)  This is of course a security hole.  Instead, the secrets - keyword as expected by the Airbyte connector and values - either be stored in Vault or in a Secrets asset and the module should then extract these, append them to the other values specified in Asset yaml and pass these as configuration parameters to the airbyte connector.

@elsalant : how urgent is this issue?
I think that the best way to address this problem is using Vault, and the Fybrik python vault  library: https://github.com/fybrik/fybrik/tree/master/python/vault