text:
Problem after SW update and re-install

Hi,
as performed several times before I used the update function to get the latest version on my RPi controller.
Unfortunately it ended up with 2 error messages:
"Unable to reach Redis database. You may need to reinstall PiFire or enable rdis-server.
The control process did not respond to a request and may be stopped.
So I reinstalled PiFire with:
curl https://raw.githubusercontent.com/nebhead/pifire/main/auto-install/install.sh | bash
and ended up in a different error on supervisor page:
Webapp fatal error.
can't find command '/usr/local/bin/pifire/bin/gunicorn'

and this error log message:
n /usr/local/lib/python3.9/dist-packages (from adafruit-circuitpython-typing->Adafruit-Blinka->adafruit-circuitpython-ads1x15) (1.14.0)
Return Code: 0
Reading package lists...
Building dependency tree...
Reading state information...
python3-smbus is already the newest version (4.2-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Return Code: 0
command output: PiFire Board Configuration Tool v1.0.0
command output: Ben Parmeter - 2024 - MIT License
command output: --help, -h for command details
command output:
command output: Results:
command output: - Setting the 1Wire pin: SUCCESS
command output: - Enabling SPI: SUCCESS
command output: - Enabling I2C: SUCCESS
command output: - Attempting to append data to /etc/modules:  SUCCESS (appending file /etc/modules)
command output: PiFire Board Configuration Tool v1.0.0
command output: Ben Parmeter - 2024 - MIT License
command output: --help, -h for command details
command output:
command output: Results:
command output: - Enabling SPI: SUCCESS

It sounds from your description that at least the second time you installed pifire, it didn't install correctly.  Did you wipe the SDCard before running the installation script?

Hi,
Reinstalling was not that easy as the raspberry did not boot with network connectivity. Nevertheless after new image and re-installing latest version the error messages are gone but for whatever reason the auger does not work anymore. All other Relais are working fine, only the auger output is not providing any signal.
Do you have any idea?
Even in manual mode I can see the icon on the display but the relay gets no signal.
Any special config at raspberry needed?

I am running HW board ver 2.00 with a raspberry zero 2W, mechanical Relais Modul, SPI Display, Encoder Button and vl53l0x sensor. Do you need any log file?

Are you now on the latest PiFire (main branch)?  v1.8.x?
In the configuration wizard, are you selecting the 2.00a PCB?

Can get the settings.json file (let me know if you need help getting this) and post the platform configuration section?   It should look something like this (yours will have different values):
  "platform": {
    "buttonslevel": "HIGH",
    "current": "custom",
    "dc_fan": true,
    "devices": {
      "display": {
        "dc": 24,
        "led": 5,
        "rst": 25
      },
      "distance": {
        "echo": 27,
        "trig": 23
      },
      "input": {
        "down_dt": 20,
        "enter_sw": 21,
        "up_clk": 16
      }
    },
    "inputs": {
      "selector": 17,
      "shutdown": 17
    },
    "outputs": {
      "auger": 14,
      "dc_fan": 26,
      "fan": 15,
      "igniter": 18,
      "power": 4,
      "pwm": 13
    },
    "real_hw": false,
    "standalone": true,
    "system": {
      "1WIRE": 6,
      "SPI0": {
        "CE0": 8,
        "CE1": 7
      }
    },
    "system_type": "prototype",
    "triggerlevel": "HIGH"
  }

Hi,
yes I am on latest version now:
System Update (Current Version: 1.8.8)
I have chosen the Version 2.00a PCB during config.
The other 3 relais are working fine on the board even when I switch the cables (auger vs. fan).
It looks like GPIO14 is not providing any output at all, neither high or low.
Settings.json is attached,
But where do I find the platform configuration settings?
Von: nebhead @.>
Gesendet: Montag, 25. November 2024 17:36
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
Are you now on the latest PiFire (main branch)? v1.8.x?
In the configuration wizard, are you selecting the 2.00a PCB?
image.png (view on web) https://github.com/user-attachments/assets/63b85e16-1315-480e-9039-3148020839e0
Can get the settings.json file (let me know if you need help getting this) and post the platform configuration section? It should look something like this (yours will have different values):
"platform": {
"buttonslevel": "HIGH",
"current": "custom",
"dc_fan": true,
"devices": {
"display": {
"dc": 24,
"led": 5,
"rst": 25
},
"distance": {
"echo": 27,
"trig": 23
},
"input": {
"down_dt": 20,
"enter_sw": 21,
"up_clk": 16
}
},
"inputs": {
"selector": 17,
"shutdown": 17
},
"outputs": {
"auger": 14,
"dc_fan": 26,
"fan": 15,
"igniter": 18,
"power": 4,
"pwm": 13
},
"real_hw": false,
"standalone": true,
"system": {
"1WIRE": 6,
"SPI0": {
"CE0": 8,
"CE1": 7
}
},
"system_type": "prototype",
"triggerlevel": "HIGH"
}
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2498503105 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634B3MAVYTGZA7THNGZDT2CNGWRAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGUYDGMJQGU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B75K7LYAF7YCZC7VUL2CNGWRA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUU5QQ4C.gif Message ID: @.*** @.***> >

Settings.json is attached, But where do I find the platform

Unfortunately the settings.json did not come across in GitHub.  If you look at the file, you should see a section that says: "platform".

Ah, now I got it…
"platform": {
"buttonslevel": "HIGH",

"current": "pcb_2.00a",

"dc_fan": false,

"devices": {

  "display": {

    "dc": 24,

    "led": 5,

    "rst": 25

  },

  "distance": {

    "echo": 27,

    "trig": 23

  },

  "input": {

    "down_dt": 20,

    "enter_sw": 21,

    "up_clk": 16

  }

},

"inputs": {

  "selector": 17,

  "shutdown": null

},

"outputs": {

  "auger": 14,

  "dc_fan": null,

  "fan": 15,

  "igniter": 18,

  "power": 4,

  "pwm": null

},

"real_hw": true,

"standalone": true,

"system": {

  "1WIRE": null,

  "SPI0": {

    "CE0": 8,

    "CE1": 7

  }

},

"system_type": "raspberry_pi_all",

"triggerlevel": "HIGH"

},
"probe_settings": {
"probe_map": {

  "probe_devices": [

    {

      "config": {

        "ADC0_rd": "10000",

        "ADC1_rd": "10000",

        "ADC2_rd": "10000",

        "ADC3_rd": "10000",

        "i2c_bus_addr": "0x48",

        "voltage_ref": "3.28"

      },

      "device": "ADS1115",

      "module": "ads1115_adafruit",

      "ports": [

        "ADC0",

        "ADC1",

        "ADC2",

        "ADC3"

      ]

    }

  ],

  "probe_info": [

    {

      "device": "ADS1115",

      "enabled": true,

      "label": "Grill",

      "name": "Grill",

      "port": "ADC0",

      "profile": {

        "A": 0.05966017913127897,

        "B": -0.01048654943772497,

        "C": 4.987389532180097e-05,

        "id": "99b8f02d-233d-11ee-a7a2-e5396c02c5fd",

        "name": "PT-1000-Ideal"

      },

      "type": "Primary"

    },

    {

      "device": "ADS1115",

      "enabled": true,

      "label": "Probe1",

      "name": "Probe-1",

      "port": "ADC1",

      "profile": {

        "A": 0.08349559509913372,

        "B": -0.015417214989461945,

        "C": 8.10020549005308e-05,

        "id": "04204563-2335-11ee-9a44-e5396c02c605",

        "name": "PT-1000-OEM-2023"

      },

      "type": "Food"

    },

    {

      "device": "ADS1115",

      "enabled": true,

      "label": "Probe2",

      "name": "Probe-2",

      "port": "ADC2",

      "profile": {

        "A": 0.08349559509913372,

        "B": -0.015417214989461945,

        "C": 8.10020549005308e-05,

        "id": "04204563-2335-11ee-9a44-e5396c02c605",

        "name": "PT-1000-OEM-2023"

      },

      "type": "Food"

    }

  ]

},

"probe_profiles": {
  "04204563-2335-11ee-9a44-e5396c02c605": {

    "A": 0.08349559509913372,

    "B": -0.015417214989461945,

    "C": 8.10020549005308e-05,

    "id": "04204563-2335-11ee-9a44-e5396c02c605",

    "name": "PT-1000-OEM-2023"

  },

  "99b8f02d-233d-11ee-a7a2-e5396c02c5fd": {

    "A": 0.05966017913127897,

    "B": -0.01048654943772497,

    "C": 4.987389532180097e-05,

    "id": "99b8f02d-233d-11ee-a7a2-e5396c02c5fd",

    "name": "PT-1000-Ideal"

  },

  "ET73-HM": {

    "A": 0.00024723753,

    "B": 0.00023402251,

    "C": 1.3879768e-07,

    "id": "ET73-HM",

    "name": "ET-73-Heatermeter"

  },

  "ET73-SP": {

    "A": 0.00023067434,

    "B": 0.00023696596,

    "C": 1.2636414e-07,

    "id": "ET73-SP",

    "name": "ET-73-skyeperry1"

  },

  "PT-1000-OEM": {

    "A": 0.04136906456,

    "B": -0.00677987613,

    "C": 2.760294589e-05,

    "id": "PT-1000-OEM",

    "name": "PT-1000-Grill-Probe-OEM"

  },

  "PT-1000-PiFire": {

    "A": 0.05469905897345206,

    "B": -0.009473055040089443,

    "C": 4.3768560703857386e-05,

    "id": "PT-1000-PiFire",

    "name": "PT-1000-Grill-Probe-PiFire"

  },

  "TWPS00": {

    "A": 0.00073431401,

    "B": 0.0002157437,

    "C": 9.515686e-08,

    "id": "TWPS00",

    "name": "Thermoworks-Pro-Series-HeaterMeter"

  },

  "iGrill-HM": {

    "A": 0.0007739251279,

    "B": 0.0002088025997,

    "C": 1.154400438e-07,

    "id": "iGrill-HM",

    "name": "iGrill-Heatermeter"

  }

}

},
"pwm": {
"frequency": 25000,

"max_duty_cycle": 100,

"min_duty_cycle": 20,

"profiles": [

  {

    "duty_cycle": 20

  },

  {

    "duty_cycle": 35

  },

  {

    "duty_cycle": 50

  },

  {

    "duty_cycle": 75

  },

  {

    "duty_cycle": 100

  }

],

"pwm_control": false,

"temp_range_list": [

  3,

  7,

  10,

  15

],

"update_time": 10

},
"recipe": {
"probe_map": {

  "food": [

    "Probe1",

    "Probe2",

    "Probe3"

  ],

  "primary": "Grill"

}

},
"safety": {
"maxstartuptemp": 45,

"maxtemp": 300,

"minstartuptemp": 1,

"reigniteretries": 1,

"startup_check": true

},
"shutdown": {
"auto_power_off": false,

"shutdown_duration": 240

},
"smoke_plus": {
"duty_cycle": 75,

"enabled": false,

"fan_ramp": false,

"max_temp": 102,

"min_temp": 70,

"off_time": 5,

"on_time": 5

},
"startup": {
"duration": 240,

"prime_on_startup": 0,

"smartstart": {

  "enabled": false,

  "exit_temp": 46,

  "profiles": [

    {

      "augerontime": 15,

      "p_mode": 0,

      "startuptime": 360

    },

    {

      "augerontime": 15,

      "p_mode": 1,

      "startuptime": 360

    },

    {

      "augerontime": 15,

      "p_mode": 3,

      "startuptime": 240

    },

    {

      "augerontime": 15,

      "p_mode": 5,

      "startuptime": 240

    }

  ],

  "temp_range_list": [

    15,

    25,

    30

  ]

},

"start_to_mode": {

  "after_startup_mode": "Smoke",

  "primary_setpoint": 165

},

"startup_exit_temp": -17

},
"versions": {
"build": 36,

"cookfile": "1.5.0",

"recipe": "1.0.0",

"server": "1.8.8"

}
}
Von: nebhead @.>
Gesendet: Montag, 25. November 2024 19:56
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
Settings.json is attached, But where do I find the platform
Unfortunately the settings.json did not come across in GitHub. If you look at the file, you should see a section that says: "platform".
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2498799959 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634BYBZETRINYF6TSX3ST2CNXCFAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYG44TSOJVHE .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B4NHFVKGSOBUQREAJ32CNXCFA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUU6CUVO.gif Message ID: @.*** @.***> >

