make build-image fails on Ubuntu 18.04.2 LTS with go1.12.5 and docker 18.06.2-ce

make build-image failure
checking for pkg-config... /usr/sbin/pkg-config
checking pkg-config is at least version 0.9.0... /usr/sbin/pkg-config: error while loading shared libraries: libglib-2.0.so.0: cannot open shared object file: No such file or directory
no
checking for libkmod... no
configure: error: in `/ndctl':
configure: error: The pkg-config script could not be found or is too old.  Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables KMOD_CFLAGS
and KMOD_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See `config.log' for more details
The command '/bin/sh -c ./configure ${NDCTL_CONFIGFLAGS}' returned a non-zero code: 1
Makefile:80: recipe for target 'build-image' failed
make: *** [build-image] Error 1

Environment
Kernel
5.0.11-050011-generic

OS
Ubuntu 18.04.2 LTS

Docker
Server Version: 18.06.2-ce
Storage Driver: devicemapper

Please try with the latest "devel" branch. We only had "build-image" as target for a while and went back to building multiple images. As an aside, even if we only build one, we should stick to "make build-images" instead of going back and forth.
Another change that you might not have is that switch to Clear Linux as base in the Dockerfile.
But having said that, I am confused that you are getting this error. The build should run entirely inside the Docker container and thus it shouldn't matter what you have on the host system. make build builds on the host, but that's not what's failing here.

@pohly it used to work before. In fact it worked yesterday on a different machine. So it could be that clearlinux base image or bundle contents have changed. Let me see if we need to add another bundle to the Dockerfile.

I was building today and it worked for me. Which revision of pmem-csi are you using?

Just to be sure I tried again, with success:
Step 7/34 : RUN swupd update && swupd bundle-add ${NDCTL_BUILD_DEPS} go-basic-dev && rm -rf /var/lib/swupd
 ---> Running in df1ddd1ea4a0
Update started.
Preparing to update from 29280 to 29690
Downloading packs...
...
 ---> Running in bb435ed46709
Removing intermediate container bb435ed46709
 ---> aaa3f4f7f76d
Successfully built aaa3f4f7f76d
Successfully tagged localhost:5000/pmem-csi-driver-test:canary

This with current "devel" = 0d0f7f8e2823b2149d39802df316e783e30c1c11.

I tried to build as well, and it works on a Ubuntu 18.04.2 host.
I see similar version indication by line Preparing to update from 29280 to 29690 in output
The section where your configure hits trouble, looks OK in my build:
checking for pkg-config... /usr/sbin/pkg-config
checking pkg-config is at least version 0.9.0... yes

I tried to verify it's not by cached good state by pruning all docker caches, works after that as well.
Was there some problem with base image that got fixed soon after?
Can you still see the same problem?


Firefox 55+ and checkboxes

Firefox 55 does not show checkboxes for most webextensions this includes textarea cache lite.

Could you please add more detail or add some screenshots for your report?

When you go to the options of the addon if the addon has checkboxes there in firefox 55+ those checkboxes do not show up.

Thank you!

hi @rayman89 ,
I just install ff v55.0b13 , and go to option page of TCL
The checkbox is there safe and sound. like this

Could you confirm whether this problem still happen or not? if it is, please provide the OS version for me (Win7, macOS Sierra, ... etc) thank you :)

Checkboxes are showing now probably firefox fixed it.


[SPARK-35598] Improve Spark-ML PCA analysis

What changes were proposed in this pull request?

When performing a PCA, the covariance matrix is calculate first.
In the function RowMAtrix.computeCovariance() there is the following code:
    if (rows.first().isInstanceOf[DenseVector]) {
      computeDenseVectorCovariance(mean, n, m)
    } else {
      computeSparseVectorCovariance(mean, n, m)
    }

As can be seen, there are two different function to compute the covariance matrix depending on whether the matrix is sparse or dense. Now, the decision if the matrix is sparse or dense is based only on the type of the first row (DenseVector or SparseVector).
I propose to calculate the sparsity of the matrix, as the ratio between number-of-zeros and total-number-of elements. And use the sparsity to switch between the two functions.
In later pull request #32734 the code checks that all rows are SparseVector, if all rows are sparse it uses the sparse covariance computation.
Still, I would prefer to have the switch based on the actual sparsity of the matrix, rather than on its implementation. To notice you can have 2 matrices, with same elements and same number of zeros, implemented with SparseVector or DenseVector.
Why are the changes needed?

Have more consistent results. With my implementation 2 matrices with same elements produce same results, independently if they are implemented using SparseVector or using DenseVector
Does this PR introduce any user-facing change?

No
How was this patch tested?

I added 2 tests in the RowMatrixSuite.scala to verify that the sparsity is calculated properly.

Can one of the admins verify this patch?

Sure it can be verified performing a PCA analysis, the one in the doc, for example.
There are also PCA test in the RowMatrixSuite

Ping @Antozamm


Failed to start the kernel - Jupyter Notebook error

