Microsoft.Filesystem.File/Content - Export don't work / SET strange behaviour
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 55/100
Línea de trabajo
Start with the dsc config export command and the Microsoft.Filesystem.File/Content resource invocation shown in the logs. Trace the filecontent process through the command_resource export path, focusing on the reported JSON EOF error. Done means exporting the sample configuration produces the expected file content and metadata without an error.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest version
- Search the existing issues.
Summary
Hi as I'm testing new file content I see that when I like to export I goot issue, but when I run the same file with SET is working like export
Steps to reproduce
- I have configuration file like this when I don't have content
$schema: https://aka.ms/dsc/schemas/v3/bundled/config/document.json
resources:
- name: Test File
type: Microsoft.Filesystem.File/Content
properties:
path: C:\dsc\config\file-content\test.txt
My test file content - file is created manually in local path
Hello World
Hello World 2
- Running export - this output error
dsc -l debug config export --file .\export-dsc-file-content.yaml
- Running SET this give outpur like this
dsc -l debug config set--file .\export-dsc-file-content.yaml
executionInformation:
duration: PT2.4210989S
endDatetime: 2026-09-20T11:49:08.838760-07:00
executionType: actual
operation: set
securityContext: elevated
startDatetime: 2026-09-20T11:49:06.417661100-07:00
version: 3.4.0-preview.1
metadata:
Microsoft.DSC:
duration: PT2.4210948S
endDatetime: 2026-09-20T11:49:08.838755900-07:00
executionType: actual
operation: set
securityContext: elevated
startDatetime: 2026-09-20T11:49:06.417661100-07:00
version: 3.4.0-preview.1
results:
- executionInformation:
duration: PT0.0162712S
metadata:
Microsoft.DSC:
duration: PT0.0162712S
name: Test File
type: Microsoft.Filesystem.File/Content
result:
beforeState:
path: C:\dsc\config\file-content\test.txt
afterState:
path: C:\dsc\config\file-content\test.txt
content: "Hello World\r\nHello World 2"
sha256: 4cb711e6d67352a139c55c3ae57a7d8a84f454479bd48f031fbcc08f254a24da
sha512: 2ebbe8171d841341fa9c4d00414a385200ac9d1308fd53ec6b45322f9ca7f3ceb6fa6f1bf2ac578017a311c2730139718598c2c287d64f421a72e01f1217e6e6
_exist: true
_inDesiredState: true
changedProperties: null
messages: []
hadErrors: false
Expected behavior
dsc -l debug config export --file .\export-dsc-file-content.yaml
executionInformation:
duration: PT2.4210989S
endDatetime: 2026-09-20T11:49:08.838760-07:00
executionType: actual
operation: set
securityContext: elevated
startDatetime: 2026-09-20T11:49:06.417661100-07:00
version: 3.4.0-preview.1
metadata:
Microsoft.DSC:
duration: PT2.4210948S
endDatetime: 2026-09-20T11:49:08.838755900-07:00
executionType: actual
operation: set
securityContext: elevated
startDatetime: 2026-09-20T11:49:06.417661100-07:00
version: 3.4.0-preview.1
results:
- executionInformation:
duration: PT0.0162712S
metadata:
Microsoft.DSC:
duration: PT0.0162712S
name: Test File
type: Microsoft.Filesystem.File/Content
result:
beforeState:
path: C:\dsc\config\file-content\test.txt
afterState:
path: C:\dsc\config\file-content\test.txt
content: "Hello World\r\nHello World 2"
sha256: 4cb711e6d67352a139c55c3ae57a7d8a84f454479bd48f031fbcc08f254a24da
sha512: 2ebbe8171d841341fa9c4d00414a385200ac9d1308fd53ec6b45322f9ca7f3ceb6fa6f1bf2ac578017a311c2730139718598c2c287d64f421a72e01f1217e6e6
_exist: true
_inDesiredState: true
changedProperties: null
messages: []
hadErrors: false
Actual behavior
2026-09-20T18:47:21.723149Z DEBUG dsc_lib::configure: 1390: Invoke property expressions
2026-09-20T18:47:21.723727Z DEBUG dsc_lib::parser: 48: Parsing statement: C:\dsc\config\file-content\test.txt
2026-09-20T18:47:21.724244Z DEBUG dsc_lib::parser: 82: Parsing string literal: C:\dsc\config\file-content\test.txt
2026-09-20T18:47:21.724757Z DEBUG dsc_lib::configure: 966: resource_type Microsoft.Filesystem.File/Content
2026-09-20T18:47:21.725317Z INFO dsc_lib::configure: 129: Resource 'Microsoft.Filesystem.File/Content' does not support export filtering, the engine will filter the exported instances (experimental feature)
2026-09-20T18:47:21.725731Z DEBUG dsc_lib::dscresources::dscresource: 589: Invoking export for 'Microsoft.Filesystem.File/Content'
2026-09-20T18:47:21.733017Z ERROR dsc_lib::dscresources::command_resource: 1313: PID 8548: Invalid JSON input: EOF while parsing a value at line 1 column 0
2026-09-20T18:47:21.733965Z DEBUG dsc_lib::dscresources::command_resource: 912: Process 'filecontent' id 8548 exited with code 2
2026-09-20T18:47:21.734519Z ERROR dsc_lib::dscresources::command_resource: 970: Failed to run process 'filecontent': Command: Resource 'filecontent' [exit code 2] manifest description: Invalid input
2026-09-20T18:47:21.735565Z ERROR dsc::subcommand: 238: Command: Resource 'filecontent' [exit code 2] manifest description: Invalid input
PS C:\dsc\config\file-content> dsc config export
2026-09-20T18:47:38.800616Z ERROR Error: JSON: EOF while parsing a value at line 1 column 0
PS C:\dsc\config\file-content> dsc config export --help
Export the current configuration
Error details
2026-09-20T18:47:21.723149Z DEBUG dsc_lib::configure: 1390: Invoke property expressions
2026-09-20T18:47:21.723727Z DEBUG dsc_lib::parser: 48: Parsing statement: C:\dsc\config\file-content\test.txt
2026-09-20T18:47:21.724244Z DEBUG dsc_lib::parser: 82: Parsing string literal: C:\dsc\config\file-content\test.txt
2026-09-20T18:47:21.724757Z DEBUG dsc_lib::configure: 966: resource_type Microsoft.Filesystem.File/Content
2026-09-20T18:47:21.725317Z INFO dsc_lib::configure: 129: Resource 'Microsoft.Filesystem.File/Content' does not support export filtering, the engine will filter the exported instances (experimental feature)
2026-09-20T18:47:21.725731Z DEBUG dsc_lib::dscresources::dscresource: 589: Invoking export for 'Microsoft.Filesystem.File/Content'
2026-09-20T18:47:21.733017Z ERROR dsc_lib::dscresources::command_resource: 1313: PID 8548: Invalid JSON input: EOF while parsing a value at line 1 column 0
2026-09-20T18:47:21.733965Z DEBUG dsc_lib::dscresources::command_resource: 912: Process 'filecontent' id 8548 exited with code 2
2026-09-20T18:47:21.734519Z ERROR dsc_lib::dscresources::command_resource: 970: Failed to run process 'filecontent': Command: Resource 'filecontent' [exit code 2] manifest description: Invalid input
2026-09-20T18:47:21.735565Z ERROR dsc::subcommand: 238: Command: Resource 'filecontent' [exit code 2] manifest description: Invalid input
PS C:\dsc\config\file-content> dsc config export
2026-09-20T18:47:38.800616Z ERROR Error: JSON: EOF while parsing a value at line 1 column 0
PS C:\dsc\config\file-content> dsc config export --help
Export the current configuration
Environment data
Name Value
---- -----
PSVersion 7.6.1
PSEdition Core
GitCommitId 7.6.1
OS Microsoft Windows 10.0.26100
Platform Win32NT
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.4
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Version
dsc 3.4.0-preview.1
Visuals
No response
- Lenguaje dominante
- Rust
- Estrellas
- 536
- Forks
- 76
- Merge medio
- 1 d 20 h
- PR fusionados (30 d)
- 15
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de PowerShell/DSC
-
"apt install dsc" will install the preview release instead of stablePosiblemente ocupada @SteveL-MSFT la tomó hace 1 día. AbiertoIssue-Bug Need-Review
PowerShell/DSC#1746 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Issue-Enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
PowerShell/DSC#1737 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
PowerShell/DSC#1736 ·
Los mantenedores suelen responder en 1 día
-
`directives.version` is checked against dsc-lib's crate version (3.2.0), not the running dsc versionPosiblemente ocupada @michaeltlombardi la tomó hace 4 días. AbiertoIssue-Bug
Dificultad 3/5 Medio día Aptitud para principiantes 74/100
PowerShell/DSC#1735 · 1 comentario · 1 reacción · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Make it impossible to accidentally define a nonfunctional secret extensionPosiblemente ocupada @Gijsreyn la tomó hace 1 día. AbiertoIssue-Enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 38/100
PowerShell/DSC#1729 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de PowerShell/DSC
Issues similares
-
docs(openclaw): RTK_REWRITE_HOST relaxes every default ask, not only commands no rule matchedAbiertoarea:docs documentation good first issue priority:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
rtk-ai/rtk#4500 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
triage:accepted
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
open-telemetry/otel-arrow#4343 ·
Los mantenedores suelen responder en 2 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
mishraprafful/multihull#150 ·
Los mantenedores suelen responder en 1 día
-
`npx --package=vite-plus vp create` fails with exit 127 when npm is the chosen package managerAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
voidzero-dev/vite-plus#2970 ·
Los mantenedores suelen responder en 1 día
-
ai_p2 comp-parquet-reader-v3
Dificultad 2/5 Medio día Aptitud para principiantes 66/100
ClickHouse/ClickHouse#124986 ·
Los mantenedores suelen responder en 1 día