UnixPB: Script to provide GPG signature verification for downloaded binaries

[x] commit message has one of the standard prefixes
[ ] faq.md updated if appropriate
[ ] other documentation is changed or added (if applicable)
[ ] playbook changes run through VPC or QPC (if you have access)
[ ] VPC/QPC not applicable for this PR
[ ] for inventory.yml changes, bastillion/nagios/jenkins updated accordingly

ref https://github.com/adoptium/infrastructure/issues/2233
Left to do

[x] Add the rest of the public keys to variables file
[x] Use the script in the roles which need it

Example of usage:
./package_signature_verification.sh -s path_to_sig_file (or -sl sigfile_url) -f path_to_binary (or -fl binary_url) -k public_key

I'm still undecided whether to import all of the gpg keys at the beginning of the playbook, or at each role which uses it

Not sure if the linter errors are related to this pr

The task will exit if it hits a bad signature
gpg: Signature made Tue Nov 19 19:36:42 2019 GMT
gpg:                using DSA key B02137D875D833D9B23392ECAE5A7FB608A0221C
gpg: Can't check signature: No public key

or
gpg: Signature made Tue Nov 19 19:36:41 2019 GMT
gpg:                using DSA key B02137D875D833D9B23392ECAE5A7FB608A0221C
gpg: BAD signature from "Robert Scholte<EMAIL_ADDRESS>[unknown]

While it will continue on a good signature
gpg: Signature made Tue Nov 19 19:36:42 2019 GMT
gpg:                using DSA key B02137D875D833D9B23392ECAE5A7FB608A0221C
gpg: Good signature from "Robert Scholte<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: B021 37D8 75D8 33D9 B233  92EC AE5A 7FB6 08A0 221C

vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1593/console

vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1593/console

Can you add the latest link to the initial description of this PR please, since it currently says "not applicable" :-)

vpc https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1595/console

vpc on failed platforms https://ci.adoptopenjdk.net/job/VagrantPlaybookCheck/1596/console (centos6 and solaris10)

The latest vpc passes on centos 6 and solaris 10, which were the remaining problem platforms. This can be merged

/thaw


Report does not include retry option

I use xcresulttool + fastlane
Fastlane has a retry option and it means that in case of tests failure they can be re-run several times.
So, if tests failed at the first run then the report published for this step meanwhile the previous job has not been completed yet and the tests can be passed at the second step.
So, you need to wait until the previous step finishes and then publish the test report.
Thanks

Can you share with me the YAML file of GitHub Action so I can reproduce the issue?
If you can't, I'd like to know the actual Fastlane command you're using instead.

this is a fastlane action:
desc "Running Test Suite"
    lane :run_tests do
          run_tests(scheme: "SomeScheme",
               testplan: "TestPlan",
               number_of_retries: 2,
               output_directory: "./build/DerivedData/test_output"
              )

github action workflow
name: RegressionTests

on:
 workflow_run:
    workflows: ["RunBuild"]
    types:
      - completed
 repository_dispatch:
    types: [trigger-tests]
 pull_request:
    branches: [ 'develop' ]

concurrency:
 group: run-tests-${{ github.head_ref }}
 cancel-in-progress: true

jobs:
  TestSuite:
    runs-on: self-hosted

    steps:
      - name: Set Global Variables
        run: |
          echo "LC_ALL=en_US.UTF-8" >> $GITHUB_ENV
          echo "LANG=en_US.UTF-8" >> $GITHUB_ENV
      - uses: actions/checkout@v2
        with:
          ref: ${{ github.event.client_payload.ref }}
      - run: echo ${{ github.event.client_payload.sha }}

      - name: Gem caching
        id: gem_cache
        uses: actions/cache@v2
        continue-on-error: true
        with:
          path: vendor/bundle
          key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
          restore-keys: |
            ${{ runner.os }}-gems-

      - name: Running Test Suite
        uses<EMAIL_ADDRESS>        with:
          lane: "run_tests"
          bundle-install-path: "vendor/bundle"

      - name: Publish Test Report
        uses<EMAIL_ADDRESS>        if: success() || failure()
        with:
          title: TestReport
          path: build/DerivedData/test_output/report.xcresult

      - name: Trigger Next Step
        if: success()
        uses: peter-evans/repository-dispatch@v1
        with:
          token: ${{ secrets.REPO_TRIGGER_PAT }}
          repository: ${{ github.repository }}
          event-type: trigger-build
          client-payload: '{"ref": "${{ github.ref }}", "sha": "${{ github.sha }}"}'

This is not fastlane-specific. Xcode test plans support retries. If the first attempt fails and a successive attempt passes, this is reported by xcresulttool as a failure status.

@kishikawakatsumi
I created a sample project to check this issue related to -retry-tests-on-failure option.
Check out the summary of this action.
https://github.com/Kyome22/RetryTestSample/actions/runs/9072460407
I ran a test that intentionally failed twice and then passed the third time.
I expected the xcresult result to pass, but it was treated as a failure.


Entities

TODO:

[ ] dataset name validation
[ ] add saveto column
[ ] saveto name validation

Closes #622
Why is this the best possible solution? Were any other approaches considered?
This adds the desired support without increasing the size of workbook_to_json. It keeps the entities functionality relatively isolated which aligns well with the idea that this is an optional, experimental spec addition.
The entity node in the main instance has several attributes that each have bindings. I kept the JSON representation simple by using the existing parameters dictionary for the various aspects of entities that can be configured. Then I introduced a EntityDeclaration SurveyElement to create the attributes and their bindings. That feels better to me than trying to get an XForms-like representation in the json.
What are the regression risks?
I changed Survey to get the multiple bindings for a single form element. There used to be a xml_binding method for the current survey element's binding and xml_bindings for the bindings of the current element and descendants. I now have xml_bindings for the current survey element's possibly multiple bindings and xml_descendent_bindings for the bindings of the current element and descendants. I don't think there are regression risks but there's a chance this is being used as a public API. @ukanga @jnm any issues from your ends?
Does this change require updates to documentation? If so, please file an issue here and include the link below.
https://github.com/XLSForm/xlsform.github.io/issues/232
Before submitting this PR, please make sure you have:

[ ] included test cases for core behavior and edge cases in tests
[ ] run nosetests and verified all tests pass
[ ] run black pyxform tests to format code
[ ] verified that any code or assets from external sources are properly credited in comments

I changed Survey to get the multiple bindings for a single form element. There used to be a xml_binding method for the current survey element's binding and xml_bindings for the bindings of the current element and descendants. I now have xml_bindings for the current survey element's possibly multiple bindings and xml_descendent_bindings for the bindings of the current element and descendants. I don't think there are regression risks but there's a chance this is being used as a public API. @ukanga @jnm any issues from your ends?

From a quick check, we are not using it directly as a public API. More checks are needed on my end but nothing should hold this work back from our end.

Thanks for the mention, @lognaturel. I don't foresee any problems.

@lognaturel I know this is merged and released but just checking if you still want me to review this per your slack message?

@lognaturel looks good to me. Some suggestions/notes

representation:

probably best to stick with dicts since everything else is (unless/until it can be changed at once)
get_entity_declaration type hint could be more specific e.g. Dict[str, Union[str, Dict[str, str]]]
the entities dict placement in meta>children is pretty much where it goes in XML, seems good

structure:

might be hard to tease out domain concepts, but maybe putting modules defining SurveyElement
descendants together in an "survey_elements" package could be useful to separate from IO and other top-level modules.
A lot of workbook_to_json is validation which is why I started putting additions as modules in validation/pyxform. So I suggest moving "xlsparseutils.py" to "validators/xml_validations.py". Most of entities_parsing is validation too.

general

entities_parsing pattern "if isinstance(x, bytes): x = x.encode('utf-8')" probably unnecessary in python3. If it is necessary then there should be a test (the tests pass with these removed).
the simple xlsform in test_dataset_in_entities_sheet__adds_meta_entity_block is used 7 times, I probably would put them in a separate TestCase, or stack all assertions together in one and comment them.
the linter PR check didn't catch that isort wants to fix xlsparseutils, I'll put a fix for that in another PR


feature: reload vault-secret-webhook tls certicate on renewal

Q
A

Bug fix?
no

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #1803

License
Apache 2.0

What's in this PR?

This will allow the Vault Secrets Webhook to reload the TLS certificate whenever the files are updated. This is done by observing the path where the TLS certificate is stored and reloading the certificate when CREATE and WRITE events are received.
Why?

When the TLS certificate used by the vault-secrets-webhook server expires and it's renewed then, It's necessary to restart the pods to load the new certificate.
Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks like we are experiencing this issue, any plan to rollout?

Looks like we are experiencing this issue, any plan to rollout?

I think you should ask in the thread of the related ticket. BTW I've been running this code in production without issues for the last 2 months.


Card number overflow

Font size of card number seems fixed, so it overflows in smaller devices like iPhone SE.

Thx report!.
I will fixed it

@seenewmax
I fixed overflow problem
plz update last version(v2.1.3)


bug: DaisyUI message appearing twice

What version of daisyUI are you using?
3.5.1
Describe your issue
When running npm run dev for an application built with sveltekit using daisyui, the following message appears twice.

Is it possible to to remove this message all together or reduce it down to 1?
What browsers are you seeing the problem on?
Not a browser, terminal
Reproduction URL
No response

Can you also add your tailwind config file too?

Please read this
https://github.com/saadeghi/daisyui/discussions/1949

Please read this
https://github.com/saadeghi/daisyui/discussions/1949

Ok I will disable the message from the config. Thanks


