amplify push causes local changes to be reverted instead of pushed to the cloud

Describe the bug
I've made some changes to the authentication schema in the cloudformation.yml file and updated the parameters.json file to add 2 custom attributes. Whenever I try to push them to the cloud using "amplify push" the command instead pulls the current state of the cloud and reverts my local changes.
Amplify CLI Version
4.27.1
To Reproduce

Change parameters.json and/or cloudformation.yml
Run "amplify push"

Expected behavior
I want my User Pool attributes to be updated in the cloud.
Desktop (please complete the following information):

OS: Windows]
Node Version: v12.18.3

Update: tried adding the custom attributes in the cloud and running "amplify pull". The terminal informed me that there are no changes and nothing happened.

@Zablas have you been able to successfully push other resources in the project? What parameters / modifications did you make to the cloudformation template?

@edwardfoyle I have noticed an interesting thing that after running "amplify update auth" and doing some other unrelated changes and then running "amplify push" it no longer complains about missing attributes even though locally they are not present but they are represented in the cloud. I have added these lines of code in my cloud formation:
        -
          Name: notifications
          Required: true
          Mutable: true
          AttributeDataType: String
          StringAttributeConstraints:
            MinLength: 1
            MaxLength: 256

        -
          Name: radius
          Required: true
          Mutable: true
          AttributeDataType: Number
          NumberAttributeConstraints:
            MinValue: 1
            MaxValue: 100

These are now gone locally but as I've mentioned everything seems to still be working.

@Zablas you'll have to be careful about running update on resources where you have made manual changes to the templates. In some cases, update operations will overwrite changes that you have made manually. That being said, I would expect that after doing a push, what is present in the cloud would be the same as what you have locally. Are you sure you were looking at the same region / environment?

@edwardfoyle Yes, I am sure. These are my only resources open on this account.

I'm having the same issue, I updated my schema.graphql
(base) ➜  vite git:(aws-login) **amplify status**

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Api      | xxxxx         | **Update**    | awscloudformation |
| Auth     | vxxxxx  | No Change | awscloudformation |
| Storage  | xxxxx   | No Change | awscloudformation |

(base) ➜  vite git:(aws-login) amplify push
✔ Successfully pulled backend environment dev from the cloud.

Current Environment: dev

| Category | Resource name | Operation | Provider plugin   |
| -------- | ------------- | --------- | ----------------- |
| Auth     | xxxxxxxxx  | No Change | awscloudformation |
| Storage  | xxxxxxxxxx   | No Change | awscloudformation |
| Api      | xxxxxxxxx       | No Change | awscloudformation |

All changes made to schema.graphql   are reverted

@Stevenje @Zablas I've experienced this exact same issue when I'm modifying files in amplify/#current-cloud-backend/.. directories instead of files in amplify/backend/... :) Could you please check again if that's not the case?

hey @kaustavghosh06 unfortunately I had to move away from amplify - but if it helps the only file I edited was schema.graphql file and was trying to push updates from that. Not sure if thats in both locations. Hope that helps.

@Stevenje Yeah, the schema.graphql is present in both the directories. Closing this issue - but if you come across this anytime in the future please feel free to open up a new issue.

@kaustavghosh06  , please re-open this ticket. I have exactly the same issue that @Stevenje mentioned.
OS: OSX
Node Version: 10.22.1
Amplify: 4.37.1
| Category | Resource name   | Operation | Provider plugin   |
| -------- | --------------- | --------- | ----------------- |
| Api      | f402            | Update    | awscloudformation |
| Auth     | cognito3d888862 | No Change | awscloudformation |

Here the changes are being recognized
and when I run amplify push it reverts to the old schema, like no change ever happen. 🤨

| Category | Resource name   | Operation | Provider plugin   |
| -------- | --------------- | --------- | ----------------- |
| Api      | f402            | No Change | awscloudformation |
| Auth     | cognito3d888862 | No Change | awscloudformation |

All changes made to schema.graphql are reverted
I updated to the latest amplify CLI just to be sure it was not that.
I've been working with amplify for the last year and this was never a problem
Thanks for your help!

This error still persists. Why are you closing the tickets without actually fixing the root cause?

I am experiencing same issue when I update userPool groups with custom permissions and roles. When I do the changes locally and do amplify status, it shows the changes. On applying the changes by doing amplify push, I can see the local changes are reverted. This seems a bug

@kaustavghosh06 please reopen this issue

Interesting this is happening only on some nested stack not on main CF template


10.0.18362.2158 #103安装出错

Dear Sir, I am using your developed
support 10.0.18362.2158 #103 There is an error in the installation prompt

Maybe you can kill the antivirus software and retry


Create a media query challenge may fail

Challenge: https://learn.freecodecamp.org/responsive-web-design/responsive-web-design-principles/create-a-media-query/
I have seen issues with this challenge on the forum a number of times.
The test is using the computed properties but because you can set a minimum font size in the browser this may not work. In Chrome, you can use chrome://settings/fonts and set the minimum font size to be greater than 10px. If you then run the test it will fail.
Changing the test to use a regex instead might be better.
I'm not sure if this proposed change will fix all problem cases but it will at least take care of any minimum font size set in the browser. It should likely also fix any browser compatibility issues. I say that because this is one of the challenges where switching browsers often seem to help people pass the test.

@lasjorg Can I look at this issue?

@RandellDawson @lasjorg
I also want to point out that the following code passes even if it's incorrect because the way we test right now.

@RandellDawson @lasjorg
I also want to point out that the following code passes even if it's incorrect because the way we test right now.

@RandellDawson @lasjorg
I also want to point out that the following code passes even if it's incorrect because the way we test right now.

I think one possible solution (avoid regex) is just have the original style section as:
<style>
  p {
    font-size: 30px;
  }

  /* Add media query below */

</style>

and then have the camper change the font-size to 20px or 25px with the media query.  The main reason people change this setting to something greater than 10px, is because the resolution on many screens is higher than it used to be, so 10px seems "small".

@aditijoshi14 That is true.  This will involve changing the tests.

@RandellDawson That makes sense.  Chaing the size will surely fix the original issue.  Also, yes we do have to change the test for fixing the issue I pointed out above. Can I work fixing both of these issues? Also, do you want me to make a different new issue for the problem I pointed out or is it okay to have PR under this issue?

