test: Changes to add KPIs to e2e action

Fixes #N/A
Description
Changes the e2e tests to allow for using a python script to extract KPIs from prometheus during the e2e testing.
How was this change tested?
Work in progress. Testing via actions and testing in experimental EKS clusters with Nick Tran.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.09%) to 81.355%

Totals

Change from base Build<PHONE_NUMBER>:
0.09%

Covered Lines:
8308

Relevant Lines:
10212

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.07%) to 81.336%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
8306

Relevant Lines:
10212

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.8%) to 80.464%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8320

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.7%) to 80.532%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/scheduling/requirements.go
2
98.01%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
8327

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.8%) to 80.484%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/node/termination/terminator/eviction.go
2
89.09%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8322

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.8%) to 80.513%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8325

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.8%) to 80.464%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8320

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.7%) to 80.532%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
8327

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.8%) to 80.513%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/expiration.go
2
89.66%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.8%

Covered Lines:
8325

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.7%) to 80.532%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

pkg/apis/v1beta1/nodepool.go
3
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
8327

Relevant Lines:
10340

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
19 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.7%) to 80.528%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/expiration.go
2
89.66%

pkg/apis/v1beta1/nodepool.go
3
95.24%

pkg/controllers/provisioning/controller.go
14
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
8325

Relevant Lines:
10338

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

103 of 211 (48.82%)  changed or added relevant lines in 13 files are covered.
21 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.7%) to 80.528%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/apis/v1beta1/nodepool.go
14
15
93.33%

pkg/controllers/disruption/multinodeconsolidation.go
5
6
83.33%

pkg/controllers/disruption/singlenodeconsolidation.go
4
5
80.0%

pkg/controllers/disruption/helpers.go
48
50
96.0%

pkg/apis/v1beta1/zz_generated.deepcopy.go
1
5
20.0%

pkg/test/pods.go
0
99
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/test/expectations/expectations.go
2
93.69%

pkg/controllers/node/termination/terminator/eviction.go
2
89.09%

pkg/apis/v1beta1/nodepool.go
3
95.24%

pkg/controllers/provisioning/controller.go
14
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
8325

Relevant Lines:
10338

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.08%) to 78.386%

Totals

Change from base Build<PHONE_NUMBER>:
0.08%

Covered Lines:
8722

Relevant Lines:
11127

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.06%) to 78.368%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/disruption/drift.go
2
89.09%

Totals

Change from base Build<PHONE_NUMBER>:
0.06%

Covered Lines:
8720

Relevant Lines:
11127

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 78.404%

Files with Coverage Reduction
New Missed Lines
%

pkg/apis/v1/nodepool.go
2
75.95%

pkg/apis/v1beta1/nodepool.go
2
95.24%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
8724

Relevant Lines:
11127

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
66 unchanged lines in 8 files lost coverage.
Overall coverage increased (+0.03%) to 78.33%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/controllers.go
1
0.0%

pkg/controllers/nodeclaim/disruption/expiration.go
2
92.31%

pkg/apis/v1/nodepool.go
2
75.95%

pkg/apis/v1/labels.go
2
92.59%

pkg/apis/v1/taints.go
3
0.0%

pkg/operator/operator.go
11
2.99%

pkg/utils/nodeclaim/nodeclaim.go
12
40.52%

pkg/controllers/disruption/controller.go
33
76.09%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
8668

Relevant Lines:
11066

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
68 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.007%) to 78.312%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/controllers.go
1
0.0%

pkg/controllers/nodeclaim/disruption/expiration.go
2
92.31%

pkg/apis/v1/nodepool.go
2
75.95%

pkg/apis/v1/labels.go
2
92.59%

pkg/controllers/node/termination/terminator/eviction.go
2
89.09%

pkg/apis/v1/taints.go
3
0.0%

pkg/operator/operator.go
11
2.99%

pkg/utils/nodeclaim/nodeclaim.go
12
40.52%

pkg/controllers/disruption/controller.go
33
76.09%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
8666

Relevant Lines:
11066

💛  - Coveralls


New feature suggestion or collaboration

can be discussed here

Hello, I would like to contribute on this project. Can you suggest where should I start from?

First use this app, https://play.google.com/store/apps/details?id=com.rahuls.sharednotes
then review the app and open up issues and feature suggestion here


Typo: Create a new project > Create a new visual > 4. says to replace project.json instead of package.json

Create a new project
Create a new visual

The package.json file containst a list of project dependencies. Replace your project.json file with this one.

Should be:

The package.json file containst a list of project dependencies. Replace your package.json file with this one.

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

ID: 95b6da01-c39e-67af-541e-6c9ee48c1d26
Version Independent ID: bc9e9e91-8151-e02f-ee88-e12929dff9ba
Content: Build a bar chart visual in Power BI - Power BI
Content Source: powerbi-docs/developer/visuals/create-bar-chart.md
Service: powerbi
Sub-service: powerbi-custom-visuals
GitHub Login: @mberdugo
Microsoft Alias: monaberdugo

Thanks for your comment, @JimAtPCG. This issue has been assigned to the doc author for review.

Thanks for pointing this out, @JimAtPCG
I'll fix it right away.


Placeholder illegal nesting not generating error

Hey, was writing some scss and upon saving there was no reaction from the compiler, also no error was displayed (running on --silent).
Tested the code at sassmeister and turned out i had an illegal nesting error that wasn't being displayed.
%block-wysiwyg {
    ol, ul { padding-left: 17px
        li { font-size: 1.6em; list-style-type: none; position: relative;
            &:before { content: " "; width: 7px; height: 7px; border-radius: 100%; }
        }
    }
}

Apparently Illegal nesting: Only properties may be nested beneath properties. How come this isnt being displayed as an error?

I think you're having an issue with some other wrapper (Gulp/Grunt?) since silent isn't an option in this library and running node-sass from the commanline also produces the following error
{
  "formatted": "Error: Illegal nesting: Only properties may be nested beneath properties.\n        on line 3 of test.scss\n>>         li { font-size: 1.6em; list-style-type: none; position: relative;\n   ----------^\n",
  "message": "Illegal nesting: Only properties may be nested beneath properties.",
  "column": 11,
  "line": 3,
  "file": "/Users/nschonni/Documents/github/test/test.scss",
  "status": 1
}


Add node_count to stale node json output.

To help make decisions when processing stale nodes having the total number of nodes available
is very helpful.

Thank you.


Add cut "shotgun_doublebarrel" model from TFO

Video ingame:
https://cdn.discordapp.com/attachments/1121520467791056997/1124063836702523422/yeet.mp4
all stats have been brought over from TFO aswell.
should make people more happy when playing neinguars gungame as it features said weapon but used the weapons placeholder model (a mastiff).

noticed an error, will reopen once fixed


Fix bugs in safe restricted-python evaluation

Use safe getattr method to restrict access to _-prefixed attributes
Add guards for iterators to make lists and loops work
https://github.com/amyxzhang/policykit/pull/533/commits/8516a3def1f94de7f4455347ccce2aa7edd7e097 Fix bug where strftime was raising an exception https://github.com/amyxzhang/policykit/issues/534
https://github.com/amyxzhang/policykit/pull/533/commits/8516a3def1f94de7f4455347ccce2aa7edd7e097 Include line numbers for syntax errors in web log viewer:

Looks great! Feel free to merge!


Adding carousel navigation buttons and removing certificate button on education card as discussed in #302 and  #326

Feature request proposal-

Adding carousel navigation buttons for the education page as discussed in #326
Removing certificate button on education card as discussed in #302

Will start working on this!


xml:ids SHOULD be latin characters

In the current test file there are already attributes @xml:ids for characters <person> in the <particDesc>. They are in Georgina script, which seems not be be a problem for the wellformedness of the XML though.
I validated the file with our new upcoming schema that includes some schematron checks and they report issues with the connection of character labels in <speaker>/ @who attributes and the (not) corresponding in the elements in the  <particDesc>.
For example, there is a speech:
<sp who="#ანდუყაფარ">
            <speaker>ანდუყაფარ</speaker>

რა ვქნა, ძმაო, არა შვრება. რა გაეწყობა, ვერა მომიხერხებია რა, რუსული კარგად იცის,
              რუსის დიდკაცებთან დადის, მერე ჩემი რძალიც იმისკენ არის.

          </sp>

The schema check reports:

Beschreibung: A speech act SHOULD link to a 'person' or 'personGrp' element in 'particDesc'. Use a valid character ID and provide it as a pointer by prepending it with a hash '#'."

If I STRG+F for ანდუყაფარ I can not find the exact string in the ids in the particDesc. There is a somewhat close match:
<person xml:id="ანდუყაფარი" sex="MALE">
            <persName>ანდუყაფარი</persName>
          </person>

Still, not being able the read the text AND the IDs it is hard for me to tell if that' simply a spelling error in the ID.
It would be easier to check if the values of the @xml:ids where latin transliterations of the Georgian ones.
In other corpora that use non-latin scripts, e.g. the Russian and the Ukrainian Drama Corpus we have transliterated IDs, e.g.
<person xml:id="hlestakov" sex="MALE">
            <persName>Хлестаков</persName>
            <persName xml:lang="ger">Chlestakow</persName>
          </person>

<personGrp sex="UNKNOWN" xml:id="khor_ditej">
            <name>Хор дітей</name>
          </personGrp>

