HDDS-1735. Create separate unit and integration test executor dev-support script

hadoop-ozone/dev-support/checks directory contains multiple helper script to execute different type of testing (findbugs, rat, unit, build).
They easily define how tests should be executed, with the following contract:
* The problems should be printed out to the console
* in case of test failure a non zero exit code should be used

The tests are working well (in fact I have some experiments with executing these scripts on k8s and argo where all the shell scripts are executed parallel) but we need some update:
1. Most important: the unit tests and integration tests can be separated. Integration tests are more flaky and it's better to have a way to run only the normal unit tests
2. As HDDS-1115 introduced a pom.ozone.xml it's better to use them instead of the magical "am pl hadoop-ozone-dist" trick--
3. To make it possible to run blockade test in containers we should use - T flag with docker-compose
4. checkstyle violations are printed out to the console
See: https://issues.apache.org/jira/browse/HDDS-1735

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
31
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
31
Maven dependency ordering for branch

+1
mvninstall
472
trunk passed

+1
mvnsite
0
trunk passed

-1
pylint
1
Error running pylint. Please check pylint stderr files.

+1
shadedclient
726
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
31
Maven dependency ordering for patch

+1
mvninstall
449
the patch passed

+1
mvnsite
0
the patch passed

-1
pylint
1
Error running pylint. Please check pylint stderr files.

+1
pylint
1
There were no new pylint issues.

-1
shellcheck
1
The patch generated 8 new + 6 unchanged - 0 fixed = 14 total (was 6)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
715
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
88
hadoop-hdds in the patch passed.

+1
unit
168
hadoop-ozone in the patch passed.

+1
asflicense
36
The patch does not generate ASF License warnings.

2947

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs pylint

uname
Linux c87588353a8c 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / d203045

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/artifact/out/branch-pylint-stderr.txt

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/artifact/out/patch-pylint-stderr.txt

shellcheck
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/artifact/out/diff-patch-shellcheck.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/testReport/

Max. process+thread count
413 (vs. ulimit of 5500)

modules
C: hadoop-ozone hadoop-ozone/fault-injection-test/network-tests U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/1/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 pylint=1.9.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
32
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
52
Maven dependency ordering for branch

+1
mvninstall
482
trunk passed

+1
mvnsite
0
trunk passed

-1
pylint
5
Error running pylint. Please check pylint stderr files.

+1
shadedclient
783
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
22
Maven dependency ordering for patch

+1
mvninstall
431
the patch passed

+1
mvnsite
0
the patch passed

-1
pylint
6
Error running pylint. Please check pylint stderr files.

+1
pylint
6
There were no new pylint issues.

+1
shellcheck
0
The patch generated 0 new + 0 unchanged - 7 fixed = 0 total (was 7)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
703
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
104
hadoop-hdds in the patch passed.

+1
unit
176
hadoop-ozone in the patch passed.

+1
asflicense
48
The patch does not generate ASF License warnings.

3007

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs pylint

uname
Linux 2c4cf55cdab1 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 1c254a8

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/2/artifact/out/branch-pylint-stderr.txt

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/2/artifact/out/patch-pylint-stderr.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/2/testReport/

Max. process+thread count
444 (vs. ulimit of 5500)

modules
C: hadoop-ozone hadoop-ozone/fault-injection-test/network-tests U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/2/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 pylint=1.9.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
32
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
44
Maven dependency ordering for branch

+1
mvninstall
504
trunk passed

+1
mvnsite
0
trunk passed

-1
pylint
1
Error running pylint. Please check pylint stderr files.

+1
shadedclient
772
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
32
Maven dependency ordering for patch

+1
mvninstall
454
the patch passed

+1
mvnsite
0
the patch passed

-1
pylint
2
Error running pylint. Please check pylint stderr files.

+1
pylint
2
There were no new pylint issues.

+1
shellcheck
1
The patch generated 0 new + 0 unchanged - 7 fixed = 0 total (was 7)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
708
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
103
hadoop-hdds in the patch passed.

+1
unit
179
hadoop-ozone in the patch passed.

+1
asflicense
48
The patch does not generate ASF License warnings.

3076

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs pylint

uname
Linux f16dcd073b52 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9c90729

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/3/artifact/out/branch-pylint-stderr.txt

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/3/artifact/out/patch-pylint-stderr.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/3/testReport/

Max. process+thread count
446 (vs. ulimit of 5500)

modules
C: hadoop-ozone hadoop-ozone/fault-injection-test/network-tests U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/3/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 pylint=1.9.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
32
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
32
Maven dependency ordering for branch

+1
mvninstall
474
trunk passed

+1
mvnsite
0
trunk passed

-1
pylint
1
Error running pylint. Please check pylint stderr files.

+1
shadedclient
774
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
30
Maven dependency ordering for patch

+1
mvninstall
453
the patch passed

+1
mvnsite
0
the patch passed

-1
pylint
2
Error running pylint. Please check pylint stderr files.

+1
pylint
2
There were no new pylint issues.

+1
shellcheck
2
The patch generated 0 new + 0 unchanged - 7 fixed = 0 total (was 7)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
702
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
104
hadoop-hdds in the patch passed.

+1
unit
179
hadoop-ozone in the patch passed.

+1
asflicense
49
The patch does not generate ASF License warnings.

3029

Subsystem
Report/Notes

Docker
Client=17.05.0-ce Server=17.05.0-ce base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs pylint

uname
Linux cc2fdb9998fb 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9c90729

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/4/artifact/out/branch-pylint-stderr.txt

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/4/artifact/out/patch-pylint-stderr.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/4/testReport/

Max. process+thread count
411 (vs. ulimit of 5500)

modules
C: hadoop-ozone hadoop-ozone/fault-injection-test/network-tests U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/4/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 pylint=1.9.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

@elek  I was trying to merge, but seems like we have some conflicts. Perhaps due to the fact that I merged a patch from nanda, also there is an author check warning.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
69
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

0
shelldocs
1
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

+1
test4tests
0
The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

0
mvndep
50
Maven dependency ordering for branch

+1
mvninstall
532
trunk passed

+1
mvnsite
0
trunk passed

-1
pylint
8
Error running pylint. Please check pylint stderr files.

+1
shadedclient
792
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
32
Maven dependency ordering for patch

+1
mvninstall
474
the patch passed

+1
mvnsite
0
the patch passed

-1
pylint
8
Error running pylint. Please check pylint stderr files.

+1
pylint
8
There were no new pylint issues.

+1
shellcheck
0
The patch generated 0 new + 0 unchanged - 7 fixed = 0 total (was 7)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
669
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
99
hadoop-hdds in the patch passed.

+1
unit
175
hadoop-ozone in the patch passed.

+1
asflicense
40
The patch does not generate ASF License warnings.

3152

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/5/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs pylint

uname
Linux 3e3d75757cf8 4.4.0-138-generic #164-Ubuntu SMP Tue Oct 2 17:16:02 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9119ed0

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/5/artifact/out/branch-pylint-stderr.txt

pylint
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/5/artifact/out/patch-pylint-stderr.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/5/testReport/

Max. process+thread count
423 (vs. ulimit of 5500)

modules
C: hadoop-ozone hadoop-ozone/fault-injection-test/network-tests U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/5/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6 pylint=1.9.2

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
38
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

0
@author
0
Skipping @author checks as author.sh has been patched.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1
mvninstall
469
trunk passed

+1
mvnsite
0
trunk passed

+1
shadedclient
732
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1
mvninstall
426
the patch passed

+1
mvnsite
0
the patch passed

+1
shellcheck
1
The patch generated 0 new + 0 unchanged - 7 fixed = 0 total (was 7)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
632
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
98
hadoop-hdds in the patch passed.

+1
unit
176
hadoop-ozone in the patch passed.

+1
asflicense
41
The patch does not generate ASF License warnings.

2788

Subsystem
Report/Notes

Docker
Client=18.09.7 Server=18.09.7 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1035

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs

uname
Linux 36fd912879ea 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24 10:58:50 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 9119ed0

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/6/testReport/

Max. process+thread count
446 (vs. ulimit of 5500)

modules
C: hadoop-ozone U: hadoop-ozone

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1035/6/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

@elek I was trying to merge, but seems like we have some conflicts. Perhaps due to the fact that I merged a patch from nanda, also there is an author check warning.

Yes, I rebased in on the top of the trunk.
Author check is false positive as one of the scripts greps for "@author" tags, obviously it contains the @author inside as string. I changed it to use string concatenation (@a + uthor) to make yetus happy....


low_power example: pick nits

Objective

no-longer-extant type WinitConfig referenced in comments
mouse_button_input refers to KeyCode input
"spacebar" flagged as a typo by RustRover IDE

Solution

replace WinitConfig with WinitSettings in comments
rename mouse_button_input to just button_input
change "spacebar" to "space bar"

☝🏻 updated main on my fork and rebased


