List the blobs in a container V12

I'm going through the walk through on Azure Blob Storage V12.
The section Labeled List the blobs in a container has the following snippet of code:
`Console.WriteLine("Listing blobs...");
// List all blobs in the container
await foreach (BlobItem blobItem in containerClient.GetBlobsAsync())
{
Console.WriteLine("\t" + blobItem.Name);
}`
The containerClient.GetBlobsAsync() doesn't appear to exist for me. I get the error message:
foreach statement cannot operate on variables of type 'AsyncPageable' because 'AsyncPageable' does not contain a public instance definition for 'GetEnumerator'
Is there a requirement of a particular version of dotnetcore. We are currently using 2.1.x LTS.

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

ID: 60e56e69-1c44-2056-ad5f-319535e4b525
Version Independent ID: 49fa6098-0b8e-ebf5-efe7-f50f3604e325
Content: Quickstart: Azure Blob storage library v12 - .NET
Content Source: articles/storage/blobs/storage-quickstart-blobs-dotnet.md
Service: storage
Sub-service: blobs
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

Source Material:
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-dotnet?source=docs

@RA-Work-A Thanks for your question. We are checking on this and will respond to you soon.

@RA-Work-A The code was tested with .NET Core v3.0. Are you able to try that?

@mhopkins-msft Possibly, but not w/o discussion with my team. Is upgrading my major version the only way to try this piece of functionality? If not, will rolling back to v11 work w/ v2.1x?

@RA-Work-A This quickstart is specifically targeted at v12. I just tried it with .NET Core 2.1 and it worked fine for me.

@RA-Work-A I may have figured it out. To run this with .NET Core v2.1, you need to add a <LangVersion>Preview</LangVersion> tag to your project file. Here is an example PropertyGroup from a .csproj file targeting .NET Core 2.1:
<PropertyGroup>
  <OutputType>Exe</OutputType>
  <TargetFramework>netcoreapp2.1</TargetFramework>
  <LangVersion>Preview</LangVersion>
</PropertyGroup>

Let me know if that works.
~ Mark

@mhopkins-msft That doesn't work for me. I have taken the liberty of uploading a simple console app for you to review. AzureStorageSample

Of Note, I'm also using VS 15.9.7

Hi @RA-Work-A,
Since I'm able to get the quickstart code running with .NET Core 2.1 it doesn't appear that this is a documentation issue. I recommend you post your question to the forums or contact support for further help. Here's a link to the support forums: https://azure.microsoft.com/en-us/support/community/
Thanks,
~ Mark
#please-close


Methods rename

GetUserAndSCM2 is now GetUserAndSCMForCourse
gorm methods GetRepository and DeleteRepository are now GetRepostoryByRemoteID and DeleteRepositoryByRemoteID correspondingly, to reflect the expected ID type

Coverage remained the same at 44.222% when pulling 2c211ef9cf8f4014864e76ccaf4cac4c5198fe39 on methods_rename into a2bc658d8f9c6115cf136cfa50ea2e3696cb4364 on master.


_posts/0000-01-02-DiegoJML.md

At this point I've created a branch, created a new file and made a commit and opened a pull request

Change file name

Change file name


refactor(staking): 🌹 hoist uptime tracking into ValidatorUptimeTracker extension trait

this is a small collection of noop refactors, cherry-picked out of #4070.
most importantly, this hoists track_uptime into a standalone extension trait. additionally, some improvements to telemetry helped make debugging tests in #4070 easier.

merging eagerly to clear the way for #4070, if that's alright!


Corporate Console - CLA Manager who has been already added to a project in the company is able to request to join the company

Background

Launch Corporate Console
Login as clamanager2
Click on the Company Bakbone
Click MANAGE APPROVED LIST for EMM project
Add nirupamavkrsna as CLAManager to the project
Login to Corporate Console as nirupamavkrsna
Issue1
Observed the company Bakbone is not listed in the Companies list even if the user is CLA Manager to a project in the company
Issue2
Click on Get Started
Search for company Bakbone
Click JOIN COMPANY
Observed that the CLA MAnager is able to request to join the company even if he/she is already added as CLA Manager to the project

The old v1 console is deprecated and removed.


Use machine_options[:ssh_username] for transport.

Give precedence to machine_options instead of machine_spec when itcomes
choosing the ssh username.
Also update the machine_spec with the machine_options value if transport
is successful.
This replaces #45 with a clean commit history.
Should solve #44 and #51.

In general, we haven't been giving precedence to machine_options because keys can drift over time; but I'm leaving this open even though #65 was committed, because there is a real discussion to have on this point.  I'm not happy at all with our credentials story, yet.

@miguelcnf for the moment I'm moving this one to Later since the primary issue (ssh_username is not honored) is fixed; but I still want to have this discussion.  It seems to me that there are real tradeoffs either way--if you prefer machine_options, it becomes changeable (which is super good), and if you prefer machine_spec, then recipe drift won't break your ability to reach older machines (which is also good).

Closing this for now; we're still aware of it but not planning to merge this at the moment.

@jkeiser Can we reopen this discussion?
chef-provisioning-aws today has implemented ssh transport (https://github.com/chef/chef-provisioning-aws/blob/master/lib/chef/provisioning/aws_driver/driver.rb#L948) in a way you can't update ssh_username on second convergence of machine node unless you actually delete the machine first. This is because machine_spec is higher precedence then what you set in machine_options. There seems to be no workaround is if you desire to update ssh_username (and force 2nd chef-client run) without deleting your machine.
I'd like to have this converstation because we followed this same implementation for our chef-provisioning-opennebula driver. I don't really want to our driver to have different logic then chef-provisioning-aws since its the most popular driver.

When I first wrote this I found it annoying but not a show stopper, I still look at it the same but in my head it makes total sense that machine_options have priority over machine_spec exactly for what @poliva83 described.
@tyler-ball let me know if you want me to look at this branch again and resolve conflicts etc.

a use case to have machine_spec with higher precedence than machine_options would be if there is a single provisioning user that can deploy VMs (for example to prod) and nobody else should have access to those machines ... how about making it configurable? this is how I implemented unique VM names, fqdn enforcement, and stop method override in opennebula driver

I don't think we should make the machine_options <=> machine_spec precedence configurable.  It seems like adding a knob where we don't need one.
I think that machine_options should override machine_spec.  It would be a breaking change so we would need a major version bump, but after documenting it I think it would make more sense to users.  What you specify in your recipe should always take precedence over what has been stored in the background.


Add support for hash fragment redirect targets

Adds support for hash fragment redirect targets.
This will allow e.g. old.md: new.md#section to work as expected.
I added a helper function to split the hash fragment off the rest of the path. Whenever the hash fragment gets in the way of path manipulation logic, it gets detached and/or reattached, as appropriate.
To validate I added duplicate test cases with hash fragments, though there are no tests for on_post_build(). I verified that with a mkdocs project, but can't readily share that verification.
Fixes #16

I think this is done. I am unsure how to address the concern over silent drop of the second return value from the helper function on line 133 on plugin.py. In my experience this hasn't caused any issues, but I defer to your expertise.

Thanks

:heavy_check_mark: :shipit:   https://github.com/mkdocs/mkdocs-redirects/releases/tag/1.1.0


This is my first issue

I am trying this.

And I'm commenting on that!
Manual - GT-1B Boss Studio.pdf

Done


ORC-777: Make the vectorized row batch size configurable in MR record readers and writers

What changes were proposed in this pull request?
The changes in this PR expose a new ORC config "orc.row.batch.size", which can be set as part of the MR job configuration to configure the MR readers/writers. The configuration is retrieved inside the ORCInput(Output)Format classes, before the readers/writers are initialized.
Why are the changes needed?
The change is needed to provide greater configurability of the ORC MR readers/writers.
Current behavior of OrcInput(Output)Format is to create an ORC reader/writer with the default row batch size of 1024. This may need to be overridden in certain scenarios to prevent OOMs during reads/writes.
How was this patch tested?
The existing unit tests in TestOrcOutputFormat and TestMapreduceOrcOutputFormat cover the changes to the signature of the constructors in OrcMapreduceRecordWriter and OrcMapreduceRecordReader. The change to override the row batch size config was also tested by running a MR job that used the snapshot version of the orc-mapreduce library.

@pgaref IIUC, what you are proposing is to have an overloaded constructor in OrcMapreduceRecordReader/Writer that accepts rowBatchSize as an argument (like we do in this PR), but leave it to the caller to override the getRecordWriter() method, which in turn calls the overloaded constructor. This way we don't need to introduce a separate config. LMK if I am missing anything.

Hey @sv2000  -- yes you are on point. Just want to avoid having an extra configuration here as it could confuse users.
If we can introduce a new constructor for Reader/Writer and release the change (on 1.6 or 1.7) it could sort out the issue.
Thoughts?

@pgaref IIUC, what you are proposing is to have an overloaded constructor in OrcMapreduceRecordReader/Writer that accepts rowBatchSize as an argument (like we do in this PR), but leave it to the caller to override the getRecordWriter() method, which in turn calls the overloaded constructor. This way we don't need to introduce a separate config. LMK if I am missing anything.

Hey @sv2000 -- yes you are on point. Just want to avoid having an extra configuration here as it could confuse users.
If we can introduce a new constructor for Reader/Writer and release the change (on 1.6 or 1.7) it could sort out the issue.
Thoughts?

@pgaref I am ok with the proposed change. One potential downside though would be that every user that needs to configure the row batch size will have to override the getRecordWriter() method. But may be worth the cost to pay to avoid the confusion of introducing a new config.

If we reach an agreement, shall we move forward in that way, @sv2000 ?

@pgaref @dongjoon-hyun Addressed comments on this PR. Can you help take a look?

To @sv2000 . I left a few minor comments about coding styling.
To @pgaref . Could you confirm that all of your concerns are addressed, please?

Thanks @dongjoon-hyun. I addressed your comments. Can you help take a look?

Hey @sv2000  thanks for making the changes -- thats exactly what I had in mind!
Let update PRs description and some of the Mapreduce Tests to use the new constructors -- will merge after that.

@pgaref Added unit tests to use the overloaded constructors and updated the PR description. LMK if the changes look ok.


discovery: compute SampleConfig only once

We previously computed the same thing every time.
This gives ~10s speedup in tests.

Codecov Report

Merging #1524 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1524      +/-   ##
============================================
- Coverage     87.05%   87.05%   -0.01%
  Complexity     4126     4126
============================================
  Files           404      404
  Lines         16619    16618       -1
  Branches       1764     1764
============================================
- Hits          14467    14466       -1
  Misses         1666     1666
  Partials        486      486

Impacted Files
Coverage Δ
Complexity Δ

...oogle/api/codegen/discovery/ViewModelProvider.java
90% <100%> (-0.17%)
11 <0> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update be88251...889bfa8. Read the comment docs.


CM-569_BE_user_can_logout

This PR is required as part of the logout story to unset the users refresh token, in effect loging them out the app.

Add /logout endpoint to api which unsets the users refresh token.

Add basic cypress test for logout

User can log out CM-569
created logout endpoint which unsets refresh token.
Added cypress test for logout

Hold off on merging. I need to double check if this will actually invalidate. I'm concerned a user will be able to circumnavigate this.

Hold off on merging. I need to double check if this will actually invalidate. I'm concerned a user will be able to circumnavigate this.

It won't invalidate the token it will just unset it in the client so that it no longer has it to use. We can do token blacklisting but i'd be inclined not to over complicate things for the first pass.

I've updated logout to use the built in jwt-extended function for unsetting cookies.
I've also removed the users endpoint as it shouldn't be included in this PR since we've deprecated the need for it.
This isn't passing cypress tests, so once those are updated feel free to merge. Thanks Nick!


Get rid of SASS files

Fixes #3577.
Turned out to be more involved than I expected, quite a few variables needed to be renamed and quite a few SASS concepts replaced even when moving everything just into createGlobalStyle.
This PR gets rid of all SASS dependencies, including sass-lint which should make our build times faster, styling more modular and consistent and also shrink down our security vulnerabilities list. This piece of work was long due :)
There should be no user visible changes in this PR, which is also the best way to test it - check the UI and make sure no styles are broken.

