[SPARK-10697][ML] Add lift to Association rules

What changes were proposed in this pull request?
The PR adds the lift measure to Association rules.
How was this patch tested?
existing and modified UTs

Test build #95263 has started for PR 22236 at commit 92c32dd.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2557/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95263/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2558/
Test PASSed.

Test build #95265 has started for PR 22236 at commit 7f052b8.

cc @holdenk @srowen @yanboliang

Test build #95265 has finished for PR 22236 at commit 7f052b8.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95265/
Test FAILed.

@srowen then what about recomputing when reading saved models? This seems a good compromise to me as it saves the writing of the data, it allows having lift for old models, but it doesn't introduce any perf regression when creating a model.
Of course the "terribly expensive" quite depends on how much data there is etc.etc. Anyway, it is a pass on the freqItemset RDD. As it is not cached, it means we have to generate all the possible itemsets and perform an aggregation on them. Maybe that is not the most expensive part of the algorithm, but saving it seems worth to me.

Yeah, I like that idea. Just compute it on initializing the model.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2576/
Test PASSed.

Test build #95294 has started for PR 22236 at commit 957a6a2.

Test build #95287 has finished for PR 22236 at commit 4c8b7be.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95287/
Test FAILed.

Test build #95294 has finished for PR 22236 at commit 957a6a2.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95294/
Test FAILed.

Merged build finished. Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2591/
Test PASSed.

Test build #95314 has started for PR 22236 at commit 88eb571.

Test build #95314 has finished for PR 22236 at commit 88eb571.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95314/
Test PASSed.

just FYI about another related PR: https://github.com/apache/spark/pull/17280
and maybe I should close it? @srowen

thanks for pointing that out @hhbyyh . I wasn't aware of it. I think lift and confidence are more useful metrics than the support (the votes on the JIRAs seem also to agree with me on this). Anyway, after this PR, adding support too would be trivial.
I checked your PR @hhbyyh and if you don't mind I'll take the naming from there as I prefer it over the one I used here. :) Thanks.

@holdenk @srowen anyway I realized that computing the lift for previously saved models is not feasible as we don't know the number of training records, so we cannot compute the items support.
I'll keep the re-computation at read time in order to avoid saving the itemSupport map, but for previous models the lift is going to be null as we cannot compute it. Thanks.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2611/
Test PASSed.

Test build #95341 has started for PR 22236 at commit 44a0021.

Test build #95341 has finished for PR 22236 at commit 44a0021.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95341/
Test PASSed.

Take it and good luck.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2663/
Test PASSed.

Test build #95407 has started for PR 22236 at commit 706303f.

Test build #95407 has finished for PR 22236 at commit 706303f.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95407/
Test PASSed.

Test build #95548 has started for PR 22236 at commit 2407e05.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/2742/
Test PASSed.

Test build #95548 has finished for PR 22236 at commit 2407e05.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/95548/
Test PASSed.

Merged to master


Fixed dimensionality issues in LinearInequalityConstraint implementation

Issue #, if available: #288
Description of changes: Fixed the bug, added some validation and more tests
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks like a hiccup somewhere - the build has completed fine, but wasn't updated here.

