owner 0x907a04ad5ac49acde9e197ae1f1c66b94250fcc6, add and remove is same

Related Safe Addresses
0x12f6ea48da5edd60ec6077c7657109c92e908625
0xeef205db9196ebdb5b2c653df0ca4db401784531
0x1aabccae98e1c34625bebeee7c980577410cdf61
0x2a509d75f0d06b84578f230faa953f6062262ce9
0x3197b70753cdf1940afba9b302907549fe3af260
0x3fafb386b1b7a3857085096c0926bdf65bb1e584
0x42c8e7baacca2e7697edd89b148bda7726fe7862
0x4ce426850f2fd04f44dd16ced2e9851c2abc4b12
0x62b5a2e429441032e1e76a3f59183a999fe25148
0x6a7de36e5d5e010a7bfa60718516f7b54611890d
0x6ff5ee43ee9d7878acb1d22818921a21d82c8bb5
0x71d1e3e46336328e0b01c7514377f0795f504aa0
0x77502b6db9656be39099f7dc7b86097a3c626da7
0x864fe78f21ccf839d555aa567e030d4c1ac21792
0xae331114cf1e9679632e5cb25c69310e7b63f0f9
0xb5cbfacb1e628e48ec54940c29e0c08e97fd4200
0xb62d7df9e8e0b0495a328a6397d2d083ddbbaac9
0xc36c385e454e5bb86cdbdd2bf805c4c82459788c
0xca4f5cf31b890e3a24ec061878980c63c5296c1b
0xd284b2bdfe1a7636f5d540ed46f7bbdf5c82b3d4
0xe8e5e5db490e2bf4407017588b1927432e4a677b

Reasoning

There is an abnormal behavior that is understandable 🍄

However, if there are many abnormal behaviors, then there is enough reason to determine that these addresses are airdrop farmer.

All of them the owner is same 0x907a04ad5ac49acde9e197ae1f1c66b94250fcc6, only this address

All of the multi-sign address, the behaviour is always same and stange .

All their addOnwer and removeOwner transaction took place from 2021-05-27 to 2021-06-23. (50% happend in 2021/06/23 one day)

All of them execute 1 transactions, add owner and remove owner in 1 tx, always the same tx.

Add owner address is always 0x907a04ad5ac49acde9e197ae1f1c66b94250fcc6 , remove owner address is always 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D

Please Check Table

Address -- multi-sign address
Execute transactions -- The number of execute transactions by multi-sign address
AddOwnerTxAmount -- The number of add owner
AddOwnerAddress -- The Address of add owner
AddOwnerTx -- The tx of add owner
AddOwnerDate -- The date of add owner
RemoveOwnerTxAmount -- The number of remove owner
RemoveOwnerAddress -- The Address of remove owner
RemoveOwerTx -- The tx of remove owner
RemoveOwerDate -- The date of remove owner

Address
Execute transactions
AddOwnerTxAmount
AddOwnerAddress
AddOwnerTx
AddOwnerDate
RemoveOwnerTxAmount
RemoveOwnerAddress
RemoveOwerTx
RemoveOwerDate

0x12f6ea48da5edd60ec6077c7657109c92e908625
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xf5235cf11c8518bbcba3568a4228e0f5a4d095d214bbcac2b833080955d4eb99
2021/06/02T22:11:59.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xf5235cf11c8518bbcba3568a4228e0f5a4d095d214bbcac2b833080955d4eb99
2021/06/02T22:11:59.000Z

0xeef205db9196ebdb5b2c653df0ca4db401784531
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x91c2a9d70a780d30beaf0655f48f4a9a08880d73f4b70ba94e179d8dd082c046
2021/06/23T01:52:01.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x91c2a9d70a780d30beaf0655f48f4a9a08880d73f4b70ba94e179d8dd082c046
2021/06/23T01:52:01.000Z

0x1aabccae98e1c34625bebeee7c980577410cdf61
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x7e21f98c55804dbdf723fa901f79384f79427f49a1d5fd0abc223100a38e0c84
2021/06/23T02:41:36.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x7e21f98c55804dbdf723fa901f79384f79427f49a1d5fd0abc223100a38e0c84
2021/06/23T02:41:36.000Z

0x2a509d75f0d06b84578f230faa953f6062262ce9
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x1e21b2abf80ead56998b9cc369075b1f04d355976b04a424d41538feb0233641
2021/06/01T16:33:31.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x1e21b2abf80ead56998b9cc369075b1f04d355976b04a424d41538feb0233641
2021/06/01T16:33:31.000Z

0x3197b70753cdf1940afba9b302907549fe3af260
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x62cc210be74c54dba3fa5e8cc7bc118d991d8ffb8eb306c4baf5f85e1dc7d0a4
2021/06/23T01:47:57.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x62cc210be74c54dba3fa5e8cc7bc118d991d8ffb8eb306c4baf5f85e1dc7d0a4
2021/06/23T01:47:57.000Z

0x3fafb386b1b7a3857085096c0926bdf65bb1e584
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xf75cac88d5af99a0f0ebde6fb4b661c4a4282d16fda69e0c4d418589dbd157fd
2021/06/23T03:12:18.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xf75cac88d5af99a0f0ebde6fb4b661c4a4282d16fda69e0c4d418589dbd157fd
2021/06/23T03:12:18.000Z

0x42c8e7baacca2e7697edd89b148bda7726fe7862
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x185a6f0d5f48a3a8dec4102caa98f9f71f1205ad1cae805011bc6b5a332ef861
2021/06/23T03:22:55.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x185a6f0d5f48a3a8dec4102caa98f9f71f1205ad1cae805011bc6b5a332ef861
2021/06/23T03:22:55.000Z

0x4ce426850f2fd04f44dd16ced2e9851c2abc4b12
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x61e016141c5ef4d39212056c46a23c5a6ea279c62c3a8c82c8a4494498f81f22
2021/06/08T21:46:53.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x61e016141c5ef4d39212056c46a23c5a6ea279c62c3a8c82c8a4494498f81f22
2021/06/08T21:46:53.000Z

0x62b5a2e429441032e1e76a3f59183a999fe25148
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x642575c00e12adfd3eb85ba339aa036e3a53ee5150453236a140bfa32c315ada
2021/06/23T02:13:03.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x642575c00e12adfd3eb85ba339aa036e3a53ee5150453236a140bfa32c315ada
2021/06/23T02:13:03.000Z

0x6a7de36e5d5e010a7bfa60718516f7b54611890d
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x52a0aeae9289ae4fe44824b0d694da2a10f4be9768f7135d9f470b5aeab369c3
2021/06/23T02:48:15.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x52a0aeae9289ae4fe44824b0d694da2a10f4be9768f7135d9f470b5aeab369c3
2021/06/23T02:48:15.000Z

0x6ff5ee43ee9d7878acb1d22818921a21d82c8bb5
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xd641d3cfdb00baf65bd55dc4dcd6a78f2db20b6559a0dc4d493ac7c8faef4758
2021/06/08T17:58:26.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xd641d3cfdb00baf65bd55dc4dcd6a78f2db20b6559a0dc4d493ac7c8faef4758
2021/06/08T17:58:26.000Z

0x71d1e3e46336328e0b01c7514377f0795f504aa0
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xa41f4076ab5f10bdf8037c9febf35a8ebca32e429b9a7ec78376341876a90774
2021/06/23T01:54:18.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xa41f4076ab5f10bdf8037c9febf35a8ebca32e429b9a7ec78376341876a90774
2021/06/23T01:54:18.000Z

0x77502b6db9656be39099f7dc7b86097a3c626da7
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xa7ccbc4b85a37dc819eedbe1f4ae24034036f52ed07618385fb11710ff21a301
2021/06/23T02:59:45.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xa7ccbc4b85a37dc819eedbe1f4ae24034036f52ed07618385fb11710ff21a301
2021/06/23T02:59:45.000Z

0x864fe78f21ccf839d555aa567e030d4c1ac21792
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x96a37e72803dbe255f83b70e62d7b296c42bf4f43e866f457ab3a59250d7cc98
2021/06/23T03:40:51.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x96a37e72803dbe255f83b70e62d7b296c42bf4f43e866f457ab3a59250d7cc98
2021/06/23T03:40:51.000Z

0xae331114cf1e9679632e5cb25c69310e7b63f0f9
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xf788e7947644d7b23fa3067dc37ee4b81001bdfcdf4447b14f30588df151410b
2021/06/08T20:33:57.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xf788e7947644d7b23fa3067dc37ee4b81001bdfcdf4447b14f30588df151410b
2021/06/08T20:33:57.000Z

0xb5cbfacb1e628e48ec54940c29e0c08e97fd4200
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x4aece49342cb58c388f557ebd80355e323c1f0b8edf8035569919eb6718f9ada
2021/06/08T20:24:35.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x4aece49342cb58c388f557ebd80355e323c1f0b8edf8035569919eb6718f9ada
2021/06/08T20:24:35.000Z

0xb62d7df9e8e0b0495a328a6397d2d083ddbbaac9
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x0397dbb01f011533f87f0eaa6b376077c0c92265ed3fcaba9c993ccae8979d04
2021/06/01T16:44:59.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x0397dbb01f011533f87f0eaa6b376077c0c92265ed3fcaba9c993ccae8979d04
2021/06/01T16:44:59.000Z

0xc36c385e454e5bb86cdbdd2bf805c4c82459788c
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x05c0cc0872d242924abc3f94fc600ccc5446149c7d68aefb49a1e98b4c7d1eee
2021/06/08T18:33:44.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x05c0cc0872d242924abc3f94fc600ccc5446149c7d68aefb49a1e98b4c7d1eee
2021/06/08T18:33:44.000Z

0xca4f5cf31b890e3a24ec061878980c63c5296c1b
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x54270711abf6592897a592ec4b3d51b8f5259e8f629e8dfff9c2bc0ae779aa17
2021/06/23T02:44:04.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x54270711abf6592897a592ec4b3d51b8f5259e8f629e8dfff9c2bc0ae779aa17
2021/06/23T02:44:04.000Z

0xd284b2bdfe1a7636f5d540ed46f7bbdf5c82b3d4
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0xcd4318efc75f472cd0700cc964c723387f263fa8b29d979f8423e48f4430925a
2021/06/08T04:06:35.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0xcd4318efc75f472cd0700cc964c723387f263fa8b29d979f8423e48f4430925a
2021/06/08T04:06:35.000Z

