text:
Why bosh plan to remove the registry from whole project?

Hi. I found bosh's plan to remove registry.
https://github.com/cloudfoundry/bosh-notes/blob/a34e33e95bda0712aa24ba03c1e49e4a1f147be1/cpi-api-v2.md
https://github.com/cloudfoundry/bosh-notes/blob/master/registry-removal.md
But I did not know the reason for this? Do we have any related discussions?
Thank you.

@EdwardStudy we came to the conclusion that removing the registry will improve the security model of Bosh.
Do you have any concerns with removing it?

Hi, @pivotal-jamil-shamy. Thanks for your reply.
I thought that the registry in director would be a SPOF of bosh architecture if the registry crashed or the registry db was unable to provide service.
So, could you explain more details about the security model of Bosh?
Thank you.

@cppforlife can you provide advice for how they should handle this.

cc @maximilien let's chat about this in our next sync

The Bosh is using the NATS old password for my new deployment. Can anyone please suggest me how can we replace NATS old password into Bosh registry with linking with the new password, so my deployment get successful. Thanks!

{"timestamp":"1525120714.657526970","source":"Route Registrar","message":"Route Registrar.Running","log_level":1,"data":{}}
{"timestamp":"1525120714.667801380","source":"Route Registrar","message":"Route Registrar.nats-connection-failed","log_level":2,"data":{"error":"nats: authorization violation","nats-hosts":[""]}}
{"timestamp":"1525120714.667839289","source":"Route Registrar","message":"Route Registrar.Exiting with error","log_level":3,"data":{"error":"nats: authorization violation","trace":"goroutine 1 [running]:\ncode.cloudfoundry.org/lager.(*logger).Fatal(0xc420056300, 0x6a4916, 0x12, 0x7aace0, 0xc420019e90, 0x0, 0x0, 0x0)\n\t/var/vcap/packages/route_registrar/src/code.cloudfoundry.org/lager/logger.go:131 +0xc7\nmain.main()\n\t/var/vcap/packages/route_registrar/src/code.cloudfoundry.org/route-registrar/main.go:83 +0xa34\n"}}
{"timestamp":"1525120754.712074280","source":"Route Registrar","message":"Route Registrar.Initializing","log_level":1,"data":{}}
{"timestamp":"1525120754.712217093","source":"Route Registrar","message":"Route Registrar.creating nats connection","log_level":1,"data":{}}
{"timestamp":"1525120754.712245464","source":"Route Registrar","message":"Route Registrar.Writing pid","log_level":1,"data":{"file":"/var/vcap/sys/run/route_registrar/route_registrar.pid","pid":"6671"}}
{"timestamp":"1525120754.712294817","source":"Route Registrar","message":"Route Registrar.Running","log_level":1,"data":{}}
{"timestamp":"1525120754.725129128","source":"Route Registrar","message":"Route Registrar.nats-connection-failed","log_level":2,"data":{"error":"nats: authorization violation","nats-hosts":["10.64.128.23:4222","10.64.128.24:4222"]}}

@wickyhasan this does not look like a problem with bosh itself. please find appropriate repo to make an issue: may be following: https://github.com/cloudfoundry/route-registrar

authors: EdwardStudy cppforlife dpb587-pivotal pivotal-jamil-shamy wickyhasan

repo: cloudfoundry/bosh-notes


text:
Bosh Director Deployment Failed

I am using the latest bosh version to deploy bosh director.
My bosh version is 2.0.28-cb77557. The deployment failed at
Started installing CPI
  Compiling package 'ruby-2.4/cff0ddb99e62cd9dfa146248dcbfd6df2a62a54e'... Finis  hed (00:00:00)
  Compiling package 'vsphere_cpi/e978df2abd6124573d76f4a204570cde9d4d429e'... Fi  nished (00:00:00)
  Compiling package 'iso9660wrap/82cd03afdce1985db8c9d7dba5e5200bcc6b5aa8'... Fi  nished (00:00:00)
  Installing packages... Finished (00:00:01)
  Rendering job templates... Finished (00:00:00)
  Installing job 'vsphere_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:01)

Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-trusty-go_agent/3468.11'... Failed   (00:00:05)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

creating stemcell (bosh-vsphere-esxi-ubuntu-trusty-go_agent 3468.11):
  CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","  message":"No route to host - No route to host - connect(2) for \"10.9.24.30\" po  rt 443 (10.9.24.30:443)","ok_to_retry":false}

Exit code 1

Here is my deployment script:
#!/bin/bash
/usr/local/bin/bosh create-env bosh.yml \
--state=mystate.json \
--vars-store=mycreds.yml \
-o vsphere/cpi.yml \
-o uaa.yml \
-o misc/powerdns.yml \
-o credhub.yml \
-v director_name=ctbc_k8s \
-v internal_cidr=10.9.24.192/26 \
-v internal_gw=10.9.24.254 \
-v internal_ip=10.9.24.193 \
-v network_name=Mgmt-TPE-PG-Mgmt \
-v vcenter_dc=TPE-DC \
-v vcenter_ds=vsanDatastore \
-v vcenter_cluster=Management \
-v vcenter_ip=10.9.24.30 \
-v vcenter_user=‘administrator@sysage.sso’ \
-v vcenter_password=‘VM@sysage123’ \
-v vcenter_templates=ctbc_templates \
-v vcenter_vms=ctbc_vms \
-v vcenter_disks=ctbt_disks \
-v dns_recursor_ip=10.9.24.31

Need advices if someone sees this issue before. Thanks!

seems like your jumpbox (where this command is running) cannot access your vcenter/esxi hosts (10.9.24.30).

vcenter and the jumpbox are both in the same subnet. 10.9.24.x . I also ping vcenter and it is alive from jumpbox point-of-view.

No route to host - No route to host - connect(2) for "10.9.24.30" po  rt 443 (10.9.24.30:443)

not sure what to tell ya, error above is pretty definitive.

Sorry..my bad. I pasted a wrong error message for my own test. Here is the one
Started validating
  Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh'... Finished (00:00:00)
  Downloading release 'bosh-vsphere-cpi'... Skipped [Found in local cache] (00:00:00)
  Validating release 'bosh-vsphere-cpi'... Finished (00:00:00)
  Downloading release 'uaa'... Skipped [Found in local cache] (00:00:00)
  Validating release 'uaa'... Finished (00:00:01)
  Downloading release 'credhub'... Skipped [Found in local cache] (00:00:00)
  Validating release 'credhub'... Finished (00:00:00)
  Validating cpi release... Finished (00:00:00)
  Validating deployment manifest... Finished (00:00:00)
  Downloading stemcell... Skipped [Found in local cache] (00:00:00)
  Validating stemcell... Finished (00:00:04)
Finished validating (00:00:08)

Started installing CPI
  Compiling package 'ruby-2.4/cff0ddb99e62cd9dfa146248dcbfd6df2a62a54e'... Finished (00:00:00)
  Compiling package 'vsphere_cpi/e978df2abd6124573d76f4a204570cde9d4d429e'... Finished (00:00:00)
  Compiling package 'iso9660wrap/82cd03afdce1985db8c9d7dba5e5200bcc6b5aa8'... Finished (00:00:00)
  Installing packages... Finished (00:00:00)
  Rendering job templates... Finished (00:00:00)
  Installing job 'vsphere_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:01)

Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-trusty-go_agent/3468.11'... Failed (00:00:13)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

creating stemcell (bosh-vsphere-esxi-ubuntu-trusty-go_agent 3468.11):
  CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"HTTPClient::KeepAliveDisconnected: Connection reset by peer","ok_to_retry":false}

Exit code 1

hmm, that's better error message but it seems that something is interfering
with stemcell upload. proxy?
On Fri, Dec 1, 2017 at 5:49 PM, Shawnho notifications@github.com wrote:

Sorry..my bad. I pasted a wrong error message for my own test. Here is the
one
Started validating
Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00)
Validating release 'bosh'... Finished (00:00:00)
Downloading release 'bosh-vsphere-cpi'... Skipped [Found in local cache] (00:00:00)
Validating release 'bosh-vsphere-cpi'... Finished (00:00:00)
Downloading release 'uaa'... Skipped [Found in local cache] (00:00:00)
Validating release 'uaa'... Finished (00:00:01)
Downloading release 'credhub'... Skipped [Found in local cache] (00:00:00)
Validating release 'credhub'... Finished (00:00:00)
Validating cpi release... Finished (00:00:00)
Validating deployment manifest... Finished (00:00:00)
Downloading stemcell... Skipped [Found in local cache] (00:00:00)
Validating stemcell... Finished (00:00:04)
Finished validating (00:00:08)
Started installing CPI
Compiling package 'ruby-2.4/cff0ddb99e62cd9dfa146248dcbfd6df2a62a54e'... Finished (00:00:00)
Compiling package 'vsphere_cpi/e978df2abd6124573d76f4a204570cde9d4d429e'... Finished (00:00:00)
Compiling package 'iso9660wrap/82cd03afdce1985db8c9d7dba5e5200bcc6b5aa8'... Finished (00:00:00)
Installing packages... Finished (00:00:00)
Rendering job templates... Finished (00:00:00)
Installing job 'vsphere_cpi'... Finished (00:00:00)
Finished installing CPI (00:00:01)
Starting registry... Finished (00:00:00)
Uploading stemcell 'bosh-vsphere-esxi-ubuntu-trusty-go_agent/3468.11'... Failed (00:00:13)
Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
creating stemcell (bosh-vsphere-esxi-ubuntu-trusty-go_agent 3468.11):
CPI 'create_stemcell' method responded with error: CmdError{"type":"Unknown","message":"HTTPClient::KeepAliveDisconnected: Connection reset by peer","ok_to_retry":false}
Exit code 1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cloudfoundry/bosh/issues/1852#issuecomment-348658407,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALV959wF5Wdr-JmYCAxHB1J6Jlj1IiZks5s8KylgaJpZM4QzHkU
.

Hmm...not sure and that's why I am testing different combinations. However, there is no proxy between vCenter and jumpbox. I am hoping to see some better diagnostic logs to understand why. The error message looks like bosh client uses httpclient to connect to vcenter and kick off for 13 seconds but remote peer (maybe vcenter) reset the link.

Allow me to update my own issue.
Since this issue was 'communication reset by peer', it occurred to me it could be vCenter compatibility issue. I therefore did a cross-check on another environment with vCenter 6.5U1 (build 5973321) and the problem disappeared. The one which gave me problem is
vCenter Server 6.5 0b Patch 1 (5178943).
I will try to upgrade the vCenter and check again.

source: gharchive/issue

repo: cloudfoundry/bosh

license_type: permissive