Boo I don't have write access anymore so my review doens't count :(


Processing SVF files directly

Loading devices from SVF files with openFPGALoader take forever.
How difficult would it be to take the SVF parsing from openFPGALoader and run it locally on the RP2040?
It would be nice to be able to send a .SVF file into the RP2040 through a virtual UART and process it locally.
Could we use the SVF parsing from openFPGALoader, or should we look for one that already runs on an MCU?

Can you provide some concrete data? How does it compare with bin programming? What JTAG frequency do you use? Do you know where the bottleneck is? Can you share your SVF file? It turns out that the author of openFGPALoader wasn't all positive about enabling SVF support for every FPGA targets because SVF is inherently slow compared to bin programming. The reason is that some delays are typically inserted in places due to programming delays imposed by the hardware. In bin mode, openFPGALoader loops around a read register status until the device is ready. SVF do not allow this so a conservative delay is typically introduced which is always slower than the probe loop.

The board I am using (MAX10 10M08 Evaluation Kit) does does not have bin support for comparison, but the SVF programming takes several minutes for a small device.  I was running at the fastest 16Mbps supported by pick-dirtyJtag.  There may be some potential optimizations like skipping verification of the image.
The way SVF works, it has to check the TDO data for each transaction.  I expect it would be quicker to check the data on the MCU than to send the TDO data back to openFPGALoader for processing.  The other advantage could be the elimination of openFPGALoader.  You could send the SVF file directly to the UART and do all the processing on the pico board.
I may attempt this myself.  I am mostly wondering if you think the openFPGALoader SVF parsing could be ported to the RP2040 since you seem to be familiar with both.  Or would you look for another SVF implementation to port?

I am guessing you are right. SVF checking TDO may be the reason it is slow. However, there must be a generation mode where the generated SVF does not do this. For sure, this shortened Lattice file does not and loads 300KB in a couple of seconds.
bitstream-shortened.zip
As far as SVF parsers go I only know the one in openFPGALoader and it is C++ based. You will have to add the right C++ support libraries. It isn't anything that I would be interested in merging back into this project because it is too specific of a case to be interesting to most users. I would be glad to direct people who could benefit from it to your repo.

I'm not use FPGA at all. But i am facing the same situation. I'm using the OpenOCD, In my case, for read every 4bytes memory, At least, It need send 2 command queues to Pico. I guess it should be 1 for TAP_STATE_MOVE + write IR and 1 for TAP_STATE_MOVE + read DR. The OpenOCD not submit read command in bulk.
In the screenshot, you can see Pico need about ~4ms to processing every command queue. It should explain why dump speed is 0.15kb/s.
Of course, I am using the VMware and the code on Pico is not optimized. But, it will not help too much even the problem is solved. Because of USB send frame every 1 ms. 4ms -> 1ms, 0.15kb -> 0.6kb, not enough.

Besides of make openFPGALoader/OpenOCD running on Pico, I think the most generic way is use MPU to do this. So it no need for modify OpenOCD to really submit command in bulk. Just make a JTAG adapter driver as usual.
ARM core running Linux and OpenOCD, and make MCU core as I/O processor. Use shared memory to exchange data between ARM and MCU. MCU use GPIO bit-bang and SPI to do JTAG. Like the original dirtyJTAG.
I think the shared memory will eliminate the processing/transfer time of every command queue.
I'm already do some test on Rockchip RV1106, MCU can do bit-bang at 1 MHz. Compare to ST/TI, the board is cheap and easy to get.

How about J-Link and other commercial debugger to handle this?
If I use OpenOCD + J-Link, the same result as Pico?
J-Link GDB Server, huge improvement? I guess they really submit command in bulk.

About Jlink and the Jlink GDB server. The microprocessor in the Jlink device handles all of the chatty traffic of the debug protocol. It only sends the results to the gdb server on the USB line.
The reason you get so poor USB utilization is that you need a USB turnaround (send, the receive) every 64 bits of communication between OpenOCD and the adapter. OpenFPGALoader send binary without the need to have a turnaround and I see that the USB bus (FS) is almost totally used up when I use pico dirtyJtag

About Jlink and the Jlink GDB server. The microprocessor in the Jlink device handles all of the chatty traffic of the debug protocol. It only sends the results to the gdb server on the USB line.
The reason you get so poor USB utilization is that you need a USB turnaround (send, the receive) every 64 bits of communication between OpenOCD and the adapter.  Thank you for your explanation.


Webcam Issue

Tested it and works fine. But the cams are only working if both devices are on the same network or wifi/host.
Try to connect both devices from two different networks.

Any updates regarding this?


None of the az cli service property update commands function

The --resource-group arg isn't valid for service-properties update

C:\> az storage blob service-properties update --resource-group yyy --account-name xxx --enable-change-feed
az: error: unrecognized arguments: --resource-group yyy --enable-change-feed
usage: az [-h] [--verbose] [--debug] [--only-show-errors]
          [--output {json,jsonc,yaml,yamlc,table,tsv,none}] [--query JMESPATH]
          {storage} ...

I'm met with errors for both --enable-change-feed and --enable-versioning

C:\> az extension add -n storage-or-preview
Extension 'storage-or-preview' is already installed.
C:\> az storage blob service-properties update --account-name xxx --enable-change-feed
az: error: unrecognized arguments: --enable-change-feed
usage: az [-h] [--verbose] [--debug] [--only-show-errors]
          [--output {json,jsonc,yaml,yamlc,table,tsv,none}] [--query JMESPATH]
          {storage} ...
C:\> az storage blob service-properties update --account-name xxx--enable-versioning
az: error: unrecognized arguments: --enable-versioning
usage: az [-h] [--verbose] [--debug] [--only-show-errors]
          [--output {json

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

ID: 73edc3d1-d0db-0ee3-7928-19bd1e509d55
Version Independent ID: 4b0e8f7c-591c-c5c4-37f4-e5a47914b873
Content: Configure object replication (preview) - Azure Storage
Content Source: articles/storage/blobs/object-replication-configure.md
Service: storage
Sub-service: blobs
GitHub Login: @tamram
Microsoft Alias: tamram

Thanks for reporting this. I have assigned the issue to the content author to investigate further and update the document as appropriate.

@brandonh-msft - This looks like it was a problem with your CLI version. But this feature is now GA. I recommend using Azure CLI version 2.11.1 or later. Updated doc is here:
https://docs.microsoft.com/en-us/azure/storage/blobs/object-replication-configure?tabs=azure-cli
#please-close

@brandonh-msft - This looks like it was a problem with your CLI version. But this feature is now GA. I recommend using Azure CLI version 2.11.1 or later. Updated doc is here:
https://docs.microsoft.com/en-us/azure/storage/blobs/object-replication-configure?tabs=azure-cli
#please-close

@tamram I had 2.11.1:
azure-cli v2.11.1 is the latest version available based on your source(s).

@brandonh-msft - Thanks for pointing out this error. I've updated the example in the article. The change should be live by tomorrow.
The correct command to use is az storage account blob-service-properties update. This command sets the service properties via the resource provider.
Also note, if you are running the CLI examples, you may encounter an error when you attempt to configure the source account. I've alerted the team to this issue and they are investigating.
Finally, the CLI may give warnings about the storage account or-policy command being in preview. These warnings should also be removed soon.

@brandonh-msft - The updated example is now live.
https://docs.microsoft.com/azure/storage/blobs/object-replication-configure?tabs=azure-cli#configure-object-replication-when-you-have-access-to-both-storage-accounts
#please-close


Implement HTTP Protocol

Expected Behavior
Implement HTTP Protocol for mobile projects

Current Behavior

Possible Solution

Steps to Reproduce

Context (Environment)

Done https://github.com/kuzzleio/sdk-dart/pull/63


Identify Suspending as the best place to save data

Change the wording so that suspending is still the best place to save data. Add the caveat that if you are doing background work, it is also good to perform a save operation in EnteredBackground.

@cc-cortes,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Remove unused images?

Since images should be the bulk of all data we store, there should be a server script that deletes all images older than X days that are not referenced in any node or note.
I imagine this would clear up some space.

We add rough 10 GB more data per event, and this costs us about $1 more per
month. In the grand scheme of server costs, our storage cost is still under
$10, or about 5%.
On Mon., Jun. 3, 2019, 07:45 Martin Zackrisson<EMAIL_ADDRESS>wrote:

Since images should be the bulk of all data we store, there should be a
server script that deletes all images older than X days that are not
referenced in any node or note.
I imagine this would clear up some space.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1826?email_source=notifications&email_token=AAL7MCNCWANGE4U57DJ64WLPYT77LA5CNFSM4HSHHLTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXIMRYA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL7MCNJIRYJWEBHU5A2D7DPYT77LANCNFSM4HSHHLTA
.

FWIW that cost will go up (double) once I switch to actual clustering, as
each of the front-end nodes will need a copy of the data.
On Mon., Jun. 3, 2019, 08:58 Mike Kasprzak<EMAIL_ADDRESS>wrote:

We add rough 10 GB more data per event, and this costs us about $1 more
per month. In the grand scheme of server costs, our storage cost is still
under $10, or about 5%.
On Mon., Jun. 3, 2019, 07:45 Martin Zackrisson<EMAIL_ADDRESS>wrote:

Since images should be the bulk of all data we store, there should be a
server script that deletes all images older than X days that are not
referenced in any node or note.
I imagine this would clear up some space.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ludumdare/ludumdare/issues/1826?email_source=notifications&email_token=AAL7MCNCWANGE4U57DJ64WLPYT77LA5CNFSM4HSHHLTKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GXIMRYA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL7MCNJIRYJWEBHU5A2D7DPYT77LANCNFSM4HSHHLTA
.


[discussion] make it possible to use bash for service scripts

All,
I am opening this because one of our downstream users has requested that we make it possible and I would like to gather thoughts about doing it.
OpenRC has never officially supported any script language other than posix shell for service scripts. Sometimes you have been able to get away with non-posix code, but not always.
I have been asked to allow bashisms in service scripts.
My thought is that, in order to do so, we would need to maintain multiple copies of, at least, gendepends, and maybe any other *.sh script in OpenRC, to run under each shell we support.

I don't know that there would need to be any code changes for the internal code in openrc, simply changing the shebang should do the trick.

Only changing the shebangs would require changing the shebangs at build time  in openrc-run.sh and gendepends.sh as well as assuming that all posix compatible scripts would run under bash in full bash mode.
If this change is made, all service scripts on your system would then be running under bash instead of bash in sh mode. Is it reasonable to assume that all service scripts can run under full bash?
If you want to test, make those changes on a system, reboot it and see what happens.

In my opinion, its a disproportional amount of effort to implement it compared to the gains.
If I understand correctly, for each shell, you'd need scripts made for the specific shell.
I would see difficulties to keep them all in sync, bashism specific stuff, posix, zsh whatever. Is that wise, or differently asked, what is the big gain of this exercise other than being able to write bash openrc-run?

@udeved  The plan is to allow this as long as it doesn't interfeer with the base code of OpenRC. Bash can understand posix shell even in bash mode from what I understand, so we can  make it work as long as the code that interfaces directly with openrc-run.sh is posix. I'll push a commit shortly.

i would restrict this a bit rather than completely opening it to any shell (as that basically means any interpreter, e.g. Python).  stipulate that POSIX shell must be supported, and then make it an option on a per-init.d script basis.  if we supported options in the header of the init.d script (maybe require it be the 2nd line?), then openrc-run could parse that at runtime, and then change from /bin/sh to something else.
using the shebang might also be an option, but we'd have to take care to split+parse that ourselves since the syntax only supports a single option (including whitespace).  and it can be limited in how long it can be by the kernel.


Udpate RD6006P

Sorry you were really quick to approve that =) Caught I'd uploaded the wrong version that was missing the side pegs, fixed is here.

what can I say I was really excited about this one :D

Allright, I've made a small change to the model to make the STL solid and to also pull the base up so that it can be printed without supports.  Should make no difference in the functionality but will make it loads easier to print (less time and no supports).
Thanks for the contribution!  I have an older Riden PSU that could probably use an update, and this might be the thing that has me make that happen :D

Glad you enjoy it, I saw someone else had one of these mounted and instantly wanted one.
More files coming soon :D


Update README.md

Fixed typo

Can you merge the pull request, sir?

Will be done.
Hello,
My name is Nitkarsh Chourasia.
I am a professional Python Developer from India, Maharashtra, South Mumbai
Let's connect:
GitHub: https://github.com/NitkarshChourasia
LinkedIn : https://www.linkedin.com/in/nitkarshchourasia

Can you merge the pull request, sir?

https://chat.whatsapp.com/ICJdMvoSrFVG7StsCEkQhs
This is a community where we do and solve and support and encourage competitive programming (DSA mostly people know by).
Do mind connecting.
Best regards,
Nitkarsh Chourasia

Can you merge the pull request, sir?

Done.

@sanikaahadap


[Docs]: Please check if the type notation of array in this picture is correct.

I'm not sure whether Array<SomeType>[] is written intentionally or by mistake.
Maybe it means Array<SomeType> or SomeType[]?
URL of the doc: http://lowcode-engine.cn/lowcode .
CDN URL of the pic: https://img.alicdn.com/tfs/TB16BEFeMgP7K4jSZFqXXamhVXa-1456-957.png .

um, absolutely it's a mistake, we will fix that~

After discussion we removed the image and the documentation has been updated.


[Marker.io] buttons in the header are not configured

Steps to reproduce:

check and click thebuttons present in the header area

Actual result: they are not configured
Expected result: please configure

Reported by: vinod<EMAIL_ADDRESS>- Contact via Marker.io
Source URL: https://wf-b.stg.prezzee.com/en-us/pricing
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1366 x 641Pixel Ratio@1x

🤖 Marker.io bot - This issue was marked as ✅ Resolved in Marker.io


⚠ Bofrost.gr has degraded performance

In 7491166, Bofrost.gr (https://www.bofrost.gr) experienced degraded performance:

HTTP code: 200
Response time: 2889 ms

Resolved: Bofrost.gr performance has improved in b80975f after 7 minutes.


Add favicon and ci job to test PRs

Summary

Add favicon
and ci job to test PRs

with favicon and how it is in prod right now

test when something is wrong in hugo and ci should fail: https://github.com/sigstore/sigstore-blog/actions/runs/4122726753/jobs/7119857309


Flaky installation of GoogleAppMeasurement in 7.11 with SwiftPM

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.5
Firebase SDK version: 7.11.0
Installation method: Swift Package Manager
Firebase Component: Analytics

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
From a blank project in Xcode 12.5, attempt to add Firebase via SwiftPM.
Occasionally, this fails to reproduce with the message:
artifact of binary target 'GoogleAppMeasurement' failed extraction: The operation couldn't be completed. (TSCBasic.StringError error 1.)
artifact of binary target 'GoogleAppMeasurementWithoutAdIdSupport' failed extraction: The operation couldn't be completed. (TSCBasic.StringError error 1.)

Relevant Code:
No code needed, error occurs in Xcode during installation.

This is likely the underlying implementation of the unzipping:
https://github.com/apple/swift-tools-support-core/blob/435a2708a6e486d69ea7d7aaa3f4ad243bc3b408/Sources/TSCUtility/Archiver.swift#L65
Will try to work off that and reproduce.

Using the unzip command an extra directory __MACOSX shows up. I suspect this is due to an incorrect compression of the release artifacts, and Xcode gets confused when there are 2 XCFrameworks nested there. This could also explain the flakiness in that sometimes the proper XCFramework gets selected.

7.11.1 for SwiftPM was released and this appears to be resolved.

@ryanwilson does this warrant a release note?

@ryanwilson does this warrant a release note?

Probably - but let's hold off momentarily as I just had the issue happen again.

This seems to have stabilized with some combination of recent Xcodes and Firebase releases. I'll close for now and we can reopen if it reoccurs.


Npm: Failed to get required authentication tokens

I am always having this warning at the beginning of the execution of the Npm task:
2017-03-27T11:18:19.8873236Z vsts-npm-auth v<IP_ADDRESS>
2017-03-27T11:18:19.8873236Z -----------------------
2017-03-27T11:18:19.9943260Z Creating npmrcFile. Path: C:\a\1\npm\auth.1559.npmrc
2017-03-27T11:18:20.2652065Z ##[warning]Failed to get the required authentication tokens for npm. Error: C:\a_tasks\Npm_fe47e961-9fa8-4106-8639-368c022d43ad\0.2.21\Npm\vsts-npm-auth\bin\vsts-npm-auth.exe failed with return code: 1
2017-03-27T11:18:20.2672046Z [command]C:\Program Files\nodejs\npm.cmd config list
2017-03-27T11:18:29.9350844Z ; cli configs
2017-03-27T11:18:29.9350844Z user-agent = "npm/3.10.8 node/v6.9.1 win32 x64"
Any idea to remove the warning ?

Same here. Any ideas?

Same here, same error

@tbuffryslb,
Will you post the contents of your .npmrc?  Obfuscate as necessary.

for us it's:
`registry=https://companyname.pkgs.visualstudio.com/_packaging/companyname.Sdk.Ui@Release/npm/registry
always-auth=true
@progress:registry=https://registry.npm.telerik.com/`

@IanMoroney,
Looking at your .npmrc I am fairly certain that this is a "INFO" message that has been mis-characterized as a "WARNING".
Is your build succeeding?  IOW, are you successfully downloading packages from both companyname.pkgs.visualstudio.com and registry.npm.telerik.com?

I think  i found some reason of this, i am running the npm task on an agent, but this agent hasn't been configured with npm install -g vsts-npm-auth command, and i have not runned the vsts-npm-auth -config .npmrc on the agent,
my .npmrc is setup locally into my project source code, which is not y et known by the npm tasks ...

We recently shipped a new version of the npm task that doesn't need to vsts-npm-auth package for auth. The new version of the task (1.x) will automatically add auth for feeds in your account specified in your project .npmrc
We are still in process of deploying the tasks, so if it's still not available in your specific VSTS account, it should be deployed in the next couple of days.


Usability improvements to foundry-merge-node

With this PR, we can now use the foundry-merge-nodes command to merge two nodes in different branches into a single node that subsumes both. This lets us merge branches back after a split, for example after an if statement or a loop, continuing the execution as a single branch, which has the potential of greatly improving the scalability of the tool in code with many loops or if statements.
However, this command has a few limitations in terms of usability:

The corresponding nodes in each branch (same PC) need to be present in the KCFG in order to be merged. This is not necessarily easy to ensure.
Because it requires manual intervention, the result of the verification becomes harder to reproduce.

We should think about ways to address these limitations to make this functionality easier to use. For example, suppose there was a cheatcode kevm.mergePoint() that denotes the point where we want to merge branches:
if (condition) {
    // if branch
} else {
    // else branch
}

kevm.mergePoint();

If we could implement this cheatcode such that the point where it's called is always added as a node to the KCFG, this would take care of (1). Going one step further, if we had an option to automatically merge such nodes if they have the same PC, this would take care of (2) (but this heuristic might not always work, for example if the merge point itself is inside a loop or a function that is called multiple times). But I don't know if something like that could actually be implemented, because it is a cheatcode that would not be handled solely from inside kevm, instead needing to somehow communicate with pyk.
I'd like to hear people's thoughts on this and brainstorm possible options.

For now, the alternative that I'm using to mergePoint is to make an external call that does nothing (it can be implemented as a dummy cheatcode, for example) and turn on --break-on-calls. But this will break on every external call, which will slow down execution a bit.

I would call it a kevm.cut() instead, in the same notion of a cut-rule, and we can just make the rule which implements it a cut-rule. This is in line with the idea of cut-points from @daejunpark's thesis: https://www.semanticscholar.org/paper/Cut-Bisimulation-and-Program-Equivalence-Park-Kasampalis/be608a0dcfe23747c4146ed0f10a544ab015e059

One potential complication that just occurred to me based on the current engagement: the point where we ideally want to merge can be inside the client code, in which case calling a cheatcode is not really possible.

Oh, right, thanks @lucasmt. @ehildenb said the same thing — his suggestion is to let the user specify PCs in the contract being verified that we can use to generate some dummy rule expressing how the merge should happen and/or add these PC to the <cut opcodes> cell (or something like this) in the configuration.
@lucasmt do you think it would work? @ehildenb could you please check if I got it right?
@nwatson22 please let me know if you have any suggestions or comments on this issue too.

@palinatolmach Yeah, I think that could work. We would need to update the PC if the code changed, but that would be a relatively minor inconvenience compared with manually editing the KCFG every time to find the node we want.

I would also suggest to merge according to some condition, for instance:
kevm.merge(removeNode != 0)

At this point, all nodes that satisfy the condition removeNode != 0 (where removeNode is a code variable) would be merged.


Cross Compilation features

Hello there,
and thank you for your awesome work.
Since we're planning to add compilation capabilities to our CI/CD environment we also have the needing to be able to cross-compile from various platforms to others.
I managed to add flags to specify valid node.js compilation platforms (both os and cpu arch):
./nodec --dest-os=linux --dest-arch=x64 index.js

I managed to get it to also cross-compile between mac and linux (with some limitations due to newer v8 versions, known things out there).
Valid architectures and CPUs are the same of the vanilla node.js (it should be checked with added dependencies, BTW).
In order to properly cross-compile one must use a valid toolchain, since this project always compiles from source it could also be provided inside the repo itself, what do you think about it?
Let me know if it looks good to you and your thoughts.

Sorry for the delay. I'll look into it ASAP. Thanks for the PR.

With @pmq20 having v1 support C++ based native modules wouldn't this not work in most cases as native modules need to be built on their intended platforms? I'm pretty sure bcrypt compiled on Mac doesn't work on Linux, but maybe I'm wrong?

@pmq20 Thanks, I'll rebase against the latest changes asap not sure about the windows failing compilation, but I think it might be already broken when I started working on the PR.
@firrae By using node.js from source code you basically get the same support you'd get for the node executable itself (node-compiler only wraps it by creating the temporary filesystem before to actually call the entry file). So you can refer to the official support, I guess, for possible issues with native modules. By the way you can find several docs online about node.js specific cross-compilation cases [1] which are pretty well covered.
In order to do so successfully of course you need to set up a cross compilation toolchain and properly configure it inside your shell environment.
The only issue I got from Mac was about the install process trying to execute some runtime scripts on the host machine – the infamous mkpeephole – because, of course, you can compile it and produce a valid binary for the destination platform, but it won't certainly run anything successfully on the host (compiling system) if it's different from the target platform. This is a know issue happening since v7 [2].
You can check code comments to see the options needed to avoid common cross compilation issues, I thought to enable them by default when cross compilation is detected
# --without-intl=none fixes: icutrim.py - it tries to run a binary made for linux on mac
# --cross-compiling is required require host executables rather than target ones
# --without-snapshot avoids mksnapshot to run on host platform after build

I'm still stuck with the mkpeephole.
P.S. I also managed to get internally a way to define what node.js version to compile from, but since then the master has been updated with patches on the node code. So now it must be checked that those patches are compatible with v6.x before to be able to downgrade (at this point it might make sense to force the specific min and max versions supported by those patches).
@pmq20 If the patches are compatible with the v6.x line we could exploit git to patch the source code automatically (more or less the same way React Native does it [3]).
[1] https://github.com/netbeast/docs/wiki/Cross-Compile-NPM-modules
[2] https://github.com/nodejs/node/issues/9707
[3] https://facebook.github.io/react-native/docs/upgrading.html

@lexor90 that's interesting, I've never had to look at cross-compiling before the project I'm currently on so thanks for the links! It's good to know.

@firrae I just gave a quick look at the node-gyp cross-compilation status which is what native modules do use to compile themselves from sources and it seems there's still some issue with it [1] mainly because all of the libraries built upon it have no concept of cross-compiling, so they do assume that target_host === building_host. I think there's more support for cross compilation across different processor architectures (eg. x86 to ARM) rather than across different operating systems though, thanks to the variety of embedded platforms and mobile devices that need to be targeted.
I know for sure there's some way to get bcrypt cross compiled properly (by exporting needed files from the target platform) but I never tried it though.
Maybe a quick workaround here would be to be able to run some pre defined script on the first run on your target machine, in order to install those modules and just link the libraries from the outside. Some sort of shared library.
But I don't actually know what kind of involvement would it mean on the implementation side and what kind of compatibility support would it retain with plain nodejs. I'd rather search for some solutions that may already be in use out there.
[1] https://github.com/nodejs/node-gyp/issues/829

Semi off topic:
Personally speaking, I'm in a bind where the idea of build once and deploy anywhere is almost a necessity so we've built out our own flow for it. The project I'm on has the need to be installed on isolated servers with no internet connection and limited build tools (usually it's a VM they spin up and tell us to install on) so having to build it on startup wouldn't help me, personally, but I bet there are plenty of other use cases where this would be greatly welcome. Once I solve my build issue using this (currently bcrypt doesn't seem to work for me) I'll likely set up a build pipeline that builds on each of our supported platforms.
Thanks for the links and info though.

@lexor90 I noticed that you have a binary and a shell script in the bin directory of your PR, are those needed for something or just the results of a test that got included in a push?

@firrae Yeah, you're right. I somehow missed I've checked them in.
I'm going to remove them as they are not related to the project itself, thanks.
BTW the bin/run.sh gives you an example of shell environment setup to cross-compile node.js (and more generically any C/C++ project). It basically rewrites the environment variables used by buildtools to use the executable we want rather than the system's default.

@pmq20 can we setup a cross-compile toolchain on our CI in order to test this? I think the easiest cross-compilation would be changing the target processor (we do also support changing operating system, but it's quite tricky as the binary format does differ - for example mac uses mach-o, while linux uses elf).
If this looks good to you merge it, we're simply exposing the native support (we also need to point out to the official node bugtracker for any issue regarding cross-compilation as long as it's not concerned to one of our nodec-specific dependencies).

@lexor90 May I share another possible approach on cross-compiling? @ngot has found out that simply attaching a chunk of data to the end of the executable does no harm to the executable itself. By utilizing this technique we could pre-compile a dozen of binaries for each arch and OS, and download them when compiling a user's project. The compiler could just compress the user's folder into a SquashFS image and attach it to the end of the downloaded binary and it is done. In this way, cross-compiling is easily achieved. Still need proof of concept but I think this direction is very promising.
Also, thank you @ngot for the great idea!

here is the example :

https://github.com/fibjs/fibjs/blob/master/fibjs/src/base/fibjs.cpp#L107
https://github.com/fibjs/fibjs/blob/master/test/selfzip_test.js#L72

Hey there,
that would be great. Seriously, it would get rid of what takes the most to compile.
I know that also pkg works with precompiled binaries (according to their readme) and I was at first looking at this possibility, as it would mean to have a much quicker compilation time, but then I could not find a way to make this happen since we need to compile nodec from source.
I'm surely going deeper into this approach, as it could be a nice solution also for #40.
Cross compilation would still be needed in order to compile properly the remaining part of nodec otherwise one would have a combination of nodejs and nodec compiled for two different platforms (this means you'd download nodejs for linux, but compile squashfs on mac os x which would obviously lead to a not working binary).

@pmq20 if we are able to precompile npm alongside nodejs we could also get rid of the local npm command, so we don't need to check the current system-wide version of node. Am I right? The build would become then truly reproducible and working on any system with or without nodejs installed (at the moment we do depend on npm install before to actually compile node and libsquash). The only difference would be that npm must be run on the host platform (which is doing the compilation) while the precompiled node would match the target platform (which is where it must be run to).

@lexor90 Yes, and npm is written in Javascript instead of C++ so it is easier. My thinking is we divide the compile process into 2 passes. On the first pass a vanilla Node.js environment is compiled without any hack and produced and cached to be used later as a local node environment. On the 2nd pass, the user's project entrance is hacked into node and do the real compiling for the user.

Such a wanted feature, is there any plans to merge this ?


Standalone Swift Package archive failed when swift-atomics is a SPM transitive dependency

Hi,
I'm not able to archive my standalone swift package supporting only iOS platform when I have swift-atomics in the SPM transitive dependencies of my swift package SPM dependencies.
Information

Package version: 1.0.2
Platform version: 12.4
Swift version: swift-driver version: 1.45.2 Apple Swift version 5.6.1 (swiftlang-<IP_ADDRESS>3.66 clang-13<IP_ADDRESS>)
Target: x86_64-apple-macosx12.0

Checklist

[x] If possible, I've reproduced the issue using the main branch of this package.
[x] I've searched for existing reports of the same issue.

Steps to Reproduce

Create a basic standalone swift package like Package.swift.txt
Try to archive swift package for iOS and iOS Simulator platforms

Expected behavior
Archive my swift package for generic/platform=iOS and generic/platform=iOS Simulator destinations in order to generate a .xcframework
Actual behavior
I have a standalone swift package that targets only iOS (v13+).
My swift package has as dependency google-auth-library-swift which has as dependency swift-nio which has as dependency swift-atomics.
When I try to generate the .xcframework from my swift package, I have this error while archiving for iOS and iOS Simulator destinations:
Command line invocation:
    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -project /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/SafeRider.xcodeproj -configuration Release -archivePath /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build/SafeRider/iphoneos.xcarchive -destination generic/platform=iOS BUILD_DIR=/Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build SKIP_INSTALL=NO IPHONEOS_DEPLOYMENT_TARGET=13.0 BUILD_LIBRARIES_FOR_DISTRIBUTION=YES SKIP_INSTALL=NO -scheme SafeRider archive

User defaults from command line:
    IDEArchivePathOverride = /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build/SafeRider/iphoneos.xcarchive
    IDEPackageSupportUseBuiltinSCM = YES

Build settings from command line:
    BUILD_DIR = /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build
    BUILD_LIBRARIES_FOR_DISTRIBUTION = YES
    IPHONEOS_DEPLOYMENT_TARGET = 13.0
    SKIP_INSTALL = NO

Ld /Users/sebastienbalard/Library/Developer/Xcode/DerivedData/SafeRider-gryczvykejxqntfoykjzxkaooaoi/Build/Intermediates.noindex/ArchiveIntermediates/SafeRider/InstallationBuildProductsLocation/Library/Frameworks/_AtomicsShims.framework/_AtomicsShims normal (in target '_AtomicsShims' from project 'SafeRider')
    cd /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -target arm64-apple-ios13.0 -dynamiclib -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS15.5.sdk -L/Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build/Release-iphoneos -F/Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build/Release-iphoneos -F/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks -filelist /Users/sebastienbalard/Library/Developer/Xcode/DerivedData/SafeRider-gryczvykejxqntfoykjzxkaooaoi/Build/Intermediates.noindex/ArchiveIntermediates/SafeRider/IntermediateBuildFilesPath/SafeRider.build/Release-iphoneos/_AtomicsShims.build/Objects-normal/arm64/_AtomicsShims.LinkFileList -install_name @rpath/_AtomicsShims.framework/_AtomicsShims -Xlinker -rpath -Xlinker /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/macosx -dead_strip -Xlinker -object_path_lto -Xlinker /Users/sebastienbalard/Library/Developer/Xcode/DerivedData/SafeRider-gryczvykejxqntfoykjzxkaooaoi/Build/Intermediates.noindex/ArchiveIntermediates/SafeRider/IntermediateBuildFilesPath/SafeRider.build/Release-iphoneos/_AtomicsShims.build/Objects-normal/arm64/_AtomicsShims_lto.o -Xlinker -export_dynamic -fembed-bitcode -Xlinker -bitcode_verify -Xlinker -bitcode_hide_symbols -Xlinker -bitcode_symbol_map -Xlinker /Users/sebastienbalard/Workspace/LibertyRider/saferider-ios/.build/swift-create-xcframework/build/Release-iphoneos -Xlinker -final_output -Xlinker /Library/Frameworks/_AtomicsShims.framework/_AtomicsShims -Xlinker -dependency_info -Xlinker /Users/sebastienbalard/Library/Developer/Xcode/DerivedData/SafeRider-gryczvykejxqntfoykjzxkaooaoi/Build/Intermediates.noindex/ArchiveIntermediates/SafeRider/IntermediateBuildFilesPath/SafeRider.build/Release-iphoneos/_AtomicsShims.build/Objects-normal/arm64/_AtomicsShims_dependency_info.dat -o /Users/sebastienbalard/Library/Developer/Xcode/DerivedData/SafeRider-gryczvykejxqntfoykjzxkaooaoi/Build/Intermediates.noindex/ArchiveIntermediates/SafeRider/InstallationBuildProductsLocation/Library/Frameworks/_AtomicsShims.framework/_AtomicsShims
Undefined symbols for architecture arm64:
  "_swift_release_n", referenced from:
      __sa_release_n in _AtomicsShims.o
  "_swift_retain_n", referenced from:
      __sa_retain_n in _AtomicsShims.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

My problem seems to be related to https://github.com/apple/swift-atomics#portability-concerns,  it is the same part of code which causes a problem but your "manual workaround" fails in my SP "iOS only" case.
$ swift build -Xcc -mcx16 -Xswiftc -DENABLE_DOUBLEWIDE_ATOMICS -c release -v
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/usr/bin/xcrun --sdk macosx --find xctest
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -emit-supported-features /var/folders/wk/b_snvw5j52s4fvs94yl9v23m0000gn/T/TemporaryDirectory.fXQsde/dummyInput-1.swift
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -print-target-info
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift-frontend -frontend -emit-supported-features /var/folders/wk/b_snvw5j52s4fvs94yl9v23m0000gn/T/TemporaryDirectory.n1XVva/dummyInput-2.swift
Planning build
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk iphoneos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk appletvos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk watchos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
error: the library 'SafeRider' requires macos 10.10, but depends on the product 'OAuth2' which requires macos 10.12; consider changing the library 'SafeRider' to require macos 10.12 or later, or the product 'OAuth2' to require macos 10.10 or earlier.
error: the library 'SafeRider' requires macos 10.10, but depends on the product 'OAuth2' which requires macos 10.12; consider changing the library 'SafeRider' to require macos 10.12 or later, or the product 'OAuth2' to require macos 10.10 or earlier.

Any help would be greatly appreciated.
Thanks.

The upcoming 1.1 release is scheduled to bump the minimum toolchain version to Swift 5.6, allowing double wide atomics to be unconditionally enabled. This will obsolete the ENABLE_DOUBLEWIDE_ATOMICS condition, resolving this problem.

Correction: I commented on the wrong bug -- unfortunately fixing this will likely need us to remove these two functions, which requires us to first fix https://github.com/apple/swift/issues/56105.


Add material design shadows

Converted @dbox awesome material design shadows.
Closing https://github.com/jescalan/axis/issues/277
Tasks:

Add stylus source & link in index
Add tests & fixtures
Add visual test section

The failing test is unrelated.

Will submit a PR to the docs asap, my university network is blocking git ports. :watman:

Thanks for doing! My 2 notes would be:

I don't think we have to add an entire category for shadows. It can live in utilities or layout.
We need to format the comments to be more consistent with axis code comments, not the sassdocs style.

@jescalan can be the final authority!

Ah, I see

I was looking at the structure and sorted it in after gradients. I certainly don't view it as a utility or layout tool.
Agreed, I did not want to remove the annotations but just saw that the params info is inside roots-www.

@jescalan What do you think about the category-issue? Will open a new PR once all required changes are clear.

Honestly, I'm not sure if a feature like this belongs in axis. It's usage is limited narrowly to one specific design style, whereas most of the other utilities we have here are design-agnostic and could be used across any site. I think it's a great utility to have around if you are using material design, I'm just not sure it belongs in axis -- it might fit better in a material design UI library.

I think the material name can be a little misleading. Yes, that's where the shadows came from. But, the Axis table mixin was ported directly from bootstrap as well.
IMHO these are just easy shortcuts to creating beautiful dropshadows. I wouldn't say this is limited to one design style.  Material design doesn't get © on dropshadows.
Honestly doesn't bother me one way or another if it gets added. Just my .02.

Material design doesn't get © on dropshadows

Again, referring to https://github.com/jescalan/axis/issues/277
I will file a new PR that levels out the bumps mentioned:

Sassdocs / Axis Docs style
naming material

@jescalan has final say, so better hold off for now

I would still vote 🚫 -- I just don't see this having many use cases outside of material design. But if anyone else wants to chime in and give a 👍 then I might be convinced.

👌

I still think axis lacks some shadow helpers / utils.
@jescalan what are your thoughts on this and what are the requirements for a tool like this?

@jescalan do you welcome a pull request for drop shadows & presets and what would the requirements be?

Drop shadows don't strike me as basic UI elements or common utilities...


Suggestion: Add button to copy post text for Alt text

Hi, I just learned about this nice tool of yours! The post I read pointing to it goes on to suggest that one should "remember to copy the post text as alt text".
Mastopoet could make that easy for the user by providing a "Copy alt text" button right next to the "Download .png" button like so:

Implemented in 00ccc1e

Wow, that was fast! Thank you! :rocket:


🐛 Github Reporter not generating annotations correctly

Environment information
Commands are being run in a Warpbuild Github Actions runner (specifically warp-ubuntu-latest-x64-2x), but i've tested and this happens on ubuntu-latest too
CLI:
  Version:                      1.8.0
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "unknown"
  JS_RUNTIME_VERSION:           "v18.19.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "yarn/4.1.0"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    false
  VCS disabled:                 false

Workspace:
  Open Documents:               0

What happened?

Set up biome in a project with linting errors
Run yarn biome ci --reporter=github in an actions workflow/step

Expected result
Expected: Annotation output should turn into an annotation in the Github Actions execution logs/Files Changed view
Actual: The annotation is output as a string and nothing happens. i.e. I see this in the console:
::error title=lint/correctness/useJsxKeyInIterable,file=path/to/file.tsx,line=36,endLine=36,col=20,endColumn=48::Missing key property for this element in iterable.
Error: Process completed with exit code 1.

Instead of this, and all the other annotations stuff:
Error: Missing key property for this element in iterable.

I can confirm that the annotation format is correct - if I manually echo the output it turns into an annotation correctly, and it's only from yarn biome ci that it fails to work.
Code of Conduct

[X] I agree to follow Biome's Code of Conduct

Yeah I have been trying to understand why it hasn't been working properly, and I can't figure out why

Tested, it's also working for me! Thanks for the fix.
I think if Github annotations are going to be generated it might be better to force colours off as opposed to setting a flag to explicitly turn them off, but i'm happy to leave that as just a note and close this issue.

I think if Github annotations are going to be generated it might be better to force colours off as opposed to setting a flag to explicitly turn them off

I completely agree with you.
One thing is turning colours off also means that the colours for summary details/total are also off: https://github.com/biomejs/biome/blob/fc9b1ebc7d1b76b63678b85fc580aab48f2e5014/crates/biome_cli/src/reporter/terminal.rs#L88-L141
This is not a big deal, but the ideal fix for this should be only switching off colours for the "annotation" part.
I'd like to reopen this as a reminder. Either forcing colours off entirely in this mode, or only keeping annotataions colorless is an acceptable fix.

I'd like to reopen this as a reminder. Either forcing colours off entirely in this mode, or only keeping annotataions colorless is an acceptable fix.

I think removing colours based on the reporter is the way to go. Keeping annotation colourless feels too complex, and I don't envision future cases where we need such a sophisticated feature.


[metadata] Add workspace.dependencies and <dep>.workspace to cargo-metadata (Rust 1.64+)

Problem
cargo metada does not show the workspace dependencies nor if a dependency is inherited from the workspace in its output.
Proposed Solution
Add the missing metadata to the output.
Notes
We should also remember to update oli-obk/cargo_metadata at the same time to make it immediately available to most people

What is is you are wanting to do programmatically with the workspace. entries and packages references them?

I wanted to write a little tool to see if a dependency was inherited or not from the workspace, and if it's features matched the ones defined in workspace.dependencies. Same for things like workspace.package infos (repository for example, in multi-crates repositories)

Another example, for my PR on cargo-edit, it would avoid reading the manifest twice, once through the metadata to resolve the version and one manually to find if package.version.workspace is true

The cost of reading the manifest multiple times feels relatively small to me in the context of cargo-set-version and cargo-release.

For this specific case yes, at least in terms of IOs. In terms of code, it's quite a few lines to check a boolean. It's also lots of duplicated code in each program that want to check this

To give numbers to what @epage is saying:
When working on workspace inheritance we found a case where cargo was reading most manifests twice and making it only once dropped the time by about 10ms (150ms to 140ms) for one large workspace and on smaller workspaces, it was a few 1ms - 2 ms. This was on an M1 Mac with an SSD but I would still not be concerned about the added time.
Looking at the issue of duplicated code for any project that has to deal with this, I am not very concerned. There is always going to be some level of this across the ecosystem. I would be concerned that changing the cargo metadata output could be a breaking change and have winder implications than intended.

We can make cargo-metadata changes without them being breaking, it just comes with a complexity and performance penalty to all other cargo-metadata users.  We have to weigh these out in adding more content to cargo-metadata.  Ideally, we would add a query language on top of it so people can request what they want.  Even with that, in this case, it requires cargo to do extra book keeping to track the extra information about workspace inheritance.
From there, the question is how much of a need is there for this to weigh the needs of these users against everything else.

Looking at the issue of duplicated code for any project that has to deal with this, I am not very concerned

That's what concerns me the most. To correctly check a workspace, the procedure is

Ask cargo_metadata for the the workspace members
Check root Cargo.toml for workspace.package.version = "version"
For each workspace members, read the manifest, checking for package.version.workspace = true (in all the forms accepted by TOML, so obligatory direct dependency on either toml_edit or toml, and writing specific code for this)

The last step is easy but could also be a one-line check if it was present in the metadata, at very little cost for cargo I believe since it already must check for this when computing the version itself

From there, the question is how much of a need is there for this to weigh the needs of these users against everything else.

Yes, it could be I'm the only person needing this, in which case it's not very useful. I have seen at least one other tool (on Reddit r/rust I think ?) that moves workspace crates to [workspace.dependencies] and checks their version is inherited from the workspace (so it also needs to check for package.version.workspace = true, not just matching versions)

I'm going to propose to the cargo team that we close this.  This adds a lot of bookkeeping on cargo's side while being one of several forms of normalized information where we don't track the unnormalized form.  The workaround (read each manifest) is relatively trivial (its what cargo does in cargo add and cargo rm).

Since dependencies are shown for each workspace member - as well as other bits of information like which features they are using or using the default features, etc. - wouldn't it be idiomatic to show whether that information was inherited from a workspace? I appreciate from #4018 that identifying the "current" package isn't always authoritative, but it seems every package in a workspace already has package-specific "attributes" to its dependency list. Identifying the "current" crate isn't too difficult nor worry me too much with duplicative effort, but parsing dependencies for all the current and possible future permutations as @poliorcetics eludes to is something it seems either cargo metadata or the cargo crate should do in a consolidated manner.

I don't see how this is a question of what is "idiomatic".  cargo metadata today shows normalized output.
It puts a big compatibility burden on us to show a partially-normalized form.
There is also the question of how normalized

Whether a dependency is inherited or not
What fields were inherited
Other inherited information like package fields
When it comes to [lints], we might add overriding and so that gets back to "what fields are inherited" question that dependencies have.

For any of these questions, this would also require us adding all of this bookkeeping to cargo so we can present it.  cargo metadata doesn't look directly at cargo-util-schema::maniest::Manifest and render it but is pulling the data from the core types in cargo that are used for all regular processing.


FYI/Crash Report

https://pastebin.com/69TEVp0F

Damn, and I thought I'd gotten all the crashes. Sorry about this, I'm not great at testing it seems.

I believe it's fixed now. I tested it on three different versions of MC with the configs deleted.


Ping does not match latency from the TCP connection of the ffxiv process

To the best of my knowledge, the "realest" latency one has with the FFXIV servers is the TCP connection latency used by the FFXIV process, and it can be found in Windows in the Resource Monitor.
When checking if the ping shown in the plugin matches, I found that 90% of the time in my case, the latency is different (see attached screenshot).

Since I have no knowledge of C# I have no idea what exactly you are "pinging" but the value shown by the plugin matches what I get when doing a ping in a terminal and not the ping from the actual connection, which to the best of my knowledge is far more useful.
I guess this issue is more of a question at the moment.

The plugin does an ICMP ping, so it will be an underestimate, currently. I am, however, looking into piping typeperf instead, which should be more reliably functional and be as accurate as resmon.

Actually, it looks like there's a WinAPI method to just get that information directly, so I'll figure out and implement that over the next few days: https://docs.microsoft.com/en-us/windows/win32/api/iphlpapi/nf-iphlpapi-getpertcpconnectionestats?redirectedfrom=MSDN

To specifically answer your question, the ping currently shown by the plugin is the ping you would get from running the ping command from the console. This is the minimum latency between you and the gateway server, not the usual latency between you and the game server behind that. The two numbers are sometimes the same, but the latency between you and the game server can be higher than the value shown.
I'm working on fixing this by using a better API method.

Thanks for the quick answer(s), i'll be waiting eagerly to see the update :)


Leon weather

What type of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Refactor
[ ] Documentation
[ ] Not Sure?

Does this PR introduce breaking changes?

[ ] Yes
[X ] No

Description:
With this package you can ask Leon about the weather in all the cities of the world.
It's not full finish because it's miss test and little things.

Hello @gnouf1,
Thanks for that PR! I'll take a look at that later.
In the meantime, let me know when you have finished it and do not hesitate to ask any questions.

Okay, i'm gonna add config file and future weather.
And I just want to say : I take a great pleasure when I work on features for leon :p

I'm happy to see that you enjoy working on new Leon features!
If you have any feedback or see things to improve, do not hesitate to reach me out, I'd love to hear them.

Okay no problem !
After this features i gonna make other i guess, i have time this month.
For me apart from the JS test it seems good for a version 1.0.0.

I was writing about the same package. I'd like to point out a few suggestions:

To me the name of the package sounds a bit redundant, perhaps we could call it simply weather;
English comments would be appreciated;
Perhaps we could use the Python wrapper for OpenWeatherMap: PyOWM;
Support for Celsius and Fahrenheit scales;
Set the api token in the settings.json file along with other settings like deciding which temperature scale to use etc.

English comment are just a little forget from me, sorry :)
And for settings.json I totaly agree with you !

English commentary are up, config file is also OK, Farenheit and Kelvin are now usuable !

Awesome! :clap:
It would also be better if your commit messages are in English to ensure that most people understand :relaxed:

Of course !
Sorry i'm new on github (and python) and I learn how to use it :)
From now on I'll be careful about that :)

Test up :)

