Pairing and re-pairing issue with Xiaomi devices

zigbee2mqtt add-on version (if edge, please report commit hash):
1.16.0
Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):

Description of problem:
paring 20 devices (xiaomi sensors) I cannot pair additional devices. Even deleting a paired device I cannot pair new devices,. The devices I'm not able to pair are Aquara Water Leak sensors even if I've already paired two devices of the same kind successfully. I've also paired - in the same zigbee network - two Xiaomi devices that has been recognised as "router" ( a plug and  a door-lock  ) but - even if correctly paired and they both work as expected - they are not able to act as router and accept pairing requests from the Aquara Water -Leak sensors. When trying to pair the Aquara Water Leak sensors no messages are shown from the Front-End and on zigbee2mqtt log. Distance of the sensors from the Coordinator (running on a CC2531 USB dongle) and from the two Xiaomi "routers" is about 1 mt, no other coordinators  are active and the sensors battery are brand new. I've also tried to unpair a Xiaomi button switch in order to reduce the number of devices on the network but with no luck, in addition to that the Xiaomi button switch - that was paired before - now is impossible to pair again... In the database.db file there are currently just 18 rows/entities: 1 Coordinator, 2 routers and 15 end-devices.
Your entire configuration from the frontend (with sensitive fields redacted):
`{
    "commit": "1.16.0",
    "config": {
        "advanced": {
            "adapter_concurrent": null,
            "availability_blacklist": [],
            "availability_blocklist": [],
            "availability_passlist": [],
            "availability_timeout": 0,
            "availability_whitelist": [],
            "cache_state": true,
            "cache_state_persistent": true,
            "cache_state_send_on_startup": true,
            "channel": 11,
            "elapsed": false,
            "ext_pan_id": [
                221,
                221,
                221,
                221,
                221,
                221,
                221,
                221
            ],
            "homeassistant_discovery_topic": "homeassistant",
            "homeassistant_legacy_triggers": true,
            "homeassistant_status_topic": "hass/status",
            "last_seen": "disable",
            "legacy_api": true,
            "log_directory": "/share/zigbee2mqtt/log/%TIMESTAMP%",
            "log_file": "log.txt",
            "log_level": "debug",
            "log_output": [
                "console",
                "file"
            ],
            "log_rotation": true,
            "log_syslog": {},
            "pan_id": 6754,
            "report": false,
            "soft_reset_timeout": 0,
            "timestamp_format": "YYYY-MM-DD HH:mm:ss"
        },
        "ban": [],
        "blocklist": [],
        "device_options": {},
        "devices": {
            "0x00158d000130ec12": {
                "friendly_name": "PIR n.1"
            },
            "0x00158d00015b62bd": {
                "friendly_name": "Porta Casa"
            },
            "0x00158d00015c7d98": {
                "friendly_name": "Condizionatore"
            },
            "0x00158d00016d065c": {
                "friendly_name": "Temperatura & Umidità Cameretta"
            },
            "0x00158d00016d0c08": {
                "friendly_name": "Temperatura & Umidità Bagno Principale"
            },
            "0x00158d00016d0c88": {
                "friendly_name": "Temperatura & Umidità Bagno in Camera"
            },
            "0x00158d00016d0d14": {
                "friendly_name": "Temperatura & Umidità Salone"
            },
            "0x00158d0001a2b575": {
                "friendly_name": "Temperatura & Umidità Camera da Letto"
            },
            "0x00158d0001d5944e": {
                "friendly_name": "Allagamento Bagno in Camera"
            },
            "0x00158d0001e73b3d": {
                "friendly_name": "Porta Freezer"
            },
            "0x00158d0001e73b97": {
                "friendly_name": "Porta Frigorifero"
            },
            "0x00158d000200b341": {
                "friendly_name": "Sensore Livello Sump"
            },
            "0x00158d000200b3f4": {
                "friendly_name": "Sensore Vasca di Osmosi"
            },
            "0x00158d000237266c": {
                "friendly_name": "Allagamento Terrazzo"
            },
            "0x00158d00028e2eb2": {
                "friendly_name": "Serratura Porta"
            },
            "0x00158d00057f8078": {
                "friendly_name": "PIR n.3"
            },
            "0x00158d0005818a36": {
                "friendly_name": "PIR n.2"
            }
        },
        "experimental": {
            "new_api": true,
            "output": "json"
        },
        "external_converters": [],
        "frontend": {
            "port": 8099
        },
        "groups": {},
        "homeassistant": true,
        "map_options": {
            "graphviz": {
                "colors": {
                    "fill": {
                        "coordinator": "#e04e5d",
                        "enddevice": "#fff8ce",
                        "router": "#4ea3e0"
                    },
                    "font": {
                        "coordinator": "#ffffff",
                        "enddevice": "#000000",
                        "router": "#ffffff"
                    },
                    "line": {
                        "active": "#009900",
                        "inactive": "#994444"
                    }
                }
            }
        },
        "mqtt": {
            "base_topic": "zigbee2mqtt",
            "include_device_information": false,
            "server": "mqtt://core-mosquitto",
            "user": "**********"
        },
        "passlist": [],
        "permit_join": false,
        "queue": {},
        "serial": {
            "disable_led": false,
            "port": "/dev/ttyACM0"
        },
        "whitelist": []
    },
    "coordinator": {
        "meta": {
            "maintrel": 3,
            "majorrel": 2,
            "minorrel": 6,
            "product": 0,
            "revision": 20190608,
            "transportrev": 2
        },
        "type": "zStack12"
    },
    "log_level": "debug",
    "network": {
        "channel": 11,
        "extended_pan_id": "0xdddddddddddddddd",
        "pan_id": 6754
    },
    "permit_join": true,
    "version": "1.16.0"
}`

Your logs from Home Assistant
No errors in the Homeassistant log when trying to pair the devices.

