microsoft / microsoft/foundry-local

[Bug] Using the switch foundry server start --port xxxx causes foundry model list to return less models

Open
#1,065 1 comment 0 reactions 0 assignees View on GitHub
bug
Dominant language
C++
Stars
2.6k
Forks
369
Avg merge
2d 17h
Merged PRs (30d)
39

Description

### Describe the issue

When you start foundry server with the switch --port xxxx or --idle-timeout xxxx causes a bug so when you execute foundry model list NPU models are not listed and some times not even GPU Models. If you start the server without either of those switches foundry model list returns all possible models, NPU GPU CPU

### To reproduce

When you start foundry server with the switch --port xxxx or --idle-timeout xxxx causes a bug so when you execute foundry model list NPU models are not listed and some times not even GPU Models. If you start the server without either of those switches foundry model list returns all possible models, NPU GPU CPU

### Urgency

_No response_

### Platform and architecture

Windows X64

### OS Version

Windows 11 25H2

### Installation type

Released package/binary

### Foundry Local version

0.10.3

### API or surface area

CLI

### Hardware acceleration/backend

WinML EPs

### Backend/runtime version

NA

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue through the CLI with `foundry server start --port xxxx` and `--idle-timeout xxxx`, then compare `foundry model list` with a server started without those switches. Trace the server-start and model-list entry points; done means NPU, GPU, and CPU models are listed consistently in all cases.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.