text:
undefined symbol when importing PyTorch Lightning after installing stable baselines3

Bug description
I am not able to use or import PyTorch Lightning after installing Stable Baselines3.
I get the error:
ImportError: /home/alballns/miniconda3/envs/kdn_env/lib/python3.9/site-packages/torchtext/_torchtext.so: undefined symbol: _ZNK3c104Type14isSubtypeOfExtERKSt10shared_ptrIS0_EPSo
I tried to re-install pytorch_lightning, PyTorch, torchtext, and made sure their versions are all compatible.
But still couldn't fix the issue.
Please help! Thanks!
How to reproduce the bug
No response
Error messages and logs

here is a part of the track trace:

`----> 8 import pytorch_lightning as pl

File ~/miniconda3/envs/kdn_env/lib/python3.9/site-packages/pytorch_lightning/__init__.py:20, in <module>
     17 _PACKAGE_ROOT = os.path.dirname(__file__)
     18 _PROJECT_ROOT = os.path.dirname(_PACKAGE_ROOT)
---> 20 from pytorch_lightning.callbacks import Callback  # noqa: E402

File ~/miniconda3/envs/kdn_env/lib/python3.9/site-packages/pytorch_lightning/callbacks/__init__.py:14, in <module>
      1 # Copyright The PyTorch Lightning team.
      2 #
      3 # Licensed under the Apache License, Version 2.0 (the "License");
   (...)
     12 # See the License for the specific language governing permissions and
     13 # limitations under the License.
---> 14 from pytorch_lightning.callbacks.base import Callback

[ ... many lines here ... ]

File ~/miniconda3/envs/kdn_env/lib/python3.9/site-packages/torchtext/vocab/vocab_factory.py:4, in <module>
      2 from typing import Dict, Iterable, Optional, List
      3 from collections import Counter, OrderedDict
----> 4 from torchtext._torchtext import (
      5     Vocab as VocabPybind,
      6 )
      9 def vocab(ordered_dict: Dict, min_freq: int = 1) -> Vocab:
     10     r"""Factory method for creating a vocab object which maps tokens to indices.
     11
     12     Note that the ordering in which key value pairs were inserted in the `ordered_dict` will be respected when building the vocab.
   (...)
     42         >>> v2['out of vocab'] is v2[unk_token] #prints True
     43     """

ImportError: /home/alballns/miniconda3/envs/kdn_env/lib/python3.9/site-packages/torchtext/_torchtext.so: undefined symbol: _ZNK3c104Type14isSubtypeOfExtERKSt10shared_ptrIS0_EPSo`

Environment

#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version (e.g., 1.5.0):
#- Lightning App Version (e.g., 0.5.2):
#- PyTorch Version (e.g., 1.10):
#- Python version (e.g., 3.9):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):
#- Running environment of LightningApp (e.g. local, cloud):

More info
No response

Hi, @n-balla, can you please share with us the environment you use so that we can help you debug further? The easiest way to do so would be to run python requirements/collect_env_details.py
Thanks a lot!

Thank you for your reply!
Here is the environment details:
`* CUDA:
- GPU:
- NVIDIA Quadro K6000
- available:         True
- version:           10.2

Lightning:

pytorch-lightning: 1.5.10
torch:             1.8.0
torchaudio:        0.10.2
torchmetrics:      0.7.2
torchtext:         0.9.0
torchvision:       0.11.3

Packages:

absl-py:           1.0.0
aiohttp:           3.8.1
aiosignal:         1.2.0
antlr4-python3-runtime: 4.8
argon2-cffi:       21.3.0
argon2-cffi-bindings: 21.2.0
asttokens:         2.0.5
async-timeout:     4.0.2
attrs:             21.4.0
backcall:          0.2.0
beautifulsoup4:    4.11.1
bleach:            5.0.0
blinker:           1.4
brotlipy:          0.7.0
cachetools:        5.0.0
certifi:           2022.5.18.1
cffi:              1.15.0
charset-normalizer: 2.0.12
click:             8.1.3
cloudpickle:       2.1.0
colorama:          0.4.4
cryptography:      37.0.2
cycler:            0.11.0
cytoolz:           0.11.2
dask:              2022.5.0
debugpy:           1.6.0
decorator:         5.1.1
defusedxml:        0.7.1
docker-pycreds:    0.4.0
entrypoints:       0.4
executing:         0.8.3
fastjsonschema:    2.15.3
fonttools:         4.33.3
frozenlist:        1.3.0
fsspec:            2022.5.0
future:            0.18.2
gitdb:             4.0.9
gitpython:         3.1.27
google-auth:       2.6.6
google-auth-oauthlib: 0.4.6
grpcio:            1.46.3
gym:               0.21.0
gym-notices:       0.0.8
hydra-core:        1.1.1
idna:              3.3
imagecodecs:       2021.11.20
imageio:           2.15.0
imgaug:            0.4.0
importlib-metadata: 4.11.4
ipykernel:         6.13.1
ipython:           8.4.0
ipython-genutils:  0.2.0
ipywidgets:        7.7.0
jedi:              0.18.1
jinja2:            3.1.2
joblib:            1.1.0
jsonschema:        4.6.0
jupyter:           1.0.0
jupyter-client:    7.3.4
jupyter-console:   6.4.3
jupyter-core:      4.10.0
jupyterlab-pygments: 0.2.2
jupyterlab-widgets: 1.1.0
kiwisolver:        1.4.2
locket:            1.0.0
markdown:          3.3.7
markupsafe:        2.1.1
matplotlib:        3.5.1
matplotlib-inline: 0.1.3
mistune:           0.8.4
multidict:         6.0.2
munkres:           1.1.4
nbclient:          0.6.4
nbconvert:         6.5.0
nbformat:          5.4.0
nest-asyncio:      1.5.5
networkx:          2.8.2
notebook:          6.4.12
numpy:             1.22.2
oauthlib:          3.2.0
omegaconf:         2.1.1
packaging:         21.3
pandas:            1.4.1
pandocfilters:     1.5.0
parso:             0.8.3
partd:             1.2.0
pathtools:         0.1.2
pexpect:           4.8.0
pickleshare:       0.7.5
pillow:            9.0.1
pip:               22.0.3
prometheus-client: 0.14.1
promise:           2.3
prompt-toolkit:    3.0.29
protobuf:          3.19.4
psutil:            5.9.0
ptyprocess:        0.7.0
pure-eval:         0.2.2
pyasn1:            0.4.8
pyasn1-modules:    0.2.7
pycparser:         2.21
pydeprecate:       0.3.1
pygments:          2.12.0
pyjwt:             2.4.0
pyopenssl:         22.0.0
pyparsing:         3.0.9
pyqt5:             5.12.3
pyqt5-sip:         4.19.18
pyqtchart:         5.12
pyqtwebengine:     5.12.1
pyrsistent:        0.18.1
pysocks:           1.7.1
python-dateutil:   2.8.2
pytorch-lightning: 1.5.10
pytz:              2022.1
pyu2f:             0.1.5
pywavelets:        1.3.0
pyyaml:            6.0
pyzmq:             23.1.0
qtconsole:         5.3.1
qtpy:              2.1.0
requests:          2.27.1
requests-oauthlib: 1.3.1
rsa:               4.8
scikit-image:      0.19.1
scikit-learn:      1.0.2
scipy:             1.8.0
send2trash:        1.8.0
sentry-sdk:        1.5.12
setuptools:        59.5.0
shapely:           1.8.2
shortuuid:         1.0.9
six:               1.16.0
smmap:             5.0.0
soupsieve:         2.3.2.post1
stable-baselines3: 1.6.1
stack-data:        0.2.0
tensorboard:       2.8.0
tensorboard-data-server: 0.6.0
tensorboard-plugin-wit: 1.8.1
termcolor:         1.1.0
terminado:         0.13.1
testpath:          0.5.0
threadpoolctl:     3.1.0
tifffile:          2022.2.9
tinycss2:          1.1.1
tomli:             2.0.1
toolz:             0.11.2
torch:             1.8.0
torchaudio:        0.10.2
torchmetrics:      0.7.2
torchtext:         0.9.0
torchvision:       0.11.3
tornado:           6.1
tqdm:              4.62.3
traitlets:         5.2.1.post0
typing-extensions: 4.2.0
unicodedata2:      14.0.0
urllib3:           1.26.9
wandb:             0.12.10
wcwidth:           0.2.5
webencodings:      0.5.1
werkzeug:          2.1.2
wheel:             0.37.1
widgetsnbextension: 3.6.0
yarl:              1.7.2
yaspin:            2.1.0
zipp:              3.8.0

System:

OS:                Linux
architecture:

64bit
ELF

processor:         x86_64
python:            3.9.10
version:           #1 SMP Thu Apr 8 19:51:47 UTC 2021
`

I tried several torch/ torchtext versions trying to solve the issue, but the problem couldn't be solved yet.

@n-balla, it looks, like your environment is quite broken. stable-baselines3==1.6.1 wants to have torch>=1.11, I know, that torchvision version are quite tightly linked to particular torch version and I expect it's the same for torchtext, plus it seems your versions of torch and torchtext are quite old (and I think torch 1.8.0 is unsupported by now, but I'm not 100% sure about it). It appears to me, you got to that point by "reusing" an old environment, to which you installed a new package (in this case probably stable-baselines3 since that is quite recent), while not specifying --upgrade flag for pip.
In order to check whether your environment is healthy, you can run pip check.
However, if you don't need a specific of any of these libraries, I just tried to run pip install torchtext stable-baselines3 pytorch-lightning --extra-index-url https://download.pytorch.org/whl/cu116 in a fresh, python 3.9.14 environment and everything seems to be wokring as expected. I have a newer version of CUDA, but that seems to be the only difference.
Please, let me know if this helps!

My environment details:

* CUDA:
	- GPU:
		- NVIDIA T1200 Laptop GPU
	- available:         True
	- version:           11.6
* Lightning:
	- pytorch-lightning: 1.7.7
	- torch:             1.12.1+cu116
	- torchmetrics:      0.10.0
	- torchtext:         0.13.1
* Packages:
	- absl-py:           1.2.0
	- aiohttp:           3.8.3
	- aiosignal:         1.2.0
	- async-timeout:     4.0.2
	- attrs:             22.1.0
	- cachetools:        5.2.0
	- certifi:           2022.9.24
	- charset-normalizer: 2.1.1
	- cloudpickle:       2.2.0
	- contourpy:         1.0.5
	- cycler:            0.11.0
	- fonttools:         4.37.4
	- frozenlist:        1.3.1
	- fsspec:            2022.8.2
	- google-auth:       2.12.0
	- google-auth-oauthlib: 0.4.6
	- grpcio:            1.49.1
	- gym:               0.21.0
	- idna:              3.4
	- importlib-metadata: 4.13.0
	- kiwisolver:        1.4.4
	- markdown:          3.4.1
	- markupsafe:        2.1.1
	- matplotlib:        3.6.1
	- multidict:         6.0.2
	- numpy:             1.23.3
	- oauthlib:          3.2.1
	- packaging:         21.3
	- pandas:            1.5.0
	- pillow:            9.2.0
	- pip:               22.0.4
	- protobuf:          3.19.6
	- pyasn1:            0.4.8
	- pyasn1-modules:    0.2.8
	- pydeprecate:       0.3.2
	- pyparsing:         3.0.9
	- python-dateutil:   2.8.2
	- pytorch-lightning: 1.7.7
	- pytz:              2022.4
	- pyyaml:            6.0
	- requests:          2.28.1
	- requests-oauthlib: 1.3.1
	- rsa:               4.9
	- setuptools:        58.1.0
	- six:               1.16.0
	- stable-baselines3: 1.6.2
	- tensorboard:       2.10.1
	- tensorboard-data-server: 0.6.1
	- tensorboard-plugin-wit: 1.8.1
	- torch:             1.12.1+cu116
	- torchmetrics:      0.10.0
	- torchtext:         0.13.1
	- tqdm:              4.64.1
	- typing-extensions: 4.4.0
	- urllib3:           1.26.12
	- werkzeug:          2.2.2
	- wheel:             0.37.1
	- yarl:              1.8.1
	- zipp:              3.9.0