Actually, the more I think about this, we can not just look at the computed value regardless of the font-size we are looking for, because we don't have a way of mocking the user's screen height.  We really need something like puppeteer to simulate the screen height at below and above 800px to validate the correct size is used.
I guess we are stuck with using regex for both tests.  I suggest we also add a new test which validates the normal font-size for p elements is 20px, so the user does not change the seed code.  Then, I suggest we rearrange the tests, so the current second test becomes the first.  There is no need to modify the test below because we just want to make sure they are using a media query of any kind and this test does validate that.  The second test (currently the first test) is where we will need to make sure the media query is used and that the font-size will be 10px when the height is less than or equal to 800px.
This means the new second test's regex will be very similar to the first test's regex, but it will validate the ```
p {
font-size: 10px;
}
exists inside the media query definition.

@aditijoshi14 Go ahead and take a shot at the tests using what I have described above.  Also, go ahead and remove the assert message arguments from the `testString`s, as they are no longer needed.

@RandellDawson Thank you so much for providing me detail information on things that I should get started with.
It is good that we no longer need message argument from the testString as it was just repetitive.
I will get started with this.

@RandellDawson
Here is the order of the test:

Checking media query is declared right or not (currently the second test)
Checking font-size is set to 10px or not for screen size lower than 800px using media queries. (using regex).
Checking the normal font-size for p elements is 20px.

For number 3, I can only think of a regex solution. Because if we keep the following test, it might not always pass as it depends on the browser's screen size.
$('p').css('font-size') == '20px'
Should I just proceed with regex for the 3rd test as well?

To check number 3 above, you should strip out any media query (regex with a replace) and then validate that you find:
  p {
    font-size: 20px;
  }

That sounds like a valid test. I will work on it and push a PR.


Fix precompiler if should be ifdef in ota agent

Fix precompiler if should be ifdef in ota agent
Description
Just very minor change, this fails with stricter compilation settings otherwise:
aws_iot_ota_agent.h:408:13: error: "WIN32" is not defined, evaluates to 0 [-Werror=undef]
         #if WIN32
             ^~~~~
cc1: all warnings being treated as errors

Checklist:

[  ] I have tested my changes. No regression in existing tests.
[  ] My code is Linted.
(didn't take the effort, i assume very much both are still true, also couldn't find doc to quickly run tests and lint, should be some cmake targets? pointers appreciated if necessary :/ )

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


Ux improvements feb 22

yarn run v1.22.17
$ eslint .
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/1/

yarn run v1.22.17
$ eslint .
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/2/

yarn run v1.22.17
$ eslint .
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/3/

yarn run v1.22.17
$ eslint .
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/ActionItem/ActionItem.js
13:48  error  'onClose' is missing in props validation             react/prop-types
18:5   error  Trailing spaces not allowed                          no-trailing-spaces
31:7   error  'question' is never reassigned. Use 'const' instead  prefer-const
32:7   error  'answer' is never reassigned. Use 'const' instead    prefer-const
61:9   error  Props should be sorted alphabetically                react/jsx-sort-props
62:9   error  Props should be sorted alphabetically                react/jsx-sort-props
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/ActionItem/ManualResourceMappingCase.js
3:28  error<EMAIL_ADDRESS>imported multiple times  import/no-duplicates
6:32  error<EMAIL_ADDRESS>imported multiple times  import/no-duplicates
17:3   warning  'answer' is defined but never used. Allowed unused args must match /^_/u                                                            no-unused-vars
19:9   error    Identifier 'parsed_response' is not in camel case                                                                                camelcase
22:5   error    Identifier 'parsed_response' is not in camel case                                                                                camelcase
22:23  error    Unnecessary use of conditional expression for default assignment                                                                    no-unneeded-ternary
22:23  error    Identifier 'parsed_response' is not in camel case                                                                                camelcase
30:5   warning  Unexpected console statement                                                                                no-console
31:51  error    Expected property shorthand                                                                                object-shorthand
37:7   error    Expected property shorthand                                                                                object-shorthand
41:3   warning  Unexpected console statement                                                                                no-console
44:5   warning  Unexpected console statement                                                                                no-console
47:9   error    Identifier 'feedback_response' is not in camel case                                                                                camelcase
47:9   error    'feedback_response' is never reassigned. Use 'const' instead                                                                        prefer-const
53:5   warning  Unexpected console statement                                                                                no-console
58:9   error    Identifier 'post_feedback_request' is not in camel case                                                                             camelcase
58:9   error    'post_feedback_request' is never reassigned. Use 'const' instead                                                                    prefer-const
58:40  error    Identifier 'data_to_send' is not in camel case                                                                                camelcase
59:7   warning  Unexpected console statement                                                                                no-console
71:5   warning  Unexpected console statement                                                                                no-console
78:9   error    Identifier 'registry_entry' is not in camel case                                                                                camelcase
79:27  error    Identifier 'registry_entry' is not in camel case                                                                                camelcase
83:3   warning  Unexpected console statement                                                                                no-console
94:29  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
102:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
104:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
105:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
113:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
115:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
116:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
124:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
126:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
127:19  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
135:40  error    Expected '===' and instead saw '=='                                                                                eqeqeq
147:40  error    Expected '===' and instead saw '=='                                                                                eqeqeq
150:40  error    Expected '===' and instead saw '=='                                                                                eqeqeq
158:31  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/ActionItem/UnhandledFeedbackCase.js
1:17  warning  'useState' is defined but never used. Allowed unused vars must match /React/u   no-unused-vars
2:8   warning  'PropTypes' is defined but never used. Allowed unused vars must match /React/u  no-unused-vars
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/ActionItem/ValueMappingCase.js
12:64  warning  'answer' is defined but never used. Allowed unused args must match /^_/u  no-unused-vars
13:9   error    Identifier 'parsed_response' is not in camel case                         camelcase
16:5   error    Identifier 'parsed_response' is not in camel case                         camelcase
16:23  error    Unnecessary use of conditional expression for default assignment          no-unneeded-ternary
16:23  error    Identifier 'parsed_response' is not in camel case                         camelcase
21:3   error    Expected exception block, space or tab after '//' in comment              spaced-comment
23:3   error    Expected exception block, space or tab after '//' in comment              spaced-comment
27:5   warning  Unexpected console statement                                              no-console
28:51  error    Expected property shorthand                                               object-shorthand
32:5   warning  Unexpected console statement                                              no-console
35:9   error    Identifier 'feedback_response' is not in camel case                       camelcase
35:9   error    'feedback_response' is never reassigned. Use 'const' instead              prefer-const
41:5   warning  Unexpected console statement                                              no-console
46:9   error    Identifier 'post_feedback_request' is not in camel case                   camelcase
46:9   error    'post_feedback_request' is never reassigned. Use 'const' instead          prefer-const
46:40  error    Identifier 'data_to_send' is not in camel case                            camelcase
47:7   warning  Unexpected console statement                                              no-console
53:51  warning  Unexpected console statement                                              no-console
67:29  error    Props should be sorted alphabetically                                     react/jsx-sort-props
75:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
77:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
78:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
86:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
88:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
89:19  error    Props should be sorted alphabetically                                     react/jsx-sort-props
97:40  error    Expected '===' and instead saw '=='                                       eqeqeq
99:60  error    Props should be sorted alphabetically                                     react/jsx-sort-props
102:40  error    Expected '===' and instead saw '=='                                       eqeqeq
110:31  error    Props should be sorted alphabetically                                     react/jsx-sort-props
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/RemoteSyncView/RemoteSyncSummary.js
1:17  warning  'useState' is defined but never used. Allowed unused vars must match /React/u                                                             no-unused-vars
2:8   warning  'PropTypes' is defined but never used. Allowed unused vars must match /React/u                                                            no-unused-vars
3:32  error<EMAIL_ADDRESS>imported multiple times  import/no-duplicates
6:20  warning  'useMutation' is defined but never used. Allowed unused vars must match /React/u                                                          no-unused-vars
7:24  error<EMAIL_ADDRESS>imported multiple times  import/no-duplicates
24:43  error    Unexpected empty object pattern                                                                                no-empty-pattern
28:17  warning  'isLoading' is assigned a value but never used. Allowed unused vars must match /React/u                                                   no-unused-vars
28:28  warning  'refetch' is assigned a value but never used. Allowed unused vars must match /React/u                                                     no-unused-vars
32:13  error    Identifier 'sync_status_report' is not in camel case                                                                                camelcase
35:7   warning  Unexpected console statement                                                                                no-console
36:14  error    Identifier 'sync_status_report' is not in camel case                                                                                camelcase
41:5   warning  Unexpected console statement                                                                                no-console
42:9   error    Identifier 'trigger_worker_get' is not in camel case                                                                                camelcase
42:9   error    'trigger_worker_get' is never reassigned. Use 'const' instead                                                                             prefer-const
54:31  warning  Unexpected console statement                                                                                no-console
57:7   error    Identifier 'grid_rows' is not in camel case                                                                                camelcase
58:7   error    'arrows' is never reassigned. Use 'const' instead                                                                                prefer-const
61:5   error    Identifier 'grid_rows' is not in camel case                                                                                camelcase
67:53  error    Reserved props must be listed before all other props                                                                                react/jsx-sort-props
84:51  error    Reserved props must be listed before all other props                                                                                react/jsx-sort-props
113:11  error    Empty components are self-closing                                                                                react/self-closing-comp
125:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
126:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
127:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
128:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
135:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
136:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
137:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
138:13  error    Props should be sorted alphabetically                                                                                react/jsx-sort-props
144:5   warning  Unexpected console statement                                                                                no-console
156:10  error    Identifier 'grid_rows' is not in camel case                                                                                camelcase
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/RemoteSyncView/index.js
1:25  error  Unable to resolve path to module './RemoteSyncView'  import/no-unresolved
/home/jenkins/workspace/folio-org_ui-remote-sync_PR-62/project/src/components/TransformationProcessRecord/TransformationProcessRecord.js
10:55  error    'onClose' is missing in props validation                                                react/prop-types
32:5   warning  Unexpected console statement                                                            no-console
33:5   error    All 'var' declarations must be at the top of the function scope                         vars-on-top
33:5   error    Unexpected var, use let or const instead                                                no-var
33:9   warning  'testdata' is assigned a value but never used. Allowed unused vars must match /React/u  no-unused-vars
35:5   warning  Unexpected console statement                                                            no-console
39:29  error    Identifier 'json_record' is not in camel case                                           camelcase
✖ 113 problems (85 errors, 28 warnings)
52 errors and 0 warnings potentially fixable with the --fix option.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/4/

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/6/

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/7/

Test errors found. See https://jenkins-aws.indexdata.com/job/folio-org/job/ui-remote-sync/job/PR-62/8/


$ObjMap and splat gives incorrect results

When splatting the result of an $ObjMap, I seem to lose type safety (flow try link):
type A = {a: number};
type B = {...$ObjMap<A, <T>(T) => Array<T>>};
type C = {...$Exact<$ObjMap<A, <T>(T) => Array<T>>>};
type D = {...$ObjMap<$Exact<A>, <T>(T) => Array<T>>};
type E = {...$Exact<$ObjMap<$Exact<A>, <T>(T) => Array<T>>>};

({a: 'a'}: B);
({a: 'a'}: C);
({a: 'a'}: D);
({a: 'a'}: E);

It seems like no matter what combination of $Exact used (see https://github.com/facebook/flow/issues/3999), it says "No error!"

As of Flow 55, all of these now error and give messages that seem right to me.


Enhance support for Checksums

Describe the enhancement
Continuation of #5130, #5138

[ ] Support cksum format checksum size and checksum size name (not popular enough?)
[ ] Add .digest and .cksum to extensions
[ ] Add digest to aliases
[ ] Support popular formats in .digest files

@Alhadis, this is from #5130:

but is there a way to highlight it when it is explicitly specified, such as ```hash blocks in Markdown?