I had an issue importing cv2 into python3,9 env A, so i created env gg with python 3.8. Now i got this error when opening a new jupyter notebook in this environment. Im not too familiar with troubleshooting so anything would be appreciated. thank you!
Traceback (most recent call last):
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\web.py", line 1704, in _execute
result = await result
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 769, in run
yielded = self.gen.throw(*exc_info)  # type: ignore
File "D:\Anaconda3\envs\gg\lib\site-packages\notebook\services\sessions\handlers.py", line 69, in post
model = yield maybe_future(
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 762, in run
value = future.result()
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 769, in run
yielded = self.gen.throw(*exc_info)  # type: ignore
File "D:\Anaconda3\envs\gg\lib\site-packages\notebook\services\sessions\sessionmanager.py", line 88, in create_session
kernel_id = yield self.start_kernel_for_session(session_id, path, name, type, kernel_name)
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 762, in run
value = future.result()
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 769, in run
yielded = self.gen.throw(*exc_info)  # type: ignore
File "D:\Anaconda3\envs\gg\lib\site-packages\notebook\services\sessions\sessionmanager.py", line 100, in start_kernel_for_session
kernel_id = yield maybe_future(
File "D:\Anaconda3\envs\gg\lib\site-packages\tornado\gen.py", line 762, in run
value = future.result()
File "D:\Anaconda3\envs\gg\lib\site-packages\notebook\services\kernels\kernelmanager.py", line 176, in start_kernel
kernel_id = await maybe_future(self.pinned_superclass.start_kernel(self, **kwargs))
File "D:\Anaconda3\envs\gg\lib\site-packages\jupyter_client\multikernelmanager.py", line 185, in start_kernel
km.start_kernel(**kwargs)
File "D:\Anaconda3\envs\gg\lib\site-packages\jupyter_client\manager.py", line 313, in start_kernel
self.kernel = self._launch_kernel(kernel_cmd, **kw)
File "D:\Anaconda3\envs\gg\lib\site-packages\jupyter_client\manager.py", line 222, in _launch_kernel
return launch_kernel(kernel_cmd, **kw)
File "D:\Anaconda3\envs\gg\lib\site-packages\jupyter_client\launcher.py", line 134, in launch_kernel
proc = Popen(cmd, **kwargs)
File "D:\Anaconda3\envs\gg\lib\subprocess.py", line 854, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "D:\Anaconda3\envs\gg\lib\subprocess.py", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified

Doesn't sound like it is related to IJulia?


output html file size

After converting this file - https://github.com/alexkmbk/1CI/blob/master/README_RU.md with --export option, I've got 553 KB output html file size.
-why it is so large (the image linked to it just around 20KB)
-Is there a way to decrease the size of output files?

This is because the downloaded styles (which make the page look like GitHub) are being injected into the exported HTML file.
You can save size by not inlining the styles:
$ grip --export --no-inline README_RU.md

The resulting file is around 45KB.
But now your output won't be styled correctly because Grip isn't there to fulfill those static assets:
<link rel="icon" href="/__/grip/static/favicon.ico" />
  <link rel="stylesheet" href="/__/grip/asset/frameworks-e53fc1ddbde2a9e5645df620f65c80ef723c741b33293b6f22a2b7f2c8145fcf.css" />
  <link rel="stylesheet" href="/__/grip/asset/github-4664ce357daee067bd8ee8e99e0833d04b115022dbf4ca637241c0f7d1f832b7.css" />
  <link rel="stylesheet" href="/__/grip/asset/site-4b977eeae4ecbfd2f7a7ad7788382645b21e771bbf47835e3793edb12292ff2e.css" />

One option is to create the __/grip/asset/ directory alongside your README_RU.html output, put the assets that grip serves in there (run grip on your README, view source, and download the assets from there), and serve that with python -m SimpleHTTPServer (or -m http.server if you're using Python 3).
Another option is to hot-link direct back to GitHub. Be aware that GitHub changes their assets and filenames every now and then though.
So using --no-inline is less portable, since you'll always have to link back to some copy of the assets when you view the rendered output, but can useful if you're exporting many files and reuse the assets. It's also useful if don't need the assets at all.
Hope this helps!

Thank you very much! Btw, it looks like the grip utility now is one of the best.

@alexkmbk Glad that helped. Thanks :smiley:


UseHealthChecks vs. MapHealthChecks /5

Fixes #29421

Internal previews

📄 File
🔗 Preview link

aspnetcore/host-and-deploy/health-checks.md
Health checks in ASP.NET Core

@JuergenGutsch please review. It's way too long, should I cut most of that out?

@ngbrown please review

@CarlosLanderas @jods4 @mettelephant @FirstAfterGod2501 @bhugot please review

@Rick-Anderson I think the updated explanation looks good.

@Rick-Anderson Not sure why I'm pinged on this doc change?
I commented on health checks before, it was to ask for a way to register health checks through DI. I don't think this change is related?

@Rick-Anderson I'm also not sure why I was pinged for this change either. I've opened an issue on health check logging before, but it doesn't seem to be related to this change.

@JuergenGutsch please review. It's way too long, should I cut most of that out?

I seems like in .NET 8 we will be able to write app.MapHealthChecks("/healthz").ShortCircuit();, see #28935
I think this should also be mentioned here.

I seems like in .NET 8 we will be able to write app.MapHealthChecks("/healthz").ShortCircuit();, see #28935 I think this should also be mentioned here.

That was added in #29110

I seems like in .NET 8 we will be able to write app.MapHealthChecks("/healthz").ShortCircuit();, see #28935 I think this should also be mentioned here.

See #29709


Scroll down to reviews when clicking review link in product details

In #1111, we changed 'write a review' to 'show reviews'
when you click that link, the tab changes, all good.
however can we scroll down to the reviews?

closing as i should have cleared my cache, works


Corrupted graphs need to be rerun at some point

While running the parallel converter some graphs failed to be read -- I decided to assemble them here.
NKI-ENH_0186697_biggraphs.graphml
Jung2015_M87160886_biggraphs.graphml
Jung2015_M87164774_biggraphs.graphml
Jung2015_M87183242_biggraphs.graphml
Jung2015_M87109104_biggraphs.graphml
Jung2015_M87138290_biggraphs.graphml
@gkiar please reassign as necessary

Is it obvious what's wrong?  I'm curious if big graphs are failing to run
(perhaps file size << normal graph) or corrupted in some less obvious way.
Best,
Will
On Mon, Oct 12, 2015 at 12:05 PM, Disa Mhembere<EMAIL_ADDRESS>wrote:

While running the parallel converter some graphs failed to be read -- I
decided to assemble them here.
NKI-ENH_0186697_biggraphs.graphml
Jung2015_M87160886_biggraphs.graphml
Jung2015_M87164774_biggraphs.graphml
Jung2015_M87183242_biggraphs.graphml
Jung2015_M87109104_biggraphs.graphml
Jung2015_M87138290_biggraphs.graphml
@gkiar https://github.com/gkiar please reassign as necessary
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/m2g/issues/157.

That would work for some, but sadly not all. The igraph write operation
seems to not be not atomic from what I can tell, so pretty large files that
are partial writes exist.
On Mon, Oct 12, 2015 at 12:16 PM, William Gray<EMAIL_ADDRESS>wrote:

Is it obvious what's wrong? I'm curious if big graphs are failing to run
(perhaps file size << normal graph) or corrupted in some less obvious way.
Best,
Will
On Mon, Oct 12, 2015 at 12:05 PM, Disa Mhembere<EMAIL_ADDRESS>wrote:

While running the parallel converter some graphs failed to be read -- I
decided to assemble them here.
NKI-ENH_0186697_biggraphs.graphml
Jung2015_M87160886_biggraphs.graphml
Jung2015_M87164774_biggraphs.graphml
Jung2015_M87183242_biggraphs.graphml
Jung2015_M87109104_biggraphs.graphml
Jung2015_M87138290_biggraphs.graphml
@gkiar https://github.com/gkiar please reassign as necessary
—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/m2g/issues/157.

—
Reply to this email directly or view it on GitHub
https://github.com/openconnectome/m2g/issues/157#issuecomment-147449644.

Believe I've redone all of these. Reopen if I'm wrong, @disa-mhembere


Running without a build

Hi, I'm in the middle of testing this library. Is it possible to use it without a build step? It works with webpack, but currently my whole projects runs without a need for build, so I can make changes and iterations very quickly. Helps a lot with debugging too :)
The server runs it fine with just require, but client doesn't seem compatible with ES6 import. So I'm wondering whether it's possible to bundle it up for the client, like geckos.io?

Yes, I can do that. I'm on vacation right now, but I will try to do it as quickly as possible.

Thanks man. Have a great vacation!
I dont mean to hurry you up in any way, please do it whenever you feel like it, but Im just hoping to know if it's a matter of days or weeks or more?

You're welcome. I guess <10 days.

Done.
Checkout the README file.

Thanks!


Cannot kill process

Version: <IP_ADDRESS> | axocover
Reason
System.ComponentModel.Win32Exception: Acesso negado
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/465309/app_versions/34/crash_reasons/169403772

Fixed in https://github.com/axodox/AxoTools/releases/tag/release-1.0.163


Allow global configuration of tslint.json

It's nice to have a configuration by projects of tslint rules, but it can be useful to have only one set of rules for every projects that are gonna be analyze by one instance of SonarQube.

It's not a bad shout. At the same time we'd have to make the custom rules directory globally-configurable too, but both are trivial changes. Will see about it tomorrow.


[BUG] upgrade stuck in waiting plan restart-rancher-system-agent to complete

Describe the bug
Upgrade pending on Upgradeing System Service, when check the log of pod apply-manifests, it shows

Waiting for plan hvst-upgrade-fm29b-skip-restart-rancher-system-agent to complete...

To Reproduce
Steps to reproduce the behavior:

Install Harvester with any nodes
Create an image for VM creation
Create Cluster network and VM network
Setup backup-target
Create new storageclass sc1 with 3 replicas and set it as default
Create VM vm1 with VM network's VLAN
Write data into vm1 then take backup vm1b
Restore vm1b into vm2
Create VM vm3 with additional volume
Perform upgrade

Expected behavior
upgrade should success
Environment:

Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal DL360 3 nodes
Harvester ISO version: v1.2.1 -> v1.2.2-rc1
ui-source Option: Auto

Additional context
The upgrade is performed by test automation (locally)
Support bundle
supportbundle_229d2fc0-5c52-42e2-a10e-9cd6a437adb1_2024-04-26T07-43-07Z.zip

Hit in a 3 nodes upgrade test from v1.2.1 -> v1.2.2-rc2

The plan object hvst-upgrade-fm29b-skip-restart-rancher-system-agent has no status field from the support-bundle; but other plan objects have.
- apiVersion: upgrade.cattle.io/v1
  kind: Plan
  metadata:
    creationTimestamp: "2024-04-25T20:55:07Z"
    generation: 1
    managedFields:
    - apiVersion: upgrade.cattle.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:spec:
          .: {}
          f:concurrency: {}
          f:nodeSelector:
            .: {}
            f:matchLabels:
              .: {}
              f:harvesterhci.io/managed: {}
          f:serviceAccountName: {}
          f:tolerations: {}
          f:upgrade:
            .: {}
            f:args: {}
            f:command: {}
            f:image: {}
          f:version: {}
      manager: kubectl-create
      operation: Update
      time: "2024-04-25T20:55:07Z"
    name: hvst-upgrade-fm29b-skip-restart-rancher-system-agent
    namespace: cattle-system
    resourceVersion: "363026"
    uid: 245884a7-fc5f-426f-a7ad-ce87c9f8ed79
  spec:
    concurrency: 10
    nodeSelector:
      matchLabels:
        harvesterhci.io/managed: "true"
    serviceAccountName: system-upgrade-controller
    tolerations:
    - operator: Exists
    upgrade:
      args:
      - sh
      - -c
      - set -x && mkdir -p /run/systemd/system/rancher-system-agent.service.d && echo
        -e '[Service]\nEnvironmentFile=-/run/systemd/system/rancher-system-agent.service.d/10-harvester-upgrade.env'
        | tee /run/systemd/system/rancher-system-agent.service.d/override.conf &&
        echo 'INSTALL_RKE2_SKIP_ENABLE=true' | tee /run/systemd/system/rancher-system-agent.service.d/10-harvester-upgrade.env
        && systemctl daemon-reload && systemctl restart rancher-system-agent.service
      command:
      - chroot
      - /host
      image: registry.suse.com/bci/bci-base:15.4
    version: 72c4fe8c

The system-upgrade-controller seems to have issue from 2024-04-25T20:51:55
rancher-79d47f56-kjzkl/rancher.log

2024-04-25T20:51:55.627240258Z 2024/04/25 20:51:55 [ERROR] error syncing 'fleet-local/local': handler monitor-system-upgrade-controller-readiness: unable to sync system upgrade controller status for [&TypeMeta{Kind:Cluster,APIVersion:provisioning.cattle.io/v1,}] [fleet-local/local], status.FleetWorkspaceName was blank, requeuing
2024-04-25T20:51:55.758930047Z 2024/04/25 20:51:55 [INFO] [planner] rkecluster fleet-local/local: configuring bootstrap node(s) custom-5c1eb391c3d4: waiting for plan to be applied
2024-04-25T20:51:55.940208473Z 2024/04/25 20:51:55 [ERROR] error syncing 'fleet-local/local': handler monitor-system-upgrade-controller-readiness: unable to sync system upgrade controller status for [&TypeMeta{Kind:Cluster,APIVersion:provisioning.cattle.io/v1,}] [fleet-local/local], status.FleetWorkspaceName was blank, requeuing
2024-04-25T20:51:56.080572880Z 2024/04/25 20:51:56 [INFO] [planner] rkecluster fleet-local/local: configuring bootstrap node(s) custom-5c1eb391c3d4: waiting for plan to be applied
2024-04-25T20:51:56.083257126Z 2024/04/25 20:51:56 [ERROR] error syncing 'fleet-local/local': handler monitor-system-upgrade-controller-readiness: unable to sync system upgrade controller status for [&TypeMeta{Kind:Cluster,APIVersion:provisioning.cattle.io/v1,}] [fleet-local/local], status.FleetWorkspaceName was blank, requeuing
...

The provisioning.cattle.io/v1 cluster ojbect fleet-local/local object has no status
fleetWorkspaceName: fleet-local   (refer the output in another thread: https://github.com/harvester/harvester/issues/5718#issuecomment-2094048513)
apiVersion: v1
items:
- apiVersion: provisioning.cattle.io/v1
  kind: Cluster
  metadata:
    annotations:
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"provisioning.cattle.io/v1","kind":"Cluster","metadata":{"annotations":{},"name":"local","namespace":"fleet-local"},"spec":{"kubernetesVersion":"v1.25.9+rke2r1","rkeConfig":{"controlPlaneConfig":{"disable":["rke2-snapshot-controller","rke2-snapshot-controller-crd","rke2-snapshot-validation-webhook"]}}}}
      objectset.rio.cattle.io/applied: H4sIAAAAAAAA/4yQzU7DMBCEXwXt2Slt079Y4oAQ4sCVF9jYS2Ow15G9CYfK746SVqJC4udo78xovjlBIEGLgqBPgMxRUFzkPD1j+0ZGMskiubgwKOJp4eKts6ChT3F02UV2fKyMH7JQqkwiFAL1ozV+MKXqOL6DhoCMRwrEciUYa3Xz7NjePZwj/8xiDAQafDTo/yXOPZrJAUXB3NdFfnGBsmDoQfPgvQKPLflfR+gwd6Bhu9ztt3XdUGNwc7Crdr9u6jW1y/pg91vb2LXdbHarA6jzYpbSVwho6DCNNIMWBd9Yrtu+eiKpzpeiIPdkpnbzx2Wq+0G6R7Z9dCygT2WSCcpwwciURrJPxJRmZtDLUj4DAAD//5CVWGcAAgAA
      objectset.rio.cattle.io/id: provisioning-cluster-create
      objectset.rio.cattle.io/owner-gvk: management.cattle.io/v3, Kind=Cluster
      objectset.rio.cattle.io/owner-name: local
      objectset.rio.cattle.io/owner-namespace: "null"
    creationTimestamp: "2024-04-25T14:02:00Z"
    finalizers:
    - wrangler.cattle.io/provisioning-cluster-remove
    - wrangler.cattle.io/rke-cluster-remove
    generation: 2
    labels:
      objectset.rio.cattle.io/hash: 50675339e9ca48d1b72932eb038d75d9d2d44618
      provider.cattle.io: harvester
    managedFields:
    - apiVersion: provisioning.cattle.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            .: {}
            f:objectset.rio.cattle.io/applied: {}
            f:objectset.rio.cattle.io/id: {}
            f:objectset.rio.cattle.io/owner-gvk: {}
            f:objectset.rio.cattle.io/owner-name: {}
            f:objectset.rio.cattle.io/owner-namespace: {}
          f:finalizers:
            .: {}
            v:"wrangler.cattle.io/provisioning-cluster-remove"null: {}
            v:"wrangler.cattle.io/rke-cluster-remove"null: {}
          f:labels:
            .: {}
            f:objectset.rio.cattle.io/hash: {}
            f:provider.cattle.io: {}
        f:spec:
          .: {}
          f:localClusterAuthEndpoint: {}
      manager: rancher
      operation: Update
      time: "2024-04-25T14:02:00Z"
    - apiVersion: provisioning.cattle.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:metadata:
          f:annotations:
            f:kubectl.kubernetes.io/last-applied-configuration: {}
        f:spec:
          f:kubernetesVersion: {}
          f:rkeConfig: {}
      manager: kubectl-client-side-apply
      operation: Update
      time: "2024-04-25T14:03:35Z"
    - apiVersion: provisioning.cattle.io/v1
      fieldsType: FieldsV1
      fieldsV1:
        f:status:
          .: {}
          f:clientSecretName: {}
          f:clusterName: {}
          f:conditions: {}
          f:observedGeneration: {}
          f:ready: {}
      manager: rancher
      operation: Update
      subresource: status
      time: "2024-04-25T20:55:00Z"
    name: local
    namespace: fleet-local
    resourceVersion: "362895"
    uid: 0d2d4ee9-3158-4651-9025-e7a009e84b0d
  spec:
    kubernetesVersion: v1.25.9+rke2r1
    localClusterAuthEndpoint: {}
    rkeConfig: {}
  status:
    clientSecretName: local-kubeconfig
    clusterName: local
    conditions:
    - lastUpdateTime: "2024-04-25T14:04:38Z"
      message: marking control plane as initialized and ready
      reason: Waiting
      status: Unknown
      type: Ready
    - lastUpdateTime: "2024-04-25T14:02:00Z"
      status: "False"
      type: Reconciling
    - lastUpdateTime: "2024-04-25T14:02:00Z"
      status: "False"
      type: Stalled
    - lastUpdateTime: "2024-04-25T14:03:35Z"
      status: "True"
      type: Created
    - lastUpdateTime: "2024-04-25T20:55:00Z"
      status: "True"
      type: RKECluster
    - status: Unknown
      type: DefaultProjectCreated
    - status: Unknown
      type: SystemProjectCreated
    - lastUpdateTime: "2024-04-25T14:02:13Z"
      status: "True"
      type: Connected
    - lastUpdateTime: "2024-04-25T14:29:17Z"
      status: "True"
      type: Updated
    - lastUpdateTime: "2024-04-25T14:29:17Z"
      status: "True"
      type: Provisioned
    observedGeneration: 2
    ready: true
kind: List
metadata:
  continue: "null"
  resourceVersion: "978153"

@w13915984028 could you help to check is it the same root cause of the original case?
I saw that @albinsun's cluster have RKE2 cluster running on it, but the original case haven't.

I guess our lastest PRs (restart fleet-agent) may have solved this issue. Please re-validate it on v1.2.2-RC3 release.

I additionally have hit this with rc2 - going to re-check with rc3

bumped to reproduce/often as seems theme with v1.2.2-rc2

I did not notice this on v1.2.2-rc3

Hit in a 3 nodes upgrade test from v1.2.1 -> v1.2.2-rc2. Will test again after RC3 release.

Provide my test run statistics.
I did not hit this too in about 5 trials on the 3 nodes upgrade v1.2.1 to v1.2.2-rc3 (w/ Rancher and RKE2 guest cluster.)

Closing this in favor of above comments.


Local import path

Hello!
I have a private project in which I need to include custom import formatting rules and I can't / do not want to publish import-sort-style-* module. Is there a way I could import plugin from local project directory?
As a workaround I am using ln -s ../import-sort-style-mystyle ./node_modules, but is there a cleaner way?
EDIT:
I am using this plugin file so it makes no purpose to publish this as an NPM module. It relies too strongly on project specific directory structure:
function isLocalClass(imported) {
  return imported.moduleName.startsWith("src/framework/classes");
}

function isLocalComponent(imported) {
  return imported.moduleName.startsWith("src/components");
}

function isLocalEffect(imported) {
  return imported.moduleName.startsWith("src/effect");
}

function isLocalHelper(imported) {
  return imported.moduleName.startsWith("src/framework/helpers");
}

function isLocalInterface(imported) {
  return imported.moduleName.startsWith("src/framework/interfaces");
}

function isLocalModule(imported) {
  return imported.moduleName.startsWith("src/");
}

function isLocalType(imported) {
  return imported.moduleName.startsWith("src/framework/types");
}

function format(styleApi) {
  const {
    and,
    hasDefaultMember,
    hasNamedMembers,
    hasNamespaceMember,
    hasNoMember,
    hasOnlyDefaultMember,
    hasOnlyNamedMembers,
    hasOnlyNamespaceMember,
    isAbsoluteModule,
    isRelativeModule,
    member,
    name,
    naturally,
    not,
    or,
    startsWithAlphanumeric,
    startsWithLowerCase,
    startsWithUpperCase,
  } = styleApi;

  return [
    {
      match: and(
        hasNamespaceMember,
        not(isLocalModule)
      ),
      sort: member(naturally),
    },
    {
      match: and(
        hasOnlyDefaultMember,
        not(isLocalModule)
      ),
      sort: member(naturally),
    },
    {
      match: not(isLocalModule),
      sort: member(naturally),
    },
    { separator: true },

    // import Foo from "src/components/Foo"
    {
      match: isLocalComponent,
      sort: member(naturally),
    },
    { separator: true },

    // import useFoo from "src/effects/useFoo"
    {
      match: isLocalEffect,
      sort: member(naturally),
    },
    { separator: true },

    // import Foo from "src/framework/classes/Foo"
    // import foo from "src/framework/helpers/foo"
    {
      match: and(
        hasOnlyDefaultMember,
        or(
          isLocalClass,
          isLocalHelper
        ),
      ),
      sort: member(naturally),
    },
    {
      match: or(
        isLocalClass,
        isLocalHelper
      ),
      sort: member(naturally),
    },
    { separator: true },

    // import Foo from "src/framework/interfaces/Foo"
    // import Foo from "src/framework/types/Foo"
    {
      match: and(
        hasOnlyDefaultMember,
        or(
          isLocalInterface,
          isLocalType,
        ),
      ),
      sort: member(naturally),
    },
    {
      match: or(
        isLocalInterface,
        isLocalType,
      ),
      sort: member(naturally),
    },
    { separator: true },
  ];
}

module.exports = format;

Also, overall I am really grateful for this project. It really saves a lot of time and effort to keep everything in order. :)

Side note: using Yarn portal / link protocols might help here as a workaround also:
https://next.yarnpkg.com/features/protocols

This is great and should be added to the README !

Hi @mcharytoniuk we are using it with a scoped package and it works like a charm 👍
just add it like this into package.js
  "importSort": {
    ".js, .jsx, .es6, .es, .mjs, .ts, .tsx": {
      "style": "@npmjsAccount/import-sort-style-your-style"
    }
  }

@naume sorry, but it does not solve the issue. I really do not want to use npm or any other registry and just import the file directly from the project.

@naume ok, I thought this through and you can actually use something like https://github.com/lerna/lerna to keep packages in one repo and use namespaces like you mentioned. Did you have something like that in mind?

@mcharytoniuk Hi, how did you managed to make it work with yarn portal? I've added sth like this to devDependencies "import-sort-style-daniel": "file:./config/import-sort-style",. It is a folder with index.ts and package.json inside. I do call yarn and it is properly moved to node_modules but I still got an error when using it:
▶ ./node_modules/import-sort-cli/lib/index.js ./src/components/Current.js

src/components/Current.js:
Error: Style "daniel" could not be resolve

@dkoprowski Did you config the package.json correctly? Because I'm using the same syntax "import-sort-style-daniel": "file:./config/import-sort-style" and it worked for me (with npm though)


More generics around usages of ExceptionHandler.java

We've pushed the generics for exception handler around a bit more so that the disruptor and exceptionHandler tie up.
Things to look out for in your review:

we've converted some usages of <?> to
we've convinced ourselves that the cast in ExceptionHandlerSetting  with  will work out ok - but this bit felt a little dodgy.

Cheers, merged.


feat: factor out parseFrameMessage

What changed? Why?
While working with frames, it's beneficial to be able to get the whole validated message. Since we parse and validate the message as part of getFrameAccountAddress, I pulled the relevant code out into a new function.
Notes to reviewers
How has it been tested?
yolo'd this, would love to hear any strategies for testing
edit: did manually test in a frame by copying code over and it appears to work

Ciao @cnasc, after merging https://github.com/coinbase/onchainkit/pull/28 form @robpolak we got some conflic. Love your idea of parseFrameMessage, please resolve the conflict and go ahead with it.

Ehm @robpolak's tests are broken in this PR

😅 @cnasc can you help us get on a solid testing case, so that we can add it in CI, and than deploy, please.
Ideally would be dope to release a new OnchainKit version in the next couple of hours.


Update make_changelog.py to support semver

What is the purpose of this change?
Update make_changelog.py to support semver which rclone started using from v1.47.0 onwards.

Was the change discussed in an issue or in the forum before?

Checklist

[x] I have read the contribution guidelines.
[ ] I have added tests for all changes in this PR if appropriate.
[ ] I have added documentation for the changes if appropriate.

[x] I'm done, this Pull Request is ready for review :-)

Nice one - thanks :-)


[Sanitization] Sanitize user input before it is used

When the frontend sends us user input, we should sanitize all fields to prevent malicious data from circulating through the application.

User input is already sanitized by React.


fix benchmark.js bug

Coverage remained the same at 100.0% when pulling 17138c58875b135544c4f581bdbe967c8e7c0037 on benchmark-fix into 04ff3be1f13647c4769bb74bef9d3d6f04f273d0 on master.


Unable to update via HACS

Hi,
I followed the instructions in the pinned issue, but was not able to solve the installation issue.

I've uninstalled and tried to install again, but I receive the error mentioned above.

It looks like I was to fast in reporting the issue.
Steps that solved the issue for me:

remove current version (1.3.2)
restart HA
try install 1.3.8 => fail
try install 1.3.2 => success
try install 1.3.8 => fail
try install 1.3.7 => success
try install 1.3.8 => success


t

Steps to Reproduce

...
...
...

Logs

Logs

ok

@tagesholly1
please describe the bug or the feature request


Ingress not working when rbac.namespaced=true

When rbac.namespaced is set to true the following error pops up in the logs:
reflector.go:127] pkg/mod/k8s.io/client-go@v0.19.2/tools/cache/reflector.go:156: Failed to watch *v1beta1.IngressClass: failed to list *v1beta1.IngressClass: ingressclasses.networking.k8s.io is forbidden: User "system:serviceaccount:develop:traefik-ingress-controller" cannot list resource "ingressclasses" in API group "networking.k8s.io" at the cluster scope

