text:
Numpy<1.24 due to f90wrap incompatibility

See https://github.com/jameskermode/f90wrap/issues/175
NumPy 1.24 ships with "new f2py features and fixes": https://numpy.org/doc/stable/release/1.24.0-notes.html
This requirement can be relaxed once f90wrap has caught up.

Codecov Report

Merging #11 (f750d0f) into main (60ee964) will increase coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #11      +/-   ##
==========================================
+ Coverage   90.85%   91.06%   +0.21%
==========================================
  Files          84       75       -9
  Lines       14155    13225     -930
==========================================
- Hits        12860    12044     -816
+ Misses       1295     1181     -114

Flag
Coverage Δ

lint_rules
?

loki
91.06% <ø> (-0.04%)
:arrow_down:

transformations
?

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

Impacted Files
Coverage Δ

loki/frontend/regex.py
95.93% <0.00%> (-0.60%)
:arrow_down:

loki/build/workqueue.py
66.19% <0.00%> (-0.47%)
:arrow_down:

loki/visitors/visitor.py
79.62% <0.00%> (-0.38%)
:arrow_down:

loki/lint/rules.py
96.61% <0.00%> (-0.32%)
:arrow_down:

loki/transform/fortran_max_transform.py
97.05% <0.00%> (-0.30%)
:arrow_down:

loki/frontend/ofp.py
97.23% <0.00%> (-0.09%)
:arrow_down:

loki/frontend/source.py
96.83% <0.00%> (-0.02%)
:arrow_down:

loki/visitors/find.py
99.03% <0.00%> (-0.01%)
:arrow_down:

loki/backend/fgen.py
96.84% <0.00%> (-0.01%)
:arrow_down:

loki/frontend/omni.py
96.19% <0.00%> (-0.01%)
:arrow_down:

... and 9 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: codecov-commenter reuterbal

repo: ecmwf-ifs/loki


text:
Permalink for ice sheet mass change notebook 1

Data Type
Satellite ECVs - Land Hydrology & Cryosphere
Assessment Category
Uncertainty
Dataset Name
satellite-ice-sheet-mass-balance
Question Number
1
Workflow ID
eqctier3-69b5b542-7776-4fd6-899e-e8f218e83852
Zipped Notebook
ice_sheet_gmb-1.ipynb.zip
Environment

name: wp5
channels:
  - conda-forge