Unfortunately not. ```hash blocks are highlighted by the same mechanism responsible for highlighting a file's source-code. For all intents and purposes, they're exactly the same.

Don't the blocks below highlight differently? They are ```c, ```html, and ``` blocks, respectively.
int main() {} // <strong attr="val">HTML</strong>

int main() {} // <strong attr="val">HTML</strong>

int main() {} // <strong attr="val">HTML</strong>

Here's what I was trying to get at with that post:
Since the highlighting can be controlled by the info string after the three backticks, how does that work? Is it related to the aliases property? If so, can we use that to let users specify cksum specifically? Or is cksum not even popular enough for us to care about?

Since the highlighting can be controlled by the info string after the three backticks, how does that work? Is it related to the aliases property?

Yes, if the content of that infostring matches the language name or any of its aliases then that language is applied.

@theonlypwner Any of the aliases listed in languages.yml will activate checksum highlighting. Be aware that there's no correlation between which alias you pick and what checksums get highlighted; i.e., all supported checksum patterns will be highlighted, even if the code-block was tagged with, say, ```md5 (a hypothetical example, seeing as how md5 isn't currently supported as an alias).

If so, can we use that to let users specify cksum specifically? Or is cksum not even popular enough for us to care about?

I think we can add cksum as an alias. As a file-extension, a quick search for *.cksum files shows there's some usage on GitHub. You'll need to submit a pull-request and wait for @lildude to run an evaluation of its usage to know for sure, though.

