text:
pydantic dependency seems to be broken

Solution to issue cannot be found in the documentation.

[X] I checked the documentation.

Issue
Thank you for this awesome package!
I just did a fresh install of ome-types (both 0.4.0 and 0.3.3), and found that the dependency in the recipe may be broken. I didn't look into to the details but probably the recipe needs pydantic<2.0.0?
The followings are the error message from just running import ome_types for both versions.
From v0.4.0
cannot set '__get_pydantic_core_schema__' attribute of immutable type 'lxml.etree.QName'

From v0.3.3
---------------------------------------------------------------------------
PydanticImportError                       Traceback (most recent call last)
Cell In[1], line 1
----> 1 import ome_types

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/__init__.py:11
      8     __version__ = "unknown"
     10 try:
---> 11     from . import model
     12     from .model import OME
     13 except ModuleNotFoundError as e:

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/model/__init__.py:2
      1 from .affine_transform import AffineTransform
----> 2 from .annotation import Annotation
      3 from .annotation_ref import AnnotationRef
      4 from .arc import Arc

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/model/annotation.py:7
      3 from pydantic import Field
      5 from ome_types._base_type import OMEType
----> 7 from .annotation_ref import AnnotationRef
      8 from .simple_types import AnnotationID, ExperimenterID
     11 class Annotation(OMEType):

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/model/annotation_ref.py:3
      1 from ome_types._base_type import OMEType
----> 3 from .reference import Reference
      4 from .simple_types import AnnotationID
      7 class AnnotationRef(Reference, OMEType):

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/model/reference.py:6
      2 from weakref import ReferenceType
      4 from ome_types._base_type import OMEType
----> 6 from .simple_types import LSID
      9 class Reference(OMEType):
     10     """Reference is an empty complex type that is contained and extended by all the
     11     `*Ref` elements and also the Settings Complex Type Each `*Ref` element defines
     12     an attribute named ID of simple type `*ID` and no other information Each
     13     simple type `*ID` is restricted to the base type LSID with an appropriate
     14     pattern
     15     """

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/ome_types/model/simple_types.py:5
      2 from enum import Enum
      4 from pydantic import color
----> 5 from pydantic.types import ConstrainedFloat, ConstrainedInt, ConstrainedStr
      8 class base64Binary(ConstrainedStr):
      9     pass

File ~/miniconda3/envs/ome3/lib/python3.11/site-packages/pydantic/_migration.py:295, in getattr_migration.<locals>.wrapper(name)
    289     raise PydanticImportError(
    290         '`BaseSettings` has been moved to the `pydantic-settings` package. '
    291         f'See https://docs.pydantic.dev/{VERSION}/migration/#basesettings-has-moved-to-pydantic-settings '
    292         'for more details.'
    293     )
    294 if import_path in REMOVED_IN_V2:
--> 295     raise PydanticImportError(f'`{import_path}` has been removed in V2.')
    296 globals: Dict[str, Any] = sys.modules[module].__dict__
    297 if name in globals:

PydanticImportError: `pydantic.types:ConstrainedFloat` has been removed in V2.

For further information visit https://errors.pydantic.dev/2.1.1/u/import-error

Installed packages
For v0.4.0

# Name                    Version                   Build  Channel
annotated-types           0.5.0              pyhd8ed1ab_0    conda-forge
appnope                   0.1.3              pyhd8ed1ab_0    conda-forge
asttokens                 2.2.1              pyhd8ed1ab_0    conda-forge
backcall                  0.2.0              pyh9f0ad1d_0    conda-forge
backports                 1.0                pyhd8ed1ab_3    conda-forge
backports.functools_lru_cache 1.6.5              pyhd8ed1ab_0    conda-forge
brotli-python             1.0.9           py311h814d153_9    conda-forge
bzip2                     1.0.8                h0d85af4_4    conda-forge
ca-certificates           2023.7.22            h8857fd0_0    conda-forge
certifi                   2023.7.22          pyhd8ed1ab_0    conda-forge
charset-normalizer        3.2.0              pyhd8ed1ab_0    conda-forge
click                     8.1.6           unix_pyh707e725_0    conda-forge
click-default-group       1.2.2              pyhd8ed1ab_1    conda-forge
dataclasses               0.8                pyhc8e2a94_3    conda-forge
decorator                 5.1.1              pyhd8ed1ab_0    conda-forge
docformatter              1.7.5              pyhd8ed1ab_0    conda-forge
executing                 1.2.0              pyhd8ed1ab_0    conda-forge
icu                       72.1                 h7336db1_0    conda-forge
idna                      3.4                pyhd8ed1ab_0    conda-forge
importlib-metadata        6.8.0              pyha770c72_0    conda-forge
importlib_metadata        6.8.0                hd8ed1ab_0    conda-forge
ipython                   8.14.0             pyhd1c38e8_0    conda-forge
jedi                      0.18.2             pyhd8ed1ab_0    conda-forge
jinja2                    3.1.2              pyhd8ed1ab_1    conda-forge
libcxx                    16.0.6               hd57cbcb_0    conda-forge
libexpat                  2.5.0                hf0c8a7f_1    conda-forge
libffi                    3.4.2                h0d85af4_5    conda-forge
libiconv                  1.17                 hac89ed1_0    conda-forge
libsqlite                 3.42.0               h58db7d2_0    conda-forge
libxml2                   2.11.4               hd95e348_0    conda-forge
libxslt                   1.1.37               h20bfa82_1    conda-forge
libzlib                   1.2.13               h8a1eda9_5    conda-forge
lxml                      4.9.3           py311h19a211c_0    conda-forge
markupsafe                2.1.3           py311h2725bcf_0    conda-forge
matplotlib-inline         0.1.6              pyhd8ed1ab_0    conda-forge
ncurses                   6.4                  hf0c8a7f_0    conda-forge
ome-types                 0.4.0              pyhd8ed1ab_0    conda-forge
openssl                   3.1.1                h8a1eda9_1    conda-forge
parso                     0.8.3              pyhd8ed1ab_0    conda-forge
pexpect                   4.8.0              pyh1a96a4e_2    conda-forge
pickleshare               0.7.5                   py_1003    conda-forge
pint                      0.22               pyhd8ed1ab_1    conda-forge
pip                       23.2.1             pyhd8ed1ab_0    conda-forge
prompt-toolkit            3.0.39             pyha770c72_0    conda-forge
prompt_toolkit            3.0.39               hd8ed1ab_0    conda-forge
ptyprocess                0.7.0              pyhd3deb0d_0    conda-forge
pure_eval                 0.2.2              pyhd8ed1ab_0    conda-forge
pydantic                  2.1.1              pyhd8ed1ab_0    conda-forge
pydantic-core             2.4.0           py311h299eb51_0    conda-forge
pygments                  2.15.1             pyhd8ed1ab_0    conda-forge
pysocks                   1.7.1              pyha2e5f31_6    conda-forge
python                    3.11.4          h30d4d87_0_cpython    conda-forge
python_abi                3.11                    3_cp311    conda-forge
readline                  8.2                  h9e318b2_1    conda-forge
requests                  2.31.0             pyhd8ed1ab_0    conda-forge
setuptools                68.0.0             pyhd8ed1ab_0    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
stack_data                0.6.2              pyhd8ed1ab_0    conda-forge
tk                        8.6.12               h5dbffcc_0    conda-forge
toposort                  1.10               pyhd8ed1ab_0    conda-forge
traitlets                 5.9.0              pyhd8ed1ab_0    conda-forge
typing-extensions         4.7.1                hd8ed1ab_0    conda-forge
typing_extensions         4.7.1              pyha770c72_0    conda-forge
tzdata                    2023c                h71feb2d_0    conda-forge
untokenize                0.1.1                      py_0    conda-forge
urllib3                   2.0.4              pyhd8ed1ab_0    conda-forge
wcwidth                   0.2.6              pyhd8ed1ab_0    conda-forge
wheel                     0.41.0             pyhd8ed1ab_0    conda-forge
xsdata                    23.7               pyhd8ed1ab_0    conda-forge
xz                        5.2.6                h775f41a_0    conda-forge
zipp                      3.16.2             pyhd8ed1ab_0    conda-forge