dependencies:
  - _libgcc_mutex=0.1=conda_forge
  - _openmp_mutex=4.5=2_gnu
  - affine=2.4.0=pyhd8ed1ab_0
  - aiohttp=3.9.5=py311h459d7ec_0
  - aiosignal=1.3.1=pyhd8ed1ab_0
  - alsa-lib=1.2.12=h4ab18f5_0
  - annotated-types=0.7.0=pyhd8ed1ab_0
  - ansicolors=1.1.8=pyhd8ed1ab_0
  - antlr-python-runtime=4.11.1=pyhd8ed1ab_0
  - anyio=4.4.0=pyhd8ed1ab_0
  - argon2-cffi=23.1.0=pyhd8ed1ab_0
  - argon2-cffi-bindings=21.2.0=py311h459d7ec_4
  - arrow=1.3.0=pyhd8ed1ab_0
  - asciitree=0.3.3=py_2
  - asttokens=2.4.1=pyhd8ed1ab_0
  - async-lru=2.0.4=pyhd8ed1ab_0
  - attr=2.5.1=h166bdaf_1
  - attrs=23.2.0=pyh71513ae_0
  - aws-c-auth=0.7.22=hf36ad8f_6
  - aws-c-cal=0.6.15=h816f305_1
  - aws-c-common=0.9.23=h4ab18f5_0
  - aws-c-compression=0.2.18=he027950_7
  - aws-c-event-stream=0.4.2=hb72ac1a_14
  - aws-c-http=0.8.2=h75ac8c9_3
  - aws-c-io=0.14.9=hd3d3696_3
  - aws-c-mqtt=0.10.4=hb0abfc5_7
  - aws-c-s3=0.5.10=h44b787d_4
  - aws-c-sdkutils=0.1.16=he027950_3
  - aws-checksums=0.1.18=he027950_7
  - aws-crt-cpp=0.26.12=he940a02_1
  - aws-sdk-cpp=1.11.329=h0f5bab0_6
  - azure-core-cpp=1.12.0=h830ed8b_0
  - azure-identity-cpp=1.8.0=hdb0d106_1
  - azure-storage-blobs-cpp=12.11.0=ha67cba7_1
  - azure-storage-common-cpp=12.6.0=he3f277c_1
  - azure-storage-files-datalake-cpp=12.10.0=h29b5301_1
  - babel=2.14.0=pyhd8ed1ab_0
  - beautifulsoup4=4.12.3=pyha770c72_0
  - bleach=6.1.0=pyhd8ed1ab_0
  - blosc=1.21.6=hef167b5_0
  - bokeh=3.4.2=pyhd8ed1ab_0
  - bottleneck=1.4.0=py311h18e1886_1
  - branca=0.7.2=pyhd8ed1ab_0
  - brotli=1.1.0=hd590300_1
  - brotli-bin=1.1.0=hd590300_1
  - brotli-python=1.1.0=py311hb755f60_1
  - bzip2=1.0.8=hd590300_5
  - c-ares=1.28.1=hd590300_0
  - ca-certificates=2024.6.2=hbcca054_0
  - cached-property=1.5.2=hd8ed1ab_1
  - cached_property=1.5.2=pyha770c72_1
  - cads-api-client=1.0.3=pyhd8ed1ab_0
  - cairo=1.18.0=hbb29018_2
  - cartopy=0.23.0=py311h14de704_1
  - cdsapi=0.7.0=pyhd8ed1ab_0
  - certifi=2024.6.2=pyhd8ed1ab_0
  - cf-units=3.2.0=py311h18e1886_5
  - cf_xarray=0.9.2=pyhd8ed1ab_0
  - cffi=1.16.0=py311hb3a22ac_0
  - cfgrib=0.9.13.0=pyhd8ed1ab_0
  - cfitsio=4.4.1=hf8ad068_0
  - cftime=1.6.4=py311h18e1886_0
  - charset-normalizer=3.3.2=pyhd8ed1ab_0
  - click=8.1.7=unix_pyh707e725_0
  - click-plugins=1.1.1=py_0
  - cligj=0.7.2=pyhd8ed1ab_1
  - cloudpickle=3.0.0=pyhd8ed1ab_0
  - cmocean=4.0.3=pyhd8ed1ab_0
  - colorama=0.4.6=pyhd8ed1ab_0
  - colorspacious=1.1.2=pyh24bf2e0_0
  - comm=0.2.2=pyhd8ed1ab_0
  - contourpy=1.2.1=py311h9547e67_0
  - cycler=0.12.1=pyhd8ed1ab_0
  - cytoolz=0.12.3=py311h459d7ec_0
  - dask=2024.6.2=pyhd8ed1ab_0
  - dask-core=2024.6.2=pyhd8ed1ab_0
  - dask-expr=1.1.6=pyhd8ed1ab_0
  - dbus=1.13.6=h5008d03_3
  - debugpy=1.8.2=py311h4332511_0
  - decorator=5.1.1=pyhd8ed1ab_0
  - defusedxml=0.7.1=pyhd8ed1ab_0
  - distributed=2024.6.2=pyhd8ed1ab_0
  - eccodes=2.34.0=he84ddb8_0
  - entrypoints=0.4=pyhd8ed1ab_0
  - esmf=8.6.1=nompi_h0a5817f_2
  - esmpy=8.6.1=pyhc1e730c_0
  - exceptiongroup=1.2.0=pyhd8ed1ab_2
  - executing=2.0.1=pyhd8ed1ab_0
  - expat=2.6.2=h59595ed_0
  - fasteners=0.17.3=pyhd8ed1ab_0
  - findlibs=0.0.5=pyhd8ed1ab_0
  - flox=0.9.8=pyhd8ed1ab_0
  - fmt=10.2.1=h00ab1b0_0
  - folium=0.17.0=pyhd8ed1ab_0
  - font-ttf-dejavu-sans-mono=2.37=hab24e00_0
  - font-ttf-inconsolata=3.000=h77eed37_0
  - font-ttf-source-code-pro=2.038=h77eed37_0
  - font-ttf-ubuntu=0.83=h77eed37_2
  - fontconfig=2.14.2=h14ed4e7_0
  - fonts-conda-ecosystem=1=0
  - fonts-conda-forge=1=0
  - fonttools=4.53.0=py311h331c9d8_0
  - fqdn=1.5.1=pyhd8ed1ab_0
  - freeglut=3.2.2=ha6d2627_3
  - freetype=2.12.1=h267a509_2
  - freexl=2.0.0=h743c826_0
  - frozenlist=1.4.1=py311h459d7ec_0
  - fsspec=2024.6.1=pyhff2d567_0
  - gdal=3.9.1=py311hf92cf48_2
  - geopandas=1.0.0=pyhd8ed1ab_0
  - geopandas-base=1.0.0=pyha770c72_0
  - geos=3.12.1=h59595ed_0
  - geotiff=1.7.3=hf7fa9e8_1
  - gettext=0.22.5=h59595ed_2
  - gettext-tools=0.22.5=h59595ed_2
  - gflags=2.2.2=he1b5a44_1004
  - giflib=5.2.2=hd590300_0
  - glib=2.80.2=h8a4344b_1
  - glib-tools=2.80.2=h73ef956_1
  - glog=0.7.1=hbabe93e_0
  - graphite2=1.3.13=h59595ed_1003
  - greenlet=3.0.3=py311hb755f60_0
  - gst-plugins-base=1.24.5=hbaaba92_0
  - gstreamer=1.24.5=haf2f30d_0
  - h11=0.14.0=pyhd8ed1ab_0
  - h2=4.1.0=pyhd8ed1ab_0
  - harfbuzz=8.5.0=hfac3d4d_0
  - hdf4=4.2.15=h2a13503_7
  - hdf5=1.14.3=nompi_hdf9ad27_105
  - hpack=4.0.0=pyh9f0ad1d_0
  - httpcore=1.0.5=pyhd8ed1ab_0
  - httpx=0.27.0=pyhd8ed1ab_0
  - hyperframe=6.0.1=pyhd8ed1ab_0
  - icu=73.2=h59595ed_0
  - idna=3.7=pyhd8ed1ab_0
  - importlib-metadata=8.0.0=pyha770c72_0
  - importlib_metadata=8.0.0=hd8ed1ab_0
  - importlib_resources=6.4.0=pyhd8ed1ab_0
  - ipykernel=6.29.4=pyh3099207_0
  - ipython=8.26.0=pyh707e725_0
  - isoduration=20.11.0=pyhd8ed1ab_0
  - jasper=4.2.4=h536e39c_0
  - jedi=0.19.1=pyhd8ed1ab_0
  - jinja2=3.1.4=pyhd8ed1ab_0
  - joblib=1.4.2=pyhd8ed1ab_0
  - json-c=0.17=h7ab15ed_0
  - json5=0.9.25=pyhd8ed1ab_0
  - jsonpointer=3.0.0=py311h38be061_0
  - jsonschema=4.22.0=pyhd8ed1ab_0
  - jsonschema-specifications=2023.12.1=pyhd8ed1ab_0
  - jsonschema-with-format-nongpl=4.22.0=pyhd8ed1ab_0
  - jupyter-lsp=2.2.5=pyhd8ed1ab_0
  - jupyter-server-proxy=4.2.0=pyhd8ed1ab_0
  - jupyter_client=8.6.2=pyhd8ed1ab_0
  - jupyter_core=5.7.2=py311h38be061_0
  - jupyter_events=0.10.0=pyhd8ed1ab_0
  - jupyter_server=2.14.1=pyhd8ed1ab_0
  - jupyter_server_terminals=0.5.3=pyhd8ed1ab_0
  - jupyterlab=4.2.3=pyhd8ed1ab_0
  - jupyterlab-myst=2.4.2=pyhd8ed1ab_0
  - jupyterlab_pygments=0.3.0=pyhd8ed1ab_1
  - jupyterlab_server=2.27.2=pyhd8ed1ab_0
  - kealib=1.5.3=hee9dde6_1
  - keyutils=1.6.1=h166bdaf_0
  - kiwisolver=1.4.5=py311h9547e67_1
  - krb5=1.21.3=h659f571_0
  - lame=3.100=h166bdaf_1003
  - lcms2=2.16=hb7c19ff_0
  - ld_impl_linux-64=2.40=hf3520f5_7
  - lerc=4.0.0=h27087fc_0
  - libabseil=20240116.2=cxx17_h59595ed_0
  - libaec=1.1.3=h59595ed_0
  - libarchive=3.7.4=hfca40fe_0
  - libarrow=16.1.0=h4a673ee_10_cpu
  - libarrow-acero=16.1.0=hac33072_10_cpu
  - libarrow-dataset=16.1.0=hac33072_10_cpu
  - libarrow-substrait=16.1.0=h7e0c224_10_cpu
  - libasprintf=0.22.5=h661eb56_2
  - libasprintf-devel=0.22.5=h661eb56_2
  - libblas=3.9.0=22_linux64_openblas
  - libboost-headers=1.85.0=ha770c72_2
  - libbrotlicommon=1.1.0=hd590300_1
  - libbrotlidec=1.1.0=hd590300_1
  - libbrotlienc=1.1.0=hd590300_1
  - libcap=2.69=h0f662aa_0
  - libcblas=3.9.0=22_linux64_openblas
  - libclang-cpp15=15.0.7=default_h127d8a8_5
  - libclang13=18.1.8=default_h6ae225f_0
  - libcrc32c=1.1.2=h9c3ff4c_0
  - libcups=2.3.3=h4637d8d_4
  - libcurl=8.8.0=hca28451_1
  - libdeflate=1.20=hd590300_0
  - libedit=3.1.20191231=he28a2e2_2
  - libev=4.33=hd590300_2
  - libevent=2.1.12=hf998b51_1
  - libexpat=2.6.2=h59595ed_0
  - libffi=3.4.2=h7f98852_5
  - libflac=1.4.3=h59595ed_0
  - libgcc-ng=14.1.0=h77fa898_0
  - libgcrypt=1.11.0=h4ab18f5_0
  - libgdal=3.9.1=he176cbe_2
  - libgettextpo=0.22.5=h59595ed_2
  - libgettextpo-devel=0.22.5=h59595ed_2
  - libgfortran-ng=14.1.0=h69a702a_0
  - libgfortran5=14.1.0=hc5f4f2c_0
  - libglib=2.80.2=h8a4344b_1
  - libglu=9.0.0=ha6d2627_1004
  - libgomp=14.1.0=h77fa898_0
  - libgoogle-cloud=2.25.0=h2736e30_0
  - libgoogle-cloud-storage=2.25.0=h3d9a0c8_0
  - libgpg-error=1.50=h4f305b6_0
  - libgrpc=1.62.2=h15f2491_0
  - libiconv=1.17=hd590300_2
  - libjpeg-turbo=3.0.0=hd590300_1
  - libkml=1.3.0=h01aab08_1018
  - liblapack=3.9.0=22_linux64_openblas
  - libllvm14=14.0.6=hcd5def8_4
  - libllvm15=15.0.7=hb3ce162_4
  - libllvm18=18.1.8=hc9dba70_0
  - libnetcdf=4.9.2=nompi_h135f659_114
  - libnghttp2=1.58.0=h47da74e_1
  - libnsl=2.0.1=hd590300_0
  - libogg=1.3.5=h4ab18f5_0
  - libopenblas=0.3.27=pthreads_h413a1c8_0
  - libopus=1.3.1=h7f98852_1
  - libparquet=16.1.0=h6a7eafb_10_cpu
  - libpng=1.6.43=h2797004_0
  - libpq=16.3=ha72fbe1_0
  - libprotobuf=4.25.3=h08a7969_0
  - libre2-11=2023.09.01=h5a48ba9_2
  - librttopo=1.1.0=h8917695_15
  - libsndfile=1.2.2=hc60ed4a_1
  - libsodium=1.0.18=h36c2ea0_1
  - libspatialite=5.1.0=h6fbd9c4_7
  - libsqlite=3.46.0=hde9e2c9_0
  - libssh2=1.11.0=h0841786_0
  - libstdcxx-ng=14.1.0=hc0a3c3a_0
  - libsystemd0=255=h3516f8a_1
  - libthrift=0.19.0=hb90f79a_1
  - libtiff=4.6.0=h1dd3fc0_3
  - libudunits2=2.2.28=h40f5838_3
  - libutf8proc=2.8.0=h166bdaf_0
  - libuuid=2.38.1=h0b41bf4_0
  - libvorbis=1.3.7=h9c3ff4c_0
  - libwebp-base=1.4.0=hd590300_0
  - libxcb=1.16=hd590300_0
  - libxcrypt=4.4.36=hd590300_1
  - libxkbcommon=1.7.0=h2c5496b_1
  - libxml2=2.12.7=hc051c1a_1
  - libzip=1.10.1=h2629f0a_3
  - libzlib=1.3.1=h4ab18f5_1
  - llvmlite=0.43.0=py311hbde99c3_0
  - locket=1.0.0=pyhd8ed1ab_0
  - lz4=4.3.3=py311h38e4bf4_0
  - lz4-c=1.9.4=hcb278e6_0
  - lzo=2.10=hd590300_1001
  - mapclassify=2.6.1=pyhd8ed1ab_0
  - markdown-it-py=3.0.0=pyhd8ed1ab_0
  - markupsafe=2.1.5=py311h459d7ec_0
  - matplotlib=3.8.4=py311h38be061_2
  - matplotlib-base=3.8.4=py311ha4ca890_2
  - matplotlib-inline=0.1.7=pyhd8ed1ab_0
  - mdurl=0.1.2=pyhd8ed1ab_0
  - minizip=4.0.7=h401b404_0
  - mistune=3.0.2=pyhd8ed1ab_0
  - mpg123=1.32.6=h59595ed_0
  - msgpack-python=1.0.8=py311h52f7536_0
  - multidict=6.0.5=py311h459d7ec_0
  - multiurl=0.3.1=pyhd8ed1ab_0
  - munkres=1.1.4=pyh9f0ad1d_0
  - mysql-common=8.3.0=hf1915f5_4
  - mysql-libs=8.3.0=hca2cd23_4
  - nbclient=0.10.0=pyhd8ed1ab_0
  - nbconvert=7.16.4=hd8ed1ab_1
  - nbconvert-core=7.16.4=pyhd8ed1ab_1
  - nbconvert-pandoc=7.16.4=hd8ed1ab_1
  - nbformat=5.10.4=pyhd8ed1ab_0
  - nc-time-axis=1.4.1=pyhd8ed1ab_0
  - ncurses=6.5=h59595ed_0
  - nest-asyncio=1.6.0=pyhd8ed1ab_0
  - netcdf-fortran=4.6.1=nompi_h228c76a_104
  - netcdf4=1.7.1=nompi_py311h25b3b55_101
  - networkx=3.3=pyhd8ed1ab_1
  - notebook-shim=0.2.4=pyhd8ed1ab_0
  - nspr=4.35=h27087fc_0
  - nss=3.101=h593d115_0
  - numba=0.60.0=py311h4bc866e_0
  - numcodecs=0.12.1=py311h4332511_1
  - numpy=1.26.4=py311h64a7726_0
  - numpy_groupies=0.11.1=pyhd8ed1ab_0
  - openjpeg=2.5.2=h488ebb8_0
  - openssl=3.3.1=h4ab18f5_1
  - orc=2.0.1=h17fec99_1
  - overrides=7.7.0=pyhd8ed1ab_0
  - packaging=24.1=pyhd8ed1ab_0
  - pandas=2.2.2=py311h14de704_1
  - pandoc=3.2.1=ha770c72_0
  - pandocfilters=1.5.0=pyhd8ed1ab_0
  - papermill=2.6.0=pyhd8ed1ab_0
  - parso=0.8.4=pyhd8ed1ab_0
  - partd=1.4.2=pyhd8ed1ab_0
  - patsy=0.5.6=pyhd8ed1ab_0
  - pcre2=10.44=h0f59acf_0
  - pexpect=4.9.0=pyhd8ed1ab_0
  - pickleshare=0.7.5=py_1003
  - pillow=10.3.0=py311h82a398c_1
  - pip=24.0=pyhd8ed1ab_0
  - pixman=0.43.2=h59595ed_0
  - pkgutil-resolve-name=1.3.10=pyhd8ed1ab_1
  - platformdirs=4.2.2=pyhd8ed1ab_0
  - plotly=5.22.0=pyhd8ed1ab_0
  - ply=3.11=pyhd8ed1ab_2
  - pooch=1.8.2=pyhd8ed1ab_0
  - poppler=24.04.0=hb6cd0d7_0
  - poppler-data=0.4.12=hd8ed1ab_0
  - postgresql=16.3=h8e811e2_0
  - proj=9.4.1=hb784bbd_0
  - prometheus_client=0.20.0=pyhd8ed1ab_0
  - prompt-toolkit=3.0.47=pyha770c72_0
  - properscoring=0.1=py_0
  - psutil=6.0.0=py311h331c9d8_0
  - pthread-stubs=0.4=h36c2ea0_1001
  - ptyprocess=0.7.0=pyhd3deb0d_0
  - pulseaudio-client=17.0=hb77b528_0
  - pure_eval=0.2.2=pyhd8ed1ab_0
  - pwlf=2.2.1=py311h38be061_3
  - pyarrow=16.1.0=py311hbd00459_4
  - pyarrow-core=16.1.0=py311h8c3dac4_4_cpu
  - pyarrow-hotfix=0.6=pyhd8ed1ab_0
  - pycparser=2.22=pyhd8ed1ab_0
  - pydantic=2.7.4=pyhd8ed1ab_0
  - pydantic-core=2.18.4=py311h5ecf98a_0
  - pydantic-settings=2.3.4=pyhd8ed1ab_0
  - pydoe=0.3.8=py_1
  - pygments=2.18.0=pyhd8ed1ab_0
  - pyogrio=0.9.0=py311hfc743a8_0
  - pyparsing=3.1.2=pyhd8ed1ab_0
  - pyproj=3.6.1=py311hc21b84f_7
  - pyqt=5.15.9=py311hf0fb5b6_5
  - pyqt5-sip=12.12.2=py311hb755f60_5
  - pyshp=2.3.1=pyhd8ed1ab_0
  - pysocks=1.7.1=pyha2e5f31_6
  - python=3.11.9=hb806964_0_cpython
  - python-dateutil=2.9.0=pyhd8ed1ab_0
  - python-dotenv=1.0.1=pyhd8ed1ab_0
  - python-eccodes=1.7.1=py311h18e1886_0
  - python-fastjsonschema=2.20.0=pyhd8ed1ab_0
  - python-json-logger=2.0.7=pyhd8ed1ab_0
  - python-tzdata=2024.1=pyhd8ed1ab_0
  - python_abi=3.11=4_cp311
  - pytz=2024.1=pyhd8ed1ab_0
  - pyyaml=6.0.1=py311h459d7ec_1
  - pyzmq=26.0.3=py311h08a0b41_0
  - qt-main=5.15.8=ha2b5568_22
  - rasterio=1.3.10=py311h539dff6_4
  - re2=2023.09.01=h7f4b329_2
  - readline=8.2=h8228510_1
  - referencing=0.35.1=pyhd8ed1ab_0
  - regionmask=0.12.1=pyhd8ed1ab_0
  - requests=2.32.3=pyhd8ed1ab_0
  - rfc3339-validator=0.1.4=pyhd8ed1ab_0
  - rfc3986-validator=0.1.1=pyh9f0ad1d_0
  - rich=13.7.1=pyhd8ed1ab_0
  - rioxarray=0.15.7=pyhd8ed1ab_0
  - rpds-py=0.18.1=py311h5ecf98a_0
  - s2n=1.4.16=he19d79f_0
  - scikit-learn=1.5.0=py311he08f58d_1
  - scipy=1.14.0=py311h517d4fd_0
  - seaborn=0.13.2=hd8ed1ab_2
  - seaborn-base=0.13.2=pyhd8ed1ab_2
  - send2trash=1.8.3=pyh0d859eb_0
  - setuptools=70.1.1=pyhd8ed1ab_0
  - shapely=2.0.4=py311h0bed3d6_1
  - shellingham=1.5.4=pyhd8ed1ab_0
  - simpervisor=1.0.0=pyhd8ed1ab_0
  - sip=6.7.12=py311hb755f60_0
  - six=1.16.0=pyh6c4a22f_0
  - snappy=1.2.0=hdb0a2a9_1
  - sniffio=1.3.1=pyhd8ed1ab_0
  - snuggs=1.4.7=py_0
  - sortedcontainers=2.4.0=pyhd8ed1ab_0
  - soupsieve=2.5=pyhd8ed1ab_1
  - sparse=0.15.4=pyhd8ed1ab_0
  - spdlog=1.13.0=hd2e6256_0
  - sqlalchemy=2.0.31=py311h331c9d8_0
  - sqlite=3.46.0=h6d4b2fc_0
  - stack_data=0.6.2=pyhd8ed1ab_0
  - statsmodels=0.14.2=py311h18e1886_0
  - structlog=24.2.0=pyhd8ed1ab_0
  - tblib=3.0.0=pyhd8ed1ab_0
  - tenacity=8.4.2=pyhd8ed1ab_0
  - terminado=0.18.1=pyh0d859eb_0
  - threadpoolctl=3.5.0=pyhc1e730c_0
  - tiledb=2.24.1=h2aae180_1
  - tinycss2=1.3.0=pyhd8ed1ab_0
  - tk=8.6.13=noxft_h4845f30_101
  - toml=0.10.2=pyhd8ed1ab_0
  - tomli=2.0.1=pyhd8ed1ab_0
  - toolz=0.12.1=pyhd8ed1ab_0
  - tornado=6.4.1=py311h331c9d8_0
  - tqdm=4.66.4=pyhd8ed1ab_0
  - traitlets=5.14.3=pyhd8ed1ab_0
  - typer=0.12.3=pyhd8ed1ab_0
  - typer-slim=0.12.3=pyhd8ed1ab_0
  - typer-slim-standard=0.12.3=hd8ed1ab_0
  - types-python-dateutil=2.9.0.20240316=pyhd8ed1ab_0
  - typing-extensions=4.12.2=hd8ed1ab_0
  - typing_extensions=4.12.2=pyha770c72_0
  - typing_utils=0.1.0=pyhd8ed1ab_0
  - tzcode=2024a=h3f72095_0
  - tzdata=2024a=h0c530f3_0
  - udunits2=2.2.28=h40f5838_3
  - uri-template=1.3.0=pyhd8ed1ab_0
  - uriparser=0.9.8=hac33072_0
  - urllib3=2.2.2=pyhd8ed1ab_1
  - wcwidth=0.2.13=pyhd8ed1ab_0
  - webcolors=24.6.0=pyhd8ed1ab_0
  - webencodings=0.5.1=pyhd8ed1ab_2
  - websocket-client=1.8.0=pyhd8ed1ab_0
  - wheel=0.43.0=pyhd8ed1ab_1
  - xarray=2024.6.0=pyhd8ed1ab_1
  - xarraymannkendall=1.4.5=pyhd8ed1ab_0
  - xcb-util=0.4.1=hb711507_2
  - xcb-util-image=0.4.0=hb711507_2
  - xcb-util-keysyms=0.4.1=hb711507_0
  - xcb-util-renderutil=0.3.10=hb711507_0
  - xcb-util-wm=0.4.2=hb711507_0
  - xerces-c=3.2.5=hac6953d_0
  - xesmf=0.8.6=pyhd8ed1ab_0
  - xhistogram=0.3.2=pyhd8ed1ab_0
  - xkeyboard-config=2.42=h4ab18f5_0
  - xorg-fixesproto=5.0=h7f98852_1002
  - xorg-inputproto=2.3.2=h7f98852_1002
  - xorg-kbproto=1.0.7=h7f98852_1002
  - xorg-libice=1.1.1=hd590300_0
  - xorg-libsm=1.2.4=h7391055_0
  - xorg-libx11=1.8.9=hb711507_1
  - xorg-libxau=1.0.11=hd590300_0
  - xorg-libxdmcp=1.1.3=h7f98852_0
  - xorg-libxext=1.3.4=h0b41bf4_2
  - xorg-libxfixes=5.0.3=h7f98852_1004
  - xorg-libxi=1.7.10=h7f98852_0
  - xorg-libxrender=0.9.11=hd590300_0
  - xorg-renderproto=0.11.1=h7f98852_1002
  - xorg-xextproto=7.3.0=h0b41bf4_1003
  - xorg-xf86vidmodeproto=2.3.1=h7f98852_1002
  - xorg-xproto=7.0.31=h7f98852_1007
  - xskillscore=0.0.26=pyhd8ed1ab_0
  - xyzservices=2024.6.0=pyhd8ed1ab_0
  - xz=5.2.6=h166bdaf_0
  - yaml=0.2.5=h7f98852_2
  - yarl=1.9.4=py311h459d7ec_0
  - zarr=2.18.2=pyhd8ed1ab_0
  - zeromq=4.3.5=h75354e8_4
  - zict=3.0.0=pyhd8ed1ab_0
  - zipp=3.19.2=pyhd8ed1ab_0
  - zlib=1.3.1=h4ab18f5_1
  - zstandard=0.22.0=py311hb6f056b_1
  - zstd=1.5.6=ha6fb4c9_0
  - pip:
      - c3s-eqc-automatic-quality-control==0.1.2.dev112+g680c19a
      - cacholote==1.1.0
      - cads-toolbox==0.0.2b0
      - cgul==0.0.4
      - coucal==0.0.1b3
      - emohawk==0.0.4b0
      - kaleido==0.2.1
      - pymannkendall==1.4.3
