Condition endpoint error with codes for system http://hl7.org/fhir/sid/icd-10-cm

Subject of the issue
Receiving errors on codes for system, http://hl7.org/fhir/sid/icd-10-cm.
Test Result: Fail
×
USCC-02: Server returns expected results from Condition search by patient
A server SHALL support searching by patient on the Condition resource
https://www.hl7.org/fhir/us/core/CapabilityStatement-us-core-server.html
Error Message: Invalid Condition: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition.code.coding[0]: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R51' Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category')
Your environment

Edition of inferno (Community or Program):  Community
Version of inferno: Version 2.9.0
Which browser and version(s) is the bug present on?: Chrome

Steps to reproduce

https://inferno.healthit.gov/community

US Core v3.1.0, url: https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/ click on Begin

Run Condition Tests, with Patient ID 300

Include:

The selected test suite - Condion
The URL of the FHIR server being tested - https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/
The Test ID, if it's a problem with a specific test. - 300

Expected behavior
Pass the USCC-02 and USCC-11 test
Actual behavior
USCC-02 and USCC-11 fail
Test Result: Fail
×
USCC-02: Server returns expected results from Condition search by patient
A server SHALL support searching by patient on the Condition resource
https://www.hl7.org/fhir/us/core/CapabilityStatement-us-core-server.html
Error Message: Invalid Condition: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition.code.coding[0]: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R51' Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category')
1 Request
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition?patient=300
HealthIT.gov
This server is provided for demonstration purposes.
Do not use to access sensitive data or Protected Health Information (PHI).
Data is removed every Sunday at 12:01am ET.
Inferno Logo COMMUNITY EDITION
US Core v3.1.0 FHIR R4
Inferno Logo Small https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4
SMART App Launch
SMART On FHIR Discovery - 5 tests - Show Details
Retrieve server's SMART on FHIR configuration
Dynamic Registration - 4 tests - Show Details
Verify that the server supports the OAuth 2.0 Dynamic Client Registration Protocol.
Manual Registration - 1 test - Show Details
Manually register the Inferno application with the authorization service
Standalone Launch Sequence - 9 tests - Show Details
Demonstrate the SMART Standalone Launch Sequence.
EHR Launch Sequence - 11 tests - Show Details
Demonstrate the SMART EHR Launch Sequence.
US Core v3.1.0 Profiles
Capability Statement - 5 tests - Show Details
Retrieve information about supported server functionality in the Capability Statement.
Patient Tests - 15 tests - Show Details
Verify that Patient resources on the FHIR server follow the US Core Implementation Guide
AllergyIntolerance Tests - 10 tests - Show Details
Verify that AllergyIntolerance resources on the FHIR server follow the US Core Implementation Guide
CarePlan Tests - 12 tests - Show Details
Verify that CarePlan resources on the FHIR server follow the US Core Implementation Guide
CareTeam Tests - 10 tests - Show Details
Verify that CareTeam resources on the FHIR server follow the US Core Implementation Guide
Condition Tests - 5/7 Required Tests Passed - 1/6 Optional Tests Passed - Show Details
Verify that Condition resources on the FHIR server follow the US Core Implementation Guide
Test Results
Inputs
HTTP Requests
About
USCC-01: Server rejects Condition search without authorization results...
USCC-02: Server returns expected results from Condition search by patient results...
Details: Invalid Condition: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition.code.coding[0]: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R51' Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category')
USCC-03: OPTIONAL | Server returns expected results from Condition search by patient+category results...
Details: Invalid Condition: Condition.code.coding[0]: Code "B99.9" not found; The code "B99.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B99.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#B99.9'
This optional test is not required for conformance.
USCC-04: OPTIONAL | Server returns expected results from Condition search by patient+onset-date results...
Details: onset-date on resource does not match onset-date requested
This optional test is not required for conformance.
USCC-05: OPTIONAL | Server returns expected results from Condition search by patient+clinical-status results...
Details: Invalid Condition: Condition.code.coding[0]: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#J00'
This optional test is not required for conformance.
USCC-06: OPTIONAL | Server returns expected results from Condition search by patient+code results...
USCC-07: Server returns correct Condition resource from Condition read interaction results...
USCC-08: OPTIONAL | Server returns correct Condition resource from Condition vread interaction results...
Details: FHIR::Condition version_id not returned
This optional test is not required for conformance.
USCC-09: OPTIONAL | Server returns correct Condition resource from Condition history interaction results...
Details: Bad response code: expected 200, 201, but found 404.
This optional test is not required for conformance.
USCC-10: Server returns Provenance resources from Condition search by patient + _revIncludes: Provenance:target results...
USCC-11: Condition resources returned conform to US Core R4 profiles results...
Details: Condition/P-52223: Condition.code: Code "R53.83" not found; The code "R53.83" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R53.83) is not valid in the value set USCoreConditionCode Condition/P-52223: Condition.code.coding[0]: Code "R53.83" not found; The code "R53.83" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R53.83) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R53.83' Condition/P-53112: Condition.code: Code "S69.90XA" not found; The code "S69.90XA" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#S69.90XA) is not valid in the value set USCoreConditionCode Condition/P-53112: Condition.code.coding[0]: Code "S69.90XA" not found; The code "S69.90XA" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#S69.90XA) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#S69.90XA' Condition/H-49906: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition/H-49906: Condition.code: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set USCoreConditionCode Condition/H-49906: Condition.code.coding[0]: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R51' Condition/H-49906: Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category') Condition/P-51402: Condition.code.coding[0]: Code "R05" not found; The code "R05" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R05) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R05' Condition/P-49946: Condition.code: Code "B99.9" not found; The code "B99.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B99.9) is not valid in the value set USCoreConditionCode Condition/P-49946: Condition.code.coding[0]: Code "B99.9" not found; The code "B99.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B99.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#B99.9' Condition/P-53137: Condition.code: Code "R09.89" not found; The code "R09.89" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R09.89) is not valid in the value set USCoreConditionCode Condition/P-53137: Condition.code.coding[0]: Code "R09.89" not found; The code "R09.89" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R09.89) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R09.89' Condition/H-53027: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition/H-53027: Condition.code: Code "R50.9" not found; The code "R50.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R50.9) is not valid in the value set USCoreConditionCode Condition/H-53027: Condition.code.coding[0]: Code "R50.9" not found; The code "R50.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R50.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R50.9' Condition/H-53027: Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category') Condition/P-52658: Condition.code: Code "B01.9" not found; The code "B01.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B01.9) is not valid in the value set USCoreConditionCode Condition/P-52658: Condition.code.coding[0]: Code "B01.9" not found; The code "B01.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B01.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#B01.9' Condition/P-51401: Condition.code.coding[0]: Code "R05" not found; The code "R05" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R05) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R05' Condition/P-50846: Condition.code: Code "H92.01" not found; The code "H92.01" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#H92.01) is not valid in the value set USCoreConditionCode Condition/P-50846: Condition.code.coding[0]: Code "H92.01" not found; The code "H92.01" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#H92.01) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#H92.01' Condition/P-53118: Condition.code: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set USCoreConditionCode Condition/P-53118: Condition.code.coding[0]: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#J00' Condition/P-51403: Condition.code: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set USCoreConditionCode Condition/P-51403: Condition.code.coding[0]: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#J00'
USCC-12: All must support elements are provided in the Condition resources returned. results...
USCC-13: Every reference within Condition resource is valid and can be read. results...
Implantable Device Tests - 10 tests - Show Details
Verify that Device resources on the FHIR server follow the US Core Implementation Guide
DiagnosticReport For Report And Note Exchange Tests - 14 tests - Show Details
Verify that DiagnosticReport resources on the FHIR server follow the US Core Implementation Guide
DiagnosticReport For Laboratory Results Reporting Tests - 14 tests - Show Details
Verify that DiagnosticReport resources on the FHIR server follow the US Core Implementation Guide
DocumentReference Tests - 16 tests - Show Details
Verify that DocumentReference resources on the FHIR server follow the US Core Implementation Guide
Encounter Tests - 3/9 Required Tests Passed - 0/6 Optional Tests Passed - Show Details
Verify that Encounter resources on the FHIR server follow the US Core Implementation Guide
Goal Tests - 11 tests - Show Details
Verify that Goal resources on the FHIR server follow the US Core Implementation Guide
Immunization Tests - 11 tests - Show Details
Verify that Immunization resources on the FHIR server follow the US Core Implementation Guide
MedicationRequest Tests - 14 tests - Show Details
Verify that MedicationRequest resources on the FHIR server follow the US Core Implementation Guide
Smoking Status Observation Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Pediatric Weight For Height Observation Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Laboratory Result Observation Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Pediatric BMI For Age Observation Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Pulse Oximetry Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Body Height Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Body Temperature Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Blood Pressure Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Body Weight Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Head Circumference Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Heart Rate Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Observation Respiratory Rate Tests - 13 tests - Show Details
Verify that Observation resources on the FHIR server follow the US Core Implementation Guide
Procedure Tests - 12 tests - Show Details
Verify that Procedure resources on the FHIR server follow the US Core Implementation Guide
Clinical Notes Guideline Tests - 10 tests - Show Details
Verify that DocumentReference and DiagnosticReport resources on the FHIR server follow the US Core R4 Clinical Notes Guideline
Location Tests - 6/8 Required Tests Passed - 0/5 Optional Tests Passed - Show Details
Verify that Location resources on the FHIR server follow the US Core Implementation Guide
Medication Tests - 6 tests - Show Details
Verify that Medication resources on the FHIR server follow the US Core Implementation Guide
!
Organization Tests - 7/8 Required Tests Passed - 0/2 Optional Tests Passed - Show Details
Verify that Organization resources on the FHIR server follow the US Core Implementation Guide
Practitioner Tests - 10 tests - Show Details
Verify that Practitioner resources on the FHIR server follow the US Core Implementation Guide
PractitionerRole Tests - 11 tests - Show Details
Verify that PractitionerRole resources on the FHIR server follow the US Core Implementation Guide
Provenance Tests - 6 tests - Show Details
Verify that Provenance resources on the FHIR server follow the US Core Implementation Guide
Test Result: Fail
×
USCC-11: Condition resources returned conform to US Core R4 profiles
This test checks if the resources returned from prior searches conform to the US Core profiles. This includes checking for missing data elements and valueset verification.
http://hl7.org/fhir/us/core/StructureDefinition/us-core-condition
Error Message: Condition/P-52223: Condition.code: Code "R53.83" not found; The code "R53.83" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R53.83) is not valid in the value set USCoreConditionCode Condition/P-52223: Condition.code.coding[0]: Code "R53.83" not found; The code "R53.83" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R53.83) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R53.83' Condition/P-53112: Condition.code: Code "S69.90XA" not found; The code "S69.90XA" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#S69.90XA) is not valid in the value set USCoreConditionCode Condition/P-53112: Condition.code.coding[0]: Code "S69.90XA" not found; The code "S69.90XA" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#S69.90XA) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#S69.90XA' Condition/H-49906: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition/H-49906: Condition.code: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set USCoreConditionCode Condition/H-49906: Condition.code.coding[0]: Code "R51" not found; The code "R51" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R51) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R51' Condition/H-49906: Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category') Condition/P-51402: Condition.code.coding[0]: Code "R05" not found; The code "R05" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R05) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R05' Condition/P-49946: Condition.code: Code "B99.9" not found; The code "B99.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B99.9) is not valid in the value set USCoreConditionCode Condition/P-49946: Condition.code.coding[0]: Code "B99.9" not found; The code "B99.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B99.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#B99.9' Condition/P-53137: Condition.code: Code "R09.89" not found; The code "R09.89" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R09.89) is not valid in the value set USCoreConditionCode Condition/P-53137: Condition.code.coding[0]: Code "R09.89" not found; The code "R09.89" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R09.89) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R09.89' Condition/H-53027: Condition.category[0].coding[0]: Coding.system must be an absolute reference, not a local reference Condition/H-53027: Condition.code: Code "R50.9" not found; The code "R50.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R50.9) is not valid in the value set USCoreConditionCode Condition/H-53027: Condition.code.coding[0]: Code "R50.9" not found; The code "R50.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R50.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R50.9' Condition/H-53027: Condition.category[0].coding[0].system: URI values cannot have whitespace(' http://hl7.org/fhir/us/core/CodeSystem/condition-category') Condition/P-52658: Condition.code: Code "B01.9" not found; The code "B01.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B01.9) is not valid in the value set USCoreConditionCode Condition/P-52658: Condition.code.coding[0]: Code "B01.9" not found; The code "B01.9" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#B01.9) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#B01.9' Condition/P-51401: Condition.code.coding[0]: Code "R05" not found; The code "R05" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#R05) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#R05' Condition/P-50846: Condition.code: Code "H92.01" not found; The code "H92.01" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#H92.01) is not valid in the value set USCoreConditionCode Condition/P-50846: Condition.code.coding[0]: Code "H92.01" not found; The code "H92.01" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#H92.01) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#H92.01' Condition/P-53118: Condition.code: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set USCoreConditionCode Condition/P-53118: Condition.code.coding[0]: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#J00' Condition/P-51403: Condition.code: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set USCoreConditionCode Condition/P-51403: Condition.code.coding[0]: Code "J00" not found; The code "J00" is not valid in the system http://hl7.org/fhir/sid/icd-10-cm; The code provided (http://hl7.org/fhir/sid/icd-10-cm#J00) is not valid in the value set All codes known to the system for 'http://hl7.org/fhir/sid/icd-10-cm#J00'
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.category[0]: None of the codes provided are in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category (http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category, and a code should come from this value set unless it has no suitable code) (codes = http://hl7.org/fhir/us/core/CodeSystem/condition-category#health-concern)
Condition.code: None of the codes provided are in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code (http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code, and a code should come from this value set unless it has no suitable code) (codes = http://hl7.org/fhir/sid/icd-10-cm#R05)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.category[0].coding[0]: Code System URI ' http://hl7.org/fhir/us/core/CodeSystem/condition-category' is unknown so the code cannot be validated
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0].coding[0]: Code System URI ' http://hl7.org/fhir/us/core/CodeSystem/condition-category' is unknown so the code cannot be validated
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.code: None of the codes provided are in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code (http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code, and a code should come from this value set unless it has no suitable code) (codes = http://hl7.org/fhir/sid/icd-10-cm#R05)
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.extension[2]: Unknown extension http://cpsi.reason.text
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.extension[0]: Unknown extension http://cpsi.problem-treated-this-visit
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.category[0]: None of the codes provided are in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category (http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category, and a code should come from this value set unless it has no suitable code) (codes = http://hl7.org/fhir/us/core/CodeSystem/condition-category#health-concern)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[1]: Unknown extension http://cpsi.reason.text
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.category[0]: Display Name for http://terminology.hl7.org/CodeSystem/condition-category#problem-list-item should be one of 'Problem List Item' instead of 'problem-list-item'
Condition.extension[0]: Unknown extension http://cpsi.reason.id
Condition.extension[1]: Unknown extension http://cpsi.reason.id
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
Condition.code: No code provided, and a code should be provided from the value set http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code (http://hl7.org/fhir/us/core/ValueSet/us-core-condition-code)
Condition.identifier[0].type: None of the codes provided are in the value set http://hl7.org/fhir/ValueSet/identifier-type (http://hl7.org/fhir/ValueSet/identifier-type, and a code should come from this value set unless it has no suitable code) (codes = http://terminology.hl7.org/CodeSystem/v2-0203#U)
16 Requests
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-52223
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-52263
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-53112
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/H-49906
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-51402
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-49947
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-49946
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-53137
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/H-53027
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-51401
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-52658
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-50846
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-53118
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-51403
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-49033
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition/P-51209
Part of the JSON:
Request
GET   200   https://rqhandler-dev.cpsi.com/primary/requesthandler/fhir/R4/Condition?patient=300
Headers
User-Agent: Ruby FHIR Client
Accept-Charset: utf-8
Accept: application/fhir+json
Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjI0NkVBOUEzODNDOTRFRUY5MDI0MDgzNDUyODdBNUE2NEI0Q0Q2RTgiLCJ4NXQiOiJKRzZwbzRQSlR1LVFKQWcwVW9lbHBrdE0xdWciLCJ0eXAiOiJKV1QifQ.eyJzdWIiOiJSYW5kb21fVmFsdWV8UmFuZG9tX1ZhbHVlIiwibmFtZSI6IkpvaG4gRG9lIiwiQ2xpZW50SUQiOiJHUkgiLCJBcHBsaWNhdGlvbklkIjoiMDc1NTYyYzAtZDBmYy00YmZhLTk0YTAtMjM1ZWU4NGQ4NDE4IiwibmJmIjoxNTkyMjU3NDg5LCJleHAiOjE1OTIyNjQ2ODksImlhdCI6MTU5MjI1NzQ4OSwiaXNzIjoiaHR0cHM6Ly9jZW50cmlxLXNoZWxsLmNoYmFzZS5jb20vIiwiYXVkIjoiaHR0cHM6Ly9ycWhhbmRsZXItZGV2LmNwc2kuY29tL3ByaW1hcnkvcmVxdWVzdGhhbmRsZXIvZmhpci9zdHUzLyJ9.kD8w4SoemcPAhgs2h_n7a47jmMZTAO7T7YJEp3PUtOcIqQGOHF48GtG2HKWwwSjCHMBOA4FOxDNnjf8ieOFfAfEuw7GeztclGpOtz9t1s7nF-TwNCMmrveIoreUjSRtWGmBIGJX7AXb7d8jSNDtebiLVEl-hBJRFCYYEMMiDSJTb2T5gGhE-D0Ev2d4pLnN5ASOK_5ChvtCk0Dydj2m7qxiqRLFlRj741SimZdud6-m6m1dlwcljfgyEqxPO5FaWIspaTyaj_5UWVXlBeO6shbktPQp4aKZurc4bl71tCrmtjCoKbSSSLYkO4r7I4e58A5qE_DpTnDgItffXdRXS_OzaZNiy10xAmaA9nEHvxI0HG5kfMuJCKkKRU13Vfkj0fXlWaNCa3RmbhaFUYrXNO4ucueukro7fSNXWnzseVjVR4h-7gSNholoYmB025VO9HxaWDTnni9AmvqTMLPFEl4b3EiV0cXXP24pbgWBVHuOeqJzKfDfLNZr2qfMU35-RD3PuMJrGdLVuQbUocohDt1sk_rR7excf6ab7z5Qw5FFpQdlg3DpRBk7SGKOOzhaeCa27Re88VM-qWfYB6q16AADJi80k-sH9LGwHeFTklCxSZiWo3QK4JRLsRMg2yVvXIjAabyjA-IXnczkvNHTkQIPGSVbNnh1aCRkSHxOJYn8
Response
Headers
date: Mon, 15 Jun 2020 21:45:02 GMT
content-type: application/json; charset=utf-8
server: envoy
x-envoy-upstream-service-time: 641
vary: Accept-Encoding
transfer-encoding: chunked
Body
{
"resourceType": "Bundle",
"total": 16,
"link": [
{
"relation": "self",
"url": "https://cvddevelop111.cpsi.com:5211/fhir/R4/Condition?patient=300"
}
],
"entry": [
{
"fullUrl": "https://cvddevelop111.cpsi.com:5211/fhir/R4/Condition/P-49033",
"resource": {
"resourceType": "Condition",
"id": "P-49033",
"identifier": [
{
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
"code": "U",
"display": "Unspecified identifier"
}
],
"text": "Medical_HistoryID"
},
"value": "P-49033",
"assigner": {
"reference": "Organization/2"
}
}
],
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-category",
"code": "problem-list-item",
"display": "problem-list-item"
}
],
"text": "problem-list-item"
}
],
"code": {
"coding": [
{
"system": "http://snomed.info/sct",
"code": "247234006",
"display": "Ear finding (finding)"
}
],
"text": "Ear finding (finding)"
},
"subject": {
"reference": "Patient/300"
},
"clinicalStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-clinical",
"code": "active"
}
]
},
"verificationStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
"code": "provisional"
}
]
},
"recordedDate": "2019-10-28T16:31:51.403-05:00",
"recorder": {
"reference": "Practitioner/2"
},
"asserter": {
"reference": "Practitioner/2"
},
"onsetString": "04/2015",
"extension": [
{
"url": "http://cpsi.reason.id",
"valueInteger": 23
},
{
"url": "http://cpsi.reason.text",
"valueString": "New information is available"
}
],
"meta": {
"lastUpdated": "2020-06-10T10:38:09.833-05:00"
}
}
},
{
"fullUrl": "https://cvddevelop111.cpsi.com:5211/fhir/R4/Condition/H-49906",
"resource": {
"resourceType": "Condition",
"id": "H-49906",
"identifier": [
{
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
"code": "U",
"display": "Unspecified identifier"
}
],
"text": "Medical_HistoryID"
},
"value": "H-49906",
"assigner": {
"reference": "Organization/2"
}
}
],
"category": [
{
"coding": [
{
"system": " http://hl7.org/fhir/us/core/CodeSystem/condition-category",
"code": "health-concern",
"display": "health-concern"
}
],
"text": "health-concern"
}
],
"code": {
"coding": [
{
"system": "http://hl7.org/fhir/sid/icd-10-cm",
"code": "R51",
"display": "Headache"
},
{
"system": "http://snomed.info/sct",
"code": "25064002",
"display": "Headache (finding)"
}
],
"text": "Headache (finding)"
},
"subject": {
"reference": "Patient/300"
},
"verificationStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
"code": "entered-in-error"
}
]
},
"recordedDate": "2020-01-02T16:13:31.477-06:00",
"recorder": {
"reference": "Practitioner/2"
},
"asserter": {
"reference": "Practitioner/2"
},
"onsetDateTime": "2020-04-06T00:00:00.000-05:00",
"extension": [
{
"url": "http://cpsi.problem-treated-this-visit",
"extension": [
{
"url": "1",
"valueReference": {
"reference": "Encounter/37360"
}
},
{
"url": "2",
"valueReference": {
"reference": "Encounter/37361"
}
}
]
},
{
"url": "http://cpsi.reason.id",
"valueInteger": 25
},
{
"url": "http://cpsi.reason.text",
"valueString": "Information entered in error (185981001)"
}
],
"meta": {
"lastUpdated": "2020-05-01T16:12:26.63-05:00"
}
}
},
{
"fullUrl": "https://cvddevelop111.cpsi.com:5211/fhir/R4/Condition/P-49946",
"resource": {
"resourceType": "Condition",
"id": "P-49946",
"identifier": [
{
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
"code": "U",
"display": "Unspecified identifier"
}
],
"text": "Medical_HistoryID"
},
"value": "P-49946",
"assigner": {
"reference": "Organization/2"
}
}
],
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-category",
"code": "problem-list-item",
"display": "problem-list-item"
}
],
"text": "problem-list-item"
}
],
"code": {
"coding": [
{
"system": "http://hl7.org/fhir/sid/icd-10-cm",
"code": "B99.9",
"display": "Unspecified infectious disease"
},
{
"system": "http://snomed.info/sct",
"code": "722892007",
"display": "Fever with infection"
}
],
"text": "Fever with infection"
},
"subject": {
"reference": "Patient/300"
},
"verificationStatus": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-ver-status",
"code": "entered-in-error"
}
]
},
"recordedDate": "2020-01-07T13:41:47.107-06:00",
"recorder": {
"reference": "Practitioner/2"
},
"asserter": {
"reference": "Practitioner/2"
},
"onsetDateTime": "2020-01-07T13:41:00.000-06:00",
"extension": [
{
"url": "http://cpsi.problem-treated-this-visit",
"extension": [
{
"url": "1",
"valueReference": {
"reference": "Encounter/37778"
}
}
]
},
{
"url": "http://cpsi.reason.id",
"valueInteger": 25
},
{
"url": "http://cpsi.reason.text",
"valueString": "Information entered in error (185981001)"
}
],
"meta": {
"lastUpdated": "2020-04-08T15:06:00.79-05:00"
}
}
},
{
"fullUrl": "https://cvddevelop111.cpsi.com:5211/fhir/R4/Condition/P-49947",
"resource": {
"resourceType": "Condition",
"id": "P-49947",
"identifier": [
{
"type": {
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/v2-0203",
"code": "U",
"display": "Unspecified identifier"
}
],
"text": "Medical_HistoryID"
},
"value": "P-49947",
"assigner": {
"reference": "Organization/2"
}
}
],
"category": [
{
"coding": [
{
"system": "http://terminology.hl7.org/CodeSystem/condition-category",
"code": "problem-list-item",
"display": "problem-list-item"
}
],
"text": "problem-list-item"
}
],
"code": {
"coding": [
{
"system": "http://hl7.org/fhir/sid/icd-10-cm",
"code": "M53.9",
"display": "Dorsopathy, unspecified"
},
{
"system": "http://snomed.info/sct",
"code": "302258001",
"display": "Back problem (finding)"
}

Hello healthland:
Thank you for submitting this. We have identified some issues in our terminology validation process. The team is working on fixing them.

Hello!
Thank you for the update.  We did find if we use this for the system: http://www.icd10data.com/icd10pcs  then it will pass on Inferno.
Please let us know if another system should be used.
Thank you!

You mentioned USCC test case in the original post. I think your intension is to validate Condition using US Core Condition profile. This profile has an extensible binding on Condition.code to US Core Condition Code ValueSet (https://www.hl7.org/fhir/us/core/ValueSet-us-core-condition-code.html). The value set contains codes from SNOMED-CT, ICD-10-CM, and ICD-9-CM. ICD-10-PCS is for clinical procedure. I don't think it fits in Condition resources.

Ok, so once the fix is done the  system, http://hl7.org/fhir/sid/icd-10-cm, should work?

This looks like it is working now.  Thank you!

This looks like it is working now.  Thank you!


Old Service Principal Credentials can still login after AKS SP is reset

How to reproduce the issue?

Create an AKS cluster on azure portal(let AKS creates a new SP automatically):

Follow the document https://docs.microsoft.com/en-us/azure/aks/update-credentials#reset-existing-service-principal-credential to reset the AKS cluster SP:
$ SP_ID=$(az aks show --resource-group myResourceGroup --name myAKSCluster --query servicePrincipalProfile.clientId -o tsv)
$ SP_SECRET=$(az ad sp credential reset --name $SP_ID --query password -o tsv)
$ az aks update-credentials --resource-group myResourceGroup --name myAKSCluster --reset-service-principal --service-principal $SP_ID --client-secret $SP_SECRET

Then I can still az login with the old SP credentials after the SP was reset successfully, and i can't delete this old password as i can't see this old one from my side.
This will cause security issues since the old SP password still works even after the SP is reset.

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

ID: a3f84bdc-9ed0-eb85-f3af-9711e8083a95
Version Independent ID: 03a47d06-5fbf-4764-0882-99cd8bd41110
Content: Use Azure service principals with Azure CLI
Content Source: docs-ref-conceptual/create-an-azure-service-principal-azure-cli.md
Service: azure-cli
GitHub Login: @dbradish-microsoft
Microsoft Alias: dbradish

@DreamRivulet Thanks for the question! We're investigating this and will get back to you shortly.

This is a known issue that az ad sp credential reset doesn't take effect immediately because AAD service needs some time to propagate.
@DreamRivulet, does the password expire eventually after several seconds (sometimes several minutes)?


Single app, Multiple User pools: App crashes when loading a new amplifyconfiguration.json

Describe the bug
My application has multiple tenants and it was designed to configure the Amplify with the user pool information of that particular tenant which the user belongs to.
The problem is that when the user signs out and tries to authenticate using  credentials of a user in different user pool the application crashes saying that the configure function was already performed.
Steps To Reproduce
Steps to reproduce the behavior:
1. Amplify.configure() using a valid amplifyconfiguration.json
2. Authenticate using a valid user of that User pool
3. Sign out
4. Amplify.configure() with a amplifyconfiguration.json of a different user pool
5. The app crashes

Expected behavior
I need to know how to unload a amplifyconfiguration.json in order to load a new file of a different User pool
Amplify Framework Version
1.5.5
Amplify Categories
Auth
Dependency manager
Cocoapods
Swift version
4.0
CLI version
4.41.2
Xcode version
12.5.1 (12E507)
Relevant log output
No response
Is this a regression? (i.e. was this working before a version upgrade)
No response
Device
iPad
iOS Version
14+
Specific to simulators
No response
Additional context
No response

Calling multiple configuration during runtime is not currently supported in Amplify iOS. Closing this as duplicate to this ticket - https://github.com/aws-amplify/amplify-ios/issues/527


feat: overrides uniformity accross all the categories

Rename "overrideProps" to "override"
Rename "props" parameter to "resources"
Remove "return props" requirement and test that it doesn't crash
"✔ Do you want to edit override.ts file now? (y/N)" should default to "true"
Support for: amplify build -> from amplify build-override
Changes are applied to all categories
use vm2 uniformly

Codecov Report

Merging #8695 (001f039) into extOverrides3 (dec20eb) will decrease coverage by 0.00%.
The diff coverage is 21.62%.

@@                Coverage Diff                @@
##           extOverrides3    #8695      +/-   ##
=================================================
- Coverage          56.32%   56.31%   -0.01%
=================================================
  Files                834      834
  Lines              47108    47122      +14
  Branches            9435     9435
=================================================
+ Hits               26532    26537       +5
- Misses             19758    19767       +9
  Partials             818      818

Impacted Files
Coverage Δ

...rmation/auth-stack-builder/auth-stack-transform.ts
83.22% <0.00%> (+0.51%)
:arrow_up:

...h-stack-builder/user-pool-group-stack-transform.ts
85.71% <0.00%> (+1.00%)
:arrow_up:

...c/overrides-manager/override-skeleton-generator.ts
19.23% <0.00%> (ø)

...ion/src/root-stack-builder/root-stack-transform.ts
79.72% <0.00%> (+1.06%)
:arrow_up:

...dformation/cdk-stack-builder/s3-stack-transform.ts
10.29% <12.50%> (+0.84%)
:arrow_up:

...formation/cdk-stack-builder/ddb-stack-transform.ts
78.04% <31.25%> (-4.39%)
:arrow_down:

packages/amplify-cli/src/commands/build.ts
87.09% <100.00%> (ø)

Continue to review full report at Codecov.

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


Cannot create playlists in Radiant

I have to use the web browser or my phone in order to create playlists. If I try to do it in Radiant the playlist never shows up.

Originally, the reason behind this was Google's poor support for Safari (which powers Radiant).
I've just spotted that it seems to be letting me create them now, and I've added a few tracks, so I'm guessing Google have resolved the issue at their end.


Adding Hub Collaborator

My username is @MinWu859. @ebeshero please add me as a collaborator to this DHClass-Hub.

@MinWu859 I've sent you an invitation to join the repo! Please check your email to accept the invitation. :-)


doc: deploy crate docs to GitHub pages

Which issue does this PR close?

Closes #.
Rationale for this change
arrow-rs has so many crates. We often need to browse the doc for more than one crates. But on doc.rs, we can't go to other crates conveniently.

Deploying to GitHub pages can improve the situation

See it on my fork: https://xxchan.github.io/arrow-rs
https://github.com/xxchan/arrow-rs/actions/workflows/docs.yml

What changes are included in this PR?

Are there any user-facing changes?

Another strategy that is used for other arrow projects is to publish the apache site (e.g. https://arrow.apache.org/datafusion/)
This is described in https://github.com/apache/arrow-datafusion/tree/main/docs#release-process
I would be happy to help figure out how to make the process work here as well

Thank you @xxchan  -- this is very helpful.

Let's merge this and see how it works

Maybe we need to update asf.yaml

Yes, I think we need to do the same thing as in DataFusion
@xxchan would it be possible for you to look into doing so? Aka what is described in https://github.com/apache/arrow-rs/pull/4436#issuecomment-1598815865?
If you don't have time that is also fine, I can revert this change and we can work on it when we do have time

There is a ASF INFRA doc, but I have no access to the wiki
https://infra.apache.org/github-pages.html
On Mon, 26 Jun 2023 at 21:20, Andrew Lamb @.***> wrote:

Yes, I think we need to do the same thing as in DataFusion
@xxchan https://github.com/xxchan would it be possible for you to look
into doing so? Aka what is described in #4436 (comment)
https://github.com/apache/arrow-rs/pull/4436#issuecomment-1598815865?
If you don't have time that is also fine, I can revert this change and we
can work on it when we do have time
—
Reply to this email directly, view it on GitHub
https://github.com/apache/arrow-rs/pull/4436#issuecomment-1608094705,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBQZNII6SHTXLAGJENX3I3XNHOJPANCNFSM6AAAAAAZMLSSII
.
You are receiving this because you were mentioned.Message ID:
@.***>

@martin-g  did the work in DataFusion via https://github.com/apache/arrow-datafusion/pull/5670 -- maybe that is enough?


App crashes on barcode-scan with VIBRATE-setting enabled

Hi there,
it seems that zxing-android-embedded has silently dropped support for its vibrate-setting?
I got this crash when scanning a barcode with vibrate enabled:
java.lang.SecurityException: Requires VIBRATE permission
    at android.os.Parcel.readException(Parcel.java:1546)
    at android.os.Parcel.readException(Parcel.java:1499)
    at android.os.IVibratorService$Stub$Proxy.vibrateMagnitude(IVibratorService.java:307)
    at android.os.SystemVibrator.vibrate(SystemVibrator.java:119)
    at android.os.SystemVibrator.vibrate(SystemVibrator.java:84)
    at android.os.Vibrator.vibrate(Vibrator.java:89)
    at android.os.Vibrator.vibrate(Vibrator.java:71)
    at com.google.zxing.client.android.BeepManager.playBeepSoundAndVibrate(SourceFile:72)
    at com.google.zxing.client.android.CaptureActivity.handleDecode(SourceFile:442)
    at com.google.zxing.client.android.CaptureActivityHandler.handleMessage(SourceFile:97)
    at android.os.Handler.dispatchMessage(Handler.java:102)
    at android.os.Looper.loop(Looper.java:145)
    at android.app.ActivityThread.main(ActivityThread.java:6837)
    at java.lang.reflect.Method.invoke(Native Method)
    at java.lang.reflect.Method.invoke(Method.java:372)
    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1404)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1199)

The commits that removed the vibrate-permission (among other permissions) are:
commit 354f209871d1aec61836e43f5f1314391eab1039
Author: Ralf Kistner<EMAIL_ADDRESS>Date:   Fri Mar 20 09:46:33 2015 +0200

    Trim manifest of legacy lib.

commit e7b16bc3fea77078ed453889a0c4698a24c42058
Author: Ralf Kistner<EMAIL_ADDRESS>Date:   Thu Mar 19 17:43:22 2015 +0200

    Manually update manifest.

commit 213a1a2ecac422c705edb5065c637bb8b37ea337
Author: Ralf Kistner<EMAIL_ADDRESS>Date:   Thu Mar 19 17:41:02 2015 +0200

    Update zxing-android-complete to 3.2.0.

Why were those permissions removed but not the code that needs them (at least in the vibrate-case)?

It's removed since vibrate is disabled by default, so most apps don't use it, and don't want the extra permission. You can just add the permission yourself if you need the vibrate functionality.
Either way the 2.x branch of the library is not actively supported anymore.


Update to SF 6.4

Hello,
I just updated and add 2 new releases.
One up to symfony 6.4 without breaking installations on symfony 6.3 compatiblity.
And another one compatible with symfony 7.
I'm waiting for quillJS to relases its 2.0 to do a major update with quillJS 2.0 compatiblity.
Thanks again.


Switch to float value to matrices when possible.

(See #83 for info on win Azure Pipelines failure. Tests pass on local windows machine.)


Fix invalid json (typo)

I'm not sure how this got in there, thanks!

@NoelDavies this is a result of the lack of CI (#9) .

Couldn't agree more mate.

Released in v1.0.2


(fix): export the CERT_MGR_VERSION env var for releasing

Description

Update the Makefile to export the CERT_MGR_VERSION environment variable when releasing

Motivation

fix the problem encountered when trying to cut the v0.1.0 release: https://github.com/operator-framework/catalogd/actions/runs/4757675157/jobs/8454773378#step:7:257

but also wondering what the reason is for not exporting them in one place up above like we have here?

No particular reason - I think we put them where they are since they are only used for the release process so at the time it made sense to keep them near the release target. We can move them in a follow-up if we want to be more consistent with what operator-controller is doing.


Announce Reproducible Research Lunch chats

We can include the reproducible research drop-in session in the next Turing bulletin.....we just need a paragraph.
I'll write one now....

Done for October 2019 too! Closing now.


tests:update testcases

Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.

[Experimental Bot, please feedback here]
Fill In The Commit Message: This PR contains a Commit with an Empty Commit Message. Please fill in the Commit Message with the PR Summary.
This PR template itself meets the NuttX requirements by providing a clear structure for contributors to document their changes thoroughly.  It explicitly asks for all the information required by the NuttX guidelines, covering the summary, impact, and testing aspects.  However, a PR using this template will only meet the requirements if the user fills out all sections completely and accurately.  The placeholder text in the second half of the template emphasizes this need for user-provided information.

@ttnie please fix the style issue:
https://github.com/apache/nuttx/actions/runs/12391974530/job/34590172311?pr=15262


Migration to TF2 and new version 0.3

This is a migration of DeLFT to TensorFlow 2.7 and associated Keras, see #87. This is a new DeLFT version, which is significantly rewritten to achieve the migration and it adds several new features.
Removed:

ELMo embeddings, because there is no TF2 implementation afaik (which closes #6)
custom integration of BERT based on the original Google implementation

Added:

usage of HuggingFace transformer library to integrate transformers as Keras layers (for both text classification and sequence labeling). This allows to load a variety of pre-trained models in the same architecture having a transformer layer. For the moment BERT layers are supported for all pretrained BERT models, but it's easy to add others like RoBERTa. It also adds a lot of new possibilities for training (optimizers, custom loss, early stop for BERT fine-tuned stuff), for creating easily new models, training supports callbacks (#96).
usage of the Chain CRF Keras layer (also migrated to TF2) for all architectures, with sparse and hot-one encoding of labels and masked loss function
on top of the existing updated architectures, addition of new architectures for sequence labelling: BERT_CRF with input features channel (BERT_CRF_FEATURES) and BERT_CRF with character input channel (BERT_CRF_CHAR and BERT_CRF_CHAR_FEATURES)
usage of optimizer with learning rate decay
move the documentation to readthedoc https://delft.readthedocs.io/en/tf2/
include the task scripts in a directory delft/applications inside the library (#36)
rename embedding-registry.json to resources-registry.json and move it to the library (under delft/) too
side effect: also solve #80,  #79

Work in progress:

update documentation for new parameters and add new benchmarking
more tests, better error/exceptions
retrain RNN models (they are still super small, so they can be shipped with the github repo)
possibility to load pre-trained transformers locally (now they are fetched from huggingface hub only)
review how resource/embeddings registry file is used and where to upload larger DeLFT trained models with transformer layers
explore a way not to rely too much on a private commercial service for managing models

Other:

without any runtime consideration in the migration yet, we have a bit of runtime improvement as compared to the previous custom integration apparently: around 6500 tokens/s versus 5000 tokens/s with BERT-CRF sequence labeling for CoNLL 2003 NER

On Mac OSx I tested using python 3.9 and I could not build numpy for some obscure reason perhaps related to macOs stuff... it works with python 3.8.


update hreflang locale validation

Fixes #193
Re-commit of the core changes in https://github.com/ultrabug/mkdocs-static-i18n/pull/197 with a few minor additions (removal of unused variables, warning message update).
Co-authored-by: @jonaharagon Jonah Aragon<EMAIL_ADDRESS>Co-authored-by: Hugo Slepicka<EMAIL_ADDRESS>

Thank you


Throws error when hovering over elements with transparency

Expected behavior
No errors.
Actual behavior
Throws "Error: Parts is null" in browser console everytime I hover over a transparent element. The issue is solved when Fontanello is disabled.
Steps to reproduce the problem

Create an element with transparency value less than 1 (Eg. below)
.demo {"background:rgba(0,0,0, 0.99);  width:100px; height:100px;"}
Hover over it
Browser console throws an error each time you hover.
Screenshot:

Specifications

Version: 1.2.1
OS: Windows 10
Browser: Firefox 88.0

Thanks for your bug report!
It looks like this issue came with the release of Firefox 88. I'll look into it and let you know when a fix is out.

@Ertan9 this issue should be resolved in version 1.2.2 which is available for download. Please let me know if you experience any other issues!


Update Node.js Callendar

Update Node.js Callendar with Mentorship Meetings.
@nodejs/community-committee

Event: Every Friday 09am to 10am LA Time;
Attendees<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Join url: https://davidguttman.github.io/mentorship/meeting

FWIW @davidguttman it would be awesome to see a proposal for that meeting linking structure within the project itself :)

Done.

Thanks @bnb


Library not loaded...

Hi,
I am trying to link the nmssh-framework to my osx app, but I get the following error message. Does anyone have any idea, what it could be?
I build the nmssh-framework for 64 bit, no problems.
I added it as well as describe.
dyld: Library not loaded: @executable_path/../Frameworks/NMSSH.framework/Versions/A/NMSSH
Referenced from: /Users/necat/Develop/OSX/PhotoIptcEdit/build/Debug/Photoiptcedit.app/Contents/MacOS/Photoiptcedit
Reason: image not found
thanks for help,
regards necat

It did not work for me :(

I have the same issue
dyld: Library not loaded: @rpath/NMSSH.framework/NMSSH
  Referenced from: /Users/manuelfritsch/Library/Developer/CoreSimulator/Devices/02C3DCBE-6EDA-4FF5-A1E5-B20E439EBDFE/data/Containers/Bundle/Application/3B53C782-44D8-40FB-9DB9-0D52DF233CCB/CraftBeerPi.app/CraftBeerPi
  Reason: image not found
(lldb)

Manuel: click the + in Copy files and add NMSSH.framework


Remove Leigh as an alternative name to Higher Leigh

Leigh has been entered in the Gazetteer as an alternative to Higher Leigh. There are several places that contain the name Leigh in Somerset.
Can we please move the search links from Leigh. The best option is to attach them to Higher Leigh as we have no easy way of identifying where they belong.
Can Leigh then be removed from the Gazetteer, please.
Geoff

Done


Query improvements

In unit tests, generated queries are wrapped in QueryableOnce, to ensure that DataSourceLoader never executes a query repeatedly.

Query execution is delayed as much as possible.

1 & 2 together guarantee (provided good test coverage) that GroupHelper, AggregateCalculator and RemoteGroupTransformer don't involve multiple enumerations, except special cases when explicit EnsureBuffered call is required.

The use of ExpressionWatcher moved to a more appropriate place.

:shipit:


Create tool to show "stale" APIs

These are APIs where there have been commits since to prod code
other than the project file, since the last release
Start of current output (API ID, last release date, last release version, unreleased changes):
Google.Analytics.Data.V1Alpha                      2020-08-18: 1.0.0-alpha01 + 1 change
Google.Cloud.AutoML.V1                             2020-03-17: 2.0.0 + 4 changes
Google.Cloud.BigQuery.Connection.V1                2020-07-06: 1.0.0 + 3 changes
Google.Cloud.BigQuery.DataTransfer.V1              2020-03-17: 2.0.0 + 5 changes
Google.Cloud.BigQuery.Reservation.V1               2020-07-06: 1.0.0 + 2 changes
Google.Cloud.BigQuery.V2                           2020-06-04: 2.0.0 + 1 change
Google.Cloud.BigQuery.Storage.V1                   2020-03-17: 2.0.0 + 4 changes
Google.Cloud.Bigtable.Admin.V2                     2020-05-05: 2.1.0 + 4 changes
Google.Cloud.Bigtable.V2                           2020-04-08: 2.0.0 + 5 changes

In other news, we could do with re-releasing everything :)
Many of these have only changed due to generator changes, e.g. filling in the service method documentation or timeouts, or even just API comment changes. So those could be just patch releases.

In other news, we could do with re-releasing everything :)
Many of these have only changed due to generator changes, e.g. filling in the service method documentation or timeouts, or even just API comment changes. So those could be just patch releases.

And also to pick up some of the changes in GAX anf gRPC re quota project. But releasing everything right now is going to be a party. I'm still on in though.

If we change the dependencies by a minor version, we should bump the API package minor version as well. I think we probably want to start upgrade the dependencies automatically, possibly in set-version / increment-version. Let's think about that next week :)


refactor the output of hpargparse with rich

I refactor the output of hpargparse with rich.
--hp-list json:

--hp-list yaml:

--hp-detail / --hp-list detail:

There seem some typesetting problems:

Codecov Report

Merging #11 into master will increase coverage by 0.17%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
+ Coverage   95.16%   95.33%   +0.17%
==========================================
  Files           4        4
  Lines         186      193       +7
==========================================
+ Hits          177      184       +7
  Misses          9        9

Impacted Files
Coverage Δ

hpargparse/hputils.py
95.18% <100.00%> (+0.18%)
:arrow_up:

Continue to review full report at Codecov.

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

the typesetting problems are fixed.


Chromium version support clarification

What does this mean?

Important
Unified Service Desk version <IP_ADDRESS>9 supports Chromium version 84.
Unified Service Desk version <IP_ADDRESS>7 supports Chromium version 71.

Do the USD versions only support the mentioned version of Chromium or this version and all above?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 93f3b5ae-8caf-79a5-82a2-0b3a9b060312
Version Independent ID: b2899114-ee3e-d6a7-7326-b9c0181f46d3
Content: Use the Chrome Process hosting method for your controls in Unified Service Desk
Content Source: ce/unified-service-desk/chrome-process.md
Service: dynamics-365-customerservice
GitHub Login: @mh-jaya
Microsoft Alias: v-jmh

Hello,
Reg the following content, the specified USD versions support the specific Chromium version only.
Unified Service Desk version <IP_ADDRESS>9 supports Chromium version 84.
Unified Service Desk version <IP_ADDRESS>7 supports Chromium version 71.
Thanks,
Jaya


virtual scroll with dynamic data cuts off

In my virtual scroll the items stop rendering when I have scrolled down after a few hundred pixels.
The items are generated dynamically on a 500ms interval
export class Infinite extends Component {
  constructor(props) {
    super(props);
  }

  state = {
    items: [{id:1}]
  }
  componentDidMount() {
    setInterval(() => {
      var items = this.state.items;
      items.push({id:items.length + 1});
      this.setState({items:items})
    }, 500)
  }

  render () {
    var list = this.state.items
    return (
      <VirtualScroll
        ref="virtualScroll"
        width={300}
        height={300}
        rowsCount={list.length}
        rowHeight={20}
        className="virtualScroll"
        rowRenderer={
          index => {return(
{list[index].id}
)}
        }
      />

    )
  }
}

Hi @shakdoesgithub,
Please provide me with a test case that reproduces your problem. As it is my best guess is that you forgot to require/import the react-virtualized/styles CSS required for positioning of windowed cells.

@bvaughn that might be it. Where is that CSS at? I guess that's where the confusion is.

The examples in the docs should all show it (if not please let me know) but you can require it like so:
import { VirtualScroll } from 'react-virtualized';
import 'react-virtualized/styles.css'; // only needs to be imported once

I'm going to mark this issue as closed for now because I'm pretty sure that's the cause. If not we can still keep talking on this ticket. :)

I'm having this issue too — basically I can't scroll beyond around 40-60 items on a 500px by 500px list view (VirtualScroll). Is it possible to just include the react-virtualized/styles.css as the src to a


updating ajs-integration

Current coverage is 100% (diff: 100%)

Merging #5 into master will not change coverage

@@           master    #5   diff @@
===================================
  Files           1     1
  Lines          28    28
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           28    28
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 3a2b027...6476610


starte17 fails when included in enter-chroot command

Please paste the output of the following command here: sudo edit-chroot -all

name: trusty
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/trusty...
crouton: version 1-20160518095657~master:fd37bb79
release: trusty
architecture: amd64
xmethod: xiwi
targets: gtk-extra,e17,gnome,xiwi,xfce
host: version 7978.74.0 (Official Build) stable-channel candy
kernel: Linux localhost 3.10.18 #1 SMP Thu May 12 00:50:00 PDT 2016 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Please describe your issue:
chronos@localhost / $ sudo enter-chroot -n trusty starte17
Entering /mnt/stateful_partition/crouton/chroots/trusty...
-su: 1: starte17: not found

sudo enter-chroot -n trusty startgnome || startxfce4
work as expected.
Enlightenment can be started by running the wrapper script directly:
sudo /usr/local/bin/starte17
If known, describe the steps to reproduce the issue:

It's in the host-bin not the chroot-bin so, from crosh, just use: sudo starte17 -n trusty
It will, in turn run xinit /usr/bin/enlightenment_start in the chroot shell.

Thanks Dennis. Turns out the bug was in the user!

Happens to all of us - especially me! :+1:


11.1.0-beta1 breaks app near startup on Android Emulator

Describe the bug
Upgrading from 11.0.7 to 11.1.0-beta1 causes my app to crash. The last lines in the debug output window are:
[monodroid-assembly] open_from_bundles: failed to load assembly Nerdbank.Bitcoin.dll
Loaded assembly: /data/data/com.Nerdbank.eZcash.App/files/.__override__/Nerdbank.Bitcoin.dll
Resolved pending breakpoint at 'ImportAccountViewModel.cs:62,1' to void Nerdbank.Zcash.App.ViewModels.ImportAccountViewModel.set_Key (string value) [0x00000].
Resolved pending breakpoint at 'ImportAccountViewModel.cs:129,1' to void Nerdbank.Zcash.App.ViewModels.ImportAccountViewModel.set_BirthdayHeight (ulong value) [0x00000].
[bank.eZcash.App] Explicit concurrent copying GC freed 6495(355KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 3229KB/6458KB, paused 358us,61us total 8.818ms
[libc] Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7ec769f4b000 in tid 7332 (bank.eZcash.App), pid 7332 (bank.eZcash.App)

To Reproduce
The repro app in question isn't open source, and I don't know what element about it causes the crash. Any suggestions?
Expected behavior
No crash
Avalonia version
11.1.0-beta1
OS
No response
Additional context
No response

Are there any useful stacktraces in logcat maybe?
Also, you can try to listen for AndroidEnvironment.UnhandledExceptionRaiser (android specific) or Dispatcher.UnhandledExceptions (avalonia specific).

Neither of the event handlers you suggested I add were invoked for this crash. But thanks for them anyway as I'm sure they'll be useful to keep an eye on.
Here is my logcat log:
logcat.txt
You may find logs relevant to my app by searching for nerdbank.
Here are some potentially interesting ones, though more logs follow it, so I don't know if this represents the actual crash:
03-16 10:07:22.062	pixel_5_-_api_33_more_ram	Error	293	tombstoned	Tombstone written to: tombstone_06
03-16 10:07:22.051	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	backtrace:
      #00 pc<PHONE_NUMBER>1e54d8  /data/app/~~kpBhPwtif7hxBmDu1mfrtQ==/com.Nerdbank.eZcash.App-F4mi8cmm2tG0hUAgDIRikg==/lib/x86_64/libmonosgen-2.0.so (BuildId: 3ba63d5dff93e8a5b8060abc931774c8e0eb59ae)
      #01 pc<PHONE_NUMBER>1e9809  /data/app/~~kpBhPwtif7hxBmDu1mfrtQ==/com.Nerdbank.eZcash.App-F4mi8cmm2tG0hUAgDIRikg==/lib/x86_64/libmonosgen-2.0.so (BuildId: 3ba63d5dff93e8a5b8060abc931774c8e0eb59ae)
      #02 pc<PHONE_NUMBER>1ea30e  /data/app/~~kpBhPwtif7hxBmDu1mfrtQ==/com.Nerdbank.eZcash.App-F4mi8cmm2tG0hUAgDIRikg==/lib/x86_64/libmonosgen-2.0.so (BuildId: 3ba63d5dff93e8a5b8060abc931774c8e0eb59ae)
      #03 pc<PHONE_NUMBER>00e035  <anonymous:4134e000>
03-16 10:07:22.048	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x00007ec7689b1000
    rax 00007ec7689a1000  rbx 00007ec962495b18  rcx<PHONE_NUMBER>000059  rdx<PHONE_NUMBER>00ffff
    r8  00007ec7689a0f70  r9  00007ec962495b1a  r10 00007ec9614159e0  r11<PHONE_NUMBER>000000
    r12 00007ec7689a1000  r13 00007ffcc53aca60  r14 00007ec7689a1000  r15 00007ec84f4d66d8
    rdi 00007ec7689a1020  rsi<PHONE_NUMBER>000000
    rbp 00007ffcc5424b80  rsp 00007ffcc53aca00  rip 00007ec76b46a4d8
03-16 10:07:22.048	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	uid: 10169
03-16 10:07:22.047	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	pid: 27946, tid: 27946, name: bank.eZcash.App  >>> com.Nerdbank.eZcash.App <<<
03-16 10:07:22.047	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	Cmdline: com.Nerdbank.eZcash.App
03-16 10:07:22.047	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	Process uptime: 31s
03-16 10:07:22.047	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	Timestamp: 2024-03-16 10:07:21.809750700-0600
03-16 10:07:22.046	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	ABI: 'x86_64'
03-16 10:07:22.046	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	Revision: '0'
03-16 10:07:22.046	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	Build fingerprint: 'google/sdk_gphone_x86_64/emu64xa:13/TE1A.220922.034/10940250:userdebug/dev-keys'
03-16 10:07:22.046	pixel_5_-_api_33_more_ram	Error	28109	DEBUG	*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
03-15 22:20:10.153	pixel_5_-_api_33_more_ram	Info	0	logd	logdr: UID=10169 GID=10169 PID=28109 n tail=0 logMask=1 pid=27946 start=0ns deadline=0ns
03-15 22:20:10.148	pixel_5_-_api_33_more_ram	Info	0	logd	logdr: UID=10169 GID=10169 PID=28109 n tail=0 logMask=8 pid=27946 start=0ns deadline=0ns
03-16 10:07:21.804	pixel_5_-_api_33_more_ram	Info	28109	crash_dump64	performing dump of process 27946 (target tid = 27946)
03-16 10:07:21.803	pixel_5_-_api_33_more_ram	Info	293	tombstoned	received crash request for pid 27946
03-16 10:07:21.801	pixel_5_-_api_33_more_ram	Info	28109	crash_dump64	obtaining output fd from tombstoned, type: kDebuggerdTombstoneProto
03-16 10:07:21.743	pixel_5_-_api_33_more_ram	Debug	788	EGL_emulation	app_time_stats: avg=796.94ms min=2.15ms max=6647.32ms count=9
03-16 10:07:21.732	pixel_5_-_api_33_more_ram	Error	27946	libc	Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x7ec7689b1000 in tid 27946 (bank.eZcash.App), pid 27946 (bank.eZcash.App)
03-16 10:07:21.701	pixel_5_-_api_33_more_ram	Info	27946	bank.eZcash.App	Explicit concurrent copying GC freed 14237(835KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 3242KB/6484KB, paused 423us,65us total 9.001ms

I've faced the same issue with Android Emulator ...
@maxkatz6 For me issue happens for Android SDK API 35, all older version like API 32, 33, 34 looks like works fine

I'm on 11.1.0-rc2 now and it works fine for me. But I'm using Android API 34.
Feel free to close, or keep open for @redradist's sake.

@redradist which Avalonia version do you use?

@redradist which Avalonia version do you use?

Version 11.1.1


Round-tripping a data frame with >1000 columns is unexpectedly slow or even fails

Environment
Delta-rs version: 0.10.1
Binding:  Python
Environment:

OS: macOS 13.3 / Apple M2 Pro

Bug
What happened:
When evaluating delta-rs as a replacement for hand-managed Parquet files, I noticed that reading files with some thousand columns is unbearably slow. The number of rows does not matter; the issue can be reproduced with a single row.
The runtime does not increase linearly. See the listing below.
Reading the created Parquet file directly does not have any performance issues.
What you expected to happen:
The reading performance should not massively degrade when the number of columns increases.
How to reproduce it:
An absolutely naive script, writing and reading back a frame with a single row.
import sys
import time

import numpy as np
import pandas as pd
from deltalake import DeltaTable
from deltalake.writer import write_deltalake

column_count = int(sys.argv[1])

df = pd.DataFrame(np.zeros((1, column_count)), columns=(str(i) for i in range(column_count)))

write_deltalake("delta.table", df)

dt = DeltaTable("delta.table")

start_time = time.perf_counter()

df_in = dt.to_pandas()

print(f"Needed {round(time.perf_counter() - start_time, 2)}s to read {column_count} rows.")

More details:
Needed 0.01s to read 100 rows.
Needed 0.06s to read 200 rows.
Needed 0.16s to read 300 rows.
Needed 0.34s to read 400 rows.
Needed 0.62s to read 500 rows.
Needed 1.04s to read 600 rows.
Needed 1.71s to read 700 rows.
Needed 2.41s to read 800 rows.
Needed 3.35s to read 900 rows.
Needed 4.57s to read 1000 rows.
Needed 8.74s to read 1250 rows.
Needed 15.05s to read 1500 rows.

~2000 rows did not finish within several minutes.~ Do not succeed at all, the process crashed with SIGBUS.
Snakeviz profile:

I tried with the below specs and performance is ok:

Ubuntu 22.04
deltalake version 0.15.3

Needed 0.01s to read 100 rows.
Needed 0.02s to read 200 rows.
Needed 0.02s to read 300 rows.
Needed 0.03s to read 400 rows.
Needed 0.03s to read 500 rows.
Needed 0.05s to read 600 rows.
Needed 0.05s to read 700 rows.
Needed 0.05s to read 800 rows.
Needed 0.06s to read 900 rows.
Needed 0.08s to read 1000 rows.
Needed 0.1s to read 1250 rows.
Needed 0.11s to read 1500 rows.

@ylashin thanks! Closing this then as resolved


Add functionality to indicate the map center

it would be useful (e.g. for #727, #730) to have a shortcut or an option in the debug modal to show a cross or something else indicating the map center.

Options

A little + in the middle of the map — might get confused with another map symbol
Lines running vertically/horizontally across the entire map — might get confused with tile boundaries

I guess we could mitigate against the confusion by placing a semi-transparent layer above the map then place the center marker on top of that.
Thoughts?

I don't think there will be much confusion because the user would switch the center "marker" intentionally on/off, but a semi-transparent layer is a good idea (if the map content is still visible enough :-)).
I would prefer

A little + in the middle of the map

Maybe black with a white outline so it would be visible both on light and dark maps.


[bug]Rooch Node Shutdown: OOM caused by querying large number of high memory usage Objects

Proposal Details
The original report https://github.com/rooch-network/rooch/security/advisories/GHSA-q7jw-699g-rrxf
The bug is fixed in #2694 #2698 #2701
Please help check status @m4sterchain

After the report is published, I can not reply to the report, so I am creating a new issue.


Case-insensitive option?

Needs an additional parameter to control case-insensitive comparison.

Added in f0f0f2903a726675471575f09f54ff80dac7d71d.


More ipv6 tests to increase coverage

These increase coverage by one (different) condition in two of my implementations (one is a linear scan, the other is mixed regex-based).
trailing 4 hex symbols is valid is added just as something to compare against.

Thanks!


[Doc Improvement][JavaScript Test]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-gs-javascript.yml
91
40
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit d46ed63:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-gs-javascript.yml
91
40
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2948971:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/sbs-gs-javascript.yml
91
40
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/resources/schema/manifest-schema.md
92
25
link
:white_check_mark:

msteams-platform/sbs-gs-javascript.yml
91
40
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 2057580:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/resources/schema/manifest-schema.md
:white_check_mark:Succeeded
View

msteams-platform/sbs-gs-javascript.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

This was a test PR.


Miscellaneous cleanups:

Clarify use of cancel view in OfferCreate transactor
Reduce OfferStream public interface
Reduce severity of some developer-only logging from ERROR to DEBUG

@vinniefalco, @ximinez

Suggested:
Tidy up offer crossing
:+1:

Travis failure is not spurious: https://travis-ci.org/ripple/rippled/jobs/71452166
It also fails in Windows for the same reason.

Other than the problem with JLOG, the changes look good.

Yeah, I forgot the header. Will fix.

Can you please improve JLOG, using the structure of WriteLog, in a separate commit?

Yep

@HowardHinnant is JLOG good now?

Ditto on @HowardHinnant's failure.

Bah, I again missed adding the right header file. One second.

Build works now. :+1:

Builds with no warnings.  Passes unittest and npm.  I've been up for 10min without sync (release + assert).  I'll give it a few more minutes, then stop and try again with a clear db...

Had trouble shutting it down.  Appeared to hang with 20 threads, and 2% cpu usage for about 4min.  Force-quit it.

Sync'd and stopped after clearing the db.


Possible User Error: Using getMyLocation offline on Android

Hello, I've done some research on this issue to no avail. When using the "getMyLocation" function offline (wifi/cellular data off) on Android it throws the following error:
{
"status": "false",
"error_code":"service_not_available",
"error_message": "This app has been rejected to use Location Services."
}
I'm not sure what's "rejected" my app, whether it's because it can't reach Google's servers or if the issue is local. Turning data back on and it works like a charm.
Is this normal? Is there a workaround?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/26624961-possible-user-error-using-getmylocation-offline-on-android?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F637500&utm_medium=issues&utm_source=github).

Please use Cordovas Geolocation plugin, it's much more stable and updated.


[Bug]: Segmentation fault error when running cargo shuttle

What happened?
After successful installation of shuttle with command cargo install shuttle any attempt to run cargo shuttle ends with status -1 without additional logs.
e63906bf469a:/workspaces$ cargo shuttle login
Segmentation fault

Using strace to explore the issue I see this:
execve("/usr/local/cargo/bin/cargo-shuttle", ["/usr/local/cargo/bin/cargo-shutt"...], 0x7fffd9600720 /* 47 vars */) = 0
mmap(NULL, 1240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f6eda7e3000
arch_prctl(ARCH_SET_FS, 0x7f6eda7e33f8) = 0
set_tid_address(0x7f6edbbb6c60)         = 17793
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=NULL} ---
+++ killed by SIGSEGV +++

and with valgrind:
==20295== Memcheck, a memory error detector
==20295== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==20295== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info
==20295== Command: /usr/local/cargo/bin/cargo-shuttle
==20295==
==20295== Jump to the invalid address stated on the next line
==20295==    at 0x0: ???
==20295==    by 0xB44E2F: ossl_init (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0xB19E2E: curl_global_init (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0x255EA3: std::sys_common::once::futex::Once::call (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0x270EDF: curl::INIT_CTOR::init_ctor (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0xFA4A83: libc_start_init (__libc_start_main.c:64)
==20295==    by 0x270EFA: ??? (in /usr/local/cargo/bin/cargo-shuttle)
==20295==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==20295==
==20295==
==20295== Process terminating with default action of signal 11 (SIGSEGV)
==20295==  Bad permissions for mapped region at address 0x0
==20295==    at 0x0: ???
==20295==    by 0xB44E2F: ossl_init (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0xB19E2E: curl_global_init (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0x255EA3: std::sys_common::once::futex::Once::call (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0x270EDF: curl::INIT_CTOR::init_ctor (in /usr/local/cargo/bin/cargo-shuttle)
==20295==    by 0xFA4A83: libc_start_init (__libc_start_main.c:64)
==20295==    by 0xFA4AA8: libc_start_main_stage2 (__libc_start_main.c:91)
==20295==    by 0x270EFA: ??? (in /usr/local/cargo/bin/cargo-shuttle)
==20295==
==20295== HEAP SUMMARY:
==20295==     in use at exit: 0 bytes in 0 blocks
==20295==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==20295==
==20295== All heap blocks were freed -- no leaks are possible
==20295==
==20295== For lists of detected and suppressed errors, rerun with: -s
==20295== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

So, it seems like the issue with openssl crate and specifically the issue with musl-based systems
Possible solutions are:

Specify special rust flags to link with system's musl instead of bundled on install i.e. RUSTFLAGS=-Ctarget-feature=-crt-static cargo install cargo-shuttle
Enable feature vendored-openssl for shuttle (or make it default feature) i.e. cargo install cargo-shuttle --features vendored-openssl (it requires perl and make tools to work)
Install shuttle with binstall as it seems like prebuilt binary already built with vendored-openssl i.e. cargo binstall cargo-shuttle
As suggestend in issue replace openssl crate with another implementation

I solved the issue for myself, but perhaps to make life easier for others, some updates to the troubleshooting guide or any other actions should be taken.
Version
v0.11.2
Which operating systems are you seeing the problem on?
Linux
Which CPU architectures are you seeing the problem on?
x86_64
Relevant log output
No response
Duplicate declaration

[X] I have searched the issues and there are none like this.

Thank you for this and for investigating the cause @meskill, this is a great bug report! We'll take a closer look at this after the upcoming release which is due on monday. :pray:

Closing since we are no longer using openssl in cargo-shuttle


Reverse copy?

Is there a way to do reverse copy command - take the working file and copy it into the template file replacing actual values with variable placeholders? The reasoning is - I am constantly developing the code and need the template to be in sync with the latest updates.

Just did a little JS script:
#!/usr/bin/env node
// @ts-nocheck

const yaml = require('js-yaml');
const fs = require('fs');

const tmplr = yaml.load(fs.readFileSync(`.tmplr.yml`, 'utf-8')).steps;
const files = tmplr.filter((step) => 'copy' in step);
const variables = tmplr.filter((step) => 'read' in step);

for (let file of files) {
  let fileContent = fs.readFileSync(file.to, 'utf-8');

  for (let variable of variables) {
    const regex = new RegExp(`(arn:aws[^:]*:[^:]*:[^:]*:)?${variable.eval}`, 'g');
    fileContent = fileContent.replace(regex, (match, p1) => (p1 ? match : `{{ tmplr.${variable.read} }}`));
  }

  fs.writeFileSync(file.copy, fileContent, { encoding: 'utf8', flag: 'w' });
  console.log(`✔ Un-templated: "${file.to}" -> "${file.copy}"`);
}

Basically reverse replacement (the RegEx part is for my particular scenario, I don't want replacement in the middle of ARN string)


Yunyang/feature/item db

Partially implemented ItemDB added

forget to include google-services.json, which is mistakenly ignored by .gitignore, a new pr will be replace this one


which are the correct EVALUATION_SCALES values

in the main code you have:
       if args.multi_scale:             EVALUATION_SCALES = [0.5, 0.75, 1.0, 1.25, 1.5, 1.75]  # must be all floats!             EVALUATION_SCALES = [0.15, 0.25, 0.5]  # must be all floats!
is the first one intended to be overridden by the second?

Hello @eyaler. the first one is right.
EVALUATION_SCALES = [0.5, 0.75, 1.0, 1.25, 1.5, 1.75]

First one is used by the original paper, second one works better subjectively.


Prepare for 0.5.1 release

Device model and serial information is exposed
Less likely to encounter certificate errors
Better reconnection after network errors
No longer fails when fan controllers are present
Basic support for fan controllers

All that's left is to increase this version number, merge to master, tag, and push to PyPI?

I think I did it.


Implement additional argument validation steps and record multiple failures before exiting

This PR adds validation for:

conditional compilation arguments
-profile-generate and -profile-use
-F and -Fsystem

Additionally, if a validation step fails when initializing the driver, don't fail immediately. Instead, record any other validation failures and then exit before planning.

@swift-ci test

Looks like I made a small mistake with the original implementation - a couple of these diagnostics should be warnings. Thanks for the quick review @DougGregor!

@swift-ci test

@swift-ci test

@swift-ci test


SCD40 temperature calibration

SCD40 is samping ~ 4F higher than external sensor sitting next to it. Need to check with calibrated sensor to determine which sensor is inaccurate, and if SCD40, look for calibration API

Look at setSensorAltitude() and/or setAmbientPressure()

implemented setSensorAltitude() and it is in testing

scd40 branch implemented setSensorAltitude() and a power management change, but I'm not sure the current code has any other calibration issues that can be addressed in software. There is a recommended way to initially calibrate the sensor which involves a week of indoor and outdoor (lowest CO2 level) time. We could also look at case design, but I don't think there is a significant issue?


Improve class handler support

Codecov Report
Patch and project coverage have no change.

Comparison is base (e49b13d) 91.46% compared to head (2a50040) 91.46%.

:exclamation: Current head 2a50040 differs from pull request most recent head 99a485b. Consider uploading reports for the commit 99a485b to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   91.46%   91.46%
=======================================
  Files           2        2
  Lines         246      246
  Branches       43       43
=======================================
  Hits          225      225
  Misses         21       21

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[bug?] "created_at" has been updated when save whit options.patch == true

environment -> windows10，mysql5.7
model -> hasTimestamps: true,
await modelInstance.save({
  name: 'Jack',
}, { patch: true })
‘created_at’ column has been updated

await modelInstance.save({
  name: 'Jack',
})
‘created_at’ column not updated

My fault


add Milankovitch cycles

Closes #27 and closes #29

Add look up for orbital parameters from Laskar 2004 dataset.
Update dealing with dates to make Insolation work with Float32 values.
Add tests and documentation for the new Milankovitch cycles.
Specifically test that long-term variations in vernal equinox and perihelion date are correct.
Change mean anomaly to be calculated relative to epoch not to vernal equinox.
Remove Manifest files.

Docs preview here: https://clima.github.io/Insolation.jl/previews/PR34

bors try

bors try

bors try

bors r+