It is also the case for the Hebrew Drama Corpus:
<person xml:id="mkhls ildim">
      <persName>
       מקהלת ילדים
      </persName>

Just to prevent misunderstandings: the Hebrew example actually has an invalid ID. XML IDs cannot contain space characters among others (see full spec at https://www.w3.org/TR/REC-xml/#NT-Name). Technically they can consist of characters from various scripts, but for DraCor we follow the convention to use only ASCII characters. The reason being that IDs may be used to construct URLs and anything beyond the ASCII range would have to be URI encoded which would make the URLs less readable.


Add a mode where soynode will load precompiled templates from disk. This will make i18n load much faster.

Hello @kylehg, @archfear,
Please review the following commits I made in branch 'nicks/precompile'.
dbce15c103f9181424184f7d0276637eda1394bf (2016-12-02 15:09:02 -0500)
Add a mode where soynode will load precompiled templates from disk. This will make i18n load much faster.
R=@kylehg
R=@archfear

LGTM


chore(main): release 1.12.6

:robot: I have created a release beep boop
1.12.6 (2023-04-08)
Miscellaneous Chores

deps: bump pestphp to ^2.0 (a06dc58)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rotex1800/registration/releases/tag/v1.12.6 :sunflower:


Is there any reference to the definition of baseline creatinine?

Hi, I have recently read the definition of baseline creatinine , which is expressed as follows:
-- This query extracts the serum creatinine baselines of adult patients on each hospital admission.
-- The baseline is determined by the following rules:
--     i. if the lowest creatinine value during this admission is normal (<1.1), then use the value
--     ii. if the patient is diagnosed with chronic kidney disease (CKD), then use the lowest creatinine value during the admission, although it may be rather large.
--     iii. Otherwise, we estimate the baseline using the Simplified MDRD Formula:
--          eGFR = 186 × Scr^(-1.154) × Age^(-0.203) × 0.742Female
--     Let eGFR = 75. Scr = [ 75 / 186 / Age^(-0.203) / (0.742Female) ] ^ (1/-1.154)
I wonder that is there any reference to this definition of baseline creatinine?
Thank you!

Hi,
I wrote the original version of scripts about AKI and baseline Scr, and Alistair improved it a lot.
There are various ways to estimate baseline SCr, and it's found that these methods caused a variation in AKI incidence up to 15% [1]. This definition was summarised by myself. I don't know whether there is any reference that adopted exactly the same definition.
Notably, AKI was annotated based on the lowest creatinine in the past 7 days as the baseline Scr, consistent with that in MIMIC-III. I didn't use my definition because I'm afraid that this definition is not accepted.
https://github.com/MIT-LCP/mimic-iv/blob/da0339348c283835dd01788f6c17d1fceb99c88e/concepts/organfailure/kdigo_stages.sql#L3
Maybe I can help to provide more methods to estimate the missing baseline.
[1] Wiersema R, Jukarainen S, Eck RJ, Kaufmann T, Koeze J, Keus F, Pettilä V, van der Horst ICC, Vaara ST. Different applications of the KDIGO criteria for AKI lead to different incidences in critically ill patients: a post hoc analysis from the prospective observational SICS-II study. Crit Care. 2020 Apr 21;24(1):164. doi: 10.1186/s13054-020-02886-7.

Thanks a lot for your valuable information.
Previous various definitions of the baseline Scr usually did not distinguish the patients with or without CKD, which would misclassify the patient with AKI or CKD. Your definition is a very good idea that needs further verification.


Swift Example for Stripe

Are their any good examples of the Stripe example written in Swift?

There are no samples in Swift.  JavaScript on node.js is currently the only language and environment supported for Cloud Functions.


Input Number has problems with decimals since 6.2.6/6.2.7

Describe the bug
Input of numbers with decimal places is broken since 6.2.6/6.2.7
How to reproduce
Steps to reproduce the behavior:

Goto https://sveltestrap.js.org/?path=/docs/form-input--docs#numbers
Enter decimal numbers like "1,22".

Expected behavior
The value should stay "1,22"
Screenshots
https://github.com/sveltestrap/sveltestrap/assets/8957069/0274e922-722e-4415-a625-92e5eb8417d6
Desktop (please complete the following information):
Current Chrome on Mac OS
Additional context
I'm pretty sure it's related to https://github.com/sveltestrap/sveltestrap/pull/61

I just ran into this. Is there any known workaround for now?

Downgrade to 6.2.5 worked for me

Apologies for the delayed response. I've reviewed your issue and I'm hesitant to change this logic since it aligns with the native number input type behavior. If you want to use decimals or commas, it seems like using a text input field with validation would make sense.

Uhh, this is a breaking change. And I'm pretty sure Kommas in Numbers are absolute fine when your Locale tells the browser to use these.

I reread your issue and realized your example contains commas not decimals. There is an issue with decimals, but not with supporting commas. I plan to PR a fix for the decimals soon.


Hovertemplate breaks

Update hovertemplate to  read better: numbers on left, more or less aligned in a column.
It's not perfect because the font being used doesn't have consistent width for digits comma and space.
Small error in a commit, doesn't matter in the end:
File was unsaved in VS code, so the commit at 666b7d9 wasn't quite the latest version.
So the commit message is "future", prophesying the name change in the next commit 937f9c0.
By the way:
The reason I changed the name was to avoid getting too concrete.
The name weeklyTotalExtra expresses the contents too much. If it was total, weekly, extra, then I would not want to change the name. So "hovertemplateBody" says that this is used in the hovertemplate:, but not exactly what is in it and what order.

Fixing the spacing issue could probably be done by <span>ing the case numbers and giving them the same width in CSS. Other than this, seems fine.


Latest vim9script deprecated usage of # in function name

I suggest replace such functions with capital first letter and prepend export.
I'm not sure if vim8 vimrc will need to call import to call lsp#setOptions.
It might be a good idea to migrate to global variable based config like the old times, as it is bit awkward to call import during configuration.

A such commit would look like this, though probably it'll need a lot of patching to make it up to the standard of this project.
https://github.com/kohnish/lsp/commit/74f8d32192189ec292b5a37fc6ef2adcf7e28a33

Thanks for the patch. I have committed aeede042a93441f038f6b36448aaf383969bc86b to support the LSP plugin with both the latest Vim and an older version. Some of the changes are similar to what you have done in your branch. Can you try the updated plugin and let me know if you see any issues? Thanks

Thanks for such a fast patch.
This seems to work with the latest master.  (From vim9script vimrc)
source $HOME/.vim/pack/plugins/opt/lsp/plugin/lsp.vim
g:LspAddServer(lsp_servers)

Instead of sourcing the plugin/lsp.vim file, why can't you use "packadd lsp"?

Hey, thanks for the tip. I already do it but didn't work out (function not found) I'll try it later with up-to-date vim.


It doesn't show any other gun skins accept standard vandal ;(

you have to own skins

you have to own skins

In the video, the YouTuber is saying that we can get skins by owning them and here u r telling that we need to have the skins?


SQLite support?

Hey there. Would be nice to have SQlite support, ideal for small forums, easy to maintain and low on resources.
Thanks!

Any news on this?


Please clarify if there is any hard limitation in using BTP's "Default Identity Provider" for Cloud ALM (SAP ID / UID)

Issue description

To avoid double maintenance of user accounts in IAS and ALM, I am considering not using IAS and instead SAP UID based login.
Feedback Type (Optional)
clarity
Page Title on SAP Help Portal (prefilled)
Troubleshooting and FAQ
Page URL on SAP Help Portal (prefilled)
https://help.sap.com/docs/cloud-alm/setup-administration/troubleshooting-faq

Hi @piejanssens,
Thanks a lot for your feedback.
There is currently no hard limitation.
However, you should be aware that you will be responsible yourself for the compliance to security policies and that custom policies are not supported in the SAP ID service.
Moreover, many applications on SAP BTP already require the SAP Cloud Identity Services as their identity and access management solution. It is likely that the number of these applications will grow, which will cause a considerable amount of migration efforts on your side.
Therefore, we strongly recommend using an Identity Authentication tenant for SAP Cloud ALM from the start.
For more information on SAP Cloud Identity Services on SAP BTP, refer to the Best Practices for SAP BTP.

Thanks. I will use IAS with a proxy to the IdP to avoid maintenance of user identities in IAS' user store.

https://people.sap.com/piejanssens


Can't build on my system

Gcc throws an error that basically says it can't find std::strings in include/exception.hpp. Simply adding #include <string> fixed the problem.

Hi again! 😊
As you mentioned, the <string> include is missing. On recent versions of MSVC and GCC I suspect that std::string leaks from <string_view>. What version of GCC are you using? If possible, try using GCC 9.3.0 or later.
Many thanks for letting me know and making Centurion a little bit better! The library will go headet-only in version 5.1.0, so you wont have to build it yourself.

Hi again! 😊
As you mentioned, the <string> include is missing. On recent versions of MSVC and GCC I suspect that std::string leaks from <string_view>. What version of GCC are you using? If possible, try using GCC 9.3.0 or later.
Many thanks for letting me know and making Centurion a little bit better! The library will go headet-only in version 5.1.0, so you wont have to build it yourself.

I'm using GCC 10.2.0. I can confirm that in MSVC the string header leaks from string_view, but GCC 10.2 doesn't include it in the string_view header, i don't know if 9.3 does.
Anyway the library looks really high quality and well documented too!

I'm using GCC 10.2.0. I can confirm that in MSVC the string header leaks from string_view, but GCC 10.2 doesn't include it in the string_view header, i don't know if 9.3 does.
Anyway the library looks really high quality and well documented too!

That's good to know! This has now been fixed on the WIP 5.1.0 branch.
Thank you for your kind words, the library will be of even higher quality with a new mocked test suite in 5.1.0.

That's good to know! This has now been fixed on the WIP 5.1.0 branch.
Thank you for your kind words, the library will be of even higher quality with a new mocked test suite in 5.1.0.


Allow for limiting resolve_sequence_association to procedures that are inlined in loki-transform convert

This PR makes the resolve_sequence_association option of loki-transform.py convert accept one of three options (instead of on/off before):

'off': sequence association is turned off (default)
'all': all calls found are checked and resolved for sequence association
'inlined-only': sequence association is checked and resolved only for procedures that get inlined (member procedures or inline pragma-marked procedures only)

The main changes here are:

changing the argument resolve_sequence_association to be a click.Choice among the three above values. I also did my best to make changes to the respective cmake files. I am not an expert with cmake, but I hope the tests will catch any errors I might have made. Basically I moved resolve_sequence_association from an "option" to a "oneValueArgument" in one of the cmake files.

adding logic to the convert function to pass the correct resolve_sequence_association choice to SanitiseTransformation and InlineTransformation.

I reintroduced resolve_sequence_association as a constructor argument for InlineTransformation.

In transform_inline.py, I added a new function resolve_sequence_association_for_inlined_calls (we can discuss if it should actually be in transform_sanitise.py). This function implements the functionality of the "inlined-only" option, making changes in transform_subroutine of InlineTransformation, only if all of the following are true:

user requests resolve_sequence_association (for InlineTransformation)
either of inline_internals or inline_marked is set to True (for InlineTransformation)
the procedure to be processed contains calls that will be inlined

slight refactoring of transform_sequence_association in transform_sanitise.py. This function processes all calls of a procedure simultaneously. I rewrote this in terms of a new function transform_sequence_association_append_map(call_map, call) that builds up the transformation map for resolving sequence assiociation one call at a time. This allows for resolving sequence association on a "call by call" basis elsewhere, as opposed to every call in a procedure. I use this in the implementation of resolve_sequence_association_for_inlined_calls above.

I modified the help of loki-transform.py convert accordingly and added new tests for InlineTransformation that end up calling resolve_sequence_association_for_inlined_calls.

Many thanks @reuterbal for the review. I have made the changes you requested. It appears that some of the regression tests failed, but it seems like they fail due to some FIELD API related issue.

Thanks, @mlange05. I agree with what you said about configuration files.


rpcerror(engine): Support server-side stack trace.

What problem does this PR solve?
Issue Number: close #6756
What is changed and how it works?

Added server-side stack trace support.

Check List
Tests

Unit test

Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
None.

/merge

/merge

/run-verify

/run-verify
/run-leak-test

/run-verify
/run-leak-test


chore(main): release 0.2.0

:robot: I have created a release beep boop
0.2.0 (2024-11-21)
Features

Add --dry-run (5e06433)

Bug Fixes

deps: update rust crate clap to v4.5.20 (#8) (e9dee0f)
deps: update rust crate clap to v4.5.21 (#18) (c7601d2)
deps: update rust crate reqwest to 0.12 (#14) (6de18c0)
deps: update rust crate serde to v1.0.214 (#9) (2cd16d1)
deps: update rust crate serde to v1.0.215 (#17) (0d9ef1d)
deps: update rust crate serde_json to v1.0.132 (#11) (30d4c8f)
deps: update rust crate serde_json to v1.0.133 (#19) (5a7ab72)
deps: update rust crate service_conventions to 0.0.23 (#12) (d82e237)
deps: update rust crate tokio to v1.41.1 (#15) (c6c4e36)
Don't delete unlabeled images (4461f61)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philipcristiano/docker-registry-cleaner/releases/tag/v0.2.0 :sunflower:


Training with custum data and convert to Pascal VOC11

Hello,
Please, I am preparing my own database to do the training I am using CVAT.org,
When I download the converted data to Pascal VOC11, I noticed that the annotation files were missing information and mentioned unknow as shown in the following figure

any suggestions please
thank you

Did you export from CVAT in pascal VOC format or did you use some other tool to convert it?
Are there any annotations in any of the xml files?  Did you create bounding boxes in CVAT?

From: syliabe @.>
Sent: Wednesday, June 30, 2021 5:56:24 AM
To: dusty-nv/jetson-inference @.>
Cc: Subscribed @.***>
Subject: [dusty-nv/jetson-inference] Training with custum data and convert to Pascal VOC11 (#1135)
Hello,
Please, I am preparing my own database to do the training I am using CVAT.org,
When I download the converted data to Pascal VOC11, I noticed that the annotation files were missing information and mentioned unknow as shown in the following figure
[Screenshot from 2021-06-30 11-52-32]https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fuser-images.githubusercontent.com%2F86236508%2F123941006-09f25700-d99a-11eb-8d6e-1b264d62a25e.png&data=04|01|dustinf%40nvidia.com|efb58caaaeed4a1643f208d93bad52c8|43083d15727340c1b7db39efd9ccc17a|0|0|637606437866233944|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=pNTGT4pLPMSr03NqdiQ45n2bJyOCh37lz5NgRE%2BaSAw%3D&reserved=0
any suggestions please
thank you
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-inference/issues/1135, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADVEGK7IXGZ3IOHVQETVNZTTVLS4RANCNFSM47R7IZWQ.

Yes I exported from CVAT to Pascal VOC format, what I did is that I took a set of data I put it on CVAT.org then export in Pascal VOC11, suddenly I had Annotation, ImageSets and JPEGImages files
in Annotations we find

As @dusty-nv have said you didn't draw the Bounding box or some other shape for annotation basically you have not annotated the picture.
Kindly do that and paste the result picture.
Thank you!


[BUG] What is Channel unknown

I am using fvm to manage flutter sdk , I installed sdk 2.0.6 by fvm.
And I when I run fvm releases, It's result is:
Mar 19 21  │ 2.0.3
Apr 2 21   │ 2.0.4
Apr 15 21  │ 2.2.0-10.1.pre
Apr 15 21  │ 2.2.0-10.1.pre
Apr 16 21  │ 2.0.5
Apr 27 21  │ 2.3.0-0.1.pre
Apr 29 21  │ 2.2.0-10.2.pre
Apr 30 21  │ 2.0.6
May 10 21  │ 2.2.0-10.3.pre
May 10 21  │ 2.3.0-1.0.pre
May 18 21  │ 2.2.0
May 18 21  │ 2.3.0-12.1.pre
--------------------------------------
May 19 21  │ 2.2.0             beta
--------------------------------------
--------------------------------------
May 27 21  │ 2.2.1             stable
--------------------------------------
--------------------------------------
May 28 21  │ 2.3.0-16.0.pre    dev
--------------------------------------

Which type of version is stable?  for example 2.0.6
Now when I run fvm flutter doctor I got this:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 2.0.6, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[✓] Chrome - develop for the web
[!] Android Studio (not installed)
[✓] VS Code (version 1.56.2)
[✓] Connected device (2 available)

! Doctor found issues in 1 category.
What is Channel unknown,?
I want just install stable version.

@tazik561 duplicate of this https://github.com/leoafarias/fvm/issues/291, to summarize there is a difference between a release channel and a release. A release can be part of multiple channels. This is correct behavior, and part of an ongoing discussion within the Flutter repo. https://github.com/flutter/flutter/issues/40950

@tazik561 duplicate of this #291, to summarize there is a difference between a release channel and a release. A release can be part of multiple channels. This is correct behavior, and part of an ongoing discussion within the Flutter repo. flutter/flutter#40950

Now , 2.0.6 is stable? and can I change channel unknown?

The only way the channel is known is if you install a release channel. Then flutter tooling will know that the tag is part of a release channel. That means you would have to do fvm use stable, and stay in that channel with its upgrades.

@tazik561 are you having a particular issue with the fact that it displays unknown?

The only way the channel is known is if you install a release channel. Then flutter tooling will know that the tag is part of a release channel. That means you would have to do fvm use stable, and stay in that channel with its upgrades.

Not possible because stable channel is  2.2.1 and my project is not support this version yet.

The only way the channel is known is if you install a release channel. Then flutter tooling will know that the tag is part of a release channel. That means you would have to do fvm use stable, and stay in that channel with its upgrades.

Not possible because stable channel is 2.2.1 and my project is not support this version yet.

Yes, I lost hot reload in this version and when I doing hot reload my application is terminated.

@tazik561 In that case you need to pin the version directly. There doesn't seem to be any "issues" caused by having the channel unknown unless you try to do the upgrade workflow.

Not possible because stable channel is 2.2.1 and my project is not support this version yet. Thanks

I understand. You can continue to pin the version directly fvm use 2.0.6 that should work just fine. That is why I asked above, are you having issues because of the channel "unknown"?

Ok I will go ahead and close this.

See https://github.com/flutter/flutter/issues/84347#issuecomment-862743141
TL;DR:
Flutter uses the current channel to figure out what features to enable
See https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/features.dart#L367
When you use fvm, the channel is unknown, so the experimental features of master are enabled.
There was a bug that then caused hot reload to stop working.
So actually, the fact that the channel is unknown can cause issues.

@knaeckeKami thanks will check it out to see if there is a proper workaround.

@knaeckeKami and @kuhnroyal  if you guys can help test to make sure you are getting the correct behavior pub global activate fvm 2.1.2-dev.0,
the only downside is that the upgrade message shows up for the version and might cause users to upgrade.. I wonder if I should put a guard if version is not a channel.

The version default to stable now which helps with my current problem.
But I don't think this is enough. It needs to support version X on channel Y format somehow which means it needs to support 2 CLI arguments and have the optional channel in the JSON config.
If there is no channel defined it needs to default to stable.
version and channel

install specific version from channel

channel only

install latest version from channel

version only

try to find most mature channel with the version and install - stable > beta > dev
warn users if the cannel is not stable

A good starting point for this logic is https://github.com/subosito/flutter-action
This probably is a breaking change.

For example version 2.0.0 is available on stable and beta.
I don't have a way to install it form the beta channel atm.

Yes I wanted to avoid that but makes sense. I can pass a flag —channel if using with a version and prioritize that one.
Not sure if I should warn the users as I don’t think is common for people to install a stable version from beta. But we should allow the override.

Not sure if I should warn the users as I don’t think is common for people to install a stable version from beta. But we should allow the override.

I would add a warning when there is only a version configured and this version is not on stable, basically telling the user which channel was detected and that they should add the --channel flag to hide this warning and make it explicit.

Yeah, with 2.1.2-dev.0 the channel is detected correctly and this fixes the issue with the experimental features to be enabled on a supposedly "stable" version.
I agree that there should probably be a way to pick the channel for a given version if it was released on multiple versions.

Any suggestions how to handle the upgrade? The users now will be presented with the message to upgrade.
once they do fvm will lose track of the version and it won’t match, I can’t do much since this can happen from outside of fvm.
should we just have a notice and maybe flag if you run “fvm flutter upgrade” on a non channel version?

should we just have a notice and maybe flag if you run “fvm flutter upgrade” on a non release channel?

Yea I would intercept this case and make it an interactive question y/n and tell them the consequences.
And maybe proxy all other commands with --no-version-check.

I will have to store that version also, in the config... seems like there is a lot of complexity for something that I am not sure is done on purpose. Having a stable version on a release, especially since they make it to beta after stable most of the time.

I didn't really look into the architecture of fvm so I don't know what is easy to implement, but maybe you could also filter to "upgrade" message from being printed?
Also fvm could have a check if the current flutter version matches the expected version.
And yeah fvm flutter upgrade should be flagged.
Honestly, maybe we should open an issue on flutter.

Linking this for reference https://github.com/flutter/flutter/issues/59533

Also I opened #84781, which would at least cause more awareness of that behaviour

Hey guys I think I found an elegant solution for the channel version problem. Right now the behavior will be.

beta => Latest version on beta
2.2.2 => Finds channel on priority (stable, beta, dev)
beta-2.2.2 => Gets 2.2.2 from beta channel
'commit_hash` => Gets commit from master channel

This channel_name+version keeps all the rest of the config and tooling working how is expected. Here are the behavior below.

This would be fine for me, I would personally go with beta/2.2.2 as some versions already contains dashes.

@kuhnroyal wants to avoid headaches with / and the file system since this is the directory that will look for the cache version, including any custom versions. Now for example you can have any flutter fork inside any named directory and just call it.

What about 2.2.2@beta - I think this is even better

pub global activate fvm 2.1.2-dev.1 has the --no-version-check and also the new convention 2.2.2@beta

2.2.0 release closing this

Getting this on fvm flutter pub run:
Could not find an option named "no-version-check".

Need to figure out which commands support this. Probably only plain flutter commands an not those that proxy themselves to dart/pub.

Hmmm…  I am adding the “—no-version-check” and seems it would also run on pub…  maybe I need to change to add to the first index of args instead of in the end .
I am not in front of the computer. But if you want to dia quick fix, it is on flutter_command.dart and I can merge

Went ahead and removed it for now until I have a chance to write testes around this


Reduce object-bits for test to avoid OOM

Kani often runs out of memory on tests/expected/function-contract/history/stub.rs when running the regressions. In particular, quadruple_harness consumes over 9 GB of memory. This PR reduces the object bits for this test to 8 to avoid OOM issues. This brings down memory usage to ~125 MB.
Before:
$ /usr/bin/time -v kani -Zfunction-contracts stub.rs --harness quadruple_harness
        Maximum resident set size (kbytes): 9136036

After:
$ /usr/bin/time -v kani -Zfunction-contracts stub.rs --harness quadruple_harness --enable-unstable --cbmc-args --object-bits 8
...
        Maximum resident set size (kbytes): 125172

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 and MIT licenses.

I wonder if we should tweak with the current default

I tried tweaking the test, but eventually gave up. For example, switching from 32-bit integers to 16 or 8-bits does not decrease the memory usage much.
I'm open to suggestions.


Grafana dashboard

Do you perhaps have a Grafana dash json to import?

postfix_grafana.json.txt
This is the json template of our dashboard. It is based on our federated setup recordingrules. Therefore, I am not sure if this helps.

postfix_grafana.json.txt
This is the json template of our dashboard. It is based on our federated setup recordingrules. Therefore, I am not sure if this helps.

@BartVerc could you also share the recording rules you use with this dashboard?
Thanks!

anyone else started working on this? i started rolling my own before realizing this existed. i wonder how hard it would be to convert @BartVerc's dashboard into something that works without resampling rules...

I made a dashboard based on @BartVerc's work and published it on grafana.com:
https://grafana.com/dashboards/10013
It seems to work okay, although I have no data for the lmtp daemon. I also wonder how useful the TLS Cipher section really is: the cardinality of that one is kind of huge and it doesn't say anything really useful. What would be nice is the ratio of protocol use (none, TLS 1.0, 1.1, 1.2, etc) but I couldn't figure out a formula for that. I tried this:
(sum(rate(postfix_smtpd_tls_connections_total{instance=~"$instance"}[5m])) by (instance)) / (sum(rate(postfix_smtpd_connects_total{instance=~"$instance"}[5m])) by (instance))

But that gave the wrong numbers (e.g. something larger than 1) for some series. I nevertheless included something that might be useful.
Is this sufficient to close this ticket? Maybe a PR to add it to the readme?

@anarcat nice work!
The metric postfix_lmtp_messages_processed_total used in the "Message processing rate" graph shows indeed no data. The recording rule expression we use is this: avg(rate(postfix_lmtp_delivery_delay_seconds_count{job="postfix_exporter"}[15m])) by (instance).
About the TLS cipher, we use this recording rule (which I combined from multiple federated setups) :
avg_over_time( sum by(cipher, protocol, trust) (rate(postfix_smtpd_tls_connections_total{job="postfix_exporter"}[5m]))[1d])
Same for smtp. This never gives us numbers larger than 1.

i see. it seems like i don't have any postfix_lmtp_delivery_delay_seconds_count metrics either - presumably we don't have any LTMP transport setup anywhere. it's probably still worth fixing that expression in our dashboard, so I'll do so next.
this rule fails to "compile" here:
avg_over_time( sum by(cipher, protocol, trust) (rate(postfix_smtpd_tls_connections_total{job="postfix_exporter"}[5m]))[1d])

... at least in a Prometheus query, which fails with:

Error executing query: parse error at char 120: range specification must be preceded by a metric selector, but follows a *promql.AggregateExpr instead

This works, but gives much lower results than I was hoping for...
 avg( sum by(cipher, protocol, trust) (rate(postfix_smtpd_tls_connections_total{job="postfix"}[5m])))

btw, I have published the dashboards not only on grafana.com but also this git repo now:
https://gitlab.com/anarcat/grafana-dashboards
i hope that's useful...

Dash looks great. Thank you soo much

thanks! should we link it from the README?


Shadowing of functions or modules

During correcting the red black tree due to new features, I encountered types for List.append where shadowed. The simplified version of this problem with my short investigation:
import open Base/Assert
import List

let x = [1,2,3]
let y = [4,5,6]

let z = List.append x y

{#
# Error is only if this file exist in the lib folder.
# Outside of lib folder it doesn't produce error.
# For error occurrence all of imports are needed.
# More testing needed for determining whether
# it's much larger problem with modules and installed libraries.
#}

This problem requires somewhat unusual conditions to reproduce: this file has to be evaluated as a non-library program (for example by passing it as an argument to dbl) while being placed in the library directory. This is because the current implementation of imports assumes that the hierarchy for the standard library and the program are separate. This is clearly not going to be too much of a problem in practice, so I'm not too pressed about fixing it in DBL, though we could make the future Fram compiler more robust once it's time to implement file support there. Since you marked this as wontfix already, I'll just close the issue for now.


Gallery view is single column

I created a new page with a gallery view, similar to the index page. On this new page, the rendered page lists the sub pages in a single column.
Expected: gallery view is shown in two columns, as it is in Notion.
web page:
https://www.filmphoto.io/cameras

Notion page:
https://jaypozo.notion.site/Cameras-461c95e6745c4dc6ac8646b50fc73198

Hmmm, https://nextjs-notion-starter-kit.transitivebullsh.it/ shows the main repo deployed without any changes.
The screenshots show that you've at least made additional changes beyond changing rootNotionPageId since it's using a custom header. So without knowing the full scope of additional changes, it's really difficult to try to help you.
That being said, you're welcome to tweak the CSS in https://github.com/transitive-bullshit/nextjs-notion-starter-kit/blob/main/styles/notion.css to fit your needs.

Ahhh I see what's going on.
Your main collection here https://www.filmphoto.io is formatted properly, but the collection on your subpage https://www.filmphoto.io/cameras isn't formatted properly, right?
I think the issue is https://github.com/transitive-bullshit/nextjs-notion-starter-kit/blob/main/styles/notion.css#L20-L22
This makes the home page slightly wider so it shows two columns by default, but on other pages this doesn't take effect by default. You'll need to tweak this to fix your issue.

Great, thank you!


ddem bin filtering too strict for CL_NPI

During the hypsometric fit, some elevation bins are filtered by the NMAD filter. This seems too strict as it removes valid bins

A quick investigation shows that the minimum dh value is -70, while the NMAD is ~3.4. This means a factor of about 20 between the NMAD and maximum value, way beyond the factor 5 set as default.
A larger value could be set, but then the filter would most likely never be used.

What happens if you disable this filter?
I would think some combination of individual bin count/area and individual bin stats could be used to exclude potentially problematic bins, rather than a global filter.
Or maybe some "rolling bin" filter that considers values from n adjacent bins to evaluate whether a given bin is problematic.


Fixed text issue in tips pge

**Issue No: #106 **

Updated text in tips page

Preview: https://tanya-gupta25.github.io/HealhUb/pages/tips.html

So much spacing on the left? fix that


linters stopped working in sublime but work from the command line, no warnings in console

Hi,
My linters worked in the past but stopped working recently (probably after I did something that I don't remember).  It will lint my .html file with Javascript, but won't lint my .js file.

Is that console output while the javascript file has been loaded and saved? It doesn't show any activity from the linter so that typically means the linter doesn't believe it's supposed to run on that file. So also check to make sure the js file has a JavaScript syntax highlighting

Yeah, that's the output from the .js file. How do I check if the file has Javascript syntax highlighting?

In the bottom right-hand corner it should say JavaScript and if you click it, it should be coming from the JavaScript dropdown.

Ahhh that did it! I had it sent to Unity JavaScript, oops. Thank you!!!

Awesome! yeah I think that is one of the more confusing pieces of the system. It is syntax dependant, so that it doesn't try to run python linters on your js code, but that also blocks any syntax that it doesn't know. Here's a doc about setting a custom syntax map if you prefer the Unity JS syntax http://www.sublimelinter.com/en/latest/global_settings.html#syntax-map
Glad we could solve this! :beers:


chore(element): dashboard element ganache testing resolve

CI is failing for the same reason it was before, web3 module is somehow thinking it is running in electron, when building the app.


[Auth] Convert LoginView to SwiftUI

New UI for email/password page:

#no-changelog

Will address any further feedback in a following PR.


Crashing with NuclearCraft?

Issue Description:
Hi there - according to your CurseForge page, EnderIO is crashing with NuclearCraft, but I can't find any info on the details. It would be nice to try to fix this before the two mods start being considered for packs together.

https://github.com/turbodiesel4598/NuclearCraft/issues/253

oh. oops, and I didn't realize it was you who opened this issue.


Strict/StrictData

Closing as this is a language change, this should follow the Eta Proposal Process:
https://github.com/typelead/eta-proposals


Release v6.1.0

Can somone review the changelog and see if i need to update any titles/labels.
There exist only features and bugs fixes in this release so i did a minor bump

@TraGicCode looks good to me. Do you know if any of the changes are a breaking change?

From what i checked i didn't see a breaking change.  No new parameters and none removed

do you want to run the release_travis rake task?

I'm on it!


fix: split extension publishing into separate jobs

I split publishing to marketplace and open vsx into separate jobs as now, when I wanted to test publishing with different token I was not even able to do so because of successful open vsx publish, workflow was failing (as given version of extension was there already).
we need this split:

to try release again
to be able to test different tokens later without making changes in code base

@ivangsa please approve

/rtm

If the extensionId must be unique maybe it's time to request the publisher transfer in the marketplace.
If you agree I will do that tomorrow

Let's do it. And once you confirm we can rerun pipeline and immediately republish

Ok, I requested the ownership transfer
I added you as CC in the email, so you also get any update


Add IPageHandlerModelConvention to sample

IPageHandlerModelConvention is covered in the topic but should also appear as an example in the sample app.
Razor Pages route and app conventions in ASP.NET Core
mvc\razor-pages\razor-pages-conventions.md
https://docs.microsoft.com/aspnet/core/mvc/razor-pages/razor-pages-conventions

@pranavkm Need a tip: What's a good sample app example of IPageHandlerModelConvention that you think readers would like to see?
public class CustomPageHandlerModelConvention
    : IPageHandlerModelConvention
{
    public void Apply(PageHandlerModel model)
    {
        // Do something here
    }
}

@NTaylorMullen ❓ ... Is this ...
https://github.com/aspnet/Docs/blob/master/aspnetcore/razor-pages/razor-pages-conventions/sample/CustomPageApplicationModelProvider.cs
https://docs.microsoft.com/aspnet/core/razor-pages/razor-pages-conventions#replace-the-default-page-app-model-provider
... worth the effort with the (apparent) changes in protection level between 2.1 and 2.2?
If I try to base the custom page application model provider on IPageApplicationModelProvider (instead of DefaultPageApplicationModelProvider), it hates on me with further protected objects ...

Microsoft.AspNetCore.Mvc.RazorPages.Resources
HandleOptionsRequestsPageFilter
PropertyHelper

I guess I could keep ripping the guts out of the framework to try and make it work, but is it worth the effort for this scenario.

Could we drop that topic? We generally discourage replacing the application model provider, a convention is what we'd expect most users to implement.

@pranavkm You mean just drop the section and sample for it, right? ... you don't mean the entire topic, right?

You mean just drop the section and sample for it, right?

Yup 👍


portiacrawl command not found

I'm finally ready to crawl but when executing
portiacrawl /Users/<user>/Software/90\ Web\ Scraping/portia/slyd/slyd/data/projects/<project_name>
to get all spiders listed for the project, I always receive the following error message
-bash: portiacrawl: command not found
I'm using

Mac
vagrant
virtual box

I have also observed that in the documentation the path for the projects is
/slyd/data/projects/
instead of (my system)
/slyd/slyd/data/projects/
The same problem was described here, but it doesn't help:
#30

The portiacrawl program isn't added to your system path. If you want to run your spider change directory to portia/slybot/bin and run portiacrawl from there

I have navigated in the terminal to portia/slybot/bin and ran portiacrawl again, but I till receive the same error.
-bash: portiacrawl: command not found
When I doubleclick on the portiacrawl file in portia/slybot/binfrom the finder, it opens in the terminal and gives me the description, which looks everything alright.

To run it in the terminal you ned to use ./portiacrawl from the terminal. If you want to be able to run it as just portiacrawl from any directory add the directory that portiacrawl is in to your path

thanks, I'm one step further
Do I have to be in a specific directory in the terminal or does the directory not matter?
now, I can execute the portiacrawl command:
/Users/<user>/Software/90\ Web\ Scraping/portia/slybot/bin/portiacrawl /Users/<user>/Software/90\ Web\ Scraping/portia/slyd/slyd/data/projects/wg_gesucht wg-gesucht.de
but it gives out the following error message:
Traceback (most recent call last):   File "/Users/<user>/Software/90 Web Scraping/portia/slybot/bin/portiacrawl", line 65, in <module>     main()   File "/Users/<user>/Software/90 Web Scraping/portia/slybot/bin/portiacrawl", line 63, in main     subprocess.call(command_spec)   File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 522, in call     return Popen(*popenargs, **kwargs).wait()   File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 710, in __init__     errread, errwrite)   File "/usr/local/Cellar/python/2.7.11/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 1335, in _execute_child     raise child_exception OSError: [Errno 2] No such file or directory
What I'm also asking myself is how does the terminal determine between the spaces in the path and the spaces between portiacrawl PROJECT_PATH SPIDER_NAME ?

You have \  in the path and   between the arguments.
if you run cd /Users/<user>/Software/90\ Web\ Scraping/portia/ you can shorten the run command to:
slybot/bin/portiacrawl slyd/slyd/data/projects/wg_gesucht wg-gesucht.de
I think the error is because you don't have scrapy installed. Can you try running those commands from inside the vagrant vm? You can use vagrant ssh to access the vagrant VM, then cd /vagrant and then try to run the command that I gave you above. You can also look into scrapyd for running your spiders.

I received the following:
 /usr/local/lib/python2.7/dist-packages/scrapy/crawler.py:115: ScrapyDeprecationWarning: SPIDER_MANAGER_CLASS option is deprecated. Please use SPIDER_LOADER_CLASS.
  self.spider_loader = _get_spider_loader(settings)
2016-02-08 14:00:25 [scrapy] INFO: Scrapy 1.0.0 started (bot: scrapybot)
2016-02-08 14:00:25 [scrapy] INFO: Optional features available: ssl, http11
2016-02-08 14:00:25 [scrapy] INFO: Overridden settings: {'DUPEFILTER_CLASS': 'scrapyjs.SplashAwareDupeFilter'}
2016-02-08 14:00:25 [scrapy] INFO: Enabled extensions: CloseSpider, TelnetConsole, LogStats, CoreStats, SpiderState
2016-02-08 14:00:25 [py.warnings] WARNING: /usr/local/lib/python2.7/dist-packages/scrapyjs/middleware.py:8: ScrapyDeprecationWarning: Module `scrapy.log` has been deprecated, Scrapy now relies on the builtin Python library for logging. Read the updated logging entry in the documentation to learn more.
  from scrapy import log

2016-02-08 14:00:25 [py.warnings] WARNING: /usr/local/lib/python2.7/dist-packages/scrapyjs/dupefilter.py:8: ScrapyDeprecationWarning: Module `scrapy.dupefilter` is deprecated, use `scrapy.dupefilters` instead
  from scrapy.dupefilter import RFPDupeFilter

2016-02-08 14:00:25 [py.warnings] WARNING: /usr/local/lib/python2.7/dist-packages/scrapyjs/cache.py:11: ScrapyDeprecationWarning: Module `scrapy.contrib.httpcache` is deprecated, use `scrapy.extensions.httpcache` instead
  from scrapy.contrib.httpcache import FilesystemCacheStorage

2016-02-08 14:00:25 [scrapy] INFO: Enabled downloader middlewares: HttpAuthMiddleware, DownloadTimeoutMiddleware, UserAgentMiddleware, RetryMiddleware, DefaultHeadersMiddleware, MetaRefreshMiddleware, HttpCompressionMiddleware, RedirectMiddleware, PageActionsMiddleware, CookiesMiddleware, SlybotJsMiddleware, ChunkedTransferMiddleware, DownloaderStats
2016-02-08 14:00:25 [scrapy] INFO: Enabled spider middlewares: HttpErrorMiddleware, OffsiteMiddleware, RefererMiddleware, UrlLengthMiddleware, DepthMiddleware
2016-02-08 14:00:25 [scrapy] INFO: Enabled item pipelines: DupeFilterPipeline
2016-02-08 14:00:25 [scrapy] INFO: Spider opened
2016-02-08 14:00:25 [scrapy] INFO: Crawled 0 pages (at 0 pages/min), scraped 0 items (at 0 items/min)
2016-02-08 14:00:25 [scrapy] DEBUG: Telnet console listening on <IP_ADDRESS>:6023
2016-02-08 14:00:27 [scrapy] DEBUG: Crawled (200) <GET http://www.wg-gesucht.de/> (referer: None) ['partial']

And I can't remember that I installed scrapy, I thought that it would be automatically installed with portia?
In which folder should I install it?

I changed the settings in the crawler sections and now it is running continuously albeit not where I exactly want to retrieve the data, but this I can figure out later.
Thanks a bunch! Without you I would be never able to get this running!

When you are running the spider you can use -o output.json to output the data as json. Find out more here


How to get updated CSV data for multiple environment support

In continuation of issue "is it possible to have data per environment? how can this be done? #586"; I need to supply different csv file based on environment.
I'm calling a method in BeforeSuite hook which copies my test data from specific env folder to execution env folder.  [means I updated the csv file before consuming in scenario]
But during execution; my step is still referring the old csv data.
Kindly assist.
Expected behavior
In scenario execution; updated csv should be called.
table:src/test/resources/testdata/execution/data.csv
Actual behavior
Old csv file is referring.
Steps to reproduce
table:src/test/resources/testdata/execution/data.csv
Login

User Login into application with <USER_EMAIL_ID>,

Gauge version
Gauge version: 1.0.3
Plugins
html-report (4.0.6)
java (0.6.9)
screenshot (0.0.1)

duplicate of https://github.com/getgauge/gauge/issues/1083


MMSCameraViewController version issue

Hi,
Current version supports up to v1.2.1 of MMSCameraViewController as given in the podspec
s.dependency 'MMSCameraViewController',  '~> 1.2.1'
The version should be updated because it's not possible to get the current updates of MMSCameraViewController if you are using cocoapods. (for example iPhoneX support fixes of MMSCameraViewController, etc...)
Thanks in advance.

Hi, This has been corrected in version 1.6.0


How to import on ES6?

First and foremost, awesome library, works like a charm, much ❤
I have been trying to get the below working using import statements but to no avail. Could you point to, or provide an example of, how to get the below working using import statements? I am unable to get this running in my typescript file.
Big = require("big.js")
Big = require("toformat")(Big)

const big = new Big("122222222.233434")

console.log(
  big.toFormat({
    decimalSeparator: "|",
    groupSeparator: "^",
  })
)

Ok, that was harder than I thought but.. last combination works.
import { Big } from "big.js"
import toFormat from "toformat"

const someFunction = () => {
  toFormat(Big)

  const big = new Big("122222222.233434")

  console.log(
    big.toFormat({
      decimalSeparator: "|",
      groupSeparator: "^",
    })
  )
}

Would you accept a PR to the readme describing this import method?


[WIP] Cleanups of JDBC connector

is this for sql server connector?
Then nice work ;)

This is part of our streamlining of the common parts of the sql connectors. Which will make it easier to roll out more Sql flavors.


Fix downstream commit detection

In some cases, upstream commits were included in the git log command, causing the verify-git-history test to fail because the commits did not follow name rules.

/lgtm
/approve

/label jira/valid-bug

/override ci/prow/e2e-azure-ovn
/override ci/prow/e2e-azure-ovn-upgrade
This PR has zero effect on the payload, so no need to run E2E


HTTP response message: Conflict

I'm a little confused as to what is going on.  I'm using bamboo and plugin version 1.7.5
I can do a manual upload with curl no problem - but using the artifactory plugin directly is giving me 409 HTTP errors and I can't figure out how to figure out what this "conflict" is.  Could somebody provide some guidance as to what I should be looking for or how to fix this?
Oh - I'm using a Generic Deploy task also - as I'm trying to upload some zip files.
    Exception occurred while executing task
15-Feb-2016 06:00:08    java.io.IOException: Failed to deploy file: HTTP response code: 409. HTTP response message: Conflict
15-Feb-2016 06:00:08            at org.jfrog.build.client.ArtifactoryBuildInfoClient.throwHttpIOException(ArtifactoryBuildInfoClient.java:661)
15-Feb-2016 06:00:08            at org.jfrog.build.client.ArtifactoryBuildInfoClient.uploadFile(ArtifactoryBuildInfoClient.java:532)
15-Feb-2016 06:00:08            at org.jfrog.build.client.ArtifactoryBuildInfoClient.deployArtifact(ArtifactoryBuildInfoClient.java:303)
15-Feb-2016 06:00:08            at org.jfrog.bamboo.task.ArtifactoryGenericDeployTask.deploy(ArtifactoryGenericDeployTask.java:177)
15-Feb-2016 06:00:08            at org.jfrog.bamboo.task.ArtifactoryGenericDeployTask.execute(ArtifactoryGenericDeployTask.java:90)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.task.TaskExecutorImpl.executeTasks(TaskExecutorImpl.java:216)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.task.TaskExecutorImpl.execute(TaskExecutorImpl.java:102)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.build.pipeline.tasks.ExecuteBuildTask.call(ExecuteBuildTask.java:75)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent.build(DefaultBuildAgent.java:188)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.v2.build.agent.BuildAgentControllerImpl.waitAndPerformBuild(BuildAgentControllerImpl.java:112)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.v2.build.agent.DefaultBuildAgent$1.run(DefaultBuildAgent.java:110)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.utils.BambooRunnables$1.run(BambooRunnables.java:49)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.security.ImpersonationHelper.runWith(ImpersonationHelper.java:31)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.security.ImpersonationHelper.runWithSystemAuthority(ImpersonationHelper.java:20)
15-Feb-2016 06:00:08            at com.atlassian.bamboo.security.ImpersonationHelper$1.run(ImpersonationHelper.java:52)
15-Feb-2016 06:00:08            at java.lang.Thread.run(Thread.java:745)

Hi @jeeftor,
The best way to find the cause of the conflict is to look for the 409 response in the Artifactory logs. Artifactory should return the same response for the PUT requests sent from curl and the plugin. I suggest you compare the two requests as they are printed in the logs. Please let us know if this helps.

Hi @jeeftor
In the artifactory plugin I had the same issue, the problem was that I had specified a wrong snapshot repository where I didn't had the rights, maybe this helps you
kr

For me the problem was i didnt assemble new aar and tried to send the old one

The HTTP 409 can happen when you try to upload a .jar with some information (e.g. version) but it already has a conflicting jar inside.


Motify typo in pulsar-client-admin-shaded/pom.xml

In the pulsar project, it is found that the  tag of the "pom.xml" file in multiple sub modules is incorrect. Do you need to modify it?
<parent>     <groupId>org.apache.pulsar</groupId>     <artifactId>pulsar</artifactId>     <version>2.10.0-SNAPSHOT</version>     <relativePath>../pom.xml</relativePath>   </parent>

Test


Extended example of picocli-shell-jline2 with IParameterConsumer

I also tested interactive options in the jline3 variant. They work fine.
Changes for #767

Codecov Report

Merging #775 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #775   +/-   ##
=========================================
  Coverage     93.15%   93.15%
  Complexity      385      385
=========================================
  Files             2        2
  Lines          5684     5684
  Branches       1480     1480
=========================================
  Hits           5295     5295
  Misses          186      186
  Partials        203      203

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 fe37466...1f886d5. Read the comment docs.


std::result_of has been deprecated in C++17 and removed in C++20. Replaced by std::invoke_result

std::result_of has, as of writing, 8 occurances in infra/util/Observer.hpp
Since C++17 a helper type has been added for std::invoke_result, named std::invoke_result_t removing the need of using std::invoke_result<...>::type

I take it we can close this issue

This has been fixed in modern-cmake, but is not (yet) part of develop. If that suits your needs then keep the issue closed. Otherwise you can leave it open until the fix lands in develop.


Duplicated events handling

It may happen that we receive the same event multiple times (https://github.com/keep-network/keep-ecdsa/issues/355). We don't want to kick off duplicated processes for such events.
In this PR we introduce a way to track requests and start only single processes for them.
We register an event in the struct after receiving it. If it's already there we will log an error and return from the process. If it's a unique event we will start the process. While we return from the process (no matter if with failure or success) we will remove the event from the tracking struct.
Closes: https://github.com/keep-network/keep-ecdsa/issues/355

@nkuba Can you please merge master or rebase?

@nkuba @lukasz-zimnoch Tests updated as discussed, please take a look.

/LGTM


Remove sanitizing outbound request URI

There was feature to sanitize outbound request URI. However, doing so is wrong. We only should sanitize inbound request request URI. This PR fixes this issue.
Moreover, in addition to that, I have refactored the code a bit to make it more readable.

Below is the issue for this PR.

PR fixes #4316


native-image unit test inject reference bean failed

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 3.3.0-beta.2-SNAPSHOT
Operating System version: macOS 14.1.2
Java version: GraalVM Oracle 17.0.9

Steps to reproduce this issue

clone https://github.com/FoghostCn/dubbo-samples/tree/master/2-advanced/dubbo-samples-native-image/
run dubbo-samples-native-image-provider first
cd /dubbo-samples-native-image-consumer
exec mvn clean test -PnativeTest

Expected Behavior
unit test pass
Actual Behavior
NullPointerException, demoService is not inject, it is null

@CrazyHZM PTAL


performance reduction while open incremental validation

What did you do?

create dm and tidb cluster
create source and task with incremental validation
add workload to

What did you expect to see?
replication qps and txn execution latency performance reduce less than 5%.
What did you see instead?
performance reduce more than 5%.
Versions of the cluster
DM version (run dmctl -V or dm-worker -V or dm-master -V):
v6.2.0

Upstream MySQL/MariaDB server version:
(paste upstream MySQL/MariaDB server version here)

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
(paste TiDB cluster version here)

How did you deploy DM: tiup or manually?
(leave TiUP or manually here)

Other interesting information (system version, hardware config, etc):
>
>

current status of DM cluster (execute query-status <task-name> in dmctl)
(paste current status of DM cluster here)

/assign buchuitoudegou

/severity minor

/found automation


Clean up

Remove overcomplicated break match construct
Use bounded loop to prevent accidentally turning it into an infinite loop

I mean... Sure. I suppose we have very different ideas of what makes good code (robustness vs readability).
Agree to disagree on this one.
PS: Not sure why you didn't just push to #2479, I was always gonna see it since I have to rebase on top for the rest of the changes anyway ¯\_(ツ)_/¯ .

It's not like I'm hiding this change, but

The other changes were good as is
I don't think I can approve a PR that I edit

Even if I can, I shouldn't
I also shouldn't ask the others to review more than they need to
I also can't be sure when someone takes the time to review something

So for multiple reasons, I instead merged your PR to not let it sit and accumulate merge conflicts.

Agree to disagree on this one.

I am happy to leave it here. Your contributions are appreciated either way!


feat: Chaos in Contact form input fields

This pr intends to cause chaos in the input field of contact forms.
https://github.com/user-attachments/assets/fefe6d2a-a725-45ac-af33-b52460cd98f7
Labels:

Priority: Medium
Level: 1
gssoc-extd

Sir, I am having a failure with the deployment. Can you guide on this.

@KhawajaFashi  Firstly tell me which issue did you work upon
Mention on your issue like this ⬇
Closes: #issuenumber

@KhawajaFashi  Firstly tell me which issue did you work upon
Mention on your issue like this ⬇
Closes: #issuenumber

Closes: #14

@KhawajaFashi  Firstly tell me which issue did you work upon
Mention on your issue like this ⬇
Closes: #issuenumber

Closes: #14

These are the errors due to which deployment is failed, please look into it

I have fixed the errors in navbar.jsx then what could be the problem now?

Close this PR and create a new one
Mention the issue as well as this PR in the new PR


[#1833] Added landmarks for improved keyboard navigation.

#1833
===
Added ARIA landmarks for easier keyboard navigation.
Here's a visual representation:

If the tabs are split, the two groups will read: "primary editor region" & "secondary editor region"

Coverage decreased (-0.005%) to 65.826% when pulling c40ea195b86352239c4cdde5a4b00718f1e3f7e0 on toanzian/acc-#1833 into c7a8a91fa7ed408bee49343f7c9ff792d405b857 on master.


Split and analyze multiple SQL

I now have a scenario that is the online management of SQL scripts. I need to parse all SQL of a file string into a list for item by item parsing. Now I haven't found a useful method. Do you support it? Or can I use ";" as the end of a single SQL? Hope to get some support.

Greetings.
net.sf.jsqlparser.parser.CCJSqlParserUtil#parseStatements(java.lang.String) is your friend:
/**
     * Parse a statement list.
     *
     * @return the statements parsed
     */
    public static Statements parseStatements(String sqls) throws JSQLParserException {
        boolean allowComplexParsing = getNestingDepth(sqls)<=ALLOWED_NESTING_DEPTH;

        CCJSqlParser parser = newParser(sqls).withAllowComplexParsing(allowComplexParsing);
        return parseStatements(parser);
    }


Unwanted TCP telemetry [istio 1.6.0-rc.0 w/ CNI]

Using Istio 1.6.0-rc.0 on OpenShift 4.4.3 (CNI) there is unwanted TCP traffic involving mgmtCluster.  This is not new in rc.0 but I don't know when it was introduced.   There is telemetry from unknown to destination_service_name "mgmtCluster" and to each destination_workload.  This is what I see with rc.0 using bookinfo with mongo.

For comparison, this is the same using 1.5.2, where the telemetry looks better:

In both versions the traffic from ratings-v2 to mongo is not great, it's split as traffic from unknown to the mongo workload, and also as a request from ratings-v2 to the mongo service (but without  any workload).  It's likely a different issue, but letting you know just in case it's related.
Expected behavior
The unwanted traffic should be filtered (see the 1.5.2 screenshot).
Steps to reproduce the bug
Run bookinfo with 1.6.0-rc.0 and check the telemetry.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
See above.
How was Istio installed?
istioctl
Environment where bug was observed (cloud vendor, OS, etc)
OpenShift 4.4.3 on AWS
This may be related to https://github.com/istio/istio/pull/23841

Is it possible for you to test with 1.6.0-beta.1?

@jacob-delgado That is what I was running yesterday when I reported this issue in slack.  1.6.0-beta.1 did have this tcp problem, as well as the http problem with InboundPassthroughClusterIpv4.  The latter went away with rc.0.

I am able to replicate this with OpenShift 4.4.3. Going to test with vanilla k8s.

This might break other dashboards & alerting etc folks might have. Does anyone know what’s causing this?

1.6.0-rc.2 solves the mgmtCluster issue in my testing on OpenShift 4.4.3.
If necessary, I will open a separate issue to follow up on the way the mongo traffic is represented.

1.6.0-rc.2 solves the mgmtCluster issue in my testing on OpenShift 4.4.3.
If necessary, I will open a separate issue to follow up on the way the mongo traffic is represented.

Let's close this issue--I'll have you do it since you opened it--and open an new one to track. Thanks for verifying this.


extend image singlespa/import-map-deployer and use config.json file

Is this a correct sample setup to work correctly with singlespa/import-map-deployer?

I've now reverted the conf.js file, added a Readme and typings for NodeJS (to avoid red scribbles in VSCode).

Yes, not easential. My VS code setup was complaining about the global process refs without it though.


SystemError in tf.constant when dtype is tf.uint64 and value is nagetive.

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
tf 2.15
Custom code
No
OS platform and distribution
Linux Ubuntu 20.04
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
I know that negative number is an unexpected input, but when the dtype is tf.uint32 and tf.uint64,tf.constant can map negative number to the corresponding unsigned integer. In fact,tf.uint32 does exactly this.
Taking tf.constant(-10, dtype=tf.uint64) as an example, in eager mode, this API will trigger a SystemError error when it is called for the first time, but subsequent calls will no longer trigger the error. I think it is a bug.
Standalone code to reproduce the issue
https://colab.research.google.com/drive/17EtoIjT5Ml7FOQnSh5PIxMcVQFB_eDNF#scrollTo=UBwqMQNy4OHb

Relevant log output
SystemError: <class 'tensorflow.python.framework.ops.EagerTensor'> returned a result with an exception set

@xl1043237213  tf_value = tf.constant(-10, dtype=tf.uint64) tries to create a constant tensor named tf_value with the value -10 and data type tf.uint64. However, tf.uint64 can only represent non-negative integers.
Could you please ensure you only provide non-negative values when using tf.constant with unsigned integer dtypes.
Thank you!

Thanks for your response. :)
tf_value = tf.constant(-10, dtype=tf.uint64) triggers SystemError but tf_value = tf.constant(-10, dtype=tf.uint32) does not. I think it's a matter of insufficient processing of boundary inputs. If value of tf.constant must be a non-negative integer when using with unsigned integer dtypes, I think tf.constant should trigger ValueError when value  is a negative integer.

@xl1043237213  You are right about the expected behavior. Could you explicitly check the value before passing it to tf.constant. You can use an if statement or a function like tf.math.greater_equal to ensure the value is non-negative. In the future TensorFlow versions will address this behavior and provide a more informative error message.
Thank you!

Thanks. I got it.

@xl1043237213 Could you please let us know if we can move this issue to closed status?
Thank you!

Yes, I hope tensorflow will fix the issue soon.😊 I will close this issue.


[wip]Add eBPF support for optimizer

Add pkg/optimizer package.
Remove events configuration entry which is no need for users.
Add eBPF support for optimizer.

Here is a example output for eBPF optimizer:
> cat pytorch:1.12.1.csv
timestamp,command,path,position,size
1688978328332,python,/root/miniconda3/lib/python3.10/lib-dynload/cmath.cpython-310-x86_64-linux-gnu.so,118784,4096
1688978328375,python,/root/miniconda3/lib/python3.10/lib-dynload/_socket.cpython-310-x86_64-linux-gnu.so,184320,4096
1688978328377,python,/root/miniconda3/lib/python3.10/lib-dynload/array.cpython-310-x86_64-linux-gnu.so,126976,4096
1688978328379,python,/root/miniconda3/lib/python3.10/lib-dynload/_multiprocessing.cpython-310-x86_64-linux-gnu.so,28672,4096
1688978328416,python,/root/miniconda3/lib/python3.10/lib-dynload/_ssl.cpython-310-x86_64-linux-gnu.so,348160,4096
1688978328416,python,/root/miniconda3/lib/libssl.so.1.1,1122304,4096
1688978328424,python,/root/miniconda3/lib/python3.10/lib-dynload/unicodedata.cpython-310-x86_64-linux-gnu.so,2224128,4096
1688978328429,python,/root/miniconda3/lib/python3.10/lib-dynload/_asyncio.cpython-310-x86_64-linux-gnu.so,114688,4096

The runtime environment for this patch is harsh and the project gobpf is unmaintained for a while. I would like to consider a more suitable library to implement this feature.

Is it still in progress?


cpu 100% problem

@wu-sheng My project include cpp2sky to report tracing data, i find one thread cost cpu 100%,afer debug i think find a bug:
void TracerImpl::run() {
  void* got_tag;
  bool ok = false;
  while (true) {
    // TODO(shikugawa): cleanup evloop handler.
    if (cds_timer_ != nullptr && cds_timer_->check()) {
      cdsRequest();
    }

    grpc::CompletionQueue::NextStatus status = cq_.AsyncNext(
        &got_tag, &ok, gpr_time_from_nanos(0, GPR_CLOCK_REALTIME));

here should be  GPR_TIMESPAN,  so i fix like follow  in my local branch  :
  void* got_tag;
  bool ok = false;
  while (true) {
    // TODO(shikugawa): cleanup evloop handler.
    if (cds_timer_ != nullptr && cds_timer_->check()) {
      cdsRequest();
    }

#if 0
    grpc::CompletionQueue::NextStatus status = cq_.AsyncNext(
        &got_tag, &ok, gpr_time_from_nanos(0, GPR_CLOCK_REALTIME));
#endif
    grpc::CompletionQueue::NextStatus status = cq_.AsyncNext(
        &got_tag, &ok, gpr_time_from_nanos(100000000, GPR_TIMESPAN));
    switch (status) {
      case grpc::CompletionQueue::TIMEOUT:
        continue;
      case grpc::CompletionQueue::SHUTDOWN:
        return;
      case grpc::CompletionQueue::GOT_EVENT:
        break;
    }
    static_cast<StreamCallbackTag*>(got_tag)->callback(!ok);
  }
}

ping @wbpcode

here should be GPR_TIMESPAN, so i fix like follow in my local branch :

I am not very familiar to the gRPC lib and didn't use the grpc client in this sky2cpp lib. So, feel free to point out if I am wrong.
The AsyncNext method here take a deadline parameter, seems it shouldn't be a type of GPR_TIMESPAN.
Can you paste a link or doc here to tell why GPR_TIMESPAN should be used here?

here should be GPR_TIMESPAN, so i fix like follow in my local branch :

I am not very familiar to the gRPC lib and didn't use the grpc client in this sky2cpp lib. So, feel free to point out if I am wrong. The AsyncNext method here take a deadline parameter, seems it shouldn't be a type of GPR_TIMESPAN.
Can you paste a link or doc here to tell why GPR_TIMESPAN should be used here?
code is best doument , practice is best guid


Create KedroMlflowConfig.setup() method and enable configuration to export credentials as environment variables

Description
Fix #31 and #97.
Development notes

When instantiating a KedroMlflowConfig object, there is no interaction with mlflow to create the associated experiment. It must be created explicitly
A method was added to export mlflow credentials on the fly when running a pipeline.

# credentials.yml
my_credentials:
  AWS_SECRET_KEY: <key>

# mlflow.yml
credentials: my_credentials

interactively, you must now call the setup method to setus the configuration up:

# exploratory.py
from kedro.context import load_context
from kedro_mlflow.context import get_mlflow_config

context=load_context(".")
mlflow_config=get_mlflow_config(context)
mlflow_config.setup(context)

Checklist

[X] Read the contributing guidelines
[X] Open this PR as a 'Draft Pull Request' if it is work-in-progress
[X] Update the documentation to reflect the code changes
[X] Add a description of this change and add your name to the list of supporting contributions in the CHANGELOG.md file. Please respect Keep a Changelog guidelines.
[X] Add tests to cover your changes

Notice

[X] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Codecov Report

Merging #126 (70760cc) into develop (63dcd50) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##           develop      #126   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           25        25
  Lines          713       725   +12
=========================================
+ Hits           713       725   +12

Impacted Files
Coverage Δ

kedro_mlflow/framework/context/config.py
100.00% <100.00%> (ø)

kedro_mlflow/framework/hooks/pipeline_hook.py
100.00% <100.00%> (ø)

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 63dcd50...70760cc. Read the comment docs.

Managing datsets credentials is a totally different thing because we need to export temporarily credentials to avoid interfereing with the tracking credentials. This is in the very short term todo list, though.


More Sign In changes

This PR targets the alpha branch.

Input account is now address. The app cannot be expected to have a reference to, or be able to construct, a WalletAccount object before connecting to the wallet. The account's address is already expected to uniquely identify the account. This also brings the field name inline with EIP-4361.
Input chain is now chainId. The type is loosened to string. The wallet should not care what this value is, as it only concerns the application and sign in messages generally should not be used by on chain programs to secure access to resources. This also brings the field name inline with EIP-4361.
Input version has been loosened to string. The wallet should not care what this value is, there's only 1 version in EIP-4361, and we'd need to update the spec for the feature if the fields changed.
Output signatureType has been tightened to ed25519. Wallets and apps will need to understand the same signature types, and only one is supported for now. The minor feature version should change if we support more signature types.
Doc comments added.

Published
🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>🦋<EMAIL_ADDRESS>


Don't show PASS on success for gitvalidate

Make test logs less verbose so that failures are easier to spot.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

Fixes: https://github.com/containers/libpod/issues/4581
@edsantiago PTAL

@ssbarnea PTAL

Ok, I thought the pipefail would exit with != 0.

It does, but remember that make executes every separate line in a separate shell; so a lone set -o pipefail on its own line will not affect the next one. Very quick testing on my end shows this to be more promising:
    set -o pipefail; GIT_CHECK_EXCLUDE=...

Long rambling notes ahead, caveat lector.
First, it turns out that vbatts/git-validation has both -v and -q flags, and we're invoking it with -v. That goes a long way toward explaining the verbosity. After playing with removing -v and/or adding -q, I think the most helpful output comes from simply removing -v, not adding -q, and changing the grep in your PR to:
          ... | { egrep -v ' PASS$$' || test $$? = 1; }

(that is, use egrep instead of grep, and then single-quote, space, PASS, dollar, dollar, single quote). The reason for that is that just grepping out PASS would filter any commit message containing the string PASS - such as this one.
Going further, I think the ultimate root cause here is the hardcoding of EPOCH_TEST_COMMIT.

How about this (on Makefile:6) and removing the -v on the git-validation call (line 470)?
EPOCH_TEST_COMMIT ?= $(shell git merge-base HEAD $${DEST_BRANCH:-master})

@edsantiago Fixed
@mheon PTAL

Oh - what I was suggesting is that with the git merge-base you no longer need the pipefail nor grep -v

LGTM! Before merging: @cevich, could you take a look at the EPOCH change and give it your blessing?

/lgtm

could you take a look at the EPOCH change and give it your blessing?

I was too late/slow :cry: I think my concerns were minor though, given that we already run git all over the place in the Makefile and nothing broke before this merged :smile: