UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

Thanks for helping create youtube-dl.
There seems to be a problem with Unicode handling. With youtube-dl [any video], OR trying the latest git master HEAD (d5f6429de87da4bffa0be7703d774681393f1ffb) and ./setup.py build, I get:
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl", line 5, in
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3138, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3124, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3151, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 652, in _build_master
ws = cls()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 645, in init
self.add_entry(entry)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 701, in add_entry
for dist in find_distributions(entry, True):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2139, in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2521, in from_location
py_version=py_version, platform=platform, **kw
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2835, in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2486, in _version_from_file
line = next(iter(version_lines), '')
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2654, in _get_metadata
for line in self.get_metadata_lines(name):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2030, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2025, in get_metadata
metadata = f.read()
File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte
The line in question is:
from pkg_resources import load_entry_point
The installed youtube-dl version (/usr/local/bin/youtube-dl) is 2015.12.18.
Now, to my understanding, 0xb6 is, indeed, invalid as a utf8 start byte. Where this is coming from is beyond me at the moment. As the second byte, it is present in eg. ¶ (U+00B6, aka 0xc2 0xb6) and ö (U+00F6, aka 0xc3 0xb6).
So far, I've found this presentation: http://nedbatchelder.com/text/unipain.html
And this poor fellow, with the ~samish problem: http://www.gossamer-threads.com/lists/engine?do=post_view_flat;post=1070061;page=1;mh=-1;list=python;sb=post_latest_reply;so=ASC

Sorry, but I am unable to build the latest version. I get the same error as above. Personally, I find this strange.

Sorry, but I am unable to build the latest version. I get the same error as above. Personally, I find this strange.

Could you provide more details about "unable to build the latest version"? Including the commands you've tried to build and the error messages.

Could you provide more details about "unable to build the latest version"? Including the commands you've tried to build and the error messages.

./setup.py build
Traceback (most recent call last):
File "./setup.py", line 11, in
from setuptools import setup
File "/usr/lib/python2.7/dist-packages/setuptools/init.py", line 12, in
from setuptools.extension import Extension
File "/usr/lib/python2.7/dist-packages/setuptools/extension.py", line 8, in
from .dist import _get_unpatched
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 19, in
import pkg_resources
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3138, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3124, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3151, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 652, in _build_master
ws = cls()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 645, in init
self.add_entry(entry)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 701, in add_entry
for dist in find_distributions(entry, True):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2139, in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2521, in from_location
py_version=py_version, platform=platform, **kw
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2835, in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2486, in _version_from_file
line = next(iter(version_lines), '')
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2654, in _get_metadata
for line in self.get_metadata_lines(name):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2030, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2025, in get_metadata
metadata = f.read()
File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

./setup.py build
Traceback (most recent call last):
File "./setup.py", line 11, in
from setuptools import setup
File "/usr/lib/python2.7/dist-packages/setuptools/init.py", line 12, in
from setuptools.extension import Extension
File "/usr/lib/python2.7/dist-packages/setuptools/extension.py", line 8, in
from .dist import _get_unpatched
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 19, in
import pkg_resources
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3138, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3124, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3151, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 652, in _build_master
ws = cls()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 645, in init
self.add_entry(entry)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 701, in add_entry
for dist in find_distributions(entry, True):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2139, in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2521, in from_location
py_version=py_version, platform=platform, **kw
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2835, in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2486, in _version_from_file
line = next(iter(version_lines), '')
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2654, in _get_metadata
for line in self.get_metadata_lines(name):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2030, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2025, in get_metadata
metadata = f.read()
File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

In /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py around line 2022:
    def get_metadata(self, name):
        if name=='PKG-INFO':
            with io.open(self.path, encoding='utf-8') as f:
                metadata = f.read()
            return metadata
        raise KeyError("No metadata except PKG-INFO is available")

Could you add a line print(self.path) before io.open(self.path, ...). Like this:
    def get_metadata(self, name):
        if name=='PKG-INFO':
            print(self.path)
            with io.open(self.path, encoding='utf-8') as f:
                metadata = f.read()
            return metadata
        raise KeyError("No metadata except PKG-INFO is available")

And run the build command again?
WARNING: Changing system files is risky. Please backup all files you're going to change.

In /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py around line 2022:
    def get_metadata(self, name):
        if name=='PKG-INFO':
            with io.open(self.path, encoding='utf-8') as f:
                metadata = f.read()
            return metadata
        raise KeyError("No metadata except PKG-INFO is available")

Could you add a line print(self.path) before io.open(self.path, ...). Like this:
    def get_metadata(self, name):
        if name=='PKG-INFO':
            print(self.path)
            with io.open(self.path, encoding='utf-8') as f:
                metadata = f.read()
            return metadata
        raise KeyError("No metadata except PKG-INFO is available")

And run the build command again?
WARNING: Changing system files is risky. Please backup all files you're going to change.

./setup.py build
Traceback (most recent call last):
File "./setup.py", line 11, in
from setuptools import setup
File "/usr/lib/python2.7/dist-packages/setuptools/init.py", line 12, in
from setuptools.extension import Extension
File "/usr/lib/python2.7/dist-packages/setuptools/extension.py", line 8, in
from .dist import _get_unpatched
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 19, in
import pkg_resources
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2004, in
class FileMetadata(EmptyProvider):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2022, in FileMetadata
print(self.path)
NameError: name 'self' is not defined

Could you paste contents around line 2000~2050 of the original /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py?

register_loader_type(zipimport.zipimporter, ZipProvider)
class FileMetadata(EmptyProvider):
"""Metadata handler for standalone PKG-INFO files
Usage::

    metadata = FileMetadata("/path/to/PKG-INFO")

This provider rejects all data and metadata requests except for PKG-INFO,
which is treated as existing, and will be the contents of the file at
the provided location.
"""

def __init__(self, path):
    self.path = path

def has_metadata(self, name):
    return name=='PKG-INFO' and os.path.isfile(self.path)

def get_metadata(self, name):
    if name=='PKG-INFO':
        with io.open(self.path, encoding='utf-8') as f:
            metadata = f.read()
        return metadata
    raise KeyError("No metadata except PKG-INFO is available")

def get_metadata_lines(self, name):
    return yield_lines(self.get_metadata(name))

class PathMetadata(DefaultProvider):
"""Metadata provider for egg directories
Usage::

    # Development eggs:

    egg_info = "/path/to/PackageName.egg-info"
    base_dir = os.path.dirname(egg_info)
    metadata = PathMetadata(base_dir, egg_info)
    dist_name = os.path.splitext(os.path.basename(egg_info))[0]
    dist = Distribution(basedir, project_name=dist_name, metadata=metadata)

    # Unpacked egg directories:

    egg_path = "/path/to/PackageName-ver-pyver-etc.egg"
    metadata = PathMetadata(egg_path, os.path.join(egg_path,'EGG-INFO'))
    dist = Distribution.from_filename(egg_path, metadata=metadata)
"""

Seems you've added it to the wrong line. Originally it's
def get_metadata(self, name):
    if name=='PKG-INFO':
        with io.open(self.path, encoding='utf-8') as f:
            metadata = f.read()
        return metadata
    raise KeyError("No metadata except PKG-INFO is available")

Change it to:
def get_metadata(self, name):
    if name=='PKG-INFO':
        print(self.path)
        with io.open(self.path, encoding='utf-8') as f:
            metadata = f.read()
        return metadata
    raise KeyError("No metadata except PKG-INFO is available")

