move debugging tips to separate optional lab

this is a grab bag of topics that could possibly included in another lab at point of use, but I feel is better isolated to a separate location for reference.

Seems like we should at least mention this lab in the readme.

@duglin I agree, we need entries for 3 and 4 as well.

Down here, right https://github.com/IBM/kube101/blame/master/workshop/README.md#L161-L167 ?

@brahmaroutu to handle

@duglin I wrote up the direct link to the lab text. Should be done with this PR for now.


[WIP] Initial draft of Prologue.

This is a very preliminary draft of the zeroth chapter, following notes at https://github.com/clawpack/riemann_book/wiki/Introductory-notebook-outline.  It's pretty straightforward, but I'm not very happy with it.  It feels too dry for an introduction.  I'm wondering if we should turn it on its head by starting with an interesting example as motivation and then working backward to the basics from that.
I haven't filled in the later parts of the chapter (shallow water example, approximate solutions, and generalizations).
Please criticize, or just take this and rewrite it in a better way.

Closed in favor of #62.


Add CSS tree-sitter language

Requires upstream changes to bump to tree-sitter 0.20.
Upstream PR: https://github.com/tree-sitter/tree-sitter-css/pull/22
Tree sitter issue: https://github.com/lapce/lapce/issues/272

Upstream repository has been silent for the last 7 months. Should be fork it to unblock this PR?

Upstream repository has been silent for the last 7 months. Should be fork it to unblock this PR?

Sorry for the radio silence, yep seems like that may be a better way forward. Shame that the upstream is so slow.
Cheers

This can be closed as CSS tree-sitter was added in https://github.com/lapce/lapce/commit/c2e08d08b1be592a8c5b717213bf71cf3e2fbdf3


si.blockDevices and si.fsSize intermittently returns network mapped drives

Describe the bug
si.blockDevices and si.fsSize intermittently returns network mapped drives. Most of the time doesn't return the network mapped drives.
To Reproduce
Steps to reproduce the behavior:

used functions: si.blockDevices and si.fsSize, both returns or not returns network mapped drives

async function fsSize() {     var data = await si.fsSize()         console.log(data)     }
or
async function blockDevices() {     var data = await si.blockDevices()         console.log(data)     }
Current Output
Returns "C:", "D:"
Expected behavior
Returns "C:", "D:", "N:"
I double checked and N: is right mapped
Environment (please complete the following information):

systeminformation package version: 5.1.1
OS: Windows 10 20H2
Hardware: Dell G3 notebook

Additional context
Would suggest to implement a new function:
getNetworkMappedDrives()
and use the:
Get-ItemProperty -Path "HKCU:\Network\*"
To return network mapped drives from Windows Registry.

@dverzolla  can you check the output of
wmic logicaldisk get /value

and post result here (as text)? Maybe you have to do it several times ... as you describe that the output is not consistent ... systeminformation is relying on the output of this command.

@dverzolla ... just checked here on my side ... cannot reproduce this behaviour. Network drives are shown properly
Tested on

Windows 10
systeminformation 5.1.1
Hardware: Shuttle PC

@sebhildebrandt congrats for the superb project! It's been really helpful in my project.
As you can see bellow, the wmic logicaldisk get /value doesn't show mapped network "N:".
And yes, the network is mapped and is accessible. I even rebooted the machine and 'wmic' still doesn't show it.
Maybe is something on my network configuration (I will reach the administrator), but if other systeminformation users are having the same issue, maybe you could overcome this doing the query to windows register: Get-ItemProperty -Path "HKCU:\Network\*"
wmic logicaldisk get /value output:
Access=0
Availability=
BlockSize=
Caption=C:
Compressed=FALSE
ConfigManagerErrorCode=
ConfigManagerUserConfig=
CreationClassName=Win32_LogicalDisk
Description=Disco Fixo Local
DeviceID=C:
DriveType=3
ErrorCleared=
ErrorDescription=
ErrorMethodology=
FileSystem=NTFS
FreeSpace=29622661120
InstallDate=
LastErrorCode=
MaximumComponentLength=255
MediaType=12
Name=C:
NumberOfBlocks=
PNPDeviceID=
PowerManagementCapabilities=
PowerManagementSupported=
ProviderName=
Purpose=
QuotasDisabled=TRUE
QuotasIncomplete=FALSE
QuotasRebuilding=FALSE
Size=233551425536
Status=
StatusInfo=
SupportsDiskQuotas=TRUE
SupportsFileBasedCompression=TRUE
SystemCreationClassName=Win32_ComputerSystem
SystemName=DS-PC-026
VolumeDirty=FALSE
VolumeName=OS
VolumeSerialNumber=B82A47A5
Access=0
Availability=
BlockSize=
Caption=D:
Compressed=FALSE
ConfigManagerErrorCode=
ConfigManagerUserConfig=
CreationClassName=Win32_LogicalDisk
Description=Disco Fixo Local
DeviceID=D:
DriveType=3
ErrorCleared=
ErrorDescription=
ErrorMethodology=
FileSystem=NTFS
FreeSpace=8610824192
InstallDate=
LastErrorCode=
MaximumComponentLength=255
MediaType=12
Name=D:
NumberOfBlocks=
PNPDeviceID=
PowerManagementCapabilities=
PowerManagementSupported=
ProviderName=
Purpose=
QuotasDisabled=TRUE
QuotasIncomplete=FALSE
QuotasRebuilding=FALSE
Size=912261115904
Status=
StatusInfo=
SupportsDiskQuotas=TRUE
SupportsFileBasedCompression=TRUE
SystemCreationClassName=Win32_ComputerSystem
SystemName=DS-PC-026
VolumeDirty=FALSE
VolumeName=Samsung
VolumeSerialNumber=7EF6A5AF

@dverzolla as you can see, I would need all information from the above command and the windows registry would not provide all this...
As I did not heard from others having a problem here, I guess we should wait a few days and if there is no further response, I would close this one, OK?

Sure,  appreciate.
On Mon, Feb 8, 2021 at 1:18 PM Sebastian Hildebrandt <
<EMAIL_ADDRESS>wrote:

@dverzolla https://github.com/dverzolla as you can see, I would need
all information from the above command and the windows registry would not
provide all this...
As I did not heard from others having a problem here, I guess we should
wait a few days and if there is no further response, I would close this
one, OK?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sebhildebrandt/systeminformation/issues/483#issuecomment-775261979,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAR4HU324CETCTIYKJ3FCRDS6AFDVANCNFSM4XJBPATQ
.

--
David Verzolla

Just adding a note here for further reference.
When I run wmic logicaldisk get /value inside windows terminal, it returns "N:", as bellow. Running straight in powershell or cmd (either using admin privileges or not), doesn't show "N:".
Access=0
Availability=
BlockSize=
Caption=N:
Compressed=FALSE
ConfigManagerErrorCode=
ConfigManagerUserConfig=
CreationClassName=Win32_LogicalDisk
Description=Conexão de Rede
DeviceID=N:
DriveType=4
ErrorCleared=
ErrorDescription=
ErrorMethodology=
FileSystem=NTFS
FreeSpace=514544680960
InstallDate=
LastErrorCode=
MaximumComponentLength=255
MediaType=0
Name=N:
NumberOfBlocks=
PNPDeviceID=
PowerManagementCapabilities=
PowerManagementSupported=
ProviderName=\<IP_ADDRESS>\data
Purpose=
QuotasDisabled=
QuotasIncomplete=
QuotasRebuilding=
Size=1019556659200
Status=
StatusInfo=
SupportsDiskQuotas=FALSE
SupportsFileBasedCompression=FALSE
SystemCreationClassName=Win32_ComputerSystem
SystemName=DS-PC-026
VolumeDirty=
VolumeName=Dados
VolumeSerialNumber=061840B5

@sebhildebrandt I think I've found the weird behaviour. Seems to be the privilege I ran powershell with.
When I run powershell using Administrator privileges, the network mapped are not being shown, otherwise, with my user privileges (that have mapped the network drives), the network drives are returned.
Please, could you try at your side?
 As drives are mapped per user, this should be absolutely fine ... closing this for now.


Certificate has expired.

Certificate has expired (valid from 5/18/2018 to 5/18/2019). Can anyone renew this please? :)

#43 also https://github.com/kprinssu/anne-keyboard-windows/issues/47#issuecomment-472069240

Can someone repackage the tool? Right now we can't install it.

I will be doing a new build later this weekend. Please wait until then.

I will be doing a new build later this weekend. Please wait until then.

My birthday is on June 12th! Do you think you could renew the certificate so I can use your great app please? 😄

Well then

Any news on the new build?

This is no longer actively maintained. Check out https://github.com/IOIIIO/anne-keyboard-windows for the latest fork

That one also says the certificate has expired >_>

@ethanmsmith I downloaded the file to the linked repository and ran it, but it still says that the certificate has expired.
Is there any way I can use it?

Due to me working full-time and switching over to Linux/macOS, I do not think I will be providing support for this project.
Please consider using the official Obins app or building this app from scratch.


Add orthographic camera support back to directional shadows

Objective
Fixes #7797
Solution
This seems like a simple fix, but I'm not 100% confident and I may have messed up the math in some way. In particular, I'm not sure what I should be using for an FOV value.
However, this seems to be producing similar results to 0.9.
Here's the orthographic example with a default directional light.

One moment, this does not work.

Actually, I'm 99% confident that the value I'm using for the tan_half_fov is nonsensical and that this isn't working properly.
I'll dig into it more later or hopefully a rendering expert can chime in.

Maybe something along these lines, breaking the "frustum corners" math into a separate function: https://github.com/rparrett/bevy/tree/orthographic-directional-two