@Alhadis My point was that if we create another language entry with aliases, filenames, and extensions specifically for cksum, we can highlight in the cksum format for only  ```cksum blocks and *.cksum files because you said it's better to have no highlighting than wrong highlighting. Creating another language entry would create the correlation between the chosen alias and how the highlighting is performed.
But if the cksum format isn't popular enough, then it might not be necessary. In a search for *.cksum files, most results look like the SHA1SUMS file format, which is already supported. I would recommend adding .cksum to extensions, which I have added to the task list. I don't think it is necessary to add cksum to aliases.

I will also respond to your other comment in #5138 here:

Well, I can add support for patterns like this…
digest1:dwLYXWqDkzaJhlo1P6sQqpxgU5cBRRYM9Sna/buqhHIoAX6/np9fYp9Zbgb3Rc7I

… however, I'm unfamiliar with whatever program generates this kind of output, and I'd ideally like some authoritative reference on what formats are accepted in such lines (the example looks to be using base64, but I'd rather not go by guesswork if I can help it).

It seems like digest1: is an encryption prefix in GeoServer passwd files. That prefix, crypt1:, and crypt2: precede a base64 string, while plain: precedes a plaintext password. Should passwd-type files also be included in the Checksums language, or should that be in another language like passwd?

Also, I noticed some files in the format name whitespace hash instead of hash whitespace name, which I hope either won't cause issues for the syntax highlighter or can be fixed later.

There's no foolproof way to tell name hash from a filename that contains spaces, followed by a word that happens to contain n alphanumeric characters. Conversely, a line that begins with precisely n characters is a little less ambiguous. Consider files that begin with arbitrary text (e.g., comments), or even files like this that aren't technically a checksum list, but are still highlighted non-intrusively.

If there's no foolproof way, should we just simply give up and not support the name hash format?


HBASE-22978 : Online slow response log

Signed-off-by: Bharath Vissapragada<EMAIL_ADDRESS>branch-2 backport of https://github.com/apache/hbase/commit/b24ea32b3ba13b020c194795558b358e4d4b7eda

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 23s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+0 :ok:
prototool
0m  1s
prototool was not available.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 6 new or modified test files.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 15s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 58s
branch-2 passed

+1 :green_heart:
compile
3m 21s
branch-2 passed

+1 :green_heart:
checkstyle
5m 19s
branch-2 passed

+0 :ok:
refguide
11m 48s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
4m 43s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
5m 14s
branch-2 passed

+0 :ok:
spotbugs
1m 25s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
23m  3s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
5m 33s
the patch passed

+1 :green_heart:
compile
3m 20s
the patch passed

+1 :green_heart:
cc
3m 20s
the patch passed

+1 :green_heart:
javac
3m 20s
the patch passed

+1 :green_heart:
checkstyle
0m 10s
The patch passed checkstyle in hbase-protocol-shaded

+1 :green_heart:
checkstyle
0m 24s
The patch passed checkstyle in hbase-common

+1 :green_heart:
checkstyle
0m 39s
The patch passed checkstyle in hbase-client

+1 :green_heart:
checkstyle
1m 17s
hbase-server: The patch generated 0 new + 139 unchanged - 1 fixed = 139 total (was 140)

+1 :green_heart:
checkstyle
0m 39s
The patch passed checkstyle in hbase-thrift

+1 :green_heart:
checkstyle
0m 10s
The patch passed checkstyle in hbase-shell

+1 :green_heart:
checkstyle
2m  1s
root: The patch generated 0 new + 569 unchanged - 1 fixed = 569 total (was 570)

+1 :green_heart:
rubocop
0m 11s
There were no new rubocop issues.

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  4s
The patch has no ill-formed XML file.

+0 :ok:
refguide
7m  7s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
shadedjars
4m 42s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
17m 31s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

+1 :green_heart:
hbaseprotoc
8m 47s
the patch passed

+1 :green_heart:
javadoc
5m 25s
the patch passed

+1 :green_heart:
findbugs
24m 25s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
147m 29s
root in the patch passed.

+1 :green_heart:
asflicense
3m 26s
The patch does not generate ASF License warnings.

303m 14s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1228/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1228

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile refguide xml cc hbaseprotoc prototool rubocop

uname
Linux cef71b6732a1 4.15.0-74-generic #84-Ubuntu SMP Thu Dec 19 08:06:28 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1228/out/precommit/personality/provided.sh

git revision
branch-2 / 836e1a1caf

Default Java
1.8.0_181

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1228/1/artifact/out/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1228/1/artifact/out/patch-site/book.html

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1228/1/testReport/

Max. process+thread count
7523 (vs. ulimit of 10000)

modules
C: hbase-protocol-shaded hbase-common hbase-client hbase-server hbase-thrift hbase-shell . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1228/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11 rubocop=0.80.0

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


why quic-go is slower than websocet?

hi, all, when i using the latest release code to test, creating 10 streams in one session, and each sending 10MB file, is slower than 10 websocket connection. And the pseudo code as follows:
quic client;
session := quic.DialAddr()
startTime := time.Now()
var wg sync.WaitGroup
wg.Add(10)
for i :=0; i<10; i++{
go func(){
stream, := session.OpenStream()
stream.Write([]byte{10MB})
wg.Done()
}()
}
wg.Wait()
endTime := time.Now()
diff := endTime.Sub(startTime0
And the websocket client:
startTime := time.Now()
var wg sync.WaitGroup
wg.Add(10)
for i :=0; i<10; i++{
go func() {
lock.lock()
c := websocket.DIal()
c.WriteMessage(c, []byte{10MB})
lock.Unlock()
wg.Done()
}()
}
wg.Wait()
endTime := time.Now()
diff := endTime.Sub(startTime0
through the code, i found all stream write will through the session.run(), so the packet will send  in order, not really concurrently writing, while we can run many thread, and write the packet without lock in c and the UDP socket. can anybody know that how can we increase the performance.

QUIC is not expected to be faster on local transfers. Why would it be?


stardust-xr-protostar: 0-unstable-2024-07-19 -> 0-unstable-2024-12-29

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for stardust-xr-protostar is: Prototype application launchers for Stardust XR
meta.homepage for stardust-xr-protostar is: https://stardustxr.org
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0-unstable-2024-12-29 in filename of file in /nix/store/nq44jg3jayi807hawc7158kln1wpv99s-stardust-xr-protostar-0-unstable-2024-12-29

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

stardust-xr-protostar

Instructions to test this update (click to expand)

Either download from the cache:
nix-store -r /nix/store/nq44jg3jayi807hawc7158kln1wpv99s-stardust-xr-protostar-0-unstable-2024-12-29 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A stardust-xr-protostar https://github.com/r-ryantm/nixpkgs/archive/5594c47eb25ff63f1619952f45cac27313471fd7.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/5594c47eb25ff63f1619952f45cac27313471fd7#stardust-xr-protostar

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/nq44jg3jayi807hawc7158kln1wpv99s-stardust-xr-protostar-0-unstable-2024-12-29
ls -la /nix/store/nq44jg3jayi807hawc7158kln1wpv99s-stardust-xr-protostar-0-unstable-2024-12-29/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

stardust-xr-protostar

Maintainer pings
cc @Pandapip1 @technobaboo for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

@NixOS/nixpkgs-merge-bot merge
No apparent code changes


Electrum does not show one of two BTC addresses contained on ledger

A friend of mine has a (non-segwit) account on his ledger with 2 BTC addresses containing BTC as of the time of the hard fork (28.2.18) and still today. Both addresses belong to the same account. The Electrum wallet for BTCP does only show one of the two addresses. The other one is not shown and therefore he has no access to his BTCP.
Is there a way to convert a public BTC address to the corresponding BTCP address? This would help to check whether the BTCP explorer at least shows the right content.

I have found a website (findmycoins.ninja) which shows me the respective BTCP address and there I can see that the blockchain correctly holds the BTCP. The error seems to be with the Electrum wallet which does not show the address although it belongs to the displayed HD wallet.

You probably need to generate more addresses. Either that or your coins are in a change address.

Check here in the gap limit section and the way to generate more addresses in the console:
http://docs.electrum.org/en/latest/faq.html

The address which I miss is a change address, resulting from an outbound transfer. I can generate a lot of new addresses but this does not make visible the missing address. Anyway the one address which is visible was one that I created later then the missing one. If addresses get generated in a given order based on the public master key then the Electrum wallet should have seen it before the one which is visible because it got created earlier!? Or is there some other algorithm with change addresses? Then how will it be either possible to access them without a transaction history?

I found the solution!
I can force Electrum wallet to generate change addresses instead of receive addresses! That finally generated the missed address!
Use the following command in the console:
print(wallet.create_new_address(True))
Repeat it until the address pops up (balance changes). Or use a loop:
for x in range(0, 100): print(wallet.create_new_address(True))


define cosine similarity function

Fixes issue https://github.com/autodistill/autodistill/issues/137

@lakshmanmoiiai Thank you for your contribution! Your code looks good, although we need you to accept the CLA before we can merge it. Please accept the CLA at: https://github.com/autodistill/autodistill/pull/138#issuecomment-1961241363

Following up on this :)

A fix for this was introduced in #163, so I am going to close this PR. If you want to replace the current solution, feel free to submit a new PR.


Support for PHP 8+

Hi
I was looking for a tools like this for a while and it seems to be what I'm looking for but, if I'm not wrong, it do not support PHP version greater than 7.2.
Is there a plan to support PHP 8?

Hi, happy New Year and thank you for the reminder. There's a PR out with
support for 8 that I have to get merged. I'll try to get it done this week
😉
El jue, 12 ene 2023 7:12, Aurélien Tournayre @.***>
escribió:

Hi
I was looking for a tools like this for a while and it seems to be what
I'm looking for but, if I'm not wrong, it do not support PHP version
greater than 7.2.
Is there a plan to support PHP 8?
—
Reply to this email directly, view it on GitHub
https://github.com/mihaeu/dephpend/issues/78, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQRO7OVBWRQVP73NR573WDWR6OFTANCNFSM6AAAAAATY3QWG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Happy New Year too!
I can't wait for the PR to be merged so I can test :wink:

First of all thank you for creating this tool, it's great. Any news about this issue? Do you need any help so you can merge that PR soon?
Thank you

@mihaeu Any update?

Any update?


CreateContainerIfNotExistsAsync Crashes without exception when running in xUnit

Describe the bug
Using the local emulator or azure instance, CreateContainerIfNotExistsAsync crashes out the xUnit application without any exception. The offending line is in TransportHandler.cs line 87. The same code runs fine in a Console application
To Reproduce
using (var client = new CosmosClient("AccountEndpoint=https://localhost:8081/;AccountKey=C2y6yDjf5/R+ob0N8A7Cgv30VRDJIWEHLM+4QDU5DE2nQ9nDuVTqobD4b8mGGyPMbIZnqyMsEcaGQy67XIw/Jw=="))
{
    var database = await client.Databases.CreateDatabaseIfNotExistsAsync(_databaseId);
}

Expected behavior
At a minimum some exception
Actual behavior
Blows out the application
Environment summary
SDK Version: NetCore 3.0.100-preview5-011363 with Cosmos source
OS Version Windows

Closing this since there has been no updates. Please reopen if it still an issue.

+1 CreateDatabaseIfNotExistsAsync can hang forever, or crash with no exception


Add publish github action to replace quay builds

Description
Test using github actions for build and push instead of quay. This will prevent docker rate limiting errors when building.
If this works here for awhile the intention is to do so in all MTC repos.
Check each of the following when appropriate to help reviewers verify work is complete.
Modifying an existing version

[ ] I modified operator permissions in the OLM CSV and operator.yml
[ ] I modified the operator deployment in the OLM CSV and operator.yml
[ ] I modified operand permissions in the OLM CSV and ansible role
[ ] I modified CRDS in the OLM CSV and ansible role

Adding a new release version

[ ] I created a new z release directory in deploy/olm-catalog/crane-operator
[ ] I updated channels in the crane-operator.package.yaml
[ ] I created a new release directory in deploy/non-olm
[ ] I created or updated the major.minor link in deploy/non-olm
[ ] I updated the spec.skips parameter in the CSV

Successful run on my personal master branch:
https://github.com/jmontleon/mig-operator/actions/runs/961777028
Successful run on my personal release-1.99.99 branch:
https://github.com/jmontleon/mig-operator/actions/runs/961800939
Tags from these runs on mig-operator-container:
https://quay.io/repository/jmontleon/mig-operator-container?tab=tags
Tags from these runs on mig-operator-bundle:
https://quay.io/repository/jmontleon/mig-operator-bundle?tab=tags
Note for master we also push to latest just like quay does.

I'll disable the autoamted builds in quay after this is reviewd and approved before merging.

/lgtm
Wondering if we should also publish an index image?

/lgtm
Wondering if we should also publish an index image?

I have a separate PR started for metadata. I am trying to think on how to do this and update multiple channels intelligeantly.

I made an update. I just made the secret names a little more descriptive and added the sprint-* branches auto build as well.
If this works out for the operator and I expand it to all the other repos I can probably take out these stupid waits I put in so quay wouldn't drop our builds (they have a max number of builds you can kick off per some period, but I've yet to find it documented).
https://github.com/konveyor/mig-operator/blob/master/deploy/sprint-build.yml#L92-L94

/lgtm
Wondering if we should also publish an index image?

I have a separate PR started for metadata. I am trying to think on how to do this and update multiple channels intelligeantly. I might start with dev alone since that case is a little easier, although we still have to do something to tell it what the previous built up index image.... whether we hard code something and update it periodically, or, I don't know.
I guess we could just carry the head of the two most recent channels plus devel and allows combine, e.g. 1.3.2, 1.4.5, and devel and update a list periodically?
I don't know if I'm overthinking it, but I'm basically asking/looking for ideas on how to do this without writing something insanely complex that covers the 99% case of giving people and developers access to Crane with our catalogsource.

@shawn-hurley what if we did this with a github action that has a list of supported channels like:
channels:
- release-v1.5
- release-v1.4
- release-v1.3

For development we always just use the head of the default branch.
When we finish a release we move a tag release-v1.5 from the release-1.5.0 branch to the release-1.5.1 branch etc.
Then we can use the tag to find the right bundles in order to build and push an index image that combines the latest bundles for whatever channels we want.


2021-01-31 kickoff

Which issue this PR addresses:
Enables us to start developing new API 2020-01-31-preview and test it in dev
What this PR does / why we need it:
This will make an extension to call preview API exclusively.
If you are using an extension to interact with production RP - this will stop working. Please offload the extension for these activities.
Pulled back ^ as we might want to discuss more. But I have a feeling this will be "Told you so". Sometimes we have to break things for sake of progress...
All E2E in dev will be running on preview API.
All E2E in PROD and INT will be running on stable API
Next will be swagger and cli generation WITH new fields and submission initial swagger for review: https://github.com/Azure/ARO-RP/compare/master...mjudeikis:api.skeleton?expand=1
Test plan for issue:
In development
Is there any documentation that needs to be updated for this PR?
This is just the beginning. Later - yet.

/azp run e2e

/azp run e2e


Empty Relations are not sent.

For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!

[x] You've met the prerequisites.

[x] You're running the latest version of Parse Server.

[x] You've searched through existing issues. Chances are that your issue has been reported or resolved before.

Environment Setup
VERBOSE=1
Steps to reproduce
Same as the issue #1136, it is really hard to reproduce but I put every detail in the logs
Logs/Trace
So, the problem is pretty simple, there is a difference between the parse.com response and the parse-server response. I do not know if it is by design but what I know is that it makes my app crash :laughing:
The idea is that parse-server does not send the existence of the relation in the object (even if they are in schema):
Parse-Server
{
	"objectId": "8RZCH4EdCL",
	"location": {
		"__type": "GeoPoint",
		"latitude": 48.137004,
		"longitude": 11.575928
	},
	"criteria": [{
		"key": "Deutsch - fließend",
		"status": true
	}, {
		"key": "Führerschein-Klasse B",
		"status": true
	}],
	"merchant": {
		"ACL": {
			"km36mV2uG2": {
				"read": true,
				"write": true
			},
			"*": {
				"read": true
			}
		},
		"objectId": "km36mV2uG2",
		"address": {
			"__type": "GeoPoint",
			"latitude": 51.6102001,
			"longitude": 0.5754663000000164
		},
		"username"<EMAIL_ADDRESS>		"email"<EMAIL_ADDRESS>		"merchant": true,
		"salutation": "test",
		"firstName": "test",
		"lastName": "test",
		"name": "test test test",
		"addressString": "Rawreth, Wickford, Essex SS11, UK",
		"company": "test",
		"phone": "11",
		"emailOpen": true,
		"phoneOpen": false,
		"updatedAt": "2016-03-21T19:23:23.732Z",
		"createdAt": "2016-03-21T19:21:41.325Z",
		"emailVerified": true,
		"__type": "Object",
		"className": "_User"
	},
	"title": "test",
	"salaryAmount": 1111,
	"description": "test",
	"finished": false,
	"category": {
		"__type": "Pointer",
		"className": "Category",
		"objectId": "MnaaKc2Rn1"
	},
	"salaryGiven": true,
	"salaryTimeUnit": "pro Monat",
	"updatedAt": "2016-03-21T19:25:27.661Z",
	"createdAt": "2016-03-21T19:25:27.661Z"
}

Likes, Matches and Dislikes are missing. However they're in Parse.com
{
	"createdAt": "2016-02-27T17:43:06.241Z",
	"criteria": [{
		"key": "Deutsch - fließend",
		"status": true
	}, {
		"key": "Mindestens 18 Jahre alt",
		"status": true
	}],
	"description": "I love the tests",
	"dislikes": {
		"__type": "Relation",
		"className": "_User"
	},
	"likes": {
		"__type": "Relation",
		"className": "_User"
	},
	"location": {
		"__type": "GeoPoint",
		"latitude": 48.137004,
		"longitude": 11.575928
	},
	"matches": {
		"__type": "Relation",
		"className": "_User"
	},
	"merchant": {
		"Criteria": [],
		"__type": "Object",
		"className": "_User",
		"createdAt": "2016-02-27T17:14:40.294Z",
		"email"<EMAIL_ADDRESS>		"emailVerified": true,
		"firstName": "Laurent",
		"lastName": "Meyer",
		"objectId": "ver8RkWZIQ",
		"test": {
			"__type": "Relation",
			"className": "_User"
		},
		"updatedAt": "2016-02-27T19:12:04.381Z",
		"username": "lolobosseMerchant"
	},
	"objectId": "3ZWdQStMRy",
	"selected": {
		"__type": "Pointer",
		"className": "_User",
		"objectId": "XiVpb2r6LJ"
	},
	"title": "I test the QA2",
	"updatedAt": "2016-03-22T18:41:42.447Z"
}

For the sceptical here is my schema from Parse server:
{
   "className":"Job",
   "fields":{
      "title":{
         "type":"String"
      },
      "merchant":{
         "type":"Pointer",
         "targetClass":"_User"
      },
      "matches":{
         "type":"Relation",
         "targetClass":"_User"
      },
      "likes":{
         "type":"Relation",
         "targetClass":"_User"
      },
      "description":{
         "type":"String"
      },
      "finished":{
         "type":"Boolean"
      },
      "salaryTimeUnit":{
         "type":"String"
      },
      "salaryAmount":{
         "type":"Number"
      },
      "location":{
         "type":"GeoPoint"
      },
      "dislikes":{
         "type":"Relation",
         "targetClass":"_User"
      },
      "reviewed":{
         "type":"Boolean"
      },
      "selected":{
         "type":"Pointer",
         "targetClass":"_User"
      },
      "reviewed_by_user":{
         "type":"Boolean"
      },
      "category":{
         "type":"Pointer",
         "targetClass":"Category"
      },
      "criteria":{
         "type":"Array"
      },
      "salaryGiven":{
         "type":"Boolean"
      },
      "fromDetailView":{
         "type":"Boolean"
      },
      "createdBy":{
         "type":"Pointer",
         "targetClass":"_User"
      },
      "ACL":{
         "type":"ACL"
      },
      "createdAt":{
         "type":"Date"
      },
      "updatedAt":{
         "type":"Date"
      },
      "objectId":{
         "type":"String"
      }
   },
   "classLevelPermissions":{
      "find":{
         "*":true
      },
      "get":{
         "*":true
      },
      "create":{
         "*":true
      },
      "update":{
         "*":true
      },
      "delete":{
         "*":true
      },
      "addField":{
         "*":true
      },
      "readUserFields":[

      ],
      "writeUserFields":[

      ]
   }
}

Did I miss something or it is actually a bug?

duplicate from #1311


fix(quota): consumption -> consumed

Small fix to use consumed as the quota key instead of consumption. consumed is what we're seeing on the final API but consumption was used in original design doc. This PR also updates our tests and fixtures to use the same key.
Testing

Trade-offs

Dependencies

Screenshots

:tada: This PR is included in version 2.124.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


🐛 [qBittorrent] OpenVPN password escaping not handled

Description
Open VPN passwords that contain special characters in the same syntax of string escapes are not handled correctly.
In this example & does not properly execute.
This was not an issue on build 4.6.2.
Reproduction steps
1. Navigate to qBittorrent AddOn Configuration page
2. Enable "openvpn_eanbled"
3. Set up all the openVPN settings.
4. Have a "openvpn_password" that contains a special character that is escaped. (e.g. \&, \c, \\, \8 etc.)

Addon Logs
Starting...
/etc/cont-init.d/00-banner.sh: executing

-----------------------------------------------------------
 Add-on: qBittorrent
 bittorrent client with optional vpn
-----------------------------------------------------------
 Add-on version: 4.6.4-2
 You are running the latest version of this add-on.
 System: Home Assistant OS 12.2  (aarch64 / yellow)
 Home Assistant Core: 2024.4.3
 Home Assistant Supervisor: 2024.04.0
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums
-----------------------------------------------------------
 Provided by: https://github.com/alexbelgium/hassio-addons
-----------------------------------------------------------
 Defining permissions for main user :
User UID: 1000
User GID : 1000
-----------------------------------------------------------
/etc/cont-init.d/00-folders.sh: executing
/etc/cont-init.d/00-global_var.sh: executing
DNS_server='<IP_ADDRESS>,<IP_ADDRESS>'
PGID='1000'
PUID='1000'
SavePath='/somesavepath'
Username='<someusername>'
certfile='fullchain.pem'
customUI='vuetorrent'
keyfile='privkey.pem'
localdisks='somelocaldisk'
openvpn_config='<someconnection>.ovpn'
openvpn_enabled='true'
openvpn_password='\&'
/env.py:13: SyntaxWarning: invalid escape sequence '\&'
  os.environ['openvpn_password'] = '\&'
openvpn_username='<someusername>'
/env.py:13: SyntaxWarning: invalid escape sequence '\&'
  os.environ['openvpn_password'] = '\&'
qbit_manage='false'
/env.py:13: SyntaxWarning: invalid escape sequence '\&'
  os.environ['openvpn_password'] = '\&'
ssl='false'
/env.py:13: SyntaxWarning: invalid escape sequence '\&'
  os.environ['openvpn_password'] = '\&'
whitelist='localhost'
/env.py:13: SyntaxWarning: invalid escape sequence '\&'
  os.environ['openvpn_password'] = '\&'
/etc/cont-init.d/00-local_mounts.sh: executing
---------------------------------------------------
[13:27:38] INFO: Available Disks for mounting :
NAME         LABEL     SIZE FSTYPE RO
└─sda1       STORAGE 931.5G ext4    0
---------------------------------------------------
Supported fs :  ext3 ext2 ext4 squashfs vfat msdos f2fs fuseblk
Inspired from : github.com/dianlight
---------------------------------------------------
Local Disks mounting...
... sda1 is a physical device
[13:27:38] INFO: Mounting sda1 of type ext4
[13:27:38] INFO: Success! sda1 mounted to /mnt/somedrive
/etc/cont-init.d/00-smb_mounts.sh: executing

Architecture
No response
OS
HAos

Thanks! I'll check what can have changed in my code lately. Sorry for the issue

To be sure to understand : in the addon iron your password is only & or it is a string containing it?

When you type your password I think it should be the exact openvpn password, the escape happens when exporting the variables in my script

I have tried and can't replicate for & :
/etc/cont-init.d/00-global_var.sh: executing
DNS_server='<IP_ADDRESS>,<IP_ADDRESS>'
PGID='0'
PUID='0'
SavePath='/mnt/xxx/downloads'
Username='admin'
certfile='fullchain.pem'
cifspassword='xxx'
cifsusername='xxx'
customUI='vuetorrent'
keyfile='privkey.pem'
localdisks='xxx'
openvpn_alt_mode='false'
openvpn_enabled='false'
openvpn_password='#%^*+=-/:;()€&@'
openvpn_username='xxx'

So after analysis the only characters that dob't work are ' " and \ as they are understood as operators. Are those characters present in usual openvpn passwords? It's complex to use those due to interference but if needed I could think of a way to sanitize it

By default HA uses "" for variables in it's yaml config so I don't think that it would support it anyway...


Generated code produces errors when "noImplicitAny": true is used

We get the following errors when enabling the noImplicitAny option in TypeScript compiler when using the angular2-webpack-starter project:
ERROR in [default] /src/main.browser.ts:26:32
Parameter 'status' implicitly has an 'any' type.

ERROR in [default] /src/main.browser.ts:31:32
Parameter 'err' implicitly has an 'any' type.

ERROR in [default] /src/main.browser.ts:31:37
Parameter 'outdatedModules' implicitly has an 'any' type.

ERROR in [default] /src/main.browser.ts:36:34
Parameter 'dependencies' implicitly has an 'any' type.

This is caused by code that is being patched in by the hmr-loader into the bootstrapping code. The solution seems simple, add missing any type annotations. However I'm not sure whether this module is used for projects that don't use TypeScript, which would produce syntax errors for them.
A better solution would be to patch in a function call instead of raw code and to hold the implementation of this function inside of this library so that TypeScript won't ever type check the code. But for this I have no idea how to support the different available module systems to import the function that will be patched in.
Any suggestions?

I also have this problem, but I think it depends on the order in which the typescript and the hmr loaders are used...

Yeah, I saw that the loader order was changed in the AngularClass/angular2-webpack-starter , seemingly to work around this problem. This solves the problem for me.


Load geometry from STL files

Closes #49
Also significantly improves update rendering time in the JSON display when using large geometry files, doing parent assignment and in an existing O(n) loop rather than a separate O(n2) loop

Codecov Report

Merging #50 into master will decrease coverage by 1.1%.
The diff coverage is 74.28%.

@@            Coverage Diff             @@
##           master      #50      +/-   ##
==========================================
- Coverage   81.83%   80.72%   -1.11%
==========================================
  Files           9        9
  Lines         765      768       +3
==========================================
- Hits          626      620       -6
- Misses        139      148       +9

Impacted Files
Coverage Δ

geometry_constructor/qml_json_model.py
99.21% <100%> (-0.06%)
:arrow_down:

geometry_constructor/geometry_models.py
62.74% <55%> (-5.04%)
:arrow_down:

Continue to review full report at Codecov.

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


strokeDashArray instead of strokeDasharray

detail ...

Are you sure? strokeDasharray is just the camelCase version of the CSS property stroke-dasharray.

Google tells me that you are right :-)
It felt wrong linguistically.


Async lookups-cached-global by default

Also better lookup docs

Between this and #3068 I think this
fixes #3063

@drcrallen I think as-is, setting firstCacheTimeout to 0 will cause the manager to report failure in scheduleAndWait, leading to a bunch of error messages and also to delete(id) getting called. If it's meant to act async-y it should report success even if the task hasn't finished yet.

@gianm that was missing a test. Fixed that case

👍  looks good!

👍


fix: Return whole pages by default for _method_pages; pass record_key_list to get old behaviour

See issue #8
Currently for all paged calls, when you make the API call you get a generator back. Each iteration of the generator, if necessary, makes a page request. It then yields a single element of (hopefully) what you were looking to obtain (e.g. orders for get_orders). This makes building a list of these, or dealing with them, very easy, but there are some potential issues which this method and its implementation.

A guess is made at the entry of interest by looking through the response for a list. If the response contains any other lists, e.g. the buy_browse_search call which may return an autoCorrections container, then the wrong entry may be returned.
Warnings are lost (unless they accidentally get selected as the entry of interest, in which case all you get is the warnings).

To deal with this, I propose adding a 'record_list_key' keyword parameter, default value None, to method_paged. When set to None, api calls will return of list of the complete response from each API call (including prev, next, limit, offset, total etc). This would also include any warnings or additional list entries (such as autoCorrections). However, this does mean the user needs to spend a (trivial) amount of extra time assembling their fields of choice.
Another issue is that it is not possible to limit the number of records exactly, as it is not known which element is actually to be limited. It is possible to only retrieve the necessary number of pages, however, so a user may get 400 elements (two pages) when they only want 350, but they will not get 10,000.
If the user supplies a record_list_key, then the previous behaviour will apply, except that now there is no need for guessing the correct list element so the correct field of interest will always be returned. It is, as before, trivial to return exactly the desired number of elements to the user (and to discard additional elements returned with the final page).
THIS IS A BREAKING CHANGE - another option would be to make 'auto' the record_key_list default which would attempt to guess the correct response field that is being paged, which would preserve the current default behaviour.

Probably this breaks the paged tests and would need documentation updates (unless I added the 'auto' feature)...

Look here for why this was closed.


CI Updates

          1 Error

:no_entry_sign:
Please include an entry in CHANGELOG.md—if this is a trivial Pull Request that does not require a changelog entry please include #trivial in the title.

          1 Warning

:warning:
package.json was edited.

          1 Message

:book:
:tada:  Thanks for the Pull Request!

  Generated by :no_entry_sign: Danger


added .vscode to gitignore and correct the decoded outputs and targets

Now the console output is:
Inference results TARGET: a b  c d  ...
It should be:
Inference results TARGET: ab cd ...

I signed it!

It has been fixed in master.


CAN RX interrupt

Hi again
Yes you were right, I'm reverting to your version of the interrupt, except for one thing. You don't need my if (FNRB == FBP) break at the end of the loop, it will recover anyway, so here's a commit to remove this. This should also reduce the number of dropped messages during recovery.
I have verified and seen that it will just enter the "This should not happen" case a couple of times until FBP catches up with FNRB and then it will be back to normal again.
Thanks for all the help!

Oops sorry for my lack of github skills, the diff is correct but there's only supposed to be one commit here (the last one)
BR /Jens

Hi Jens,
I updated the code with your last commit. Thank you.


Generate more idiomatic Flux in query builder

Closes #13775
Updates the Flux code generated by the query builder to use the aggregateWindow helper when possible. Queries previously generated like so:
from(bucket: "telegraf")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r._measurement == "cpu" or r._measurement == "disk")
  |> filter(fn: (r) => r._field == "used_percent")
  |> window(period: v.windowPeriod)
  |> mean()
  |> group(columns: ["_value", "_time", "_start", "_stop"], mode: "except")
  |> yield(name: "mean")

Will now be generated as:
from(bucket: "telegraf")
  |> range(start: v.timeRangeStart, stop: v.timeRangeStop)
  |> filter(fn: (r) => r._measurement == "cpu" or r._measurement == "disk")
  |> filter(fn: (r) => r._field == "used_percent")
  |> aggregateWindow(every: v.windowPeriod, fn: mean)
  |> yield(name: "mean")

any idea how we could keep track of the number type issue nathaniel highlighted? It's certainly going to come up again.

Yeah not sure... maybe it makes sense to wait until the issue is reported by a user, so we have a more acute description of the problem. Or we could create an issue—my worry is that the issue would be too broad of a problem statement and unactionable.

any idea how we could keep track of the number type issue nathaniel highlighted? It's certainly going to come up again.

Eventually I expect this to be something that a Flux language server could expose. Not sure exactly the details of how that will all work, but this kind of thing is a type error which in many cases should be discoverable statically.


OpenXR & Radeon 7900XTX & iRacing

When playing Iracing through openXR (mixed reality) the game flashes constantly in red in both eyes, makes its unplayable.
Not sure where and how to report this properly. Could be drivers issue? Or iracing implementation? Or openxr compatibility issue with new AMD cards?
Video: https://youtu.be/yoAwpAsAQ-4

Issue found: ingame built in antialiasing creates red artefacts. Only with openxr & new amd card.

Closing as 3rd party driver issue.


Merge missing 1.3.0 tag changes

Merges up the 1.3.0 tag contents to master.

This PR contains and additional weird commit, so I redid it at #199

It was an annotated merge, I just documented what was being done, so it was more understandable.

Sorry, github doesn't play well with manual merges, and had me confused there.


Can't load icon font

Hi.
I just can't find solution for icon font not loading on pages. It is a local Windows install, everything updated to latest version through npm. Didn't do any customizations to theme files so far. It is a clean install.
I see that component icon.css is importing icons from url(".../themes/default/assets/fonts/icons.eot");  (There is " \ " after first dot, but Github doesn't outputs it).  Where " \ " should be "/ ".
Tried for testing purposes to change that to url("./../themes/default/assets/fonts/icons.eot"); but it still doesn't load, in debuger I see error:
downloadable font: download failed (font-family: "Icons" style:normal weight:normal stretch:normal src index:3): bad URI or cross-site access not allowed source: file:///E:/GoogleDrive/PROJECTS/my-framework/semantic/dist/themes/default/assets/fonts/icons.ttf
If you could tell me am I doing something wrong and how to fix it, or is it a bug in Semantic.

Ok, I found the reason why url("./../themes/default/assets/fonts/icons.eot"); did not work. I transfered it to local server and it loaded icon font.
But when I run gulp build it makes url(".../themes/default/assets/fonts/icons.eot"); again.
How to overide that?

I had this same issue. Had to modify the template.
@fontName: 'icons';
@fallbackSRC: url("/Content/@{fontPath}/@{fontName}.eot");
@src:
  url("/Content/@{fontPath}/@{fontName}.eot?#iefix") format('embedded-opentype'),
  url("/Content/<EMAIL_ADDRESS>format('woff2'),
  url("/Content/<EMAIL_ADDRESS>format('woff'),
  url("/Content/<EMAIL_ADDRESS>format('truetype'),
  url("/Content/<EMAIL_ADDRESS>format('svg')
;

i just removed dots before "\themes" in semantic.css
it's working now
@font-face {   font-family: 'Icons';   src: url("\themes/default/assets/fonts/icons.eot");   src: url("\themes/default/assets/fonts/icons.eot?#iefix") format('embedded-opentype'), url("\themes/default/assets/fonts/icons.woff2") format('woff2'), url("\themes/default/assets/fonts/icons.woff") format('woff'), url("\themes/default/assets/fonts/icons.ttf") format('truetype'), url("\themes/default/assets/fonts/icons.svg#icons") format('svg');

Still an invalid url though, so not the best way to go. @jlukic I know you're busy, but is this a Windows thing?

I have a partial fix. I am using Windows 7. It is the most stable environment for me still.
Added @fontPath: "./../themes/default/assets/fonts"; to semantic/src/site/elements/icon.variables and it fixed path in dist/components/icon.css
Added also @fontPath: "./themes/default/assets/fonts"; to semantic/src/site/global/site.variables but it did not fix the path in dist/semantic.css but outputs the same path as in dist/components/icon.css
Maybe @jlukic can help with that?

@rlightner "Had to modify the template."
WHICH template?

I know it’s been a while, but apparently it was fixed somewhere in-between.

Fixed for semantic-ui-less here: https://github.com/grinich/Semantic-UI-LESS/commit/fb74dbc47628098a14be92767d05f8a82c480675

A fix is available here for semantic-ui-less: https://github.com/grinich/Semantic-UI-LESS/commit/fb74dbc47628098a14be92767d05f8a82c480675


Transaction Fees: 80% to treasury, 20% to block producer

Wanted to put up an issue for this as it’s important for Kusama, please CRUD this issue as needed.
Detailed research here
How a transaction fee is constituted and split
There will be several types of transactions, with different fee levels. This fee differentiation is used to reflect the different costs in resources incurred by transactions, and to encourage/discourage certain types of transactions. Thus, we need to analyze the resource usage of each type of transaction, to adjust the fees (to be done).
Part of the transaction fee needs to go as a reward to the block producer for transaction inclusion, as otherwise they would have an incentive not to include transactions since smaller blocks are faster to produce, distribute and incorporate in chain. However, the block producer should not be rewarded the full amount of the fee, so they are discouraged from stuffing blocks.
How much of the tx fee goes to the block producer is an adjustable parameter via governance; we originally suggest 20%, and suggest that the other 80% go to treasury (instead of burning) to keep better control of inflation/deflation).
This percentage might depend on the transaction type, to encourage the block producer to include certain tx types without necessarily increasing the fee.
@0x7CFE @Kianenigma

spreadsheet has this as @0x7CFE . now it's @Kianenigma ? would be good to keep the issue and spreadsheet aligned with each other and reality.

My mistake. I am not directly assigned to this.

Ain this done by now? https://github.com/paritytech/substrate/pull/2912


datastructures.FileMultiDict does not act like MultiDict

Pasting my patch file with comments, should be self-explanatory:

#Werkzeug's FileMultiDict class has a bug: it doesn't act like multi-dict,
#it acts like a regular dict insttead, i.e. it only stores one value (file)
#per key.

import mimetypes
from werkzeug.datastructures import FileStorage, FileMultiDict

# New implementation of FileMultiDict.add_file():
def new_add_file(self, name, file, filename=None, content_type=None):
    if isinstance(file, FileStorage):
        value = file
    else:
        if isinstance(file, basestring):
            if filename is None:
                filename = file
            file = open(file, 'rb')
        if filename and content_type is None:
            content_type = mimetypes.guess_type(filename)[0] or \
                           'application/octet-stream'
        value = FileStorage(file, filename, name, content_type)

    # this line is critical to this patch.
    # Werkzeug used to do self[name] = value
    self.add(name, value)

# patch:
FileMultiDict.add_file = new_add_file

Fixed quite some time ago.


Merging arm-intake into dev

Getting the arm and intake subsystems into the dev branch

You need to format the code before it can be merged

Spotless has been satisfied! 🎉

i forgot about this and now its in conflict with dev bc i updated spotless independently--sorry. Mind resolving the conflict?

np, but iirc, didn't you want me to not merge this? Something about how the other feat branches are just taking from this one anyway?

Yeah I guess I'm unclear how to handle this, will think about it more.

The features from this pr have been moved to betabot branches, closing.


Add doc-comment to test README examples

Thanks for the PR, but I would personally prefer to keep it manually up-to-date and would prefer to avoid taking on a new dev-dependency.

Sure! Don't hesitate to add it if you change your mind. ;)


How can I cache the InitialData of useSWRInfinite?

As the title says, you need to cache the InitialData with useSWRInfinite.
Every time I load a page after the first page, the InitialData is lost.
What should I do?
Repro Steps / Code Example
const { data, error, setSize, size } = useSWRInfinite(
    (pageIndex, previousPageData) => {
      if (previousPageData && !previousPageData.next) return null;
      return previousPageData?.next ?? initialData.next;
    },
    fetcher,
    { initialData: [initialData] }
  );

SWR version: 0.5.6

It turns out that this just means that InitialData is not cached, but is it impossible to cache InitialData?

Please check the new cache API, you should be able to provide a prefilled cache with it: https://swr.vercel.app/docs/advanced/cache.


Unknown builtin op: torchvision::roi_align.

🐛 Describe the bug
I’am trying to use torch.jit.load to load a model but meet an error as follow.
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
~\AppData\Local\Temp\ipykernel_11836\3154094266.py in <module>
      1 # Load torchscript version of model
----> 2 model = torch.jit.load(torchscript_path)

c:\Users\SUSIE\Anaconda3\envs\osr\lib\site-packages\torch\jit\_serialization.py in load(f, map_location, _extra_files)
    160     cu = torch._C.CompilationUnit()
    161     if isinstance(f, str) or isinstance(f, pathlib.Path):
--> 162         cpp_module = torch._C.import_ir_module(cu, str(f), map_location, _extra_files)
    163     else:
    164         cpp_module = torch._C.import_ir_module_from_buffer(

RuntimeError:
Unknown builtin op: torchvision::roi_align.
Could not find any similar ops to torchvision::roi_align. This op may not exist or may not be currently supported in TorchScript.
:
  File "code/__torch__/torchvision/ops/roi_align.py", line 18
  else:
    rois = unchecked_cast(Tensor, boxes)
  _6 = ops.torchvision.roi_align(input, rois, spatial_scale, output_size[0], output_size[1], sampling_ratio, aligned)
       ~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
  return _6
'roi_align' is being compiled since it was called from '_multiscale_roi_align'
Serialized   File "code/__torch__/torchvision/ops/poolers.py", line 128
  _30 = "scales and mapper should not be None"
  _31 = __torch__.torchvision.ops.poolers._convert_to_roi_format
  _32 = __torch__.torchvision.ops.roi_align.roi_align
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
  _33 = "This Python function is annotated to be ignored and cannot be run"
  _34 = uninitialized(Tensor)
'_multiscale_roi_align' is being compiled since it was called from 'MultiScaleRoIAlign.forward'
Serialized   File "code/__torch__/torchvision/ops/poolers.py", line 19
    _0 = __torch__.torchvision.ops.poolers._filter_input
    _1 = __torch__.torchvision.ops.poolers._setup_scales
    _2 = __torch__.torchvision.ops.poolers._multiscale_roi_align
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ <--- HERE
    featmap_names = self.featmap_names
    x_filtered = _0(x, featmap_names, )

Versions
Collecting environment information...
PyTorch version: 1.12.0
Is debug build: False
CUDA used to build PyTorch: 11.3
ROCM used to build PyTorch: N/A
OS: Microsoft Windows 10 家庭中文版
GCC version: (tdm64-1) 9.2.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A
Python version: 3.7.13 (default, Oct 19 2022, 10:19:43) [MSC v.1916 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.19041-SP0
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to:
GPU models and configuration: GPU 0: NVIDIA GeForce MX150
Nvidia driver version: 516.01
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture=9
CurrentClockSpeed=1600
DeviceID=CPU0
Family=205
L2CacheSize=1024
L2CacheSpeed=
Manufacturer=GenuineIntel
MaxClockSpeed=1800
Name=Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
ProcessorType=3
Revision=
Versions of relevant libraries:
[pip3] numpy==1.21.5
[pip3] pytorch-metric-learning==1.5.1
[pip3] torch==1.12.0
[pip3] torchaudio==0.12.0
[pip3] torchvision==0.13.0
[conda] blas                      1.0                         mkl
[conda] cudatoolkit               11.3.1               h59b6b97_2
[conda] mkl                       2021.4.0           haa95532_640
[conda] mkl-service               2.4.0            py37h2bbff1b_0
[conda] mkl_fft                   1.3.1            py37h277e83a_0
[conda] mkl_random                1.2.2            py37hf11a4ad_0
[conda] numpy                     1.21.5           py37h7a0a035_3
[conda] numpy-base                1.21.5           py37hca35cd5_3
[conda] pytorch                   1.12.0          py3.7_cuda11.3_cudnn8_0    pytorch
[conda] pytorch-metric-learning   1.5.1
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torchaudio                0.12.0               py37_cu113    pytorch
[conda] torchvision               0.13.0               py37_cu113    pytorch

Sorry @SUSIEE01 it's hard to help without knowing the code you tried. The roi_align op is jit-scriptable so I assume this is a setup issue on your side. I'll close the issue, feel free to reopen if the problem persists


The information about pinning a tag no longer works

What is happening:
When a tag is pinned it creates an all resources tile on the dashboard that is NOT filtered by the tag.
What is expected:
It creates a tag tile that directs you to an all resources list filtered by tag OR an all resources tile that is filtered by the tag.

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

ID: bc003943-8bc8-10ac-e633-5640cff3c397
Version Independent ID: f8826361-f601-acf9-3e3d-c96579c02093
Content: Tag resources for logical organization - Azure Resource Manager
Content Source: articles/azure-resource-manager/resource-group-using-tags.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@nullstatement Thanks for your comment. We are actively investigating and will get back to you shortly.

@tfitzmac  As the user mentioned, seems filter on the dashboard tiles (All resources) has been removed. Can you verify and update the document accordingly?

@SwathiDhanwada-MSFT - I could remove it from the docs, but this seems much more like a bug in the portal. Do you have a way of passing this request on to the portal team?

@tfitzmac I have emailed the issue to one of the PG contacts of Azure Portal. Upon response , I will post here.

I am removing those steps for now. If this functionality is added back to the portal, I can add them back in.

The update should get published on Monday.

#please-close

@nullstatement @tfitzmac Here is the information I have received from Engineering team. As of now , there is no way to pin the list of resources with filters set. However, Engineering team has a work item planned for later this semester to provide this functionality.


Use ANSI styling in output

Feature Request
Summary
By virtue of using clap, help and usage messaging is already ANSI styled. The software's own output could be improved by using ANSI styling as well. From the Command Line Interface Guidelines:

Use color with intention. For example, you might want to highlight some text so the user notices it, or use red to indicate an error. Don’t overuse it—if everything is a different color, then the color means nothing and only makes it harder to read.

Given the rather simple nature of this software, my suggestion would be to limit the use of ANSI styling to highlighting important information (e.g. what file system entry a line is about) or dimming optional information (e.g. error tips).
Suggestion
The following snippet aims to give an idea of how ANSI styling can be used to improve the software output. This suggestion is not necessarily complete nor final.

Note: Using HTML tags to give an idea of what would be styled, not necessarily how. Using  to indicate something deserves emphasis,  to dim text.

$ rm example_file example_dir
Would remove example_file
Cannot remove example_dir: Is a directory (use '--dir' to remove)

1 would be removed (use '--force' to remove), 1 error occurred

$ rm example_file example_dir --dir
Would remove example_file
Would remove example_dir

2 would be removed (use '--force' to remove), 0 errors occurred

$ rm example_file example_dir --dir --force
Removed example_file
Removed example_dir

2 Removed, 0 errors occurred

Requirements (DRAFT)

Implementation should respect (some) NO_COLOR options, this should be verified in the no_color.rs test suite

While closed, suggestions for improvements/additions/changes to ANSI styling in regular software output are welcome. Either leave a comment here or create a new issue :slightly_smiling_face:


Alert disappears when a keyboard is presented in iOS 8 (landscape)

Hi,
I tried to add a UITextView to the custom alert, but the alert will disappear when the keyboard is presented in iOS 8, landscape mode. I fix this issue by modifying the method -keyboardWillShow:
UIInterfaceOrientation interfaceOrientation = [[UIApplication sharedApplication] statusBarOrientation];
if (UIInterfaceOrientationIsLandscape(interfaceOrientation)  && NSFoundationVersionNumber <= NSFoundationVersionNumber_iOS_7_1) {
    CGFloat tmp = keyboardSize.height;
    keyboardSize.height = keyboardSize.width;
    keyboardSize.width = tmp;
}

Since iOS 8 will return the correct frame in landscape mode, we don't need to exchange its width and height. I add one more condition NSFoundationVersionNumber <= NSFoundationVersionNumber_iOS_7_1 to resolve this issue.

awesome, thanks! do you mind adding a pull request?

I will add a pull request, thanks!

Please check the pull request: https://github.com/wimagguc/ios-custom-alertview/pull/71

thanks @oscarfung, this is merged now :)


YARN-5025. Container move (relocation) between nodes

134

 Quality gate: Failed
52 Issues

 2 Vulnerabilities
 50 Code issues

Details


ui-cleanup

Fixes some console errors and small UI inconsistencies

Codecov Report

Merging #136 (47f0077) into main (ea465c8) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 47f0077 differs from pull request most recent head b3bdd9e. Consider uploading reports for the commit b3bdd9e to get more accurate results

@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   93.23%   93.23%
=======================================
  Files         107      107
  Lines        2659     2659
=======================================
  Hits         2479     2479
  Misses        180      180

Continue to review full report at Codecov.

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


Generalize List-Id regex

Some of my lists (vim_use, vim_dev) have _ in the list name like this:
List-ID: <vim_use.googlegroups.com>
The ListMailsFilter.py regex '[a-z0-9-]+' fail to recognize the list id and don't tag it because the "_".
The List-Id header is define on rfc2919 rfc2919 and the dot-atom-text on rfc2822 rfc2822.
I think that when can include the characters define as atext (defined on rfc2822 rfc2822) and use "[a-zA-Z0-9!#$%&'*+-/=?^_{|}~]"` in the regex and we can remove the @ as @ can't be present.
Or implement the grammar that define List-Id so <vim.use.google.com> is tagged with vim.use
What you think?