prefix: /data/common/miniforge3/envs/wp5

Note: you may need to restart the kernel to use updated packages.

Anything else we need to know?
Provide permalink.

Hi @yoniv1 , I fixed the headers in the notebooks you already submitted, but could you please fix it in the new notebooks?
Please revise it and send me the right version.

Hi @malmans2,
It should be ok now!

Here is the permalink: https://github.com/ecmwf-projects/c3s2-eqc-quality-assessment/blob/26d5d0036abd3921d5b26fd1dd427249e5794a25/Satellite_ECVs/Land_Hydrology%26Cryosphere_ECVs/satellite_satellite-ice-sheet-mass-balance_uncertainty_q01.ipynb
Please make sure that the notebook name is correct.
If you need to make modifications (e.g., to address the reviewer's comment), please share here the new version of the notebook and I will provide a new permalink.
Let me know when the notebook is accepted, I will merge the PR into main.

Hi @yoniv1,
I've aligned the notebook with the latest template. If you check the preview, you'll notice some minor formatting edits.
If you need to review this notebook, please make sure to start from the latest version.
Here is the latest permalink: https://github.com/ecmwf-projects/c3s2-eqc-quality-assessment/blob/6b0dfc684a4425ddc4953c4c331ea2ed59b2697d/Satellite_ECVs/Cryosphere/satellite_satellite-ice-sheet-mass-balance_uncertainty_q01.ipynb
PREVIEW
You don't need to re-submit the permalink; the last one you used is still valid.
As far as I know, all notebooks now belong to separate workflows. Could you please send me the Workflow ID associated with this notebook?
Also, it was decided to split the Land Hydrology and Cryosphere folders, I assume this notebook belongs to the latter.

Task: 53c108e2-a8d3-11ef-a96d-b6cb81721144
Workflow: eqctier3-c858600f-a176-4e46-8c5d-e60adbbef4b5

source: gharchive/issue

license_type: permissive

license_source: github-api


text:
Another back-end to look at YAXArrays.jl

https://github.com/meggart/YAXArrays.jl
Developed at MPI by serious developer. @meggart @felixcremer

Thanks a lot for pinging us. I would be happy to discuss your backend system. Actually were having the same problem that there is a multitude of different named array implementations, so we made https://github.com/meggart/YAXArrayBase.jl that defines a common interface for different packages so one can use them interchangeably. The medium-term goal in YAXArrays is to switch all functions to this interface so that all the mapslices functions etc can be applied directly to all kinds of arrays, be it AxisKeys, DImensionalData or AxisArrays.
So as an alternative to implementing a YAXArrays backend one might implement the interface from YAXArrayBase for cfgrib.Dataset. See this for different implementations of the interface....

authors: Balinus meggart


text:
pip install ecmwflibs

What maintenance does this project need?
I am working on a Windows 11 computer that has Python 3.11.9 installed on it as the only version of Python
Yesterday I installed ecmwflibs in a test virtual environment, and it automatically installed eccodes (among other things)
Today I am trying to install ecmwflibs in my actual project environment using the command
pip install ecmwflibs (as I did yesterday)
I get the message in the terminal window to say it has been successfully installed, but it has not installed eccodes (which is the library I require)
Can someone suggest where I should look or what I should do to get it to do a full install in the virtual environment for me
Organisation
private

I have it working again

repo: ecmwf/ecmwflibs


text:
y轴label显示错误

提问前应该做的事
请确保提问前做了以下事，将完成的项目的 [] 改为 [x]：

[X] 我已通读过 README
[X] 我已阅读过 FAQ

需提供的信息
将符合项的 [] 改为 [x]，并补充需要的信息：
简单描述问题：
series中提供了数据[0，0，0]、[0，0，0]、[1，1，1]、[1，1，1]，出现了绘制不正确和y轴的label显示问题
预期效果：
（如有需要请提供预期的图）
实际效果：

如图少了两根线， y轴的显示的label也有问题
（如有需要请提供截图）
复现环境：

[X] 在微信开发工具中存在该问题
[X] 在真机上存在该问题

线不显示应该是覆盖了，能不能判断如果数据覆盖，使用微小偏移量或者透明度 线条粗细等解决覆盖的问题呢？
我同时看见某些折线图就算覆盖就看的出来啊。
好奇怪的问题

另外 求放出小程序未压缩的js,官方下载的没这个新。

提供一下完整的配置项？
未压缩的 js 可以在 ECharts 官网或 GitHub 下载最新版的未压缩文件，替换 echarts.js 即可。

@Ovilia 不好意思，经过发现是格式化的问题

正常是这样的

authors: Ovilia cnsilvan

repo: ecomfe/echarts-for-weixin


text:
legend 排序问题

legend无法排序,legend里面是乱序的

这个顺序是 legend 里 data 的顺序

谢谢

authors: pissang rikan

repo: ecomfe/echarts


text:
建议map类型markline的label可以设置显示位置

如题，因为在使用过程中会出现多个点指向同一个点，如果不显示label数据不直观，看到不具体值，如果显示的话所有点挤在一起，什么也看不出来。如果可以设置label的位置，比如设置到中间，名者发出点之类的。

貌似设置下label的position:'start'就可以了，其实就是变相的把label标注放到markline的起点位置了


text:
axisLabel.textStyle.fontSize的问题

问题简述 (One-line summary)
关于axisLabel.textStyle.fontSize配置项的值 好像只有比默认值大才能生效 比默认值小不能生效 现在是想在移动端浏览 故期望 尽量挤压四周空间 留给图表主要内容更大的展示区域
版本及环境 (Version & Environment)

ECharts 版本 (ECharts version):3.1.7
浏览器类型和版本 (Browser version):
操作系统类型和版本 (OS Version):

重现步骤 (Steps to reproduce)

期望结果 (Expected behaviour)
可能哪里有问题 (What went wrong)
ECharts配置项 (ECharts option)

option = {
			title : {
				text: '企业信用指数',
				left:'center'
			},
			legend: {
				data:['本月','上月','去年同期'],
				left:'center',
				top: '10%'
			},
			grid:{
				top:'20%',
				bottom:'10%'
			},
			xAxis : [
				{
					type : 'category',
					splitLine:{show:false},
					axisLine:{lineStyle:{color:'#000000',width:1}},
					axisLabel:{interval:0},
					data : ['竞争指数','经营效率指数','信用风险临界指数','信用能力综合指数']
				}
			],
			yAxis : [
				{
					type : 'value',
					min: 60,
					max: 100,
					splitNumber: 8,
					axisLabel:{textStyle:{fontSize:20}},
					//axisLabel:{textStyle:{fontSize:6}},//默认值为12
					axisLine:{lineStyle:{color:'#000000',width:1}}
				}
			],
			series : [
				{
					name:'本月',
					type:'line',
					itemStyle:{normal:{lineStyle:{width:3}}},
					data:[84,73.5,92,74]
				},
				{
					name:'上月',
					type:'line',
					itemStyle:{normal:{lineStyle:{width:3}}},
					data:[90,82.5,90,82]
				},
				{
					name:'去年同期',
					type:'line',
					itemStyle:{normal:{lineStyle:{width:3}}},
					data:[92,85,95,81]
				}
			]
}

其他信息 (Other comments)

浏览器限制最小只能 12px

authors: R-River pissang


text:
echarts  多次访问后，echarts图字体颜色加粗

One-line summary [问题简述]
多有页面都有echarts图，在这几个页面之间快速切换，连续操作数次后，整个项目所有的echarts图的字体颜色都加粗啦
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:3.3.2
Browser version [浏览器类型和版本]:chrome
OS Version [操作系统类型和版本]:win10

Expected behaviour [期望结果]
正常显示
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息

]