great work!


[FR] distutils.errors.* is not fully re-exported

What's the problem this feature will solve?
The Migration Advice in PEP 0632 says that setuptools is a sufficient replacement for distutils.errors. However, only DistutilsError and RemovedCommandError exist there. In distutils, there are:
In [7]: [e for e in dir(distutils.errors) if e.endswith('Error')]
Out[7]:
['CCompilerError',
 'CompileError',
 'DistutilsArgError',
 'DistutilsByteCompileError',
 'DistutilsClassError',
 'DistutilsError',
 'DistutilsExecError',
 'DistutilsFileError',
 'DistutilsGetoptError',
 'DistutilsInternalError',
 'DistutilsModuleError',
 'DistutilsOptionError',
 'DistutilsPlatformError',
 'DistutilsSetupError',
 'DistutilsTemplateError',
 'LibError',
 'LinkError',
 'PreprocessError',
 'UnknownFileError']

While all of the Distutils-prefixed ones derive from DistutilsError, the ones without the prefix are derived from CCompilerError, and so cannot be caught using anything exported by setuptools. Concretely, this makes it difficult to check for compiler flags, as done here.
Describe the solution you'd like
Re-export all distutils.errors.* in setuptools.errors.
Alternative Solutions
Currently, we use distutils.errors, but won't be able to after Python 3.12. One can use a generic Exception too, but that's not recommended.
Or as a complete alternative, if setuptools had a way to check whether a compiler supported a flag in a builtin way, then we wouldn't need to catch the CompileError ourselves.
Additional context
No response
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

I had this same question regarding use of this in scikit-image's setup.py. What is the recommended path forward here?


[19.03] virtualenv: Update patch for 16.2.0

(Cherry-picked from 2556b7bfad8341aa25fa4a3f9a2d4e4c8c85f67f)
Motivation for this change
I was affected by https://github.com/NixOS/nixpkgs/issues/57008 on 19.03 (23fd1394dc6bef03a2ff010278a24403a97f0647) and backporting the fix by @glasserc from https://github.com/NixOS/nixpkgs/pull/57533 fixed the issue.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build python2.pkgs.virtualenv python3.pkgs.virtualenv


Unable to perform ocr on image

Hi,
whenever I try to perform an ocr on an image, the console shows this error:
Uncaught (in promise) TypeError: Cannot read properties of null (reading '0')
at index.b5ed4a22.js:2:111129
How can I solve this? Logseq 0.8.11, Logseq-searchable 1.0.2 on macOS Ventura, tesseract 5.2.0 installed via homebrew.
Thank you!
Stephan

Have you installed the plugin through the marketplace? Because you wouldn't have to install tesserect at all if you did.
On 1 Dec 2022 at 11:13 AM +0400, stephanzettt @.***>, wrote:

Hi,
whenever I try to perform an ocr on an image, the console shows this error:
Uncaught (in promise) TypeError: Cannot read properties of null (reading '0')
at index.b5ed4a22.js:2:111129
How can I solve this? Logseq 0.8.11, Logseq-searchable 1.0.2 on macOS Ventura, tesseract 5.2.0 installed via homebrew.
Thank you!
Stephan
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Yes, I installed it through the marketplace. Tessaract was installed previously.

Are dependencies like tesseract.js loaded during installation? Apparently, there is no such file present on my system.

I'm having the same issue too, unfortunately. Installed through marketplace (also tried re-installing it too)

What OS are you running?
On 11 Feb 2023 at 12:16 PM +0400, Liam Scott-Russell @.***>, wrote:

I'm having the same issue too, unfortunately. Installed through marketplace (also tried re-installing it too)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

What OS are you running?
…
On 11 Feb 2023 at 12:16 PM +0400, Liam Scott-Russell @.>, wrote: I'm having the same issue too, unfortunately. Installed through marketplace (also tried re-installing it too) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.>

❯ uname -a
Linux arch-linux 6.1.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 24 Jan 2023 21:07:04 +0000 x86_64 GNU/Linux

❯ pacman -Q | grep logseq
logseq-desktop-bin 0.8.16-1

I had a look through the code and the raw text of the specific image that I'm trying to OCR, and I believe that the issue might stem from the fact that I'm using the built-in PDF annotator to highlight an area from a PDF, which "embeds" an image into the block, but doesn't actually create a link to a local file. Rather, it refers to an area annotation span within the PDF, which I believe Logseq then inserts as an image preview in the block.
e.g
- [:span]
  ls-type:: annotation
  hl-page:: 27
  hl-color:: yellow
  id:: 63e74c78-43e1-4f9f-a598-b9492df48af4
  hl-type:: area
  hl-stamp::<PHONE_NUMBER>226

Perhaps this is the cause of the issue?

Yeah, that’s likely the issue. Logseq doesn’t expose that to the plugin API unfortunately.
On 12 Feb 2023, 2:33 AM +0400, sawhney17/logseq-searchable @.***>, wrote:

I had a look through the code and the raw text of the specific image that I'm trying to OCR, and I believe that the issue might stem from the fact that I'm using the built-in PDF annotator to highlight an area from a PDF, which "embeds" an image into the block, but doesn't actually create a link to a local file. Rather, it refers to an area annotation span within the PDF, which I believe Logseq then inserts as an image preview in the block.

Yeah, that’s likely the issue. Logseq doesn’t expose that to the plugin API unfortunately.
…
On 12 Feb 2023, 2:33 AM +0400, sawhney17/logseq-searchable @.***>, wrote: I had a look through the code and the raw text of the specific image that I'm trying to OCR, and I believe that the issue might stem from the fact that I'm using the built-in PDF annotator to highlight an area from a PDF, which "embeds" an image into the block, but doesn't actually create a link to a local file. Rather, it refers to an area annotation span within the PDF, which I believe Logseq then inserts as an image preview in the block.

ahh that's unfortunate that they don't support that, thanks for clearing this up


Error : Not working !!!

raise WebSocketBadStatusException("Handshake status %d", status)
websocket._exceptions.WebSocketBadStatusException: Handshake status 403

can you try now ? It is still working for me.

can you try now ? It is still working for me.

Working 4 me ;)


Extra package causes make-dep-globs error

I have defined an extra package foreign-generic here
https://github.com/purs-nix/purs-nix/blob/2c970695f0ca8d5524bbcacb02f0537e1cc8ff31/examples/hello-world/flake.nix#L26-L46
which is not in the package set.
This definition follows these instructions https://github.com/purs-nix/purs-nix/blob/master/docs/adding-packages.md with a couple of modifications due to this: https://github.com/purs-nix/purs-nix/issues/34
nix build shows this error:
error: cannot coerce a set to a string

       at /nix/store/pqw2sx1hf5cjhvlnbpxpbv6rxsmam5l8-source/purs-nix.nix:88:32:

           87|         make-dep-globs = deps:
           88|           toString (map (a: ''"${a}/**/*.purs"'') deps);
             |                                ^
           89|

which I think originates here:
https://github.com/purs-nix/purs-nix/blob/2c970695f0ca8d5524bbcacb02f0537e1cc8ff31/purs-nix.nix#L87-L91
Am I adding the extra package incorrectly, causing this issue? Is it an error in make-dep-globs?
Thanks

I was using this incorrectly. This works:
https://github.com/peterbecich/halogen-chess/blob/2d881da34f513f79da479d804b7eb740d0dcc887/flake.nix#L52-L96


d87ee5af03a1cec0c6d992fb540babdbe392c739

https://github.com/microsoft/vscode/issues/169950#issue-1509778934

d87ee5af03a1cec0c6d992fb540babdbe392c739

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!


Change node versions we test with on travis

At this time stable (6.2) is failing because of some dependency that apparently
has an issue with the architecture of the system that travis is running the
build on. Not clear at this time, but also not super important to me. We are
standardizing on 4.4.4 for all silvermine projects currently, so we'll test
that as well as 4 and 5 latest.