Thanks for digging up the relevant information from the RFCs. Does the new regular expression match your list ids?

Yes. Thanks teythoon. Its match every list id that I had problems.

You are welcome :)


Set vtk version (solve segfault for newest versions)

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


Update app store descriptions

Describe the bug
The app store descriptions are not reflective of what the demo / app is about.
Expected behavior
The appstore description should tell a developer that they can install the Ory mobile example app to connect to a hosted instance of Kratos. It showcases how the app calls and sends commands to the Kratos API to register a user and receives back a payload from the Kratos API. The example application can be forked on GitHub and used and customized by a developer to showcase registration for their own mobile applications. It shows how easily registration is automated and software can be replicated.

Do you have a concrete suggestion for the description that I could copy&paste to the store? :)

This is the Ory example app for developers to see how easy it is to set up user registration. The app connects to a hosted instance of Ory Kratos via the API. You can use the app to register a user and create a profile. The app sends data to the Kratos API and receives back a payload which you can inspect to see how everything works, and how the profile is set up.
You can fork the code for the app on GitHub, customize it, and try it for yourself with your own mobile applications. You will see how easily registration and profile creation can be automated and software can be replicated. No more heavy lifting and instant gratification out of the box :)


unable to use testcontainers with credentials (ryuk + private registry)

