thread 'tokio-runtime-worker' panicked at 'called Result::unwrap() on an Err value: could not fetch bootstrap

If this PR https://github.com/a16z/helios/pull/253/files, as at commit f4a7d4c66a770f437c79a0842d9b387544fce5de, if i run the following to build a Docker container using Ubuntu 23.04
./docker/docker.sh

and then after that script enters me into the container i run
cargo run -p helios --example client

it outputs the following:
    Finished dev [unoptimized + debuginfo] target(s) in 0.65s
     Running `target/debug/examples/client`
Constructed client!
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: could not fetch bootstrap

Location:
    /opt/consensus/src/consensus.rs:304:26', /opt/consensus/src/consensus.rs:80:32
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

i'm using version nightly-2023-07-31 in the Docker container, because the latest master branch uses that version in the rust-toolchain file

In your example, you are using lightclientdata.org, which serves ethereum mainnet data, but you are using the goerli configs and a goerli execution rpc.
Also note that we are working on a couple of PRs to clean a few things up, so the current state of master will be in a bit of a weird spot for the next few days.

actually, now that i'm connecting to Goerli with the right endpoint, that error could not fetch bootstrap is because it can't get the checkpoint
i also noticed the instructions in config.md, which say to paste the following in ~/.helios/helios.toml.
so i ran the following
mkdir -p ~/.helios
mkdir -p /root/.helios/data/goerli
vim ~/.helios/helios.toml

Then pasted the following in ~/.helios/helios.toml
[goerli]
# The consensus rpc to use. This should be a trusted rpc endpoint. Defaults to Nimbus testnet.
consensus_rpc = "http://testing.prater.beacon-api.nimbus.team"
# [REQUIRED] The execution rpc to use. This should be a trusted rpc endpoint.
execution_rpc = "https://ethereum-goerli-rpc.allthatnode.com"
# The port to run the JSON-RPC server on. By default, Helios will use port 8545.
rpc_port = 8545
# The latest checkpoint. This should be a trusted checkpoint that is no greater than ~2 weeks old.
# If you are unsure what checkpoint to use, you can skip this option and set either `load_external_fallback` or `fallback` values (described below) to fetch a checkpoint. Though this is not recommended and less secure.
checkpoint = "0xb5c375696913865d7c0e166d87bc7c772b6210dc9edf149f4c7ddc6da0dd4495"
# The directory to store the checkpoint database in. If not provided, Helios will use "~/.helios/data/goerli", where `goerli` is the network.
# It is recommended to set this directory to a persistent location mapped to a fast storage device.
data_dir = "/root/.helios/data/goerli"
# The maximum age of a checkpoint in seconds. If the checkpoint is older than this, Helios will attempt to fetch a new checkpoint.
max_checkpoint_age = 86400
# A checkpoint fallback is used if no checkpoint is provided or the given checkpoint is too old.
# This is expected to be a trusted checkpoint sync api (like provided in https://github.com/ethpandaops/checkpoint-sync-health-checks/blob/master/_data/endpoints.yaml).
fallback = "https://sync-goerli.beaconcha.in"
# If no checkpoint is provided, or the checkpoint is too old, Helios will attempt to dynamically fetch a checkpoint from a maintained list of checkpoint sync apis.
# NOTE: This is an insecure feature and not recommended for production use. Checkpoint manipulation is possible.
load_external_fallback = true

But when i ran cargo run -p helios --example client i still got the same error could not fetch bootstrap
i'm also confused about how to check if the checkpoint hash is valid or not. my understanding is that a checkpoint hash should be a block hash for that network that is no greater than ~2 weeks old
if i go to https://goerli.etherscan.io/block/0xb5c375696913865d7c0e166d87bc7c772b6210dc9edf149f4c7ddc6da0dd4495 it says it can't locate that block hash. but that's a value that is provided in the default config.md.
and if i follow the instructions in config.md, by using a trusted checkpoint that is no greater than ~2 weeks old. such as block 9528294 that i found has block hash 0xfbec233115dc7497df5f6d06ca819a0de14c1d47a2b8903ab85607c0af4b5ff2, and that that block hash exists and was finalised https://goerli.etherscan.io/block/0xfbec233115dc7497df5f6d06ca819a0de14c1d47a2b8903ab85607c0af4b5ff2, so i add that in ~/.helios/helios.toml and also in client.rs, but when i run cargo run -p helios --example client i still get the same error

Yes so the checkpoint is a beaconchain blockhash, rather than a execution block hash. This checkpoint is way to old (nearly a year). Normally, when it fails the fallback would kick in and automatically fetch a better one, but due to the refactors I mentioned that feature is currently not working.
To find a better checkpoint, you can go to https://prater.beaconcha.in/ and get the blockhash for the first block in any epoch. For example, the first blockhash in epoch 197110 is 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b which should work.

Yes so the checkpoint is a beaconchain blockhash, rather than a execution block hash. This checkpoint is way to old (nearly a year). Normally, when it fails the fallback would kick in and automatically fetch a better one, but due to the refactors I mentioned that feature is currently not working.
To find a better checkpoint, you can go to https://prater.beaconcha.in/ and get the blockhash for the first block in any epoch. For example, the first blockhash in epoch 197110 is 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b which should work.

thanks i tried using that blockhash from the beaconchain in this commit https://github.com/a16z/helios/pull/253/commits/b638ea602000adf62eac3b01f6ad8316945593d0 where i also added that blockhash to in the file ~/.helios/helios.toml as the checkpoint value for [goerli], but for some reason i still get the same error still

Hmm when I try to run it with these settings outside of docker by doing cargo run -- -n goerli -c http://testing.prater.beacon-api.nimbus.team -e https://ethereum-goerli-rpc.allthatnode.com --checkpoint 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b it seems to sync correctly. Is it possible your docker environment is causing issues?

cargo run -- -n goerli -c http://testing.prater.beacon-api.nimbus.team -e https://ethereum-goerli-rpc.allthatnode.com --checkpoint 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b

i just tried running the same command inside the Docker container:
cargo run -- -n goerli -c http://testing.prater.beacon-api.nimbus.team -e https://ethereum-goerli-rpc.allthatnode.com --checkpoint 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b

and it output the
[2023-08-16T21:43:20Z INFO  client::rpc] rpc server started at <IP_ADDRESS>:8545
[2023-08-16T21:43:31Z INFO  consensus::consensus] updated head               slot=6307990  confidence=82.81%  age=00:05:05:31
[2023-08-16T21:43:31Z INFO  consensus::consensus] sync committee updated
[2023-08-16T21:43:31Z INFO  consensus::consensus] finalized slot             slot=6307904  confidence=82.81%  age=00:05:22:43
[2023-08-16T21:43:33Z INFO  consensus::consensus] updated head               slot=6309516  confidence=82.62%  age=00:00:00:21
[2023-08-16T21:43:33Z INFO  consensus::consensus] finalized slot             slot=6309440  confidence=82.62%  age=00:00:15:33
[2023-08-16T21:43:34Z INFO  consensus::consensus] consensus client in sync with checkpoint: 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b
[2023-08-16T21:43:43Z INFO  consensus::consensus] updated head               slot=6309517  confidence=82.81%  age=00:00:00:19

so things to try or consider now are

try change load_external_fallback to false in ~/.helios/helios.toml  --> didn't work
whether i need to use a proxy like in helios-ts where they use executionRpc:"http://localhost:9001/proxy",, and consensusRpc: "http://localhost:9002/proxy", but i'm only exposing port 8545
what other Helios CLI options to use from the help menu cargo run -- --help

    -b, --rpc-bind-ip <RPC_BIND_IP>        [env: RPC_BIND_IP=]
    -c, --consensus-rpc <CONSENSUS_RPC>    [env: CONSENSUS_RPC=]
    -d, --data-dir <DATA_DIR>              [env: DATA_DIR=]
    -e, --execution-rpc <EXECUTION_RPC>    [env: EXECUTION_RPC=]
    -f, --fallback <FALLBACK>              [env: FALLBACK=]
    -h, --help                             Print help information
    -l, --load-external-fallback           [env: LOAD_EXTERNAL_FALLBACK=]
    -n, --network <NETWORK>                [default: mainnet]
    -p, --rpc-port <RPC_PORT>              [env: RPC_PORT=]
    -s, --strict-checkpoint-age            [env: STRICT_CHECKPOINT_AGE=]
    -V, --version                          Print version information
    -w, --checkpoint <CHECKPOINT>          [env: CHECKPOINT=]

so i tried
cargo run -p helios --example client -- -n goerli -c http://testing.prater.beacon-api.nimbus.team -e https://ethereum-goerli-rpc.allthatnode.com --checkpoint 0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b -p 8545 -l false -f https://sync-goerli.beaconcha.in -d /root/.helios/data/goerli -b <IP_ADDRESS>

but that gave the same error too

When running Helios as a library config files and cli arguments are not used. All configuration is done using the ClientBuilder

so in consensus.rs, in the Inner function bootstrap, when it calls get_bootstrap(&self.initial_checkpoint), that calls get_bootstrap in file nimbus_rpc.rs, snippet below
        let mut bootstrap = self
            .rpc
            .get_bootstrap(&self.initial_checkpoint)
            .await
            .map_err(|_| eyre!("could not fetch bootstrap"))?;

which constructs a req variable "http://testing.prater.beacon-api.nimbus.team/eth/v1/beacon/light_client/bootstrap/0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b", which i can successfully load here http://testing.prater.beacon-api.nimbus.team/eth/v1/beacon/light_client/bootstrap/0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b
which shows it uses "capella" fork of Goerli, which starts from epoch 162304 according to helios/config/src/networks.rs
but it doesn't get past this line even though its using that req value, so it propagates an error from that function instead of returning Ok(res.data)
        let res = client
            .get(req)
            .send()
            .await
            .map_err(|e| RpcError::new("bootstrap", e))?
            .json::<BootstrapResponse>()
            .await
            .map_err(|e| RpcError::new("bootstrap", e))?;