PDP Fit & Finish

Overall, LGTM. I would be fine merging as is, no matter the result of that style discussion. Let's give it a few mins and see if Claudina weighs in.

DTM.


On-90

Add check if batchIndex is zero
this tafera is related to this item in the jira
create new Test for CarbonChain.check
added another test to check if the carbonChain check method returns a boolean
add a pattern that removes all .d.ts files from the coverage folder
translate jsdocs translated portuguese to english

updated the carbonChain check types


2D backpack demo could not work.

With Git repository cartographer_ros 319be1ad, cartographer 4f1914b2  and ceres-solver version 1.12.0, 2D backpack demo could not generate map, wrong status:

rostopic echo /tf: shows imu_link data not changing, vertical_laser_link changing with topic /imu
the map stop changed after first submap generated, even all topices correct read from bag file.

.

I am unable to reproduce this. Could you send the exact commandline you ran and maybe a screencapture of the problem you see (because the screenshot does not seem wrong to me).

I just follow the comands at document about
Download the 2D backpack example bag.
wget -P ~/Downloads https://storage.googleapis.com/cartographer-public-data/bags/backpack_2d/cartographer_paper_deutsches_museum.bag
Launch the 2D backpack demo.
roslaunch cartographer_ros demo_backpack_2d.launch bag_filename:=${HOME}/Downloads/cartographer_paper_deutsches_museum.bag
And I will show you some  screenshot Gif later.
I found it when I do some test for 2D laser and imu, i meet some error and I have posted some screenshot about my project at here, after that I re-test cartographer_paper_deutsches_museum.bag and I found it was almost the same.

@SirVer I had got a screencapture to show you some status, please check mp4 video file, I don't know whether it is correct that I learned the map coordinate system was not changed with IMU coordinate system changing.

@bygreencn Your problem is clearly visible in the GIF, thanks for making it.
Your terminal output shows that you are far from real-time - the sensor data is only consumed at 2-3% real time. This indicates that either you did not build in release mode (which should be impossible if you did not change the CMakeLists.txt) or that your Ceres library does not have access to all its dependencies.
I suggest nuking your build directories and restart from scratch. Maybe your build configuration got messed up. If this does not work, I suggest trying to run inside one of our Docker containers and see if the problem is gone there.
Maybe related: https://github.com/googlecartographer/cartographer_ros/issues/247

Closing, as this seems to be build environment related and not really a Cartographer issue. If you think Cartographer could change something to improve the situation, I will reopen.

@SirVer Yes, I run it on Debug mode, 2d demo bag file and my test projcet. Do you mean that these status is reasonable, if I changed to release version, I could get the correct result? I will try and give an response.

@bygreencn Yes, debug mode is 50-100 times slower, i.e. unusable. We terminate compilation for that reason when you try to compile in debug mode.


Fix ARM Template

Changes to fix ARM template deployment. As of today it fails when the DSC extension is invoked.
Tracked in Issue #84

As of now, the DSC script is still not working. This is the last fix needed to merge this branch.


Investigate issue when switching user profiles

There is an issue when switching user profiles that needs to be investigated.

Under investigation from the proxy team. On hold until further updates from the proxy team or Giuseppe Mendola.

KLP Login Widget was not the cause


KOGITO-4569: Additional tests

Additional tests of executing models containing:

Relation Expression
Collect Hit Policy Decision Table Expressions
Multiple DRDs
DMN model including another DMN model

For more details see: https://issues.redhat.com/browse/KOGITO-4569
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting master: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

The Linux check is successful.


Implement case-specific database, table names

Current implementation ignores casing in database and table names.
Allow for names to be case-specific.

Targetted by #7.


Troubleshoot Logout

Make sure logout is working the way we wanted.
When faculty logs out and when student logs out.

When faculty logs out the student should automatically be disconnected.
When the student logs out, the student should be removed from faculty's list.

Student doesn't disappear from the instructor's list when they log out after connecting.


Added seasons client

Added seasons client for endpoint:
https://docs.api.jikan.moe/#tag/seasons

Hey, @tutkli, it's done.

@andron0909 Thank you! This PR is available in v0.6.4 😄


[5.7][CodeCompletion] Don't suggest initializers on existential types

Cherry-pick #59265 into release/5.7
rdar://94369218

@swift-ci Please test

@swift-ci Please test


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/MatthewMueller/cheerio
https://github.com/cheeriojs/cheerio

https://github.com/mikeal/request
https://github.com/request/request

Thanks Mr. README Bot. This repo is no longer maintained, as noted in the README.

:sweat_smile:


Update Links Property href to resource

In the latest jsonapi.org Standard, the url to fetch related records was renamed to resource, see http://jsonapi.org/format/#document-structure-resource-relationships

@wwwdata Progress on RC3 compliance can be found in [this pull request] (https://github.com/kurko/ember-json-api/pull/71). Please add your comment there if the issue persists in the latest version of the pull request.

yes, this issue is old, i will close it


Theme installation command produces an empty directory

I have no idea if it's just me but despite the fact it was working two days ago on the same machine, now the installation command just produce an empty directory

nuxt content command is still working properly

Oh thanks, should be fixed now!


Have a router to handle different pages

https://www.npmjs.com/package/react-router?ref=hackernoon.com
Front page with tracking of how many of the tasks for each workshop that is finished. And which workshop and workshop area to show.

Got the routing part working. Mostly. Closing for now.


Worker Prefetch results ignored by browser

Qwik Version
v<IP_ADDRESS>
Operating System (or Browser)
Debian Linux
Node Version (if applicable)
No response
Which component is affected?
Qwik Runtime
Expected Behaviour
Prefetched files are in the cache and ready to go.
Actual Behaviour
The browser refetches the files that the worker already fetched.
Additional Information
You can check it the network tab here and then click the Cart button in the top right: https://33f24279.storefront-qwik-starter.pages.dev/

https://www.loom.com/share/0cf6c67be84a491a850a88baa0a091fe

My bad. Moral of the story: Don't have disable cache on in your network tab while debugging.


rs.AddAlignedDimension: use view cplane when colinear points are pass…

…ed. Fixes #RH-61121

RH-61121


../@key doesn't work

../@key doesn't work to get the index of a parent loop.

lib/runtime/context.js <- this is where to look to try and fix that bug.

Thanks. I was mainly just adding the issue to remember to do it later. :)

On Nov 26, 2016, at 10:53 AM, Michaelangelo Jong<EMAIL_ADDRESS>wrote:
lib/runtime/context.js <- this is where to look to try and fix that bug.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

slash paths are no longer a feature.


[jnigen] lints

@HosseinYousefi please address lint issues or mark as good-first-issue and contributions-welcome.

@HosseinYousefi please address lint issues or mark as good-first-issue and contributions-welcome.

I'll fix them. Thanks!


Time Range Picker

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Hi, is there any plan to develop a time range picker ? Thanks
Examples 🌈
No response
Motivation 🔦
No response

We don't have it on the roadmap as of now. However, if we see significant interest in the community, we may consider creating one.


WFFHCOHORT-178 : Implement Measure Evaluation in REST API

This PR enables the /evaluation API in the cohort engine REST service that was previously stubbed out. It removes all the previously stubbed out APIs related to batch execution since those features are not part of the R1 target. They may be added back again at a later date.
The /evaluation API now takes as input a MIME multipart/form-data request. The multipart message should have two attachments:

requestData which is a JSON structure describing the evaluation to perform including the FHIR server credentials for data and terminology, the patient to evaluate, the measure to evaluation, parameter overrides for the CQL engine, and measure evidence options. I opted to use the existing JSON config format to configure the FHIR server endpoint.
measure which is a ZIP file in the authoring tool's measure artifact format (measure.json in a fhirResources folder and all library.json files in fhirResources/libraries). The response is a FHIR Measure Report artifact or an error response. See the Swagger page for complete details.

A test request can be executed using curl -F<EMAIL_ADDRESS><EMAIL_ADDRESS>https://.../services/cohort/api/v1/evaluation?version=2021-03-11.
Here is a sample of requestData.json:
{
    "dataServerConfig": {
        "@class": "com.ibm.cohort.fhir.client.config.IBMFhirServerConfig",
        "endpoint": "ENDPOINT",
        "user": "USER",
        "password": "PASSWORD",
        "logInfo": [
            "REQUEST_SUMMARY",
            "RESPONSE_SUMMARY"
        ],
        "tenantId": "test-fvt"
    },
    "patientId": "PATIENTID",
    "measureContext": {
        "measureId": "MEASUREID",
        "parameters": {
            "Measurement Period": {
                "type": "interval",
                "start": {
                    "type": "date",
                    "value": "2019-07-04"
                },
                "startInclusive": true,
                "end": {
                    "type": "date",
                    "value": "2020-07-04"
                },
                "endInclusive": true
            }
        }
    },
    "evidenceOptions": {
        "includeEvaluatedResources": false,
        "defineReturnOption": "ALL"
    }
}

In order to support passing of parameter override values into the REST API, we needed a canonical representation of parameters as JSON objects. The MeasureCLI had done some work in this area, but it was local to the cohort-cli project and it used the original command-line string encoding mechanism to inform its design. I opted in this PR to go for a more strongly typed approach. I added a full Parameter type hierarchy where each type only defines the specific properties that are relevant to that type. Each of these Parameter subclasses supports mapping from their representation to the CQL typesystem representation. These new Parameter objects were used to replace the MeasureCLI implementation which caused a lot of ripple down effects. Most notably, the JSON configuration file format for the MeasureCLI has changed in the way that parameters are expressed. Parameters are now a map that looks like "parameters": {"parameter1" : { "type": "integer", value=10 } }" etc.
The Measurement Period parameter needed some special attention. We have an implementation that will generate a Measurement Period parameter in some circumstances and it was overwriting whatever came in from the REST layer with generated values.  Ideally, I would have liked to completely remove the generation of Measurement Period, but start and end date are required input to the MeasureEvaluation open source component and getting rid of the generation was going to cause a lot of problems. I opted to just update the generation logic to be smarter and only generate when no input parameter with the same name was provided.
I touched a dozen or so files that were unrelated to my PR because they were causing warnings in my editor and I was obsessing about getting a clean Problems view. I also updated a half-dozen or so files' Javadoc to clean up Maven build warnings.

I wasn't sure I exactly understood the purpose of SimpleParameter:
maybe StringBackedParameter would be a better name (if I understand its usage properly).

Yeah, not the best name choice. I will use your suggestion.


Increment version for avs releases

Increment package version after release of Azure.ResourceManager.Avs

API change check
API changes are not detected in this pull request.


hosts file of linking container is not updated if linked container is re-created with same name

Lets assume the following situation: You have a haproxy container as a frontend that is linked to some backend application containers, serving the apps. If one RESTARTS an application container, it will get a new IP address and this address is automatically updated in the hosts file of the linking (haproxy) container. So far so good!
My problem is that if I have a new application version to deploy, I do a rm -f of the running application container and re-run the container with the same name but a possibly newer version of the image. In this case, the hosts file of the linking (haproxy) container does NOT get updated.
From my point of view, this should be the case and would not cause any trouble: it is not possible to have several containers with the same name, even stopped or running, so one should consider a re-creation of a container with a name that is "linked" into another container as just the same as re-starting the container without a deletion. Thus, the hosts file of the linking container(s) should be updated as well.
Tested with docker version 1.4.1 and boot2docker on Mac

Would be good to have it working the same way in both situations.

:+1:  It' would simplify a lot composition.

That's not that simple, as Docker daemon setup parent-child relationship when --link is created, so as you are deleting a child, the parent is totally unknown of that. See https://github.com/docker/docker/issues/2733
I suggest you to solve that problem by using fig (or other outside tools) according to the issue above.

Closing since this is mitigated by the new services API.
Basically you do something like docker run -d --publish-service <name>, and the name is published to the network (via dns, with a bridge network using /etc/hosts). When you create a new container publishing the same name, this is pushed out to all other containers.
This functionality can be seen as replacing --links.

@cpuguy83 which version of the docker will have this feature?
Thanks.

@vanga: it's in the experimental branch since 1.7 was released.


Adds costs to the objective function.

It refactors code, to make sure rating settlements is after we know which settlements simulate ok.
Estimates gas for each settlement, and uses that estimation for a more accurate objective value.

I've left some comments in the code that need answering.
Not sure what I could do to test it?

Regarding naming, since a settlement is not actually rated until we pass the gas_price in the call to objective_value, I suggest instead either pass the gas_price to RatedSettlement, or change the name RatedSettlement->SimulatedSettlement. Let me know if you like this idea, and which one.


Game Interaction

This might be worth playing around with: https://docs.pycord.dev/en/stable/api/ui_kit.html#discord.ui.Modal


The file of the Latest version detected as Virus by Chrome browser.

Hi there. I tried to download the latest file via chrome, but it was detected with virus.. Can you help me how to successfully download the file?. Sorry, I am not really a techy person..

after download complete you receive a message in the bottom of chrome that the file contain a virus
just click the three dots in chrome at the top right and select downloads you will see the file with option to keep

This is not really a virus. Compiling with pyinstaller to make exe always detects as virus. You can safely ignore that. However if you still have doubts or can't download for some reason, you can run from source code directly. To do so you just need to install python 3 and git on your machine (follow any youtube tutorial) then https://github.com/MShawon/YouTube-Viewer#installation follow these 3 commands to setup requirements. And use this command to run this script https://github.com/MShawon/YouTube-Viewer#usage
But as egbrave mentioned you should find a keep option in chrome when you see the virus detected message.

I see. Thank you so much for responding my question @egbrave and, for giving enlightenment and some info @MShawon. ;-)


Vector radial search blog

Describe the blog post your would like to write
This blog post will cover the concept and use cases of vector radial search using OpenSearch.
What is the title of the blog post?
Vector Radial Search in OpenSearch
Who are the authors?
@junqiu-lei @vamshin @dylan-tong-aws
What is the proposed posting date?
6/10/2024

#2994


allow_population_by_field_name = True should be added to more generated types for better tooling (e.g. mypy) support

Describe the bug
The following python file is reported as an error when using additional python static checking such as mypy. This also prevents IDE autocomplete from working for some combination of Python support:
# test.py
from uuid import uuid4
from trestle.oscal.common import InventoryItem

item = InventoryItem(
        uuid=str(uuid4()),
        description="an item",
        props=[],
        links=[],
        responsible_parties=[],
        implemented_components=[],
    )

❯❯❯ mypy test.py
test.py:4: error: Unexpected keyword argument "responsible_parties" for "InventoryItem"; did you mean "responsible-parties"?  [call-arg]
test.py:4: error: Unexpected keyword argument "implemented_components" for "InventoryItem"; did you mean "implemented-components"?  [call-arg]
Found 2 errors in 1 file (checked 1 source file)

This is likely because allow_population_by_field_name = True is not set in the config of all generated types that have aliases that include -.
To Reproduce

Install compliance-trestle
Install mypy
Run mypy on a file with the above contents.

Expected behavior
Mypy should not report an error.
Screenshots / Logs.
If applicable, add screenshots to help explain your problem.
Workaround
The error can be ignored in configuration or with line comments:   # type: ignore[call-arg]
Environment

OS: [e.g. iOS]
Python version:
Installed packages: mypy 1.7.1 (compiled: yes)

This seems to work for me?
=====
(venv.develop) degenaro:trestle.develop$ mypy /home/degenaro/git/A/python/test.py
Success: no issues found in 1 source file
(venv.develop) degenaro:trestle.develop$ mypy -V
mypy 1.9.0 (compiled: yes)
(venv.develop) degenaro:trestle.develop$ trestle version
Trestle version v2.6.1 based on OSCAL version 1.0.4
(venv.develop) degenaro:trestle.develop$ cat /home/degenaro/git/A/python/test.py
# test.py
from uuid import uuid4
from trestle.oscal.common import InventoryItem

item = InventoryItem(
        uuid=str(uuid4()),
        description="an item",
        props=[],
        links=[],
        responsible_parties=[],
        implemented_components=[],
    )

@degenaro Are you perhaps running this from a location where this mypy config block would get picked up that appears to just ignore this error?

Not familiar with mypy. I tried --verbose for more information. Everything seems nominal. Result is success.
(venv.develop) degenaro:trestle.develop$ mypy /home/degenaro/git/A/python/test.py --verbose

LOG:  Mypy Version:           1.9.0
LOG:  Config File:            setup.cfg
LOG:  Configured Executable:  /home/degenaro/venv.develop/bin/python
LOG:  Current Executable:     /home/degenaro/venv.develop/bin/python
LOG:  Cache Dir:              .mypy_cache
LOG:  Compiled:               True
LOG:  Exclude:                []
LOG:  Found source:           BuildSource(path='/home/degenaro/git/A/python/test.py', module='test', has_text=False, base_dir='/home/degenaro/git/A/python', followed=False)
LOG:  Metadata fresh for test: file /home/degenaro/git/A/python/test.py
LOG:  Metadata fresh for trestle.oscal.common: file /home/degenaro/git/trestle.develop/trestle/oscal/common.py
LOG:  Metadata fresh for uuid: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/uuid.pyi
LOG:  Metadata fresh for builtins: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/builtins.pyi
LOG:  Metadata fresh for trestle.oscal: file /home/degenaro/git/trestle.develop/trestle/oscal/__init__.py
LOG:  Metadata fresh for trestle: file /home/degenaro/git/trestle.develop/trestle/__init__.py
LOG:  Metadata fresh for trestle.core.base_model: file /home/degenaro/git/trestle.develop/trestle/core/base_model.py
LOG:  Metadata fresh for __future__: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/__future__.pyi
LOG:  Metadata fresh for re: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/re.pyi
LOG:  Metadata fresh for datetime: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/datetime.pyi
LOG:  Metadata fresh for enum: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/enum.pyi
LOG:  Metadata fresh for typing: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/typing.pyi
LOG:  Metadata fresh for pydantic: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/__init__.py
LOG:  Metadata fresh for sys: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/sys/__init__.pyi
LOG:  Metadata fresh for _typeshed: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_typeshed/__init__.pyi
LOG:  Metadata fresh for typing_extensions: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/typing_extensions.pyi
LOG:  Metadata fresh for collections.abc: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/collections/abc.pyi
LOG:  Metadata fresh for _ast: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_ast.pyi
LOG:  Metadata fresh for types: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/types.pyi
LOG:  Metadata fresh for _collections_abc: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_collections_abc.pyi
LOG:  Metadata fresh for io: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/io.pyi
LOG:  Metadata fresh for trestle.core: file /home/degenaro/git/trestle.develop/trestle/core/__init__.py
LOG:  Metadata fresh for trestle.core.models.file_content_type: file /home/degenaro/git/trestle.develop/trestle/core/models/file_content_type.py
LOG:  Metadata fresh for trestle.common.const: file /home/degenaro/git/trestle.develop/trestle/common/const.py
LOG:  Metadata fresh for trestle.common.err: file /home/degenaro/git/trestle.develop/trestle/common/err.py
LOG:  Metadata fresh for trestle.common.str_utils: file /home/degenaro/git/trestle.develop/trestle/common/str_utils.py
LOG:  Metadata fresh for trestle.common.type_utils: file /home/degenaro/git/trestle.develop/trestle/common/type_utils.py
LOG:  Metadata fresh for trestle.core.trestle_base_model: file /home/degenaro/git/trestle.develop/trestle/core/trestle_base_model.py
LOG:  Metadata fresh for pydantic.fields: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/fields.py
LOG:  Metadata fresh for pydantic.parse: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/parse.py
LOG:  Metadata fresh for ruamel.yaml: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/__init__.py
LOG:  Metadata fresh for trestle.common: file /home/degenaro/git/trestle.develop/trestle/common/__init__.py
LOG:  Metadata fresh for logging: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/logging/__init__.pyi
LOG:  Metadata fresh for pathlib: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/pathlib.pyi
LOG:  Metadata fresh for orjson: file /home/degenaro/venv.develop/lib/python3.10/site-packages/orjson/__init__.pyi
LOG:  Metadata fresh for sre_compile: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/sre_compile.pyi
LOG:  Metadata fresh for sre_constants: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/sre_constants.pyi
LOG:  Metadata fresh for abc: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/abc.pyi
LOG:  Metadata fresh for time: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/time.pyi
LOG:  Metadata fresh for collections: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/collections/__init__.pyi
LOG:  Metadata fresh for contextlib: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/contextlib.pyi
LOG:  Metadata fresh for pydantic.dataclasses: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/dataclasses.py
LOG:  Metadata fresh for pydantic.annotated_types: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/annotated_types.py
LOG:  Metadata fresh for pydantic.class_validators: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/class_validators.py
LOG:  Metadata fresh for pydantic.config: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/config.py
LOG:  Metadata fresh for pydantic.decorator: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/decorator.py
LOG:  Metadata fresh for pydantic.env_settings: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/env_settings.py
LOG:  Metadata fresh for pydantic.error_wrappers: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/error_wrappers.py
LOG:  Metadata fresh for pydantic.errors: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/errors.py
LOG:  Metadata fresh for pydantic.main: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/main.py
LOG:  Metadata fresh for pydantic.networks: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/networks.py
LOG:  Metadata fresh for pydantic.tools: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/tools.py
LOG:  Metadata fresh for pydantic.types: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/types.py
LOG:  Metadata fresh for pydantic.version: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/version.py
LOG:  Metadata fresh for importlib.abc: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/abc.pyi
LOG:  Metadata fresh for importlib.machinery: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/machinery.pyi
LOG:  Metadata fresh for dataclasses: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/dataclasses.pyi
LOG:  Metadata fresh for os: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/os/__init__.pyi
LOG:  Metadata fresh for codecs: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/codecs.pyi
LOG:  Metadata fresh for trestle.core.models: file /home/degenaro/git/trestle.develop/trestle/core/models/__init__.py
LOG:  Metadata fresh for string: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/string.pyi
LOG:  Metadata fresh for trestle.core.commands.common.return_codes: file /home/degenaro/git/trestle.develop/trestle/core/commands/common/return_codes.py
LOG:  Metadata fresh for trestle.common.log: file /home/degenaro/git/trestle.develop/trestle/common/log.py
LOG:  Metadata fresh for pydantic.typing: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/typing.py
LOG:  Metadata fresh for pydantic.utils: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/utils.py
LOG:  Metadata fresh for pydantic.validators: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/validators.py
LOG:  Metadata fresh for pydantic.schema: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/schema.py
LOG:  Metadata fresh for copy: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/copy.pyi
LOG:  Metadata fresh for json: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/json/__init__.pyi
LOG:  Metadata fresh for pickle: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/pickle.pyi
LOG:  Metadata fresh for ruamel: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel
LOG:  Metadata fresh for ruamel.yaml.cyaml: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/cyaml.py
LOG:  Metadata fresh for ruamel.yaml.main: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/main.py
LOG:  Metadata fresh for threading: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/threading.pyi
LOG:  Metadata fresh for sre_parse: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/sre_parse.pyi
LOG:  Metadata fresh for functools: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/functools.pyi
LOG:  Metadata fresh for warnings: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/warnings.pyi
LOG:  Metadata fresh for itertools: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/itertools.pyi
LOG:  Metadata fresh for inspect: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/inspect.pyi
LOG:  Metadata fresh for pydantic.json: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/json.py
LOG:  Metadata fresh for decimal: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/decimal.pyi
LOG:  Metadata fresh for ipaddress: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/ipaddress.pyi
LOG:  Metadata fresh for email_validator: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/__init__.py
LOG:  Metadata fresh for pydantic.datetime_parse: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/datetime_parse.py
LOG:  Metadata fresh for math: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/math.pyi
LOG:  Metadata fresh for weakref: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/weakref.pyi
LOG:  Metadata fresh for importlib: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/__init__.pyi
LOG:  Metadata fresh for importlib._abc: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/_abc.pyi
LOG:  Metadata fresh for importlib.metadata: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/metadata/__init__.pyi
LOG:  Metadata fresh for os.path: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/os/path.pyi
LOG:  Metadata fresh for subprocess: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/subprocess.pyi
LOG:  Metadata fresh for resource: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/resource.pyi
LOG:  Metadata fresh for _codecs: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_codecs.pyi
LOG:  Metadata fresh for trestle.core.commands.common: file /home/degenaro/git/trestle.develop/trestle/core/commands/common/__init__.py
LOG:  Metadata fresh for trestle.core.commands: file /home/degenaro/git/trestle.develop/trestle/core/commands/__init__.py
LOG:  Metadata fresh for argparse: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/argparse.pyi
LOG:  Metadata fresh for keyword: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/keyword.pyi
LOG:  Metadata fresh for json.decoder: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/json/decoder.pyi
LOG:  Metadata fresh for json.encoder: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/json/encoder.pyi
LOG:  Metadata fresh for ruamel.yaml.constructor: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/constructor.py
LOG:  Metadata fresh for ruamel.yaml.representer: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/representer.py
LOG:  Metadata fresh for ruamel.yaml.resolver: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/resolver.py
LOG:  Metadata fresh for ruamel.yaml.compat: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/compat.py
LOG:  Metadata fresh for ruamel.yaml.error: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/error.py
LOG:  Metadata fresh for ruamel.yaml.tokens: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/tokens.py
LOG:  Metadata fresh for ruamel.yaml.events: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/events.py
LOG:  Metadata fresh for ruamel.yaml.nodes: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/nodes.py
LOG:  Metadata fresh for ruamel.yaml.loader: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/loader.py
LOG:  Metadata fresh for ruamel.yaml.dumper: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/dumper.py
LOG:  Metadata fresh for ruamel.yaml.comments: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/comments.py
LOG:  Metadata fresh for ruamel.yaml.docinfo: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/docinfo.py
LOG:  Metadata fresh for glob: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/glob.pyi
LOG:  Metadata fresh for _thread: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_thread.pyi
LOG:  Metadata fresh for _warnings: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_warnings.pyi
LOG:  Metadata fresh for dis: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/dis.pyi
LOG:  Metadata fresh for pydantic.color: file /home/degenaro/venv.develop/lib/python3.10/site-packages/pydantic/color.py
LOG:  Metadata fresh for _decimal: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_decimal.pyi
LOG:  Metadata fresh for email_validator.exceptions_types: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/exceptions_types.py
LOG:  Metadata fresh for email_validator.validate_email: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/validate_email.py
LOG:  Metadata fresh for email_validator.version: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/version.py
LOG:  Metadata fresh for _weakref: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_weakref.pyi
LOG:  Metadata fresh for _weakrefset: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_weakrefset.pyi
LOG:  Metadata fresh for importlib.metadata._meta: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/importlib/metadata/_meta.pyi
LOG:  Metadata fresh for email.message: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/message.pyi
LOG:  Metadata fresh for posixpath: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/posixpath.pyi
LOG:  Metadata fresh for ruamel.yaml.tag: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/tag.py
LOG:  Metadata fresh for ruamel.yaml.scalarstring: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/scalarstring.py
LOG:  Metadata fresh for ruamel.yaml.scalarint: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/scalarint.py
LOG:  Metadata fresh for ruamel.yaml.scalarfloat: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/scalarfloat.py
LOG:  Metadata fresh for ruamel.yaml.scalarbool: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/scalarbool.py
LOG:  Metadata fresh for ruamel.yaml.timestamp: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/timestamp.py
LOG:  Metadata fresh for ruamel.yaml.util: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/util.py
LOG:  Metadata fresh for ruamel.yaml.serializer: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/serializer.py
LOG:  Metadata fresh for ruamel.yaml.anchor: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/anchor.py
LOG:  Metadata fresh for binascii: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/binascii.pyi
LOG:  Metadata fresh for base64: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/base64.pyi
LOG:  Metadata fresh for copyreg: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/copyreg.pyi
LOG:  Metadata fresh for traceback: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/traceback.pyi
LOG:  Metadata fresh for textwrap: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/textwrap.pyi
LOG:  Metadata fresh for ruamel.yaml.reader: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/reader.py
LOG:  Metadata fresh for ruamel.yaml.scanner: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/scanner.py
LOG:  Metadata fresh for ruamel.yaml.parser: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/parser.py
LOG:  Metadata fresh for ruamel.yaml.composer: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/composer.py
LOG:  Metadata fresh for ruamel.yaml.emitter: file /home/degenaro/venv.develop/lib/python3.10/site-packages/ruamel/yaml/emitter.py
LOG:  Metadata fresh for opcode: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/opcode.pyi
LOG:  Metadata fresh for colorsys: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/colorsys.pyi
LOG:  Metadata fresh for numbers: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/numbers.pyi
LOG:  Metadata fresh for email_validator.syntax: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/syntax.py
LOG:  Metadata fresh for email_validator.rfc_constants: file /home/degenaro/venv.develop/lib/python3.10/site-packages/email_validator/rfc_constants.py
LOG:  Metadata fresh for email: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/__init__.pyi
LOG:  Metadata fresh for email.charset: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/charset.pyi
LOG:  Metadata fresh for email.contentmanager: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/contentmanager.pyi
LOG:  Metadata fresh for email.errors: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/errors.pyi
LOG:  Metadata fresh for email.header: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/header.pyi
LOG:  Metadata fresh for email.policy: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/policy.pyi
LOG:  Metadata fresh for genericpath: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/genericpath.pyi
LOG:  Metadata fresh for unicodedata: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/unicodedata.pyi
LOG:  Metadata fresh for idna: file /home/degenaro/venv.develop/lib/python3.10/site-packages/idna/__init__.py
LOG:  Metadata fresh for email._policybase: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/email/_policybase.pyi
LOG:  Metadata fresh for idna.package_data: file /home/degenaro/venv.develop/lib/python3.10/site-packages/idna/package_data.py
LOG:  Metadata fresh for idna.core: file /home/degenaro/venv.develop/lib/python3.10/site-packages/idna/core.py
LOG:  Metadata fresh for idna.intranges: file /home/degenaro/venv.develop/lib/python3.10/site-packages/idna/intranges.py
LOG:  Metadata fresh for idna.idnadata: file /home/degenaro/venv.develop/lib/python3.10/site-packages/idna/idnadata.py
LOG:  Metadata fresh for bisect: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/bisect.pyi
LOG:  Metadata fresh for _bisect: file /home/degenaro/venv.develop/lib/python3.10/site-packages/mypy/typeshed/stdlib/_bisect.pyi
LOG:  Loaded graph with 165 nodes (0.050 sec)
LOG:  Found 100 SCCs; largest has 42 nodes
LOG:  100 fresh SCCs (165 nodes) left in queue (and will remain unprocessed)
LOG:  Build finished in 0.054 seconds with 0 modules, and 0 errors
Success: no issues found in 1 source file

