ActiveDirectoryDsc: Modules fail to run port reboot  after ADDomain created a forest

Details of the scenario you tried and the problem that is occurring

Affects Windows Server 2016-2019, Windows Server 2012 R2 runs fine
Running DSC configuration that creates a single DC forest and then creates OUs and Group. Forest is created without any issues and system reboots. After reboot next task fails  with error:" Unable to find a default server with flags: 'MinimumDirectoryServiceVersion:Windows2000 | ADWS | ReturnDnsName"
When DSC runs at the next interval 15 minutes later all tasks complete successfully

Verbose logs showing the problem
[
  {"time": "2020-12-21T14:37:31.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [] Starting consistency engine."},
  {"time": "2020-12-21T14:37:31.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [] A pending configuration exists. DSC will process a set request on the pending configuration."},
  {"time": "2020-12-21T14:37:36.690-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[TimeZone]TimeZone]  "},
  {"time": "2020-12-21T14:37:36.690-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[TimeZone]TimeZone]  "},
  {"time": "2020-12-21T14:37:36.721-8:00", "type": "verbose", "message": "[test-dsc]:                            [[TimeZone]TimeZone] Testing the time zone."},
  {"time": "2020-12-21T14:37:36.846-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[TimeZone]TimeZone]  in 0.1560 seconds."},
  {"time": "2020-12-21T14:37:36.846-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[TimeZone]TimeZone]  "},
  {"time": "2020-12-21T14:37:36.846-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[TimeZone]TimeZone]  "},
  {"time": "2020-12-21T14:37:36.846-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:36.846-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:36.862-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-DNS-Server feature."},
  {"time": "2020-12-21T14:37:37.081-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:37.143-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:37.143-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:37.190-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Loading 'FormatsToProcess' from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\Feature.format.ps1xml'."},
  {"time": "2020-12-21T14:37:37.487-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psm1'."},
  {"time": "2020-12-21T14:37:37.628-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:37.628-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:37.628-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:37.628-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:37.643-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:37.643-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:37.643-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:37.643-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-DNS-Server using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:37.659-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-DNS-Server"},
  {"time": "2020-12-21T14:37:46.143-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-DNS-Server"},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-DNS-Server feature."},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features]  in 9.3600 seconds."},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource0::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the AD-Domain-Services feature."},
  {"time": "2020-12-21T14:37:46.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] Querying for feature AD-Domain-Services using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:46.221-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: AD-Domain-Services"},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: AD-Domain-Services"},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the AD-Domain-Services feature."},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features]  in 0.2340 seconds."},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource1::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-AD-AdminCenter feature."},
  {"time": "2020-12-21T14:37:46.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-AD-AdminCenter using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:46.456-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-AD-AdminCenter"},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-AD-AdminCenter"},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-AD-AdminCenter feature."},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features]  in 0.2340 seconds."},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource2::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-ADDS feature."},
  {"time": "2020-12-21T14:37:46.675-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-ADDS using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:46.690-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-ADDS"},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-ADDS"},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-ADDS feature."},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features]  in 0.2660 seconds."},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource3::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-AD-PowerShell feature."},
  {"time": "2020-12-21T14:37:46.940-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-AD-PowerShell using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:46.956-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-AD-PowerShell"},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-AD-PowerShell"},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-AD-PowerShell feature."},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features]  in 0.2340 seconds."},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource4::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.175-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-AD-Tools feature."},
  {"time": "2020-12-21T14:37:47.190-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:47.190-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-AD-Tools using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:47.206-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-AD-Tools"},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-AD-Tools"},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-AD-Tools feature."},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features]  in 0.2500 seconds."},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource5::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Begin executing Test functionality on the RSAT-Role-Tools feature."},
  {"time": "2020-12-21T14:37:47.425-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Perform operation 'Enumerate CimInstances' with following parameters, ''namespaceName' = root\\cimv2,'className' = Win32_OperatingSystem'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Operation 'Enumerate CimInstances' complete."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Loading module from path 'C:\\windows\\system32\\WindowsPowerShell\\v1.0\\Modules\\ServerManager\\ServerManager.psd1'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Get-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Install-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing cmdlet 'Uninstall-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing function 'Disable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing function 'Enable-ServerManagerStandardUserRemoting'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing alias 'Add-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Importing alias 'Remove-WindowsFeature'."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] Querying for feature RSAT-Role-Tools using Server Manager cmdlet Get-WindowsFeature."},
  {"time": "2020-12-21T14:37:47.440-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' started: RSAT-Role-Tools"},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] The operation 'Get-WindowsFeature' succeeded: RSAT-Role-Tools"},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]:                            [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features] End executing Test functionality on the RSAT-Role-Tools feature."},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features]  in 0.2350 seconds."},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[WindowsFeature]Resource6::[WindowsFeatureSet]ADDS_Features]  "},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[ADDomain]CreateForest]  "},
  {"time": "2020-12-21T14:37:47.659-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[ADDomain]CreateForest]  "},
  {"time": "2020-12-21T14:37:47.972-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] Querying for domain 'contosoad.com'. (ADD0001)"},
  {"time": "2020-12-21T14:37:48.987-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] The AD Server for domain 'contosoad.com' is currently not ready. (ADD0002)"},
  {"time": "2020-12-21T14:37:49.003-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] Attempt 1 of 15 to call Get-ADDomain failed, retrying in 30 seconds. (ADD0010)"},
  {"time": "2020-12-21T14:38:19.458-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] The AD Server for domain 'contosoad.com' is currently not ready. (ADD0002)"},
  {"time": "2020-12-21T14:38:19.458-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] Attempt 2 of 15 to call Get-ADDomain failed, retrying in 30 seconds. (ADD0010)"},
  {"time": "2020-12-21T14:38:50.303-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] Active Directory domain 'contosoad.com' found. (ADD0003)"},
  {"time": "2020-12-21T14:38:50.428-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADDomain]CreateForest] The domain 'contosoad.com' is in the desired state. (ADD0008)"},
  {"time": "2020-12-21T14:38:50.443-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[ADDomain]CreateForest]  in 62.7840 seconds."},
  {"time": "2020-12-21T14:38:50.443-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Skip   Set      ]  [[ADDomain]CreateForest]  "},
  {"time": "2020-12-21T14:38:50.443-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Resource ]  [[ADDomain]CreateForest]  "},
  {"time": "2020-12-21T14:38:50.443-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[ADOrganizationalUnit]UserAccuntsOU]  "},
  {"time": "2020-12-21T14:38:50.443-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[ADOrganizationalUnit]UserAccuntsOU]  "},
  {"time": "2020-12-21T14:38:50.459-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADOrganizationalUnit]UserAccuntsOU] Retrieving OU 'User Accounts' from path 'dc=contosoad,dc=com'. (ADOU0001)"},
  {"time": "2020-12-21T14:38:51.397-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[ADOrganizationalUnit]UserAccuntsOU]  in 0.9530 seconds."},
  {"time": "2020-12-21T14:38:51.397-8:00", "type": "error", "message": "PowerShell DSC resource MSFT_ADOrganizationalUnit  failed to execute Test-TargetResource functionality with error message: System.InvalidOperationException: Error getting OU 'User Accounts'. (ADOU0014) ---> Microsoft.ActiveDirectory.Management.ADServerDownException: Unable to find a default server with Active Directory Web Services running. ---> Microsoft.ActiveDirectory.Management.ADException: Unable to find a default server with flags: 'MinimumDirectoryServiceVersion:Windows2000 | ADWS | ReturnDnsName'.\r\n   --- End of inner exception stack trace ---\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.DiscoverServerName(Boolean forceDiscovery)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.CreateEndpointAddress(String configName)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.InitializeChannel[TChannel](TChannel& channel, ChannelFactory`1& chFactory, String endpointName, CommunicationException& commException)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.SearchAnObject(ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.Search(ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.ADWebServiceStoreAccess.Microsoft.ActiveDirectory.Management.IADSyncOperations.Search(ADSessionHandle handle, ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.ADObjectSearcher.GetRootDSE()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetRootDSE()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetConnectedStore()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetCmdletSessionInfo()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADGetCmdletBase`3.ADGetCmdletBaseBeginCSRoutine()\r\n   at Microsoft.ActiveDirectory.Management.CmdletSubroutinePipeline.Invoke()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.BeginProcessing()\r\n   --- End of inner exception stack trace --- "},
  {"time": "2020-12-21T14:38:51.397-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Resource ]  [[ADOrganizationalUnit]GroupsOU]  "},
  {"time": "2020-12-21T14:38:51.397-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ Start  Test     ]  [[ADOrganizationalUnit]GroupsOU]  "},
  {"time": "2020-12-21T14:38:51.412-8:00", "type": "verbose", "message": "[test-dsc]:                            [[ADOrganizationalUnit]GroupsOU] Retrieving OU 'Groups' from path 'dc=contosoad,dc=com'. (ADOU0001)"},
  {"time": "2020-12-21T14:38:51.428-8:00", "type": "verbose", "message": "[test-dsc]: LCM:  [ End    Test     ]  [[ADOrganizationalUnit]GroupsOU]  in 0.0310 seconds."},
  {"time": "2020-12-21T14:38:51.428-8:00", "type": "error", "message": "PowerShell DSC resource MSFT_ADOrganizationalUnit  failed to execute Test-TargetResource functionality with error message: System.InvalidOperationException: Error getting OU 'Groups'. (ADOU0014) ---> Microsoft.ActiveDirectory.Management.ADServerDownException: Unable to find a default server with Active Directory Web Services running. ---> Microsoft.ActiveDirectory.Management.ADException: Unable to find a default server with flags: 'MinimumDirectoryServiceVersion:Windows2000 | ADWS | ReturnDnsName'.\r\n   --- End of inner exception stack trace ---\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.DiscoverServerName(Boolean forceDiscovery)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.CreateEndpointAddress(String configName)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.InitializeChannel[TChannel](TChannel& channel, ChannelFactory`1& chFactory, String endpointName, CommunicationException& commException)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.SearchAnObject(ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.AdwsConnection.Search(ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.ADWebServiceStoreAccess.Microsoft.ActiveDirectory.Management.IADSyncOperations.Search(ADSessionHandle handle, ADSearchRequest request)\r\n   at Microsoft.ActiveDirectory.Management.ADObjectSearcher.GetRootDSE()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetRootDSE()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetConnectedStore()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.GetCmdletSessionInfo()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADGetCmdletBase`3.ADGetCmdletBaseBeginCSRoutine()\r\n   at Microsoft.ActiveDirectory.Management.CmdletSubroutinePipeline.Invoke()\r\n   at Microsoft.ActiveDirectory.Management.Commands.ADCmdletBase`1.BeginProcessing()\r\n   --- End of inner exception stack trace --- "},
  {"time": "2020-12-21T14:38:51.428-8:00", "type": "verbose", "message": "[test-dsc]:                            [] Consistency check completed."}
]

Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
Configuration DcConfig
{
	[CmdletBinding()]

	Param
	(
		[Parameter(Mandatory = $true)]
		[ValidateNotNullorEmpty()]
		[PSCredential]$DomainAdminCredentials,
		[string]$DomainName,
		[string]$NetBiosDomainname,
		[string]$ForwarderIPaddress,
		[string]$ForwarderDomain,
		[string]$TimeZone

	)

	Import-DscResource -ModuleName PSDscResources
	Import-DscResource -ModuleName ComputerManagementDsc
	Import-DscResource -ModuleName ActiveDirectoryDsc

	$groupList = @(
		"Logistics",
		"Information Technology",
		"IT Support",
		"Strategic Information Systems",
		"Data Entry",
		"Research and Development",
		"Strategic Sourcing",
		"Purchasing",
		"Operations",
		"Public Relations",
		"Corporate Communications",
		"Advertising Market Research",
		"Strategic Marketing",
		"Customer Service",
		"Telesales",
		"Account Management",
		"Marketing",
		"Sales",
		"Payroll",
		"Recruitment",
		"Training",
		"Human Resource",
		"Accounting",
		"Finance"
	)

	Node 'localhost'
	{
		LocalConfigurationManager {
			ConfigurationMode    = 'ApplyAndAutoCorrect'
			RebootNodeIfNeeded   = $true
			ActionAfterReboot    = 'ContinueConfiguration'
			AllowModuleOverwrite = $true
		}
		TimeZone TimeZoneExample {
			isSingleInstance = 'Yes'
			TimeZone         = $TimeZone

		}
		WindowsFeatureSet ADDS_Features
		{
			Name = @('RSAT-DNS-Server','AD-Domain-Services','RSAT-AD-AdminCenter','RSAT-ADDS','RSAT-AD-PowerShell','RSAT-AD-Tools','RSAT-Role-Tools')
			Ensure = 'Present'
		}
		ADDomain CreateForest {
			DomainName                    = $DomainName
			Credential                    = $DomainAdminCredentials
			SafemodeAdministratorPassword = $DomainAdminCredentials
			DomainNetbiosName             = $NetBiosDomainname
			DependsOn                     = '[WindowsFeatureSet]ADDS_Features'
		}

		#create user OUs
		ADOrganizationalUnit UserAccuntsOU
		{
			Name="User Accounts"
			Path="dc=$($NetBiosDomainname),dc=com"
			Ensure = "Present"
			DependsOn =   '[ADDomain]CreateForest'
		}
		ADOrganizationalUnit EnabledUsersOU
		{
			Name="Enabled Users"
			Path="OU=User Accounts,dc=$($NetBiosDomainname),dc=com"
			Ensure = "Present"
			DependsOn =   '[ADOrganizationalUnit]UserAccuntsOU'
		}

		#create Group OUs
		ADOrganizationalUnit GroupsOU
		{
			Name="Groups"
			Path="dc=$($NetBiosDomainname),dc=com"
			Ensure = "Present"
			DependsOn =   '[ADDomain]CreateForest'
		}
		ADOrganizationalUnit SecurityGroupsOU
		{
			Name="Security Groups"
			Path="OU=Groups,dc=$($NetBiosDomainname),dc=com"
			Ensure = "Present"
			DependsOn =   '[ADOrganizationalUnit]GroupsOU'
		}

		foreach ($group in $groupList) {
			ADGroup $group
			{
				GroupName = $group
				DisplayName = $group
				GroupScope = "Global"
				Category = "Security"
				Path = "OU=Security Groups,OU=Groups,dc=$($NetBiosDomainname),dc=com"
				Ensure = "Present"
				Dependson  = '[ADOrganizationalUnit]SecurityGroupsOU'
			}
		}
		Script SetForwarders {
			TestScript =
			{
			 $result = $null
			 $result = (Get-DnsServerZone -Name $using:ForwarderDomain -ErrorAction SilentlyContinue)
				if ($result -eq $null) {
					return $false
				}
				else {
					return $true
				}

			}
			GetScript  =
			{
				$TestResult = Test-ADDSDomainControllerInstallation -DomainName $using:domainname -SafeModeAdministratorPassword $using:DomainAdminCredentials.Password -Credential $using:DomainAdminCredentials
				if ($testresult.status -notcontains "Error") {
					$results = @{"domain" = $True }
				}
				else {
					$results = @{"domain" = $false }
				}
				return $results
			}
			SetScript  =
			{
				Add-DnsServerConditionalForwarderZone -MasterServers $using:ForwarderIPaddress -Name $using:ForwarderDomain

			}
			Dependson  = '[ADDomain]CreateForest'
		}
		WaitForADDomain DscForestWait {
			DomainName              = $ForwarderDomain
			DependsOn               = '[Script]SetForwarders'
			WaitTimeout             = 3600
			WaitForValidCredentials = $true
			Credential              = $DomainAdminCredentials
			RestartCount            = 5

		}
		ADDomainTrust SetTrust {
			Ensure               = "Present"
			SourceDomainName     = $DomainName
			TargetDomainName     = $ForwarderDomain
			TargetCredential     = $DomainAdminCredentials
			TrustType            = "Forest"
			TrustDirection       = "Outbound"
			Dependson            = '[WaitForADDomain]DscForestWait'
			AllowTrustRecreation = $true
		}

	}
}