@leeight @cnberg @chriswong


text:
chore(payment-options): always show a price inside each payment from list

Screenshots

Antes

Depois

Checklist

[x] I've read and understood contributing guidelines;
[x] If changing UI, I've tested on most common viewports, desktop and mobile devices;

This is a claim for some clients for long time ago

Porque quando boleto e pix são condições normais, aparece o escrito Boleto | PIX, mas normalmente tem cartão de crédito, então fica assim:
Boleto
Pix
Cartão de Crédito  - Condicoes cartão de crédito
E ai eu já ouvi reclamação de cliente achando que parcela no boleto ou pix. Nesse caso, ou colocamos um hr ou borda pra separar as linhas para não dar o duplo sentido, ou mostrar o preço claro daquela opção..

E ai eu já ouvi reclamação de cliente achando que parcela no boleto ou pix.

Não acho que isso aqui resolveria não...

ou colocamos um hr ou borda pra separar as linhas

Ou um espaçamento maior

source: gharchive/pull-request

repo: ecomplus/storefront

license: MIT


text:
DiscreteDistribution object should store reference to continuous distribution it was approximated from

https://github.com/econ-ark/HARK/issues/640#issuecomment-621943931
So that it can be inspected and its underlying mu, sigma, count values (for example) can be compared to new configurations.

An implementation:

[ ] when a continuous variable is approxed to a DiscreteDistribution, have the latter:

keep a pointer to the CV
keep the arguments given to approx

in the case where combineIndepDstns is used, the above step isn't possible...
[ ] Ultimately, combineIndepDstns should be replaced; we should have a continuous multivariate distribution class analogous to the other continuous distribution

Note that there are many possible ways to discretize any particular continuous distribution, which will have different parameters, so we will need to keep track of the method  and its parameters.  For example, for a continuous distribution, you could have equiprobable, Hermite, bounded equiprobable, truncated equiprobable, bounded equiprobable, etc.

that is exactly what is done in PR #954

To be clear: PR #954 assumes the approx method picks the discretization procedure based on a keyword argument.
The DiscreteDistribution tracks the keyword arguments of approx.
Currently, we have do not have multiple discretization procedures for a single distribution type. If there was an example of an alternative discretization procedure implemented in code, it would be easier to demonstrate how this would work, and discuss alternative architectures.

See #804

This was discussed at least as long ago as #121, and a number of examples were scattered through the diffuse discussions that were concentrated and distilled here.
The concrete instance we should probably start with is the case of the normal (and lognormal) distributions.  Two distinct choices are important:

How to handle any "tail mass" (at the top and the bottom) that cannot be captured because any discretization will have a bottommost and a topmost point, but the continuous distribution may go to positive or negative infinity
How to distribute mass points and probability weights for the probability mass between the topmost and bottommost points.

