TypeError: Cannot read properties of undefined (reading 'replace')

Same as with this issue: https://github.com/kysely-org/kysely-postgres-js/issues/9
I'm using latest of everything and this is on nextjs 14, node 20.
I tried to understand the problem but I failed to do so.
I rolled back to pg and worked fine, therefore I think it's either postgres or this adapter.

Hey 👋
Can you paste your package.json's dependencies object or provide a reproduction repository?

Hi @igalklebanov , sorry but I already migrated out of nextjs.
I think MAYBE the problem is that the connection string was undefined. Not completely sure, but that might be.
Sorry.

Hey, @igalklebanov
I have the same error as op
D:\backend\node_modules\postgres\cjs\src\connection.js:389
      stack: { value: err.stack + query.origin.replace(/.*\n/, '\n'), enumerable: options.debug },
                                               ^
TypeError: Cannot read properties of undefined (reading 'replace')
    at queryError (D:\backend\node_modules\postgres\cjs\src\connection.js:389:48)
    at errored (D:\backend\node_modules\postgres\cjs\src\connection.js:384:17)
    at Socket.error (D:\backend\node_modules\postgres\cjs\src\connection.js:376:5)
    at Socket.emit (node:events:514:28)
    at Socket.emit (node:domain:489:12)
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)

package.json
{
  "name": "backend",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "build": "npx tsc",
    "start": "node dist/index.js",
    "dev": "nodemon src/index.ts"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "dotenv": "^16.4.2",
    "express": "^4.18.2",
    "kysely": "^0.27.2",
    "kysely-postgres-js": "^2.0.0",
    "pg": "^8.11.3"
  },
  "devDependencies": {
    "@types/express": "^4.17.21",
    "@types/node": "^20.11.17",
    "kysely-codegen": "^0.11.0",
    "nodemon": "^3.0.3",
    "ts-node": "^10.9.2",
    "typescript": "^5.3.3"
  }
}

Exactly same issue, while default pg dialect works as should.

"kysely-postgres-js": "^2.0.0",
"pg": "^8.11.3"

Hey 👋
You've installed pg which is the wrong underlying postgres client.

same problem next 12.3.4 or next 14

I got the same problem as well, here's the error it gives
file:///app/node_modules/postgres/src/connection.js:389
      stack: { value: err.stack + query.origin.replace(/.*\n/, '\n'), enumerable: options.debug },
                                               ^