* System:
	- OS:                Linux
	- architecture:
		- 64bit
		- ELF
	- processor:
	- python:            3.9.13
	- version:           #1 ZEN SMP PREEMPT_DYNAMIC Tue, 04 Oct 2022 14:37:01 +0000

Thank you @otaj !
This was only one of the environments I tried.
Here is another one, with a newer torch and torchtext, and still gave the exact same error:
`* CUDA:
- GPU:
- Tesla V100-SXM2-32GB
- available:         True
- version:           10.2

Lightning:

pytorch-lightning: 1.7.7
torch:             1.12.1
torchmetrics:      0.10.0
torchtext:         0.13.1

Packages:

absl-py:           1.2.0
aiohttp:           3.8.3
aiosignal:         1.2.0
ale-py:            0.7.4
argon2-cffi:       21.3.0
argon2-cffi-bindings: 21.2.0
asttokens:         2.0.5
async-timeout:     4.0.2
attrs:             22.1.0
autorom:           0.4.2
autorom.accept-rom-license: 0.4.2
backcall:          0.2.0
beautifulsoup4:    4.11.1
bleach:            5.0.0
cachetools:        5.2.0
certifi:           2022.9.24
charset-normalizer: 2.1.1
click:             8.1.3
cloudpickle:       2.2.0
commonmark:        0.9.1
contourpy:         1.0.5
cycler:            0.11.0
debugpy:           1.6.0
decorator:         5.1.1
defusedxml:        0.7.1
entrypoints:       0.4
executing:         0.8.3
fastjsonschema:    2.15.3
fonttools:         4.37.4
frozenlist:        1.3.1
fsspec:            2022.8.2
google-auth:       2.12.0
google-auth-oauthlib: 0.4.6
grpcio:            1.49.1
gym:               0.21.0
gym-notices:       0.0.8
idna:              3.4
importlib-metadata: 4.13.0
importlib-resources: 5.10.0
ipykernel:         6.13.1
ipython:           8.4.0
ipython-genutils:  0.2.0
ipywidgets:        7.7.0
jedi:              0.18.1
jinja2:            3.1.2
jsonschema:        4.6.0
jupyter:           1.0.0
jupyter-client:    7.3.4
jupyter-console:   6.4.3
jupyter-core:      4.10.0
jupyterlab-pygments: 0.2.2
jupyterlab-widgets: 1.1.0
kiwisolver:        1.4.4
markdown:          3.4.1
markupsafe:        2.1.1
matplotlib:        3.6.1
mistune:           0.8.4
multidict:         6.0.2
nbclient:          0.6.4
nbconvert:         6.5.0
nbformat:          5.4.0
nest-asyncio:      1.5.5
notebook:          6.4.12
numpy:             1.23.3
oauthlib:          3.2.1
opencv-python:     4.6.0.66
packaging:         21.3
pandas:            1.5.0
pandocfilters:     1.5.0
parso:             0.8.3
pexpect:           4.8.0
pickleshare:       0.7.5
pillow:            9.2.0
pip:               22.2.2
prometheus-client: 0.14.1
prompt-toolkit:    3.0.29
protobuf:          3.19.6
psutil:            5.9.2
pure-eval:         0.2.2
pyasn1:            0.4.8
pyasn1-modules:    0.2.8
pydeprecate:       0.3.2
pygments:          2.12.0
pyparsing:         3.0.9
pyrsistent:        0.18.1
python-dateutil:   2.8.2
pytorch-lightning: 1.7.7
pytz:              2022.4
pyyaml:            6.0
pyzmq:             23.1.0
qtconsole:         5.3.1
qtpy:              2.1.0
requests:          2.28.1
requests-oauthlib: 1.3.1
rich:              12.6.0
rsa:               4.9
send2trash:        1.8.0
setuptools:        65.4.1
six:               1.16.0
soupsieve:         2.3.2.post1
stable-baselines3: 1.6.2
stack-data:        0.2.0
tensorboard:       2.10.1
tensorboard-data-server: 0.6.1
tensorboard-plugin-wit: 1.8.1
tinycss2:          1.1.1
torch:             1.12.1
torchmetrics:      0.10.0
torchtext:         0.13.1
tqdm:              4.64.1
typing-extensions: 4.4.0
urllib3:           1.26.12
wcwidth:           0.2.5
webencodings:      0.5.1
werkzeug:          2.2.2
wheel:             0.37.1
widgetsnbextension: 3.6.0
yarl:              1.8.1
zipp:              3.9.0

System:

OS:                Linux
architecture:

64bit
ELF

processor:         x86_64
python:            3.9.10
version:           #1 SMP Fri Jan 14 13:59:45 UTC 2022`

Huh, that is admittedly weird and definitely should not happen. I don't think we have any imports of torchtext in our imports, at least on 1.7.7 version. Would you be able to share with me the steps you made in order to obtain this environment, i.e. which packages you installed explicitly and in which order?
I have to say, I have a hard time replicating this. I just run pip install absl-py==1.2.0 aiohttp==3.8.3 aiosignal==1.2.0 ale-py==0.7.4 argon2-cffi==21.3.0 argon2-cffi-bindings==21.2.0 asttokens==2.0.5 async-timeout==4.0.2 attrs==22.1.0 autorom==0.4.2 autorom.accept-rom-license==0.4.2 backcall==0.2.0 beautifulsoup4==4.11.1 bleach==5.0.0 cachetools==5.2.0 certifi==2022.9.24 charset-normalizer==2.1.1 click==8.1.3 cloudpickle==2.2.0 commonmark==0.9.1 contourpy==1.0.5 cycler==0.11.0 debugpy==1.6.0 decorator==5.1.1 defusedxml==0.7.1 entrypoints==0.4 executing==0.8.3 fastjsonschema==2.15.3 fonttools==4.37.4 frozenlist==1.3.1 fsspec==2022.8.2 google-auth==2.12.0 google-auth-oauthlib==0.4.6 grpcio==1.49.1 gym==0.21.0 gym-notices==0.0.8 idna==3.4 importlib-metadata==4.13.0 importlib-resources==5.10.0 ipykernel==6.13.1 ipython==8.4.0 ipython-genutils==0.2.0 ipywidgets==7.7.0 jedi==0.18.1 jinja2==3.1.2 jsonschema==4.6.0 jupyter==1.0.0 jupyter-client==7.3.4 jupyter-console==6.4.3 jupyter-core==4.10.0 jupyterlab-pygments==0.2.2 jupyterlab-widgets==1.1.0 kiwisolver==1.4.4 markdown==3.4.1 markupsafe==2.1.1 matplotlib==3.6.1 mistune==0.8.4 multidict==6.0.2 nbclient==0.6.4 nbconvert==6.5.0 nbformat==5.4.0 nest-asyncio==1.5.5 notebook==6.4.12 numpy==1.23.3 oauthlib==3.2.1 opencv-python==4.6.0.66 packaging==21.3 pandas==1.5.0 pandocfilters==1.5.0 parso==0.8.3 pexpect==4.8.0 pickleshare==0.7.5 pillow==9.2.0 pip==22.2.2 prometheus-client==0.14.1 prompt-toolkit==3.0.29 protobuf==3.19.6 psutil==5.9.2 pure-eval==0.2.2 pyasn1==0.4.8 pyasn1-modules==0.2.8 pydeprecate==0.3.2 pygments==2.12.0 pyparsing==3.0.9 pyrsistent==0.18.1 python-dateutil==2.8.2 pytorch-lightning==1.7.7 pytz==2022.4 pyyaml==6.0 pyzmq==23.1.0 qtconsole==5.3.1 qtpy==2.1.0 requests==2.28.1 requests-oauthlib==1.3.1 rich==12.6.0 rsa==4.9 send2trash==1.8.0 setuptools==65.4.1 six==1.16.0 soupsieve==2.3.2.post1 stable-baselines3==1.6.2 stack-data==0.2.0 tensorboard==2.10.1 tensorboard-data-server==0.6.1 tensorboard-plugin-wit==1.8.1 tinycss2==1.1.1 torch==1.12.1 torchmetrics==0.10.0 torchtext==0.13.1 tqdm==4.64.1 typing-extensions==4.4.0 urllib3==1.26.12 wcwidth==0.2.5 webencodings==0.5.1 werkzeug==2.2.2 wheel==0.37.1 widgetsnbextension==3.6.0 yarl==1.8.1 zipp==3.9.0 to install exactly the versions listed in your last environment, pip check didn't complain and import pytorch_lightning had no issues as well

I am getting a similar error:
Exception has occurred: OSError /home/ec2-user/.local/lib/python3.7/site-packages/torchtext/lib/libtorchtext.so: undefined symbol: _ZN5torch6detail10class_baseC2ERKSsS3_SsRKSt9type_infoS6_   File "/home/ec2-user/deep-behavior-embedding/finetune.py", line 8, in <module>     from pytorch_lightning.accelerators import accelerator
------------------------- ------------------- ----------------------------------------
absl-py                   1.3.0
aiohttp                   3.8.3
aiosignal                 1.2.0
alembic                   1.8.1
astunparse                1.6.3
async-timeout             4.0.2
asynctest                 0.13.0
attrs                     22.1.0
aws-cfn-bootstrap         2.0
boto3                     1.24.91
botocore                  1.27.91
cachetools                5.2.0
certifi                   2022.9.24
cffi                      1.15.1
charset-normalizer        2.1.1
click                     8.1.3
cloudpickle               2.2.0
cmake                     3.24.1.1
cramjam                   2.5.0
cycler                    0.11.0
databricks-cli            0.17.3
dataclasses               0.6
docker                    6.0.0
docutils                  0.14
entrypoints               0.4
fastparquet               0.8.1
Flask                     2.2.2
fonttools                 4.37.4
frozenlist                1.3.1
fsspec                    2022.8.2
future                    0.18.2
gitdb                     4.0.9
GitPython                 3.1.29
google-auth               2.12.0
google-auth-oauthlib      0.4.6
greenlet                  1.1.3.post0
grpcio                    1.49.1
gunicorn                  20.1.0
idna                      3.4
importlib-metadata        4.13.0
importlib-resources       5.10.0
intel-openmp              2022.2.0
itsdangerous              2.1.2
Jinja2                    3.1.2
jmespath                  1.0.1
joblib                    1.2.0
jsonlines                 3.1.0
kiwisolver                1.4.4
lockfile                  0.11.0
Mako                      1.2.3
Markdown                  3.4.1
MarkupSafe                2.1.1
matplotlib                3.5.3
mkl                       2022.2.0
mkl-include               2022.2.0
mlflow                    1.29.0
multidict                 6.0.2
numpy                     1.21.6
oauthlib                  3.2.1
packaging                 21.3
pandas                    1.3.5
Pillow                    9.2.0
pip                       20.2.2
prometheus-client         0.15.0
prometheus-flask-exporter 0.20.3
protobuf                  3.19.6
psutil                    5.9.2
pyasn1                    0.4.8
pyasn1-modules            0.2.8
pycparser                 2.21
pyDeprecate               0.3.2
PyJWT                     2.5.0
pyparsing                 3.0.9
pystache                  0.5.4
python-daemon             2.2.3
python-dateutil           2.8.2
pytorch-lightning         1.7.0
pytz                      2022.4
PyYAML                    6.0
pyzmq                     24.0.1
querystring-parser        1.2.4
requests                  2.28.1
requests-oauthlib         1.3.1
rsa                       4.9
s3transfer                0.6.0
scikit-learn              1.0.2
scipy                     1.7.3
setuptools                49.1.3
simplejson                3.2.0
six                       1.16.0
sklearn                   0.0
smmap                     5.0.0
SQLAlchemy                1.4.41
sqlparse                  0.4.3
tabulate                  0.9.0
tbb                       2021.7.0
tensorboard               2.10.1
tensorboard-data-server   0.6.1
tensorboard-plugin-wit    1.8.1
threadpoolctl             3.1.0
torch                     1.13.0a0+gitunknown /usr/local/lib64/python3.7/site-packages
torchinfo                 1.7.1
torchmetrics              0.10.0
torchtext                 0.13.1
tqdm                      4.64.1
typing                    3.7.4.3
typing-extensions         4.4.0
urllib3                   1.26.12
websocket-client          1.4.1
Werkzeug                  2.2.2
wheel                     0.37.1
yarl                      1.8.1
zipp                      3.9.0
zmq                       0.0.0

