GAM Export to CSV

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When exporting GAM information to CSV, it combines everything in the first column.  Splitting by the "," is not a great option and often doesn't work.  The only way I have found to fix this issue is by re-importing the export and then re-exporting using Powershell.  A better way to export to CSV and see your information would be better.

Commands I am using to fix this:
#Exports the data
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Using Powershell to re-import so I can export again and each column appear in it's own column
$GAMDevices = import-csv C:\GAM\Exports\GAM-Devices.csv
$GAMDevices | Export-csv c:\GAM\Reports$GAM-Devices-Formatted-Correctly.csv
Describe the solution you'd like
A clear and concise description of what you want to happen.
Better Export to CSV Funcationality.  Opening a CSV and all the data is in the first column is frustrating.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Better Export to CSV Funcationality.  Opening a CSV and all the data is in the first column is frustrating.
Additional context
Add any other context or screenshots about the feature request here.

A CSV file has columns separated by commas which is what GAM produces.
The program that reads the CSV files needs to interpret the comma as a column separator.
Try: $GAMDevices = import-csv C:\GAM\Exports\GAM-Devices.csv -Delimiter ,
Ross
Ross Scroggs
@.***

On May 30, 2024, at 8:00 AM, OldManWindowsGuy @.***> wrote:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
When exporting GAM information to CSV, it combines everything in the first column. Splitting by the "," is not a great option and often doesn't work. The only way I have found to fix this issue is by re-importing the export and then re-exporting using Powershell. A better way to export to CSV and see your information would be better.
GAM-Export-CSV.jpg (view on web) https://github.com/GAM-team/GAM/assets/171264888/d40a8d95-35b5-4728-a2a0-e50edcc81fbc
Commands I am using to fix this:
#Exports the data
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Using Powershell to re-import so I can export again and each column appear in it's own column
$GAMDevices = import-csv C:\GAM\Exports\GAM-Devices.csv
$GAMDevices | Export-csv c:\GAM\Reports$GAM-Devices-Formatted-Correctly.csv
Describe the solution you'd like
A clear and concise description of what you want to happen.
Better Export to CSV Funcationality. Opening a CSV and all the data is in the first column is frustrating.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Better Export to CSV Funcationality. Opening a CSV and all the data is in the first column is frustrating.
Additional context
Add any other context or screenshots about the feature request here.
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL2LP5E6C6DRS52NNK3ZE45INAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDKOBYHEZTEMQ.
You are receiving this because you are subscribed to this thread.

Sorry, you misunderstood my comment.  The export to CSV is the issue.  Not the re-importing which fixes the formatting and exporting.
Microsoft Excel is the program I am using to review it, it's all mashed in 1 line and column if I don't use Powershell to fix the formatting....

#Exports the data and results in Excel reading all the data in 1 Column
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Using Powershell to re-import so I can export again and each column appear in it's own column
$GAMDevices = import-csv C:\GAM\Exports\GAM-Devices.csv
Again, when I use Powershell above to re-import into a variable called $GAMDevices, I can export it and it be properl formatted for a spreadsheet program to open the data and each source, in its own Column.
$GAMDevices | Export-csv c:\GAM\Reports\GAM-Devices-Formatted-Correctly.csv
So the issue, is literally the export Piping command to CSV above "GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv".  I can only fix the formatting by the re-import and export using Powershell.  This ">" to csv is just piping it out and doesn't do a great job.

The export to the CSV is not the issue, it's Excel. When you import a CSV file info Excel, you have to tell it that the column delimiter is comma, it often defaults to tab.
Ross
Ross Scroggs
@.***

On May 30, 2024, at 8:28 AM, OldManWindowsGuy @.***> wrote:
Sorry, you misunderstood my comment. The export to CSV is the issue. Not the re-importing which fixes the formatting and exporting.
Microsoft Excel is the program I am using to review it, it's all mashed in 1 line and column if I don't use Powershell to fix the formatting....
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2139945150, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL565YKNWZSCAWUAHYDZE5ASVAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZHE2DKMJVGA.
You are receiving this because you commented.

Send me a Meet/Zoom invitation and I'll help.
ross.scroggs @ gmail.com http://gmail.com/
Ross
Ross Scroggs
@.***

On May 30, 2024, at 8:36 AM, OldManWindowsGuy @.***> wrote:
#Exports the data and results in Excel reading all the data in 1 Column
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Using Powershell to re-import so I can export again and each column appear in it's own column
$GAMDevices = import-csv C:\GAM\Exports\GAM-Devices.csv
Again, when I use Powershell above to re-import into a variable called $GAMDevices, I can export it and it be properl formatted for a spreadsheet program to open the data and each source, in its own Column.
$GAMDevices | Export-csv c:\GAM\Reports\GAM-Devices-Formatted-Correctly.csv
So the issue, is literally the export Piping command to CSV above "GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv". I can only fix the formatting by the re-import and export using Powershell. This ">" to csv is just piping it out and doesn't do a great job.
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2139973788, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL7QHZZXFIQYAFTTKMDZE5BQDAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZHE3TGNZYHA.
You are receiving this because you commented.

I'm a unix and mac user, and gam generates valid CSVs 100% of the time. I load them in excel, in google sheets, etc. Have never seen this problem.
Sounds like it's the issue ross already described, or possibly the file has unix (\n) line endings and your excel is expecting windows (\r\n) endings and getting cranky.

Must be as Daethnir said, it's not that it's not generating a CSV.  It does do that.  But depending on your Spreadsheet tool, Excel doesn't read it without manually having to tell Excel what the eliminator is each time.  Powershell Export-CSV doesn't have this issue the GAM export has and can export to csv just fine and excel open it with it all in its own columns.
Looks like the solution is probably just to add time to my script, export from GAM and use Microsoft to fix the CSV in Excel.

What is: gam version
Ross Scroggs
@.***

On May 30, 2024, at 8:39 AM, daethnir @.***> wrote:
I'm a unix and mac user, and gam generates valid CSVs 100% of the time. I load them in excel, in google sheets, etc. Have never seen this problem.
Sounds like it's the issue ross already described, or possibly the file has unix (\n) line endings and your excel is expecting windows (\r\n) endings and getting cranky.
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2139985630, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYLY4VM5R6BL3TU3WP6DZE5B4FAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMZZHE4DKNRTGA.
You are receiving this because you commented.

GAM version is 6.58

You have standard GAM, it have no ability to change the comma to some other character.
With Advanced GAM, yu can specify that you want tab (for example) to be the column delimiter.
Upgrading is easy: https://github.com/taers232c/GAMADV-XTD3/wiki/How-to-Upgrade-from-Standard-GAM
You would then do:
gam redirect csv C:\GAM\Exports\GAM-Devices.csv columndelimiter "\t"  Print CROS allfields
Ross
Ross Scroggs
@.***

On May 30, 2024, at 11:31 AM, OldManWindowsGuy @.***> wrote:
GAM version is 6.58
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140596609, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL562QIN3JBR2IYFL4DZE5WB7AVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQGU4TMNRQHE.
You are receiving this because you commented.

Actually, looking at the Text Output of the CSV file.  I think I see why Microsoft Excel is not delimiting it automatically.  The GAM export using > to CSV is not encapsulating the information in quotes (i.e. "deviceid", "activeTimeRanges.o.activeTime","serialnumber" and instead is doing this deviceid, activeTimeRanges.o.activeTime,serialnumber).  Powershell must be auto delimiting on the "," and excel is doesn't like that, because a comma alone could be in the cell.  So just dumps into 1 column.
If the GAM tool could export this information quoted, that would probably resolve the Excel Issue seeing it and forcing you to define the delimitor when opening.  Which doesn't work in excel due to some sort of word wrapping.
Take a model information field like this: ASUS Chromebook Flip C214 (EDU), ASUS Chromebook Flip C234 (CANADA CONSUMER) found in the report, having to define when you open the spread sheet, throws off all the columns.
See the output, the top is done by Powershell Export to CSV, which quotes the fields for better delimitation.

Further analysis, it does quote it, but only when the field itself does contain a ",".  so it would be great if this could be updated to always quote "" the data and fields.  Then this would work and have no issues in Excel.

The CSV spec does have rules about when quotes are needed (e.g. a field contains the separator character) but they are not needed except in those cases.
Adding them to every field would add needless overhead; this should not be done, the file is already valid CSV until proven otherwise.

MS Excel is designed to behave this way.  See Microsoft Community post CSV
excel sheets do not open in columns
for more information.
Erik
On Thu, May 30, 2024 at 4:37 PM daethnir @.***> wrote:

The CSV spec does have rules about when quotes are needed (e.g. a field
contains the separator character) but they are not needed except in those
cases.
Adding them to every field would add needless overhead; this should not be
done, the file is already valid CSV until proven otherwise.
—
Reply to this email directly, view it on GitHub
https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140824124, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUNKPFQKX2MOMXGGA3X4VLZE6EXBAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHAZDIMJSGQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you, I understand how to Delimit a file in Excel using that feature.  What I am saying, that doesn't work for the output provided by the GAM tool.....
After manually delimiting on the ",".  I has what should be Columns, showing as rows.... The first 8 rows, are actually supposed to be columns if this was delimiting correctly....

I missed the check box for the headers, but again. this is the problem with manual delimitors.  But it doesn't sound like this is a feature that can be fulfilled as its been determine to be too much over head.
I will use Powershell to re-import the file and correct the issues.  Just create more overhead for my script.
Thanks for the consideration.  It would help windows admins out some trying to use this tool and for things we can't do in the console.

GAM is producing a valid, correctly delimited CSV (Comma Separated Values) file.
The fact that Excel can't read it correctly by default is Excel's problem.
Send me a Meet/Zoom invitation if you'd like to discuss.
Ross
Ross Scroggs
@.***

On May 30, 2024, at 1:55 PM, OldManWindowsGuy @.***> wrote:
Thank you, I understand how to Delimit a file in Excel using that feature. What I am saying, that doesn't work for the output provided by the GAM tool.....
After manually delimiting on the ",". I has what should be Columns, showing as rows.... The first 8 rows, are actually supposed to be columns if this was delimiting correctly....
Excel-Not-Able-To.jpg (view on web) https://github.com/GAM-team/GAM/assets/171264888/2bd880b2-ef2c-4084-b026-8e103cd09cea
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140850747, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL4WTQLFD3IVIUVYBM3ZE6G5ZAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHA2TANZUG4.
You are receiving this because you commented.

We can close this feature request, I was hoping to improve the export.  I was hoping the product could be updated to work more seamlessly with other products like Excel.
Thanks for the consideration.

See: https://superuser.com/questions/606272/how-to-get-excel-to-interpret-the-comma-as-a-default-delimiter-in-csv-files
Ross
Ross Scroggs
@.***

On May 30, 2024, at 2:17 PM, OldManWindowsGuy @.***> wrote:
We can close this feature request, I was hoping to improve the export. I was hoping the product could be updated to work more seamlessly with other products like Excel.
Thanks for the consideration.
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140879616, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL4CUOJNNFMSICOTAQTZE6JQFAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHA3TSNRRGY.
You are receiving this because you commented.

This is not so much about opening it in excel and being able to review it.  But really more about using another scripting tool to wrap around the GAM Export.  The GAM tool itself is not much useful without being able to build a script and automation around it to do what you want.
Even PowerShell, doesn't recognize the data dumped into a variable as an Array of data with columns.  It's one large set with no ability to filter on the individual columns.  I've have tried adding the @(), splitting it out etc.  Below is about the only thing I found to make it work. Export it, re-import it to a new variable.  I'd like to have just dumped into a variable and be able to manipulate as needed.
$MyVariable = GAM Print CROS allfields
$MyVariable.SerialNumber
This should just provide me a list of SerialNumbers....  But it doesn't because it doesn't recognize it correctly.
So instead, I have dump it out to a CSV file first:
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Then re-import that CSV
$MyNewVariableImport = import-csv C:\GAM\Exports\GAM-Devices.csv
To be able to use the individual column members
$MyNewVariable.SerialNumber
I closed the Feature Request; I'll deal with the overhead on my script side.  I just figured it would be something simple to fix on the coding side (even a command switch to change the CSV output).  But I will code it on my end instead.

Again, with Advanced GAM you can choose whatever column delimiter character you'd like.
Ross
Ross Scroggs
@.***

On May 30, 2024, at 4:15 PM, OldManWindowsGuy @.***> wrote:
This is not so much about opening it in excel and being able to review it. But really more about using another scripting tool to wrap around the GAM Export. The GAM tool itself is not much useful without being able to build a script and automation around it to do what you want.
Even PowerShell, doesn't recognize the data dumped into a variable as an Array of data with columns. It's one large set with no ability to filter on the individual columns. I've have tried adding the @(), splitting it out etc. Below is about the only thing I found to make it work. Export it, re-import it to a new variable. I'd like to have just dumped into a variable and be able to manipulate as needed.
$MyVariable = GAM Print CROS allfields
$MyVariable.SerialNumber
This should just provide me a list of SerialNumbers.... But it doesn't because it doesn't recognize it correctly.
So instead, I have dump it out to a CSV file first:
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Then re-import that CSV
$MyNewVariableImport = import-csv C:\GAM\Exports\GAM-Devices.csv
To be able to use the individual column members
$MyNewVariable.SerialNumber
I closed the Feature Request; I'll deal with the overhead on my script side. I just figured it would be something simple to fix on the coding side (even a command switch to change the CSV output). But I will code it on my end instead.
Script.jpg (view on web) https://github.com/GAM-team/GAM/assets/171264888/d16dd270-812a-458f-982a-22ec1fde977c
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140989516, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL3AVC5I3KVO6LRVHLDZE6XIPAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHE4DSNJRGY.
You are receiving this because you commented.

With Advanced GAM, you can also direct the output directly to a Google Sheet.
Ross
Ross Scroggs
@.***

On May 30, 2024, at 4:15 PM, OldManWindowsGuy @.***> wrote:
This is not so much about opening it in excel and being able to review it. But really more about using another scripting tool to wrap around the GAM Export. The GAM tool itself is not much useful without being able to build a script and automation around it to do what you want.
Even PowerShell, doesn't recognize the data dumped into a variable as an Array of data with columns. It's one large set with no ability to filter on the individual columns. I've have tried adding the @(), splitting it out etc. Below is about the only thing I found to make it work. Export it, re-import it to a new variable. I'd like to have just dumped into a variable and be able to manipulate as needed.
$MyVariable = GAM Print CROS allfields
$MyVariable.SerialNumber
This should just provide me a list of SerialNumbers.... But it doesn't because it doesn't recognize it correctly.
So instead, I have dump it out to a CSV file first:
GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Then re-import that CSV
$MyNewVariableImport = import-csv C:\GAM\Exports\GAM-Devices.csv
To be able to use the individual column members
$MyNewVariable.SerialNumber
I closed the Feature Request; I'll deal with the overhead on my script side. I just figured it would be something simple to fix on the coding side (even a command switch to change the CSV output). But I will code it on my end instead.
Script.jpg (view on web) https://github.com/GAM-team/GAM/assets/171264888/d16dd270-812a-458f-982a-22ec1fde977c
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2140989516, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL3AVC5I3KVO6LRVHLDZE6XIPAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBQHE4DSNJRGY.
You are receiving this because you commented.

I'll give it a try

I'm available right now (it's about 6:30PM PDT) or in the morning from 6:30 to 7:30.
If you'd like hekp, send a Meet/Zoom invitation.
Ross
Ross Scroggs
@.***

On May 30, 2024, at 5:55 PM, OldManWindowsGuy @.***> wrote:
I'll give it a try
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2141060558, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL2QOS5SM7BOJ7EECF3ZE7DABAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRGA3DANJVHA.
You are receiving this because you commented.

This is not so much about opening it in excel and being able to review it. But really more about using another scripting tool to wrap around the GAM Export. The GAM tool itself is not much useful without being able to build a script and automation around it to do what you want.
Even PowerShell, doesn't recognize the data dumped into a variable as an Array of data with columns. It's one large set with no ability to filter on the individual columns. I've have tried adding the @(), splitting it out etc. Below is about the only thing I found to make it work. Export it, re-import it to a new variable. I'd like to have just dumped into a variable and be able to manipulate as needed.
$MyVariable = GAM Print CROS allfields
$MyVariable.SerialNumber
This should just provide me a list of SerialNumbers.... But it doesn't because it doesn't recognize it correctly.
So instead, I have dump it out to a CSV file first: GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Then re-import that CSV $MyNewVariableImport = import-csv C:\GAM\Exports\GAM-Devices.csv
To be able to use the individual column members $MyNewVariable.SerialNumber
I closed the Feature Request; I'll deal with the overhead on my script side. I just figured it would be something simple to fix on the coding side (even a command switch to change the CSV output). But I will code it on my end instead.

I’ve been doing this exact thing for a few years now. Same reason. Let me know if you find a better way.

How about:
$MyVariable = GAM Print CROS allfields | ConvertFrom-Csv -Delim ','
Ross
Ross Scroggs
@.***

