stop_signal supported with docker stack deploy

support was added nearly two years ago, c.f. https://github.com/docker/cli/issues/370

Deploy preview for docsdocker ready!
Built with commit 580312e771f979b9c3b0f763f6ff63fa2a0f59b7
https://deploy-preview-8399--docsdocker.netlify.com

Deploy preview for docsdocker ready!
Built with commit 580312e771f979b9c3b0f763f6ff63fa2a0f59b7
https://deploy-preview-8399--docsdocker.netlify.com


Add -LiteralPath to Get-Node and Get-ChildNode

Add -LiteralPath to Get-Node and Get-ChildNode

Implemented for Get-Node with -Literal switch in 0.1.0


Fixed bug where value was an hour off with stepping enabled

setValue(targetMoment) rounds the value using the stepping option, when the rounded minutes were 60 or more the code did not increase the hours.

Moment is supposed to "bubble" those automatically. Please show me a jsfiddle of what's not working. Also, all PRs must be submitted to the development branch

Bubbling up makes the fix even easier, I'll just have to remove the "% 60" :)
I'll make a pull request for the dev branch, would like to see this included in a patch for the current version though!
Here's the fiddle with the issue:
http://jsfiddle.net/gjcwzpgp/


GandhiSaid

GandhiSaid

Thanks for joining us! Closing until next year's run. :)
Man, you had tons, haha. :D

:+1: Looking forward for the next year.


file not recognized: File format not recognized

command-line-arguments
C:\Go\pkg\tool\windows_amd64\link.exe: running gcc failed: exit status 1
C:\Users\username\AppData\Local\Temp\go-link-619833591\go.o: file not recognized: File format not recognized
collect2.exe: error: ld returned 1 exit status

Got me.  Can you maybe add a detailed description of what you were doing?  Maybe show the command you entered to come about this error?   Without some context there's no way I can help here :(


Use DMD in Slave Mode

Hi,
Thanks for creating this package! I am trying to use a Vialux DMD in slave mode such that an external trigger signal can be used to display the next image. I've seen some hints in the code about this, but I'm unsure about how to apply it. Also, do you know if there's a method to externally trigger the DMD to turn off? Would appreciate any help!
Best,
Felix & Gordon :D
cc: @roflmaostc

Hi @wavefrontshaping,
I wanted to see if there is any news?
Otherwise we probably use this librarry: https://gitlab.phys.ethz.ch/mohanj/holography/-/blob/096ce42d18efc5f4eda14a53013a4cffb3220830/dmd/communication.py
Best,
Felix

Hi,
Have you check the ALP API documentation?
It seems that, according to Section 2.14 AlpProjControl of the API description, that one can change such parameters using the C function ALPProjControl, which  you can call using DMD.ProjControl(...) in Python.
Never done it but according to the doc, you should simply use DMD.ProjControl(ALP_PROJ_MODE, ALP_SLAVE) to put it in slave mode.
from ALP4 import *
...
DMD.ProjControl(ALP_PROJ_MODE, ALP_SLAVE)

Of course, you should then configure the timings according to your needs.

Just to write down for future readers. Triggers works, there some sharp edges noted below.
from ALP4 import *
dmd = ALP4(version = '4.3', libDir=".")

# Initialize the device
dmd.Initialize()

imgSeq = ([
    np.asarray(Image.open("../01.png").convert('L')).ravel(),
    np.asarray(Image.open("../02.png").convert('L')).ravel(),
]

imgSeq = np.array(imgSeq)
print(imgSeq.shape)
dmd.SeqAlloc(nbImg = imgSeq.shape[0], bitDepth = 8)

# Send the image sequence as a 1D list/array/numpy array
dmd.SeqPut(imgData = imgSeq)

# set to 50Hz
# If you set fraction to 1, then the DMD misses sometimes the triggers because
# the DMD switches to the next image only if the pictureTime is over.
# so it shows an image for the pictureTime, blanks the DMD and waits for the trigger
# to show the next image.
fraction = 0.95
dmd.SetTiming(pictureTime = round(0.05*1_000_000 * fraction))
dmd.ProjControl(ALP_PROJ_MODE, ALP_SLAVE)

dmd.Run()
# best case start the triggers here otherwise you might skip some frames

@wavefrontshaping if welcomed, I can put a minimal example to the README with a PR

Hi,
@roflmaostc
I wonder why you are setting the pictureTime? This should be the framerate of the DMD but you're using the hardware trigger.
fraction = 0.95 dmd.SetTiming(pictureTime = round(0.05*1_000_000 * fraction))

We observed some issues if the pictureTime is longer than the real trigger intervals. In that case the DMD would ignore the triggers.
So pictureTime has to be slightly lower than real interval. Maybe it's better to subtract 10 (in units of microsecond) instead of the fraction hack.


Long click to copy message and link intergration

Hi,
here are some interesting features

long click on a message to copy message content to clipboard
link integration, URL must be identify and tranfrom to a clickable link that directly open the phone browser

here is this at ?


ADDomain invalid password after windows update

Problem description
We are using azure arm templates with a DSC extention to deploy a windows AD in our test environment.
For the last few years this worked without issue but since last week we cant deploy new environments.
Because of the following error message:
The password supplied to the Desired State Configuration resource MSFT_ADDomain is not valid. The password cannot be null or empty.  error.
We are having this issue on both  2016-Datacenter and 2022-Datacenter.
When we use a older azure image reference the dsc configuration works.
                    "imageReference": {
                        "publisher": "MicrosoftWindowsServer",
                        "offer": "WindowsServer",
                        "sku": "2016-Datacenter",
                        "version": "14393.5125.220505"
                    },

But if we redeploy the configuration after the machine is up for a few hours and it had installed the lasted windows updates the configuraiton no longer works
Verbose logs
Azure deployment log:
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"VMExtensionProvisioningError","message":"VM has reported a failure when processing extension 'CreateADForest'. Error message: \"DSC Configuration 'CreateADPDC' completed with error(s). Following are the first few: The password supplied to the Desired State Configuration resource MSFT_ADDomain is not valid. The password cannot be null or empty. The SendConfigurationApply function did not succeed.\"\r\n\r\nMore information on troubleshooting is available at https://aka.ms/VMExtensionDSCWindowsTroubleshoot "}]}

DSC extension handler log:
VERBOSE: [2022-06-20 07:53:48Z] Extension request for sequence number 3
attempting to create lock.3 mutex
VERBOSE: [2022-06-20 07:53:48Z] Attempting to grab mutex
DscExtensionHandler_Lock for sequence number 3
VERBOSE: [2022-06-20 07:53:48Z] Acquired lock for extension instance for
sequence number 3
VERBOSE: [2022-06-20 07:53:48Z] Attempting to acquire extension lock
VERBOSE: [2022-06-20 07:53:48Z] Attempting to grab mutex
DscExtensionHandler_Lock
VERBOSE: [2022-06-20 07:53:48Z] Acquired lock for extension
VERBOSE: [2022-06-20 07:53:48Z] lock does not exist: begin processing
VERBOSE: [2022-06-20 07:53:48Z] Starting DSC Extension ...
VERBOSE: [2022-06-20 07:53:48Z] Getting handler execution status
HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status ...
VERBOSE: [2022-06-20 07:53:48Z] Updating execution status
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status)
VERBOSE: [2022-06-20 07:53:48Z] Transitioning to DataValidation state ...
VERBOSE: [2022-06-20 07:53:48Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:53:48Z] Retrieving system information ...
VERBOSE: [2022-06-20 07:53:55Z]     OS Version : 10.0
VERBOSE: [2022-06-20 07:53:55Z]     Server OS  : True
VERBOSE: [2022-06-20 07:53:55Z]     64-bit OS  : True
VERBOSE: [2022-06-20 07:53:55Z]     PS Version : 5.1.14393.5127
VERBOSE: [2022-06-20 07:53:55Z] Validating user provided settings for the DSC
Extension Handler ...
VERBOSE: [2022-06-20 07:53:55Z] Reading handler settings from
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\RuntimeSettings\3.setting
s
VERBOSE: [2022-06-20 07:53:55Z] Found protected settings on Azure VM.
Decrypting.
VERBOSE: [2022-06-20 07:53:59Z] Updating user preference for Data Collection
......
VERBOSE: [2022-06-20 07:53:59Z] Get DSC Extension Handler install status  ...
VERBOSE: [2022-06-20 07:53:59Z]  Status: Installed
VERBOSE: [2022-06-20 07:53:59Z] Updating execution status
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status)
VERBOSE: [2022-06-20 07:53:59Z] Transitioning to ProcessConfiguration state
...
VERBOSE: [2022-06-20 07:53:59Z] Getting handler execution status
HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status ...
VERBOSE: [2022-06-20 07:54:00Z] Getting handler execution status
HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status ...
VERBOSE: [2022-06-20 07:54:00Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:54:00Z] Applying DSC configuration:
VERBOSE: [2022-06-20 07:54:00Z]     Sequence Number:              3
VERBOSE: [2022-06-20 07:54:00Z]     Configuration URL:
https://slvdr7azure7filecopy.blob.core.windows.net/tqjkpal6qjgb2/DSC/CreateADPD
C.zip?sv=2015-04-05&sr=c&sig=eU6xOvyNFK3Xu0%2FbfLTwfQMj%2BPI48etbS3I6QUu8QTY%3D
&se=2022-06-20T08%3A53%3A18Z&sp=r
VERBOSE: [2022-06-20 07:54:00Z]     Configuration Script:
CreateADPDC.ps1
VERBOSE: [2022-06-20 07:54:00Z]     Configuration Function:       CreateADPDC
VERBOSE: [2022-06-20 07:54:00Z] Creating Working directory:
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\bin\..\DSCWork\CreateADPD
C.3
VERBOSE: [2022-06-20 07:54:00Z] Downloading configuration package
VERBOSE: [2022-06-20 07:54:00Z] Downloading
https://slvdr7azure7filecopy.blob.core.windows.net/tqjkpal6qjgb2/DSC/CreateADPD
C.zip to
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\bin\..\DSCWork\CreateADPD
C.3\CreateADPDC.zip
VERBOSE: [2022-06-20 07:54:00Z] Extracting CreateADPDC.zip
VERBOSE: [2022-06-20 07:54:05Z] Installing custom DSC resource modules to
C:\Program Files\WindowsPowerShell\Modules
VERBOSE: [2022-06-20 07:54:05Z] Installing custom DSC resource module
ActiveDirectoryDsc
VERBOSE: [2022-06-20 07:54:05Z] Copying
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\Act
iveDirectoryDsc to C:\Program
Files\WindowsPowerShell\Modules\ActiveDirectoryDsc ...
VERBOSE: [2022-06-20 07:54:06Z] Installing custom DSC resource module xStorage
VERBOSE: [2022-06-20 07:54:06Z] DSC resource module xStorage already exists.
Removing it first ...
VERBOSE: [2022-06-20 07:54:06Z] Copying
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\xSt
orage to C:\Program Files\WindowsPowerShell\Modules\xStorage ...
VERBOSE: [2022-06-20 07:54:06Z] Installing custom DSC resource module
xNetworking
VERBOSE: [2022-06-20 07:54:06Z] DSC resource module xNetworking already exists.
 Removing it first ...
VERBOSE: [2022-06-20 07:54:06Z] Copying
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\xNe
tworking to C:\Program Files\WindowsPowerShell\Modules\xNetworking ...
VERBOSE: [2022-06-20 07:54:07Z] Installing custom DSC resource module
xPendingReboot
VERBOSE: [2022-06-20 07:54:07Z] DSC resource module xPendingReboot already
exists. Removing it first ...
VERBOSE: [2022-06-20 07:54:07Z] Copying
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\xPe
ndingReboot to C:\Program Files\WindowsPowerShell\Modules\xPendingReboot ...
VERBOSE: [2022-06-20 07:54:07Z] Installing custom DSC resource module
xComputerManagement
VERBOSE: [2022-06-20 07:54:07Z] DSC resource module xComputerManagement already
 exists. Removing it first ...
VERBOSE: [2022-06-20 07:54:07Z] Copying
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\xCo
mputerManagement to C:\Program
Files\WindowsPowerShell\Modules\xComputerManagement ...
VERBOSE: [2022-06-20 07:54:07Z] Looking for the definition of the configuration
 function.
VERBOSE: [2022-06-20 07:54:07Z] Executing
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\bin\..\DSCWork\CreateADPD
C.3\CreateADPDC.ps1
VERBOSE: [2022-06-20 07:54:08Z] Preparing configuration arguments and
configuration data.
VERBOSE: [2022-06-20 07:54:08Z] Adding encryption certificate
E9927E07C416C05E8EBF380AB2CF1D6F90BC348D to the configuration data
VERBOSE: [2022-06-20 07:54:08Z] Creating MOF files.
VERBOSE: [2022-06-20 07:54:08Z] Executing the configuration function to
generate the MOF files.
WARNING: It is not recommended to use domain credential for node 'localhost'.
In order to suppress the warning, you can add a property named
'PSDscAllowDomainUser' with a value of $true to your DSC configuration data for
 node 'localhost'.
VERBOSE: [2022-06-20 07:54:17Z] Meta configuration found. Injecting
Thumbprint.
VERBOSE: [2022-06-20 07:54:18Z] CertificateID not present in existing meta
configuration; inserting E9927E07C416C05E8EBF380AB2CF1D6F90BC348D.
VERBOSE: [2022-06-20 07:54:18Z] Verifying metaconfiguration for reboot
information...
VERBOSE: [2022-06-20 07:54:18Z] Backing up
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\Cre
ateADPDC\localhost.meta.mof
VERBOSE: [2022-06-20 07:54:18Z] No match for RegistrationKey found in the meta
mof file
VERBOSE: [2022-06-20 07:54:18Z] WMF 5 or newer, Injecting RebootNodeIfNeeded =
False and ActionAfterReboot = "StopConfiguration"
VERBOSE: [2022-06-20 07:54:18Z] Executing Set-DscLocalConfigurationManager...
VERBOSE: [2022-06-20 07:54:18Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] Performing the operation
"Start-DscConfiguration: SendMetaConfigurationApply" on target
"MSFT_DSCLocalConfigurationManager".
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] Perform operation 'Invoke CimMethod'
with following parameters, ''methodName' =
SendMetaConfigurationApply,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] An LCM method call arrived from
computer ad-server with user sid S-1-5-18.
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]  [MSFT_DSCMetaConfiguration]  in 0.0150 seconds.
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]    in  0.1250 seconds.
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] Operation 'Invoke CimMethod'
complete.
VERBOSE: [2022-06-20 07:54:19Z] [VERBOSE] Set-DscLocalConfigurationManager
finished in 0.287 seconds.

VERBOSE: [2022-06-20 07:54:21Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:54:22Z] [VERBOSE] Perform operation 'Invoke CimMethod'
with following parameters, ''methodName' = SendConfigurationApply,'className' =
 MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: [2022-06-20 07:54:22Z] [VERBOSE] An LCM method call arrived from
computer ad-server with user sid S-1-5-18.
VERBOSE: [2022-06-20 07:54:22Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[WindowsFeature]DNS]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[WindowsFeature]DNS]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]DNS] The operation 'Get-WindowsFeature' started: DNS
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]DNS] The operation 'Get-WindowsFeature' succeeded: DNS
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[WindowsFeature]DNS]  in 0.6560 seconds.
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[WindowsFeature]DNS]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[WindowsFeature]DNS]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[Script]EnableDNSDiags]
VERBOSE: [2022-06-20 07:54:24Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[Script]EnableDNSDiags]
VERBOSE: [2022-06-20 07:54:25Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[Script]EnableDNSDiags]  in 0.0620 seconds.
VERBOSE: [2022-06-20 07:54:25Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]  [[Script]EnableDNSDiags]
VERBOSE: [2022-06-20 07:54:25Z] [VERBOSE] [ad-server]:
   [[Script]EnableDNSDiags] Performing the operation "Set-TargetResource" on
