*: Add Read duration metrics for TiKV

Signed-off-by: jyz0309<EMAIL_ADDRESS>
What problem does this PR solve?
relate kvproto pull request:

kv_read_wall_time

relate tidb pull request :

link

Problem Summary:
Add Read duration metrics for TiKV SLI/SLO.
What is changed and how it works?
What's Changed:
Addkv_read_wall_ms in TimeDetail. Add function collect_scan_summary for RequestHandler to collect the scan executor time.

How it work?
Use collect_scan_summary to collect the exec_stats.summary_per_executor, which is always the scan executor. and use it to get the scan executor time.
Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test
Manual test (add detailed scripts or steps below)

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Release note

*: Add Read duration and throughput metrics for TiKV

Is this PR ready for reviewing?

Yep. I have called @zhongzc to help me review

/run-all-tests

/run-all-tests

/lgtm cancel

@jyz0309 Please add some details to this pull request.

What information does this pull request trying to add.
How do you achieve this.

Rest LGTM.

LGTM

Just a little bit of concern for the test: should we add some tests for these changes?

Just a little bit of concern for the test: should we add some tests for these changes? @zhongzc @jyz0309

These changes won't break anything and it's not easy to test it. I can accept just test manually.

/lgtm

/run-all-tests

/run-all-tests


Cannot access thingsboard after installing in kube cluster using HELM

I have installed thingsboard using HELM. All the services and pods are up and running but cannot access the thingsboard app.
I have tried the following-

Using ingress ip
Using tb-https ip
It seems none of them are working.

Here is the status of the pods

Here is the status of the services

Status of the cert-manager and nginx-ingress:

How can I access the thingsboard?

HAve you set an an ingress? I cannot see it in the logs shown.
In order to access the service you'll need on of these:

ingress and a ingress controller like nginx, DNS pointing there...
set service as loadbalancer, but that's a lot more tricky, because some routes should go to the Thingsboard webui and others to the Thingsboard node
Do you have other ingress services working in this cluster so you can be sure ingress is working properly?


OrientDB Query(NOT LIKE)

which is the equivalent  query for "NOT LIKE" in orientDB

for example: select from object where objId NOT LIKE '%AMP%'

retreive the records where objId doesnot contain string AMP

any workarounds for this?

Hi @neilsaviodsouza
the workaround is
select from object where NOT (objId LIKE '%AMP%')

Thanks
Luigi

Great, thanks.

Not relevant anymore, closing it.


Investigating why this submission: https://www.ebi.ac.uk/gwas/depo-curation/submissions/617bbfa3921d1b000131a073 is blocked for editing from the depo-curation app

This submission
https://www.ebi.ac.uk/gwas/depo-curation/submissions/617bbfa3921d1b000131a073
is blocked for editing from the depo-curation app.
@sajo-ebi could you please take a look - this is a blocker for data release to start.

Is this issue resolved @buniello ?

yes, resolved


feat: check policy validity to prevent duplicate check

Miniscript::from_ast() only executes check_global_consensus_validity() which does not include check_global_policy_validity(). Change to use check_global_validity() to check both consensus and policy validness.
wrap_into_miniscript() executes check_global_validity() internally after Miniscript::from_ast(). As Miniscript::from_ast() now executes check_global_validity(),  it doesn't have to check duplicately.

I was originally thinking to change check_global_validity() inside wrap_into_miniscript() to check_global_policy_validity()(as consensus check is done by from_ast()). I think it's better to strengthen the validness check in from_ast(), and do nothing in wrap_into_miniscript().

Actually, looking at this again, we have Miniscript::from_components_unchecked that allows for creating miniscripts that are not policy valid. And maybe parsing policy non-valid should not have first class support anyways.

Thanks for detailed review! I wasn't not sure whether it's intentional. I've changed just commit message from fix: ... to feat: ... for the clear record.

Sure, if you think this is an improvement @sanket1729 I will review this and merge it.
But in general I want to overhaul all the validation logic (which not only includes standardness vs non-standardness but also "sane" vs "insane"), which currently is spread across the codebase in adhoc and inconsistent ways. I have https://github.com/rust-bitcoin/rust-miniscript/discussions/723#discussioncomment-10383465 about this plan and have made a substantial amount of progress toward it.
But in order to do this I needed to clean up some error returns, which required I eliminate some recursion throughout the library, which is currently blocked on https://github.com/rust-bitcoin/rust-miniscript/pull/745 (which is a pretty minor PR, but it's in my working branch and I use it heavily to guide my un-recursion work, so I'd like it to be merged before PR'ing more stuff).

Ok, looking at my current working branch, I have about 40 commits queued up and none of them are in conflict with this (one completely rewrites the Miniscript string parser but this part of the logic is essentially unchanged, so I'll need to rebase but it's not like this is unnecessary/wasted work).
So let's pull this in.

which is currently blocked on https://github.com/rust-bitcoin/rust-miniscript/pull/745 (which is a pretty minor PR, but it's in my working branch and I use it heavily to guide my un-recursion work, so I'd like it to be merged before PR'ing more stuff).

Sorry, I missed this and it drowned in notifications. ACKed this PR now. Excited for the cleanups. We can holdoff merging this if you want to try to opening a PR with the other changes.

No worries! I've been pretty busy with Simplicity and hadn't had time to work on this anyway, or I would've pinged you.
And I merged this one -- will rebase my work on it, changing the local checks to global ones in my refactor.


adding awards

Haha I love these awards!
One request though, can you either come up with a new issuer that might issue these goofy awards or just make the existing Fluree University profile the issuer of these?


 Could you try conda list graphvite and check if the signature is cuda92?

conda list graphvite
Name                    Version                   Build  Channel
graphvite                 0.1.0               py27cuda100    milagraph
So it means when I used conda install -c milagraph graphvite, it built with cuda 10.0？Could you tell me how to build with cuda 9.2?

OK, I found that conda install -c milagraph graphvite=0.1.0=py27cuda92 is OK, Thanks!


Please approve recognition of our many contributors

Issue for adding our many contributors to our public readme

@all-contributors
please add @sonejah21 for design
please add @DHolmanCoding for code
please add @philwinder for ideas
please add @bmunday3 for ideas, maintenance, question


Get Caffe2 Error when import the pytorch-lightning.

🐛 Bug
Get Caffe2 Error when import the pytorch-lightning.
To Reproduce
Steps to reproduce the behavior:
import pytorch_lightning
WARNING:root:This caffe2 python run does not have GPU support. Will run in CPU only mode.
WARNING:root:Debug message: /opt/caffe2/build/lib/libcaffe2.so: undefined symbol: dnnLRNCreateForward_F32
CRITICAL:root:Cannot load caffe2.python. Error: /opt/caffe2/build/caffe2/python/caffe2_pybind11_state.so: undefined symbol: _Py_ZeroStruct

Environment

CUDA:

GPU:

Tesla P100-PCIE-16GB

available:         True
version:           10.0.130

Packages:

numpy:             1.18.1
pytorch_lightning   0.7.5
pyTorch_debug:     False
pyTorch_version:   1.2.0
tensorboard:       2.2.1
tqdm:              4.45.0

System:

OS:                Linux
architecture:

64bit

processor:         x86_64
python:            3.7.6
version:           #76-Ubuntu SMP Wed Feb 12 03:02:44 UTC 2020

well I do no think it is lightning issue as we rely on pytorch... @williamFalcon?

how do you activate the environment before you do the import? It must be trying to load caffe somewhere but definitely not in lightning.

Does it happen in the interactive python shell too?

Does it happen in the interactive python shell too?

Yes it does!

can you try import pytorch?

can you try import torch?

PyTorch is ok.

It seems that there is some conflict in Caffe2 and PyTorch Lightning in Azure DLVM setup.
When I delete the Caffe2, it works fine now.


hue stops polling for results abruptly after 5 min leading to network error in case of large file csv downloads

Is there an existing issue for this?

[X] I have searched the existing issues

Description
We are getting an error while downloading the presto query result from Hue UI. We are using hue 4.7.1 to execute queries on Presto, after executing the query we use download the query result as CSV option in Hue UI. The download progresses for sometime but then it fails (We get this error in the browser: Failed - Network error). We do not find any error logs on the hue pods though
We observe this issue for large file csv downloads with the root cause that hue stops polling for results abruptly after 5 min. This happens 4 out of 5 times and hence the download fails with network error . Is there any configuration/ time-out parameter that can be configured on the hue end that can fix this issue ?

Steps To Reproduce

Run a query that contains at least 5 columns  and 10 million rows.
Click on the option to download as a csv
Observe that the download fails with message as network error

Logs
No response
Hue version
4.7.1

@ranade1 I know this is for an old release, but do you know anything about this, can it be configured?

Could you please provide more details on the following?

Which version of Hue are you using?

Is Hue running on a CDH On-Prem setup?

What is the size of the data file you are trying to download?

Can you share the configuration specifics of the Hue server?


Extremely slow runtime when using jacfwd()

I recently switched from autograd to jax, as I saw that jax supports jit which will (hopefully) make runtimes faster. However, when comparing the speed of autograd's jacobian(fun) against jax's jit(jacfwd(fun)), the results are disappointing. I haven't done concrete timings yet, but when using jacobian(fun) in my program, it can produce results in about 5 minutes, however, when using jit(jacfwd(fun)) it'll probably take over an hour (I stopped the program after about 15 minutes when I saw it wasn't going anywhere).
I feel like I must be doing something wrong, has anyone else experiences such large runtime differences when using autograd's jacobian(fun) versus jax's jit(jacfwd(fun))?

Can you provide a small runnable reproduction? It's impossible to speculate about performance without something concrete we can benchmark ourselves.

It's gotta be all compilation time (and something's getting unrolled). +1 to a repro!


Configurator scrollbar not entirely acessible

Home Assistant release with the issue:
0.72.1
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on RPi 3
Component/platform:
Configurator
Description of problem:
The scrollbar is hidden/not acessible (half of it). I need to grab it on the left, if I want to.
If I delete that element that's overlapping it with Chrome-Inspect, the scrollbar works normally again.
I can better show it with this GIF:

I hope this can be fixed, as this is very annoying when trying to reach that scrollbar.

Since this is directly related to the configurator and not only the addon, I have created an issue here: https://github.com/danielperna84/hass-configurator/issues/102


Derelict Properties Amendment

All abandoned properties are to be torn down, regardless of district or type of district.

approved >.>


How to get device token using cordova-plugin-firebase-messaging in Cordova?

