text:
Cannot finetune GLM-4-V with Deepspeed

I have tried to use deepspeed zero2 & zero3. I have met different issues.
For default-zero2, I got AttributeError: 'DummyOptim' object has no attribute 'step'

For default-zero3, I got RuntimeError: 'weight' must be 2-D

My conda environment:
cuda 11.8
torch                     2.4.0+cu118
torchvision               0.19.0+cu118
transformers              4.44.2
deepspeed                 0.15.1

Use DeepSpeed with multiple GPUs please.
zero3: Please upgrade ms-swift.

Hi Jintao, thanks for your kind reply.
I'm using multiple gpus and I believe I have installed the latest version of ms-swift.  I have attached my conda env below if that can help. Thanks!
Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
absl-py                   2.1.0                    pypi_0    pypi
accelerate                0.34.2                   pypi_0    pypi
addict                    2.4.0                    pypi_0    pypi
aiofiles                  23.2.1                   pypi_0    pypi
aiohappyeyeballs          2.4.0                    pypi_0    pypi
aiohttp                   3.10.5                   pypi_0    pypi
aiosignal                 1.3.1                    pypi_0    pypi
aliyun-python-sdk-core    2.15.2                   pypi_0    pypi
aliyun-python-sdk-kms     2.16.5                   pypi_0    pypi
altair                    5.4.1                    pypi_0    pypi
annotated-types           0.7.0                    pypi_0    pypi
antlr4-python3-runtime    4.9.3                    pypi_0    pypi
anyio                     4.6.0                    pypi_0    pypi
argon2-cffi               23.1.0                   pypi_0    pypi
argon2-cffi-bindings      21.2.0                   pypi_0    pypi
arrow                     1.3.0                    pypi_0    pypi
arxiv                     2.1.3                    pypi_0    pypi
asttokens                 2.4.1                    pypi_0    pypi
async-lru                 2.0.4                    pypi_0    pypi
async-timeout             4.0.3                    pypi_0    pypi
attrdict                  2.0.1                    pypi_0    pypi
attrs                     24.2.0                   pypi_0    pypi
babel                     2.16.0                   pypi_0    pypi
beautifulsoup4            4.12.3                   pypi_0    pypi
binpacking                1.5.2                    pypi_0    pypi
bitsandbytes              0.42.0                   pypi_0    pypi
bleach                    6.1.0                    pypi_0    pypi
blinker                   1.8.2                    pypi_0    pypi
brotli                    1.1.0                    pypi_0    pypi
bzip2                     1.0.8                h4bc722e_7    conda-forge
ca-certificates           2024.8.30            hbcca054_0    conda-forge
cachetools                5.5.0                    pypi_0    pypi
certifi                   2024.8.30                pypi_0    pypi
cffi                      1.17.1                   pypi_0    pypi
charset-normalizer        3.3.2                    pypi_0    pypi
click                     8.1.7                    pypi_0    pypi
colorama                  0.4.6                    pypi_0    pypi
comm                      0.2.2                    pypi_0    pypi
contourpy                 1.3.0                    pypi_0    pypi
cpm-kernels               1.0.11                   pypi_0    pypi
crcmod                    1.7                      pypi_0    pypi
cryptography              43.0.1                   pypi_0    pypi
cycler                    0.12.1                   pypi_0    pypi
dacite                    1.8.1                    pypi_0    pypi
datasets                  2.21.0                   pypi_0    pypi
debugpy                   1.8.5                    pypi_0    pypi
decorator                 4.4.2                    pypi_0    pypi
decord                    0.6.0                    pypi_0    pypi
deepspeed                 0.15.1                   pypi_0    pypi
defusedxml                0.7.1                    pypi_0    pypi
dill                      0.3.8                    pypi_0    pypi
distro                    1.9.0                    pypi_0    pypi
docstring-parser          0.16                     pypi_0    pypi
duckduckgo-search         5.3.1b1                  pypi_0    pypi
editdistance              0.8.1                    pypi_0    pypi
einops                    0.8.0                    pypi_0    pypi
et-xmlfile                1.1.0                    pypi_0    pypi
evalscope                 0.5.4                    pypi_0    pypi
evaluate                  0.4.3                    pypi_0    pypi
exceptiongroup            1.2.2                    pypi_0    pypi
executing                 2.1.0                    pypi_0    pypi
fastapi                   0.115.0                  pypi_0    pypi
fastjsonschema            2.20.0                   pypi_0    pypi
feedparser                6.0.11                   pypi_0    pypi
ffmpy                     0.4.0                    pypi_0    pypi
filelock                  3.16.1                   pypi_0    pypi
fonttools                 4.54.1                   pypi_0    pypi
fqdn                      1.5.1                    pypi_0    pypi
frozenlist                1.4.1                    pypi_0    pypi
fsspec                    2024.6.1                 pypi_0    pypi
func-timeout              4.3.5                    pypi_0    pypi
future                    1.0.0                    pypi_0    pypi
fuzzywuzzy                0.18.0                   pypi_0    pypi
gitdb                     4.0.11                   pypi_0    pypi
gitpython                 3.1.43                   pypi_0    pypi
gradio                    4.44.0                   pypi_0    pypi
gradio-client             1.3.0                    pypi_0    pypi
griffe                    1.3.1                    pypi_0    pypi
grpcio                    1.66.1                   pypi_0    pypi
h11                       0.14.0                   pypi_0    pypi
h2                        4.1.0                    pypi_0    pypi
h5py                      3.11.0                   pypi_0    pypi
hjson                     3.1.0                    pypi_0    pypi
hpack                     4.0.0                    pypi_0    pypi
httpcore                  1.0.5                    pypi_0    pypi
httpx                     0.27.2                   pypi_0    pypi
huggingface-hub           0.25.1                   pypi_0    pypi
hyperframe                6.0.1                    pypi_0    pypi
idna                      3.10                     pypi_0    pypi
imageio                   2.35.1                   pypi_0    pypi
imageio-ffmpeg            0.5.1                    pypi_0    pypi
immutabledict             4.2.0                    pypi_0    pypi
importlib-metadata        8.5.0                    pypi_0    pypi
importlib-resources       6.4.5                    pypi_0    pypi
ipykernel                 6.29.5                   pypi_0    pypi
ipython                   8.27.0                   pypi_0    pypi
ipywidgets                8.1.5                    pypi_0    pypi
isoduration               20.11.0                  pypi_0    pypi
jedi                      0.19.1                   pypi_0    pypi
jieba                     0.42.1                   pypi_0    pypi
jinja2                    3.1.4                    pypi_0    pypi
jiter                     0.5.0                    pypi_0    pypi
jmespath                  0.10.0                   pypi_0    pypi
joblib                    1.4.2                    pypi_0    pypi
json5                     0.9.25                   pypi_0    pypi
jsonlines                 4.0.0                    pypi_0    pypi
jsonpointer               3.0.0                    pypi_0    pypi
jsonschema                4.23.0                   pypi_0    pypi
jsonschema-specifications 2023.12.1                pypi_0    pypi
jupyter                   1.1.1                    pypi_0    pypi
jupyter-client            8.6.3                    pypi_0    pypi
jupyter-console           6.6.3                    pypi_0    pypi
jupyter-core              5.7.2                    pypi_0    pypi
jupyter-events            0.10.0                   pypi_0    pypi
jupyter-lsp               2.2.5                    pypi_0    pypi
jupyter-server            2.14.2                   pypi_0    pypi
jupyter-server-terminals  0.5.3                    pypi_0    pypi
jupyterlab                4.2.5                    pypi_0    pypi
jupyterlab-pygments       0.3.0                    pypi_0    pypi
jupyterlab-server         2.27.3                   pypi_0    pypi
jupyterlab-widgets        3.0.13                   pypi_0    pypi
kiwisolver                1.4.7                    pypi_0    pypi
lagent                    0.2.3                    pypi_0    pypi
lazy-loader               0.4                      pypi_0    pypi
ld_impl_linux-64          2.43                 h712a8e2_1    conda-forge
levenshtein               0.26.0                   pypi_0    pypi
libffi                    3.4.2                h7f98852_5    conda-forge
libgcc                    14.1.0               h77fa898_1    conda-forge
libgcc-ng                 14.1.0               h69a702a_1    conda-forge
libgfortran               14.1.0               h69a702a_1    conda-forge
libgfortran5              14.1.0               hc5f4f2c_1    conda-forge
libgomp                   14.1.0               h77fa898_1    conda-forge
libnsl                    2.0.1                hd590300_0    conda-forge
libsqlite                 3.46.1               hadc24fc_0    conda-forge
libstdcxx                 14.1.0               hc0a3c3a_1    conda-forge
libuuid                   2.38.1               h0b41bf4_0    conda-forge
libxcrypt                 4.4.36               hd590300_1    conda-forge
libzlib                   1.3.1                hb9d3cd8_2    conda-forge
lxml                      5.3.0                    pypi_0    pypi
markdown                  3.7                      pypi_0    pypi
markdown-it-py            3.0.0                    pypi_0    pypi
markupsafe                2.1.5                    pypi_0    pypi
matplotlib                3.9.2                    pypi_0    pypi
matplotlib-inline         0.1.7                    pypi_0    pypi
mdurl                     0.1.2                    pypi_0    pypi
mistune                   3.0.2                    pypi_0    pypi
mmengine                  0.10.5                   pypi_0    pypi
mmengine-lite             0.10.5                   pypi_0    pypi
modelscope                1.18.1                   pypi_0    pypi
moviepy                   1.0.3                    pypi_0    pypi
mpi                       1.0.1                     mpich    conda-forge
mpi4py                    4.0.1           py310hc9139ab_0    conda-forge
mpich                     4.2.3              h670b19f_100    conda-forge
mpmath                    1.3.0                    pypi_0    pypi
ms-opencompass            0.1.1                    pypi_0    pypi
ms-swift                  2.4.2.post2              pypi_0    pypi
ms-vlmeval                0.0.9                    pypi_0    pypi
multidict                 6.1.0                    pypi_0    pypi
multiprocess              0.70.16                  pypi_0    pypi
narwhals                  1.8.3                    pypi_0    pypi
nbclient                  0.10.0                   pypi_0    pypi
nbconvert                 7.16.4                   pypi_0    pypi
nbformat                  5.10.4                   pypi_0    pypi
ncurses                   6.5                  he02047a_1    conda-forge
nest-asyncio              1.6.0                    pypi_0    pypi
networkx                  3.3                      pypi_0    pypi
ninja                     1.11.1.1                 pypi_0    pypi
nltk                      3.9.1                    pypi_0    pypi
notebook                  7.2.2                    pypi_0    pypi
notebook-shim             0.2.4                    pypi_0    pypi
numpy                     1.26.4                   pypi_0    pypi
nvidia-cublas-cu11        11.11.3.6                pypi_0    pypi
nvidia-cublas-cu12        12.1.3.1                 pypi_0    pypi
nvidia-cuda-cupti-cu11    11.8.87                  pypi_0    pypi
nvidia-cuda-cupti-cu12    12.1.105                 pypi_0    pypi
nvidia-cuda-nvrtc-cu11    11.8.89                  pypi_0    pypi
nvidia-cuda-nvrtc-cu12    12.1.105                 pypi_0    pypi
nvidia-cuda-runtime-cu11  11.8.89                  pypi_0    pypi
nvidia-cuda-runtime-cu12  12.1.105                 pypi_0    pypi
nvidia-cudnn-cu11         9.1.0.70                 pypi_0    pypi
nvidia-cudnn-cu12         9.1.0.70                 pypi_0    pypi
nvidia-cufft-cu11         10.9.0.58                pypi_0    pypi
nvidia-cufft-cu12         11.0.2.54                pypi_0    pypi
nvidia-curand-cu11        10.3.0.86                pypi_0    pypi
nvidia-curand-cu12        10.3.2.106               pypi_0    pypi
nvidia-cusolver-cu11      11.4.1.48                pypi_0    pypi
nvidia-cusolver-cu12      11.4.5.107               pypi_0    pypi
nvidia-cusparse-cu11      11.7.5.86                pypi_0    pypi
nvidia-cusparse-cu12      12.1.0.106               pypi_0    pypi
nvidia-nccl-cu11          2.20.5                   pypi_0    pypi
nvidia-nccl-cu12          2.20.5                   pypi_0    pypi
nvidia-nvjitlink-cu12     12.6.68                  pypi_0    pypi
nvidia-nvtx-cu11          11.8.86                  pypi_0    pypi
nvidia-nvtx-cu12          12.1.105                 pypi_0    pypi
omegaconf                 2.3.0                    pypi_0    pypi
openai                    1.47.1                   pypi_0    pypi
opencc                    1.1.9                    pypi_0    pypi
opencv-python             4.10.0.84                pypi_0    pypi
openpyxl                  3.1.5                    pypi_0    pypi
openssl                   3.3.2                hb9d3cd8_0    conda-forge
orjson                    3.10.7                   pypi_0    pypi
oss2                      2.19.0                   pypi_0    pypi
overrides                 7.7.0                    pypi_0    pypi
packaging                 24.1                     pypi_0    pypi
pandas                    2.2.3                    pypi_0    pypi
pandocfilters             1.5.1                    pypi_0    pypi
parso                     0.8.4                    pypi_0    pypi
peft                      0.12.0                   pypi_0    pypi
pexpect                   4.9.0                    pypi_0    pypi
phx-class-registry        5.0.0                    pypi_0    pypi
pillow                    10.4.0                   pypi_0    pypi
pip                       24.2               pyh8b19718_1    conda-forge
platformdirs              4.3.6                    pypi_0    pypi
plotly                    5.24.1                   pypi_0    pypi
ply                       3.11                     pypi_0    pypi
portalocker               2.10.1                   pypi_0    pypi
prettytable               3.11.0                   pypi_0    pypi
proglog                   0.1.10                   pypi_0    pypi
prometheus-client         0.21.0                   pypi_0    pypi
prompt-toolkit            3.0.47                   pypi_0    pypi
protobuf                  5.28.2                   pypi_0    pypi
psutil                    6.0.0                    pypi_0    pypi
ptyprocess                0.7.0                    pypi_0    pypi
pure-eval                 0.2.3                    pypi_0    pypi
py-cpuinfo                9.0.0                    pypi_0    pypi
pyarrow                   17.0.0                   pypi_0    pypi
pycparser                 2.22                     pypi_0    pypi
pycryptodome              3.20.0                   pypi_0    pypi
pydantic                  2.9.2                    pypi_0    pypi
pydantic-core             2.23.4                   pypi_0    pypi
pydeck                    0.9.1                    pypi_0    pypi
pydub                     0.25.1                   pypi_0    pypi
pygments                  2.18.0                   pypi_0    pypi
pympler                   1.1                      pypi_0    pypi
pyparsing                 3.1.4                    pypi_0    pypi
pypinyin                  0.53.0                   pypi_0    pypi
python                    3.10.15         h4a871b0_1_cpython    conda-forge
python-dateutil           2.9.0.post0              pypi_0    pypi
python-dotenv             1.0.1                    pypi_0    pypi
python-json-logger        2.0.7                    pypi_0    pypi
python-levenshtein        0.26.0                   pypi_0    pypi
python-multipart          0.0.10                   pypi_0    pypi
python_abi                3.10                    5_cp310    conda-forge
pytz                      2024.2                   pypi_0    pypi
pyyaml                    6.0.2                    pypi_0    pypi
pyzmq                     26.2.0                   pypi_0    pypi
rank-bm25                 0.2.2                    pypi_0    pypi
rapidfuzz                 3.10.0                   pypi_0    pypi
readline                  8.2                  h8228510_1    conda-forge
referencing               0.35.1                   pypi_0    pypi
regex                     2024.9.11                pypi_0    pypi
requests                  2.32.3                   pypi_0    pypi
requests-toolbelt         1.0.0                    pypi_0    pypi
rfc3339-validator         0.1.4                    pypi_0    pypi
rfc3986-validator         0.1.1                    pypi_0    pypi
rich                      13.8.1                   pypi_0    pypi
rouge                     1.0.1                    pypi_0    pypi
rouge-chinese             1.0.3                    pypi_0    pypi
rouge-score               0.1.2                    pypi_0    pypi
rpds-py                   0.20.0                   pypi_0    pypi
ruff                      0.6.7                    pypi_0    pypi
sacrebleu                 2.4.3                    pypi_0    pypi
safetensors               0.4.5                    pypi_0    pypi
scikit-image              0.24.0                   pypi_0    pypi
scikit-learn              1.5.2                    pypi_0    pypi
scipy                     1.14.1                   pypi_0    pypi
seaborn                   0.13.2                   pypi_0    pypi
semantic-version          2.10.0                   pypi_0    pypi
send2trash                1.8.3                    pypi_0    pypi
sentence-transformers     3.1.1                    pypi_0    pypi
sentencepiece             0.2.0                    pypi_0    pypi
setuptools                69.5.1                   pypi_0    pypi
sgmllib3k                 1.0.0                    pypi_0    pypi
shellingham               1.5.4                    pypi_0    pypi
shtab                     1.7.1                    pypi_0    pypi
simple-ddl-parser         1.6.1                    pypi_0    pypi
simplejson                3.19.3                   pypi_0    pypi
six                       1.16.0                   pypi_0    pypi
smmap                     5.0.1                    pypi_0    pypi
sniffio                   1.3.1                    pypi_0    pypi
socksio                   1.0.0                    pypi_0    pypi
sortedcontainers          2.4.0                    pypi_0    pypi
soupsieve                 2.6                      pypi_0    pypi
stack-data                0.6.3                    pypi_0    pypi
starlette                 0.38.6                   pypi_0    pypi
streamlit                 1.38.0                   pypi_0    pypi
sty                       1.0.6                    pypi_0    pypi
sympy                     1.13.3                   pypi_0    pypi
tabulate                  0.9.0                    pypi_0    pypi
tenacity                  8.5.0                    pypi_0    pypi
tensorboard               2.17.1                   pypi_0    pypi
tensorboard-data-server   0.7.2                    pypi_0    pypi
termcolor                 2.4.0                    pypi_0    pypi
terminado                 0.18.1                   pypi_0    pypi
threadpoolctl             3.5.0                    pypi_0    pypi
tifffile                  2024.9.20                pypi_0    pypi
tiktoken                  0.7.0                    pypi_0    pypi
timeout-decorator         0.5.0                    pypi_0    pypi
tinycss2                  1.3.0                    pypi_0    pypi
tk                        8.6.13          noxft_h4845f30_101    conda-forge
tokenizers                0.19.1                   pypi_0    pypi
toml                      0.10.2                   pypi_0    pypi
tomli                     2.0.1                    pypi_0    pypi
tomlkit                   0.12.0                   pypi_0    pypi
torch                     2.4.0+cu118              pypi_0    pypi
torchvision               0.19.0+cu118             pypi_0    pypi
tornado                   6.4.1                    pypi_0    pypi
tqdm                      4.66.5                   pypi_0    pypi
traitlets                 5.14.3                   pypi_0    pypi
transformers              4.44.2                   pypi_0    pypi
transformers-stream-generator 0.0.5                    pypi_0    pypi
triton                    3.0.0                    pypi_0    pypi
trl                       0.11.0                   pypi_0    pypi
typer                     0.12.5                   pypi_0    pypi
types-python-dateutil     2.9.0.20240906           pypi_0    pypi
typing-extensions         4.12.2                   pypi_0    pypi
tyro                      0.8.11                   pypi_0    pypi
tzdata                    2024.2                   pypi_0    pypi
uri-template              1.3.0                    pypi_0    pypi
urllib3                   2.2.3                    pypi_0    pypi
uvicorn                   0.30.6                   pypi_0    pypi
validators                0.34.0                   pypi_0    pypi
watchdog                  4.0.2                    pypi_0    pypi
wcwidth                   0.2.13                   pypi_0    pypi
webcolors                 24.8.0                   pypi_0    pypi
webencodings              0.5.1                    pypi_0    pypi
websocket-client          1.8.0                    pypi_0    pypi
websockets                12.0                     pypi_0    pypi
werkzeug                  3.0.4                    pypi_0    pypi
wheel                     0.44.0             pyhd8ed1ab_0    conda-forge
widgetsnbextension        4.0.13                   pypi_0    pypi
xlsxwriter                3.2.0                    pypi_0    pypi
xtuner                    0.1.23                   pypi_0    pypi
xxhash                    3.5.0                    pypi_0    pypi
xz                        5.2.6                h166bdaf_0    conda-forge
yapf                      0.40.2                   pypi_0    pypi
yarl                      1.12.1                   pypi_0    pypi
zipp                      3.20.2                   pypi_0    pypi

