[FLINK-5256] Extend DataSetSingleRowJoin to support Left and Right joins

add support outer joins with single record via DataSetSingleRowJoin
Thanks for contributing to Apache Flink. Before you open your pull request, please take the following check list into consideration.
If your changes take all of the items into account, feel free to open your pull request. For more information and/or questions please refer to the How To Contribute guide.
In addition to going through the list, please provide a meaningful description of your changes.

[x] General

The pull request references the related JIRA issue ("[FLINK-XXX] Jira title text")
The pull request addresses only one issue
Each commit in the PR has a meaningful commit message (including the JIRA id)

[ ] Documentation

Documentation has been added for new functionality
Old documentation affected by the pull request has been updated
JavaDoc for public methods has been added

[x] Tests & Build

Functionality added by the pull request is covered by tests
mvn clean verify has been executed successfully locally or a Travis build has passed

Hi,
outer joins with single record is supported via DataSetSingleRowJoin and simultaneously outer joins with many  records is supported via DataSetJoin

Hi @fhueske. I updated PR. Please look my changes. Thanks!


v1.26.0 release issue

Is this a BUG REPORT or FEATURE REQUEST?
BUG
Choose one: BUG REPORT or FEATURE REQUEST

Versions
CCM Version: v1.26.0
Environment:

Kubernetes version (use kubectl version): v1.26.6
OS (e.g. from /etc/os-release): ubuntu
Kernel (e.g. uname -a):
Others:

What happened?
Unable to use kubectl apply -f https://github.com/oracle/oci-cloud-controller-manager/releases/download/v1.26.0/oci-cloud-controller-manager.yaml. The SPEC has
containers:
        - name: oci-cloud-controller-manager
          image: ghcr.io/oracle/cloud-provider-oci:latest

This causes an imagepullbackoff. I believe it should be
containers:
        - name: oci-cloud-controller-manager
          image: ghcr.io/oracle/cloud-provider-oci:v1.26.0

After setting the correct version I was able to get my cluster up.
What you expected to happen?
I expected the oci-cloud-controller-manager pod to move into running state
How to reproduce it (as minimally and precisely as possible)?
Should be able to repro it by appling the released v1.26.0 version of oci-cloud-controller-manager.yaml to a cluster and watch for the imagepullpackoff.
Anything else we need to know?

I believe the assets for v1.26.0 have been updated and it looks like it is now working. I'll close this issue.


No such module 'Realm' - Error on Catalina (10.15.7)

No such module 'Realm' - Error on Catalina (10.15.7)
Goals
Integrate Realm as a binary framework (xcframework) in Swift Package Manager
Expected Results
The code is expected to compile.
The same works on BigSur but not on Catalina
Actual Results
I get an error during build - "No such module 'Realm'"
Steps for others to Reproduce

Downloaded the package from: Realm-Git - 10.10.0
On console, navigate to the realm source code (../realm-cocoa-master)
sh build.sh help - Should show list of all the options
sh build.sh clean
sh build.sh xcframework osx

xcframework successfully written out to: /realm-cocoa-master/build/Realm.xcframework
xcframework successfully written out to: /realm-cocoa-master/build/RealmSwift.xcframework
Added the depdency to XCFramework in package.swift
.binaryTarget(name: "Realm", path: "Dependencies/Realm.xcframework"),
.binaryTarget(name: "RealmSwift", path: "Dependencies/RealmSwift.xcframework"),
Package build fails. (The same works on BigSur). I re-built the framework on Catalina to make sure there aren't any compatibility issues.
Version of Realm and Tooling
Realm framework version: 10.10.0
Xcode version: Version 12.3 (12C33)
iOS/OSX version: 10.15.7

Hi @ravikirankhareedi just to be clear, on Catalina the XCFramework build succeeds, just the failure is when you try to build the swift package that references it?

Hi @ravikirankhareedi just to be clear, on Catalina the XCFramework build succeeds, just the failure is when you try to build the swift package that references it?

Yes, That is correct.

Can we see what your swift.package for your project looks like?

// swift-tools-version:5.3
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "MyDB",
    platforms: [.macOS(.v10_15)],
    products: [
        // Products define the executables and libraries a package produces, and make them visible to other packages.
        .library(
            name: "MyDB",
            targets: ["MyDB", "Realm", "RealmSwift"]),
    ],
    dependencies: [
        // Dependencies declare other packages that this package depends on.
        // .package(url: /* package url */, from: "1.0.0"),
        .package(path: "Cmn")
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages this package depends on.
        .target(
            name: "MyDB",
            dependencies: [
                "Cmn"
            ],
            path: "Sources/",
            swiftSettings:[.unsafeFlags(["-enable-testing"])]),
        .binaryTarget(name: "Realm", path: "Dependencies/Realm.xcframework"),
        .binaryTarget(name: "RealmSwift", path: "Dependencies/RealmSwift.xcframework"),
        .testTarget(
            name: "MyDBTests",
            dependencies: ["MyDB"]),
    ]
)

Maybe adding the binaryTarget to a wrapper might work, as described here https://stackoverflow.com/a/65255303

Closing as this is an Xcode related issue and not a Realm issue.


[WIP] Replace iterators with slices (Non command buffer)

A more debatable half of #1604, which APIs use slices and which should use iterators is more up for consideration. My implementation for the Device iterators frequently just collects them anyway which to me suggests there isn't much point (apart from some idea of API uniformity).

I agree that the documentation would be a bit scary, but I'm not sure about API though; another pro is that this change means that the functions accept anything that looks vaguely like an iterator, which should simplify user's code.
However, I can't comment on how useful it actually is and it definitely does add some complexity.

Review status: 16 of 25 files reviewed at latest revision, 13 unresolved discussions.

examples/hal/quad/main.rs, line 164 at r1 (raw file):
Previously, kvark (Dzmitry Malyshau) wrote…
nit: could probably also do [set_layout]

Sadly no, set_layout is used later and [set_layout] moves it.

src/hal/src/device.rs, line 203 at r1 (raw file):
Previously, kvark (Dzmitry Malyshau) wrote…
strange idea: maybe we can omit this from gfx-backend-empty now that we have default implementations? ;)

I'm not sure, not implementing either will probably do something funky at compile time, but unimplemented! panics at runtime. If you want I can but I feel like there is no harm leaving one there.

src/hal/src/device.rs, line 494 at r1 (raw file):
Previously, kvark (Dzmitry Malyshau) wrote…
I'm a little concerned that his would prevent the expected behavior when the user passes in timeout of 0. We should still be checking all the fences, but this implementation may bail out in the process

I think this should work as expected now.

src/hal/src/device.rs, line 505 at r1 (raw file):
Previously, kvark (Dzmitry Malyshau) wrote…
why do we need to collect here?

fences needs to be iterated over multiple times, the only other option would be to find a way of making the iterator Clone-able.

src/hal/src/device.rs, line 515 at r1 (raw file):
Previously, msiglreith wrote…
I don't think we need issue a thread switch here, drivers will most likely do it internally anyways.

Could this not be a problem for the Mutex simulated fences in Metal, it will now just spin?

Comments from Reviewable

Review status: 16 of 25 files reviewed at latest revision, 13 unresolved discussions.

src/hal/src/device.rs, line 515 at r1 (raw file):
Previously, AIOOB (AIOOB) wrote…
Could this not be a problem for the Mutex simulated fences in Metal, it will now just spin?

wait_on_fence handling is a bit out of scope atm, but we should rather use native primitives for synchronization (in particular semaphores here) than trying to create our own with locks, loops, etc. IMO

Comments from Reviewable