Try adding a USB extension cord to move the usb stick away from your RPI. Also would be nice to see some information around the adapter if it has the right version.
Typically your issue is more for the zigbee2mqtt repo as the add-on just wraps around that (https://github.com/Koenkk/zigbee2mqtt/issues/new/choose)

Marius thanks for the prompt reply. The USB CC2351 dongle is already connected to the RPi via a USB male-female cable. The firmware running on the adapter is the CC2531_DEFAULT_20190608.zip available on Github (https://github.com/Koenkk/Z-Stack-firmware/tree/master/coordinator/Z-Stack_Home_1.2/bin/default). If this info will not give you any clue in order to solve the issue I'll open an issue on the original project.

@lenny1972 Can you try running the source routing firmware?

I've already the source routing firmware installed on my CC2351 dongle. Anyway I found the reason of sensors unable to pair. Reading this article [()]https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623/55?u=veeceeoh)] I found that my fritzbox router (broadcasting the wifi signal on both 2.4 Ghz and 5 Ghz) probably caused interference to the CC2351 dongle zigbee  network. I simply switch in the zigbee2mqtt configuration the channel from the 11 (the default one) to 25 that is reported to work good with Xiaomi devices/sensors (a lot of interesting info here [()]https://community.hubitat.com/t/xiaomi-aqara-devices-pairing-keeping-them-connected/623 and everything worked like a charm. For people having my same pairing issue should be a solution. IMPORTANT: Take in mind that changing the network channel require to pair all the sensors again..


[Bug] substitute patterns in docker-prepare.sh

Substitute patterns in docker-prepare.sh use backlashes as delimiters, but the default sed on Mac does not allow backslashes to be used as delimiters and emits the following error logs.
$ ~/GitHub/italia/spid-cie-oidc-django$ which sed
/usr/bin/sed
$ ~/GitHub/italia/spid-cie-oidc-django$ bash docker-prepare.sh
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash
sed: 1: "s\http://<IP_ADDRESS>:8000 ...": substitute pattern can not be delimited by newline or backslash

Closed by https://github.com/italia/spid-cie-oidc-django/pull/242
thank you Taka!


Passing arg to bool flag breaks other flags

My urfave/cli version is
v2.27.4
Checklist

[x] Are you running the latest v2 release? The list of releases is here.
[x] Did you check the manual for your release? The v2 manual is here
[x] Did you perform a search about this problem? Here's the GitHub guide about searching.

Dependency Management

My project is using go modules.

Describe the bug
Using a boolean flag with a argument does not terminate the command.
To reproduce
package main

import (
	"fmt"
	"log"
	"os"

	"github.com/urfave/cli/v2"
)

func main() {
	app := &cli.App{
		Flags: []cli.Flag{
			&cli.BoolFlag{
				Name: "bool",
			},
			&cli.StringFlag{
				Name: "text",
			},
		},
		Action: func(ctx *cli.Context) error {
			fmt.Println(ctx.String("bool"))
			fmt.Println(ctx.String("text"))
			return nil
		},
	}

	if err := app.Run(os.Args); err != nil {
		log.Fatal(err)
	}
}

Observed behavior
When a argument is passed to a bool flag then subsequent flags are not read correctly anymore
$ go run . --bool --text str
true
str

$ go run . --bool wrong --text str
true

Expected behavior
If a argument is passed to a bool flag then the command should fail as that is an invalid input
Run go version and paste its output here
go version go1.22.2 darwin/arm64

@svartkanin The whole point of bool flags is to not pass an arg. Why are you passing an arg for the bool flag in the first place ?

@dearchap I'm aware of that, but if someone accidentally uses the flags this way there will be unintentional behaviour because the parsing is all messed up for the flags coming after as it does not terminate.
How would we verify that the flags were used as intended?

It's not easy. What happens if 'wrong' is actually defined as a sub command ? We would then try to process it as such thinking that's what the user intended

If there is no subcommand defined with that name and the Args parameter is set to false for the given command this should result in a failure

Also issue with boolFlag in v3.0.0-alpha9: --flag=false and --flag false is not the same. First parsed to false, but second to true

Its not really an issue. Its the design for command line flags in general. As per this https://pkg.go.dev/flag this is the standard format
-flag x  // non-boolean flags only

without that it becomes ambigious. We cannot intend user's intention here.


HTML in vimhelp file

I was just reading the noice docs, and noticed a section containing HTML tags. Probably an oversight.

I'm using https://github.com/kdheepak/panvimdoc to create vimdocs, and they apparently don't parse html.


Choose executor result topics

Real drones have a lot of topics with many messages. Convenient to have feature to choose topics, which record for result of liability.

I'm agree with you. Also it can be very useful for security reason.


fedimint-cli dev invite-code broken in mprocs

and I don't see how the current impl could ever work since the client is restarted for every command, resetting the internal state that's not persisted to DB. Maybe we should just save the invite code to the DB so this functionality can be implemented properly.

Maybe we should just save the invite code to the DB so this functionality can be implemented properly.

The only problem with this is that at some point we'll properly implement single-use or expiring invite codes, which would break here. But perhaps we could cross that bridge when we come to it.

call: this should be removed and re-added with a non-dev command


error: -no valid 'pas-environment' entitlement string found for application

Hi
I am running the gits but getting below error:
error: -no valid 'pas-environment' entitlement string found for application
trying to get the iPad key so i can send push notification
Thank you

The name should be same that why It was giving this error


chore: reduce size, only dist

Description

Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[] Other

hmm 2kb vs 20kb * 7,500 installs from npm


crash image not showing with "gameover" function

when the smart car crashes with rivals cars, the "BANG" image that should be displayed is not showing up!

Issue resolved!


[Bug] When querying the Hive external table, an Invalid data error occurred.

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
doris-2.0.4-rc02-e529646
What's Wrong?
When querying the hive external table, an "Invalid data" error occurs.
java.sql.SQLException: errCode = 2, detailMessage = (<IP_ADDRESS>)[CANCELLED][INTERNAL_ERROR]Couldn't deserialize thrift msg:
TProtocolException: Invalid data

        0#  doris::Status doris::deserialize_thrift_msg<tparquet::ColumnIndex>(unsigned char const*, unsigned int*, bool, tparquet::ColumnIndex*) at /root/src/doris-2.0/be/src/util/t
hrift_util.h:153
        1#  doris::vectorized::PageIndex::parse_column_index(tparquet::ColumnChunk const&, unsigned char const*, tparquet::ColumnIndex*) at /root/src/doris-2.0/be/src/common/status.h
:443
        2#  doris::vectorized::ParquetReader::_process_page_index(tparquet::RowGroup const&, std::vector<doris::vectorized::RowRange, std::allocator<doris::vectorized::RowRange> >&)
at /root/src/doris-2.0/be/src/common/status.h:443
        3#  doris::vectorized::ParquetReader::_next_row_group_reader() at /root/src/doris-2.0/be/src/common/status.h:443
        4#  doris::vectorized::ParquetReader::get_next_block(doris::vectorized::Block*, unsigned long*, bool*) at /root/src/doris-2.0/be/src/common/status.h:443
        5#  doris::vectorized::VFileScanner::_get_block_impl(doris::RuntimeState*, doris::vectorized::Block*, bool*) at /root/src/doris-2.0/be/src/common/status.h:443
        6#  doris::vectorized::VScanner::get_block(doris::RuntimeState*, doris::vectorized::Block*, bool*) at /root/src/doris-2.0/be/src/vec/exec/scan/vscanner.cpp:0
        7#  doris::vectorized::ScannerScheduler::_scanner_scan(doris::vectorized::ScannerScheduler*, doris::vectorized::ScannerContext*, std::shared_ptr<doris::vectorized::VScanner>)
 at /root/src/doris-2.0/be/src/common/status.h:355
        8#  std::_Function_handler<void (), doris::vectorized::ScannerScheduler::_schedule_scanners(doris::vectorized::ScannerContext*)::$_1::operator()() const::{lambda()#4}>::_M_in
voke(std::_Any_data const&) at /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/shared_ptr_base.h:701
        9#  doris::WorkThreadPool<true>::work_thread(int) at /var/local/ldb-toolchain/bin/../lib/gcc/x86_64-linux-gnu/11/../../../../include/c++/11/bits/atomic_base.h:646
        10# execute_native_thread_routine at /data/gcc-11.1.0/build/x86_64-pc-linux-gnu/libstdc++-v3/include/bits/unique_ptr.h:85
        11# start_thread
        12# clone

        at com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(SQLError.java:130) ~[mysql-connector-j-8.0.33.jar!/:8.0.33]
        at com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(SQLExceptionsMapping.java:122) ~[mysql-connector-j-8.0.33.jar!/:8.0.33]
        at com.mysql.cj.jdbc.StatementImpl.executeQuery(StatementImpl.java:1200) ~[mysql-connector-j-8.0.33.jar!/:8.0.33]

The structure of the SQL is as follows:
select col1,col2
          from tbl1
          where col3='xxx'
          group by col1,col2;

This error seems to only occur on some tables, and running similar SQL on other tables does not result in an error.
What You Expected?
There will be no query errors.
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

After removing the where condition in the SQL, the error changed to
ERROR 1105 (HY000): errCode = 2, detailMessage = (<IP_ADDRESS>)[CANCELLED][INTERNAL_ERROR]Read parquet file hdfs://xxx/.../day=xxx/000001_0 failed, reason = [IO_ERROR]Failed to deserialize parquet page header. offset: 1193158, header size: 1444553, end offset: 2637711, real header size: 1444553

        0#  doris::vectorized::PageReader::next_page_header() at /root/src/doris-2.0/be/src/common/status.h:378
        1#  doris::vectorized::ColumnChunkReader::

is 2.0.3 OK?


[Space Age ; minor issue] wrong technology for unlocking iron stick

Describe the bug
The app thinks that iron stick is unlocked by "Circuit Network" research and not "Electric energy distribution 1"
Screenshots

As you can see, iron stick is missing from it's correct technology unlocks
This is how it looks in game:


Add a Delete button for each files in the preview page

I've added a Delete button to be able to Delete a single file in the preview page.
Some code was present, but the button was missing.

There is already a detele-button for each file, just click on it and you can choose wheter to download or delete the file ;)


Collision when using swifter

collision between:
/nix/store/zn4ksalrynlx3iwd4d0ldq7aiqn84ysv-python3.8-opencensus-context-0.1.2/lib/python3.8/site-packages/opencensus/common/__pycache__/__init__.cpython-38.pyc
and
/nix/store/2cfyjnic605mjr5j7zck88gk7bkqwpim-python3.8-opencensus-0.7.12/lib/python3.8/site-packages/opencensus/common/__pycache__/__init__.cpython-38.pyc
the issue can be tested simply with this command line:
nix shell github:davhau/mach-nix#shellWith.swifter
or with this flake.nix file:
{
  description = "Using mach-nix from a flake";

  inputs = {
    nixpkgs.url = github:NixOS/nixpkgs/nixos-unstable;
    mach-nix.url = github:DavHau/mach-nix/master; # v3.0.0 release tag
  };

  outputs = { self, nixpkgs, mach-nix }: let
    system = "x86_64-linux";
    pkgs = (import nixpkgs { inherit system; }).pkgs;
    mach-nix-utils = import mach-nix {
      inherit pkgs;
      python = "python3";
    };
    requirements = ''
      #matplotlib
      #pandas
      #numpy
      #scikit-learn
      #ipykernel
      #nbconvert
      #notebook
      #seaborn
      #graphviz
      swifter
    '';
  in {
    devShell."${system}" = mach-nix-utils.mkPythonShell {
        inherit requirements;
    };
  };
}

I saw #185 and #201 so I thaught it was a good idea to report this here.
However, do you think it could be an upstream bug?

Hey, thanks for reporting this. This is not a mach-nix bug. opencensus-context and opencensus are two different packages which both provide a file with the exact same import path.
I just added a troubleshooting section to examples.md with some explanation why this happens and how to fix that.
Please have a look at it, and let me know if this helps you.

This here should work:
let
  mach-nix = import (builtins.fetchGit {
    url = "https://github.com/DavHau/mach-nix/";
    ref = "refs/tags/3.2.0";
  }) {};

in
mach-nix.mkPython {
  requirements = ''
    swifter
  '';
  _.opencensus-context.postInstall = ''
    rm $out/lib/python3.8/site-packages/opencensus/common/__pycache__/__init__.cpython-38.pyc
    rm $out/lib/python3.8/site-packages/opencensus/__pycache__/__init__.cpython-38.pyc
  '';
}

Oh! I didn't see your message, sorry for the late reply
I succeeded in installing the pqckage in another way but I'm happy it was a useful feedback


update java version in maven-compiler-plugin

Update Java version from 8 to 11. Closes #71

Codecov Report

Merging #73 (8e4df3e) into master (0476e03) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##             master      #73   +/-   ##
=========================================
  Coverage     88.09%   88.09%
  Complexity        8        8
=========================================
  Files             2        2
  Lines            42       42
  Branches          3        3
=========================================
  Hits             37       37
  Misses            5        5

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

@volodya-lombrozo I updated the java version to 11, but the project stopped being assembled due to the IllegalArgumentException of qulice -- https://github.com/objectionary/speco/actions/runs/4271509780/jobs/7436026079#step:11:4252. I don't really understand what the problem is, maybe you have encountered this error?

@advasileva Looks like it's quite old problem.

@volodya-lombrozo This advice from Mikhail helped hide errors in the ide. Of course, it's better to fix the original problem with qulice


apple tv 4k after change ip can't work

Home Assistant release with the issue:
0.81.6
Last working Home Assistant release (if known):
Never (In my experience)
Operating environment (Hass.io/Docker/Windows/etc.):
Ubuntu 18.04 server
Component/platform:
https://www.home-assistant.io/components/apple_tv/
Description of problem:
at firest,this plug working fine,after apple tv 4k reboot, the ip was change,so i write the right ip to config file and reboot ha service,the apple tv not working,then i try to resert my apple tv,also not working,but the homeassistant can find my tv in apple_tv_scan service
apple tv version: tvos12.0.1
python version:3.6.5
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
apple_tv:
  - host: <IP_ADDRESS>
    login_id: xxxxxx-xxx-xxxx-xxxx-xxxxx
    credentials:xxxxxxxxxxxxx

Traceback (if applicable):
Oct 21 10:55:32 hp-gen8 hass[47431]: 2018-10-21 10:55:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Oct 21 10:55:32 hp-gen8 hass[47431]: Traceback (most recent call last):
Oct 21 10:55:32 hp-gen8 hass[47431]:   File "/srv/homeassistant/homeassistant_venv/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 339, in _async_add_entity
Oct 21 10:55:32 hp-gen8 hass[47431]:     'Invalid entity id: {}'.format(entity.entity_id))
Oct 21 10:55:32 hp-gen8 hass[47431]: homeassistant.exceptions.HomeAssistantError: Invalid entity id: media_player.
Oct 21 10:55:32 hp-gen8 hass[47431]: 2018-10-21 10:55:32 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Oct 21 10:55:32 hp-gen8 hass[47431]: Traceback (most recent call last):
Oct 21 10:55:32 hp-gen8 hass[47431]:   File "/srv/homeassistant/homeassistant_venv/lib/python3.6/site-packages/homeassistant/helpers/entity_platform.py", line 339, in _async_add_entity
Oct 21 10:55:32 hp-gen8 hass[47431]:     'Invalid entity id: {}'.format(entity.entity_id))
Oct 21 10:55:32 hp-gen8 hass[47431]: homeassistant.exceptions.HomeAssistantError: Invalid entity id: remote.

