Async Patient Source

Summary
Added functionality to handle an asynchronous patient source which queries a FHIR server to retrieve patient data and records
New Behavior
This PR sets up cql-exec-fhir to process async PatientSources which will eventually be able to get passed in after updates to fqm-execution. This PR does the legwork in cql-exec-fhir that will eventual enable users to pass in a simple list of patientIDs and a fhir server url though fqm-execution for measure evaluation, data requirements, and gaps in care, rather than an entire patient bundle or full fleshed out patient source.
Code Changes

Added AsyncPatientSource class which creates an axios instance with the passed in server url and defines the asynchronous functions currentPatient() and nextPatient() which are called by cql-execution during eCQM calculation
Added AsyncPatient class which gets returned by currentPatient() and nextPatient(), stores FHIR patient data, and implements an asynchronous version of findRecords() which will pull all the resources of a given type that reference the patient
Added Patient compartment definition to identify how resources can reference patient
Updated babelrc to correctly compile using async/await terminology
Added Prettier
Updated eslint config to use ECMA 12
Added unit testing

Testing Guidance
Dang prettier really did a number on these files... those changes can largely be ignored. The code that actually needs a rigorous review is the AsyncPatientSource and AsyncPatient classes in fhir.js as well as the changes to package.json, the compartment definition file, and the prettier + eslint + babel config changes.
These changes can be integration tested by making a few changes to fqm execution:

Add the following classes to src/types/CQLExecFHIR.d.ts:

  class AsyncPatient extends FHIRObject implements IPatient {
    findRecords(profile: string): FHIRObject;
  }

  export class AsyncPatientSource {
    constructor(serverInfo: string);
    loadPatientIds(ids: string[]): void;
    currentPatient(): AsyncPatient | undefined;
    nextPatient(): AsyncPatient | undefined;
    reset: void;
    static FHIRv401(serverInfo: string): AsyncPatientSource;
  }

Add the following at line 131 of cli.ts:

  import * as cqlExecFhir from 'cql-exec-fhir';
  const TEST_IDS = ['numer-EXM130', 'denom-EXM130'];
  const patientSource = cqlExecFhir.AsyncPatientSource.FHIRv401('http://localhost:3000/4_0_1');
  patientSource.loadPatientIds(TEST_IDS);

Add await before executor.exec on line 101 of src/execution/Execution.ts. The line should now read:
const results = await executor.exec(patientSource, executionDateTime);
Copy cql-execution from repository here
Run npm link path/to/cql-execution/directory
Run npm link path/to/cql-exec-fhir/directory
Run npm run build
Clear your test server database by running npm run db:reset
Start the test server at http://localhost:3000
Upload the EXM130 transaction bundle to the test server. Slack me if you don't know how to do this
Run node build/cli.ts  -m "path/to/EXM130/Measure/bundle" -o "reports" -p "path/to/EXM130/patient/bundle" -s "2019-01-01" -e "2019-12-31" -f > output.json
Note, the -f flag here will cause fqm-execution to compile and AsyncPatientSource instead of using in the pased-in patient bundle, however an error will be thrown if the patientBundles arg is entirely omitted
Check the ouput.json file and ensure that we have exactly 1 numerator and 1 denominator patient :)
If you wanna be super rigorous, check the test server logs and ensure that it is searching for patients and other fhir resources during the measure calculation.

Since we brought prettier into the project, it's a good idea to also add eslint-config-prettier to the project since it deconflicts some of the rules between eslint and prettier. Installation should be easy:
yarn add -D eslint-config-prettier

Add this to eslintrc:
  "extends": ["eslint:recommended", "prettier"]


Demo is broken because of reducer bug with Symbols

Neither of the array buttons in the demo work because of this bug in redux-actions. The actions are dispatched and logged correctly, but the reducer doesn't transform the state correctly when the action type is a Symbol. No problems with redux-logger itself -- just letting you know.

Wow, thanks, didn't pay attention. I don't usually use Symbols (same reason https://github.com/acdlite/redux-actions/issues/20#issuecomment-134340125), just added support in #14 and updated demo.
I remove Symbol() from demo.

FYI, this issue was just fixed in<EMAIL_ADDRESS>so the old demo should be fine if you bump the dep! :)


Task 9, 10

@singharvind09
Update a PR number in respective task tracker
Task -5
Code verified. Complete a code
Task -6
Code verified. Change default activity name and provide annotations

Task -7
Code verified. Change default activity name and provide annotations
Task -8
Code verified. Change default activity name and provide annotations
Task -9
Code verified. Change default activity name and provide annotations
Task -10
Code verified. Change default activity name and provide annotations
Task -11
Code verified. Change default activity name and provide annotations


RecursionError： maximum recursion depth exceeded when debug unittest