target "Executing the SetScript with the user supplied credential".
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]:
   [[Script]EnableDNSDiags] Enabling DNS client diagnostics
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]  [[Script]EnableDNSDiags]  in 1.9070 seconds.
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[Script]EnableDNSDiags]
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[WindowsFeature]DnsTools]
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[WindowsFeature]DnsTools]
VERBOSE: [2022-06-20 07:54:26Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]DnsTools] The operation 'Get-WindowsFeature' started:
RSAT-DNS-Server
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]DnsTools] The operation 'Get-WindowsFeature' succeeded:
RSAT-DNS-Server
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[WindowsFeature]DnsTools]  in 0.4380 seconds.
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[WindowsFeature]DnsTools]
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[WindowsFeature]DnsTools]
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[xDNSServerAddress]DnsServerAddress]
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[xDNSServerAddress]DnsServerAddress]
VERBOSE: [2022-06-20 07:54:27Z] [VERBOSE] [ad-server]:
   [[xDNSServerAddress]DnsServerAddress] Test-TargetResource: Checking the DNS
server addresses.
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]:
   [[xDNSServerAddress]DnsServerAddress] Get-DnsClientServerStaticAddress:
Getting staticly assigned DNS server IPv4 address for interface alias
'Ethernet'.
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]:
   [[xDNSServerAddress]DnsServerAddress] Get-DnsClientServerStaticAddress:
Statically assigned DNS server IPv4 address for interface alias 'Ethernet' is
'<IP_ADDRESS>,<IP_ADDRESS>'.
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]:
   [[xDNSServerAddress]DnsServerAddress] Test-TargetResource: DNS server
addresses are set correctly.
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[xDNSServerAddress]DnsServerAddress]  in 1.1720 seconds.
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[xDNSServerAddress]DnsServerAddress]
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[xDNSServerAddress]DnsServerAddress]
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[xWaitForDisk]Disk2]
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[xWaitForDisk]Disk2]
VERBOSE: [2022-06-20 07:54:28Z] [VERBOSE] [ad-server]:
   [[xWaitForDisk]Disk2] Test-TargetResource: Checking for disk with Number
'2'.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[xWaitForDisk]Disk2] Test-TargetResource: Found disk with Number '2' named
'Msft Virtual Disk'.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[xWaitForDisk]Disk2]  in 1.5620 seconds.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[xWaitForDisk]Disk2]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[xWaitForDisk]Disk2]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[xDisk]ADDataDisk]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[xDisk]ADDataDisk]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[xDisk]ADDataDisk] Test-TargetResource: Testing disk with Number '2' status
 for drive letter 'F'.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[xDisk]ADDataDisk] Test-TargetResource: Checking if disk with Number '2' is
 initialized.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[xDisk]ADDataDisk] Perform operation 'Query CimInstances' with following
parameters, ''queryExpression' = SELECT BlockSize from Win32_Volume WHERE
DriveLetter = 'F:','queryDialect' = WQL,'namespaceName' = root\cimv2'.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[xDisk]ADDataDisk] Operation 'Query CimInstances' complete.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[xDisk]ADDataDisk]  in 0.3280 seconds.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[xDisk]ADDataDisk]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[xDisk]ADDataDisk]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[WindowsFeature]ADDSInstall]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[WindowsFeature]ADDSInstall]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADDSInstall] The operation 'Get-WindowsFeature' started:
AD-Domain-Services
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADDSInstall] The operation 'Get-WindowsFeature' succeeded:
AD-Domain-Services
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[WindowsFeature]ADDSInstall]  in 0.3440 seconds.
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[WindowsFeature]ADDSInstall]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[WindowsFeature]ADDSInstall]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[WindowsFeature]ADDSTools]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[WindowsFeature]ADDSTools]
VERBOSE: [2022-06-20 07:54:30Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADDSTools] The operation 'Get-WindowsFeature' started:
RSAT-ADDS-Tools
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADDSTools] The operation 'Get-WindowsFeature' succeeded:
RSAT-ADDS-Tools
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[WindowsFeature]ADDSTools]  in 0.4690 seconds.
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[WindowsFeature]ADDSTools]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[WindowsFeature]ADDSTools]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[WindowsFeature]ADAdminCenter]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[WindowsFeature]ADAdminCenter]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADAdminCenter] The operation 'Get-WindowsFeature' started:
RSAT-AD-AdminCenter
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]:
   [[WindowsFeature]ADAdminCenter] The operation 'Get-WindowsFeature'
succeeded: RSAT-AD-AdminCenter
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[WindowsFeature]ADAdminCenter]  in 0.3280 seconds.
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Skip   Set
]  [[WindowsFeature]ADAdminCenter]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [[WindowsFeature]ADAdminCenter]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [[ADDomain]FirstDS]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ Start  Test
]  [[ADDomain]FirstDS]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Test
]  [[ADDomain]FirstDS]  in 0.0310 seconds.
VERBOSE: [2022-06-20 07:54:31Z] [ERROR] The password supplied to the Desired
State Configuration resource MSFT_ADDomain is not valid. The password cannot be
 null or empty.
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] Time taken for configuration job to
complete is 9.073 seconds
VERBOSE: [2022-06-20 07:54:31Z] [ERROR] The SendConfigurationApply function did
 not succeed.
VERBOSE: [2022-06-20 07:54:31Z] [VERBOSE] Operation 'Invoke CimMethod'
complete.
VERBOSE: [2022-06-20 07:54:32Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:54:32Z] Updating execution status
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status)
VERBOSE: [2022-06-20 07:54:32Z] LCM state is PendingConfiguration
VERBOSE: [2022-06-20 07:55:33Z] DSC configuration completed.
VERBOSE: [2022-06-20 07:55:33Z] Resetting metaconfiguration...
VERBOSE: [2022-06-20 07:55:33Z] Restoring
C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\DSCWork\CreateADPDC.3\Cre
ateADPDC\localhost.meta.mof.bk...
VERBOSE: [2022-06-20 07:55:33Z] Executing Set-DscLocalConfigurationManager...
VERBOSE: [2022-06-20 07:55:33Z] Settings handler status to 'transitioning'
(C:\Packages\Plugins\Microsoft.Powershell.DSC\<IP_ADDRESS>\Status\3.status)
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] Performing the operation
"Start-DscConfiguration: SendMetaConfigurationApply" on target
"MSFT_DSCLocalConfigurationManager".
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] Perform operation 'Invoke CimMethod'
with following parameters, ''methodName' =
SendMetaConfigurationApply,'className' =
MSFT_DSCLocalConfigurationManager,'namespaceName' =
root/Microsoft/Windows/DesiredStateConfiguration'.
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] An LCM method call arrived from
computer ad-server with user sid S-1-5-18.
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ Start  Resource
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ Start  Set
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]  [MSFT_DSCMetaConfiguration]  in 0.0150 seconds.
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ End    Resource
]  [MSFT_DSCMetaConfiguration]
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] [ad-server]: LCM:  [ End    Set
]    in  0.0940 seconds.
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] Operation 'Invoke CimMethod'
complete.
VERBOSE: [2022-06-20 07:55:36Z] [VERBOSE] Set-DscLocalConfigurationManager
finished in 0.205 seconds.

VERBOSE: [2022-06-20 07:55:37Z] [ERROR] while enabling MDS telemetry... [MDS
Telemetry]
C:\WindowsAzure\GuestAgent_2.7.41491.1057_2022-06-18_094615\WindowsAzureEventSo
urce.dll does not exist ...
VERBOSE: [2022-06-20 07:55:37Z] Getting handler execution status
HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status ...
VERBOSE: [2022-06-20 07:55:37Z] Updating execution status
(HKLM:\SOFTWARE\Microsoft\Azure\DSC\<IP_ADDRESS>\Status)
VERBOSE: [2022-06-20 07:55:37Z] Transitioning to Completed state ...
VERBOSE: [2022-06-20 07:55:37Z] Releasing SameSeq mutex
VERBOSE: [2022-06-20 07:55:37Z] Releasing mutex DscExtensionHandler_Lock

