Change from Write-SimpleLogFile to OutputOverrides on Set-ExchAVExclusions

Issue:
move the log function from  Write-SimpleLogFile to OutputOverrides in order to remove Write-SimpleLogFile
Reason:
Simplify the code and use the same function in all scripts
Fix:
Change the functions
Validation:
Test in lab

@iserrano76 please provide a snapshot of your sanity run of the script. Then we can approve and merge.

@iserrano76 please provide a snapshot of your sanity run of the script. Then we can approve and merge.

This is the output of the previous version:

and this one the new output:

and about the log file, this is the one in the previous version:

[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\clientaccess\oab
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\fip-fs
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\groupmetrics
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\logging
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\calendar repair assistant
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\managed folder assistant
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\mailbox
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\connectivity
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\protocollog\smtpreceive
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\protocollog\smtpsend
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\agentlog\submission
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\agentlog\delivery
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\routing
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\throttling\delivery
[1/22/2024 2:17:00 PM] - Adding c:\temp\ews\pipeline
[1/22/2024 2:17:00 PM] - Adding C:\Windows\Temp\OICE_????????-????-????-????-????????????
[1/22/2024 2:17:00 PM] - Adding C:\Windows\Temp\OICE_????????-????-????-????-????????????.?
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\connectivity
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\protocollog\smtpreceive
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\protocollog\smtpsend
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\agentlog
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\routing
[1/22/2024 2:17:00 PM] - Adding c:\inetpub\temp\iis temporary compressed files
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\pop3
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\imap4
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\queue
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\senderreputation
[1/22/2024 2:17:00 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\temp
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\connectivity
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\messagetracking
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\irmlogs
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\activeusersstats
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\serverstats
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\protocollog\smtpreceive
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\routing
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\protocollog\smtpsend
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\queueviewer
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\latencylog
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\generallog
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\wlm
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\agentlog
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\journallog
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\transporthttp
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\pipelinetracing
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\pickup
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\replay
[1/22/2024 2:17:01 PM] - Adding c:\program files\microsoft\exchange server\v15\working\oleconverter
[1/22/2024 2:17:01 PM] - Adding e:\transportroles\data\queue
[1/22/2024 2:17:02 PM] - Adding config
[1/22/2024 2:17:02 PM] - Adding chk
[1/22/2024 2:17:02 PM] - Adding edb
[1/22/2024 2:17:02 PM] - Adding jfm
[1/22/2024 2:17:02 PM] - Adding jrs
[1/22/2024 2:17:02 PM] - Adding log
[1/22/2024 2:17:02 PM] - Adding que
[1/22/2024 2:17:02 PM] - Adding dsc
[1/22/2024 2:17:02 PM] - Adding txt
[1/22/2024 2:17:02 PM] - Adding lzx
[1/22/2024 2:17:03 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\ComplianceAuditService.exe
[1/22/2024 2:17:03 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\fms.exe
[1/22/2024 2:17:03 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe
[1/22/2024 2:17:03 PM] - Adding C:\Windows\System32\inetSrv\inetInfo.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Directory.TopologyService.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.EdgeSyncSvc.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\PopImap\Microsoft.Exchange.Imap4.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PopImap\Microsoft.Exchange.Imap4service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Notifications.Broker.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\PopImap\Microsoft.Exchange.Pop3.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PopImap\Microsoft.Exchange.Pop3service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.RPCClientAccess.Service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Search.Service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Store.Service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Store.Worker.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeCompliance.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeDagMgmt.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeDelivery.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeFrontendTransport.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxAssistants.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxReplication.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeRepl.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeThrottling.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Runtime\1.0\Noderunner.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\OleConverter.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\ParserServer\ParserServer.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\ScanEngineTest.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\ScanningProcess.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\UpdateService.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\wsbExchange.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\EdgeTransport.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.AntispamUpdateSvc.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.ContentFilter.Wrapper.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Diagnostics.Service.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.ProtectedServiceHost.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Servicehost.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMHost.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeTransport.exe
[1/22/2024 2:17:04 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeTransportLogSearch.exe
[1/22/2024 2:17:04 PM] - Exclusions Completed
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\clientaccess\oab
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\fip-fs
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\groupmetrics
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\calendar repair assistant
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\managed folder assistant
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\mailbox
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\connectivity
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\protocollog\smtpreceive
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\protocollog\smtpsend
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\agentlog\submission
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\agentlog\delivery
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\mailbox\routing
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\throttling\delivery
[1/22/2024 4:15:08 PM] - Adding c:\temp\ews\pipeline
[1/22/2024 4:15:08 PM] - Adding C:\Windows\Temp\OICE_????????-????-????-????-????????????
[1/22/2024 4:15:08 PM] - Adding C:\Windows\Temp\OICE_????????-????-????-????-????????????.?
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\connectivity
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\protocollog\smtpreceive
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\protocollog\smtpsend
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\agentlog
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\frontend\routing
[1/22/2024 4:15:08 PM] - Adding c:\inetpub\temp\iis temporary compressed files
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\pop3
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\imap4
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\queue
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\senderreputation
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\data\temp
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\connectivity
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\messagetracking
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\logging\irmlogs
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\activeusersstats
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\serverstats
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\protocollog\smtpreceive
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\routing
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\protocollog\smtpsend
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\queueviewer
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\latencylog
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\generallog
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\wlm
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\agentlog
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\journallog
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\transporthttp
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\logs\hub\pipelinetracing
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\pickup
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\transportroles\replay
[1/22/2024 4:15:08 PM] - Adding c:\program files\microsoft\exchange server\v15\working\oleconverter
[1/22/2024 4:15:08 PM] - Adding e:\transportroles\data\queue
[1/22/2024 4:15:09 PM] - Adding config
[1/22/2024 4:15:09 PM] - Adding chk
[1/22/2024 4:15:09 PM] - Adding edb
[1/22/2024 4:15:09 PM] - Adding jfm
[1/22/2024 4:15:09 PM] - Adding jrs
[1/22/2024 4:15:09 PM] - Adding log
[1/22/2024 4:15:09 PM] - Adding que
[1/22/2024 4:15:09 PM] - Adding dsc
[1/22/2024 4:15:09 PM] - Adding txt
[1/22/2024 4:15:10 PM] - Adding lzx
[1/22/2024 4:15:11 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\ComplianceAuditService.exe
[1/22/2024 4:15:11 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\fms.exe
[1/22/2024 4:15:11 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\HostController\hostcontrollerservice.exe
[1/22/2024 4:15:11 PM] - Adding C:\Windows\System32\inetSrv\inetInfo.exe
[1/22/2024 4:15:11 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Directory.TopologyService.exe
[1/22/2024 4:15:11 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.EdgeSyncSvc.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\PopImap\Microsoft.Exchange.Imap4.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PopImap\Microsoft.Exchange.Imap4service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Notifications.Broker.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\PopImap\Microsoft.Exchange.Pop3.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PopImap\Microsoft.Exchange.Pop3service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.RPCClientAccess.Service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Search.Service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Store.Service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Store.Worker.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeCompliance.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeDagMgmt.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeDelivery.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeFrontendTransport.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxAssistants.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeMailboxReplication.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeRepl.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeThrottling.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\Runtime\1.0\Noderunner.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\OleConverter.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Search\Ceres\ParserServer\ParserServer.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\ScanEngineTest.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\ScanningProcess.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\FIP-FS\Bin\UpdateService.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\wsbExchange.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\EdgeTransport.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.AntispamUpdateSvc.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\Microsoft.Exchange.ContentFilter.Wrapper.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Diagnostics.Service.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.ProtectedServiceHost.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\Microsoft.Exchange.Servicehost.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMHost.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeTransport.exe
[1/22/2024 4:15:12 PM] - Adding C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeTransportLogSearch.exe
[1/22/2024 4:15:12 PM] - Exclusions Completed

and this is the one for the new version:

[01/22/2024 16:15:12] : Starting Logger Instance 01/22/2024 16:15:12
[01/22/2024 16:15:12] : Set-ExchAVExclusions.ps1 script version <IP_ADDRESS>2
[01/22/2024 16:15:12] : WARNING: This script appears to be an unsigned test build.


[#5958] Dependency cleanup

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@e4177db). Click here to learn what that means.
The diff coverage is 23.52%.

@@            Coverage Diff            @@
##             master    #5968   +/-   ##
=========================================
  Coverage          ?   41.01%
=========================================
  Files             ?     3010
  Lines             ?    90656
  Branches          ?    11867
=========================================
  Hits              ?    37185
  Misses            ?    50238
  Partials          ?     3233

Impacted Files
Coverage Δ

...tstrap/agentdir/AgentDirBaseClassPathResolver.java
52.25% <0%> (ø)

...vercorp/pinpoint/bootstrap/agentdir/FileUtils.java
26.53% <22.5%> (ø)

.../navercorp/pinpoint/bootstrap/agentdir/Assert.java
40% <40%> (ø)

...navercorp/pinpoint/bootstrap/agentdir/BootDir.java
72% <50%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e4177db...f230e7d. Read the comment docs.


Can't find Promise.cast() method in this DOCs

Something wrong with that method?

Promise.cast() has been deprecated for a long time now, ever since ES6 decided to drop it. You should switch to Promise.resolve() for all your casting needs

Could I add this to: http://bluebirdjs.com/docs/deprecated-apis.html?
There is still documentation, tutorials etc out there that use .cast which makes things complicated for those who do not have this context (like me, 5 minutes ago)
The Promise.cast function is still an alias in the latest code base aswell
https://github.com/petkaantonov/bluebird/blob/master/src/promise.js#L191


Set X-XSRF-TOKEN manually in header, should override default

When I try to set the header "X-XSRF-TOKEN" it is overridden by the default.
// `xsrfHeaderName` is the name of the http header that carries the xsrf token value
xsrfHeaderName: 'X-XSRF-TOKEN', // default

It is pretty smart that it can autofetch, but if we don't want this, it should respect the headers set, and overriden any defaults.
I also tried setting xsrfHeaderName to null but that will cause a header of null to be sent

Are you setting the header manually with the request?
axios.get('/some/path', {
  headers: {
    'X-XSRF-TOKEN': 'foobar'
  }
});

Closing this due to inactivity. Please feel free to reopen if needed.


Color issues when theme is Light or Dark Modern, or unset

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: Version: 1.78.2 (Universal) Commit: b3e4e68a0bc097f0ae7907b217c1119af9e03435
OS Version: macOS 13.3.1 (a) (22E772610a)

Steps to Reproduce:

Set workbench.colorCustomizations.foreground to "#ff0000"
Set workbench.colorCustomizations.editorWidget.background to "#ff0000"
Set the theme to either Light Modern or Dark Modern, OR delete the workbench.colorTheme setting completely

Expected Behaviour
The appropriate color customisations take affect.
Actual Behaviour
Some UI elements revert to some default color and customisations do not take affect.

Hey @aeschli!

Some themes, such as Dark/Light Modern define that color, some not.

Are you saying that the .colorCustomizations: {...} is not a override on whatever theme I'm seting at .colorTheme? 🤔

For the quick pick foreground we first look at the color quickInput.foreground. If it's set by the settings, we take that one, if it's set by the theme we take that one. If not define we fall back to foreground. Again we look at the settings first and then the theme.
-> To redefine the quick pick foreground color, you need to set quickInput.foreground

So, why quickInput.foreground if the rest of the control panel styles are mostly drive by list...? 🤔
I also see that when I remove the colorTheme (so, the fallback is Dark Modern if I understand correctly), I still have the foreground set, but label in the side bar default, again, to another color. 😅
I would assume that those base colors are the default, unless something more specific is set, eg. quickInput.foreground over foreground. And in general, colorCustomizations is an override to whatever theme is set. 🤔

So, why quickInput.foreground if the rest of the control panel styles are mostly drive by list...? 🤔

Never mind. I probably remembered that wrong... 😞

Hey @aeschli ,
Could you please clarify this too? Maybe I misunderstand something still. 😓

I also see that when I remove the colorTheme (so, the fallback is Dark Modern if I understand correctly), I still have the foreground set, but labels in the side bar default, again, to another color. 😅

eg. in the Explorer or the Search panel
Thanks!


Demo Kit: Can't navigate from Sample to API reference

Steps to reproduce the problem

Open a sample page. E.g.: https://openui5nightly.hana.ondemand.com/entity/sap.m.ActionSelect/sample/sap.m.sample.ActionSelect
Click on the API Reference button in the header

What is the expected result?
The API reference loads as expected
What happens instead?

Any other information? (attach screenshot if possible)
Reproducible in all browsers.

Sometimes, the API reference page itself fails to display when I click on an item from the tree. It's hard to reproduce though. The above case is always reproducible.

Hello @boghyon ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Diana

I can' reproduce this issue anymore. Not sure what exactly fixed it. This issue can be closed.

Has been fixed as side effect of d9ef949ee799684b62f8ab94adf17c93c4c49e29 . That change has completely disabled the functionality around applyExtensionPoint (which appears in the error stack trace in your screenshot).
I leave this issue nevertheless open as the failure suggests that there are one or even two other issues as well.

Hi, I think we can close it now. The change d9ef949 is not active anymore and the issue cannot be reproduced.


Invalid 404 links for events

Summary
Most links on the event handler topic are 404 pages.
Reproduction Steps
Go here https://guide.pycord.dev/getting-started/more-features
Under event handlers, click on few links. Most redirect to 404 pages. Examples:

https://docs.pycord.dev/en/stable/api.html#discord.Intents
https://docs.pycord.dev/en/stable/api.html#discord.Bot.event
https://docs.pycord.dev/en/stable/api.html#discord.on_member_join

Expected Results
The links should redirect to correct pages
Actual Results
Links are 404 pages
System Information
Chrome
Checklist

[X] I have searched the open issues for duplicates.

Additional Context
No response

Triaging as high prio.
@Pycord-Development/contributors please look into this :)


Add support for Local Machine store

Hi!
I noticed that here the CertOpenSystemStoreA function is used.
Does it mean that win-export-certificate-and-key and mongosh as a whole do not support certificates from the Local Machine store?
See https://docs.microsoft.com/en-us/windows/win32/api/wincrypt/nf-wincrypt-certopensystemstorea :
Remarks
Only current user certificates are accessible using this method, not the local machine store.

Whereas MongoDB checks both Local Machine and Current User stores:
https://github.com/mongodb/mongo/blob/7a68603aed1dd0b75caf0faae3a9986886af0f18/src/mongo/util/net/ssl_manager_windows.cpp#L1196
If so, could you add support for certificates from the Local Machine store?

@ifedotov-re Hello, and thanks for reporting this! What you say makes sense, and I’ve opened https://jira.mongodb.org/browse/MONGOSH-1112 to track this on our side. If you want, you can also take a stab at fixing this yourself.

Does it mean that win-export-certificate-and-key and mongosh as a whole do not support certificates from the Local Machine store?

I guess, yes. That’s not an intentional omission, though.

@ifedotov-re We have released mongosh 1.2.2 with support for this, please feel free to try it out and let us know if everything works as it should!


Extraction list validation

Multiple users of poseidon2 reported issues with the filter file for the extract command. For effective extraction the user has to prepare a perfect (no spelling mistakes, no trailing tabs) list of individual and and group IDs. This is sometimes difficult to achieve.
poseidon2 has no mechanism to check for wrong input - it just silently ignores wrong entries. We should come up with some better feedback in trident.

Hi! To avoid mistakes when creating the filter list, I wrote a short bash script utilising the .fam file. You put in all entities you want to extract and it creates a file with group and individual IDs. Idk if it's useful but it exists :D

Excellent! I closed this issue, because trident now checks for and reports entities (packages, groups, individuals) that do not exist in the repository (-d).
Where exactly does your script fit into the pipeline? I'm just curious if there is something we can do to make data extraction with forge more smooth.

Well it's just very short and simple. You just put in all entities you want to extract (Pop), the path to the fam_file and an output_name. Upon execution the script then prints column 1 and 2 of the fam_file, greps all $POP and saves them in output_name.txt
Then you just use poseidon2 extract output_name.txt <input_package> <output_directory>
I can send it to you if you want

Ah! I see. That is indeed useful for poseidon2 extract and plink extract!
But I think for trident forge it is not necessary, because trident allows to directly list individuals, ja?

Should be. I wrote it before forge was opened for testing, so ;D


Map keeps loading the chunks over and over again from the server

Hello,
I think there is a bug that is causing the browser to keep requesting the chunks/regions from the server in an infinite loop. Here is my network tab of me loading the map and letting it sit there without touching it at all. You can see that there are thousands of web requests and over a GB of data transferred.

Sorry for the extremely delayed reply. This is expected behaviour for Pl3xmap/Squaremap maps (which this map appears to be).
LiveAtlas mirrors Squaremap's mechanism for tile updates, which is to just request all the visible tiles again periodically. This is inherently less efficient then dynmap's approach of flagging individual tiles as needing updates, but Squaremap respects cache headers and will return 304s for unchanged tiles to reduce unneeded bandwidth use. They will still add up significantly over time if players are actively building though, due to the large area each tile covers.
Unfortunately the refresh interval is controlled by map.background-render.interval-seconds in Squaremap's config, and is thus tied to server-side rendering speed. It may be worth asking them to decouple those settings if it is a problem.


(GH-20) Bundle pct-templates with pkg

This PR modifies new.go to read from $CWD/templates by
default, enabling a "ready to go" experience for the PCT LA.
When a user runs pct new --list they will see the default
templates we have elected to ship with the package.
The build scripts have been modified to clone the templates from
puppetlabs/baker-round repo to dist/templates, which will then
be bundled in the archive by goreleaser.

@sanfrancrisko I added a few commits that you can squash into yours. This needs a rebase with main, but I didnt want to rewrite your history

The acceptance test failures will need debugged further: https://github.com/puppetlabs/pdkgo/issues/55
We should not hold up this PR because of those failures, for now.


Cleric and Divine Soul spell list issue

I am doing the classic Tempest 2 + Sorcerer X, but with Divine Soul so I can have spirit guardians. Unfortunately, I cannot select higher level cleric spells for my sorcerer spells because it says I already know all the cleric spells, invalidating Divine Soul cleric spell selection.

There is a checkbox under multiclass to allow re learn spells from other classes


How to start using the remote explorer!?

I'm sorry for my ignorance, but how do I start using the plugin after setting up the configuration file!?

Hi,
After setup the config file, you can go to a file and right-click on it, and select Upload (Alt+U). Also, you can enable auto-upload, then when you change a file, it will be uploaded automatically.


feat(diff) retry on 404s for Konnect events

Retry on 404s if running against Konnect.

Codecov Report
Patch coverage has no change and project coverage change: -0.03 :warning:

Comparison is base (a7cf38f) 35.59% compared to head (20f2dc7) 35.57%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #894      +/-   ##
==========================================
- Coverage   35.59%   35.57%   -0.03%
==========================================
  Files          92       92
  Lines       11273    11280       +7
==========================================
  Hits         4013     4013
- Misses       6867     6874       +7
  Partials      393      393

Impacted Files
Coverage Δ

diff/diff.go
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Per Gabriele this may actually be that we include static IDs in tests, and run duplicates of the test on push and pull_request, and they race to delete. If so we can maybe get rid of one--I'm not sure why we'd need to run both.

Per Gabriele this may actually be that we include static IDs in tests, and run duplicates of the test on push and pull_request, and they race to delete

That sounds like a good approach to not reuse IDs across tests that share an external system
where those IDs are being used. 👍

Closed in favor of https://github.com/Kong/deck/pull/896 to avoid concurrent tests.


Save dispatch attributes in backend controller

This is needed when adding new dispatch attributes. Other backend controllers like payment already have this.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-13965.
Please use this issue to track the state of your pull request.

This change introduces some other problems. If the attribute is already created, things get saved correctly. If you don't have an attribute for the dispatch yet, it will result in endless new attribute entries. This is because the data sent from the server does not match with the mapping in ExtJS - in fact, the answer loses the attributeId and dispatchId.
Since we are implementing a whole new attribute management in Shopware 5.2, we won't fix this issue.

If the new attribute system enables saving of dispatch attributes it is okay for us :+1: Otherwise I could fix this PR. Since you are doing this in the PaymentController, too it might not be too expensive.
See: https://github.com/shopware/shopware/blob/5.1/engine/Shopware/Controllers/Backend/Payment.php#L183 and https://github.com/shopware/shopware/blob/5.1/engine/Shopware/Controllers/Backend/Payment.php#L241

Yup, it will. :-)
Keeping this PR closed. Thank you

I'm really excited about the new attribute management and appreciate platform changes more than new marketing features :+1:


Fixes a segmentation fault error

For some reason i've been getting segmentation faults trying to use the transform method.  It seems to work when you use the transformFile method instead.  I did bring this up on gitter but no one responded. Hope it helps.

Sorry, all tests are passing regardless of assertions in this scenario.  I will close this and put together a proper issue tomorrow.


Is it possible to gather log file and fps when running from C++

First of all, thank you for your amazing work.
From this section:
a log file generated by setting the environment variable DEPTHAI_LEVEL to debug, then running the code and saving the standard output: the tool will parse the log file exactly like it does with the "pipeline_graph run" method, looking for the "Schema dump:" string;

Is the FPS also gathered when reading from the log file?

About the FPS, do you mean the parameter used in a setFps() call for a ColorCamera or a MonoCamera ?
I guess the information appears somewhere in the Schema dump printed in the log file but is not easy to retrieve because the parameter is serialized somewhere in the properties.
If I look at the pipeline.txt file you posted here: https://github.com/geaxgx/depthai_pipeline_graph/files/11463879/pipeline.txt , I guess the ColorCamera fps is serialized with other properties of the camera somewhere in the bold part below:
[2023-05-11 19:54:48.121] [debug] Schema dump: {"connections":[{"node1Id":7,"node1Output":"out","node1OutputGroup":"","node2Id":8,"node2Input":"in","node2InputGroup":""},{"node1Id":6,"node1Output":"out","node1OutputGroup":"","node2Id":7,"node2Input":"in","node2InputGroup":""},{"node1Id":5,"node1Output":"manip_img","node1OutputGroup":"io","node2Id":6,"node2Input":"inputImage","node2InputGroup":""},{"node1Id":5,"node1Output":"manip_cfg","node1OutputGroup":"io","node2Id":6,"node2Input":"inputConfig","node2InputGroup":""},{"node1Id":3,"node1Output":"passthrough","node1OutputGroup":"","node2Id":5,"node2Input":"passthrough","node2InputGroup":"io"},{"node1Id":3,"node1Output":"out","node1OutputGroup":"","node2Id":5,"node2Input":"dets_in","node2InputGroup":"io"},{"node1Id":0,"node1Output":"preview","node1OutputGroup":"","node2Id":5,"node2Input":"preview","node2InputGroup":"io"},{"node1Id":3,"node1Output":"out","node1OutputGroup":"","node2Id":4,"node2Input":"in","node2InputGroup":""},{"node1Id":2,"node1Output":"out","node1OutputGroup":"","node2Id":3,"node2Input":"in","node2InputGroup":""},{"node1Id":0,"node1Output":"preview","node1OutputGroup":"","node2Id":2,"node2Input":"inputImage","node2InputGroup":""},{"node1Id":0,"node1Output":"preview","node1OutputGroup":"","node2Id":1,"node2Input":"in","node2InputGroup":""}],"globalProperties":{"calibData":null,"cameraTuningBlobSize":null,"cameraTuningBlobUri":"","leonCssFrequencyHz":700000000.0,"leonMssFrequencyHz":700000000.0,"pipelineName":null,"pipelineVersion":null,"sippBufferSize":18432,"sippDmaBufferSize":16384,"xlinkChunkSize":-1},"nodes":[[0,{"id":0,"ioInfo":[[["","video"],{"blocking":false,"group":"","id":28,"name":"video","queueSize":8,"type":0,"waitForMessage":false}],[["","still"],{"blocking":false,"group":"","id":26,"name":"still","queueSize":8,"type":0,"waitForMessage":false}],[["","isp"],{"blocking":false,"group":"","id":25,"name":"isp","queueSize":8,"type":0,"waitForMessage":false}],[["","preview"],{"blocking":false,"group":"","id":27,"name":"preview","queueSize":8,"type":0,"waitForMessage":false}],[["","raw"],{"blocking":false,"group":"","id":24,"name":"raw","queueSize":8,"type":0,"waitForMessage":false}],[["","frameEvent"],{"blocking":false,"group":"","id":23,"name":"frameEvent","queueSize":8,"type":0,"waitForMessage":false}],[["","inputConfig"],{"blocking":false,"group":"","id":22,"name":"inputConfig","queueSize":8,"type":3,"waitForMessage":false}],[["","inputControl"],{"blocking":true,"group":"","id":21,"name":"inputControl","queueSize":8,"type":3,"waitForMessage":false}]],"name":"ColorCamera","properties":[185,25,185,27,0,3,0,0,0,185,3,0,0,0,185,5,0,0,0,0,0,185,5,0,0,0,0,0,0,0,0,0,0,0,0,185,3,0,0,0,185,3,0,0,0,0,0,0,0,0,0,0,0,0,0,0,189,0,255,1,0,0,129,192,3,129,96,6,255,255,255,255,0,136,0,0,160,64,0,136,0,0,128,191,136,0,0,128,191,1,185,4,0,0,0,0,3,3,4,10,4]}],[1,{"id":1,"ioInfo":[[["","in"],{"blocking":true,"group":"","id":20,"name":"in","queueSize":8,"type":3,"waitForMessage":true}]],"name":"XLinkOut","properties":[185,3,136,0,0,128,191,189,3,114,103,98,0]}],[2,{"id":2,"ioInfo":[[["","out"],{"blocking":false,"group":"","id":19,"name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","inputConfig"],{"blocking":true,"group":"","id":18,"name":"inputConfig","queueSize":8,"type":3,"waitForMessage":false}],[["","inputImage"],{"blocking":true,"group":"","id":17,"name":"inputImage","queueSize":8,"type":3,"waitForMessage":true}]],"name":"ImageManip","properties":[185,6,185,8,185,7,185,4,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,185,3,185,2,136,0,0,0,0,136,0,0,0,0,185,2,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,0,136,0,0,128,63,136,0,0,128,63,0,1,185,15,133,32,2,133,64,1,0,0,0,0,186,0,1,0,186,0,0,0,136,0,0,0,0,0,1,185,6,7,0,0,0,0,133,255,0,0,1,1,0,0,134,0,0,16,0,4,0,0,189,0]}],[3,{"id":3,"ioInfo":[[["","out"],{"blocking":false,"group":"","id":16,"name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","passthrough"],{"blocking":false,"group":"","id":15,"name":"passthrough","queueSize":8,"type":0,"waitForMessage":false}],[["","in"],{"blocking":true,"group":"","id":14,"name":"in","queueSize":5,"type":3,"waitForMessage":true}]],"name":"DetectionNetwork","properties":[185,6,130,75,30,35,0,189,12,97,115,115,101,116,58,95,95,98,108,111,98,8,0,0,185,7,1,136,0,0,0,63,0,0,186,0,187,0,136,0,0,0,0]}],[4,{"id":4,"ioInfo":[[["","in"],{"blocking":true,"group":"","id":13,"name":"in","queueSize":8,"type":3,"waitForMessage":true}]],"name":"XLinkOut","properties":[185,3,136,0,0,128,191,189,9,100,101,116,101,99,116,105,111,110,0]}],[5,{"id":5,"ioInfo":[[["io","manip_cfg"],{"blocking":false,"group":"io","id":12,"name":"manip_cfg","queueSize":8,"type":0,"waitForMessage":false}],[["io","manip_img"],{"blocking":false,"group":"io","id":11,"name":"manip_img","queueSize":8,"type":0,"waitForMessage":false}],[["io","preview"],{"blocking":true,"group":"io","id":10,"name":"preview","queueSize":8,"type":3,"waitForMessage":false}],[["io","dets_in"],{"blocking":true,"group":"io","id":9,"name":"dets_in","queueSize":8,"type":3,"waitForMessage":false}],[["io","passthrough"],{"blocking":true,"group":"io","id":8,"name":"passthrough","queueSize":8,"type":3,"waitForMessage":false}]],"name":"Script","properties":[185,3,189,14,97,115,115,101,116,58,95,95,115,99,114,105,112,116,189,8,60,115,99,114,105,112,116,62,1]}],[6,{"id":6,"ioInfo":[[["","out"],{"blocking":false,"group":"","id":7,"name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","inputConfig"],{"blocking":true,"group":"","id":6,"name":"inputConfig","queueSize":8,"type":3,"waitForMessage":true}],[["","inputImage"],{"blocking":true,"group":"","id":5,"name":"inputImage","queueSize":8,"type":3,"waitForMessage":true}]],"name":"ImageManip","properties":[185,6,185,8,185,7,185,4,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,185,3,185,2,136,0,0,0,0,136,0,0,0,0,185,2,136,0,0,0,0,136,0,0,0,0,136,0,0,0,0,0,136,0,0,128,63,136,0,0,128,63,0,1,185,15,133,128,0,133,0,1,0,0,0,0,186,0,1,0,186,0,0,0,136,0,0,0,0,0,1,185,6,32,0,0,0,0,133,255,0,0,1,0,0,0,134,0,0,16,0,4,0,0,189,0]}],[7,{"id":7,"ioInfo":[[["","out"],{"blocking":false,"group":"","id":4,"name":"out","queueSize":8,"type":0,"waitForMessage":false}],[["","passthrough"],{"blocking":false,"group":"","id":3,"name":"passthrough","queueSize":8,"type":0,"waitForMessage":false}],[["","in"],{"blocking":true,"group":"","id":2,"name":"in","queueSize":5,"type":3,"waitForMessage":true}]],"name":"NeuralNetwork","properties":[185,5,130,126,177,13,0,189,12,97,115,115,101,116,58,95,95,98,108,111,98,8,0,0]}],[8,{"id":8,"ioInfo":[[["","in"],{"blocking":true,"group":"","id":1,"name":"in","queueSize":8,"type":3,"waitForMessage":true}]],"name":"XLinkOut","properties":[185,3,136,0,0,128,191,189,11,114,101,99,111,103,110,105,116,105,111,110,0]}]]}
But I don't know how to unserialize the information.

Sorry I meant what the actual frame rate the different nodes are running at.
I have the camera fps set to 30, but it outputs at 10 fps through xlink out, and I cannot deduce why.
Thank you again!

The fps you set with a call to setFps() corresponds to the max fps you can get. The real observed fps depends on the slowest component in the pipeline. For instance, if you are using an heavy NeuralNetwork model, it may have a big impact on the fps.

Much appreciated! I was wondering if you were to able capture "actual fps" from the log files. Thank you for the great work!


Add Scrollbar

I don't see a scrollbar and would like to be able to scroll my terminal. Would it be possible to add one?

x-terminal supports this, as its xterm based, this isnt likely to happen without xterm. Since this uses term.js which is no longer developed try x-terminal


Update mitmengine to use new fingerprints

Hi there! I've added an additional test to _TestProcessorCheck() that takes a new signature (recently observed in ClickHouse) and currently prints out the corresponding Report. I wrote this extra test to ensure that new fingerprints are given expected Reports. The test itself still fails because I haven't populated the Report struct used as a sanity check; this is because I'm not sure what Report output I expect to see. (TL;DR this PR is a WIP; by the end of it I hope we are confident about the new browser signatures we are using for mitmengine, formalize how these signatures are collected, and have tests to ensure mitmengine Reports are as expected)
So far, I've run this new test with multiple types of browser.txt files used for fingerprint comparison. I was hoping this would give me clarity about what I should expect (and sanity check that the merged fingerprints produce the same expected output), but I was surprised to see a userAgent/fingerprint pair I thought was legitimate get deemed an "impossible" pair.
For browser_merge.txt (merged browser fingerprint file):
mitmengine.Report{
MatchedUASignature:"1:70:1:2::1:",
BrowserSignature:"303:~a,2f,35,9c,ff:~0,5,d:::*:",
BrowserSignatureMatch:0x1,
Reason:"invalid_cipher",
ReasonDetails:"~a,2f,35,9c,ff vs a,2f,35,9c,9d,1301,1302,1303,c013,c014,c02b,c02c,c02f,c030,cca8,cca9",
BrowserGrade:0x0,
ActualGrade:0x2,
WeakCiphers:false,
LosesPfs:false,
MatchedMitmSignature:"",
MatchedMitmName:"",
MatchedMitmType:0x0,
Error:error(nil)
}

^ So, does "impossible" mean that the traffic's fingerprint cannot possibly correspond to the presented userAgent? That's what I guess, given that invalid_cipher is given as a reason. This strikes me as weird, given that this was the sixth most popular userAgent/fingerprint string pair I observed as of late.
The non-overlapping cipher, 0xff, corresponds to TLS_EMPTY_RENEGOTIATION_INFO_SCSV (source)
This fake ciphersuite was used to support backwards compatibility with TLS 1.0 and 1.1-only servers rfc5746 Perhaps a new release of Chrome got rid of this, given Chrome's work towards eliminating TLS 1.0 and 1.1 support.
For browser.txt (unmerged browser fingerprint file):
mitmengine.Report{
MatchedUASignature:"1:30-70:1:2::1:",
BrowserSignature:"301:~?7,?a,?13,?16,2f,?32,?33,35,?38,?39,ff:~?0,?23:::*:", BrowserSignatureMatch:0x1,
Reason:"invalid_version",
ReasonDetails:"301 vs 303",
BrowserGrade:0x0,
ActualGrade:0x2,
WeakCiphers:false,
LosesPfs:false,
MatchedMitmSignature:"",
MatchedMitmName:"",
MatchedMitmType:0x0,
Error:error(nil)
}

^ This just looks plain wrong; how the heck does this fingerprint get compared to something with just TLS 1.0? I think this is because my version of browser.txt mixes inputs from clickhouse (which include ~ figures) and this results in weird comparison logic...
For browser_clickhouse.txt (current merged signatures used by clickhouse):
got: &errors.errorString{s:"unknown_user_agent"}

^ This explains why so much in our dashboard gets interpreted as "unknown" :) Very much symptomatic of inserter using outdated fingerprints.
The various browser*.txt files used above are included in testdata/mitmengine if you want to peek at them; we can remove them from git later.

I found the issue above--the logic for comparing version values had an off-by-one error, where exact version matches weren't matched at all. I've submitted a fix for this in the PR. Now new fingerprints match :)
This PR now consists of three components:

Minor refactoring and fixes
Adding new tests for fingerprints to ensure sanity when fingerprint files are updated, plus one benchmark over the processor.Check() function.
Adding a new "best matching" algorithm for fingerprints that cannot be matched to a browser, but should be matched to the closest fingerprint to ensure more accurate Report metrics about "closest match" browsers, like BrowserSignature, BrowserGrade, and Reason . (Previously, the last browser record iterated over was default the "closest match" browser. This algorithm simply consists of counting maximum overlap between fingerprint ciphers, extensions, curves, and EC point format; the browser record with the highest count of overlap is treated as the "closest match" browser.

Let me know if you have any other questions! Otherwise I will work on another PR for optimizing record lookups :)


How to handle heterogenous object sizes with diameter parameter

Hi,
Thank you for your amazing work.
I'm using the pre-trained nuclei segmentation model on a dataset where the size and shape of the cells can differ quite substantially.
I'm noticing a significant performance drop  when these images with heterogenous nuclei are being used as inputs. You outline in your documentation the impact of a too small or too high diameter but I was wondering what you would advise when the approximated diameter is suitable for only some of the objects in the image. I can provide example images upon request.
Thank you in advance for your help!
Samuel

Please do post an example image, I am curious what your size range is. I have found that resizing really isn't necessary when you train your own models (especially with Omnipose), so that might be your next step.

At the moment I'm just using CellPose as a pre-trained nuclei segmentation model without any fine-tuning.

The example set of four images above shows my input image at position [0,0] with variation in the size of the nuclei. Image at position [0,1] is the output from using:
python -m cellpose --dir /dir/to/imgs --pretrained_model nuclei --chan[0,0] --diameter 0
Based on your comments in https://github.com/MouseLand/cellpose/issues/454 I adjusted the transforms. py normalise99 range to be 0.01 - 99.99 I then reran the segmentation and produced the image at position [0,2]. Finally when I still wasn't getting the results I was expecting I ran with the cytoplasm model which across a collection of images produces much better results (example shown at position [0,3]). You'll see for each of the three masks I have also added the approximated diameter from CellPose. Additional examples below:

It may be that the size range (and its impact on the diameter est) may not be the issue. Wondering why the cytoplasm model performs better on DAPI channel that the nuclei stained model.

Is this in part due to the rescaling? I observe the significant difference in the approximated diameter for Cytoplasm vs Nuclei models which is to be expected. From your documentation for the Cytoplasm model the numerator in the rescaling is 30/diameter compared to 17/diameter for the nuclei model.

if your nuclei are very non-uniform, then the cytoplasm model may perform better. the nuclei in the nucleus training set were fairly homogeneous. you may alternatively want to train your own model on your data, this is now possible in the GUI (pip install cellpose --upgrade)


fix ct.new flag not work

[ ] Make sure you have followed Kube-OVN Code Style.

What type of this PR
Examples of user facing changes:

Features
Bug fixes
Docs
Tests

Which issue(s) this PR fixes:
Fixes #(issue-number)

Need be backport back to release-1.9


delay reopen file to underlaying writer and do not block with queue is full

LGTM, thx for your contribution


Make nightly run green again

There are testsuite failures with A/A depoyments

Revert https://github.com/keycloak/keycloak-benchmark/commit/92cf75b2791eda7a625039ea6600d1479145327b when done


"Change the web root" sample code misleading/outdated because of .NET 6 breaking change of Webhost settings

Concerning: https://docs.microsoft.com/en-us/aspnet/core/fundamentals/minimal-apis?view=aspnetcore-6.0#change-the-web-root
The docs on "Change the web root" and the code sample following that state, that changing the webroot can be done by using builder.WebHost.UseWebRoot("webroot");.
This is false, because:

It contradicts documentation on this change between .NET 5 and 6:

https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60-samples?view=aspnetcore-6.0#change-the-web-root (see code sample)

https://docs.microsoft.com/en-us/aspnet/core/migration/50-to-60?view=aspnetcore-6.0&tabs=visual-studio#differences-between-the-aspnet-core-5-and-6-hosting-models:

It's not possible to change any host settings such as app name, environment, or the content root after the creation of the WebApplicationBuilder. […]

Using the sample code on .NET 6 results in a build error:

Unhandled exception. System.NotSupportedException: The web root changed from "[…]" to "[…]". Changing the host configuration using WebApplicationBuilder.WebHost is not supported. Use WebApplication.CreateBuilder(WebApplicationOptions) instead. […]

Perhaps the extension method should be removed as well, because it doesn't seem to serve a purpose anymore.)
Thank you! :)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b09824ab-b051-75a1-13b7-b0e281cc46e0
Version Independent ID: b09824ab-b051-75a1-13b7-b0e281cc46e0
Content: Minimal APIs overview
Content Source: aspnetcore/fundamentals/minimal-apis.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@Ducki  thanks for reporting this.

Using the sample code on .NET 6 results in a build error:

That's actually a run time error. It would be nice to issue a build warning.

Perhaps the extension method should be removed as well, because it doesn't seem to serve a purpose anymore.)

We have many customers using .NET 3.1 and 5.0, so we can't remove it.

I see, sorry for the wrong wording. I opened a pull request that uses the sample code from the migration guide.
Thank you 👍


How to remove spacing around multiple type hints

Support question
Right now, CS Fixer is creating spaces either side of the pipe separators with multiple type hint parameters e.g.
public function test(int | float | string | null $arg)
How do I get it to remove these so it becomes like so:
public function test(int|float|string|null $arg)
The same also applies to return types.
Thanks!

This temp solution worked for me https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/5495#issuecomment-777187487

Thanks for posting, but this doesn't seem to work for me...
'binary_operator_spaces' => [
    'align_double_arrow' => true,
    'align_equals' => true,
    'operators' => ['|' => null]
],


Speed ups to the setNumberDensities method on the composites

Currently, setting the number densities on a composite requires iteratively reaching down into the composite tree to calculate volumes of components. This process is relatively slow and if it can be sped up then the UniformMesh can be sped up. This is an issue where the uniform mesh conversion process can take upwards of 20 minutes to complete and this is unreasonable for analyses using the ARMI framework.
I do not have specific timing tests available right now, can this can be added later.

Being addressed in #1042 and can be closed then that is merges


Luis Azure Resource information

The information in step 7. is no longer updated with how LUIS presents things.
The screenshot should be updated.
Also, the bot settings ask for a LUIS endpoitn key, and it's not clear where we get that key from.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c55e6920-2987-2b78-66b7-3dee92ab8689
Version Independent ID: 5d9f5e75-ee25-cc5d-bdd5-594712badf63
Content: Tutorial: Add language understanding to bot - Bot Composer
Content Source: composer-docs/tutorial/tutorial-luis.md
Service: bot-composer
GitHub Login: @WashingtonKayaker
Microsoft Alias: kamrani

Hi @tiagonmas thanks for reporting the issue. We actually noticed this issue as well and are doing a patch release of the docs coming soon.


Enhance/add model tests for juniorstory

adds specs for all methods that create a sentence for an attribute of a juniorstory

hey @RaimundSchramm thanks so much for this! So sorry I never responded, pls ping me next time!
I'd love to merge this - can you resolve the conflicts first thou? Let me know if you need help/have no time etc....

thank you!!!


how to convert jpdl4 to bpmn2?

i can't find the file which named 'jpdl4-bpmn2.xsl'

That's correct, this has been only done for 3 to bpmn2. If you like the XSD is available here:
https://github.com/droolsjbpm/jbpmmigration/blob/master/src/main/resources/schema/jpdl/jpdl-4.2.xsd
Use that and the current example to create supporting conversion for the newer 4.2.


The package doesn't support jQuery 3

The package is broken on new projects since it is outdated and relies on an outdated jQuery version with breaking changes.

The PR fixing it on the original repo. (jackocnr/intl-tel-input#427)
The jQuery breaking change notice.

Output from the console
jquery.js:9793 Uncaught TypeError: url.indexOf is not a function(…)
          jQuery.fn.load @ jquery.js: 9793
    (anonymous function) @ intlTelInput.js:61
    (anonymous function) @ intlTelInput.js:12
    (anonymous function) @ intlTelInput.js:14

loader.js:219 Uncaught Error: Could not find module `ember-resolver` imported from `customer-advising-dashboard/resolver`(…)

How do you want to proceed ?

Is this bug resolved?

@krnbatta there have been no commits on the project since the issue was filed, so I don't believe so.
An additional challenge for anyone looking to upgrade or migrate is that the underlying intl-tel-input library has [droppedhttps://github.com/jackocnr/intl-tel-input/issues/346) autoformat, which is a feature our apps and users are likely used to.

Hello, This project looks like is not currently mantained. I've made a fork of this project. Check it at  https://emberobserver.com/addons/ember-intl-tel-input2


[BUG] Journal entry tokens on map are remembering page offsets from the previously used journal entry token when referencing the same PDF.

Describe the bug
I'm referencing the same PDF for multiple PDF Journal Entries -- but refer to different page offsets.  I drop these journal entries onto my different maps.  Problem is that the journal entry token on each map is remembering the page offset last used -- even when caching is disabled.
To Reproduce
Steps to reproduce the behavior:

Create a PDF Journal Entry called BOO for PDF A with page offset X.  Notice that "Test Settings" works as expected.
Create a PDF Journal Entry called FOO for PDF A with page offset Y.  Notice that "Test Settings" works as expected.
Drag an instance of BOO to Map NEAT.
Drag an instance of FOO to Map COOL.
Go to Map NEAT and double-click on instance BOO.
Notice that it probably shows the PDF using page offset Y from #2 above.
Notice that as you manipulate the PDF for either BOO or FOO that the page offset you expect for the other is messed up.  Shows the last page offset you were using.
However, notice that "Test Settings" works as expected for all the Journal Entries listed in the Journal.
Notice that the page offset used for the last "Test Settings" is remembered by all the journal entry instances on the maps.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version Information:

Browser:  Using Foundry VTT application.
FoundryVTT 0.6.6
PDFoundry 0.7.4
Pathfinder 1 version 0.74.0 (I don't think you need my module information)

Additional context
It's absolutely critical to my purposes to be able to reference the same PDF in multiple Journal Entries and be able to use different page offsets.  If I move around in the PDF, I do NOT want that offset remembered -- I always want the page offset I setup for the Journal Entries to be used.  Currently, accessing the Journal Entries from the Journal directly and clicking the "Test Settings" button is the behavior I want to have when I click the Journal Entry instances on my maps -- and I will use that as a work-around until this issue is fixed.  But it would make things much easier if this problem was fixed.

Let me make sure I have your use case correct here, because this behavior is expected and as such not really a "bug". The page offset in the PDF configuration isn't intended to be used so that the page opens to a specific page every time. There are options both in the creation of journal links and map notes configuration that allow you to open to a specific page.
If the goal is to open to a specific page when you double click the map note, you can do that by setting the page in the map pin settings (double right click the pin and you get the map note configuration, I underlined the part you're looking for). If the underlined field is blank, it opens to the last viewed page. If you specify a page it'll open to the page specified + the offset from the configuration.

If the goal isn't to open a specific page - could you elaborate on exactly what you're trying to do with these two distinct remembered locations so I can make sure I properly understand the requested functionality?

Oh, yes, you understand my use case.  I tried using the page offset because I did not know about this option in the map pin.  Thank you.  I will try it.

Yes, it works as you described!  Thank you for answering my question.  Your module makes everything much easier for our games!  Thank you!!!

Ok great, glad to hear; I'm going to close this issue for now then. If anything else comes up feel free to open up another issue.


[FRONTEND] Use ttgir module num-warps instead of default value

Use ttgir num-warps attribute instead of default value.

What if kwargs does contain num_warps, do you still want to use num_warps encoded in the ttgir?

What if kwargs does contain num_warps, do you still want to use num_warps encoded in the ttgir?

I think if kwargs contains a value of num_warps that's different from what's assumed by the compiler, then we should throw an error to avoid undefined behavior


Create Landing/Login Page

[x] Button for POST functionality
[x] Button to redirect to signup
[x] POST should send email and password.
[x] Should have error functionalities to ensure email and password are not left blank

Buttons added, all functionality in


Debug stuck on pause in callback?

Testing #115160

I can hit the callback, but I can't press the resume button.
If I go to the call stack viewlet and hover over the Attach to Extension Host part, I notice that I can press the resume button from there and continue debugging (just learned about this feature while typing up this issue).
I'm guessing it's a glitch in the debugger?

I saw the same thing yesterday: https://github.com/microsoft/vscode/issues/115275

I saw the same thing yesterday: https://github.com/microsoft/vscode/issues/115275

Same as my comment in that issue  - unlucky the only piece of information that I am interested in is collapsed here - the CALL STACK view :)
Thanks for creating this issue.
I have fixed a "somewhat" similar bug 30 minutes ago. In order to know if it is the same bug: does you application have some deemphasized stack frames (they appear grayed out in the CALL STACK)? If answer is yes -> please wait for next Insiders and it should be fixed, if not let me know.
If your application does not have any "grayed out" stack frames, then is it possible that I just clonse the repo and try to reproduce on my own?
If not, we can also involve Connor. But maybe you first answer the first question.

Same as my comment in that issue  - unlucky the only piece of information that I am interested in is collapsed here - the CALL STACK view :)
Thanks for creating this issue.
I have fixed a "somewhat" similar bug 30 minutes ago. In order to know if it is the same bug: does you application have some deemphasized stack frames (they appear grayed out in the CALL STACK)? If answer is yes -> please wait for next Insiders and it should be fixed, if not let me know.
If your application does not have any "grayed out" stack frames, then is it possible that I just clonse the repo and try to reproduce on my own?
If not, we can also involve Connor. But maybe you first answer the first question.

Thank you!

Thank you!


Is the plugin source code available?

Is the source code for the plugin available for auditing?

You mean is the project open source? Currently not as I'm still working on core feature. But I hope to make it open source soon like my other extension.
For audit I presume you're referring to security scans. If yes, Microsoft performs multiple scan on all extension before they code sign and releasing package.


Add --staged option

Why
As a developer, I often juggle multiple tasks. For example, while working on my branch xyz, I was asked to fix an urgent issue. Instead of stashing my changes, I switched branches to address it quickly. After making the fix, I wanted to run Laravel Pint and PHPStan to check for issues, but I needed to focus only on the staged changes.
Currently, there’s a --dirty flag, but I propose adding a --staged flag. This would allow us to run Pint exclusively on staged files, improving our workflow when context-switching.
alias pint-staged="vendor/bin/pint $(git diff --cached --name-only --diff-filter=ACM)"

I have created this alias to run Pint on staged files. This command lets me quickly validate staged changes without affecting uncommitted work. But after this PR merge, I will remove it from .zshrc.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


Skipping breaks bug

Prerequisites

[x] I'm using latest version: v 0.21.1
[x] I've checked Known issues

Description
[Description of the issue]
When running breaks on full-screen with the 'don't let me skip breaks' option enabled, it is extremely simple to escape the break screen by pressing command +tab twice
Operating system: MacOS High Sierra 10.13.6
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: Cannot skip break
Actual behavior: Can skip break
Reproduces how often: 100%
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Hi, this is how macOS behaves, I mean on OS-level. I can't change that ;/ I tried in past some ideas how to workaround it, but it never worked...

Dang, yours is such a nifty minimalistic tool otherwise. Thanks so much for what you've created.
Just a thought, have you checked Dejal's Time Out app. It is a screen timer but with many many features that can get quite confusing. However, its plus point is that the breaks come in as a screen overlay and while the comment + tab can switch to other apps (which can be seen if the break screen is set to semi-transparent) but the overlay remains.
This is an idea, which if you would try would make Stretchly just simple awesome.

Yeah I've seen that app, many many summers ago. He is using native code, so his app can do more powerful stuff. I am using Electron as aiming to be able to use app on more platforms, but Electron's APIs are less powerful ;/


D3 opacity transition erases dotted lines/makes path invisible

I am trying to achieve a transition upon a colored via clipping chart (http://bl.ocks.org/mbostock/4062844) that has its path "above" dotted.
Once I try to do a click event to take the path above to opacity 0 it dissapears and there is no way of bringing it back, leaving only the path "below".
Example: https://youtu.be/MsAcJQgVR3k
Code:
d3.selectAll(".tag"+d.key.replace(/\s+/g, ''))
  .transition().duration(500)
  .style("opacity", newOpacity);

SO: http://stackoverflow.com/questions/34969051/d3-opacity-transition-erases-dotted-lines-makes-path-invisible

Works for me.
http://bl.ocks.org/mbostock/b6c18261ef23b688f88f

I have gotten it to work with one, but it seems that once I make it multiseries it breaks. That's why I post it here.
Maybe (most likely) I'm doing something wrong, but it just seemed strange that I could make it work with one and once I made it multiseries it would behave erratically.
Moreover, I've been testing for the past week in different browsers/OS systems and the results are all over the place.

Unfortunately I don’t have time to investigate this further (especially without any code that demonstrates the problem). It’s certainly possible there’s a browser rendering bug related to the clipping mask, but this doesn’t sound like a D3 bug in any case.

I've done several versions, but just in case you do find the time (and maybe something does pop up) I will paste the last implementation (at least the important part)
    // Loop through each symbol / key
    dataNest.forEach(function(d,i) {
        svg.append("clipPath")
              .attr("id", "clip-above")
            .append("rect")
              .attr("width", width)
              .attr("height", function(){
                console.log(th(d.key), d.key);
                return y(th(d.key));
              });

          svg.append("clipPath")
              .attr("id", "clip-below")
            .append("rect")
              .attr("y", y(th(d.key)))
              .attr("width", width)
              .attr("height", height - y(th(d.key)));

          var clip = ["below", "above"];

          clip.forEach(function(v,i){
            svg.append("path")
              .attr("class", function() { return 'tag'+d.key.replace(/\s+/g, '') + " line " + v; })
              .attr("clip-path", function() { return "url(#clip-" + v + ")"; })
              // .attr("id", 'tag'+d.key.replace(/\s+/g, ''))
              .attr("d", line(d.values))
              .style('fill', 'none')
              .style("stroke", function() { // Add the colours dynamically
                  return color(d.key);
              });
          });
}

If you can find what's wrong that would be great, if not thanks anyways and I appreciate you taking the time

Yeah, so if dataNest has multiple elements, you are creating multiple clipPaths with the same id (clip-above or clip-below). Unfortunately, you need to give them globally unique IDs on the page, due to the design of SVG. If they’re the same across the lines then you could just create them once and share them, though.

You're totally right. I don't know how I missed that for so long...
Just changed it and is working perfectly now.


Problem with inserting nested elements

I have a problem when trying to set content with code like:

a

b

It throws an error
quill.js:3445 Uncaught TypeError: Cannot read property 'emit' of undefined
at Scroll.update (quill.js:3445)
at MutationObserver. (quill.js:10945)
What can I do to fix this bug?

This repo uses an outdated version of Quill.js and was produced to demonstrate a custom build of QuillJS that could be used with Custom Elements. Unfortunately, I am not in a position to support this going forward.


continuous integration for phpcs

add phpcs check in travis

@EmanueleMinotto you are my standard man! :) Can you help me?!

sure boss!

exaggerated!! Thanks!


puppet-gitlab requires outdated module dependencies

General apology
I'm no expert in puppet nor git issues. Please be kind with my issue and me.
Affected versions

vshn/puppet-gitlab 1.15.1
puppetlabs/apt 4.1.0
Puppet 4.10.5
Ubuntu 16.04 LTS

How to reproduce
puppet module install vshn-gitlab when current version of puppetlabs-apt is installed, or
puppet module list --verbose when modules are installed by --force.
What am i seeing?
$ puppet module list --verbose
Warning: Module 'puppetlabs-apt' (v4.1.0) fails to meet some dependencies:
  'vshn-gitlab' (v1.15.1) requires 'puppetlabs-apt' (>=2.1.0 <3.0.0)
...

Expected behaviour
A clean install.
Suggest solution
Bump required maximum version of puppetlabs-apt to <5.0.0. Unfortunately i don't have the competency to actually tell whether there is code that isn't 4.x-compliant.

According to the changelog in the apt module it should be fully backwards compatible through the 4.x release.
https://github.com/puppetlabs/puppetlabs-apt/blob/master/CHANGELOG.md
Might just be worth changed the max version to less than 5 and see if any warnings appear in tests.

See https://github.com/vshn/puppet-gitlab/pull/169


Clarify and test data_callback error handling

data_callback, for example, can return a negative value on error.  This is expected to trigger a CUBEB_STATE_ERROR and stop the stream, leaving it in a state safe to call cubeb_stream_stop (possibly redundant) and cubeb_stream_destroy.
We should clarify the documentation as necessary (it's documented that CUBEB_ERROR is a valid return code, but what about the other CUBEB_ERROR_* results?) and add tests that ensure the backends correctly handle this.
cubeb_wasapi asserts instead of handling the error.
Since we don't trigger that assert in Gecko, I expect that the data_callback error handling is inconsistent in each backend, and even in the backends that do try to handle errors the handling is un(der)tested.

https://github.com/kinetiknz/audioipc/commit/85e9839059f4bf8f68130825b8fd02c39a6a51b9 extends the need here by adding another error path in data_callback.  I'll address the cubeb-side error handling issues shortly.

This has been done for the Tier-1 backends in https://github.com/mozilla/cubeb/pull/698 (and the associated Rust repos).  test_callback_ret verifies this behaviour.


Dynamic Timers

I am trying to create a number of dynamic timers in the mounted lifecycle event of a component:
  mounted() {
    if (this.jobs) {
      for (let job of this.jobs) {
        this.$store.dispatch(`dashboard-${this.id}/LOAD_DATA`, { elementId: job.name, service: job.service })
        if (job.refresh && job.refresh.interval) {
          this.timers[`${this.id}-${job.name}`] = {
            name: `${this.id}-${job.name}`,
            time: job.refresh.interval,
            autostart: false,
            repeat: true,
            callback() {
              this.$store.dispatch(`dashboard-${this.id}/LOAD_DATA`, { elementId: job.name, service: job.service })
            }
          }
          console.log(this.timers)
          this.$timer.start(`${this.id}-${job.name}`)
        } else {
          this.$timer.stop(`${this.id}-${job.name}`)
        }
      }
    }
  },

But, when it gets to the $timer.start() call, I get the following: "[vue-timers.start] Cannot find timer tal-cs-tier1-callsInbound". The console.log(this.timers)shows that the timer object exists. I have tired both object notation and array.

Okay, it seems the issue is with the callback. I can only get it to work if the method has the same name as the timer. Is there any way around this.
My use case is: I pass in a collection of jobs, so I want to dynamically create a timer for each job, with its own name, and then use a common method as a callback. Is this possible?