For v0.3.3
# Name                    Version                   Build  Channel
annotated-types           0.5.0              pyhd8ed1ab_0    conda-forge
appnope                   0.1.3              pyhd8ed1ab_0    conda-forge
asttokens                 2.2.1              pyhd8ed1ab_0    conda-forge
backcall                  0.2.0              pyh9f0ad1d_0    conda-forge
backports                 1.0                pyhd8ed1ab_3    conda-forge
backports.functools_lru_cache 1.6.5              pyhd8ed1ab_0    conda-forge
bzip2                     1.0.8                h0d85af4_4    conda-forge
ca-certificates           2023.7.22            h8857fd0_0    conda-forge
decorator                 5.1.1              pyhd8ed1ab_0    conda-forge
elementpath               2.5.3              pyhd8ed1ab_0    conda-forge
executing                 1.2.0              pyhd8ed1ab_0    conda-forge
icu                       72.1                 h7336db1_0    conda-forge
ipython                   8.14.0             pyhd1c38e8_0    conda-forge
jedi                      0.18.2             pyhd8ed1ab_0    conda-forge
libexpat                  2.5.0                hf0c8a7f_1    conda-forge
libffi                    3.4.2                h0d85af4_5    conda-forge
libiconv                  1.17                 hac89ed1_0    conda-forge
libsqlite                 3.42.0               h58db7d2_0    conda-forge
libxml2                   2.11.4               hd95e348_0    conda-forge
libxslt                   1.1.37               h20bfa82_1    conda-forge
libzlib                   1.2.13               h8a1eda9_5    conda-forge
lxml                      4.9.3           py311h19a211c_0    conda-forge
matplotlib-inline         0.1.6              pyhd8ed1ab_0    conda-forge
ncurses                   6.4                  hf0c8a7f_0    conda-forge
ome-types                 0.3.3              pyhd8ed1ab_0    conda-forge
openssl                   3.1.1                h8a1eda9_1    conda-forge
parso                     0.8.3              pyhd8ed1ab_0    conda-forge
pexpect                   4.8.0              pyh1a96a4e_2    conda-forge
pickleshare               0.7.5                   py_1003    conda-forge
pint                      0.22               pyhd8ed1ab_1    conda-forge
pip                       23.2.1             pyhd8ed1ab_0    conda-forge
prompt-toolkit            3.0.39             pyha770c72_0    conda-forge
prompt_toolkit            3.0.39               hd8ed1ab_0    conda-forge
ptyprocess                0.7.0              pyhd3deb0d_0    conda-forge
pure_eval                 0.2.2              pyhd8ed1ab_0    conda-forge
pydantic                  2.1.1              pyhd8ed1ab_0    conda-forge
pydantic-core             2.4.0           py311h299eb51_0    conda-forge
pygments                  2.15.1             pyhd8ed1ab_0    conda-forge
python                    3.11.4          h30d4d87_0_cpython    conda-forge
python_abi                3.11                    3_cp311    conda-forge
readline                  8.2                  h9e318b2_1    conda-forge
setuptools                68.0.0             pyhd8ed1ab_0    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
stack_data                0.6.2              pyhd8ed1ab_0    conda-forge
tk                        8.6.12               h5dbffcc_0    conda-forge
traitlets                 5.9.0              pyhd8ed1ab_0    conda-forge
typing-extensions         4.7.1                hd8ed1ab_0    conda-forge
typing_extensions         4.7.1              pyha770c72_0    conda-forge
tzdata                    2023c                h71feb2d_0    conda-forge
wcwidth                   0.2.6              pyhd8ed1ab_0    conda-forge
wheel                     0.41.0             pyhd8ed1ab_0    conda-forge
xmlschema                 1.11.3             pyhd8ed1ab_0    conda-forge
xz                        5.2.6                h775f41a_0    conda-forge

### Environment info