Hi, i try to get device token with cordova-plugin-firebase-messaging , but i get empty value, i created app in Firebase console and download google-services  and added in root folder. In  index.htm file i call that google-services.json. In index.js code as follows.
     document.addEventListener('deviceready', onDeviceReady, false);          function onDeviceReady() {         // Cordova is now initialized. Have fun!          //alert("3");     cordova.plugins.firebase.messaging.getToken().then(function(token) {         alert("Got device token: ", token);      });      }
But i did not get token when open app.
My Cordova version is 11.0.0 and i installed cordova.plugins.firebase.messaging only.
Any reply much appreciated.
Thanks and regards
Aravind

I have the same problem. Getting an empty string or null (haven't checked that yet).

Hi, i can get device token and payload details when passing from firebase, but badge count not showing in app icon in android. Did u try badge count in app icon instead of red dot ?

What have you done to fix the problem that you didn't got an token with the getToken Method?
Since I'm stuck with the first problem (empty token) I haven't tried anything else since I can't send any message to the phone without a token.


Test1

👷 Deploy Preview for polite-dolphin-8b4710 processing.

Name
Link

🔨 Latest commit
c16a3c0a8277c97693e592b94062611a144bda20

🔍 Latest deploy log
https://app.netlify.com/sites/polite-dolphin-8b4710/deploys/6359f6a44042c900092421af


Add tests for dfp

Removed calls checking URL since we are already doing this when we decode encoded data to make sure it is the same as the data that is passed in from get-device-info

Merged this in because this is just tests.


elm 0.19 ready

Hey,
could you re-publish the package so it is compatible to elm 0.19?
Thank you! Great work!

Done.
I didn't have much time to sink into it, and the changes to Css and Browser were a pain, I hope I got all bugs.
Closed by https://github.com/xarvh/elm-slides/pull/21

Thank you!!


Map

Closes #128
US 09.01.01
As an owner, I want to specify a geo location on a map of where to receive a book when I accept a request on the book.
US 09.02.01
As a borrower, I want to view the geo location of where to receive a book I will be borrowing.
i merged this with one of amy's older branches to test it
has two buttons in the bookinfoactivity:
-set and get location
set now has autocomplete
get will move you to the marker where the meeting location is
after changes:
now as soon as a request is accepted the owner must choose a location
after choosing location returns to the book info activity
then a button shows up at the bottom "view location"
which takes them to a map with marker of where to meet
clicking the marker gives options to get directions or open in google maps app
since the user story does not say borrower should choose a location i didn't allow borrower to change location when returning the book

Also, it seems kind of strange to me that clicking the current location button doesn't also set the location. As a user, I should be able to to not have to type in my exact location. Also, I don't really get when setting the location happens, when you type in the address? Is there a way to make setting the location more explicit like clicking the marker?

Can reproduce the crash @AY-Chen is seeing.

@AY-Chen
user is now forced to choose a location after accepting a request
pressing back is disabled until a location is selected
also stopped displaying the marker when setting a new location, though camera will take you to that location since that was the last place movecamera() was called

You wrote in Slack that the flow should be like this:
"i think it's Owner Scan (for Borrowing) + Set Location -> Borrower Scan (for Borrowing) -> Borrower Scan (for Returning) + Set Location -> Owner Scan (for Returning)"
But then there was no place for the borrower to set the location. Is it assumed that the same location for checkout will be for pickup?
Also, you can still crash the app by pressing get location right after the book is returned:
https://drive.google.com/open?id=1hF9dEiXBqX8Y5-uO7lseUQr-hgToOR3f
Either disable the get location button if the location doesn't exist or handle the location not existing in the map activity.

I reread the User Stories and they don't specify borrower setting a location, just owner
so i assumed only the owner sets location
the new commit disables getting/view location immediately after returning a book


WIP: Use lasso to intern names

This makes Name use a NonZeroU32 internally, shrinking its size from 32 Bytes to 4 while keeping a niche value.
without interning
Total: 23.528866195s, 1359mb allocated 0b resident
   268mb Unaccounted
  2100kb Remaining

with interning
Total: 22.504256039s, 1222mb allocated 0b resident
   269mb Unaccounted
    10mb Remaining

("Remaining" contains the storage used by the interner here)
TODO:

[ ] Get rid of undesirable dependencies (ahash / const-random)

This seems impossible to fix without a new dashmap release, so maybe we should use yet-a-different library for interning

[ ] Allow clearing the interner and track its memory usage separately (https://github.com/Kixiron/lasso/pull/5)
[ ] Test memory growth in real-world use cases (I think we'll reintern variations of large string literals over and over again when editing inside them – lasso does no reference counting unlike string_cache, so this might be bad in the long run)
[x] impl Debug for Name should print the string, not the contained number
[ ] There's some really weird test failures still

I've been thinking about adding a few things that coincide with what you need quite well:

Configurable memory limits for all interners, allowing a fixed capacity of used memory
Alternative multi-threaded maps/impls, I'm not super satisfied with dashmap's dependency situation either, but I don't know of another library that meets my needs

Simply having an RwLock<Rodeo> could also meet your needs just as well for less dependencies, it'll cost slightly in access times but it will naturally pair with having it globally accessible

This seems impossible to fix without a new dashmap release, so maybe we should use yet-a-different library for interning

we want to use dashmap in salsa as well, so it might make sense to poke maintainers.

@matklad @Kixiron dashmap author here! v3's dependency situation is a bit of a mess indeed. v4 is shaping up to fix that but it's not 100% done yet, turns out lockfree concurrent maps aren't something you can whip together in an evening exactly. v4 has some beta versions out now but they don't have all features yet, most notably they are missing a generic entry CAS feature which is coming before release. v4 depends only on once_cell but with an optional dependency on serde too.

I just noticed that CI is passing. It really shouldn't. Some tests fail locally on 2 different machines.

Perhaps this needs a rebase? CI Checks merge commit: https://github.com/rust-analyzer/rust-analyzer/pull/5491/checks?check_run_id=899309432#step:2:408

Nope, still the same failures all over the place.

Oh, nice, they fail nondeterministically :(

compile_time rand non-deterministic Test failure would be fun, if this is it.


TextField autofill for SMS verification messages

Is it planned to support autofill possibility for verification messages in TextFields?
How to show verification code suggestion on keyboard from Message (iOS 12 with .oneTimeCode)

As this feature is currently only supported with the iOS UITextField and the system keyboard, this probably cannot be implemented currently from my point of view, as flutter draws it's elements itself and does not rely on native components.

Did you try https://pub.dartlang.org/packages/sms_autofill ? :)

Did you try https://pub.dartlang.org/packages/sms_autofill ? :)

The package is Android only

@stefandevo for me it works also on iOS (at least at some point it did^^)

This was implemented a while ago (https://github.com/flutter/flutter/issues/4818) , but I think it seems quite broken at the moment. Not only is it unreliable, but the suggestion bar somehow gets placed on top of the Keyboard, meaning its hard to see and click.

@jaumard Testing with your example and I tried to request SMS OTP code from Firebase Phone Auth, but it's not working. Did I miss something?

@locpt firebase phone auth is not compliant with this package, as the readme state:  SMS must End with an 11-character hash string that identifies your app  and you can't do that with firebase phone auth. That's why it doesn't work

@jaumard Is there any ways to archive like your package sms_autofill for Firebase Phone Auth? I don't want to request SMS permission from the user to auto-fill the OTP code. It sounds weird. I have tried some packages or research so far but seem like no way to archive that requirement. I wanna receive your recommendation.

No there is no way, but you don't need SMS permission to auto-fill the OTP code if you follow the instructions of auto_fill package.

@locpt firebase phone auth is not compliant with this package, as the readme state: SMS must End with an 11-character hash string that identifies your app and you can't do that with firebase phone auth. That's why it doesn't work

Does this mean using firebase to authenticate users makes this package impossible to use? I'm confused whether firebase phone auth is different from firebase auth.

So firebase is the problem?

Two years later, now the flutter has support for autofill on ios, but i couldn't run on ios

But it is not works properly. Sms code above keyboard does not hide when I focuse on another TextField ( on the other screen ). And I ever can't disable autosuggestion by myself, with my keyboardType =(

OTP works for me on iOS:


Direct Bluetooth and Wifi Funtionality.

Is your feature request related to a problem? Please describe
I'd like direct Bluetooth and Wifi Functionality like they have on chromebooks. this allows me to control devices over bluetooth and wifi easily. 😁
Describe the solution you'd like
Direct Bluetooth and wifi functionality.
Describe alternatives you've considered
Chromebooks are a really good example of how this should work.
Please specify the version of Windows Subsystem for Android
2307.40000.6.0

Thank you for the feedback. Could you please give us more information about your scenario, especially around the Wifi functionality?

#522


Implement Library Import

Implement the process for importing library data and copying files to library folders.

Part of the import is to "prettify" titles.  Besides the title casing algorithm already added, here are other ways to standardize titles during the import:
Album:

Detect "x Edition" and move that data to the Edition field.
Detect "Soundtrack" in grouping and genre fields, add flag.
Detect "Compilation" in grouping, add flag.
Detect "Promotional" in title, add flag.
Detect holidays in title.
Detect disc number in title.

In post import analysis:

Add album release and "first released on" based off year in import tag.
Add album is live flag if all tracks are live
Add album is remix flag if all tracks are remixes.
Add album holiday if all tracks are for a holiday or already detected holiday in title.

Artist:

Detect leading articles "the" or "a" and save in separate field.

Song:

Replace [ and ] with ( and )
Detect asides in song titles:

Flags to add Artist collaborators:
* (Featuring xxx)
* (Feat. xxx)
* (Feat xxx)
* (With xxx)
* Ends with "Featuring xxx"
* Ends with "Feat. xxx"

Remixes/Versions
* (xxx Mix)
* (xxx Remix)
* (Remix)
* (Remix xxx)
* (xxx Remix xxx)
* (xxx Version)
* (Edit)
* (xxx Edit)
* (xxx Remake)
* (xxx Rework)
* (xxx Re-work)
* (xxx Dub)
* (xx Take xx)
* (xxx Acoustic)
* (Acoustic)
* (Acoustic xxx)
* (Instrumental)
* (Home Recording)
* (Radio Appearance)
* (Demo)
* (Demo xxx)
* (xxx Demo)

Live
* (Live)
* (Live at xxx)
* (Live from xxx)
* (Live on xxx)
* (Live in xxx)

Cover
* (xxx Cover)

Just Remove
* (Bonus Track)
* (xxx Bonus Track)
* (Previously Unreleased)
* (*)


Unable to connect to QGC and MavSDK

Hi,
I'm unable to connect to the PX4 SITL using both QGC and MavSDK.
This is the MavSDK python script. It is stuck in the drone.connect step.
import asyncio
from mavsdk import System

async def run():
    drone = System()
    await drone.connect(system_address="udp://:14540")

    print("Waiting for drone to connect...")
    async for state in drone.core.connection_state():
        print(state)  # Print the connection state for debugging
        if state.is_connected:
            print(f"Drone discovered with UUID: {state.uuid}")
            break

asyncio.run(run())

I'm sharing the logs from the docker container
(base)  ~  docker run --rm -it jonasvautherin/px4-gazebo-headless:1.14.3
Scanning dependencies of target gazebo_iris__empty
WARNING gazebo_iris__empty target DEPRECATED, please use gazebo-classic_iris__empty
make[5]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  0%] Built target parameters_xml
[  0%] Built target ver_gen
[  0%] Built target events_header
[  0%] Built target uorb_headers
[  0%] Built target flighttasks_generated
[  1%] Built target events_json
[  1%] Built target actuators_json
[  1%] Built target component_general_json
[  1%] Built target romfs_gen_files_target
[ 22%] Built target uorb_msgs
[ 22%] Built target geo
[ 22%] Built target perf
[ 22%] Built target tinybson
[ 24%] Built target work_queue
[ 24%] Built target drivers_board
[ 24%] Built target parameters
[ 25%] Built target px4_work_queue
[ 27%] Built target px4_platform
[ 27%] Built target lockstep_scheduler
[ 27%] Built target px4_daemon
[ 28%] Built target px4_layer
[ 28%] Built target adsb
[ 29%] Built target airspeed
[ 30%] Built target bezier
[ 30%] Built target hysteresis
[ 30%] Built target avoidance
[ 30%] Built target battery
[ 30%] Built target cdev
[ 30%] Built target systemlib
[ 31%] Built target uORB
[ 31%] Built target lib__cdev__test__cdev_test
[ 31%] Built target circuit_breaker
[ 31%] Built target CollisionPrevention
[ 34%] Built target controllib
[ 34%] Built target lib__controllib__controllib_test
[ 34%] Built target conversion
[ 34%] Built target drivers_accelerometer
[ 35%] Built target drivers_gyroscope
[ 35%] Built target drivers_magnetometer
[ 35%] Built target l1
[ 35%] Built target mathlib
[ 35%] Built target output_functions_header
[ 35%] Built target mixer_module
[ 35%] Built target motion_planning
[ 35%] Built target npfg
[ 35%] Built target pid
[ 35%] Built target RateControl
[ 35%] Built target rc
[ 35%] Built target lib__rc__rc_tests
[ 36%] Built target ringbuffer
[ 37%] Built target sensor_calibration
[ 37%] Built target SlewRate
[ 38%] Built target SystemIdentification
[ 38%] Built target tecs
[ 39%] Built target timesync
[ 39%] Built target tunes
[ 39%] Built target variable_length_ringbuffer
[ 39%] Built target version
[ 39%] Built target WeatherVane
[ 39%] Built target wind_estimator
[ 39%] Built target world_magnetic_model
[ 39%] Built target arch_tone_alarm
[ 39%] Built target modules__uORB__uORB_tests
[ 40%] Built target lib__work_queue__test__wqueue_test
[ 41%] Built target drivers__camera_trigger
[ 41%] Built target git_gps_devices
[ 43%] Built target drivers__gps
[ 43%] Built target message_display
[ 43%] Built target drivers__osd__msp_osd
[ 43%] Built target drivers__tone_alarm
[ 43%] Built target modules__airship_att_control
[ 43%] Built target modules__airspeed_selector
[ 43%] Built target modules__attitude_estimator_q
[ 44%] Built target modules__camera_feedback
[ 44%] Built target failure_detector
[ 44%] Built target mode_util
[ 47%] Built target health_and_arming_checks
[ 47%] Built target failsafe
[ 47%] Built target ArmAuthorization
[ 48%] Built target ArmStateMachine
[ 50%] Built target modules__commander
[ 51%] Built target ActuatorEffectiveness
[ 51%] Built target ControlAllocation
[ 52%] Built target modules__control_allocator
[ 52%] Built target modules__dataman
[ 53%] Built target EKF2Utility
[ 57%] Built target modules__ekf2
[ 58%] Built target modules__events
[ 58%] Built target FlightTask
[ 59%] Built target FlightTaskUtility
[ 59%] Built target FlightTaskAuto
[ 59%] Built target FlightTaskDescend
[ 60%] Built target FlightTaskFailsafe
[ 60%] Built target FlightTaskManualAltitude
[ 60%] Built target FlightTaskManualAltitudeSmoothVel
[ 60%] Built target FlightTaskManualAcceleration
[ 61%] Built target FlightTaskManualPosition
[ 61%] Built target FlightTaskManualPositionSmoothVel
[ 61%] Built target FlightTaskTransition
[ 62%] Built target follow_target_estimator
[ 62%] Built target FlightTaskAutoFollowTarget
[ 62%] Built target FlightTaskOrbit
[ 63%] Built target modules__flight_mode_manager
[ 63%] Built target modules__fw_att_control
[ 63%] Built target fw_autotune_attitude_control
[ 63%] Built target launchdetection
[ 63%] Built target runway_takeoff
[ 63%] Built target modules__fw_pos_control
[ 64%] Built target modules__fw_rate_control
[ 65%] Built target drivers__gimbal
[ 65%] Built target modules__gyro_calibration
[ 67%] Built target modules__gyro_fft
[ 68%] Built target modules__land_detector
[ 68%] Built target modules__landing_target_estimator
[ 69%] Built target modules__load_mon
[ 70%] Built target modules__local_position_estimator
[ 71%] Built target modules__logger
[ 71%] Built target modules__mag_bias_estimator
[ 72%] Built target module__manual_control
[ 72%] Built target git_mavlink_v2
[ 72%] Built target mavlink_c_generate_uavionix
[ 74%] Built target modules__mavlink
[ 75%] Built target mavlink_c_generate
[ 75%] Built target modules__mavlink__mavlink_tests
[ 75%] Built target AttitudeControl
[ 76%] Built target modules__mc_att_control
[ 76%] Built target mc_autotune_attitude_control
[ 77%] Built target zero_order_hover_thrust_ekf
[ 77%] Built target modules__mc_hover_thrust_estimator
[ 77%] Built target PositionControl
[ 77%] Built target Takeoff
[ 77%] Built target modules__mc_pos_control
[ 77%] Built target modules__mc_rate_control
[ 77%] Built target geofence_breach_avoidance
[ 78%] Built target mission_feasibility_checker
[ 80%] Built target modules__navigator
[ 80%] Built target modules__payload_deliverer
[ 80%] Built target modules__rc_update
[ 81%] Built target modules__replay
[ 81%] Built target modules__rover_pos_control
[ 81%] Built target data_validator
[ 81%] Built target vehicle_acceleration
[ 81%] Built target vehicle_imu
[ 82%] Built target vehicle_air_data
[ 82%] Built target vehicle_angular_velocity
[ 82%] Built target vehicle_gps_position
[ 82%] Built target vehicle_magnetometer
[ 84%] Built target vehicle_optical_flow
[ 84%] Built target modules__sensors
[ 84%] Built target modules__simulation__battery_simulator
[ 85%] Built target modules__simulation__pwm_out_sim
[ 85%] Built target modules__simulation__sensor_airspeed_sim
[ 85%] Built target modules__simulation__sensor_baro_sim
[ 85%] Built target modules__simulation__sensor_gps_sim
[ 85%] Built target modules__simulation__senosr_mag_sim
[ 86%] Built target modules__simulation__simulator_mavlink
[ 86%] Built target modules__simulation__simulator_sih
[ 87%] Built target modules__temperature_compensation
[ 87%] Built target modules__uuv_att_control
[ 87%] Built target modules__uuv_pos_control
[ 88%] Built target modules__vtol_att_control
[ 88%] Built target systemcmds__actuator_test
[ 88%] Built target systemcmds__bsondump
[ 88%] Built target systemcmds__dyn
[ 89%] Built target systemcmds__failure
[ 89%] Built target systemcmds__led_control
[ 89%] Built target systemcmds__param
[ 89%] Built target systemcmds__perf
[ 89%] Built target systemcmds__sd_bench
[ 90%] Built target systemcmds__shutdown
[ 90%] Built target systemcmds__system_time
[ 93%] Built target systemcmds__tests
[ 94%] Built target systemcmds__tests__hrt_test
[ 94%] Built target systemcmds__topic_listener
[ 94%] Built target systemcmds__tune_control
[ 94%] Built target systemcmds__uorb
[ 95%] Built target systemcmds__ver
[ 95%] Built target systemcmds__work_queue
[ 95%] Built target modules__fake_gps
[ 95%] Built target modules__fake_imu
[ 95%] Built target examples__fake_magnetometer
[ 96%] Built target examples__hello
[ 96%] Built target examples__px4_mavlink_debug
[ 96%] Built target examples__px4_simple_app
[ 96%] Built target examples__work_item
[ 97%] Built target px4
[ 98%] Built target git_sitl_gazebo-classic
[ 98%] Performing build step for 'sitl_gazebo-classic'
[  3%] Built target mav_msgs
[  6%] Built target std_msgs
[  8%] Built target nav_msgs
[ 11%] Built target physics_msgs
[ 13%] Built target klt_feature_tracker
[ 29%] Built target models_gen
[ 45%] Built target sensor_msgs
[ 48%] Built target OpticalFlow
[ 49%] Built target ForceVisual
[ 52%] Built target LiftDragPlugin
[ 52%] Built target AdvancedLiftDragPlugin
[ 55%] Built target gazebo_user_camera_plugin
[ 57%] Built target gazebo_groundtruth_plugin
[ 58%] Built target gazebo_lidar_plugin
[ 60%] Built target gazebo_sonar_plugin
[ 61%] Built target gazebo_random_velocity_plugin
[ 63%] Built target gazebo_opticalflow_mockup_plugin
[ 64%] Built target gazebo_opticalflow_plugin
[ 65%] Built target gazebo_camera_manager_plugin
[ 67%] Built target gazebo_airship_dynamics_plugin
[ 68%] Built target gazebo_airspeed_plugin
[ 70%] Built target gazebo_vision_plugin
[ 72%] Built target gazebo_uuv_plugin
[ 74%] Built target gazebo_imu_plugin
[ 75%] Built target gazebo_gimbal_controller_plugin
[ 76%] Built target gazebo_wind_plugin
[ 79%] Built target gazebo_mavlink_interface
[ 81%] Built target gazebo_catapult_plugin
[ 82%] Built target gazebo_motor_model
[ 83%] Built target gazebo_multirotor_base_plugin
[ 84%] Built target gazebo_usv_dynamics_plugin
[ 86%] Built target gazebo_magnetometer_plugin
[ 88%] Built target gazebo_barometer_plugin
[ 90%] Built target gazebo_parachute_plugin
[ 91%] Built target gazebo_pose_sniffer_plugin
[ 92%] Built target gazebo_aruco_plugin
[ 93%] Built target gazebo_controller_interface
[ 95%] Built target gazebo_drop_plugin
[ 96%] Built target gazebo_gst_camera_plugin
[ 97%] Built target gazebo_gps_plugin
[ 98%] Built target gazebo_irlock_plugin
[100%] Built target gazebo_video_stream_widget
[ 98%] No install step for 'sitl_gazebo-classic'
[ 98%] Completed 'sitl_gazebo-classic'
[100%] Built target sitl_gazebo-classic
Scanning dependencies of target gazebo-classic_iris__empty
SITL ARGS
sitl_bin: /root/Firmware/build/px4_sitl_default/bin/px4
debugger: none
model: iris
world: empty
src_path: /root/Firmware
build_path: /root/Firmware/build/px4_sitl_default
GAZEBO_PLUGIN_PATH :/root/Firmware/build/px4_sitl_default/build_gazebo-classic
GAZEBO_MODEL_PATH :/root/Firmware/Tools/simulation/gazebo-classic/sitl_gazebo-classic/models
LD_LIBRARY_PATH :/root/Firmware/build/px4_sitl_default/build_gazebo-classic
Using: /root/Firmware/Tools/simulation/gazebo-classic/sitl_gazebo-classic/models/iris/iris.sdf
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory
not running gazebo gui
SITL COMMAND: "/root/Firmware/build/px4_sitl_default/bin/px4" "/root/Firmware/build/px4_sitl_default"/etc

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [init] found model autostart file as SYS_AUTOSTART=10015
INFO  [param] selected parameter default file parameters.bson
INFO  [param] selected parameter backup file parameters_backup.bson
  SYS_AUTOCONFIG: curr: 0 -> new: 1
ERROR [param] Parameter UXRCE_DDS_KEY not found.
  SYS_AUTOSTART: curr: 0 -> new: 10015
  CAL_ACC0_ID: curr: 0 -> new: 1310988
  CAL_GYRO0_ID: curr: 0 -> new: 1310988
  CAL_ACC1_ID: curr: 0 -> new: 1310996
  CAL_GYRO1_ID: curr: 0 -> new: 1310996
  CAL_ACC2_ID: curr: 0 -> new: 1311004
  CAL_GYRO2_ID: curr: 0 -> new: 1311004
  CAL_MAG0_ID: curr: 0 -> new: 197388
  CAL_MAG0_PRIO: curr: -1 -> new: 50
  CAL_MAG1_ID: curr: 0 -> new: 197644
  CAL_MAG1_PRIO: curr: -1 -> new: 50
* SENS_BOARD_X_OFF: curr: 0.0000 -> new: 0.0000
* SENS_DPRES_OFF: curr: 0.0000 -> new: 0.0010
INFO  [dataman] data manager file './dataman' size is 7866640 bytes
etc/init.d-posix/rcS: 39: [: Illegal number:
INFO  [init] PX4_SIM_HOSTNAME: localhost
INFO  [simulator_mavlink] Waiting for simulator to accept connection on TCP port 4560
INFO  [simulator_mavlink] Simulator connected on TCP port 4560.
INFO  [lockstep_scheduler] setting initial absolute time to 500000 us
INFO  [commander] LED: open /dev/led0 failed (22)
ERROR [param] Parameter UXRCE_DDS_DOM_ID not found.
etc/init.d-posix/rcS: 292: etc/init.d-posix/rcS: uxrce_dds_client: not found
INFO  [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 18570 remote port 14550
INFO  [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540
INFO  [mavlink] mode: Onboard, data rate: 4000 B/s on udp port 14280 remote port 14030
INFO  [mavlink] mode: Gimbal, data rate: 400000 B/s on udp port 13030 remote port 13280
INFO  [logger] logger started (mode=all)
INFO  [logger] Start file log (type: full)
INFO  [logger] [logger] ./log/2024-06-12/17_05_31.ulg
INFO  [logger] Opened full log file: ./log/2024-06-12/17_05_31.ulg
INFO  [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO  [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO  [px4] Startup script returned successfully
pxh> INFO  [tone_alarm] home set
INFO  [tone_alarm] notify negative
INFO  [commander] Ready for takeoff!
(base)  ✘  ~  docker run --rm -it jonasvautherin/px4-gazebo-headless:1.14.3
Scanning dependencies of target gazebo_iris__empty
WARNING gazebo_iris__empty target DEPRECATED, please use gazebo-classic_iris__empty
make[5]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  0%] Built target parameters_xml
[  0%] Built target ver_gen
[  0%] Built target events_header
[  0%] Built target uorb_headers
[  0%] Built target flighttasks_generated
[  1%] Built target events_json
[  1%] Built target actuators_json
[  1%] Built target component_general_json
[  1%] Built target romfs_gen_files_target
[ 22%] Built target uorb_msgs
[ 22%] Built target geo
[ 22%] Built target perf
[ 22%] Built target tinybson
[ 24%] Built target work_queue
[ 24%] Built target drivers_board
[ 24%] Built target parameters
[ 25%] Built target px4_work_queue
[ 27%] Built target px4_platform
[ 27%] Built target lockstep_scheduler
[ 27%] Built target px4_daemon
[ 28%] Built target px4_layer
[ 28%] Built target adsb
[ 29%] Built target airspeed
[ 30%] Built target bezier
[ 30%] Built target hysteresis
[ 30%] Built target avoidance
[ 30%] Built target battery
[ 30%] Built target cdev
[ 30%] Built target systemlib
[ 31%] Built target uORB
[ 31%] Built target lib__cdev__test__cdev_test
[ 31%] Built target circuit_breaker
[ 31%] Built target CollisionPrevention
[ 34%] Built target controllib
[ 34%] Built target lib__controllib__controllib_test
[ 34%] Built target conversion
[ 34%] Built target drivers_accelerometer
[ 35%] Built target drivers_gyroscope
[ 35%] Built target drivers_magnetometer
[ 35%] Built target l1
[ 35%] Built target mathlib
[ 35%] Built target output_functions_header
[ 35%] Built target mixer_module
[ 35%] Built target motion_planning
[ 35%] Built target npfg
[ 35%] Built target pid
[ 35%] Built target RateControl
[ 35%] Built target rc
[ 35%] Built target lib__rc__rc_tests
[ 36%] Built target ringbuffer
[ 37%] Built target sensor_calibration
[ 37%] Built target SlewRate
[ 38%] Built target SystemIdentification
[ 38%] Built target tecs
[ 39%] Built target timesync
[ 39%] Built target tunes
[ 39%] Built target variable_length_ringbuffer
[ 39%] Built target version
[ 39%] Built target WeatherVane
[ 39%] Built target wind_estimator
[ 39%] Built target world_magnetic_model
[ 39%] Built target arch_tone_alarm
[ 39%] Built target modules__uORB__uORB_tests
[ 40%] Built target lib__work_queue__test__wqueue_test
[ 41%] Built target drivers__camera_trigger
[ 41%] Built target git_gps_devices
[ 43%] Built target drivers__gps
[ 43%] Built target message_display
[ 43%] Built target drivers__osd__msp_osd
[ 43%] Built target drivers__tone_alarm
[ 43%] Built target modules__airship_att_control
[ 43%] Built target modules__airspeed_selector
[ 43%] Built target modules__attitude_estimator_q
[ 44%] Built target modules__camera_feedback
[ 44%] Built target failure_detector
[ 44%] Built target mode_util
[ 47%] Built target health_and_arming_checks
[ 47%] Built target failsafe
[ 47%] Built target ArmAuthorization
[ 48%] Built target ArmStateMachine
[ 50%] Built target modules__commander
[ 51%] Built target ActuatorEffectiveness
[ 51%] Built target ControlAllocation
[ 52%] Built target modules__control_allocator
[ 52%] Built target modules__dataman
[ 53%] Built target EKF2Utility
[ 57%] Built target modules__ekf2
[ 58%] Built target modules__events
[ 58%] Built target FlightTask
[ 59%] Built target FlightTaskUtility
[ 59%] Built target FlightTaskAuto
[ 59%] Built target FlightTaskDescend
[ 60%] Built target FlightTaskFailsafe
[ 60%] Built target FlightTaskManualAltitude
[ 60%] Built target FlightTaskManualAltitudeSmoothVel
[ 60%] Built target FlightTaskManualAcceleration
[ 61%] Built target FlightTaskManualPosition
[ 61%] Built target FlightTaskManualPositionSmoothVel
[ 61%] Built target FlightTaskTransition
[ 62%] Built target follow_target_estimator
[ 62%] Built target FlightTaskAutoFollowTarget
[ 62%] Built target FlightTaskOrbit
[ 63%] Built target modules__flight_mode_manager
[ 63%] Built target modules__fw_att_control
[ 63%] Built target fw_autotune_attitude_control
[ 63%] Built target launchdetection
[ 63%] Built target runway_takeoff
[ 63%] Built target modules__fw_pos_control
[ 64%] Built target modules__fw_rate_control
[ 65%] Built target drivers__gimbal
[ 65%] Built target modules__gyro_calibration
[ 67%] Built target modules__gyro_fft
[ 68%] Built target modules__land_detector
[ 68%] Built target modules__landing_target_estimator
[ 69%] Built target modules__load_mon
[ 70%] Built target modules__local_position_estimator
[ 71%] Built target modules__logger
[ 71%] Built target modules__mag_bias_estimator
[ 72%] Built target module__manual_control
[ 72%] Built target git_mavlink_v2
[ 72%] Built target mavlink_c_generate_uavionix
[ 74%] Built target modules__mavlink
[ 75%] Built target mavlink_c_generate
[ 75%] Built target modules__mavlink__mavlink_tests
[ 75%] Built target AttitudeControl
[ 76%] Built target modules__mc_att_control
[ 76%] Built target mc_autotune_attitude_control
[ 77%] Built target zero_order_hover_thrust_ekf
[ 77%] Built target modules__mc_hover_thrust_estimator
[ 77%] Built target PositionControl
[ 77%] Built target Takeoff
[ 77%] Built target modules__mc_pos_control
[ 77%] Built target modules__mc_rate_control
[ 77%] Built target geofence_breach_avoidance
[ 78%] Built target mission_feasibility_checker
[ 80%] Built target modules__navigator
[ 80%] Built target modules__payload_deliverer
[ 80%] Built target modules__rc_update
[ 81%] Built target modules__replay
[ 81%] Built target modules__rover_pos_control
[ 81%] Built target data_validator
[ 81%] Built target vehicle_acceleration
[ 81%] Built target vehicle_imu
[ 82%] Built target vehicle_air_data
[ 82%] Built target vehicle_angular_velocity
[ 82%] Built target vehicle_gps_position
[ 82%] Built target vehicle_magnetometer
[ 84%] Built target vehicle_optical_flow
[ 84%] Built target modules__sensors
[ 84%] Built target modules__simulation__battery_simulator
[ 85%] Built target modules__simulation__pwm_out_sim
[ 85%] Built target modules__simulation__sensor_airspeed_sim
[ 85%] Built target modules__simulation__sensor_baro_sim
[ 85%] Built target modules__simulation__sensor_gps_sim
[ 85%] Built target modules__simulation__senosr_mag_sim
[ 86%] Built target modules__simulation__simulator_mavlink
[ 86%] Built target modules__simulation__simulator_sih
[ 87%] Built target modules__temperature_compensation
[ 87%] Built target modules__uuv_att_control
[ 87%] Built target modules__uuv_pos_control
[ 88%] Built target modules__vtol_att_control
[ 88%] Built target systemcmds__actuator_test
[ 88%] Built target systemcmds__bsondump
[ 88%] Built target systemcmds__dyn
[ 89%] Built target systemcmds__failure
[ 89%] Built target systemcmds__led_control
[ 89%] Built target systemcmds__param
[ 89%] Built target systemcmds__perf
[ 89%] Built target systemcmds__sd_bench
[ 90%] Built target systemcmds__shutdown
[ 90%] Built target systemcmds__system_time
[ 93%] Built target systemcmds__tests
[ 94%] Built target systemcmds__tests__hrt_test
[ 94%] Built target systemcmds__topic_listener
[ 94%] Built target systemcmds__tune_control
[ 94%] Built target systemcmds__uorb
[ 95%] Built target systemcmds__ver
[ 95%] Built target systemcmds__work_queue
[ 95%] Built target modules__fake_gps
[ 95%] Built target modules__fake_imu
[ 95%] Built target examples__fake_magnetometer
[ 96%] Built target examples__hello
[ 96%] Built target examples__px4_mavlink_debug
[ 96%] Built target examples__px4_simple_app
[ 96%] Built target examples__work_item
[ 97%] Built target px4
[ 98%] Built target git_sitl_gazebo-classic
[ 98%] Performing build step for 'sitl_gazebo-classic'
[  6%] Built target std_msgs
[  6%] Built target physics_msgs
[  8%] Built target nav_msgs
[ 11%] Built target mav_msgs
[ 27%] Built target sensor_msgs
[ 29%] Built target klt_feature_tracker
[ 45%] Built target models_gen
[ 46%] Built target ForceVisual
[ 48%] Built target LiftDragPlugin
[ 49%] Built target AdvancedLiftDragPlugin
[ 52%] Built target gazebo_user_camera_plugin
[ 54%] Built target gazebo_groundtruth_plugin
[ 56%] Built target gazebo_sonar_plugin
[ 57%] Built target gazebo_lidar_plugin
[ 58%] Built target gazebo_random_velocity_plugin
[ 59%] Built target gazebo_camera_manager_plugin
[ 61%] Built target gazebo_opticalflow_mockup_plugin
[ 64%] Built target OpticalFlow
[ 65%] Built target gazebo_airspeed_plugin
[ 67%] Built target gazebo_airship_dynamics_plugin
[ 69%] Built target gazebo_uuv_plugin
[ 71%] Built target gazebo_vision_plugin
[ 72%] Built target gazebo_gimbal_controller_plugin
[ 73%] Built target gazebo_wind_plugin
[ 75%] Built target gazebo_imu_plugin
[ 77%] Built target gazebo_catapult_plugin
[ 78%] Built target gazebo_motor_model
[ 81%] Built target gazebo_mavlink_interface
[ 82%] Built target gazebo_multirotor_base_plugin
[ 83%] Built target gazebo_usv_dynamics_plugin
[ 85%] Built target gazebo_barometer_plugin
[ 87%] Built target gazebo_magnetometer_plugin
[ 89%] Built target gazebo_parachute_plugin
[ 90%] Built target gazebo_pose_sniffer_plugin
[ 91%] Built target gazebo_controller_interface
[ 92%] Built target gazebo_aruco_plugin
[ 94%] Built target gazebo_drop_plugin
[ 95%] Built target gazebo_gst_camera_plugin
[ 96%] Built target gazebo_gps_plugin
[ 97%] Built target gazebo_irlock_plugin
[ 98%] Built target gazebo_opticalflow_plugin
[100%] Built target gazebo_video_stream_widget
[ 98%] No install step for 'sitl_gazebo-classic'
[ 98%] Completed 'sitl_gazebo-classic'
[100%] Built target sitl_gazebo-classic
Scanning dependencies of target gazebo-classic_iris__empty
SITL ARGS
sitl_bin: /root/Firmware/build/px4_sitl_default/bin/px4
debugger: none
model: iris
world: empty
src_path: /root/Firmware
build_path: /root/Firmware/build/px4_sitl_default
GAZEBO_PLUGIN_PATH :/root/Firmware/build/px4_sitl_default/build_gazebo-classic
GAZEBO_MODEL_PATH :/root/Firmware/Tools/simulation/gazebo-classic/sitl_gazebo-classic/models
LD_LIBRARY_PATH :/root/Firmware/build/px4_sitl_default/build_gazebo-classic
Using: /root/Firmware/Tools/simulation/gazebo-classic/sitl_gazebo-classic/models/iris/iris.sdf
ALSA lib confmisc.c:767:(parse_card) cannot find card '0'
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_card_driver returned error: No such file or directory
ALSA lib confmisc.c:392:(snd_func_concat) error evaluating strings
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_concat returned error: No such file or directory
ALSA lib confmisc.c:1246:(snd_func_refer) error evaluating name
ALSA lib conf.c:4528:(_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
ALSA lib conf.c:5007:(snd_config_expand) Evaluate error: No such file or directory
ALSA lib pcm.c:2495:(snd_pcm_open_noupdate) Unknown PCM default
AL lib: (EE) ALCplaybackAlsa_open: Could not open playback device 'default': No such file or directory
not running gazebo gui
SITL COMMAND: "/root/Firmware/build/px4_sitl_default/bin/px4" "/root/Firmware/build/px4_sitl_default"/etc

______  __   __    ___
| ___ \ \ \ / /   /   |
| |_/ /  \ V /   / /| |
|  __/   /   \  / /_| |
| |     / /^\ \ \___  |
\_|     \/   \/     |_/

px4 starting.

INFO  [px4] startup script: /bin/sh etc/init.d-posix/rcS 0
INFO  [init] found model autostart file as SYS_AUTOSTART=10015
INFO  [param] selected parameter default file parameters.bson
INFO  [param] selected parameter backup file parameters_backup.bson
  SYS_AUTOCONFIG: curr: 0 -> new: 1
ERROR [param] Parameter UXRCE_DDS_KEY not found.
  SYS_AUTOSTART: curr: 0 -> new: 10015
  CAL_ACC0_ID: curr: 0 -> new: 1310988
  CAL_GYRO0_ID: curr: 0 -> new: 1310988
  CAL_ACC1_ID: curr: 0 -> new: 1310996
  CAL_GYRO1_ID: curr: 0 -> new: 1310996
  CAL_ACC2_ID: curr: 0 -> new: 1311004
  CAL_GYRO2_ID: curr: 0 -> new: 1311004
  CAL_MAG0_ID: curr: 0 -> new: 197388
  CAL_MAG0_PRIO: curr: -1 -> new: 50
  CAL_MAG1_ID: curr: 0 -> new: 197644
  CAL_MAG1_PRIO: curr: -1 -> new: 50
* SENS_BOARD_X_OFF: curr: 0.0000 -> new: 0.0000
* SENS_DPRES_OFF: curr: 0.0000 -> new: 0.0010
INFO  [dataman] data manager file './dataman' size is 7866640 bytes
etc/init.d-posix/rcS: 39: [: Illegal number:
INFO  [init] PX4_SIM_HOSTNAME: localhost
INFO  [simulator_mavlink] Waiting for simulator to accept connection on TCP port 4560
INFO  [simulator_mavlink] Simulator connected on TCP port 4560.
INFO  [lockstep_scheduler] setting initial absolute time to 1012000 us
INFO  [commander] LED: open /dev/led0 failed (22)
ERROR [param] Parameter UXRCE_DDS_DOM_ID not found.
etc/init.d-posix/rcS: 292: etc/init.d-posix/rcS: uxrce_dds_client: not found
INFO  [mavlink] mode: Normal, data rate: 4000000 B/s on udp port 18570 remote port 14550
INFO  [tone_alarm] home set
INFO  [mavlink] mode: Onboard, data rate: 4000000 B/s on udp port 14580 remote port 14540
INFO  [mavlink] mode: Onboard, data rate: 4000 B/s on udp port 14280 remote port 14030
INFO  [mavlink] mode: Gimbal, data rate: 400000 B/s on udp port 13030 remote port 13280
INFO  [logger] logger started (mode=all)
INFO  [logger] Start file log (type: full)
INFO  [logger] [logger] ./log/2024-06-12/17_30_47.ulg
INFO  [logger] Opened full log file: ./log/2024-06-12/17_30_47.ulg
INFO  [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO  [mavlink] MAVLink only on localhost (set param MAV_{i}_BROADCAST = 1 to enable network)
INFO  [px4] Startup script returned successfully
pxh> INFO  [tone_alarm] notify negative
INFO  [commander] Ready for takeoff!

It is working with both the QGC and MAVSDK python scripts using gazebo-jmavsim.

On which system are you running? Can you try the previous version, just to make sure:
docker run --rm -it jonasvautherin/px4-gazebo-headless:1.14.2

It is working with both the QGC and MAVSDK python scripts using gazebo-jmavsim.

On which system are you running? Can you try the previous version, just to make sure:
docker run --rm -it jonasvautherin/px4-gazebo-headless:1.14.2

I'm running on Ubuntu 22.04. 1.14.2 wasn't working either.
I suspected some issue with my docker setup and troubleshooted it. After setting the FORWARD chain policy to ACCEPT, it is working now for both 1.14.2 and 1.14.3.


Walk on the train without standing on a platform block

On beta-6 I can only get on a train when standing on a platform block. That makes sense but I have lots of platforms built on deserts, forests, etc. and the row of blocks one block from the train which should be platform blocks were replaced by other blocks to match the environment. So now I can't walk onto a train on those platforms. Could you please add an option to let us decide whether players should be on a platform block to enter a train?

for me, i use stone as floor or use carpets to cover the platform blocks
you can just put psd/apgs, also the use of platform block is for train doors to open

for me, i use stone as floor or use carpets to cover the platform blocks
you can just put psd/apgs, also the use of platform block is for train doors to open

Oh, you're right but I forgot to mention that those platform blocks were hidden one block under the platform to ensure train doors are open.
Yes the door will open in this way and that may be a bug but it does help to make the platform more customized.
Covering with carpets is a great solution in some cases. But humps on both sides of the platform still looks a bit strange.
Okay, I may be demanding here so it's only my ideas on the feature.

You can now place platform blocks on ground level and cover them up with one block.


Broken link "Azure Private Link service limitations"

The link Azure Private Link service limitations results in a 404.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b68f2c4-bb6c-11a2-6c61-8af4057a2438
Version Independent ID: e3498bed-1447-6841-8353-9f1b5d3dc8df
Content: Create a private Azure Kubernetes Service cluster - Azure Kubernetes Service
Content Source: articles/aks/private-clusters.md
Service: container-service
GitHub Login: @mlearned
Microsoft Alias: mlearned

@cdunford
Thanks for your feedback! We will investigate and update as appropriate.

Thanks! I made a pull request to fix this link. https://github.com/MicrosoftDocs/azure-docs-pr/pull/107743


🐛 Fix pivoting based e2e test file name

What this PR does / why we need it:
Renaming pivoting_based_feature_tests.go because at least Goland complains about a non test file (*tests.go, note the trailing s ) using a private function (e.g. validateGlobals())  of a test file (e2e_suite_test.go).
Introduced by #572
/cc @mboukhalfa @furkatgofurov7 @smoshiur1237

/ok-to-test

/test-v1b1-ubuntu-integration

/lgtm
Thanks for the fix


Proj4 dll is not copied with gdal libraries, making some gdal functions nonfunctional

for example, OCTTransform() function to transform coordinates from meters to lat/lon doesn't work. When I copied proj_4_9.dll to executable directory and renamed it to proj.dll, the transformation works.

See GDAL fails to load proj4_9.dll (#3258) for more details on where gdal attempts to load the wrong dll name.

Hi @RobertSpir , when GDAL is exported, the headers and library of proj4 will also be exported.
So, the only problem is that the library for proj4 needs to be renamed to proj.dll?

GDAL loading proj dynamic library mode is dynamically loaded(using load_library), so the project using gdal can NOT add proj.dll to the list of libraries that must be dependent on the build, which caused vcpkg to fail to copy proj.dll to the build folder depending on the dependencies.

Hi @RobertSpir, thanks for reporting this issue.
I've fixed this issue now, please update vcpkg and rebuild gdal.
Thanks.


[Feature] Add ms-stft and ms-sb-cqt discriminators

Thanks for very cool project.
This is the best and simple LLM-based TTS Implementation I have ever seen!
For audio quality, I highly recommend adding MS-STFT Discriminator of Encodec, and MS-SB-CQT Discriminator (https://arxiv.org/abs/2311.14957).
When using above discriminators, I have experienced a better audio quality for this kind of autoencoder model.
Thanks!

Hi, we are testing different discriminators in another project, which includes these two discrimiantors and also the loss balancer introduced by encodec. If the experiment shows great improvment, we will definitely merge the updates into this repo.

Will you suggest keeping mpd and mrd (which uses 4 discriminator) or using ms-stft and ms-sb-cqt only?

I suggested keeping mpd and msd!
Although some objective metrics could be decreased, MPD is very important for perceptual audio quality.

In that case, that's basically following Amphion's solution here.

Added to: https://github.com/fishaudio/fish-speech/tree/vqgan-v2 Still testing though.

@leng-yue  Consider using RVQ? it shows good performance

@lucasjinreal
RVQ is already used in vq encoder. When I check config, they already utilized 4 codebooks.

@sh-lee-prml thank u for point it out, is that same arch with RVQ?

@lucasjinreal
Yes same
You can see the details in this repo
https://github.com/fishaudio/fish-speech/blob/main/fish_speech/models/vqgan/modules/encoders.py
https://github.com/lucidrains/vector-quantize-pytorch/blob/master/vector_quantize_pytorch/residual_vq.py
You can also utilize the GroupedRVQ like HiFi-Codec (https://github.com/yangdongchao/AcademiCodec)
@leng-yue
I have some questions for this.

Have you compared the performance for RVQ and GroupedRVQ?

and I think that although RVQ or GroupedRVQ could improve the audio quality, RVQ could affect the performance of LLM model because the increased sequences make it difficult to predict the next token, and increases the memory and inference speed. So, I do not prefer to use the RVQ for audio codec actually.

Alternatively, the prob. RVQ of CLaM-TTS (https://openreview.net/forum?id=ofzeypWosV) may resolve this issue even with RVQ.

We observed that GVQ is better than RVQ in this task, we think that's because its codebook doesn't have a residual structure (codebook 0 is most important, 1 is less important, etc). So in the next version of VQ-GAN, we will also use the GVQ with 4 codebooks, but with larger codebook size.

@leng-yue  Does the speed slowered much? Will it runs in reasonable speed on CPU?

Fish Speech is not designed for CPU.

We also observed that adding ms-stft and ms-sb-cqt doesn't bring significant improvment comparing to mpd + mrd in our objective and subjective tests. Thus, the vqgan-v2 only uses mpd and mrd.


Gradle build failed.

when I use the 26 version of the Android Support Libraries, it failed to build.
    compile 'com.android.support:appcompat-v7:26.+'
    compile 'com.wdullaer:materialdatetimepicker:3.2.2'

if i commented  compile 'com.wdullaer:materialdatetimepicker:3.2.2',it works well.

The current published version of the library depends on an older version of the support library.
Java cannot use 2 different versions of the same package namespace, so this could generate an error.
Try adding this clause from the README in your build.gradle
https://github.com/wdullaer/MaterialDateTimePicker#how-do-i-use-a-different-version-of-the-support-library-in-my-app
That way, the version of the support library from materialdatetimepicker won't be used.
Alternatively, you can wait until I publish a version that depends on a newer version of the support library.

v3.2.3 uses support library v26.0.1, which should fix your build

Can you update it to 26.1.0. I still have issues even after addding
compile ('com.wdullaer:materialdatetimepicker:3.3.1') {         exclude group: 'com.android.support' } in gradle.

That exclude statement should work. Exactly which error are you getting?

I'm getting the foolowing error in console Error:Execution failed for task ':app:processDebugManifest'.

Manifest merger failed : Attribute meta-data#android.support.VERSION@value value=(26.0.1) from [com.android.support:support-v13:26.0.1] AndroidManifest.xml:28:13-35
is also present at [com.android.support:customtabs:26.1.0] AndroidManifest.xml:25:13-35 value=(26.1.0).
Suggestion: add 'tools:replace="android:value"' to  element at AndroidManifest.xml:26:9-28:38 to override.

Are you sure there are no other dependencies with subdependencies on the support library (such as firebase)?
Are you explicitly declaring MaterialDateTimePickers support library dependencies in your app? (all of them need to be there)


missing update() method in Groups

looks like Groups::update() was not implemented. see PR #151

closing as the PR was merged.


Changes to einsum

Adds support for BLAS-like alpha, beta parameters to einsum along with out. Also adds contraction using TBLIS via pyscf-tblis.

Codecov Report
Patch coverage: 74.41% and project coverage change: -0.05 :warning:

Comparison is base (f877067) 99.54% compared to head (56e915e) 99.50%.

:exclamation: Current head 56e915e differs from pull request most recent head dbcd9f4. Consider uploading reports for the commit dbcd9f4 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #16      +/-   ##
==========================================
- Coverage   99.54%   99.50%   -0.05%
==========================================
  Files          50       50
  Lines       76007    76139     +132
  Branches      656      611      -45
==========================================
+ Hits        75663    75762      +99
- Misses        234      261      +27
- Partials      110      116       +6

Impacted Files
Coverage Δ

ebcc/util.py
72.42% <74.41%> (+0.99%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


PPP: Draft Dexter

Codecov Report

Merging #253 (7dfb08b) into master (52d764c) will decrease coverage by 1.96%.
The diff coverage is 71.72%.

@@             Coverage Diff              @@
##             master     #253      +/-   ##
============================================
- Coverage     72.15%   70.19%   -1.97%
- Complexity      399      900     +501
============================================
  Files            70      129      +59
  Lines          1232     2741    +1509
  Branches        125      360     +235
============================================
+ Hits            889     1924    +1035
- Misses          311      613     +302
- Partials         32      204     +172

Impacted Files
Coverage Δ

src/main/java/taskbook/AppParameters.java
75.00% <ø> (ø)

src/main/java/taskbook/Main.java
0.00% <ø> (ø)

src/main/java/taskbook/MainApp.java
0.00% <0.00%> (ø)

src/main/java/taskbook/commons/core/Config.java
68.18% <ø> (ø)

...c/main/java/taskbook/commons/core/GuiSettings.java
69.23% <ø> (ø)

...rc/main/java/taskbook/commons/core/LogsCenter.java
78.37% <ø> (ø)

src/main/java/taskbook/commons/core/Messages.java
0.00% <ø> (ø)

src/main/java/taskbook/commons/core/Version.java
82.50% <ø> (ø)

...c/main/java/taskbook/commons/core/index/Index.java
100.00% <ø> (ø)

...ok/commons/exceptions/DataConversionException.java
100.00% <ø> (ø)

... and 123 more

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


[Examples] Add off-the-shelf tensorflow example

Coverage increased (+4.7%) to 50.747% when pulling a5c5a70f5bb12d81f56685f1da081056056260ea on xiongyf/add-tf-examples into a7a719e7fe0b8e5be4758f6085cf3c601e17fca0 on master.

can you add a readme.md in /examples/? and highlight that if user would like to play with PAI, just copy the json you add in this PR and submit to PAI cluster.


Obsolete scope attribute in table docs examples.

As of now in docs section regarding tables there is such an example:

      #
      First
      ...

MDN says scope attribute is marked as obsolete in HTML5.
Shouldn't it be removed from example in the docs?

scope is obsoleted on  cells only. NOT on  cells. see https://developer.mozilla.org/en-US/docs/Web/HTML/Element/th / https://www.w3.org/TR/html53/obsolete.html#non-conforming-features


How to combine with existing express server?

I need to implement the TURN server along with existing express server. How can I do that without listening on different ports?

impossible as node-turn only support upd for now and http use tcp...


/api/v1/model/metrics/ response is empty

I am running heapster and I can see the metrics flowing to influxdb. But when I try to access the metrics using the following endpoint http://{master-ip}/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/metrics/ I get empty response. Same goes with /api/v1/model/namespaces/ and /api/v1/model/nodes/{node-name}/metrics
I use the following parameters  "--use_model=true","--model_resolution=1m". Any help here is really appreciated.

cc @afein

Do you get any response when accessing http://{master-ip}/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/?
Also, could you tell us the heapster version you're using through kubectl logs <heapster-pod>?

Yes, I do get response for http://{master-ip}/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/model/
[   "metrics/",   "namespaces/",   "nodes/" ]
Heapster version 0.17.0
I do see these errors in the log
W0827 03:52:04.018268       1 impl.go:515] Internal Error: reached unreachable CPU Usage parsing flow W0827 03:52:04.018483       1 impl.go:515] Internal Error: reached unreachable CPU Usage parsing flow W0827 03:52:04.018612       1 impl.go:515] Internal Error: reached unreachable CPU Usage parsing flow E0827 03:52:04.021118       1 util.go:69] Recovered from panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference) /usr/local/google/home/vishnuk/go/src/github.com/GoogleCloudPlatform/heapster/Godeps/_workspace/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:63 /usr/local/google/home/vishnuk/go/src/github.com/GoogleCloudPlatform/heapster/Godeps/_workspace/src/github.com/GoogleCloudPlatform/kubernetes/pkg/util/util.go:54 /usr/lib/google-golang/src/runtime/asm_amd64.s:401 /usr/lib/google-golang/src/runtime/panic.go:387 /usr/lib/google-golang/src/runtime/panic.go:42

Edited the last comment to fix formatting.
@sanjana-bhat for multiline quotes, to keep newlines, use triple backquotes.

Thanks @mvdan
@afein, is there something that I'm missing for the APIs to work?

Hey @sanjana-bhat, sorry for the delay. The internal error is actually not supposed to occur outside of unit tests, which is quite confusing. It represents a case where your CPU usage metrics are actually flowing into the heapster model backwards in time.
We are currently in the process of refactoring the underlying codebase of the APIs (#478) so this issue might only affect v0.17.0.
Can you try deploying heapster using the docker image located at afein/heapster-model:latest?
If your setup is still not operational with that docker image then the underlying problem would be related to your deployment environment, which we can try to dig into further.
If your setup does becomes operational with that docker image then the underlying problem will be fixed in the next heapster release.
Also, can you post the replication controller file that you are using to spawn heapster?

Heapster RC:
{
    "apiVersion": "v1",
    "kind": "ReplicationController",
    "metadata": {
        "labels": {
            "k8s-app": "heapster",
            "name": "heapster",
            "version": "v6"
        },
        "name": "heapster",
        "namespace": "kube-system"
    },
    "spec": {
        "replicas": 1,
        "selector": {
            "k8s-app": "heapster",
            "version": "v6"
        },
        "template": {
            "metadata": {
                "labels": {
                    "k8s-app": "heapster",
                    "version": "v6"
                }
            },
            "spec": {
                "containers": [
                    {
                        "image": "kubernetes/heapster:v0.17.0",
                        "name": "heapster",
                        "command": [
                            "/heapster",
                            "--source=kubernetes:http://{k8s-master-host}:6443?inClusterConfig=false&auth=",
                            "--sink=influxdb:http://monitoring-influxdb:8086",
                            "--use_model=true",
                            "--model_resolution=1m"
                        ],
                        "ports": [
                            {
                                "containerPort": 8082
                            }
                        ]
                    }
                ]
            }
        }
    }
}

I will try with the docker image located at afein/heapster-model:latest

@afein, I still see the same errors
W0901 01:44:30.442023       1 impl.go:171] failed to parse ContainerMetricElement: failed to add cpu-limit metric: failed to add metric to DayStore: the provided timepoint has a timestamp in the past
W0901 01:44:30.445863       1 impl.go:171] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value 0 is less than the previous one<PHONE_NUMBER>88
W0901 01:44:30.446051       1 impl.go:171] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value 0 is less than the previous one<PHONE_NUMBER>09
W0901 01:44:30.446162       1 impl.go:171] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value 0 is less than the previous one<PHONE_NUMBER>52
W0901 01:44:30.446275       1 impl.go:171] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value 0 is less than the previous one<PHONE_NUMBER>47
E0901 01:44:30.446528       1 util.go:69] Recovered from panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
E0901 01:46:07.622115       1 kube_events.go:127] failed to store events in cache: failed to store event {{NodeReady default  %node% map[] } Node %node% status is now: NodeReady kubelet 2015-09-01 01:35:30 +0000 UTC {{ } {%node%.13ffb6bd3e5c0336  default /api/v1/namespaces/default/events/%node%.13ffb6bd3e5c0336  333599 0 0001-01-01 00:00:00 +0000 UTC 2015-09-01 02:35:30 +0000 UTC map[] map[]} {Node  %node% %node%   } NodeReady Node %node% status is now: NodeReady {kubelet %node%} 2015-09-01 01:35:29 +0000 UTC 2015-09-01 01:35:30 +0000 UTC 2}} - UID cannot be empty

Heapster service file:
{
    "apiVersion": "v1",
    "kind": "Service",
    "metadata": {
        "labels": {
            "kubernetes.io/cluster-service": "true",
            "kubernetes.io/name": "Heapster"
        },
        "name": "heapster",
        "namespace": "kube-system"
    },
    "spec": {
        "ports": [
            {
                "port": 8082,
                "targetPort": 8082
            }
        ],
        "selector": {
            "k8s-app": "heapster"
        }
    }
}

There seems to be some sort of issue with the data that is being scraped from the nodes.
 Also I explicitly create kube-system namespace as that was missing in etcd. After this, only /api/v1/model/nodes/%node%/stats/ returns me non-empty response. All the other endpoints including /api/v1/model/metrics return empty response.
{
  "uptime":<PHONE_NUMBER>4486179580,
  "stats": {
   "cpu-limit": {
    "minute": {
     "average": 2000,
     "percentile": 2000,
     "max": 2000
    },
    "hour": {
     "average": 2000,
     "percentile": 2000,
     "max": 2000
    },
    "day": {
     "average": 2000,
     "percentile": 2000,
     "max": 2000
    }
   },
   "cpu-usage": {
    "minute": {
     "average": 255,
     "percentile": 255,
     "max": 255
    },
    "hour": {
     "average": 913,
     "percentile": 1590,
     "max": 1650
    },
    "day": {
     "average": 1085,
     "percentile": 1650,
     "max": 1650
    }
   },
   "fs-limit-dev-vda": {
    "minute": {
     "average":<PHONE_NUMBER>6,
     "percentile":<PHONE_NUMBER>6,
     "max":<PHONE_NUMBER>6
    },
    "hour": {
     "average":<PHONE_NUMBER>0,
     "percentile":<PHONE_NUMBER>0,
     "max":<PHONE_NUMBER>0
    },
    "day": {
     "average":<PHONE_NUMBER>0,
     "percentile":<PHONE_NUMBER>0,
     "max":<PHONE_NUMBER>0
    }
   },
   "fs-usage-dev-vda": {
    "minute": {
     "average":<PHONE_NUMBER>9,
     "percentile":<PHONE_NUMBER>0,
     "max":<PHONE_NUMBER>0
    },
    "hour": {
     "average":<PHONE_NUMBER>4,
     "percentile":<PHONE_NUMBER>0,
     "max":<PHONE_NUMBER>0
    },
    "day": {
     "average":<PHONE_NUMBER>0,
     "percentile":<PHONE_NUMBER>0,
     "max":<PHONE_NUMBER>4
    }
   },
   "memory-limit": {
    "minute": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "hour": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "day": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    }
   },
   "memory-usage": {
    "minute": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "hour": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "day": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    }
   },
   "memory-working": {
    "minute": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "hour": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    },
    "day": {
     "average":<PHONE_NUMBER>,
     "percentile":<PHONE_NUMBER>,
     "max":<PHONE_NUMBER>
    }
   }
  }

@afein and @vishh
I increased the log level and noticed the model data structure is not being updated because of the following warnings "Internal Error: reached unreachable CPU Usage parsing flow" and hence no metrics seem to be added. After debugging I found out that prevRoundedStamp and roundedStamp values are the same and the following condition https://github.com/kubernetes/heapster/blob/master/model/impl.go#L541 is false most of the time.
I use the default poll_duration and stats_resolution values whereas model_resolution is set to 2m. Any changes that I need to do to fix this?

From my understanding, it appears that heapster is constantly reading 0 for cpu usage while parsing model data.
Can you try accessing
http://{master-ip}/api/v1/proxy/namespaces/kube-system/services/heapster/api/v1/metric-export and searching for cpu/usage values that are zero?

@afein, it does seem that way. But cpu/usage values are zero only for specific containers under /system.slice cgroup. But this shouldn't cause the API to return empty response at the cluster, node or namespace level right? Not all values are zero.
May be add a condition here https://github.com/kubernetes/heapster/blob/master/model/impl.go#L530 if(ok) so that nil pointer dereference doesn't occur?
Here is a sample response from the above API call:
[
    {
        "labels": {
            "container_base_image": "",
            "container_name": "k8s_etcd.aa8dfebb_kube-dns-v8-kfmsf_kube-system_86936fe4-5207-11e5-9c3e-fa163e56b235_39cdc306",
            "host_id": "illusioninfusion",
            "hostname": "illusioninfusion"
        },
        "metrics": {
            "cpu/limit": [
                {
                    "start": "2015-09-03T18:41:39Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 99
                }
            ],
            "cpu/usage": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value":<PHONE_NUMBER>51
                }
            ],
            "memory/limit": [
                {
                    "start": "2015-09-03T18:41:39Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 52428800
                }
            ],
            "memory/major_page_faults": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 63
                }
            ],
            "memory/page_faults": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 12408
                }
            ],
            "memory/usage": [
                {
                    "start": "2015-09-03T18:41:39Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 19165184
                }
            ],
            "memory/working_set": [
                {
                    "start": "2015-09-03T18:41:39Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 12181504
                }
            ],
            "network/rx": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 0
                }
            ],
            "network/rx_errors": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 0
                }
            ],
            "network/tx": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 0
                }
            ],
            "network/tx_errors": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 0
                }
            ],
            "uptime": [
                {
                    "start": "2015-09-03T06:46:50Z",
                    "end": "2015-09-03T18:41:39Z",
                    "value": 42900007
                }
            ]
        }
    },
    {
        "labels": {
            "container_base_image": "",
            "container_name": "/system.slice/mdmonitor.service",
            "host_id": "illusioninfusion",
            "hostname": "illusioninfusion"
        },
        "metrics": {
            "cpu/limit": [
                {
                    "start": "2015-09-03T18:41:33Z",
                    "end": "2015-09-03T18:41:33Z",
                    "value": 1000
                }
            ],
            "cpu/usage": [
                {
                    "start": "2015-09-02T18:48:42Z",
                    "end": "2015-09-03T18:41:33Z",
                    "value": 0
                }
            ],
            "uptime": [
                {
                    "start": "2015-09-02T18:48:42Z",
                    "end": "2015-09-03T18:41:33Z",
                    "value": 85988219
                }
            ]
        }
    }
]