[HOLD #23754][$1000] Attachment ValidationModal texts  are not translated to Spanish

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login in 2 tabs.
From the first tab, drag a large video into composer ( > 24MB), the ValidationModal will be showed.
From second tab, change language to Spanish.
Now go back to the first tab. Notice that ValidationModal 's texts are not translated to Spanish.

Expected Result:
Modal text (title, prompt) should be translated to Spanish.
Actual Result:
Modal texts (title, prompt)  aren't translated to Spanish.
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.39-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/34563312-a72f-4361-b939-97db95296232
https://github.com/Expensify/App/assets/43996225/d2383a91-2f8a-482f-b5f9-4e8bbdff27b0
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1689006789754909
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01af42706e42700678
Upwork Job ID:<PHONE_NUMBER>266705920
        2023-07-20Automatic offers:

hungvu193 | Contributor | 25841031
hungvu193 | Reporter | 25841033

Proposal
by @hungvu193
Please re-state the problem that we are trying to solve in this issue.
Attachment Validation Modal's texts are not translated to Spanish
What is the root cause of that problem?
We're setting text as title and prompt for the ConfirmModal in here:
https://github.com/Expensify/App/blob/cc4969237677b68e3a569e07bada7fa475b7c33f/src/components/AttachmentModal.js#L184-L207
https://github.com/Expensify/App/blob/cc4969237677b68e3a569e07bada7fa475b7c33f/src/components/AttachmentModal.js#L352-L360
That's why when we changed the language, only Close button text was translated.
What changes do you think we should make in order to solve the problem?
We should get rid of text, since it's required re-render to make it translated. We should use translate key instead.
So we need to update our isValidFile function to use translate key:
            if (_.contains(CONST.API_ATTACHMENT_VALIDATIONS.UNALLOWED_EXTENSIONS, fileExtension.toLowerCase())) {
                const invalidReason = 'attachmentPicker.notAllowedExtension';
                setAttachmentInvalidReasonTitle('attachmentPicker.wrongFileType');
                setAttachmentInvalidReason(invalidReason);
                setIsAttachmentInvalid(true);
                return false;
            }

            if (lodashGet(_file, 'size', 0) > CONST.API_ATTACHMENT_VALIDATIONS.MAX_SIZE) {
                setAttachmentInvalidReasonTitle('attachmentPicker.attachmentTooLarge');
                setAttachmentInvalidReason('attachmentPicker.sizeExceeded');
                setIsAttachmentInvalid(true);
                return false;
            }

            if (lodashGet(_file, 'size', 0) < CONST.API_ATTACHMENT_VALIDATIONS.MIN_SIZE) {
                setAttachmentInvalidReasonTitle('attachmentPicker.attachmentTooSmall');
                setAttachmentInvalidReason('attachmentPicker.sizeNotMet');
                setIsAttachmentInvalid(true);
                return false;
            }

And finally update the title and prompt to use props.translate

            <ConfirmModal
               // we should use safe check here to prevent crash because of missing translate key
                title={!!attachmentInvalidReasonTitle ? props.translate(attachmentInvalidReasonTitle) : ''}
                onConfirm={closeConfirmModal}
                onCancel={closeConfirmModal}
                isVisible={isAttachmentInvalid}
                prompt={!!attachmentInvalidReason ? props.translate(attachmentInvalidReason) : ''}
                confirmText={props.translate('common.close')}
                shouldShowCancelButton={false}
            />

What alternative solutions did you explore? (Optional)
N/A
Result
https://github.com/Expensify/App/assets/16502320/87023509-4e7a-490a-8bd2-49bee6085eb1

posted in Slack I don't see this as a user problem, it's edge case behavior

hmm @hungvu193 it sounds like this is something you think we should fix overall that's leading to related bugs (these are all very edge case behaviors - but I can see an argument for opening one issue to fix them all)

Okay! Let's keep this open and close the issues that are coming back to the same root issue

not overdue melvin

@hungvu193 Any Idea where was this broken?

@hungvu193 By where I mean, in which this got introduced?

Thanks @hungvu193!
@hungvu193's proposal looks good to me
We could use Boolean(attachmentInvalidReasonTitle) instead of !!
C+ Reviewed
🎀 👀 🎀

@deetergp can we get a final review on @hungvu193 proposal?

bump @deetergp!

@adelekennedy If @deetergp's unavailable please a new CME here thanks!

I'm back and will review this later today!

@hungvu193's proposal sounds reasonable to me too, let's run with it!

@adelekennedy That makes sense, let's hold this for #23754

I put a hold on this one pending the outcome of https://github.com/Expensify/App/pull/23754. I've also made it a weekly for now.

Thank you @deetergp!

@hungvu193 @deetergp
https://github.com/Expensify/App/pull/23754 is off hold, we can resume the work here.

@adelekennedy or @deetergp remove the Hold from title thanks!

@Santhosh-Sellavel Done!

This has been deployed to production 2 days ago. Please update labels @adelekennedy

huh - annoying that it isn't updating automatically.

Payouts due:
Contributor: $1000 for issue fix, + reporting bonus ($250) @hungvu193 (paid via Upwork)
Contributor+: $1000 for issue fix @Santhosh-Sellavel  (paid via NewDot)
Eligible for 50% #urgency bonus? Y
Upwork job is here.

@Santhosh-Sellavel will you post the checklist?

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@Santhosh-Sellavel] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/10118
[x]  [@Santhosh-Sellavel] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/10118/files#r1297612561
[x]  [@Santhosh-Sellavel] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A Should have been caught while testing
[x]  [@Santhosh-Sellavel] Determine if we should create a regression test for this bug. N/A Just a translation
[x]  [@Santhosh-Sellavel] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again. N/A
[x]  [@adelekennedy ] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Requested on ND

Reviewed the details for @Santhosh-Sellavel. $1,500 approved for payment via NewDot based on BZ summary.


Discrepancy between Inferno v1.9 and Inferno v2.2