```shell
active environment : ome3
    active env location : /Users/hayato.ikoma/miniconda3/envs/ome3
            shell level : 2
       user config file : /Users/hayato.ikoma/.condarc
 populated config files : /Users/hayato.ikoma/.condarc
          conda version : 23.7.2
    conda-build version : not installed
         python version : 3.9.17.final.0
       virtual packages : __archspec=1=x86_64
                          __osx=10.16=0
                          __unix=0=0
       base environment : /Users/hayato.ikoma/miniconda3  (writable)
      conda av data dir : /Users/hayato.ikoma/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/main/osx-64
                          https://conda.anaconda.org/main/noarch
                          https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
                          https://repo.anaconda.com/pkgs/main/osx-64
                          https://repo.anaconda.com/pkgs/main/noarch
                          https://repo.anaconda.com/pkgs/r/osx-64
                          https://repo.anaconda.com/pkgs/r/noarch
          package cache : /Users/hayato.ikoma/miniconda3/pkgs
                          /Users/hayato.ikoma/.conda/pkgs
       envs directories : /Users/hayato.ikoma/miniconda3/envs
                          /Users/hayato.ikoma/.conda/envs
               platform : osx-64
             user-agent : conda/23.7.2 requests/2.31.0 CPython/3.9.17 Darwin/22.5.0 OSX/10.16
                UID:GID : 503:20
             netrc file : None
           offline mode : False

0.4.0 works with both pydantic 1 and 2.
I've seen that issue, but thought i had caught it with a try block...
In any case, this should go in the ome types repo (and not the feedstock here), can you open the issue over there?
Thanks

oh, yeah, I just tested it here.  I believe you can safely ignore that message (I'll silence it in a future release).  import ome_types still works though no?  It does for me when I run
$ mamba create -n ometest ome-types
$ mamba activate ometest
$ python -c "import ome_types; print(ome_types")
cannot set '__get_pydantic_core_schema__' attribute of immutable type 'lxml.etree.QName'
<module 'ome_types' from '~/mambaforge/envs/ometest/lib/python3.11/site-packages/ome_types/__init__.py'>
``

the message is removed in https://github.com/tlambert03/ome-types/pull/211

Thank you for looking into it!

(V0.3.3 definitely does not work with pydantic 2)

If that's the case, could we have pydantic < 2.0.0 for ome-types < 4.0.0? I actually tried to install 0.3.3 in a fresh environment and hit the error I posted above.

right, 0.3.3 is quite old at this point.  before I knew that pydantic was going to be so different and a pin was needed.  I could technically go back and patch the release, but note that you can also do it yourself by stating conda create -n ttt 'ome-types<0.4' 'pydantic<2'.  Is there a reason you want to use 0.3.3 instead of ome types 0.4.0?

see #12

Oh, sorry. I didn't know it will be a huge amount of work because I've never written a conda recipe. I was thinking that it would be just appending <2 somewhere. Thank you for working on it.
Yes, I know I can do pydantic<2 when I create a new environment. But I just thought it would be nice to have it for the community and prevent others from having the same issue.
I had a couple of issues with 0.3.3 around validation throwing out errors in a weird situation (e.g. openmicroscopy website was temporarily down, somehow malformed xml schema was used for validation due to some internet connection issues). As 0.3 -> 0.4 upgrade sounds like a huge upgrade (haven't looked into what's changed), I was considering to keep using 0.3 for now to prevent having more unknown errors.

It's not a huge upgrade.  I put a lot of work into making sure that 0.4 is backwards compatible.  So you should be able to just use 0.4 with your existing code.  You may see a number of name change warnings, but they will tell you what you need to change.  But I tested at least 4 external packages that heavily use ome types to make sure that 0.4 didn't break their usage.
More info here, but I'd say give it a try
https://ome-types.readthedocs.io/en/latest/migration/

repo: conda-forge/ome-types-feedstock


text:
Constrain python versions

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

@conda-forge-admin, please rerender

source: gharchive/pull-request

authors: conda-forge-linter xylar

license_type: permissive

license_source: github-api


text:
Windows build

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/parallel This is ready for review/merge.

thanks !

authors: conda-forge-linter rvalieris xhochy

repo: conda-forge/parallel-feedstock


text:
@conda-forge-admin please update version

Additional comment:
No response

Hi @bollwyvl, could you please re-trigger the version update? The release has been fixed and uploaded, now: https://pypi.org/project/pyodide-build/0.29.0/

Also, would it be alright if Hood, Gyeongjae, and I could join you as recipe maintainers for this feedstock?

Of course! :rocket: :unicorn:
I'll do a manual PR once the PyPI sdist is up, and for the forms to be observed, would probably need comments by the interested parties there to confirm the change.

This version is updated. Still awaiting additional issues/PRs for maintainers.

source: gharchive/issue

authors: agriyakhetarpal bollwyvl

repo: conda-forge/pyodide-build-feedstock


text:
move to gcc7

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/python-app @minrk I'm not sure if this PR does the job properly, but the goal was to add python.app to the gcc7 channel so that gcc7 recipes can pick it up properly from conda-forge (and not from defaults).

Thanks! This disables the main channel builds, which I think might not be desirable, though a new non-gcc7 build is perhaps unlikely before finishing the migration.

Maybe it would be better for python.app to be an extra output of the python feedstock itself with an exact dependency on the python it's built with?

ok, I see the point! I can add
channel_targets:
- conda-forge gcc7 main

is this what you meant?

Maybe it would be better for python.app to be an extra output of the python feedstock itself with an exact dependency on the python it's built with?

AFAIU I think this would be optimal, although I have never dealt with multiple package outputs up to now so I'm not sure where to start from (probably I would need a good example recipe)

@minrk shall we add the main channel or are we good with this?

I think there still should be two builds per python, one for the main channel and another for gcc7

@minrk ok, but I'm not sure how to add the main channel to the build matrix. Can you help me? It seems like this:
channel_targets:
  - conda-forge gcc7
  - conda-forge main

does not have the intended effect.

The two builds are tied to the compilers. It might be simplest to add a C compiler as a build dependency even though it's unused, instead of using conda_build_config.yaml:
requirements:
  build:
    - {{ compiler('c') }}
  host:
  ...

@conda-forge/python-app should be good to go!

@cpbotha @ChrisBarker-NOAA can you please merge if you agree with these changes?

Thanks

Happy to help!

authors: carlodri conda-forge-linter mariusvniekerk minrk


text:
add qt6 to abi_migration_branches

I don't fully understand why main=5 and qt6 has a separate branch[^1], but in any case, in order to facilitate the long-term transition from 5->6, we need to keep rebuilding qt6 for various abi migrations. The bot gets this info from the main branch, hence this PR.
[^1]: rather than main being on the newest version and previous LTS versions getting their own branch

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter h-vetinari

repo: conda-forge/qt-main-feedstock


text:
Drop --without-internal-tzcode on OSX

This PR implements similar changes to #291 (done in 4.2 branch).
Will wait a bit to see that the new 4.2 builds are working before proposing this for review.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin please rerender

@conda-forge-admin please rerender

repo: conda-forge/r-base-feedstock


text:
Update bookdown to 0.9

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

authors: conda-forge-linter philip-khor

repo: conda-forge/r-bookdown-feedstock


text:
Bump build.

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: cbrueffer conda-forge-linter

repo: conda-forge/r-ggsci-feedstock


text:
MNT: Re-rendered with conda-smithy 3.1.12 and pinning 2018.10.16

R 3.5.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

repo: conda-forge/r-mvoutlier-feedstock


text:
Update recipe

Checklist

[x] Used a personal fork of the feedstock to propose changes

[x] Bumped the build number (if the version is unchanged)

[ ] Reset the build number to 0 (if the version changed)

[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)

[x] Ensured the license file is being packaged.

I already rerendered locally

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-linter jdblischak

repo: conda-forge/r-rtensor-feedstock


text:
R3.5

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (@conda-forge-admin, please rerender)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Using toolchain directly in this manner is deprecated.  Consider using the compilers outlined here.

Hi! This is the friendly automated conda-forge-webservice.
I tried to re-render for you, but it looks like there was nothing to do.

repo: conda-forge/r-wrassp-feedstock


text:
test import of cobra

which is an indirect requirement of rptools

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi @bernt-matthias ,
A new version of rpbasicdesign is released 1.1.1 where the bug was fixed. I also added the cobra import test to the recipe: https://github.com/conda-forge/rpbasicdesign-feedstock/pull/11
Thank you !

repo: conda-forge/rpbasicdesign-feedstock


text:
meta: bump dependency ranges

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Fixes https://github.com/iterative/scmrepo/issues/285

@conda-forge-admin, please rerender

repo: conda-forge/scmrepo-feedstock


text:
MNT: Re-render the feedstock [ci skip]

Hi! This is the friendly conda-forge-admin automated user.
I've re-rendered this feedstock with the latest version of conda-smithy (1.6.1) and noticed some changes.
If the changes look good, then please go ahead and merge this PR.
If you have any questions about the changes though, please feel free to ping the 'conda-forge/core' team (using the @ notation in a comment).
Remember, for any changes to the recipe you would normally need to increment the version or the build number of the package.
Since this is an infrastructural change, we don't actually need/want a new version to be uploaded to anaconda.org/conda-forge, so the version and build/number are left unchanged and the CI has been skipped.
Thanks!

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

authors: conda-forge-admin conda-forge-linter

repo: conda-forge/scp-feedstock


text:
V2.0.0

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Had to change build.sh to build with conda-build 3.16 to make it work. Similar to conda-forge/terraform-feedstock@c40c1a2

authors: agcopenhaver conda-forge-linter


text:
add chrisjsewell as maintainer

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin , please rerender

authors: conda-forge-linter ltalirz

repo: conda-forge/topika-feedstock


text:
Allow verification_merchant_account_id to be passed in directly

To ceate/update credit card

:+1: Just had the one question.

Merged #25

authors: arvanasse dougperez

repo: conduit/conduit-braintree

license: mit

license_source: bigquery


text:
Think of a good way to integrate RVPS into KBS

Now KBS integrates AS as a mod. However, inside AS the evaluation logic will request RVPS for digests.
As the design, RVPS now provide two basic APIs

API to input provenance
API to retrieve reference values

This makes RVPS have to monopolize a thread to process input and retrieve requests concurrently and continuously. Thus there might be two designs

Everytime a AttestationService object is created, an rvps inside will spawn an tokio green thread to process input and retrieve and shutdown requests ( shutdown triggered by the drop of the AttestationService object). This way works like spawn a go routine in golang. In this way the outcaller of AttestationService should specify an extra port to listen to receive input requests, which actually inner RVPS uses.
RVPS runs as a single binary, and AS will connect RVPS using grpc or something else.  In this way when we create an AS object, we need to specify the remote address of RVPS.

Way 1: There are only one binary running. However the rvps and AS' caller will share a same process but different green thread, when the rvps crashes the AS module together with caller like KBS will crash. Also it seems somehow weird.
Way 2: Although it will bring extra running binaries, we can provide a docker-compose to help user to quickly set-up a KBS + RVPS micro service.
I'm not sure which one is better although a litter agree with way 2, or we impl both of them, and add a switch in KBS:

If the rvps' remote addr is specified, use way 2
If listen to a local addr, use way 1

The two design should be

AS wraps input API, and let the caller of AS deal with the input api. The input and retrieve can be isolated by a rwlock.
Run a separate binary of RVPS, and let as to connect.


text:
Exit abnormally when sending message

Description
I installed kafka under Windows, but kafka will exit abnormally, and my program will terminate abnormally when sending a message to kafka during running. How can I determine whether kafka is connected normally
Description: The process was terminated due to an unhandled exception. Exception Info: Confluent.Kafka.ProduceException2[System.String,System.Object]: Local: Message timed out at Confluent.Kafka.Producer2.ProduceAsync(TopicPartition topicPartition, Message2 message, CancellationToken cancellationToken) at ImportPIVASData.Kafka.KafkaProducer.SendAsync(String Topic, String Key, String Value) in D:\work\projects\ImportPIVASData\ImportPIVASData\Kafka\KafkaProducer.cs:line 62 at System.Threading.Tasks.Task.<>c.<ThrowAsync>b__139_1(Object state) at System.Threading.QueueUserWorkItemCallback.<>c.<.cctor>b__6_0(QueueUserWorkItemCallback quwi) at System.Threading.ExecutionContext.RunForThreadPoolUnsafe[TState](ExecutionContext executionContext, Action1 callback, TState& state) at System.Threading.QueueUserWorkItemCallback.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch()
How to reproduce
Checklist
Please provide the following information:

[ ] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[ ] Confluent.Kafka nuget version.
[ ] Apache Kafka version.
[ ] Client configuration.
[ ] Operating system.
[ ] Provide logs (with "debug" : "..." as necessary in configuration).
[ ] Provide broker log excerpts.
[ ] Critical issue.

You can set the debug config property to "all" to get verbose logging. it might be an issue related to needing to set advertised listeners. note that there are a number of issues running Kafka on Windows and it is not supported. Maybe following the instructions here will get you set up correctly: https://www.confluent.io/blog/set-up-and-run-kafka-on-windows-linux-wsl-2/

authors: easyboot mhowlett

repo: confluentinc/confluent-kafka-dotnet


text:
The roles are quite not really usable like this

It would require a lot of effort for using these roles.
It would be better to have a single role with some subroles.
eg: cp-ansible/tasks/zookeeper/main.yml
kafka-broker/main.yml
Along with something like confluent_role: ["zookeeper", "kafka-broker"] that will include the correct tasks

We choose to use the ansible built-in role functionality versus creating subroles at this time.

authors: cotedm vfoucault

repo: confluentinc/cp-ansible


text:
Merge confluent

What changes were proposed in this pull request?

Upgraded Kafka, Zookeeper and Schema Registry
Ensured ingress compatibility with K8S 1.22+.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: Keyvan Hedayati:x: K1Hyve:x: blootsvoetsKeyvan Hedayati seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant blootsvoets

repo: confluentinc/cp-helm-charts


text:
Integrate Keep3r jobs

Problem
What problem are we solving and why does it matter, ser?
Keep3r has an interesting system where you can pay for keeper jobs through staking tokens rather than paying directly for executions.
Proposed Solution
Thoughts on solution design. We should do  to solve this problem.

[ ] Implement Keep3r jobs: https://keep3r-network-v2-gu2ybr7cp-yunoek.vercel.app/docs/tutorials/create-a-job-step-by-step
[ ] Implement offchain scripts: https://github.com/defi-wonderland/phuture-keeper-scripts/blob/main/src/deposit-manager-job.ts
[ ] Stake K3PR LP to generate credits.

Acceptance Criteria
From an end tester and/or user perspective, the below criteria must be met to consider this done:

[ ] processFromRoot and propagate go through Keep3r network.

Need to make more contract changes. Will have it ready to test on testnet today.

Working on testing on Goerli with DeFi Wonderland.

Deployed new RelayerProxyHub to Goerli and Mainnet. Working on getting keepers up on testnet. Created task #3878 to make our lighthouse a backup.

Keepers already sending transactions on testnet, mainnet, and staging. Next step: Get lighthouse working as backup, merge branch to all environments.

https://goerli.etherscan.io/tx/0xeac02665fac923a1919056eed2e96030b05b19c26875e9ccff9aa21e5f9e7402
Propagate via Keep3r is not working for some domains.

I believe that is due to encoded data. It should be bytes32!

Propagate via LH + gelato works properly after ZkSync L2TxCost issue fixed

https://goerli.etherscan.io/tx/0xeac02665fac923a1919056eed2e96030b05b19c26875e9ccff9aa21e5f9e7402
Propagate via Keep3r is not working for some domains.

I believe that is due to encoded data. It should be bytes32!

We're using this script: https://github.com/connext/connext-keeper-scripts
Can you help debug?

Complexity: 3
See the discussion in Backlog Prio 1
Powered by Parabol

authors: alexwhte liu-zhipeng rhlsthrm

repo: connext/monorepo

license: MIT


text:
add Dragon Coin

团队背景：
在当前线下交易场景中，加密货币并没有被广泛使用。随着加密货币的用途和理念日益普及，相信在不久的将来，加密货币也会融入到我们的日常生活与消费中。每年，在消费者和商家之间产生的消费规模预计达22万亿美元；人们用当地货币支付所有的消费，从每天早上的一杯咖啡到每周的购物。Dragon Coin基金会正在推动商家全面接受加密货币。通过利用现有的全球商业生态系统，Dragon Coin将会大大加速加密货币的大众化过程。
Dragon Coin全球支付将要实现的是创造一个全球通用并且可以代替传统银行的业务。通过使用Dragon Coin，您可以安全的存储资金，并随时随地用任何货币进行交易，包括加密币。所有的操作都可以通过您的智能手机上安装的Dragon Coin应用程序完成。Dragon Coin创建的数字钱包，可以代替传统的VISA卡模式，使您能够在世界任何地方，用任何类型的货币完成付款交易。
项目基本情况:
Dragon coin是一个专注于支付、信贷金融行业商业应用底层的公有链项目，是一个通用的去中心化的金融信息平台，也是新一代的基于区块链的互联网金融平台。前期基于以太坊Ethereum智能合约搭建,后期上线主网,完善自己的公有链生态体系;Dragon coin通过区块链技术来实现独立分散式多数字货币全球支付，付款，汇率、信贷等金融业务，我们希望通过Dragon Coin来连接真实商业世界和数字世界，将不同的业务和场景通过技术连接在一起，实现高效协作。
更多关于Dragon coin的信息
官网: http://dragoncoin.link/
博客: http://blog.sina.com.cn/u/6720951612
Telegram: https://t.me/Dragon_Coin
Twitter: https://twitter.com/DCoin1969
建议 gas limit: 60000

已经在1.0添加你的代币DC(Dragon)，请搜索添加测试，另外由于以太坊代币种类多，添加代币工作量大，同时为了避免误导部分 imToken 用户，我们暂时只添加社区内相对流行（有交易所收录，比如币安）的代币 logo 。但是我们暂时不添加贵团队的代币 logo 完全不影响代币的转账，只要贵方的代币是基于以太坊的 ERC 20标准代币，imToken 都是支持的。

authors: ogt-redknie wenyanwang

repo: consenlabs/token-profile


text:
update 0x1b30a0e0aa128aab4d25993a8c1353681c205e0a token

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项

[x] logo 尺寸：120*120 px
[x] logo 背景：透明
[x] 代币有至少一笔成功的转账记录
[x] 此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
[x] .json 和 .png 文件名一致（包括大小写）

项目资料：
官方公告：
团队背景：
项目基本情况：
媒体报道：
收录的交易所：
转账所需 Gas Limit（对 ERC-20 项目方）：（默认为 60000）

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists

[ ] logo dimensions: 120*120 px
[ ] logo background: Transparent
[ ] At least one transaction on the token contract
[ ] For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
[ ] Same document name for both .json and .png (Including capitalization)

Project background:
Official announcement:
Project team background:
Project basic information:
Media publications:
Tradeable exchanges:
Recommended Gas Limit (For ERC-20 project teams) for transaction: (Default is 60,000)

请检查合约checksum格式

非常抱歉，由于该PR长时间未更新，我们先关闭这个PR
如果仍需提交，请参考教程重新提交：
https://github.com/consenlabs/token-profile#token-profile-guideline


text:
Fix tests

Temporarily fixing test cases.

We'll need to address this duplications. Merging now to unblock the downstream PR.

authors: cryptoAtwill maciejwitowski

repo: consensus-shipyard/ipc


text:
Error when multiple paths are passed with --all

Previously, gb vendor --all a b would just delete all vendored
packages.
Closes #646

Hello,
I've fixed the build for the testing/testmain changes in Go 1.8, #657. Please rebase your change and push again.
Sorry for the delay, I've recently changed jobs.
Thanks
Dave

authors: davecheney nubunto

repo: constabulary/gb


text:
README / User Guide

Write this ASAP
Readme

What is construct?
Core concepts
Installation

Guide

API usage
Default Actions
Configuration
Plugins
Templates
Link to CLI Documentation

Setup docs with Github Pages for each Construct repo. Now I've got to actually write the darn docs

Wrote some preliminary documentation. Requires a lot more work.
Going to circle back in the next week or so after considering how to present the Construct API and general usage more clearly.

Documentation is back at a clean slate after rewriting the core.

repo: construct-org/construct


text:
🛑 anomouresbingo.partouze-cagoule.fr is down

In fa2b012, anomouresbingo.partouze-cagoule.fr (https://anomouresbingo.partouze-cagoule.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: anomouresbingo.partouze-cagoule.fr is back up in 4b11d83.

Resolved: anomouresbingo.partouze-cagoule.fr is back up in 55d8fc4.

repo: constructions-incongrues/status


text:
🛑 partouze-cagoule.fr is down

In e20a467, partouze-cagoule.fr (https://partouze-cagoule.fr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: partouze-cagoule.fr is back up in 005b63d.


text:
🛑 thisisradioclash.org is down

In 6973761, thisisradioclash.org (https://thisisradioclash.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: thisisradioclash.org is back up in a70cafa.


text:
🛑 lagrandepurge.resterdigne.net is down

In 2ffe680, lagrandepurge.resterdigne.net (https://lagrandepurge.resterdigne.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: lagrandepurge.resterdigne.net is back up in e611eec after 5 minutes.


text:
🛑 chattedechevre.partouze-cagoule.fr is down

In a77192f, chattedechevre.partouze-cagoule.fr (https://chattedechevre.partouze-cagoule.fr) was down:

HTTP code: 502
Response time: 347 ms

Resolved: chattedechevre.partouze-cagoule.fr is back up in 458e82e after 1 hour, 46 minutes.


text:
🛑 tiragesingrats.millemilliards.net is down

In cb3c7f9, tiragesingrats.millemilliards.net (https://tiragesingrats.millemilliards.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: tiragesingrats.millemilliards.net is back up in a20c003.


text:
DeprecationWarning: The loop argument is deprecated since Python 3.8

$proxybroker find --types https --lvl High -l 10
/home/user/.local/lib/python3.9/site-packages/proxybroker/cli.py:380: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
  proxies = asyncio.Queue(loop=loop)
/usr/lib/python3.9/asyncio/queues.py:48: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
  self._finished = locks.Event(loop=loop)
/home/user/.local/lib/python3.9/site-packages/proxybroker/api.py:97: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
  self._on_check = asyncio.Queue(maxsize=max_conn, loop=self._loop)
/usr/lib/python3/dist-packages/aiohttp/connector.py:964: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
  hosts = await asyncio.shield(self._resolve_host(
/usr/lib/python3/dist-packages/aiohttp/locks.py:21: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10.
  self._event = asyncio.Event(loop=loop)
/usr/lib/python3.9/asyncio/trsock.py:20: DeprecationWarning: Using send() method on sockets returned from get_extra_info('socket') will be prohibited in asyncio 3.9. Please report your use case to bugs.python.org.
  warnings.warn(
DeprecationWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3.9/asyncio/trsock.py:20: DeprecationWarning: Using recv() method on sockets returned from get_extra_info('socket') will be prohibited in asyncio 3.9. Please report your use case to bugs.python.org.
  warnings.warn(
DeprecationWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/python3.9/asyncio/trsock.py:20: DeprecationWarning: Using close() method on sockets returned from get_extra_info('socket') will be prohibited in asyncio 3.9. Please report your use case to bugs.python.org.
  warnings.warn(
DeprecationWarning: Enable tracemalloc to get the object allocation traceback

<Proxy RO 0.11s [HTTPS] 84.247.51.123:3128>
proxies*9```