Coverage remained the same at 68.792% when pulling 5109ad2e100480c0b81cbfbb5ab32f40aed8bbbd on change_npm_travis_versions into b55c48cd5ff348a11bd4576412071f8821893958 on master.


Dockerfile part2

This PR simplify download of systemvm templates, work with docker-compose and enable integration-api port and use of localstorage without reconfiguration of cloudstack.
Thanks

aside of the vhd-util download, +1 LGTM based on code review.
Does not impact cloudstack core

remote branch broken. closing this PR...


Support export to Markdown

The addition of Markdown would be essential for many when being utilized for writing documentation and providing/consuming code samples.
Thanks for the work on this!!

I'm willing to get a feature branch started and spearhead this feature if the maintainers are game (or assist where needed, if someone has already started on it).


jdk_security3: sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager/PreferredKey fails

sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager/PreferredKey fails with java.lang.Exception: Failed to get the preferable key aliases
20:47:11 HOME=/home/jenkins
20:47:11 LANG=en_US.UTF-8
20:47:11 PATH=/bin:/usr/bin
20:47:11     /home/jenkins/workspace/openjdk_test_x86-64_linux/openjdkbinary/j2sdk-image/jre/bin/../../bin/javac
20:47:11         -J-ea
20:47:11         -J-esa
20:47:11         -J-Xmx512m
20:47:11         -J-Dtest.class.path.prefix=/home/jenkins/workspace/openjdk_test_x86-64_linux/jvmtest/OpenJDK_Playlist/SE80/work/classes/0/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager:/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -J-Dtest.src=/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -J-Dtest.src.path=/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -J-Dtest.classes=/home/jenkins/workspace/openjdk_test_x86-64_linux/jvmtest/OpenJDK_Playlist/SE80/work/classes/0/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -J-Dtest.class.path=/home/jenkins/workspace/openjdk_test_x86-64_linux/jvmtest/OpenJDK_Playlist/SE80/work/classes/0/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -J-Dtest.vm.opts='-ea -esa -Xmx512m'
20:47:11         -J-Dtest.tool.vm.opts='-J-ea -J-esa -J-Xmx512m'
20:47:11         -J-Dtest.compiler.opts=
20:47:11         -J-Dtest.java.opts=
20:47:11         -J-Dtest.jdk=/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdkbinary/j2sdk-image/jre/bin/../..
20:47:11         -J-Dcompile.jdk=/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdkbinary/j2sdk-image/jre/bin/../..
20:47:11         -J-Dtest.timeout.factor=4.0
20:47:11         -d /home/jenkins/workspace/openjdk_test_x86-64_linux/jvmtest/OpenJDK_Playlist/SE80/work/classes/0/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -sourcepath /home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager
20:47:11         -classpath /home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager:/home/jenkins/workspace/openjdk_test_x86-64_linux/jvmtest/OpenJDK_Playlist/SE80/work/classes/0/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager:/home/jenkins/workspace/openjdk_test_x86-64_linux/openjdkbinary/j2sdk-image/jre/bin/../../lib/tools.jar
20:47:11         -XDignore.symbol.file=true /home/jenkins/workspace/openjdk_test_x86-64_linux/openjdk-test/OpenJDK_Playlist/openjdk-jdk8u/jdk/test/sun/security/ssl/com/sun/net/ssl/internal/ssl/X509KeyManager/PreferredKey.java
20:47:11
20:47:11 ACTION: main -- Failed. Execution failed: `main' threw exception: java.lang.Exception: Failed to get the preferable key aliases

From the readme, I understand we can run an individual test (testExampleExtended_SE80_0) as below:
make _testExampleExtended_SE80_0
What is the test name or make target name to run this test?

To reproduce the failure you can run make jdk_security3_0. Note if test is excluded in ProblemList.txt you will also need to comment out that excluded tests.

Recreated this issue the test fails as chooseClientAlias() method does not return the DSA key
alias = km.chooseClientAlias(new String[] {"DSA", "RSA"},null, null);
String algorithm = km.getPrivateKey(alias).getAlgorithm(); // This returns RSA instead of DSA and this is because DSA key has expired. See keytool output below:
$ keytool -list -v -keystore ./etc/keystore -storepass passphrase
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 3 entries
Alias name: dummydsa
Creation date: Mar 10, 2007
Entry type: PrivateKeyEntry
Certificate chain length: 1
Certificate[1]:
Owner: CN=dummy.example.com, OU=Dummy, O=Dummy, L=Cupertino, ST=CA, C=US
Issuer: CN=dummy.example.com, OU=Dummy, O=Dummy, L=Cupertino, ST=CA, C=US
Serial number: 45f3a314
Valid from: Sat Mar 10 22:35:00 PST 2007 until: Tue Mar 07 22:35:00 PST 2017
Certificate fingerprints:
SHA1: E5:EE:0A:8B:90:37:64:FD:B5:8C:03:D5:ED:3B:9F:2B:48:71:14:08
SHA256: BB:0E:3C:95:2F:C4:B6:BE:A6:F7:09:DB:82:27:33:8E:81:14:D6:81:EA:F0:9D:5F:B2:DC:A1:AE:7B:93:72:FC
Signature algorithm name: SHA1withDSA
Subject Public Key Algorithm: 1024-bit DSA key
Version: 1
Fails with both openjdk9-openj9 build and openjdk9 build.

There is a bug already raised for this, expired certificate was fixed but the change was backed out due to some other DTLS tests failures. See https://bugs.openjdk.java.net/browse/JDK-8176354
I think this test should be excluded, can I go ahead and raise a PR to exclude this?

@chandrams Could you please confirm the test only fails with jdk9? I didn't see the failure recently with jdk8. Thanks.

@sophia-guo It failed with openjdk8 build too
java -showversion PreferredKey
openjdk version "1.8.0-internal"
OpenJDK Runtime Environment (build 1.8.0-internal-jenkins_2017_07_27_20_16-b00)
OpenJDK 64-Bit Server VM (build 25.71-b00, mixed mode)
algorithm = RSA alias = DSA
Exception in thread "main" java.lang.Exception: Failed to get the preferable key aliases
at PreferredKey.main(PreferredKey.java:71)
I checked the DSA key in the keystore in openjdk-jdk8u test material it has expired. Can you please let me know with which jdk8 build you tested or if you could retest it. Thanks.
Note - I 'm just running this test alone as a standalone and not jdk_security3 target.

Test build are using jdk8 https://api.adoptopenjdk.net/openjdk8/nightly/

I had run only the test PreferredKey as a standalone.  I have tested it using the jdk_security3 target with both Java8 and Java9, the test doesn't run as it is already excluded in ProblemList.txt in openjdk-jdk8u and openjdk-jdk9 repos.  Hence we can close this issue.


Feature/tuya panel gateway sdk

Description
Universal gateway control business component
1.AddDeviceTip
2.SetPassword
3.TempHumWithBlur
4.TopBarWithArc
Package

[ ] tuya-panel-animation-sdk
[ ] tuya-panel-api
[ ] tuya-panel-electrician-sdk
[ ] tuya-panel-ipc-sdk
[ ] tuya-panel-lamp-sdk
[ ] tuya-panel-lock-sdk
[ ] tuya-panel-robot-sdk
[x] tuya-panel-gateway-sdk

Type of change
Please select the relevant option.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

@Oliverzzq 大佬，看下需要改的地方

Codecov Report

Merging #42 (4471c62) into main (b094f06) will decrease coverage by 0.03%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##             main      #42      +/-   ##
==========================================
- Coverage   56.66%   56.63%   -0.04%
==========================================
  Files          98      115      +17
  Lines        4011     4204     +193
  Branches      848      888      +40
==========================================
+ Hits         2273     2381     +108
- Misses       1730     1821      +91
+ Partials        8        2       -6

Impacted Files
Coverage Δ

...-gateway-sdk/src/components/addDeviceTip/index.tsx
42.30% <42.30%> (ø)

...l-gateway-sdk/src/components/setPassword/index.tsx
48.27% <48.27%> (ø)

...teway-sdk/src/components/tempHumWithBlur/index.tsx
88.88% <88.88%> (ø)

...gateway-sdk/src/components/topbarWithArc/index.tsx
93.33% <93.33%> (ø)

...eway-sdk/src/components/addDeviceTip/i18n/index.ts
100.00% <100.00%> (ø)

...-gateway-sdk/src/components/addDeviceTip/styles.ts
100.00% <100.00%> (ø)

...teway-sdk/src/components/setPassword/i18n/index.ts
100.00% <100.00%> (ø)

...l-gateway-sdk/src/components/setPassword/styles.ts
100.00% <100.00%> (ø)

...y-sdk/src/components/tempHumWithBlur/i18n/index.ts
100.00% <100.00%> (ø)

...ay-sdk/src/components/tempHumWithBlur/res/index.ts
100.00% <100.00%> (ø)

... and 35 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b094f06...4471c62. Read the comment docs.


[rjsf] Styles fixes

Signed-off-by: harkiratsm<EMAIL_ADDRESS>Description
This PR fixes #
Notes for Reviewers
Two Columns Layout.
Signed commits

[ ] Yes, I signed my commits.

Newer Changes -

Two Columns Layout for the Design Configurator
& fix three items from this https://app.clickup.com/t/2wnamcr

This PR fixes -

Fixed the behaviour when input field .
On expand the items/object/array fields are not expanding.
Be consistent with cursor on tooltip - default pointer (arrow).
Apply a bottom margin to name and namespace + no overlapping.
Fixed labels and annotations behaviour in Design Configurator .
...... typing

@harkiratsm signal after today's feedback has been incorporated.

Newer Changes are - scaling the fields using space-around .

@leecalcote

@harkiratsm provide a revised, itemized list of changes, please.

@harkiratsm provide a revised, itemized list of changes, please.

https://github.com/meshery/meshery/pull/6360#issuecomment-1277436451

@harkiratsm I don't know what this means: [ Not accepted currently ]


ta-lib

Is it very necessary ?

No, unless you use a trading method that uses talib indicators. TAli is mostly for people writing their own strategies.

Just ask because when you start gekko (and when I'm following it) you asked someone for a Genetic Algorithm without ta-lib wich is incompatible for Win32)
I wrote since a long time my own strategies.. Thank you

you asked someone for a Genetic Algorithm without ta-lib wich is incompatible for Win32)

Ah yes, this was some exploring: This Genetic Algorithm never ended up in Gekko (mostly because of differences in how positions are taken in that project compared to how gekko deals with them). So right now you cannot use that in combination with gekko...

I wrote since a long time my own strategies.. Thank you

If you write your own you only need talib if you want to add talib indicators to your method.

My fifferent point of vue is that this library need ta-lib that I cant use in Win.
It was a very very good way, but the owner never answerd even if he worked on a version without Ta-lib wich was a good start.
I just use my own strategie on old gekko without talib.
Thank you to answered
From: Mike van Rossum
Sent: Monday, March 6, 2017 1:25 PM
To: askmike/gekko
Cc: Pascal Marois ; Author
Subject: Re: [askmike/gekko] ta-lib (#612)
you asked someone for a Genetic Algorithm without ta-lib wich is incompatible for Win32)
Ah yes, this was some exploring: This Genetic Algorithm never ended up in Gekko (mostly because of differences in how positions are taken in that project compared to how gekko deals with them). So right now you cannot use that in combination with gekko...

I wrote since a long time my own strategies.. Thank you
If you write your own you only need talib if you want to add talib indicators to your method.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Allow tl.where to select pointers

That looks good! I think test_where could even be generalized to something like _test_ternary (similar to _test_binary). Also, we probably need a better way to test pointer operands in operations (either for expected error message or correctness). Maybe a more generic way to test pointer would be  to have something like dtypes + ['bfloat16', 'float32*'] with numpy_random using int64 instead of pointers, and the kernel converting to_from int64 around the operations.
On another note, we should probably declare dtypes_with_bfloat16 = dtypes + ['bfloat16'] to avoid evaluating this quantity over and over again.

I think test_where could even be generalized to something like _test_ternary (similar to _test_binary), so that we can reuse it in the future if we ever test something that behaves similar to where.

A generic _test_ternay seems hard, as we need to infer the type of the result. Can you think of other use cases of _test_ternary?

Also, we probably need a better way to test pointer operands in operations (either for expected error message or correctness). Maybe a more generic way to test pointer would be to have something like dtypes + ['bfloat16', 'float32*'] with numpy_random using int64 instead of pointers, and the kernel converting to_from int64 around the operations.

Good idea.

On another note, we should probably declare dtypes_with_bfloat16 = dtypes + ['bfloat16'] to avoid evaluating this quantity over and over again.

Good idea!

A generic _test_ternay seems hard, as we need to infer the type of the result. Can you think of other use cases of _test_ternary?

Oh I was thinking it would also be provided as an argument. I don't have any important use case in mind though. Let's just postpone this improvement for now; we can add it later if the need ever arises (e.g., we want to test fma or lop3).

Also, we probably need a better way to test pointer operands in operations (either for expected error message or correctness). Maybe a more generic way to test pointer would be to have something like dtypes + ['bfloat16', 'float32*'] with numpy_random using int64 instead of pointers, and the kernel converting to_from int64 around the operations.

The current approach seems much simpler

With the current approach, it will be hard to test tl.where(cond, ptr, nullptr) since nullptr can't be dereferenced.


Fix typos in the loading datasets docs

This PR fixes two typos in the loading datasets docs, one of them being a broken link to the load_dataset function.

thanks!


How to deal with space in path when execute command in windows?

For example:
Ex.1
c := cmd.NewCommand(`"C:\Program Files\Java\jre1.8.0_192\bin\java.exe" --version`)
    _ = c.Execute()
    fmt.Println(c.Stdout())
    fmt.Println(c.Stderr())

'\"C:\Program Files\Java\jre1.8.0_192\bin\java.exe\"' �����ڲ����ⲿ���Ҳ���ǿ����еĳ���
���������ļ���

Plz focus on the path string. And I don't know why \" instead of "
Ex.2
c := cmd.NewCommand(`C:\Program Files\Java\jre1.8.0_192\bin\java.exe --version`)
    _ = c.Execute()
    fmt.Println(c.Stdout())
    fmt.Println(c.Stderr())

'C:\Program' �����ڲ����ⲿ���Ҳ���ǿ����еĳ���
���������ļ���

Ex.1 and Ex.2 can solve by define the workingDir
Ex.3
When some problem need an arguments with a windows style file with space, the error occurs.
And I didn't find the way to solve it.
Plz help~

@catfishlty I wonder if this could be easily handled with the stdlib path package https://pkg.go.dev/path?

Closing feel free to comment if you're still having this issue. I haven't been able to reproduce.

Thanks for your reply, I'll try it.


Add settings icon to plot

After a plot is added, we currently need to delete it and add it again if we want to change its settings. Add an icon and modal to handle this, e.g. <box-icon name='cog'></box-icon>

Hi Graham,
I've added in the functionality to change plot settings on the fly by reusing the current 'add plot' modal. Changing the plot data appears to work well, but not also the changing of the layout and plot type.
When changing the `colWidth' property the plot does not resize. Changing the height works fine.
When changing the plot type the new plot is drawn on top of the old plot. I think it is because the new plot type function does not have the functionality to properly clear dom elements of other plot types.
Separately: I also noticed that new plots that are added have the `remove plot' buttons by default, and this isn't configurable through the UI. This could be seen to allow a fixed layout to be mixed with plots that can be added/removed on-the-fly, or we can address it in some way.


[ServiceBus] prepare for April 2022 releasse

update release date in CHANGELOG

API change check for @azure/service-bus
API changes are not detected in this pull request for @azure/service-bus


terramate-bin: init at 0.8.3

Description of changes
Latest binary release of Terramate: https://github.com/terramate-io/terramate
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

That was my original goal but there seems to be an issue with v0.4.3+ releases that prevents a successful build via Nix.
From what I can make of the error it appears to be related to a test requiring network access denied by the Nix build sandbox.
I'm not familiar enough with Go or buildGoModule to resolve the issue hence giving users an option to choose a binary release (especially for those using something devbox in CI/CD environments wanting to minimise runtimes).

Would love to get a review so this can be merged and made available to Devbox users.

Result of nix run nixpkgs#nixpkgs-review -- pr 293256 on aarch64 Darwin
1 package built:
terramate-bin
Seems to build and run fine on ARM Darwin

Would love to get a review so this can be merged and made available to Devbox users.

I do not think it makes sense to introduce this package as there is already an terramate package which builds from source and provides binaries through cachenix. I updated the exiting package to 0.8.3 in this PR: https://github.com/NixOS/nixpkgs/pull/310559 Please have a look if this solves your problem of an outdated version.

Appreciate all the feedback and assistance with this PR. Will close in favour of PR 310559


mount --daemon does not work with encrypted config

What is the problem you are having with rclone?
rclone mount does not work when the config is encrypted. It seems that during the daemonization, neither the password or the decrypted config is passed from the parent to the child process. Maybe there can be a mechanism to pass either of them through pipe or environment variables.
What is your rclone version (eg output from rclone -V)
v1.42-062-gf72eade7
Which OS you are using and how many bits (eg Windows 7, 64 bit)
Ubuntu 18.04
Which cloud storage system are you using? (eg Google Drive)
This problem should be there regardless of backend type.
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone mount remote: /mountpoint --daemon
A log from the command with the -vv flag (eg output from rclone -vv copy /tmp remote:tmp)
Aug 01 16:46:47 <hidden> rclone[23920]: rclone: Version "v1.42-062-gf72eade7" starting with parameters ["./rclone" "-vv" "mount" "remote:" "/mountpoint" "--daemon" "--debug-fuse" "--syslog"]
Aug 01 16:46:52 <hidden> rclone[23920]: Using config file from "/home/<hidden>/.config/rclone/rclone.conf"
Aug 01 16:46:54 <hidden> rclone[23920]: remote: Saved new token in config file
Aug 01 16:46:56 <hidden> rclone[23920]: rclone: Version "v1.42-062-gf72eade7" finishing with parameters ["./rclone" "-vv" "mount" "remote:" "/mountpoint" "--daemon" "--debug-fuse" "--syslog"]
Aug 01 16:46:56 <hidden> rclone[23936]: rclone: Version "v1.42-062-gf72eade7" starting with parameters ["./rclone" "-vv" "mount" "remote:" "/mountpoint" "--daemon" "--debug-fuse" "--syslog"]
Aug 01 16:46:56 <hidden> rclone[23936]: Couldn't decrypt configuration, most likely wrong password.
Aug 01 16:46:56 <hidden> rclone[23936]: Failed to read line: EOF

Thanks for reporting this - I've confirmed that it is a problem.
Do you fancy working on a fix?

Thanks for replying. Would like to work on this but I think we need to talk about the solution a bit.
I would propose adding an environment variable RCLONE_CONFIG_KEY (or maybe a better name) and passing the configKey through that variable when daemonizing. This way we don't have to store or pass plain text passwords if users don't want to set RCLONE_CONFIG_PASS. And passing the configKey rather than the decrypted config itself also allows the child process to write back to the file (E.g., when saving a checkpoint for Amazon Cloud Drive).
But of course, the best way to do this should be using a pipe, which is not supported by go-daemon (See https://github.com/sevlyar/go-daemon/issues/19). :(
Would like to hear your opinion on this.

I've had to solve this sort of problem before and an environment variable is a good solution here.
I think we should probably use a variable which won't conflict with normal use, say _RCLONE_CONFIG_PASS or something like that.  The fs/config could export SavePassToEnv and LoadPassFromEnv which manages it.  For security we should delete the var from the environment once it is loaded.

Okay, I've pushed a first commit for this issue. configKey is passed to the child now and --daemon is working with encrypted config. But we may be having some problems with unsetting the environment variable: It seems that calls like os.Unsetenv("_RCLONE_CONFIG_KEY") can't remove the variable from a user's easy reach, for example /proc/$PID/environ.

Okay, I've pushed a first commit for this issue. configKey is passed to the child now and --daemon is working with encrypted config.

Nice

But we may be having some problems with unsetting the environment variable: It seems that calls like os.Unsetenv("_RCLONE_CONFIG_KEY") can't remove the variable from a user's easy reach, for example /proc/$PID/environ.

You are right - that is unexpected by me, but seems to be the way it works.
It is posssible to change /proc/PID/environ but not particularly easy from Go in a cross platform way.
We could use config.Obscure and config.Reveal to mask the password in the environment which would be better than nothing...
Pipes would be nice here wouldn't they!

I have changed to obscure.Obscure now. It is almost no better than base64, though. :(
Have also commented in the go-daemon repo to see if it's possible that pipes can be supported soon.

Maybe we can make use of a temporary file. This can be removed more easily.

A temporary file is a good idea - we can pass the name of it in the environment then delete it straight away.  Not 100% secure but better than before I think.  Need to be careful with the perms on the temporary file but ioutil.TempFile does the correct thing.

This is now merged - thank you for your contributino @Cnly :-)


Introduce github.com/motemen/go-cli

after issue of #194
Introduce github.com/motemen/go-cli for subcommand management.

LGTM :+1:


The data for Representing pointclouds with WIRE

Hallo! I want to ask how to convert the .xyz data from the The Stanford 3D Scanning Repository to the .mat data for the experiments in this paper? Could you give me the code for the conversion please? Thank you very much!

Hello, I am also interested in running the 3D experiment. Can you please provide the .mat data or the conversion code?

@danivelikova please check the data folder, we included a 512x512x512 occupancy volume of Thai statue
@Aiolus-X please check below a simple script that generates mat files from ply files. Hope that helps!
#!/usr/bin/env python

import sys
import numpy as np
from scipy import io

# Please add the path to ACORN github repository:
# https://github.com/computational-imaging/ACORN
sys.path.append('/path/to/ACORN/repository')

# ACORN imports
import dataio

def main(expname, res=512):
    expname = 'thai_statue'             # Name of the ply file
    res = 512                           # Size of the occupancy volume (res, res, res)

    print('Loading mesh dataset')
    ocd = dataio.OccupancyDataset('../data/ply/%s.ply'%expname,
                                  nsamples=0, res=res)

    axis_coords = np.linspace(-1, 1, res)
    X, Y, Z = np.meshgrid(axis_coords, axis_coords, axis_coords)

    coords = np.hstack((X.reshape(-1, 1),
                        Y.reshape(-1, 1),
                        Z.reshape(-1, 1)))

    print('Evaluating occupancy')
    occupancy = ocd.evaluate_occupancy(coords)

    occupancy = occupancy.reshape(res, res, res)

    print('Saving data')
    mdict = {'hypercube': (occupancy*255).astype(np.uint8)}

    io.savemat('%s_%d.mat'%(expname, res), mdict)

hello!
I want to know that have you ever tried to reconstruct surface directly from point clouds?  Just like SIREN does.
I changed your code to follow SIREN's sample approach, i.e., F(x) = 0 if x is the point of the input point clouds, abs(F(x)) > 0 if x is arbitrary spatial point. And use the eikonal loss. (The same way as SIREN). However, I find it did not converge.  I follow your setting in wire_occupancy.py,
omega0 = 10.0
sigma0 = 40.0
Can you give some advice? Thanks!

@csyhping thank you for catching that. I did modify the OccupancyDataset function as followns.
class OccupancyDataset():
    def __init__(self, pc_or_mesh_filename, nsamples=20000000, res=2048):
        self.intersector = None
        self.kd_tree = None
        self.kd_tree_sp = None
        self.mode = None

        if not pc_or_mesh_filename:
            return

        print("Dataset: loading mesh")
        self.mesh = trimesh.load(pc_or_mesh_filename, process=False, force='mesh', skip_materials=True)

        def normalize_mesh(mesh):
            print("Dataset: scaling parameters: ", mesh.bounding_box.extents)
            mesh.vertices -= mesh.bounding_box.centroid
            mesh.vertices /= np.max(mesh.bounding_box.extents / 2)

        normalize_mesh(self.mesh)

        self.intersector = inside_mesh.MeshIntersector(self.mesh, res)
        self.mode = 'volume'

        print('Dataset: sampling points on mesh')
        if nsamples > 0:
            samples = trimesh.sample.sample_surface(self.mesh, nsamples)[0]

            self.kd_tree_sp = spKDTree(samples)

    def __len__(self):
        return 1

    def evaluate_occupancy(self, pts):
        # We will need to batch the query process as it is causing memory out
        # errors
        batchsize = int(1e6)
        npts = pts.shape[0]
        occupancy_list = []
        for b_idx in tqdm(range(0, npts, batchsize)):
            b_idx2 = min(npts, batchsize+b_idx)
            pts_sub = pts[b_idx:b_idx2, :]
            query_sub = self.intersector.query(pts_sub).astype(int).reshape(-1, 1)
            occupancy_list.append(query_sub)

        occupancy = np.vstack(occupancy_list)
        return occupancy

I sampled a total of 1024x1024x1024 points. It does take a lot of time, but fortunately it is a one time operation. Hope that helps!

For obtaining metrics like IoU, I think 512 and 1024 are similar. However, I find that a 1024 cube visually has lot more details than 512. That also explains why I used 1024 for all visual results, and 512 for metrics comparison. Hope that helps!


Use systemd on Fedora

Systemd units should be used on Fedora.
Fedora has supported systemd since Fedora 15.

Updated since https://github.com/William-Yeh/ansible-prometheus/commit/416679576cc4ff208c4c34a20bd747c16597446c
Thank you.


Byte-range support for iOS compatibility

There were already a few discussions about supporting Byte-range (content-range / partial-range) a few years ago. For now, tus and tusd don't implement support for it, which is understandable in the respective context:

https://github.com/tus/tus-resumable-upload-protocol/issues/2: "Range" vs. "Content-Range"
https://github.com/tus/tus-resumable-upload-protocol/issues/116: Upload-Offset vs Range?
https://github.com/tus/tusd/issues/296: Upload to tusd behind HTTPS reverse proxy disconnects with EOF

The decision to not support Byte-range leads to another nasty side-effect on our "favourite" mobile operating system iOS: Media files (audio / video) stored on tus can not be played on iOS!

HTTP servers hosting media files for iOS must support byte-range requests, which iOS uses to perform random access in media playback. (Byte-range support is also known as content-range or partial-range support.) Most, but not all, HTTP 1.1 servers already support byte-range requests.

This renders tus unusable for e.g. storing video / audio notes through a mobile app and enabling the user to play the respective files without downloading them in advance.

I can understand that this is an inconvenience for you but tusd is not intended to serve content. Just as the tus protocol itself, tusd was built for handling file uploads and not file downloads. This decision helps us keep tusd maintainable and focused on one specific thing (which are file uploads in our case). For handling file downloads there are already other tools which take care of this job a lot better than we could. If you save files on disk, we recommend using nginx or some other proxy. If you use the S3Store or GCSStore, you can download the content from the bucket directly. In all of those cases, the byte ranges should be supported.

You can also support byte-ranges in your GET endpoint, which tus does not document and you are thus free to implement your required functionality. IOS players need not even be aware of the POST / PATCH / etc endpoints tus creates.

Yes, you are correct, @RubenGarcia. The tus protocol does not prevent the support of byte range requests. However, supporting this feature is not in line with the goals that we have/had for tusd. We want tusd to focus on uploads and not on downloads, which it is not optimized for.

That's what I'm saying.
I meant beevelop can support byte-ranges in non-tus mandated endpoints.
I did not mean for the tus protocol to be modified.
You (Acconut) can add something like this to the documentation: "The definition of download endpoints is outside of the scope of the tus protocol", if it is not written explicitly there yet.

Thanks for the clarification, @RubenGarcia. In that case, I misunderstood your comment :)


feat: Added cloudwatch log group skip_destroy and log_group_class

Description
Adds skip_destroy and log_group_class for the cloudwatch log groups.
Motivation and Context
Adds skip_destroy and log_group_class for the cloudwatch log groups.
Breaking Changes
No.
How Has This Been Tested?

[ ] I have updated at least one of the examples/* to demonstrate and validate my change(s)
[x] I have tested and validated these changes using one or more of the provided examples/* projects

[x] I have executed pre-commit run -a on my pull request

This PR is included in version 6.7.0 :tada:


ROS bag sample

Hi, I'm a newer here. Could you please include that "NOISY_spin_2.bag" file into your project for us to have a quick start?

Hi, the datasets we used for the demo page are available here. Hope this helps!
https://github.com/udacity/didi-competition
https://projects.csail.mit.edu/stata/downloads.php


WIP signals: initial implementation

Signed-off-by: Jiri Kuncar<EMAIL_ADDRESS>

Integrated as part of #19.


Use touch events for iOS platforms instead of point events

The "Scribble" feature of iOS intercepts point events. So that we can lose some of them when tapping rapidly. We should use touch events for iOS platforms according to https://developer.apple.com/forums/thread/664108 and https://stackoverflow.com/questions/64314226/ipados-14-apple-pencil-fast-tapping-not-working-html-javascript-ontouchstart/64316781#64316781.
I've tested this solution on iPad Air 2020 with Apple Pencil. It works right.
closes #518

Is there some other way to detect the pencil instead of changing this for anyone on a mac?

I was thinking about it but didn't find another solution.
It's only possible to detect the type of input from a user after an event was fired. For the Point Event there is event.pointerType and event.touches[0].touchType for the Touch Event. But we want to know about it before the first event. If I'm right it's not possible.
The code /Macintosh/.test(navigator.userAgent) && 'ontouchstart' in document returns true only for iOS, for MacOS this code returns false because there is no ontouchstart in the document object.


boards: Add TDK RoboKit1 for testing Sensors

Has a lot of great sensors on it including a very fast 6 axis IMU,
atmospheric, and time of flight sensors.
This is a fantastic board to test sensors and algorithms on.
Signed-off-by: Tom Burdick<EMAIL_ADDRESS>

Removed the ADC from the board support yaml for now to remove (hopefully) the remaining CI error.


[SPARK-8558][BUILD] Script /dev/run-tests fails when _JAVA_OPTIONS env var set

Can one of the admins verify this patch?

Jenkins, this is ok to test.

Merged build triggered.

Merged build started.

Test build #35560 has started for   PR 6956 at commit ad577d7.

Test build #35560 has finished for   PR 6956 at commit ad577d7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merged build triggered.

Merged build started.

Test build #35576 has started for   PR 6956 at commit cd455ef.

Merged build triggered.

Merged build started.

Test build #35580 has started for   PR 6956 at commit 7d781a0.

Test build #35576 has finished for   PR 6956 at commit cd455ef.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test build #35580 has finished for   PR 6956 at commit 7d781a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM

Merged build triggered.

Merged build started.

Test build #35718 has started for   PR 6956 at commit 31b6edc.

Test build #35718 has finished for   PR 6956 at commit 31b6edc.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Thanks for updating.  LGTM, so I'm merging this into master.


pipenv doesn't understand some version markers

Pipenv fails to parse some python version markers
given this Pipfile:

[[source]]
name = "pypi"
verify_ssl = true
url = "https://pypi.python.org/simple"

[packages]

[dev-packages]
coverage = "*"

[requires]
python_version = "3.5"

when running pipenv internally runs resolver.py it fails because it is unable to properly parse the version markers of the coverage packages.
so given that Pipfile if I run pipenv lock it crashes (exit code 1) because  resolver.py fails
here is part of the output from running pipenv lock --verbose
                         ROUND 16
Current constraints:
  coverage==4.5.1

Finding the best candidates:
  found candidate coverage==4.5.1 (constraint was ==4.5.1)

Finding secondary dependencies:

New dependencies found in this round:
Removed dependencies in this round:
  removing ['coverage', '==4.5.1', '[]']
Unsafe dependencies in this round:
------------------------------------------------------------
Result of round 16: not stable

INFO:pip9._vendor.requests.packages.urllib3.connectionpool:Starting new HTTPS connection (1): pypi.python.org
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment
INFO:notpip.req.req_set:Collecting coverage==4.5.1
INFO:pip9.download:File was already downloaded /home/afoa/.cache/pipenv/wheels/coverage-4.5.1-cp35-cp35m-manylinux1_x86_64.whl
WARNING:notpip.req.req_set:Ignoring coverage: markers 'python_version == ">=2.6,!=3.0.*,!=3.1.*,!=3.2.*,<4"' don't match your environment

environment:

Pipenv version: `'11.8.3'`

Pipenv location: `'/usr/local/lib/python3.5/dist-packages/pipenv'`

Python location: `'/usr/bin/python3'`

Other Python installations in `PATH`:

  - `2.7`: `/usr/bin/python2.7`
  - `2.7`: `/usr/bin/python2.7`
  - `3.5`: `/usr/bin/python3.5m`
  - `3.5`: `/usr/bin/python3.5`

  - `2.7.12`: `/usr/bin/python`
  - `2.7.12`: `/usr/bin/python2`
  - `3.5.2`: `/usr/bin/python3`

PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '3.5.2',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '4.4.0-1050-aws',
 'platform_system': 'Linux',
 'platform_version': '#59-Ubuntu SMP Tue Jan 30 19:57:10 UTC 2018',
 'python_full_version': '3.5.2',
 'python_version': '3.5',
 'sys_platform': 'linux'}

System environment variables:

  - `XDG_SESSION_ID`
  - `BYOBU_DARK`
  - `BYOBU_PREFIX`
  - `BYOBU_READLINK`
  - `BYOBU_ACCENT`
  - `BYOBU_BACKEND`
  - `SSH_CONNECTION`
  - `SSH_AUTH_SOCK`
  - `PYTHONUNBUFFERED`
  - `BYOBU_SED`
  - `BYOBU_HIGHLIGHT`
  - `BYOBU_WINDOW_NAME`
  - `BYOBU_TTY`
  - `BYOBU_CONFIG_DIR`
  - `XDG_RUNTIME_DIR`
  - `NO_NPM_FEEDBACK`
  - `LANG`
  - `TMUX`
  - `OLDPWD`
  - `_`
  - `EVENT_NOEPOLL`
  - `PYTHONDONTWRITEBYTECODE`
  - `MAIL`
  - `LOGNAME`
  - `BYOBU_CHARMAP`
  - `GOPATH`
  - `SHLVL`
  - `BYOBU_TIME`
  - `NO_FANMGMT_CLEAN`
  - `FB_USER_ID`
  - `BYOBU_LIGHT`
  - `PS1`
  - `GOBIN`
  - `TERM`
  - `SSH_TTY`
  - `DEVLOCAL`
  - `BYOBU_PAGER`
  - `NO_VE_FEEDBACK`
  - `PIP_PYTHON_PATH`
  - `PATH`
  - `HOME`
  - `BYOBU_ULIMIT`
  - `BYOBU_RUN_DIR`
  - `PWD`
  - `TMUX_PANE`
  - `BYOBU_DISTRO`
  - `BYOBU_DATE`
  - `SHELL`
  - `USER`
  - `SSH_CLIENT`
  - `BYOBU_PYTHON`

Pipenv–specific environment variables:

Debug–specific environment variables:

  - `PATH`: `/home/afoa/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin:/opt/go/bin`
  - `SHELL`: `/bin/bash`
  - `LANG`: `en_US.UTF-8`
  - `PWD`: `/home/afoa/projects/test`

---------------------------

Contents of `Pipfile` ('/home/afoa/projects/test/Pipfile'):

toml
[[source]]
name = "pypi"
verify_ssl = true
url = "https://pypi.python.org/simple"

[packages]

[dev-packages]
coverage = "*"

[requires]
python_version = "3.5"

</details>

I tried to debug the issue, the code responsible for parsing the version markers is running under notpip

Did you manage to find what notpip thinks your environment (the one not matching the markers) is?

it is either the evaluation logic not handling this marker properly. or the logic that parses the markers (loaded from the coverage package) doesn't parse it correctly.
basically, it tries to use the equals operator and the rhs of the expression is >=2.6
so it fails because the comparison being made is basically "3.5" == ">=2.6"

@asherf I've typically seen errors pop up like this when there are conflicts between the installation path of pipenv and python (e.g. /usr/bin and /usr/local/bin) where the latter doesn't have the former on its search path.  Does it work if you invoke with python3 -m pipenv install?

/usr/local/bin/pipenv
pnw-dev-afoa~/projects/test:yoyoma$ which python3
/usr/bin/python3

yep. that seems to be the case.
running it like you suggested (w/ lock not install pipenv command) yields the same result.
however, I don't see a python interpreter in /usr/local/bin/

No there wouldn't be, can you run pipenv lock --clear --verbose or pipenv-resolver --clear --verbose coverage? If you're still having an issue I'd recommend uninstalling pipenv and installing it in user isolation from master: python3 -m pip uninstall pipenv && python3 -m pip install --user --no-cache-dir --ignore-installed -e git+https://github.com/pypa/pipenv.git#egg=pipenv and then make sure you have ~/.local/bin on your $PATH: export PATH="$HOME/.local/bin:$PATH" and see if you

@techalchemy sounds good. I'll try that.

Sorry for the trouble & thanks for jumping through these hoops!

@techalchemy the solution you suggested solved the problem...
so feel free to close this issue... it is still weird to me that in certain scenarios the package markers are not parsed correctly... but then again... python packaging 🤷♂

@asherf we actually had a bug in our resolver (fixed in #1808) which I suspect was the culprit here :+1:  thanks for your help!


Move GITHUB_BASE definition to buildlib

Test run with custom job: https://saml.buildvm.hosts.prod.psi.bos.redhat.com:8888/job/hack/job/dpaolell/job/custom/56/console

Thanks. Let's try it.


How can we get the progress of the request?

Currently there is no easy way of getting the progress. It's one of the features I'm thinking about to implement, but not in next future.
In the meantime, if it's really important for you, you could do following:
Create an intercepting InputStream which counts the number of read-calls (or bytes read). Wrap your real InputStream with this intercepting stream and give this to DavidWebb as body of the request. Your interception can now track the progress.
What do you use as body? byte[], File, InputStream, String, ...?

I see. Thank you. I am using an InputStream for the body.

Do you know the length in advance? Then you could have a look at ProxyInputStream (as an example) and let this stream call you back when bytes are read.
Obviously without the length you can just report the number of bytes transferred, but not the percentage.
I'll leave this issue open as an enhancement request, because this is one of the features requested most often.


WIP: An initial gateway implementation

The initial implementation uses PyZMQ and JeroMQ in the ZMQ_DEALER mode that allows a single socket to be used for non-blocking bidirectional communication between two nodes with a certain buffer control until the calls become blocking (1000 pending messages on my machine).
Closes #107, the JARs are loaded through a Java SE ServiceLocator mechanism.

@rssouza feel free to add more commits here! The ZMQ part is working OK. What has to be done:

[ ] Send and receive messages in separate threads to avoid hitting the ZMQ buffer "water mark"
[ ] Either switch the code to use msgpack or switch the Gateway spec to use JSON (we'll have to do base64 encoding of the msgBody in that case and I'd prefer to avoid that)
[ ] Define a Java interface for the loaded services
[ ] Wrap the backend in an OSLC Server
[ ] Implement service loading on the backend
[ ] Expose a TRS Server on the Gateway
[ ] Package the Backend as a Docker image that GW Frontend developers can build their images FROM

@likelion would be great if you can review this PR but it's too raw at this stage, I will ping you when it's ready.

Also, not sure if the ZMQ_PAIR is a better option than the ZMQ_DEALER.

@likelion @rssouza the last commit includes my initial shot at loading OSLC resource classes as well as the (un)marshalling classes dynamically via classpath. I think the general concept is ready for your design review. I will chat with @jadelkhoury tomorrow how can we build an OSLC server dynamically from that.

@berezovskyi Looks good to me, pretty straight-forward, I didn't try to run it though. Maybe a Dockerfile would be helpful here...

@likelion a few Dockerfiles are coming! But first I need to turn the backend into a webapp. Just had a good chat with @jadelkhoury and we narrowed the scope on it pretty well.

@likelion the deploy is fixed now.
But we have been hit by #150 after JAX-RS 2.0 supported was merged into master in Lyo.

@rssouza I rebased this on master and squashed some commits. If you wish, we can merge this now is and open a new issue for the TODOs. Or, if you think there is no risk of merge conflicts later, we can keep it open until we have something more functional.


Update CLI to use Knack 0.6.2 (preview mechanism)

Closes #5969.
Updates the CLI to use the latest knack.

Removes the command suggestion code since it now happens in knack Turns out there is CLI-specific logic in the spellchecker so I have to keep the logic in place. It just means that knack now has a limited implementation of this feature (it doesn't handle values)
Uses the Preview status tag from the latest knack to annotate commands, groups, and arguments in preview.
Deprecates and hides BatchAI commands (service is being retired)
Hides already deprecated ACS commands.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[X] I adhere to the Command Guidelines.

Adding DNM label so we can consider the strategy for existing preview modules more fully before we release this. However, now that the mechanism is done, this should unblock @marstr from his packaging work.


Label for md-radio-group

Bug, feature request, or proposal:

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

What is the expected behavior?
We need some built-in means to add labels (probably, not only for md-radio-group) when needed.
What is the current behavior?
There is no built-in way to give a label to a md-radio-group. You have to add, lay out and style HTML label, span or div by yourself.
What are the steps to reproduce?
Using a sample layout:
Sort by
<md-radio-group>
    <md-radio-button value="1">Date</md-radio-button>
    <md-radio-button value="2">Status</md-radio-button>
    <md-radio-button value="3">From</md-radio-button>
    <md-radio-button value="4">To</md-radio-button>
</md-radio-group>

Leads to an un-styled label:

What is the use-case or motivation for changing an existing behavior?
Many times we want to label a md-radio-group, but don't have built-in means to do so.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
"@angular/material": "2.0.0-beta.11"

Perhaps if we implement #7891, it'll work for radio-group as well.

A quick solution for that, is using a mat-list and the [mat-subheader], like so:
<mat-list>

Label for RadioGroup

    <mat-radio-group class="example-radio-group" [(ngModel)]="favoriteSeason">
    <mat-radio-button class="example-radio-button" *ngFor="let season of seasons" [value]="season">
      {{season}}
    </mat-radio-button>
  </mat-radio-group>
</mat-list>

Eq: https://plnkr.co/edit/k73FSy?p=preview
PS: You might need a little of style for your mat-radio-group and mat-radio-button.
.example-radio-group {
    display: inline-flex;
    flex-direction: column;
  }

  .example-radio-button {
    margin: 5px 16px;
  }

I had the same problem and created a simple component that leverages the functionality provided by the MatFormField component.
You can use it like this:
<radio-group-form-field>   <mat-label>Favorite Color</mat-label>   <mat-radio-group formControlName="favoriteColor" required="true">     <mat-radio-button value="1">Red</mat-radio-button>     <mat-radio-button value="2">Green</mat-radio-button>     <mat-radio-button value="3">Blue</mat-radio-button>   </mat-radio-group>   <mat-hint>The gender hint</mat-hint>   <mat-error *ngIf="testForm.controls['favoriteColor'].errors && !testForm.controls['favoriteColor'].untouched">     A favorite color is required.   </mat-error> </radio-group-form-field>
radio-group-form-field.ts.txt

@marcusportmann anyone use the radio-group-form-field in angular 11? I'm trying to resolve the incompatibilities myself.

@marcusportmann anyone use the radio-group-form-field in angular 11? I'm trying to resolve the incompatibilities myself. I've gotten close(?)...currently getting:
ERROR TypeError: Cannot read property 'errorState' of undefined
    at MatFormField_HostBindings (form-field.js:824)
    at definition.hostBindings (core.js:12380)
    at processHostBindingOpCodes (core.js:8947)

Please do not use this issue for problems or bugs. File a new bug via the issue template or use Stack Overflow to get an answer to your problem.

check out a newer version: https://github.com/marcusportmann/inception/tree/master/src/inception-angular/projects/ngx-inception/src/lib/core/components


classes in dataset and verbalizer are different

I notice that in the dataset, 0 means unmatched and 1 means matched.
But in verbalizer, 0 means matched and 1 means unmatched. Do you notice this difference?
In prompt.py
classes = [
"yes",
"no",
]

@Peng-fei-Wang @Zeng1998

Hello, @lihuiliullh. We are dealing with it and will notify you know when we have the results.


Vite chokes outputting sourcemaps for modules with query parameters when there are certain kinds of plugins outputting sourcemaps from transform

Describe the bug
Using @rollup/plugin-replace with a web worker imported using ?worker causes sourcemaps to break.
Note that transform callbacks are allowed to return source maps with sources & sourcesContent not set correctly, e.g. [null], & rollup is supposed to correct the other fields, only really looking at mappings, names AFAIK.
See https://rollupjs.org/plugin-development/#source-code-transformations
Originally reported here, but pinpointed to Vite:

https://github.com/Rich-Harris/magic-string/issues/238
https://github.com/rollup/plugins/issues/1422

cc @YossiSaadi
Reproduction
https://github.com/segevfiner/vite-worker-sourcemaps-bug
Steps to reproduce

Run pnpm install & pnpm dev.
The sourcemaps for worker.ts and test.js are borked. Pointing to null as the source file, Vite also spews Sourcemap for "/Users/segevfiner/junk/vite-worker-sourcemaps-bug/src/worker.ts" points to missing source files.

System Info
System:
    OS: macOS 13.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 105.47 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.19.0/bin/yarn
    npm: 9.4.0 - ~/.nvm/versions/node/v16.19.0/bin/npm
  Browsers:
    Chrome: 109.0.5414.119
    Safari: 16.3
  npmPackages:
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    vite: ^4.0.0 => 4.1.0-beta.1

Used Package Manager
pnpm
Logs

Click to expand!
Sourcemap for "/Users/segevfiner/junk/vite-worker-sourcemaps-bug/src/worker.ts" points to missing source files
  vite:sourcemap Missing sources:
  vite:sourcemap   /Users/segevfiner/junk/vite-worker-sourcemaps-bug/src/worker.ts?type=module&worker_file +0ms

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This happens to me using @rollup/plugin-replace in a regular .js file (not web worker) and without a ? in the url

Taking a second look, this seems to be fixed by #13662.


Add support for alpaca

How hard would it be to add support for the alpaca model (usage below)
https://github.com/ggerganov/llama.cpp/blob/master/alpaca.sh

Very easy - just replace the Cmd command in server.go.
https://github.com/avilum/llama-saas/blob/master/server.go#L21
It should be as simple as that.
Let me know if you managed to run it 🙏🏻


whats the Querry for the Predicted Segmentation Mask?

thank you for you modifications
i have change the line of 46 " x_train, y_train, batch_size=args.batch_size" with " x_train, y_train, batch_size=args.batch" and then also make modification in line 120 "result = model.evaluate(x,batch_size=args.batch)" but i am getting the namespace error. Yes i want to get the predicted Segmentation masks.

Hi, the code has been updated to support saving of segmentation results (masks), please follow the instructions in README.md and try again:)
You don't need to change any code at this point. If there is still a problem, please let me know! Thanks


Synchronize spool and preform motor

Calculate and program the speed at which both motors need to spin so that the preform is lowered at the right speed. If this timing is wrong, the fiber could break or be eneven.
We need to measure the linear speed of the preform motor so Joy can do the calculations.

Put the excel sheet for the calculations on the wiki


Repo description

Please set proper description.
Consider Microsoft PHP drivers for SQL Server
Setting the URL would be nice https://msdn.microsoft.com/en-us/library/dd903047(SQL.11).aspx

These can be done - with proper rights - on the top of this page: https://github.com/Microsoft/msphpsql

Thank you.
--
+36204242498
Ezen a készüléken sok az elütés.
Elnézést!
On November 10, 2016 1:54:11 AM CET, Meet Bhagdev<EMAIL_ADDRESS>wrote:

Closed #165.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/Microsoft/msphpsql/issues/165#event-853819332


Add backward support for complex abs and angle

Add backward support for complex abs and angle for Type 1 complex tensor

Merged to main #7289


Added a number to repeated logs

Repeated logs/warnings/errors now show how many times they have been repeated as described in #25 .

I also removed _showDebug = false; in GameLogger.LogWarningImpl since it closed the debug console every time a warning was printed, which doesn't seem right.
PS: This is my first PR, so I hope I didn't mess anything up.
I've been really enjoying working with this engine.

This works great, thank you!


Feature request: add support for placeholder

It would be great if the input field would support the placeholder tag?
Example

<input` type="text" name="fname" placeholder="First name">