Not sure what the issue is. I tried downgrading from 1.7.7 to 1.7.0 and still got the same error. I'm running Python 3.7.10.

Hi, @EvanZ, I am fairly confident this is a mismatch between torch and torchtext versions. We are importing torchtext to check if it is available in 1.7.* releases and it crashes on import since there is that mismatch.

Hey @otaj yes this was indeed our problem as far as I can tell. We upgraded torchtext and it works now.

Perfect, @EvanZ, that is great to hear! I will close this issue now then.

source: gharchive/issue

authors: EvanZ n-balla otaj

repo: Lightning-AI/lightning

license_type: permissive

license_source: github-api


text:
[CLI] Move storage from app prefix to project/app prefix

What does this PR do?
We decided to move app storage prefix from app_id to project_id/app_id.
This PR makes the change. The environment variable LIGHTNING_STORAGE_PATH will be set inside the workflow container, and we will take the storage path from this environment variable.
If it's not specified, it will use the previous logic for defining app storage prefix.
Does your PR introduce any breaking changes? If yes, please list them.
Yes! App storage prefix will be different for new apps.
@rlizzo @panos-is @rusenask please take a look should we check do we have something from previously created app storages in the new logic, e.g. here: https://github.com/Lightning-AI/lightning/blob/master/src/lightning_app/storage/orchestrator.py#L90:L92 ?
We will deprecate old-way created storages in ~1 month.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

should we check do we have something from previously created app storages in the new logic, e.g. here: https://github.com/Lightning-AI/lightning/blob/master/src/lightning_app/storage/orchestrator.py#L90:L92 ?

I think for this we can actually get rid of that conditional and the old way of doing things entirely. This code would only ever run on newly created apps, not currently running apps that don't know the about the environment variable.
We just need to start injecting the env var on the cloud (before this is merged so that e2e tests can pass) and call it a day :)

@dmitsf Just double checking, is the milestone correct, as this is a new addition/breaking change rather than a bugfix?

@dmitsf Just double checking, is the milestone correct, as this is a new addition/breaking change rather than a bugfix?

Thanks! Changed to 0.7.

source: gharchive/pull-request

authors: awaelchli dmitsf rlizzo


text:
Sort Trainer arguments based on importance

What does this PR do?
I propose to organize the Trainer's arguments based on importance/usage frequency. This is just my take on it, please make suggestions. Alternatively, they could also be grouped by function.
Before, the arguments were arranged randomly.
cc @borda @justusschock @awaelchli

this is a breaking change so a user can't pass just an argument

Before, the arguments were arranged randomly.

not randomly but with respect to minimizing breaking changes.... :)

authors: Borda awaelchli


text:
Don't import pretty_errors

It's really inappropriate for a low-level library like this to be making global changes to the way stack traces are rendered.  Especially since the "pretty" stack traces don't include file names or line numbers!
This is just crazy.  All I wanted to do was import lightning, and I had to spend a couple hours tracking down why my stack traces were suddenly useless.  If users want this behavior, they should knowingly opt-in themselves.  They shouldn't be forced in by some dependency of a dependency of a dependency.

📚 Documentation preview 📚: https://torchmetrics--2543.org.readthedocs.build/en/2543/

Thank you for sharing your opinion; how/why do you install debug dependency in the first place? :thinking:

I just installed lightning, yesterday:
$ python -m venv venv
$ . venv/bin/activate
$ pip install torchmetrics==1.4.0
...
$ pip freeze | grep pretty
pretty-errors==1.2.25

It's good that torchmetrics doesn't break stack traces by default as of 1.4.0.post0, but there's still no reason for this library to have the potential to do so.  If a user want to use pretty_errors, they should modify site_customize.py or alias python, as recommended by pretty_errors itself.

authors: Borda kalekundert

repo: Lightning-AI/torchmetrics


text:
Rename the plugin to remain compatible with other libraries which use the official Camera plugin.

When trying to use this plugin with our projects, they failed to build because the name of the plugin was the same as the original camera plugin and other plugins were referencing that. To avoid duplication of included plugins, I had to rename the plugin to match the project's name and thought maybe someone else would like to do the same.
Great plugin btw! Thanks for all your great work.

Hi any idea on when will this issue be resolved?

Happy to do it, but what would you like me to change it to?

authors: alexandrevillard richardbushnell


text:
🛑 LinerlyBot (Discord) is down