On May 31, 2024, at 5:13 AM, paulmiglio @.***> wrote:
This is not so much about opening it in excel and being able to review it. But really more about using another scripting tool to wrap around the GAM Export. The GAM tool itself is not much useful without being able to build a script and automation around it to do what you want.
Even PowerShell, doesn't recognize the data dumped into a variable as an Array of data with columns. It's one large set with no ability to filter on the individual columns. I've have tried adding the @(), splitting it out etc. Below is about the only thing I found to make it work. Export it, re-import it to a new variable. I'd like to have just dumped into a variable and be able to manipulate as needed.
$MyVariable = GAM Print CROS allfields
$MyVariable.SerialNumber
This should just provide me a list of SerialNumbers.... But it doesn't because it doesn't recognize it correctly.
So instead, I have dump it out to a CSV file first: GAM Print CROS allfields > C:\GAM\Exports\GAM-Devices.csv
Then re-import that CSV $MyNewVariableImport = import-csv C:\GAM\Exports\GAM-Devices.csv
To be able to use the individual column members $MyNewVariable.SerialNumber
I closed the Feature Request; I'll deal with the overhead on my script side. I just figured it would be something simple to fix on the coding side (even a command switch to change the CSV output). But I will code it on my end instead.
https://private-user-images.githubusercontent.com/171264888/335399082-d16dd270-812a-458f-982a-22ec1fde977c.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTcxNTc4MTQsIm5iZiI6MTcxNzE1NzUxNCwicGF0aCI6Ii8xNzEyNjQ4ODgvMzM1Mzk5MDgyLWQxNmRkMjcwLTgxMmEtNDU4Zi05ODJhLTIyZWMxZmRlOTc3Yy5qcGc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNTMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDUzMVQxMjExNTRaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1jZDFiYzIzNzhkZTA3NDhlMWY5ZDI0NDNmYjYzZDhlMzQ1ZmJjNmQxYzlhOTg3NmZkNDYwNTRlYjkyZjY1NjJmJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.C3r8FiHoctl56tVkrZmRIRIvoCUJHcTk7tr2wBK4xl8
I’ve been doing this exact thing for a few years now. Same reason. Let me know if you find a better way.
—
Reply to this email directly, view it on GitHub https://github.com/GAM-team/GAM/issues/1690#issuecomment-2141937923, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCTYL6PE67KZA55VIE7DHDZFBSNHAVCNFSM6AAAAABIRDGSHSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBRHEZTOOJSGM.
You are receiving this because you commented.


size limit for metadata?

Hi!
I have a Client and a Server in two Winform apps.
I send a data request command from the Client to the Server:
metadata.Add("Command", "GetDateData");
Client.Connect();
SyncResponse serverResponse = Client.SendAndWait(ClientTimeout, "", metadata);

Then, at the Server side, I check the command metadata, and send back a Json serialized List of class objects (DfileProperties), from the methode "private SyncResponse SyncRequestReceivedServer(SyncRequest req) { ..... }":
replyMetadata.Add("Command", "GetDateData");
string json = JsonConvert.SerializeObject(DfileProperties.GetRange(0, 4), Formatting.None);
replyMetadata.Add("ServerDayData", json);

return new SyncResponse(req, replyMetadata, "");

The interesting thing is that, if the object list DfileProperties contains like 5000 elements, the data never arrives, I get timeout error at the SendAndWait() method. If I limit the List size to like 3 items, the data comes through. Is there a size limit?
The Class is not huge, only contains some basic type props, like 25 int, string and DateTime values.
Any idea what can be the problem?
Thanks! :)

Hi @bukkideme there isn't a size limit on it.  If you were to serialize the object you're attempting to send, how long would it be?  What timeout are you specifying for SendAndWait?  Also note that you can include objects in the metadata without serializing them yourself.  The metadata dictionary is part of the WatsonMessage class, and the whole thing is serialized prior to being sent.  Cheers

Also for large objects you may want to consider sending them as part of the data and not part of the metadata.  Just a general design principle in my opinion that metadata is reserved for control types of information (such as HTTP headers) whereas the data should be sent as payload.  However that doesn't mean you shouldn't be able to send it back as metadata.

Hi! Thanks for the reply! I had a 20 sec timeout, and the data is not that large. I might made some other mistake which resulted in the experienced issue anyway...
As you suggested, I just moved to a Client.Send() method, so I send the request to the server, then the server replies back with the same Server.Send() method, sending the larger data as a JSON byte array.
Now everything just works perfect! :) This package is very useful, thanks! :)

Glad you got it working @bukkideme - I will spend some time testing large-ish metadata to see if I can find a way to reproduce.  Cheers!

Hi @bukkideme sorry for taking a long time to get back to you on this.  The reason this is happening is as follows:

Metadata is packaged as part of each message frame
The message frame's demarcation from the payload (data) is \r\n\r\n
To build a message, Watson reads from the underlying socket one byte at a time and persists that to a header buffer
The header buffer's tail is evaluated for the pattern in 2, and if present, the end of the header has been reached.  If not, it continues reading one byte at a time