Check the docs on inputAttrs to set that in the readme


invalid number error

I am trying to insert the following into influxDB
RealQuotes,Symbol=AAPL,Quote_Time=1592937025071 Trade_Time=1592937023359,Last_Price=370.1999,Total_Volume=38349566,Exchange_ID=NASDAQ,Volatility=0.0085,Security_Status=Normal,Reg_Market_Trade_Time=1592937023359
First I am getting an invalid number error.  Can anyone help?
Mu influxDB version is 1.8.0
Thanks!

@lramnath your line protocol isn't valid. How are you hoping to structure the data in InfluxDB? What are the fields? What are the tags?


LW-11521 be-v0.30.1

Context
The asset-projector has some performances issues.
Proposed Solution
Added an index to reduce SQL queries weight.
Important Changes Introduced
Minor query refactoring to remove a JOIN.

How are we releasing this? merging it to release branch? new release off master?

Some problems with the workflow, makes this PR not approvable.


Fix veteran attack strength calculation and let defending units gain veteran status upon winning

Thank you for this.

I'm glad I could help!

I got a compile error: The compile could not convert "1.5" from double to int. I've created an alternative solution.

Okay.  Thanks.


Missing fixed attributes in Thermostat (CON-1126)

Attributes 3, 4, 5, 6, 20, 21, 22, 35, 36, 38, 39 on the Thermostat cluster are all fixed.
Does this need a mfg_tool update to set them?