DSC configuration
# Powershell desired state script to install AD, Adfs
# This script also creates a new AD forest.
configuration CreateADPDC
{
   param
   (
        [Parameter(Mandatory)]
        [String]$DomainName,

        [Parameter(Mandatory)]
        [System.Management.Automation.PSCredential]$Admincreds,

        [Int]$RetryCount=30,
        [Int]$RetryIntervalSec=30
    )
    # After editing this file run this command to recreate CreateADPDC.zip
    #      Publish-AzureRmVMDscConfiguration CreateADPDC.ps1 -OutputArchivePath CreateADPDC.zip -Force -Verbose
    # required modules:
    # powershell core: Publish-AzureVMDscConfiguration CreateADPDC.ps1 -ConfigurationArchivePath  CreateADPDC.zip -Force
    #  Install-Module -Name PSDesiredStateConfiguration -Repository PSGallery
    # Install-Module -Name xComputerManagement
    # Install-Module -Name xPendingReboot
    # Install-Module -Name xNetworking
    # Install-Module -Name xActiveDirectory
    # Install-Module -Name xStorage
    #Import-DscResource -ModuleName xActiveDirectory, xStorage, xNetworking, PSDesiredStateConfiguration, xPendingReboot, xComputerManagement
    Import-DscResource -ModuleName ActiveDirectoryDsc, xStorage, xNetworking, PSDesiredStateConfiguration, xPendingReboot, xComputerManagement
    [System.Management.Automation.PSCredential ]$DomainCreds = New-Object System.Management.Automation.PSCredential ("${DomainName}\$($Admincreds.UserName)", $Admincreds.Password)
    $Interface=Get-NetAdapter|Where Name -Like "Ethernet*"|Select-Object -First 1
    $InterfaceAlias=$($Interface.Name)

    Node localhost
    {
        LocalConfigurationManager
        {
            RebootNodeIfNeeded = $true
        }

	    WindowsFeature DNS
        {
            Ensure = "Present"
            Name = "DNS"
        }

        Script EnableDNSDiags
	    {
      	    SetScript = {
		        Set-DnsServerDiagnostics -All $true
                Write-Verbose -Verbose "Enabling DNS client diagnostics"
            }
            GetScript =  { @{} }
            TestScript = { $false }
	        DependsOn = "[WindowsFeature]DNS"
        }

	    WindowsFeature DnsTools
	    {
	        Ensure = "Present"
            Name = "RSAT-DNS-Server"
            DependsOn = "[WindowsFeature]DNS"
	    }

        xDnsServerAddress DnsServerAddress
        {
            # https://docs.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16
            Address        = '<IP_ADDRESS>', '<IP_ADDRESS>'
            InterfaceAlias = $InterfaceAlias
            AddressFamily  = 'IPv4'
	        DependsOn = "[WindowsFeature]DNS"
        }

        xWaitforDisk Disk2
        {
            DiskId = 2
            RetryIntervalSec =$RetryIntervalSec
            RetryCount = $RetryCount
        }

        xDisk ADDataDisk {
            DiskId = 2
            DriveLetter = "F"
            DependsOn = "[xWaitForDisk]Disk2"
        }

        WindowsFeature ADDSInstall
        {
            Ensure = "Present"
            Name = "AD-Domain-Services"
	        DependsOn="[WindowsFeature]DNS"
        }

        WindowsFeature ADDSTools
        {
            Ensure = "Present"
            Name = "RSAT-ADDS-Tools"
            DependsOn = "[WindowsFeature]ADDSInstall"
        }

        WindowsFeature ADAdminCenter
        {
            Ensure = "Present"
            Name = "RSAT-AD-AdminCenter"
            DependsOn = "[WindowsFeature]ADDSInstall"
        }

        ADDomain FirstDS
        {
            DomainName = $DomainName
            Credential = $DomainCreds
            SafemodeAdministratorPassword = $DomainCreds
            DatabasePath = "F:\NTDS"
            LogPath = "F:\NTDS"
            SysvolPath = "F:\SYSVOL"
	        DependsOn = @("[xDisk]ADDataDisk", "[WindowsFeature]ADDSInstall")
        }

        # wait vor AD to be ready
        WaitForADDomain DscForestWait
        {
           DomainName = $DomainName
           Credential= $DomainCreds
           WaitForValidCredentials = $true
           DependsOn = "[ADDomain]FirstDS"
        }

        # Ensure no pending reboots
        xPendingReboot Reboot1
        {
            Name = "RebootServer"
            DependsOn = "[WaitForADDomain]DscForestWait"
        }

        #install ADFS
        WindowsFeature installADFS
        {
            Ensure = "Present"
            Name   = "ADFS-Federation"
            DependsOn = "[xPendingReboot]Reboot1"
        }
   }
}

Suggested solution
I have tried changing the OS. (using 2022-datacenter latest)
I have updated the to the latest version of ActiveDirectoryDsc
We were using xADDomain <IP_ADDRESS> but that looked like a older version.
I have tried changing the ADDomain credentails to not included domain information.
(Just username:password instead of domain/username:password)
But everything leads to the same error.
Does anyone have any clue how I can fix this?
Operating system the target node is running
OsName               : Microsoft Windows Server 2016 Datacenter
OsOperatingSystemSKU : DatacenterServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 14393.5192.amd64fre.rs1_release.220610-1622
OsLanguage           : en-US
OsMuiLanguages       : {en-US}

PowerShell version and build the target node is running
Name                           Value
----                           -----
PSVersion                      5.1.14393.5127
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.5127
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

ActiveDirectoryDsc version
ActiveDirectoryDsc 6.2.0   C:\Program Files\WindowsPowerShell\Modules\ActiveDirectoryDsc\ActiveDirectoryDsc.psd1

I have same issues as you do,. This is not only related to ActiveDirectoryDSC, got same issues with WapConfiguration, ADFS etc. I had to go back to last month image.

Join the #dsc channel, there are mentioned on similar there: https://dsccommunity.org/community/contact/

We are having the same problem with customers using new 2016-Datacenter images on azure.  We narrowed it down to the latest version (14393.5192.220612).  The previous version (14393.5125.220505) continues to work.  We dont yet know which KB in that release is causing it.

Same problem occurs on Windows Server 2022 Datacenter running 10.0.20348.643. Removing KB5014678 fixes the The password cannot be null or empty issue observed.

Suggest open a support case with MS.
Also join the community channel mentioned above, and talk to others having the same issue. @mgreenegit is also in the community channel and have seen that there is an issue for users.

Just happened upon this issue while looking for something else. I also experienced this issue and have confirmed that the issue has been resolved with one of the updates released yesterday.
Cc: @mgreenegit

The Azure DevOps build workers has gotten the patch now, that means that this issue is fixed . Closing this.


Translate /docs/configuration in Korean

/kind translation
/area documentation
https://falco.org/docs/configuration/
https://github.com/falcosecurity/falco-website/issues

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign radhikapc
You can assign the PR to them by writing /assign @radhikapc in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

configuration 항목에 필요한 추가 파일도 번역하였습니다.

@jmyung @futureCreator  리뷰 부탁드립니다.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml
ff7b716 Update configuration.md
447558f Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml
ff7b716 Update configuration.md
447558f Update config.yaml
056a675 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml
ff7b716 Update configuration.md
447558f Update config.yaml
056a675 Update config.yaml
f6afb38 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml
ff7b716 Update configuration.md
447558f Update config.yaml
056a675 Update config.yaml
f6afb38 Update config.yaml
ee33283 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