That all looks OK.  Is there a possible issue with your relay?   Or the wiring from the relay header?  Do you have a multimeter?  Can you test the relay header is outputting high or low when expected?

Well it is really strange. In the end I used the manual config with GPIO4 instead GPIO14 for the auger and changed the input cables at the relais card.
The power relais is not working now on GPIO14 but GPIO4 is turning the auger on.
Encoder switch is not working now, will have a look on this later on.
Von: nebhead @.>
Gesendet: Montag, 25. November 2024 20:30
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
That all looks OK. Is there a possible issue with your relay? Or the wiring from the relay header? Do you have a multimeter? Can you test the relay header is outputting high or low when expected?
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2498863283 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634B3TC7NBS6LFTXL4EBT2CN3CRAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYHA3DGMRYGM .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B5X4SZLJWPXZL45SY32CN3CRA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUU6GQLG.gif Message ID: @.*** @.***> >

This pin is also used as a UART pin if configured, so hopefully that didn't get turned on be default or anything.  Normally this is not configured for UART.   You can check your /boot/firmware/config.txt to see if there is any lines that are enabling UART.

OK, that all looks fine.  Well, except for the PWM pin being activated.  I'd recommend adding a # in front of that line to ensure PWM is not enabled.  Assuming you are not using a DC Fan on this build.
So when you measure voltage of GPIO14, are you changing the output with manual mode?  Does it still not switch?  That might indicate that the GPIO14 is damaged/not working.  What we might be able to do is to utilize another spare GPIO to the relay instead.  Basically tie another of the GPIO's from the AUX header that you are not currently using - we can set the settings.json appropriately to utilize the other GPIO.

First of all I am really mad about myself, why did I changed anything on a proper running system… ☹
Maybe it’s a better idea to downgrade to an older version?
Looking at the /boot/firmware/config.txt file, where to put the #?
Do you mean it like this?
enable_uart=0
dtparam=act_led_trigger=actpwr
dtoverlay=pwm,func=4,pin=13  # Modified by PiFire Board Configuration Utility
Meanwhile the controller is working remotely with the manual setup and using GPIO4 for the auger instead of GPIO14 and it keeps the set temperature/mode fine.
I am using the ili9341 with the rotary encoder, this encoder is not working at all.
No matter which of the 2 encoders I am choosing during setup wizard.
The display is working after startup until I have changed the “set temp” or “workmode” several times.
After doing this changes the display turns blank, just shining bright, the webinterface and the smoker itself continues running.
Once I noticed that with a blank display the notification for running out of pellets continues sending alarms despite I filled up the pellets and the webinterface shows 100%.
When I push the stop button on the web interface the system stops immediately without the 240 sec. fan cool down time. Is this behavior ok?
During startup I am missing the prime functionality before ignite function.
Is this available by starting via the web interface?
Von: nebhead @.>
Gesendet: Dienstag, 26. November 2024 18:01
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
OK, that all looks fine. Well, except for the PWM pin being activated. I'd recommend adding a # in front of that line to ensure PWM is not enabled. Assuming you are not using a DC Fan on this build.
So when you measure voltage of GPIO14, are you changing the output with manual mode? Does it still not switch? That might indicate that the GPIO14 is damaged/not working. What we might be able to do is to utilize another spare GPIO to the relay instead. Basically tie another of the GPIO's from the AUX header that you are not currently using - we can set the settings.json appropriately to utilize the other GPIO.
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2501443898 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634BYCMB4B3ROS27HXVFL2CSSMXAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGQ2DGOBZHA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B2Y54XBMV7BSGGDDRT2CSSMXA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUVDEATU.gif Message ID: @.*** @.***> >

BTW. I found the Prime and Start functionality on the web interface!
Von: @.*** @.>
Gesendet: Mittwoch, 27. November 2024 13:29
An: 'nebhead/PiFire' @.>
Betreff: AW: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
First of all I am really mad about myself, why did I changed anything on a proper running system… ☹
Maybe it’s a better idea to downgrade to an older version?
Looking at the /boot/firmware/config.txt file, where to put the #?
Do you mean it like this?
enable_uart=0
dtparam=act_led_trigger=actpwr
dtoverlay=pwm,func=4,pin=13  # Modified by PiFire Board Configuration Utility
Meanwhile the controller is working remotely with the manual setup and using GPIO4 for the auger instead of GPIO14 and it keeps the set temperature/mode fine.
I am using the ili9341 with the rotary encoder, this encoder is not working at all.
No matter which of the 2 encoders I am choosing during setup wizard.
The display is working after startup until I have changed the “set temp” or “workmode” several times.
After doing this changes the display turns blank, just shining bright, the webinterface and the smoker itself continues running.
Once I noticed that with a blank display the notification for running out of pellets continues sending alarms despite I filled up the pellets and the webinterface shows 100%.
When I push the stop button on the web interface the system stops immediately without the 240 sec. fan cool down time. Is this behavior ok?
During startup I am missing the prime functionality before ignite function.
Is this available by starting via the web interface?
Von: nebhead @.*** @.> >
Gesendet: Dienstag, 26. November 2024 18:01
An: nebhead/PiFire @. @.> >
Cc: thomasstrach @. @.> >; Author @. @.***> >
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
OK, that all looks fine. Well, except for the PWM pin being activated. I'd recommend adding a # in front of that line to ensure PWM is not enabled. Assuming you are not using a DC Fan on this build.
So when you measure voltage of GPIO14, are you changing the output with manual mode? Does it still not switch? That might indicate that the GPIO14 is damaged/not working. What we might be able to do is to utilize another spare GPIO to the relay instead. Basically tie another of the GPIO's from the AUX header that you are not currently using - we can set the settings.json appropriately to utilize the other GPIO.
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2501443898 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634BYCMB4B3ROS27HXVFL2CSSMXAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRGQ2DGOBZHA .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B2Y54XBMV7BSGGDDRT2CSSMXA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUVDEATU.gif Message ID: @.*** @.***> >

First of all I am really mad about myself, why did I changed anything on a proper running system… ☹ Maybe it’s a better idea to downgrade to an older version?

Don't beat yourself up.  We'll figure this out.  You can try to downgrade, but I'm willing to bet you're going to have issues.

Looking at the /boot/firmware/config.txt file, where to put the #? Do you mean it like this?
enable_uart=0
dtparam=act_led_trigger=actpwr
dtoverlay=pwm,func=4,pin=13 # Modified by PiFire Board Configuration Utility

Yep, perfect.
Do you see any other lines in there, for example for 1-Wire that are enabled?   We definitely want to disable 1-Wire and have had reports of the new version turning it on by mistake.

Meanwhile the controller is working remotely with the manual setup and using GPIO4 for the auger instead of GPIO14 and it keeps the set temperature/mode fine.

So, that's encouraging.  Still strange that the GPIO14 is misbehaving.  Do you have a different Pi by any chance?  We could not even hook it up to the board, and install PiFire, just to test if GPIO14 behaves differently.

I am using the ili9341 with the rotary encoder, this encoder is not working at all. No matter which of the 2 encoders I am choosing during setup wizard. The display is working after startup until I have changed the “set temp” or “workmode” several times. After doing this changes the display turns blank, just shining bright, the webinterface and the smoker itself continues running.

Can you take a screenshot of the one that you are using the configuration wizard?   It sounds like it might be a config issue that I've seen before.  Also, I've seen this with loose wiring to the display.  Unless this is consistent, there are a few things that can be touchy here.

Once I noticed that with a blank display the notification for running out of pellets continues sending alarms despite I filled up the pellets and the webinterface shows 100%.

This might be an actual bug.  I'll look into this.

When I push the stop button on the web interface the system stops immediately without the 240 sec. fan cool down time. Is this behavior ok?

Yes, the stop button will cause it to stop immediately where as the little finish flag will go through a shutdown cycle for 240s.  The finish flag only shows up after you exit startup mode.

During startup I am missing the prime functionality before ignite function. Is this available by starting via the web interface?

Looks like you found it!

