text:
test_repr_multiindex* and test_array_repr_dtypes_unix tests failing on 32-bit platforms

What happened?
When running the test suite on 32-bit platforms (e.g. x86), I'm getting the following test failures:
FAILED xarray/tests/test_dataarray.py::TestDataArray::test_repr_multiindex - ...
FAILED xarray/tests/test_dataarray.py::TestDataArray::test_repr_multiindex_long
FAILED xarray/tests/test_dataset.py::TestDataset::test_repr_multiindex - Asse...
FAILED xarray/tests/test_formatting.py::test_array_repr_dtypes_unix - Asserti...

(log below)
I think the tests assume specific object sizes for 64-bit platforms.
This is Python 3.11.9 on 32-bit x86, retested on 380979fc213b3d1f53f097bab9b61851391be729.
What did you expect to happen?
Tests passing.
Minimal Complete Verifiable Example
# on a 32-bit architecture, literally:
python -m pytest

MVCE confirmation

[ ] Minimal example — the example is as focused as reasonably possible to demonstrate the underlying issue in xarray.
[ ] Complete example — the example is self-contained, including all data and the text of any traceback.
[ ] Verifiable example — the example copy & pastes into an IPython prompt or Binder notebook, returning the result.
[X] New issue — a search of GitHub Issues suggests this is not a duplicate.
[X] Recent environment — the issue occurs with the latest version of xarray and its dependencies.

Relevant log output
=================================== FAILURES ===================================
______________________ TestDataArray.test_repr_multiindex ______________________

self = <xarray.tests.test_dataarray.TestDataArray object at 0xe9e027f0>

    def test_repr_multiindex(self) -> None:
        expected = dedent(
            """\
            <xarray.DataArray (x: 4)> Size: 32B
            array([0, 1, 2, 3], dtype=uint64)
            Coordinates:
              * x        (x) object 32B MultiIndex
              * level_1  (x) object 32B 'a' 'a' 'b' 'b'
              * level_2  (x) int64 32B 1 2 1 2"""
        )
>       assert expected == repr(self.mda)
E       AssertionError: assert '<xarray.Data...4 32B 1 2 1 2' == '<xarray.Data...4 32B 1 2 1 2'
E
E         Skipping 97 identical leading characters in diff, use -v to show
E         Skipping 43 identical trailing characters in diff, use -v to show
E         - x) object 16B MultiIndex
E         ?           ^^
E         + x) object 32B MultiIndex
E         ?           ^^...
E
E         ...Full output truncated (4 lines hidden), use '-vv' to show

/tmp/xarray/xarray/tests/test_dataarray.py:122: AssertionError
___________________ TestDataArray.test_repr_multiindex_long ____________________

self = <xarray.tests.test_dataarray.TestDataArray object at 0xe9e029d0>

    def test_repr_multiindex_long(self) -> None:
        mindex_long = pd.MultiIndex.from_product(
            [["a", "b", "c", "d"], [1, 2, 3, 4, 5, 6, 7, 8]],
            names=("level_1", "level_2"),
        )
        mda_long = DataArray(
            list(range(32)), coords={"x": mindex_long}, dims="x"
        ).astype(np.uint64)
        expected = dedent(
            """\
            <xarray.DataArray (x: 32)> Size: 256B
            array([ 0,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 12, 13, 14, 15, 16,
                   17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31],
                  dtype=uint64)
            Coordinates:
              * x        (x) object 256B MultiIndex
              * level_1  (x) object 256B 'a' 'a' 'a' 'a' 'a' 'a' ... 'd' 'd' 'd' 'd' 'd' 'd'
              * level_2  (x) int64 256B 1 2 3 4 5 6 7 8 1 2 3 4 ... 5 6 7 8 1 2 3 4 5 6 7 8"""
        )
>       assert expected == repr(mda_long)
E       AssertionError: assert '<xarray.Data...2 3 4 5 6 7 8' == '<xarray.Data...2 3 4 5 6 7 8'
E
E         Skipping 228 identical leading characters in diff, use -v to show
E         Skipping 124 identical trailing characters in diff, use -v to show
E         - x) object 128B MultiIndex
E         ?           - ^
E         + x) object 256B MultiIndex
E         ?            ^^...
E
E         ...Full output truncated (4 lines hidden), use '-vv' to show

/tmp/xarray/xarray/tests/test_dataarray.py:143: AssertionError
_______________________ TestDataset.test_repr_multiindex _______________________

self = <xarray.tests.test_dataset.TestDataset object at 0xe9d08170>

    def test_repr_multiindex(self) -> None:
        data = create_test_multiindex()
        expected = dedent(
            """\
            <xarray.Dataset> Size: 96B
            Dimensions:  (x: 4)
            Coordinates:
              * x        (x) object 32B MultiIndex
              * level_1  (x) object 32B 'a' 'a' 'b' 'b'
              * level_2  (x) int64 32B 1 2 1 2
            Data variables:
                *empty*"""
        )
        actual = "\n".join(x.rstrip() for x in repr(data).split("\n"))
        print(actual)
>       assert expected == actual
E       AssertionError: assert '<xarray.Data...\n    *empty*' == '<xarray.Data...\n    *empty*'
E
E         Skipping 71 identical trailing characters in diff, use -v to show
E         - <xarray.Dataset> Size: 64B
E         ?                         -
E         + <xarray.Dataset> Size: 96B
E         ?                        +
E           Dimensions:  (x: 4)...
E
E         ...Full output truncated (9 lines hidden), use '-vv' to show

/tmp/xarray/xarray/tests/test_dataset.py:351: AssertionError
----------------------------- Captured stdout call -----------------------------
<xarray.Dataset> Size: 64B
Dimensions:  (x: 4)
Coordinates:
  * x        (x) object 16B MultiIndex
  * level_1  (x) object 16B 'a' 'a' 'b' 'b'
  * level_2  (x) int64 32B 1 2 1 2
Data variables:
    *empty*
_________________________ test_array_repr_dtypes_unix __________________________

    @pytest.mark.skipif(
        ON_WINDOWS,
        reason="Default numpy's dtypes vary according to OS",
    )
    def test_array_repr_dtypes_unix() -> None:

        # Signed integer dtypes

        ds = xr.DataArray(np.array([0]), dims="x")
        actual = repr(ds)
        expected = """
    <xarray.DataArray (x: 1)> Size: 8B
    array([0])
    Dimensions without coordinates: x
            """.strip()