VS Code version
1.60.2
Extension version
python: v2021.10.1365161279
OS type
Linux
OS version
ubuntu 20.04
Python distribution
Anaconda
Python version
3.9.7 64-bit
Language server
Pylance
Expected behaviour
No exception
Actual behaviour
============================= test session starts ==============================
platform linux -- Python 3.9.7, pytest-6.1.2, py-1.11.0, pluggy-0.13.1
rootdir: /apps/omega
plugins: cov-2.10.1
collected 1 item
tests/fetcher/test_abstract_quotes_fetcher.py 提示：当前环境 pandas 版本高于 0.25，get_price 与 get_fundamentals_continuously 接口 panel 参数将固定为 False
注意：0.25 以上版本 pandas 不支持 panel，如使用该数据结构和相关函数请注意修改
auth success
Frame skipped from debugging during step-in.
Note: may have been skipped because of "justMyCode" option (default == true). Try setting "justMyCode": false in the debug configuration (e.g., launch.json).
Traceback (most recent call last):
File "_pydevd_bundle/pydevd_cython.pyx", line 1664, in _pydevd_bundle.pydevd_cython.ThreadTracer.call
RecursionError: maximum recursion depth exceeded
Fatal Python error: _Py_CheckRecursiveCall: Cannot recover from stack overflow.
Python runtime state: initialized
Thread 0x00007ff70b524700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 316 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/queue.py", line 180 in get
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/api.py", line 364 in dispatch_events
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/api.py", line 199 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydev_bundle/pydev_monkey.py", line 1054 in call
Thread 0x00007ff70c526700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 312 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/utils/delayed_queue.py", line 54 in get
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/inotify_buffer.py", line 43 in read_event
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/inotify.py", line 129 in queue_events
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/api.py", line 148 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydev_bundle/pydev_monkey.py", line 1054 in call
Thread 0x00007ff70cd27700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/inotify_c.py", line 285 in read_events
File "/root/miniconda3/envs/omega/lib/python3.9/site-packages/watchdog/observers/inotify_buffer.py", line 88 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydev_bundle/pydev_monkey.py", line 1054 in call
Thread 0x00007ff73affd700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 316 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 574 in wait
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 246 in _on_run
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 46 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
Thread 0x00007ff73b7fe700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 316 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 574 in wait
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 200 in _on_run
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 46 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
Thread 0x00007ff73bfff700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 312 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 574 in wait
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_timeout.py", line 43 in _on_run
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 46 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
Thread 0x00007ff74093e700 (most recent call first):
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 219 in _read_line
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 237 in _on_run
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 46 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
Thread 0x00007ff74113f700 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 316 in wait
File "/root/miniconda3/envs/omega/lib/python3.9/queue.py", line 180 in get
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 382 in _on_run
File "/root/.vscode-server/extensions/ms-python.python-2021.10.1365161279/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 46 in run
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 973 in _bootstrap_inner
File "/root/miniconda3/envs/omega/lib/python3.9/threading.py", line 930 in _bootstrap
Current thread 0x00007ff742b92180 (most recent call first):
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 58 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 47 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 32 in format_cb
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 37 in _format_callbacks
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 76 in _future_repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 51 in _repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 61 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 47 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 32 in format_cb
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 37 in _format_callbacks
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 76 in _future_repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 51 in _repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 61 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 47 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 32 in format_cb
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 37 in _format_callbacks
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 76 in _future_repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 51 in _repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 61 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 47 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 32 in format_cb
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 37 in _format_callbacks
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 76 in _future_repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 51 in _repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 61 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 40 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 47 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 32 in format_cb
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 37 in _format_callbacks
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/base_futures.py", line 76 in _future_repr_info
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 139 in repr_instance
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 62 in repr1
File "/root/miniconda3/envs/omega/lib/python3.9/reprlib.py", line 52 in repr
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 38 in _format_args_and_kwargs
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 56 in _format_callback
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/format_helpers.py", line 23 in _format_callback_source
File "/root/miniconda3/envs/omega/lib/python3.9/asyncio/events.py", line 51 in _repr_info
...
Steps to reproduce
Not 100% producible. Occurs more on virtual machines runs on one ESXi servers, but not always.
Logs
No response
Code of Conduct

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

we have reproduced this problem, it caused by aioredis and ms-python, unitest together.
reproduce steps:

install aioredis 1.3.1 (2.0.1 also has same problem)
set breakpoint on line 16 of cache.py
run unittest test case.
when program paused on line 16: await redis.set("test", int(time.time()), let program continue

Now you'll get above exception.
If you run unittest without breakpoints, no exceptions.
Hope this helps.
redis_test.zip
.

we have created a issue for tracking this: https://github.com/zillionare/omega/issues/46
the branch can reproduce this pr is:  https://github.com/zillionare/omega/tree/zillionare/issue46
To reproduce:

git clone the code
run pip install poetry, poetry install -E test
debug unittest tests/jobs/test_syncjobs.py::TestSyncJobs::test_load_sync_params


[CocoaPods] Add SQLite module map for each architecture

Piggy-backing off of https://github.com/stephencelis/SQLite.swift/pull/380
☝ What does this PR do?
This fixes the build problem where people were unable to build depending on what version of Xcode they were using. I know, it sounds bizarre...
✌ How does it do it?
I split up the module maps up by architecture, and imported them in the private build settings (basically the same technique I mentioned in this comment)
📖  More Information!
While I was investigating, I downloaded both versions of Xcode (dmg and AppStore). The dmg version was fine. The AppStore version would build for devices, but not for the simulator. But! If I rearranged the order of the x86, arm, arm64 modules, I could get it to succeed/fail in building in the other way around!
So I thought, I don't know which version of Xcode is correct, but one of them is certainly buggy. But it would be better if it would build for anyone regardless of what version of Xcode they were using.
Yeah, it's a little disappointing to have more files like this to take care of, but I couldn't find another way to make a kind of 'conditional import'.
Plus! I've gotten it to successfully build on CircleCI, so that make me feel a little bit better! :smile:

This was the first time my build went through on the build server (trying out BuddyBuild). The previous solution only worked locally.

Round and round we go :)
This is similar to one of the first solutions I had to this problem. The way SwiftPM works makes it a more ideal candidate, too, so :+1:.

Thanks for investigating! This Xcode update was rockier than I think we all hoped :smile:

Thanks :smile:
Yeah I hadn't really followed all the changes as they started happening. I got sick the day after this all started, and just got better in time to pick up the rear end!

This Xcode update was rockier than I think we all hoped

Yeah, no kidding... In more ways than just this library too!
:+1:

Hey :)
Looks good to me, but i am still wondered why this works without the umbrella header.
I try to apply the solution to my own project, but my project requires the umbrella header in the module map.

@fuxx I believe it's because this module map exists in addition to the generated one, with a different module name (CSQLite in this case).


Certificate indicators based on having the actual certificate is not optimal.  We should be able to just imput the certificate parameters.

[Enter feedback here]

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

ID: 43e56d5e-bd24-b23a-ab4e-2a1253e09d14
Version Independent ID: 93ff9b4e-f401-3d75-965e-106b7ce646c3
Content: Create indicators based on certificates - Windows security
Content Source: windows/security/threat-protection/microsoft-defender-atp/indicator-certificates.md
Product: w10
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Hello @waydaws - Thank you for your feedback. Can you please explain in a little more detail what parameters are required to be added in the document so that I can look into this?
Thanks
Imran.

@jonimran.  Yes, for example the Signer Distinguished Name, as they're sometimes specified in IOCs (and sometimes better than hashes for controlling what's allowed or not).

Thanks for your reply @waydaws - I am sorry I didn't get your point. Can you please let me know which part of the document needs to change/updated with what information?

Ah, I see.  It's not the document.  I was trying to comment on product itself.

Thank you for providing feedback.
Please consider opening a product feedback ticket for any of your suggestions or feature requests to help Microsoft improve your experience, you could add your feedback via the Microsoft Windows 10 Feedback Hub. You might find others have made a similar request that you can add to, or you can open a new one.
Thank you for your contribution to make the docs better! Much appreciated!


Fix leak with multi-output primitives

The test case shows how this was happening. I think the fix is safe since the only case where we could have a race is in the asynchronous eval in which case:

No eval is allowed during transforms so the array will be detached during eval
Hence, we don't go into the multi-output destructor since it will be handled by the detach.

Let's merge this and I will do a follow on with the retain graph fix.


cri-o: Make $BUILDTAGS overwriteable

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@zowoq @vdemeester

Closing in favor of https://github.com/NixOS/nixpkgs/pull/85869


Add support for Composer

For future releases it was great you could add this composer.json and add the package to packagist.org :)

I'm genuinely curious why this would be desirable. Composer is the "Dependency Manager for PHP", not Javascript. That's what NPM, Jam, Bower, and others are for.
Would you suggest adding a slick.gemspec file too, so it can be added to RubyGems to be installable via Bundler?

Composer is a dependency manager for PHP projects. That does not mean that the package have to be php, as you will use non-php packages in php projects too.
Besides that, npm, jam and bower are package managers that run on node. Why shouldn't a PHP based package manager not be allowed to handle Javascript-Packages?
I personally do not use Ruby for webdevelopment, but I do not see a reason, why that should not be a valid request.
If the maintainer of this project does not want that, that's fine. But then we would need to maintain a fork to do it anyways.

Why not use the composer-asset-plugin for this. This has the possibility to add sources from npm/bower in your composer.json.

Because it Is slow and it does only work when the plugin is installed globally. These are two crucial problems.

I'm kind of on @deefour 's level here...
I've not seen a composer.json file in pretty much any frontend libraries before... https://github.com/jquery/jquery jQuery doesn't have it, so dependencies wouldn't be met, anyway?
I'll close this, but I'm pinging @kenwheeler so he can have one final goosey and bring it back from the grave if he wants composer.json support :smile:
Thanks for your effort, @derhasi . :)


Update v9 theme colors and revert button background colors

Description
This reverts the button background colors change in 1.14 (removing new variable but given issues + short time frame thing its okay) and updates colors for v9 theme.
Issues Resolved
N/A
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