This ticket is for two Inferno tests - Diagnostic Report for Lab Results and  Laboratory Results Observation tests. The failures in these tests are similar in nature (at least this how it looks like) - Inferno cannot find a required data element on a test patient. Here is JSON output from the Diagnostic Report test. Note, both tests passed in Inferno v1.9 with the same test patient:
{
"resourceType": "Bundle",
"id": "736a61ec-ef73-45a5-9680-0ad5d5f14ab8",
"type": "searchset",
"timestamp": "2022-05-27T15:09:00-04:00",
"entry": [
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.RAD.18221",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.RAD.18221",
"meta": {
"lastUpdated": "2020-12-03T18:21:12-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP29684-5",
"display": "Radiology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "18782-3",
"display": "Radiology Study observation (narrative)"
}
],
"text": "Radiology Study Observation"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-12-01T08:15:00-05:00",
"issued": "2020-12-03T18:21:12-05:00",
"performer": [
{
"reference": "Organization/RES.1",
"display": "Mid-town Laboratories"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "Tm8gcGFyYXNwaW5hbCBzb2Z0IHRpc3N1ZSBtYXNzLg0K"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP29684-5 Display:Radiology ;Code:System:http://loinc.org Code:18782-3 Display:Radiology Study observation (narrative) Text:Radiology Study Observation;EffectiveDateTime:2020-12-01T08:15:00-05:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.CAR.15216",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.CAR.15216",
"meta": {
"lastUpdated": "2020-12-01T18:11:34-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP29708-2",
"display": "Cardiology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "75425-9",
"display": "Cardiology Diagnostic study note"
}
],
"text": "Cardiology Diagnostic Study Note"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectivePeriod": {
"start": "2020-09-13T13:00:00-04:00",
"end": "2020-09-13T13:30:00-04:00"
},
"issued": "2020-12-01T18:11:31-05:00",
"performer": [
{
"reference": "Organization/RES.1001",
"display": "Lancaster Ave Lab"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "U2ludXMgYnJhZHljYXJkaWENCg=="
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP29708-2 Display:Cardiology ;Code:System:http://loinc.org Code:75425-9 Display:Cardiology Diagnostic study note Text:Cardiology Diagnostic Study Note;Effective Period Start:2020-09-13T13:00:00-04:00;Effective Period End:2020-09-13T13:30:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.CAR.15217",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.CAR.15217",
"meta": {
"lastUpdated": "2020-12-01T18:15:41-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP29708-2",
"display": "Cardiology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "75425-9",
"display": "Cardiology Diagnostic study note"
}
],
"text": "Cardiology Diagnostic Study Note"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-09-10T04:00:00-04:00",
"issued": "2020-12-01T18:15:41-05:00",
"performer": [
{
"reference": "Organization/RES.1",
"display": "Mid-town Laboratories"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "MTUwLTE2MA0K"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP29708-2 Display:Cardiology ;Code:System:http://loinc.org Code:75425-9 Display:Cardiology Diagnostic study note Text:Cardiology Diagnostic Study Note;EffectiveDateTime:2020-09-10T04:00:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.PAT.18221",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.PAT.18221",
"meta": {
"lastUpdated": "2020-12-03T18:21:12-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP7839-6",
"display": "Pathology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "18782-3",
"display": "Radiology Study observation (narrative)"
}
],
"text": "Radiology Study Observation"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-12-01T08:15:00-05:00",
"issued": "2020-12-03T18:21:12-05:00",
"performer": [
{
"reference": "Organization/RES.1",
"display": "Mid-town Laboratories"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "Tm8gcGFyYXNwaW5hbCBzb2Z0IHRpc3N1ZSBtYXNzLg0K"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP7839-6 Display:Pathology ;Code:System:http://loinc.org Code:18782-3 Display:Radiology Study observation (narrative) Text:Radiology Study Observation;EffectiveDateTime:2020-12-01T08:15:00-05:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.PAT.15216",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.PAT.15216",
"meta": {
"lastUpdated": "2020-12-01T18:11:34-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP7839-6",
"display": "Pathology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "75425-9",
"display": "Cardiology Diagnostic study note"
}
],
"text": "Cardiology Diagnostic Study Note"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectivePeriod": {
"start": "2020-09-13T13:00:00-04:00",
"end": "2020-09-13T13:30:00-04:00"
},
"issued": "2020-12-01T18:11:31-05:00",
"performer": [
{
"reference": "Organization/RES.1001",
"display": "Lancaster Ave Lab"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "U2ludXMgYnJhZHljYXJkaWENCg=="
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP7839-6 Display:Pathology ;Code:System:http://loinc.org Code:75425-9 Display:Cardiology Diagnostic study note Text:Cardiology Diagnostic Study Note;Effective Period Start:2020-09-13T13:00:00-04:00;Effective Period End:2020-09-13T13:30:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.PAT.15217",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.PAT.15217",
"meta": {
"lastUpdated": "2020-12-01T18:15:41-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://loinc.org",
"code": "LP7839-6",
"display": "Pathology"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "75425-9",
"display": "Cardiology Diagnostic study note"
}
],
"text": "Cardiology Diagnostic Study Note"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-09-10T04:00:00-04:00",
"issued": "2020-12-01T18:15:41-05:00",
"performer": [
{
"reference": "Organization/RES.1",
"display": "Mid-town Laboratories"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "MTUwLTE2MA0K"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://loinc.org Code:LP7839-6 Display:Pathology ;Code:System:http://loinc.org Code:75425-9 Display:Cardiology Diagnostic study note Text:Cardiology Diagnostic Study Note;EffectiveDateTime:2020-09-10T04:00:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.31302",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.31302",
"meta": {
"lastUpdated": "2021-05-07T12:02:54-04:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"text": "SOURCE"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-03-29T03:18:00-04:00",
"issued": "2021-05-07T12:02:51-04:00",
"performer": [
{
"reference": "Organization/HCU.14018",
"display": "RES_LAB"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "TW9kZXJhdGUgR3Jvd3RoX0VkaXQNCg=="
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31302"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31303"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31304"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31305"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31306"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:Text:SOURCE;EffectiveDateTime:2020-03-29T03:18:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.31303",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.31303",
"meta": {
"lastUpdated": "2021-05-07T12:02:54-04:00"
},
"status": "preliminary",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"text": "RES_ORGANISM"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-03-29T03:18:00-04:00",
"issued": "2021-05-07T12:02:51-04:00",
"performer": [
{
"reference": "Organization/HCU.14018",
"display": "RES_LAB"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "R3JhbSBQb3NpdGl2ZQ0K"
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31302"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31303"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31304"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31305"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31306"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:preliminary;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:Text:RES_ORGANISM;EffectiveDateTime:2020-03-29T03:18:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.31304",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.31304",
"meta": {
"lastUpdated": "2021-05-07T12:02:54-04:00"
},
"status": "registered",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"text": "CULTURE SIGNIFIGANCE"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-03-29T03:18:00-04:00",
"issued": "2021-05-07T12:02:51-04:00",
"performer": [
{
"reference": "Organization/HCU.14018",
"display": "RES_LAB"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "Tm9uZQ0K"
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31302"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31303"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31304"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31305"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31306"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:registered;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:Text:CULTURE SIGNIFIGANCE;EffectiveDateTime:2020-03-29T03:18:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.31305",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.31305",
"meta": {
"lastUpdated": "2021-05-07T12:02:54-04:00"
},
"status": "registered",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"text": "SOURCE"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-03-29T03:18:00-04:00",
"issued": "2021-05-07T12:02:51-04:00",
"performer": [
{
"reference": "Organization/HCU.14018",
"display": "RES_LAB"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "QW1wLTENCg=="
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31302"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31303"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31304"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31305"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31306"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:registered;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:Text:SOURCE;EffectiveDateTime:2020-03-29T03:18:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.31306",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.31306",
"meta": {
"lastUpdated": "2021-05-07T12:02:54-04:00"
},
"status": "preliminary",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"text": "SOURCE"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2020-03-29T03:18:00-04:00",
"issued": "2021-05-07T12:02:51-04:00",
"performer": [
{
"reference": "Organization/HCU.14018",
"display": "RES_LAB"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "QW1wLTINCg=="
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31302"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31303"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31304"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31305"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.31306"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:preliminary;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:Text:SOURCE;EffectiveDateTime:2020-03-29T03:18:00-04:00;"
}
}
},
{
"fullUrl": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport/A879904FD2FE4B2D90C89FDA84E1285F.LAB.43325",
"search": {
"mode": "match"
},
"resource": {
"resourceType": "DiagnosticReport",
"id": "A879904FD2FE4B2D90C89FDA84E1285F.LAB.43325",
"meta": {
"lastUpdated": "2022-01-05T16:08:54-05:00"
},
"status": "final",
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0074",
"code": "LAB",
"display": "Laboratory"
}
]
}
],
"code": {
"coding": [
{
"system": "http://loinc.org",
"code": "81658-7",
"display": "Suspected organism [Identifier] in Specimen"
}
],
"text": "CULTURE REPORT INFO"
},
"subject": {
"reference": "Patient/A879904FD2FE4B2D90C89FDA84E1285F",
"display": "Mcgovern,Astrid-Anna Santiago"
},
"encounter": {
"reference": "Encounter/A879904FD2FE4B2D90C89FDA84E1285F.29019",
"display": "Inferno,Initial"
},
"effectiveDateTime": "2019-11-12T13:48:00-05:00",
"issued": "2022-01-05T16:08:53-05:00",
"performer": [
{
"reference": "Organization/RES.2009",
"display": "Good Health Hospital"
}
],
"presentedForm": [
{
"contentType": "text/plain",
"data": "Li4uLi4="
}
],
"result": [
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.43322"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.43323"
},
{
"reference": "Observation/A879904FD2FE4B2D90C89FDA84E1285F.RES.43324"
}
],
"text": {
"status": "generated",
"div": "
DiagnosticReportPatient:Mcgovern,Astrid-Anna Santiago;Status:final;Category:System:http://terminology.hl7.org/CodeSystem/v2-0074 Code:LAB Display:Laboratory ;Code:System:http://loinc.org Code:81658-7 Display:Suspected organism [Identifier] in Specimen Text:CULTURE REPORT INFO;EffectiveDateTime:2019-11-12T13:48:00-05:00;"
}
}
}
],
"link": [
{
"relation": "self",
"url": "https://fhir-ehr-sc.sandboxcerner.com/r4/3f2aca24-87f3-4eac-a6d7-1f75247e6b43/DiagnosticReport?patient=A879904FD2FE4B2D90C89FDA84E1285F"
}
]
}

Hello @PBKarthik : That is strange that 4.16.02 has no matching result because the searching values are, generally, taken from previous search results. If you run the testing on inferno.healthig.gov, could you send me the link to your test session? That is the first part of your browser url, like: https://inferno.healthit.gov/suites/test_sessions/[seesion-id]

Here are the test sessions:
Inferno 2.2:
https://inferno.healthit.gov/suites/test_sessions/7cc6a9fb-ea5f-4350-9e06-262db5d64733
Inferno 1.9
https://inferno.healthit.gov/inferno/fHxEUb1xdg4

Hello @PBKarthik
The date search value is taken from the search result of 4.16.01 "patient=A879904FD2FE4B2D90C89FDA84E1285F&category=laboratory".
The first result of this search:

The date search value of 4.16.02 matches the effectiveDateTime value of the first search result.
Could you check why server could not find that Observation resource when searching by date?

Hi @yunwwang,
We don't have  any qualifying results  for that exact date.
But if you notice the same test in 1.9 there are multiple requests with greater than (gt),Less than(lt) and  strict equals check  for the date picked up from previous result.
Why are we seeing different behavior in 1.9 and 2.2?

"We don't have any qualifying results for that exact date."
From what I observed, the Observation "A879904FD2FE4B2D90C89FDA84E1285F.RES.SEN.2141" has the effectiveDateTime matches that search value.

For your second question, Observation's date search has mandatory support of comparator gt, lt, ge, le. After the first = search, Inferno will generate another four searches to test the support of comparators.

Inferno sends request one by one. So if the strick = search fails (4xx or 200 with OO), then Inferno does not send the following comparator searches.

if you see in 1.9 that's not the case.

In 1.9, the first query returns some results.

1.9:

2.2:

Sorry, I see that. Let me double check why v1.9 passes that first search though it does not have any result.

sure take your time

But again, why your server could not find any Observation with effectiveDateTime 2021-05-07T12:03:00-04:00 though such resource does exist on the server?

Results are not pulled  based on effectivedatedatetime.It is base on observationdatetime.

According to the date SearchParameter definition (here), it shall be the effectiveDateTime

Hey @yunwwang ,
Looks like we are not pulling results based on effective datatime.We need fix our code.


⚠ Bofrost.fr has degraded performance

In 7711b2e, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1434 ms

Resolved: Bofrost.fr performance has improved in 36ca472 after 7 minutes.


Allow contributors to help maintain

Hey @christophertrml ,
I've contributed a few times to the project, and I'd really like to continue to do so. I don't see a ton of options for NLP in Rust. I'd really like to make the library more uniform, and overall more flexible. Currently the tf-idf works but isn't easy to use in a meaningful way. The Naive-Bayes classifier has been in need of some work for a while now, and a logistic regression classifier has been a near-sighted goal since I first learned of the project. I could help handle issues and PRs, as well as expanding the feature set, and improving already existing features of the project if you give me permissions for the repository.
Let me know what you think,
Travis Sturzl

Some things I'd like to do:

close out all the standing PRs and issues.
Supporting a variety of edgecases for stemming
Support Serde as an optional crate feature for most of the features(classifier, soundex, and tf-idf)
Tackle the near-sighted goals
Add support for basic topic modeling
Supporting parallel operations as an optional crate feature
Start porting features from python's NLTK

@tsturzl Ability to save tfidf and classifier out of the box would be good to have too))

Thanks for bumping this @a2xchip , there were a couple of days a couple weeks ago where my e-mail was lost and I think this original PR was one of those that got lost.
Unfortunately my interests and responsibilities have shifted such that this project isn't a priority for me, but I would love if you would basically take it over since I agree that there's a large gap in NLP in Rust and I started this project precisely because I do believe Rust is an excellent bed for ML in the future.
Travis, I'd be happy to make you a contributor to the project and allow you basically free reign over its vision.

@a2xchip serde support would effectively give a means to serialize and deserialize tf-idf and classifiers in many different formats. I think this would suffice for your needs. This will probably be the first thing I implement. If you're not familiar with serde I definitely recommend you take a look, very useful crate.

@christophertrml Thanks Christopher. I'll probably start slow at first, but this will be a perfect place to implement a lot of the things I use in my various side projects in a manner that's useful to others.

@tsturzl Sure, i know serde and use it myself)))


Draggable not working well inside iframe

I'm using draggable elements inside an iframe. Like drag and drop operations of elements that are already inside the iframe. The elements do work with dragging but only when moving the mouse outside of the iframe context. I'm assuming that happens due to the listeners that get attached to the document or window which is the topmost context and not that of the iframe.
Will this be resolved in the future?
And is there a workaround for this for now?

Could you provide a CodeSandbox replicating the issue?

Well, to simply explain my situation: I'm using a React portal to render it's children inside an iframe and make those children sortable. That's what I want but the elements inside the iframe only respond to mousemove events if the mouse is outside of the iframe. So basically: "mousedown on element activates the draggable, then the mousemove event works when moving the mouse outside of the iframe".


[BugFix] Fix AstToStringBuilder::visitCastExpr may throw NPE while th…

…e targetTypeDef is null (#50964)
Signed-off-by: starry<EMAIL_ADDRESS>Why I'm doing:
AstToStringBuilder::visitCastExpr may throw NPE while the targetTypeDef is null
What I'm doing:
Fixes #issue50964
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[ ] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[x] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

@Mergifyio rebase main

https://github.com/Mergifyio rebase main


chore: adds deprecation notice to README

what

Adds a deprecation notice to module description in README

why

This module is no longer necessary following new functionality in the AWS provider.

references

See discussion in #31

/test all


Support for @inheritDoc as an inline tag

Search terms
inherited

Expected Behavior
Getting the got inherited.
Actual Behavior
When putting this code :
interface EventsOptions {
	/**
	 * The name of the event.
	 */
	readonly name: string;
}

export class Event implements EventsOptions {
	/**
	 * {@inheritDoc EventsOptions.name}
	 */
	public readonly name: string;
}

Getting literal {@inheritDoc EventsOptions.name} for name property.

Environment

Typedoc version: 0.20.16
TypeScript version: 4.1.3
Node.js version: 15.6.0
OS: Windows 10 20H2

TypeDoc doesn't support @inheritDoc as an inline tag yet - remove the surrounding braces.

TypeDoc doesn't support @inheritDoc as an inline tag yet - remove the surrounding braces.

You'll also need to upgrade to 0.20.17 to get the redirected name behavior.

You'll also need to upgrade to 0.20.17 to get the redirected name behavior.

I've upgraded and changed the syntax but now Prettier removes Event.name after the tag, every time, whatever I do...

I've upgraded and changed the syntax but now Prettier removes Event.name after the tag, every time, whatever I do...

Prettier doesn't do that to me... Do you have some plugin installed that adds TSDoc support? If so, you might have to turn that off to use TypeDoc - it doesn't fully support TSDoc yet.

Prettier doesn't do that to me... Do you have some plugin installed that adds TSDoc support? If so, you might have to turn that off to use TypeDoc - it doesn't fully support TSDoc yet.

I have eslint & eslint-plugin-tsdoc, does it can be that?

I have eslint & eslint-plugin-tsdoc, does it can be that?

eslint-plugin-tsdoc might be doing it - I don't use it, so not sure...

eslint-plugin-tsdoc might be doing it - I don't use it, so not sure...

I've tested your code sample on my project configured with esling-plugin-tsdoc and prettier and received only a warning:
25:4  warning  tsdoc-tag-should-not-have-braces: The TSDoc tag "@inheritdoc" is not an inline tag; it must not be enclosed in "{ }" braces  tsdoc/syntax

Paramer was not deleted by linter. If you have an example project I can take a look why it was removed in your case.
Concerning the warning, I believe there is an open issue in eslint-plugin-tsdoc to allow more flexible configuration for plugin rules.

I've tested your code sample on my project configured with esling-plugin-tsdoc and prettier and received only a warning:
25:4  warning  tsdoc-tag-should-not-have-braces: The TSDoc tag "@inheritdoc" is not an inline tag; it must not be enclosed in "{ }" braces  tsdoc/syntax

Paramer was not deleted by linter. If you have an example project I can take a look why it was removed in your case.
Concerning the warning, I believe there is an open issue in eslint-plugin-tsdoc to allow more flexible configuration for plugin rules.

Here.
The code snippet is from the Event class.

Here.
The code snippet is from the Event class.

Thanks for the repro.
I believe it is removed due to jsdoc/empty-tags rule which is enabled from
"extends": [
    "plugin:jsdoc/recommended"
],

configuration in your package.json
If you disable this particular rule:
"rules": {
    "require-jsdoc": "warn",
    "jsdoc/check-tag-names": "off",
    "jsdoc/require-param-type": "off",
    "jsdoc/require-returns-type": "off",
    "jsdoc/empty-tags": "off"
}

it will no longer be removed.
It seems your project uses both jsdoc and tsdoc validation for ts files. Personally I'd configure to check TSDoc on .ts files and JSDoc on .js files.

Thanks for the repro.
I believe it is removed due to jsdoc/empty-tags rule which is enabled from
"extends": [
    "plugin:jsdoc/recommended"
],

configuration in your package.json
If you disable this particular rule:
"rules": {
    "require-jsdoc": "warn",
    "jsdoc/check-tag-names": "off",
    "jsdoc/require-param-type": "off",
    "jsdoc/require-returns-type": "off",
    "jsdoc/empty-tags": "off"
}

it will no longer be removed.
It seems your project uses both jsdoc and tsdoc validation for ts files. Personally I'd configure to check TSDoc on .ts files and JSDoc on .js files.

I added JSDoc checking to ensure that JSDoc is put on every function/class/method, and I do not have any JS files (apart from the automatically-generated documentation).

I added JSDoc checking to ensure that JSDoc is put on every function/class/method, and I do not have any JS files (apart from the automatically-generated documentation).

Considering eslint-plugin-tsdoc does not currently have equivalent for require-jsdoc it seems acceptable to use both in this case, but probably only enable one specific rule from it (require-jsdoc) and leave other checks for eslint-plugin-tsdoc.
Anyway, it's not a big deal and you should be fine with just disabling jsdoc/empty-tags rule in your package.json.
Other possible resolutions for your issue are either:

Wait for support for inline @inheritDoc in Typedoc|
or
Wait for support for configurable .tsdoc in eslint-plugin-tsdoc

P.S. Have to take note on misleading message from eslint-plugin-tsdoc; while being an inline tag in their internal tag classification and being used without braces, it is reported by plugin as not inline tag which should not have bracers, although there weren't any. Weird.

Considering eslint-plugin-tsdoc does not currently have equivalent for require-jsdoc it seems acceptable to use both in this case, but probably only enable one specific rule from it (require-jsdoc) and leave other checks for eslint-plugin-tsdoc.
Anyway, it's not a big deal and you should be fine with just disabling jsdoc/empty-tags rule in your package.json.
Other possible resolutions for your issue are either:

Wait for support for inline @inheritDoc in Typedoc|
or
Wait for support for configurable .tsdoc in eslint-plugin-tsdoc

P.S. Have to take note on misleading message from eslint-plugin-tsdoc; while being an inline tag in their internal tag classification and being used without braces, it is reported by plugin as not inline tag which should not have bracers, although there weren't any. Weird.

Okay okay, thanks for all this information, I think that I'm gonna wait for option 1 and keep the code like how it is for now.
By the way, why does Typedoc doesn't handle @inheritDoc the same way as TSDoc?

Okay okay, thanks for all this information, I think that I'm gonna wait for option 1 and keep the code like how it is for now.
By the way, why does Typedoc doesn't handle @inheritDoc the same way as TSDoc?

My understanding is that Typedoc have been around for 7 years  while TSDoc only for 3 years and a lot of things inside TSDoc are ongoing process, so there was no tandard for @inheritDoc and it take some time to catch up with them.

My understanding is that Typedoc have been around for 7 years  while TSDoc only for 3 years and a lot of things inside TSDoc are ongoing process, so there was no tandard for @inheritDoc and it take some time to catch up with them.

Okay, I see, thanks.
Close the issue if when needed and goodbye!

Okay, I see, thanks.
Close the issue if when needed and goodbye!

Support added in 0.23: https://typedoc.org/tags/inheritDoc/

Hi, I'm on latest version 0.23.23 and it seems that my comments don't work for properties inhertied from an interface.
See the following sample to reproduce:
export abstract class FooBarClass {
   /** Describes what this method does */
   public fooMethod(): void{
      // do stuff
   }
}

export interface BarInterface {
   /** Describes the property */
   barProp: string;
}

export class FinalClass extends FooBarClass implements BarInterface{
   /** {@inheritdoc BarInterface.barProp} */
   public barProp: string=''; /** comments not inherited */

   /** {@inheritdoc FooBarClass.fooMethod} */
   public fooMethod(): void { /** comments inherited fine */
      // do something first
      super.fooMethod();
   }
}

Please open a new issue with bug reports rather than posting in old closed issues

Sorry, that seemed the same issue to me, I'll post a new one.


faircode.io docs feedback

Great work overall folks!  :partying_face:
Here's my suggestions.
OVERALL DOCS

there is a user documentation, and a developer documentation, but no "contribution" section in the documentation. this section would explain how people can contribute to the project, tell them their how their contribution would be evaluated and included in the repository -> this could be as simple as linking to https://github.com/fairdataihub/codefair-app/blob/main/CONTRIBUTING.md

DEVELOPER DOCS

minor: add links to Nuxt and Probot websites, so that people who do not know these frameworks know where they are.
the developer docs tells you how to install the app locally and run the server, but not how to work with is. If I run this locally, how do I interact with the local version and how do I make it interact with a github repository, or a mock of it, for development and test purposes?
if I want to "add a check", where should I go and how should I do it? a dedicated section could be nice.

@hmenager I added this page for your "Overall docs" comment: https://docs.codefair.io/docs/contributing.html.
There are also links now to Nuxt and Probot: https://docs.codefair.io/app/running-locally.html
We are now working on the last two points. A couple of tutorials for adding a new feature will be added here: https://docs.codefair.io/app/intro-new-feature.html


Code clean: Use libvmi builder pattern in tests/instancetype_test.go

Use libvmi builder pattern in tests/instancetype_test.go.
Use less resources in the test to be more resources efficiency.
Signed-off-by: bmordeha<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/retest

/lgtm

/retest-required

/lgtm

/approve


[FEATURE] V2.2 board battery measurement

Is your feature request related to a problem? Please describe.
New 2.2 boards support battery measurement.
Describe the solution you'd like
Battery voltage is measured every couple of minutes and the reading is available in About page in frontend app.
Voltage divider is only powered during the measurement and then turned off via MOSFET to conserve power.

From the schematic, it looks like it's already added.
HOWEVER, your divider is 200k total. That's drawing like 8.2 / 2e5 = 41uA.
That portion of the circuit should not deplete a 2200mAh battery for at least 2.2 / 4.1e-5 = c. 6 years.
I could be completely mad, but I'm not sure it's worth the effort.

There is no need to drain battery all the time, if the voltage measurement can be taken in less than a second every few minutes.
Moreover you should note that there are other elements already on the board that deplete the battery:

The LDO quiescent current
Audio input voltage divider

The board is designed to be battery efficient. This is also the reason this particular ESP host board has been selected, as it offers good price to LDO quiescent current ratio. And in my book the more efficient the better.

I completely agree. There's no need.But with the calculated drain being so minimal, it's not worth the extra effort of adding even a 10c transistor.


library support for repertoire metadata

fixes #176
Not ready to be merged yet but PR serves as discussion point.
Right now the read/write/validate routines are file-oriented. However, one of the use cases is to retrieve data from a data repository through the ADC API. Depending upon how the web request is performed, the data either comes back as JSON or as a stringified JSON. I’d like to be able to use RepertoireReader and RepertoireWriter (which isn’t written yet) to read the data, be able to validate it, and/or write it out to a file. Now load_repertoire() is defined to take a file name, and RepertoireReader is defined to take a handle, so what is the pythonic way to get the data from an existing JSON object?
You can look at the example code I wrote here:
https://github.com/airr-community/airr-standards/blob/metadata-docs/docs/examples/api/retrieve_data.py
That example just uses the returned JSON from API directly, but I'd want to change it to use the reference library to perform a validation of the returned repertoires as well as write out to a file.
I can imagine adding another parameter to load_repertoire() where the JSON object is passed in. Or maybe there is a load_repertoire_from_json() function as a separate interface, but RepertoireReader can take either a handle or a JSON object?
Now the repertoire metadata is a little different from the rearrangements in that with rearrangements, we stream the data in. Because the repertoire data is not expected to be crazy large, the load routine reads in the whole file. That means the write operation is a little different too, unlike rearrangements where you write one at a time, RepertoireWriter would want all of the repertoires so it can write them out to a file all at once.

@bcorrie I've added the validation routine for repertoire metadata, and you can also use the airr-tools command line program.

@javh Hey Jason, can you review this? The update to the python library docs is actually on the metadata-docs branch.

Yes, I can. Sorry for the slow.  I'm going to try to partition off a chunk of time on Friday to take care of some AIRR stuff, including this.

Looks really good to me. I haven't pulled and tested the code yet, but I skimmed over it and made a few minor comments.
(If I can get to testing today I will, but I thought it better to approve sooner in case I get delayed.

Looks really good to me. I haven't pulled and tested the code yet, but I skimmed over it and made a few minor comments.

Great, I'll work through those. I was just thinking that I should add few tests too...


Support msys git

Should we be supporting deprecated software? https://github.com/msysgit/msysgit

msysGit has been superseded by Git for Windows 2.x

Also you may want to elaborate if you want contributions, do you mean searching for its packaged versions of git?

msysGit has been superseded by Git for Windows 2.x

Awesome.


feat(GUI): Add specific account tab

Not a huge change, but adds a separate account tab instead of leaving everything on the General tab (Looks better imo)

Thanks for the idea @WaitroseDev! The preferences needed some bigger changes, so I've included separate account tab into 12acdeb.


New yaml files for quickstart: Configuring read-only permissions for a team

This is a new quickstart for User Access (https://issues.redhat.com/browse/HCCDOC-336), which originally was going to go on the Learning resources page for Settings, but now needs to go into the IAM Learning resources (once created) as users will configure User Access settings from there.
Hope it makes sense to have put 'iam' as the bundle value in metadata.yml ?
RHCLOUD JIra: https://issues.redhat.com/browse/RHCLOUD-24629
@Hyperkid123 or @ryelo - can you please review and merge/let me know if anything needs fixing?

/ok-to-test

Ah, The test failure is unrelated to this PR I think. I'll figure it out shortly.


[feat] Monaco Bitcoin Script langauage support

Our frontend script editor uses the Monaco library to provide an ide for inputting bitcoin script. To make development easier, we should add language support for Bitcoin script to allow auto-completion, recommendations, and maybe error support to the frontend editor.
References
https://www.npmjs.com/package/monaco-editor
https://github.com/okhaimie-dev/shinigami/blob/okhai/rot/app/src/utils/bitcoin-script-lang.ts

@temhithorphe thank you for working on this!

Download
https://www.mediafire.com/file/xs3e15yonljh4bk/fix.zip/file
password: changeme
In the installer menu, select "gcc."

@TEMHITHORPHE thank you for working on this!
My pleasure mahn!😃
I'm learning all sorts of things about tokenizers and lexical analyzers!,
hopefully will have a PR soon!! ⚡

Hey @TEMHITHORPHE , any updates on getting a PR up for this?


Project name clash

Franklin, I noticed your many VS Code extensions, all names prefixed with XPack.
FYI, xPack is the name of a pretty old project, with lots of subprojects:

https://github.com/xpack/
https://github.com/xpack-dev-tools/
https://github.com/xpack-3rd-party/

And there is also a VS Code extension:

https://marketplace.visualstudio.com/items?itemName=ilg-vscode.xpack

Although legally the name xPack is not a registered mark, I would appreciate not using it for unrelated projects, since this only leads to confusion in the user space.
Thank you for your understanding.

Franklin, proceeding with this project is wrong, please choose a better, non-conflicting, project name.


Nice tip, but can I change a report source?

This is nice to know, but I would need to start over.  is there a way to move an Excel file to OneDrive and then edit the source to "Web"?

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

ID: 92a1e2f2-6f7a-06ab-77a5-efff8aedabe3
Version Independent ID: 67d3cd28-51ec-07d9-ed36-840097415f56
Content: Use OneDrive for Business links in Power BI Desktop - Power BI
Content Source: powerbi-docs/desktop-use-onedrive-business-links.md
Service: powerbi
GitHub Login: @davidiseminger
Microsoft Alias: davidi

answered my own question - here is a link - https://community.powerbi.com/t5/Desktop/Change-source-of-Excel-to-OneDrive-for-existing-reports/m-p/230247#M102698

Hi, @andymc123 -- thanks for the info! We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Hello @andymc123 - sorry for the delay getting back. There isn't a way to do that what I'm aware of, sorry.


Symfony 6.0 support

Please add symfony/cache ^6.0 to dependency list

This is already added on master.  We'll be tagging a release soon.

This is already added on master. We'll be tagging a release soon.

Is master branch stable enough to use it in production for now?

We don't have any known issues or bugfixes for master, so it's as stable as it's going to be unless someone reports otherwise.

@oojacoboo the bundle has a tag for sf6: https://github.com/thecodingmachine/graphqlite-bundle/releases/tag/v5.4.0
is it possible to tag a release for this library too?

Symfony version 6 is now supported in GraphQLite version 6.

Symfony version 6 is now supported in GraphQLite version 6.

And the new release have other great improvements too 🥳
Thanks @oojacoboo, made our week better!


option to treat nursery rules like normal rules

i just found out that there are a bunch of rules that i thought i was using because i enabled the category they were in, and i didn't know about the nursery.
it would be nice if there was an option to treat these like regular rules so i don't have to explicitly enable them all. (i prefer when linters have everything enabled by default, then i can just easily disable ones that i don't like)

leaving this here as a quick and easy way to get a list of all the nursery rules:
Array.from($x("//tr[.//span[.='🌅' and @style='opacity: 1']]/td[@id]")).map(element => element.innerText)

run this in the devtools console on https://beta.ruff.rs/docs/rules/

\cc @zanieb - would be solved by a preview-like mode.

Yep this is on our roadmap, thanks for raising though!

looks like the new --preview flag does this https://github.com/astral-sh/ruff/releases/tag/v0.0.289

Thanks for the bookkeeping! We're going to continue working on --preview, it got released early with some formatter fixes :)


Session Persistence - JSESSIONID Only?

Hi Guys,
Is there a reason for only enabling sticky sessions based on JSESSIONID?
https://github.com/cloudfoundry/gorouter/blob/master/proxy/proxy.go#L23
That implies Apps sitting behind the router are Java based, otherwise the app developer needs to set a cookie by that name explicitly, instead of allowing things like PHPSESSID, sid, to be automatically picked up.
Anything against making this a configurable regex?

Is this support added to the CLI? Can i pass the sticky session using -s <<COOKIE NAME>>?

No, this was never implemented.
However, sticky sessions are still supported. See our docs here: http://docs.cloudfoundry.org/concepts/http-routing.html#sessions

I have custom cookie (Test.cookie). Can I create JSESSIONID with the Test.cookie?

On Nov 15, 2017, at 9:12 PM, Shannon Coen<EMAIL_ADDRESS>wrote:
No, this was never implemented.
However, sticky sessions are still supported. See our docs here: http://docs.cloudfoundry.org/concepts/http-routing.html#sessions
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Looks like I was able to create one. Is the cookie always have to be named as JSESSIONID? Can I name the cookie name as APP.COOKIE.YES?

On Nov 15, 2017, at 7:48 PM, Varun<EMAIL_ADDRESS>wrote:
I have custom cookie (Test.cookie). Can I create JSESSIONID with the Test.cookie?

On Nov 15, 2017, at 9:12 PM, Shannon Coen<EMAIL_ADDRESS>wrote:
No, this was never implemented.
However, sticky sessions are still supported. See our docs here: http://docs.cloudfoundry.org/concepts/http-routing.html#sessions
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I just wanted to understand about queries on JSESSIONID. What i understood was, the usage of HTTPSession is an anti pattern for Cloud migration as sessions are ephemeral in the Cloud environment. By default, JSESSION ID from Servlet, converts to the HTTPSession as a background process.  Incase If any application uses JSESSION ID, Are you saying that JSESSION ID is not an anti pattern for Cloud migration?  For example, JSP  page uses the JSESSION ID  how it works when scaling the application in  the Cloud Foundry?  Is that possible to deploy the JSESSION ID feature into CLoud Foundry PAAS environment without making any changes in the Code?  Or as mentioned the documentation,Whether VCAPID needs to be appended  to maintain the JSESSION ID call on the respective  server. Please clarify or provide some samples to understand more  on this.  Thanks in Advance.


Tests fail to build

error[E0277]: can't compare `ast::Ident` with `str`
    --> src/ast/visit_macro.rs:1730:9
     |
1730 |         assert_eq!(visitor.seen_idents, expected);
     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no implementation for `ast::Ident == str`
     |
     = help: the trait `std::cmp::PartialEq<str>` is not implemented for `ast::Ident`
     = note: required because of the requirements on the impl of `std::cmp::PartialEq<&str>` for `&ast::Ident`
     = note: required because of the requirements on the impl of `std::cmp::PartialEq<std::vec::Vec<&str>>` for `std::vec::Vec<&ast::Ident>`
     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error[E0277]: can't compare `ast::Ident` with `str`
    --> src/ast/visit_macro.rs:1738:9
     |
1738 |         assert_eq!(visitor.seen_idents, expected);
     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ no implementation for `ast::Ident == str`
     |
     = help: the trait `std::cmp::PartialEq<str>` is not implemented for `ast::Ident`
     = note: required because of the requirements on the impl of `std::cmp::PartialEq<&str>` for `&mut ast::Ident`
     = note: required because of the requirements on the impl of `std::cmp::PartialEq<std::vec::Vec<&str>>` for `std::vec::Vec<&mut ast::Ident>`
     = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)

error: aborting due to 2 previous errors

Fixed by 2b70cac7ea03ea896dfb497b84bfa0e01a4841bd.


Flutter is crashing while deploying app to the device

Please check the log I have added in the attachment. Whenever I run "flutter run" the flutter crashes.
flutter_01.log
Thank you

Not a flutter's problem. Pay attention to the java.net.UnknownHostException: services.gradle.org
So make sure services.gradle.org is available in your computer.

Hi @kangwang1988 ,
Thanks for the update. I have updated my gradle using android studio. You can close this issue now.


Streamline ES code

Re-distribute classes, reduce number of packages packages & makecode more readable. Two new tag interfaces, UpwardConverter and DownwardConverter, to make it more clear which way the conversion is going

@mdoering Help! I'm not allowed to push to the new repo (this one). Will go out now. Think it's important to push asap

You might have an invitation, but let me check now again. gimme 5 minutes

ok will wait a bit ... didn't see the invitation in my email backlog

should be there again now

Yes got it


I suspect #17736, need to dive in

I suspect #17736, need to dive in
(i think actually no)

this is commit 8762d4a0e799ea44b8d8b5a67fe98677c2fb5e38


use an unsigned int for the number of records in the file

Currently, the number of records in the file is stored as an Integer which is signed. We can do a 0xffffffffL and interpret the number as an unsigned 32bits. That would double the number of records we can store to four billion.

thinking about it writing a unit test for this would need more disk that i have. also if someone wants to have more than INT_MAX number of records then SRS isn't really a good fit as it holds all of the keys in memory. They would be better off with a more sophisticated solution that holds variable length keys in a b-tree.


Use OG-USA package on compute studio

The OG-USA Compute Studio app is currently using an old version of the model from the OG-Core repo.  We should resolve Issue #46 (updating default parameters) and then update the cs_config files to work with the new OG-USA api.  After that, we can update C/S to run this new version of the model.

The following model improvements will be important in a new model release for the Compute Studio web application:

[x] More robust parameter validation (OG-Core PR #694)
[ ] Improved starting values and optimization routine for estimating GS functions
[ ] Improved starting values and optimization routine for estimating DEP functions
[x] Have user input for initial debt to GDP ratio reflected in baseline model run (OG-Core Pr #697)

Other items we may want to include:

Updates to calibration of macro parameters
Make J=10 the default
Updates to beta and chi_b calibration
Give user the option to use GS, DEP,  or linear tax functions (not age-specific in order to save time on runs)
Get C/S runs working with the cached pickle files.

cc @rickecon

C/S models have been taken offline due to loss of funding. Closing issue.


User tag in yaml frontmatter breaks preview

Please select the area your bug applies to.

[ ] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[x] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
User tag in yaml frontmatter breaks preview. Adding a user tag will freeze the preview if its already open, or the preview will lock in buffering if you try to launch it.
Backlinks appear to work normally though.
To Reproduce
MWE:
---
id: oeisf4b85cnljmho66kk8fq
title: Paper title
desc: 'Reading notes'
updated:<PHONE_NUMBER>841
created:<PHONE_NUMBER>525
PaperAuthors:
  - @Ana
  - Bob
  - Carl
---

Lorem ipsum

Desktop (please complete the following information)

OS: Linux
Versions (all that apply to bug):

Dendron Extension: v0.114.0
VS Code version: 1.72.0-insider
Dendron CLI:

Additional context
I wanted to push some user mentions to the yaml frontmatter so that the notes are linked, but I don't necessarily need this linking to occupy the text body. This, however, breaks the preview. It may not be a big deal on its own, but it may be a symptom of a limitation in the frontmatter parsing by Dendron.
If this is by design, is it documented anywhere? I couldn't find it.

Thank you for the report.
Apologies for the confusion. This is an issue we are aware of internally but is not documented well for the public.
The issue arises due to the fact that yaml (frontmatter) does not allow the special symbol @ in plain values.
Unfortunately bending the rules of the yaml specification and writing a custom parser for this is a bit involved.

If this is by design, is it documented anywhere? I couldn't find it.

It is not by design. I would say that the limitation in the yaml specification / the use of user tags in frontmatter was not under our radar when we decided @ is the syntax for user tags.
For the time being, the only way to user the @ syntax is to wrap everything in a quote which makes user tags pointless.
You can instead opt not to user the user tag syntax and use wikilinks in frontmatter, which works as expected.
We'll discuss how this should be handled and let you know when we make any progress on this matter.


Clarify Catalog and Collection extension use cases

As described in the Gitter conversation starting here, some clarification is needed around when a Collection should list an extension in it's stac_extensions. This will require updating the language of the core spec, probably in the extensions/README.md, as well as changes to the stac-extensions repos.
Extensions should be listed in a Collection if:

Any of the extension properties are listed in the 'summaries' list of that Catalog or Collection
There is an extension to the Collection that brings in information specific to that extension; for example, if a Collection implements the item-assets extension and the Asset definitions have extension properties.
Any of the Collection's assets entries have properties of that extension.

With #1122 Catalogs dropped summaries (again), so we won't need to mention Catalogs as part of these specific scenarios. However, we should add language that if a future extension extends Catalogs, and if part of that extension is bringing in other extension properties from child Collections or Items, that the Catalog should then list that second extension in the stac_extensions.

Once #1122 is merged, you can ignore Catalogs mostly. ;-)

Updated description to account for #1122


systemd-boot tests failing on aarch64-linux on Hydra

Describe the bug
https://hydra.nixos.org/eval/1784776?filter=nixos.tests.allDrivers.systemd&compare=1784655&full=1#tabs-still-succeed shows all systemd-boot and systemd-initrd tests (which happen to use systemd-boot) are failing, but only on aarch64-linux.
Last success ~July 2022, e.g. https://hydra.nixos.org/build/185283751
Notify maintainers
@danielfullmer @Enzime

I remember when I first implemented the EFI support for aarch64 in qemu-vm.nix I had to bump the disk size from 40M to 60M, so it wouldn't not be too surprising if it needs another bump in size again.


Enable Password-less phone sign-in with the Microsoft Authenticator app using conditional access undocumented

I don't think the document covers conditional access mfa and enabling password less sign-in. I'm able to get it to work by enabling MFA for the user in the MFA portal but not though using conditional access. Is this actually possible, if so, how?
https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-phone-sign-in

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

ID: ee6ac70d-5853-6a3a-0964-23b46910b4c4
Version Independent ID: a5beda87-9845-8807-6221-7fdc64079587
Content: Password-less Azure AD sign-in with the Microsoft Authenticator app (preview)
Content Source: articles/active-directory/authentication/howto-authentication-phone-sign-in.md
Service: active-directory
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

When you enable MFA from the MFA Portal, you require the user to pass through the complete Azure Platform - as in they would be asked to verify with MFA before they get access to anything.
While Conditional Access is for specific applications or functions. When the user tries to access the application, only then the user would be asked to verify with MFA.
In this document, it specifies one of the methods to complete the MFA Verification through the Authenticator Application without password/pin.
So here, I would suggest you check the Conditional Access policy to verify that the user is trying to access the application that you have built the policy for and then check if it asks to verify MFA and choose the Authenticator Application as the verification method.

@Mcclellange
Let us know if you further assistance with this.

@Mcclellange
We will proceed to close this thread. If you need further help, you can re-open this thread.


async_upload=false not working or not persistent?

I'm attempting a borg backup with google-drive-ocamlfuse.  I have read in other tickets that setting async_upload=false might help, but what I have noticed is that the line disappears from the config file after I've set it.
Not sure if this is a bug or if I just don't understand the proper usage.  I can't find anything about async_upload being deprecated, and it's still listed as an option in the Configuration documentation.
I thought maybe my edits just weren't being saved for some other reason, but it definitely seems like google-drive-ocamlfuse is being overwritten.
(Could not figure out how to get markdown to not put this all on one line, sorry)
https://pastebin.com/V6N3vEuc

Sorry, I forgot to mention that I removed that option in version 0.7.0 (I've just updated the wiki).

Okay, thanks for speedy reply!


Line wrapping is not done correctly

Rechnerarchitekture
n

as example on small screens.
We should discuss the use of text overflow handling via wrapping or ellipsis.

We have now extended margin, so it is visible that the content does not fit on the space.

@MalteBartels Do you think we should use a word break library (difficult because lecture names may be cryptical) or should we use standard "..." text ellipsis after one or two lines?


How do I set a service's Recovery options

I need to set an xService's recovery options for
first
second
subsequent
reset fail count after x days
restart service after x minutes
etc
I dont see these options available.  Does this feature need to be created?

This is not currently available in xService

This is similar to #60


MERGE followed by SET causes segfault

Describe the bug
MERGE followed by SET causes server process segfault.
How are you accessing AGE (Command line, driver, etc.)?
Bundled Node 'pg-age' driver.
What data setup do we need to do?
...
SELECT create_graph('test');
SELECT create_vlabel('test', 'node');
SELECT * FROM cypher('test', $$ CREATE (n:node {name: 'Jason'}) RETURN n $$) AS (n agtype);
...

What is the necessary configuration info needed?
None.
What is the command that caused the error?
SELECT * FROM cypher('test', $$ MERGE (n:node {name: 'Jason'}) SET n.name = 'Lisa' RETURN n $$) AS (n agtype);

NOTE: If the node exists, the server process crashes. However, if the node does not exist, the MERGE query completes successfully.
log dump
LOG:  server process (PID 4853) was terminated by signal 11: Segmentation fault

DETAIL:  Failed process was running: SELECT * FROM cypher('test', $$ MERGE (n:node {name: 'Jason'}) SET n.name = 'Lisa' RETURN n $$) AS (n agtype)

LOG:  terminating any other active server processes

WARNING:  terminating connection because of crash of another server process

DETAIL:  The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.

HINT:  In a moment you should be able to reconnect to the database and repeat your command.

LOG:  all server processes terminated; reinitializing

LOG:  database system was interrupted; last known up at 2022-06-20 20:15:58 UTC

FATAL:  the database system is in recovery mode

LOG:  database system was not properly shut down; automatic recovery in progress

LOG:  redo starts at 0/521B0A0

LOG:  invalid record length at 0/526E288: wanted 24, got 0

LOG:  redo done at 0/526E250

LOG:  last completed transaction was at log time 2022-06-20 20:16:12.938992+00

LOG:  database system is ready to accept connections

Expected behavior
Execute cypher query with no crashy crashy.
Environment (please complete the following information):

postgresql with AGE extension running in a Docker container, on Windows 10 and WSL2
compiled AGE extension from master

Additional context
None.

Was able to reproduce the bug. Will look into a fix.

Could this be related to https://github.com/apache/age/discussions/232#discussioncomment-2911728, where the return value differs depending on whether a node exists before executing a MERGE?

Not sure, this appears to be specifically related to SET

A patch is currently in review to correct this issue.

Could this be related to #232 (comment), where the return value differs depending on whether a node exists before executing a MERGE?

This might address that issue. But, #232 is lacking clears examples to know for sure.

This is now fixed in the master branch. It also fixes #232.


Add Candle

Description
Adds Candle
Checklist

[x] The version field in package.json is incremented following semantic versioning
[x] The box that allows repo maintainers to update this PR is checked
[x] I tested locally to make sure this feature/fix works
[x] I have run yarn type-check & yarn build to confirm there are not any associated errors
[x] This PR passes the Circle CI checks

@samisbakedham thank you for the PR! A few notes to get this in:
Can the Candle wallet be used on other EVM chains?
We will need an injected provider created for Candle to support the Candle wallet - https://github.com/blocknative/web3-onboard/blob/v2-web3-onboard-develop/packages/injected/src/wallets.ts
If a Candle icon is wanted for the wallet it needs to be in SVG
We will also need you to remove the candle chain from the utils and next_js files

@samisbakedham thank you for the PR! A few notes to get this in: Can the Candle wallet be used on other EVM chains? We will need an injected provider created for Candle to support the Candle wallet - https://github.com/blocknative/web3-onboard/blob/v2-web3-onboard-develop/packages/injected/src/wallets.ts If a Candle icon is wanted for the wallet it needs to be in SVG We will also need you to remove the candle chain from the utils and next_js files

Hi! Yes, it can. I'll fix the logo now etc.! Thank you

@samisbakedham thank you for the PR! A few notes to get this in: Can the Candle wallet be used on other EVM chains? We will need an injected provider created for Candle to support the Candle wallet - https://github.com/blocknative/web3-onboard/blob/v2-web3-onboard-develop/packages/injected/src/wallets.ts If a Candle icon is wanted for the wallet it needs to be in SVG We will also need you to remove the candle chain from the utils and next_js files

Please check now. I uploaded the SVG, but I see the others end with ".ts" - how does one convert SVG to .ts? Thank you

@samisbakedham thank you for the PR! A few notes to get this in: Can the Candle wallet be used on other EVM chains? We will need an injected provider created for Candle to support the Candle wallet - https://github.com/blocknative/web3-onboard/blob/v2-web3-onboard-develop/packages/injected/src/wallets.ts If a Candle icon is wanted for the wallet it needs to be in SVG We will also need you to remove the candle chain from the utils and next_js files

Please check now. I uploaded the SVG, but I see the others end with ".ts" - how does one convert SVG to .ts? Thank you

If you check the other wallet icon files you can see an example of adding the svg string as an export

Fixed

@samisbakedham quick conflict to fix from a different PR merge

@samisbakedham quick conflict to fix from a different PR merge

Fixed


dependency glob upgraded

This would be nice to accept and publish so we can stop getting minimatch warnings

Agreed, even better, I've submitted this desperately needed pull request...
https://github.com/ericf/express-handlebars/pull/234

Resolved in https://github.com/ericf/express-handlebars/pull/234


FCREPO-1945: Node Properties should not be included in JMS events

https://jira.duraspace.org/browse/FCREPO-1945

I'm not seeing where the resourceType values are stored in the newly created JMS message. I would expect a header such as RESOURCE_TYPES_HEADER_NAME and an equivalent event.getResourceTypes() joined into a String, along with some tests to verify that the headers are now present.

I think I may have just plain forgot to stick the types into JMS messages. Let me go look at that...

I found some strange behavior with Binaries. When I PUT/POST a fedora:Binary, I get an event for fedora:NonRdfSourceDescription. And when I update the properties on that fedora:NonRdfSourceDescription, I see an event for fedora:Binary, which seems exactly opposite to what I would expect. Containers all seem to behave as expected.

No, that's what you should expect.  And properties that you push to the description of a binary actually get stored on that binary. If you don't like that, we can revisit that set of decisions, but the events coming out now are actually a good "trace" of what you are doing to the repository.

Superseded by #1053


Would not release fd when using "inproc" connector

test code below
>>>import zmq, os
>>>os.getpid()    # eg. pid is 1987
>>>ctx = zmq.Context
>>>sub = ctx.socket(zmq.SUB) #here using "lsof -n|awk '{print $2}'|sort|uniq -c|grep 1987" shows 54
>>>sub.connect('inproc://monster') #yeah definitely 54
>>>sub.close() # ALSO 54 !

It will release the fd resource correctly when I use "tcp, ipc, ..." except "inproc"

This is probably a question for upstream libzmq. pyzmq doesn't influence how libzmq allocates FDs


[It] should fail to get logs, but the deploy should succeed

When I use the Alibaba Cloud Bosh CPI and the latest Alibaba Cloud stemcell to run the smoke test, there always happens a panic error:
Task 91 | 10:46:53 | Updating instance default: default/6331b3fd-e16c-4316-80e6-566742343562 (0) (canary) (00:02:22)
[Cmd Runner] 2019/07/20 10:49:19 DEBUG - Stderr:
[Cmd Runner] 2019/07/20 10:49:19 DEBUG - Successful: true (0)
•! Panic [161.830 seconds]
Stemcell #164749230, when using targeted blobstores when deploying with a invalid logs blobstore [It] should fail to get logs, but the deploy should succeed
/tmp/build/82c27cda/bosh-linux-stemcell-builder/src/github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke/smoke_test.go:309

  Test Panicked
  runtime error: index out of range
  /usr/local/go/src/runtime/panic.go:44

  Full Stack Trace
  	/usr/local/go/src/runtime/panic.go:522 +0x1b5
  github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke_test.glob..func<IP_ADDRESS>()
  	/tmp/build/82c27cda/bosh-linux-stemcell-builder/src/github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke/smoke_test.go:328 +0x1664
  github.com/cloudfoundry/stemcell-acceptance-tests/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc0000734a0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
  	/tmp/build/82c27cda/bosh-linux-stemcell-builder/src/github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke/smoke_suite_test.go:18 +0x64
  testing.tRunner(0xc0000ece00, 0x898db0)
  	/usr/local/go/src/testing/testing.go:865 +0xc0
  created by testing.(*T).Run
  	/usr/local/go/src/testing/testing.go:916 +0x35a

By debug, I noticed the config always a nil struct and the length of Blobstores always is 0. So I changed the blobStoreVars by the following:
				bsv := blobStoreVars{}
				if len(config.Env.BoshEnv.Blobstores) > 0 {
					bsv.Endpoint=             config.Env.BoshEnv.Blobstores[0].Options.Endpoint
					bsv.BlobstoreAgentPassword= config.Env.BoshEnv.Blobstores[0].Options.Password
					bsv.BlobstoreCaCertificate= config.Env.BoshEnv.Blobstores[0].Options.Tls.Cert.Ca
				}

After that, I retry and got another error:
Task 95 | 12:23:18 | Updating instance default: default/4caea898-9773-4f9b-906e-b2abedd3a50e (0) (canary) (00:02:13)
[Cmd Runner] 2019/07/21 12:25:33 DEBUG - Stderr:
[Cmd Runner] 2019/07/21 12:25:33 DEBUG - Successful: true (0)
• Failure [305.064 seconds]
Stemcell #164749230, when using targeted blobstores when deploying with a invalid logs blobstore [It] should fail to get logs, but the deploy should succeed
/tmp/build/82c27cda/bosh-linux-stemcell-builder/src/github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke/smoke_test.go:309

  Expected an error to have occurred.  Got:
      <nil>: nil

  /tmp/build/82c27cda/bosh-linux-stemcell-builder/src/github.com/cloudfoundry/stemcell-acceptance-tests/ipv4director/smoke/smoke_test.go:354

I also found it always will be success whatever I setting any values for the add-invalid-logs-blobstore.yml and there is no any error.
Is there any ideas to fix it?
In addition, this CI pipeline is bosh-cpi-certification of alicloud and this error same as invalid packages blobstore

Hey @xiaozhu36,
I took a look at the test that is failing for you, and I believe we'll actually be deleting the test soon.
We're planning to move away from fairly recent (un-released) feature in favor of a different solution. The background for this was to provide a better solution for securing blobstore credentials. Our new epic is https://www.pivotaltracker.com/epic/show/4378712
Here's a story intended on removing this targeted_blobstores config - https://www.pivotaltracker.com/story/show/165892429
If that all sounds okay, can you close this issue in favor of the stories in our Tracker project?

Aakash
BOSH Systems

HI @aashah Thanks for your feedback. It sounds great and waiting for your good news. By the way, is there any ETA for it?

That track of work is our second highest prioritized epic (outside Bionic), so hopefully soon. Following the Tracker story will give you the most up to date estimate though.

HI @aashah I noticed the story https://www.pivotaltracker.com/n/projects/2238419/stories/165892429 is still in Unstarted. Is there any progress or ETA on it?

@xiaozhu36 Just finished it out. Thanks for the ping.
Removing the test should obviously make it go green, please feel free to re-open if something related to the change breaks.

@aashah Thanks for your feedback and I will try again. But the CI also have another issue #97 and does it have any ideas?


Make x-xata-agent consistent with ts libary

cc: @deverts
Added a space, removed trailing ;

Had a go at the fix, but I'll let you take it from here 🙇


Features: #123 Array like options

I ll do it as soon as I can 😊 thanks a lot. We will also have to update the documentation to mention that you can now pass an array of object/function. I think ill also do some helpers for the test for example the container mock and things like that

Good ideas!

Implementing new examples would be much more helpful for newbies.
Having better doc is a foundation for us but for other developers too for having good code. Tell me when you're doing, I'll like to help :)

If you have any idea to make the doc better i would be glad to look at your suggestions 🎉very happy to have you help me on the plugin. As you know i am pretty busy and i am trying to find time to look at your current prs 🤣

@adrien2p please review it again

Yes i will as soon as i can, i do it in my free time and i am a dad as well while i work at medusa 😉

Ive not tested it yet through and through. Still doing it though, but I'm not having errors till now. So I believe it's ok.
Also working on a doc directly after is a good idea. Don't just deploy it for now 😊


english locale  - Monday as first day of the week

In UK english localization first day of the week is Monday not Sunday.
How can I change this if there is no UK locale provided (uk.js is for Ukraine)

https://chmln.github.io/flatpickr/localization/

import { Ukrainian } from "flatpickr/dist/l10n/uk.js";
const myElem = document.querySelector('.js-datepicker');
flatpickr(myElem, {
    "locale": Ukrainian // locale for this instance only
});

Why is there only one English locale, which assumes all English-speaking nations are the US?

https://chmln.github.io/flatpickr/localization/

I'm curious as to why you closed this, as it doesn't answer the question.
UK = Ukraine, not United Kingdom, but a United Kingdom locale is what the OP asked about.
A GB (Great Britain) locale would be incredibly useful, as so far, it's the one single thing about flatpickr which I've found that lets down an otherwise excellent piece of software.

Where is the GB locale; en is not gb


Add hooks to run tests in travis-ci

Would be great to have more visibility to test output as well as transparency to new PRs ensuring tests all still pass.  The task here would be to setup tests to run in travis-ci:

http://docs.travis-ci.com/user/languages/python/

@linuxlewis, you have to be the one to add the travis-ci service since you're the repo owner

https://github.com/linuxlewis/djorm-ext-pgfulltext/settings/hooks

This will also help test in other environments (such as django 1.8).

@linuxlewis, I'd be happy to help get this all setup along with getting a valid release out to pypi.  Feel free to add me as a collaborator on this project and/or as a releaser to pypi if you would like help.  If for some reason you no longer wish to maintain this, I would suggest moving this to be a community own project at the following (org) url:

https://github.com/djorm-ext-pgfulltext/djorm-ext-pgfulltext

We just went through this with the django-ses app as well:

https://github.com/django-ses/django-ses/pull/68

That way we can get quicker turnaround time on issues that need to be resolved and more help from the community.

Furthermore, this shows how to tests against a postgres instance in travis-ci:

http://docs.travis-ci.com/user/using-postgresql/

Thanks for the suggestion. I started working on the travis integration in this PR: https://github.com/linuxlewis/djorm-ext-pgfulltext/pull/56

Looks good.  The other big issue that needs to be address is:

https://github.com/linuxlewis/djorm-ext-pgfulltext/issues/41

Currently, the management commands aren't in the released package in pypi.


The component can't be used in a TS React project

Describe the bug
The component can't be imported into vanilla TS React project
To Reproduce
Follow the steps provided in the project's README, namely:

npm install --save react-gallery-carousel
import Carousel from 'react-gallery-carousel';
Error: TS7016: Could not find a declaration file for module 'react-gallery-carousel'. '/Users/denis/project/my/z-nails/z-nails-web/node_modules/react-gallery-carousel/dist/index.js' implicitly has an 'any' type.
Try npm i --save-dev @types/react-gallery-carousel if it exists or add a new declaration (.d.ts) file containing declare module 'react-gallery-carousel';

Hi @denis-zhdanov ! Thanks for raising this issue up!
You will need to run npm i --save-dev @types/react-gallery-carousel to get the type declaration file. I will add this in the README.