@sanjana-bhat I added such a condition on #508, which is planned to be merged shortly.

@afein, I pulled in this condition in my heapster docker image and I see non-empty response for /metrics. Has /stats being removed recently? I built the docker image from the master branch.

@sanjana-bhat yes, the /stats endpoint has been removed temporarily to facilitate code review. It will be reintroduced in a future PR and it is definitely going to be included in the next heapster release.
Is everything else fully operational?

Great! Yes, everything looks okay now. Thanks!

@afein, when is the next heapster release? Can I expect these changes to be a part of that?

The /stats endpoints were merged today in master, so you should be able to access the full feature set by building the current HEAD.
I am not aware about the exact date of the next release (\cc @vishh), but any further changes until that release would most probably involve internal quality

We are waiting on the issues that are part of this
milestone to be resolved before making a new release.
On Tue, Sep 8, 2015 at 8:01 PM, Alexandros Mavrogiannis <
<EMAIL_ADDRESS>wrote:

The /stats endpoints were merged today in master, so you should be able to
access the full feature set by building the current HEAD.
I am not aware about the exact date of the next release (\cc @vishh
https://github.com/vishh), but any further changes until that release
would most probably involve internal quality
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/501#issuecomment-138762644
.

@afein, /stats gives average, max and 95th percentile over the past minute. Suppose time now is 23:30, /stats returns average for 23:29?

As of now, the model is updated roughly every 2.5 * model_resolution (which defaults to 2.5 minutes).
This means that the latest data available through both /stats and /metrics is the average for the last minute that is stored, which could be either 23:28, 23:29 or 23:30. If you are interested in the exact time, you can invoke the /metrics endpoint as well

I have specified model_resolution to 1 min. Is that considered or it always takes default?

The model_resolution flag is always considered, however 1 min is also the default value for model_resolution (https://github.com/kubernetes/heapster/blob/master/heapster.go#L43).

@afein and @vishh, what are the recommended resource specifications for heapster container?

I would suggest providing 300MB of memory and 0.2 cores for Heapster to
begin with. If you see heapster getting closer to these limits, let me
know. Disk space should not be of concern since heapster is currently
stateless.
On Thu, Sep 17, 2015 at 10:45 AM, Sanjana J Bhat<EMAIL_ADDRESS>wrote:

@afein https://github.com/afein and @vishh https://github.com/vishh,
what are the recommended resource specifications for heapster container?
—
Reply to this email directly or view it on GitHub
https://github.com/kubernetes/heapster/issues/501#issuecomment-141163798
.

I'm closing this issue. @sanjana-bhat feel free to re-open if I failed to address any concerns.

@vishh I'm using heapster 0.19.0 in k8s 1.2.0 and getting this error couple times in a few days
...
W0420 04:09:44.699088       1 impl.go:225] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value<PHONE_NUMBER>96 is less than the previous one<PHONE_NUMBER>49
W0420 04:09:44.699281       1 impl.go:225] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value<PHONE_NUMBER>12 is less than the previous one<PHONE_NUMBER>49
W0420 04:09:44.699440       1 impl.go:225] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value<PHONE_NUMBER>73 is less than the previous one<PHONE_NUMBER>49
W0420 04:09:44.699537       1 impl.go:225] failed to parse ContainerMetricElement: failed to calculate instantaneous CPU usage: the provided value<PHONE_NUMBER>55 is less than the previous one<PHONE_NUMBER>49
...

