Cannot run commands

I have just installed iF# as described in the readme. I then run the ipython notebook --profile ifsharp command, which starts up the server. At this point, all seems to be working fine. But when I open the Feature Notebook, the following is written in the console, and nothing really seems to work in the notebook itself.
2014-10-20 19:46:39.091 [NotebookApp] WARNING | Notebook /Feature Notebook.ipynb is not trusted
2014-10-20 19:46:39.400 [NotebookApp] ERROR | Unhandled error in API request
Traceback (most recent call last):
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/html/base/handlers.py", line 336, in wrapper
    result = method(self, *args, **kwargs)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/html/services/sessions/handlers.py", line 65, in post
    kernel_id = km.start_kernel(path=path)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/html/services/kernels/kernelmanager.py", line 90, in start_kernel
    kernel_id = super(MappingKernelManager, self).start_kernel(**kwargs)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/kernel/multikernelmanager.py", line 116, in start_kernel
    km.start_kernel(**kwargs)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/kernel/manager.py", line 217, in start_kernel
    **kw)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/kernel/manager.py", line 173, in _launch_kernel
    return launch_kernel(kernel_cmd, **kw)
  File "/Users/torbonde/anaconda/lib/python2.7/site-packages/IPython/kernel/launcher.py", line 260, in launch_kernel
    stdin=_stdin, stdout=_stdout, stderr=_stderr, cwd=cwd, env=os.environ)
  File "/Users/torbonde/anaconda/lib/python2.7/subprocess.py", line 710, in __init__
    errread, errwrite)
  File "/Users/torbonde/anaconda/lib/python2.7/subprocess.py", line 1327, in _execute_child
    raise child_exception
OSError: [Errno 2] No such file or directory
ERROR:tornado.access:{
  "Origin": "http://localhost:8888",
  "Content-Length": "56",
  "Accept-Language": "da-dk",
  "Accept-Encoding": "gzip, deflate",
  "Connection": "keep-alive",
  "Accept": "application/json, text/javascript, */*; q=0.01",
  "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10) AppleWebKit/600.1.25 (KHTML, like Gecko) Version/8.0 Safari/600.1.25",
  "Host": "localhost:8888",
  "Referer": "http://localhost:8888/notebooks/Feature%20Notebook.ipynb",
  "X-Requested-With": "XMLHttpRequest",
  "Content-Type": "application/x-www-form-urlencoded; charset=UTF-8"
}
ERROR:tornado.access:500 POST /api/sessions (::1) 37.50ms referer=http://localhost:8888/notebooks/Feature%20Notebook.ipynb
WARNING:tornado.access:404 GET /static/components/codemirror/mode/fsharp/fsharp.js (::1) 1.02ms referer=http://localhost:8888/notebooks/Feature%20Notebook.ipynb

Can anyone tell me what is going on? I should probably tell you that I am running OS X. I have a feeling this might cause the problems.

I have tried on both OS X 10.10.1 Mono 3.12.0 and Ubuntu 14.04 Mono 3.12.0 and am able to find the libzmq.* (dylib/so) file.
However I get the same error below on both when I try to launch IfSharp. I am able to build and run on Windows.
I did find this issue can happen if fszmq is used outside of windows. https://github.com/zeromq/fszmq/issues/41
@cgravill and @torbonde there were no additional changes you needed to do in order to get IfSharp to work with mono?
[ERROR] FATAL UNHANDLED EXCEPTION: System.Runtime.InteropServices.MarshalDirectiveException: string marshalling conversion 35 not implemented
  at (wrapper managed-to-native) fszmq.C:zmq_bind (intptr,string)
  at fszmq.SocketModule.Bind (fszmq.Socket socket, System.String address) [0x00000] in <filename unknown>:0
  at IfSharp.Kernel.App.Start$cont@228 (System.String[] args, Microsoft.FSharp.Core.Unit unitVar) [0x00000] in <filename unknown>:0
  at IfSharp.Kernel.App.Start (System.String[] args) [0x00000] in <filename unknown>:0
  at IfSharpConsole.Program.Main (System.String[] args) [0x00000] in <filename unknown>:0
2015-01-24 17:01:51.721 [NotebookApp] KernelRestarter: restarting kernel (3/5)
WARNING:root:kernel 09d4a489-f1a2-4a4b-bb46-483659851b0d restarted

