ipytree Jupyter Widget not working in notebook editor

The very useful ipytree Jupyter Widget does not function inside the vscode notebook editor.
When clicking on a node in the tree, a model dialog is popped up, which looks like is responding to an attempt to open a editor window that is associated with the node content or some part of the underlying HTML attached to the node.

The same code in a Jupyter Lab web instance functions as expected.
This issue is mentioned in the ipytree Github here
Environment data

VS Code version: 1.68
Jupyter Extension version (available under the Extensions sidebar): v2022.5.1001601848
Python Extension version (available under the Extensions sidebar): v2022.8.0
OS (Windows | Mac | Linux distro) and version: Windows
Python and/or Anaconda version: various, 3.10
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): conda
Jupyter server running: Local

Expected behaviour
Click on ipytree node and UI updates with any attach callback firing
Actual behaviour
Model popup error

Steps to reproduce:
Following instructions on https://github.com/QuantStack/ipytree
conda install -c conda-forge ipytree

run example code eg:
from ipytree import Tree, Node
tree = Tree(stripes=True)
node1 = Node('node1')
tree.add_node(node1)
tree

And then click on the node

This can repro without using ipytree. Just use the example that Don provided.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.68.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!


Build: Protobuf fails with "File already exists in database"

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
source
TensorFlow version
tf 2.13.0
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
3.10
Bazel version
5.1.1
GCC/compiler version
11.3
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
Using the TF_SYSTEMLIBS version of protobuf (i.e. a preinstalled protobuf) when building TensorFlow from source results in
[libprotobuf ERROR /build/protobuf/3.19.4/GCCcore-11.3.0/protobuf-3.19.4/src/google/protobuf/descriptor_database.cc:641] File already exists in database: tensorflow/dtensor/proto/layout.proto
[libprotobuf FATAL /build/protobuf/3.19.4/GCCcore-11.3.0/protobuf-3.19.4/src/google/protobuf/descriptor.cc:2021] CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):
terminate called after throwing an instance of 'google::protobuf::FatalException'
  what():  CHECK failed: GeneratedDatabase()->Add(encoded_file_descriptor, size):

I can't make much sense out of that failure and Google yielded results related to having the protobuf file in loaded in shared libraries multiple times.
All I could do is indeed trace it to from tensorflow.dtensor.proto import layout_pb2 in tensorflow/dtensor/python/layout.py
Standalone code to reproduce the issue
The failing build step invokes `/bin/bash -c 'bazel-out/ppc-opt/bin/tensorflow/create_tensorflow.python_api_tf_python_api_gen_v2 --root_init_template=tensorflow/api_template.__init__.py --apidir=bazel-out/ppc-opt/bin/tensorflow/_api/v2/ --apiname=tensorflow --apiversion=2  --compat_apiversion=1 --compat_apiversion=2  --compat_init_template=tensorflow/compat_template_v1.__init__.py --compat_init_template=tensorflow/compat_template.__init__.py --packages=tensorflow.python,tensorflow.dtensor.python.accelerator_util,tensorflow.dtensor.python.api,tensorflow.dtensor.python.config,tensorflow.dtensor.python.d_checkpoint,tensorflow.dtensor.python.d_variable,tensorflow.dtensor.python.input_util,tensorflow.dtensor.python.layout,tensorflow.dtensor.python.mesh_util,tensorflow.dtensor.python.tpu_util,tensorflow.dtensor.python.save_restore,tensorflow.lite.python.analyzer,tensorflow.lite.python.lite,tensorflow.lite.python.authoring.authoring,tensorflow.python.modules_with_exports --output_package=tensorflow._api.v2 --use_relative_imports=True --loading=default bazel-out/ppc-opt/bin/tensorflow/tf_python_api_gen_v2.params'`

Relevant log output
# Configuration: 020ca55738349851eb8a5a672fc7b8d08dc15ebd99b324f52fddbad2f32820b8
# Execution platform: @local_execution_config_platform//:platform
ERROR: /build/TensorFlow/tensorflow-2.13.0/tensorflow/BUILD:1646:19: Action tensorflow/_api/v2/v2.py failed: (Aborted): bash failed: error executing command
  (cd /build/TensorFlow/bazel-root/663b1bf019e1a9ec9827eae691fce071/execroot/org_tensorflow && \
  exec env - \
    CPATH=/sw/installed/cURL/7.83.0-GCCcore-11.3.0/include:/software/double-conversion/3.2.0-GCCcore-11.3.0/include:/software/flatbuffers/2.0.7-GCCcore-11.3.0/include:/sw/installed/giflib/5.2.1-GCCcore-11.3.0/include:/sw/installed/hwloc/2.7.1-GCCcore-11.3.0/include:/sw/installed/ICU/71.1-GCCcore-11.3.0/include:/software/JsonCpp/1.9.5-GCCcore-11.3.0/include:/sw/installed/libjpeg-turbo/2.1.3-GCCcore-11.3.0/include:/sw/installed/libpng/1.6.37-GCCcore-11.3.0/include:/software/nsync/1.25.0-GCCcore-11.3.0/include:/software/protobuf/3.19.4-GCCcore-11.3.0/include:/sw/installed/pybind11/2.9.2-GCCcore-11.3.0/include:/software/snappy/1.1.9-GCCcore-11.3.0/include:/sw/installed/SQLite/3.38.3-GCCcore-11.3.0/include:/sw/installed/zlib/1.2.12-GCCcore-11.3.0/include:/sw/installed/OpenSSL/1.1/include \
    LD_LIBRARY_PATH=/software/RE2/2022-06-01-GCCcore-11.3.0/lib:/software/snappy/1.1.9-GCCcore-11.3.0/lib:/sw/installed/libpng/1.6.37-GCCcore-11.3.0/lib:/software/nsync/1.25.0-GCCcore-11.3.0/lib:/sw/installed/libjpeg-turbo/2.1.3-GCCcore-11.3.0/lib:/software/JsonCpp/1.9.5-GCCcore-11.3.0/lib:/sw/installed/ICU/71.1-GCCcore-11.3.0/lib:/sw/installed/giflib/5.2.1-GCCcore-11.3.0/lib:/software/flatbuffers/2.0.7-GCCcore-11.3.0/lib:/software/double-conversion/3.2.0-GCCcore-11.3.0/lib:/sw/installed/HDF5/1.12.2-gompi-2022a/lib:/sw/installed/Szip/2.1.1-GCCcore-11.3.0/lib:/sw/installed/SciPy-bundle/2022.05-foss-2022a/lib/python3.10/site-packages/numpy/core/lib:/sw/installed/ScaLAPACK/2.2.0-gompi-2022a-fb/lib:/sw/installed/FFTW.MPI/3.3.10-gompi-2022a/lib:/sw/installed/FFTW/3.3.10-GCC-11.3.0/lib:/sw/installed/FlexiBLAS/3.2.0-GCC-11.3.0/lib:/sw/installed/OpenBLAS/0.3.20-GCC-11.3.0/lib:/sw/installed/OpenMPI/4.1.4-GCC-11.3.0/lib:/sw/installed/UCC/1.0.0-GCCcore-11.3.0/lib:/sw/installed/PMIx/4.1.2-GCCcore-11.3.0/lib:/sw/installed/libfabric/1.15.1-GCCcore-11.3.0/lib:/sw/installed/UCX/1.12.1-GCCcore-11.3.0/lib:/sw/installed/libevent/2.1.12-GCCcore-11.3.0/lib:/sw/installed/hwloc/2.7.1-GCCcore-11.3.0/lib:/sw/installed/libpciaccess/0.16-GCCcore-11.3.0/lib:/sw/installed/numactl/2.0.14-GCCcore-11.3.0/lib:/sw/installed/Python/3.10.4-GCCcore-11.3.0/lib:/sw/installed/libffi/3.4.2-GCCcore-11.3.0/lib64:/sw/installed/GMP/6.2.1-GCCcore-11.3.0/lib:/sw/installed/SQLite/3.38.3-GCCcore-11.3.0/lib:/sw/installed/Tcl/8.6.12-GCCcore-11.3.0/lib:/sw/installed/bzip2/1.0.8-GCCcore-11.3.0/lib:/sw/installed/binutils/2.38-GCCcore-11.3.0/lib:/sw/installed/DB/18.1.40-GCCcore-11.3.0/lib:/sw/installed/libreadline/8.1.2-GCCcore-11.3.0/lib:/sw/installed/gettext/0.21-GCCcore-11.3.0/lib:/sw/installed/ncurses/6.3-GCCcore-11.3.0/lib:/sw/installed/libxml2/2.9.13-GCCcore-11.3.0/lib:/sw/installed/XZ/5.2.5-GCCcore-11.3.0/lib:/sw/installed/expat/2.4.8-GCCcore-11.3.0/lib:/sw/installed/cURL/7.83.0-GCCcore-11.3.0/lib:/sw/installed/OpenSSL/1.1/lib:/sw/installed/zlib/1.2.12-GCCcore-11.3.0/lib:/software/protobuf/3.19.4-GCCcore-11.3.0/lib:/sw/installed/Java/11.0.6-ppc64le/lib:/sw/installed/GCCcore/11.3.0/lib64:/usr/local/cuda/lib64 \
    LIBRARY_PATH=/sw/installed/cURL/7.83.0-GCCcore-11.3.0/lib:/software/double-conversion/3.2.0-GCCcore-11.3.0/lib:/software/flatbuffers/2.0.7-GCCcore-11.3.0/lib:/sw/installed/giflib/5.2.1-GCCcore-11.3.0/lib:/sw/installed/hwloc/2.7.1-GCCcore-11.3.0/lib:/sw/installed/ICU/71.1-GCCcore-11.3.0/lib:/software/JsonCpp/1.9.5-GCCcore-11.3.0/lib:/sw/installed/libjpeg-turbo/2.1.3-GCCcore-11.3.0/lib:/sw/installed/libpng/1.6.37-GCCcore-11.3.0/lib:/software/nsync/1.25.0-GCCcore-11.3.0/lib:/software/protobuf/3.19.4-GCCcore-11.3.0/lib:/sw/installed/pybind11/2.9.2-GCCcore-11.3.0/lib:/software/snappy/1.1.9-GCCcore-11.3.0/lib:/sw/installed/SQLite/3.38.3-GCCcore-11.3.0/lib:/sw/installed/zlib/1.2.12-GCCcore-11.3.0/lib:/sw/installed/OpenSSL/1.1/lib \
    PATH=/sw/installed/libpng/1.6.37-GCCcore-11.3.0/bin:/sw/installed/libjpeg-turbo/2.1.3-GCCcore-11.3.0/bin:/sw/installed/NASM/2.15.05-GCCcore-11.3.0/bin:/sw/installed/ICU/71.1-GCCcore-11.3.0/sbin:/sw/installed/ICU/71.1-GCCcore-11.3.0/bin:/sw/installed/giflib/5.2.1-GCCcore-11.3.0/bin:/software/flatbuffers/2.0.7-GCCcore-11.3.0/bin:/software/dill/0.3.6-GCCcore-11.3.0/bin:/sw/installed/HDF5/1.12.2-gompi-2022a/bin:/sw/installed/SciPy-bundle/2022.05-foss-2022a/bin:/sw/installed/FFTW/3.3.10-GCC-11.3.0/bin:/sw/installed/FlexiBLAS/3.2.0-GCC-11.3.0/bin:/sw/installed/OpenMPI/4.1.4-GCC-11.3.0/bin:/sw/installed/UCC/1.0.0-GCCcore-11.3.0/bin:/sw/installed/PMIx/4.1.2-GCCcore-11.3.0/bin:/sw/installed/libfabric/1.15.1-GCCcore-11.3.0/bin:/sw/installed/UCX/1.12.1-GCCcore-11.3.0/bin:/sw/installed/libevent/2.1.12-GCCcore-11.3.0/bin:/sw/installed/hwloc/2.7.1-GCCcore-11.3.0/bin:/sw/installed/numactl/2.0.14-GCCcore-11.3.0/bin:/sw/installed/UnZip/6.0-GCCcore-11.3.0/bin:/sw/installed/pybind11/2.9.2-GCCcore-11.3.0/bin:/sw/installed/Python/3.10.4-GCCcore-11.3.0/bin:/sw/installed/SQLite/3.38.3-GCCcore-11.3.0/bin:/sw/installed/Tcl/8.6.12-GCCcore-11.3.0/bin:/sw/installed/bzip2/1.0.8-GCCcore-11.3.0/bin:/sw/installed/binutils/2.38-GCCcore-11.3.0/bin:/sw/installed/git/2.36.0-GCCcore-11.3.0-nodocs/bin:/sw/installed/Perl/5.34.1-GCCcore-11.3.0/bin:/sw/installed/DB/18.1.40-GCCcore-11.3.0/bin:/sw/installed/gettext/0.21-GCCcore-11.3.0/bin:/sw/installed/ncurses/6.3-GCCcore-11.3.0/bin:/sw/installed/libxml2/2.9.13-GCCcore-11.3.0/bin:/sw/installed/XZ/5.2.5-GCCcore-11.3.0/bin:/sw/installed/expat/2.4.8-GCCcore-11.3.0/bin:/sw/installed/cURL/7.83.0-GCCcore-11.3.0/bin:/sw/installed/OpenSSL/1.1/bin:/software/protobuf/3.19.4-GCCcore-11.3.0/bin:/software/Bazel/5.1.1-GCCcore-11.3.0/bin:/sw/installed/Java/11.0.6-ppc64le:/sw/installed/Java/11.0.6-ppc64le/bin:/sw/installed/GCCcore/11.3.0/bin:/home/s3248973/.local/EasyBuildDev/easybuild-framework:/home/s3248973/.yarn/bin:/home/s3248973/.config/yarn/global/node_modules/.bin:/home/s3248973/.local/bin:/usr/local/cuda/bin:/usr/lib64/qt-3.3/bin:/sw/taurus/tools/slurmtools/default/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/opt/ibutils/bin:/opt/puppetlabs/bin \
    PYTHONNOUSERSITE=1 \
    PYTHONPATH=/software/TensorFlow/2.13.0-foss-2022a/lib/python3.10/site-packages:/software/TensorFlow/2.13.0-foss-2022a/lib/python3.10/site-packages:/software/protobuf-python/3.19.4-GCCcore-11.3.0/lib/python3.10/site-packages:/software/flatbuffers/2.0.7-GCCcore-11.3.0/lib/python3.10/site-packages:/software/dill/0.3.6-GCCcore-11.3.0/lib/python3.10/site-packages:/software/h5py/3.7.0-foss-2022a/lib/python3.10/site-packages:/sw/installed/SciPy-bundle/2022.05-foss-2022a/lib/python3.10/site-packages:/sw/installed/pybind11/2.9.2-GCCcore-11.3.0/lib/python3.10/site-packages:/sw/installed/Python/3.10.4-GCCcore-11.3.0/easybuild/python \
    PYTHON_BIN_PATH=/sw/installed/Python/3.10.4-GCCcore-11.3.0/bin/python \
    PYTHON_LIB_PATH=/software/TensorFlow/2.13.0-foss-2022a/lib/python3.10/site-packages \
    TF2_BEHAVIOR=1 \
    TF_SYSTEM_LIBS=absl_py,astor_archive,astunparse_archive,boringssl,com_google_protobuf,curl,cython,dill_archive,double_conversion,flatbuffers,functools32_archive,gast_archive,gif,hwloc,icu,jsoncpp_git,libjpeg_turbo,nasm,nsync,opt_einsum_archive,org_sqlite,pasta,png,pybind11,six_archive,snappy,tblib_archive,termcolor_archive,typing_extensions_archive,wrapt,zlib \
  /bin/bash -c 'bazel-out/ppc-opt/bin/tensorflow/create_tensorflow.python_api_tf_python_api_gen_v2 --root_init_template=tensorflow/api_template.__init__.py --apidir=bazel-out/ppc-opt/bin/tensorflow/_api/v2/ --apiname=tensorflow --apiversion=2  --compat_apiversion=1 --compat_apiversion=2  --compat_init_template=tensorflow/compat_template_v1.__init__.py --compat_init_template=tensorflow/compat_template.__init__.py --packages=tensorflow.python,tensorflow.dtensor.python.accelerator_util,tensorflow.dtensor.python.api,tensorflow.dtensor.python.config,tensorflow.dtensor.python.d_checkpoint,tensorflow.dtensor.python.d_variable,tensorflow.dtensor.python.input_util,tensorflow.dtensor.python.layout,tensorflow.dtensor.python.mesh_util,tensorflow.dtensor.python.tpu_util,tensorflow.dtensor.python.save_restore,tensorflow.lite.python.analyzer,tensorflow.lite.python.lite,tensorflow.lite.python.authoring.authoring,tensorflow.python.modules_with_exports --output_package=tensorflow._api.v2 --use_relative_imports=True --loading=default bazel-out/ppc-opt/bin/tensorflow/tf_python_api_gen_v2.params')

Hi @Flamefire ,
Could you please confirm the sequence of steps. Tf2.13v supports protobuf >=3.20 versions as per source where as it seems protobuf 3.19v has been installed.

@SuryanarayanaY Thanks for the hint, yes I used protobuf 3.19. However switching to protobuf 3.20.3 (build from source from the Github tag) with python-protobuf 3.20.3 (build from source from the PyPi archive, which seems to be the latest where a Python 3.x protobuf is available) didn't resolve the issue. I still get the same error (except of course the path mentioned contains now "protobuf-3.20.3")

@vam-google , Could you please look into the issue and confirm whether it falls under your scope.


[BUG]: CSI Health monitor for Node missing for CSM PowerFlex in Operator samples

Bug Description
option to enable health monitoring is present in the controller, but not on the node. All drivers except PowerFlex have it defined for both controller and node. This is an option provided in the DN UI, so we need to included it 2.9 samples in operator.
controller:
envs:
# X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from Controller plugin - volume condition.
# Install the 'external-health-monitor' sidecar accordingly.
# Allowed values:
#   true: enable checking of health condition of CSI volumes
#   false: disable checking of health condition of CSI volumes
# Default value: false
- name: X_CSI_HEALTH_MONITOR_ENABLED
value: "false"
History: There was an issue around this a while back in CSM and this option was removed (https://github.com/dell/csm-operator/pull/187/files). However, the original issue was resolved but we never got around to re-adding this flag back.
Logs
N/A
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
N/A
Expected Behavior
Health Monitoring is enabled on node.
CSM Driver(s)
CSI PowerFlex
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
N/A
Operating System
N/A

link: 19037


Wheels: Enable EGL and osmesa in python wheels

Fix https://github.com/f3d-app/f3d/issues/1788

Needs a docker images update


Not swapping nested symbols

Dear Sonburn,
First of all amazing plugin. I think you already provided me with some helpful answers on sketchplugins.com Hope you are able to help me on this bug as well and in the meantime improve your plugin.
I prepared a sketch file and video demonstrating the issue I found.
https://www.dropbox.com/s/ef294ww3y1hyb3y/nested-symbols-issue.zip?dl=0

a symbol from a library if it contains a nested symbol it does not swap
swapped symbols remain in the file as "normal" symbols, and are not cleaned up

possible causes
changeInstanceToSymbol
Does not update the nested symbols
updateOverridesWithObjectIDMap
Does not update ID's of nested symbols
removeFromParent
Changed instances are not removed from the document if they are unused.
Let me know if you need any more input.

@sonburn Any thoughts on this?

@tijmenvangurp, sorry for the delayed response.
If the symbol containing nested symbol(s) is a local symbol, meaning it exists on the Symbols page (or in the document somewhere), then the nested symbol will be swapped with Symbol Swapper.
If the symbol containing nested symbol(s) is a foreign symbol, meaning it exists in a Library, then the local version of symbol actually exists in the foreign symbols object, which I cannot modify.
The only way to achieve the illusion that a nested symbol within a foreign symbol has been swapped would be to simply override the nested symbol with the desired symbol. Despite the fact that this is technically not a swap, it would be complicated as well, as I would need to check to make sure there is not another override already in place for that nested symbol.
I will think on this a bit more though.

Hey @sonburn Thanks for your answer. I think the use case that I have is quite specific. Will let you know if I find an answer on this! I am fine if you close this issue as this is probably not the intent of your plugin.


Integration test update for organization multi meta-attribute filtering

Purpose
$Subject
Approach
Updated the OrganizationManagementSuccessTest test class's testFilterOrganizations method data provider by adding an additional test case to cover scenarios where organizations are filtered by two meta attributes.
Related Issues

https://github.com/wso2/product-is/issues/20688

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/10322557873

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/10322557873
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/10329765070

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/10329765070
Status: success


Retry on dataSource metadata CAS failures where retrying might help.

This retries when the start condition is met but SELECT -> INSERT/UPDATE
fails, which indicates a race. If the start condition isn't met, there
won't be any retrying.
Fixes #3600.

@dclim @pjain1, volunteered you as reviewers :)

👍

👍


"Basic SEMS portal login failed" DSM update?

Hi,
After using this script for several months successfully, since yesterday I get this login error. Only thing I can think of tha5 has changed is a DSM update on my Synology NAS.
In Debug mode I didn't find a clue:

ash-4.3# /bin/php goodwe2pvo.php

array(6) {

  ["hasError"]=>

  bool(false)

  ["code"]=>

  int(0)

  ["msg"]=>

  string(7) "Success"

  ["data"]=>

  array(6) {

    ["uid"]=>

    string(36) "ac826737-1ee6-45b5-b4d7-ef5e428700d2"

    ["timestamp"]=>

    float(1562924506410)

    ["token"]=>

    string(32) "84ac808a7306734bf6610854d25a9910"

    ["client"]=>

    string(3) "ios"

    ["version"]=>

    string(6) "v2.1.0"

    ["language"]=>

    string(2) "en"

  }

  ["components"]=>

  array(4) {

    ["para"]=>

    NULL

    ["langVer"]=>

    int(25)

    ["timeSpan"]=>

    int(0)

    ["api"]=>

    string(45) "http://eu.semsportal.com:82/api/Auth/GetToken"

  }

  ["api"]=>

  string(30) "https://eu.semsportal.com/api/"

}