The operating system the target node is running
Windows Server 2016
Windows Server 2019
Both Azure Marketplace OS images
Version and build of PowerShell the target node is running

Version of the DSC module that was used
6.0.1

You need to move the WaitForADDomain resource to just after the ADDomain resource. you are trying to create OUs before the Domain Controller is ready.

...and the resources after should depend on WaitForADDomain, not '[ADDomain]CreateForest'. 🤔

The WaitForDomain function in the configuration is for trust creation and confirms existence of second domain.  You seem to be suggesting I should be running two "WaitForDomain"  functions one for local ( to the configuration) domain and one for the remote. However, this very same,  configuration works 100% each time and every time on Windows Server 2012 R2. (I'm attaching logs from successful run) and worked on as far back as at a least four years ago in 2016
This suggest  that the flow is not in the logic of the configuration but in the way module does not account for differences between Windows Server 2012 r2  and Windows Server 2016-2019.
If indeed the only way to get this to work is to have two WaitForDomain functions, I think, documentation should reflects this.


remove PENDING_CLOSE flag

We have come across a problem when try to use this module. We found that the circuit breaker will be kept open if it's going to the "halfOpen" state the second time. There will be no way to close the circuit breaker afterwards.
After a little of debugging, it looks like the problem is caused by the PENDING_CLOSE flag. I can't really tell why we need the flag, and removing it fix the problem.
The case is being shown in the test.
@lance can you please review this and see if I am right?
Thanks.

@wei-lee thanks for making the contribution. But we actually do need PENDING_CLOSE.
It's a real edge case, but the reason we have PENDING_CLOSE is because the circuit should only ever attempt to execute once when in the HALF_OPEN state. In a scenario where lots and lots of requests are occurring in parallel, many could execute while the circuit is HALF_OPEN. By checking the PENDING_CLOSE state, we ensure this doesn't happen.
You did discover a bug, however. So thank you! The PENDING_CLOSE flag was never being reset. I've fixed that, and used your test case in my latest commit.


Stack Overflow during TextFormat generation

oss-fuzz found a test case that is properly parsed, but fails to re-serialized it back out to TextFormat, but only in the debug version of the fuzz test.  The input is:
79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{49{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{49{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}49{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}49{79{79{79{79{79{79{79{79{79{79{79{79{79{79{79{}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}}#49{79{79{7}{7

Which basically boils down to just deep nesting of the recursive message, close to the recursion limit.
This sorta appears to be like #1034.
Since the TextFormat output is used for the debugDescription not being able to dump a deep message that were were able to parse will likely be a little confusing to developers that run into this.

I tried a manual edit to the generated fuzz_testing.pb.swift version of traverse to wrap each if let ... block with a try { if let ... }() closure, like we did for the other issue.  That does seem to reduce the stack usage in debug build so the a rerun of the data on FuzzTextFormat passes.

Fixed via https://github.com/apple/swift-protobuf/pull/1183


Compatibility with Jupyter Lab

Is there any chance of updating this to make it work with Jupyter Labs? It's a bit tedious to constantly swap between the Lab and Notebook interfaces to see outputs.

Thanks, I think this is a duplicate of #36

On 23 Oct 2018, at 15:28, Zach Edwards<EMAIL_ADDRESS>wrote:
Is there any chance of updating this to make it work with Jupyter Labs? It's a bit tedious to constantly swap between the Lab and Notebook interfaces to see outputs.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Oh yeah! Apologies I did take a look before I posted but must have missed it.
Will close this issue now :)


Complete bulk memory table related features

pretty much wip

ok now intepreter passes https://github.com/WebAssembly/spec/blob/9b4d86fbcd3309c3365c8430a4ac5ef2126c43a8/test/core/bulk.wast on my local machine.. other spectests are conflated with ref type proposal (notable multi tables) so I will defer the spec test compatibility test to the ref type proposal impl later.
will do the JIT tomorrow

ok resolved all comments! merging!


Fix horizontal overflow / truncated text issues

This PR addresses horizontal overflow / truncated text at region boundaries due to the original content width being passed down to the elements within each region.
The fix is quite small: adding two new properties to computationUnsafeProperties, block-size and inline-size. @FremyCompany worth noting I did have to add inline-size as well (you suggested block-size as the fix in #43 ).

Thank you for testing the fix!


[ACS] Release notes are not updated for Android v1.0.9 and iOS v3.0.1 releases

Release notes are available on sdk docs.
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-campaign-standard/adobe-campaign-standard-release-notes#may-27-2022
https://aep-sdks.gitbook.io/docs/using-mobile-extensions/adobe-campaign-standard/adobe-campaign-standard-release-notes#february-9-2022

This has already been done!


[Feature] Render objects in a certain layer without outlines?

The outlinesLayerMask doesn't work for this purpose since the edge detection algorithm picks up the edges of the black part (objects that are masked from the normal pass) in the normal texture.
Is there a way to do this?

I think I found the solution, just set background color of normal texture settings to a transparent color


adding support for -from/-to to http adapter

fixes #194
preliminary version of how to do get this done and also expose the
functionality in a way that we can apply to other adapters with ease.

@demmer @davidvgalbraith what do you think of this approach ? I can then apply it to stdio adapter as well so we get -from/-to support in there. I was also thinking we're starting to have many of these helper functions that parseTime, toNative, filterPoints that do multiple passes on the same array of points and could probably benefit from having a nice way of only doing a single passing while applying N functions which would modify/drop the point. The exact way of doing this can be discussed but I think we'd benefit quite drastically in terms of performance from not doing the multiple passes.

bump!

If you do X work in one pass and Y work in another pass, or if you do X + Y work in a single pass, you've still done the same amount of work. So I don't think there'd be a noticeable performance difference from consolidating like that. +1 on this, though.

lgtm


Long running thread

How would you incorporate a long-running thread that pushes events to the client?
I assume the thread would call socket.send_and_broadcast_channel(message), but what would be the best way to launch that thread so it would be ran by runserver_socketio?
I'm trying to create a simple monitoring application that reads server metrics and pushes these metrics to the client when they change. The chat example is great, but it's events are still triggered by the client, so it's unclear how a pure server-push example would work.

WebSockets probably aren't being used, see #19

Presumably answered yourself in #99


Commiting a change to en.yml throws duplicated mapping key error

Most appropriate sections of the p5.js website?
Other (specify if possible)
What is your operating system?
Windows
Web browser and version
No response
Actual Behavior
When committing a change (seemingly any change) to src/data/en.yml, grunt i18n throws:
Fatal error: duplicated mapping key at line 586, column 5:
       line 883: '  p5.utils'

It looks like that's referring to i18n-tracking.yml, and I do see two different entries for line 883:
'  p5.utils' and '    With these skills you will be able to create some basic shaders, but shader programming can go incredibly deep,'
I'm not familiar with i18n, so any guidance on what's going on here would be much appreciated!
Expected Behavior
grunt i18n runs without errors
Steps to reproduce
@katlich112358 ran into this issue when editing en.yml line 313
support-17-alt: ''

to
support-17-alt: 'text'

But I tried removing that change and making other changes and ran into the same issue.
Would you like to work on the issue?
Yes

This is referring to i18n-tracking.yml having duplicate entries with the key line 883 which is not valid, since the i18n step is only run when en.yml is modified, this was not caught before.
The i18n tracking is not really being used nor quite fit for purpose, I'll remove it and other experiments I was working on for now while exploring some better solutions for these.


DOM Driver getter should accept custom element name as selector

From @staltz on June 6, 2015 7:0
@staltz

I'm trying to foresee why would people need selector instead of className but can't come up with a valid reason right now.

@ivan-kleshnin

I'd like to be able to query by component names. They should be more stable than classes. And a bit cleaner about user intentions. Such names should be globally unique (like in web components) so I think it's ok to query by them.

Copied from original issue: cyclejs/cycle-core#129

Not anymore relevant.


Reduce SKR Policy Size

Following list shows the endpoints that are being removed or modified:
Removed:

East Canada
UK South
Canada Central
UK West
North Central US
Japan West

Modified:

Central India
UAE North
Germany West Central

Looks good


cni: use right network NS while removing link

WithNetNSPath(removeIfFromNSIfExists) == removeIfFromNSIfExists(hostNS,
..). removeIfFromNSIfExists runs in expected network namespace but
it gets hostNS as a argument
Signed-off-by: Nirmoy Das<EMAIL_ADDRESS>https://github.com/cilium/cilium/blob/c1f2f3fbe871b3a8b2dbd2b85ff9d1cd4389cfa4/vendor/github.com/containernetworking/cni/pkg/ns/ns.go#L145

This change is

@aanm removeIfFromNSIfExists should get netNs of the endpoint.
in https://github.com/cilium/cilium/blob/c1f2f3fbe871b3a8b2dbd2b85ff9d1cd4389cfa4/plugins/cilium-cni/cilium-cni.go#L481-L483 removeIfFromNSIfExists get hostNS as 1st argument

@nirmoy can you add to your commit message

Fixes: dd19c96e33ef ("Ignore non-existing link error in cni del")

@aanm updated

test-me-please

@aanm @tgraf Does this need backporting?

@joestringer no, it is unreleased code, I've also removed the release-note/bug.


Improve short codes live tests

Reorganize and improve the short codes live tests to be more robust and thoroughly check each endpoint.  Improve logging/error checking/validation, etc

@ericasp16
Unrelated to this PR, but can you please add an entry to the codeowners file for this packege? See https://github.com/Azure/azure-sdk-for-js/blob/main/.github/CODEOWNERS#L36-L42. This will ensure that your PRs get labelled properly and get the right reviewers get looped in automatically

Another unrelated note to this PR, but related to this package is at #18688
Please take a look at that separately as well.


Add movies / web series to liked items array

Add movies / web series to liked items array
keypoints

Add liked items to this array, they need to be stored in the firestore database.
Also implement a way to get the array from database and display.

I would like to work on this issue


Fixes : trad, variant cache bug, user config preservation on variant generation (xpansion)

Hello @pl-buiquang, do you remember why you coded this: Preserve unmanaged user config on variant generation ?
It is preventing me to handle properly xpansion variants because it overwrites the parent configuration in the variant snapshot so i would like to remove this part of the code.
The problem is that i fail to understand why you coded it and so do other team member (also i do not find any doc on the subject) and i do not want to remove this part of the code carelessly.


Dataset Annotation file format

Dear authors,
Congratulations on this awesome work! This is a superb and solid work.
Thanks for releasing dropbox versions of the dataset. I have some questions regarding dataset format and annotations:

Where can I find the object label or type for each sequence? Is it the first part in the label of the sequence? For example, if a video is labeled as S100014_0003_0002, is the object used S100014? Also, what does 0003 and 0002 stand for? Are they intent labels or camera views?
Where can I find the intent label? Are the intent labeled per-frame or for certain segments?
For the OakInk-Image, I see hand annotations under anno/hand_v and anno/hand_j. What coordinate system are they in? World coordinates or Camera coordinates?
When there are two hands in a video (for example, when handing over and receiving objects) do you annotate hand poses for both the hands or just a single hand?
How are hand pose files labelled? I see two pickle files for the same frame. For example, I see anno/hand_v/A01001__0003__0002__2021-09-26-20-02-08__0__6__1.pkl and anno/hand_v/A01001__0003__0002__2021-09-26-20-02-08__0__6__2.pkl. What are the differences?
Where can I find the camera extrinsics for each video?

Can you please clarify the above questions?
Also, are you planning to release a README file explaining the annotation and file format?

Thanks for your interest in our dataset,
We will update the README file to give more detailed explanation on OakInk dataset.

The object models used in OakInk-Image are at $OAKINK_DIR/image/obj/
The first part of the sequence label represent object_id.
For example, the sequence labeled as S100014_xxxx_xxxx means that the object used in this sequence is S100014.obj. Now I will explain the sequence label and its meaning:
Sequence label —>  meanings:

sequence “A_B_C”:   A means object_id, B means intent_id, and C means subject_id;
sequence “A_B_C_D”:  A means object_id, B means intent_id, and C & D means subject_id (C is the giver, D is the receiver)

The intent  is labeled per sequence. We asked a subject to perform intent of  “use” and  record his/her hand during the whole course of interaction.  The intent_name to intent_id mappings are:
ALL_INTENT = {
    "use": "0001",
    "hold": "0002",
    "liftup": "0003",
    "handover": "0004", handover = give + receive
}

you can use our toolkit: oikit/oi_image/oi_image.py::get_joints_3d and  get_verts_3d
to access joints/verts in camera coordinates system.

We annotate both hands, this also explains the questions 5.

If a sequence appears to have two annotated hands (giver and receiver), it will have two pickle files. Each file stores one subject’s hand annotation.

For camera extrinsics, check: oikit/oi_image/oi_image.py::get_mano_pose. It describe how to use the cam_extr

The oikit provide basic usage of our dataset. You can find the code for loading data and annotations in it.
Best,
Lixin

Thank you for clarifying this.
I have a follow up question regarding OakInk-Shape annotation format. For example, I am looking at the folded: oakink_shape_v2/bottle/A16012/0cc013118e/S16105.

In this path, I think A16012 correspond to the object. What about 0cc013118e and S16105? Do they have any specific meaning?
Also, the file oakink_shape_v2/bottle/A16012/0cc013118e/S16105/hand_param.pkl has fields pose, shape, tsl. The pose has shape 16x4. Can you please explain what does this corresponding to? If I am not wrong, hand pose is in 3 dimensions right?

Thank you.

Hi,

the 0cc013118e is a hash code that we use to identify a certain object instance. it has no direct meaning.
the pose are represented as quaternion, thus is 16 x 4 in shape. You can easily transform them to the axis-angle by using our oikit here

Hope these helps.
Lixin

Thank you Lixin!

Is my understanding of OakInk-Shape data format correct?
The root directory ./oakink_shape_v2 contains objects of different categories such as apple, banana, binoculars, bottle, etc. For each of these object categories, there can be various instances of that object category. For example, ./oakink_shape_v2/bottle/ has various instance such as A16012, A16013, A16026, etc. And for each type of instance, for example, ./oakink_shape_v2/bottle/A16012/ there are different possible hand grasp annotations. These are typically stored in some_hexadecimal_folder/hand_param.pkl. Is this right?
If yes, I am a little confused by the directory structure. Sometimes there is a single hexadecimal folder such as 0eec013c90 containing hand_param.pkl . For example, ./oakink_shape_v2/apple/C90001/0eec013c90/ has only one hand_param.pkl . But in some cases, such as ./oakink_shape_v2/bottle/A16012/0cc013118e/ has multiple subdirectories such as S16101, S16102, etc.
Can you please correct me if I am wrong or provide some clarifications here?
Thanks!

Hi, thank you for your interest in our work.
Yes, we store the hand grasp parameters in hand_param.pkl.
As we introduced in our paper, we use Tink to transfer the grasp knowledge from a real-world object to a virtual counterpart object of the same category. Take bottle/A16012/0cc013118e/hand_param.pkl as an example, the parameter here is a grasp of bottle_A16012, while bottle/A16012/0cc013118e/s16101/hand_param.pkl stores the grasp parameter of bottle_s16101 which is transferred from the former grasp.
In short, category/real_object_id/hexadecimal/hand_param.pkl is the original grasp of the real object, while category/real_object_id/hexadecimal/virtual_object_id/hand_param.pkl is the transferred grasp of the virtual counterpart object from the original grasp with Tink.
In some cases, since the grasp might not be suitable for transferring or the category does not contain enough object CAD models, we only provide the grasps of real-world objects, like apple/C90001/0eec013c90.
Also, as we have a perceptual evaluation, some hand poses have been filtered since they do not satisfy visual plausibility.

Awesome, thanks!
One followup question. For real object case ./oakink_shape_v2/binoculars/C42001/, there are multiple hexadecimal folders. Does this corresponding to different type of hand grasps for the same object C420001 ?

Another follow up question regarding image data (sorry for lot of questions)!
For sequences where the intent is handover, there are two actions give and receive, which means that there are two hands. Do you provide annotations for both the hands. For example, I am looking at annotations in ./image/anno/hand_j/ . There are two types: Y35037_0004_0007_0002__2021-10-09-14-23-47__0__107__0.pkl and Y35037_0004_0007_0002__2021-10-09-14-23-47__1__107__0.pkl. I assume that 0 before 107  always corresponds to the giver, where 1 always correspond to the receiver. Is this right?

Another follow up question regarding image data (sorry for lot of questions)!
For sequences where the intent is handover, there are two actions give and receive, which means that there are two hands. Do you provide annotations for both the hands. For example, I am looking at annotations in ./image/anno/hand_j/ . There are two types: Y35037_0004_0007_0002__2021-10-09-14-23-47__0__107__0.pkl and Y35037_0004_0007_0002__2021-10-09-14-23-47__1__107__0.pkl. I assume that 0 before 107 always corresponds to the giver, where 1 always correspond to the receiver. Is this right?

Yes, that is correct.

Dear authors,
I am trying to visualize some data based on different mode of splits or even different data splits using this.
But it looks like these splits are not updated in the code yet: OakInk-Image loader.
Can you please update this?
Thanks

Of course, we plan to update version_3 of the Oakink dataset around July 25th.
You only need to replace the current anno.zip file.
version_3 includes:

subject and object split file of OakInk-Image
a refined version of annotation, in which we fix some artifacts on the handover sequences

Dear authors,
I am trying to visualize some data based on different mode of splits or even different data splits using this.
But it looks like these splits are not updated in the code yet: OakInk-Image loader.
Can you please update this? That is, can you please provide different data splits based on subjects/ objects, and also train/ val/ test splits?
Thanks


Katalyst-colocation-orm can be installed on enhanced-k8s cluster but katalyst-colocation cannot be installed

What happened?
I followed Colocate your application using Katalyst to install Katalyst.
It mentioned that if you use Kubewharf enhanced kubernetes, install katalyst-colocation
And if you use vanilla kubernetes, install katalyst-colocation-orm
My node follows Install Kubewharf enhanced-k8s to install enhanced k8s, but only katalyst-colocation-orm can be installed instead of katalyst-colocation
If I install katalyst-colocation, it will report the following error in katalyst-colocation-agent
I0610 13:10:27.641756       1 state_checkpoint.go:121] "[cpu_plugin] State checkpoint: restored state from checkpoint"
I0610 13:10:27.641777       1 util.go:68] [katalyst-core/pkg/agent/qrm-plugins/cpu/util.GetCoresReservedForSystem] get reservedQuantityInt: 0 from ReservedCPUCores configuration
I0610 13:10:27.641787       1 util.go:77] [katalyst-core/pkg/agent/qrm-plugins/cpu/util.GetCoresReservedForSystem] take reservedCPUs:  by reservedCPUsNum: 0
I0610 13:10:27.641832       1 policy.go:950] [katalyst-core/pkg/agent/qrm-plugins/cpu/dynamicpolicy.(*DynamicPolicy).cleanPools] there is no pool to delete
I0610 13:10:27.641842       1 policy.go:964] [katalyst-core/pkg/agent/qrm-plugins/cpu/dynamicpolicy.(*DynamicPolicy).initReservePool] initReservePool reserve:
I0610 13:10:27.641859       1 state_mem.go:109] "[cpu_plugin] updated cpu plugin pod entries" podUID="reserve" containerName="" allocationInfo="{\"pod_uid\":\"reserve\",\"owner_pool_name\":\"reserve\",\"allocation_result\":\"\",\"original_allocation_result\":\"\",\"topology_aware_assignments\":{},\"original_topology_aware_assignments\":{},\"init_timestamp\":\"\",\"labels\":null,\"annotations\":null,\"qosLevel\":\"\"}"
I0610 13:10:27.644274       1 policy.go:1039] [katalyst-core/pkg/agent/qrm-plugins/cpu/dynamicpolicy.(*DynamicPolicy).initReclaimPool] exist initial reclaim: 0-9
I0610 13:10:27.644300       1 agent.go:102] needToRun "qrm_cpu_plugin"
I0610 13:10:27.644308       1 agent.go:91] initializing "qrm_io_plugin"
I0610 13:10:27.644320       1 agent.go:102] needToRun "qrm_io_plugin"
I0610 13:10:27.644325       1 agent.go:91] initializing "qrm_network_plugin"
W0610 13:10:27.644335       1 util.go:122] [katalyst-core/pkg/agent/qrm-plugins/network/staticpolicy.filterNICsByAvailability] nic: eno1 doesn't have IP address
I0610 13:10:27.644344       1 util.go:302] [katalyst-core/pkg/agent/qrm-plugins/network/staticpolicy.getReservedBandwidth] reservedBanwidth: 0, nicCount: 1, policy: first,
I0610 13:10:27.644361       1 state_net.go:47] "[network_plugin: katalyst-core/pkg/agent/qrm-plugins/network/state.NewNetworkPluginState] initializing new network plugin in-memory state store"
I0610 13:10:27.644372       1 util.go:37] [GenerateMachineState: katalyst-core/pkg/agent/qrm-plugins/network/state.GenerateMachineState] NIC wlp2s0's speed: -1, capacity: [0/0], reservation: 0
I0610 13:10:27.644511       1 util.go:37] [GenerateMachineState: katalyst-core/pkg/agent/qrm-plugins/network/state.GenerateMachineState] NIC wlp2s0's speed: -1, capacity: [0/0], reservation: 0
I0610 13:10:27.644531       1 state_net.go:121] "[network_plugin: katalyst-core/pkg/agent/qrm-plugins/network/state.(*networkPluginState).SetMachineState] updated network plugin machine state" NICMap="{\"wlp2s0\":{\"egress_state\":{\"Capacity\":0,\"SysReservation\":0,\"Reservation\":0,\"Allocatable\":0,\"Allocated\":0,\"Free\":0},\"ingress_state\":{\"Capacity\":0,\"SysReservation\":0,\"Reservation\":0,\"Allocatable\":0,\"Allocated\":0,\"Free\":0},\"pod_entries\":{}}}"
I0610 13:10:27.644543       1 state_net.go:145] "[network_plugin: katalyst-core/pkg/agent/qrm-plugins/network/state.(*networkPluginState).SetPodEntries] updated network plugin pod resource entries" podEntries="{}"
I0610 13:10:27.644555       1 state_checkpoint.go:136] "[network_plugin: katalyst-core/pkg/agent/qrm-plugins/network/state.(*stateCheckpoint).restoreState] state checkpoint: restored state from checkpoint"
I0610 13:10:27.644572       1 policy.go:177] [katalyst-core/pkg/agent/qrm-plugins/network/staticpolicy.(*StaticPolicy).ApplyConfig] apply configs, qosLevelToNetClassMap: map[dedicated_cores:0 reclaimed_cores:0 shared_cores:0 system_cores:0], podLevelNetClassAnnoKey: katalyst.kubewharf.io/net_class_id, podLevelNetAttributesAnnoKeys: []
I0610 13:10:27.644581       1 agent.go:102] needToRun "qrm_network_plugin"
I0610 13:10:27.644588       1 agent.go:91] initializing "periodical-handler-manager"
I0610 13:10:27.644593       1 agent.go:102] needToRun "periodical-handler-manager"
I0610 13:10:27.644600       1 agent.go:91] initializing "katalyst-agent-orm"
I0610 13:10:27.644631       1 manager.go:86] "Creating topology manager with policy per scope" topologyPolicyName=""
E0610 13:10:27.644640       1 manager.go:129] unknown policy: ""
E0610 13:10:27.644647       1 agent.go:94] Error initializing "katalyst-agent-orm"
I0610 13:10:27.644662       1 file.go:257] [GetUniqueLock] release lock successfully
I0610 13:10:28.396105       1 file.go:90] fsNotify watcher notify "/var/lib/kubelet/resource-plugins/kubelet_qrm_checkpoint": CREATE
I0610 13:10:28.396155       1 topology_adapter.go:281] qrm state file changed, notify to update topology status
I0610 13:10:28.396166       1 kubeletplugin.go:177] send topology change notification to plugin kubelet-reporter-plugin
run command error: failed to init ORM: unknown policy: ""