What are finale steps ? :)

I'll review it later, thanks! :smile:
In the meantime, feel free to pick up another module you would like to develop or whatever you think is good and open an issue to discuss about it first.

Little update, now he use multilanguage weather :)

Merge with other weather package

https://github.com/leon-ai/leon/pull/108.


External link doesn't work

Hello,
Sometimes external links doesn't works. For example there is a problem with: https://istio.io/docs/setup/kubernetes/quick-start#deploy-your-application
Http header:
HTTP/2 200
cache-control: public, max-age=0, must-revalidate
content-type: text/html; charset=UTF-8
date: Wed, 08 Aug 2018 10:41:23 GMT
etag: "05ebadd25d610adc020ae2687ad48531-ssl"
strict-transport-security: max-age=31536000
age: 90664
content-length: 60689
server: Netlify

It looks like it was a timeout. Would be nice to have information why link is bad...


Changing option via keyboard shortcut does not persist to user.yaml

Describe the bug
Changing (e.g. toggling) an option to be saved via the options menu successfully persists to user.yaml, and therefore persists when changing schemas or exiting and restarting Rime. The persistence fails when changing the option via a keyboard shortcut.
To Reproduce
Below are high-level reproduction instructions on Weasel and detailed reproduction instructions with librime built from source on Linux (with build dependencies installed).
Weasel
session 1