But wait...
(venv.develop) degenaro:trestle.develop$ mypy -c /home/degenaro/git/A/python/test.py --verbose

LOG:  Mypy Version:           1.9.0
LOG:  Config File:            setup.cfg
LOG:  Configured Executable:  /home/degenaro/venv.develop/bin/python
LOG:  Current Executable:     /home/degenaro/venv.develop/bin/python
LOG:  Cache Dir:              .mypy_cache
LOG:  Compiled:               True
LOG:  Exclude:                []
LOG:  Found source:           BuildSource(path=None, module='__main__', has_text=True, base_dir=None, followed=False)
LOG:  Metadata not found for __main__
LOG:  Parsing <string> (__main__)
LOG:  Bailing due to parse errors
LOG:  Build finished in 0.002 seconds with 0 modules, and 1 errors
<string>:1: error: invalid syntax  [syntax]
Found 1 error in 1 file (errors prevented further checking)

I'm happy to have a virtual meeting to discuss, if you like. Perhaps you can help me to reproduce?

LOG:  Config File:            setup.cfg

This output confirms that mypy is reading configuration from the setup.cfg.  This method of configuration is not specific to mypy, for example, flake8 settings are also configured there.
To reproduce the error in this issue:

Run the test in a different different directory so that mypy does not read configuration from a setup.cfg or
Comment out the [mypy] configuration sections in the setup.cfg file.

The good news is that I'm able to recreate now:
/home/degenaro/git/A/python/test.py:7: error: Unexpected keyword argument "responsible_parties" for "InventoryItem"; did you mean "responsible-parties"?  [call-arg]
/home/degenaro/git/A/python/test.py:7: error: Unexpected keyword argument "implemented_components" for "InventoryItem"; did you mean "implemented-components"?  [call-arg]

The bad news is that adding allow_population_by_field_name = True does not seem tho help. I must be doing something wrong...

class InventoryItem(OscalBaseModel):
    """
    A single managed inventory item within the system.
    """

    class Config:
        extra = Extra.forbid
        allow_population_by_field_name = True

    uuid: constr(
        regex=r'^[0-9A-Fa-f]{8}-[0-9A-Fa-f]{4}-[45][0-9A-Fa-f]{3}-[89ABab][0-9A-Fa-f]{3}-[0-9A-Fa-f]{12}$'
    ) = Field(
        ...,
        description=
        'A machine-oriented, globally unique identifier with cross-instance scope that can be used to reference this inventory item elsewhere in this or other OSCAL instances. The locally defined UUID of the inventory item can be used to reference the data item locally or globally (e.g., in an imported OSCAL instance). This UUID should be assigned per-subject, which means it should be consistently used to identify the same subject across revisions of the document.',
        title='Inventory Item Universally Unique Identifier',
    )
    description: str = Field(
        ...,
        description='A summary of the inventory item stating its purpose within the system.',
        title='Inventory Item Description'
    )
    props: Optional[List[Property]] = Field(None)
    links: Optional[List[Link]] = Field(None)
    responsible_parties: Optional[List[ResponsibleParty]] = Field(None, alias='responsible-parties')
    implemented_components: Optional[List[ImplementedComponent]] = Field(None, alias='implemented-components')
    remarks: Optional[str] = None

Here is a hacked version of the test.py.
# test.py
from uuid import uuid4
from trestle.oscal.common import InventoryItem, ResponsibleParty

try:

    role_id = 'x'
    party_uuids = [str(uuid4())]

    rp = ResponsibleParty(
            role_id = role_id,
            party_uuids = party_uuids,
        )

    list_rp = [rp]

    item = InventoryItem(
            uuid=str(uuid4()),
            description="an item",
            props=[],
            links=[],
            responsible_parties=list_rp,
            implemented_components=[],
        )

    print(f'{item}')

except Exception as e:
    print(e)

And here is running directly via python invocation, which runs fine it seems:
python  /home/degenaro/git/A/python/test.py
uuid='9ae72e56-97f6-44f6-b7f1-a0c9e4178413' description='an item' props=[] links=[] responsible_parties=[ResponsibleParty(role_id='x', party_uuids=['9507f340-c0d4-4061-a97d-04c73611c34a'], props=None, links=None, remarks=None)] implemented_components=[] remarks=None