Only katalyst-agent not working
root@debian-node-1:~# kubectl get pods -n katalyst-system
NAME                                                       READY   STATUS             RESTARTS      AGE
katalyst-colocation-katalyst-agent-f5glx                   0/1     CrashLoopBackOff   4 (36s ago)   2m32s
katalyst-colocation-katalyst-agent-jzgft                   0/1     CrashLoopBackOff   4 (52s ago)   2m32s
katalyst-colocation-katalyst-controller-59b5c89cd6-jcn9m   1/1     Running            0             2m32s
katalyst-colocation-katalyst-controller-59b5c89cd6-vpjvq   1/1     Running            0             2m32s
katalyst-colocation-katalyst-metric-85c47ff4bf-nl9sf       1/1     Running            0             2m32s
katalyst-colocation-katalyst-scheduler-77cdd9d66f-8mszz    1/1     Running            0             2m32s
katalyst-colocation-katalyst-scheduler-77cdd9d66f-c27qc    1/1     Running            0             2m32s
katalyst-colocation-katalyst-webhook-5f6ccc7cb-ngz2x       1/1     Running            0             2m32s
katalyst-colocation-katalyst-webhook-5f6ccc7cb-vrnzs       1/1     Running            0             2m32s

But install katalyst-colocation-orm in Kubewharf enhanced kubernetes work fine（pod status of agent is Running）
What did you expect to happen?
install katalyst-colocation in KubeWharf-enhanced-kubernetes work fine
How can we reproduce it (as minimally and precisely as possible)?
Install katalyst-colocation using helm after installing KubeWharf-enhanced-kubernetes
helm install katalyst-colocation -n katalyst-system --create-namespace kubewharf/katalyst-colocation
Software version
No response