Feature map support isn't right.
Attrib 10 is not getting made !LTNE
Attrib 13, 14 not getting made COOL & OCC, HEAT & OCC
so on for 15, 16, 17, 18, 19, 1a, 34, 37

@jonsmirl Thanks for the report! I'll take a look and update.

@jonsmirl We are expecting application should add HEAT, COOL feature first before adding other features

Attributes 13, 14 are getting created on occupancy feature .
Attributes 15, 16, 17, 18 are optional for HEAT and COOL feature so we are not creating them by default
Attribute 19 is created with AUTO feature.
1a is optional
34, 37 are created in setback feature.

Attrib 10 is not getting made !LTNE

I'll add support for LTNE feature, but will not create attribute 10 by default since its conformance is optinal.

I haven't seen your solution yet for fixed attributes in code.
Maybe for fixed attributes in code when you create the cluster or turn on the feature, you have to include the fixed attributes as parameters?

I missed turning occupancy on in my code. I am just trying to turn everything on to ensure that all of the attributes appear.

Don't fixed attributes set from code need to look something like this? You have to supply the fixed attributes when the cluster is created.
cluster::thermostat::create(epThermo, &thermo_config, CLUSTER_FLAG_SERVER, cluster::thermostat::feature::cooling::get_id()
                    | cluster::thermostat::feature::setback::get_id(fixed values) | cluster::thermostat::feature::heating::get_id(fixed values)
                    | cluster::thermostat::feature::occupancy::get_id(fixed values)
                    | cluster::thermostat::feature::schedule_configuration::get_id(fixed values), fixed values);