This is likely because allow_population_by_field_name = True is not set in the config of all generated types that have aliases that include -.

The bad news is that adding allow_population_by_field_name = True does not seem to help. I must be doing something wrong...

I think that was the only difference between InventoryItem and a model that was working with hyphens, but it's been 3 months so I don't remember what the other one I was looking at was.
There is a workardound  # type: ignore[call-arg], so this might not be worth looking at more until after pydantic v2 #1417 is implemented, WDYT?

OK. I'm hopeful that #1533 will be merged into develop and a release created in the very near future. Can look at #1417 after that.

I can be pretty thick. I install compliance-trestle.
(venv.develop) degenaro:trestle.develop$ trestle version
Trestle version v3.1.0 based on OSCAL version 1.1.2

I add a new test case (see below).
tests/trestle/core/models/models_test.py
# -*- mode:python; coding:utf-8 -*-

# Copyright (c) 2020 IBM Corp. All rights reserved.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
#     https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
"""Tests for trestle create path actions class."""

from uuid import uuid4
from trestle.oscal.common import InventoryItem, ResponsibleParty

def test_create_inventory_item():
    """Test create inventory item."""

    role_id = 'role_id'
    party_uuids = [str(uuid4())]

    rp = ResponsibleParty(
            role_id=role_id,
            party_uuids=party_uuids,
        )

    item = InventoryItem(
        uuid=str(uuid4()),
        description="an item",
        props=[],
        links=[],
        responsible_parties=[rp],
        implemented_components=[],
    )
    assert(item)
    assert(len(item.responsible_parties) == 1)
    assert(item.responsible_parties[0].role_id == role_id)
    item.responsible_parties = []
    assert(len(item.responsible_parties) == 0)

I run make test-all. No errors/failures. Thus, test works, showing that setting  responsible_parties using the field name works, yes?

I run make test-all. No errors/failures. Thus, test works, showing that setting responsible_parties using the field name works, yes?

That issue is not that it works, the issue is that mypy, a more complete type checker, outside of the trestle source tree/some specific venv, fails:
$ virtualenv venv
$ source venv/bin/activate
$ pip install compliance-trestle
$ pip install mypy
$ mypy test.py

est.py:10: error: Unexpected keyword argument "role_id" for "ResponsibleParty"; did you mean "role-id"?  [call-arg]
test.py:10: error: Unexpected keyword argument "party_uuids" for "ResponsibleParty"; did you mean "party-uuids"?  [call-arg]
test.py:18: error: Unexpected keyword argument "responsible_parties" for "InventoryItem"; did you mean "responsible-parties"?  [call-arg]
test.py:18: error: Unexpected keyword argument "implemented_components" for "InventoryItem"; did you mean "implemented-components"?  [call-arg]
Found 4 errors in 1 file (checked 1 source file)

(venv.x) degenaro:venv.x$ mypy /home/degenaro/git/test/test.py
/home/degenaro/git/test/test.py:11: error: Unexpected keyword argument "role_id" for "ResponsibleParty"; did you mean "role-id"?  [call-arg]
/home/degenaro/git/test/test.py:11: error: Unexpected keyword argument "party_uuids" for "ResponsibleParty"; did you mean "party-uuids"?  [call-arg]
/home/degenaro/git/test/test.py:19: error: Unexpected keyword argument "responsible_parties" for "InventoryItem"; did you mean "responsible-parties"?  [call-arg]
/home/degenaro/git/test/test.py:19: error: Unexpected keyword argument "implemented_components" for "InventoryItem"; did you mean "implemented-components"?  [call-arg]
Found 4 errors in 1 file (checked 1 source file)
(venv.x) degenaro:venv.x$ mypy --config-file /home/degenaro/git/trestle.develop/mypy.cfg /home/degenaro/git/test/test.py
Success: no issues found in 1 source file
(venv.x) degenaro:venv.x$ cat /home/degenaro/git/trestle.develop/mypy.cfg

[mypy]
plugins = pydantic.v1.mypy

Currently in trestle root folder setup.cfg we have:
[mypy]
plugins = pydantic.mypy

Since we are using pydantic.v1, this should be changed to:
[mypy]
plugins = pydantic.v1.mypy

Fantastic! That resolves it, thanks.


Implementing save/load

I thought I had saving and loading the state of the ink figured out, but it's only working if I haven't made any choices yet. My game uses multiple ink story jsons, and If I try loading while the same ink story is in the runner, the passage text displays the very first passage in the story (incorrect, it should display the loaded passage), displays the correct choices for the loaded passage, and continues from that point.
If I load from a different story (load a state from json B while json A is currently playing), it displays the correct choices but the passage text is blank and clicking just makes the choices vanish.
Here's my code:
func save_game():
    var save_game = File.new()
    var dir = Directory.new()
    dir.remove("user://savegame.save")
    save_game.open("user://savegame.save", File.WRITE)
    save_game.store_line(inkRunner.myStory) # current loaded ink json reference
    save_game.store_line(inkRunner.saveState()) # function to save the story state
    save_game.close()

func saveState():
    var savedJson = story.state.to_json()
    return (savedJson)

func load_game():
    var save_game = File.new()
    if not save_game.file_exists("user://savegame.save"):
        return # Error! We don't have a save to load.
    save_game.open("user://savegame.save", File.READ)
    var loadStory = save_game.get_line()
    var data = save_game.get_line()
        inkRunner.myStory = loadStory
    inkRunner.wipeChoices() # function to clear the current choice buttons
    inkRunner.on_new_story_start(loadStory)
    inkRunner.loadState(data)
    save_game.close()

func loadState(state):
    story.state.load_json(state)
    wipeChoices()
    continue_story()

# Without calling wipeChoices() the new buttons just pop up under the old ones.

func wipeChoices():
    StoryVBoxContainer.remove_child(_current_choice_container)
    if is_instance_valid(_current_choice_container):
        _current_choice_container.queue_free()

here's my continue_story():
func continue_story():
    while story.can_continue:
        var text = story.continue()
        var label = LineLabel.instance()
        label.bbcode_text = text

        StoryVBoxContainer.add_child(label)
        var scrollbar = StoryScrollContainer.get_v_scrollbar()

        scrollbar.max_value += 1000
        StoryScrollContainer.scroll_vertical = scrollbar.max_value

        if story.current_tags.size() > 0:
            check_tags()

    if story.current_choices.size() > 0:

        _current_choice_container = ChoiceContainer.instance()
        StoryMarginContainer.add_child(_current_choice_container)

        _current_choice_container.create_choices(story.current_choices)
        _current_choice_container.connect("choice_selected", self, "_choice_selected")

@mcoorlim it's a bit tricky to know what's going on without being able to fiddle with the project.
Can you show me the code for on_new_story_start()? Does it just replace inkRunner.story?

If I load from a different story (load a state from json B while json A is currently playing), it displays the correct choices but the passage text is blank and clicking just makes the choices vanish.

ink tries to be as tolerant as possible when loading incompatible states, but if you use a state save from another story, you're likely to meet undefined behaviours.

ink tries to be as tolerant as possible when loading incompatible states, but if you use a state save from another story, you're likely to meet undefined behaviours.

on_new_story_start() exists to load in the new ink file.
func on_new_story_start(inkToLoad):
	match chapter:
		1:
			myStory = chapter1Story
			_load_story(inkToLoad)
			_bind_externals_1()
	continue_story()

'chapter' here is a variable set to the current story... which I don't believe I store when I save!
Fixing that solves the problem where loading from a different file breaks the game, but I still have the issue where upon loading I'm given the first ink passage in the file. I'm given the loaded choice buttons, though, and after I click a choice the game proceeds correctly.

The last line in on_new_story_start() is probably why you get the first passage printed upon loading the new story. It's called before inkRunner.loadState(data), so the story starts from scratch.
As for displaying the right passage before hitting the choices, do you export the state before said passage or after it was outputted by story.continue()?

I export when the player hits the save button on the godot level (which only sends a signal to run save_game())

Alright, then you need to keep track of the last passage shown on screen at any given time. I suppose you can then save it alongside the state when the user press the save button¹ and put it back on screen right before loadState(). ink doesn't backtrack, so once a line is outputted, it's gone.
¹ I noticed that you currently store both the story and the state as two different lines in your savegame. Saving the last passage may break your logic, as lines returned by story.continue() usually (but not always) end with newline characters.

Hm. Is there a way I can save the children of the VBoxContainer where I'm keeping all my instanced story passages, and then reload them? These are the actual label nodes, and preserving them would enable the player to read back and see where in the story they're at. (I'm not entirely sure how to write them to file, then read them back in where they're supposed to go)

I was able to save and re-import those labels using this tutorial: https://docs.godotengine.org/en/stable/tutorials/io/saving_games.html
It's all working fine now. Thanks so much for the continued assistance!

No worries, happy to help!