>       assert actual == expected
E       AssertionError: assert '<xarray.Data...oordinates: x' == '<xarray.Data...oordinates: x'
E
E         Skipping 37 identical trailing characters in diff, use -v to show
E         - <xarray.DataArray (x: 1)> Size: 8B
E         ?                                 ^
E         + <xarray.DataArray (x: 1)> Size: 4B
E         ?                                 ^
E           array([

/tmp/xarray/xarray/tests/test_formatting.py:1090: AssertionError

Anything else we need to know?
No response
Environment

INSTALLED VERSIONS
commit: 380979fc213b3d1f53f097bab9b61851391be729
python: 3.11.9 (main, May  6 2024, 20:29:08) [GCC 13.2.1 20240210]
python-bits: 32
OS: Linux
OS-release: 6.9.4-gentoo-dist
machine: x86_64
processor: AMD Ryzen 5 3600 6-Core Processor
byteorder: little
LC_ALL: None
LANG: C.UTF8
LOCALE: ('en_US', 'UTF-8')
libhdf5: None
libnetcdf: None
xarray: 2024.6.0
pandas: 2.2.2
numpy: 1.26.4
scipy: 1.13.1
netCDF4: None
pydap: None
h5netcdf: None
h5py: None
zarr: None
cftime: 1.6.4
nc_time_axis: None
iris: None
bottleneck: 1.4.0rc5
dask: None
distributed: None
matplotlib: 3.9.0
cartopy: None
seaborn: None
numbagg: None
fsspec: None
cupy: None
pint: None
sparse: None
flox: None
numpy_groupies: None
setuptools: 69.5.1
pip: None
conda: None
pytest: 8.2.2
mypy: None
IPython: None
sphinx: None

I see some of those tests are skipped on windows; possibly we should also check for whether the platform is 32 bit and skip on those?

Either that, or adjusting expected sizes depending on the platform.

These are looking at the reprs, so adjusting the expectations isn't easy.
We would def take a PR to skip them based on the platform though!

Does skipping based on the value of sys.maxsize sound about right? I think that's the simplest way of determining whether we're dealing with a 64-bit platform.

That seems to be the recommended way

we can also try hard-coding the dtype for those variables

Actually, fixing expectations doesn't seem that hard, so I'm going to try doing that first. If you don't like that, we can look into other solutions.

authors: dcherian keewis max-sixty mgorny

repo: pydata/xarray


text:
Fix bulleted list indentation in docstrings

[x] Closes #5248
[x] Passes pre-commit run --all-files

As I understand it, the issue described in #5248 is caused by bad indentation... With this PR, we get the following:

@max-sixty, let me know if there are other instances that need to be fixed as part of this PR....

That looks great! Thanks!
If there's a way of auto-failing anything that violates this, that would keep it good. But maybe the previous text is indistinguishable from normal prose...
Not worth worry about at all — really — FYI this looks a tiny bit inconsistent:

@max-sixty, the inconsistencies are now fixed...

If there's a way of auto-failing anything that violates this, that would keep it good. But maybe the previous text is indistinguishable from normal prose...

Not sure there's a way to automatically detecting these issues :(

the initial issue, at least, would have been caught by velin

the initial issue, at least, would have been caught by velin

Right... In a previous comment https://github.com/pydata/xarray/pull/4872#issue-568848688 you mentioned that the primary reason the velin hook was deactivated is because of the package maturity. Have you had a chance to test drive it lately? Is there a timeline on when we should activate it?
https://github.com/pydata/xarray/blob/9f118624e7924c80fc305f351fa9621d2b58514c/.pre-commit-config.yaml#L27-L30

Maybe it's time to let Velin spring free! @keewis up to you, as ever

@andersy005 I'll hit the button here, if that's OK with you?

Thanks, @max-sixty

Thank you @andersy005 !

Have you had a chance to test drive it lately?

Maybe it's time to let Velin spring free!

no, not recently. I'll need to investigate more, but I think we should probably do that soon. There should be standard rst linters, too, but those might need more configuration: sphinx adds a lot of new directives.

source: gharchive/pull-request

authors: andersy005 keewis max-sixty

license_type: permissive

license_source: github-api


text:
Add Dataset.dtypes property

[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst
[x] New functions/methods are listed in api.rst

Currently returns a Mapping from variable names to dtypes for ALL variables in the Dataset, including coordinates.
Possibly better to only return data_vars dtypes? Give me your thoughts on that, it is easy to change.

Great!
My inkling would be only data variables, given that's all we iterate over on a Dataset. We could also add this into the DatasetCoords / DataArrayCoords for completeness.
Any other thoughts?

My inkling would be only data variables, given that's all we iterate over on a Dataset.

I would have thought the same. I have updated it now.

See related discussion here: https://github.com/pydata/xarray/issues/1699
I like the idea of .dtypes only listing data variables and coords.dtypes for the rest. This would nicely generalize to DataArray.coords.dtypes

Is it intentional that DataArrayCoordinates and DatasetCoordinates are not part of api?

Is it intentional that DataArrayCoordinates and DatasetCoordinates are not part of api?

Good question, I'm not sure. They are not intended to be created by users IIUC, it's more like a "view" of the underlying coords. Does anyone have a view?

Good question, I'm not sure. They are not intended to be created by users IIUC, it's more like a "view" of the underlying coords. Does anyone have a view?

My understanding of these classes is that they are just slightly more complex mapping0like objects that we return instead of returning dicts in some cases. Sometimes they are intended to be immutable views and sometimes mutable IIUC. But I agree that they aren't intended to be instantiated directly by users.

Thank you v much @headtr1ck !

authors: TomNicholas dcherian headtr1ck max-sixty


text:
"AttributeError: 'FfsClient' object has no attribute 'get_file_bytes'"

This is a regression generated by line 17 https://github.com/pygate/pygate-gRPC/blob/8d875b000888539aa4ec0faa4526dad07fbb910c/examples/ffs_push_pull_file.py#L17 in examples/ffs_push_pull_file.py

Actually, this error only occurs when I run the script from pipenv shell. I've installed all the dependencies in a virtualenv and it works fine. So maybe pipfile needs an update?

I have moved the get_file_bytes from an instance method of ffs to a separate helper method. So maybe we're using a later version of the package?

source: gharchive/issue

authors: leonardge peterVG

repo: pygate/pygate-gRPC

license: MIT


text:
Publish on conda-forge?

Any thoughts about publishing this on conda-forge, so it would become "conda-installable"? This would allow other packages depending on geobuf to be published there, too. See https://github.com/conda-forge/staged-recipes.

Ok, meanwhile it happend. ;) See https://github.com/conda-forge/geobuf-feedstock and https://anaconda.org/conda-forge/geobuf.

repo: pygeobuf/pygeobuf

license: ISC


text:
DOC: pygeos.get_dimensions on empty LINESTRING

Based on pygeos.get_dimensions

Returns the inherent dimensionality of a geometry.
The inherent dimension is 0 for points, 1 for linestrings and linearrings, and 2 for polygons. For geometrycollections it is the max of the containing elements. Empty and None geometries return -1.

Strange, I was expecting -1 here:
pygeos.get_dimensions(pygeos.Geometry("LINESTRING EMPTY"))
> 1

I am trying to filter out LINESTRING EMPTY, maybe I should use another method to check "emptiness"
mask = array([<pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry MULTIPOINT (-7.23e+06 4.88e+06, -6.7e+06 4.96e+06)>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry POINT (-6.7e+06 4.96e+06)>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>,
       <pygeos.Geometry LINESTRING EMPTY>], dtype=object)

pygeos.get_dimensions(mask)
> array([[1, 1, 1, 1, 1, 0, 1, 1, 1],
       [1, 1, 1, 1, 1, 0, 1, 1, 1]], dtype=int32)

Edit:
Looks like this would do it, but it is quite verbose, to filter out all empty LINESTRINGS
mask[(pygeos.get_num_coordinates(crosses_mask) == 2) & (pygeos.get_type_id(crosses_mask) == pygeos.GeometryType.LINESTRING)]

Use is_empty to identify empty geometries.

Use is_empty to identify empty geometries.

The docstring should be update then, as I think it is only for empty GeometryCollections that it returns -1.

The docstring should be update then, as I think it is only for empty GeometryCollections that it returns -1.

(keeping the issue open since the docstring is wrong)

(keeping the issue open since the docstring is wrong)

repo: pygeos/pygeos


text:
Allow changing initial state of ToggleButton

Adds a toggled parameter to gui.ToggleButton that determines the initial toggled state of the widget.

Sorry for the delay.
To avoid the extra code in the library, the value property exists for this purpose. All Widgets contain this property to be used for manually setting the value (such as initial value). For example:
my_pushbutton = PushButton(...)
my_pushbutton.value = True

Oh alright, didn't know that. Thanks.

repo: pyglet/pyglet


text:
Figure out API for incorporating information from lift tests on MMM

@juanitorduz mentioned that in the literature this is usually incorporated into the prior information, but I think that in the HelloFresh project @lucianopaz found a way to incorporate such information via observed variables in the same MMM model?

I think with the great work by @wd60622 in https://github.com/pymc-labs/pymc-marketing/pull/590, we can close this one 🚀 !

repo: pymc-labs/pymc-marketing


text:
Pipenv clean fails if venv doesn't exist

$ python -m pipenv.help output
Pipenv version: `'11.7.1'`
Pipenv location: '/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv'
Python location: '/usr/local/Cellar/pipenv/11.7.1/libexec/bin/python'
Other Python installations in PATH:

2.7: /usr/bin/python2.7

2.7: /usr/bin/python2.7

3.6: /usr/local/bin/python3.6m

3.6: /usr/local/Cellar/pipenv/11.7.1/libexec/bin/python3.6

3.6: /usr/local/bin/python3.6

3.6: /usr/local/bin/python3.6

3.6.4: /usr/local/Cellar/pipenv/11.7.1/libexec/bin/python

2.7.10: /usr/bin/python

3.6.4: /usr/local/Cellar/pipenv/11.7.1/libexec/bin/python3

3.6.4: /usr/local/bin/python3

3.6.4: /usr/local/bin/python3

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.4',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '17.4.0',
 'platform_system': 'Darwin',
 'platform_version': 'Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST '
                     '2017; root:xnu-4570.41.2~1/RELEASE_X86_64',
 'python_full_version': '3.6.4',
 'python_version': '3.6',
 'sys_platform': 'darwin'}

System environment variables:

LDFLAGS
VIRTUALENVWRAPPER_SCRIPT
VIRTUALENVWRAPPER_PROJECT_FILENAME
TERM_PROGRAM
NVM_CD_FLAGS
TERM
SHELL
HISTSIZE
CPPFLAGS
TMPDIR
Apple_PubSub_Socket_Render
TERM_PROGRAM_VERSION
OLDPWD
TERM_SESSION_ID
LC_ALL
NVM_DIR
USER
CROSS_ACCOUNT_STACK_AWS_PROFILE_NAME_BBM_MASTER
COMMAND_MODE
SSH_AUTH_SOCK
__CF_USER_TEXT_ENCODING
FAB_COMPLETION_CACHE_TASKS
VIRTUAL_ENV
WORKON_HOME
PROJECT_HOME
VIRTUALENVWRAPPER_PYTHON
NPM_TOKEN
PATH
WERKZEUG_DEBUG_PIN
VIRTUALENVWRAPPER_HOOK_DIR
PWD
LANG
ITERM_PROFILE
XPC_FLAGS
PS1
FAB_COMPLETION_CACHED_TASKS_FILENAME
PYTEST_ADDOPTS
HISTCONTROL
XPC_SERVICE_NAME
SHLVL
HOME
COLORFGBG
CFLAGS
ITERM_SESSION_ID
LOGNAME
LC_CTYPE
PKG_CONFIG_PATH
PROMPT_COMMAND
VIRTUALENVWRAPPER_WORKON_CD
EXTRA_CFLAGS
SECURITYSESSIONID
EXTRA_LDFLAGS
COLORTERM
_
PIP_PYTHON_PATH
PYTHONUNBUFFERED

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/Cellar/pipenv/11.7.1/libexec/bin:/Users/craig/.yarn/bin:/Users/craig/.local/bin:/usr/local/opt/openssl/bin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
SHELL: /bin/bash
LANG: en_GB.UTF-8
PWD: /tmp
VIRTUAL_ENV: /usr/local/Cellar/pipenv/11.7.1/libexec

Contents of Pipfile ('/private/tmp/Pipfile'):
[[source]]

url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]

requests = "*"

[dev-packages]

[requires]

python_version = "3.6"

Contents of Pipfile.lock ('/private/tmp/Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "33a0ec7c8e3bae6f62dd618f847de92ece20e2bd4efb496927e2524b9c7b8df8"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.6"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.python.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "certifi": {
            "hashes": [
                "sha256:14131608ad2fd56836d33a71ee60fa1c82bc9d2c8d98b7bdbc631fe1b3cd1296",
                "sha256:edbc3f203427eef571f79a7692bb160a2b0f7ccaa31953e99bd17e307cf63f7d"
            ],
            "version": "==2018.1.18"
        },
        "chardet": {
            "hashes": [
                "sha256:84ab92ed1c4d4f16916e05906b6b75a6c0fb5db821cc65e70cbd64a3e2a5eaae",
                "sha256:fc323ffcaeaed0e0a02bf4d117757b98aed530d9ed4531e3e15460124c106691"
            ],
            "version": "==3.0.4"
        },
        "idna": {
            "hashes": [
                "sha256:2c6a5de3089009e3da7c5dde64a141dbc8551d5b7f6cf4ed7c2568d0cc520a8f",
                "sha256:8c7309c718f94b3a625cb648ace320157ad16ff131ae0af362c9f21b80ef6ec4"
            ],
            "version": "==2.6"
        },
        "requests": {
            "hashes": [
                "sha256:6a1b267aa90cac58ac3a765d067950e7dbbf75b1da07e895d1f594193a40a38b",
                "sha256:9c443e7324ba5b85070c4a818ade28bfabedf16ea10206da1132edaa6dda237e"
            ],
            "index": "pypi",
            "version": "==2.18.4"
        },
        "urllib3": {
            "hashes": [
                "sha256:06330f386d6e4b195fbfc736b297f58c5a892e4440e54d294d7004e3a9bbea1b",
                "sha256:cc44da8e1145637334317feebd728bd869a35285b93cbb4cca2577da7e62db4f"
            ],
            "version": "==1.22"
        }
    },
    "develop": {}
}

------------
Expected result
pipenv clean exist successfully. Virtualenv is created.
Actual result
craig@amogato2:/tmp
$ pipenv clean
Creating a virtualenv for this project…
Using /usr/local/bin/python3.6m (3.6.4) to create virtualenv…
⠋Running virtualenv with interpreter /usr/local/bin/python3.6m
Using base prefix '/usr/local/Cellar/python/3.6.4_4/Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/craig/.virtualenvs/tmp-agwWamBd/bin/python3.6
Also creating executable in /Users/craig/.virtualenvs/tmp-agwWamBd/bin/python
Installing setuptools, pip, wheel...done.

Virtualenv location: /Users/craig/.virtualenvs/tmp-agwWamBd
Traceback (most recent call last):
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/bin/pipenv", line 11, in <module>
    load_entry_point('pipenv==11.7.1', 'console_scripts', 'pipenv')()
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 722, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 697, in main
    rv = self.invoke(ctx)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/vendor/click/decorators.py", line 17, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/cli.py", line 459, in clean
    ctx=ctx, three=three, python=python, dry_run=dry_run, verbose=verbose
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/core.py", line 2451, in do_clean
    r = get_requirement(installed)
  File "/usr/local/Cellar/pipenv/11.7.1/libexec/lib/python3.6/site-packages/pipenv/utils.py", line 128, in get_requirement
    req = [r for r in requirements.parse(dep)][0]
IndexError: list index out of range

Steps to replicate
$ cd /tmp
$ mkdir clean-bug
$ cd clean-bug
$ pipenv install requests
$ pipenv --rm
$ pipenv clean

thanks for the report!

authors: jakul kennethreitz

repo: pypa/pipenv


text:
pipenv lock -r should output hashes but not index

Be sure to check the existing issues (both open and closed!), and make sure you are running the latest version of Pipenv.
Check the diagnose documentation for common issues and the PEEP list before posting! We may close your issue if it is very similar to one of them. Please be considerate and follow the PEEP process, or be on your way.
Make sure to mention your debugging experience if the documented solution failed.
Is your feature request related to a problem? Please describe.
When generating a requirements.txt file from a Pipfile, it currently does not include any --hash flags. Consequently, running pip install is vulnerable to certain supply chain attacks.
However, it does contain the index (via both -i and --extra-index-url).
Describe the solution you'd like
When generating a requirements.txt file from a Pipfile, it should include --hash on everything. That way someone running pip install on the resulting file will benefit from the enhanced security this provides.
However, it should not include the index, as it may include credentials which should not be written in plaintext. Or, at the very least, it should output it verbatim as it appears in the Pipfile, without expanding environment variables.
Describe alternatives you've considered
Today we don't use pipenv lock -r and instead have a custom solution for this.
Additional context
Add any other context or screenshots about the feature request here. It may be a good idea to mention that platform and Python version you are on.

@rittneje the new requirements command was released so I am closing this issue out for now.

authors: matteius rittneje


text:
revert library_dir_option patch.

Revert patch on distutils._msvccompiler.MSVCCompiler.library_dir_option.
See comments on #694.

Thanks. I tried again to build brotli from my local Windows machine (Python35-x86) using the latest setuptools tag v25.1.6, and it finally works.
This time, I made sure the correct setuptools was imported before I can say "it works". Sorry for the confusion.

authors: JGoutin anthrotype

repo: pypa/setuptools

