BUG crashed in pickling

Describe the bug
On the second run of my task, the following log line triggers continuously in a loop forever:
CRITICAL:rocketry.task:Task 'daily_notification' crashed in pickling. Cannot pickle: {'__dict__': {'session': <rocketry.session.Session object at 0x2f6d4f9a0>, 'permanent': False, 'fmt_log_message': "Task '{task}' status: '{action}'", 'daemon': None, 'batches': [], 'name': 'daily_notification', 'description': None, 'logger_name': 'rocketry.task', 'execution': None, 'priority': 0, 'disabled': False, 'force_run': False, 'force_termination': False, 'status': 'run', 'timeout': None, 'parameters': Parameters(), 'start_cond': None, 'end_cond': None, 'multilaunch': None, 'on_startup': False, 'on_shutdown': False, 'func_run_id': None, 'func': <function daily_notification at 0x1038cd4c0>, 'path': None, 'func_name': 'main', 'cache': False, 'sys_paths': []}}

The log line is the same each time, except for the Session object reference.
On  CTRL+C the trace back contains:
INFO:rocketry.scheduler:Interupted. Shutting down...
Traceback (most recent call last):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/schedule.py", line 128, in serve
    await self.run_cycle()
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/schedule.py", line 182, in run_cycle
    await self.run_task(task)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/schedule.py", line 211, in run_task
    await task.start_async(log_queue=self._log_queue)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 514, in start_async
    self.run_as_process(params=params, direct_params=direct_params, task_run=task_run, **kwargs)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 735, in run_as_process
    process.start()
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/process.py", line 121, in start
    self._popen = self._Popen(self)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/context.py", line 224, in _Popen
    return _default_context.get_context().Process._Popen(process_obj)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/popen_fork.py", line 19, in __init__
    self._launch(process_obj)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/popen_spawn_posix.py", line 47, in _launch
    reduction.dump(process_obj, fp)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/multiprocessing/reduction.py", line 60, in dump
    ForkingPickler(file, protocol).dump(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in __getstate__
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in <dictcomp>
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in __getstate__
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in <dictcomp>
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in __getstate__
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1324, in <dictcomp>
    unpicklable = {key: val for key, val in state.items() if not is_pickleable(val)}
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1318, in __getstate__
    if not is_pickleable(state):
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/utils/pickle.py", line 6, in is_pickleable
    pickle.dumps(obj)
  File "/Users/tekumara/code/dt-web-glimpse/.venv/lib/python3.9/site-packages/rocketry/core/task.py", line 1326, in __getstate__
    self.logger.critical(f"Task '{self.name}' crashed in pickling. Cannot pickle: {unpicklable}", extra={"action": "fail", "task_name": self.name})
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1835, in critical
    self.log(CRITICAL, msg, *args, **kwargs)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1844, in log
    self.logger.log(level, msg, *args, **kwargs)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1512, in log
    self._log(level, msg, args, **kwargs)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1589, in _log
    self.handle(record)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1599, in handle
    self.callHandlers(record)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1661, in callHandlers
    hdlr.handle(record)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 952, in handle
    self.emit(record)
  File "/Users/tekumara/.pyenv/versions/3.9.13/lib/python3.9/logging/__init__.py", line 1086, in emit
    stream.write(msg + self.terminator)
KeyboardInterrupt
INFO:rocketry.scheduler:Shutdown completed. Good bye.

My task:
@app.task(hourly)
async def daily_notification() -> None:
    file = "summary.png"
    # we are using the sync clients so run them on a thread
    await to_thread.run_sync(
        glance.browser.screenshot,
        file
    )
    await to_thread.run_sync(glance.slack.upload_screenshot, file)

Desktop (please complete the following information):

OS: macos
Python version 3.9

Additional context
rocketry 2.5.1

As a workaround, switching the task execution to thread or async (rather than default of process) avoids this problem, presumably because pickling doesn't need to happen.

Thanks for reporting this! These pickling issues are often hard to find as they are often OS-dependent or come up in special situations.
I think an unpicklable attribute from Rocketry's session leaks to the process for some reason.
If interested, the task sort of prunes the session:

In the task pickling: https://github.com/Miksus/rocketry/blob/master/rocketry/core/task.py#L1316
Pruning the session: https://github.com/Miksus/rocketry/blob/master/rocketry/session.py#L541-L547

If I remember correctly, the process task needs some config options from the session thus most of the session configs are pickled. I tried to make it so that it would throw away only known unpicklable attributes, but I am not sure if it should work the other way around (including only the ones we know we can pickle).
Another could be the function but that function looks pretty standard.
How are your app configurations, and do you perhaps set some attributes to the session?

Thanks for the explanation!
This is the only config I have:
app = Rocketry(
    # see https://rocketry.readthedocs.io/en/stable/handbooks/config.html
    config={
        "task_execution": "process",
    }
)

Interestingly, if I remove that config and just use app = Rocketry() it works even though I though that process was the default.


Asset metadata overwrite fix

Fixes https://github.com/lightninglabs/taproot-assets/issues/368.
As @habibitcoin already correctly identified, one of our SQL queries is incorrect and overwrites valid meta information with NULL when importing a proof.

Woot! Confirmed this works locally as well. Thanks!


IF the localhost configs give you pause, feel free to remove them.


Improve tests

I use Jest all over the place. I think we should use it, however, I don’t care about the tool used (Jest, Mocha, …), but we need to create robust tests.
We already have some tests, but it is quite messy and not thourough.

Closing as duplicate of #171


SvelteKit won't build because scripts added in the head element with strict CSP use a nonce

Describe the bug
Ok so basically I'm using strict CSP with kit.csp.mode set to "auto" and I added %sveltekit.nonce% to the nonce attribute of a <script> located in the <head> of app.html as instructed by the docs.
This causes the build to fail with the following error:
Error: Cannot use prerendering if page template contains %sveltekit.nonce%

Setting kit.csp.mode to "hash" is not an option since scripts in kit.csp.mode can only use a nonce.
Also, I'm not aware if nonces are considered better than hashes, but they do seem more lightweight, so that's potentially another reason a developer would not want to set kit.csp.mode to hash.
The only solution is to either manually calculate the hash and add it to the CSP policy but obviously that's not a good idea because, when I tested, SvelteKit successfully compiles with the wrong hash, and all it would take is for one character to change in the script, the developer forgetting to change the hash, not noticing the error, and the result would be a pretty nasty bug in production.
Or, as a workaround, you could disable prerendering entirely, which would be arguably even worse.
I think the solution here should be to either make SvelteKit use hashes for scripts in app.html, or to offer a %sveltekit.hash% placeholder, similar to %sveltekit.nonce%, thus giving the user more flexibility by being slightly less convenient.
I'm not sure whether this should be a bug report or a feature request, I ended up choosing to report it as a bug, sorry if it was the wrong choice.
Reproduction
To repro just run npm run build
https://stackblitz.com/edit/sveltejs-kit-template-default-jntr65
Logs
No response
System Info
N/A (bug can be easily reproduced in StackBlitz and has nothing to do with the underlying environment)

Severity
serious, but I can work around it
Additional Information
No response

It's deliberate:

When mode is 'auto', SvelteKit will use nonces for dynamically rendered pages and hashes for prerendered pages. Using nonces with prerendered pages is insecure and therefore forbidden.

https://github.com/sveltejs/kit/blob/737eb67aea8a29f891327856006ec6f25ad76f2b/packages/kit/src/runtime/server/page/render.js#L59
I couldn't find anything on why there are no hash's in the app template so I'll leave this open

@ghostdevv What's the workaround that you've come up with?

I don't remember having one unfortunately

I was about to open an issue for this as well. While the docs clearly state nonces can't be used for prerendered pages it's also the only way to add nonces to inline scripts in app.html. So in some ways the docs contradict itself by creating this catch22 for apps that have both statically and dynamically rendered pages.
What I would expect for prerendered pages using app.html is to convert <script nonce="%sveltekit.nonce%" /> to `, where the "nonce" is simply used as a hash in the latter example.
My workaround was to simply create a loose CSP policy with an explicit allow list 🤷🏻
Haven't tried this, but in theory another workaround could be to include this script as a nonce in a main server layout file (nonce supported for dynamic pages), but that assumes the static pages won't need that same script =/


Prompt template overrides

Is your feature request related to a problem? Please describe.
I am modifying core templates from different providers to alter the style of thinking for my agent and control all aspects of its prompting.
Describe the solution you'd like
Override prompt templates in the character file for all prompts (twitter generation, search, interaction, etc)
Describe alternatives you've considered
Diverging (which would suck).

Merged, can add template overrides into character files


spark: 3.5.0->3.5.1, 3.3.3->3.3.4

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Link to currently reviewing PR:
https://github.com/NixOS/nixpkgs/pull/297234

4 packages failed to build:
python312Packages.dask-yarn python312Packages.dask-yarn.dist python312Packages.skein python312Packages.skein.dist

11 packages built:
hadoop hadoop2 hadoop_3_2 pig python311Packages.dask-yarn python311Packages.dask-yarn.dist python311Packages.skein python311Packages.skein.dist spark spark_3_3 spark_3_4

dask-yarn depends on skein. Skein is broken upstream.

@LeSuisse please revert bd4ade1943fee0116c4f427bed0f923649582383 and see the comment about spark versions in this PR

Hello,
I suggest to revert the changes in this PR if you wish.
For the records I proposed the removal of spark_3_3 because:

it is no more proposed for download on the download page of the upstream project, it does not seem fair for us, as a downstream distributor, to still propose it (it can leads to bug reports upstream on a version that is no more supported so it can be an extra load for the upstream project)
it should have been dropped before the release of 23.11 because the support range of spark_3_3 does not overlap the support range of 23.11
the release of 24.05 is not that far away

As mentioned in the comment, upstream's 18-month support window isn't a hard and fast rule, considering they sometimes release new versions the day before support supposedly ends. Removing what is essentially a 3 month old release as EOL doesn't make sense.
As for upstream being bothered by bug reports for unsupported versions, two of the three highest priority issues on upstream's jira are bug reports for spark 3.3.
That being said, you're right, 24.05 is not that far away. Adding it back just to remove it in a month is not worth the hassle. At least for future versions, please avoid removing packages that are deprecated by technicality.

The package is not even proposed on the upstream download page anymore, we are a bit past the "deprecated by technicality" stage.
BTW, it would be nice if you could sort out your addition to the NixOS/nixpkgs-maintainers team so you can get the notifications on this package. We already had a similar discussion in #230737 and I have a feeling it is not going to be the last time if it stays that way.

Thanks for merging. I had been added to NixOS/nixpkgs-maintainers a few months ago, but I did not get a notification for your PR. Maybe ofborg only tags maintainers for changes to packages, and not removals?


kodi: Fix Blu-ray ISO playback

Originally, attempting to play a Blu-ray ISO resulted in errors like:
2021-05-10 22:04:30.045 T:875821 WARNING <general>: CreateLoader - unsupported protocol(udf) in udf://%2fkodi-test-library%2fblu-ray-test.iso/BDMV/index.bdmv

and a failure to play the ISO file.
This log message originates from
https://github.com/xbmc/xbmc/blob/a80d1293b0579bbed7dd7d20304ba34a20519f78/xbmc/filesystem/FileFactory.cpp#L177,
which can only be generated when the check at
https://github.com/xbmc/xbmc/blob/a80d1293b0579bbed7dd7d20304ba34a20519f78/xbmc/filesystem/FileFactory.cpp#L139-L142
doesn't exist and hence doesn't recognize the udf:// protocol at all.
This ensures that the UDF-reading library is built and included
correctly, which allows Blu-ray ISO files to be played back successfully
once again.
I tested this on my local NixOS installation by making the change, then
running:
nix-shell -p kodi -I "nixpkgs=${NIXPKGS}" --command kodi

locally with success and seeing playback succeed for Blu-ray ISO files
using Kodi launched from within the shell.

Motivation for this change
Fix Blu-ray ISO playback in Kodi 19.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] 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/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Thanks for opening this PR. I have several questions:

why can't we use a copy of this library from nixpkgs?
i haven't really really with bluray technology much, especially the decrypting stuff, but don't we need more libraries than this? and to build libraries with non free configuration options that aren't enabled by default?
if i dig out a bluray disc can i trivially confirm kodi 19 won't play the disc; can i trivially confirm this PR allows me to play the disc?

I'll try to find a bluray disc once I can buy I'm pretty sure they're packed away in some boxes and not at my house at the moment...

Thanks for looking at it!
I would love to use this package from nixpkgs, but I was unable to locate it or an equivalent already in the repo, and hence went this route.
The contents of that archive look like this, for reference:
libudfread-1.1.0
├── bootstrap
├── ChangeLog
├── configure.ac
├── COPYING
├── examples
│   ├── udfcat.c
│   └── udfls.c
├── m4
│   └── attributes.m4
├── Makefile.am
└── src
    ├── blockinput.h
    ├── default_blockinput.c
    ├── default_blockinput.h
    ├── ecma167.c
    ├── ecma167.h
    ├── udfread.c
    ├── udfread.h
    ├── udfread.pc.in
    ├── udfread-version.c
    └── udfread-version.h.in

From what I can tell, my changes tell Kodi where the source code for libudfread lives and Kodi then includes it in the build rather than relying on an existing external library. I believe I found this URL by delving through the Kodi source, so apparently they expect this situation on some platforms and provide the source for this purpose.
There's nothing stopping us from finding someone who publishes this library and then including it, but I went this route only because it seemed like the path of least resistance.
As far as I can tell libudfread doesn't really have anything to do with Blu-ray specifically, but more with reading the UDF structure of disc images that Blu-ray happens to use. Kodi seems to already include the various Blu-ray libraries as part of its build since I didn't need to do anything else to get it working after making this change.
I haven't actually checked to see whether the patched/un-patched Kodi versions will play a Blu-ray disc directly as opposed to an image of one, but I can check that as well as I have the required hardware on hand. I could also try to cook up a minimal disc image that makes it easy to test for the problem, one that's not ~50GB in size.

Let's package libudfread separately (so other packages can use it and so it's visible to tools like vulnix): #153971

Fixed in other PR.


CSP Individual Final

CSP Individual Review:

One minute video, prepared in CPT style to highlight your feature with the project ie no voice and captions (Video)
Correlation to CPT, an article that show how your features or pull requests map to College Board requirements (Blog)

Peer Review:

Video

Done well:

Showcased all features of the program clearly
Concise, accurate, and relevant captions that did not block the program
Good use of zooms to focus on the program's functionality

Can improve on:

Expand more on the features
Video quality is slightly low and watermark is a little distracting
Potential typo at 0:37, "retried" --> retrieved?

Blog

Done well:

Detailed description of project's purpose and various personal contributions
Relevant and numerous code sections provided and how it fulfilled CollegeBoard's requirements was explained
Key commits and reflection was added in addition to the base requirements

Can improve on:

Add video requirements and explain how video met these
Explanations could be more focused on the requirements as some slightly derail into the full functionality or purpose of an aspect rather than how it meets the requirements

On this note, the explanation for the list/collection type can be expanded on to describe in more detail how it manages complexity

2 typos under "All Commits of February"

Grade

0.92/1. The requirements for the post (showing how code maps to CollegeBoard requirements) was done in good detail, and while some parts could be refined (either expanded to include more detail or edited to focus more on exactly how it fulfills the requirement) it was overall enough, and many code snippets, key commits, and a reflection was included on top.

Peer Review:

Video

Done Well:

Good showcase of website functionality and how everything worked
No unnecessary display and concise use of time
Good captions, explains simply

To improve:

Honestly thought it fit collegeboard requirements perfectly, not much to change other than stylistic stuff like watermarks

Blog

Done Well:

Clear explanation of requirements and project explanation
Went above and beyond on blog content
Strong relevant code sections

To improve:

A little too in depth at points - could be more concise
Missing display of what requirements the video fulfilled
Seems sometimes redundant

OVERALL GRADE:

.95/1. Went above and beyond on blog with extra sections like the reflection and key commits, very clear in what you fulfilled. Blog's only problem was conciseness, overall requirements were detailed. Video was clear and to the point, displayed functionality well. Good job!


Fix ElementList.getattr() to no longer hide ElementNotFound

When elements aren't found on the page, calling methods like ElementList.click() didn't raise this error. Instead it would report "AttributeError: 'ElementList' object has no attribute 'click'" which confuses users to look at other places than the actual error.

@vdboor thanks for contribute.


Large modal missing scrollbar after close a small modal up on it

v4.0.0-alpha.2.
The large modal has scrollbar due to is too height,but if I open a small modal up on it,after the small one close,the large modal's scrollbar is missing.

My solution for this issue is hide the large modal before show the small one,and show it back after the small one closed.
Is there a better options?
The
$('#myModal').data('bs.modal').handleUpdate()
//actually is
$('#myModal').data('bs.modal')._handleUpdate()

does nothing in my case.

@unbug Please post a JS Bin or JS Fiddle that reproduces the problem.

@cvrebert Sorry for the delay,here is the demo

Hi @unbug!
You appear to have posted a live example (https://jsbin.com/bahacos/edit), which is always a good first step. However, according to the HTML5 validator, your example has some validation errors, which might potentially be causing your issue:

line 21, column 1 thru column 118: The aria-labelledby attribute must point to an element in the same document.
line 455, column 1 thru column 118: The aria-labelledby attribute must point to an element in the same document.

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

@cvrebert Ok,bot,I fixed the issue demo

Hi @unbug!
You appear to have posted a live example (https://jsbin.com/bahacos/edit), which is always a good first step. However, according to Bootlint, your example has some Bootstrap usage errors, which might potentially be causing your issue:

W002: <head> is missing X-UA-Compatible <meta> tag that disables old IE compatibility modes

You'll need to fix these errors and post a revised example before we can proceed further.
Thanks!
(Please note that this is a fully automated comment.)

See http://v4-alpha.getbootstrap.com/components/modal/#multiple-open-modals-not-supported


Minor bug fixes

Fixed type annotation of EnumAttributeProperty and fixed the return value: Return the name instead of the value of the enum.
Fixed a faulty attribute name on PhysicalFunctionPkg: components > functions and passed the correct class for the rootfunction: PhysicalComponent > PhysicalFunction.

I appreciate the effort, but yes, like I said these two commits are already in master. So no need to merge them again. :)


STORM-1546: Adding Read and Write Aggregations for Pacemaker to make it HA compatible

Addressed your comments. Not sure why they have not disappeared.

@d2r @revans2 Any additional comments?

+1

Documentation updated.

Thanks for doc update. +1


5.0.0 cannot derive from Transaction anymore

Just taking a look and found out it constructor now internal. Can it be changing to protected instead so altcoin can implementing outside NBitcoin?

yes, please make a PR.


I followed commands but in If=5 Driver=(None)

I have EC25-E, and i'm trying connect to board via adb. First of all, i cannot see device. I followed your commands but in this time when i write
sudo cat /sys/kernel/debug/usb/devices
I encountered with that
I:* If#= 5 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)

@furkan-kalabalik sorry late reply as I don't look into my GitHub issue page.  For your module, can you show the full /sys/kernel/debug/usb/devices ?
If you are using Standard EC25-E Module, then ADB interface is disabled, thus you can't access it.


PS: my router ip is <IP_ADDRESS> ( and there is no one on my network having this ip)
user is my 'username'
Please help ! 👍

Hi,
The error suggests you already have something listening on port 80 on that IP. Are you running a webserver on the server?

hi,
I checked there is nothing listening on port 80, even i changed the ip, same error
thank you for your reply

Have you assigned <IP_ADDRESS> to the machine in question.
Can you please paste the output of the following commands
ip a
netstat -nlpt

okay, thank for the reply again
i did all the steps and everything is working fine, but it is not caching.
my question is :
can we apply this procedure through Virtualbox with ubunto on it? Host pc platform is windows 10.

Okay all good and working, i switched to virtualbox instead of vmWARE workstation.


Passing per request context to callbacks?

Consider the below pseudocode - any ideas re how one might set and then access per request props in the handlers?
The use case for is for things like currentUser, a or a per request db connection object, per request cache, etc.
import { handleRequest } from 'thaler/server';

// Cloudflare worker pseudocode
export default {
  async fetch(request) {
    // build up per request context
    const ctx = {
      // some db that operates over http/ws, such as neon (pg), planetsacle, or clickhouse, etc
      db: initDbCon(),
      currentUser: await parseReqUser(request),
      logger,
    }

    /**
     * Could pass ctx in for this case, when a call is being made from client? To be made available to the callback handlers
     *
     * BUT not sure how we could get ctx to the callback handlers in the SSR case, when no new fetch is involved
     */
    const request = await handleRequest(request, { extra: ctx });
    if (request) {
      // Request was matched
      return request;
    }

    // render and return the app html stream
    return new Response(renderToStream(() => <App />))
  },
};

// Example $loader
const list = loader$(async (_, { extra }) => {
  if (!extra.currentUser) {
    // error out, redirect, etc
  }

  return extra.db.listPosts();
});

Hmmm, good idea. I might add this. This isn't supported currently and a bit tricky to do when server functions are called in the server (since we don't do roundtrips). So for now you might rely on manual dependency injection.


Any plans to add Swift Package Manager support?

Hi, is there any plans to add Swift Package Manager support?

SDK 4.4.1 is now available as a SPM package, use the following repo URL: https://github.com/nutiteq/mobile-sdk-ios-swift-package.git


Commit the initial version of E2E test

Set up the E2E test for CNSI using e2e-framework. Currently, only inspection policies and settings are covered. Will complete all the E2E test cases in the future.

UT is failing, seems like new added test case is triggered.

UT is failing, seems like new added test case is triggered.

Yep. Actually, the E2E tests passed on my KIND env, but it seems like the tests cannot be executed in this unit test GitHub workflow.  We may need a separate workflow for the E2E tests in Github. Will fix this later.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ab34bca). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #131   +/-   ##
=======================================
  Coverage        ?   43.70%
=======================================
  Files           ?       10
  Lines           ?     1167
  Branches        ?        0
=======================================
  Hits            ?      510
  Misses          ?      624
  Partials        ?       33

Flag
Coverage Δ

unittests
43.70% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Vapid authentication

Based on the web-push javascript vapid implementation, I added VAPID authentication, which works on modern Chrome and Firefox browsers.
This fixes #1.

Thank you very much!

Awesome, would you mind releasing a new version to hex.pm?

Just released as 0.2.0, thanks again for the PR!


Squat Training

Measure Squat Training using VB algorithm

Done with https://github.com/cfogrady/VitalWear/commit/a49a156154db4a8f8db1e848ad1954ca58801416
https://github.com/cfogrady/VitalWear/commit/14bc51520598ad0bfaa3b39b6f1c4ec8537461e0
https://github.com/cfogrady/VitalWear/commit/7f2c2fb4380085ae82de9a2d8e0610d67b45593b


Error This relationship field has the following invalid relationships: 6545bee1525dd1edc2e5362a 0

Hello. I get an error on version payloadcms 2.0.15 when I try to save a document
{
    "errors": [
        {
            "name": "ValidationError",
            "data": [
                {
                    "field": "offerId",
                    "message": "This relationship field has the following invalid relationships: 6545bee1525dd1edc2e5362a 0"
                }
            ],
            "message": "The following field is invalid: offerId"
        }
    ]
}

Hey @georgiev-anton - we have fix merged for this. PR is here.
Once we get new release published for Payload, we'll update this plugin with the new version and this will be taken care of.
Thanks for bringing this to our attention!

@georgiev-anton - a new version of Payload has been released since the merge of the fix. So, if you go ahead and update payload to latest, the issue above should be resolved.

thanks)

@PatrikKozak I have faced with the same issue when I apply filterOptions to relationship
{       name: 'table',       label: 'table',       type: 'relationship',       relationTo: 'table',       index: true,       filterOptions: () => ({         parentItem: {           exists: false,         }       }),     },
This works fine either I turn off the plugin or turn off the filterOptions

@PatrikKozak  I have the same problem, the plugin dont work for the last version of payload.

@PatrikKozak
With payload 2.14.0 I have the same issue. When providing filterOptions I cannot save:

Hey @smoglica @Rikhart @NazarBashinskiy @georgiev-anton - thanks for bringing this to my attention!
I was able to get this fixed - in the process we will also be transferring this package to the Payload monorepo.
PRs for this are here:

v2: https://github.com/payloadcms/payload/pull/6044
v3 (beta): https://github.com/payloadcms/payload/pull/6045

We'll get these merged asap.


sd_setImage completion block not returning image some times.

Im using pod 'SDWebImage', '~>3.8'
when I'm loading for first time very thing is fine, images are loading are correctly in collection view, when i keep scrolling the image is missing, Even though the image is in cache, its not giving the image when scrolling .

can you replicate it in the demo project?


Names of relocations used by the overlay system

Currently the relocations have the following names:
R_RISCV_OVL_HI20
R_RISCV_OVL_LO12_I
R_RISCV_OVL32
R_RISCV_OVLPLT_HI20
R_RISCV_OVLPLT_LO12_I
R_RISCV_OVLPLT32

I propose that it might be better to rename the R_RISCV_OVL_* relocations to be R_RISCV_OVLTOK_*. My motive for this is that by using 'OVLTOK' it's a bit clearer that the value being encoded is a token value rather than an address. It also draws a clearer distinction from the OVLPLT relocations which really are addresses to a resident thunk.

Make sense.
I am assigning this to @Craig. We will need to update the HLD as well.
Thanks, Ed

Another question here. Should we remove the 32 from the names of the relocations. If tokens can only be 32-bits then maybe this is unnecessary since it implies the potential existence of a 64-bit relocation?

I've opened a merge request to do this #31

As you mentioned, the 32bit postfix is for highlighting the length of the token; it does not imply it is for 32 machines. The length of the token is a derivative of how many groups we can have in the program and also can give a wider offset to reach far functions in the group.
If we will want to have 48 or 64bit token in the future, it is possible since it is not restricted on the overlay-software-standard.adoc
Bottom line I agree, we should remove the 32 postfixes just because we can have different sizes of tokens in the future, and those will be encapsulated to the same relocation ID

If later it was possible to have different sized tokens then I assume this would be decoupled from the XLEN? If that's the case how would you ensure ABI compatibility across different object files which may disagree about the size of the relocation? That could be achieved by using an attribute or a different ABI
The tools are going to need to know how wide the underlying token is anyway, since they need to generate a load to it. I'm not sure there's a particular need to try and minimize the number of relocations used either.

As explained, the 32bit postfix is for the token size. It is not related to the machine architecture; therefore, it should not be decoupled with XLEN.
The current overlay implementation (per HLD) can only work on 32bit machines.
To support token size other than 32bit, we need more changes in the toolchain + engine. Currently, the HLD is only addressing 32bit tokens.
This means that tools should follow the HLD and only support 32bit tokens.
The generic overlay standard is not inforcing token size and/or implementation. Therefore other targets or other implementations can be with different token size


How to specify the path to a tsconfig.json?

Hi,
I'm trying to use the lib on a TypeScript project using path aliases but it fails immediately on:
Error: cannot find module '~/config'

I have the path defined in my tsconfig.json like so:
{
  "paths": {
    "~/*": ["./*"],
  }
}

It works correctly with esbuild but not with esrun. From taking a quick glance at the source I couldn't see if it was possible to pass a path to a tsconfig.json.

Just ran into this issue... any luck?

@joshhansen https://github.com/rsms/estrella might be work a look.

The tsconfig.json file is actually already used since the library uses esbuild but in order to make package imports work better I had to implement an esbuild plugin that tried to "detect" which path corresponds to a package and mark it as external.
I implemented a better system that should detect common alias paths like "@/", "~/" and "$...".


extend domain to negative m

I encountered a problem in computing complete elliptic integrals for negative values of m while I was working on my PhD project. The function K(m) can be actually computed also for m<0. This is equivalent to the so-called 'imaginary modulus transformation' for this kind of integrals (http://analyticphysics.com/Mathematical Methods/A Miscellany of Elliptic Integrals.htm):
K(-m)=(1/\sqrt(1+m))K(m/m+1)
In this way, K(m) is well-defined for -\infty<m<1.
I simply removed the if condition on 'm<0': the routine computes the correct values of the integral for negative m (I compared it to the mathematica implementation of this function and numerical integration).
I expect the same problem to hold also for the incomplete integral F(\phi,m).

I encountered a problem in computing complete elliptic integrals for negative values of m while I was working on my PhD project. The function K(m) can be actually computed also for m<0. This is equivalent to the so-called 'imaginary modulus transformation' for this kind of integrals (http://analyticphysics.com/Mathematical Methods/A Miscellany of Elliptic Integrals.htm):
K(-m)=(1/\sqrt(1+m))K(m/m+1)
In this way, K(m) is well-defined for -\infty<m<1.
I simply removed the if condition on 'm<0': the routine computes the correct values of the integral for negative m (I compared it to the mathematica implementation of this function and numerical integration).
I expect the same problem to hold also for the incomplete integral F(\phi,m).

Fixes #12

As per the reference (the same one for #12), K(-m)=(1/sqrt(1+m)) K(m/m+1), but that condition/case is not added to the code?
Also, K still remains the same in the code, and only E is changed?

@hamzaelsaawy you are right, I wanted to fix the domain for the function K(m) and I did it for the function E.
The new commit fixes this mistake: K(m) can be computed for negative values of m and the function E was restored. Actually, I expect that all elliptic functions (both first or second order) can be extended to negative domain of their argument (I refer again to the link http://analyticphysics.com/Mathematical Methods/A Miscellany of Elliptic Integrals.htm). I have to check carefully, eventually I will fix the other functions.

I agree, all three integrals should (in most cases) handle negative moduli.
The core algorithms should be able to handle negative (and complex) moduli -- with some edge cases.
For K, 1-m > 0  so m < 1 is all we need.
(This comes from RF(0, 1-m, 1), https://dlmf.nist.gov/19.16. It is more complicated for the incomplete cases though https://dlmf.nist.gov/19.25)

@nolta, did you have any thoughts on this?

Needs tests.

I am also in the need for negative values of m.

I'd still like to have some tests for this, but i'm going to go ahead and merge.


About the detailed user privilege control

 I'm so sorry for my terrible english.
I met some problems when i use the last version portainer :

Do you have the read only user for per docker-service?
When i create service by Linux Terminal.  The portainer can not control the privilege.

Maybe  I think you can depend on the special Labels with the service to control the privilege on the portaienr web.

Do you have the read only user for per docker-service?

Fine-grained access controls are discussed in #1259 (read-only account is related to #69)

When i create service by Linux Terminal. The portainer can not control the privilege.

See https://github.com/portainer/portainer/issues/1257 & https://github.com/portainer/portainer/issues/960


[$500] Asking sign-in again from public room after refresh

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

Action Performed:

Open any public room without any authentication
Login from the prompts shown in the public channel
Complete login and observe you're loggedin
Refresh page and it's asking login again.

Expected Result:
Once after login it shouldn't ask login again.
Actual Result:
Asking login again.
Workaround:
Unknown
Platforms:

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

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

Version Number: v1.3.67-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/115492554/79839c1f-ca6a-434d-b7b0-aedb5c937c8c
https://github.com/Expensify/App/assets/115492554/533b62da-7f7c-4ba7-bf8d-070cc274eeaf
Expensify/Expensify Issue URL:
Issue reported by: @b4s36t4
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693989869553719
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~015c546ad4cf74de6e
Upwork Job ID:<PHONE_NUMBER>343184896
Last Price Increase: 2023-09-11

Proposal
Please re-state the problem that we are trying to solve in this issue.
If the user signs in while viewing an anonymous report, the authentication state is not persisted.
What is the root cause of that problem?
Once the user opens a public room without having been signed in, they are signed in as an anonymous user. This information is retained in Oryx in the session key with authTokenType being anonymousUser, which is not unset when the user signs in. Once the window is refreshed, this value leads the application to incorrectly believe that the stored session belongs to an anonymous user, rather than a signed in user.
What changes do you think we should make in order to solve the problem?
Default authTokenType to null in DEFAULT_ACCOUNT_DATA.
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01ba3da8d6f0466a75

Thanks @parasharrajat - In that case do you recommend closing this or leaving it open but not accepting proposals?

@sophiepintoraetz - Looks like a double assignment so I'm going to remove you so you don't have to worry about this.

Gotcha, thanks @parasharrajat - I'm raising internally now.

Bumped internally again.

@parasharrajat - Can you tell me who the people are that are working on these Onyx changes you mention? I've asked a few times in Slack and no one can point me in the right direction.

Thank you!

@parasharrajat Yes it still re-produceable took a latest pull and tested.

Coming from here, assigning myself. @daordonez11 mentioned that we're still getting the value for authTokenType, so probably we're not clearing out the value from an API command.

Thank you @marcochavezf - I'll follow along but ping me if you need me to do something I'm not doing 🙌

I think this dube of this https://github.com/Expensify/App/issues/26615#issuecomment-1737031211
@marcochavezf you are right. this onyx issue
https://github.com/Expensify/react-native-onyx/pull/333

Hi @pradeepmdk, I saw your comment here, do you know by chance if that also impacts this issue?

@marcochavezf Yes, this is also fixed.. because the root cause same.
https://github.com/Expensify/App/pull/28299
this PR upgrading the onyx. but after upgrading we are facing some crash issues due to some other fix also, in this upgraded version
https://github.com/Expensify/react-native-onyx/pull/329/files.
so maybe they will revert but I am not sure about that part.

@marcochavezf you can verify this one staging now.
https://github.com/Expensify/App/assets/16595846/e7e0452d-1264-4dd8-bd06-28d3de6b0117

@marcochavezf yes, this is fixed now. you can verify this one staging now.
Untitled.mp4

Oh cool, @strepanier03 I think we can then close this one

Sounds good, I'll do that now.


Add crypto to dependencies

The package doesn't contain the needed libraries to actually be used. This fixes that.

Seems that this is due to chrome being garbage and overwriting the crypto dependency. Closing.


Pattern matching error reported by mavdnoise

I'm also getting this problem. this is my second time buying turnips, and I missed them one week. It's also my first week tracking with this app. I've only ever bought and sold on my island.
https://turnipprophet.io?prices=<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.105
Originally posted by @mavdnoise in https://github.com/mikebryant/ac-nh-turnip-prices/issues/145#issuecomment-615951342

@mavdnoise how absolutely certain are you that your Tuesday PM number is accurate and also from your island? If we remove that value from the calculation, it produces a pattern just fine.
https://turnipprophet.io?prices=105.60..<IP_ADDRESS>.<IP_ADDRESS>.105.105
The math suggests that the range for acceptible values on Tuesday PM would have been 53-59, while you reported a here 71.


Step-by-step installation instructions

I want to use DDMathParser in my iOS single view application (using Swift 2.1) and I read your wiki.

DDMathParser is packaged as a Swift framework, and there are several ways to install it:

Add DDMathParser.xcodeproj to your workspace and link MathParser.framework into your app.
Install using Carthage.
Install using CocoaPods.

But I still don't understand which way is the easiest and how to do it.
Can someone explains me step by step please?

Hi Dave!
I see in another issue that you're asking for SPM support as well, so on the wiki installing page there will eventually be: manual install (this issue), Carthage, CocoaPods and SPM.
Do you plan to have a separate wiki subpage (with step-by-step instructions) for each of those installation methods?
I can start by taking a shot at this issue (manual installation), if that's ok?

Hi, Has this been answered someplace?    I can use some help. Thank-you.


New user on CAS gets stuck during first login

Discovered during #1272, we have some strong params issues to resolve due to our interdependence on CanCanCan. The details are in that thread, the most recent point is below:

okay, so I think the issue is that :username isn't being added to the permitted params because the default user can't manage reservations (line 232 of users_controller: permitted_attributes << :username if can? :manage, Reservation)
I also can't accept the TOS because the checkbox is disabled if you can't manage reservations.

Note that I'm making this high priority and sticking it in v5.3.1 - this is because all of our clients use CAS so we need to get a working version for them ASAP for user testing.

Ok, now to address the comment - the issue here is only the :username strong params filtering. Users don't get to accept the Terms of Service during user creation, that only happens during the checkout of their first reservation.
I'm confused about the permissions issue since the default user should be a superuser and therefore should have full access according to CanCanCan (and therefore can? :manage, Reservation should return true). Is the user not logged in yet (so current_user returns nil)? I feel like we have two separate cases that need to be debugged here:

Can a newly-minted superuser log in for the first time using CAS?
Can a patron create a new account and log in using CAS?

The latter case will likely require you to use the Rails console to delete your user account in the database and manually try to re-create it; you can then modify your role in the Rails console if necessary as well. Let me know how that sounds!

No -- you get stuck on the "New User" page, trying to enter information for a user that already exists as created by the seed script. (@user.save fails because the username is the same as the one that is entered in the seed script)

Yes. Tested by making the superuser netid not my netid.

Ok, so it's not a strong params issue. It is, however, very weird, it shouldn't be redirecting you to the "New User" page since the user already exists. Can you see what the chain of redirects is when you log in?

We need a better idea of what's happening in that second redirect - wanna throw some binding.pry's in the CAS login code (it should mostly or all be in ApplicationController) and see what's going on?

You might have to read some of my comments from #2 to trace the Devise login stuff...


Automated backport of #2708: Fix IPsec whack returning exit status 33

Backport of #2708 on release-0.13.
#2708: Fix IPsec whack returning exit status 33
For details on the backport process, see the backport requests page.

This can be release-noted together with the other related IPSec change, https://github.com/submariner-io/submariner/pull/2708.

Release note PR: https://github.com/submariner-io/submariner-website/pull/1041


Fix data written by dictionary_pickler.py

The changes to the return types of DictionaryFactory.get_dictionary() in 63933fc broke the generation of dictionaries using training/dictionary_pickler.py. This commit fixes that again, by undoing the changes to training/dictionary_pickler.py made by 63933fc.

Neat, thanks!


Should [[DisposableResourceStack]] be cleared after dispose?

In 7.5.8 DisposeResources ( disposeCapability, completion ) it loops through [[DisposableResourceStack]] and disposes all of the resources in the stack but I'm not seeing where it might remove those resources or clear the stack. Is there any reason to hold on to them after disposal? If someone is holding on to a DisposableStack after disposal, wouldn't we also want to prevent them from also having to continue to hold on to all of the now disposed resources?
class LongLivedObject {
    #stack = new DisposableStack()
    start() {
      if (this.completed) throw new Error("Completed")
      this.#stack.use(someResource)
      // ...
    }
    stop() {
      // ...
      this.#stack.dispose() // still holding on to someResource?
    }
    get completed() {
      return this.#stack.disposed
    }
}

Hm, that link 404s

Updated link.

Good call - seems like _disposeCapability_.[[DisposableResourceStack]] should be emptied before the final return

A stack can only be disposed once, and the value of the internal slot is not observable. So there's no reason to clear empty it out.

@bakkot is right. However I have seen implementation leaks like this one over and over. It's not specific to this case, but I'm wondering if we should have an editor note to point out the content of the stack is no longer observable after disposal.

Makes sense. I'll close this unless you want to repurpose it for adding a note.

This is a side effect of reusing the same algorithm steps between using/await using and DisposableStack/AsyncDisposableStack. For using/await using, DisposeResources is called just before the environment record is removed, and thus will eventually be GC'd, but a DisposableStack can obviously stick around if there's something holding onto it after dispose() is called. I'm fine with either an explicit spec step to clear out the List, or adding a note.

I am considering adding a note like the one in GeneratorStart indicate that the capability will never be reused, but the step in GeneratorStart is predicated on the [[GeneratorState]] slot being set to completed. A DisposeCapability record doesn't have such a field, so it may actually be better to just set [[DisposableResourceStack]] to an empty List, along with the note.


feat: Enable isReady for debugger for GCF

This PR mainly serve for GCF. The introduced isReady will return a
promise, and to be resolved either

time since last breakpoint fetch is within a heuristic duration.
breakpoint update completed.

@ofrobots @DominicKramer I have comments addressed. PTAL :)


TypeError with example

Describe the bug
Don't build the serverless function
To Reproduce
Implement the example of README.md
Logs
Vercel CLI 21.2.3 dev (beta) — https://vercel.com/feedback
> Ready! Available at http://localhost:8080
> Building now-rust@2.0.0:api/v3/index.rs
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
    at validateString (internal/validators.js:124:11)
    at Object.join (path.js:375:7)
    at Object.build (C:\Users\Desarrollo\AppData\Local\com.vercel.cli\Cache\dev\builders\node_modules\now-rust\dist\index.js:134:33)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async processMessage (C:\Users\Desarrollo\AppData\Roaming\npm\node_modules\vercel\dist\builder-worker.js:39:18) {
  code: 'ERR_INVALID_ARG_TYPE'
}

Environment:

rust: 1.49.0 (e1884a8e3 2020-12-29)
now-rust: 2.0.4

Hello friend, how to solve this problem?


Would you please add icon ahead of markdown file?

Would you please add an icon ahead of markdown in the following version file like some other themes do, for examle below, it may help identify markdown file more efficiently.

Sorry, I do not plan to add icons for .md files currently. All items are marked by a related file tag except for the .md files, thus, the .md file without an icon is itself an icon.


#2103: Curves: Property panel changes

[ ] Implement automatic output of fit function parameters in the property panel
[x] Restructure properties in the property panel by categories
[x] Add capability to control global series options as well as each series option in the property panel
[ ] Show custom labels in the property panel
[x] Add a unique key to the accordion so it can restore the previous state
[x] Add proper tooltips on the properties
[x] Add detectSettings() method which will go through cells initially and tell if there is a custom set property value or not
[x] Implement capability to create stats column properly with the column+series+stat name
[x] Implement capability to create median stats column properly with the column+median+stat name

This issue has been mirrored in Jira: https://reddata.atlassian.net/browse/GROK-16128


Issued date is after the modification date?

Hello @rfcalhau ,
First issued date vs last Modified date.
According to LOV Bot, the modification date is before the first issued date? (April vs May)?
I also suggest to use a date type for dcterms:modified
<http://purl.org/dc/terms/issued> "2023-05-08"^^xsd:date ;
                         <http://purl.org/dc/terms/license> "https://creativecommons.org/licenses/by/4.0/legalcode"^^xsd:anyURI ;
                         <http://purl.org/dc/terms/modified> "2023-04-08"^^xsd:date

Is that correct?
Best,

Thanks a lot.


📃: QR Code and Bar Code Reader

🔴 Title : QR Code and Bar Code Reader
🔴 Tech stack : HTML, CSS, JavaScript, Python, Flask
🔴 Objective : To add feature of scanning QR Code and Bar Code
🔴 Summary : This project introduces a QR code and barcode scanner application using OpenCV and Python. The application can detect and decode QR codes and barcodes from images and video streams, providing a user-friendly interface for scanning.
📸 Screenshots
N/A

✅ Details to Include When Taking the Issue:
Name : Vivek Gazalwar
Participant Role : GSSOC, Hacktoberfest

Happy Contributing! 🚀
Wishing you all the best on your open source journey. Enjoy! 😎

already present in project


preferredDiskBus not applied to persisted disk during volume hot plug

/area instancetype
/sig storage
What happened:
$subject, the generated disk uses the default scsi bus instead of the preferredDiskBus of an associated preference.
There shouldn't be a need to generate a disk device at all when persisting a volume in the VirtualMachine unless --serial is provided. We do however need to generate the disk in the VMI and should apply any associated preferences to the disk before applying defaults.
What you expected to happen:

Preferences should be applied before defaults to any generated disk devices.
No disk device should be persisted to the VirtualMachine unless --serial is provided.

How to reproduce it (as minimally and precisely as possible):
$ ./cluster-up/kubectl.sh patch -n kubevirt kv/kubevirt --type merge -p '{"spec": {"configuration": {"developerConfiguration": {"featureGates": ["HotplugVolumes"]}}}}'

$ ./cluster-up/kubectl.sh kustomize https://github.com/kubevirt/common-instancetypes.git | ./cluster-up/kubectl.sh apply -f -
[..]

$ ./cluster-up/virtctl.sh create vm --instancetype u1.micro --preference cirros --volume-containerdisk name:cirros,src:registry:5000/kubevirt/cirros-container-disk-demo:devel   --name cirros | ./cluster-up/kubectl.sh apply -f -
selecting podman as container runtime
selecting podman as container runtime
virtualmachine.kubevirt.io/cirros created

$ ./cluster-up/kubectl.sh apply -f - <<EOF
apiVersion: cdi.kubevirt.io/v1beta1
kind: DataVolume
metadata:
  name: example-blank-dv
spec:
  source:
    blank: {}
  pvc:
    accessModes:
      - ReadWriteOnce
    resources:
      requests:
        storage: 1Gi
EOF
selecting podman as container runtime
datavolume.cdi.kubevirt.io/example-blank-dv created

$ ./cluster-up/virtctl.sh addvolume cirros --volume-name=example-blank-dv --persist
selecting podman as container runtime
Successfully submitted add volume request to VM cirros for volume example-blank-dv

$ ./cluster-up/kubectl.sh get virtualmachineclusterpreferences/cirros -o json | jq .spec.devices
selecting podman as container runtime
{
  "preferredDiskBus": "virtio",
  "preferredInterfaceModel": "virtio"
}

$ ./cluster-up/kubectl.sh get vms/cirros -o json | jq .spec.template.spec.domain.devices.disks
selecting podman as container runtime
[
  {
    "disk": {
      "bus": "scsi"
    },
    "name": "example-blank-dv",
    "serial": "example-blank-dv"
  }
]

./cluster-up/kubectl.sh get vmis/cirros -o json | jq .spec.domain.devices.disks
selecting podman as container runtime
[
  {
    "disk": {
      "bus": "virtio"
    },
    "name": "cirros"
  },
  {
    "disk": {
      "bus": "scsi"
    },
    "name": "example-blank-dv",
    "serial": "example-blank-dv"
  }
]

Additional context:
Add any other context about the problem here.
Environment:

KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): N/A
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): N/A
Kernel (e.g. uname -a): N/A
Install tools: N/A
Others: N/A

https://kubevirt.io/user-guide/operations/hotplug_volumes/#why-virtio-scsi
https://github.com/kubevirt/kubevirt/blob/421a6a3acb79204f8fab1e46cb061a33a8f6dbd7/pkg/virtctl/vm/add_volume.go#L127-L138
The reasoning for hardcoding the bus to scsi is pretty tenuous IMHO and poorly documented outside of the excellent user-guide (code and the command help output).
I honestly believe that users should have control over this, with the ability to provide a specific bus or have one applied for them by the backend be it from the preference or defaults (which is scsi anyway IIRC).
Even if we disregard the bus the injection of a disk now breaks ordering after a hard reboot and VMI recreation when the initial boot volume doesn't provide a disk in the VirtualMachine:
$ ./cluster-up/kubectl.sh get vms/cirros -o json | jq .spec.template.spec.domain.devices.disks
selecting podman as container runtime
[
  {
    "disk": {
      "bus": "scsi"
    },
    "name": "example-blank-dv",
    "serial": "example-blank-dv"
  }
]

$ ./cluster-up/kubectl.sh get vmis/cirros -o json | jq .spec.domain.devices.disks
selecting podman as container runtime
[
  {
    "disk": {
      "bus": "virtio"
    },
    "name": "cirros"
  },
  {
    "disk": {
      "bus": "scsi"
    },
    "name": "example-blank-dv",
    "serial": "example-blank-dv"
  }
]

$ ./cluster-up/virtctl.sh restart cirros

$ ./cluster-up/kubectl.sh get vmis/cirros -o json | jq .spec.domain.devices.disks
selecting podman as container runtime
[
  {
    "disk": {
      "bus": "scsi"
    },
    "name": "example-blank-dv",
    "serial": "example-blank-dv"
  },
  {
    "disk": {
      "bus": "virtio"
    },
    "name": "cirros"
  }
]


feat(es/testing): Parse test code as a Program instead of a Module

Description:
This PR addresses the issue described in #8713

BREAKING CHANGE:
This will break existing unit tests that use fold_module/visit_module/visit_mut_module if the visitor is intended to work for both modules and scripts, instead of using fold_program/visit_program/visit_mut_program. This will also break existing unit tests if they're testing with input code that gets parsed as a script in parse_program if the visitor expects a module (they will need to update their test! calls to add module as the first argument, or use a function like apply_module_transform)

Related issue (if exists):

Closes #8713

Several swc tests rely on the parsed test code being a module due to their visitors, going to have to fix these. The good news is that this will fix any of these issues for people using parse_script. e.g. some of the simplifier tests fail on scripts but not on modules.

I will probably clean up the internal API a bit because I think it's a bit messy, but essentially how testing works now:

Current test implementations will continue to work, unless the visitor(s) being tested is implemented wrongly. Since parse_program is the default now and not parse_module, any visitors using visit_module instead of visit_program won't work if the parsed AST ends up being a script (because visit_module won't be called, only visit_script will). Visitors should use visit_program if they want to handle both modules and scripts.
Callers can force the test implementation to use parse_module or parse_script instead of parse_program by calling test!(module, ...) and test!(script, ...) respectively.
Some tests need to use test!(module, ...) as mentioned above, since their visitors depend on the code being a module. A good example are the fixture tests in swc_ecma_transforms_module.

Sounds good, thank you!

Not sure what we think of the internal api, test!(module, ...), test!(script, ...), apply_module_transform etc.

@kdy1 can you un-merge? Not finished yet. Forgot to mark as draft

I've pushed my changes (should be good to go now), but I'll need to rebase once you revert the commit.

@levi-nz Done. https://github.com/swc-project/swc/pull/9621


java-test-fixtures plugin corrupts runtime classpath for integration tests

This might be related to #10872. Also see my ramblings in https://discuss.gradle.org/t/resources-included-as-file-and-jar-in-tests/36881/.
Expected Behavior
Adding the java-test-fixtures plugin should not duplicate resources on the classpath.
Current Behavior
The test fails because the resource in src/main/resources is duplicated on the classpath:
URL [jar:file:/home/cotto/IdeaProjects/classpathgradle/build/libs/classpathgradle.jar!/file.txt],
URL [file:/home/cotto/IdeaProjects/classpathgradle/build/resources/main/file.txt]

Context
The java-test-fixtures plugin changes the runtime classpath that is used by integration tests. For regular tests a fix is implemented as documented in #10872, which uses the hardcoded string "test" in https://github.com/gradle/gradle/blob/master/subprojects/plugins/src/main/java/org/gradle/api/plugins/JavaTestFixturesPlugin.java#L84. This might be the cause of the issue.
Steps to Reproduce
https://github.com/C-Otto/classpathgradle

Run ./gradlew build and see that the test passes.
Enable the java-test-fixtures plugin and see that the test fails
Remove the runtimeClasspath += ... line and see that the test passes

Your Environment
https://gradle.com/s/u32yuqhhlcroe

Duplicate of #10898?

My hack:
sourceSets {
    integrationTest {
        compileClasspath += sourceSets.main.output

        // https://github.com/gradle/gradle/issues/13781
        if (!pluginManager.hasPlugin("java-test-fixtures")) {
            runtimeClasspath += sourceSets.main.output
        }
    }
}

My workaround hack:
build.gradle:
evaluationDependsOnChildren()
configure(subprojects.findAll { it.name != 'xxx' }) {
sourceSets {
    integrationTest {
        compileClasspath += sourceSets.main.output
        if (!project.pluginManager.hasPlugin("java-test-fixtures")) {
            runtimeClasspath += sourceSets.main.output
        }
    }
}

sub-project/build.gradle:
plugins {
    id 'java-test-fixtures'
}

Might be related to #11696

Please unstale this. It's a bug, no matter how old it is.

I've just hit this issue in a current project. This definately needs to be adressed, it basically renders the testfixtures-plugin unusable in Projects with integration tests using resources.
In our project liquibase complains about finding the changelog twice, in the jar and the file itself on the classpath and therefore the liquibase excution is unable to run.
> Task :printCPtest
<projectDir>\build\classes\java\test
<projectDir>\build\resources\test
<projectDir>\build\libs\<project>-0.1.1+75-test-fixtures.jar
<projectDir>\build\libs\<project>-0.1.1+75-plain.jar <-------------- problematic entry
<.gradle>caches\modules-2\files-2.1\org.junit.platform\junit-platform-engine\1.8.2\b737de09f19864bd136805c84df7999a142fec29\junit-platform-engine-1.8.2.jar
<.gradle>caches\modules-2\files-2.1\org.junit.platform\junit-platform-commons\1.8.2\32c8b8617c1342376fd5af2053da6410d8866861\junit-platform-commons-1.8.2.jar
<.gradle>caches\modules-2\files-2.1\org.junit.platform\junit-platform-launcher\1.8.2\c334fcee82b81311ab5c426ec2d52d467c8d0b28\junit-platform-launcher-1.8.2.jar
<.gradle>caches\modules-2\files-2.1\org.opentest4j\opentest4j\1.2.0\28c11eb91f9b6d8e200631d46e20a7f407f2a046\opentest4j-1.2.0.jar

Task to get this oputput:
tasks.register('printCP') {
	doFirst {
		sourceSets.main.runtimeClasspath.each { println it }
	}
}

tasks.register('printCPtest') {
	doFirst {
		sourceSets.test.runtimeClasspath.each { println it }
	}
}

tasks.register('printCPxtest') {
	doFirst {
		sourceSets.xtest.runtimeClasspath.each { println it }
	}
}

Our fix is to use the following code in a custom gradle plugin:
DefaultJavaPluginConvention convention = project.getAsDynamicObject().getConvention().getPlugin(DefaultJavaPluginConvention.class)
            ConfigurationContainer configurations = project.getConfigurations()
            SourceSet xtestSourceSet = convention.getSourceSets().named("xtest").get()
            xtestSourceSet.setCompileClasspath(project.getObjects().fileCollection().from(configurations.named("xtestCompileClasspath").get()))
            xtestSourceSet.setRuntimeClasspath(project.getObjects().fileCollection().from(xtestSourceSet.getOutput(), configurations.named("xtestRuntimeClasspath").get()))

Basically this has to be done for every configuration besides "test", since that is already covered by the code in #10872


onExit is automatically firing

Describe the bug
I'm using intro.js wrapper for React js in functional components. I'm was debug the component and every time my component renders the onExit callback automatically fired by the library.
To Reproduce
This should be like onChange event or onComplete event, when someone interact with the exit/skip button the event should be call at that time.
Expected behavior
I think this should be resolved in next PR
How often does this bug happen?
Every time
System Info
OS: Windows (10)
Browser: Chrome
Version 108.0.5359.125 (Official Build) (64-bit)
Additional Context
I created a codesandbox with the behavior of library, you can check the code and add your valuable thoughts in it.

To understand the issue, you can add a log to your useMount hook:
useMount(() => {
    console.log("> useMount");

    setdata({ ...data, run: true });
});

The console would log > useMount two times.
This behavior is due to your usage of <StrictMode> in your index.js file that enables the following check:

Your components will re-render an extra time to find bugs caused by impure rendering.

To test this, you can remove the <StrictMode> wrapping your application in index.js to see the console logs only 1 time > useMount and 0 times the log in the onExit event handler.
Note that all of these checks are development-only and do not impact the production build.

Dear @HiDeoo, As we know that React. StrictMode is a tool that highlights potential issues in a programme that may occurs in future or by any other chance. Is there any other way that is more proficient and stable? I've to call API's to store the record on db level.

Dear @HiDeoo, As we know that React. StrictMode is a tool that highlights potential issues in a programme that may occurs in future or by any other chance. Is there any other way that is more proficient and stable? I've to call API's to store the record on db level.

Your API call will only be fired twice in development mode so that may not even be an issue. If your call is affecting the state, you can check the new documentation regarding handling effects firing twice in development which describe a way to avoid having the second call in development affecting the state a second time.

@HiDeoo , can you please elaborate why onExit is triggered when onComplete callback is called + vice versa?

This is the default behavior of intro.js and intro.js-react is not doing anything fancy regarding these callbacks. You can check my comment here to get more details and a workaround provided by intro.js-react to figure out if the tour is complete or not when using only this callback.

@HiDeoo, First of all thank you for your fast and effective response, I'm facing another issue with the library regarding import  attaching the warring that is triggered in the console.

import "intro.js/introjs.css";
node_module

package.json
    "intro.js": "^6.0.0",
    "intro.js-react": "^0.7.1",

Looks like the issue is related to intro.js from the error message that some other people are still encountering.

do we need to install intro.js in react.js project for intro.js-react or intro.js-react is an independent from intro.js? like do we need to install intro.js or not?

do we need to install intro.js in react.js project for intro.js-react or intro.js-react is an independent from intro.js? like do we need to install intro.js or not?

This is specified in the installation instructions:

Make sure to have React & Intro.js installed (they're peer dependencies) and the Intro.js CSS definitions properly loaded into your project.

@HiDeoo, Thank you for your time and knowledge. I got my all queries resolved.


Questions about InstagramConstants

Hello, recently, my bot is blocked by Instagram without I change his behavior, but my account isn't blocked on my Android APK.
I would like to know if the problem could be that every people here use the same configuration (DEVICE_MANUFACTURER, DEVICE_MODEL, DEVICE_EXPERIMENTS, USER_AGENT....) and so with time, Instagram begin to identify our Bots thanks this datas?
We use an old android version and an old instagram version.. do you think that could be one of the reasons?
One more thing, could we change/customize easily these datas or it's difficult and/or dangerous?
If someone could explain or has infos about that?
Thanks for your time :)

Addressed in rewrite or no longer relevant.


update the artifacts version of the solution template.

@LGDoor,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


about vulkano_shaders macro question

I am a beginner:
When I want to use custom variables to control the Vulkan_shaders Macro:

example:
let type = String::from("vertex");
create_shader_macro!(shader, type, "xxxx.glsl");
rust cannot expand variables in macro
How do, thanks!

This isn't possible because of how macros work. Macros are expanded at the time that the program is compiled, whereas variables only get their value when the program is actually run.

This isn't possible because of how macros work. Macros are expanded at the time that the program is compiled, whereas variables only get their value when the program is actually run.

Thanks, from the compiler's perspective, it is true that.
Lisp(Macros) and Javascript(Meta Programming) can do this.
However, since all codes are generated from code, there will always be better design patterns, but I have not found them yet.


Noetic Fixes

Fixes the IMU rate to 500 and topic to be in the robot namespace for Spirit
This fixes the build issue when using multi-threaded builds for newer Ipopt (closes https://github.com/robomechanics/quad-sdk/issues/335)
Includes teleop_twist_keyboard to mirror the inclusion (I couldn't install the one from ROS on my 20.04 ubuntu machine it seems).

@ologandavid @selvingarciag96 can you review this PR and try the branch on noetic?

@ardalantj Planning stack and preliminary tests seem to be in order. Just needs a code review on your end.


deps: update deprecated

Fixes #1360
This PR is to update the glob dependency, which is used both in the build process and in the lib/fs.ts module in the apparently unused glob method.
The library's API has changed, so where its called has been refactored.
This fixes introducing deprecated subdependencies to projects that use houdini.
It also replaces directly deprecated dependencies, installed with this project (but not depending projects).
The build completes successfully. This commit does not affect graphql functionality, only build processes.

I updated this PR to fix also some internal deprecated dependencies. However, the majority of them require upgrading: vite 5, svelte 4, sveltekit, typescript 5, prettier 3 and a few others (which seems wise, and soon required). However, this change requires modifying a bunch of files (mainly because of the new NodeNext moduleresolution requiring relative imports to end in '.js'.
Since upgrading these core libraries makes no sense without the changes in this PR, it makes sense to wait until it's approved/processed.
I have still not managed to get the TS5 build working (typedef errors), but have uploaded the progress in https://github.com/rgon/houdini/tree/deps-upgrade-ts5

I think we'll leave upgrading the dependencies for the Houdini 2.0 release.
I have tried upgrading to Svelte 4 before, but got stuck on some peer dependencies that I wasn't able to fix. Since Houdini 2.0 will also upgrade to Svelte 5, I figure it's not too big of a deal to leave Svelte on v3 for now...

@SeppahBaws Then, I don't mind you closing this PR. Should I open a separate one to track the WIP of Svelte 4, TS5 & larger updates (I have made an attempt at rgon:deps-upgrade-ts5)? Upgrading to Svelte 5 will require all of these build-process changes anyways, which are quite a bit of effort. Other than that, Svelte 4 should not break anything else, and should be a smart middle ground not to break everything at once.
I seem to have fixed those peer dependency issues, but am having trouble with the DTS build.


Box Reboot Does Not Create Event

When a box is rebooted, no event is created in the event log (and hence no triggers fire). Here is the menu option used to reboot:

Observing the AP being rebooted, the actual reboot does occur as requested, but no corresponding log event is seen.

Moving to our internal backend section.

Added this to next build, will be cooked later this evening :)

If you find another other triggers missing, please let us know.

Will do - I've been having fun with Slack triggers and seeing what
emoticons etc. I can put in for various triggers.
On 21 June 2016 at 20:41, Simon (Big Chief) Morley<EMAIL_ADDRESS>
wrote:

If you find another other triggers missing, please let us know.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cucumber-tony/cucumber-frontend/issues/96#issuecomment-227549185,
or mute the thread
https://github.com/notifications/unsubscribe/AS5npNLs-CcQtpMzkwcAVXOlOueifCUzks5qOD5vgaJpZM4I69yF
.

Sorting the trigger formatting is next on the list. Think we have most events covered - open to other suggestions.
Going to implement the cpu / client alert when we're past the milestone.

Here are my triggers for Slack so far. Feel free to plunder or ignore as
you see fit :)
Network config update:
:pencil: The configuration of the network {{Ssid}} was updated at
location: {{Location_Name}} (Update made at by {{Username}})
Box down:
:bell: Box {{Description}} in location {{Location_Name}} has gone
off-line (last contact was at {{Last_Heartbeat}})
Box Up:
:no_bell: Box {{Description}} in location {{Location_Name}} has come
back on-line
Box reset:
:boom: Box {{Description}} in location {{Location_Name}} has been reset
by {{Username}}
Box resync:
:left_right_arrow: Box {{Description}} in location {{Location_Name}}
has been re-synced by {{Username}}
On 21 June 2016 at 21:01, Simon (Big Chief) Morley<EMAIL_ADDRESS>
wrote:

Sorting the trigger formatting is next on the list. Think we have most
events covered - open to other suggestions.
Going to implement the cpu / client alert when we're past the milestone.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cucumber-tony/cucumber-frontend/issues/96#issuecomment-227554476,
or mute the thread
https://github.com/notifications/unsubscribe/AS5npHa-hgjF8wx9x_D1cSP7z6xwIJDbks5qOEMpgaJpZM4I69yF
.

The box reboot event now creates a log entry, but the description field is
blank so that there is no message field in the event summary:
[image: Inline images 1]
[image: Inline images 2]
On 22 June 2016 at 00:56, Simon (Big Chief) Morley<EMAIL_ADDRESS>
wrote:

Closed #96 https://github.com/cucumber-tony/cucumber-frontend/issues/96.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cucumber-tony/cucumber-frontend/issues/96#event-699822905,
or mute the thread
https://github.com/notifications/unsubscribe/AS5npN7kROa5Y5FkxwISuOHnbneDZsEMks5qOHoigaJpZM4I69yF
.

One of the workers still has to catch up, should be deployed later today.


Add SysDig monitoring to the following OCP namespace

Add SysDig monitoring to the following OCP namespaces:
e79518 - Digital Trust Services Trust Over IP
a99fd4 - Digital Trust Demo Apps
ca7f8f - Digital Trust Monitoring Services

@rajpalc7, Why is this ticket on this project?  I believe this ticket was tracking the work; https://github.com/bcgov/DITP-DevOps/issues/47


QAQC: Medians

Medians
mdage

e: all match
m: some mismatch for certain NTA and tracts

mdefftwrk

e: mostly match, large mismatch for the following

m:

large differences mostly for certain tracts but not for NTAs
does this make sense? because NTAs are aggregated from tracts, if tracts MOE are not matching, why would NTA MOE match?

mdhhinc

e: mostly match, a small numbers of mismatches (difference within 2)
m: only 1 large mismatch

mdfaminc

e: large difference for 3 tracts (but the NTA containing these blocks are ok)

m:

BX0991 =<PHONE_NUMBER>0
36081019901 > QN02, and QN02 MOE is fine


email_mirror.py: Israel encoding iso-8859-8-i

An E-Mail with Israel encoding part gets stuck in the E-Mail gateway:
File "/home/zulip/deployments/2022-04-02-06-21-17/zerver/lib/email_mirror.py", line 244, in get_message_part_by_type
    return content.decode(charsets[idx], errors="ignore")
LookupError: unknown encoding: iso-8859-8-i

see also
https://github.com/zulip/zulip/issues/2328

Hi @sutidor, I'd like to work on this issue. Can you please add a  label?

Hi @anniechnn , could you please describe your proposed approach for solving this issue?

@alya, I can't add labels, only maintainers can. Would you please?

Related discussion on CZO: https://chat.zulip.org/#narrow/stream/31-production-help/topic/email_mirror.2Epy.3A.20Israel.20encoding.20iso-8859-8-i.20.2323188/near/1448522

With that context, I'm marking this issue as "help wanted". However, folks should still keep in mind the following guideline from the Zulip contributor guide:

Before you claim an issue, you should be confident that you will be able to tackle it effectively.


#255 improvement - Fixed issue with type:file

Fixes issue with type: file and also adds test for mentioned failing case, but it seems to be working
Contributing to Twilio

All third party contributors acknowledge that any contributions they provide will be made under the same open source license that the open source project is provided under.

[x] I acknowledge that all my contributions will be made under the project's license.

I'm not really sure how type: string format: binary should be handled...i patched it up to work for the person asking in #255 but i think we should open different issue on how to handle binary data properly

Thanks again for the discussion!


add option to disable fallback

Fixes #116
One thing that I don't like about this is that BCP is not retried.

Why it is not retried?

Thanks @MiroCillik .  ugh

Adding a simple test that the PDO fallback didn't happen shouldn't be too hard.
There are 2 new tests there that do exactly this, did you miss them?

lol, sorry miro!     Pushed now, thanks

Adding this option has nothing to do with retries or?

Well, there's no retry wrapper on the BCP, it retries the fallback if that fails.  Not sure if it should maybe be for another issue/PR though.  Curious to @tomasfejfar thoughts.

I think we really need to cleanup the "main loop" first - extract and isolate the BCP and PDO into their own classes or at least methods. BCP has it's own class, but only for the extraction itself. There is ton of other code in the try/catch block still.
I may try to do it, if you want...

@pivnicek lol, I just looked at it and thought that I must've been blind yesterday :D
OK it's fine with the tests. Tomas is right about cleaning "the main loop" a little bit.

Yeah @tomasfejfar I agree about the cleanup (give it a go by all means! :) ).  But I think it should be in a different PR.

Certainly in different PR.


fix(Types):Fixed the types of whileElement to be aligned with the documentation …

…and the reality
Description

This pull request addresses the issue described here: #3662

In this pull request, I have removed the unsupported actions from waitFor().whileElement()

For features/enhancements:

[ ] I have added/updated the relevant references in the documentation files.

For API changes:

[ ] I have made the necessary changes in the types index file.

Let's emphasize this on our docs (only scroll is allowed)

Released with Detox 20.21.0.


chore: Improve documentation

What this PR does / why we need it:
Improve documentation by moving development related topics into a new
file called DEVELOPMENT.md. Enhance README.md by adding more information
about the structure of instance types and characteristics of each
series. The description of the GN instance type series is updated to
also mention Kubernetes.
Based on descriptions taken from
https://github.com/fabiand/instanceTypes.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/cc @jcanocan @dominikholler

@jcanocan Updated the PR

/lgtm