0xe8e5e5db490e2bf4407017588b1927432e4a677b
1
1
0x907a04ad5aC49acDE9E197ae1f1C66b94250fcC6
https://etherscan.io/tx/0x98a3f444c9f6faa1ca44979ec30f3de86ed8d77150edecf10aa927b2926cc089
2021/05/27T17:00:14.000Z
1
0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
https://etherscan.io/tx/0x98a3f444c9f6faa1ca44979ec30f3de86ed8d77150edecf10aa927b2926cc089
2021/05/27T17:00:14.000Z

Methodology
Addresses are reported by retrieving information from the chain, using bitquery's graphql, and detecting abnormal behavior, such as empty wallets, mutual transfers, etc.
When only some of the anomalous behaviors are present, we can consider the address reasonable, but when an address has all the anomalous behaviors, we have good reason to suspect that the address is false. Especially if the multi-signature address and the owner address have obvious exceptions both, then it is obvious that this is airdrop farmer.
Abnormal behaviors include

For Multi-Sign Address

Few transactions were executed
There is a lot of overlap in the interactions, such as the destination address, and the time
The owner of multiple multi-signature addresses is exactly the same, and never changes from start to finish

For Owner Address

Empty address
The first source of funds is the owner.
Mutual transfer
Behavior similarity

If the verification is passed and  my strategy is great,  I can provide my source code, but for now it is not conveninet
Safe Address
0xce495858e36c95f491b5a32ca2664405cf10ab76
Thanks

Thanks for the report. All of these Safes have been found by a previous report, unfortunately.


fly execute sometimes has weird curl errors