pip install ms-swift -U

authors: Jintao-Huang Li-Jicheng


text:
🛑 Bitwarden is down

In 629aedd, Bitwarden ($BITWARDEN_URL) was down:

HTTP code: 523
Response time: 3104 ms

Resolved: Bitwarden is back up in 91ac987.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 Grafana is down

In 6bc7414, Grafana ($GRAFANA_URL) was down:

HTTP code: 403
Response time: 598 ms

Resolved: Grafana is back up in 6b220f6.


text:
BUG: try_cast_to_pandas doesn't preserve dtypes for empty frame

Reproducer:
def test_try_cast_to_pandas_preserve_dtypes():
    modin_df = pd.DataFrame({"col": [1]}, dtype=np.int64)
    pandas_df = pandas.DataFrame({"col": [1]}, dtype=np.int64)
    modin_df.query("col > 2", inplace=True), pandas_df.query("col > 2", inplace=True)
    casted_to_pandas_df = modin.utils.try_cast_to_pandas(modin_df)
    df_equals(casted_to_pandas_df, pandas_df)
    df_equals(casted_to_pandas_df.dtypes, pandas_df.dtypes)

Error:
E   AssertionError: Series are different
E
E   Series values are different (100.0 %)
E   [index]: [col]
E   [left]:  [object]
E   [right]: [int64]

@anmyachev @Billy2551 is working on #4605. In case you don't need this fixed urgently, you could skip the fix and wait for a comprehensive fix, which should hopefully come within 3 months, for #4605.

@anmyachev @Billy2551 is working on #4605. In case you don't need this fixed urgently, you could skip the fix and wait for a comprehensive fix, which should hopefully come within 3 months, for #4605.

Good! My other PR highlights this problem in CI, then I'll just mark it as xfail.