This seems to cause that Ingress resources won't be processed. When rbac.namespaced is false, this does not happen as in that case the correct permissions in networking.k8s.io are set in the ClusterRole.

I think this is something I fixed, with the following PR: #337 ( https://github.com/traefik/traefik-helm-chart/pull/337/files#diff-f4430485e5002c71e33daa985c34e0fe4e4738a271c697ba0b1aaaba1718e041 )
That was not my issue, though I did notice there's nothing allowing access to IngressClasses, when traefik is deployed with namespaces rbac.


Hello World Example and Contributions?

Hi there, I am evaluating different open source node graph projects for Unity as the basis for other tools I'm writing, both internal and also open source. I like this one because the appearance matches the newer native Unity graph tools and that its available as a package (easy dependency management). I have a couple of questions for you when you have a chance:

Do you have a hello world example available somewhere that would demonstrate how to setup a basic graph? I see you have several screenshots on the readme demonstrating the nodes/graphs, but other than the WIP project linked here I'm not sure where to get started. I have followed some of the wiki instructions for creating nodes, graph views, but am not sure where to go from there.
If I ended up using this I'd like to help contribute bug fixes/features as I can; how do you want contributions to be made, do you have any particular style guide for code, and is Trello the main backlog source for this project?

Thanks!

Hey,
Indeed this project uses the new API for graph visualization in Unity: GraphView as well as some recent C# features :)

