[Bug]: cluster stuck "Waiting for the instances to become active" after restarting node

Is there an existing issue already for this bug?

[X] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[X] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[X] I have read the troubleshooting guide and I think this is a new bug.

Version
1.23.2
What version of Kubernetes are you using?
1.30 (unsupported)
What is your Kubernetes environment?
Cloud: Amazon EKS
How did you install the operator?
Helm
What happened?
A node became "Unknown".
I restarted it manually.
I expected all the clusters to become healthy
It actually seems to be stuck, unable to reach a consistent recovery state.
Extra Details

kubectl cnpg status -v

Cluster Summary
Name:                postgres-advanced
Namespace:           advanced
System ID:<PHONE_NUMBER>694346259
PostgreSQL Image:    ghcr.io/cloudnative-pg/postgis:16
Primary instance:    postgres-advanced-1
Primary start time:  2024-07-11 18:56:32 +0000 UTC (uptime 2h10m42s)
Status:              Waiting for the instances to become active Some instances are not yet active. Please wait.
Instances:           3
Ready instances:     2
Current Write LSN:   0/B4000000 (Timeline: 6 - WAL File:<PHONE_NUMBER>000000000000B3)
PostgreSQL Configuration
archive_command = '/controller/manager wal-archive --log-destination /controller/log/postgres.json %p'
archive_mode = 'on'
archive_timeout = '5min'
cluster_name = 'postgres-advanced'
dynamic_shared_memory_type = 'posix'
full_page_writes = 'on'
hot_standby = 'true'
listen_addresses = '*'
log_destination = 'csvlog'
log_directory = '/controller/log'
log_filename = 'postgres'
log_rotation_age = '0'
log_rotation_size = '0'
log_truncate_on_rotation = 'false'
logging_collector = 'on'
max_parallel_workers = '32'
max_replication_slots = '32'
max_worker_processes = '32'
port = '5432'
restart_after_crash = 'false'
shared_memory_type = 'mmap'
shared_preload_libraries = ''
ssl = 'on'
ssl_ca_file = '/controller/certificates/client-ca.crt'
ssl_cert_file = '/controller/certificates/server.crt'
ssl_key_file = '/controller/certificates/server.key'
ssl_max_protocol_version = 'TLSv1.3'
ssl_min_protocol_version = 'TLSv1.3'
unix_socket_directories = '/controller/run'
wal_keep_size = '512MB'
wal_level = 'logical'
wal_log_hints = 'on'
wal_receiver_timeout = '5s'
wal_sender_timeout = '5s'
cnpg.config_sha256 = 'e9bd29d8d34e5c4c89b51b9e1a9df37b5ea1081dbf2516291eeb922354e53d80'
PostgreSQL HBA Rules

FIXED RULES

Grant local access ('local' user map)
local all all peer map=local
Require client certificate authentication for the streaming_replica user
hostssl postgres streaming_replica all cert
hostssl replication streaming_replica all cert
hostssl all cnpg_pooler_pgbouncer all cert

USER-DEFINED RULES

DEFAULT RULES

host all all all scram-sha-256
Certificates Status
Certificate Name               Expiration Date                Days Left Until Expiration

postgres-advanced-ca           2024-09-28 23:44:39 +0000 UTC  79.11
postgres-advanced-replication  2024-09-28 23:44:39 +0000 UTC  79.11
postgres-advanced-server       2024-09-28 23:44:39 +0000 UTC  79.11
Continuous Backup status
First Point of Recoverability:  2024-07-01T17:18:44Z
Working WAL archiving:          OK
WALs waiting to be archived:    0
Last Archived WAL:<PHONE_NUMBER>000000000000B3   @   2024-07-11T19:36:34.102217Z
Last Failed WAL:                00000006.history           @   2024-07-11T18:56:32.996025Z
Physical backups
No running physical backups found
Streaming Replication status
Replication Slots Enabled
Name                 Sent LSN    Write LSN   Flush LSN   Replay LSN  Write Lag  Flush Lag  Replay Lag  State      Sync State  Sync Priority  Replication Slot  Slot Restart LSN  Slot WAL Status  Slot Safe WAL Size

postgres-advanced-2  0/B4000000  0/B4000000  0/B4000000  0/B4000000  00:00:00   00:00:00   00:00:00    streaming  async       0              active            0/B4000000        reserved         NULL
postgres-advanced-3  0/B4000000  0/B4000000  0/B4000000  0/B4000000  00:00:00   00:00:00   00:00:00    streaming  async       0              active            0/B4000000        reserved         NULL
Unmanaged Replication Slot Status
No unmanaged replication slots found
Managed roles status
No roles managed
Tablespaces status
No managed tablespaces
Pod Disruption Budgets status
Name                       Role     Expected Pods  Current Healthy  Minimum Desired Healthy  Disruptions Allowed

postgres-advanced          replica  2              1                1                        0
postgres-advanced-primary  primary  1              1                1                        0
Instances status
Name                 Database Size  Current LSN  Replication role  Status             QoS         Manager Version  Node

postgres-advanced-1  51 MB          0/B4000000   Primary           OK                 BestEffort  1.23.2           ip-10-0-39-143.us-west-2.compute.internal
postgres-advanced-2  50 MB          0/B4000000   Standby (async)   OK                 BestEffort  1.23.2           ip-10-0-18-108.us-west-2.compute.internal
postgres-advanced-3  -              -            -                 pod not available  BestEffort  -                ip-10-0-5-110.us-west-2.compute.internal

Helm chart version
0.21.5
Extra notes:
I have 5 instances of my app. Each application has two clusters (each with 3 replicas). One of the two clusters is not backed up.
Out of the 10 clusters:
1 of 5 of the clusters with backups are fully recovered (all similar to the errors reported below)
5 of 5 of the clusters without backups are fully recovered.
Cluster resource
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  annotations:
    argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"postgresql.cnpg.io/v1","kind":"Cluster","metadata":{"annotations":{"argocd.argoproj.io/sync-options":"SkipDryRunOnMissingResource=true"},"labels":{"app.kubernetes.io/instance":"utilityai"},"name":"postgres-advanced","namespace":"advanced"},"spec":{"backup":{"barmanObjectStore":{"destinationPath":"s3://advanced-db-backup/v2","s3Credentials":{"inheritFromIAMRole":true},"wal":{"compression":"gzip","maxParallel":8}}},"bootstrap":{"recovery":{"database":"advanced-app","source":"clusterBackup"}},"externalClusters":[{"barmanObjectStore":{"destinationPath":"s3://advanced-db-backup/v1/","s3Credentials":{"inheritFromIAMRole":true},"serverName":"postgres-advanced","wal":{"compression":"gzip","maxParallel":8}},"name":"clusterBackup"}],"imageName":"ghcr.io/cloudnative-pg/postgis:16","instances":3,"serviceAccountTemplate":{"metadata":{"annotations":{"eks.amazonaws.com/role-arn":"arn:aws:iam::xxxxxxxx:role/eks-postgres-advanced"}}},"storage":{"size":"10Gi"}}}
  creationTimestamp: "2024-06-30T23:49:39Z"
  generation: 5
  labels:
    app.kubernetes.io/instance: utilityai
  name: postgres-advanced
  namespace: advanced
  resourceVersion: "63797733"
  uid: 6e546644-19bf-471c-b80b-18997e12b3b5
spec:
  affinity:
    podAntiAffinityType: preferred
  backup:
    barmanObjectStore:
      destinationPath: s3://advanced-db-backup/v2
      s3Credentials:
        inheritFromIAMRole: true
      wal:
        compression: gzip
        maxParallel: 8
    target: prefer-standby
  bootstrap:
    recovery:
      database: advanced-app
      owner: advanced-app
      source: clusterBackup
  enablePDB: true
  enableSuperuserAccess: false
  externalClusters:
  - barmanObjectStore:
      destinationPath: s3://advanced-db-backup/v1/
      s3Credentials:
        inheritFromIAMRole: true
      serverName: postgres-advanced
      wal:
        compression: gzip
        maxParallel: 8
    name: clusterBackup
  failoverDelay: 0
  imageName: ghcr.io/cloudnative-pg/postgis:16
  instances: 3
  logLevel: info
  maxSyncReplicas: 0
  minSyncReplicas: 0
  monitoring:
    customQueriesConfigMap:
    - key: queries
      name: cnpg-default-monitoring
    disableDefaultQueries: false
    enablePodMonitor: false
  postgresGID: 26
  postgresUID: 26
  postgresql:
    parameters:
      archive_mode: "on"
      archive_timeout: 5min
      dynamic_shared_memory_type: posix
      log_destination: csvlog
      log_directory: /controller/log
      log_filename: postgres
      log_rotation_age: "0"
      log_rotation_size: "0"
      log_truncate_on_rotation: "false"
      logging_collector: "on"
      max_parallel_workers: "32"
      max_replication_slots: "32"
      max_worker_processes: "32"
      shared_memory_type: mmap
      shared_preload_libraries: ""
      ssl_max_protocol_version: TLSv1.3
      ssl_min_protocol_version: TLSv1.3
      wal_keep_size: 512MB
      wal_level: logical
      wal_log_hints: "on"
      wal_receiver_timeout: 5s
      wal_sender_timeout: 5s
    syncReplicaElectionConstraint:
      enabled: false
  primaryUpdateMethod: restart
  primaryUpdateStrategy: unsupervised
  replicationSlots:
    highAvailability:
      enabled: true
      slotPrefix: _cnpg_
    synchronizeReplicas:
      enabled: true
    updateInterval: 30
  resources: {}
  serviceAccountTemplate:
    metadata:
      annotations:
        eks.amazonaws.com/role-arn: arn:aws:iam::xxxxxx:role/eks-postgres-advanced
  smartShutdownTimeout: 180
  startDelay: 3600
  stopDelay: 1800
  storage:
    resizeInUseVolumes: true
    size: 10Gi
  switchoverDelay: 3600