Review status: 16 of 25 files reviewed at latest revision, 12 unresolved discussions.

src/hal/src/device.rs, line 203 at r1 (raw file):
Previously, AIOOB (AIOOB) wrote…
I'm not sure, not implementing either will probably do something funky at compile time, but unimplemented! panics at runtime. If you want I can but I feel like there is no harm leaving one there.

It's easy to try out, right? Just go to the empty backend, comment out a few methods, and see if it builds. I expect it to compile fine but go to the stack overflow when run. And this would be fine to me, since I don't think there is any value in guaranteeing the empty backend to instantly panic: it's only there to compile-test against.

src/hal/src/device.rs, line 494 at r1 (raw file):
Previously, AIOOB (AIOOB) wrote…
I think this should work as expected now.

Well, technically, no. The elapsed() here can already be non-zero.

src/hal/src/device.rs, line 505 at r1 (raw file):
Previously, AIOOB (AIOOB) wrote…
fences needs to be iterated over multiple times, the only other option would be to find a way of making the iterator Clone-able.

Oh I see now.

src/hal/src/device.rs, line 515 at r1 (raw file):
Previously, msiglreith wrote…
wait_on_fence handling is a bit out of scope atm, but we should rather use native primitives for synchronization (in particular semaphores here) than trying to create our own with locks, loops, etc. IMO

In general, either there is a simple working default implementation, or just defer this decision to the backends. In this case, there appear to be enough concerns to consider this a non-trivial implementaiton.

Comments from Reviewable

I think that its most things addressed. The only things that I can see that could be added are single variant versions of update_descriptor_sets, bind_graphics_descriptor_sets and bind_compute_descriptor_sets.

@AIOOB alright, shipit!
bors r+

There appears to be general agreement on the topic. We can nail down the details (descriptor sets) in follow ups, if needed.


Problem with selecting licenses following the instruction

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
The article contains a lot of licenses for which there are no available templates currently on GitHub. I cannot make BSD 4-Clause License show correctly on my repository sidebar even though it is listed on the help page.
However, I can find older repositories for which it shows correctly: https://github.com/m-bain/whisperX
Is there some magic keyword that makes license text linkable to the license name as here:

What part(s) of the article would you like to see updated?
List of licenses on the page should be updated here
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository
or an explanation of how to add a license should be modified here:
https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository
Additional information
No response

@alin256 Thank you for opening this issue! ✨
You're right in that the relevant doc does not include instructions on how to add the less commonly used licenses (e.g. BSD-4 Clause), which requires copy / pasting the license text in. I'll have our team review this in order to explore adding these instructions to the doc.
In the meantime, to add the BSD-4 Clause license - you can reference this helpful appendix, select the BSD-4 Clause license, and copy/paste the license text in manually -

This will populate the populate the sidebar with the correct license, which I tested on my end -

The appendix referenced above can be found in this doc, just as a heads up 💛 Submitting this now for our team to review updating the doc instructions!

Dear @nguyenalex836,
I raised this issue because copy-pasting does not work. I.e. the license identifier on the right and the license description on the top does not correlate with the pasted text.
For example in my repository, after some experimentation, I choose BSD-3-Clause template and rewrote everything inside it still to have BSD-3-Clause written over it. Because at some point I applied the BSD-3-Clause template.

@alin256 Thank you for letting me know! You would need to create a new LICENSE.md file in order to paste in the BSD-4 Clause license content -

Go to your repo and click "Add file" ---> "Create new file"

Instead of choosing a license template, name the new file LICENSE.md

Go to https://choosealicense.com/licenses/bsd-4-clause/# and copy the license text

Go back to your new LICENSE.md file and paste the license text in

Commit your changes / create the new file

You may then delete the BSD-3 Clause license you have been previously working with ✅

If after following these instructions you are still unsuccessful, I would strongly suggest reaching out to our fantastic support team for additional assistance 💛

Dear @nguyenalex836,
For some reason, your solution works (maybe the magic is calling it .md?!).
It would be a great help for GitHub users if the manual you provided is communicated on the relevant help page.
Would it work from any of the licenses listed in https://choosealicense.com/appendix/ ?

@alin256 Glad to hear that!

It would be a great help for GitHub users if the manual you provided is communicated on the relevant help page.

I will let our team speak to this when they review this issue!

Would it work from any of the licenses listed in https://choosealicense.com/appendix/ ?

I am unsure, but questions like these would be best addressed by our fantastic support team 💛

@nguyenalex836
I encountered a problem when modifying the data in the bsd-4-clause that we discussed.
If I put full details of my project in the LICENSE.md, as the clause #3, the  BSD-4-Clause license label disappears from the repository.
I assume there is some comparison of the license file to a template which breaks if the project name is too long. I tried back and forth, e.g. this commit:
"This product includes software developed by the DISTINGUISH project (Decision support using neural networks to predict geological uncertainties when geosteering, Research Council of Norway grant #344236)."
https://github.com/geosteering-no/spade-gan-inversion/commit/f60f08956d19f74166dfe28297ece2390cf7b27c
Can you follow up with the backend team to clarify how the underlying logic works.

Hi @alin256 - the topics you raised in your last comment would be best addressed by our fantastic support team. I'm going to go ahead and close this issue 💛


drone.info.get_version() INFORMATION_NOT_RECEIVED_YET

Arducopter 4.5.0
Jetson Orin NX, python 3.9
Name: mavsdk
Version: 2.5.1
Summary: Python wrapper for MAVSDK
Home-page: https://github.com/mavlink/MAVSDK-Python
Author:
Author-email:
License: UNKNOWN
Location: /home/orinnx-1of3/.local/lib/python3.9/site-packages
Requires: aiogrpc, grpcio, protobuf
Required-by:

try:
info = await drone.info.get_version()
print(info)
except InfoError as error:
print(f"drone.info.get_version error: {error}")
await cancel_all_tasks(ardupilot_running_tasks)
return True

Main in -- 2024-04-26 15:50:14.903863
System server version :  3 . 9
System server done
drone.connect : None
OrinNX Waiting for drone to connect...
-- Connected to drone!
drone.info.get_version error: INFORMATION_NOT_RECEIVED_YET: 'Information Not Received Yet'; origin: get_version(); params: ()
task name:  Task-3
print_status_text CancelledError
run result True
Main out -- 2024-04-26 15:50:19.455387

Can you share the mavsdk_server log?

Arducopter 4.3.0 is okay.
System server version :  3 . 10
System server done
drone.connect : None
Pi4B Waiting for drone to connect...
-- Connected to drone!
Version: [flight_sw_major: 4, flight_sw_minor: 3, flight_sw_patch: 0, flight_sw_vendor_major: 52, flight_sw_vendor_minor: 51, flight_sw_vendor_patch: 57, os_sw_major: 0, os_sw_minor: 0, os_sw_patch: 0, flight_sw_git_hash: 313762383, os_sw_git_hash:<PHONE_NUMBER>65363, flight_sw_version_type: RELEASE]
Flight mode: STABILIZED
Altitude: -2
Position info: Position: [latitude_deg: 0.0, longitude_deg: 0.0, absolute_altitude_m: 0.0, relative_altitude_m: -2.2170000076293945]
GPS info: GpsInfo: [num_satellites: 0, fix_type: NO_FIX]
RawGps info: RawGps: [timestamp_us: 0, latitude_deg: 0.0, longitude_deg: 0.0, absolute_altitude_m: 0.0, hdop: 100.0, vdop: 100.0, velocity_m_s: 0.0, cog_deg: 0.0, altitude_ellipsoid_m: 0.0, horizontal_uncertainty_m: 0.0, vertical_uncertainty_m: 0.0, velocity_uncertainty_m_s: 0.0, heading_uncertainty_deg: 0.0, yaw_deg: 0.0]
Battery: 99.0%
Battery_v: 0.0V