I merged that other experimental branch into this one, because testing on the naive solution I first attempted showed that it was obviously broken with very unstable shadows.
This is is behaving much better, but needs more testing.

It seems that this approach also has stability issues.

https://user-images.githubusercontent.com/200550/221083612-fef8dcb5-a5d7-49ee-bfc7-25a9586828b8.mov
I think this is working properly.
Note: Unlike perspective projections, maximum_distance seems very effective at increasing shadow quality.

If you don't mind, could you double check those corners again? After applying the last two suggestions they seemed obviously wrong/different for the far plane.

If you don't mind, could you double check those corners again? After applying the last two suggestions they seemed obviously wrong/different for the far plane.

Looks good to me! I wonder if github suggestions was doing some weird with them

bors r+


使用阿里云的amqp rabbitmq时报错

使用阿里云的amqp rabbitmq时报错  reply-text=QueueConsumerNameInvalid，咨询阿里得知因为他们$是非法字符，而zipkin的consumertag是zipkin2.collector.rabbitmq.RabbitMQCollector$RabbitMQSpanConsumer0

sorry google translate isn't working well. Do you mean to say if there are
chinese characters in a consumer tag, the rabbitmq feature errors?

"$"   this character

This is in inner class that's why there is a $ character.
I'm unclear what impact this has, can you post an exception or error message?

please take a look at this https://github.com/openzipkin/zipkin/pull/2641


Added recursion to array/linalg/tsqr to better manage the single core bottleneck

Added recursion to tsqr to better manage the single core bottleneck.
For example: a (200000 × (10000, 100)) tower of blocks will end up with a (200000×100, 100) QR decomposition to compute in the single core case. This would be significantly bigger than the expectation of having to do computes on (10000, 100) blocks. We can lighten that load by turning that single core step into a (20000 × (1000, 100)) recursive call, which becomes (2000 × (1000, 100)) then  (200 × (1000, 100)) then  (20 × (1000, 100)) then (2 × (1000, 100)) then a single core  (200, 100) QR compute.
More elaboration in: https://github.com/dask/dask/issues/3584
A balance is struck by only recursing when there is a need for it (the single core compute has to work on a block/chunk larger than the largest chunk) and when "meaningful reduction can be made" in the size of the single core compute (aspect ratio of the tall-and-skinny chunks is at least 2; the above example has an aspect ratio of 10).

[X] A few tests added (various recursion depths)
[X] Existing tests passed
[X] Passes flake8 dask

This appears to conflict with master.  Depending on how familiar you are with git you might want to rebase and remove the old commits from the previous PR.

The code might look a bit inelegant. But I figure the verbosity for array output dimensions makes it a little more comprehensible (to me at least)...

Incidentally, I just did a quick merge of master into the branch. Hope there's no issue with that.

The code might look a bit inelegant. But I figure the verbosity for array output dimensions makes it a little more comprehensible (to me at least)...

Can you recommend a good example problem to play with this?  Something that would perform poorly before but now works well?  I wouldn't mind using this solution first to build confidence before diving into the code.

But the source code is fairly simple.... the change is that it checks if it should do recursion and does/does not do it to compute Q and R. Then the rest of the code proceeds as per normal, with the modifications to make sure output sizes are correct. (I don’t have that much faith in that bit, but the tests have reasonable coverage, and they pass.)

I enjoyed playing with this.  I ran the following computation and looked at the output of the distributed scheduler's graph page:
import dask.array as da
x = da.random.random((2000000, 100), chunks=(5000, 100))

q, r = da.linalg.qr(x)

Before

After

I did push a small change to your fork to update all of the keynames.  This helps them come through on the diagnostic dashboard a bit better.  You may want to pull from your branch before you start any more work here.

@marianotepper you may want to take a look at this modification of your tsqr implementation

I 💖 Graph.
Remember how confused I was when I first tried .persist()... why is this still there... why is it... persisting.

Just noticed that stuff is failing?
What happened with test_bag?  Running it in the REPL or in Jupyter, there are problems:
Thu Jun 14, 01:50:55 !603 $ python3
Python 3.6.5 (default, Mar 30 2018, 06:41:53)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-9<IP_ADDRESS>)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import dask.bag as db
>>> urls = ['https://raw.githubusercontent.com/weierophinney/pastebin/'
...         'master/public/js-src/dojox/data/tests/stores/patterns.csv',
...         #'https://en.wikipedia.org'
...        ]
>>> b = db.read_text(urls)
>>> b.npartitions  # assert b.npartitions == 2
1
>>> b.compute()
['uniqueId, value\n', '9, jfq4@#!$!@Rf14r14i5u\n', '6, BaBaMaSaRa***Foo\n', '2, bar*foo\n', '8, 123abc\n', '4, bit$Bite\n', '3, 123abc\n', '10, 123abcdefg\n', '1, foo*bar\n', '7, \n', '5, ']
>>> import dask.bag as db
>>> urls = ['https://raw.githubusercontent.com/weierophinney/pastebin/'
...         'master/public/js-src/dojox/data/tests/stores/patterns.csv',
...         'https://en.wikipedia.org'
...        ]
>>> b = db.read_text(urls)
>>> b.npartitions  # assert b.npartitions == 2
2
>>> b.compute()
objc[75111]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[75111]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
objc[75113]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[75113]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.

Don't know enough about bags to know what in https://en.wikipedia.org could be so toxic... Oh... wait...

Ok... It fails with more than 1 url. Either on its own works.

Either on its own works.

That's just weird. I guess maybe some endpoints do not like to be poked too often?
The possible cases have come to my notice recently

a server which provides no content length; anything dynamic (like wikipedia) should do this, but so long as its smaller than the blocksize, it works fine
the server provides the compressed length, not the final length; maybe requesting 'identity' encoding in the HEAD call copes with this (was an issue for github content), but haven't implemented this
the URL redirects, which for GET gets you the final content but HEAD gets you the redirect itself. Can add allow_redirect=True explicitly to the HEAD call.

Naturally, these are all tricky to test.

Do you have thoughts on how to address this short term so that other PRs aren't affected?

I could pop in identity and allow_redirect; or possibly try to find URLs that we can have more confidence in (s3/gcs public links?)

Would look like https://github.com/martindurant/dask/commit/76d415b29941c5a017ad79a8771a1886f324bd3f

OK, I've restarted tests and they pass.
@martindurant if you're able to resolve the http test that would be welcome.  I get nervous when I start getting into the habit of manually restarting tests.  We're in that state with dask/distributed and it is definitely a drag on productivity.
@convexset this looks great to me.  I appreciate the clean code and good test coverage.  I'm happy to merge.  However, I wonder if you'd be up for putting an analysis of the memory requirements of the algorithm within the docstring.  I suspect that what is in there curently is incorrect, and that future developers like yourself might appreciate a concrete statement of how this algorithm behaves according to array and chunk size.

I'm also personally curious what drew you to this problem.
More nefariously, I'm also wondering what other kinds of problems I might be able to convince you to solve in the future ;)

