Information is wrong.

"You have used an attribute that is not supported in this version of Visual C++."
... and yet other projects using the same attributes compile just fine with this version of C++!

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

ID: 545cead3-2a93-4888-0e69-7e542ebea155
Version Independent ID: c2b4f61a-b363-3f8d-96ed-3bacd9649b1c
Content: Compiler Error C2337
Content Source: docs/error-messages/compiler-errors-1/compiler-error-c2337.md
Product: visual-cpp
Technology: cpp-diagnostics
GitHub Login: @corob-msft
Microsoft Alias: corob

@JN-LT
The description could use an update. Here's the new description:
"Your code uses an attribute that isn't supported in this context. Or, the attribute isn't available in this version of the compiler. To resolve this issue, remove the unsupported attribute."
This fix should be visible by tomorrow.

You have no idea just how gratifying it is to see an issue addressed! Thank you!!
At my place of work, tickets are opened, and then closed a few days later, but no action is taken, and nothing is ever fixed/resolved.
Jeff Nygren
Software Engineer II | ext. 65440
From: Colin Robertson<EMAIL_ADDRESS>Sent: Thursday, September 19, 2019 6:54 PM
To: MicrosoftDocs/cpp-docs<EMAIL_ADDRESS>Cc: Jeff Nygren<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/cpp-docs] Information is wrong. (#1561)
@JN-LT [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JN-2DLT&d=DwMCaQ&c=sy2pFYeXOTBQJUPqadkFIXq5lzPIgQxhI8DCCAdSjYc&r=poGLmuyW3Dl91ktHt8oLNA7K2yLg53oHsD29YZ0mVDw&m=_ViSbswXlNHAWNYmJPPiH3Jt1uMOH1meIB5iFK0RcGA&s=Wfu36c8z344_XXQU7mTPOpIwicJuqewOvNOcl3ShcJM&e=
The description could use an update. Here's the new description:
"Your code uses an attribute that isn't supported in this context. Or, the attribute isn't available in this version of the compiler. To resolve this issue, remove the unsupported attribute."
This fix should be visible by tomorrow.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_MicrosoftDocs_cpp-2Ddocs_issues_1561-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DANFPIPVG5BLIDHPR5L5PP2DQKQGLJA5CNFSM4IWEMV62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7FERMA-23issuecomment-2D533350576&d=DwMCaQ&c=sy2pFYeXOTBQJUPqadkFIXq5lzPIgQxhI8DCCAdSjYc&r=poGLmuyW3Dl91ktHt8oLNA7K2yLg53oHsD29YZ0mVDw&m=_ViSbswXlNHAWNYmJPPiH3Jt1uMOH1meIB5iFK0RcGA&s=-VGn_27-XTrn0DuiZWJELr7wzxhiiN_mrJxXuSjjd-4&e=, or mute the thread [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ANFPIPT4QXVA4W5CJC573QLQKQGLJANCNFSM4IWEMV6Q&d=DwMCaQ&c=sy2pFYeXOTBQJUPqadkFIXq5lzPIgQxhI8DCCAdSjYc&r=poGLmuyW3Dl91ktHt8oLNA7K2yLg53oHsD29YZ0mVDw&m=_ViSbswXlNHAWNYmJPPiH3Jt1uMOH1meIB5iFK0RcGA&s=QX_J6ARIOCbtlTuGIhFbc8sKM9eVX4jzcfx2y_A-XlY&e=.


Update submodules and dependencies

Also switch from cabal script to mafia.

/cc @tmcgilchrist

/cc @tmcgilchrist

Nice 🚲


object focus (for fields) does not switch to other object, after another object was moved

I just noticed a question for object focus while editing with iD.
For example: the focus is for the moment on a node lets say a cafe object (amenity=cafe element). There is another node which is an amenity=bench. I would like first to correct the position (lat/lon) and second to add more additional attributes for the bench object.
So I will move the bench-node and goto left window side for adding more fields, but then I see the focus is still at the cafe-node object.
Is this an intended behavior? If not. please could you change it in a way that the focus is on bench object after moving the bench-node.
(I think this can be also reproduced for osm way-elements)
.
see here:

When moving independent objects, the selection should be changed to the moved object.

This sounds okay. Other editing apps like Keynote and Sketch work like this and it feels natural.
@bhousel What do you think about doing this for points but not vertices?

This sounds okay. Other editing apps like Keynote and Sketch work like this and it feels natural.
@bhousel What do you think about doing this for points but not vertices?

I agree this seems ok for points..

:-)

@quincylvania
Points are ok. Vertexes of a selected way need to be excluded, but we don't need to exclude vertexes at all.
When dragging a connecting vertex or a tagged vertex without selecting at least one of the parent ways first, the selection should switch to the dragged vertex.

When dragging a connecting vertex or a tagged vertex without selecting at least one of the parent ways first, the selection should switch to the dragged vertex.

I disagree, at least for untagged vertices. Dragging an untagged vertex strongly implies the user just meant to reshape the way, not inspect anything. I'm imaging the selection constantly changing while the user is aligning a road and it driving them nuts.

@quincylvania

I disagree, at least for untagged vertices.

We seem to be talking about different things here.
In general, an untagged vertexes needs a parent way to be selected to become dragable, so it is a vertex of a selected way, and needs to be excluded according to my previous post. Tagged vertices should be handled identically when dragged in the same member.
I do only request to change the focus in the following cases:

Dragging a vertex (e.g. a highway connection) while something unrelated (e.g. a building) is selected.
Dragging a vertex while nothing is selected.

Both cases are limited to connecting or tagged vertexes, because other ones aren't dragable in these cases.
As a general rule, dragging a node should always change something which is or gets selected:
This can either mean reshaping a selected way or repositioning a selected node.


Pub/Sub documentation for polling is wrong.

The PubSubReactiveFactory doesn't have the method createPolledFlux like documented here.
It should be just poll.

Good catch, thank you!

I'm going to fix this right now!


Did you know that Manning has a Tiny PowerShell Projects in meap right now?

https://www.manning.com/books/tiny-powershell-projects

Yup. Completely different take. This is a port of the "Tiny Python Projects" by Ken Youens-Clark.
I also pitched Manning on "Tiny PowerShell Projects" book along Ken's thinking.

Good deal.  Just wanted to make sure you were aware.
On Fri, Jan 6, 2023 at 9:56 AM Doug Finke @.***> wrote:

Yup. Completely different take. This is a port of the "Tiny Python
Projects" by Ken Youens-Clark.
I also pitched Manning on "Tiny PowerShell Projects" book along Ken's
thinking.
—
Reply to this email directly, view it on GitHub
https://github.com/dfinke/Tiny-PowerShell-Projects/issues/9#issuecomment-1373830201,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKI2IXGTKGHVWWGPUAAUDTWRA6EHANCNFSM6AAAAAATTGFW3E
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
https://powershellstation.com

Thanks @MikeShepard.  Hoping to get the author to speak at my Meetup.
I started this project before Manning book started the book.
Always good to have options 🙂


FunctionApp:func azure functionapp publish timeouts with "Updating Application Settings for Remote build..." message

When installing Python functions for a function app, sometimes the tool timeouts after printing 'Updating Application Settings for Remote build... ' message

**Just run the following command from the Azure Functions folder:
func azure functionapp publish dt-shao2-vi-rest-function-app-uspklrodz4yzi --python
**

The call should just create the functions and not timeout. In fact, re running the command without any changes often does that

This happens both in Linux (zsh) and Windows, installing the later version

Adding service team to take a look.

This is related to funccli & not azure-cli please report to the right GitHub project. Thanks!


How to manage packages with PowerShell?

How can I manage chocolatey packages from PowerShell? For example, how to list installed packages in a "PS friendly" way alike:
List-ChocoPackage | Select-Object Name,Version | Format-Table -AutoSize

Or if that's not feasible, how about having the choco binary output some kind of machine-readable-output like JSON?

This repository is deprecated. Please see https://github.com/chocolatey/choco - your question is actually better to ask in Gitter.

Gitter is https://gitter.im/chocolatey/choco


Update serial_scanner.py

Missing the () from print line 41

Thank you for you contribution to the repo and the community


Support a synchronous API

I know about the benefits of having async methods. But, however, there are always situations, that do not allow using the async/await pattern, often outside your control. My case is an encapsulated business domain that raises an event, that should be handled synchronously by UserManager.
I also know there are various techniques to make this happen, however, I spent various days to find a possibility to do so, that does not deadlock in a single cpu environment (cheap azure build agent, cheap azure hosting), not only because it is really hard to reproduce that issue locally. Btw: I ended up with this answer on SO, but to be honest: I am not able to explain, why this is better than TaskFactory.StartNew(func).Unwrap().GetAwaiter().GetResult() . It is proven to work by trial and error, what makes me feel not so comfortable.
Is there a specific reason to force the consumer of ASP.Net Identity Core to the async pattern, except "that's how it should be done today. basta."?

It's this way because at it's core (pun intended) ASP.NET Core is async. "That's how it should be done today. Marc" :)
So we have no plans to write sync wrappers.


Bloom filter

Implemented Bloom Filter Operator and also couple of demos.

Something odd is happening with this merge. The build has gone on since January 17th!


Getting HifiBerry to work!?

Everything looks fine after the installation. Airplay and Bluetooth is getting connected, but there is NO SOUND coming out...
I have a Pi 3 with HifiBerry MiniAmp
I tried the enable-hifiberry.sh, but it says I have no permission. I manually switched dtoverlay to hifiberry-dac in /boot/config.txt but it doesn't work. :(

You need to execute the scripts with "sudo", e.g. sudo ./enable-hifiberry.sh. Could you try this?
I might need to adjust the scripts so they do the "sudo" part by themselves.

May I slightly derail this thread, as I think this will be helpful for others. I'm trying to add equalizer into mix with Hifiberry DAC+, however after hours of googling/reading the ALSA docs I still cannot get the right asound.conf configuration. I can't figure out the correct config to make following source device to rpi-audio-receiver (either via bt or airplay) to hifiberry amp2 via equalizer. Could anyone share their knowledge wether this possible?

What is your current asound.conf? And which equalizer are you using, alsaequal?

What is your current asound.conf? And which equalizer are you using, alsaequal?

My current asound.conf looks like this:
pcm.dmixer {   type dmix   ipc_key 1024   ipc_perm 0666     slave {     pcm "hw:1,0"     period_time 0     period_size 1024     buffer_size 8192     rate 44100   }   bindings {     0 0     1 1   } } ctl.dmixer {   type hw   card 0 } pcm.softvol {   type softvol   slave.pcm "dmixer"   control {     name "Master"     card 0   } } pcm.!default {   type plug   slave.pcm "softvol" }
With this setup I have sound coming out of HifiBerry DAC+. As soon as I add alsaequal either before the softvol or after I have nothing out of the speakers via rpi-audio-receiver, but if I test manually with player specifying the output device I can make it play and equalizer works.

So you "only" need to figure out how to configure the defaults so they work without having to specify the output device. How does your config look like with alsaequal added and how do you call aplay so it works with the equalizer?

So you "only" need to figure out how to configure the defaults so they work without having to specify the output device. How does your config look like with alsaequal added and how do you call aplay so it works with the equalizer?

The asound.conf with eq looks like this:
pcm.dmixer {   type dmix   ipc_key 1024 # any unique value   ipc_perm 0666 # mixing for all users   slave {     pcm "hw:1,0"     channels 2     period_time 0     period_size 1024     rate 44100     buffer_size 16384   }   bindings {     0 1     1 0   } } pcm.softvol {   type softvol   slave.pcm "dmixer"   control {     name "Master"     card 0   } } ctl.equal {   type equal } pcm.plugequal {   type equal   slave.pcm plug:softvol } pcm.equal {   type plug;   slave.pcm plugequal } pcm.!default {   type plug   slave.pcm plugequal }
I'm testing it with speaker-test command and mpg123 player and aplay command: speaker-test -D default -c 2 & mpg123 test.mp3 & aplay test.wav — all three commands successfully play sound, equalizer works, softvol 'Master' volume works, however when I switch to airplay/bluetooth — no sound.

That's strange. I did not test your config yet, but it seems okay. I assume you already restarted the services (shairport-sync, bluealsa)?
I had similar problems with pivumeter, a graphical VU meter using LEDs. It seems that dmixer does not play well with meter plugins, and I could not find any documentation about it, so I gave up. In your case it seems different because aplay actually works, so it seems to me only a small part is missing (i.e. make the services do the same thing aplay does).

That's strange. I did not test your config yet, but it seems okay. I assume you already restarted the services (shairport-sync, bluealsa)?
I had similar problems with pivumeter, a graphical VU meter using LEDs. It seems that dmixer does not play well with meter plugins, and I could not find any documentation about it, so I gave up. In your case it seems different because aplay actually works, so it seems to me only a small part is missing (i.e. make the services do the same thing aplay does).

UPDATE:
Well I've managed to make it work over bluetooth, the thing was that when it plays through bluealsa it uses root as a user (I guess?) therefore alsamixer should be launched from root in order to adjust eq. I'm still digging to airplay config, as It seems it uses different user for playback

Try to use "ipc_key_add_uid false" in your dmixer config. That said, I removed my custom dmixer config, as it should be automagically created.
I use a "Adafruit speaker bonnet" and my working asound.conf (local audio + bluetooth) looks like this:
# Use soft volume control because or card does not have hardware volume control
pcm.!default {
  type plug
  slave.pcm "softvol" # redirect output to softvol (instead of "hw:0,0")
}

# Output to dmixer first. This enables:
# - automatic conversion to a format that the hardware "hw:0,0" can play
# - playing multiple simultaneous streams
pcm.softvol {
  type softvol
  slave {
    pcm "dmix" # redirect the output to dmix (instead of "hw:0,0")
}
  control {
    name "PCM" # override the volume slider to set the softvol volume
    card 0
  }
}


wrs-avp-kmod does not compile on Linux kernel 4.7

When compiling on latest Fedora 24 Cloud image, I got the error
make[1]: Entering directory '/usr/src/kernels/4.7.2-201.fc24.x86_64'
CC [M]  /home/tapio/wrs-avp-kmod-1.2.3/avp_misc.o
CC [M]  /home/tapio/wrs-avp-kmod-1.2.3/avp_net.o
/home/tapio/wrs-avp-kmod-1.2.3/avp_net.c: In function ‘avp_net_tx’:
/home/tapio/wrs-avp-kmod-1.2.3/avp_net.c:357:5: error: ‘struct net_device’ has no member named ‘trans_start’; did you mean ‘mem_start’?
dev->trans_start = jiffies; /* save the timestamp */
 ^~

The fix is explained in Linux kernel commit    4d659fcb20d3d3302b429c889a73a92ff2804b9a: replace the line with
netif_trans_update(dev);

Thanks for the report, will investigate and provide an update.

Hi Tapio;
The latest source tree for 16.10 now includes support for Linux Kernel 4.7 and has been posted here.


Add support of next EC2 API methods: ModifyVolume and DescribeVolumesModifications

Add support of next EC2 API methods: ModifyVolume and DescribeVolumesModifications
Description

Add support of ModifyVolume and DescribeVolumesModifications EC2 API methods.
Fix name of ebs/volumeType extra attribute mapping.

Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[ ] Documentation
[x] Tests
[ ] ICLA (required for bigger changes)

Coverage increased (+0.01%) to 87.283% when pulling 2f8189068f5d23bf04595468b4b7e4d76be5da63 on Scalr:for-upstream/modify_volume into 1a07215991a8c6be7e877d669eca9c007308806f on apache:trunk.

changes look great 👍


Refresh Project View

This is not a bug report but more of question on how to find my way around having just installed Atom for the first time.
I am working on a symfony project which on at the begining generates entity files when you define schema in yml files from the cli. However, I am unable to view the directory and generated files on my project view. I have tried to google, searched here and even tried to find packages that can achieve my requirement for a way to refresh the project tree view with no success.
Can anyone point me to the right direction?

Questions like this are more suited for https://discuss.atom.io and will likely be answered faster if you post there instead.

Thanks and sorry for not following protocol. I'll ask there.
Get Outlook for Android
On Thu, Jun 9, 2016 at 4:51 PM +0300, "Ben3eeE"<EMAIL_ADDRESS>wrote:
Questions like this are more suited for https://discuss.atom.io and will likely be answered faster if you post there instead.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[Bug]: unexpected css transform for color

System Info
System:
    OS: macOS 14.2.1
    CPU: (8) arm64 Apple M3
    Memory: 114.19 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.19.0 - ~/Library/Caches/fnm_multishells/26058_1725135681510/bin/node
    Yarn: 1.22.22 - ~/Library/Caches/fnm_multishells/26058_1725135681510/bin/yarn
    npm: 10.2.3 - ~/Library/Caches/fnm_multishells/26058_1725135681510/bin/npm
    pnpm: 9.7.1 - ~/Library/Caches/fnm_multishells/26058_1725135681510/bin/pnpm
    bun: 1.1.5 - ~/.bun/bin/bun
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 128.0.6613.114
    Safari: 17.2.1

Details
rspack and webpack handle css differently.
see minimal reproduction.
Reproduce link
No response
Reproduce Steps
See readme

It seems be transformed by lightningcss when minimize css. You can try it in playground
If you want to avoid this behavior, you can set the target in LightningCssMinimizerRspackPlugin.
https://rspack.dev/plugins/rspack/lightning-css-minimizer-rspack-plugin#minimizeroptions

fixed in #7811


Builds failing for arm64 (vscode-ripgrep 0.10.0 doesn't have an arm64 build)?

VSCode Version: latest
OS Version: debian stretch

Does this issue occur when all extensions are disabled?: Yes
error /root/build/code/node_modules/vscode-ripgrep: Command failed.
Exit code: 1
Command: node ./lib/postinstall.js
Arguments:
Directory: /root/build/code/node_modules/vscode-ripgrep
Output:
Downloading ripgrep failed: Error: No asset named ripgrep-0.10.0-linux-arm64.zip found
This seems to be new.  Having looked at the repository it's hitting (https://github.com/roblourens/ripgrep/releases), it appears that 0.9.0 did support arm64, but there's no arm64 zip in the releases for 0.10.0, causing the builds to fail for this architecture.
I know arm64 isn't officially supported, but I suspect this is an unintentional omission, so raising here (the ripgrep repo doesn't support the Issues feature or I would raise there).

I missed uploading it, thanks for the reminder!


Fix BucketObjectv2 should only trigger an update on code changes

This fixes the issue by switching to use Pulumi assets instead of the filepath directly. The filepath includes the random cdk.out directory so it will always be different. Assets handle this case.
fixes #73

Nice!


BUG: Scipy >=1.11.1, GCC 8.5.0 and Cython 3.0.5 combination on RHEL8/Centos Stream 8 results in undefined symbol for wrap_PyUFunc_getfperr when collecting tests

Describe your issue.
When running the tests after having scipy compiled on a RHEL8/CentOS Stream 8 system with Cython >= 3, I get an undefined symbol error for wrap_PyUFunc_getfperr and more specifically 202 errors which are all of the type:
____________________________________________________________________________________________ ERROR collecting cluster/tests/test_disjoint_set.py _____________________________________________________________________________________________
ImportError while importing test module '/usr/local/lib64/python3.11/site-packages/scipy/cluster/tests/test_disjoint_set.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
scipy/cluster/__init__.py:27: in <module>
    from . import vq, hierarchy
scipy/cluster/vq.py:72: in <module>
    from scipy.spatial.distance import cdist
scipy/spatial/__init__.py:116: in <module>
    from ._geometric_slerp import geometric_slerp
scipy/spatial/_geometric_slerp.py:9: in <module>
    from scipy.spatial.distance import euclidean
scipy/spatial/distance.py:121: in <module>
    from ..special import rel_entr
scipy/special/__init__.py:772: in <module>
    from . import _ufuncs
_ufuncs.pyx:1: in init scipy.special._ufuncs
    ???
E   ImportError: /usr/local/lib64/python3.11/site-packages/scipy/special/_ufuncs_cxx.cpython-311-x86_64-linux-gnu.so: undefined symbol: wrap_PyUFunc_getfperr

The GCC version is 8.5.0 and I've tested both Python 3.11 and 3.12. It only happens with Cython >= 3, the previous Cython versions pose no problem.
Also higher GCC versions (e.g.  11.4.1 on RHEL9) don't exhibit this behavior with the same parameters.
I've tested the scipy versions from 1.11.1 to 1.11.4 and it's the same for all.
Reproducing Code Example
on a Centos Stream 8 container system:

Dependencies:
$ dnf config-manager --set-enabled powertools
$ dnf install dnf-plugins-core
$ dnf builddep python3.11-scipy
$ dnf remove python3.11-Cython # to remove the older version provided by the distro
$ dnf install python3.11-pip git

Clone the scipy repo and checkout the v.1.11.4 tag
$ git submodule update --init
$ python3.11 -m pip install Cython==3.0.5
$ SCIPY_USE_PYTHRAN=0 python3.11 _setup.py build
$ SCIPY_USE_PYTHRAN=0 python3.11 _setup.py install
$ cd /usr/local/lib64/python3.11/site-packages/
$ python3.11 -m pytest scipy/

Error message
____________________________________________________________________________________________ ERROR collecting cluster/tests/test_disjoint_set.py _____________________________________________________________________________________________
ImportError while importing test module '/usr/local/lib64/python3.11/site-packages/scipy/cluster/tests/test_disjoint_set.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
scipy/cluster/__init__.py:27: in <module>
    from . import vq, hierarchy
scipy/cluster/vq.py:72: in <module>
    from scipy.spatial.distance import cdist
scipy/spatial/__init__.py:116: in <module>
    from ._geometric_slerp import geometric_slerp
scipy/spatial/_geometric_slerp.py:9: in <module>
    from scipy.spatial.distance import euclidean
scipy/spatial/distance.py:121: in <module>
    from ..special import rel_entr
scipy/special/__init__.py:772: in <module>
    from . import _ufuncs
_ufuncs.pyx:1: in init scipy.special._ufuncs
    ???
E   ImportError: /usr/local/lib64/python3.11/site-packages/scipy/special/_ufuncs_cxx.cpython-311-x86_64-linux-gnu.so: undefined symbol: wrap_PyUFunc_getfperr
______________________________________________________________________________________________ ERROR collecting cluster/tests/test_hierarchy.py ______________________________________________________________________________________________
ImportError while importing test module '/usr/local/lib64/python3.11/site-packages/scipy/cluster/tests/test_hierarchy.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
scipy/cluster/__init__.py:27: in <module>
    from . import vq, hierarchy
scipy/cluster/vq.py:72: in <module>
    from scipy.spatial.distance import cdist
scipy/spatial/__init__.py:116: in <module>
    from ._geometric_slerp import geometric_slerp
scipy/spatial/_geometric_slerp.py:9: in <module>
    from scipy.spatial.distance import euclidean
scipy/spatial/distance.py:121: in <module>
    from ..special import rel_entr
scipy/special/__init__.py:772: in <module>
    from . import _ufuncs
_ufuncs.pyx:1: in init scipy.special._ufuncs
    ???
E   ImportError: /usr/local/lib64/python3.11/site-packages/scipy/special/_ufuncs_cxx.cpython-311-x86_64-linux-gnu.so: undefined symbol: wrap_PyUFunc_getfperr
_________________________________________________________________________________________________ ERROR collecting cluster/tests/test_vq.py __________________________________________________________________________________________________
ImportError while importing test module '/usr/local/lib64/python3.11/site-packages/scipy/cluster/tests/test_vq.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib64/python3.11/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
scipy/cluster/__init__.py:27: in <module>
    from . import vq, hierarchy
scipy/cluster/vq.py:72: in <module>
    from scipy.spatial.distance import cdist
scipy/spatial/__init__.py:116: in <module>
    from ._geometric_slerp import geometric_slerp
scipy/spatial/_geometric_slerp.py:9: in <module>
    from scipy.spatial.distance import euclidean
scipy/spatial/distance.py:121: in <module>
    from ..special import rel_entr
scipy/special/__init__.py:772: in <module>
    from . import _ufuncs
_ufuncs.pyx:1: in init scipy.special._ufuncs
    ???
E   ImportError: /usr/local/lib64/python3.11/site-packages/scipy/special/_ufuncs_cxx.cpython-311-x86_64-linux-gnu.so: undefined symbol: wrap_PyUFunc_getfperr

SciPy/NumPy/Python version and system information
1.11.4 1.23.5 sys.version_info(major=3, minor=11, micro=5, releaselevel='final', serial=0)
lapack_armpl_info:
  NOT AVAILABLE
lapack_mkl_info:
  NOT AVAILABLE
openblas_lapack_info:
    libraries = ['openblasp', 'openblasp']
    library_dirs = ['/usr/lib64']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
lapack_opt_info:
    libraries = ['openblasp', 'openblasp']
    library_dirs = ['/usr/lib64']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
blas_armpl_info:
  NOT AVAILABLE
blas_mkl_info:
  NOT AVAILABLE
blis_info:
  NOT AVAILABLE
openblas_info:
    libraries = ['openblasp', 'openblasp']
    library_dirs = ['/usr/lib64']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
blas_opt_info:
    libraries = ['openblasp', 'openblasp']
    library_dirs = ['/usr/lib64']
    language = c
    define_macros = [('HAVE_CBLAS', None)]
Supported SIMD extensions in this NumPy install:
    baseline = SSE,SSE2,SSE3
    found = SSSE3,SSE41,POPCNT,SSE42,AVX,F16C,FMA3,AVX2,AVX512F,AVX512CD,AVX512_SKX,AVX512_CLX,AVX512_CNL,AVX512_ICL
    not found = AVX512_KNL,AVX512_KNM

python3.11 _setup.py build

A few questions here:

Why are you using the old setup.py infrastructure instead of building with meson?
Why do you need to build from source instead of using a pre-built binary (pip install scipy)?
Is this just x86_64 Linux, or something more exotic?

python3.11 _setup.py build

A few questions here:
1. Why are you using the old `setup.py` infrastructure instead of building with `meson`?

While the reproducer I've provided is working through building scipy from the github sources, the actual discovery happened when building scipy as an rpm for the python3.12 stack. I can't use meson since we don't ship it in RHEL. Although just for the sake of investigation, I've tried to work it out a bit and check what happens (by installing meson through pip) but I fell short on the openblas detection mechanism of the meson build system.

2. Why do you need to build from source instead of using a pre-built binary (`pip install scipy`)?

Answered above.

3. Is this just `x86_64` Linux, or something more exotic?

Tested on x86_64, aarch64, s390x and ppc64le, all with the same result, so it's not arch dependent.

I would be focussing here on getting your build to work with the new meson approach, using setup.py is not supported any more. What went wrong with the openblas detection with meson?
meson uses pkg-config or cmake to figure out where openblas lives. So set PKG_CONFIG_PATH to where the openblas.pc file lives and you should be sweet.

I would be focussing here on getting your build to work with the new meson approach, using setup.py is not supported any more. What went wrong with the openblas detection with meson?
meson uses pkg-config or cmake to figure out where openblas lives. So set PKG_CONFIG_PATH to where the openblas.pc file lives and you should be sweet.

That is not possible at least for the rpm's. meson is not shipped through the distro. In order to make it work I'll either have to utilize a lower Cython version or figure out this issue if possible.
The problem with meson and openblas detection is the missing .pc file from the openblass-devel package, which was not a problem with the setup.py build. I guess I can workaround it by creating my own .pc file and configure the env variable but unfortunately I am restricted to using only the setup.py for the rpm's at this time.

Unfortunately setup.py is not something that is going to be supported by the dev team at this point, but we will try to work to get the meson based approach usable for you.

Can you ask the openblass-devel package to ship a .pc file, or a cmake config file? (what are the restrictions for them not adding it)

Further instructions for meson related blas library detection can be found at https://docs.scipy.org/doc/scipy/building/blas_lapack.html.

The 1.11.x minor release does not support Cython 3: https://github.com/scipy/scipy/blob/maintenance/1.11.x/pyproject.toml#L16. We have backported as many changes as possible, but there's a reason there's a <3 constraint there. Cython 3 broke a lot of things, and was released after 1.11.0.
The pragmatic thing to do here seems to be to simply use a newer GCC or an older Cython, since you say both fix the problem.
Re Meson/RHEL/OpenBLAS:

The root cause of this problem is that Fedora (and hence RHEL I assume) has a packager who refuses to ship openblas.pc. The bug is https://bugzilla.redhat.com/show_bug.cgi?id=1574517. If you have some leverage to move that along, that'd be great, because the attitude there is ridiculous. They're knowingly leaving out necessary build config files (the .cmake ones too IIRC).
We'll get around to working around the problem, but not before Meson 1.4.0
I'll also note that if you're building an RPM to be packaged in RHEL (is that the case?), then you should be using FlexiBLAS rather than OpenBLAS I believe. Use -C-Dblas=flexiblas -C-Dlapack=flexiblas for that (see http://scipy.github.io/devdocs/building/blas_lapack.html for more details).

Unfortunately setup.py is not something that is going to be supported by the dev team at this point, but we will try to work to get the meson based approach usable for you.

Unfortunately as mentioned before it's not possible to utilize meson for this usecase. I understand though that the developers would like to move forward to meson and not support the setup.py infrastructure anymore, so if it's not possible to figure this out I'll utilize the lesser Cython version.

* Can you ask the `openblass-devel` package to ship a .pc file, or a cmake config file? (what are the restrictions for them not adding it)

Interestingly enough I found out that RHEL8 actually ships a .pc file as of recently: https://gitlab.com/redhat/centos-stream/rpms/openblas/-/blob/c8s/openblas.spec#L686
But still when I tried out the meson build it didn't detect it.
Nevertheless, as I can't use meson, pondering about this is not going to help me in this case.

Further instructions for meson related blas library detection can be found at https://docs.scipy.org/doc/scipy/building/blas_lapack.html.

The 1.11.x minor release does not support Cython 3: https://github.com/scipy/scipy/blob/maintenance/1.11.x/pyproject.toml#L16. We have backported as many changes as possible, but there's a reason there's a <3 constraint there. Cython 3 broke a lot of things, and was released after 1.11.0.
The pragmatic thing to do here seems to be to simply use a newer GCC or an older Cython, since you say both fix the problem.

I understand, that might be the way to go. If however there could be some pointers provided in order to debug this further, I'd appreciate that.

Re Meson/RHEL/OpenBLAS:
* The root cause of this problem is that Fedora (and hence RHEL I assume) has a packager who refuses to ship `openblas.pc`. The bug is https://bugzilla.redhat.com/show_bug.cgi?id=1574517. If you have some leverage to move that along, that'd be great, because the attitude there is ridiculous. They're knowingly leaving out necessary build config files (the `.cmake` ones too IIRC).

* We'll get around to working around the problem, but not before Meson 1.4.0

* I'll also note that if you're building an RPM to be packaged in RHEL (is that the case?), then you should be using FlexiBLAS rather than OpenBLAS I believe. Use `-C-Dblas=flexiblas -C-Dlapack=flexiblas` for that (see http://scipy.github.io/devdocs/building/blas_lapack.html for more details).

RHEL8 doesn't ship FlexiBLAS, just OpenBLAS (in contrast to RHEL9), so that's is not an option unfortunately.
Nevertheless, the issue here is not about the meson build specifically, but if I can figure out the problem with setup.py. If that is not possible I'll utilize Cython < 3 and that should be fine. I get that devels would prefer to iron out the new build system instead of old obsolete infrastructure, so it's ok if we close this issue.

If however there could be some pointers provided in order to debug this further, I'd appreciate that.

I have some recollection about seeing wrap_PyUFunc_getfperr before. I can't remember though if it was fixed in Cython or in SciPy - I suspect in Cython.

If that is not possible I'll utilize Cython < 3 and that should be fine.

That sounds easiest indeed.

so it's ok if we close this issue.

Thanks @stratakis, I'll do that.

That symbol is supposed to be defined in special, https://github.com/search?q=repo%3Ascipy%2Fscipy wrap_PyUFunc_getfperr&type=code

I see the same issue popping up here: https://github.com/conda-forge/scipy-feedstock/pull/244#issuecomment-1683142256 and here: https://github.com/termux-user-repository/tur/issues/546
Possibly related to https://github.com/scipy/scipy/issues/19003


External workflow modules and singularity?

Snakemake version
6.4.1
Describe the bug
Snakedeploy works by creating a new Snakefile, specifying the workflow as a module. It seems as if this leads to the containers being ignored even when using the --use-singularity flag. Also described here: https://github.com/snakemake/snakedeploy/issues/16
Minimal example
mamba create -c bioconda -c conda-forge --name snakemake snakemake snakedeploy
conda activate snakemake
git clone https://github.com/nikostr/dna-seq-deepvariant-glnexus-variant-calling.git
mkdir snakedeploy_test
cd snakedeploy_test
snakedeploy deploy-workflow https://github.com/nikostr/dna-seq-deepvariant-glnexus-variant-calling . --tag v0.3.0
cp -r ../dna-seq-deepvariant-glnexus-variant-calling/.tests .

Running snakemake -j1 --use-conda --conda-frontend mamba --use-singularity works in the cloned but not in the deployed directory.

Closed by PR #1040.


⚠ Panel - Hydeos has degraded performance

In d996ffb, Panel - Hydeos (https://pterodactyl.hydeos.fr) experienced degraded performance:

HTTP code: 200
Response time: 1521 ms

Resolved: Panel - Hydeos performance has improved in 6ce32db after 25 minutes.


iOS add to homescreen > paper wallet screen blocks the progress of new-account

Location
new-account, paper-wallet?
Expected behavior
After the paper wallet screen opens, I want to close it.
Actual behavior
But I cannot close it.
Steps to reproduce the problem
Add Swarmdev.city to homescreen, create account. Get stuck at paper wallet.
Operating system / hardware
iOS, add to homescreen

Addition; Every "popup" window is uncloseable, fi. the etherscan link found in txhistory.


MSAL and Full trust Oauth for First party app

We have an Angular front end connecting to a Web Api project using a bearer token and the Full trust Oauth flavor.
Will MSAL work well for our front end?
Thanks

@jrmcdona What is the full trust Oauth flavor you are referring to? MSAL.js uses the Implicit grant of Oauth. Regarding the web api, is it your application's own backend API or a third party API?

Closing this issue for now. Please re-open if necessary.


rayon-demo doesn't compile with Rust nightly

   Compiling rayon-demo v0.0.0 (file:///home/markus/rayon/rayon-demo)
error[E0482]: lifetime of return value does not outlive the function call
  --> src/tsp/graph.rs:50:49
   |
50 |     pub fn edges<'a>(&'a self, source: Node) -> impl Iterator<Item=Edge> {
   |                                                 ^^^^^^^^^^^^^^^^^^^^^^^^
   |
note: the return value is only valid for the lifetime 'a as defined on the method body at 50:5
  --> src/tsp/graph.rs:50:5
   |
50 | /     pub fn edges<'a>(&'a self, source: Node) -> impl Iterator<Item=Edge> {
51 | |         self.all_nodes()
52 | |             .filter_map(move |target| {
53 | |                 self.edge_weight(source, target)
...  |
61 | |             })
62 | |     }
   | |_____^

error: aborting due to previous error

error: Could not compile `rayon-demo`.

To learn more, run the command again with --verbose.

Thanks for reporting!  #482 should fix this.


Change stage pod cleanup to remove any stale stage pods (no filter on correlation label)

Make stage pod cleanup delete all previous stage pods found in namespaces to be migrated, regardless of correlation label
Remove the Prepare "combo" phase in favor of more explicit individual phases under the Prepare step.
Remove stage pod cleanup from FailedItinerary, we want to leave stage pods around so user can inspect. Stage pod will be auto-cleaned at rollback or next migration when user has decided what to do.

Closes #700

@sseago I addressed your comments in the latest change.

Tried to make it more clear that the new label is specifically for cleanup purposes.

func (t *Task) stagePodCleanupLabel() map[string]string {

Go back to using stage pod correlation labels for non-cleanup tasks
Filter stage pod cleanup queries using namespaces included on migplan

@sseago added support for doing stage pod cleanup in the presence of src:dest namespace mapping.

Wrote up #740 to describe an issue I saw while working on this PR. Our registry pod queries need to be more specific.


Access chairs, privacy officer and data manager

If an application is sent for revision, we often advise the researcher to contact the privacy officer/data manager for advice. These advisory members of the FEtC-H, can, at that point, not be linked to the application anymore (status: revisie noodzakelijk). Is there a way by which they can access all applications without having the secretary role? That would be the easiest solution (from the secretary's point of view), since researchers may also seek advice from p.o. and/or d.m. on their own initiative.

Actually, this kind of access also applies to both chairs of the FEtC-H.
It should be clear to any of these people which applications they need to assess.

Okay, seems like a good idea. Access controls are quite tight as they stand.
Currently, both chairs already have access to both chambers. But they can only see applications that they have been assigned to.
In the future, the desired situation is as follows:

Select users such as Chairs, PO, and DM should be able to view ALL applications of both chambers.

Make a group that has permissions in combination with a room. Should be able to see everything, yet not edit things. 'kijkrechten'


Problem with the MP3-TF-16P sound

When the saber get power, the boot sound is heard, but some times it gets cut (and no more sound is heard - the player disconnects), and for sure when I start the saber (Main Button pressed), the leds get on, but the sound start and gets cut in the middle, the hum, never or almost never gets to be reproduced. Doing a DEBUG in the sound library, when that happens, I can see an error "DFPlayer: Unhandled sended message: " and some data, so I'm sure the Arduino Nano is sending the instruction, but the MP3-TF... gets disconnected for some reason. Maybe is sound files issues, or am preparing the SD card wrong, but I followed the instructions. Any help, please. Thank you in advanced and this is great work.

An using the sounds provided in this project and also used the Jakesoft converter, and added 120 seconds more to the original files, I had the same problem for the original files. I've tried both ways.

After some research (am not electronic, am developer). I found that the 5Volts provided by the Arduino Nano (connected to the PC, by USB) was not enough to start the lights and the sound at the same time, that's why the issue described above was happening. Solution use a po0wer source with the next voltages 7.4-8.2, supply to the LED strip no more than 5 volts, but the Arduino can work with all that power, using the VIN port (7-10V). Hope this helps somebody with the same issue. Cheers.

Hi Amaury!
You want to power the Arduino via from a 3.7V battery via the 5V pin, and
the sound and lights need to be powered directly from the battery, not
through arduino/USB power.  You do not need to run on a double cell set up,
you also SHOULD NOT do that.
This is a common issue, and it is a user installation issue, not a design
issue.
I hope that helps!
Jason "Kuma" Brinkerhoff
*Mad Science Workshoppe, *proprietor
http://jbkuma.com/workshoppe
On Sun, Jul 31, 2022 at 5:21 PM Amaury Chong Rodríguez <
@.***> wrote:

Closed #109 https://github.com/Protonerd/FX-SaberOS/issues/109 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/Protonerd/FX-SaberOS/issues/109#event-7096846440, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3UEMCIGN24TROB2CBUGY3VW3U6LANCNFSM55B2OK4Q
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you for answer and for the info!!!!. I'll do it that way.


IdxTone Refresh

The following repos should be checked and/or refreshed to match latest IdxToneRemoval json file

[x] https://github.com/pffy/googledocs-addon-chinese-frequency – IdxToneRemoval.gs
[x] https://github.com/pffy/googledocs-addon-hanyupinyin – IdxToneRemoval.gs
[x] https://github.com/pffy/googlescript-hanyupinyin – IdxToneRemoval.gs
[x] https://github.com/pffy/googlescript-tonelesspinyin – IdxToneRemoval.gs
[x] https://github.com/pffy/javascript-tonelesspinyin – idx-toneremoval.js

idx refresh complete


Noviny/brisk as gatsby plugin pt1

The first commit of this should have been merged already, so not sure what that's about.
I wrote up some things about this PR in this readme that explains the motivations, current things wrong, and next steps.

[ ] check why the first commit is not on master
[ ] rebase on master and resolve conflicts
[ ] update task for brisk docs documentation task to document dev workflow
[ ] rename bad start script
[ ] build-docs should just run brisk
[ ] document the clean script
[ ] remove unneeded yarn from dev script
[ ] update website readme


German Scheme Feedback: Glossary Hosting Environment

P.52
"The Hosting Environment consists of everything that is outside the TOE boundary and is equivalent to the CC term "Operational Environment.""
From this definition it sounds as if Hosting environment is a hypernym for TOE platform and Trusted Platform. This would contradict to the def of Trusted Platform: "[...] Trusted Platform is the underlying hosting environment [...]" which would mean that TP is identical to the Hosting Environment. How do these terms relate (Hosting Environment, TOE Platform, Trusted Platform)?

As we only touch the hosting environment in the context of the Trusted Platform, we will remove "Hosting Environment" from the glossary.


Prefer to load UA assemblies from the default ALC

This update makes it so that assemblies with Microsoft.DotNet.UpgradeAssistant prefixes are only loaded in extensions' assembly load contexts if the assemblies aren't able to be loaded in the default context.

We did this at one point I believe and intentionally changed it. What's this trying to fix?

@twsouthwick Huh, I don't remember that. Any idea why we changed it? Simona noticed that the UpgradeStepSample wasn't working because it has a project-to-project reference to Microsoft.DotNet.UpgradeAssistant.Abstractions which causes that dll to show up in the sample extension's build output. Because of that, when she tried to use the extension, it was mysteriously failing. Turns out ExtensionAssemblyLoadContext as it was prior to this change was preferring the extension-local version of Microsoft.DotNet.UpgradeAssistant.Abstractions to the one in the default ALC resulting in errors while loading the extension's service provider since base types didn't match.
An alternative fix would be to leave this code alone and make sure that extensions never have shared UA binaries next to them (project-to-project references make that a bit more of a pain but most developers will just use NuGet references which can just use private assets or something similar). It seems like an easy mistake to make, though (our samples somehow fell into this problem) and I can't think of any reason not to just always share Microsoft.DotNet.UpgradeAssistant.* libraries if we're able to. If there's some reason we changed this in the past, though, we can make keeping the binaries straight the extension author's responsibility.

The guidance for extensions is not to ship the abstractions library - it's removed from the packages when an extension is built. I'd prefer to update the samples to not copy them to the output.
I think the issue was that we had logic as to what to include and what not to. We hit weird issues with versioning, and it seemed better to just assume if an extension shipping binaries, it wanted those binaries. Since the abstractions library is the main contract, we could  potentially exclude that. Extensions shouldn't be using other UA libraries though.

That makes sense. I've updated this to only exclude the abstractions library, since that's one that extensions will depend on and should always be loaded in the default alc. I've also updated the samples to not copy that dll.

It's been a while, but the samples could probably use the pattern used by the loose assemblies that gets things referenced right automatically

Tested this locally against one of my sample projects using --extension cmd line arg against the UpgradeStepSample and successfully got

as expected.

@mjrousos looks like this change fails our Release build:
CSC : error CA1014: Mark assemblies with CLSCompliant [D:\a\_work\1\s\samples\UpgradeStepSample\UpgradeStepSample.csproj]
##[error]CSC(0,0): error CA1014: (NETCORE_ENGINEERING_TELEMETRY=Build) Mark assemblies with CLSCompliant
  Microsoft.DotNet.UpgradeAssistant.Extensions.Default.CodeFixes -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Extensions.Default.CodeFixes\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Extensions.Default.CodeFixes.dll
  Downloading from "[https://upgradeassistant.blob.core.windows.net/indexes/2021_09_17.index"](https://upgradeassistant.blob.core.windows.net/indexes/2021_09_17.index%22) to "D:\a\_work\1\s\src\extensions\looseassembly\LooseAssembly.NuGet\.data\2021_09_17.index" (245,503,658 bytes).
  Microsoft.DotNet.UpgradeAssistant.Steps.Backup -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Steps.Backup\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Steps.Backup.dll
  Microsoft.DotNet.UpgradeAssistant.Steps.Razor -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Steps.Razor\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Steps.Razor.dll
  Microsoft.DotNet.UpgradeAssistant.Steps.Templates -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Steps.Templates\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Steps.Templates.dll
  Microsoft.DotNet.UpgradeAssistant.Abstractions.Internal -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Abstractions.Internal\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Abstractions.Internal.dll
CSC : error CA1014: Mark assemblies with CLSCompliant [D:\a\_work\1\s\samples\SourceUpdaterSample\SourceUpdaterSample.csproj]
##[error]CSC(0,0): error CA1014: (NETCORE_ENGINEERING_TELEMETRY=Build) Mark assemblies with CLSCompliant
  Microsoft.DotNet.UpgradeAssistant.Analysis -> D:\a\_work\1\s\artifacts\bin\Microsoft.DotNet.UpgradeAssistant.Analysis\Debug\netstandard2.0\Microsoft.DotNet.UpgradeAssistant.Analysis.dll
  LooseAssembly.NuGet -> D:\a\_work\1\s\artifacts\bin\LooseAssembly.NuGet\Debug\net5.0\Microsoft.DotNet.UpgradeAssistant.Extensions.LooseAssembly.NuGet.dll
CSC : error CA1014: Mark assemblies with CLSCompliant [D:\a\_work\1\s\samples\PackageMapSample\PackageMapSample.csproj]
##[error]CSC(0,0): error CA1014: (NETCORE_ENGINEERING_TELEMETRY=Build) Mark assemblies with CLSCompliant
CSC : error CA1014: Mark assemblies with CLSCompliant [D:\a\_work\1\s\samples\FindReplaceStepSample\FindReplaceStepSample.csproj]
##[error]CSC(0,0): error CA1014: (NETCORE_ENGINEERING_TELEMETRY=Build) Mark assemblies with CLSCompliant

Ah, there's a root Directory.build.targets that's adding a common AssemblyInfo.cs that isn't getting included anymore after my change. I'll add an import to the new Directory.build.targets to import the root one.


Need Support to Configure xk6 Diameter with DTLS using SCTP

I was following this link to test diameter protocol: GitHub - MATRIXXSoftware/xk6-diameter: A k6 extension for Diameter protocol 1
I was able to make it work for non TLS with TCP. I want to configure xk6 Diameter with DTLS using SCTP. Do we have any sample config or any help link which mentions all this in detail.

You can enable TLS/SCTP using this example configuration:
let client = diam.Client({
    requestTimeout: "50ms",
    enableWatchdog: false,
    authApplicationId: [app.ChargingControl],
    vendorSpecificApplicationId: [
        {
            authApplicationId: app.ChargingControl,
            vendorId: vendor.TGPP,
        }
    ],
    capabilityExchange: {
        vendorId: 35838,
    },
    transportProtocol: "sctp",
    tls: {
        enable: true,
    },
})

Thanks @lwlee2608 for the response will try this and update.

@lwlee2608  I am using freediameter server version 1.2.1. I am seeing following error in the server:
21:16:46  NOTI   freeDiameterd daemon initialized. 21:16:54  ERROR  ERROR: in '(fd_tls_rcvthr_core(cnx, ctx->strid ? ctx->session : cnx->cc_tls_para.session))' :  Transport endpoint is not connected 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  ERROR  TLS ERROR: in 'gnutls_handshake( ctx->session )' :     Error in the pull function. 21:16:54  NOTI   Handshake failed on 15/16 stream pairs 21:16:54  ERROR  ERROR: in '((fd_sctp3436_handshake_others(conn, priority, alt_creds)))' :      Transport endpoint is not connected
Below is configuration I made based on the above suggestion:
let client = diam.Client({     requestTimeout: "50ms",     enableWatchdog: false,     authApplicationId: [app.ChargingControl],     vendorSpecificApplicationId: [         {             authApplicationId: app.ChargingControl,             vendorId: vendor.TGPP,         }     ],     capabilityExchange: {         vendorId: 35838,     },     transportProtocol: "sctp",     tls: {         enable: true,         cert: "/etc/ssl/CA/server3_cert.pem",         key: "/etc/ssl/CA/server3_key.pem",     }, })
Not sure its a problem with the server or the data that client is sending from xk6-diameter.

I have not used FreeDiameter, so I am unable to help you with that.
However, I tested xk6-diameter with this diameter server.
https://github.com/lwlee2608/diameter-example
SCTP  without TLS:

SCTP with TLS:

Sure Thanks @lwlee2608. The main reason I am sticking with freediameter is that it supports applications like SIP, 3GPP, NAS, EAP etc to test.  The server that you have shared above can it be used to test all these Diameter applications or Is this a custom server only for testing basic diameter flows. If we don't have support for this applications now in both client and server do we have any plans to add these later both from client and server perspective.


Add pass to eliminate local loads and stores in basic block.

This pass is another in a series of passes designed to reduce SPIR-V file sizes using classic code optimization techniques.
For every entry point function, remove unneeded loads and stores of
function scope variables. For each targeted variable load, if previous store
to that variable in the block, replace the load's result id with the value id of the
store. If previous load within the block, replace the current load's result id
with the previous load's result id. In either case, delete the current
load. Finally, check if any remaining stores are useless, and delete store
and variable if possible.
The presense of access chain references and function calls can inhibit
the above optimization.
This pass is most effective if preceeded by Inlining and
LocalAccessChainConvert. This pass will reduce the work needed to be done
by LocalSingleStoreElim and LocalSSARewrite.
You will notice that many members of this latest pass are redundant with those in LocalAccessChainConvertPass. Ultimately these will be collected in an Optimization Context along with state that will persist across passes. See issue #608.

OK. I think I have incorporated all comments from the access chain convert pass into this PR.
Again, you will note that this pass contains a number of member functions that are duplicates from the access chain conversion pass. These should all be folded into the proposed optimization context class.
This pass will handle nested access chains the same as non-nested. The behavior of GetPtr (and its comment) have been updated to deal with this.
This pass will not process modules that have non-logical addressing.

Please rebase this against master.

Rebased, squashed, and pushed into master as  7c8da66bc