[X] Update CHANGELOG.md
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

note: failing test in osd due to other changes


More examples, please!

Just stumbled on this today and I can see the benefits of using a framework like this. Would really love to see more examples of how it might apply to real-world situations. Things like:

Navigation
Personalization
Dynamic UI elements (favorites, ratings, etc)
Other UI tricks like animations, effects, transitions, etc

Thanks for this, will be watching!

Ok, I’ll maybe provide a demo website, to see what DisplayJS is capable of 😊

But I can’t say when it will be available because I have a lot of work 😊


fix: pod secondary range name should not be same as service secondary range name

attempt to fix gruntwork-io/terraform-google-gke/issues/118
use services_secondary_range_name var instead of defaulting to cluster_secondary_range_name

This fix is in tandem with https://github.com/gruntwork-io/terraform-google-network/pull/62

Closing in favor of https://github.com/gruntwork-io/terraform-google-gke/pull/121


pod counts and details panel lists do not respect namespace

In Weave Cloud (Dev) we have a memcached service in the default namespace and one in the frankenstein namespace. But when the view has either namespace selected, the "# pods" shown for the service is the aggregate of the two, and when bringing up the details panel, the pods for both services are listed. When selecting 'All Namespaces', two memcached nodes are shown, both containing the aggregrate set of pods.

Looks like a pod's parents are set without regard to the namespace. So, for example, each of the memcached pods in our Weave Cloud Dev cluster has two replica-sets and two deployments as a parent - one in the default namespace and one in the frankenstein namespace.
I suspect the problem is in kubernetes.Reporter.podTopology.
@2opremio @paulbellamy am I on the right track? Any clues you can offer?

Yep, you seem to be the right track, I will have a look at the code later (
probably we are not using the ids correctly or the ids don't contain the
namespace)
On Aug 24, 2016 20:41, "Matthias Radestock"<EMAIL_ADDRESS>wrote:

Looks like a pod's parents are set without regard to the namespace. So,
for example, each of the memcached pods in our Weave Cloud Dev cluster has
two replica-sets and two deployments as a parent - one in the default
namespace and one in the frankenstein namespace.
I suspect the problem is in kubernetes.Reporter.podTopology
https://github.com/weaveworks/scope/blob/v0.17.1/probe/kubernetes/reporter.go#L349
.
@2opremio https://github.com/2opremio @paulbellamy
https://github.com/paulbellamy am I on the right track? Any clues you
can offer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/scope/issues/1824#issuecomment-242184266,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACQOJJaU40FZgojRQOlrN5jJm3WyylBFks5qjJ5ogaJpZM4Jq3E7
.


Add camera custom zoom step

This PR introduces the zoom_step variable. That variable controls how fast the camera zoom changes.
Fixes #18

Cheers mate!


Update design system to version 31.0.0

This is an auto-generated PR.
Design system release: https://github.com/ONSdigital/design-system/releases/tag/31.0.0

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/496

Superseded by https://github.com/ONSdigital/eq-questionnaire-runner/pull/496


[orgmode]