Oh... I was preparing a tutorial for dask. (As Pandas++ with dask data frames, numpy++ with dask arrays, Python++ with dask bag, and scikit-learn+ with dask-ml/dask-search-cv...) And I couldn't do a QR decomposition... Then I dug into the source and found out. Rabbit holes...
Add to the doc string. And probably make the recursion criterion adjustable (it's currently "a factor of 2" but I can see how some might want factors of 10).

could you remove the elements which you think inadvisable? use_recursion for example

Is it safe to remove?  Are there cases where using it is necessary?  The sense I've gotten from your PR is that recursion here seems to always be worth it when the algorithm decides so.  Are there fail cases?

_max_vchunk_size is used internally to keep track of the maximum chunk height from the first invocation because that might actually contract if things cannot be "nicely tiled".

OK, that helps explain things.  Perhaps it would be good to include a small note that that parameter is used internally during recursion, and should not be set by users?

k blocks of (m,n) ---> one (kn, n) block to distribute... multiples of n might not include m.

I'm not sure I understand what question this answers.  Is this a cost in addition to the O(mn) memory use?  My apologies for being a bit scattered here.  I've been bouncing between several problems like this one over the past couple days.

I removed use_recursion and tidied up the documentation.
Anyway, with regards to memory usage... Let's talk about k m×n blocks.
The first pass of QR decompositions require the storage of a large Q, and smaller R are stacked into multiple chunks for the next pass. (kmn storage)
After that next pass, the large Q's are stored again, now we need kmn (n/m) more storage.
After that next pass, the large Q's are stored again, and we need kmn (n/m)^2 more storage.
Each time, the space requirement decreases by a factor of m/n (so tall blocks see this going down fast).
\int_0^{\infty} exp(-αx) dx = 1/α... so...
\int_0^{\infty} (m/n)^{-x} dx = 1 / ln (m/n)
So, where m/n is 2... we have 1.44269504, and it gets smaller the bigger m/n is...
Ok... I'm removing the log factor since we have a bound.

OK, merging this. Thanks again @convexset !

Anyway, if there is a map of things that are nice to have but to be done. I'd gladly take a look and try my hand at something.

Well, there are currently a few hundred issues in the issue tracker but wading through them all is probably not the most fun activity.  If you have particular interests we can probably find something or ask around.  So far it seems like you're interested in distributed linear algebra and algorithmic code.  Do you have any other interests?  There are plenty of fun problems out there.  Given the little I know about your interests so far, here are some potential issues:

https://github.com/dask/dask/issues/3576
https://github.com/dask/dask/issues/3554
https://github.com/dask/dask/issues/3377
https://github.com/dask/dask/issues/2851

Also, it would be useful to get your take on these issues after this PR.  It may be that you have resolved them:

https://github.com/dask/dask/issues/3419
https://github.com/dask/dask/issues/2675

I was also playing with this issue yesterday and found it quite interesting.  It's also something that I would find personally valuable:

https://github.com/dask/dask/issues/2225


New Daikin Cloud Portal

Hi,
since july 4th the integration seems broken...
i think the cause it's the new Daikin Cloud Portal, the oldest api are been closed...
There's on track a new implementation to close the gap with new daikin portal?

Duplicate to #28


opensearch-dashboards-functional test repo should always checkout release branch head commit

Description
Added a new parameter to test_args "--ft-repo-ref" which allows users to specify which branch they want to checkout when testing opensearch-dashboards-functional test repo.
Issues Resolved
Closes #4057
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thanks for contribution @chawinphat.
To my understanding, this PR added a new parameter for user to specify a ref.
If not, then default back to the commit from build manifest.
If so, then the title should be corrected as it is not always checkout release branch head commit.
Please correct me if that is not the case.
Thanks.

Close in favor:

#4419


Getting warning from Sql task on hosted Windows agent

==============================================================================
Task         : Azure SQL Database deployment
Description  : Deploy an Azure SQL Database using DACPAC or run scripts using SQLCMD
Version      : 1.216.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/sql-azure-dacpac-deployment
==============================================================================
Added TLS 1.2 in session.
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.

I am also getting this from AzureFileCopy@3
Added TLS 1.2 in session.
Import-Module -Name C:\modules\azurerm_6.13.1\AzureRM\6.13.1\AzureRM.psd1 -Global
Clear-AzureRmContext -Scope Process
Clear-AzureRmContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Add-AzureRMAccount -ServicePrincipal -Tenant XXX -Credential System.Management.Automation.PSCredential -Environment AzureCloud
 Set-AzureRmContext -SubscriptionId XXX -TenantId XXX
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.

Receiving same warning on on-premises. Any solutions?

Same warnings on AzureFileCopy@4 and AzureFileCopy@5 as well.

Same here with AzureFileCopy@4.

Output from AzureFileCopy@5 task:
`==============================================================================
Task         : Azure file copy
Description  : Copy files to Azure Blob Storage or virtual machines
Version      : 5.216.2
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-file-copy
Added TLS 1.2 in session.
##[command]Import-Module -Name C:\Modules\az_9.2.0\Az.Accounts\2.11.1\Az.Accounts.psd1 -Global
##[warning]Both Az and AzureRM modules were detected on this machine. Az and AzureRM modules cannot be imported in the same session or used in the same script or runbook. If you are running PowerShell in an environment you control you can use the 'Uninstall-AzureRm' cmdlet to remove all AzureRm modules from your machine. If you are running in Azure Automation, take care that none of your runbooks import both Az and AzureRM modules. More information can be found here: https://aka.ms/azps-migration-guide
##[command]Clear-AzContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
##[command]Clear-AzContext -Scope Process
##[command]Connect-AzAccount -ServicePrincipal -Tenant xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -Credential System.Management.Automation.PSCredential -Environment AzureCloud @processScope
##[command] Set-AzContext -SubscriptionId xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -TenantId xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
##[command]Import-Module -Name C:\Modules\az_9.2.0\Az.Resources\6.5.0\Az.Resources.psd1 -Global
##[command]Import-Module -Name C:\Modules\az_9.2.0\Az.Storage\5.2.0\Az.Storage.psd1 -Global
##[command]Import-Module -Name C:\Modules\az_9.2.0\Az.Compute\5.2.0\Az.Compute.psd1 -Global
##[command]Import-Module -Name C:\Modules\az_9.2.0\Az.Network\5.2.0\Az.Network.psd1 -Global
##[warning]The names of some imported commands from the module 'Microsoft.Azure.PowerShell.Cmdlets.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
##[warning]The names of some imported commands from the module 'Az.Network' include unapproved verbs that might make them less discoverable. To find the commands with unapproved verbs, run the Import-Module command again with the Verbose parameter. For a list of approved verbs, type Get-Verb.
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.`

We have the same problem: AzureFileCopy@4 and AzureFileCopy@5 output the
##[warning]The command ‘Get-SpnAccessToken’ is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.
line.
Until now this we perceived no functional degradation yet but it remains to be seen until what date and time we can use the function...
It seems that version 5 is the latest version so an update of the AzureFileCopy component would be very welcome

I'm getting the same warning message on AzureFileCopy version 3.216.2 on a MS hosted Windows vm.
Import-Module -Name C:\modules\azurerm_6.13.1\AzureRM\6.13.1\AzureRM.psd1 -Global
Clear-AzureRmContext -Scope Process
Clear-AzureRmContext -Scope CurrentUser -Force -ErrorAction SilentlyContinue
Add-AzureRMAccount -ServicePrincipal -Tenant x-y-z -Credential System.Management.Automation.PSCredential -Environment AzureCloud
 Set-AzureRmContext -SubscriptionId x-y-z -TenantId x-y-z
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.

Agent details:
Current agent version: '2.217.2'
Operating System: Microsoft Windows Server 2022 10.0.20348 Datacenter
Runner Image: windows-2022, Version: 20230129.1
Runner Image Provisioner: <IP_ADDRESS>

Me too

Same here for Azure File Copy Task @5.216.2, even after upgrading all components to latest version and implementing new AZ powershell modules instead of AzureRM modules on the build  agent,

Same here. We are seeing the same warning in both Azure File Copy Task @3 and 5.

Same here. V4 and 5
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.

Since somebody asked me about this I looked into it.
It looks like it is due to the update to VstsAzureRestHelpers_.psm1 from November 17 last year. Might be worth checking if another update elsewhere has been delayed.
https://github.com/microsoft/azure-pipelines-tasks/commit/f88343acf27b53cd8fa4112f76b7ac2bf84df14b#diff-e7717abe1d4a4bc136d4e37c1e2695fc81b89047c49dfd7adf9b155d9135a2b9

+1

When running DACPAC task we get the same warning but when enabling "System.Debug" logging I became aware of an environment variable named USE_MSAL.
Result with default value for USE_MSAL (empty)
##[debug]Get-AzureRMAccessToken - started - endpoint=@{Url=https://management.azure.com/; Data=; Auth=} - scheme=ServicePrincipal
##[debug]USE_MSAL (empty)
##[debug]MSAL - useMSAL = False
##[warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.
##[debug]Processed: ##vso[task.logissue type=warning]The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed.
##[debug]MSAL - Get-EnvironmentAuthUrl - endpoint=@{Url=https://management.azure.com/; Data=; Auth=}
##[debug]MSAL - Get-EnvironmentAuthUrl - useMSAL=False
##[debug]MSAL - Get-EnvironmentAuthUrl - envAuthUrl=https://login.windows.net/
##[debug]Fetching Access Token

Result with USE_MSAL set to true
##[debug]Get-AzureRMAccessToken - started - endpoint=@{Url=https://management.azure.com/; Data=; Auth=} - scheme=ServicePrincipal
##[debug]USE_MSAL: 'true'
##[debug]MSAL - USE_MSAL override is found: true
##[debug]MSAL - useMSAL = True
##[debug]MSAL - Get-EnvironmentAuthUrl - endpoint=@{Url=https://management.azure.com/; Data=; Auth=}
##[debug]MSAL - Get-EnvironmentAuthUrl - useMSAL=True
##[debug]MSAL - Get-EnvironmentAuthUrl - envAuthUrl=https://login.microsoftonline.com/
##[debug]MSAL - ServicePrincipal - clientSecret is used.
##[debug]Fetching Access Token - MSAL

Hopefully this helps.

Thank you @Nubbe. Setting a variable USE_MSAL=true actually works!

Hi @Nubbe ,
Can you please let me know where need to configure the value in Azure Devops pipeline?

@mamohanma Just add a variable with key USE_MSAL and value "true". What I did was use powershell to write the variable just for the task: Write-Host "##vso[task.setvariable variable=USE_MSAL]true"

Hi @celluj34 ,
Thanks for your information.
Actually I am not familiar with Azure DevOps. So do you have any reference link for this setup.?
We are using Azure DevOps pipeline, within that we configured the SQL deployment. in that SQL deployment we are getting the warning "The command 'Get-SpnAccessToken' is obsolete. Use Get-AccessTokenMSAL instead. This will be removed".

Literally all you need to do is, before your SQL task, add a powershell (or bash, or whatever is appropriate) task and Write-Host (or echo, for bash) the task.setvariable command I wrote above. That's it.

Literally all you need to do is, before your SQL task, add a powershell (or bash, or whatever is appropriate) task and Write-Host (or echo, for bash) the task.setvariable command I wrote above. That's it.

This worked for me in the in my release pipeline, thank you sir.

For people having trouble with implementing it, here's an example:
steps:
  - powershell: Write-Host "##vso[task.setvariable variable=USE_MSAL]true"
    displayName: USE MSAL

    ... (other tasks)

Literally all you need to do is, before your SQL task, add a powershell (or bash, or whatever is appropriate) task and Write-Host (or echo, for bash) the task.setvariable command I wrote above. That's it.

Can't you use the env property on the task as well for this ?   Haven't tested it, but I think this would be more elegant :)

You can! But I already had a script doing stuff so I just put it there.