DSL problems

It does not appear to be easy to have en enum, which encodes certain strings:
enum Bah:
  case valid
  case values
  case wait

values & wait will give compile errors.
The DSL, is incomplete, as these are commented out in a few places. To the best of my knowledge, they Arne't "crucial" and will therefore likely be left this way.

I think this works much better now


"Chips" selection bug

Component List -> Chips: open the "chip" and while keeping the mouse over the strings in each element try to select the row: fail most of the times, with some flickering of the background while you move the mouse up and down the list; no problem selecting each element while clicking to the right of the strings
browser: Firefox 37.0.2 on Linux Mint 17.1 Rebecca

Hi @emil-perhinschi,
We fixed the bug, check it on the website at Components -> Chips
Thank you for the feedback.

This is still reproducible, have a look on the following screenshot:

Resolved: added background-color for class .e-chip .open on li hover (file: chips.less)


folder needs to exist for sqlitefile to be created

Link to reproduction
No response
Environment Info
Windows,
NPM
Describe the Bug
When running npx create-payload-app@beta and passing a path to the .db-file that contains a subfolder, the subfolder needs to exist for payload to create the file on init.
Reproduction Steps
Run npx create-payload-app@beta
Select SQLite as the database.
Pass ./db/dbfile.db as the path fo the file.
Opening localhost:3000/admin will crash as there is no connection to the db possible as the file does not exist.
Adapters and Plugins
No response

We're simply relying on how the underlying package for SQLite works and it doesn't create a folder automatically, therefore it's not a bug with Payload.
However, it may be a useful feature to have in the future, I'm converting this to a discussion.


KAFKA-6054: Fix upgrade path from Kafka Streams v0.10.0

\cc @bbejeck @vvcephei
This is a port of #4746 for 0.10.2 branch plus one more commit to extend the system test accordingly. Will to more PRs for all other branches similar to this one. Please comment on #4746 first, and I'll address those comments on all PRs. The existing comments on $4746 are already included in this PR.

Upgrade system test passed: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1563/
Triggered all Streams system tests here: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1564/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3786/
Test FAILed (JDK 7 and Scala 2.10).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3787/
Test FAILed (JDK 7 and Scala 2.10).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3788/
Test FAILed (JDK 7 and Scala 2.10).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3789/
Test FAILed (JDK 7 and Scala 2.10).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3790/
Test FAILed (JDK 7 and Scala 2.10).

Note: Java 9 does not work on old 0.10.2 branch -- Java9 was set up later and we can ignore failing Java9 builds.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3791/
Test PASSed (JDK 7 and Scala 2.10).

Updated this with 0.10.1 comments and follow ups.
System tests passed: https://jenkins.confluent.io/job/system-test-kafka-branch-builder/1589/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3792/
Test PASSed (JDK 7 and Scala 2.10).

Retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3793/
Test PASSed (JDK 7 and Scala 2.10).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.10/3794/
Test PASSed (JDK 7 and Scala 2.10).

Merging this to 0.10.2 now.

Merged to 0.10.2.
Follow up PR to address missed comments: #4778


Autocompletion not working if the keyboard is undock

Hi,
Thank you for your API.
I've just notice something weird, the autocompletion stop working if I undock the keyboard.
If I redock the keyboard the autocompletion works again.
Any idea?
Cheers
Alain

+1 here...this is a serious issues i thing.


[Bug]: cannot run after updating 1.314-1.316

What happened?
A bug happened!
cannot run after updating. no matter 1.314, 1.315, 1.316.
I use 1.312 now. Manual update to 1.313 can run. But 1.314 can't run.

Player.log
Player-prev.log
if the data.db is required, I can send it.
Platform
None

<EMAIL_ADDRESS>your data.db file.

<EMAIL_ADDRESS>your data.db file.

already sent it. thanks.


Is this method can be transferred to general LLM?

I notice that your work only focus on code LLM, I wanna to use your method in general LLM to fix some factual error in model's response. Sincerely ask you for advice.

I think the key is to accurately classify and locate the factual errors and give LLM feedback. For code LLM, it is easy to do with compiler. Hope this help. : )

Thank you so much ! We're trying to solve this point, it's hopeful to realize. But I also have a question: If the location is not clear (natural language in reality is non-linear), but you know what information is wrong, is there a recommended solution?

BTW, what exactly does "the amplitude fluctuation in fine-grained feedback caused by variable values of S and E" mean in the paper, Is $L_{adaptive}$introduced to alleviate this problem?

Thank you so much ! We're trying to solve this point, it's hopeful to realize. But I also have a question: If the location is not clear (natural language in reality is non-linear), but you know what information is wrong, is there a recommended solution?

If you are not sure where the location of wrong information is, you can try to use coarse-grained feedback only.

Thank you so much !


Support H2 history collector

H2 seems to only support a single connection by default. Setting MVCC=TRUE might enable support for multiple connections.


client.getChainSpecData doesn't give the same SS58prefix as the constant System.SS58prefix on Paseo

FWIW Paseo was 42, and is now 0 which is probably the reason, so this is expected. I guess this 42 is in the genesis chain spec, and it's been later changed in a runtime upgrage.
client.getChainSpecData().then(({ properties}) => console.log(properties.ss58Format))
It's not a bug per se.. and the name getChainSpecData is good to understand the issue. Now I expect devs to use this, like me, to get started and show the right decimal, token, prefix, and they may not know that Paseo changed, or that the current state isn't the same as what was in the genesis chain spec. Paseo is isolated today, but some other network in the future will change, as we expect them to all use 0 eventually on Polkadot for instance.
Let me know what's your suggestion. I'd consider using another function like getChainProperties, and use the latest runtime constants. In the mean time I'll ignore this property and use the system.Ss58Prefix.

The chainspec data is "trusted data", it's completely arbitrary data.
The System.SS58prefix is what matters, because it's what it's in the runtime of the chain. You can use a light-client and verify that value.
If you are getting discrepancies, that's probably because whoever setup the node messed up the chainspec properties.  Please reach out to them. This is not an issue with polkadot-api.
Also, I have explained over and over, in many occasions why the getChainSpecData should not be used by normal DApp developers. It's mostly for dev-tools and doing introspection. Do not ever create a DApp that relies on getChainSpecData.

Having a config file in every single app out there, that everyone will have to create/update is certainly not great. Having a list of rpc/relay for light client, and fetching everything upon connection sounds so much better. The decimals & tokens, should absolutely be on chain IMHO. Maybe this is something @kianenigma can help me with to write a Polkadot sdk issue, and get tht in the wishlist.
For now think this is something that we need to have in the docs, it it won't prevent every mistake, it's a start. If I found getChainSpecData, others will find it. and the mistake will be made again.

For now, I think this is something that we need to have in the docs. It won't prevent every mistake, but it's a start. If I found getChainSpecData, others will find it, and the mistake will be made again.

We are planning significant improvements to the documentation, and I will ensure this issue is explained more thoroughly. I had assumed that DApp developers understood that the 'properties' entry in the chainspec is "trusted data" and shouldn't be relied upon. Since that might not be the case, I'll make sure we emphasize this point clearly in the updated docs.

The issue of moving properties on-chain is a recurring topic. For instance, refer to this conversation that took place during the review of RFC-8.
Wouldn't it be beneficial if we had a standard way to access this information trustlessly?
Absolutely - it would be ideal.
Do we currently have a standard that enables this?
Unfortunately, we do not.
While we indirectly have a pseudo-standard for accessing the SS58-prefix through RFC-78, there are teams within the "Polkadot UX Guild" advocating for ignoring the on-chain value of their own chains 🙃🤦.
Is anyone likely to champion and enforce such a standard?
It's highly unlikely. The ecosystem currently resembles a "wild west," where incentives are not aligned to promote standards—in fact, they often do the opposite. This isn't just my perspective; you might reach out to the Web3 Foundation, which hasn't yet completed the Polkadot specification, to ask why they're not actively championing these standards.
So what can we do in the meantime?
Given the current situation and the unlikelihood of having this information standardized on-chain soon, the best advice for dApp developers is to maintain their own configuration files for each network. Alternatively, setting up a centralized GitHub repository to store these configurations is a possibility. Personally, I find this solution less than ideal and somewhat unsettling, so I prefer not to partake in it.
For context, if RFC-8 were ever implemented, I'm fairly confident it would address this problem and establish a de facto standard, much like how FRAME has set standards in other areas.
Is there any chance RFC-8 will be implemented?
Who knows? Probably not, though. Despite being one of the first RFCs approved, to my knowledge, there have been zero efforts toward its implementation so far.
I had hoped my team could eventually tackle this issue. However, we're currently overwhelmed with work and would require extensive coordination with Parity to proceed. Unfortunately, this means it's unlikely to happen anytime soon.

I'll make sure we emphasize this point clearly in the updated docs.