TypeError: Cannot read properties of undefined (reading 'replace')
    at queryError (file:///app/node_modules/postgres/src/connection.js:389:48)
    at errored (file:///app/node_modules/postgres/src/connection.js:383:14)
    at TLSSocket.data (file:///app/node_modules/postgres/src/connection.js:318:9)
    at TLSSocket.emit (node:events:518:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at TLSWrap.onStreamRead (node:internal/stream_base_commons:190:23)

Node.js v20.11.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Here's the deps version I'm using
"kysely": "^0.27.2",
"kysely-postgres-js": "^2.0.0",
"postgres": "^3.4.3",

This seems related to postgres, and not this package as all stack traces thus far lead to https://github.com/porsager/postgres/blob/master/src/connection.js#L389
Try using your postgres instance outside of Kysely with the same options.

Closing this.
Tests are passing with Node LTS, postgres@latest, kysely@latest.
Was able to reproduce the same exception when docker container was down or by passing a wrong host option - so it's clear all of you are passing wrong connection options or something.
Not related to Kysely or kysely-postgres-js.

I can confirm that this is a cryptic error message but it's related to a malformed URL. In my case I had a ?schema= in my connection string and postgres-js didn't like it. cc @porsager

I can confirm that this is related to a malformed URL. In my case I had a ?schema= in my connection string and postgres-js didn't like it. cc @porsager, it's a cryptic error message and might be worth exploring a fix.

Yeah maybe but i use credentials not url and error still happens

I can confirm that this is related to a malformed URL. In my case I had a ?schema= in my connection string and postgres-js didn't like it. cc @porsager, it's a cryptic error message and might be worth exploring a fix.

I remove ?schema= from url and  it work


etcd node changes can cause unhealthy cluster (especially in case of leader re-election, slow etcd or large etcd size)

**What kind of request is this (question/bug/enhancement/feature request):Bug
Steps to reproduce (least amount of steps as possible):
Rancher Version: v2.3.2
Kubernetes Version: v1.13.5
Docker Version: 17.3.2
AWS Worker Node Version: CentOS Linux release 7.6.1810 , m5.2xlarge , kernel:4.4.184-1.el7.elrepo.x86_64
The cluster is Amazon EC2 Launched Cluster via Rancher GUI.
The cluster has 3 separate nodes which handle etcd & controlpanel.. Worker nodes are seperate and don't have etcd & controlpanel
1) Try to add a AWS worker node. The node is stuck during provisioning. I see following commands run in /var/log/secure on the node
============================================
grep COMMAND /var/log/secure  | grep <provisioninguser>
Dec 11 11:34:22 ip-x-x-x-x sudo: <provisioninguser> : TTY=pts/0 ; PWD=/home/<provisioninguser> ; USER=root ; COMMAND=/bin/hostname blah-blah
Dec 11 11:34:22 ip-x-x-x-x sudo:  <provisioninguser> : TTY=pts/0 ; PWD=/home/<provisioninguser> ; USER=root ; COMMAND=/bin/tee /etc/hostname
Dec 11 11:34:25 ip-x-x-x-x sudo:  <provisioninguser> : TTY=pts/0 ; PWD=/home/<provisioninguser> ; USER=root ; COMMAND=/bin/tee -a /etc/hosts
Dec 11 11:34:29 ip-x-x-x-x sudo:  <provisioninguser> : TTY=pts/0 ; PWD=/home/<provisioninguser> ; USER=root ; COMMAND=/bin/yum install -y curl
Dec 11 11:34:58 ip-x-x-x-x sudo:  <provisioninguser> : TTY=pts/0 ; PWD=/home/<provisioninguser> ; USER=root ; COMMAND=/bin/yum -y update -x docker-*

Then the provisioning user logs out after couple of minutes without doing anything
Dec 11 11:37:27 <hostname> sshd[pid]: pam_unix(sshd:session): session closed for user <provisioninguser>

Result:
AWS Worker node stuck in provisioning and then when tried to remove it , its stuck in "Removing " State with message
Provisioning with <provisioninguser>...; waiting on node-controller
Other details that may be helpful:
Environment information
Rancher Version: v2.3.2
Kubernetes Version: v1.13.5
Docker Version: 17.3.2

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
rancher/rancher-agent:v2.3.2
rancher/hyperkube:v1.13.5-rancher1
rancher/rancher:v2.3.2 ( This is run in a separate "local" k8s cluster
Installation option (single install/HA):HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported): Infrastructure Provider Amazon EC2
Machine type (cloud/VM/metal) and specifications (CPU/memory): AWS m5.2xlarge
Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.2", GitCommit:"66049e3b21efe110454d67df4fa62b08ea79a19b", GitTreeState:"clean", BuildDate:"2019-05-16T18:55:03Z", GoVersion:"go1.12.5", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.5", GitCommit:"2166946f41b36dea2c4626f90a77706f426cdea2", GitTreeState:"clean", BuildDate:"2019-03-25T15:19:22Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):

Client:
 Version:      17.03.2-ce
 API version:  1.27
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:21:36 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.03.2-ce
 API version:  1.27 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   f5ec1e2
 Built:        Tue Jun 27 02:21:36 2017
 OS/Arch:      linux/amd64
 Experimental: false

gzrancher/rancher#9105

Anyone from rancher team looking into this. Its a blocker for us right now

@Oats87 Chris - can you look into this?

Any update on this ?

At this point, I am planning to delete the node from the backend etcd keystore and see what happens ETCDCTL_API=3 etcdctl delete /registry/management.cattle.io/nodes/<cluster-id>/<error-node-id>

I had the same issue in "Rancher 2.3.3" after I upgrade kubernetes custom cluster (Running on EC2) to 1.16.3 Instances, but the interesting point was that it self solved after 3 hours (the node disappear).
Now I'm afraid it'll happen again.

Ok this was fixed after I killed the docker-machine cmd which was spawned from the rancher workload running under cattle-system namespace.  Also the etcdctl delete solution works. Once I ran it , it deleted the node from the ui, but docker-machine cmd was still running inside the rancher deployment.
ETCDCTL_API=3 etcdctl del /registry/management.cattle.io/nodes/<cluster-id>/<error-node-id>

@Hitesh-Agrawal so you're saying you had a hung docker-machine process running within a jail in Rancher? Did you ever try just killing all of the Rancher pods (to force a restart) and seeing if things cleared up?

@Hitesh-Agrawal so you're saying you had a hung docker-machine process running within a jail in Rancher? Did you ever try just killing all of the Rancher pods (to force a restart) and seeing if things cleared up?

@Oats87 Yep I believe even doing that would have cleared things up.
Also regarding the node stuck in provisioning at COMMAND=/bin/yum -y update -x docker-* was due to awscli installed via pip in my custom image which was causing issue with above yum command
Replaced below in my image from
curl -O https://bootstrap.pypa.io/get-pip.py
python get-pip.py
pip install awscli --upgrade

to
yum -y install awscli
You probably need to introduce a timeout for the hung docker-machine process.

I see this or a similar issue when creating a cluster in 2.3.6 with nodes of 2 Cores and 4GiB of RAM. I've seen these sorts of issues may be caused by resource issues, but I also see them in clusters where this is not the case
Steps:

Deploy cluster with 1 cp/etcd node
Scale up to 3 nodes using + in the UI
Scale down to 1 node

Alternatively, I also see failures when scaling down one node at a time.  After a cp/etcd node was removed in the v2.3.6 cluster (leaving 2 behind) I saw one of the two get stuck with waiting on the node to respond (unfortunately I lost the screenshot and error).  Deleting the node forced a recreation and resolved the issue.
It took roughly 8 attempts to recreate before I was able to get nodes stuck again after the first attempt (which similarly failed). The failure doesn't appear to be predictable but it is common enough that I've seen this behavior on many test clusters for several versions. I've not yet been able to recreate in 2.4.3, and i notice that the nodes take longer to deploy and remove, so this may have been fixed?

2.4.3，similar issue

Based on https://github.com/rancher/rancher/issues/24547#issuecomment-645008685, the following was investigated:
As it wasn't consistently reproduced, I started with testing removing one and two nodes at a time. Sometimes this would succeed, sometimes this would fail. Based on this outcome I tried checking the etcd leader and make sure that when deleting a node, it was the etcd leader. This caused more delay in recovering the cluster because re-election is triggered. Because there is no wait/healthcheck on member delete, there is not enough time to re-elect a leader and either the next member delete (in case of deleting multiple nodes) or the cluster health check that we do on reconcile only is coming too soon and doesnt have enough time to let the cluster settle.
The fix is to add a health check the cluster on member delete.
To reproduce (either RKE CLI or Rancher node driver):

Create a 2 node and a 3 node cluster
Check the etcd leader using the command on https://rancher.com/docs/rancher/v2.x/en/troubleshooting/kubernetes-components/etcd/#check-endpoint-status
Make sure to delete the node that is the leader (in the 2 node cluster) and that node and another random node in the 3 node cluster
Observe the cluster failing because etcd is not recovering

To make it easier to reproduce, raise the election-timeout on etcd so it takes longer to elect a new leader:
services:
  etcd:
    extra_args:
      election-timeout: "50000"

Looks like this has already been fixed but just in case, we've seen this recreated as follows:
In a new test cluster running on rke 1.17.11-rancher1-1, rancher 2.4.4, host OS all Ubuntu 18.04, docker 19.3.11 all on vSphere on-prem using canal:

Created 2 pools, 1 for etcd/cp and1 for workers

Created 1 node for combined etcd/cp and 1 node for workers

Im now going to upgrade the cluster to 3 etcd/cp by immediately increasing the amount of nodes in the pool by hitting the + icon twice.

Result:
This ends up with the 2 new etcd/cp nodes ending in error:  Error creating machine: Error running provisioning: Failed to obtain lock: Maximum number of retries (60) exceeded

Ok this was fixed after I killed the docker-machine cmd which was spawned from the rancher workload running under cattle-system namespace. Also the etcdctl delete solution works. Once I ran it , it deleted the node from the ui, but docker-machine cmd was still running inside the rancher deployment.
ETCDCTL_API=3 etcdctl del /registry/management.cattle.io/nodes/<cluster-id>/<error-node-id>

This is what worked for me as well. In my case, I was using the OpenStack provisioner with incorrect settings. To be specific, I had an error in my network configuration causing the instance to be unreachable. Rancher was permanently waiting for SSH without any timeout.

Available to test with v2.4.9-rc1

The bug is reproduced in v2.4.8 single install setup
Steps:

add a cluster 4 nodes: 3 etcd+controlplane, 1 worker
ssh into one of the etcd+controlplane node to find the etcd leader
delete the leader node and another one etcd+controlplane node at the same time from Rancher UI

Results:

the cluster is stuck in the updating state and never recover

The fix is validated in the following RKE CLI

v1.1.11-rc1
v1.2.2-rc2

Steps:

use RKE CLI to provision a 4 node cluster: 3 etcd+controlplane, 1 worker
ssh into one of the etcd+controlplane node to find the etcd leader
remove the leader node and another one etcd+controlplane node in the rancher-cluster.yml
run rke up again to update the cluster

Results:

the cluster is upgraded successfully


Please provide CAML examples and specify that PnP PowerShell do not accept RowLimit parameter

Same here https://github.com/pnp/PnP-PowerShell/issues/879

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

ID: 9d9f0311-903f-01a2-478d-28e0a196b5c5
Version Independent ID: 3adca24b-cf2a-63d1-7eb5-631c6448daca
Content: Add-PnPView (sharepoint-pnp)
Content Source: sharepoint/sharepoint-ps/sharepoint-pnp/Add-PnPView.md
GitHub Login: @techwriter40
Microsoft Alias: kirks

@officedocsbot assign @yogkumgit

Hello @wowYann how are you?
Thanks for your feedback.
I need to kindly redirect you to open PnP cmdlets issues here, a member of the PnP community will handle your request there.
Thank you!

@get-itips Thank you very much for the contribution and sharing this explanation. @wowYann Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Radio-image labels?

I feel like adding labels for radio-image options would be highly useful. So, instead of just defining radio-image choices like key => url, you could have something like
key => array(      label => 'label',     url => 'url' )
Then it could just add a title attribute to each option's .image-clickable span element. Are there any plans for anything like this?

Any thoughts on this? Seem like a relatively easy feature to implement...surely I can't be the only one that needs this..?

Fixed.
But instead of label and url I used src and alt 'cause those are the attribules used in the image, so it made more sense that way.

Fantastic! I'll update my themes asap!

Keep in mind that this only works with the development branch of the plugin...
Try it and if you have any suggestions regarding the styling, let me know. Pull requests are greatly appreciated :)

Yeah, I realized that as soon as I posted... may hold off on applying to themes, haha. anyway, I'll check it out and let you know if I have suggestions. Thanks for getting to this!


Excessively long stack traces

Hi great work on this module!
I get strange stack traces when a test fails. Here's an example
Error: index must be defined in /myProject/src/entities/Face.js (line 9)
/myProject/src/entities/Face.js:9:1841
/myProject/tests/entities/FaceSpec.js:21:82
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:35:34
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
/myProject/node_modules/jasmine-promises/dist/jasmine-promises.js:47:15
   ..... this continues for another 40 lines ....

Any idea how to limit this?

+1

+1

Thanks! I've just pushed a fix for this.
Let me know of any further issues.


Auto-up after mount and unmount

After running the mount and unmount commands, automatically re-run up.
Potential drawbacks: We might start services that weren't running before.

I'm not sure this is a good idea. I used to have all kinds of helpers like this in the old cage but they ended up being a nuisance 80% of the time.

Yeah, that's an excellent point. If we do this at all, it probably ought to wait until after we have the ability to poll Docker and see which pods/containers are currently up, and which would need to be restarted. Moving off of milestone and into RFC status for further discussion.

There doesn't currently seem to be any consensus that this is a good idea.
I suppose that we could be a bit more precise, now that we have detailed container state: We could selectively re-up only those services that are (1) affected by the volume mount change and (2) already running in the user's environment.
But I'm not convinced this is actually a good idea, especially now that we warn the user to re-run up after they run mount.

Yeah, after consideration, I'm closing this RFC for now. Thank you for your feedback!


[TACKLE-8] Jitpack building ahead of time

To speed up the building process for other projects while using Jitpack, it's worth adding "Building ahead of time"

Done the required configuration following https://jitpack.io/docs/BUILDING/#building-ahead-of-time


Add test that could not be built

Codecov Report
Patch and project coverage have no change.

Comparison is base (c7b0d21) 6.58% compared to head (554e746) 6.58%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@          Coverage Diff           @@
##           master     #20   +/-   ##
======================================
  Coverage    6.58%   6.58%
======================================
  Files           5       5
  Lines         425     425
======================================
  Hits           28      28
  Misses        395     395
  Partials        2       2

Flag
Coverage Δ

unittests
6.58% <ø> (ø)

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

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


Switch to serverless

Using one of those:

https://github.com/Miserlou/Zappa
https://github.com/aws/chalice

@codingjoe we still can use Redis from Heroku for lambda function in AWS, for example, but do you know how can we manage to schedule commands there?

@amureki I think this is an overkill. You would need to use a different storage solution. Honestly it's easier to keep as is. A hobby dyno doesn't cost the world.


[jvm-packages] compile against different versions of spark

spark is coming with the 2.0 version which introduces several incompatible changes over the previous version
one of the issues is that the user will not upgrade to spark 2.0 immediately and sometimes, they just cannot upgrade due to various reasons.....
xgboost4j-spark shall upgrade with the pace of spark but also needs to ensure that the current users who will not upgrade to spark 2.0 are not excluded....
We need to introduce several profiles in maven, against spark 1.6,1.6.1, 2.0, and scala 2.10, 2.11.....etc.

+1

+1


Assess HTML interactive examples

User story
Given the new HTML interactive examples, assess all examples to determine whether they need updates
Acceptance criteria
We have a list of HTML examples that need updates.

-> https://github.com/mdn/interactive-examples/issues/1138#issuecomment-432043942


Add i18n support to Data Management Interface front end app

AS a Data Management Interface user
I WANT TO use multilanguage application
IN ORDER TO see use the application in my preferred language
Acceptance Criteria:

[ ] Front end React.js uses i18n support framework Introduction, changes to i18n translation files take effect on GUI immediately
[ ] New languages can be added to the application

@kunnark @alimuhammadahmer add "Changes to i18n translation files take effect on GUI immediately" as part of AC.

@turnerrainer AC improved.

@alimuhammadahmer please refer to commit(s) to i18n translation files.

@turnerrainer  https://github.com/buerokratt/Data-Anonymizer/pull/121/files#diff-346d5fefd7c4b5283fa3fc037f9debc51e039e0e9e43dbda8df28997bcc6c1a8


feat(nextjs): update deps, ZITADEL provider

@peintnermax I had a look at this PR and tried to run it from scratch. I think it needs some love:
Installation (readme)
The two sections are not helpful

https://github.com/zitadel/zitadel-examples/tree/nextjs-auth-update/nextjs#getting-started
https://github.com/zitadel/zitadel-examples/tree/nextjs-auth-update/nextjs#install-authentication-library

Instead what I had to do

clone the repo
cd nextjs
yarn install
yarn run dev
open localhost:3000

or am I missing something?
Configuration

I would split the section into Setup in ZITADEL and Configuration
Put Setup in ZITADEL first then continue with configuration of the nextjs app
The link to ZITADEL projects points to zitadel.ch

.env file

there is an env file in the repo, please update to reflect the new version:

NEXTAUTH_URL=http://localhost:3000
ZITADEL_ISSUER=[yourIssuerUrl]
ZITADEL_CLIENT_ID=[yourClientId]
ZITADEL_CLIENT_SECRET=[randomvalue]
NEXTAUTH_SECRET=[randomvalue]

I got an error, so we might want to add the NEXTAUTH_SECRET:

export default NextAuth({

  providers: [
  ],
  callbacks: {
  },
  secret: process.env.NEXTAUTH_SECRET,
});

will link a PR for the zitadeldocs soon where links will be updated


Change page titles so that page-content title comes before the site title

Currently page titles are of the form KEDA | <content-title>. It is more typical (and makes analytics analytics easier) if title has a format like <content-title> | KEDA.
Any objections to making this change @tomkerkhove et all?

@kedacore/keda-maintainers Any objections on this?

+1

Majority, let's do it @chalin!

/assign


Sentiment analysis

It'd be cool to add a sentiment analysis to determine the negativity or positivity of the text being processed.

We've experimented with that a lot, we just haven't implemented it in the current version of Knwl.js quite yet. Thanks, @NoelDavies!


jQuery loading issue

I have a slider that is loaded with jquery that gets broken when transitioning between pages. Will I have to find a way to reload jquery as well as my scripts utilizing it under the provided event listeners?

Ah. I see what I was doing now. I didn't reload all of my variables that utilized jquery in the swup event listener causing a break. Thank you for getting back to me.


Add Cards alignments to Contributors section instead of slideshow to Improve UX

Hey @Akshatchaube01
I suggest adding cards only instead of slideshow to the our contributors section in about us page
as the slideshow never stops even when hover, making it Is difficult to see the list also it reduce the  user experience
https://github.com/user-attachments/assets/a4be7f40-c36f-4ea4-924c-99a5d2f4e3d7
I would like to remove it and add cards only with proper alignments and perfectly responsive!
Like this:

https://github.com/user-attachments/assets/221f5759-c11f-40b1-b4a6-e0fca1a6c9e7

We are not looking for this right now


[CARBONDATA-4161] Describe complex columns

Why is this PR needed?
Currently describe formatted displays the column information of a table and some additional information. When complex types such as  ARRAY, STRUCT, and MAP types are present in the table, column definition can be long and it’s difficult to read in a nested format.
What changes were proposed in this PR?
The DESCRIBE output can be formatted to avoid long lines for multiple fields. We can pass the column name to the command and visualize its structure with child fields.
Does this PR introduce any user interface change?

Yes ,
DDL Commands:

DESCRIBE COLUMN fieldname ON [db_name.]table_name;
DESCRIBE short [db_name.]table_name;

Is any new testcase added?

Yes

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3349/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5100/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5103/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5136/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3385/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3402/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5176/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3424/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5178/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3426/

retest this please

LGTM

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5179/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3427/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5189/

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3437/

LGTM

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3444/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5196/

retest this please

Build Success with Spark 2.4.5, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbon_PR_Builder_2.4.5/3461/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12602/job/ApacheCarbonPRBuilder2.3/5209/


Does "pegtl" support the operation of binary data serialization/deserialization?

If yes, have you provided any demonstration examples? Thank you
I only saw the parsing of "protobuf" syntax, but did not find a real example of parsing and mapping binary data blocks.

The PEGTL is for parsing, so it can't help you with serialisation, regardless of text or binary formats.
For deserialisation I'd say the PEGTL isn't especially well suited to binary data, however (a) we have used the PEGTL infrastructure in our taoJSON library for parsing binary JSON-like data formats (CBOR, UBJSON and MsgPack) and (b) support for binary data will be improved as soon as I get around to finishing the back-porting of some experiments to the main branch.
You can look at the taoJSON code here: https://github.com/taocpp/json/tree/main/include/tao/json and If you want to try parsing binary data with the PEGTL then please feel free to contact us here, both for questions and for feedback, it's always useful to see how other people use the library.

Yes, I am considering using "pegtl" for binary deserialization parsing. Binary data blocks are also composed of different rules, and there are two parsing methods

Describe the specified binary block by parsing the "protobuf" syntax, and use a virtual machine like method to complete data deconstruction

The rules for defining binary blocks with c++templates are parsed through template expansion.

The first method may cause some consumption, but supports hot update
The second method may be zero consumption, but each rule modification requires recompilation, and templating may not be suitable for the hash table structure


Releases Should have checksums

Downloading a tar file from the releases page without a corresponding checksum file is frightening :fearful: . Maybe you could make them as part of your release process?

https://github.com/cue-lang/cue/releases/download/v0.4.0/checksums.txt

@nathanjsweet as @verdverm linked we already have the checksums included as part of our release assets so I believe this issue can be closed. Please do reply in case we've misunderstood.


USB: naming thread for usbd work queue

usb drivers usually allocate a work queue (usb_dc_nrfx.c, usb_dc_kinetis.c, usb_dc_native_posix.c) but don't name it, which is annoying when debugging and an unknown thread is listed
Adding something like would be helpful
k_thread_name_set(&usbd_work_queue.thread, "usbdworkq");

@sdalu why don't you send a Pull Request?

@carlescufi I'll certainly do it, next year, but at least there is a reminder :sweat_smile:

@carlescufi I'll certainly do it, next year, but at least there is a reminder :sweat_smile:

Here's your yearly-ish reminder :)


pass props to handleSubmit() function

#1546

Current coverage is 96.87% (diff: 100%)

Merging #1548 into v5 will increase coverage by <.01%

@@                 v5      #1548   diff @@
==========================================
  Files            73         73
  Lines          4159       4163     +4
  Methods         769        770     +1
  Messages          0          0
  Branches        315        315
==========================================
+ Hits           4029       4033     +4
  Misses          130        130
  Partials          0          0

Powered by Codecov. Last update bd1cecf...e9cbf35

Released as v5.3.3.


Payer can not be different accounts error

I currently am trying to send a transaction as follows:
		var response =
			await
			fcl.send
			(
			[ fcl.transaction (_transaction_code)
			, fcl.args (_arguments)
			, fcl.proposer (proposer)
			, fcl.payer (proposer)
			, fcl.authorizations ([fcl_api.authz, proposer])
			, fcl.limit (9999) ] )
		return await
			fcl .tx (response) .onceSealed () }

On the old version of the js fcl API, it works fine and the transaction goes through. However on the new version, I get the following error message:

Is this caused by issue #1226. If yes, is there any workaround till the issue is fixed?

Has this been fixed yet?

having same issue


Saving "last_column" in visit_Arel_Attributes_Attributes may break Arel::Nodes::NamedFunction

Maybe I'm not "doing it right", but I cound't find any solutions by browsing through the source code or checking
Google... So, here it goes:
When calling a named function such as "CONCAT" with table columns/attributes among the parameters, the type of the column/attribute is used to convert the following attribute. As far as I could understand, this is required to properly convert the type of the right hand side of binary visitors, and is acomplished by saving the "last_column" instance attribute when visiting a Arel::Attribute::Atribute (which is later used by "quote").
However, when supplying a list of values to a named function (or any other arel node which uses "expressions.map{}" I believe), the evaluation of the nodes sequentially breaks due to this type convertion.
An example always helps, so:
class T < ActiveRecord::Base
end
ts = T.arel_table
Arel::Nodes::NamedFunction.new('CONCAT', [ts['id'], '#']).to_sql
# "CONCAT(`complaint_records`.`id`, 0)"
Not that the '#' string is converted to 0, because the previous value in the array is an Arel::Attributes::Attribute whose type is "integer".

This can be closed as per https://github.com/rails/rails/issues/10655#issuecomment-18094629


feat(cli): add a list-names verb, accept "raw" paths

This commit:

adds a cargo hax list-names commands that outputs the list of all external names used by a crate. Note that outputs "raw" paths.
make the --include-namespace option accept "raw" paths.

Closing this, we have to implement it a nicer way, PR #743 should help.
Tracking issue: https://github.com/hacspec/hax/issues/767


service.describe() throws because of spelling error

There's a spelling error in tapregext.py of fornat instead of format.  Subtle.
When I tried to run the following code:
import pyvo
service = pyvo.dal.TAPService('http://gea.esac.esa.int/tap-server/tap')
service.describe()
Output:
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): gea.esac.esa.int:80
DEBUG:urllib3.connectionpool:http://gea.esac.esa.int:80 "GET /tap-server/tap/tables HTTP/1.1" 200 None
DEBUG:urllib3.connectionpool:Starting new HTTP connection (1): gea.esac.esa.int:80
DEBUG:urllib3.connectionpool:http://gea.esac.esa.int:80 "GET /tap-server/tap/capabilities HTTP/1.1" 200 None
Capability ivo://ivoa.net/std/TAP
Interface vs:ParamHTTP
http://gea.esac.esa.int/tap-server/tap/tap
Language ADQL
Output format application/x-votable+xml
Also available as votable
Output format application/x-votable+xml
Also available as votable_plain
Output format text/csv
Also available as csv
Output format application/json
Also available as json
Output format application/fits
Also available as fits
Output format text/xml
Also available as votable_plain_conesearch
Upload method supported
ivo://ivoa.org/tap/uploadmethods#inline
Upload method supported
ivo://ivoa.org/tap/uploadmethods#http
Upload method supported
ivo://ivoa.org/tap/uploadmethods#ftp
Upload method supported
ivo://ivoa.net/std/TAPRegExt#upload-inline
Upload method supported
ivo://ivoa.net/std/TAPRegExt#upload-http
Upload method supported
ivo://ivoa.net/std/TAPRegExt#upload-ftp
Time a job is kept (in seconds)
Default 259200
Traceback (most recent call last):
File "./vo2oracle.py", line 11, in
service.describe()
File "/home/cbanek/env/lib/python3.6/site-packages/pyvo/dal/tap.py", line 328, in describe
cap.describe()
File "/home/cbanek/env/lib/python3.6/site-packages/pyvo/io/vosi/tapregext.py", line 401, in describe
print(indent("Maximum {}".fornat(self.retentionperiod.hard)))
AttributeError: 'str' object has no attribute 'fornat'
Fix is incoming in a PR.