Do you have a hello world example available somewhere

All the screenshots from the readme are avaliable in this project (Example folder), it also contains very simple implementation of graph like this one: https://github.com/alelievr/NodeGraphProcessor/tree/master/Assets/Examples/Editor/05_All which is a good starting point since it only have a toolbar and all basic graph functionality. As for asset management (open the graph when opening the asset), you can have a look at this file: https://github.com/alelievr/NodeGraphProcessor/blob/master/Assets/Examples/Editor/GraphAssetCallbacks.cs, it uses standard Unity API to open the graph window from the asset.
Mixture is a much more advanced project without any documentation so I wouldn't recommend it as starting point, but if you already know the API / code it can provide some useful examples (I still need to write the readme though)

If I ended up using this I'd like to help contribute bug fixes/features as I can

Every pull requests is welcomed :) I'll review them when i have some time to spend on the project.
I don't really enforces any coding convention, as long as the code is clean, commented and readable.
And for trello, i think i'll move most of it to a Github project to make issue tracking and feature requests more visible and accessible.

Hey,
Indeed this project uses the new API for graph visualization in Unity: GraphView as well as some recent C# features :)

Do you have a hello world example available somewhere

All the screenshots from the readme are avaliable in this project (Example folder), it also contains very simple implementation of graph like this one: https://github.com/alelievr/NodeGraphProcessor/tree/master/Assets/Examples/Editor/05_All which is a good starting point since it only have a toolbar and all basic graph functionality. As for asset management (open the graph when opening the asset), you can have a look at this file: https://github.com/alelievr/NodeGraphProcessor/blob/master/Assets/Examples/Editor/GraphAssetCallbacks.cs, it uses standard Unity API to open the graph window from the asset.
Mixture is a much more advanced project without any documentation so I wouldn't recommend it as starting point, but if you already know the API / code it can provide some useful examples (I still need to write the readme though)

Thanks for the heads up, I'll have to check that out. I've attempted to clone this repo and checkout the master branch, but strangely enough my GIT client has been crashing from what appears to be pulling the ShaderGraph submodule.

Is this submodule still needed? It appears that the code at that repo is no longer up-to-date and has moved to a separate repository.

If I ended up using this I'd like to help contribute bug fixes/features as I can

Every pull requests is welcomed :) I'll review them when i have some time to spend on the project.
I don't really enforces any coding convention, as long as the code is clean, commented and readable.
And for trello, i think i'll move most of it to a Github project to make issue tracking and feature requests more visible and accessible.

Sounds great, looking forward to it! 👍

Is this submodule still needed? It appears that the code at that repo is no longer up-to-date and has moved to a separate repository.

I didn't see that there was still the old git submodule in this repo it's not used anymore. I just deleted it in 5889bc95f5659dd8d6a1ccf15e51183ab73e2031, thanks :)


tagalign enabled

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en

Pull request type

Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no api changes)
[x] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: #967
What is the new behavior?

Other information

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (321be1b) 67.41% compared to head (e82b735) 38.51%.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #993       +/-   ##
===========================================
- Coverage   67.41%   38.51%   -28.90%
===========================================
  Files         261      207       -54
  Lines       24686    21410     -3276
===========================================
- Hits        16641     8247     -8394
- Misses       7177    12815     +5638
+ Partials      868      348      -520

Flag
Coverage Δ

?

go-1.17.x
38.51% <ø> (-27.30%)
:arrow_down:

go-1.20.x
?

go-1.21.x
?

integration
?

macOS
?

ubuntu
38.51% <ø> (-0.31%)
:arrow_down:

unit
38.51% <ø> (-0.40%)
:arrow_down:

windows
?

ydb-22.5
?

ydb-23.1
?

ydb-23.2
?

ydb-23.3
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[react-i18n] Allows using short aliases for "i18n.translate"

Overview
For increased DX and terseness of the codebase, it would be nice if we could use a short alias for i18n.translate, so that:
// Instead of
<MyComponent title={i18n.translate('MyComponent.Something')}>

// on could write
<MyComponent title={_t('MyComponent.Something')}>

This is in theory possible by aliasing the import of i18n from the hook like:
const [{translate: _t}] = useI18n();

but for some reason this is failing with Cannot destructure property 'pseudolocalize' of 'this' as it is undefined.. The failure happens at this exact place as soon as the code tries using _t(). This happens inside a child component of SharedTranslations, if that could be of interest.
Suggested solutions:

Is the destructure failure "fixable"? In that case there is nothing to ask for
Is it possible to just provide an alias at the hook level, so to return _t as in const {_t} = useI18n()?

Type

[x] Changes to existing features

Motivation
This is for the sake of code readability, without having to mentally skip over a lot of long "i18.translate", which also can save some word wrapping.

Is the destructure failure "fixable"? In that case there is nothing to ask for

When you do const [i18n] = useI18n(); i18n is an instance of the I18n class. You can't use destructuring on a class when the class relies upon this to reference the other methods on the class because the destructuring destroys the reference to this.
Changing I18n from a class to some stateless object is almost certainly not possible as it relies upon a lot of state (see all the stuff that gets set in its constructor) and would be a major breaking change if it was even possible. Thus I do not believe that it is possible to make this change.


Kernel interrupt causes kernel to crash

interrupting the kernel will cause the kernel to crash, which then loses the entire kernel context of previous execution
Repro steps in screenshot below.

This is by design. A kernel interrupt is throwing an exception. If the python code running doesn't handle it, it can cause the entire process to die.
Jupyter behaves this way too.

I apologize if im missing something,
But in Jupyter, the kernel doesnt get restarted if it is interrupted. The context remains. E.g. in the example below, the kernel maintains reference to the x=1 execution.

But in the interactive window, the context is lost:

That's just luck. We do nothing different than jupyter does.

Actually I think we're showing the message even if there isn't a restart. The kernel didn't actually restart.

So the bug here is the message showing up, not the kernel restarting :)

Looking at the code, looks like there's a number of problems:

Restart handler in interruptKernel doesn't use the status from the restart handler (Should look like this)

            const restartHandler = (e: ServerStatus) => {
                if (e === ServerStatus.Restarting) {

When the interrupt finishes, the 'then' clause is indicating a restart. It should do nothing.

            // Start our interrupt. If it fails, indicate a restart
            this.session
                .interrupt(timeoutMs)
                .then(() => restarted.resolve([]))
                .catch(exc => {
                    traceWarning(`Error during interrupt: ${exc}`);
                    restarted.resolve([]);
                });

Not fixing this will cause customers to not trust the tool.

Validated. No more restart message when the kernel was interrupted.


refactor: use guard clause for ParameterizedTypeImpl.getTypeName

Codecov Report
Base: 87.21% // Head: 87.21% // No change to project coverage :thumbsup:

Coverage data is based on head (9c506c9) compared to base (b75531c).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #34   +/-   ##
=========================================
  Coverage     87.21%   87.21%
  Complexity      173      173
=========================================
  Files            16       16
  Lines           485      485
  Branches         66       66
=========================================
  Hits            423      423
  Misses           45       45
  Partials         17       17

Impacted Files
Coverage Δ

...ava/net/jailgens/mirror/ParameterizedTypeImpl.java
91.66% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Make hardcoded fetch 100 each worker user configurable

What would you like to be added:
https://github.com/juicedata/juicefs/blob/main/pkg/sync/cluster.go#L137-L166
Make
				objs = append(objs, obj)
				if len(objs) > 100 {
					break LOOP
				}

User configurable
Why is this needed:
We are using juicefs sync --workers to get 16 very large files from tencent COS to KS3 local jfs
And as we have 8 workers, however 16 is lesser than 100, so all 16 files are using one worker instead of all
Currently our temporary solution is to PAD each big file with 99 empty files, which is, well, working at least
However it would be nicer if I can use juicefs sync --workers on 16 files directly, so

We should have a limit on the total size of fetched keys.


Use lowercase only for HAPROXY_0_VHOST label value

I followed the doc and was not able to make the VHOST setting work until I changed the label value to all lowercase. Updated the marathon JSON to reflect it.
CC @brndnmtthws for review.

Strange, it shouldn't matter since the checks are case insensitive. Regardless, 👍 and thanks!


Add cookbooks for 64-bit Windows test matrix

This PR adds some new cookbooks to chef-acceptance that exercise functionality deemed important to validate for the 64-bit Chef on Windows test-matrix - see:
https://docs.google.com/spreadsheets/d/1i_H8skdOLyhLDNfL4VWrOCSRbyBR5BE56vp48KZ1rR0/edit
@client-core @jkeiser @tyler-ball

:+1:
For other readers I would like to call out that we are running the windows cookbook tests in here by making our .kitchen.yml include the suite names from the remote .kitchen.yml.

:+1:


Add output multi-link move using shift-click

Problem
When an output connects to multiple inputs, and you'd like to move all of those links to another node, you are currently required to drag each new link one by one.
Solution
Hold shift to pull all links on an output to a new node, or new output.  Does not disconnect links until they land on a valid target.
It functions with reroute nodes, however it requires that they are dropped onto the new output directly, not just anywhere on the node.  This is expected, really.
Limitations
It -does not- currently work with the drop to blank space + search for new node.  It will j ust rewire the first.  This can probably be fixed easily enough.

@webfiltered
Sorry for the late reply. I think when I fork this repo under ComfyOrg, it does not automatically add it to my watch list, so I missed your PRs. Going to review them all and get them merged!
What is the major blocker on your setup that requires manual work?

If you need something merged, you can ping me directly on discord / matrix

Actually would it be easier to create a reroute node when shift click output? I know someone was requesting this feature build into core.
https://github.com/user-attachments/assets/ca05126a-8963-4009-adbc-2037441bfa15
It's currently in https://github.com/coolzilj/ComfyUI-LJNodes

@webfiltered There is a regression on link release behavior. PTAL https://github.com/Comfy-Org/litegraph.js/pull/37

I am struggling to locate the code in that screenshot - hopefully indicating that it's new and not just something I missed.
But I'm updating my PR repos now.

The change was made in https://github.com/Comfy-Org/litegraph.js/pull/10


Custom importer sass.NULL usage

The documentions for custom importers state that
If an importer does not want to handle a particular path, it should return sass.NULL
But if you implement the importer in a package, that will be used as a dependency, this package will have a dependency on node-sass and have node-sass package in it's node_modules.
So when this importer is run from another package, like grunt-sass that has its own dependency on node-sass, the node-sass module used in grunt-sass and in the importer will not be the same object and the object reference equality check in node-sass will fail.
var result = importer.call(options.context, file, prev, done);
//result will be a sass.NULL from another node-sass object and the === fails
if (result) {
    done(result === module.exports.NULL ? null : result);
}

This cause node-sass to think all imports are handled by this importer no matter what.

This is assuming the importer implementation does a require('node-sass') to get a node-sass reference. How else would it be able to access sass.NULL

Good questions. Maybe @am11 or @saper would have thoughts here.

In some situation using peerDependencies will probably solved it, but probably not everywhere

Would that help if we would just return undefined? I actually think we should drop sass.NULL and use that native node type, just haven't got around to implementing it yet.

@chriseppstein I'd like to hear your thoughts on this since I expect any decision here will impact eyeglass.

@kenborge, you have made a very good point and thanks for spotting and reporting this issue.
This issue is in node-sass code itself, which can be hot fixed as:
- done(result === module.exports.NULL ? null : result);
+ done(result.toString() === module.exports.NULL.toString() ? null : result);
// both will return `[object SassNull]` which is different than `[object Object]`

or
- done(result === module.exports.NULL ? null : result);
+ done(result.constructor.toString() === module.exports.NULL.constructor.toString() ? null : result);

The idea was to not advertise these export too much and still able to provide control for explicitly returning SassNull type.

@kenborge can you check if my preliminary fix #1308 makes it better? Are you importers called synchronously or asynchronously? If async, then this could be a duplicate of #1296.

Actually asking for sass.NULL is a mistake. With #1308 returning JavaScript null should work as well.

In JavaScript return null;, return; and returning nothing are interchangeable, which is not applicable here as we need to differentiate between done and return. Explicitly returning sass.NULL is by design.

@am11 What about undefined?

@saper, either test the type sass.NULL or drop sass.NULL completely and use return null everywhere (i.e. breaking change). The reason why it wasn't done that (return null and test based on undefined) way in first place is to avoid the confusion and keep the type-systems separate.

My patch uses null everywhere and aliases sass.NULL and sass.sass_types.Null.NULL to null for compatibility.

A couple things.

if you implement the importer in a package, that will be used as a dependency, this package will have a dependency on node-sass

This is essentially forcing a peer dependency, which I agree is bad.

Actually asking for sass.NULL is a mistake.
Explicitly returning sass.NULL is by design.

I agree that with returning sass.NULL.

In JavaScript return null;, return; and returning nothing are interchangeable

Technically not true.
> function foo() { return null; }
undefined
> function bar() { return; }
undefined
> foo()
null
> bar()
undefined

What about undefined?

We could strictly check against undefined to get around the issue @am11 mentions with return null. @saper's patch does this.
Although technically null is not undefined as @am11 points out they are used interchangeably in the JS community. So much so a lot of developers don't know the conceptual difference. This means we're practically asking for false bug reports due to this misunderstanding.

My preference would be move sass-types into it's own repo as discussed in https://github.com/sass/node-sass/issues/1088#issuecomment-166467651
This solves the peerDependency problem, preserves the semantics of returning sass.NULL from importers/functions, and resolves abilities with returning null vs undefined.

It's also worth noting that we currently do not distinguish between custom importers returning false, null, undefined, or sass.NULL.
The exception being #1308 where we don't correctly handle return sass.NULL with async importers.

I've added test coverage for the existing importer noop return semantics in #1319. This will prevent us from unintentionally introducing BC breaks.

TLDR;
@kenborge you issue is fixed in https://github.com/sass/node-sass/pull/1318 and will be in v3.4.3.
@am11 @saper I've opened #1320 to discussion creating a sass-types package.

There are several problems with explicitly using undefined (it can be redefined for example), but we use it only because we want to be nice to those returning via return value instead of done(value) - we intercept that return value for them. It is not a proper solution, but kind of works and checking for undefined fits that ugly pattern.

Maybe we would better off by moving this code into the C++ binding. We should know better in C++ if the value was returned and how.

@xzyfer Returning null or undefined in place of sass.NULL does not appear to work (3.4.2). The importer will just hang indefinitely after processing a few files whereas it completes using sass.NULL.

@pmowrer I believe this has been patched in the current beta. Try npm install node-sass@beta.


More tax updates

Docs Build status updates of commit 74546fb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

dynamics-gp/payroll/US19JanTaxR1.md
:white_check_mark:Succeeded
View

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


Adjust the log level of FISCO BCOS v2.x

PBFT related log
PBFTENGINE_LOG(DEBUG) << LOG_DESC("InvalidPrepare: not saved after commit")
                              << LOG_KV("EINFO", oss.str());

should adjust to INFO

solved in PR #2267


Mandatory part+ を作成 (sokuno)

実装予定の項目
Mandatory Part

Minimal technical requirement

Backend

Django (Frontend Module)
PostgreSQL (Database Module)

Frontend

Javascript

[ ] single-page application
[ ] latest stable up-to-date version of Google Chrome
[ ] The user should encounter no unhandled errors and no warnings when browsing the website.
[ ] Everything must be launched with a single command line to run an autonomous container provided by Docker. Example: docker-compose up --build

Game

[ ] Therefore, users must have the ability to participate in a live Pong game against another player directly on the website. Both players will use the same keyboard.
[ ] A player must be able to play against another player, but it should also be possible to propose a tournament. This tournament will consist of multiple players who can take turns playing against each other. You have flexibility in how you implement the tournament, but it must clearly display who is playing against whom and the order of the players.
[ ] A registration system is required: at the start of a tournament, each player must input their alias name. The aliases will be reset when a new tournament begins.
[ ] There must be a matchmaking system: the tournament system organizes the matchmaking of the participants and announces the next fight.
[ ] All players must adhere to the same rules, which includes having identical paddle speed.
[ ] The game itself must be developed in accordance with the default frontend constraints (as outlined above), or you may choose to utilize the FrontEnd module, or you have the option to override it with the Graphics module. While the visual aesthetics can vary, it must still capture the essence of the original Pong (1972).

Security concerns

[ ] Any password stored in your database, if applicable, must be hashed.
[ ] Your website must be protected against SQL injections/XSS.
[ ] If you have a backend or any other features, it is mandatory to enable an HTTPS connection for all aspects (Utilize wss instead of ws...).
[ ] You must implement some form of validation for forms and any user input, either within the base page if no backend is used or on the server side if a backend is employed.

必要なくなったので閉じます


npx react-native init new application won't run (React Native 0.66, macOS 11.6, Xcode 13.0)

Description
** BUILD FAILED **
The following build commands failed:
CompileC /Users/my-username/Library/Developer/Xcode/DerivedData/AwesomeProject-gosjsvksbvgusscazfjiagvwmfqy/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RCT-Folly.build/Objects-normal/x86_64/FileUtil.o /Users/my-username/AwesomeProject/ios/Pods/RCT-Folly/folly/FileUtil.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RCT-Folly' from project 'Pods')
(1 failure)
React Native version:
System:
OS: macOS 11.6
CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
Memory: 365.40 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.19.0 - ~/.nvm/versions/node/v12.19.0/bin/node
Yarn: 1.22.11 - /usr/local/bin/yarn
npm: 6.14.8 - ~/.nvm/versions/node/v12.19.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
Android SDK: Not Found
IDEs:
Android Studio: 3.6 AI-192.7<IP_ADDRESS>92135
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
Languages:
Java: 14.0.1 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.66.0 => 0.66.0
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce

Run the following commands as shown on the Get Started page of the docs, to create a new application:

npx react-native init AwesomeProject
cd AwesomeProject
npx react-native start

In a new terminal while Metro is running, run the following command:

npx react-native run-ios

Expected Results
Expect the application to run on the simulator successfully.

I had a similar problem and the following got the app to run:

cd ios, pod install.
Start an IPhone 12 simulator before running.

I'm finding XCode 13 a bit treacherous at this point, but it seems a simple react-native init app will run.

@OmarJay1 Unfortunately your suggestion did not resolve the issue.

i have same issue

I have the same issue

I have the same issue.

Has anyone found a solution or a work around to start a project?

Not sure which step solves the issue, but I was able to run the project successfully by using these steps:

Update Node to latest version (v16.10.0)
Update XCode build system from "Legacy" to "New Build System".
Delete Pods and run "pod install" afterwards (must be in ios folder).
Run npm install.
Then finally run Metro bundler "npx react-native start" and  App "npx react-native run-ios."

Hello. I found a way to fix it. do the steps @conzidev mentioned but using the node version 14.17.0. I hope this can help.

@OmarJay1 I can't see that it gives me any more info about the error. Regarding pod install, I don't actually seem to need to run this, as I think this is done automatically as part of npx react-native init (app_name).
@dawinValenzuela Thanks for the suggestion. Although I still can't get a new app running, I seem to get fewer errors using Node 14.17.0 than any other version I have tried.
I have now tried various versions of Node (using nvm) but still cannot get a new app running.
The constants are:

macOS 11.6
Xcode 13.0

I have changed Xcode > Preferences > Locations > "Command line tools" from Xcode 13 to Xcode 12.5.1 but this doesn't resolve the issue so I have changed it back to 13.
Typically the steps I take are simply the following, as per the documentation:

npx react-native init AwesomeProject
cd AwesomeProject
npx react-native run-io

It's at this point I get the build failure error(s). I have noticed the errors do not seem to be consistent, though the usually related to RCT-Folly. The most recent time I followed these steps I got the following error (which is different to other times):
The following build commands failed:

CompileC /Users/(my-username)/Library/Developer/Xcode/DerivedData/AwesomeProject-gosjsvksbvgusscazfjiagvwmfqy/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RCT-Folly.build/Objects-normal/x86_64/SysUio.o /Users/(my-username)/AwesomeProject/ios/Pods/RCT-Folly/folly/portability/SysUio.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RCT-Folly' from project 'Pods')

CompileC /Users/(my-username)/Library/Developer/Xcode/DerivedData/AwesomeProject-gosjsvksbvgusscazfjiagvwmfqy/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RCT-Folly.build/Objects-normal/x86_64/NetOps.o /Users/(my-username)/AwesomeProject/ios/Pods/RCT-Folly/folly/net/NetOps.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RCT-Folly' from project 'Pods')

(2 failures)

The running the exact same command again gives this:
The following build commands failed:

CompileC /Users/ed/Library/Developer/Xcode/DerivedData/AwesomeProject-gosjsvksbvgusscazfjiagvwmfqy/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RCT-Folly.build/Objects-normal/x86_64/SysUio.o /Users/ed/Repositories/Tasks\ by\ Striketype/AwesomeProject/ios/Pods/RCT-Folly/folly/portability/SysUio.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler (in target 'RCT-Folly' from project 'Pods')

(1 failure)

I appreciate the suggestions so far and would welcome any other ideas.

hi! were you able to find a solution to this error?

I was able to get past this error by creating a new RN project inside a different parent folder

No problem!I feel the same way about it and was surprised the folder name could cause this but at least it works now haha.
If anyone figures out why this happens, please let me know :)

I don’t think it will be the path name for me, as the path which doesn’t work now definitely used to work (and it has no unusual characters in it). I was thinking it might be because a previous version of something has been installed at that location (maybe to do with pods)?

After few hours of searching online, finally it works.
Changing the parent directory does help to build the ios!

does anyone know why changing the parent directory helps?


fix: Persist the original "parentNode" when "retrieving" the root View created by createEmbeddedView

PR Checklist

[X] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
[X] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
[X] You have signed the CLA.
[X] All existing tests are passing: https://github.com/NativeScript/nativescript-angular/blob/master/DevelopmentWorkflow.md#running-the-tests
[ ] Tests for the changes are included -  Due to having to profile the JS heap I am not sure how we can efficiently make a unit test for that

What is the current behavior?
When using the Angular createEmbeddeedView from the ViewContainerRef, after calling clear() the created NativeScript Views are left in the memory
What is the new behavior?
When using the Angular createEmbeddeedView from the ViewContainerRef, after calling clear() the created NativeScript Views are left in the memory
Fixes/Implements/Closes #[Issue Number].
https://github.com/telerik/nativescript-ui-feedback/issues/825

The fix does look a bit mystical, but I think it is correct.
As @VladimirAmiorkov explained - we do this trick of creating an element with angular API (createEmbeddedView) and then detaching the NS-view form the original place that angular put it and put it somewhere else (in this case give it to the ListView to handle it).
However, in the process of detaching we were breaking the parent->child relation that angular renderer knows about. So it fails to clear the references when it needs to (on ViewContainerRef.clear()).
With this fix we preserve this relation trough parentNode so that clear() can do its job.
@sis0k0 Can you also take a look? Do you think this fix might have "side-effects"?

@vakrilov - Can we make sure this gets put into 5.0.  This is causing a very nasty memory leak in Angular applications, and with a RLV it is causing horrible memory loss causing the app to become unresponsive after a handful of master->detail->back navigations..

@vakrilov - LOL sorry, I thought this was the fix on the main NativeScript repo (this issue: https://github.com/NativeScript/NativeScript/pull/6353/)  -- I'm not as worried about this repo as you guys update it more frequently than the main NS repo...   :grin:

test build_ng_routable_animations build_ng_animation_examples


eliminate test seeds

use all real paths. we store prod data in a different repo and mount on server.

not convinced this is still relevant.


[Compute] Fix #23194: sig image-version create: Fix the Parameter tags must be of type dict error when --tags parameter is passed as key=value pairs

Issue - close: #23194
Related command

sig image-version create
Description

This issue was introduced by PR #22645.
Because after the command az sig image-version create adds the command level validator process_image_version_create_namespace, the original parameter level validator validate_tags is overwritten.
https://github.com/Azure/azure-cli/blob/cf51447b54a88d88466fdad3d6675a4dfb06e139/src/azure-cli/azure/cli/command_modules/vm/_params.py#L140
https://github.com/Azure/azure-cli/blob/cf51447b54a88d88466fdad3d6675a4dfb06e139/src/azure-cli-core/azure/cli/core/commands/parameters.py#L280-L284
https://github.com/Azure/azure-cli/blob/cf51447b54a88d88466fdad3d6675a4dfb06e139/src/azure-cli-core/azure/cli/core/commands/validators.py#L41-L47
Therefore, this PR adds back the validate_tags validator.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

Compute

Is this fix available in that? If not is there an ETA on the availability of the fixed version?

@idshehe This fix will be released on 09-06


Asymmetry: ∈ replaced by in but ∉ stays the same

Right now ∈ is replaced by in but since ∉ exists the formatted code may become
asymmetric since ∉ is left alone and not replaced by e.g. !(...). Perhaps ∈ should be
left alone as well for now.

Actually, I have only implemented the replacement in loop contexts so e.g. x ∈ X stays the same. Since ∉ can't be used in loop contexts I think it is fine as is.


Text truncate/Line clamp 617

Consider -webkit-line-clamp as it has 97%+ usage according to caniuse
As per Tachyons #617
Typical implementations  look like:
.line-clamp {
  display: -webkit-box;
  -webkit-box-orient: vertical;
}

.clamp-3 {
  -webkit-line-clamp: 3;
}

The challenge here is coverage of arbitrary line lengths. At the moment,  CSS attr() only has significant support for the content: properterty. Because of this, we would have to declare a range of line lengths. However, identifying the cow-paths of typical use is a challenge and very project specific. Including a clamp values say 1 - 20,  would just result in bloat across the breakpoints.
However when support for <type-or-unit> values is increased for more properties, then the following might be possible:
  <p class='line-clamp' data-clamp="5">long text </p>

.line-clamp {
  display: -webkit-box;
  -webkit-line-clamp: attr(data-clamp number, 0);
  -webkit-box-orient: vertical;
}

Reading: https://css-tricks.com/line-clampin/
https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-line-clamp
https://www.w3.org/TR/css-overflow-3/#propdef--webkit-line-clamp
https://www.w3.org/TR/css-overflow-3/#propdef-line-clamp

Due to the bloat that this would create, and the relative ease in creating a bespoke module for a custom build, this isn't going to be pursued.


Add ability to send attachments in an interaction initial response

Summary
Adds the ability to pass attachments with create_initial_response
Checklist

[ ] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted.

Related issues

I'ma see if i can work on the rest server equivalent logic for this today

Btw I do have a prototype impl of sending attachments on rest but i'm going to be waiting for discord to push a change they said they'd be pushing soon:tm: so if you remove the interaction server from this pr and switch out to handling de-duplicating the logic by moving out the payload building logic to a separate function instead of making the create_message logic work for create initial response this can be merged without the server logic
(and i'll do the server logic in another pr)

Sry for the delay

For a bit more specific detail on how OI think this should be handled: instead of modifying _create_message to also handle initial response specific logic I think we would be better off taking the logic for building the message response payload and doing something like
def _build_message(self, message_body: JSONObjectBuilder, ...) -> Optional[URLEncodedFormBuilder]:

where _build_message should cover both edit and create semantics, and if it returns a URLEncodedFormBuilder then the calling logic should handle inserting the "payload_json" field before making the request

Tests are still a TODO but a pre-emptive review would be welcomed @FasterSpeeding 😉

Meow

Woof


highlight js form npm does not hightlight by default

the core lib is not enough
it does not include any language by default
https://github.com/highlightjs/highlight.js/issues/1665
fast solution would be to import highlightjs + necessary language highlighting, initialize it then export it,
and include that file instead
better would be to fix the issue in the main repo

Uncomment what was done in this commit https://github.com/GrosSacASac/DOM99/commit/341f7527e5f2b8914267b59ce6bce8cea2c4c08c


0.17 condense regression

Recently I tried to update my tern-dependent libs to 0.17.0. However I noticed a regression in the condense output.
var condense = require('tern/lib/condense');
var tern = require('tern');
var fs = require('fs');
var path = require('path');

var server = new tern.Server({
  async: false,
  projectDir: __dirname
});

var filename = path.join(__dirname, 'arguments.js');

server.request({
  files: [{
    name: filename,
    text: 'var arguments = 1;',
    type: 'full'
  }]
}, function(err) {
  if (err) {
    throw err;
  }
});

server.flush(function(err) {
  if (err) {
    throw err;
  }

  console.log(JSON.stringify(condense.condense(filename, filename, {
    spans: true,
    server: server
  }), null, 2));
});

tern 0.16.0:
{
  "!name": "/Users/ramitos/dev/jsctags/arguments.js",
  "arguments": {
    "!type": "number",
    "!span": "4[0:4]-13[0:13]"
  }
}

tern 0.17.0:
{
  "!name": "/Users/ramitos/dev/jsctags/arguments.js"
}

I'm going to try to find what went wrong, but this can be helpful in - most probable - case I can't fix it.

We've started always normalizing file names to be relative to the project root, because absolute versus relative paths were causing confusion in the module system.
If you call server.normalizeFilename on your filename, you'll get output again. As it is, it won't match the variable's origin field, which will then be ignored.

@marijnh I ended up not having time to look at this again, so thank you very much for you answer :wink:


Polkatax - legalizing your staking income

Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "project_name.md") and updated.
[x] A BTC or Ethereum (DAI) address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below USD $30k for initial grant applications and $100k for follow-up grants.
[x] The initial PR contains only one commit (squash if needed before submitting your PR).
[x] The grant will only be announced once we've successfully delivered the first milestone.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@pmensik Thanks for the application. @jonasW3F has worked on something similar, perhaps he can provide some feedback.
Also, we can only support the development of open source software, so we cannot fund things like buy www.polkatax.com domain.

Apart from that, we currently don't award multiple grants in parallel and I believe this also applies to both programs in conjunction.
Since you have another open application for the General Grants Program and given Jonas' comments, I'm gonna go ahead and close this for now.
Thank you for your understanding.

@pmensik another option would be for you to apply for this grant first (the UI part is interesting nevertheless, since Jonas' tool is currently purely CLI) since it's much smaller and then for the Subauction one. Additionally you could apply for the latter through Open Grants as a follow-up grant, which should be easier.

@alxs @jonasW3F Great feedback, I didn't know such a project already exists. Good point with the follow-up grant, however, regarding the time-frame, we are quite eager to start developing both projects (with Polkatax having a priority since it can be finished really soon) - especially given the fact that the backend is already there. I am just worried that we might be able to finish the project sooner than w3f approves the grant :-) So how to deal with such a situation?

That's up to you.
However, since you're asking, given

the significantly reduced scope of this grant discounting infrastructure and backend
considering that you plan to monetise it,
seeing as you plan to work on it regardless of whether the application is accepted, and
considering this might lead to you experiencing some delays and/or uncertainty, since both an application and a milestone would need to be reviewed and accepted before you could apply again,

I would recommend you to consider carrying the costs for this yourselves and to focus on the Subauction application. You can start work on that project a bit later than the accepted date if necessary, in which case just let us know.
This is just my opinion though and you should go for whatever works best for you. Just let me know if you choose otherwise and I'll reopen this application.

@alxs Ok, those are really fair points so let's close it and let's see what we can do about it later on. Thank you


Studio Detail View

https://invis.io/D8528K5CU
@kperusko @sshaar08 this might be redundant to another ticket, lets discuss

duplcate of #8


[Snyk] Security upgrade @lhci/cli from 0.11.1 to 0.14.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

packages/template-retail-react-app/package.json
packages/template-retail-react-app/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Denial of Service (DoS) SNYK-JS-WS-7266574
  768

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Not impacted: DoS vulnerability in ws package not used in retail-react-app.


Generated JSON query is incorrect

Bug description
I raised a similar JSON query problem some months ago, and despite several new releases of Prisma in the meantime, the problem persists.
This problem is a show-stopper for me.
The problem is with the JSON extraction query code generated by Prisma -
The Prisma MySQL query distils down to
SELECT messageBody FROM testMessage
WHERE (JSON_UNQUOTE(JSON_EXTRACT(messageBody, '$.messageText'))) LIKE "%test%";

returns 0 records
switching the order of the JSON functions - to UNQUOTE before  EXTRACT
SELECT messageBody FROM testMessage
WHERE (JSON_EXTRACT(JSON_UNQUOTE(messageBody), '$.messageText')) LIKE "%test%";

returns  1+ records,

To verify, I ran these queries in MySQL

and

and with UNQUOTE before EXTRACT

To eliminate any case sensitivity, I tried various combinations of case for messagebody and messagetext.  Only the UNQUOTE before EXTRACT worked.
How to reproduce

Expected behavior
The expected behavior is the return of at least one record.
Prisma information

// Add your schema.prisma

model testMessage {
id Int @id @default(autoincrement()) @db.UnsignedInt
subject String
messageBody Json?
}
// Add your code using Prisma Client

Environment & setup
Windows 10 Pro

npm node -v
10.8.1
 "next": "^14.1.4",

MySQL v8

Prisma Version
npm prisma -v
10.8.1

  "@prisma/client": "^5.15.0",
 "prisma": "^5.15.0",

This issue persists in Prisma version 5.16.1

This issue still persists in Prisma version 5.17.0

This issue now holding me up and I can not progress with my search feature.
I have tried creating a raw query and for example this query works fine - and yields the expected results:
SELECT *
FROM instruments
WHERE (LOWER(JSON_EXTRACT(JSON_UNQUOTE(instruments.itemData), "$.instrument.description")) LIKE LOWER("%guitar%")
OR
LOWER(JSON_EXTRACT(JSON_UNQUOTE(instruments.itemData), "$.instDescription.manufacturer")) LIKE LOWER("%Martin%")
OR
LOWER(JSON_EXTRACT(JSON_UNQUOTE(instruments.itemData), "$.instDescription.model")) LIKE LOWER("%Prof II%")
OR
LOWER(JSON_EXTRACT(JSON_UNQUOTE(instruments.itemData), "$.instDescription.productCode")) LIKE LOWER("%x123%")
OR
LOWER(JSON_EXTRACT(JSON_UNQUOTE(instruments.itemData), "$.instDescription.description")) LIKE LOWER("%martin%"));

Notice the order of JSON_EXTRACT(JSON_UNQUOTE(
But I can not use the raw query going forward since my queries are rather complex and had hoped that Prisma Filtering and Sorting features would help me achieve my goal.  If I use similar filtering queries without the filtering on JSON content, the queries work fine.  As soon as I filter on JSON content the query fails because of the JSON_EXTRACT/JSON_UNQUOTE problem,
I have looked at the Prisma source in view of making this change myself, but could not locate the code where MySQL statements are generated.  Maybe someone could point me at the place in the code.  I'll fix it myself and push my contribution to Git.
I'd also very much appreciate someone from the dev team taking a look at this issue as soon as possible.
Thanks

You provided query does not match the schema you posted and you provided response does not match the query you are showing us either. Could you please go back to the issue template and fill out all the missing information, ensuring all entries much with each other?
If I have to guess - it looks you are stringifying the data before writing the data to JSON column - you should not do that, prisma will stringify the data for you. Single string is a valid JSON value, so if you supply a string as input, that string would be the value of JSON field, not the JSON value it describes. Could you show us writing code for this?
And just to put an end to the point you are making here - no, JSON_UNQUOTE and JSON_EXTRACT should absolutely not change places. This will break most of the quoted JSON strings, as in example here.

Hey @Aloysius999 ,
With the lack of information and our inability to reproduce this issue, we're now closing it. Feel free to comment if you have any updates about it.
Thank you 🙏


Modin (0.7.2) allows astype('categorical') but produces object as a result?

System information

Linux Mint 19.3
Modin version 0.7.2 (modin.__version__)
pandas 1.0.1
Python version 3.7

Describe the problem
I'm not clear if the Categorical dtype is supported, Modin seems to use object rather than category dtype in some reports.
Source code / logs
Below I make a DataFrame (Pandas and Modin) with 1 million 'a' and 1 million 'b' in a list, then make a new Series astype('categorical').
In the Modin example we get two object columns for info(), in the Pandas example I get 1 object and 1 categorical. Should categorical be supported for Modin?
Asking for the dtype for the categorical column does report a categorical result.
Example using Pandas:
df_cat = pd.DataFrame({'items': ['a'] * 1_000_000 + ['b'] * 1_000_000})
df_cat['items_cat'] = df_cat['items'].astype('category')
df_cat.info()
<class 'pandas.core.frame.DataFrame'>
RangeIndex: 2000000 entries, 0 to 1999999
Data columns (total 2 columns):
 #   Column     Dtype
---  ------     -----
 0   items      object
 1   items_cat  category
dtypes: category(1), object(1)
memory usage: 17.2+ MB

Same example using Modin:
import modin.pandas as mdpd
df_md_cat = mdpd.DataFrame({'items': ['a'] * 1_000_000 + ['b'] * 1_000_000})
df_md_cat['items_cat'] = df_md_cat['items'].astype('category')

df_md_cat['items_cat'].dtype
CategoricalDtype(categories=['a', 'b'], ordered=False)

df_md_cat.info()
<class 'modin.pandas.dataframe.DataFrame'>
RangeIndex: 2000000 entries, 0 to 1999999
Data columns (total 2 columns):
 #   Column     Dtype
---  ------     -----
 0   items      object
 1   items_cat  object
dtypes: object(2)
memory usage: 30.5+ MB

Ah - so trying to make a category on a string in the above example doesn't work but making a categorical from a list of integers does work. However - it gets mis-reported by info():
df_md_cat2 = mdpd.DataFrame({'items': [1] * 1_000_000 + [2] * 1_000_000})
df_md_cat2['items_cat'] = df_md_cat2['items'].astype('category')
df_md_cat2['items_cat'].dtype
# the result is the same CategoricalDtype as Pandas shows
CategoricalDtype(categories=[1, 2], ordered=False)

# info() however shows two int64 columns in the list
# and in the summary, with no categoricals
df_md_cat2.info()
<class 'modin.pandas.dataframe.DataFrame'>
RangeIndex: 2000000 entries, 0 to 1999999
Data columns (total 2 columns):
 #   Column     Dtype
---  ------     -----
 0   items      int64
 1   items_cat  int64
dtypes: int64(2)

Hi @ianozsvald thanks for the report!
Categorical should be supported. I can reproduce the issue myself, thank you for the reproducer. We fall back to pandas for the info string, so it's interesting that the pandas implementation is failing like this. I will investigate, we may just need to override the resulting string with the correct dtypes.

This is the same as #1165, we have some progress on the bug in that thread so I will close this for duplication purposes. I will add a comment on that thread about the info case to ensure we don't lose this specific use case.


Increase margins between lines for easier reading

Below pic is when i did a quick inspect and edited the margins to be about 16px, but it can probably be smaller lol
Before and after comparison

done in v1.4.1


Address security concerns in render_model* tags

Coverage decreased (-0.01%) to 90.974% when pulling 9f3d08c318ed5876aec7b3e1cd24a6d2312ce580 on mkoistinen:issue/removes_mark_safe into 3bfbea6e43b8a5c9b0cc481b6d4bfededf177be8 on divio:support/3.1.x.

Coverage decreased (-0.003%) to 90.982% when pulling 370d322e320cada60affedb98721b550a8517e5f on mkoistinen:issue/removes_mark_safe into 3bfbea6e43b8a5c9b0cc481b6d4bfededf177be8 on divio:support/3.1.x.

See #5166

@mkoistinen technically LGTM.
I'd try to avoid introducing a new way of describing the problem in the setting name. CMS_UNESCAPED_RENDER_MODEL_TAGS is not exactly the thing I'd look for when dealing with a problem that is dominated by the term mark_safe.
How about calling it CMS_RENDER_MODEL_TAGS_WITH_MARK_SAFE or
CMS_RENDER_MODEL_TAGS_WITH_MARK_SAFE_BY_DEFAULT?

@mkoistinen does this implementation also support this notation?
{% render_model_block mymodel "myfield" mark_safe=False %}

what is the implication if I do {% render_model_block mymodel "myfield" "" "" "safe" %} ?

@stefanfoulis re: CMS_RENDER_MODEL_TAGS_WITH_MARK_SAFE, that sounds like a safe thing to leave set to True, whereas CMS_UNESCAPED_RENDER_MODEL_TAGS sounds unsafe.
I don't think this implementation supports "kwargs" style parameters. I'm not sure its possible without overhauling these template tags.

@mkoistinen why adding "mark_safe" when you can use the filters argument for this?

re {% render_model_block mymodel "myfield" mark_safe=False %}: the reason I'd like it to be possible to explicitly say: "don't mark_safe!" even if CMS_UNESCAPED_RENDER_MODEL_TAGS=True is so that someone can already fix a template to do the secure thing, even if the global setting in a project is still the insecure option.

IIRC classy tags does not support that syntax, but I might be wrong
You can achieve that with {% render_model_block mymodel "myfield" "" "" "escape" %}

@yakky ok 👍 ("escape")

Coverage increased (+0.3%) to 91.245% when pulling 6b9e112448be751c2f27351e97ec2ac5581de983 on mkoistinen:issue/removes_mark_safe into 3bfbea6e43b8a5c9b0cc481b6d4bfededf177be8 on divio:support/3.1.x.

LGTM

Ok to merge

Coverage increased (+0.007%) to 90.992% when pulling e149e0bdd9282c3d07962c7d2ed01a3f73d06dfd on mkoistinen:issue/removes_mark_safe into 3bfbea6e43b8a5c9b0cc481b6d4bfededf177be8 on divio:support/3.1.x.

Coverage increased (+0.007%) to 90.992% when pulling e149e0bdd9282c3d07962c7d2ed01a3f73d06dfd on mkoistinen:issue/removes_mark_safe into 3bfbea6e43b8a5c9b0cc481b6d4bfededf177be8 on divio:support/3.1.x.


[WIP] Update compose-file reference for sysctls

documentation changes for https://github.com/docker/cli/pull/1754
marking this "WIP" as this has not yet been released

Deploy preview for docsdocker ready!
Built with commit 83d2c230faec193986adf829c64db487159e7460
https://deploy-preview-8481--docsdocker.netlify.com

Rebased
/cc @usha-mandya @ulyssessouza

@usha-mandya I forgot about this one; think this one should be ready to merge as well (once netlify finishes)


python3Packages.pycm: clean up checkPhase

Motivation for this change
As promised in #134727.
Things done

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

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

[NA] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 134749 at 18c1b519 run on aarch64-linux 1

2 packages built successfully:

python38Packages.pycm
python39Packages.pycm


Synchronous/Wait Kafka instance creation

Related to #601 which is now addressed, I was thinking about my experience with the Azure CLI.
With that CLI you can specify a --no-wait parameter to start a long-running operation asynchronously; the rhoas CLI is somehow async by default.
When creating a new Kafka instance, it starts the provisioning and you have to use the status command to see the progress.
Maybe having a --wait parameter could be useful to make it synchronous so having the CLI to block and check periodically the status of the provisioning and exiting when the Kafka instance is actually ready.

Related to https://github.com/redhat-developer/app-services-cli/issues/41

Does backend supports watch? We could do pooling for this as well

Does backend supports watch?

No, the backend does not support watch or synchronous creation. Polling is a good workaround.

Backend does not yet support synchronous creation. Once it is possible this is definitely something that will be added.

Backend does not yet support synchronous creation.

It is unlike that synchronous creation will be supported by the backend.

Backend does not yet support synchronous creation.

It is unlike that synchronous creation will be supported by the backend.

Good to know. Is the async=true query param going to remain as a "just in case" measure?

Backend does not yet support synchronous creation.

It is unlike that synchronous creation will be supported by the backend.

Good to know. Is the async=true query param going to remain as a "just in case" measure?

This will always remain and it is a required parameter indicate that the operation will be performed in async manner. If you set it to false I believe the request should fail even now with a 400 HTTP code.


nixos-rebuild switch --upgrade behaviour should be consistent when installing the bootloader fails

Describe the bug
I have a boot loader setup that can be thought of as ... "not ideal", to put it mildly. I was on NixOS 22.05. Tried upgrading to 23.11. sudo nixos-rebuild switch --upgrade gave me the following error and exited with 1:
...
updating systemd-boot from 250.4 to 254.6
Copied "/nix/store/qgjsvm3c4131qasxqbzphhd62j0lvvwh-systemd-254.6/lib/systemd/boot/efi/systemd-bootx64.efi" to "/boot/efi/EFI/systemd/systemd-bootx64.efi".
Skipping "/boot/efi/EFI/BOOT/BOOTX64.EFI", it's owned by another boot loader (no version info found).
Traceback (most recent call last):
  File "/nix/store/v55r9ww078799y1q3ds4df88pnklxhl3-systemd-boot/bin/systemd-boot-builder", line 344, in <module>
    main()
  File "/nix/store/v55r9ww078799y1q3ds4df88pnklxhl3-systemd-boot/bin/systemd-boot-builder", line 332, in main
    install_bootloader(args)
  File "/nix/store/v55r9ww078799y1q3ds4df88pnklxhl3-systemd-boot/bin/systemd-boot-builder", line 280, in install_bootloader
    subprocess.check_call(["/nix/store/qgjsvm3c4131qasxqbzphhd62j0lvvwh-systemd-254.6/bin/bootctl", "--esp-path=/boot/efi"] + bootctl_flags + ["update"])
  File "/nix/store/rac8pxbi1vapwrlqzbrkycbyg521djzw-python3-3.11.6/lib/python3.11/subprocess.py", line 413, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/nix/store/qgjsvm3c4131qasxqbzphhd62j0lvvwh-systemd-254.6/bin/bootctl', '--esp-path=/boot/efi', 'update']' returned non-zero exit status 1.
warning: error(s) occurred while switching to the new configuration

So I assumed the upgrade was unsuccessful. But, I tried running the command again but this time it exited successfully. Actually the upgrade was successful since I rebooted and checked the version.
Steps To Reproduce
Expected behavior
IMO, the behaviour should have been consistent. Either sudo nixos-rebuild switch --upgrade should have produced an error both times or it shouldn't have produced an error altogether.
Additional context
Follow up of a discussion with @ElvishJerricco
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
- system: `"x86_64-linux"`
 - host os: `Linux 6.1.76, NixOS, 23.11 (Tapir), 23.11.3920.25e3d4c0d359`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

To clarify, here's what happened.
BOOTX64.EFI was owned by another boot loader, i.e. not a systemd-boot binary. This caused bootctl update to exit non-zero even though it did update systemd-bootx64.efi, which terminated systemd-boot-builder.py before it was finished. On subsequent rebuilds, bootctl update was not invoked at all because systemd-bootx64.efi was found with the up-to-date version, so systemd-boot-builder.py was able to finish.
This inconsistency is problematic, but I'm not sure what to do about it.

I'll add a note that assuming ownership of the default fallback location is likely undesirable "spec-wise", though also somewhat understandable pragmatically.
(This ownership of the default fallback location is a systemd-boot issue. Likely an upstream one. And isn't the point of resolving this discussion...)


Escaping Literal Quotes in Strings

Hi there, I'm stuck here.
Challenge escaping-literal-quotes-in-strings has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
My code:

var myStr = "I am a \"double quoted\" string inside \"double quotes\"."; // Change this line

So, what's the problem? I can't complete this task because of this error:

You should use two double quotes (") and four escaped double quotes (").

But.. I'm use them all, no?

Encountering same issue here on Safari 9.1

Related:
https://github.com/FreeCodeCamp/FreeCodeCamp/commit/31e904f4ff116f3d951c5a67655d0e65460fb3ed

me too...

I also have this problem. Using Mozilla 49.0.

I have the same problem as well. Using chrome.

+1

Reference to #10258

Closing as duplicate of #10258

+1

Please remove space before ""
var myStr= "I am a "double quoted" string inside "double quotes".";


FLEX-2294 ~ Adds variables for TLS configuration.

This pull request makes the build fail.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Configuration.java#L94: Constructor has 8 parameters, which is greater than 7 authorized.

All is well.

SonarQube analysis reported 1 issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Configuration.java#L94: Constructor has 8 parameters, which is greater than 7 authorized.

All is well.

SonarQube analysis reported 2 issues

 2 major

Watch the comments in this conversation to review them.
1 extra issue
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Configuration.java#L94: Constructor has 8 parameters, which is greater than 7 authorized.

All is well.


Autoresizing textfield text

Hi, I'm trying to autoshrink, autoresize the text in the textfield when the text is more length than the textfield width. But when I type in the textfield the text will move out on the left side, and the first letters disappears...

Can you share the method you are using? This should work the same as for UITextField since SkyFloatingLabelTextField just inherits from it

I'm having the same issue.  I'm pre-filling the text for a textField with fetched data from an API call, and the text isn't shrinking to fit.  I've added textFieldName.adjustsFontSizeToFitWidth = true as well checking the box in IB and nothing seems to fix it.  Help?

Apparently UITextField will only go down to a minimum font size of 14. If you set the minimum to 10, it will only reach 14.
Source: https://stackoverflow.com/a/30881385/1283228


Close and recreate the PR.


Inference speed

Hello, I am trying to reproduce the results on 8 A100, while my inference speed is quite slow. So I am interested in the original inference speed. By the way, what is the inference speed in “egl” and “osmesa”

We didn't record exact numbers, but it does take hours to finish the evaluation.


Remove wl_shell

We've never seen a correct wl_shell implementation anywhere in the wild and the consensus seems to be among Wayland developers that it is not possible to create a fully-featured shell client with this protocol. It is officially deprecated by the Wayland project and has recently been dropped by sway.

Very fine by me

Fixed with #185


"Bad file descriptor" error on windows 10 bash subsystem

Running cargo watch on the ubuntu bash subsystem of windows 10 results in the following error:
> cargo watch
ERROR:cargo_watch: Failed to init notify (Io(Error { repr: Os { code: 9, message: "Bad file descriptor" } }))

Does this mean anything to you?

Cargo Watch should now fallback to polling if it can't use the native version. I'm thinking this is an issue of Windows Bash reporting as Linux for the rust build system, and Notify assuming that inotify is available. If it doesn't fallback, try to force it with --poll.

Closing. Reopen if it still occurs.

I believe inotify supported landed in the latest release of the Linux subsystem, so this should be properly fixed now.


align keypoints with raw FP

Simply added a note about lack of temporal alignment for keypoint sessions.

Will this affect my currently running conversion? Should I cancel it in progress until this is resolved?

This should be good to merge -- this was the branch that I ran for the keypoint sessions that are uploaded to DANDI