Fission-AI/OpenSpec · error
Warning: Could not read ${profilePath}: ${err?.message ?? St
Error message
Warning: Could not read ${profilePath}: ${err?.message ?? String(err)} What it means
Error "Warning: Could not read ${profilePath}: ${err?.message ?? String(err)}" thrown in Fission-AI/OpenSpec.
Source
Thrown at src/core/completions/installers/powershell-installer.ts:280
const profilePaths = this.getAllProfilePaths();
let anyRemoved = false;
for (const profilePath of profilePaths) {
try {
// Read profile content with encoding detection
let profileContent: string;
let fileEncoding: BufferEncoding = 'utf-8';
let fileBom: Buffer = Buffer.alloc(0);
try {
const file = await this.readProfileFile(profilePath);
profileContent = file.content;
fileEncoding = file.encoding;
fileBom = file.bom;
} catch (err: any) {
if (err?.code === 'ENOENT') {
continue; // Profile doesn't exist, nothing to remove
}
console.warn(`Warning: Could not read ${profilePath}: ${err?.message ?? String(err)}`);
continue;
}
// Remove OPENSPEC:START -> OPENSPEC:END block
const startMarker = '# OPENSPEC:START';
const endMarker = '# OPENSPEC:END';
const startIndex = profileContent.indexOf(startMarker);
if (startIndex === -1) {
continue; // No OpenSpec block found
}
const endIndex = profileContent.indexOf(endMarker, startIndex);
if (endIndex === -1) {
console.warn(`Warning: Found start marker but no end marker in ${profilePath}`);
continue;
}
View on GitHub (pinned to 6926ccb18a)
When it happens
Trigger: Thrown at src/core/completions/installers/powershell-installer.ts:280 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Fission-AI/OpenSpec@6926ccb18a (2026-08-25).
Data as JSON: /api/errors/bf633997d042aa3a.
Report an issue: GitHub.