Basic SEMS portal login failed. Enable debug mode

>

Any suggestions?

Mine was failing also, but I don't think it has anything to do with DSM.  When reviewing the debug output of the gw2pvo call I noticed that the calls were successful, but the script was acting like they failed.  After looking around a little I noticed that GoodWe had changed the response message from "success" to "Success".

DEBUG    {'data': [{'i': 1.1573, 'd': '07/11/2019', 'p': 16.3}, {'i': 1.6614, 'd': '07/12/2019', 'p': 23.4}], 'hasError': False, 'components': {'timeSpan': 0, 'langVer': 25, 'para': None, 'api': 'http://au.semsportal.com:82/api/PowerStationMonitor/GetPowerStationPowerAndIncomeByDay'}, 'msg': 'Success', 'code': 0}

In the gw_api.py file, send function, I changed the check for success to use the python lower() function and after that it worked.

> if data['msg'].lower() == 'success' and data['data'] is not None:
                    return data['data']

Indeed: that was the issue!! Your trick (.lower()) works well. Thanks

I was running this in Centos and hit an error at about the same time and saw this today, turns out it fixed my issue too.  Thanks.

@Steve-Wax thank you!
in the file:  /usr/local/lib/python3.7/dist-packages/gw2pvo/gw_api.py
edit line 128 :  if data['msg'] == 'success' and data['data'] is not None:
to:  if data['msg'].lower() == 'success' and data['data'] is not None:

I've switch to checking data['code'] instead, which should work more reliable (4b97b7a).

I've just released it as a new package:
pip3 install https://github.com/markruys/gw2pvo/releases/download/1.3.1/gw2pvo-1.3.1-py3-none-any.whl


Added functionaly to allow nested supscriptions for scalability.

Allows eventForwarding, and socket connections

So as a load balancer, or what does it do exactly?

Yes sorry I didnt add more details.
But yes, for load balancing.
Just allows a server to forward the events, for example:
Parent echo server - eventForwarder - echo server
|     |      |
child child child echo servers - connect to the parent via socket io client
/  / / / / / /
browser
The parent forwards the event by just sending 'event' to the children, container {message, channel} which is then parsed in the same way.
The config changes:
{
  eventForwarding: false,
  receivingMethods: ['redis', 'socket', 'http'] // to enable disabling of methods
  socket: false // the socket object == {host, opts} (used for connecting to socket io client)
}

Won't be supporting this at this time.


GAH: Possibly rearrange the text so the nine numbered items are across the top 123, 456, 789

Do you understand what I meant when I made this comment?
I was thinking of having the instruction panel read more like
1   4   7
2   5   8
3   6   9
with the letter following below. It was to clean up some white space that was between the numbers and letter but in the latest release that I see that space has been removed as other items have been rearranged.

Latest prototype the text looked good. I think we can close this one


Automatic add/remove to custom Trakt Userlist.

Hello,
It is possible to have separate user lists for tvshows and movies in "Added setting to allow automatic add/remove to custom Trakt Userlist."?
Thanks

Added in 0.0.55.


Fix only specific rules

I have checked the examples and the main page but I haven't found any configuration properties for the diktatFix task. Is it possible to fix only a specific rule, like TRAILING_COMMAS. If it's not available , it would be a really convenient feature.

Nice enhancement for the future

Is there some workaround I can use to just fix a specific rule or are you aware of another fast solution. I have hundreds of TRAILING_COMMA and WRONG_NEWLINES warnings but in between there are also warnings for other rules. It would be a bit cumbersome to disable the other rules temporarily. Any ideas?

Unfortunately, you can do this only with a configuration file diktat-analysis.yml. All rules are enabled by the default, but you can simply mark them as false from true by one replacement in this file.

Alright then I will go this way for now. Thanks

https://github.com/saveourtool/diktat/issues/1274
Will be selective in the plugin for IDEA


Allow a DomParticle to request focus for an element.

Sample use case: in miniblog, user clicks '+' to create a new post and DetailSlider comes in. The textarea should already be focused else user has to click in it again to begin typing.
@sjmiles if you briefly sketch a design you have in mind I am happy to take a crack at it.

@yuinchien this is the issue I mentioned today. This will affect mobile as well since when user presses '+' the keyboard won't appear immediately. The user will have to click again to bring it up.

This would not block the rock.

@sjmiles has a draft PR that supports focus for posts, ref. https://github.com/sjmiles/arcs/commit/574ff5b58dceee3ea7a17a48b86f9a9a2ea2262e


Clean artefacts generated by the tests

Some files are generated by the tests and may end up installed under dist-packages as reported in the Debian BTS.
Please consider either generating these files in a temporary location, or remove them after the assertions are passed.

Fixed in 1.11.8. Thanks for the report!

No problem. Thanks for the prompt fix.
Le 7 mars 2018 09:37, "Nico Schlömer"<EMAIL_ADDRESS>a écrit :
Fixed in 1.11.8. Thanks for the report!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nschloe/meshio/issues/204#issuecomment-371080210, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AB36b0JBw7C45V4VgNXYxpfSo9ORIqMpks5tb6prgaJpZM4SfXtu
.


Basic components of the go program

Need to finish draft for the following:
I) Key concepts:

GOPATH and GOROOT
package statement
import statement
func main
go build
go run

Note:
All drafts should follow following template:
1) Key concepts
2) Potential interview questions (2-5) with answers and explanation
3) A few practice questions (5-10)

Draft for GOPATH and GOROOT completed

Completed draft for:
package statement
import statement
func main
go build
go run


Emma nechamkin/holc patch

@emma-nechamkin - it looks like we're just taking something out of the narwhal score so is it safe to assume no frontend work needed for this at this time?

@emma-nechamkin - it looks like we're just taking something out of the narwhal score so is it safe to assume no frontend work needed for this at this time?

100% yes! just backend rn


Doesn't open folder in iTerm

Starting a few days ago, when I use "Terminal: Open in project folder", iTerm opens up but it isn't focused, and it doesn't run any commands to cd to the project folder.
I'm using the very latest version of this package and iTerm, and my settings are:
{
  "terminal": "iTerm2-v3.sh",
  "parameters": ["--open-in-tab"]
}

This is likely related to #150 but I'm not sure what would cause those issues. Are there any messages in the Sublime Text console?

No messages appear in the console at all when running this command.

Hmmm, that sure is weird. I will look into reproducing the issue within the next week. If I can't reproduce the error, then it's likely we'll revert the PR as it's been causing a bunch of issues on Windows as well =/

I'm unable to reproduce the error on Linux Mint sadly but I hesitant to ditch the env setting as it's quite practical. Instead, I would like to dig a little further into the issue.
@garyking What happens when you run the iTerm2-v3.sh script locally?
# Download Sublime Terminal's iTerm2-v3.sh
wget https://raw.githubusercontent.com/wbond/sublime_terminal/1.16.2/iTerm2-v3.sh

# Enable script as an executable
chmod +x iTerm2-v3.sh

# Run script (maybe run from Terminal so you get fresh start behavior)
./iTerm2-v3.sh --open-in-tab

After the last command I get:
56:136: execution error: iTerm got an error: Can’t get current window. (-1728)

What happens when you run the script without --open-in-tab?

Exact same error. iTerm also still opens.

Weird, this sounds like a problem in the script itself. Can you try debugging it to figure out what's wrong?

So far I've noticed that if iTerm is running, then "Open project in Terminal" opens a new tab in iTerm in the project folder just fine. I'll do some more testing later.

Problem fixed as of the latest iTerm update 3.0.15 released a few days ago.


exclude doc.go from ever being overwritten

We'd like to add at least a package-level doc for many services. To start we'll put these in doc.go files in the package folder. Can we configure autogeneration not to touch or overwrite doc.go files? Thanks.

This issue should be staled now, closing


Refactor interpackage dependencies to minimize client dependency tree

@SuperQ brought up the issue that the prometheus client_golang project uses only a couple of functions from procfs for gathering process data, but the procfs package has dependencies on the xfs and nfs (and recently also iostats) packages, so these subpackages are pulled in to the client's dependency tree even if they are not used.  Ideally, any clients of procfs should only see minimal additions to their dependency tree.
Before looking at possible solutions, I think it's important to note that even with the current dependency tree, the go compiler seems to be smart enough to not actually bring in code from the xfs or nfs packages into the resulting binary if they are not used.
However, if we do decide to remove the dependency from procfs to the xfs and nfs packages, there are a few options.
(1) We could move the XFSStats method into the xfs package (and do something similar with the NFS methods).  However, since XFSStats is currently defined as a method of the FS type, it makes it a little more tricky to decouple it.  Since golang doesn't allow methods to be defined on a struct from another package, we'd have to either change it to a normal function and have a dependency on procfs, or duplicate the FS type and a couple other associated methods in the xfs package.
(2) Another option is to just merge the xfs and nfs packages into procfs.  This doesn't really reduce the client dependencies, but it does make the tree appear smaller and simplifies the procfs packages structure.  This solution would likely also require making the sysfs package dependent on the procfs package to use some of the common data structures and functions.
(3) We could do a larger package reorganization to make each package very small and specific.  We could do something like create a package structure similar to the path structure of the /proc and /sys filesystems.  We would probably also need a set of packages for common data structures which are used by both proc and sys.

Fixed by #136


2.14.1 tagged on wrong commit

Hi,
The newly created Tag 2.14.1 is was created on this commit: https://github.com/RocketChat/Rocket.Chat.Electron/commit/fad346350b7265f6f7b532275f07c45380a76b81
This is the same commit as 2.14.0. Means the archives of the source code on the releases page are identical.

Ouch! Thank you very much, it was fixed.


For example should have a example drive letter

[Enter feedback here]
At https://docs.microsoft.com/en-us/azure/virtual-desktop/create-file-share#configure-ntfs-permissions towards the end it has a for example, but the drive letter is still  . Just need to replace with P: or something.

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

ID: 3b190fd1-42f6-3a90-5931-74b2ccd309c3
Version Independent ID: c4ca3c86-6257-59dd-e5a3-d40d4e0fa83c
Content: Create an Azure Files file share with a domain controller - Azure
Content Source: articles/virtual-desktop/create-file-share.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@lunar87  Thanks for the feedback, we will investigate and update this thread accordingly.

@lunar87 Can you please elaborate on the change you are requesting for the example here:

We will now close this issue. Please help with providing the details when you are ready and tag me in a comment. I will reopen it and we will gladly continue the discussion.

@Karishma-Tiwari-MSFT My feedback go interpreted as HTML.  Where is has an example, it still has "mounted-drive-letter" where it really should have an example drive letter such as "icacls P: /grant john.doe@contoso.com:(M)"


[infra] Upgrade Docsy