I was also getting some other errors on Python 3.8. It would still collect proxies but it would never finish and always crash. I reverted to using Python 3.7 and all warnings/errors gone

Python 3.9
The same errors

same on 3.8.10

I got this as well. I agree with taewookim. This repo doesn't appear to be maintained.

As this project is not maintained by the original developer, we've forked ProxyBroker and continued maintaining the proxybroker2 project since 2020.

https://github.com/bluet/proxybroker2
https://github.com/constverum/ProxyBroker/pull/161

If anyone's interested, please join. We need more volunteers. :-)

authors: Bazili028 ResistOrRegret adigeefe bluet taewookim vesper8

repo: constverum/ProxyBroker


text:
Give better error for missing arches in base image

OSBS-7971

Signed-off-by: Adam Cmiel acmiel@redhat.com
Maintainers will complete the following section:

[x] Commit messages are descriptive enough
[x] "Signed-off-by:" line is present in each commit
[x] Code coverage from testing does not decrease and new code is covered
[x] JSON/YAML configuration changes are updated in the relevant schema
[x] Changes to metadata also update the documentation for the metadata
[x] Pull request includes link to an osbs-docs PR for user documentation updates
[x] New feature can be disabled from a configuration file

no release notes needed, minor change only

authors: MartinBasti chmeliik