heapster pod yaml config:
...
- image: kubernetes/heapster:v0.19.0
  name: heapster
  resources:
    limits:
      memory: 300Mi
  ports:
    - name: heapster-api
      containerPort: 8082
      hostPort: 8082
  command:
    - /heapster
    - --source=kubernetes:http://api-server:8080
    - --sink=influxdb:http://influxdb-server:8086
    - --stats_resolution=10s
    - --sink_frequency=15s
...

heapster stop sending metrics to influxdb when this error occurred unless I restart the container.
So please help me more clear on the problem. Is it an async problem between cadvisor and heapster?


Replace OpenStruct dependency with Struct

Instead of reverting #2754 since it will still fail, this is a new attempt at replacing the OpenStruct dependency with a Struct from this suggestion: https://github.com/rspec/rspec-rails/pull/2754#discussion_r1556524959

@pirj this is ready and looking good. Can you please re-run the failed CI jobs? Those should pass. Reviewing each, it's the same failure and I've seen on other builds so either a flaky and/or unrelated. Thank you for the suggestion. It's better than depending on OpenStruct.

Thank you. This is indeed much better.


Added Eq instance for GenericSignature

It compiles for me and the very basic tests pass.

@paf31 how's this one now? I'll incorporate it in the RC if you're happy with it now.