license_source: github-api


text:
refactor: replace multi_json with json_pure in runtime only

We need multi_json for tests means server.stub but remove it only from runtime now

no glue why this is now failing

see release note about https://github.com/cloudfoundry/cf-uaa-lib/releases/tag/v4.0.6

source: gharchive/pull-request

repo: cloudfoundry/cf-uaac


text:
Panic when using cf curl when uaa is down

Describe the bug and the command you saw an issue with
Cf curl panics if there is no uaa and the auth token is expired.
To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:

cf login as admin
bosh stop uaa
Decode Auth token from ~/.cf/config.json and wait until the expiration time
run cf curl v3/

Relevant Stack Trace
± ew |master ✓| → cf curl /v3

		Something unexpected happened. This is a bug in cf.

		Please re-run the command that caused this exception with the environment
		variable CF_TRACE set to true.

		Also, please update to the latest cli and try the command again:
		https://code.cloudfoundry.org/cli/releases

		Please create an issue at: https://code.cloudfoundry.org/cli/issues

		Include the below information when creating the issue:

		Command
		cf curl /v3

		CLI Version
		6.47.1+0921a21b7.2019-10-18

		Error
		runtime error: invalid memory address or nil pointer dereference

		Stack Trace
			goroutine 1 [running]:
	code.cloudfoundry.org/cli/util/panichandler.HandlePanic()
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/util/panichandler/handler.go:19 +0x81
	panic(0x1a230a0, 0x24f5ee0)
		/usr/local/Cellar/go@1.12/1.12.10/libexec/src/runtime/panic.go:522 +0x1b5
	code.cloudfoundry.org/cli/cf/api.CloudControllerCurlRepository.Request(0x2b51d30, 0xc0001e8200, 0x2b52020, 0xc0001cebb0, 0x1ba8400, 0x1, 0x12a05f200, 0x0, 0x0, 0x0, ...)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/cf/api/curl.go:62 +0x60f
	code.cloudfoundry.org/cli/cf/commands.(*Curl).Execute(0xc000090400, 0x1d485e0, 0xc0001e8780, 0x1d485e0, 0xc0001e8780)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/cf/commands/curl.go:111 +0x29d
	code.cloudfoundry.org/cli/cf/cmd.Main(0x0, 0x0, 0xc0000f0000, 0x3, 0x3)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/cf/cmd/cmd.go:122 +0xc94
	main.handleError(0x1d15b40, 0x2530ec0, 0x1d2e280, 0xc00011a4d0, 0x1d15b40, 0x2530ec0)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/main.go:271 +0x504
	main.executionWrapper(0x2b51bd0, 0x251d950, 0xc0001005a0, 0x0, 0x2, 0x0, 0x0)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/main.go:249 +0x2a9
	code.cloudfoundry.org/cli/vendor/github.com/jessevdk/go-flags.(*Parser).ParseArgs(0xc0001c6150, 0xc0000f0010, 0x2, 0x2, 0xc0002ffee0, 0x7035c5709e7ef34e, 0x2510120, 0xc000000180, 0xc0000f0f30)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/vendor/github.com/jessevdk/go-flags/parser.go:331 +0x883
	main.parse(0xc0000f0010, 0x2, 0x2, 0x1a28100, 0x251bc40, 0xc0000ba058)
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/main.go:61 +0xaa
	main.main()
		/Users/pivotal/concourse/volumes/live/457944c4-1b81-4699-4c45-d4cad5ec4847/volume/gopath/src/code.cloudfoundry.org/cli/main.go:49 +0xa3

When UAA can't be found, this line returns an error, meaning the response is <nil> while err is a HTTPNotFoundError. After executing this line err gets reset to <nil>, allowing us to call .Body on a nil pointer

Hey thanks @ewrenn8, for creating this issue. We'll try to review some time soon.

Thank you for your submission. If you still run into this issue with the latest CLI v8,  please open a new ticket.

authors: a-b abbyachau ewrenn8

repo: cloudfoundry/cli


text:
SSO link is incorrect for v1.5+ of PCF