I think we have some issue with the katalyst-colocation helm chart here which enables orm by default, will have to fix it.
BTW, installing kubewharf enhanced kubernetes is error-prone and the installation guide is not universal enough to cover every scenario. so if possible I would recommend trying katalyst-colocation-orm on a vanilla kubernetes.


Fix ossa borrow completion

end_borrow was not considered as a lifetime ending use, leading to insertion of redundant end_borrows at boundaries.

@swift-ci smoke test

@swift-ci smoke test


Add fzf-tmux script

... and clean up the documentation

Maybe it's better to use tmux terminology and talk about tmux panes instead of splits?

@Tranquility Good point. I'm too used to Vim terminology. I'll update the doc.


Language interpolation fails scripts loading

When loading a page with the lang="en-CA" set, CDTS trys to load scripts that don't exist.
I had set the default language attribute to en-Ca on my page in the html element like:
<html lang="{{ site.lang | default: 'en-Ca' }}" xmlns="http://www.w3.org/1999/xhtml" class="no-js" dir="ltr">

Which ended up returning this issue:

SEC7112: Script from https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_32/js/i18n/en-Ca.min.js was blocked due to mime type mismatch
2 HTTP404: NOT FOUND - The server has not found anything matching the requested URI (Uniform Resource Identifier).
GET - https://www.canada.ca/etc/designs/canada/cdts/gcweb/v4_0_32/js/i18n/en-Ca.min.js

Which causes features in WET to stop working.
I think it would make sense to have some interpolation on the lang element to know that if en-CA is entered the en.min.js script should be loaded; not the en-CA.min.js.

Hello @s-laugh: The issue is outside our scope, you should report the issue to WET team.
https://github.com/wet-boew/wet-boew

Hello @s-laugh: The issue is outside our scope, you should report the issue to WET team.
https://github.com/wet-boew/wet-boew

Since the project is under the same group, the issue could just be moved.

Transferring an issue to another repository


Fix spurious HTTP related test failure [2.0]

Do not enforce an http-max-response-time-ms for the ignition wallet in testnet.template.  These responses are not large and sometimes burps happen

#8862 indicates that a -1 here is not a good choice


Can't debug the application

Followed the project setup step by step and created a very minimal project. When I start debugging I get the error:
Process terminated without establishing connection to debugger. application descriptor not found
Here is my launch.json:
{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "swf",
            "request": "launch",
            "name": "Launch SWF",
            "profile": "mobileDevice",
            "screensize": "iPhoneRetina",
            "screenDPI": 326,
            "versionPlatform": "IOS"
        },
        {
            "type": "swf",
            "request": "attach",
            "name": "Attach SWF"
        }
    ]
}

I can see that VS Code can see the sdk from the lower right corner of the VSCode window.
EDIT: Building works fine using "ActionScript: compile debug build" task.

application descriptor not found

It seems to be having trouble finding your Adobe AIR -app.xml file. Did you specify it in asconfig.json so that it gets populated and copied to your output folder?

I can see that Main.swf and Main-app.xml is copied to the output folder after building. Also the value of the content element is replaced with "Main.swf" in the app descriptor file in the output folder.

Can you share the contents of asconfig.json?

Also, double check that the AIR namespace at the root of Main-app.xml is appropriate for the version of the AIR SDK that you're using.

asconfig.json:
{
	"config": "airmobile",
	"compilerOptions": {
		"output": "bin/Main.swf"
	},
	"application": "src/Main-app.xml",
	"files": [
		"src/Main.as"
	]
}

Main-app.xml:
<?xml version="1.0" encoding="utf-8" ?>
<application xmlns="http://ns.adobe.com/air/application/31.0">
	<id>com.example.Main</id>
	<versionNumber>0.0.0</versionNumber>
	<filename>Main</filename>
	<name>Main</name>
	<initialWindow>
		<content>[Path to content will be replaced by Visual Studio Code]</content>
		<visible>true</visible>
	</initialWindow>
</application>

VS Code shows the AIR SDK version as <IP_ADDRESS>. I used bot 31.0 and <IP_ADDRESS> in the app descriptor file.

I can put the project under a repo if it helps.

Sorry, accidentally clicked the close button.

If you modify launch.json to add a program field that points to bin/Main-app.xml, does it work?
{
    "type": "swf",
    "request": "launch",
    "name": "Launch SWF",
    "profile": "mobileDevice",
    "screensize": "iPhoneRetina",
    "screenDPI": 326,
    "versionPlatform": "IOS",
    "program": "bin/Main-app.xml"
}

No it doesn't 😕
I can temporarily upload the project to a repo if you'd like to try it yourself but this is not much different from the template you set up in the wiki.

You can zip it up and attach it here, if you'd like.

Here it is.
action-script.zip

Hey @joshtynjala, any progress on this?

I haven't had a chance to try your project yet. I will do it later today.

@onselakin You are missing .vscode/tasks.json file:
{
    // See https://go.microsoft.com/fwlink/?LinkId=733558
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "tasks": [
        {
            "identifier": "build-debug",
            "type": "actionscript",
            "debug": true,
            //"air": "ios",
            "group": {
                "kind": "build",
                "isDefault": true
            }
        }
    ]
}

