Generate and review validation reports: chs_islandora

Step 2: Generate reports [status: in progress --> ready for review]

[ ] Generate validation reports (run validate_by_mapper DAG): https://7a8067cb-3b99-477e-a883-7e311175a9b4.c3.us-west-2.airflow.amazonaws.com/dags/validate_by_mapper_type/grid?dag_run_id=manual__2023-11-08T01%3A05%3A51%2B00%3A00
[ ] Add a comment (in this issue) to the output URLs
[ ] Download the validation reports locally; prepend the collection registry number to the filename
[ ] Upload validation reports to the Rikolti Data Validation folder

Step 3: Review reports  [status: ready for review --> review in progress]

[ ] Review sample collections validation reports; leave notes in the spreadsheet
[ ] Quickly (and not very deeply) scan through other validation reports (to identify if any new metadata fields surface)
[ ] Synthesize notes at the mapper level
[ ] Share an update (and surface any anomalies) during a weekly check-in (Mondays at 3:00pm)

Step 4: Have data validation issues? Address & resolve validation issues (synthesized mapper-level):

[ ] Create a new issue (“Validation results: Rikolti mapper name“) and report/request CIC fixes & investigations. Assign to CIC.
[ ] Add a comment to link to the new “validation results” issue.
[ ] Add a “blocked/paused” label to this issue. Include a status note in this issue title (e,g., HOLD for CIC fixes; HOLD for code review; etc.)
[ ] Move this issue back to the “To Do” pile.