I was able to get it to working (in OS X, haven't tried Ubuntu yet) by rebuilding the 3.2.7 branch of fszmq and replacing all instances of UnmanagedType.AnsiBStr with UnmanagedType.LPStr in the Native.fs as suggested by @pblasucci, and then just replacing the fszmq.dll library in the IfSharp bin folder. I would have just used the master branch, but methods have been removed/renamed and would require changes to IfSharp.Kernel.

@mndrake Out of curiosity, have you tried using the 4.0.x branch of fszmq? It should have addressed the LPStr issue. Although you will need to build it with --define:BSD_EAGAIN in order to run it correctly on OS X (because even agreeing on a simple error code is too much for the major OS developers).

@pblasucci I was able to use the 4.0.x branch successfully building locally as well as using the latest from nuget. I'm assuming that the latest nuget package was not built with the --define:BSD_EAGAIN flag. Even though it appears to be working with the nuget .dll what is the issue with not using the compiler flag on OS X?
@cgravill I was able to get a basic chart example working after adding and tweaking FSharp.Charting.Gtk and posted an example result in a gist (http://nbviewer.ipython.org/gist/mndrake/5d00eceea245704e8cf1). I was glad to get get something working and will post a fork when I am able to clean it up a bit. I had to create a temp file to write a png to and then read it back as a byte array, since I could not find a OxyPlot method that would write to a memory stream.

@mndrake That's terrific news! The main issue is Windows and Linux use the same value for the EAGAIN error code. However, most popular Unix systems define a different value for the same error. It's possible your code hasn't ran into this (it's definitely tucked into a small but important subset of possible scenarios). At any rate, I'm glad you got things working. Well done!

Here's a fork that is working for me for OS X. I had to create a custom FSharp.Charting.Gtk fork since I was not able to get the Model internal field exposed via reflection. I will try again later, since I would prefer to just have a ToPng method in IfSharp.Kernel instead of creating one in Sharp.Charting.Gtk. Figured "get it working" then others can help with the "get it right".
https://github.com/mndrake/IfSharp/tree/mono_mac
https://github.com/mndrake/FSharp.Charting
It even works in QT console!

That looks excellent. I was having some issues with panics on interacting with GTK. I'll try working from clean and your branch to see if we can get it running on Ubuntu too.

@cgravill I was able to get the following branch working on Ubuntu 14.04. I included the libzmq files so hopefully it will work by just restoring packages.
https://github.com/mndrake/IfSharp/tree/mono_linux

I think these issues have been combined and resolved in the Jupyter branch. I'll close this but feel free to open another focused issue if there are remaining issues with the Jupyter branch.


Promise support for Postgres

Using promises instead of callbacks fail.
Probably related to #12

Is there a work-around for this case for the moment (using await client.query() without a callback?)

We have not tested the workaround you mentioned yet. Theoretically you will lose the query subsegment as CLS doesn't track context on async/await. We need to thoroughly test the promise usage around Postgres so we can confidently say the SDK Postgres works with Promise.

Any news on this?

Related #60

I created #64 to address this.

This is released as part of v2.1.0. Please let me know if you have any questions.


Kotlin Typed Accessors not generated for a NamedDomainObjectContainer Extension when using addLater

Expected Behavior
Evaluation of the addLater Provider is done before generating typed accessors.
Current Behavior
Evaluation of the addLater Provider is done after generating typed accessors so a user cannot use them.
Context
Accordinging to the docs it is possible to generate custom typed accessors: https://docs.gradle.org/8.0-rc-1/userguide/kotlin_dsl.html#type-safe-accessors

Elements in project-extension containers (for example the source sets contributed by the Java Plugin that are added to the sourceSets container)

Steps to Reproduce
./gradlew build
Reproducer.zip

abstract class Foo @Inject constructor(private val name: String) : Named {
    override fun getName(): String = name
}

val foos = project.objects.domainObjectContainer(Foo::class.java)
project.extensions.add("foos", foos)
foos.addLater(project.provider { project.objects.newInstance("testFoo") })

Workaround
foos.add(project.provider { project.objects.newInstance("testFoo") }.get())

Your Environment
Gradle 8.0-rc-1

Build scan URL: https://scans.gradle.com/s/6dx33fmh5avks

Thank you for providing a valid reproducer.
The issue is in the backlog of the relevant team but the existence of a workaround makes it non-critical so it might take a while before a fix is made.

Another workaround can be to use register to keep the lazy aspect.

Yeah, register is a valid workaround to add one element.
In my code I use addAllLater to add multiple elements from a provider, and there is no registerAll, which makes sense, there is addAllLater.

Do you accept a PR?
If so, do you have any hints where to start implementing it?


Unusual Remapping (Renaming) Behaviour

Describe the bug
When remapping (changing path name) certain tokens, they usually get added to other token-types. I was editing my Font type tokens, deleting and remapping to typography. When I checked the inspect tab to double check the tokens applied, the font+typography naming where prefixed with the padding tokens.
Here is the used-case of a user facing the same issue:

For example, in the dimension tokens of a component I had the tokens:
idm-comp.table-header.item.inset.sm
idm-comp.table-header.item.inset.md
I subgrouped the group "item" again by adding .screen-lg. Now - idm-comp.table-header.screen-lg.item.inset.sm
After that this, the new subgroup was added to some mapping-links like color and borderwidth, borderradius, and not in the token names itself but in the mapping link which I can see in the inspect view.
So I had to remove the screen-lg in this mapping-links to correct it.

Expected behavior
Plugin shouldn't remap tokens into other token-types.
Screenshots or Screencasts
I have annotated the groups and the incorrect prefixed token names in Red

User screenshots:

User Recording:
User renames one group from Utrecht to Todo, but upon confirming the remap process all other tokens are renamed as well
https://github.com/tokens-studio/figma-plugin/assets/93133012/e70e95d2-275e-43ef-b073-b4f1db7efee5

This bug seems to be back. If via the JSON editor I:

Rename the group from utrecht. to todo..
Save json
Apply to page to update the references
See error

In the inspect panel I can see they haven't remapped and that I have to manually remap them from utrecht. to todo.
https://github.com/tokens-studio/figma-plugin/assets/93133012/b26616fa-8aec-4ccc-b49d-9db624a0ccb1
Test file

This is reproducible as of rc10

@six7 still present in 2.2.1.

@keeganedwin I dont understand the issue description, can you try to rephrase or create a 1min video explaining it?


Numpy version number in requirements.txt too low on MacOS

Dependency error when building (Mac OS 13.1). Changing numpy Version number to numpy==1.24.1 makes error message disappear.
ERROR: Ignored the following versions that require a different python version: 1.21.2 Requires-Python >=3.7,<3.11; 1.21.3 Requires-Python >=3.7,<3.11; 1.21.4 Requires-Python >=3.7,<3.11; 1.21.5 Requires-Python >=3.7,<3.11; 1.21.6 Requires-Python >=3.7,<3.11
ERROR: Could not find a version that satisfies the requirement numpy==1.21.3 (from versions: 1.3.0, 1.4.1, 1.5.0, 1.5.1, 1.6.0, 1.6.1, 1.6.2, 1.7.0, 1.7.1, 1.7.2, 1.8.0, 1.8.1, 1.8.2, 1.9.0, 1.9.1, 1.9.2, 1.9.3, 1.10.0.post2, 1.10.1, 1.10.2, 1.10.4, 1.11.0, 1.11.1, 1.11.2, 1.11.3, 1.12.0, 1.12.1, 1.13.0, 1.13.1, 1.13.3, 1.14.0, 1.14.1, 1.14.2, 1.14.3, 1.14.4, 1.14.5, 1.14.6, 1.15.0, 1.15.1, 1.15.2, 1.15.3, 1.15.4, 1.16.0, 1.16.1, 1.16.2, 1.16.3, 1.16.4, 1.16.5, 1.16.6, 1.17.0, 1.17.1, 1.17.2, 1.17.3, 1.17.4, 1.17.5, 1.18.0, 1.18.1, 1.18.2, 1.18.3, 1.18.4, 1.18.5, 1.19.0, 1.19.1, 1.19.2, 1.19.3, 1.19.4, 1.19.5, 1.20.0, 1.20.1, 1.20.2, 1.20.3, 1.21.0, 1.21.1, 1.22.0, 1.22.1, 1.22.2, 1.22.3, 1.22.4, 1.23.0rc1, 1.23.0rc2, 1.23.0rc3, 1.23.0, 1.23.1, 1.23.2, 1.23.3, 1.23.4, 1.23.5, 1.24.0rc1, 1.24.0rc2, 1.24.0, 1.24.1)
ERROR: No matching distribution found for numpy==1.21.3

I don't think it's mac related. Have you tried python3.8?

This is unrelated to OS version, rather than python version. The last change on requirements.txt was done 8 months ago, I think it is time to bump up versions for all related pip packages, including numpy.

numpy 1.22.0 works

Fixed this! Should be good now.


CASMTRIAGE-6980 Fix indentation

Description

These lines belong to the above step, but the indentation causes their HTML render to imply otherwise.
Checklist

[ ] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[ ] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[ ] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

/backport release/1.6


Remove outdated manifests from install/kubernetes

Resolves #4859
/cc @mandarjog @hklai
/assign @mandarjog

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
Assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @Tahler. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
9113f6726be7cd5f94b9ffd042d2f4163d6e5572
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
9113f6726be7cd5f94b9ffd042d2f4163d6e5572
link
/test istio-presubmit

prow/istio-unit-tests.sh
9113f6726be7cd5f94b9ffd042d2f4163d6e5572
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-bookInfo

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-bookInfo

prow/e2e-simpleTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-simple

prow/istio-presubmit.sh
fcf630a34cbd1c5c4c6d861aa3852fa2932aac21
link
/test istio-presubmit

prow/istio-unit-tests.sh
fcf630a34cbd1c5c4c6d861aa3852fa2932aac21
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@Tahler: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests.sh
194766001cff8b14b2c3eb502bf846fa331e4a27
link
/test e2e-bookInfo

prow/istio-pilot-e2e.sh
fa53f45f2c9efef28823294d4f427b8b02fa59d7
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I arrived at a solution where I just remove the unwanted files before the final archive. It's a little hacky for my liking but there was plenty of overlap and convolution that other solutions would require some redesign of the test/release pipeline.
@myidpt @wattli @mandarjog Do the citadel files (or any of the other files removed in this commit) need to be included in the release?

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: mandarjog
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [mandarjog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

Revised so as not to remove the *citadel* manifests from the release (they are used in some tasks).

Removed the commits which were only refactors. They belong in a different PR.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hklai, mandarjog
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [hklai,mandarjog]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

Okay. It passes release qualifications with one change. Good thing we tested through the release so thanks for that reminder.
https://github.com/istio-releases/daily-release/pull/552
https://gcsweb.istio.io/gcs/istio-prerelease/daily-build/tahler-test-release-4/

Have you tried downloading the artifacts and install manually as well?

Yes. I was able to install Istio with these artifacts and deploy bookinfo on a fresh GKE cluster. The main files, "istio.yaml" and "istio-auth.yaml", are identical to the daily releases.


identity: Avoid kvstore lookup for local identities

Reserved and CIDR identities are local to the agent and not stored in
the kvstore. This commit changes the identity cache to avoid performing
a kvstore lookup for CIDR entries (which is currently done when a CIDR
identity is released).
This PR is an optimization and should not change any observable
behavior (besides less unnecessary calls the kvstore).
This is a follow-up to https://github.com/cilium/cilium/pull/13205#discussion_r490306171
Signed-off-by: Sebastian Wicki<EMAIL_ADDRESS>

LGTM, ideally the commits should contain a Fixes: commit sha so we know to which branches the commit was backported.

I considered that, but the issue is unrelated to the linked PR, i.e. the behavior was present probably since we introduced local identities. The necessary lookup which is fixed here was just discovered as part oft the previous PR. Therefore I don't think Fixes: commit applies here ;)
For the same reason I also don't think this necessarily requires a backport. I'm not opposed to a backport, but this PR is not fixing any critical bug.

test-me-please

Seems like there should also be a way to do the same for LookupIdentityByID below.

Good point! I thought about it, but didn't realize that I could also determine by the numeric identity number if it was a global identity or not.
I amended the commit to include the condition for LookupIdentityByID as well, could you please take a look again @joestringer?

test-me-please


Allow for class level ngram updates to not timeout

When updating the ngrams for a large collection of documents, it's
possible for the cursor to timeout. Therefore add a boolean option,
timeout to the class level update_ngram_index method. This option
defaults to true.
Additionally, lock in the version of rubocop as pulling a newer minor
version (0.91.1) resulted in breakage do to new required yml
configurations.
Finally exclude full_text_search_spec.rb and full_text_search.rb
from a few specific rubocop linters to avoid future linting issues
related to file line counts.
Related: #44

@dblock Updated with your comments! One note, I locked rubocop into 0.55 and removed the ~> due to it pulling 0.91.1 locally and on Travis and generating a lot of errors related to an outdated rubocop_todo.yml file.

@dblock Updated with your comments! One note, I locked rubocop into 0.55 and removed the ~> due to it pulling 0.91.1 locally and on Travis and generating a lot of errors related to an outdated rubocop_todo.yml file.

Makes sense, feel free to upgrade rubocop in a separate PR.


Add a public setIcon() method to FloatingActionMenu

Hi,
Could you please add a public setIcon() to the FloatingActionMenu to set the icon programmatically?
Thanks

+1
I currently need to set the FloatingActionMenu icon  to different icons when opened and closed but
unfortunately, setIcon is not implemented.
Better yet, setOpenIcon, setCloseIcon methods will be useful to add.
Thanks

Like it is defined in the specification : http://material-design.storage.googleapis.com/publish/material_v_4/material_ext_publish/0Bzhp5Z4wHba3TmpnUHVKRV9DU0E/components-buttons-fab-transition_speeddial_02.webm

Please have a look at the sample. Is that what you need?

Awesome!
Can we add it to the documentation for everyone else


Experiment(backup/restore): Don't have support for CSI based volume.

Is this a BUG REPORT or FEATURE REQUEST?

Feature Request

Choose one: BUG REPORT or FEATURE REQUEST

What happened:

Backup/restore experiment doesn't have support for CSI volumes.

What you expected to happen:

Experiment should perform backup/restore functional test on CSI based volumes.

How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

PR ref: https://github.com/openebs/e2e-tests/pull/416


CI fails because "build.ps1 -restore" command stops if dotnet SDK version (global.json) is not available

Describe the bug
CI build fails after 90 minutes (pipeline timeout). "build.ps1 -restore" command stops if dotnet SDK version (global.json) is not available.
CI:

vmimage: windows-latest, ubuntu-latest
Version of DotNetDev.ArcadeLight.Sdk 1.5.53

Additional context
Azure vmimages will not always provide latest dotnet SDK versions

windows-latest
ubuntu-latest

Workaround: Always execute UseDotNet@2 before Build.ps1 -restore is executed
        - task: UseDotNet@2
          displayName: 'Use dotnet SDK (global)'
          inputs:
            packageType: 'sdk'
            useGlobalJson: true


change height of header

This PR references issue #78 by making the header background image fit the screen. It scales correctly for mobile devices as well!

Thanks for the contribution @SWELLZ.


the link to download conformance reports is broken and not working

Please fix.

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

ID: 784b1052-9ed9-3adb-7d38-3241529c8ec2
Version Independent ID: 6e6effbb-bb80-4bae-8644-b5bf44101c0c
Content: U.S. Section 508 - Microsoft Compliance
Content Source: microsoft-365/compliance/offering-Section-508-VPATS.md
Product: microsoft-365-enterprise
GitHub Login: @robmazz
Microsoft Alias: robmazz

@JeremyTyers - thanks for the feedback, I'm updating the topic with the correct link (https://cloudblogs.microsoft.com/industry-blog/government/2018/09/11/accessibility-conformance-reports/) now.


Define Action handler of Signin module

Related Issues
https://github.com/tymsai/marmoym-client/issues/140
Checklist

[x] Tested successfully.
[ ] Titles of commit message and PR are in English.
[ ] PR number at the title will be removed when squash and merge.
[ ] Guideline is followed.

Impressive. It's a brilliant start on action handling with React, knowing that you haven't had the knowledge on anything of the library.
And as talked in the conference, I want you to first resolve conflicts. We'll do that together this time.

git@github.com:UnoRich/marmoym-client.git


CrashLoopBackoff in Matts Consumer

1.2021-10-12T11:09:51.503+0000: °GC (Allocation Failure) 2021-10-12T11:09:51.503+0000: °DefNew: 21376K->2623K(24000K), 0.0342573 secs§ 21376K->5382K(77248K), 0.0344189 secs§ °Times: user=0.01 sys=0.03, real=0.04 secs§
2. 2021-10-12 11:10:03 ERROR Metadata:301 - °Consumer clientId=consumer-matts-group-1, groupId=matts-group§ Topic authorization failed for topics °my-topic§
Getting these two Error please help

Hi thanks for replying,OPA is relatively new topic so this was the only repository where I found the complete thing and was very much helpful..Would it be possible for you to share your email id please


Cannot get useful information when an error occurs

Hi,
I've observed the following behaviour: when using nethsm-sdk-rs and an API error occurs we're not getting real cause but rather error in serde: EOF while parsing a value at line 1 column 0.
As one practical example is the backup function (although I've seen it in other cases too).
If I'm not mistaken the actual issue is that on an API failure the code wants to deserialize the body of the response (in default_api.rs file: https://github.com/Nitrokey/nethsm-sdk-rs/blob/main/src/apis/default_api.rs#L2509) and the deserialization fails because the request has empty content (content-length: 0). (The deserialization in the backup case wants to create a SystemBackupPostError, looking at the source it's not clear how that would work without correct JSON in the error-case API response https://github.com/Nitrokey/nethsm-sdk-rs/blob/main/src/apis/default_api.rs#L561-L566).
It's quite possible I'm holding it wrong somehow so any suggestions are welcome!
(Our internal ticket: https://gitlab.archlinux.org/archlinux/signstar/-/issues/29 CC @dvzrv)

Thanks for the report!  Please check if https://github.com/Nitrokey/nethsm-sdk-rs/pull/31 helps in this case.  Also, if you know what kind of input triggers the problem, I can add a test case for it.

Also, if you know what kind of input triggers the problem, I can add a test case for it.

I think I know how to trigger that manually from a command line but let me get back to that and report back. Thanks for your time! :wave:

Hi @robin-nitrokey,
I've tested it on one use case and it looks quite a lot better - instead of serde error we're getting nethsm_sdk_rs::apis::Error::ResponseError! Of course we need to map the status code 401 into a variant on our end but it's possible now.
By the way I've noticed that the error message is basically stuffed in the header: "www-authenticate": "Basic realm=\"invalid authorization\"". (I wonder if there's a more standard approach for passing error messages to the client in the works, the Error types are really tiny)
As far as I'm concerned we could consider this closed and if I notice it doesn't work in some other place I'm happy to create a new issue.
Thanks for your help and time! :wave:

Thanks for the feedback!  Generally, most endpoints return error messages as part of the body in a JSON document.  But as this is not part of the OpenAPI spec, the generated error types don’t contain these strings.  I’m not sure why there is no error message in the body in this case.  My guess is that this is due to the control flow – authorization is handled by a lower level than the NetHSM business logic, and probably that level does not return error messages.

I’m not sure why there is no error message in the body in this case. My guess is that this is due to the control flow – authorization is handled by a lower level than the NetHSM business logic, and probably that level does not return error messages.

Thanks for confirming this! I'm planning to handle and save the error message string in the content body so I guess the login failure issue was not such a great use case... Now I need to look for another operation that can fail :thinking:

I see.  Maybe this test case is useful for you – if you call a normal operation on an unprovisioned instance, you should see an error message:
https://github.com/Nitrokey/nethsm-sdk-rs/blob/bd34dbf14a816bb984719938890a4f337d3a7565/tests/basic.rs#L27-L35
To do it properly, you would need to decode error.content as JSON and try to access the msg (?) field.

To do it properly, you would need to decode error.content as JSON and try to access the msg (?) field.

I think it's called message:
Error: NetHsm(Api("Adding user failed: Status code: 412: {\"message\":\"Service not available\"}"))

I'm going through the ticket that was reported by @dvzrv and it seems we've seen the "serde error" only in case of login failure :thinking: The other errors are currently properly packed in an Error::ResponseError. One way or another the idea of parsing returned JSON is going to make it quite more readable.
I think it's good to go!
I've got one more thing but I'll create a separate ticket for that.
Thanks for your help and time! :bow:

Yes, the login error triggered that problem specifically because it had no body, so it could not be deserialized into a ResponseError.


Update copyright headers for 2018

Our copyright headers currently say:
Copyright 2017 The Wallaroo Authors.

Let's update it to say:
Copyright 2017-2018 The Wallaroo Authors.

I don't believe this matters. There's no legal requirement to update as far as I know.
If that is the case, this seems like extra work that we don't need to do that adds noise to history etc.
Is there a reason to do this?

I only brought this up in the name of consistency -- if we're furnishing our source files with dates, it makes sense to keep doing it.
I understand the fact about adding noise to history, fair enough. If you think this is unnecessary to do in one fell swoop, I'm not going to press the issue. I do think we should be updating the copyright headers in files that we touch in the course of regular work.
Or drop the headers, and put a nice big COPYRIGHT file in the project root.

We can't drop all of them. Some are still BSD and not Wallaroo copyright (derived from Pony code).

@pzel Can we close this?


fix: sd-jwt without disclosures and must have ~

According to the spec and as also highlighten in this discussion, an SD-JWT without disclosures or kb-jwt must have a trailing ~
https://github.com/oauth-wg/oauth-selective-disclosure-jwt/issues/375

Ah that must've changed. When I implemented it was recommended that everything can be omitted when no disclosures are used.


Fixes for tooling improvement branch

See https://github.com/facebookresearch/mbrl-lib/pull/161

Running the tests now; it might also be feasible to update all the way to gym==0.26 or Gymnasium (the new fork of gym by the maintainers; gym is now unmaintained). They have better type support and fixes, but some large API changes to the step and reset methods.


Resolve ampersand to component-specific class, not instance-specific class

In the bellow example, one would expect the margin-left rule to apply to the button themed with the admin palette. But this is not the case : the ampersand is resolved to the instance class.
import React from 'react';
import styled, { ThemeProvider } from 'styled-components';

const normalPalette = {
   background: 'black',
   foreground: 'white'
}

const adminPalette = {
   background: 'white',
   foreground: 'black'
}

// Create a <Button> react component which background and foreground rules
// are theme-dependant, but the sibling rule with left margin should be transversal
// Unfortunately, it doesn't work because the two sibling button instances have
// different class names.
const Button = styled.button`
  ${({ theme }) => `
    background-color: ${theme.background};
    color: ${theme.foreground};
  `}
  &+& {
    margin-left: 10px;
  }
`;

export default () => {
  return (
    <div>
      <ThemeProvider theme={normalPalette}>
        <Button> normal button </Button>
      </ThemeProvider>
      <ThemeProvider theme={adminPalette}>
        <Button> admin button </Button>
      </ThemeProvider>
    </div>
  );
}

The workaround now is to use a direct reference to the component, as in such example. However, this is counter-intuitive, cumbersome and ugly !
Plus, in my use-case, I declare components and their styles in two steps since I am implementing a rich featured theme engine. In such circumstances, I cannot refer to react components classes.
Feature request (breaking change)
& should now be resolved to the component static class selector.
Alternative (non-breaking)
Offer a specific pseudo class that will be resolved to the static class selector, such as :sc.

This would be a breaking change, but I think it makes total sense to resolve & to the component-specific class now that we have it rather than the instance-class.
/cc @philpl @geelen

We already had an issue here regarding this but I think we mistakenly closed it: https://github.com/styled-components/styled-components/issues/774
In v3 we might have more tools to solve this, since we'll be able to reliable detect this selector and resolve it differently.

Instead all references with two styled components (& + &, & > &, & &) should resolve the second parent selector to the component specific class.

@philpl so that would also include compositions like &__icon + &__icon, right ?
What do you thing of the possibility for your library consumer to explicitly chose which class to refer to ? I though of specific namespaced pseudo classes but this is kind of hacky.

@sveinburne I don’t think that that’s a good idea.
Resolving the parent selector to the component class only will always lead to unexpected behaviour, so given the choice that will throw people off.
Having a special selector would be a non-standard CSS feature which we don’t want to introduce.
And last but not least, the “${() => Component}” interpolation will continue to work, which eliminates any need for a separate API, really.
Since these selectors that use the parent selector to refer to other components of the same type, but not necessarily the same props, are a special edge case, and I have not seen any other case where workarounds for selectors are necessary.
Thus if we detect these special cases and resolve them differently there’s:

no new APIs
no new edge cases
no need for awareness on the user’s side that this is happening

This detection should become quite trivial in v3, if we pull off ISTF, which I’m working on right now: https://github.com/cssinjs/istf-spec

@thysultan how feasible do you think is it to implement this now using a stylis middleware that targets selectors?
If we could detect something like /(.*&.*)?[+>](.*(&).*)+{/g and replace the ampersand (parent selector) after + or > with the component class using a simple regex, would that hurt perf a lot? I think you are a better judge of that than I am

@philpl It is feasible.
As an alternative proposal(Possibly a non-breaking change)...
Given the output s-c emits.
<button class="sc-bdVaJa cVcVQf"> normal button </button>
<button class="sc-bdVaJa fNjRsK"> admin button </button>

Why not use the sc-bdVaJa class to target all button instances for non dynamic values and cVcVQf for dynamic values.
In the example
&+& {
    margin-left: 10px;
}

would emit to a sc-bdVaJa while
  ${({ theme }) => `
    background-color: ${theme.background};
    color: ${theme.foreground};
  `}

To different styles targeting cVcVQf and fNjRsK.
From another angle you might be able to extend this branching of dynamic vs static to making use of the insertRule API solely for these dynamic branches.

@thysultan from a v2 and stylis perspective it's very hard to determine which rules are dynamic and which aren't. Also, I think this would break down if you had the example selector together with a dynamic selector, i.e.:
  ${elementTag} & + & {
     margin-left: 10px;
  }

I think it's harder to do and more error prone with more edge cases being created by an instable dynamic v static analysation. The difference is harder to define than it is said, while I can explain the selector change above with one regex, so I'm unsure whether this won't be more unstable.

From another angle you might be able to extend this branching of dynamic vs static to making use of the insertRule API solely for these dynamic branches.

This sounds like the static extraction optimisation, which will be hard to do even with v3, but I am thinking of this.
It's pretty hard to do these statis v dynamic analysations efficiently, since we either look at the tag's input before the transformation, or at the raw css with resolved interpolations, or at the final CSS from stylis.

Possibly a non-breaking change

Btw I think if we'd change the behaviour this dramatically, it definitely will be a breaking change for some cases. But if we just cover the cases that don't work correctly anyway, if I'm not mistaken, it shouldn't negatively influence anyone.
We basically just have to cover & + & ... and & > & ... where content can be around the ampersand symbols and where the first ampersand is optional.
New Idea: So actually, since it doesn't matter what happens to the other ampersand, maybe we can look at the selectors only once and transform them before the CSS reaches stylis? This would make such a transformation extremely cheap, performance wise, but more bug-prone I guess.

I'm positive ${elementTag} & + & { margin-left: 10px; } and other edge cases would work if you introduce a stylis middleware, an overview of the implementation logic:

Replace the interpolation with a static hash/placeholder.

You then have the delta – which is all the static content.
If it is not already the case you could probably do all of this at the component declaration level i.e when you call const Button = styled.div...  making the static part a constant time O(1) per component instead of a per instance operation.
At that point you now have you processed static css and a hashtable of components and their dynamic parts that you can pass to a new instance of Stylis that only handles dynamic css.

@thysultan it’s definitely possible, but let’s keep this issue on topic :smile:
I don’t think it’s worth introducing this right now as it’s a lot of work for such a small issue. Also, we have to “eject” dynamic rules that come before static ones as the static ones will have to keep their precedence. (Explained at the end of this https://gist.github.com/philpl/7b8a021f19ead2ec534091976a1ff6dc)
So I’m not convinced that we should start to introduce the static/dynamic logic and string manipulation for replacing interpolations when I’m specifically working on ISTF to make this part safer as well in the future.
I do have some code for the interpolation placeholders in the Babel plugin if there’s no other way. But since there is another way in this case I think we don’t have to go down this road

Sure, i'll open a new issue with my ideas on that.

replace the parent selectors / & after + or > with the component class using a simple regex`

@philpl The only hurdle i can see with is that middlewares are not privy to the & tokens, since at that point it would be the namespace passed to stylis. Though there is the option of adding a middleware pre-selector context that runs before & tokens are converted to the namespace to facilitate this.

@thysultan

Though there is the option of adding a middleware pre-selector context that runs before & tokens are converted to the namespace to facilitate this.

So it doesn't exist right now?

@philpl  Correct.

This is done in v4


fileDepsInfo.get is not a function or its return value is not iterable

Hi
I ran into a fatal error when trying to get svlangserver up and running on Emacs with lsp-mode. The error happens for all SystemVerilog files shortly after the file is opened in Emacs and lsp-mode tries to run the server. Maybe you have an idea to what the problem is based on the logs from Emacs below.
svlangserver::stderr
/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:292
        for (let fileDep of fileDepsInfo.get(file)) {
                                         ^

TypeError: fileDepsInfo.get is not a function or its return value is not iterable
    at SystemVerilogIndexer._incDepsRank (/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:292:42)
    at SystemVerilogIndexer._incDepsRank (/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:302:22)
    at /usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:287:22
    at Map.forEach (<anonymous>)
    at SystemVerilogIndexer._updatePkgFilesInfo (/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:284:32)
    at ChildProcess.<anonymous> (/usr/lib/node_modules/@imc-trading/svlangserver/lib/svindexer.js:198:22)
    at ChildProcess.emit (node:events:365:28)
    at emit (node:internal/child_process:920:12)
    at processTicksAndRejections (node:internal/process/task_queues:84:21)

Process svlangserver stderr finished

lsp-log
Command "/usr/bin/svlangserver" is present on the path.
Command "hdl_checker --lsp" is present on the path.
Command "/usr/bin/svlangserver" is present on the path.
Command "hdl_checker --lsp" is present on the path.
Found the following clients for /home/cbs/etc/example_code/systemverilog/crc32_8.sv: (server-id svlangserver, priority -1), (server-id lsp-verilog, priority -2)
The following clients were selected based on priority: (server-id svlangserver, priority -1)
This server does not support foldingRangeProvider
INFO: settings[systemverilog.includeIndexing] = **/*.{sv,svh}
INFO: settings[systemverilog.excludeIndexing] = test/**/*.{sv,svh}
INFO: settings[systemverilog.launchConfiguration] = /usr/bin/verilator -sv --lint-only -Wall
INFO: settings[systemverilog.defines] =
INFO: settings[systemverilog.lintOnUnsaved] = true
INFO: settings[systemverilog.formatCommand] = /usr/bin/verible-verilog-format
INFO: settings[systemverilog.disableCompletionProvider] = false
INFO: settings[systemverilog.disableHoverProvider] = false
INFO: settings[systemverilog.disableSignatureHelpProvider] = false
INFO: settings[systemverilog.disableLinting] = false
INFO: Indexing 87 files ...
INFO: Loaded cached index for 87 files
INFO: Done indexing 115 files!!!
INFO: Took<PHONE_NUMBER>996893 milliseconds

Messages
LSP :: svlangserver:211705 initialized successfully in folders: (/home/cbs/etc/example_code/systemverilog)
LSP :: svlangserver has exited (exited abnormally with code 1)
Server svlangserver:211705 exited with status exit(check corresponding stderr buffer for details). Do you want to restart it? (y or n) n

Software versions
$ uname -a
Linux carbon 5.12.2-1-MANJARO #1 SMP PREEMPT Fri May 7 17:53:15 UTC 2021 x86_64 GNU/Linux
$ svlangserver -v
Version is 0.3.2
$ emacs --version
GNU Emacs 28.0.50
$ lsp-mode
20210517.213

init.el
  (require 'lsp-verilog)
  (custom-set-variables
   '(lsp-clients-svlangserver-launchConfiguration "/usr/bin/verilator -sv --lint-only -Wall")
   '(lsp-clients-svlangserver-formatCommand "/usr/bin/verible-verilog-format"))
  (add-hook 'verilog-mode-hook #'lsp-deferred)

Wondering if the cache is corrupted somehow. Can you please try deleting the .emacs/.svlangserver directory in your workspace folder and then re-invoking emacs ? Do you see any errors in the lsp-log on the first invocation after deletion of cache?
Thanks

No I get the same error after deleting .emacs. Here is the output of lsp-log (but opening a file in a folder with fewer source files than before)
Command "/usr/bin/svlangserver" is present on the path.
Command "hdl_checker --lsp" is present on the path.
Command "/usr/bin/svlangserver" is present on the path.
Command "hdl_checker --lsp" is present on the path.
Found the following clients for /home/cbs/tmp/sv/crc32_8.sv: (server-id svlangserver, priority -1), (server-id lsp-verilog, priority -2)
The following clients were selected based on priority: (server-id svlangserver, priority -1)
This server does not support foldingRangeProvider
INFO: settings[systemverilog.includeIndexing] = **/*.{sv,svh}
INFO: settings[systemverilog.excludeIndexing] = test/**/*.{sv,svh}
INFO: settings[systemverilog.launchConfiguration] = /usr/bin/verilator -sv --lint-only -Wall
INFO: settings[systemverilog.defines] =
INFO: settings[systemverilog.lintOnUnsaved] = true
INFO: settings[systemverilog.formatCommand] = /usr/bin/verible-verilog-format
INFO: settings[systemverilog.disableCompletionProvider] = false
INFO: settings[systemverilog.disableHoverProvider] = false
INFO: settings[systemverilog.disableSignatureHelpProvider] = false
INFO: settings[systemverilog.disableLinting] = false
INFO: Indexing 6 files ...
INFO: Done indexing 8 files!!!
INFO: Took<PHONE_NUMBER>976449 milliseconds

I looked into if it's a specific one of my source files that is causing the error but it doesn't seem like it. I reduced my source catalog to two files that individually doesn't cause the error, but when both present it happens. I don't have them uploaded anywhere but I can paste them below in case you want to try and reproduce the error.
common_pkg.sv
package common_pkg;
  parameter TEST_PARAM = 12;
  int test_int = 14;

  typedef struct packed {
    logic        a;
    logic        b;
  } mytype2_t;

endpackage // common_pkg

testmodules.sv
`include "common_pkg.sv";
import common_pkg::*;

module testmodule (
  input logic                    clk_i,
  input [$clog2(TEST_PARAM)-1:0] aa_i,
  input logic                    a_i,
  output logic [1:0]             b_o
  );

  mytype2_t my;

  initial begin
    my.a = 0;
    my.b = 0;
  end

  always @(posedge clk_i) begin
    undeclared_var <= 1'b1;

    my.a <= 1'b1;
    my.b <= 1'b1;
  end
  logic undeclared_var;

  always_comb begin
    tmpa = tmpb;
    tmpb = 1;
  end
  logic tmpa;
  logic tmpb;

endmodule // testmodule

Thanks. I will check this out on my end.
May I ask why the common_pkg.sv is being included at the top? This will cause the tool to lint that file twice.
If you exclude the common_pkg.sv from indexing (using the systemverilog.excludeIndexing setting), does that cause the error to go away?

These files are just a collection of SystemVerilog files I keep to test with different language servers and Emacs configurations. I didn't write all of them myself and some might even contain syntax errors.
But from your comment it looks like it's triggered by common_pkg being included twice. If I delete the first line of testmodules.sv with `include I don't get the error anymore.

That is a good confirmation that the double linting might be an issue. I will look into fixing the error. Meanwhile hopefully this workaround is ok for you.
Thanks

Fixed in 0.3.4 release.


Rearrange QAT imports

This commit includes imports reordering which includes:

Moving QAT related API from main mct to mct.qat
Moving constants that are used by gptq and qat to the core constants (instead of being in qat constants).
Moving get_gptq_trainer_obj from FrameworkImplementation to a new class called GPTQFrameworkImplementation.
Adding 2 new classes (per-framewrok) that inherits GPTQFrameworkImplementation.

Update tutorials as well.


wasm-bindgen-test: #[should_panic] on one test prevents using console_error_panic_hook on another

Hey! First of all, as always, thank you so much for all the work y'all do on wasm for rust :heart:
I just come to report one tiny bug I hit, with the following code:
use wasm_bindgen_test::{wasm_bindgen_test, wasm_bindgen_test_configure};

wasm_bindgen_test_configure!(run_in_browser);

#[wasm_bindgen_test]
async fn bar() {
    std::panic::set_hook(Box::new(console_error_panic_hook::hook));
}

#[wasm_bindgen_test]
#[should_panic(expected = "bar")]
async fn foo() {
    panic!("bar");
}

This code results in a panic:
panicked at library/std/src/panicking.rs:135:9:
cannot modify the panic hook from a panicking thread

It's pretty convenient to have a panic hook setup to debug failing wasm tests, so I'm submitting this as an issue here.
The workaround is pretty simple: just extract the should_panic tests to another integration test, and it's good to go.
Anyway, lots of thanks for everything that already exists!

Unfortunately this will remain broken until Rust implements the exception handling proposal.
This is in line with Cargo test as well, using panic = "abort" together with should_panic doesn't really work on native either.

Hmm I'm not sure I understand? The wasm_bindgen_tests don't run with panic = "abort", do they? Otherwise I'd expect even just setting the panic hook to fail, but it did work fine before I added my first should_panic test.
And considering that tests are run sequentially, even if the implementation of should_panic needs a custom panic hook (which would be my guess), it still should be able to just set the panic hook when starting a new should_panic test, which shouldn't lead to this panic.
What am I missing?

Hmm I'm not sure I understand? The wasm_bindgen_tests don't run with panic = "abort", do they?

The Wasm target in general on Rust has no support for unwinding, so everything compiled to Wasm will use panic = "abort".

Otherwise I'd expect even just setting the panic hook to fail, but it did work fine before I added my first should_panic test.

Panic hooks are still run even with panic = "abort", but after the panic hook it will run std::process::abort() instead of unwinding.

And considering that tests are run sequentially, even if the implementation of should_panic needs a custom panic hook (which would be my guess), it still should be able to just set the panic hook when starting a new should_panic test, which shouldn't lead to this panic.

The problem is that Rust doesn't actually allow the application to continue to run after std::process::abort(), so continuing an application after a panic in Wasm is unsound. See https://github.com/rust-lang/rust/issues/117344.
But yes, a temporary fix might be to just reapply the panic hook after every should_panic test.

Oh, so if I understand correctly even having two #[should_panic] tests in a single module is currently unsupported? That's a bit sad, but good to know, thank you! :)

To be precise, #[should_panic] in general is not supported! Currently it works just by chance. E.g. if https://github.com/rust-lang/rust/issues/117344 gets fixed properly, it won't work at all.

Hmm maybe an idea, though it would not work well with non-headless tests.
What if we required the use of nextest to run the test suite? This would require implementing quite a bit more of the API for wasm-bindgen-test-runner, but it could allow the use of #[should_panic] in tests… I think? Because then it would never re-enter the module.

What if we required the use of nextest to run the test suite? This would require implementing quite a bit more of the API for wasm-bindgen-test-runner, but it could allow the use of #[should_panic] in tests… I think? Because then it would never re-enter the module.

I don't think requiring nextest is desirable, but supporting it would be nice!


[stdlib] Parametrize libdl like the other libs.

libdl is not present on OpenBSD and is not necessary to specify on this
platform. Parametrize it like the other libs and condition its use.

Yes. This pr only removes -ldl when OpenBSD.

cc @compnerd can you take a look?

ping.

ping

ping

@compnerd, would you review?

rebase?


SAPRFC legacy code migration

Hello,
First of all, thanks for the contribution.
I'm trying to migrate a legacy app using your lib.
I have a problem calling a function (FUNCTION_NAME in example below) where I need to append a value (123 in the example below) at the end of an internal table (TABLE1 in the example below) as a way to filter the results.
I tried invoking the function as below:
$function = $connection->getFunction('FUNCTION_NAME');

$returnValue = $function->invoke([
	'PARAMETER1' => 'PARAMETER1_VALUE',
	'TABLE1' => ['TABLE1_FIELD' => '123'],
]);

But I get the following message:
Failed to set TABLE row, expected array for parameter TABLE1
Could you please help me find out the solution?
Thanks in advance.

Just adding a little detail.
In the legacy app, the PARAMETER1 was set with a saprfc_import function.
While the TABLE1 was set with a saprfc_table_append function.

The error Failed to set TABLE row, expected array for parameter TABLE1  is caused by wrong parameter format in the ìnvoke() call.
Table parameters expect arrays of arrays, so something like this should work:
$function = $connection->getFunction('FUNCTION_NAME');

$returnValue = $function->invoke([
	'PARAMETER1' => 'PARAMETER1_VALUE',
	'TABLE1' => [
            ['TABLE1_FIELD' => '123'],
        ],
]);

It works perfectly. Thank you.


Helpful file additions

[x] Add requirements.txt for pip/easy_install users

[x] Add gitignore for pycharm users

[x] formatting on ethdrain.py

[x] added python-version file for pyenv/virtualenv users

Feel free to cherry-pick

Thanks!
Just wondering: why 2 new lines between functions? Is it a python-specific coding style?

https://www.python.org/dev/peps/pep-0008/#blank-lines

👍


fix: allow to add link with code block inside alias text part

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/22492
PROPOSAL: https://github.com/Expensify/App/issues/22492#issuecomment-1627450749
Tests

Go to a chat and add following comment

[```code```](google.com)

Verify that only code is displayed as code block and link google.com is displayed as auto link.
Edit the comment and verify the initial draft is

[```
code
```
]([google.com](https://google.com))

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

https://github.com/Expensify/App/assets/117511920/66d14c1c-3efc-424e-8312-ffc7e9550cdc

Mobile Web - Chrome

https://github.com/Expensify/App/assets/117511920/c24aa192-39ff-4b44-bd64-38d8e8bdb153

Mobile Web - Safari

https://github.com/Expensify/App/assets/117511920/7e2220aa-76cf-488a-aa19-9f5ec813bfc6

Desktop

https://github.com/Expensify/App/assets/117511920/c96a18d5-4fc9-43db-b0cd-8ff0a88b1dd9

iOS

https://github.com/Expensify/App/assets/117511920/291c283a-d19a-4ff7-a6bf-90fb1fb219b5

Android

https://github.com/Expensify/App/assets/117511920/d60497b6-a7d1-41b4-a72d-b46a80b81844

@hayata-suenaga @thesahindia @pecanoro
I know @eh2077 has been assigned for this issue.
But I could not stop to propose more improved approach. I think if (abort || match[1].includes('<pre>')) { is not reasonable (ofc, it results expected behavior), because modifyTextForUrlLinks function is called from both of link and autolink rule and then we can't figure out which rule needs the condition, so better to add a tweak on MARKDOWN_LINK_REGEX pattern. (simply add (?!\\[[\\s\\S]*<pre>[\\s\\S]*\\]))
const MARKDOWN_LINK_REGEX = new RegExp(`(?!\\[[\\s\\S]*<pre>[\\s\\S]*\\])\\[([^\\][]*(?:\\[[^\\][]*][^\\][]*)*)]\\(${MARKDOWN_URL_REGEX}\\)(?![^<]*(<\\/pre>|<\\/code>))`, 'gi');

Your thoughts ?

@Antasel I answered your comment on the issue itself thanks

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.3.44-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.45-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Jsonpath with bool values or null panics

I am not able to use jsonpath that has bool or null values, even though it is mentioned in README. For example this code based on example:
use serde_json::{json,Value};
use jsonpath_rust::json_path_value;
use jsonpath_rust::JsonPathFinder;
use jsonpath_rust::JsonPathValue;

fn main(){
    let  finder = JsonPathFinder::from_str(r#"{"first":{"second":[{"active":1},{"passive":1}]}}"#<EMAIL_ADDRESS>== true)]").unwrap();
    let slice_of_data:Vec<JsonPathValue<Value>> = finder.find_slice();
    let js = json!({"active":1});
    assert_eq!(slice_of_data, json_path_value![&js,]);
}

It is based on the example. Notice the jsonpath string is<EMAIL_ADDRESS>== true)]
The error when running is:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: " --> 1:30\n  |\n1 |<EMAIL_ADDRESS>== true)]\n  |                              ^---\n  |\n  = expected atom"', src/main.rs:7:139

Looks like this case is not added to grammar rules

Potential fix: https://github.com/besok/jsonpath-rust/pull/23

That is true. I don't see in gramma any traces of true|false|null literals.


Why is it wrong when I move webpack.config.js to the build folder

Hi,I have a problem.
Why is it wrong when I move webpack.config.js to the build folder？
It is cannot support IE8。
package.json
  "scripts": {
    "dev": "webpack-dev-server --config build/webpack.config.js",
  }

Packaging results：
Before:

After:

thank you!,
I found the reason：
{
        test: /\.js$/,
        include: [path.resolve(__dirname, '**../src**')],
        use: {
          loader: 'babel-loader',
        },
},


Avoid using id as a variable name

id() is reserved in Python for the identity function; see http://stackoverflow.com/questions/77552/id-is-a-bad-variable-name-in-python

+1 from @pobocks

Suggest reopen - it's still being used as a function argument in several places (example: https://github.com/RockefellerArchiveCenter/asExportIncremental/blob/master/asExportIncremental.py#L67)


Include more in-depth examples of querying WAF Logs

In all of the Azure documentation I can find, I see zero examples of WAF log queries for Log Analytics.
I currently work as Azure CSS Networking, and I have no resources to share with customers on how to perform even basic queries in Log Analytics.
All the articles merely link to general Log Analytics docs, nothing even remotely specific to WAF logs are present.
This section of the page : https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-diagnostics#firewall-log
Does not even mention Log Analytics, and states " The data is stored in the storage account that you specified when you enabled the logging."
This section further, does not mention Log Analytics :
https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-diagnostics#view-and-analyze-the-access-performance-and-firewall-logs
This guy's website does more than our own documentation does. Maybe we can do better?
https://francescomolfese.it/en/2018/07/azure-application-gateway-come-monitorarlo-con-log-analytics/

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

ID: e5f080ad-843f-d7be-eba6-2837993d052b
Version Independent ID: b6f75acf-e3ed-f6c3-a29e-8f440eb0a9dd
Content: Monitor access logs, performance logs, back-end health, and metrics for Azure Application Gateway
Content Source: articles/application-gateway/application-gateway-diagnostics.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: amitsriva

@csweet89 Thanks for the feedback Chris! I have assigned the issue to the content author to evaluate and update as appropriate.

Cool, thanks!
If I can be so bold as to suggest a query?
AzureDiagnostics
| where action_s == "Detected"
| summarize count() by ruleId_s, Message, details_message_s
This might not be 100% accurate, as I'm doing it from memory, but the purpose was just to count all the rule violations and provide a brief description for users. Just so they can see what is being detected.

@csweet89 Suggestions are always appreciated, @vhorne will be the one to take this forward. If this is taken this offline, please cc me on the Email.

@csweet89 An article was created to address log analytics topic. Please feel free to create a PR to add any queries you find useful.
https://docs.microsoft.com/en-us/azure/application-gateway/log-analytics
#please-close


[TACHYON-1648]Add the Chinese version of documentation page 'Hadoop MapReduce'

Add the Chinese version of documentation page 'Hadoop MapReduce'. See https://tachyon.atlassian.net/browse/TACHYON-1648

Can one of the admins verify this patch?

ok to test

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8501/
Test PASSed.

LGTM
Thank you for the translation!

Thanks for this PR. I left some comments @summerDG . Please find some time to address that. Happy Spring Festival!

BTW, please remember to add a screencast of the html page.

http://www.tachyon-project.org/documentation/master/en/Running-Hadoop-MapReduce-on-Tachyon.html

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8512/
Test PASSed.

LGTM. Thanks for the translation!


:sparkles: (notify) add wecom notify support

add wecom rebot notify support (https://developer.work.weixin.qq.com/document/path/91770).
closes  #5

Thanks for this contribution, look very good!
And could you please update the notification-related session in README.md?


Add token to magic_links create response

Verified by calling client.magic_links.create(user_id="user in my test account") and checking that the returned value had a valid token.
Fixes #112

Closing to re-open with @stytch GH account


No recently added anything

Describe the bug
The recently added TV sensor shows as off, even though I can see in Kodi that there's new TV shows.  Also, the attributes show this!
Data
[{"title_default": "$title", "line1_default": "$episode", "line2_default": "$release", "line3_default": "$rating - $runtime", "line4_default": "$number", "icon": "mdi:eye-off"}]

This is weird.  It was working before.
This naturally causes the card not to show anything.
Home Assistant and Custom Component versions (please complete the following information):
Home Assistant version: 2023-04-01
kodi-recently-added component version: 5.1.1

I have the same issue, in addition the sensors all show with names like kms_m_dec0746d3633e52946e6fbc6c69508ff meaning that I can't identify between them.

Hi,
I just published a version 5.1.2 that (should) fix the issue related to the "recently added" stuff.
@LukeBH ,
There was a breaking change with version 5.x. To allow multiple instances of the sensors, I had to attribute a unique ID to every sensor. By default, the entity id is the same as the unique id, but you can easily change that manually in HA. I'll try to have something more human readable in a future release.
@Rudd-O ,
If everything ok for you with the version 5.1.2, can you close the ticket please?

You can close the ticket.  It is fixed now.


New launcher maybe do not run newest version.

Hi @cryinkfly, I am not 100% sure but i think when Fusion get (bigger) update, directory name is changed.
New launcher presented in  PR #70 uses:
find /$HOME -name Fusion360.exe -printf %h -quit 2>/dev/null
and for me it return:
//home/tony/aplications/fusion360/drive_c/Program Files/Autodesk/webdeploy/production/e69ac0f55aa8512db83c718906bbdedf0daa2f89
But that's not latest version, correct is '4c84784f9b312b4c6ccb78d46529ebb70d7a5a09:
ls -la /home/tony/aplications/fusion360/drive_c/Program\ Files/Autodesk/webdeploy/production/
celkem 72

drwxrwxr-x 46 tony tony 20480 jun 19 20:33 e69ac0f55aa8512db83c718906bbdedf0daa2f89
drwxrwxr-x 45 tony tony 20480 jul 28 22:54 4c84784f9b312b4c6ccb78d46529ebb70d7a5a09
drwxrwxr-x  2 tony tony  4096 jul 24 12:46 6a0c9611291d45bb9226980209917c3d
drwxrwxr-x 46 tony tony 20480 jun 16 19:23 9b196c6eb71126665f61dbf5a4b48d188eb6263c

Something like this would return latest created file:
find /$HOME -name Fusion360.exe -printf "%T+ %p\n" | sort -r 2>&1 | head -n 1 | sed -r 's/.+0000000000 (.+)/\1/'

Hey @Tony763 I already noticed that in advance ... 😅
But since I'm actually still on vacation, I haven't checked that when a newer version comes out. 🤔😊
Thank you again for your great help! 👌

So I was able to incorporate your idea and created a solution:
fusion360starter="$(find $HOME -name Fusion360.exe -printf "%T+ %p\n" | sort -r 2>&1 | head -n 1 | sed -r 's/.+0000000000 (.+)/\1/')" && WINEPREFIX="$HOME/.wineprefixes/fusion360" wine "$fusion360starter"


Add pattern '${base64:JHtqbmRp'

I request to add pattern ${base64:JHtqbmRp which is evaluated to ${jndi. I think with the current algorithm, the detector can not detect these kind of patterns.
Ref
https://github.com/SigmaHQ/sigma/blob/master/rules/web/web_cve_2021_44228_log4j_fields.yml#L40

Oh, yes - from my own rule ... thanks

Oh, no, it's already in there : https://github.com/Neo23x0/log4shell-detector/blob/main/log4shell-detector.py#L35

Can i suggest that instead of looking for the string outright... a more foolproof way to handle the base64 is to actually do the decode. Because the issue is you can base64 encode any subset of the URI and combine it with other chars.

Could you explain why we would need more coverage with an example?
Which use isn't covered by ${base64:JHtqbmRp?

You can do this as an example.. encode only "di"
${jn${base64:JZGk}://}
or this ... encode just the "d"
${jn${base64:ZA==}i://}
or... any number of combinations of things that are part of the string

Ah, I see - yes, good to cover that as well

FYI, base64 isn't actually in a release yet, just in master, so these payloads shouldn’t work unless the target has chosen to add the lookup themselves.


Add prefix example on CONTRIBUTING.md

git log --oneline | cut -d " " -f 2 | grep '^\[[A-Z][A-Za-z0-9\-]*\]$' | sort | uniq -

The following prefixes were excluded from the prefix example.

[RN]
[React-Native]
[ReactKit]
[ReactNative]
[MAdMan]
[Pod] - duplicate (Pods)
[Images] - duplicate (Image)

While this would be nice, I think it could slow down merging PR's and would require a lot of buy-in from all parties. Thoughts @vjeux?

It would definitely be nicer to have consistent prefixes but honestly, I'm not sure that its worth the effort trying to enforce it compared to the wins of having it consistent.
Also, keep in mind that we use the exact same titles as they are authored by Facebook engineers. So when you see [ReactNative], it may mean that this particular engineer is not working on React Native as its primary job and just submits a feature for it. Therefore ReactNative in his context is the best way to communicate the topic of the commit. Multiple contexts are hard


fetch gitlab_ssl_certificate so the gitlab-runners can use it

One task that runs is Create self-signed certificate.
This task creates {{ gitlab_ssl_certificate }}, self-signed. If I want to register a gitlab-runner on other machines, then I need to copy: it to these gitlab-runner machines. Having it available in files/ would be really convenient.

- name: fetch certificate
  fetch:
    src: /etc/gitlab/ssl/gitlab.crt
    dest: files/certs/{{ gitlab_host }}.crt
    flat: true


SAMZA-1280 document for the general/universal resource localization in YARN

This PR added a MD for explaining localizing any resource in Samza on YARN  by configuring 4 key configurations.
yarn.resources.<resource-name>.path
yarn.resources.<resource-name>.local.name
yarn.resources.<resource-name>.local.type
yarn.resources.<resource-name>.local.visibility
This PR also updated the configuration table, updated index table and fixed several broken links in other docs.
The preview was done by following the following instructions and it looked fine.

go to samza/docs dir
run "bundle exec jekyll build"
run "_docs/local-site-test.sh"
run "bundle exec jekyll serve --watch --baseurl --port 4444"
open the browser and check
http://localhost:4444/learn/documentation/versioned/
http://localhost:4444/learn/documentation/versioned/yarn/yarn-resource-localization.html
http://localhost:4444/learn/documentation/versioned/jobs/configuration-table.html

It is not clear when the resource localization feature should be used. Can it be used based on the application needs or is it specific to security? Based on my understanding, it is the former. Please correct me if I am wrong.

@fredji97 Can you please answer my question?
Also, can you please reduce the description of PR to one or two lines? The entire description goes into the commit message. I would prefer that to be more concise. Once this is done, I can commit the PR. Thanks!

Here are the 4 configurations we are using:
yarn.resources.<resource-name>.path
yarn.resources.<resource-name>.local.name
yarn.resources.<resource-name>.local.type
yarn.resources.<resource-name>.local.visibility
Here are the test procedures for the preview.

go to samza/docs dir
run "bundle exec jekyll build"
run "_docs/local-site-test.sh"
run "bundle exec jekyll serve --watch --baseurl --port 4444"
open the browser and check
http://localhost:4444/learn/documentation/versioned/
http://localhost:4444/learn/documentation/versioned/yarn/yarn-resource-localization.html
http://localhost:4444/learn/documentation/versioned/jobs/configuration-table.html

@vjagadish1989 @fredji97 is on vacation for about a week I think. So, please merge this PR and make the suggested minor changes in a separate patch. :)


[SPARK-49566][SQL] Add SQL pipe syntax for the SET operator

What changes were proposed in this pull request?
This PR adds SQL pipe syntax support for SET operator.
This operator removes one or more existing column from the input table and replaces each one with a new computed column whose value is equal to evaluating the specified expression.
This is equivalent to SELECT * EXCEPT (name), <newExpressions> AS name in the SQL compiler. It is provided as a convenience feature and some functionality overlap exists with lateral column aliases.
For example:
-- Setting with an expression.
values (0, 'pqr', 2), (3, 'tuv', 5) as tab(a, b, c)
|> set c = a + length(b);

0, 'pqr', 3
3, 'tuv', 6

Why are the changes needed?
The SQL pipe operator syntax will let users compose queries in a more flexible fashion.
Does this PR introduce any user-facing change?
Yes, see above.
How was this patch tested?
This PR adds a few unit test cases, but mostly relies on golden file test coverage. I did this to make sure the answers are correct as this feature is implemented and also so we can look at the analyzer output plans to ensure they look right as well.
Was this patch authored or co-authored using generative AI tooling?
No

cc @cloud-fan @gengliangwang here is the |> SET operator :)

thanks, merging to master!

@HyukjinKwon @allisonwang-db  shall we implement df.withColumn with this way?


Nvidia nvs5100m -- no gpus found

Hi,
I suspect a bug in my gpu drivers (255.0.28):
void VulkanExampleBase::initVulkan(bool): Assertion `gpuCount > 0' failed

Can you run the cube demo?
And if you think it's an NVIDIA driver bug, you should probably tell NVIDIA :)

Hi,
I link to this lib:
https://github.com/SaschaWillems/Vulkan/blob/master/libs/vulkan/libvulkan.so
because i do not have such although i installed the driver. (?!) Looks like a driver issue,
Damn. I guess i will have to boot windows ...

ICDs such as NVIDIA's driver don't come with libvulkan.so (or at least they shouldn't).
That library acts like a sort of dispatch table, letting any application see all the drivers available (and therefore the hardware those drivers support).
You should search for a package called vulkan-icd-loader (or something similar) in your distribution's package manager. If all else fails, you can always install the Vulkan SDK manually :)
You need 3 things to run a Vulkan app:

Vulkan-capable hardware
An ICD which supports that hardware (eg. NVIDIA's driver)
The loader (libvulkan.so)

Thanks :+1:


Please upgrade to netstandard2.1

RT

netstandard2.2 is out now. (It was released 2 days before you opened this issue.) It might be worthwhile to skip 2.1 and go to 2.2.

see v3.1.0


Cloudformation resources do not get whitelisted

Describe the bug
The debug logs say that resources within a cloudformation stack are whitelist but when you look at the whitelist itself those resources are not there.
To Reproduce
Steps to reproduce the behavior:
Run the app and have cloudformation deletion enabled.
Expected behavior
Resources within cloudformation stacks should be whitelist and they are not
Screenshots

Versions (please complete the following information):

Serverless Framework: 2.62.0
boto3: 1.17.75
botocore: 1.20.75

AWS (please complete the following information):

Region: us-west-2

Additional notes
When I invoke again it shows the same "adding to whitelist" message so this confirms that on the initial run it says it is adding them but it's not doing it.

Ah I see that makes sense now. Thank youf or clarifying things for me!


Placeholder for JSON_PATH in JSON_SET

Hi, I tried different combinations:
SET `data`= JSON_SET(`data`, ?, ?) , [name, value]
SET `data`= JSON_SET(`data`, ??, ?) , [name, value]
SET `data`= JSON_SET(`data`, ?, ?) , ['"$.' + name + '"', value]
SET `data`= JSON_SET(`data`, ??, ?) , ['"$.' + name + '"', value]

And nothing is working, getting error.
How can I escape JSON_PATH in JSON functions?

I'm assuming your name variable does not start with the $. based on your last two examples. If so, your issue is you are including extra quotes on the second two. The following should work:
conn.query('SET `data`= JSON_SET(`data`, ?, ?)', ['$.' + name, value])


Adding University of Houston

Website Address - https://uh.edu/

@Tejaswini947 I am sorry, the domain cougarnet.uh.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


cannot connect to api server

Describe the bug
The api-client cannot conect to the api server.
To Reproduce
While librespot-api is running, open the api-client, set the field to ws://localhost:24879, click on connect. Nothing happens.
Expected behavior
Following the steps previously described, the api-client should connect to the api server.
Screenshots/Stracktraces/Logs
Screenshots if applicable, stacktrace and log is a crash occurred.
Version/Commit
Librespot-api compiled with maven from branch dev.

The api-client has been removed and won't be available anymore in future releases. It was too bulky and unnecessary as part of this project. It is equally simple to just use curl.

Ok, thanks for the quick response. So all the API logic will be removed from librespot-java?

The API logic will remain. I have modified it a little bit to make lighter, but I am happy to improve it as I don't use it much.

Thanks, so how do I establish the connection?

I have updated the README right now.

Thanks a lot!


Allow collapsing entire threads

difficulty/medium? No idea :D

Solved with https://github.com/adtac/commento/commit/689be47fde173e7576af9c5f8b594d90fb60c719


Implementations are required to accept a Gateway with a UDP listener when running HTTPRoute conformance tests

What happened:
https://github.com/kubernetes-sigs/gateway-api/pull/2661 added support for a UDP conformance test.
However, the corresponding Gateway is always installed https://github.com/kubernetes-sigs/gateway-api/blob/6865ac1ce5018695a60a180157c0644f03666af9/conformance/base/manifests.yaml#L721-L734
Implementations that don't support UDP will not Accept this Gateway:

Because protocol is not supported https://github.com/kubernetes-sigs/gateway-api/blob/6865ac1ce5018695a60a180157c0644f03666af9/apis/v1/gateway_types.go#L327-L331
Because no other non-UDP listeners are present - https://github.com/kubernetes-sigs/gateway-api/blob/6865ac1ce5018695a60a180157c0644f03666af9/apis/v1/gateway_types.go#L781

As a result, the tests cannot proceed and are stuck at:
helpers.go:222: gateway-conformance-infra/udp-gateway Gateway not Accepted yet
    helpers.go:221: Accepted condition set to Status False with Reason ListenersNotValid, expected Status True
    helpers.go:221: Accepted was not in conditions list [[{Accepted False 1 2024-03-26 21:20:04 +0000 UTC ListenersNotValid Gateway has no valid listeners} {Programmed False 1 2024-03-26 21:20:04 +0000 UTC Invali
d Gateway has no valid listeners}]]
. . .

What you expected to happen:
Supporting UDPRoute is not required for HTTPRoute conformance tests.
How to reproduce it (as minimally and precisely as possible):
Running the conformance test with supported features that don't have UDP. For example:
--supported-features=HTTPRouteQueryParamMatching,HTTPRouteMethodMatching,HTTPRoutePortRedirect,HTTPRouteSchemeRedirect,HTTPRouteHostRewrite,HTTPRoutePathRew
rite,GatewayPort8080

Here is an example output of the Gateway status set by NGF during a conformance tests run:
status:
  addresses:
  - type: IPAddress
    value: <IP_ADDRESS>
  conditions:
  - lastTransitionTime: "2024-03-26T21:20:04Z"
    message: Gateway has no valid listeners
    observedGeneration: 1
    reason: ListenersNotValid
    status: "False"
    type: Accepted
  - lastTransitionTime: "2024-03-26T21:20:04Z"
    message: Gateway has no valid listeners
    observedGeneration: 1
    reason: Invalid
    status: "False"
    type: Programmed
  listeners:
  - attachedRoutes: 0
    conditions:
    - lastTransitionTime: "2024-03-26T21:20:04Z"
      message: 'protocol: Unsupported value: "UDP": supported values: "HTTP", "HTTPS"'
      observedGeneration: 1
      reason: UnsupportedProtocol
      status: "False"
      type: Accepted
    - lastTransitionTime: "2024-03-26T21:20:04Z"
      message: 'protocol: Unsupported value: "UDP": supported values: "HTTP", "HTTPS"'
      observedGeneration: 1
      reason: Invalid
      status: "False"
      type: Programmed
    name: coredns
    supportedKinds: []

Thanks for catching this one, let's move the gateway

/assign


Creates settings.json in every project

Blockman creates a settings.json file in every project that has a .vscode folder. How do I disable this behavior?

Please provide, what is the content of the created settings.json file? I have never seen Blockman creating such file.

The content of the file is this:
{
    "workbench.colorCustomizations": {
        "editor.lineHighlightBackground": "#1073cf2d",
        "editor.lineHighlightBorder": "#9fced11f"
    }
}

I already added these to my user settings, so I'm not sure why this file is created in every workspace.

Sorry, I could not reproduce it. I tried manually creating .vscode file, also tried to create [name].code-workspace file, also tried to clear state of Blockman to trigger the activation events as it would be on a first installation event. But Blockman does not seem to have any deal with .vscode folder or inner files of that folder.
Almost 3 years passed since I published Blockman, and I have never seen anyone experiencing this issue. And it seems also logical, because Blockman applies the settings only on the first installation event, never again. Blockman does not change anything on restart, or when you open a new project folder.

Thank you for taking some time to look into this. I must have a global setting somewhere that I'm unaware of that's doing this. I just assumed it was something in Blockman because I have many other extensions installed, and it started happening after I installed Blockman. The settings in the settings.json also only happen to be the ones that are set by Blockman.

Maybe it would be good if you try to create a new profile in VS Code. With this new profile, you can have only one extension (Blockman), and test it how it will deal with .vscode folder. You can switch between the new profile and old default profile any time.

I created a new profile with only the Blockman extension installed and the settings.json file is not generated when I use that profile. I'll try disabling settings in my default profile one-by-one to track down the cause. I appreciate your help!


[Feature Request]: Consider publishing an actual 'latest' version too

Description
Currently, we publish latest minor and latest patch, in addition to the default patch version. However, we don't actually provide a latest major.
While it wouldn't be a best practice to use that version in production environments it would probably still be intersting for testing purposes and e.g. aligned with other means like the PS-Gallery.

What is the use case we want to cover? Is there a requirement from somewhere/someone?

Implemented with this commit


Slower than System.Random?

I wrote a tiny utility for performing a Fisher–Yates shuffle here. At first I wrote this using System.Random and StdGen but was informed this was supposedly extremely slow. I then updated to use this library  here. Surprisingly this led to worse performance on every experiment that I ran. Is this the wrong use case for this library (e.g. generating a million Ints between from i to 1000000 as i goes from 1 to 999999)? Or am I doing something else wrong? I did make sure to only generate a single generator but I am not very informed about the ins-and-outs of RNG and so this might simply be an inappropriate use case.

I only glanced at code. I can't see anything obviously wrong but I suspect that problem is lack of specialization. You could try to add INLINE/SPECIALIZE pragmas to the worker functions in Mutable.Shuffle

Here's a simplistic benchmark: BenchShuffle.zip.
Switch the random number generator on line 40 of BenchShuffle.hs, and switch to the corresponding branch of @Boarders' perfect-vector-shuffle library in the cabal.project file, to compare MWC with System.Random. The results I have obtained are as follows:
random-1.1
shuffle/10^6
                    | lower bound | estimate | upper bound
OLS regression      | 1.31 s      | 1.32 s   | 1.34 s
R² goodness-of-fit  | 1.000       | 1.000    | 1.000
Mean execution time | 1.30 s      | 1.31 s   | 1.31 s
Standard deviation  | 6.10 ms     | 7.48 ms  | 8.56 ms

mwc-random-<IP_ADDRESS>
shuffle/10^6
                    | lower bound | estimate | upper bound
OLS regression      | 1.94 s      | 1.97 s   | 1.98 s
R² goodness-of-fit  | 1.000       | 1.000    | 1.000
Mean execution time | 1.97 s      | 1.98 s   | 1.98 s
Standard deviation  | 2.76 ms     | 4.49 ms  | 5.48 ms

and for comparison tf-random-0.5:
shuffle/10^6
                     | lower bound | estimate | upper bound
OLS regression       | 970 ms      | 1.05 s   | 1.08 s
R² goodness-of-fit   | 0.999       | 0.999    | 1.000
Mean execution time  | 1.04 s      | 1.05 s   | 1.06 s
Standard deviation   | 10.6 ms     | 12.7 ms  | 14.0 ms

@Shimuuar : Adding INLINE, SPECIALISE, INLINEABLE and the ghc-options -fexpose-all-unfoldings
and -fspecialize-aggressively seems to make no difference and it is still significantly slower than System.Random without any of those added (it also does not seem to affect the performance if I add those pragmas there though).

I tried to reproduce issue and wasn't able to build reproducer. Is this still actual?


[FEATURE REQUEST] Adding color to the social icons when hovered upon

Description
Is your feature request related to a problem? Please describe.
Currently when we hover over the social icons in the footer they change their size, we can also a nice color to them which is according to their official brand color.
Describe the solution you'd like
adding suitable colors while hovering
Additional Notes (optional)
I'd like to work on it under GSSOC'23 if you approve @Abhirup-02 .

Somebody is already working on that


No messages received via usb

I have a problem connecting to the Mosaic-X5  Board via USB connection. The setup is complete but the data streams never start:
Driver output, where the receiver hangs: `[ INFO] [1695217621.574985984]: /septentrio_gnss: Setup complete.
[DEBUG] [1695217621.575028507]: /septentrio_gnss: Successully connected. Leaving connect() method
[DEBUG] [1695217621.575107190]: /septentrio_gnss: Leaving ROSaicNode() constructor..
[DEBUG] [1695217621.575844638]: /septentrio_gnss: A message received:   SBFOutput, Stream3, USB2, MeasEpoch+AttEuler+PVTCartesian+PVTGeodetic+PosCovGeodetic+VelCovGeodetic+DOP+ReceiverTime+ChannelStatus+AttCovEuler, msec50
[DEBUG] [1695217621.575914777]: /septentrio_gnss: handleCd: USB2>`

Can you please share your config and what version of the driver you are using?

Config gnss.yaml:

# GNSS/INS Parameters

# We set this with a udev rule. Use /dev/ttyACM0 or so in if you don't have udev rule set
device: serial:/dev/septentrioMosaic

serial:
  baudrate: 921600
  hw_flow_control: "off"

stream_device:
  tcp:
    ip_server: ""
    port: 0
  udp:
    ip_server: ""
    port: 0
    unicast_ip: ""

configure_rx: true

login:
  user: ""
  password: ""

osnma:
  mode: "loose"
  ntp_server: ""
  keep_open: true

frame_id: gps

aux1_frame_id: gps_base

get_spatial_config_from_tf: true

use_ros_axis_orientation: true

receiver_type: gnss

multi_antenna: true

datum: Default

att_offset:
  heading: 90.0
  pitch: 0.0

ant_type: "Unknown"
ant_serial_nr: "Unknown"
ant_aux1_type: "Unknown"
ant_aux1_serial_nr: "Unknown"

polling_period:
  pvt: 50
  rest: 0

use_gnss_time: false

latency_compensation: false

rtk_settings:
  ntrip_1:
    id: ""
    caster: ""
    caster_port: 2101
    username: ""
    password: ""
    mountpoint: ""
    version: "v2"
    tls: false
    fingerprint: ""
    rtk_standard: "auto"
    send_gga: "auto"
    keep_open: true
  ip_server_1:
    id: ""
    port: 0
    rtk_standard: "auto"
    send_gga: "auto"
    keep_open: true
  serial_1:
    port: ""
    baud_rate: 115200
    rtk_standard: "auto"
    send_gga: "auto"
    keep_open: true

publish:
  # For both GNSS and INS Rxs
  navsatfix: true
  gpsfix: true
  gpgga: true
  gprmc: true
  gpst: true
  measepoch: true
  pvtcartesian: true
  pvtgeodetic: true
  basevectorcart: false
  basevectorgeod: false
  poscovcartesian: true
  poscovgeodetic: true
  velcovcartesian: false
  velcovgeodetic: true
  atteuler: true
  attcoveuler: true
  pose: true
  twist: true
  diagnostics: true
  aimplusstatus: true
  galauthstatus: false
  # For GNSS Rx only
  gpgsa: false
  gpgsv: false

# logger

activate_debug_log: true```

The driver version is the version from the dev branch.

Thank you for the config. I tried it with both USB serial interfaces and it worked on my setup.
I am sorry, but I am a little clueless right now why it dos not work in your setup. Does your udev rule map /dev/ttyACM0 to /dev/septentrioMosaic ? Because on my machine /dev/ttyACM0 has the connection descriptor USB1 and /dev/ttyACM1 has USB2. Your debug output shows USB2.

I think the Udev rule is causing the error. I created a symlink to /dev/septentrioMosaic. I managed now to make everything work on the jetson nano with tcp connection without internet sharing. Thanks for your help:)

Great you could work it out.
Can you please share what was the trick to get it work on Jetson with tcp?

Ok, thank you for the explanation.
I indeed also had a look at this ntrip_client some time ago but since we have our receivers connected via real Ethernet we did not have a need for it so far.
The option to publish a generic NMEA sentence is on my TODO list but I do not have much time right now.