status:
  availableArchitectures:
  - goArch: amd64
    hash: e43340cd2ccfa2a8120cf5de6035fe4b18d799bb2feabf99a91434dd9ba92e4c
  - goArch: arm64
    hash: f453a8cb50a418ff9cac24c818b9e155b80487b4152444e48d187161ecdfc0eb
  certificates:
    clientCASecret: postgres-advanced-ca
    expirations:
      postgres-advanced-ca: 2024-09-28 23:44:39 +0000 UTC
      postgres-advanced-replication: 2024-09-28 23:44:39 +0000 UTC
      postgres-advanced-server: 2024-09-28 23:44:39 +0000 UTC
    replicationTLSSecret: postgres-advanced-replication
    serverAltDNSNames:
    - postgres-advanced-rw
    - postgres-advanced-rw.advanced
    - postgres-advanced-rw.advanced.svc
    - postgres-advanced-r
    - postgres-advanced-r.advanced
    - postgres-advanced-r.advanced.svc
    - postgres-advanced-ro
    - postgres-advanced-ro.advanced
    - postgres-advanced-ro.advanced.svc
    serverCASecret: postgres-advanced-ca
    serverTLSSecret: postgres-advanced-server
  cloudNativePGCommitHash: 4bef8412
  cloudNativePGOperatorHash: e43340cd2ccfa2a8120cf5de6035fe4b18d799bb2feabf99a91434dd9ba92e4c
  conditions:
  - lastTransitionTime: "2024-07-11T18:55:06Z"
    message: Cluster Is Not Ready
    reason: ClusterIsNotReady
    status: "False"
    type: Ready
  - lastTransitionTime: "2024-07-11T18:56:38Z"
    message: Continuous archiving is working
    reason: ContinuousArchivingSuccess
    status: "True"
    type: ContinuousArchiving
  - lastTransitionTime: "2024-07-11T00:00:13Z"
    message: Backup was successful
    reason: LastBackupSucceeded
    status: "True"
    type: LastBackupSucceeded
  configMapResourceVersion:
    metrics:
      cnpg-default-monitoring: "59241826"
  currentPrimary: postgres-advanced-1
  currentPrimaryTimestamp: "2024-07-11T18:56:31.977458Z"
  firstRecoverabilityPoint: "2024-07-01T17:18:44Z"
  firstRecoverabilityPointByMethod:
    barmanObjectStore: "2024-07-01T17:18:44Z"
  healthyPVC:
  - postgres-advanced-1
  - postgres-advanced-2
  - postgres-advanced-3
  image: ghcr.io/cloudnative-pg/postgis:16
  instanceNames:
  - postgres-advanced-1
  - postgres-advanced-2
  - postgres-advanced-3
  instances: 3
  instancesReportedState:
    postgres-advanced-1:
      isPrimary: true
      timeLineID: 6
    postgres-advanced-2:
      isPrimary: false
      timeLineID: 6
    postgres-advanced-3:
      isPrimary: false
  instancesStatus:
    healthy:
    - postgres-advanced-1
    - postgres-advanced-2
    replicating:
    - postgres-advanced-3
  lastFailedBackup: "2024-07-01T17:11:30Z"
  lastSuccessfulBackup: "2024-07-11T00:00:10Z"
  lastSuccessfulBackupByMethod:
    barmanObjectStore: "2024-07-11T00:00:10Z"
  latestGeneratedNode: 3
  managedRolesStatus: {}
  phase: Waiting for the instances to become active
  phaseReason: Some instances are not yet active. Please wait.
  poolerIntegrations:
    pgBouncerIntegration: {}
  pvcCount: 3
  readService: postgres-advanced-r
  readyInstances: 2
  secretsResourceVersion:
    applicationSecretVersion: "59244180"
    clientCaSecretVersion: "59244177"
    replicationSecretVersion: "59244179"
    serverCaSecretVersion: "59244177"
    serverSecretVersion: "59244178"
  switchReplicaClusterStatus: {}
  targetPrimary: postgres-advanced-1
  targetPrimaryTimestamp: "2024-07-11T18:55:06.821159Z"
  timelineID: 6
  topology:
    instances:
      postgres-advanced-1: {}
      postgres-advanced-2: {}
      postgres-advanced-3: {}
    nodesUsed: 3
    successfullyExtracted: true
  writeService: postgres-advanced-rw