:+1: Looks good to me, thanks!


Confusing naming of Message

What is called Message in pydifact is not a message in EDIFACT sense of the term.
This is realy confusing.
As pydifact does not currently handle Message Interchange and Functional group objects.
Here are some ways how pydifact.message.Message could be renamed IMHO :

pydifact.document.Document : "document" word as no meaning in EDIFACT
pydifact.SegmentCollection would be the more accurate

I know this is painful (because breaking retro-compatibility).
I could be interested (I have my own interest into doing that) into implementing those containers into pydifact, but this bug is a blocker for that.

This is a good idea. backwards compatibility is no problem, we are at v0.0.5, and it's stated as "eats-your-dog" software. So yes, Document is a great idea.
I don't have time just now - If you want you can try hat @JocelynDelalande ? I would need a few weeks maybe until I find time again for that change. If you make it faster, just tell me (if you start on that) - so we don't do it across... ;-)
Oh, and implementing that containers - no problem - please tell me a bit about them (and maybe your interests?) - I had a vague concept about implementing containers - I just want to check if yours is compatible with mine...

Yes, I will definitively give it a shot ; I have a data structure scheme already in mind :).
But thinking about it, I wonder wether it is a good idea to keep the the Document (current Message) notion or not. Rationale : the Interchange and Message wrapping is mandatory in EDIFACT, there will never be a group of segments "out in the wild".
WDYT on this point @nerdoc  ?