Thanks for your effort with my problems, really very much appreciated!
See my comments below:
Von: nebhead @.>
Gesendet: Mittwoch, 27. November 2024 18:09
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
First of all I am really mad about myself, why did I changed anything on a proper running system… ☹ Maybe it’s a better idea to downgrade to an older version?
Don't beat yourself up. We'll figure this out. You can try to downgrade, but I'm willing to bet you're going to have issues.
Ok, I will continue with this version and hope you can help me to get it fixed.
Looking at the /boot/firmware/config.txt file, where to put the #? Do you mean it like this?
enable_uart=0
dtparam=act_led_trigger=actpwr
dtoverlay=pwm,func=4,pin=13 # Modified by PiFire Board Configuration Utility
Yep, perfect.
Just implementent the change, will have to test it.
Do you see any other lines in there, for example for 1-Wire that are enabled? We definitely want to disable 1-Wire and have had reports of the new version turning it on by mistake.
I cannot find anything in this file regarding 1-wire.
Meanwhile the controller is working remotely with the manual setup and using GPIO4 for the auger instead of GPIO14 and it keeps the set temperature/mode fine.
So, that's encouraging. Still strange that the GPIO14 is misbehaving. Do you have a different Pi by any chance? We could not even hook it up to the board, and install PiFire, just to test if GPIO14 behaves differently.
I have just ordered another raspberry  zero 2W to test this out. Will take some days…
I am using the ili9341 with the rotary encoder, this encoder is not working at all. No matter which of the 2 encoders I am choosing during setup wizard. The display is working after startup until I have changed the “set temp” or “workmode” several times. After doing this changes the display turns blank, just shining bright, the webinterface and the smoker itself continues running.
Can you take a screenshot of the one that you are using the configuration wizard? It sounds like it might be a config issue that I've seen before. Also, I've seen this with loose wiring to the display. Unless this is consistent, there are a few things that can be touchy here.
I used GPIO 20/21/16 for the button Down/Enter/Buttom up config (pre-set), that’s where my encoder is connected.
I have tried out both selections for the encoder
Once I noticed that with a blank display the notification for running out of pellets continues sending alarms despite I filled up the pellets and the webinterface shows 100%.
This might be an actual bug. I'll look into this.
When I push the stop button on the web interface the system stops immediately without the 240 sec. fan cool down time. Is this behavior ok?
Yes, the stop button will cause it to stop immediately where as the little finish flag will go through a shutdown cycle for 240s. The finish flag only shows up after you exit startup mode.
Ah, I only used the shutdown on the display with the rotary encoder before.
During startup I am missing the prime functionality before ignite function. Is this available by starting via the web interface?
Looks like you found it!
Yes, I used the display with encoder before for startup.
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2504388655 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634B4MEPZJMOUEBAWOJGT2CX4D7AVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBUGM4DQNRVGU .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B3BIF7VEENFNFZQSZL2CX4D7A5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUVIXYC6.gif Message ID: @.***>

I have just ordered another raspberry  zero 2W to test this out. Will take some days…

This is great - it should help us to understand if what we are seeing is a hardware problem with the existing Pi.