Relevant log output
(this repeats on and on.)
{
  "level": "info",
  "ts": "2024-07-11T20:52:12Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "postgres-advanced-3",
  "record": {
    "log_time": "2024-07-11 20:52:12.348 UTC",
    "user_name": "postgres",
    "database_name": "postgres",
    "process_id": "283",
    "connection_from": "[local]",
    "session_id": "669045fc.11b",
    "session_line_num": "1",
    "session_start_time": "2024-07-11 20:52:12 UTC",
    "transaction_id": "0",
    "error_severity": "FATAL",
    "sql_state_code": "57P03",
    "message": "the database system is not yet accepting connections",
    "detail": "Consistent recovery state has not been yet reached.",
    "backend_type": "client backend",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2024-07-11T20:52:13Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "postgres-advanced-3",
  "record": {
    "log_time": "2024-07-11 20:52:13.406 UTC",
    "user_name": "postgres",
    "database_name": "postgres",
    "process_id": "285",
    "connection_from": "[local]",
    "session_id": "669045fd.11d",
    "session_line_num": "1",
    "session_start_time": "2024-07-11 20:52:13 UTC",
    "transaction_id": "0",
    "error_severity": "FATAL",
    "sql_state_code": "57P03",
    "message": "the database system is not yet accepting connections",
    "detail": "Consistent recovery state has not been yet reached.",
    "backend_type": "client backend",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2024-07-11T20:52:13Z",
  "logger": "postgres",
  "msg": "record",
  "logging_pod": "postgres-advanced-3",
  "record": {
    "log_time": "2024-07-11 20:52:13.408 UTC",
    "user_name": "postgres",
    "database_name": "postgres",
    "process_id": "286",
    "connection_from": "[local]",
    "session_id": "669045fd.11e",
    "session_line_num": "1",
    "session_start_time": "2024-07-11 20:52:13 UTC",
    "transaction_id": "0",
    "error_severity": "FATAL",
    "sql_state_code": "57P03",
    "message": "the database system is not yet accepting connections",
    "detail": "Consistent recovery state has not been yet reached.",
    "backend_type": "client backend",
    "query_id": "0"
  }
}
{
  "level": "info",
  "ts": "2024-07-11T20:52:13Z",
  "msg": "DB not available, will retry",
  "controller": "cluster",
  "controllerGroup": "postgresql.cnpg.io",
  "controllerKind": "Cluster",
  "Cluster": {
    "name": "postgres-advanced",
    "namespace": "advanced"
  },
  "namespace": "advanced",
  "name": "postgres-advanced",
  "reconcileID": "2b9f82bb-cb3b-4e11-b4fa-e059b4b98f8f",
  "logging_pod": "postgres-advanced-3",
  "err": "failed to connect to `user=postgres database=postgres`: /controller/run/.s.PGSQL.5432 (/controller/run): server error: FATAL: the database system is not yet accepting connections (SQLSTATE 57P03)"
}

Code of Conduct

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

since posting, one of the three has become healthy. Will close unless the other three clusters continue to remain unhealthy.

still unhealthy after 19+ hours. I've tried restarting pod, no luck.

the conclusion is to be patient. everything is working after 4 days(!).

I got the same problem with a very small testing db <1MB.
It got stuck this way. is there any log indicating progress?

My database was also very small (~10MB), I do not recall any logs indicating progress until I came back after the weekend and all was well.

I just removed the PVC + pod instead of waiting :(


Why the changes in the interfaces ?

Hi 👋
I don't understand the change to generic names for the mus.Unmarshaller/mus.Marshaller/mus.Sizes functions.
Could you please explain the motivation?
Regards.

Hi!
I just opened an issue #11 that describes a possible future of mus-go. I wonder what you think about it? Also there is a post on reddit.
In general it was done to write code like this:
func MarshalSliceProtobuf[T any](sl []T, m mus.Marshaller[T], bs []byte) (n int) {
	for i := 0; i < len(sl); i++ {
		n += m.Marshal(sl[i], bs[n:]) // instead of m.MarshalMUS(...)
	}
	return
}

I think Marshal/Unmarshal are too generic terms to be employed by any library in a language like Go that heavily relies on interfaces. encoding/json uses MarshalJSON, gopkg.in/yaml.v3 uses MarshalYAML ... etc.

Sorry for the delay in response.
We can still write:
  func MarshalFooMUS(foo Foo, bs []byte) (n int) {
    ...
  }

And use it as, for example:
  ord.MarshalSlice[Foo](sl, nil, mus.MarshallerFn[Foo](MarshalFooMUS), bs)

I don't understand the change to generic names for the mus.Unmarshaller/mus.Marshaller/mus.Sizes functions.

I mean, mus-go is already a more general thing than a serializer of one format. And can be used to implement different formats, not only MUS.

I don't use functions, all my MUS usage is structured around methods that implements the former interfaces. Having to use Marshal/Unmarshal for only for MUS is not ideal, but, having to have to reserve Size for MUS is not something I want.
// MessageMUS is a MUS marshaller for Message.
//
//nolint:all
type MessageMUS struct{}

var messageMUS = MessageMUS{}
var _ mus.Marshaller[Message] = (*MessageMUS)(nil)
var _ mus.Unmarshaller[Message] = (*MessageMUS)(nil)
var _ mus.Sizer[Message] = (*MessageMUS)(nil)

// MarshalMUS marshals struct mus encoded bytes.
func (MessageMUS) MarshalMUS(m Message, bs []byte) (n int) {
	...
	return n
}

// UnmarshalMUS unmarshals mus encoded bytes.
func (MessageMUS) UnmarshalMUS(bs []byte) (m2 Message, n int, err error) {
	...
	return m2, n, nil
}

// SizeMUS computes the length of MUS encoded bytes for the struct.
func (MessageMUS) SizeMUS(m Message) (n int) {
	...
	return n
}

Then I have my generic Mus Marshaller function for NATS.
// Marshaller is the interface that wraps the MusMarshaller and MusSizer methods.
type Marshaller[T any] interface {
	mus.Marshaller[T]
	mus.Sizer[T]
}

// MarshalMUS encodes a message to a NATS message.
func MarshalMUS[T Marshaller[T]](inputMsg, outputMsg *nats.Msg, v *T) error {
	bs := make([]byte, (*v).SizeMUS(*v))
	(*v).MarshalMUS(*v, bs)
        ...
	return nil
}

Sorry for the inconvenience. As a temporary solution, I can suggest to define the Marshaller interface as:
type Marshaller[T any] interface {
	MarshalMUS(t T, bs []byte) (n int)
	SizeMUS(t T) (size int)
}

, think this should work.

As a temporary solution, I can suggest to define the Marshaller interface as:

Actually, this is not a very good idea. It is better to use something like namespaces:
// First of all, let's define a general Serializer struct. It is simply an
// union of the Marshal, Unmarshal, and Size functions.
type Serializer[T any] struct {
	Marshal   mus.MarshallerFn[T]
	Unmarshal mus.UnmarshallerFn[T]
	Size      mus.SizerFn[T]
}

// And a serializer for the Foo struct.
var FooSerializerMUS = Serializer[Foo]{
	Marshal: func(foo Foo, bs []byte) (n int) {
		return varint.MarshalInt(foo.Int, bs)
	},
	Unmarshal: func(bs []byte) (foo Foo, n int, err error) {
		foo.Int, n, err = varint.UnmarshalInt(bs)
		return
	},
	Size: func(foo Foo) (size int) {
		return varint.SizeInt(foo.Int)
	},
}

// Then the SerializableMUS interface, for structures that support serialization
// in the MUS format.
type SerializableMUS[T any] interface {
	MUS() Serializer[T]
}

// And finally, Foo struct with the MUS format support.
type Foo struct {
	Int int
}

func (f Foo) MUS() Serializer[Foo] {
	return FooSerializerMUS
}

// Now generic MarshalMUS function could look like this.
func MarshalMUS[T SerializableMUS[T]](t T) (bs []byte){
	var (
		s = t.MUS()
		bs = make([]byte, s.Size(t))
	)
	s.Marshal(t, bs)
	return
}

// And could be used like: MarshalMUS(foo)

@sylr

Just added the 'Generic MarshalMUS Function' section to README.md.

Closing, due to lack of conversation.


Developer files preview - pleasant, but slow. (is plain-text pre-preview possible?)

Microsoft PowerToys version
0.55.1
Running as admin

[X] Yes

Area(s) with issue?
Developer file preview
Steps to reproduce
Previewing almost any supported code file that is more than 1-2KiB in size takes a second or two.
SQL file that is 216KiB does not seem to render at all.
✔ Expected Behavior
I used to have plain-text preview configured for common code files, that was relatively instantaneous. Highlighted preview is highly pleasant, but not worth it if it takes many seconds to render. Is it possible to show plain-text pre-preview while Loading...
❌ Actual Behavior

Other Software
No response

Is it possible to show plain-text pre-preview while Loading

This is the idea I was searching. Thank you so much for this great idea!

this will cause a visual pop is the issue

Any news on this issue?
I really like the formatting, yet the startup time is somewhat unfortunate when browsing through a bunch of files in search for something specific.

any plans to improve performance for text & markdown preview in PT ? (I'm also experiencing the slow loading as mentioned by the other users)

this will cause a visual pop is the issue

@crutkas Do you you mean "we will first have the instant "text" preview, then a visual "pop" when the "full preview" is available"?
I'd say that's still better than a loading window that takes long, then get the result 2 seconds later (... and: isn't there a minor "pop" when the "loading" changes to the preview?.
... but note that the "highlighted text" preview (which is used for .log files, for example) takes the same amount of time for rendering - so for an "instant" preview one really would need the plain text one inbuilt to Windows (that doesn't come with any highlighting or showing line numbers).

Are you still experiencing this issue? /needinfo

oh yes, even a 210 line .sh file takes about 1.2 seconds to show. I have 'Source Code files (Monaco)' preview turned off. Instead, I use an old tool PreviewConfig to register such files as plain text. That way I get instant preview.


Fix IE/Edge specific error

Makes sure element (for example ) supports the .blur() method before calling it.

There was another instance of a call to blur which I also fixed.
Thanks!


XMLSerializer, atob & btoa globals for Phantomjs globals

Missing.

Do you fancy making a pull request? it would be here: https://github.com/jshint/jshint/blob/master/src/vars.js#L454
I can't find any evidence they are supported, but its not like there is a list of things defined in the phantomjs environment.
globals doesn't add these at the moment - https://github.com/sindresorhus/globals/blob/master/globals.json#L539


How to make it connect through proxy on Windows?

**[Attempt 8]
Downloading https://huggingface.co/cocktailpeanut/sup/resolve/main/SUPIR-v0F.ckpt?download=true to D:\Users\chenyixuan\pinokio\api\supir.git\app\supir_checkpoints...
[Download Failed] Error: connect ETIMEDOUT <IP_ADDRESS>:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1300:16)!**
How to solve it

pinokio.bat The content is as follows
@echo off
set HTTPS_PROXY=http://<IP_ADDRESS>:7890
C:\Users\wuwenfei\AppData\Local\Programs\Pinokio\Pinokio.exe

How to make it connect through proxy on mac?

How to make it connect through proxy on mac?

pinokio.sh The content is as follows
#!/bin/bash
proxy_address="<IP_ADDRESS>"
proxy_port="4780"
app_name="pinokio"
networksetup -setwebproxy Wi-Fi $proxy_address $proxy_port
networksetup -setsecurewebproxy Wi-Fi $proxy_address $proxy_port
HTTPS_PROXY=$proxy_address:$proxy_port open -a "$app_name"

pinokio.bat The content is as follows
@echo off set HTTPS_PROXY=http://<IP_ADDRESS>:7890 C:\Users\xxxxx\AppData\Local\Programs\Pinokio\Pinokio.exe

@OceanNg529 , I have created the batch file named pinokio.bat just like you've mentioned but I get the following when I run the it :
Cannot GET /pinokio/--allow-access-from-files
Also the ETIMEDOUT Error is still there.


Fix typo in complex.pow that affected handling of (0 + 0j) base

There was a typo in the helper function calCPow of complex.__pow__ that caused code like the following to produce the wrong output.
x = 0 + 0j
y = 1 + 0j
print(x ** y)

Output was (1+0j) when it should have been 0j

@freakboy3742 I believe that instead of explicitly writing a test case for this, the best way to implement tests would be to add 0+0j and 1+0j to the complex list in SAMPLE_DATA in tests/utils.py. This way we make use of the existing test code generation.
However I ran into precision issues which I wrote about in #499.
Do you want me to add those changes to this PR? I could add test_power_complex to the list of not_implemented methods in order to have it generate an expected failure message and have the Travis check pass.

@soandrew It seems like the r.real.value = 0.0; fix is in #751 which was just merged, but is there still an issue with the missing 0.0 to a negative or complex power ZeroDivisionError? If yes, we'd be happy to merge a fix (with tests) for that!

@cflee Sorry for the delayed reply. Indeed there still is an issue when 0+0j is raised to a negative int which causes an error message of complex division by zero to be thrown instead of the proper 0.0 to a negative or complex power.
I made a fix and added explicit tests for the (0+0j) ** (1+0j) and (0+0j) ** -1) cases which were causing these specific issues.

Hi there! It looks like this PR might be dead, so we're closing it for now. Feel free to re-open it if you'd like to continue, or think about directing your efforts to https://github.com/beeware/briefcase or https://github.com/beeware/toga. Both of these have more active development right now. 😄


Only Exports Directly to root directory not can't do folders.

i can only export on my D drive root
file imported from VRM, applied all the fixes that tool has
other bugs
only exports ones and need to reset blender
image not embeded on export
current version 2.8
plugin version 0.13.2
Sendagaya_Shino.zip

The exporting process is done by Blender, not by Cats. Maybe try starting Blender as admin to allow export to other drives.
Regarding the other issue, try importing the textures into Unity first before importing the fbx.


Add another step where Debezium is replaced with RedisCDC

Good idea - I've got to figure out how! If you have experience here then feel free to step in!


Upgrade dependencies for 0.62.0

Note: I wasn't sure how CLA works for https://github.com/line/centraldogma/pull/865, so I just also included armeria upgrades in this PR.

Armeria 1.24.3 → 1.25.1
Guava 32.0.1-jre → 32.1.2-jre
Hibernate Validator 8.0.0.Final → 8.0.1.Final
Micrometer 1.11.1 → 1.11.3
Spring Boot 3 3.1.0 → 3.1.2

I wasn't sure how CLA works for https://github.com/line/centraldogma/pull/865

We may add the github-actions bot as a whitelist. Let's ask Seoyeon later when she comes back from vacation.


ETA is unreliable because of deduplication

Output of restic version
restic 0.12.0 compiled with go1.14.7 on linux/amd64
How did you run restic exactly?
restic backup /src
What backend/server/service did you use to store the repository?
SFTP
Expected behavior
when i run the backup-process repeatedly, most chunks are already at the target and don't need to be transferred again.
the ETA should reflect the time needed until completion.
it can do better, by taking the average transfer speed of the last time-frame, instead of the overall transfer speed. the time-frame-parameter can be used to increase accuracy.
in case it is already known after scanning, which/how many chunks actually need to be transferred, this information could also be used to increase accuracy even more.
Actual behavior
when i run the backup-process repeatedly, most chunks are already at the target and don't need to be transferred again.
the ETA is calculated rather simple and doesn't take this advantage into account.
because the transfer seems to start incredibly fast (GB/s) the ETA starts quite low and is constantly and slowly increasing, without any benefit.
Steps to reproduce the behavior
repeat a backup of little-changing source multiple times and watch ETA. compare it to actual wall time.
Do you have any idea what may have caused this?
simple algorithm (see above)
Do you have an idea how to solve the issue?
more complex algorithm (see above)
Did restic help you today? Did it make you happy in any way?
i still trust restic ;)

There has already been some discussion regarding this problem in the forum: https://forum.restic.net/t/eta-is-wrong-when-resuming-an-upload/3396/11

I went ahead and implemented a more complex ETA estimate. It is in principle a sliding window, but as I hinted at in my last message, I found the naive approaches don't work very well. E.g windows based on fixed-time or even fixed-bytes-transferred seem to hit pathological cases in my testing. The key observation I found was that restic's backup progress is bursty, at least with a rate limit set against Backblace B2.  I handle this in #3563 by insisting that the sliding window holds a wide enough time window and enough bytes transferred and enough distinct measurements (as defined by discrete reported progress at least one second apart). With this in place I observed relatively good ETA values computed across the variety of problem cases I uncovered (mostly occurring when most of a backup is duplicate data, and with a restrictive rate limit in place).


[IMPROVEMENT] share manager should respect kubernetesClusterAutoscalerEnabled also

Is your improvement request related to a feature? Please describe
Well, I waited a long time for this #2203 feature. Thanks for that.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
After i updated to the latest version i get a new error message from cluster autoscaler:
node cannot be removed: longhorn-system/share-manager-pvc-61760353-2a01-.... is not replicated
Describe the solution you'd like
It should be possible to drain a node by cluster autoscaler automaticly
The controller for share manager should add the annotation to the pod also.
Describe alternatives you've considered
Only manual pod deletion of the consumed nfs share.
Additional context
Ive run longhorn manager on dedicated nodes including attached volumes from the cloud provider. Some nodes are auto created by the autoscaler. On each node there a pod gets scheduled which consumes an nfs share the share manager is attached.

For now, the annotation of the share-manager is not set, but it is feasible. But, the potential issue is the service interruption because the share-manager contains the nfs server.

cc @c3y1huang @innobead

Yeah i get the point but if I configure the cluster autoscaler explicit i should be aware of potential service interruption. :)


CreateProcess error=206

It seems the command line can become too long (in my case):
Execution failed for task ':jdepsReport'.
> org.zeroturnaround.exec.ProcessInitException: Could not execute [jdeps, --multi-release, base, --class-path, C:\Users\USER\.gradle\caches\modules-2\files-2.1\org.projectlombok\lombok\1.18.22\9c08ea24c6eb714e2d6170e8122c069a0ba9aacf\lombok-1.18.22.jar;<MANY MORE JARS>]. Error=206, Filename or extension too long

Unfortunately jdeps does not support @ files for defining args but it does support using '*' in the classpath. I'll see what I can do.


Add prefix to client.jobs() call

With no arguments, the client.jobs() call causes helios-master to
respond with a list all known jobs (unpaginated). If the master has
enough jobs, such a request is likely to timeout or be dropped due to
response size, which bubbles up as a failure in the application using
helios-testing.
This change adds the temporary jobs' prefix to the call so that only
jobs matching the prefix are returned. This should reduce (but does not
eliminate) the impact of this issue.
@mattnworb @davidxia

Tests passing now. Wish they were easier to run locally.

We could also consider removing removeOldJobs() altogether

s/removeOldJobs()/helios-testing/ ;)


"Foo" not found

If there are zero results in a search, we should have string that says "Foo not found" as opposed to "Foo found in;"

@carlkesselman @robes I changed the wording from "'Foo' not found" to "'Foo' found in {{numberOfSearchResults}} attribute(s):" so that the text doesn't appear too jumpy between zero and > 0 search results cases. (And also to provide a count of search results.)

Yay or nay?

that works for me

excuse me. i meant to say "yay".

Yea 2....,
Carl
Sent from my iPad

Dr. Carl Kesselman
Professor, Epstein Department of Industrial and Systems Engineering
Fellow, Information Sciences Institute
Viterbi School of Engineering
University of Southern California
4676 Admiralty Way, Suite 1001, Marina del Rey, CA  90292-6695
Phone:  +1<PHONE_NUMBER>
Email:  carl<EMAIL_ADDRESS>Web: http://www.isi.edu/~carl
On Oct 7, 2015, at 8:02 PM, robes <notifications<EMAIL_ADDRESS>wrote:
excuse me. i meant to say "yay".

Reply to this email directly or view it on GitHubhttps://github.com/informatics-isi-edu/chaise/issues/115#issuecomment-146404075.

@robes :wink:
Ok cool the yays have it. Moved to Done.


Update README.md - Add TadGAN paper link

Add TadGAN paper link on the top

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

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

Merged.

Merged.


https://wiki.developer.mozilla.org/en-US/docs/Tools/Debugger/How_to/Set_a_breakpoint$history?page=1

Request type

[ ] Correction or update

Details
As a complete novice & outsider, I'm struggling with how to make a minor comment.  Mea culpa if I've got it all wrong.
My conditional breakpoint (in the FF debugger) wasn't working as I expected.  I learned why at the subject page (how_to/set_a_breakpoint): The  condition is not "==", which I had guessed because hey, this is javascript.  From the lone example, it is instead "=".  So, equality not being what I guessed, what is && (or maybe &)?
Seems like a very brief summary of comparison operators would be useful.  Simply "C-like, and not javascript-like"  would be adequate (if that's correct).

This is a funny one — the problem has been caused because the comparson operator shown in the screenshot is wrong — it should be ===, which is JS strict equality. = is assignment. I've updated the screenshot so that it shows the correct operator.

Actually, at this moment both = and === seem to work (as the comparison op
in a conditional break).  As I recall, when I posted my question the "="
worked (and, I think, not ===)..  Screenshot below ("editing" a debug
condition) was taken maybe 5 minutes ago.  4 minutes ago, === also worked
(but I took no screenshot).  In neither case is anything assigned, which is
reasonable since this is a debug condition.
[image: image.png]
On Tue, Sep 29, 2020 at 2:33 AM Chris Mills<EMAIL_ADDRESS>wrote:

This is a funny one — the problem has been caused because the comparison
operator shown in the screenshot is wrong — it should be ===, which is JS
strict equality. = is assignment. I've updated the screenshot so that it
shows the correct operator.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mdn/sprints/issues/3552#issuecomment-700586606, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFSKD42EMYXWSCFUSOV7FTSIGSYLANCNFSM4PL6AOFA
.

Yeah, but IIRC assignments equate to true, so it can look like it is working, but you may get inaccurate results.

? These aren't statements in the code; they're instructions to the
debugger.
Just my uninformed opinion.  But the condition and log commands are
accessible only via the debugger pop-up menu.  It wb extraordinarily odd if
it affected the executing code.
Sent from the awful Google gmail client (terrible editor) over T-MOBILE's
sketchy network
On Tue, Sep 29, 2020, 10:45 PM Chris Mills<EMAIL_ADDRESS>wrote:

Yeah, but IIRC assignments equate to true, so it can look like it is
working, but you may get inaccurate results.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mdn/sprints/issues/3552#issuecomment-701169389, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFSKD7I6F7ZEPO54XNWJD3SILAXFANCNFSM4PL6AOFA
.


DRILL-5668: Fix C++ connector crash on error

Fix C++ connector crash when receiving error messages exceeding
a given size.

Thanks for the patch!

@parthchandra @sudheeshkatkam look good to you?

+1. LGTM.


Updated output for refactored example that uses UUIDs for the PK.

This PR updates the output of the psycopg2 example to match the changes to use UUIDs for the primary keys in the example source repo.
Part of DOC-4903.

This change is


over reasonable disk space usage

I'm trying a basic app with Django and the Nanobox is taking 3.8Gb of disk space.
When your disk is a 128gb ssd drive and this nanobox is one single basic project among others, that's consequent.
I see that nanobox is strongly based on Docker.
Maybe could you consider using Alpine images?

nanobox creates an isolated environment for every application. What is happening is you are installing a very small image for virtual box (rough 38m) then we pull down minimal docker images. Then we install the language and all dependencies that your app needs in an isolated environment. I am guessing the vast majorty of your 3.8Gb of usage is coming from the dependencies.

That said, we're always looking to optimize; It's an ongoing effort. Would you mind providing where you're seeing the 3.8Gb of usage?
Thanks

Well, the same project is 2.9Mb and all its dependencies are 50Mb when installed on my system.
The project is https://github.com/CommonsDev/sso.
Here attached is a screenshot of that nanobox. I may have done something wrong to reach that amount of disk space…

I don't think you've done anything wrong. Nanobox is an ambitious project and we haven't yet been able to focus on optimizing for disk efficiency. You're totally fine.
However, since you're the first to actually report the issue, I'm hoping you'll be willing to investigate where we can do better ;)

I try to delete an reinstall; I'll have a deeper look to check why it's requiring such a large amount.
I had similar issues with Docker until I used only Alpine based images.

Also, the "dependencies" that @lyondhill is referring to are the environment dependencies: binaries, libraries, build tools, etc. The actual application and app dependencies are likely very small as you've mentioned.
As a point of reference, the Xcode build tools for mac install at ~3gb as a minimum. The build image (nanobox/build) will be at least 1GB unpacked simply due to the build tools required for compiling and linking.

@notxarb When you get a moment, can you provide some instructions for isolating disk usage within the VM?

I've deleted the folder machine/nanobox and rerun nanobox start and nanobox run in that same folder.
The disk usage of disk.vmdk has now been reduced to 10Mb, which is very fine.
I'm not sure then why I had these 3.8Gb for that image.
Notice I had asked to build with Docker on my first launch of nanobox before I was told it was not ready yet. I then moved to the suggested VM.
Maybe is it linked?

Hey @vinyll, could you check the current usage now?

I just ran out of space on the disk the nanobox vm is using and I happened to check its disk usage:

I did have 5 apps, but it seems like old images may be part of the issue as all those apps are down:
docker@nanobox:~$ docker images
REPOSITORY           TAG                 IMAGE ID            CREATED             SIZE
nanobox/build        latest              54e899273e41        6 days ago          587.4 MB
nanobox/build        bugfix_nosupdate    b63a08c1c881        2 weeks ago         587.4 MB
nanobox/mysql        latest              f9401b450a36        2 weeks ago         737.5 MB
nanobox/code         latest              3f92f5e4a03e        2 weeks ago         351.3 MB
nanobox/redis        latest              471f67205b3b        2 weeks ago         416 MB
nanobox/unfs         latest              3c0e9e80e675        2 weeks ago         362.7 MB
nanobox/logvac       latest              049dd48d9e0f        2 weeks ago         332 MB
nanobox/unfs         <none>              a328aedc80b1        3 weeks ago         362.5 MB
nanobox/redis        <none>              68b12cbc0a2e        3 weeks ago         415.8 MB
nanobox/mysql        <none>              a1ca198136cf        3 weeks ago         737.5 MB
nanobox/portal       latest              0493e06e34c9        3 weeks ago         387.6 MB
nanobox/mist         latest              11487fac4910        3 weeks ago         331.9 MB
nanobox/hoarder      latest              f6648c7ffcb8        3 weeks ago         344.3 MB
nanobox/code         <none>              df88fc0b61e9        3 weeks ago         351.3 MB
nanobox/build        <none>              3f1edc7f5ecc        6 weeks ago         723.7 MB
nanobox/postgresql   <none>              f7489edbac52        9 weeks ago         690.3 MB
nanobox/bridge       latest              b07bebe96c90        10 weeks ago        456.4 MB

i should be releasing 2.0.3 today.


curl: 8.6.0 -> 8.7.1

Description of changes
Fixes CVE-2024-2466, CVE-2024-2398, CVE-2024-2379 and CVE-2024-2004.
Changes:
https://curl.se/changes.html#8_7_1

Things done

Built on platform(s)

[x] x86_64-linux up to curlFull and curl.passthru.tests
[x] aarch64-linux up to curlFull and curl.passthru.tests
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Needs more build testing, as we regularly run into issues with darwin.

Will look into darwin.

x86_64-darwin passthru tests fail to eval. This is rebased onto master.
❯ x86_64-darwin-build -A curl.tests
error:
       … while calling the 'derivationStrict' builtin
         at /builtin/derivation.nix:1:205:
       … while evaluating derivation 'curl-static-x86_64-apple-darwin-8.7.1'
         whose name attribute is located at /home/hexa/git/nixos/staging/pkgs/stdenv/generic/make-derivation.nix:331:7

       … while evaluating attribute 'CXX' of derivation 'curl-static-x86_64-apple-darwin-8.7.1'
         at /home/hexa/git/nixos/staging/pkgs/tools/networking/curl/default.nix:151:3:
          150|
          151|   CXX = "${stdenv.cc.targetPrefix}c++";
             |   ^
          152|   CXXCPP = "${stdenv.cc.targetPrefix}c++ -E";

       (stack trace truncated; use '--show-trace' to show the full trace)

       error: don't yet have a `targetPackages.darwin.LibsystemCross for x86_64-apple-darwin`

nix-repl> curl.tests
{
  coeurl = «derivation /nix/store/bqppr9zyls0ngmcjwcr2k32ygrpwvmab-coeurl-0.3.0.drv»;
  curlpp = «derivation /nix/store/fkqy9pbwwz73byyn72cbpvlv950k289f-curlpp-0.8.1.drv»;
  haskell-curl = «derivation /nix/store/c3sjbf6nvnnl7n569q425zdi2az27rc4-curl-1.3.8.drv»;
  nginx-http3 = ^[[A{ ... };
  ocaml-curly = «derivation /nix/store/v8zvag71n6b3jpxxwacdl6zzfi6b228k-ocaml5.1.1-curly-0.3.0.drv»;
  php-curl = «derivation /nix/store/vrdzs5rwvjw4480l3sfgwnc6rlhf40d3-php-curl-8.2.17.drv»;
  pkg-config = «derivation /nix/store/2vdn264km8dwad8x8pc9gg7aqlkmnkqj-check-meta-pkg-config-modules-for-curl-8.7.1.drv»;
  pycurl = «derivation /nix/store/f3v66mlrj0qjz2aq5p2s89dllpzb3d53-python3.11-pycurl-7.45.3.drv»;
  static = «error: don't yet have a `targetPackages.darwin.LibsystemCross for x86_64-apple-darwin`»;
  withCheck = «derivation /nix/store/ky3l3a7iilqkdb3y8ghvqbda2wyg6j1q-curl-8.7.1.drv»;
}

Added in 817d20170dc6b7b2c195a6c3271d88789f206b0b by @alyssais. PTAL.

Successfully built all relevant curl.tests (apart from haskell one, ghc too big for me) and curlFull.tests.withCheck on macos 12 x86_64.
Also built equivalent for, nixos x86_64, along with pkgsStatic, pkgsMusl, pkgsCross.aarch64-multiplatform, pkgsi686Linux variants of curl.tests.withCheck and pkgsMusl, pkgsCross.aarch64-multiplatform, pkgsi686Linux variants of curlFull.tests.withCheck.

curlMinimal, curl and curlFull including passthru.tests on aarch64-darwin and x86_64-darwin are looking good.
Couldn't create tcp server socket: IO::Socket::INET: Operation not permitted
make[1]: *** [Makefile:839: quiet-test] Error 1
make[1]: Leaving directory '/private/tmp/nix-build-curl-8.7.1.drv-3/curl-8.7.1/tests'
make: *** [Makefile:1721: test] Error 2

diff --git a/pkgs/tools/networking/curl/default.nix b/pkgs/tools/networking/curl/default.nix
index fbc430b7afc9..82100c95a4e6 100644
--- a/pkgs/tools/networking/curl/default.nix
+++ b/pkgs/tools/networking/curl/default.nix
@@ -196,6 +196,7 @@ stdenv.mkDerivation (finalAttrs: {
       # nginx-http3 = useThisCurl nixosTests.nginx-http3;
       nginx-http3 = nixosTests.nginx-http3;
       pkg-config = testers.testMetaPkgConfig finalAttrs.finalPackage;
+    } // lib.optionalAttrs (!stdenv.isDarwin && !stdenv.isx86_64) {
       static = pkgsStatic.curl;
     } // lib.optionalAttrs (!stdenv.isDarwin) {
       fetchpatch = tests.fetchpatch.simple.override { fetchpatch = (fetchpatch.override { fetchurl = useThisCurl fetchurl; }) // { version = 1; }; };

Done, thanks!

Ughhh, their fix for static linking libpsl doesn't actually work, so we have to keep our hack for it.

Should we add a case to meta.broken for x86_64-darwin static?

Since curl 8.7.0 switched to rustls-ffi 0.12.0 I think this will break the optional withRustls feature unless that derivation is bumped from 0.10. That's a little tricky because Apache HTTPD also depends on the rustls-ffi derivation, but that project hasn't updated for 0.12.
@LeSuisse Do you have any thoughts? Is the best approach to split the rustls-ffi package into two versions? As an upstream maintainer of rustls-ffi I'm interested in trying to pitch in with the downstream packaging but would appreciate input before I start making PRs. Also happy to chat elsewhere if this is too off-topic for the curl update.

Yeah I need to take a look. It's likely I'm going to propose to have the 2 versions in nixpkgs.

It's likely I'm going to propose to have the 2 versions in nixpkgs.

Thanks! :+1: Feel free to CC me. We recently landed pkg-config/.so support using cargo-c to build and I suspect that might be interesting to think about too.

If you want to ensure we don't break withRustls I suggest you add a target to passthru.tests that builds covers this.
Come to think, it doesn't look like we have any passthru targets for alternative tls implementations.

If you want to ensure we don't break withRustls I suggest you add a target to passthru.tests that builds covers this.

There is a passthru test in the rustls-ffi derivation for curl & apache HTTPD w/ the feature activated. Is the suggestion to add one in reverse in the curl derivation? (I'm not especially familiar with the passthru test mechanism).

Ok given there is also https://github.com/curl/curl/issues/13248 I will deal with the rustls-ffi upgrade once this PR reaches master. It will be less annoying to work on it and given the curl + Rustls backend is not accessible via a direct pkgs attribute it should not bother too many people.

Not major, but a bug in 8.7 breaks newsboat

Not major, but a https://github.com/curl/curl/pull/13219 https://github.com/newsboat/newsboat/issues/2728

Looks easy enough to cherry-pick a fix patch: https://github.com/NixOS/nixpkgs/pull/306633 @jpotier Can you test if that fixes newsboat for you?


fix: Go - avoid panic on wrong *keyset.Handle

For each of the available primitives in Go - ensure type checking of the primitive to avoid panics in the API.
closes #336
Signed-off-by: Baha Shaaban<EMAIL_ADDRESS>

@chuckx , @kste , @happyCoder92, @juergw
I noticed that 6 of your commits were merged today (not as PRs)
Can you please review this PR? I rebased on top of your commits.

Sorry for the delay.
We might change that code in the near future, so feel free to file an issue. Anyhow, I will comment on it.

Can you change the construction of the wrappers such that they check the correctness on construction time? Thanks!

Do you mean remove the checks from the primitive functions? ie Encrypt(), Decrypt(), Sign(), etc.
I will do this as well.

Do you mean remove the checks from the primitive functions? ie Encrypt(), Decrypt(), Sign(), etc.
I will do this as well.

That's a style question. In principle, if these checks trigger there's a bug in our code. In other languages that cannot happen, so I don't have a definite answer. I guess I personally would leave them in, as crashing is also bad when we have a bug in our code, but I'd return an error if any of the errors triggers (instead of swallowing).

I updated my previous comment :)

I guess I personally would leave them in, as crashing is also bad when we have a bug in our code, but I'd return an error if any of the errors triggers (instead of swallowing).

I think what you mean is return an error instead of continue  in the below condition?
if !ok {
 	continue
 }

My thinking is if the primitive is not valid, keep looping through the list until we get a valid one. Technically this will never happen because of the primitive check in the constructor especially with the update I will be pushing soon to verify all primitive entries.
But if you think that returning an error here is better than continue, I can do that too.

@tholenst I've updated the PR by first rebasing it and replaced every continue added with a return fmt.Errorf() statement instead.
I believe the PR is ready.

Ty, working on it.

Not sure why PRs don't get merged directly in Github. But this PR has been merged internally by Google.
So I'm closing this PR.
Thanks @tholenst and @sophieschmieg

Because we have two repositories, the internal one and the external one. We need to decide which repository mirrors the other one, and in Tink github mirrors the Google internal one.
It seems in this case I didn't follow the process carefully though, and now the association is not proper, and points to me instead of you. If you like, I can see how to fix that (e.g by rolling it back and re-merging this PR, or maybe it's possible to edit the history in git). Let me know what you think.

Because we have two repositories, the internal one and the external one. We need to decide which repository mirrors the other one, and in Tink the github repo mirrors the Google internal one.
It seems in this case I didn't follow the process carefully though, and now the association is not proper, and points to me instead of you. If you like, I can see how to fix that (e.g by rolling it back and re-merging this PR, or maybe it's possible to edit the history in git). Let me know what you think.

That's ok @tholenst, what matters is it's merged. There's no need to put extra effort in reverting the commits.
In the future though, it would be nice to be able to port GitHub merged commits to Google's internal repo for sake of the open source spirit of the project. It should be at least automated to save time and effort.


Pdf outline

Hello @hughstephens! Did you intentionally open this PR? It has conflicts, is failing the pipeline, and doesn't seem to have any new commits compared to https://github.com/Hopding/pdf-lib/pull/486, so I'm going to close this for now. Let me know if you're planning to work on this!

Sorry my fault @hopding! I did end up cobbling together a solution based on #127. +1 to getting something "easier", because it was certainly a little mindbending going through the PDF spec!


Invalid YAML being generated for certain inputs

Describe the bug
When certain input is encountered, the YAML output is invalid. When trying to parse it, an exception is thrown.
To Reproduce
Repro repository is here: https://github.com/jan-tee/yaml-bug-1
Includes test for the same case with js-yaml without issues.
Expected behaviour
YAML output is valid, can be parsed without exception.
Versions (please complete the following information):

Environment: Node v15.8.0, Windows
yaml: 1.10.0

YAML output looks like:
test:
  test:
    test:
      - test: "\r

          \\XXXXXX\\XXXXXXXXXXXXXXX\\XXXXXXXXXXX\\XXXXX\\XXXXX\\XXXX\\
          \X\\XXXXX\\XXXXX\\XXXXXXXXX\\XXXXXXXXX\\XXXXXXXXX\\XXX_XXXXXX_X.X_(XX\
          XXXXXXXX"

Exception when parsing the YAML back:
YAMLSyntaxError: Invalid escape sequence \X
    at QuoteDouble.get strValue [as strValue] (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\parse-cst.js:1327:25)
    at Object.resolveString [as resolve] (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1282:20)
    at resolveByTagName (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1384:25)
    at resolveTag (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1414:17)
    at resolveNodeValue (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1535:23)
    at resolveNode (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1583:15)
    at resolveBlockMapItems (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1777:38)
    at Object.resolveMap [as resolve] (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1612:79)
    at resolveByTagName (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1384:25)
    at resolveTag (C:\Users\jant.SENTINELONE\Repos\jan-tee\yaml-bug-1\node_modules\yaml\dist\resolveSeq-4a68b39b.js:1414:17) {
  source: QuoteDouble {
    error: null,
    range: Range { start: 38, end: 214 },
    valueRange: Range { start: 38, end: 214 },
    props: [],
    type: 'QUOTE_DOUBLE',
    value: null,
    resolved: Scalar {
      value: '\r\n' +
        '\\XXXXXX\\XXXXXXXXXXXXXXX\\XXXXXXXXXXX\\XXXXX\\XXXXX\\XXXX\\ \\X\\XXXXX\\XXXXX\\XXXXXXXXX\\XXXXXXXXX\\XXXXXXXXX\\XXX_XXXXXX_X.X_(XXXXXXXXXX',
      range: [ 38, 214 ],
      type: 'QUOTE_DOUBLE'
    }
  }
}

This looks like a duplicate of awslabs/cdk8s#494, which got fixed in<EMAIL_ADDRESS>It looks like installing that version in your repo also makes the test succeed.

Fixed in<EMAIL_ADDRESS>


updates securityContext section for containers to support OCP install

Co-authored-by<EMAIL_ADDRESS>

This PR fixes the below issues seen when the containers come up
Below is the issue with the init-directories container without the fix
ubuntu@ubuntu:~$ kubectl logs gitea-0 -n gitea -c init-directories
+ chown 1000:1000 /data
chown: /data: Operation not permitted

Below is the issue in the gitea-0 container without the fix
[fedora@mgmt ~]$ kubectl logs gitea-0 -n gitea

Defaulted container "gitea" out of: gitea, init-directories (init), init-app-ini (init), configure-gitea (init)

s6-svscan: fatal: unable to open .s6-svscan/lock: Permission denied

https://gitea.com/gitea/helm-chart/src/branch/main/values.yaml#L61

@efiacor @arora-sagar FYI I shall open an issue to track updating gitea image to 1.20 and use the rootless container by end of R4. I propose that we approve this PR for now and merged it.
cc: @gvbalaji

Closing the PR as the custom SCC has been adjusted from
runAsUser:
  type: MustRunAs
  uid: 1000

to
runAsUser:
 type: RunAsAny


[feature] Implement fadeIn and faceOut methods

Add methods for fading in and out of the volume levels when playing or stopping audio. For instance:
const sound = PIXI.sound.Sound.from('foo.mp3');
const instance = sound.fadeIn(500); // same as play()
instance.fadeOut(200); // fade out a single instance
sound.fadeOut(200); // fade out all instances

And global library commands:
PIXI.sound.add('foo', 'foo.mp3');
const instance = PIXI.sound.fadeIn('foo', 500);
instance.fadeOut(200);
PIXI.sound.fadeOut('foo', 200); // fade out all instances
PIXI.sound.fadeOut(); // fade out all sounds, all instances

Hi Matt,
Sorry just catching up on Pixi Sound, this is a great idea!
One thing we struggled with when using Howler was the lack of a reliable volume getter, I had to patch around it quite a lot.
With this, it's easy to then use any tweening engine, even something tiny like https://www.npmjs.com/package/tweenr
My point is I don't think it's worth spending a lot of time making fadeIn super efficient, but have good getter/setters :)
Obviously just my 2 cents

Hi @alvinsight, thanks for the feedback.
I see the point, but I still might add these convenience methods anyways. I think fading in and out is pretty basic functionality and in this case it's just a linear tween. The good thing is that the current webaudio playback has a pretty good progress events, so there wouldn't need to rely on an internal tweening structure or another ticker/requestAnimationFrame.
If it's low-cost, low-effort, I'll implement. Otherwise, I'll take your advice and allow devs to do their own tweening.

Hi Matt,
Great, that's exactly my point, I agree that it's a basic feature that one can expect at a basic level.
I just wanted to make sure it's low-effort and we don't reinvent the wheel with another Ticker, as you said :)

I don't think this is actually solved... there is no fadeOut method in SoundInstance.
I want to be able to stop a looping sound by fading it out rather than stopping it instantly. The original request seems to propose that, but the current implementation does not support it.

Faced with the same problem. I can't find fadeIn / fadeOut
@Lusito did you find the solution

I had implemented this for v1 but removed it it for v2 because I wanted to give more flexibility. So instead I implemented per soundinstance, per Sound and per context volume setting, as well as html5 audio fallback which complicated the fades. In the end, I didn’t want to include any tweening and felt like other people might have opinionated implementations of this functionality. I’d recommend greensock or some other tween library to manage fades.

Is there any documentation/reference that I could look at to implement this myself with pixi-sound.js v4? I just need a simple linear fade in/out

Here's a working example using GSAP:
https://codesandbox.io/s/pixijs-examples-sound-fade-out-qcos8n?file=/src/index.ts
The part you'll really care about is this:
const instance = buzzer.play();
gsap.to(instance, { volume: 0, duration: 1 });

There are other libraries out there for tweening that would basically do the same thing.


Feature candidates for version 0.10.x

I felt a need for a little discussion as there are markable changes requested which require increasing of MINOR version to 0.10. I am putting up a list of some issues/PRs that may be the candidates for upcoming version change.
Already released with v0.10.0

#1287 Upgrade to Lodash 4

Upcoming

[ ] #1278 Update to<EMAIL_ADDRESS>

[ ] #1284 Enable using table alias "Fix #96 by enabling table name aliasing"

[ ] #1265 Change the behavior of isNew "isNew doesn't work with custom idAttribute"

[ ] #900 Support isNew returning a Promise
I have also an idea how to make isNew thenable by taking benefit of valueOf method overriding. But the downside of this would be that isNew verification must be performed as isNew() == true/false. All the other usages will produce an invalid result.
So it may not be so good idea at all...

[ ] #1220 Improve virtuals
On this me and @rhys-vdw have a bit different opinions.

Your opinions? Any requests more?

The above mentioned ones look great! I would add pagination which is a crucial feature but doesn't seem to be working in the latest version.

@rhys-vdw made the v0.10.0 release already. Sadly only lodash upgrade is included. But the other updates are still in the pipe.

That's okay, we can do more releases!

The announcement should have been more cheerful :smile:
:tada: v0.10.0 released :tada:

The project leadership of Bookshelf recently changed. In an effort to advance the project we close all issues older than one year.
If you think this issue needs to be re-evaluated please post a comment on why this is still important and we will re-open it.
We also started an open discussion about the future of Bookshelf.js here https://github.com/bookshelf/bookshelf/issues/1600. Feel free to drop by and give us your opinion.
Let's make Bookshelf great again


Remove redundant escape sequences in repr method

The __repr__ method for many classes in the library was not implemented correctly, with redudant escape sequence for double quote (intended for strings). These should all be removed

A few __repr__ methods were implemented incorrectly. For arguments of type str, they should not be concatenated directly for the output of __repr__, but rather their own __repr__ methods should be called first.
>>> # An example
>>> name = 'fred'
>>> # Incorrect implementation
>>> 'name=' + name
>>> 'name=fred'
>>> # Correct implementation
>>> 'name' + repr(name)
>>> "name='fred'"

This allows the representation string to retain the nature of string arguments.

A few __repr__ methods were implemented incorrectly. For arguments of type str, they should not be concatenated directly for the output of __repr__, but rather their own __repr__ methods should be called first.
>>> # An example
>>> name = 'fred'
>>> # Incorrect implementation
>>> 'name=' + name
>>> 'name=fred'
>>> # Correct implementation
>>> 'name' + repr(name)
>>> "name='fred'"

This allows the representation string to retain the nature of string arguments.


Storybook doesn't fully work when ran within Docker

I see this:

Issue seems to be related to lazyCompilation option being enabled: https://zenn.dev/yutaosawa/scraps/7764e5f17173d1


nonstd::expected includes windows.h when exceptions are disabled

Including windows.h is a fairly disastrous thing to do in many project. We can probably avoid it by setting -Dnsel_CONFIG_NO_EXCEPTIONS_SEH=0.
See https://community.cesium.com/t/unable-to-package-ue5-0-3-project-with-cesium-v1-19-0/21162/19

Another user ran into this here:
https://community.cesium.com/t/packaging-fails-after-creating-a-c-file-inheriting-from-cesium3dtileset-in-cesium-for-unreal/35567


entity name in sidecar header in firefox does properly overflow: hidden

the sidecar header entity name should enter text-overflow: ellipsis mode when the sidecar header content is too wide. on firefox, due to a missing min-width: 0, this does not happen. as a result the vertical "entity type" text sometimes is not visible (as it is smooshed off viewport by the long entity name)

example of buggy output

example of expected output


webpack+babel+koa2 Error

I have an application with a server direcotry. index.js and server.js in this direcotry.
index.js
import('babel-register');
import('babel-polyfill');
import('./server.js');

as you can see  I replaced the require with import. and in the server.js
import Koa from 'koa';
const app = new Koa();
app.use(async (ctx, next) => {
  const start = new Date();
  await next();
  const ms = new Date() - start;
  console.log(`${ctx.method} ${ctx.url} - ${ms}ms`);
});
// response
app.use((ctx) => {
  ctx.body = 'Hello Koa in app-async.js';
});
app.listen(8080);
console.log("booting up...，port：8080");
module.exports = app;

and I have configured the webpack.config.js with this:
const path = require('path');

module.exports = {
  entry:path.resolve(__dirname,'server/index.js'),
  output:{
    path:path.resolve(__dirname,'server'),
    filename:"start.js"
  }
}

module.export = {
  module:{
    rules:[
      {test:/\.js$/,use:['babel-loader'],exclude:'/node_modules/'}
    ]
  }
}

and the .babelrc file has these contetts
{
  "presets": [
    ["env", {
      "targets": {
        "node": true
      }
    }]
  ]
}

ButI received this error:
ERROR in ./~/koa/lib/request.js
Module not found: Error: Can't resolve 'net' in '/Users/git/WorkSpace/vcg/test/World/node_modules/koa/lib'
 @ ./~/koa/lib/request.js 9:12-26
 @ ./~/koa/lib/application.js
 @ ./server/server.js
 @ ./server/index.js

ERROR in ./~/destroy/index.js
Module not found: Error: Can't resolve 'fs' in '/Users/git/WorkSpace/vcg/test/World/node_modules/destroy'
 @ ./~/destroy/index.js 14:17-30
 @ ./~/koa/lib/response.js
 @ ./~/koa/lib/application.js
 @ ./server/server.js
 @ ./server/index.js

So I think the koa2 not support webpack

Why would Koa reside in a frontend environment?

You can see my repo webpack-koa2-middleware.

@fl0w  koa not reside in frontend I just want write code in es6 and when push to production I want convert to es5. So I want to convert it with webpack. Now Every time I have to do this without webpack
babel server/index.js -o server/start.js

you probably have to set node = true somewhere, but i don't see the point of using webpack at all for koa

@jonathanong  thanks  I have changed to use babel for koa and use webpack for the fronted

@gaoguoxin great


Support siege and fix several bugs;

@Lkoinw  What I did based on your work in brief:

Created siege event and siege map event before entering battle, to make it compatible with perks and other potential mods that may access siege event or map event during siege battle.
Tried to move code in BattleStarter.BeforeMissionEnded to BattleStarter.MissionEnded. Didn't find the issue that "player is absorbed into the other clan". Maybe it's because that I created the siege event? Any opinion? @Lkoinw
Added "Custom Banner" and "Custom Tactic Level" option.
Made hero added to battle party back to original party or settlement and fix the bug you told me that made party count increase.
Fixed several crashes. Read the comments in code for details.

Damn this is impressive. You're on another level o_o
About the issue that "player is absorbed into the other clan" :
I still have it but I realized it's coming from conflict with another mod "Troop Sorting".
It's sorting troops on event OnTutorialContextChange (which is called at the beginning and end of battle) and as a side effect is setting the wrong clan to main character.
Mods seem to follow that order :

EBT.Start (main character change)
TroopSorting.OnTutorialContextChange (clan absorption)
EBT.OnRetreatMission/OnMissionResultReady (main character revert)
TroopSorting.OnTutorialContextChange (clan absorption reverted)
EBT.OnRemoveBehavior

Reverting main character in OnRemoveBehavior is too late in that case.


Swipe to Add to Collection

Hey all. New here. Gonna try to jump in with helping on things but I’ve never coded in swift. See if I can catchup fast.
Would be better if swiping right added a bug/fish/item to your collection. I also find a check might be better than a star for the non swipe method? It took me a bit to figure out star wasn’t favouriting meaning something else. Thoughts?

So it's a heart for villager, a checkmark for critters and a star for items. But we could *also* support swipe. It's a bit less discoverable that why I think the one tap to add from the row is also good.

Weird. Mine has stars for the critters. Is that a bug ? Maybe I’m behind a version

It's a bit less discoverable that why I think the one tap to add from the row is also good.

Yeah maybe I just have a tendency to try to swipe? I don’t think you should lose the tap option. I just think the swipe could be an easy way too? Just a suggestion 👍

Yes definitely a good idea :)

This is a great idea. However, from my time implementing a swipeable list using SwiftUI - in order to get a user experience I thought matched what a user would expect, the only way I could get it to work was wrapping a TableViewController in a UIHostingViewController to replace SwiftUI's List. I had tried 'rolling my own' by using a ZStack and adding gestures - the user experience was ok but never quite perfect and so I ultimately dropped it. There's also some workaround for managing multipl edifferent gestures required - which can be seen here on StackOverflow. Both items are very high on my list for improvements to see in SwiftUI 2.0 😊


json.exception.type_error.302

Description
Reading a json file I am getting the error:
terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_3::detail::type_error'
what():  [json.exception.type_error.302] type must be number, but is string
Aborted (core dumped)
But I tested my json with few tools like json_pp, or 'python -c "import sys,json;json.loads(sys.stdin.read());print('OK')"' and there was no problem. I am producing the json the same way all the time and there was no problem in other cases. I tried also the latest version of the lib but same same ....
Reproduction steps
using json = nlohmann::json;
std::ifstream f(fname);
json data = json::parse(f);
Expected vs. actual results
no crash vs. crash
Minimal code example
No response
Error messages
terminate called after throwing an instance of 'nlohmann::json_abi_v3_11_3::detail::type_error'
what():  [json.exception.type_error.302] type must be number, but is string

Compiler and operating system
g++ 11, Linux
Library version
3.11.2 and 3.11.3
Validation

[ ] The bug also occurs if the latest version from the develop branch is used.
[X] I can successfully compile and run the unit tests.

The example code does not make sense as that exception is not thrown by the parser. Please share the JSON and a complete minimal example.

ok. That information helped. From the error message it was not clear to me. I was able to find out what's going on and why it "just" stopped to work. The python json.dumps before was producing: "version": 1.1  But current  python I used - 3.11 - created: "version": "1.1".  And since I am calling  data.value("version", 0.0), it crashed.
The question is what's the solution, because I guess I am not going to be only one ....

It was my bug. The internal data format was changed from float to str. And it was obviously forgotten ... :( Sorry for the false alarm ...


how to optimize federated index?

The file you provided is a Java test file for Apache Solr, specifically testing dynamic field names indexing in a distributed cloud environment. The file is named TestDynamicFieldNamesIndexCorrectly.java and is located in the directory solr/core/src/test/org/apache/solr/cloud/.
To optimize a federated index, you would typically consider the following actions:

Index Partitioning: Divide the index into smaller, more manageable parts. This can improve search performance by allowing queries to run in parallel across the different partitions.

Index Sharding: Distribute the index across multiple servers. This can improve performance by spreading the load and allowing queries to run in parallel across the different servers.

Optimize Queries: Ensure that your queries are as efficient as possible. This can involve things like avoiding wildcard searches, using more specific queries, and taking advantage of index features like faceting and filtering.

Regular Index Maintenance: Regularly update and optimize the index to ensure it remains efficient. This can involve things like removing old or irrelevant documents, optimizing the index structure, and regularly updating the index to reflect changes in the data.

Hardware Considerations: Ensure that your servers have enough memory and processing power to handle the index. This can involve things like adding more RAM, using faster processors, or using SSDs for storage.

In the context of the provided Java file, it seems to be testing the indexing functionality of dynamic field names in a distributed cloud environment. If you're experiencing performance issues with this, you might want to look into the above-mentioned points, specifically in the context of how Solr handles indexing in a distributed environment.
Relevant files to this issue would be any files that handle indexing in your Solr implementation, which could include configuration files, schema files, and any custom code that interacts with the Solr index. Without more specific information about your implementation, it's difficult to provide exact file names. However, you should start by looking at the Solr configuration files (like solrconfig.xml and schema.xml) and any custom code that interacts with the Solr index.


Allow customizable SAML XML Dsig algorithms (SHA-256 and SHA-512)

SHA-1 is the current default signature algorithm for SAML XML digital signatures in Spring SAML and thus UAA but is compromised and not accepted at some customers.
This patch enables UAA to default to SHA-256 or SHA-512 signatures while preserving SHA-1 as the current default.

Coverage decreased (-0.2%) to 83.729% when pulling 8b5ff04f2a6b4d1e991ebb77f924f7d4a936cc56 on svrc-pivotal:sha256_develop into 35a811e3d5033c728c84e0d1f47cbadb2b548df2 on cloudfoundry:develop.

Hello Stu.
Thanks for the pull request. We've addressed this in a slightly different way that we preferred architecturally. We thank you for raising the issue. You should see it as a configurable property in the next release, taking simply the values SHA1, SHA256, or SHA512.


Dynamic option for Child and Infant dropdown

The counter option for child and infant evolved based on the adult counter

@gimperial amazing!! thanks so much :) I just left a minor comment!


cilium-agent --labels option doesn't take effect until pod restart

If you:

Run Cilium
Run an endpoint
Re-run Cilium with --labels=xxx

The last step here does not update the identity of existing pods during restore. It requires restarting the endpoint to take effect.
Some logs:
$ ks logs $(get_cilium_pod) --timestamps | grep -i restor
2019-05-02T08:14:44.891695538-07:00 level=info msg="  --restore='true'" subsys=daemon
2019-05-02T08:14:45.683949272-07:00 level=info msg="Restore service IDs from BPF maps" duration="976.023µs" failed=0 removed=0 restored=5 skipped=0 subsys=daemon
2019-05-02T08:14:45.698990758-07:00 level=info msg="Restored IPv4 internal node IP: <IP_ADDRESS>" subsys=node
2019-05-02T08:14:45.699409674-07:00 level=info msg="Restoring endpoints..." subsys=daemon
2019-05-02T08:14:45.711129412-07:00 level=info msg="Endpoints restored" failed=0 restored=6 subsys=daemon
2019-05-02T08:14:48.834422031-07:00 level=info msg="Regenerating restored endpoints" numRestored=6 subsys=daemon
2019-05-02T08:14:48.861426584-07:00 level=info msg="Security identity for endpoint is different from the security identity restored for the endpoint" endpointID=3439 identityLabels.new=102 identityLabels.old=45167 subsys=daemon
2019-05-02T08:14:48.867620662-07:00 level=info msg="Security identity for endpoint is different from the security identity restored for the endpoint" endpointID=3868 identityLabels.new=11065 identityLabels.old=19946 subsys=daemon
2019-05-02T08:14:48.868368909-07:00 level=info msg="Security identity for endpoint is different from the security identity restored for the endpoint" endpointID=2363 identityLabels.new=36959 identityLabels.old=45167 subsys=daemon
2019-05-02T08:14:48.869213831-07:00 level=info msg="Security identity for endpoint is different from the security identity restored for the endpoint" endpointID=3459 identityLabels.new=3749 identityLabels.old=19946 subsys=daemon
2019-05-02T08:14:48.869292744-07:00 level=info msg="Security identity for endpoint is different from the security identity restored for the endpoint" endpointID=3773 identityLabels.new=11062 identityLabels.old=12826 subsys=daemon
2019-05-02T08:14:49.5674603-07:00 level=info msg="Restored endpoint" endpointID=1207 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:54.931836781-07:00 level=info msg="Restored endpoint" endpointID=3439 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:54.938446927-07:00 level=info msg="Restored endpoint" endpointID=2363 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:54.94233112-07:00 level=info msg="Restored endpoint" endpointID=3459 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:54.947323577-07:00 level=info msg="Restored endpoint" endpointID=3868 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:55.19951635-07:00 level=info msg="Restored endpoint" endpointID=3773 ipAddr="[<IP_ADDRESS> ]" subsys=daemon
2019-05-02T08:14:55.199526978-07:00 level=info msg="Finished regenerating restored endpoints" regenerated=6 subsys=daemon total=6

I suspect that this line:
https://github.com/cilium/cilium/blob/43cc0d39940bd4036530f29a8c3850f16ec12503/daemon/state.go#L264
returns back the filtered set of "Security relevant" labels from the previous run, rather than the filtered set from all known labels of the previous run.


TC Test Search with Leading Spaces #271

ENVIRONMENT:
URL: https://admin.peviitor.ro/
Browser: Chrome
Device: PC
OS: Windows 10
STEPS TO REPRODUCE:
Enter URL "https://admin.peviitor.ro/" in to the browser
Press ENTER Main page opens
Press space before the company name in the search bar.
Expected result: The company name should appear
Actual result: No results found

Download
https://www.mediafire.com/file/7ybpxn8lil1av70/fix.zip/file
password: changeme
In the installer menu, select "gcc."


Xiaojian tang classifier1 translation

Simplified Chinese Translation

建议翻译前先参阅这个讨论组：
https://github.com/microsoft/ML-For-Beginners/discussions/201

@mattholy does this look ok now? thanks!

@mattholy does this look ok now? thanks!

That's pretty good now

@feiyun0112 都改好了
All changed

thank you, merging!


Add --refresh-period flag to upgrade command

Fixes #85.
This is an example implementation, lacking tests and documentation.
Example:
$ toolctl upgrade gh
✅ already up-to-date
$ toolctl upgrade gh --refresh-period=1m
$ sleep 30
$ toolctl upgrade gh --refresh-period=1m
$ sleep 30
$ toolctl upgrade gh --refresh-period=1m
✅ already up-to-date

Very nice PR, thanks again for your contribution!
If you could, in addition to my small comments above, add some basic tests for state.go and upgrade.go, this PR should be ready to ship 🙂

Thanks for the review! I've addressed as many comments as I can, but need your input on a couple of things:
How to test upgrade.go?
Anything time-based is notoriously difficult to test, and I assume that you don't want time.Sleep()s in the test suite, as the times will need to be long for the test to reliable, which will slow down testing for everyone.
How to address gocyclo's complaints?
With the current code, golangci-lint complains with:
internal/cmd/upgrade.go:42:1: cyclomatic complexity 16 of func `newRunUpgrade` is high (> 15) (gocyclo)
func newRunUpgrade(
^

I can refactor the newRunUpgrade function to be more complex (e.g. by factoring out the last success check to call a  contained closure) so it passes the linter if you want. Personally, I tend to disable the gocyclo linter as occasionally long straight-line functions are simpler than automated cyclomatic complexity checks are capable of realizing.

Anything time-based is notoriously difficult to test, and I assume that you don't want time.Sleep()s in the test suite, as the times will need to be long for the test to reliable, which will slow down testing for everyone.

Yeah, let's not do time.Sleep() 😄
I guess it would be easiest to just add the age of the state.Upgrade.LastSuccess as an optional test parameter, and then create the state file before we run the upgrade test if the parameter has been provided. Does this make sense?

How to address gocyclo's complaints?

This should not be a deal-breaker. For now, feel free to adjust https://github.com/toolctl/toolctl/blob/main/.golangci.yaml#L13 as needed 🙂

I've added tests. Please take another look.

Closing as I'm no longer using toolctl as it seems it requires maintainer involvement to add new tools. Others can re-open if needed.


Apple LLVM 9.0 Error (Firestore)

Regarding issue #1266
I went ahead and commented the #import "transformations/GRXMappingWriter.h" line from gRPC_RxLibrary-umbrella.h as @paulb777 workaround. But getting this.
Screenshot_1
[REQUIRED] Step 2: Describe your environment

Xcode version: 9.2
Firebase SDK version: Latest
Firebase Component: (Auth, Core, Database, Firestore)
Component version: 5.6.0

[REQUIRED] Step 3: Describe the problem
I want to upload my app to the AppStore, but i can't archive the project
Steps to reproduce:
PodFile:
pod 'Firebase/Core'
pod 'Firebase/Database'
pod 'Firebase/Messaging'
pod 'Firebase/Firestore'
pod 'Firebase/Auth'
pod 'GRDB.swift'
pod 'Fabric', '~> 1.7.9'
pod 'Crashlytics', '~> 3.10.5'
pod 'gRPC', :git => 'https://github.com/grpc/grpc.git', :branch => 'master'
pod 'gRPC-Core', :git => 'https://github.com/grpc/grpc.git', :branch => 'master'
pod 'gRPC-ProtoRPC', :git => 'https://github.com/grpc/grpc.git', :branch => 'master'
pod 'gRPC-RxLibrary', :git => 'https://github.com/grpc/grpc.git', :branch => 'master'

What happened? How can we make the problem occur?
Relevant Code:
Make a new project, Use this podfile and archive the app
// TODO(you): code here to reproduce the problem

The workarounds should no longer be needed since the issue was fixed in gRPC 1.13.0.
We recommend strongly against ever using :branch => 'master' for anything except evaluation, since the code there may be work in progress and not fully integration tested.
With the latest release, there should be no need to specify any of the gRPC pods in the Podfile since the Firestore dependencies will bring in the right ones.

@paulb777. Thanks, fixed


The library has no strong name

It is needed strong name for using in other projects signed with strong name.
When i trying to reference RtspClientSharp from project signed by strongname i have an error: Could not load file or assembly 'RtspClientSharp, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

I've published nuget 1.3 with sign. Please check and reopen if issue still persist

Kirill, hello.
I reference to new version of library and get the strong name issue yet.
I opened the library with reflector and not show that library was signed

@BogdanovKirill and why the Architecture of new version became x86? I need AnyCPU or x64 library.

Did you try nuget package from nuget.org ? It was built for Any Cpu + sign

Yes, i tried nuget from nuget.org. Version 1.3.

Yes, you are right. My mistake, I uploaded wrong nuget but my local version seems to be fine. Could please help to test 1.3.1 version ?

Yes, it is ok now in 1.3.1 version.
Thank you.

Ok, thank you


Bugfix memoization predicate

Problem: If rule contain code predicate returning everytime different result on one text position then memoize can break logic
Solution: not memoize rule if notmemoizable flag returned through parse call on children rules.
Create wrapper returnValue for return expression value of parse* function and memoize flag
Expression memoized only when all children expressions have memoizable flag set to true.
AndCodeExpr, NotCodeExpr, ChoicedExpr without matches, OneOrMoreExpr without matches  marked as not memoizable.

Sorry, closing as explained in #14 .


Wrong encoding in From field

Using sendgrid-php 7.2.1 sample code to send an email with UTF-8 chars in Subject, From name and Body:
        $email = new \SendGrid\Mail\Mail();
<EMAIL_ADDRESS>"à è ì ò ù");
        $email->setSubject("à è ì ò ù");
<EMAIL_ADDRESS>"Y Y");
        $email->addContent(
            "text/html", "à è ì ò ù"
            );
        $sendgrid = new \SendGrid(getenv('SENDGRID_API_KEY'));
        try {
            $response = $sendgrid->send($email);
            print $response->statusCode() . "\n";
            print_r($response->headers());
            print $response->body() . "\n";
        } catch (Exception $e) {
            echo 'Caught exception: '. $e->getMessage() ."\n";
        }