Hi
I am trying to use orgmode compiler in nikola. I have both emacs 22.3 and orgmode 9.0.9 setup on windows 10. I have also tried changing the init.el file with the following
(add-to-list 'load-path "C:\Org\org-9.0.9\lisp")
(add-to-list 'load-path "C:\Org\org-9.0.9\contrib\lisp" t)
conf.py is already configured as well.
Still I cannot use 'nikola build'. I get the following error
[2017-08-14T10:49:25Z] ERROR: Nikola: In order to use the orgmode compiler, you must install the "emacs" and "org-mode" software.
[2017-08-14T10:49:25Z] ERROR: Nikola: Exiting due to missing dependencies.
Any help would be appreciated
Sumit

Is Emacs on your executable path?
Nikola uses it's own custom init.el when starting Emacs.  You will need to edit the init.el file in your <site>/plugins/orgmode/ directory, and make the changes required to let Emacs find your org-mode installation.

Hi @punchagan
Yes emacs is on my executable path. I am able to run it from cmd line.
I have added the following in the init.el file as well
(add-to-list 'load-path "C:\Org\org-9.0.9\lisp")
(add-to-list 'load-path "C:\Org\org-9.0.9\contrib\lisp" t)
(require 'org)
Thanks for your response.
Sumit

Please edit the init.el file supplied by the orgmode Nikola plugin present in your site's plugin directory.  The Emacs used by this plugin doesn't care about your init.el in ~/.emacs.d.

Hi @punchagan I have made the changes in <site>/plugins/orgmode/init.el as you mentioned before.

any development so far?
did you solve the problem @bamsumit?

Hi @punchagan , I couldn't find a solution. So I moved away from using org mode on Nikola altogether.

I'm also facing the same issue, any help is appreciated.


verifyMainThread() checks in RxJava 2 variants don't go to onError

Note sure if this is by design or not, but the exceptions thrown by verifyMainThread() fail hard rather than going to onError() (since it doesn't know the disposed state during the calling subscribe and will just bubble it straight to RxJavaPlugins#onError() or throw. Since we have the observer there, should we send the exception to its onError() instead?
Specifically, I think this is actually a significant behavior change from the implementation in RxJava 1 or using create(), which would send this to onError().
Result is if you want to gracefully handle that case, you end up having to try/catch the actual subscribe() call itself

I wouldn't like to change this behaviour. Calling such methods on wrong thread is developers' mistake and it should blow up in theirs face. I cannot imagine how you could handle such error in onError and how could you be prepared for it.

True ^, the only thing to keep in mind is that with RxJava 2 developers kinda have to add error Handler for RxJava plugins since all errors happened after unsubsuption go there (such as network request timeout) and there is a chance that exception from RxBinding will be silently swallowed by poorly written error hanlder and lead to hours spent in debugging.

I agree it should blow up, but I think it should also go to onError(). Idiomatic RxJava dictates as much, even on invalid inputs like null values. This just feels a big gotcha now.

there is a chance that exception from RxBinding will be silently swallowed by poorly written error hanlder and lead to hours spent in debugging.

That argument doesn't really make sense as you could really claim it as a case against using any error handling in RxJava. The whole point is you have an elegant means of handling them.

The whole point is you have an elegant means of handling them

Which does not make sense for NotOnMainThreadException :)
If it'll be delivered to observer, plugin swallowing will not be an issue.
On Wed, Feb 1, 2017, 14:17 Zac Sweers<EMAIL_ADDRESS>wrote:

there is a chance that exception from RxBinding will be silently swallowed
by poorly written error hanlder and lead to hours spent in debugging.
That argument doesn't really make sense as you could really claim it as a
case against using any error handling in RxJava. The whole point is you
have an elegant means of handling them.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/JakeWharton/RxBinding/issues/353#issuecomment-276633059,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7B3G-VJnKU5dDLQGvb1UhR9dx8jGsgks5rYGnjgaJpZM4Ly3Ya
.

I disagree. I'm not sure what principle requires that thread exceptions must be hard crashes.
I am arguing it should be delivered to the observer. I'm not really sure what plugin swallowing to do with this. If the observer has no onError handling, it bubbles back to the plugin system anyway before finally throwing.

It should go to onError.

Cool, I'll work on a PR today


Crash on root native check

I set rootcloak to hide root things from rootbeer sample app, and then the app crashes at root native check.
Notice: rw paths successfully detected.
OTP Smartbank app (Hungary) uses this root checking library, and it also crashes. Also, if i dont use rootcloak for smartbank, then it will not launch...
I bet the Hungarian OTP team not going to update the library in their app, so can you give me a quick fix how can i bypass the detection in an old version? You know, old versions not supported..
Me and many other users of the app thinks that OTP wants to decide if we want to use root, and it's a bad behavior.
Anyway, here is the log (OTP Smartbank crash when checking for root if rootcloak tries to hide it):
And a video (about the crashing sample app)

Did this crash occur on the latest release build, the latest master branch, or on another build?

Sorry, i don't know :/ I'm not a developer of the app, i only wanted to use it in my rooted phone. If you can provide a method to see it, i can provide it to you. Maybe if i decompile the app?

As @MPeti1 suspects this is likely caused by an outdated version of the library included in the app in question. The library no longer crashes if the native root checking library cannot be loaded, but I think we still need to update the sample app on the Play store. The Hungarian OTP team should update the library used so they can provide better UX for when root is detected or suspected rather than just crashing.
Also as we are the ones attempting to detect root we aren't really the best people to ask how to bypass our own work ;)

This was an issue that I fixed in the latest master. Once the next release of rootbeer is out, this will be fixed.


Remove the draft training videos

I created some 20 draft instructional videos on FreeCEN2 usage one year ago. These very recorded zoom sessions and the videos are stored on my personal YouTube account.
It is time that these were removed from my account and replaced on FreeCEN2 by access to the professional instructional videos

I was thinking this yesterday, too! The Coords had some suggested improvements, but nothing major. If we're happy to not let the perfect be the enemy of the good, I'll upload them into YouTube when I don't need the bandwidth for meetings etc.

Work in progress, links here: https://docs.google.com/document/d/1xAbAFG4usBxV5zYxDF2EnsFeKDiu8A7EFJQ74rrHcCA/edit?usp=sharing
(document is only accessible by those logged into a FreeUKGen account

@Captainkirkdawson to deploy.

Thanks, Kirk. I have downloaded that one from your channel, and uploaded it to ours (as we don't have an equivalent). I have embedded all videos in this page on Refinery: https://test3.freecen.org.uk/cms/draft-instructional-videos. Next steps are to tidy it up and make it live.

I had a quick look at the first video and have the following comments:

the views of the site pages are distorted
it is not possible to read most of the red comments, even in full screen
If you select "View on Youtube", the opening view (with the start button) is clipped at the sides
the closed captions are pretty accurate but they render "FreeCEN" as "free send" and "freecen.org.uk" as "freesend.org.uk"

@DeniseColbert to make page live.

@DeniseColbert The link has been made and it is active on production.
I noticed 2 things. Firstly one cannot view the pages in full screen which makes them very hard to follow.
Secondly there is no video on the login process and how to recover the password


Variant image assignment issue

Trying to save a variant while only changing the image_id is giving 400 bad request error. The image and variant are of the same product. As you can see in the screenshot below the product id is the same for both image and variant. Can't assign images to variants. This issue persists for 4 days. Is coming up randomly for some products. Any idea of the cause of issue or how to work around it or any help or pointers would be appreciated. No other value is changed, nothing else is touched. Other API calls are working properly.
> product = ShopifyAPI::Product.find(4374031728707) => gives correct product

> image = product.images.find{|i| i.id ==<PHONE_NUMBER>8083}
 => #<ShopifyAPI::Image:0x000055ac8bdaf4e8 @attributes={"id"=>13579689558083, "position"=>18, "created_at"=>"2019-12-08T05:57:39-05:00", "updated_at"=>"2019-12-08T05:57:39-05:00", "alt"=>nil, "width"=>1500, "height"=>1500, "src"=>"https://cdn.shopify.com/s/files/1/0064/3422/6243/products/81YMzVfoy5L._SL1500_4734ed82-055a-4316-97e5-1b1a2ca50b38.jpg?v=1575802659", "variant_ids"=>[], "admin_graphql_api_id"=>"gid://shopify/ProductImage/13579689558083"}, @prefix_options={:product_id=>4374031728707}, @persisted=true>

> variant = product.variants.find {|v| v.id ==<PHONE_NUMBER>5411}
 => #<ShopifyAPI::Variant:0x000055ac8bd1f078 @attributes={"id"=>31267120185411, "title"=>"Large-Grey", "price"=>"14.770", "sku"=>"B07P9RZVXF", "position"=>1, "inventory_policy"=>"deny", "compare_at_price"=>nil, "fulfillment_service"=>"manual", "inventory_management"=>"shopify", "option1"=>"Large-Grey", "option2"=>nil, "option3"=>nil, "created_at"=>"2019-12-08T05:57:40-05:00", "updated_at"=>"2019-12-08T05:57:40-05:00", "taxable"=>true, "barcode"=>nil, "grams"=>122, "image_id"=>13579689558083, "weight"=>0.2688, "weight_unit"=>"lb", "inventory_item_id"=>32828621029443, "inventory_quantity"=>3, "old_inventory_quantity"=>3, "requires_shipping"=>true, "admin_graphql_api_id"=>"gid://shopify/ProductVariant/31267120185411"}, @prefix_options={:product_id=>4374031728707}, @persisted=true, @remote_errors=nil, @validation_context=nil, @errors=#<ActiveResource::Errors:0x000055ac8c2eeb98 @base=#<ShopifyAPI::Variant:0x000055ac8bd1f078 ...>, @messages={}, @details={}>>

> variant.image_id
 => nil

> variant.image_id = image.id
 =><PHONE_NUMBER>8083

> variant.image_id
 =><PHONE_NUMBER>8083

> variant.save
Traceback (most recent call last):
        1: from (irb):441
ActiveResource::BadRequest (Failed.  Response code = 400.  Response message = Bad Request.)

> variant.errors.messages
 => {}

We will have an update to release today possibly that will add more information to 400 errors so hopefully, that will enlighten us what is happening here. Does this only happen intermittently? Does it succeed with the same information on subsequent requests?

No, its pretty much constant, for example I tried a number of times for this same variant and Image combo a number of times during the last few days. Regardless of how many times I tried it it fails. Even my code redoes the failed requests a up to 3 times, they also all fail.
But I did find a work around
#given the same variant and image
> new_variant = ShopifyAPI::Variant.new(id: variant.id, image_id: image.id)
> new_variant.save
 => true

And that works. Which is honestly strange. The only thing I can think of is there are additional validations on update that are failing on some of the other attributes, validations which only trigger on update and not create.


Bring feature to change network from guest to host on utm’s ios version to deal with the issue “why did my pc restart? There’s a problem that’s preventing us from getting your pc ready to use ……..

Describe the issue
A clear and concise description of what the issue is. BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Configuration (required)

UTM Version: 4.4.1
OS Version: ipados 16.6
Device Model: ipad 9 (wifi)
Is it jailbroken (name jailbreak used)? No
How did you install UTM? Sidestore

I have seen in closed issues that this problem can be solved in mac 🖥, but what about the iOS version of utm , i facing this issues when i am installing windows 10. If there is any way to fix this problem , please tell


libjwt: 1.15.2 -> 1.15.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/benmcollins/libjwt/releases.
meta.description for libjwt is: JWT C Library
meta.homepage for libjwt is: https://github.com/benmcollins/libjwt
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.3 with grep in /nix/store/z3fb7f3xpz7d9cgvyj7zq486hv05jwm6-libjwt-1.15.3
found 1.15.3 in filename of file in /nix/store/z3fb7f3xpz7d9cgvyj7zq486hv05jwm6-libjwt-1.15.3

Rebuild report (if merged into master) (click to expand)

7 total rebuild path(s)

7 package rebuild(s)

First fifty rebuilds by attrpath
haskellPackages.libjwt-typed
libjwt
python310Packages.pyslurm
python311Packages.pyslurm
slurm
slurm-spank-stunnel
slurm-spank-x11

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z3fb7f3xpz7d9cgvyj7zq486hv05jwm6-libjwt-1.15.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libjwt https://github.com/r-ryantm/nixpkgs/archive/2f98bc931737ccdecf57fe16bcd4aa22a3bd20d8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z3fb7f3xpz7d9cgvyj7zq486hv05jwm6-libjwt-1.15.3
ls -la /nix/store/z3fb7f3xpz7d9cgvyj7zq486hv05jwm6-libjwt-1.15.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages failed to build:

python310Packages.pyslurm
python311Packages.pyslurm

4 packages built:

libjwt
slurm
slurm-spank-stunnel
slurm-spank-x11

Maintainer pings
cc @pnotequalnp for testing.

Result of nixpkgs-review pr 230435 run on aarch64-darwin 1

3 packages built:

haskellPackages.libjwt-typed
haskellPackages.libjwt-typed.doc
libjwt


Added FlexDotnetCMS to README.md

CMS/FlexDotnetCMS - https://github.com/MacdonaldRobinson/FlexDotnetCMS
A powerful, flexible, decoupled and easy to use and Fully Featured ASP .NET CMS, it can also be used as a Headless CMS

Sorry, but the community hasn't rallied behind this project to get it included. Thanks for your contribution.


Make component containers able to launch

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
Current docker container images for each components released from autoware does not contain launch files to run the packages inside each container. We can add tier4_*_launch packages under autoware.universe to respective images to enable launching by components.
Purpose
Let users enable to run Autoware using component containers.
Possible approaches
Modify the docker file to copy each component launch files into respective docker images.
We could also consider moving the launch packages from the launch folder into respective folder (e.g., moving tier4_control_launch to control folder)  as we do the refactoring of the launch system in this discussion so that we have simpler docker file.
Definition of done

[ ] modify the docker file to include launch packages into each containers

[x] create a draft PR
[ ] test if generated containers can be launched standalone

[ ] break up the launch folder to move the launch packages into respective component folder
[ ] revert the changes in the docker file after refactoring

colcon graph --dot --legend | dot -Tsvg -o graph.svg

with only autoware.universe packages:


TLV capture and parsing for proxy protocol v2

Adds rawTLVs to Header struct
API Change

non-io.EOF errors encountered when reading from payload reader are returned
from parseVersion2 and Read
Padding is saved in rawTLV

TLV splitting is implemented by Header.TLVs(), TLV length validation without
this explicit call
Includes helpers for parsing AWS VPCEs and SSL information
Parsing of other types possible by consumers via the PP2Type constants using
the TLV and PP2SSL exported types

Given the overlap with #2 I'll see if I can give this code a try later this week and see if it also accomplishes what I was trying to do with #2. Not that that should be the goal in itself, but I'd like to see if - if we start changing the API - can do so with only a single change rather than having to change it multiple times.

I'd like to see if - if we start changing the API - can do so with only a single change rather than having to change it multiple times.

This is a backwards compatible change, if there are non-bwc API changes that are required for #2 then I'd suggest rolling a new major version while letting this go into a minor version release.

Closed in favor of https://github.com/pires/go-proxyproto/pull/10

This is a backwards compatible change

Good point. Though you are extending the public interface a bit, so I'd like to see if it also suffices for my original requirements. Just to see if we can prevent a future BC break. (or at least know so in advance)

Maybe it's time to do releases and stop getting this from master. dep/go modules have come a long way.


Added elapsed time to server loaded message

For curious people, who want to know exactly how long it took to get the server up and running.

Nice, thanks!

I merged a bit quickly - just realised that this is reporting seconds as "ms". It's a nice addition though, we can fix that "ms" up later on.

Updated in 9bb553a


'Add Page' does not add new .md file

Fresh docker install from linuxserver/raneto using out-of-box settings

/config set with UID/GID matching PUID/PGID of container for user 'abc'
Able to add new category (directory is created with drwxr-xr-x)
UNABLE to add page (provide page name, click 'Save', dialog disappears and nothing gets created; only log shows POST /rn-add-page 200 4.815 ms - 105)

I am also seeing this

Some things I noticed:

Please use the new-ish official image located here: https://hub.docker.com/r/raneto/raneto
Are you linking a volume for [RANETO DIR]/content?
What OS is the container host?
Are you using Docker CLI, Podman, Docker Desktop (Window/macOS GUI)?

#322 potentially related


🌐 Add Ukrainian translation for docs/uk/docs/tutorial/body-fields.md

Context:
Ukrainian translation for docs/uk/docs/tutorial/body-fields.md
Changes:
Created Ukrainian version of docs/uk/docs/tutorial/body-fields.md

📝 Docs preview for commit 47329aa7644cb569c71f3644d140d67d8bd488a4 at: https://642845c4.fastapitiangolo.pages.dev

📝 Docs preview for commit fe18a37b789c1d8ba244a9d483a61b94cb6d8d0a at: https://aaa94259.fastapitiangolo.pages.dev

Thanks for your help! 😄 @ArtemKhymenko
And for the reviews @rostik1410 and @mezgoodle 🚀


Add SMS Role SSL certificate info

We need to add the info for HTTPe selfsigned certificate

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

ID: 9c095180-90a2-79c6-a7fb-6504cafbcfb6
Version Independent ID: fb9c2930-b213-3eef-c7bb-c8f11ec97aca
Content: CMG Certificates - Configuration Manager
Content Source: sccm/core/clients/manage/cmg/certificates-for-cloud-management-gateway.md
Product: configuration-manager
Technology: configmgr-client
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Hi @MSBeatriz, can you please expand a bit more on this? For example:

Which certificate are you referring to?
What additional info is needed?

Hi Aaron,
I was going to draft it but I lost my access to Github.
(Waiting on support as I have not recovery keys on my current pc (renewed) and for some reason on authenticatior tool Github was removed. They will remove my account and I will re-setup it… At least I had nothing there that I have not saved locally)
About SMS Role SSL certificate:
What we need is to clarify that when we setup HTTPe, there´s a selfsigned certificate added into IIS web service from MP secure communication.
This causes many issues on customer environments, where the cert is not configured properly, and customers are un-aware of this.
This could be added on  section: Enable Management point certificate for HTTPs, with a note regarding HTTPe certificate.
Or adding new section for HTTPe Management Point ¿?
There´s another certificate to mention related to CMG CP we might need to clarify as well.
We need client auth cert locally on server cert store, so we might need add another section? Or maybe add this info on other place of docs?
Let me know if those certificate info should be here or not. CMG functionality depends on them both.
Best regards,
Beatriz Moran Serrano
SEE EMEA Configuration Manager - Customer Services and Support
TLF: +34 (91) 3919641
Email: bmoran<EMAIL_ADDRESS>Did I help you today?  Please provide feedback  or Send Kudos: http://kudos/
Manager:  Stefan Nachreiner<EMAIL_ADDRESS>+49 (89) 31762417
From: Aaron Czechowski<EMAIL_ADDRESS>Sent: sábado, 16 de noviembre de 2019 3:01
To: MicrosoftDocs/SCCMdocs<EMAIL_ADDRESS>Cc: Beatriz Moran Serrano<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/SCCMdocs] Add SMS Role SSL certificate info (#2011)
Hi @MSBeatrizhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMSBeatriz&data=02|01|bmoran%40microsoft.com|f263ceb0b6d34452b96008d76a38e39c|72f988bf86f141af91ab2d7cd011db47|1|0|637094664886271393&sdata=h8kPVUliiYQTDQsmBEvkgbCGcjDuKVUk%2Br0L75V8Ty0%3D&reserved=0, can you please expand a bit more on this? For example:

Which certificate are you referring to?
What additional info is needed?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FSCCMdocs%2Fissues%2F2011%3Femail_source%3Dnotifications%26email_token%3DAKIBXA4GMBSQWJLXEHHEI3DQT5H7LA5CNFSM4JNX3EO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEHGVJY%23issuecomment-554592935&data=02|01|bmoran%40microsoft.com|f263ceb0b6d34452b96008d76a38e39c|72f988bf86f141af91ab2d7cd011db47|1|0|637094664886271393&sdata=vFmXx6vO01x0F%2BzhmgFBNjvtgPFcnUaglNPggVcFuqc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKIBXAYFH72JO2JHBOOXBX3QT5H7LANCNFSM4JNX3EOQ&data=02|01|bmoran%40microsoft.com|f263ceb0b6d34452b96008d76a38e39c|72f988bf86f141af91ab2d7cd011db47|1|0|637094664886281383&sdata=Z7%2FPx2JVShCc1ZaxR8L9uXsXxeWmqp8gJar3jaCa8fg%3D&reserved=0.


Add StyleRoot component to replace isRoot config

isRoot had the odd behavior that it wrapped its contents in a div. Instead, make the “style root” a separate, explicit component.
Definitely open to feedback about the name!

This also has another difference from isRoot: you can't have keyframes or media queries in the same component that renders StyleRoot, e.g.:
render() {
  return (

  );
}

This is unlikely to be a problem in real apps, but makes the tests slightly annoying.

Another alternative is that any Radium component will create the StyleKeeper if it doesn't receive one in context, and you must render the


Remove unneeded "recursive" flag when removing a file

https://github.com/plus3it/SystemPrep/blob/master/Utils/systemprep-joindomain.sh#L208

Fixed by #72


Who is the winner?)

Guys, just wondering who won? Want to see the code)

I'm apologize for late notice. 😢
I commented result of competition on each pull-request's comment.