When issuing a cf login --sso against a install of PCF 1.5+ the given url is for the uaa.
This no longer works, as it requires the login url instead.
ex.
One Time Code (Get one at https://uaa.run.pez.pivotal.io/passcode)
should be
One Time Code (Get one at https://login.run.pez.pivotal.io/passcode)
the prompt is coming from login, but the data seems to be set down in endpoints.go...
https://github.com/cloudfoundry/cli/blob/master/cf/api/endpoints.go#L80
https://github.com/cloudfoundry/cli/blob/master/cf/commands/login.go#L128

It will be available in the next release
https://www.pivotaltracker.com/n/projects/997278/stories/96567690

Story's done.

authors: camelpunch fhanik xchapter7x


text:
Add query parameters supported by CC 3.165.0 list operations

Listing resources supports query parameters named in docs.

AppUsageClient will be able to list events after_guid
Many clients gain support for label_selector, created_at and updated_at

/easycla

repo: cloudfoundry/go-cfclient

license: MIT


text:
metric-store.service.internal alias is not being published to bosh dns

What is this issue about?
BOSH components cannot communicate with the internal bosh alias metric-store.service.internal domain since it is not published via the bosh-dns-aliases-release job.
What version of Metric Store are you using?
1.4.2

This maybe specific to our tile release only but let's check all targets.

repo: cloudfoundry/metric-store-release


text:
Update integration tests

Description
Please include a summary of the change.
Type of change

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

Testing performed?

[ ] Unit tests
[ ] Integration tests
[ ] Acceptance tests

Checklist:

[ ] This PR is being made against the main branch, or relevant version branch
[ ] I have made corresponding changes to the documentation
[ ] I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

Should wait until after #108

These should be more like acceptance tests honestly

repo: cloudfoundry/system-metrics-release


text:
Please bump golang to 1.14

Thank you!

We appreciate you bringing this to our attention. We've shipped v67, which has the golang version systematically bumped in the job golang-1-windows. We've also removed the non-floating golang-1.13-windows, so that we'll have fewer of these out of date issue.
Thank you.

authors: aemengo danail-branekov

repo: cloudfoundry/windows-tools-release


text:
[Bug]: Barman cloud WAL restore exception: SSL validation failed [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:992)

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.

Contact Details
No response
Version
1.24.0
What version of Kubernetes are you using?
1.31
What is your Kubernetes environment?
Self-managed: k3s
How did you install the operator?
Helm
What happened?
Impossible to backup and restore using Oracle Object Storage
Cluster resource
---
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  name: pgcluster
  namespace: postgresql
spec:
  affinity:
    nodeSelector:
      kubernetes.io/arch: arm64
  backup:
    retentionPolicy: "15d"
    barmanObjectStore:
      destinationPath: s3://pgclusterbackup
      endpointURL: https://ORACLE_NAMESPACE.compat.objectstorage.sa-saopaulo-1.oraclecloud.com
      endpointCA:
        name: digicertca
        key: ca.crt
      s3Credentials:
        accessKeyId:
          name: oracle-creds
          key: ORACLE_ACCESS_KEY
        secretAccessKey:
          name: oracle-creds
          key: ORACLE_SECRET_KEY
      data:
        compression: snappy
      wal:
        compression: snappy
        maxParallel: 4
  imageName: ghcr.io/cloudnative-pg/postgresql:16.4-1-bookworm
  instances: 3
  primaryUpdateStrategy: unsupervised
  storage:
    storageClass: local-path
    size: 15Gi

Relevant log output
{"level":"info","ts":"2024-09-22T20:55:50Z","logger":"barman-cloud-wal-restore","msg":"2024-09-22 20:55:49,999 [33] ERROR: Barman cloud WAL restore exception: SSL validation failed for https://grc8rqyi2x7i.compat.objectstorage.sa-saopaulo-1.oraclecloud.com/pgclusterbackup [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:992)","pipe":"stderr","logging_pod":"pgcluster-5"}

Code of Conduct

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

Fixed using endpointURL: https://grc8rqyi2x7i.compat.objectstorage.sa-saopaulo-1.oci-customer.oci.com
I can't explain the reason

fixed, due to aggressive network policy

repo: cloudnative-pg/cloudnative-pg


text:
[FEAT] - Enhance Cluster onboarding process

Priority
(Medium) I'm annoyed but I'll live
Description
tbd
Reference Issues
No response

Adding to the wishlist:

I can onboard a directly connected cluster from the UI and don't require greenhousectl

API endpoint for onboarding / mass onboarding
Onboard cluster via kubectl ( no need for greenhousectl)

closed with #655

authors: IvoGoman auhlig kengou

repo: cloudoperators/greenhouse


text:
SOPS support

Describe the Feature
It would be great if Atmos had some interface for retrieving secrets from SOPS to be passed into terraform configuration.
Because we do our terraform configuration in Atmos' YAML, our TF configuration remains the same across environments/deployments. This is usually a good thing, but when something like a secret would change across environments, now we either need our terraform configuration to have some dynamic portion where it will grab the correct secret, or we would need to put the secret in raw YAML which isn't gonna happen.
I'm not sure about the extensibility of YAML
Expected Behavior
Some function in Atmos YAML to decode a SOPS secret from a given path.
Or some function in Atmos to read our SOPS files based on which stack/environment we are currently in and make those secrets available to reference in the YAML somehow.
Use Case
Secrets management can be better integrated with Atmos.
Describe Ideal Solution
See expected behavior
Alternatives Considered
No response
Additional Context
Terraform has a SOPS provider that we can use to do this work in our modules, and Terragrunt has native SOPS functions that can be used to do this in orchestration. Their implementation can be a reference.

We've recently extended atmos to support all types of datasources, although most are from gomplate. Unfortunately gomplate doesn't provide native SOPS.
It's a really interesting idea if stack configs could reference a datasource for SOPS encrypted secrets, guarded by cloud-specific keys like KMS.
See how we configure data sources today: https://atmos.tools/cli/configuration#templates
All we would need to do is add a datasource for a sops-encrypted file, then we could support key/value lookups using all the normal mechanisms.
https://github.com/getsops/sops

Love this idea -- Good issue @kevcube as this would definitely help us since we love SOPS so much.
@osterman is it possible to create datasources that are just for atmos? Or do they need to come from the upstream gomplate project?

We can include them simply in the Atmos core, without requiring them in the upstream dependencies. Also, if any of your team would be interested in getting more involved hands-on, let me know and we can coordinate.

This will be a very interesting feature to add to atmos
Currently, I am using terragrunt which has a natif support if sops datasource and this block me to move into atmos

authors: Gowiem kevcube osterman zadm

repo: cloudposse/atmos


text:
UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.1 to before v5.4.162",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=3792cb2ff43b1b193136a03ce1336462a827d792",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=642fc22210a5e59d40b1e4d56d21ec3effd401f2"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "3792cb2ff43b1b193136a03ce1336462a827d792",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "642fc22210a5e59d40b1e4d56d21ec3effd401f2",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "perf bpf: Avoid memory leak from perf_env__insert_btf()\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.162 by commit 642fc22210a5e59d40b1e4d56d21ec3effd401f2, it was introduced in version v5.1 by commit 3792cb2ff43b1b193136a03ce1336462a827d792. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1002265

repo: cloudsecurityalliance/gsd-database


text:
angular_devise + rails-api is vulnerable to CSRF attacks

Because rails-api strips out rails' CSRF protection - protect_from_forgery - assuming that everyone using rails-api will use token authentication, and because angular_devise relies on cookie authentication, using rails-api with angular_devise means that you are vulnerable to CSRF. At the very least, it might be good to have a one-line comment in the angular_devise Readme section on CSRF making a clear warning to people, because rails-api is becoming very common, and has been merged into Rails.
Please correct me if I'm wrong here, but I think this is a possible vulnerability worth highlighting.

Oh dear!
I thought this was enough "Aditionally, if you have CSRF Forgery Protection enabled for your controller actions, you will also need to include the X-CSRF-TOKEN header with the token provided by rails. The easiest way to include this is to use the angular_rails_csrf gem."
So, @aarongray, I'm not well versed in the matter of CSRF, that gem is not enough? :/

That gem is enough when the CSRF protection is ON. However, rails-api gem turns it off. I don't know what's the easiest way to turn it on for rails-api since I use full rails gem in my app which has it enabled.

README.md regarding CSRF was updated in #63

authors: TheOneTheOnlyDavidBrown aarongray thelastinuit vfonic

license: mit

license_source: bigquery


text:
Cofirmed stress test on Cloud Environment.

[x] Tests pass
[x] Appropriate changes to README are included in PR

Hi @takabow,
I've updated library versions by dependabot and confirmed the app worked on Cloud Environment. Please review this PR.


text:
Adding new AWS::CloudWatch::CompositeAlarm object, per March 2 2020 u…

…pdate

Thanks!

authors: axelpavageau markpeek

repo: cloudtools/troposphere


text:
docs(readme.md):add wechat-group-qrcode image

What type of PR is this?
docs: readme.md & readme_cn.md

What this PR does / why we need it (English/Chinese):
add wechat qrcode image

Which issue(s) this PR fixes:

 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.clark seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant baiyutang

repo: cloudwego/hertz


text:
希望提供 Trans 使用 gonet 的示例。

文档 https://www.cloudwego.io/zh/docs/kitex/tutorials/framework-exten/transport/ 提供了定制传输层的说明，比较抽象，作为框架使用者不知道怎么用。
changelog https://www.cloudwego.io/zh/blog/2022/08/26/kitex-v0.4.0-版本发布/  提到 v0.4.0 支持了 gonet 作为传输层，只说在 window 场景作为默认的传输层。但没有说明如何强制指定。

诉求：

https://www.cloudwego.io/zh/docs/kitex/tutorials/framework-exten/transport/  文档添加如何使用 gonet 配置的示例。
example 代码库添加关于传输层配置的示例，比如，添加一个可运行的 demo， 这个 demo 配置使用 gonet 作为传输层。

@HeyJavaBean 是否考虑完善下官网文档呢？

写法如下
var opts []server.Option
opts = append(opts, server.WithTransServerFactory(gonet.NewTransServerFactory()))
opts = append(opts, server.WithTransHandlerFactory(gonet.NewSvrTransHandlerFactory()))
svr := xxxservice.NewServer(handler, opts...)

authors: GuangmingLuo HeyJavaBean rectcircle

repo: cloudwego/kitex-examples


text:
doc: fix netpoll readme

修正了一些大小写和语法问题：Haproxy → HAProxy；KiteX → Kitex；to be open sourced → coming soon

 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.

感谢，但还请完善一下改动，包括同步修改中英文，并批量更新要修改的链接

authors: AshleeT CLAassistant Hchenn

repo: cloudwego/netpoll


text:
win10子系统Ubuntu10.04出现maybe in an endless loop (version = 69503)死循环

win10子系统内核版本：Linux  4.4.0-18362-Microsoft #1-Microsoft Mon Mar 18 12:02:00 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
出现死循环输出：
[:00000000] A message from [ :00000000 ] to [ :01000001 ] maybe in an endless loop (version = 69505)
[:00000000] A message from [ :00000000 ] to [ :01000001 ] maybe in an endless loop (version = 69505)
[:00000000] A message from [ :00000000 ] to [ :01000001 ] maybe in an endless loop (version = 69505)
[:00000000] A message from [ :00000000 ] to [ :01000001 ] maybe in an endless loop (version = 69505)

暂不支持 windows , 出现问题可以自己查。如果能修好，欢迎提 pr 。
信息是说 :01000001 这个服务出现了死循环，一直没有返回。通常第一个服务是 log 服务。

不过奇怪的是：如果 :01000001 是 log 服务，且阻塞，那么理论上你也无法看见 log 信息才对。所以你需要核查 :01000001 到底是什么。

使用win10的debian子系统测试成功了，可能Ubuntu子系统哪里有问题

wsl用的是MS重写的定制版kernel,
很多底层系统调用都没实现,
虽然很轻量,但是各种兼容一言难尽.
tail -f, gdb, docker这些时不时就会掉坑里.
坑太大, MS自己已经放弃了.
建议只在wsl下开发然后去linux下测试.
或换wsl2

提议，打开这个issue，在有pr时再关闭

WSL1 + Ubuntu 20.04碰到同样的问题，研究了下是libc的sleep有问题，另外一个表现是在控制台运行 sleep 1s 会报错 "Error- sleep: cannot read realtime clock: Invalid argument"。这里有个解决办法 https://www.how2shout.com/how-to/how-to-upgrade-ubuntu-18-04-lts-to-20-04-lts-on-wsl-windows-10.html

authors: cloudwu etnlGD fanlix fawdlstty lgbgoingdown

repo: cloudwu/skynet


text:
How to generate trial_pair_Verification.txt file if I would like to use own datasets.

Hi @dvisockas  @joonson,
Thanks for sharing the codes. Great work.
I would like to ask how should I prepare to generate trial_pair_Verification.txt file if I would like to use own datasets？
Take the veri_test.txt for voxceleb1 for example:
It contains 37720 rows. 40 speakers from voxcelceb1 test set. 4874 sentences in total.
each speaker has various sentences as below :
{'id10300': '304', 'id10301': '48', 'id10302': '166', 'id10303': '103', 'id10304': '162', 'id10305': '137', 'id10306': '184', 'id10307': '156', 'id10308': '64', 'id10309': '165', 'id10281': '84', 'id10280': '67', 'id10283': '233', 'id10282': '84', 'id10285': '93', 'id10284': '90', 'id10287': '48', 'id10286': '149', 'id10289': '87', 'id10288': '48', 'id10270': '158', 'id10271': '73', 'id10272': '50', 'id10273': '240', 'id10274': '54', 'id10275': '74', 'id10276': '185', 'id10277': '67', 'id10278': '187', 'id10279': '63', 'id10298': '127', 'id10299': '49', 'id10296': '98', 'id10297': '79', 'id10294': '138', 'id10295': '88', 'id10292': '265', 'id10293': '194', 'id10290': '137', 'id10291': '76'}
each speaker has various trails as below:
{'id10300': '2080', 'id10301': '336', 'id10302': '1328', 'id10303': '544', 'id10304': '1288', 'id10305': '1088', 'id10306': '1472', 'id10307': '1248', 'id10308': '496', 'id10309': '1320', 'id10281': '648', 'id10280': '496', 'id10283': '1864', 'id10282': '672', 'id10285': '728', 'id10284': '672', 'id10287': '384', 'id10286': '1184', 'id10289': '664', 'id10288': '368', 'id10270': '1120', 'id10271': '568', 'id10272': '392', 'id10273': '1920', 'id10274': '400', 'id10275': '568', 'id10276': '1480', 'id10277': '512', 'id10278': '1480', 'id10279': '488', 'id10298': '1016', 'id10299': '392', 'id10296': '784', 'id10297': '624', 'id10294': '1088', 'id10295': '704', 'id10292': '2080', 'id10293': '1544', 'id10290': '1072', 'id10291': '608'}
How is the these trails organised?
I would like to use the same strategy to prepare my own test dataset.
Thanks

Hey @ASR2020Guru , great username! :laughing:
The sample txt file can he found here
For this repository code to work without changing it, the test file needs to be conducted in such a manner that each row consists of three whitespace separated values: are two files spoken by the same speaker (1 or 0), first file path, second file path.
An example:
1 speaker_one/hello.wav speaker_one/goodbye.wav
0 speaker_one/intro.wav speaker_two/hello.wav

Note that you don't need to provide an absolute path as --test_path argument will add a base path to all provided speaker test pairs.
Does that answer your question?

Hi @dvisockas ,
Thanks for your quick reply. I am new to GitHub :)
I would like to know how to split the data for this trial_pair_Verification.txt file.
Correct me if I was wrong:
As indicated as the trial_pair_Verification.txt file which downloaded from robots.ox.ac.uk
Is the data pair of this trial_pair_Verification.txt file comes from the test folder of VoxCelceb1 (all 40 speakers)?
As I posted in the above thread, take speaker id10270 as an example:

in the the test folder of VoxCelceb1, speaker id10270 has 158 sentence. in the trial_pair_Verification.txt file, speaker id10300 has 1120 rows.

if we look closer in the  trial_pair_Verification.txt file,

1 id10270/x6uYqmx31kE/00001.wav id10270/8jEAjG6SegY/00008.wav
0 id10270/x6uYqmx31kE/00001.wav id10300/ize_eiCFEg0/00003.wav
1 id10270/x6uYqmx31kE/00001.wav id10270/GWXujl-xAVM/00017.wav
0 id10270/x6uYqmx31kE/00001.wav id10273/0OCW1HUxZyg/00001.wav
1 id10270/x6uYqmx31kE/00001.wav id10270/8jEAjG6SegY/00022.wav
0 id10270/x6uYqmx31kE/00001.wav id10284/Uzxv7Axh3Z8/00001.wav
1 id10270/x6uYqmx31kE/00001.wav id10270/GWXujl-xAVM/00033.wav
0 id10270/x6uYqmx31kE/00001.wav id10284/7yx9A0yzLYk/00029.wav

we can see each sentence of speaker id10270 has 8 trail pair rows, 4 of them are from same speaker , other 4 are random choosed from other speakers.

So is that 158 sentence of speaker id10270 should has 158*8=1264 rows(not 1120 rows)?

As I posted in the above thread, in this trail file, each speaker has about (7.77*(each speaker's sentences numbers)) rows, not like (8*(each speaker's sentences numbers)) rows. It makes me confused.

I would like to prepare my own dataset for test, so I have to create a trail file. I would like to follow Voxceleb's trail file stratege.
But I found that I cannot understand how it split/choose data to create such a trail file.
Thank you in advance.
Cheers

One of the reasons could be that not all the speakers have the same amount of files, hence if you would use all the files of each of the speakers you would have an imbalanced test set. If you want to understand the trial file creation I believe you would be better off contacting the VGG group :slightly_smiling_face:

Good point 👍
Thanks


text:
specify backend for running black formatting

I am not sure if this is right, but this looks like it might fix the issue on Luigi's populate fake data pull request.

I think we decided it was okay to have formatting check in scripts, so I am closing this one.


text:
Could not read source map: vue-global-config.mjs.map

Before you start, please make sure to:

[X] Read the document
[X] Have tried the latest version
[X] Search to see if your issue already exists
[X] Look for Q&A through appropriate channels like Stack Overflow

Link to minimal reproduction
https://github.com/AlexNastold/json-editor-vue-bug
Validation

[X] ⚠ I understand that invalid, incomplete or superfluous reproduction can lead to this issue being closed

Describe the bug and steps to reproduce
Could not read source map for file:///home/anastold/git-projects/admin-dashboard-ng2/node_modules/.pnpm/json-editor-vue%400.15.1_%40lezer%2Bcommon%401.2.1_vue%403.4.27_typescript%405.4.5_/node_modules/json-editor-vue/node_modules/.pnpm/vue-global-config%400.6.1_%40vue%2Bcomposition-api%401.7.2_vue%403.4.26_typescript%405.4.5___vue%403.4.26_typescript%405.4.5_/node_modules/vue-global-config/dist/vue-global-config.mjs: ENOENT: no such file or directory, open '/home/anastold/git-projects/admin-dashboard-ng2/node_modules/.pnpm/json-editor-vue@0.15.1_@lezer+common@1.2.1_vue@3.4.27_typescript@5.4.5_/node_modules/json-editor-vue/node_modules/.pnpm/vue-global-config@0.6.1_@vue+composition-api@1.7.2_vue@3.4.26_typescript@5.4.5___vue@3.4.26_typescript@5.4.5_/node_modules/vue-global-config/dist/vue-global-config.mjs.map'

Clone repository
Install dependencies
Run "pnpm dev"
Start chrome or edge with vscode "run and debug"
Look at vscodes "DEBUG CONSOLE"

System Info
System:
    OS: Linux 4.18 Red Hat Enterprise Linux 8.4 (Ootpa)
    CPU: (4) x64 Intel(R) Xeon(R) Gold 6240 CPU @ 2.60GHz
    Memory: 7.10 GB / 15.65 GB
    Container: Yes
    Shell: 5.5.1 - /usr/bin/zsh
  Binaries:
    Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
    npm: 10.2.4 - ~/.nvm/versions/node/v20.11.0/bin/npm
    pnpm: 9.0.6 - ~/.nvm/versions/node/v20.11.0/bin/pnpm
  npmPackages:
    @popperjs/core: ^2.11.8 => 2.11.8
    @tinymce/tinymce-vue: ^5.1.1 => 5.1.1
    @tsconfig/node20: ^20.1.4 => 20.1.4
    @types/bootstrap: ^5.2.10 => 5.2.10
    @types/humanize-duration: ^3.27.4 => 3.27.4
    @types/jquery: ^3.5.29 => 3.5.30
    @types/node: ^20.12.8 => 20.12.11
    @types/uuid: ^9.0.8 => 9.0.8
    @vite-pwa/assets-generator: ^0.2.4 => 0.2.4
    @vitejs/plugin-vue: ^5.0.4 => 5.0.4
    @vue/eslint-config-prettier: ^9.0.0 => 9.0.0
    @vue/eslint-config-typescript: ^13.0.0 => 13.0.0
    @vue/tsconfig: ^0.5.1 => 0.5.1
    archiver: ^7.0.1 => 7.0.1
    autoprefixer: ^10.4.19 => 10.4.19
    axios: ^1.6.8 => 1.6.8
    bootstrap: 5.3.3 => 5.3.3
    bootstrap-icons: ^1.11.3 => 1.11.3
    chalk: ^5.3.0 => 5.3.0
    chart.js: ^4.4.2 => 4.4.2
    corejs-typeahead: ^1.3.4 => 1.3.4
    datatables.net: ^2.0.5 => 2.0.7
    datatables.net-bs5: ^2.0.5 => 2.0.7
    datatables.net-buttons: ^3.0.2 => 3.0.2
    datatables.net-buttons-bs5: ^3.0.2 => 3.0.2
    datatables.net-fixedcolumns-bs5: ^5.0.0 => 5.0.0
    datatables.net-plugins: ^2.0.5 => 2.0.7
    datatables.net-responsive-bs5: ^3.0.2 => 3.0.2
    datatables.net-scroller-bs5: ^2.4.1 => 2.4.2
    datatables.net-vue3: ^3.0.1 => 3.0.1
    dayjs: ^1.11.11 => 1.11.11
    eslint: ^8.56.0 => 8.57.0
    eslint-plugin-vue: ^9.25.0 => 9.25.0
    flag-icons: ^7.2.1 => 7.2.1
    https-proxy-agent: ^7.0.4 => 7.0.4
    humanize-duration: ^3.32.0 => 3.32.0
    i18next: 23.11.3 => 23.11.3
    i18next-vue: ^4.0.0 => 4.0.0
    inquirer: ^9.2.20 => 9.2.20
    jquery: ^3.7.1 => 3.7.1
    js-file-download: ^0.4.12 => 0.4.12
    json-editor-vue: ^0.15.1 => 0.15.1
    knip: ^5.11.0 => 5.13.0
    machina: ^4.0.2 => 4.0.2
    node-fetch: ^3.3.2 => 3.3.2
    npm-check-updates: ^16.14.20 => 16.14.20
    npm-run-all: ^4.1.5 => 4.1.5
    pinia: ^2.1.7 => 2.1.7
    prettier: ^3.2.5 => 3.2.5
    rollup-plugin-license: ^3.3.1 => 3.3.1
    rollup-plugin-visualizer: ^5.12.0 => 5.12.0
    sass: ~1.76.0 => 1.76.0
    sharp: ^0.33.3 => 0.33.3
    stylelint: ^16.5.0 => 16.5.0
    stylelint-config-standard-scss: ^13.1.0 => 13.1.0
    stylelint-config-standard-vue: ^1.0.0 => 1.0.0
    svgo: ^3.2.0 => 3.3.0
    throttle-debounce: ^5.0.0 => 5.0.0
    tinymce: ^7.0.1 => 7.1.0
    typescript: ~5.4.5 => 5.4.5
    unplugin-auto-import: ^0.17.5 => 0.17.5
    uuid: ^9.0.1 => 9.0.1
    vite: ^5.2.11 => 5.2.11
    vite-plugin-image-optimizer: ^1.1.7 => 1.1.7
    vite-plugin-pwa: ^0.20.0 => 0.20.0
    vite-plugin-vue-devtools: ^7.1.3 => 7.1.3
    vue: ^3.4.26 => 3.4.27
    vue-chartjs: ^5.3.1 => 5.3.1
    vue-datepicker-next: ^1.0.3 => 1.0.3
    vue-router: ^4.3.2 => 4.3.2
    vue-scrolling-table: ^2.0.0 => 2.0.0
    vue-tsc: ^2.0.16 => 2.0.16
    vue3-toastify: ^0.2.1 => 0.2.1
    vuedraggable: 4.1.0 => 4.1.0
    workbox-window: ^7.1.0 => 7.1.0

Package Manager
pnpm

Can't reproduce.

It's empty.

https://github.com/microsoft/vscode/issues/102335
I think you should upgrade your VSCode and disable all installed extensions, then retry.

Important is step 4:

Still, everything is fine.

Strange - your output in the "debug console" ist my output in "terminal". In "debug console" there is only the message from browser console:

What is the result after upgrading VSCode to the latest version and disabling all extensions?

If you do a search you'll find that there are tons of Could not read source map errors around VSCode, you should first rule out that it's not caused by VSCode or VSCode's configuration, e.g. first of all, reset your configuration (you can back it up first).

Closing now due to inactivity. If there are any updates please just reply directly, no need to reopen a new one.

Finally the addition of "resolveSourceMapLocations" in my launch.json fixed it - the weird thing is, that wasn't a problem in the past and no other dependencies seemed to make any problems.

Sorry for wasting your time, but anyway, thank you very much for checking.

authors: AlexNastold cloydlau

repo: cloydlau/json-editor-vue


text:
Introduce structure!

Hello! What an anti-software we have here :)
Would you welcome few shell functions