choose any schema, A
use options menu to toggle any option
choose a different schema, B
choose A
verify that the option has been toggled

session 2

choose any schema, A
use keyboard shortcut to toggle any option
choose a different schema, B
choose A
verify that the option has not been toggled!!!

librime on Linux (input into shell)
N.B. full_shape is an option that needs to be saved
session 1
git clone https://github.com/rime/librime librime1
cd librime1
make
cd build/bin
./rime_api_console
{F4}                                      # this shows that full_shape is currently off
2
3                                         # this toggles full_shape through options menu
{F4}                                      # this shows that full_shape is currently on
exit
cat user.yaml                             # this shows that full_shape is currently on
./rime_api_console
{F4}                                      # this shows that full_shape is currently on

session 2
git clone https://github.com/rime/librime librime2
cd librime2
make
cd build/bin
./rime_api_console
{F4}                                      # this shows that full_shape is currently off
{Escape}
{Control+Shift+3}                         # this toggles full_shape through keyboard shortcut
{F4}                                      # this shows that full_shape is currently on
exit
cat user.yaml                             # this shows that full_shape is currently off!!!
./rime_api_console
{F4}                                      # this shows that full_shape is currently off!!!

Expected behavior
On every platform, in session 2, on lines marked with !!!, the option should show as having been toggled, or on.
Flavor(please complete the following information):
Select your flavor:

[ ] ibus-rime
[ ] fcitx-rime
[ ] fcitx5-rime
[ ] Squirrel
[ ] Trime
[x] Weasel

Package:

OS: Microsoft Windows 10 Home 10.0.19045 Build 19045
Version: 0.15.0
URI: https://github.com/rime/weasel/releases/download/0.15.0/weasel-<IP_ADDRESS>-installer.exe

Additional context
I have been able to fix the bug locally as follows:
Comparing calls to Context::set_option in switch_translator.cc and key_binder.cc, those in switch_translator.cc are followed by a call to Config::SetBool whereas those in key_binder.cc are not. By adding similar statements to key_binder.cc, the bug is fixed. The logic needs to be fixed for all of radio_select_option, toggle_option, set_option, and unset_option; perhaps they can share a function which performs the persistence.
I am unsure about how to contribute my fix to this project, but am happy to do so.
Thank you!

目前的策略就是這樣.
參考其他主流中文輸入法, 快捷鍵做臨時的狀態切換.
而方案選單類似設置程序的作用.

不過這裏可能有 BUG:
session 2 裏, 切換方案前後 full_shape 應當不變.
這不是通過保存到 user.yaml 實現的, 而是不清除或重置內存中的狀態.
除非方案裏指名要重置 (如 ascii_mode 通常在切換方案後重置爲 0).