Message/Document is not a nessicity, no. As stated, I just "transcoded" pydifact from a PHP lib which was IMHO very structured, so I took the structures too. The original php library AFAIK went away from this abstracted OOP syntax and went to a (faster) procedural parsing.
I am not inclined following this approach, as I think that, although it may be a bit faster, this is not the main purpose of a python lib. If I need speed on a low-end device, I'd have to use C/C++ etc. anyway, and no language with a GC and a runtime engine.
But, again, Message (Document) is not strictly necessary as bbject.
OTOH: I read the standard you linked above - and (please correct me) as far as I understand, this means that a (official) "message" means the segments between the message header (i.e. UNA) and the message trailer (UNT). So, e.g.
UNA...
  UNH
    {Message}
  UNS
UNT

meaning "message" is the inner part, not the whole thing, right?

An interchange of data in the context of EDIFACT, is composed of
one or more messages containing segments which in turn are made
up of data elements.

Maybe "Interchange" would be the best name then?

In OSI terms, a connection could include one or more EDIFACT
interchanges, each separated from the other by control service
segments which identify the start and end of each interchange.
Within each interchange, there is then a hierarchical structure
which allows for both control and identification of data for
processing.  This structure is shown in Section 6 of ISO 9735.

In an UN/EDIFACT interchange,
everything from the first character of the Interchange Control
Header segment to the last character of the Interchange Control
Trailer segment, is user data,...