repo: containerbuildsystem/atomic-reactor


text:
Refactor test.sh

Best reviewed one commit at a time. See messages therein.
Maintainers will complete the following section

[ ] Commit messages are descriptive enough
[ ] Code coverage from testing does not decrease and new code is covered
[ ] JSON/YAML configuration changes are updated in the relevant schema
[ ] Changes to metadata also update the documentation for the metadata
[ ] Pull request has a link to an osbs-docs PR for user documentation updates
[ ] New feature can be disabled from a configuration file

/packit build


text:
Bump OpenTelemetry contrib to v0.36.4

Bumps go.opentelemetry.io/contrib missed in https://github.com/containerd/containerd/pull/7660

/ok-to-test

authors: lucacome samuelkarp

repo: containerd/containerd


text:
fix(shim): rewrite cgroups v2 parsing logic

this commit rewrites the cgroups v2 parsing logic in get_cgroup function which is used to fetch stats of a container. The reason for the rewrite was that in some cases the original logic would panic due to index of bound for parsing paths like
0::/kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice:cri-containerd:278a0aac1fff30dfbc41b4a32ba9de4519928fe7480213dba87aa1498838ef34
we ran into this issue in deleting a spin container in the spin shim.
the rewrite replaces index access to properly propogate the error to the caller of the function and added a few unit tests for the parsing logic.
see more discussion https://github.com/spinkube/containerd-shim-spin/issues/39, https://github.com/containerd/runwasi/issues/418

The cgroups v2 parsing logic is inspired by https://github.com/opencontainers/runc/blob/1950892f69597aa844cbf000fbdf77610dda3a44/libcontainer/cgroups/fs2/defaultpath.go#L83
but there is a critical difference:
The runc cgroups parsing logic will actually fail to parse
0::/kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice:cri-containerd:278a0aac1fff30dfbc41b4a32ba9de4519928fe7480213dba87aa1498838ef34
because it does not take the whole path splitted by the colons. The runc parsing logic would only get kubepods-besteffort-pod162385e5_7f69_4c38_ba9c_db0a8f02b35e.slice which is not the actual cgroups path.
I was not sure if this is a bug in runc, or a bug on how spin container's cgroups path was constructed in the first place.

Couple of questions:

Is the path with colons like that valid?
What is generating the path with colons and should this be fixed in the code generating the path to be more idiomatic?

I can validate that with this patch, what we are seeing in https://github.com/spinkube/containerd-shim-spin/issues/39 is now fixed.

Is the path with colons like that valid?

I think runc with Go impl can actually handle path with colons. So it should be valid.

What is generating the path with colons and should this be fixed in the code generating the path to be more idiomatic?

Maybe youki's libcgroups? I am not entirely sure

Could you please take a look, @mxpv 🙏?

Frankly speaking (in longer term) I think we should not carry groups related code in the shim crate. shim crate supposed to be the foundation for building new shim runtimes for containers, without carrying any implementation details.

I think there are two pending issues which are not resolved by this PR where I made an issue for each

authors: Mossaka jsturtevant mxpv radu-matei

repo: containerd/rust-extensions


text:
provide conmon documentation

Description
Currently this is very little to none documentation available on conmon and what it actually does.
There are some vague statements at https://cri-o.io/ for example, such as "Each container is monitored by a separate conmon process. The conmon process holds the pty of the PID1 of the container process. It handles logging for the container and records the exit code for the container process."
This doesn't make it clear on what function it actually does.
To avoid confusion it would be helpful if there was some documentation available on it's function and what it means that "each container is monitored by a separate conmon process" for example. Can conmon take any action if it detects some error with the container?
What does "handles logging" mean?
The architecture image on https://cri-o.io/ is a good starting point but perhaps it can be better described what it then integrates with, when I quickly look through the code I can see journald for example being used.
This type of integration would be good to have documented so that I can better understand what it does.

We haven't added much documentation on Conmon because we treat it purely as an implementation detail; no one should be using Conmon except for Podman and CRI-O, and we don't even put it in the system's default $PATH as such.
In brief, Conmon is an extremely small C program with almost no memory footprint that wraps the OCI runtime (usually runc) that runs the actual container. Upon being launched by Podman, it double-forks to daemonize and detach from the parent that launched it, then launches the OCI runtime as its child. It will live for as long as the runtime (and container) live, and when the container dies it records its exit time and exit code for Podman or CRI-O. While the container is alive, Conmon provides a socket for attaching to the container, holding open the container's standard streams and forwarding them over the socket (and also writes the contents of the container's streams to a log file so podman logs and CRI-O can read them). And that's about it.
In short, it's an extremely minimal C binary that manages containers so that Podman processes can die in the foreground and the container will still be under our supervision, available to be attached to and recording exit information when it dies. Each container has a single Conmon process that acts as its parent until the container dies, and each Conmon process manages a single container.

A further note: "can conmon take any action if it detects some error with the container?"
No. Conmon is extremely minimal, and doesn't have the logic to detect or handle errors. If we wanted to add such logic, we'd do it in Podman and CRI-O, to keep Conmon simple and its memory footprint minimal.

@mheon What you wrote above should probably be added to the conmon readme. :^)

I agree. I asked @opuk on IRC to open the issue here.
Although conmon does not do much, the more curious users (and devs) are currently having a hard time finding out what conmon does. For some, it might seem suspicious that some additional but undocumented binary is installed.

We should also create a man page for it.

do folks agree this should be moved to the conmon repo?

Actually conmon has documentation now at github.com/containers/conmon. Closing this issue as such, reopen over there if you disagree

authors: baude haircommander mheon opuk rhatdan vrothberg

repo: containers/libpod


text:
Uses/requires CNI for slirp4ns

/kind bug
Description
When running podman in root mode, it requires/uses CNI to build slirp4ns networks.  In rootless mode with same parameters, CNI is not used.
CNI is problematic because it messes around with iptables directly which breaks when they are managed externally.  For this, I need a pure userspace solution (more or less like dockerd --iptables=false) like slirp4ns.

Steps to reproduce the issue:

rm -rf /etc/cni/net.d  (or keep it and use podman inspect later to see whether CNI is used)

run as root:
podman run -it --network=slirp4ns fedora:31

run as user:
podman run -it --network=slirp4ns fedora:31

Describe the results you received:
Step 2 fails with
ERRO[0000] CNI network "slirp4ns" not found

Step 3 succeeds.
Describe the results you expected:
Step 2 succeeds and CNI is not used.
Output of podman version:
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.1
  podman version: 1.6.2