退出 rime_api_console 進程後再運行就不是同一個 session 了.

Understood; thank you for your help.
I guess the issue can be closed?


Hamburger menu layout distorted when orientation is changed while menu is hidden

Consider application that has specific page without the menu used for landing. When user navigates away from this page the hamburger menu is shown. Now, if user navigates back to the landing page and orientation switch occurs, the menu layout is distorted when user again navigates back to page where the menu is shown.
So in summary:

Show hamburger menu
Hide menu by setting IsFullScreen to True (happens when user navigates to specific page in this scenario)
Change orientation (with mobile device, probably valid if changing the screen orientation on desktop too)
Show menu (again, happens due to user navigation in this scenario)
Observe the hamburger menu. Depending on if you switch from landscape to portrait orientation, or vice versa, and whether the navigation in the steps is initialized via the hamburger menu or not, the menu is shown distorted in different ways. In best case scenario, the menu is still very easily shown in wrong display mode.

Thanks for reporting this.

I think this happens because HamburgerMenu splitview is removed from visual tree in Fullscreen mode and does not see the orientation change.

@carstenschuette @toituu I've tested my changes for this problem and worked. Take a look there and see is working so i can make a PR.

I believe this is resolved in 1.1.10


silance "is" with 'str' literal syntax warning from pretrainedmodels in python >= 3.12

I would really like to remove dependencies on these unmaintained libraries and replace them with timm: https://github.com/qubvel-org/segmentation_models.pytorch/pull/918#issuecomment-2438395280

@adamjstewart This sounds amazing. But in the meantime we can merge this fix for a quick patch.

Thanks for update!


[Feature] Projection Matrix Publisher

Now, Autoware calibration publisher load calibration file and publish tf data.
But, I think it is not good way.
This is because we cannot know full transform before we launch calibration publisher.
And, we can use only fixed camera in Autoware.
New Feature
Add projection_matrix_publisher node and it read tf data between camera and lidar and publish projection matrix data.

Why do you think using tf is not a good thing?

It is because all frame transform should be described in URDF.
Now, we cannot use camera frame in URDF.


How can I explicitly retrieve the position of a dynamic physics body

Hey all, we've been trying out ViRo for a multiplayer AR game, works very nicely. I have a question though: if i want to explicitly retrieve the position of a dynamic physics body, how would I proceed?

The position of a physics body is effectively the position of the node. Thus, you might be able to call getTransformAsync on a viro control to get that information.
https://docs.viromedia.com/v2.1.0/docs/viroview#methods
this.boxRef.getTransformAsync().then((transform) => {
        var pos = transform.position;
        // Do stuff with position
      });


Sign up : stuck for ever after clicking "Sign up"

Today's GIGA test; coinstac is stuck for ever on Ubuntu 16.04 after entering information and clicking on "Sign up". Yes it looks like I was able to sign up, I received a mail and my credentials are working.

When I click "Sign Up" in above screen. Don't know if that's on purpose, but some feedback would be useful, such as "Now you can log in".


Explicitly note coercion to string for .contains

as per #992

This PR fails 'make xtest' (but is easily fixable)
xt/trailing-whitespace.t (Wstat: 256 Tests: 376 Failed: 1)
  Failed test:  94
  Non-zero exit status: 1

The sentence you add overlaps with some of the text that's already there, for contains. (regarding start and needle)

Really? Trailing whitespace is not allowed in doc text? OK. I've removed it where I found it.

Really? Trailing whitespace is not allowed in doc text?

Trailing whitespace is invisible, and disallowing it removes corner
cases from tools that process the text.
That's the usual reason why such a policy is considered reasonable.

Thanks.


vx_ext_amd - updates & cleanup

Cleanup
Fix Doxygen comments

@LakshmiKumar23 build this PR to verify that it does not produce any warnings.

@kiritigowda No warnings from our side. I only see this
c++: error: unrecognized command-line option ‘--rtlib=compiler-rt’

However, build for mivisionx is broken. Please merge #1144 before release

@kiritigowda No warnings from our side. I only see this
c++: error: unrecognized command-line option ‘--rtlib=compiler-rt’

However, build for mivisionx is broken. Please merge #1144 before release

which commit broke the develop? I thought we tested it last night?


Upgrade to Graph API v2.x

I got message when login to Facebook with ngCordovaOauth: You must upgrade this app to Graph API v2.x, v1.0 will be deprecated on April 30, 2015

Thanks!
As soon as I have time I'll work on a fix.  For technical reference, please see here:
https://developers.facebook.com/docs/apps/upgrading

Just pushed a change with Facebook 2.0.
Thanks again for reporting it!


make umn table responsive