and "preLaunchTask": "build-debug" line in your .vscode/launch.json:
{
	// Use IntelliSense to learn about possible SWF debug attributes.
	// Hover to view descriptions of existing attributes.
	// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
	"version": "0.2.0",
	"configurations": [
		{
			"type": "swf",
			"request": "launch",
			"name": "Launch SWF",
			"profile": "mobileDevice",
			"screensize": "iPhoneRetina",
			"screenDPI": 326,
			"versionPlatform": "IOS",
			"program": "bin/Main-app.xml",

			"preLaunchTask": "build-debug"
		},
		{
			"type": "swf",
			"request": "attach",
			"name": "Attach SWF"
		}
	]
}

Note: VSCode says Warning but it works:

User defined identifiers are deprecated. For custom task used the name as a reference and for tasks provided by extensions use their defined task identifier.

I just tried your project. I compiled a debug build and then I launched the debugger. The AIR simulator opened, and the debugger connected successfully.
Perhaps there is something wrong with your AIR SDK? Maybe you should re-download it.

@joshtynjala Same time answering here :) @onselakin probably didn't build before debug.

@joshtynjala I re-downloaded but same error here, really strange.
@neminovno No, I build before pressing Debug :-)
I'm sharing the screenshot of VSCode so you can better see what's going on there.

I compile the project without any errors, you can see the bin folder and its contents are created. When I press F5, after the project is built a second time, I get the error you see on the screenshot.
At this stage, I don't see AIR simulator running but I can run Flash Player projector content debugger manually and open the compiled swf. Also I can attach to the Flash player debugger without any problems.
I guess the only difference from Josh's setup is Air simulator doesn't run automatically and this makes me uncomfortable as the development workflow is interrupted.

Ok, a minor development here.
I never look at the problems window while coding with VSCode because I find the terminal almost always more stable in error reporting but when I looked to the problems list this time I saw this error:
unable to open '/Users/onselakin/Development/AirSdk/frameworks/locale/en_TR'.
/Users/onselakin/Development/AirSdk/frameworks/airmobile-config.xml (line: 64)

@joshtynjala Does the extension send locale information to the compiler because although I changed the airmobile-config.xml manually it still tried to find a folder named en_TR under the frameworks/locale folder.

although I changed the airmobile-config.xml manually it still tried to find a folder named en_TR under the frameworks/locale folder

Did you restart VSCode after doing this?

Did you restart VSCode after doing this?

Yes, restarting fixed the locale problem, but the main problem is still there.

@onselakin Can you post the contents of bin/Main-app.xml? It should be similar to src/Main-app.xml, but I'd like to make sure that the string replacement worked correctly.

src/Main-app.xml:
<?xml version="1.0" encoding="utf-8" ?>
<application xmlns="http://ns.adobe.com/air/application/31.0">
	<id>com.example.Main</id>
	<versionNumber>1.0.0</versionNumber>
	<filename>Main</filename>
	<name>Main</name>
	<initialWindow>
		<content>[Path to content will be replaced by Visual Studio Code]</content>
		<visible>true</visible>
	</initialWindow>
</application>

bin/Main-app.xml
<?xml version="1.0" encoding="utf-8" ?>
<application xmlns="http://ns.adobe.com/air/application/31.0">
	<id>com.example.Main</id>
	<versionNumber>1.0.0</versionNumber>
	<filename>Main</filename>
	<name>Main</name>
	<initialWindow>
		<content>Main.swf</content>
		<visible>true</visible>
	</initialWindow>
</application>

Does the full path to bin/Main-app.xml contain any non-Latin UTF characters? Maybe the AIR simulator is can't handle that.

No, there aren't any non-Latin characters. It's under /Users/onselakin/Development/action-script folder.

Inside launch.json, give the absolute path a try:
"program": "Users/onselakin/Development/action-script/bin/Main-app.xml"

Finally! I thought I tried this but it seems I haven't!
Thank you @joshtynjala!


Mini-dump thread stack frames are missing

After upgrading our dump parsing application to CLRMD v2.0, and attempting to parse a mini-dump, we are seeing missing stack frames for some threads. The mini-dump was taken from a process that is running on Ubuntu-20.04 and is also being parsed on the same system.
Here are some screenshots of a thread and its stack frame traced using Dotnet-dump analyze, a sample clrstack class file provided in the CLRMD repository and our custom tracing application running on CLRMD v1.1.
Any idea as to what is causing this issue?
Dotnet-dump analyze:

CLRMD v2.0 sample dump parser:
https://github.com/microsoft/clrmd/blob/124b189a2519c4f13610c6bf94e516243647af2e/src/Samples/ClrStack/ClrStack.cs
(*** The only modification done to this class was that I removed the parsing of DumpStackObjects so that there are only thread callstacks in the output.)

Application running CLRMD v1.1:

This is typically due to not being able to properly find PE images for the files in question.  We have a System.Diagnostics.Trace.WriteLine call in ClrMD (both versions I think) which prints out messages, for example:  https://github.com/microsoft/clrmd/blob/master/src/Microsoft.Diagnostics.Runtime/src/Implementation/SymbolServerLocator.cs#L239
https://github.com/microsoft/clrmd/blob/4051dff2b192c47d78bb21d28ca84ed9acc6af25/src/Microsoft.Diagnostics.Runtime/src/Implementation/SymbolServerLocator.cs#L271
You can see these in Visual Studio's debugger events, or you can connect a standard listener to Diagnostics.Trace to write out to console.  Can you collect that data and post it here?  That should explain what's going on.

I've ran the parser with a listener connected, but I received no Trace messages from the SymbolServerLocator. I've also tried to load the binaries before enumerating through the threads.
        foreach (var module in dataTarget.EnumerateModules())
        {
            Console.WriteLine($"Finding binary: {module.FileName}");
            var binaryLocation = dataTarget.BinaryLocator.FindBinaryAsync(module.FileName, module.IndexTimeStamp, module.IndexFileSize, true);
            Console.WriteLine($"FindBinary output: {binaryLocation.Result}");
        }

Each module that was ran through the BinaryLocator returned the module location so I dont think that there are files missing(?).
I've also noticed that the ability to set a symbol path to the SymbolLocator has been removed, instead it is checking for environment variables set beforehand. This could be the cause of the problem if there are any binaries that are not found and are needed to be downloaded from the server, but this doesn't hold since CLRMD 2.0 parses our full-dumps without a problem.


ARL NPU support

Any plan to support on ARL NPU or just update openvino version

Support for ARL NPU will be coming soon. It will include an updated OpenVINO release, but that should be hidden in the installation, there won't be anything that you will need to do differently.

v2.99-R3 is now released. It should work for ARL, please let me know if you have any issues.


Converting to a CMake build system, updating to SDK version 2.0.3

While most of the actual code remains the same, this is a complete paradigm change which really blows away all currently supported workflows, so I really appreciate your encouragement to submit this PR.
A quick changelog:

CMake build system based heavily off the work in the Playdate SDK
An updated link map from the most recent Playdate SDK

This includes some additions to clear linker errors around exceptions, but it's unlikely that this is a functional solution

A completely new workflow based on taking a dependency on this repo and building a CMake project around it

There is an example "Hello World" project which demonstrates what a user should expect to see in their build scripts

Thank you again for considering this PR.

I don't think I can properly review this as I don't have time right now, but I trust that you are invested more than I am right now, so I'll give you collab access and you can merge this if you feel that it is ready.

Edit: I'm giving you collab access. :)


Connection enhancements

Implements https://github.com/rwaldron/particle-io/issues/69 and https://github.com/rwaldron/particle-io/issues/67.
Gives two optional ways to connect to the Particle:
By Name
var byName = new Particle({
  token: process.env.PARTICLE_TOKEN,
  deviceName: process.env.PARTICLE_DEVICE_NAME || "crazy_pickle"
});