Recently upgraded testcontainers from 1.4.3 to 1.8.1 and found that it is unable to pull images from our private registry at docker hub. The daemon is configured with an auth token created by docker login and persisted in ~/.docker/config.json. Testcontainers/dockerjava appears to ignore the auth tokens persisted there?
To unblock our Jenkins plugins I've added a ~/.docker-java.properties with the registry & credentials for our private docker hub regristry as per https://github.com/docker-java/docker-java. This allowed images to be pulled down again.
However, when running the first time, testcontainers pulls down ryuk which fails as follows:
2018-08-01 14:45:03,581 [test] INFO  o.t.DockerClientFactory - Docker host IP address is localhost
2018-08-01 14:45:03,836 [test] INFO  o.t.DockerClientFactory - Connected to docker:
  Server Version: 1.10.3
  API Version: 1.22
  Operating System: Ubuntu 14.04.4 LTS
  Total Memory: 16047 MB
2018-08-01 14:45:04,656 [test] ERROR c.g.d.c.a.ResultCallbackTemplate - Error during callback
com.github.dockerjava.api.exception.InternalServerErrorException: Get https://quay.io/v2/testcontainers/ryuk/manifests/0.2.2: unauthorized: Invalid Username or Password

	at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:109)
	at com.github.dockerjava.netty.handler.HttpResponseHandler.channelRead0(HttpResponseHandler.java:33)
	at org.testcontainers.shaded.io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:105)
	at org.testcontainers.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)
	at org.testcontainers.shaded.io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:348)

It looks like it's trying to use the configured credentials to access the public repo at quay.io and of course fails.  Chicken and egg situation?

related: https://github.com/testcontainers/testcontainers-java/issues/790

fixed by virtue of fixing #820