PromtEngineer / PromtEngineer/localGPT

[BUG] doesnt work on windows os. Fixes listed to get it working

Open
#925 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
22.2k
Forks
2.5k
PR merge metrics
No merged PRs in 30d

Description

๐Ÿ› Bug Description

Some issues on windows os that can be fixed with documentaion and code fixes

๐Ÿ”„ Steps to Reproduce

try running on windows os

โœ… Expected Behavior

working on windows

โŒ Actual Behavior

errors on windows

๐Ÿ“ธ Screenshots

If applicable, add screenshots to help explain your problem.

๐Ÿ–ฅ๏ธ Environment Information

Desktop/Server:

  • OS: [e.g. macOS 13.4, Ubuntu 20.04, Windows 11]
  • Python Version: [e.g. 3.11.5]
  • Node.js Version: [e.g. 23.10.0]
  • Ollama Version: [e.g. 0.9.5]
  • Docker Version: [e.g. 24.0.6] (if using Docker)

Browser (if web interface issue):

  • Browser: [e.g. Chrome, Safari, Firefox]
  • Version: [e.g. 118.0.0.0]

๐Ÿ“‹ System Health Check

Please run python system_health_check.py and paste the output:

[Paste system health check output here]

๐Ÿ“ Error Logs

Please include relevant error messages or logs:

[Paste error logs here]

๐Ÿ”ง Configuration

  • Deployment method: [Docker / Direct Python]
  • Models used: [e.g. qwen3:0.6b, qwen3:8b]
  • Document types: [e.g. PDF, DOCX, TXT]

๐Ÿ“Ž Additional Context

Add any other context about the problem here.

๐Ÿค” Possible Solution

1)The windows os doesnt handle all the icons in terminal and generates python char decoding errors
Fix: set PYTHONIOENCODING=utf-8
run this command in the terminal before running any of the python files in this package
Please add this to the documentation

  1. npm dev commands fails which even though npm exists in windows
    Fix: this code in the run_system.py to handle npm.cmd shims

import shutils
self.logger.info(f"๐Ÿ”„ Starting {service_name} on port {config.port}...")

    try:
        # Setup environment
        env = os.environ.copy()
        if config.env:
            env.update(config.env)
        self.logger.info(f"Command: {' '.join(config.command)}")
                    # Resolve executable on Windows (handle npm -> npm.cmd shims)
        cmd = list(config.command)
        if os.name == 'nt' and cmd:
            resolved = shutil.which(cmd[0])
            if resolved:
                cmd[0] = resolved

        # Start process
        process = subprocess.Popen(
            cmd, #config.command,
            cwd=config.cwd,
            env=env,
            stdout=subprocess.PIPE,
            stderr=subprocess.STDOUT,
            text=True,
            bufsize=1,
            universal_newlines=True
        )

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up โ€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Windows behavior and run python system_health_check.py, then inspect run_system.py and the existing documentation. Compare the reported terminal decoding errors and npm command failures with the proposed Windows handling; done means the documented setup works and the affected commands run successfully on Windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, python
Domain
backend, documentation, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.