Thank you! I used to know what's a chain spec, and I forgot. I talked about "genesis" above which is totally different, and as you said: non-trusted, unlike the chain spec that contains the genesis. The amount of Dapp devs that know what a chain spec file is, is probably very very low since it's linked to nodes, that Dapp devs generally don't mess with.
I came across this yesterday as an example, it's a papi step by step tutorial by dotcodeschool.com that just got release. I'll ping Nikos to change this. Dapp devs should ideally not be told about this function at all.

Thnx @Tbaut for the information.
I would prefer to add a note that I am using that for the sake of the tutorial and that normally in production developers should NOT rely on that due to the things that Josep mentioned.
I will update accordingly
@josepot if you think it should be removed or something specific to be added - please let me know 🙏🏽


Potential issue in the GNN demonstrator example with tensorflow backend

During the review process of the library's paper, a reviewer pointed out that the following error occurs in their local system with TensorFlow 3.9.2 and Python 3.10.6.
TypeError: Sequential.call() got multiple values for argument 'training'

This occurs when running the code of the APPNP example. The issue lies fully with the example and not with any additional library functionality - it will not motivate a hotfix.
Investigate whether this issue is unique to the version of TensorFlow or whether the latter has yet again updated something that will break the example in all future versions. At the very least, this error should not occur in github actions.
If this is not the case, investigate whether this issue is platform-dependent.

Tensorflow interface inconsistencies have been patched in examples.


round line-height value from computed float value

In IE11, when the actual line height is 22.88px, it turns out that element's clientHeight returns 23, not 22. getLineHeight function returns 22 as a result of parseInt. This causes the condition in https://github.com/CezaryDanielNowak/React-dotdotdot/blob/98875e7206470dcfb862839d47a01ccdb4617656/src/clamp.js#L230 to fail and the element gets truncated until it's empty.
How to reproduce:
https://jsbin.com/nijapexemu/edit?js,output

Thanks!


Re-introduce test framework logging flags.

Cleanup the settings/logging code.
Refactor Istio logging code to allow injecting of logging lambdas.
Wire-up the log options to test-framework flags.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
192ac22c8e0df6b00056214840b9131c16773e18
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
5576839c02dd89f5810c580d40310c9479e5aeb2
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [geeknoid,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test e2e-simple

/lgtm
/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, nmittler
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [geeknoid,nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ozevren: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
30143f79bd313cbcf770c85b2437c79ba441b2f3
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Checked/Unchecked toggle icon behavior consistently generates unexpected result

Problem Description

The icons don't render 'properly' on the checkbox when 'checked':
When unchecked

When checked

import Checkbox from 'material-ui/lib/checkbox'
import ToggleIconLeft from 'material-ui/lib/svg-icons/hardware/keyboard-arrow-left'
import ToggleIconRight from 'material-ui/lib/svg-icons/hardware/keyboard-arrow-right'

...

<Checkbox
          label='Toggle LeftNav'
          checkedIcon={<ToggleIconLeft />}
          unCheckedIcon={<ToggleIconRight />}
          style={leftNavToggleStyle}
          onTouchTap={this.handleToggle} />

Versions

Material-UI: 0.14.4
React: 0.14
Browser: Chrome 48 and FF 41.0.2

I can't dig into implementation issues and do a PR right now, so going to work-around it but thought it should be flagged.

We have been porting the component on the next branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.


Conditional import of devtools based on NODE_ENV

An attempt to address https://github.com/developit/preact/issues/431 to make devtools conditional and NOT in production.

Coverage remained the same at 97.695% when pulling 6c3304764bfce33ff1031e5f702ba779a67c718c on t47io:devtool-env-prod into 00cf45f91e7cda9f80f6cf27f3fd7d28918434e2 on developit:master.

What else should I look into?

Coverage remained the same at 97.695% when pulling 514306bb7066f09604b6a8aef1c8b533c6f01425 on t47io:devtool-env-prod into 00cf45f91e7cda9f80f6cf27f3fd7d28918434e2 on developit:master.

Well, it seems good but I'm not confident enough to prove it until someone tests that it really works with webpack.

I just realized - this file is bundled via rollup, so the require() won't work.  I think instead we need to wrap the entirety of devtools/devtools.js in the process check and leave this file as a simple import + invoke.

Coverage remained the same at 100.0% when pulling aa6dabb1380e047ade3cf937638b025550a82fd7 on t47io:devtool-env-prod into 9e1dd185bb1d6505c35477d8101c886c25dc51c8 on developit:master.

Hi,
Is it probable that fix for disabling preact/devtools in production mode will be merged soon?
Thanks!

Use preact/debug instead. It has this fix implemented. @_developit closing this one?

Use preact/debug instead. It has this fix implemented. @developit closing this one?


Cannot use --enable-aspa option

In latest version today, I cannot use --enable-aspa option.
In addition, I think other options like --disable-rsync are not available now.
Please tell me how options have been changed in these days.

ASPA support has been moved behind a feature flag because it may still change. We don’t want people that never upgrade to accidentally get stuck with an outdated profile version.
To compile with ASPA support, you need to include the aspa feature when building by using the --features aspa option with cargo build or cargo install. E.g., to build from a checked out source tree:
cargo build --release --locked --features aspa

Oh, --disable-rsync does work here.

I'm sorry.
I couldn't confirm --disable-rsync accurately.

When using Routinator whose commit num is 2b450d0, Routinator could read ASPA object in krill testbed.
However, latest version Routinator couldn't.
Have you changed implementation of reading ASPA?
I use RRDP.

Yes. The ASPA specification has changed. Krill doesn’t support this new specification yet.

Thank you.
If you don't mind, please tell me the changed part of ietf-draft.

Hi,
I added a warning to the Krill documentation:
https://krill.docs.nlnetlabs.nl/en/stable/manage-aspas.html
Essentially the optional AFI limit for provider ASNs is dropped in the updated ASPA profile, and as a result, the ASN.1 structure was simplified. Because it's still very early days for ASPA adoption, the feeling (also expressed in the sidrops  IETF working group) was that it would be okay to have a breaking change.
Once Krill 0.14.0 is out (expected around September), it will support the V1 ASPA profile.

Thank you very much for teaching me and developing to support new ASPA.


No template for issue and pull request in dwn-server

The repository "developer.tbd.website" contains templates for both issue creation and pull requests. It is recommended to include these templates in this repository as well. Doing so will enhance the clarity and effectiveness of contributions made by other contributors.
Fix :-
it is easy just have to make a similar template for the contributor

would like to work on this issue!!

Can I work on this issue?


Update gemini to 2.4.3

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

I noticed that the checksum has been invalid for a few weeks now, and this updates it.
TravisCI:
audit for gemini: failed
 - only sha256 changed (see: https://github.com/caskroom/homebrew-cask/blob/master/doc/cask_language_reference/stanzas/sha256.md)
Error: audit failed for 1 cask: gemini

Evidence of SHA256 change in download package:

When running brew cask install gemini it results in an error presently and tells you that c3c2ef623bee5fc43c845ad5537cba4f3eb518d881db25db1e5a09ea69d5508e is the correct SHA at this moment in time (see diff for this PR, and it matches).
When running curl -LO 'https://dl.devmate.com/com.macpaw.site.Gemini2/Gemini2.dmg'  && shasum -a 256 Gemini2.dmg it returns with c3c2ef623bee5fc43c845ad5537cba4f3eb518d881db25db1e5a09ea69d5508e  Gemini2.dmg, which matches the SHA in my PR.
When uploading the file from point #2 to VirusTotal, c3c2ef623bee5fc43c845ad5537cba4f3eb518d881db25db1e5a09ea69d5508e is the SHA256 it reports, as seen at https://www.virustotal.com/#/file/c3c2ef623bee5fc43c845ad5537cba4f3eb518d881db25db1e5a09ea69d5508e/detection

NOTE: VirusTotal does not show the SHA256 for this download with the URL, only with the uploaded file. See: https://www.virustotal.com/#/url/48c89c57896803f1db0d73347d097e8de640e5ec029c6645cf899e8d8a758615/details
Additionally, no public statement was found from MacPaw, the publisher of Gemini, that the file has changed or any posting of checksums.

https://www.virustotal.com/#/file/c3c2ef623bee5fc43c845ad5537cba4f3eb518d881db25db1e5a09ea69d5508e/details

@cameronmalek We don’t need evidence of the file having been changed. We can see it changed. What we need is proof that the change is legitimate and not the result of a malicious actor, hence why we have the specific verification steps.


Solution 3 - Azure portal images are not current

The menu shown in the image is not what the portal displays. In particular, the "Resource providers" we are supposed to select does not appear in the portal.
Is there a step prior to step 1? Perhaps to navigate to a subscription page in the portal?

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

 Your feedback has been shared with the content owner for further review.

@mtnygard - thanks for this feedback. I have updated the images to show all the steps.

#please-close