Turning on occupancy didn't change anything, these are the attributes reported to a wildcard subscription. Don't know what FFFC is reporting so many times.
I (1682101) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682102) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682103) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682104) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFD is 6 **********
I (1682105) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682106) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000000 is null **********
I (1682108) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682279) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682280) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000001B is 4 **********
I (1682281) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682282) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000001C is 1 **********
I (1682284) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682285) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000012 is 2000 **********
I (1682286) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 3 **********
I (1682287) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000011 is 2600 **********

LTNE feature is missing in esp_matter_feature.h
The cluster code is not creating all of the features
https://github.com/espressif/esp-matter/blob/main/components/esp_matter/esp_matter_cluster.cpp#L1541
Missing occupancy, schedule, setback, auto, ltne

I added code to force all on of the features except LTNE (missing).
Something is wrong in the CHIP layers, the feature map is reporting as 63.  Briefly looking, the CHIP cluster code makes no mention of the Occupancy, Schedule and SetBack features. So something is missing inside CHIP.
I (357060) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000FFFC is 63 **********

But when I print it from the esp-matter code it is 3f which is what I set it to.
JDS features 3f
W (989) esp_matter_core: Command 0x00000000 on cluster 0x00000201 already exists. Not creating again.

I am sending in 3F for the feature map and I see these attributes. So seven missing 7, 8, 10, 15, 16, 17, 18. Plus what to do with fixed. Plus these will all need to be audited for correct default values.
I (583302) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000000 is null **********
0x0001 Optional
I (583490) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000002 is 1 **********
0x0003 Fixed
0x0004 Fixed
0x0005 Fixed
0x0006 Fixed
0x0007 Missing (Cool)
0x0008 Missing (Heat)
0x0009 Deprecated
0x0010 Missing (!LTNE)
I (583482) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000011 is 2600 **********
I (583480) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000012 is 2000 **********
I (583492) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000013 is 2600 **********
I (583494) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000014 is 2000 **********
0x0015 Missing (Heat)
0x0016 Missing (Heat)
0x0017 Missing (Cool)
0x0018 Missing (Cool)
I (583505) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000019 is 25 **********
0x001A Optional
I (583303) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000001B is 4 **********
I (583305) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x0000001C is 1 **********
0x001D Optional
0x001E Optional
0x001F Fixed
I (583500) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000020 is 0 **********
I (583502) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000021 is 0 **********
I (583503) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000022 is 0 **********
0x0023 Optional
0x0024 Optional
0x0025 Optional
skip
0x0029 Optional
0x0030 Optional
0x0031 Optional
0x0032 Optional
skip
I (583485) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000034 is null **********
I (583486) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000035 is null **********
I (583488) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000036 is null **********
I (583495) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000037 is null **********
I (583497) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000038 is null **********
I (583498) esp_matter_attribute: ********** R : Endpoint 0x000A's Cluster 0x00000201's Attribute 0x00000039 is null **********
0x003a Optional
0x0040 Optional
0x0041 Optional
0x0042 Optional
0x0043 Optional
0x0044 Optional
0x0045 Optional
0x0046 Optional
0x0047 Optional