Regrettably this did not solve the issue for me. The variable has been set but in the following call of azure file copy I still get warning and error messages:
##[warning]The provided service principal secret will be included in the 'AzureRmContext.json' file found in the user profile ( C:\Windows\system32\config\systemprofile.Azure ). Please ensure that this directory has appropriate protections.
##[error]ExceptionMesge: ExceptionMesge: Authentication failed. The 'Authorization' header is provided in an invalid format. (in function: Get-AzRmResourceGroup) (in function: Get-AzRMStorageKeys)
although the warning does not seem to imply a big deal the error still will have to be fixed.

For people having trouble with implementing it, here's an example:
steps:
  - powershell: Write-Host "##vso[task.setvariable variable=USE_MSAL]true"
    displayName: USE MSAL

    ... (other tasks)

Actually, if you're using YAML pipelines, you can define this with your other variables:
variables:
  # These variables are for testing and deugging.
  buildTestOnly: false
  devTestOnly: false
  system.debug: false
  USE_MSAL: true # https://github.com/microsoft/azure-pipelines-tasks/issues/17677

  # If all tests have passed, we can set prodReady to true.
  prodReady: true

My pipeline says "user can't override USE_MSAL system variable" when I try and override it in the variables.
##[error]Unable to process command '##vso[task.setvariable variable=USE_MSAL]true' successfully. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=817296)
##[error]Overwriting readonly variable 'USE_MSAL' is not permitted. See https://github.com/microsoft/azure-pipelines-yaml/blob/master/design/readonly-variables.md for details.

I had the same error. Could it be that it's true by default now? I removed the script to set it to true, but the warnings or errors from before did not return.


Test error when creating user

Hi,
Got an error when logging in with a new LDAP user. The problem was the admin I manually created with WP had the same mail address than my ldap user.
The worst thing is that it does not report it even in debug mode and server gives a 500 error :
PHP Catchable fatal error:  Object of class WP_Error could not be converted to string in /var/www/[.....]/wp-content/plugins/authldap/authLdap.php on line 345
Made this quick fix at least to have the info in debug mode, but a clear message back to the user should be great if possible.
-------------------- (starting line  342 of authLdap.php)
// if the user exists, wp_insert_user will update the existing user record
$userid = wp_insert_user($user_info);
    // CODE ADDED
    if( !is_wp_error($userid) ) {
       authLdap_debug('user id = ' . $userid);
    } else {
       authLdap_debug('Error creating user : ' . $userid->get_error_message());
       throw new UnexpectedValueException('Error creating user');
    }
     // END CODE ADDED
    // flag the user as an ldap user so we can hide the password fields in the user profile
    update_user_meta($userid, 'authLDAP', true);

And thanks for the plugin.
Regards,
Patrick

This is a duplicate of #20. Thanks for the fix which I will implement tomorrow.

@patrickpr We can't actually give a hint on the login-page but I added a log-entry to the authLDAP-debug log as well as to the error-log of the web-server.
As a failing LDAP-login falls back to authenticating against the default wordpress-database only their error-messages are displayed in the login form :frowning:


BatchImage.IsUseless() and checking white list

the current method of sorting our white list entries and then checking against sorted entries introduces extra output sometimes...
E.g.
"snaka under NOTmab11, stroma, NOTepi",
"bk under snaka, stroma, NOTepi"
will also match
NOTmab11 under snaka, stroma, NOTepi
This is only an issue when markers become masks that are already valid in prior white list entries.

Another issue here is that this is terribly inefficient. Instead of generating all possibilities (which is O(n!) ), we should be parsing the input and generating only the Masks and Markers needed. That will resolve this bug as well as improve run times dramatically. The code in question is:
def MasksFromList(self, mask_list, combination_max):
        """
        Given a list of Mask or Marker objects
        returns a list of all combinations of masks
        in the form of a tuple. (mask_loc,name)
        """
        mask_tuples = []
        count = 0
        for lim in xrange(1, combination_max+1):
                for item in itertools.combinations(mask_list, lim):

                    # Create our list of names
                    names = [x.name for x in item]
                    # If this combination is not useless...
                    if not self.IsUseless(names):
                        count += 1
                        # TODO: A BatchImage object should really have a sense of what batch its operating on.
                        # Some meta data like the path of the batch should be sufficient to log meaningful info.
                        logger.debug("Processing Mask {0}".format(count))
                        # our original mask will have all indices in it
                        output_mask = np.arange(0, self.num_pixels)
                        for mask in item:
                            # like a cumsum of intersections...
                            output_mask = GetIntersection(output_mask, mask.masked_indices.flatten())
                        names = ', '.join(names)
                        mask_tuples.append((output_mask, names))

        return mask_tuples

Solved by PR: #18


[Tabular][Bugfix] Fix windows int32 issue on skl2onnx

Issue #, if available:
https://github.com/autogluon/autogluon/actions/runs/3747457242/jobs/6363705204
Description of changes:
fix windows int32 issue on skl2onnx
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/platform_tests


seahawks data is outdated

Hi I hope this addon is still maintained because I was using it a lot!
unfortunately there are no new videos on the seahawks channel since the playoffs.

Hi! Sorry about the late response, I only got around to test it today. I am seeing up to date videos with the NFL Teams plugin for Seahawks. Which version of the plugin do you have? The latest version is 1.3.2 and is available through the official repository.

I have updated the plugin now to version 1.3.3. It adds sorting by dates for teams such as Seahawks which should make it easier to see when new videos are added. The update has been submitted to the repository now (PR) and should hopefully soon be available for automatic updates in Kodi.
If you can't wait to try it out, you can also download a zip file with the latest release here: https://github.com/Tenzer/plugin.video.nfl-teams/releases/tag/v1.3.3.

Hi
I checked all the teams (all videos folder) and they all do have recent videos, except for the seahawks.
I thought maybe this was a cache issue so also tried to uninstall/install but nothing changed...
I run plugin version 1.3.3 on kodi 17.3 (openelec 8.0.4)

Hmm, I'm using a plugin (script.common.plugin.cache) for caching responses for websites to make the plugin quicker to navigate around in, but it's only set to cache items for 1 hour.
With version 1.3.3 of this plugin, if you navigate to "All videos" for Seahawks and sort by date, what is the most recent date you are shown?

Jan 13 2017

It could seem like my use of the cache plugin is wrong, and it just caches items forever when they are added. I'm sorry about this and I'll dig deeper into it soon!

man that was pretty cool. I pasted "script.common.plugin.cache" into my firefox url bar in order to search for it, maybe I can find a way to reset it, and it crashed firefox to kingdom come....

Awesome!
I've made a fix now, you can update manually via https://github.com/Tenzer/plugin.video.nfl-teams/releases/download/v1.3.4/plugin.video.nfl-teams-1.3.4.zip or wait until it shows up in the Kodi repository in a day or two (I'll submit it in a moment).

That worked - Thanks a lot! now all I need is an o-line.