Check this:
http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/#debug-connection-issues

Check this: http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/#debug-connection-issues

$ ~/.local/lib/python3.9/site-packages/mavsdk/bin/mavsdk_server serial:///dev/ttyTHS0:921600
[04:42:20|Info ] MAVSDK version: v2.9.1 (mavsdk_impl.cpp:26)
[04:42:20|Info ] Waiting to discover system on serial:///dev/ttyTHS0:921600... (connection_initiator.h:20)
[04:44:19|Debug] New system ID: 1 Comp ID: 1 (mavsdk_impl.cpp:737)
[04:44:19|Debug] Component Autopilot (1) added. (system_impl.cpp:389)
[04:44:19|Warn ] Vehicle type changed (new type: 2, old type: 0) (system_impl.cpp:231)
[04:44:19|Debug] Discovered 1 component(s) (system_impl.cpp:537)
[04:44:19|Info ] System discovered (connection_initiator.h:62)
[04:44:19|Info ] Server started (grpc_server.cpp:165)
[04:44:19|Info ] Server set to listen on <IP_ADDRESS>:50051 (grpc_server.cpp:166)
[04:44:19|Warn ] sending again after 0.505286 s, retries to do: 3  (520). (mavlink_command_sender.cpp:312)
[04:44:20|Warn ] sending again after 1.00831 s, retries to do: 2  (520). (mavlink_command_sender.cpp:312)
[04:44:21|Warn ] sending again after 1.51132 s, retries to do: 1  (520). (mavlink_command_sender.cpp:312)
[04:44:21|Error]
$ python3 mavsdk_test_debug.py
Main in -- 2024-05-03 16:44:42.778549
System server version :  3 . 9
System server done
drone.connect : None
Orin NX Waiting for drone to connect...
-- Connected to drone!
drone.info.get_version error: INFORMATION_NOT_RECEIVED_YET: 'Information Not Received Yet'; origin: get_version(); params: ()
task name:  Task-3
print_status_text CancelledError
run result True
shutdown -- 2024-05-03 16:44:46.346463
Main out -- 2024-05-03 16:44:46.346559
$

Check this: http://mavsdk-python-docs.s3-website.eu-central-1.amazonaws.com/#debug-connection-issues

with Arducopter 4.5.0
$ ~/.local/lib/python3.9/site-packages/mavsdk/bin/mavsdk_server serial:///dev/ttyTHS0:921600
[04:54:24|Info ] MAVSDK version: v2.9.1 (mavsdk_impl.cpp:26)
[04:54:24|Info ] Waiting to discover system on serial:///dev/ttyTHS0:921600... (connection_initiator.h:20)
[04:54:24|Debug] New system ID: 1 Comp ID: 1 (mavsdk_impl.cpp:737)
[04:54:24|Debug] Component Autopilot (1) added. (system_impl.cpp:389)
[04:54:24|Warn ] Vehicle type changed (new type: 13, old type: 0) (system_impl.cpp:231)
[04:54:24|Debug] Discovered 1 component(s) (system_impl.cpp:537)
[04:54:24|Info ] System discovered (connection_initiator.h:62)
[04:54:24|Info ] Server started (grpc_server.cpp:165)
[04:54:24|Info ] Server set to listen on <IP_ADDRESS>:50051 (grpc_server.cpp:166)
[04:54:25|Warn ] sending again after 0.507659 s, retries to do: 3  (520). (mavlink_command_sender.cpp:312)
[04:54:25|Warn ] sending again after 1.01066 s, retries to do: 2  (520). (mavlink_command_sender.cpp:312)
[04:54:26|Warn ] sending again after 1.51371 s, retries to do: 1  (520). (mavlink_command_sender.cpp:312)
[04:54:26|Error]
$ python3 mavsdk_test_debug.py
Main in -- 2024-05-03 16:54:38.812153
System server version :  3 . 9
System server done
drone.connect : None
Orin NX Waiting for drone to connect...
-- Connected to drone!
drone.info.get_version error: INFORMATION_NOT_RECEIVED_YET: 'Information Not Received Yet'; origin: get_version(); params: ()
task name:  Task-3
print_status_text CancelledError
run result True
Main out -- 2024-05-03 16:54:42.358292
$