There isn't a way AFAIK of peeking ahead in a network stream to find the first occurrence of \r\n\r\n, which is why it's reading one byte at a time and evaluating the buffer each time.
So with a lot of metadata, let's say 1MB, that's 1024 * 1024 (roughly) evaluations of the end of the buffer to see if the end of the headers has been reached.
I did a simple test using the Test.Metadata project (which I'll be committing momentarily).  With 5 key/value pairs in the metadata, is was fast.  50, still ok, 500 it started becoming a problem (148ms), and 5000 was really slow (16.3 seconds).
I'll add some guidance in the README to make sure this is cleared up for others.  Hope this helps!


Cosmos DB | Update for Az.CosmosDB 0.1.4 | Common

Description
For Az.CosmosDB 0.1.4 release, update samples for account/common-focused cmdlets.
Checklist

[ ] This pull request was tested on both of:

[X] PowerShell 5.1 (Windows)
[ ] PowerShell 6.x
[X] PowerShell 7.x (Latest PowerShell)

[X] Scripts do not contain static passwords or other secret tokens.
[X] All Azure resource identifiers which must be universally unique are guaranteed to be so.

Testing information
Windows 10.0.18363, Powershell 5.1, Az 3.8.0
Windows 10.0.18363, Powershell 7.0.0, Az 3.8.0

#sign-off


chore: add clusterroles for tasks and builds to admin and edit

Just adding the missing clusterroles to the admin role to allow the lagoon namespace deployer service account to interact with builds and tasks within the namespace as required
Currently the deployer service account can interact with all other resources within the namespace during a build, and being able to interact with other builds or tasks that may exist in the namespace would be useful for being able to handle previous build or task cleanups within a build process.

It would be nice to get this into a lagoon-remote update as part of lagoon-remote 0.87.0 in the 2.17 branch


[BUG] God mode i can die with enemies

Describe the bug
I activate god mode and I still die from enemies (I don't know if it could be some incompatibility between mods)
Information (please complete the following information):

Game version: 0.219.16 (Steam)
ValheimTooler version: 1.11.0
ValheimTooler distribution: (I don't know what to really put here)
Has other mods used? Yes

Hi @choukpop ,
I indeed suspect that this is some incompatibility with another mod, could you please try with only ValheimTooler and no other mods to see if it works?
If it is indeed working without the other mods that would mean that one of them prevent my tool to activate the feature properly :/
Then sadly there would be no other choice but to add them back one by one to find out which one is causing this bug.
Kind regards,
Astropilot

Good morning, I just tested it with the mod and it works
I wanted to ask if there isn't any way to correct the incompatibility? I'm now using this mod (https://thunderstore.io/c/valheim/p/QoLTeam/Valheim_Admin_Tool) which I think uses the same way of doing God mode and it works without any incompatibilities
I only reported the "bug" because I really prefer your design and it's cleaner


Update http4s-twirl to 1.0.0-M15

Updates org.http4s:http4s-twirl from 1.0.0-M4 to 1.0.0-M15.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s", artifactId = "http4s-twirl" } ]

labels: library-update, semver-pre-release

Superseded by #215.


Make lenses fallible

As outlined on discord, this makes it so that Lens::view returns Option<'&a Self::Target>. This is mostly abstracted away by adding an unwrap() in Field::get. This can be interacted with safely by using Binding::new_fallible, which has a TODO which I will need some help resolving.

If we like this and we think that vizia is young enough to make such a big breaking change, I would like to propose that Binding::new and Binding::new_fallible be renamed to Binding::new_unwrap and Binding::new.

Good news! I figured out how to address the TODO I previously mentioned. This PR is now ready for merging, assuming you like the API.
As a bonus, I made Lens::index work. I changed the commented implementation a bit because using Then required the intermediate data to be Model, which was undesirable in my use case.

The two subtle bugs mentioned in the above commit message are:
a) if a fallible binding had the initial value of none, it would fail to cache any data. I resolved this by adding the force parameter.
b) if fallible bindings are directly nested inside each other, they would override each other's cached data. I resolved this by forcing the system to cache on the most recent child, i.e. the binding itself.

Superseded by #33 and #41


Reduce docker image layers

Using only one RUN command reduces the docker images layers thus makes it smaller

Nice one! 🥂


Cannot find module

When starting my app I get the error:
Error: Cannot find module 'tsparticles/dist/Options/Classes/Options'
Any idea why?
"react-particles-js": "^3.5.1"

Thanks that worked :)

Fixed with v3.5.2

Fixed with v3.5.2

3.6.0又开始报错了
The same error occurred


Version 2.2.0 crashes when using app.test_client() as a context-manager in multi-threaded tests

The following code defines a simple app, and queries it from a test that uses threads:
import threading

from flask import Flask
import pytest

def create_app():
    app = Flask(__name__)

    @app.route("/hi", methods=["POST"])
    def hello():
        return "Hello, World!"

    return app

@pytest.fixture()
def app():
    app = create_app()
    yield app

@pytest.fixture()
def client(app):
    with app.test_client() as client:
        yield client

def test_request_example(client):
    successes = 0

    def f():
        nonlocal successes
        response = client.post("/hi")
        assert "Hello, World!"    This will
        also trigger the execution of functions registered by the
        :meth:`~flask.Flask.teardown_request` decorator.

        .. versionchanged:: 0.9
           Added the `exc` argument.
        """
        clear_request = len(self._cv_tokens) == 1

        try:
            if clear_request:
                if exc is _sentinel:
                    exc = sys.exc_info()[1]
                self.app.do_teardown_request(exc)

                request_close = getattr(self.request, "close", None)
                if request_close is not None:
                    request_close()
        finally:
            ctx = _cv_request.get()
            token, app_ctx = self._cv_tokens.pop()
>           _cv_request.reset(token)
E           ValueError: <Token var=<ContextVar name='flask.request_ctx' at 0x7fc44844a1d0> at 0x7fc444a18a80> was created in a different Context

../../.local/lib/python3.9/site-packages/flask/ctx.py:407: ValueError
======================================================================= short test summary info ========================================================================
FAILED test_flask_threads.py::test_request_example - ValueError: <Token var=<ContextVar name='flask.request_ctx' at 0x7fc44844a1d0> at 0x7fc444a18a80> was created in...
===================================================================== 1 failed, 1 warning in 0.11s =====================================================================

Environment:

Python version: 3.9
Flask version: 2.2.0

I think this only worked by accident before. The problem is that you're unconditionally pushing the client in the fixture, for every test, and isn't popping it until the end of the test. This conflicts with using it in multiple threads. First, you should not push the client in the fixture, only push it when you actually need to make a request and preserve the context. Second, only preserve the context in the same thread, don't try to use the same pushed context across threads.


share me location to start npm start

share me location to start npm start

Have installed node?

yes i have install node


Open file translation

Describe the bug
A clear and concise description of what the bug is.
Platform / versions (please complete the following information):

Platform: [e.g. Mac, Windows, Debian, Ubuntu ...]
Version: [e.g. 11.0.0]

Only GLOBAL.FILES are visible for choice of coclustering files


test/gke: Disable K8sServicesTest Checks service across nodes with L7 policy Tests NodePort with L7 Policy

The test is known to be broken. Disabling until #11235 is fixed

test-me-please

test-gke

Coverage increased (+0.003%) to 44.494% when pulling bea5e3eaf83182db0f38266f557a84c4c4a493d1 on pr/tgraf/disable-host-l7 into 50d4acbc1d97d77940f97fecc3287db3777f26b0 on master.

test-gke

test-gke


json object of URL code

When you using GetByCode method it returns a number of parameters. However, two things:

WebsideID is returning in some kind of digital format, not a usual WebsideID. Is it ok?

If Notes field contains too much symbols, it crops a whole string and doesn't return websideid.

1. That should be fine for now, I'll create an issue to enhance the data returned
2. If you look at the email source code you will see it contains all the data :-) Some of it was just interpreted as HTML code.

1. See #11

Ok, thanks.
I've commented the 11-th


brightness warning

[homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.

Same here. The Pole lamp is going crazy. Constantly disconnect and/or cycles through brightness. Even when a static scene is selected in the Wiz app.
Log sample:
[18/10/2023, 07:28:41] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 07:48:55] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 07:48:57] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 16:17:45] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 16:18:06] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 16:28:48] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 16:29:00] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:47:31] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:47:32] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:47:35] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:10] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:10] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:13] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:13] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:13] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:30] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:31] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:31] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:35] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:37] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:38] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:39] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:39] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:44] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:44] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:45] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:45] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:51] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:52] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:53] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:55] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:48:55] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:13] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:14] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:17] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:23] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:25] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:31] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:33] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Brightness': characteristic value expected valid finite number and received "NaN" (number). See https://homebridge.io/w/JtMGR for more info.
[18/10/2023, 17:49:45] [homebridge-tp-link-tapo] This plugin slows down Homebridge. The read handler for the characteristic 'On' was slow to respond! See https://homebridge.io/w/JtMGR for more info.

I get a similar warning.
[2/6/2024, 11:10:36 AM] [homebridge-wiz-lan] This plugin generated a warning from the characteristic 'Color Temperature': characteristic value expected valid finite number and received "Infinity" (number). See https://homebridge.io/w/JtMGR for more info.
I noticed that the Dimming Functions doesnt work. I have a feeling this is related to that, but I don't really understand all of this stuff.


Sample for ark-core FileStorage JNI bindings usage

Doesn't really work on my devices... Tried on Android versions 8 and 11.
Steps to test:

Create an empty folder.
Select it in storage demo.
Either:
a. Leave the prefix field empty.
- Adding some values doesn't lead to creation of the storage on disk.
- Deleting non-existing values doesn't lead to crash or error.
b. Fill the prefix field.
- Crash as soon as the field input is complete.

Doesn't really work on my devices... Tried on Android versions 8 and 11.
Steps to test:

Create an empty folder.
Select it in storage demo.
Either:
a. Leave the prefix field empty.

Adding some values doesn't lead to creation of the storage on disk.
Deleting non-existing values doesn't lead to crash or error.
b. Fill the prefix field.
Crash as soon as the field input is complete.

Hi! @kirillt Just repeating what we previously discussed: this issue was being caused by the fact that the released APK did not include ark-core JNI binaries.
Now, with the latest updates, it fortunately might be fixed, but let me know if it still persists

@oluiscabral still doesn't work. Nothing is written to disk.

@oluiscabral still doesn't work. Nothing is written to disk.

@kirillt That's unfortunate... But I might know what's happening. I'll try another potential solution and let you know again when it's done

@kirillt Just converted the JAR into an AAR. Let me know if it's still working for you

syncStatus called on non-existent file causes crash
JNI DETECTED ERROR IN APPLICATION: JNI FindClass called with pending exception java.lang.RuntimeException: IO error: No such file or directory (os error 2)

readFS, sync, syncStatus, merge, get not implemented

syncStatus called on non-existent file causes crash
JNI DETECTED ERROR IN APPLICATION: JNI FindClass called with pending exception java.lang.RuntimeException: IO error: No such file or directory (os error 2)

Thanks for contributing, @mdrlzy!
It's nice that you created a foundation to test each one of the FileStorage methods. I wonder what @tuancoltech thinks about it, because initially I'd also updated the UI and formatted the code, but ended reverting it back after @kirillt told me that Tuan was actually working on it (UI)
Anyways, I have a few considerations about the points you brought. syncStatus indeed throws an error if the FileStorage is not yet persisted on disk. This is actually the behavior of the source code on ark-core. The same applies for sync (that depends on syncStatus), readFS and even erase. All of them presume that writeFS was already called at least once, that is the FileStorage is on disk.
So all that said, maybe should we disable the buttons related to those methods if the button for writeFS was not yet clicked?
About merge and get, both of them are already working for me. Did it crash when you tested them out?

It's nice that you created a foundation to test each one of the FileStorage methods. I wonder what @tuancoltech thinks about it, because initially I'd also updated the UI and formatted the code, but ended reverting it back after @kirillt told me that Tuan was actually working on it (UI)

I dont know. Kirill asked me to do review/refactor.

So all that said, maybe should we disable the buttons related to those methods if the button for writeFS was not yet clicked?

Good idea. Done. Can you test it?

About merge and get, both of them are already working for me. Did it crash when you tested them out?

Everything works for me. Except for some cases where the storage file is missing but it seems to be justified
Let's wait for Kirill's review

@oluiscabral to create better API suited for app developers' needs, we need one of these two static functions in fs-storage:

fn list(root: Path): Vec<Path> that lists all storages in a root folder, regardless of their type. I believe that would be too difficult without relying on specific subpath, so we could simply list everything under $root/.ark/user. The sample, or an app could filter this list by the storage name.

Example: list("/a/b/c/") returns ["/a/b/c/.ark/user/tags", "/a/b/c/.ark/user/scores"]

fn load(root: Path, name: String): Option<BaseStorage> loads the storage with name name if it exists. The path for any combination of root and name is determined by fs-storage and can change in future. Especially, when we add atomic versions into fs-storage.

Example: load("/a/b/c/", "tags") returns Some(FileStorage("/a/b/c/.ark/user/tags"))
Example: list("/a/b/c/", "properties") returns Some(FolderStorage("/a/b/c/.ark/user/properties"))
Example: list("/a/b/c/", "garbage") returns None

This way, the app developer will be able to specify the "root" folder and the storage name and simply load or initialize the storage without working with the file path directly.
@mdrlzy initially I had the idea of flexible path selection in the sample, to ease testing, but I don't think it's a good idea to expose the path via the API to the app developer. We should prevent incorrect usage of the underlying files of the storage. Could you modify the sample to only allow selection of root and name for the storage? If the storage exists, fs-storage must inform the app developer about the storage type: FileStorage, or FolderStorage. If it doesn't exist yet, the app developer is free to choose the type to initialize new storage.
empty storage is ok to be not persisted, for the rest we have sync status, it sounds ok to have storage in pending state if we have something like "flush" or "sync" operation

@mdrlzy also, would be great to add display for SyncStatus that is returned by fn sync_status
It seems to me (although I'm not 100% sure) that usages of flush method should be replaceable with fn sync.
@oluiscabral other minor changes to the BaseStorage API could be done:

restrict visibility to write_fs and read_fs, it should be used only by the storage module itself
declare public getter entries returning same type as read_fs, i.e. Result<&BTreeMap<K, V>>
change return type of read_fs to simply Result<()>

initially I had the idea of flexible path selection in the sample, to ease testing, but I don't think it's a good idea to expose the path via the API to the app developer. We should prevent incorrect usage of the underlying files of the storage. Could you modify the sample to only allow selection of root and name for the storage? If the storage exists, fs-storage must inform the app developer about the storage type: FileStorage, or FolderStorage. If it doesn't exist yet, the app developer is free to choose the type to initialize new storage.
empty storage is ok to be not persisted, for the rest we have sync status, it sounds ok to have storage in pending state if we have something like "flush" or "sync" operation

The problem is that if storage file does not exist then syncStatus, sync, readFS, erase causes crash.
So when using api in this form we need to know whether the file exists or not.
There is also no binding for FolderStorage yet.

also, would be great to add display for SyncStatus that is returned by fn sync_status

We already have button that shows toast with sync status. Is this not enough?

We already have button that shows toast with sync status. Is this not enough?

Should be enough. Sorry, I haven't tested the APK yet.


pinning API

WIP

API calls

[x] ipfs.pin.ls
[x] ipfs.pin.add
[x] ipfs.pin.rm

[ ] Works in js-ipfs milestone 6
[x] Works in js-ipfs-api

Thank you @RichardLitt :D Applied almost all your CR, will add a couple more tests to cover remaining cases :)

Applied all the CR :)

lgtm


Added two new contributers

Resolves #914
Resolves #915
Account Number: 3b59cd93d7cb88fd55caaea77f07328b57cce7e3d1a14b13410291c698dccf2e

@DinShpati Don't club multiple issues in a single PR. One issue, One PR. Can you update your PR?

@DinShpati Don't club multiple issues in a single PR. One issue, One PR. Can you update your PR?

sure


Manual deployment

Hi,  I did a manual deployment as i was unable to deploy using the automated option.
All the steps were followed and the ARM template deployed successfully, the issue i have is when accessing the config page (configurationAppUrl )  for the expert web app it does not prompt me to authenticate and is not displaying the screen shown in the documentation.

Any ideas why this might be the case, i configured the app registration in azure ad as per the documentation. this is the land page i get when enter the configurationAppUrl  into the browser.

Hi @peakers1976, thank you for raising the query, can you confirm if you see the below screen once the deployment completed, the screenshot shared above meant some of the services are still deploying and not fully completed.

Hi @peakers1976, thank you for raising the query, can you confirm if you see the below screen once the deployment completed, the screenshot shared above meant some of the services are still deploying and not fully completed.

Hi @Porkai-Pandian, thank you for the follow-up, yes the screenshot you are referring to does show up

Hi @Porkai-Pandian , Just an update, I re-ran the ARM template again doing exactly what I had done previously and this time the configuration page prompts me for a sign-in and displays the config page.


Allow configuring MBEDTLS_TLS_EXT_CID at compile time

The numerical identifier of the CID extension hasn't been settled yet and different implementations use values from different drafts. Allow configuring the value at compile time as discussed in https://github.com/ARMmbed/mbedtls/issues/3892#issuecomment-757523779.
I made this PR against 3.0. Should we do it in 2.2x as well, since the CID extension ID is likely to fluctuate then settle during its lifetime?

First, thanks for addressing my issue with this PR.

I made this PR against 3.0. Should we do it in 2.2x as well, since the CID extension ID is likely to fluctuate then settle during its lifetime?

FMPOV, it's more important for 2.2x.
The draft-ietf-tls-dtls-connection-id is currently reviewed and the requested changes so far are about terms on expressions, but not longer the used data and security functions. So, hope it gets released within the next months and then with a stable defined MAC and code points.


Markdown syntax issues

Can you improve the highlighting for the markdown syntax. Below is an example of Tokyo Night and another for the One Dark theme.
Tokyo Night

One Dark

Resolved by https://github.com/ssaunderss/zed-tokyo-night/pull/6


PlanMyTrip News

When a change is requested, you should do changes in the same PR. You should never create a new PR for every change request. Remember this always. One change request. After that, I will mark this PR as accepted.

I am not very familar with these concepts.But now I get it.Surely moving forward will keep these lessons.

Always make the PR title related to the code that you want to merge or fix that you have made. Can you edit the PR title?

Changed the PR title


Showstopper: Crash when mqtt.publish and HTTP.GET is executed simultaneously

While running 4 clients at the same time publishing a message every 16ms and requesting a GET, GOST crashes.

Seems to be fixed after setting db connections and reintroducing schema into sql statements instead of using SET SEARCH_PATH =


How to Customize the CAF Module naming convention ?

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description
Is your feature request related to a problem?
Unable to determine from the documentation how to customize the CAF naming convention, or to what extent this is possible.
Describe the solution you'd like
A section in the documentation indicating how to:

Add customising parameters to the naming of resources
What adjustments are possible to the caf module naming convention for resources
Any limitations to the naming convention customisation

Additional context
Enterprises often require some unique modification to a naming convention

Thank you for your query @archmangler
The module is designed to focus on the architecture, with the intent that this lets customer focus on what is most important rather than naming conventions. The built-in naming is also an important aspect of ensuring all resources are uniquely named as customers expand their infrastructure over time.
That said, we have allowed a mechanism for customising all settings (including resource names):

For management groups, you would do this by disabling the deploy_core_landing_zones and defining your own management group hierarchy using the custom_landing_zones input variable. Care should be taken when doing this as there are certain capabilities of the module relating to policies which rely on certain management group IDs to ensure the correct settings are provided for input parameters on the Policy Assignments.
Additionally, the advanced block within the configure_connectivity_settings and configure_management_settings allows you to manipulate settings for any resource. This is undocumented and likely to be simplified when we refactor the module to support optional() types within the type schema (this is now GA in Terraform v1.3.0) but we have not yet committed this work to our backlog due to other priorities.

If you want to use the advanced block to do this, please have a look through some of our closed issues where you will find this has already been answered. A couple of good examples to refer to are:

#292
#332

I will close this issue as it's technically a duplicate and we are already tracking follow-up work on this via issue #292.

Trigger ADO Sync


Ctrl+V not working

Your Windows build number: 10.0.16299.214

Bash version: 4.3.48(1)-release-(x86_64-pc-linux-gnu)

"Kernel" version: 4.4.0-43-Microsoft

What you're doing and what's happening: Trying to paste text into the console, but all I'm getting is ^V, which is probably some archaic escape character that noone needs anymore.

What's wrong / what should be happening instead: Pressing Ctrl+V inserts ^V into the terminal, rather than copied text. Same for Ctrl+Shift+V and Ctrl+Ins. Only the right mouse button successfully pastes text. I would expect Ctrl+V to just paste the copied text, just like in the regular command prompt (cmd.exe) where it works totally fine.

Strace of the failing command, if applicable:  N/A

My settings in Alt+Space->Properties are default, afaik. But to be clear:
QuickEdit Mode: ticked
Insert Mode: unticked
Enable Ctrl key shortcuts: ticked
Filter clipboard contents on paste: ticked
Enable line wrapping selection: ticked
Extended text selection keys: ticked
Use legacy console: unticked

Contributing.md

Reporting issues in Windows Console or WSL text rendering/user experience

Note that WSL distro's launch in the Windows Console (unless you have taken steps to launch a 3rd party console/terminal). Therefore, please file UI/UX related issues in the Windows Console issue tracker.

#235

@DarthSpock
Ctrl+V works fine in the regular command prompt. So there is some sort of different between it and the WSL console. I wouldn't file a bug like this at the Windows Console, because it's working fine. It's only broken for the WSL terminal. This indicates a bug inside WSL, where maybe Ctrl+V is overridden with whatever.

See the post above yours not to mention the label (dead giveaway).

I have the same issue. I see snide phrases like "dead giveaway" that are not explaining the issue. Please would someone explain how to fix this or how to file this in a way the elicits more than snarky remarks. Thank you.

@edpell Next Feature Update will bring CTRL+SHIFT+C and CTRL+SHIFT+V support.
https://blogs.msdn.microsoft.com/commandline/2018/04/13/copy-and-paste-arrives-for-linuxwsl-consoles/

Why Ctrl+Shift+V? Why not make it work the as in the command prompt??

@thany Because Unix terminal has always been like this. CTRL+C and CTRL+V have already a reason to exist different form copy/paste.
https://superuser.com/questions/421463/why-does-ctrl-v-not-paste-in-bash-linux-shell

Ctrl+V doesn't do anything in WLS.
Besides, consistency is more important than legacy.
It'll only be confusing if we've got mixed shortcut keys for the same action is VERY similar terminals (cmd vs wls).

Ctrl+V doesn't do anything in WLS.

And yet …

That's even weirder. At least the menu is on the right track.
Maybe Ctrl+V doesn't work because in the menu it says "Ctrl minus V" 😀
Anyway,

Ctrl+Shift+V is different from Command Prompt, so that's undesirable. It would be the same as on most Linux distros, but who cares! It currently inserts ^V into the shell, which is weird but some tool might do something with it, who knows.
Ctrl+V is the standard, not only in Command Prompt, but also in EVERY other application. Currently it inserts ^V into the shell when hitting Ctrl+V twice, but a single Ctrl+C does absolutely nothing.
Right mouse click is okay, because it has always worked. Please keep that intact.

To aid users who desperately want or need Ctrl+Shift+V to paste, let's implement both Ctrl+Shift+V AND Ctrl+V.

@thany @kthy This issue is closed because it's a Console issue not a WSL actionable and one that has already been resolved: https://blogs.msdn.microsoft.com/commandline/2018/04/13/copy-and-paste-arrives-for-linuxwsl-consoles/

That's nice. So displaying Ctrl-V as shortcut for paste is a feature, even though that's not the shortcut that was implemented?

Since it hasn't been referenced yet (apologies for not doing so), here's the reference in the proper Console tracker for this issue: https://github.com/Microsoft/console/issues/264 which provides guidance from a Console dev.

@thany Try to add these registry values:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Console]
"CtrlKeyShortcutsDisabled"=dword:0
"ExtendedEditKey"=dword:1
"ExtendedEditKeyCustom"=dword:1
"InterceptCopyPaste"=dword:1

No difference.
Ctrl+V does paste in command prompt, but does not paste in WSL.
Ctrl+Shift+V does not paste in either.
All on the same pc, same network, same user, same day, same moon phase.

Ctrl+Shift+V does not paste in either.

Works for me here on "Use Ctrl+Shift+C/V as Copy/Paste" set. This is on 18267.
The behavior of Ctrl-V is not on planet actionable. WSL (and the Real Linux™ kernel) has never heard of a 'paste', triggered by Ctrl-V or otherwise. And this issue is closed.

@therealkenc

WSL (and the Real Linux™ kernel) has never heard of a 'paste', triggered by Ctrl-V or otherwise.

Which is why we can assign it to Paste.

Which is why we can assign it to Paste.

The Linux kernel has never heard of "to Paste" either.
[Fun but unrelated trivia: Ctrl-C Ctrl-Z have implications at the kernel via termios and the ioctl(2) syscall, in that they can generate interrupts from the kernel to a process via the tty layer. This is due to quirky historic reasons having to do with control characters sent by teletype terminals.]
"Paste", meanwhile, has nothing to do with anything the kernel cares about. WSL hasn't the faintest idea what is in your Windows paste buffer. Or in the paste buffer of someone loitering in a Starbucks halfway around the world using a Macbook Air connected to Ubuntu on WSL via ssh. Which is why this issue is closed and tagged console. Since February. And was addressed, it appears, in 17643.

@therealkenc You are explaining exactly why Ctrl+V could be used for pasting.
Of course the kernel doesn't know about it. That's why it will work!
Paste is essentially just inserting the characters in the clipboard, into WSL as if they were typed in. That's how it works when right-clicking, and that's how it should work when Ctrl+V'ing.

Paste is essentially just inserting the characters in the clipboard, into WSL

Paste does not insert anything into WSL; essentially, or otherwise.

As @thany mentioned

Ctrl+V does paste in command prompt, but does not paste in WSL.
Ctrl+Shift+V does not paste in either.

Strangely, Ctrl+V does paste inside the VS Code integrated terminal (setup to use WSL).
"terminal.integrated.shell.windows": "C:\Windows\System32\wsl.exe"
This behavior suggests it's the command prompt window and how it processes Ctrl key commands once you've invoked the WSL kernel.
Hope this helps!

Strangely, Ctrl+V does paste inside the VS Code integrated terminal

Not strange.

This behavior suggests it's the command prompt window Windows Console

Ya think?

and how it processes Ctrl key commands

Correct. The paste operation in Windows Console with WSL is Ctrl+_Shift_+C/V per Rich's blog post. Which the console team chose to do in order to quoth "ensure that we don't break any existing behaviors". Which is not dissimilar to how wsltty chose to do their paste operation, for the same reasons, although wsltty went with the more traditional paradigm of Ctrl+Shift+Ins. VSCode (actually xtermjs) went with Ctrl-V for their own reasons. xterm still uses the middle mouse button to paste (and most certainly not Ctrl-V), because they're old-school that way. Everyone's prerogative.

once you've invoked the WSL kernel

The WSL kernel has nothing to do with it, and does not know nor does not care what xterm or wsltty or PuTTY or code or the Windows Console chooses to do about cut and paste operations. But people keep posting to this long-since closed-as-a-clam Windows Subsystem for Linux tracker anyway.

@therealkenc

Paste does not insert anything into WSL; essentially, or otherwise.

Maybe you're misunderstand my point there.
Clearly it does something when rightclicking the terminal. It inserts the contents of the clipboard. It does, really. It definitely inserts something. Whether it does that by "typing" I don't know, but afaik this is how most terminals work - including Windows' command prompt & powershell, macOS' terminal, Ubuntu's terminal, etc. They somehow inject "typing", which can easily be proved by pasting characters that control a program in some way.

Paste does not insert anything into WSL; essentially, or otherwise.
Maybe you're misunderstand my point there.

No I understood you fine.

Clearly it does something when rightclicking

Pronoun. You mean Windows Console. Not WSL. Which is the tracker you're in right now.

They somehow

Mostly Mike I think.

[Mike] somehow inject[s] "typing"

..into the Windows Console. WSL doesn't know about typing either. No keyboard driver.
Some loose ends for earlier posts since I'm here...

^V into the shell, which is weird

Not weird.

but some tool might do something with it,

For example tools like GNU bash(1) or v1(1) or its younger cousin vim(1).

who knows

Pretty much everyone who has used vi since 1976.

Currently it inserts ^V into the shell when hitting Ctrl+V twice,

No, it (the Windows Console) sends a Ctrl-V (hex 0x16) to the tty when you hit that keyboard sequence once. That control code in turn gets picked up by the bash shell according to the lnext (literal next) stty(1) setting. The following character, which might or might not be a second Ctrl-V, gets taken literally. So for example, if you were to type just Ctrl-M (hex 0x0d) you get a carriage return (CR). If you type Ctrl-V Ctrl-M you get an uninterpreted literal Ctrl-M.

but a single Ctrl+C does absolutely nothing.

Ctrl-C (by default) causes a SIGINT to be sent by the tty layer, which, if bash has the tty, gets trapped and causes you to get a new prompt line. If a command (child process of bash) is running and has the tty, a SIGINT is sent to that running process, and depending on the process, usually results in the process exiting but could (in principle) do anything (including nothing) depending on the signal handler.
In any event, it appears 1809 hasn't hit the street yet. Ctrl+Shift+V should start pasting into the Windows Console with WSL for you when it does. Bonne chance.

Please stop ripping my sentences apart and putting them out of context. Of course Mike isn't inserting anything into my console.
Let me repeat myself:
Ctrl+V does work in Command Prompt.
Ctrl+V does work in Powershell
Ctrl+V does NOT work in WSL.
You claim WSL runs on the same console. Fine. But in WSL paste doesn't work, so WSL is doing something or whatever that breaks it. So the issue is somehwere around WSL. Not in the windows console, not in command prompt, not in the linux kernel, but that magical layer in between all of them: WSL. The bug is in WSL, because that's the only place where paste doesn't work.
Now please stop arguing about what WSL is or isn't, and accept that paste just doesn't bloody work on WSL only. Please.

accept that paste just doesn't bloody work on WSL

Paste works in WSL. It just has a different keyboard shortcut. This is because of Reasons™.

Of course Mike isn't inserting anything into my console.

I understood you. In your context you meant Mike when you said 'they [the coders] inject typing [by way of their implementation]', and I had already given you a hard time about pronouns. Plus Mike and the rest of the Console team did an amazing job so I wanted to give credit where credit was due.

Ctrl+V does NOT work in WSL.

Ctrl+V does work in WSL (strictly speaking, /bin/bash). bash invokes literal next if that's the stty setting.
ken@DESKTOP-4UTIQSF:~$ stty -a | grep lnext
werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0;

but that magical layer in between all of them: WSL

The layer in between the Windows Console and the WSL kernel is pretty magical, I'll give you that. But ConPTY just passes on the 0x16 unmolested. ConPTY doesn't know what the Windows Console is doing about paste operations either.

Now please stop arguing about what WSL is or isn't

You perceive an argument where none exists. This WSL tracker has been closed since February.

Okay. So instead of sending 0x16, [it could] send all characters in the clipboard?... Doesn't seem like rocket science to me.

Yes, it (the Windows Console) could do that. Wouldn't be rocket science. They (by which I mean Mike) won't, of course, to quoth "ensure that we [Rich means the Console team] don't break any existing behaviors".
In fact it was pretty tricky (maybe not rocket science but definitely computer science) for the Console team to change their paste behavior to Ctrl+Shift+V without breaking existing Powershell behavior or break existing Linux/Unix behavior. Or prevent Ctrl+V from being incongruous with Ctrl+C. Quite a feat really. Which is probably why it took two years.

cc @bitcrazed for Console guidance

Are there any updates to this issue? Seems like the misleading menu option for "Paste Ctrl-V" works but the actual hotkey does not.
It worked for me for a few moments, but a new shell brought it back to the broken state. I was not able to reproduce the working state.
It's also worth noting that while the Ctrl-V hotkey worked, the extended text selection keys (ALT-<arrow keys>, etc.) also worked. Now, both these features do not work. This issue is discussed in https://github.com/microsoft/terminal/issues/715. In summary, these two options in Console Windows Properties seem to have no effect.
Windows 10 Build 18362

@victorlin handling any copy or paste from keystrokes is actually done entirely by the console, and not by WSL itself.
If you're using the regular Windows console, then Ctrl+Shift+C/V feature should be turned on and used for copy and paste from the keyboard, in general Ctrl+V will not work for paste in WSL.
If you'd like to use Ctrl+V for paste (and customize other hotkeys) I'd recommend you start using the Windows Terminal as it's possible there.

@victorlin

👉 Note that now Windows Terminal is available from the Microsoft Store, we strongly encourage you to download and start using it if possible: Terminal is undergoing active development, and provides many features that you and others will find useful, including customizable key-mappings.

As described in the post where we announced Copy & Paste in WSL:
Windows Console - the app you see on screen when you run a command-line shell/app behaves differently depending on what shell/app you're running:
When using Windows Console connected to Cmd or PowerShell, you can paste text using ctrl+v.
When using Windows Console connected to a Linux/WSL instance, if you have checked the relevant checkbox in that Console's "options" properties page, you can paste text using ctrl+shift+v:

When using Linux/WSL, Console is set to "raw" mode in which is sends the chars/VT typed into the keyboard input directly to the attached shell/app (i.e. bash running in Ubuntu), and the shell/app then decides what to do with the input. However, many *nix apps use ctrl+v to perform different actions; for example, page-up in emacs.
To avoid such 'collisions', we instead 'steal' ctrl+shift+v key chords (which have no direct ASCII/VT representation anyway) and generate the correct paste behavior, sending the text on your clipboard to the shell as if they were typed chars.
We provided a way for you to enable/disable this behavior if you ever run a *NIX app which does (somehow/for-some-reason) reserve/require ctrl+shift+v for some pre-defined behavior.
If you want to use ctrl+shift+v in all your command-line shells, launch a Console instance (via Cmd or PowerShell), check the associated setting, and hit Ok.

@bitcrazed thanks for the detailed explanation. Pasting using ctrl+shift+v works as intended.
However, the Edit menu (screenshot in https://github.com/microsoft/WSL/issues/2944#issuecomment-432154388) still shows ctrl+v as the hotkey for Paste. I know this is Windows Console behavior, but the inconsistency may be confusing for many users.
The other issue I referenced (which is unrelated to pasting - let me know if this should be discussed in a new issue) is that extended text selection shift+←/→ does not work in a WSL Console while it works in Powershell/Cmd.

Alas, there's only so much we can change in the Console before we start breaking someone ... somwhere ... usually somewhere really important and critical.
This is one of the main reasons we avoid making UI changes to Console wherever we can, and why we created the new Terminal in the first place: Console's primary job is to preserve backward compatibility. If you want improved/fixed behaviors, we invite you to move to the Terminal where we have MUCH more freedom.
Re. your 2nd point - again, this is due to a limitation in how certain key strokes/chords are converted into ANSI/VT sequences: As per https://support.microfocus.com/kb/doc.php?id=7021621#

Key
Numeric
ANSI ModeApplication
VT52 ModeCursor or Application

Up
CsiA
Ss3A
EscA

Dn
CsiB
Ss3B
EscB

Rt
CsiC
Ss3C
EscC

Lt
CsiD
Ss3D
EscD

There are no ANSI/VT sequences for shift+<arrow> keys.
However, when attached to Cmd or PowerShell, Console is in "cooked input mode" and is able to communicate to Windows command-line apps that arrow keys were clicked with shift modifiers.
Alas, we have no way of introducing a new "lightly-poached input mode" for *NIX apps due to the same reasons as above, so, once again, we encourage you to adopt the new Terminal.

But why is it so hard to add an option to keep Ctrl+V as paste, and Shift+arrow as select? Hell, untick it by default if you're really that afraid of purists with hay forks and torches coming at you when suddenly their obscure terminal program no longer accepts Shift+left as input for some uninteresting feature and they have to go ALL the way into the options to enable insane input behaviour.
The other side of the knife is much sharper, I feel. There are a LOT more people used to cmd.exe on Windows, and simply expect a replacement terminal not to require more effort to do a blatantly simple thing like paste or select. Maybe they are not the kind of people to start a war against Microsoft for not supporting their uninteresting obscure little scripts, but they ARE in much greater numbers.

Now, please, reopen the issue, and consider doing something about it, because even if by design - a bug is a bug. Be it in the program, or in the design, but the bug is still somewhere.

There is no bug in WSL here. There is, pedantically, a mis-labeled menu in cmd.exe. This issue has been closed since 2018 (as a dupe no less) and will not be re-opened.

But why is it so hard to add an option to keep Ctrl+V as paste

That has already been explained at length.

Now, please, reopen the issue

Please stop. You aren't even in the right place to bikeshed.

I don't know what bikeshed means, but no matter how you mansplain why I'm wrong, the issue remains.


Don't remove a reminder's alarm after the reminder has fired

While running the bot I was never able to get !alarmme in 2 minutes;alarm test to work reliably. The initial reminder was triggered just fine but subsequent alarms never happened.
Looking over the code and monitoring the logs (with level set to DEBUG) I observed that after a reminder fires, it deletes itself by calling self.cancel(). However, this call not only removes the reminder but also any associated alarms, causing them to never fire.
After the small fixes in this PR were applied, the alarms started working as expected.

I just realised I did almost the exact same thing as you in https://github.com/anoadragon453/matrix-reminder-bot/commit/6626e93c4c410cde28da7cc00d9c401f58e93244#diff-f0ed4b203f44e8e763bd182949a83224R135 :facepalm:
Thanks for pointing this out, even if I forgot about it and then fixed it later as it was bugging me too much :D
And thanks for the .upper() fix, I had missed that even in that commit. Ported in https://github.com/anoadragon453/matrix-reminder-bot/commit/f1c3b0b847522a9048828a801d85146723e5961b.


CustomEvent.svg needs updating to new style

The problem
Describe the bug
One of these things is not like the others

System (please complete the following information):

Dialogic Version: 1.4.1

Solutions
Possible fixes
Emilio halp!

I'll merge a new one whenever I can 😅

pushed a new icon! feel free to re-open if needed


JIT does not work when prefix callback is specified

What version of @tailwindcss/jit are you using?
0.1.10
What version of Node.js are you using?
15.9.0
What browser are you using?
all of them
What operating system are you using?
macOS
Reproduction repository
https://github.com/signor-pedro/tailwind-repro
Commenting this out makes JIT work
prefix(selector) {
    if (['.align-bottom', '.ml-1'].includes(selector)) {
      return 'tw-';
    }

    return '';
  },

Just to clarify - adding a prefix callback does not break only the classes which should be prefixed.
When I specify the prefix callback, the entire tailwind fails to generate anything (even classes such as bg-indigo-200 which are not manipulated with in any way in the callback)

Added in v0.1.17! There's one limitation which is that you can't do exact matches against dynamically generated utilities, like ml-5. Instead, you'll just want to match against the prefix of the utility, so like this:
prefix(selector) {
  if (['.align-bottom', '.ml'].some(utility => selector.startsWith(utility))) {
    return 'tw-';
  }

  return '';
},

Hopefully this is good enough for the use cases people have for this feature in the real world 👍🏻

Thank you very much, the solution is good enough, only needed to override bootstrap-conflicting classes (which are all the ml-s etc. anyways).
Made my day!


CI: error NETSDK1204: Ahead-of-time compilation is not supported on the current platform 'osx-x64'.

For some reason, sometimes our tests now fail on macOS with the following error:

error NETSDK1204: Ahead-of-time compilation is not supported on the current platform 'osx-x64'.

We should fix this.

We don't even install .NET 8 on CI. WTF.


Any example for using this micro-service framework without Spring?

Our company has been deploying all services based on Vert.x for a long time. I found that some transport modules in this framework is based on Vert.x. However, I didn't find any example for only using Vert.x without Spring. The example in REST over Vertx(http://servicecomb.incubator.apache.org/users/communicate-protocol/) seems depending on Spring as well. Would you please provide some examples without using Spring?

Some of the core components use spring features, and most important part like Spring MVC programming feature. Thus java-chassis can not run without spring yet.

Hi @lmsreborn  , if you had any question, please contact us again, thanks!


Use new address model for address spaces

Remove Instance*

Rename Instance -> AddressSpace

Add SecretCertProvider

Rename instancecontroller -> standardcontroller

Merge address controller into standardcontroller

Change serialization code and introduce serializers on model type instead

Configure resteasy with custom object mapper

Configure endpoints according to address space

Remove creation of routes in templates and create them in address controller

@grs @rgodfrey I don't expect you to review all this code before I merge it, but at least you can see whats going on.


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter email for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.email
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E184] "common.wakeup" is deprecated and ignored. Please remove from io-package.json.
[ ] :heavy_exclamation_mark: [E804] Please process issue [#276] "Compatibility check and testing for node.js 22"

WARNINGS:

[ ] :eyes: [W034] @iobroker/adapter-core 3.1.6 specified. 3.2.2 is recommended. Please consider updating dependencies at package.json
[ ] :eyes: [W127] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W134] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W154] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W184] "common.materialize" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI".
[ ] :eyes: [W953] .npmignore found - consider using package.json object "files" instead.

SUGGESTIONS:

[ ] :pushpin: [S522] Please consider migrating to admin 5 UI (jsonConfig).

Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Suggestions reported by repository checker should be reviewed. Suggestions can be ignored due to a decision of the developer but they are reported as a hint to use a configuration which might get required in future or at least is used be most adapters. Suggestions are always optional to follow.
You may start a new check or force the creation of a new issue at any time by adding the following comment to this issue:
@iobroker-bot recheck
or
@iobroker-bot recreate
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 15 Nov 2024 02:51:39 GMT based on commit b4a329a0f8b6135249c59a5171a480253ce96d9b
ioBroker.repochecker 3.2.2

@ioBroker-Bot recreate


Rename porter-azure to porter-arm.

This is the first pr in the update of the legacy azure mixin. This will transform into
a porter-arm mixin that supports only ARM templates.

/azp run porter-arm


[CARBONDATA-3200] No-Sort compaction

When the data is loaded with SORT_SCOPE as NO_SORT, and done compaction upon, the data still remains unsorted. This does not affect much in query. The major purpose of compaction, is better pack the data and improve query performance.
Now, the expected behaviour of compaction is sort to the data, so that after compaction, query performance becomes better. The columns to sort upon are provided by SORT_COLUMNS.
The new compaction works as follows:

Do sorting on unsorted & restructured data and store in temporary files
Pick a row from those temporary files, and already sorted carbondata files, according to a comparator on sort_columns.
Write data to a new segment (similar to old compaction flow).
Repeat steps 2 & 3 until no more rows are left.

Dependency: PR 3014

[ ] Any interfaces changed?  -->  No
[ ] Any backward compatibility impacted?   -->  No
[ ] Document update required?  ->  No
[ ] Testing done
[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2254/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10299/

Need it add a param to control whether to sort when no_sort?
Maybe user only want to merge small segments to a big segment, slow data merging may be unaccepted

@qiuchenjian We dont need a parameter to control to control whether to sort the data or not while compacting. The sole purpose of compaction is to improve subsequent query performance, and even though the compaction gets slow, it is doing what is intended.

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10325/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2071/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2276/

@NamanRastogi Lots of code is duplicated here, Please try to unify with other compactor processor to avoid the duplication.

@NamanRastogi You can merge HybridSorter into CompactionResultSortProcessor. For unsorted file it will be same flow, for sorted file you add one adapter(InMemorySortTempFileChunkHolder) on top of  RawResultIterator which will be inline with SortTempFileChunkHolder class so Interface will be same.  And In SingleThreadFinalMerger expose one method which will take List of Sorted RawResultIterator and add to record holder heap(PrirotyQueue).
InMemorySortTempFileChunkHolder you have to convert Object[] to IntermediateSortTempRow in getRowMethod

@NamanRastogi please resolve conflicts and fix all failure

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2328/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2120/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10376/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2123/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2127/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2333/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10381/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2334/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2128/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10382/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10383/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2335/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10385/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2337/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2137/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10391/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2343/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2138/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2344/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10392/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2355/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2146/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2364/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10403/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2150/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10405/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2155/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10409/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2368/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder2.1/2166/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/2380/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:8080/job/carbondataprbuilder2.3/10422/


[BottomNavigationButton] onClick and onChange handler overwritten

The handler that invokes onChange and onClick will be overwritten if an onClick prop is provided.
We're not pulling the onClick prop out in the destructure, so when we apply other to ButtonBase, we overwrite the onClick handler.  The unit test is evergreen, because it's checking to see if the spy we're passing in is being called when click is simulated, which it is, though not through the handleChange method.
To fix this, I've pulled onClick before destructuring.  If onClick is provided, it will be invoked in the handleChange class method.  I've also added some tests to get BottomNavigationButton to 100% code coverage (part of the effort for #9527).

All set!

@kgregory You need to rebase, I have fixed the failing build on HEAD.


The released weight fails to reproduce performance as reported

Hi! Images generated via weights released led to worse reported numbers compared to those in the paper, may I ask how many epochs of training required for reproduction, and the epochs you have trained for your released weights, thanks.

The released pre-trained weight is exactly the one we used for evaluation in our paper.

we modified your test.py to gen full val set and bicubic upsample followed by pad top, as described in another issue. Then we swap the gen val set to nus and do cvt & bevfusion validation without modifying the downstream codes. could there be any thing wrong in our practice, please shed some light!

As your descriptions seem to match our paper, they are correct. Please look into more details to discover any possible issues in your implementation. Otherwise, please wait patiently for our future updates.
If this is the answer you want, there is no special trick in our evaluation (e.g., we used all scenes from the val dataset and all boxes). Sorry, I cannot help you with such a general question. I will close this issue.
If you have any specific problems, please open other issues and post them there, just like others did.


Make heart and sun emojis default, but removable

Requested by user zero

This can be deleted : https://github.com/Terkwood/grats/blob/994593f95a0250d931916b3d716e4d04d2cad4c5/src/model/mod.rs#L25


Pulling out higher level relations with UMLS entity linking?

I'm interested in categorizing the UMLS entities into some broader categories. For example, an entity linked to "Intestines" (C0021853) is also a narrower concept of "Gastrointestinal system" (C0012240).
Using the TUI I can get the larger group, but these are quite broad (i.e. Intestines is linked to TUI "Body Part, Organ, or Organ Component").
Is there a way within scispaCy to explore the relationships among the linked UMLS entities?

Hi @maxfarrell,
Unfortunately we haven't preserved that information in the pruning of UMLS that we use to do entity linking (it would be nice to keep all the info in UMLS, but it quickly makes the KB impractically large). To do this you'd need a copy of UMLS yourself, which you could then extract these relations from.
One idea as an approximation to this would be to group all the concepts which share any aliases? This might give you reasonable groupings, maybe.

Closing due to inactivity/I think I roughly answered your question :)