For distributing the "tail mass" there are two common choices: ["truncation"]((https://reference.wolfram.com/language/ref/CensoredDistribution.html) and "censoring".  With "censoring", all of the mass of points beyond the limit is assigned to a point AT the limit.
For distributing the points inside the interval, there are many possible choices.  The most popular two are Gauss-Hermite and equiprobable, but many other choices are possible.
Mathematica handles all of this by having a set of predefined objects that it know are discrete distributions, and to which it accordingly knows it can apply certain operations (mean, variance, etc).   Similarly for continuous distributions.
I'm not proposing anything remotely so fancy.
Suppose I want to define the "true" model as one in which the distribution of income shocks is a censored lognormal with the censoring taking place at three standard deviations.
Then we might have, say, three or four different "approximated" models:

Equiprobable between [-3 sigma, +3 sigma], with 7 equiprobable points
Equiprobable between [-3 sigma, +3 sigma], with 21 equiprobable points
Censored with the correct censored probability masses at exactly -3 sigma and +3 sigma, and then equiprobable between, with 7 points
Censored with the correct censored probability masses at exactly -3 sigma and +3 sigma, and then Gauss-Hermite between, with 9 points

I'm not proposing that we build a tool to which we can give all of these and many other various possibilities, and it does all the work.  Instead, I'm proposing that we tell the user: "You write a function which has a set of arguments.  The function, when called with those arguments, generates the discrete distribution you want.  What you pass to our Solve and our Simulate routines is your function, and the specific parameter values you want it evaluated at if we get to the point where we need it.  (Which we surely will unless there's a bug in the code before that point)."
This is basically what Pablo does.

I was unclear. I meant an example of multiple discretization procedures for the same distribution written in Python code.
I would not feel comfortable, myself, implementing what you propose without being able to demonstrate its functionality with at least two such functions.
Can you point to the Dolo code that does this?

Ah , it looks like we do have code for both equiprobable and Gauss-Hermite approximations to lognormal in HARK, sort of...
This starts with the parameters of the continuous distribution, and returns a discrete distribution.
https://github.com/econ-ark/HARK/blob/e2fe6cfa8fd81208e5c40961b645331688148254/HARK/distribution.py#L600
Contrast this with the current implementation of approx which is a method on the continuous distribution:
https://github.com/econ-ark/HARK/blob/e2fe6cfa8fd81208e5c40961b645331688148254/HARK/distribution.py#L98
I think what you are proposing is that these two modes of discretization should exist as standalone functions. Maybe that's the current architecture of  approxLognormalGaussHermite. But you'll notice that the resulting DiscreteDistribution does not, in that case, understand that it's derived from a continuous lognormal distribution. In fact, this design undercuts the object-oriented way we've been moving towards for Distributions.
Have I misunderstood you?

Took a closer look at how this is currently handled in the case of our widely used mean-one approximation to the lognormal, which is via the MeanOneLognormal class, and the approx method applied to it.
At some point I'd propose we make the following changes:

Call it Lognormal_MeanOne (my preference is for names to go from the general to the specific)
The approx method needs to take several different options, each of which has different parameters:  (a) Equiprobable (just the number of points); (b) Gauss-Hermite (just the number of points); (c) Censored-Equiprobable (number of points, and upper and lower censoring points; (d) Censored-Gauss-Hermite (number of points, and upper and lower censoring points.

As I remarked somewhere else, I very much like the architecture of how Mathematica handles this.  Doing something similar may be too heavy a lift for our purposes, but it might not be so hard -- I'm really not sure.

No underscores in class names.
Otherwise, I'm following what you're saying.

OK; you're the PEP8 jedi master.  But, yes, I think the right way to think about it is that a discrete approximation is a thing that is done to a continuous distribution.  And there are multiple different ways to do it, which be combined (censoring and equiprobable, censoring and hermite, truncated and hermite, etc).

authors: llorracc sbenthall

repo: econ-ark/HARK

license_source: bigquery


text:
FR: add Bard directive

The about section of the repo states that the @bard directive is implemented but it's not working for me. It just outputs @bard($content) as a string.

Ya looks like I wrote that and then didn't implement, sorry about that. I'll make this a feature request

@BobWez98 what would you want it to output?

Please use native Statamic 3.3 tag helper, this addon will be archived.

repo: edalzell/statamic-blade


text:
[BUG REPORT] Unable to Stop edamame_posture on Ubuntu VM: Encountering "No schemas installed" and PID Lock Issues

Bug report
## Description
After starting edamame_posture on an Ubuntu 22.04 virtual machine, I encounter issues when attempting to stop the service. The stop command results in an error related to screen saver schemas, and subsequent attempts to restart the service fail due to PID locking issues. Additionally, there are lingering edamame_posture processes that remain defunct.

## Steps to Reproduce

Start edamame_posture:
sudo ./edamame_posture start vm-runner edamame.tech HIDE_PIN_CODE linux false github_ubuntu

Stop edamame_posture:
sudo ./edamame_posture stop

## Expected Behavior

The edamame_posture service should stop gracefully without errors.
All associated processes should terminate properly, allowing the service to be restarted without issues.

## Actual Behavior

Stopping the service results in the following error:
Stopping background process (116604)
2024-11-08T08:29:20.997901Z ERROR edamame_core::order_factory: Error in capture command result for too slow or disabled screensaver lock: No schemas installed
Stack backtrace:
   0: anyhow::kind::Adhoc::new
   1: edamame_core::runner::run::{{closure}}
   2: <edamame_foundation::threat::ThreatMetric as edamame_core::order_factory::MetricOrderTrait<edamame_foundation::threat::ThreatMetric>>::order::{{closure}}
   ...
   17: <unknown>
   18: <unknown> - threat is Unknown

Attempting to restart the service fails with:
Core version: 0.7.2
Core information: Core version is 0.7.2, built on 2024-11-05T10:07:24.145992564Z with branch master on Linux 22.04 Ubuntu by runner, memory usage: 8.534822 MB
Starting background process...
Error daemonizing: unable to lock pid file, errno 11

Using ps aux reveals lingering processes:
root      116603  0.0  0.1 851028 16668 ?        S    08:09   0:00 ./edamame_posture start vm-runner edamame.tech HIDE_PIN_CODE linux false github_ubuntu
root      116604  0.6  0.0      0     0 ?        Z    08:09   0:07 [edamame_posture] <defunct>
root      119343  0.0  0.1 783380 16352 ?        S    08:29   0:00 ./edamame_posture start vm-runner edamame.tech HIDE_PIN_CODE

## Logs
2024-11-08T08:29:20.997901Z ERROR edamame_core::order_factory: Error in capture command result for too slow or disabled screensaver lock: No schemas installed

Stack backtrace:
   0: anyhow::kind::Adhoc::new
   1: edamame_core::runner::run::{{closure}}
   2: <edamame_foundation::threat::ThreatMetric as edamame_core::order_factory::MetricOrderTrait<edamame_foundation::threat::ThreatMetric>>::order::{{closure}}
   3: edamame_core::score_factory::ScoreFactory::start_computation::{{closure}}::{{closure}}
   4: tokio::runtime::task::core::Core<T,S>::poll
   5: tokio::runtime::task::harness::Harness<T,S>::poll
   6: tokio::runtime::scheduler::multi_thread::worker::Context::run_task
   7: tokio::runtime::scheduler::multi_thread::worker::Context::run
   8: tokio::runtime::context::runtime::enter_runtime
   9: tokio::runtime::scheduler::multi_thread::worker::run
  10: <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll
  11: tokio::runtime::task::core::Core<T,S>::poll
  12: tokio::runtime::task::harness::Harness<T,S>::poll
  13: tokio::runtime::blocking::pool::Inner::run
  14: std::sys::backtrace::__rust_begin_short_backtrace
  15: core::ops::function::FnOnce::call_once{{vtable.shim}}
  16: std::sys::pal::unix::thread::Thread::new::thread_start
  17: <unknown>
  18: <unknown> - threat is Unknown

## Environment

OS: Ubuntu 22.04
Virtualization: Virtual Machine
edamame_posture Version: 0.7.2
Build Details: Built on 2024-11-05T10:07:24.145992564Z with branch master
Memory Usage: 8.534822 MB
Command Executed:sudo ./edamame_posture start vm-runner edamame.tech HIDE_PIN_CODE linux false github_ubuntu
sudo ./edamame_posture stop

Fixed

authors: franklyonnet quentinvedrenne


text:
fail on grayscale image

imgcat: src/load_image.cc:48: bool load_image(const char*, Image*, LoadOpts*): Assertion `(img.spectrum() == 3) || (img.spectrum() == 4)' failed.

Thanks for reporting this! This is fixed in imgcat 2.0.1. If you installed using Homebrew, you can upgrade:
brew upgrade imgcat

authors: byangderek eddieantonio

repo: eddieantonio/imgcat

license: isc


text:
Problem with keyboard event simulating

Though it's possible to simulate some specific keys to test keyboard events, it's actually too limited - only a few keys are allowed:
https://github.com/eddyerburgh/avoriaz/blob/c6fa79e30cf774493cc832ebf8edfc8f30a2b07f/src/Wrapper.js#L373-L383
So I think it's necessary to make it possible to test any keys.
Also, as this article suggests, it's best to watch event.which property rather than event.keyCode. But avoriaz has only set value for keyCode property. If only event.which has been used by the application logic, then we can not test that at all.
https://github.com/eddyerburgh/avoriaz/blob/c6fa79e30cf774493cc832ebf8edfc8f30a2b07f/src/Wrapper.js#L397-L400
In general, the synthetic event should be able to be freely modified to suit any specific needs:
wrapper.trigger('keyup', { which: 8 }) // backspace key

I think this is a great suggestion. Are you able to implement it? We could release, along with your other changes, in 4.0.0

Yeah, no problem!

I think we could outsource the work to this module https://github.com/KenanY/create-event ?

Yes, although we can only use it for keyup, keydown click and dblclick
events
On Thu, Aug 10, 2017 at 8:24 PM, Fangzhou Li notifications@github.com
wrote:

I think we could outsource the work to this module
https://github.com/KenanY/create-event ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/eddyerburgh/avoriaz/issues/102#issuecomment-321649159,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMlbW0LzB2CCtAtQi-GEyjv49mvClYYPks5sW1jzgaJpZM4OxUvN
.

These days I have spent some time reading the source code of triggerhappy. It provides a lots more features, including touch events testing. I think we can learn something from it and jest and we will have a lot to discuss about.
But for now, I think there is an urgent need for testing keyboard events and we should implement those as soon as possible.

I don't know if anyone is already working on this issue/enhancement, but can that person also look at the feature of key + shiftKey=true (and altKey) because that is currently also not functioning. in specific this line  wrapper.find('input')[0].trigger('keyup', { keycode: 53, shiftKey: true }); (in this case %)

@mathijswesterhof Hi, I'm not working on this. Sorry.

This project isn't actively maintained, although I'm happy to accept PRs.
I recommend using Vue Test Utils, which is based on avoriaz—https://github.com/vuejs/vue-test-utils

good to know, i'll try to migrate then, see if the problem is solvable on vue-test-utils. if not I'll make a pr there

authors: eddyerburgh mathijswesterhof riophae

repo: eddyerburgh/avoriaz

license: mit


text:
ColorChecker: New features

update remaining players live
store a history of the cells checked by each player to show an animation at the end
better visibility for point markers and strikethroughs (bold x for example)
if the player skips, a color is selected. bug!
include the filled color or column in the info bubble

done

repo: edelmaenner/edelgames


text:
Async call ACSK

As a e-health user
i want my requests signed with the DS to not be dependent on the availability of the CA provider services
So that I won't waste my time

list of certificated UA providers: http://www.ukrstat.gov.ua/elektr_zvit/inf_akcen/centr.htm

!Note
Each certificate contains crlDistributionPoints and crlDeltaDistributionPoints, so while every provider of OSCP did not describe URLs to get CRLs (Certificates   Revoked List) and URLs with  list of certificates on-hold, digital_signature server can store only revoked certificates of that providers, their certificates were checked in digital_signature server

Для сертификатов выпущеных АЦСК ДП УСС начиная с  19.06.2017:
Полный список отозванных сертификатов (обновляется 1 раз в неделю) -     https://csk.uss.gov.ua/download/crls/CSKUSS2017-Full.crl
Частичный список отозванных сертификатов (обновляется каждые 2 часа) - https://csk.uss.gov.ua/download/crls/CSKUSS2017-Delta.crl
Для сертификатов выпущеных АЦСК ДП УСС до 19.06.2017:
Полный список отозванных сертификатов (обновляется 1 раз в неделю) -     https://csk.uss.gov.ua/download/crls/CSKUSS-Full.crl
Частичный список отозванных сертификатов (обновляется каждые 2 часа) - https://csk.uss.gov.ua/download/crls/CSKUSS-Delta.crl
Спецализированного API нет и не может быть в любом из АЦСК УКРАИНЫ.
Списки отозванных сертификатов у всех АЦСК публичны и информациия о списках отозванных сертификатов (ссылки) содержится в сертификатах выданных АЦСК.
Но считается плохой практикой использовать данные списки. Как минимум существует 2-ух часовый коридор, когда сертификат отозван, а список отозванных сертификатов еще не опубликован (дельта CRL публикуется каждые 2 часа). Используйте онлайн проверку статуса сертификата – Online Certificate Status Protocol (OCSP).

це по провайдеру  ДП «Українські спеціальні системи»

+-108975 - 111491 - time of old function with OCSP check (from C)
+-88071 - 115869 - time of new with OCSP request  (from elixir)
+- 51742-58081 - time of new without OCSP request
new call of nif without OCSP request  fails with :nif_service_timeout
logic of test has problems?

authors: lymychp marinakr warehousman


text:
Make license_number required for pharmacy legal entity on create

#3370

Coverage remained the same at 88.43% when pulling 8ec3f687a1bdc4ae1645603f4bc5bd3a8f7374c5 on dev-3370-make-license-required-for-pharmacy-on-create-le into e2378ece15b9b64e8a437cae21d1eafe082510ce on develop.

authors: coveralls progsmile


text:
Failing tests on RDS

EdgeDB Version: 157e58b78315339ff620e04d7afcecb05f0505df
OS Version: macOS 11.2.1 Darwin Kernel Version 20.3.0 xnu-7195.81.3~1/RELEASE_X86_64
AWS RDS Version: 12.4

This is an issue to track all the failing tests when running on AWS RDS.

[x] ALTER ROLE ... SET password := ... fails. Fixed in #2282

[ ] test_edgeql_ddl_role_02 (test_edgeql_ddl.TestEdgeQLDDL)
Traceback (most recent call last):
  File "edb/testbase/server.py", line 127, in wrapper
    self.loop.run_until_complete(
  File "asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "tests/test_edgeql_ddl.py", line 6284, in test_edgeql_ddl_role_02
    await self.assert_query_result(
  File "edb/testbase/server.py", line 534, in assert_query_result
    self._assert_data_shape(res, exp_result_json, message=msg)
  File "edb/testbase/server.py", line 742, in _assert_data_shape
    return _assert_generic_shape((), data, shape)
  File "edb/testbase/server.py", line 710, in _assert_generic_shape
    return _assert_list_shape(path, data, shape)
  File "edb/testbase/server.py", line 660, in _assert_list_shape
    _assert_generic_shape(
  File "edb/testbase/server.py", line 714, in _assert_generic_shape
    return _assert_dict_shape(path, data, shape)
  File "edb/testbase/server.py", line 619, in _assert_dict_shape
    _assert_generic_shape(path + (f'["{sk}"]',), data[sk], sv)
  File "edb/testbase/server.py", line 730, in _assert_generic_shape
    self.fail(
AssertionError: data shape differs: False != True PATH: [0]["superuser"]

[ ] test_server_proto_ddlprop_01 (test_server_proto.TestServerProtoDdlPropagation)
Traceback (most recent call last):
  File "edb/testbase/server.py", line 127, in wrapper
    self.loop.run_until_complete(
  File "asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "tests/test_server_proto.py", line 1895, in test_server_proto_ddlprop_01
    async with tb.start_edgedb_server(adjacent_to=self.con) as sd:
  File "edb/testbase/server.py", line 1495, in __aenter__
    data = await asyncio.wait_for(
  File "asyncio/tasks.py", line 481, in wait_for
    return fut.result()
  File "edb/testbase/server.py", line 1431, in _read_runtime_info
    raise RuntimeError("EdgeDB server terminated")
RuntimeError: EdgeDB server terminated

[ ] test_edgeql_select_polymorphic_10 (test_edgeql_select.TestEdgeQLSelect) (passes when ran separately)
Traceback (most recent call last):
  File "edb/testbase/server.py", line 127, in wrapper
    self.loop.run_until_complete(
  File "asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "tests/test_edgeql_select.py", line 1538, in test_edgeql_select_polymorphic_10
    await self.assert_query_result(
  File "edb/testbase/server.py", line 547, in assert_query_result
    res = await self.con._fetchall(
  File "edgedb/asyncio_con.py", line 201, in _fetchall
    result, _ = await self._impl._protocol.execute_anonymous(
  File "edgedb/protocol/protocol.pyx", line 633, in execute_anonymous
  File "edgedb/protocol/protocol.pyx", line 405, in _execute
edgedb.errors.InternalServerError: remaining connection slots are reserved for non-replication superuser connections

The latter two are probably related to the RDS connection limit.  We need to query and surface that setting via BackendRuntimeParams and size our backend connection pool accordingly.  Bundled postgres clusters run with max_connections: 500 currently

Thanks for the clue! Will try again with bumped limit.

authors: elprans fantix

repo: edgedb/edgedb


text:
create function ddl is not transactional

This has been fixed by the schema rework.


text:
Rename test_dump04.py to test_dump_v2.py

Since we're likely going to want to introduce a new dump test for each
major version we release, I want to name them based on major release
version numbers, moving forward.
I'll cherry-pick this commit onto our 2.0 branch to build dumps.

Ha, if I cherry pick it to build the dumps, then it thinks the version is 2.1, so instead I am running gen-test-dumps as uncommitted changes with EDGEDB_BUILD_IS_RELEASE=1 set


text:
fix: Make default http export secret settings blank as default

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Http Export has secrets setting populated causing TAF tests to fail
Issue Number: #279
What is the new behavior?
Http Export has secrets setting back to un-set
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Are there any new imports or modules? If so, what are they used for and why?
no
Are there any specific instructions or things that should be known prior to reviewing?
Other information

recheck

repo: edgexfoundry/app-service-configurable


text:
helm deployment: edgex-ui-go does not work

🐞 Bug Report
Affected Services [REQUIRED]
edgex-ui
Is this a regression?
This has probably always been broken in the Kubernetes deployment in secure mode.
Description and Minimal Reproduction [REQUIRED]
See discussion for original bug report.
🔥 Exception or Error

edgex-ui-go container logs contains:

/(target service)/api/v3/ping
2023/09/20 18:03:53 http: proxy error: context deadline exceeded

🌍  Your Environment
Deployment Environment: kubernetes
EdgeX Version [REQUIRED]: main (pending 3.1)
Anything else relevant?

This functionality is broken because edgex-ui forwards requests to the EdgeX API gateway.
In the Docker deployment, it does this through an internal unencrypted HTTP port and passes the authentication token through.
This is configured in the edgex-ui configuration file res/docker/configuration.yaml:
APIGateway:
    Server: edgex-nginx
    ApplicationPort: 8000
    ApplicationPortSSL: 8443

These values are incorrect and not overridden in the helm chart deployment.
A possible override is:
--- a/templates/edgex-ui/edgex-ui-deployment.yaml
+++ b/templates/edgex-ui/edgex-ui-deployment.yaml
@@ -39,6 +39,10 @@ spec:
           hostIP: {{.Values.edgex.hostPortExternalBind}}
         {{- end}}
         env:
+        - name: APIGATEWAY_SERVER
+          value: ingress-nginx-controller.ingress-nginx.svc
+        - name: APIGATEWAY_APPLICATIONPORT
+          value: "80"

This will cause the edgex-ui backend to send requests to the internal HTTP service port for the NGINX ingress controller.
After making these changes, edgex-ui will behave as follows (where 10.108.97.79 is the service ip of edgex-ui)
$ curl -i http://10.108.97.79:4000/core-data/api/v3/ping
HTTP/1.1 404 Not Found
Content-Length: 146
Content-Type: text/html

While this is better than the HTTP 503 error, it still does not work.
This is because the core-data ingress resource is declared as follows:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  labels:
    org.edgexfoundry.service: {{.Values.edgex.app.core.data}}
  name: {{.Values.edgex.app.core.data}}
  annotations:
    nginx.ingress.kubernetes.io/rewrite-target: /$1
    nginx.ingress.kubernetes.io/auth-tls-verify-client: "on"
    nginx.ingress.kubernetes.io/auth-tls-secret: "edgex/edgex-client-ca"
    nginx.ingress.kubernetes.io/auth-tls-verify-depth: "1"
spec:
  ingressClassName: nginx
  rules:
  - host: "{{.Values.edgex.security.tlsHost}}"
    http:
      paths:
      - path: /core-data/(.*)
        pathType: Prefix
        backend:
          service:
            name: {{.Values.edgex.app.core.data}}
            port:
              name: http
  tls:
  - secretName: edgex-tls
    hosts:
    - "{{.Values.edgex.security.tlsHost}}"

Where tlsHost defaults to edgex.
In other words, the ingress controller is listening on a mutual-auth TLS required TLS host named "edgex".
This means that only the following kinds of requests will be honored:
$ curl -s --resolve edgex:443:ipaddress --cacert server-ca.pem --cert client.pem --key client.key  "https://edgex/..."

In other words, they must be edgex hostname, on some ipaddress, with a client certificate and key supplied.
The helm deployment of EdgeX does not implement JWT authentication via the ingress controller, but relies on mutual-auth TLS instead.  Prior to EdgeX 3.0, it was not safe to expose EdgeX services directly via ingress routes, as the services themselves had not direct way to authenticate incoming requests.  Even in EdgeX 3.0, there may still be some API routes that are unauthenticated, so directly exposing EdgeX services via Kubernetes ingress resources is risky.
Since the ingress controller doesn't check JWT authentication and edgex-ui-go does not have access to the TLS certificate and key to successfully pass TLS client authentication, edgex-ui-go is unable to reissue the background request.
In other words, edgex-ui is broken in the helm deployment in secure mode.

repo: edgexfoundry/edgex-helm


text:
GetCloudletManifest re-creates the password for configure-node.sh script every time you run it

Since it re-creates the password every time, if there is already a node trying to download the ansible tarball, it fails to authenticate. We should keep the password and not re-generate it every time.

CreateCloudletNodeReq in cloudletnode_api.go re-creates the new password, since we create a hash, which we cannot just revert. It looks like we should store basic auth hash somewhere(maybe in vault) in order to be able to generate the manifest consistently.

repo: edgexr/edge-cloud-platform


text:
update readme translation

Update README.md file translation

Il serai intéressant de traduire le guide d'écriture. Tu serais prêt à le faire?

Oui tu peux me tag dans l'issue en question

repo: edimitchel/docs-fr


text:
Add more favicons to db #162

Addressing #162 ; @edoardottt , once you are good and merge this to devel, I could add the favicon value from #161. Do you want me to create a new branch for 161?

Do you want me to create a new branch for 161?

Yeah, it would be better

authors: edoardottt iamshreeram

repo: edoardottt/favirecon


text:
关于柱状图的优化

如果维度栏和颜色栏存在相同的，使用柱状图的图表就会变细，且样式不可配置

我的还会出现一堆0

authors: CharlesTHN Mryandada


text:
Text Color

text color is not working.
<br.com.stickyindex.StickyIndex
android:id="@+id/sticky_index_container_filter_by_league"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:textColor="#FFFFFF"
android:layout_marginTop="@dimen/dp72"
android:rowHeight="@dimen/dp7" />

Fixed in version 1.3.0 - see README.md to see how to obtain that.
<br.com.stickyindex.view.StickyIndex
            android:id="@+id/stickyIndex"
            android:layout_width="80dp"
            android:layout_height="wrap_content"
            android:textSize="20sp"
            android:textStyle="bold"
            app:rowHeight="64dp"
            app:stickyWidth="60dp"
            android:textColor="#0236e0"/>

authors: edsilfer ozankonur

repo: edsilfer/sticky-index


text:
Auth Views

Added signup and signin forms views.

Resolves edu-python-course/tasktracker#10, edu-python-course/tasktracker#11

repo: edu-python-course/tasktracker-bootstrap


text:
Laravel Validation

Is it possible to add some functionality to easily add all Laravel Validation errors to a NotificationBag

That sure is possible. Why don't you create a PR?

I hope I've done it right. At least, it works for me.
See: https://github.com/edvinaskrucas/notification/pull/76

authors: emielmolenaar mitchellklijs

repo: edvinaskrucas/notification


text:
How to pass variables($input) to fields written within getSubscription?

My components have query fragments of the following form:
initialVariables : {
	type : 'videos',
	pageSize : 10,
	community : 3
},
fragments: {
	viewer: () => Relay.QL`
		fragment on Viewer {
			id,
			newItemsAvailable(type : $type, community : $community),
			newsFeedItems(first : $pageSize, type : $type, community : $community) {
				pageInfo {
					hasNextPage
				},
				edges {
					cursor,
					node {
						...
					}
				}
			}
		}
	`
},

I want to subscribe to changes in the field newItemsAvailable. To do so I would need the following getSubscription function:
getSubscription() {
  return Relay.QL`
    subscription {
      newsFeedItemsAvailableSubscription(input: $input) {
        viewer {
          newItemsAvailable(type : $type, community : $community)
        }
      }
    }
  `;
}

I can't omit (type : $type, community : $community)  from here since that would give an error. In the worst case I would have to send dummy hardcoded values.
I guess
subscriptions: [
    ({ viewer, type, community }) => new NewsFeedItemsAvailableSubscription({ viewer, type, community }),
  ]

and
getVariables() {
  return {
    id: this.props.viewer.id,
    type: this.props.type,
    community: this.props.community
  };
}

feed the values of type and community into $input through ...subscription.getVariables(). However, how can I make them available in newItemsAvailable(type : $type, community : $community). I haven't looked into the source code of Relay so have no clue of how all this generally works.

If the above isn't possible(using $input), I feel the above snippets are sufficient to get an understanding of what I am trying to do here. Does Relay store fields fetched using separate variables separately? If so, I think it makes sense to subscribe multiple times on the same field using different variables and the above pattern is one that I think can be used.

https://github.com/facebook/relay/issues/1046 seems relevant. Especially the comment by nodkz on the "new Mutation API".

repo: edvinerikson/relay-subscriptions


text:
Highlighting doesn't trigger unless there's a space

The original version of this extension worked without a space, e.g. //? would produce a blue highlight. I've just upgraded to this newe one and it seems to have gotten lost along the way.

Please check https://github.com/edwinhuish/better-comments-next/issues/2#issuecomment-1868548243

authors: edwinhuish texonidas

repo: edwinhuish/better-comments-next


text:
Removing legacy code related to My Videos

Description
LEARNER-7221
We had removed My Videos section in iOS release V2.12.1. But still, some code that was related to My Videos section is present and executing in the background. Also removed course_enrollments call that was being sent in the background thread. This API call was also required for the My Videos section,
Notes
How to test this PR

@saeedbashir Test cases are failing.

@salman2013 Ready for another pass.

repo: edx/edx-app-ios


text:
Make all success alerts disappear after some time

The alert messages are now closed by the users. This issue aims to make them disappear on their own after some time.

Hey, does this issue still needs to be fixed?

Yes it's still an active issue.

Alright, gonna be reviewing the code to fix it.

I tried to solve it and hope fully that solution suits you I have given pull request for this issue

authors: IoannisSina Vaibhav234k Vansh-Baghel


text:
Incorrect Indentation of Comments when Using stringify() Function

Describe the bug
I am experiencing an issue with the stringify() function. The function does not maintain the correct indentation for comments in the output YAML when the input YAML has commented-out sections.
To Reproduce

Provide the following YAML as input to the stringify() function:

definitions:
  properties:
    SomeRequest:
        email:
#        sampleEnum:
#          type: string
#          enum:
#            - first value
#            - second one
#            - last
#          default: 'first value'

Run the stringify() function to format the YAML.

definitions:
  properties:
    SomeRequest:
      email:
        #        sampleEnum:
        #          type: string
        #          enum:
        #            - first value
        #            - second one
        #            - last
        #          default: 'first value'

Expected behaviour
The output YAML should maintain the original indentation of the comments as shown in the input:
Versions (please complete the following information):

yaml: 2.5.0

This is not a bug. Your comments clearly contain significant leading whitespace within the comment body, and this is intentionally retained normalizing their indentation.

Is there any possible configuration to retain original comment indentation?

The lower-level CST contains all parts of the input: https://eemeli.org/yaml/#parser

authors: Krzysztof-Kolodziejczyk eemeli

repo: eemeli/yaml

license: ISC


text:
Live debugging

-d / --debug
This option will let you peek in the stash or run IPython on the current step.
Commands

s: prints stash
d: opens Interactive Python.
h: prints commands
In Python shell, context can be accessed via step.context.stash. Note that modifications to step object will carry over to the steps below.
It is usually a better idea to inspect the stash before the step being debugged.

Notes

I was hoping to have an interactive and colorful way of parsing the stash, but this was the solution I could come up with.
Curses can be added to run the commands with a single click instead of pressing enter afterwards. However, I would need help to prevent curses from clearing the screen. (Which I is probably not easy)

Pull Request Test Coverage Report for Build 1108

8 of 24 (33.33%)  changed or added relevant lines in 2 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.05%) to 59.358%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

terraform_compliance/main.py
2
3
66.67%

terraform_compliance/steps/terrain.py
6
21
28.57%

Files with Coverage Reduction
New Missed Lines
%

terraform_compliance/common/defaults.py
6
84.21%

Totals

Change from base Build 1101:
-0.05%

Covered Lines:
1294

Relevant Lines:
2180

💛  - Coveralls

authors: Kudbettin coveralls

repo: eerkunt/terraform-compliance


text:
Validation error disappears from screen

If I select a line in an XML file that failed to validate against the XSD file, the error appears in the status bar at the bottom of the application. However, it disappears after a few seconds so I can no longer read the error. Is this expected? Are the errors logged anywhere else? Thanks

This should be fixed in v0.3.7.
It'll a take a while to land in Package Control, but if you have the time, could you give it a go and let me know whether it fixes the issue for you?

Thanks, I'll try to install it soon.

I'll close this, but if the issue isn't fixed for you, please let me know and I'll take another look.

authors: eerohele stodge

repo: eerohele/exalt


text:
🛑 Almacenata is down

In a2c5d82, Almacenata (http://www.almacenata.coop.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacenata is back up in 3661aa3.

repo: efecear/upptime


text:
🛑 efece.ar is down

In 8fef936, efece.ar (https://www.efece.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: efece.ar is back up in 3fdc23b after 20 minutes.


text:
🛑 Jorge Retamoza Web is down

In 516a151, Jorge Retamoza Web (https://www.retamoza.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jorge Retamoza Web is back up in 681d906 after 12 minutes.


text:
🛑 Nodo UTT Ramos Mejia is down

In 03a92b0, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 0aeab19 after 23 minutes.


text:
🛑 Almacén BioPandora is down

In a377722, Almacén BioPandora (https://www.biopandora.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén BioPandora is back up in 4e5d20d.


text:
🛑 Nodo UTT Ramos Mejia is down

In 2c8a8dd, Nodo UTT Ramos Mejia (https://www.uttnodoramosmejia.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nodo UTT Ramos Mejia is back up in 767ba4b.


text:
🛑 Almacén Reina Batata is down

In c3a8d52, Almacén Reina Batata (https://www.reina-batata.com.ar) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Almacén Reina Batata is back up in efbb2a4.


text:
[BUG] User registeration does not save name and lastname

The service simply does not take name and last name as variables, requires quick fixing

Probably will not fix beacuse I do not need name and surname in the app.


text:
[WIP] feat: impl the real ContextModel

see https://github.com/eggjs/egg/issues/1885

Checklist

[ ] npm test passes
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message follows commit guidelines

Affected core subsystem(s)

Description of change

Codecov Report

Merging #36 into master will decrease coverage by 6.12%.
The diff coverage is 78.57%.

@@            Coverage Diff             @@
##           master      #36      +/-   ##
==========================================
- Coverage     100%   93.87%   -6.13%
==========================================
  Files           5        5
  Lines          37       49      +12
==========================================
+ Hits           37       46       +9
- Misses          0        3       +3

Impacted Files
Coverage Δ

agent.js
100% <ø> (ø)
:arrow_up:

app/extend/context.js
100% <100%> (ø)
:arrow_up:

lib/loader.js
92.1% <66.66%> (-7.9%)
:arrow_down:

Continue to review full report at Codecov.

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

repo: eggjs/egg-sequelize


text:
support exec without arguments.

Hey, this tool is useful, but when i use it at first time by exec nw, i found a problem: there's nothing output.
maybe you should let it support exec without any arguments, just like other cli.
if it doesn't work without correct number of arguments, show people how to use it, not keep silent.
: )

Awesome, merged.

authors: egoist soulteary

repo: egoist/nwjs


text:
Panic instead of partially running actions

This PR changes the ignores in lib.rs to panics, as a stopgap against half-run rules. It also fixes the resulting failing tests by doing the demand transformation manually.

This resolves the most urgent concern from #228, which is that rules can fail silently.

Looks good. Can you add an explicit panic message?

Added.

authors: Alex-Fischman mwillsey

repo: egraphs-good/egglog


text:
Question about licensing of Terracotta classes

Are Terracotta classess embedded into final jars governed by Apache 2.0 or Terracotta Public License?
If I use ehache, do I have to include the phrase "Powered by Terracotta" as a clickable hyperlink directing to http://www.terracotta.org at the bottom of any user interface screen ?

If you simply use ehcache foss jar, there are no classes within that licensed for TPL.
If you use a bundling that includes the Terracotta client libraries, or additionally include (distribute) the ehcache-terracotta jar, then yes, that includes items currently licensed under TPL.
How to adhere to the TPL license would be a question for your lawyer, but probably isn't far off what you noted in your question.

authors: jhouserizer wojteo


text:
Update cache-event-listeners.adoc

Did a small language tweak

Can one of the admins verify this patch?


text:
Grant Daniel Karlsson reviewer rights

I recommend to add Daniel Karlsson into the reviewers team.
Originally posted by @kruzikh in https://github.com/ehn-dcc-development/ehn-dcc-valuesets/issues/46#issuecomment-1023138015
Handle: danka74

@skounis @ryanbnl Agree to invite Daniel as an outside collaborator? Also agree to give him reviewer rights?

Is he working for one of the MS or EC?
--
Ryan
On Thu, 27 Jan 2022 at 14:14, Meinte Boersma @.***>
wrote:

@skounis https://github.com/skounis @ryanbnl
https://github.com/ryanbnl Agree to invite Daniel as an outside
collaborator? Also agree to give him reviewer rights?
—
Reply to this email directly, view it on GitHub
https://github.com/ehn-dcc-development/ehn-dcc-valuesets/issues/47#issuecomment-1023193597,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADPLHII5Z6MEG3ZTJNYWITUYFAMLANCNFSM5M53RPEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Daniel is a member of the semantic subgroup.

Then it's a no brainer, of course he can be added :)
--
Ryan
On Thu, 27 Jan 2022 at 14:20, Hynek @.***> wrote:

Daniel is a member of the semantic subgroup.
—
Reply to this email directly, view it on GitHub
https://github.com/ehn-dcc-development/ehn-dcc-valuesets/issues/47#issuecomment-1023204181,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADPLHLNPIO45V5PRVCPJHDUYFBDRANCNFSM5M53RPEA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I invited danka74 with “Triage” right which should suffice for reviewing. We can grant more rights at any time.

authors: dslmeinte kruzikh ryanbnl

repo: ehn-dcc-development/ehn-dcc-valuesets


text:
add reed solomon encoding

Add reed solomon encoding by wrapping the rust reed-solomon-simd crate and exposing it via FFI.
Part of #141

Thanks for all the feedback. :) Addressed it all. Added some limitations for total shards and shard size, that should prevent any overflows too.

repo: eigerco/strawberry


text:
Refactor coordinates and add support for 4-Vectors

Fixes #517

Things to do:

[x] Write tests for refactor
[x] Update examples, metric, Example Notebooks (wherever coordinates were removed in #512).
[ ] Update CHANGELOG

Mini-Changelog:

einsteinpy.coordinates:

Renamed coordinates.velocity to coordinates.differential
Added 4-Vector support to core and differential (formerly, velocity)
Added support for calculation of time-like component of 4-Velocity

einsteinpy.metric:

Added support for einsteinpy.coordinates.differential
Added support for astropy.units
Refactored metric.Schwarzschild and metric.KerrNewman
Partially fixed #523:

Update 1: Schwarzschild is error-free now. Metric definitions in Kerr and KerrNewman are error-free too. Remaining methods (_christoffels, _dg_dx, f_vec) are yet to be altered.
Update 2: Schwarzschild and Kerr are error-free now.  KerrNewman is yet to be altered.
Update 3: KerrNewman's f_vec needs to be cross-checked. Remaining methods have been corrected.

einsteinpy.geodesic:

Added support for einsteinpy.coordinates.differential
Added support for astropy.units
Moved old code to Geodesic class, while Time-like geodesic calculation is now through TimelikeGeodesic class (which derives from Geodesic)
Added state class variable, that stores the initial state of the particle.

einsteinpy.units:

Added a primitive() function, that helps in obtaining float values out of astropy.units.quantity.Quantity objects.
Removed astro_dist & astro_sec (These are just scaling factors and these are not being used anywhere at the moment - Removed to get better codecov diff score)

einsteinpy.bodies:

Refactored bodies to remove a (Fixes #517) and some minor changes.

Fixed #517, #524, partially fixed #523

Added new tests and refactored old tests, wherever applicable

Refactored example notebooks

Hello @JeS24! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file src/einsteinpy/bodies.py:

Line 73:121: E501 line too long (174 > 120 characters)
Line 76:121: E501 line too long (174 > 120 characters)

In the file tests/test_bodies.py:

Line 88:121: E501 line too long (158 > 120 characters)
Line 96:121: E501 line too long (158 > 120 characters)

@shreyasbapat Is CodeClimate supposed to check tests/?

MyPy needs to be less aggressive with type checking.

The tests would fail most probably. @shreyasbapat There were the issues, I was talking about. However, I am attempting a minor fix/refactor, which may fix these, without removing astropy.units.

@shreyasbapat PR is ready for review now.

I will review in a while. I am very busy for a couple of days. You can start working on other things for now.

@shreyasbapat Yeah, I am currently working on Null Geodesics, working out the equations and all.

repo: einsteinpy/einsteinpy


text:
Fix windows build

Fixes #31

Looks like there's a regression - now the Ubuntu build fails?

Looks like there's a regression - now the Ubuntu build fails?

Sorry, I didn't have a change to resolve the regression issue. I've looked into it further and I'm hitting a roadblock.
https://github.com/vitejs/vite/blob/main/packages/vite/src/node/plugins/html.ts#L385
config.root = C:/Users/schal/storybook-builder-vite/packages/example-react
id = C:/Users/schal/storybook-builder-vite/packages/storybook-builder-vite/input/iframe.html
shortEmitName = ../storybook-builder-vite/input/iframe.html
However, vite:html complains at this point because it expects an absolute path relative to config.root. I have a feeling your originally approach was correct and using a virtual input is the way to go.

I've re-written the fix to still use the virtual input entry, however it is now using ${config.root}/iframe.html for the virtual id.

Did a squash force push to tidy things up

I rebased on top of https://github.com/eirslett/storybook-builder-vite/pull/51, and CI passes now.  This looks like a good fix, thanks @schalk-b!

authors: IanVS eirslett schalk-b

repo: eirslett/storybook-builder-vite