3186224 Update config.yaml
cc1a702 Update configuration.md
3d723d2 Update config.yaml
60269fd Update config.yaml
ff7b716 Update configuration.md
447558f Update config.yaml
056a675 Update config.yaml
f6afb38 Update config.yaml
ee33283 Update config.yaml
9a76d75 Update config.yaml

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/assign

@bluefriday
그런데 이미 #279 에 PR이 올라온 게 있네요.
확인 부탁드립니다 🙏


[Quote] Hanging quote and general alignment

User Story

The specs state that the starting quote should hang off the left of the column, and all other text should be aligned to the column.

Currently, the Quote component does not hang the starting quotation mark on the left side of the column. The starting quote is aligned to the column, and all other text is inset within the column structure.

Question:
Is it possible for the starting quote to hang to the left of the column?

If yes, this can be a development story
If not, we may need to update the visual specs, or a combination of spec + dev updates to achieve the desired outcome.

Additional information

Discovered this during our clean up
Potentially affects Call out quote specs

Acceptance criteria

[ ] Dev & design collaboration to understand how to achieve desired design intent
[ ] Specs and/or story updated
[ ] Dev and design review

@oliviaflory
I've opened a PR to address this issue.

Also noticed Callout component could need some update to maintain the changing quote.


preselectedOptionIndex on checkbox causes unintended selection when navigating in apps