Just received the controller and things have turned around.
After formatting the sd card, now the WIFI was connected automatically, that was not happening before with several attemps.
All is running fine, no problems anymore.
Display is working, encoder and all GPIOs.
I will try again when I have time with old Pi, maybe the SD card and/or the Pi is wrong.
Thanks a lot for your patience and support!
Von: nebhead @.>
Gesendet: Donnerstag, 28. November 2024 17:35
An: nebhead/PiFire @.>
Cc: thomasstrach @.>; Author @.>
Betreff: Re: [nebhead/PiFire] Problem after SW update and re-install (Issue #207)
I have just ordered another raspberry zero 2W to test this out. Will take some days…
This is great - it should help us to understand if what we are seeing is a hardware problem with the existing Pi.
—
Reply to this email directly, view it on GitHub https://github.com/nebhead/PiFire/issues/207#issuecomment-2506482923 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AL634BYYYOFGNY7URXYPKWT2C5A3LAVCNFSM6AAAAABR7WHVFSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBWGQ4DEOJSGM .
You are receiving this because you authored the thread.  https://github.com/notifications/beacon/AL634B57YGWDVJZE3IDPQU32C5A3LA5CNFSM6AAAAABR7WHVFSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUVMXSOW.gif Message ID: @.*** @.***> >

Excellent news!  You are very welcome.  Hope all is well from here on out.

authors: nebhead thomasstrach

repo: nebhead/PiFire


text:
Hindi Translation added

Add language Hindi #57

Closes #57

removed 'hacktoberfest accepted' label bcs of this

source: gharchive/pull-request

authors: abdulmannans nebojsatomic

license: MIT

license_type: permissive

license_source: github-api


text:
tools to convert tl schema to protobuf

is there a tool/program to convert TL schema to corresponding protobuf?

https://github.com/nebulaim/mtprotoc

source: gharchive/issue

repo: nebulaim/telegramd

license_source: bigquery


text:
[Chatllama] RLHF Training - RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method

While training RL model with the following command
python artifacts/main.py artifacts/config/config.yaml --type RL

we get the torch dataset error. To fix the error, we changed the following lines in trainer.py:427
        # from
        #dataloader = DataLoader(
            #ExperienceDataset(memories, device), batch_size=batch_size
        #)
       # to
       dataset = ExperienceDataset(memories, device)

and in trainer.py:455
#from
#training_data=dataloader
#to
training_data=dataset

Issue Reference - #229
Post this fix, we are facing the following error
Using /home/ubuntu/.cache/torch_extensions/py39_cu117 as PyTorch extensions root...
No modifications detected for re-loaded extension module utils, skipping build step...
Loading extension module utils...
Time to load utils op: 0.00028014183044433594 seconds
Traceback (most recent call last):
  File "/home/ubuntu/artifacts/main.py", line 48, in <module>
    rlhf_trainer.train()
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/chatllama/rlhf/trainer.py", line 788, in train
    self.learn(memories)
  File "<@beartype(chatllama.rlhf.trainer.RLTrainer.learn) at 0x7f279c996820>", line 33, in learn
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/chatllama/rlhf/trainer.py", line 492, in learn
    for i, (
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/deepspeed/runtime/dataloader.py", line 125, in __next__
    return next(self.data)
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/deepspeed/runtime/dataloader.py", line 158, in <genexpr>
    self.data = (x for x in self.dataloader)
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 628, in __next__
    data = self._next_data()
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 1333, in _next_data
    return self._process_data(data)
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/dataloader.py", line 1359, in _process_data
    data.reraise()
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/_utils.py", line 543, in reraise
    raise exception
RuntimeError: Caught RuntimeError in DataLoader worker process 0.
Original Traceback (most recent call last):
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/_utils/worker.py", line 302, in _worker_loop
    data = fetcher.fetch(index)
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/_utils/fetch.py", line 58, in fetch
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/utils/data/_utils/fetch.py", line 58, in <listcomp>
    data = [self.dataset[idx] for idx in possibly_batched_index]
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/chatllama/rlhf/trainer.py", line 207, in __getitem__
    self.data[idx].states.to(self.device),
  File "/opt/conda/envs/pytorch/lib/python3.9/site-packages/torch/cuda/__init__.py", line 217, in _lazy_init
    raise RuntimeError(
RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method

Attaching the log, dataset, config for reference
Training log -
rl_train.log
Configurations -
test.zip
Dataset -
rlhf_training_data.zip
Training Environment:
Nvidia - A10 - 24 GB - g5.4xlarge - AWS instance
Packages are installed from the README instructions

Hi, @shrinath-suresh this issue should be resolved in the PR #233 . The batch size can be changed in config.yaml if doesn't fit your memory requirements.
Let me know if everything is working.
Thanks for your feedback!

@PierpaoloSorbellini  I had the same error，hope you solve it soon.
"RuntimeError: Cannot re-initialize CUDA in forked subprocess. To use CUDA with multiprocessing, you must use the 'spawn' start method"

@PierpaoloSorbellini Thanks for the fix. The issue got resolved. However, on the next steps, i observed the following behaviour.
Even if the multi gpu command is issued, the RL training happens only with single gpu . I found this open issue for the same - #288
Currently getting OOM even with opt-125m.pt model. Attaching log for reference
OutOfMemoryError: CUDA out of memory. Tried to allocate 2.00 MiB (GPU 0; 22.04 GiB total capacity; 2.39 GiB already allocated; 3.12 MiB free; 2.50 GiB reserved in total by PyTorch) If reserved memory is
>> allocated memory try setting max_split_size_mb to avoid fragmentation.  See documentation for Memory Management and PYTORCH_CUDA_ALLOC_CONF

Full log here -
chatllama-multi-gpu.log
Do you think its because of the hardware restriction ? We are training with g5.12xlarge AWS instance (4 A10 GPUs with 24GB).

Hi @shrinath-suresh, thanks for the quick response.
Did you enable DeepSpeed or accelerate in the config.yaml and use the proper command to launch the training ?
More info should be already available at the bottom of the readme.md in the PR.
We actually observed that all the GPUs were used during testing.
For the out of memory error try to play with the batch size after observing if the GPUs are actually used.
We are introducing some optimization techniques for reducing memory requirements, like LoRA using the peft library. We still have to fine tune the hyperparameters of these techinques. You can enable peft by the same config.yaml file and in the same folder you can find the related configuration options, but you still have to play a bit with them once enabled.
More info are going to be added in further development of the documentation.

Sure @PierpaoloSorbellini  . I have already set the batch size to 1 and enabled fp16 in ds config.
config.yaml
---
trainer_config:
  # learning rates
  actor_lr: 0.000005
  critic_lr: 0.000009
  # PPO Hyperparameters
  actor_eps_clip: 0.2
  critic_eps_clip: 0.2
  beta_s: 0.02
  # coefficient for the discounted rewards
  gamma_discounted: 1
  # path to examples to be sampled (training dataset) see rlhf_dataset.json
  examples_path: "./rlhf_training_data.json"
  # number of episodes and generation performed for each episode
  # in the train() method
  num_episodes: 1
  max_timesteps: 4
  # number of timesteps after which the learn() method is called
  # (to update the weights)
  update_timesteps: 4
  # number of example sampled at each timestep
  num_examples: 1
  # batch and epochs for the training
  batch_size: 1
  epochs: 1
  # number of episodes after which update the checkpoints in RL training
  checkpoint_steps: 1000
  # here specify the name of the actor_rl checkpoint from which resume
  # during actor RL training. If null load the last one.
  checkpoint_name: null

actor_config:
  model: "facebook/opt-125m"
  model_folder: "./models"
  tokenizer_path: "path-to-tokenizer"
  train_dataset_path: "./actor_training_data.json"
  validation_dataset_path: null
  # froze model embedding during training
  froze_embeddings: True
  # use fairscale layers to build the model instead of vanilla pytorch
  # only for llama
  use_fairscale: False
  # max sequence length for the actor (i.e. prompt + completion) it depends on
  # the model used.
  max_sequence_length: 2048
  # max tokens generated by the actor (completion only)
  max_tokens: 2048
  # minimum number of tokens generated by the actor
  min_tokens: 100
  # additional prompt tokens to be used for template or as safety
  additonal_prompt_tokens: 20
  # temperature for the actor
  temperature: 0.1
  batch_size: 1
  # number iteration after print
  iteration_per_print: 1000
  lr: 0.000009
  epochs: 1
  # number of backpropagation after saving the checkpoints
  checkpoint_steps: 1000
  # number of checkpoints to keep while removing the older
  # (keep memory consumption of checkpoints reasonable)
  n_checkpoints_to_keep: 1
  # here specify the name of the actor checkpoint from which resume
  # during actor training. If null load the last one.
  checkpoint_name: null
  # deepspeed settings
  deepspeed_enable: True
  deepspeed_config_path: "./artifacts/config/ds_config.json"
  # accelerate settings
  accelerate_enable: False
  # use_peft - the parameters of PEFT can be modified in the peft_config.yaml
  peft_enable: True
  peft_config_path: "./artifacts/config/peft_config.yaml"

reward_config:
  # model to be chosen are gp2-large, bart-base, longformer-base-4096
  # more can be simply added in the reward.py __init__()
  model: "facebook/opt-125m"
  model_folder: "./models"
  # hidden size of the additional ffw head to produce the scores
  model_head_hidden_size: 2048
  max_sequence_length: 2048
  train_dataset_path: "./reward_training_data.json"
  validation_dataset_path: null
  batch_size: 1
  epochs: 1
  iteration_per_print: 1000
  # steps after which the checkpoint are saved
  checkpoint_steps: 10000
  # here specify the name of the reward checkpoint from which resume
  # during reward training. If null load the last one.
  checkpoint_name: null
  lr: 0.000009
  # deepspeed settings
  deepspeed_enable: True
  deepspeed_config_path: "./artifacts/config/ds_config.json"
  # accelerate settings
  accelerate_enable: False

critic_config:
  # model to be chosen are gp2-large, bart-base, longformer-base-4096
  # more can be simply added in the reward.py __init__()
  model: "facebook/opt-125m"
  # hidden size of the additional ffw head to produce the scores
  model_head_hidden_size: 2048
  max_sequence_length: 2048
  model_folder: "./models"
  # here specify the name of the critic checkpoint from which resume
  # during critic training. If null load the last one.
  checkpoint_name: null

ds_config.json
{
    "train_batch_size": 1,
    "gradient_accumulation_steps": 1,
    "optimizer": {
      "type": "Adam",
      "params": {
        "lr": 0.00015
      }
    },
    "fp16": {
      "enabled": false,
      "auto_cast": false,
      "loss_scale": 0,
      "initial_scale_power": 16,
      "loss_scale_window": 1000,
      "hysteresis": 2,
      "min_loss_scale": 1
  },
  "zero_optimization": {
    "stage": 2,
    "allgather_partitions": true,
    "allgather_bucket_size": 5e8,
    "overlap_comm": false,
    "reduce_scatter": true,
    "reduce_bucket_size": 5e8,
    "contiguous_gradients" : true,
    "offload_param": {
      "device": "cpu",
      "nvme_path": "/local_nvme",
      "pin_memory": true,
      "buffer_count": 5,
      "buffer_size": 1e8,
      "max_in_cpu": 1e9
    },
    "offload_optimizer": {
      "device": "cpu",
      "nvme_path": "/local_nvme",
      "pin_memory": true,
      "buffer_count": 4,
      "fast_init": false
    },
    "stage3_max_live_parameters" : 1e9,
    "stage3_max_reuse_distance" : 1e9,
    "stage3_prefetch_bucket_size" : 5e8,
    "stage3_param_persistence_threshold" : 1e6,
    "sub_group_size" : 1e12,
    "elastic_checkpoint" : true,
    "stage3_gather_16bit_weights_on_model_save": true,
    "ignore_unused_parameters": true,
    "round_robin_gradients": true
    }
  }

Command used to launch -
accelerate launch --multi_gpu artifacts/main.py artifacts/config/config.yaml --type RL

Havent changed anything in peft.yaml. will try it out.

@PierpaoloSorbellini Thank you very much. I created a fresh setup and was able to train with the dataset given in the instructions and my dataset as well.
There are few small fixes needed. Created a separate PRs for the same

Readme fix - https://github.com/nebuly-ai/nebullvm/pull/327
RL training - https://github.com/nebuly-ai/nebullvm/pull/329
Reward training - https://github.com/nebuly-ai/nebullvm/pull/330

Please review and let us know your comments

repo: nebuly-ai/nebullvm


text:
Query data that includes '@' is not able to be found

i tried querying an email for example
`
// FindAccount retrieves an account by email from the "accounts" table.
func FindAccount(client *supabase.Client, email string) (map[string]interface{}, error) {
var results []map[string]interface{}
err := client.DB.From("accounts").Select("*").Eq("email", email).Execute(&results)
log.Info(results)
if err != nil {
	return nil, err
}

if len(results) == 0 {
	return nil, nil
}

return results[0], nil

}
`
but it keeps returning an empty mapping but when there isnt any symbols it works and it was found. is there something i need to do to handle this kind of things ?

I faced the exact same issue and I solved it by using Filter instead of Eq.
You can try doing this -
err := client.DB.From("accounts").Select("*").Filter("email", "eq", email).Execute(&results)
log.Info(results)
if err != nil {
	return nil, err
}

if len(results) == 0 {
	return nil, nil
}

return results[0], nil

repo: nedpals/supabase-go


text:
Simpler solution

File(s) Modified: 1343-number-of-sub-arrays-of-size-k-and-average-greater-than-or-equal-to-threshold.js
Language(s) Used: javascript
Submission URL: _https://leetcode.com/problems/number-of-sub-arrays-of-size-k-and-average-greater-than-or-equal-to-threshold/submissions/1138529692_

@rafael84 Your solution is easier to follow. Thanks for your contribution 👍

repo: neetcode-gh/leetcode


text:
H should be h, Leetcode Syntax

File(s) Modified: 1-Two-Sum.py, 2-Add-Two-Numbers.py, etc...
Language(s) Used: python, javascript, etc...
Submission URL: https://leetcode.com/problems/koko-eating-bananas/
No submission just the question syntax is h, not H

Thanks, @Mark-777-0!


text:
Problem with API gateway Terraform resource

Something is wrong with the resource / Terraform / API Gateway, as it does not attach the Lambda.
https://github.com/nelg/aws-waf-security-automation/blob/063a34d4f8a0f02a219ba1ba4a2a0680659af1c2/apigatewaybadbotmethod.tf#L34
Any ideas world?

Exact issue was starting to dig on :)

https://github.com/nelg/aws-waf-security-automation/blob/master/apigatewaybadbot.tf#L25
THINK this should be changed... to '{proxy+}'

Looks like that's in your branch... continuing to dig :)

Looks like that's in your branch... continuing to dig :)

I found that in the AWS console, if I attach the Lambda function to the API gateway resource (second level proxy under ANY method, as terraform is supposed to, the Terraform error stops and the rest of it works.
So, something is going wrong with this specific bit.  Not sure if it's a terraform bug or not

authors: jasonmcintosh nelg

repo: nelg/aws-waf-security-automation


text:
Fix Narrative domains

Change narrative.network to narrative.org.

It might be nice if this list was auto-updated from https://github.com/CityOfZion/neo-mon

fixed this in the database for now. We are doing the auto-update/node discovery in the next release. @wy to merge

repo: neo-ngd/Happynodes


text:
antshares UI exception -

If I use the "Close" command to close the UI (upper left under the icon) instead of the X (Upper right) the app exits, but when I open the app again I get an error and the app fails to start. (error listed below).
Looking into the code, it may be because in MainForm.Designer.cs line 712 it only listens for the "Main Form Close" event instead of the "Window Close" event so the DB is not closed properly.
https://msdn.microsoft.com/en-us/library/system.windows.window.closing(v=vs.110).aspx
vs
https://msdn.microsoft.com/en-us/library/system.windows.forms.form.formclosing(v=vs.110).aspx
AntShares.Implementations.Blockchains.LevelDB.LevelDBException
Corruption: 613 missing files; e.g.: .\Chain/039966.ldb
at AntShares.Implementations.Blockchains.LevelDB.NativeHelper.CheckError(IntPtr error)
at AntShares.Implementations.Blockchains.LevelDB.DB.Open(String name, Options options)
at AntShares.Implementations.Blockchains.LevelDB.LevelDBBlockchain..ctor(String path)
at AntShares.Program.Main()

I have tested and found that either of "close" of "X" will raise the "FormClosing" event and DB will be closed.

authors: coranos erikzhang

repo: neo-project/neo-gui


text:
Deal with void return value correctly

Now the evaluation stack return nothing when there is no return value. so it will caused error on this piece of code.
https://github.com/neo-project/neo-node/blob/3acb8aa42c42bc2817fd958444a7dab182c19082/neo-cli/CLI/MainService.cs#L565-L568
for example:
invoke NNS with AddRoot method:
        [ContractMethod(0_03000000, CallFlags.WriteStates)]
        private void AddRoot(ApplicationEngine engine, string root)
        {
            if (!rootRegex.IsMatch(root)) throw new ArgumentException(null, nameof(root));
            if (!CheckCommittee(engine)) throw new InvalidOperationException();
            StringList roots = engine.Snapshot.Storages.GetAndChange(CreateStorageKey(Prefix_Roots), () => new StorageItem(new StringList())).GetInteroperable<StringList>();
            int index = roots.BinarySearch(root);
            if (index >= 0) throw new InvalidOperationException("The name already exists.");
            roots.Insert(~index, root);
        }

Work fine in mine
public class Contract1 : SmartContract
    {
        public static void a()
        {

        }
    }

Work fine in mine
public class Contract1 : SmartContract
    {
        public static void a()
        {

        }
    }

repo: neo-project/neo-node


text:
Update README.md

please accept it

Please pick up an issue from our https://github.com/neo4j-labs/neodash/issues list.
Thanks!


text:
Require properties be tagged for multiparameter attribute support?

Rails has the concept of multiparameter attributes, which are properties that get broken into pieces for a view and then assembled magically by the model. datetime_select is an example, http://api.rubyonrails.org/classes/ActionView/Helpers/DateHelper.html#method-i-datetime_select.
Adding support for this was one of my earliest contributions to the gem, using code I found somewhere from someone who was trying to add support to another ORM. Looking at it now, I see that it's pretty expensive. https://github.com/neo4jrb/neo4j/blob/master/lib/neo4j/shared/property.rb#L77. At a minimum, that's two new hashes for every node that comes through, more than that if something has changed.
I propose that we add a multiparameter: true option to the property class method. We can then change this method to only try "reassembling" those multiple fields if it has reason to believe that they might be present. It puts the burden on the user, which might bug some Rails users, but I think that it's in everyone else's best interest.

No.

license: mit


text:
[NeoML] Sort fields by size to decrease the struct size

If one have large number of fields, arranging them in order of size, from largest to smallest, may result in slightly less memory usage.

Would you mind writing a "before"-"after" comparison please? Just hover a mouse over constexpr auto res = sizeof( T ) and VS will show you the result.

Would you mind writing a "before"-"after" comparison please? Just hover a mouse over constexpr auto res = sizeof( T ) and VS will show you the result.

Thank you, good point
Before
sizeof CDnn           = 200
sizeof CBaseLayer     = 424

After
sizeof CDnn           = 192
sizeof CBaseLayer     = 400

Difference is small, because it is the very small possibility to stack structs, and gain of ints and booleans stack is small.

authors: favorart pavel-voropaev

repo: neoml-lib/neoml


text:
"could not remove ephemeral file" warning in detach

From the log of test_normal_work.py test, for example:
2022-12-11T22:58:32.714259Z  WARN tenant_detach{tenant=7f3e10b05470d621ee7b5dd3e2665d5d}: could not remove ephemeral file '/home/heikki/git-sandbox/neon/test_output/test_normal_work[3-1]/repo/tenants/7f3e10b05470d621ee7b5dd3e2665d5d/timelines/ebcec4755ec8392b0de2c297359d76b7/ephemeral-2': No such file or directory (os error 2)

This warning is allowlisted in neon_fixtures.py:
            # FIXME: there is a race condition between GC and detach, see
            # https://github.com/neondatabase/neon/issues/2442
            ".*could not remove ephemeral file.*No such file or directory.*",

I did some digging, and that diagnosis is not quite right. GC is not involved. The problem is in the detach code itself. task_mgr::detach_tenant does this:

Put the tenant to Stopping state
Wait for all tasks registered with the tenant to finish
Remove all files in the tenant-directory
Remove the Tenant from the TENANTS hash map

The warning happens in step 4. When the Tenant is removed from the hash map and dropped, it drops all its Timelines, and the possible EphemeralFiles held open by in-memory layers of those Timelines. Dropping the EphemeralFile struct unlinks the underlying file, but because we already removed it in step 3, it prints the warning.

Note that current we rely on the tenant present in the TENANTS hash map with the Stopping state up until the end of the operation: this way, we ensure no other operations can be launched during tenant shutdown.

authors: SomeoneToIgnore hlinnaka

repo: neondatabase/neon


text:
Bug in load_layer_map() treatment of future layers

        for filename in &deltafilenames {
            ensure!(filename.start_lsn < filename.end_lsn);
            if filename.end_lsn > disk_consistent_lsn {
                warn!(
                    "found future delta layer {} on timeline {}",
                    filename, self.timelineid
                );

                rename_to_backup(timeline_path.join(filename.to_string()))?;
                continue;
            }

Now we skip delta files that are partially in the future.
filename.end_lsn > disk_consistent_lsn
It can lead to losing data between filename.start_lsn and disk_consistent_lsn
@hlinnaka , @patins , FYI
Maybe it's the same issue as #470

@lubennikovaav is this still relevant ?

Hmm the above code snippet is still very much with us: https://github.com/neondatabase/neon/blob/2153d2e00a917b675b454ae8d222e2946900e4d1/pageserver/src/tenant/timeline.rs#L1371-L1379
I'd say that the same bug could still happen, had not considered this ... Might chance some problematic issues in staging with missing layer files, unless those are deleted already.

It can easily happen after abnormal pageserver restart (when it is stoped without waiting checkpoint to be completed)
It this case there can be layers newer than disk consistent LSN and them should be removed (renamed) on startup.

@knizhnik is there an actionable given that we have safekeeprs and the WAL will be sent again ?
Is there anything else needed to do except from removing the "renamed" files ?
@lubennikovaav

Sorry, I do not understand what you mean by actionable?
Our storage is non-transactional. I.e. we can not enforce any ACID guarantees  when saving layers to the disk.
So current policy is the following:

Write data to the disk
Flush (fsync) changes
Advance disk consistent LSN

After restart we should remove all files with LSN > disk consistent LSN because we can not guarantee their consistency.
This layer files are not currently removed by renamed to  "*backup". It is done mostly for debugging reasons. This backup files can be safely removed and we replay from WAL all require changed.

The bug stated that we can actually lose data
From your explanation, I understand that it is not the case, and whenever we process "future" delta layers we rename them and discard them from loading (they will be recreated by safekeeper replaying the WAL) and we rename these layers to backup
The actionable work that we are left with here is to remove these backup files

The actionable work that we are left with here is to remove these backup files

And this was #3660.

closing this one as #3660 has the missing work

authors: knizhnik koivunej lubennikovaav shanyp


text:
control_plane: follow up for embedded migrations

Problem
In https://github.com/neondatabase/neon/pull/6637, we remove the need to run migrations externally, but for compat tests to work we can't remove those invocations from the neon_local binary.
Once that previous PR merges, we can make the followup changes without upsetting compat tests.
Summary of changes
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

@arpad-m this is the same stuff you already reviewed in #6637, just split into a second PR -- sorry for the noise.

Re-opened https://github.com/neondatabase/neon/issues/559 for the test_pg_regress failure.


text:
Proxy release 2024-07-25

Proxy release 2024-07-25
Please merge this Pull Request using 'Create a merge commit' button

Proxy changes:

https://github.com/neondatabase/neon/pull/8377
https://github.com/neondatabase/neon/pull/8470

authors: conradludgate vipvap


text:
E716 with ccls

Description
I use ccls as my language server. when I open or save a c file, I met this:

Error executing vim.schedule lua callback: [string ":lua"]:18: Vim(call):E716: Key not present in Dictionary: "uri"

my lspconfig in init.vim
lua << EOF
local nvim_lsp = require'lspconfig'
nvim_lsp.ccls.setup {
    cmd = { "ccls" };
    filetypes = { "c", "cpp", "objc", "objcpp" };
    root_dir = nvim_lsp.util.root_pattern("compile_commands.json", ".git");
	init_options = {
		highlight = {
			lsRanges = true;
		}
	};
}
EOF

Neovim version
NVIM v0.6.0-dev+551-ged2573b7e
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Nvim-lspconfig version
No response
Operating system and version
Ubuntu 18.04
Affected language servers
ccls
Steps to reproduce

open a c flile
save file (:w)

Actual behavior

Error executing vim.schedule lua callback: [string ":lua"]:18: Vim(call):E716: Key not present in Dictionary: "uri"

Expected behavior
No response
Minimal config
:-)

Health check
lspconfig: require("lspconfig.health").check()

INFO: ccls: configuration checked.

LSP log
Nothing

Can't reproduce on master

more infomation on latest nvim：
Error executing vim.schedule lua callback: [string ":lua"]:22: Vim(call):E716: Key not present in Dictionary: "uri"
stack traceback:
        [C]: in function 'nvim_call_function'
        [string ":lua"]:22: in function 'handler'
        ...mount_nvim682tB1u/usr/share/nvim/runtime/lua/vim/lsp.lua:700: in function 'cb'
        vim.lua:285: in function <vim.lua:285>

There's nothing in your log when you use the minimal config included in this repo?

nvim0.5 not have this problem. Here is log:
[ START ] 2021-11-08T17:15:18+0800 ] LSP logging initiated
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.111] clangd version 9.0.0-2~ubuntu18.04.2 (tags/RELEASE_900/final)\nI[17:15:19.111] Working directory: /home/wangxb/work/hybrid-dvr/utils/shy_demux\nI[17:15:19.111] argv[0]: clangd-9\nI[17:15:19.111] argv[1]: --background-index\nI[17:15:19.111] Starting LSP over stdin/stdout\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.479] <-- initialize(1)\nI[17:15:19.479] --> reply:initialize(1) 0 ms\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	'17:15:19 ccls           initialize.cc:274 I initialize in directory /home/wangxb/work/hybrid-dvr/utils/shy_demux with uri file:///home/wangxb/work/hybrid-dvr/utils/shy_demux\n17:15:19 ccls           initialize.cc:297 I initializationOptions: {"compilationDatabaseCommand":"","compilationDatabaseDirectory":"","cache":{"directory":".ccls-cache","format":"binary","hierarchicalPath":false,"retainInMemory":2},"capabilities":{"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"}","moreTriggerCharacter":[]},"foldingRangeProvider":true,"workspace":{"workspaceFolders":{"supported":true,"changeNotifications":true}}},"clang":{"excludeArgs":[],"extraArgs":[],"pathMappings":[],"resourceDir":""},"client":{"diagnosticsRelatedInformation":true,"hierarchicalDocumentSymbolSupport":true,"linkSupport":true,"snippetSupport":true},"codeLens":{"localVariables":true},"completion":{"caseSensitivity":2,"detailedLabel":true,"dropOldRequests":true,"duplicateOptional":true,"filterAndSort":true,"include":{"blacklist":[],"maxPathSize":30,"suffixWhitelist":[".h",".hpp",".hh",".inc"],"whitelist":[]},"maxNum":100,"placeholder":true},"diagnostics":{"blacklist":[],"onChange":1000,"onOpen":0,"onSave":0,"spellChecking":true,"whitelist":[]},"highlight":{"largeFileSize":2097152,"lsRanges":true,"blacklist":[],"whitelist":[]},"index":{"blacklist":[],"comments":2,"initialNoLinkage":false,"initialBlacklist":[],"initialWhitelist":[],"maxInitializerLines":5,"multiVersion":0,"multiVersionBlacklist":[],"multiVersionWhitelist":[],"name":{"suppressUnwrittenScope":false},"onChange":false,"parametersInDeclarations":true,"threads":0,"trackDependency":2,"whitelist":[]},"request":{"timeout":5000},"session":{"maxNum":10},"workspaceSymbol":{"caseSensitivity":1,"maxNum":1000,"sort":true},"xref":{"maxNum":2000}}\n17:15:19 ccls           initialize.cc:329 I use -resource-dir=/snap/ccls/current//usr/lib/llvm-7/lib/clang/7.0.0\n17:15:19 ccls           initialize.cc:361 I workspace folder: /home/wangxb/work/hybrid-dvr/utils/shy_demux/\n'
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 ccls              project.cc:426 I loaded /home/wangxb/work/hybrid-dvr/utils/shy_demux/compile_commands.json\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 ccls              project.cc:473 I search directory: /usr/include/ <\n17:15:19 ccls              project.cc:473 I search directory: /include/ <\n17:15:19 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/ext/libxeDEX/include/  \n17:15:19 ccls              project.cc:473 I search directory: /usr/local/include/ <\n17:15:19 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/ext/libxeLOG/include/  \n17:15:19 ccls              project.cc:473 I search directory: /snap/ccls/current/usr/lib/llvm-7/lib/clang/7.0.0/include/ <\n17:15:19 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/inc/  \n17:15:19 ccls              project.cc:473 I search directory: /usr/include/x86_64-linux-gnu/ <\n17:15:19 ccls           initialize.cc:386 I start 4 indexers\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 ccls           initialize.cc:394 I dispatch initial index requests\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.483] <-- initialized\nI[17:15:19.483] unhandled notification initialized\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 indexer3         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/mpeg4_parse.c\n17:15:19 indexer2         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/simple_demux.c\n17:15:19 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/h264_parse.c\n17:15:19 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/streampull.c\n17:15:19 ccls             pipeline.cc:493 I loaded project. Refresh semantic highlight for all working file.\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.485] <-- textDocument/didOpen\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 indexer2         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/hecp.c\n17:15:19 indexer3         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/test.c\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.500] Enqueueing 0 commands for indexing\nI[17:15:19.500] Updating file /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c with command inferred from /home/wangxb/misc/myApp/shy_demux/src/simple_demux.c\n[/home/wangxb/misc/myApp/shy_demux/build]\n/usr/bin/cc -DCONFIG_USE_XEDEX2=1 -DXELOG_2_CONSOLE=1 -Wall -O2 -I/home/wangxb/misc/myApp/shy_demux/inc -I/home/wangxb/misc/myApp/shy_demux/ext/libxeLOG/include -I/home/wangxb/misc/myApp/shy_demux/ext/libxeDEX/include -c /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c -fsyntax-only -resource-dir=/usr/lib/llvm-9/lib/clang/9.0.0\nI[17:15:19.500] Couldn't set working directory when creating compiler invocation.\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"ccls"	"stderr"	"17:15:19 preamble     sema_manager.cc:763 I create session for /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c\n17:15:19 indexer1         pipeline.cc:298 I load cache for /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.510] Couldn't set working directory when building the preamble.\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.610] Couldn't set working directory when building the preamble.\n"
[ ERROR ] 2021-11-08T17:15:19+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:19.650] --> textDocument/publishDiagnostics\n"
[ ERROR ] 2021-11-08T17:15:20+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:20.165] <-- shutdown(2)\nI[17:15:20.165] --> reply:shutdown(2) 0 ms\n"
[ ERROR ] 2021-11-08T17:15:20+0800 ] ...nt_nvimIQB1BI/usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:462 ]	"rpc"	"clangd-9"	"stderr"	"I[17:15:20.165] <-- exit\n"
[START][2021-11-08 17:15:26] LSP logging initiated
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.587] clangd version 9.0.0-2~ubuntu18.04.2 (tags/RELEASE_900/final)\nI[17:15:27.587] Working directory: /home/wangxb/work/hybrid-dvr/utils/shy_demux\nI[17:15:27.587] argv[0]: clangd-9\nI[17:15:27.587] argv[1]: --background-index\nI[17:15:27.587] Starting LSP over stdin/stdout\nI[17:15:27.587] <-- initialize(1)\nI[17:15:27.587] --> reply:initialize(1) 0 ms\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 ccls           initialize.cc:274 I initialize in directory /home/wangxb/work/hybrid-dvr/utils/shy_demux with uri file:///home/wangxb/work/hybrid-dvr/utils/shy_demux\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	'17:15:27 ccls           initialize.cc:297 I initializationOptions: {"compilationDatabaseCommand":"","compilationDatabaseDirectory":"","cache":{"directory":".ccls-cache","format":"binary","hierarchicalPath":false,"retainInMemory":2},"capabilities":{"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"}","moreTriggerCharacter":[]},"foldingRangeProvider":true,"workspace":{"workspaceFolders":{"supported":true,"changeNotifications":true}}},"clang":{"excludeArgs":[],"extraArgs":[],"pathMappings":[],"resourceDir":""},"client":{"diagnosticsRelatedInformation":true,"hierarchicalDocumentSymbolSupport":true,"linkSupport":true,"snippetSupport":true},"codeLens":{"localVariables":true},"completion":{"caseSensitivity":2,"detailedLabel":true,"dropOldRequests":true,"duplicateOptional":true,"filterAndSort":true,"include":{"blacklist":[],"maxPathSize":30,"suffixWhitelist":[".h",".hpp",".hh",".inc"],"whitelist":[]},"maxNum":100,"placeholder":true},"diagnostics":{"blacklist":[],"onChange":1000,"onOpen":0,"onSave":0,"spellChecking":true,"whitelist":[]},"highlight":{"largeFileSize":2097152,"lsRanges":true,"blacklist":[],"whitelist":[]},"index":{"blacklist":[],"comments":2,"initialNoLinkage":false,"initialBlacklist":[],"initialWhitelist":[],"maxInitializerLines":5,"multiVersion":0,"multiVersionBlacklist":[],"multiVersionWhitelist":[],"name":{"suppressUnwrittenScope":false},"onChange":false,"parametersInDeclarations":true,"threads":0,"trackDependency":2,"whitelist":[]},"request":{"timeout":5000},"session":{"maxNum":10},"workspaceSymbol":{"caseSensitivity":1,"maxNum":1000,"sort":true},"xref":{"maxNum":2000}}\n17:15:27 ccls           initialize.cc:329 I use -resource-dir=/snap/ccls/current//usr/lib/llvm-7/lib/clang/7.0.0\n17:15:27 ccls           initialize.cc:361 I workspace folder: /home/wangxb/work/hybrid-dvr/utils/shy_demux/\n'
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 ccls              project.cc:426 I loaded /home/wangxb/work/hybrid-dvr/utils/shy_demux/compile_commands.json\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 ccls              project.cc:473 I search directory: /usr/include/ <\n17:15:27 ccls              project.cc:473 I search directory: /include/ <\n17:15:27 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/ext/libxeDEX/include/  \n17:15:27 ccls              project.cc:473 I search directory: /usr/local/include/ <\n17:15:27 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/ext/libxeLOG/include/  \n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 ccls              project.cc:473 I search directory: /snap/ccls/current/usr/lib/llvm-7/lib/clang/7.0.0/include/ <\n17:15:27 ccls              project.cc:473 I search directory: /home/wangxb/misc/myApp/shy_demux/inc/  \n17:15:27 ccls              project.cc:473 I search directory: /usr/include/x86_64-linux-gnu/ <\n17:15:27 ccls           initialize.cc:386 I start 4 indexers\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 ccls           initialize.cc:394 I dispatch initial index requests\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/simple_demux.c\n17:15:27 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/h264_parse.c\n17:15:27 indexer3         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/src/mpeg4_parse.c\n17:15:27 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/test.c\n17:15:27 indexer1         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/hecp.c\n17:15:27 ccls             pipeline.cc:493 I loaded project. Refresh semantic highlight for all working file.\n17:15:27 indexer3         pipeline.cc:386 I delete /home/wangxb/misc/myApp/shy_demux/test/streampull.c\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.969] <-- initialized\nI[17:15:27.969] unhandled notification initialized\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.970] <-- textDocument/didOpen\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.973] Enqueueing 0 commands for indexing\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 indexer1         pipeline.cc:298 I load cache for /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"ccls"	"stderr"	"17:15:27 preamble     sema_manager.cc:763 I create session for /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.982] Updating file /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c with command inferred from /home/wangxb/misc/myApp/shy_demux/src/simple_demux.c\n[/home/wangxb/misc/myApp/shy_demux/build]\n/usr/bin/cc -DCONFIG_USE_XEDEX2=1 -DXELOG_2_CONSOLE=1 -Wall -O2 -I/home/wangxb/misc/myApp/shy_demux/inc -I/home/wangxb/misc/myApp/shy_demux/ext/libxeLOG/include -I/home/wangxb/misc/myApp/shy_demux/ext/libxeDEX/include -c /home/wangxb/work/hybrid-dvr/utils/shy_demux/src/simple_demux.c -fsyntax-only -resource-dir=/usr/lib/llvm-9/lib/clang/9.0.0\nI[17:15:27.982] Couldn't set working directory when creating compiler invocation.\n"
[ERROR][2021-11-08 17:15:27] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:27.984] Couldn't set working directory when building the preamble.\n"
[ERROR][2021-11-08 17:15:28] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:28.055] Couldn't set working directory when building the preamble.\n"
[ERROR][2021-11-08 17:15:28] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:28.094] --> textDocument/publishDiagnostics\n"
[ERROR][2021-11-08 17:15:36] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:36.297] <-- shutdown(2)\nI[17:15:36.297] --> reply:shutdown(2) 0 ms\n"
[ERROR][2021-11-08 17:15:36] .../vim/lsp/rpc.lua:412	"rpc"	"clangd-9"	"stderr"	"I[17:15:36.297] <-- exit\n"