I found another implementation doc from Microsoft here:
Interchange
   Group
      Transaction set/message
         Segment
            Data Element
               Sub Element

So InterchangeIMHO would be a good name for the whole thing?

So InterchangeIMHO would be a good name for the whole thing?

:+1: that is mandatory, and there should not be more than 1, so Interchange is the good 1st-level element.

meaning "message" is the inner part, not the whole thing, right?

Yes

And speaking about references, I found http://www.gxs.co.uk/wp-content/uploads/tutorial_edifact.pdf to be a good introduction, and it has nice schematics. Like :

(but be carefull, even if it is OK for most of it, it does not always use the exact accurate words to name things)

This is a great picture, never saw this. I even didn't know that there could be more than one messages in a group until a few days ago.

Hm. I think about testing.
def test_get_segment():
    message = Message.from_segments([Segment("36CF", 1), Segment("36CF", 2)])
    segment = message.get_segment("36CF")
    assert Segment("36CF", 1) == segment

Here Envelope or Interchange makes no sense. Even if under testing umbrella everything is a bit different.
But here it doesn't need to be an Envelope, nor a complete Interchange. in this context Message  is just a sequence of Segments - which in fact never exists in real life.
Under this circumstances your idea  SegmentCollection would be a good name, or Sequence.
@JocelynDelalande your opinion?

