text:
didnt show logical/physical disk in report.

html report only have:
[Tool Parameters]
[Alerts by Chronological Order]
[Memory]
[Memory Available MBytes (Alerts: 0|0)]
[Network Interface]
[Network Interface Bytes Total/sec (Stats only)]
[Processor]
[Processor % Processor Time (Alerts: 0|2)]
[Incomplete analyses]
[Disclaimer]

Hey @happytony for this blg file you gathered to process, what OS and is it a localized instance?

first i use PAL 2.8.2 version, 2.8.1 also try the old version 2.3.2
original is blg file, i do try to convert to csv as well. can see the disk record in there.
os i capture is win2012R2, win2016, win2019. and i do PAL analysis on win10.
but for csv, it just a list of text data, seem not influence by OS.
the counter i capture is some logical disk, some physical disk, some network sent/receive bytes, and also CPU time, and memory available. well, html only show the rest , but dont have logical and physical disk. no wonder i use which blg/csv, new old PAL. the result is same.

Hey @happytony for this blg file you gathered to process, what OS and is it a localized instance?

first i use PAL 2.8.2 version, 2.8.1 also try the old version 2.3.2
original is blg file, i do try to convert to csv as well. can see the disk record in there.
os i capture is win2012R2, win2016, win2019. and i do PAL analysis on win10.
but for csv, it just a list of text data, seem not influence by OS.
the counter i capture is some logical disk, some physical disk, some network sent/receive bytes, and also CPU time, and memory available. well, html only show the rest , but dont have logical and physical disk. no wonder i use which blg/csv, new old PAL. the result is same.

Ok but is the OS localized, so instead of en-us a different language is enabled?

Ok but is the OS localized, so instead of en-us a different language is enabled?

i check the setting is english US(default). but do have chinese input.

Ok but is the OS localized, so instead of en-us a different language is enabled?

you means the place i capture logman have other language or the place i run PAL.
but anyway, but side have chinese input, but default is en-US.

i run this. Get-WinSystemLocale
it show chinese. let me try play on this and see. Thank you.

after Set-WinSystemLocale en-US (restart), still the same, the report didnt show disk.

interesting. yeah lets see what clint says.
On Sat, Apr 15, 2023 at 12:13 PM happytony @.***> wrote:

after Set-WinSystemLocale en-US (restart), still the same, the report
didnt show disk.
—
Reply to this email directly, view it on GitHub
https://github.com/clinthuffman/PAL/issues/82#issuecomment-1509884492,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACFOL6K4MD3AJ3MQVPPX3Z3XBLCK7ANCNFSM6AAAAAAW7NZMUA
.
You are receiving this because you commented.Message ID:
@.***>

show more info:

xml have same bug.
try to use another 2 device to analysis, report is same bug.
here is 3 script i colect data:

logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30

-c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes"
-c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes"

run in PAL.ps1 is same case.
i attach 1 of result file to show my case.

oh, what profile are you using to analyze? and are you checking the box for
"analyze all performance counters"?
On Sat, Apr 15, 2023 at 2:27 PM happytony @.***> wrote:

show more info:

xml have same bug.
try to use another 2 device to analysis, report is same bug.
here is 3 script i colect data:

logman create counter MonitorUsage -c "\Processor(_Total)% Processor
Time" "\LogicalDisk(_Total)\Current Disk Queue Length"
"\PhysicalDisk(_Total)\Current Disk Queue Length"
"\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk
Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec"
"\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes
Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes
Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes
Received/sec" "\Memory\Available MBytes" -f bincirc -o
C:\logfile\process.blg -si 00:01:30

-c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk
Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length"
"\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk
Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec"
"\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes
Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes
Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes
Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet
_2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet
_2)\Bytes Received/sec" "\Memory\Available MBytes"
-c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk
Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length"
"\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk
Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec"
"\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface(*)\Bytes
Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network
Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network
Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit
Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210
Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available
MBytes"

run in PAL.ps1 is same case.
i attach 1 of result file to show my case.
[image: image]
https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png

—
Reply to this email directly, view it on GitHub
https://github.com/clinthuffman/PAL/issues/82#issuecomment-1509922167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA
.
You are receiving this because you commented.Message ID:
@.***>

oh, what profile are you using to analyze? and are you checking the box for "analyze all performance counters"?
…
On Sat, Apr 15, 2023 at 2:27 PM happytony @.> wrote: show more info: 1. xml have same bug. 2. try to use another 2 device to analysis, report is same bug. 3. here is 3 script i colect data: - logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30 -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes" -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(_Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes" 1. run in PAL.ps1 is same case. 2. i attach 1 of result file to show my case. [image: image] https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png — Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA . You are receiving this because you commented.Message ID: @.***>

@jeffstokes72 you means the threshold file right? i use "system overview", "quick system overview" and auto detect. i do try on another 2 not related. but i forgot what title.
but all is same result.

oh, what profile are you using to analyze? and are you checking the box for "analyze all performance counters"?
…
On Sat, Apr 15, 2023 at 2:27 PM happytony @.___> wrote: show more info: 1. xml have same bug. 2. try to use another 2 device to analysis, report is same bug. 3. here is 3 script i colect data: - logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30 -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes" -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes" 1. run in PAL.ps1 is same case. 2. i attach 1 of result file to show my case. [image: image] https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png — Reply to this email directly, view it on GitHub <#82 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA . You are receiving this because you commented.Message ID: @.***>

@jeffstokes72 you means the threshold file right? i use "system overview", "quick system overview" and auto detect. i do try on another 2 not related. but i forgot what title. but all is same result.

for process all counter, not all time i click. i try many time. on and off i click.