I am almost certain there is a plugin in your runtime path that is setting up a handler override which matches the 0.5 style handlers. I need you to confirm that you're using the exact minimal init.lua from the issue template.

I am almost certain there is a plugin in your runtime path that is setting up a handler override (lspsaga or otherwise) which matches the 0.5 style handlers. I need you to confirm that you're using the exact minimal init.lua from the issue template. You can also temporarily move ~/.local/share/nvim to a backup location (be careful, this contains your undos)

Yes! I comment my plugin one by one, and found that vim-lsp-cxx-highlight is the problem. thank you.

authors: lasypig mjlbach

repo: neovim/nvim-lspconfig


text:
docs: make vimdocs consistent with readme

Add changes from #2514 to vimdoc. Better late than never. Also fix lsp-config links, it's lspconfig

As far as the current readme goes, in my opinion the way it is right now is okay, I don't see anything that's unnecessary there. You only get the most important information to get you started and the most common pitfalls. Yes, there is some duplication, but in this case I think it's worth it to get the basic instructions on how to configure lspconfig more visible.


text:
Fix missing migration

Fix #432

Coverage remained the same at 95.699% when pulling bd9fce88c235ea6be032a1d15a31bf41df14a444 on hotfix/missing_migration into e6a717040584fc12aa490d986ff0cdcc043724cb on release/0.9.x.

