Error occurs when processing files with Japanese names #205

New Issue

adam · 2025-12-30T01:22:11+01:00

adam commented

2025-12-30 01:22:11 +01:00

Originally created by @kaniza on GitHub (Sep 18, 2024).

I was trying to use the pkl command to process files with Japanese names. However, an error occurs when attempting to evaluate the file.

Information for Bug Report

pkl --version:

Pkl 0.26.3 (macOS 14.4.1, native)

Complete Error Message:

An unexpected error has occurred. Would you mind filing a bug report?

Steps to Reproduce

Check the version of pkl:

$ pkl --version
Pkl 0.26.3 (macOS 14.4.1, native)

Create a file en.pkl and check the content:
```
$ cat en.pkl
name = ""
```
Evaluate the file with pkl:
```
$ pkl eval en.pkl
name = ""
```
Copy the file and rename it to a Japanese name:
```
$ cp en.pkl 日本語.pkl
```

Attempt to evaluate the Japanese-named file:

$ pkl eval 日本語.pkl
An unexpected error has occurred. Would you mind filing a bug report?

Originally created by @kaniza on GitHub (Sep 18, 2024). I was trying to use the `pkl` command to process files with Japanese names. However, an error occurs when attempting to evaluate the file. #### Information for Bug Report - **pkl --version**: ``` Pkl 0.26.3 (macOS 14.4.1, native) ``` - **Complete Error Message**: ``` An unexpected error has occurred. Would you mind filing a bug report? ``` #### Steps to Reproduce 1. Check the version of `pkl`: ```shell $ pkl --version Pkl 0.26.3 (macOS 14.4.1, native) ``` 2. Create a file `en.pkl` and check the content: ```shell $ cat en.pkl name = "" ``` 3. Evaluate the file with `pkl`: ```shell $ pkl eval en.pkl name = "" ``` 4. Copy the file and rename it to a Japanese name: ```shell $ cp en.pkl 日本語.pkl ``` 5. Attempt to evaluate the Japanese-named file: ```shell $ pkl eval 日本語.pkl An unexpected error has occurred. Would you mind filing a bug report? ```

adam closed this issue

2025-12-30 01:22:12 +01:00

adam commented

2025-12-30 01:22:13 +01:00

@bioball commented on GitHub (Oct 11, 2024):

Definitely a bug, thanks for the report!

@bioball commented on GitHub (Oct 11, 2024): Definitely a bug, thanks for the report!

adam referenced this issue

2025-12-30 01:24:33 +01:00

[PR #205] [MERGED] Fix multiple output example code #450

Sign in to join this conversation.