Description
The preselectedOptionIndex property on checkboxes may cause unintended selections when navigating in an app. For example, if we have a list of optional checkboxes, and we dont want to select any of the options, we can uncheck them all. If the user navigates to next page, and back again, the checkboxes will automatically select the preselectedOptionIndex again.
The user might not notice this and the form will be submitted with incorrect information.
To Reproduce
(app with repro: https://dev.altinn.studio/repos/haakemon/ui-components/src/branch/bug-checkbox-multi-pages-initial-value )

Create a app with 2 pages
Add checkboxes on page 1, and set a preselectedOptionIndex.
Start the app, and go to page 1. Untick all checkboxes
Navigate to page 2
Navigate back to page 1, observe the checkbox will now have selected the default value again

There is an additional bug with checkboxes and preselectedOptionIndex, where you are currently unable to deselect that checkbox at all, since on every render, it will select the checkbox automatically. This is being fixed as part of Altinn/altinn-studio#7464
Expected behavior
The checkbox should not select the default value when navigating back
Additional info
I'm not sure if theres any good way to solve this, or if its possible to solve at all with the current architecture.
No production apps (as per this list in November 2021) are using this property, so we could consider to remove it entirely. This property also does not cover all usecases, f.ex you cannot have multiple preselected values.
App authors can anyway solve the preselecting of data by setting the form data to the wanted values during instantiation, or prefill.

Multiple apps in production now uses this functionality, especially fufinn-behovsendring. I also noticed a need for improving this functionality when debugging Altinn/altinn-studio#8255. Maybe triggering this functionality should be moved out from the component, if possible. The way it is implemented now means the component will re-render itself after the first render where it has options (but none has been selected). In the mentioned issue, multiple levels of this leads to unnecessary requests (I haven't fixed that part, as it's not a breaking bug). When the added complexity of dependencies taken into account, solving this in the frontend in a way that avoid re-renders and useless requests quickly becomes unbearable, and not really worth the effort to do properly for what it brings to the table, IMO.

As so many other issues, this related to:

#377
#345
#555

With #555 an app-developer could implement support for this behavior in repeating groups via ProcessDataWrite (by automatically selecting an option for new rows), and for data outside repeating groups, it is already possible with a prefill. In order to fix this problem while maintaining the functionality, we would need some way to indicate (outside the data model!) that the user made a conscious choice to revert our pre-selection and go back to a neutral state. In addition to that, the feature relies on an index inside the options, not a value, making it very fickle in cases where you don't know the order of options returned.
TL;DR: Let's implement #555, deprecate and remove the feature instead. Bat-signalling #339!


[iOS] Create SessionDetail UI

Idea Description

Please implement SessionDetail UI to SessionView.

Preview only is okey.
Some actions from this view aren't included in this issue.

Reference images and links
https://www.figma.com/file/NcSMs6dMsD88d4wOY0g3rK/DroidKaigi-2022-Conference-App?node-id=21%3A583

I would like to attempt this 🤚 🙇♂

Thanks! Assigned :+1:


Organizing selectors

I've started using selectors to slice the store whenever I pull out something from it. For instance:
store.select(s => s.auth.current) becomes store.select(fromApp.getAuthCurrent)
Where fromApp is an import * as fromApp 'path/to/root/reducer/barrel. This is by example of the great example app.
Now, getAuthCurrent is actually a composition of getAuthState (from root selectors) and getCurrent (from auth selectors). That composition is done in the root reducer folder's index.ts barrel because otherwise I'd have to import the root selectors in my feature and I would import them in feature module's selectors.
What I'm struggling to understand is whether doing e.g.:
store.select(fromApp.getAuthState).select(fromAuth.getCurrent)
is something that makes sense? It seems to somewhat defiy the purpose of selectors.
So the main question is this: how do you organize selectors, on root/app level and feature level, how do you compose them and where do you compose them?

The example app provides some guidance on selectors. You keep selectors for a reducer in the same place. You compose selectors in a feature area in the place. Then you compose them in your root reducer file to expose them as the "public api". Instead of chaining two select statements, you'd have a selector for auth state, and a selector for current that composes auth state and gets the current based on its selection.
Hope this helps.


Trouble building the VTK app

Once again I'm on Ubuntu 13.10 64 bit. I have these libs installed from the 13.10 repos:
libvtk5-dev
libqt4-dev

Here are the errors I get on cmake:
moorepants@moorepants-2170p:build-with-vtk(docs)$ cmake \
>    -DCMAKE_BUILD_TYPE:CHAR=Release \
>    -DBUILD_SHARED_LIBS:BOOL=1 \
>    -DBTK_WRAP_PYTHON:BOOL=1 \
>    -DBTK_WRAP_OCTAVE:BOOL=1 \
>    -DBUILD_TESTING:BOOL=1 \
>    -DBTK_TESTING_DATA_PATH:CHAR=~/Data/BTKData \
>    -DBTK_EXTRA_COMPILER_WARNINGS:BOOL=1 \
>    -DBUILD_DOCUMENTATION:BOOL=1 \
>    -DBUILD_DOCUMENTATION_API:BOOL=1 \
>    -DBUILD_DOCUMENTATION_API_UNSELECTED_MODULES:BOOL=1 \
>    -DBUILD_EXAMPLES:BOOL=1 \
>    -DPYTHON_LIBRARY:CHAR=/usr/lib/x86_64-linux-gnu/libpython2.7.so \
>    -DPYTHON_INCLUDE_DIR:CHAR=/usr/include/python2.7 \
>    -DBTK_USE_VISSUPPORT:BOOL=1 \
>    -DBTK_USE_VTK:BOOL=1 \
>    -DBUILD_TOOLS:BOOL=1 \
>    -G "Unix Makefiles" ..
-- The imported target "vtkParseJava" references the file
   "/usr/bin/vtkParseJava"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkWrapJava" references the file
   "/usr/bin/vtkWrapJava"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkCommonJava" references the file
   "/usr/lib/jni/libvtkCommonJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkFilteringJava" references the file
   "/usr/lib/jni/libvtkFilteringJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkImagingJava" references the file
   "/usr/lib/jni/libvtkImagingJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkGraphicsJava" references the file
   "/usr/lib/jni/libvtkGraphicsJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkGenericFilteringJava" references the file
   "/usr/lib/jni/libvtkGenericFilteringJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkIOJava" references the file
   "/usr/lib/jni/libvtkIOJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkRenderingJava" references the file
   "/usr/lib/jni/libvtkRenderingJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkVolumeRenderingJava" references the file
   "/usr/lib/jni/libvtkVolumeRenderingJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkHybridJava" references the file
   "/usr/lib/jni/libvtkHybridJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkWidgetsJava" references the file
   "/usr/lib/jni/libvtkWidgetsJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkParallelJava" references the file
   "/usr/lib/jni/libvtkParallelJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkInfovisJava" references the file
   "/usr/lib/jni/libvtkInfovisJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkGeovisJava" references the file
   "/usr/lib/jni/libvtkGeovisJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkViewsJava" references the file
   "/usr/lib/jni/libvtkViewsJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkQtChart" references the file
   "/usr/lib/libvtkQtChart.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "QVTK" references the file
   "/usr/lib/libQVTK.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtkChartsJava" references the file
   "/usr/lib/jni/libvtkChartsJava.so.5.8.0"
but this file does not exist.  Possible reasons include:
* The file was deleted, renamed, or moved to another location.
* An install or uninstall procedure did not complete successfully.
* The installation package was faulty and contained
   "/usr/lib/vtk-5.8/VTKTargets.cmake"
but not all the files it references.

-- WARNING: Even if the code works with VTK 5.8, small glitches are visible in charts (e.g. the first item plotted has for effect to initially display the boundaries in Mokka). It is advised to compile Mokka with VTK 5.10 or greater
-- Found Freetype: /usr/lib/x86_64-linux-gnu/libfreetype.so (found version "2.4.12")
-- Looking for Q_WS_X11
-- Looking for Q_WS_X11 - found
-- Looking for Q_WS_WIN
-- Looking for Q_WS_WIN - not found
-- Looking for Q_WS_QWS
-- Looking for Q_WS_QWS - not found
-- Looking for Q_WS_MAC
-- Looking for Q_WS_MAC - not found
CMake Error at /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:108 (message):
  Could NOT find Qt4 (missing: QT_MOC_EXECUTABLE QT_UIC_EXECUTABLE) (found
  version "4.8.4")
Call Stack (most recent call first):
  /usr/share/cmake-2.8/Modules/FindPackageHandleStandardArgs.cmake:315 (_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-2.8/Modules/FindQt4.cmake:1389 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  Code/VisSupport/VTK/CMakeLists.txt:40 (FIND_PACKAGE)

-- Configuring incomplete, errors occurred!

Where do I find the exact dependencies needed for building the visual apps?

The imported target "vtkQtChart" references the file "/usr/lib/libvtkQtChart.so.5.8.0" [...]
Try command 'sudo apt-get install libvtk5.8-qt' to solve it.


Provide users an "Contact us" button

Users need a way to contact our support team from within the app.
The support team is using Zendesk to respond to user requests. They have created a dedicated support email for Saturn users. We also want to provide a button within the app from which users can email help.
We need to design the affordances for emailing help and integrate Zendesk's prebuilt solution. From what Geraldine has told me, this should be able to automatically capture information like console errors. See Brad to take a look at the support team's Zendesk rollout plan.
There is an affordance in current mocks for "report a bug". I think this should be a more general "Contact us", but I'm happy to listen to arguments here.
https://projects.invisionapp.com/d/main#/console/13746874/286545629/preview

Check in with Comms to see if this is blocked on them

This is no longer blocked by #740

Default fields are name, email, "how can we help you", and attachments. You can create custom fields.
Kate added a subject field (bug, feature request, etc). I think we'll want to keep that, since the comms flow that Ilyana showed me has some branches that hinge on these categories.
I think we can suppress name and email since we have those from the logged in user. We can surface email if people tell us they want a different one (we do make it possible on registration for users to provide a "contact email" instead of the user id. THAT'S the one we should be using).
I think we should suppress attachments. I imagine we'll want to scrape things like any console errors.

Based on the general support flowchart, I'm suggesting we capture the request type (bug, feature request, general question, documentation request), "how can we help you", and scrape any console errors.
We should plug the email in automatically as the user's sam contact email (NOT the login ID). If that's not possible, we should include an "email" field defaulted with login ID.

[ ] add Contact Us to left main navigation
[ ] use ? help icon
[ ] form is blue from the Workspace nav
[ ] text on form and buttons is white
[ ] add subject field: Question, Feature Request, Documentation Request, Bug (default)
[ ] form pops up in righthand corner
[ ] Scrape console errors
[ ] include user's current page
[ ] auto-fill user's contact email, if none then login email
[ ] invisibly include user's name

Browser support: @bradtaylor what browsers do we want to make sure Terra works well on? How many versions?
Within Zendesk ticket forms when a field in the form is required, it does not work in Safari. I haven't investigated more but it sounds like a user in Safari can submit a form without all of the required fields. I'm assuming Safari is a required browser.

Fields:

[ ] hidden: name
[ ] email: default contact, login, have option to edit
[ ] description
[ ] type: default Bug, Feature Request, Question
[ ] hidden: console errors
[ ] hidden: page submitted from ("Submitted from: http://localhost:3000/#browse-data")
[ ] hidden: priority (dropdown)
[ ] hidden: theme (text field)
[ ] hidden: user status (dropdown)
[ ] hidden: multiple users affected (checkbox)

The form is set up on the Zendesk side. I am discussing with our Zendesk rep about getting @katevoss set up as a developer in our system, and will let you know when I have more info. In the meantime, let me know if there's anything I can help with.

@katevoss Chrome is required. I'm not sure our level of browser support for Safari, IE. @panentheos @zarsky-broad can you comment?
We need this very soon, so let's roll it out and worry about browser support as followup

Currently Chrome or FF (though I don't know how much FF testing we actually do). Safari and IE are generally lagging and/or broken and should be considered nice-to-have for now.

@knoblett something to consider, should we have a dev instance of Zendesk set up so that when our team is testing things out that we won't be sending emails and tickets to the official prod version of Zendesk?
Also, I hit a rate limit of the number of requests to create a ticket. Do you know if there is a limit in production for how many times we can create requests? I can look into it but I wasn't sure if you'd heard anything from sales at Zendesk.

Some info from Zendesk on our API rate limit: https://develop.zendesk.com/hc/en-us/articles/360001068967--API-UPDATE-Account-wide-API-rate-limit-rollout

Yes; That would be a good idea to use a dev instance of Zendesk for testing. We can do it for free for as long as your trial will last, but long-term it would be better from a financial aspect to work in the main Zendesk we have. If the latter is the case, let me know and I will communicate it to our support agents so they'll be able to distinguish between real requests and test requests.
Does the link you put in about APIs answer your question? If not, I can introduce you to Hunter, our Zendesk rep, to get that question answered.

@bradtaylor We have an opportunity for a cute, whimsical, pleasant message once a user submits a support request.
Something like:

Successfully sent. Our elves will get back to you shortly.

or

All done! Check your email to update your support request.

Thanks for contacting us. We'll get back to you soon.

Success! We will be in touch by email.

Success! We'll put Terry on the case!

What do you think?


Print user-friendly error if internet is down

Yesterday my internet seemed very slow so I used speed-test to test it. It seemed my internet connection was down entirely and it couldn't reach the speed-test servers.
{ [Error: getaddrinfo ENOTFOUND www.speedtest.net www.speedtest.net:80]
  code: 'ENOTFOUND',
  errno: 'ENOTFOUND',
  syscall: 'getaddrinfo',
  hostname: 'www.speedtest.net',
  host: 'www.speedtest.net',
  port: 80 }

So I thought it would be a good idea to show a more user-friendly error if this happens. Feel free to suggest another error message or to not merge at all :).

Good idea! I'm always super happy about making things more user-friendly. Please do open issues on my other projects too if you notice anything that could be more user-friendly ;)

Thanks Sam :)

just wondering, why was this PR closed? kind of discouraging for future contributions if there is no feedback on why it was rejected

@vasco3 Look at the commit log: https://github.com/sindresorhus/speed-test/commits/master I just manually squashed and merged it to keep a clean commit history.

Also, see the above:

No problem! Always happy to contribute to your repos ;) :beers:

oh ok thanks :)


[cert-manager-1.14] Cherry-pick of commits from master

Pull changes from master branch.
TODO:

[ ] o/release PR to update test changes on this branch to enable FIPS: https://github.com/openshift/release/pull/52639

/label tide/merge-method-rebase

/test unit

/lgtm
/approve

/label qe-approved
/label px-approved
/label docs-approved
This is just a cherry-pick PR.


dash-dot line with anti-aliasing problem

The dash-dots spacing is reduced when exporting with export_fig, (using -a2 option for example). It makes it very ugly.
myaa has the same issue.
Tested on Matlab 2014a and 2014b with HG2, on Windows 8 64bit
(I'm looking for a way to export anti-aliased graphics containing lines and surf at the same time. Not that easy...)

r=100;
theta = linspace(0,2*pi,100);
[x,y] = pol2cart(theta,r*ones(1,100));
[x1,y1] = pol2cart(theta,0.9*r*ones(1,100));

rc = 0.1;
h = 0.3;
m = h/rc;
[R,A] = meshgrid(-linspace(0,rc,11),linspace(0,2*pi,50));
X3 = R .* cos(A)*r;
Y3 = R .* sin(A)*r;
Z3 = -(m*R+h)*r;

hold on
plot(x,y)
plot(x1,y1,'-.')

%plots are with anti-aliasing
s = surf(X3,Y3,Z3)
s.FaceLighting = 'gouraud';
s.AmbientStrength = 0.6;
s.DiffuseStrength = 0.8;
s.SpecularStrength = 0.9;
s.SpecularExponent = 25;
s.BackFaceLighting = 'reverselit';
s.FaceColor=[0.25 0.25 0.25];
set(s,'FaceAlpha',0.3);
set(s,'EdgeAlpha',0);

view(2)
%anti-aliasing is gone...

[filename, pathname] = uiputfile({'*.png';'*.tiff';'*.jpg';'*.pdf'}, 'Save as');
export_fig([pathname filename],'-a2');

I believe that this is due to an internal Matlab bug in the OpenGL renderer, as can be seen by running the builtin print command. If you run export_fig(..., '-painters') you should see better results (and much smaller output files).
I'm closing this issue since I do not think there is any feasible workaround for this. If you (or anyone else) think otherwise, please let me know and I'll review it.


Pretty Good Ground State Computation

During the construction of Isomtetry, we will need the ground state for a hamiltonian. The problems are

Single site methods don't converge well enough
Double site methods cannot retrieve single site InfiniteMPS
Symmetry encoded state cannot be put back to regualr InfiniteMPS easily.

Do we have to settle for a pretty good ground state?

They used sublattice rotation.


⚠ Samsung has degraded performance

In 2b54915, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2560 ms

Resolved: Samsung performance has improved in e5c72f6.


Fixed #25196 -- Normalized database representations in test database messages.

https://code.djangoproject.com/ticket/25196

merged in afe777639cc1c591df32591e196d4cda5783c615, thanks!


Space should dismiss auto complete

This looks like it might be fixed with the latest auto complete changes.

fixed in https://github.com/OmniSharp/omnisharp-atom/pull/222


Unable unlock randomally

Unable unlock randomally.
In the logs i only read :
Attempting facial authentication for user MYUSER
The camera is on and it remains on.
I can't read
login approved
I have to a hard reboot.
There aren't errors in logs.
It has a random behaviour.
When there aren't errors is the worse way for to diagnostic a bug.
What happens?

What version of Howdy are you on (sudo howdy version) and what distro?

What version of Howdy are you on (sudo howdy version) and what distro?

Howdy 2.6.0
Void Linux
It stucks randomally on this line in pam.py
# Run compare as python3 subprocess to circumvent python version and import issues
status = subprocess.call(["/usr/bin/python3", os.path.dirname(os.path.abspath(__file__)) + "/compare.py", pamh.get_user()])

If this you can help

That line is basically what executes the entire program (calling the core script) so no surprises there. Does it happen in different lighting environments?

That line is basically what executes the entire program (calling the core script) so no surprises there. Does it happen in different lighting environments?

Before to insert howdy authentication in important  pam file , i tried to put it in sudo file (/etc/pam.d/sudo) for testing it.
Initially it works fine, then
Suddenly, after sudo command,  it remains blocked with led camera on and in log file i see "[HOWDY] Attempting facial authentication for user". I need to kill process to unblock it.

Are there any errors in /var/log/apache2/error.log?

I see in log file only following lines without errors:
2020-08-11T16:02:14.70687 auth.emerg: Aug 11 18:02:14 sudo: [HOWDY] Attempting facial authentication for user MYUSER

I haven't apache installed.
When there aren't errors , it more difficult to find a workaround

Sorry, i mentioned the wrong log file, should have been /var/log/auth.log

Perhaps i found the problem. I added howdy in the /etc/pam.d/other file, for the screen locker (KDE).
I think that it is wrong. I moved that in /etc/pan.d/kde and it seems works fine.
Anyway, I'll test it for some days, if it works fine then I'll close this issue.

I spoke too soon. Suddenly it stops with the LED camera on. On archlinux it works fine. I checked all packages and related versions. I don't understand because itself blocks

I added howdy in the following files:
/etc/pam.d/sudo
/etc/pam.d/sddm  (login)
/etc/pam.d/kde      (screenlocker)
It works fine but suddenly i get this error:
(python3:5308): GStreamer-CRITICAL **: 14:25:43.249:
Trying to dispose element pipeline0, but it is in READY instead of the NULL state.
You need to explicitly set elements to the NULL state before
dropping the final reference, to allow them to clean up.
This problem may also be caused by a refcounting bug in the
application or some element.


[doc] Fix burn-tch doc for burn crate

Checklist

[x] Confirmed that run-checks all script has been executed.
[x] Made sure the book is up to date with changes in this PR.

Changes
Set the correct feature for docs build.

Switching to draft.
This requires more thoughts than expected.

Not completely sure about this but this is an attempt to add the basis to make enabled features during docs.rs builds more explicit.

Removed


proposed HCLS changes

@Doix OK still some things in HCLS breaking that I think might need changed in either the schema or the data

The changes look good to me. Feel free to merge.

Merging so I can get started on requirement levels. There will need to be a complete review of the schema at some point, may as well do that after we add the req_lev's


⚠ Secret Website 3 has degraded performance

In e1c74ce, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 3302 ms

Resolved: Secret Website 3 performance has improved in c5b277b.


Convert whole folder of C code

Do you want to add the function that can convert whole folder of spcified programming language code?I demanded that because I want to translate binutils to another programming language.It is too large that cannot be converted in the website's tiny text frame.Do you want to dispark the API that can be used for massive code converting?

Hello @TYDQSoft ,
Unfortunately, there is currently no plan to do this. You will have to code it yourself or find another tools that already support this
Best Regards,
Jon


Add some default context values and benchmark metadata

The contextual struct is so far empty - everything is opt-in. That's cool, but some things are just so common that they might be useful to include by default.
Ideas:

[x] Datetime for the start of the benchmark run.
[x] Elapsed wall time (measured e.g. by time.perf_counter_ns()).
[x] git SHA / tag of the current project if in a repository.
[x] Version info of installed popular SciComp packages (TF, PyTorch, NumPy, JAX, ...).
[x] Maybe even sysinfo? (GBM does this)

And as for the benchmark JSON:

[x] Standardize error_occurred and error_message to also be included on success (but empty) to stabilize the schema (though we should take care to not print them to the console when everything went fine).
[x] Include description key containing Benchmark.fn.__doc__ (might even be worth saving as a toplevel member like Benchmark.description()?)
[x] Include fn key with the fully qualified function name (i.e. f"{fn.__qualname__}.{fn.__name__}").

The remaining context providers were added in #64.
A follow-up will be done on deciding how to nest semantically similar values.


Support citext

Motivation
citext is a popular extension and when enabled, seaography thinks it's an enum an generates invalid code
Proposed Solutions
Recognise that citext is pretty much like Text for all purposes that matter for client code. Maybe just an alias?
Additional Information
This is the code generated, which is wrong:
#[derive(
    Debug,
    Clone,
    PartialEq,
    EnumIter,
    DeriveActiveEnum,
    Eq,
    Copy,
    async_graphql::Enum,
    seaography::macros::EnumFilter,
)]
#[sea_orm(rs_type = "String", db_type = "Enum", enum_name = "citext")]
pub enum Citext {}