From what I've seen so far, from_pandas function doesn't save dtypes of the empty dataframe either (because the empty dataframe doesn't get into put function).

Problem not reproducible on master.

authors: anmyachev mvashishtha

repo: modin-project/modin


text:
test_reduce_specific failed due to different exception messages

Found in https://github.com/modin-project/modin/pull/6954

HDK engine is deprecated and will be removed in a future version.

authors: YarShev anmyachev


text:
Correctly populate file-type fields on context change

Add additional values to the array sent back for file & image type fields only so they populate the fields correctly on context change.
What does it do ?
Checks if a field type is an image or file and sets two additional values in the returned JSON so that form.setValues() can do its job properly.
Why is it needed ?
These fields weren't being repopulated on context change which was leading to oversaving of the default/global value on each save following the main page load. (Main page loads, brings default value, context change does nothing, next save overwrites context value with still-present global/default vale).
Related issue(s)/PR(s)
Let us know if this is related to any issue/pull request
This should resolve #147

Thanks, included in 2.1

source: gharchive/pull-request

authors: Mark-H jcdm

repo: modmore/ClientConfig

license: mit

license_source: bigquery


text:
Tests failure when using Vitest and module-federation/vite together

@module-federation/vite@1.1.8
vite@5.2.0,
vitest@1.6.0
When running test the following error is thrown
TypeError: Method Promise.prototype.then called on incompatible receiver [object Module]

Upgraded to vitest@2.1.5 but the end result is the same :(

Hi @theohagos can you create a basic example with that shows this issue please?

@gioboa it is an internal JPMorgan project so afraid won't be able to post an exact replica but I have narrowed it down to recoiljs that is causing this error. I am also using nx workspace with rspack module federation to create remote MFEs. These apps also use recoil with vitest and the tests run successfully without this error.

So the problem is the combination mf/vite + recoiljs + vitest, right?

Hello @gioboa,
Yes exactly that. Remove recoiljs test passes, add recoiljs back and then test throws above error. But there is no error when running the app, it works, it consumes remotes and no issues there.
Funnily enough I have the opposite problem with originjs/vite-plugin-federation, that is what led me to this plugin. With origin, tests pass but the app fails with this error Cannot read properties of null (reading 'useState'), looks like it is loading multiple version of react.

looks like it is loading multiple version of react.

You can share react dep to avoid that problem, but idk if you can do it with that plugin

Have you tried with different Node versions?

I have the same error when running Vitest + mf/vite
My versions:
vite@5.4.2,
vitest@2.0.5
I'm not using Recoil. Tested with node versions 16, 18 and 20. All of them outputs the same error message:

I tested using vi.doMock and Error: [vitest] There was an error when mocking a module. If you are using "vi.mock" factory, make sure there are no top level variables inside, since this call is hoisted to top of the file. Read more: https://vitest.dev/api/vi.html#vi-mock message disappears but TypeError: Method Promise.prototype.then called on incompatible receiver [object Module] continues.

Hi @gioboa,
so it looks like it may not be specific to recoiljs since @deizianens is ALSO facing the same error without using recoiljs?

Hi @deizianens , can you create a basic example that reproduce the issue please?

Sure @gioboa
You can reproduce the error TypeError: Method Promise.prototype.then called on incompatible receiver [object Module] with:
https://github.com/deizianens/mfe-vite

It is happening to me too, my tests were working with originjs/vite-plugin-federation and when I replaced it with this library, they started to fail, but I don't use Recoil, only vitest

When you were using originjs/vite-plugin-federation was there any additional setup or mocking you had to do to get the tests to pass? I have tried both and both seem to have issues with the tests.  I'm getting the same error. Unfortunately, it is for my employer, and can not share specifics

@saraiba33 I haven't changed anything, but what I did to skip this issue was to avoid federation when running tests, just doing the following in vite.config:
 plugins: [
      ...
      mode !== 'test' &&
        federation({
     ...

I tried the repo and I update the dependencies
"@module-federation/vite": "^1.2.0",
"vite": "^6.0.2"

It's working fine
@theohagos can you please check this out?

I tested the @deizianens example https://github.com/deizianens/mfe-vite
and without federation.shared config the error is gone. I'll investigate more in the next days.

I get the same error when I include a Suspense around my component

authors: JamesMHenderson deizianens gioboa mgreca saraiba33 theohagos

repo: module-federation/vite


text:
Add ampersand support for selectors

Our primitives would export something like:
export const resetStyles = {
  root: {
    display: 'flex',

    '&[data-state-disabled]': {
      pointerEvents: 'none',
    },
  },
};

and then the consumer would do:
import { ComponentPrimitive, resetStyles } from '@interop/primitives';

const Component = styled(ComponentPrimitive, {
  ...resetStyles.root,
  border: '1px solid green';
});

The ampersand means this spreading by the consumer would work in styled-components, emotion and also stitches.
@christianalfoni was thinking we could have selector logic as:

If it starts with &, remove it
If it now starts with : or [, treat as state selector
If not, insert a space to treat as nested element selector

{
  '&:hover': {},
  'div': {},
  '&[..]': {},
}

Also, I raised a comment before about potentially interpolating a class from a component toString method https://github.com/modulz/stitches/issues/52#issuecomment-656708402.
Specifically the ability to do something like:
[`${Input}:checked + &`]: {
  color: 'green',
  border: '1px solid red',
}

If our Input.toString() returned a randomly generated class specific to the component (.i1234) could we maybe make this output the following?
.i1234:checked + .color1 { color: 'green'; }
.i1234:checked + .border-size1 { border-size: '1px' }
.i1234:checked + .border-style1 { border-style: 'solid' }
.i1234:checked + .border-color1 { border-color: 'red' }

In this case, the & wouldn't be removed and instead it would be replaced with the atomic class.

@hadihallak maybe a good first issue? @christianalfoni can review

Initial implementation here https://github.com/modulz/stitches/pull/88
We only support & at the beginning of the selector. This is mainly for familiarity with other devs and remove the need to have a space to target descendants.

Okay, so I did an implementation of this on poc for reference.
Instead of looking at the prop to figure out if it is a selector or not, I rather look at props[prop], if it is an object it means there are nested styles, which means the prop is a selector
This makes things a lot more straight forward it looks. Basically creating the whole selector now becomes:
    // Allow using "&" to position the classname, also multiple times
    const selector =
      this.pseudo && this.pseudo.includes("&")
        ? this.pseudo.replace(/&/gi, `.${className}`)
        : this.pseudo
        ? `.${className}${this.pseudo}`
        : `.${className}`;

Fixed in #112

authors: christianalfoni hadihallak jjenzz peduarte

repo: modulz/stitches


text:
🛑 STATUS.MOFE.IO is down

In a88abc3, STATUS.MOFE.IO (https://status.mofe.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: STATUS.MOFE.IO is back up in 80b9e64.

repo: mofelee/upptime


text:
🛑 STATUS.MOFE.IO is down

In 7c3c594, STATUS.MOFE.IO (https://status.mofe.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: STATUS.MOFE.IO is back up in ed55725.


text:
Nwm dev

Please review the latest version of HOWTO after applying user's notes. I have changed the format and it is detailed. I am not sure if it is better or more confusing! Please comment.

Thanks.
Sent from my phone. please excuse me for any possible typos.
On Sat, Apr 25, 2020, 20:58 Ava Trimble notifications@github.com wrote:

Please review the latest version of HOWTO after applying user's notes. I
have changed the format and it is detailed. I am not sure if it is better
or more confusing! Please comment.
You can view, comment on, or merge this pull request online at:
https://github.com/moghimis/ADC-WW3-NWM-NEMS/pull/5
Commit Summary

added more rules
Merge branch 'nwm_dev' of
https://github.com/trimbleava/ADC-WW3-NWM-NEMS into nwm_dev
modified
modified HOWTO
Modified based on user input

File Changes

M HOWTO
https://github.com/moghimis/ADC-WW3-NWM-NEMS/pull/5/files#diff-05bc0511c8db43874bb452c70f7b6ddf
(731)

Patch Links:

https://github.com/moghimis/ADC-WW3-NWM-NEMS/pull/5.patch
https://github.com/moghimis/ADC-WW3-NWM-NEMS/pull/5.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/moghimis/ADC-WW3-NWM-NEMS/pull/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4GLFEKBE5M4TIUMYNEQ3DROOBLJANCNFSM4MQ7VVWA
.

authors: moghimis trimbleava


text:
Latest Stats Proposal

It would be nice to add the average ETH burnt per day since 159 launched. I'd imagine it's a fairly simple calculation, something along the lines of:
average burnt per day = (total burnt) / ( [(current epoch)-(start epoch)] \ 86400)
Current:

Latest Stats

Base Fee
56 GWEI

Watching the Burn
297 users

Proposed:

Latest Stats

Base Fee
56 GWEI

Ave Burn Per Day
4,567.89 ETH

Watching the Burn
297 users

Yes on the pipeline :D /cc @stevengcook

@hanniabu  it now looks like this, we have aggregations for 1d 7d 1m and all

authors: hanniabu mohamedmansour

repo: mohamedmansour/ethereum-burn-stats


text:
The topology and DCD trajectory files don't have the same number of atoms

Dear Sir
I am trying TTMD calculation with default config_rt.dat files provided by you. I am getting following errors, please help me to solve this problem
Traceback (most recent call last):
File "/mnt/d/TTMD-2.0/package/ttmd.py", line 150, in
RUN_class.run(VARS)
File "/mnt/d/TTMD-2.0/package/ttmd.py", line 55, in run
self.serial(vars)
File "/mnt/d/TTMD-2.0/package/ttmd.py", line 65, in serial
replica_run(i, self.device, vars)
File "/mnt/d/TTMD-2.0/package/ttmd.py", line 114, in replica_run
REPLICA_class.simulation()
File "/mnt/d/TTMD-2.0/package/replica.py", line 52, in simulation
simulation.run()
File "/mnt/d/TTMD-2.0/package/simulation/run.py", line 38, in run
avg = self.score_simulation(trj, i, set)
File "/mnt/d/TTMD-2.0/package/simulation/run.py", line 174, in score_simulation
outscore = self.score(self.complprmtop, wrap_trj, temp)
File "/mnt/d/TTMD-2.0/package/scoring_function/rt.py", line 52, in score
u = mda.Universe(topology, trajectory)
File "/home/drsaravanan/miniconda3/envs/ttmd2/lib/python3.10/site-packages/MDAnalysis/core/universe.py", line 365, in init
self.load_new(coordinates, format=format, in_memory=in_memory,
File "/home/drsaravanan/miniconda3/envs/ttmd2/lib/python3.10/site-packages/MDAnalysis/core/universe.py", line 569, in load_new
raise ValueError("The topology and {form} trajectory files don't"
ValueError: The topology and DCD trajectory files don't have the same number of atoms!
Topology number of atoms 6116
Trajectory: run_300.dcd Number of atoms 76588
error.txt
Please check error.txt file

Dear Saranthee,
this issue is generated by a bug in the code.
It should be easily overcome by setting "dryer = yes" in the config file.
We are grateful for your patience and perseverance in using ttmd and we apologize for the inconvenience.
Kind regards,
Silvia

Dear Molecularmodelingsection/Ttmd,
The command "dryer=yes" is already available in the config file. In the
RUN_1/MD/ path, I got run_300, dry_300, and swag_300 files already. It is
taking automatically wrong prmtop file. It should take solv. prmtop and
run_300.dcd or dry_complex.prmtop with dry_300.dcd.
I have tried for three different complexes it is not working
also, I removed ttmd and reinstall ttmd it is not working
I kindly request you please help me to solve this problem
If you ready to check the files i will send you or i will give access to my
computer to check. Please help to solve this
On Tue, Apr 9, 2024 at 3:01 PM silviett @.***> wrote:

Dear Saranthee,
this issue is generated by a bug in the code.
It should be easily overcome by setting "dryer = yes" in the config file.
We are grateful for your patience and perseverance in using ttmd and we
apologize for the inconvenience.
Kind regards,
Silvia
—
Reply to this email directly, view it on GitHub
https://github.com/molecularmodelingsection/TTMD/issues/12#issuecomment-2045129851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFTFUOY4YVYMRC4W4OWJFULY4PRCFAVCNFSM6AAAAABFWZY2WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVGEZDSOBVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Dear TTMD group,
I am eagerly anticipating your response.
Kindly inform me if you are prepared to engage in collaborative research
work.
I possess a collection of complexes and require TTMD results.
Please inform me at your earliest convenience.
On Tue, Apr 9, 2024 at 3:39 PM Saravanan Kandasamy @.***>
wrote:

Dear Molecularmodelingsection/Ttmd,
The command "dryer=yes" is already available in the config file. In the
RUN_1/MD/ path, I got run_300, dry_300, and swag_300 files already. It is
taking automatically wrong prmtop file. It should take solv. prmtop and
run_300.dcd or dry_complex.prmtop with dry_300.dcd.
I have tried for three different complexes it is not working
also, I removed ttmd and reinstall ttmd it is not working
I kindly request you please help me to solve this problem
If you ready to check the files i will send you or i will give access to
my computer to check. Please help to solve this
On Tue, Apr 9, 2024 at 3:01 PM silviett @.***> wrote:

Dear Saranthee,
this issue is generated by a bug in the code.
It should be easily overcome by setting "dryer = yes" in the config file.
We are grateful for your patience and perseverance in using ttmd and we
apologize for the inconvenience.
Kind regards,
Silvia
—
Reply to this email directly, view it on GitHub
https://github.com/molecularmodelingsection/TTMD/issues/12#issuecomment-2045129851,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BFTFUOY4YVYMRC4W4OWJFULY4PRCFAVCNFSM6AAAAABFWZY2WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVGEZDSOBVGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Dear TTMD group, I am eagerly anticipating your response. Kindly inform me if you are prepared to engage in collaborative research work. I possess a collection of complexes and require TTMD results. Please inform me at your earliest convenience. On Tue, Apr 9, 2024 at 3:39 PM Saravanan Kandasamy @.> wrote:
…
Dear Molecularmodelingsection/Ttmd, The command "dryer=yes" is already available in the config file. In the RUN_1/MD/ path, I got run_300, dry_300, and swag_300 files already. It is taking automatically wrong prmtop file. It should take solv. prmtop and run_300.dcd or dry_complex.prmtop with dry_300.dcd. I have tried for three different complexes it is not working also, I removed ttmd and reinstall ttmd it is not working I kindly request you please help me to solve this problem If you ready to check the files i will send you or i will give access to my computer to check. Please help to solve this On Tue, Apr 9, 2024 at 3:01 PM silviett @.> wrote: > Dear Saranthee, > this issue is generated by a bug in the code. > It should be easily overcome by setting "dryer = yes" in the config file. > We are grateful for your patience and perseverance in using ttmd and we > apologize for the inconvenience. > Kind regards, > Silvia > > — > Reply to this email directly, view it on GitHub > <#12 (comment)>, > or unsubscribe > https://github.com/notifications/unsubscribe-auth/BFTFUOY4YVYMRC4W4OWJFULY4PRCFAVCNFSM6AAAAABFWZY2WWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBVGEZDSOBVGE > . > You are receiving this because you authored the thread.Message ID: > @.***> >

cd TTMD/package/simulation/
vi run.py and locate  line 38
Replace trj with traj. (I think it should look like "avg = self.score_simulation(traj, i, set)")

authors: kulibour saranthee silviett

repo: molecularmodelingsection/TTMD


text:
63-somnfeature-request---cdxml-file-as-user-input

Resolves #62
Resolves #64
Removed #63 Blocked
Staging environment is updated with this PR
Testing Procedure #62
Go to - https://mmli.fastapi.staging.mmli1.ncsa.illinois.edu/docs#/Somn/check_reaction_sites_somn_all_reaction_sites_get

Valid chemical

with chiral BrC1=C(C=CC=C1)CO[C@@H]2CCCCO2, role el
expected output: ..."has_chiral": true...,
without chiral BrC1=C(C=CC=C1)CO[CH]2CCCCO2, role el
expected output: ..."has_chiral": false...,

Invalid chemical

BrC1=C(C=CC=C1)CO[CH]2CCCCO, role el
expected output:  ... "detail": "Invalid SMILES string: BrC1=C(C=CC=C1)CO[C@@H]2CCCCO" ...

Chemical which failed 3d testing

TBD
expected output:  ... "detail": "Unable to generate 3D coordinates for XXX" ...

Testing procedure #64
Go to - https://mmli.fastapi.staging.mmli1.ncsa.illinois.edu/docs#/Somn/check_reaction_sites_somn_all_reaction_sites_get
Number of heavy atoms = number of non-hydrogen atoms

Valid chemical

without hydrogenBrC1=C(C=CC=C1), role el
expected output: ..."num_heavy_atoms": 7...,
with hydrogen BrC1=C(C=CC=C1)CO[C@@H]2CCCCO2, role el
expected output: ..."num_heavy_atoms": 15...,

Invalid chemical

BrC1=C(C=CC=C1)CO[CH]2CCCCO, role el
expected output:  ... "detail": "Invalid SMILES string: BrC1=C(C=CC=C1)CO[C@@H]2CCCCO" ...

Chemical which failed 3d testing

TBD
expected output:  ... "detail": "Unable to generate 3D coordinates for XXX" ...

blocked at #63 - detailed in issue page

repo: moleculemaker/mmli-backend


text:
Support /base/*? semantics

TL;DR: the docs are wrong here:
{/* will match everything else */}
<Route path="/:rest*">
   {(params) => `404, Sorry the page ${params.rest} does not exist!`}
</Route>

"/:rest*" does not in fact match "everything else" (does not match paths containing empty path segments).
Real world use-case that currently cannot currently be matched in this way: https://en.wikipedia.org/wiki///
Rather than showing the 404 page, the page will be blank for any path containing double slashes!

See https://github.com/WICG/urlpattern/issues/163 for why the existing capability /base/:remaining_path* doesn't cover all the bases! Instead, a pattern that does match everything after /base is /base/*?. For compatibility with react-router's behavior, the * segment's value could be auto-named simply * (cannot conflict with a named identifier since named identifiers must be alphanumeric). The * identifier can be of course renamed in the render function if you don't want to do params['*'], e.g.:
<Route path='/*?'>
    {({'*': rest}) => `404, Sorry the page ${rest} does not exist!`}
</Route>

Use-case: with a couple additional customizations, this enhancement will allow a robust nested router architecture.
Alternative: forget about URLPattern's questionable syntax choices and implement the same semantics with /base/*, dropping the trailing ? and staying consistent with react-router:
<Route path='/*'>
    {({'*': rest}) => `404, Sorry the page ${rest} does not exist!`}
</Route>

2nd Alternative: update the current behavior to align with the docs (even though this isn't currently compatible with URLPattern or path-to-regexp), and allow the existing syntax of /:remaining_path* to match arbitrary paths (including those with empty path segments in them).  We could then do /base/:_* to achieve the same thing as react-router's /base/*. Not quite as concise (which could be annoying for users who are repeating this pattern constantly), but it would work.

This has been added in v3-rc.1. I have switched to https://github.com/lukeed/regexparam which is more reliable and smaller.

authors: HansBrende molefrog

repo: molefrog/wouter

license: Unlicense


text:
Need support for search params.

Need something like useSearchParams in React Router to handle queries.

I was also facing the issue of extracting search params. But I have built a custom hook for that. I can raise a pull request for it.

Hi! Sorry, this isn't well documented (yet! PRs are welcome). You can subscribe to search string updates via:
import { useSearch, useLocationProperty, navigate } from 'wouter/use-location';

// get all search params:
const search = useSearch();

Note that you will have to parse these using URLSearchParams or a 3rd party library. We might add this in the future releases.

I see, this isn't provided out-of-the-box right now. But I'll try to hack a simple implementation for that.

I've written the useSearchParams function based on react-router's implementation for wouter. The API is similar if not identical to react-router's useSearchParams version.
So far it has been working great for me, hope it helps :)
lib/wouter.ts
import { useCallback, useMemo, useRef } from 'react';
import { navigate, useSearch } from 'wouter/use-location';

// Based on react-router: https://github.com/remix-run/react-router/blob/main/packages/react-router-dom/index.tsx

type ParamKeyValuePair = [string, string];

type URLSearchParamsInit =
  | string
  | ParamKeyValuePair[]
  | Record<string, string | string[]>
  | URLSearchParams;

export function createSearchParams(
  init: URLSearchParamsInit = '',
): URLSearchParams {
  return new URLSearchParams(
    typeof init === 'string' ||
    Array.isArray(init) ||
    init instanceof URLSearchParams
      ? init
      : Object.keys(init).reduce((memo, key) => {
          const value = init[key];
          return memo.concat(
            Array.isArray(value) ? value.map((v) => [key, v]) : [[key, value]],
          );
        }, [] as ParamKeyValuePair[]),
  );
}

export function getSearchParamsForLocation(
  locationSearch: string,
  defaultSearchParams: URLSearchParams | null,
) {
  const searchParams = createSearchParams(locationSearch);

  if (defaultSearchParams) {
    // Use `defaultSearchParams.forEach(...)` here instead of iterating of
    // `defaultSearchParams.keys()` to work-around a bug in Firefox related to
    // web extensions. Relevant Bugzilla tickets:
    // https://bugzilla.mozilla.org/show_bug.cgi?id=1414602
    // https://bugzilla.mozilla.org/show_bug.cgi?id=1023984
    defaultSearchParams.forEach((_, key) => {
      if (!searchParams.has(key)) {
        defaultSearchParams.getAll(key).forEach((value) => {
          searchParams.append(key, value);
        });
      }
    });
  }

  return searchParams;
}

export function useSearchParams(defaultInit?: URLSearchParamsInit) {
  if (typeof URLSearchParams !== 'undefined') {
    console.warn(
      `You cannot use the \`useSearchParams\` hook in a browser that does not ` +
        `support the URLSearchParams API. If you need to support Internet ` +
        `Explorer 11, we recommend you load a polyfill such as ` +
        `https://github.com/ungap/url-search-params\n\n` +
        `If you're unsure how to load polyfills, we recommend you check out ` +
        `https://polyfill.io/v3/ which provides some recommendations about how ` +
        `to load polyfills only for users that need them, instead of for every ` +
        `user.`,
    );
  }

  const defaultSearchParamsRef = useRef(createSearchParams(defaultInit));
  const hasSetSearchParamsRef = useRef(false);

  const search = useSearch();
  const searchParams = useMemo(
    () =>
      // Only merge in the defaults if we haven't yet called setSearchParams.
      // Once we call that we want those to take precedence, otherwise you can't
      // remove a param with setSearchParams({}) if it has an initial value
      getSearchParamsForLocation(
        search,
        hasSetSearchParamsRef.current ? null : defaultSearchParamsRef.current,
      ),
    [search],
  );

  const setSearchParams = useCallback(
    (
      nextInit:
        | URLSearchParamsInit
        | ((prev: URLSearchParams) => URLSearchParamsInit),
      navigateOpts?: Parameters<typeof navigate>['1'],
    ) => {
      const newSearchParams = createSearchParams(
        typeof nextInit === 'function' ? nextInit(searchParams) : nextInit,
      );
      hasSetSearchParamsRef.current = true;
      navigate('?' + newSearchParams, navigateOpts);
    },
    [searchParams],
  );

  return [searchParams, setSearchParams] as const;
}

app.tsx
export function App() {
  const [searchParams, setSearchParams] = useSearchParams();

  return (
    <main>
      <p>{searchParams.get('key')}</p>

      <button onClick={() => setSearchParams({ key: 'value' })}>
        Set Param
      </button>
      <button
        onClick={() =>
          setSearchParams((prevSearchParams) => ({
            ...Object.fromEntries(prevSearchParams),
            array: ['value_1', 'value_2'], // Array is supported just like react-router.
          }))
        }
      >
        Merge Params
      </button>
    </main>
  );
}

If interested, I could open up a PR to add this as an official helper util :)

Cool, that could be a nice feature to have in v3. We're preparing the first release candidate right now, I will let you know once it is ready, so you can start working on a PR.

The RC is out now. There is no useSearchParams yet, but we added it to the roadmap for v3.1

i find it quite often that you might want to replace searchParam but you don't really want to trigger a re-render in same component!
useSearch will trigger re-render everytime; infact current implementaion trigger re-render even if params/href didnot change at all. (it re-render on any navigation event)
a nice js helper to manipulate searchParams is more than enough more most cases imo
export function replaceSearchParam(qs: Record<string,string|number|boolean|null>, replace=false){
  const params = new URLSearchParams(location.search);
  for (const [key, value] of Object.entries(qs)) {
    if(value === null){
      params.delete(key);
    } else {
      params.set(key, `${value}`);
    }
  }
  if(replace){
    history.replaceState(null, "", `${location.pathname}?${params}`);
  } else {
    history.pushState(null, "", `${location.pathname}?${params}`);
  }
}

i find it quite often that you might want to replace searchParam but you don't really want to trigger a re-render in same component!
useSearch will trigger re-render everytime; infact current implementaion trigger re-render even if params/href didnot change at all. (it re-render on any navigation event)
a nice js helper to manipulate searchParams is more than enough more most cases imo
export function replaceSearchParam(qs: Record<string,string|number|boolean|null>, replace=false){
  const params = new URLSearchParams(location.search);
  for (const [key, value] of Object.entries(qs)) {
    if(value === null){
      params.delete(key);
    } else {
      params.set(key, `${value}`);
    }
  }
  if(replace){
    history.replaceState(null, "", `${location.pathname}?${params}`);
  } else {
    history.pushState(null, "", `${location.pathname}?${params}`);
  }
}

I believe triggering a re-render upon search changes is the desired behaviour. E.g, updating query ?status=failed will trigger an update on the UI and refetch API with status = "failed".
May I know on what occasion that you would want to update the search params without re-rendering? This also mean that when you hit back on the browser, nothing happens because UI does not re-render.


text:
Some webhooks not firing resulting in status not being changed

Expected behavior
Almost every payment gets through in our backend.
1 - 2 times a month the webhook is not firing, we don't see a log record for that specific order.
Steps to reproduce the behavior
We don't know why some get through en some doesn't.
Environment

PrestaShop version: 1.6.1.3 (replace this with the full version you are using).
Mollie module version: 1.2.6 (replace this with the full version you are using).

Hi @semammerlaan ,
We don't have enough information in order to properly advice you. You're also using an outdated verson of the Mollie module which is no longer supported. If you prefer to use an older version (because your PS version is pretty outdated as well), it might be best to use the Mollie module v1.3.0 or v1.3.1 which you can download here:
https://github.com/mollie/PrestaShop/releases?after=v2.0.4
Because the module version you are using is no longer in active development, we are closing this issue.
Kind Regards

authors: semammerlaan snowycatsoftware

repo: mollie/PrestaShop


text:
TypeError :parser.incoming._addHeaderLines is not a function

Hi, I'm working  http2 with express.js on my server. It good to work when I use firefox brower to connect the server, but it can't connect when I use chrome to connect, the server side show the following information :

And the server closed immediately. What's problem with me? Can someone help me to solved it.
Tools version:
express.js : 4.14
node-http2 : 3.3.6
firefox : 50.0
chrome : 54.0.2840.99 m

I am getting this issue too. Why is this issued closed without any solution or discussion?


text:
allow public_key, private_key in initiating session

Please do a version bump too ❤ ..

Ok, is all the HA integration in place?

Almost, I think I have the things I want in place now.

Excellent work, you rock! I'll make a release later today!

What about the comment you made inline? (on mobile can't search for it now)

Referring to this: https://github.com/molobrakos/tellduslive/commit/e0bbac416fd87ca0f3a2c7a510ff6dc146b42ea9#r31582180

https://github.com/molobrakos/tellduslive/releases/tag/v0.10.8

authors: fredrike molobrakos

repo: molobrakos/tellduslive


text:
Enable api domain config for event api client

Ticket: https://mlc.atlassian.net/browse/MCS-1148?focusedCommentId=253751&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-253751

Close since we have baseURL to allow customized API domain

repo: moloco-mcm/event-api-client-js


text:
chore: add better logging for dictionary tests

PR Description:
The test now outputs the actual keys and values stored in the dictionary like below example:
Hit Response Dictionary Contents:
Key: 60-7E-FC-0E-86-2F-C8-4D-AE-BD-1B-18-FB-1C-18-CE | Value: 87-4C-1A-5B-61-2A-DA-47-A4-26-3A-F3-40-65-68-55
Key: 9F-24-B9-EB-39-84-B4-43-A4-23-75-B4-DF-0C-54-CE | Value: 61-53-2C-CD-04-4D-56-49-8D-73-7D-33-B2-A6-A6-88

Follow-up pr - https://github.com/momentohq/client-sdk-dotnet/pull/570

repo: momentohq/client-sdk-dotnet


text:
fix(components/card): status color positioning

Description
The scope of the changes in this pull request is to fix the missing status-color visual elements from the <Card /> component for <MeetingContainerCard /> consumption.
Screenshots

Links
SPARK-329844

LGTM. Make sure to check the MeetingContainer > Common story with a narrow browser to see if the long title is still handled properly.

Looks like it is, lmk if you see any issues.


text:
Formula to calculate survival_time_in_days when patient is alive

Notes from discussion with @justaddcoffee on 4/16.
If person/patient is "Alive" then we need a way of populating survival time in days, and we can do that as follows:
when we last saw the patient (day of last encounter) - when the patient was diagnosed

In the GDC API, the field that corresponds to each of the above variables is:

when we last saw the patient (day of last encounter) -- diagnoses.days_to_last_follow_up
when the patient was diagnosed -- diagnoses.age_at_diagnosis

@sujaypatil96 we hacked on this a bit today. We observed that in the current code, survival time for Alive patients was often negative.
We think that is because last_follow_up means days since diagnosis (not days since birth):
Via: https://docs.gdc.cancer.gov/Data_Dictionary/viewer/#?view=table-definition-view&id=diagnosis&anchor=days_to_last_follow_up
"Time interval from the date of last follow up to the date of initial pathologic diagnosis, represented as a calculated number of days."
So, we've changed the code accordingly. Does this look correct to you?

@justaddcoffee yup, the code makes sense to me. All that needs to be returned is the "days_to_last_follow_up".
Do we need to comment out the code that makes calls to _process_vital_status() here?

https://github.com/monarch-initiative/oncoexporter/blob/develop/src/oncoexporter/cda/cda_individual_factory.py#L98C26-L98C47
https://github.com/monarch-initiative/oncoexporter/blob/develop/src/oncoexporter/cda/cda_individual_factory.py#L113-L114

@sujaypatil96 is _process_vital_status() not being used? I just ran the code through a debugger and it seems this is still the way we are populating vital status for the phenopacket, right?

repo: monarch-initiative/oncoexporter


text:
Please add tasteless.io

Tasteless.io is a adult store merchant accepting Monero :)

Added in #646
Thank you!
+merchant
+in progress

authors: bitcoinsextoys erciccione

repo: monero-project/monero-site


text:
Merchants & Services:::Goods

CryptoKey now accepts Monero as payment (Selling various solutions for cryptocurrency seed word backup), please add to the list, thanks!
Site URL: CryptoKey

I'm on it


text:
🛑 Bitlending Staging Monetix is down

In e339176, Bitlending Staging Monetix (https://api.bitlending-staging.monetix.io/health) was down:

HTTP code: 502
Response time: 547 ms

Resolved: Bitlending Staging Monetix is back up in a286447.

repo: monetixio/upptime


text:
[Feature Request] belongsToMany in HybridRelations

Add belongsToMany in HybridRelations

Feature request tracked in PHPORM-116

Hello, are there any updates on this thread because for my project using Laravel filament I need this.
Or are there any workaround ?

authors: GromNaN vahidei valodes

repo: mongodb/laravel-mongodb


text:
CLOUDP-114733: decrypt key using AWS KMS

Proposed changes
decrypt logs using AWS KMS

Jira ticket: CLOUDP-114733

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

My steps to test this

Create symmetric key in AWS

I basically followed https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html

To prepare test data I've started with a local key file

loglines.json

{"ts":{"$date":{"$numberLong":"1644232049921"}},"version":"0.0","compressionMode":"zstd","keyStoreIdentifier":{"provider":"local","filename":"localKey"},"encryptedKey":{"$binary":{"base64":"+yjPCaKKE1M8fZmPGzGHkyfHYxaw34okpavsHzpd8iPVx2+JjOhXwXw5E2FdI5Rcb5JgmcPUFRPISh/7Si1R/g==","subType":"0"}},"MAC":"qE9fUsGK0EuRrrCRAQAAAAAAAAAAAAAA","auditRecordType":"header"}
{"ts":{"$date":{"$numberLong":"1644232049922"}},"log":"1Lu4o8XVMM/Rg7GKAQAAAAEAAAAAAAAA/8tXQ36mEd90OaAOzCOSti7N5a2jr0B9ek48/uvyteG/zUJHyM16Hs3wMEhDqTQGBwGhWSHEqXh0/5Jbz6tXsYHhDTMr1BOsn1zaavZScx/CkO5+Hd8Vx+zeFPREtQTe1y+JngXSIroezeyV0/zF4YC4vpug+OZtrEQLNEgwT2bjaqUyaKDbmzCNetd2Ff/eFfMFzinbzKVgXAC7T4YmDuowqXommEXLIBiYh2u4VagwJKZRw5OGZjnvqwyVpSPgGqLxGKUoFigh3NgC6EuGi17VIs5BLRZOIw7+OfbPgQQiKzjCxCk="}
{"ts":{"$date":{"$numberLong":"1644232050645"}},"log":"gjn0BYabxQku84PTAQAAAAIAAAAAAAAAuTcMKIEGtlkPyGGqcj3mVOW0d+SUKGREXwicsBC5oDs+f4GkiNQmwXzpsassKTGLCS30xoEe/2NK/pBB7hB0mUmmoEVXCqgT28aztDXlkN5GeX0ECCYG4HoQyzyVdIi/SFF1Xa7jTLkYGdqwghDaMD/PzJVXcdhCckqPUn9CZKurMnsVZ7KiL8hpgNpQ8Q=="}
{"ts":{"$date":{"$numberLong":"1644232050645"}},"log":"8nCVKIkN1ebPXTIFAQAAAAMAAAAAAAAAMJ6H+8m76AZ0nOAHAWUmd7iZVHepDNpWyIBhTo4C5R7gBHFsPOlr4IETL/v6I+HSU4KBNnOFpoCA7KurmwNwQ7J8xdjrteCWB7WDIzP9cusu+4lsBdkhL/ExIJAaL/Rn/8Kq9482DyPtlxOldSUBP8QlyEJQ/iZ5W2fpgKdZtjCD4g+r6NPOgGjyrtr5bSqWts2f9Omth3r073HViNw="}

localKey

LxbM6ik6lgJjKEkugTdkRUoHCeyArNxg2xx7kGHl/io=

I've followed the steps to grab a local key decrypted

Local Key decrypted (lek.txt)

pnvb++3sbhxIJdfODOq5uIaUX8yxTuWS95VLgES30FM=

I've converted from base64 to binary

base64 -d lek.txt > lek.bin

finally re-encrypted the key into key.encrypted.txt

aws kms encrypt --key-id "<<key-id>>" --plaintext fileb://lek.bin --output text --region eu-west-1  --profile mms-scratch

Replaced header line (first line) in loglines.json with:

{"ts":{"$date":{"$numberLong":"1644232049921"}},"version":"0.0","compressionMode":"zstd","keyStoreIdentifier":{"provider":"aws","region":"<<region>>","endpoint":"km.<<region>>.amazonaws.com","key":"<<key arn>>"},"encryptedKey":{"$binary":{"base64":<<contents of lek.encrypted.txt>>,"subType":"0"}},"MAC":"qE9fUsGK0EuRrrCRAQAAAAAAAAAAAAAA","auditRecordType":"header"}

ran decryption

go run ./cmd/atlas/atlas.go logs decrypt --file ./loglines.json --awsAccessKey <accessKey> --awsSecretAccessKey <secretKey>

Go code LGTM

Go code LGTM

anything blocking your approval @johansteyn ?

authors: fmenezes johansteyn

repo: mongodb/mongodb-atlas-cli


text:
Storage autoScaling with diskSizeGB

By default autoScaling.diskGBEnabled  is enabled
I've tried to create cluster with instanceSizeName: M10, for this instanceSize suggested diskSizeGB is 10 GB, I want to create cluster with bigger disk:
providerSettings:
  instanceSizeName: M10
  providerName: GCP
  regionName: WESTERN_EUROPE
diskSizeGB: 12

Then I've resized disk manually to 14GB (I didn't have enough data to have autoScaling to trigger disk resize, but I think this scenario is comparable).
With the next changes of AtlasCluster CR (added providerBackupEnabled: false, but the actual change is not important here):
providerSettings:
  instanceSizeName: M10
  providerName: GCP
  regionName: WESTERN_EUROPE
diskSizeGB: 12
providerBackupEnabled: false

And this triggers the disk to be downscaled to 14GB -> 12GB as defined in spec
How diskSizeGB suppose to work with autoScaling.diskGBEnabled? Is it expected behavior? I would expect that diskSizeGB would be skipped after initial provisioning if autoScaling.diskGBEnabled is enabled

Discussed that it makes sense to check the same behavious with instance size and autoscaling, e.g:
Initial cluster provisioned as M30 - created CR
This CR has autoscaling, say M30 till M50
Then autoscaling makes it M40 (that we do manually)
Then we change CR, say disabling backups
What's the cluster size? We want it to be M40, but suspect it'll be M30 :(

This has been fixed.

authors: jasonmimick melifaro tetianakravchenko

repo: mongodb/mongodb-atlas-kubernetes


text:
🛑 Lobembe is down

In c30f95d, Lobembe (https://lobembe.mongulu.cm) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Lobembe is back up in aae05a7 after 18 minutes.

repo: mongulu-cm/uptime


text:
Update auth, dynamodb, s3, sqs to 2.16.96

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:dynamodb
software.amazon.awssdk:s3
software.amazon.awssdk:sqs

from 2.16.89 to 2.16.96.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, semver-patch

Superseded by #692.

repo: monix/monix-connect


text:
Added NativeScript swags

Org name: NativeScript
Description: Empower JavaScript
with native APIs. Liberate your development by using platform APIs directly without leaving your  of JavaScript.

Thank you @sshiv5768 !

repo: monizb/hacktoberfest-swag-list


text:
[tests][objc] Make sure variables are declared with the right type.

Otherwise we might not be able to call methods, because clang will look for any matching selector in any type it knows about, which results compiler errors like:
In module 'XCTest' imported from /work/Embeddinator-4000/tests/objc-cli/libmanaged/Tests/Tests.m:1:
In module 'UIKit' imported from /Applications/Xcode83.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework/Headers/XCUIElement.h:8:
/Applications/Xcode83.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.3.sdk/System/Library/Frameworks/UIKit.framework/Headers/UIAccelerometer.h:24:51: note: one possibility
@property(nonatomic,readonly) UIAccelerationValue x;
                                                  ^
In file included from /work/Embeddinator-4000/tests/objc-cli/libmanaged/Tests/Tests.m:3:
../build/test-framework-ios-temp-dir/iPhoneSimulator/managed.framework/Headers/managed.h:323:39: note: also found
@property (nonatomic, readonly) float x;
                                      ^
/work/Embeddinator-4000/tests/objc-cli/libmanaged/Tests/Tests.m:171:13: error: multiple methods named 'y' found with mismatched result, parameter type or attributes
        XCTAssert ([p2 y] == -2.0f, "y 2");
                   ^~~~~~

So by declaring the proper type for variables, clang doesn't have to guess.

Build and tests passed.

authors: monojenkins rolfbjarne


text:
[BUG] SKImageSourceHandler not found in 1.68.1 for iOS project

Description
SKImageSourceHandler not found in 1.68.1 for iOS projecct

Code

Expected Behavior
Should be found

Actual Behavior
Compile error

Basic Information

Version with issue:   1.68.1
Last known good version:  1.68.0
IDE:   Visual Studio / Visual Studio for Mac
Platform Target Frameworks: iOS

Android: NA
iOS:  13.2
Linux: NA
macOS:  NA
Tizen:  NA
tvOS:  NA
UWP:  NA
watchOS:  NA
Windows Classic: NA

Target Devices:  NA

Screenshots

Reproduction Link

Just checking that you have installed the SkiaSharp.Views.Forms NuGet into the iOS project? That type should be in that package.
I can see it there: https://www.fuget.org/packages/SkiaSharp.Views.Forms/1.68.1/lib/xamarin.ios/SkiaSharp.Views.Forms.dll/SkiaSharp.Views.Forms/SKImageImageSource

This is what we are getting on iOS project

@is it because of this change in nuspec?

It shouldn't be since iOS is .NET Standard 2.0 and the type should be in THAT nuget, not the dependencies.
Let me have a look at your repo.

I had a look and I see what is happening here. I moved the netstandard library into the ref folder in the nuget so that it won't actually run. But, it appears that the ref folder overrides ALL the platforms.
This typically is fine if the APIs are the same, but because we have more public types (such as SKImageSourceHandler) in the iOS (and the others) this doesn't work.

@pmahend1 Thanks for reporting this issue. I have pushed out a fix to the preview feed:
https://aka.ms/skiasharp-eap/index.json
Try version 1.68.1.1-preview.2 as that should have the fix. (there is a 1.68.2 series, but that is actually older because I decided to get .1.1 out first with this fix)

I checked ,it seem to have fixed the issue. @mattleibow Please let me know once you release into nuget org.

Awesome. Will do.

repo: mono/SkiaSharp


text:
issue from v1.0.2

Hi, since the release v1.0.2 we can't update our project anymore :

We had to force the 1.0.1. version
any idea ?

any idea ??

Hi @benoitmidon,
I think this issue is fix with the PR #32.
Can you try with the dev-master version of this plugin?
If it's good, we will be creating a release soon.
If not, can you give me your version of sylius?

authors: benoitmidon delyriand

repo: monsieurbiz/SyliusHomepagePlugin


text:
Updated README.md

Signed-off-by: Umanga Chapagain chapagainumanga@gmail.com

LGTM
If we are using oc lets mention in README at some stage that it works with OKD.

Fixed.

repo: monstorak/monstorak


text:
Validation in Basic example html does not work if removes $v from html and validators does not return to params

In your example https://jsfiddle.net/Frizi/b5v4faqf/ that belongs to a basic example in html, the results of $ params required and minLength are showing as "null" ....
The example shows:
"$params": {
"required": null,
"minLength": null
}
And should show
$params": {
"required": {
"type": "required"
},
"minLength": {
"type": "minLength",
"min": 5
}
}
I'm using the same example in an project, if the {{$ v}} is removed form the html validation does not work and "$params" are not displayed correctly , both in my project and jsfiddle.
How can I use a basic example that works as it should?

That's probably a bug in browser bundle. I'll have to create an e2e setup to automate testing for that. This should work as expected if you use npm package with webpack or any other bundler.

marking as duplicate of #103, please continue discussion there.

Wrong, this is actually still failing, but only in browser bundle.

Fixed in v0.4.3

I still get
"$params": {
"required": null,
"minLength": null
}

I am using it in electron

Same here, always null objects in $params.

+1
Using it in an electron environment and since switching the $params are always null.

authors: Frizi RipkensLar freccon guzmo hong-duc

repo: monterail/vuelidate


text:
Validations on collections with dynamic elements

What i have is basically a collection of objects. There are inputs with v-model associated to those objects' properties and a button for removing an object from the array. Think of this as a list of contacts.
What the issue refers to specifically is: that when an element is removed from the array (which it's done with splice) the validations of the items left, get messed up. It seems like it stops tracking the items and even after retrying with several other ways, it's still the same.
Some of the solutions that i've tried are:

Using v-bind:key in the template
Using $trackBy with a key consisting in a random generated pseudoId for each element in the array
Instead of using splice for removing the element, replacing the whole array
Using $reset
Combinations of all the options from above

I've noticed that even if i used the $trackBy option and  "printed" the $v object, the key for each object in the collection still corresponds to the item's index in the array.
I'll put some example code below.
Forgive me if there's something wrong with it, i'm writing it from memory, but i hope you get the point

    <input type="text" v-model="person.firstName" />
    <input type="text" v-model="person.email" />
    Email is required
    <button v-on:click="remove(index)>Remove</button>

{
    validations : {
        people : {
            $each : {
                email :  {
                    required : function(email, person) {
                          return (person.firstName && email) || email;
                    }
                }
            }
        }
    },
    data : {
        people : [{     // initialize as empty for showing the empty inputs
             firstName : "",
             email : ""
        }]
    },
    methods : {
        add : function() {
            this.people.add({
                 firstName : "",
                 email : ""
            })
        },

        remove : function(index) {
            if (this.people.length === 1 ) {
                this.people.splice(0, 1, {
                     firstName : "",
                     email : ""
                });
            } else {
                this.people.splice(index, 1);
            }
        }
    }
}

This seems like a bug to me, I will need to test it more, but I think I might recognise it already.
It seems like you are referencing the object directly on array, but through the second parameter. It might be related to #51. While it is a bug (which might be fixed already, to be released), you probably can avoid it by simplifying your logic.
$each: {
    email :  {
        required : function(email, person) {
            return (person.firstName && email) || email;
        }
    }
}

This validator can be simplified to not reference multiple values at once. (A and B) or B means simply B.
$each: {
    email :  { required }
}

I've noticed that even if i used the $trackBy option and "printed" the $v object, the key for each object in the collection still corresponds to the item's index in the array.

That's expected. $trackBy influences the validation state tracking, but original keys are still used as indices on validation object.

Hello @Frizi, thank you for the answer and for the validation advice, but unfortunately it's just part of what the issue is.
The real problem i think it's related to what you said previously about keeping track of changes in arrays and not recomputing the $each validator. At the end, the items left in the array aren't being validated.
Can you let me know if this could be fixed or if it's a known issue/limitation?

Please check it against current master. It contains said fix. I'm only waiting for $params feature to be finally finished and merged, then I'll do the release. If there is still a bug, it can also be fixed before that.

Checked with master. It's working now, but it needed a little bit of workaround.
What i did was generating a pseudo id property to each element and using $trackBy with that id. I said i tried that before and didn't work, but now it's working good
@Frizi Thanks a lot! You may close this issue if there aren't more questions/suggestions :wink:

@sesegura Could you also try without any $trackBy? Default is to track by the key/array index, it should still work.

Already tried but didn't work either.
Also tried with v-bind:key="item.pseudoId and no $trackBy but no results.

Can you post the working example? It's a bug if it doesn't work by default.

This is kind of the setup that is currently working for me:

    <input type="textfield" name="name" v-model="item.name">
    Error
    <button v-on:click="remove(index)">Remove</button>

<button v-on:click="add">Add</button>

{
  validations : {
    items : {
       $each : {
          $trackBy : 'pseudoId',
          name : VuelidateValidations.required
       }
    }
  },
  methods : {
      add : function() {
          this.items.push({
              pseudoId : Math.random(),  // the function i'm using is actually more elaborated than this
              name : ''
          });
      },
      remove : function(index) {
          if (this.items.length === 1) {
              this.items.splice(0, 1, {
                  pseudoId : Math.random(),
                  name : ''
              });
          } else {
              this.items.splice(index, 1);
          }
      }
  }
}

          name : VuelidateValidations.required

This is odd. What you ment is probably
name: {
  required: VuelidateValidations.required
}

What you did should make the actual object required, which is always true. Actually weird it works, I have to test it.

Sorry, i wrote the previous code example from memory, the actual example has that structure with required being inside the name object.
I'll edit my previous comment for making that fix in the example.

@sesegura Thanks, that makes a lot of sense now 😄

I have a similar issue.
I use an array hold a list of choices of a question. Each choice have an input field with v-model bind to the label property of the choice in the array. And in the validation, the label is required.
I put a placeholder choice with empty label in the array for initial rendering. And then when editing an existing question which has a list of choices, I use splice(0) to clean up the placeholder choice and then use push() to add the existing choices.
The validation of the first choice always fails, even after I edit the choice label. And it is kind of fixed by printing the $v object.
Here is the code.

  <input type="text" class="form-control input-sm label-input" v-model="choice.label">

Blank choice is not allowed

validations: {
    question: {
      title: {
        required
      },
      type: {
        required
      },
      choices: {
        required,
        $each: {
          label: {
            required
          }
        }
      }
    }
  }

/* This is the part that I add the placeholder choice */
this.question.choices.push({id: 0, label: '', sortOrder: 1})

The hack I use is print out the first choice in the $v object.

{{ $v.question.choices.$each[0] }}

@sesegura @jamesjieye Please check your issues against latest version.

Bug fixed for me :)

@Frizi I think it will be great to add $trackBy to the collection example in the docs because for now, it's pretty hard to find it.
Actually, I found it in this issue, but not in the docs :)

Sorry folks , how would you validate dynamic select inside datatable
https://user-images.githubusercontent.com/47603281/52724826-74033080-2f86-11e9-9dd5-ea9db4dbfea2.png

Hi folks, im trying to achieve somthing similar but with a select inside a datatable ,but dont know how ,i want to click on validate button to validate all selects like this below:

authors: Frizi ZatchMichael chymz jamesjieye sesegura shrpne


text:
application template chooser (ATC) wizard's page

Intention

I'm submitting a design discussion request
Summary
This article proposes the separation of two complex custom controls - application template chooser (aka ATC), indicated by the vertical arrow and monterey package chooser (aka MPC) indicated by the horizontal arrow, shown on the screenshot below

from the first page of the Monterey project creation wizard. This way the first page will only contain the application template chooser

@JeroenVinke proposed this idea as a start:

I like it a lot and am continuing from here, with the following reasoning:

each category of templates should be selected by its Logo (small tile)

many of our existing templates should be collected together and made accessible via GitHub tile

selected category of template should provide easy definition of all of its properties.

when finishing with the template chooser, the wizard proceeds to the next page, with the clear indication of the context chosen so far.

Application template chooser (ATC) custom element
Here is the screenshot of the ATC (outside of any context, showing the situation where the user selected the GitHub "mini-tile"

Note that the "mini tiles" area should be extensible (just like the "regular tiles" are via App launcher tool. Each mini tile defines all information about its template.
We should maintain the registry of templates, of course 😏

Still do be defined

Equivalents of the Image 1 above for all other template types, together with all required attributes for each type.
Wizard page following the page with ATC element

Questions on 12/3/2016
Look at the Image 1 in the above section and observe the its similarity between the Monterey's tiles (that live in the main page. The thought to reuse them in the context of this newly added page where i already made some clumsy steps that are not finished comes to mind.
On the second thought the use case for this scenario is different from the one that takes place on the main page as the tiles that represent the template type need to coexist with "real tiles", there is always the danger of missing some side-effects - and the original tiles were not really designed for such reuse.
My above defined requirement

Note: "mini tiles" area should be extensible (just like the "regular tiles" are via App launcher tool).

Each mini tile defines all information about its template is a key extensibility feature, so I do not want to give up on it. So, it seems that I just took a byte of a tough apple and expect your recommendation to hack some basic "local infrastructure" that would render and be able to invoke a set of tiles like this one:

Love this!

Note: we need to limit the search to find only the Monterey application templates. This means that we should maintain the registry of templates - where each registry entry points to the relevant GitHub repository.

Do we? I would like Monterey to be able to install and run any application (which is an unrealistic goal of me, but still). Therefore, you should be able to select any template through monterey (without leaving Monterey itself).
There are a few ways to accomplish this:

Add Git integration in Monterey. @Thanood  created https://github.com/monterey-framework/monterey/issues/382 with the proposal to use GitKraken, but I would like Monterey to talk to git directly, so the user does not need to install gitkraken. @vegarringdal mentioned http://www.nodegit.org/ which I like a lot.
In sourcetree you can do this:

Here you see a list of all your repositories (and the repositories of your organizations). You can simply select one and clone it. Cloning a project of mine is something I do way more often than I download a project of someone else. So if we can add this to Monterey then that would be pretty useful I think.
Adding Git support will be more work but since our download count has stagnated, I am fine with taking more time to do it the right way.

Allow user to search GitHub from within Monterey

Here the user can search for GitHub repositories, and select one. Of this repository the user can choose a subfolder. Because the user can now search for GitHub repositories, it is not needed to paste in a Github URL anymore
The user can now also select templates like https://github.com/preboot/angular-webpack.

Pre-selected templates
Since we also want to hand-pick (and highlight) some templates, we can do this:

Open issue: it is not obvious whether the "mini-tile" should be a subclass of the "regular tile" or an independent component. I would expect the answer to that from Jeroen, of course

Instead of "mini-tile" we could call them "radio-tiles". I can probably create a reusable custom element for this.

Comments to the previous post

I would like Monterey to be able to install and run any application (which is an unrealistic goal of me, but still). Therefore, you should be able to select any template through monterey (without leaving Monterey itself).

I think the same - just did not explain the concept of the registry of templates

The most general case is certainly "open access" to GitHub, where NodeGit will be a great tool to use. Nevertheless, I would like to improve my original concept of the Application Template Chooser (ATC)

OK, let's give it a shot 👍

I fully agree with Git integration, precisely in the sense you indicate here -- bit that has nothing (or very little) to do with ACT component.

Git integration may be the wrong name. What I would like to do is show the user a list of their (and their organizations') repositories, so they can select one. This is done through the GitHub API as well (which I mistakenly called "Git integration"). That is the job of the ATC, to search for (and select) a template. This can be done through a variety of sources:

Manually searching for a repository on GitHub (what you have designed in the screen design)
Selecting one of your own (or your organizations') repositories (also done through GitHub API)
Selecting a template out of our registry

Git integration (through NodeGit) can happen later, I just want Monterey to show me my repositories, which I use a ton more than random GitHub repositories

Git integration (through NodeGit) can happen later, I just want Monterey to show me my repositories, which I use a ton more than random GitHub repositories.

I think that we are fine now.

authors: JeroenVinke adriatic

repo: monterey-framework/monterey


text:
MOBILE-1489 resource: Download progress indication

MOBILE-1489 resource: Download progress indication
This solves issue MOBILE-1489.

Hello,
thanks for working on this, I've submitted it for peer-review via the https://tracker.moodle.org/browse/MOBILE-1489 issue.
You should subscribe (watch) this issue in the tracker to get further notifications

authors: jleyva martinmine


text:
Unable to find an executable binary for yarn, expected file ~/.proto/tools/yarn/1.22.20/bin/yarn.js

What version?
The version bundled with moon 1.11.1
Which command?
No response
What happened?
It appears that the structure of the archive downloaded for yarn v1 changed in the just released yarn 1.22.20 such that there is a package folder in the ~/.proto/tools/yarn/1.22.20 directory this causes proto to be unable to find the specific tool path ~/.proto/tools/yarn/1.22.20/bin/yarn.js (because it exists at ~/.proto/tools/yarn/1.22.20/package/bin/yarn.js). This is specifically a problem with the node_depman plugin but I can't find the source or a repository to report the issue there.
There also doesn't appear to be a way to tell proto to use a different version of yarn v1 when the toolchain specifies yarn 2+
I don't expect this to be limited to a specific version of proto because it has to do with how to tool version is unpacked.
Any logs?
No response
Operating system?
MacOS
Architecture?
Arm64

Annoying, fix here: https://github.com/moonrepo/node-plugin/pull/20

appreciate this report and the quick fix @milesj, our CI started failing as well: https://github.com/gallery-so/gallery/actions/runs/6869327266/job/18681866538?pr=2083
should we expect this to be autofixed once the update is released?

It should for older versions of moon/proto. Latest versions use fixed versions now.

@milesj still seeing issues despite upgrading moon + proto, moving convo to discord: https://discord.com/channels/974160221452763146/1174101530748669952/1174101530748669952

https://github.com/moonrepo/node-plugin/releases/tag/v0.5.1

authors: Robinnnnn bryanjswift milesj

repo: moonrepo/proto


text:
manage several opticalFlow regions dynamically

Hello @moostrik ,
I'm wondering If I can use your addon to read several areas at same time..
I can handle serveral static ftAverageFlow areas in the way you setup the system.
flows.push_back(&temporalAverageFlowItem1);
flows.push_back(&temporalAverageFlowItem2);
...
but if I want to have several dynamic areas : create and destroy them dynamically, I can not pass there just a pointer of something I'm not saving. Right? How I could do this?
Another way I'm thinking about is just setup one ( full size ), and try to read pixel by pixel the OpticalFlow restults. Any tips how to do read several small regions or by pixel of a ftOpticalFlow?

this is not an issue.
You could play around with the region of interest (setRoi()) in the ftAverageFlow

Sorry that I set this as an issue. I do not know where to ask you this. Where else I can write this feature?
Do you mean I can just set several ROI and read them as different results all in one frame? That would be so great!
My best, would be to draw all the ROI's at same time so then drawVisualizer for all of them.  That, I got it only when adding static ftAverageFlow items into the system.
Ok, I've just tried what you suggested. But did not work for me. Only one is working at time.
I did this:
//Update
	opticalFlow.update();
	averageFlow.setInput(opticalFlow.getVelocity());

//Draw
	if (toggleAverageDraw) {
		ofEnableBlendMode(OF_BLENDMODE_ALPHA);
		for (int i = 0; i < myAvgFlowRois.size(); i++) {
			averageFlow.setRoi(myAvgFlowRois[i]);
			averageFlow.update();
			averageFlow.drawInput(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);
			averageFlow.drawVisualizer(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);
		}
	}

I guess DrawVisualizer will not be possible, I will have to do my own I I want it.
But, yes you were right. I can get different averageFlow results on the fly. I'm working on it.  I almost there: now I'm drawing the different results, but one item switched. If I have 3 ROIS -> 0 is 1. 1 is 2  and 2 is 0.
I you do not mind I will post it here:

//Now all in Draw:
	if (toggleAverageDraw) {
		ofEnableBlendMode(OF_BLENDMODE_ALPHA);
		for (int i = 0; i < myAvgFlowRois.size(); i++) {
			averageFlow.setInput(opticalFlow.getVelocity());
			averageFlow.update();

			averageFlow.setRoi(myAvgFlowRois[i]);
			averageFlow.drawInput(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);
			averageFlow.drawVisualizer(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);

			ofDrawBitmapStringHighlight("getStDevMagnitude -> " + ofToString(averageFlow.getStDevMagnitude(), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight-20);
			ofDrawBitmapStringHighlight("getComponent 0 -> " + ofToString(averageFlow.getComponent(0), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight - 60);
			ofDrawBitmapStringHighlight("getComponent 1 -> " + ofToString(averageFlow.getComponent(1), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight - 40);
		}
	}

I did this small fix to have them in order.
		for (int i = 0; i < myAvgFlowRois.size(); i++) {

			averageFlow.setInput(opticalFlow.getVelocity());
			averageFlow.setRoi(myAvgFlowRois[i]);
		//second try required to draw and give results over actual averageFlow
			averageFlow.setInput(opticalFlow.getVelocity());
			averageFlow.setRoi(myAvgFlowRois[i]);

			averageFlow.update();

			averageFlow.drawInput(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);
			averageFlow.drawVisualizer(myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight, myAvgFlowRois[i].width*densityWidth, myAvgFlowRois[i].height*densityHeight);

			ofDrawBitmapStringHighlight("getStDevMagnitude -> " + ofToString(averageFlow.getStDevMagnitude(), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight - 20);
			ofDrawBitmapStringHighlight("getComponent 0 -> " + ofToString(averageFlow.getComponent(0), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight - 60);
			ofDrawBitmapStringHighlight("getComponent 1 -> " + ofToString(averageFlow.getComponent(1), 3), myAvgFlowRois[i].x*densityWidth, myAvgFlowRois[i].y*densityHeight - 40);
		}

But when I'm using more than 5 ROIs FPS is going down dramatically.
There is a bottle neck here, aparently repeat N times -> averageFlow.update();

Reading a texture from videoRAM to normalRAM is a very time consuming process.
For your purpose it might be more sensible to first read the whole image to pixels and analyze the subsections second.

That make sense!
My first approach -> Use ofxCvFloatImage images to read inputFbo, then apply update (Average Calcs) for-each ROI and save average calcs of each ROI. Do you think is ok?
I've already tried, but I've got a weird error after update floatPixelData convertGrayToFloat( IplImage* grayImg, IplImage* floatImg )  with my new Opencv Image.
Do you thing there another easier way to do it?
Probably not necessary to add opencvn addon, but It's a way to handle that image types and apply Rois easy.

authors: carlesgutierrez moostrik

repo: moostrik/ofxFlowTools


text:
fix: remove logging of search queries

Fixes: https://github.com/moov-io/watchman/issues/488

Codecov Report

Merging #489 (51645e8) into master (25f51df) will increase coverage by 0.04%.
The diff coverage is 0.00%.

:exclamation: Current head 51645e8 differs from pull request most recent head 5e85191. Consider uploading reports for the commit 5e85191 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff            @@
##           master    #489      +/-   ##
=========================================
+ Coverage    8.20%   8.25%   +0.04%
=========================================
  Files          44      44
  Lines        3509    3490      -19
=========================================
  Hits          288     288
+ Misses       3197    3178      -19
  Partials       24      24

authors: adamdecaf codecov-commenter

repo: moov-io/watchman


text:
Table has "Created at" column twice

The Jobs table has the "Created at" column twice.
I think the first column should be "Started at"??

Will be fixed in mooxphp/jobs Version 2.0.1

authors: Jacobtims adrolli

repo: mooxphp/jobs


text:
Does it work with 1.0.0-preview3-32184 .NET core verison?

Can you let me know.
Thank you so much.

OK. thank you very much. I have just downgrade in server side for working with current your client version

Yes, you have to do this for now. I will update this issue once I the code is fixed. Also FYI the installation instructions are now not correct because I moved to Cocoapods for the WebSocket library. I will update them soon as well.

Thanks. Can you let me know how to connect multi hubs to server?

Can you let me know how to connect to multi hubs on server?

Thanks.

I made a few changes and the latest version should now work with preview2 except #10 which should not cause issues.

repo: moozzyk/SignalR-Client-Swift


text:
NDK r16b marked as unsupported during the build

I tried to build it up using latest available version of official ndk (16.1), but it ended up with this message:
Building boost version: 1.65.1 Detected Android NDK version 16.1 Undefined or not supported Android NDK version: 16.1
similar thing happened with r10e version from ndk archive. unfortunately i didn't found older versions on official website.
Linux Mint 18.2 x64

Take a look at build-android.sh line 285
"16.0")
   TOOLCHAIN=${TOOLCHAIN:-llvm}
   CXXPATH=$AndroidNDKRoot/toolchains/${TOOLCHAIN}/prebuilt/${PlatformOS}-x86_64/bin/clang++
   TOOLSET=clang
   ;;

It looks like 16.0 is the latest supported version. Try changing line 285
from "16.0")  to  "16.1")

Hello Fjord ,
You can find the older NDK version in below link,
[(https://developer.android.com/ndk/downloads/older_releases.html)]
I am using NDK version r16b . It is working fine.

authors: Kumarasamy aquawicket fj0rd

repo: moritz-wundke/Boost-for-Android


text:
HashMap toArray() does not use $preserveKeys by default

While $preserveKeys = FALSE is default everywhere, wouldn't it be better to break the consistency for Maps? Or better yet, preserve keys by default? It feels like it should be more general use case.
From the user standpoint, I would rather use self describing $map->toArray(). The additional boolean argument is not self explanatory (on first sight, without checking the function declaration). And while $map->toArray($withKeys = TRUE); is readable, it does not really cut the mustard as it's waaaay too long.

The one function that comes to mind for me on this topic from PHP core is iterator_to_array. It has a preserve keys parameter ($use_keys) which is optional and defaults to true.
Only in cases where I use it and where I know the keys are standing in the way I can switch it to off by setting it.
I think this follows the same principle as outlined by @morrisonlevi in the last comment.
So perhaps this is already fixed by switching to such a default?

authors: Mikulas hakre

repo: morrisonlevi/Ardent


text:
Fix Local World Size

Make LOCAL_WORLD_SIZE set in pytest to fix non-dist tests

same comment as composer pr

fixed!

authors: dakinggg rishab-partha

repo: mosaicml/llm-foundry


text:
MDSWriter throws an error when writing to a local directory using Python 3.8

Environment
Python 3.8 (Kubeflow notebook)

OS: [Ubuntu 20.04]
Hardware (GPU, or instance type): N/A

To reproduce
Steps to reproduce the behavior:
Script (copied from README):
$ cat write_data.py
import numpy as np
from PIL import Image
from streaming import MDSWriter

# Local or remote directory in which to store the compressed output files
data_dir = '/home/jovyan/tmp'

# A dictionary mapping input fields to their data types
columns = {
    'image': 'jpeg',
    'class': 'int'
}

# Shard compression, if any
compression = 'zstd'

# Save the samples as shards using MDSWriter
with MDSWriter(out=data_dir, columns=columns, compression=compression) as out:
    for i in range(10000):
        sample = {
            'image': Image.fromarray(np.random.randint(0, 256, (32, 32, 3), np.uint8)),
            'class': np.random.randint(10),
        }
        out.write(sample)

python3 write_data.py

Expected behavior
I expect the data to be written successful to the local directory ./tmp without any issues. I suspect this is an issue since the feature cancel_futures is only Python 3.9+. See comment on PR.
Additional context
Error trace:
Traceback (most recent call last):
  File "write_data.py", line 24, in <module>
    out.write(sample)
  File "/home/jovyan/.local/lib/python3.8/site-packages/streaming/base/format/base/writer.py", line 265, in __exit__
    self.finish()
  File "/home/jovyan/.local/lib/python3.8/site-packages/streaming/base/format/base/writer.py", line 244, in finish
    self.executor.shutdown(wait=True, cancel_futures=False)
TypeError: shutdown() got an unexpected keyword argument 'cancel_futures'

Hi @coders1122 , thanks for raising the issue. As you have mentioned, parameter cancel_futures is being added in Python 3.9 or later. Since, we are keeping cancel_futures as False anyhow which is also a default parameter in shutdown() method, we can remove the cancel_futures parameter from self.executor.shutdown(wait=True, cancel_futures=False). Do you mind raising a PR with a fix since you have found out the issue? If you have a limited bandwidth, then I can also raise a PR. Thanks!

I'm having troubles using multiple accounts (personal, corp) for Github on the same machine. Since it's quite trivial, mind setting the PR out for this instance?
Thank you for the quick response!

The above PR has been merged. Closing this issue. Thank you for reporting it.

repo: mosaicml/streaming