host:
  BuildahVersion: 1.11.3
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.2-1.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.2, commit: 186a550ba0866ce799d74006dab97969a2107979'
  Distribution:
    distribution: fedora
    version: "31"
  MemFree: 2040983552
  MemTotal: 32669814784
  OCIRuntime:
    name: crun
    package: crun-0.10.6-1.fc31.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.10.6
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree: 4177784832
  SwapTotal: 4294963200
  arch: amd64
  cpus: 8
  eventlogger: journald
  hostname: ensc-virt.intern.sigma-chemnitz.de
  kernel: 5.3.15-300.fc31.x86_64
  os: linux
  rootless: false
  uptime: 26h 4m 9.38s (Approximately 1.08 days)
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 26
  GraphDriverName: overlay
  GraphOptions:
    overlay.mountopt: nodev,metacopy=on
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  ImageStore:
    number: 35
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.6.2-2.fc31.x86_64

I think it's slirp4netns not slirp4ns - this seems to assume that you're naming a specific network to join the container to, not the slirp4netns network mode.

a sorry; played around too much with these parameters to find a solution.  It happens for slirp4netns too:
# podman run -it --network=slirp4netns fedora:31
Error: error configuring network namespace for container 333904201fd754e3ad250b20375637d729d8c57671737aa4bbe5509fc209e3d1: Missing CNI default network

or (when CNI networks are defined), the TAP interfaceis attached to the CNI bridge:
# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.5efd27246f02       no              veth51c30c92
                                                        vethc52bca13

# podman run -it --network=slirp4netns fedora:31

and in another shell
# brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.5efd27246f02       no              veth1b744da0
                                                        veth51c30c92
                                                        vethc52bca13

Ack, that definitely sounds like a bug in how we're configuring slirp as root.

To demonstrate the real problem:

Create a minimal CNI setup which does not touch the iptables
{
    "cniVersion": "0.4.0",
    "name": "podman",
    "plugins": [
        {
            "type": "bridge",
            "bridge": "br0",
            "isGateway": false,
            "ipMasq": false,
            "ipam": {
                "type": "host-local",
                "routes": [
                    {
                        "dst": "0.0.0.0/0"
                    }
                ],
                "ranges": [
                    [
                        {
                            "subnet": "10.1.0.0/24",
                            "gateway": "10.1.0.1"
                        }
                    ]
                ]
            }
        }
    ]
}

(clear nat table)

Run as root
podman run --rm --publish=10000:10000  -it  --network=slirp4netns

Execute in the container
nc -l -p 10000

Monitor network traffic on the host in the background
# tcpdump -i enp0s31f6 -nnn -s0 port 10000

Connect from the outside to port 10000 and send some data
$ telnet my-host 10000
abc

Close connection, reconnect and play around a little bit

Output in step 5 shows the expected
17:41:36.869048 IP 192.168.0.132.43516 > 192.168.3.24.10000: Flags [SEW], seq 1272706154
17:41:36.869104 IP 192.168.3.24.10000 > 192.168.0.132.43516: Flags [S.E], seq 1468818041, ack 1272706155
17:41:36.869316 IP 192.168.0.132.43516 > 192.168.3.24.10000: Flags [.], ack 1

17:41:41.596255 IP 192.168.0.132.43516 > 192.168.3.24.10000: Flags [P.], seq 1:6, ack 1
17:41:41.596307 IP 192.168.3.24.10000 > 192.168.0.132.43516: Flags [.], ack 6

But sometimes the internal private IP appears:
17:41:42.094191 IP 192.168.0.132.43516 > 192.168.3.24.10000: Flags [P.], seq 6:7, ack 1
17:41:42.094225 IP 192.168.3.24.10000 > 192.168.0.132.43516: Flags [.], ack 7
17:41:42.094336 IP 10.0.2.100.10000 > 192.168.0.132.43516: Flags [.], ack 2
17:41:46.256096 IP 10.0.2.100.10000 > 192.168.0.132.43516: Flags [.], ack 2

@AkihiroSuda Could you comment on this?

Why are you trying to run slirp4netns as root?

I don't think this is a problem with Slirp itself - it sounds like we're not properly respecting the requested slirp4netns setting and applying CNI as well. A lot of networking code is written with the implicit assumption that root=CNI, rootless=slirp - I bet that's where this slipped in.

@ensc Can you possibly test #4853 and verify that it resolves the problem?

authors: AkihiroSuda ensc mheon rhatdan


text:
exec: fix --preserve-fds

There were two problems with preserve fds.
libpod didn't open the fds before passing _OCI*PIPE to conmon. This caused libpod to talk on the preserved fds, rather than the pipes, with conmon talking on the pipes. This caused a hang.
Libpod also didn't convert an int to string correctly, so it would further fail.
Fix these and add a unit test to make sure we don't regress in the future
fixes: https://github.com/containers/libpod/issues/4020
Signed-off-by: Peter Hunt pehunt@redhat.com

Targetting for 1.6.0 final
/approve

nice work @haircommander   LGTM

LGTM

/lgtm
/hold
hold cancel when tests pass.

LGTM assuming happy tests

@haircommander Your new test seems to be failing

crun apparently doesn't support --preserve-fds. Just working on writing a test now...

Yes, @giuseppe,  we definitely need this fixed for F31.

@rhatdan @mheon @baude @jwhonce @QiWang19 @TomSweeneyRedHat happy green tests

I don't know how that happened but I'm not asking questions.
/lgtm

/hold cancel

authors: TomSweeneyRedHat baude haircommander mheon rhatdan


text:
Combine GlobalFlags and EngineFlags into EngineOptions

EngineOptions obtained in command via
opts, err := registry.Options(cmd)

Signed-off-by: Jhon Honce jhonce@redhat.com

LGTM other than the name discussion.

@jwhonce Needs rebase.

/lgtm

authors: TomSweeneyRedHat baude jwhonce rhatdan


text:
Correct dev version

Should have been v1.3.1-dev
Signed-off-by: Brent Baude bbaude@redhat.com

/lgtm

authors: baude mheon

repo: containers/netavark


text:
Bump to 0.0.3

Update the changelog
Signed-off-by: Daniel J Walsh dwalsh@redhat.com

@4383 Ok, I pushed the tag on master and published the release.  Is everything ok now?

@rhatdan nice! it's ok now.
https://pypi.org/project/podman/0.0.3/

@rhatdan Another interesting way to manage ChangeLog in the next release could be to use reno to obtain a more focused and beautiful changelog instead of only list commits.
https://pypi.org/project/reno/
Reno is compatible with pbr too.
Thoughts?

You would know far better then me.  I am no PYPI expert.

The advantages to use reno is to split ChangeLog by items like:

features
fixes
etc...

@rhatdan I'll measure the needed works to introduce that in python-podman

repo: containers/python-podman


text:
Allow API to bind to IP, rather than all interfaces

Allowing the API to bind to all interfaces can cause interferance, and can trigger firewall issues on Macs.
It is probably a good idea to have an IP to bind to, so that integration tests can be run easier, and security can be improved in the future.

This is becoming annoying with #400.
Going to prioritize this.

repo: containous/maesh


text:
RDS Gateway MSRPC reverse proxy

Do you want to request a feature or report a bug?
A feature

What did you do?
set up Traefik using file backend and pointed it at my RDS Gateway

What did you expect to see?
RDS RPC traffic passed through to the gateway
What did you see instead?
RDS RPC traffic not passed through, making RDP over HTTPS fail
Output of traefik version: (What version of Traefik are you using?)

v1.4.0-rc5

What is your environment & configuration (arguments, toml, provider, platform, ...)?
    [backends.rds]
     [backends.rds.servers.prod]
      url = "https://rds.external.domain"
   [frontends.rds]
    backend = "rds"
    passHostHeader = true
    passTLSCert = true
      [frontends.rds.routes.prod]
      rule = "Host: rds.external.domain"

@RoeeJ It appears that you are listening on rds.external.domain and forwarding to rds.external.domain. Is that your intent?
Also, when you say traffic is not passed through, can you elaborate? Do requests get logged by traefik?
Can you view the debug logs to verify?
Thanks!

@RoeeJ just for information - why in the world you need to do this? You can just put IIS directly to internet.

@dtomcej Hey, there are DNS mappings of the external domains to internal IPs, this was just a test as I was thinking it might be a problem with the certs not matching.
I'll check the debug logs but I think the gist of it is that RPC over HTTP isn't using the "regular" verbs (GET/POST/PUT and so on)
@zyzop Currently I only have a single public facing IP, I know I can just point it at IIS (which I did) but it doesn't do load balancing and/or has docker/rancher integration which just makes things messier.

authors: RoeeJ dtomcej zyzop

repo: containous/traefik