Note that the print line is exactly before with io.open(...

Oops, sorry.
Here's the printout with that line:
./setup.py build
/usr/lib/python2.7/argparse.egg-info
/usr/lib/python2.7/wsgiref.egg-info
/usr/lib/python2.7/lib-dynload/Python-2.7.egg-info
/usr/local/lib/python2.7/dist-packages/youtube_upload-0.8.0.egg-info
/usr/local/lib/python2.7/dist-packages/escpos-1.0.7.egg-info
/usr/local/lib/python2.7/dist-packages/calendar_indicator-0.3.1.egg-info
/usr/lib/python2.7/dist-packages/pyxdg-0.25.egg-info
/usr/lib/python2.7/dist-packages/yum_metadata_parser-1.1.4.egg-info
/usr/lib/python2.7/dist-packages/mercurial-3.5.2.egg-info
/usr/lib/python2.7/dist-packages/vboxapi-1.0.egg-info
/usr/lib/python2.7/dist-packages/wxPython_common-<IP_ADDRESS>.egg-info
/usr/lib/python2.7/dist-packages/bzr-2.7.0dev1.egg-info
/usr/lib/python2.7/dist-packages/pycurl-<IP_ADDRESS>.egg-info
/usr/lib/python2.7/dist-packages/lhafile-0.1.0fs4.egg-info
/usr/lib/python2.7/dist-packages/arandr-0.1.8.egg-info
/usr/lib/python2.7/dist-packages/rpm_python-<IP_ADDRESS>.egg-info
/usr/lib/python2.7/dist-packages/python_debianbts-2.6.0.egg-info
/usr/lib/python2.7/dist-packages/qbzr-0.23.1.egg-info
/usr/lib/python2.7/dist-packages/SecretStorage-2.1.2.egg-info
/usr/lib/python2.7/dist-packages/ecdsa-0.13.egg-info
/usr/lib/python2.7/dist-packages/docutils-0.12.egg-info
/usr/lib/python2.7/dist-packages/simplejson-3.7.3.egg-info
/usr/lib/python2.7/dist-packages/python_apt-1.1.0.b1.egg-info
/usr/lib/python2.7/dist-packages/scapy-2.2.0.egg-info
/usr/lib/python2.7/dist-packages/httplib2-0.9.1.egg-info
/usr/lib/python2.7/dist-packages/BzrTools-2.6.0.egg-info
/usr/lib/python2.7/dist-packages/gdata-2.0.18.egg-info
/usr/lib/python2.7/dist-packages/zenmap-7.00.egg-info
/usr/lib/python2.7/dist-packages/pycrypto-2.6.1.egg-info
/usr/lib/python2.7/dist-packages/pygobject-3.18.2.egg-info
/usr/lib/python2.7/dist-packages/pysqlite-1.0.1.egg-info
/usr/lib/python2.7/dist-packages/pyrit-0.4.0.egg-info
/usr/lib/python2.7/dist-packages/python_xlib-0.14.egg-info
/usr/lib/python2.7/dist-packages/numpy-1.9.2.egg-info
/usr/lib/python2.7/dist-packages/apt_xapian_index-0.47.egg-info
/usr/lib/python2.7/dist-packages/pygpgme-0.3.egg-info
/usr/lib/python2.7/dist-packages/pygame-1.9.1release.egg-info
/usr/lib/python2.7/dist-packages/bzr_builddeb-2.8.6.egg-info
/usr/lib/python2.7/dist-packages/roman-2.0.0.egg-info
/usr/lib/pymodules/python2.7/rpl-1.5.5.egg-info
Traceback (most recent call last):
File "./setup.py", line 11, in
from setuptools import setup
File "/usr/lib/python2.7/dist-packages/setuptools/init.py", line 12, in
from setuptools.extension import Extension
File "/usr/lib/python2.7/dist-packages/setuptools/extension.py", line 8, in
from .dist import _get_unpatched
File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 19, in
import pkg_resources
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3139, in
@_call_aside
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3125, in _call_aside
f(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 3152, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 652, in _build_master
ws = cls()
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 645, in init
self.add_entry(entry)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 701, in add_entry
for dist in find_distributions(entry, True):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2140, in find_on_path
path_item, entry, metadata, precedence=DEVELOP_DIST
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2522, in from_location
py_version=py_version, platform=platform, **kw
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2836, in _reload_version
md_version = _version_from_file(self._get_metadata(self.PKG_INFO))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2487, in _version_from_file
line = next(iter(version_lines), '')
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2655, in _get_metadata
for line in self.get_metadata_lines(name):
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2031, in get_metadata_lines
return yield_lines(self.get_metadata(name))
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 2026, in get_metadata
metadata = f.read()
File "/usr/lib/python2.7/codecs.py", line 314, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte

Thanks for helping debugging. The problem is /usr/lib/pymodules/python2.7/rpl-1.5.5.egg-info but not youtube-dl. As I can see from http://sourceforge.net/projects/rpl/files/rpl/rpl-1.5.5/, the author of rpl uses non-UTF8 characters in its setup.py. You may want to uninstall it and contact its author.
Also, don't forget to restore the original /usr/lib/python2.7/dist-packages/pkg_resources/__init__.py.


Allows include? to accept a string

Proposing what I hope is a minor change to allow the include? method to accept a string. This is a compatibility request for use in Rails when replacing the default class used by Postgres for process cidr values.

@aviemet thanks for the PR. Nice idea. 👍🏻


tetra-gtk-theme: init at 1.6

Looked like I might want it, thought others might find it interesting as well.

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: tetra-gtk-theme
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: tetra-gtk-theme
Partial log (click to expand)
Installing theme...

Installation complete. Enjoy!
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8x5g4dsw9lgbxsb0vy9qnycq7qh2yaq4-tetra-gtk-theme-0.1.6
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/8x5g4dsw9lgbxsb0vy9qnycq7qh2yaq4-tetra-gtk-theme-0.1.6
checking for references to /build in /nix/store/8x5g4dsw9lgbxsb0vy9qnycq7qh2yaq4-tetra-gtk-theme-0.1.6...
/nix/store/8x5g4dsw9lgbxsb0vy9qnycq7qh2yaq4-tetra-gtk-theme-0.1.6

Success on x86_64-linux (full log)
Attempted: tetra-gtk-theme
Partial log (click to expand)
Installing theme...

Installation complete. Enjoy!
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/5s1rv48cj07w33a1cx3xa3n1smw9g7fw-tetra-gtk-theme-0.1.6
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/5s1rv48cj07w33a1cx3xa3n1smw9g7fw-tetra-gtk-theme-0.1.6
checking for references to /build in /nix/store/5s1rv48cj07w33a1cx3xa3n1smw9g7fw-tetra-gtk-theme-0.1.6...
/nix/store/5s1rv48cj07w33a1cx3xa3n1smw9g7fw-tetra-gtk-theme-0.1.6


1.0: If a node is on "NotReady" status Supergiant won't spin a new node

Provider: AWS
Kubernetes version: 1.6.7
Supergiant version: 0.15.6
We had an issue and one of our nodes filled up. This caused the docker daemon to die hence making the node status "NotReady". This happened over the weekend and there were several pending pods that were never started. I even tried to manually schedule pods to see if Supergiant would spin a new node but after some time waiting I gave up: it looks like under these circumstances SG won't spin a new node.
One thing that may or may not have anything to do with this issue but I think makes sense to mention is that the node that filled up was the initial node (the one that's added alongside the master when you create a new kube)

Hi, @alterx, do you think I could work with you sometime to figure out how to reproduce this error?

Closing due to age and response.


[Feature Request] Update to tonic 0.10

Describe the solution you'd like
Update tonic in workspace to 0.10 and fix anything needed. In Python I saw something around the proxier! macro and IntoRequest, but I didn't investigate and it may be unique to Python's macro.

As usual this needs https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-otlp to update to newer tonic first which may take a while

I see. https://github.com/open-telemetry/opentelemetry-rust/pull/1310 is in PR but unsure when it'll move through. I'll come back to this when I see that (or similar) move.

Ideally, this crate's tonic dependency can (possibly) be updated independently of that of Opentelemetry's ?
I mean like this
core/Cargo.toml
opentelemetry-tonic = { version = "0.9", package = "tonic", features = ["tls", "tls-roots"] }

core/src/telemetry/metrics.rs
use opentelemetry_tonic::metadata::MetadataMap;
//use tonic::metadata::MetadataMap;

And update tonic  = "0.10" and prost-* to "0.12"

@h7kanna It can be, for sure, but I kinda wanted to avoid having multiple copies of tonic which is a rather large dep. Maybe that's not such a big deal but, so far the need to update as fast as possible hasn't been too important.

Yes ofcourse, I just wanted to point out that it is possible if needed.


Test the command php bin/console app:new-jwt-token

coz it seems there is a regression, the token seems falsy
retest it

It works !


eslint error fixes

Errors stopped gulp from compiling MDL
MDL version: v1.1.2
Operating system: OSX
Operating system version: v10.11.4
Node version: v5.10.1
What steps will reproduce the problem:
While running gulp all && gulp serve, gulp errored out due to eslint errors:
/material-design-lite/src/mdlComponentHandler.js
  366:51  error  Properties shouldn't be quoted as all quotes are redundant  quote-props

/material-design-lite/src/checkbox/checkbox.js
  123:5  warning  Unexpected 'todo' comment  no-warning-comments

/material-design-lite/src/icon-toggle/icon-toggle.js
  119:5  warning  Unexpected 'todo' comment  no-warning-comments

/material-design-lite/src/radio/radio.js
  133:5  warning  Unexpected 'todo' comment  no-warning-comments

/material-design-lite/src/switch/switch.js
  122:5  warning  Unexpected 'todo' comment  no-warning-comments

/material-design-lite/src/tabs/tabs.js
  88:7  warning  Do not use 'new' for side effects  no-new

/material-design-lite/src/textfield/textfield.js
  273:11  warning  Unexpected 'todo' comment  no-warning-comments

/material-design-lite/src/layout/layout.js
  520:11  warning  Do not use 'new' for side effects  no-new

✖ 8 problems (1 error, 7 warnings)

[12:08:59] 'lint:sources' errored after 811 ms
[12:08:59] ESLintError in plugin 'gulp-eslint'
Message:
    Failed with 1 error
[12:08:59] 'all' errored after 4.11 s
[12:08:59] Error in plugin 'run-sequence'
Message:
    An error occured in task 'lint:sources'.

Mocha tests seemed to pass
# tests 89
# pass 89
# fail 0
[12:09:31] Finished 'mocha' after 4.86 s

But then there was an error in the stream:
stream.js:74
      throw er; // Unhandled stream error in pipe.
      ^
Error: src/mdlComponentHandler.js:252: WARNING - invalid cast - must be a subtype or supertype
from: (Element|HTMLCollection|NodeList)
to  : (Array|null)
        elements = Array.prototype.slice.call(/** @type {Array} */ (elements));
                                                                   ^

0 error(s), 1 warning(s), 93.1% typed

Fixes LGTM.
cc @sgomes to peek at the failure happening. Looks like an unrelated closure compiler error from a cast. Not sure if we should merge this then fix or what.

@joemidi Just realized this is going into master which is an issue. Can you please re-submit the PR against mdl-1.1? Then I can go ahead and merge it in.
Anything affecting 1.1 goes into that branch, then it is merged up into master for future releases. We can't merge the other way due to compatibility issues with new code.

Ah right okay. Will close this and re-submit.


Supporting Undelete in BlobStoreStats class

Adding code to support Undelete in BlobStoreStats class.

Codecov Report

Merging #1474 into master will decrease coverage by 0.05%.
The diff coverage is 76.05%.

@@             Coverage Diff              @@
##             master    #1474      +/-   ##
============================================
- Coverage     73.27%   73.21%   -0.06%
+ Complexity     7917     7869      -48
============================================
  Files           559      560       +1
  Lines         43401    43649     +248
  Branches       5449     5502      +53
============================================
+ Hits          31803    31959     +156
- Misses        10019    10087      +68
- Partials       1579     1603      +24

Impacted Files
Coverage Δ
Complexity Δ

...rc/main/java/com/github/ambry/cloud/VcrServer.java
81.73% <ø> (ø)
8.00 <0.00> (ø)

...c/main/java/com/github/ambry/rest/NettyServer.java
71.15% <ø> (ø)
6.00 <0.00> (ø)

...c/main/java/com/github/ambry/store/IndexValue.java
95.07% <ø> (ø)
55.00 <0.00> (ø)

...in/java/com/github/ambry/store/BlobStoreStats.java
63.12% <32.98%> (-7.33%)
96.00 <1.00> (-8.00)

.../com/github/ambry/cloud/VcrReplicationManager.java
71.27% <50.00%> (-1.26%)
13.00 <1.00> (+1.00)
:arrow_down:

...main/java/com/github/ambry/store/IndexSegment.java
86.73% <56.52%> (-0.84%)
134.00 <9.00> (+1.00)
:arrow_down:

...ava/com/github/ambry/store/BlobStoreCompactor.java
90.90% <87.75%> (-1.22%)
114.00 <0.00> (-42.00)

...y/network/http2/Http2ClientStreamStatsHandler.java
95.23% <95.23%> (ø)
5.00 <5.00> (?)

...main/java/com/github/ambry/config/CloudConfig.java
100.00% <100.00%> (ø)
1.00 <0.00> (ø)

...ava/com/github/ambry/config/Http2ClientConfig.java
100.00% <100.00%> (ø)
1.00 <0.00> (ø)

... and 31 more

Continue to review full report at Codecov.

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


load add streamload header skip_locations

Proposed changes
Issue Number: close #xxx
Streamload is redirected to be. When the client and a be cannot be accessed (such as packet loss), an error will be reported to the client.
At this time, the client can skip the be by adding -H "skip_locations: <IP_ADDRESS>,<IP_ADDRESS>" to ensure the normal operation of the client.

run buildall

run cloud p1

run external


updated types-directory in package.json

solves issue 215

@jshor Please review this issue, it breaks the newest version of the package.


Console error when clicking on the confirmation checkbox when deleting a wallet

See error:

Steps to reproduce:

Create a new wallet
Click on "Delete wallet" in wallet settings
Click "I understand this is an irreversible action" checkbox
Notice the error in the console

Probably not a big deal but that error looks kind of scary.

Closed via #2847


Bigtable instance admin client OptionsSpan

See #8164 for a description.

This is the legacy instance admin client, it is deprecated so no new features on it


Make close safe to call multiple times

Fixes

Make it safe to call device.close() multiple times.

While the inline documentation is clear that the device must be open to call close(), it's an easy mistake to make to call close multiple times. This will appear to work most of the time, but if the Napi::ThreadSafeFunction in completionQueue has been destroyed by Node, then the Node process will crash (with SIGABRT in my case). This means the crashes may be intermittent and hard to root-cause.
The proposed change also makes Device::Open() and Device::Close() more similiar since Open() checks if (!self->device_handle) while Close() didn't check if (self->device_handle).
Context

device.close
Device::Close
UVQueue::stop
TypedThreadSafeFunction::Release
napi_release_threadsafe_function

Program to reproduce
const usb = require('usb');

const device = usb.findByIds(0x2b04, 0xc00c); // change to a device connected to your machine

device.open();
device.close();
setTimeout(() => {
	device.close(); // without the fix, Node crashes when this is called
}, 1000); // arbitrary delay to let Node clean up the TypedThreadSafeFunction

Checklist

[X] Tested the change acts as expected
[X] Checked the change doesn't remove or change existing functionality
[X] Considered how the feature impacts the product and tested around it (not just the happy paths)
[ ] Where possible, executed the hardware tests on multiple operating systems

You're welcome! I'm just glad to have found the root cause for this sporadic issue :)


Add kilosort data interface

This should close #451
Critically, this solves a bug in the recently _add_waveforms (see #472) when the return statement was not properly indented.
How to test the behavior?
I added a gin test for this that takes into account the fact that this is an object from spikeinterface.

@h-mayorquin Thanks!


[Proposal] OpenAPI for S3 multipart upload

Thanks!
Let's talk about the client having to specify the number of parts in advance.

Added this one as limitation, didn't want to open another API which I will not use.
Adding the new api "request for part(s) presign URLs" will not break or change the current API.

Thanks!

Thanks about the multipart upload complete api parts order, the response in the previous comment, I'll paste it here too:
Error Code: InvalidPartOrder

Description: The list of parts was not in ascending order. The parts list must be specified in order by part number.
HTTP Status Code: 400 Bad Request

Documented in https://docs.aws.amazon.com/cli/latest/reference/s3api/complete-multipart-upload.html


Regex and API mismatch (for at least container name length)

When calling the following
var liveOutputAsset = await client.Assets.CreateOrUpdateAsync(outputAssetName, containerName, "dev", "live output asset");
with a containerName with caps letters I get

Value does not respect regex pattern ^(?=.{3,63}$)[a-z0-9]+(-[a-z0-9]+)*$. (Parameter 'containerName')

also indicating that the lenght limit is between 3 and 63 but then if I fix my issue with containerName.ToLower() and pass it in I get this error from the API telling me its between 2 and 32.
Bad Request : Validation failed. Field name:'mladenblazortest-7961e6df-de353968' is invalid: ['Length must be between 2 and 32.']

Status: 400
Response:
{
  "error": {
    "code": "1000.2000.1000.1080",
    "detail": "Validation failed. Field name:'mladenblazortest-7961e6df-de353968' is invalid: ['Length must be between 2 and 32.']"
  },
  "ref": "695adf4c-1149-4827-a810-fceb464c2436",
  "status": 400
}

Hello, thanks for the issue.
The container name in Azure has the following restriction https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata#container-names which seem different from the message from MK.IO.
I will check with MediaKind.

This is strange, I cannot repro. My code :
// create asset
string name = "mladenblazortest-7961e6df-de353968";

// list assets
var mkioAssetsResult = client.Assets.List(null, $"name eq '{name}'", null, null);

// it works

Is dev really the name of your storage ?

Thanks.
I don't hit the API error telling that container name should between 2 and 32. I used your code and added .ToLower().
var outputAssetName = MKIOClient.GenerateUniqueName("MladenBlazortest").ToLower();
var containerName = "asset-" + outputAssetName;
var liveOutputAsset = await client.Assets.CreateOrUpdateAsync(outputAssetName, containerName, "eventstreamingdev", "live output asset");

I also test with longer name, without any issue.
var outputAssetName = MKIOClient.GenerateUniqueName("MladenBlazortest", 12).ToLower();

Ok sorry for this! I was mixing things up! Its the client.LiveEvents.CreateAsync code that has this error and not client.Assets.CreateOrUpdateAsync I just assumed it because that code is before the other one and I for some reason used a longer name after figuring out the ToLower() (at least I think I did that).
   var LiveEventName = "MladenBlazortestMladenBlazortest"; // for super long name
   var liveEvent = await client.LiveEvents.CreateAsync(MKIOClient.GenerateUniqueName(LiveEventName), "uksouth", new LiveEventProperties
   {
       Description = "live event description",
       Input = new LiveEventInput
       {
           StreamingProtocol = LiveEventInputProtocol.RTMP
       },
       StreamOptions = ["Default"],
       Encoding = new LiveEventEncoding { EncodingType = LiveEventEncodingType.PassthroughBasic }
   }, tags, CancellationToken.None);

The error message doesn´t say anything about what is causing the issue.. if it would have said something like

"The Live event name needs to have lenght between 2-32"

I would probably have cought it.

This makes sense. I can repro now. I am adding some checks and tests for the live event name (and also tags).

In latest release https://github.com/microsoft/MK.IO/releases/tag/v2.1.0


No id returned

I create an index and I add documents.
When:

searching
getting documents (multiple or not)
the API does not display the ids of the documents.

Steps

[ ] Fix in the code
[ ] Add tests to check this issue

Version
On the master branch, on this commit. Should be fixed for the v0.9.0.

https://github.com/meilisearch/MeiliSearch/blob/2b780ab2c5f2da2eb5e9475ff789da5cba11c359/meilisearch-core/src/update/settings_update.rs#L37-L42
At this time we should also add the identifier as displayed and indexed.


Use pydantic for ETL settings validation

So far I have created pydantic models for everything but ferc1_to_sqlite and CEMS.
Currently, I am specifying all individual dataset settings as attributes in DatasetsSettings. This works fine for now but in the future, we could dynamically add dataset settings by reading them in from a separate file.  I think we would still have to manually create validators to establish dependencies between datasets like eia 860 and 923.
We could also move these validators into the dataset pipelines on the prefect branch. That way the validators and actual pipeline are coupled. A super out-there idea is to have perfect dependencies be inferred from the validators or vice versa.

This is ready for another review.
Changes

GenericDatasetSettings now requires working tables and working partitions class variables. There can be an arbitrary number of partitions. create_dataset_settings(dataset_name) will dynamically create a field for each partition.
pc.WORKING_PARTITIONS and pc.PUDL_TABLES remain the one true place partition and table metadata.
I updated the development settings files docs.

Pydantic has made our settings validation cleaner and more reusable for future datasets. That being said, we can continue to improve on dynamically generating settings validation for new datasets. I wrote up a couple of issues (#1316) outlining my ideas.
I think dataset settings validation will continue to evolve as we integrate this branch with prefect and metadata updates.

Testing out one more change to etl_full.yml before merging this in.


cycle between band form neutrophil relationship and mature neutrophil

Cycle:

mature neutrophil develops_from: "band form neutrophil"
band form neutrophil subClassOf: "mature neutrophil"

This is not coherent, unless develops_from is reflexive, or band form neutrophils have existed for all of time...
This is preventing the uberon release, as we can't make a basic ontology (basic ontologies have no cycles in the graph).

Protege seems to hang when trying to open cl-edit -- I wonder if this is the reason?

Thanks Chris.


How to know when ad gets impression?

How to know when ad gets impression so to trigger reloadAd() fun ?

@EngDjango that could be an enhancement on next release


Window will not stay shown on launch for packaged .app

If I run the app from the command line with electron npm start I can have the menubar window start off as shown using either mb.window.show() or mb.showWindow().
However, once I package the app with electron-packager and launch the .app, the window flashes for a brief moment but won't stay shown.
menubar 2.2.1, electron 0.33.1, electron-positioner 2.0.2
var menubar = require('menubar')

var mb = menubar()

mb.on('ready', function ready () {
  console.log('app is ready')
  mb.window.show()
})

Hmm I have no idea why this is happening, sorry. Will leave it open in case someone else has ideas

In a fun turn of events, it works on Windows (8 at least).

this is most likely an electron issue, I would try to reproduce the issue
using plain electron (e.g. no require('menubar')) and open an issue there
to get it fixed
On Mon, Oct 19, 2015 at 11:13 AM, cwhits<EMAIL_ADDRESS>wrote:

In a fun turn of events, it works on Windows (8 at least).
—
Reply to this email directly or view it on GitHub
https://github.com/maxogden/menubar/issues/76#issuecomment-149301631.

Plain electron appears to work. It stays shown once built with electron-packager :confused:
var app = require('app');
var BrowserWindow = require('browser-window');

app.on('ready', function() {
var win = new BrowserWindow({ width: 800, height: 600, show: false });
win.on('closed', function() {
      win = null;
});

win.loadUrl('https://github.com');
win.show();
});

@cwhits oh try this menubar code:
var menubar = require('menubar')

var mb = menubar({preloadWindow: true})

mb.on('ready', function ready () {
  console.log('app is ready')
  mb.on('create-window', function () {
    mb.window.show()
  })
})

The only other info I have to add is that menubar.window thinks that it's visible. I added some logging to the menubar module's index.js file and the value of menubar.window.isVisible() is true right after the 'ready' emitter even though I can't see the window.

@maxogden That code doesn't help. Create-window doesn't seem to be emitted after ready. If I add a console.log('create-window emitted') above mb.window.show(), it never gets outputted.

alright. I'm on my phone now, but you might be able to figure it out by
looking at the menubar source code
On Wednesday, October 28, 2015, cwhits<EMAIL_ADDRESS>wrote:

@maxogden https://github.com/maxogden That code doesn't help.
Create-window doesn't seem to be emitted after ready. If I add a console.log('create-window
emitted') above mb.window.show(), it never gets outputted.
—
Reply to this email directly or view it on GitHub
https://github.com/maxogden/menubar/issues/76#issuecomment-151968424.

--
Sent from my phone

@maxogden I've added logs at almost every point in the menubar source and still couldn't figure it out. Everything appears to be doing what it's supposed to.
I've finally found a workaround but I don't understand why it works.
The screen won't stay displayed if I do:
    mb.on('ready', function ready () {
        mb.window.show()
    })

BUT if I add a 1ms timeout, it stays displayed...
    mb.on('ready', function ready () {
        setTimeout(function(){mb.window.show();}, 1);
    })

Try show the window on the after-create-window event.
var menubar = require('menubar')

var mb = menubar({preloadWindow: true})

mb.on('ready', function ready () {
  console.log('ready')
})

mb.on('after-create-window', function () {
  mb.window.show()
})

@jenslind Nope. It flashes briefly but doesn't stay open. Doing the 1ms timeout also works as a workaround there too.

After some investigation it looks like app.dock.hide() is causing this.
Removing it or moving it to after the window is created worked.

This is indeed the solution to this issue @jenslind. Should I make a PR for this?

Did anyone manage to solve this?


Enlarge volume for app-draft-frontend instances

Add new variable to main.tf to allow for a custom volume size.
One of the instances in the autoscaling group is running out of inodes
There doesn't seem to be anything significant we can delete, so we
are increasing the volume size.

The default block size value in the node_group module is 20GB. Is the intention here to override that value in all the environments with 40GB?


Block invite pages from search engines?

Part of #7166 improve search metadata

Should pages like https://odysee.com/$/invite/@apologeet:3 be searchable in the first place?
It is appearing in SiteLinks and search results, which isn't useful there.  We can no longer alter SiteLinks directly since it is now automated, but we can influence it:

[ ] Do that noindex thing mentioned above to prevent future crawls
[ ] I think Josh can purge all existing crawled items with the /$/invite/ pattern from Google Console.

@tzarebczan, your thoughts before I attempt the removal?

I'm okay with removing, and we'll see if @nikooo777 can purge.


Unique constraint violation: bad return value

ArangoXEcto version
1.3.1
Elixir and OTP version
1.15.7 - OTP 26
Ecto version
3.11.1
ArangoDB version
3.10.10
Steps to Reproduce

create persistent index on two fields (:name, :surname)
try to submit a form with name and surname fields already existing

Expected Behavior
changeset error should be returned
Observed Behavior
Exception raised:
[error] GenServer #PID<0.3183.0> terminating
** (stop) bad return value: "ArangoXEcto does not support rollbacks at this time"
Additional Context
No response

Hi @StevenG74, sorry it took a while to see this. Are you able to provide an example of your code?
As a side note, rollbacks will be supported in the next version.

Hi @TomGrozev, sorry for the delayed answer, I managed to write a simple app to reproduce the issue, and the problem seems to be solved, even in my original (production) app.
The demo app is this one:
https://github.com/StevenG74/arangodb_test
Thanks anyway for your support, and for the great job you are doing with this library.
Steven


Add private repo test

Fixes #79
Two of the examples remain untested: webhooks, termination.

Not working, as this PR has been opened from a fork (not a branch) and doesn't have access to repo secrets.
Using "pull_request_target" runs the workflow from the default branch with secrets, but makes it impossible to iterate with testing on new workflows in PRs...


Add a recommendation module in product detail page

Is it possible to add a recommendation list on product detail page?

Hi @jiamuyang
Cezerin has Related Products - list of products which will be listed on the product detail page.
Is this what you looking for?


API CHANGE: Change all private methods and properties to protected

Addresses this issue: https://github.com/sabberworm/PHP-CSS-Parser/issues/56

Can you rebase this against the current master and I will merge it.


Make screenshot url in README absolute

On the Hugo theme site the screenshot in your README isn't shown because a relative path is used that doesn't correspond to the directory structure on https://themes.gohugo.io/

Fixed in commit<PHONE_NUMBER>9502bdd7d3b54584c5dc98198c5d15


Removing !important statements from theme variables

Also, fixing stale theme loading error (kontena-dark gets replaced by lens-dark)
Fixes #1292

Signed-off-by: Alex Andreev<EMAIL_ADDRESS>

Thank you! 😄


feat(@angular/cli): support passing files to ng lint, closes #7612

This works for the described use cases like with lint-staged or anything else which expects ng lint to accept files as args similarly to tslint.
ps: my first PR ever so be kind thank you!

Link to original issue.

@Brocco can you review and see how it fits into https://github.com/angular/angular-cli/issues/7612?

Closing this in favor of the Architect effort; you can now specify which app/lib you want to lint.

@hansl That's not useful if you want to use libraries like lint-staged--like the OP stated.

@hansl closing the PR seems to be not reasonable. What the users want is perform linting on target files, but not particular sub projects.

@hansl The main reasons this feature is requested are:

Linting entire apps/libs/projects is very resource/time intensive
It's valuable to lint files before committing them

Your rationale for closing this is a solution that shaves millimeters off of a meter long issue.


Updates / project status?

@handnot2 I've noticed merge requests have been sitting open a for a while, and with OTP 24 out now deprecated some functions used here, are you still interesting in maintaining this project moving forward? If not, would you consider letting others help out in some fashion?
I know this work has been hugely valuable for me to do some SSO integrations I would not have been able to do (via samly) otherwise, and am willing to pitch in to make sure both remain viable going foward.

@jamesvl agreed, I think it would be useful for the community if this project were more actively maintained. I believe the BSD license allows the work to be modified and would be supportive of moving the maintenance effort to a fork if this repository is no longer active.
@handnot2, @arekinath many thanks for all your work on esaml. Please respond if you would rather continue to use this repo for maintaining esaml.

I'm happy to create a "esaml" org account and move the original repo there, and give handnot2 admin on the org (and commit access to others who are maintaining it), if that seems useful?

I'd certainly be willing to help triage or do reviews if we pursued this path.
Having an official move of the repo would be nice for anyone using the hex packages; it would be ideal to avoid creating a new hex project if we could.

@arekinath the esaml org account seems like a good idea to me... the only issue is that @handnot2 doesn't seem to be responding and has no contribution activity since april 2019, so it might be a good idea to have some other admins from the community (@jamesvl or myself, for example).
What do you think?

I have forked this to maintain it through dropbox here: https://github.com/dropbox/esaml
I'm currently in the process of getting ownership of the project through hex.pm too. Are there any other places that I should try to take over ownership? I've been handling all of the corporate takeover stuff since October.


Fix compilation of Jacobian with for loops and vmap

Context:
Some gradients/jacobians do not compile because the insertion point in the lowering is not correctly set.
Description of the Change:
The insertion is the call op and not the body of the function.
Benefits:
We can compile and run more derivatives of vmap and for loop.
[sc-59758]

Testing this fix on the following example results in very long (infinite?) compile or runtime:
import pennylane as qml
import jax
from jax import numpy as jnp
import catalyst

n_wires = 5
data = jnp.sin(jnp.mgrid[-2:2:0.2].reshape(n_wires, -1)) ** 3
targets = jnp.array([-0.2, 0.4, 0.35, 0.2])

dev_name = "lightning.qubit"
dev = qml.device(dev_name, wires=n_wires)

@qml.qnode(dev)
def circuit(data, weights):
    """Quantum circuit ansatz"""

    for i in range(n_wires):
        qml.RY(data[i], wires=i)

    for i in range(n_wires):
        qml.RX(weights[i, 0], wires=i)
        qml.RY(weights[i, 1], wires=i)
        qml.RX(weights[i, 2], wires=i)
        qml.CNOT(wires=[i, (i + 1) % n_wires])

    return qml.expval(qml.sum(*[qml.PauliZ(i) for i in range(n_wires)]))

# try broadcasting
jit_circuit = catalyst.qjit(catalyst.vmap(circuit, in_axes = (1, None)))

def my_model(data, weights, bias):
    # works with default.qubit
    if dev_name == "default.qubit":
        return circuit(data, weights) + bias

    # works with lightning.qubit, not broadcasted
    # return jnp.array([circuit(jnp.array(d), weights) for d in data.T])

    # only works with loss_fn, fails at grad step
    return jit_circuit(data, weights) + bias

@jax.jit
def loss_fn(params, data, targets):
    predictions = my_model(data, params["weights"], params["bias"])
    loss = jnp.sum((targets - predictions) ** 2 / len(data))
    return loss

weights = jnp.ones([n_wires, 3])
bias = jnp.array(0.)
params = {"weights": weights, "bias": bias}

print(loss_fn(params, data, targets))
print(jax.grad(loss_fn)(params, data, targets))  # runs for > 20 minutes

Closes https://github.com/PennyLaneAI/catalyst/issues/294


Cannot overwrite message callback

When using ColyseusRoom.OnMessage twice on the same message ID, I get the following exception:
ArgumentException: An item with the same key has already been added. Key: myMessage

An easy fix would be to modify the OnMessage method to take in consideration if a previous message with the given id already exists. However, I wanted to know if this is a bug or a real design choice before submitting a PR.

I made a pull request (#199) containing a solution like the example you provide :)


Add NZ English and Te Reo to UK Extd

FYI, this corresponds to v 2.0 on the web store

Thanks @colmbuckley for merging this


use canon to lookup jumandic in seq2seq module

Codecov Report

Merging #159 (bc9afd4) into dev (031ceba) will decrease coverage by 0.16%.
The diff coverage is 84.90%.

@@            Coverage Diff             @@
##              dev     #159      +/-   ##
==========================================
- Coverage   86.93%   86.78%   -0.16%
==========================================
  Files          58       58
  Lines        5030     5041      +11
==========================================
+ Hits         4373     4375       +2
- Misses        657      666       +9

Impacted Files
Coverage Δ

src/kwja/callbacks/word_module_writer.py
87.58% <71.42%> (-1.01%)
:arrow_down:

src/kwja/utils/jumandic.py
90.90% <86.95%> (-9.10%)
:arrow_down:

... and 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Problem with loading related entities after Select()

Hi
Currently I am walking through one of ASP.NET tutorials and I`m trying to run it on ASP.NET Core (with EF Core). However there is a problem with one of LINQ queries like below. It should return a collection of Notification objects with Artist and Genre, but it returns only Notifications with Artis nad Genreset to null (UserNotifications is a many-to-many relationship between Notifications and User; Notifications is related to Gig ang Gig to Artist).
var userId = User.FindFirst(ClaimTypes.NameIdentifier).Value;
        var notifications = _context.UserNotifications
            .Where(un => un.UserId == userId)
            .Select(un => un.Notification)
            .Include(g => g.Artist)
            .Include(g => g.Genre)
            .ToList();

Problem seems to be solved when I add the following query before:
        var notificationsTest = _context.Notifications
            .Include(u => u.Gig).ThenInclude(u => u.Artist)
            .ToList();

Why this happens and How can I put this in a single LINQ query in EF Core?
Further technical details
EF Core version: 1.0.0
Operating system: Windows 10
Visual Studio version: VS 2015 U3

Select overrides Includes
See this https://github.com/aspnet/EntityFramework/issues/6177#issuecomment-236229259
(I think it's very confusing and not intuitive, but that's how it works.)

Does this change somehow from EF6 to EF Core, because according to tutorial this query should works on old EF?
How should this query looks like to also return related entities?

@bartekkois

No idea, I used EF 6 only for a short while, and it was in a project with a crappy architecture and codebase.

You already answered it in your issue, just remove the Select, use Include and ThenIncldue currently you can't traverse back the tree, so you need to start again:
var notifications = _context.UserNotifications
.Where(un => un.UserId == userId)
.Include(un => un.Notification)
.ThenInclude(g => g.Artist)
.Include(un => un.Notification)
.ThenInclude(g => g.Genre)
.ToList();

p.s. I'm not a MS employee, you might want to wait for an official answer, but that's is AFAIK the answer.

What @gdoron suggested is the correct workaround.

@bartekkois I am going to mark this as an answered question, but:

Feel free to re-open if the answer doesn't work.
It would be great if you could point us to the exact tutorial page where you found something similar so that we can make sure that there is no bug in the tutorial.

FWIW, I don't think this query would have returned the related entities in EF6 either. In EF6 the paths passed to Include() have to represent valid navigation paths from the result type of the query.

I have found that exmaple in https://app.pluralsight.com/library/courses/full-stack-dot-net-developer/table-of-contents. Exactly two of them:
        var gigs = _context.Attendances
            .Where(u => u.AttendeeId == userId)
            .Select(a => a.Gig)
            .Include(a => a.Artist)
            .Include(g => g.Genre)
            .ToList();

        var notifications = _context.UserNotifications
            .Where(un => un.UserId == userId && un.IsRead == false)
            .Select(un => un.Notification)
            .Include(g => g.Gig.Artist)
            .ToList();


mcmc dimnames with samplesAsCodaMCMC=TRUE have empty space

Compared to standard JAGS implementations the mcmc object generated by nimble with the option samplesAsCodaMCMC=TRUE has empty spaces after the comma in dimnames.
varname[1, 1]
instead of
varname[1,1]
This can break code used for JAGS before, for example when relying on the tidybayes package. A change to the way rjags saves the dimnames might be worth considering.

@Schmidtpk Thanks for the suggestion.  We will look into this.

@Schmidtpk Thanks for the suggestion.  We will look into this.

@Schmidtpk @danielturek I note that the version with the space corresponds to node names in nimble, and also to the R parse and deparse system (the reason for nimble's syntax for node names):
deparse(parse(text = "varname[1,1]")[[1]]) returns "varname[1, 1]"
Maybe a utility function (rather than an option) to rename as JAGS would be helpful?

@Schmidtpk @danielturek I note that the version with the space corresponds to node names in nimble, and also to the R parse and deparse system (the reason for nimble's syntax for node names):
deparse(parse(text = "varname[1,1]")[[1]]) returns "varname[1, 1]"
Maybe a utility function (rather than an option) to rename as JAGS would be helpful?


Create tushar.md

Thanks @tusharkashyap63 :+1:

@johnjacobkenny can you help me when I am syncing my forked repo this file(TUSHAR.md) is colliding with a file named 'tushar.md'

@Sheetal777 would you like to help out here 🙂

@Sheetal777 would you like to help out here 🙂

Oh sorry, I think it's fixed now! 😅

@vijaya-bhaskar I already fixed it.


Error key "MustardUI" not found on blender-4.2.0-alpha+main.38fcaf9ab93f-windows.amd64-release.

Good source code and tools for Mustard ...
I get this error on blender-4.2.0-alpha+main.38fcaf9ab93f-windows.amd64-release

Seems like an error in the installation. Always install the add-on downloading the package from the release pages:
https://github.com/Mustard2/MustardTools/releases
https://github.com/Mustard2/MustardUI/releases
https://github.com/Mustard2/MustardSimplify/releases
That is, downloading from the main GitHub page of the project messes up with the file names, ending in this particular error.


js9_node sync is not working

Installation information

jumpscale version: 9.3
operating system: ubuntu

Detailed description
js9_node sync is not working, I'm getting jumpscale code management always requires path in form of $somewhere/code/$type/$account/$reponame error in tmux when I'm trying to execute
js9_node sync -i gw-andrew -m
Steps to reproduce
js9_node sync -i gw-andrew -m
Relevant stacktraces
Traceback (most recent call last):
  File "/usr/local/bin/js9_node", line 152, in <module>
    cli()
  File "/usr/local/bin/js9_node", line 107, in monitor
    node.sync(monitor=True)
  File "/opt/code/github/jumpscale/core9/JumpScale9/tools/nodemgr/Node.py", line 234, in sync
    ddirs = self.getActiveCodeDirs()
  File "/opt/code/github/jumpscale/core9/JumpScale9/tools/nodemgr/Node.py", line 217, in getActiveCodeDirs
    repo = j.clients.git.currentDirGitRepo()
  File "/opt/code/github/jumpscale/core9/JumpScale9/clients/git/GitFactory.py", line 32, in currentDirGitRepo
    return self.get(res)
  File "/opt/code/github/jumpscale/core9/JumpScale9/clients/git/GitFactory.py", line 590, in get
    return GitClient(basedir, check_path=check_path)
  File "/opt/code/github/jumpscale/core9/JumpScale9/clients/git/GitClient.py", line 51, in __init__
    "jumpscale code management always requires path in form of $somewhere/code/$type/$account/$reponame")
JumpScale9.errorhandling.JSExceptions.Input: ERROR: jumpscale code management always requires path in form of $somewhere/code/$type/$account/$reponame ((type:input.error)
jumpscale code management always requires path in form of $somewhere/code/$type/$account/$reponame

That's how code paths should be indeed. Will close this because it's a requirement of jumpscale architecture


Propagate error status for retriable errors

When Service Catalog reports status with a temporary error, it doesn't set the Failure condition. It has only Ready condition with status: False and reason/message describing a temporary error.
Example:
  conditions:
  - lastTransitionTime: 2018-09-19T03:25:56Z
    message: 'Error provisioning ServiceInstance of ClusterServiceClass (K8S: "<redacted>"
      ExternalName: "sqs") at ClusterServiceBroker "aws-broker": Status: 409; ErrorMessage:
      <nil>; Description: Service instance with the given ID already exists: serviceInstanceId=<redacted>,
      serviceDefinitionId=<redacted>; ResponseError: <nil>'
    reason: ProvisionCallFailed
    status: "False"
    type: Ready

When Smith is processing such status, it simply reports with "InProgress: True" and no additional message/reason, e.g.
    - conditions:
      - lastTransitionTime: 2018-09-19T03:19:58Z
        lastUpdateTime: null
        status: "False"
        type: Blocked
      - lastTransitionTime: 2018-09-19T03:19:58Z
        lastUpdateTime: null
        status: "True"
        type: InProgress
      - lastTransitionTime: 2018-09-19T03:19:58Z
        lastUpdateTime: null
        status: "False"
        type: Ready
      - lastTransitionTime: 2018-09-19T03:19:58Z
        lastUpdateTime: null
        status: "False"
        type: Error
      name: perftest-queue--instance

@benbarclay another issues that is almost a duplicate of this one is https://github.com/atlassian/smith/issues/317. That one is about propagating "in progress" while this one is about error conditions. Feel free to solve both in a single PR 🤷♂


Improve documentation on the all module

Improve documentation on the all module by doing:

Document guarantee that all will only ever contain opcode constants
Fix stale/incorrect code comment

Done as follow up to #1295

Removed code comment as suggested.

CI failure is in master. I will PR to fix it.

I will PR to fix it.

Woops, I missed that comment :)

I forgot about Kix's suggestion about guaranteeing opcodes start with OP_, now its added.

Oh, I'd like to keep "Ord and PartialOrd intentionally not implemented." comment and even make it a doc comment.

Added new patch using text from comment above by @apoelstra

Rebased on master, no other changes.

I've force pushed changes that hopefully implement review suggestions. Please review carefully because the Core bug described is totally unknown to me and I did not go digging in Core source code looking for it. Also I re-worded the suggestion to mention All::classify, I believe that is what was meant by "Please use the associated methods on Opcode to distinguish different types of opcodes."

I'm happy with this. I think maybe Core developers might dispute this being a "bug" but I think it is :) and anyway I don't think it'd be a big deal if we had to change it later.


Update README.rst

Corrected DELETE /sessions/{batchId} to DELETE /sessions/{sessionId}

Good catch, thanks!

And if you have time to sign the CCLA (take 30s) it would be awesome! https://docs.google.com/forms/d/1DVn3B5_fntw0QByIOq8TsAUnz32noAy-wYS7hq6le5M/viewform


sourceIcon flag is not used

The commandline docs indicate sourceIcon can be used, but it doesn't work

Resolved by @morcerf in #31


privacy policy page built

Related Issue
#1439
Description
Built the whole privacy policy page and link it to the whole site.
Screenshots:

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist:

[ ] I have performed a self-review of my code
[ ] I have read and followed the Contribution Guidelines.
[ ] I have tested the changes thoroughly before submitting this pull request.
[ ] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

conflict issue

conflict issue

Okay sir will fix it and ping you back

@arghadipmanna101 sir conflicts fixed please see now


A lot of warnings in -Wunused-but-set-variable and Wunused-variable

I grep our TeamCity log. There are 816 -Wunused-but-set-variable and  386 -Wunused-variable warnings come from OpenBLAS: https://github.com/PaddlePaddle/Paddle/issues/3281#issuecomment-344138280
Do you have any plans to fix these warnings?
Looking forward to your reply!

While I can only speak for myself, I did not see them as an immediate priority problem so far given the lack of active developers on this (mainly) volunteer project. Also when this topic last came up months ago I did not want to touch the level3 blas code as it seemed another developer was actively working on the affected functions. Fixing the warnings should be straightforward if time consuming, but I would hate to clean up harmless declarations of currently unused things that actually may be hooks already put in place for later developments. (Though most likely the majority will simply be leftovers from cut-and-paste coding.)
Did you experience any problems in connection with these warnings, or is this just that it creates an unfavorable impression about the general quality of the code ?

Regarding the warnings arising from the fallback code in kernel/generic, I guess I could offer the additional excuse that these are historic slips of the pen, written by Kazushige Goto a decade ago for what was then libGoto or GotoBLAS. So they have been there from the beginning of (our) time :-)

Thanks for your quick reply.

Did you experience any problems in connection with these warnings, or is it just that this creates an unfavorable impression about the general quality of the code

We didn't experience problems, but it creates a very long log for our teamcity.

Fixing the warnings should be straightforward if time consuming

How about add Wunused-but-set-variable and Wunused-variable in flags such as CMAKE_CXX_FLAGS, which can avoid these warnings?

Suppressing the warnings will probably draw criticism from others for sweeping things under the rug...
At least for the "historic" codes in kernel/generic, the messages arise from varying macro expansion as often in OpenBLAS the same source file is compiled into multiple related functions for handling float/double/complex input etc. So "fixing" would mean adding a ton of #ifdefs rather than just commenting or removing truely unneeded lines. It is quite likely that this applies to the level3 blas codes as well, while at least the j and at[] variables in the x86_64 gemv and symv kernels appear to be genuinely useless. (Still time that could be spent on fixing actual bugs that lead to actual errors)

One other thing to consider is that when you are doing a build with DYNAMIC_ARCH=1 to allow runtime selection of code for a wide range of cpus, you will be compiling the same source files over and over where they are shared with or without small adjustments between cpu models. So the actual number of unique files is much smaller than the impressive number of 800 warnings that will only jump up whenever support for another related cpu is added. (And the actual number of unique issues is smaller still, as the same file may contain several computations where one of the arguments is unused under certain build-time circumstances.)
As an aside, if your coworker thinks a project must be poorly maintained if it has 150 open issues of widely varying severity, maybe he should look at tensorflow, numpy or julialang...

Dead code causing both warnings  is optimized away with any optimizing compiler anyway. i.e fix would be cosmetic for build process but noop for code generated

Hmm. The unused-but-set warning about n in level3_gemm3m_thread.c may point to an actual shortcoming in the code where (I think) it may theoretically create threads even for very small workloads when range_m or range_n is set and either range does not correspond to the m or n argument. (m and in particular n is calculated from the range limits, but args->m, args->n are used in the decision - I guess that translates into "for operations on submatrices, the dimensions of the entire matrix are still used to decide whether or not to multithread here"). Not sure about actual impact, at least this has been unchanged since libGoto.
The kernel/generic/zgemm_?copy_ stuff on the other hand is probably best masked with a cast to (void) as the alternative would be adding a ton of ifdefs. As mentioned above, actual use of these
variables depends on which flavor of zgemm_?copyi, ...r, or ...b is getting built from the single source.

clang4 picks on a bit more like unused after increment that gcc cannot notice. I will take on those, it is mostly no-brain work.

@martin-frbg @brada4 Thanks very much for your quick pull request!
Besides, there are 18 near initialization warnings come from OpenBLAS: https://github.com/PaddlePaddle/Paddle/issues/3281#issuecomment-344852001

https://github.com/PaddlePaddle/Paddle/pull/5704 compile OpenBLAS with -Wno-unused-but-set-variable -Wno-unused-variable temporary to avoid long log.

That's actually
setparam_PRESCOTT.c:560:60: warning: initialization from incompatible pointer type
setparam_PRESCOTT.c:560:60: note: (near initialization for 'gotoblas_PRESCOTT.zgeadd_k')

repeated for all the 18 cpu variants in the build due to some confusion if the third argument to zgeadd_k should be a float or a double. The majority claims "double"), only common_param.h thinks it is a float - let me see who wins...

I believe these warnings have been all but eliminated now, at least for the x86 DYNAMIC_ARCH case.
Remaining warnings are mostly (imported) from netlib lapack, and should probably be fixed in that codebase first. OK to close ?

@martin-frbg still the cross targets (w32 for example) are not handled. Also many -Wunused-but-set are left, I fixed only part that gcc dos not see of that class - unused-but-incremented( += etc), which made half clang warnings earlier.
Lots of editing still ahead to clear output mentioned here.

Code cleanup can continue (though it is probably best to comment offending lines instead of removing them, so that any wrong assumptions or unfinished plans remain visible, in particular in original K.Goto code). I was only suggesting that the issues within the scope of this particular ticket have been resolved.

They are being resolved, prioritising parts that change code (and are more suspect to unearth bugs) ;)

Also assembly kernels that get called fortran style (i.e with pointer arguments where assembly accesses RW pointed-to data) are not understood and warning gets generated.
In principle they could be wrapped with pragma directives to silence misguided compiler warning. @martin-frbg ?

Which compiler are you seeing this with ? Offhand this sounds more like a compiler problem, and I am not too keen on making purely cosmetic changes all over the place just to silence a pointless warning generated by a particular compiler version that may not even affect many people.

I agree. It is gcc

gcc but using some uncommon warning options I assume ? With 7.2.0 at -Wall (or even with the two options from the original issue topic), I notice a handful of the newfangled "misleading indentation" warnings and a few complaints about uninitialized variables in the tests, but the vast majority of warnings now is caused by coding style issues in netlib lapack. Hence my earlier suggestion to close this issue rather than embark on a coding style witchhunt just to placate a single (perhaps overly) picky compiler.

only out of warnings i addressed that look loke bugfixes were =0.0 and to lesser degree dead increment. Rest is plainly cosmetic.

Actually just a dozen of libm fabs and very few type mismatch warnings are left in plain make.
clang analyzer just misses asm, and sets some rarely used warning types

I think it is cleaned as much as possible. I will look other time at my yesterdays edits and make PR
is@localhost:~/OpenBLAS> make CC=gcc NO_CBLAS=1 DYNAMIC_ARCH=1 FC=DISABLED MAKE_NB_JOBS=-1 -s -j 5 2>&1 | tee ../gcc7.out
OpenBLAS: Detecting fortran compiler failed. Cannot compile LAPACK. Only compile BLAS.
ar: creating ../libopenblasp-r0.3.0.dev.a
OK.

 OpenBLAS build complete. (BLAS)

  OS               ... Linux
  Architecture     ... x86_64
  BINARY           ... 64bit
  C compiler       ... GCC  (command line : gcc)
  Library Name     ... libopenblasp-r0.3.0.dev.a (Multi threaded; Max num-threads is 6)

To install the library, you can run "make PREFIX=/path/to/your/installation install".

clang5
fabs() is defined for long double args as same as fabsl(), so warning is fake.
probably unused function had great future intended. It is shorter than warning text, and does not make any side effect at all.
is@localhost:~/Templates/OpenBLAS/trunk> make CC=clang NO_CBLAS=1 DYNAMIC_ARCH=1 FC=DISABLED MAKE_NB_JOBS=-1 -s -j 5 2>&1 | tee ../clang5.out
OpenBLAS: Detecting fortran compiler failed. Cannot compile LAPACK. Only compile BLAS.
rotg.c:25:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da);
                    ^
rotg.c:25:21: note: use function 'fabsl' instead
  long double ada = fabs(da);
                    ^~~~
                    fabsl
rotg.c:26:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double adb = fabs(db);
                    ^
rotg.c:26:21: note: use function 'fabsl' instead
  long double adb = fabs(db);
                    ^~~~
                    fabsl
2 warnings generated.
rotg.c:25:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da);
                    ^
rotg.c:25:21: note: use function 'fabsl' instead
  long double ada = fabs(da);
                    ^~~~
                    fabsl
rotg.c:26:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double adb = fabs(db);
                    ^
rotg.c:26:21: note: use function 'fabsl' instead
  long double adb = fabs(db);
                    ^~~~
                    fabsl
2 warnings generated.
zrotg.c:17:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da_r) + fabs(da_i);
                    ^
zrotg.c:17:21: note: use function 'fabsl' instead
  long double ada = fabs(da_r) + fabs(da_i);
                    ^~~~
                    fabsl
zrotg.c:17:34: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da_r) + fabs(da_i);
                                 ^
zrotg.c:17:34: note: use function 'fabsl' instead
  long double ada = fabs(da_r) + fabs(da_i);
                                 ^~~~
                                 fabsl
2 warnings generated.
zrotg.c:17:21: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da_r) + fabs(da_i);
                    ^
zrotg.c:17:21: note: use function 'fabsl' instead
  long double ada = fabs(da_r) + fabs(da_i);
                    ^~~~
                    fabsl
zrotg.c:17:34: warning: absolute value function 'fabs' given an argument of type 'long double' but has parameter of type 'double' which may cause truncation of value [-Wabsolute-value]
  long double ada = fabs(da_r) + fabs(da_i);
                                 ^
zrotg.c:17:34: note: use function 'fabsl' instead
  long double ada = fabs(da_r) + fabs(da_i);
                                 ^~~~
                                 fabsl
2 warnings generated.
ar: creating ../libopenblasp-r0.3.0.dev.a
setparam_PRESCOTT.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_CORE2.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_PENRYN.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_DUNNINGTON.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_NEHALEM.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_OPTERON.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_OPTERON_SSE3.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_BARCELONA.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_BOBCAT.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_ATOM.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_NANO.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_SANDYBRIDGE.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_BULLDOZER.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_PILEDRIVER.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_STEAMROLLER.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_EXCAVATOR.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_HASWELL.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
setparam_ZEN.c:673:23: warning: unused function 'get_l3_size' [-Wunused-function]
static __inline__ int get_l3_size(void){
                      ^
1 warning generated.
OK.

 OpenBLAS build complete. (BLAS)

  OS               ... Linux
  Architecture     ... x86_64
  BINARY           ... 64bit
  C compiler       ... CLANG  (command line : clang)
  Library Name     ... libopenblasp-r0.3.0.dev.a (Multi threaded; Max num-threads is 6)

Can't we give that a rest ? I am not even sure that fabsl would be portable across all supported platforms.

Primary concern of unmanageable warnings is addressed on concerned platform+compiler combination as far as OpenBLAS hands could reach.
Those 2 warnings are just noise. I share your doubt about fabsl()
Probably I will check around i386 as/if time permits, maybe aarch64 if i get gadget of that sort.


fix: fixing semantic-release failure

dependency: none
PR summary
Fixing Semantic-release failure
Fixes:

https://app.travis-ci.com/github/IBM/networking-java-sdk/jobs/622908556
PR Checklist
Please make sure that your PR fulfills the following requirements:

[ ] The commit message follows the Angular Commit Message Guidelines.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[x] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

What is the current behavior?

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

:tada: This PR is included in version 0.37.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Added missing types

Hi. Thanks for the awesome library.
The type definition looks outdated so I fixed it.

Coverage decreased (-0.4%) to 94.468% when pulling a401c94a770a11e914b57f262c9b1e4ca7d8848d on mu29:fix/types into 08e8bbeaa76c5ec194abea388a193bedac7f35fc on fridays:master.


Add the marker cluster

Too Many Markers, has support map cluster?
thanks

Not yet but hopefully soon. I'm already talking to a developer who included this. We try to get this out real quick

Will add the cluster by the end of the week


Iss 139 upgrade hooks form

Related Issue
Resolves #139
Description

Made code changes to update react-hooks-form from v6 to v7.

Impacted Areas in Application
Packages:

Updated react-hooks-form to latest version
Updated TypeScript to latest version (TS 4.3 or above was required)

Forms:

Updated syntax for register method
Updated syntax for error object

Steps to Test or Reproduce

Tested form submits correctly.
Tested error checking and error messages show correctly.

Related PRs
If you PR is related to other part of PR, list them here

PR Checklist:

[x] My code follows the style guidelines of this project and I have double check my own code
[ ] I have made corresponding changes to the documentation, if any
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have run npm run test and be sure all test pass
[x] I have run npm run build:dev and be sure no error blocks the build
[x] I have test locally that everything run as expected
[x] I have properly fill in the PR template
[x] I have ask for reviews

@gsambrotta Were you hoping to have tests added for the Contact and Subscribe forms? I don't mind adding those.

Thank you very much @karlrez!
I'm checking the PR in these days but looks great.
We are upgrading to react 18 and there seems to be an issue with enzyme.
We probably need to remove it.
Any chance you have some free time to help with migrating all the tests from enzyme to react test library?

Thank you very much @karlrez!
I'm checking the PR in these days but looks great.
We are upgrading to react 18 and there seems to be an issue with enzyme.
We probably need to remove it.
Any chance you have some free time to help with migrating all the tests from enzyme to react test library?

Hey @gsambrotta! For sure, I would be interested in migrating the tests. I do have a few prior commitments, so I might be about two weeks or so until I have a PR up. If you still want me to go ahead, can you let me know which test files you guys want migrated over?

@karlrez that would be very very helpful! :tada:
I finally manage to fix all the dependencies to React 17.0.2 so we should be ok with waiting a couple of weeks before upgrading to react 18.
The tests are the ones that still use Enzyme.
It should be:

AllResultsView
Footer
SubscribeForm
ImagesView
ButtonPrimary
Header
Hero
Map
NewsView
SearchBar
Toast
Tooltip
app

Not all the test cases inside those files use Enzyme. Most of the time is just 1 or 2 test cases for each file.
I will write an Issue for this task

@gsambrotta sounds good! Feel free to assign me to the issue once it is up.

I close this in favor of pr #172 which is the same just with a merge conflict from the last push from develop branch.


Dataset load for benchmarking

Added a utility for loading dataset from hugging face

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@HashemAlsaket Sure, I am trying it but when I am pulling the main branch it shows:
Your branch is up to date with 'origin/main'.
But the #72 changes are not present in my local system
Could you guide here?


Improve gdb pretty-printer for newer libstdc++

These changes were adapted from the most recent gcc source

rebase!

@tcojean thanks for finding the source :)


Error on large contexts & memory usage

When having a "long" conversation and an increasing context window, ollama run will sometimes report an error:
"http://<IP_ADDRESS>:11434/api/generate": EOF"

This also may occur if there is insufficient memory. Ollama should handle these cases gracefully.

Hello.  I get the error anytime I go over ~1200 tokens, regardless of the model.  num_ctx is set to 4096.  I'm on an M2 Mac with 96 GB memory and 64 GB free.  It occurs both via the command line and HTTP.  Thanks.  Otherwise, your product is wonderful.  Excellent work.

There are a lot of stability improvements release in 0.0.13 which should address this and other Post "http://<IP_ADDRESS>:11434/api/generate": EOF issues

These errors should be gone (or at least far better) as of 0.13 – will close this for now but do feel free to re-open if it happens again!


Allow passing options

We need to allow passing in options to TSLint, so we'll be able to support mocha.
This requires this PR to be merged first: https://github.com/kratiahuja/broccoli-tslinter/pull/28

My plan was to follow ember-cli-eslint and use the chai tests automatically when someone is using mocha in the ember project already.


Hang when invoking async code synchronously from a sync context

Description
Sometimes I need to run async code synchronously, such as when an Apple framework API calls my closure (no async support) and requires a result from it, but the code required to retrieve that result is async.  In an ideal world this wouldn't occur, but in typical macOS and iOS GUI programming it occurs quite often.
And conceptually this is trivial; indeed in prior paradigms like NSRunloop this sort of pattern was easy to implement, since runloops were re-entrant.  There's no such API available to me for Swift Concurrency, as far as I'm aware.
I've almost got it working with Swift Concurrency, without runtime issues and compiler complaints, but I'm stuck on the last hurdle and I'm not sure it's not a compiler / stdlib bug.
Reproduction
import Dispatch

extension Task {
    static func sync(_ code: () async throws(Failure) -> Success) throws(Failure) -> Success {
        let semaphore = DispatchSemaphore(value: 0)

        nonisolated(unsafe) var result: Result<Success, Failure>? = nil

        withoutActuallyEscaping(code) {
            let sendableCode = unsafeBitCast($0, to: (@Sendable () async throws -> Success).self)

            _ = Task<Void, Never>.detached(priority: .userInitiated) { @Sendable () async -> Void in
                do {
                    result = .success(try await sendableCode())
                } catch {
                    result = .failure(error as! Failure)
                }

                semaphore.signal()
            }

            semaphore.wait()
        }

        return try result!.get()
    }
}

Expected behavior
Everything runs fine, life moves on.
The actual behaviour is that it just silently hangs at runtime, even though the code compiles without any complaints in Swift 6 mode.  The code closure is never actually invoked; the Task's closure seems to just silently hang when trying to call it.  There is no evidence of it anywhere in any thread's callstack (the thread running sync is stuck on the semaphore.wait()).
Yet if I mark the code parameter as @Sendable, it works fine.  However, then I'm erroneously requiring code to be sendable and it causes design and implementation problems for the caller (mainly re. capture local state, which isn't and shouldn't have to be sendable because there's no concurrency or escaping involved).
My only hypothesis so far is that it's trying to force code to run on the same thread as sync is called on, thus a fairly pedestrian deadlock, but: I don't know why (the code closure isn't intentionally bound to any particular isolation context) and I don't understand how merely making the closure @Sendable somehow changes that.  Thus why I'm wondering if this is actually expected behaviour in any sense, or rather a bug.
I tried in vain every possible attribute and modifier I could think of (lots of nonisolated stuff, @_inheritActorContext, etc), even stuff I didn't expect to work merely for completeness, and nothing has helped.
Environment
Xcode 15 beta 5.
swift-driver version: 1.113 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.6 clang-16<IP_ADDRESS>)
Additional information
No response

I believe your analysis is correct. The signature of this function is promising that code, because it is non-Sendable, cannot change isolation domains. And if this function is called from a non-isolated context, I think it will always be called synchronously. But the unsafeBitCast is why this unsupported arragement isn't being caught at compile time.
I'm pretty sure your only options are to mark the code closure Sendable or sending.

My only hypothesis so far is that it's trying to force code to run on the same thread as sync is called on

What I'm saying is I'm pretty sure this is exactly what is happening. I'm not even sure you can rely on the Task.detached here either. When already non-isolated, I don't know what its behavior is other than clearing out TaskLocal values.

What befuddles me is that there's no indication in the code that the closure in question (nor anything it invokes transitively via await) is isolated to any particular context.  It is by design all code that can be called in any context.  None is tied to an actor (global or otherwise).  None uses any thread- or task-local state.
Worse, there doesn't seem to be any syntax the compiler will accept to ensure this - keywords like nonisolated aren't accepted in function parameter signatures, for example.
Separately, I should note that the code as posted is buggy even if the closure parameter is @Sending, because there's a race between signalling the semaphore and the task actually ending; when that race is lost, the closure is still retained and withoutActuallyEscaping crashes. 😔
It seems like there's a missing unsafeWithoutActuallyEscaping, and/or a way to actually signal when the task is fully cleaned up (I tried everything I could think of involving actors, TaskGroup, recursive Task.detached, etc, and nothing works).

Tangentially, I tried using sending throughout and return values (from tasks & closures) to convey the results, rather than capturing local mutable variables - in order to make it moot that the closure parameter has to be @Sendable - but:

I couldn't actually get it to compile.  I'm not saying it's impossible, just that I spent over an hour refactoring what amounts to only a few dozen lines of code, and it just seemed to be an endless sequence of compiler complaints (none of which were indicative of actual flaws in the code, just me trying to convince the compiler - it felt a lot like fighting with the borrow checker in Rust, only without any actual correctness benefits).
It really complicated some of the code (e.g. I can no longer use defer or other simple mechanisms for clean-up, since I have to send the objects in question back & forth and the Swift compiler isn't smart enough to understand what's going on - which is fair, since I can barely wrap my head around the code at that point, it becomes so complicated 😕).

I realise that all this is pretty abstract, and I'm not sure if & where the bug(s) are in the compiler here (beyond the many places in which it is overly conservative about concurrency-safety).  But if nothing else, there is a clear pragmatic gap in the Swift language regarding bridging sync to async code.


How can i set write access password (readonly mode)  for excel file

I am trying to set write password
"use strict";
const XlsxPopulate = require('../../lib/XlsxPopulate');
// Load the input workbook from file with a password.
XlsxPopulate.fromFileAsync("./in.xlsx", { password: "open sesame" })
.then(workbook => {
// Read a value from the workbook.
console.log(workbook.sheet("Sheet1").cell("A1").value());
// Write to file with a new password.
return workbook.toFileAsync("./out.xlsx", { password: "123" });
})
.catch(err => console.error(err));
but the resuft not have read only mode

result is expected

It mean i can readonly when i don't have password
Thank you so much for your support

You did it?

You did it?


fix: Retry on ConnectionAbortedError on Windows

Fixes an error I experienced that appears to be resolved when retrying so I have just made it retry on all errors (except the login errors). Unfortunately this still won't fix #113.

Superseded by #121


Unwrap job_responsibilities items

The placement of each job responsibility string
within a dict is arbitrary, as illustrated by
the current behavior of _process_experience_details,
which makes a comprehension from job_responsibilities by

immediately getting the values of that dict (discarding the one
key in the dict)
ensuring the return of values() is returned as a list
taking the first element of that list
and instantiating a Responsibility with the element
as the value for the description

The first three steps are in service of unwrapping something that
defined by the application's own schema, and as such, the schema
can decide that it doesn't need to be wrapped in the first place.

Should note, I was unable to get pdf_generation.py to either see my virtual environment's installed modules, or the setup.py script did not iinclude certain modules that were needed in order to run the test script. Either way, this change is untested.


AddToHueAndSaturation TypeError: Cannot cast ufunc add output from dtype('float64') to dtype('int32') with casting rule 'same_kind'

Getting the error in the title using AddToHueAndSaturation with statistical distributions for value. Was using iap.Normal which produced same error.
from imgaug import augmenters as iaa
from imgaug import parameters as iap

seq = iaa.Sequential([iaa.AddToHueAndSaturation(iap.Uniform(-30, 30), from_colorspace='BGR', per_channel=0.3)], random_order=False)
images_aug = seq.augment_image(img)

Traceback (most recent call last):
  File "<debug input>", line 1, in <module>
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 257, in augment_image
    return self.augment_images([image], hooks=hooks)[0]
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 1429, in _augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\color.py", line 114, in _augment_images
    hooks=hooks,
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 1429, in _augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 2052, in _augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 1429, in _augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\meta.py", line 365, in augment_images
    hooks=hooks
  File "C:\Python354x64\lib\site-packages\imgaug\augmenters\arithmetic.py", line 140, in _augment_images
    image += sample
TypeError: Cannot cast ufunc add output from dtype('float64') to dtype('int32') with casting rule 'same_kind'

This is now fixed in master. For images it might still be "cleaner" to use DiscreteUniform(a, b) instead of Uniform(a, b) and Discretize(Normal(loc, scale)) for normal distributions, though floats should now work too.


Updated swift version to 4.2

Closes #5

Codecov Report

Merging #6 into master will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff          @@
##           master    #6   +/-   ##
====================================
  Coverage      80%   80%
====================================
  Files           4     4
  Lines         115   115
====================================
  Hits           92    92
  Misses         23    23

Continue to review full report at Codecov.

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

Thanks for your PR @afonsograca, can you update the swift badge on README.md as well?