Please fill out the issue template. What does your config for the appletv media_player look like?

Please fill out the issue template. What does your config for the appletv media_player look like?

OK,change the issus


Fix url and path when version regex specified

Making a couple tweaks to finish up the changes to handle special microsoft/git versioning. Specifically, we need to ensure the path version aligns with the manifest version (winget requirement) and pass the fullUrl rather than url for formatting.
This is an example of what our PRs will look like with these changes applied.
Here is the tracking issue for this work (I can't seem to link directly since it's not in this repo).

@ldennington We're assuming here that the first instance of a {{version:R}} regex pattern R in the manifest text template is the one that should be used for the manifest file path?
I think it would be better to have the manifest be generated, and then re-inspect the end result looking for the PackageVersion property and use that value as the version file path.
This would ensure that the manifest is definitely valid in the eyes of the winget-pkgs repo (the PackageVersion and file path version must match).
Left some suggestions/diffs that would do that (generate the manifest and lookup the final PackageVersion value). Let me know what you think!
(Created a branch based off of this one with the suggestion commits below here: https://github.com/mjcheetham/update-winget/tree/path-version)

Mmm I don't think those updates quite worked - when I tested, vfs is still included in all the versions (see https://github.com/ldennington/winget-playground/pull/42/files). I'll try to dig in and fix today.

@ldennington We're assuming here that the first instance of a {{version:R}} regex pattern R in the manifest text template is the one that should be used for the manifest file path?
I think it would be better to have the manifest be generated, and then re-inspect the end result looking for the PackageVersion property and use that value as the version file path.
This would ensure that the manifest is definitely valid in the eyes of the winget-pkgs repo (the PackageVersion and file path version must match).
Left some suggestions/diffs that would do that (generate the manifest and lookup the final PackageVersion value). Let me know what you think!
(Created a branch based off of this one with the suggestion commits below here: https://github.com/mjcheetham/update-winget/tree/path-version)

Mmm I don't think those updates quite worked - when I tested, vfs is still included in all the versions (see https://github.com/ldennington/winget-playground/pull/42/files). I'll try to dig in and fix today.

Never mind. It helps when I use the correct yml for testing. Please ignore the above comment.


Do not tween inherited properties

I'm using TweenJS with Three.js and this is very annoying.
For example, I can't easily operate with THREE.Vector instances because of large amount of their inherited properties. Simple "Tween.get(vector1).to(vector2)"-pattern is inefficient for now.
a._cloneProps = function(a) {
    var b = {};
    for (var c in a) // if (a.hasOwnProperty(c)) would be nice here
        b[c] = a[c];
    return b
}

Interesting. Totally see the use case here of passing a typed DTO. I am a little concerned that in some cases people will want the inherited property to come through, and it will be confusing why it doesn't.
As an aside, the actual implementation would require a check in the for...in loop(s) in _appendProps. It's also complicated by the fact that we now delete properties of the props object if a plugin tells us to ignore it.
I'm going to take a look at this to see if I can identify a good solution. In the interim, you could just run the DTO through a simple clone method to output a generic object with the values you want.

I addressed this issue in 3d23dedaf915964a2dd390fb7b53234fbfa23ab4, feedback welcome.


Visualization requests

Some things to add:

[ ] Pareto distribution of any Section or Subset

Comment anything else (or just watch my notes)

[ ] Distribution of RMs as margin of chosen over rejected


Readme: Chinese Translation

Readme: Chinese Translation

Looks awesome! Thank you so much for your time and effort! : ))


Timer does not sync with webapp until extension is opened

OS version: Catalina 10.15
Browser version: Version 77.0.3865.120 (Official Build) (64-bit)
Extension version: Version 1.42.1

Relevant integration (if any):
N/A
🐛 Describe the bug
Toggl Button doesn’t sync with the webapp timer until you open the extension.
For example, I have had the webapp tracking time all day, but the chrome extension was still grey. I clicked on it, and when it opened the time entry I was currently running showed up.
Expected behaviour
I would expect the extension to immediately pick up the running timer info, regardless of being opened or not.
Steps to reproduce
Steps to reproduce the behaviour:

Go to webapp
Start a timer
Don't open the extension. It will stay grey
Open extension, it will pick the timer up.

Other details or context
More details here.

User Report

User report

User Report

Technical notes:
not 100% sure on any of this yet.
I think background scripts are no kept loaded as much of the time, and we don't have a case to set it to be persistent.
We'll need to poll, inside chrome.runtime.alarm calls, to see if anything is running (and for how long), rather than using websocket for that (which is what I'm currently assuming we do).

Hopefully will be much improved by #1556, currently going through incremental release. Keeping issue open to track things.

This is significantly improved (fixed?) in the latest versions.
I don't think we need to keep this open anymore, so let's close it and make new issues for any specific problems that come up in future 🎉 .


Include opposite task options in documentation

Fixes #24966

@bot-gradle test BD

I've triggered the following builds for you:

BuildDistributions build

@bot-gradle test and merge

I've triggered a build for you.


Add Forth exercise

I'm thinking of walking through some of this solution in my Exercism announcement blog post to highlight some of Roc's nice features like error handling. Curious to hear your feedback on that idea and the solution!

I think it's a great idea to use this example in your blog post! 👍


QC: Step test and internal consistency test

Implement step test and internal consistency test for quality control.

Will be solved in #36


1.1.42 release notes

Description & motivation
To-do before merge
Pre-release docs
Is this change related to an unreleased version of dbt?

[ ] Yes: please

update the base branch to next
add Changelog components: <Changelog>[New/Changed] in v0.x.0</Changelog>
add links to the "New and changed documentation" section of the latest Migration Guide

[x] No: please ensure the base branch is current
[ ] Unsure: we'll let you know!

FYI @schottj @runleonarun

FYI @schottj @runleonarun
I ran into trouble with the original SHA I was using so I had to do the release with a newer SHA and I updated the draft changelog text to reflect that. Wanted to give you a heads up in case you had already started reviewing the text before now.


Proxying video texture for canvas working with demo but canvas tainted with my install