Thank you. Somewhere i fixed this, but it seems it landed in some git stash kind of black hole.
Please do the PR against the v0.9.x branch.


#1 Build vue framework

To lock the versions of dependencies that are installed over a project.
For more information, please checkout this link.
https://stackoverflow.com/questions/48524417/should-the-package-lock-json-file-be-added-to-gitignore


Current table models can't support overtime

need to find a game with overtime and scrape data, possibly create new function for body for overtime?

Commit 7ebdd48 addressed this in Dev branch.


Wanted: a variant of parse_macro_input that produces the intermediate Result.

Goal
I want to implement a struct MyAttrArgs with a method:
impl MacroArgs {
  fn parse(args: TokenStream) -> syn::Result<Self> { … }
}

I am attempting to use darling because it provides the right user experience and nice developer ergonomics: the parameters get parsed into a custom struct.
Problem
I cannot rely on parse_macro_input!, as the darling example suggests, because that literally returns a TokenStream (which doesn't fit my desired return type).
I cannot use syn::parse2 which has the right interface for my desired API, except syn::AttributeArgs doesn't implement syn::parse::Parse.
Questions
The main big picture question is: am I just confused about how to design proc-macros implemetations well?
Specific questions:

Why doesn't syn::AttributeArgs implement Parse so that I could use parse2?
Why can parse_macro_input! parse things that parse2 cannot? Is there a rationale for that? (And how does it accomplish this?)
Why isn't there a variant of parse_macro_input! which produces the intermediate Result directly instead of hardcoding a return?
(For darling:) Why doesn't darling implement syn::parse::Parse for the annotated structs so that they could be produced by parse2?
(For darling:) Why doesn't FromMeta have a method like from_tokenstream(TokenStream) -> syn::Result<Self> ?

Update: if I call into a doc(hidden) API, my project compiles and tests pass. :-(
The call site is: let args: syn::AttributeArgs = syn::parse_macro_input::parse(tokens.into())?;

Update: I implemented a work-around by hand-rolling a parser with this signature:
/// We cannot use `parse_macro_input!` which returns a `TokenStream` and `AttributeArgs` does not
/// impl `syn::parse::Parse`, so we do this by hand. :-<
fn parse_attribute_args(tokens: TokenStream) -> Result<syn::AttributeArgs> { … }

Now tests pass. It really feels like I'm doing something wrong or missing a big picture about proc-macro implementation design, but it works for now.

syn::AttributeArgs no longer exists in syn 2 so I'm not sure whether this is still necessary.

I'll have to dust off that project and see what's the right replacement for AttributeArgs.
Meanwhile, I still remain confused about the macros returning TokenStream whereas I want to write many small functional building blocks that return syn::Result<T> and I'm not clear on how to match up the impedance mismatch.


Handle Deprecated Fideslang Resources in Fides

Is your feature request related to a specific problem?
We now support marking Fideslang taxonomy resources as deprecated but Fides does not treat deprecated resources differently.
This PR deprecates our first data use in Fideslang. https://github.com/ethyca/fideslang/pull/174
Describe the solution you'd like
Don't return deprecated taxonomy items in the API or filter the FE to not display deprecated taxonomy items.  Make it so they're not visible and can't be assigned to other resources.
Describe alternatives you've considered, if any
A description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

https://ethyca.atlassian.net/browse/PROD-1216

@rsilvery this has not been completed


.lock - ransomware (false-positive)?

Hello,
We recently had a request to have your software utilized for XML modeling with Abacus, however, as part of our analysis and scanning process a file was flagged as ransomware. (see attached)
We contacted support via the Contact's page on your website and they replied stating that it was a false-positive and that the file was of "zero-byte / zero length". Nonetheless we have refrained from using this software until we can receive a solid confirmation that the scan was in fact a false-positive.
We used the x64 install with SHA-1 > bb71df085ef3522bc379529a785a69064b9f7b27    Archi-Win64-Setup-5.2.0.exe.
We like to gain confidence in utilizing this software and would like for the scan conducted by Cuckoo to result with no ransomware flag. Might there anything that can be done to reassure no such ransomware exists in your software?
V/R - Alex

As I said, that file is a zero length byte that is part of the installation of the underlying Eclipse framework. It's a lock file. It's empty, it does nothing. It's not even used.
I suggest you contact Cuckoo.

Appreciate the reply and clarification.
On Jan 18, 2024, at 1:39 AM, Phil Beauvoir @.***> wrote:

As I said, that file is a zero length byte that is part of the installation of the underlying Eclipse framework. It's a lock file. It's empty, it does nothing. It's not even used.
I suggest you contact Cuckoo.
—
Reply to this email directly, view it on GitHubhttps://github.com/archimatetool/archi/issues/1016#issuecomment-1898124196, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AU6B535YTCRQQVVU4Z66F5LYPDUTPAVCNFSM6AAAAABB743BE6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJYGEZDIMJZGY.
You are receiving this because you authored the thread.Message ID: @.***>


⚠ Bofrost.lu has degraded performance

In 1f9a54a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1674 ms

Resolved: Bofrost.lu performance has improved in 0428d6a after 6 minutes.


Is HA  Bridge mainly for lighting controls? Can device category be customized?

I tried to add the Ecobee3 and Schlage locks and it comes up to be a switch.
I also have dry contact switches acting as my garage and gate opener, when I say turn on all lights it opens my garage and my gate as well. Can device category be customized?

Everything is handled like a switch in essence as the ha-bridge emulates a Philips Hue Bridge. So you can control anything you want with what you put in the URLs, but is in the context of ON, OFF and DIM to the ha-bridge.

Did I answer your question?


Box visible below button

For the following code, using angular ladda version 0.3.1:
<button type="button" class="btn btn-success" data-dismiss="modal" ng-disabled="changeform.$invalid || !valuesChanged()" ng-click="submit()" ladda="loadingStatus.loading" data-style="expand-left">{{'Change' | translate}}</button>

I get an ugly box below the button when I click it. The ladda-spinner appears, but so does the box. (I wasn't quick enough to catch both at the same time though, so in this screen shot you can only see the ugly box):

I believe this has to do with the way ladda is placing the spinner, and nothing to do with this project. Unfortunately, ladda's issues tracker is closed.

@floydqwz I also think this is ladda library issue. But if you change some css style, it should be resolved. Try add some style your button like overflow: hidden.


Request: Show monster element damage & blights.

Would it be possible to add each monsters elemental damage and what blights they can inflict on their weakness page?

This has been implemented in the monster summary screen. Thanks for you input!


add poissonreg

[x] I have converted fonts to outlines in the .svg
[x] My PNG has dimensions 2521 x 2911

Can you please remove the url from the sticker? We're no longer using them because you can't actually read them on the printed stickers.

The URL is now removed on the svg and the png, thanks to @gregswinehart 🙌


Move GenericIssuer code out of the v1 API

In  https://github.com/jetstack/cert-manager/pull/3038/#discussion_r449145480  @munnerz  wrote:

This [GenericIssuer] is used by the 'issuers' and 'clusterissuers' controllers so that they can work with both Issuer types and ClusterIssuer (by having them both implement 'GenericIssuer').
The signatures returned version types (e.g. GetSpec() returns a v1beta1 IssuerSpec etc).
It's not actually used right now in this API version, so we can remove it. I agree it shouldn't be in this package, and I think it should be possible to 'refactor this away' with some better written controllers for issuers.
Will remove from v1beta1, but leaving in v1alpha3 and 2 as I don't want to make a retroactive change in this PR smile

I considered doing this refactoring in https://github.com/jetstack/cert-manager/pull/3196 but wimped out. Let's do it after the v1 release.
/kind feature

/area api
/priority important-longterm

/close


[Automated] Upgrade to latest dependencies

Produced via:
./hack/update-deps.sh --upgrade
./hack/update-codegen.sh

/cc houshengbo
/assign houshengbo

Let me regenerate the deps manually to see how it goes.


Adding "Must" panic sinks.

I added the sinks, but will not write test or change the documentation until I know that this is wanted and gets included.
This lets you write prototypes (or even production code) with less error checking cluttering.
For example:
goVersion := script.Get("https://go.dev/VERSION?m=text").MustString()

As panics() can be recovered, this can be an elegant strategy to write script like code, quite secure in my opinion.

retracted


Support Backward Compatibility with ElasticSearch 6.8 & 7.x versions

Description
It is draft PR to discuss the approach for supporting backward compatibility with ElasticSearch nodes.
The way version compatibility logic is implemented in 6.8 & 7.x, the OpenSearch has to return a 7.x version for it pass. OpenSearch node will return 7.10.2 if the remote node is ElasticSearch node otherwise 1.0.0
Note: Couple of tests are failed. I did basic sanity by launching mixed cluster using docker to ensure ElasticSearch & OpenSearch nodes are able to connect to each other. Raising it early to get feedback on the approach.
Issues Resolved
https://github.com/opensearch-project/OpenSearch/issues/669
Check List

[ ] Add logic to return BC ES version during handshake
[ ] Remove masking logic
[ ] Add logic to ensure OpenSearch is treated as successor to ES versions
[ ] Besides handshake, JoinExecutor logic also expects compatible version in DiscoveryNode object otherwise node will fail to connect to master
[ ] Add checks to fail handshake if ES node >= 7.10.3 (an actual ES node) as those version could be incompatible with OpenSearch
[ ] Verify any other class which is calling writeVersion if it depends on localNode version
[ ] All tests pass
[ ] Run BWC tests
[ ] Document the behavior of APIs when mixed nodes are present in the cluster

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Approach during Handshake:

HandshakeRequest sends the minCompatibleVersion of the local node as it is not aware of the remote node version yet
During HandshakeResponse remote node sends its actual version, which is then set as the channelVersion.
The current proposal in the PR is to use 6.7.99 as the minCompatibleVersion for OpenSearch 1.x instead of 6.8 as this helps in (indirectly) identifying the remote node version during handleHandshake method itself and then send appropriate version (BC ES version/ OpenSearch 1.x version) in response. The advantage of doing is early identification of remote node version as otherwise if OpenSearch node also sends 6.8.0, there is no way to differentiate ES 7.x version from OpenSearch version and OpenSearch node will end up sending BC version to both ES & OpenSearch remote node. Sending only BC version to ElasticSearch node provide easy deprecation path for this BC version logic in OpenSearch 2.0.0 (which can expect upgrade from only Opensearch 1.x, though this is not finalized yet). Also 6.7 is already EOL, so there is no way there will be a real 6.7.99 version from ElasticSearch.

Callout:

Also considered sending a pseudo version something like 7.10.99 in response, this could help if customer want to identify OpenSearch nodes in APIs like _cat/nodes, Thoughts?
The response of some API like _cat/nodes will show BC if the request is routed via ElasticSearch node. Pending list of all the APIs impacted.

@dblock : we added this masking logic earlier so that OpenSearch version id is higher than ES version ids but that is not working out as ES minCompatibility logic doesn't allow any higher version but only one higher version is accepted and as we need to support 6.8 as well, so BC version from OpenSearch has to be 7.x

@shwetathareja This can be closed, no?


Clover Sliders Fetch the id of the body for Canvases

Hello,
Today while experimenting with A/V in Canopy, I noticed a problem that seems to be coming from Clover Sliders.  Whenever a thumbnail in a Clover Slider represents an A/V work, it attempts to fetch the id of the body of the Canvas.
Here is an example where you can see this (just look at the Network tab on the main page or any work page):
https://rfta-fall-2023.vercel.app/
You can also see it here:
https://dc.library.northwestern.edu/items/46394d80-6862-479a-bac1-e5486bc86723

This has been resolved in https://github.com/samvera-labs/clover-iiif/pull/151


adds support for compliance filter query param on compliance route

Codecov Report

Merging #1394 into master will decrease coverage by 0.11%.
The diff coverage is 64.28%.

@@            Coverage Diff             @@
##           master    #1394      +/-   ##
==========================================
- Coverage   60.67%   60.55%   -0.12%
==========================================
  Files         181      183       +2
  Lines        3987     3998      +11
  Branches      914      914
==========================================
+ Hits         2419     2421       +2
- Misses       1568     1577       +9

Impacted Files
Coverage Δ

wherehows-web/app/routes/browse/entity.ts
72.72% <ø> (ø)
:arrow_up:

wherehows-web/app/controllers/datasets/dataset.ts
23.25% <ø> (ø)
:arrow_up:

wherehows-web/app/constants/datasets/shared.ts
77.27% <ø> (ø)
:arrow_up:

wherehows-web/app/utils/helpers/routes.ts
100% <ø> (ø)
:arrow_up:

...web/app/controllers/datasets/dataset/compliance.ts
100% <100%> (ø)

wherehows-web/app/routes/search.ts
100% <100%> (ø)
:arrow_up:

...hows-web/app/routes/datasets/dataset/compliance.ts
50% <42.85%> (ø)

wherehows-web/app/routes/datasets/dataset.ts
16.66% <50%> (ø)
:arrow_up:

wherehows-web/app/components/purge-policy.ts
81.48% <0%> (-18.52%)
:arrow_down:

... and 2 more

Continue to review full report at Codecov.

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

Coverage remained the same at 22.752% when pulling ef6cfdc02ae64b65b873d0a9063af6843e152d6a on theseyi:compliance-filter-query into cd94e5af6fc574323f3f25ed0c2a490cd5f8aaae on linkedin:master.


lxcfs restarted on update rather than reloaded

Cannot open /proc/stat: Transport endpoint is not connected in some containers, access available after container restart, I couldn't reproduce on another lxd hosts (but thats could be due over 100 days uptime with canonical-livepatch on production hosts), all auto-updated to lxcfs from proposed (2.0.8-0ubuntu1~16.04.1), but using http://ppa.launchpad.net/ubuntu-lxc/lxd-stable/ubuntu xenial main, mb thats the issue.
Ubuntu 16.04.x
 driver: lxc
  driver_version: 2.1.0
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.13.0-16-generic
  server: lxd
  server_pid: 10127
  server_version: "2.18"
  storage: btrfs
  storage_version: "4.4"

lxc<PHONE_NUMBER>4943.490 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>4943.490 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>4943.983 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>4943.983 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>2826.172 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>2826.230 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>2826.230 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>2826.354 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc<PHONE_NUMBER>2826.354 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.

This is very likely a lxcfs problem. Can you show systemctl status lxcfs and lxcfs --version, please?

2.0.8-0ubuntu1~16.04.1
`
● lxcfs.service - FUSE filesystem for LXC
Loaded: loaded (/lib/systemd/system/lxcfs.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-11-08 06:53:18 UTC; 3h 2min ago
Docs: man:lxcfs(1)
Process: 10087 ExecStopPost=/bin/fusermount -u /var/lib/lxcfs (code=exited, status=0/SUCCESS)
Main PID: 10109 (lxcfs)
Tasks: 5
Memory: 3.3M
CPU: 23ms
CGroup: /system.slice/lxcfs.service
└─10109 /usr/bin/lxcfs /var/lib/lxcfs/
Nov 08 06:53:18 lxcfs[10109]:   2: fd:   7: freezer
Nov 08 06:53:18 lxcfs[10109]:   3: fd:   8: perf_event
Nov 08 06:53:18 lxcfs[10109]:   4: fd:   9: rdma
Nov 08 06:53:18 lxcfs[10109]:   5: fd:  10: net_cls,net_prio
Nov 08 06:53:18 lxcfs[10109]:   6: fd:  11: pids
Nov 08 06:53:18 lxcfs[10109]:   7: fd:  12: cpu,cpuacct
Nov 08 06:53:18 lxcfs[10109]:   8: fd:  13: hugetlb
Nov 08 06:53:18 lxcfs[10109]:   9: fd:  14: cpuset
Nov 08 06:53:18 lxcfs[10109]:  10: fd:  15: blkio
Nov 08 06:53:18 lxcfs[10109]:  11: fd:  16: name=systemd
`
lxcfs --version
2.0.8

Hm, seems that somehow fuse got unmounted on one of the updates. If you can restart the container this should fix it.

Just checked, and actually I have it on production lxd hosts too.
So yes https://launchpad.net/ubuntu/+source/lxcfs/2.0.8-0ubuntu1~16.04.1
This update didn't worked good for me.

Uploaded a fix.


Optimised layout

Describe the solution you'd like
It would be interesting to develop some scripts to compute the best layout, taking into account a corpus of text and few metrics.
This paper shows that trigrams ordered layout can be up to 15% faster than unigram based layouts.
It also proposes some measures of efficiency, however it seems these measures do not have much correlation with actual wpm.

however it seems these measures do not have much correlation with actual wpm.

wpm is like the least important metric anyway (so long as it's not going down) - over a lifetime of typing, or even just a few years if you type a lot as my horribly damaged thumbs and relevant hand parts discovered, the metric that really matters is, in decreasing order: strain (how far from resting state are you reaching, with how much muscle activation and tension), distance you gotta cover, and maybe total motion.


[#137] Fix migration bug and add correct setup command

https://github.com/DivanteLtd/vue-storefront/issues/137
Now migration and restore dump work correct.

Thanks Sergey!


Change Angular 2.0 alpha reference to beta

Now that Angular 2.0 has been promoted to a beta product, the alpha reference in the doc should be replaced.

:shipit:

Merged. Thanks! e601c479158ee4abeb2d401b9688545ff23b30a0


Remove unused option from Lift Down help

Lift down does not uses the "--auto-approve" option (See #254), so it shouldn't appear in the help of the lift down command

Thanks for the PR!


Websockets.Client does not support DNXCore

I get this error when trying to add Microsoft.AspNet.WebSockets.Client as a dependency of a DNXCore application:
The dependency Microsoft.AspNet.Websockets.Client 1.0.0-rc1-final in project "..." does not support framework DNXCore,Version=v5.0

A quick glance at the project.json for the Protocol and Server projects shows that they correctly target DNXCore, but Client does not. Any way we can get that changed?

That won't be possible for this project, it takes advantage of capabilities in HttpWebRequest that are only present on full .NET. I only created this project as a proof of concept and to enable Win7 clients.
Most apps should just use System.Net.WebSockets.ClientWebSocket, For CoreCLR this is available in System.Net.WebSockets.Client.

Roger, thanks. Might be a good idea to indicate that somewhere so as to dissuade any future misunderstanding.


#304: Fixes the height of lines container when additional panels are …

This fixes the height of lines container when additional panels are added to Content Manager (e.g. backlinks in document added by Backlinks core plugin).
Example before fix:

Example after fix:

@vslinko  please take a look :)

@vslinko look pls!


Add Prettier, Eslint, husky, lint-staged in the monorepo_setup branch

Description
Adding eslint and prettier will make sure everyone follows the standard of the code. Both should run as part of lint-staged using husky.
Expected Behavior
When ever someone commits the changed, the husky should run the commands provided pre-commit. The pre-commit commands should be eslint and prettier fixes. These commands should run in all the application inside packages.
Current Behavior
No eslint or prettier.
Notes
- Reference repository here.
- Brand should be made from monorepo_stepup and PR should also be raised on the same branch.
Confirmation Checklist

[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.

@aps08  can you assign me this issue

@a-s-t-e-y-a Are you part of team.shiksha discord server ?

Yes

Let's connect over there, and we can discuss. @a-s-t-e-y-a

okay


Avoid unnecessary clones

Avoid unnecessary clones
Description
Modify VirtualMachine::load_data, MemorySegmentManager::load_data, Memory::insert and Memory::insert_value to avoid unnecessary .clone() invocations.
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #478 (65a0629) into main (7945b60) will decrease coverage by 5.30%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #478      +/-   ##
==========================================
- Coverage   96.62%   91.32%   -5.31%
==========================================
  Files          52       48       -4
  Lines        9071     2951    -6120
==========================================
- Hits         8765     2695    -6070
+ Misses        306      256      -50

Impacted Files
Coverage Δ

src/vm/vm_core.rs
92.92% <ø> (-3.42%)
:arrow_down:

src/vm/vm_memory/memory.rs
93.42% <100.00%> (-3.64%)
:arrow_down:

src/vm/vm_memory/memory_segments.rs
95.23% <100.00%> (-3.56%)
:arrow_down:

src/cairo_run.rs
72.91% <0.00%> (-14.19%)
:arrow_down:

src/vm/context/run_context.rs
78.78% <0.00%> (-14.13%)
:arrow_down:

src/vm/runners/builtin_runner/bitwise.rs
67.64% <0.00%> (-13.71%)
:arrow_down:

src/serde/deserialize_program.rs
79.72% <0.00%> (-13.67%)
:arrow_down:

src/vm/runners/builtin_runner/ec_op.rs
79.66% <0.00%> (-12.24%)
:arrow_down:

src/vm/runners/builtin_runner/output.rs
76.92% <0.00%> (-11.97%)
:arrow_down:

src/serde/deserialize_utils.rs
81.53% <0.00%> (-9.64%)
:arrow_down:

... and 38 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

This got bit rotten.


Just questions

1: does catt do anything to keep cast_site running?
If I run catt from linux, the website seems to keep running indefinitely, great for info screens..
However, belive it or not, not everybody have a linux machine handy.
There are apps to do the same on android, however they all seem to close the browser in the chromecast when I close the app, so the TV goes back to the pause screen when I close the app. Even if I disconnect the phone from wifi, the TV still stops.
Is it just a matter of finding an app. which doesn't force the chromecast to stop when closing the app, or id there some part of catt which run in the background?
2: Is there a catt for windows? Casting a chrome tab from a windows PC still leaves the problem that the rendering is done on the PC, which then have to stay running at the site.
3: Does the browser in the new chrome tv-stick have a higher resolution than the "lowres" from the regular chromecast?

No part of catt runs in the background, it exits when you see iti exit.
It should work on Windows, yes.
I'm not sure about that, unfortunately.

Just to inform: Catt indeed can run and work under Windows 10.
Indeed, it can be installed on Android, even run, but alas Catt scan show no devices.

Hmm, I think that depends on your setup, because it shows devices on my phone just fine. There are some general scanning issues that may also affect it. Thanks for the update!


Fix cast to null

It currently fails with ArrowNotImplementedError instead of TypeError when one tries to cast integer to null type.
Because if this, type inference breaks when one replaces null values with integers in map (it first tries to cast to the previous type before inferring the new type).
Fix https://github.com/huggingface/datasets/issues/4483

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Update to google-auth 0.9 to support newer Guzzle version

I already have Guzzle so can't use this until it's updated to use google-auth v0.9
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - google/apiclient v2.0.0 requires google/auth 0.8 -> satisfiable by google/auth[v0.8].
    - Installation request for google/apiclient ^2.0 -> satisfiable by google/apiclient[v2.0.0].
    - Conclusion: remove guzzlehttp/psr7 1.3.0
    - Conclusion: don't install guzzlehttp/psr7 1.3.0
    - google/auth v0.8 requires guzzlehttp/psr7 1.2.* -> satisfiable by guzzlehttp/psr7[1.2.0, 1.2.1, 1.2.2, 1.2.3].
    - Can only install one of: guzzlehttp/psr7[1.2.0, 1.3.0].
    - Can only install one of: guzzlehttp/psr7[1.2.1, 1.3.0].
    - Can only install one of: guzzlehttp/psr7[1.2.2, 1.3.0].
    - Can only install one of: guzzlehttp/psr7[1.2.3, 1.3.0].
    - Installation request for guzzlehttp/psr7 (locked at 1.3.0) -> satisfiable by guzzlehttp/psr7[1.3.0].

@bencromwell I have opened a PR to fix this, but please tell me why it's so important to use guzzlehttp/psr7:1.3.0?

@bencromwell try adding "google/apiclient": "^2.0" directly to composer.json and running composer update and you'll have a better time.
Composer won't update your existing deps unless you run composer update, so it behaves differently when you simply use composer require, and in this case, throws an error.

I see what you mean - at first I thought you meant the package in general now I see you meant that specific version.
Composer update does indeed work:

Removing guzzlehttp/psr7 (1.3.0)
Installing guzzlehttp/psr7 (1.2.3)
Downloading: 100%

Can only assume judging by semver that any implementation using these deps (older version) is missing backwards compatible fixes.
Thanks for opening the PR :+1:


ERROR:wally.report:Diring hdd report generation

Hi,
after i started an hdd test on a local attatched disk, under debian 9.
I get following error durring report creation:
10:54:24 - INFO     - wally           - Start html_report_stage
INFO:wally:Start html_report_stage
10:54:24 - ERROR    - wally.report    - Diring hdd report generation
Traceback (most recent call last):
File "wally/report.py", line 821, in make_io_report
report = func(dinfo, lab_info, comment)
File "wally/report.py", line 642, in make_hdd_report
images = make_plots(perf_infos, plots)
File "wally/report.py", line 511, in make_plots
error2=data_dev)
File "wally/report.py", line 374, in io_chart
matplotlib.rcParams.update({'font.size': 10})
NameError: global name 'matplotlib' is not defined
ERROR:wally.report:Diring hdd report generation
Traceback (most recent call last):
File "wally/report.py", line 821, in make_io_report
report = func(dinfo, lab_info, comment)
File "wally/report.py", line 642, in make_hdd_report
images = make_plots(perf_infos, plots)
File "wally/report.py", line 511, in make_plots
error2=data_dev)
File "wally/report.py", line 374, in io_chart
matplotlib.rcParams.update({'font.size': 10})
NameError: global name 'matplotlib' is not defined
Would be great if i can get a fix for that.
OS: Debian 9.4
To get fio running i have copied the fio binaries and renamed it to fio_stretch_x86_64.bz2
I have installed disk_perf_test_tool via:
git clone https://github.com/Mirantis/disk_perf_test_tool.git
I have executed: /disk_perf_test_tool/scripts/install.sh
After that i have run local HDD Test via:
python -m wally test hdd configs-examples/hdd2.yaml
hdd2.yaml:
include: default.yaml
explicit_nodes:
local: testnode
tests:
- io:
cfg: hdd
params:
FILENAME: /dev/vdb
TEST_FILE_SIZE: 2G

Sry, v1 is not supported anymore. Issue does not appear in v2. Will close this


about the gpu device and training

It seems that PUFlow is better than previous work. I want to know the GPU used in this paper and about all the training time.
thanks again, I note that PDFlow is also your work, and thanks for your reply in My PDFlow issue yesterday.

This work is also trained on an RTX3080 card.
For the discrete model, we trained on each dataset for about 12-16 hours.
For the continuous model, it is hard to tell when the model is converged. But for the specific model we provided in this repo, it took about 3-4 days in practice.


How to install on Windows.

Description
I read this on the README

Neofetch supports almost 150 different operating systems. From Linux to Windows, all the way to more obscure operating systems like Minix, AIX and Haiku.

And I also read https://github.com/dylanaraps/neofetch/wiki/Installation, but couldn't find any documentation about Windows installation.

You need to be using Cygwin, MSYS/MingGW or Linux substrate for Windows. You can install Neofetch using the Makefile or by just downloading the script and running it.

Personally, I installed it using scoop


[FEATURE] Hamburger color

Description
the Hamburger color should be White (to much color in the navbar and typography, white make it look better than black)
Screenshots
from this...

to this ...

We need to confirm with the design team first, before we fix this.

go ahead man

Awesome!! I'll close the issue now! 🚀🚀


Switch to new PPA for R packages

I am the maintainer of this PPA. I am migrating it into a new PPA that contains backports of important libraries needed for building R packages on Travis.
Thanks!
@jimhester

LGTM

@BanzaiMan can you merge this? Both R reviewers (me and jim) have approved :)


Update README.md

Update deprecated clojure alias invocations

Thank you!


update-lerna-manifest: flag to only update the tsconfig.json (top level)

use case: we use regexes in the lerna manifest but want to use the make packages functionality without manual modification

This is handled by the typescript-build-linker for now, at least in simple cases. In fact, opening an issue to stop editing the top-level tsconfig.json in the first place
probably won't get to it for a long time

This is handled by the typescript-build-linker for now, at least in simple cases. In fact, opening an issue to stop editing the top-level tsconfig.json in the first place
probably won't get to it for a long time


feat: add upper bound for max epoch in zklogin sig

Description
currently a zklogin sig is valid as long as max_epoch is larger than current epoch. this adds a protocol config that the max_epoch cannot be too large, the config sets the upper bound to 2 + current epoch.
based on new testing framework in simtest only.
Test Plan
simtest
If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[x] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[x] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes
Protocol version upgrades to 42. This adds a feature flag to set the upper bound of the max epoch for a zklogin signature.

i just did another rebase and can i please get a review?

for sdk i just updated a test to use the same test case as the zklogin test vector file
the default upper bound is set to 30 @Jordan-Mysten
there is an update to graphql tests, to also use zklogin test vector file @wlmyng
@lxfind @mystenmark for the sui core changes and simtests


Refactor editing ux

Bugs:

[x] form title and description are not rendered
[x] Choice and Multiple Choice fields:

[x] can't enter choices (currently pressing Enter propagates outside the modal)
[ ] can't validate input (currently the choices aren't in the schema in the format expected by the Python jsonschema validator)

[ ] make all the captcha widgets work (currently only honeypot does)
[ ] fix failing tests (mostly related to captchas)
[ ] fix lint errors

Cleanup:

[ ] remove old form block
[ ] rename packages

Features:

[x] custom (preset) fields
[x] thank you / confirmation settings
[x] field types

[x] render Multiple Choice as checkboxes
[x] Single Choice
[x] Time
[x] Numeric

[x] mailer features

[x] Administration Info
[x] Fixed Attachment
[x] Template

@davisagli as anticipated verbally, we would need the package to still have setup.py, at least until PEP 660 is fully implemented in zc.buidlout (see https://github.com/buildout/buildout/issues/652)


Allow relaxing of content type restrictions

I'm working in a context where the remote json_ld document is not always served with a content type header (or served with text/plain); this causes the ReqwestLoader to throw an error, because the content type is invalid.
It'd be nice to have an option (or maybe one exists, and I couldn't find it in the documentation) to ignore/assume/remap content types in some way.

This seems non standard. In this case I suggest making your own context loader, I prefer not to introduce any more complexity to this loader (especially since there's still some work to do on it).


[Travis] Prelaunch iOS simulator before tests

Fixes the issue with Exit status 65 for us, as far as I understand there is an issue with xcodebuild.
Using Fastlane's Scan solution works and another solution from Travis issue.

Woho 🎉


doc: remove unimplemented -t arg from split-pane

Summary of the Pull Request
Fixes #4878
PR Checklist

[x] Fixes #4878
[x] I work here
[x] Requires documentation to be updated

Has this issue been merged with master.  I just reimaged this machine and have the no keyboard input right away.

You mean, has this documentation change been merged to fix your keyboard input? It’s just a documentation change ...

@HSVAdam I think you're looking for #4448, I typo'd when I accidentally duped #7288 to this one.

@zadjii-msft Yes that is it thank you.  I will comment on there.

Whoops, sorry for the snark ;)


[Snyk] [DO NOT MERGE] Upgrade org.scala-lang:scala-library from 2.13.12 to 2.13.13

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.scala-lang:scala-library from 2.13.12 to 2.13.13.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2024-02-21.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

handled in a different commit


remove unneeded metrics from scaling dashboards

Fixes: https://github.com/knative-sandbox/monitoring/issues/3

/hold

/remove-hold

/lgtm

@dprotaso Have a look at this when you get back.
Let me know what you think about the datasource switcher at the top. It is a nice idea from the mixin dashboards bundled with prom-operator-stack project.
Other than that, every chart now shows metrics when a service is being invoked.


please supply a bogus APIkeys.json file for reference

I went to the weather site
it gave me a long string
I saved it as APIkeys.json in the directory but the noteboook complains:
`JSONDecodeError: Expecting value: line 1 column 1 (char 0)
`
please supply a bogus APIkeys.json file for reference
thank you

Done.


sysinfo.py --> sys_info.py

Links in text below are missing the underscore.
Also my service would start. So in the service file, the file name should also be renamed to sys_info.py

ok, fixed


i18n: correct ASS(S) fr translation of Hateful Visage

Fixes #5217.
cc @Akurosia who added this in #4990

As the "Hateful Visage" is the skill and not the bnpc in this case, i think original translation is correct (as i think the bnpc is in a fully different instance)

As the "Hateful Visage" is the skill and not the bnpc in this case, i think original translation is correct (as i think the bnpc is in a fully different instance)

Looking at the log provided in the issue, in this case it is the bnpc and not the skill name. The replaceSync section is for bnpc names / messagesand replaceText should be for skills / timeline texts.

thanks for clarification, i see the issue now, will look to avoid it next time :)


[Refactoring]: Seperation into chapters

I seperated each segment into a function and also added a gameover function.
This will avoid too much repitition.
I won't take too much work away on this.
Have fun learning python.
This pull request is addressing #5
fixes #5

restyled is pretty annoying

restyled is pretty annoying

I'll remove it, if you want. Was just trying to use stuff for free which I can get with the GitHub Student plan. What did it change exactly?

Thanks for your contribution!

Have fun learning python.

thanks

I'll remove it, if you want. Was just trying to use stuff for free which I can get with the GitHub Student plan. What did it change exactly?

It enforces multiple formatters, which wouldn't compatible to each other.
A simple linter would be probably better, some commonly used ones are pylint and flake.
If you want i could setup a workflow file for that, just run it on your device and try out which fits your needs.


Q: Core logging and Application Insights

Core logging is meant to be used by Azure Service teams - or that is how I understand it. But it also appears to be a logging library akin to Winston in some ways.
Application Insights is more about collecting logging and metrics into an Azure data store (conceptual data store). I've used Application Insights and like it.
A few questions:
Would a customer ever use both, such as core logging feeding into application insights?
While core logging is meant to be used by Service teams for their client SDK libraries, is there a reason a customer couldn't/shouldn't pick up the core logging library and use it?

I'm assuming this is a question about @azure/logger? The main motivation for the package is we wanted a consistent logging story for our packages that gave the developer control and mimicked popular NodeJS logging behavior (i.e. the debug package.)
I would expect most Node applications to use debug or similar directly. The only reason we couldn't depend upon debug ourselves is that it doesn't support IE11, which is an unfortunate requirement for storage. That said, there's no reason why someone couldn't use @azure/logger for their own logging, though it would be rather awkward that all of their logs would be under the azure namespace.
I don't think we wanted to force customers to adopt AppInsights by depending strongly on it, though there is no reason that you can't funnel all output from @azure/logger into AppInsights.
Perhaps @bterlson can correct anything I am mistaken about, as he was the original designer of the package.

@xirzec When  you use the term 'developer', is that generally an Azure SDK service team building a client library or is that any one inside or outside MSFT? Who is the intended audience?

Sorry I should have said consumer which is our term for developers who depend on SDK packages.
In general though, we don't expect consumers to depend directly on any of the core packages.

Ok, got it.

@xirzec: The monkey patching of debug that AI does is very problematic and isn't compatible with community modules, namely pino-debug. The original PR to merge the IE10 compatibility for that voiced concerns that this would happen. I have to include some third party dependencies follow-redirect in various places to prevent AI from throwing errors from the monkey patches. If at all possible removing or making the shim aware/compatible with other shims would be advisable.
Working with Azure modules has made debugging, logging and error handling a real challenge that I haven't faced on any other Node.js projects in the past.

@xirzec: The monkey patching of debug that AI does is very problematic and isn't compatible with community modules, namely pino-debug. The original PR to merge the IE10 compatibility for that voiced concerns that this would happen. I have to include some third party dependencies follow-redirect in various places to prevent AI from throwing errors from the monkey patches. If at all possible removing or making the shim aware/compatible with other shims would be advisable.

I'm not sure what you are referring to by "the monkey patching of debug" though it appears you're talking about something that AppInsights is doing?
Perhaps you want to file an issue in their repository? https://github.com/Microsoft/ApplicationInsights-node.js/

Working with Azure modules has made debugging, logging and error handling a real challenge that I haven't faced on any other Node.js projects in the past. As a consumer, it was very unclear what was for internal development/usage versus what I was supposed to use. What errors/comments/mechanisms for Microsoft's internal use or ours. This has been getting better with more recent development but was very rough on earlier Service Bus versions.

I'd love to send feedback to the appropriate teams if you can file an issue that describes where you think we can do a better job.
For one thing, I think we could do a better job documenting how @azure/logger works. That's the only logging mechanism that I think we support in SDK packages, but perhaps there are some one-off solutions that I'm not aware of.
As far as I know, none of the packages in this repository send any error telemetry to Microsoft, so all of what is there is for the benefit of the developer using the package. Services do have logging on the server-side that support teams can access, but there's nothing the SDK does for this other than setting a descriptive user agent and providing unique client request ids.

The follow-redirects bug is fixed in the latest version (and the debug dependency was removed) we were able to remove two hacks/workarounds just in time for handoff to the client! 🎉
It would be really nice is @azure/logger accepted a structured logging mechanism that follows the logs4j interface. The current interface is bespoke.
@xirzec @ramya-rao-a:
https://github.com/microsoft/ApplicationInsights-node.js/issues/731

It's important to be aware of the ecosystem around debug particularly: https://github.com/pinojs/pino-debug
I can share the hoops that we're jumping through on our end if it'll help give you an idea of what a customer who uses structured logging needs.
Even if the eventual destination is Azure Monitor/AI that doesn't mean it's not going to go out on stdout and be processed using standard K8s mechanisms.

I can share the hoops that we're jumping through on our end if it'll help give you an idea of what a customer who uses structured logging needs.

We would love to hear more on this @jmealo
Would you mind logging a new issue for this? Or does #13817 cover what you are thinking of?

@ramya-rao-a: I think some additional work might be required before a customer can realistically use structured logging (#13817 may not be useful on its own). I made a feature request to track that work separately: https://github.com/Azure/azure-sdk-for-js/issues/13824


Add state transition v6

WASM bytecode from https://github.com/FuelLabs/fuel-core/releases/download/v0.32.0/fuel-core-0.32.0-aarch64-apple-darwin.tar.gz


Integrate support for batching server-side GraphQL requests

👋 Hi! I've recently been looking in how we can best support third-party integrations in Hydrogen. While Hydrogen is typically focused on serving components from our own first-party storefront API, most headless merchants still end up needing to integrate with third-party services. I've been looking into how we can be as opinionated as possible when it comes to this integration so that we can offer much better performance & ergonomics than manually fetching an external API on the client and massaging all the data yourself.
We've been documenting some thoughts about how we can best achieve that over here, but ultimately we think we can add the most value to fetching third-party data with three things: caching, batching, and mapping. Why these three strategies?

Caching should significantly increase performance when dealing with third-party data by colocating it alongside the Hydrogen runtime and would be a nice value-add for running Hydrogen on Oxygen.
Batching all GraphQL requests to a given service would also reduce the number of waterfalling network requests needed to render a given page.
Mapping foreign keys in a third-party datastore to the results returned from the SF API can be really tedious and requires a lot of glue code we can remove if we set have some default assumptions about how data is stored for given third-parties.

This idea in the form of a code example illustrates what the ergonomics of all server fetches in Hydrogen could look like if you squinted:
  const query = gql`
    query product($handle: String!) {
      product(handle: $handle) {
        id
      }
    }
  `;
  // These three shop queries are batched across hook calls (or across components within a Suspense boundary) into a single GraphQL request
  const {data: data1} = useBatchedGraphQLQuery(query, { handle });
  // Duplicate query detected while batching, no need to perform additional work & hashes to the same cache key
  const {data: data2} = useBatchedGraphQLQuery(query, { handle });
  // Cache-aware batching crafts the smallest request necessary, incorporates individual cache hits and makes use of H2 caching strategy
  const {data: data3} = useBatchedGraphQLQuery(query, { handle: 'foo' }, {cache: { maxAge: 10 }});

  const selectionSet = gql`{
    title
    upc
  }; `
  // Takes an existing Shopify product record and request data mapped to it via foreign key in external CMS
  const {data: foo1} = useBatchedRecordsQuery(data.product, selectionSet, new SanityService(...));
  // Batches many records with the same selection set within the same query,
  // alongside other batched queries to the same service, while caching some records differentially
  const {data: foo2} = useBatchedRecordsQuery(
    {id: 'gid://shopify/Product/673085082834431'},
    selectionSet,
    new SanityService(...),
    { cache: { maxAge: 1} },
  );

There's even a "working" prototype with comments for something similar if you want do just dive right in! But in trying to implement this, a few complications arose, and they mostly center around Hydrogen's use of the react-query library for the useQuery hook.

We're currently using react-query (and previously useServerFetch) to wrap & schedule promises for execution so that we can render React components with the data they need on the server. Rendering React components asynchronously isn't supported, so the need of these sorts of hooks for fetching data on the server before rendering definitely seems reasonable.
Some of the reasons we originally adopted react-query was that it provided a more robust implementation for server-side requests that work with Suspense, that it works on the client, and that it comes with a built-in cache. However, some of the now-known drawbacks of adopting it as a library are that it doesn't support async fetches, and that the headers and other information about the response aren't being exposed.
One more drawback that the map+cache+batch prototype uncovered is that useQuery absolutely won't allow for batching GraphQL requests, or delaying any async operation across hook invocations for that matter. react-query includes its own scheduler to resolve promises as eagerly as possible and offers no configurability for deferring execution across hooks. If proper batching support were to be considered a priority, some of the options we have would be to either try to introduce batching support upstream in a library that wasn't designed for it, maintain our fork of react-query with batching support, or return to writing our own implementation à la useServerFetch.
Although things sound dire, being in control of our own custom hook for server fetches (again) could be beneficial for us:

react-query has it's own separate layer of caching that could stand to be consolidated with the rest of our caching framework for simplicity & debuggability.
In a RSC-world, support for client-side queries isn't something that we should necessarily strive to maintain.
The library adds significant complexity and overhead for what effectively amount to a fetch call (at least when it comes to how we're using its features in Hydrogen)
No proof-of-concept for this yet, but we should be able to automatically batch all GraphQL requests originating from anyt/all components within distinct Suspense boundaries.

I think it could be interesting to entertain the idea of building our own server-side data-fetching hook. The problem has been solved before: react-frontload is a tiny library that could server as inspiration for building one of these pseudo-synchronous hooks. Looking for feedback as to whether folks think about something like this!

All this being said, as we try to converge with RSC, it's unclear whether building a hook would be necessary for server fetches in the future, or if just a general data-fetching library will suffice.
Although data-fetching in an RSC world doesn't seem to have been finalized, all examples point to the ability to make use of asynchronous libraries for data-fetching in server components (eg. db.notes.get(props.id) in the official RFC, and a new React server renderer that supports Suspense and waiting on asynchronous data on the server without double-rendering).

I'm relatively new to the world of React so I may be overlooking a couple things. Looking for some feedback on the general appetite for replacing useReactQuery, and also hoping this issue sparks some discussion about our server-side data-fetching patterns, both for now and in the future with RSC.

Update to interested parties: we shipped preloading support in https://github.com/Shopify/hydrogen/pull/700 using preload: true and preload: '*' 🎉
Additional work could be done to analyze and combine GraphQL queries in a way that doesn't create an even slower or more complex resulting query.
For now, we should see how this works for our use case.


Java version in Dockerfile

Line #7 in Dockerfile. Java should be changed from
openjdk11

to
openjdk17

https://github.com/nvuillam/npm-groovy-lint/pull/317


Use struct as context key

Based on https://github.com/garrettladley/fiberpaginate/issues/10

I've synced and pushed all changes via enchancement branch, hence I'll close this PR


Update handling of registry errors

Update to #3109
Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Codecov Report

Merging #3173 into master will increase coverage by 4.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3173      +/-   ##
==========================================
+ Coverage   45.24%   49.26%   +4.02%
==========================================
  Files         111      100      -11
  Lines       11978     9426    -2552
==========================================
- Hits         5419     4644     -775
+ Misses       5725     3957    -1768
+ Partials      834      825       -9

Flag
Coverage Δ

#linux
49.26% <100%> (-0.02%)
:arrow_down:

#windows
?

Impacted Files
Coverage Δ

remotes/docker/fetcher.go
61.53% <100%> (-4.12%)
:arrow_down:

remotes/docker/auth.go
63.82% <0%> (-3.97%)
:arrow_down:

remotes/docker/status.go
21.42% <0%> (-3.58%)
:arrow_down:

platforms/cpuinfo.go
3.77% <0%> (-0.85%)
:arrow_down:

log/context.go
36.84% <0%> (-0.66%)
:arrow_down:

namespaces/context.go
55% <0%> (-0.56%)
:arrow_down:

errdefs/grpc.go
74.6% <0%> (-0.4%)
:arrow_down:

remotes/docker/pusher.go
0% <0%> (ø)
:arrow_up:

content/local/locks.go
100% <0%> (ø)
:arrow_up:

... and 62 more

Continue to review full report at Codecov.

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

LGTM
However I think the Wrapf approach is probably better. Please test that and open a PR to do that if you find it works. When you output (.Error()) with wrap it will also add the error messages of the wrapped error at the end just like done here, however it also allows the caller to get the typed error through Cause.

Just catching up on this, will test with Wrapf next week when I’m back in the office. Thanks for the tidy up on the original @crosbymichael


[BUG] - Button Url is not displayed in the LinkInput input field

The value is written in the attributes and properly rendered in the frontend.
"@eightshift/frontend-libs-tailwind": "^1.2.0",
"@eightshift/ui-components": "^1.4.6",

Fixed in Eightshift UI components 1.4.7


Implement Analyze Text

Proposed changes
Addresses #335, implements AnalyzeText, AnalyzeTextCallback and tests following the same structure as the equivalent methods for URL.
Types of changes
What types of changes does your code introduce to the community .NET SDK?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update or tests (if none of the other choices apply)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have lint'ed all of my code using repo standards
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added necessary documentation (if appropriate)

Further comments

AnalyzeClientTests have not been linted as it currently is not using repo standards (could include that in this PR or open seperate issue?)

Summary by CodeRabbit

New Features

Introduced two new methods for text analysis: AnalyzeText for synchronous processing and AnalyzeTextCallBack for asynchronous processing with callback support.
Added a new TextSource class to encapsulate text input for analysis.

Tests

Enhanced unit test coverage for the AnalyzeClient class, validating the behavior of new methods under various conditions.

Documentation

Updated interface documentation for new methods to clarify parameters and return types.

Hi @kaller01
This is amazing! and you even added UnitTests for the new code! Awesome!
I will take a look at this today. Since there are other things in the pipeline to be released, I will see about getting this in.


Problems while using ignore : ERROR in Cannot read property 'glob' of undefined

plugins: [
    new CopyWebpackPlugin([
      {ignore: [
                '/app',
              ]},
      { from: path.resolve(__dirname, 'src'), to: path.resolve(__dirname, 'build') }
    ])
  ]

I reverted the changes made yesterday. 2.1.5 may resolve this

Sorry, 2.1.5 won't fix your issue, because the config is incorrect. Try this:
plugins: [
    new CopyWebpackPlugin([{
        from: path.resolve(__dirname, 'src'),
        to: path.resolve(__dirname, 'build')
    }],
    {
        ignore: [
            '/app',
        ]
    })
]

I'm sorry this is the same config as far as I can see.

I imagine you intend to ignore everything in that directory, so you probably want it to be /app/**/* and you probably want to ignore files that start with a . too.
plugins: [
    new CopyWebpackPlugin([{
        from: path.resolve(__dirname, 'src'),
        to: path.resolve(__dirname, 'build')
    }],
    {
        ignore: [{
            glob: '/app/**/*',
            dot: true
        }]
    })
]

Thanks this is now working for me :)


feat: support external service

Signed-off-by: Ling Samuel<EMAIL_ADDRESS>Type of change:

[x] New feature provided

What this PR does / why we need it:
First part of #927
Proposal is here: https://github.com/apache/apisix-ingress-controller/issues/927#issuecomment-1206116262
This feature is considered unstable because how to implement some features (schemes and ports) is still under discussion.
Doc PR is incoming.

This is a new implementation of #726 and #927  , PTAL.
/cc @elvis-cai  @purekeeper @BrandonArp @NMichas

Codecov Report

Merging #1306 (603c828) into master (0b999ec) will increase coverage by 0.43%.
The diff coverage is 34.89%.

@@            Coverage Diff             @@
##           master    #1306      +/-   ##
==========================================
+ Coverage   39.80%   40.23%   +0.43%
==========================================
  Files          75       75
  Lines        6962     7118     +156
==========================================
+ Hits         2771     2864      +93
- Misses       3892     3929      +37
- Partials      299      325      +26

Impacted Files
Coverage Δ

pkg/providers/apisix/translation/apisix_plugin.go
57.54% <ø> (ø)

pkg/providers/apisix/translation/translator.go
0.00% <ø> (ø)

pkg/providers/utils/string.go
0.00% <0.00%> (ø)

...kg/providers/apisix/translation/apisix_upstream.go
48.83% <35.29%> (-51.17%)
:arrow_down:

pkg/providers/apisix/translation/apisix_route.go
25.02% <35.83%> (+5.88%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

All tests passed, just a linter error.

could you please resolve conflicts? thanks


[CIVP-11787] Add joblib backend

Add a new civis.parallel module which contains tools to register a custom backend for the joblib library. This will let users leverage the Civis Platform infrastructure for parallel computing, and makes it easy to distribute parallel scikit-learn computations over the Civis infrastructure.
Most of this code was developed in a separate repo and has been in Civis internal use. This PR copies over that code, adapts it to work in the civis-python repo, and makes small modifications for Python 2 compatibility.

@mheilman , the second commit is the one that needs more attention here.

Also I just realized that the remote worker depends on the API client which would have the remote worker function in it. Thus if I am not mistaken, we don't need to upload the joblib worker function. I don't think backwards compatibility with containers that have older API clients is a good enough reason the keep this, but (shrug).

For the record, could you add a note to the PR description that most of this code was reviewed previously in PRs to an internal repo?
Also, it looks like this adds three functions to the API (make_backend_factory, make_backend_template_factory, infer_backend_factory), along with some miscellaneous things like exception classes, etc.  This seems good. Am I missing anything?
What's the plan for updating the documentation and changelog?

@mheilman , I think I've addressed all of your comments. I added a note to the changelog about this (thanks for reminding me). I plan to write documentation in another PR early next week.
@beckermr , I added another commit which skips uploading the worker function and instead pip installs civis if it's not present already. I also put on the exec calls. I'd planned to leave those for a follow-on PR, to keep the size of this diff down, but I suppose those changes are small. And it shouldn't break anything.
Writing new versions of the file transfer functions which can retry on AWS network errors seems like a bigger job, and not in scope for this PR.

So three new issues here:

add cancel_timeout parameter for containers
add retry on file i/o in remote worker func
change hidden to archive_on_success (or just add the later?)

LGTM from me (not that you all need it!)

One more task is to work on the deps

Where did we put these 4 issues?

@beckermr , issues filed here (#108 , #109 )and on Jira.

Cool. We should make the archive on success issue too. I am happy to work on that one.


Provided default value in ZSH_CUSTOM

@jimeh any objections on my PR?

Anyone?

@red-avtovo I’m really sorry, this one has repeatedly slipped through the cracks for me. Looks good, so I’m happy to merge :)


[feature]: add channel conditional validation to AddAsset*Order RPC endpoints

Currently, the AddAssetBuyOrder and AddAssetSellOrder RPC endpoints initiates the RFQ communication process with a specified target peer. This issue proposes a modification to the endpoint to include a pre-condition check. Specifically, the RFQ process should only commence if there is an existing tap channel for the specified asset between the local node and the target peer, and that channel has sufficient funds. If these conditions are not met, the endpoints should return a helpful error.

RFQ rework is a prerequisite