making the script readable
and much-much-much smaller
and more robust/less error prone?

@jeremyheiler What do you think?

for example
api()
{
    local request="$1"
    local filename="${2:-$1}"

    curl -X GET \
      -H "Content-Type: application/json" \
      -L "https://api.clubhouse.io/api/v3/${request}?token=${CLUBHOUSE_API_TOKEN}" >"data/${filename}.json"
}

@szepeviktor You are free to fork the repository or make your own scripts! However, at this time we're fine with the simplicity of the script as it is. Thank you for your interest!

Okay.

authors: jeremyheiler szepeviktor

repo: clubhouse/exporter


text:
French translation for the e UI

Hello, i really like your work with this software, but as a french user, I will like to translate your entire software to make it usable by all french player who block because tey are not gifted in english.
I make some work in the "Translations.cs" in first, and i continue little by little as for exemple with "MainWindow.xaml"
I am not a computer programmer, and i don't know very lot about respect of the work of other, so, before to continue more on this, i want to know what you think about this, and if you want to se what i do to validate the changes i make

Ne fais pas le travail en double J'ai déjà traduis quelque fichiers dont celui dont tu parles. On pourrait unir nos efforts. Je n'arrive pas à compiler le code source actuel.

J'ai aussi des pb de compilation avec le SpeechResponder et pour l'instant, j'ai pas les compétences de régler le soucis sans une loooongue étude.
Par contre, si on fait un rebuild du SpeechService traduit et qu'on remplace le SpeechService.dll ainsi créé dans le répertoire de EDDI, on a les traductions.
C'est peut-être pas très propre comme solution, mais elle marche chez moi
----- Mail original -----
De: "popoqc" notifications@github.com
À: "cmdrmcdonald/EliteDangerousDataProvider" EliteDangerousDataProvider@noreply.github.com
Cc: "Astilane" paul.capmarty@free.fr, "Author" author@noreply.github.com
Envoyé: Vendredi 14 Juillet 2017 01:07:12
Objet: Re: [cmdrmcdonald/EliteDangerousDataProvider] French translation for the e UI (#240)
Ne fais pas le travail en double J'ai déjà traduis quelque fichiers dont celui dont tu parles. On pourrait unir nos efforts. Je n'arrive pas à compiler le code source actuel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .

J'ai rapporté l'erreur sur le GitHub j'attend une réponse.
Ils utilisent un vieux logiciel d'installation gratuit et efficace,
InnoSetup. Je l'ai utilisé pour ma version 2.3.0 puis de cette façon,
pas besoin de la version anglaise.
Le 14-07-17 à 15:46, Astilane a écrit :

J'ai aussi des pb de compilation avec le SpeechResponder et pour
l'instant, j'ai pas les compétences de régler le soucis sans une
loooongue étude.
Par contre, si on fait un rebuild du SpeechService traduit et qu'on
remplace le SpeechService.dll ainsi créé dans le répertoire de EDDI,
on a les traductions.
C'est peut-être pas très propre comme solution, mais elle marche chez moi
----- Mail original -----
De: "popoqc" notifications@github.com
À: "cmdrmcdonald/EliteDangerousDataProvider"
EliteDangerousDataProvider@noreply.github.com
Cc: "Astilane" paul.capmarty@free.fr, "Author"
author@noreply.github.com
Envoyé: Vendredi 14 Juillet 2017 01:07:12
Objet: Re: [cmdrmcdonald/EliteDangerousDataProvider] French
translation for the e UI (#240)
Ne fais pas le travail en double J'ai déjà traduis quelque fichiers
dont celui dont tu parles. On pourrait unir nos efforts. Je n'arrive
pas à compiler le code source actuel.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cmdrmcdonald/EliteDangerousDataProvider/issues/240#issuecomment-315450658,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYJ6nDedVut76D6k7Ib0bvg6O42qzF8Bks5sN8WPgaJpZM4OUhns.

authors: Astilane popoqc

repo: cmdrmcdonald/EliteDangerousDataProvider


text:
Spectating Issue

Dying while performing an emote will break your spectator camera until the ship leaves and you respawn. Your camera will be stuck in the void even if you switch spectator targets.

You are most likely using Corporate Restructure. This mod has errors that have not been fixed for a long time, and it actually prevents a lot of code from other mods from running, including mine.
But, if you are not running this mod, let me know and I can investigate this.

I am not running corporate restructure, no. This bug did not happen on previous versions of Too Many Emotes and started happening recently, one of the updates after adding jug band.

Ah, I misread your post. Dying was the trigger. Hmmm, I actually believe this happened to me before, so I don't think you're crazy. Let me see if I can find out what's going on. Thanks!


text:
Trigger Jenkins build on successful Travis run

Right now I believe Jenkins polls for any PRs to run. Ideally we'd like Jenkins to only be triggered when Travis passes. Hopefully there are Travis triggers and Jenkins APIs to make this possible.

I remember that we tried this before in #183.  That attempt failed and I backed it out because it only used a single, static trigger.  Once that Jenkinsfile got merged into master and other users eventually rebased their working branches, every commit they made to those branches would cause an explosion of build requests in unrelated branches, like open PRs to upstream, upstream master, and everywhere in between.
I'm happy to revisit this but it will take me a little while to understand how to do it correctly in order to avoid the disaster that resulted last time.

Takeaway from yesterday's discussion: @crd477 will instead explore a multi-stage Jenkins pipeline and we'll ditch Travis entirely.

I don't know if we settled on what the initial pass/fail stage would look like in terms of build steps and environment.  Could you describe that or point me to a Travis stage that I should use as a model?

I think the travis.yml in the repo is a good place for us to start for the first stage. On all systems it runs:
make
make check-format
make check-lint
make check-censored

That seems like a good first stage. The second stage could be the Jenkins pipeline we have now.
A theoretical third stage would be a scalability test on a beefy EC2 box if everything else passes, but we don't have the infrastructure for that yet.

Sorry for the delay in getting back to this.  Does the "shape" depicted here match the goal?
This is just a mocked up example but if it's right in principle, I'll submit the actual change.

Yes, this looks like what we want.

authors: apavlo crd477 mbutrovich

repo: cmu-db/terrier


text:
Fixes #35 Remove duplicate stateful apps entry

@CathPag It looks like all of the content @TomLeyden created in the Google doc was brought into the stateful_apps.md entry.
Let me know if I misunderstood what needs to be done here - I only deleted the duplicate file.

@SamDelamarter, yes, and now we have three entries:

stateful_apps.md
stateful_vs_stateless_applications.md
stateless_apps.md

We need one for stateful and another one for stateless. Don't want to delete the stateful vs stateless entry if there is good info in there. Wanna consolidate? Tom didn't have time, so if you'd like to tackle that, that'd be great!

authors: CathPag SamDelamarter

repo: cncf/glossary


text:
玩客云 docker安装迅雷报错 docker: no matching manifest for linux/arm/v7 in the manifest list entries.

玩客云刷casaos后，从docker 安装迅雷，报错 docker: no matching manifest for linux/arm/v7 in the manifest list entries.
docker run -d --name=xunlei --hostname=mynas --net=host -v /mnt/sdb1/xunlei:/xunlei/data -v /mnt/sdb1/downloads:/xunlei/downloads --restart=unless-stopped --privileged cnk3x/xunlei:latest

me too, how to resolve it?

cnk3x/xunlei  is not support armv7


text:
docker运行最新的镜像，提示找不到文件，访问显示502错误

下面为完整日志：
~$ sudo docker run --name=xunlei --hostname=lv1 --net=bridge -p 2345:2345 -v /media/disk1/xunlei/data:/xunlei/data -v /media/disk1/xunlei/downloads:/xunlei/downloads -e "LANG=zh_CN.utf8" --restart=unless-stopped --privileged  registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest
Unable to find image 'registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest' locally
latest: Pulling from cnk3x/xunlei
d4c3c94e5e10: Pull complete
2c8daff7e243: Pull complete
Digest: sha256:45cf8f70e7fbec6a46115e38e3b79dfc0502444a657803396ccb59a89f3ae8db
Status: Downloaded newer image for registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest
06/25 08:01:21 INF run mode=fork
06/25 08:01:21 INF proot init root=/xunlei
06/25 08:01:21 INF fork root=/xunlei command=/usr/bin/xlp
06/25 08:01:21 INF fork pid=14
06/25 08:01:21 INF run mode=chroot
06/25 08:01:21 INF _  _ _  _ _  _ _    ____  _
06/25 08:01:21 INF  /  |  | |\ | |    |___  |
06/25 08:01:21 INF /_ || | | | |___  |
06/25 08:01:21 INF daemon version: v3.11.2-3
06/25 08:01:21 INF spk version: v3.11.2
06/25 08:01:21 INF
06/25 08:01:21 INF Config
06/25 08:01:21 INF   - DashboardPort:     2345
06/25 08:01:21 INF   - DashboardUsername: none
06/25 08:01:21 INF   - DashboardPassword: none
06/25 08:01:21 INF   - DownloadPath:      /xunlei/downloads
06/25 08:01:21 INF   - DataPath:          /xunlei/data
06/25 08:01:21 INF   - Debug:             false
06/25 08:01:21 INF   - NewRoot:           /xunlei
06/25 08:01:21 INF Environ
06/25 08:01:21 INF   - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
06/25 08:01:21 INF   - HOSTNAME=lv1
06/25 08:01:21 INF   - LANG=zh_CN.utf8
06/25 08:01:21 INF   - LANGUAGE=zh_CN.UTF-8
06/25 08:01:21 INF   - LC_ALL=C
06/25 08:01:21 INF   - XL_DASHBOARD_PORT=2345
06/25 08:01:21 INF   - XL_DEBUG=false
06/25 08:01:21 INF   - XL_CHROOT=/xunlei
06/25 08:01:21 INF   - XL_PREVENT_UPDATE=true
06/25 08:01:21 INF   - HOME=/var/packages/pan-xunlei-com/shares/迅雷/.drive
06/25 08:01:21 INF   - XL_DIR_DOWNLOAD=/xunlei/downloads
06/25 08:01:21 INF   - XL_DIR_DATA=/xunlei/data
06/25 08:01:21 INF   - RUN_WITH_CHROOT=/xunlei
06/25 08:01:21 INF   - SYNOPLATFORM=apollolake
06/25 08:01:21 INF   - SYNOPKG_PKGNAME=pan-xunlei-com
06/25 08:01:21 INF   - SYNOPKG_PKGVER=3.11.2
06/25 08:01:21 INF   - SYNOPKG_PKGDEST=/var/packages/pan-xunlei-com/target
06/25 08:01:21 INF   - SYNOPKG_DSM_VERSION_MAJOR=7
06/25 08:01:21 INF   - SYNOPKG_DSM_VERSION_MINOR=2
06/25 08:01:21 INF   - SYNOPKG_DSM_VERSION_BUILD=64570
06/25 08:01:21 INF   - DriveListen=unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock
06/25 08:01:21 INF   - PLATFORM=群晖
06/25 08:01:21 INF   - OS_VERSION=apollolake dsm 7.2-64570
06/25 08:01:21 INF   - ConfigPath=/var/packages/pan-xunlei-com/shares/迅雷/
06/25 08:01:21 INF   - DownloadPATH=/var/packages/pan-xunlei-com/shares/迅雷/下载
06/25 08:01:21 INF   - TLSInsecureSkipVerify=true
06/25 08:01:21 INF   - GIN_MODE=release
06/25 08:01:21 INF syno mock addr=:2345
06/25 08:01:21 INF xunlei-pan-cli-launcher.amd64 start cmd="/var/packages/pan-xunlei-com/target/bin/bin/xunlei-pan-cli-launcher.amd64 -launcher_listen unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com-launcher.sock -pid /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid -logfile /var/packages/pan-xunlei-com/shares/迅雷/.drive/log-launcher.log -logsize 1MB -update_url http://127.0.0.1:2345/webman/3rdparty/pan-xunlei-com/version"
06/25 08:01:21 INF xunlei-pan-cli-launcher.amd64 started pid=22
06/25 08:01:22 ERR [xunlei-pan-cli-launcher.amd64.2] loadHistory ReadFile err:open /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/.history: no such file or directory path:/var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/.history
06/25 08:01:22 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:01:22 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:01:22 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:01:22 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:01:22 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:01:22 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 1
^[a06/25 08:01:42 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:01:42 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:01:42 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:01:42 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:01:42 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:01:42 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 2
06/25 08:02:12 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:02:12 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:02:12 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:02:12 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:02:12 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:02:12 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 3
06/25 08:02:29.71 INFO loadenv from /var/packages/pan-xunlei-com/target/ui
06/25 08:02:29.71 INFO [error={"Op":"open","Path":"/var/packages/pan-xunlei-com/target/ui/envconfig","Err":2}&file=/var/packages/pan-xunlei-com/target/ui/envconfig]read envconfig failed use default
06/25 08:02:29.71 INFO getEnvs succ DownloadPATH=/var/packages/pan-xunlei-com/shares/迅雷/下载
06/25 08:02:29.71 INFO getEnvs succ DriveListen=unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock
06/25 08:02:29.71 INFO getEnvs succ PLATFORM=群晖
06/25 08:02:29.71 INFO getEnvs succ ConfigPath=/var/packages/pan-xunlei-com/shares/迅雷/
06/25 08:02:29.71 INFO getEnvs succ TLSInsecureSkipVerify=true
06/25 08:02:29.71 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:29.71 INFO [config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/&device_space=]use config
06/25 08:02:29.71 INFO [report=true&use_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins]getPluginPATH
06/25 08:02:29.71 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:29.71 INFO setDownloadAlias DriveFileMount :map[]
06/25 08:02:29.71 INFO config.init getEnvStrArray DownloadPATH:[/var/packages/pan-xunlei-com/shares/迅雷/下载] len:1
06/25 08:02:29.71 INFO config.init init succ: &{isInit:true NasIDKey: NasId: NasSubIdKey: NasSubId: DeviceId: WorkDir: BinPath:/var/packages/pan-xunlei-com/target/ui Platform:群晖 PathSplit:: DownloadPATHs:[/var/packages/pan-xunlei-com/shares/迅雷/下载] TorrentPath: DriveFileMount:map[] PluginTokenDuration:5h0m0s PluginPATH:/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins AuthTokenPATH: DriveArgs: DrivePlayer: DriveListen:unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock DrivePortFile: DriveLogLevel:info DriveLogFile: DriveLogSize:10MB DriveLogFormat: DriveUpdate: DriveConfigPATH:/var/packages/pan-xunlei-com/shares/迅雷/ DrivePIDFile: DriveInfoFile: DrivePublicPort:21603 FreePortRange:[] FreePortRangeUDP:[] LauncherLogFile: LauncherLogSize: LauncherPIDFile: LauncherListen:127.0.0.1:5051 NfoIsDisable: RefreshTokenDuration:1h KvCacheDuration:24h0m0s TaskCfgPath: ScrapeCacheDuration:24h0m0s SyncWatchDogDuration:30m0s CachePATH: DeviceSpace: DeviceName: TLSInsecureSkipVerify:true ImportTask:true SingleTaskMaxMB:100 SingleTaskReserveMB:20 OverallShareMaxMB:200 ThirdAuthURL: PanCliEnv: GeneDBShadowFileDuration:24h DebugPrintFileEvents:[] GossipFile:/var/packages/pan-xunlei-com/shares/迅雷/.drive/gossip.json PluginWithBash:false Webhook:{Modules:map[] URL:} HostXluser:https://xluser-ssl.xunlei.com HostApiPan:https://api-pan.xunlei.com HostShoulei:https://api-shoulei-ssl.xunlei.com HostHighSpeedFlow:https://api-pan.xunlei.com EnableTaskCfg:true WebhookHealthzToken:}
06/25 08:02:29.71 INFO start detect platform
06/25 08:02:29.71 INFO Detector.Detect envPlatform:群晖
06/25 08:02:29.71 INFO detect platform: synology X9ibISwpIp8jQ4Ya nasid: labels: [withQrcodeLogin withOtherAuthLogin withPlugin withPreviewPrivilege allowUseConfigPathAsCachePath withRootDiskSelect withInstallLocalPlugin withHighSpeedFlowCtrl withFetchFolder withSyncDriveFile withUserResetScrapeResult]
2024/06/25 08:02:29 Failed to dial: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
2024/06/25 08:02:29 http: proxy error: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
06/25 08:02:31.25 INFO loadenv from /var/packages/pan-xunlei-com/target/ui
06/25 08:02:31.25 INFO [error={"Op":"open","Path":"/var/packages/pan-xunlei-com/target/ui/envconfig","Err":2}&file=/var/packages/pan-xunlei-com/target/ui/envconfig]read envconfig failed use default
06/25 08:02:31.25 INFO getEnvs succ DownloadPATH=/var/packages/pan-xunlei-com/shares/迅雷/下载
06/25 08:02:31.25 INFO getEnvs succ DriveListen=unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock
06/25 08:02:31.25 INFO getEnvs succ PLATFORM=群晖
06/25 08:02:31.25 INFO getEnvs succ ConfigPath=/var/packages/pan-xunlei-com/shares/迅雷/
06/25 08:02:31.25 INFO getEnvs succ TLSInsecureSkipVerify=true
06/25 08:02:31.25 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:31.25 INFO [config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/&device_space=]use config
06/25 08:02:31.25 INFO [report=true&use_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins]getPluginPATH
06/25 08:02:31.25 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:31.25 INFO setDownloadAlias DriveFileMount :map[]
06/25 08:02:31.25 INFO config.init getEnvStrArray DownloadPATH:[/var/packages/pan-xunlei-com/shares/迅雷/下载] len:1
06/25 08:02:31.25 INFO config.init init succ: &{isInit:true NasIDKey: NasId: NasSubIdKey: NasSubId: DeviceId: WorkDir: BinPath:/var/packages/pan-xunlei-com/target/ui Platform:群晖 PathSplit:: DownloadPATHs:[/var/packages/pan-xunlei-com/shares/迅雷/下载] TorrentPath: DriveFileMount:map[] PluginTokenDuration:5h0m0s PluginPATH:/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins AuthTokenPATH: DriveArgs: DrivePlayer: DriveListen:unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock DrivePortFile: DriveLogLevel:info DriveLogFile: DriveLogSize:10MB DriveLogFormat: DriveUpdate: DriveConfigPATH:/var/packages/pan-xunlei-com/shares/迅雷/ DrivePIDFile: DriveInfoFile: DrivePublicPort:21603 FreePortRange:[] FreePortRangeUDP:[] LauncherLogFile: LauncherLogSize: LauncherPIDFile: LauncherListen:127.0.0.1:5051 NfoIsDisable: RefreshTokenDuration:1h KvCacheDuration:24h0m0s TaskCfgPath: ScrapeCacheDuration:24h0m0s SyncWatchDogDuration:30m0s CachePATH: DeviceSpace: DeviceName: TLSInsecureSkipVerify:true ImportTask:true SingleTaskMaxMB:100 SingleTaskReserveMB:20 OverallShareMaxMB:200 ThirdAuthURL: PanCliEnv: GeneDBShadowFileDuration:24h DebugPrintFileEvents:[] GossipFile:/var/packages/pan-xunlei-com/shares/迅雷/.drive/gossip.json PluginWithBash:false Webhook:{Modules:map[] URL:} HostXluser:https://xluser-ssl.xunlei.com HostApiPan:https://api-pan.xunlei.com HostShoulei:https://api-shoulei-ssl.xunlei.com HostHighSpeedFlow:https://api-pan.xunlei.com EnableTaskCfg:true WebhookHealthzToken:}
06/25 08:02:31.25 INFO start detect platform
06/25 08:02:31.25 INFO Detector.Detect envPlatform:群晖
06/25 08:02:31.25 INFO detect platform: synology X9ibISwpIp8jQ4Ya nasid: labels: [withQrcodeLogin withOtherAuthLogin withPlugin withPreviewPrivilege allowUseConfigPathAsCachePath withRootDiskSelect withInstallLocalPlugin withHighSpeedFlowCtrl withFetchFolder withSyncDriveFile withUserResetScrapeResult]
2024/06/25 08:02:31 Failed to dial: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
2024/06/25 08:02:31 http: proxy error: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
06/25 08:02:42.07 INFO loadenv from /var/packages/pan-xunlei-com/target/ui
06/25 08:02:42.07 INFO [error={"Op":"open","Path":"/var/packages/pan-xunlei-com/target/ui/envconfig","Err":2}&file=/var/packages/pan-xunlei-com/target/ui/envconfig]read envconfig failed use default
06/25 08:02:42.07 INFO getEnvs succ DownloadPATH=/var/packages/pan-xunlei-com/shares/迅雷/下载
06/25 08:02:42.07 INFO getEnvs succ DriveListen=unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock
06/25 08:02:42.07 INFO getEnvs succ PLATFORM=群晖
06/25 08:02:42.07 INFO getEnvs succ ConfigPath=/var/packages/pan-xunlei-com/shares/迅雷/
06/25 08:02:42.07 INFO getEnvs succ TLSInsecureSkipVerify=true
06/25 08:02:42.07 INFO [config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/&device_space=]use config
06/25 08:02:42.07 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:42.07 INFO [report=true&use_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins]getPluginPATH
06/25 08:02:42.07 INFO [device_space=&config_path=/var/packages/pan-xunlei-com/shares/迅雷/.drive/]use config
06/25 08:02:42.07 INFO setDownloadAlias DriveFileMount :map[]
06/25 08:02:42.07 INFO config.init getEnvStrArray DownloadPATH:[/var/packages/pan-xunlei-com/shares/迅雷/下载] len:1
06/25 08:02:42.07 INFO config.init init succ: &{isInit:true NasIDKey: NasId: NasSubIdKey: NasSubId: DeviceId: WorkDir: BinPath:/var/packages/pan-xunlei-com/target/ui Platform:群晖 PathSplit:: DownloadPATHs:[/var/packages/pan-xunlei-com/shares/迅雷/下载] TorrentPath: DriveFileMount:map[] PluginTokenDuration:5h0m0s PluginPATH:/var/packages/pan-xunlei-com/shares/迅雷/.drive/plugins AuthTokenPATH: DriveArgs: DrivePlayer: DriveListen:unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock DrivePortFile: DriveLogLevel:info DriveLogFile: DriveLogSize:10MB DriveLogFormat: DriveUpdate: DriveConfigPATH:/var/packages/pan-xunlei-com/shares/迅雷/ DrivePIDFile: DriveInfoFile: DrivePublicPort:21603 FreePortRange:[] FreePortRangeUDP:[] LauncherLogFile: LauncherLogSize: LauncherPIDFile: LauncherListen:127.0.0.1:5051 NfoIsDisable: RefreshTokenDuration:1h KvCacheDuration:24h0m0s TaskCfgPath: ScrapeCacheDuration:24h0m0s SyncWatchDogDuration:30m0s CachePATH: DeviceSpace: DeviceName: TLSInsecureSkipVerify:true ImportTask:true SingleTaskMaxMB:100 SingleTaskReserveMB:20 OverallShareMaxMB:200 ThirdAuthURL: PanCliEnv: GeneDBShadowFileDuration:24h DebugPrintFileEvents:[] GossipFile:/var/packages/pan-xunlei-com/shares/迅雷/.drive/gossip.json PluginWithBash:false Webhook:{Modules:map[] URL:} HostXluser:https://xluser-ssl.xunlei.com HostApiPan:https://api-pan.xunlei.com HostShoulei:https://api-shoulei-ssl.xunlei.com HostHighSpeedFlow:https://api-pan.xunlei.com EnableTaskCfg:true WebhookHealthzToken:}
06/25 08:02:42.07 INFO start detect platform
06/25 08:02:42.07 INFO Detector.Detect envPlatform:群晖
06/25 08:02:42.07 INFO detect platform: synology X9ibISwpIp8jQ4Ya nasid: labels: [withQrcodeLogin withOtherAuthLogin withPlugin withPreviewPrivilege allowUseConfigPathAsCachePath withRootDiskSelect withInstallLocalPlugin withHighSpeedFlowCtrl withFetchFolder withSyncDriveFile withUserResetScrapeResult]
2024/06/25 08:02:42 Failed to dial: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
2024/06/25 08:02:42 http: proxy error: dial unix /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.sock: connect: no such file or directory
06/25 08:02:52 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:02:52 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:02:52 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:02:52 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:02:52 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:02:52 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 4
06/25 08:03:42 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:03:42 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:03:42 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:03:42 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:03:42 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:03:42 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 5
06/25 08:04:42 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:04:42 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:04:42 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:04:42 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:04:42 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:04:42 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 6
06/25 08:05:52 ERR [xunlei-pan-cli-launcher.amd64.2] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:05:52 WRN [xunlei-pan-cli-launcher.amd64.2] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
06/25 08:05:52 ERR [xunlei-pan-cli-launcher.amd64.2] launcher file /var/packages/pan-xunlei-com/shares/迅雷/.drive/bin/xunlei-pan-cli.3.11.2.amd64 not executable
06/25 08:05:52 ERR [xunlei-pan-cli-launcher.amd64.2] startVersion err:file not executable: 3.11.2 version:3.11.2
06/25 08:05:52 ERR [xunlei-pan-cli-launcher.amd64.2] start new version 3.11.2=>3.11.2 err:file not executable: 3.11.2
06/25 08:05:52 WRN [xunlei-pan-cli-launcher.amd64.2] launcher version error file not executable: 3.11.2 retry 7

但是到对应目录下，中文变为乱码，不知道这个会不会有影响

感觉是ubuntu发行版的问题，我用的是24.04，打算装回22.04看看

一样的问题，只不过我触发的原因是将外部设备映射到docker会报错，随便找个其他文件夹映射就不报错了，感觉像是权限的问题

更新修复了一些问题，可以重新拉取试试。

registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest，大佬，用这个镜像还是不行

sudo docker run --name=xunlei --hostname=lv1 --net=bridge -p 2345:2345 -v /xunlei/data:/xunlei/data -v /xunlei/downloads:/xunlei/downloads --restart=unless-stopped --privileged registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest
07/01 11:00:31 INF [main] mount...
07/01 11:00:31 INF [main] can't find package version, repair it
07/01 11:00:34 INF [main] _  _ _  _ _  _ _    ____  _
07/01 11:00:34 INF [main]  /  |  | |\ | |    |___  |
07/01 11:00:34 INF [main] /_ || | | | |___  |
07/01 11:00:34 INF [main] daemon version: v3.20.0
07/01 11:00:34 INF [main] spk version: 3.21.0
07/01 11:00:34 INF [main] port: 2345
07/01 11:00:34 INF [main] ip:
07/01 11:00:34 INF [main] dashboard username:
07/01 11:00:34 INF [main] dashboard password:
07/01 11:00:34 INF [main] dir download: /xunlei/downloads
07/01 11:00:34 INF [main] dir data: /xunlei/data
07/01 11:00:34 INF [main] uid:
07/01 11:00:34 INF [main] gid:
07/01 11:00:34 INF [main] prevent update: true
07/01 11:00:34 INF [main] chroot: /xunlei
07/01 11:00:34 INF [main] debug: false
07/01 11:00:34 INF [main] args: "--dashboard_port" "2345" "--dir_download" "/xunlei/downloads" "--dir_data" "/xunlei/data" "--prevent_update" "--chroot" "/xunlei"
07/01 11:00:34 INF [mock] web started listen=[::]:2345
07/01 11:00:34 INF [xunlei-pan-cli] start cmd="/var/packages/pan-xunlei-com/target/bin/bin/xunlei-pan-cli-launcher.amd64 -launcher_listen unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com-launcher.sock -pid /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid -update_url http://127.0.0.1:2345/webman/3rdparty/pan-xunlei-com/version"
07/01 11:00:34 INF [xunlei-pan-cli] started pid=34
07/01 11:00:35 ERR [xunlei-pan-cli] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
07/01 11:00:35 WRN [xunlei-pan-cli] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory
07/01 11:00:35 ERR [xunlei-pan-cli] oauth2client/client.go:250 [device_space=] > client.Request GetCredentials err:access token is expired
07/01 11:00:35 ERR [xunlei-pan-cli] drive/client.go:664 [func_st=07/01 11:00:35&trace_id=3NcHciWv&pid=45&func_name=Client.UpdateUserInfo] > UpdateUserInfo Request err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://xluser-ssl.xunlei.com/v1/user/me","HttpStatus":401} url:https://xluser-ssl.xunlei.com/v1/user/me
07/01 11:00:35 ERR [xunlei-pan-cli] oauth2client/client.go:250 [device_space=] > client.Request GetCredentials err:access token is expired
07/01 11:00:35 ERR [xunlei-pan-cli] drive/events.go:93 [req={"space":"","filters":"{"type":{"in":"TYPE_PLAY"}}","limit":30,"page_token":""}] > GetEvents RawRequest err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://api-pan.xunlei.com/drive/v1/events?filters={"type":{"in":"TYPE_PLAY"}}\u0026limit=30\u0026page_token=\u0026space=","HttpStatus":401}
07/01 11:00:35 ERR [xunlei-pan-cli] runner/device_runners.go:63  > CreateTasksRunner UpdateUserInfo err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://xluser-ssl.xunlei.com/v1/user/me","HttpStatus":401} deviceSpace:

sudo docker run --name=xunlei --hostname=lv1 --net=bridge -p 2345:2345 -v /xunlei/data:/xunlei/data -v /xunlei/downloads:/xunlei/downloads --restart=unless-stopped --privileged registry.cn-shenzhen.aliyuncs.com/cnk3x/xunlei:latest 07/01 11:00:31 INF [main] mount... 07/01 11:00:31 INF [main] can't find package version, repair it 07/01 11:00:34 INF [main] _ _ _ _ _ _ _ ____ _ 07/01 11:00:34 INF [main] / | | |\ | | |___ | 07/01 11:00:34 INF [main] / || | | |_ |___ | 07/01 11:00:34 INF [main] daemon version: v3.20.0 07/01 11:00:34 INF [main] spk version: 3.21.0 07/01 11:00:34 INF [main] port: 2345 07/01 11:00:34 INF [main] ip: 07/01 11:00:34 INF [main] dashboard username: 07/01 11:00:34 INF [main] dashboard password: 07/01 11:00:34 INF [main] dir download: /xunlei/downloads 07/01 11:00:34 INF [main] dir data: /xunlei/data 07/01 11:00:34 INF [main] uid: 07/01 11:00:34 INF [main] gid: 07/01 11:00:34 INF [main] prevent update: true 07/01 11:00:34 INF [main] chroot: /xunlei 07/01 11:00:34 INF [main] debug: false 07/01 11:00:34 INF [main] args: "--dashboard_port" "2345" "--dir_download" "/xunlei/downloads" "--dir_data" "/xunlei/data" "--prevent_update" "--chroot" "/xunlei" 07/01 11:00:34 INF [mock] web started listen=[::]:2345 07/01 11:00:34 INF [xunlei-pan-cli] start cmd="/var/packages/pan-xunlei-com/target/bin/bin/xunlei-pan-cli-launcher.amd64 -launcher_listen unix:///var/packages/pan-xunlei-com/target/var/pan-xunlei-com-launcher.sock -pid /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid -update_url http://127.0.0.1:2345/webman/3rdparty/pan-xunlei-com/version" 07/01 11:00:34 INF [xunlei-pan-cli] started pid=34 07/01 11:00:35 ERR [xunlei-pan-cli] KillDrivePid ioutil.ReadFile err:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory 07/01 11:00:35 WRN [xunlei-pan-cli] kill process error:open /var/packages/pan-xunlei-com/target/var/pan-xunlei-com.pid.child: no such file or directory 07/01 11:00:35 ERR [xunlei-pan-cli] oauth2client/client.go:250 [device_space=] > client.Request GetCredentials err:access token is expired 07/01 11:00:35 ERR [xunlei-pan-cli] drive/client.go:664 [func_st=07/01 11:00:35&trace_id=3NcHciWv&pid=45&func_name=Client.UpdateUserInfo] > UpdateUserInfo Request err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://xluser-ssl.xunlei.com/v1/user/me","HttpStatus":401} url:https://xluser-ssl.xunlei.com/v1/user/me 07/01 11:00:35 ERR [xunlei-pan-cli] oauth2client/client.go:250 [device_space=] > client.Request GetCredentials err:access token is expired 07/01 11:00:35 ERR [xunlei-pan-cli] drive/events.go:93 [req={"space":"","filters":"{"type":{"in":"TYPE_PLAY"}}","limit":30,"page_token":""}] > GetEvents RawRequest err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://api-pan.xunlei.com/drive/v1/events?filters={"type":{"in":"TYPE_PLAY"}}\u0026limit=30\u0026page_token=\u0026space=","HttpStatus":401} 07/01 11:00:35 ERR [xunlei-pan-cli] runner/device_runners.go:63 > CreateTasksRunner UpdateUserInfo err:{"error":"unauthenticated","error_description":"either credentials or access token not found(access token is expired)","error_uri":"https://xluser-ssl.xunlei.com/v1/user/me","HttpStatus":401} deviceSpace:

这是没登录前显示的正常日志，从这里看还没发现失败的迹象啊

iam so sorry....我傻了


text:
gitignore: add .idea

Fixes: #4

Landed in c633887

repo: cnnlabs/generator-cnn-base


text:
Update carousel picture ASAP

The carousel's first slide needs to use the following picture:

Katy requests this be completed with urgency. Thank you!
Resources

Figma design file: New carousel image

Updated the slide in PR #262

Amazing, thanks for the quick work @bhushankhope!

authors: bhushankhope libby-maier


text:
[Workload] Pods Per Node Scalability Test

Title: [Workload] Scalability test: Pods Per Node
Describe the solution you'd like

Kubernetes v1.22 can now handle up to 5000 nodes per cluster but best practice dictates there should be no more than 110 pods per node for your CNF.
https://kubernetes.io/docs/setup/best-practices/cluster-large/

Test Category Name

Scalability

Documentation tasks:

[ ] Update installation instructions if needed
[ ] Update Test Categories md if needed
[ ] Update USAGE md if needed

[ ] How to run
[ ] Description and details

[ ] What the best practice is
[ ] Why are we testing this

[ ] Remediation steps if test does not pass

QA tasks
Dev Review:

[ ] walk through A/C
[ ] do you get the expected result?
[ ] if yes,

[ ] move to Needs Peer Review column
[ ] create Pull Request and follow check list
[ ] Assign 1 or more people for peer review

[ ] if no, document what additional tasks will be needed

Peer review:

[ ] walk through A/C
[ ] do you get the expected result?
[ ] if yes,

[ ] move to Reviewer Approved column
[ ] Approve pull request

[ ] if no,

[ ] document what did not go as expected, including error messages and screenshots (if possible)
[ ] Add comment to pull request
[ ] request changes to pull request

@agentpoyo  is this issue still relevant for CNTI?

authors: agentpoyo lixuna

repo: cnti-testcatalog/testsuite


text:
how to access element in iframe that has no tag

i'd like to try the way ----with browser.get_iframe("**") as iframe:
but the iframe doesn't has a tag of id or name even index,how could i access the element in this kind of frame
i want to click the date 20160925,the source code is something like this:

thanks

closed in 0.11.0 release

authors: andrewsmedina aswwindkk

repo: cobrateam/splinter


text:
builtins: add parse and to_char_with_style variants for date types

PR: https://github.com/cockroachdb/cockroach/pull/68351
From release notes:

Implemented the parse_time and parse_timetz builtins, which parses a TIME or TIMETZ with immutable volatility. [#68351][#68351]

We probably don't need to document this built-in explicitly (it's included from the generated docs).

authors: ericharmeling jseldess

repo: cockroachdb/docs


text:
release-20.1: cli/zip: misc fixes

PR: https://github.com/cockroachdb/cockroach/pull/48094
From release notes:

The copy of system and crdb_internal tables extracted by cockroach debug zip is now written using the TSV format (inside the .zip file), instead of an ASCII-art table. [#48094][#48094] {% comment %}doc{% endcomment %}

Dup of https://github.com/cockroachdb/docs/issues/7417


text:
DOC-5851: Remove unnecessary redirects.

Fixes DOC-5851

This change is

I reviewed by looking 3 pages in the preview under /dev and they came up fine.


text:
Mesos tutorial

Fixes #507

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/48c5ddd2e2d18b7285856ba3034618ea5b8e6ecd/

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 7 unresolved discussions, some commit checks failed.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 19 at r1 (raw file):

### Requirements

- At this time, only CockroachDB v1.0.x is supported. Support for subsequent versions of CockroachDB is comming soon.

s/comming/coming

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 32 at r1 (raw file):

- The `cockroachdb` DC/OS service has been tested only on DC/OS versions 1.9 and 1.10.
- Accessing the CockroachDB Admin UI from inside or outside the DC/OS cluster is not possible at this time.

It is technically possible, it's just not easy. You don't have the change that part of the phrasing if you don't want, but I would ask that you remove the words "inside or" from this sentence, since it actually is easy to access the admin UI from inside the cluster (it's just usually not easy to run a web browser hooked up to your monitor from inside the cluster).

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 36 at r1 (raw file):

- Neither volume type nor volume size requirements may be changed after initial deployment.
- Rack placement and awareness are not supported at this time.
- Storage of backups, and restoring from backups, in datastores other than S3 is not yet supported.

Should we be more specific here? Enterprise backups can be stored/restored to/from anywhere they normally can be. It's just the DCOS-specific cockroach dump wrapper that only knows how to speak to AWS.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 106 at r1 (raw file):

    - A `vip` address, which is an HA-enabled hostname for accessing any of the instances. You'll use the `vip` address in the next step.

    In general, the `.mesos` endpoints will only work from within the same DC/OS cluster. From outside the cluster, you can either use the direct IPs or set up a proxy service that acts as a frontend to your CockroachDB instance. For development and testing purposes, you can use [DC/OS Tunnel](https://dcos.io/docs/latest/developing-services/tunnel/) to access services from outside the cluster, but this option is not suitable for production use.

Did you get the DC/OS Tunnel working? I'd expect that we could use it to access the admin UI, but never personally got it working so I didn't feel comfortable recommending it.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 224 at r1 (raw file):

### Restart a Node

You can restart a node while keeping it as its current location with its current persistent volume data. This may be thought of as similar to restarting a system process, but it also deletes any data that is not on a persistent volume.

s/keeping it as/keeping it at/

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 253 at r1 (raw file):

### Replace a Node

You can move a node to a new system and discard the persistent volumes at the prior system to be rebuilt at the new system. Nodes are not moved automatically, so this step must be performed performed, for example, before a system is offlined or when a system has already been offlined.

s/performed performed/performed/

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 344 at r1 (raw file):

By default, the AWS access and secret keys will be pulled from your environment via the `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` environment variables, respectively. You must either have these environment variables defined or specify the flags for the backup to work.

## Step 9. Stop the cluster

As loosely mentioned in our Slack DMs, we might want to also mention cleaning up the DC/OS cluster itself.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/7553d9ccc9e7e2fb368f56cd32ebf5cf92f47d6f/

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 19 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
s/comming/coming

Done.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 32 at r1 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
SSH tunneling is easier than running a browser inside the cluster. I did ssh -L 8123:cockroachdb-0-node-init.cockroachdb.mesos:8123 -t core@${PUBLIC_MESOS_NODE} and then accessed the UI at localhost:8123.

I didn't test this. I'll spin up another cluster, test it, and if it works well, add it as another"Monitor the cluster" step or something.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 36 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
Should we be more specific here? Enterprise backups can be stored/restored to/from anywhere they normally can be. It's just the DCOS-specific cockroach dump wrapper that only knows how to speak to AWS.

Removed this bullet and added more detail to the backup/restore section. PTAL.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 106 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
Did you get the DC/OS Tunnel working? I'd expect that we could use it to access the admin UI, but never personally got it working so I didn't feel comfortable recommending it.

I'll test and document.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 224 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
s/keeping it as/keeping it at/

Done.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 253 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
s/performed performed/performed/

Done.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 344 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
As loosely mentioned in our Slack DMs, we might want to also mention cleaning up the DC/OS cluster itself.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f5799621da7d233fa660304d8d2eb8c7768c04a0/

 pending the couple UI-related comments

Review status: 5 of 6 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 32 at r1 (raw file):
Previously, jseldess wrote…
I didn't test this. I'll spin up another cluster, test it, and if it works well, add it as another"Monitor the cluster" step or something.

👍

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 32 at r1 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
👍

Wohoo. Got it work. PTAL.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8bb1c76a52b45cd1c8ac7a76084b1b8598fab485/

Nice! Just a couple small comments on the UI bits, otherwise this is good to go

Review status: 5 of 6 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 181 at r3 (raw file):

    ~~~

3. Discover the http endpoints for your CockroachDB cluster:

This step isn't technically needed since it's always going to be the same address -- we could just tell people to directly go to http.cockroachdb.l4lb.thisdcos.directory.mydcos.directory. Your call on whatever you think is nicer.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 204 at r3 (raw file):

    ~~~

3. In a browser, go to the `vip` address with `.mydcos.directory` appended before the `:80` port, e.g., `http.cockroachdb.l4lb.thisdcos.directory.mydcos.directory:80`.

s/3/4/, unless you remove the step above
Also, the :80 isn't needed.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 181 at r3 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
This step isn't technically needed since it's always going to be the same address -- we could just tell people to directly go to http.cockroachdb.l4lb.thisdcos.directory.mydcos.directory. Your call on whatever you think is nicer.

Done.

v1.0/orchestrate-cockroachdb-with-mesosphere-insecure.md, line 204 at r3 (raw file):
Previously, a-robinson (Alex Robinson) wrote…
s/3/4/, unless you remove the step above
Also, the :80 isn't needed.

Done.

Comments from Reviewable

TFTR, @a-robinson!

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/2595a02c9afb22d43b49e8fd3a8c58a8f709e0d5/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d6877e900925990165f8124ce568b243c64abe3d/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/468b2f498e8b40c44ab7010232b82e94448443df/

authors: a-robinson cockroach-teamcity jseldess


text:
Not receiving connection lost event when Vector is turned off

I am not receiving connection lost events when Vector is turned off, or powers himself off (eg when he is stuck/lost and his battery gets low).
I think the fix would be to add timers to the event stream handler, control response handler, and camera handler.  When a new event occurs there, it resets the timer.  When the timer expires, it would then raise a lost connection event, lost control event, etc.
This looks like it could interact with several other parts of the assembly.  So I thought it would be best to bring it up as an issue first, before making changes in lots places.  What would your prefer design be?
Thank-you and have a great day!

Hello Randy,
I just published a fix for this to the current branch.  The previous logic was any loss of the event stream was considered a disconnect and would shut everything down.  Unfortunately, as you noticed, when Vector is powered off there is no gPRC notification to shut down the streams.
I added a 5 second timeout to the event stream to trigger the stream shutdown as well as a flag to indicate that this is a connection loss disconnect.  This was necessary because a normal disconnect does a bunch of calls to Vector to properly shut everything down and that's not possible if he's been powered off.
I've tested it and it works well (my poor Vector has been rebooted so many times).  Grab the latest commit and you should be good to go.


text:
Fail to Authorize API Key

I cannot authorize my API keys after copying them from my obsidian vault.

Seems like I have two vaults on my laptop and the port conflicts. I changed the port and things work now.

repo: coddingtonbear/obsidian-local-rest-api