[Re-generate & re-review (repeat steps 2-3 above, as needed.]
Step 5: Have acceptable validation reports?

[ ] Move the valid (accepted) reports to the “VALID” folder in google drive.
[ ] Update the mapper progress spreadsheet; indicate that the mapper is accepted

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/3501/validation/11-08-2023T01:20:17.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#3501/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26726/validation/11-08-2023T01:20:20.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26726/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26727/validation/11-08-2023T01:20:20.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26727/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26923/validation/11-08-2023T01:20:21.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26923/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26924/validation/11-08-2023T01:20:21.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26924/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26925/validation/11-08-2023T01:20:23.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26925/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26926/validation/11-08-2023T01:20:23.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26926/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27504/validation/11-08-2023T01:20:23.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27504/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27505/validation/11-08-2023T01:20:24.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27505/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27506/validation/11-08-2023T01:20:25.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27506/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27508/validation/11-08-2023T01:20:25.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27508/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27509/validation/11-08-2023T01:20:26.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27509/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27510/validation/11-08-2023T01:20:27.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27510/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27511/validation/11-08-2023T01:20:27.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27511/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27512/validation/11-08-2023T01:20:28.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27512/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27514/validation/11-08-2023T01:20:28.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27514/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27515/validation/11-08-2023T01:20:29.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27515/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27516/validation/11-08-2023T01:20:29.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27516/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27517/validation/11-08-2023T01:20:30.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27517/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27518/validation/11-08-2023T01:20:44.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27518/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27519/validation/11-08-2023T01:20:54.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27519/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27520/validation/11-08-2023T01:20:56.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27520/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27521/validation/11-08-2023T01:20:56.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27521/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27522/validation/11-08-2023T01:20:56.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27522/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27523/validation/11-08-2023T01:20:57.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27523/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27524/validation/11-08-2023T01:20:57.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27524/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27525/validation/11-08-2023T01:20:58.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27525/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27526/validation/11-08-2023T01:20:58.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27526/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27527/validation/11-08-2023T01:20:59.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27527/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27528/validation/11-08-2023T01:20:59.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27528/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27529/validation/11-08-2023T01:21:00.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27529/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27530/validation/11-08-2023T01:21:01.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27530/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27532/validation/11-08-2023T01:21:01.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27532/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27536/validation/11-08-2023T01:21:02.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27536/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27537/validation/11-08-2023T01:21:02.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27537/

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27538/validation/11-08-2023T01:21:03.csv

[2023-11-08, 01:21:03 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27538/

@christinklez Needs notes review/synthesizing

Issue reported to CIC: https://github.com/ucldc/rikolti/issues/634

[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/3501/vernacular_metadata_2023-12-20T22:52:47/mapped_metadata_2023-12-20T22:56:42/validation_2023-12-20T23:07:20.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#3501/vernacular_metadata_2023-12-20T22:52:47/mapped_metadata_2023-12-20T22:56:42/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26726/vernacular_metadata_2023-12-20T22:52:48/mapped_metadata_2023-12-20T22:56:45/validation_2023-12-20T23:07:22.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26726/vernacular_metadata_2023-12-20T22:52:48/mapped_metadata_2023-12-20T22:56:45/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26727/vernacular_metadata_2023-12-20T22:53:00/mapped_metadata_2023-12-20T22:57:12/validation_2023-12-20T23:07:23.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26727/vernacular_metadata_2023-12-20T22:53:00/mapped_metadata_2023-12-20T22:57:12/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26923/vernacular_metadata_2023-12-20T22:53:02/mapped_metadata_2023-12-20T22:57:16/validation_2023-12-20T23:07:23.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26923/vernacular_metadata_2023-12-20T22:53:02/mapped_metadata_2023-12-20T22:57:16/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26924/vernacular_metadata_2023-12-20T22:53:03/mapped_metadata_2023-12-20T22:57:21/validation_2023-12-20T23:07:24.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26924/vernacular_metadata_2023-12-20T22:53:03/mapped_metadata_2023-12-20T22:57:21/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26925/vernacular_metadata_2023-12-20T22:53:04/mapped_metadata_2023-12-20T22:57:23/validation_2023-12-20T23:07:25.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26925/vernacular_metadata_2023-12-20T22:53:04/mapped_metadata_2023-12-20T22:57:23/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/26926/vernacular_metadata_2023-12-20T22:53:09/mapped_metadata_2023-12-20T22:57:35/validation_2023-12-20T23:07:25.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#26926/vernacular_metadata_2023-12-20T22:53:09/mapped_metadata_2023-12-20T22:57:35/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27504/vernacular_metadata_2023-12-20T22:53:09/mapped_metadata_2023-12-20T22:57:36/validation_2023-12-20T23:07:26.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27504/vernacular_metadata_2023-12-20T22:53:09/mapped_metadata_2023-12-20T22:57:36/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27505/vernacular_metadata_2023-12-20T22:53:15/mapped_metadata_2023-12-20T22:57:40/validation_2023-12-20T23:07:26.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27505/vernacular_metadata_2023-12-20T22:53:15/mapped_metadata_2023-12-20T22:57:40/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27506/vernacular_metadata_2023-12-20T22:53:17/mapped_metadata_2023-12-20T22:57:44/validation_2023-12-20T23:07:27.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27506/vernacular_metadata_2023-12-20T22:53:17/mapped_metadata_2023-12-20T22:57:44/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27508/vernacular_metadata_2023-12-20T22:53:18/mapped_metadata_2023-12-20T22:57:47/validation_2023-12-20T23:07:28.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27508/vernacular_metadata_2023-12-20T22:53:18/mapped_metadata_2023-12-20T22:57:47/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27509/vernacular_metadata_2023-12-20T22:53:23/mapped_metadata_2023-12-20T22:57:50/validation_2023-12-20T23:07:28.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27509/vernacular_metadata_2023-12-20T22:53:23/mapped_metadata_2023-12-20T22:57:50/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27510/vernacular_metadata_2023-12-20T22:53:23/mapped_metadata_2023-12-20T22:57:54/validation_2023-12-20T23:07:29.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27510/vernacular_metadata_2023-12-20T22:53:23/mapped_metadata_2023-12-20T22:57:54/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27511/vernacular_metadata_2023-12-20T22:53:26/mapped_metadata_2023-12-20T22:58:01/validation_2023-12-20T23:07:30.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27511/vernacular_metadata_2023-12-20T22:53:26/mapped_metadata_2023-12-20T22:58:01/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27512/vernacular_metadata_2023-12-20T22:53:28/mapped_metadata_2023-12-20T22:58:04/validation_2023-12-20T23:07:30.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27512/vernacular_metadata_2023-12-20T22:53:28/mapped_metadata_2023-12-20T22:58:04/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27514/vernacular_metadata_2023-12-20T22:53:30/mapped_metadata_2023-12-20T22:58:09/validation_2023-12-20T23:07:31.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27514/vernacular_metadata_2023-12-20T22:53:30/mapped_metadata_2023-12-20T22:58:09/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27515/vernacular_metadata_2023-12-20T22:53:30/mapped_metadata_2023-12-20T22:58:11/validation_2023-12-20T23:07:31.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27515/vernacular_metadata_2023-12-20T22:53:30/mapped_metadata_2023-12-20T22:58:11/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27516/vernacular_metadata_2023-12-20T22:53:32/mapped_metadata_2023-12-20T22:58:13/validation_2023-12-20T23:07:32.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27516/vernacular_metadata_2023-12-20T22:53:32/mapped_metadata_2023-12-20T22:58:13/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27517/vernacular_metadata_2023-12-20T22:53:32/mapped_metadata_2023-12-20T22:58:15/validation_2023-12-20T23:07:32.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27517/vernacular_metadata_2023-12-20T22:53:32/mapped_metadata_2023-12-20T22:58:15/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27518/vernacular_metadata_2023-12-20T22:53:34/mapped_metadata_2023-12-20T22:58:18/validation_2023-12-20T23:07:47.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27518/vernacular_metadata_2023-12-20T22:53:34/mapped_metadata_2023-12-20T22:58:18/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27519/vernacular_metadata_2023-12-20T22:54:56/mapped_metadata_2023-12-20T23:01:28/validation_2023-12-20T23:07:58.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27519/vernacular_metadata_2023-12-20T22:54:56/mapped_metadata_2023-12-20T23:01:28/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27520/vernacular_metadata_2023-12-20T22:56:07/mapped_metadata_2023-12-20T23:05:57/validation_2023-12-20T23:07:59.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27520/vernacular_metadata_2023-12-20T22:56:07/mapped_metadata_2023-12-20T23:05:57/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27521/vernacular_metadata_2023-12-20T22:56:14/mapped_metadata_2023-12-20T23:06:12/validation_2023-12-20T23:08:00.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27521/vernacular_metadata_2023-12-20T22:56:14/mapped_metadata_2023-12-20T23:06:12/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27522/vernacular_metadata_2023-12-20T22:56:14/mapped_metadata_2023-12-20T23:06:13/validation_2023-12-20T23:08:00.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27522/vernacular_metadata_2023-12-20T22:56:14/mapped_metadata_2023-12-20T23:06:13/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27523/vernacular_metadata_2023-12-20T22:56:15/mapped_metadata_2023-12-20T23:06:14/validation_2023-12-20T23:08:01.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27523/vernacular_metadata_2023-12-20T22:56:15/mapped_metadata_2023-12-20T23:06:14/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27524/vernacular_metadata_2023-12-20T22:56:16/mapped_metadata_2023-12-20T23:06:19/validation_2023-12-20T23:08:01.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27524/vernacular_metadata_2023-12-20T22:56:16/mapped_metadata_2023-12-20T23:06:19/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27525/vernacular_metadata_2023-12-20T22:56:17/mapped_metadata_2023-12-20T23:06:21/validation_2023-12-20T23:08:02.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27525/vernacular_metadata_2023-12-20T22:56:17/mapped_metadata_2023-12-20T23:06:21/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27526/vernacular_metadata_2023-12-20T22:56:18/mapped_metadata_2023-12-20T23:06:22/validation_2023-12-20T23:08:03.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27526/vernacular_metadata_2023-12-20T22:56:18/mapped_metadata_2023-12-20T23:06:22/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27527/vernacular_metadata_2023-12-20T22:56:22/mapped_metadata_2023-12-20T23:06:34/validation_2023-12-20T23:08:03.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27527/vernacular_metadata_2023-12-20T22:56:22/mapped_metadata_2023-12-20T23:06:34/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27528/vernacular_metadata_2023-12-20T22:56:24/mapped_metadata_2023-12-20T23:06:37/validation_2023-12-20T23:08:04.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27528/vernacular_metadata_2023-12-20T22:56:24/mapped_metadata_2023-12-20T23:06:37/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27529/vernacular_metadata_2023-12-20T22:56:26/mapped_metadata_2023-12-20T23:06:44/validation_2023-12-20T23:08:04.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27529/vernacular_metadata_2023-12-20T22:56:26/mapped_metadata_2023-12-20T23:06:44/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27530/vernacular_metadata_2023-12-20T22:56:27/mapped_metadata_2023-12-20T23:06:46/validation_2023-12-20T23:08:05.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27530/vernacular_metadata_2023-12-20T22:56:27/mapped_metadata_2023-12-20T23:06:46/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27532/vernacular_metadata_2023-12-20T22:56:32/mapped_metadata_2023-12-20T23:06:58/validation_2023-12-20T23:08:06.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27532/vernacular_metadata_2023-12-20T22:56:32/mapped_metadata_2023-12-20T23:06:58/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27536/vernacular_metadata_2023-12-20T22:56:32/mapped_metadata_2023-12-20T23:06:58/validation_2023-12-20T23:08:06.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27536/vernacular_metadata_2023-12-20T22:56:32/mapped_metadata_2023-12-20T23:06:58/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27537/vernacular_metadata_2023-12-20T22:56:33/mapped_metadata_2023-12-20T23:07:02/validation_2023-12-20T23:08:07.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27537/vernacular_metadata_2023-12-20T22:56:33/mapped_metadata_2023-12-20T23:07:02/data/
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Download validation report at: https://rikolti-data.s3.amazonaws.com/27538/vernacular_metadata_2023-12-20T22:56:34/mapped_metadata_2023-12-20T23:07:06/validation_2023-12-20T23:08:07.csv
[2023-12-20, 23:08:07 UTC] {{logging_mixin.py:150}} INFO - Review collection data at: https://rikolti-data.s3.us-west-2.amazonaws.com/index.html#27538/vernacular_metadata_2023-12-20T22:56:34/mapped_metadata_2023-12-20T23:07:06/data/

@gamontoya This set of collections is ready for your re-review! (Fresh validation reports copied in above, dated Dec 20.) Thanks!


UI fails to load previously cached frames when working with large images

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

Expected Behaviour

A user can navigate through all frames in a job regardless of image size.
Current Behaviour

The UI gets stuck in a loading state when trying to go backwards through already loaded frames.
Possible Solution

This seems to be some issue with retrieving frames that have been cached, because the UI always stops at one of the image chunk points.
Steps to Reproduce (for bugs)

Here is a live example uploaded on cvat.org: https://cvat.org/tasks/66868/jobs/97576

Create a task with 100 images (all 2048x2448)
Open the job and step through all frames
Once at the end, step backwards through all frames
At some point, the UI shows the loading icon and fails to load any previous images. You can however step back forward, but everything backwards fails to load.

Hi, this is an expected issue due to image cache size limitation in the current implementation, especially for high resolution images.

Hey @azhavoro thanks for the response. Do you know if or when this issue might have a fix? Just downscaling the images isn't really an option because we really need pixel accuracy on higher resolution images. I've also looked into just disabling the cache, but trying to disable it through the UI as well as the API doesn't seem to work. Any advice would be greatly appreciated!

@maximusunc Sorry, my previous comment was wrong, I thought you were talking about reloading each frame in the backward, which is related with the limited cache size. Thanks for the fix, I'll test it today.


Issue 409

got rid from excessed dm-dropdown-static-include div tag to resolve issue 409

needs to implement removing tag for min version


Fix regular expressions Cross-Site Scripting (XSS) vulnerability[CVE-2019-16769]

PR #21 is raised to fix this vulnerability.


Botbyte AI Integration

Integrated botbyte AI and also am working on the responses as if given by our supreme leader

Hi Rakshit,
The bot can be trained on community stats and user profiles if needed, my
team will work on it with support from your side as well. RIght now, it
goes through your metadata and is crawling your site
On Tue, Jul 16, 2024, 15:43 Rakshit Singh @.***> wrote:

Hey sanket chatbot is not in the list of features we are looking to
implement as of now, if this could be trained on community stats and user
profiles then maybe might give it a thought? Right now it does not provide
any functionality dont you think
—
Reply to this email directly, view it on GitHub
https://github.com/Bot-Rakshit/bm_frontend/pull/12#issuecomment-2230528617,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASH4KIL4F4G7FGNDC2I6YD3ZMTW5PAVCNFSM6AAAAABK52LX5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQGUZDQNRRG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for the contribution sanket, right now we are working on priority features/bugs that needs to be solved. I shall get back to you by the weekend? For now i'm not closing this pr

Sure, no problem.
On Tue, Jul 16, 2024, 19:22 Rakshit Singh @.***> wrote:

Thanks for the contribution sanket, right now we are working on priority
features/bugs that needs to be solved. I shall get back to you by the
weekend? For now i'm not closing this pr
—
Reply to this email directly, view it on GitHub
https://github.com/Bot-Rakshit/bm_frontend/pull/12#issuecomment-2230949680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASH4KINIH445AAYNJZIYBHTZMUQQDAVCNFSM6AAAAABK52LX5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQHE2DSNRYGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

closing it for now, will get back to this next week


node v4.0 support + dependency bump

saucelabs fails due credentials:
Error:
Zuul tried to run tests in saucelabs, however no saucelabs credentials were provided.
See the zuul wiki (https://github.com/defunctzombie/zuul/wiki/Cloud-testing) for info on how to setup cloud testing.

:+1: thanks
looks like travis only sets the secure encrypted env vars which contain the saucelab credentials when the build was triggered by the travis account owner.
otherwise it would be a security hole and allow abuse and retrieval (simply env in the test script...) of encrypted env vars through arbitrary PRs.
it's not optimal for PR CI though.


Improve contents of $PSVersionTable Automatic Variable with Windows Edition Number

Currently, the $PSVersionTable automatic variable provides a number of key properties of the version of PowerShell running. One thing missing from that variable is the Edition value of the running Windows OS.
Steps to reproduce

PS [C:\foo> ]> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Microsoft Windows 10.0.18262
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.1.0}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Expected behavior:

````powershell
PS [C:\foo> ]> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.1.0
PSEdition                      Core
GitCommitId                    6.1.0
OS                             Microsoft Windows 10.0.18262
Edition                        1809
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0, 5.0, 5.1.10032.0, 6.1.0}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Actual behavior
The automatic variable does not currently contain the Edition whereas running WInVer provides that. You can also use a WMI call. But Updating $PSVersionTable would be very useful.

[System.Environment]::OSVersion may be what you are looking for.  I don't think we want to keep making $PSVersionTable bigger.  Would rather have a cross-platform Get-ComputerInfo that has OS info.

[System.Environment]::OSVersion does not return the Edition of WIndows 10. :-(

@doctordns Get-ComputerInfo as it exists today is expensive to run and I don't think returns info the user wants in a consumable form most of the time.  If you can explain the use case where you need this info, it would help to justify adding it.

Another note is that PowerShell is portable - what is Edition on Unix? I think that for consistency it should be in CoreFX.


Test against DRF 3.8

Failing (existing) test: https://github.com/lock8/django-rest-framework-jwt-refresh-token/blob/2490188b69a4a334ff848a9d6e6655ad48694832/tests/test_long_refresh_token_views.py#L169-L183


Crashes when Calling Sync on a DispatchQueue in a Transaction with a Statement Inside

If you call sync on a DispatchQueue (and run a statement inside the closure) inside of a transaction, SQLite.swift will have called sync twice on the same DispatchQueue and therefore crash the program.
Internally, SQLite.swift checks the current executing DispatchQueue to find if it contains a context value made out of the bits of the Connection to figure out if it should call sync on it or not. Sync being called on a DispatchQueue changes out the queue associated with the current execution context, but continues running code on the same call stack.
func test() {
    let connection = try! Connection()

    let dispatchQueue = DispatchQueue(label: "Test")

    try! connection.transaction {
        dispatchQueue.sync {
            // Crash
            try! connection.execute(".")
        }
    }

    let wait = 1 + 1
}

I also see this in my crash logs stack trace when I submitted my app on App Store and they reviewed it.
Please shed some light on this issue.

Any news on this? I saw something some crash logs that brought me here and it might be related

Probably duplicate of #365


Cannot construct JacobianFactor in Python

Description
I believe something is wrong with constructing JacobianFactors from the result of a linearize() operation when using the python wrapper.  Tagging @varunagrawal and @ProfFan due to the fact this is python related.
Specifically, the RTTI dynamic casts used in JacobianFactor constructors do not seem to be working properly.  Here are two example usages:
https://github.com/borglab/gtsam/blob/ff7ddf48bd8bb2f993437f01cd32a4727d6f023b/gtsam/linear/JacobianFactor.cpp#L58-L67
https://github.com/borglab/gtsam/blob/ff7ddf48bd8bb2f993437f01cd32a4727d6f023b/gtsam/linear/JacobianFactor.cpp#L196-L211
For whatever reason, nonlinear factors constructed in python, which are then called with .linearize() to create a JacobianFactor, cannot be passed into the JacobianFactor(factor) constructors because boost::dynamic_pointer_cast<JacobianFactor>(factor) returns a null pointer.
Steps to reproduce
This example python script fails:
import gtsam
import gtdynamics as gtd

def main():
    f = gtd.MinTorqueFactor(0, gtsam.noiseModel.Unit.Create(1))

    init = gtsam.Values()
    init.insert(0, 0.0)

    flin = f.linearize(init)
    flin.print("Linearized Factor: ")
    print("\nLinearized factor has type: ", type(flin), '\n')
    # output: Linearized factor has type:  <class 'gtsam.gtsam.JacobianFactor'>

    gtsam.JacobianFactor(flin)  # this throws an error

if __name__ == '__main__':
    main()

Which throws the error:
In JacobianFactor(const GaussianFactor& rhs), rhs is neither a JacobianFactor nor a HessianFactor

Expected behavior
The python result should match that of this example C++ script succeeds:
#include <gtdynamics/factors/MinTorqueFactor.h>

#include <gtsam/nonlinear/NonlinearFactorGraph.h>

#include <iostream>

using namespace gtsam;
using namespace gtdynamics;

int main() {
  auto f = MinTorqueFactor(0, noiseModel::Unit::Create(1));

  auto init = Values();
  init.insert(0, 0.0);

  auto flin = f.linearize(init);
  flin->print("Linearized Factor: ");
  std::cout << "\nLinearized factor has type: " << typeid(*flin).name() << std::endl<< std::endl;
  // Output: Linearized factor has type: N5gtsam14JacobianFactorE

  auto jf = JacobianFactor(*flin);
}

Environment

MacOS 11.3.1, MacBook Air (M1, 2020),
AppleClang <IP_ADDRESS>50022
gtsam hash b99bf4e92912f4ad0020f79d6b222a3d6593514f
I also experienced similar errors when I ran on an ubuntu intel lab machine, but I didn't rigorously test these particular test files.
Additional information
This only occurs for nonlinear factors defined outside of the GTSAM repo.  So, for example, PriorFactor, BetweenFactor, etc all still work as expected.
This causes noticeable failures on optimizations with Constrained noise models, may be causing silent correctness errors on other optimizations, and is likely causing all non-GTSAM factors to be calling the HessianFactor constructor instead of the JacobianFactor constructor (performance penalty).

*No capacity to work on this for now, need to get ICRA ddl done

Temporarily using this workaround to use name-based type matching:
JacobianFactor::JacobianFactor(const GaussianFactor& gf) {
  // Copy the matrix data depending on what type of factor we're copying from
  if (!strcmp(typeid(gf).name(), typeid(JacobianFactor).name()))
    *this = JacobianFactor(*static_cast<const JacobianFactor*>(&gf));
  else if (!strcmp(typeid(gf).name(), typeid(HessianFactor).name()))
    *this = JacobianFactor(*static_cast<const HessianFactor*>(&gf));
  else
    throw std::invalid_argument(
        "In JacobianFactor(const GaussianFactor& rhs), rhs is neither a JacobianFactor nor a HessianFactor");
}

And do a similar thing in _convertOrCastToJacobians.
Note: for constrained optimization, you still need to manually set the linearSolverType param to QR - for some reason GTSAM is also not properly recognizing that the constrained noise models and auto-switching to QR.  e.g.
params = gtsam.LevenbergMarquardtParams()
params.setLinearSolverType("MULTIFRONTAL_QR")
result = gtsam.LevenbergMarquardtOptimizer(graph, init, params).optimize()

I'm leaving this open because it needs to eventually be fixed, but this workaround works for now.

Yeah we'll figure it out after ICRA :)

Sorry for forgetting about this for a long time.
Adding debug prints
In JacobianFactor constructor, I added:
std::cout << "Constructing a Jacobian factor from a Gaussian Factor!!\n"  //
          << "typeid of JacobianFactor is " << typeid(JacobianFactor).name()
          << '\t' << typeid(JacobianFactor).hash_code() << "\n"   //
          << "typeid of input argument is " << typeid(gf).name()  //
          << '\t' << typeid(gf).hash_code() << std::endl;

Then in GTDynamics MinTorqueFactor construtor, I added
std::cout << "Constructing a MinTorqueFactor..." << std::endl;
std::cout << "typeid of gtdynamics' JacobianFactor is "
          << typeid(gtsam::JacobianFactor).name() << '\t'
          << typeid(gtsam::JacobianFactor).hash_code() << std::endl;

Test code
The test code in c++:
auto values = gtsam::Values();
values.insert(0, 0.0);
{
  auto f = gtsam::PriorFactor(0, 0.0, gtsam::noiseModel::Unit::Create(1));
  auto gaussian_factor = f.linearize(values);
  gtsam::JacobianFactor jacobian_factor(*gaussian_factor);
}
{
  auto f = gtdynamics::MinTorqueFactor(0, gtsam::noiseModel::Unit::Create(1));
  auto gaussian_factor = f.linearize(values);
  gtsam::JacobianFactor jacobian_factor(*gaussian_factor);
}

and in python:
values = gtsam.Values()
values.insert(0, 0.0)

f = gtsam.PriorFactorDouble(0, 0.0, gtsam.noiseModel.Unit.Create(1))
gaussian_factor = f.linearize(values)
jacobian_factor = gtsam.JacobianFactor(gaussian_factor)

f = gtd.MinTorqueFactor(0, gtsam.noiseModel.Unit.Create(1))
gaussian_factor = f.linearize(values)
jacobian_factor = gtsam.JacobianFactor(gaussian_factor)  # this throws an error

Results
c++ results:
Constructing a Jacobian factor from a Gaussian Factor!!
typeid of JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
typeid of input argument is N5gtsam14JacobianFactorE<PHONE_NUMBER>
Constructing a MinTorqueFactor...
typeid of gtdynamics' JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
Constructing a Jacobian factor from a Gaussian Factor!!
typeid of JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
typeid of input argument is N5gtsam14JacobianFactorE<PHONE_NUMBER>

python results:
Constructing a Jacobian factor from a Gaussian Factor!!
typeid of JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
typeid of input argument is N5gtsam14JacobianFactorE<PHONE_NUMBER>
Constructing a MinTorqueFactor...
typeid of gtdynamics' JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
Constructing a Jacobian factor from a Gaussian Factor!!
typeid of JacobianFactor is N5gtsam14JacobianFactorE<PHONE_NUMBER>
typeid of input argument is N5gtsam14JacobianFactorE<PHONE_NUMBER>
Traceback (most recent call last):
  File "/Users/gerry/GIT_REPOS/GTDynamics/gtdynamics/cablerobot/src/test.py", line 22, in <module>
    main()
  File "/Users/gerry/GIT_REPOS/GTDynamics/gtdynamics/cablerobot/src/test.py", line 14, in main
    jacobian_factor = gtsam.JacobianFactor(gaussian_factor)  # this throws an error
ValueError: In JacobianFactor(const GaussianFactor& rhs), rhs is neither a JacobianFactor nor a HessianFactor

So I think this is an indication that the python wrapper is using a different version of gtdynamics, so maybe we just need GTSAM_EXPORT in gtdynamics?
Going to continue working on this.

I figured out the problem: my gtdynamics.cpython-39-darwin.so and gtsam.cpython-39-darwin.so files are linking to different places.  Specifically:

gtdynamics.cpython-39-darwin.so is linking to /Users/gerry/lib/libgtsamDebug.4.dylib while
gtsam.cpython-39-darwin.so is linking to /Users/gerry/GIT_REPOS/gtsam/build/gtsam/libgtsamDebug.4.dylib

(found using otool -l)
Note that also gtdynamics.cpython-39-darwin.so is using @rpath/libgtdynamicsDebug.dylib, but rpath is set to:
Load command 26
          cmd LC_RPATH
      cmdsize 64
         path /Users/gerry/GIT_REPOS/GTDynamics/build/gtdynamics (offset 12)
Load command 27
          cmd LC_RPATH
      cmdsize 32
         path /Users/gerry/lib (offset 12)

so actually I think it's also going to be linking to the "wrong" file.

I don't know if this is specific to my machine or not.  Would someone else mind pasting their output of:
otool -l /Users/gerry/miniforge3/lib/python3.9/site-packages/gtdynamics-1.0.0-py3.9.egg/gtdynamics/gtdynamics.cpython-39-darwin.so
otool -l /Users/gerry/miniforge3/lib/python3.9/site-packages/gtsam-4.1.0-py3.9.egg/gtsam/gtsam.cpython-39-darwin.so

(replacing /Users/gerry/miniforge3 with wherever your python packages are; the folder can be found using python -c 'import gtsam; print(gtsam.__path__)')
???


Fully document project template

Description
When running kedro new the project template that comes out is not fully documented.
Context
The kedro template should set a good example for those using it.  Many new python developers are using kedro's template as their way to get started and are building from it's example.   It should pass interrogate and/or pydocstyle out of the box.
environment
I installed kedro@master to compare to the upcoming version.
Interrogate

pydocstyle

Personally my template uses these tools, this is one more hurdle for me to get through every time the template is significantly updated
Possible Implementation
I'm happy to help, but fear that the process will be a slow back and fourth without discussion ahead of time.  Is this something the kedro team would like to take PR for?  Is it best done in one PR, or module by module.

Hey @WaylonWalker, pylint already warns about missing-module-docstring or missing-function-docstring, so I'm tempted to leave that as the only one responsible for this sort of thing so we don't have a cacophony of third-party linting tools. Having said that, if there are places where you believe there should be more docstrings, feel free to raise a PR (either here or on starters repo), and we'll be happy to approve! ✅


Skip Validation is not working with json style of storage-config secret.

/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
What did you expect to happen:
When a user uses json style of storage-config, skip verification option does not work.
which was working with  serving.kserve.io/s3-verifyssl  annotation.
json style
apiVersion: v1
stringData:
  localMinIO: |
    {
      "type": "s3",
      "access_key_id": "admin",
      "secret_access_key": "password",
      "endpoint_url": "http://minio.minio.svc:9000",
      "bucket": "modelmesh-example-models",
      "region": "us-south"
      "verify": "0"   <===
    }
kind: Secret
metadata:
  name: storage-config
type: Opaque

annotation style
apiVersion: v1
data:
  AWS_ACCESS_KEY_ID: VEhFQUNDRVNTS0VZ
  AWS_SECRET_ACCESS_KEY: VEhFUEFTU1dPUkQ=
kind: Secret
metadata:
  annotations:
    serving.kserve.io/s3-endpoint: minio.minio.svc:9000
    serving.kserve.io/s3-region: us-east-2
    serving.kserve.io/s3-useanoncredential: "false"
    serving.kserve.io/s3-usehttps: "1"
    serving.kserve.io/s3-verifyssl: "0"        <===
  name: storage-config
  namespace: kserve-demo
type: Opaque

What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version:
Knative Version:
KServe Version:
Kubeflow version:
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube/Kind version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

For StorageSpec the JSON is copied to equivalent environment variables. That's done here: https://github.com/kserve/kserve/blob/6f4bf79e4dd8bd15fb920508b2652bb20222ad9f/python/kserve/kserve/storage/storage.py#L114-L120. There is no copying done for any verify field.
The only place where I can find the structure of the storage secret is here: https://github.com/kserve/kserve/tree/master/docs/samples/storage/storageSpec#create-common-storage-secret. There is no mention of a verify field, so I'm not sure if this can be seen as a bug, yet I agree that it is desirable to have a field to turn off SSL verification.

fixed by #3267

/close


HTTP 1.0 and protocol sniffing

Currently, Istio doesn't enable http/1.0 by default (env var can turn it on). However, we match http/1.0 in the protocol sniffing, only to reject it.
We would be better off just passing it through as TCP

sounds good, but the env should also function on the protocol sniffing

Yeah I agree
On Tue, Jan 4, 2022, 11:45 PM Zhonghu Xu @.***> wrote:

sounds good, but the env should also function on the protocol sniffing
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/36707#issuecomment-1005452515, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXPVSXTMRNNKB7YJMZDUUPZI3ANCNFSM5LI5ZSGA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

HI @howardjohn
We were facing this issue in 1.12.2 and then we upgraded to 1.13.1 and yet we see the same
2022-03-03 15:04:37.559 EST[2022-03-03T20:04:37.300Z] "POST /retail/<redacted>/eligibility HTTP/1.0" 426 - low_version - "-" 0 0 0 - "-" "-" "-" "internal-sit2.digital-subscription-qa.com" "-" - - <IP_ADDRESS>:8443 <IP_ADDRESS>:47457 internal-sit2.digital-subscription-qa.com -

Nah,
Plain VS and dr and nothing else. So we have a IBM Datapower calling the service and for some reason it is calling in http 1.0.  They are hitting the DNS "internal-sit2.digital-subscription-qa.com" that is the istio-ingress and then the traffic goes to the pods via VS and DR. I could post the VS and dr if needed but there is nothing special about it. Heck here is the VS and DR
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: digital-subscription-vs-internal
  namespace: sit2
  annotations:
    argocd.argoproj.io/sync-wave: '6'
spec:
  hosts:
  - 'internal-sit2.digital-subscription-qa.com'

  gateways:
    - default/internal-ingress-gateway
  http:

  - name: route-digital-subscription-1
    match:
    - uri:
        prefix: "/retail/<redacted>/"

    route:
    - destination:
        host: "digital-subscription.sit2.svc.cluster.local"
        port:
          number: 21117
        subset: v1
      weight: 100

here is the DR
apiVersion: networking.istio.io/v1alpha3
kind: DestinationRule
metadata:
  name: digital-subscription-dr
  namespace: sit2
  annotations:
    argocd.argoproj.io/sync-wave: '5'
spec:
  host: digital-subscription.sit2.svc.cluster.local
  trafficPolicy:
    tls:
      mode: ISTIO_MUTUAL
  subsets:
  - name: v1
    labels:
      version: v1

This fix only applies to mesh. If its gateway there is no protocol sniffing

Oh Wait
I have the service defined as and it is defined as http. so that disable this? Now what do I do?
apiVersion: v1
kind: Service
metadata:
  labels:
    app: digital-subscription
    version: v1
    part-of: digital-subscription
  name: digital-subscription
  namespace: sit2
  annotations:
    argocd.argoproj.io/sync-wave: '1'
spec:
  ports:
  - name: http-digital-subscription
    port: 21117
    targetPort: 21117
  selector:
    app: digital-subscription
  type: ClusterIP

@howardjohn
Does that mean essentially we are stuck or is there a solution to this, please?

Hi.
any update on this?


Gatsby exploration

What if we built a community site using Gatsby? What would that experience be like? https://www.gatsbyjs.com/

Gatsby did not feel like a good fit after I looked over how it worked.


CodeMirror support Clickhouse sql mode

Hi, I was wondering if code mirror will ever have a mode for the database Clickhouse syntax highlighting or is there a way to do it with codemirror now? Thanks!

I don't know anything about this language, but no, CodeMirror will not support it out of the box, so if you want support, you'll have to figure out how to write it yourself (possibly using mode/sql/sql.js as a basis).


Separate a library

https://github.com/KazuCocoa/DroidTestHelper/issues/17

finish building the app
the app works well


Add surrouding_pair modifier

Previous comments from @AndreasArvidsson: https://github.com/pokey/cursorless-talon/pull/45#issuecomment-890407519


⚠ Bofrost.fr has degraded performance

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

HTTP code: 200
Response time: 1012 ms

Resolved: Bofrost.fr performance has improved in 4234f5c after 6 minutes.


GH2014: Allow multiple NugetFeeds for InProcess-NugetClient

added basic argument validation in NuGetSourceRepositoryProvider ctor
added support for multiple feeds as suggested here #2014
added basic unit tests testing argument validation
added unit tests for NuGetSourceRepositoryProvider testing added functionality

should fix #2014

@mholo65 is there anyting left to do on this PR?

No, should be ok! I’ll try finding time to take a final look soon!

@Insire I've rebased this. Will merge as soon as CI passes.

@Insire your changes have been merged. Thank you for your contribution.

What are your thoughts on adding -nuget_sources parameter (along with existing -nuget-source). This use case is already in cake in the form of version or ver?
I'll pick it in case you are wondering. :)

@nikhilagrawaldotnet said...
his use case is already in cake in the form of version or ver?

Can you point me at where you are seeing this?

In Cake.Arguments.ArgumentParser
if (name.Equals("version", StringComparison.OrdinalIgnoreCase) || name.Equals("ver", StringComparison.OrdinalIgnoreCase))

@nikhilagrawaldotnet hmm, that is one specific use case for the arguments for Cake.exe itself.  You are talking about adding an alias for one of the aliases that is executed by Cake, which isn't really the same thing.  In this instance, I don't think there is a need to do this.
@cake-build/cake-team what are your thoughts?

@gep13 @nikhilagrawaldotnet
Well there are differences. --version and --ver is an argument that Cake.exe itself knows how to handle, while --nuget_source is a configuration that only Cake.NuGet.dll knows how handle. Please not that configurations can also be set via environment variables or cake.config. I do feel that nuget_source as singular feels wrong, but it might be too late to change that, and we'll end up with two different configuration keys with same value for a long time. However, even in nuget.exe  this is calles source even though it accepts a list of sources concatenated with ;.

In that case this discussed stands closed. #MicDrop

@mholo65 said...
However, even in nuget.exe this is calls source even though it accepts a list of sources concatenated with ;.

This was my exact thought too.


Visualization bug in nbscreenshot

🐛 Bug
Hi all,
I just noticed a visualization a bug when using napari.utils.nbscreenshot(viewer). The screenshot doesn't 100%ly fit to what I see in the actual napari window. Differences are highlighted with white arrows in this screenshot:

To Reproduce
The notebook where I observed this is online available. The error is reproducible on my machine. For the screenshot, please scroll to the very end of the notebook.
https://nbviewer.jupyter.org/github/BiAPoL/Bio-image_Analysis_with_Python/blob/3fa983e7109f39f18aabb33b7e4fe70898c7e682/image_processing/07_Labeling.ipynb
Expected behavior
Pixel intensities from the canvas should be copied correctly to the screenshot.
Environment

Please copy and paste the information at napari info option in help menubar here:

napari: 0.4.7
Platform: Windows-10-10.0.19041-SP0
Python: 3.8.8 (default, Feb 24 2021, 15:54:32) [MSC v.1928 64 bit (AMD64)]
Qt: 5.15.2
PyQt5: 5.15.2
NumPy: 1.19.2
SciPy: 1.6.1
Dask: 2021.03.0
VisPy: 0.6.6

OpenGL:
- GL version: 4.6.0 - Build <IP_ADDRESS>81
- MAX_TEXTURE_SIZE: 16384

Screens:
- screen 1: resolution 1920x1080, scale 1.0

Plugins:
- clEsperanto: 0.7.4
- console: 0.0.2
- svg: 0.1.4

Any other relevant information:

Additional context
That's propably a low-priority bug. No hurry from my side :-)
Happy Easter!

Unfortunately we've already seen several reports of this, #1566 and #1237. We need to look in more. Fine to leave this open though as it is another example

I can't reproduce this, it looks like this was fixed by https://github.com/vispy/vispy/pull/2090
If it pops up again, please re-open or make a new issue.


Project: LocalGuideAI

Project name
LocalGuideAI
Description
A local guide in the form of a simple .NET MAUI app that uses ChatGPT AI.
Project Repository URL
https://github.com/danzuep/LocalGuideAI
Project video
https://github.com/danzuep/LocalGuideAI/blob/main/Assets/Videos/Android.mp4
Team members
danzuep

Alternative video links:

Android
PC


WIP Edit read.me (2)

/azp run  Public BuildXL PR Validation

/azp run  Public BuildXL PR Validation


add support for edit localizations files

Hi, any plan for add support for export and import localization file from core files?
Thanks for good work

We don't support repacking yet, and this is a required step in order to make localization and other modding stuff possible.
Stay tuned, at some day this feature will see the light 🙂

thanks for good work
I look forward to it

Hi, project doesn't update in like 2 month, you guys still work on it?

Hello @YouKnow-sys,
Don't really. Sadly I don't have free time to work on this project.
I see there's no much mods for Death Stranding were created since the game was released that makes me thinking that no one was able to create suitable modding tools since that.
As I said before, at some day this feature will see the light. I had a lot of ideas to implement and I feel very sorry for abandoning this amazing project. By the way, this project is also open-source, so you can try to make your best and contribute to it.


how to change the default port 9000?

Thanks for the suggestion @lovepocky this is added in 095fe0bf350c2436d688e8bc0fe3df94d7f3ec06


Item/armor durability variable?

Is there a variable for the durabilities of your gear?
If not can you please add it? Would be really helpfull!

Sorry for the late response, I was sleeping!
I will add held item durability in the next update!

And armor durability too!

Ah no worries, thanks in advance!

{held_item_durability}
{helmet_durability}
{chestplate_durability}
{leggings_durability}
{boots_durability}
{offhand_durability}
Have all been added to v3!
as well as:
;durability, slot_number, variable_name;

and
getItem(Number slot).durability

on javascript


Point bruteforce favours further iterations than closer ones because they are earlier in time

read title

pepoG

pe po gee

Fixed in PR https://github.com/CodyNinja1/TMIBruteforceGUI/pull/36/files

busy ness


MetricFilters doesn't not filter out external collector metrics.

It seems metric filters in scollector are not working for metrics published by external collectors. Though if I try to filter out the complete external collector using Filter key, it works but filtering out individual metrics using MetricFilters key doesn't work.

I think the filtering is done as part of the collector code, which isn't executed for external collectors. I'll take a look at it when I have some time, hopefully next week.

Thanks @gbrayut. We are writing external collectors in different languages to get the metrics from different sources and want to use scollector as a container and to leverage on its core features as much as possible like batching, internal buffering, filters etc instead of building them outside.

Possibly related https://github.com/bosun-monitor/bosun/issues/597

@gbrayut the filtering is done in AddTS (which is used for almost everything except external collectors), I don't know why external collectors are pushed directly in the channel of openstsdb.DataPoint
Quick fix would be to add a check
if skipMetric(dp.Metric) {
    continue
}

just before the lines
https://github.com/bosun-monitor/bosun/blob/master/cmd/scollector/collectors/program.go#L153
and
https://github.com/bosun-monitor/bosun/blob/master/cmd/scollector/collectors/program.go#L167
Real fix would be to understand why Add or AddTS is not used here

Is any priority decided for this issue?


Accept a reveal timeout param for open channel task

In https://github.com/raiden-network/raiden/pull/4999 i introduce a new parameter reveal_timeout in the PATCH channel endpoint. This PR enables the OpenChannelTask to accept this new parameter.
NOTE: Do not merge until the above PR is merged.

No needs for this at the moment.


Wrong in array display

For those two different arrays, the view displays the same content now.

It is fixed in version 0.1.2.


Running docker image doesn't work

I want to use this to run a classic mycroft install off of.
Running:
docker run -p 6712:6712 -p 8086:6712 --name local_backend ghcr.io/openvoiceos/local-backend:dev
Shows:
2024-03-01 22:50:13.272 - OVOS - ovos_config.utils:init_module_config:36 - INFO - Configuring ovos_local_backend config
2024-03-01 22:50:13.280 - OVOS - ovos_config.utils:init_module_config:61 - INFO - Updating configuration at: /root/.config/OpenVoiceOS/ovos.conf
sqlite:////root/.local/share/ovos_backend.db
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 145, in __init__
self._dbapi_connection = engine.raw_connection()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 3293, in raw_connection
return self.pool.connect()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 452, in connect
return _ConnectionFairy._checkout(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 1268, in _checkout
fairy = _ConnectionRecord.checkout(pool)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 716, in checkout
rec = pool._do_get()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/impl.py", line 168, in _do_get
with util.safe_reraise():
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/util/langhelpers.py", line 147, in __exit__
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/impl.py", line 166, in _do_get
return self._create_connection()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
return _ConnectionRecord(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 678, in __init__
self.__connect()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 902, in __connect
with util.safe_reraise():
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/util/langhelpers.py", line 147, in __exit__
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 898, in __connect
self.dbapi_connection = connection = pool._invoke_creator(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/create.py", line 637, in connect
return dialect.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/default.py", line 616, in connect
return self.loaded_dbapi.connect(*cargs, **cparams)
sqlite3.OperationalError: unable to open database file

The above exception was the direct cause of the following exception:                                                                                [7/56]

Traceback (most recent call last):
File "/usr/local/bin/ovos-local-backend", line 8, in <module>
sys.exit(main())
File "/usr/local/lib/python3.10/dist-packages/ovos_local_backend/__main__.py", line 14, in main
start_backend(args.flask_port, args.flask_host)
File "/usr/local/lib/python3.10/dist-packages/ovos_local_backend/backend/__init__.py", line 56, in start_backend
app = create_app()
File "/usr/local/lib/python3.10/dist-packages/ovos_local_backend/backend/__init__.py", line 24, in create_app
app, db = connect_db(app)
File "/usr/local/lib/python3.10/dist-packages/ovos_local_backend/database.py", line 35, in connect_db
db.create_all()
File "/usr/local/lib/python3.10/dist-packages/flask_sqlalchemy/extension.py", line 884, in create_all
self._call_for_binds(bind_key, "create_all")
File "/usr/local/lib/python3.10/dist-packages/flask_sqlalchemy/extension.py", line 865, in _call_for_binds
getattr(metadata, op_name)(bind=engine)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/sql/schema.py", line 5796, in create_all
bind._run_ddl_visitor(
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 3243, in _run_ddl_visitor
with self.begin() as conn:
File "/usr/lib/python3.10/contextlib.py", line 135, in __enter__
return next(self.gen)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 3233, in begin
with self.connect() as conn:
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 3269, in connect
return self._connection_cls(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 147, in __init__
Connection._handle_dbapi_exception_noconnection(
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 2431, in _handle_dbapi_exception_noconnection
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 145, in __init__
self._dbapi_connection = engine.raw_connection()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/base.py", line 3293, in raw_connection
return self.pool.connect()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 452, in connect
return _ConnectionFairy._checkout(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 1268, in _checkout
fairy = _ConnectionRecord.checkout(pool)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 716, in checkout
rec = pool._do_get()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/impl.py", line 168, in _do_get
with util.safe_reraise():
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/util/langhelpers.py", line 147, in __exit__
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/impl.py", line 166, in _do_get
return self._create_connection()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
return _ConnectionRecord(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 678, in __init__
self.__connect()
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 902, in __connect
with util.safe_reraise():
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/util/langhelpers.py", line 147, in __exit__
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/pool/base.py", line 898, in __connect
self.dbapi_connection = connection = pool._invoke_creator(self)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/create.py", line 637, in connect
return dialect.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/default.py", line 616, in connect
return self.loaded_dbapi.connect(*cargs, **cparams)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) unable to open database file
(Background on this error at: https://sqlalche.me/e/20/e3q8)

I just started using this after finding out the other project was dead, when i tried it i dont get that but with docker ps i get my images and this one just says "restarting" all the time under STATUS. No clue if this could be related but I'm also not the best with docker.


Layout/EmptyLineBetweenDefs and Style/SingleLineMethods break on ruby 3 with endless defs

I was trying out Ruby 3 new single line def syntax.

Expected behavior
To show linting errors and warnings, or success output (for correct code).
Inspecting 1 file
.

1 file inspected, no offenses detected

Actual behavior
Rubocop breaks and tells me to file an issue here:
root@cb4bbf7a522c:/usr/src/app# rubocop bug.rb
Inspecting 1 file
An error occurred while Layout/EmptyLineBetweenDefs cop was inspecting /usr/src/app/bug.rb:6:2.
To see the complete backtrace run rubocop -d.
An error occurred while Style/SingleLineMethods cop was inspecting /usr/src/app/bug.rb:6:2.
To see the complete backtrace run rubocop -d.
C

Offenses:

bug.rb:8:18: C: Naming/MethodParameterName: Method parameter must be at least 3 characters long.
  def initialize(a)
                 ^

1 file inspected, 1 offense detected

2 errors occurred:
An error occurred while Layout/EmptyLineBetweenDefs cop was inspecting /usr/src/app/bug.rb:6:2.
An error occurred while Style/SingleLineMethods cop was inspecting /usr/src/app/bug.rb:6:2.
Errors are usually caused by RuboCop bugs.
Please, report your problems to RuboCop's issue tracker.
https://github.com/rubocop-hq/rubocop/issues

Mention the following information in the issue report:
1.6.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.3.0, running on ruby 3.0.0 x86_64-linux)

Steps to reproduce the problem
Create bug.rb with this content:
# frozen_string_literal: true

# bug
class Foo
  # return the instance as value object
  def self.run(...) = new(...).tap(&:run)

  def initialize(a)
    @a = a
  end

  def run
    puts @a
  end
end

run rubocop bug.rb
RuboCop version
root@cb4bbf7a522c:/usr/src/app# rubocop -V
1.6.1 (using Parser <IP_ADDRESS>, rubocop-ast 1.3.0, running on ruby 3.0.0 x86_64-linux)

Thank you very much for your answer. I thought, mistakenly, that I was in the latest version. When I updated the problem was indeed solved.


Spreadsheet name

Update spreadsheet name to include platform/customer name for when multiple instances of the tool is set up

This has been included in v1.3.  Instead of using the customer/platform name, the file now generates with a random GUID as its name.


Unable to delete a user on Craft Nitro instance because of MySQL read timeout

Description
I'm attempting to delete a user with 232 entries and the database times out on this. I'm using MySQL and a Nitro instance. Perhaps we can bump the default read timeout to be more than 15 seconds on Nitro?
Steps to reproduce

Have a user with a lot of entries.
Delete that user and choose to delete all of their entries.

Additional info
The failing SQL is:
UPDATE `matrixblocks` SET `deletedWithOwner`=1 WHERE `id`='123456'

Nitro version: 1.0.1
Multipass version: 1.4.0

This is the error message:
Lost connection to MySQL server during query.Read timeout (15 seconds) reached.
Error code 2013.

I don't see anything with a value of 15 though.

@ryanpcmcquen which version of Craft CMS are you running. Do you have any plugins that might be hooking into the user events (that you know of)?
I'm going to try to replicate on my end

Craft CMS 3.4.30, the plugins shouldn't matter since even the direct SQL fails. But I don't have any that I know of that would affect user deletion.

@ryanpcmcquen alright, I have my environment setup to replicate. Added 5k entries for a single user and will try. I'm on 3.5.8 but like you said it should not matter (missed that point in your description).

@jasonmccallister, any luck?

@ryanpcmcquen I am unable to reproduce this. I am running the following Nitro machine:
Using config: /Users/jasonmccallister/.nitro/nitro-dev.yaml
------
php: "7.4"
mounts:
- source: ~/dev/plugins-dev
  dest: /home/ubuntu/sites/plugins-dev
databases:
- engine: mysql
  version: "5.7"
  port: "3306"
sites:
- hostname: plugins.nitro
  webroot: /home/ubuntu/sites/plugins-dev/web

I added 5000 entries and deleted a user and transferred to another user and it happened quickly. I was on the latest Craft (<IP_ADDRESS>). I'm going to downgrade to 3.4.30. I don't know of any issues related to removing users and updates.
Can you try nitro db restart to restart the database container and see if that resolves it?

We just released Nitro 2 where we switched from Multipass to Docker and added a ton of new features. Please see the announcement for more details.
This issue was specific to Multipass so we are going to close this out. Please see the documentation on upgrading from Nitro 1.


record ID should be set cascade entities for known uuid entities

@fuss86  thanks for this
@carlspring it looks good to me too, and can be merged

@fuss86 : Thanks for your fixes!
@sbespalov : Thanks for reviewing!


Remove redundant default argument values in _bind_methods

DirAccess::list_dir_begin, DisplayServer::is_touchscreen_available and TileMapLayer::notify_runtime_tile_data_update have no arguments since Godot 4, the default argument declarations in _bind_methods are redundant.

While these changes are correct they do break hashes which in turn break binds, unsure how to ensure the binds are properly associated, might need to bind compatibility methods to ensure they are registered correctly, assuming the existing methods work in extensions
CC @dsnopek

Note that TileMapLayer::notify_runtime_tile_data_update is likely a copy/paste error, and not a leftover from older versions as it wasn't in 4.0

might need to bind compatibility methods to ensure they are registered correctly

Yeah, if the methods are bound, then adding a compatibility method is the way to go. It's possible even the same function pointer could be used, but just with a ClassDB::bind_compatibility_method() with the argument defaults added back.


[BUG] Auto scan not turning off consistenly

Version
<IP_ADDRESS>
What platform are you using?
Android
OS Version
Stock Android 14 on Pixel 7 Pro
What happened?
I thought I have auto scan turned off in Settings -> Auto scan -> Discover and add documents automatically. But occasionally the app still captures only a portion of what the camera screen shows, and then doesn't show the crop screen with the magnifier tool.
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@48-mq that s different from auto scan:

auto-scan: if a "region" is discovered and not moving for a second then it will be automatically captured without you having to press the capture button
what you are seeing is a different behavior: if you capture, without batch mode, and a region is discovered matching some criteria (size, ...) then it is automatically added without you having to confirm the region. It is for things to get faster

The second feature can be deactivated in document-detection settings (force crop confirmation or something like that).


HttpSession for websocket

Hi,
Is there any way of getting http session in websocket? I believe it maybe impossible for @OnWebSocketMessage, but it should be possible from upgrade http request when socket is about to open.
What I've tried:
session.getUpgradeRequest().getSession()

Unfortunately always return null.
session.getUpgradeRequest().getCookies()

Returns session cookie just fine.
Anyone have some insight on that? I'm I doing something wrong?

Would this explain the problem?
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/websocket/api/UpgradeRequest.html#getSession--

@jakaarl Yep, this pretty much close the issue.
So how am I able to design some access control for web socket without session?
Can I make WebSocketCreator  using Spark? Jetty doc says this would allow me to obtain Http Session.

@Dobosz see:

https://auth0.com/blog/auth-with-socket-io/
https://devcenter.heroku.com/articles/websocket-security

I guess it would be a good idea if Spark provided access to the session, or better still, supported securing web socket sessions with tokens.

Thanks I will look into that.
Can I access session storage from Spark, so I can retrieve the session? Assuming cookie authentication of course.
How would session with/by tokens work? Would Spark user extract token from Json and provide it to some kind of session manager? Or are you going for some kind of mark token first and session will be provided to you?

+1 for this.
How is one supposed to send events to targeted individuals based upon their session

Would this explain the problem?
http://download.eclipse.org/jetty/stable-9/apidocs/org/eclipse/jetty/websocket/api/UpgradeRequest.html#getSession--

The link is broken :confused:

Fixed link.
https://www.eclipse.org/jetty/javadoc/jetty-9/org/eclipse/jetty/websocket/api/UpgradeRequest.html#getSession()

Just a small comment here from the stratosphere.  You certainly can get access to the HttpSession in an web socket upgrade request if you're on the server side (which most of us are)!   I use the session to help validate that my web socket should open.
That being said, all of the comments and concerns with regards to HttpSession lifecycle are certainly relevant.


updatedAt field is not updated

Describe the bug
The updatedAt field on my types is not getting updated when making updates to the database.
To Reproduce
I have a model like the following:
type Example {
    id: ID! @unique
    createdAt: DateTime!
    updatedAt: DateTime!
    text: String
}

I create an Example. Then i update the text on the created example and updatedAt is not updated. It still remains the same as the createdAt field.
Expected behavior
I would expect updatedAt to change when any field is updated on the type.
Versions (please complete the following information):
"prisma-binding": "2.1.6",
"prisma-yml": "1.19.1",
"graphql-yoga": "1.16.7",
"prisma": "1.19.1",

I see other bugs related to this issue, but i am still seeing this as a problem.

@prolink007 : Which connector are you using?

@prolink007 : Which connector are you using?

I am not sure what you mean by "connector". This is mySql, if that is what you are asking.

Any news on this issue? Still looking for assistance.

@prolink007 : We have a dedicated test case for this behaviour. I just ran it with the MySQL connector and it passes as expected. Do you have more details that would help me reproduce this? My guess is that you are running with a really old version of the Prisma core.

@mavilein How do i check my prisma core version? I showed you the versions i am using in the original post. Are those the correct versions? Do you need the version of something else?

@prolink007 : Open the url /management on your prisma server, e.g.http://localhost:4466/management on localhost. Then perform the following query:
{
  serverInfo {
    version
    commit
    primaryConnector
  }
}

Let's see what this will tell us :-)

@mavilein
{
  "data": {
    "serverInfo": {
      "version": "1.8.4",
      "commit": "86cf1d1adacded29c2b898d2d617b30b86fba483"
    }
  }
}

primaryConnector was not available so i removed it from the query.

@prolink007 : As i guessed you are running a really old version of the Prisma server. Please upgrade to the latest version and your issue will be fixed :-)

@mavilein How do i upgrade the prisma server? All the versions i have that are prisma related seem to be the latest version.

Prisma server is dockerized. It should be in your docker-compose.yml file I guess ?

Had to update the
services:
  prisma:
    image: prismagraphql/prisma:1.20

In my yml file.


Feature request: stop parsing messages from file after a maximum time

This would allow to parse the first x seconds of a MIDI file, and stop early
I can submit a pull request if you want @olemb

Great idea, Pull Request welcome.
I'd like to add that for it to be a really good fit in the library, I think it would need to be a bit more generic and allow to choose any range.
This opens a can of worms though:

What do we do with messages that provide context like tempo, signature, program changes… that aren't in the range but may be needed to give a proper playback experience?


Nuxt generate does not work with <style lang=

Version
@nuxtjs/tailwindcss:
nuxt:
Reproduction Link

Steps to reproduce
What is Expected?
What is actually happening?

wrong button


Login fails?

I don't seem to be able to Login? I'm not sure if I am doing something wrong.

@jbowkett84 can you please add some context: app version, device, login provider (google, facebook, OSM)

Thanks for the message Bogdan, it's working now that I have tried it again this morning.
I'm on iOS, iPhone, login by OSM, version 1.5.3(1).
James
James Bowkett MSc FGS
+447870733284
<EMAIL_ADDRESS>Sent from my iPhone

On 5 May 2017, at 14:57, Bogdan Sala<EMAIL_ADDRESS>wrote:
@jbowkett84 can you please add some context: app version, device, login provider (google, facebook, OSM)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for your quick answer. I will close this now.


search an individual column?

Can someone please help me with the code to search an individual column within the table?  I'm very new to programming so please excuse my ignorance.  Thanks in advance for any help.

https://datatables.net/reference/option/searchCols

https://github.com/aldeed/meteor-tabular#search-in-one-column


Skott own modules are not installed

Hi,
Thanks for your work.
I've installed your package globally but I get an error
Error
➜  sgo ✗ skott src/App.tsx

 Running Skott from entrypoint: src/App.tsx
 Processed 1 file (2.285ms)
 ✓ no circular dependencies found (depth=Infinity)
 Third-party dependencies: ❌
 --> Use --trackThirdPartyDependencies to enable tracking.
 Built-in dependencies: ❌
 --> Use --trackBuiltinDependencies to enable tracking.
 Type-level only dependencies: ✅

 Skott exited with code 1
node:fs:1438
  handleErrorFromBinding(ctx);
  ^

Error: ENOENT: no such file or directory, scandir '/Users/aze/.config/yarn/global/node_modules/skott/node_modules/skott-webapp/dist'
    at readdirSync (node:fs:1438:3)
    at totalist (/Users/aze/.config/yarn/global/node_modules/totalist/sync/index.js:6:12)
    at module.exports (/Users/aze/.config/yarn/global/node_modules/sirv/build.js:149:3)
    at openWebApplication (file:///Users/aze/.config/yarn/global/node_modules/skott/dist/bin/ui/webapp.js:45:20)
    at displaySkott (file:///Users/aez/.config/yarn/global/node_modules/skott/dist/bin/main.js:134:9) {
  errno: -2,
  syscall: 'scandir',
  code: 'ENOENT',
  path: '/Users/aze/.config/yarn/global/node_modules/skott/node_modules/skott-webapp/dist'
}

I checked here /Users/aze/.config/yarn/global/node_modules/skott and found out that packages are not installed.
Tried to install them myself using yarn installbut I end up on a maybe encrypted variable @skott%2fconfig
Yarn-error.log
Arguments:
  /Users/aze/.nvm/versions/node/v16.19.0/bin/node /opt/homebrew/Cellar/yarn/1.22.19/libexec/bin/yarn.js install

PATH:
  /Users/aze/.nvm/versions/node/v16.19.0/bin:/Users/aze/.rbenv/shims:/Users/aze/Library/Caches/fnm_multishells/1122_1671351776860/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Users/aze/Library/Android/sdk/emulator:/Users/aze/Library/Android/sdk/platform-tools:/Users/aze/Library/Android/sdk/tools:/Users/aze/Library/Android/sdk/tools/bin

Yarn version:
  1.22.19

Node version:
  16.19.0

Platform:
  darwin arm64

Trace:
  Error: https://registry.yarnpkg.com/@skott%2fconfig: Not found
      at Request.params.callback [as _callback] (/opt/homebrew/Cellar/yarn/1.22.19/libexec/lib/cli.js:66145:18)
      at Request.self.callback (/opt/homebrew/Cellar/yarn/1.22.19/libexec/lib/cli.js:140890:22)
      at Request.emit (node:events:513:28)
      at Request.<anonymous> (/opt/homebrew/Cellar/yarn/1.22.19/libexec/lib/cli.js:141862:10)
      at Request.emit (node:events:513:28)
      at IncomingMessage.<anonymous> (/opt/homebrew/Cellar/yarn/1.22.19/libexec/lib/cli.js:141784:12)
      at Object.onceWrapper (node:events:627:28)
      at IncomingMessage.emit (node:events:525:35)
      at endReadableNT (node:internal/streams/readable:1358:12)
      at processTicksAndRejections (node:internal/process/task_queues:83:21)

npm manifest:
  {
    "name": "skott",
    "version": "0.12.1",
    "description": "Automatically construct and visualize Graphs generated from your JavaScript and TypeScript project",
    "author": "Antoine Coulon",
    "license": "MIT",
    "repository": {
      "type": "git",
      "url": "git+https://github.com/antoine-coulon/skott.git"
    },
    "bugs": {
      "url": "https://github.com/antoine-coulon/skott/issues"
    },
    "main": "dist/index.js",
    "bin": {
      "skott": "./dist/bin/cli.js"
    },
    "type": "module",
    "exports": {
      ".": "./dist/index.js"
    },
    "types": "./dist/index.d.ts",
    "dependencies": {
      "@typescript-eslint/typescript-estree": "^5.40.0",
      "compression": "^1.7.4",
      "digraph-js": "^2.0.2",
      "estree-walker": "^3.0.1",
      "fs-tree-structure": "0.0.1",
      "kleur": "^4.1.5",
      "ligie": "^0.0.6",
      "meriyah": "^4.2.1",
      "openurl": "^1.1.1",
      "ora": "^6.1.2",
      "polka": "^0.5.2",
      "sade": "^1.8.1",
      "sirv": "^2.0.2",
      "skott-webapp": "0.0.3",
      "table": "^6.8.0"
    },
    "devDependencies": {
      "@nodesecure/eslint-config": "^1.3.0",
      "@skott/config": "0.0.1",
      "@types/chai": "^4.3.0",
      "@types/compression": "^1.7.2",
      "@types/mocha": "^9.0.0",
      "@types/node": "^16.11.12",
      "@types/polka": "^0.5.4",
      "@types/sade": "^1.7.4",
      "chai": "^4.3.4",
      "eslint": "^8.4.1",
      "eslint-config-prettier": "^8.3.0",
      "eslint-import-resolver-typescript": "^2.5.0",
      "eslint-plugin-import": "^2.26.0",
      "eslint-plugin-prettier": "^4.0.0",
      "memfs": "^3.4.6",
      "mocha": "^9.1.4",
      "prettier": "^2.5.1",
      "rimraf": "^3.0.2",
      "ts-node": "^10.8.1",
      "typescript": "^4.5.2"
    },
    "files": [
      "dist",
      "./README.md"
    ],
    "keywords": [
      "javascript",
      "graph",
      "nodejs",
      "visualization",
      "module",
      "dependencies"
    ],
    "scripts": {
      "build": "rimraf ./dist && tsc --project tsconfig.build.json",
      "lint": "eslint .",
      "prestart": "pnpm run build",
      "start": "node dist/bin/cli.js",
      "test": "mocha --parallel"
    }
  }

yarn manifest:
  No manifest

Lockfile:
  No lockfile

Any idea how to solve this ?

@bam-charlesbo Hi, thanks for reporting that issue. I usually try with npm and pnpm and it seems to work as of now, could you tell me if this works for you by installing the package using npm please?
Might be a specific issue related to Yarn, so I'd be happy to solve that very quickly
FYI if you want to test skott without the webapp, you can supply another displayMode e.g: skott --displayMode=file-tree or skott --displayMode=graph

@bam-charlesbo it seems that it won't work when Skott is installed as a local dependency rather than a cli. I need to fix that path resolution for the dependency 'skott-webapp' which is the standalone package used to render the application.
Thanks for reporting that!

@bam-charlesbo could you please try with the latest version I just published 0.12.2? It should normally fix the problem

Yes it works !
I updated the package and tried the same command.
Well done !
Thanks for your reactivity 🤘

@bam-charlesbo thanks, happy to know it works now :) thanks again for reporting that!


Ipad Landscape

Thanks for  #121. But if the ipad is in landscape mode it only show an empty grey modal and it never go away.

+1
I updated the plugin to version 0.9.2 and still not working.
Thanks

I have the same problem on iPhone 4, iOS 7.1.2


To enable Google Translate functionality for multiple languages.

Issue Overview:
We need to implement Google Translate functionality to enable multilingual support on our platform. This will require integrating the Google Translate widget into the designated container to provide users with an effortless translation experience.
Tasks:

Integrate Google Translate Widget:

Embed the Google Translate widget within the designated container to offer language translation options to users.

Customize Appearance:

Utilize Tailwind CSS (or a relevant styling framework) to tailor the visual appearance of the translation container, ensuring it aligns with the overall design of the platform.

Language Support:

Ensure the widget supports all specified target languages.
Test translations across these languages to confirm accuracy and a smooth language-switching experience.

Responsive Design:

Verify that the translation feature functions seamlessly across various screen sizes (mobile, tablet, desktop).

Expected Outcome:

Users can select their preferred language from the translation container.
The page content should be accurately translated without interrupting the user experience.
The design and layout should remain consistent with the rest of the platform's interface.

@rebornstar1 are you working on it

I’d like to take on the task of integrating the Google Translate widget to enable multilingual support on your platform. I will ensure it’s styled using Tailwind CSS, supports the required languages, and is fully responsive. I'll keep you updated as I progress.

@SnehaPatil47 you can proceed but use material ui as ui is based on it

Thank you
On Mon, Oct 21, 2024, 7:56 AM Vikas Sharma @.***> wrote:

Assigned #23 https://github.com/sharmavikas4/MERN_BLOG/issues/23 to
@SnehaPatil47 https://github.com/SnehaPatil47.
—
Reply to this email directly, view it on GitHub
https://github.com/sharmavikas4/MERN_BLOG/issues/23#event-14756443816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCNBALZEUE2PSFN5LKJ2SHLZ4RQ5TAVCNFSM6AAAAABPSAXRJGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUG42TMNBUGM4DCNQ
.
You are receiving this because you were assigned.Message ID:
@.***>

@SnehaPatil47 what's the progress


Bug: Schedule Conflict Error for Same Date and Time with Different Names

Description:
The application throws a conflict error when attempting to add multiple schedules with the same date and time for the same contact, even though the names are different. According to the expected behavior, schedules with different names should be allowed at the same date and time.
Prerequisites:

At least one contact must be available in the system.

Steps to Reproduce:

Execute the command to add a schedule:
add-schedule c/1 n/Dinner d/10-10-2024 t/1800

Execute another command to add a different schedule with the same date and time but a different name:
add-schedule c/1 n/Lunch d/10-10-2024 t/1800

Expected Behavior:
Both schedules should be added successfully, as the names are different. Only schedules with the exact same name, date, and time should trigger a conflict.
Actual Behavior:
The program shows an error:
This schedule conflicts with an existing schedule.
Screenshot:

This is no longer required as we don't allow multiple schedules with the same date and time


Cannot connect after flashing to S3-box.

Ok, I do not know what I am missing here.
I first tried the S3-BOX-lite - it does not prompt for the password. Just display the screen "No WiFi" after a few seconds. My smartphone connects to the wifi ap, but it never asks for the wifi-credentials.
Then I downloaded the github code, add the wifi credentials to the code, flash that and the device goes into a boot-loop, Screen stay black all the time.
Then I tried a S3-BOX by flashing the code from ESPHOME.io/projects. Selected the correct device, but after flashing the wifi-credentials problem is the same. Never asks for the credentials and screen turn to "no Wi-fi" display.
It was picked up by HA integrations, but clicking on "configure" does not do anything, it just tries to connect without any luck. Connection failed
Do I have to connect the device into the Yellow that runs HA or into any PC connected to the newwork?
Even connecting it directly to the yellow that is running HA, does not make any difference.

If you were able to install the firmware from https://esphome.io/projects then you've got a connection to the device and shouldn't need to plug it in to Yellow. Think I experienced something similar upon initial install, but then I was able to just select "Change wifi" on the pop up from the projects site to configure wifi again (after being fairly confident I just had done so after initial installation).

The problem was that I connected to the ESP-BOX3 in "download mode" to flash. That is wrong. Just need to power on and connect to USB to flash. Then it worked.
I used Willow before and it required it to be in "download mode", therefore that's how I was used to doing it.