Glad to hear it works now. I think we all could do with a new O-line (I'm a Cardinals fan).


Proposing article clarity

Proposing a few changes to the article, which are:

Updating the json samples to only include the relevant changes since the article is primarily about number matching; the samples also were enabling additional context, which has it's own article.
Adding a note on what the required Graph permissions are for updating the policy, so that an administrator does not inadvertently over consent to permissions because they are not sure what is needed.
Adding a note regarding the single group, and that organizations who are targeting all users, for something like enabling passwordless, will now be restricting that setting as well, and clarifying that they will want to create an additional group that might be out of the scope of the pilot/test they are running for additional context.
#ATCP

@msfthiker : Thanks for your contribution! The author(s) have been notified to review your proposed change. @mjsantani

#label:"aq-pr-triaged"

Any update on this?

@Justinha, can you review this PR? Thanks.

@msfthiker thanks for the submission and sorry for delay. I added the permissions on my side, and engineering reviewed but declined edits to json examples.
#please-close


Decide flexibility in virtual width of dcache

https://github.com/black-parrot/black-parrot/blob/9b3cea5c453d307f893044be6cd5c09f907cab9e/bp_be/src/v/bp_be_mem/bp_be_mem_top.v#L476
Should just take low 12 bits of vaddr, rather than using these fields, since we are just using this for translation.

Depends on what parameters we want to fix.  I think it's reasonable to have a dcache which only accepts a 12 bit vindex and reconfigures sets, based on cacheline size internally to support this, so this change is probably fine.

There's also the question of allowing synonyms in the I$...

My point is, this code doesn't need to consider the index or the offset, it is only used for VM, which has no relationship to the cache parameters. There is no benefit to writing the code this way. It can just blindly take the low 12 bits. In all other places except this one, it just uses a constant which evaluates to 12.  So defining it this way is just creating an unnecessary mismatch in width for no benefit.

Oh, I misinterpreted and thought we were talking about the D$ packet, not the mmu_cmd.  Agree

So based off a discussion with Andrew W, this is actually incorrect behavior. We need to pass the entire 64-bit effective address in the mem_cmd, so that

we can check that bits 39-64 match bit 38 in the case of translation enabled
passthrough bit 39 in the case of translation disabled

https://groups.google.com/a/groups.riscv.org/d/msgid/isa-dev/CABXpatqk%2BGinxy%3DV_u7K5iYB6N_wYuLeNA5YZSEhPy0BEqU6dQ%40mail.gmail.com?utm_medium=email&utm_source=footer

I think you have attached this comment to the wrong issue... this comment is saying that the page offset field for VM should be populated just by taking the low 12 bits instead of this expression.
M

No, this is the right issue. The mmu_cmd struct needs to change to be 64 bit address, not split into page offset and vtag as the issue title says

fixed by #543


Move content into separate files

The first idea is to have the following content structure:
content/page/$single_pages.md
content/elements/service/$serviceA.md
content/elements/contact.md
Services and other elements could be sorted by weight first and by date second.
Each element or item within a frontpage element has its own file. Global settings like disabling elements would still live in config.toml, but usual default would be, if a file is available for an element it is considered enabled and needs to optionally be disabled in config.toml.
Furthermore the email and contact form provider could be considered global settings and be kept in config.toml.
As this will break compatibility a major version change should occur.

Wouldn't it be easier to move the services, events in the about section as well as the team member descriptions in data files? This way we can sort them by date and weight too. And it trivial to check if a data file for a certain category is present or not.

Furthermore the email and contact form provider could be considered global settings and be kept in config.toml.

I agree.
To flatten the config file even more we could move the definition of strings as well by using the i18n feature of Hugo. Simultaneously we could start to add full support for i18n.

As this will break compatibility a major version change should occur.

I should start to tag future versions of this theme.

I would define content for the services etc. more as content than as data. Therefore I would use content files. Especially as single pages are also located there.
i18n support could first be done via these new separate files and within a second iteration all remaining strings should be extracted into a config or content within these files. So first separate and then move the remaining strings.
At least that's how I understood i18n support. It's basically just another content file with a postfix such as _en.md or _de_DE.md for example. So all strings (config and content) defined in there are already translatable.
Probably the last feature on the non breaking branch would be single page. Afterwards I would prefer a breaking change as compatibility will become hard. Should we just use the dev branch then?

Afterwards I would prefer a breaking change as compatibility will become hard. Should we just use the dev branch then?

Yes. master should only contain backwardscompatible and stable commits.

So with hugo 0.18 nodes will be gone and all elements will be pages. I am still looking through the code to find out how to make the changes we want work with hugo 0.18.
So basically we have a good breaking point.

Seems like its coming along nicely. Quite a huge rewrite. So it might take me a bit to finish this up (not the main focus unfortunately).
Currently all elements on the front page are located within a special section "index".
Each element is its own file and handles their config within the front matter.
For some elements data files are used. As example: team, services, about/timeline.
I still have to add sorting and finish the migration to this new structure.
Maybe a first iteration is working in the coming week.

Regarding Hugo v0.18: a new release in the near future is not planned. Hence I think we could use v0.17 as breakpoint instead.

I still have to add sorting and finish the migration to this new structure.
Maybe a first iteration is working in the coming week.

Your ideas for the revisions are good.

It seems currently I am still using only 0.17 features. I am still looking into the actual differences of the specific change and asked the dev to jump in.
Still have a small unresolved issue with the timeline and modBool.
Wanted to do something like:
{{ range sort $i, $e := $.Site.Data.timeline }}
  <li {{ if (not (modBool $i 2)) }}class="timeline-inverted" {{ end }}>

But the index doesn't work there as one would image due to $i not being an integer, but a string.
The content of $.Site.Data.timeline is something like:
map[beginnings:map[description:Lorem ipsum dolor sit amet, consectetur adipisicing elit. Sunt ut voluptatum eius sapiente, totam reiciendis temporibus qui quibusdam, recusandae sit vero unde, sed, incidunt et ea quo dolore laudantium consectetur! title:Our Humble Beginnings weight:10 img:1.jpg date:2009-2011]]
How would one get the index of one specific event?

The latest version of Hugo was a template function called int that allows you to cast $i to an integer.

Still wouldn't work as $i would be "beginnings" in this case. I am looking into a counter within the range loop. But couldn't yet figure out how this can be done without making it complex.

Got it working:
{{ $.Scratch.Set "counter" 0 }}
{{ range sort $.Site.Data.timeline }}
  {{ $i := $.Scratch.Get "counter" }}
  <li {{ if (not (modBool $i 2)) }}class="timeline-inverted" {{ end }}>
  {{ $.Scratch.Add "counter" 1 }}
{{ end }}

As hugo-agency-theme is mostly in maintainance mode and no new features will be added.
We created Syna as a more flexible iteration of this theme.
Syna is uses separate content files to create a website. Each fragment making up a single site is also split into multiple files within the same directory. For more information take a look at the documentation.


Update the Instrumenter doc

Updates the instrumenter doc, initializing it.

qué

The existing docs suggest setting Linguist.instrument to the Instrumenter class: Linguist.instrumenter = CustomInstrumenter.
That's not going to work as the instrument method calls instrumenter.instrument(*args, &bk), which is an instance method.
I think that doc embedded in the comments may be confusing as it doesn't work as stated. That's why I created this small PR.

Ah, veo!
/cc @pchaigno @kivikakk

Practising languages on a code collaboration tool, we are living in the future ✨ ✨
PS: Sounds more natural if you say "entiendo" instead of "veo" 😃

I pretend to contribute to this repo, but I'm really using the name Linguist as a rabid excuse to shit-talk in as many world languages as possible.


Does this work with NSwag?

Hi there! So I feel rather silly right now... 😁 I just spent a couple hours teaching myself the new Source Generators feature in order to basically build the same thing you did:
https://github.com/LarsKemmann/JsonPolymorph
Yay for duplicating effort because search engines didn't show me your repository. 🙄 It wasn't until I went to install my newly published NuGet package in Visual Studio that I saw your project show up.
So, I have an ASP.NET Core Web API and I'm currently using NSwag (which assumes Newtonsoft.Json) to generate an OpenAPI v3 schema as well as client-side TypeScript code. The core objective I have is to enable that scenario.
Is there a way to accomplish what I'm trying to do using your library? I'm (pleasantly) surprised that you were able to get polymorphic deserialization to work using System.Text.Json - kudos! Now I just need to know if I can generate a compatible OpenAPI v3 schema using that approach.

Hi @LarsKemmann
I've done some NSwag stuff in the past with https://github.com/wivuu/nswag-liquid-slim to generate smaller templates
I haven't done anything today to specifically support NSwag, what did you have in mind? Just newtonsoft Jason attributes? I'm not sure what we can do to fully support NSwag without surgery to NSwag itself.
Anyway, ideas and PRs are very welcome if you want to collaborate

Sorry I haven't responded sooner, I'm still trying to think through the right approach for my use case. I do have a somewhat-related question: have you been able to use this library successfully with nested record types?

So this is interesting... your library handles nested polymorphic record types without any issues, while mine is unable to do that. Did you have to do anything special to enable nested polymorphic serialization?
Here is the model I'm using for my test:
enum AgeType
{
    ExactAge,
    AgeInYears
}
abstract partial record Age([JsonDiscriminator] AgeType Type);
sealed record ExactAge(DateTime DateOfBirth) : Age(AgeType.ExactAge);
sealed record AgeInYears(int Years, DateTime AsOf) : Age(AgeType.AgeInYears);

enum AnimalType
{
    Insect,
    Mammal,
    Reptile,
    //Bird
}

abstract partial record Animal([JsonDiscriminator] AnimalType Type, string Name, Age Age);
sealed record Insect(Age Age, int NumLegs = 6, int NumEyes = 4) : Animal(AnimalType.Insect, "Insectoid", Age);
sealed record Mammal(Age Age, int NumNipples = 2) : Animal(AnimalType.Mammal, "Mammalian", Age);
sealed record Reptile(Age Age, bool ColdBlooded = true) : Animal(AnimalType.Reptile, "Reptilian", Age);

Nope.. the way it's implemented nesting should have no trouble; the inner content of a record would be deserialized the same way as the outer content, using the json converter attribute

Well, I am so thankful that I now am able to round-trip nested polymorphic types with your library. 🙂 However, the enum discriminator requires a fair amount of ceremony (see https://github.com/CareTogether/CareTogetherCMS/commit/8c2ce17a99487a72a294bf7ee1c17a96e2ca5367 -- it was painful 😂). I haven't looked too closely at the implementation in your library, but I wonder if just using the type names (maybe fully-qualified if necessary) would be sufficient to replace the switch logic? If you look up overloads by type name rather than by enum value, it's the same end result, right? And generating the discriminator property in the serialized JSON based on the runtime type (again, fully qualified if necessary) shouldn't be too difficult, I would think... in theory?
If you have some pointers on how that could be done, I'd like to try putting together a PR at some point to add the declarative/convention-based approach into your library as an alternative supported pattern. (I first have to see if what you've suggested for NSwag will work in my use case; that's my next challenge.)
Thanks for listening -- and for the excellent work you've shared here! I really appreciate it. 🙂

I haven't done anything today to specifically support NSwag, what did you have in mind? Just newtonsoft Jason attributes? I'm not sure what we can do to fully support NSwag without surgery to NSwag itself.

With the Newtonsoft-based approach I took in my library, Newtonsoft's JsonHierarchyConverter integrates with NSwag so the generated OpenAPI JSON correctly reflects the polymorphism (oneOf directives). With this library, on the other hand, neither NSwag nor Swashbuckle are (as far as I can tell) able to detect the polymorphism and thus the generated OpenAPI JSON only ever includes the base type. I was planning to use TypeScript code generation to build a client SDK as a core part of the developer experience for my solution, but at this point it looks like System.Text.Json won't support polymorphism until .NET 7 so I'll have to go the manual route until then. Unless you have any ideas for annotating the type hierarchies in a way that NSwag or Swashbuckle will pick up?

@LarsKemmann It shouldnt be hard to generate any additional attributes you want to add, assuming it can be reasoned at compile-time. Perhaps a Wivuu.JsonPolymorphism.NSwag would be in order?
Unfortunately outside of bug-fixes I won't have a lot of time to devote to this library for the next couple months; it's currently serving its purpose for my needs in production. I'd be happy to accept collaboration though.
Can you give an example of how inferring by name of type would work (without enums)? I wanted to make the discriminator an actual property, rather than a hidden/magic property, so it needed a type, and an enum fit best.
Are you thinking:
record Insect();
record Grasshopper: Insect();
record Butterfly: Insect();

Where some automatic property would be serialized for these types?

Yes, exactly, that was the approach I took in my library, with a default property name of discriminator (which could in theory be overridden easily via an attribute constructor argument). I just apply a [JsonHierarchyBase] to the Insect record and the source generator does the rest.
And by the way, I just came back to post that when I said my library couldn't handle nested polymorphic types, I had actually just forgotten to add Microsoft.AspNetCore.Mvc.NewtonsoftJson to my web API project. 🤦♂ So my library actually serves my needs for the time being, as well. 😂 However, I'm very interested in moving away from Newtonsoft in the future to shed some weight from the project, so I will probably look at this again around the .NET 7 preview timeframe!

For my usecase, I wanted to be able to search a database by the 'kind', so for example in Entity Framework (for Cosmos) or Cosmos SDK itself, you would do something like db.Insects.Where(i => i.Kind == InsectType.Grasshopper)


Drop stop and require explicit next?

Pro required next:

consistent with page.js, koa, express, connect, and pretty much every middleware running system I've seen.
obvious to maintainers if a middleware does stuff before, after, or both before and after the following functions.
hard to accidentally move on (or accidentally wait) with explicit next. use((ctx) => { doAsync() }) vs use((ctx) => doAsync())
only one way to move on (instead of calling next and returning).
less arguments to middleware functions

Pro stop:

not doing anything is a weird way to terminate the sequence. arguable
there should be fewer terminating functions than middleware, so stop is less overall noise.
if not waiting for middleware to resolve, how do you do async work in bubble phase (after await next()) before moving up the stack?

@aaronshaf any thoughts?

Managing the flow ultimately won this argument, the 3rd point in favor of stop.
While there are some potential footguns in automatically moving on to the next middleware, a dev that does not properly understand promises or how to manage async code, can almost as easily call next at a poor time. Foolproofing isn't really a goal.
It's pretty straightforward that a middleware holds up the flow downstream until it completes or calls next, and then holds up the flow back upstream until it completes or calls resolve.


python3Packages.types-setuptools: 57.4.4 -> 57.4.5

Motivation for this change
Update to latest upstream release 57.4.5
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build python38Packages.types-setuptools python39Packages.types-setuptools
@ofborg build python39Packages.cyclonedx-python-lib checkov


Is it a release or pr notification?

The readme says it sends notifications when "a pull request event occurs."
But the name of the application is "GitHub Release Notification".
I'm looking for an easy way to get notifications on new releases so I'm a little confused (I don't do new releases on pull requests fwiw).

@eburnette , thank you for reaching out. The current action is designed to send notifications for pull request events only (opened, synchronized, closed).
Before creating a new release, you likely create a pull request targeting your main branch. At Thunkable, our release branches are prefixed with release/. We want notifications when:
A new release branch is created, listing the commits.
A new commit is added to the release branch (e.g., for fixing a regression found by QA).
The release branch is merged into the main branch.
Here's an example configuration:
on:
  pull_request:
    types: [opened, synchronize, closed]

jobs:
  notify:
    if: startsWith(github.event.pull_request.head.ref, 'release/')
    runs-on: ubuntu-latest
    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Run Slack notification action
        uses<EMAIL_ADDRESS>        with:
          slack-token: ${{ secrets.SLACK_BOT_TOKEN }}
          github-token: ${{ secrets.GITHUB_TOKEN }}
          slack-channel: 'SLACK_CHANNEL_ID'

Please describe your current workflow, and we can explore adapting the action for release events if needed.

I create a github release every time there is a commit to the main branch so I'd like a slack notification that points people to the release page where they can download the artifacts.


APIPlugin support sort parameter on models with @key

Is your feature request related to a problem? Please describe.
When using @key directive on a model to create a provisioned API with the sort parameter.
type Todo @model
@key(name:"byA",fields:["field1","field2"],queryField:"byField1") {
  id: ID!
  field1: String!
  field2: Float!
}

Describe the solution you'd like
Allow a way to pass in parameters at the GraphQLRequest builders
Amplify.API.query(.paginatedList(Todo.self, limit: 100, sort: SortInput.ascending)

Describe alternatives you've considered
Following https://docs.amplify.aws/lib/graphqlapi/advanced-workflows/q/platform/ios to creating my own custom GraphQLRequest
extension GraphQLRequest {
    static func listTodos(nextToken: String? = nil) -> GraphQLRequest<ListTodo> {
        let operationName = "listTodos"
        let document = """
        query listTodos($limit: Int, $sort: SortInput, $nextToken: String) {
          \(operationName)(limit: $limit, sort: $sort, nextToken: $nextToken) {
            items {
              id
              field1
              field2
            }
          }
        }
        """
        var variables = ["limit": 100, "sort": "asc"]
        if let nextToken = nextToken {
          variables.update(nextToken, forKey: "nextToken")
        }
        return GraphQLRequest<ListTodo>(document: document,
                                    variables: variables,
                                    responseType: ListTodo.self,
                                    decodePath: operationName)
    }
}

struct ListTodo {
   var items: [Todo]
   var nextToken: String?
}

or use DataStore's supoprt for querying with a sort and page size: https://docs.amplify.aws/lib/datastore/data-access/q/platform/ios#sort
Additional context
Add any other context or screenshots about the feature request here.

I would like this as well

Since V2 transformer was released, the original feature request should be refactored to use @primaryKey and @index instead of @key. This issue should still be open since we do not provide the sort parameter on the GraphQLRequest builders


NormalizedAc.concreteElements: use HashMap

Part of #2508

Review checklist
The author performs the actions on the checklist. The reviewer evaluates the work and checks the boxes as they are completed.

[ ] Summary. Write a summary of the changes. Explain what you did to fix the issue, and why you did it. Present the changes in a logical order. Instead of writing a summary in the pull request, you may push a clean Git history.
[ ] Documentation. Write documentation for new functions. Update documentation for functions that changed, or complete documentation where it is missing.
[ ] Tests. Write unit tests for every change. Write the unit tests that were missing before the changes. Include any examples from the reported issue as integration tests.
[ ] Clean up. The changes are already clean. Clean up anything near the changes that you noticed while working. This does not mean only spatially near the changes, but logically near: any code that interacts with the changes!

Test SET.set2list is set2list:
Except:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-940")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-876"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))
Actual:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-876")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-940"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))