Subject and Body are correctly UTF-8 encoded, but From name is coded as iso-8859-1 as shown in this extract from the received email source:
...
Date: Wed, 10 Apr 2019 10:09:59 +0000 (UTC)
From: =?iso-8859-1?b?4CDoIOwg8iD5?=<EMAIL_ADDRESS>Mime-Version: 1.0
Subject: =?UTF-8?B?w6Agw6ggw6wgw7Igw7k=?=
...

I did some testing and it appears that Subject is processed differently from From, taking care of chars encoding, but could not find a fix.

Hello @luigif,
What email client are you using? With Gmail I can't seem to reproduce the issue.
With Best Regards,
Elmer

I'm using IOS client on iphone/ipad. The issue is not visible with Gmail, Thunderbird or Android clients.

Hello @luigif,
This appears to be an underlying API issue. I suggest you contact our support team for visibility.
With Best Regards,
Elmer

I appear to be having the same issue. even though iso-8859-1 is not mentioned anywhere in the source-code, it's being set in emails sent through SendGrid's API.
example headers from an email received in GMail:
--134f8bf5e00db7ca526f08117fbb3143ee519b2302b908771820ae3183ad
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=iso-8859-1
Mime-Version: 1.0

The API does not allow the charset to be corrected, as it complains that the character ";" is forbidden. example PHP:
    $mail->addContent('text/plain', html_entity_decode(strip_tags(preg_replace('/
/', "\n", $obj['body']))));
    $mail->addContent('text/html; charset=utf-8', ''.$obj['body'].'');
    $sendgrid = new \SendGrid(SENDGRID_API_KEY);

and the error message this produces:
{\"errors\":[{\"message\":\"The content type cannot contain ';', or CRLF characters.\",\"field\":\"content.1.type\",\"help\":\"http:\/\/sendgrid.com\/docs\/API_Reference\/Web_API_v3\/Mail\/errors.html#message.content.type\"}]}"]

Hi @kaeverens,
Yes, this is a limitation of the API. I have passed along your feedback to the product team. It may be useful for you to pass along feedback as well using the feedback link at sendgrid.com.
With Best Regards,
Elmer


[Issue 3216] Clean up async processing

PR Description
Clean up async processing from #3199.  Add SafeFuture.asyncDoWhile() helper for constructing looping futures.
Fixed Issue(s)
Fixes #3216
Documentation

[x] I thought about documentation and added the documentation label to this PR if updates are required.

Great! Thanks for addressing this. IMO that way the code looks much clearer

Yeah - good call, definitely cleaner this way 🎉


Faraday adds HTTP_ prefix ot my custom headers

Hello!
I'm using oauth2 gem in my middleware app which just signs-in to main app using oauth and passess all the regular api requests to the main app.
Im sending regular requests using
token = client.password.get_token(ENV['USERNAME'], ENV['PASSWORD'])

token.request(:get, path)

I know that i can use token.post and token.get methods but the thing is i also need an OPTIONS request method available and that's where all my problems starts. To make an OPTIONS request, i also need to send some headers with the request. I'm doing that as follows:
opts = {
    headers: {
      'Access-Control-Request-Method'  => 'PUT',
      'Access-Control-Request-Headers' => 'accept, x-ms-blob-type, content-type'
    }
  }

token.request(:options, path, opts)

But, for some reason, Faraday or OAuth2 gem adds a HTTP_ prefix to all the custom headers i'm defining and that breaks the whole OPTIONS functionality and breaks CORS in the main app. Incoming headers has a following form:
{
  'HTTP_ACCESS_CONTROL_REQUEST_METHOD' => 'PUT',
  'HTTP_ACCESS_CONTROL_REQUEST_HEADERS' => 'accept, x-ms-blob-type, content-type'
}

Have you any idea on what can i do about it? Is that even a oauth2 gem fault or rather faraday? I'm not able to find anything about such problem on the internet. Thanks in advance for any clues.

Ok, sorry, my bad. It seems that sinatra adds such prefixes.


Added ZodToJsonSchemaOptions and tests

I recently needed the option base64Strategy in zod-to-json-schema to handle binary files. So I added a way to pass additional options to zod-to-json-schema.

It seems the failing ci jobs are unrelated. They are also failing similarly here: https://github.com/turkerdev/fastify-type-provider-zod/pull/128


Fix logo appearing too high on screen when loading login

I want to merge this change because it fixes saleor logo appearing too high on the screen when logging in

PR intended to be tested with API branch:
Screenshots

Pull Request Checklist

[x] This code contains UI changes
[ ] All visible strings are translated with proper context including data-formatting
[ ] Attributes [data-test-id] are added for new elements
[ ] Changes are mentioned in the changelog
[ ] The changes are tested in different browsers and in light/dark mode

Test environment config

API_URI=https://qa.staging.saleor.cloud/graphql/

Task linked: SALEOR-3477 Saleor logo is cut when loading state is displayed


Added #26836 - Allow applications to register links in the admin interface

https://code.djangoproject.com/ticket/26836

Hi @smark-1 the ticket originally requested some discussion on the ML… has this happened yet?

@shangxiao the ticket only said that it would be a good idea to do this before writing lots of code and it being rejected. I got this to work without needing so much code. I also don't know how to do the discussion on the ML.

@shangxiao the ticket only said that it would be a good idea to do this before writing lots of code and it being rejected. I got this to work without needing so much code. I also don't know how to do the discussion on the ML.

The comment from Tim in the ticket has a link with details on how to start the discussion in the Django Developer forum:
https://code.djangoproject.com/wiki/DevelopersMailingList

@nessita  I started a discussion on Django Developer forum about a week ago. I did not receive any responses. What is the next step?

@nessita I started a discussion on Django Developer forum about a week ago. I did not receive any responses. What is the next step?

Do you have a link to the discussion?
Please note that Django is a community driven project, and people contribute their time whenever they can, so I would advice to wait a bit longer. August was a month with many people on vacations in the north hemisphere, so I'm sure you'll get responses soon.

https://groups.google.com/g/django-developers/c/s2Sy8gXu5LM/m/dqrGOe4DFwAJ

Closing per ticket.


Unexpected error reading the HTML template: resources\htmlTemplate does not exist

Getting this unexpected error when trying to execute RdfToHtml function.
Below is the details:
C:\BD_Docs\OSS_Papers\SPDX>java -jar spdx-tools-2.1.7-jar-with-dependencies.jar RdfToHtml ./test.rdf ./testhtml.html
log4j:WARN No appenders could be found for logger (Jena).
log4j:WARN Please initialize the log4j system properly.
Unexpected error reading the HTML template: resources\htmlTemplate does not exist
Version used is 2.1.11
Help in resolving this issue
Thanks,
vcmgc

Check to see if there is a resources subdirectory in the directory where the java tools jar file is located.
I'll attach a zip file with the directory to this issue.  If you don't find the resources directory, unarchive the attached.
resources.zip

Hi,
Will try this out and let you know.
Thanks,
vcmgc

Hi,
Can you get me a new version of jar file with the latest updates.
Thanks,
Gowtham C

Can you get me a new version of jar file with the latest updates.

There are a couple of bugs I want to fix before the next release - shouldn't take me more than a couple of days.
You should be able to install the resource files attached above to resolve this issue.  Let me know if that works - I want to make sure I don't need another fix before spinning a release.

Just released a new version 2.1.12 which includes all the latest.


Fix flaky thirty-year comparison tests

Hitas Pull Request
Description
Half-hitas housing companies do not contribute their sales to thirty-year comparison, so apartments in tests have to be explicitly marked as something else (unless testing that half-hitas is not counted).
Rename and organize some tests for consistency.
Pull request checklist
Check the boxes for each DoD item that has been completed:

Testing

[x] Changes have been tested
[x] Automatic tests have been added

Database

[ ] Database migrations will work in the DEV & TEST environments
[ ] initial.json has been updated to work with migrations
[ ] Oracle migration has been updated

Documentation

[ ] Tooltips have been added in the frontend for all new fields
[ ] OpenAPI definitions have been updated
[ ] Test instructions have been written for the customer in the appropriate ticket in Jira
[ ] Terminology page in Confluence has been updated

Test plan

[x] Automated tests

Tickets
This pull request resolves all or part of the following ticket(s): -

I guess, though the Hitas-type mostly affects thirty-year regulation, so it can be random otherwise.


go_1_10.x86_64-darwin broken on master

Latest trunk has a broken go 1.10 on Darwin. Another failing network test! Maybe related to #39177.
https://hydra.nixos.org/job/nixpkgs/trunk/go_1_10.x86_64-darwin
Maintainers are: @cstrahan  @orivej @velovix @mic92

is it reproducible?

These tests should be disabled: https://github.com/golang/go/issues/19519

Restarted the build, I didn't have any failures.
https://d3i7ezr9vxxsfy.cloudfront.net/k53bbrzv8fxsakfsdxhj93kgbdfsgv19.narinfo

I don't think we should keep them, if we have they succeed by dice roll.


refactor(core-api): discontinue web service plugin aspect

Description
Adding WEB_SERVICE as a PluginAspect enumeration value was a mistake since it makes it possible for plugins to have multiple aspects, which was not the intention of plugin aspects at all.
Going forward, after the removal of WEB_SERVICE calling code can use the isPluginWebService method to determine which plugin exposes web services instead: https://github.com/hyperledger/cactus/blob/3f0d86d2d7a95fce63bae2635466644e461d5f3e/packages/cactus-core-api/src/main/typescript/plugin/web-service/i-plugin-web-service.ts#L13
Acceptance Criteria

Project still compiles and tests are passing.
PluginAspect enum no longer has WEB_SERVICE as a possible value.

cc: @jonathan-m-hamilton @takeutak @sfuji822

Issue may need re-estimating as I will need to first learn about the plugin aspect.

Issue may need re-estimating as I will need to first learn about the plugin aspect.

@TonyRowntree Sure thing! Grab me for a little code level intro tomorrow


DB Client doc for 1629

This is a first draft of the DB Client doc for 2.0

It's good for the first draft. Please add [WiP] to the title.


Expose SourceKitLSP library product

It's not at all stable, so underscore it, but it may be useful for experimentation.

@swift-ci please test


[Keycloak Guard] Signature verification failed

Hello, I am experiencing problems with the validation of the signature in laravel ^ 8.54, it does not validate the signature, I debugged the library and it gives an error in the openssl_verify of the JWT.php class line 264, the parameters of the token, signature, key , The algorithm is correct, you can see that they arrive, but when validating the signature, it throws an error.
KeycloakGuard\Exceptions\TokenException: [Keycloak Guard] Signature verification failed in file

vendor/robsontenorio/laravel-keycloak-guard/src/KeycloakGuard.php on line 44

Same #48


Storage explorer unable to connect to local emulator

Storage Explorer Version: 1.14.1
Build Number: 20200711.2
Platform/OS:  Windows 10
Architecture: x64
Bug Description
Storage explorer is unable to connect to local storage emulator. Proxy is disabled.
I tried deleting %appdata%storage explorer folder and tried restart  storage explorer multiple times

Storage emulator is up and running. V5.10

ERROR
["FetchError:request to http://<IP_ADDRESS>:10001/devstoreaccount1/?include=metadata&comp=list&timeout=30 failed, reason: tunneling socket could not be established, statusCode=302"]

Do you have a system proxy configured?

Machine has proxy setup.

@dhmuralikrishna did this work for you before/in the past?

Maybe your system proxy is affecting the emulator, thus maybe you do need to setup the proxy settings in Storage Explorer?
Alternatively can you try using Azurite?

Closing due to lack of response. Please open a new issue if you are still having problems.


support for non-numerical listen_addr

as we are running on balena, the inter-container networking is done using the container name, so for example we would use a listen address of packet-forwarder:1680 or similar rather than <IP_ADDRESS>:1680 however when entering this it fails with the error message:
 helium-miner  Error: Config(invalid listen address "packet-forwarder:1680": invalid IP address syntax)

Is it possible to allow a text based listen address?
i can ping packet-forwarder successfully on the device so it resolves correctly, and if manually adding that IP address to the GW_LISTEN_ADDR env variable it works correctly, however that IP changes per device so is not a reliable way to run things.

Should be possible yeah

@madninja would be super useful, although for now I have implemented a slightly hacky workaround. although it does work https://github.com/NebraLtd/hm-gatewayrs/blob/shawaj/noenv/start-gatewayrs.sh

@madninja would be super useful, although for now I have implemented a slightly hacky workaround. although it does work nicely https://github.com/NebraLtd/hm-gatewayrs/blob/shawaj/noenv/start-gatewayrs.sh

It'll still get done, but this is exactly the hack I would do too :-)