license: mit

license_source: bigquery


text:
Deadline: reworked pools assignment

Brief description
Previous solution was nonconsistent, expected values for pools in multiple places in Setting.
Description
New collector and validator was introduced. Collector adds pool names from Setting (merged and removed separate pool settings in hosts sections) if not already present on a instance (as Maya has it, potentially others with New Publisher).
Validator checks if name of pools on the instances matches to current values on DL (does a query of DL).
Additional info
Refactored _requests_get and requests_post wrappers into openpype.lib.connections - name up for commenting/changing.
Testing notes:

configure project_settings/deadline/publish/CollectDeadlinePools
1.a - insert non existent values
1.b - insert values matching situation on DL
publish on DL and check pools

Maya render instance (and all render instances in other hosts) should check the settings and prefill the pools and groups from the settings
Pools and Groups should not be a drop-down, but text fields as we can combine multiple groups to fine-tune specific scene requirements. Ex. I need to submit my heavy scene to group Maya, Ram256 and GPU to render on machines with Maya installed, with more than 256 GB RAM and GPU card)

I would suggest to add pools and group to Nuke write instance (the same as we have in Maya)

there is also an issue in collect render layers (I'm not sure if it is connected to this PR though)
// pyblish.CollectMayaRender : collecting layer: rs_Main //
// Error: pyblish.plugin : Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "D:\REPO\OpenPype\openpype\hosts\maya\plugins\publish\collect_render.py", line 391, in process
KeyError: 'SecondaryPool'
Traceback (most recent call last):
  File "D:\REPO\OpenPype\.venv\lib\site-packages\pyblish\plugin.py", line 522, in __explicit_process
    runner(*args)
  File "<string>", line 391, in process
KeyError: 'SecondaryPool' //
b'Processing Context Label'

collect_render issue was resolved.

I'd expect users might want to set the Pool per project and per application, so that e.g. Maya runs in a different pool than Nuke or Harmony. Thoughts?

You are correct. I've already created issue #3057  to do it outside of this PR.

@BigRoy I thought that pools are per project and groups would be per host.
But maybe we should add there profile for host, task name?

authors: BigRoy kalisp m-u-r-p-h-y

repo: pypeclub/OpenPype


text:
FutureWarning: '+init=:' syntax is deprecated. ':' is the preferred initialization method. When making the change, be mindful of axis order changes: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6   projstring = _prepare_from_string(" ".join((projstring, projkwargs))

Code Sample, a copy-pastable example if possible
A "Minimal, Complete and Verifiable Example" will make it much easier for maintainers to help you:
http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports
# Your code here

Problem description
[this should explain why the current behavior is a problem and why the expected output is a better solution.]
Expected Output
Environment Information

Output from: pyproj -v

Output from: python -m pyproj -v

Output from: python -c "import pyproj; pyproj.show_versions()"

pyproj version (python -c "import pyproj; print(pyproj.__version__)")
PROJ version (python -c "import pyproj; print(pyproj.proj_version_str)")
PROJ data directory (python -c "import pyproj; print(pyproj.datadir.get_data_dir())")
Python version (python -c "import sys; print(sys.version.replace('\n', ' '))")
Operation System Information (python -c "import platform; print(platform.platform())")

Installation method

conda, pip wheel, from source, etc...

Conda environment information (if you installed with conda):

Environment (conda list):

$ conda list proj

Details about  conda and system ( conda info ):

$ conda info

Not enough information. Closing soon if clarity is not added to this issue.

After the Execution of the complete code, then the following message came in the terminal in vs code

This is the desired behavior. Please read: https://pyproj4.github.io/pyproj/stable/gotchas.html#axis-order-changes-in-proj-6 for how to update.

Essentially replace +init=epsg:4326 with EPSG:4326 and be careful of axis order changes (#538).


text:
make tests in /test Python 3 compatible

Replace:
cPickle with pickle
commands.getoutput() with subprocess.check_output()
All also run on Python 2.7.

Nice! Approved on my end assuming tests pass.


text:
Annotations are broken

Having this code:
searchType: task.done
searchTarget: Walk, Run
datasetName: Walk, Run
folder: Diary
month:
    mode: annotation
    annotation: 🚶♀,🏃♀
    startWeekOn: 'Mon'
    todayRingColor: orange
    selectedRingColor: white
    showSelectedValue: false
    todayRingColor: white

It outputs this.

if i hover that mountains of text, it's like this. looks like it prints the html and does not render it.

Version 1.10.6

Hi @felixsanz,
For some reason the emoji characters (🚶♀ and🏃♀) in your code block or notes are replaced by html img tags.
That's why there are texts like '<img draggable="false" class="emoji" ......' in the rendered view.
You can copy the emoji here.

This is not the first time users met this problem.
So I decide add a function to deal with html img tags.

Hi @felixsanz,
For some reasons, the emoji characters ( and) shown in your code block or notes are replaced by html img tags. (They are not emoji characters) That's why there are texts like '<img draggable="false" class="emoji" ......' in the rendered view.
Please copy the emoji here and replace those in your code block by the copied ones.
By the way, did you install any plugin related to emoji?

Yes i know that the code blocks are replaced by html, but doesn't matter where i copy those emojis, or if i use the two emoji plugins available for obsidian, it's always the same result

Hi,
Please download this example and check if it works.
Here is what I got

Nope, same issue. I'm using Linux in case is related

Mmm…
Will find a Linux machine and do some tests on it.
Thanks for the report.

The emojis can be displayed with no problem in obsidian.

The problem is your calendar that renders a  tag instead of the emoji. Maybe the tag is malformed?

Tracker did not create any html img tag.
Maybe the unicode characters are modified at some point before fed into Tracker.
The first thought about this is the YAML parser.
Tracker uses the embeded YAML parser provided by Obsidian API.
Maybe the parser behaves different on Linux.

Tracker does not create any html img tag.
Maybe the unicode characters are modified at some point before fed into Tracker.
The first thought about this is the YAML parser.
Tracker uses the embeded YAML parser provided by Obsidian API.
Maybe the parser behaves different on Linux.
By the way, could you test this for me?
Use single quotes to wrap the unicode characters
like this
searchTarget: ','

doesn't fix it :(
You're right, it's the YAML parser, check this:
https://github.com/blacksmithgu/obsidian-dataview/issues/118
Even the gear emoji displays wrong

Commit: https://github.com/blacksmithgu/obsidian-dataview/commit/fc7c8e6d65b8e13ebaad94918f971d17385338bb

It's different.
We use the function parseYaml from Obsidian API to get parameters from YAML.
Thus if what we got is an image tag, the only option is to turn it back to a emoji character.

The problem is similar but the solution is not related.
We use the function parseYaml from Obsidian API to get parameters from YAML.
Thus if what we got are image tags, the only option for us is to turn them back to emoji characters.
Will do it.

The alt="" parameter of the image tag already include the emoji, maybe you should insert just the content of the alt="" parameter into the calendar, instead of the whole  tag? If that's a solution looks pretty easy!

The alt="" parameter of the image tag already include the emoji, maybe you should insert just the content of the alt="" parameter into the calendar, instead of the whole  tag?

That was my plan.

Fixed!

Thanks for the fix.
Since image tags could be placed in any field in YAML, the problem should be treated more generally.
Also, we don't want to leave any image tags to the SVG graph building.
Thus, all image tags with alt will be replaced by the text in alt, otherwise replaced by empty string.
A fix has been committed (3810a63) for this.

It works on the calendar but you say that the problem affects the whole YAML options and it's not fixed there.
Example:
...
line:
    title: Weight Log 🚶
...

Will fix it.
Really appreciate your report.

no problem. if you need test specific options count on me

Hi @felixsanz,
Thanks again.
The fix was released with version 1.10.7.
You are still welcome to make pull requests or suggestions.

authors: felixsanz pyrochlore

repo: pyrochlore/obsidian-tracker


text:
Fix Kappa interface error display on Python3

KaSim/KaSa interface errors do not display when running PySB under
Python 3 (e.g. #300) due to a missing bytes-to-string conversion.
This PR resolves this using .decode('utf8') and adds a unit test
to check errors are raised properly with KaSim.

Coverage increased (+0.03%) to 75.828% when pulling 56de3fda54bcafeff3a91c00019a94206261de16 on alubbock:kasimPy3errorfix into 011b713d2a71e1f99019335fac074a6a62899634 on pysb:master.

Coverage increased (+0.03%) to 75.778% when pulling 9a16a9895f96935da85aac1af7404d64704a1994 on alubbock:kasimPy3errorfix into fc24f8b8903785625aa5b564bd2a01f9f3918050 on pysb:master.

Coverage increased (+0.03%) to 75.778% when pulling 109904d834241b6e2ff0f904840733d3be417624 on alubbock:kasimPy3errorfix into fc24f8b8903785625aa5b564bd2a01f9f3918050 on pysb:master.

Coverage increased (+0.03%) to 75.778% when pulling 109904d834241b6e2ff0f904840733d3be417624 on alubbock:kasimPy3errorfix into fc24f8b8903785625aa5b564bd2a01f9f3918050 on pysb:master.

authors: alubbock coveralls

repo: pysb/pysb


text:
[blocked] Pyodide v0.24.0 - will be 0.24.1

This MR would like to update Pyodide to its latest version:
https://blog.pyodide.org/posts/0.24-release/
Everything works just fine but I haven't brought in any new feature ... however, what I've observed by local tests:

there's no visible/relevant bootstrap speedup
if I pass packages as array directly to loadPyodide (avoiding the manual dance) matplot example breaks and fail due pyodide bootstrap errors ... I haven't fully read the API change or feature so this might be on me - update opened an issue in pyodide https://github.com/pyodide/pyodide/issues/4152 update this is indeed matplotlib breaking with latst Pyodide
I haven't tried other things like the filename as that requires bigger changes/refactoring so I agree with @antocuni we might want to add/check that after our RC1 goes out

If there's any other fix we'd like to have, this MR is ready to go AS-IS and I've seen no regression whatsoever so it's probably worth it updating before the RC goes out.

WARNING
The matplotlib package breaks with Pyodide 0.24.0 (other packages seem to be fine) ... I'd like to put this change on hold until we have time to actually check everything is fine.

i ran into a similar issue for matplotlib on worker only, but may be running on 0.24.0.  I will double check this.

FYI it looks like our matplotlib examples are all broken due https://github.com/pyodide/pyodide/issues/4153#issuecomment-1724879825 ... I will try to fix that in here and see how it goes but honestly I am not sure how to fix that as I don't know the lib much. Any help appreciated /cc @antocuni @JeffersGlass

Confirmed the blocker for this Pyodide release https://github.com/pyodide/pyodide/issues/4153#issuecomment-1725125095
We probably need to wait for the next one and be sure our examples still work.

I am updating both Pyodide and Ruby in this follow up MR https://github.com/pyscript/polyscript/pull/49
Closing this as behind current main and not Ruby related too.

authors: WebReflection bugzpodder

repo: pyscript/polyscript


text:
test_caldav_unit fails for tag 1.3.3

============================= test session starts ==============================
platform linux -- Python 3.11.3, pytest-7.4.0, pluggy-1.0.0
rootdir: /tmp/aur/python-caldav/src/caldav-1.3.3
plugins: cov-4.1.0
collected 117 items

tests/test_caldav.py s.s..s..s...........ss..............s....s......... [ 43%]
.........s...............s..                                             [ 67%]
tests/test_caldav_unit.py .................F...........                  [ 92%]
tests/test_cdav.py ......                                                [ 97%]
tests/test_utils.py .                                                    [ 98%]
tests/test_vcal.py ..                                                    [100%]

=================================== FAILURES ===================================
_________________________ TestCalDAV.testHugeTreeParam _________________________

self = <tests.test_caldav_unit.TestCalDAV object at 0x7f247a9427d0>

        def testHugeTreeParam(self):
            """
            With dealing with a huge XML response, such as event containing attachments, XMLParser will throw an exception
            huge_tree parameters allows to handle this kind of events.
            """

            xml = """
    <multistatus xmlns="DAV:">
      <response>
        <href>/17149682/calendars/testcalendar-84439d0b-ce46-4416-b978-7b4009122c64/</href>
        <propstat>
          <prop>
                    </prop>
          <status>HTTP/1.1 200 OK</status>
        </propstat>
        <propstat>
          <prop>
            <calendar-data xmlns="urn:ietf:params:xml:ns:caldav"/>
          </prop>
          <status>HTTP/1.1 404 Not Found</status>
        </propstat>
      </response>
      <response>
        <href>/17149682/calendars/testcalendar-84439d0b-ce46-4416-b978-7b4009122c64/20010712T182145Z-123401%40example.com.ics</href>
        <propstat>
          <prop>
            <calendar-data xmlns="urn:ietf:params:xml:ns:caldav">

    BEGIN:VCALENDAR
    PRODID:-//MDaemon Technologies Ltd//MDaemon 21.5.2
    VERSION:2.0
    METHOD:PUBLISH
    BEGIN:VEVENT
    UID:
     040000008200E0007000B7101A82E0080000000050BF99B19D31
    SEQUENCE:0
    DTSTAMP:20230213T142930Z
    SUMMARY:This a summary of a very bug event
    DESCRIPTION:Description of this very big event
    LOCATION:Somewhere
    ORGANIZER:MAILTO:noreply@test.com
    PRIORITY:5
    ATTACH;VALUE=BINARY;ENCODING=BASE64;FMTTYPE=image/jpeg;
     X-FILENAME=image001.jpg;X-ORACLE-FILENAME=image001.jpg:
    """
            xml += (
                "gIyIoLTkwKCo2KyIjM4444449QEBAJjBGS0U+Sjk/QD3/2wBDAQsLCw8NDx0QEB09KSMpPT09\n"
                * 153490
            )
            xml += """
     /Z
    DTSTART;TZID="Europe/Paris":20230310T140000
    DTEND;TZID="Europe/Paris":20230310T150000
    END:VEVENT
    END:VCALENDAR
    </calendar-data>
          </prop>
          <status>HTTP/1.1 200 OK</status>
        </propstat>
      </response>
    </multistatus>
    """
            davclient = MockedDAVClient(xml)
            resp = mock.MagicMock()
            resp.headers = {"Content-Type": "text/xml"}
            resp.content = xml

            davclient.huge_tree = False
            try:
                DAVResponse(resp, davclient=davclient)
>               assert False
E               assert False

tests/test_caldav_unit.py:955: AssertionError

During handling of the above exception, another exception occurred:

self = <tests.test_caldav_unit.TestCalDAV object at 0x7f247a9427d0>

        def testHugeTreeParam(self):
            """
            With dealing with a huge XML response, such as event containing attachments, XMLParser will throw an exception
            huge_tree parameters allows to handle this kind of events.
            """

            xml = """
    <multistatus xmlns="DAV:">
      <response>
        <href>/17149682/calendars/testcalendar-84439d0b-ce46-4416-b978-7b4009122c64/</href>
        <propstat>
          <prop>
                    </prop>
          <status>HTTP/1.1 200 OK</status>
        </propstat>
        <propstat>
          <prop>
            <calendar-data xmlns="urn:ietf:params:xml:ns:caldav"/>
          </prop>
          <status>HTTP/1.1 404 Not Found</status>
        </propstat>
      </response>
      <response>
        <href>/17149682/calendars/testcalendar-84439d0b-ce46-4416-b978-7b4009122c64/20010712T182145Z-123401%40example.com.ics</href>
        <propstat>
          <prop>
            <calendar-data xmlns="urn:ietf:params:xml:ns:caldav">

    BEGIN:VCALENDAR
    PRODID:-//MDaemon Technologies Ltd//MDaemon 21.5.2
    VERSION:2.0
    METHOD:PUBLISH
    BEGIN:VEVENT
    UID:
     040000008200E0007000B7101A82E0080000000050BF99B19D31
    SEQUENCE:0
    DTSTAMP:20230213T142930Z
    SUMMARY:This a summary of a very bug event
    DESCRIPTION:Description of this very big event
    LOCATION:Somewhere
    ORGANIZER:MAILTO:noreply@test.com
    PRIORITY:5
    ATTACH;VALUE=BINARY;ENCODING=BASE64;FMTTYPE=image/jpeg;
     X-FILENAME=image001.jpg;X-ORACLE-FILENAME=image001.jpg:
    """
            xml += (
                "gIyIoLTkwKCo2KyIjM4444449QEBAJjBGS0U+Sjk/QD3/2wBDAQsLCw8NDx0QEB09KSMpPT09\n"
                * 153490
            )
            xml += """
     /Z
    DTSTART;TZID="Europe/Paris":20230310T140000
    DTEND;TZID="Europe/Paris":20230310T150000
    END:VEVENT
    END:VCALENDAR
    </calendar-data>
          </prop>
          <status>HTTP/1.1 200 OK</status>
        </propstat>
      </response>
    </multistatus>
    """
            davclient = MockedDAVClient(xml)
            resp = mock.MagicMock()
            resp.headers = {"Content-Type": "text/xml"}
            resp.content = xml

            davclient.huge_tree = False
            try:
                DAVResponse(resp, davclient=davclient)
                assert False
            except Exception as e:
>               assert type(e) == lxml.etree.XMLSyntaxError
E               AssertionError: assert <class 'AssertionError'> == <class 'lxml.etree.XMLSyntaxError'>
E                +  where <class 'AssertionError'> = type(AssertionError('assert False'))
E                +  and   <class 'lxml.etree.XMLSyntaxError'> = <module 'lxml.etree' from '/usr/lib/python3.11/site-packages/lxml/etree.cpython-311-x86_64-linux-gnu.so'>.XMLSyntaxError
E                +    where <module 'lxml.etree' from '/usr/lib/python3.11/site-packages/lxml/etree.cpython-311-x86_64-linux-gnu.so'> = lxml.etree

tests/test_caldav_unit.py:957: AssertionError
=========================== short test summary info ============================
FAILED tests/test_caldav_unit.py::TestCalDAV::testHugeTreeParam - AssertionEr...
================== 1 failed, 106 passed, 10 skipped in 16.10s ==================

Huh ... it passes on github, perhaps some versioning problems with the lxml module?  I'll look into it.

1.3.4 has been released

Oh noes ... I was too quick and broke the style test.  There will be a 1.3.5 soon. (I thought I configured github so that it should not merge pull requests unless all tests passed ... weird)

authors: fauxmight tobixen

repo: python-caldav/caldav


text:
Tolerate receiving frames on a closed stream

We encountered this issue while running HTTPX against duckduckgo.com using HTTP/2:
https://github.com/encode/httpx/issues/173
Basically DDG would emit headers, data with end_stream=True, then emit a window update for that stream. h2 would error out on the window update because the stream is closed. Can h2 be changed to tolerate receiving non-response frames on a closed stream?

Perhaps we should send STREAM_CLOSED on a RST_STREAM frame when this occurs?
https://httpwg.org/specs/rfc7540.html#StreamErrorHandler

This was fixed in #1191

@pgjones do you plan to make a new release soon?

Dupe of #1183.
Yep, hopefully Friday.

Closing this as it's already been solved! Thank you everyone. :)

authors: pgjones sethmlarson vmagamedov


text:
Provide base class for events

Right now I'm trying to add more type information to the mitmproxy HTTP/2 stack and stumbled upon the fact that alle h2 events are just objects. I would like to see a generic h2.events.Event class or something similar.
Does it make sense to provide a base class for all events?

I suggested this a while ago but didn't create a PR. I'm sure it would be pretty easy to create. :)

Yup, this would be necessary for defining events. I'm happy to have a no-op base class.

authors: Kriechi Lukasa SethMichaelLarson


text:
Auto-ACK Settings

Hi,
In your docs it is stated:

In HTTP/2, settings changes need to be acknowledged. hyper-h2 does not
automatically acknowledge them, because it is possible that the caller may
not be happy with the changed setting (or would like to know about it).

Could you elaborate on why the caller "might not be happy" with the changes?
There is no negotiation of settings, either you ACK them, or you get a GoAway or something, as far as I understand it? Creating a RemoteSettingsChanged by itself is nice to have, but manually having to ACK them is IMHO not necessary, it would be cleaner to handle that the same way pings are auto-handled.
Or am I missing some important edge-case?
Thanks for the explanation.
P.S. I know it is only 2 LOCs, but still - if we could put these lines into hyper-h2 I think it is easier to use.

@Kriechi I am 50/50 on this.
So, you're correct that there's no negotiation of settings. However, if a user receives a settings value they do not like (e.g. SETTINGS_MAX_CONCURRENT_STREAMS set to 0, which will temporarily disallow the creation of new streams), they may prefer to send a GOAWAY than to acknowledge the settings. This makes it possible to avoid sending a potentially misleading SETTINGS ACK, when the settings have not actually been acknowledged.
With that said, I'm open to being convinced that this is actually such a minor use-case that we don't need to allow it.

Sending a GoAway instead of SettingsAck makes sense - but I would guess that is very uncommon.
As discussed earlier, maybe the default behaviour of hyper-h2 could be to ACK new settings automatically - and the user can disable this during H2Connection instantiation.

I'm beginning to lean towards simply removing this as an option: automatically acknowledge the settings, and not worry about the desire to say GOAWAY in response. If we really find we need the flag we can add it in later.

authors: Kriechi Lukasa


text:
Specification Extensions are not supported - x- is prohibited

Hi,
using f57d401
~/venv/lapidary/bin/lapidary init openapi/openapi.yaml lib dsp8010
…
pydantic.error_wrappers.ValidationError: 194 validation errors for OpenApiModel
info -> x-copyright
  extra fields not permitted (type=value_error.extra)
paths -> __root__ -> /redfish/v1/Chassis/{ChassisId}/MediaControllers -> get -> x-deprecatedReason
  extra fields not permitted (type=value_error.extra)
paths -> __root__ -> /redfish/v1/Chassis/{ChassisId}/MediaControllers -> get -> x-versionDeprecated
  extra fields not permitted (type=value_error.extra)
paths -> __root__ -> /redfish/v1/Chassis/{ChassisId}/MediaControllers -> $ref
  field required (type=value_error.missing)
paths -> __root__ -> /redfish/v1/Chassis/{ChassisId}/MediaControllers -> get
  extra fields not permitted (type=value_error.extra)

This is unfortunate as I consider (this part of the) input data valid OpenAPI.
It's the DSP8010 OpenAPI description document of the Redfish protocol by the DMTF. archive live
The x- is questions in the (Specification Extensions)[https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.1.0.md#specification-extensions].

The naive approach would be to change the OpenAPI model classes to read Config.extra=Ignore or Allow instead of Forbid. You can try it to see if you get any other errors.
Unfortunately it would allow all keys, not just those matching ^x-. I'm pretty sure Pydantic validators have a solution to this. I'll take a look, unless you'd like to.

I found a few other things that Lapidary doesn't currently support to run this schema:

multi-file schemas (external $refs)
operations without operationId

Also a single stub file with nearly 2000 methods would be very slow for tools to read. GSMTasks has 150 and it's sluggish.
I think all those issues should be handled at some point.

I'm pretty sure Pydantic validators have a solution to this. I'll take a look, unless you'd like to.

I use a pre validator to remove x-* from the data.
https://github.com/commonism/aiopenapi3/blob/c619ee9fcfc3780b64bc6c53eee61158123a44d8/aiopenapi3/base.py#L30-L52

authors: commonism rafalkrupinski

repo: python-lapidary/lapidary


text:
🛑 Dev Forum is down

In 00a49eb, Dev Forum (https://devforum.roblox.com/) was down:

HTTP code: 403
Response time: 140 ms

Resolved: Dev Forum is back up in e5fd6cd after 40 minutes.

repo: pythoniaweb/statusboom


text:
🛑 Data Storage Api is down

In 34df783, Data Storage Api (https://gamepersistence.roblox.com/) was down:

HTTP code: 404
Response time: 91 ms

Resolved: Data Storage Api is back up in fd9cfd5 after 1 hour, 24 minutes.


text:
❓ [Question] What am I missing to install TensorRT v1.1.0 in a Jetson with JetPack 4.6

❓ Question
I am getting some errors trying to install TensorRT v1.1.0 in a Jetson with JetPack 4.6 for using with Python3
What you have already tried
I followed the Official installation of Pytorch v1.10.0 by using binaries according to the  offical Nvidia Forum. Then, I followed the official steps of this repository which are:

Install Bazel - successfully
Build Natively on aarch64 (Jetson) - Here I am getting the problem

Environment

PyTorch Version :1.10.0
OS (e.g., Linux): Ubuntu 18.04
How you installed PyTorch: Using pip3 according to Nvidia Forum
Python version: 3.6
CUDA version: 10.2
TensorRT version: 8.2.1.8
CUDNN version: 8.2.0.1
GPU models and configuration: Jetson NX with JetPack 4.6
Any other relevant information: Installation is clean. I am using the CUDA and TensorRT that come flashed wich JetPack.

Additional context
Starting from a clean installation of JetPack and Torch 1.10.0 installed by using official binaries, I describe the installation steps I did for using this repository with the errors I am getting.
1- Install Bazel
git clone -b v1.1.0 https://github.com/pytorch/TensorRT.git
sudo apt-get install openjdk-11-jdk
export BAZEL_VERSION=$(cat /home/tkh/TensorRT.bazelversion)
mkdir bazel
cd bazel
curl -fSsL -O https://github.com/bazelbuild/bazel/releases/download/$BAZEL_VERSION/bazel-$BAZEL_VERSION-dist.zip
unzip bazel-$BAZEL_VERSION-dist.zip
bash ./compile.sh
cp output/bazel /usr/local/bin/

At this point I can see bazel 5.1.1- (@non-git) with bazel --version.
2- Build Natively on aarch64 (Jetson)
Then, I modified my WORKSPACE file of this repository in this way
workspace(name = "Torch-TensorRT")

load("@bazel_tools//tools/build_defs/repo:http.bzl", "http_archive")
load("@bazel_tools//tools/build_defs/repo:git.bzl", "git_repository")

http_archive(
    name = "rules_python",
    sha256 = "778197e26c5fbeb07ac2a2c5ae405b30f6cb7ad1f5510ea6fdac03bded96cc6f",
    url = "https://github.com/bazelbuild/rules_python/releases/download/0.2.0/rules_python-0.2.0.tar.gz",
)

load("@rules_python//python:pip.bzl", "pip_install")

http_archive(
    name = "rules_pkg",
    sha256 = "038f1caa773a7e35b3663865ffb003169c6a71dc995e39bf4815792f385d837d",
    urls = [
        "https://mirror.bazel.build/github.com/bazelbuild/rules_pkg/releases/download/0.4.0/rules_pkg-0.4.0.tar.gz",
        "https://github.com/bazelbuild/rules_pkg/releases/download/0.4.0/rules_pkg-0.4.0.tar.gz",
    ],
)

load("@rules_pkg//:deps.bzl", "rules_pkg_dependencies")

rules_pkg_dependencies()

git_repository(
    name = "googletest",
    commit = "703bd9caab50b139428cea1aaff9974ebee5742e",
    remote = "https://github.com/google/googletest",
    shallow_since = "1570114335 -0400",
)

# External dependency for torch_tensorrt if you already have precompiled binaries.
local_repository(
    name = "torch_tensorrt",
    path = "/opt/conda/lib/python3.8/site-packages/torch_tensorrt"
)

# CUDA should be installed on the system locally
new_local_repository(
    name = "cuda",
    build_file = "@//third_party/cuda:BUILD",
    path = "/usr/local/cuda-10.2/",
)

new_local_repository(
    name = "cublas",
    build_file = "@//third_party/cublas:BUILD",
    path = "/usr",
)
#############################################################################################################
# Tarballs and fetched dependencies (default - use in cases when building from precompiled bin and tarballs)
#############################################################################################################

####################################################################################
# Locally installed dependencies (use in cases of custom dependencies or aarch64)
####################################################################################

# NOTE: In the case you are using just the pre-cxx11-abi path or just the cxx11 abi path
# with your local libtorch, just point deps at the same path to satisfy bazel.

# NOTE: NVIDIA's aarch64 PyTorch (python) wheel file uses the CXX11 ABI unlike PyTorch's standard
# x86_64 python distribution. If using NVIDIA's version just point to the root of the package
# for both versions here and do not use --config=pre-cxx11-abi

new_local_repository(
    name = "libtorch",
    path = "/home/tkh-ad/.local/lib/python3.6/site-packages/torch",
    build_file = "third_party/libtorch/BUILD"
)

new_local_repository(
    name = "libtorch_pre_cxx11_abi",
    path = "/home/tkh-ad/.local/lib/python3.6/site-packages/torch",
    build_file = "third_party/libtorch/BUILD"
)

new_local_repository(
    name = "cudnn",
    path = "/usr/local/cuda-10.2/",
    build_file = "@//third_party/cudnn/local:BUILD"
)

new_local_repository(
   name = "tensorrt",
   path = "/usr/",
   build_file = "@//third_party/tensorrt/local:BUILD"
)

# #########################################################################
# # Testing Dependencies (optional - comment out on aarch64)
# #########################################################################
#pip_install(
#    name = "torch_tensorrt_py_deps",
#    requirements = "//py:requirements.txt",
#)

#pip_install(
#    name = "py_test_deps",
#    requirements = "//tests/py:requirements.txt",
#)

#pip_install(
#    name = "pylinter_deps",
#    requirements = "//tools/linter:requirements.txt",
#)

Finally, when I launch python3 py/setup.py install --use-cxx11-abi the error happend
py/setup.py:52: UserWarning: Assuming jetpack version to be 4.6, if not use the --jetpack-version option
  warnings.warn("Assuming jetpack version to be 4.6, if not use the --jetpack-version option")
/usr/lib/python3.6/distutils/dist.py:261: UserWarning: Unknown distribution option: 'long_description_content_type'
  warnings.warn(msg)
running install
Jetpack version: 4.6
building libtorchtrt
INFO: Build options --compilation_mode, --cxxopt, --define, and 1 more have changed, discarding analysis cache.
INFO: Analyzed target //:libtorchtrt (1 packages loaded, 3226 targets configured).
INFO: Found 1 target...
ERROR: /home/tkh-ad/.cache/bazel/_bazel_tkh-ad/9449ca3ce00d402b1ed43474fe8a8b7c/external/cudnn/BUILD.bazel:18:11: Middleman _middlemen/@cudnn_S_S_Ccudnn_Uheaders-BazelCppSemantics_build_arch_aarch64-opt failed: missing input file 'external/cudnn/include/cudnn.h', owner: '@cudnn//:include/cudnn.h'
ERROR: /home/tkh-ad/.cache/bazel/_bazel_tkh-ad/9449ca3ce00d402b1ed43474fe8a8b7c/external/cudnn/BUILD.bazel:18:11: Middleman _middlemen/@cudnn_S_S_Ccudnn_Uheaders-BazelCppSemantics_build_arch_aarch64-opt failed: 1 input file(s) do not exist
Target //:libtorchtrt failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /home/tkh-ad/.cache/bazel/_bazel_tkh-ad/9449ca3ce00d402b1ed43474fe8a8b7c/external/cudnn/BUILD.bazel:18:11 Middleman _middlemen/@cudnn_S_S_Ccudnn_Uheaders-BazelCppSemantics_build_arch_aarch64-opt failed: 1 input file(s) do not exist
INFO: Elapsed time: 1.866s, Critical Path: 0.02s
INFO: 2 processes: 2 internal.
FAILED: Build did NOT complete successfully

Note1: I installed TensorRT v1.0.0 successfully a week ago and now I am stuck trying to install in another Jetson.
Note2: I am getting the same error trying to install TensorRT v.1.0.0. Maybe is by the Bazel..

SOLVED!
The issue was here
new_local_repository(
    name = "cudnn",
    **path = "/usr/local/cuda-10.2/",**
    build_file = "@//third_party/cudnn/local:BUILD"
)

that path need to be just /usr/

Nice!

repo: pytorch/TensorRT


text:
feat: Added support for custom torch operators and converters in torchtrtc

Description
This PR addresses the RFC for custom torch ops and converters. Details can be referenced here:
https://github.com/pytorch/TensorRT/discussions/1103
Fixes # (issue)
#877
Type of change
Please delete options that are not relevant and/or add your own.

New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines of this project (You can use the linters)
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas and hacks
[ ] I have made corresponding changes to the documentation
[ ] I have added tests to verify my fix or my feature
[x] New and existing unit tests pass locally with my changes
[ ] I have added the relevant labels to my PR in so that relevant reviewers are notified

We could just extend the current custom converters example to show the CLI usage

We can add the option to compile the custom converter into a library and ingest it.


text:
[DataPipe] Cancel future object and always run callback in FullSync during shutdown

Stack from ghstack:

-> #1171

Differential Revision: D46157349

@nivekt has imported this pull request.  If you are a Meta employee, you can view this diff on Phabricator.

repo: pytorch/data


text:
Refactor DynamicLayer so the logic for each transform is separate

See functorch/csrc/Interpreter.h for the rundown of what happened.

cc @samdow @Chillee @bdhirsh if you folks wanted to take a look.
I'm relatively confident that the code is correct (it was me copy-pasting code from different locations) so don't feel a need to review it (I'll merge it in a couple of days if the CI is green)

repo: pytorch/functorch


text:
Delete "Does not show Jenkins builds"

As of https://github.com/pytorch/pytorch-ci-hud/commit/8c8911d7fe4c20888cf3407fdf06438f8399be45 Jenkins builds are displayed in new-style HUD

Do we need to keep the 'old-style' around anymore since we have the Jenkins builds on the normal one now?

@driazati I don't know answer to that one, but it does not hurt to have it

authors: driazati malfet

repo: pytorch/pytorch-ci-hud


text:
CMake GPU distributions cannot be compiled on Windows

🐛 Bug
CMake distributions of libtorchvision fail when trying to compile on Windows and NVCC, due to some commands that have syntax errors:
CudaBuildCore:
  Compiling CUDA source file ..\torchvision\csrc\cuda\DeformConv_cuda.cu...
  cmd.exe /C "C:\Users\circleci\AppData\Local\Temp\tmpe700956ac9f7445899d28481754c2c25.cmd"
  "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin\nvcc.exe" -gencode=arch=compute_35,code=\"sm_35,compute_35\" --use-local-env -ccbin "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\bin\HostX64\x64" -x cu  -I"C:\tools\miniconda3\Lib\site-packages\torch\include" -I"C:\tools\miniconda3\Lib\site-packages\torch\include\torch\csrc\api\include" -I"C:\Program Files\NVIDIA Corporation\NvToolsExt\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include" -I"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include"     --keep-dir x64\Release -maxrregcount=0  --machine 64 --compile -cudart static /EHsc /wd4267 /wd4251 /wd4522 /wd4838 /wd4305 /wd4244 /wd4190 /wd4101 /wd4996 /wd4275 /bigobj -Xcompiler="/EHsc -Ob2"    -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -DWIN32 -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -D_WINDLL -D_MBCS -Xcompiler "/EHsc /W3 /nologo /O2 /Fdtorchvision.dir\Release\vc142.pdb /FS /Zi  /MD /GR" -o torchvision.dir\Release\DeformConv_cuda.obj "C:\Users\circleci\project\torchvision\csrc\cuda\DeformConv_cuda.cu"

  circleci@PACKER-5F0EEC91 C:\Users\circleci\project\cpp_build>"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin\nvcc.exe" -gencode=arch=compute_35,code=\"sm_35,compute_35\" --use-local-env -ccbin "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\bin\HostX64\x64" -x cu  -I"C:\tools\miniconda3\Lib\site-packages\torch\include" -I"C:\tools\miniconda3\Lib\site-packages\torch\include\torch\csrc\api\include" -I"C:\Program Files\NVIDIA Corporation\NvToolsExt\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include" -I"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include"     --keep-dir x64\Release -maxrregcount=0  --machine 64 --compile -cudart static /EHsc /wd4267 /wd4251 /wd4522 /wd4838 /wd4305 /wd4244 /wd4190 /wd4101 /wd4996 /wd4275 /bigobj -Xcompiler="/EHsc -Ob2"    -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -DWIN32 -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -D_WINDLL -D_MBCS -Xcompiler "/EHsc /W3 /nologo /O2 /Fdtorchvision.dir\Release\vc142.pdb /FS /Zi  /MD /GR" -o torchvision.dir\Release\DeformConv_cuda.obj "C:\Users\circleci\project\torchvision\csrc\cuda\DeformConv_cuda.cu"
  nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\BuildCustomizations\CUDA 10.1.targets(764,9): error MSB3721: The command ""C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\bin\nvcc.exe" -gencode=arch=compute_35,code=\"sm_35,compute_35\" --use-local-env -ccbin "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.26.28801\bin\HostX64\x64" -x cu  -I"C:\tools\miniconda3\Lib\site-packages\torch\include" -I"C:\tools\miniconda3\Lib\site-packages\torch\include\torch\csrc\api\include" -I"C:\Program Files\NVIDIA Corporation\NvToolsExt\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include" -I"C:\Program Files (x86)\Microsoft Visual Studio\Shared\Python37_64\include" -I"C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include"     --keep-dir x64\Release -maxrregcount=0  --machine 64 --compile -cudart static /EHsc /wd4267 /wd4251 /wd4522 /wd4838 /wd4305 /wd4244 /wd4190 /wd4101 /wd4996 /wd4275 /bigobj -Xcompiler="/EHsc -Ob2"    -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -DWIN32 -D_WINDOWS -DNDEBUG -DNOMINMAX -D__CUDA_NO_HALF_OPERATORS__ -D"CMAKE_INTDIR=\"Release\"" -Dtorchvision_EXPORTS -D_WINDLL -D_MBCS -Xcompiler "/EHsc /W3 /nologo /O2 /Fdtorchvision.dir\Release\vc142.pdb /FS /Zi  /MD /GR" -o torchvision.dir\Release\DeformConv_cuda.obj "C:\Users\circleci\project\torchvision\csrc\cuda\DeformConv_cuda.cu"" exited with code 1. [C:\Users\circleci\project\cpp_build\torchvision.vcxproj]
Done Building Project "C:\Users\circleci\project\cpp_build\torchvision.vcxproj" (CudaBuildCore target(s)) -- FAILED.

To Reproduce
Steps to reproduce the behavior:

Generate MSVC project with cmake with cmake .. -DTorch_DIR=%TORCH_PATH%/share/cmake/Torch -DWITH_CUDA=1
Try to compile libtorchvision with msbuild "-p:Configuration=Release" torchvision.vcxproj

Expected behavior
libtorchvision should be compiled with GPU support on Windows
cc @peterjc123 @nbcsm @guyang3532 @maxluk @gunandrose4u @smartcat2010 @mszhanyi

@peterjc123 could you help with this?

Where is the corresponding cmake command?

@peterjc123, sorry for the incomplete instructions, the complete CMake instructions are the following, from the root of the source of torchvision, %TORCH_PATH% corresponds to the installation location of PyTorch:

mkdir build
cd build
cmake .. -DTorch_DIR=%TORCH_PATH%/share/cmake/Torch -DWITH_CUDA=1

@peterjc123 do you know what could be the issue?

Hi @fmassa, sorry for missing the message. I'll look into it soon.

I managed to get it working by replacing CMakeList.txt to the content below for 1.6.0.
cmake_minimum_required(VERSION 3.0)
project(torchvision)
set(CMAKE_CXX_STANDARD 14)
set(TORCHVISION_VERSION 0.6.0)

option(WITH_CUDA "Enable CUDA support" OFF)

if(WITH_CUDA)
  enable_language(CUDA)
  add_definitions(-D__CUDA_NO_HALF_OPERATORS__)
  set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} --expt-relaxed-constexpr")
endif()

find_package(Python3 COMPONENTS Development)
find_package(Torch REQUIRED)

function(CUDA_CONVERT_FLAGS EXISTING_TARGET)
    get_property(old_flags TARGET ${EXISTING_TARGET} PROPERTY INTERFACE_COMPILE_OPTIONS)
    if(NOT "${old_flags}" STREQUAL "")
        string(REPLACE ";" "," CUDA_flags "${old_flags}")
        set_property(TARGET ${EXISTING_TARGET} PROPERTY INTERFACE_COMPILE_OPTIONS
            "$<$<BUILD_INTERFACE:$<COMPILE_LANGUAGE:CXX>>:${old_flags}>$<$<BUILD_INTERFACE:$<COMPILE_LANGUAGE:CUDA>>:-Xcompiler=${CUDA_flags}>"
            )
    endif()
endfunction()

file(GLOB HEADERS torchvision/csrc/*.h)
file(GLOB OPERATOR_SOURCES torchvision/csrc/cpu/*.h torchvision/csrc/cpu/*.cpp torchvision/csrc/*.cpp)
if(WITH_CUDA)
  file(GLOB OPERATOR_SOURCES ${OPERATOR_SOURCES} torchvision/csrc/cuda/*.h torchvision/csrc/cuda/*.cu)
  CUDA_CONVERT_FLAGS(torch_cpu)
  CUDA_CONVERT_FLAGS(torch_cuda)
endif()
file(GLOB MODELS_HEADERS torchvision/csrc/models/*.h)
file(GLOB MODELS_SOURCES torchvision/csrc/models/*.h torchvision/csrc/models/*.cpp)

if(MSVC)
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} /wd4819")
  if(WITH_CUDA)
    set(CMAKE_CUDA_FLAGS "${CMAKE_CUDA_FLAGS} -Xcompiler=/wd4819")
    foreach(diag cc_clobber_ignored integer_sign_change useless_using_declaration
      set_but_not_used field_without_dll_interface
      base_class_has_different_dll_interface
      dll_interface_conflict_none_assumed
      dll_interface_conflict_dllexport_assumed
      implicit_return_from_non_void_function
      unsigned_compare_with_zero
      declared_but_not_referenced
      bad_friend_decl)
      string(APPEND CMAKE_CUDA_FLAGS " -Xcudafe --diag_suppress=${diag}")
    endforeach()
  endif()
endif()

add_library(${PROJECT_NAME} SHARED ${MODELS_SOURCES} ${OPERATOR_SOURCES})
target_link_libraries(${PROJECT_NAME} PRIVATE ${TORCH_LIBRARIES} Python3::Python)
set_target_properties(${PROJECT_NAME} PROPERTIES EXPORT_NAME TorchVision)

target_include_directories(${PROJECT_NAME} INTERFACE
  $<BUILD_INTERFACE:${HEADERS}>
  $<INSTALL_INTERFACE:${CMAKE_INSTALL_INCLUDEDIR}>)

include(GNUInstallDirs)
include(CMakePackageConfigHelpers)

set(TORCHVISION_CMAKECONFIG_INSTALL_DIR "share/cmake/TorchVision" CACHE STRING "install path for TorchVisionConfig.cmake")

configure_package_config_file(cmake/TorchVisionConfig.cmake.in
  "${CMAKE_CURRENT_BINARY_DIR}/TorchVisionConfig.cmake"
  INSTALL_DESTINATION ${TORCHVISION_CMAKECONFIG_INSTALL_DIR})

write_basic_package_version_file(${CMAKE_CURRENT_BINARY_DIR}/TorchVisionConfigVersion.cmake
  VERSION ${TORCHVISION_VERSION}
  COMPATIBILITY AnyNewerVersion)

install(FILES ${CMAKE_CURRENT_BINARY_DIR}/TorchVisionConfig.cmake
  ${CMAKE_CURRENT_BINARY_DIR}/TorchVisionConfigVersion.cmake
  DESTINATION ${TORCHVISION_CMAKECONFIG_INSTALL_DIR})

install(TARGETS ${PROJECT_NAME}
  EXPORT TorchVisionTargets
  LIBRARY DESTINATION ${CMAKE_INSTALL_LIBDIR}
  )

install(EXPORT TorchVisionTargets
  NAMESPACE TorchVision::
  DESTINATION ${TORCHVISION_CMAKECONFIG_INSTALL_DIR})

install(FILES ${HEADERS} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME})
install(FILES
  torchvision/csrc/cpu/vision_cpu.h
  DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME}/cpu)
if(WITH_CUDA)
  install(FILES
    torchvision/csrc/cuda/vision_cuda.h
    DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME}/cuda)
endif()
install(FILES ${MODELS_HEADERS} DESTINATION ${CMAKE_INSTALL_INCLUDEDIR}/${PROJECT_NAME}/models)

BTW, I'll try to cherry-pick the changes and make a pr.

Thanks @peterjc123 !

@peterjc123
What does it mean "with_cuda" in torchvision?
I think can attach cuda on the model without with_cuda compile?!

@ingbeeedd WITH_CUDA refers to the option whether you want the CUDA kernels of the torchvision ops (https://github.com/pytorch/vision/tree/main/torchvision/csrc/ops/cuda) or not. If your model doesn't rely on them, you can set it to OFF.

@peterjc123
It's a cuda operation related to object detection. Thank you

authors: andfoy fmassa ingbeeedd peterjc123

repo: pytorch/vision


text:
Torch Load Warning causing test suite to fail.

🐛 Describe the bug
Personally, I'm unable to follow the codepath, but it seems that the recent warning introcued in pytroch 2.4 is causing the test_transforms_v2 tests to fail due to the very strict warnings.
https://github.com/pytorch/vision/blob/main/test/test_transforms_v2.py#L57
2024-08-24T19:20:41.2823509Z _____ TestResizedCrop.test_transform[make_segmentation_mask-ratio-value2] ______
2024-08-24T19:20:41.2825077Z test/test_transforms_v2.py:3659: in test_transform
2024-08-24T19:20:41.2825572Z     check_transform(
2024-08-24T19:20:41.2826263Z test/test_transforms_v2.py:397: in check_transform
2024-08-24T19:20:41.2826701Z     pickle.loads(pickle.dumps(transform))
2024-08-24T19:20:41.2827710Z ../_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.10/site-packages/torch/storage.py:414: in _load_from_bytes
2024-08-24T19:20:41.2828812Z     return torch.load(io.BytesIO(b))
2024-08-24T19:20:41.2829850Z ../_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python3.10/site-packages/torch/serialization.py:1040: in load
2024-08-24T19:20:41.2830545Z     warnings.warn(
2024-08-24T19:20:41.2832296Z E   FutureWarning: You are using `torch.load` with `weights_only=False` (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for `weights_only` will be flipped to `True`. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via `torch.serialization.add_safe_globals`. We recommend you start setting `weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.

Versions
Pytorch 2.4
Conda-forge
sample log from https://github.com/conda-forge/torchvision-feedstock/pull/94:
181.log.txt

It looks like the issue might be in line 57 of test_transforms_v2.py
pytestmark = [pytest.mark.filterwarnings("error")]

I could be wrong. The comment above it suggests that warnings are turned into errors, and your log suggests that you're using torch.load 'with weights_only=False'. Is this explicitly called in your arguments or are you relying on the default value?

I am running the test suite when building the package for conda-forge.
I've removed that line to move forward with our builds, but I mostly wanted to flag this to the pytorch team as a whole.
We sometimes find ourselves a little more bleeding edge at the conda-forge builds, but I found it strange since torchvision officially supports pytorch 2.4.0 and that is when that warning first appeared.

Thanks for the report @hmaarrfk .
I think the error you're observing has already been addressed in both torchvision and pytorch codebases.
I had opened https://github.com/pytorch/vision/issues/8517 in torchvision and https://github.com/pytorch/pytorch/issues/130242 in pytorch, and https://github.com/pytorch/pytorch/pull/130246 was the fix. It may not have been picked up in pytorch 2.4 but hopefully it should be included in pytorch 2.4.1 (and in any case, in 2.5).

great thanks!

My reading of the solution is that you specified False which stops triggering the warning, but you left the "unsecure loading".
hmm, i have to say, one of the things i dislike the most about pytorch is its usage of pickle to load and store data structures.
I understand it enables fast iteration, but these security problems are a long standing issue in the design of pickle. However I also understand that it is difficult to move away from storage formats.
So good luck working through this migration (torchvision + pytorch!).
We are looking forward to continuing to be users of your software!
Hopefully you don't find my opening of issues too annoying.

authors: Jbenav200 NicolasHug hmaarrfk


text:
Register nms and roi_align Autocast policy for PyTorch Intel GPU backend

Intel GPU backend has been introduced to PyTorch, https://github.com/pytorch/pytorch/blob/main/third_party/xpu.txt. Some Torchvision models fails on torchvision::nms and torchvision::roi_align when enabling AMP execution. The PR is filed to add Autocast policy for Intel GPU backend, aligning CUDA and CPU policy and calculating on float for these two operators.
See details in [RFC] Intel GPU Upstreaming · Issue #114723 · pytorch/pytorch (github.com) about PyTorch Intel GPU backend.

Please refine the PR title and description.

Please refine the PR description and title.

Irrelevant lint error,

Please refine the PR title and description.

Updated.

hi @fengyuan14 looks like there are coupe of CI failures  RuntimeError: operator torchvision::nms does not exist please fix. These does not looks like existing errors, current state of torchvision is green: https://hud2.pytorch.org/hud/pytorch/vision/main

hi @fengyuan14 looks like there are coupe of CI failures  RuntimeError: operator torchvision::nms does not exist please fix. These does not looks like existing errors, current state of torchvision is green: https://hud2.pytorch.org/hud/pytorch/vision/main

Sure. I am checking the difference here, since it works at my local.

hi @fengyuan14 looks like there are coupe of CI failures  RuntimeError: operator torchvision::nms does not exist please fix. These does not looks like existing errors, current state of torchvision is green: https://hud2.pytorch.org/hud/pytorch/vision/main

Checked the failure. The failure only occurs in the step, Install testing utilities, and only on Macos+Python3.11. The step is ahead of building the Torchvision with my changes. In addition, other tests, Macos/Linux+Python3.xx, passed the step.
  Installing collected packages: urllib3, pluggy, iniconfig, idna, expecttest, coverage, charset-normalizer, certifi, requests, pytest, pytest-mock, pytest-cov
  Successfully installed certifi-2024.7.4 charset-normalizer-3.3.2 coverage-7.6.0 expecttest-0.2.1 idna-3.7 iniconfig-2.0.0 pluggy-1.5.0 pytest-7.4.4 pytest-cov-5.0.0 pytest-mock-3.14.0 requests-2.32.3 urllib3-2.2.2
Traceback (most recent call last):
  File "/Users/ec2-user/runner/_work/vision/vision/pytorch/vision/test/smoke_test.py", line 7, in <module>
    import torchvision
  File "/Users/ec2-user/.local/lib/python3.11/site-packages/torchvision/__init__.py", line 6, in <module>
    from torchvision import _meta_registrations, datasets, io, models, ops, transforms, utils
  File "/Users/ec2-user/.local/lib/python3.11/site-packages/torchvision/_meta_registrations.py", line 163, in <module>
    @torch._custom_ops.impl_abstract("torchvision::nms")
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ec2-user/runner/_work/_temp/miniconda/envs/ci/lib/python3.11/site-packages/torch/library.py", line 744, in register
    use_lib._register_fake(op_name, func, _stacklevel=stacklevel + 1)
  File "/Users/ec2-user/runner/_work/_temp/miniconda/envs/ci/lib/python3.11/site-packages/torch/library.py", line 183, in _register_fake
    handle = entry.fake_impl.register(func_to_register, source)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Users/ec2-user/runner/_work/_temp/miniconda/envs/ci/lib/python3.11/site-packages/torch/_library/fake_impl.py", line 31, in register
    if torch._C._dispatch_has_kernel_for_dispatch_key(self.qualname, "Meta"):
       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: operator torchvision::nms does not exist
ERROR conda.cli.main_run:execute(47): `conda run ./.github/scripts/unittest.sh` failed. (See above for error)
Error: Process completed with exit code 1.

Could you help to rerun the failure case?

@fengyuan14 , you can rebase this PR to trigger the CI again.

@pytorchbot rebase -b main

@NicolasHug Could you help to review the PR?

authors: EikanWang atalman fengyuan14


text:
Add README.md

I have compiled the necessary information for "New Submission for SciPy 2022 (SciPy Tutorials)" in a draft version in README.md.
@akaszynski @banesullivan @adeak If you have time could you review the contents?

I was going to commit my proofreading suggestions myself, but I don't believe I have commit rights to this repo. Could you please add the pyvista/developers team to this repo, @tkoyama010?

@adeak Thanks for review. I added pyvista/developers to administrator.

I added pyvista/developers to administrator.

Thank you @tkoyama010. Although admin rights might be too much. I think pyvista/developers only has write access to pyvista main repo for instance.
Also thanks for the work too :)

Excellent work @tkoyama010, thanks for getting this started. I'll be able to present, and might even be able to present there representing myself and potentially even Ansys.

Although admin rights might be too much. I think pyvista/developers only has write access to the pyvista main repo for instance.

@adeak  Now developers are maintainers now. If you want to be an Admin please mention it.

Let’s consider submitting this soon.

February 15    Tutorial submission deadline

How about submitting it on February 13?

@akaszynski @adeak @banesullivan Thanks for your help with the review. I'm proposing this content for the Scipy2022 Conference tonight. (Can someone APPROVE the changes? I need it for merging).

@tkoyama010, the deadline is extended, right? or do we need to submit tonight?

the deadline is extended, right? or do we need to submit tonight?

Yes, it is extended. I would have submitted it earlier if I didn't have any additional reviews, but @banesullivan gave it a useful review and I'll continue to elaborate.

Sorry for coming in late here! 😄 Thanks for all of your hard work on this!

@tkoyama010, thanks for your hardwork leading this! I made some minor changes. Ready to merge and we should submit soon here

authors: adeak akaszynski banesullivan tkoyama010

repo: pyvista/pyvista-tutorial


text:
乐云的缓存有时效性

乐云的缓存有时效性，会过期但是链接不会更新

乐云缓存链接应该是2天(48小时)后过期，之前验证过，没问题的。现在不行了么，具体时效性多久了解么？

现在具体多长时间没试，因为我上传的文件是22号19点上传的，而且从新解析还是上次的缓存链接，可能是不是需要加个判断或者第一次解析到下一次解析时间+48小时从新解析缓存呢

乐云缓存链接应该是2天(48小时)后过期，之前验证过，没问题的。现在不行了么，具体时效性多久了解么？

现在具体多长时间没试，因为我上传的文件是22号19点上传的，而且从新解析还是上次的缓存链接，可能是不是需要加个判断或者第一次解析到下一次解析时间+48小时从新解析缓存呢

判断是有的，缓存到期肯定重新解析，但乐云有效期比较久，还没有严格测试过，但应该问题不大

好了 好像第二次解析有延时

repo: qaiu/netdisk-fast-download


text:
🛑 nitter.privacytools.io is down

In 3761861, nitter.privacytools.io (https://nitter.privacytools.io) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nitter.privacytools.io is back up in f7102f6 after 21 minutes.


text:
🛑 nitter.fediflix.org is down

In 5439cce, nitter.fediflix.org (https://nitter.fediflix.org) was down:

HTTP code: 403
Response time: 735 ms

Resolved: nitter.fediflix.org is back up in a9a1ef1 after 3 hours, 6 minutes.


text:
🛑 nitter.pw is down

In e781e7b, nitter.pw (https://nitter.pw) was down:

HTTP code: 404
Response time: 275 ms

Resolved: nitter.pw is back up in 95dbccb.


text:
🛑 nitter.fediflix.org is down

In 211463f, nitter.fediflix.org (https://nitter.fediflix.org) was down:

HTTP code: 403
Response time: 489 ms

Resolved: nitter.fediflix.org is back up in ec0566a after 2 hours, 21 minutes.


text:
🛑 nitter.us.projectsegfau.lt is down

In 3a525d3, nitter.us.projectsegfau.lt (https://nitter.us.projectsegfau.lt) was down:

HTTP code: 503
Response time: 598 ms

Resolved: nitter.us.projectsegfau.lt is back up in 4d1f242 after 24 minutes.


text:
🛑 nitter.cutelab.space is down

In b0ebee8, nitter.cutelab.space (https://nitter.cutelab.space) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nitter.cutelab.space is back up in edb09bf after 10 minutes.


text:
🛑 notabird.site is down

In 47b6a14, notabird.site (https://notabird.site) was down:

HTTP code: 520
Response time: 50 ms

Resolved: notabird.site is back up in c408cd3.


text:
🛑 nitter.tiekoetter.com is down

In ab8a0cf, nitter.tiekoetter.com (https://nitter.tiekoetter.com) was down:

HTTP code: 502
Response time: 769 ms

Resolved: nitter.tiekoetter.com is back up in 653b77e.


text:
🛑 notabird.site is down

In 3f9181b, notabird.site (https://notabird.site) was down:

HTTP code: 520
Response time: 77 ms

Resolved: notabird.site is back up in e2ed89a after 51 days, 14 hours, 50 minutes.


text:
🛑 nitter.tiekoetter.com is down

In ad9ecc1, nitter.tiekoetter.com (https://nitter.tiekoetter.com) was down:

HTTP code: 502
Response time: 464 ms

Resolved: nitter.tiekoetter.com is back up in 0675934 after 4 hours, 45 minutes.


text:
🛑 notabird.site is down

In 5b655ac, notabird.site (https://notabird.site) was down:

HTTP code: 520
Response time: 58 ms

Resolved: notabird.site is back up in 5dd43e3 after 3 hours, 12 minutes.


text:
🛑 nitter.tiekoetter.com is down

In 81b9a7c, nitter.tiekoetter.com (https://nitter.tiekoetter.com) was down:

HTTP code: 502
Response time: 546 ms

Resolved: nitter.tiekoetter.com is back up in a234ce8 after 1 hour, 17 minutes.


text:
🛑 tweet.whateveritworks.org is down

In b62ee62, tweet.whateveritworks.org (https://tweet.whateveritworks.org) was down:

HTTP code: 502
Response time: 568 ms

Resolved: tweet.whateveritworks.org is back up in 1a8f584 after 16 minutes.


text:
🛑 notabird.site is down

In ce3ebf8, notabird.site (https://notabird.site) was down:

HTTP code: 520
Response time: 70 ms

Resolved: notabird.site is back up in 7f32f5e after 10 minutes.


text:
🛑 nitter.tiekoetter.com is down

In de99d27, nitter.tiekoetter.com (https://nitter.tiekoetter.com) was down:

HTTP code: 502
Response time: 675 ms

Resolved: nitter.tiekoetter.com is back up in 7ab3d5e after 46 minutes.


text:
🛑 nitter.tiekoetter.com is down

In 81051f2, nitter.tiekoetter.com (https://nitter.tiekoetter.com) was down:

HTTP code: 502
Response time: 648 ms

Resolved: nitter.tiekoetter.com is back up in 6c60431 after 37 minutes.


text:
🛑 notabird.site is down

In 2a04d4e, notabird.site (https://notabird.site) was down:

HTTP code: 520
Response time: 81 ms

Resolved: notabird.site is back up in aa471cb.


text:
Re-factor test run statistics update via WS

Currently test statistics are not updated correctly, we have to review and fix that problem to reflect correct pass/failed... statistics.

is done

authors: Boniara hursevich

repo: qaprosoft/zafira


text:
Request content-type should default to application/json

Spring defaults to application/json as expected content-type, this documenter should do the same (not */*)

@ethlo Thanks for bringing this up. I think it's in de.qaware.openapigeneratorforspring.common.paths.method.SpringWebHandlerMethodContentTypesMapper which you could override to fix it now, but I'll see if I can fix it within the library itself. Currently, it uses */* for request and response types, which is probably not right.

Thanks for the hints!
I worked around it for now with:
    @Bean
    public OperationPostFilter replaceContentType()
    {
        return (operation, handlerMethod) ->
        {
            final RequestBody rb = operation.getRequestBody();
            if (rb != null)
            {
                final Content requestParams = rb.getContent();
                final Iterator<Map.Entry<String, de.qaware.openapigeneratorforspring.model.media.MediaType>> requestsIter = requestParams.entrySet().iterator();
                while (requestsIter.hasNext())
                {
                    final Map.Entry<String, de.qaware.openapigeneratorforspring.model.media.MediaType> e = requestsIter.next();
                    if (ALL_VALUE.equals(e.getKey()))
                    {
                        requestsIter.remove();
                        requestParams.put(APPLICATION_JSON_VALUE, e.getValue());
                    }
                }
            }

            return true;
        };
    }

authors: ethlo neiser

repo: qaware/openapi-generator-for-spring


text:
When client is configured using url, port seems to be incorrectly set on some methods

I have a weird error: when Qdrant client is initialized with a full URL (ie https://hostname:port), client methods fails with a fetch failed / timeout errors but some don't.
The code:
const qdrantClient = new QdrantClient({ url: 'https://mydomain.com:443' });
try {
  await qdrantClient.getCollection('test');
}  catch (e) {
  console.log(e);
}

When used locally with a URL like http://localhost:6333 there's no issue, but when the URL is https://mydomain.com:443 I get a fetch failed error.
If I add the port manually in the client setup:
const qdrantClient = new QdrantClient({ url: 'https://mydomain.com:443', port: 443 });

It works normally.
EDIT: It also seems only some methods are affected by this, as I can make search queries just fine without having the port explicitly set?

Hello,
This issue arises because of the way URL package parses urls with default ports (443 for https and 80 for http) -
Note: If an input string passed to the URL() constructor doesn't contain an explicit port number (e.g., https://localhost) or contains a port number that's the default port number corresponding to the protocol part of the input string (e.g., https://localhost:443), then in the URL object the constructor returns, the value of the port property will be the empty string: ''.
reference: port

Would like to chip in here. As we are hosted qdrant in a self-host vanilla k8s and exposed the service via https instead of node port. As such we suspect this is the reason why we cannot integrate this qdrant service with others such as anything-llm in this way.

authors: bmkor harshalmittal4 sinedied

repo: qdrant/qdrant-js


text:
页面空白并且无法登录

版本0.4.4

网络原因


text:
占硬盘空间过大，没有缓存清理

今天查了一下mac下的文件，发现这个文件下的目录有18g这么大。请加入缓存定期清除功能。
尽量每个 issue 只提一个 bug 或新功能
提新 issue 前请确认 👉

没人提过这个 issue（这里看所有 issue）
项目的 Todo 里没有与你 issue 相关的内容（这里看 Todo）

反馈 bug 需要的信息

用的是网页版还是客户端
浏览器名称或电脑操作系统
控制台 Console 页面的截图（按 F12 可打开控制台）

设置里有限制音频缓存的选项

THX.

authors: memorydream xuezhai-f


text:
SQUASH: Rework config loading

Loading configs in the way we initially envisioned is a bit more complex than we initially hoped. This got grosser than I intended. Refactors/unit tests will come tomorrow. Fortunately, we should not need this to start messing with Parsl.

This now also contains the changes from parsl to parallel in the public API


text:
Pin pandas below 2.0

Pinning pandas below 2.0 will potentially fix some dependency issues.

Coverage: 92.935%. Remained the same when pulling 9d886bd9b3c75c8c0ea55318034c131909745381 on charles-cowart:pandas_pin into 17ae9ca60c3f93f2ffb5e5188b575f0aec527a14 on qiita-spots:dev.

authors: charles-cowart coveralls

repo: qiita-spots/qiita


text:
Lint ignore because of Qiskit

Steps to reproduce the problem
Run lint over a quantum circuit with measurement gate
ex : qc.measure(qram, c)
What is the current behavior?
E1101: Instance of 'QuantumCircuit' has no 'measure' member (no-member)
This error come from Terra
Resolve
We need to ignore this error in our Lint template

Corrected in qiskit-terra 19

repo: qiskit-community/ecosystem


text:
Various CI updates

Summary

remove Qiskit Aer (as it is not needed)
also test Python 3.11 (postponing this for now)
bump to Python 3.8 where 3.7 is not necessary
do not install Qiskit Terra from main (see also https://github.com/Qiskit/qiskit-nature/pull/1159)
disable CI for forks (see also https://github.com/Qiskit/qiskit-nature/pull/1163)

Details and comments

Pull Request Test Coverage Report for Build 4989565811

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 69.697%

Totals

Change from base Build 4813042321:
0.0%

Covered Lines:
69

Relevant Lines:
99

💛  - Coveralls

authors: coveralls mrossinek

repo: qiskit-community/qiskit-nature-pyscf


text:
213 move transform_data.py to code/codebase and major pylint

Summary
Addresses #213. Moves  transform_data.py to code/codebase
Also ran black just out of paranoia which ended up reformatting transform_data.py and the jupyter notebooks:
geometry_test.ipynb
docs/tutorials/1-tutorial-example.ipynb
Details and comments

 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 2 committers have signed the CLA.:x: grace-harper-ibm:x: awcross1You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant grace-harper-ibm

repo: qiskit-community/qiskit-qec


text:
Revision of BinaRena codebase - 1

Multiple improvements including:

Can export current view as a JSON file and later load it to resume.
Can export program log containing important numbers and status.
Added some flexibility to the dimensionality reduction script.
Fixed a bug that clears the plot in Firefox.

@pavia27 I have reached a milestone in coding. Now I am updating the program.

repo: qiyunlab/binarena


text:
Add typst-orange-template

Repo URL: https://github.com/flavio20002/typst-orange-template

Thanks for the awesome contribution @flavio20002 !

repo: qjcg/awesome-typst


text:
Some users in PSN not returning in the api

The following player has a  PSN Account and the api is returning "Impossible to fetch User. User not found on this platform"
but if you look for the player in https://fortnitetracker.com/profile/psn/estano2002
you are able to see his stats

I have the same problem with the username of a PC-only player. The API returns "Impossible to fetch User. User not found on this platform" but I can find it on Fortnite Tracker (https://fortnitetracker.com/profile/pc/Zelenion)

Here, A PSN account can work only if his account is link to Epic Games Account

authors: akairu mlcsthor qlaffont

repo: qlaffont/fortnite-api


text:
Export data from QdtTable

Hi,
I have created a grid using QdtTable component, which renders around 100k rows with 8 columns. I have kept the qHeight property to 20 as default, so each page has around 20 rows in more than 5k pages available through pagination. Inside the Qdt table component, I have also created a button to export this data into csv using 'react-csv' library. But I am able to export only those 20 rows which are on the current page and not the whole dataset. Am I approaching this right? Is there an easier way out to export data from the existing qdt components?

I believe this is possible with https://help.qlik.com/en-US/sense-developer/November2019/APIs/EngineAPI/services-GenericObject-ExportData.html but there's no such functionality built into QdtTable, and currently getting refs to an object created with qdt-components is broken due to switching from class components to functional components. So the only way forward this very moment without changing qdt-components is to make another hypercube (you can use qdtComponents.qDocPromise to get the qDoc) and call the exportData function on that.

Even if we use another hypercube to export data, it would still fetch max 10000 data points and not all the 5k pages after setting the Initial fetch property to maximum. So it won't help in the use case I am working on. One possible way is to loop through each page once the export button is clicked and store this data in an array. Then instead of referring to the Qdt-table, I can export that array object. Only roadblock for me in achieving this is, how and where to run this loop in the current qdt component setup. Should it be in the useHypercube hook or QdtTable? I tried to loop over the pageIndex in QdtTable , but it changes the page in the rendered QdtTable as well. Appreciate your input on this.

What I mean is to create a hypercube, or any generic object, then use this method - https://help.qlik.com/en-US/sense-developer/November2019/APIs/EngineAPI/services-GenericObject-ExportData.html
I just tried it, and was able to successfully export almost 400,000 cells of data no problem.
qdtComponents.qDocPromise.then((qDoc) => {   qDoc.createSessionObject({     qInfo: { qType: 'data' },     qHyperCubeDef: {       qDimensions: [         {           qDef: { qFieldDefs: ['NAME'] },         },       ],       qMeasures: [         {           qDef: { qDef: 'Sum(BRANCHES)' },         },       ],       qInitialDataFetch: [{         qWidth: 2,         qHeight: 1000,       }],     },   }).then((qObj) => {     qObj.exportData('OOXML', '/qHyperCubeDef').then((res) => {       const a = window.document.createElement('a');       a.innerHTML = 'Download data';       a.href = ${(options.config.secure ? 'https://' : 'http://') + options.config.host + (options.config.port ? :${options.config.port} : '') + options.config.prefix}${res.qUrl};       window.document.body.appendChild(a);       console.log(res);     });   }); });

I'm moving this to an enhancement. You can implement your own function like I demonstrated above for now easily, but I would like to have export data, done correctly using the exportData function, added to every qdt-component.

authors: fkabinoff kvivekkr

repo: qlik-demo-team/qdt-components


text:
Test Issue - liyrj

Test Body - wnfbpnxtqg

Test Comment - sttip

repo: qlikqaa/dummyrepo


text:
Test Issue - wuchq

Test Body - flwvfcpils

Test Comment - cdvdh


text:
Test Issue - dcmpo

Test Body - plwqrlltkh

Test Comment - ahkre


text:
Test Issue - cgclt

Test Body - hlnvcozyak

Test Comment - hyfvp


text:
Test Issue - chlzi

Test Body - wpejitvlkt

Test Comment - bnxli


text:
Test Issue - rzpbs

Test Body - wlglqtedts

Test Comment - dhebg


text:
Test Issue - tlbyj

Test Body - qcjkybdils

Test Comment - xcpom


text:
Test Issue - fhbrw

Test Body - ieyhdstazz

Test Comment - lzsay


text:
Test Issue - isnqn

Test Body - kivacrxhcu

Test Comment - gpsxv


text:
Test Issue - hyruf

Test Body - qigzuodkmi

Test Comment - btmoo


text:
Test Issue - qwmpd

Test Body - txhpraaqlt

Test Comment - ofdkt


text:
Test Issue - flgnq

Test Body - bnaadwnpsz

Test Comment - quroz


text:
Test Issue - jdwrj

Test Body - rblvccktgt

Test Comment - fztlv


text:
Test Issue - irioh

Test Body - zvoxzrtfgc

Test Comment - mrmtq


text:
Test Issue - zkjaf

Test Body - zddyxbmiuj

Test Comment - qwogj


text:
Test Issue - srezu

Test Body - vmosfuasrb

Test Comment - cxqxu


text:
Test Issue - mwruv

Test Body - zngcwxpgvf

Test Comment - wdjtx


text:
Test Issue - grili

Test Body - vzrjsmdpos

Test Comment - gdmfp


text:
Test Issue - zaelp

Test Body - upxrfbmsmt

Test Comment - kmrdq


text:
Test Issue - rahfx

Test Body - qclvudreyx

Test Comment - etmdv


text:
Test Issue - vntfw

Test Body - wpsbwpaxnw

Test Comment - ljzwk


text:
Test Issue - hslvf

Test Body - hyiomcpuja

Test Comment - bhoxa


text:
Cleaned up Gergo/Georgi

Added pages for Georgi and cleaned up the Gergo page.

Not sure how active this repo is, so tagging @skullydazed @drashna @noroadsleft for visibility

Sorry for missing the notification @noroadsleft . Should be good now :)

#response_container_BBPPID{font-family: initial; font-size:initial; color: initial;}  Thanks @noroadsleft ! We good to merge now?                                                                                From: notifications@github.comSent: April 24, 2019 10:53 PMTo: qmk.fm@noreply.github.comReply to: reply@reply.github.comCc: jeremythegeek@gmail.com; author@noreply.github.comSubject: Re: [qmk/qmk.fm] Cleaned up Gergo/Georgi (#46)  @noroadsleft approved this pull request.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Fixed it up :D

Thanks!

authors: drashna germ