i changed the line to .map_err(|e| eyre!("could not fetch bootstrap {}", e))?; to output the error, and the error was:
rpc error on method: bootstrap, message: error sending request for url (http://testing.prater.beacon-api.nimbus.team/eth/v1/beacon/light_client/bootstrap/0x7beab8f82587b1e9f2079beddebde49c2ed5c0da4ce86ea22de6a6b2dc7aa86b): error trying to connect: dns error: task 8 was cancelled

i'm not sure yet how to debug further to find out what task 8 refers to

task 8 was cancelled

so that error implementation is here https://github.com/tokio-rs/tokio/blob/master/tokio/src/runtime/task/error.rs#L138

i get the similar errors running the basic example, as shown below
run basic example
cargo run -p helios --example basic

outputs error
[2023-08-17T05:50:56Z INFO  basic] Built client on network "GOERLI" with external checkpoint fallbacks
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: could not fetch bootstrap rpc error on method: bootstrap, message: error sending request for url (http://testing.prater.beacon-api.nimbus.team/eth/v1/beacon/light_client/bootstrap/0x428474ba0c1ce5049efe4324d503f69f0370fae2095954db4864c57097c90574): error trying to connect: dns error: task 9 was cancelled

Location:
    /opt/consensus/src/consensus.rs:308:26', /opt/consensus/src/consensus.rs:83:32
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: block not available: latest

i also get similar errors running the call example, as shown below
run call example
cargo run -p helios --example call

outputs error
[2023-08-17T05:46:31Z INFO  call] [ABIGEN] 0x8bb9a8baeec177ae55ac410c429cbbbbb9198cac::renderBroker(uint256) -> Response Length: 106476
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: could not fetch bootstrap rpc error on method: bootstrap, message: error decoding response body: missing field `data` at line 1 column 49

Location:
    /opt/consensus/src/consensus.rs:308:26', /opt/consensus/src/consensus.rs:83:32
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
[2023-08-17T05:46:32Z INFO  call] [ABIGEN] 0x8bb9a8baeec177ae55ac410c429cbbbbb9198cac::renderBroker(uint256, uint256) -> Response Length: 64549
[2023-08-17T05:46:32Z DEBUG call] Calling helios client on block: Latest
Error: block not available: latest

Location:
    /rustc/a17c7968b727d8413801961fc4e89869b6ab00d3/library/core/src/convert/mod.rs:716:9

I think errors like thread 'tokio-runtime-worker' panicked at 'called Result::unwrap()on anErrvalue: could not fetch bootstrap rpc error on method: bootstrap, message: error decoding response body: missing fielddata at line 1 column 49  are caused because I switched from using Alchemy to a different provider, not recognising the warning that is already in the README.md file that says that the Execution RPC must be an Ethereum provider that supports the eth_getProof endpoint, and that providers like Infura does not currently support this, and that Alchemy is recommended

I think errors like thread 'tokio-runtime-worker' panicked at 'called Result::unwrap() on an Err value: could not fetch bootstrap rpc error on method: bootstrap, message: error decoding response body: missing field data at line 1 column 49 are caused because I switched from using Alchemy to a different provider, not recognising the warning that is already in the README.md file that says that the Execution RPC must be an Ethereum provider that supports the eth_getProof endpoint, and that providers like Infura does not currently support this, and that Alchemy is recommended.
For example, I changed GOERLI_EXECUTION_RPC=https://eth-goerli.g.alchemy.com/v2/XXXXX in the .env.example file to GOERLI_EXECUTION_RPC=https://ethereum-goerli-rpc.allthatnode.com, but i think that causes the issue

actually i still seem to get the same error using Alchemy

The most recent errors have been resolved as per #258


Linking issues on main

Noticing that test.yaml CI builds on main are failing to link on ubuntu. This is just a PSA that I'm debugging that over here.

Looks like GitHub quietly changed the parsing of $GITHUB_ENV, so my doubled quoted things broke. 😒 Fixed in https://github.com/oxidize-rb/actions/commit/20e615d6ade0383b762c2a342c2da1a7b00fa24c


Handle launch of tuihtml script when output_html.html does not exist

$ tuihtml

Traceback (most recent call last):
  File "/Users/jwr003/repos/gems-qa-auto/venv/bin/tuihtml", line 8, in <module>
    sys.exit(main())
  File "/Users/jwr003/repos/gems-qa-auto/venv/lib/python3.9/site-packages/pytest_tui/html.py", line 63, in main
    (mode, ino, dev, nlink, uid, gid, size, atime, mtime, ctime) = os.stat(
FileNotFoundError: [Errno 2] No such file or directory: '/Users/jwr003/repos/gems-qa-auto/gems_qa_tests/results/output_html.html'

Done


Updating .gitignore for existing version of PASS

Is your feature request related to a problem? Please describe.
Previous .gitignore file includes items that was relevant to a previous version of PASS when it was still using Parcel as a bundler instead of Vite.
Describe the solution you'd like
The fix for this is simply to remove the paths that no longer exist.

Branch with updated .gitignore merged into Development


World data load bug

I seem to have a bug here: https://ibb.co/kyKCLn7
When I spawn a new world for the first time, it works ok. If I go back to the main menu and spawn a new world again, the bug shown in the picture occurs.
My modlist:
Mod Manager
Queue for Sinks
More Marble Structures
Missing Element Textures
Airlock Door
Fast Save
Forbid Items
GasOverlay
DGSM
Survival Not Required
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This bug also occurs after the following sequence of events:

Generate world and arrive at initial dupe selection screen
Back out to the main menu
Generate world and arrive at initial dupe selection screen
Back out to the main menu
Crash to desktop

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Suggestion from another mod author:
Aki: "they accidentally apply the template modifications at every world data load, instead of once per game load.
should be an easy fix, its a simple oversight."

Hi @Yossarian82,
thank you for finding and reporting this bug! Aki was right about the source of this issue: I patched the world templates every time a world is generated. A simple check to avoid patching more than once fixed this. :-)
Version 1.1.1 is live on Steam Workshop, please give it a try!


python312Packages.google-cloud-dataproc: 5.10.0 -> 5.10.2

Changelog: https://github.com/googleapis/google-cloud-python/blob/google-cloud-dataproc-v5.10.2/packages/google-cloud-dataproc/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 339496 run on x86_64-linux 1

8 packages built:

python311Packages.dbt-bigquery
python311Packages.dbt-bigquery.dist
python311Packages.google-cloud-dataproc
python311Packages.google-cloud-dataproc.dist
python312Packages.dbt-bigquery
python312Packages.dbt-bigquery.dist
python312Packages.google-cloud-dataproc
python312Packages.google-cloud-dataproc.dist


Use notification channel on Android

This is required for Android Oreo.
Hard-code channel parameters for now.

r? @keybase/react-hackers

Compare to https://github.com/zo0r/react-native-push-notification/pull/657

Yes, this is on top of keybase-fixes-off-302


Field is not set when not part of the update modifier

I would like to use the custom function like this.
amount: {
    type: Number,
    decimal: true,
    custom: function () {
      let currency = this.field('currency');
      if (this.isSet && currency.isSet) {
        let transactionMinimumAmount = Currencies.findOne({
          code: currency.value
        }).transactionMinimumAmount;
        if (this.value < transactionMinimumAmount) {
          return 'minNumber';
        }
      }
    }
  }

Problem is, if I update my document setting only the amount field as in {$set: {amount: 8}}, the currency field is never set and the check is not performed.
This workaround works, but is not pretty.
amount: {
    type: Number,
    decimal: true,
    custom: function () {
      let currency = this.field('currency');
      if (this.isSet) {
        // to avoid dirty checking like this
        if (!currency.isSet) {
          let plan = Plans.findOne(this.docId);
          currency = {
            value: plan.currency
          };
        }
        let transactionMinimumAmount = Currencies.findOne({
          code: currency.value
        }).transactionMinimumAmount;
        if (this.value < transactionMinimumAmount) {
          return 'minNumber';
        }
      }
    }
  }

Is that normal behavior?

Yes, that is expected. simple-schema does not have any knowledge of what data is in your database. It only helps you validate the modifier object you give it.


Fix edge case where validations may not show up

Description

The culprit turned out to be checking shouldValidateNode inside of getValidationsForNode. The result of this could somehow change without the node reference updating. This may be due to reusing nodes when they supposedly have not changed? Needed to add back the filter on shouldValidateNode the few places that were missing it, most users of getValdiationsForNode were already using it anyway.
The changes in ComponentValidations are not related, but noticed that the key was a bit fragile.
Related Issue(s)

https://altinn.slack.com/archives/C02EJ9HKQA3/p1716540609951709

Verification/QA

Manual functionality testing

[x] I have tested these changes manually
[ ] Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
[ ] No testing done/necessary

Automated tests

[ ] Unit test(s) have been added/updated
[ ] Cypress E2E test(s) have been added/updated
[ ] No automatic tests are needed here (no functional changes/additions)
[ ] I want someone to help me make some tests

UU/WCAG (follow these guidelines until we have our own)

[ ] I have tested with a screen reader/keyboard navigation/automated wcag validator
[x] No testing done/necessary (no DOM/visual changes)
[ ] I want someone to help me perform accessibility testing

User documentation @ altinn-studio-docs

[ ] Has been added/updated

[x] No functionality has been changed/added, so no documentation is needed
[ ] I will do that later/have created an issue

Support in Altinn Studio

[ ] Issue(s) created for support in Studio

[x] This change/feature does not require any changes to Altinn Studio

Sprint board

[x] The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
[ ] I don't have permissions to do that, please help me out

Labels

[x] I have added a kind/* label to this PR for proper release notes grouping
[ ] I don't have permissions to add labels, please help me out

Oooh, would it be possible to create a Cypress test for this?
I can try, but I have never seen this happen before in any other app, so I am not quite sure how it can be reproduced


Here2 UAVCAN: PX4 does not detect MS5611 Baro

I'm testing an Here2 Module in UAVCAN mode on a Pixhawk4 Board.
The PX4 version I'm running is the stable 1.9.2 and I have the UAVCAN_ENABLE parameter set to 2.
PX4 can successful recognize the Gps Antenna and the Here2 Magnetometer.
I'm instead not able to let the Here2 Barometer MS5611 show as a new barometer.Seems like PX4 is not recognizing it.
Here is my /dev/ folder ls output:

accel0
accel1
adc0
baro0
bmi055_accel
bmi055_gyro
console
gyro0
gyro1
icm20689
ist8310_int
led0
mag0
mag1
mmcsd0
ms5611_spi_int
mtdblock0
mtdblock1
null
pipe0
pipe1
pwm_output0
px4io
range_finder0
range_finder1
rgbled_pwm0
tone_alarm0
ttyACM0
ttyS0
ttyS1
ttyS2
ttyS3
ttyS4
ttyS5
ttyS6
uavcan/

I'm back on this issue with some more details:
I checked the system console during the system boot on a Pixhawk3 board where I have a direct access to the debug ports (the behavior is the same of the Pixhawk 4 one):

MCU: STM32F???, rev. A
[hardfault_log] Fault Log is Armed
INFO  [tune_control] Publishing standard tune 1
INFO  [param] selected parameter default file /fs/mtd_params
Board defaults: /etc/init.d/rc.board_defaults
rgbled on I2C bus 1 at 0x55 (bus: 100 KHz, max: 100 KHz)
WARN  [rgbled_ncp5623c] no RGB led on bus #1
nsh: rgbled_pwm: command not found
WARN  [blinkm] I2C init failed
WARN  [blinkm] init failed
Board sensors: /etc/init.d/rc.board_sensors
WARN  [mpu6000] no device on bus #3 (SPI1)
MPU6000 on SPI bus 1 at 14 (1000 KHz)
INFO  [mpu9250] Bus probed: 3
MPU9250 on SPI bus 1 at 4 (1000 KHz)
INFO  [mpu9250] accel cutoff set to 30.00 Hz
INFO  [mpu9250] gyro cutoff set to 30.00 Hz
WARN  [lis3mdl] no device on bus 2
WARN  [lis3mdl] no device on bus 1
LIS3MDL_SPI on SPI bus 1 at 7 (11000 KHz)
INFO  [lis3mdl] Poll rate set to max (80hz)
WARN  [hmc5883] no device on bus 2 (type: 2)
WARN  [qmc5883] no device on bus 2 (type: 2)
WARN  [rm3100] no device on bus 2
WARN  [rm3100] no device on bus 1
RM3100_SPI on SPI bus 5 at 1 (1000 KHz)
WARN  [rm3100] no device on bus 4
MS5611_SPI on SPI bus 1 at 3 (20000 KHz)
WARN  [bst] no devices found
INFO  [uavcan] Node ID 20, bitrate 1000000
INFO  [uavcan] sensor bridge 'gnss' init ok
INFO  [uavcan] sensor bridge 'mag' init ok
INFO  [uavcan] sensor bridge 'baro' init ok
WARN  [uavcan] CentralizedServer init: -13
WARN  [uavcan] Node init failed: -13
ERROR [uavcan] Firmware Server Failed to Start -13
INFO  [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
uavcan_mag adding channel 20...
uavcan_mag channel 20 class instance 2 ok
WARN  [uavcan] GNSS ORB fd 8
Starting Main GPS on /dev/ttyS3
Starting MAVLink on /dev/ttyS1
INFO  [mavlink] mode: Normal, data rate: 1200 B/s on /dev/ttyS1 @ 57600B
INFO  [px4io] default PWM output device
INFO  [init] Mixer: /etc/mixers/hexa_x.main.mix on /dev/pwm_output0
px4flow [438:100]
INFO  [px4flow] scanning I2C buses for device..
INFO  [logger] logger started (mode=all)
NuttShell (NSH)
nsh> WARN  [uavcan] GNSS receiver node ID: 20
WARN  [uavcan] GNSS ORB->UAVCAN bridge stopped, because there are other GNSS publishers
INFO  [ecl/EKF] EKF aligned, (pressure height, IMU buf: 22, OBS buf: 14)

I report the output of UAVCAN status too, hope it can help:

nsh> uavcan status
Pool allocator status:
Capacity hard/soft: 500/250 blocks
Reserved:  28 blocks
Allocated: 11 blocks
UAVCAN node status:
Internal failures: 0
Transfer errors:   0
RX transfers:      17414
TX transfers:      727
CAN1 status:
HW errors: 95
IO errors: 95
RX frames: 30682
TX frames: 505
CAN2 status:
HW errors: 85117
IO errors: 85117
RX frames: 0
TX frames: 485
ESC actuators control groups: sub: 0 / req: 0 / fds: 2
ESC mixer: NONE
Sensor 'gnss':
RX errors: 0, using old Fix: 1, receiver node id: 125
Sensor 'mag':
devname: /dev/mag
channel 0: node id 125 --> class instance 1
channel 1: empty
channel 2: empty
channel 3: empty
channel 4: empty
Sensor 'baro':
devname: /dev/baro
channel 0: empty
channel 1: empty
channel 2: empty
channel 3: empty
channel 4: empty
Online nodes (Node ID, Health, Mode):
125 OK         OPERAT


Apply Custom Validators without the need of a DB lookup for ContentType

Closes: #DNE
What's Changed
Observing the need for this: https://github.com/nautobot/nautobot/pull/3614/files#diff-cca2a364f59877c49898f8d14d311f7567adfb80b5aec6fa51748be4f79ef9b5R44-R46
This might be one of the weird DB calls we see on startup pre-fork in Celery 🤷
TODO

[x] Explanation of Change(s)
[ ] Added change log fragment(s) (for more information see the documentation)
[ ] Attached Screenshots, Payload Example
[ ] Unit, Integration Tests
[ ] Documentation Updates (when adding/changing features)
[ ] Example Plugin Updates (when adding/changing features)
[ ] Outline Remaining Work, Constraints from Design

Brilliant!


Backports: networkx, context cleanup

Backports:

networkx tight pin for remaining v1.1 patches (https://github.com/dbt-labs/dbt-core/issues/5286#issuecomment-1146262827)
docs + code cleanup in https://github.com/dbt-labs/dbt-core/pull/5334

Let's include both of these in v1.1.1-rc2

I thought 1.1 didn't have the networkx problem?

@gshank It didn't, but we're still using a less-than-ideal method (relative to new approach proposed in https://github.com/dbt-labs/dbt-core/pull/5326).
Per https://github.com/dbt-labs/dbt-core/issues/5286#issuecomment-1146262827:

I like pinning 1.1 and not backporting since it's a change that introduces risk. We can add that to the RC2 that we are going to push out soon

Makes sense.


Resolve round edge cases in Snowflake backend

While working on #9486 I have disabled some edge case tests by marking them pending, because they were behaving differently than on Postgres and thus failing.
We should update the scheme to correctly handle this testing - either adding a separate test for Snowflake or updating the test to accept either behavior.

On hold until the PR disabling the tests gets merged.


Optimal path generated by GNN model smoother is not collison-free

Hi,
I tried GNN smooter to find the optimal path but I notice that the current implementation cannot ensure collision-free. Here is an example from 'maze2hard' environment and index = 2. GNN explorer can find the collison free path,  but the optimal path obtained by GNN smoother is not collison-free as the below figure shows. Specificallty, I set smoother ='model' and let this line https://github.com/rainorangelemon/gnn-motion-planning/blob/76d9f580a0bdbaee0522f02f15166bfd852d7a22/eval_gnn.py#L255 to find the smooth path.

Would you please take a look at it? I will also try to debug it and create a pull request to fix it. Thanks.
Best regards,
Wenjin

Fixed with pull request


Update checks-action to 1.1.1

the checks action we use has updated again recently, and possibly with an issue that solves the deployment_status issue which has been the main hurdle of Link Check since GitHub Actions were introduced to it.

I opened this PR to test, and it seems a simple version change doesn't fix the issue. The new sha field may be an avenue we can take for fixing the Checks issue, however.
For now, I'll close this PR so as not to leave this dangling while I focus on other things. I'll either reopen this or make a new issue in the future.


chore: bump ethers

companion for https://github.com/gakonst/ethers-rs/pull/766

Doing in separate #397


Can we add support for overflow:scroll blocks?

We would need to change the API a little bit so that we can bind the stickyfill to a particular block instead of the whole page, not to mention we may have multiple scrollable blocks on a single page.
Any reason why this hasn't been done already? I can start working on a fix for this if its desirable?

The reason is me being lazy, mainly. This shouldn’t change the API, actually. But instead of one global scroll listener we would need one for each overflow context. I’ll poke around it in the next few days.

Thanks, I think this would be incredibly useful, let me know if you would like some help figuring this out.

Hey, so I tried different approaches and the major problem is that there’s no good way to make fixed positioning work inside a scrollable block.
One way is to make a wrapper div and position sticky block inside it. The cons of this approach:

wrapper modifies the DOM structure, can potentially mess up the styles and other things
sticky block has to be moved up in the DOM tree to be absolutely positioned in the wrapper (again, DOM modifications)
has to somehow account for scrollbar widths
hard to implement stickies that are partly covered by the edge (e.g. top: -10px)

So this isn’t really an option.
The other way is to set a zero transform (transform: translateX(0)) to scrollable block which forces new coordinate system on that block. This works in IE and Edge, fixed block becomes fixed inside the scrollable area, but the block flicks and jerks, doesn’t look very nice. In Chrome and FF fixed block becomes absolutely positioned.
So it’s not really worth it. It won’t work in old Chrome and FF versions and it looks crappy in IE/Edge.
If you have any ideas of how to implement this, please share.
Closing for now.

It seems this is unfixable on IE11 and other browsers which do not support sticky elements. =/

Is there any workaround for this? Something one can for a specific project, without having to worry much about DOM modifications, compatibility with every older browser (except for IE11 :( ) etc?


Simulation UI - Add slider to control how much time a crashed vehicle lasts until it is destroyed

Done!


Collapse Search Panels - Dock 2317

Description
Following the mocks, the search sidebar has a new default state in which about half of the panels are collapsed.  A nice little change which avoids that long scroll to the bottom of the page.  As Charles suggested in the ticket, the state of the panels is saved to local storage, so upon page reload or navigation, the panels that have been collapsed or expanded by the user is remembered.
The tools search looks identical, collapsed panels follow the tools search mocks:

Workflows
Tools

Before:
Very simple, all panels begin expanded, no state is saved, if you collapsed any panels on page refresh they will be expanded again.
https://user-images.githubusercontent.com/97123241/219798551-ed3d54a0-fb80-4efb-8644-75e4e2d711a9.mp4
After:
Half of the panels begin collapsed, when a user collapses or expands any panels it's state is remembered upon refresh and navigation. I also set the reset button to clear local storage of the panel's state and reset them back to their default (half collapsed) state.
https://user-images.githubusercontent.com/97123241/219798880-0ebbca57-99e7-41c7-9cc2-3cd94925eb5e.mp4
Also created a few spin-off tickets to update some of the search UI: SEAB-5258, SEAB-5257
Review Instructions
Check out the search panels, ensure some are collapsed by default and state is saved.
Issue
DOCK-2317
Security
If there are any concerns that require extra attention from the security team, highlight them here.
Please make sure that you've checked the following before submitting your pull request. Thanks!

[ ] Check that your code compiles by running npm run build
[ ] Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
[ ] If this is the first time you're submitting a PR or even if you just need a refresher, consider reviewing our style guide
[ ] Do not bypass Angular sanitization (bypassSecurityTrustHtml, etc.), or justify why you need to do so
[ ] If displaying markdown, use the markdown-wrapper component, which does extra sanitization
[ ] Do not use cookies, although this may change in the future
[ ] Run npm audit and ensure you are not introducing new vulnerabilities
[ ] Do due diligence on new 3rd party libraries, checking for CVEs
[ ] Don't allow user-uploaded images to be served from the Dockstore domain
[ ] If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.
[ ] Check whether this PR disables tests. If it legitimately needs to disable a test, create a new ticket to re-enable it in a specific milestone.

I didn't trace through the code -- will it handle this gracefully?

Yeah I believe it should, if we look through local storage and see a panel that maps to true then we add the expanded attribute to that panel's html so it begins expanded.  If we add a new panel in the future where there is no mapping to local storage, the expanded attribute won't be added and the panel will just begin closed.

Please do create a ticket for it.

Follow-up ticket: SEAB-5271


Missing SDK package work items for completed release plans (management plane)

Context: https://github.com/Azure/azure-sdk-tools/issues/8796#issuecomment-2313545673

We have a solution for management plane Typespec release plans (not yet implemented).
Need to figure out if we need this information for OpenAPI


Fix CompactProtocol warning

A reference was left in the code to this module, but it doesn't exist (yet).
Fixes #55.

Coverage decreased (-0.7%) to 90.373% when pulling 8a558a6ea922aaea435cce8b55769f76231800b8 on pguillory:compact into 819216f83016c549d9570c6acb44f7ce1e09f51f on pinterest:master.

Coverage decreased (-0.7%) to 90.373% when pulling 8a558a6ea922aaea435cce8b55769f76231800b8 on pguillory:compact into 819216f83016c549d9570c6acb44f7ce1e09f51f on pinterest:master.

Coverage decreased (-0.7%) to 90.373% when pulling 8a558a6ea922aaea435cce8b55769f76231800b8 on pguillory:compact into 819216f83016c549d9570c6acb44f7ce1e09f51f on pinterest:master.


JUnit demonstrating issue https://hibernate.atlassian.net/browse/HHH-5757 with hibernate 5

I commented the issue as well. The code demonstrates that querying a oneToOne association with an entity throws an exception because of a parameter not set.
The problem is deeper than that, actually a oneToOne relationship query :
select this_.id as id1_4_1_, personaddr2_.id as id1_5_0_ from Person this_ left outer join PersonAddress personaddr2_ on this_.id=personaddr2_.id where personaddr2_.id=?
is reduced to :
select this_.id as id1_4_1_, personaddr2_.id as id1_5_0_ from Person this_ left outer join PersonAddress personaddr2_ on this_.id=personaddr2_.id where this_.id=?
I understand that in case of a shared primary key not optional relationship, that makes sense (but complex to develop and bugged here). But the reduction is done systematically (even with a foreign key I am afraid) and it should not be done when optional.

Superseded by this PR which also offers a fix.

Thanks for the Pull Request. Did you sign the CLA? We need it signed so that we can integrate your commit.

Hello. I just signed the CLA. Thanks for your work.


Set kube-apiserver service external traffic policy to local so that a…

…udit events appear with their real source IP

I assume this PR got outdated as there is now the istio-gateway in front of the services, which makes it even harder to reveal client source IPs for the audit logs.
This PR comes with the disadvantage that there is a chance that the API server becomes unavailable when the MetalLB on the worker node that runs the API server instance(s) is rolled / updated / not running properly. (https://metallb.universe.tf/usage/#local-traffic-policy-1)
Maybe there is a solution using forwarding headers, which does not come with this drawback? It could be reasonable to just open an issue regarding this requirement for further discussions and close this PR.

Yes this is now outdated; the problem persists though since the service for the istio gateway has externalTrafficPolicy: Cluster.
There is already an issue: https://github.com/metal-stack/gardener-extension-provider-metal/issues/186. I am closing this PR and we'll discuss how to move forward from here in the issue.


UPSTREAM: : align dockerfile and manifests for bin target

Description

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

/approve


Removal of unnecessary color classes in Protein

Removal of unused color classes
Summary of Changes

Added the new ProteinColor class to handle all coloring issues of all protein plugins
Removed the old Color class from protein & protein_cuda, the UncertaintyColor class, and the old ColorModule
Adapted all Renderers to use the new ProteinColor class

/format

/format

/format


Dropdown menu, hover text color shall be black

The +91 (IN) part should be black. React side is OK.

low priority for R21 Q3

@huayunh what if it is active and hovered?

I guess that can be a possible solution. So hover = background color change, and active = text color change. This can avoid the dilemma discussed in #45.
Although from a designer's perspective, I would always suggest https://github.com/brightlayer-ui/angular-themes/pull/45#issuecomment-984750162 to avoid ambiguity.


Issues regarding to SSE events

There are some issues with SSE events that I like to discuss because I don't know how it can be moved on.

Currently go-marathon is using https://github.com/donovanhide/eventsource as underlying client. However, the client itself has some issues. For example,  https://github.com/donovanhide/eventsource/pull/33. It seems like it might take some time to get it fixed. Rewriting the client will require some changes to go-marathon as well. This will bring to the second topic

When go-marathon is disconnected from the server, it should immediately return to the application side and let the application side refresh the states in Marathon. Simply retrying, which is the current strategy,  will result the application missing the events and eventually out-sync with states in Marathon. In an extreme case, due to network issue, the application can be disconnected from Marathon for long time and when retry finally succeeds, the local state is already largely behind.
So the client also needs to expose an errors channel to the application side.

Another issue is potentially, the order of the events received in each listener can be different from the events received from Marathon. I mentioned the issued in this closed pr: https://github.com/gambol99/go-marathon/pull/270 But at the time, I did not spend too much time on it because our app does not require the order to be correct but it's no longer the case.

But before fix issue 3 I really wish issue 1 and 2 can be solved because currently I am using a non-elegant fix in my private fork. What are your guys' opinions on the issues?

Hey @iandyh, thanks for your questions. Here are my thougths:

I can see two options here: a) Invest into the eventsource library to fix the issues that we need to get fixed; or b) try to find another library. I can't tell which of the two options might be better; from my experience though, getting feature requests and bug fixes into eventsource has never been a problem from a collaborative perspective. So when I'm doubt, I'm inclined to stick with eventsource and drive any changes we need upstream.
Agreed that we need a way to expose the "event stream was broken" signal to the caller, and returning the error would be the most straight-forward way. I was shortly wondering if we could accept a callback function that'd be called every time the stream fails, so clients get a hook to catch up on missing events on their own while go-marathon continues to do retries under the hood. This will likely be more complex to implement, however, and I'm not sure if the benefit would truly out-weight the costs. Either way, the existing approach of doing retries transparently should continue to be possible as certain clients are fine with missing events.
Definitely another issue we should tackle.

Feel free to work on any of the challenges you mentioned and submit PRs once you think we've reached a reasonable design.

Hi @timoreimann, Thanks for the response.
Speaking 1 and 2, I'll still argue having timeout is the easiest way to solve the problem. The implementation will also be much easier from go-marathon point of view. A likely solution will be like
if time.After(10 * time.Second) {
    stream.Close()
}
// Return error to application side

Regarding to issue 3, somehow I cannot reproduce the issue anymore. But I found a relevant discussion on stackoverflow: https://stackoverflow.com/questions/25860633/order-of-goroutine-unblocking-on-single-channel
The most straightforward way to solve would be replacing goroutings with blocking calls. So if one listener is blocked, the rest of listeners are also blocked:
if event.ID&context.filter != 0 {
        context.completion.Add(1)
        defer context.completion.Done()
	select {
		case ch <- event:
		case <-context.done:
			// Terminates goroutine.
	}
}

I've been thinking about this for a while, this seems to be the only solution I can come up with.

hey @iandyh

Speaking 1 and 2, I'll still argue having timeout is the easiest way to solve the problem.

Hm, not sure if I can follow you: 1. seems to be about the eventsource library in general, and 2. about exposing stream errors from the library. Are you suggesting to generate an error artifically after some static time interval?
Re: 3: How about using a channel buffer with a configurable size (so that the impact of slow consumers is limited)?
A further extension could be to use a ring buffer with either a LIFO or FIFO strategy so that senders never block. Existing libraries are available.

Are you suggesting to generate an error artifically after some static time interval?

Yes, and during the interval, the event source library should do the retry. Moreover, I also think go-marathon should set a configurable timeout here and simply close the connection after timeout and return errors to the application. The application needs to refresh Marathon state and re-initiate the SSE connection.
Regarding to issue 3. Not sure about it. Probably it's overkilled? Because it would be probably easier to have its own SSE connection for each consumer.

Are you suggesting to generate an error artifically after some static time interval?

Yes, and during the interval, the event source library should do the retry. Moreover, I also think go-marathon should set a configurable timeout here and simply close the connection after timeout and return errors to the application. The application needs to refresh Marathon state and re-initiate the SSE connection.

In general, I'd prefer to strive for a deterministic solution where errors are generated and exposed exactly when an issue has knowingly been detected. Relying on timeouts feels like a workaround that may exacerbate attaining properties like correctness and performance on the user's end. But maybe I'm still missing a point here?
As far as eventsource is concerned, the maintainer has expressed willingness to continue accepting PRs. As mentioned, I'm also open to consider other libraries if they happen to provide the features we are looking for.
There's still a chance I might be misunderstanding. Let me know in this case, either by further discussion or a small PoC PR.


Decide on case style in babe-project

At the moment, we have many different styles in the names of the different repositories in babe-project:

snake case: babe_site
kebab case: babe-project
upper camel case: MinimalTemplate ColorReference
lower camel case: departurePoint
all caps: BABE

In the front-end code itself, there are also different styles present: e.g. deployMethod and contact_email in the call of babeInit.
In the downloaded csv data from the server app, there are also different styles present: e.g. submission_id and startTime.
I know it is difficult to find a coherent solution, because there are different predominating styles in the different programming communities. (javascript/node, elixir, R, Python)
But I think, we should try to stick to one style in the complete project or to stick to the predominating style of the respective language.
I suggest to use snake case notation in the complete project, because, as far as I know, it is the preferred style in elixir and R, it is already used predominately in this project and I personally find it better readable.

I agree.

On Dec 5, 2018, at 12:03, JannisBush<EMAIL_ADDRESS>wrote:
At the moment, we have many different styles in the names of the different repositories in babe-project:
snake case: babe_site
kebab case: babe-project
upper camel case: MinimalTemplate ColorReference
lower camel case: departurePoint
all caps: BABE
In the front-end code itself, there are also different styles present: e.g. deployMethod and contact_email in the call of babeInit.
In the downloaded csv data from the server app, there are also different styles present: e.g. submission_id and startTime.
I know it is difficult to find a coherent solution, because there are different predominating styles in the different programming communities. (javascript/node, elixir, R, Python)
But I think, we should try to stick to one style in the complete project or to stick to the predominating style of the respective language.
I suggest to use snake case notation in the complete project, because, as far as I know, it is the preferred style in elixir and R, it is already used predominately in this project and I personally find it better readable.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

This might be useful: https://www.npmjs.com/package/eslint-plugin-eslint-snake-case
The key names for downloaded data come from the frontend submission. Those names can also be changed in the frontend templates.
The naming of BABE is that we couldn't find a distinct name for the backend app... So I just went with that. Any suggestion?


Encoder 48300180.eqep return onlu -1 or 1 or 0

Describe the bug
The encoder EQEP0 return only three values -1, 0, 1.
**Describe which image you are running (example: bone-debian-10.2-iot-armhf-2020-02-03-4gb.img.xz) **
bone-ubuntu-18.04.4-ros-iot-armhf-2020-05-18-6gb.img
System is booted from SDCARD
Describe your hardware
BeagleBone Blue
Describe any Capes Installed
Please run this built-in script
sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[029041f6866049997bbfd2c7667b3c6e8c95201c]
eeprom:[A335BNLTBLA21712EL002910]
model:[TI_AM335x_BeagleBone_Blue]
dogtag:[BeagleBoard.org ROS Image 2020-05-18]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2019.04-00002-g31a8ae0206]:[location: dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblue.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
UBOOT: Loaded Overlay:[BB-ADC-00A0]
kernel:[4.19.94-ti-rt-r43]
nodejs:[v8.10.0]
/boot/uEnv.txt Settings:
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.14.20200814.0-0~bionic+20200814]
pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~bionic+20200813]
pkg:[kmod]:[24-1ubuntu3.5rcnee0~bionic+20200810]
pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~bionic+20200716]
groups:[beagle : beagle root adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input bluetooth netdev i2c cloud9ide gpio pwm eqep remoteproc admin spi iio docker tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet]
dmesg | grep remote
[   42.330772] remoteproc remoteproc0: 4a334000.pru is available
[   42.346759] remoteproc remoteproc1: 4a338000.pru is available
[  154.575230] remoteproc remoteproc2: wkup_m3 is available
[  154.592590] remoteproc remoteproc2: powering up wkup_m3
[  154.592613] remoteproc remoteproc2: Booting fw image am335x-pm-firmware.elf, size 217168
[  154.592894] remoteproc remoteproc2: remote processor wkup_m3 is now up
[  282.595682] remoteproc remoteproc0: powering up 4a334000.pru
[  282.604229] remoteproc remoteproc0: Booting fw image am335x-pru0-rc-encoder-fw, size 36040
[  282.604275] remoteproc remoteproc0: remote processor 4a334000.pru is now up
[  853.519686] remoteproc remoteproc0: stopped remote processor 4a334000.pru
dmesg | grep pru
[   42.330772] remoteproc remoteproc0: 4a334000.pru is available
[   42.330953] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[   42.346759] remoteproc remoteproc1: 4a338000.pru is available
[   42.346958] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
[  282.595682] remoteproc remoteproc0: powering up 4a334000.pru
[  282.604229] remoteproc remoteproc0: Booting fw image am335x-pru0-rc-encoder-fw, size 36040
[  282.604275] remoteproc remoteproc0: remote processor 4a334000.pru is now up
[  853.519686] remoteproc remoteproc0: stopped remote processor 4a334000.pru
dmesg | grep pinctrl-single
[    1.065640] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    1.289110] pinctrl-single 44e10800.pinmux: pin PIN102 already requested by 48300180.eqep; cannot claim for ocp:P9_30_pinmux
[    1.305932] pinctrl-single 44e10800.pinmux: pin-102 (ocp:P9_30_pinmux) status -22
[    1.313470] pinctrl-single 44e10800.pinmux: could not request pin 102 (PIN102) from group pinmux_P9_30_spi_pin  on device pinctrl-single
dmesg | grep gpio-of-helper
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END
To Reproduce
Steps to reproduce the behavior:

Connect quadrant encoder to eqep0
Run rc_test_encoders
or
watch -n 0.1 cat /sys/devices/platform/ocp/48300000.epwmss/48300180.eqep/position
Rotate shaft of encoder whith is connected to EQEP0 and see error, returned value is -1 or 0 or 1
Other encoders are working properly.

Expected behavior
The encoder EQEP0 should work like other encoders and return valid values.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Same issue with bone-debian-10.5-iot-armhf-2020-08-25-4gb.img.xz
Please let me know if there is anything I can provide to debug this issue further.

Really odd. Any chance you can put a scope on the 2 qep lines?

Oh, also, is there anything in the output of 'dmesg' about the qep?

debian@beaglebone:~$ dmesg | grep qep
[    1.108918] eqep 48300180.eqep: ver. 1.0
[    1.109175] eqep 48300180.eqep: count_mode:0
[    1.109186] eqep 48300180.eqep: invert_qa:1
[    1.109195] eqep 48300180.eqep: invert_qb:1
[    1.109203] eqep 48300180.eqep: invert_qi:0
[    1.109211] eqep 48300180.eqep: invert_qs:0
[    1.109220] eqep 48300180.eqep: swap_inputs:0
[    1.109228] eqep 48300180.eqep: QDECCTL:0x0180
[    1.109237] eqep 48300180.eqep: QPOSINIT:0x00000000
[    1.109244] eqep 48300180.eqep: QPOSMAX:0xffffffff
[    1.109251] eqep 48300180.eqep: QPOSCNT:0x00000000
[    1.109259] eqep 48300180.eqep: omit_interrupt:0
[    1.109267] eqep 48300180.eqep: QEINT:0x0800
[    1.109274] eqep 48300180.eqep: QUPRD:0x05f5e100
[    1.109281] eqep 48300180.eqep: QEPCTL:0x009e write
[    1.109289] eqep 48300180.eqep: QEPCTL:0x009e read
[    1.109316] eqep 48300180.eqep: irq:60, clk_rate:100000000
[    1.109864] eqep 48302180.eqep: ver. 1.0
[    1.110005] eqep 48302180.eqep: count_mode:0
[    1.110016] eqep 48302180.eqep: invert_qa:1
[    1.110024] eqep 48302180.eqep: invert_qb:1
[    1.110033] eqep 48302180.eqep: invert_qi:0
[    1.110041] eqep 48302180.eqep: invert_qs:0
[    1.110048] eqep 48302180.eqep: swap_inputs:0
[    1.110056] eqep 48302180.eqep: QDECCTL:0x0180
[    1.110064] eqep 48302180.eqep: QPOSINIT:0x00000000
[    1.110071] eqep 48302180.eqep: QPOSMAX:0xffffffff
[    1.110078] eqep 48302180.eqep: QPOSCNT:0x00000000
[    1.110087] eqep 48302180.eqep: omit_interrupt:0
[    1.110094] eqep 48302180.eqep: QEINT:0x0800
[    1.110102] eqep 48302180.eqep: QUPRD:0x05f5e100
[    1.110109] eqep 48302180.eqep: QEPCTL:0x009e write
[    1.110116] eqep 48302180.eqep: QEPCTL:0x009e read
[    1.110212] eqep 48302180.eqep: irq:62, clk_rate:100000000
[    1.110466] eqep 48304180.eqep: ver. 1.0
[    1.110662] eqep 48304180.eqep: count_mode:0
[    1.110671] eqep 48304180.eqep: invert_qa:1
[    1.110679] eqep 48304180.eqep: invert_qb:1
[    1.110687] eqep 48304180.eqep: invert_qi:0
[    1.110695] eqep 48304180.eqep: invert_qs:0
[    1.110703] eqep 48304180.eqep: swap_inputs:0
[    1.110710] eqep 48304180.eqep: QDECCTL:0x0180
[    1.110718] eqep 48304180.eqep: QPOSINIT:0x00000000
[    1.110726] eqep 48304180.eqep: QPOSMAX:0xffffffff
[    1.110733] eqep 48304180.eqep: QPOSCNT:0x00000000
[    1.110741] eqep 48304180.eqep: omit_interrupt:0
[    1.110748] eqep 48304180.eqep: QEINT:0x0800
[    1.110755] eqep 48304180.eqep: QUPRD:0x05f5e100
[    1.110762] eqep 48304180.eqep: QEPCTL:0x009e write
[    1.110769] eqep 48304180.eqep: QEPCTL:0x009e read
[    1.110787] eqep 48304180.eqep: irq:64, clk_rate:100000000
[    1.114175] pinctrl-single 44e10800.pinmux: pin PIN102 already requested by 48300180.eqep; cannot claim for ocp:P9_30_pinmux
or whole dmesg:
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.19.94-ti-r42 (voodoo@x3-am57xx-beagle-x15-2gb) (gcc version 8.3.0 (Debian 8.3.0-6)) #1buster SMP PREEMPT Tue Mar 31 19:38:29 UTC 2020
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: TI AM335x BeagleBone Blue
[    0.000000] Memory policy: Data cache writeback
[    0.000000] cma: Reserved 48 MiB at 0x9c800000
[    0.000000] On node 0 totalpages: 130560
[    0.000000]   Normal zone: 1148 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 130560 pages, LIFO batch:31
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (sgx neon)
[    0.000000] random: get_random_bytes called from start_kernel+0xac/0x4b4 with crng_init=0
[    0.000000] percpu: Embedded 17 pages/cpu s38988 r8192 d22452 u69632
[    0.000000] pcpu-alloc: s38988 r8192 d22452 u69632 alloc=17*4096
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 129412
[    0.000000] Kernel command line: console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100 quiet
[    0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Memory: 438116K/522240K available (13312K kernel code, 1136K rwdata, 4308K rodata, 1024K init, 350K bss, 34972K reserved, 49152K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
vector  : 0xffff0000 - 0xffff1000   (   4 kB)
fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
vmalloc : 0xe0000000 - 0xff800000   ( 504 MB)
lowmem  : 0xc0000000 - 0xdfe00000   ( 510 MB)
pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
modules : 0xbf000000 - 0xbfe00000   (  14 MB)
.text : 0x(ptrval) - 0x(ptrval)   (14304 kB)
.init : 0x(ptrval) - 0x(ptrval)   (1024 kB)
.data : 0x(ptrval) - 0x(ptrval)   (1137 kB)
.bss : 0x(ptrval) - 0x(ptrval)   ( 351 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] ftrace: allocating 42043 entries in 124 pages
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] rcu: 	RCU restricting CPUs from NR_CPUS=2 to nr_cpu_ids=1.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] IRQ: Found an INTC at 0x(ptrval) (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000022] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every<PHONE_NUMBER>1ns
[    0.000042] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>9 ns
[    0.000052] OMAP clocksource: timer1 at 24000000 Hz
[    0.001622] timer_probe: no matching timers found
[    0.001965] Console: colour dummy device 80x30
[    0.001995] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[    0.002000] This ensures that you still see kernel messages. Please
[    0.002004] update your kernel commandline.
[    0.002064] Calibrating delay loop (skipped) preset value.. 995.32 BogoMIPS (lpj=1990656)
[    0.002081] pid_max: default: 32768 minimum: 301
[    0.002368] Security Framework initialized
[    0.002383] Yama: becoming mindful.
[    0.002530] AppArmor: AppArmor initialized
[    0.002634] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.002647] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.003752] CPU: Testing write buffer coherency: ok
[    0.003815] CPU0: Spectre v2: using BPIALL workaround
[    0.004310] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[    0.025578] Setting up static identity map for 0x80100000 - 0x80100060
[    0.033480] rcu: Hierarchical SRCU implementation.
[    0.049492] smp: Bringing up secondary CPUs ...
[    0.049510] smp: Brought up 1 node, 1 CPU
[    0.049522] SMP: Total of 1 processors activated (995.32 BogoMIPS).
[    0.049528] CPU: All CPU(s) started in SVC mode.
[    0.051243] devtmpfs: initialized
[    0.077875] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.078528] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns:<PHONE_NUMBER>100000 ns
[    0.078552] futex hash table entries: 256 (order: 2, 16384 bytes)
[    0.082488] xor: automatically using best checksumming function   neon
[    0.082506] pinctrl core: initialized pinctrl subsystem
[    0.083813] NET: Registered protocol family 16
[    0.089052] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[    0.167857] l4_wkup_cm:clk:0010:0: failed to disable
[    0.208112] audit: initializing netlink subsys (disabled)
[    0.213582] audit: type=2000 audit(0.200:1): state=initialized audit_enabled=0 res=1
[    0.216949] OMAP GPIO hardware version 0.1
[    0.220065] GPIO line 106 (LS_BUF_EN) hogged as output/high
[    0.236043] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.261642] raid6: using algorithm neonx8 gen() 0 MB/s
[    0.261655] raid6: .... xor() 0 MB/s, rmw enabled
[    0.261662] raid6: using neon recovery algorithm
[    0.269243] edma 49000000.edma: TI EDMA DMA engine driver
[    0.275343] SCSI subsystem initialized
[    0.277623] libata version 3.00 loaded.
[    0.277937] usbcore: registered new interface driver usbfs
[    0.277994] usbcore: registered new interface driver hub
[    0.278115] usbcore: registered new device driver usb
[    0.279321] pps_core: LinuxPPS API ver. 1 registered
[    0.279330] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti<EMAIL_ADDRESS>[    0.279352] PTP clock support registered
[    0.280255] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.281902] Advanced Linux Sound Architecture Driver Initialized.
[    0.282710] NetLabel: Initializing
[    0.282719] NetLabel:  domain hash size = 128
[    0.282724] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.282821] NetLabel:  unlabeled traffic allowed by default
[    0.283879] clocksource: Switched to clocksource timer1
[    0.446316] VFS: Disk quotas dquot_6.6.0
[    0.446420] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.447287] AppArmor: AppArmor Filesystem Enabled
[    0.460102] NET: Registered protocol family 2
[    0.461125] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[    0.461164] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[    0.461206] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    0.461263] TCP: Hash tables configured (established 4096 bind 4096)
[    0.461396] UDP hash table entries: 256 (order: 1, 8192 bytes)
[    0.461419] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[    0.461767] NET: Registered protocol family 1
[    0.474966] RPC: Registered named UNIX socket transport module.
[    0.474978] RPC: Registered udp transport module.
[    0.474983] RPC: Registered tcp transport module.
[    0.474988] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.475700] Unpacking initramfs...
[    0.871598] Freeing initrd memory: 6884K
[    0.872607] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.875441] Initialise system trusted keyrings
[    0.876038] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[    0.883116] zbud: loaded
[    0.890609] NFS: Registering the id_resolver key type
[    0.890653] Key type id_resolver registered
[    0.890659] Key type id_legacy registered
[    0.890677] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.891042] fuse init (API version 7.27)
[    0.901580] Key type asymmetric registered
[    0.901594] Asymmetric key parser 'x509' registered
[    0.901694] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    0.906064] io scheduler noop registered
[    0.906075] io scheduler deadline registered
[    0.906389] io scheduler cfq registered (default)
[    0.906399] io scheduler mq-deadline registered
[    0.909594] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    0.921948] Serial: 8250/16550 driver, 6 ports, IRQ sharing disabled
[    0.925618] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, base_baud = 3000000) is a 8250
[    0.935727] console [ttyS0] enabled
[    0.936914] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 31, base_baud = 3000000) is a 8250
[    0.937856] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 32, base_baud = 3000000) is a 8250
[    0.938883] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 33, base_baud = 3000000) is a 8250
[    0.939807] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 34, base_baud = 3000000) is a 8250
[    0.941049] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 35, base_baud = 3000000) is a 8250
[    0.944309] omap_rng 48310000.rng: Random Number Generator ver. 20
[    0.945095] sdhci: Secure Digital Host Controller Interface driver
[    0.945103] sdhci: Copyright(c) Pierre Ossman
[    0.945633] omap_gpio 44e07000.gpio: Could not set line 6 debounce to 200000 microseconds (-22)
[    0.945644] omap_hsmmc 48060000.mmc: Got CD GPIO
[    0.946198] omap_hsmmc 48060000.mmc: Linked as a consumer to regulator.1
[    0.946550] random: fast init done
[    0.946917] random: crng init done
[    0.973255] omap_hsmmc 481d8000.mmc: Linked as a consumer to regulator.1
[    0.998579] omap_hsmmc 47810000.mmc: Linked as a consumer to regulator.2
[    1.006519] mmc0: host does not support reading read-only switch, assuming write-enable
[    1.008708] mmc0: new high speed SDHC card at address 0007
[    1.014060] mmcblk0: mmc0:0007 SD08G 7.42 GiB
[    1.020738]  mmcblk0: p1
[    1.047784] mmc1: new high speed MMC card at address 0001
[    1.053205] mmcblk1: mmc1:0001 S10004 3.56 GiB
[    1.053836] mmcblk1boot0: mmc1:0001 S10004 partition 1 4.00 MiB
[    1.054434] mmcblk1boot1: mmc1:0001 S10004 partition 2 4.00 MiB
[    1.054792] mmcblk1rpmb: mmc1:0001 S10004 partition 3 4.00 MiB, chardev (245:0)
[    1.056163]  mmcblk1: p1
[    1.100401] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.108918] eqep 48300180.eqep: ver. 1.0
[    1.109175] eqep 48300180.eqep: count_mode:0
[    1.109186] eqep 48300180.eqep: invert_qa:1
[    1.109195] eqep 48300180.eqep: invert_qb:1
[    1.109203] eqep 48300180.eqep: invert_qi:0
[    1.109211] eqep 48300180.eqep: invert_qs:0
[    1.109220] eqep 48300180.eqep: swap_inputs:0
[    1.109228] eqep 48300180.eqep: QDECCTL:0x0180
[    1.109237] eqep 48300180.eqep: QPOSINIT:0x00000000
[    1.109244] eqep 48300180.eqep: QPOSMAX:0xffffffff
[    1.109251] eqep 48300180.eqep: QPOSCNT:0x00000000
[    1.109259] eqep 48300180.eqep: omit_interrupt:0
[    1.109267] eqep 48300180.eqep: QEINT:0x0800
[    1.109274] eqep 48300180.eqep: QUPRD:0x05f5e100
[    1.109281] eqep 48300180.eqep: QEPCTL:0x009e write
[    1.109289] eqep 48300180.eqep: QEPCTL:0x009e read
[    1.109316] eqep 48300180.eqep: irq:60, clk_rate:100000000
[    1.109864] eqep 48302180.eqep: ver. 1.0
[    1.110005] eqep 48302180.eqep: count_mode:0
[    1.110016] eqep 48302180.eqep: invert_qa:1
[    1.110024] eqep 48302180.eqep: invert_qb:1
[    1.110033] eqep 48302180.eqep: invert_qi:0
[    1.110041] eqep 48302180.eqep: invert_qs:0
[    1.110048] eqep 48302180.eqep: swap_inputs:0
[    1.110056] eqep 48302180.eqep: QDECCTL:0x0180
[    1.110064] eqep 48302180.eqep: QPOSINIT:0x00000000
[    1.110071] eqep 48302180.eqep: QPOSMAX:0xffffffff
[    1.110078] eqep 48302180.eqep: QPOSCNT:0x00000000
[    1.110087] eqep 48302180.eqep: omit_interrupt:0
[    1.110094] eqep 48302180.eqep: QEINT:0x0800
[    1.110102] eqep 48302180.eqep: QUPRD:0x05f5e100
[    1.110109] eqep 48302180.eqep: QEPCTL:0x009e write
[    1.110116] eqep 48302180.eqep: QEPCTL:0x009e read
[    1.110172] omap_hsmmc 47810000.mmc: card claims to support voltages below defined range
[    1.110212] eqep 48302180.eqep: irq:62, clk_rate:100000000
[    1.110466] eqep 48304180.eqep: ver. 1.0
[    1.110662] eqep 48304180.eqep: count_mode:0
[    1.110671] eqep 48304180.eqep: invert_qa:1
[    1.110679] eqep 48304180.eqep: invert_qb:1
[    1.110687] eqep 48304180.eqep: invert_qi:0
[    1.110695] eqep 48304180.eqep: invert_qs:0
[    1.110703] eqep 48304180.eqep: swap_inputs:0
[    1.110710] eqep 48304180.eqep: QDECCTL:0x0180
[    1.110718] eqep 48304180.eqep: QPOSINIT:0x00000000
[    1.110726] eqep 48304180.eqep: QPOSMAX:0xffffffff
[    1.110733] eqep 48304180.eqep: QPOSCNT:0x00000000
[    1.110741] eqep 48304180.eqep: omit_interrupt:0
[    1.110748] eqep 48304180.eqep: QEINT:0x0800
[    1.110755] eqep 48304180.eqep: QUPRD:0x05f5e100
[    1.110762] eqep 48304180.eqep: QEPCTL:0x009e write
[    1.110769] eqep 48304180.eqep: QEPCTL:0x009e read
[    1.110787] eqep 48304180.eqep: irq:64, clk_rate:100000000
[    1.114175] pinctrl-single 44e10800.pinmux: pin PIN102 already requested by 48300180.eqep; cannot claim for ocp:P9_30_pinmux
[    1.125652] pinctrl-single 44e10800.pinmux: pin-102 (ocp:P9_30_pinmux) status -22
[    1.133263] pinctrl-single 44e10800.pinmux: could not request pin 102 (PIN102) from group pinmux_P9_30_spi_pin  on device pinctrl-single
[    1.145637] bone-pinmux-helper ocp:P9_30_pinmux: Error applying setting, reverse things back
[    1.154236] bone-pinmux-helper: probe of ocp:P9_30_pinmux failed with error -22
[    1.162661] mmc2: new high speed SDIO card at address 0001
[    1.171680] libphy: Fixed MDIO Bus: probed
[    1.172797] CAN device driver interface
[    1.174332] c_can_platform 481d0000.can: c_can_platform device registered (regs=735cec01, irq=43)
[    1.176090] usbcore: registered new interface driver smsc95xx
[    1.177439] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.177502] ehci-platform: EHCI generic platform driver
[    1.177799] ehci-omap: OMAP-EHCI Host Controller driver
[    1.178598] usbcore: registered new interface driver usb-storage
[    1.181916] am335x-phy-driver 47401300.usb-phy: 47401300.usb-phy supply vcc not found, using dummy regulator
[    1.182114] am335x-phy-driver 47401300.usb-phy: Linked as a consumer to regulator.0
[    1.185489] am335x-phy-driver 47401b00.usb-phy: 47401b00.usb-phy supply vcc not found, using dummy regulator
[    1.185649] am335x-phy-driver 47401b00.usb-phy: Linked as a consumer to regulator.0
[    1.189123] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[    1.189177] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 1
[    1.189525] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    1.189536] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    1.189543] usb usb1: Product: MUSB HDRC host driver
[    1.189550] usb usb1: Manufacturer: Linux 4.19.94-ti-r42 musb-hcd
[    1.189558] usb usb1: SerialNumber: musb-hdrc.1
[    1.190432] hub 1-0:1.0: USB hub found
[    1.190494] hub 1-0:1.0: 1 port detected
[    1.202340] omap_rtc 44e3e000.rtc: registered as rtc0
[    1.203663] i2c /dev entries driver
[    1.206932] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.207472] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)
[    1.212495] ledtrig-cpu: registered to indicate activity on CPUs
[    1.213039] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[    1.213377] omap-aes 53500000.aes: will run requests pump with realtime priority
[    1.215805] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[    1.219489] hidraw: raw HID events driver (C) Jiri Kosina
[    1.226560] gnss: GNSS driver registered with major 242
[    1.233177] NET: Registered protocol family 10
[    1.304568] Segment Routing with IPv6
[    1.304704] mip6: Mobile IPv6
[    1.304861] NET: Registered protocol family 17
[    1.304890] can: controller area network core (rev 20170425 abi 9)
[    1.304996] NET: Registered protocol family 29
[    1.305080] 8021q: 802.1Q VLAN Support v1.8
[    1.305163] Key type dns_resolver registered
[    1.305170] mpls_gso: MPLS GSO support
[    1.305478] ThumbEE CPU extension supported.
[    1.305494] Registering SWP/SWPB emulation handler
[    1.305505] omap_voltage_late_init: Voltage driver support not added
[    1.313722] registered taskstats version 1
[    1.313732] Loading compiled-in X.509 certificates
[    1.313870] zswap: loaded using pool lzo/zbud
[    1.317282] Btrfs loaded, crc32c=crc32c-generic
[    1.317396] AppArmor: AppArmor sha1 policy hashing enabled
[    1.373485] tps6521x_pwrbutton tps65217-pwrbutton: DMA mask not set
[    1.374306] input: tps65217_pwr_but as /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
[    1.375274] tps65217 0-0024: TPS65217 ID 0xe version 1.2
[    1.376285] at24 0-0050: 32768 byte 24c256 EEPROM, writable, 1 bytes/write
[    1.376398] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    1.378222] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
[    1.380059] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
[    1.384691] cpu cpu0: Linked as a consumer to regulator.4
[    1.384801] cpu cpu0: Dropping the link to regulator.4
[    1.385291] cpu cpu0: Linked as a consumer to regulator.4
[    1.387377] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    1.388847] ALSA device list:
[    1.388858]   No soundcards found.
[    1.395085] Freeing unused kernel memory: 1024K
[    1.395808] Run /init as init process
[    7.060677] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
[    7.947384] systemd[1]: System time before build time, advancing clock.
[    8.006570] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[    8.007306] systemd[1]: Detected architecture arm.
[    8.035523] systemd[1]: Set hostname to .
[    9.426902] systemd[1]: /lib/systemd/system/rc_battery_monitor.service:5: PIDFile= references path below legacy directory /var/run/, updating /var/run/rc_battery_monitor.pid → /run/rc_battery_monitor.pid; please update the unit file accordingly.
[    9.564686] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[    9.566859] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[    9.567542] systemd[1]: Listening on initctl Compatibility Named Pipe.
[    9.569282] systemd[1]: Listening on Journal Audit Socket.
[    9.569513] systemd[1]: Reached target Remote File Systems.
[    9.570562] systemd[1]: Listening on udev Control Socket.
[   10.426994] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro
[   10.629897] remoteproc remoteproc0: 4a334000.pru is available
[   10.630089] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 probed successfully
[   10.631750] remoteproc remoteproc1: 4a338000.pru is available
[   10.648182] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 probed successfully
[   11.720972] systemd-journald[469]: Received request to flush runtime journal from PID 1
[   23.393310] using random self ethernet address
[   23.393329] using random host ethernet address
[   23.783734] Mass Storage Function, version: 2009/09/11
[   23.783758] LUN: removable file: (no medium)
[   24.111676] using random self ethernet address
[   24.111694] using random host ethernet address
[   24.334833] usb0: HOST MAC f4:5e:ab:f6:b1:c9
[   24.338427] usb0: MAC f4:5e:ab:f6:b1:c8
[   24.344369] usb1: HOST MAC f4:5e:ab:f6:b1:cb
[   24.347323] usb1: MAC f4:5e:ab:f6:b1:cc
[   24.585165] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   24.841963] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
[   31.720136] wlan-en-regulator: disabling
[   46.453438] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[   46.777073] remoteproc remoteproc2: wkup_m3 is available
[   46.791836] remoteproc remoteproc2: powering up wkup_m3
[   46.792047] remoteproc remoteproc2: Booting fw image am335x-pm-firmware.elf, size 217168
[   46.792313] remoteproc remoteproc2: remote processor wkup_m3 is now up
[   46.792335] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x193
[   46.890847] PM: bootloader does not support rtc-only!
[   51.481167] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   51.502778] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   51.506660] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[   51.506690] cfg80211: failed to load regulatory.db
[   51.926718] Bluetooth: Core ver 2.22
[   51.926905] NET: Registered protocol family 31
[   51.926913] Bluetooth: HCI device and connection manager initialized
[   51.926942] Bluetooth: HCI socket layer initialized
[   51.926956] Bluetooth: L2CAP socket layer initialized
[   51.927021] Bluetooth: SCO socket layer initialized
[   51.992387] Bluetooth: HCI UART driver ver 2.3
[   51.992406] Bluetooth: HCI UART protocol H4 registered
[   52.000273] Bluetooth: HCI UART protocol LL registered
[   52.000289] Bluetooth: HCI UART protocol ATH3K registered
[   52.000485] Bluetooth: HCI UART protocol Three-wire (H5) registered
[   52.982720] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   52.982736] Bluetooth: BNEP filters: protocol multicast
[   52.982765] Bluetooth: BNEP socket layer initialized
[   54.025189] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[   54.077121] wlcore: loaded
[   54.516177] Bluetooth: RFCOMM TTY layer initialized
[   54.516221] Bluetooth: RFCOMM socket layer initialized
[   54.516285] Bluetooth: RFCOMM ver 1.11
[   54.688299] wlcore: PHY firmware version: Rev <IP_ADDRESS>.242
[   54.729301] wlcore: firmware booted (Rev <IP_ADDRESS>.79)
[   54.774380] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   56.123689] wlan0: authenticate with f0:99:bf:0c:c4:c0
[   56.136830] wlan0: send auth to f0:99:bf:0c:c4:c0 (try 1/3)
[   56.268098] wlan0: send auth to f0:99:bf:0c:c4:c0 (try 2/3)
[   56.287697] wlan0: authenticated
[   56.296123] wlan0: associate with f0:99:bf:0c:c4:c0 (try 1/3)
[   56.300877] wlan0: RX AssocResp from f0:99:bf:0c:c4:c0 (capab=0x1411 status=0 aid=2)
[   56.314607] wlan0: associated
[   56.569781] cryptd: max_cpu_qlen set to 1000
[   57.592775] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by f0:99:bf:0c:c4:c0
[   57.619078] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[   57.649765] wlcore: Association completed.
[   57.824232] IPv6: ADDRCONF(NETDEV_UP): SoftAp0: link is not ready
[   59.846359] wlcore: down
[   59.963169] IPv6: ADDRCONF(NETDEV_CHANGE): SoftAp0: link becomes ready
[  361.046294] remoteproc remoteproc0: powering up 4a334000.pru
[  361.063572] remoteproc remoteproc0: Booting fw image am335x-pru0-rc-encoder-fw, size 36040
[  361.063616] remoteproc remoteproc0: remote processor 4a334000.pru is now up
[  426.526981] remoteproc remoteproc0: stopped remote processor 4a334000.pru

Attached is qep signals. Looks good.
This issue is related to SW, it worked just fine with the pre-installed image from factory. I believe it was 4.4 kernel (I forgot to check this before upgrading to the latest image).

root@beaglebone:/home/debian# dmesg | grep qep
[    1.088854] eqep 48300180.eqep: ver. 1.0
[    1.089102] eqep 48300180.eqep: count_mode:0
[    1.089113] eqep 48300180.eqep: invert_qa:1
[    1.089122] eqep 48300180.eqep: invert_qb:1
[    1.089131] eqep 48300180.eqep: invert_qi:0
[    1.089139] eqep 48300180.eqep: invert_qs:0
[    1.089148] eqep 48300180.eqep: swap_inputs:0
[    1.089157] eqep 48300180.eqep: QDECCTL:0x0180
[    1.089165] eqep 48300180.eqep: QPOSINIT:0x00000000
[    1.089173] eqep 48300180.eqep: QPOSMAX:0xffffffff
[    1.089180] eqep 48300180.eqep: QPOSCNT:0x00000000
[    1.089189] eqep 48300180.eqep: omit_interrupt:0
[    1.089196] eqep 48300180.eqep: QEINT:0x0800
[    1.089204] eqep 48300180.eqep: QUPRD:0x05f5e100
[    1.089211] eqep 48300180.eqep: QEPCTL:0x009e write
[    1.089219] eqep 48300180.eqep: QEPCTL:0x009e read
[    1.089247] eqep 48300180.eqep: irq:60, clk_rate:100000000
[    1.089820] eqep 48302180.eqep: ver. 1.0
[    1.089972] eqep 48302180.eqep: count_mode:0
[    1.089982] eqep 48302180.eqep: invert_qa:1
[    1.089991] eqep 48302180.eqep: invert_qb:1
[    1.089999] eqep 48302180.eqep: invert_qi:0
[    1.090007] eqep 48302180.eqep: invert_qs:0
[    1.090015] eqep 48302180.eqep: swap_inputs:0
[    1.090023] eqep 48302180.eqep: QDECCTL:0x0180
[    1.090031] eqep 48302180.eqep: QPOSINIT:0x00000000
[    1.090038] eqep 48302180.eqep: QPOSMAX:0xffffffff
[    1.090045] eqep 48302180.eqep: QPOSCNT:0x00000000
[    1.090053] eqep 48302180.eqep: omit_interrupt:0
[    1.090060] eqep 48302180.eqep: QEINT:0x0800
[    1.090067] eqep 48302180.eqep: QUPRD:0x05f5e100
[    1.090149] eqep 48302180.eqep: QEPCTL:0x009e write
[    1.090157] eqep 48302180.eqep: QEPCTL:0x009e read
[    1.090179] eqep 48302180.eqep: irq:62, clk_rate:100000000
[    1.090525] eqep 48304180.eqep: ver. 1.0
[    1.090653] eqep 48304180.eqep: count_mode:0
[    1.090663] eqep 48304180.eqep: invert_qa:1
[    1.090671] eqep 48304180.eqep: invert_qb:1
[    1.090679] eqep 48304180.eqep: invert_qi:0
[    1.090687] eqep 48304180.eqep: invert_qs:0
[    1.090696] eqep 48304180.eqep: swap_inputs:0
[    1.090704] eqep 48304180.eqep: QDECCTL:0x0180
[    1.090712] eqep 48304180.eqep: QPOSINIT:0x00000000
[    1.090720] eqep 48304180.eqep: QPOSMAX:0xffffffff
[    1.090727] eqep 48304180.eqep: QPOSCNT:0x00000000
[    1.090735] eqep 48304180.eqep: omit_interrupt:0
[    1.090743] eqep 48304180.eqep: QEINT:0x0800
[    1.090750] eqep 48304180.eqep: QUPRD:0x05f5e100
[    1.090757] eqep 48304180.eqep: QEPCTL:0x009e write
[    1.090764] eqep 48304180.eqep: QEPCTL:0x009e read
[    1.090786] eqep 48304180.eqep: irq:64, clk_rate:100000000
[    1.094121] pinctrl-single 44e10800.pinmux: pin PIN102 already requested by 48300180.eqep; cannot claim for ocp:P9_30_pinmux

Exactly, I confirm. Everything work perfectly when I use pre-instaled
system, but when I want use another debian or ubuntu running from sd-card
this EP1 not work. So this is software (or configure) problem not hardware.
pt., 16 paź 2020 o 11:07 bjnilsen<EMAIL_ADDRESS>napisał(a):

Attached is qep signals. Looks good.
This issue is related to SW, it worked just fine with the pre-installed
image from factory. I believe it was 4.4 kernel (I forgot to check this
before upgrading to the latest image).
[image: qep_signals]
https://user-images.githubusercontent.com/72491249/96239228-be308680-0f9f-11eb-9fd5-ee49b0e3f938.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/beagleboard/Latest-Images/issues/67#issuecomment-709925152,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABH2KPWQMTGYY45VOIGQIETSLAENRANCNFSM4RS4RAYQ
.

--
Pozdrawiam
Marek Długosz

The pinmux error looks suspicious:
[ 1.114175] pinctrl-single 44e10800.pinmux: pin PIN102 already requested by 48300180.eqep; cannot claim for ocp:P9_30_pinmux

Ok, thank you!
What and where we should correct to make it work?
As I wrote above, if system is booted from eMMC all four encoders work propertly.

Any idea what's wrong or how to fix it?

I got the -1, 0, 1 outputs when config-pin was used to mux multiple pins to the same eQEP.

The problem is that device tree am335x-boneblue.dts uses the wrong pin:
/* E1 */ 	eqep0_pins: pinmux_eqep0_pins { 		pinctrl-single,pins = < 			AM33XX_PADCONF(AM335X_PIN_MCASP0_AXR0, PIN_INPUT, MUX_MODE1)		/* (B12) mcasp0_aclkr.eQEP0A_in */ 			AM33XX_PADCONF(AM335X_PIN_MCASP0_FSR, PIN_INPUT, MUX_MODE1)		/* (C13) mcasp0_fsr.eQEP0B_in */ 		>; 	};
Wrong:
AM335X_PIN_MCASP0_AXR0
Correct:
AM335X_PIN_MCASP0_ACLKR

Nice find @bjnilsen , can you issue a pull request to: https://github.com/beagleboard/BeagleBoard-DeviceTrees to fix it ;)

Pull request added: https://github.com/beagleboard/BeagleBoard-DeviceTrees/pull/28

Pull request merged. Until the fix is released one can use the following steps to solve the problem:
(assuming 4.19.94-ti-r55 kernel on BeagleBone Blue)

git clone https://github.com/beagleboard/BeagleBoard-DeviceTrees.git
cd BeagleBoard-DeviceTrees
make
sudo cp src/arm/am335x-boneblue.dtb /boot/dtbs/4.19.94-ti-r55/am335x-boneblue.dtb
reboot

All: I just had the same issue with reading eqep encoder 1. It reads either 1 and 0; or -1 and 0. I just purchased my Beaglebone blue recently and upgraded the software. Has the kernel been upgraded? Can I check to see if I have a  working kernel or if I need to implement the fix referenced above?


Merge two Clarity extensions into one

same issue as https://github.com/blockstack/clarity-vscode/issues/8 but in this repo

as per notes from our discussion with the foundation, these are the high priority features:

[ ]  Syntax highlighting
[ ]  IntelliSense / Quick Suggestions / documentation on hover.

[ ]  Auto-complete for built-ins as well as user-defined functions & variables.

[ ]  Auto-formatting (with rules).
[ ]  Cross-platform install (without having to compile from source).

cc @MarvinJanssen @lgalabru


AES support

The latest version of minizip supports AES: https://github.com/nmoinvaz/minizip
Can ZipArchive add the support as well?

+1 to update minizip. Xcode complains about many static analyzer issues

Any news on that matter?


Release extensions independently

Hey, great work on this text editor, it's amazing!
I am just wondering if it's possible to use the extensions outside the editor and if not, would it be possible to release them separately? I'm trying to add the typescript extension to an editor, but I don't want the React component that bundles all the languages and extensions together.

Hey @sachinraja, that should be possible AFAIK, I can look into that soon and let you know! If possible, then I'm in favour of releasing them separately!

Thanks! I really appreciate all your work here, it's helped a lot to write my own extensions. Let me know if there's anything I can do to help.

Hey, so having looked into this, it is definitely possible, but it'll introduce some complexity that, quite honestly, isn't worth it for us right now, since the primary consumer of this library is the Data Platform, and we don't have the capacity to do maintain that properly.
If you absolutely do need an extension on its own, your best course of action, in my opinion, would be to fork this repository, and take it from there. Sorry about this!

That's completely fine. I've copied the extensions into my project and tweaked some things for now (with the LICENSE of course).


couldn't logout from current session

linkedinHelper.logout() doesn't work.
Can anyone tell me that how can I logout current user?
I have download the Example project. When I click on the login button, ViewController is present with LinkedIn Login.
After successful login, ViewController is dismissed, pressed the logout button and once again click on the login button.
I got previous user details.

@vishalpethani there is a misunderstanding of the logout function, the user you logged in in web view will stay in, the logout function will only clear out the session in current app.
If you need to logout in web view, then only way is going to linkedin in web and logout there.


URL_BASE includes ':' for SSH and '/' for https

Fix #13 by switching a larger part of the URL as URL_BASE for SSH and https

This does exclude the possibility of non GitHub repos but since all the repos originate from GitHub this should be fine for now.

Probably one should rather use
option (USE_SSH "Use ssh to access git repos" OFF)
if (${USE_SSH})
    set (URL_PROTOCOL "git@")
    set (URL_SEP ":")
else ()
    set (URL_PROTOCOL "https://")
    set (URL_SEP "/")
endif ()

and then
${URL_PROTOCOL}github.com${URL_SEP}ORNL-Fusion/PARVMEC.git

when registering the projects. However, this looks a little bit cluttered...

If we encounter non-github based sub projects, we can modify it at a later date.

Ok.

This does exclude the possibility of non GitHub repos but since all the repos originate from GitHub this should be fine for now.

Probably one should rather use
option (USE_SSH "Use ssh to access git repos" OFF)
if (${USE_SSH})
    set (URL_PROTOCOL "git@")
    set (URL_SEP ":")
else ()
    set (URL_PROTOCOL "https://")
    set (URL_SEP "/")
endif ()

and then
${URL_PROTOCOL}github.com${URL_SEP}ORNL-Fusion/PARVMEC.git

when registering the projects. However, this looks a little bit cluttered...

If we encounter non-github based sub projects, we can modify it at a later date.

Ok.


Auto login after password reset

Hi what would be the recommended way to login someone after they have reset their password? Ideally without having to enter username and password into another form so straight after they have successfully updated the password like confirmEmailAndSignIn
Since I don't have their email handy I can't call the login function and sign them in.
Cheers

So you want some Auth#resetPasswordAndSignIn in addition to Auth#resetPassword, analogous to Auth#confirmEmailAndSignIn for Auth#confirmEmail, right?
I think the reasoning why this isn’t here yet has been that the password reset process should not be streamlined so much that it can easily be used for “login via email”, without remembering the password, and using the reset for every single login. But, after all, why not? Perhaps that decision should indeed be up to the individual service using this library.
Typing the new password once more also ensures that it’s not forgotten again right away. But if the user is copying the password between fields, that doesn’t help, anyway.
Until the feature is here, when using Auth#forgotPassword and building the link to send to the user, you could include an additional parameter with the email address. When the link is clicked and you use Auth#resetPassword, perhaps use Auth#admin#logInAsUserByEmail afterwards – but only after a successful reset, of course.

On the other hand, here, we already discussed returning the email address from Auth#resetPassword. So that would help with your use case as well.
But that would still only be one part of the solution, since you need either the password or Auth#admin#logInAsUserByEmail to complete the login. Sending or storing the password somewhere is generally dangerous, so that only leaves one solution. And the new (proposed) Auth#resetPasswordAndSignIn, of course.

Implemented in https://github.com/delight-im/PHP-Auth/commit/d49b35690cac0bbaa8e158840b5c5dee1104ca43 and documented in https://github.com/delight-im/PHP-Auth/commit/dcd893a12cbf9fb9bb64fa966944e88f1963d141

Thank you for this really appreciate it! To update my version is it a matter of just replacing all the files? I take this isn't a major release so can't update via composer.
Cheers

You can update to any release via Composer :)
Simply running
$ composer update delight-im/auth

should be sufficient.
If you still didn’t want to use Composer, replacing the files would be enough in this case, yes.


Fallback to default locale if country locale fallback returns empty result

Fixes #562
Actually partially reverted d9dde97 and added the test.

Thank you :+1:


CodeTriage Badge

This repository was added to code triage project for increase assistance from developers from all the world. Check here
Need to add badge:
[![Open Source Helpers](https://www.codetriage.com/howtohireme/give-me-poc/badges/users.svg)](https://www.codetriage.com/howtohireme/give-me-poc)

Done


⚠ Bofrost.be has degraded performance

In 617c787, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2323 ms

Resolved: Bofrost.be performance has improved in d8c7ca0.


remove etcd secret creation from odh-deployer

Cherry-picking #a744656ebf672a33974c2eb62fa2114c49535281 from master to 1.24

Merging as this is a cherry-pick from main


nit file link change

:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/tutorials/quickstarter/PrototypeBoards.md
:warning:Warning

Details

windows-iotcore/learn-about-hardware/SuggestedBoards.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/PrototypeBoards.md

Line 22: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#flashing-with-emmc-for-up-squared-other-intel-devices).
Line 23: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#using-the-iot-dashboard-dragonboard-410c).
Line 23: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#flashing-with-emmc-for-up-squared-other-intel-devices).
Line 24: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).
Line 25: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).
Line 26: [Warning] Invalid file link:(~/tutorials/quickstarter/DeviceSetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

windows-iotcore/tutorials/quickstarter/PrototypeBoards.md
:warning:Warning

Details

windows-iotcore/learn-about-hardware/SuggestedBoards.md
:white_check_mark:Succeeded

windows-iotcore/tutorials/quickstarter/PrototypeBoards.md

Line 22: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#flashing-with-emmc-for-up-squared-other-intel-devices).
Line 23: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#using-the-iot-dashboard-dragonboard-410c).
Line 23: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#flashing-with-emmc-for-up-squared-other-intel-devices).
Line 24: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).
Line 25: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).
Line 26: [Warning] Invalid file link:(~/tutorials/quickstarter/devicesetup#using-the-iot-dashboard-raspberry-pi-and-minnowboard).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add trakt icon

Description

Add trakt.tv icon
Type of change

:x: Bug fix (non-breaking change which fixes an issue)
:white_check_mark: Icon addition (non-breaking change that adds/modifies Lawnicons's icons)
:x: General change (non-breaking change that doesn't fit the above categories, such as copyediting)

Icons addition information

Icons added

Trakt (tv.trakt.trakt)

I've been working on some other icons, if this hasn't been accepted by the time I'm done I'll add it to this if that's fine.

Reviewers will definitely tell you it's worth to read the Lawnicon guidelines and fix what's wrong.

Reviewers will definitely tell you it's worth to read the Lawnicon guidelines and fix what's wrong.

Hi, I'm sorry that the contributions upset you, I'll try to find what's wrong and fix them.
But, I am going to assume that you are not happy with the icons that have curves as they do not match the 6px round radius.
If not for that, I'll gladly fix anything else that might be pointed out.
Thanks

@manasch Hi, I'm not upset. I thought I'd draw your attention to the guidelines ahead of time because the moderators will ask you to do it anyway.

@x9136 Hi, I understand sorry.
I am making the changes rn. From what I found, I made the mistake of not using base as 12px and rounded corners not having the 6px radius.
I've switched all to 12px base with the minimal ones getting 14px as well as finer details getting 6px. My only doubt would lie in the usage of the standard widths mentioned.
I will be making another commit with the fixes soon.
I hope this would resolve it.

I have made the changes to fit the guidelines. The only one that I see to be rejected is fasthub-re (in which I will give up on that, I do not know how I can draw that better :smiling_face_with_tear:).
I used 8px as the default stroke as 12px was too thick. As for the finer details I used 6px.
I have ensured that the rest of them use the base stroke as 12px as much as possible along with 14px for the ones that are minimal.
I hope this fits to the standard.
Thanks.

@manasch Cool, but you forgot to round corners somehow. 🥲 There are no right angle icons in this pack.

That is actually quite embarrassing. Sorry for the repeated work, I have changed them all to have rounded corners.
I actually failed to understand from the guidelines what rounded corners meant.
Sorry again.

@Chefski Hey, before I make another commit, was just checking for any other changes to be made and noticed that the svg's I made have newlines and the color is mentioned as black whereas the ones already existing in the repo have no newlines (everything in oneline) and color as #000.
Would this be an issue and if so do I manually change it?  I've been using figma to create and export them and I don't see any export setting to get it the same way as the existing icons.


Upgrade base to 1.5.4

This changes the way we're doing installation, to just use the upstream binaries/tarballs instead of apt.  The apt repos appear to be slow to update, and all they're doing is installing a binary and a systemd script anyway.

This PR is to our develop branch, since master auto-deploys to the production S3 bucket (by way of Amazon's synchronization to their repo.)
@avattathil do I have that correct?  We should only merge to our master branch when we're ready for prod?

ping @jbeda @timothysc

Will do 1.5.5 and the systemd incantations in a follow-up PR.