text:
Traefik suddenly offers SSLv3

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?
I updated from 1.7.13 to version 1.7.14 of Traefik. Then run a TLS check (https://www.ssllabs.com/ssltest/) and suddenly got a rating downgrade from A+ of B.

What did you expect to see?
I expected to see my original A+ rating to continue to be A+ due to secure defaults.

What did you see instead?
Rating went down from A+ to B because Traefik suddenly starts to support SSLv3.

Output of traefik version: (What version of Traefik are you using?)

$ docker run --rm traefik:v1.7.14 version
Version:      v1.7.14
Codename:     maroilles
Go version:   go1.12.8
Built:        2019-08-14_09:46:58AM
OS/Arch:      linux/amd64

$ docker run --rm traefik:v1.7.13 version
Version:      v1.7.13
Codename:     maroilles
Go version:   go1.11.12
Built:        2019-08-08_04:46:14PM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
version: '2'
services:
  proxy:
    image: traefik:v1.7.14
    cpu_shares: 3072
    mem_limit: 256mb
    memswap_limit: 512mb
    read_only: true
    depends_on:
      - dockersocket
    security_opt:
      - label=level:s0:c100

    ports:
    - "80:80"
    - "443:443"

    volumes:
    - "/var/srv/traefik/acme:/etc/traefik/acme"

    command: "-c /dev/null --docker --docker.endpoint=tcp://dockersocket:2375 --acme --acme.email=<redacted> --acme.storage=/etc/traefik/acme/acme.json --acme.entryPoint=https --acme.onhostrule --acme.dnsprovider=cloudflare --acme.dnschallenge --entryPoints='Name:http Address::80 Redirect.EntryPoint:https' --entryPoints='Name:https Address::443 Compress:true TLS' --defaultentrypoints=http,https --docker.exposedbydefault=false --insecureskipverify=true"

I don't use an additional toml file for configuration.
I have an idea where it might comes from:
https://github.com/containous/traefik/commit/989a59cc29f58e25c07dab2eab97f0f683cef5ab
At least this seems to be the latest change to the TLS code which might lead to autodetected SSLv3 support? As there is a cipher overlap between TLS1.0 and SSLv3 around TLS_RSA_WITH_AES_128_CBC_SHA, TLS_RSA_WITH_AES_256_CBC_SHA and TLS_RSA_WITH_3DES_EDE_CBC_SHA.
Additional hint: I verified that just by changing the image version back to 1.7.13 the rating went back to A+ and SSLv3 was disabled.

Note that the constants in question are detailed in:
https://golang.org/pkg/crypto/tls/#pkg-constants
But more of note:
https://golang.org/doc/go1.13#crypto/tls
SSLv3 was always disabled by default, other than in Go 1.12, when it was mistakenly enabled by default server-side. It is now again disabled by default. (SSLv3 was never supported client-side.)

😢
and the fix:
https://github.com/golang/go/issues/33837

Thanks @SISheogorath for this report, we will work on getting this resolved ASAP.

In the meanwhile I was able to help myself with this patch:
https://git.shivering-isles.com/shivering-isles/infrastructure/commit/624f7809af6e86152e82694811970e2e655fa5e1
(Adding TLS.minVersion:VersionTLS10)

Cool. That was essentially what I was going to suggest you try, and was going to be my avenue for a patch.
Good to know that it will work.

authors: SISheogorath dtomcej


text:
Refs 2669: add/modify descriptions for operations

Summary
We are adding the missing descriptions for some endpoints. Along with this, we have also reworded them with the purpose of ongoing enhancements in API docs.
Testing steps

Modified the commit message based on one check that got failed.

[test]

@swadeley does this look okay to you?

i filed a card on our board: https://issues.redhat.com/browse/HMS-2669 and updated the title to link up with that

⚠ This task currently requires qe-approval, but this PR does not fully resolve the task.  Please contact QE to determine appropriate testing required.

@swadeley addressed your views :+1:

Thank you all

authors: jlsherrill mjivraja swadeley


text:
feat: increase limits to 5000 [PHX-2946]

The CLI runs stable with the current limits, so we increase the limits by x10

@ruderngespra sorry your comment got swallowed - add is the operation with the biggest payload, and therefore the one with the highest risk. delete is the cheapest operation, and updateis a guess that it's also rather small. We could also do5000` for all - wdyt?

@ruderngespra sorry your comment got swallowed - add is the operation with the biggest payload, and therefore the one with the highest risk. delete is the cheapest operation, and update is a guess that it's also rather small. We could also do 5000 for all - wdyt?

I am fine with the current limits, I think that makes sense, we can further adjust based on customer input if needed

authors: marcolink ruderngespra

repo: contentful/contentful-merge


text:
Elements sometimes disappear in preview mode

When we open preview mode and have live preview and inspector props enabled the UI elements will sometimes disappear.
Note that in this screenshot I have selected the h1 element which is not displaying in preview. Usually after clicking, resizing, or editing a few things it will appear again:

There should also be buttons beneath the text which are also missing

Hey, thank you for the report!

UI elements will sometimes disappear.

This is going to be tricky to reproduce. Could you please submit a minimal reproducible example to help with the investigation?
Feel free to use CodeStandbox or any other similar service of your choosing.

@z0al it seems that the height of the element is set to 0 are you use a ref to calculate the element dimensions?

@z0al any updates here?

This seems resolved after updating to 2.6.0

This seems resolved after updating to 2.6.0

repo: contentful/live-preview


text:
Encountered unexpected errors while processing of 2 documents.

I am getting an error when generating documents in Contentlayer, the error is:
Error: Found 2 problems in 4 documents.
└── Encountered unexpected errors while processing of 2 documents. This is possibly a bug in Contentlayer. Please open an issue.
 • "installation/index.mdx": UnexpectedMDXError: Error: Build failed with 1 error:
 _mdx_bundler_entry_point-650ecf62-9900-471e-be1a-20b717fdcbfd.mdx:0:0: ERROR: [plugin: @mdx-js/esbuild] TypeError: Cannot read properties of undefined (reading 'inTable')
     at Object.exitCodeText (file:///workspaces/ai-api-docs/node_modules/mdast-util-gfm-table/lib/index.js:123:17)
     at compile (file:///workspaces/ai-api-docs/node_modules/mdast-util-from-markdown/lib/index.js:352:40)
     at fromMarkdown (file:///workspaces/ai-api-docs/node_modules/mdast-util-from-markdown/lib/index.js:187:29)
     at parser (file:///workspaces/ai-api-docs/node_modules/remark-parse/lib/index.js:18:12)
     at Function.parse (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:273:12)
     at executor (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:393:31)
     at new Promise (<anonymous>)
     at Function.process (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:380:14)
     at process (file:///workspaces/ai-api-docs/node_modules/@mdx-js/mdx/lib/util/create-format-aware-processors.js:50:22)
     at onload (file:///workspaces/ai-api-docs/node_modules/@mdx-js/esbuild/lib/index.js:151:22)
     at requestCallbacks.on-load (/workspaces/ai-api-docs/node_modules/esbuild/lib/main.js:1434:28)
     at processTicksAndRejections (node:internal/process/task_queues:95:5)
     at handleRequest (/workspaces/ai-api-docs/node_modules/esbuild/lib/main.js:729:13)
 • "installation/node.mdx": UnexpectedMDXError: Error: Build failed with 1 error:
 _mdx_bundler_entry_point-8fcb210e-7e8c-43a8-bddd-1d64451d8c57.mdx:0:0: ERROR: [plugin: @mdx-js/esbuild] TypeError: Cannot read properties of undefined (reading 'inTable')
     at Object.exitCodeText (file:///workspaces/ai-api-docs/node_modules/mdast-util-gfm-table/lib/index.js:123:17)
     at compile (file:///workspaces/ai-api-docs/node_modules/mdast-util-from-markdown/lib/index.js:352:40)
     at fromMarkdown (file:///workspaces/ai-api-docs/node_modules/mdast-util-from-markdown/lib/index.js:187:29)
     at parser (file:///workspaces/ai-api-docs/node_modules/remark-parse/lib/index.js:18:12)
     at Function.parse (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:273:12)
     at executor (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:393:31)
     at new Promise (<anonymous>)
     at Function.process (file:///workspaces/ai-api-docs/node_modules/unified/lib/index.js:380:14)
     at process (file:///workspaces/ai-api-docs/node_modules/@mdx-js/mdx/lib/util/create-format-aware-processors.js:50:22)
     at onload (file:///workspaces/ai-api-docs/node_modules/@mdx-js/esbuild/lib/index.js:151:22)
     at requestCallbacks.on-load (/workspaces/ai-api-docs/node_modules/esbuild/lib/main.js:1434:28)
     at processTicksAndRejections (node:internal/process/task_queues:95:5)
     at handleRequest (/workspaces/ai-api-docs/node_modules/esbuild/lib/main.js:729:13)

SourceFetchDataError: {
"_tag": "HandledFetchDataError"
}
My contentlayer.config.ts file has this code:
import path from "path"
import {
defineDocumentType,
defineNestedType,
makeSource,
} from "contentlayer/source-files"
import rehypeAutolinkHeadings from "rehype-autolink-headings"
import rehypePrettyCode, { Options } from "rehype-pretty-code" // Import the Options type from rehype-pretty-code
import rehypeSlug from "rehype-slug"
import { codeImport } from "remark-code-import"
import remarkGfm from "remark-gfm"
import { getHighlighter, loadTheme } from "shiki"
import { visit } from "unist-util-visit"
/** @type {import('contentlayer/source-files').ComputedFields} */
const computedFields: import('contentlayer/source-files').ComputedFields<"Doc"> = {
slug: {
type: "string",
resolve: (doc: any) => /${doc._raw.flattenedPath},
},
slugAsParams: {
type: "string",
resolve: (doc: any) => doc._raw.flattenedPath.split("/").slice(1).join("/"),
},
}
const LinksProperties = defineNestedType(() => ({
name: "LinksProperties",
fields: {
doc: {
type: "string",
},
api: {
type: "string",
},
},
}))
export const Doc = defineDocumentType(() => ({
name: "Doc",
filePathPattern: **/*.mdx,
contentType: "mdx",
fields: {
title: {
type: "string",
required: true,
},
description: {
type: "string",
required: true,
},
published: {
type: "boolean",
default: true,
},
links: {
type: "nested",
of: LinksProperties,
},
featured: {
type: "boolean",
default: false,
required: false,
},
component: {
type: "boolean",
default: false,
required: false,
},
toc: {
type: "boolean",
default: true,
required: false,
},
},
computedFields,
}))
export default makeSource({
contentDirPath: "./content/docs",
documentTypes: [Doc],
mdx: {
remarkPlugins: [remarkGfm, codeImport],
rehypePlugins: [
rehypeSlug,
() => (tree) => {
visit(tree, (node) => {
if (node?.type === "element" && node?.tagName === "pre") {
const [codeEl] = node.children
if (codeEl.tagName !== "code") {
return
}
        if (codeEl.data?.meta) {
          // Extract event from meta and pass it down the tree.
          const regex = /event="([^"]*)"/
          const match = codeEl.data?.meta.match(regex)
          if (match) {
            node.__event__ = match ? match[1] : null
            codeEl.data.meta = codeEl.data.meta.replace(regex, "")
          }
        }

        node.__rawString__ = codeEl.children?.[0].value
        node.__src__ = node.properties?.__src__
        node.__style__ = node.properties?.__style__
      }
    })
  },
  [
    rehypePrettyCode as any as (options?: Options) => void, // Cast rehypePrettyCode to the correct type
    {
      getHighlighter: async () => {
        const theme = await loadTheme(
          path.join(process.cwd(), "/lib/themes/dark.json")
        )
        return await getHighlighter({ theme })
      },
      onVisitLine(node: any) {
        // Prevent lines from collapsing in `display: grid` mode, and allow empty
        // lines to be copy/pasted
        if (node.children.length === 0) {
          node.children = [{ type: "text", value: " " }]
        }
      },
      onVisitHighlightedLine(node: any) {
        node.properties.className.push("line--highlighted")
      },
      onVisitHighlightedWord(node: any) {
        node.properties.className = ["word--highlighted"]
      },
    },
  ],
  () => (tree) => {
    visit(tree, (node) => {
      if (node?.type === "element" && node?.tagName === "div") {
        if (!("data-rehype-pretty-code-fragment" in node.properties)) {
          return
        }

        const preElement = node.children.at(-1)
        if (preElement.tagName !== "pre") {
          return
        }

        preElement.properties["__withMeta__"] =
          node.children.at(0).tagName === "div"
        preElement.properties["__rawString__"] = node.__rawString__

        if (node.__src__) {
          preElement.properties["__src__"] = node.__src__
        }

        if (node.__event__) {
          preElement.properties["__event__"] = node.__event__
        }

        if (node.__style__) {
          preElement.properties["__style__"] = node.__style__
        }
      }
    })
  },
  [
    rehypeAutolinkHeadings,
    {
      properties: {
        className: ["subheading-anchor"],
        ariaLabel: "Link to section",
      },
    },
  ],
],

},
})

The issue might be due to changes in the contentlayer's configuration or the addition of a new .mdx file, causing unexpected problems. I'm not sure why this is happening, but if you want to resolve it, try removing the recent changes you made. It seems to be a significant bug, as I've encountered it more than 10 times while working on my website. My suggestion would be to consider migrating to other alternatives. Despite my previous fondness for it, I'm currently in the process of switching to @next/mdx.
And Yes, It is not getting maintained actively.

authors: myselfprincee xAstralMars

repo: contentlayerdev/contentlayer


text:
Multiple Reference field update and includeReferenceContentTypeUID not working with includeReference

Hey all, just pinging here to say that I would love to take advantage of the new "multiple" options for references fields, but reference resolution doesn't seem to be working property on multiple reference fields.
Simply changing an existing reference field to allow multiple types breaks that field's resolution -- as in, resolving references with the .includeReference() method no longer works. Adding includeReferenceContentTypeUID() did not seem to have any effect on the resolution, in fact, adding that method to the chain seems to break ALL reference resolutions for that Query.
Any direction would be appreciated! Thanks,
Walt

Hi Walt-er,
We are looking into it and update you soon.
Thanks
Rohit

Hi Walt-er,
The upgradation impacts the include referencing of your existing published entries. In the case of all published entries, you need to save these entries so that your Reference field format changes to the upgraded format, and then publish these entries again. Now, the includeReference() and includeReferenceContentTypeUID() query should work for you.
Thanks

Hi Rohit, thanks for the followup. I have saved and re-published both the reference and there reference-er, but the reference inclusions is still broken. Is there anything I need to change about my Query call?
const Query = this.contentstackConnection
	.ContentType(contentType)
	.Entry(pageUid)
	.language(language)
	.includeReferenceContentTypeUID()
	.includeReference(references);

Alternatively, is there anything I now need to change about my references array? It's an array of field UIDs, i.e. ["masthead", "media_gallery"].

Hi Walt-er,
As per I understand you are trying to use include_reference under reference and reference within reference field, which is two level, currently in multiple content type reference, we have configuration for including reference which is set to 1. So you are getting only single level reference and not able to fetch reference within references.
It will be helpful if you provide your request, response and  your expected response.
Thanks

repo: contentstack/contentstack-javascript


text:
Communication between 32bit and 64bit pdocess

Hi,
Does eCAL supports communication between 32bit and 64bit process?

Hello venkatmakam,
it is one of eCALs (+ protobufs) core features to enable interprocess communication between different archtictures and therefore also between 32 and 64 bit processes. For sure you have to provide the matching eCAL library to your process.

authors: floriangeis venkatmakam

repo: continental/ecal


text:
new Buffer deprecated

In the docs we show new Buffer which I think has been deprecated.

Fixed in 7914b12934d69d1c26fdfd255b482e4c9da0dc4a.

authors: arb cjihrig

repo: continuationlabs/zipit


text:
Supporting min-p sampling setting on llama.cpp

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[x] I'm not able to find an open issue that requests the same enhancement

Problem
min-p is an alternative sampling method that is supported by llama.cpp (I believe exllama also supports it). In my experience it's both way easier and way better than any other sampling method out there.
As an example using deepseek-coder 33b in llama.cpp
Prompt: "Write the fibonacci function in Python3"
min_p 0.05
def fibonacci(n:int, memo={}) -> int:
    if n <=2 : return 1 # base case 1, 2 => 1

    if n not in memo:
        memo[n] = fibonacci(n-1, memo) + fibonacci(n-2,memo) # store the result

    return memo[n]
# Test cases
print("Test case 1")
print(f"The 5th Fibonacci is {fibonacci(5)} ")
print(f"The 9th Fibonacci is {fibonacci(9)} ")

Default sampling settings
def fibonacci(n):
  if n == 0:
      return 0
  elif n ==1:
      return 1
  else :
      return (fibonacci(n - 1) + fibonacci(n -2))
n = int(input())
print(fibonacci(n))

Solution
For more details on the sampling method itself: https://www.reddit.com/r/LocalLLaMA/comments/17vonjo/your_settings_are_probably_hurting_your_model_why/
The llama.cpp server supports min-p in a similar way to any other sampling method

@Azeirah Nice! That was a good read, learned some things and might actually change our defaults to this.
To set min-p, assuming you are using "provider": "llama.cpp" in your config.json, you can do this:
{
  "model": "deepseek-33b",
  "provider": "llama.cpp",
  "title": "Deepseek Coder",
  "llama_cpp_args": { "min-p": 0.05}
}

and we will pass the llama_cpp_args to the server like here

Though I do notice that the docs there don't list min-p, so it could be that they are just out of date, but if it doesn't work then maybe a PR is in order.
I'll also make a point to add min-p to our completion_options object

@Azeirah minP is added as an option here. It will work with the llama.cpp provider, but doesn't look like any of the others support this option

authors: Azeirah sestinj

repo: continuedev/continue