HTEX broken on Mac OS X

I have trouble getting HTEX to work. Maybe I'm doing something fundamentally wrong but the following MWE gets stuck for me for parsl 0.7.2:
import parsl
import os
from parsl.app.app import python_app
from parsl.configs.htex_local import config as htex_config
from parsl.configs.local_ipp import config as ipp_config

@python_app
def dummy_app(inputs=[], outputs=[]):
    return "Dummy app finished!"

if __name__ == "__main__":
    parsl.set_stream_logger()
    print(f"Using parsl version {parsl.__version__}")

    # This works
    # parsl.load(ipp_config)
    # This doesn't work
    parsl.load(htex_config)

    results = dummy_app()
    print(results.result())

The logger output is
2019-04-08 16:20:04 parsl.executors.high_throughput.executor:483 [DEBUG]  Launched block 0:32494
2019-04-08 16:20:04 parsl.dataflow.strategy:125 [DEBUG]  Scaling strategy: simple
2019-04-08 16:20:04 parsl.dataflow.dflow:670 [INFO]  Task 0 submitted for App dummy_app, waiting on tasks []
2019-04-08 16:20:04 parsl.dataflow.dflow:680 [DEBUG]  Task 0 set to pending state with AppFuture: <AppFuture at 0x103b29d30 state=pending>
2019-04-08 16:20:04 parsl.executors.high_throughput.executor:452 [DEBUG]  Pushing function <function dummy_app at 0x103b2d620> to queue with args ()
2019-04-08 16:20:04 parsl.dataflow.dflow:458 [INFO]  Task 0 launched on executor htex_local
2019-04-08 16:20:05 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 16:20:05 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('617cd0ccc1bc', 0, True)]
2019-04-08 16:20:05 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 16:20:10 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 16:20:10 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('617cd0ccc1bc', 0, True)]
2019-04-08 16:20:10 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines

with the last 3 messages repeating without finishing the program.
If I instead use the HTEX config from the docs (https://parsl.readthedocs.io/en/latest/parsl-introduction.html#Local-execution-with-pilot-jobs):
htex_config = Config(
    executors=[
        HighThroughputExecutor(
            label="htex_Local",
            worker_debug=True,
            cores_per_worker=1,
            provider=LocalProvider(
                channel=LocalChannel(),
                init_blocks=1,
                max_blocks=1,
            ),
        )
    ],
    strategy=None,
)

the program just hangs after
2019-04-08 16:18:36 parsl.executors.high_throughput.executor:483 [DEBUG]  Launched block 0:32436
2019-04-08 16:18:36 parsl.dataflow.strategy:125 [DEBUG]  Scaling strategy: None
2019-04-08 16:18:36 parsl.dataflow.dflow:670 [INFO]  Task 0 submitted for App dummy_app, waiting on tasks []
2019-04-08 16:18:36 parsl.dataflow.dflow:680 [DEBUG]  Task 0 set to pending state with AppFuture: <AppFuture at 0x107abdef0 state=pending>
2019-04-08 16:18:36 parsl.executors.high_throughput.executor:452 [DEBUG]  Pushing function <function dummy_app at 0x107ac2620> to queue with args ()
2019-04-08 16:18:36 parsl.dataflow.dflow:458 [INFO]  Task 0 launched on executor htex_Local

Using IPP (parsl.configs.local_ipp.config) or threads (parsl.configs.local_threads.config) works, however.

Hi @tilmantroester, thanks for using Parsl.
I just tried your script with htex_local and it worked on my machine. I was wondering what machine you ran that on (e.g., login node of supercomputer or laptop). Could you please paste us the whole logs in runinfo/XXX directory.
We can help you debug that on our slack channel too (link: http://parsl-project.org/support.html)

I'm running this on my laptop (macOS 10.14.4, python 3.7).
All log files
parsl.log (I killed the process at the end):
Config(
    app_cache=True,
    checkpoint_files=None,
    checkpoint_mode=None,
    checkpoint_period=None,
    data_management_max_threads=10,
    executors=[HighThroughputExecutor(
        address='<IP_ADDRESS>',
        cores_per_worker=1,
        heartbeat_period=30,
        heartbeat_threshold=120,
        interchange_port_range=(55000, 56000),
        label='htex_local',
        launch_cmd='process_worker_pool.py {debug} {max_workers} -c {cores_per_worker} --poll {poll_period} --task_url={task_url} --result_url={result_url} --logdir={logdir} --hb_period={heartbeat_period} --hb_threshold={heartbeat_threshold} ',
        managed=True,
        max_workers=inf,
        poll_period=10,
        provider=LocalProvider(
            channel=LocalChannel(
                envs={},
                script_dir=None,
                userhome='/Users/yooken/Research/KiDS/pipeline_testing'
            ),
            cmd_timeout=30,
            init_blocks=1,
            launcher=SingleNodeLauncher(),
            max_blocks=1,
            min_blocks=0,
            move_files=None,
            nodes_per_block=1,
            parallelism=1,
            walltime='00:15:00',
            worker_init=''
        ),
        storage_access=[],
        suppress_failure=False,
        worker_debug=False,
        worker_port_range=(54000, 55000),
        worker_ports=None,
        working_dir=None
    )],
    lazy_errors=True,
    monitoring=None,
    retries=0,
    run_dir='runinfo',
    strategy='simple',
    usage_tracking=False
)
2019-04-08 18:27:45.801 parsl.dataflow.dflow:79 [INFO]  Parsl version: 0.7.2
2019-04-08 18:27:45.801 parsl.dataflow.usage_tracking.usage:126 [DEBUG]  Tracking status: False
2019-04-08 18:27:45.801 parsl.dataflow.usage_tracking.usage:127 [DEBUG]  Testing mode   : False
2019-04-08 18:27:45.802 parsl.dataflow.dflow:101 [INFO]  Run id is: e31088b3-5dfb-490a-9944-d8c41acbdf4b
2019-04-08 18:27:45.918 parsl.dataflow.memoization:52 [INFO]  App caching initialized
2019-04-08 18:27:45.921 parsl.executors.high_throughput.executor:392 [DEBUG]  Starting queue management thread
2019-04-08 18:27:45.921 parsl.executors.high_throughput.executor:274 [DEBUG]  [MTHREAD] queue management worker starting
2019-04-08 18:27:45.922 parsl.executors.high_throughput.executor:396 [DEBUG]  Started queue management thread
2019-04-08 18:27:45.948 parsl.executors.high_throughput.executor:233 [DEBUG]  Created management thread: <Thread(Thread-1, started daemon<PHONE_NUMBER>91648)>
2019-04-08 18:27:45.948 parsl.executors.high_throughput.executor:207 [DEBUG]  Launch command: process_worker_pool.py   -c 1 --poll 10 --task_url=tcp://<IP_ADDRESS>:54685 --result_url=tcp://<IP_ADDRESS>:54393 --logdir=/Users/yooken/Research/KiDS/pipeline_testing/runinfo/005/htex_local --hb_period=30 --hb_threshold=120
2019-04-08 18:27:45.948 parsl.executors.high_throughput.executor:210 [DEBUG]  Starting HighThroughputExecutor with provider:
LocalProvider(
    channel=LocalChannel(
        envs={},
        script_dir='/Users/yooken/Research/KiDS/pipeline_testing/runinfo/005/submit_scripts',
        userhome='/Users/yooken/Research/KiDS/pipeline_testing'
    ),
    cmd_timeout=30,
    init_blocks=1,
    launcher=SingleNodeLauncher(),
    max_blocks=1,
    min_blocks=0,
    move_files=None,
    nodes_per_block=1,
    parallelism=1,
    walltime='00:15:00',
    worker_init=''
)
2019-04-08 18:27:45.962 parsl.executors.high_throughput.executor:483 [DEBUG]  Launched block 0:37003
2019-04-08 18:27:45.963 parsl.dataflow.strategy:125 [DEBUG]  Scaling strategy: simple
2019-04-08 18:27:45.963 parsl.dataflow.dflow:670 [INFO]  Task 0 submitted for App dummy_app, waiting on tasks []
2019-04-08 18:27:45.964 parsl.dataflow.dflow:680 [DEBUG]  Task 0 set to pending state with AppFuture: <AppFuture at 0x1065a4cf8 state=pending>
2019-04-08 18:27:45.964 parsl.executors.high_throughput.executor:452 [DEBUG]  Pushing function <function dummy_app at 0x1065a7620> to queue with args ()
2019-04-08 18:27:45.966 parsl.dataflow.dflow:458 [INFO]  Task 0 launched on executor htex_local
2019-04-08 18:27:45.966 parsl.dataflow.dflow:786 [INFO]  Waiting for all remaining tasks to complete
2019-04-08 18:27:45.966 parsl.dataflow.dflow:792 [DEBUG]  Waiting for task 0 to complete
2019-04-08 18:27:46.968 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:27:46.969 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:27:46.969 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:27:51.967 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:27:51.967 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:27:51.967 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:27:56.968 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:27:56.968 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:27:56.969 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:01.973 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:01.974 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:01.974 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:06.977 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:06.977 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:06.978 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:11.982 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:11.983 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:11.983 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:16.984 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:16.985 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:16.985 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:21.987 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:21.988 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:21.988 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:26.992 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:26.993 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:26.993 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:31.993 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:31.994 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:31.994 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:36.994 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:36.995 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:36.995 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:41.995 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:41.996 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:41.997 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:46.999 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:47.000 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:47.000 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:52.003 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:52.014 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:52.015 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:28:57.007 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:28:57.007 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:28:57.008 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:02.012 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:02.013 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:02.013 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:07.015 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:07.016 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:07.016 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:12.018 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:12.019 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:12.019 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:17.020 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:17.020 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:17.021 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:22.024 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:22.024 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:22.025 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:27.024 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:27.025 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:27.025 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:32.028 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:32.028 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:32.029 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:37.033 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:37.034 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:37.034 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:42.034 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:42.035 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: [('e844a4104139', 0, True)]
2019-04-08 18:29:42.035 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 1 connected engines
2019-04-08 18:29:47.036 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:47.036 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:29:47.037 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:29:52.036 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:52.046 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:29:52.046 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:29:57.036 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:29:57.037 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:29:57.037 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:02.038 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:02.039 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:02.039 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:07.041 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:07.042 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:07.042 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:12.045 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:12.054 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:12.054 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:17.046 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:17.047 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:17.048 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:22.047 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:22.047 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:22.048 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:27.047 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:27.048 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:27.048 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:32.047 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:32.048 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:32.048 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:37.048 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:37.049 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:37.049 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:42.054 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:42.055 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:42.055 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:47.055 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:47.056 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:47.056 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:52.055 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:52.065 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:52.065 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:30:57.057 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:30:57.058 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:30:57.058 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:02.057 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:02.058 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:02.058 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:07.062 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:07.063 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:07.063 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:12.063 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:12.064 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:12.065 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:17.067 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:17.068 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:17.068 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:22.067 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:22.067 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:22.068 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:27.072 parsl.executors.high_throughput.executor:420 [DEBUG]  Got outstanding count: 1
2019-04-08 18:31:27.073 parsl.executors.high_throughput.executor:426 [DEBUG]  Got managers: []
2019-04-08 18:31:27.073 parsl.dataflow.strategy:206 [DEBUG]  Executor htex_local has 1 active tasks, 1/0/0 running/submitted/pending blocks, and 0 connected engines
2019-04-08 18:31:29.960 parsl.dataflow.dflow:805 [INFO]  DFK cleanup initiated
2019-04-08 18:31:29.960 parsl.dataflow.dflow:716 [INFO]  Summary of tasks in DFK:
2019-04-08 18:31:29.960 parsl.dataflow.dflow:747 [INFO]  Tasks in state States.launched: 0
2019-04-08 18:31:29.960 parsl.dataflow.dflow:754 [INFO]  End of summary
2019-04-08 18:31:29.960 parsl.dataflow.dflow:829 [INFO]  Terminating flow_control and strategy threads
2019-04-08 18:31:29.960 parsl.providers.local.local:231 [DEBUG]  Terminating job/proc_id: 37003
2019-04-08 18:31:29.961 parsl.executors.high_throughput.executor:531 [WARNING]  Attempting HighThroughputExecutor shutdown
2019-04-08 18:31:29.961 parsl.executors.high_throughput.executor:535 [WARNING]  Finished HighThroughputExecutor shutdown attempt
2019-04-08 18:31:29.961 parsl.data_provider.data_manager:99 [DEBUG]  Done with executor shutdown
2019-04-08 18:31:29.961 parsl.dataflow.dflow:861 [INFO]  DFK cleanup complete

@tilmantroester Thanks for reporting this issue. We've unfortunately had very limited testing on Mac systems and I am not surprised that there would be some Mac specific issues.
Looking through the logs, it looks like most of the executor system seems to have come online correctly.
If you do get a chance to try something, could you please retry the test with worker_debug=True set in the executor config and share the logs here?
@annawoodard is a Mac user and she's going to take a crack at this issue soon.

Thanks for looking into this! Ultimately, I'd deploy it on a Linux machine but for development purposes it be nice to test things locally.
The logs with worker_debug=True are here.
Here's the MWE used to create those logs:
import parsl
import os
from parsl.app.app import python_app
# from parsl.configs.htex_local import config as htex_config
from parsl.configs.local_ipp import config as ipp_config
from parsl.configs.local_threads import config as threads_config

from parsl.providers import LocalProvider
from parsl.channels import LocalChannel
from parsl.config import Config
from parsl.executors import HighThroughputExecutor

htex_config = Config(
    executors=[
        HighThroughputExecutor(
            label="htex_Local",
            worker_debug=True,
            cores_per_worker=1,
            provider=LocalProvider(
                channel=LocalChannel(),
                init_blocks=1,
                max_blocks=1,
            ),
        )
    ],
)

@python_app
def dummy_app():
    return "Dummy app finished!"

if __name__ == "__main__":
    parsl.set_stream_logger()
    print(f"Using parsl version {parsl.__version__}")

    parsl.clear()
    # This works
    # parsl.load(ipp_config)
    # parsl.load(threads_config)

    # This doesn't work
    parsl.load(htex_config)

    print("Launching dummy app")
    results = dummy_app()
    print("Launched dummy app")
    parsl.wait_for_current_tasks()
    # print(results.result())

interchange.log contains a a lot of repeating
2019-04-10 09:58:10.306 interchange:233 [DEBUG]  [TASK_PULL_THREAD] 1 tasks in internal queue
2019-04-10 09:58:10.314 interchange:400 [DEBUG]  Managers count (total/interesting): 1/0
2019-04-10 09:58:10.314 interchange:430 [DEBUG]  [MAIN] either no interesting managers or no tasks, so skipping manager pass
2019-04-10 09:58:10.315 interchange:447 [DEBUG]  [MAIN] entering bad_managers section
2019-04-10 09:58:10.315 interchange:460 [DEBUG]  [MAIN] leaving bad_managers section
2019-04-10 09:58:10.316 interchange:461 [DEBUG]  [MAIN] ending one main loop iteration

It looks like this is because qsize is not implemented:
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Queue.qsize
Note that this may raise NotImplementedError on Unix platforms like Mac OS X where sem_getvalue() is not implemented.

Someone else already solved this problem, their approach looks reasonable to me: https://github.com/vterron/lemon/commit/9ca6b4b1212228dbd4f69b88aaf88b12952d7d6f

While this is being implemented, is there a workaround that I could use? Or should I just stick with IPP for now?

@tilmantroester I suspect that fixes to HTEX will take a bit of time, so I'd recommend using IPP for local and switching to HTEX when running on the remote system. Just to be clear, you'd have to be running completely on linux based systems for HTEX to work right now.

I'll confirm this is a problem that makes the last cell in the default tutorial hang on my mac as well


Added SetStrv to glib.settings

Implement SetStrv, but doesn't compile. Please help fix. The documentation of the function is here https://developer.gnome.org/gio/stable/GSettings.html#g-settings-set-strv. I have opened a question in StackOverflow (https://stackoverflow.com/questions/47907238/convert-glib-c-method-with-string-array-as-parameter-to-go), but nobody answered. I don't have enough knowledge of C to do this.

Looking at the code in gtk.go from line 6550 they have used this code to create a C string array.
I have have changed your code with the way it is done in gtk.go above.
Not tested as I do not program in cgo, and I do not use this function.
You could try and see if it helps.
// SetStrv is a wrapper around g_settings_set_strv().
func (v *Settings) SetStrv(name string, values []string) bool {
	cstr1 := (*C.gchar)(C.CString(name))
	defer C.free(unsafe.Pointer(cstr1))

	// cvalues := C.make_strings(C.int(len(values) + 1))
	cvalues := make([]*C.gchar, len(values))

	for i, accel := range values {
		cvalues[i] = (*C.gchar)(C.CString(accel))
		defer C.free(unsafe.Pointer(cvalues[i]))
	}
	cvalues = append(cvalues, nil)

	// C.set_string(cvalues, C.int(len(values)), nil)
	return gobool(C.g_settings_set_strv(v.native(), cstr1, &cvalues[0]))

Thanks @tommyshem! Now it compiles, and I have done some test, and it seems to work. I have commited my forked repo, and the travis build has been relaunched with successful results. The pull is request is now ready and working.

@okelet Glad it worked.


🐛 overrides overrides extends overrides 😂

Environment information
CLI:
  Version:                      1.7.2
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_DIR:                unset
  NO_COLOR:                     unset
  TERM:                         "xterm-256color"
  JS_RUNTIME_VERSION:           "v20.10.0"
  JS_RUNTIME_NAME:              "node"
  NODE_PACKAGE_MANAGER:         "pnpm/9.0.6"

Biome Configuration:
  Status:                       Loaded successfully
  Formatter disabled:           false
  Linter disabled:              false
  Organize imports disabled:    true
  VCS disabled:                 true

Workspace:
  Open Documents:               0

What happened?
// biome.json
{
  "extends": ["./some-config.json"],
  "overrides": [{...}]
}

/// some-config.json
{
  "overrides": [{...}, { "include": ["package.json"], "formatter": { "lineWidth": 20 } }]
}

The overrides in biome.json overrides overrides in some-config.json
specifically, I observe the package.json override does not work until I do:
// biome.json
{
  "extends": ["./some-config.json"],
  "overrides": [{...}, { "include": ["package.json"], "formatter": { "lineWidth": 20 } }]
}

Expected result
The overrides in biome.json concatenates overrides in some-config.json
Code of Conduct

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

Instead of replacing the inherited overrides, we could extend it by first copying it and the appending the new overrodes. This is technically a breaking change. This could be changed in Biome 2.0

I'm not really sure about this...
Using extends inside overrides was one of the reasons why eslint pushed for a flat config.
Our configuration is already complex, and should weigh more complexity very carefully and justify very well.
I am going to close this issue for now because I prefer to not push more complexity on the configuration as a bug fix. As mentioned by Vic, it's a possible breaking change.
I will move this issue into a discussion.


How to "not" an entire BitVec in place?

I tried bits ^= true but apparently this impl BitXorAssign does not exist.
I don't see any other traits that would work without allocating an entire new BitVec.

I figured it out. I did not realize the Not impl is already implemented by moving Self. So I was able to do:
*bits = !std::mem::take(bits);


Decision for mono- vs poly- repo structure

Draft post that we will discuss tomorrow

Based on our meeting today, everyone (including me) will add more to this decision post to explain the reasons for why we need a decision for this, more pros and cons, and draw backs for our particular situation. Based on the content and reasoning, I will make a decision about it in a month (~Oct. 14).

It's been a month since the discussion and, given on one has added anything else to this post, I've updated it with the final decision. This also fits well with the requirement that Seedcase components be individually installable/usable. After the workshop next week, I'll pull out the design, community, and learn sections of the website into their own repos.


When HTTP / 2 is enabled, a virtual user may have multiple connections to a domain and port at the same time.

When HTTP / 2 is enabled, a virtual user may have multiple connections to a domain and port at the same time.
Each time you use resources in a scenario, the virtual user establishes a new connection.
Even if the virtual user already has a connection, a new connection will be added, so multiple connections will be held for the same IP address and port.
When using HTTP / 2, I think it's correct that a virtual user has 0 or 1 connection to the same IP address and port.
I confirmed in the following environment.
Gatling 3.7.4
AdoptOpenJDK11
When capturing with WireShark, useOpenSsl = false in gatling.conf is temporarily set.

Could you please provide a Short, Self Contained, Correct (Compilable), Example (see http://sscce.org/)?

When using HTTP / 2, I think it's correct that a virtual user has 0 or 1 connection to the same IP address and port.

Not necessarily. In particular when the user-agent doesn't have any prior knowledge of the remote peer supporting HTTP/2. What happens if you configure prior knowledge, https://gatling.io/docs/gatling/reference/current/http/protocol/#enablehttp2

Sample.zip
This event seems to occur only when the IP address is set in baseUrl.
The behavior did not change with or without .http2PriorKnowledge.
In the case of the following definition,
1-request to 6-request were sent on the same connection.
Attachment TestS.scala (Simulation ID is issue.TestS)
  val httpProtocol = http
    .baseUrl("https://gatling.io")
    ...
    .enableHttp2

  val scn = scenario("GatlingDoc")
    .exec(
      http("1-request")...
        .resources(
          http("2-request")...,
          http("3-request")...
        )
    )
    .exec(
      http("4-request")...
        .resources(
          http("5-request"),
          http("6-request")
        )
    )

If you change gatling.io to an IP address, it will be sent over 3 connections.

1-request, 4-request ⇒Connection A
2-request, 3-request(1st resources) ⇒Connection B
5-request, 6-request(2nd resources) ⇒Connection C
Attachment TestM.scala (Simulation ID is issue.TestM)

After receiving the 1-request response,
2-request, 3-request, 5-request, 6-request are sent, but is it necessary to establish connections B and C?

Fixed. Thanks for reporting!


[Doc Improvement][Prerequisites and cloud resources]

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
98
5
link
:white_check_mark:

msteams-platform/toolkit/prerequisites.md
91
12
link
:white_check_mark:

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

Docs Build status updates of commit 5a229f3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/get-started/glossary.md
:warning:Warning
View
Details

msteams-platform/tabs/how-to/tab-requirements.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-single-sign-on.md
:warning:Warning
View
Details

msteams-platform/toolkit/prerequisites.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/toolkit/TeamsFx-collaboration.md
:warning:Warning
View
Details

msteams-platform/toolkit/teams-toolkit-fundamentals.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/get-started/glossary.md

Line 75, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.
Line 120, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.
Line 121, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.

msteams-platform/tabs/how-to/tab-requirements.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/toolkit/add-single-sign-on.md

Line 354, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/prerequisites.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites.md(10,1)'. First level headings must be unique within a docset.
Line 14, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.
Line 15, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/provision.md

Line 22, Column 29: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/TeamsFx-collaboration.md

Line 20, Column 51: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/teams-toolkit-fundamentals.md

Line 159, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
6
link
:white_check_mark:

msteams-platform/toolkit/prerequisites.md
91
12
link
:white_check_mark:

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

Docs Build status updates of commit 1ab7f71:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/get-started/glossary.md
:warning:Warning
View
Details

msteams-platform/tabs/how-to/tab-requirements.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-single-sign-on.md
:warning:Warning
View
Details

msteams-platform/toolkit/prerequisites.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/toolkit/TeamsFx-collaboration.md
:warning:Warning
View
Details

msteams-platform/toolkit/teams-toolkit-fundamentals.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/get-started/glossary.md

Line 75, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.
Line 120, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.
Line 121, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/accounts.md'.

msteams-platform/tabs/how-to/tab-requirements.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/toolkit/add-single-sign-on.md

Line 354, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/prerequisites.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites.md(10,1)'. First level headings must be unique within a docset.
Line 14, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.
Line 15, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/provision.md

Line 22, Column 29: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/TeamsFx-collaboration.md

Line 20, Column 51: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/teams-toolkit-fundamentals.md

Line 159, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
6
link
:white_check_mark:

msteams-platform/get-started/glossary.md
95
17
link
:white_check_mark:

msteams-platform/toolkit/add-single-sign-on.md
90
11
link
:white_check_mark:

msteams-platform/toolkit/prerequisites-tools.md
91
12
link
:white_check_mark:

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

Docs Build status updates of commit 292a9b2:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/tabs/how-to/tab-requirements.md
:warning:Warning
View
Details

msteams-platform/toolkit/prerequisites-tools.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/toolkit/TeamsFx-collaboration.md
:warning:Warning
View
Details

msteams-platform/toolkit/teams-toolkit-fundamentals.md
:warning:Warning
View
Details

msteams-platform/get-started/glossary.md
:white_check_mark:Succeeded
View

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-single-sign-on.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/tab-requirements.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites-tools.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites-tools.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/toolkit/prerequisites-tools.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites-tools.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites-tools.md(10,1)'. First level headings must be unique within a docset.
Line 14, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.
Line 15, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/provision.md

Line 22, Column 29: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/TeamsFx-collaboration.md

Line 20, Column 51: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/teams-toolkit-fundamentals.md

Line 159, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
7
link
:white_check_mark:

msteams-platform/get-started/glossary.md
95
17
link
:white_check_mark:

msteams-platform/toolkit/add-single-sign-on.md
90
11
link
:white_check_mark:

msteams-platform/toolkit/prerequisites-tools.md
91
12
link
:white_check_mark:

msteams-platform/toolkit/provision.md
91
57
link
:white_check_mark:

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

Docs Build status updates of commit 1e34900:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/tabs/how-to/tab-requirements.md
:warning:Warning
View
Details

msteams-platform/toolkit/prerequisites-tools.md
:warning:Warning
View
Details

msteams-platform/toolkit/TeamsFx-collaboration.md
:warning:Warning
View
Details

msteams-platform/toolkit/teams-toolkit-fundamentals.md
:warning:Warning
View
Details

msteams-platform/get-started/glossary.md
:white_check_mark:Succeeded
View

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/add-single-sign-on.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/tab-requirements.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites-tools.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites-tools.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/toolkit/prerequisites-tools.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/prerequisites-tools.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/prerequisites-tools.md(10,1)'. First level headings must be unique within a docset.
Line 14, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.
Line 15, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/TeamsFx-collaboration.md

Line 20, Column 51: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

msteams-platform/toolkit/teams-toolkit-fundamentals.md

Line 159, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'accounts.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
6
link
:white_check_mark:

msteams-platform/get-started/glossary.md
95
17
link
:white_check_mark:

msteams-platform/toolkit/accounts.md
91
12
link
:white_check_mark:

msteams-platform/toolkit/add-single-sign-on.md
90
11
link
:white_check_mark:

msteams-platform/toolkit/provision.md
91
57
link
:white_check_mark:

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

Docs Build status updates of commit b051f75:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/get-started/glossary.md
:warning:Warning
View
Details

msteams-platform/tabs/how-to/tab-requirements.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:warning:Warning
View
Details

msteams-platform/toolkit/accounts.md
:warning:Warning
View
Details

msteams-platform/toolkit/add-single-sign-on.md
:warning:Warning
View
Details

msteams-platform/toolkit/provision.md
:warning:Warning
View
Details

msteams-platform/get-started/glossary.md

Line 75, Column 2: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/prerequisites-tools.md'.
Line 120, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/prerequisites-tools.md'.
Line 121, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../toolkit/prerequisites-tools.md'.

msteams-platform/tabs/how-to/tab-requirements.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/accounts.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/accounts.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/TOC.yml

Line 104, Column 15: [Warning: file-not-found - See documentation] Invalid file link: 'toolkit/prerequisites-tools.md'.

msteams-platform/toolkit/accounts.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'Prerequisites - Teams' is duplicated in: 'tabs/how-to/tab-requirements.md(2,8), toolkit/accounts.md(2,8)'. Titles must be unique within a docset.
Line 10, Column 1: [Warning: duplicate-h1s - See documentation] H1 'Prerequisites' is duplicated with other articles: 'tabs/how-to/tab-requirements.md(10,1), toolkit/accounts.md(10,1)'. First level headings must be unique within a docset.

msteams-platform/toolkit/add-single-sign-on.md

Line 354, Column 3: [Warning: file-not-found - See documentation] Invalid file link: 'prerequisites-tools.md'.

msteams-platform/toolkit/provision.md

Line 22, Column 29: [Warning: file-not-found - See documentation] Invalid file link: 'prerequisites-tools.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
6
link
:white_check_mark:

msteams-platform/get-started/glossary.md
95
17
link
:white_check_mark:

msteams-platform/toolkit/accounts.md
91
12
link
:white_check_mark:

msteams-platform/toolkit/provision.md
91
57
link
:white_check_mark:

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

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

File
Status
Preview URL
Details

msteams-platform/get-started/glossary.md
:white_check_mark:Succeeded
View

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/toolkit/accounts.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/provision.md
:white_check_mark:Succeeded
View

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

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

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
97
6
link
:white_check_mark:

msteams-platform/get-started/glossary.md
95
17
link
:white_check_mark:

msteams-platform/toolkit/accounts.md
90
13
link
:white_check_mark:

msteams-platform/toolkit/provision.md
91
58
link
:white_check_mark:

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

Docs Build status updates of commit 1e35635:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Closing the PR due to multiple conflicts.


Update website to reflect modal v1.3.0

This includes modifications:

Update bower components
Update website version
Some link issues resolved
Some Sass import issues resolved

Thanks.


gocb 2.6.1 update

i can't fix opentelemetry_test.go because metrictest is removed

Thanks @henesgokdag sorry for the slow review. I'll try to find some time to look into how to update testing now that metrictest doesn't exist.

Closing as we have now merged a change to update to 2.7.2


Change tempest full to parallel run

Substitute -t (serial) option with --parallel to speed up tempest full
Even though parallel is the default i left it to be more explicit.

@kbaikov Can all tests run in parallel? Isn't there any risk for some strange and unexpected failures?

The only reason it was switched to serial was for ease of debugging. Serial actions are easier to track in logs.
But the speedup of the parallel run is worth it.

@vmoravec I run with this option from jenkins no difference in test count and no visible issues  : See links below
parallel run which took about 30 min  https://ci.suse.de/view/Cloud/view/QA/job/cloud-mkphyscloud-qa-test-tempest-full/40/
non parallel took more than 2 h https://ci.suse.de/view/Cloud/view/QA/job/cloud-mkphyscloud-qa-test-tempest-full/39/

we didn't find issues with parallel runs on virtual hardware, also because we have project isolation for each test, and more stress on the system is good. +1 from me.


Add action cards discard pile

https://github.com/haunt-roll-fail/haunt-roll-fail/blob/3829ee3eb7da30ba4d49f2726e55ac1804be76fd/haunt-roll-fail/arcs/game.scala#L1534
How much guardrail do we need for actions that would result in no gain? Right now there is no boundary, so up to the players to decide if they should carry out the action. The same can be applied to Farseers, that if there is not enough cards in the deck (blind and open alike), it is okay to do enough (taking all available cards).

Generally I'm inclined not to prompt meaningless actions, even if they are technically allowed.
And I also try to warn players if they skip free actions, or do something 99.99% players playing to win wouldn't do.
If some marginal denial strategy exists that can make such an action worth considering, I would add a separate menu action that would clearly state that this action wastes resources with no other effect.
(Like I wouldn't prompt an action called "Place 3 ships in a controlled system" to a player with Skirmishers or Loyal Marines, but no ships in supply. Though if playing guild cards just so they can't be stolen is a thing, I would add a sub-menu called "Discard Guild Cards Without Effect" and allow discarding them from there. I wouldn't prompt for the system to place non-existent ships in.)

Agreed that some helpful hint when an action won't fully resolve will be helpful. Can we stage that change in another PR, as many actions will need to be enhanced to warn the user.


hwmv2: Port STM32MP1X SoCs & boards

Port STM32MP1X SoCs & boards to Hardware Model V2.

Despite inforamtion coming from yaml, I wonder if vendor should actually be 96boards instead of arrow (see https://www.96boards.org/product/avenger96/)

I agree.

Rebased to resolve conflict.

ajarmouni-st requested review from arnopo and erwango now

By mistake, sorry!

rebase needed

rebase needed


New Client Template

Created New Client Template

Template looks good.

@ccifra  Please review the new client tool

The client will not work if we need to update the client code with a changed proto. Given, client will not have use generated code, users can recreate client from scratch as a temp fix
I have tested the "Server Stream" and "Unary" - There are issues during run with "Client Stream". I am not sure what are the use cases for "Bidirectional". Please use this and test the solution for these two cases and send me a example if possible.
Fixed the issue that is reported recently - when script is rerun with a proto containing new message.


Fix logging for elastic beanstalk

Changes
In pre-production one of the instances was unable to write the log files do to permissions issue on the box. This causes the application to fall over on startup. It seems to be a common problem with django and elastic beanstalk. The recommend approach seems to be to create a directory in /var/log on the ec2 instance and give it the correct permission for the application, then all application log files should be written there.
How to test

Deploy this change to elastic beanstalk
Check both instances are responding correctly
Check the log file exists in /var/log/author

Who can test
Anyone apart from @warrenbailey

Temporarily closing

LGTM :+1: Needs a rebase though


ValueError: too many values to unpack (expected 2)

Hello,
First of all, thank you for your work !
I will use your work for a school project but when I launch ./run_sample_training_pipeline.sh but i have a Python error : ValueError: too many values to unpack (expected 2)

The program seems to work on other, so that can be a Python version error.
On my computer i have got the Python 3.7.2 version can you give me yours ?
Thank you in advance.

i think the code was broken for a bit.. can you try to sync and run the script again? sorry about that...

How can I sync it ?

depends on how you cloned the repo, but i'm guessing it's going to be just git pull origin master

I already pull but the branch is up to date. The latest was 7 days ago.

great. i'm on python 3.5.2
two questions;

do you see this every time you run run_sample_training_pipeline.sh ?

what version skimage do you have? i'm on 0.13.0

python3 -c "import skimage;print(skimage.__version__)"

i should add a requirements.txt .... #15

I see this error every time I use run_sample_training_pipeline.sh, and i tested it on 2 computers. Same error. One on Mac Os Mojave and one on ArchLinux.
My skimage is 0.14.2.
I will try to downgrade my python version tomorrow and I will keep you updated.

not sure it's a python version, but something about the centroid
that error implies region.centroid is an iterable with >2 elements but  the skimage docs (for all versions) just lists the centroid as being a two tuple... http://scikit-image.org/docs/dev/api/skimage.measure.html#skimage.measure.regionprops
you could stick a print in the line above and see what region.centroid is ...

Ok, I add a print(region.centroid) in utils.py and the value of region.centroid is (255.5, 191.5, 0.0).

I dont know how skimage work so I can't tell you if this value are good or not.
Thank you for your help.

i'd expect a 2 tuple there, not a 3 tuple. the skimage docs for all versions i've checked (including 0.14) say that centroid from regionprops will be a 2 tuple... i can't explain it sorry
http://scikit-image.org/docs/0.14.x/api/skimage.measure.html#regionprops

So I will try to solve this problem and open a pull request if I solve it.
Thank you !

That's it ! You can merge it. 😄

fixed in #16
thanks!


Edit item

Especially on a phone, it is too easy to make (especially, when my wife has MS and her hands are a bit shakey). How can I edit the text of an item?

Thanks for you feedback!
Are you talking about 2 separate problems?
I think it would be possible the make the longtap time longer. Maybe as an option. Did you mean that?
As of now it is not possible to edit the text. However, I see no problem to implement it.

Sorry, I was trying to be funny and I was just confusing (happens to me all the time, sigh). No, I meant just editing the text.

Sorry, It's been a long day;)
But yeah, editing should be possible!

This will only be possible after we also update the backend. But that wont happen before app v2.0 will be there.

OK, not holding my breath then ;)


WorkboxWebpackPlugin.GenerateSW: "non-precached-url" error after updating from v5 to v6

Library Affected:
workbox-webpack-plugin
Browser & Platform:
all browsers
Issue or Feature Request Description:
I have an error in the console after updating workbox-webpack-plugin from v5.1.4 to v6.0.2:

And offline lighthouse test is broken now.
My config:
cacheId: 'rentalreport',
navigateFallback: '/index.html',
navigateFallbackAllowlist: [/^(?!\/__)/],
swDest: 'sw.js',
clientsClaim: true,
skipWaiting: true,
cleanupOutdatedCaches: true,
exclude: [/\.mp4$/, /\.map$/, /\.cache$/],
runtimeCaching: [{
  urlPattern: /\.(?:jpe?g|png|svg|css|js)$/,
  handler: 'NetworkFirst'
}]

I didn't find how update config for v6.0.2.
What do I need to change?

What does you precache manifest (the array that's passed in to precacheAndRoute()) look like in your generated service worker? Are you manually editing that list in some way, like by adding in 'index.html'?

What does you precache manifest (the array that's passed in to precacheAndRoute()) look like in your generated service worker? Are you manually editing that list in some way, like by adding in 'index.html'?

You'll get that error if you use navigateFallback and pass in the URL of an HTML document that isn't precached.
If you want to use navigateFallback: 'index.html', then make sure that your index.html document is included in your precache manifest.
Are you usinig html-webpack-plugin (if so, which version?) to generate your index.html, or some other approach? And what version of webpack are you using?

You'll get that error if you use navigateFallback and pass in the URL of an HTML document that isn't precached.
If you want to use navigateFallback: 'index.html', then make sure that your index.html document is included in your precache manifest.
Are you usinig html-webpack-plugin (if so, which version?) to generate your index.html, or some other approach? And what version of webpack are you using?

index.html is not included in the precache manifest
GenerateSW v6.0.2 generates sw.js which includes only:
e.registerRoute(new e.NavigationRoute(e.createHandlerBoundToURL("/index.html")
GenerateSW v5.1.4 generates sw.js which includes:
e.precacheAndRoute([{url:"/index.html",revision:"5cb3ce05c54e0ab0fe42583e6b65801a"},...])
and
e.registerRoute(new e.NavigationRoute(e.createHandlerBoundToURL("/index.html")
Yes, I use html-webpack-plugin v4.5.1 and webpack v5.15.0.

index.html is not included in the precache manifest
GenerateSW v6.0.2 generates sw.js which includes only:
e.registerRoute(new e.NavigationRoute(e.createHandlerBoundToURL("/index.html")
GenerateSW v5.1.4 generates sw.js which includes:
e.precacheAndRoute([{url:"/index.html",revision:"5cb3ce05c54e0ab0fe42583e6b65801a"},...])
and
e.registerRoute(new e.NavigationRoute(e.createHandlerBoundToURL("/index.html")
Yes, I use html-webpack-plugin v4.5.1 and webpack v5.15.0.

Thanks for that info. I believe what's going on is that you're using a version of html-webpack-plugin that isn't fully compatible with webpack v5. Your generated index.html ends up not being visible to workbox-webpack-plugin when using webpack v5, so it can't be precached.
As per the current html-webpack-plugin docs, you need to use the next release for webpack v5 compatibility:
npm i --save-dev html-webpack-plugin@next

Thanks for that info. I believe what's going on is that you're using a version of html-webpack-plugin that isn't fully compatible with webpack v5. Your generated index.html ends up not being visible to workbox-webpack-plugin when using webpack v5, so it can't be precached.
As per the current html-webpack-plugin docs, you need to use the next release for webpack v5 compatibility:
npm i --save-dev html-webpack-plugin@next

https://github.com/vite-pwa/vite-plugin-pwa/issues/731


Add parser and scenario aidalinfo/tcpudp-flood-traefik

Hello Crowdsec team !
Here is my parser and scenario linked to the article for tcp/udp flood protection with traefik reverse proxy. I followed the workflow well it seems. I've done the hub test and the hub explain.
I remain at your disposal if needed!
Thanks.

Also I would suggest using cache_size to limit how many items are held in memory because 1000 would most likely cause RAM issues

Hi !
@LaurenceJJones Thank you for your recommandation I've added cache size of 300 for optimize memory. This is ok you think ?
@buixor I've added assert file ! I think that ok :)
cli result :
☁  hub [tcpudp-flood-traefik-aidalinfo] ⚡  ../cscli -c ../dev.yaml hubtest run tcpudp-flood-traefik
INFO[16-01-2024 13:43:28] Running test 'tcpudp-flood-traefik'
INFO[16-01-2024 13:43:32] Test 'tcpudp-flood-traefik' passed successfully (94 assertions)
───────────────────────────────
Test                   Result
───────────────────────────────
tcpudp-flood-traefik   ✅
───────────────────────────────

I still think 300 too large, other than once it overflows what will the user do with the information? other than they already know it to be a tcp/udp attack

Ok I understand, Thank you !


SwagCommercial -> EmployeeDetailPageEvent has no Employee.

Used Shopware Version: <IP_ADDRESS>
B2B for Shopware 6
Hi,
I've got Problem with SwagCommercial Plugin, there is not project to select like this.
Problem is in B2B Components (6.5.0 version).
In:
B2B/EmployeeManagement/Storefront/Page/Employee/Detail/EmployeeDetailPageLoader:57
setEmployee is set after event is executed.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/B2B-1258.
[created from NEXT-40115, comment 485023]

[public] Shopware automated response: This issue is linked to the internal issue: NEXT-40115
[created from NEXT-40115, comment 529549]


Implement and test LUT4

Added LUT4 to netlist data-type and monad API for Cava and produced a small test to check against config LSB/MSB errors.
xsim --tclbatch lut4_and_tb.tcl lut4_and_tb_sim

****** xsim v2018.3 (64-bit)
  **** SW Build 2405991 on Thu Dec  6 23:36:41 MST 2018
  **** IP Build 2404404 on Fri Dec  7 01:43:56 MST 2018
    ** Copyright 1986-2018 Xilinx, Inc. All Rights Reserved.

source xsim.dir/lut4_and_tb_sim/xsim_script.tcl
# xsim {lut4_and_tb_sim} -autoloadwcfg -tclbatch {lut4_and_tb.tcl}
Vivado Simulator 2018.3
Time resolution is 1 ps
source lut4_and_tb.tcl
## open_vcd lut4_and_tb.vcd
## log_vcd *
INFO: HDL object /lut4_and_tb/i0_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i1_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i2_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i3_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/o_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
## log_vcd [ get_objects * ]
INFO: HDL object /lut4_and_tb/i0_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i1_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i2_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/i3_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
INFO: HDL object /lut4_and_tb/o_vectors is an unpacked array. VCD does not support unpacked array type according to IEEE LRM 1800-2009, section21.7.5.
## add_force {/lut4_and_tb/clk} {0 0ns} {1 50ns} -repeat_every 100ns
## run 200ns
               50000: tick = 0, i0 = 0, i1 = 0, i2 = 0, i3 = 0, o = 0
              150000: tick = 1, i0 = 1, i1 = 1, i2 = 1, i3 = 1, o = 1
PASSED
## flush_vcd
## close_vcd
## exit
INFO: [Common 17-206] Exiting xsim at Thu May  7 20:57:49 2020...

Self-merging.


Question about potential AMR improvements

Hey there! I was reading the MFEM implementation of AMR in https://docs.mfem.org/html/classmfem_1_1ThresholdRefiner.html#a38c1c7e70aa4854dac52e5a076c220e7 and I noticed you were sequentially traversing all the elements in the mesh each time you were going to refine it, so I was wondering if it was possible to refine the mesh in a more efficient way. For instance, I know that Paramesh(https://ntrs.nasa.gov/api/citations/19990110710/downloads/19990110710.pdf) used some sort of hierarchical approach dividing the mesh into half's (similarly to a binary search). Additionally, I was wondering if there were plans to implement AMR with reinforcement learning in MFEM, as shown in this paper from LLNL scientists (https://proceedings.mlr.press/v206/yang23e/yang23e.pdf).
Best Regards,

ping: @jakubcerveny, @rw-andersonm, @tarikdzanic


INCIDENT-599: Stop parsing reprove identity claim

Proposed changes
What changed
Stop parsing reprove identity claim
Why did it change
A change has been made in Orch that has meant that the value coming through is no longer a string - possibly a boolean.
This is causing the getStringClaim() method to throw. This has caused a P1 outage.
The change on orch side is being reverted - this change is a backup just in case to return functionality.
Issue tracking

INCIDENT-599

Closing due to the Orch reversion working


what if workers had a web server?

start to replace pios commands with API endpoints -> pios no longer SSHs, just sends API requests.
can have access to local calibrations, plugins
API:

GET ??: returns which jobs are running
GET ??: which plugins are installed
PATCH ??: replaces monitor run callback.

start of change towards #232
lighttpd + flask again.

same port as main ui (look in config.ini)

maybe a ui with very basic information for debugging?

config.ini?
read-only view of JobManager database?

Changes required to workers

[ ] install lighttpd
[ ] install huey? Sure why not.
[ ] install all the other ui python libs (list needed)

This makes me want to merge the images: the python requirements are nearly the same, same folder for www, lots of similar services. However, no MQTT, no db app, no mqtt-to-db, chrony, okay yea no merge yet.

It is a good idea to restrict hitting the worker api unless your leader. We can do this with lighttpd confs (and env variables).

Basically the goal of this first is to remove any instances of ssh-ing from the leader to workers, replaced with web request to their servers.


[5.8] Get the available user instance.

Get the available user instance:
You can get the available user instance by user() general helper function.

I think there are already easy ways to get this? Auth::user() ... $request->user()


Organise CSS files and update confi.py file

Description

Move css files from _static/ to _static/css. Therefore, the
_templates/Layout.html is updated
Modify open and close dates of the course manual. I also modify the version of the course. (The idea is to change the version every time we make changes in the course manual, but it is just a plan.)

Testing
I tested manually, the a+ manual was compiled and visualised in a firefox browser.

[ ] I (developer) have created unit tests and the tests pass
[ ] I (developer) have created functional tests (Selenium tests) if applicable
[X] I (developer) have tested the changes manually
[ ] Reviewer has finished the code review
[ ] After the review, the developer has made changes accordingly
[ ] Customer/Teacher has accepted the implementation of the feature

No preferences on how to merge the PRs. I think I will handle the conflicts myself.

I split changes into two commits. and now it should be ready for the review

@jaguarfi one of the commits seems to be empty now. It includes no changes at all.

There is no reasoning or answer to "why" in the commit or the description here and this doesn't fix any issues, thus resoning for these changes isn't anywhere.
That said, less there are this the teacher needs to copy to a new coruse the better. Thus, if there are no styles the manual requires, then there shouldn't be a css file. However, it would be fine to include a placeholder, if we asume the course implementation in the repository is considered an example implementation.

@Mankro yes, you are right. I had problems with git rebase -i I am still  learning that.

@raphendyr are you talking about the course.css file?

@raphendyr are you talking about the course.css file? .I also changed the description of the commit message.

Yes. The course.css. It includes definitions for .admonition, which seems to be in a-plus-rst-tools too (in aalto theme). Also, there is stuff about .topic too. If these are (or should be) in rst-tools,t hen they could be updated there.
Furthermore, active_element.css includes css defitions, which are way too generic for the name like .left and .right. Aren't these provided by bootstrap with .pull-right and so on? In addition, I think all active elements related should be in rst-tools.
These are not exactly about the PR, but the PR happens to keep these files around, when I don't think they should be in the course repo at all.

This change helps keep files organised, and it might help to automated proccess such as minification by using wildcards. For example, in gupl we could use something like this gulp.src('./lib/*.css')

Currently, glob match of _static/*.css would be enough. In the future _static/css/*.css and possibly _static/css/*.sass could be used. In short, the folder structure doesn't help with automation, but it could help humans to navigate the content under _static.

True, there is room to consider which styles should be defined in a-plus-rst-tools and what is course-specific.

I will keep the course.css file here for now, although those styles should be moved to the aplus theme in the future. Since there couple of things that need to be improved in the aplus theme, we can start with apluslms/a-plus-rst-tools#88 as a first step, and later on we can analise  the theme in more detail, after the summer interns finish with all the changes to the UI and the accesibility audit.
The active-elements.css files has been used as an example here. Therefore, we can create an issue for updatind the active-elements example. In addition, having the css follder can help for human navigation. (As a side note, yes, you are right about glob match, I was thinking in something else but I mixed my thoughts up :) )
But, what I want to accomplish with this PR is to start organizing the course content and use it as a course manual. The course template will be something different (I am still working on that), and it should not contain course specific files such as the course.css file


mTLS auth endpoint bubbles up error with Enterprise free mode

Enterprise images running in free/unlicensed mode return 403s for endpoints that are Enterprise-only.
dump.GetAllMTLSAuths() has logic to return an empty set of mTLS auth credentials when the response is a 404 (what OSS images return) but nothing for a 403, which bubbles back up to dump.Get() and upward: https://github.com/Kong/deck/blob/v1.4.0/dump/dump.go#L616-L622
Handling this is a bit tricky, as this endpoint can return a 403 in different situations. Either:

Enterprise is running in free mode, and this endpoint is not available at all.
Enterprise is running in licensed mode, but decK is using an RBAC user that lacks permissions for it.

Do we need to handle these differently? In free mode, the 403 is effectively equivalent to a 404, since the database can't possibly contain any mTLS auth entities. In licensed mode, mTLS auth entities may exist, but decK cannot see them.
Treating either type of 403 the same as a 404 in dump.Get() may be fine. An empty entity set isn't of much interest until you try to solve later. If you haven't asked decK to create any such entities, it should and will do nothing. If you have asked decK to create that entity type, that failure will bubble up, and should, as decK cannot reconcile the state.

From previous initial discussion with @hbagdi, we want to avoid treating 403s like 404s if possible. We could instead infer that this endpoint is unavailable from a combination of the version and license available from the root endpoint. I don't think there's any explicit free mode marker, but the license object is just absent when using it:
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# export KONG_LICENSE_DATA='{}'
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# kong start
Using Konnect Enterprise without a license
Kong started
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# curl -s localhost:8001 | jq ".version, .license"
"<IP_ADDRESS>-enterprise-edition"
null
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# export KONG_LICENSE_DATA='{"license":"REDACTED"}'
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# kong restart
Kong stopped
Kong started
[kong-enterprise-edition-<IP_ADDRESS>-alpine:/]# curl -s localhost:8001 | jq ".version, .license"
"<IP_ADDRESS>-enterprise-edition"
{
  "customer": "Kong Inc",
  ...
}

At present I don't think we have general-purpose Enterprise/version gates in decK; this would require we build one. The Enterprise-only stuff is, AFAIK, documented as such, but ultimately we trust users not to use features (workspace creation, RBAC entities) if they're not available.

I just ran into this and I see another user in Kong Nation did as well: https://discuss.konghq.com/t/deck-fails-with-mtls-auths-403-error/7918
This renders Free Mode incompatible with decK until fixed.

@rainest Given the high-impact nature of this problem, let's treat 403 and 404 for this case. We want to avoid unlicensed and licensed differentiation in decK as far as possible as it unnecessarily complicates the code. In your patch, please add a comment in the code to explain a) what we are doing is bad b) why we still do it c) it MUST not be repeated anywhere else.

We want to avoid unlicensed and licensed differentiation in decK as far as possible

I don't know that we can actually get away from this entirely given the way Enterprise works, where some endpoints aren't available depending on your settings, but we can do it more elegantly. IMO something along the lines of the go-kong test feature detection seems appropriate. Instead of inferring this from the response code, we can check the root API endpoint to check if we're in free mode or if RBAC is disabled and make the associated decK functions return empty object sets.


feature: golang runtime library definition

Defines go runtime library package and begins layout of process management and request/response flow. Begins test suite that initializes client and verifies expected response from node runtime. Adds build scripts for embedding js runtime lib and generating jsii-calc go modules for testing.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 97ff125d81d3765fe9aec96bc4b49b9a5f0afb07
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: f35d2e3e11e0ebad4f32d315f951524356398843
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 9f07ab4a0276a296c93928d5ce463ec2e66e825e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: bf51fd537c3da55e14575d7624ca9144c2c4f879
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 1cd61f15c5362afc545c9b5ce05e96a860909734
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 0bace9f3de9b23689330ebda5946948e1e54fc7c
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


EXT form: remove doubled form state

Description
Removes double rendering of ext form, data is kept in an immutable record (ui-schema format) and converted only at need (instead of at every keystroke).
UPDATE: a test fails only on CI, added a temp commit to test it.
Related issue(s)
Resolves #1810

/test pre-busola-integration-test-k3s-cluster

/test pre-busola-integration-test-k3s-cluster

/test pre-busola-integration-test-k3s-cluster

/test pre-busola-integration-test-k3s-cluster

/test pre-busola-integration-test-k3s-cluster

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace

/test pre-busola-integration-test-k3s-namespace