Yes, let's use SegmentCollection : Sequence would give the false impression that it is a word with a  meaning in EDIFACT world, which is untrue. btw, this should also be the same Envelope or AbstractSegmentContainer from #19, no ?

I renamed it to SegmentCollection.

Ah, yes, #19 should be the same. Let's talk there further.


Request to update d3-array dependency from 2.12.1 to 3.0.1

I get a build error since upgrading typescript.
I believe your dependency on an old version of d3-array is the culprit.
If you could cast a new version of react-wordcloud, upgrading the dependency on at least this 1 library, it'd be great.
Happy to help test.
Thanks!!
https://www.npmjs.com/package/d3-array

I believe d3-scale would also need to be upgraded... perhaps it is safe to update all d3 dependencies to their latest versions.
Thanks again.

It seems the repo is no longer maintained. I've created a fork that works with latest D3 libs. Let me know if it you have any issues with it.
ahmohamed/react-wordcloud

It seems the repo is no longer maintained. I've created a fork that works with latest D3 libs. Let me know if it you have any issues with it.
ahmohamed/react-wordcloud

This is saving my life! I wonder if you have or could make it available on NPM? Thanks!

If someone else stumble upon issues with outdated d3 dependencies. Please feel free to use https://www.npmjs.com/package/react-wordcloud-d3-update-fork


Revise client_impl.py's handling of private-api errors

Per zoom discussion w @wasade @dhakim87 @AmandaBirmingham on 20200605:

Rewrite ApiRequest._check_response so that it raises custom exceptions for 401/403 and for other 400+s, and so that it returns only the successful api result (instead of a tuple)

Note: the one case where the header is also needed is going to have to be handled somehow but we didn't decide yet how

Set up flask handlers for those custom exceptions to either redirect to home url (for 401/403) or return client error page (for all other 400+s)
Modify all code that calls ApiRequest get/post/etc to no longer do the if needs_reroute then: return output check after every such call--no longer needed!

Note: I just transferred this which seems to trigger an email notification -- sorry about that


Support WALRUS (Postgres RLS) Integration with Realtime Server

Feature request
Is your feature request related to a problem? Please describe.
Currently, Realtime server sends all database changes to all connected clients despite Postgres Row Level Security policies. This poses security concerns when developers wish to broadcast database changes containing sensitive data to an authorized subset of connected clients based on tables with RLS enabled and row security policies.
Realtime server will integrate WALRUS (Write Ahead Log Realtime Unified Security), which means there are some changes that lib clients need to make in order to support this new security functionality.
Describe the solution you'd like
The following changes will need to be made:

Pass user auth token, if available, as channel params with key user_token when subscribing client to Realtime channel.
Update Realtime transformers to pass through changes when they're already arrays.
Realtime w/ WALRUS will pass Postgres array types as [1, 2, 3], _int4, and ["a", "b", "c"], _text, instead of "{1,2,3}" (_int4/_text) so this can be forwarded without any transformations. However, clients should maintain backward compatibility so they should still be able to handle stringified Postgres array (e.g. "{1,2,3}") cases.

The changes have already been applied to supabase-js and realtime-js and their PRs can be referenced while making the necessary changes:

Passing user auth token as user_token

feat: add user_token when creating realtime channel subscription #270

Update Realtime transformers (including bug fixes)

feat: update transformers to accept already transformed walrus changes #107
fix: error parsing JSON when transforming array data types #113
The bug fixes include longstanding issues with transformers in realtime-js where range types are first JSON parsed (which results in an error sometimes due to Postgres' range exclusive and inclusive bounds) and how stringified (e.g. "{1,2,3}") array types are split (can't always split on "," in cases like _daterange). Please see PR for additional context.
Additional context
We're looking to launch WALRUS in Realtime at the end of November, and all developers using the JS client will have to do is version bump their supabase-js to v1.2.0, which contains all the changes described above.
Please reach out if there's any questions and definitely tag me to confirm PRs if you'd like! Thank you!

It's been a while since this was posted. Just adding context here in case anyone ones to pick this up -- off the top of head things we need to get this in.

Patch realtime-py so that the installation works across platforms
Update GoTrue-py to be able to notify all subscribers when events come in
Convert Supabase-py to run realtime-py on a separate thread or process so that realtime-py can run concurrently with the rest of the libs.

There are probably more tasks as well feel free to add/comment below

We need some more discussion on the implementation of realtime-py. Imo we should only provide an async interface (because the underlying websockets stuff is inherently async). Right now we do some hacky wrap-every-async-call stuff but I think that'd just be an easy spot for bugs to arise, and if we expose that as public API we'd be obligated to provide support for it.

I'll open up a doc or a thread of sorts for further discussion


⚠ Bofrost.at has degraded performance

In 549d213, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1511 ms

Resolved: Bofrost.at performance has improved in 217d987.