Why upgrade Docsy?
The main reason is that the Bootstrap (BS) version used by this repo's Docsy theme (which dates back to 2020!), reached end-of-life last year, and so BS will not be receiving any more upgrades, not even security patches. Also, Docsy has receiving a lot of enhancements and fixes since 2020 -- in particular it no longer has recursive submodule dependencies!
Why this repo?
A number of TAG and other websites share the version of Docsy used in this repo. After discussion with @cjyabraham and @nate-double-u, we agreed that this repo might be a good candidate for exploring the Docsy upgrade. As I mentioned above, the local Docsy files are from Nov 2020, and have custom changes applied on top of that. It would be much better if an official release of Docsy was used instead, and if we moved any customization into repo-specific files (which is the recommended way of using Docsy).
Benefits
If / once the Docsy upgrade happens, this repo might be used to inspire & inform a CNCF website-starter template.
Impact?
My goal is to explore the Docsy upgrade in a way that is the least disruptive as possible, in particular, that the website will continue to auto-publish based on submitted content, and that there will be no other changes to the site's content or appearance[^1].
Comments?
Comment here if you have any questions or concerns. You can also reach out via the CNCF #techdocs channel.
/cc @caniszczyk @cjyabraham @nate-double-u @leonardpahlke
Prep & site rework

[x] #155
[x] #166
[x] #169

Tasks

[x] #160
[ ] ...

Related

https://github.com/cncf/tag-contributor-strategy/issues/402

https://github.com/cncf/tag-contributor-strategy/pull/399

[^1]: No change in appearance to anyone who isn't a fontend designer. Some minor changes in appearance are to be expected, since Bootstrap and FontAwesome have changed since 2020, with impacts on glyphs, font sizes, spacing, etc.

Sounds good to me, thanks!

Looks like this issue is completed ✅, is this correct @chalin? Thanks so much for upgrading the website!

Hi @leonardpahlke - no, this is far from complete. What has been accomplished is to Reintroduce Docsy as a submodule #160, which is an essential first step, but Docsy has not be upgraded yet. Such an upgrade is a nontrivial undertaking given the numerous style and layout overrides that exist. I'm unsure if/when I'll have the time to look into this; it might not be until 24Q2.
As I've mentioned elsewhere, it might be easier to start from the latest Docsy (0.8.0 as of the time of writing) and (re-)create the site style from there. If there are any frontend designers willing to tackle that, I'd be willing to contribute my Docsy knowledge.
/cc @nate-double-u @krook @caniszczyk

Thanks for the insights @chalin !


Bug: Modal buttons in different orders, consistency update

Bug Description:
For consistency:
Cancel buttons should be on top with action on the bottom. if side by side cancel on left and action on right.
This affects share icons. (see screenshots below)
Screenshots (If applicable):

Possible Solution (optional):
Update components related to affected modals, both related to document sharing.

HI @Jared-Krajewski , I would like to work on this issue. Can you assign this to me?

Hey, I want to work on this issue, Can you please assign it to me?

@Jared-Krajewski  Solved with pr #538 , could you help to review? Thank you.


Python JSON-like dictionary return

Feature Request
There are several cases where it be useful to be able to return a Python dictionary that has already passed through the JSON encoders so that it can be easily added to a REST response or similar.
from datetime import datetime
from pydantic import BaseModel
import json

class User(BaseModel):
    id: int
    signup_ts: datetime = datetime.now()

u1 = User(id=1)
u2 = User(id=2)

ret = {"users": [u1.dict(), u2.dict()]}
json.dumps(ret) # Failure due to datetime object

# Potential feature
ret = {"users": [u1.json(as_dict=True), u2.json(as_dict=True)]}
json.dumps(ret)

I do understand the use case for pydantic would be more to have a response that is an entire pydantic object which would recursively serialize itself to JSON correctly, but we have still found several cases where this would be useful. Happy to add this feature ourselves.

Ugly though it is I doubt anything will catch ujson.loads(model.json()).
Since:

Pydantic claims to care about performance, and I doubt we can find a performant and sensible approach here
I suspect (even more than with other things) everyone will want something different in this case.

We should leave it out of pydantic.
But since this is the second independent question about this, maybe we should add a section to documentation?

replaced by #951


Option 2: Fix stdin parsing

This is my second fix https://github.com/NetworkConfiguration/dhcpcd/issues/285. It checks if there was a single "interface" argument passed and if that argument value is -. If such an argument exists, then dhcpcd forcibly waits on stdin. This also removes the unreliable "check if the stdin buffer is full" semantics, which I don't think should break other use cases. Running dhcpcd -U <interface> will work just like it did before, by contacting the network manager[1]. I assume you prefer this fix over the first one I wrote, because that one breaks the "no interface means dump all interfaces" expectation, but I still offered both fixes for you to decide because that documented expectation also appears broken.
[1] this requirement also seems like a bug when the lease file has already been acquired with a --oneshot call, but as long as we have some stable way across releases to parse a lease without the daemon running I guess I don't care strongly if that one of these gets fixed

Aside: Apologies for the flurry of issues filed and multiple PRs for the same issue. I'm currently trying to document what I see as unexpected / broken behavior, and (for now) fix the ones that I see as most important (https://github.com/NetworkConfiguration/dhcpcd/issues/285 and also https://github.com/NetworkConfiguration/dhcpcd/issues/282, which I see now has a PR waiting review: https://github.com/NetworkConfiguration/dhcpcd/pull/284).
A note on dhcpcd adoption plans
The next cloud-init release is expected to include dhcpcd support. if I don't hear a response on how you plan to move forward with https://github.com/NetworkConfiguration/dhcpcd/issues/285, I will probably end up requesting that this patch and also https://github.com/NetworkConfiguration/dhcpcd/pull/284 (I still need to test that one) to be included in Ubuntu, since the upcoming 24.04 release is also expected to drop support for isc-dhclient, and using dhcpcd's --leasedump in cloud-init is much preferable to writing my own.

You'll need to change dhcpcd.8.in as well to document the new requirement for dumping leases needing the - part.
Luckily interface names cannot start with a - so this is a safe change.

Thanks for the review @rsmarples. I'm busy now, but will try to get back to this PR in the next few weeks if possible. Otherwise I plan circle back to this after the next Ubuntu release.

@holmanb Has this made any progress?

@holmanb @perkelix I decided to merge it and and adjust it in 43954779.
It's a good idea.


Fix Accept-Encoding handling to work correctly if only two compression schemes are available

Description
This fixes compression::get_preferred_encoding() to consider all encodings listed in Accept-Encoding header and not only the top one. While at it, I replaced dynamic construction of available encodings on each call by a constant.
Motivation and Context
As things are right now, compression::get_preferred_encoding() only handles the scenarios “one compression scheme enabled” and “all compression schemes enabled” correctly, with the former being handled as a special case. If for example only compression-deflate and compression-gzip features are enabled and the client requests Accept-Encoding: br, gzip, it will return None because Brotli isn’t enabled – yet it should have recognized gzip being enabled.
How Has This Been Tested?
I’ve adjusted the integration tests to explicitly test for the scenario where the top listed encoding isn’t something we support (identity). While at it, I fixed a bug in this test – it failed if only some compression features were enabled but not all.

This should be solved by shadowing the resp variable.

Yes, I’ve already noticed that issue myself and addressed it in #368.


Fix a broken link in the README

Just a quick fix for the easingTypes link in the README. It was pointing to an old bit of code that no longer exists. Updated it to link to your tween-functions project instead.

Thanks!


Old page still visible after removed from build

Describe the bug
I removed a page from my Gatsby app, it is still visible on the deployment url (not using a custom domain)
Expected behavior
The pages available on a deployment should match what's generated by the build.
Additional context
I reloaded on a different browser, cleared the browser cache, force reloaded.
Sample code
I downloaded the build artifacts from the amplify build step, and the page is not in there. This is likely a bug in the deployment step, as I only see updates and skips from the deploy logs, but no "delete" operation.

It might be related to https://github.com/aws-amplify/amplify-console/issues/74

This is an intentional feature within Amplify Console to gracefully handle a number of scenarios, like code splitting as an example, so that new builds don't invalidate cached resources while a user is actively browsing your app. Deleted resources are eventually invalidated and purged after several builds, and will then no longer be accessible from your app's url.

@cslogan-red interesting, I’d like to have more information about this from the console, but for now your comment is helpful. 👍

I am also in hot water because I can't purge files that users have explicitly requested be removed from our platform, we have deleted them in the build but the cache still exists. Is there any short term workaround for this while we find a better solution?

We are using Amplify to deploy our app but received several ChunckLoadErrors. Is this feature of keeping old assets not enabled by default? Is there a way to enable it?


generate url filament.resources instead filament.pages. on custom page

Describe the bug
The route of generateUrl on custom pages is filament.pages
To reproduce
On custom page, I have:
Pages\MyCustom::routeTo('/{record}/test', 'test'),
Then use
Pages\MyCustom::generateUrl() and it's looking for "filament.pages." route but the route is "filament.resources."

Fixed by #524.


install datastax-agent beforehead otherwise set version may not be fulfilled

DataStax Agent package is contained as an open dependency of DSE package, that was installed before, installing latest datastax-agent version. If you have specified an earlier version for that package, even if its a patch one, it would fail. Installing it upfront fixes this.

@dcparker88 How does this looks? It's strange that no one else has suffered from this before.

I haven't been using datastax-agent recently, however I do remember running in to this. I just always let it upgrade the agent. Thanks for this, this is much better :+1:


Improve subscribe/unsubscribe message feed notices

To simplify message feed subscribe/unsubscribe elements, we should:

Remove the "Unsubscribe" and "Subscribe" buttons.
Change the channel name to use a pill, like we have in settings. Clicking on the pill should open the channel card.
Remove the number of subscribers from channel pills (including the ones in settings).
Add more info and functionality to the channel cards:

Add "N subscribers" just below the channel description, styled like the group member count in #32100.
Add a "Subscribe" / "Unsubscribe" option below channel settings (as appropriate), like we have in the ... menu.

Current UI screenshots

