text:
Setuptools pulls down incompatible version of package with develop

Context: IPython just released 6.0rc1 on to PyPI, which is only compatible with 3.3+. pip install ipython on python 2.7 pulls down IPython 5.3.0 as you'd expect when invoked as pip install ipython. However, setuptools instead pulls down IPython 6.0 leading to an installation error.
Minimally reproducible example:
# setup.py
from setuptools import setup

setup(
    name='example',
    install_requires=['ipython'],
)

Outputs:
(env) $ python -c 'import pkg_resources; print pkg_resources.get_distribution("setuptools")'
setuptools 34.4.1
(env) $ python setup.py develop
running develop
running egg_info
writing requirements to example.egg-info/requires.txt
writing example.egg-info/PKG-INFO
writing top-level names to example.egg-info/top_level.txt
writing dependency_links to example.egg-info/dependency_links.txt
reading manifest file 'example.egg-info/SOURCES.txt'
writing manifest file 'example.egg-info/SOURCES.txt'
running build_ext
Creating /Users/jtratner/env/lib/python2.7/site-packages/example.egg-link (link to .)
example 0.0.0 is already the active version in easy-install.pth

Installed /Users/jtratner
Processing dependencies for example==0.0.0
Searching for ipython
Reading https://pypi.python.org/simple/ipython/
Downloading https://pypi.python.org/packages/76/46/c505c48d264715136edde1a1960f9158133e34c03bbfe4c955dbc5948ce4/ipython-6.0.0rc1.tar.gz#md5=e57acb5fabd9f18b739de35a1f00eac5
Best match: ipython 6.0.0rc1
Processing ipython-6.0.0rc1.tar.gz
Writing /var/folders/h2/64h07zpd7576xz6wcq8jdzrw0000gp/T/easy_install-BGbWO9/ipython-6.0.0rc1/setup.cfg
Running ipython-6.0.0rc1/setup.py -q bdist_egg --dist-dir /var/folders/h2/64h07zpd7576xz6wcq8jdzrw0000gp/T/easy_install-BGbWO9/ipython-6.0.0rc1/egg-dist-tmp-zb3BA7

IPython 6.0+ does not support Python 2.6, 2.7, 3.0, 3.1, or 3.2.
When using Python 2.7, please install IPython 5.x LTS Long Term Support version.
Beginning with IPython 6.0, Python 3.3 and above is required.

See IPython `README.rst` file for more information:

    https://github.com/ipython/ipython/blob/master/README.rst

Python sys.version_info(major=2, minor=7, micro=9, releaselevel='final', serial=0) detected.

error: Setup script exited with 1

and on the same system pip does the "right" thing
(env) $ pip install --no-cache-dir -i https://pypi.python.org/simple ipython
# snip...
Successfully installed appnope-0.1.0 backports.shutil-get-terminal-size-1.0.0 decorator-4.0.11 enum34-1.1.6 ipython-5.3.0 ipython-genutils-0.2.0 pathlib2-2.2.1 pexpect-4.2.1 pickleshare-0.7.4 prompt-toolkit-1.0.14 ptyprocess-0.5.1 pygments-2.2.0 scandir-1.5 simplegeneric-0.8.1 traitlets-4.3.2 wcwidth-0.1.7
(env) $ pip uninstall ipython

I've tested and this happens on OSX and a centos6 box I have access to.