authors: coveralls yakky

repo: nephila/djangocms-blog


text:
I saw a little issue.

This condition will always be “true”:
https://github.com/nerd-of-now/NCP-VGC-Damage-Calculator/blob/main/script_res/ap_calc.js#L664
should use "!="

If you're referring to the "!==", it is a more precise "!=" in JavaScript.

After going through it, the operator wasn't the issue; JavaScript just doesn't perform the operation as expected. The rest of the code's still follows the same logic, so I didn't catch it. Removing the code would work, but using jQuery's $.isEmptyObject() fixes the condition and seems to have better performance. https://github.com/nerd-of-now/NCP-VGC-Damage-Calculator/commit/f5a939e1ce78c224ed0fa5bb4694a34d8a3cac17

authors: Uahh nerd-of-now

repo: nerd-of-now/NCP-VGC-Damage-Calculator


text:
A strange bug report when I use Sceneconstract with gaussian.

How did you create the Gaussians? Can you try printing the types of mask, positions.cov and jc_means

authors: qhdqhd tancik

repo: nerfstudio-project/nerfstudio


text:
Modal creation

Support the generation of modals from python, ie:

The modals should support leva panels and markdown.

Implemented in #72

authors: jonahbedouch tancik

repo: nerfstudio-project/viser


text:
Is it possible to support tf-tree visualization?