In b516b81, LinerlyBot (Discord) (https://linerlybot-discord.linerly.tk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LinerlyBot (Discord) is back up in 155338d.

repo: Linerly/status

license: MIT


text:
🛑 LinerlyBot (Discord) is down

In 1379953, LinerlyBot (Discord) (https://linerlybot-discord.linerly.tk) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LinerlyBot (Discord) is back up in 92a86a7.


text:
🛑 Nextcloud is down

In 3ff43fb, Nextcloud (https://cloud.linerly.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextcloud is back up in 7ba6994 after 2 hours, 4 minutes.


text:
Merge 1.8.5

See https://github.com/Homebrew/brew/releases/tag/1.8.5

==> brew tests --no-compat --online
Too long with no output (exceeded 10m0s)

https://circleci.com/gh/Linuxbrew/brew/1318
I'll try rebuilding.

repo: Linuxbrew/brew

license_source: bigquery


text:
role: freeipa_server: msg: In unattended mode you need to provide at least -r, -p and -a options

When running the freeipa_server role ansible-playbook --inventory <inventory> linuxfabrik.lfops.freeipa_server --tags freeipa_server,  i get the error message below:

TASK [freeipa.ansible_freeipa.ipaserver : Install - Server installation test] *******************************************************************************************************************************
Monday 19 September 2022  14:34:47 +0200 (0:00:00.053)       0:00:02.725 ******
fatal: [<hostname>]: FAILED! => changed=false
  msg: In unattended mode you need to provide at least -r, -p and -a options

Rocky Linux release 8.6 (Green Obsidian)

the specific freeipa error is caused by neither the domain nor the realm being set: https://github.com/freeipa/ansible-freeipa/issues/718.
lfops tries to use the ansible_facts["domain"] for the domain and realm. However determining ansible_facts["domain"] requires the DNS setup to be correct (which was not the case here). I will improve the lfops role to check for a proper DNS setup before calling the official freeipa role.

authors: NavidSassan bzblf

repo: Linuxfabrik/lfops

license: Unlicense


text:
Different export format

Right now the export use jiffy and generate a json. It would be nicer to simply output a string format that is more specific.
There are a few. No idea yet which one would make sense. Will add more research

See in particular https://github.com/aggregateknowledge/hll-storage-spec/blob/master/STORAGE.md

repo: LivewareProblems/hyper


text:
🛑 LogSentinel SIEM dashboard is down

In 8361417, LogSentinel SIEM dashboard (https://siem.logsentinel.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LogSentinel SIEM dashboard is back up in e3e9fa5.

repo: LogSentinel/status


text:
[Bug] 下载路径不兼容mac系统

src/global/initLocalStore.ts
里面的desktop路径使用了\分割符，在mac中的下载路径就变成 User/xxx\DeskTop/timestam.mp3
试试使用
const desktopDir = ${homeDir}/Desktop。
我没有windows电脑，就没试。在windows下不行的话，也得使用path.join了。

我创建了一个跨平台分支，merge 了本 repo 关于跨平台保存路径的修复的 pr，如果需要的话可以使用： https://github.com/CubikTech/tts-vue-multiplatform
如有问题可以在分支仓库的 issue 里提交反馈

我没有MAC，很多地方没有做mac的适配
可以试试const desktopDir = require("path").resolve(homeDir, "Desktop");

authors: Cubik65536 LokerL lephones

repo: LokerL/tts-vue


text:
Nested includes error

Laravel Rest Api Version
2.4.2
Laravel Version
10
PHP Version
8.1
Database Driver & Version
mysql
Description

(POST) api/posts/search relation [belongsTo.hasMany] it's working

{
  "search": {
    "includes": [
      {
        "relation": "user.roles"
      }
    ]
  }
}

(POST) api/posts/search relation [hasMany.belongsTo] it's error

{
  "search": {
    "includes": [
      {
        "relation": "comments.user"
      }
    ]
  }
}

//Lomkit\\Rest\\Query\\Builder::__construct(): Argument #1 ($resource) must be of type Lomkit\\Rest\\Http\\Resource, null given

Steps To Reproduce
Description

Hello,
Could you give me your "CommentResource" relations please ? I'll try to reproduce this after to confirm the bug 😄

sorry, it's my code

authors: GautierDele ThanhSonITNIC

repo: Lomkit/laravel-rest-api


text:
0.9.13 crashes before cloning the repository

After clicking "start translating" app closes immediately...

Actually, after crash the chosen repo does show on the list, but without strings.xml file, updating that file also crash the app

Could you please provide what repository is failing?

Well, on my device every repository is failing.

Could you debug the application yourself? A stack trace would be really useful.

Found this: https://i.imgur.com/7BVAGGS.png

Thank you, the fact that you use Polish + the error says "IllegalFormatPrecisionException" is actually really helpful. The translator for the Polish strings had a typo from "%. 1f%%" to the correct "%.1f%%". Until the fix is available, you can switch to the English locale (or any other) and it should work!

Running the "Invalid format string" inspection helps pinpoint these kind of errors, too.

So it was my fault... xD
Thanks

So it was my fault... xD

Whoops, didn't notice that haha. It's alright :P

authors: Bjornskjald Lonami

repo: LonamiWebs/Stringlate


text:
🛑 jpvir is down

In f12f954, jpvir ($JPVIR) was down:

HTTP code: 0
Response time: 0 ms

Resolved: jpvir is back up in b239ee2.

repo: LonelyJupiter/UPPTIME


text:
Many successive JOINFAIL attempts - requires setting RP_MARGIN_DELAY to ~5000ms

Hello,
I have recently completed a board port for SWL2001 to work on ESP32-S3 with the Semtech SX1262. I can successfully join with my LNS (AWS), but only typically after several failed JOINFAIL events occurring first. Occasionally, it will join successfully on the first attempt.
I have also noticed that I must set RP_MARGIN_DELAY to a value around 5000ms for it to ever join successfully. When I enable MODEM_HAL_DBG_TRACE_RP, I notice that I always get the print that the high priority task (the join request) is in the future, and a delay amount of around 4800ms.
I have verified that the LNS is configured for the correct MAC version (1.0.4), and the correct regional parameters version. I have tried configuring both RP2_101 and RP2_103 on the SWL2001 side, with the corresponding correct RP version on AWS, as well as using MAC version 1.0.3 with similarly matching configurations on AWS, but have yet to have a successful combination with consistent results.
Is it the case that this is just the reality and behavior of LoRaWAN? Or should join attempts and RX window 1 and 2 openings be more accurate and consistent than this? Any help is appreciated.
Thanks.
Brandon
UPDATE:
I found this document and followed the section 8, RX Window Debugging procedure. I am now using a board delay of 1ms (the same as it was previously), and an RP margin delay of 234ms - far less than the previously mentioned 5000ms delay I was using.
I am able to join with this timing, but it still seems to take more JOINFAIL events than I had hoped for.

@lbm-team Bump. Hoping to get a little guidance or suggestions for reducing JOINFAILs.

Hi lbm-team,
Thank you for your response. Yes, I followed the porting guide and have run the porting tests. All tests are now passing (explanation ahead).
I realized that the reason for the need to increase the RP margin delay was a delay I added in the busy line wait loop. The intent was to avoid hogging processor time with a busy wait, as there are other peripherals and threads in my use-case. Re-running the RX debugging procedure with the delay removed shows that timing is now correct (both delays were exactly 5000ms) without any margin delay adjustment. The result from the related porting test also no longer indicates that RX and TX configuration times are too long as it did prior to the change.
This being said, I still observe more join failures than I would expect. With the RP margin delay now fixed, I have entirely run out of ideas as to what the problem could be, other than possibly the issue stemming from my gateway.
main_porting_tests_output.txt

Is this issue still valid ? Many thanks.

The issue has yet to be resolved, but yes can be closed. Thanks.

authors: bdesterBE brandester32 opeyrard


text:
🛑 [IRC] SSL Round Robbin is down

In 0d10d1b, [IRC] SSL Round Robbin (irc.digitalirc.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [IRC] SSL Round Robbin is back up in dd9696b after 17 minutes.

repo: LordRandom/digitalirc-status


text:
🛑 Pog Bot is down

In 9256846, Pog Bot ($BOT_PING_URL) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pog Bot is back up in 4351b04.

repo: LordRonz/status


text:
奇怪的bug

1.心情值明明已经是100了，但播放的动画仍然是不开心的状态
2.在不开心的状态下直播，所播放的动画是写文案时的动画
https://github.com/LorisYounger/VPet/assets/96658974/c33c4fb5-5fd5-442d-be6a-691978932d3c

错误动画修好了

心情对应不上应该是没有计算新状态的原因, 之前计算状态只在每计算周期进行.
现已修复

repo: LorisYounger/VPet


text:
Incompatible with OptiFine?

When i try to use the mod and start MC it doesnt start and crashes, i think my PC isnt the problem, but idk why that happens
no problem with another mods, only optifine
i tried with only those 2, but i only can have activated or changed or optifine, not both
14gb Ram
AMD A8 6500B
Radeon HD8570D
so... idk why that happens, i want to play with shaders (and some optimization tweaks)

Known issue, Optifine sucks with other mods. I recommend using Rubidium, and Oculus for shaders.

Known issue, Optifine sucks with other mods. I recommend using Rubidium, and Oculus for shaders.

Embeddium is more updated then Rubidium. Rubidium hasn't seen updates in a long time.

repo: LtxProgrammer/Changed-Minecraft-Mod


text:
8.2.0 getPlaylist => 400 Error

Steps to reproduce
Use this simple code to reproduce:
import { Innertube, UniversalCache } from 'youtubei.js';

const yt = await Innertube.create({
  cache: new UniversalCache(false)
});

async function main(id: string) {
  const playlist = await yt.getPlaylist(id)
  console.log("videos =>", playlist.videos)
  console.log("total =>", playlist.videos.length)
  return playlist
}

main(<VALID_PLAYLIST_ID>)

Failure Logs
file:///home/runner/innertube-playlist-typescript/node_modules/youtubei.js/dist/src/utils/HTTPClient.js:99
            throw new InnertubeError(`Request to ${response.url} failed with status ${response.status}`, yield response.text());
                  ^

InnertubeError: Request to https://www.youtube.com/youtubei/v1/browse?key=AIzaSyAO_FJ2SlqU8Q4STEHLGCilw_Y9_11qcW8&prettyPrint=false&alt=json failed with status 400
    at HTTPClient.<anonymous> (/home/runner/innertube-playlist-typescript/node_modules/youtubei.js/src/utils/HTTPClient.ts:145:11)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/innertube-playlist-typescript/node_modules/tslib/tslib.js:166:62)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  info: '{\n' +
    '  "error": {\n' +
    '    "code": 400,\n' +
    '    "message": "Request contains an invalid argument.",\n' +
    '    "errors": [\n' +
    '      {\n' +
    '        "message": "Request contains an invalid argument.",\n' +
    '        "domain": "global",\n' +
    '        "reason": "badRequest"\n' +
    '      }\n' +
    '    ],\n' +
    '    "status": "INVALID_ARGUMENT"\n' +
    '  }\n' +
    '}\n',
  date: 2024-01-11T03:41:00.717Z,
  version: '8.2.0'
}

Node.js v18.12.1

Expected behavior
Returns object that is typed with "Playlist" instance.
Current behavior
Got 400 error
Version
Default
Anything else?
No response
Checklist

[X] I am running the latest version.
[X] I checked the documentation and found no answer.
[X] I have searched the existing issues and made sure this is not a duplicate.
[X] I have provided sufficient information.

I got it. It is working sometimes (not everytime), so I will still open this issue; please have a look for me.

I get the same error, but with the iOS client on getChannel

@llsc12 Most of the library only supports the WEB client, the iOS one is only there so you can use it with getBasicInfo. See https://github.com/LuanRT/YouTube.js/issues/555 for more information.

bump

Any updates?

@kms0219kms Could you please provide some examples of playlist IDs that don't work for you?

@kms0219kms Could you please provide some examples of playlist IDs that don't work for you?

This was intermittent, and happened with almost every playlist.
I tried with these playlists:
https://youtube.com/playlist?list=PLGjrfkkeSCpuZtSDfWxSTu5bRbors-Ru_&feature=shared
https://youtube.com/playlist?list=PLGjrfkkeSCpuhHt_P1ijAYYQceDJdQlfC&feature=shared
https://youtube.com/playlist?list=PLGjrfkkeSCpsmBsmkqoDrEMENM2SRGMsC&feature=shared
https://youtube.com/playlist?list=PLGjrfkkeSCpuISmlt8vhzRMifOCwGddKn&feature=shared
https://youtube.com/playlist?list=PLGjrfkkeSCpuRsD8tGGhwKRxwLJyE20WT&feature=shared

@absidue


text:
Add native sentiment analysis for other languages

Add native sentiment analysis instead of relying on Google Translator for some commonly-used languages
In order of use (check logs below):

[ ] Italian
[ ] Portuguese
[ ] Spanish
[ ] German
[ ] Danish

Counter({'it': 414, 'en': 75, 'pt': 55, 'de': 39, 'tl': 28, 'vi': 23, 'sw': 18, 'af': 18, 'nl': 16, 'ro': 15, 'cy':
 15, 'hu': 15, 'ca': 11, 'et': 11, 'so': 10, 'fi': 9, 'id': 9, 'es': 8, 'tr': 7, 'lt': 6, 'sk': 6, 'fr': 6, 'no': 6
, 'pl': 4, 'da': 4, 'hr': 3, 'sv': 3, 'lv': 1, 'sl': 1})

Counter({'es': 24, 'en': 12, 'de': 2, 'it': 2, 'pt': 1, 'et': 1, 'da': 1, 'fi': 1, 'vi': 1, 'tr': 1, 'so': 1, 'sl': 1, 'tl': 1})

Counter({'it': 80, 'pt': 19, 'de': 18, 'vi': 10, 'tl': 7, 'en': 6, 'so': 5, 'ca': 4, 'cy': 4, 'ro': 2, 'sk': 2, 'af': 2, 'hu': 2, 'id': 2, 'lt': 1, 'no': 1, 'es': 1, 'et': 1, 'pl': 1, 'sw': 1})

Counter({'it': 93, 'pt': 20, 'de': 18, 'vi': 10, 'tl': 7, 'en': 6, 'so': 5, 'ca': 4, 'cy': 4, 'af': 3, 'hu': 3, 'ro': 2, 'sk': 2, 'id': 2, 'lt': 1, 'no': 1, 'es': 1, 'et': 1, 'pl': 1, 'sw': 1})

Counter({'es': 7, 'fi': 1, 'tl': 1, 'lv': 1, 'sw': 1})

Several intents have been performed to support this languages but have failed for one reason or another.
Things I've tried:
https://huggingface.co/oliverguhr/german-sentiment-bert
https://pypi.org/project/sentiment-analysis-spanish/
https://github.com/aylliote/senti-py
https://github.com/NicGian/SentITA

repo: LuisMayo/ace-attorney-bot


text:
Validate http11 body type

Raising ValueError in HTTP11Connection._send_body on invalid body type
Added tests for the case when the error may be raised. Also testing the
other cases when errors regarding the type of body argument may be
raised.
Added to the docstring the option to send an iterable of bytestrings as a body.

Thanks for this!
I've left a few small notes inline that I'd like you to address before I merge this. =) Additionally, I think switching to use a TypeError here, while semantically more accurate, is more churn than I want at this stage in the library's life. Do you mind leaving those as ValueError? I'll probably end up wanting to introduce a custom exception for this case anyway.

Done :)

Fantastic @AvivC! Thanks! :sparkles: :cake: :sparkles:

You're welcome :)

authors: AvivC Lukasa

repo: Lukasa/hyper

license: mit


text:
🛑 Greater Bank is down

In a77b810, Greater Bank (https://public.cdr-api.greater.com.au/cds-au/v1/banking/products) was down:

HTTP code: 403
Response time: 942 ms

Resolved: Greater Bank is back up in 9a5e489.

repo: LukePrior/OpenBankingUptime


text:
patched in st-glyph-wide-support

Fixes Glyph truncation. Patch from st site: https://st.suckless.org/patches/glyph_wide_support/

Hi @iStagnant, does the patch actually work for you?
I have just tried it and it certainly improves the situation, but doesn't really solve the issue.
I'll demonstrate the behavior of wide glyphs from Neovim, with 3 terminals:

Most left terminal is st without this patch.
Terminal in the middle is st with this patch applied
Most right terminal is alacritty which apparently has this mostly solved.

Moving forward:

From this gif, we can observe:

All 3 terminals are able to display character correctly upon loading file.
When wide glyph character is selected by the block cursor:

st version without this patch redraws (and highlights) just the original space of this character, while remainder remains without highlight.
st version with this patch redraws (and highlights) wide character as a whole, so that part is certainly fixed by this.
alacritty also fails to redraw whole character, just like st without this patch.

When character after wide glyph (in this case, that is space) is selected by the block cursor:

st version without this patch redraws that character and chops the remainder of the wide glyph.
st version with this patch does the same thing, unfortunately.
alacritty also draws over remainder of wide glyph character, but obviously remembers that it needs to restore it after next movement.

Move backwards:

From this gif, we can observe:

Once the wide glyph character is chopped after initial drawing:

st without this patch can't properly redraw it, even when moving over it (in both directions).
st with this patch is actually able to properly redraw it once it's selected again (from both directions), so that is also fixed.
alacritty had it already working so it just works normally without needing to do anything special.

Losing focus while positioned on the character after wide glyph.

From this gif, we can observe:
After wide glyph character was chopped and we lose the focus to change the cursor shape:

st without this patch doesn't have it restored.
st with this patch also doesn't have it restored.
alacritty has it restored as soon as it is done with highlighting character after it.

FYI, @Dreomite  as the original author of the patch.

Hello @Iskustvo i couldn't replicate the behaviour you are getting, when i tried it on the icons in my dwm config.h (you can try it it's in dwmrice/.config/dwm) it showed normal behaviour sure the " at the end kind of entered in the icons but that wasn't the issue this was supposed to solve. And sorry for not including visual examples i was in a hurry to test this and i can't access my laptop for the next 4 days.

No worries, thank you for answering quick enough!
Unfortunately, the behavior is exactly the same for all 3 "versions" of terminals (like above) with your tag icons :disappointed:
Btw, are you using this repository or clean st?
I just did a quick check with this repository (clean master, without this PR) and it seems that everything is already working here, the only thing missing seems to be that when the character is highlighted, the remainder stays without reverted color (but isn't chopped!).
Funny enough, that's the one thing that original patch fixes when applied to clean st directory, as observed in first gif :rofl:
I also tried this branch and I don't see any difference compared to the clean master, am I missing something?
Last but not least, I would really appreciate if anyone can double-check and confirm what I'm writing here.
At the very list, we should be aware if official patch is not working on clean st code.
If uncomfortable with manually applying patches, feel free to use my build-wrapper repository.
cd /tmp # Or wherever
git clone --recursive https://github.com/Iskustvo/simple_terminal.git # Download my build wrapper around st
cd simple_terminal
rm -rf patches/* # Delete all patches that I use
make get_upstream_patch LINK=https://st.suckless.org/patches/glyph_wide_support/st-glyph-wide-support-20220411-ef05519.diff # Download official patch with this fix
make -j8 # Apply downloaded patch and build st
(./st/st &> /dev/null)& # Open newly built st
# Test behavior from above on any wide glyph symbol

This patch is applied to this repository and not clean st.
And maybe it does not fis this issue, it does make the glyphs appear fully and bot chopped in half

This patch is applied to this repository and not clean st.
And maybe it does not fis this issue, it does make the glyphs appear fully and not chopped in half, check @Dreomite first issue to see what i mean by chopped in half.
And through the research that i did i found a couple of patches:

A boxdraw compatible patch  which i applied here because this repo has boxdraw patched in.

This patch is applied to this repository and not clean st.
And maybe it does not fix this issue, it does make the glyphs appear fully and not chopped in half, check @Dreomite's first issue to see what i mean by chopped in half.
And through the research that i did i found a couple of patches:

A boxdraw compatible patch  which i applied here because this repo has boxdraw patched in.
A couple non boxdraw compatible patches:

The first is this one  from the patches section on suckless's site which works on the latest version of st.
This one created by @mohkale which also work on the latest version of st.
And obviously the original patch done by @Dreomite which only works on st versions below 0.8.4

And all of these patches fix the issue of glyphs being chopped in half, the only difference between boxdraw compatible and the non compatible ones is that if you apply any of the non compatible patches to a build of st that has boxdraw patched in weird characters appear instead of lines.
Lastly i already confirmed that all these patches that derive from @Dreomite's first patch fix the issue of glyphs getting chopped in half, but i don't know about your issue, so i would like to ask you to git checkout e3b821d this repo and try and see if your issue in fixed in the original commit by @Dreomite if not then this patch was flawed from the beginning and only fixes the issue of glyphs getting chopped in half.
~github's ui on phone is trash i clicked close with comment like 2 times by mistake~

You are correct, I have tested all patches you mentioned (including e3b821d) and all of them fix the original issue as explained by @Dreomite. Unfortunately, none of them fixed the issue I posted here.
However, that issue is fixed somewhere on master branch in this repository, so fix for it does exist, either directly or indirectly. I'll try to git bisect it unless someone knowledgeable about it responds here.
Regardless, thanks a lot for all the clarifications!

Ok, so here's the thing.
This patch for ligatures solved the issue. More precisely, this is the only thing needed for proper redrawing of wide glyphs:
diff --git a/st.c b/st.c
index 62def59..cc6c78e 100644
--- a/st.c
+++ b/st.c
@@ -2640,7 +2640,8 @@ draw(void)

        drawregion(0, 0, term.col, term.row);
        xdrawcursor(cx, term.c.y, term.line[term.c.y][cx],
-                       term.ocx, term.ocy, term.line[term.ocy][term.ocx]);
+               term.ocx, term.ocy, term.line[term.ocy][term.ocx],
+               term.line[term.ocy], term.col);
        term.ocx = cx;
        term.ocy = term.c.y;
        xfinishdraw();
diff --git a/win.h b/win.h
index 6de960d..94679e4 100644
--- a/win.h
+++ b/win.h
@@ -25,7 +25,7 @@ enum win_mode {

 void xbell(void);
 void xclipcopy(void);
-void xdrawcursor(int, int, Glyph, int, int, Glyph);
+void xdrawcursor(int, int, Glyph, int, int, Glyph, Line, int);
 void xdrawline(Line, int, int, int);
 void xfinishdraw(void);
 void xloadcols(void);
diff --git a/x.c b/x.c
index 43d1ba4..85deee6 100644
--- a/x.c
+++ b/x.c
@@ -1510,14 +1510,17 @@ xdrawglyph(Glyph g, int x, int y)
 }

 void
-xdrawcursor(int cx, int cy, Glyph g, int ox, int oy, Glyph og)
+xdrawcursor(int cx, int cy, Glyph g, int ox, int oy, Glyph og, Line line, int len)
 {
        Color drawcol;

        /* remove the old cursor */
        if (selected(ox, oy))
                og.mode ^= ATTR_REVERSE;
-       xdrawglyph(og, ox, oy);
+
+       /* Redraw the line where cursor was previously.
+        * It will restore wide glyphs and ligatures broken by the cursor. */
+       xdrawline(line, 0, oy, len);

        if (IS_SET(MODE_HIDE))
                return;

I don't know if other patches also include this redrawing part of the code, so I opened PR for official wiki to add separate patch that includes the original solution + this change above. Though I still have to figure out where to review my opened PR and potential review comments :laughing:

Nice job @Iskustvo! Since your solution is better i will close my PR and once you're done with everything you could open PR here.

No, no, you misunderstood me, sorry I wasn't clear enough!
I meant that the only thing missing from the original/standalone patch for wide glyphs is the extracted snippet which solves my redrawing issue.
In this repository, you already have that part in the code base (added through patch for ligatures) and only need to provide what you already have in this PR.
So, regarding this PR, everything is good as-is, "my" addition is only needed for standalone version of this patch, for someone who applies it on a clean st, like I do.
Therefore, please reopen this PR, you should already be familiar with the process :smile:

authors: Iskustvo iStagnant

repo: LukeSmithxyz/st


text:
Update Logo WarriorsMC

General:

[ ] The pull request title is descriptive. (ex. Added Lunar Network, not Updated metadata.json)
[ ] The pull request does not contain any unrelated commits. (ex. commits from previous pull requests)

Mapping Additions or Updates:

[ ] Folder with appropriate name has been created / updated (must not include any non-alpha characters or whitespace).
[ ] No changes were made to the file's formatting (4 spaces per tab).
[ ] There are no syntax errors.
[ ] There is no pre-existing mapping matching my id (check if there is an existing folder).
[ ] My field values match your requirements.
You can view our patterns here: metadata.schema.json, or take a look below and complete the field checklist:

[ ] id: a lowercase string, which should match the folder name (ex. myserver)
[ ] name: a string (ex. MyServerPvP)
[ ] description: hook between 16 and 80 characters (ex. Home of Competitive Minecraft PvP)
[ ] addresses: an array with lowercase strings (ex. ["my.server", "your-server.com"])

You do not need to specify subdomains, Lunar Client services automatically detect them.

[ ] primaryAddress: the primary address that people connect to with (please include the subdomain if required) (ex. mc.my.server)
[ ] minecraftVersions: an array with Minecraft versions as strings _(ex. ["1.18._", "1.19.2"] - Must be versions or subversions supported by Lunar Client)*
[ ] primaryMinecraftVersion: a Minecraft version as a string (ex. 1.19.2 - Must be a subversion supported by Lunar Client)
[ ] primaryColor: a hexademical color code that primarily distinguishes the server (ex. #00FFFF)
[ ] secondaryColor: a hexademical color code that accompanies the primaryColor of the server (ex. #FF0000)
[ ] primaryRegion: the primary region where your server operates in (ex. NA)
[ ] regions: a list of regions where you have servers located that service your players (ex. ["NA", "EU", "AS"])
[ ] gameTypes: a list of games that describe the content on your server, must be a max of 3 listed (ez. ["PVP", "UHC", "HCF"])
[ ] crossplay: whether the server has support for Bedrock Edition players (through proxies such as GeyserMC)
[ ] (optional) presentationVideo: YouTube video ID (in slug) to server trailer / introduction (ex. 7EV4cPuJvXE)
[ ] (optional) website: url of server website, must include URL schema (http:// or https://) (ex. https://www.your-server.com)
[ ] (optional) store: url of server store, must include URL schema (http:// or https://) (ex. https://store.your-server.com)

Socials

[ ] (optional) twitter: username of twitter account without the @ (ex. MyServer)
[ ] (optional) discord: invite link to discord (ex. https://discord.com/invite/4ceEJuH)
[ ] (optional) youtube: slug or username of youtube channel (ex. MyServer)
[ ] (optional) instagram: username of instagram account (ex. MyServer)
[ ] (optional) twitch: username of twitch account (ex. MyServer)
[ ] (optional) telegram: slug of telegram group (ex. MyServer)
[ ] (optional) reddit: slug of subdreddit wtih 'r/' (ex. MyServer)
[ ] (optional) tiktok: username of tiktok account (ex. MyServer)
[ ] (optional) facebook: slug of facebook page (ex. MyServer)

Compliance

[ ] (optional) privacyPolicy: url to your Privacy Policy (ex. https://www.lunar.gg/privacy)
[ ] (optional) termsOfService: url to your Terms of Service (ex. https://www.lunar.gg/terms)
[ ] (optional) rules: url to your Rules (ex. https://www.lunar.gg/rules)

Media:
Logo

[ ] My logo is a png file.
[ ] I have uploaded my logo to my server folder (ex. lunarnetwork) and named it logo.png.
[ ] My logo has a transparent background and is square (1:1 aspect ratio).
[ ] My logo is 512 pixels in width and height.
[ ] My logo is my own property and complies with relevant copyright/privacy laws.

Background

[ ] My background is a png file.
[ ] I have uploaded my background to my server folder (ex. lunarnetwork) and named it background.png.
[ ] My background has an aspect ratio of 16:9.
[ ] My background is atleast 1920 pixels in width and 1080 pixels in height (can be bigger, but must remain the same aspect ratio).
[ ] My background contains relevant content pertaining to the server, is my own property, and complies with relevant copyright/privacy laws.
[ ] My background doesn't contain any markings, text, or logos (unless part of a build).

Hi @Anakinnnnn, I hope you are well, you know that a few days ago you already updated my logo, however, in the presence of discord, my old logo continues to appear. What should I do to make the new one appear? Cordial greetings

repo: LunarClient/ServerMappings


text:
Alpha channel is discarded in screenshots before writing to disk #1455

Added util::imagewriter::WriteBmpImageNoAlpha() and util::imagewriter::WritePngImageNoAlpha().
Kept previous versions in case the output of alpha channel becomes a command-line option.

CI gfxreconstruct build queued with queue ID 164594.

CI gfxreconstruct build # 3977 running.

CI gfxreconstruct build # 3977 failed.

CI gfxreconstruct build queued with queue ID 165242.

CI gfxreconstruct build # 3983 running.

CI gfxreconstruct build queued with queue ID 165254.

CI gfxreconstruct build # 3984 running.

CI gfxreconstruct build # 3984 passed.

CI gfxreconstruct build queued with queue ID 165339.

CI gfxreconstruct build # 3985 running.

CI gfxreconstruct build # 3985 passed.

CI gfxreconstruct build queued with queue ID 165782.

Would it be a good idea to give the user the option to keep alpha values?

CI gfxreconstruct build # 3988 passed.

Would it be a good idea to give the user the option to keep alpha values?

So far we've had no indication that anyone has required the alpha values for anything.  We may discover that they do, but we are also getting close to merging a PR to allow saving out inputs and outputs to any draw call.  Saving the color output attachments of the last draw call before QueuePresent would be (I think) a much better solution and gives the real framebuffer contents before presentation.
So I think please squash-merge this and if anyone out in the ecosystem squawks then we can add back in a flag to optionally turn on alpha.

repo: LunarG/gfxreconstruct


text:
manage signed timestamped values

# Comments for current PR

add your comments here
...

!!! WARNING : DO NOT EDIT THE CHECKLIST BELOW !!!
Checklist : Merge from DEVELOP branch
Code Quality

[ ] Each function has a header (description, inputs, outputs)
[ ] Code is commented (particularly in hard to understand areas)
[ ] There are no new warnings that can be corrected
[ ] Commits policy is respected (constitancy commits, clear commits comments)

Tests Review

[ ]  Manual Tests for new features have been reviewed
[ ]  Automatic Tests for new features have been reviewed

Tests are passed the best as I can

[ ]  Non regression existing tests are passed OK
[ ]  New tests for new features & bug fixes are passed OK

Documentation

[ ] Documentation is up to date
[ ] Changelog for next release is up-to-date : fill here
[ ] If needed, tests are briefly described in test repository

We don't need to use int64_t so I changed my PR.
After reading your comments, I think we should put this feature on hold for a moment. This feature is tighly coupled with our tools as the Saas tool. I think we should wait for this feature to have a clear view of what we need to do.

repo: Luos-io/LuosHAL


text:
Helper text of fields not showing

Hello, I'm using v2.2.1 of the package. I noticed that the helper text of the fields is not showing in the form.
I tried text and textarea fields just to be sure that the problem was not in the specific type of field, but no help text appeared in both types.
The help text works when I move the field outside the HasManyNested field, so I suppose it's something with the package itself.

I am not able to replicate the bug, can you check for conflicts with other packages?

authors: Lupennat bozhidarampeco

repo: Lupennat/nova-nested-many


text:
🛑 EnderChest（末影箱-云盘） is down

In 0dd7621, EnderChest（末影箱-云盘） (https://enderchest.anavi.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: EnderChest（末影箱-云盘） is back up in 9d696dd after 6 minutes.

repo: LxnChan/status


text:
🛑 Official（泠泫凝的异次元空间-主页） is down

In 78c4461, Official（泠泫凝的异次元空间-主页） (https://lxnchan.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Official（泠泫凝的异次元空间-主页） is back up in 113b957 after 12 minutes.


text:
🛑 EnderChest（末影箱-云盘） is down

In c6f95ab, EnderChest（末影箱-云盘） (https://enderchest.anavi.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: EnderChest（末影箱-云盘） is back up in 17078a2 after 4 minutes.


text:
🛑 Official（泠泫凝的异次元空间-主页） is down

In 61f45d8, Official（泠泫凝的异次元空间-主页） (https://lxnchan.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Official（泠泫凝的异次元空间-主页） is back up in f6e86ec after 18 minutes.


text:
🛑 EnderChest（末影箱-云盘） is down

In 8342766, EnderChest（末影箱-云盘） (https://enderchest.anavi.cn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: EnderChest（末影箱-云盘） is back up in cc6743e after 17 minutes.


text:
[Feature Request] Possibility to set arbitrary framerate target for DRS, before or after frame generation

I understand the DRS system in FF XVI works by reducing the rendering resolution until the target frame rate set in the options is reached. Then the selected upscaling method (DLSS, FSR or XESS) is used to bring the image up to the output resolution. Unfortunately the available frame rate targets are not very granular, they just go 30, 60, 120 and 240. It is also unclear, if and how frame generation is considered here.
It would be great, if we could define an arbitrary frame rate target for the DRS system and also could specify, if the target is applicable for the fps before or after frame generation.
On my system I would like to be able to either:

set a 55fps target before frame generation
set a 90fps target after frame generation

Thanks for the great work guys, yet another game saved by your efforts.

A little note here, not entirely related, but by modifying the code at ffxvi.exe+AAE4A2 allows us to directly set the current resolution scale. R10 + 0x140 points to the byte which is the current resolution scale, bl is the second parameter to the subroutine.

I tested the custom framerate feature from v0.8.4 with game version 1.01, but it does not seem to work.
First I set DLSS to DLAA, disabled frame generation, selected the 60fps target and enabled DRS, the game is then correctly locking at 60fps, loading the GPU with ~80% according to RTS. Then I switched the target framerate to 40, worked as expected. Then when I selected the 30.00 FPS target the game locked to 30fps, and not to the 50fps I set in the ini file.
I also tried to restart the game with all settings in place, but that is also not working.
I attached the log file and my settings as FFXVIFix.ini.txt
FFXVIFix.log
FFXVIFix.ini.txt

I tested the custom framerate feature from v0.8.4 with game version 1.01, but it does not seem to work. First I set DLSS to DLAA, disabled frame generation, selected the 60fps target and enabled DRS, the game is then correctly locking at 60fps, loading the GPU with ~80% according to RTS. Then I switched the target framerate to 40, worked as expected. Then when I selected the 30.00 FPS target the game locked to 30fps, and not to the 50fps I set in the ini file. I also tried to restart the game with all settings in place, but that is also not working.
I attached the log file and my settings as FFXVIFix.ini.txt FFXVIFix.log FFXVIFix.ini.txt

If you set "30.00 FPS" in the menu, then click "Frame Rate" again, does it show your custom framerate target? I can't speak to how it works with dynamic resolution system as that's not something I have looked into yet.
This is how it looks on my end with 50fps set.
[Custom Framerate]
; Set enabled to true to replace the "30.00 FPS" frame rate option in-game with a custom value set below.
; Bear in mind that this framerate value is applied prior to frame generation.
Enabled = true
Framerate = 50

No, on my end the 50.00 FPS option does not show up in the menu at all. Compared to your screenshot I have additional FPS options like 29.97 or 59.94, which I think is, because I am playing on a TV, not a PC monitor. Could it maybe because of these additional FPS options available on my end, that FFXVIfix is cannot inject the custom FPS value?

authors: Drahsid Lyall weltuntergang666

repo: Lyall/FFXVIFix


text:
layer per stage

Hi
I notice there is a "layer_per_stage" parameter in cifar100 pytorch implementation:
https://github.com/Lyken17/SparseNet/blob/master/src/pytorch/denselink.py#L154
model1-BC (depth=100, k1=16, k2=32, k3=64)
model2-BC (depth=100, k1=32,k2=64,k3=128)
What is the exact parameter in these two models?
Thanks a lot

Any update? Thanks a lot @Lyken17

My implementation of sparsenet-BC on cifar100 (d=100, k=32,64,128) validation error is 20.24%, which is 2% percent higher than 18.22%, I think it is due to the layer_per_stage(parameter in my implementaion is 17.34M, while is 16.7M in the github results, I Tried different layer-per-stage, however didnot get 16,7M), which the paper did not give.
Since I want to cite your paper's results for my model, therefore I need to reimplement your network and get similar results first
Looking forward to your  reply @Lyken17

For other network settings, I get similiary outputs in paper
For example, model-BC d_100_k_24 is 22.71%(your), 22.97%(my)
@Lyken17

@Lyken17

I asked the author through e-mail, and he says the parameter layer_per_stage was not enabled.

Hi, I add the densenet-bottleneck tensorflow version
#!/usr/bin/env python
# -*- coding: UTF-8 -*-

import numpy as np
import tensorflow as tf
import argparse
import os

from tensorpack import *
from tensorpack.tfutils.symbolic_functions import *
from tensorpack.tfutils.summary import *
# import math

"""
CIFAR10 DenseNet example. See: http://arxiv.org/abs/1608.06993
Code is developed based on Yuxin Wu's ResNet implementation: https://github.com/ppwwyyxx/tensorpack/tree/master/examples/ResNet
Results using DenseNet (L=40, K=12) on Cifar10 with data augmentation: ~5.77% test error.

Running time:
On one TITAN X GPU (CUDA 7.5 and cudnn 5.1), the code should run ~5iters/s on a batch size 64.

Reimplementation notes:

"""

BATCH_SIZE = 64

class Model(ModelDesc):
    def __init__(self, depth, growth_rate, fetch,
                 bottleneck, compression=1, dropout=0,
                 num_classes=10):

        super(Model, self).__init__()
        self.N = int((depth - 4) / 3)
        self.growthRate = growth_rate
        self.fetch = fetch
        self.bottleneck = bottleneck
        self.compression = compression
        self.num_classes = num_classes
        # print('*** self.fetch', self.fetch)

    def _get_inputs(self):
        return [InputDesc(tf.float32, [None, 32, 32, 3], 'input'),
                InputDesc(tf.int32, [None], 'label')]

    def _build_graph(self, input_vars):
        image, label = input_vars
        image = image / 128.0 - 1 # convert range to -1 ~ 1

        from .utils import conv3x3, conv1x1, add_layer, add_layer_without_concat, add_transition, add_bottleneck_transition,add_bottleneck_without_concat

        def dense_net(name, num_classes=10):
            l = conv3x3('conv0', image, 16, 1)

            from .utils import linearFetch, expFetch
            if self.fetch == "dense":
                fetch = linearFetch
            else:
                fetch = expFetch
            # print('***fetch', fetch)

            # stage 1
            with tf.variable_scope('block1') as scope:
                saved_activations = [l]
                for i in range(self.N):
                    if not self.bottleneck:
                       l = add_layer_without_concat('densen_layer.{}'.format(i), l, self.growthRate[0])
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)
                       # l = add_transition('transition1', l)
                    else:
                       l = add_bottleneck_without_concat('densen_layer.{}'.format(i), l, self.growthRate[0])
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)
                       # l = add_bottleneck_transition('transition1', l)
                if not self.bottleneck:
                   l = add_transition('transition1', l)
                else:
                   l = add_bottleneck_transition('transition1', l)
            # print('*** after stage1, l', l) # (?,16,16,96)

            # stage 2
            with tf.variable_scope('block2') as scope:
                saved_activations = [l]
                for i in range(self.N):
                    if not self.bottleneck:
                       l = add_layer_without_concat('densen_layer.{}'.format(i), l, self.growthRate[1])
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)
                       # l = add_transition('transition2', l)
                    else:
                       l = add_bottleneck_without_concat('densen_layer.{}'.format(i), l, self.growthRate[1])
                       # print('*** l', i, l)
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)
                       # l = add_bottleneck_transition('transition2', l)
                if not self.bottleneck:
                   l = add_transition('transition2', l)
                else:
                   l = add_bottleneck_transition('transition2', l)

            # stage 3
            with tf.variable_scope('block3') as scope:
                saved_activations = [l]
                for i in range(self.N):
                    if not self.bottleneck:
                       l = add_layer_without_concat('densen_layer.{}'.format(i), l, self.growthRate[2])
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)
                    else:
                       l = add_bottleneck_without_concat('densen_layer.{}'.format(i), l, self.growthRate[2])
                       saved_activations.append(l)
                       l = tf.concat(fetch(saved_activations), 3)

            l = BatchNorm('bn_last', l)
            l = tf.nn.relu(l)
            l = GlobalAvgPooling('gap', l)
            logits = FullyConnected('linear', l, out_dim=self.num_classes, nl=tf.identity)

            return logits

        logits = dense_net("dense_net")

        prob = tf.nn.softmax(logits, name='output')

        cost = tf.nn.sparse_softmax_cross_entropy_with_logits(logits=logits, labels=label)
        cost = tf.reduce_mean(cost, name='cross_entropy_loss')

        # wrong = prediction_incorrect(logits, label)
        wrong = tf.cast(tf.logical_not(tf.nn.in_top_k(logits, label, 1)), tf.float32, name='wrong_vector')

        # monitor training error
        add_moving_summary(tf.reduce_mean(wrong, name='train_error'))

        # weight decay on all W
        wd_cost = tf.multiply(1e-4, regularize_cost('.*/W', tf.nn.l2_loss), name='wd_cost')
        add_moving_summary(cost, wd_cost)

        add_param_summary(('.*/W', ['histogram']))  # monitor W
        self.cost = tf.add_n([cost, wd_cost], name='cost')

    def _get_optimizer(self):
        lr = tf.get_variable('learning_rate', initializer=0.1, trainable=False)
        tf.summary.scalar('learning_rate', lr)
        return tf.train.MomentumOptimizer(lr, 0.9, use_nesterov=True)

However, the total parameter of the network is 4.087M on cifar100 and 4.052M on cifar10
Can you have a look at this program?
Looking forward to your reply


text:
🛑 Documentation Page is down

In 091d1ee, Documentation Page (https://docs.lyrid.io/img/lyridsvg.svg) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Documentation Page is back up in 811daf0 after 3 minutes.

repo: LyridInc/statuspage


text:
About the ribseg dataset

Hello, I want to locate the location of my rib fracture (for example, the first one on the left or the fifth one on the right). Therefore, I need a CT file with 24 rib segmentation masks, calculate its bbox coordinates according to the mask marks of each rib, and then match it with the bbox coordinates of the rib fracture I detected, so as to locate. Can the CT of the ribseg dataset achieve my goal?

do you know ModuleNotFoundError: No module named 'models.SegNet'？

it should be the relative path, simply changing it to absolute path should work

authors: BelieferQAQ Kingxudong ShixuanGu


text:
put modal popup confirmation to withdraw before 0.1

just because the fee is higher before 0.1XMR
Thanks

Very good idea. We'll be reworking that whole transaction area and this is a strong addition. Thank you.

authors: Thunderosa octapudus


text:
Test documentation and failing slow running tests

First, a small paragraph on how users can run the tests with pytest and what the machine requirements are (cuda), with a mention of the --runslow option would be expected in the README.
I was able to run the "fast" tests with success, but I encountered errors with the slow running tests.

The test_field_divergence test fails due to missing cuda device (expected), but perhaps the test could be skipped in the absence of an available cuda device.
The test_nnparams_load_trained_TAUNET and test_nnparams_load_trained_CUSTOMMLP fail because the object OnePointSpectraDataGenerator is instantiated without the zref argument:

    @pytest.mark.slow
    def test_nnparams_load_trained_CUSTOMMLP():
        pb = CalibrationProblem(
            nn_params=NNParameters(
                nlayers=2, hidden_layer_sizes=[10, 10], activations=[nn.GELU(), nn.ReLU()]
            ),
            prob_params=ProblemParameters(
                nepochs=2, eddy_lifetime=EddyLifetimeType.CUSTOMMLP
            ),
            loss_params=LossParameters(alpha_pen2=1.0, alpha_pen1=1.0e-5, beta_reg=2e-4),
            phys_params=PhysicalParameters(L=L, Gamma=Gamma, sigma=sigma, domain=domain),
            device=device,
        )

        k1_data_pts = domain
        DataPoints = [(k1, 1) for k1 in k1_data_pts]

>       Data = OnePointSpectraDataGenerator(data_points=DataPoints).Data
E       TypeError: OnePointSpectraDataGenerator.__init__() missing 1 required positional argument: 'zref'

test/io/test_model_params.py:123: TypeError

Please clarify if this is the expected behaviour.

I saw that the slow running tests are not run on each commit, so maybe that's the issue...

Hi. These have been fixed in #103 and the slow tests are now run on all push/pull-request to main.

Could you just add that --runslow is a pytest option in the development installation instructions, so users who want to run the tests don't have to go read the test code to figure this out ?

Good !

authors: mjachi olivecha

repo: METHODS-Group/DRDMannTurb


text:
Pandas intro

The intro of jupyter notebook with some code of panda use introduction of meeting

I have added new notebook with continued work of Global Trends DS exploration


text:
roslaunch error

Description:
Ubuntu 18.04
ROS: melodic
When i tried to run roslaunch kimera_vio_ros_euroc.launch, i got such output errors:
Command:
roslaunch kimera_vio_ros kimera_vio_ros_euroc.launch

Console output:

... logging to /home/hzq/.ros/log/d81405e8-a4f7-11eb-b60f-c46516114b0c/roslaunch-hzq-19301.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://hzq:45941/

SUMMARY
========

PARAMETERS
 * /gt_accel_bias: [-0.012492, 0.547...
 * /gt_gyro_bias: [-0.002229, 0.020...
 * /kimera_vio_ros/kimera_vio_ros_node/base_link_frame_id: base_link
 * /kimera_vio_ros/kimera_vio_ros_node/ground_truth_odometry_rosbag_topic:
 * /kimera_vio_ros/kimera_vio_ros_node/imu_rosbag_topic: /imu0
 * /kimera_vio_ros/kimera_vio_ros_node/left_cam_frame_id: cam0
 * /kimera_vio_ros/kimera_vio_ros_node/left_cam_rosbag_topic: /cam0/image_raw
 * /kimera_vio_ros/kimera_vio_ros_node/log_gt_data: False
 * /kimera_vio_ros/kimera_vio_ros_node/map_frame_id: map
 * /kimera_vio_ros/kimera_vio_ros_node/mono_ransac_threshold: 30
 * /kimera_vio_ros/kimera_vio_ros_node/online_run: False
 * /kimera_vio_ros/kimera_vio_ros_node/params_folder_path: /home/hzq/my_spac...
 * /kimera_vio_ros/kimera_vio_ros_node/position_det_threshold: 0.3
 * /kimera_vio_ros/kimera_vio_ros_node/right_cam_frame_id: cam1
 * /kimera_vio_ros/kimera_vio_ros_node/right_cam_rosbag_topic: /cam1/image_raw
 * /kimera_vio_ros/kimera_vio_ros_node/rosbag_path: /home/hzq/dataset...
 * /kimera_vio_ros/kimera_vio_ros_node/stereo_ransac_threshold: 20
 * /kimera_vio_ros/kimera_vio_ros_node/use_lcd: False
 * /kimera_vio_ros/kimera_vio_ros_node/use_online_cam_params: False
 * /kimera_vio_ros/kimera_vio_ros_node/velocity_det_threshold: 0.1
 * /kimera_vio_ros/kimera_vio_ros_node/world_frame_id: world
 * /kimera_vio_ros/posegraph_viewer/frame_id: world
 * /rosdistro: melodic
 * /rosversion: 1.14.10
 * /use_sim_time: True

NODES
  /kimera_vio_ros/
    kimera_vio_ros_node (kimera_vio_ros/kimera_vio_ros_node)
    posegraph_viewer (pose_graph_tools/visualizer_node)

auto-starting new master
process[master]: started with pid [19311]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to d81405e8-a4f7-11eb-b60f-c46516114b0c
process[rosout-1]: started with pid [19322]
started core service [/rosout]
process[kimera_vio_ros/kimera_vio_ros_node-2]: started with pid [19329]
process[kimera_vio_ros/posegraph_viewer-3]: started with pid [19330]
[ INFO] [1619266996.333315824]: Initializing pose graph visualizer
I0424 20:23:16.524582 19329 Logger.cpp:59] Opening output file: traj_gt.csv
I0424 20:23:16.525610 19329 RosBagDataProvider.cpp:52] Constructing RosbagDataProvider from path:
 - Rosbag Path: /home/hzq/dataset/euroc/MH_01_easy.bag
With ROS topics:
 - Left cam: /cam0/image_raw
 - Right cam: /cam1/image_raw
 - IMU: /imu0
 - GT odom:
I0424 20:23:16.526614 19329 RosBagDataProvider.cpp:83] Initialize Rosbag Data Provider.
I0424 20:23:16.526623 19329 RosBagDataProvider.cpp:201] Parsing rosbag data.
F0424 20:23:16.547317 19329 RosBagDataProvider.cpp:222] Check failed: vio_params_.backend_params_->autoInitialize_ == 1 (0 vs. 1) Requested ground-truth initialization, but no gt_odom_topic was given. Make sure you set ground_truth_odometry_rosbag_topic, or turn autoInitialize to false in BackendParameters.yaml.
*** Check failure stack trace: ***
    @     0x7f01cd846b0d  google::LogMessage::Fail()
    @     0x7f01cd8489b1  google::LogMessage::SendToLog()
    @     0x7f01cd84663d  google::LogMessage::Flush()
    @     0x7f01cd849389  google::LogMessageFatal::~LogMessageFatal()
    @     0x7f01cd00c8e8  VIO::RosbagDataProvider::parseRosbag()
    @     0x7f01cd00d121  VIO::RosbagDataProvider::initialize()
    @     0x7f01ccffaa2b  VIO::KimeraVioRos::createDataProvider()
    @     0x7f01ccffb57f  VIO::KimeraVioRos::runKimeraVio()
    @     0x561b23a77b2a  (unknown)
    @     0x7f01cbca4bf7  __libc_start_main
    @     0x561b23a7803a  (unknown)
[kimera_vio_ros/kimera_vio_ros_node-2] process has died [pid 19329, exit code -6, cmd /home/hzq/my_space/devel/lib/kimera_vio_ros/kimera_vio_ros_node --use_lcd=false --vocabulary_path=/home/hzq/my_space/src/Kimera-VIO/vocabulary/ORBvoc.yml --flagfile=/home/hzq/my_space/src/Kimera-VIO/params/Euroc/flags/Mesher.flags --flagfile=/home/hzq/my_space/src/Kimera-VIO/params/Euroc/flags/VioBackend.flags --flagfile=/home/hzq/my_space/src/Kimera-VIO/params/Euroc/flags/RegularVioBackend.flags --flagfile=/home/hzq/my_space/src/Kimera-VIO/params/Euroc/flags/Visualizer3D.flags --logtostderr=1 --colorlogtostderr=1 --log_prefix=1 --v=0 --log_output=false --log_euroc_gt_data=false --output_path=/home/hzq/my_space/src/Kimera-VIO-ROS/output_logs/ --viz_type=0 --visualize=true reinit_flag:=reinit_flag reinit_pose:=reinit_pose odometry:=odometry resiliency:=resiliency imu_bias:=imu_bias optimized_trajectory:=optimized_trajectory pose_graph:=pose_graph mesh:=mesh frontend_stats:=frontend_stats debug_mesh_img/image_raw:=debug_mesh_img/image_raw feature_tracks/image_raw:=feature_tracks/image_raw time_horizon_pointcloud:=time_horizon_pointcloud __name:=kimera_vio_ros_node __log:=/home/hzq/.ros/log/d81405e8-a4f7-11eb-b60f-c46516114b0c/kimera_vio_ros-kimera_vio_ros_node-2.log].
log file: /home/hzq/.ros/log/d81405e8-a4f7-11eb-b60f-c46516114b0c/kimera_vio_ros-kimera_vio_ros_node-2*.log

Additional files:
Please attach all the files needed to reproduce the error.
Please give also the following information:

KimeraVIO branch, tag or commit used:lastest master
GTSAM version used:default
OpenGV version used:default
OpenCV version used: 3.4.1
Operating system and version Ubuntu 18.04
Did you change the source code? (yes / no): no

when i look into source code, i found the var 'autoInitialize' has been set to 0. why the roslaunch still wants me to set it to false in BackendParameters.yaml?

hi,
Do you solve it?
I have the same issue.

Hi,
I solved the problem in a wired way.
I changed the value of autoInitialize to 1 in the configure file. And it works
Best wishes and good luck~

2021年5月19日 下午4:25，zheng-xiao @.***> 写道：
hi,
Do you solve it?
I have the same issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/MIT-SPARK/Kimera-VIO-ROS/issues/141#issuecomment-843869669, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHVZ5BF4XMJLJE5SJKP7LRDTONYXVANCNFSM43QDZECA.

i sovled the problem by changing the value of 'autoInitialize' to 1 in the configure file, and it works.

how did u set the rospath in the RosbagDataProvider.cpp to the location where you have your ros bag?
I mean this
Rosbag Path: /home/hzq/dataset/euroc/MH_01_easy.bag
Any help would be much appreciated. Thank you.

... logging to /home/umer/.ros/log/6939e404-9936-11ee-b525-1f53059cc506/roslaunch-084-17380.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://192.168.18.11:36815/
SUMMARY
PARAMETERS

/gt_accel_bias: [-0.012492, 0.547...
/gt_gyro_bias: [-0.002229, 0.020...
/kimera_vio_ros/kimera_vio_ros_node/base_link_frame_id: base_link
/kimera_vio_ros/kimera_vio_ros_node/bow_batch_size: 1
/kimera_vio_ros/kimera_vio_ros_node/bow_skip_num: 1
/kimera_vio_ros/kimera_vio_ros_node/depth_cam_rosbag_topic:
/kimera_vio_ros/kimera_vio_ros_node/external_odometry_rosbag_topic:
/kimera_vio_ros/kimera_vio_ros_node/force_same_image_timestamp: True
/kimera_vio_ros/kimera_vio_ros_node/ground_truth_odometry_rosbag_topic:
/kimera_vio_ros/kimera_vio_ros_node/image_transport: raw
/kimera_vio_ros/kimera_vio_ros_node/imu_rosbag_topic: /imu0
/kimera_vio_ros/kimera_vio_ros_node/left_cam_frame_id: cam0
/kimera_vio_ros/kimera_vio_ros_node/left_cam_rosbag_topic: /cam0/image_raw
/kimera_vio_ros/kimera_vio_ros_node/log_gt_data: False
/kimera_vio_ros/kimera_vio_ros_node/map_frame_id: map
/kimera_vio_ros/kimera_vio_ros_node/mono_ransac_threshold: 30
/kimera_vio_ros/kimera_vio_ros_node/odom_frame_id: odom
/kimera_vio_ros/kimera_vio_ros_node/online_run: False
/kimera_vio_ros/kimera_vio_ros_node/params_folder_path: /home/umer/catkin...
/kimera_vio_ros/kimera_vio_ros_node/position_det_threshold: 0.3
/kimera_vio_ros/kimera_vio_ros_node/publish_vlc_frames: True
/kimera_vio_ros/kimera_vio_ros_node/right_cam_frame_id: cam1
/kimera_vio_ros/kimera_vio_ros_node/right_cam_rosbag_topic: /cam1/image_raw
/kimera_vio_ros/kimera_vio_ros_node/robot_id: 0
/kimera_vio_ros/kimera_vio_ros_node/rosbag_path:
/kimera_vio_ros/kimera_vio_ros_node/sensor_params_folder_path:
/kimera_vio_ros/kimera_vio_ros_node/stereo_ransac_threshold: 20
/kimera_vio_ros/kimera_vio_ros_node/use_external_odom: False
/kimera_vio_ros/kimera_vio_ros_node/use_lcd: False
/kimera_vio_ros/kimera_vio_ros_node/use_lcd_registration_server: False
/kimera_vio_ros/kimera_vio_ros_node/use_rviz: True
/kimera_vio_ros/kimera_vio_ros_node/velocity_det_threshold: 0.1
/kimera_vio_ros/posegraph_viewer/frame_id: map
/rosdistro: noetic
/rosversion: 1.16.0
/use_sim_time: True

NODES
/kimera_vio_ros/
kimera_vio_ros_node (kimera_vio_ros/kimera_vio_ros_node)
posegraph_viewer (pose_graph_tools/visualizer_node)
ROS_MASTER_URI=http://localhost:11311
process[kimera_vio_ros/kimera_vio_ros_node-1]: started with pid [17394]
process[kimera_vio_ros/posegraph_viewer-2]: started with pid [17395]
[ INFO] [1702418197.561855348]: Initializing pose graph visualizer
ERROR: unknown command line flag 'colorlogtostderr'
ERROR: unknown command line flag 'log_prefix'
ERROR: unknown command line flag 'logtostderr'
ERROR: unknown command line flag 'minloglevel'
ERROR: unknown command line flag 'v'
================================================================================REQUIRED process [kimera_vio_ros/kimera_vio_ros_node-1] has died!
process has died [pid 17394, exit code 1, cmd /home/umer/catkin_ws/devel/lib/kimera_vio_ros/kimera_vio_ros_node --use_lcd=false --vocabulary_path=/home/umer/catkin_ws/src/Kimera-VIO/vocabulary/ORBvoc.yml --flagfile=/home/umer/catkin_ws/src/Kimera-VIO/params/Euroc/flags/Mesher.flags --flagfile=/home/umer/catkin_ws/src/Kimera-VIO/params/Euroc/flags/VioBackend.flags --flagfile=/home/umer/catkin_ws/src/Kimera-VIO/params/Euroc/flags/RegularVioBackend.flags --flagfile=/home/umer/catkin_ws/src/Kimera-VIO/params/Euroc/flags/Visualizer3D.flags --use_external_odometry=false --do_coarse_imu_camera_temporal_sync=false --do_fine_imu_camera_temporal_sync=false --lcd_no_optimize=false --lcd_no_detection=false --depth_image_mask= --logtostderr=1 --colorlogtostderr=1 --log_prefix=1 --minloglevel=0 --v=0 --log_output=false --log_euroc_gt_data=false --output_path=/home/umer/catkin_ws/src/Kimera-VIO-ROS/output_logs/ --lcd_disable_stereo_match_depth_check=false --no_incremental_pose=false --viz_type=0 --visualize=true reinit_flag:=reinit_flag reinit_pose:=reinit_pose odometry:=odometry resiliency:=resiliency imu_bias:=imu_bias optimized_trajectory:=optimized_trajectory pose_graph:=pose_graph mesh:=mesh frontend_stats:=frontend_stats debug_mesh_img/image_raw:=debug_mesh_img/image_raw feature_tracks/image_raw:=feature_tracks/image_raw time_horizon_pointcloud:=time_horizon_pointcloud __name:=kimera_vio_ros_node __log:=/home/umer/.ros/log/6939e404-9936-11ee-b525-1f53059cc506/kimera_vio_ros-kimera_vio_ros_node-1.log].
log file: /home/umer/.ros/log/6939e404-9936-11ee-b525-1f53059cc506/kimera_vio_ros-kimera_vio_ros_node-1*.log
Initiating shutdown!
[kimera_vio_ros/posegraph_viewer-2] killing on exit
[kimera_vio_ros/kimera_vio_ros_node-1] killing on exit
shutting down processing monitor...
... shutting down processing monitor complete
done
can any one guide me, how to get rid of this error

Hi. I had the same error. Did you solve it? I tried setting autoInitialize to 1 but this didn't work.

authors: Abirami-Segar avaniab huziqi umer1223 zheng-xiao

repo: MIT-SPARK/Kimera-VIO-ROS


text:
[ENH] add eta to rbcs for nonlinear free surface

What changes does this PR introduce?
Draft for comment: obcs allows setting etaH, but I wanted an rbcs-type sponge, so I added this to rbcs.
This is potentially valuable for fjords and other embayments where we want to force the tide via sea surface height in a large receiving basin.  I do this by adjusting the sponge in the receiving basin so that the surface wave is free in the fjord itself.
Does this PR introduce a breaking change?
No
Other information:
I have a simple version of a toy model that works with this at https://github.com/jklymak/FjordForce. That example could be simplified, its just a simulation I had that had a reasonable fjord with large receiving basin set up.

[ ] Needs documentation
[ ] Needs tests?

One thing I'm not clear on - for obcs they have a calculation for OBCS_APPLY_SURF_DR.  I wasn't clear if this was needed here, or because I was directly manipulating etaH it would get calculated in CALC_SURF_DR.

Thanks @mjlosch for taking a look.  For my testing, did you run exp4.nlfs as-is, or did you modify at all?

I just checked out the branch and ran ./testreport -t 'exp4.nlfs tutorial_reentrant_channel with and without the -devel option. I did this on my MacBook with gfortran. If you cannot reproduce that, I'll have a closer look.

Thanks - I can have a look in a few days.

Thanks @mjlosch  this passes that test report.  I added an if statement to rbc_apply_eta.F.
Happy to write a test for this setup.

@jklymak thanks for sharing your code.
I was supposed to look at this PR a long time ago but a little busy these days.
There are several things that I would need to check (including how this fit into time-stepping with various options) as it affects the continuity equation and might affect tracer conservation.
This would not be an issue if the relaxation was only used near Open-Boundary (part of a "sponge layer") but might not always be the case.
The other thing is that we are considering an alternative implementation of  Open-Boundary Conditions that would allow naturally to prescribe the SSH at the OB and account for the pressure gradient across the OB.
If this was available and working, it might be used instead of this Eta relaxation, at least in some cases.
So I would suggest we keep this PR open and keep it up-to-date (will merge latest master branch in) and decide later which direction to take.

Thanks @jm-c  - I use this in an a-physical sponge part of the domain where I would also sponge active and passive tracers, so I don't consider tracer conservation important in my use cases.  I'm not sure use cases where a-physically forcing eta could conserve anything (definitely not mass!) but perhaps there are such use cases...

authors: jklymak jm-c mjlosch

repo: MITgcm/MITgcm


text:
Safari ignores hashtags in hyperlinked URL

http://i.imgur.com/UTWxiEJ.gifv
In gif, user is directed to authentication with MLH
Then redirected to our server with the access token
But because of the Hashtag, the data is deleted and redirected to server without data
More info:
http://stackoverflow.com/questions/18663410/safari-ignoring-removing-hashatags-when-clicking-hyperlinks
Solution suggestion: convert to using question marks instead of hashtags :)

Hi Aron,
It's actually intentional (and part of the OAuth protocol) for the access_token to be passed through as a # / hashtag parameter because that way it isn't visible by the server and the server logs.
If you use the MyMLH Authorization Code Flow you'll be able to receive everything as a ? / question mark parameter as that's a far more securer and better recommended flow for MyMLH applications.
With that being said, I wasn't aware that safari does not have full support for hashtags. We'll debate this internally and see if there's any solutions we can roll out. Hope that helps!

Thanks Bilawal! That helps, we're currently looking into solutions on our side.
Thanks for replying so quickly!

You're welcome!

Hi Bilawal, I am also working on the project with the issue.
I will setup the application to use the Authorization Code Flow, but I initially did not as the documentation mentions

You wouldn't want to use this on your client side application because your application's secret token would be exposed to the world.

Our application is a client application and users will only be accessing information about their profile.  Would it still be acceptable / safe to use that flow?  I was under the impression that this flow should only be used for those that need access to all registered users (Organizers and etc.).  I am confident that this flow would resolve the problem, but I do not want to sacrifice security.

Hi csinko,
You shouldn't use the Authorization Code Flow on a client-side only application. That's why the Implicit Flow exists, because in the ideal world, we'd want everyone to use Authorization Code Flow.
Realistically, the best option you have right now is to create a very lightweight backend that contains these credentials and makes requests to MyMLH. Then your mobile application can connect to your backend which will connect to MyMLH. This would also be great for a client side application as it could connect to a backend. It's not ideal at all, and we'll be investigating ways to make this easier, but it's a viable option for now.
And we'll be investigating the following:

Workaround for storing client ID and secret in a mobile app that can be decompiled
Implicit Grant Flow with support for browsers with little hashtag support in URLs

Hope this makes things clearer. Cheers!

bih,
I have read more into the Safari issue and was able to get a working solution without much change.
The issue is occurring due to the fact that I have our webserver doing a 301 forward from http traffic to https.  A common way to have it setup, and something that you set and forget, as all traffic ends up going to https as desired.  Safari was dropping the # variables during the 301 redirect, while other browsers do not.
The solution was to simply update our callback URL to include "https" so that the 301 redirect process is not needed, and it is working great now!

Ah okay, glad to hear that you were able to fix it. Let me know if you have any other questions. 👍

authors: agates4 bih csinko

repo: MLH/my-mlh-omniauth


text:
Preprocessing adds unique IDs to data

Somewhere in our preprocessing steps, the fullVisitorId gets screwed up. From the load notebook:
train = load("../data/train.csv", nrows=10000)
test = load("../data/test.csv", nrows=None)
print(test["fullVisitorId"].nunique())

Loaded file ../data/train.csv
Shape is: (10000, 54)
Loaded file ../data/test.csv
Shape is: (804684, 53)
617242
NOTE: so far it is correct, the expected number of IDs is 617242. But after the next step:
train_processed, test_processed = process(train, test)
print(test_processed["fullVisitorId"].nunique())

Dropping constant columns...
Generating date columns...
Finding total visits...
Splitting back...
618207
There is suddenly a thousand more. Clearly, this way we cannot produce the required predictions. This happened before when we didn't read the fullVisitorId column as a string. Now we do, but somewhere in process() it seems to go wrong. The number of observations in the datasets does not change, so I guess it is a data type thing. Is it implicitly converted to numeric somewhere?

Got a fix, PR coming up.

Out of curiosity, can you point out where the error happened in the PR or here?

I'm not entirely sure where, but somewhere when working on the merged/concatenated data, the data is sorted. Probably some internal Pandas thing?

This behavior changed between pandas version but I though the sort argument: merged = pd.concat([train, test], sort=False)  would take care of this. Apparently it doesn't

Oh but I see, the problem happens after the merge. So it could be anything. Your fix seems fine to be though let's merge asap.

Yeah exactly, in one of the preprocessing steps after merging and before splitting, but it's hard to say where. So this was the quickest solution I guess.

authors: joepvdbogaert steremma


text:
sideNavでのhistory.push

sadeNavファイルにthis.props.history.push('/setting')とすると、できないと言われるのですが、これがリンクの元のページだからでしょうか？
このようなファイル上ではどのようにパスを設定したらいいでしょうか？

できないと言われるというのは、具体的にどのようなエラーでしょうか。

このようなエラーです
`TypeError: Cannot read property 'push' of undefined
SideNav._this.settingClick
src/components/SideNav.js:55
52 | };
53 |
54 | settingClick=()=>{

55 |   this.props.history.push('/setting')
56 | }
57 |
58 | handleClose = () => this.setState({ open: false })`

historyがundefinedになっているってことですよね。
historyがpropsとして渡されるのはRouteに指定したcomponentだけです。
それ以外で利用したい場合はwithRouterを使うとできると思います。
withRouter - React Router

ありがとうございます。遷移できるようになりました。

authors: MOTOMUR karamari


text:
[bug] Automatic upload for shared collection not working

Testserver: qa-gluons user: catherina@brauchma.net
Test date: 04.08.2016
Device: Tablet Nexus 9 Android 5.1.1.
User:
Action: Testcase CAM-44:Upload metadata to collection without MDP (user) (Tablet Nexus 9)
->other user shared the collection with user (read+update)
-> automatic upload to "coll 160804 without MDP shared with test001"
-> camera symbol
-> take fotos
Observation: no upload task running and no fotos uploaded
Manual upload works fine.
Expected result: User only with upload grants for the collectin is able to upload automatically

can't reproduce with HTC tablet and Samsung

authors: hofmannc liyyil

repo: MPDL/LabCam


text:
Weather Information shows wrong time

Where does this bug apply to
Weather Information layer
Describe the bug
Time indicated on the graph are wrong. Example time at track 1224, time shown in the weather info graph 1424
Expected behavior
Time shown in the weather info window to current to be like on track
Desktop (please complete the following information):
MacOS ventura latest release.
Ulmv latest release

Thanks for reporting. The issue is fixed for the next release!

authors: LUXADSBACARS MRAJEKO