I noticed that some of the property tests were actually failing because the term contained symbolic elements which were reordered. Turns out I had modified part of Kore.Builtin.AssociativeCommutative to use HashMap instead of Map, and we reuse the same functions for the symbolic parts and the concrete parts. Fixing this meant switching back to using Map throughout that module, and at the end converting the concrete Maps to HashMaps.
Other issues are related to our builtin evaluation and tests: we use Map and Set there, so we end up with two representations which differ by the ordering of the elements.
Would a good solution be to switch everything related to maps and sets to use HashMap and HashSet instead? I think that mixing the regular and hashed versions is pretty confusing and it's probably not that ideal in terms of performance, but I might be wrong or overlooking something.
Sort of related: do we still want to keep the symbolic elements and the opaque elements in lists?

We decided to use the hashed versions instead everywhere in the builtin code.

Integration test failure:
module VERIFICATION
  imports PATH

endmodule

module ONE-PATH-B-SPEC
  imports VERIFICATION
  imports PATH

  // This should be provable as an one-path claim, but should not be provable as an
  //all-path claim.
  claim <k> select => b </k>
       <state> SetItem(b) SetItem(c) </state>
    [one-path]

endmodule

with semantics:
module PATH
  import BOOL
  import INT
  import SET
  syntax S ::= "a" | "b" | "c"
  syntax Cmd ::= "select"

  configuration <k> .K </k> <state> .Set </state>

  rule <k> select => X ...</k> <state>... SetItem(X:S) ...</state>
endmodule

Expected result is \\top, but with these changes it's:
<generatedTop>
  <k>
    c ~> .
  </k>
  <state>
    SetItem ( b )
    SetItem ( c )
  </state>
</generatedTop>

Set.test_toList runs which consistently fail:

Initial pattern:
/* Fl Fn D Sfa Cl */
/* InternalSet: */ concatSet{}(
    /* concrete element: */ elementSet{}(\dv{Int{}}("-744")),
    /* concrete element: */ elementSet{}(\dv{Int{}}("-680"))
)
Expected:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-680")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-744"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))
Actual:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-744")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-680"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))

-------------------------------------------------------
Initial pattern:
/* Fl Fn D Sfa Cl */
/* InternalSet: */ concatSet{}(
    /* concrete element: */ elementSet{}(\dv{Int{}}("-1000")),
    /* concrete element: */ elementSet{}(\dv{Int{}}("-936"))
)
Expected:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-936")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-1000"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))
Actual:
\and{List{}}(
    /* term: */
    /* Fl Fn D Sfa Cl */
    /* InternalList: */ concatList{}(
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-1000")),
        elementList{}(/* Fl Fn D Sfa Cl */ \dv{Int{}}("-936"))
    ),
\and{List{}}(
    /* predicate: */
    /* D Sfa */ \top{List{}}(),
    /* substitution: */
    \top{List{}}()
))


[admin] Publish

Docs Build status updates of commit 4b3a0b0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/cross-reference-flow-1.PNG
:white_check_mark:Succeeded
View

docs/images/cross-reference-flow-2.PNG
:white_check_mark:Succeeded
View

docs/images/cross-reference-flow-3.PNG
:white_check_mark:Succeeded
View

docs/resources/samples/event-data.xlsx
:white_check_mark:Succeeded
View

docs/resources/samples/event-transactions.xlsx
:white_check_mark:Succeeded