Thanks for the info. Next time consider putting code output between 3 backticks to make it more readable (```).
In any case, I can see one clue:
[04:54:25|Warn ] sending again after 0.507659 s, retries to do: 3 (520). (mavlink_command_sender.cpp:312)
[04:54:25|Warn ] sending again after 1.01066 s, retries to do: 2 (520). (mavlink_command_sender.cpp:312)
[04:54:26|Warn ] sending again after 1.51371 s, retries to do: 1 (520). (mavlink_command_sender.cpp:312)

This is for command 520 which is MAV_CMD_REQUEST_AUTOPILOT_CAPABILITIES which is required to display the information.
So it basically looks like ArduPilot doesn't answer to this command but instead it might respond to the new command MAV_CMD_REQUEST_MESSAGE. We should probably try to use the new command.
We had a similar discussion in https://github.com/mavlink/MAVSDK/issues/1605. I wonder when is a good time to switch over. Maybe the time is now :smile:

I see.
Interestingly, Pi4B with python 3.10, I seem not able to reproduce it with Arducopter 4.3.0 and 4.5.0.

both mavsdk-python 2.6.2
Python 3.9
[04:54:26|Error] [04:25:35|Info ] MAVSDK version: v2.10.2 (mavsdk_impl.cpp:26)
[04:25:35|Info ] Waiting to discover system on serial:///dev/ttyTHS0:921600... (connection_initiator.h:20)
[04:25:35|Debug] New system ID: 1 Comp ID: 1 (mavsdk_impl.cpp:720)
[04:25:35|Debug] Component Autopilot (1) added. (system_impl.cpp:365)
[04:25:35|Warn ] Vehicle type changed (new type: 13, old type: 0) (system_impl.cpp:216)
[04:25:35|Debug] Discovered 1 component(s) (system_impl.cpp:508)
[04:25:35|Info ] System discovered (connection_initiator.h:62)
[04:25:35|Info ] Server started (grpc_server.cpp:169)
[04:25:35|Info ] Server set to listen on <IP_ADDRESS>:50051 (grpc_server.cpp:170)
[04:25:36|Warn ] sending again after 0.508631 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:25:36|Warn ] sending again after 1.01172 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:25:37|Warn ] sending again after 1.51479 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:25:37|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:40|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:40|Warn ] sending again after 0.503525 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:40|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:41|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:41|Warn ] sending again after 1.00689 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:41|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:41|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:41|Warn ] sending again after 1.51026 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:41|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:42|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:42|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:26:42|Warn ] sending again after 0.503293 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:42|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:43|Warn ] sending again after 1.00639 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:43|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:43|Error] Error: Param for gyro offset_x failed. (telemetry_impl.cpp:1912)
[04:26:43|Warn ] sending again after 1.50947 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:43|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:44|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:44|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:44|Warn ] sending again after 0.503646 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:44|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:44|Warn ] sending again after 0.504154 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:44|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:45|Warn ] sending again after 1.00742 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:45|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:45|Warn ] sending again after 1.00747 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:45|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:45|Warn ] sending again after 1.51063 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:45|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:45|Warn ] sending again after 1.51067 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:45|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:46|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:26:46|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:46|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:46|Error] Error: Param for gyro offset_y failed. (telemetry_impl.cpp:1927)
[04:26:46|Warn ] sending again after 0.505104 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:46|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:47|Warn ] sending again after 1.00835 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:47|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:47|Warn ] sending again after 1.51148 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:47|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:48|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:48|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:48|Warn ] sending again after 0.505491 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:48|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:48|Warn ] sending again after 0.505545 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:48|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:49|Warn ] sending again after 1.00868 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:49|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:49|Warn ] sending again after 1.00873 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:49|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:49|Error] Error: Param for gyro offset_z failed. (telemetry_impl.cpp:1942)
[04:26:49|Warn ] sending again after 1.51182 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:49|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:49|Warn ] sending again after 1.51188 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:49|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:50|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:26:50|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:50|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:50|Warn ] sending again after 0.506064 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:50|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:51|Warn ] sending again after 1.00916 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:51|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:51|Warn ] sending again after 1.51226 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:51|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:52|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:52|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:52|Error] Error: Param for accel offset_x failed. (telemetry_impl.cpp:1867)
[04:26:52|Warn ] sending again after 0.50616 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:52|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:52|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:52|Warn ] sending again after 0.506284 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:53|Warn ] sending again after 1.00944 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:53|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:53|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:53|Warn ] sending again after 1.00959 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:53|Warn ] sending again after 1.51267 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:53|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:53|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:53|Warn ] sending again after 1.51277 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:54|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:26:54|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:54|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:54|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:54|Warn ] sending again after 0.506917 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:55|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:55|Error] Error: Param for accel offset_y failed. (telemetry_impl.cpp:1882)
[04:26:55|Warn ] sending again after 1.01007 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:55|Warn ] sending again after 0.507017 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:55|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:55|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:55|Warn ] sending again after 1.51323 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:56|Warn ] sending again after 1.01019 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:56|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:56|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:56|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:56|Warn ] sending again after 1.51338 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:56|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:56|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:26:56|Warn ] sending again after 0.5074 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:57|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:26:57|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:26:57|Warn ] sending again after 1.01055 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:57|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:26:58|Warn ] sending again after 1.51368 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:26:58|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:26:58|Error] Error: Param for accel offset_z failed. (telemetry_impl.cpp:1897)
[04:26:58|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:26:58|Warn ] sending again after 0.507894 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:26:58|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:59|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:26:59|Warn ] sending again after 0.508003 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:26:59|Warn ] sending again after 1.01109 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:26:59|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:26:59|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:26:59|Warn ] sending again after 1.01121 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:26:59|Warn ] sending again after 1.51426 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:26:59|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:00|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:00|Warn ] sending again after 1.51435 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:00|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:00|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:00|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:01|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:01|Warn ] sending again after 0.508611 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:01|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:01|Error] Error: Param for mag offset_x failed. (telemetry_impl.cpp:1822)
[04:27:01|Warn ] sending again after 1.01173 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:02|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:02|Warn ] sending again after 1.5149 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:02|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:02|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:02|Warn ] sending again after 0.508942 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:02|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:03|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:03|Warn ] sending again after 0.509041 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:03|Warn ] sending again after 1.01214 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:03|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:03|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:03|Warn ] sending again after 1.01227 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:03|Warn ] sending again after 1.51535 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:03|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:04|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:04|Warn ] sending again after 1.51546 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:04|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:04|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:04|Error] Error: Param for mag offset_y failed. (telemetry_impl.cpp:1837)
[04:27:04|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:05|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:05|Warn ] sending again after 0.509487 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:05|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:05|Warn ] sending again after 1.01265 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:05|Warn ] sending again after 0.509623 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:05|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:06|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:06|Warn ] sending again after 1.51598 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:06|Warn ] sending again after 1.01295 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:06|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:06|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:06|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:06|Warn ] sending again after 1.51612 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:06|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:07|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:07|Warn ] sending again after 0.500165 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:07|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:07|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:07|Error] Error: Param for mag offset_z failed. (telemetry_impl.cpp:1852)
[04:27:07|Warn ] sending again after 1.00326 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:08|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:08|Warn ] sending again after 1.50639 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:08|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:08|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:08|Warn ] sending again after 0.500256 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:08|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:09|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:09|Warn ] sending again after 0.500341 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:09|Warn ] sending again after 1.00342 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:09|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:09|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:09|Warn ] sending again after 1.00358 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:09|Warn ] sending again after 1.50668 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:09|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:10|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:10|Warn ] sending again after 1.50685 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:10|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:10|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:10|Error] Error: Param for gyro offset_x failed. (telemetry_impl.cpp:1912)
[04:27:10|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:11|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:11|Warn ] sending again after 0.500791 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:11|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:11|Warn ] sending again after 1.0039 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:12|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:12|Warn ] sending again after 1.5071 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:12|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:12|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:12|Warn ] sending again after 0.501108 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:12|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:13|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:13|Warn ] sending again after 0.501251 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:13|Warn ] sending again after 1.00436 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:13|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:13|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:13|Error] Error: Param for gyro offset_y failed. (telemetry_impl.cpp:1927)
[04:27:13|Warn ] sending again after 1.00451 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:13|Warn ] sending again after 1.50766 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:13|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:14|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:14|Warn ] sending again after 1.50791 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:14|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:14|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:14|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:15|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:15|Warn ] sending again after 0.501843 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:15|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:15|Warn ] sending again after 1.00496 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:15|Warn ] sending again after 0.502072 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:15|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:16|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:16|Warn ] sending again after 1.50811 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:16|Warn ] sending again after 1.00529 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:16|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:16|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:16|Error] Error: Param for gyro offset_z failed. (telemetry_impl.cpp:1942)
[04:27:16|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:16|Warn ] sending again after 1.50842 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:16|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:17|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:17|Warn ] sending again after 0.502622 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:17|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:17|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:17|Warn ] sending again after 1.00578 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:18|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:18|Warn ] sending again after 1.50898 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:18|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:18|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:18|Warn ] sending again after 0.502833 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:18|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:19|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:19|Warn ] sending again after 0.502901 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:19|Warn ] sending again after 1.006 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:19|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:19|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:19|Error] Error: Param for accel offset_x failed. (telemetry_impl.cpp:1867)
[04:27:19|Warn ] sending again after 1.00612 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:19|Warn ] sending again after 1.50925 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:19|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:20|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:20|Warn ] sending again after 1.50931 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:20|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:20|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:20|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:21|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:21|Warn ] sending again after 0.503516 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:21|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:21|Warn ] sending again after 1.00672 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:22|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:22|Warn ] sending again after 1.50998 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:22|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:22|Error] Error: Param for accel offset_y failed. (telemetry_impl.cpp:1882)
[04:27:22|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:22|Warn ] sending again after 0.503859 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:22|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:23|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:23|Warn ] sending again after 0.504003 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:23|Warn ] sending again after 1.00713 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:23|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:23|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:23|Warn ] sending again after 1.00714 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:23|Warn ] sending again after 1.51024 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:23|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:24|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:24|Warn ] sending again after 1.51029 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:24|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:24|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:24|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:25|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:25|Warn ] sending again after 0.504264 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:25|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:25|Error] Error: Param for accel offset_z failed. (telemetry_impl.cpp:1897)
[04:27:25|Warn ] sending again after 1.0074 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:25|Warn ] sending again after 0.504415 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:25|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:26|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:26|Warn ] sending again after 1.51064 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:26|Warn ] sending again after 1.00764 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:26|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:26|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:26|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:26|Warn ] sending again after 1.51074 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:26|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:27|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:27|Warn ] sending again after 0.504683 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:27|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:27|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:27|Warn ] sending again after 1.00782 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:28|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:28|Warn ] sending again after 1.51094 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:28|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:28|Error] Error: Param for mag offset_x failed. (telemetry_impl.cpp:1822)
[04:27:28|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:28|Warn ] sending again after 0.505164 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:28|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:29|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:29|Warn ] sending again after 0.505191 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:29|Warn ] sending again after 1.00842 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:29|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:29|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:29|Warn ] sending again after 1.00845 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:29|Warn ] sending again after 1.51166 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:29|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:30|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:30|Warn ] sending again after 1.51174 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:30|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:30|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:30|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:31|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:31|Warn ] sending again after 0.505727 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:31|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:31|Error] Error: Param for mag offset_y failed. (telemetry_impl.cpp:1837)
[04:27:31|Warn ] sending again after 1.00882 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:32|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:32|Warn ] sending again after 1.51199 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:32|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:32|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:32|Warn ] sending again after 0.505979 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:32|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:33|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:33|Warn ] sending again after 0.506048 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:33|Warn ] sending again after 1.00921 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:33|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:33|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:33|Warn ] sending again after 1.00924 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:33|Warn ] sending again after 1.51238 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:33|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:34|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:34|Warn ] sending again after 1.51257 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:34|Warn ] sending again after 0.0201796 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:34|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:34|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:34|Error] Error: Param for mag offset_z failed. (telemetry_impl.cpp:1852)
[04:27:34|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:34|Warn ] sending again after 0.523259 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:35|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:35|Warn ] sending again after 0.496523 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:35|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:35|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:35|Warn ] sending again after 0.506745 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:35|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:35|Warn ] Timeout for not-existing command: 520! Ignoring... (mavlink_command_sender.cpp:362)
[04:27:36|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:36|Warn ] sending again after 1.00994 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:36|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:36|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:36|Warn ] sending again after 0.506871 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:36|Warn ] sending again after 1.51313 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:36|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:37|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:37|Warn ] sending again after 1.0101 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:37|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:37|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:37|Error] Error: Param for gyro offset_x failed. (telemetry_impl.cpp:1912)
[04:27:37|Warn ] sending again after 1.5132 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:38|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:38|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:38|Warn ] sending again after 0.507148 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:38|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:38|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:38|Warn ] sending again after 0.507282 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:39|Warn ] sending again after 1.0104 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:39|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:39|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:39|Warn ] sending again after 1.01049 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:39|Warn ] sending again after 1.51358 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:39|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:39|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:39|Warn ] sending again after 1.51372 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:40|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:40|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:40|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:40|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:40|Error] Error: Param for gyro offset_y failed. (telemetry_impl.cpp:1927)
[04:27:40|Warn ] sending again after 0.507687 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:41|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:41|Warn ] sending again after 1.01089 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:41|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:41|Warn ] sending again after 1.51404 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:42|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:42|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:42|Warn ] sending again after 0.508164 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:42|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:42|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:42|Warn ] sending again after 0.508272 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:43|Warn ] sending again after 1.01139 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:43|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:43|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:43|Warn ] sending again after 1.0115 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:43|Warn ] sending again after 1.51456 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:43|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:43|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:43|Error] Error: Param for gyro offset_z failed. (telemetry_impl.cpp:1942)
[04:27:43|Warn ] sending again after 1.51466 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:44|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:44|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:44|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:44|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:44|Warn ] sending again after 0.507896 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:45|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:45|Warn ] sending again after 1.01109 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:45|Warn ] sending again after 0.508086 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:45|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:45|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:45|Warn ] sending again after 1.5143 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:46|Warn ] sending again after 1.01135 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:46|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:46|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:46|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:46|Warn ] sending again after 1.51452 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:46|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:46|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:46|Error] Error: Param for accel offset_x failed. (telemetry_impl.cpp:1867)
[04:27:46|Warn ] sending again after 0.508583 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:47|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:47|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:47|Warn ] sending again after 1.01177 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:47|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:47|Warn ] sending again after 1.51492 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:48|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:48|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:48|Warn ] sending again after 0.509082 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:48|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:48|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:48|Warn ] sending again after 0.509226 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:49|Warn ] sending again after 1.01273 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:49|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:49|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:49|Warn ] sending again after 1.01285 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:49|Warn ] sending again after 1.51606 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:49|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:49|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:49|Error] Error: Param for accel offset_y failed. (telemetry_impl.cpp:1882)
[04:27:49|Warn ] sending again after 1.51618 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:50|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:50|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:50|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:50|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:50|Warn ] sending again after 0.509809 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:51|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:51|Warn ] sending again after 1.01299 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:51|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:52|Warn ] sending again after 1.51612 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:52|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:52|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:52|Warn ] sending again after 0.500072 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:52|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:52|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:52|Error] Error: Param for accel offset_z failed. (telemetry_impl.cpp:1897)
[04:27:53|Warn ] sending again after 0.500136 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:53|Warn ] sending again after 1.00333 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:53|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:53|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:53|Warn ] sending again after 1.00346 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:53|Warn ] sending again after 1.50658 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:53|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:53|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:54|Warn ] sending again after 1.50671 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:54|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:54|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:54|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:54|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:55|Warn ] sending again after 0.500626 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:55|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:55|Warn ] sending again after 1.00389 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:55|Warn ] sending again after 0.500913 s, retries to do: 3  (512). (mavlink_command_sender.cpp:321)
[04:27:55|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:55|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[04:27:55|Error] Error: Param for mag offset_x failed. (telemetry_impl.cpp:1822)
[04:27:56|Warn ] sending again after 1.50712 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:56|Warn ] sending again after 1.0041 s, retries to do: 2  (512). (mavlink_command_sender.cpp:321)
[04:27:56|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:56|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[04:27:56|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:56|Warn ] sending again after 1.50722 s, retries to do: 1  (512). (mavlink_command_sender.cpp:321)
[04:27:56|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:327)
[04:27:56|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[04:27:57|Warn ] sending again after 0.501148 s, retries to do: 3  (520). (mavlink_command_sender.cpp:321)
[04:27:57|Error] Retrying failed (512) (mavlink_command_sender.cpp:348)
[04:27:57|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[04:27:57|Warn ] sending again after 1.00437 s, retries to do: 2  (520). (mavlink_command_sender.cpp:321)
[04:27:58|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[04:27:58|Warn ] sending again after 1.50752 s, retries to do: 1  (520). (mavlink_command_sender.cpp:321)
[04:27:58|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[04:27:58|Error] Retrying failed (520) (mavlink_command_sender.cpp:348)
[04:27:58|Warn ]

Python 3.10 (get_version() okay)
[04:50:27|Info ] MAVSDK version: v2.10.2 (mavsdk_impl.cpp:26)
[04:50:27|Info ] Waiting to discover system on serial:///dev/ttyAMA1:921600... (connection_initiator.h:20)
[04:50:27|Debug] New system ID: 42 Comp ID: 100 (mavsdk_impl.cpp:720)
[04:50:27|Debug] Component Camera 1 (100) added. (system_impl.cpp:365)
[04:50:27|Debug] Discovered 1 component(s) (system_impl.cpp:508)
[04:50:27|Debug] New system ID: 1 Comp ID: 1 (mavsdk_impl.cpp:720)
[04:50:27|Debug] Component Autopilot (1) added. (system_impl.cpp:365)
[04:50:27|Warn ] Vehicle type changed (new type: 13, old type: 0) (system_impl.cpp:216)
[04:50:27|Debug] Discovered 1 component(s) (system_impl.cpp:508)
[04:50:27|Info ] System discovered (connection_initiator.h:62)
[04:50:27|Debug] Component Unsupported component (250) added. (system_impl.cpp:365)
[04:50:27|Info ] Server started (grpc_server.cpp:169)
[04:50:27|Info ] Server set to listen on <IP_ADDRESS>:50051 (grpc_server.cpp:170)
[04:50:27|Debug] Component Ground station (190) added.


Add docker-compose.yml and change README.md

Add docker-compose.yml and add instructions on how to setup the server with it.

Hi @BenjaminLindberg,
Instructions for docker/docker-compose are already available here https://hub.docker.com/r/athou/commafeed
Do you feel they are insufficient?

Hey @Athou
I think that the docker documentation is fine, but it would be good to include a docker-compose.yml file.
This is so that users can directly clone the repository and run it with just one command, and not worry about creating a docker-compose.yml file themselves.

I see. Why would you clone the repository though? The repository is for sources only, the docker-compose.yml file doesn't need anything from the repository to work, as the image is downloaded from Docker Hub, already built.
There are also multiple ways of running CommaFeed with docker-compose:

with h2/mysql/mariadb/postgresql/sqlserver
with a redis cache
with a reverse proxy (nginx, apache, caddy, ...)

One way is not better than the other, it's a matter of usage and preference, so the current documentation on Docker Hub describing multiple configurations makes sense to me.


Less default styles / theming support

Hi. Thanks for this work.
The css has some styles that will clash with many site designs, like font-family: Arial, 'Helvetica Neue', Helvetica, sans-serif; It would be great if the css could be splitted: One providing the core css absolutely necessary for placement etc, and one second css file with the css specific to the design.
Like with http://github.hubspot.com/vex/ that could result in support for included themes, but more important is that it owuld make it easier to make jplist for the the site design.

Hi,
Thank you for the feedback.
This version of jPList almost doesn't have CSS styles and in most examples uses Bootstrap framework for demo pages. Developer may use any styles / frameworks that needed and any HTML structure. The only exception is custom dropdown control and range slider as it's not possible to implement them without CSS, but even in these cases the styles are minimal and can be changed in any way.

Hi, thanks for your answer. The examples tricked me by reusing the bootstrap styles, but that is exactly what is wanted. Very nice.
https://github.com/1rosehip/jplist-es6/blob/master/dist/1.1.2/jplist.styles.css does indeed not many styles. The font-family thing I mentioned, and some color assignments. I believe you that those are really necessary for making the dropdown works.
Looks nice so far!


Add narrative chapter about initialization

So it’s time to depend on examples even less.
Although the sections on validators and converters are copied mostly verbatim from there. I’m not sure how to cull examples in a meaningful way? It could be a little briefer and just refer to the new chapter.
But it finally gives a good place to explain intricacies of initialization.
Feedback welcome!
Fixes #289 #314 #264 #255 #263 #171 #107 #30

I believe I’ve addressed everything.
I’ve also added a news fragment to point people to our new chapters.

Excellent work @hynek !


Resolve #210

Resolve #210

Codecov Report

Merging #338 into master will decrease coverage by 22.2%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #338       +/-   ##
==========================================
- Coverage   24.15%   1.94%   -22.21%
==========================================
  Files          72      73        +1
  Lines        1718    1795       +77
  Branches      285     298       +13
==========================================
- Hits          415      35      -380
- Misses       1217    1759      +542
+ Partials       86       1       -85

Impacted Files
Coverage Δ

atcoder-problems-backend/src/crawler.rs
0% <ø> (-28.27%)
:arrow_down:

...oder-problems-backend/src/sql/submission_client.rs
0% <0%> (-82.15%)
:arrow_down:

...tcoder-problems-backend/src/crawler/fix_crawler.rs
0% <0%> (ø)

atcoder-problems-backend/src/server/utils.rs
0% <0%> (-100%)
:arrow_down:

atcoder-problems-backend/src/sql/language_count.rs
0% <0%> (-89.48%)
:arrow_down:

atcoder-problems-backend/src/sql/accepted_count.rs
0% <0%> (-87.81%)
:arrow_down:

...tcoder-problems-backend/src/sql/rated_point_sum.rs
0% <0%> (-85.37%)
:arrow_down:

atcoder-problems-backend/src/sql/streak.rs
0% <0%> (-84.62%)
:arrow_down:

atcoder-problems-backend/src/sql/problem_info.rs
0% <0%> (-80%)
:arrow_down:

...tcoder-problems-backend/src/sql/contest_problem.rs
0% <0%> (-80%)
:arrow_down:

... and 11 more

Continue to review full report at Codecov.

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


Failed to push workdir to the guest when the provision is beaker

$
summary: Demo
discover:
  - name: demo
    how: fmf
    url: https://gitlab.com/ZhaojuanGuo/kernel-tests.git
    ref: 523-rdma
    test:
      - /rdma/opa-fm
provision:
    how: beaker
    image: RHEL-9.3.0-20230821.32
    hardware:
        hostname: "rdma-cki-04.rdma.lab.eng.rdu2.redhat.com"
    key: "/home/zguo/.ssh/id_rsa"
    user: root
    password: QwAo2U6GRxyNPKiZaOCx
execute:
    how: tmt

$ tmt run plans --name /rdma/plans/example-provision-beaker -d -vvv
/var/tmp/tmt/run-023
    warn: /rdma/plans/example-provision-beaker:provision - {'how': 'beaker', 'image': 'RHEL-9.3.0-20230821.32', 'hardware': {'hostname': 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'}, 'key': '/home/zguo/.ssh/id_rsa', 'user': 'root', 'password': 'QwAo2U6GRxyNPKiZaOCx'} is not valid under any of the given schemas
Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker' created.

/rdma/plans/example-provision-beaker
summary: Demo
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/discover' created.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/provision' created.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/prepare' created.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/execute' created.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/report' created.
    Report step always force mode enabled.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/report' created.
    Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/finish' created.
    discover
    workdir: /var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/discover
        how: fmf
        name: demo
        order: 50
        Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/discover/demo' created.
        url: https://gitlab.com/ZhaojuanGuo/kernel-tests.git
        Clone 'https://gitlab.com/ZhaojuanGuo/kernel-tests.git' to '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/discover/demo/tests'.
        ref: 523-rdma
        Checkout ref '523-rdma'.
        hash: 10c24c72
        tests: /rdma/opa-fm
        Check metadata tree in '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/discover/demo/tests'.
        summary: 1 test selected
            /rdma/opa-fm
    provision
    workdir: /var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/provision
        Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/provision/default-0' created.
        how: beaker
        order: 50
        hardware: hostname: rdma-cki-04.rdma.lab.eng.rdu2.redhat.com

        image: RHEL-9.3.0-20230821.32
        Transformed hardware:
            and:
              - hostname:
                    _op: ==
                    _value: rdma-cki-04.rdma.lab.eng.rdu2.redhat.com
        guest: has been requested
        job id: rdma-cki-04.rdma.lab.eng.rdu2.redhat.com
        wait: waiting for condition 'get_new_state' with timeout 1:00:00, deadline in 3600.0 seconds, checking every 60.00 seconds
        status: Waiting        wait: 'get_new_state' still pending, 3598.26 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3536.70 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3474.87 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3413.12 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3351.29 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3289.22 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3227.26 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3165.52 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3103.26 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 3041.59 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 2979.86 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 2918.22 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 2856.37 seconds left, current tick 60.00 seconds
        status: Installing        wait: 'get_new_state' still pending, 2794.62 seconds left, current tick 60.00 seconds
        status: Waiting           wait: 'get_new_state' still pending, 2732.88 seconds left, current tick 60.00 seconds
        status: Waiting        wait: 'get_new_state' still pending, 2671.13 seconds left, current tick 60.00 seconds
        status: Waiting        wait: 'get_new_state' still pending, 2609.38 seconds left, current tick 60.00 seconds
        status: Waiting        wait: 'get_new_state' still pending, 2547.63 seconds left, current tick 60.00 seconds
        status: Reserved        wait: 'get_new_state' finished successfully, 2485.89 seconds left

        address: rdma-cki-04.rdma.lab.eng.rdu2.redhat.com
        multihost name: default-0
        Create the master ssh connection: ssh -oForwardX11=no -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null -oServerAliveInterval=60 -oServerAliveCountMax=5 -S/run/user/1000/tmt/tmp7vl8n74z -MNnT<EMAIL_ADDRESS>        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; cat /etc/os-release' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/provision/default-0' already exists.
<EMAIL_ADDRESS>password:         Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; cat /etc/lsb-release' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; arch' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        query: Command 'arch' produced no usable output.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; cat /etc/redhat-release' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        query: Command 'cat /etc/redhat-release' produced no usable output.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; cat /etc/fedora-release' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        query: Command 'cat /etc/fedora-release' produced no usable output.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; uname -r' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        query: Command 'uname -r' produced no usable output.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; stat /run/ostree-booted' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; dnf5 --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; dnf --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; yum --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; cat /proc/filesystems' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; whoami' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        arch: unknown
        distro: unknown
        kernel: unknown
        package manager: unknown
        selinux: no
        is superuser: no
        summary: 1 guest provisioned
    prepare
    workdir: /var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/prepare
        queued push task #1: push on default-0

        push task #1: push on default-0
    Push workdir to guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
    Ensure that rsync is installed on the guest.
    Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; rsync --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        cmd: rsync --version
        err: Warning: Permanently added 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com' (ED25519) to the list of known hosts.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err<EMAIL_ADDRESS>Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
    Check the package manager.
    Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; dnf --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        cmd: dnf --version
        err: Warning: Permanently added 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com' (ED25519) to the list of known hosts.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err<EMAIL_ADDRESS>Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
    Check for a read-only distro.
    Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; rpm-ostree --version' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        cmd: rpm-ostree --version
        err: Warning: Permanently added 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com' (ED25519) to the list of known hosts.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err<EMAIL_ADDRESS>Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
    Execute command 'export TMT_PLAN_DATA=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/data; export TMT_TREE=/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/tree; yum install -y rsync' on guest 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com'.
        cmd: yum install -y rsync
        err: Warning: Permanently added 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com' (ED25519) to the list of known hosts.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err: Permission denied, please try again.
        err: ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        err<EMAIL_ADDRESS>Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).
    fail: Failed to push workdir to the guest. This usually means that login as 'root' to the guest does not work.
    fail: Command 'yum install -y rsync' returned 255.
    finish
    workdir: /var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/finish

    Prune '/rdma/plans/example-provision-beaker' plan workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker'.
        Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/execute/default-0' created.
        Workdir '/var/tmp/tmt/run-023/rdma/plans/example-provision-beaker/report/default-0' created.
        summary: 0 tasks completed

plan failed

The exception was caused by 1 earlier exceptions

Cause number 1:

    prepare step failed
    The exception was caused by 1 earlier exceptions
    Cause number 1:
        Command 'yum install -y rsync' returned 255.
        stderr (7 lines)
        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Warning: Permanently added 'rdma-cki-04.rdma.lab.eng.rdu2.redhat.com' (ED25519) to the list of known hosts.
        ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        Permission denied, please try again.
        ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
        Permission denied, please try again.
        ssh_askpass: exec(/usr/libexec/openssh/gnome-ssh-askpass): No such file or directory
<EMAIL_ADDRESS>Permission denied (publickey,gssapi-keyex,gssapi-with-mic,password).

Hi @guoguojenna, would you please paste your fmf file? Then I will take a look to figure out why.

Hi @idorax , thanks for the checking, here is my fmf file:
$ cat a.fmf
summary: Demo
discover:

name: demo
how: fmf
url: https://gitlab.com/ZhaojuanGuo/kernel-tests.git
ref: 523-rdma
test:

/rdma/opa-fm
provision:
how: beaker
image: RHEL-9.3.0-20230821.32
hardware:
hostname: "rdma-cki-04.rdma.lab.eng.rdu2.redhat.com"
key: "/home/zguo/.ssh/id_rsa"
user: root
password: ##the beaker default password##
execute:
how: tmt

Is there any way to avoid the password input for testing with beaker on tmt

Update, I copied my ssh public key here, and this issue is gone. Thanks Huanian for checking this!
https://beaker.engineering.redhat.com/prefs/#ssh-public-keys

Update, I copied my ssh public key here, and this issue is gone.

@guoguojenna, can we close this issue?

Closing.


Functionality, Component, and Role Comment-Based Help sections don't work as expected

Steps to reproduce
PS C:\> Get-Help -Name Connect-Armor -Functionality
Get-Help : Missing an argument for parameter 'Functionality'. Specify a parameter of type 'System.String[]' and try again.
At line:1 char:30
+ Get-Help -Name Connect-Armor -Functionality
+                              ~~~~~~~~~~~~~~
+ CategoryInfo          : InvalidArgument: (:) [Get-Help], ParameterBindingException
+ FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.GetHelpCommand

PS C:\> ( Get-Help -Name Connect-Armor ).Functionality
Armor session management

PS C:\> $help = Get-Help -Name Connect-Armor -Full; $help.Functionality
Armor session management

PS C:\> ( ( Get-Help -Name Connect-Armor -Full ).ToString() | Select-String -Pattern 'FUNCTIONALITY|COMPONENT' ).Count
0

PS C:\> Get-Help -Name Connect-Armor -Full | Select-String -Pattern 'FUNCTIONALITY|COMPONENT'

<EMAIL_ADDRESS>inputTypes=@{inputType=@{type=@{name=None- this function does not accept pipeline inputs.}}}; returnValues=@{returnValue=@{type=@{name=ArmorSession}}};
<EMAIL_ADDRESS>description=System.Management.Automation.PSObject[]; details=@{name=Connect-Armor}; <EMAIL_ADDRESS><EMAIL_ADDRESS>syntax=<EMAIL_ADDRESS>name=Connect-Armor}}; xmlns:maml=http://schemas.microsoft.com/maml/2004/10;
xmlns:command=http://schemas.microsoft.com/maml/dev/command/2004/10; xmlns:dev=http://schemas.microsoft.com/maml/dev/2004/10; Name=Connect-Armor; Category=Function; Synopsis=; Component=Armor API; Role=; Functionality=Armor session management; ModuleName=Armor}

Expected behavior
The new(ish) Functionality, Component, and Role help sections should output the section content for all standard use cases or a null string if not set.

Actual behavior
The Get-Help command throws an error if the corresponding parameter is called, and does not show up in the Full help output.

Environment data

6.0.2 + 6.1.0 preview 3
Reference: https://github.com/PowerShell/platyPS/issues/373

Here's what I think needs addressing (all points should probably be separate issues):

about_comment_based_help not providing guidance on how to fill in the .FUNCTIONALITY and .COMPONENT and .ROLE sections; it seems that no built-in cmdlets have these sections filled in.

Get-Help -Full / -Detailed not outputting these sections at all - they can only be retrieved as properties on the objects output by Get-Help

A quick workaround is to pipe the Get-Help command to Format-List.

The unexpected stringification behavior of Get-Help output (see below).

As for Get-Help -Functionality / Get-Help -Component:
These are not switches that output the section of interest.
Rather, they act as filter parameters that accept one or more values (with wildcard support) to select (list) help topics with matching sections.
In your case:
# Ditto for Get-Help -Component *armor*
PS> Get-Help  -Functionality *armor*

Name                              Category  Module                    Synopsis
----                              --------  ------                    --------
Connect-Armor                     Function                            Connects to the Armor API and establishes a session.

As for your attempts to find information in the help text using Select-String:
The real test would be (and indeed it yields no result, because said sections are missing):
PS> Get-Help Connect-Armor -Full | Out-String -Stream | Select-String 'FUNCTIONALITY|COMPONENT'

That is, Out-String -Stream is needed for Select-String to operate on the same output as what would print to the console; it forces use of the default output formatting.
However - although it is a separate issue - the current behavior of implicit and explicit stringification is questionable:
Applying .ToString() directly always yields the empty string:
PS> '' -eq (Get-Help Get-ChildItem).ToString()
True

By contrast, implicit stringification - which happens inside "..." and when piping to a string-binding cmdlet such as Select-Object - produces the equivalent of .psobject.ToString();
PS> (Get-Help Get-ChildItem).psobject.ToString()
<EMAIL_ADDRESS>inputTypes=@{inputType=<EMAIL_ADDRESS>description=System.Management.Automation.PSObject[]}}<EMAIL_ADDRESS>details=@{verb=Get; noun=ChildItem; description=System.Management.Automation.PSObject[]; name=Get-ChildItem}<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>description=System.Management.Automation.PSObject[]; xmlns:maml=http://schemas.microsoft.com/maml/2004/10; xmlns:command=http://schemas.microsoft.com/maml/dev/command/2004/10; xmlns:dev=http://schemas.microsoft.com/maml/dev/2004/10; xmlns:MSHelp=http://msdn.microsoft.com/mshelp; Name=Get-ChildItem; Category=Cmdlet; Synopsis=Gets the items and child items in one or more specified locations.; Component=; Role=; Functionality=; PSSnapIn=; ModuleName=Microsoft.PowerShell.Management}

In fact, this behavior is tied to type [pscustomobject], which is what Get-Help outputs: #6163 asks for .ToString() and .psobject.ToString() to be the same, though in the specific case of Get-Help output you could argue that the ETS should be used to provide a .ToString() method that renders the help text (an implicit Out-String).

Agreed on all points and thank you for the detailed explanation, @mklement0.  I'll create separate issues for each.

Closing in favor of:

#7113
#7114
#7115
#7116


feat: adding support for systemjs remotes

Description

Adds support for loading systemjs based remotes

Related Issue

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] I have updated the documentation.

@2heal1 @ScriptedAlchemy Can this be merged ?


Implement sensor graph example

Signed-off-by: shubham wadhwa<EMAIL_ADDRESS>

[x]  Remove draft as soon as you are ready
[x]  Please use prettier.io as linter
[x]  Change this pull request  title to "Implement sensor graph example"
[x]  Rebase your branch git history to latetest release-0.11
[x]  Write a meaningful commit message

A good commit message example might be:
Add ReactJS sensor graph example

This example is a simple sensor data plotter implemented in RactJS blah blah


Add KNN Regression Model

I'm creating a K-Nearest Neighbors (KNN) regression model using a dataset. I'm following these steps:
Loading and exploring the dataset.
Preprocessing the data.
Splitting the data into training and testing sets.
Building and training the KNN regression model.
Evaluating the model.

@sanjay-kv
Kindly assign me this issue


Allow using the desktopModeMediaQuery prop in SQFormDatePicker

Currently, muiFieldProps's type does not include desktopModeMediaQuery. I would like to be able to customize when the picker switches to and from desktop mode.
My code:
<SQFormDatePicker
  name="birthDate"
  label="Birthdate"
  muiFieldProps={{
    allowSameDateSelection: true,
    desktopModeMediaQuery: '@media (pointer: fine)',
  }}
/>

Current error:
Type '{ allowSameDateSelection: true; desktopModeMediaQuery: string; }' is not assignable to type 'MuiFieldProps<Moment>'. Object literal may only specify known properties, and 'desktopModeMediaQuery' does not exist in type 'MuiFieldProps<Moment>'.

Is this prop available on the v5 of MUI?
Specifically can you use the prop against the latest version of SQForm. I might try testing this in storybook.
Bummer about this not being on mui v.4.

I was only able to find documentation of desktopModeMediaQuery for MUI v5, but I did find this code for MUI v4. From what I can tell, the desktopModeMediaQuery prop is on MUI's DatePicker for both v4 and v5, but TS throws an error when trying to put it into SQFormDatePicker's muiFieldProps. Testing with SQForm v11.0.3, the code
<SQFormDatePicker
  name="birthDate"
  label="Birthdate"
  muiFieldProps={{
    desktopModeMediaQuery: '@media (pointer: fine)',
  }}
/>

results in a similar error as above:
Type '{ desktopModeMediaQuery: string; }' is not assignable to type 'MuiFieldProps<Moment>'. Object literal may only specify known properties, and 'desktopModeMediaQuery' does not exist in type 'MuiFieldProps<Moment>'.

TS can be told to ignore the type:
<SQFormDatePicker
  name="birthDate"
  label="Birthdate"
  muiFieldProps={{
    // @ts-ignore
    desktopModeMediaQuery: '',
  }}
/>

This code does not throw an error and desktopModeMediaQuery works as expected.
Testing this in storybook also works as expected.

Sounds like we have an error in our typing. That should be fixed.
Also it sounds like this will work in v5. Since that is on its way and the issue that brought this up is low priority. I don't think we need to find an v4 way to solve this.


Add test for dtype coverage of jax.numpy ufuncs

Our current test suite for jax.numpy ufuncs is built on hand-defined op_record entries for all defined functions. This leaves some potential inputs untested, and in particular there are a number of dtypes supported by numpy but not supported by the corresponding jax function.
This PR adds an automatically generated set of tests to ensure dtype coverage for jax.numpy ports of top-level numpy ufuncs. The test extracts the list of ufuncs available in numpy's top-level namespace, generates a list of valid input dtypes for each, and uses these dtypes as inputs to the jax.numpy wrappers of the ufuncs.
This has already led to improved coverage of a number of wrapper functions (see linked PRs below). There are a few remaining known failures explicitly skipped in the test: primarily bool inputs which numpy casts to integers. It is not clear to me whether we should strive to support all of these in JAX, but I am leaving them as a TODO.

Internal tests all pass.


Emit warning to host logs for non-manage rights ServiceBus triggers

helps with #1048
Service bus sdk seems pretty untestable, added INamespaceManager cruft to try to get a bit of test coverage, happy for any suggested improvements.
This manage access rights issue isn't limited to Subscriptions, Queues exhibit the same behavior.
Not sure that host logs are the best place as there's very limited visibility (no warnings in the functions portal, for example).

So where do these logs show up? They don't show up in the user facing portal? That's what we need.

The logs appear in host logs (not the function logs, which we surface in the portal to the user).  I think these should probably be routed to function logs (seemed pretty invasive), or throw an error here and force the user to correct the issue, assuming we can't make an easy fix for Listen/Manage in scale controller.
I looked into grabbing a message count with listen rights, couldn't find anything promising in the sdk or rest apis. Haven't reached out to the SB team, they might know something

Changed this to throw, which causes a function indexing exception that appears in the portal:


Fraction numbers should not be shown in scenario cards and tool tips

Basically to change the format of the numbers (no. of cases) that are showing up on the frontend. Instead of decimal number it should be whole numbers, as no. of cases can never be in fractions. The best way is to change through API calls.

Is this issue already fixed in develop?