Thanks for this great project.
I see that there are pose adjustments that support various joints in SMPL to pull the deformation of the model.
I tried to find a python visualization to simulate the tf-tree in ROS/rviz for visualization.
In fact, it is to add multiple coordinate systems according to the transformation matrix and establish the connection between them. (It would be better if it could support displaying text)
I would like to inquire whether viser can currently support the implementation of this feature through some add functions.

Hi!
Yeah, many of us working on viser are coming from robotics backgrounds (and/or using it for robotics projects), so supporting tf-style frame trees is important to us. The way things are setup emulates meshcat's interface for transformation trees.
You can try looking through the code for the first example: https://nerfstudio-project.github.io/viser/examples/00_coordinate_frames/
For text, you can see how add_gui_label() is called in the camera commands example: https://nerfstudio-project.github.io/viser/examples/05_camera_commands/
There's also a blurb about how the "scene node" name works here: https://nerfstudio-project.github.io/viser/conventions/#scene-tree-naming

Hi @brentyi, Thank you for your quick and detailed answer, I will try it out later and give you feedback

Hi @brentyi, Thanks for the reminder, we tested it and it met our expectations. Thank you so much!
I will close this issue.

authors: MaxChanger brentyi


text:
Nest 8 + amqp bug

ERROR [ExceptionHandler] Nest can't resolve dependencies of the AmqpModule (?). Please make sure that the argument ModuleRef at index [0] is available in the AmqpModule context.
Potential solutions:

If ModuleRef is a provider, is it part of the current AmqpModule?
If ModuleRef is exported from a separate @Module, is that module imported within AmqpModule?
@Module({
imports: [ /* the Module containing ModuleRef */ ]
})

Error: Nest can't resolve dependencies of the AmqpModule (?). Please make sure that the argument ModuleRef at index [0] is available in the AmqpModule context.
Potential solutions:

If ModuleRef is a provider, is it part of the current AmqpModule?
If ModuleRef is exported from a separate @Module, is that module imported within AmqpModule?
@Module({
imports: [ /* the Module containing ModuleRef */ ]
})

Hello,
having the same with nestjs 9.0.11.
Downgrading nest to 8.0.0 made my app start again.
Was this issue ever solved?
Thanks and best regards

authors: SergioArrighi huangang

repo: nest-x/nestx-amqp


text:
[25] createch discipline classifier

Closes #25
Checklist:

[ ] I have refactored my code out from notebooks/
[ ] I have checked the code runs
[ ] I have tested the code
[ ] I have run pre-commit and addressed any issues not automatically fixed
[ ] I have merged any new changes from dev
[ ] I have documented the code

[ ] Major functions have docstrings
[ ] Appropriate information has been added to READMEs

[ ] I have explained the feature in this PR or (better) in output/reports/
[ ] I have requested a code review

Merging #26 and #22 into one.


text:
Ready for release 1.1.0

Uses the behaviour correctly for the create_task typespec and bumps version number to 1.1.0

Coverage remained the same at 73.611% when pulling 7c1d71c0294534115ed0e88d13ec5b693c91b150 on create-task into 7834b7d87efa4e4ac050b07094e7b83513ad1223 on master.

authors: P-WM coveralls

repo: nested-tech/closex


text:
Docker Desktop Compatibility (Windows 11)

Hello,
I am trying to use Sysbox with Docker Desktop (WSL version: 2.0.14.0, Kernel version: 5.15.133.1-1).
I am wondering if Sysbox supports my system or if I should use Ubuntu instead.

Hi @naderayed, thanks for your inquiry.
So there's a couple of options:
Docker Desktop includes Sysbox already, but uses it for a feature called Enhanced Container Isolation. This is meant to secure development environments by running all containers in rootless mode. It also allows you to run Docker-in-Docker in rootless mode. Take a look at the link above and check if that's what you need.
Alternatively, if you want to use Sysbox with the basic Docker Engine (not Docker Desktop) on WSL, that also works. In that case you install Docker Engine and Sysbox on the Ubuntu WSL distro as you would on any other Ubuntu host.
Hope that helps.

Closing ...

@ctalledo Since "Enhanced Container Isolation" is a business feature, is there any other way to use Sysbox with Docker Desktop?

Hi @lsalazarm99,

Since "Enhanced Container Isolation" is a business feature, is there any other way to use Sysbox with Docker Desktop?

Not currently ... thanks.

authors: ctalledo lsalazarm99 naderayed

repo: nestybox/sysbox


text:
External secret for email password

Noticed that this was one of the only credentials I couldn't slap into an external secret and source from the chart. This should allow that functionality. I did test locally and it looked like it put the value in all of the right places. Didn't find a whole lot about guidelines on contributing, so let me know if there's anything additional I need to do. Thanks!

Splitting up the secrets into function is certainly not a bad idea. It seems you've already done a fair deal of that, if you're talking about what I think you are. Also, thanks for the suggestions. Committing now.

@LeoColomb Is there something specific I need to do to pass the failing check? Is it just increasing Chart version in Chart.yaml to 5.0.0-beta.155?

@KittyKatt Yes, a bump if the version would make it pass. 😊
Thanks!

@KittyKatt Yes, a bump of the version would make it pass. 😊
Thanks!

Thanks! Sorry I didn't see it sooner. Happy to see it get merged!

authors: KittyKatt LeoColomb

repo: netbox-community/netbox-chart


text:
求助！mfa执行第6步报错，老板等着要demo，求救求救

MFA Step6
已执行
mfa validate
--overwrite
--clean
--single_speaker
data/DataBaker/mfa/lab
data/DataBaker/mfa/mfa_pronounciation_dict.txt
执行报错
mfa train
--overwrite
--clean
--single_speaker
data/DataBaker/mfa/lab
data/DataBaker/mfa/mfa_pronounciation_dict.txt
data/DataBaker/mfa/mfa/mfa_model.zip
data/DataBaker/mfa/TextGrid
我是下载了freeDatasets的素材，放到了data/DataBaker/raw下，只保留了10条，用来尝试根据声音文件和文本标签来克隆， 删掉了PhoneLabeling下的内容，
data/
├── DataBaker
│   ├── README.md
│   ├── raw
│   │   └── BZNSYP
│   │       ├── PhoneLabeling
│   │       ├── ProsodyLabeling
│   │       │   └── 000001-000010.txt
│   │       └── Wave
│   │           ├── 000001.wav
│   │           ├── 000002.wav
│   │           ├── 000003.wav
│   │           ├── 000004.wav
│   │           ├── 000005.wav
│   │           ├── 000006.wav
│   │           ├── 000007.wav
│   │           ├── 000008.wav
│   │           ├── 000009.wav
│   │           └── 000010.wav

当执行到step6 第二条命令时就报错了，看不懂这个是什么错误
报错信息如下：
/home/ifebs/miniconda3/envs/EmotiVoiceTrain/bin/gmm-boost-silence --boost=1.0 1 /home/ifebs/Documents/MFA/lab/lda/10.mdl -
LOG (gmm-boost-silence[5.5.1112]:main():gmmbin/gmm-boost-silence.cc:93) Boosted weights for 1 pdfs, by factor of 1
/home/ifebs/miniconda3/envs/EmotiVoiceTrain/bin/gmm-align-compiled --transition-scale=1.0 --acoustic-scale=0.1 --self-loop-scale=0.1 --beam=1
0 --retry-beam=40 --careful=false --write-per-frame-acoustic-loglikes=ark:/home/ifebs/Documents/MFA/lab/lda/like.1.3.ark - ark,s,cs:/home/ife
bs/Documents/MFA/lab/lda/fsts.1.3.ark 'ark,s,cs:splice-feats --left-context=3 --right-context=3 scp,s,cs:"/home/ifebs/Documents/MFA/lab/lab/s
plit3/feats.1.3.scp" ark:- | transform-feats "/home/ifebs/Documents/MFA/lab/lda/lda.mat" ark:- ark:- |' ark:/home/ifebs/Documents/MFA/lab/lda
/ali.1.3.ark ark,t:-
LOG (gmm-boost-silence[5.5.1112]:main():gmmbin/gmm-boost-silence.cc:103) Wrote model to -
splice-feats --left-context=3 --right-context=3 scp,s,cs:/home/ifebs/Documents/MFA/lab/lab/split3/feats.1.3.scp ark:-
transform-feats /home/ifebs/Documents/MFA/lab/lda/lda.mat ark:- ark:-
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:127) 1-7
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:617) Retrying utterance 1-7 with beam 40
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:626) Did not successfully decode file 1-7, len = 28
9
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:127) 1-8
LOG (transform-feats[5.5.1112]:main():featbin/transform-feats.cc:158) Overall average [pseudo-]logdet is -3.40272 over 880 frames.
LOG (transform-feats[5.5.1112]:main():featbin/transform-feats.cc:161) Applied transform to 3 utterances; 0 had errors.
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:617) Retrying utterance 1-8 with beam 40
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:626) Did not successfully decode file 1-8, len = 30
7
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:127) 1-9
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:617) Retrying utterance 1-9 with beam 40
WARNING (gmm-align-compiled[5.5.1112]:AlignUtteranceWrapper():decoder/decoder-wrappers.cc:626) Did not successfully decode file 1-9, len = 28
4
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:135) Overall log-likelihood per frame is -nan over 0 frames.
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:137) Retried 3 out of 3 utterances.
LOG (gmm-align-compiled[5.5.1112]:main():gmmbin/gmm-align-compiled.cc:139) Done 0, errors on 3

@syq163  哥 求帮忙

repo: netease-youdao/EmotiVoice


text:
Enums

Fixes #28


text:
On the fly hugo update by git-gateway

Hello,
is it possible to regenerate the site after each persisted entry by git-gateway? How could I have the copy of the repository also locally?
I see, that there is a gulp watching /site directory for changes, running hugo afterwards. The problem is, that by git-gateway (apparently) there is no local copy of the repository, so it is not being triggered.
So I have to wait for the automatic deployment, which is bad for the purpose of my app, as I need immediate result.
Thank you in advance!

You'd have to run git pull each time you save a change.

authors: erquhart uncledent

repo: netlify/netlify-cms


text:
Markdown Field Documentation is Incorrect (editor_components instead of editorComponents)