Another oddity, I see 11,12,13,14 on the wire, but I am only receiving reports for 11,12 in my app. So it is filtering the '& OCC' ones. I suspect that is related to the CHIP stack reporting 63 for my feature map when I have 3F set.  Something is wrong in the CHIP featuremap bits for this cluster. 63 is missing the bit for the OCC feature.

@jonsmirl By default we are creating MANDATORY attribute, commands, features in Esp-Matters component. Inside the feature_create we are creating MANDATORY things only. If you want anything that is optional in spec, you have to add them in the application using attribute_creater APIs.
And for the fixed attributes, every cluster_create API have config with them where you can pass your values while creating cluster as we did in light example.

Missing occupancy, schedule, setback, auto, ltne

You can use add APIs to create the features. Also I have added LTNE feature its in internal review.

I see I was miss reading some of the optional flags. So will have to add of those as needed myself.
63 and 3F look to be the same.
It needs this:
diff --git a/components/esp_matter/esp_matter_cluster.cpp b/components/esp_matter/esp_matter_cluster.cpp
index 07b39bb..325a2c2 100644
--- a/components/esp_matter/esp_matter_cluster.cpp
+++ b/components/esp_matter/esp_matter_cluster.cpp
@@ -1547,6 +1547,18 @@ cluster_t *create(endpoint_t *endpoint, config_t *config, uint8_t flags, uint32_
     if (features & feature::cooling::get_id()) {
         feature::cooling::add(cluster, &(config->cooling));
     }
+    if (features & feature::setback::get_id()) {
+        feature::setback::add(cluster, &(config->setback));
+    }
+    if (features & feature::occupancy::get_id()) {
+        feature::occupancy::add(cluster, &(config->occupancy));
+    }
+    if (features & feature::schedule_configuration::get_id()) {
+        feature::schedule_configuration::add(cluster, &(config->schedule_configuration));
+    }
+    if (features & feature::auto_mode::get_id()) {
+        feature::auto_mode::add(cluster, &(config->auto_mode));
+    }

     return cluster;
 }