![image](https://github.com/user-attachments/assets/c23f4298-e9c2-4b8c-9c7c-e0886f712321)
![image](https://github.com/user-attachments/assets/64456216-e890-4fae-823f-acb4edc83c11)

CZO thread

I wanna work on this issue..  As #32092  is still under review..

I would like to work on this issue.

@zulipbot claim

Can i work on this
The status of my current PR is that some tests are failing for which I am actively seeking help here
Here is the branch I made to work on this commit Link

@zulipbot claim

@zulipbot claim

Hi @userAdityaa, this issue is already assigned—you might have missed it. Please check the guidelines on claiming issues to avoid spending time on issues that are already taken. Thanks!


Add Logging to GoServer

add DataLogging to Server

choose Database (whide column DB)
add accesslogs for server and GQLendpoint

move some configs to DB from config.yml

added logging for server and api

TODO add changing of configs


breaking change

in new 5.8 version SimpleX update themes.

Hey @sineptic,
Thanks a lot for notifying me, as soon as I have a moment, I will check out the new version and updates the themes.

I want try  make it(catppuccin theme). Where I can find guidance? I know only where palette, but where are how to apply it?

Hi @sineptic,
You have a guide on how to apply the themes here: https://github.com/catppuccin/simplex?tab=readme-ov-file#usage
Follow the steps on the Usage section.

I updated the colors to match the new version, thanks for opening the issue @sineptic !

STOP!


Inconsistent behaviour between .ts and .vue imports from referenced project

Vue - Official extension or vue-tsc version
v2.0.24
VSCode version
1.90.2
Vue version
3.4.31
TypeScript version
5.5.2
System Info
No response
Steps to reproduce

See reproduction repository
Open App.web.test.ts
Notice that it can import from ./index, but not from ./App.vue, while they come from the same referenced project tsconfig.app.json

Link to minimal reproduction
https://github.com/PindaPixel/vue-tsconfig-paths
Any additional comments?
I do not know for certain whether it should be able to import App.vue or should not be able to import from ./index, but to me it seems that at the very least it should be consistent between the two.

The issue here is that you only include ['**/*.web.test.ts'] in tsconfig.web.test.json. In the tsconfig that should cover the testing context, you should add all your source files so typescript can actually resolve your types.
Use https://github.com/vuejs/create-vue to create a project with a well-defined base structure.

Check https://www.typescriptlang.org/docs/handbook/project-references.html


Added Keyboard Piano Project

Press key on Keyboard to play sound !!
Kindly Merge the pull Request with hacktoberfest Label

Press key on Keyboard to play sound !! Kindly Merge the pull Request with hacktoberfest Label

please wait for its review.


Search and filters working

https://github.com/BrowseBox/browsebox-web/blob/8d09292c5ed6d350842e1ed2ba5aaedefb99beb0/src/Components/ItemComponents/ShowSearchedAds.js#L24
https://github.com/BrowseBox/browsebox-web/blob/8d09292c5ed6d350842e1ed2ba5aaedefb99beb0/src/Components/ItemComponents/ShowFilteredAds.js#L26
Code factor is taking issue with these bits. Do they need fixed?


Compare ocaml versions

Addresses issue #88.
Now labels value can be written like:
k=v
k<>v
k<v
k<=v
k>v
k>=v

Looks great, thanks!


Seq2C custom options fix

Thanks for being ahead of me Brad in this!
A minor fix from me, to avoid overriding the options in case of presence of normals. This won't affect Marisa's and Sally's case as they use -E for germline, but good to have this fix anyway.

Great catch -- thanks much Vlad.


Configuring LE wildcard cert on EKS w/ Route53 DNS

So I'm having difficulty getting my LE wildcard cert setup on my EKS cluster (was running K8s 0.18, but just upgraded to 0.19). My understanding is I need to do a DNS challenge which I'm trying to get setup and I'm hitting a major roadblock on.  I started by creating the cert-manager namespace and ran the kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.2.0/cert-manager.yaml command to install v1.2 of cert-manager.
That installed successfully so I went on to create an AWS user that has the proper permissions to modify the Route53 config with this configuration.
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "route53:GetChange",
            "Resource": "arn:aws:route53:::change/*"
        },
        {
            "Effect": "Allow",
            "Action": [
                "route53:ChangeResourceRecordSets",
                "route53:ListResourceRecordSets"
            ],
            "Resource": "arn:aws:route53:::hostedzone/*"
        },
        {
            "Effect": "Allow",
            "Action": "route53:ListHostedZonesByName",
            "Resource": "*"
        }
    ]
}

Then I created my secret, ClusterIssuer and Certificate w/ these parameters.
apiVersion: v1
kind: Secret
metadata:
  name: prod-route53-credentials-secret
type: Opaque
stringData:
  secret-token: [aws-user-secret]
---
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
  name: letsencrypt-prod
spec:
  acme:
    email: [my-email]
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    privateKeySecretRef:
      name: letsencrypt-prod
    solvers:
    - selector:
        dnsZones:
          - "example.com"
      dns01:
        route53:
          region: us-east-1
          hostedZoneID: [route53-hosted-zone-id]
          accessKeyID: [aws-user-key-id]
          secretAccessKeySecretRef:
            name: prod-route53-credentials-secret
            key: secret-token
---
apiVersion: cert-manager.io/v1alpha2
kind: Certificate
metadata:
  name: le-crt
spec:
  secretName: tls-secret
  issuerRef:
    kind: ClusterIssuer
    name: letsencrypt-prod
  commonName: example.com
  dnsNames:
    - "example.com"
    - "*.example.com"

I applied that in both the default and cert-manager namespaces to see if one would work.  Everything looks like it created properly, but I'm not seeing the challenge key being added to our DNS, and I'm not seeing the https route on the app work either.  How can I further debug this?
One error I did notice when I run kubectl logs -n cert-manager -f -l app=cert-manager --all-containers is:
reflector.go:127] external/io_k8s_client_go/tools/cache/reflector.go:156: Failed to watch *v1.CertificateRequest: failed to list *v1.CertificateRequest: conversion webhook for cert-manager.io/v1alpha2, Kind=CertificateRequest failed: Post "https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s": x509: certificate signed by unknown authority

Hi @NeuralChris, some users have seen issues on AWS EKS with a custom CNI, could it potentially be that #3645 ?
Otherwise, the flow of what you expect to happen once you have created a Certificate would be that there is another custom resource CertificateRequest created and specifically for ACME there will also be an Order  and Challenge custom resources- for debugging it is probably worth to check the status of each of those -if they have been created- and the Certificate as well.
From that specific error message though it looks like it might have failed before getting that far, but it might have recovered afterwards.

Thanks for the reply @irbekrm!
I'm not sure on the custom CNI (I'm new to AWS and never tried a wildcard cert before).  Are you suggesting I run those lines that removes those validation webhooks?
I tried to run kubectl get CertificateRequest and the same error I posted above showed up: Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=CertificateRequest failed: Post "https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s": x509: certificate signed by unknown authority
When I try to get the Order or Challenge resources, they don't exist.

I went ahead and deleted the two validation web hooks and then deleted the ClusterIssuer and Certificate and recreated them to hopefully reinitiate the request, but I'm getting the same error when trying to get the CertificateRequest.

Are you suggesting I run those lines that removes those validation webhooks?

Sorry, I think that GitHub issue conversation I linked was a bit misleading- I don't think you should delete the webhook 😄  I think the user who raised that issue fixed it by following our docs here, but it looks like your issue might be related to the TLS cert that the webhook presents not being trusted by the Kubernetes API server.

I tried to run kubectl get CertificateRequest and the same error I posted above showed up: Error from server: conversion webhook for cert-manager.io/v1alpha2, Kind=CertificateRequest failed: Post "https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s": x509: certificate signed by unknown authority

It's worth checking the logs of cainjector component and checking that the cert-manager-webhook-ca secret in cert-manager namespace exists and the contents of that. There are some troubleshooting docs specifically for webhook issues on cert-manager website, did you maybe already have a chance to look at those?


⚠ PrivateHD has degraded performance

In e3c196a, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 5360 ms

Resolved: PrivateHD performance has improved in 7c2cedd.


Truncate Text in Right not working

react-native, react and native-base version
react-native: 0.49.3
react: 16.0.0-beta.5
native-base: ^2.3.5
Expected behaviour
I'm trying to truncate text in a Right component in a ListItem. The text should get truncated when it reaches the Body component.
Actual behaviour
The Right component pushes on the Body component and does not get truncated until the text reaches the left most side of the screen.
Steps to reproduce (code snippet or screenshot)

        <ListItem
          icon
          button
          onPress={() => {}}
        >
          <Body>
            <Text>Repeat</Text>
          </Body>
        <Right>
            <Text note numberOfLines={1}>Lorem ipsum dolor sit amet, consectetur ad</Text>
        </Right>
        </ListItem>

Screenshot of emulator/device

Is the bug present in both ios and android or in any one of them?
iOS
Android?

@jarrx  can you try this
<ListItem icon>
  <Left>
    <Text>Repeat</Text>
  </Left>
  <Body>
    <Text note numberOfLines={1}>Lorem ipsum dolor sit amet, consectetur ad</Text>
  </Body>
  <Right>
    <Icon name="arrow-forward" />
  </Right>
</ListItem>

Screenshot

@akhil-geekyants
It worked and after some styling I could make the list item look the same way as it did before, (right title further to the left, main title further to right etc).
A problem with this solution though is that it does not truncate subtitles as expected. It behaves the same way as it did before so I solved this by simply using the same ListItem setup as before when I have subtitles, and this setup when wanting the right title to truncate.
Thanks for the help.


New version: SoftwareOK.Q-Dir version 11.93

Created by 🥟 Dumplings in workflow run #10018.

Log
Updated: 11.91 → 11.93
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
The manifests for the last version 11.91 will be removed. Reason: No installer URL is changed compared with the last state while the version is updated
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)


I have done minor changes in navbar and  contact me button

You Don't have to make changes in the index.html.
just make another file with your username.html and copy the code from index.html to that and then make changes.
Refer to Issue1

Good work. I am merging your PR.
Do give us a star by hitting the star button of this repo!


Support for gpio:close/1 on feature/smp branch

Adds support for both erlang and elixir to stop and free the resources of the gpio port driver on esp32.
Closes issue #277
These changes are made under both the "Apache 2.0" and the "GNU Lesser General
Public License 2.1 or later" license terms (dual license).
SPDX-License-Identifier: Apache-2.0 OR LGPL-2.1-or-later

opened on wrong branch


Reenable go-gossipsub tests

Motivation

Reenable go-gossipsub tests

Description
Closes #178 #183

Codecov Report

Merging #201 (e8f5a8f) into master (78fd9be) will increase coverage by 3.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #201      +/-   ##
==========================================
+ Coverage   73.17%   76.63%   +3.45%
==========================================
  Files           2        2
  Lines        1909     1909
  Branches      110      142      +32
==========================================
+ Hits         1397     1463      +66
+ Misses        512      446      -66

Impacted Files
Coverage Δ

ts/message/rpc.js
76.49% <0.00%> (+3.49%)
:arrow_up:

Continue to review full report at Codecov.

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

go-gossipsub tests are stable, ready for review


Coupling layers

Adds Coupling layers

Codecov Report

Merging #92 (54b4078) into main (4992731) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #92      +/-   ##
==========================================
+ Coverage   98.25%   98.29%   +0.04%
==========================================
  Files           6        6
  Lines         229      235       +6
==========================================
+ Hits          225      231       +6
  Misses          4        4

Flag
Coverage Δ

