Skip to content

Releases: pinokiocomputer/pinokio

3.6.23

20 Feb 13:29
Compare
Choose a tag to compare

libsqlite fix

libsqlite 3.49.0 has made a breaking change that breaks apps like stable-diffusion-webui or forge conda-forge/sqlite-feedstock#130

This is not a Pinokio bug, but anyone using a conda package that relies no libsqlite would have this issue (even if you manually install stuff without even using pinokio). As seen here lllyasviel/stable-diffusion-webui-forge#2669 and many other places.

The fundamental fix should be for the conda sqlite maintainers to actually fix this broken release but since we can't wait, going to fix this so it works even when they don't fix it anytime soon.

Fixed it by pinning sqlite at 3.47.2

3.6.7

19 Feb 15:23
Compare
Choose a tag to compare

Yet another FFMPEG fix

Problem: 3.6.5 Bugfix fixed the install issue (it wasn't even installing because a conda issue), but when actually trying to use after successfully installing (for example to extract frames) it was failing with DLL issues.

Fixes various DLL errors from video manipulating apps such as Facefusion.

Solution: Pin FFMPEG=5.1.2

3.6.5

18 Feb 22:57
Compare
Choose a tag to compare
  1. FFMPEG FIX: the latest version of ffmpeg conda package is broken because of some conflict, pin it to the previous version that works
  2. Mac sudo shell fix: use the new applet code that supports all archs

3.6.0

01 Feb 14:42
Compare
Choose a tag to compare

Lots and Lots of Bug Fixes

Again fixed a lot of issues based on bug reports since 3.3

Added in 3.6

  1. On Windows, give full write permission to ~/pinokio just to make sure we NEVER run into any EACCESS errors.
  2. Set CUDA_HOME to point to ~/pinokio/bin/miniconda
  3. build attribute added to shell.run: When "build": true, all the Visual Studio Build Tools related environment variables are injected into the shell.run session by running vcvarsall.bat.
  4. Script schema updated to <=3.6.0

Example:

{
  "method": "shell.run",
  "parrams": {
    "message": "python setup.py install",
    "build": true,
    "venv": "env"
  }
}

Added in 3.5

  1. Port 42000: all pinokio instances will now use port 42000 regardless of platform.
  2. UV Fix: In some cases, using the automatic python download feature of UV was not working properly because UV for some reason uses system python instead of managed python, which loses isolation. Now UV uses totally isolated managed python, which works on any OS and any system.
  3. visual studio installer fix
  4. Fix Networking issues: In some cases, having certain environment variables set messes up network connections, so Pinokio makes sure to ignore them
  5. Start logging immediately after the app starts (instead of after everything is initialized): Because something could go wrong while initializing, and need to capture hose too.

3.5.0

30 Jan 16:53
Compare
Choose a tag to compare
3.5.0 Pre-release
Pre-release

Bug Fix

Again fixed a lot of issues based on bug reports since 3.3

  1. Port 42000: all pinokio instances will now use port 42000 regardless of platform.
  2. UV Fix: In some cases, using the automatic python download feature of UV was not working properly because UV for some reason uses system python instead of managed python, which loses isolation. Now UV uses totally isolated managed python, which works on any OS and any system.
  3. visual studio installer fix
  4. Fix Networking issues: In some cases, having certain environment variables set messes up network connections, so Pinokio makes sure to ignore them
  5. Start logging immediately after the app starts (instead of after everything is initialized): Because something could go wrong while initializing, and need to capture hose too.

3.4.0

27 Jan 16:37
Compare
Choose a tag to compare

What's new

  1. Mac conda environment fix
  2. Mac xcode command line tools install fix
  3. Windows visual studio build tools install fix
  4. Linux build tools support (GXX via conda)
  5. Linux CUDA + G++ compatibility support (via an environment variable)
  6. More robust port availability checking logic.

1. Mac Conda Environment Fix

Set

CONDA_ENVS_PATH: ~/pinokio/bin/miniconda/envs
CONDA_PKGS_DIRS: ~/pinokio/bin/miniconda/pkgs

2. Mac xcode command line tools install fix

  • just because xocde-select -p returns a path doesn't mean it's installed.
  • to properly check the install state, must run ls -m $(xcode-select -p) to see if it returns Library, SDKs, and usr

3. Windows Visual Studio Refactor

  1. Handle cases where there are already multiple visual studio instances installed
  2. Handle cases where there are corrupt or paused installations of visual studio (build tools)
  3. Display a warning that if you get in an install loop, the best solution is to just open visual studio installer and uninstall broken installs

4. Linux CUDA & G++ Compatibility Fix

By default NVCC for CUDA121 requires G++ no greater than 12. But globally installed G++ may have higher versions and it would result in failure

5. More robust available port checking

is_port_running(port): To take into account ALL possible cases, instead of trying to create sockets to a url with a port, just simulate starting a server at the port, and if there's an exception, then it means the port doesn't work.

3.3.53

27 Jan 08:04
Compare
Choose a tag to compare
3.3.53 Pre-release
Pre-release
Installer update

Mac Install Fix: package sentinel into the installer

3.3.52

27 Jan 05:33
Compare
Choose a tag to compare
3.3.52 Pre-release
Pre-release

Mac Conda Environment Fix

Set

CONDA_ENVS_PATH: ~/pinokio/bin/miniconda/envs
CONDA_PKGS_DIRS: ~/pinokio/bin/miniconda/pkgs

Windows Visual Studio Refactor

  1. Handle cases where there are already multiple visual studio instances installed
  2. Handle cases where there are corrupt or paused installations of visual studio (build tools)
  3. Display a warning that if you get in an install loop, the best solution is to just open visual studio installer and uninstall broken installs

Linux CUDA & G++ Compatibility Fix

By default NVCC for CUDA121 requires G++ no greater than 12. But globally installed G++ may have higher versions and it would result in failure

More robust available port checking

is_port_running(port): To take into account ALL possible cases, instead of trying to create sockets to a url with a port, just simulate starting a server at the port, and if there's an exception, then it means the port doesn't work.

3.3.50

27 Jan 04:05
Compare
Choose a tag to compare
3.3.50 Pre-release
Pre-release

Mac Conda Environment Fix

Set

CONDA_ENVS_PATH: ~/pinokio/bin/miniconda/envs
CONDA_PKGS_DIRS: ~/pinokio/bin/miniconda/pkgs

Windows Visual Studio Refactor

  1. Handle cases where there are already multiple visual studio instances installed
  2. Handle cases where there are corrupt or paused installations of visual studio (build tools)
  3. Display a warning that if you get in an install loop, the best solution is to just open visual studio installer and uninstall broken installs

Linux CUDA & G++ Compatibility Fix

By default NVCC for CUDA121 requires G++ no greater than 12. But globally installed G++ may have higher versions and it would result in failure

More robust available port checking

is_port_running(port): To take into account ALL possible cases, instead of trying to create sockets to a url with a port, just simulate starting a server at the port, and if there's an exception, then it means the port doesn't work.

3.3.29

25 Jan 21:11
Compare
Choose a tag to compare

Sorry for the frequent releases, but it's important that we get this out asap so here we go.

One other edge case we discovered with Visual Studio Build Tools is, often VS buildtools 2022 FAILS when used during building wheels.

If you search online, the recommendation is to "downgrade" to 2019, so if we really wanted to have a robust system, Pinokio should enforce visual studio build tools 2019 no matter what. What this means is:

  1. If no visual studio installed => Install visual studio build tools 2019
  2. if visual studio build tools 2022 installed => install visual studio build tools 2019 => now you have both 2019 and 2022 (but pinokio will always use 2019 since 2022 often doesn't work and we can't risk that)
  3. If Visual Studio is installed (2022, 2019, etc) => Also install visual studio build tools 2019 => now you have normal visual studio and visual studio build tools 2019

Going forward, Pinokio will always make the user install Visual Studio Build Tools 2019.