By Host/Port
var byIp = new Particle({
  host: '<IP_ADDRESS>',
  port: 48879
});

The existing mechanism (deviceId) still works:
var byId = new Particle({
  token: process.env.PARTICLE_TOKEN,
  deviceId: process.env.PARTICLE_DEVICE_ID
});

Will review tomorrow

@rwaldron Thanks for the review.  Fixed.


Use vue-virtual-scroller 1.0.10

The latest compatible (with package.json) release of vue-virtual-scroller (1.1.2) has an issue where scrollToItem breaks if a gridSize is not mentioned. This causes a bug on the Workflow History page where selecting any item in the activity list causes the entire list to snap back up, which adversely affects UX with longer activity lists.
Since the lockfile already uses 1.0.10, this PR downgrades the version in package.json to match it, so that anyone using cadence-web as an NPM package also gets vue-virtual-scroller 1.0.10.

Hi, @Assem-Uber issue still exists in the new cadence-web "3.35.5-beta.2".

@matteeos thanks for reporting the problem.
can you please provide the version of vue-virtual-scroller in your package-lock.json

it's 1.0.10
    "vue-virtual-scroller": {
      "version": "1.0.10",
      "resolved": "https://unpm.uberinternal.com/vue-virtual-scroller/-/vue-virtual-scroller-1.0.10.tgz",
      "integrity": "sha512-Hn4qSBDhRY4XdngPioYy/ykDjrLX/NMm1fQXm/4UQQ/Xv1x8JbHGFZNftQowTcfICgN7yc31AKnUk1UGLJ2ndA==",
      "requires": {
        "scrollparent": "^2.0.1",
        "vue-observe-visibility": "^0.4.4",
        "vue-resize": "^0.4.5"
      }
    }

matching defined in package.json<EMAIL_ADDRESS>

@matteeos seems like there is another dependency change causing that issue.
Are you tracking the differences between your package-lock.json before and after the issue ?

No, just did a few versions upgrade of cadence and found that issue. I see @kotcrab already have created issue for it https://github.com/uber/cadence-web/issues/632 so let's continue there.


Tracker to stop rebuilding FCOS

The README includes details on the diff between FCOS and OKD. Let's figure out how to address each of them without having to rebuild FCOS.

manifest.yaml is a copy of FCOS manifest with the following changes:

tweaked version (special OKD version is set to designate the difference between OKD image and FCOS) and custom ostree ref

We naturally won't need this anymore once we stop rebuilding FCOS.

On top of FCOS base configuration additional OKD packages are installed:

openshift-hyperkube - kubelet

OK yup, that's the big one. I guess for that we'd need something like https://github.com/openshift/os/issues/498.

crio, cri-tools - container runtime

https://github.com/coreos/fedora-coreos-tracker/issues/767

NetworkManager-ovs for OpenshiftOVN
open-vm-tools, qemu-guest-agent - cloud tools for vSphere/oVirt

These are Fedora packages, right? Should be able to package layer.

openshift-clients - RPM with oc binary

Same as openshift-kyperkube.

glusterfs, glusterfs-fuse - required to pass glusterfs tests

These are also Fedora packages, right?

packages is updated to avoid including zincati (OKD uses CVO/MCO for updates)

We can mask the Zincati service.

Available repos are disabled in postprocess section to make sure updates are reproducible

If we start package layering, then we need the repos enabled. But I think we could have a new mode in rpm-ostree where we only allow some package layering. Alternatively... we ship all the Fedora packages we need in a separate container? (Something like OS extensions, but it'd need to be more closely integrated.)

OKD machine-os inherits image.yaml to produce ostree commit and manifest-lock.* files to ensure base packages are as close to FCOS as possible.
Overlayed configuration is used in overlay.d, symlinking FCOS settings. The repo also has OKD-specific 99okd overlay, which does the following:

dhclient.conf in order to prevent br-ex interface from getting a wrong MAC
sshd_config.d dropin to allow ssh-rsa keys to be compatible with OCP.
localtime symlinked to UTC (required for fluentd).
gcp-hostname service which uses Afterburn to set GCP hostname.

I think these could all be part of the Ignition config, no?
So yeah, it seems like the big ones are openshift-hyperkube and openshift-clients. If we can resolve those by somehow shoving them in the release payload, do we agree the rest should be solvable?

As a concrete example, if OKD doesn't rebuild FCOS, then it becomes much easier to add Prow testing of OKD to https://github.com/coreos/fedora-coreos-config, which I think would be of great benefit to OKD (and also ties into https://github.com/coreos/fedora-coreos-tracker/issues/767; see https://github.com/coreos/fedora-coreos-tracker/issues/767#issuecomment-934448876).

These are Fedora packages, right? Should be able to package layer.

iiuc that can be done only after https://hackmd.io/@darkmuggle/rJw8Cyh9_ is accepted as an enhancement, right?

gcp-hostname service which uses Afterburn to set GCP hostname.
I think these could all be part of the Ignition config, no?

That'd require us to fork installer again and/or carry more patches for MCO

These are Fedora packages, right? Should be able to package layer.

iiuc that can be done only after hackmd.io/@darkmuggle/rJw8Cyh9_ is accepted as an enhancement, right?

Would be nice to not block on that if possible.
Are all those packages needed before pivot?

gcp-hostname service which uses Afterburn to set GCP hostname.

I think these could all be part of the Ignition config, no?

That'd require us to fork installer again and/or carry more patches for MCO

Ahh right OK, that rings a bell now (sorry, I don't have a good handle on all the backstory here). Hmm, if it can't live in the installer/MCO, it seems like those projects should at least define a way for OKD to extend them at build time for what it needs.

Would be nice to not block on that if possible.

Sure, but I'm not aware of any other way to create an additional layer on top of FCOS really.

Are all those packages needed before pivot?

We pivot from genuine FCOS image by extracting MCO from machine-config-image. All of these packages end up in the final OS required to start the node.
However it would be useful to build OKD OS LiveCD, so that we could make use of Assisted Installer and SNO Bootstrap-in-place (all of these work with RHCOS LiveCD)

it seems like those projects should at least define a way for OKD to extend them at build time for what it needs

We have a defined way how to extend installer, but the idea is to keep changes as minimal as possible, so that we wouldn't wait for ages for lgtm and avoid filling up openshift-installer with FCOS-specific logic.
No particular plan for MCO, there are bits which make it work with RHCOS and FCOS, but some PRs are pending review

/remove-lifecycle stale
/lifecycle frozen

https://github.com/coreos/enhancements/blob/main/os/coreos-layering.md is highly relevant here.


Help making a custom executable

Hello, I'm trying to modify the paw color in data.cpp  by modifying the variable "paw": [255, 255, 255] by "paw": [239, 154, 35] (as shown here). I'm having several issues when running the Makefile and after hours of trying to solve the problem I was wondering if anyone can help me making the executable and sending it to me.
Sorry for the inconvenience.

You don't change that in the Makefile, you change it in the config.json file that is in the same folder as your executable.
Remember to download the latest release first.


add this project to https://www.scala-js.org/libraries/facades.html

Exactly what I was looking for.

Thanks! Please provide some feedback once you've had a chance to play with it.

Will do.
It's not clear that people understand how important this project is given
that node/js is really the next jvm. There will only a few large scale
platforms to run on since the world cannot manage more than a few at a time
given the cost of each platform.
On Sat, Apr 15, 2017 at 9:19 PM Lawrence Daniels<EMAIL_ADDRESS>wrote:

Thanks! Please provide some feedback once you've had a chance to play with
it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/scalajs-io/nodejs/issues/8#issuecomment-294327395,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIOaX-qChfY2ZzpMWpgxn264-OAtEl7ks5rwWy1gaJpZM4M-egi
.

My sincere hope is that this project can help drive adoption of Scala.js on Node.js. We'll see!

Request made.