unittests
98.29% <100.00%> (+0.04%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

tests/test_bijectivetensor.py
98.64% <ø> (ø)

tests/test_bijector.py
100.00% <100.00%> (ø)

tests/test_distribution.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Support training for VideoCLIP lightning module

Summary:
Add training step, validation step, and optimizer to VideoCLIP lightning module so the model can be trained.
Test plan:
In notebook

Codecov Report

Merging #194 (ec775ae) into main (e315f02) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #194   +/-   ##
=======================================
  Coverage   93.02%   93.02%
=======================================
  Files          47       47
  Lines        2812     2812
=======================================
  Hits         2616     2616
  Misses        196      196

Continue to review full report at Codecov.

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

Looks good to me. Do you plan to add any other validation metrics besides loss?

Just added recall logging to both train and validation steps (same as original mugen repo) since i overlooked that originally


Create new section with receiver contract and lifetimes of sender/receiver

Discuss complete life-cycle of an async operation, including the required lifetimes of scheduler, sender, receiver, op state, and queries with relation to each other. Also, address stability requirements.

Discuss complete life-cycle of an async operation, including the required lifetimes of scheduler, sender, receiver, op state, and queries with relation to each other.

calling a completion signal invalidates the stop token.

Completion signal operations cannot be called before start has begun executing.

Also, rename "receiver-protocol" to "async-function-protocol" or something else indicative of the fact that it relates to the interrelated responsibilities of conforming schedulers/senders/receivers/operation states.

The validity of a sender returned by schedule(sched) does not depend on the validity of the scheduler.

Well.. in the sense that the scheduler might be just a handle to something longer-lived, like it is in the Qt adaptation of QThread, sure, the scheduler doesn't need to be kept around, since it's just a separate thin non-owning wrapper. If the work-runner just models scheduler, you likely want to keep the scheduler around. :)

An operation state shall not be moved or copied once start() has begun executing.

I'd rephrase this - the operation state cannot be moved or copied, operation states prevent this by not being copyable or movable.

If the work-runner just models scheduler, you likely want to keep the scheduler around.

I disagree. I don't want generic code to have to worry about keeping the scheduler around after it has requested a scheduler-sender. If the scheduler owns resources, the scheduler-sender would have to share that resource by, e.g. reference counting it. EDIT: The idiomatic way of doing this, however, is to put the resources into a context and make the scheduler be a handle type.

Pardon me, but that's some hot nonsense. Generic code wouldn't have to worry about keeping a scheduler around, because how and from where to get access to a scheduler is non-generic to begin with. But if you want to tell people "you don't need to keep any scheduler around in any of your code once you've gotten a sender from it via 'schedule()', you're going to tell them how to crash their programs. I find it extremely icky to suggest that the scheduler-sender should share resources. If you have a thread pool that models scheduler, of course you're going to keep the thread pool around while it runs work, and you're damn straight not going to share its queues and other resources in the senders it dishes out. That would also then mean that those queues are going to be shared with the operation states that the senders eventually spit out. Such amount of sharing is just barking mad, when to avoid that, all you need to do is keep a thread pool around while it's running work.
In other words, I don't think this model has a guarantee that any object modeling scheduler can just be destroyed after it has given you a sender from schedule(). And that will bother zero users, because many of them want to schedule() again to do more work, they want transfer() other senders to that scheduler, they want to on() work onto that scheduler, they want to repeat_effect_until() on a scheduler. There are boatloads of use scenarios where you will want to keep a scheduler around anyway.

operation states prevent this by not being copyable or movable.

Nowhere is a movable operation state prohibited. One could move one as much as one liked but not after start() is called.
The library-provided ones generally have internal pointers, and so yes, they are immovable.

Right. So generic algorithms that deal with operation states have to accommodate non-movable operation states. No generic code can assume that an opstate  is movable. That makes it an algorithmic requirement, or dare I say it.. ..a part of the concept.

Look at it this way: I could've made QThread a scheduler directly, instead of adding a factory function that returns a scheduler internally pointing to it. If you're going to tell me that the senders produced by such a scheduler need to share ownership of the QThread, I'm going to stop using this model right then and there, because all generic uses work just fine when the senders produced by the QThread-scheduler just point to the QThread, without any reference-counted shared ownership of the QThread in the senders. So please don't retroactively introduce such reference-counting madness, it's not necessary, and has a completely unnecessary cost in both efficiency and in complexity.

I don't think that's what I said. From what you just said, it sounds like you have a scheduler that points to a QThread. No reference counting is needed here.
If your scheduler owns a QThread such that destroying the scheduler invalidates any senders obtained from it, then that is a problem. The QThread should live in a context and the scheduler should refer to it.

Or to explain differently: you're concerned that some generic code would need to hold on to a scheduler unless there's a guarantee that the scheduler doesn't need to be kept around. I'm saying that no generic code needs to do that, and I'm saying that it's harmful to provide a guarantee that the scheduler can just be tossed to the bin. No generic code requires such a guarantee, no sender algorithm needs to destroy a scheduler, so the lifetime of the scheduler is outside the realm of the important bits of this model. But if we shoehorn that lifetime into the model, we suddenly make modeling a scheduler and its senders much harder, without any algorithmic need for it. In other words, your concern is unfounded, whereas the guarantee you suggest brings another concern for me that some code can be written that relies on that guarantee, which leads to unwarranted sharing in places where we don't need it.
To explain it yet differently, there is no algorithms that require that a scheduler can be destroyed once it's done a schedule(). Algorithms that would require it are harmful. This guarantee is unnecessary.

I don't think that's what I said. From what you just said, it sounds like you have a scheduler that points to a QThread. No reference counting is needed here.
If your scheduler owns a QThread such that destroying the scheduler invalidates any senders obtained from it, then that is a problem. The QThread should live in a context and the scheduler should refer to it.

I could write it so that QThread is the scheduler. If you destroy the QThread and you have senders pointing to it still running work, that's a user error, and the model shouldn't perform magical acrobatics to protect against that.
I don't see how the "context", however that is modeled, helps. You're just moving the cheese, saying that the context must outlive the senders. It's no more difficult to have the scheduler outlive the senders. And that bothers none of your generic code.

It's no more difficult to have the scheduler outlive the senders. And that bothers none of your generic code.

There is a big difference. A scheduler is something I pass around by value and copy freely. All copies are equal, meaning they all schedule onto the same context. That's what copy_constructible in the scheduler concept means.
Your QThread is your context. You should have a function to return a scheduler from it.

It's no more difficult to have the scheduler outlive the senders. And that bothers none of your generic code.

There is a big difference. A scheduler is something I pass around by value and copy freely. All copies are equal, meaning they all schedule onto the same context. That's what copy_constructible in the scheduler concept means.
Your QThread is your context. You should have a function to return a scheduler from it.

You can pass schedulers around by value just fine. But that doesn't mean the model guarantees that all schedulers can be destroyed willy-nilly. There's no algorithm in libunifex or P2300 that requires that. That's what I'm objecting to, and we shouldn't provide such a guarantee when nothing needs it. You can simply omit this part in the lifetime description, and that does no particular harm. If you want, you could say that scheduler-senders don't (need to) own their scheduler, nor do they (need to) own their context.

Sigh, I mean, fine, we do want the guarantee that those copies can be destroyed. :) Fine, I guess it's saner the way you described it originally. I suppose it would help if we then explain that there should be a long-lived context that the senders point to, without owning it, and we certainly should never talk about reference-counted ownership in any of this, that was certainly a serious red herring.

So, now that we have cleared my stupid confusion, how about we describe this thus, exact wording to be honed:

There is a platform-specific or program-defined execution context (that is not specified by this section) that schedulers refer (point) to, schedulers do not own that context. The context outlives the schedulers.
Senders produced by a schedule() operation refer (point) to the same context, and don't refer to the scheduler. Therefore the scheduler doesn't need to outlive said senders, and again, the context outlives the senders.
Not all senders refer to a context. For example, a sender produced by just() doesn't refer to an execution context.

I could have a non-normative note that most schedulers point to a context owned elsewhere and that it must outlive its schedulers and the senders obtained from them. That isn't true for e.g. the inline_scheduler.

I think perhaps we could define the concept of "scheduler validity".
A scheduler has handle/reference semantics similar to that of an iterator.
A scheduler can become invalid if the lifetime of the execution resources that it uses ends.
We could then say that a sender produced by calling schedule(sched) and the corresponding operation state produced by calling connect() on that are also invalidated whenever the scheduler used to produce them would be invalidated.
Then we just need to say what things are valid to do with an invalidated scheduler/sender/operation-state.
e.g. do we only allow destruction? or do we want to require that destruction of (some of) these things "happens before" the scheduler is invalidated?

The validity of a sender returned by schedule(sched) does not depend on the validity of the scheduler.

I think here we want to say something like the validity of the sender does not depend on the lifetime of sched - but I think the returned sender would inherit the validity properties of the scheduler. i.e. it's as-if the returned sender held a copy of the scheduler handle.

The validity of an operation state returned by connect(snd, rcv) does not depend on the validity of snd or rcv.

Again, I think we want to say here that the validity of the operation state does not depend on the lifetime of snd and rcv. The operation-state is assumed to decay-copy the passed receiver, and similarly is assumed to decay-copy any state it needs from the sender into the returned operation-state.
The validity of the operation-state will then inherit the validity properties of the sender passed to connect. i.e. if the sender would have become invalid when some other resource was destroyed then the operation-state will also become invalid when that resource is destroyed.
Some senders will be unconditionally valid (i.e. their validity is not tied to the lifetime of some other resource), and some senders will be conditionally valid (e.g. a schedule-sender that holds a reference to a QThread-based context).


buttonWidth  does not work correctly

Hi iBodia,
Please, check if you have enabled allowsButtonsWithDifferentWidth.
// default is NO. Controls whether buttons with different width are allowed. Buttons are resized to have the same size by default.
@property (nonatomic) BOOL allowsButtonsWithDifferentWidth;


Fixes the 'CLAMP' problem in EditorSpinSlider ...

... when arrow keys are pressed up or down.
Fixes #81272
I have only tried Inspertor, I am not sure if the old changes are necessary for something else.
The old version changed the values by 0.001 from time to time.
https://github.com/godotengine/godot/assets/41921395/65962971-c3b8-4374-b03b-9dc596c4bcf3

I already did this in #80551.

ok, I would also like to catch mouse wheel events. e.g. Ctrl + up/down does not work under MacOS, already assigned with the system function Show all windows of the front app. But mainly to increase the usability, if it is possible directly when the mouse is over the input field, without 'input focus'.
Should I wait until 'merge' has been executed? #80551

Would suggest against it. Would lead to a lot of accidental value changes when I try to adjust my inspector view.

Nevermind, this PR works well in all situations, I think it's better than mine actually. So my PR can be closed, though I think my comments can be carried over to improve the clarity of the code.
// Modifiers based on web browsers' DevTools. before the Ctrl/Alt/Shift modifier code.
// If the step is smaller than 1 but can be expressed as a 1/int fraction, then set the change to 1.
// For example, 0.001 is 1/1000, so then the change will be 1.
// Otherwise, for example if the step is 0.4, use that step directly. before the step declaration.

Thanks!


d455 rgb camera not working