https://github.com/opentelekomcloud-docs/elastic-cloud-server/pull/30 together with https://github.com/opentelekomcloud/otcdocstheme/pull/99 are addressing same in a more reusable way


Optimization profile text

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.006%) to 99.565%

Totals

Change from base Build<PHONE_NUMBER>:
-0.006%

Covered Lines:
11641

Relevant Lines:
11644

💛  - Coveralls


Option for Ctrl-T to use current command-line content as a search pattern

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
I use CTRL-T a hundred times a day, but my brain still thinks that it is going to respect an initial query:
$ cat something<CTRL-T>

But that doesn't happen -- something has no effect here. In the same spirit as Option for Ctrl-R to use current command-line content as a search pattern -- is it possible to populate the initial query with something here?
There are a few challenges here that are a beyond me:

Once I select the file name with fzf, how do I overwrite the value (something) on the command line?
How do I make it work with a custom CTRL-T command, e.g. FZF_CTRL_T_COMMAND='fd'?

is it possible to populate the initial query with something here?

The functionality is provided by "fuzzy completion", which is by default triggered when you append a trigger sequence (default: **) then press TAB key.
# Triggering fuzzy completion
cat something**<TAB>

The added benefit is that it also can extract the directory part of the prefix and start the search from that directory.
# Start search from /tmp
# Initial query is set to "something"
cat /tmp/something**<TAB>

So in case you need this functionality, you can reach for the fuzzy completion instead of the simple CTRL-T.

However, if you find it cumbersome to type the trigger sequence (**), then you can use the configuration shown in the link below so that CTRL-T will trigger fuzzy completion even without ** (zsh only).

https://github.com/junegunn/fzf/wiki/Configuring-fuzzy-completion#dedicated-completion-key

Configuring fuzzy completion is a bit more complicated than CTRL-T, because

It should show different entries depending on the context

e.g. You want a list of processes instead of a list of file paths when you type kill -9 **<tab>

It should be able to pass the search root to the command populating the list

e.g. cat /tmp/something**<TAB>

To sum up, here's a full example of configuration options you might want to try.
# Setting CTRL-T as a dedicated completion key that doesn't require prefix (**)
#   https://github.com/junegunn/fzf/wiki/Configuring-fuzzy-completion
export FZF_COMPLETION_TRIGGER=''
bindkey '^T' fzf-completion
bindkey '^I' $fzf_default_completion

# Configuring fuzzy completion
# https://github.com/junegunn/fzf#settings
_fzf_compgen_path() {
  fd --hidden --follow --exclude ".git" . "$1"
}

# Common fzf options to use in fuzzy completion
# export FZF_COMPLETION_OPTS=...

# fzf options for each command
_fzf_comprun() {
  local command=$1
  shift
  case "$command" in
    cd)           fzf --preview 'tree -C {} | head -200'   "$@" ;;
    export|unset) fzf --preview "eval 'echo \$'{}"         "$@" ;;
    ssh)          fzf --preview 'dig {}'                   "$@" ;;
    *)            fzf --preview 'bat -n --color=always {}' "$@" ;;
  esac
}

Please let me know if you need further assistance. Thanks.

Brilliant! This is exactly what I was looking for. Works like a charm.
I made two small tweaks:

Changed the fd command so that it only respects uses .gitignore in the repository root. 98% of the time that's where I search from, and that's what I want; but if I first cd into a sub-directory (e.g. node_modules), I want to see whatever's in that directory, regardless of .gitignore.

_fzf_compgen_path() {
	[[ ! -d "$1"/.git ]] && fd_flags="-I"
	fd --hidden --follow --exclude ".git" "$fd_flags" . "$1"
}

I was getting an error with the default preview command (*)) when the match is a directory. Added a conditional to change the preview when the match is a directory:

DEFAULT_PREVIEW='[[ -d {} ]] && exa -lF --group-directories-first --color=always {} || batcat -n --color=always {}'

...
    *)  fzf --preview $DEFAULT_PREVIEW "$@" ;;

(Obviously that command will differ depending on what ls and cat utilities you use.)


Float array pointer

Firstly, great work!
We've almost completely replaced ffi-napi in our platform with ffi-rs.
Here is some background on us if you're interested: https://lumenalabs.com
We're utilizing some biosensors and Lab Streaming Layer (https://labstreaminglayer.org/#/) to track different biometrics.
We are so close, but the function we are trying to call is here:
https://github.com/sccn/liblsl/blob/master/src/lsl_outlet_c.cpp#L40C1-L42C2
LIBLSL_C_API int32_t lsl_push_sample_ft(lsl_outlet out, const float *data, double timestamp) {
	return out->push_sample_noexcept(data, timestamp);
}

And we can't seem to get it to call in a way that sends any data to our neuro-engine.
Here is how we have it defined(...):
...
lsl_push_sample_ft: {
    library: 'lsl',
    retType: DataType.Void,
    paramsType: [DataType.External, DataType.DoubleArray, DataType.Double],
 },
...

It's the second paramType - the function in c++ is defined with a pointer to a float array, which we're assuming is the issues. We've tried every DataType.*Array we can find in hopes that something would be coerced to functioning, but we can't get it.
Any suggestions or enhancements would make our day!
Thanks so much!

i wlill handle the issue at later

It seems there can not use doubleArray type transform to floatArray, i will support DataType.floatArray ASAP

Support DataType.floatArray in<EMAIL_ADDRESS>you can try with the latest version

That worked! Epic work!

I am glad that the library can help you out


Blog - What's NEXT - /math/etc/

https://hscho100.github.io/2022/01/06/Test-Blog.html
Dark Mode is cool, and TeXt is supporting it.

첫 댓글입니다! 쉽지 않네요..

$ x = \dfrac{-b\pm\sqrt{b^2-4ac}}{2a} $


[VS Code] The host's network conditions are poor or they are no longer connected to the Live Share cloud relay. Ask them to check their network conditions, restart the collaboration session, and try again.

Error:
The host's network conditions are poor or they are no longer connected to the Live Share cloud relay. Ask them to check their network conditions, restart the collaboration session, and try again.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.335

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.24.1

platformName
Windows

platformVersion
10.0.17134

Hi @ayusrirahayu , thank you for reporting this! Did you try restarting the session ? did it solved the issue? We're tracking this issue via #555  , so I'm going to close this as a duplicate of that.  On #555  , would you give us some information? What were you doing when you saw this error message (it looks like you were a guest in the middle of a Live Share session)? How often does this happen?


comprehension issue

Hello.
I an new to point cloud processing area.
I want to know what is the difference between your method and data augmentation,please?
Thanks.

Data augmentation: randomly rotate the input point clouds.
This method: for each input point cloud,  rotate it acoording to the selected rotation group, do a max-pool on all outputs to get the final feature representation of that object.

Thanks  for your reply very much!!
When you test the experiment results, you said that during training phase you rotate the input point cloud in a 4 elements rotating group, by uniformly dividing 360 degree. Then if we manually rotate input point cloud by saying 60 degree during test phase, which is not in your rotation group, how does the network helps to improve the part segmentation actually?


workbox-google-analytics disregard payload parameters when it's a POST request

Welcome! Please use this template for reporting bugs or requesting features. For questions about using Workbox, the best place to ask is Stack Overflow, tagged with [workbox]: https://stackoverflow.com/questions/ask?tags=workbox
Library Affected:
workbox-google-analytics
Browser & Platform:
Version 101.0.4951.54 (Official Build) (arm64) in macOS Monterey
Issue or Feature Request Description:
When I used workbox-google-analytics to make sure all GA requests are processed regardless of network status, I noticed that the requests are not registering on the custom dimension that I made. When I checked the reprocessed requests (GA requests processed during background sync), I noticed that a lot of payload parameters are missing (see screenshot).

When I checked the codebase (packages/workbox-google-analytics/src/initialize.ts) it seems that it does disregard the URLSearchParams if the GA request is a POST request. This might be a bug?

I fixed it in our codebase using patch-package. Let me know if this is indeed a bug, I'm happy to submit a PR request!

Hi there,
Workbox is moving to a new engineering team within Google. As part of this move, we're declaring a partial bug bankruptcy to allow the new team to start fresh. We realize this isn't optimal, but realistically, this is the only way we see it working. For transparency, here're the criteria we applied:

For PRs, we closed everything that doesn't target the current v7 branch.
For Issues, we closed everything that was created before 2024.

Thanks, and we hope for your understanding!
The Workbox team


NPM Workspaces

What version of Remix are you using?
1.3.3
Steps to Reproduce

Init a npm monorepo setup
Create a remix app directory called packages/remix and generate a remix app in there (we went with the basic setup vs stack)
Make sure the package.json name is something more unique like @some-org/remix so as not to create any obvious conflicts.
In the root dir run npm install
Run npm run dev -w @some-org/remix

Expected Behavior
Would expect given the above setup that remix runs normally and a remix dev server is started
Actual Behavior
Remix does not like that at all. It will generate a index.d.ts and a index.js file in the packages/remix dir that I think are intended for node_modules/remix.
Running the dev server or building the prod build will produce errors like in #154 about various remix deps missing definitions like MetaFunction or Link, or various generated exports.
Temporary Solution
The good news is I was able to get myself unstuck.

Rename packages/remix to nearly anything else like packages/my-app
After npm install, be sure to run npm run postinstall -w @some-org/my-app. For convenience, create a postinstall script in the root package.json that calls the remix my-app one.

That seems to be working correctly thankfully, but I suspect when it generates index.d.ts and index.js in the packages/remix dir, that is an unintended behavior caused by the remix setup naively mistaking that folder for the node_modules remix dir.

@eccentric-j It have been a long time and a lot have changed.
Is this still an issue for you?

Will try creating a mini repro repo and see if edge case still exists

Closing this out, but please re-open if you can provide a reproduction!


