3.6.0

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

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

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

Installer update

Mac Install Fix: package sentinel into the installer

3.3.52

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

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

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.

3.3.27

Visual Studio Build Tools Hotfix

Previous fix from 3.3.25 neglected the scenario where the user doesn't have visual studio build tools installed (which will be true for most new--non developer--users just installing pinokio).

Because i couldn't uninstall and reinstall visual studio every time i test the new version, neglected to check this scenario. But just replicated this by actually uninstalling build tools and starting from scratch.

The problem has been fixed now. New users should not have any issue getting started

3.3.25

Windows Fix

This release is mainly for Windows users. More specifically for apps that require building/compiling from source code.

Visual Studio Build Tools and CUDA were not working properly on Windows. This didn't affect a lot of apps since many apps use prebuilt wheels. But some apps (such as 3D mesh generation AI apps) required building from source, and these apps were failing to install for many users.

This updated fixes all of this.

1. Visual Studio Handling: instead of injecting environment variables manually, just use the official vcvarsall.bat right after conda activation.
2. CUDA Handling: In case there's a globally installed CUDA that gets leaked in, remove those attributes so the base environment will use the CUDA installed inside the pinokio home environment

3.3.8

fs.link hotfix

fs.link fix for installing pip from github (ex: git+https://github.com/huggingface/diffusers.git)

• fixes fluxgym install issue, as well as other installers that use fs.link on any pip package that installs from github