|---------------------------------|------------------------------------------- |
| Camera Model                       | { D455 } |
| Firmware Version                   | (<IP_ADDRESS>) |
| Operating System & Version |   {Win 10  |
| Platform                                 | PC  |
| SDK Version                            | 2. 36.0                       |
Issue Description
Upon plugging the realsense d455 in and opening intel realsense viewer, it does not capture the rgb camera. it simply states "frame not detected" and errors out. the depth feed does work though.
the rgb camera is detected and shows frames in the normal windows camera app, but occasionally gives the "can not connect to your camera" error.
Does this mean my camera is defective?

Hi @BryanChrisBrown   RealSense camera hardware faults are extrmely rare.  The problem is more likely to be related to the USB system.
Are you using the official short USB cable supplied with the camera please, or your own choice of cable that is longer?  Also, are the numbers '2.1' present beside the camera name at the top of the RealSense Viewer's options side-panel?  If you have the camera plugged into a USB port, this would indicate that the camera is being mis-identified as being on a USB 2.0 connection, which provides the camera with more limited capabilities than when it is on a USB 3 connection (typically denoted by the vaue '3.2' beside the camera name).
I note that you also receive connection errors when using RGB in the Windows camera app, which also lends weight to it being a USB related issue and not a software one with the RealSense SDK (which would not be used by the Windows camera app)..

Hi Marty,
I am using the included cable, and it is showing up as usb 3.2, here's a screenshot of the realsense viewer.

These are the errors I get when first booting up the realsense viewer with the camera detected

I've also tried using my oculus link optical usb cable, and had the same issue.

Thank you very much for the images.  May I also please confirm that you installed the full RealSense SDK from the Releases page (using the 791 mb **Intel.RealSense.SDK-WIN10-<IP_ADDRESS>4.exe
** installer file) and then launched the RealSense Viewer using the launcher icon for the Viewer that the installation places on the Windows desktop?
https://github.com/IntelRealSense/librealsense/releases/

I am using that version. However I am going to reinstall it just to be sure.
I’m also not sure what this “button” is on the back of the camera

It is a cover for the hardware sync pins that are used to connect multiple cameras together so that their timing can be synchronized.

I get the following set of errors after reinstalling the 2.36.2034 sdk.

SDK 2.36.0 is the appropriate one for the D455, as it is the version where support for the D455 was introduced.  You are also using the most recent firmware.
I received my own D455 this week, so have just unboxed it for the first time to test it with SDK 2.36.0's Viewer.  I tested the RGB with both USB 3 and USB 2 ports and experienced no errors.
I see that in your supplied image you have Stereo, RGB and Motion Module all enabled.   Does RGB still not work if only RGB only is enabled?

it appears that rgb and depth work now (this was not the case the last time I tried), but as soon as I turn on the motion module the realsense viewer fails to refresh the rgb stream.

Enabling the Motion Module after enabling RGB and depth sometimes results in errors.  It is not always clear why this occurs.  It could simply be that a particular computer struggles to have all three stream types active at the same time.
Does the Motion Module generate errors if only it is enabled and RGB and Depth are off (red)?

it currently appears that turning on the motion module causes the rgb camera to no longer process properly.
After turning off the rgb camera and stereo camera, I turned on the motion module, and got the expected result.
however, when I turned the rgb camera back on, it presented me with this screen.

I recalled that I had heard of a similar case recently with the RealSense Viewer where RGB stopped working when the Motion Module was enabled.  Like yourself, that RealSense user also experienced the log error Exception was thrown during user processing callback!  null pointer passed for argument "frame"
They reported that most of the time, they most often had problems when enabling stereo first and then RGB secondly.  There was not a clear solution at the conclusion of that case though.
https://support.intelrealsense.com/hc/en-us/community/posts/360048388253/comments/360012195253

It seems like my problem is solely related to the motion module being enabled. I was able to enable stereo and then rgb successfully

As the D455 is a very new model whose pre-orders have only just shipped, I cannot rule out the possibility that there is a bug in the 2.36.0 RealSense Viewer program that affects the D455 particularly.
It may be worth seeing if the camera can work with the rs-motion example program that was designed for the D435i's IMU.  You can find a pre-made launchable version of the program by going to C: > Program Files (x86) > Intel RealSense SDK 2.0 and launching the file rs-motion
A fast way to get there is to right-click on the Viewer's desktop launch icon and select Open file location from the menu.

I've recorded a video of what happens with rs-motion.
it looks like the imu spins rapidly and then slows down and works properly. It will be available at this link once the video is done processing: https://drive.google.com/file/d/1Jvd_KiEa-nqdyt8ZXQfG36Q5fFF7NxP7/view?usp=sharing

I have not personally tested rs-motion with my D455 yet but the behavior that you describe is typical for the D435i, so it sounds as though the IMU is behaving appropriately outside of the Viewer.

I'll also note that I tried using the viewer with the t265 and the d455 simultaneously, the t265 is plugged into its own dedicated usb 3.1 adapter card. the d455 is plugged in to a dedicated usb c 3.1 port.
after enabling the t265 in the viewer the rgb stream from the d455 camera errored out. If there are any error logs I can provide to help solve these issues please let me know

Thanks for the extra detail.   I am not able to handle T265 related support cases though as somebody else is responsible for those, so it is best to keep the conversation focused on 400 Series cameras models.  :)
The link below explains how to set up logging in the Viewer and set a path for the log to be saved at.
https://github.com/IntelRealSense/librealsense/issues/5851

You have given me an idea though.  If you run the rs-multicam example then it will display a series of stream panels for each camera type attached.  I just tested it successfully with D455.  If it can show panels from both D455 and T265 on the same screen then it would lend further weight to your problem being related to the Viewer program specifically.

librealsense.log

rs-multicam is working properly.

Thanks for the log.   It didn't reveal anything new though, just the previous error generating constantly.
01/08 11:56:39,058 ERROR [15024] (synthetic-stream.cpp:48) Exception was thrown during user processing callback: Error occured during execution of the processing block! See the log for more info
01/08 11:56:39,092 WARNING [15024] (rs.cpp:1089) null pointer passed for argument "frame"

Here's a video of multiple cameras working properly in rs-multicam (2 t265 + 1 d455) definitely seems like it's an issue with the realsense viewer in particular.  https://drive.google.com/file/d/1Hf-qTTa3B1-8dIPBIkL5rWdi9YbkMcyo/view?usp=sharing
Thanks for helping me debug this. I'm glad to know that my camera isn't broken.

Great video, thanks!
It is a difficult situation, as you are clearly experiencing abnormal behavior in the Viewer but until it can be replicated by other D455 users or by RealSense team members then there is not sufficient grounds to report it as a bug.
If you feel experimental then you could try the 2.37.0 test version of the SDK (available from the top of the Releases page by expanding open the 'Assets' link).  Or you could wait and see if other new D455 users report similar effects in the coming week as they try out their pre-order cameras.

same errors with 2.37

Thanks very much for testing it and providing feedback.

@BryanChrisBrown , it is a known bug in v2.36 for the Viewer compiled with BUILD_WITH_OPENVINO flag. You've probably encountered it when running the tool from the Installer as this option is embedded in Win10 distribution package.
To workaround it disable post-processing for the RGB sensor or use the stand-alone Viewer from v2.36 Release.

To reconfirm - the issue is isolated to the Viewer tool and does not affect SDK's functionality.

Case closed due to no further comments received and solution provided.


Replace the usage of web sockets for transmitting regular Tx (no IBC)

Closing as this is being handled by the SDK


[feature request] throwing cotton candy into water makes it despawn instantly

itd be funny to implement the cotton candy disappearing when touching water LMAO

Will definitely consider this lol, for now the mod is abandoned tho


Skip retrieving MSSQL result sets that contain no rows.

Fixes https://github.com/dotnet/interactive/issues/1058
We throw an error from SqlToolsService when trying to retrieve a result set that doesn't have any rows. This change skips that retrieval step when the result set has zero rows, and instead displays a single empty row so that we still get column names in the Nteract data explorer.

@jonsequitur Pushed up my latest changes, so feel free to merge whenever.


Set Specific Time for Dashboard Refresh

Hi there,
I’m currently using the "refresh_frequency" parameter in the JSON Metadata to set my dashboards to refresh every 24 hours. However, I need to know if there’s a way to specify a specific time for the refresh, such as 3 AM.
Is there an existing parameter or method to achieve this? If so, how can I implement it?
Thank you!

@dosu  When I try to set that parameter in my JSON METADATA, I get this error:
Sorry, there was an error saving this dashboard: [object Object]

@dosu if my configuration is:
...
"color_scheme": "",
"refresh_frequency": 86400,
"expanded_slices": {},
"timed_refresh_immune_slices": [],
"cross_filters_enabled": true,
"default_filters": "{}",
...
everything works perfectly. The problem occurs if I change
"refresh_frequency": 86400 to "refresh_frequency": "0 3 * * *"

Sorry, this isn't currently a feature. You can use the Alerts & Reports feature to schedule sending an email or Slack message with the dashboard's content (basically a screenshot) at any given time, but the dashboard refresh rate is currently interval-based. I guess if you want to get up at 3am and refresh it then with a 24 hour rate, you could. Or maybe 9pm with a 6 hour cycle or something ;) If you want to advocate for this as a feature, you can open an Ideas thread here on GitHub Discussions, or if you want to contribute it as a new parameter (e.g. regresh_time), you could open a PR and/or SIP.

@rusackas thank you so so much ;)


Make 'chalk' and 'commander' dependencies optional.

They're not needed if you don't plan to use the CLI.

I released @fregante/relaxed-json if you'd like. It's an exact copy of the package, except its lacks the executable and therefore both dependencies
https://github.com/fregante/relaxed-json#readme


Stationary Medical Cloner and Scanner ejects into a wall even if there is a better option.

Description

This is something that happens more frequently on packed since the main cloning room is tighter quarters.
Screenshots

Additional context

Fixed maybe in #5408.


Correction in the Sample

Code is written in the Sample should be corrected from
IDatabase cache = lazyConnection.Value.GetDatabase();
To
IDatabase cache = lazyConnection.GetDatabase();

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

ID: 91eda09f-d369-1ff4-f458-7374597c9c80
Version Independent ID: fb963d39-68e2-3510-6b0d-5688a5a3bd57
Content: Create an ASP.NET web app with Azure Cache for Redis
Content Source: articles/azure-cache-for-redis/cache-web-app-howto.md
Service: cache
GitHub Login: @yegu-ms
Microsoft Alias: yegu

@hifni Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@yegu-ms Please confirm if we have to create a PR for this.

@hifni Thank you for pointing this out!
@NavtejSaini-MSFT We already fixed this in the doc.
#please-close


TypeError: Cannot read property 'nodeType' of null

https://github.com/Summer-andy/chrome-extensions-searchReplace/commit/222f0a4a6ef6cf3ff6f2b87068a6fad9ea916c16


Metronome IM is missing

Metronome IM is missing:

https://metronome.im/

@Neustradamus  Please add entries by doing PR: https://github.com/bluszcz/awesome-xmpp/blob/master/CONTRIBUTING.md#adding-to-this-list

Added Metronome.


What Are Limitations For Minio

In the main README.md under Compatibility with non-AWS S3 it indicates that support for Minio is limited. Could you specify which features / aspects of Minio are are not supported?
Thanks

I would like to know about it as well.

anyone else has tried it on minio?


fix the issue when init TSDBClient with check_tsdb_alive=True throw a…