laravel 5.8->6.0升级 提示 requires illuminate/support ^5.1 错误

Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install laravel/framework v6.0.1
- Conclusion: don't install laravel/framework v6.0.0
- yansongda/laravel-pay v2.0.2 requires illuminate/support ^5.1

是的，暂时还不支持 L6
晚些时候将进行适配，如果紧急，可以直接使用 yansongda/pay 进行代替
感谢支持


Address inability to scroll to top one page change without janky solution

Context
When navigating to other pages on the docs site, the site wouldn't scroll to the top on page load. This should be working by default without any weird solution. However, this was addressed by making a scrollToTop component in Docusaurus' <Layout /> component.
The commit where this solution was put into place is here: https://github.com/TBD54566975/developer.tbd.website/pull/328/commits/8432f9acc2fbff6461eb6fd5837d02421bef1ae3
Note
If you remove this code, you'll notice it stops scrolling to the top on page load. To take things even further, by running window.scrollTo(0,0) inside dev tools, you'll notice it doesn't scroll to the top even though you are explicitly running a function that would do that on any website.
Not sure what this could mean, but documenting this just in case we come across any weird, related DOM issues.

@dayhaysoos I think this was solved as part of #328, no?

Closing bc Kirah fixed this (ty kirah)


Add metadata to BasicGameSaveGameInfo(Widget) + Cyberpunk saves

Adds optional metadata to the BasicGameSaveGameInfoWidget, similar to TES / Gamebryo games:
BasicGameSaveGameInfo()  # Adds "File Date" by default
BasicGameSaveGameInfo(
    get_preview = lambda p: Path(p, "screenshot.png"), # Save preview
    get_metadata = lambda p, save: {"Name": save.getName(), ...}
)

Adds metadata for Cyberpunk 2077:

Can be merged into #105
Adds a default file date to all BasicGames, taken from the save game files (GameSaveExtension etc.)

Sorry for the delay, could you try rebasing/merging against latest master so that these change can be merged? If you don't have time, I can have a look at it myself.

Sorry for the delay, could you try rebasing/merging against latest master so that these change can be merged? If you don't have time, I can have a look at it myself.

I can probably get to it tomorrow, have to check python 11 changes (my local poetry will be conflicting, too).
If I remember correctly, I made this as backwards compatible as possible, but there is at least one game, which implements BasicGameSaveGameInfoWidget, that should be tested.
From a quick search that would still be only: Black & White 2.

Rebase done. No problems besides the ugly None vs default param checks above.

Thanks for the update!
@Silarn Added save metadata preview to Blade & Sorcery recently, could you see if these could be moved to your new generic metadata system?

Obviously this would need to be merged in first but yeah, I think you can just migrate the BaSSaveGameWidget code to a new 'bas_parse_metadata' function passed into the updated BasicSaveGameInfo.

Obviously this would need to be merged in first but yeah, I think you can just migrate the BaSSaveGameWidget code to a new 'bas_parse_metadata' function passed into the updated BasicSaveGameInfo.

I added an option to set the (max) widget width and refactored blade & sorcery, should work.
Cleaned up Black & White 2, since it was not actually using its minimal custom widget.
Want me to cleanup the history before merge?

Ok, widget size, default parameter handling and an easier option to set a custom widget added:
BasicGameSaveGameInfo.with_widget(ISaveGameInfoWidget)
Widget tested with Cyberpunk.
A test for Blade & Sorcery would be good, with only the metadata.

Unfortunately I was having a requester on Discord test my initial changes. But I might be able to get a hold of him.

Commits cleaned up. Ready to merge (depending on tests)

I removed Cyberpunk BasicGameSaveGameInfo from this PR, to be included in #105.

Rebased on master, with PR #122 merged.


Links points to the wrong page

Links for FILTERGROUP Method (Record) and SETRECFILTER Method (RecordRef) takes you to the page about data types

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

ID: d3c8b6db-97af-ace5-aa2d-9b53750e409d
Version Independent ID: 51db8bb8-8aa6-d7ed-7e34-20caf23097da
Content: FilterGroup Method - Business Central
Content Source: dev-itpro/developer/methods-auto/recordref/recordref-filtergroup-method.md
Service: dynamics365-business-central
GitHub Login: @solsen
Microsoft Alias: solsen

Thanks, will be fixed with next refresh of the docs.


fix(wpa-pkgs): masterpackager.masterpackager - installer url

WinGet PR: https://github.com/microsoft/winget-pkgs/pull/75542/files

/approve-and-merge


Update README.md

I saw the render function have <Button /> in the Usage section, it might be missing the import Button on the top, so I added in the README.

Thanks for the PR!


a11y: button tags instead of role="button" in clickable SfIcon + molecules with v-focus

Related issue
Closes #1084
Scope of work
role="button" in SfIcon changed on button tags
SfCircleIcon is a button so no need to add role="button"

@justyna-13 thank you, here you can find issues for improve this PR https://github.com/DivanteLtd/storefront-ui/issues/1116


[BUG] Cannot GET / - https://<IP_ADDRESS>:3001/ doesn't work + Packer start doesn't watch SCSS changes

Describe the bug
Cannot GET / - https://<IP_ADDRESS>:3001/ doesn't work + Packer start doesn't watch changes
To Reproduce
Steps to reproduce the behavior:

npm install
npm run build
npm run deploy
See error

Expected behavior
A clear and concise description of what you expected to happen.
 So to work... I have to do => Packer Build, packer Deploy to see changes.

?

@haroldao Were you able to fix this issue?

@haroldao Were you able to fix this issue?

nope

@haroldao This looks like an SSL issue.

The website/server should load on port 3000
The assets (js/css) will load on port 3001 and require SSL working (otherwise you get the above error)
Not familiar with Vivaldi, typically though you get a warning icon next to the url lock icon if there is an SSL error (looks like the screenshot above)

Check this section out:
Packer SSL docs
Also try the ssl:check or ssl:make command
Packer SSL commands

@hayes0724 Hi, I have the same issue, and all I've done is just starting the basic project to see if it works. I've made ssl:make and ssl:check, seems to be correct. But in the browser, when I try to get an asset, it says "Website is not available". I've noticed that if I type in the browser url "https://localhost:3001/template.index.js" instead of "https://<IP_ADDRESS>:3001/template.index.js", then I can get the file


Scheduling is not working in django app on Windows

I wrote a test like
def test1():
    print("TEST1 TEST1")

print("Executed **************************************)
schedule.every(1).minutes.do(test1)

I see the print of "Executed ******", but test1 method is never called

Test script on the same virtual env is working, so the problem is in django, I suppose

same issue here - not working on my virtual env with django on my Mac

Hey there, it looks like this code is missing a call to schedule.run_pending(). You can find working examples in the docs at https://schedule.readthedocs.io/en/stable/

Still is not working
I have a django application
In urls.py (which is executed exactly once) I have code
run_tasks_hourly((check_one_week_after, check_one_week_before,check_exact_date))
and in another file I have:
def run_tasks_hourly(tasks):
    for task in tasks:
        schedule.every(1).minutes.do(task)
    schedule.run_pending()

I see in debugger that both 'schedule.every' and 'run_pending' are executed, but my tasks were never called

@pavelber  I the example above, schedule.run_pending() is called immediately after adding the task to schedule (at that point there is no task pending). Is schedule.run_pending() getting called after 1 minute also? If not, the task will not be executed.

I’m closing this issue because of inactivity.
We can always revisit this subject though! :) If you need any help, please create a new issue. Thank you!


[MNOE-243] Disable I18n by default in generator

Disable I18n when generating a new project as it won't be needed for
most projects.
This can still be enabled in the initializer if needed.

@adamaziz15 @hedudelgado FYI

👍


Linked List Questions

I want to add 3 Linked List Question in C++

Reverse a Linked List
Merge Two Sorted Linked List
Detect and remove loop in a Linked List

Kindly assign me this issue.

I want to add multiple function question based on on Linked list in C. assign to me

Can I add how to find the middle of linked list , copy linked list to a random pointer and many more questions , please assign this issue to me

can you please assign me this work
i want to contribute


ng serve does not reload on changes in beta.28.3

OS?
Windows 10
Versions.
angular-cli: 1.0.0-beta.28.3
node: 6.9.5
os: win32 x64
@angular/common: 2.4.5
@angular/compiler: 2.4.5
@angular/core: 2.4.5
@angular/forms: 2.4.5
@angular/http: 2.4.5
@angular/platform-browser: 2.4.5
@angular/platform-browser-dynamic: 2.4.5
@angular/router: 3.4.5
@angular/compiler-cli: 2.4.5
Chrome 56.0.2924.87
Repro steps.

ng new test-app
cd test-app & npm install & ng serve
add a console.log line to app.component.ts

The log given by the failure.

node console shows

webpack: compiled successfully

browser console shows

App updated. Recompiling... Nothing changed.
Mention any other details that might be useful.
Hash shown on node console never changes.
It works with v1.0.0-beta.26.

Duplicate of #4338


Edits to best practices for accessible virtual events

What page is the change request for? Please supply the URI.
https://a11y.canada.ca/en/best-practices-for-accessible-virtual-events/
Approval needed?
None
Yes, please send a request to the following person?
No response
Who shall do the work?

[ ] I will do it, I want to contribute
[X] I am asking for someone else to please do the work

Timeline
Must be updated before Feb 5 as the page is being promoted in SSC Gazette
Additional context
Best practices for accessible virtual events EN.docx

@Syracopoulos Are there changes to be done in the French page to reflect the changes on the English?

Yes, if the English edits are accepted - they need to be reflected on the French page

All pages on our site need to have a descriptive text in plain language below the heading on every page.
This text is used in many places throughout the site.

We changed it on the landing page, I want the same edits to be reflected on the page itself

Et voici le francais!
Bonnes pratiques pour les événements virtuels accessibles FR.docx