diff --git a/components/esp_matter/esp_matter_cluster.h b/components/esp_matter/esp_matter_cluster.h
index 7cab92f..7f2952c 100644
--- a/components/esp_matter/esp_matter_cluster.h
+++ b/components/esp_matter/esp_matter_cluster.h
@@ -367,6 +367,10 @@ typedef struct config {
     uint8_t system_mode;
     feature::heating::config_t heating;
     feature::cooling::config_t cooling;
+    feature::occupancy::config_t occupancy;
+    feature::setback::config_t setback;
+    feature::schedule_configuration::config_t schedule_configuration;
+    feature::auto_mode::config_t auto_mode;
     config() : cluster_revision(6), local_temperature(), control_sequence_of_operation(4), system_mode(1) {}
 } config_t;

Thank you!!! Changes will be out soon...

Next, I am trying to figure how to implement binding of remote temp sensors. This is where I need loopback binding to work since my temp sensors can be bridged onto the thermostat node. My temp sensors are BLE based, Thread temp sensors have awful battery life. The bridge code turns the BLE temp sensor into a Matter one. https://github.com/espressif/esp-matter/issues/904

@jonsmirl Fixed with c47b98b. Please close the issue. Lets track binding issue on #904.


Correct spelling error in README.md

updating README.md will not be entertained.

No worries - but there is a spelling error in your README.md.

👍


ci: Do not run release and stale flows on forks

release.yml runs on push to master, and stale.yml runs on schedule. Both workflows should not be run on forked repositories. The credentials and permissions are missing, resulting in tons of failed runs (including email notifications):

[fork/react-native-device-info] Run failed: Mark stale issues and pull requests - master (808c1b5)

Not exactly sure what you're referring to.. All this PR does is update the two mentioned GitHub Actions workflows, so that they don't run in forked repositories anymore (and cause errors).

General info on the GitHub Actions API etc is available here:
https://docs.github.com/en/rest/reference/actions

Not exactly sure what you're referring to.. All this PR does is update the two mentioned GitHub Actions workflows, so that they don't run in forked repositories anymore (and cause errors).

I was just curious where in the documentation you saw the jazz related to github.event.repository.fork so I could read up on it. To me, the documentation is difficult to find specific things like that.
I found it though, so no worries

Yes, agree, the documentation is a bit lacking in that sense. I've successfully used this check in several repos. For example, you can see here that the release flow was skipped in my fork after I pushed the merged PR to my master branch: https://github.com/friederbluemle/react-native-device-info/runs/4709727033
If (obviously) failed for previous runs: https://github.com/friederbluemle/react-native-device-info/actions/workflows/release.yml
However, I did notice that the stale workflow (which has a "schedule" trigger) still ran, and failed. I'm not sure why, maybe it was still using an older version of the workflow file? I'll keep checking.

As I mentioned above, it turned out that for workflows with a schedule trigger, this check does not work. The reason is the github.event object is not populated the same way as it is in builds started by other triggers. More details here:
https://github.community/t/schedule-workflow-missing-github-event-repository-context/212293
https://github.community/t/github-event-repository-fork-context-does-detect-forks-in-scheduled-jobs/185925
And a fix: #1363