…  exception. because self._connect is not define and self.tsdb_urls is not init

@scarchik can you merge this in? Thank you!


MINOR: reduce debug log spam and busy loop during shutdown

While investigating some system test failures I found the Streams logs often got up to several GB in size, with much of it being due to these three lines being logged on repeat many times per ms:
[2021-07-19 11:15:26,880] DEBUG [] Invoking poll on main Consumer
[2021-07-19 11:15:26,880] DEBUG [] Main Consumer poll completed in 0 ms and fetched 0 records
[2021-07-19 11:15:26,880] DEBUG [] Thread state is already PENDING_SHUTDOWN, skipping the run once call

Even though they're debug logs this is just way too much printed way too often, and also reveals how much cpu we're wasting just spinning in this busy loop doing nothing else. It seems the situation was that the thread had been told to shut down but was waiting for an in-progress rebalance to complete before it could exit the poll loop and complete its shutdown. Turns out we were polling with Duration.ZERO in this case and therefore just running through the loop again and again and again within a single millisecond.
So, we should be passing in a larger timeout to poll() when the thread is in PENDING_SHUTDOWN to let it actually wait for the ongoing rebalance to finish. Also threw in a few miscellaneous fixes/cleanups that I came across on the side

call for review @wcarlson5 @lct45 @guozhangwang @vvcephei @cadonna

Only unrelated known/flaky test failures:

ClientUtilsTest.testResolveDnsLookup()
ProduceRequestTest.testSimpleProduceRequest()
ConsumerBounceTest.testCloseDuringRebalance()
ControllerIntegrationTest.testPartitionReassignmentToBrokerWithOfflineLogDir()
TransactionsTest.testSendOffsetsToTransactionTimeout()


Better threading model

I have just added pagination to item pages.
This exposed the fact that we need to improve the threading model to generate queries that bias in favour of top level items instead of recent ones that are also deep in the replies of another item.
We need to load as many as possible top level items, instead of pigeonholeing on a single item and its children just because they are the most recent.
For this I need to add a maximum depth for the path in the postgres query - which I imagine propagates transparently to the ActivityPub api responses without having to do anything extra.

Improved the queries to support a Depth filter in commit 88abb2aaf


codegemma models throwing weird outputs

Hi,
I see a lot of <|file_separator|> and similar sequences in the outputs. Is this something that should be fixed in the application consuming the outputs, or ollama?
$ ollama run codegemma:code
>>> int main()
 {.cpp
<|fim_prefix|>int main(){
int num1,num2,result;
num1=10;
num2=5;
result=num1+num2;
cout<<result;
return <|fim_suffix|><|fim_middle|>0;
}
<|file_separator|>

>>>

Originally posted by @fungiboletus in https://github.com/ollama/ollama/issues/3556#issuecomment-2046727592
Similarly, when using Continue with VSCode, I also see these file_separators being constantly suggested by the tab autocomplete. Not sure if it is fixed on the ollama side or on the continue side.

Hi there, sorry about that. It seems the codegemma model on ollama.com didn't have all the required stop words - that should be fixed now if you re-pull

awesome thank you!


Bump versions for zebrad 1.0.0-alpha.2

Motivation
Release!
Solution
Bumps versions to v1.0.0-alpha.2 for relevant Zebra crates and tower-batch to 0.2.0, which will be tagged by https://github.com/ZcashFoundation/zebra/releases/tag/untagged-bd38ff7699647bcf8339
Review
Anyone from Zebra team

I've checked every instance of the version string in zebra:

zebra* Cargo.tomls

tower-* Cargo.tomls

README.md

zebrad app version

network protocol user agent

[ ]  we've never updated the tower-fallback version, and there was an interface change in July 2020, so let's update it to version 0.2.0

[ ]  zebra-script depends on zebra-chain, which has changed, so zebra-script needs an increment to 1.0.0-alpha.3

[x]  zebra-rpc and zebra-client haven't changed, and have no dependencies, so they don't need an increment

[x]  zebra-utils depends on crates that have changed, so it needs an increment

[x]  all other crates have been changed and need an increment

[x]  the app and network versions are incremented every time the zebrad crate is incremented

[x]  the README.md version is incremented for every tag

This is a complex series of checks, let's turn it into a PR template or another kind of checklist?
I'm happy to do a quick edit to create the checklist, I just need to know where to put it. What do you think is best @dconnolly?
(Eventually we should automate version increments, but that's not scheduled for this sprint, so turning this list into a checklist will help with the version updates for the next few sprints/tags.)
Edit: I also want to add instructions like "look at the zebra GitHub code page, check to see which crates have new commits since the last version update, then deal with dependencies"

A PR template sounds like the correct option yeah, even when we automate a lot of things, there will be a human action that will either trigger the automation or whatever, and it can continue to evolve from PRs using that template. 👍


ci: rename master to main for jobs

Codecov Report

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

:exclamation: Current head 71da0d6 differs from pull request most recent head 74be127. Consider uploading reports for the commit 74be127 to get more accurate results

@@           Coverage Diff           @@
##             main     #340   +/-   ##
=======================================
  Coverage        ?   58.55%
=======================================
  Files           ?       45
  Lines           ?     2560
  Branches        ?      559
=======================================
  Hits            ?     1499
  Misses          ?      926
  Partials        ?      135

Continue to review full report at Codecov.

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


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

@hanz068 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree


View timing of words/phonemes?

The type for ServerMessageResult hints at timing information being available from Vosk for words.
    export interface ServerMessageResult {
    event: "result";
    recognizerId: string;
    result: {
        result: Array<{.      // This is maybe where I could find word timing.
            conf: number;
            start: number;
            end: number;
            word: string;
        }>;
        text: string;
    };
}

...but the message received in the result callback doesn't have a result.result.* value.
Is there some way to get the timing info? I would do wonderful things with it.
Big fan of vosk-web. Thanks, Ciaran!

Self-answering...
Call recognizer.setWords(true). And then the extra information will be populated. I was very excited to see it work.


API: Removes device casting from Dataset

Resolves https://github.com/dnouri/skorch/issues/223.

Removes to_tensor and self.device from Dataset.

torch.utils.data.DataLoader's collate_fn=default_collate function is able to handle our types without needing to covert them to tensors first. During training, validation, or evaluation, NeuralNet.get_loss and NeuralNet.infer will call to_tensor to move data to self.device.

When X and y are yielded from a DataLoader, their numerical values are already converted into tensors. get_loss and infer will call to_tensor with tensor-filled X and y values.  With this in mind, I refactored to_tensor to check the tensor type first and return early.

This PR frees Dataset from worrying about device and allows NeutralNet to handle device transfers. This makes Dataset be inline with datasets in torchvision.datasets, which doesn't involve the GPU when yielding data.

Excellent changes, thank you. My only wish is to add a deprecation warning for the removal of device in Dataset.
@ottonemo pls also have a look.

@thomasjpfan Can you add a deprecation message. Then we can merge this PR.

I updated this PR with a deprecation warning.

Thanks, again, for your excellent contribution.
@ottonemo can you merge?

Thanks again.


Enhancement: Customize margin on side of VN Textbox

Is your feature request related to a problem? Please describe.
On smaller resolutions (like pixel games), the hardcoded margins look a little strange. Sometimes, the text has too much padding around the sides.
Describe the solution you'd like
Add a little input box for how much margin/padding you want.
(By the way, what is the little up arrow and down arrow and number box called?)
Describe alternatives you've considered
Ignoring it. You could workaround with custom textboxes too though.
Additional context
A picture of the padding on the sides.

You can change these by having a custom stylebox (these are defined by the styleboxes content margin)

Do I have to press "make custom" in the UI to do this?


#324 - reworked search locations mechanism. refactoring of code.

I found new endpoint (in code of other projects on github - written in php and python) to obtain location feed correctly. And I've implemented it here in Java. Also I've performed refactoring a little.
Main changes are:

cleaning code of InstagramGetRequest and InstagramPostRequest
new class InstagramContent was created to store plain content of each Instagram server response to provide a possibility to discover them direclty in client code without deep debugging in this framework code.

@brunocvcunha please consider to create a develop branch to accept pull requests only in develop branch, not in master. Second is to cover the code with tests.

Addressed in rewrite or no longer relevant.


Consider auto upgrade bots

🐞 Problem
According to this study, "Projects with automated PRs made 60 percent more of the necessary [dependency] upgrades than projects that didn't" (via this tweet by Nadia Eghbal). Perhaps, instead of (or along with) doing #158, we could include this in poliastro as well.
🎯 Goal
Avoid lagging behind with the dependencies of poliastro, which is a problem that will grow bigger the more dependencies we introduce, and detect problems that happen with recent versions.
💡 Possible solutions
Probably there are some bots out there that do this for you, but some research should be done first.
📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request and add this in comments - Addresses #<put issue number here>
Ask for a review in comments section of pull request
Celebrate your contribution to this project 🎉

Ongoing, see #267 and #268.

Sent this email to pyup:

Hi!
I just read your docs and seems that all the updates go through requirements.txt. Don't you support changing setup.py directly? I normally don't use requirements files because of https://caremad.io/posts/2013/07/setup-vs-requirement/
On the other hand, with the imminent releases of pip 10 and flit, do you intend to support changing requirements in pyproject.toml, aka PEP 518?
https://snarky.ca/clarifying-pep-518/
Best!

If their answers are negative, we will have to consider other alternatives, such as:

https://github.com/marketplace/gemnasium
https://dependabot.com/
Others?

pyup response:
The problem with setup.py is that you need to execute it on the server side. Python can’t be sandboxed in a reliable way which makes it hard to support them.
PEP 518 and Pipenv’s Pipfiles will be supported. I’m currently waiting for the internal API to settle down.

I think the most sensible thing is to wait for pip 10.0. It will still take some time, so I'm postponing this.

Even though pip 10.0 was released, PEP 518 is still partially implemented and PEP 517 will have to wait, so I'm closing this issue until things improve.

Interestingly, we switched to setup.cfg in #613 and now pyup started working. I don't like its pinning behavior though, so I will see if we can configure it.


Crashes when breaking tile entities

I encounter the following crash whenever I break a manual crank, or a water wheel. If it matters at all, they were both in water. This was on fabric-loader-0.10.8-1.16.4, version 0.2.0 of the mod.
crash-2020-12-19_01.15.38-client.txt

Hmm, this actually seems to be a conflict with OptiFabric + Optifine.

I believe that updating fabric API mod fixed this conflict for me, These are the version I used:

Raise the minimal version number perhaps?

..No, it isn't. The following crash log does not have it enabled.
crash-2020-12-19_20.39.50-client.txt

(Bump) got the same error today when breaking tiles:
Cannot get property class_2753{name=facing, clazz=class net.minecraft.class_2350, values=[north, south, west, east]} as it does not exist in Block{minecraft:air}

got it only using this and optifine (i would really love to use optifine :( )

As I said prior, this has nothing to do with optifine.


move popgun.init() to angular-popgun api and call at app level

👍  LGTM. Yeah so then with this change we'll also add init to UIQ and RIQ right after. or stuff will break.