docs/resources/samples/events.xlsx
:white_check_mark:Succeeded

docs/resources/samples/excel-cross-reference.md
:white_check_mark:Succeeded
View

docs/resources/samples/samples-overview.md
:white_check_mark:Succeeded
View

docs/resources/samples/speaker-registrations.xlsx
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

licensing-information.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Throttle framerate in Unity wrapper

Hi,
I am trying to use multiple Realsense D435 cameras in Unity to display their pointclouds.
When I use 4 or more cameras , Unity crashes.
So I think throttling the framerate might help while using 4 or more cameras.
Is there a way that the camera framerate can be throttled with the Unity wrapper of the Realsense SDK ?

You can definitely reduce FPS or resolution. I'm not sure how to do this in Unity, @ogoshen @matkatz, but search for EnableStream call in the wrapper.

Any other info or crash logs you can share?
Could be a memory issue, so reducing resolution rather than fps might help...

Hi @akashcastelino,
Any update? Do you have a try per @ogoshen suggestion and based on the latest librealsense?

Is the issue clarified? I will close this if no further question.


WDS: svc-addressed waypoint capture

Presently WDS allows only for workloads to have a waypoint assigned. We need to extend WDS to allow for adding waypoint to a service to prepare for further implementation of Ambient - Capture for Services and Workloads
Istio side of https://github.com/istio/ztunnel/issues/816

Closed by this merged PR: https://github.com/istio/istio/pull/49501


[BUG] Milling Patterns are not drawn correctly

should be based off the image data, not metadata which might be wrong
https://github.com/DeMarcoLab/fibsem/tree/v0.2-dev-fix-napari-patterns

image.data.shape order was swapped
annulus pattern not working


fix(webgl): unbind fbo after configure

Sometime leaving a fbo activated after creation could lead to surprising behavior (e.g. regular draws show nothing), thought that would be a better to close it here.

Agreed! :)


[bug] need to handle refresh the balance when any transaction is completed

Is there an existing issue for this?

[x] I have searched the existing issues

RainbowKit Version
0.8.0
wagmi Version
0.11.4
Current Behavior
i have added ConnectButton in Navbar using react app, navbar render only once when app is started,
what happen whenever  i'm doing any transaction using MetaMask balance is not updating inside ConnectButton component
Expected Behavior
you have to re-render that component whenever any changes happen in MetaMask wallet
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

I could work on that, any tips where to start?

You need re-render the connect button whenever any transaction happen;
in may case ConnectButton is Child component

Opened #1415 to implement this behavior with Wagmi's balance polling behavior


[BUG] VPC NatGateway not working

Kube-OVN Version
v1.12.19
Kubernetes Version
v1.29.6
Operation-system/Kernel Version
"Ubuntu 22.04.4 LTS"
5.15.0-116-generic
Description
Similar as #4241 I'm unable to use VPC NAT GW to have pods in a VPC reach internet.  Below you can find my custom configuration
Steps To Reproduce
K8s vanilla cluster, with 3 API nodes + 2 Worker Nodes + 1 Worker node for NATGW.
KubeOVN is installed with Cilium in chain mode.
Below configuration files:
---
apiVersion: kubeovn.io/v1
kind: Vpc
metadata:
  name: alpha-vpc
spec:
  namespaces:
    - alpha
  staticRoutes:
    - cidr: <IP_ADDRESS>/0
      nextHopIP: <IP_ADDRESS>
      policy: policyDst
---
apiVersion: kubeovn.io/v1
kind: Subnet
metadata:
  name: alpha-default-subnet
spec:
  vpc: alpha-vpc
  cidrBlock: <IP_ADDRESS>/16
  protocol: IPv4
  natOutgoing: true
  namespaces:
    - alpha
---
apiVersion: kubeovn.io/v1
kind: Subnet
metadata:
  name: alpha-vpc-external-network
spec:
  protocol: IPv4
  provider: alpha-vpc-external-network.kube-system
  cidrBlock: <IP_ADDRESS>/24
  gateway: <IP_ADDRESS>
---
apiVersion: "k8s.cni.cncf.io/v1"
kind: NetworkAttachmentDefinition
metadata:
  name: alpha-vpc-external-network
  namespace: kube-system
spec:
  config: '{
      "cniVersion": "0.3.0",
      "type": "macvlan",
      "master": "ens19",
      "mode": "bridge",
      "ipam": {
        "type": "kube-ovn",
        "server_socket": "/run/openvswitch/kube-ovn-daemon.sock",
        "provider": "alpha-vpc-external-network.kube-system"
      }
    }'
---
kind: VpcNatGateway
apiVersion: kubeovn.io/v1
metadata:
  name: alpha-vpc-nat-gateway
spec:
  vpc: alpha-vpc
  subnet: alpha-default-subnet
  lanIp: <IP_ADDRESS>
  selector:
  - "node-role.kubernetes.io/vpc-gw: true"
  tolerations:
    - key: "elmec.com/vpc-gw"
      operator: "Exists"
      effect: "NoExecute"
  externalSubnets:
    - alpha-vpc-external-network
---
kind: IptablesEIP
apiVersion: kubeovn.io/v1
metadata:
  name: alpha-vpc-eip
spec:
  natGwDp: alpha-vpc-nat-gateway
  externalSubnet: alpha-vpc-external-network
---
kind: IptablesSnatRule
apiVersion: kubeovn.io/v1
metadata:
  name: alpha-vpc-snat
spec:
  eip: alpha-vpc-eip
  internalCIDR: <IP_ADDRESS>/16

ens19 is the nic on the gw dedicated node with <IP_ADDRESS>/24 subnet attached.
Current Behavior
No ping to <IP_ADDRESS> in a pod into VPC:
root@dnsutils:/# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
^C
--- <IP_ADDRESS> ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2046ms

Ping works in vpc-nat-gw:
kubectl exec -itn kube-system vpc-nat-gw-alpha-vpc-nat-gateway-0 -- sh
Defaulted container "vpc-nat-gw" out of: vpc-nat-gw, vpc-nat-gw-init (init)
/kube-ovn # ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=58 time=2.68 ms
64 bytes from <IP_ADDRESS>: icmp_seq=2 ttl=58 time=2.84 ms
^C
--- <IP_ADDRESS> ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 2.684/2.760/2.836/0.076 ms

Expected Behavior
Ping and other nw commands should work

The issue seems correlated to Cilium, I've opened an issue over there - https://github.com/cilium/cilium/issues/33889; Any advice is accepted.

lost the route?
please show the route in vpc pod?

Hi, below the requested info:
# kubectl ko nbctl lr-route-list alpha-vpc
IPv4 Routes
Route Table <main>:
                <IP_ADDRESS>/0            <IP_ADDRESS> dst-ip
# kubectl exec -itn alpha dnsutils -- bash
root@dnsutils:/# ip r
default via <IP_ADDRESS> dev eth0
<IP_ADDRESS>/16 dev eth0  proto kernel  scope link  src <IP_ADDRESS>

I'm pretty sure about the issue with Cilium, since in Hubble I see dropped packages from the NAT-GW to the Source POD with the reason "Invalid source ip".

Here are the Hubble screenshot if you are curious.

Thanks for your report, but i still not get the details about why <IP_ADDRESS> is invalid.

Cilium has a built-in feature that drop packages if malformed, Cilium furthermore create internal objects called endpoint to track pod identities. The eBPF datapath powered by Cilium see that an packet created by an identity - the VPC NatGW - is forged with a source-ip different that the pod's - since it is acting as SNAT that's normal - and therefore drop the packet.  Example:
The VPC Nat GW endpoint is, take note on the identity number 11734:
NAMESPACE     NAME                                 SECURITY IDENTITY   ENDPOINT STATE   IPV4             IPV6
kube-system   vpc-nat-gw-alpha-vpc-nat-gateway-0   11734               ready            <IP_ADDRESS>   fe80::85d:6eff:fe23:654a

With hubble I'm able to trace the datapath flow:
Jul 19 07:54:15.494: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)
Jul 19 07:54:16.519: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)
Jul 19 07:54:17.543: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)
Jul 19 07:54:18.567: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)
Jul 19 07:54:19.591: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)
Jul 19 07:54:20.615: <IP_ADDRESS> (ID:11734) <> alpha/dnsutils (ID:33611) Invalid source ip DROPPED (ICMPv4 EchoReply)

As you can see, before disabling Cilium's SourceIPVerification, the packets coming from ID 11734 are dropped since the source IP masqueraded as <IP_ADDRESS> is not equal to the Pod IP. After disabling the SourceIPVerification everything works:
Jul 19 09:00:41.075: alpha/dnsutils (ID:33611) -> <IP_ADDRESS> (world) to-stack FORWARDED (ICMPv4 EchoRequest)
Jul 19 09:00:41.076: alpha/dnsutils (ID:33611) -> <IP_ADDRESS> (ID:11734) to-endpoint FORWARDED (ICMPv4 EchoRequest)
Jul 19 09:00:42.221: alpha/dnsutils (ID:33611) <- <IP_ADDRESS> (ID:11734) to-stack FORWARDED (ICMPv4 EchoReply)
Jul 19 09:00:42.222: alpha/dnsutils (ID:33611) <- <IP_ADDRESS> (world) to-endpoint FORWARDED (ICMPv4 EchoReply)

how about letting cilium ignore gw type pod ?

I don't know if that would be possibile, Cilium is already configured to use another CIDR

Hi, I'm gonna close this issue since we found a workaround. Thanks for the support.