I have a little three js app that uses a remotely-hosted mp4 rendered on a canvas as a texture. When using cors-anywhere.herokuapp.com/* everything works fine but when using my own installation, the canvas is tainted, indicating some misconfiguration on my part but I've got no idea what I'm doing wrong.
Any ideas?

There are not enough details here to tell what's wrong. One thing that could cause the issue that you're describing is when the CORS Anywhere instance and your app are using the same origin. By default, same-origin requests are not proxied.

They are different URLs, linked as follows so I can't add headers unfortunately.
`

`
I forked your repo and launched a Heroku instance with it. Have I forgotten to configure something?

Your code is lacking the crossorigin attribute, see https://developer.mozilla.org/en-US/docs/Web/HTML/Attributes/crossorigin

It's got crossorigin="anonymous". The odd thing is that if I use your demo URL, https://cors-anywhere.herokuapp.com/* everything works perfectly. Are there any other details I could send over to you? I've run out of ideas

You could try to debug yourself, with the browser's built-in developer tools (the network tab of it). For CORS, the request and response headers are especially relevant.
For CORS Anywhere, the response body may also be interesting.

... could you be a bit more specific? Browser versions, what you've done to set up the proxy, etc. So far you're not offering enough details for me to be able to provide meaningful support.

Hey Rob,
Apologies. Set up and problems as follows:
Set up on heroku:

Once more, could you provide ALL relevant details? How am I supposed to help if I don't know how you are sending the request, what the expected behavior, the actual behavior/error messages/responses, etc?

Here are the outputs from first my proxy, then yours:

My proxy:

Yours:

The only difference is changing the URL from https://cors-random.herokuapp.com/* to https://cors-anywhere.herokuapp.com/*

m3u8 requests are blocked in my proxy due to past abuse, where the public demo was used for streaming.
Your issue reports that "it works with the demo but [not] with [your] install", but the screenshots shows the opposite. I'm not even sure if your last comment refers to the same issue as the initial report, but given that the last behavior is expected, and there is not an issue in the CORS Anywhere core, I'm closing this issue.


Can not lunch the example extension "hello world~" , it show some error.

VS Code Version: 1.53.0
OS Version:  macOS Big Sur

Steps to Reproduce:
1.yo and generate the example extension
  yo code
  choose ts extension
  whether bundle or not

Press F5 to debug the example extension "hello world"
The error shows up:

It cannot debug normally as the doc says, please help to see and fix it.
This is my vscode setting.json config about the terminal :
	"terminal.integrated.shell.osx": "/bin/zsh",
    "terminal.integrated.inheritEnv": false

Does this issue occur when all extensions are disabled?: Yes/No

@Aaronphy I cannot reproduce the problem you are seeing.
Does it make a difference if you change the "terminal.integrated.inheritEnv" to true?

Since extension debugging doesn't use the integrated terminal directly and since the error message refers to the "npm run watch" task, I suspect that the "terminal.integrated.inheritEnv": false affects the watch task in a negative way.
@alexr00 does this ring a bell?

Yes, most users need to have  "terminal.integrated.inheritEnv": true to use npm tasks. Otherwise, the location of npm cannot be found. I would close this issue since this is the intended behavior.

@Aaronphy so, "terminal.integrated.inheritEnv": false prevents npm from working (which breaks building typical npm-based extensions).


Synthesis failed for nodejs-firestore-session

Hello! Autosynth couldn't regenerate nodejs-firestore-session. :broken_heart:
Here's the output from running synth.py:
ta', 'synth.py', '--']
2021-01-07 03:09:10,989 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/nodejs-firestore-session/9/sponge_log.log
2021-01-07 03:09:10,990 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata synth.metadata synth.py --
2021-01-07 03:09:11,212 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/nodejs-firestore-session/synth.py.
On branch autosynth-9
nothing to commit, working tree clean
2021-01-07 03:09:11,346 synthtool [DEBUG] > Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
DEBUG:synthtool:Using precloned repo /home/kbuilder/.cache/synthtool/synthtool
.eslintignore
.eslintrc.json
.gitattributes
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
.github/ISSUE_TEMPLATE/support_request.md
.github/PULL_REQUEST_TEMPLATE.md
.github/release-please.yml
.github/workflows/ci.yaml
.kokoro/.gitattributes
.kokoro/common.cfg
.kokoro/continuous/node10/common.cfg
.kokoro/continuous/node10/docs.cfg
.kokoro/continuous/node10/test.cfg
.kokoro/continuous/node12/common.cfg
.kokoro/continuous/node12/lint.cfg
.kokoro/continuous/node12/samples-test.cfg
.kokoro/continuous/node12/system-test.cfg
.kokoro/continuous/node12/test.cfg
.kokoro/docs.sh
.kokoro/lint.sh
.kokoro/populate-secrets.sh
.kokoro/presubmit/node10/common.cfg
.kokoro/presubmit/node12/common.cfg
.kokoro/presubmit/node12/samples-test.cfg
.kokoro/presubmit/node12/system-test.cfg
.kokoro/presubmit/node12/test.cfg
.kokoro/publish.sh
.kokoro/release/docs-devsite.cfg
.kokoro/release/docs-devsite.sh
.kokoro/release/docs.cfg
.kokoro/release/docs.sh
.kokoro/release/publish.cfg
.kokoro/samples-test.sh
.kokoro/system-test.sh
.kokoro/test.bat
.kokoro/test.sh
.kokoro/trampoline.sh
.kokoro/trampoline_v2.sh
.mocharc.js
.nycrc
.prettierignore
.prettierrc.js
.trampolinerc
CODE_OF_CONDUCT.md
CONTRIBUTING.md
LICENSE
README.md
api-extractor.json
renovate.json
samples/README.md
2021-01-07 03:09:11,485 synthtool [DEBUG] > Installing dependencies...
DEBUG:synthtool:Installing dependencies...
npm WARN deprecated<EMAIL_ADDRESS>NOTICE: ts-simple-ast has been renamed to ts-morph and version reset to 1.0.0. Switch at your leisure...
npm WARN deprecated<EMAIL_ADDRESS>Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated<EMAIL_ADDRESS>Use cheerio-select instead
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>The package has been renamed to `open`
npm WARN deprecated<EMAIL_ADDRESS>"Please update to latest v2.3 or v2.2"
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated

><EMAIL_ADDRESS>postinstall /home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"

><EMAIL_ADDRESS>postinstall /home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/protobufjs
> node scripts/postinstall

><EMAIL_ADDRESS>postinstall /home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/@compodoc/compodoc
> opencollective-postinstall || exit 0

Thank you for using @compodoc/compodoc!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/compodoc/donate

><EMAIL_ADDRESS>prepare /home/kbuilder/.cache/synthtool/nodejs-firestore-session
> npm run compile

><EMAIL_ADDRESS>precompile /home/kbuilder/.cache/synthtool/nodejs-firestore-session
> gts clean

/home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/meow/index.js:61
		throw new Error(`Flag keys may not contain '-': ${invalidFlags.join(', ')}`);
		^

Error: Flag keys may not contain '-': dry-run
    at validateOptions (/home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/meow/index.js:61:9)
    at meow (/home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/meow/index.js:136:2)
    at Object.<anonymous> (/home/kbuilder/.cache/synthtool/nodejs-firestore-session/node_modules/gts/build/src/cli.js:30:13)
    at Module._compile (internal/modules/cjs/loader.js:1063:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
    at Module.load (internal/modules/cjs/loader.js:928:32)
    at Function.Module._load (internal/modules/cjs/loader.js:769:14)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>precompile: `gts clean`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>precompile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/kbuilder/.npm/_logs/2021-01-07T11_09_32_410Z-debug.log
2021-01-07 03:09:32,450 synthtool [ERROR] > Failed executing npm install:

None
ERROR:synthtool:Failed executing npm install:

None
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/home/kbuilder/.cache/synthtool/nodejs-firestore-session/synth.py", line 15, in <module>
    node.install()
  File "/tmpfs/src/github/synthtool/synthtool/languages/node.py", line 167, in install
    shell.run(["npm", "install"], hide_output=hide_output)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['npm', 'install']' returned non-zero exit status 1.
2021-01-07 03:09:32,494 autosynth [ERROR] > Synthesis failed
2021-01-07 03:09:32,495 autosynth [DEBUG] > Running: git reset --hard HEAD
HEAD is now at ac0330c chore(deps): update dependency gts to v3 (#154)
2021-01-07 03:09:32,502 autosynth [DEBUG] > Running: git checkout autosynth
Switched to branch 'autosynth'
2021-01-07 03:09:32,507 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Removing node_modules/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 334, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 65, in synthesize_loop
    has_changes = toolbox.synthesize_version_in_new_branch(synthesizer, youngest)
  File "/tmpfs/src/github/synthtool/autosynth/synth_toolbox.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(synth_log_path, self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:

Autosynth passed, closing! :green_heart:


[New Feature] .test(), .match() filters

Hi,
I was thinking of adding passwordFmt which checks whether a string contains 8+ characters, at least one uppercase, lowercase, and a number. There may be a 'strict' option where it also checks for at least one special character.
Let me know what you guys think of this.
Taku

Not sure it can be qualified as a common case. Password specifications vary from service to service, some being laxer than others (I personally find it bullshit, better passwords are longer passwords, even if it contains only letters, period). What could be useful however, is a pattern matching filter. Something like

...

But even that is not so common.

I Agree with @mallowigi,
pattern matching/testing could be useful, what you do with it, it's your choice.
{{ 'foobarbaz' | test: '/^[a-zA-Z]{3,}$/' }}  // → true
{{ 'foobarbaz' | match: '/[a-zA-Z]{3,}/g' }}  // → ['foo', 'bar', 'baz']

based on your example @tak215 , I generally use ng-pattern to deal with input validation, e.g:
<input ... ng-pattern="ps-regex" />


[NFC] Remove LinalgTransformationFilter from dispatch region formation

This change is NFC and simplifies the code base. LinalgTransformationFilter was previously used to ensure that the pattern that creates dispatch regions is not applied in certain places. This change replaces the pattern with a simpler walk over the IR. (The greedy pattern rewriter is no longer used for this purpose.)

@matthias-springer looks like the CI failures are real....

These are some developer notes (https://github.com/iree-org/iree/tree/main/benchmarks#repro-of-tflite-model-errors) that I had to help repro these. Dont know if these are still valid. You can reach out @pzread if you need some help repro-ing this locally.

Depends on #9914 to fix the TFLite failure.

Also depends on #9915.

How can I trigger another benchmark run?

I thought it used to do it automatically - maybe that broke? I'd try removing the label and adding it again - or see if @pzread knows the new magic :)


Is there a way to remove time from the data point?

I am consuming the data from the influxDB and writing it back to influxDB if some condition meets, but most of the data points have same time and they end up getting overwritten on the InfluxDB side, I tried deleting the field:time, but it does not seem to work, is there a way to get around this ?

Found a work around, basically we can tag all the fields which uniquely identifies each data point.


TypeError: Cannot read property 'bubblingEventTypes' of null in SRSRadialGradient

react-native-radial-gradient: "^1.1.5"
react-native: "^0.75.2",
xCode: 15.4
The project is building ok, but the app brokes when tries to render the component.
TypeError: Cannot read property 'bubblingEventTypes' of null
This error is located at:
in SRSRadialGradient
in RCTView
in Unknown
in RadialGradient
in RCTView
in Unknown
in InfoCard
in RCTView
in Unknown
in VirtualizedListCellContextProvider
in CellRenderer
in RCTScrollContentView
in RCTScrollView
in ScrollView
in ScrollView
in VirtualizedListContextProvider
in VirtualizedList
in FlatList
in CardInfoList
in RCTView
in Unknown
in RCTScrollContentView
in RCTScrollView
in ScrollView
in ScrollView
in ErrorBoundary
in ErrorHandler
in RCTView
in Unknown
in ScreenWrapper
in ProfileScreen
in StaticContainer
in EnsureSingleNavigator
in SceneView
in RCTView
in Unknown
in DebugContainer
in MaybeNestedStack
in RCTView
in Unknown
in RNSScreen
in Unknown
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in InnerScreen
in Screen
in SceneView
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in RNSScreenStack
in ScreenStack
in NativeStackViewInner
in RCTView
in Unknown
in SafeAreaProviderCompat
in NativeStackView
in PreventRemoveProvider
in NavigationContent
in Unknown
in NativeStackNavigator
in ProfileStack
in StaticContainer
in EnsureSingleNavigator
in SceneView
in RCTView
in Unknown
in DebugContainer
in MaybeNestedStack
in RCTView
in Unknown
in RNSScreen
in Unknown
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in InnerScreen
in Screen
in SceneView
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in RNSScreenStack
in ScreenStack
in NativeStackViewInner
in RCTView
in Unknown
in SafeAreaProviderCompat
in NativeStackView
in PreventRemoveProvider
in NavigationContent
in Unknown
in NativeStackNavigator
in HomeStack
in StaticContainer
in EnsureSingleNavigator
in SceneView
in RCTView
in Unknown
in RCTView
in Unknown
in Background
in Screen
in RNSScreen
in Unknown
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in InnerScreen
in Screen
in MaybeScreen
in RNSScreenNavigationContainer
in ScreenContainer
in MaybeScreenContainer
in RCTView
in Unknown
in SafeAreaProviderCompat
in BottomTabView
in PreventRemoveProvider
in NavigationContent
in Unknown
in BottomTabNavigator
in TabsStack
in StaticContainer
in EnsureSingleNavigator
in SceneView
in RCTView
in Unknown
in DebugContainer
in MaybeNestedStack
in RCTView
in Unknown
in RNSScreen
in Unknown
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in InnerScreen
in Screen
in SceneView
in Suspender
in Suspense
in Freeze
in DelayedFreeze
in RNSScreenStack
in ScreenStack
in NativeStackViewInner
in RCTView
in Unknown
in SafeAreaProviderCompat
in NativeStackView
in PreventRemoveProvider
in NavigationContent
in Unknown
in NativeStackNavigator
in RootStack
in EnsureSingleNavigator
in BaseNavigationContainer
in ThemeProvider
in NavigationContainerInner
in I18nextProvider
in Suspense
in ThemeProvider
in RCTView
in Unknown
in Portal.Host
in RNCSafeAreaProvider
in SafeAreaProvider
in SafeAreaProviderCompat
in PaperProvider
in Provider
in App
in RCTView
in Unknown
in AppContainer, js engine: hermes

Same

This issue persist even when newArchitecture is disabled. This solution may work for you:

npm i react-native-reanimated react-native-screens react-native-safe-area-context
npx pod-install (or cd ios && pod install)
npm run ios

There is most likely a version mismatch somewhere within the dependencies. Here are my versions:
    "react-native-reanimated": "^3.15.3",
    "react-native-safe-area-context": "^4.11.0",
    "react-native-screens": "^3.34.0",

If the above does not work for you, try installing react-native-gesture-handler then repeat steps 2 and 3.

This issue persist even when newArchitecture is disabled. This solution may work for you:

npm i react-native-reanimated react-native-screens react-native-safe-area-context
Add {..., plugins: ['react-native-reanimated/plugin']} to the babel.config.js file
npx pod-install (or cd ios && pod install)
npm run ios

There is most likely a version mismatch somewhere within the dependencies. Here are my versions:
    "react-native-reanimated": "^3.15.3",
    "react-native-safe-area-context": "^4.11.0",
    "react-native-screens": "^3.34.0",

If the above does not work for you, try installing react-native-gesture-handler then repeat steps 3 and 4.

Thanks.. It works with this.


[Bug]: Sunday and homebridge stops working due to Eufy plugin

What happened?
Haven't worked on Homebridge for a while so was confused why Eufy wired doorbell was the culprit.
looked at logs and "using admin account not recommended" so i edited the plugin with my Wife's eufy account, updated node and all plugins but now i just get the attached error.

i am about to wipe my homebridge and start afresh [i'm running oznu/homebridge:2022-11-14 as current release does not support restore from backup].
Also, i cannot add it to home even though the log is telling me to do so.
Device Type
Doorbell (Supported)
Plugin Version
v2.0.x (Supported)
HomeBridge Version
v1.6.x (Supported)
NodeJS Version
v18 (Supported)
Operating System
Docker (UnSupported)
Relevant log output
[8/30/2023, 8:17:25 AM] Homebridge v1.6.1 (HAP v0.11.1) (Homebridge) is running on port 51190.
[08/30/2023 07:17:25]   [EufySecurity-2.2.5]    INFO    [SnapshotManager.ts:118]        Ding Dong is set to handle snapshots with cloud images. Snapshots might be older than they appear.
[08/30/2023 07:17:25]   [EufySecurity-2.2.5]    INFO    [SnapshotManager.ts:126]        Ding Dong Empty snapshot will be sent on ring events immediately to speed up homekit notifications.
[08/30/2023 07:17:25]   [EufySecurity-2.2.5]    INFO    [platform.ts:518]       Adding new unbridged accessory: Ding Dong
[8/30/2023, 8:17:25 AM] Ding Dong DDD7 is running on port 51101.
[8/30/2023, 8:17:25 AM] Please add [Ding Dong DDD7] manually in Home app. Setup Code: 298-21-337
[08/30/2023 07:17:25]   [EufySecurity-2.2.5]    WARN    [SnapshotManager.ts:326]        Ding Dong Couldt not get cloud snapshot: Error: connect ECONNREFUSED <IP_ADDRESS>:443
[08/30/2023 07:17:25]   [EufySecurity-2.2.5]    WARN    [SnapshotManager.ts:133]        Ding Dong snapshot handler is initialized without cloud snapshot. Maybe no snapshot will displayed the first times.

config
{
            "username"<EMAIL_ADDRESS>            "password": "#####",
            "country": "GB",
            "deviceName": "Ding Dong",
            "platform": "EufySecurity",
            "ignoreStations": [
                "T8200N002#####1C"
            ],
            "ignoreDevices": [],
            "cleanCache": true,
            "cameras": [
                {
                    "serialNumber": "T8200N002#####1C",
                    "rtsp": false,
                    "enableCamera": true,
                    "enableButton": false,
                    "motionButton": false,
                    "unbridge": true,
                    "immediateRingNotificationWithoutSnapshot": true,
                    "delayCameraSnapshot": false,
                    "snapshotHandlingMethod": 1,
                    "refreshSnapshotIntervalMinutes": 10
                }
            ],
            "preferLocalConnection": true
        },

got it re-added after being unbridged.
would the culprit be = [08/30/2023 08:18:23]   [EufySecurity-2.2.5]    WARN    [SnapshotManager.ts:326]        Ding Dong Couldt not get cloud snapshot: Error: connect ECONNREFUSED <IP_ADDRESS>:443

try 2.2.6 ?

try 2.2.6 ?

That’s got me something. Nice work.
Very slow but I’ll get into homebridge and check some settings.
Thank you.

thanks for your feedback


support "comma first" option as provided by js beautifier

As the title says...the option is supported by jsbeautifier

-C, --comma-first                 Put commas at the beginning of new line instead of end

I'd be glad to take any workaround to supply opts to js beautifier in addition to those exposed on the atom ui, too. Thanks.

@jiangyang the config needs to modified to support this https://github.com/jdc0589/jsformat-atom/blob/master/lib/config.coffee. Can you put together a PR?


Unable to run tests (Windows)

I'm trying to write a failing test for https://github.com/twolfson/gulp.spritesmith/issues/55, but I'm running into issues running the tests.
First, I had to npm install -g phantomjs just to be able to npm install this project. Once that was done, I ran npm test in both Bash and an administrative command prompt in Windows 8.1. I got the exact same error in both shells:
/.../GitHub/gulp.spritesmith (break-merge *)
16:49 $npm test

><EMAIL_ADDRESS>pretest z:\Documents\GitHub\gulp.spritesmith
> twolfson-style install

><EMAIL_ADDRESS>test z:\Documents\GitHub\gulp.spritesmith
> npm run precheck && cd test && mocha . --timeout 60000 && cd .. && npm run lin
t

><EMAIL_ADDRESS>precheck z:\Documents\GitHub\gulp.spritesmith
> twolfson-style precheck docs/ lib/ test/

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn jshint ENOENT
    at exports._errnoException (util.js:746:11)
    at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
    at child_process.js:1144:20
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
    at startup (node.js:129:16)
    at node.js:814:3

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "c:\\Program Files\\nodejs\\\\node.exe" "c:\\Program Files\\nodejs
\\node_modules\\npm\\bin\\npm-cli.js" "run" "precheck"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>precheck: `twolfson-style precheck docs/ lib/ te
st/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>precheck script 'twolfson-style pr
echeck docs/ lib/ test/'.
npm ERR! This is most likely a problem with the gulp.spritesmith package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     twolfson-style precheck docs/ lib/ test/
npm ERR! You can get their info via:
npm ERR!     npm owner ls gulp.spritesmith
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     z:\Documents\GitHub\gulp.spritesmith\npm-debug.log
npm ERR! Test failed.  See above for more details.

ENOENT means "Error no entity found". This means that jshint cannot be found on your PATH. I am sure you did this but can you verify you ran npm install and that node_modules/.bin/jshint exists?

Yep, it does:
/.../GitHub/gulp.spritesmith (break-merge *)
18:10 $ls node_modules/.bin
_mocha*     js-yaml*     jshint*     rimraf*
_mocha.cmd  js-yaml.cmd  jshint.cmd  rimraf.cmd
gulp*       jscs*        mocha*      twolfson-style*
gulp.cmd    jscs.cmd     mocha.cmd   twolfson-style.cmd

Weird, maybe there's a bug in twolfson-style with respect to Windows. Can you try removing the npm run precheck and seeing if tests pass?

Nope. precheck is throwing the error.

Right, I meant adjust the package.json so you can run the tests exclusively. This is to see if there are any other errors in the test suite outside of precheck.
// Inside package.json
"test": "cd test && mocha . --timeout 60000 && cd .. && npm run lint"

Oh! I read it too fast! Sure, the tests pass, but it fails on lint:
/.../GitHub/gulp.spritesmith (break-merge)
21:23 $npm test

><EMAIL_ADDRESS>pretest Z:\Documents\GitHub\gulp.spritesmith
> twolfson-style install

><EMAIL_ADDRESS>test Z:\Documents\GitHub\gulp.spritesmith
> cd test && mocha . --timeout 60000 && cd .. && npm run lint

child_process: customFds option is deprecated, use stdio instead.

  ...................

  19 passing (10 seconds)

><EMAIL_ADDRESS>lint Z:\Documents\GitHub\gulp.spritesmith
> twolfson-style lint docs/ lib/ test/

events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: spawn jshint ENOENT
    at exports._errnoException (util.js:746:11)
    at Process.ChildProcess._handle.onexit (child_process.js:1053:32)
    at child_process.js:1144:20
    at process._tickCallback (node.js:355:11)
    at Function.Module.runMain (module.js:503:11)
    at startup (node.js:129:16)
    at node.js:814:3

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "c:\\Program Files\\nodejs\\\\node.exe" "c:\\Program Files\\nodejs
\\node_modules\\npm\\bin\\npm-cli.js" "run" "lint"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>lint: `twolfson-style lint docs/ lib/ test/`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>lint script 'twolfson-style lint d
ocs/ lib/ test/'.
npm ERR! This is most likely a problem with the gulp.spritesmith package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     twolfson-style lint docs/ lib/ test/
npm ERR! You can get their info via:
npm ERR!     npm owner ls gulp.spritesmith
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     Z:\Documents\GitHub\gulp.spritesmith\npm-debug.log
npm ERR! Test failed.  See above for more details.

BTW, I had some CRLFs everywhere, so I had to:
git config core.autocrlf false
git rm --cached -r .
git reset --hard

Strange. I don't normally have to do that with projects and I don't see a .gitattributes file on this project.

I have successfully reproduced the jshint error on an ievm. I will patch it by the end of next weekend.
With respect to CRLFs, I don't see any carriage returns in the repo (git grep $'\r). Where are you seeing them? Are you sure your global git config is configured to respect the original repo's contents?

Stupid GitHub for Windows always sets the system-wide autocrlf to true. Yeah. I fixed my global setting to override it.

We have added support for Windows in<EMAIL_ADDRESS>Since it was a patch release, the changes should automatically be picked up. I have verified that tests are back to passing in Windows :tada:
Thanks for the bug report =)


Remove second de novo

Fixes

Closes #90

Proposed Changes

No longer calls the naive de novo logic when generating Category4 - this means there's no need for 4 and 4b
Investigation to follow on whether the need for this sub-category in the first place was the result of a fixable bug in Hail's implementation

Checklist

[x] Related Issue created
[x] Tests covering new change
[x] Linting checks pass

the logic for the naive method is retained but not implemented, as a syntax reference for future methods


Group Voice Call

Hello,
Thank you for this great package,
Please, how could I use it to make a group voice call (same as twitter space) using a janus server ?
Thanks

Well my janus-client package only has the video room plugin implemented, though you can use the core Janus facade to use the underlying communications methods. You could also make your own plugin for their audio bridge plugin by extending my BasePlugin as I do not plan to implement that myself right now.
It is possible to start a video room but configure it with audio only, so no one would be publishing their video source. I suggest reading through their documentation for the audio bridge and the video room plugins:

https://janus.conf.meetecho.com/docs/audiobridge.html
https://janus.conf.meetecho.com/docs/videoroom.html

As for my messenger and UI packages, I have no plan to change any functionality that currently exists, though you can change to your own custom VideoDriver so when a call is created, perhaps you change the parameters sent to janus.

Thank you so much @RTippin


Revert "add make install, fix #202"

This reverts commit 77a16d311603533201cc5b147cadbc034abef793.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "fix_makefile" git@github.com:vikstrous/notary.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.


Rename notebooks folder to templates

What is the purpose of this PR?
Closes #725. It's no longer necessary to suffix the templates folder with _ark; this is a remnant of when the toffy pipeline was here.
How did you implement your changes
Change any reference to templates_ark to templates.

@ngreenwald good catch, looks like Github search isn't reliable for Jupyter notebooks. Just one minor reference fix.
start_docker.sh works as expected.

Sounds good. Going to wait to merge this in until we're ready for a new release to make sure people aren't stuck with an intermediate version


Sentry Relay: Error messages in logs

When checking the Docker logs of the (production) Sentry relay for #387, I noticed that we have many errors logged. They all read:
2023-06-02T19:17:03.611565Z ERROR relay_server::utils::statsd: Transaction marked as URL tags.project_id=0 event_id="c6dc510e-ca62-40bc-93ab-e9c5ce697c0c"

We should investigate what this error means and how to prevent it.

While investigating the HTTP/3 behavior on staging, I also noticed that our production instance was still sending events to the staging relay (which were probably rejected). I fixed this by applying the correct routing policy on the production CodeOcean host, which is not yet managed by Ansible. The other way around should not occur, since the staging environment does not have the public IP interface attached directly.
That having said, I have the feeling that we might need to tune the Sentry Relay setup a bit. Increasing the event_buffer_size sounds like a good start.
Other than that, I am wondering that we are not seeing any issues in the Relay Docker logs since July 10th. Did we resolve any of these?

Increasing the event_buffer_size sounds like a good start

See codeocean-terraform!131

Other than that, I am wondering that we are not seeing any issues in the Relay Docker logs since July 10th. Did we resolve any of these?

I'm wondering too. The only Sentry Relay issue we have resolved lately is #387, but I doubt that it is related to the Relay issues here. Maybe the issues here are all somehow caused by the network issues of our cluster and now the cluster is stable :shrug: Anyway, with SENTRY-RELAY-6 I have triggered an error that appeared both in the Docker logs and also in the Sentry project as issue. Therefore, I would assume that we are not missing errors..

Alrigh, thanks. Having no issues is also fine with me, so I would agree and close this issue once we merged and deployed the changed configuration. 👍

We deployed the updated config and did not notice any (new) errors in the Docker logs nor the Sentry project. Therefore, we consider this issue to be resolved.


Fields named "null" are incorrectly parsed as invalid

Version and Environment Details
Operation system:
Ubuntu 18.04.2 LTS
IDE name and version:
PhpStorm 2019.1
Build #PS-191.6183.95, built on March 28, 2019
Plugin version:
JS GraphQL (2.0.0)
Expected Behaviour
The following schema should be parsed without error:
input Foo {
  null: String
}

As per spec the only restriction on field names is the regexp /[_A-Za-z][_0-9A-Za-z]*/ and thus "null", while probably not very common, is a valid field name.
Actual Behaviour
The following error is shown and it will break (in a non-obvious way) all other types depending on this one:
Invalid Syntax : Unexpected token: "null"