sqlx doesn't support citext easily either as per https://github.com/launchbadge/sqlx/issues/295. However, I don't know if seaorm/seaography could do something about it

@cortopy I rely on https://github.com/SeaQL/sea-orm to generate the entities. After a quick look I found it is related to this file https://github.com/SeaQL/sea-orm/blob/master/sea-orm-codegen/src/entity/transformer.rs#L62

Hey @cortopy, could you illustrate the use case of citext? I'm not super familiar with it. Thanks!!

@billy1624 it is a plugin for PostgreSQL, that provides a new data type citext that the SQL database treats a column as a case insensitive string. More info here https://www.postgresql.org/docs/current/citext.html

@karatakis that's exactly it. The citext type is provided natively by postgres, so all it takes to enable is CREATE EXTENSION citext.
Seaography currently thinks that citext is an enum type, while for all purposes, it's just  the same as text.
I've been looking a bit more on seaorm and I think the issue also stems from the limited support there for user types. It seems that only enum user types are supported, but in postgres not all user types are  enums. There are also composite, range, extension-enabled, etc.
So anybody using any other type will get an enum generated that is just not right.

Can we represent citext as String in Rust?

I'd say so yes

Alright, then it's more related to sea-schema. https://github.com/SeaQL/sea-schema/issues/89
I'll keep this issue open until it has been solved

I've managed to support citext in SeaORM. Please check https://github.com/SeaQL/sea-orm/pull/1304

This issue is not present in #114, wait for 1.0.0 release :)


Bloc error

taxi_booking_bloc.dart
The superclass 'Bloc<TaxiBookingEvent, TaxiBookingState>' doesn't have a zero argument constructor.
Try declaring a zero argument constructor in 'Bloc<TaxiBookingEvent, TaxiBookingState>', or declaring a constructor in TaxiBookingBloc that explicitly invokes a constructor in 'Bloc<TaxiBookingEvent, TaxiBookingState>'.dart(no_default_super_constructor)

cupertino_icons: ^1.0.2
google_maps_flutter: ^2.0.3
flutter_bloc: ^7.0.0
bloc: ^7.0.0
equatable: ^2.0.0
shimmer: ^2.0.0
location: ^4.1.1

It give me not Insilized


Auto resize custom class category icon in inspector.

Before:

After:

Fixed #68962.

Same as https://github.com/godotengine/godot/pull/71818, I'm not sure why we resize when we can just render it at the size we want.

Same as #71818, I'm not sure why we resize when we can just render it at the size we want.

To keep discussion in one where, I describe my opnion at here.

Thanks for your contribution! I've incorporated all your work in https://github.com/godotengine/godot/pull/75472, so this is superseded now. You are properly credited in the relevant commit.


Docusaurus 2, cleanUrl false and deployment to google cloud

In the migration guide you wrote that cleanUrl option is removed and it is true now by default. That means, all urls have no .html extension ending. And that is a big problem for us)
The problem, is that our documentation is deploying as a static assets to Google Cloud Storage (https://storage.googleapis.com ...). That means, clean request cannot be redirected to dirty request, and after reloading any page we have this type of error:
<Error>
NoSuchKey
<Message>The specified key does not exist.</Message>

No such object: ...

</Error>

That happens because my-document-url is not the same object as my-document-url.html, from google's point of view.
Is it possible to override cleanUrl to false somehow in docusaurus 2?

We can't disable it, because its utilizing client side routing.
Create a redirect plugin like this
https://github.com/CanopyTax/single-spa.js.org/blob/master/website/src/plugins/docusaurus-plugin-redirects/src/index.js
https://github.com/CanopyTax/single-spa.js.org/blob/d1a69e197615fce069184b7e1634770db38eefb9/website/docusaurus.config.js#L116-L123

Thanks! But Im not sure I understand your advice.
I cannot create file my-document-url which could redirect to my-document-url/index.html, because of two reasons:

my-document-url directory already exists, and I cannot place file with the same name
When I enter my-document-url/index.html in the browser, docusaurus replaces the actual content, loaded from server, with Page Not Found (probably because in terms of docusaurus, route my-document-url/index.html does not exists).

Aha, seems that I misunderstood you previously.
Re-reading “That happens because my-document-url is not the same object as my-document-url.html, from google's point of view.” made me understand.
Its kinda a weird behavior by google though because usually most sites fallback to html or at least index.html
Hmmm.. Is there any way to redirect in the host u are using ? Such as accessing 404 get redirected to index.html for example

That is possible, but our devops assured us that it is only available for buckets, which have cname. We are using https://storage.googleapis.com/ domain directly, so, looks like in our case it is impossible.

Pretty sure there must be a way in which
you need to set a situation such that if a user requests the URL http://www.example.com/directory, it attempts to serve the file www.example.com/directory/index.html.
I dont know much abt google storage apis but its most likely web server configuration issue (?)
On the other hand, it will be nice if we can add cleanUrl false. But its a design decision back then and its not possible atm. That would requires lot of changes in our code and is definitely not the highest priority now

Why not use zeit or netlify or even gh pages. Its a great solution too

I ran into a similar situation. I'm currently using V1 of Docusaurus and for deployment I use AWS services (S3 + CloudFront).
The problem is that when the static site assets are deployed to AWS S3 bucket, you'll have to send a request for an exact path of an object (i.e. a file). It doesn't work like a traditional web server where you're automatically redirected to "index.html".
In my case, I've setup a AWS Lambda function attached to AWS CloudFront. Before AWS CloudFront (a CDN) tries to fetch an object from AWS S3 storage, the Lambda function inspects the requested URL and changes it include "/index.html" at the end, if needed; basically tries to mimic a regular web server.
I haven't dealt with Google Cloud yet, but I believe you can do something like this using Google Cloud Function. Pretty much all the cloud providers these days provides serverless functionality.
Hope that helps.

@amimas thanks for your reply. You're mentioning a Lambda function you are using:

In my case, I've setup a AWS Lambda function attached to AWS CloudFront. Before AWS CloudFront (a CDN) tries to fetch an object from AWS S3 storage, the Lambda function inspects the requested URL and changes it include "/index.html" at the end, if needed; basically tries to mimic a regular web server.

Are you willing to share that? I have the same setup and this would solve my problem.
Thanks

@joeplaa glad you found a pointer to get started. In case it helps, you can also deploy the following directly from aws lambda. The concept is the same.
https://serverlessrepo.aws.amazon.com/applications/arn:aws:serverlessrepo:us-east-1:621073008195:applications~standard-redirects-for-cloudfront


Exiting full screen on Mojave renders MacVim window empty - must be refreshed with CTRL+l

I am using MacVim compiled on macOS High Sierra with Xcode 9.3 on macOS Mojave. When exiting native full screen, MacVim window is rendered empty of contents and needs to be manually refreshed with CTRL+l to fix it.
This is a regression introduced somewhere between 8.1.425 and 8.1.436 (it works in 8.1.425).
VIM - Vi IMproved 8.1 (2018 May 18, compiled Sep 28 2018 12:36:21)
macOS version
Included patches: 1-436
Compiled by Mario Grgic
Huge version with MacVim GUI.   I know, this is a workaround, and don't solve the issue itself.
autocmd FocusLost * redraw!
autocmd VimResized * redraw!

@mario-grgic I'm not quite reproducing this. A couple changes are coming though: #745 will be merged soon which will fix a few existing fullscreen oddities (it will actually properly restore its size now), and there's another PR (#757) that aims to fix the Mojave rendering issues, so they have a chance of fixing this issue.
How are you building your MacVim? Do you have any custom settings?

I don't see this in 8.1.500 any more either.