Can you send/share the counter log?
If your counter log only captured the _Total instance of Logical Disk and Physical Disk, then no counter data will show in PAL analysis.  This is on purpose because the _Total is a sum of all of the counter instances and not useful. I recommend that you collect another counter log for all counter instance such as \LogicalDisk(*)* and then analyses it with PAL again.
Thank you,
Clint Huffman
From: @.>
Sent: Saturday, April 15, 2023 8:15 PM
To: @.>
Cc: @.***>
Subject: Re: [clinthuffman/PAL] didnt show logical/physical disk in report. (Issue #82)
oh, what profile are you using to analyze? and are you checking the box for "analyze all performance counters"?
…
On Sat, Apr 15, 2023 at 2:27 PM happytony @.___> wrote: show more info: 1. xml have same bug. 2. try to use another 2 device to analysis, report is same bug. 3. here is 3 script i colect data: - logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30 -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes" -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes" 1. run in PAL.ps1 is same case. 2. i attach 1 of result file to show my case. [image: image] https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png — Reply to this email directly, view it on GitHub <#82 (comment)https://github.com/clinthuffman/PAL/issues/82#issuecomment-1509922167>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA . You are receiving this because you commented.Message ID: @.***>
@jeffstokes72https://github.com/jeffstokes72 you means the threshold file right? i use "system overview", "quick system overview" and auto detect. i do try on another 2 not related. but i forgot what title. but all is same result.
for process all counter, not all time i click. i try many time. on and off i click.
—
Reply to this email directly, view it on GitHubhttps://github.com/clinthuffman/PAL/issues/82#issuecomment-1510030176, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEXDYVEB5NBYNH4ZWW6OF63XBNP4ZANCNFSM6AAAAAAW7NZMUA.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Can you send/share the counter log? If your counter log only captured the Total instance of Logical Disk and Physical Disk, then no counter data will show in PAL analysis. This is on purpose because the Total is a sum of all of the counter instances and not useful. I recommend that you collect another counter log for all counter instance such as \LogicalDisk()* and then analyses it with PAL again. Thank you, Clint Huffman From: @.> Sent: Saturday, April 15, 2023 8:15 PM To: @.> Cc: @.**> Subject: Re: [clinthuffman/PAL] didnt show logical/physical disk in report. (Issue #82) oh, what profile are you using to analyze? and are you checking the box for "analyze all performance counters"? … On Sat, Apr 15, 2023 at 2:27 PM happytony @._> wrote: show more info: 1. xml have same bug. 2. try to use another 2 device to analysis, report is same bug. 3. here is 3 script i colect data: - logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec"
All.zip
"\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30 -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes" -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes" 1. run in PAL.ps1 is same case. 2. i attach 1 of result file to show my case. [image: image] https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png — Reply to this email directly, view it on GitHub <#82 (comment)<#82 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA . You are receiving this because you commented.Message ID: @.> @jeffstokes72https://github.com/jeffstokes72 you means the threshold file right? i use "system overview", "quick system overview" and auto detect. i do try on another 2 not related. but i forgot what title. but all is same result. for process all counter, not all time i click. i try many time. on and off i click. — Reply to this email directly, view it on GitHub<#82 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEXDYVEB5NBYNH4ZWW6OF63XBNP4ZANCNFSM6AAAAAAW7NZMUA. You are receiving this because you are subscribed to this thread.Message ID: @.>

Thank you. i send you 2 of log here. and i will try on "logical disk *".

Can you send/share the counter log? If your counter log only captured the Total instance of Logical Disk and Physical Disk, then no counter data will show in PAL analysis. This is on purpose because the Total is a sum of all of the counter instances and not useful. I recommend that you collect another counter log for all counter instance such as \LogicalDisk()* and then analyses it with PAL again. Thank you, Clint Huffman From: @.> Sent: Saturday, April 15, 2023 8:15 PM To: @.> Cc: @.**> Subject: Re: [clinthuffman/PAL] didnt show logical/physical disk in report. (Issue #82) oh, what profile are you using to analyze? and are you checking the box for "analyze all performance counters"? … On Sat, Apr 15, 2023 at 2:27 PM happytony @._> wrote: show more info: 1. xml have same bug. 2. try to use another 2 device to analysis, report is same bug. 3. here is 3 script i colect data: - logman create counter MonitorUsage -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Sent/sec" "\Network Adapter(Realtek PCIe GBE Family Controller)\Bytes Received/sec" "\Memory\Available MBytes" -f bincirc -o C:\logfile\process.blg -si 00:01:30 -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet)\Bytes Received/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Sent/sec" "\Network Adapter(Broadcom NetXtreme Gigabit Ethernet _2)\Bytes Received/sec" "\Memory\Available MBytes" -c "\Processor(_Total)% Processor Time" "\LogicalDisk(_Total)\Current Disk Queue Length" "\PhysicalDisk(_Total)\Current Disk Queue Length" "\LogicalDisk(_Total)\Disk Reads/sec" "\PhysicalDisk(_Total)\Disk Reads/sec" "\LogicalDisk(_Total)\Disk Writes/sec" "\PhysicalDisk(Total)\Disk Writes/sec" "\Network Interface()\Bytes Total/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection)\Bytes Received/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Sent/sec" "\Network Adapter(Intel[R] I210 Gigabit Network Connection _2)\Bytes Received/sec" "\Memory\Available MBytes" 1. run in PAL.ps1 is same case. 2. i attach 1 of result file to show my case. [image: image] https://user-images.githubusercontent.com/4474370/232247132-0e84d481-a3cb-4839-9989-f412bb515292.png — Reply to this email directly, view it on GitHub <#82 (comment)<#82 (comment)>>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACFOL6MFE7ZDLQA7ZAEMLODXBLSAPANCNFSM6AAAAAAW7NZMUA . You are receiving this because you commented.Message ID: @.> @jeffstokes72https://github.com/jeffstokes72 you means the threshold file right? i use "system overview", "quick system overview" and auto detect. i do try on another 2 not related. but i forgot what title. but all is same result. for process all counter, not all time i click. i try many time. on and off i click. — Reply to this email directly, view it on GitHub<#82 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEXDYVEB5NBYNH4ZWW6OF63XBNP4ZANCNFSM6AAAAAAW7NZMUA. You are receiving this because you are subscribed to this thread.Message ID: @.>

Thank you. i send you 2 of log here. and i will try on "logical disk *".
All.zip

authors: clinthuffman happytony jeffstokes72

repo: clinthuffman/PAL


text:
Fix ConnectionClosed mapping

Fix ConnectionClosed mapping when async-tokio-rusqlite is disabled.

Changes unknown
when pulling 3fc03250548724988b99ba0778ae67770fde9db0 on czocher:fix-source-mapping
into ** on cljoly:master**.

source: gharchive/pull-request

authors: coveralls czocher

license_type: permissive

license_source: github-api


text:
Fails to install with Yarn 3: "Error: Assertion failed: Expected the root to be registered"

I am using Yarn 3.1.1 and on a fresh Docusaurus install, yarn add docusaurus-preset-openapi yields this error:
Error: Assertion failed: Expected the root to be registered

To reproduce, put this pacakge.json in an empty directory and run yarn install && yarn add docusaurus-preset-openapi afterwards:
{
  "name": "my-package",
  "packageManager": "yarn@3.1.1",
  "dependencies": {
    "@docusaurus/core": "2.0.0-beta.14",
    "@docusaurus/preset-classic": "2.0.0-beta.14",
    "@mdx-js/react": "^1.6.21",
    "clsx": "^1.1.1",
    "prism-react-renderer": "^1.2.1",
    "react": "^17.0.1",
    "react-dom": "^17.0.1"
  }
}

However, it works fine with Yarn 1.22 (a version no longer under active development), if this line is removed:
  "packageManager": "yarn@3.1.1",

Update: it still fails when Docusaurus version is set to latest:
    "@docusaurus/core": "latest",
    "@docusaurus/preset-classic": "latest",

Thanks, I will try to reproduce and fix 😊

reproduced!

I was able to get it to install using "@docusaurus/core": "2.0.0-beta.13":
{
  "name": "my-package",
  "packageManager": "yarn@3.1.1",
  "dependencies": {
    "@docusaurus/core": "2.0.0-beta.13",
    "@mdx-js/react": "^1.6.21",
    "clsx": "^1.1.1",
    "docusaurus-preset-openapi": "0.3.1",
    "prism-react-renderer": "^1.2.1",
    "react": "^17.0.1",
    "react-dom": "^17.0.1"
  }
}

I'm guess the issue is because we depend on "2.0.0-beta.13" internally?

Thank you, @bourdakos1! With 2.0.0-beta.13 it does work wonderfully 👍.

source: gharchive/issue

license: MIT


text:
Add log generator workload

Description
Adding a log generator workload that will generate X messages of Y size (in bytes) per second/minute over a duration of Z minutes. If provided it will also check the backed log aggregator to confirm it received the expected number of messages. Supported backends are elasticsearch and AWS cloudwatch.
NOTE: This requires a backend storage to be deployed if we want to create a valid ci test for this.
benchmark-wrapper PR: https://github.com/cloud-bulldozer/benchmark-wrapper/pull/254 must be merged prior to this.

Do we want to add a test? I realize that might mean ES, but I wonder if we could use cloudwatch?

Using cloudwatch is definitely an option. I'll look to see how to set fluentd to log there.

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:13

test_byowl
Pass
0
00:01:13

test_fiod
Pass
1
00:35:23

test_flent
Pass
0
00:07:51

test_fs_drift
Pass
0
00:04:29

test_hammerdb
Pass
0
00:03:51

test_iperf3
Pass
0
00:06:35

test_kubeburner
Pass
0
00:19:58

test_pgbench
Pass
0
00:02:35

test_smallfile
Pass
0
00:04:58

test_stressng
Pass
0
00:01:54

test_sysbench
Pass
0
00:01:37

test_uperf
Fail
3
00:56:46

test_vegeta
Pass
0
00:05:52

test_ycsb
Pass
0
00:02:16

test_scale_openshift
Pass
0
00:08:30

/rerun all

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:19

test_byowl
Pass
0
00:01:08

test_fiod
Pass
2
00:46:26

test_flent
Pass
0
00:07:55

test_fs_drift
Pass
0
00:04:45

test_hammerdb
Pass
0
00:03:51

test_iperf3
Pass
0
00:06:45

test_kubeburner
Pass
0
00:19:44

test_pgbench
Pass
0
00:02:27

test_smallfile
Pass
0
00:04:54

test_stressng
Pass
0
00:01:54

test_sysbench
Pass
0
00:01:16

test_uperf
Pass
1
00:44:01

test_vegeta
Pass
0
00:04:18

test_ycsb
Pass
0
00:01:55

test_scale_openshift
Pass
0
00:09:03

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:12

test_byowl
Pass
0
00:01:09

test_fiod
Pass
3
00:56:38

test_flent
Pass
0
00:07:53

test_fs_drift
Pass
0
00:04:44

test_hammerdb
Pass
0
00:03:44

test_iperf3
Pass
0
00:06:55

test_kubeburner
Pass
0
00:20:05

test_pgbench
Pass
0
00:02:35

test_smallfile
Pass
0
00:05:07

test_stressng
Pass
0
00:01:56

test_sysbench
Pass
0
00:01:18

test_uperf
Fail
3
01:01:59

test_vegeta
Pass
0
00:04:27

test_ycsb
Pass
0
00:01:55

test_scale_openshift
Pass
0
00:05:35

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:10

test_byowl
Pass
0
00:01:12

test_fiod
Pass
2
00:44:32

test_flent
Pass
0
00:08:04

test_fs_drift
Pass
0
00:04:41

test_hammerdb
Pass
0
00:04:08

test_iperf3
Pass
0
00:06:36

test_kubeburner
Pass
0
00:19:53

test_pgbench
Pass
0
00:02:33

test_smallfile
Pass
0
00:05:09

test_stressng
Pass
0
00:01:56

test_sysbench
Pass
0
00:01:20

test_uperf
Pass
1
00:43:32

test_vegeta
Pass
0
00:04:25

test_ycsb
Pass
0
00:02:00

test_scale_openshift
Pass
0
00:08:30

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Fail
3
00:00:06

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Fail
3
00:00:06

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Fail
3
00:32:15

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Fail
3
00:27:23

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Fail
3
00:07:02

/rerun all tests/test_log_generator.sh

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_log_generator
Pass
0
00:02:47

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:21

test_byowl
Pass
0
00:01:12

test_fiod
Pass
3
01:06:26

test_flent
Pass
0
00:08:34

test_fs_drift
Pass
0
00:04:59

test_hammerdb
Pass
0
00:04:54

test_iperf3
Pass
0
00:07:10

test_kubeburner
Pass
0
00:21:49

test_log_generator
Pass
0
00:03:55

test_pgbench
Pass
0
00:02:40

test_smallfile
Pass
0
00:05:08

test_stressng
Pass
0
00:01:55

test_sysbench
Pass
0
00:01:19

test_uperf
Fail
3
01:15:44

test_vegeta
Pass
0
00:04:39

test_ycsb
Pass
0
00:02:50

test_scale_openshift
Pass
1
00:11:20

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:33

test_byowl
Pass
0
00:01:14

test_fiod
Pass
1
00:32:47

test_flent
Pass
0
00:08:19

test_fs_drift
Pass
0
00:05:10

test_hammerdb
Pass
0
00:04:00

test_iperf3
Pass
0
00:06:27

test_kubeburner
Pass
0
00:21:10

test_log_generator
Pass
0
00:04:13

test_pgbench
Pass
0
00:02:53

test_smallfile
Pass
0
00:05:02

test_stressng
Pass
0
00:02:10

test_sysbench
Pass
0
00:01:22

test_uperf
Pass
0
00:27:20

test_vegeta
Pass
0
00:04:43

test_ycsb
Pass
0
00:02:09

test_scale_openshift
Pass
0
00:09:16

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:05:35

test_byowl
Pass
0
00:01:14

test_fiod
Pass
1
00:32:58

test_flent
Pass
0
00:09:15

test_fs_drift
Pass
0
00:05:51

test_hammerdb
Pass
0
00:04:24

test_iperf3
Pass
0
00:06:38

test_kubeburner
Pass
0
00:21:07

test_log_generator
Pass
0
00:04:00

test_pgbench
Pass
0
00:02:46

test_smallfile
Pass
0
00:05:21

test_stressng
Pass
0
00:01:59

test_sysbench
Pass
0
00:01:27

test_uperf
Pass
0
00:27:50

test_vegeta
Pass
0
00:04:47

test_ycsb
Pass
0
00:02:56

test_scale_openshift
Pass
0
00:06:33

/rerun all

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_backpack
Pass
0
00:04:29

test_byowl
Pass
0
00:00:14

test_fiod
Pass
1
00:36:11

test_flent
Pass
0
00:08:22

test_fs_drift
Pass
0
00:05:00

test_hammerdb
Pass
0
00:03:54

test_iperf3
Pass
0
00:06:38

test_kubeburner
Pass
0
00:20:09

test_log_generator
Pass
0
00:03:30

test_pgbench
Pass
0
00:02:42

test_smallfile
Pass
0
00:05:06

test_stressng
Pass
0
00:01:55

test_sysbench
Pass
0
00:01:25

test_uperf
Pass
0
00:27:06

test_vegeta
Pass
0
00:04:19

test_ycsb
Pass
0
00:01:50

test_scale_openshift
Pass
0
00:09:14

repo: cloud-bulldozer/benchmark-operator


text:
[PERFSCALE-2470]: Updates to the GHA

This PR updates the GHA workflow for building & publishing multi-architecture container images
Type of change

[x] Refactor
[ ] New feature
[x] Bug fix
[ ] Optimization
[ ] Documentation Update

Description

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[x] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please describe the System Under Test.
Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

Hi 👋 @rsevilla87 @jtaleric ptal


text:
Updated documentation and CI tests

Removed test for couchbase for CI run, as ycsb test would verify.
Updated test execution.
Updated documentation post breakout PR merge occurred.

What is the state of this PR?

Requires a bit of rebase, so closing this for now

authors: aakarshg jtaleric

repo: cloud-bulldozer/ripsaw


text:
Request new module: cp-watson-studio

Related user story
Issue 533
Type of module
gitops
If requesting a terraform module, what is the target cloud platform?
ibm
What is the purpose of the module?
GitOps module to install Watson Studio on CP4D (https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=studio-installing-watson)
What is the category of the module?
service

/displayName CP Watson Studio

@sgumpana invited to repo with write access

authors: seansund sgumpana

repo: cloud-native-toolkit/automation-modules


text:
Config for Elasticsearch datasource

Please advice how to configure grafana_datasources for Elasticsearch,
I have to add URL and index, no auth is required, example of config in UI: http://prntscr.com/kkxb4q

We are following standards set by grafana project. So this: http://docs.grafana.org/features/datasources/elasticsearch/#configure-the-datasource-with-provisioning should easily translate to this: https://github.com/cloudalchemy/ansible-grafana/blob/69d16c5634056481498057f798b8d05f565e70ef/defaults/main.yml#L197-L206

To manage this config I set datasource manually and get config from WEB API:
curl -H "Authorization: Bearer eyJ...X0=" http://34.xx.yy.19:3000/api/datasources/name/elasticsearch, it looked like:
{
  "id": 1,
  "orgId": 1,
  "name": "kag-el1",
  "type": "elasticsearch",
  "typeLogoUrl": "",
  "access": "proxy",
  "url": "https://vpc-kag-el1-sgshjf7eq7mhhyllggkdgynhpu.us-east-1.es.amazonaws.com",
  "password": "",
  "user": "",
  "database": "metricbeat-*",
  "basicAuth": false,
  "basicAuthUser": "",
  "basicAuthPassword": "",
  "withCredentials": false,
  "isDefault": true,
  "jsonData": {
    "esVersion": 56,
    "keepCookies": [],
    "maxConcurrentShardRequests": 256,
    "timeField": "@timestamp"
  },
  "secureJsonFields": {},
  "version": 3,
  "readOnly": true
}

Based on it and link @paulfantom provided above I've set config to use with Ansible:
    grafana_datasources:
    - name: elasticsearch
      type: elasticsearch
      access: proxy
      url: "https://vpc-kag-el1-sgshjf7eq7mhhyllggkdgynhpu.us-east-1.es.amazonaws.com"
      basicAuth: false
      database: "metricbeat-*"
      isDefault: true
      jsonData:
        esVersion: 56
        maxConcurrentShardRequests: 256
        timeField: "@timestamp"

Hope it will help somebody)

authors: kagarlickij paulfantom

repo: cloudalchemy/ansible-grafana


text:
12730 add remsh script

The remsh pattern is quite useful for connecting to running nodes for
debugging production issues. This adds a small script that lets users
connect quickly to a running node.

I should note the two caveats to this.
The first is that setting the cookie is a bit wonky. I think there might be some love in setting it via ./configure with the default of monster like we have now and including that both places.
The second is that the node name has to be set to match the short/long versions of the node. Ie, the simplest invocation is:
$ ./rel/dev1/bin/remsh davisp@127.0.0.1

Not sure if that's an issue or not.

the cookie thing is an issue for me. I  always use the value in .erlang-cookie when running BigCouch locally.

Oh for your shells. @bdionne And -setcookie overrides the .erlang.cookie?

I've been annoyed by the need to supply a name when connecting.  Can we get the script to generate a name automatically?

@bdionne Cookie support is better. Let me know if it works for you.
@kocolosk No more need for you to specify insightful names like a or aa or even aaaaaaa when using this script.

LGTM.  Squash the bugfix before merging.

authors: bdionne davisp kocolosk

repo: cloudant/bigcouch

license_source: bigquery


text:
Network index is off by 1 on HP Cloud

Testing on HP Cloud showed that the network index used was off by 1.
Bump it so that the plugin works correctly with HP Cloud.

Looking more closely and it seems the network matching needs improvement generally.  Will look at making a more complete change for this.

repo: cloudbau/vagrant-openstack-plugin

license: mit


text:
🛑 cbn.id is down

In be4201b, cbn.id (https://cbn.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cbn.id is back up in 669ea81.

repo: cloudbip/upptime


text:
🛑 lintas.net.id is down

In 7c28d80, lintas.net.id (https://lintas.net.id) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lintas.net.id is back up in c25bde8 after 13 minutes.


text:
🛑 idnix.net is down

In 8e244ce, idnix.net (https://idnix.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: idnix.net is back up in b954278.


text:
Results not visible in Notebook table format

Bug
Hue intermittently shows results in table format for a Notebook. It has shown to happen when the user executes a query in a Notebook (first time it works) then executes a query in the Hive editor and then returns to the Notebook. When they execute a query after returning to the Notebook the issue happens. The image below shows what happens when you first execute a query on the Notebook(results in table format as expected):

However, after returning to the Notebook (as described above) and executing the same query (or any other query) the following happens:

Hue version: 4.8.0
No logs appear on the browser console or on the server logs for this issue.

Yes, those are old flaky issues like this in Editor 1. Editor 2 is coming this year without those.
It runs on beta at demo.gethue.com/

Hi, @romainr thanks for your response. Will update when Editor 2 is available.

Hi, I am using Hue 4.10.0, and I find this issue still exists, so Editor2 is not available in 4.10.0? And what about 4.11 ?

Hi @sumtumn, editor v2 is now (current master branch) available behind feature a flag called "enable_hue_5=true" in the file desktop/conf/pseudo-distributed.ini under section [desktop]. Previously the flag was called "enable_notebook_2" but I'm not sure if it was supported in 4.10, you can try and have a look. Just update the config and restart Hue.

authors: bjornalm ghost joemonaghan-iw romainr sumtumn

repo: cloudera/hue


text:
Update transfer-uk-domain.md

Clarifying that a reason for failure of the transfer could be that the domain is set to expire or renew within the next 10 days, and clarifying that it mustn't be renewing (in the next 10 days) in the prerequisites.

Im blue double you, eiffel down

authors: AbsoluteZeroist misterjaytee

repo: cloudflare/cloudflare-docs


text:
modify log level of message

https://github.com/cloudflare/pingora/issues/201

closing this PR since it looks like there is a code bug in pingora itself causing the actual issue to be addressed.

repo: cloudflare/pingora


text:
HTTP/3 Patch for Nginx 1.18.0 stable ?

Curious if there's any plans to bump up or release a HTTP/3 patch for latest Nginx stable which moved from 1.16.1 to 1.18.0 http://nginx.org/en/download.html ?

good idea

And now 1.19.0.

@Wsget Nginx 1.19.0 is the mainline version, but I'd also like to see support for it.

Thanks @ghedo. Your comment gave me confidence to test it out.
We tested the patch against nginx 1.19.2 version and it seemed to work. We released an edge docker image containing latest nginx with quiche (ranadeeppolavarapu/nginx-http3:edge). Please feel free to test and play around with it to your liking.

Looks like we can close this.

The current patch file does not work anymore due to the removal of post_accept_timeout in the core, https://github.com/nginx/nginx/commit/2ec8fac2d6b8e5023c9894d10bc50d78e63f242c.

A sketch for nginx >= 1.19.7 (that has not been released yet) is here [1] and the derived patch is contained here [2].
[1] https://github.com/marinelli/nginx/tree/quiche-nginx-1.19.7
[2] https://github.com/marinelli/quiche/tree/quiche-nginx-1.19.7

1.19.7 is released now

compiled failed with 1.19.7

A preliminary patch is available in Zestginx but needs a follow-up as per the comment on line 364.
https://github.com/ZestProjects/zestginx/commit/977f2a9ec71053108aa4271f613c63704f00a3b5

authors: RanadeepPolavarapu Wsget ajs124 centminmod ghedo haohetao kn007 lazerl0rd marinelli whalehub

repo: cloudflare/quiche


text:
Add idp_entity_id, public_key and sso_endpoint attributes to cloudflare_access_application.saas_app

Closes #2812

acceptance tests all passing, thank you! 🥇
TF_ACC=1 go test ./internal/sdkv2provider -v -run "^TestAccCloudflareAccessApplication_" -count 1 -timeout 120m -parallel 1
=== RUN   TestAccCloudflareAccessApplication_BasicZone
--- PASS: TestAccCloudflareAccessApplication_BasicZone (9.72s)
=== RUN   TestAccCloudflareAccessApplication_BasicAccount
--- PASS: TestAccCloudflareAccessApplication_BasicAccount (9.37s)
=== RUN   TestAccCloudflareAccessApplication_WithCORS
--- PASS: TestAccCloudflareAccessApplication_WithCORS (9.61s)
=== RUN   TestAccCloudflareAccessApplication_WithSaas
--- PASS: TestAccCloudflareAccessApplication_WithSaas (9.76s)
=== RUN   TestAccCloudflareAccessApplication_WithAutoRedirectToIdentity
--- PASS: TestAccCloudflareAccessApplication_WithAutoRedirectToIdentity (11.23s)
=== RUN   TestAccCloudflareAccessApplication_WithEnableBindingCookie
--- PASS: TestAccCloudflareAccessApplication_WithEnableBindingCookie (9.52s)
=== RUN   TestAccCloudflareAccessApplication_WithCustomDenyFields
--- PASS: TestAccCloudflareAccessApplication_WithCustomDenyFields (9.37s)
=== RUN   TestAccCloudflareAccessApplication_WithADefinedIdps
--- PASS: TestAccCloudflareAccessApplication_WithADefinedIdps (10.93s)
=== RUN   TestAccCloudflareAccessApplication_WithMultipleIdpsReordered
--- PASS: TestAccCloudflareAccessApplication_WithMultipleIdpsReordered (22.04s)
=== RUN   TestAccCloudflareAccessApplication_WithHttpOnlyCookieAttribute
--- PASS: TestAccCloudflareAccessApplication_WithHttpOnlyCookieAttribute (10.39s)
=== RUN   TestAccCloudflareAccessApplication_WithHTTPOnlyCookieAttributeSetToFalse
--- PASS: TestAccCloudflareAccessApplication_WithHTTPOnlyCookieAttributeSetToFalse (8.81s)
=== RUN   TestAccCloudflareAccessApplication_WithSameSiteCookieAttribute
--- PASS: TestAccCloudflareAccessApplication_WithSameSiteCookieAttribute (9.22s)
=== RUN   TestAccCloudflareAccessApplication_WithLogoURL
--- PASS: TestAccCloudflareAccessApplication_WithLogoURL (14.14s)
=== RUN   TestAccCloudflareAccessApplication_WithSkipInterstitial
--- PASS: TestAccCloudflareAccessApplication_WithSkipInterstitial (9.19s)
=== RUN   TestAccCloudflareAccessApplication_WithAppLauncherVisible
--- PASS: TestAccCloudflareAccessApplication_WithAppLauncherVisible (12.82s)
=== RUN   TestAccCloudflareAccessApplication_WithSelfHostedDomains
--- PASS: TestAccCloudflareAccessApplication_WithSelfHostedDomains (9.32s)
PASS
ok  	github.com/cloudflare/terraform-provider-cloudflare/internal/sdkv2provider	176.417s


text:
IMAGES-1258: Don't pollute global scope with generally named types

Fixes #2537

Would be good to see this merged soon if possible 👀

repo: cloudflare/workerd


text:
merge isAsciiWhitespace implementations

Merges 2 implementations and introduces 2 new cc_library targets on bazel.

...just in case...


text:
🐛 BUG: Incorrectly erroring for multiple outbound mocks for vitest pool worker

Which Cloudflare product(s) does this pertain to?
Workers Vitest Integration
What version(s) of the tool(s) are you using?
0.1.12
What version of Node are you using?
20.11.0
What operating system and version are you using?
macOS Sonoma 14.4.1
Describe the Bug
Observed behavior
Incorrectly reporting conflicting miniflare errors
MiniflareCoreError [ERR_MULTIPLE_OUTBOUNDS]: Only one of `outboundService` or `fetchMock` may be specified per worker

Config:
import { defineWorkersConfig } from "@cloudflare/vitest-pool-workers/config";
import { MockAgent } from "undici";

const mockFetch = new MockAgent()

export default defineWorkersConfig({
  test: {
    poolOptions: {
      workers: {
        singleWorker: true,
        miniflare: {
          compatibilityDate: "2024-01-01",
          compatibilityFlags: ["nodejs_compat"],
          serviceBindings: {
            WORKER: "test-worker",
          },
          workers: [
            {
              name: "test-worker",
              modules: true,
              compatibilityDate: "2022-11-30",
              compatibilityFlags: ["nodejs_compat"],
              scriptPath: "./worker.js",
              fetchMock: mockFetch,
            }
          ]
        }
      },
    },
  },
});

Expected behavior
No error when trying to run tests
Steps to reproduce
Please see reproduction repo
Please provide a link to a minimal reproduction
https://github.com/tyler-goodwin/miniflare-fetch-mock-repro
Please provide any relevant error logs
npm test

> miniflare-fetch-mock-repro@1.0.0 test
> vitest

 DEV  v1.3.0 /Users/tgoodwin/work/miniflare-fetch-mock-repro

[vpw:inf] Starting single runtime for vitest.config.js...

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Errors ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

Vitest caught 1 unhandled error during the test run.
This might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Error ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
MiniflareCoreError [ERR_MULTIPLE_OUTBOUNDS]: Only one of `outboundService` or `fetchMock` may be specified per worker
 ❯ Object.transform node_modules/miniflare/dist/src/index.js:6401:13
 ❯ ZodEffects._parse node_modules/zod/lib/types.js:3050:39
 ❯ ZodEffects._parseSync node_modules/zod/lib/types.js:129:29
 ❯ ZodEffects.safeParse node_modules/zod/lib/types.js:159:29
 ❯ ZodEffects.parse node_modules/zod/lib/types.js:140:29
 ❯ parseWithRootPath node_modules/miniflare/dist/src/index.js:3889:19
 ❯ validateOptions node_modules/miniflare/dist/src/index.js:8056:36
 ❯ new Miniflare node_modules/miniflare/dist/src/index.js:8405:38
 ❯ getProjectMiniflare node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1214:20
 ❯ Object.runTests node_modules/@cloudflare/vitest-pool-workers/dist/pool/index.mjs:1460:26

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
Serialized Error: { code: 'ERR_MULTIPLE_OUTBOUNDS' }
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 Test Files  no tests
      Tests  no tests
     Errors  1 error
   Start at  15:07:05
   Duration  59ms (transform 0ms, setup 0ms, collect 0ms, tests 0ms, environment 0ms, prepare 0ms)

 FAIL  Tests failed. Watching for file changes...
       press h to show help, press q to quit
[vpw:dbg] Shutting down runtimes...

This seems to be because we parse Miniflare's config before starting up Miniflare, and then pass that parsed config to Miniflare when starting up the test runner. I don't think that's necessarily correct—as this issue shows the config is not necessarily roundtripable. I suspect we should either:

Not parse Miniflare's config outside of Miniflare, or
Remove Zod transform() calls in Miniflare's config, to make it roundtripable
I think the first option is probably the best, but it will require some investigation to see why we were parsing the config outside of Miniflare in the first place.

authors: penalosa tyler-goodwin

repo: cloudflare/workers-sdk


text:
toml editor

There are numerous occasions when we want to be able to 'automatically' edit the wrangler.toml file from withiin wrangler. Examples -

removing a deprecated field like type
renaming a deprecated field like build.upload.main to something like entry (todo)
adding durable object migrations based on some interactive flow (todo)

In rust land, we'd use a format preserving editor like toml-edit, but nothing like it exists in javascript land (that I know of). So this issue tracks the implementation of the thing.
We need to take a toml parser that given a toml string, returns an AST. We then apply edits to the AST directly, and convert it back to a toml string.
Potential code to learn from - https://github.com/ota-meshi/toml-eslint-parser
Sequencing / prioritisation: I think when we should first start simply logging the changes we want people to make directly to the terminal (for backward compat, migrations, whatever.) Once we have that in place, we can start working on this issue to automate the suggestions.

Consider using https://taplo.tamasfe.dev/lib

Other options:

https://www.npmjs.com/package/tree-sitter-toml (uses C-based tree-sitter tool). See https://tree-sitter.github.io/tree-sitter/playground
https://www.npmjs.com/package/@toml-tools/parser (sadly needs a new maintainer)

https://www.npmjs.com/package/@toml-tools/parser (sadly needs a new maintainer)

Seems like the library was mostly leveraging this which seems still highly maintained. The rest of the toml parser can be implemented using https://github.com/chevrotain/chevrotain and the parsing rules for TOML & change the API as needed.
Assuming we don't find something else that works well for our needs.

Hello.
I am the author of both Chevrotain and @toml-tools/parser.
Some questions:

Do I understand correctly that you need to make small modifications to an existing toml file, while honoring the
existing formatting / style (no full document re-write on change)?

Do you have any future "true editor" requirements in regards to the wrangler.toml file? e.g:

A VSCode extension that supports some semantic validations and content assist for wrangler.toml files?

Cheers.
Shahar.

Yes to both!

Yes to both!

Graceful automated editing
Chevrotain could be well suited as an infrastructure for this due to the CST (Concrete Syntax Tree) support.
Basically it can auto-magically output a (verbose) structure that includes all the syntax details beyond what normally exists in an AST, for example in JSON:

exact locations of commas / brackets  in a JSON
exact location of properties as opposed to only their names.

See: JSON + CST example in the playground

https://chevrotain.io/playground/

TOML Parser / Grammar
As far as I remember, TOML is a very simple language (it has obvious and minimal in the name...)

Grammar
Spec

So implementing a parser for it should not be too large of an undertaking and there is already prior work to build on:

https://www.npmjs.com/package/@toml-tools/lexer
https://www.npmjs.com/package/@toml-tools/parser

Full fledged Editor (Semantic Validations / Content Assist / Tool-tips)
This is a fair bit more complicated.
You would need to implement a Language Server for your wrangler.toml syntax/semantics.

https://microsoft.github.io/language-server-protocol/

I have worked on a similar problem for SAP's UI5 XML webviews.

VSCode marketplace link - has GIFs...

The relevant source code is in these two repos:

https://github.com/SAP/xml-tools (the generic XML parts and infrastructure)
https://github.com/SAP/ui5-language-assistant (builds on-top of xml-tools for the UI5 specific parts)

Language Server infrastructure to evaluate
Langium by Typefox is a new framework that assists in building language servers for DSLs.
I have not used it personally and it is at an early stage, however, it may be worth investigating as it could theoretically greatly simplify the full fledged editor problem.

https://github.com/langium/langium
https://tomassetti.me/quickly-create-dsls-with-langium/

@msujew may be able to elaborate more on this option?

Hey @bd82, thanks for the heads-up!
If it's only about editor support, I think Langium would be a good choice. Looking at the initial requirements, especially removing deprecated fields should be as simple as writing a validation and executing an associated code action (as in: Executing a quick fix provided by VSCode for unused imports for example).
Langium's main use case is to build a language server, so its editing interfaces are tightly coupled to the LSP types. However, everything is also working in CLI/normal app server mode, so once you conform to the LSP types, stuff like executing code actions should also be working fine. Although, we mostly just use the parsing and validation capabilities of Langium when running CLIs. Thinking about it, you probably don't even need to go through the LSP interfaces and can just work on the AST/CST itself, kind of mimicking how editors execute code actions.
It might be a bit tricky to get the toml grammar to work correctly in Langium (mostly about lexing, parsing shouldn't be an issue, white space sensitive languages are always a bit difficult to deal with), but definitely possible. However, after that's done, everything else should be straightforward, since semantic validations, content assist, tool-tips, etc. as mentioned by Shahar come out-of-the-box with minimal effort with Langium.

Closing this, since we're moving Wrangler's config to a JSONC format, and the library we use for that supports editing files (preserving comments).

authors: JacobMGEvans bd82 msujew penalosa petebacondarwin threepointone


text:
No docker manifest other than v24

Commit removed releases because of encryption  breaks any cf deployment using docker other than v23 and earlier.
Why did You removed them?
You could added v24 first and wait few day. Some kind of announcement about planned removal would by also appropriate.

hey @tproot sorry about this please refer to http://bosh.io/releases/github.com/cf-platform-eng/docker-boshrelease?all=1 for old releases

Long, perhaps link in the cf-bosh@ mailing list article that explains why
you were forced to delete all the old files to help explain.

This should explain why we had to remove old files. https://lists.cloudfoundry.org/archives/list/cf-bosh@lists.cloudfoundry.org/thread/H365YFWROOHGOGBGLPBNWT7LLBGBIQEB/

I believe this issue is resolved.

authors: drnic longnguyen11288 tproot


text:
Delete npm-debug.log

Remove npm-debug.log

doh

actually, should add npm-debug.log to .gitignore.  Now that it's been deleted :-)

authors: germanattanasio pmuellr

repo: cloudfoundry-community/node-cfenv


text:
Broker should expose an option to mandate server_side_encryption

The broker should expose an option that applies this policy to brokered buckets for applications that need to ensure all data in their buckets is encrypted at rest.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "DenyUnencryptedPut",
            "Effect": "Deny",
            "Principal": {
                "AWS": "*"
            },
            "Action": "s3:PutObject",
            "Resource": ":BUCKET-ARN:/*",
            "Condition": {
                "StringNotEquals": {
                    "s3:x-amz-server-side-encryption": "AES256"
                }
            }
        }
    ]
}

Another candidate for pairing with @jseppi.

authors: cnelson jmcarp


text:
Add HTTP proxy support to install windows updates

it would be great Install-WindowsUpdates could take a flag that could allow you to specify http/https proxy to get out to the windows updates servers.
I ran into this in a client environment. As a temporary workaround I added
netsh winhttp set proxy proxy-server="http=proxy..com:80;https=proxy..com:80" bypass-list="*.noproxu.com"
as the fist command in the install-windowsUpdates function @ https://github.com/cloudfoundry-incubator/bosh-windows-stemcell-builder/blob/master/bosh-psmodules/modules/BOSH.WindowsUpdates/BOSH.WindowsUpdates.psm1#L41

Hey @DaxterM, I assume you're still using the approach mentioned above? Do you still feel like it's a temporary workaround or has it been easy to maintain?

@crawsible  it's easy to maintain but requires forking  which makes it difficult to consume updates.  If other clients use this repo to automate the stemcell creation process I imagine they will run into this.

Ah, sorry, I didn't realize this required forking. Seems like a pretty straightforward change; I'll prioritize it.

I also need this feature.  Any idea when this might happen?

@cdelashmutt-pivotal We're hoping to get to it within the next two weeks.

authors: DaxterM cdelashmutt-pivotal crawsible


text:
Add staging info for the buildpack

extract parts to different files

[#167706394]

looks like we have got test pollution since we switched to randomized testing. units failed twice on different tests.

I'll try to fix it with someone tomorrow.
ср, 21 серп. 2019, 18:08 користувач Nima Kaviani notifications@github.com
пише:

looks like we have got test pollution since we switched to randomized
testing. units failed twice on different tests.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry-incubator/eirini-staging/pull/4?email_source=notifications&email_token=ABBOU3OGWWCLJP2J4DAWAHDQFVZADA5CNFSM4IOIDUS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD42NGKY#issuecomment-523555627,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBOU3MVVWF7JZIA7V3EA73QFVZADANCNFSM4IOIDUSQ
.

We have fixed unit tests in master and integration test in this branch.

authors: akshaymankar alex-slynko nimakaviani

repo: cloudfoundry-incubator/eirini-staging


text:
Add aws cloud provider for Windows nodes

Adds an opsfile for Windows workers running on AWS.
Here's the opsfile set I've been using for deploying on AWS with a director deployed with https://github.com/cloudfoundry/bosh-bootloader/tree/master/plan-patches/cfcr-aws
bosh -d cfcr -n deploy ~/workspace/kubo-deployment/manifests/cfcr.yml \
  -v kubo-version=latest \
  -v kubo-windows-version=latest \
  -v windows-rdp-password="Foobar123!" \
  -v windows-stemcell-version=latest \
  -v deployment_name=cfcr \
  -v windows_worker_vm_type=large \
  -v master_vm_type=default \
  -v worker_vm_type=default \
  -v apply_addons_vm_type=default \
  -o ~/workspace/kubo-deployment/manifests/ops-files/misc/single-master.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/allow-privileged-containers.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/misc/version.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/vm-types.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/use-vm-extensions.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/add-hostname-to-master-certificate.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/misc/scale-to-one-az.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/iaas/aws/cloud-provider.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/iaas/aws/lb.yml \
  -l <(bbl outputs --state-dir ~/workspace/environments/aws) \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/add-worker.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/use-overlay.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/enable-rdp.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/version.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/stemcell.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/vm-types.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/iaas/aws/windows/cloud-provider.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/use-vm-extensions.yml \
  -o ~/workspace/kubo-deployment/manifests/ops-files/windows/scale-to-one-az.yml

An important note with AWS is that we've discovered a bug with Windows networking and AWS' Enhanced Networking feature. We need to avoid these VM types (C3, C4, D2, I2, M4 (excluding m4.16xlarge), and R3) for now. I'm using m5.xlarge for my Windows VMs.

Adding this commit to https://github.com/cloudfoundry-incubator/kubo-deployment/pull/397

hi @benmoss  I am trying to add a windows-worker node on cfcr cluster on AWS. But facing the below error:

Can you guide me with this and let me now if aws support is enabled for cfcr ?

repo: cloudfoundry-incubator/kubo-deployment


text:
Informing clustered aws lattice of private docker registry (doesn't have to be secure)

Hi I'm trying to setup a Lattice for internal apps within my org. So the networking is setup to totally shield lattice VPC within the company walls (no public ips or whatnot). Got me a vm running a private docker registry. Wanna tell the lattice about it. I did this
For every cell:
ssh ubuntu@private-ip-of-cell
sudo vi /etc/init/garden-linux.conf
# add the insecureDockerRegistryList="10.PRIVATE_IP:5000" line
sudo initctl stop garden-linux && sudo initctl start garden-linux

But that doesn't survive re-creating the vms of course, so I'd love a more declarative way. Maybe theres some way to parametrize the terraform stuff? or any other way of informing the cells of private registry.

Hi @sergueif,
We have a story to automate a lot of the work described on the private docker registries page in story #92186438.
This work will include configuration of the Lattice cluster to reach a well-known location for a private docker registry.
OK to wait until we get to this feature? It's coming up after the current epic that we're working on.
--
Marco Nicosia
Product Manager
Pivotal Software, Inc.

Yes, it can wait. I managed to get a private registry in by modifying the provisioning somewhat.

Lattice was a Cloud Foundry project focused on delivering the Diego application scheduler into the hands of users as quickly as possible before Diego was fully integrated to Cloud Foundry. Lattice served that purpose well, but now Diego is available as the application scheduler for Cloud Foundry, and Cloud Foundry is the best way to use Diego. Therefore, Lattice is no longer actively maintained.
Apologies for not addressing your issue.
-Stephen

authors: menicosia sclevine sergueif

repo: cloudfoundry-incubator/lattice


text:
Add dns_config into the cf template

Hi:
We'd like to be able to config consul.agent.dns_config.allow_stale in our stub file, so that we can use the feature here
Could you help review the PR?
With many thanks.

Hi @Kaixiang
This will likely fail the unit tests.  You may wish to run ./scripts/setup-git-hooks, more generally check out the tips in CONTRIBUTING.md.  Do you mind fixing so the tests pass, and submitting as a single squashed commit that passes tests?
Thanks,
Amit

@Amit-PivotalLabs , we've changed the test, we run rspec and everything passed locally.
see if this works.

Thanks Kai, saw that. Already prioritized for the team to merge.
Best,
Amit
On Wednesday, September 21, 2016, Xiang Kai notifications@github.com
wrote:

@Amit-PivotalLabs https://github.com/Amit-PivotalLabs , we've changed
the test, we run rspec and everything passed locally.
see if this works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/cf-release/pull/1052#issuecomment-248736469,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC9t3gKA0krwuHlDzHNf5rEbqlWi6kFBks5qsZaQgaJpZM4J4RYg
.

authors: Amit-PivotalLabs Kaixiang

repo: cloudfoundry/cf-release


text:
JRebel improvements

Changes:

Add support for packaged servers and server directories
Add support for EAR apps

I also had to change some code in liberty.rb in order to expand WAR archives that are inside EAR archives deployed to packaged servers or server directories. Previously, the way it worked was that the EARs were expanded during the compile phase, where as the WARs inside them were expanded in the release phase (because only then was Dir.glob able to find them). This also caused Liberty.apps to return different results during the two phases.

I believe you should already have my CLA.

Thanks! Two comments:

Why the change the liberty.rb?
In jrebel_agent.rb it might be easier just to search for #{@app_dir}/**/WEB-INF/classes/rebel-remote.xml". Yes, that might find some apps that have this file but not actually be a war file. But I doubt we will have a lot of such cases. Besides, packaged servers or server directories usually contain the application files in the apps directory and not the dropins directory.

The change in liberty.rb was needed in order to expand WAR archives that are inside EAR archives. Previously the EARs were expanded in the compile phase, and then the WARs in the release phase. This, however, prevented us from finding rebel-remote.xml files (which we need to do in the compile phase).
I will simplify my changes to just search for #{@app_dir}/**/WEB-INF/classes/rebel-remote.xml like you suggested.

Ok. In that case something like this should work also (and be a little simpler):
 server_path = File.dirname(server_xml)
 ears = Dir.glob("#{server_path}/**/*.ear")
 Liberty.expand_apps(ears)
 wars = Dir.glob("#{server_path}/**/*.war")
 Liberty.expand_apps(wars)
 apps_found = ears + wars

I was just unsure whether Liberty.apps should also return the WARs that are inside EARs or not. Previously, it did not return them in the compile phase, where as it did return them in the release phase.
Seeing as in the case where the user deploys a standalone EAR app (i.e. not a server directory / packaged server) the WARs inside are never returned, then I figured it makes sense to not return them here either.
The question is simply which is the correct behaviour? My code chooses to never return WARs, where as your code always does.
(To be clear, the JRebel integration only cares about what is expanded, not about what is returned from Liberty.apps.)

The results of Liberty.apps are not really used anywhere except in a couple of tests. This function is primarily used for expanding the ear & war files and the way it is currently written it would return different results depending on when it was called. So, for now, go ahead with the change I suggested and we'll clean it up better later.

The whitelist has been updated to include dmitri-gb.  You can accept their pull request.

Great. @dmitri-gb can you squash your commits?

Done.

Awesome. Thanks!

authors: dmitri-gb jgawor mjear


text:
Invalid stderr message from metron

2017/03/14 15:53:57 failed to write to Doppler: write udp4 127.0.0.1:40736->127.0.0.1:0: write: connection refused

The destination address (127.0.0.1:0) should have a valid port. This code path would never work if it was trying to write to port 0, so it seems that the log messages is invalid.
/cc @apoydence

We see that this may occur in tests but not in production code. Closing until we see this happen in production code.

authors: bradylove jtarchie

repo: cloudfoundry/loggregator


text:
Restore VCAP_APP_PORT for build pack applications

During the migration from DEA to Diego, we found a number of node.js applications failed to start on Diego. It turns out that most of them are using VCAP_APP_PORT to discover the port to listen on.
This change will populate VCAP_APP_PORT in build pack applications but won't propagate it to docker apps.

It appears this function is being moved into the CC as part of #120643929. Given that has not yet landed, I opened the PR here for discussion.
Thanks.

@socalnick any comments? We need VCAP_APP_PORT back for our migration.
Thanks.

Hi @sykesm,
Any chance this could be documented for your node users? It's documented in the OSS guide to migrate apps to Diego: https://docs.cloudfoundry.org/running/apps-enable-diego.html#app-code

@socalnick @sykesm It is documented but in particular for apps where users didn't actually make code edits (i.e. NodeRed) asking them to do it for a forced migration is difficult.  Also note it's not specific to node - it breaks a python app I have.  The use of VCAP_APP_PORT was heavily documented, thought in tutorials and put forward in sample code.  Removing it breaks stuff.

As @MaeveOReilly indicated, it has been documented but since it is often buried in libraries and supporting frameworks, it's not always obvious what needs to change or what is impacted by the change. The number of applications that are impacted by this is not small.

@MaeveOReilly I don't see where NodeRed has ever used VCAP_APP_PORT, the commit that removed the port being hardcoded uses PORT.
The Migrating Apps to Diego Guide is very explicit about this environment variable being removed. I asked around and was given these links showing this has been coming since 2014:
2014-12-23 Tracker Story
2015-09-18 Diego Design Notes
2016-01-01 CF Dev Guide

Hi @SocalNick
when run in Bluemix, we use a custom settings file in order to point node-red at a database service rather than use the local filesystem. That custom settings file only recently got updated to remove the dependency on VCAP_APP_PORT - https://github.com/ibmets/node-red-bluemix/blob/master/public/app/bluemix-settings.js#L27 - because I only recently became aware of the impending change.
The problem from my perspective is that our users don't know anything about Diego. They have deployed an application to the Bluemix environment and expect it to keep working. They are not application developers themselves - they are users of node-red, not developers of CF applications.  They will not understand the significance of the removal of VCAP_APP_PORT.
Node-RED is just an example - I don't want to get too wrapped up in its specifics. There will be significant numbers of other users who will get tripped up by this. There is, in my opinion, a more fundamental principle here about not breaking user's applications which can be largely avoided by keeping this environment variable in place.

@SocalNick - the commit for Bluemix was actually this one about a month ago now.
I think what @MaeveOReilly and @sykesm are suggesting is that cf app "owners" have often not coded anything themselves, or have pulled in packages that use this env var, as is the case with the Node-Red Bluemix project, so documenting alone is not enough;  removing VCAP_APP_PORT will break at least some apps that have been running happily for some time, even if the owners are aware of Diego, but have not checked their dependencies.
Seems an easy win to simply leave VCAP_APP_PORT there.  What are the down sides ?

@knolleary @slaupster if the app owners aren't writing the apps themselves, how do you all roll out bug fixes, security fixes, or general improvements?
There's at least one workaround, but it's an experimental feature. I highly recommend finding a way to fix these apps to use $PORT.
https://github.com/cloudfoundry/diego-release/blob/develop/jobs/rep/spec#L171-L174
So in your Diego deployment manifest:
diego.executor.post_setup_hook: "sh -c \"echo 'export VCAP_APP_PORT=$PORT' >> /home/vcap/app/.profile\""
diego.executor.post_setup_user: "vcap"

@SocalNick Asking people to fix their applications is a sure-fire way to bring dissatisfaction with Cloud Foundry as a platform. While the change may seem trivial, many users do not want to have to go back and make a change to an application that is working just fine. Especially when they followed documented practices. Migration to Diego should not break backward compatibility like this, and there is no (as I can see it) strong justification for removing this environment variable and causing disruption to so many users. At minimum they will have to make code changes and do a re-deploy. At worst they will suffer an outage as their app is forcibly migrated to Diego.
Please can we have some pragmatic solution here and restore the VCAP_APP_PORT as a legacy compatibility? Thank you!
cc @sykesm

@sykesm I've dragged this over to our backlog, would you mind sending some PRs to docs to reflect that this environment variable is being reintroduced?

@SocalNick is CAPI going to do the work in the CC or do you want us to rework the PR there since https://www.pivotaltracker.com/story/show/120643929 has landed?

@sykesm we did this in the CC as well: https://github.com/cloudfoundry/cloud_controller_ng/commit/7fc57bd8584dc8209759a091b138f1b6a42d25a1

Thanks, @SocalNick.

authors: MaeveOReilly SocalNick knolleary slaupster sykesm univ0298

repo: cloudfoundry/nsync


text:
Bump ginkgo v2

Feature or Bug Description
Bump from ginkgo/v1 to the latest ginkgo v2.9.0 and updates any existing ginkgo/v2 uses to v2.9.0
Motivation
Bumping dependencies.  This should address some of the outstanding security flags for some of the outdated Go deps used by this project and consistently use the latest Ginkgo v2 testing framework across components in pxc-release.

overall this looks good to me for merging - not sure if we want any more eyes on it for a review?
the changes all look fairly straightforward, the bulk of the changes are new vendored dependencies and updating the import statements
using the "go run" syntax as advertised in the ginkgo docs where possible, updating from how we were previously vendoring it in via a tools.go file
all CLI flags are updated to kebab case from camel case
ready to merge if we don't need more reviews

Merged.  Thanks for looking it over @ryanwittrup

authors: abg ryanwittrup

repo: cloudfoundry/pxc-release


text:
Stop pinning golang.org/x/sys

Description
Couldn't find any history related to pinning this dependency, and it was
a long time ago. We should unpin this.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] This PR is being made against the main branch, or relevant version branch

Superseded by #19

repo: cloudfoundry/system-metrics-release


text:
Authorization Request Error, There was an error. The request for authorization was invalid

Checked UAA code and modified all occurrences of "localhost" pattern with ip address (X.X.X.X) in the following files:
o	login.yaml  (located in "uaa/uaa/src/main/resources/login.yml")
o	application-local.properties (located in "uaa/samples/app/src/main/resources")
o	application.properties (located in "uaa/samples/api/src/main/resources")
o	export UAA_PROFILE=local and ran the ./gradlew run; UAA server setup is working fine with public ip address  http://X.X.X.X:8080/uaa/login (marissa/koala)
o	Browsed the http://X.X.X.X:8080/app/apps. According to sample application instructions it's redirects to user login and able to login with (marissa/koala)
Issue:
o	After login it has to ask user to authorize, but it's failed by throwing below error:
Authorization Request Error: "There was an error. The request for authorization was invalid"
o	Please let me know if anything went wrong in the above steps or advice steps required to test the  authorization code flow end-to-end

Resolved the issue by running the below command in uaa directory and ran the ./gradlew run
Command: find . -type f -exec sed -i "" -e "s#http://localhost#http://your-ap-address#g" 2> /dev/null {} ;

two system properties should suffice
-Dlogin.url=http://yourip:8080/uaa
-Duaa.url=http://yourip:8080/uaa

repo: cloudfoundry/uaa