Steps to Reproduce / Link to Repo with Reproduction and Instructions
Copy/paste the schema above in probably any .graphql file.
I suspect the root of this issue actually is in another project. If you can confirm this, I'll gladly open a new issue where it would be the most appropriate.

Fields named "on" show the same behavior. Using version 2.1.0

This is causing a big issue for the Magento community since it has a field called 'null' on an input

Fixed in the upcoming 2.4.0.


Error related to sqlalchemy in middle of BEL processing

Hi there, thanks for the help previously. Unfortunately I made slight progress and found new errors.  I noticed in your config that sqlalchemy is supposed to install the newest version, and that may be the source of the problem. Hopefully it's just another version thing. You mentioned previously that you're working on many large changes that will be released soon, if that's true, I'm willing to wait for that and don't worry about addressing these issues in specific here!
Anyway, here's what I'm facing:
After downloading wikipathways, running python3 -m pathme wikipathways bel
I get partway through and then:
Exporting WikiPathways to BEL in /wynton/home/ye/mschmitz1/.pathme/wikipathways/bel:  48%|████▊     | 242/509 [09:45<25:28,  5.72s/it]Traceback (most recent call last):
File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1247, in _execute_context
self.dialect.do_execute(
File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 588, in do_execute
cursor.execute(statement, parameters)
sqlite3.InterfaceError: Error binding parameter 0 - probably unsupported type.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/runpy.py", line 193, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/__main__.py", line 8, in <module>
    main()
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 764, in __call__
    return self.main(*args, **kwargs)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 717, in main
    rv = self.invoke(ctx)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 1137, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 956, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/click/core.py", line 555, in invoke
    return callback(*args, **kwargs)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/cli.py", line 75, in bel
    wikipathways_to_pickles(resource_files, resource_folder, hgnc_manager, export_folder)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/rdf_sparql.py", line 301, in wikipathways_to_pickles
    bel_graph = wikipathways_to_bel(pathway_path, hgnc_manager)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/rdf_sparql.py", line 275, in wikipathways_to_bel
    return rdf_wikipathways_to_bel(rdf_graph, hgnc_manager)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/rdf_sparql.py", line 264, in rdf_wikipathways_to_bel
    return convert_to_bel(nodes, complexes, interactions, metadata, hgnc_manager)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/convert_to_bel.py", line 55, in convert_to_bel
    nodes = {
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/convert_to_bel.py", line 56, in <dictcomp>
    node_id: node_to_bel(node, hgnc_manager, pathway_id)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/convert_to_bel.py", line 93, in node_to_bel
    namespace, name, identifier = get_valid_gene_identifier(node_ids_dict, hgnc_manager, pathway_id)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/utils.py", line 120, in get_valid_gene_identifier
    return _validate_query(hgnc_manager, hgnc_entry, hgnc_symbol, HGNC)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/utils.py", line 83, in _validate_query
    return _get_update_alias_symbol(hgnc_manager, original_identifier, HGNC)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/pathme/wikipathways/utils.py", line 59, in _get_update_alias_symbol
    query_result = hgnc_manager.get_hgnc_from_alias_symbol(original_identifier)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/bio2bel_hgnc/manager.py", line 232, in get_hgnc_from_alias_symbol
    query_result = self.session.query(AliasSymbol).filter(AliasSymbol.alias_symbol == alias_symbol).all()
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3244, in all
    return list(self)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3403, in __iter__
    return self._execute_and_instances(context)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/orm/query.py", line 3428, in _execute_and_instances
    result = conn.execute(querycontext.statement, self._params)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 984, in execute
    return meth(self, multiparams, params)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/sql/elements.py", line 293, in _execute_on_connection
    return connection._execute_clauseelement(self, multiparams, params)
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1097, in _execute_clauseelement
    ret = self._execute_context(
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1287, in _execute_context
    self._handle_dbapi_exception(
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1481, in _handle_dbapi_exception
    util.raise_(
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 178, in raise_
    raise exception
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1247, in _execute_context
    self.dialect.do_execute(
  File "/wynton/home/ye/mschmitz1/utils/miniconda3/envs/pathways2/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 588, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.InterfaceError: (sqlite3.InterfaceError) Error binding parameter 0 - probably unsupported type.
[SQL: SELECT pyhgnc_aliassymbol.id AS pyhgnc_aliassymbol_id, pyhgnc_aliassymbol.alias_symbol AS pyhgnc_aliassymbol_alias_symbol, pyhgnc_aliassymbol.is_previous_symbol AS pyhgnc_aliassymbol_is_previous_symbol, pyhgnc_aliassymbol.hgnc_id AS pyhgnc_aliassymbol_hgnc_id
FROM pyhgnc_aliassymbol
WHERE pyhgnc_aliassymbol.alias_symbol = ?]
[parameters: ({'Survivin', 'survivin'},)]
(Background on this error at: http://sqlalche.me/e/rvf5)

And it runs into this error at the same spot every time...
Here are the packages that are installed
attrs                19.3.0
bel-repository       0.1.0
bel-resources        0.0.3
bio2bel              0.2.1
bio2bel-chebi        0.2.1
bio2bel-hgnc         0.2.2
bio2bel-kegg         0.2.5
bio2bel-reactome     0.2.3
bio2bel-wikipathways 0.2.3
certifi              2019.11.28
chardet              3.0.4
Click                7.0
click-plugins        1.1.1
compath-utils        0.2.1
configparser         4.0.2
dataclasses-json     0.4.2
decorator            4.4.2
easy-config          0.2.0
enum34               1.1.10
flasgger             0.9.4
Flask                1.1.1
Flask-Admin          1.5.5
Flask-Cors           3.0.8
idna                 2.9
ijson                2.6.1
isodate              0.6.0
itsdangerous         1.1.0
Jinja2               2.11.1
jsonschema           3.2.0
MarkupSafe           1.1.1
marshmallow          3.5.1
marshmallow-enum     1.5.1
mistune              0.8.4
multisplitby         0.0.1
mypy-extensions      0.4.3
ndex2                3.3.1
networkx             2.4
numpy                1.16.3
pandas               0.24.2
passlib              1.7.2
pathme               0.1.12
pip                  20.0.2
pybel                0.13.2
pybel-cx             0.1.3
pybel-tools          0.7.5
PyHGNC               0.2.4
PyMySQL              0.9.3
pyparsing            2.4.6
pyrsistent           0.16.0
pysolr               3.8.1
python-dateutil      2.8.1
pytz                 2019.3
PyYAML               5.3.1
rdflib               4.2.2
requests             2.23.0
requests-file        1.4.3
requests-toolbelt    0.9.1
scipy                1.4.1
setuptools           46.1.1.post20200323
six                  1.14.0
SQLAlchemy           1.3.15
stringcase           1.2.0
tqdm                 4.31.1
typing-extensions    <IP_ADDRESS>
typing-inspect       0.5.0
urllib3              1.25.8
Werkzeug             1.0.0
wheel                0.34.2
WTForms              2.2.1

Ok this is a problem on our side with the new dump of wikipathways I updated. Apparently one of the nodes from WikiPathways has 2 names and we pass a set instead of a string to the query

While I fix the problem you can download the WikiPathways files here directly:
https://drive.google.com/uc?authuser=0&id=1adwTE9cUpMb0lFiN0gbrGLaWfExtFdux&export=download
Move them under ~/.pathme/wikipathways/bel if you want to use them with PathMe directly since it expects them to be there

The other dumps for KEGG and Reactome are  here:
Download KEGG pickles (Update link if the file is replaced)
https://drive.google.com/uc?authuser=0&id=1a_6lck28Df9v2E-Dt45-ZARsdGVs-V9s&export=download
https://owncloud.scai.fraunhofer.de/index.php/s/EKkJmrXnGr2rwd6/download

Sweet, thank you! I'll give these a shot.

I have pinned the version of compath_utils now so the previous problem should be solved (it wasnt pinned and we updated the package in last weeks). I identified this problem now. Gonna fix it

This pathway (https://www.wikipathways.org/index.php/Pathway:WP1772) had some issues regarding the identifiers (they were hgnc symbols instead of the expected hgnc id) so it was crashing. I dont want to hack it since this is a problem of the resource. I will do a new release fixing the dependency problem and where this pathway wont be exported. Will try to see whether it is fixed in new newest version from this month of WP, if not then I will curate it myself there but it wont be fixed until the next release.

Good to know! The zips you linked to work, I can load them! Now I need to figure out how to wrangle the BELgraphs... Thanks for your help!

Thank to you for your patience and using PathMe. I make now the new release and close the issue.

Fixed with 8e1482ea577593f9c85f1085cbd3b9f72ef86e03


behaviour of tf.GPUOptions(allow_growth=False) seems different

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04.5 LTS
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): v1.12.0-0-ga6d8ffae09 1.12.0
Python version: 3.5.2:
CUDA/cuDNN version: cuda-9.0, cudnn-7.3.1
GPU model and memory: Titan Xp, Titan V

Describe the current behavior
In previous version, 1.10.0 wich I used, per_process_gpu_memory_fraction is occupied as soon as session is created.
However with this version (1.12.0), GPU memory occupied after a single sess.run().
config = tf.ConfigProto(
        allow_soft_placement=True,
        log_device_placement=False,
        gpu_options=tf.GPUOptions(force_gpu_compatible=True,
                                  per_process_gpu_memory_fraction=0.5,
                                  allow_growth=False))

a = tf.constant(1)
sess = tf.Session(config=config)
# <- GPU memory is not fully occupied (v.1.12.0)
#       but it was occupied right after in previous version (v.1.10.0)
sess.run(a)
# <- GPU memory is now fully occupied (v.1.12.0)

Describe the expected behavior
After session is created gpu memory should be fully occupied as specified in a variable per_process_gpu_memory_fraction
Code to reproduce the issue
shown above

Thanks for filing this issue. Could you also explain your preference for the old behavior?
I haven't tried to reproduce this yet but adding some devs who may know if there was any change in the memory allocator implementation that may have caused this.
@aaroey @poxvoculi

Exactly what do you mean by GPU memory being fully occupied?  How are you testing that?  And, most importantly, why would the old behavior be preferable?

What I mean by that if I set per_process_gpu_memory_fraction to 0.5, 50% of GPU memory is occupied as soon as session is created in v1.10.0 but in v1.12.0 only small fraction of GPU memory is occupied right after session is created.
This new behaviour is easily addressed by executing arbitrary ops or variables in session right after it is created. That is if I run any ops or variables, 50% of GPU memory is successfully occupied right after a run.
In my case, before training any models, I should do some time-consuming computations before actual training or evaluation. I usually train a lot of models on single GPUs at once due to resource limitation and the machine is shared with teammates. Because of computations before training, I occupy certain amount of memory sufficient for my model before computations by opening a session to use certain portion of GPU exclusively. If not, other colleague unexpectedly came in and occupy GPU memory resulting out of memory error after time-consuming computation which is annoying and waste of time.

Thanks for the explanation.
As a workaround, did you consider running a dummy operation immediately after creating the session to make sure that memory is reserved immediately after your process starts?

Yes, that's exactly what I do for the time being.
But the old behaviour makes more sense to me. Shouldn't memory be occupied as soon as session is created if allow_growth option is False?

GPU allocators are BFCAllocators with a suballocator that gets large regions of GPU memory.  bfc_allocator.cc is also used for CPU memory.  In that second role it is capable of growing the regions it manages, on demand.  When used for GPU memory we constrain it to grab a single large region in once.  In either case, the first memory region is allocated by the suballocator on demand, the first time an actual AllocateRaw request is presented to the allocator.
What likely caused the change you're seeing is that the allocation of Eigen GPU scratch buffers was moved from GPUDevice creation time to ReinitializeGPUDevice call time.  Hence now you see that the GPU region is not allocated until the first allocation triggered by your TF program.  That was done to break a difficult ordering problem related to properly configuring all the allocators.


Support Pytorch model when packaging

Signed-off-by: jie.hou<EMAIL_ADDRESS>

Please merge the comments :)

/lgtm


ADD: API Endpoint test for the Roster POST and GET Endpoint

GIVEN: I'm an engineer contributing to the PowerPlay repo
WHEN: I make changes to the backend directory
THEN: I see function validation on each PR for the Roster Endpoint
Acceptance Criteria

Roster data must be added to the database before Teams and Games can be tested.

For POST of Roster

Input: Correct data for a new Roster. Output: Status Code 201 is returned.
Input:  Output: Status Code 400 is returned.

For GET of Roster

Input: Correct data for a new Roster. Output: Status Code 200 is returned.
Input:  Output: Status Code 400 is returned.

Test Passes if all output pass, but Fails if one output fails.

API Endpoint test still need to be implemented. The model and db tests have been created.


feature request: display default browser

Description
pretty much self-explanatory. the default browser could be queried with xdg-settings get default-web-browser, for example

This isn't worthwhile baking into neofetch.
Just modify your config.

prin "Browser" "$(xdg-settings get default-web-browser)"
or
prin "Browser" "$BROWSER"

in your print_info() function.
See https://github.com/dylanaraps/neofetch/wiki/Customizing-Info


run binary_packages on Python 3.8, and on latest 3.x

Due to #887 , it occurred to me it may be a good idea to test on the latest version of Python as well, among others to get early warnings of deprecations.

@PetteriAimonen I managed to reproduce #887 in CI, and it rightfully causes the CI to fail. Do you want me to create a new PR with both this repro and the proposed solution from #994 ? Or how do you want me to proceed?

Yes, I think the CI test from this pull request and the fix from #994 would be good. I don't think the check_pkg_resources.sh is necessary if the CI build now catches this.

No, it won't be. That script was a workaround for CI not catching this.

@lubosz can you review the changes? It seems to be working now, but I'm not familiar enough with Python to be sure.
From what I read, this should work in the general case, but there may be some weird edge case with grpcio-tools being installed as an archive that I missed.
CI run showing that it does indeed catch #887

I talked the changes through with someone who has Python experience off GitHub, and he agreed this will work. The only breakage that could happen, which wouldn't with pkg_resources would be if grpcio-tools changes the way it's shipped, and it shomehow is an archive. Which is unlikely, and should be quickly caught by CI anyway.

Thanks a lot!


[MoveLib] Initial checkin of the governance contract

This PR adds the initial governance contract in Move. It contains 4 components:

Genesis: This module creates a singleton system state object along with SUI treasury cap during init. All genesis init values are defined here.
SuiSystem: This module defines the system state type that contains all information of the system. Most entry functions that will be called from validators are here, such as add/withdraw validator, add/withdraw stake and etc.
ValidatorSet: This module defines the validator set. It doesn't contain any entry function, and is used exclusively by SuiSystem to maintain the validator set.
Validator: This module defines the Validator struct.

Workflows of different entities:

A non-validator

A non-validator can first call Validator::create to create a new Validator object with some initial stake. Given the object, they can also add more stake by calling Validator::add_stake, or withdraw stake with Validator::withdraw_stake, or destroy it and get back the stake by calling Validator::destroy.
Once they are satisfied with the object, they can call SuiSystem::request_add_validator to request to become a new validator. After the request is made, they no longer have access to the validator object and is now considered as a pending validator

A pending validator

Once someone did (1) and became a pending validator, they could continue adding stake to that pending validator by calling SuiSystem::request_add_stake, or withdraw some stake by calling SuiSystem::request_withdraw_stake. The effects of these two calls are immediate.
They can also call SuiSystem::request_withdraw_validator. The effect is also immediate: they will no longer be a pending validator and the object is sent back.
At the end of an epoch, if the pending validator meets all conditions, it will become an active validator.

An active validator.

Similarly, one can request adding/withdraw stake on an active validator. However the effect will not be immediate, and will only be processed at the end of epoch. They can also request to withdraw the validator itself, which will also be requested at the end of epoch.
TODO: Add unittests
Things not covered by this PR and will be done in future PRs:

gas pricing
stake award distribution
stake delegations

This is awesome, especially since there's been a number of questions recently about the shape of what the ValidatorSet would look like.
Just as a point of clarification, this doesn't currently support delegating stake to a Validator (either active or pending) correct? I suspect that would complicate things given you'd need extra bookkeeping for mapping delegated stake back to some other address not affiliated with the Validator.

Just as a point of clarification, this doesn't currently support delegating stake to a Validator (either active or pending) correct? I suspect that would complicate things given you'd need extra bookkeeping for mapping delegated stake back to some other address not affiliated with the Validator.

Right, I haven't implemented delegation yet. It will be quite complex.

Addressed all feedback:

ip_address is now vector
Added max_validator_candidate_count to constrain the max number of validator candidates
Do not allow stake withdraw or validator removal for pending validators (but still allow adding stake for pending validators)
We no longer sort the validators by stake, because any validator that meets the min/max stake requirement can become alive in the next epoch.
Add total_stake and quorum_threshold

Added tests

Any other feedback?

Any other feedback?

I'm reading it now. But mostly for my own edification so not sure how much feedback I'll have. Other than most of these files are missing a new line at the end :P (great feedback, I know)

Other than most of these files are missing a new line at the end :P (great feedback, I know)
@tnowacki I haven't gotten around to setting up robust linting like we have on the move repo yet. But I want to because this sort of stuff weirdly bothers me too lol

Addressed Alonso's feedback.

@sblackshear Great question!
For what's written, yes using non-key Validator would be a lot simpler.
The only thing that I haven't made my mind around, is whether we ever want the Validator objects to be child objects, instead of wrapped ones.
There are some benefits there:

Keep the system state object small (esp if there is a size limit)
Easier for anyone to see the content of the individual validator object

Made Validator a non-key object


How to shared Monitor object between multi thread

How to shared Monitor object between multi thread?
When I use Monitor with actix-web, I want to shared monitor object by app_data,like bellow:
let mut monitor = Arc::new(Mutex::new(Monitor::::new()));
HttpServer::new(move || {
App::new()
.app_data(email_data.clone())
.app_data(monitor)
.service(web::scope("/emails").route("/push",web::post().to(push_email)))
})
but this code can not run.
The error is ：
the trait bound std::sync::MutexGuard<'_, apalis_core::monitor::Monitor<apalis::utils::TokioExecutor>>: Clone is not satisfied in {closure@examples\rest-api\src/main.rs:220:25: 220:32}
within {closure@examples\rest-api\src/main.rs:220:25: 220:32}, the trait Clone is not implemented for std::sync::MutexGuard<'_, apalis_core::monitor::Monitor<apalis::utils::TokioExecutor>>, which is required by {closure@examples\rest-api\src/main.rs:220:25: 220:32}: Clone

I will look into why this doesn't work.
I am curious though, why do you need to share the Monitor around? Monitor will not allow you to do much apart from registering workers and listening for shutdown.

Yeah，I read some job info from  http request，the job info contains cron info and some other，so，I share the monitor to register some worker，the worker run with diff crons

This looks like an actix issue, it accepts a callback and everything needs to be clone
You should do:
.app_data(monitor.clone())


Recycle Bin - Add Deleted Date

Description of problem
We run into many issues with folks deleting content and us not being able to see what else was deleted at that given time period.
Description of solution
Provide a deleted date column in the recycle bin.
Description of alternatives considered

None that we can tell, aside from manually looking through recycle bin and seeing what other content was on that page and then figuring out whether it was deleted in error or before-hand on purpose.

Screenshots

Clear-cut, no screenshots needed.

Additional context

Clear-cut, none needed.

Affected version

[ ] 9.3.0
[x] 9.2.2
[x] 9.2.1
[x] 9.2
[x] 9.1.1
[ ] 9.1
[ ] 9.0

Affected browser

[x ] Chrome
[x ] Firefox
[x ] Safari
[x ] Internet Explorer
[x ] Edge

Absolutely great feature! Maybe even sorted by deletion date descending or being able to sort by clicking on the table header.

There is a deleted date in 9.4.0 RC as far as I can see but sorting would be super useful, sorting by any columns that is. For that reason I am renaming the issue and moving it to AdminExperience


Added System.Range to system types

Hello @svick, thank you for submitting this pull request. We will try to get back to you as soon as possible.
Note to the PostSharp team, this ticket is being tracked in our dashboard under ID TP-32532.


use the new 'deployment' arg to get deployment events associated even…

… when minified
@birdage , this (along with the services PR) address the issue you saw last night; reducing the json size to 1.5 MB.  Still large, but much better than 8+MB!

@FBRTMaka thats better i knew we could do it/use it!


add option to remove timeout when debugging containers

I want to start getting more changes reviewed in Horton, mostly to share the love, but also to make sure I'm not doing anything dumb.
For this one, I needed to add an option to completely disable test timeouts when debugging a container, so the test runner doesn't give up and move to the next test while you're in the middle of debugging something.  Along the way, I discovered that msrest has a timeout mechanism built in, so i was able to leverage this and remove my old decorator-based, worker-thread-based timeouts, which is a huge bonus.


Module resolution npm: alias mapping assumes node_modules and eleventy config exist in same directory

First of all: you rock! Love the projects, excellent work, very grateful ❤
I described my issue in a comment in some more detail over in the eleventy-plugin-webc repo.
I have an issue loading the is-land plugin in an 11ty webc project. I have a large, complicated webapp codebase, where eleventy is but a small part of a larger system. The eleventy bits are located in a subdirectory of this project, ./public, while the package.json for this project exists one directory up, in the root of the project. Thus, node_modules exists one parent directory above where the eleventy project exists.
My particular problem boils down to two issues, I think, which are related:

The fsCache module seems (to me) unnecessarily restrictive re: requiring components to be subdirectories of the "working directory"
npm: component loading aliasing assumes npm: maps to ./node_modules

Issue (1) effectively prevents setting webc component loading to any directory that is not an immediate subdirectory within the eleventy project. For a monorepo style setup, this seems like an unnecessarily restrictive constraint. As mentioned, since in my setup, node_modules is one level up above the eleventy project, that exception is troublesome. Could we consider dropping the code I linked to in (1)?
Issue (2) is related to the same problem: the npm: component loading alias assumes something about the location of the node_modules directory. There is a TODO here, tantalizingly hinting at perhaps the author foreseeing an issue similar to what I'm describing here. I was thinking one way to improve this would be to search up the file tree to find the npm project root first (by looking for the presence of a package.json file), and then joining that found project root with ./node_modules. I think that would solve this issue? What do you think?
I am happy to give a PR a go to try to fix this! I wanted first to check if my thinking is correct / is a PR worth it / would the project be responsive to the issue / provide guidance on how to go about improving the situation.
Thanks for any discussion and thank you once more for an amazing open source project!

Issue (1) was introduced to fix #10.
Limiting the scope to subdirectories is a good security measure.
I would expect the monorepo tool (lerna and friends) to handle the dependencies properly. Are you allowed to share how you manage the repo?

Apologies, I have since moved to a different solution and have stopped using webc as a result. Unfortunately, I did not save the project state from that time 😢

That's fine. Do you mind to close this issue?


Upgrade Gradle to 7.6

closes #350

Just FYI, Gradle 8 will be out soon (there's already a release candidate).


Unplug vif

This is more a question, so sorry beforehand:
How can I plug/unplug a VIF?
There is a plug_vif and unplug_vif but I don't know what object has it.
Thanks

So the main intention here is to make everything feel more encapsulated. So instead of calling the requests directly from the connections object you can call them directly on the objects.
Since its a vif method you can call it directly on the vif object.
# handle connection
@connection = 'bla bla bla'

# load the vif
@vif = @connections.vifs.first

# plug the vif
@vif.plug

# unplug the vif
@vif.unplug

Let me know if you have more questions. Thanks!


add ability to use git and git branch if we need to test experimental…

… FTW code

Looks good to me


RemoveTestingApolloClient

Description
This PR removes the TestingApolloClient in favour of using the ApolloClient directly.
Fixes (issue #)

/snapit


Add CONTRIBUTING.md

Let's add this contributing. It is for my programmation studies in Edu School, and I think it would be very usefeul, not only for me, also to my classmates. Thanks!

@Joako2373 Regrettably, this request has signs of fraud. I have to close it without merging.


Fixes #11 : add null| to annotation to routeMatch

Fixes #11

@Ocramius is this change what you meant ?


Sp23 sprint1 diana montano salama

Sprint 1

Retained QA branch package-lock.json, added Diana's data to datareports after checking for duplicates


Sample data updates from Danforth meeting

add soil mask images to Sample Data
generate rgb enhanced images from sample data RGB geotiffs
run hyperspectral QA/QC on 2017 data

The hyperspectral will be covered in separate issue: https://github.com/terraref/computing-pipeline/issues/584 The others are done.