(there's a secondary issue here that I think setuptools should not be pulling down an rc release at all - but that may be because 6.0.0rc1 is not a valid release candidate description)

easy_install doesn't exclude pre and post release versions as pip does. You should probably just use pip install -e instead of setup.py develop.

Okay - but to be clear, the real problem is that it's installing an
incompatible package given the current python version. Is that expected?
On Tue, Apr 11, 2017 at 6:05 AM Jason R. Coombs notifications@github.com
wrote:

easy_install doesn't exclude pre and post release versions as pip does.
You should probably just use pip install -e instead of setup.py develop.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pypa/setuptools/issues/1009#issuecomment-293254466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABhjq6gVMaCUZKOaqDHyofB4McY3wsPrks5ru3qDgaJpZM4M5opJ
.

Yes, I think that's expected. Support for packages to declare which Python versions are supported is fairly new. I'm not even aware of any feature in pip to restrict packages based on Python version.
Indeed:
vagrant@trusty:~$ python2.7 -m pip install --pre ipython
Downloading/unpacking ipython
  Downloading ipython-6.0.0rc1.tar.gz (5.1MB): 5.1MB downloaded
  Running setup.py (path:/tmp/pip_build_vagrant/ipython/setup.py) egg_info for package ipython

    IPython 6.0+ does not support Python 2.6, 2.7, 3.0, 3.1, or 3.2.
    When using Python 2.7, please install IPython 5.x LTS Long Term Support version.
    Beginning with IPython 6.0, Python 3.3 and above is required.

    See IPython `README.rst` file for more information:

        https://github.com/ipython/ipython/blob/master/README.rst

    Python sys.version_info(major=2, minor=7, micro=6, releaselevel='final', serial=0) detected.

    Complete output from command python setup.py egg_info:

IPython 6.0+ does not support Python 2.6, 2.7, 3.0, 3.1, or 3.2.

When using Python 2.7, please install IPython 5.x LTS Long Term Support version.

Beginning with IPython 6.0, Python 3.3 and above is required.

See IPython `README.rst` file for more information:

    https://github.com/ipython/ipython/blob/master/README.rst

Python sys.version_info(major=2, minor=7, micro=6, releaselevel='final', serial=0) detected.

----------------------------------------
Cleaning up...
Command python setup.py egg_info failed with error code 1 in /tmp/pip_build_vagrant/ipython
Storing debug log for failure in /home/vagrant/.pip/pip.log

The only reason pip doesn't normally install 6.0rc1 by default is because it's a pre-release version. When 6.0 is released, pip will fail to install it also on Python 2.
Eventually, pip and/or warehouse will probably add support to read the metadata for the package and filter out non-viable versions. I'm not sure which package if any will do that. However, easy_install, being mostly deprecated, will not get support for these new features.

Support for packages to declare which Python versions are supported is fairly new. I'm not even aware of any feature in pip to restrict packages based on Python version.

That was covered by https://github.com/pypa/pip/pull/3877 writen in part by me, and explicitly to cover this use case. So it should not be wontfix as it is also one of the main reason to migrate to pip9.  We even send PR to PyPI legacy and patch to warehouse to support this.

Also can you please reopen ?

If the issue is addressed in pip, why would we re-open this issue in setuptools?

Eventually, pip and/or warehouse will probably add support to read the metadata for the package and filter out non-viable versions.

For the record, like @Carreau pointed out, such support was added in pip 9.
(tmp-f58eb2604fd386e)$ python -V
Python 3.4.6
(tmp-f58eb2604fd386e)$ pip install gidgethub
Collecting gidgethub
  Could not find a version that satisfies the requirement gidgethub (from versions: )
No matching distribution found for gidgethub
(tmp-fb86749fd437f6b)$ pip install https://pypi.python.org/packages/cc/64/75d5ad78abd12eb66a4b46eaeeff255fd4b88428c99ee118444c809c6a8c/gidgethub-2.0.0-py3-none-any.whl
Collecting gidgethub==2.0.0 from https://pypi.python.org/packages/cc/64/75d5ad78abd12eb66a4b46eaeeff255fd4b88428c99ee118444c809c6a8c/gidgethub-2.0.0-py3-none-any.whl
  Using cached gidgethub-2.0.0-py3-none-any.whl
gidgethub requires Python '>=3.6.0' but the running Python is 3.4.6

It seem your pip is out of date, as pip 9.0.1 seem to not behave as in your screenshot.
MacBook-Pro-4:~ bussonniermatthias$ python2 -m pip --version
pip 9.0.1 from /usr/local/lib/python2.7/site-packages (python 2.7)
MacBook-Pro-4:~ bussonniermatthias$ python2 -m pip install ipython --pre --upgrade
Collecting ipython
  Using cached ipython-5.3.0-py2-none-any.whl

So pip does the right thing.

Indeed. I was testing with stock pip on Ubuntu Trusty.

I'll add a line in the warning message that warn user that pip may be out of date.

I observe the same issue with setuptools-41.0.1 on Windows (but not on Linux). Usecase:
a project depends on numpy>=1.13.0. On a Windows machine with Python 2.7 and pip==19.1.1, setuptools attempts to pull an incompatible package   numpy==1.17.0rc1, which requires Python 3.5. pip install picks up correct version. I assume this bug is still correctly closed as WAI.

authors: Carreau jaraco jtratner tvalentyn xavfernandez

repo: pypa/setuptools


text:
nuke: write render node skipped with crop

Description
After we had included Crop node in Render write node group The PreCollect Write Node is now taking Crop instead of Write node and adding it into context as write node. This is causing two known problems:

using it in label of instance
blocking rendering on farm as missing colorspace knob on Crop node.

/cib

source: gharchive/issue

repo: pypeclub/OpenPype

license: MIT

license_type: permissive

license_source: github-api


text:
Trusted Publisher: Need help uploading packages to pypi.

Describe the bug

I tried to upload a package to pypi with the "Trusted Publisher" method via Github Action.
Here are the details of the publisher configuration in pypi:
Publisher name: GitHub
Workflow: python-publish.yml
Owner: aprilahijriyan
Repository: fastapi-supabase
Environment: pypi

The log from github action says that the package name is already in use (see https://github.com/aprilahijriyan/fastapi-supabase/actions/runs/11986191403/job/33419212456)
Expected behavior

My package should have been successfully uploaded, since I checked that the package name I was using was not in use on pypi.org.
To Reproduce

My Platform

Additional context

Hi, based on your error message, it looks like you're trying to use a previously used filename. I can see that the project had a previous owner that uploaded fastapi_supabase-0.1.0-py3-none-any.whl and fastapi_supabase-0.1.0.tar.gz before deleting the project.
You should change the version number of your release and retry.

Thank you @di , now it's uploaded successfully!

authors: aprilahijriyan di

repo: pypi/warehouse


text:
use full numpy test suite

Add the 'full' argument to testing to run the slow tests

Hey @serge-sans-paille, the pythran tests started failing here. Do you see the problem? I see warnings, are they being interpreted as errors? For reference: this repo is a canary for testing latest PyPy + latest pythran. It runs off a weekly cron job or whenever a PR is made. The history of CI runs is here, you can see it usually passes.

SystemError: initialization of XXX raised unreported exception

Nope, that rings no bell. That's Pythran being used from Cython from Pypy, that's a bit bold ;-) Did you update the cython dep somehow?

source: gharchive/pull-request

authors: mattip serge-sans-paille

repo: pypy/binary-testing


text:
Feature/customized encoder

Add customized :encoder support for riemann-kafka/producer
This PR are supposed to be merged after https://github.com/pyr/riemann-kafka/pull/7.

This is great, I'll release this new version shortly, thanks again!

@pyr Thank you very much for merging my pull requests.
Also thank you for all your effort on open source projects (collectd, riemann, etc.). We gain a lot from them :smiley:

authors: liuweichu pyr weichuliu

repo: pyr/riemann-kafka

license: isc

license_source: bigquery


text:
Builds will Run Multiple Times for the Same Artifact

Steps taken/Steps to reproduce
./target/debug/pyrsia build maven --gav commons-codec:commons-codec:1.15
then a second
./target/debug/pyrsia build maven --gav commons-codec:commons-codec:1.15
And it will happily accept a second build of the same thing.
Expected Behavior
Should not build the same artifact a second time.
Experienced Instance of the bug
Rust: rustc 1.63.0 (4b91a6ea7 2022-08-08)
Operating System: mac 12.5.1
Pyrsia version: Built off main (pre 0.2)

With current code, it is still the case:

nodeA (authorized)
pyrsia points to nodeB
launching almost from terminal one:

./pyrsia build docker --image alpine:3.16.2
Build request successfully handled. Build with ID 1 has been started.

and almost at the same time from terminal two:
./pyrsia build docker --image alpine:3.16.2
Build request successfully handled. Build with ID 2 has been started.

Builds twice and produces 8 artifacts in node A (4 per build).
nodeB logs:
// build 1
pyrsia::artifact_service::service    > Request build of Docker "alpine:3.16.2"
pyrsia::network::build_protocol      > Write BuildRequest: Docker: alpine:3.16.2
pyrsia::network::event_loop          > RequestResponseMessage::Response RequestId(1)
pyrsia_registry                      > 127.0.0.1:52365 "POST /build/docker HTTP/1.1" 200 "-" "-" 9.9045ms
// build 2
pyrsia::artifact_service::service    > Request build of Docker "alpine:3.16.2"
pyrsia::network::build_protocol      > Write BuildRequest: Docker: alpine:3.16.2
pyrsia::network::event_loop          > RequestResponseMessage::Response RequestId(2)
pyrsia_registry                      > 127.0.0.1:52372 "POST /build/docker HTTP/1.1" 200 "-" "-" 4.351583ms
...
// build 1:
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 9a712dde-6285-4d6f-9f93-bcd7e5a2ecb8
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 51d2d4fb-fdeb-4db3-b91f-b82eeae32232
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 8924d813-cac9-4a10-a64b-dd0d3916de47
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 43fc98a9-4db7-40ff-9ede-86b554f474b1
// build 2:
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 080a08e2-da71-404d-84e8-59b49a9d020c
pyrsia::transparency_log::log        > Transparency log inserted into database with id: b58a62b4-4e96-4b56-9ddd-57e3a382fecc
pyrsia::transparency_log::log        > Transparency log inserted into database with id: aece49d2-4156-48ae-bc9c-0595ebc18fca
pyrsia::transparency_log::log        > Transparency log inserted into database with id: 7397c6db-e0d7-46f1-8e7b-81c5abf51642

this was fixed in #1199

authors: efrisch erwin1 jperedadnr

repo: pyrsia/pyrsia


text:
(docs, bug) mgwr api change not reflected in the docs

see https://github.com/pysal/mgwr/pull/55

addressed via https://github.com/pysal/pysal/pull/1107

repo: pysal/pysal


text:
tips in geoplot only works when column is passed

The tips argument in geoplot, which controls the list of attributes to be displayed when hover=True only works when col is passed. It'd be useful to have it work even when only geometries are being displayed (and hence col=None). This can be seen in L.825, where tips are only acted upon when col exists.

Hey can I take this one up as my hopefully to be "first" contribution to the group?

@djokester have at it, all pull requests are much appreciated.

Can you give me just a little broader description of what is required of me here?

I suggest you get familiar with how geoplot works in general. A good starting point as a user level is this notebook. There you'll see that, when you plot to the bokeh backend, there's an option to have attributes from the DataFrame display as you hover over the choropleth. That works when you have a choropleth (a variable being displayed with a color scheme). However, that option does not work when you simply plot the geometries. It'd be cool if it did. That's this ticket. Does it make sense?

@darribas Yes!

@darribas but dosen't col provide the key and entries that should be displayed when hover = True.
If col is empty. What should we display on hover.

@kris-singh col provides the column in the geotable to be used for the choropleth. What appears as you hover should be controlled by tips. I think that'd make the hover functionality much more flexible. If tips is not modified and col is passed, we can have the current default of showing that.

A PR addressing this issue was merged. Can this be closed?

Yes, this can be closed - thanks for flagging this.

authors: darribas djokester kris-singh rgommers sjsrey


text:
mo_coeff are the same for RHF and CASCI calculation even when mc.natorb = True

Hello,
I have tested CASCI calculations with different combinations of the mc.canonicalization and mc.natorb options (mc is a CASCI object). I compared mo_coeff from RHF and CASCI calculations. As far as I understand, mo_coeff of CASCI calculations for core, active, and virtual orbitals can be changed depending on the options. However, when mc.natorb = True and mc.canonicalization = False, mo_coeff are the same for RHF and CASCI calculations. This seemed weird since I was expecting that mo_coeff for the active orbitals should be changed. Did I miss or misunderstand something?
I used PySCF ver. 1.7.0, and the script I used is as below:
import numpy as np
import pyscf
from pyscf import scf, gto, mcscf, mrpt
Test for a simple N2 molecule
mol = gto.M(
atom = 'N 0 0 0; N 0 0 15.0',
spin = 0)
mol.basis = 'ccpvdz'
Run RHF calculation
myhf = scf.RHF(mol)
myhf.kernel()
Run CASCI calculation.
num_act_e = 4
num_act_orb = 4
mc = mcscf.CASCI(myhf, num_act_orb, num_act_e)
For easy comparison between HF and CASCI orbitals, I chosen active orbitals above core orbitals.
num_core_orb = mc.ncore
cas_list = np.linspace(num_core_orb, num_core_orb+num_act_orb-1, num_act_orb, dtype=int)
mo = mc.sort_mo(cas_list, base=0)
mc.canonicalization = False
mc.natorb = True
mc.kernel(mo);
differences of the mo_coeff from the HF and CASCI are checked
core_diff = np.sum(np.abs(myhf.mo_coeff[:, :num_core_orb] - mc.mo_coeff[:, :num_core_orb]))
act_diff = np.sum(np.abs(myhf.mo_coeff[:, num_core_orb:num_core_orb+num_act_orb] - mc.mo_coeff[:, num_core_orb:num_core_orb+num_act_orb]))
virt_diff = np.sum(np.abs(myhf.mo_coeff[:, num_core_orb+num_act_orb:] - mc.mo_coeff[:, num_core_orb+num_act_orb:]))
print(f"core orb diff = {core_diff}")
print(f"active orb diff = {act_diff}")
print(f"virtual orb diff = {virt_diff}")

Currently mc.natorb option is only used if mc.canonicalization = True. I also find it a bit confusing.
You should get what you want if you use mc.cas_natorb_() to set mc.mo_coeff to natural orbitals.
You also can get them with nat_mo_coeff, nat_ci, nat_occ = mc.cas_natorb() or
nat_mo_coeff, nat_ci, nat_occ = mcscf.addons.cas_natorb(mc) functipns.

Thank you, bogdanoff. I can get what I want as you suggested.

Currently mc.natorb option is only used if mc.canonicalization = True. I also find it a bit confusing.
You should get what you want if you use mc.cas_natorb_() to set mc.mo_coeff to natural orbitals.
You also can get them with nat_mo_coeff, nat_ci, nat_occ = mc.cas_natorb() or
nat_mo_coeff, nat_ci, nat_occ = mcscf.addons.cas_natorb(mc) functipns.

For some historical reason, the three attributes natorb, sorting_mo_energy, and canonicalization were introduced to transform the orbitals in different scenarios. I was pretty struggling with the treatment of them.
Generally, without enabling canonicalization, I don't want the orbitals to be changed unexpectedly.

@sunqm,
I think in the most codes inactive and virtual orbitals are always canonicalized, and the options of canonical or natural orbitals exist for active space only.
I appreciate the importance of keeping orbitals unchanged for DMRG solver.
But initially I was expecting that natorb = True would give me the natural orbitals in active space.
Now it doesn't matter anymore :) .

authors: bogdanoff sunqm wjeong2020

repo: pyscf/pyscf


text:
Unify duplicate implementation of Scone

What?
There were two implementations of Scone by challenge participants.
If they are indeed the same implementation, we need to merge them into 3 files:

scone_layer.py
test_scone_layer.py
scone_train.ipynb

If they are different implementations, we need to check if one of them can be deleted.
Possible reasons to delete:

not faithful to the research paper introducing Scone,
incomplete implementation.

If we decide to keep both of them, the file names and docstrings should be updated to highlight their difference.
Why?
Because it is confusing to have two implementations of Scone without knowing their difference.
Where?
The files to modify are:

topomodelx/nn/simplicial/scone_layer.py
topomodelx/nn/simplicial/scone_layer_bis.py
test/nn/simplicial/test_scone_layer.py
test/nn/simplicial/test_scone_layer_bis.py
tutorials/simplicial/tscone_train.ipynb
tutorials/simplicial/tscone_train_bis.ipynb

How?
See for example how the duplicate SCN and SCN2 has been solved and the use of the "See Also" sections in their docstrings.

TODO: Correct the text in the intro of the scone_bis.ipynb, that currently mentions HSN.

See PR  #188

authors: michaelschaub ninamiolane

repo: pyt-team/TopoModelX


text:
Help channel cross-post filter

Users posting the same question in all the help channels at once is a problem that can easily be solved by the bot. Thus, let's add a filter to catch and notify those users.
Implementation details:

[ ] Cache one message-user pair per help channel (the latest sent message)
[ ] Add a filter that checks if the message and user matches any in the cache
[ ] Remove all but one message, then automute the user for a short duration
[ ] Notify the user about posting the same question to multiple help channels

If the question spans across multiple messages ( For example, message 1 2 and 3 ), would this means we would only cache the 3rd message? What if the user goes to another channel and paste only the 1st and 2nd messages and/or copy paste everything into a new message ( 4th ) and post that 4th in another channel?
In this case would checking for contents and check for similarities across most recent messages ( most recent 3 ) be a better case? For example above 70% from difflib?

This is irrelevant with our new help channel system.

authors: Den4200 ikuyarihS kosayoda

repo: python-discord/bot


text:
Prometheus configuration auto-reloading

I have created a repository, owl-corp/inotify-base, which is a
Debian slim image with some added niceities to trigger a script run on changes
to a given path.
We then have a script in this repository to reload Prometheus using the
management API and notify in the Discord channel if this has succeeded or not.
I have also enabled scraping of the Prometheus server and also added an alert
for failed config reloads to integrate it into our existing alerting pipeline.
Makes progress on #266, there is still no auto-deployment of content from this repository.

All review comments have been addressed in the force push.

repo: python-discord/infra


text:
Python Cheat Sheet Command

Description
This is just like tldr pages. It is a really good resource and I use them regularly either when trying to help others or wanna look up something.
Screenshots

Proposed Implementation

https://cht.sh/
It supports a number of languages, so we can default it to python.

Would you like to implement this yourself?

[x] I'd like to implement this feature myself
[ ] Anyone can implement this feature

@Shivansh-007 I'd like to see this get implemented. Would you like to work on it?

@Shivansh-007 I'd like to see this get implemented. Would you like to work on it?

repo: python-discord/sir-lancebot


text:
Explanation of get_hyperplane_value

Hi, I find your tutorials on SVM very helpful but I do not understand the get_hyperplane_value method in svm_tests.py. May I have an explanation of it? Thank you!

Hi, someone asked the same question in the comments below the video. you might want to have a look at this. i will post the same answer here:
Yes the important thing is the line equation in the so called normal form x0w0 + x1w1 = b (see https://sites.math.washington.edu/~king/coursedir/m445w04/notes/vector/equations.html). We want to solve this for x1 (probably the variable names are confusing here: x0 is our x axis, and x1, is our y axis). Then just take some points on the x axis, and use the equation to get the corresponding y points, and pass these points to matplotlib...

authors: Redcxx python-engineer

repo: python-engineer/MLfromscratch


text:
to_atomic raises MemoryError when receiving a str

Maybe we can do some type checking inside to_atomic, and raise TypeErrors?

@lalvarezguillen if I'm not mistaken this was already fixed on the upstream project (https://github.com/monero-ecosystem/monero-python/commit/a7c8579b139c75e20472f5aea36aa7ed6cb17b03). Perhaps we should sync the latest changes into our fork.

we should definitely sync

authors: dethos lalvarezguillen

repo: python-monero/monero-python


text:
[Feature]: Required Access to resource's OpenAPI attributes whose validation is failing

Suggested Behavior
Hello, I am currently using OpenAPI-core with my Flask app and I am customizing validation error responses as per following comment.
The issue I am facing is that there are some fields in request which holds sensitive information, e.g credentials, Auth-tokens.
When the validation fails on these fields we get an error string which includes value of these sensitive fields.
E.g consider following response,
{
    "errors": [
        {
            "class": "<class 'openapi_core.validation.schemas.exceptions.InvalidSchemaValue'>",
            "status": 400,
            "title": "Value {'flag': 'MyPassword1234'} not valid for schema of type object: (<ValidationError: \"'MyPassword1234' is too short\">,)"
        }
    ]
}

As we can see in above example, the password of user is exposed as part of response.
I do want to add validation for these fields however I don't want the values of these fields to be send as a response.
For that I checked whether there is a flag in OpenAPI which marks a field as sensitive and found this issue which suggested usingx-pii: true field in the yaml
Also I used FlaskOpenAPIErrorsHandler to fetch the error object and see if we get details of the flags which are set for the field where the validation failed.
Following is my Flask code
#!/usr/bin/python3
"""Test server."""

from flask import Flask, request, jsonify
from openapi_core.contrib.flask.decorators import FlaskOpenAPIViewDecorator, FlaskOpenAPIErrorsHandler
from openapi_core import Spec

# Custom Error Handler block
class ErrorHandler(FlaskOpenAPIErrorsHandler):
    """"Custom Error Handler"""
    def handle(self, errors:list):
        return jsonify({
            "causedBy" : [self.handle_error(error) for error in errors]
        }), self.OPENAPI_ERROR_STATUS.get(errors[0].__class__, 400)

    def handle_error(self, error):
        """
        Converts error object into error string message

        :param error: Error object which stores exception message
        :type error: Exception object
        :return: Error message string corresponding to error object
        :rtype: str
        """
        if error.__cause__ is not None:
            error = error.__cause__
        # TODO: If the field in error object has x-pii: true, return a generic string which does not include it's value
        if not (hasattr(error, "value") and hasattr(error, "type") and hasattr(error, "schema_errors")):
            return str(error)
        return f"Value(s) {error.value} not valid for schema of type {error.type} errors: {', '.join([err.message for err in error.schema_errors])}"

SPEC = "test.yaml"
obj = ErrorHandler()
openapi = FlaskOpenAPIViewDecorator.from_spec(Spec.from_file_path(SPEC), openapi_errors_handler=obj)

app = Flask(__name__)

@app.route("/test", methods=["POST"])
@openapi
def read_permission():
    """Test function"""
    return jsonify({
                    "flag stri_normal_json": request.json.get("flag", 1)
                })

if __name__ == "__main__":
    app.run(host="0.0.0.0", port=345, debug=True)

And following is the Yaml file
openapi: '3.0.2'
info:
  title: Test Title
  version: '1.0'
servers:
  - url: http://localhost:345/
paths:
  /test:
    post:
      requestBody:
        content:
          application/json:
            schema:
              type: object
              required:
                - flag
              properties:
                flag:
                  x-pii: true
                  type: string
                  pattern: "^[\\w.-]*$"
                  minLength: 6
                  maxLength: 20
      responses:
        200:
          description: Sample response
          content:
            application/json:
              schema:
                type: object
                properties:
                  flag stri_json:
                    type: string
                    minLength: 6
                    maxLength: 20

Please check the TODO comment inside handle_error method.
If the validation of field flag fails and if we have access to attributes of flag yaml properties e.g below properties
                flag:
                  x-pii: true
                  type: string
                  pattern: "^[\\w.-]*$"
                  minLength: 6
                  maxLength: 20

Then we would be able to have better customization and control over the response message.
Why is this needed?
Many times we need to have better control over the response generated on the failure of validation.
Current error messages generated by openapi-core exposes the field contents as part of response which makes openapi-core useless if there are sensitive fields in request body which needs to be validated.1
Having access to OpenAPI attributes of any field would be very helpful in generating custom response messages and would help us to perform validation on fields with sensitive data and also not expose the sensitive information to the response.
References
https://github.com/OAI/OpenAPI-Specification/issues/2190
Would you like to implement a feature?
Yes

Hi @rohan-97
There's not need for extension; it's a use case for a password format defined in OpenAPI 3.x
I would see this as a format unmarshaller which returns extended string type (similar to SecretStr in pydantic) and converting to string by default will give us masked string.
As a workaround for now I would catch/override InvalidSchemaValueexception.

Hello @p1c2u ,
I think the control won't hit format unmarshaller.
However I was able to get the resource's openapi attributes by checking attributes of error.schema_errors objects.
schema_errors objects had following attributes
schema: provides detail about OpenAPI attributes
validator: Provides the attributesname on which the validation failed e.g minlength, pattern
absolute_path: path of field name in entire OpenAPI schema
Using above attribute error.schema_errors[0].schema,  I am able to query attributes of the validation which is failing.

repo: python-openapi/openapi-core


text:
Extras output differs from 1.1.15

Hello,
Upon attempting to upgrade Poetry from 1.1.15 to 1.2.0, I noticed the following change in behaviour.
poetry export now includes extra definitions, previously these were expanded.
With this config (reduced for simplicity)
[tool.poetry.dependencies]
python = "~3.10"
connexion = { version = "^2.4.1", extras = ["flask", "swagger-ui"] }

Before - 1.1.15:
pipx run poetry==1.1.15 export --without-hashes -f requirements.txt -o ./requirements.txt
attrs==22.1.0; python_version >= "3.7"
certifi==2022.6.15; python_version >= "3.7" and python_version < "4"
charset-normalizer==2.1.1; python_version >= "3.7" and python_version < "4" and python_full_version >= "3.6.0"
click==8.1.3; python_version >= "3.7"
clickclick==20.10.2; python_version >= "3.6"
colorama==0.4.5; python_version >= "3.7" and python_full_version < "3.0.0" and platform_system == "Windows" or platform_system == "Windows" and python_version >= "3.7" and python_full_version >= "3.5.0"
connexion==2.14.1; python_version >= "3.6"
flask==2.2.2; python_version >= "3.7"
idna==3.3; python_version >= "3.7" and python_version < "4"
inflection==0.5.1; python_version >= "3.6"
itsdangerous==2.1.2; python_version >= "3.7"
jinja2==3.1.2; python_version >= "3.7"
jsonschema==4.15.0; python_version >= "3.7"
markupsafe==2.1.1; python_version >= "3.7"
packaging==21.3; python_version >= "3.6"
pyparsing==3.0.9; python_full_version >= "3.6.8" and python_version >= "3.6"
pyrsistent==0.18.1; python_version >= "3.7"
pyyaml==6.0; python_version >= "3.6"
requests==2.28.1; python_version >= "3.7" and python_version < "4"
swagger-ui-bundle==0.0.9; python_version >= "3.6"
urllib3==1.26.12; python_version >= "3.7" and python_full_version < "3.0.0" and python_version < "4" or python_full_version >= "3.6.0" and python_version < "4" and python_version >= "3.7"
werkzeug==2.2.2; python_version >= "3.7"

After - 1.2.0:
pipx run poetry==1.2.0 export --without-hashes -f requirements.txt -o ./requirements.txt
attrs==22.1.0 ; python_version >= "3.10" and python_version < "3.11"
certifi==2022.6.15 ; python_version >= "3.10" and python_version < "3.11"
charset-normalizer==2.1.1 ; python_version >= "3.10" and python_version < "3.11"
click==8.1.3 ; python_version >= "3.10" and python_version < "3.11"
clickclick==20.10.2 ; python_version >= "3.10" and python_version < "3.11"
colorama==0.4.5 ; python_version >= "3.10" and python_version < "3.11" and platform_system == "Windows"
connexion[flask,swagger-ui]==2.14.1 ; python_version >= "3.10" and python_version < "3.11"
flask==2.2.2 ; python_version >= "3.10" and python_version < "3.11"
idna==3.3 ; python_version >= "3.10" and python_version < "3.11"
inflection==0.5.1 ; python_version >= "3.10" and python_version < "3.11"
itsdangerous==2.1.2 ; python_version >= "3.10" and python_version < "3.11"
jinja2==3.1.2 ; python_version >= "3.10" and python_version < "3.11"
jsonschema==4.15.0 ; python_version >= "3.10" and python_version < "3.11"
markupsafe==2.1.1 ; python_version >= "3.10" and python_version < "3.11"
packaging==21.3 ; python_version >= "3.10" and python_version < "3.11"
pyparsing==3.0.9 ; python_version >= "3.10" and python_version < "3.11"
pyrsistent==0.18.1 ; python_version >= "3.10" and python_version < "3.11"
pyyaml==6.0 ; python_version >= "3.10" and python_version < "3.11"
requests==2.28.1 ; python_version >= "3.10" and python_version < "3.11"
swagger-ui-bundle==0.0.9 ; python_version >= "3.10" and python_version < "3.11"
urllib3==1.26.12 ; python_version >= "3.10" and python_version < "3.11"
werkzeug==2.2.2 ; python_version >= "3.10" and python_version < "3.11"

As the dependencies are already expanded to include extras (connexion[flask,swagger-ui]), it seems redundant to include the extras in the end requirements.txt.
This breaks some existing parsing we had to make the output of poetry export compatible with a given constraints file.

It is correct and necessary to include extras explicitly because of eg https://github.com/python-poetry/poetry/issues/5537, else pip install of the output requirements.txt fails per that issue.
So I think this is going to be wont-fix, and you'll need to update your parsing - sorry

Thanks for the clarification

@dimbleby in that case, how hard would it be to support a constraints export format? As extras are not supported in constraints files, and using a requirements.txt file output by poetry 1.2.0 now results in
ERROR: Constraints cannot have extras

I've never looked into constraints format, if the only meaningful difference is omitting extras then it can't be that hard, you'd think.
on the other hand it might be even easier for you just to sed the [extras] away...

authors: Limess NickG123 dimbleby

repo: python-poetry/poetry-plugin-export


text:
A couple of weird things I have found.

Howdy! Sorry you're having trouble. To expedite your experience,
provide some basics for me:
Operating system:
Python version: Python 3.7.3
Black version: black, version 19.3b0
Does also happen on master: Yes
When I run $ black *

Mishap 1:
My requirements.txt which contains opencv-python this is getting updated to opencv - python.

Mishap 2:
A dictionary like config.settings["foo"]["bar"]["baz"] = 1 is getting converted to:

config.settings["foo"]["bar"][
    "baz"
] = 1

even within the max line.

For your first problem, you should probably run black . instead, so Black runs only on Python files, not files that aren't Python but happen to be parseable as such.

For your second problem, I cannot reproduce it locally with the same Python and Black 19.3b0 or with black.now.sh (also 19.3b0).
What config settings do you have?

I can reproduce "Mishap 2" using line length 30:
black.now.sh
But this is probably not a very typical setting.

@robin-bloehm-mck what do you prefer Black to do in that case?

authors: JelleZijlstra hugovk maxisme robin-bloehm-mck zsol

repo: python/black


text:
Fixes for diegorusso-aarch64-bigmem

Follow-up to #546

Get the current time when a build is requested, rather than when the config is first loaded
Return a Deferred from nextBuild. By my reading of the nextBuild and Deferred docs, this is the way to do it.

checkconfig & reconfig works.

repo: python/buildmaster-config


text:
🛑 Dev Forum is down

In 5a258b6, Dev Forum (https://devforum.roblox.com/) was down:

HTTP code: 403
Response time: 214 ms

Resolved: Dev Forum is back up in ee05376 after 5 minutes.

repo: pythoniaweb/roblox-status


text:
🛑 Dev Forum is down

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

HTTP code: 403
Response time: 203 ms

Resolved: Dev Forum is back up in f9ba305 after 11 minutes.


text:
❓ [Question] How to save and load compiled model from torch-tensorrt

I am working on a Jetson Xavier NX16 and using torch-tensorrt.compile(model, "default", input, enable_optimization) every time I restart my program seems like it is just doing the same tedious task over and over.
Is there not a way for torch-tensorrt to load the serialized engine created by  torch_tensorrt.convert_method_to_trt_engine or is it only on the CXX backend API?
How would I go about saving and loading a compiled model?
Okay, so I used print(dir(comp_model)) and saw that the model had a save function. I tried using it and figured out after a friendly pop up, that I should load it with torch.jit.load and it works.
Is this an okay solution or are there some kind of insecurities with it?

yes, save the compiled module with torch.save or torch.jit.save

authors: MartinPedersenpp narendasan

repo: pytorch/TensorRT


text:
Update docs and CI for py 3.13 support

Enabling 3.13 CI for main/nightly, unsure if this needs more work for FTPython. Only enabled for Linux for now, as torch nightly does not yet have 3.13 for macos/windows
Fixes #1342
Changes
Update READMEs and CI to reflect 3.13 support

Test failure is unrelated, see https://github.com/pytorch/pytorch/issues/123649

repo: pytorch/data


text:
add padden_tokens so max_token_count is not exceeded

Fixes #788
Changes

Add count_padding argument to MaxTokenBucketizer

I'm unsure what the best name for the proposed argument is.


text:
Add decomposition for aten.native_batch_norm_backward op

This commit adds decomposition for the aten.native_batch_norm_backward
op.
Signed-Off-by: Gaurav Shukla gaurav@nod-labs.com

I think there are still some tests failing. For example, I don't believe push_back is a method on python lists  :) https://github.com/pytorch/functorch/pull/675/files#diff-8e71d16136c7deeb8104d8d5bb0dd794c208f38856f9ced3448ab02f3e34c43aR522
To run the tests, run
pytest test/test_ops.py::TestDecompositionOpInfoCUDA  -k batch_norm

and
pytest test/test_ops.py::TestDecompositionOpInfoCPU  -k batch_norm

@Chillee 'pytest test/test_ops.py::TestDecompositionOpInfoCPU  -k batch_norm` is always passing for me locally.
I do following steps to test:

pip install --pre torch  torchvision-f https://download.pytorch.org/whl/nightly/cpu/torch_nightly.html --upgrade
python setup.py install
pytest test/test_ops.py::TestDecompositionOpInfoCPU  -k batch_norm

Am I doing something wrong?

@Shukla-Gaurav Do you mean that it always passes, regardless of whether your decomposition is correct? Or are you asking why the decompositions are passing even though the CI fails?
If it's the second one, then there's some failures that are unrelated to you :)

@Shukla-Gaurav btw, is this mergeable?

@Chillee It looks like all the decompositions has been moved/removed?

@Shukla-Gaurav Yes, can you re-open this PR on upstream PyTorch?

Sure, will do that :)

authors: Chillee Shukla-Gaurav

repo: pytorch/functorch


text:
Remove the note of needing scipy in GoogleNet and Inception

📚 The doc issue
I think after merging #4256 We should update the docs to indicate scipy isn't needed. As I see in the code base models/googlenet.py and models/inception.py we use torch and not scipy.
Suggest a potential alternative/fix
Fix the note by removing the line regarding scipy.
Inception
https://github.com/pytorch/vision/blob/main/docs/source/models.rst#inception-v3
GoogleNet
https://github.com/pytorch/vision/blob/main/docs/source/models.rst#googlenet
It's a good first issue. Probably some new contributor would be interested.

Hi, I would be interested in helping with this

@Carlosbogo there was already a PR what wasn't linked to this ticket by a different user. :(

Oh no problem then, I'm glad that it got solved.

Solved? close issue.

Not yet. Once the linked PR is merged maintainers will.

authors: Carlosbogo WathikAhmed datumbox oke-aditya

repo: pytorch/vision


text:
torchvision 0.16 is not compatible with PT 1.13.1

🐛 Describe the bug
Sample code
from torchvision.datasets import mnist

Error:
    from torchvision.datasets import mnist
  File "/usr/local/lib/python3.10/site-packages/torchvision/__init__.py", line 6, in <module>
    from torchvision import _meta_registrations, datasets, io, models, ops, transforms, utils
  File "/usr/local/lib/python3.10/site-packages/torchvision/models/__init__.py", line 2, in <module>
    from .convnext import *
  File "/usr/local/lib/python3.10/site-packages/torchvision/models/convnext.py", line 8, in <module>
    from ..ops.misc import Conv2dNormActivation, Permute
  File "/usr/local/lib/python3.10/site-packages/torchvision/ops/__init__.py", line 23, in <module>
    from .poolers import MultiScaleRoIAlign
  File "/usr/local/lib/python3.10/site-packages/torchvision/ops/poolers.py", line 10, in <module>
    from .roi_align import roi_align
  File "/usr/local/lib/python3.10/site-packages/torchvision/ops/roi_align.py", line 4, in <module>
    import torch._dynamo
ModuleNotFoundError: No module named 'torch._dynamo'

This change which was released in 0.16 used _dynamo. _dynamo is part of the change which only released from PT 2.0.
Versions
torchvision=0.16
torch=1.13.1

Thanks for the report @ningziwen . That is expected, from our dependency table, you will either want to install pytorch 2.1 to use torchvision 0.16, or install torchvision 0.14 to install pytorch 1.13.
https://github.com/pytorch/vision#installation

authors: NicolasHug ningziwen


text:
Adding infrastructure for intake projects

This work came out of #20 which is on hiatus at the moment. But this part should get in so that people can start writing and testing intake projects. Plus starts the work of documenting what I'm doing #3.

Happy to insert a section about the pip+git format to get projects working off git master once the rest is ready...

@jlstevens I am done pushing if you want to just add your bit to this PR?

Sure!

@jsignell @jbednar I've pushed a section on the pip+git syntax. Happy to apply any suggestions for improvements you may have.

LGTM

authors: jlstevens jsignell

repo: pyviz-topics/examples


text:
DynamicMap's plot range does not get adjusted to stream

Hi,
I have a DynamicMap of Curve objects where each Curve is a timeseries of certain measurements (eg. Evaporation rate), and the kdims of the dynamic map is (lon, lat). So it's a dynamic map of timeseries at different locations in (lon,lat). As I manually change the parameters of the stream (ie lon, lat values), I noticed that my dynamic map's range doesn't get adjusted to the new timeseries at the new (lon,lat) location:
def get_tseries(xrd, varname, lon,lat):
    tseries = xrd[varname].sel(X=lon, Y=lat, method='nearest')
    return gv.Dataset(tseries, 'time', varname).to(hv.Curve)

LonLat = Stream.define('LonLat', X=22.35, Y=-11.45)
renamed_stream = LonLat().rename(X='lon', Y='lat')
# dmap_tseries = hv.DynamicMap(get_tseries, streams=[pt_stream.rename(X='lon', Y='lat')])
dmap_tseries = hv.DynamicMap(lambda lon,lat: get_tseries(xrd_ea, varnames[1], lon, lat),
                            streams=[renamed_stream])

display(dmap_tseries)

Send updated events:
for i,(lon,lat) in enumerate(zip(lons[::10],lats[::10])):
    if i>9:
        break
    print(i, "lon,lat: ", lon,lat)
    dmap_tseries.event(lon=lon, lat=lat)
    time.sleep(3)

Is this an expected behavior? I think it may be related to #3288. What would be a recommended way to set the ranges correctly?
Thank you!

I was able to resolve it by setting .opts(framewise=True). I'll close it.

repo: pyviz/holoviews


text:
[WIP] Tutorial PR

This is the branch on which we can write the new tutorial. I have written a very preliminary outline. in index.ipynb
Closes #174

NOTE: If you change the name of a notebook: you need to change the links in:

examples/tutorial/index.rst
doc/tutorial/index.rst
in any notebooks that link to it

@jbednar @philippjfr Managed to get the dev website built at this (incomplete) stage of the PR. Should we now merge to update the main public website with this work in progress?

I think we should update the main website so that people can start following the new instructions, but merging would be confusing as the PR isn't actually complete yet. Can't you just push a tag 'website' to this branch to make the main website update? I guess if we have to merge, then do, and open a new PR, but it would be nicer to stay in this PR and just keep tagging it whenever we are ready for a website update.

authors: jbednar jlstevens jsignell

repo: pyviz/holoviz


text:
chore: Try my GDrive again

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #
Test URLs:

Before: https://main--aem-boilerplate--pzrq.hlx.page/
After: https://chore-fstab--aem-boilerplate--pzrq.hlx.page/

No idea why @aem-code-sync is happy now, but that's good enough for me ✅ :shipit:

repo: pzrq/aem-boilerplate


text:
Correct schedule args handling

Implement correct schedule args handling. Add utils.py file for args processing. Small project structure changes and Dockerfile simplification

Thanks for your contribution!
I'm sorry I only see it now, will try to merge tomorrow morning, if I can verify that all works well on Docker and Kubernetes.

Thank you for your contribution! The local development workflow broke with this, I have moved app.py to the package __main__ and used relative imports. Merged manually with these changes. Thank you for the improvements!

Github didn't reference the commit here, but it is: https://github.com/q-m/scrapyd-k8s/commit/ea6af90abd6df40a84c842bac7349ccc97b3acd0

authors: dbealthy wvengen


text:
🛑 nitter.tiekoetter.com is down

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

HTTP code: 502
Response time: 929 ms

Resolved: nitter.tiekoetter.com is back up in 428c008 after 2 hours, 18 minutes.


text:
🛑 nitter.pw is down

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

HTTP code: 404
Response time: 1518 ms

Resolved: nitter.pw is back up in 52133f6.


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

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

HTTP code: 503
Response time: 337 ms

Resolved: nitter.us.projectsegfau.lt is back up in 1962184 after 41 minutes.


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

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

HTTP code: 503
Response time: 211 ms

Resolved: nitter.us.projectsegfau.lt is back up in 7ebae82 after 2 hours, 37 minutes.


text:
🛑 nitter.ktachibana.party is down

In 5614d64, nitter.ktachibana.party (https://nitter.ktachibana.party) was down:

HTTP code: 503
Response time: 370 ms

Resolved: nitter.ktachibana.party is back up in 925e8a4 after 4 hours, 11 minutes.


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

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

HTTP code: 503
Response time: 272 ms

Resolved: nitter.us.projectsegfau.lt is back up in c09d215 after 33 minutes.


text:
🛑 nitter.domain.glass is down

In 62ae318, nitter.domain.glass (https://nitter.domain.glass) was down:

HTTP code: 503
Response time: 501 ms

Resolved: nitter.domain.glass is back up in 1773507 after 6 hours, 45 minutes.


text:
🛑 notabird.site is down

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

HTTP code: 520
Response time: 77 ms

Resolved: notabird.site is back up in 1d49dc8.


text:
🛑 nitter.ir is down

In 71c899b, nitter.ir (https://nitter.ir) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nitter.ir is back up in 0c090f0.


text:
🛑 notabird.site is down

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

HTTP code: 520
Response time: 79 ms

Resolved: notabird.site is back up in e410e4b.


text:
🛑 notabird.site is down

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

HTTP code: 520
Response time: 80 ms

Resolved: notabird.site is back up in 40c849e after 15 minutes.


text:
🛑 nitter.lunar.icu is down

In c6aea8a, nitter.lunar.icu (https://nitter.lunar.icu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: nitter.lunar.icu is back up in 1737e62 after 5 minutes.


text:
Provide help for adding a new affiliation during customer selection

Feature request by @mGauder
During the offer creation, the addition of an affiliation to an existing customer is not intuitive.
Suggestion: Provide some hint/pointer how to add another affiliation to an existing customer during the offer creation process.

 Provide help for adding a new affiliation during customer selection #406

What exactly is intuitive (the placement? The naming?)
Where there suggestions on how to improve usability?

authors: KochTobi jenniferboedker sven1103


text:
Can't resolve PIA hostnames

Hey,
Sorry if this is such a dumb question.. but my networking background is slim to none. I'm new to the realm of docker and trying to become my own network admin.  I have this docker container running on my local server, but I can't resolve any of the PIA hostnames.  Could you shed some light on exactly what's meant by allow outgoing TCP 453 to 1.1.1.1, and what I need to do to configure that? Also, could you shed some light on the configuration of the proxy so I'm able to access this on my local network?

Hi there,
Allowing TCP 853 (not 453) for example is needed if you use your host system firewall such as iptables or ufw or another external router with complex options. If you just use a simple router with port forwarding, no need to worry about it!
You don't really need a proxy anymore I believe, just add your local network subnet (i. e. -e EXTRA_SUBNETS=192.168.1.0/24 or -e EXTRA_SUBNETS=192.168.1.6,192.168.1.8) to the container. All the readme instructions are then hopefully clear enough depending on what you want to achieve.. by the way what do you mean by access this on my local network? HTTP proxy? Published ports?

I  can confirm the proxy isn't necessary anymore.

Hey, thanks for the quick replies! Sorry, 853 yeah ;) So I haven't set up any iptables or ufw rules, but I'm running an OMV image (https://www.openmediavault.org/) - so they may have some things which are set by default.
Based on what you said it seems that I should be able to connect, so I'll check the default rules for iptables / ufw when I get home. For accessing this on my local network, I was talking about the HTTP proxy. I'd like to run other containers using this as a network, and then view their web pages on my local subnet (192.168.1.0:<port>)

Hey, thanks for the quick replies! Sorry, 853 yeah ;) So I haven't set up any iptables or ufw rules, but I'm running an OMV image (https://www.openmediavault.org/) - so they may have some things which are set by default. ...

@parker789
I'm also running a OMV image on my Odroid HC1.
When you launch the pia container you have to publish the ports you wanna use for de webinterface from the linked containers. For nzbget you should publish port 6789 (-p 6789:6789/tcp). When the pia container is running you can launch the nzbget container with** —net=container:pia**. When both containers are running you can connect to the nzbget webinterface with http://lan-ip:6789.
Kr.,
Frepke

@Frepke
Thanks for the tips! So that's what I've expected, but somehow I need to resolve this pia hostname issue first. Did you have any issues with OMV's default firewall rules and the dns resolver?

@Frepke  ...

@parker789
now you mention, it is possible that I've forwarded port 80 and/or port 443 in my router for your problem. I'm not 100% sure, but I think I had the same problem once.
Try to forward port 80 and if that doesn't help try port 443.
Good luck
Frepke

👍 will do - thanks

Note that the pia container and your other containers should be in the same Docker network for their names to get resolved properly, maybe that was your issue?

Note that the pia container and your other containers should be in the same Docker network for their names to get resolved properly, maybe that was your issue?

I thought parker789 meant that when running the pia container, the logfile gave an error while: Detecting IP addresses corresponding to ca-montreal.privateinternetaccess.com...
The container couldn't find IP addresses and will try again.
But maybe I wrong :(
kr.,
Frepke

Hi Frepke, where did you hear this? I cannot see this error mentioned by parker789 anywhere...

Hey, Frepke is correct. My docker container log gave me an error detecting the hostnames for my pia server.
As for the pia container and other containers being in the same Docker network, i'll check into that! I was able to run docker run --rm --network=container:pia alpine:3.10 wget -qO- https://ipinfo.io but this just returned my host's IP and not the VPN's

Hi Frepke, where did you hear this? I cannot see this error mentioned by parker789 anywhere...

@qdm12
Sorry, didn't read it anywhere :(
It was my interpretation of the problem because it looks to me the container wasn't running error free. I had this issue once before.
Kr.,
Frepke

@Frepke woah good job guessing the problem then !! I thought it was something completely irrelevant on my side...
@parker789 would you mind sharing the output of docker logs pia ?
If any error occurs during PIA initialization (including the first hostname resolution), the whole container should fail (hopefully!)

@qdm12 i'll get back to this when i get home tonight. i believe the state of the container is stuck in "Starting" though

I'm having a same problem now:
nslookup: can't resolve 'swiss.privateinternetaccess.com': Try again
In the logs.
It was working fine few days ago, nothing changed on my system.

That's odd 😞
Have you tried with other regions? Does it fail for all of them, some of them or just one?
One quick fix would be to have an env variable to not translate the domain name swiss.privateinternetaccess.com into IP addresses but then the firewall could not restrict outbound VPN traffic to only these IP addresses 😭

Oh never mind, I just pulled the latest PIA and it does not work as well. Let me see what I can do!

Thanks for looking into this, hope you can fix it soon.

Yes it's just a DNS issue, turning DOT=off should solve it for now, but I am investigating.

Yes it's just a DNS issue, turning -e DOT=off should solve it for now, but I am investigating.

I can confirm this, setting DOT=off and BLOCK_MALICIOUS=off makes it work again. I would guess it is somewhat related to DOT option as this is new, I had BLOCK_MALICIOUS=on for long time, but no DOT in docker-compose.

Ok so it's because of BLOCK_NSA=on on my side. This is because the list is built every 3-4 days and the PIA image is updated with the new list every 3-4 days. The PIA hostname probably got included for whatever reason, I'm checking on that. Would you mind trying with DOT=on and BLOCK_MALICIOUS=on but BLOCK_NSA=off? Thanks !

Hi @parker789 @gurabli @Frepke thank you all for your help!
In the end I have re-launched a build of the block lists (especially the NSA one), rebuilt the Docker image and it now works with DOT=on, BLOCK_MALICIOUS=on and BLOCK_NSA=on as well. I have also tested it with the image from Docker Hub which works too.
If you have any trouble, don't hesitate re-opening this issue.

Thank you too.
Kr.,
Patrick

Nice! thanks for the help. I'm back to trying to get things setup again :)

@qdm12
I'm going to piggy back on this just as I'm learning.. and no need to flood your project with question issues.
I have things up and running with a second container linuxserver/rutorrent connecting through the pia container. The ip address of both pia and rutorrent containers are both going through the VPN. nice!
Now.. the problem is i still can't access the rutorrent web-ui from my local host ip (192.168.1.10). rutorrent by default uses port 80 for the web-ui, which is obviously used by HTTP, and is already being used on the host machine for my OMV admin ui.  From my understanding, I should add something like -p 803:80/tcp on the pia container to view the rutorrents web-ui (port 80) from my host ip @ 192.168.1.10:803? I'm missing something because this does not work. any help would be appreciated! :)

Thanks @qdm12 for fixing this issue so fast!
Will check with everything blocking related enabled this evening.

@qdm12  ...

@parker789
Yes, publishing the ports that way is okay. Unfortunately port 803 isn't allowed, you have to choose a number higher than 1024.
Kr.,
Frepke

I think port 80 should be free on the PIA container's network stack and you should be able to map to the port of your choice on your host as long as it's free.
Maybe try with -p 8080:80/tcp? Ideally, you may want to avoid using ports below 1024 as these are privileged ports and might give you permission issues.

Awesome guys! @Frepke @qdm12  thanks a lot for the help. I think in the end my EXTRA_SUBNETS=192.168.1.10 was bad and needed to be 192.168.1.0/24 - everything is working though :)

if your desktop is for example 192.168.1.12 you could only add 192.168.1.12 to EXTRA_SUBNETS and not the entire subnet 192.168.1.0/24. But if you're lazy like me and just want to allow your whole LAN to access it, use the entire subnet!
By the way, side note, do not port forward to the HTTP proxy from outside your home network as the connection is, I believe, unencrypted, although it will work.

I had the exact ip added to EXTRA_SUBNETS at first, but then switched it and things started working. I changed some docker port settings at the same time though, so it was probably the port settings which actually fixed things.
Also, yeah thanks! I do need to come up with a solution to access all this outside my home network, but that's for another time


text:
yarn build:aot fails

Trying to run yarn build:aot from branch no-universal-support fails.

Error Message:
ERROR in ./src/main.browser.aot.ts
Module not found: Error: Can't resolve './compiled/src/app/app.module.ngfactory' in '/Applications/MAMP/htdocs/giveaways/src'
 @ ./src/main.browser.aot.ts 6:29-79

ERROR in [default] /Applications/MAMP/htdocs/giveaways/src/main.browser.aot.ts:7:35
Cannot find module './compiled/src/app/app.module.ngfactory'.

Couldn't parse bundle asset "/Applications/MAMP/htdocs/giveaways/dist/client/index.js".

I didn't yet look into this issue, just wanted to report it.

From readme:
To create AOT version, run yarn run compile. This will compile and build script. Then you can use yarn run prodserver to see to serve files. Do not use build:aot directly unless you have already compiled. Use yarn run compile instead, it compiles and builds:aot

I was using typescript v2.1.1.  I downgraded to version 2.0.10 just like the current version qdouble is using and now i'm seeing errors I should have been fixing that for some reason 2.1.1 was skipping over.  After fixing the errors 2.1.1 was apparently ignoring, everything compiles fine now.

angular doesn't support ts 2.1+

@DzmitryShylovich didn't know you were involved with qdouble's starter.  Is there anything you aren't involved with? lol

authors: DzmitryShylovich helzgate inzerceubytovani ricricucit

license: mit


text:
win10 开启管理员权限无法拖拽文件

win10上程序开启了管理员权限，然后过滤了以下三条消息还是无法进行文件拖拽，拖拽是显示被禁止，这是为什么呢 ？ChangeWindowMessageFilter(WM_DROPFILES, MSGFLT_ADD);
ChangeWindowMessageFilter(WM_COPYDATA, MSGFLT_ADD);
ChangeWindowMessageFilter(0x0049 , MSGFLT_ADD);

@tonydevsite 那请问这种问题该如何解决呢

已经修复

如何解决的大神

authors: qdtroy wangzhechn zhangyuxue


text:
Added support for env vars

This allows tasks to have environment variables passed to them so you can do things like the following and ensure that the proper items are in place before running tests:
tasks: [
  {:cmd, "mix ecto.setup", env: [{"MIX_ENV", "test"}]},
  "mix test"
]

If no args are passed, and empty list is provided to System.cmd/3

Pull Request Test Coverage Report for Build 138

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 78.462%

Totals

Change from base Build 137:
0.7%

Covered Lines:
51

Relevant Lines:
65

💛  - Coveralls

Friendly bump :)

Hey @akoutmos sorry I didn't have to take a look at this, I want to get ride of the TODO in the code instead of allowing it on credo.
I will merge it ASAP, thanks for the contribution! 🎉

Thanks for getting back to me! Are you talking about this one? https://github.com/qgadrian/elixir_git_hooks/blob/master/lib/mix/tasks/git_hooks/run.ex#L77

Want me to remove the TODO in this PR?

@akoutmos, please do. I updated master branch with the deprecation so no more TODOs pending anymore

Reverted the credo change. Let me know if there is anything else you would like me to do :)

Thanks for the contribution @akoutmos 🎉

No problem :). Thanks for the awesome lib!!

authors: akoutmos coveralls qgadrian


text:
缺少了很多文件和目录

如题

已添加

[还是缺少啊

我这边也是报错，应该是缺了不少文件

需要使用composer安装

git 下文件后，composer install 依旧报错。和上面的朋友提到的一样。

composer.lock
init
init.bat
requirements.php
把上面的几个文件删除，然后再执行 composer install试试

@qiaohongbo 可以了.谢谢

文件好像少了很多

需要composer安装

composer.lock
init
init.bat
requirements.php
删除了很多遍还是不行
php版本5.6

删除下载的源码，重新下载最新的再试一下；还有可能就是你的网络被限制了，你可以试着翻墙再试一下用composer install

composer install 报错

视图文件都没有

请问一下这个后台,连接不上数据库

authors: Alexcck baw123 cacacai kagomelee minzheluk qiaohongbo wslys xbdsky zli22443


text:
安装位置

exe不能自动选择安装路径
Sent from PPHub

可以下载单文件版exe（没有setup的那个），用压缩软件打开并解压里面的app-64.7z


text:
add Metadata.peek and connect to cli

Currently the only (planned) way to directly see the metadata column types using the command line is through qiime metadata tabulate (pending https://github.com/qiime2/q2-metadata/issues/3). If a user is editing their #q2:types info or their metadata values to alter the types, generating the viz will get annoying (it’s kind of like iterating with the QIIME 1 validate_mapping_file.py script). We should add a utility in qiime tools that would print the column names and their types. This could also be useful for figuring out what the column names are when viewing an artifact as metadata.

I think on the framework, this is already accomplished via the object repr and the .columns property. We can probably just present that info in q2cli (which I think is all you are really asking for).
If we did want a peek method in the framework, it kind of implies some partial loading of the file, which might be useful, but also seems like a lot of work for something that usually doesn't take much time in the first place.

What would you think about creating a command like qiime tools columns or qiime tools cols? I don't think we would want to put this functionality in qiime tools peek as that actually avoids loading artifacts. To view the columns of an artifact (which would be amazing), you would need to invoke a transformer which would take a lot longer than just "peeking" at /<uuid>/metadata.yaml.
There could be a flag like qiime tools peek --with-metadata, but it starts to get messy, and it makes looking at sample-metadata.tsv a little awkward (do I include it or not if that's my only argument)?

:+1:, this plan sounds great! What about using a slightly more descriptive name to help users out? A couple of ideas that come to mind are qiime tools metadata-columns, qiime tools inspect-metadata, or qiime tools summarize-metadata. I like the latter two options a little more than the first option because the names are more general, allowing other types of info to be displayed there in the future.

Awesome, I'm going to close this issue then and create a relevant one on q2cli!

authors: ebolyen gregcaporaso jairideout


text:
部分文件返回数据错误，这是一个严重的BUG，请重视

今天在测试时发现了一个情况，下载一个文件(xxx.txt  701b),总是失败，后来研究发现是6盘服务器的BUG，并且是严重BUG
使用案例
GET https://download2.99store.cn/oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe/wcs/user/%E5%88%86%E6%B5%81%E8%BD%AC%E8%BD%BD%E7%9A%84%E5%B8%8C%E6%9C%9B%E8%83%BD%E7%82%B9%E8%BF%9B%E6%9D%A5%E7%9C%8B%E4%B8%8B%3D%20%3D.txt?*******************************ck=aac1bb0f0f0b13388bafdd50a032e802&store=0 HTTP/1.1
Host: download2.99store.cn
Accept: */*
Range: bytes=604-700

HTTP/1.1 200 OK
Date: Thu, 31 Dec 2020 10:50:21 GMT
Content-Type: text/plain;charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
ETag: W/"FtoFW5yGfXO4stiF9FQzrS7Ddvhe"
Last-Modified: Sun, 07 Jul 2019 03:59:35 GMT
X-Reqid: 203322119924614820201231180132owE7Sukdsampled
Server: WS-web-server
Content-Encoding: gzip
Age: 2929
X-Via: 1.1 ydong91:3 (Cdn Cache Server V2.0)[82 200 2], 1.1 PS-PEK-01UVD107:2 (Cdn Cache Server V2.0)[0 200 0]
X-Ws-Request-Id: 5fedaced_PS-PEK-01WKu106_55012-39808
Access-Control-Allow-Origin: *

案例说明
正常的去下载一个文件（附加了Range: bytes=604-700，断点续传头），
期望返回正确的文件数据（96b），
实际返回发生了严重的BUG

返回了文件全部数据（而不是请求的部分数据）
返回了gzip压缩后的数据

我有测试了在请求头中附加
Accept-Encoding: identity
Accept-Encoding: deflate
Accept-Encoding:
希望强制返回非gzip数据，都无效
错误分析

未能正确的返回206 Range数据
未能正确的识别Accept-Encoding，返回合规的数据（默认无Accept-Encoding，返回原始数据，不压缩）

希望可以早点看到并回复

测试了一下，6盘Lite客户端 V0.8.3-测试版.zip，也无法正常下载这样的文件------因为被gzip压缩了

nobody care？

nobody care？

谢谢反馈，经检查我们存储服务器上文件是正常的，也正确响应了未压缩请求。
而似乎CDN侧将文件强制进行了gzip压缩，我们已经向CDN报告该故障，由于尚在假期
值班给出的解释如下：
对于一定的文件Content-Type和UA，CDN会尝试压缩文件，而且忽视掉Accept-Encoding。
能否告知您下载的时候使用的User-Agent头，我们操作增加白名单，CDN厂商应该不会短期内给出patch？

`sonic@MacBook-Pro ~ % curl "https://bg.grs.jiangsu.scs.tencent.com/oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe" -v  -H "Range: bytes=0-1" -o /dev/null
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0*   Trying 10.0.31.181...

TCP_NODELAY set
Connected to bg.grs.jiangsu.scs.tencent.com (10.0.31.181) port 80 (#0)

GET /oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe HTTP/1.1
Host: bg.grs.jiangsu.scs.tencent.com
User-Agent: curl/7.64.1
Accept: /
Range: bytes=0-1

< HTTP/1.1 206 Partial Content
< Date: Tue, 16 Feb 2021 19:05:40 GMT
< Content-Type: text/plain;charset=UTF-8
< Content-Length: 2
< Connection: keep-alive
< Accept-Ranges: bytes
< ETag: "FtoFW5yGfXO4stiF9FQzrS7Ddvhe"
< Content-Range: bytes 0-1/701
< Last-Modified: Sun, 07 Jul 2019 03:59:35 GMT
< X-Reqid: 203322119924325720210217030540bGZZpQ3lsampled
< Server: stgw/1.3.12.4_1.13.5
<
{ [2 bytes data]
100     2  100     2    0     0     28      0 --:--:-- --:--:-- --:--:--    28`

@liupan1890 部分文件下载失败 显示No URI available 还有的Range: xxxxxxxxxxx-xxxxxxx数字很大的红字错误 是这个原因吗？

1 下载请求User-Agent: Accelerider-Lite download engine
2 Invalid range header红字错误 是这个原因！！
我当时发现此BUG时发现，此BUG是随机文件发生的，就是有的文件不会发生此BUG，有的文件会发生此BUG，或许你们可以根据

GET https://download2.99store.cn/oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe/wcs/user/分流转载的希望能点进来看下%3D %3D.txt?*******************************ck=aac1bb0f0f0b13388bafdd50a032e802&store=0 HTTP/1.1

这个URL找到此文件进行测试，我遇到的问题是请求206，结果返回200，还被gzip压缩了。当时以为是我程序的BUG，立即使用官方客户端（windows版本uwp和lite都试了），也是一样的不能下载，会报错
错误原理就是：
当断点续传下载文件的最后一部分时，比如701B的文件，下载500B-701B这一部分，因为文件整体被gzip了，导致文件体积变小了（比如压缩成600B了）他就无法返回500-701，只能返回完整的文件数据（1-500B）
Invalid range header红字错误：也是，就是说程序请求断点续传，结果返回了完整的数据内容（没有返回Content-Range: bytes 0-1/701），找不到Content-Range报错Invalid range header（非法的range头）

记得多次测试后，经验是，必须是小文件比如1KB以内，最好是txt格式文件，部分文件会出现此错误（也可能是部分节点、或者部分域名download2.99store.cn）。总之错误是确实存在的，但也是类随机的，不是百分百触发。但是如果一个文件触发了此错误，短时间内多次重复下载此文件，都会触发此错误。短时间内无法通过重试下载成功下载

我们目前只能确定到节点吐出去的数据是未经压缩的。
CDN侧年前据说有更新系统 不知道是不是因为这个原因。

记得多次测试后，经验是，必须是小文件比如1KB以内，最好是txt格式文件，部分文件会出现此错误（也可能是部分节点、或者部分域名download2.99store.cn）。总之错误是确实存在的，但也是类随机的，不是百分百触发。但是如果一个文件触发了此错误，短时间内多次重复下载此文件，都会触发此错误。短时间内无法通过重试下载成功下载
另外我看到你的测试里，

"https://bg.grs.jiangsu.scs.tencent.com/oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe" -v -H
Range: bytes=0-1

直接返回了206，是正常的，没有出错，但是：
1.这是测试腾讯的CDN吧？https://download2.99store.cn/oriStore也是走的腾讯cdn吗？免费账号下载的话有的不是走泉州数据中心那个线路吗？
2.你需要测试Range: bytes=699- 就是测试下载最后的数据（gzip压缩后导致文件体积小+请求最后的数据699超出gzip文件体积===返回200）。你只测试Range: bytes=0-1只能说名正确返回了数据，但你无法证明文件是否被自动gzip压缩了
我刚刚又测试了一下，此文件，正常下载，没有触发此BUG

GET https://cdn8.99store.cn/oriStore/FtoFW5yGfXO4stiF9FQzrS7Ddvhe/wcs/user/分流转载的希望能点进来看下%3D %3D.txt?***************** HTTP/1.1
Host: cdn8.99store.cn
User-Agent: Accelerider-Lite download engine
Accept: /
Range: bytes=0-700

真是迷一样的BUG，可能是与域名（节点）有关

那个地址是源站 非CDN服务器，是在我们管理范围内，经过测试有正确响应，并且我们已经将Gzip支持关闭了。
Content-Range 头的返回与预期一致，并且没有CONTENT-ENCODING

repo: qingzhenyun/qingzhenyun-api-doc


text:
fix typo;add Typst Template for Academic CV

Repo URL:
https://github.com/DawnEver/typst-academic-cv

Hey @DawnEver this is really cool! Thanks for the awesome contribution 🚀

authors: DawnEver qjcg

repo: qjcg/awesome-typst


text:
Adding a dataset

Hi, I would like to add my own dataset, which consists in several mixed speech/music files.
In the README you mention the need for creating two different folders, but I cannot fully understand the "repartition of the data between each set for each type of label" part...
Could you please give us an example dir tree to use as reference?
Thanks

Hi! In my data folder it was divided like this:
- dataset1
     - audio
     - filelists
- dataset2
     - audio
     - filelists
...

The audio folder contains all the .wav files with their associated label as .txt.
And the filelists folder contains the names of the audio files (without extension) dispatched into different files to create the test/validation and training set: mixed_train, mixed_val, mixed_test, music_train, music_val, speech_train, speech_val or noise_train
mixed, audio, speech or noise corresponds to the time of audio.
I hope it will help! Tell me if it is not clear enough.

Thanks! I have a lot of mixed content, I should try to gather also clean speech and music...
Btw, I still not fully understand the proper structure and matching of proper files/timestamps...
Test, validation and training set could be the same files, or must they all be different?
It would be awesome if you could provide a sample folder to examine for the noobs.
Thanks

Mixed content is technically the best since it represents the goal you want to achieve. It is also the most expensive kind of data.
But having clean speech and music is an easy way to have a bigger dataset.
Test, validation and training must be strictly different, otherwise you will overfit the data.
I can try to give a more detailed example, if you have a custom dataset with 3 audio of mixed content:
- custom_dataset
    - audio
        audio1.wav
        audio1.txt
        audio2.wav
        audio2.txt
        audio3.wav
        audio3.txt
    - filelists
        mixed_train
        mixed_test
        mixed_validation

With mixed_train being:
audio1

With mixed_test being:
audio2

With mixed_validation being:
audio3

For the .txt files, if audio 1 contains music from 0s to 5s and speech from 2s to 10s, audio1.txt will be
0 5 speech
2 10 music

Is it clearer?

Sure, thank you!
I'll surely give it a try.

Hi, I successfully installed everything and added my own datasets, but when issuing python prepare_dataset/prepare_audio.py my_own_dataset I always get:
Traceback (most recent call last):   File "prepare_dataset/prepare_audio.py", line 224, in <module>     resample_dataset(args.data_location, args.dataset)   File "prepare_dataset/prepare_audio.py", line 18, in resample_dataset     cfg = utils.load_json('../datasets.json')   File "/home/developer/Documents/speech-music-detection/smd/utils.py", line 99, in load_json     with open(filename) as f: FileNotFoundError: [Errno 2] No such file or directory: '../datasets.json'
Of course dataset.json is at the project's root, and contains:
{   "my_own_dataset": {     "data_folder": "my_own_dataset/audio",     "filelists_folder": "my_own_dataset/filelists"   } }
What am I missing?
Thanks


text:
feat: add mashup examples of QCS and QSEoW for demo

Providing an example of mashup working within QCS
using build tool
without build tool - It has the ability to run sn-table which is not released yet
Providing an example of mashup working within QSEow

Why the capital letters in the file names?

Why the capital letters in the file names?

folder name? let me rename them

Why the capital letters in the file names?

folder name? let me rename them
Yeah the only the name of the folders actually

I have a refactor idea. The two examples using parcel seem to have more incommon that the two desktop examples, package json and html look identical, no? Put those two in one folder and have the non-build tool example in a different folder

I have a refactor idea. The two examples using parcel seem to have more incommon that the two desktop examples, package json and html look identical, no? Put those two in one folder and have the non-build tool example in a different folder

Okay, i have no opionion about it. But sure.

Done

My point with the refactor was that you could reuse at least the package and html file, but might be easier to keep them separate if they diverge in the future

My point with the refactor was that you could reuse at least the package and html file, but might be easier to keep them separate if they diverge in the future

yaah, i think that they will diverge in the future

repo: qlik-oss/sn-table


text:
Test Issue - qqifw

Test Body - nnudupaaxy

Test Comment - zkxty

repo: qlikqaa/dummyrepo


text:
Test Issue - nqmbc

Test Body - tnscukodha

Test Comment - ryfjv


text:
Test Issue - rgvnt

Test Body - mftjudkbco

Test Comment - ldhov


text:
Test Issue - khdtu

Test Body - amsjmjkeyk

Test Comment - kupvp


text:
Test Issue - uxvrf

Test Body - lwcspvpsrn

Test Comment - boshk


text:
Test Issue - cwwjy

Test Body - vxekmtgjdj

Test Comment - bbtrn


text:
Test Issue - vnomy

Test Body - gajcibgzfe

Test Comment - sycjs


text:
Test Issue - yfkmx

Test Body - ybfnildbym

Test Comment - jdglo


text:
Test Issue - gvvyt

Test Body - pmtzdqdmjr

Test Comment - nsaxz


text:
Test Issue - yecpl

Test Body - sxklpejxqw

Test Comment - vcrzm


text:
Test Issue - eivqy

Test Body - fjwqqarhtt

Test Comment - njqgo


text:
Test Issue - ijfdx

Test Body - meqmabepvh

Test Comment - qzpcr


text:
Test Issue - vxnib

Test Body - zlskcoccpq

Test Comment - mqsgs


text:
Test Issue - gfwcu

Test Body - mgrpivclce

Test Comment - uvrib


text:
Test Issue - uxkhb

Test Body - ieowsbcizh

Test Comment - ioiuc


text:
Test Issue - ebstf

Test Body - jlhndkqvtu

Test Comment - fipgm


text:
Test Issue - vputz

Test Body - kbecdmdddb

Test Comment - psobx


text:
Test Issue - wuiks

Test Body - eklnhijtug

Test Comment - hvbop


text:
Test Issue - somsq

Test Body - hkvxsbytvb

Test Comment - zcarc


text:
Test Issue - kgzfy

Test Body - icuxgzdahd

Test Comment - klbwt


text:
Test Issue - pnmsz

Test Body - wvmreyudbq

Test Comment - hduns


text:
Test Issue - fyacq

Test Body - msqgvukyfb

Test Comment - xzolt


text:
Test Issue - jrtal

Test Body - bqvemnanvw

Test Comment - zqvdj


text:
Test Issue - ioxro

Test Body - zdreiapvcd

Test Comment - apocr


text:
Test Issue - vrkbx

Test Body - myawsacmay

Test Comment - gwdvc


text:
Test Issue - bhwak

Test Body - wszhjvdkso

Test Comment - frzfm


text:
Test Issue - giepu

Test Body - ojfckokabj

Test Comment - qzuod


text:
Test Issue - fswnn

Test Body - zqgqgypkeh

Test Comment - dtjcp


text:
Fails to generate types for defineExpose with Vue 3.3 & TS 5.0

Describe the bug
We have components with defineExpose, the types of defineExpose stuff was properly generated in Vue 3.2, but they are no longer generated with Vue 3.3 + TS 5
There are likely other issues with Vue 3.3, such as imported types in defineProps not working with an import error, generic components not working, and so on.
Reproduction
https://stackblitz.com/edit/vitejs-vite-t4ucyt?file=src%2FApp.vue
Steps to reproduce
npm exec type-check
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^4.2.1 => 4.2.1
    vite: ^4.3.9 => 4.3.9
    vite-plugin-dts: ^2.3.0 => 2.3.0

Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

@qmhc

Does v2.3.0 supports TS 5 currently? Maybe related: #190 #194

authors: Tanimodori segevfiner

repo: qmhc/vite-plugin-dts


text:
TypeInitializationException on Linux 18.0.4

I tried the project Features on my development machine Windows 10-64 bit.
When I launch it from Visual Studio 2017, I get the following error message in the console window:
"QWindowsContext: OleInitialize() failed:  "COM error 0xffffffff80010106 RPC_E_CHANGED_MODE (Unknown error 0x080010106)""
The error message appears on the line 13, using (var application = new QGuiApplication(args)).
However, this error doesn't brake the application; the application continues and works fine.
Then I tried it to on Linux 18.0.4, the one from Windows Store. I used the following publish configuration in Visual Studio:

When I launched the application I got TypeInitializationException:

Then I tried some other publish configurations, but none of them was successful.
Then I commented out the line QQuickStyle.SetStyle("Material"), but I got the same exception(of course with a different stack trace).
Then I created a "Hello World" console application that targets the same netcoreapp2.2. I wanted to be sure that I installed correctly the .netcore 2.2 on Linux. The application works fine on Linux.
Is there something I am doing wrong?

Nothing wrong, this happens with a pure Qt app as well.
In my experience, that error has been harmless.

Thank you for your reply.
You didn't say anything about the TypeInitializationException on Linux? Do you have any idea what would cause that issue?

Is this Ubuntu using WSL?

Yes, it's WSL. I installed it from Windows Store.

WSL doesn't support GUI apps (without some hacking). You'll have to run Qml.Net on a native Linux box.

Thank you very much.

I have the same error on Ubuntu, but I'm not using WSL. What else can be a reason for such an error?

If you are interested in a TeamViewer session, email me at pauldotknopf at gmail.
Otherwise, set LD_DEBUG=all, run again, and give me the output.

authors: Ticky-Ticky ernest-morariu pauldotknopf

repo: qmlnet/qmlnet-examples


text:
object collision

Proposed change(s)

メッシュ表面へ粒子を配置する機能を追加

MeshからSDFを生成する関数を実装しました。（VisualEffectの実装関数から拝借）
MarchingCube法の一部を使って、SDFの0付近の座標を取得する関数を用意しました。（ここのソースコードを拝借）
以降、オブジェクト表面に配置された粒子を「オブジェクト粒子」とします。

MD法で粒子とオブジェクト粒子の衝突計算する関数を追加

Shader内で粒子間の衝突力を計算する部分を関数化してます。

その他、軽微なリファクタを実施

Screenshot
オブジェクト粒子の様子

衝突の様子

残課題（随時更新）

[ ] オブジェクトの移動・回転に対応する
[ ] オブジェクト粒子の密度をメッシュサイズに合わせて自動計算する
[ ] 粒子数32k個でFPS60-100を確保する

TerrainのHeightmapResolutionを上げることで同様の現象が起きなくなることを確認しました。
また、これはこちらの環境の問題かもしれませんが、最初にプロジェクトを開いた際にBucketのMeshのisReadableがFalseになっていてSDF(?)を作成する際にエラーが発生していました。
https://github.com/qoopen0815/ParticlePhysics/blob/dev/object-collision/Assets/Develop/Models/Bucket.fbx.meta#L35

オブジェクトとの衝突計算の軽量化案
近傍探索の格子をオブジェクト基準で移動・回転させることができれば、オブジェクト粒子の格子内の位置計算は初期化時に済ませることができるので、Update()のなかでは土粒子だけを対象に近傍探索すれば良くなる。
近傍探索の格子は平行移動のみサポートしているので、回転にも対応するよう修正が必要。

近傍探索範囲をTransformに追従するように改造
https://github.com/qoopen0815/ParticlePhysics/assets/26988372/e0362480-2a04-4775-b7bd-81fdb27e787b


text:
Only playlist knobby shows is "liked songs"

recently knobby will only show my "liked songs" playlist. previously i was able to access and scroll through all my saved playlists. I am running the latest version.
even if I like or save new playlists, they dont show up.

I had the same issue when loading the vanilla firmware from https://setup.knobby.net/. I would click/scroll to "playlists" and only see "liked songs".
I figured it might be an issue with the API call to the me/playlists Spotify API endpoint, so I tried opening the code in PlatformIO and first uploading the firmware manually before playing with the API call here. But I uploaded the plain old firmware with PlatformIO and the Playlist functionality just worked ¯_(ツ)_/¯. I now see 51 playlists (the firmware looks like it caps it at 50 with uint16_t limit = 50; at line 3159)
So I don't know if the official current version on the setup site is out of date or different than what's in the repo maybe? But build/upload with PlatformIO seemed to work for me!

Sorry for the radio silence! Spotify seems to have made a small breaking change to the playlists API endpoint[^1] which broke this menu. I fixed the issue on main but never got around to publishing a release until now: https://github.com/quadule/knobby/releases/tag/2024.11.24
[^1]: When specifying fields to include in the API response, pagination attributes like total are no longer included automatically.

authors: brianmgr muzerious quadule

repo: quadule/knobby


text:
Be more explicit about the layout of the ResTable_config type

Decompose union types into their individual values to:

Avoid endianness issues.
Allow for copy the mask and shift values directly from the C sources

Add support for the latest fields.

@bartsaintgermain
Fixes the night mode issue, can you review & approve? Thx!

repo: quamotion/androidxmldotnet


text:
🛑 yami-sora is down

In b2b7af7, yami-sora (https://www.yami-sora.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: yami-sora is back up in e10859e after 7 minutes.


text:
🛑 Xemphim club is down

In ff41435, Xemphim club (https://xemphim.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Xemphim club is back up in 7dc1013.


text:
🛑 cuongquach is down

In b347204, cuongquach (https://cuongquach.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cuongquach is back up in c2a6480.


text:
🛑 kokocon is down

In 7cbace3, kokocon (http://kokocon.net/) was down:

HTTP code: 500
Response time: 236 ms

Resolved: kokocon is back up in ee15511 after 6 minutes.


text:
Limit leak in us equity loader on stock rotation

BUG: Add limit to memory growth on sliding windows
Add a cap of 5 sliding windows (one per OHCLV column) to the history
loader's cache of sliding windos.

This prevents unbounded growth on algorithms that call history with a
highly varied list of equities.

To follow is splitting the cache up by column and by sid, so that the
loader does not re-prefetch sids which have already been read with
sufficient data; however this patch is enough to fix the issue where an
algo with high rotation can add up a megabyte per day of memory on
algorithms which rotate on a 5% dollar volume pipeline. With this cap
those algorithms have more plateaus with regard to memory consumption.

This patch requires new dependency of `cachetools` library.

Also, add cachetools recipe (via @richafrank )

Coverage increased (+0.005%) to 84.275% when pulling e1b376a49b23fb468e5eaf5cda0d1463fbf8975b on fix-us-equity-loader into 9e2c5d9505f81f547a6decd2a4bb9015f782ae71 on master.

authors: coveralls ehebert

repo: quantopian/zipline


text:
Create examples with different datasets

One of our favourite things about Kedro is its versatility, the ability to adapt to different use-cases and needs. It truly makes our day when our users come up with their projects exploring the countless possibilities for Kedro-usage.
To check out some of the coolest kedro-examples developed by our community, have a look at the Kedro-Examples repository.
With that in mind, we would love to see your examples! Show us what you can do!
To help you on the quest, here are some learning aids:

Video walkthrough beginner's guide to Kedro by @dataengineerone (NOTE: this video uses Kedro version 0.16.4. The latest version 0.16.5 does not have a pipeline.py file. More details here).
Our Hello World  example
Iris dataset example
Spaceflights tutorial
Video demo on how to convert your Jupyter Notebook into a Kedro project - demo repo is here
Blogpost on What is Kedro? by our super-user @WaylonWalker
Tutorial on how to create a project with Custom Datasets using the Pokémon Kaggle dataset.

Questions? You are always welcome to message us on Stack Overflow with the #kedro and #python tags. And now, you can also leave your questions at the Kedro Community website.
Now, pick your favourite dataset and let's get started! Our favourite examples will be linked on the official examples repository.
Happy sprinting!  🏃🏿♀🏃🏽♂

@laisbsc, Is this issue still available for hacktoberfest ?

authors: cemeiq laisbsc

repo: quantumblacklabs/kedro


text:
Remove cirq.Tolerance

This class ended up being nothing more than a variation on passing atol arguments, so it's not pulling enough weight to justify being in the API.

Hi @Strilanc
This looks like a simple enough issue to start my contributions with. Just to make sure I understand, you only want it removed from the API, i.e. basically removing the import from the init.py in the root directory?

@andbe91 I've started working on this but i didn't officially claim it so it's up to @Strilanc to decide; but yes, remove every reference to Tolerance (removing tolerance.py. e.t.c).

@vtomole since you have already started, it might be better if I work on another issue. Please let me know if you want me to take over for some reason.

@vtomole is correct; this would involve completely deleting the class

That being said, I think the main important arguments to propagate are atol and rtol, no need for the nan ones.

This is done. Please close.

We might want to take a pass through code to insure that we are using atol and rtol as parameters when it makes sense (probably most of the time)

authors: Strilanc andbe91 dabacon vtomole

repo: quantumlib/Cirq


text:
Move state conversion logic from _create_partial_act_on_args to the corresponding ActOnArgs

Currently all the logic for converting a zero to, say, a state vector resides in SparseSimulator._create_partial_act_on_args. The ActOnStateVectorArgs requires a full state vector to be passed in. This makes working with ActOnArgs inconvenient. You either have to have a Simulator around to create one, or call the function that creates a state vector from a basis state and pass it in, or whatever. It should be possible to call ActOnStateVectorArgs(0, qubits) and have it know what you mean. (And we should rename it, but that's a different issue).
This would also be nice because you could then write a generic function that adds some qubits to an existing state space, something like
class ActOnArgs:
...
  def with_qubits(self: TSelf, qubits) -> TSelf:
    new_space: TSelf = type(self)(0, qubits)
    return self.kron(new_space)

Again, currently if you want to do something like that, you have to have full Simulators around, and it would be nice not to have to.
I believe this would be a fairly small, uninvasive change, just moving some code around. Could be a good first or second issue. Would likely want to finish #4789 first.

@viathor this is more "area/simulator" than the other two labels.


text:
Documentation line width

A few years ago we switched to using black to auto-format and set the character width at 100.  When we did this, we ended up with a lot of doc strings that were not touched and so are 80 characters.  We now have both 80 or 100 or a mixture of docstrings.

Would be nice to just standardize on one width going forward, just so we don't have to think about it.  Possibly also say new docstring follow this, old ones are ok.

We could use a docstring format enforcer.  The best I've found so far is https://github.com/PyCQA/docformatter .  It is not super aggressive, if your description in a doc string has special characters, it prefers not to wrap things.

Low priority.

Marked discuss even though we already had a discussion about this since it seems to me that there are still some unknowns, e.g. which tool to use.

In going through the annotations of docformatter, there are lots of methods that have multiline doc strings that don't follow PEP 257 in that they don't have a single line comment followed by a space, but are instead multiline right of the bat.  Other than that it seems to make pretty reasonable choices.

@dabacon Change after-1.0 if you feel strongly about it.

authors: dabacon tanujkhattar viathor