@bobz965 I think we can agree this is worthy of being documented. The Cilium chaining doc for Kube-OVN doesn't go over that issue which is apparent pretty quickly once we start provisioning NAT gateways.
Linking the PR opened by @CiraciNicolo https://github.com/cilium/cilium/pull/34056 on the Cilium project.
I think Cilium doing source IP verification is sane. Disabling SIP verification is one way to solve the issue, but it's also removing an important feature of the CNI, especially considering that most people chaining Kube-OVN with Cilium are gonna do that for security/observability.
It would be nice to have that feature on a per pod basis. This is an issue to address on the Cilium side obviously.
It raises one question though, the PodIPs field are populated only with the information from primary interface. Any new interface added with Multus will not have the addresses in that field. So how is Cilium not blocking traffic on those custom NetworkAttachmentDefinitions on the basis that the source IP doesn't match?

@SkalaNetworks could you please post a kube-ovn/doc pr about how to use cilium with nat-gw pod？


Update limits-specifications-teams.md

https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/5748
Added link for more info.

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

I don't think this PR addresses the issue. The issue was that there was conflicting limits in the two articles. Let me investigate.

I've fixed the Live Events article to include the 180-day limit for retaining recordings. The changes will be live this afternoon.


Packaging requests: acxi

Project description
acxi is a command line audio conversion program and audio processing program. It converts and syncs all desired source lossless files to the desired output format, and to a different directory location.
Metadata

homepage URL: https://github.com/smxi/acxi
source URL: https://github.com/smxi/acxi
license: gpl3
platforms:  linux

This should be pretty easy to package, as it only depends on perl:

For backward compatibility, acxi requires only Perl 5.010 (or newer), so it
should run on anything. Several features (copy, make directory, find files) were
moved from *nix commands to Perl native commands in version 3, which should make
acxi fully platform agnostic.

I think it's just a matter of downloading the man page and the script itself, then replacing the shebang in it

Thanks for the fast response.
It does set some paths to encoders/decoders, though:
my $COMMAND_FLAC = '/usr/bin/flac';
my $COMMAND_FFMPEG = '/usr/bin/ffmpeg';
my $COMMAND_FFPROBE = '/usr/bin/ffprobe';
my $COMMAND_LAME = '/usr/bin/lame';
my $COMMAND_OGG = '/usr/bin/oggenc';
my $COMMAND_OPUS = '/usr/bin/opusenc';
# If you are not generating checksums, you do not need this.
my $COMMAND_MD5 = '/usr/bin/md5sum';
# metaflac is required for flac to mp3, to copy over the ID3 tags, or
# for ffp checksum generator.
# If you are not doing either, you don't need this.
my $COMMAND_METAFLAC = '/usr/bin/metaflac';

I guess those paths won't be correct for nixos. These are optional, but you would need at least one for the script to be useful.

Ah yes you're completely right. It was even mentioned just below the section of the readme that I linked, my bad!
Seems like all of these binaries are already packaged:

/usr/bin/flac, /usr/bin/metaflac -> pkgs.flac
/usr/bin/ffmpeg, /usr/bin/ffprobe -> pkgs.ffmpeg
/usr/bin/lame -> pkgs.lame
/usr/bin/oggenc -> pkgs.vorbis-tools
/usr/bin/opusenc -> pkgs.opusTools
/usr/bin/md5sum -> pkgs.coreutils

That's where I got stuck with my previous attempt of creating the package.
The paths have to be substituted with the corresponding location of the derivation in the nix store. So the patch probably needs to be created in the acxi.nix file, because only there I know what e.g. pkgs.flac evaluates to. But I have no idea how to do that...

Could you post what you had in that attempt? Maybe I can help you out


Oauth fix

What this PR does / why we need it:
It fixes an issue with token maps

/cc @dimitar-kostadinov


python311Packages.amaranth: 0.4.dev197+g11d5bb1 -> 0.4.3 (and co)

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Oh and btw, touching a setup-hook for a builder is always expensive, so it should go into staging.

I approve of the setup-hook changes.

I'll cut this nixpkgs-review short.

I sampled a few failures, which all failed on hydra as well. Should be safe

glasgow also builds on master, this should be be good to go

Hash mismatch in amaranth-boards:
error: hash mismatch in fixed-output derivation '/nix/store/7476cjkgniw6k8vyv87grg21mqzy02yc-source.drv':
         specified: sha256-9ZyzD4hOGW2sG24ISNwYBY6NiDe5q0rwDeMdYtzjwDA=
            got:    sha256-dwZCKMJnEY9RjzkcJ9r3TEC7W+Wfi/P7Hjl4/d60/qo=

on it


Styled search input field & btn in dark

@Rajdip019

Good job @vansh-2266
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐

SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .

Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

Good job @vansh-2266
Congrats 🎉, your PR got merged. To be eligible for the swags from ClueLess. Follow this steps.

Star this repository. ⭐
SignIn / SignUp in [ClueLess Website](https://www.clueless.tech/) .
Go to profile section from the top right hand corner.

Comment your profile URL under this comment tagging the person who merged your PR.

That’s it. Follow the leaderboard !
And don’t forget to share your achievement with your friends.

@Rajdip019  Clueless Community Profile ( https://www.clueless.tech/profile/admin/104844940037690894629 )


Fix account integration test

Coverage remained the same at 64.509% when pulling 400000f0a181239e00ff3e8140e523f1e9fae1ff on adrake/ch15899/fix-account-integration-test into ebb6bf89ceb51733c3bbe7b8e41a0ecb8b3e65d2 on master.


BLE using AWS even with AWS disabled

What issue do you have? Please be as thorough and explicit as possible.
I have a govee strip that is BLE only, it shows up in my logs, I copied the ID to the config and enabled BLE control; I even enabled the 'disable AWS' option. However when attempting to control the device, Homebridge log says 'not sending AWS update as not available or enabled' with no indication it attempted to connect to the device view BLE.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X

Which version of Homebridge/HOOBS do you have?
v1.4.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Ubuntu 20.04LTS headless
node v16.13.2
npm v8.1.2

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
homebridge-govee v4.27.0
this is my first attempt as using the plugin

Which Govee devices do you have that are causing issues? Please include product models if applicable.
H6126

Please paste any relevant logs below.

[Govee] Login successful.
[Govee] [Desk Under Lighting] has been added to Homebridge.
[Govee] Bluetooth hardware and packages found successfully.
[Govee] [Desk Under Lighting] initialising with options {"adaptiveLightingShift":0,"bluetooth":"enabled","brightnessStep":1,"logging":"debug"}.
[Govee] [Desk Under Lighting] initialised with id [6D:52:A4:C1:38:17:D9:F7] [H6126].
[Govee] [noble] stateChange: poweredOn.
[Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91 from the UK!
# send a command to the device
[Govee] [Desk Under Lighting] not sending AWS update as not available or enabled.

Hi @Z3r0CooLE
Were there no messages after this in the log about attempting via bluetooth? What exactly were you trying to do?

@bwp91 I included all log lines related to the plugin in the post and will update if new ones come up, but it never even attempts a bluetooth connection.
I'm using a Gigabyte GC-WBAX210 PCIE card as my bluetooth 5.2 LE adapter on Ubuntu 20.04LTS headless.
I've updated the machine to the latest mainline kernel and installed supported drivers.
I've installed a slew of Linux CLI Bluetooth tools and services and I can turn the adapter on/off, scan for devices and trust devices. For some reason every tool I've used fails to connect to devices even though I can scan, find, trust and get info from them so it could be related to this issue.
But in the homebridge logs the plugin claims it found and configured BT hardware and software appropriately.. Just the line saying it won't bother with AWS as I set it to disabled since the strip is BT only. I also don't get anything back form the Govee api when polling devices... not sure if it only shows WiFi enabled devices, but it seems like it should still know I have the device registered to my account.. The Mac address does get returned in HB logs though, and I have that set in the config, so I guess whatever makes the device discoverable must be working.. but yea, no errors in the logs even with debug logs on for the plugin and device.

Hey, I have the exact same Issue, also on Ubuntu - but I’m using an Intel NUC with onboard Bluetooth and it tells me everything is fine and it found everything bluetooth related, api is also connected but I get the same message: „Not sending AWS update …“
I disabled AWS and enabled BLE in the Settings.

@Z3r0CooLE headless - the same version as you, 20.04 LTS

Can anyone install the beta version of the plugin to see if this has improved anything?
Thanks!


Game crash MTR 4.0.0 1.20.1 Forge

Before reporting, I have confirmed that

[x] This bug does not appear to be reported on GitHub Issues before.
[X] This bug still exists in the latest version of the Minecraft Transit Railway mod.
[X] I have tested this in the official version of Minecraft Transit Railway, not a modified, custom, or unofficial build.

Describe the Bug
I installed Minecraft Transit Railway 4.0.0 for Forge (1.20.1). When I opened Minecraft  and Lunched the game. It crashed immediately. So how do i fix it or it will be pached?
Reproduction Steps

Install Minecraft Transit Railway 4.0.0
Drop java file in the mods file
Lunch minecraft

In-game Log and Crash Report
Crash report:
crash-2024-08-06_15.50.51-client.txt
Mod Loader
Forge
Minecraft Version
1.20.1
Minecraft Transit Railway Version
4.0.0
Operating System
Windows 11
List of Mods or Modpack You Were Using
Mods that use in 1.20.1: Minecraft Transit Railway, Nemo's Transit Expansion, architectury, CCTV Craft, traffic craft, Create, thingamajigs
Extra Information
Minecraft  crashes immediately with 4.0.0 version Forge for 1.20.1

Nemo Transit Expansion is for MTR 3 only, some features (Though not all) such as OBJ rendering has been merged into MTR 4