the ^C is from me in this one:
$ fly -t prod execute -c ci/tasks/test-unit.yml
executing build 26421
curl: res_query.c:252: __libc_res_nquery: Assertion `hp != hp2' failed.
gunzip: invalid magic
tar: short read
Aborted
exit status 1
failed
^C
aborting...
upload request failed: Put https://main.bosh-ci.cf-app.com/api/v1/pipes/9f6eb951-5093-4ad6-4909-92acf45283fa: EOF

i can only assume this has something to do with harry potter, but i double checked and my hp is definitely set to the sorcerer's stone
this one ran fine, i think, but still printed out this error:
$ fly -t prod execute -c ci/tasks/test-unit.yml
executing build 26419
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3090k    0 3090k    0     0   376k      0 --:--:--  0:00:08 --:--:--  366kcurl: (23) Failed writing body (2048 != 6144)

I don't know what I've done to trigger these, other than running fly execute a couple times on possibly shitty wifi.

It's been long enough and there's been enough revving of the archive resource that I'm not really sure if this is an issue anymore, let alone whether we could reproduce it in the first place. Gonna just close - you can reopen if you're still seeing it.

I'm experiencing similar issues:
❯ fly -t foo execute -c build.yml
executing build 511
upload request failed: Put /api/v1/pipes/08119154-33f2-409c-5b1f-7b394c76bb4d: unsupported protocol scheme ""
curl: (3) <url> malformed
gzip: invalid magic
tar: Child returned status 1
tar: Error is not recoverable: exiting now
exit status 2
failed

@nicosuave Make sure you've configured an external URL on your web node.

Thanks @vito

I have the same issue too. I followed all the steps on https://concourse.ci/flight-school.html, but on running fly -t ci execute -c build.yml, I get
executing build 28
upload request failed: Put /api/v1/pipes/86853548-1d47-4181-69bd-27566f349d82: unsupported protocol scheme ""
curl: (3) <url> malformed
gzip: invalid magic
tar: Child returned status 1
tar: Error is not recoverable: exiting now
exit status 2
failed

I've confirmed that my docker-compose concourse-web has the right CONCOURSE_EXTERNAL_URL set up.

@G2Jose Your CONCOURSE_EXTERNAL_URL needs http:// in front of it. There should be validations for that already. Hmm.

That fixed it for me, thanks @vito!

That fixed it for me, thanks @vito!

Apparently still a problem --  CONCOURSE_EXTERNAL_URL  does not seem to be validated. This fix worked for me. Thanks.
(I installed via  https://concourse.ci/docker-repository.html today)


Add findNext, findPrev actions

Summary of the Pull Request
This PR is a resurrection of #8522. @Hegunumo has apparently deleted their account, but the contribution was still valuable. I'm just here to get it across the finish line.
This PR adds new action for navigating to the next & previous search results. These actions are unbound by default. These actions can be used from directly within the search dialog also, to immediately navigate the results.
Furthermore, if you have a search started, and close the search box, then press this keybinding, it will still perform the search. So you can just hit F3 repeatedly with the dialog closed to keep searching new results. Neat!

References

Moved from #8522

PR Checklist

[x] Closes #7695
[x] I work here
[ ] Tests added/passed
[ ] Needs docs

Detailed Description of the Pull Request / Additional comments
One weird trick to double your money:
If you dispatch the action on the key down, then dismiss a selection on a key up, we'll end up immediately destroying the selection when you release the bound key. That's annoying. It also bothers @carlos-zamora in #3758. However, I think we can just only dismiss the selection on a key up. I think that's fine. It seems fine so far. We've got an entire release cycle to futz with it.
Validation Steps Performed
I've played with it all day and it seems crisp.
Co-authored-by: Kiminori Kaburagi<EMAIL_ADDRESS>

Don't forget to update the docs plz


Background sounds

After jailbreaking enabling background sounds through control centre accessibility shortcut no longer works

i have the same issue

https://cdn.discordapp.com/attachments/798438847305220178/1105356716180242534/RPReplay_Final1683607949.mov
No issues here so it must be a tweak issue.


[Feature Request] Column default values for Delta Lake

Feature request
Overview
This is a proposal to support column default values for Delta Lake tables.
Users should be able to associate default values with Delta Lake columns at table creation time or thereafter.
Motivation
Support for column defaults is a key requirement to facilitate updating the  table schema over time and performing  DML operations on wide tables with sparse data.
Further details
Please refer to an open design doc here.
This should integrate with Apache Spark's column default feature, and also represent the column metadata in a general way such that other Delta Lake clients can understand it.

Users must be able to CREATE and and ALTER tables to assign non-NULL default values to columns.
The system should support defaults of NULL, literals, or constant expressions based on built-in functions.
The system should support omitting columns from explicit column lists in INSERT commands and MERGE INSERT actions.
The system should support DEFAULT can be specified in VALUES lists and top-level SELECT queries when used in an INSERT command or MERGE INSERT action.
DESCRIBE commands should show default column values if requested.

For example:
-- The CREATE TABLE statement may specify a DEFAULT value for a column.
CREATE TABLE T (a INT, c STRING DEFAULT CONCAT(‘abc’, ‘def’))
  USING DELTA;
INSERT INTO T(a) VALUES (42);
INSERT INTO T VALUES (43, DEFAULT);
SELECT * FROM T;
(42, ‘abcdef’)
(43, ‘abcdef’)

Willingness to contribute
The Delta Lake Community encourages new feature contributions. Would you or another member of your organization be willing to contribute an implementation of this feature?

[X] Yes. I can contribute this feature independently.
[ ] Yes. I would be willing to contribute this feature with guidance from the Delta Lake community.
[ ] No. I cannot contribute this feature at this time.

I can't add comments to the doc.
Could you please add an example of metadata in the Delta Log?

@felipepessoto Thanks for joining the thread, I will add some examples. (The only way I was able to share the doc for now is by publishing it to the web as read-only, please feel free to make comments here.)
I am preparing a protocol doc change as well as the first pull request :) I can add you to the reviewers if you prefer.

Yeah, I added some comments to #2240
Thanks!

BTW I found that Google docs allows to share it in two different ways. To be able to Print/Download and optionally add comments permission you need to use this:

This is done.

Using create table statement to set default literal for columns along with not null and comment, I still get error.
Create table table_name(
columnA STRING NOT NULL default '000' comment 'sadhksjhd',
[WRONG_COLUMN_DEFAULTS_FOR_DELTA_FEATURE_NOT_ENABLED] Failed to execute CREATE TABLE command because it assigned a column DEFAULT value,
but the corresponding table feature was not enabled. Please retry the command again
after executing ALTER TABLE tableName SET
TBLPROPERTIES('delta.feature.allowColumnDefaults' = 'supported').


[New Source Plugin] Empty folders added to package manifest, "of type AuraDefinitionBundle was named in package.xml, but was not found in zipped directory"

Summary
I'm getting several "An object '[Component name]' of type AuraDefinitionBundle was named in package.xml, but was not found in zipped directory" errors in my deployment while using the new Source Plugin.
I'm not sure why this one is happening but when I try and deploy my Aura and LWC components only, -m LightningComponentBundle,AuraDefinitionBundle, some of the Aura components seem to not be included in the deployed ZIP, the components that don't make it seem to change a bit between deployments but a large selection of them seem to be alphabetical, but not 100% in any failed deployment. Maybe file access limitations? I have used the SFDX_MDAPI_TEMP_DIR env var to confirm that the component files are extracted into the staging directory but I haven't been able to inspect the actual submitted ZIP file. I thought I could pull these out of the temp directory but I'm not seeing them.
Steps To Reproduce:
I'm not sure how to replicate this outside of my code base. Maybe I could try and create lots and lots of components and push them all together? (I have 607 Aura and 430 LWC components as of this testing)
Expected result
Components should have deployed successfully.
Actual result
Deployment fails with random failures.
System Information
{
"cliVersion": "sfdx-cli/7.110.0",
"architecture": "win32-x64",
"nodeVersion": "node-v14.17.3",
"pluginVersions": [
"@oclif/plugin-autocomplete 0.3.0 (core)",
"@oclif/plugin-commands 1.3.0 (core)",
"@oclif/plugin-help 3.2.2 (core)",
"@oclif/plugin-not-found 1.2.4 (core)",
"@oclif/plugin-plugins 1.10.0 (core)",
"@oclif/plugin-update 1.4.0-3 (core)",
"@oclif/plugin-warn-if-update-available 1.7.0 (core)",
"@oclif/plugin-which 1.0.3 (core)",
"@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
"@salesforce/sfdx-trust 3.6.0 (core)",
"alias 1.1.10 (core)",
"apex 0.2.2 (core)",
"auth 1.7.1 (core)",
"config 1.2.13 (core)",
"custom-metadata 1.0.12 (core)",
"data 0.5.2 (core)",
"generator 1.1.7 (core)",
"limits 1.2.1 (core)",
"org 1.6.7 (core)",
"salesforce-alm 52.1.0 (core)",
"schema 1.0.8 (core)",
"sfdx-cli 7.110.0 (core)",
"sfdx-devops 0.4.3",
"sfdx-heber 0.0.2",
"sfdx-typegen 0.6.2",
"sfpowerkit 3.1.6",
"shane-sfdx-plugins 4.43.0",
"?????? @mshanemc/plugin-streaming 1.1.7",
"?????? @mshanemc/sfdx-sosl 1.1.0",
"source 1.0.3",
"telemetry 1.2.2 (core)",
"templates 52.1.0 (core)",
"user 1.3.1 (core)"
],
"osVersion": "Windows_NT 10.0.19042"
}

Hi @aheber - I tried to reproduce this using the ebikes_lwc repo but it worked as expected.  I'm using v1.0.6 of the source plugin which is the latest release published several hours ago.  I'm on a mac but will try on windows.
The plan is to bundle this version of the source plugin with the CLI release candidate today.  Your issue has me concerned though.  There isn't much debug output from the SDR library but you can try enabling it with the deploy command.  SDR does not write the zip to the file system so it would just be the list of files in the temp dir.

@shetzel I just test with the v1.0.6 version, same problem. I just tested against an existing org instead of creating a new org that didn't hold the components yet. This let me separate the Aura and LWC components into separate deployments. Just deploying the Aura Components caused the same error.
I'll do some digging and see if I can get a reproduction available outside of my source repo. It could certainly be a Windows thing, I can test on my mac too.
If there are other specific tests worth running for details I'm happy to give them a try. Let me know.

OK, first my apologies. This looked like something else and I crossed names of things when evaluating the results so it was a bit of a goose chase. I have an old component with a name incredibly similar to a new component and I evaluated that for being present incorrectly. The changes in components present and missing can be attributes to changing branches between tests as I was letting things run while working on other tasks.
The problem is empty folders. Where we've deleted a component (at least Aura or LWC in my testing) GIT will remove the files but leave the folders around. SDR is seeing the folder and adding it to the manifest but it isn't coming through to the ZIP file so the deployment is getting confused.
Repro here: https://github.com/aheber/sourcePluginBreak-1099
The repro should work  and should have two components of each type, one populated and one "empty" (.forceignore to make GIT persist the folder). Should cause the failure.

@shetzel (forgot to mention you)

Thanks for the repro @aheber.  We'll work on a fix unless you beat us to it.  :)

Hi @aheber just to confirm, you see this issue when you have an empty directory under force-app/main/default/lwc in your posted repo I should delete withOutContent/.forceignore and then attempt the deploy.
how come you have to add the .forceignore so that "GIT persist the folder" but "GIT will remove the files but leave the folders around" why is GIT leaving an empty folder in your demo, but not in your real project?

@WillieRuemmele, Git source tracking doesn't care about folders, it only manages them enough to create them to place files there.
On my local machine, I have legacy folders from deleted components. Either created and deleted "locally" and never committed or deleted via source tracking changes from another user, and Git never removed the associated folders on my machine. Because I've had this source folder active on my machine for several years I have a variety of of these folders that I haven't yet manually cleaned up and that source tracking doesn't care about. They have never been a problem until now.
I had to add the .forceignore files to my example repo because Git wouldn't have committed the folders because it only tracks files. I had to create a file at that directory so that Git would force the folder to be created because Git won't track or create "empty" folders.
Hope that helps explain why these folders exist.

@shetzel thanks! I don't think I'll have time this week so I don't know if I'll beat you do it. I haven't dug through the source on that repo yet to get my bearings. If it hangs around longer I'll likely try my hand at it.

I should also add to the Git convo, maybe there is a totally reasonable way to manage these empty folders with a Git config or something that I don't have turned on but I haven't ever come across it. Education welcome :)

I think the PRs associated with this issue resolved everything we saw.  If not, please response with whatever is still wrong.

Yes, I believe it is all resolved now.


Agent 2 value function not learned?

Here's another bug I found. out_lookahead receives trainstate_val2_copy.params rather than the argument trainstate_val2_copy_params that the containing function is being differentiated with respect to. As a consequence I think agent 2's value function is not being trained at all.
The analogous code for agent 1 (line 961) does not have this issue.
https://github.com/Silent-Zebra/POLA/blob/6b07e89317b07d91216db9d02c1f915f9313b66a/jax_files/POLA_dice_jax.py#L1061

Thanks for pointing this out! I really need to use more different variable names that are less likely to lead to such mistakes in the future. I guess the coin game is nice because the rewards tend to be close-ish to 0 (especially at the start with close to random policies) so the value function doesn't matter that much. This probably explains why the method still mostly works. Fixing this should improve performance specifically for agent 2.

It might matter more than you think. If the value function were used as just a REINFORCE baseline then I would agree that it won't matter much. However it is used in the advantage as a proxy for the return, so agent 2 is optimizing a nonsensical objective.

Closing as fixes have been implemented and experiments rerun (see updated readme)


python311Packages.ttp-templates: 0.3.4 -> 0.3.5

Diff: https://github.com/dmulyalin/ttp_templates/compare/refs/tags/0.3.4...0.3.5
Changelog: https://github.com/dmulyalin/ttp_templates/releases/tag/0.3.5
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
23.05 Release Notes (or backporting 22.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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 228041 run on x86_64-linux 1

4 packages failed to build:

python310Packages.pytest-ansible
python310Packages.pytest-ansible.dist
python311Packages.pytest-ansible
python311Packages.pytest-ansible.dist

42 packages built:

ansible (python310Packages.ansible-core)
ansible-later (python310Packages.ansible-later)
ansible-later.dist (python310Packages.ansible-later.dist)
ansible-lint (python310Packages.ansible-lint)
ansible-lint.dist (python310Packages.ansible-lint.dist)
ansible.dist (python310Packages.ansible-core.dist)
ansible_2_12
ansible_2_12.dist
ansible_2_13
ansible_2_13.dist
kargo
kargo.dist
python310Packages.ansible
python310Packages.ansible-compat
python310Packages.ansible-compat.dist
python310Packages.ansible-kernel
python310Packages.ansible-kernel.dist
python310Packages.ansible-runner
python310Packages.ansible-runner.dist
python310Packages.ansible.dist
ttp (python310Packages.ttp)
python310Packages.ttp-templates
python310Packages.ttp-templates.dist
ttp.dist (python310Packages.ttp.dist)
python311Packages.ansible
python311Packages.ansible-compat
python311Packages.ansible-compat.dist
python311Packages.ansible-core
python311Packages.ansible-core.dist
python311Packages.ansible-kernel
python311Packages.ansible-kernel.dist
python311Packages.ansible-later
python311Packages.ansible-later.dist
python311Packages.ansible-lint
python311Packages.ansible-lint.dist
python311Packages.ansible-runner
python311Packages.ansible-runner.dist
python311Packages.ansible.dist
python311Packages.ttp
python311Packages.ttp-templates
python311Packages.ttp-templates.dist
python311Packages.ttp.dist


Option for force Content-Disposition: attachment to inline

Related to: https://github.com/Webconverger/webc/issues/157
In our Firefox powered kiosk browser OS (Webconverger) we disable downloads. However sometimes pages of PDFs are (erroneously) marked up with Content-Disposition: attachment, instead of inline. We need a way to override to inline in order to show that PDF instead of downloading (silently ignore) it.
Here is a good example:
http://www.justice.govt.nz/courts/maori-land-court/documents/applications/Form_05_NTC_APPEAR.pdf/view
Of a typical link in the Plone CMS that's Content-Disposition: attachment, when it ideally should be inline, so that users can view the PDF.

@yurydelendik since Firefox Quantum is out, the add-on you linked to does neither allow installation nor work at all with the latest Firefox.
So, what about a change in pdf.js now?

[...] the add-on you linked to does neither allow installation nor work at all with the latest Firefox.

You could try e.g. https://addons.mozilla.org/en-US/firefox/addon/display-inline/, which is a WebExtension that in my limited testing seem to work just fine for this purpose.

Works like a charm - thank you so much! 👍


Set up sauce test runner

Work in progress. Same issues as https://github.com/jashkenas/underscore/pull/2059 + the token isn't currently encrypted. I'll regenerate and encrypted it when travis stops being silly

[ ] run tests on IE6,7,8 (currently unsupported by Karma)
[ ] clean up the travis file (develop a karma plugin to limit how many browsers they start at a single time, they have no interest in limiting based on IRC chats)

DO NOT MERGE WITHOUT GREEN LIGHTS

Android 4.0.4 died in /push. Restart?

Looks like that did it


CFE error with Mixed library and mixins

Although I don't see analyzer error I get the following error by running bin/dart b.dart :
packages/flutter/lib/src/b.dart:3:7: Error: 'A<int>' doesn't implement 'A<int>' so it can't be used with 'M<int>'.
 - 'A' is from 'package:flutter/src/a.dart' ('packages/flutter/lib/src/a.dart').
 - 'M' is from 'package:flutter/src/b.dart' ('packages/flutter/lib/src/b.dart').

with the following code:
//--------a.dart
// @dart = 2.8
abstract class A<T> {}

//--------b.dart
import 'a.dart';
mixin M<T> on A<T> {}
class B extends A<int> with M {}
void main(){}

Dart SDK version: 2.9.0-21.0.dev.flutter-84e5eeaea4 (be) (Tue Jul 21 07:45:44 2020 +0000) on "linux_x64"

/cc @johnniwinther @leafpetersen

A fix is in progress: https://dart-review.googlesource.com/c/sdk/+/155444


Autoplay not works.

Hi!,I have tried to enable autoplay..But it's not work
Can anyone help me solved this..
Link: http://5th-angle.esy.es/dfp-mat/test-autoplay.php
Best,
Imesh

I saw you posted in #53 as well so I'm going to close this and we can continue the conversation there :)


Some songs are not playing.

Hi Jigyasu.  Awesome project,

Hi @Klozer-app, Thank you 😊 Can u specify the problems happening or the extension of the file which are not playing. By the way, I suppose this issue is for Wavy Beats. So please open it [here](


Output is too verbose in CI

Is your feature request related to a problem? Please describe.
I have created a CI/CD process to sync documents automatically to confluence and everything works fine except that the tool is logging a lot and finding issues can become a problem.
I am using dry run in CI and the full sync in CD.
A clear and concise description of what the problem is and what the feature provides.
I tried to find a switch/flag in the CLI but was not able to do it.
Ideally, the dry run should allow for less verbose logging or log only if something is problematic.

@kovetskiy Hey, do you feel we could introduce some form of verbose flag? Or handle logging somehow else?


model.score() returns MSE but the docstring states that it returns R2

In dask_ml linear_models LinearRegression. If you use model.score(X_test, y_test) then you get back the Mean Squared Error instead of the R2 which is how sklearn's implementation does it.
On top of that the score method defined has a docstring that states that it returns the r2 score instead of the MSE.
We can see in the code here https://github.com/dask/dask-ml/blob/e1b21e6dbcfae8341d05d39544ab90dce21fdb2b/dask_ml/linear_model/glm.py#L304-L328
That the docstring says r2 score, but the method returns the mean_squared_error from dask_ml.utils.
Either the docstring should be changed to reflect the real return value. Or the r2_score method should be defined and then use that on the rerturn statement of the score method

Or the r2_score method should be defined and then use that on the rerturn statement of the score method

That sounds best to me. We have dask_ml.metrics.r2_score, so we should be able to fix this relatively easily. Are you interested in working on it?

@TomAugspurger the thing is that dask_ml.metrics.mean_squared_erroris not being used here, it comes from dask-gml where there is currently no r2_score method to switch with, would that require adding it there or is it possible to just use dask_ml.metrics.r2_score?

The linear model was implemented 2 years ago and dask_ml metrics was implemented a year ago. So I'm guessing that's the reason why it's using dask-gml instead of the dask_ml.metrics
I would assume that it would be better to start using dask_ml.metrics in the different models instead.
This could also raise the issue of going through the different model and implementing dask_ml.metrics instead of dask_glm.utils
@TomAugspurger what do you think ?

or is it possible to just use dask_ml.metrics.r2_score?

As you said, I think it should be enough to replace dask_glm.utils.mean_squared_error with dask_ml.metrics.r2_score, even if they don't come from the same package.

This could also raise the issue of going through the different model and implementing dask_ml.metrics instead of dask_glm.utils

Yes, I think that's best.

I can take care of this in the coming days @TomAugspurger. Should be simple enough to import and change the return statement. I can create a different issue for other dask-glm imports that could be changed to dask_ml.


Add eraser and brush size to VR and erase all to both

The UI for both modes is obviously a mess but the functionality is there.

Good job! Thanks for the hard work!
I noticed some problems with the environment when using an Oculus Quest. Removing debug="false" helped.

Nice! :star2:


[youtube] fixed --flat-playlist always showing uploader as none

Please follow the guide below

You will be asked some questions, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your pull request (like that [x])
Use Preview tab to see how your pull request will actually look like

Before submitting a pull request make sure you have:

[x] Searched the bugtracker for similar pull requests
[x] Read adding new extractor tutorial
[x] Read youtube-dl coding conventions and adjusted the code to meet them
[x] Covered the code with tests (note that PRs without tests will be REJECTED)
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
running:
youtube-dl --flat-playlist -j YOUTUBE_PLAYLIST_URL

prior to the bugfix would always have "uploader": none in each playlist item. post fix the proper uploader will appear in said field

Hey, thanks for your PR! Please prefix your commit message (and PR title) with [youtube] to indicate that it's about the youtube IE.

Hey, thanks for your PR! Please prefix your commit message (and PR title) with [youtube] to indicate that it's about the youtube IE.

woops sorry, updated.

got rid of the extra 2 commits i accidentally created when attempting to rename the commit

Add test.


add a login system

it might only use in_memory provider to be easy to test

there is 2 login systems : sf based and vuejs based, but they don't communicate together (i think)


Add typescript support for ui instead of javascript

We propose adding TypeScript support for the UI components of the project to enhance code quality, improve developer experience, and leverage the benefits of static typing.
Motivation:
TypeScript is a superset of JavaScript that adds static typing, which helps catch errors early during development and provides better tooling support. By adopting TypeScript for the UI components, we can:
Improve code readability and maintainability.
Enable better collaboration among developers through explicit type definitions.
Reduce runtime errors by catching type-related issues at compile time.
Take advantage of the rich ecosystem of TypeScript tools and libraries.

Would love to switch to Typescript too, its quite an effort 😄

I Will share the major pr but i have analyzed that whole repo needs to be changed, because the pipelines as well break if we start from the current repo status
@HenryHengZJ

@kapoorp99 yeah it is a big refractor change, do you have something already in work? feel free to add me to your repo

okk sure


Tinyxml in large size files

This is an issue about large size xml.
I am trying to parser a large size xml(over 30G). However, I think tinyxml2 cannot load such a large file. Can tinyxml2 handle large files over 30G?
Thanks!

No idea; but that far exceeds TinyXML-2 design goals. If nothing else, it would take 30G of memory to hold the file. You should probably be using a SAX parser.

Thanks for your help!


Add support for metric collection without a token

Motivation
Feature request

conf.yaml.example needs to be synced


Docker image is huge, optimization needed

Hello again!
The size of the Docker image is huge (about 3GB). I think we can do obvious optimizations to bring down the size. Even I get an occasional OOM when running the container with lower resources. I believe the app shouldn't be that memory-heavy as well right?

I am also interested in this question. https://github.com/crim50n/ChatGPT-Next-Web has almost the same functionality (no voice synthesizer) and takes 285 MB.

Agreed. Why use node:19-bullseye-slim instead of node:alpine as the base?

Resolved.


Admin Reload function to reload the database

Database loads off remote data package list. Would be nice to be able to reload this without having to reboot the entire heroku app.
/admin/reload

FIXED.


INARA Api Key finnicky

I've been trying to register my INARA Api Key, it previously worked but currently it's showing up red. I've completely reinstalled ELA multiple times, and checked that I'm using the right key via copy and paste and it still shows up red.

Seems to be off and on, it currently worked for a bit then failed once more. Maybe the API registration has a cooldown?

Yeah keeps being off and on, can't register my INARA API key, still doesn't work and then randomly starts working again.

INARA returns an error if there are too many requests in short amount of time, does it work if you leave it alone for a few minutes (with game not running) and then press "Validate"?


#1: add support for horses in database initialization

Done

/paulo - can you please review this pull request?

/paulo - can you check now?


chore(apps/gcp/prow/release): bump prow release to v0.8.1

It will only update configmap, will not affect the pods.

/hold

/unhold


Containerd unable to save during Packer docker image build within docker container

Hi,
I already asked this on the packer project page but I will also ask here since this seems to be a very docker-centric problem. I am trying to use packer inside a docker container to build docker images as follows:
cat > bla.sh<<EOL
#!/bin/bash -xe

echo "Hello folks"

exit 0
EOL

chmod +x bla.sh

cat > manifest.json<<EOL
{
  "builders":[
      {
         "commit":true,
         "image":"ubuntu:14.04.5",
         "type":"docker"
      }
   ],
   "provisioners":[
      {
         "type":"shell",
         "scripts":[
            "bla.sh"
         ]
      }
   ],
   "post-processors":[
      [
         {
            "only":[
               "docker"
            ],
            "tag":"0.0.1",
            "type":"docker-tag",
            "repository":"docker-registry.example.com/ubuntu-base"
         },
         {
            "login_password":"foo",
<EMAIL_ADDRESS>            "only":[
               "docker"
            ],
            "login_server":"https://docker-registry.example.com",
            "login_username":"foo",
            "login":true,
            "type":"docker-push"
         }
      ],
      [{
            "only":[
               "docker"
            ],
            "tag":"latest",
            "type":"docker-tag",
            "repository":"docker-registry.example.com/ubuntu-base"
         },
         {
            "login_password":"foo",
<EMAIL_ADDRESS>            "only":[
               "docker"
            ],
            "login_server":"https://docker-registry.example.com",
            "login_username":"foo",
            "login":true,
            "type":"docker-push"
         }
      ]
   ]
}
EOL

packer validate manifest.json &&  packer build -color=false manifest.json

However the provisioning gets stuck when trying to provision bla.sh.
I run docker inside the container by mounting the host's /var/run/docker.sock into the container and just using the docker binaries available from the docker release repositories as follows:
docker run -it -v /var/run/docker.sock:/var/run/docker.sock --privileged --dns <IP_ADDRESS> -w /home/jenkins-agent/ docker-registry.example.com/jenkins-agent:0.0.7 bash

I can therefore push and pull and do all docker stuff within the container without problems. Here is the regular output from attempting the packer build specified in manifest.json from above
Template validated successfully.
docker output will be in this color.

==> docker: Creating a temporary directory for sharing data...
==> docker: Pulling Docker image: ubuntu:14.04.5
    docker: 14.04.5: Pulling from library/ubuntu
    docker: Digest: sha256:062bba17f92e749bd3092e7569aa06c6773ade7df603958026f2f5397431754c
    docker: Status: Image is up to date for ubuntu:14.04.5
==> docker: Starting docker container...
    docker: Run command: docker run -v /home/jenkins-agent/.packer.d/tmp/packer-docker731907216:/packer-files -d -i -t ubuntu:14.04.5 /bin/bash
    docker: Container ID: de0da5d8b98dd11cb350d8e62e174b17d7f31bb9a1a37f166d16d33a0253114f
==> docker: Provisioning with shell script: bla.sh
Build was aborted

When I look at the syslogs of the host, I see errors about containerd not being able to save the container. This error always appears whenever I try to run the packer build with a shell provisioner. The logs are as follows:
Nov 27 16:06:15 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:15.038205355+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:18e39664a701ed59ab176513c54ead3a98f9c65b97c40f7eafa42d95d4a1f529 starttime: open /proc/2127/stat: no such file or directory"
Nov 27 16:06:15 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:15.038266574+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:18e39664a701ed59ab176513c54ead3a98f9c65b97c40f7eafa42d95d4a1f529 (pid 2127) has become an orphan, killing it"
Nov 27 16:06:17 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:17.110429824+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:266b063d3416af7c7c1450a3db71cd2708e5ad3907bd2e540159ca07f1a7c14f starttime: open /proc/2215/stat: no such file or directory"
Nov 27 16:06:17 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:17.110517715+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:266b063d3416af7c7c1450a3db71cd2708e5ad3907bd2e540159ca07f1a7c14f (pid 2215) has become an orphan, killing it"
Nov 27 16:06:17 BER-LX-01 ntpd[1300]: Listen normally on 335 veth4b1b166 [fe80::80c6:22ff:fe17:1f9%625]:123
Nov 27 16:06:17 BER-LX-01 ntpd[1300]: new interface(s) found: waking up resolver
Nov 27 16:06:19 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:19.167605128+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:cf76c52ca2f0184d58f3292f958ce31de46e36c1efcf0f5100b2ed1b852d1f34 starttime: open /proc/2332/stat: no such file or directory"
Nov 27 16:06:19 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:19.167757064+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:cf76c52ca2f0184d58f3292f958ce31de46e36c1efcf0f5100b2ed1b852d1f34 (pid 2332) has become an orphan, killing it"
Nov 27 16:06:21 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:21.208221241+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:db061d738df6e973753ebb376462fa178874bbbe8775bb17c895ae9ebc8d202c starttime: open /proc/2419/stat: no such file or directory"
Nov 27 16:06:21 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:21.208344182+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:db061d738df6e973753ebb376462fa178874bbbe8775bb17c895ae9ebc8d202c (pid 2419) has become an orphan, killing it"
Nov 27 16:06:23 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:23.264529024+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:e19832ac3ae22645939999d5b27f313b51d81618faf2d25357263782674b5c18 starttime: open /proc/2507/stat: no such file or directory"
Nov 27 16:06:23 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:23.264670439+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:e19832ac3ae22645939999d5b27f313b51d81618faf2d25357263782674b5c18 (pid 2507) has become an orphan, killing it"
Nov 27 16:06:25 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:25.304801578+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:4046c8aa6bc602535f4f94833dc1e640e965f18d094ca82e0510e3ed26bfee0a starttime: open /proc/2596/stat: no such file or directory"
Nov 27 16:06:25 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:25.305068372+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:4046c8aa6bc602535f4f94833dc1e640e965f18d094ca82e0510e3ed26bfee0a (pid 2596) has become an orphan, killing it"
Nov 27 16:06:27 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:27.362358401+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:1a58ce35b24b7f59756bf9f1896fdc2d2b8074925efb017687ce7fb681025d24 starttime: open /proc/2683/stat: no such file or directory"
Nov 27 16:06:27 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:27.362476338+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:1a58ce35b24b7f59756bf9f1896fdc2d2b8074925efb017687ce7fb681025d24 (pid 2683) has become an orphan, killing it"
Nov 27 16:06:29 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:29.418260661+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:d7af093901c4210660bde7973d882433616a5782bdc0743f4edcf18657a5dc6f starttime: open /proc/2776/stat: no such file or directory"
Nov 27 16:06:29 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:29.418387581+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:d7af093901c4210660bde7973d882433616a5782bdc0743f4edcf18657a5dc6f (pid 2776) has become an orphan, killing it"
Nov 27 16:06:29 BER-LX-01 kernel: [685940.982746] docker0: port 8(veth4b1b166) entered forwarding state
Nov 27 16:06:31 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:31.494697239+01:00" level=warning msg="containerd: unable to save 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:0c7e6de2ee342c73a59c72dc945ca76fb597f4ed98f5b604ec92f5446e620331 starttime: open /proc/2864/stat: no such file or directory"
Nov 27 16:06:31 BER-LX-01 dockerd[13546]: time="2016-11-27T16:06:31.494792097+01:00" level=info msg="containerd: 24f8fa06db96506734222dcf792b7b2ee1816bb32e50fb0f5f5ded471b4cca36:0c7e6de2ee342c73a59c72dc945ca76fb597f4ed98f5b604ec92f5446e620331 (pid 2864) has become an orphan, killing it"
Nov 27 16:06:32 BER-LX-01 kernel: [685943.690146] docker0: port 8(veth4b1b166) entered disabled state
Nov 27 16:06:32 BER-LX-01 kernel: [685943.690183] vethd6868f9: renamed from eth0
Nov 27 16:06:32 BER-LX-01 kernel: [685943.762877] docker0: port 8(veth4b1b166) entered disabled state
Nov 27 16:06:32 BER-LX-01 kernel: [685943.764246] device veth4b1b166 left promiscuous mode
Nov 27 16:06:32 BER-LX-01 kernel: [685943.764249] docker0: port 8(veth4b1b166) entered disabled state
Nov 27 16:06:34 BER-LX-01 ntpd[1300]: Deleting interface #335 veth4b1b166, fe80::80c6:22ff:fe17:1f9%625#123, interface stats: received=0, sent=0, dropped=0, active_time=17 secs

Host Platform
root@41b8a538733d:/# docker version
Client:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 21:44:32 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.3
 API version:  1.24
 Go version:   go1.6.3
 Git commit:   6b644ec
 Built:        Wed Oct 26 22:01:48 2016
 OS/Arch:      linux/amd64

root@41b8a538733d:/# docker info
Containers: 214
 Running: 3
 Paused: 0
 Stopped: 211
Images: 198
Server Version: 1.12.3
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 1062
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: null bridge host overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor seccomp
Kernel Version: 4.4.0-47-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.44 GiB
Name: work-laptop
ID: GWZO:74ZX:YVTM:ZI2C:FLCT:MGLU:HM46:NM7Q:NXKC:CIDD:2X47:WWUA
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No swap limit support
Insecure Registries:
 <IP_ADDRESS>/8

root@41b8a538733d:/# packer version
Packer v0.12.0

root@41b8a538733d:/# docker-runc --version
runc version 1.0.0-rc2
commit: f59ba3cdd76fdc08c004f42aa915996f6f420899
spec: 1.0.0-rc2-dev

root@41b8a538733d:/# docker-containerd --version
containerd version 0.2.4 commit: b818e749726ba18e430bb825396c85408dfaf2a4

root@41b8a538733d:/# docker-containerd-ctr --version
ctr version 0.2.4 commit: b818e749726ba18e430bb825396c85408dfaf2a4

uname -a
Linux work-laptop 4.4.0-51-generic #72-Ubuntu SMP Thu Nov 24 18:29:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Packer debug output log can be found at: https://gist.github.com/cprenzberg/27c53c4169c5c05ae8d88ff1d7ef657f
I look forward to any help you have to offer.
Best regards
Charles

The containerd messages are just warning and can be ignored. The logic has been fixed to avoid them to be shown for short lived processes (which is what's happening there).
It does seem that packer's docker exec with bla.sh fails though. Do you have the rest of the daemon logs for that particular instance? (it should have reference to a container named de0da5d8b98dd11cb350d8e62e174b17d7f31bb9a1a37f166d16d33a0253114f)

Hi @mlaventure
sorry i think I copy pasted the logs from another packer build. I have fixed the logs i posted earlier. The container named de0da5d8b98dd11cb350d8e62e174b17d7f31bb9a1a37f166d16d33a0253114f shows up in the logs just fine.
The exact code snippet above works just fine when I run it on the host so I don't think it is a packer issue. What do you think about the portions of the docker logs containing the following?
starttime: open /proc/2127/stat: no such file or directory

@cprenzberg I'll have a look at the updated logs.
Like I stated in my previous command the starttime related messages can safely be ignored

@cprenzberg You haven't added the rest of the daemon logs :)

@mlaventure here are the logs I have (restarted the docker engine and tried to reproduce this problem):
Dec 05 18:08:37 work-laptop systemd[1]: Stopping Docker Application Container Engine...
Dec 05 18:08:37 work-laptop dockerd[1110]: time="2016-12-05T18:08:37.629310100+01:00" level=info msg="Processing signal 'terminated'"
Dec 05 18:08:37 work-laptop dockerd[1110]: time="2016-12-05T18:08:37.677208043+01:00" level=warning msg="libcontainerd: container 9e2a85b72a07c04796ed0eb7d08c0a5fa08a8a7556815d57b2cfec751e214c6f restart c
Dec 05 18:08:41 work-laptop dockerd[1110]: time="2016-12-05T18:08:41.289574351+01:00" level=warning msg="libcontainerd: container 0d328a11cb784870ec98bfc28bb4823d999f5de14121890e7af4a9037b64b81d restart c
Dec 05 18:08:42 work-laptop dockerd[1110]: time="2016-12-05T18:08:42.644097645+01:00" level=error msg="Error during layer Store.Cleanup(): device or resource busy"
Dec 05 18:08:42 work-laptop dockerd[1110]: time="2016-12-05T18:08:42.644670792+01:00" level=info msg="stopping containerd after receiving terminated"
Dec 05 18:08:43 work-laptop systemd[1]: Stopped Docker Application Container Engine.
Dec 05 18:08:43 work-laptop systemd[1]: Starting Docker Application Container Engine...
Dec 05 18:08:43 work-laptop dockerd[31379]: time="2016-12-05T18:08:43.699486257+01:00" level=info msg="libcontainerd: new containerd process, pid: 31386"
Dec 05 18:08:44 work-laptop dockerd[31379]: time="2016-12-05T18:08:44.736986128+01:00" level=info msg="[graphdriver] using prior storage driver \"aufs\""
Dec 05 18:08:44 work-laptop dockerd[31379]: time="2016-12-05T18:08:44.895635664+01:00" level=info msg="Graph migration to content-addressability took 0.00 seconds"
Dec 05 18:08:44 work-laptop dockerd[31379]: time="2016-12-05T18:08:44.895869490+01:00" level=warning msg="Your kernel does not support swap memory limit."
Dec 05 18:08:44 work-laptop dockerd[31379]: time="2016-12-05T18:08:44.896256469+01:00" level=info msg="Loading containers: start."
Dec 05 18:08:44 work-laptop dockerd[31379]: ................................................................................................................................................................
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.092802266+01:00" level=info msg="Default bridge (docker0) is assigned with an IP address <IP_ADDRESS>/16. Daemon option --bip can be use
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.796692743+01:00" level=warning msg="Failed to allocate and map port 8529-8529: Bind for <IP_ADDRESS>:8529 failed: port is already allocated
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.831574197+01:00" level=warning msg="Failed to allocate and map port 8529-8529: Bind for <IP_ADDRESS>:8529 failed: port is already allocated
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.870720968+01:00" level=warning msg="failed to cleanup ipc mounts:\nfailed to umount /var/lib/docker/containers/0d328a11cb784870ec98bfc
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.892623668+01:00" level=error msg="Failed to start container 0d328a11cb784870ec98bfc28bb4823d999f5de14121890e7af4a9037b64b81d: driver f
Dec 05 18:08:45 work-laptop dockerd[31379]: time="2016-12-05T18:08:45.922266510+01:00" level=error msg="Failed to start container 271a4eaf3572821fa45f7a1b89c46b45e086e3cd2d10cd144b9bf3e273877f23: driver f
Dec 05 18:08:46 work-laptop dockerd[31379]: time="2016-12-05T18:08:46.077708464+01:00" level=info msg="Loading containers: done."
Dec 05 18:08:46 work-laptop dockerd[31379]: time="2016-12-05T18:08:46.077783132+01:00" level=info msg="Daemon has completed initialization"
Dec 05 18:08:46 work-laptop dockerd[31379]: time="2016-12-05T18:08:46.077816772+01:00" level=info msg="Docker daemon" commit=6b644ec graphdriver=aufs version=1.12.3
Dec 05 18:08:46 work-laptop systemd[1]: Started Docker Application Container Engine.
Dec 05 18:08:46 work-laptop dockerd[31379]: time="2016-12-05T18:08:46.097517901+01:00" level=info msg="API listen on /var/run/docker.sock"
Dec 05 18:12:14 work-laptop dockerd[31379]: time="2016-12-05T18:12:14.11878143+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:438b25c
Dec 05 18:12:14 work-laptop dockerd[31379]: time="2016-12-05T18:12:14.119091926+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:438b25c7879ae27299657f69
Dec 05 18:12:16 work-laptop dockerd[31379]: time="2016-12-05T18:12:16.181337264+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:01b4df
Dec 05 18:12:16 work-laptop dockerd[31379]: time="2016-12-05T18:12:16.181648463+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:01b4df547f346e25988b4490
Dec 05 18:12:18 work-laptop dockerd[31379]: time="2016-12-05T18:12:18.248056563+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:e8e329
Dec 05 18:12:18 work-laptop dockerd[31379]: time="2016-12-05T18:12:18.248238168+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:e8e32983eaae322fc42a38a4
Dec 05 18:12:20 work-laptop dockerd[31379]: time="2016-12-05T18:12:20.312011622+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:7c5754
Dec 05 18:12:20 work-laptop dockerd[31379]: time="2016-12-05T18:12:20.312209523+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:7c575442f2dc8f7e042607f2
Dec 05 18:12:22 work-laptop dockerd[31379]: time="2016-12-05T18:12:22.380769866+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:81e0e2
Dec 05 18:12:22 work-laptop dockerd[31379]: time="2016-12-05T18:12:22.380961122+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:81e0e2797f386e38d3396c77
Dec 05 18:12:24 work-laptop dockerd[31379]: time="2016-12-05T18:12:24.446013918+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:319ecf
Dec 05 18:12:24 work-laptop dockerd[31379]: time="2016-12-05T18:12:24.446193703+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:319ecf2e15bde13b77056ef6
Dec 05 18:12:26 work-laptop dockerd[31379]: time="2016-12-05T18:12:26.50791767+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:bb268fe
Dec 05 18:12:26 work-laptop dockerd[31379]: time="2016-12-05T18:12:26.508064207+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:bb268fe2b5df777066a4891a
Dec 05 18:12:28 work-laptop dockerd[31379]: time="2016-12-05T18:12:28.586558019+01:00" level=warning msg="containerd: unable to save 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:d31189
Dec 05 18:12:28 work-laptop dockerd[31379]: time="2016-12-05T18:12:28.586857165+01:00" level=info msg="containerd: 58246f229e135c09adf28c4944c8d749aaf4a71815255a3fc1a51fcce7b2a541:d311895a887c817cd671aa1a

@cprenzberg those lofs still don't include the needed information about de0da5d8b98dd11cb350d8e62e174b17d7f31bb9a1a37f166d16d33a0253114f.
Could you try to reproduce the issue while having the daemon in debug mode?

@mlaventure debug logs are available here
thanks

ping @mlaventure ^^

Looking at the log, your issue is that the script doesn't get properly "uploaded" to the ubuntu:14.04.5 container created by packer.
My guess is that bla.sh is within the first container, docker is on the host, the 2nd container is running on the host and not withing the packer container, so when packer does its upload thing, it somehow doesn't make it through into the second container.
Not knowing how packer does the "upload" part, I can't really go further than that.

I'm pretty sure docker within docker (which is required for packer to create a docker container when running within docker container) - is not going to work, and MitchellH tweeted about it last year, and still planning on resolving this... I have had this same issue, but docker within docker, for packer purposes, just isn't going to work AFAIK.

Got the same issue. Unrelated to packer - just an ordinary container running.

Let me close this issue for now, as it seems this is not supported by packer.
@evmin there's many possible causes for a file to not be uploaded, or mounted into a container, if you suspect there's a bug, please open a new issue with details (be sure to include the information that's requested in our issue template  https://raw.githubusercontent.com/docker/docker/master/.github/ISSUE_TEMPLATE.md)


⚠ ClamAV has degraded performance

In 7a94cee, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 79 ms

Resolved: ClamAV performance has improved in 8ad6c78 after 11 minutes.


insight often returns identical stream data at a very high frequency

I am seeing erratic behaviour from my Emotiv Insight after i subscribe to receive a 'pow' stream. Most of the times, after subscribing, the device sends identical json data very quickly after each other (thousands of times a second). Sometimes it sends proper data, after subscribing, at a much lower rate (about 8 times a second). Is my device broken?
I am using the latest Cortex software on OS X, i installed the upgrade today, but it didn't solve my problem.

Note that when i unplug the USB dongle and plug it back in, the first session/subscribe always works. After that, the headset gives the corrupt and identical data at high speed.
I think unplugging/plugging in the bluetooth dongle resets the emotiv websocket server, and that is why it then works (one time only). Switching the headset off and back on has no effect.
I will try the community SDK soon, i hope it is more reliable!

Thread get band power data run with interval 125 ms. first time headset connected, buffer data is not full so, it output 8 values/second -> this is speed of the detection. You see the output about 1000 value/s because have many response with same value. Basically, it only has 8 new values / second.

I can't verify it right now, because i need to charge my headset.
I assumed that the cortex websocket server would send a new pow stream data event 8 times per second, always. It makes no sense sending data each millisecond when it doesn't change so often, it is terribly inefficient! It would then even make more sense to subscribe/get data/unsubscribe 8 times a second...
When i use the headset the first time after plugging in the USB dongle, i can receive thousands of pow data events, at 8 times per second. This is how it should always behave from the users point of view, device buffer full or not...

I have the headset charger again, and i did some experiments. When receiving the pow data continuously, without adding a pause between the reading, i do get new different values 8 times a second, you are right. If i add a pause of 125 ms between reading, something strange happens: i don't get new values each time, but i get an irregular sequence where most values are identical and some are different. So you can't poll the device at a lower rate either...
I will try an approach where stream data is read continuously, without a pause, and let the software skip all data packets that have identical data as the previous data. I hope i can get a stream of valid data points this way, but even if it wil work, it is so inefficient :(

I tried reading other types of streams ("mot", "fac", "met" and "dev") and these all work as expected: a data frame is sent only when there is actual new data. Why does behave "pow" differently? A bug?

@notnot it is related to the bug in https://github.com/Emotiv/cortex-example/issues/24 as well so we will fix this in the upcoming release.

Update: Cortex 1.4 fixes this issue, thanks.


remove archived RocksDB WAL files on agent servers

Scope & Purpose
Remove archived RocksDB WAL files from the archive on agent servers. Previously WAL files were retained even agent servers due to an error.

[x] Bug-Fix for a released version (did you remember to port this to all relevant release branches?)
[x] The behavior in this PR can be (and was) manually tested (support / qa / customers can test it)

Testing & Verification
Also added a test suite in this PR. The test suite needs separate activation in Jenkins so that it will run
scripts/unittest wal_cleanup --storageEngine rocksdb --cluster true
https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/4821/

Tests added to the PR.
The test suite needs separate activation in Jenkins so that it will run
scripts/unittest wal_cleanup --storageEngine rocksdb --cluster true

Only an unrelated test failed


BinlogSyncer.Close() will be blocked if BinlogStreamer exists

BinlogSyncer.wg will be Add(1) when creating BinlogStreamer. And BinlogSyncer.wg only will be decrease when an error comes to BinlogSyncer.onStream.
BinlogSyncer.Close() was waiting on wg.
So if I call BinlogSyncer.Close() when there is no error in BinlogSyncer.onStream, process will be blocked.

The code in close sets a 100ms timeout here
if b.c != nil {
		b.c.SetReadDeadline(time.Now().Add(100 * time.Millisecond))
	}

how about using b.c.Close() directly?

        if b.c != nil {
                b.c.SetReadDeadline(time.Now().Add(100 * time.Millisecond))
        }
        b.c.Close()

I tried to add b.c.Close() here.
After adding this line, the process exit successfully.

Em, SetReadDeadline will have no effect if reading some data in 100ms and then be cleared. Maybe Close is right here.
can you send me a PR to fix this?

Sure, but I found another problem when verifying the fix code.
Even if I called b.c.Close() here, there is still a case that blocking on b.wg.Wait().
Because BinlogSyncer.parseEvent is sending BinlogEvent to a buffered channel(s.ch), so onStream method may be blocking on it.

How about SetReadDeadline(0)?

The point is BinlogSyncer.parseEvent thread may be already blocked on s.ch before BinlogSyncer.Close() was called.
As long as BinlogSyncer.Close() waiting on b.wg.Wait(), no matter how to close the TCP connection, onStream method on the other thread will not decrease the WaitGroup.

@andwxh , can above PR fix this problem?

Yeah! This time its completely fixed. Thank you.

I wondered is it a good practice to use two variables (wg & stopCh) in Close(), in order to ensure onStream thread stopped. But it works now.


Bug: Mongo cannot change username root

What happened?

I change mongo username to root1234, then Starting Mongo failed, connection() error occurred during connection handshake: auth error: sasl conversation error: unable to authenticate using mechanism "SCRAM-SHA-1": (AuthenticationFailed) Authentication failed.;ths addr is:<IP_ADDRESS>:37017
What did you expect to happen?
I should not have this error
How can we reproduce it (as minimally and precisely as possible)?
change mongo username in .env, make clean, docker compose down, docker compose up -d
Anything else we need to know?
No response
version

```console
$ {name} version
# paste output here
```

Cloud provider

OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

Install tools

.env, docker compose down, then make clean, docker compose up -d


Workflow_job events with empty labels get matched to scale up targets

For some reason we receive workflow_job completed events with empty labels which are unfortunately wrongly matched to a scale up target resulting in wrongly scaling down scale targets when they shouldn't be scaled down.
Example of workflow_job completed payload:
{
  "event": "workflow_job",
  "hookID": "***",
  "delivery": "***",
  "workflowJob.status": "completed",
  "workflowJob.labels": [],
  "repository.name": "***",
  "repository.owner.login": "***",
  "repository.owner.type": "Organization",
  "enterprise.slug": "***",
  "action": "completed",
  "groups": "RunnerGroup{Scope:Organization, Kind:Custom, Name:BigRunners}, RunnerGroup{Scope:Organization, Kind:Custom, Name:DefaultAutoscaling}, RunnerGroup{Scope:Organization, Kind:Custom, Name:BigRunners}"
}

scale down event:
status": "completed", "workflowJob.labels": [], "repository.name": "***", "repository.owner.login": "***", "repository.owner.type": "Organization", "enterprise.slug": "***", "action": "completed", "enterprise": "***", "organization": "***", "repository": "***", "key": "mobitroll/group/BigRunners"}
"2022-04-21T10:59:33Z;DEBUG;controllers.webhookbasedautoscaler;Patching hra runner-deployment-8c-16g-autoscaler for capacityReservations update;{"before": 0, "expired": 0, "amount": -1, "after": 0}
"2022-04-21T10:59:33Z;INFO;controllers.webhookbasedautoscaler;scaled runner-deployment-8c-16g-autoscaler by -1

What's interesting is that the workflow_job complete events don't seem to match in numbers workflow_job queued events:

label
queued
completed

null
0
274

self-hosted
2
2

self-hosted-8c-16g
4
3

self-hosted-8c-32g
1
1

ubuntu-20.04
2
2

ubuntu-latest
446
446

Expected behavior
workflow_job completed events with empty labels should not match scale up targets.
Environment:

Controller Version: v0.22.2
Deployment Method:  Helm
Helm Chart Version: 0.17.2

I captured the raw payload from the GH webhook and I think I see when this happens, it's when the workflow_job is skipped:
{
  "action": "completed",
  "workflow_job": {
    "status": "completed",
    "conclusion": "skipped",
    "steps": [

    ],
    "labels": [

    ],
)

And the corresponding log lines from the actions-runner-controller-github-webhook-server:
"2022-04-21T14:36:41Z;DEBUG;controllers.webhookbasedautoscaler;Searching in runner groups;{"event": "workflow_job", "hookID": "***", "delivery": "75129710-c180-11ec-9642-a48b3e53116d", "workflowJob.status": "completed", "workflowJob.labels": [], "repository.name": "***-frontend", "repository.owner.login": "***", "repository.owner.type": "Organization", "enterprise.slug": "***", "action": "completed", "groups": "RunnerGroup{Scope:Organization, Kind:Custom, Name:BigRunners}, RunnerGroup{Scope:Organization, Kind:Custom, Name:DefaultAutoscaling}"}"
"2022-04-21T14:36:41Z;DEBUG;controllers.webhookbasedautoscaler;groups;{"event": "workflow_job", "hookID": "***", "delivery": "75129710-c180-11ec-9642-a48b3e53116d", "workflowJob.status": "completed", "workflowJob.labels": [], "repository.name": "***-frontend", "repository.owner.login": "***", "repository.owner.type": "Organization", "enterprise.slug": "***", "action": "completed", "groups": "RunnerGroup{Scope:Organization, Kind:Custom, Name:BigRunners}, RunnerGroup{Scope:Organization, Kind:Custom, Name:DefaultAutoscaling}"}"
"2022-04-21T14:36:41Z;DEBUG;controllers.webhookbasedautoscaler;Found 2 HRAs by key;{"key": "***/group/BigRunners"}"
"2022-04-21T14:36:41Z;DEBUG;controllers.webhookbasedautoscaler;job scale up target found;{"event": "workflow_job", "hookID": "***", "delivery": "75129710-c180-11ec-9642-a48b3e53116d", "workflowJob.status": "completed", "workflowJob.labels": [], "repository.name": "***-frontend", "repository.owner.login": "***", "repository.owner.type": "Organization", "enterprise.slug": "***", "action": "completed", "enterprise": "***", "organization": "***", "repository": "***-frontend", "key": "***/group/BigRunners"}"
"2022-04-21T14:36:41Z;DEBUG;controllers.webhookbasedautoscaler;Patching hra runner-deployment-8c-16g-autoscaler for capacityReservations update;{"before": 0, "expired": 0, "amount": -1, "after": 0}"
"2022-04-21T14:36:41Z;INFO;controllers.webhookbasedautoscaler;scaled runner-deployment-8c-16g-autoscaler by -1"

Perhaps we should ignore workflow_job status complete if conclusion is skipped?

https://github.com/actions-runner-controller/actions-runner-controller/pull/1330 it's already fixed in master, the fix will be in the next release v0.23.0. If you fancy building master and deploying it to confirm that would be helpful.

#1330 it's already fixed in master, the fix will be in the next release v0.23.0. If you fancy building master and deploying it to confirm that would be helpful.

Is there an approximate ETA for v0.23.0 ?

Not sure. You can track the milestone https://github.com/actions-runner-controller/actions-runner-controller/milestone/3. Most of the issues have PR raised which we just need to do some testing where the CI can't so I probably a few weeks but life happens sometimes etc so it could be longer

Going to close this as, as previously mentioned, this is fixed via https://github.com/actions-runner-controller/actions-runner-controller/pull/1330 which will be part of the v0.23.0 release


GET /books HTTP/1.1" 500 5

For Feature Requests
Desired Feature:   normal http response.
For Bug Reports

BookStack Version (Found in settings, Please don't put 'latest'):  0.20.0
PHP Version:  PHP 7.0.25-0ubuntu<IP_ADDRESS> (cli) ( NTS )
MySQL Version:5.7.21-0ubuntu<IP_ADDRESS> (Ubuntu)

Expected Behavior
normal page display.
Current Behavior
HTTP ERROR 500
nginx log:
2018/03/16 08:59:12 [error] 3537#3537: *486 FastCGI sent in stderr: "PHP message: PHP Warning:  require(/var/www/bookstack/vendor/guzzlehttp/psr7/src/functions_incl5
PHP message: PHP Fatal error:  require(): Failed opening required '/var/www/bookstack/vendor/guzzlehttp/psr7/src/functions_include.php' (include_path='.:/usr/share/"
Steps to Reproduce
install with  Ubuntu 16.04 Installation Script
run for one or two more days with writing books.

supplement：
root@iZ2ze9hcysthc2bloinso3Z:/var/www/bookstack# composer install

php -r "!file_exists('bootstrap/cache/services.php') || @unlink('bootstrap/cache/services.php');"
php -r "!file_exists('bootstrap/cache/compiled.php') || @unlink('bootstrap/cache/compiled.php');"
Loading composer repositories with package information
Installing dependencies (including require-dev) from lock file
Nothing to install or update
Generating optimized autoload files
Illuminate\Foundation\ComposerScripts::postAutoloadDump
PHP Warning:  Uncaught ErrorException: require(/var/www/bookstack/vendor/guzzlehttp/psr7/src/functions_include.php): failed to open stream: No such file or director5
Stack trace:
#0 /var/www/bookstack/vendor/composer/autoload_real.php(55): Composer\Util\ErrorHandler::handle(2, 'require(/var/ww...', '/var/www/bookst...', 55, Array)
#1 /var/www/bookstack/vendor/composer/autoload_real.php(55): require()
#2 /var/www/bookstack/vendor/composer/autoload_real.php(45): composerRequireef4ebfde56517d00a30c3e00bd70fd1f('a0edc8309cc5e1d...', '/var/www/bookst...')
#3 /var/www/bookstack/vendor/autoload.php(7): ComposerAutoloaderInitef4ebfde56517d00a30c3e00bd70fd1f::getLoader()
#4 /var/www/bookstack/vendor/laravel/framework/src/Illuminate/Foundation/ComposerScripts.php(43): require_once('/var/www/bookst...')
#5 /usr/share/php/Composer/EventDispatcher/EventDispatcher.php(238): Illuminate\Foundation\ComposerScripts::postAutoloadDump(Object(Composer\Script\Event))
#6 /usr/share/php/C in /var/www/bookstack/vendor/composer/autoload_real.php on line 55

it seems  after a while ,  the  directory:
the total amount size of /var/www/bookstack/vendor   will change from 84M  to 32M .
what happend？  how could I to prevent the files disappear ?

@junlicn Thanks for reporting, What kind of hosting are you using and what operating system is it on?
This is a very strange issue, Does the size of vendor/ go down gradually over time or does it suddenly jump to that size?

sorry, at first I thinks it is the composer update script problem after I googled it.  But now I am not sure.  It seems after I  deleted my crontab backup shell script which have some rm command, it is normal, not disappear any more.

Okay, No problem, I'll close this issue then. Feel free to comment if you find it is a BookStack issue.


No example for BottomSheet search

From our material design catalog page, I tried to find examples of "BottomSheet" and came up empty: https://github.com/flutter/flutter/search?utf8=✓&q=path%3Aexamples+"new+BottomSheet"&type=Code

Do we have example of BottomSheet, and is GitHub's search not finding it?

Can we add examples of BottomSheets? :)

Thanks!

cc @HansMuller @InMatrix

BottomSheet isn't a thing you use on its own.  There are persistent bottom sheets (see https://docs.flutter.io/flutter/material/ScaffoldState/showBottomSheet.html) and modal bottom sheets (see https://docs.flutter.io/flutter/material/showModalBottomSheet.html) that are how you typically use this.
The docs on https://docs.flutter.io/flutter/material/BottomSheet-class.html try to explain this situation.

The gallery has persistent and modal bottom sheet demos. They're
examples/flutter_gallery/lib/demo/persistent_bottom_sheet_demo.dart
examples/flutter_gallery/lib/demo/modal_bottom_sheet_demo.dart

Thanks for the pointers, @HansMuller. I'll update the page to correct the query.

Thanks all!
On Wed, Oct 12, 2016 at 15:06 Tao Dong<EMAIL_ADDRESS>wrote:

Thanks for the pointers, @HansMuller https://github.com/HansMuller.
I'll update the page to correct the query.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/6290#issuecomment-253353862,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAVZ_ZWm3C_msM9MfXUwgBeR6he1Gn8ks5qzVnvgaJpZM4KVM9z
.


Copy branch as PGN doesn't save the FEN if the variation didn't start from initial position

It seems to happen if the FEN is only 1 move away from start, as the final digit is still 1.

fixed in v2.0.7


Add design note for lifecycle model of function node

This PR adds design note for lifecycle model of enhanced function node.
This design note includes new lifecycle mode, using external NPM modules, and initialization/finalization support.

As discussed at the F2F meeting, the plan is to first implement the "initialise" and "finalise" options and not do the "config" tab yet because that poses a lot of extra problems around dynamic handling of npm modules.
Having also looked at the code in the pull request (https://github.com/node-red/node-red/pull/2498) some addition design questions come to mind that need to be clearly documented. Given the discussion on this feature is now split between here and the implementation PR, I'm going to add some comments to both places. Some comments related to the conceptual design of the feature, and I'll those here. Some other comments relate to implementation details, which I'll add to the PR. If that split is not helpful, we can focus the conversation in one place or the other.
What APIs are available to the init/final code?

can they access context?
can they call node.send? (In the current PR, the node object has not been made available)
can they return a Promise to allow for asynchronous work to be done before the node starts handling messages or the runtime stops.

What error handling is in place for the code?

if initialize throws an error (or if it can return a promise that rejects), does the node continue to process messages?

Thank you for your comments.

can they access context?

Contexts can be accessible. I think one of the roles of the initialization and exit codes is to initialize/cleanup contexts.

can they call node.send? (In the current PR, the node object has not been made available)

I think we should not allow calling node.send. because the receiving node may not be a ready.

can they return a Promise to allow for asynchronous work to be done before the node starts handling messages or the runtime stops.

The value returned by the initialization code will be ignored because there is no way to refer it in the function body.
However, it is possible to save promises in context and refer to it in the main body.

What error handling is in place for the code?

if initialize throws an error (or if it can return a promise that rejects), does the node continue to process messages?

Whether an error in the initialization code affects message processing is processing-dependent, so message processing is not stopped by an error in the initialization code.
Currently, if an error occurs, it will be logged as follows
2 Apr 13:12:21 - [error] [function:f369ddf5.eab71] ReferenceError: node is not defined

If error handling is required, the error information should be passed using context or other means.

The value returned by the initialization code will be ignored because there is no way to refer it in the function body.
However, it is possible to save promises in context and refer to it in the main body.

I did not mean the function body should be able to access the returned promise of the initialise code.
I mean the Function node should wait to setup its on-message handler until the promise resolves. And if the promise rejects then it should not setup the on-message handler because the node is not able to handle messages.

If error handling is required, the error information should be passed using context or other means.

I'm not sure what you mean. Yes it is possible for someone to write lots of error handling code and do lots of tricks with context to pass things around. I am more concerned about the cases where a user hasn't added proper error handling code - because lots of our users are not experienced JavaScript programmers who know how to do that. We need to make sure errors are clearly reported and the behaviour makes sense. This is why I think if the initialize code throws an uncaught exception the node should not be allowed to continue processing messages.
We need real examples of Function node code that demonstrate (and test) the different possible patterns here.

I mean the Function node should wait to setup its on-message handler until the promise resolves. And if the promise rejects then it should not setup the on-message handler because the node is not able to handle messages.

I think your suggestion is appropriate.
After testing some code, I realized that we need support for two types of code: one that returns promise and one that uses callbacks.
Also, it would be nice to be able to handle multiple promises or callbacks.

Example with Promise

function foo(ms, msg) {
    var p = new Promise((resolve, reject) => setTimeout(function() {
        console.log(msg);
        resolve();
    }, ms));
    return p;
}

var p0 = foo(3000, "ONE");
var p1 = foo(2000, "TWO");
return [p0, p1];

Example with Callback

function foo(ms, msg) {
    var cb = asyncCallback();  // global function that creates callback
    setTimeout(function() {
        console.log(msg);
        cb(null, msg);
    }, ms);
}

foo(4000, "QUUX");
foo(2000, "QUUUX");

My concern is that the messages sent  before the initialization completes will be lost.
Should we queue these messages?

I'm not sure what you mean. Yes it is possible for someone to write lots of error handling code and do lots of tricks with context to pass things around. I am more concerned about the cases where a user hasn't added proper error handling code - because lots of our users are not experienced JavaScript programmers who know how to do that. We need to make sure errors are clearly reported and the behaviour makes sense. This is why I think if the initialize code throws an uncaught exception the node should not be allowed to continue processing messages.

I understand your point.  Changed the "input" handler will not be registered when an error occurs in the initialization process.   Also, the error message has been changed to add the location information as follows.
[error] [function:10192335.51f6ed] SyntaxError: Unexpected token } (setup:line 5)

We need to keep the API for the initialise function as clean and simple as possible, but also ensure it can be used properly.
I realise the init function should be defined as an async function - just as we do the body of the main function. That means users can use await- which can make for much cleaner code.
I do not think it should be possible to return multiple promises. If a user needs to do that, they can either:
await p1;
await p2;

or
return Promise.all([p1,p2]);

I'm not sure about your callback suggestion. It doesn't feel a natural api to me. A more conventional api would have one done callback, but I don't know how to make that fit.
Can I propose we stick with Promises for now and we can get user feedback on if callbacks are needed - its easier to add then take away.

Can I propose we stick with Promises for now and we can get user feedback on if callbacks are needed - its easier to add then take away.

It is no problem to limit initialization code to return single promise object.
Fixed document & current implementation according with this.
It also fixed following:

messages received before completion of initialization are queued,
value returned as a promise can be obtained by calling getInitValue function

value returned as a promise can be obtained by calling getInitValue function

I am not sure about this. It assumes the init function is expected to return a value - which it is not.
I think if the user needs the result of the promise they can store it themselves. If they are using async/await:
context.someValue = await myAsyncFunction();

or with a new Promise object:
return new Promise( (resolve, reject) => {
   // do some work
   // ...
   resolve("my value");
}).then(result => { context.someValue = result; });

I think you mentioned somewhere you implementation is queuing up calls to node.send(), but the design note doesn't describe the behaviour. Can you explain what you have implemented for this? How are the messages queued up and when do they get sent?

I am not sure about this. It assumes the init function is expected to return a value - which it is not.

If no value is returned, undefined is used as in the normal JavaScript function.

I think if the user needs the result of the promise they can store it themselves. If they are using async/await:

That's right.  However, as you commented at the beginning, using context seems not to be intuitive for non-experienced users.  Otherwise, the first idea to handle asynchronous processing using context can be used.

I think you mentioned somewhere you implementation is queuing up calls to node.send(), but the design note doesn't describe the behavior. Can you explain what you have implemented for this? How are the messages queued up and when do they get sent?

Added description on this behavior.
Messages received while async initialization is performed are kept by message handler of function node and processed in received order after the initialization completes.

@HiroyasuNishiyama I see you have added a lot of content regarding installation of modules.
We had agreed the module stuff was not something we would look at for the initial version of this feature. The idea behind the design notes is not to have a PR that is doesn't get merged because new features are constantly being added.
Please can we try to get this design merged first? You can then add the module install ideas as a new PR that can be discussed separately.
As it stands, I cannot merge this PR with those extra changes in. I have very large concerns about the whole concept of allowing the Function node to install modules and any proposal is going to take a lot of work to figure out.

I agree with you.
Reverted previous commit.
I will try to submit another PR after merge.

Have been playing with the PR for this today.
There are some implementation specific comments I will add to that PR.
From a high level design, I don't think we should include getInitValue for this initial version. It gives the impression the user can only pass one value from the setup to the main function. But in reality they can pass whatever they want using context. I don't want to confuse matters by having two different ways of doing the same thing.
It does not stop us adding something like getInitValue in the future if we get feedback that something like that is needed.

I have merged this design note because its implementation has been merged into dev for the 1.1.0 release.
We can now restart the conversation on npm module dependencies via a new PR that adds that content to the design.
Thanks! 🎉

Thank you for merging.
I have opened a new PR (https://github.com/node-red/designs/pull/31).
I would appreciate your comments on it.


Improve gradle configuration

Improving Gradle configuration to make build faster
1. First improvement is to update how checkstyle is configure
Cache is not relocatable due to config file defined with an absolute path.

Usage of getConfigDirectory() to retrieve checkstyle-suppressions.xml file will retrieve an absolute path for this file.

The proposal is to inline the configuration, by {config_loc} that will give a relative path. Using that configuration be become Cacheable for next builds
2. Second improvement is to update all tasks declaration by using tasks.register()
The proposal will defer task creation when is needed. It also align the code to use tasks.register for all defined tasks.
Here 2 build scans where you can see the improvement

the first for master branch (commit 92173ba6dbc3daadea68e4348e760e99d1e79783), where you can see that during the Configuration, tasks for build.gradle are Created immediately.

on the other side for a scan on my PR branch skurtzemann/improve-gradle-configuration (commit 711d770a2c496f2deb8c8d7426ecd0c13754b4e2) all build.gradle tasks are Created during configuration

Do you have any near-term plans to merge this pull request?