In the documentation here: https://www.netlifycms.org/docs/widgets/#markdown
It states:
editor_components: an array of strings representing the names of editor components to display (all shown by default). The image and code-block editor components are included with Netlify CMS by default, but others may be created and registered.
But the actual key is editorComponents

Thanks @acarnwath. this is related to another issue, where our docs represent the code on the default branch and not the published version of the CMS.
The change was done in https://github.com/netlify/netlify-cms/pull/4172, so the docs will be correct once we publish a new version.

authors: acarnwath erezrokah


text:
fix: remove unused devDependencies

Also:

replace make-dir and lodash packages with native
replace nyc with c8

Notes:

Opening for discussion. I know ideally I should have split this, but time :)
There's a TODO that should be addressed:
https://github.com/netlify/netlify-plugin-edge-handlers/blob/093e0eb2097d5e06e3b1f7f661b6209f49d06e4f/src/node-compat/globals.js#L7-L9
There were plenty of devDependencies present that are in @netlify/eslint-config-node hence why I dropped them
rollup-plugin-node-polyfills should be replaced because it's severely outdated
del can be replaced later when Node.js 12 support is dropped (or now if you are willing to workaround the deprecated rmdir)

I can try splitting some of these changes later if you want.

🎉 Thanks for sending this pull request! 🎉
Please make sure the title is clear and descriptive.
If you are fixing a typo or documentation, please skip these instructions.
Otherwise please fill in the sections below.
Which problem is this pull request solving?
Example: I'm always frustrated when [...]
List other issues or pull requests related to this problem
Example: This fixes #5012
Describe the solution you've chosen
Example: I've fixed this by [...]
Describe alternatives you've considered
Example: Another solution would be [...]
Checklist
Please add a x inside each checkbox:

[x] The status checks are successful (continuous integration). Those can be seen below.

BTW it seems that this fixes coverage in this repo because I guess nyc didn't include any files.
I'd still be interested to see if typescript is needed as a dependency. If not, it's a huge win. If it is, I guess the test suite needs to cover it too.

This is ready from my side @erezrokah :)

@erezrokah feel free to tackle the remaining TODO from the OP later :)

repo: netlify/netlify-plugin-edge-handlers


text:
hellodrkey example

This change is

_examples/hellodrkey/hellodrkey.go, line 54 at r1 (raw file):

func NewClient(sciondPath string) Client {
	sciond, err := sciond.NewService(sciondPath).Connect(context.Background())

Remove this empty line or add one in NewServer for consistency?

_examples/hellodrkey/hellodrkey.go, line 126 at r1 (raw file):

}

func (s Server) HostKey(meta drkey.Lvl2Meta) drkey.Lvl2Key {

Not used, right? Maybe remove this function to keep the example minimal?

_examples/hellodrkey/hellodrkey.go, line 151 at r1 (raw file):

	clientKey = client.HostKey(metaClient)

	durationClient := time.Since(t0)

Move this statement before the empty line?

_examples/hellodrkey/hellodrkey.go, line 29 at r1 (raw file):

)

var now = time.Now().UTC()

I didn't quite get why this is global var. Could we also keep it local to main and pass it around via function params?

a discussion (no related file):
I like the example because it is really minimal.
I already know the DRKey system a little bit from Lightning Filter and had no problem to understand what is going on here. Users with no prior knowledge will obviously have a harder time to understand the motivation for this example. What would be the best reference to get them started?

Does it make sense to maintain the new "invariant" (introduced during the SCIONLab update) that all examples have a README.md and that every example is also shortly referenced from the main README.md?

Maybe it would be helpful to also add a quick note to this example's README on how to generate the topology this example is expecting.

_examples/hellodrkey/README.md, line 22 at r2 (raw file):

Both slow and fast paths should obtain the same key.
And both slow and fast path are measure for performance and their times displayed at the end.

"measured" instead of "measure"?

a discussion (no related file):
Previously, juagargi (Juan A. Garcia Pardo) wrote…
Thanks for the review. Indeed much more documentation was needed. I followed your advice and added the README with a description of what hellodrkey does, and how to configure the gen directory for it to run.

Thanks, Juan. I think the new README is very helpful.

_examples/hellodrkey/hellodrkey.go, line 34 at r2 (raw file):

)

// should return the same timestamp everytime that it's called, but for simplicity we just

Maybe "Should" instead of "should"?

_examples/hellodrkey/README.md, line 30 at r3 (raw file):

1. Create a local topology with the `tiny.topo` description: `./scion.sh topology -c ./topology/tiny.topo`.
1. Edit the CS configuration for `ff00:0:111` under `gen/ff00_0_111/cs1-ff00_0_111-1.toml`

gen/ASff00_0_111/cs1-ff00_0_111-1.toml

_examples/hellodrkey/README.md, line 48 at r3 (raw file):

   connection = "gen-cache/sd1-ff00_0_111.drkey.db"

Edit the configuration for the CS in gen/ff00_0_112/cs1-ff00_0_112-1.toml and add:

gen/ASff00_0_112/cs1-ff00_0_112-1.toml

I've tested the DRKey example with the configuration described in the new README: works perfectly -- just two small typos see below. Thank you very much!

authors: juagargi marcfrei

repo: netsec-ethz/scion-apps


text:
Fix ObjectUtil message in HttpContentCompressor

Motivation:
In #11256, We introduced Iterable as a parameter but later in review, it was removed. But we forgot to change compressionOptionsIterable to just compressionOptions.
Modification:
Changed compressionOptionsIterable to compressionOptions.
Result:
Correct ObjectUtil message

@hyperxpro thanks a lot!

authors: hyperxpro normanmaurer

repo: netty/netty


text:
SockJS Support for Netty4

Please see sockjs/README.md for instructions about running tests general information regarding the SockJS support.

Any update on this? Would love sock.js support in netty! :+1:

@mortan I'm currently working on getting https://github.com/netty/netty/pull/3271 merged and after that I'll rebase and hopefully a final round of reviews before merging. Can't give an exact date but there should be some updates to this PR shortly, hopefully later this week or next.

Hey @danbev, is there any update to this? Is there anything I can do to help?

This needs to be rebased against the latest 4.1 version and verify that
things are working correctly. The last rebase passed the
sockjs-protocol-0.3.3 but only after custom updates due to how header
values are compared in the test, so nothing major. I've not got much time
at the moment due to parental leave but will try to rebase and run the
sockjs-protocol tests this weekend and also update the PR against
sockjs-protocol (the header issue mentioned above)
onsdag 4 mars 2015 skrev Tiger Toes notifications@github.com:

Hey @danbev https://github.com/danbev, is there any update to this? Is
there anything I can do to help?
—
Reply to this email directly or view it on GitHub
https://github.com/netty/netty/pull/1615#issuecomment-77157895.

Still sitting on the edge of my seat and waiting for it! :)

authors: danbev mortan tigertoes


text:
Update LineBasedFrameDecoder.java

Wrong count of discardedByes, because already discarded count is overwritten.

Sorry, that was crap. The wrapping if condition ensures, that no discarding has happened before.

@sja no problem :)

authors: normanmaurer sja


text:
codec-http2: Mark requests as chunked in Http2ServerDowngrader

Motivation:
Http2ServerDowngrader doesn't mark chunked requests as chunked, even
though the natural conversion from http/2 requests to http/1.1 requests
is to chunked ones.
Modifications:
Mark requests that aren't already complete as chunked.
Result:
Requests will be chunked, and can later be aggregated if necessary.

cc @normanmaurer @ejona86 @buchgr @Scottmitch

@mosesn LGTM... @nmittler @ejona86 @buchgr @Scottmitch PTAL as well

@mosesn LGTM

LGTM

@mosesn LGTM... can you please squash the commits ?

1 nit and lgtm

@Scottmitch @normanmaurer fixed and squashed!

@mosesn awesome. I will cherry-pick once the CI build completes.

Cherry-picked into 4.1 (da8734a6f9213cfdcf92b63fe8d014989e0ced18)

thanks @mosesn !

authors: Scottmitch buchgr ejona86 mosesn normanmaurer


text:
Remove unnecessary line in Http2ClientUpgradeCodec

Motivation:
To clean up code.
Modification:
Remove unnecessary line.
Result:
There's no functional change.

@netty-bot test this please

@monkey-mas thanks a lot!

authors: monkey-mas normanmaurer


text:
Use cases instead of API call to get systemOutputs

Background
Previously in AnalysisTable, we called the API backendClient.systemOutputsGetById() to collect systemOutputs. And we used these to display the examples in our ExampleTable.
However, the examples we need already exist in the cases argument which are passed in while creating the AnalysisTable component, so the use of API can actually be removed. On top of that, the examples we show in the table should be derived from the cases in each bucket instead of the systemOutputs.
Changes
In this PR, I added a function convertCasesToSystemOutput() in .../AnalysisTable/utils.tsx which converts the cases format to systemOutput format. By using this function, we can replace the need to call the API.
Next steps
It also seems that all variables using the struct SystemOutput used in AnalysisTable could be changed to AnalysisCase after this PR. Since there are quite a few functions using SystemOutput structs, I will make these changes in a different PR.

Closing this PR because I just noticed it doesn't work for sequence labeling tasks.


text:
Extend basic VAE example for regression models

We need a basic VAE example for regression models. So far, the class only implements binary and categorical classification.
The simplest case would be Gaussian / Normal outputs (mean and variance) at each output node of the decoder. We also need to add the respective computation of the log_prob for this case (should essentially be MSE if we use the mean of the output .

vaes/vae_example.ipynb

Thanks @Kajalsingla1997 for implementing the normal distribution cbf6648d2d64dbdf58a5d8c187570406b57bb7b7

Still open:

[] implement log_variance estimate in the decoder (output mean and log_variance)
[] use estimated log_variance in the loss function
[] test variance loss
[] use estimated log_variance in the sampling method of the Decoder
[] test sampling

Thus far, the samples generated by the heteroscedastic model (per sample variance) from MNIST are not convincing, though the model seems to have converged during training.
According to Chapter 5 (Loss Functions) from https://udlbook.github.io/udlbook/ we could try squaring our variance estimate instead of predicting the log variance (though that shouldn't be an issue).

[ ] check out the implementation of a full gaussian loss function at https://github.com/udlbook/udlbook/blob/main/Notebooks/Chap05/5_1_Least_Squares_Loss.ipynb
[ ] implement square(-root) estimate of variance


text:
Synth data

Implements a data generator. The same latent variables are generated from gaussian mixtures (supervised) and then one view is transformed according to a given transformation (built in defaults but accepts a custom function).

Plotting and simulator are up. Html documentation looks good and I made some minor updates to some HTML to make headers look better. (mvlearn.embed => Embed)

repo: neurodata/mvlearn