Serialized xml is nested too deeply - TestToolkit
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- powershell
- Domain
- tooling
Research direction
Start by reproducing the reported error with the supplied PowerShell script and -includeTestToolkit, then compare it with the Import-TestToolkitToBcContainer command mentioned in the report. The issue does not identify repository files or tests, so locate the relevant TestToolkit import/container entry points before tracing the XML serialization failure. Done means the container can be created with the Test Toolkit without the nested-XML error.
Written by the indexing model from the issue text.
Description
1. Describe the bug
I am getting the "Serialized xml is nested too deeply" error message when I create a docker container using a PowerShell script. The script includes the -includeTestToolkit flag.
2. To Reproduce
Steps to reproduce the behavior:
- Execute the following script
/*********************** Script begins ************************/
install-module BcContainerHelper -force
$accept_eula = $true
$containername = 'bc29'
$licenseFile = ''
$auth = 'Windows'
$usessl = $false
$updateHosts = $true
$assignPremiumPlan = $true
$shortcuts = 'Desktop'
$bcVersion = '29.0.0.0'
$artifactUrl = Get-BcArtifactUrl -type 'Sandbox' -country 'CA' -version $bcVersion -select 'Closest' -accept_insiderEula -storageAccount bcinsider
if ($auth -eq 'Windows') {
$credential = get-credential -UserName $env:USERNAME -Message 'Using Windows Authentication. Please enter your Windows credentials.'
}
elseif ($auth -eq 'UserPassword') {
$credential = get-credential -Message 'Using Username/Password Authentication. Please enter credentials.'
}
else {
throw '$auth needs to be either Windows or UserPassword'
}
if (!$accept_eula) {
throw 'You have to accept the eula in order to create a Container.'
}
if (!($containername)) {
throw 'You have to specify a container name in order to create a container.'
}
if (!($artifactUrl)) {
throw 'No matching build was found for your version of Business Central'
}
New-BcContainer -accept_eula:$accept_eula -accept_insiderEula
-containername $containername -artifactUrl $artifactUrl
-auth $auth -Credential $credential
-usessl:$usessl -updateHosts:$updateHosts
-licenseFile $licenseFile -assignPremiumPlan:$assignPremiumPlan
-shortcuts $shortcuts `
-includeTestToolkit
if ($licenseFile) {
Setup-BcContainerTestUsers -containerName $containername -password $credential.Password
}
/*********************** Script ends ************************/
3. Expected behavior
The docker container should be created without any errors and include all the Tests extensions.
4. Actual behavior
Le XML sérialisé est imbriqué trop profondément. Line 1, position 3605. (Serialized xml is nested too deeply. Line 1, position 3605.)
NOTE: I also tried to the following command:
Import-TestToolkitToBcContainer -containerName bc29 -includeTestRunnerOnly and got the following result:
5. Versions:
- AL Language: 18
- Visual Studio Code: N/A
- Business Central: 29.0.52454.0
- List of Visual Studio Code extensions that you have installed: None
- Operating System:
- Windows
- Linux
- MacOS
- Dominant language
- PowerShell
- Stars
- 884
- Forks
- 285
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/AL
-
accepted al-tools bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 5/5 Over a week Newbie friendliness 8/100
-
accepted
Difficulty 5/5 Over a week Newbie friendliness 12/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
suggestion
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dusk-network/exu#15 ·
-
bug:new
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
callstackincubator/simlock#450 ·
Maintainers usually reply within 1 day
-
C-bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rust-lang/rust-analyzer#23501 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
githubnext/gh-aw-workshop#4455 ·
Maintainers usually reply within 1 day