Float("Nan") == Any number is True

So with the #1493 commit, now Float("NaN") == Any Number is True
Nan == 6 is True, and so on.
x = Tensor([float("inf"), float("-inf"),float("nan"), 5,5,-4])
x == 6 is [0. 0. 1. 0. 0. 0.]

Note: Not sure about the title, admins can change it to make it more general

Probably related: #862

  def __ge__(self, x) -> Tensor: return (((self>float('-inf')) + (self<float('inf')) + (x>float('-inf')) + (x<float('inf'))) < 3).where(0.0, (1.0-(self<x)))
  def __le__(self, x) -> Tensor: return (((self>float('-inf')) + (self<float('inf')) + (x>float('-inf')) + (x<float('inf'))) < 3).where(0.0, (1.0-(self>x)))
  def __ne__(self, x) -> Tensor: return (((self>float('-inf')) + (self<float('inf')) + (x>float('-inf')) + (x<float('inf'))) < 3).where(1.0, ((self<x) + (self>x)))   # type: ignore
  def __eq__(self, x) -> Tensor: return 1.0-(self != x)       # type: ignore

shield your eyes from this cursed concoction of code 🫣
but yeah this hack fixes the float('nan') issue for ge, le, ne, and eq
probably not at all ideal
it is also possible to say screw it and totally curse the tensor.py implementation of ge, le, ne, and eq and fix #1562 while at it, but probably not a good idea.
either way this is one possible fix
gonna try to find more

Not sure how important, but that runs into issues if both are inf. What about this?
  def __ge__(self, x) -> Tensor: return (self>x) + (self==x)
  def __le__(self, x) -> Tensor: return (self<x) + (self==x)
  def __ne__(self, x) -> Tensor: return 1.0 - (self==x)
  def __eq__(self, x) -> Tensor: return (1/((self*x*float('inf')))<1) - (self<x) - (self>x)

This is testing as slightly faster that any other workaround for me. You can also divide by zero instead of multiplying by inf but this seems more intuitive/reliable

I think it is impossible to get the correct behavior with only CMPLT, the only comparison op at the moment.

this is fixed on master with CMPEQ
both
print((Tensor([float("inf"), float("-inf"),float("nan"), 5,5,-4])==6).numpy())

print((Tensor([float("inf"), float("-inf"),float("nan"), 5,5,-4])==float("nan")).numpy())

return
[False False False False False False]


Some containers exit

I've spent a good 4-5 hours trying to figure this out, these three containers keep exiting on the m2 install.

I'm on a M1 mac if this makes any difference, i've no idea what to try.

Well, I'm sad that the author stoped supporting this project. I hope everything is fine with him, because it has great potential.
For now - use forked warden repo with M1 support:
https://github.com/drpayyne/warden-multi-arch

Duplicate of #399, #348


ld: cannot find -lsupc++

When attempting to create and build a new "GUI with main window" project:
/packages/gcc-2.95.3_2017_07_20-2/.self/develop/tools/i586-pc-haiku/bin/ld: cannot find -lsupc++
collect2: ld returned 1 exit status

Haiku version R1/beta1 (also tried with hrev52957 nightly)
using both HaikuDepot version (version 2.0 d0) and latest git version (Nov 14, 2018 commit)

location of actual files (typed by hand, hopefully no typos):

/boot/system/develop/tools/x86/lib/gcc/i586-pc-haiku/7.3.0/libsupc++.a
/boot/system/develop/tools/x86/lib/gcc/i586-pc-haiku/7.3.0/libsupc++.la
/boot/system/lib/x86/libsupc++.so

Hi there,
Thanks for you bug report. I've not got a lot of time right now to have a look, but I've seen something similar before, and that fix may help.
Open your project and list the libraries it is using from the menu. Untick the libsupc library. Now try and rebuild.
Let me know if this works or not. Development of Paladin historically was done on one architecture and not thoroughly tested on another. I hope to fix this with automated testing in future.

(assuming you're referring to Project > Change system libraries) ... unfortunately there is no libsupc++ there - screenshot below.
I'm new to Haiku so this whole dual GCC thing is pretty confusing. I do notice that, in the /lib folder nearest to where that version of ld is being invoked from (/packages/gcc-2.95.3_2017_07_20-2/.self/develop/lib), there is no libsupc++.so to begin with (nor in the /system/lib/ folder that they're all symlinked to).
I did a quick search through the project and libsupc++ appears to be hardcoded in a couple places in Project.cpp. Perhaps a platform detection issue?
Sorry I can't be of more help!
screenshot:

Just wanted to add, I played around with this a bit more, and I was able to create a project and build it by opening a terminal window and running setarch x86, and then launching Paladin from that same terminal window immediately after (versus from the Deskbar shortcut). So I guess it was a matter of getting it to use the gcc7 toolchain, instead of the old 2.95 one.

Ah that is interesting. Maybe for some reason the arch on your system is set to something else... We'll have to see if we can diagnose this in future. The architecture detection is a bit basic in the current code. Thanks for the info.

Fixed in develop as of today. libsupc++ and libstdc++ now both removed, as they are always on the global library path no matter what version of Haiku you are using. Automatically fixes existing PLD files without prompting.


Fixed issue with NewDomainNetbiosName parameter

Hi @BrianFarnhill, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


fixes packet dropping issues

these changes fix packet dropping issues.

These fixes creates a new interface which is more robust to packet dropping.  The new interface allows for the client to submit a series of packets which allows for better nonce management.


Fix typo in regulation table

 [TARIFF17] fix typo in regulation FTS table

Looks good, but we need to double check the seed data before merging

I think that we could use AttributeMutator to fix the typo from TARIC import files. I've added new commit with the class FullTemporaryStopRegulationAttributeMutator that should make this correction.


fix: Fixed lesson key for CH6INO4_NORMAL

Fix for a bug noticed by @satsie where this lesson wasn't showing on normal mode for chapter 6.

https://saving-satoshi-git-fork-daviroo-fix-in-out-9f60f3-savingsatoshi.vercel.app/en/chapters/chapter-6/in-out-4?dev=true
still gives 404 any reason why?

https://saving-satoshi-git-fork-daviroo-fix-in-out-9f60f3-savingsatoshi.vercel.app/en/chapters/chapter-6/in-out-4?dev=true

Should be this link https://saving-satoshi-git-fork-daviroo-fix-in-out-9f60f3-savingsatoshi.vercel.app/en/chapters/chapter-6/in-out-4-normal?dev=true


⚠ ClamAV has degraded performance

In 2096892, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 93 ms

Resolved: ClamAV performance has improved in d81a2ab.


GDScript compiler const optimization

Fix: #7047 <- the code snippet from the issue ran 20 times faster for ITERATIONS=10000000.
We have the optimization already, but we never used it except for const and enums.
Detail
the p_reduce_const argument is a hint for the compiler, given when the expression must be a const (const ..., enum ...). though, if reduce a variable with p_reduce_const=true (or reduce this -> const c = get_var()), the compiler try to reduce the expression to constant and if that's not possible it'll return the expression as it was, which doesn't effect the compilation.
Optimizations
const C1 = 1
const C2 = 2
const C3 = C1 + C2  ## C3 = 3
var v1 = C1 + C2 ## runtime addition even thought C1, C2 are constants
var v2 = 1 + 2 + 3  ## compile time addition
var v3 = 1 + 2 + C1 ## runtime addition : C1 is an identifier, not reducing to const

const SCENE  = C_RES + C_PATH + C_TSCN ## constant string
var scene = C_RES + C_PATH + C_TSCN ## runtime (possible to determined at compile time)
var e_0 = SomeClass.InnerClass.InnerClass2.Enum.E_VALUE ## this could be replaced with 0
## at compile time

the _parse_and_reduce_expression() method never need p_reduce_const argument and it always has to be true, for now I leave it here as this PR is a proof of concept

I remember doing similar things in the past, but it led to bugs.
Can you test that things related to autoloads and access of variables of "singleton" autoloads are not broken? :smiley:

@bojidar-bg autoload  seems working find with the patch

For the reference: reverted PR - #7390 and autoload regression issue - #7412.

Regression case:
extends Control

func _gui_input(event):
	if event is InputEventMouseButton && event.is_pressed(): #Error: Invalid "is" test: the right operand isn't a type (neither a native type nor a script).
		print("Pass")

const_optimization.zip

Could all GDScriptNativeClass instance be meta type?
replacing
https://github.com/godotengine/godot/blob/85ed2edc0685b7868813ee53d14964af9158eaf2/modules/gdscript/gdscript_parser.cpp#L5878 with:
result.is_meta_type = ClassDB::is_parent_class(obj->get_class_name(), "GDScriptNativeClass");
will fix https://github.com/godotengine/godot/pull/38132#issuecomment-618828586
@bojidar-bg @vnen

Could all GDScriptNativeClass instance be meta type?

Even if it fix this case, I'm not confident to introduce this change to 3.2, since it has been tried and always introduce some regression on cases we couldn't think of. In 4.0 this code is being redone anyway, constants will be properly reduced at compile time.

closing : GDScript 2.0 have it's implementation

So is #7047 implemented in master?

@akien-mga  yeah, I's optimized (with gdscript_analyzer) and #7047 could be closed.


Super expression must either be null or a function, not undefined

Hello,
I'm using jest with https://github.com/kriasoft/react-starter-kit and it throw: Super expression must either be null or a function, not undefined
My jest config:
"jest": {
    "rootDir": "./src",
    "collectCoverage": true,
    "verbose": true,
    "scriptPreprocessor": "../node_modules/babel-jest",
    "unmockedModulePathPatterns": [
      "fbjs",
      "react",
      "react-addons-test-utils"
    ]
  },

Also test file is:
jest.dontMock('../Header');
jest.dontMock('../../../decorators/withStyles.js');
jest.setMock('../Header.css', {use: function noop() {}, unuse: function noop() {}});

import React from 'react';
import TestUtils from 'react-addons-test-utils';
const Header = require('../Header');

describe('Header', () => {
  it('shows', () => {
    const header = TestUtils.renderIntoDocument(

    );
    const headerNode = React.findDOMNode(header);
    expect(headerNode.textContent).toEqual('Header');
  });
});

And component i test is:
import React, { Component } from 'react';
import styles from './Header.css';
import withStyles from '../../decorators/withStyles';
@withStyles(styles)
class Header extends Component {
  render() {
    return (

          Header

    );
  }

}

export default Header;

I don't think there is anything wrong with jest. It must be with your setup or your tests. Are you using the latest versions of react, node and jest? From the example you posted I don't know where the error is coming from – do you have a stack trace?

$ ./node_modules/.bin/jest -v
v0.5.8
$ node -v
v4.1.0
$ npm list react
└──<EMAIL_ADDRESS>
No. i don't have a stack trace even in verbose mode

Would it be possible for you to publish your changes based on the starter kit so I can repro this myself?

Would it be possible for you to publish your changes based on the starter kit so I can repro this myself?

@cpojer: https://github.com/teosz/test-problem-reproduce

For some reason react is being mocked even though it shouldn't. This is weird.

Seems like setMock really, really sucks :)

https://gist.github.com/cpojer/72093d149e725a5e6082 this patch can make your tests work properly. In short setMock sucks and doesn't work as well as it should. I'm hoping to fix this soon. I added a mock using the new moduleNameMapper feature which will match all .css files and use the same stub for them. This now makes your tests work. You might also be able to turn this into a pull request for the react-starter-kit :)


Starting date of ESM simulations: 2015 or 2020?

Hello,
The current version (2023-12-08) of emissions files seem to imply 2020 as the starting date for ESM simulations.
What is the starting year that we agreed on for the ESM simulations, 2015 or 2020?

If 2015, input4MIPs files usually includes the 2015 monthly emissions in addition to 2020. A workaround for the ESM modellers would be to interpolate back from 2014 using the historical/CEDS emissions to generate the 2015-2019 leg.

If 2020, which SSP should be used as initial conditions from the end of 2019?

Thank you.

Hello,
I might have found my answer in a draft: RESCUE provides an extrapolation of CEDS until 2019. Where can we download it for ESM testing?
Thank you.

Hi @TimotheeBrgs ,
To address what you are raising, we are including the gridded 2015 emissions also in the next round of gridded scenario files, ie the files we are running our last bits of validation on (and intend to upload to the bsc ftp server this week), will have the following time dimension:
CFTimeIndex([2015-01-16 00:00:00, 2015-02-15 00:00:00, 2015-03-16 00:00:00,
             2015-04-16 00:00:00, 2015-05-16 00:00:00, 2015-06-16 00:00:00,
             2015-07-16 00:00:00, 2015-08-16 00:00:00, 2015-09-16 00:00:00,
             2015-10-16 00:00:00,
             ...
             2100-03-16 00:00:00, 2100-04-16 00:00:00, 2100-05-16 00:00:00,
             2100-06-16 00:00:00, 2100-07-16 00:00:00, 2100-08-16 00:00:00,
             2100-09-16 00:00:00, 2100-10-16 00:00:00, 2100-11-16 00:00:00,
             2100-12-16 00:00:00],
            dtype='object', length=120, calendar='noleap', freq=None)

ie monthly timesteps for the years 2015, 2020, 2030, 2040, ... 2100 .

Hi @coroa, thank you for your prompt and clear answer. This will fix the issue.


Agent not connecting on Docker 20.10.21

Hardware description:
Nucleo STM32H743zi
RTOS:
Zephyr 2.6
Installation type:
Micro_ros_setup, micro_ros_agent
Version or commit hash:
Humble

Steps to reproduce the issue

Start agent: docker run -it --rm --net=host  microros/micro-ros-agent:humble udp4 --port 8888  -v6
Change IP of edge in microros_transports.h  to agent IP
Edge shows waiting for connection.
Wireshark shows edge requesting a connection to agent

Agent shows:

Expected behavior
Agent should accept and connect to edge.
Actual behavior
Agent does not connect to edge.
Additional information

Tested configuration on a different computer and could not reproduce the actual behavior - will continue to debug networking side.


Added a helpful link

Hey, I have added a helpful reference link for the python tutorial in the Additional Resources & Further Reading section that I think will best add to your content and give your readers a more diverse understanding of the topic. I hope you will like this. Thank you.

你好，邮件已经收到，将尽快给你回复。

Actually, that looks like a pretty useful one. Thanks!

你好，邮件已经收到，将尽快给你回复。


Transposing x,y coords correctly for interpolated ims

Fixes #8

Codecov Report

Merging #11 into master will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #11      +/-   ##
==========================================
- Coverage   57.87%   57.75%   -0.13%
==========================================
  Files           5        5
  Lines         330      329       -1
==========================================
- Hits          191      190       -1
  Misses        139      139

Impacted Files
Coverage Δ

sentinel_to_zarr/sentinel_to_zarr.py
34.61% <0.00%> (ø)

sentinel_to_zarr/napari_sentinel_to_zarr.py
95.45% <0.00%> (-0.05%)
:arrow_down:

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 f0dd500...5a9f80b. Read the comment docs.


Ouster lidar - IMU error?

Hello here, the IMU am using have the same coordinate definition with ouster os1-64, which is front-left-up, thus I change the "extrinsicRot" and "extrinsicRPY" to identity matrices, and debug IMU according to the video, everything's fine. However, when I play my recorded bag, the result is a disaster, which seems to be IMU error.

And the terminal gives me

Do you have any suggestions? By the way, I've tested the same IMU with ouster using Lego-Loam, which is fine.
If you are interested, the recorded bag is
https://drive.google.com/file/d/10zUV7I8Mh7suLumHvFeLKOO-yTBr19wj/view?usp=sharing

It seems that the cloud from your lidar is not in REP format.
Change code in projectPointCloud() to
thisPoint.x = -laserCloudIn->points[i].x;
thisPoint.y = -laserCloudIn->points[i].y;
thisPoint.z = laserCloudIn->points[i].z;

You will notice that the IMU prediction is very bad, this is caused by bad time sync between the lidar and IMU.

Could you explain why this bad time sync happen? Cause from the terminal time debug, everthing seems fine compared with ur ouster dataset, I also tried using sim time for implementation and get bad results. I use a very simple and low-cost IMU for tests (lower than $50) with 200Hz publish frequency, should it be the reason?

It is not an IMU problem, it's Outer. Ouster lidar sometimes gives me timestamp in the future, sometimes gives timestamp a few seconds behind the system time.

Ok, weird, as am using PTP sync, the timestamp is actually given by external sources, how could Ouster given timestamp in the future or behind the system time, hard to understand.

how could Ouster given timestamp in the future or behind the system time, hard to understand.
That's also what confuses me. Ouster lidar is not stable at all.

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

Ok, thx, I thought I've successfully synced my lidar and imu, cause a friend of mine have generated  a beautiful loop map with my recorded bag,

I use a DJI manifold2 to record rosbag, with a DJI router connecting different lidars to manifold.

Just a few things to notice when applying LIO-SAM with your recorded bag

You should sync the IMU and lidar 'precisely' either by time reference(GPS, PTP, whatever) or by changing the timestamp of both IMU and lidar to ros::Time::now(), both works fine for me.
Check ur coordinates definition
Make sure you have calibrated ur IMU and modify the param setting, especially when you are using a pretty simple one(for me, a $30 IMU)
If you wanna record ur GPS with IMU, and u want to omit the confusing time sync (self decoding, serial port processing), u better record ur bag like what was done in park.bag.

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

@dllu
I connect Ouster to the NUC directly. I know that it takes a few minutes to establish sync when the sensor is booted. After the timestamp is synced using PTP, however, I would get -0.5 ~ +0.5 timestamp difference when running rostopic delay /lidar_topic. Most of the time, the delay is around +0.1.

@YushengWHU
It's good to know it's working now. How much delay do you encounter in your point cloud when you run rostopic delay?

@YushengWHU
It's good to know it's working now. How much delay do you encounter in your point cloud when you run rostopic delay?
Well, that's a point, I find that my /imu delay is 0s, while the /lidar_points delay is  2.15s on average

@YushengWHU
It's good to know it's working now. How much delay do you encounter in your point cloud when you run rostopic delay?
Well, that's a point, I find that my /imu delay is 0s, while the /lidar_points delay is  2.15s on average

That's a very large delay... My average lidar delay is only around 0.125s.

@YushengWHU
It's good to know it's working now. How much delay do you encounter in your point cloud when you run rostopic delay?
Well, that's a point, I find that my /imu delay is 0s, while the /lidar_points delay is  2.1

@YushengWHU
It's good to know it's working now. How much delay do you encounter in your point cloud when you run rostopic delay?
Well, that's a point, I find that my /imu delay is 0s, while the /lidar_points delay is  2.15s on average

That's a very large delay... My average lidar delay is only around 0.125s.

Sure, and  I want to test whether the 2.15s delay is steady or not, if yes, I can keep sync 'precisely' with IMU, unfortunatelly, the delay is step by step increasing after booted, for my case, around a 0.001s increasing per minute.

@YushengWHU
你好,我遇到了类似的问题,如你图片所示, 跑起来就飞了, 预积分也报那个警告
请问你是怎么修复的?我看到你的note了,我用的ros::Time::now()

@YushengWHU
你好,我遇到了类似的问题,如你图片所示, 跑起来就飞了, 预积分也报那个警告
请问你是怎么修复的?我看到你的note了,我用的ros::Time::now()

你用的os1还是os2 如果是os1你要按作者说的方式改一下坐标轴，这个警告都是坐标轴的问题

@YushengWHU,
我用的是os1, 看ouster datasheet, 它又有sensor frame, lidar frame, ouster输出的点云好像又是sensor系下
能加下微信好友吗?<PHONE_NUMBER>0, 想交流下,

@YushengWHU,
我用的是os1, 看ouster datasheet, 它又有sensor frame, lidar frame, ouster输出的点云好像又是sensor系下
能加下微信好友吗?<PHONE_NUMBER>0, 想交流下,

你看上面作者说的试试看，应该就可以了，我的没问题

@YushengWHU
你用的IMU输出的orientation参考的世界坐标系是哪个? ENU  NED 还是初始时刻

@YushengWHU
你用的IMU输出的orientation参考的世界坐标系是哪个? ENU NED 还是初始时刻

车体坐标系是前右上

@YushengWHU @dllu I've been having issues trying to make this work with an Ouster OS1, I have tried the solutions suggested in this issue, re-syncing timestamps, trying different frame coordinations in params.yaml but to no avail! The problem is after a few seconds of playing the bag, the base_link drops altitude and in it keeps decreasing in Z axis!
I've opened this issue here #111 but the author's comments didn't offer much help, could you maybe take a look and let me know what you think the culprit is?
Thank you!

It seems that the cloud from your lidar is not in REP format.
Change code in projectPointCloud() to
thisPoint.x = -laserCloudIn->points[i].x;
thisPoint.y = -laserCloudIn->points[i].y;
thisPoint.z = laserCloudIn->points[i].z;

You will notice that the IMU prediction is very bad, this is caused by bad time sync between the lidar and IMU.

Which REP are you referencing for the orientation of pointclouds?

@bromeara

Which REP are you referencing for the orientation of pointclouds?

I believe he is referencing to REP 103 frame conventions
https://www.ros.org/reps/rep-0103.html#coordinate-frame-conventions

@andoreso I also thought so but also I found that curious because it doesn't define a default coordinate frame for lidar sensors only for bodies. With the OS there are 3 frames published, os_sensor which is the parent of the other two frames is located at the base of the lidar with the X facing away from the cable port(Probably is normally facing the front of the vehicle but maybe its the cause of the problem), the os_lidar x-axis is then aligned with the encoder count which is facing towards the cable connector(The front of the lidar_sensor but probably not the vehicle) and then os_imu has the frames aligned to its axis. These seem to comply with 103, and I maintain a fork of the ouster driver so I was curious if there was actually a REP I should be complying with.

@bromeara
I understood from the standard that all coordinate frames should be transformed to the axis conventions with:
X = forward
Y = left
Z = up
So the os_sensor frame is in the correct frame but I believe that lio-sam ignores transforms and uses the raw PointCloud2 that is in the os_lidar frame. So the transform should be manually applied to the point cloud. I think the easy solution is to subscribe to the point cloud invert the xy values and republish it, but there may be a better solution.
Also please take what I said with a grain of salt because I just started testing lio-sam with a lidar but the inversion of x and y has worked for me in other lidar projects using ouster lidar.

Ouster has released a new firmware (v2.0), is LIO-SAM compatible with the new changes mentioned here?

Ouster has released a new firmware (v2.0), is LIO-SAM compatible with the new changes mentioned here?

We have run it on v2.0 and this is more of a question for your ouster ROS driver than this library

Hello here, the IMU am using have the same coordinate definition with ouster os1-64, which is front-left-up, thus I change the "extrinsicRot" and "extrinsicRPY" to identity matrices, and debug IMU according to the video, everything's fine. However, when I play my recorded bag, the result is a disaster, which seems to be IMU error.

And the terminal gives me

Do you have any suggestions? By the way, I've tested the same IMU with ouster using Lego-Loam, which is fine.
If you are interested, the recorded bag is
https://drive.google.com/file/d/10zUV7I8Mh7suLumHvFeLKOO-yTBr19wj/view?usp=sharing

hi,could you share me the dataset and config . just for the test , be easy.thanks.

Hello here, the IMU am using have the same coordinate definition with ouster os1-64, which is front-left-up, thus I change the "extrinsicRot" and "extrinsicRPY" to identity matrices, and debug IMU according to the video, everything's fine. However, when I play my recorded bag, the result is a disaster, which seems to be IMU error.

And the terminal gives me

Do you have any suggestions? By the way, I've tested the same IMU with ouster using Lego-Loam, which is fine.
If you are interested, the recorded bag is
https://drive.google.com/file/d/10zUV7I8Mh7suLumHvFeLKOO-yTBr19wj/view?usp=sharing

hi,could you share me the dataset and config . just for the test , be easy.thanks.

leave me your email, I will send all the required to you.

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

Ok, thx, I thought I've successfully synced my lidar and imu, cause a friend of mine have generated a beautiful loop map with my recorded bag,

I use a DJI manifold2 to record rosbag, with a DJI router connecting different lidars to manifold.

<EMAIL_ADDRESS>

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

Ok, thx, I thought I've successfully synced my lidar and imu, cause a friend of mine have generated a beautiful loop map with my recorded bag,

I use a DJI manifold2 to record rosbag, with a DJI router connecting different lidars to manifold.

<EMAIL_ADDRESS>
青楼跑的，数据不小，还有一些别的数据，有空你加我微信IchliebeYe，你来我这拷一下就行，我在GPS中心

Hello here, the IMU am using have the same coordinate definition with ouster os1-64, which is front-left-up, thus I change the "extrinsicRot" and "extrinsicRPY" to identity matrices, and debug IMU according to the video, everything's fine. However, when I play my recorded bag, the result is a disaster, which seems to be IMU error.

And the terminal gives me

Do you have any suggestions? By the way, I've tested the same IMU with ouster using Lego-Loam, which is fine.
If you are interested, the recorded bag is
https://drive.google.com/file/d/10zUV7I8Mh7suLumHvFeLKOO-yTBr19wj/view?usp=sharing

I have met the same trouble,could you tell me what method you used to make it?

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

Ok, thx, I thought I've successfully synced my lidar and imu, cause a friend of mine have generated a beautiful loop map with my recorded bag,

I use a DJI manifold2 to record rosbag, with a DJI router connecting different lidars to manifold.

Could you tell me how to sync my bag?
Thank you !

the quality of PTP time syncing depends on the ethernet hardware you're using, and whether you're using a router or switch. It can also take a few seconds (or a few minutes) to establish stable time syncing.

Ok, thx, I thought I've successfully synced my lidar and imu, cause a friend of mine have generated a beautiful loop map with my recorded bag,

I use a DJI manifold2 to record rosbag, with a DJI router connecting different lidars to manifold.

Could you tell me how to sync my bag?
Thank you !

你是说咋把雷达和IMU同步是吧，你用的啥雷达和IMU，有啥具体问题加我微信问，IchliebeYe

It seems that the cloud from your lidar is not in REP format.
Change code in projectPointCloud() to
thisPoint.x = -laserCloudIn->points[i].x;
thisPoint.y = -laserCloudIn->points[i].y;
thisPoint.z = laserCloudIn->points[i].z;

You will notice that the IMU prediction is very bad, this is caused by bad time sync between the lidar and IMU.

Wouldn't this be configurable in the imu -> lidar portion of the config yaml file as well?

@YushengWHU
老哥，能说一下你用的什么型号的IMU呀，想整一个便宜的玩玩。多谢啦

我用的xsens的mti680G， 2W3，便宜的你就淘宝搜ROS IMU，整个200块的就行，我以前买过200块的，liosam也能跑

想请问您一下 我是用的3dm gx5 25imu 为什么从第一秒就开始飞起来了呢

老哥，你的微信加不上啊。。

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

我是3dm-gx5-25 我是xyz和欧拉角没有对上...一启动就z轴飞天 你是用的microstrain官方驱动吗

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

方便联系一下嘛

IchliebeYe

我微信就这个啊。。IchliebeYe

你加楼下老哥的微信吧，我的是时间同步没有成功。。。。

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

我是3dm-gx5-25 我是xyz和欧拉角没有对上...一启动就z轴飞天 你是用的microstrain官方驱动吗
是的，官方驱动，老是有问题。。。时间同步不太成功。。。

IchliebeYe

我微信就这个啊。。IchliebeYe

can not add you either

老哥，你的微信加不上啊。。

兄弟 你跑通了嘛 用的什么型号的imu？

和作者的差不多型号的，3dm-gx4-25,不过时间同步没有成功，也正在问作者。。。

我是3dm-gx5-25 我是xyz和欧拉角没有对上...一启动就z轴飞天 你是用的microstrain官方驱动吗

兄弟怎么解决的，我用test your slam那篇论文里面的subt-t-tunnel数据集，一跑起来就起飞，不知道该怎么解决

Hi @YushengWHU
Regarding the PTP for ouster lidar, you can actually do a little hack on the ouster_ros package to make it to use ros::Time::now() when sending out /ouster_cloud_node/imu and /ouster_cloud_node/points, then the future or outdated timestamp issue will be ruled out.
Best, Samuel

Hi, I saw your reply about changing ouster_ros driver to make sync lidar point to ros::Time::now(). Could you give some help. I don't know where to change the code. Thank you so much.

This is the line you're looking for:
https://github.com/ouster-lidar/ouster-ros/blob/d48c331cfa299d3c85c5182bb38dbaf746965a04/launch/record.launch#L26

This is the line you're looking for:
https://github.com/ouster-lidar/ouster-ros/blob/d48c331cfa299d3c85c5182bb38dbaf746965a04/launch/record.launch#L26

Thank you for your kind reply. I just found my ouster-ros version is old.  I will try the new version. Thank you again.

Yeah, the driver went through some large restructuring, but (in my limited experience) works very well

@YushengWHU
Hi, I am using ouster os1 ...can you please share your yml file ? thanks

@YushengWHU Hi, I am using ouster os1 ...can you please share your yml file ? thanks

sorry, its really a long time ago, and I dont have that yaml file now, even my os1 is broken.

IchliebeYe

我微信就这个啊。。IchliebeYe

加不上。你是微信国际版的吗


Problem with EMOTIC dataset

I found almost half of the bounding boxes are not correct where the boxes do not bind the full person after I visualized the pictures.

Take 011xa4rukq1oga5il9.jpg as an example. The coordinates of the old man are [246, 90, 300, 260], it however just bind half of the old man.

Take 011xa4rukq1oga5il9.jpg as an example. The coordinates of the old man are [246, 90, 300, 260], it however just binds half of him.

@chenxindaaa Have you tried annotating the images and then training the model?

Closing due to inactivity.
Please feel free to reopen the issue.


[Task]: Hotshard investigation for mixpanel

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

cc: @rohan-arthur kindly take note.


Fix for requiring data sections with more than 2^12 entries.

Adding this WIP now to run it through CI.
Closes #3161.

I'm abandoning this approach in favour of fixing #3347 and #3346 first.


Inferred properties aren't detected in 3.0.3 documents

components:
  schemas:
    MyType:
      type: object
      properties:
        someName:
          type: string
      required:
        - anotherName /// <--- non-existent required field

The generator generates both someName and anotherName fields. The anotherName field will be of type OpenAPIRuntime.OpenAPIValueContainer. someName will be of the correct type.
OpenAPI should either error or ignore such stuff in the required values.

It is alpha.1. It does not emit any diagnostics.

And this test is passing, so this is really interesting: https://github.com/apple/swift-openapi-generator/blob/main/Tests/OpenAPIGeneratorReferenceTests/SnippetBasedReferenceTests.swift#L216
Your case must be somehow different to the one we have in our tests, can you provide more details?

@czechboy0 Here a full document that reproduces this:
openapi: 3.0.3
info:
  title: API
  description: |-
    description
  termsOfService: http://some.thing/terms/
  contact:
    email<EMAIL_ADDRESS>  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  version: 1.0.0
externalDocs:
  description: Find out more about API
  url: http://some.thing
servers:
  - url: https://some.thing
paths:
  /reports/id/{id}:
    get:
      summary: Get an existing report by ID
      description: Get an existing report by ID
      operationId: getReportById
      parameters:
        - name: id
          in: path
          description: ID of report to return
          required: true
          schema:
            type: integer
      responses:
        200:
          description: Report exists and is returned
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Report'
        400:
          description: Invalid ID supplied
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
  schemas:
    Report:
      type: object
      properties:
        file_type:
          type: string
          enum: [a]
        report_category:
          type: string
          enum: [b]
      required:
        - type
        - category

Ok found it, seems it works in 3.1.0 documents fine, but not in 3.0.3, for some reason. We use OpenAPIKit for this, so tagging @mattpolzin for help, I suspect the fix will have to come there.

Wow that was fast, thank you @mattpolzin! 👏
Before we close this issue, @MahdiBM can you update to latest dependencies in your checkout, regenerate, and verify the issue is fixed, before we close it here? 🙏

Nevermind, i see the warning.

Thanks @MahdiBM for filing this and helping us get it addressed before 1.0 🙏 And thank you @mattpolzin for the speedy fix, as always! 👏


Link to upstream svcat install instructions

The original svcat repo has been archived and svcat lives in the upstream Service Catalog repository now.
Fixes #334

Merging without CI, docs only change.


[FeatureRequest] Allow array of ElementSelector

First: thanks for this great tool, you made an amazing work.
Suggestion: allow for Array of ElementSelector.
When describing an element, I would like to be more precise by having a list of similar requirements.
That would be useful for all the YamlElementSelectorUnion: below, above, leftOf, rightOf, containsChild
For example: click on the element that contains all those children.
    containsChild:
        - text: "Text in a child view 1"
        - text: "Text in a child view 2"

Today I will have the error Cannot deserialize value of type maestro.orchestra.yaml.YamlElementSelector from Array value (token JsonToken.START_ARRAY)

@StanKocken Would containsDescendents work? https://maestro.mobile.dev/api-reference/selectors

Thanks, I did not use Maestro for a while so I cannot be sure 100%, but yes it seems this new containsDescendents seems to address this problem, thanks!


TUP-4570: fix the long type converter issue

https://jira.talendforge.org/browse/TUP-4570

I'm not seeing that these changes are being reviewed by others, and I don't see a junit test for this bug. Every fix needs to have a junit test that shows the problem.

The issue is caused by the empty string pattern for long type, it's about the ui model value of column pattern in talend ui schema config. We can add a junit to test it by only setting a fake empty string pattern if it's necessay. And now we only test it on component-0.12 and daikon-0.11 as https://jira.talendforge.org/browse/TUP-4851 make it difficult to test studio and component together. We will add the junit after TUP-4851's ok.

You don't need to worry about adding a unit test for this in the studio. You should add a unit test here in components for any fix you make in components. You have to keep in mind the new components will be used by things other than the studio. The problem with TUP-4851 will not prevent you from adding a unit test here.

https://github.com/Talend/components/pull/161
Have added the case, please merge it.


How to get the width and height of a video

How to get the width and height of a video

https://github.com/JuanBindez/pytubefix/pull/92


System.Memory binding redirect needed following update to 1.29

Similar to issue #2055
See that issue for the specific environment details
After upgrading the nuget package to 1.29 got:
Could not load file or assembly 'System.Memory, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
Note I worked around by adding a binding redirect
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentAssembly>         <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>     </assemblyBinding>
Therefore this issue is "solved" until it likely happens again with the next upgrade. Posting this incase someone else runs into this - like me for example :)

Which .NET version aka. TFM are you using?

Hi, it is 4.7.2 - Note that a single project likely won't have the issue.
See issue https://github.com/microsoft/playwright-dotnet/issues/2055
When I reported it, I uploaded a zip file with two projects that I suspect you can use to replicate this. It's the same basic problem (nuget DLL hell).

Hi, sorry for the delay!
I worked around this the same way I worked around issue https://github.com/microsoft/playwright-dotnet/issues/2055  -binding redirect (adding System.Memory), the below is what I am currently using.
I have a note that System.Text.Json is likely to be problematic following a Playwright update. and needs binding redirects for everything that it references.
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentAssembly>         <assemblyIdentity name="System.Text.Json" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>     </assemblyBinding>     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentAssembly>         <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>     </assemblyBinding>     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentAssembly>         <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>     </assemblyBinding>     <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">       <dependentAssembly>         <assemblyIdentity name="System.Collections.Immutable" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />         <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />       </dependentAssembly>     </assemblyBinding>   </runtime>

Looks stale and resolved with the workaround above, closing by that. For further issues please file a new issue.


Please report this session_id: [yellow bold]b92d8056-2ea1-11ee-a95a-acde48001122[/]

I'm following this example: https://github.com/jina-ai/langchain-serve/tree/main/examples/rest and get an Failed on building Docker image. error
Code works properly when deploy to local.
local cmd: lcserve deploy local app --env .env
deploy cmd: lcserve deploy jcloud app --secret .env --config deploy.yaml

Hi @Arcadia822, apologies about missing this, I moved it to the appropriate repo now.
Can you please enable verbose logging by passing the --verbose flag during deployment to jcloud? That would help us with debugging.  If you're on an arm64 arch, this might be relevant.


Add Chinese (zh) collation method

I guess the original languages.zj is misspelled since zj isn't mapped to any language according to https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes. Thus I changed it to zh.
The tailor_string() method is modified so that it can accept the <* operator.
It looks the [last regular] and '\uFDD0A' notations are not supported (see common/collation/zh.xml#L33-L35). I don't quite understand them but the current implementation works.
Also fixed the dependencies in Makefile.

Perhaps the Chinese collection function is too long (about 60% of lines in lua-uca-language.lua). It is better to make it a standalone file?

Thanks, that looks great! I am sure there are other things that I initially didn't implement, as I was already overwhelmed by the basic functionality of the UCA algorithm.
I've moved the Chinese library to a standalone file, as I hoped that it will make some speed difference, but it doesn't seem so. Anyway, I've also made some other changes, as I found that the names  used in require in lua-uca-collator.lua were wrong. If everything works well, I can make a new CTAN release.

Ah, yes lua-uca.tailoring is created when you install the package using Luarocks. I've added the command that will install the package before testing to the Makefile, so it should work now.

Yes, everything is working fine now.

OK, so I guess I can make a new release to CTAN?

OK, so I guess I can make a new release to CTAN?

Yes. Thanks!

OK, done :)


Processing in data collator

Hi Tingofurro,
Thanks for sharing a nice simplification repository.
I have a query for the explanation of the processing happening in the data collator:
def cc_news_collate(inps):
batch_paras = []
for inp in inps:
text = inp["text"]
paragraphs = sorted(text.split("\n"), key=lambda p: abs(p.count(" ")-35))
batch_paras.append(paragraphs[0])
return batch_paras
Why are you only appending the largest paragraph (if I am correct) rather than the complete text?
Looking forward to your response.

Hello @MehwishFatimah,
Good question. I believe that project development we used a slightly different dataset of texts. However, to reduce dependencies in the public repository we set up the code to use cc_news.
The code splits the text on new line characters, but this can be noisy in terms of extracting paragraphs, so we select the "paragraph" that has the closest number of words to 35 (a bit arbitrary) but with an objective to avoid paragraphs that are too short (likely to be single sentences) or too long (which could cause memory errors).
It is a bit arbitrary, and if you have a source of better paragraphs (or closer to the domain you are trying to simplify), I recommend switching to that.
Thanks for reaching out! :)
Philippe

Thank you so much for your detailed response. It means I can use multiple paragraphs for the training (if GPU memory allows). Would you like to share some other observations, e.g., how long text caused memory errors or the disadvantage of having a single sentence? Just for learning :)

Hey @MehwishFatimah,
Happy to give some ideas, training with RL can be finicky:

I recommend printing outputs every X minutes into a log. That way you can look back and check that training is going well, for example: (a) the different candidates are distinct (otherwise the training has collapsed), (b) average reward is increasing, (c) individual reward components correspond to expectation (otherwise the generator has learned to "trick" the rewards, which happens a lot)

Play around with hyperparameters: particularly in this work we found that the k (the number of candidates generated) was very important and the higher the better for training stability (whatever you can afford to put on the GPU). Hyper-parameters are not independent, and for instance: switching to half-precision requires finding a new learning rate, etc. It can be the difference between a good model and no learning.

Training is highly non-linear: unlike supervised training where you see the loss slowly decay, in RL training it is hard to know whether a plateau is final. In some cases, a model will all of a sudden get unstuck and learn to use a strategy that works well. I recommend letting good runs go for longer (sometimes I trained a model for 20 days), in other cases, kill runs early.

Try different initial conditions: they matter a lot because they set up the initial candidates the model learns from. Try different initial language models (for instance we switched from GPT2-base in Summary Loop to GPT2-medium in Keep it Simple and saw a large difference), finetune on the copy task to different levels, or even restart from a previously successful run.

I hope this helps, and that you're able to train your models!


ordered_class_elements should have per-item sorting setting and consider sort_algorithm as default for them

Problem description
There is no way to switch on/off sorting on per-item basis. sort_algorithm works for all of them, all at once: either sort them all by 'alpha' or sort them all 'none'. One can't set another sorting for some items.
Feature request
E.g., it could be useful in such case:
'order' => ['use_trait', 'case', 'constant_public', 'constant_protected', 'constant_private', 'property_public', 'property_protected', 'property_private', 'construct', 'destruct', 'magic', 'phpunit', 'method' => ['sort_algorithm' => 'none']],
'sort_algorithm' => 'alpha',

I mean sort everything except any methods. Or other cases - in any combinations that are allowed by this setting syntax.
It looks totally reasonable: to have one option as a default for non-mentioned ('sort_algorihm') while another could re-define, overwrite its behavior by per-item setting.
I guess this feature could help resolving other issues reported here in issue queue, such as #2746 (if applied together with #6360 ) and partially #4513 .

I think 2746 and 6360 don't benefit from none sorting, these ask for being another/special way of sorting (so not do-not-sort) of some elements.
If you not configure  'method' => ['sort_algorithm' => 'none'] but leave method out of the configuration, doesn't this already do what you want?
I struggle to see how none would work otherwise as when you configure every type of element to get sorted expect one type, where should elements of that type end up if not at the end of the class?
Can you maybe provide an PHP examples with expected input, config and output?

Thanks for your response, I appreciate.

If you not configure 'method' => ['sort_algorithm' => 'none'] but leave method out of the configuration, doesn't this already do what you want?

I've checked it locally - and looks like I got it wrong. I thought that its expected behavior - but according to your reply (and my test that I've created to illustrate it) I understood that we should clarify it.
Please review the test I've added to #6592 - and let's investigate whether it's expected or not.

It is kind of expected, as the feature was indeed build as sort everything of the same type. We can keep this issue as a valid RFC :+1:


Text annotation not resizing on edit via properties panel

Closed via https://github.com/bpmn-io/bpmn-js/commit/100f3fb2ee6373cd4b7ad0b76e520a1afb70887e.


fix(UI): use default params on template submit form. Fixes #6779

Testing:

Explanation of test steps:

Submit template from workflow templates view with default main parameter. New behavior: the default parameter value appears in the UI.
Submit entrypoint template from workflow templates view with no default parameters. The default parameter value appears in the UI for message 1, but is successfully overridden on submission.

This is the arg-defaults workflow template:
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: arg-defaults
spec:
  entrypoint: main
  templates:
    - name: main
      inputs:
        parameters:
          - name: message
            default: "main-default"
      dag:
        tasks:
          - name: say
            template: say-message
            arguments:
              parameters:
                - name: message2
                  value: "{{inputs.parameters.message}}"

    - name: say-message
      inputs:
        parameters:
          - name: message1
            default: "param-default"
          - name: message2
      outputs:
        parameters:
          - name: messages
            valueFrom:
              path: /tmp/messages
      script:
        image: alpine:3
        command: [/bin/sh]
        source: |
          echo "{{inputs.parameters.message1}}" > /tmp/messages
          echo "{{inputs.parameters.message2}}" >> /tmp/messages

Signed-off-by: Kenny Trytek<EMAIL_ADDRESS>
Tips:

Maybe add you organization to USERS.md.
Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it does not need to pass
Sign-off your commits to pass the DCO check: git commit --signoff.
Run make pre-commit -B to fix codegen or lint problems.
Say how how you tested your changes. If you changed the UI, attach screenshots.
If changes were requested, and you've made them, then dismis the review to get it looked at again.
You can ask for help!

Closing and reopening to trigger checks again. There are no Go changes in this PR, so go lint check must be flaky?

LGTM!


chore: Update associatePublicIPAddress to not be set in the launch templets

Fixes #N/A
Description

https://github.com/aws/karpenter-provider-aws/commit/9836cbe5f4256b96d5d512f1f8e254b596fcea41 Set associatePublicIPAddress to false on failure instead not setting any value for launch templates.

How was this change tested?

N/A

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

3 of 6 (50.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 82.231%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/providers/launchtemplate/launchtemplate.go
0
1
0.0%

pkg/providers/subnet/subnet.go
3
5
60.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
5410

Relevant Lines:
6579

💛  - Coveralls


some more protocol decoding

I am working on ARM version of wch-link. It seems when using the WCH-Link utility the same protocol is used
So here is the 0x0c cmd. Maybe this can help on the RISC part too.
request:
0x81    0x0C   0x02   Target CPU   speed
response:
0x82     0x0C     0x01  OK
Target CPU 0x04 = F103
0x08 = F203
Speed 1..3 means slow medium fast
Speed 0 maybe default?
OK response = 0x01

Many thanks:
I'll add the docs.
https://github.com/ch32-rs/wlink/blob/085b39b8015c5cbbda8cfe197478ab3217e1666d/src/operations.rs#L32-L36

I need a better scheme to document the protocol. @septs Any ideas?

close as completed


[Feature Request]: Implementation for FileUpload component

Description
Docs describe a file upload component but it appears this component is not directly available in the library. File upload is non-trivial to implement and the documented example for multiple file upload does not appear to be replicable externally since TokenGroup does not allow for components within Tokens.
Since file uploaders are a common need and consumers currently require additional effort to implement them, I think it would be great if we could have a FileUpload implementation directly available in the library that follows the specification described in the docs.
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate requests

Hey Jason,
thank you for reaching out. That's correct! The systems describes the user experience on the website, but it does not provide an implementation as part of the library. We are aware of this feature request, but we don't currently have short-term plans to work on it. For now, you can get around by creating your own adjacent component using a button and a custom file list implementation.
We will use this issue to track interest in having a FileUpload implementation.
Thank you,
Florian

Given the commonality of this feature, its absence could be a blocker for adoption for us. Love the ease-of-use of the existing components though!

Agreed, was really excited to see how clean the file upload example was only to find out it wasn't actually part of the components. In the short term, if the image in the example was generated and not just a mock, would it be possible to paste the source code here?

@FlorianDr Any updates on this request?  My team was really excited to use this.

Hello!
There are no particular plans for this request. It stays here for visibility, but not prioritised in any way
P.S. Best is not to ping individual people, because they may change their projects. Just leave a comment and our team will be notified regardless.

FWIW, I've been working on a file uploader implementation if anyone is interested: https://github.com/jasmaa/cloudscape-file-uploader

Hello!
Cloudscape team is working on implementing the file upload component, please bear with us!


Ability to add 3bot packages in a subfolder of a github repo

Description
Currently it is only possible to add a package in the root of a github repo using the giturl parameter in the packagemanafer add method. using a giturl like git_url="https://github.com/threefoldfoundation/tft-stellar/tree/master/ThreeBotPackages/activation-service" would be nice since we can keep functionally related packages together in a single repo. Repo explosion makes things unclear and hard to mamage.

should be solved after merging this https://github.com/threefoldtech/js-sdk/pull/1394

@Dina-Abd-Elrahman Is this also documented?


[CI:DOCS]first pass at adding swagger docs for api

Signed-off-by: baude<EMAIL_ADDRESS>

/hold cancel


Lets make World Mercator, Web Mercatir, UTM and other mercators data work together!

Its pretty nice work. It would be problem with terrain providers, but globus engine do  allow to make it. So less words more works!

Stopped for now.


Build failure

Hi,
I have just tried to rebuild a project of mine and cargo check failed with
error: array lengths can't depend on generic parameters

This can be reproduced by cloning the dev branch and running cargo check. (It looks to be an issue in the matrixmultiply dependancy.
Hope this helps!

Aha, it requires a nightly compiler to get this issue.

See also https://github.com/bluss/matrixmultiply/issues/50 and https://github.com/rust-lang/rust/issues/67743


Train code

Nice jobs!
When will you release the training code?

Yes, the training code will be released.


Automated image conversion to AVIF/WebP

Is your proposal related to a problem?
Our current Wagtail Media Library has nearly 10,000 images (stored in an Amazon S3 bucket, served through Wagtail CMS). Images are primarily served as JPG or PNG files. These formats result in larger file sizes, which not only impacts load times but also increases data transfer and energy consumption, reducing the overall sustainability of our site.
Describe the solution you'd like
To address this, we need to automate the process of converting these images to the more efficient AVIF format, enabling us to significantly reduce image sizes and the associated environmental footprint of our website. An automated solution that converts all current images, but then works when an image is uploaded will streamline the conversion and reduce the burden on our team, making this improvement both scalable and sustainable over time.
Additional context
There would need to be a fallback option for older browsers e.g. WebP
Considerations around the impact on size of Amazon Bucket required also needs to be addressed.
Working on this
I am looking to developers for a solution to this that is part of core Wagtail and would also vlaue any technical input on whether or not a fallback WebP, can be generated on the fly to avoid duplications within Amazon Bucket storage.
Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Hello, I have experience working with media formats conventions from my previous job, I might be able to do this, could you please assign this to me


Sidekiq 5.0 support

There were breaking changes as of sidekiq 5.0 that affect request_id. Namely, some class renaming around logging:

Sidekiq::Middleware::Server::Logging -> Sidekiq::JobLogger

That removed class appears to be used in https://github.com/remind101/request_id/blob/dfa414e8542a682187b3742b875cb605af2abe15/lib/sidekiq/middleware/server/request_id.rb#L10 and https://github.com/remind101/request_id/blob/dfa414e8542a682187b3742b875cb605af2abe15/spec/support/sidekiq.rb#L13
Errors look something like:
superclass must be a Class (Module given)

Has anyone had luck attempting an update? I will do some tests and report back.

Hey @srt32! Have you succeeded in adding the Sidekiq 5.0 support or shall I try to fix it?

@bluurn I am not working on this issue. Please feel free to work on it!

@srt32 Done :)


Replace upload and download SCP transfers with rsync.

@mateusz Thanks for the feedback. I've put back normalise_assets, and changed pushassets to push up to all servers for that task. To speed it up, the transfer to multiple servers is threaded.

Another way to optimise performance for this could be to use a less costly cipher for the SSH connection, e.g. ssh -c arcfour. What do you think @mateusz, @hafriedlander?


feat: Adds new release workflow

🤔 This might cause some issues. Basically, we need to parallel package paths, so they should be versioned differently.

Unsure. SanityV3 goes into general availability next week. Might be an idea to just cutoff V2.


Where can you read about the available actions?

I'm trying to create a library like this but for the Go language, but I can not find the documentation that tells me what parameters to pass to the API to perform actions such as writing a post or a comment.

You mean writing a wrapper of Go on top of this library? Why not considering a direct connection to the Steem blockchain?

I want to connect directly to the blockchain but I do not find enough documentation.

This issue is not related to this project. You could have found the necessary documentation on the internet:
https://steemit.github.io/steemit-docs/#


Bulk Import should accept a CancellationToken

Imports may take a long time. I want the ability to have it timeout after it takes to long.
I think the easiest way would be for the AwaitImport/Export Methods to accept a cancellation token to stop the polling.
And/or alternative would be a timeout parameter for the method to time out and return an TimeoutException.

@TheToor, you can currently use Task<BulkExportResponse> GetExportStatus(string token) and Task<BulkImportResponse> GetImportStatus(string token) to build your own methods as they return the current state of the import or export.

I went for the "And alternative", the AwaitImport/Export have been updated, supporting both.
Task<Stream> AwaitDownload(string token, int pollingIntervalInSeconds)
Task<Stream> AwaitDownload(string token, int pollingIntervalInSeconds, CancellationToken cancellationToken)
Task<Stream> AwaitDownload(string token, int pollingIntervalInSeconds, int timeoutInSeconds)

Task AwaitDownloadAndSave(string token, int pollingIntervalInSeconds, string path)
Task AwaitDownloadAndSave(string token, int pollingIntervalInSeconds, string path, CancellationToken cancellationToken)
Task AwaitDownloadAndSave(string token, int pollingIntervalInSeconds, string path, int timeoutInSeconds)

Task<BulkImportResponse> AwaitImport(string token, int pollingIntervalInSeconds)
Task<BulkImportResponse> AwaitImport(string token, int pollingIntervalInSeconds, CancellationToken cancellationToken)
Task<BulkImportResponse> AwaitImport(string token, int pollingIntervalInSeconds, int timeoutInSeconds)

Perfect :)
Maybe you can change the int to TimeSpan instead do more adhere to current standards?
Having a cancellation token for potentially long running operations is just good design I think.
No matter if we can build our own methods. But to be fair I didn't check that I can build my own loop :)

Agree with the TimeSpan, I will update the code later this week and replace int timeoutInSeconds with a TimeSpan timeout.

Closing this enhancement as this was implemented and released two week ago.


Alpine docker file and small docker fixes

Fixes #

Created Alpine Docker file and docker-compose files.
Alpine implementation creates three containers (ot-node, MySQL, graph dB).
Increase the graphdb service timeout to .setTimeout(30000) to allow mysql and graphdb initialization when deploying docker containers with alpine base image build.

Can we move all docker and docker-compose files into one docker directory, and then update in documentation command for starting to be docker-compose -f docker/docker-compose-ubuntu.yaml up or something similar? Also test if everything works fine if we have it like that.

@NZT48 I have moved only docker-compose file into /docker. The dockerfile can't be moved because the copy command also works when the file in the current build context.


[zh] Sync encrypt-data.md

Sync with en text:
content/zh-cn/docs/tasks/administer-cluster/encrypt-data.md

See preview please.

/approve


Update main.py

appreciate your work, repo main.py seems to have a bug.

Dear ZongPG
Thank you so much for pointing out!


added 'layout' field to Feature class so we can differentiate between…

… full width and split features. Additional features can probably defined by extending the class in the publisher.

:+1:


vm-service: Eval should support starting paused

The current set of building blocks available from the vm-service is inadequate to implement Smalltalk's "Debug-It" command, which opens a code snippet in a debugger paused at the first statement.
Doing this for the overall program is possible with --pause-isolates-on-start. Breakpoints are inadequate to implement this because the function with the snippet doesn't exist prior to the eval rpc.
It should likewise be possible to do this with a nullary closure.

Breakpoints are inadequate to implement this because the function with the snippet doesn't exist prior to the eval rpc.

Can't you just run evaled code through a trampoline, which just does a tail-call to the evaled code? Then you can place breakpoint into the trampoline, do a single-step and you will end up on the first statement of the evaled code?

The client would need to modify the users program to make such a trampoline available, and then the eval frame would display source that includes extra boilerplate to closurize the code snippet instead of the code snippet the user wrote.
The VM can just set the stepping flag before invoking the eval function.


[Security Scanner Action] Weekly update of security vulnerabilities reported by Quay

:rocket: This is an automated Pull Request.
This PR updates:

ci/security-scan/security_scan_results.md file with the latest security vulnerabilities reported by Quay.
ci/security-scan/weekly_commit_ids with the latest updated SHA digests of the notebooks (N & N-1)
Created by /.github/workflows/sec-scan.yaml

:exclamation: IMPORTANT NOTE: Remember to delete the  sec-scan-7125952222 branch after merging the changes

Thank you for this, Rama! I like it :slightly_smiling_face:
What I can see as an option for an improvement may be addition of the image grade based on the Red Hat agreement defined here - https://access.redhat.com/articles/2803031.


Is there a way to disable one-time binding for day labels?

I tried to dynamicaly change locale in datepicker following this approach:
 angular.module('ui.bootstrap.datepicker')
.config(function ($provide) {
    $provide.decorator('datepickerDirective', function ($delegate) {
        angular.forEach($delegate, function (directive) {
            var originalCompile = directive.compile;
            var originalLink = directive.link;
            console.log($delegate);
            if (originalCompile) {
                directive.compile = function () {
                    return function (scope, element, attrs, ctrls) {
                        var datepickerCtrl = ctrls[0];
                        scope.$on('$localeChangeSuccess', function () {
                            scope.move(0);
                            datepickerCtrl.refreshView();

                        });
                        originalLink.apply(this, arguments);
                    };
                }
            }
        });
        return $delegate;
    });
});

But I found that this is not working because of one-time binding for day labels. So is there a way to disable one-time binding without the need of modifying template? I use 0.13.2 version.

I would recommend modifying the template for now - this is a valid feature request for adding support for i18n updating of the view, so I am tagging this with the fresh i18n label.

Can someone please explain what modification needs to be done in the template to translate datepicker?

@sandeepthomas, please don't hijack the thread and change the topic.  Questions like yours are best served (and answered) when posted to StackOverflow.  Please see our instructions here.  Thanks.

@sandeepthomas , just delete one time bindings ('::') for day labels. Also you need to reload datepicker when locale changed if you use angular-translate lib.

@sandeepthomas , just delete one time bindings ('::') for day labels. Also you need to reload datepicker when locale changed if you use angular-translate lib.

Closing this in favor of #4626, I have figured out a solution to this issue that will be implemented as detailed there.

Just $scope.$watch for  value changes and broadcast a calendar redraw with help of this guide: https://gist.github.com/cgmartin/3daa01f910601ced9cd3


UI doesn't load on the best web browser of all time (Internet Explorer)

Can only see feedback button

i only have access to Windows 10 and Edge 20.1 currently and it work splendidly.
Can you do a run through on any version of IE you have again?  use http://client.augur.net
If you do have an issue, please note the platform and browser version.

IE 10 windows 8 was what the complaint said


support env POLARIS_COOKIE_DURATION for login cookie duration(day)

.. related docs might also need an update(if this gets merged)

Hello and thanks for the Pull Request!
I am not too keen on merging this because environment variables are not the mechanism used to configure Polaris, other than through docker-polaris. Other settings come through the command line, or the web UI (or config files).
In addition, I think this setting may be a workaround hiding a deeper issue. Could you clarify the reasoning which took you in this direction? I imagine it is because you find it annoying to re-login every day…and I completely agree.
I am planning two changes in this space for the approaching 0.13 release:

Make authentication cookies never expire
Add a sign out button (https://github.com/agersant/polaris/issues/55)

Would these changes also solve your use case?

Sure they will! It is indeed annoying to re-login everyday


Support json output for brew cask outdated

A detailed description of the proposed feature
I would like to get the output of brew cask outdated in json format. eg:
brew cask outdated --json

The motivation for the feature
It would be great to have brew cask outdated support the similar features of brew outdated.
How the feature would be relevant to at least 90% of Homebrew users
Since brew outdated --json provides a json output, to help tools that depend on json output to have common logic.

Mind if I volunteer taking on this issue?

Mind if I volunteer taking on this issue?

Sure, thank you for offering.

Also, I don't think there is currently pinned/pinned_version information for Cask::Cask.

By design, casks cannot be pinned. Many macOS apps auto-update, and we can’t really avoid that, so pinning wouldn’t work.

Thank you, @FTLam11!


configuring pipeline to avoid changing buildpacks

Changes

adds two tekton tasks: backup-source and restore-source to avoid configuring buildpack/builder to not remove the source files
using boson go builder

/kind bug

Fixes #827  #809

@zroubalik hey, regarding changing pipeline vs changing buildpacks - I have tried to capture the gist from the slack threads here: #827, wdyt about that?
And yeah, I agree, it would be better to anyway add these 2 tasks as steps in build task.

Thanks, I will check that issue, I missed it somehow, sorry.

@zroubalik thoughts on this? should I try the change of putting the new 2 tasks as steps instead - if this is how we would like to proceed considering the issue mentioned above.

@zroubalik added the build task yaml file in the pipeline resources of the kn-plugin-func repo - with 2 steps, backup and restore of source code.
because of this, the documentation will change slightly for the apply of buildpack task, but I can take care of that in another PR, let me know.

@zroubalik added the build task yaml file in the pipeline resources of the kn-plugin-func repo - with 2 additional steps, backup and restore of source code. because of this, the documentation will change slightly for the apply of buildpack task, but I can take care of that in another PR, let me know.

Sorry for the delay, though I'd prefer if we change the Go and Rust builders to not delete the function source code and config, so we have consistent experience with all runtimes. WDYT?

so we have consistent experience with all runtimes

thats actually my concern, in the slack thread of buildpacks I have linked in the original issue, i got to learn that there really is no standard in buildpacks today to handle source file deletion, so some do and some don't. So I see two choices, either to change buildpacks that do the source file deletion, maybe in future there will be more OR handle it like this.
I do see your point though, in case if we are going to maintain buildpacks, then it makes sense to do the changes at buildpacks level, but the pipeline change still looks more simpler to me - although, I havent really worked much with CICD systems so I wouldn't know how hard it would be to do the same for systems other than tekton etc.
and then there are security concerns like https://github.com/knative-sandbox/kn-plugin-func/issues/357 that @matejvasek briefly talked about in the slack thread.

BTW I just noticed that paketo java BP probably does delete sources.

@Shashankft9 I am going to go ahead and close this, since I think the problem has been addressed with a less resource intensive workaround in this PR https://github.com/knative-sandbox/kn-plugin-func/pull/1070. Thanks for your contribution in any case!


Open worlds via ftp

There should be a function so you can open and edit worlds via ftp/sftp.
This is pretty handy for people that have a (big) world on a server and just need to do a little change, if it's added you don't need to download the world and upload it again.

I have been running into some issues with this, so I have decided to passively work on this, but it will no longer be my top most priority. If anyone else wants to try to take a crack at it, all of my code related to this is on the FTP-Addition branch.

This has been added and will present in the next release.


fix: rerenders and memoization and all that jazz

Fixes #1808
Also decreases the amount of re-renders the app does.
To test:

Run demo with the following file - https://www.pfx.com.br/openapi.yaml
You might need to enable CORS - I used https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf?hl=en
Use upload form in TryIt.
Wait around a minute or so - changing the tabs also helped replicate the issue.
Expected result - file name is still present in try it (compare the behaviour with current main)

Were we ever able to reproduce this bug with a test?

@mpodlasin Noah's got a fair point about adding a test so it doesn't regress in the future

I didn't replicate the exact problem, but I have written some unit tests targeting the route causes of issue.
I also reverted to the old logic of checking if an object is a "plain object", to avoid potentially breaking stuff.

Huzzah!


Odroid XU4 (Android Nougat) freezing after several seconds

Required Info

Camera Model
D435

Firmware Version
<IP_ADDRESS>

Operating System & Version
Android 7.1.2

Kernel Version (Linux Only)
3.10.9 (Ubuntu)

Platform
Odroid XU4

SDK Version
2.0/latest

Language
Java/C++

Segment
Smartphone

Issue Description
I've been trying to get an RS camera to work on an Odroid XU4, first by downloading the app from the Google Play store, and also by compiling it myself. The camera feed typically works for a few seconds, but then it freezes. I've tried another XU4, the same issue happens, and the issue doesn't happen on other Android devices with the same camera.
Is there something I should look at in particular to solve this problem?

@daniel-dennis Which USB port did you use when get the issue? Could you please try if you get the issue when configure only depth or color? Please click the wrench button at the bottom left to configure that. And if you can collect adb logcat logs that will be more helpful for the investigation. Thanks!

@daniel-dennis Did you see the issue on USB2 or USB3 port? The default configuration of the APP should be depth1280x720@30fps which not supported by USB2. If use USB2, could you please switch to USB3 port to try again?

This is reproducible using librealsense 2.19.2 and 2.19.0 on Android 8 and 9 - there seems to be a memory issue - this happens on a high-end Samsung Galaxy Tab S4 10.5 with 6gb ram and USB3.
04-09 12:00:31.441 14977 14977 E librs camera streamer: streaming, error: UNKNOWN_ERROR 04-09 12:00:31.614 14977 15011 W librs : Timeout reached waiting for response! 04-09 12:00:31.615 14977 15011 E librs : Read pipe returned error and was clear halted ERROR:Success 04-09 12:00:31.616 712 892 I qti_sensors_hal: processReportInd: Accel - X: -0.171 Y: 0.328 Z: 9.813 04-09 12:00:31.617 14977 15010 W librs : Timeout reached waiting for response! 04-09 12:00:31.619 14977 15010 E librs : Read pipe returned error and was clear halted ERROR:Success 04-09 12:00:31.625 14977 15010 E librs : bad packet: error bit set 04-09 12:00:31.625 14977 15010 E librs : Cannot queue request: Out of memory

Any news on this? There is clearly a memory leak issue with librealsense on Android.

I have tried the com.example.realsense_java_example using librealsense with the .aar file provided from https://dl.bintray.com/intel-realsense/librealsense/com/intel/realsense/librealsense/.
I'm using a D435 camera with a similar Samsung Galaxy Tab S4 10.5 as mentioned by @fubsan above.
With SDK version 2.19.2, the example app works in that it displays the depth value somewhat reliably, but showing the camera stream to a surface view causes frequent glitches/freezes as described by the original poster.
Today I tested with SDK 2.21.0, and that fails immediately, spamming out of memory traces from librs (both with the unmodified com.example.realsense_java_example and a simple camera preview app based on the official examples):
2019-04-25 09:56:14.097 16553-16640/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory 2019-04-25 09:56:14.098 16553-16640/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory 2019-04-25 09:56:14.098 16553-16641/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory 2019-04-25 09:56:14.098 16553-16641/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory 2019-04-25 09:56:14.098 16553-16640/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory 2019-04-25 09:56:14.098 16553-16640/com.example.realsense_java_example W/librs: bulk_transfer on read endpoint returned error, ERROR: Out of memory
The java example app also crashes on app lifecycle changes:
2019-04-25 10:02:03.692 17314-17314/com.example.realsense_java_example E/AndroidRuntime: FATAL EXCEPTION: main     Process: com.example.realsense_java_example, PID: 17314     java.lang.RuntimeException: Unable to resume activity {com.example.realsense_java_example/com.example.realsense_java_example.MainActivity}: java.lang.IllegalThreadStateException         at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3805)         at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3845)         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1773)         at android.os.Handler.dispatchMessage(Handler.java:106)         at android.os.Looper.loop(Looper.java:164)         at android.app.ActivityThread.main(ActivityThread.java:7002)         at java.lang.reflect.Method.invoke(Native Method)         at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:441)         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1408)      Caused by: java.lang.IllegalThreadStateException         at java.lang.Thread.start(Thread.java:724)         at com.example.realsense_java_example.MainActivity.onResume(MainActivity.java:37)         at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1362)         at android.app.Activity.performResume(Activity.java:7432)

@daniel-dennis Any update from your side? Looking forward to your reply. Thanks!
@jonaslindgard @fubsan I couldn't reproduce the issue using librealsense v2.21 and FW <IP_ADDRESS> on Samsung Galaxy S8 with Android 8.0.  Could you please provide the full log for the issue? And what's the camera do you use when get the issue? Thanks!

I'm using the D435 camera with FW version <IP_ADDRESS>.
capture_example_logs.zip
I've attached 2 logcat logs; one using SDK 2.19.2 and the other using SDK 2.21.0.
With 2.19.2, the camera preview works
OK (with occasional glitches/freezes), but with 2.21.0 it fails immediately.
The app used is the capture example (only modification being that librs is used through downloaded .aar binary instead of locally built:
repositories {
maven {
url "https://dl.bintray.com/intel-realsense/librealsense"
}
}
dependencies {
implementation 'com.intel.realsense:librealsense:2.21.0@aar'
}

@daniel-dennis Any update from your side? Looking forward to your reply. Thanks!
@jonaslindgard @fubsan I couldn't reproduce the issue using librealsense v2.21 and FW <IP_ADDRESS> on Samsung Galaxy S8 with Android 8.0. Could you please provide the full log for the issue? And what's the camera do you use when get the issue? Thanks!

When I run the application, the following errors repeatedly appear in Logcat:

@daniel-dennis Any update from your side? Looking forward to your reply. Thanks!
@jonaslindgard @fubsan I couldn't reproduce the issue using librealsense v2.21 and FW <IP_ADDRESS> on Samsung Galaxy S8 with Android 8.0. Could you please provide the full log for the issue? And what's the camera do you use when get the issue? Thanks!

I was getting the same errors as @fubsan. I have managed to get a Realsense camera working properly on the XU4 however using the Realsense library as a backend (packaging into an aar file), and using my own frontend to display the feed (using a Unity project), so I suspect its an issue with the frame buffer not being cleared properly.

@jonaslindgard  @daniel-dennis I do see some problem with** ****thecaptureexample but not the same as yours. The problem I saw here is that the application can start and get streaming normally for the first time but no images any more after kill/stop the application.  While thecamera**example works well for me. So could you please try the **camera**example first? We will further check the issue of the capture example.

@jonaslindgard  @daniel-dennis Did you get any luck with the camera example? Looking forward to your update. Thanks!

@jonaslindgard @daniel-dennis Did you get any luck with the camera example? Looking forward to your update. Thanks!

Which example do you mean? java_example (com.example.realsense_java_example)?
Out of the given example apps (recording, playback, capture), capture seems to be the closest to my use case.

@jlindgard Sorry for any unclear in previous response. I mean the example tool in https://github.com/IntelRealSense/librealsense/tree/master/wrappers/android/tools/camera Could you please have a try?

Thank you for the clarification and for looking into this. I tested the example camera tool with com.intel.realsense:librealsense:2.22.0@aar (instead of building native code myself).
For a while it seems to work OK, but disconnecting the camera and reconnecting it seems to cause everything to slow down considerably and ultimately it stops working (app shows just black screen). Some other random behavior also occurs from time to time, e.g. one of the infrared streams stops working (app says 'invalid configuration' and jumps to settings view).

@jlindgard Thanks for the update! I'll try "disconnect and reconnect" here and update you later.

@jlindgard @daniel-dennis @jonaslindgard  According to PR#4237 merged to v2.24, the issue will get improved with the PR.  Could you please have a try with v2.24 and share the result? Thanks!

@jlindgard @daniel-dennis @jonaslindgard Did you get chance to try with v2.24?

@jlindgard @daniel-dennis @jonaslindgard  If no other questions, will close this ticket.


feat: typescript support for migration files

It would be great to be able to write and test migration files as typescript files.
i.e
migrations/1.0.0.ts
          /1.1.0.ts

My current tsconfig/jest setup complains bitterly when the Migrate class attempts to load up some js files. I can probably bash my way through to a solution but it would be great not to have to.
Secondly having the types in the up / down function definitions makes writing the actual migration logic easier. I know i can point the migrate cli / migrate class at the js files post typescript compilation but this still leads to the issue above when trying to test.

The TS script would need to be processed by Esbuild or TSC so they could be loaded.
I'm not sure I understand what you mean that tsconfig complains when loading "js" files. Can you specify allowJS?
Your second point, having types. Do you mean types for the Migrate class or for your code/
A bit more detail on your suggestions will help me understand.

The TS script would need to be processed by Esbuild or TSC so they could be loaded.

This is where i ended up. I have a step in my build process that does an esbuild/bundling of each each individual migration script in my migrations folder. The output of tsc wasn't enough in my case as my project is using a nx monorepo and was leveraging local shared modules that aren't published anywhere.
Maybe I didn't think this one through enough. The above felt a little heavyweight and I was hoping there might be a simple way to push some of this into the library to make writing migrations as typescript files easier.

I'm not sure I understand what you mean that tsconfig complains when loading "js" files. Can you specify allowJS?

My bad, I found the 'allowJS' setting after writing this. I now have a nice solution for unit testing migrations with a local dynamodb emulator and jest.

Your second point, having types. Do you mean types for the Migrate class or for your code

I mean types in the migration scripts. This has made discovering methods/intellisense on the db object in particular much easier.
  async up(db: Table, migrate: Migrate, params: { dry: boolean }) {}

vs
  async up(db, migrate, params) {}

Great that allowJs helped.
Yes, stripping types by node would be REALLY great.


ensure we don't resolve modules in parent folders

Not sure if this is relevant still but opening it here just in case.
https://github.com/nuxt/nuxt/issues/20616#issuecomment-1533727896

Thanks for making issue. Yes it is relevant i saw it multiple times but need to make a minimal reproduction (or test fixture) to make sure we don't introduce any side-effect regressions by making this change (however I'm pretty sure with all tests it will break some implicit cases that mlly was working for nested node_modules resolution, wrongly-and-correctly!)

Let's track in #158


Add iobio backend whitelist

quarantest build successful. Demo link at
http://12e8674b.quarantest.iobio.io

quarantest build successful. Demo link at
http://12e8674b.quarantest.iobio.io

quarantest build successful. Demo link at
http://ae18f50c.quarantest.iobio.io

quarantest build successful. Demo link at
http://ae18f50c.quarantest.iobio.io

The demo links are really nice

The demo links are really nice

Let me know when you deploy this and I'll test that public mosaic still works.

Let me know when you deploy this and I'll test that public mosaic still works.

@chmille4 it's actually already deployed. I tested on AWS and CHPC but totally forgot about your public instance. I just did a quick test and it looks like it's working. Let me know if I need to roll it back.

@chmille4 it's actually already deployed. I tested on AWS and CHPC but totally forgot about your public instance. I just did a quick test and it looks like it's working. Let me know if I need to roll it back.


Parser not parsing

I have an issue where the parser is returning as purely white

What it looks like currently:

Anyway to fix this?

Hey @Ssionn,
Can I just check, have you ran :TSInstall blade?
I've tried your config locally with success, so I'm sure we can get it working for you.
Thanks for checking the repo out by the way!

I've done that multiple times and it kept asking me to reinstall it, which i naturally did. Yet no result

@Ssionn
Ok what about trying :InspectTree, could you post a screenshot/ copy of the output from that?

@Ssionn
Ok what about trying :InspectTree, could you post a screenshot/ copy of the output from that?

Right now I'm at work, i'll be sure to test it when i'm home

I've tested it. This is the result:
(chunk ; [0, 0] - [34, 0]
  local_declaration: (variable_declaration ; [0, 0] - [0, 15]
    (assignment_statement ; [0, 6] - [0, 15]
      (variable_list ; [0, 6] - [0, 9]
        name: (identifier)) ; [0, 6] - [0, 9]
      (expression_list ; [0, 12] - [0, 15]
        value: (identifier)))) ; [0, 12] - [0, 15]
  (function_call ; [2, 0] - [12, 2]
    name: (dot_index_expression ; [2, 0] - [2, 40]
      table: (function_call ; [2, 0] - [2, 34]
        name: (identifier) ; [2, 0] - [2, 7]
        arguments: (arguments ; [2, 7] - [2, 34]
          (string ; [2, 8] - [2, 33]
            content: (string_content)))) ; [2, 9] - [2, 32]
      field: (identifier)) ; [2, 35] - [2, 40]
    arguments: (arguments ; [2, 40] - [12, 2]
      (table_constructor ; [2, 41] - [12, 1]
        (field ; [3, 3] - [3, 27]
          name: (identifier) ; [3, 3] - [3, 19]
          value: (string ; [3, 22] - [3, 27]
            content: (string_content))) ; [3, 23] - [3, 26]
        (field ; [4, 3] - [7, 4]
          name: (identifier) ; [4, 3] - [4, 12]
          value: (table_constructor ; [4, 15] - [7, 4]
            (field ; [5, 5] - [5, 18]
              name: (identifier) ; [5, 5] - [5, 11]
              value: (true)) ; [5, 14] - [5, 18]
            (field ; [6, 5] - [6, 45]
              name: (identifier) ; [6, 5] - [6, 38]
              value: (true)))) ; [6, 41] - [6, 45]
        (field ; [9, 3] - [11, 4]
          name: (identifier) ; [9, 3] - [9, 24]
          value: (table_constructor ; [9, 27] - [11, 4]
            (field ; [10, 5] - [10, 18]
              name: (identifier) ; [10, 5] - [10, 11]
              value: (true))))))) ; [10, 14] - [10, 18]
  local_declaration: (variable_declaration ; [14, 0] - [14, 76]
    (assignment_statement ; [14, 6] - [14, 76]
      (variable_list ; [14, 6] - [14, 19]
        name: (identifier)) ; [14, 6] - [14, 19]
      (expression_list ; [14, 22] - [14, 76]
        value: (function_call ; [14, 22] - [14, 76]
          name: (dot_index_expression ; [14, 22] - [14, 74]
            table: (function_call ; [14, 22] - [14, 55]
              name: (identifier) ; [14, 22] - [14, 29]
              arguments: (arguments ; [14, 30] - [14, 55]
                (string ; [14, 30] - [14, 55]
                  content: (string_content)))) ; [14, 31] - [14, 54]
            field: (identifier)) ; [14, 56] - [14, 74]
          arguments: (arguments))))) ; [14, 74] - [14, 76]
  (assignment_statement ; [16, 0] - [24, 1]
    (variable_list ; [16, 0] - [16, 19]
      name: (dot_index_expression ; [16, 0] - [16, 19]
        table: (identifier) ; [16, 0] - [16, 13]
        field: (identifier))) ; [16, 14] - [16, 19]
    (expression_list ; [16, 22] - [24, 1]
      value: (table_constructor ; [16, 22] - [24, 1]
        (field ; [17, 2] - [21, 3]
          name: (identifier) ; [17, 2] - [17, 14]
          value: (table_constructor ; [17, 17] - [21, 3]
            (field ; [18, 4] - [18, 59]
              name: (identifier) ; [18, 4] - [18, 7]
              value: (string ; [18, 10] - [18, 59]
                content: (string_content))) ; [18, 11] - [18, 58]
            (field ; [19, 4] - [19, 47]
              name: (identifier) ; [19, 4] - [19, 9]
              value: (table_constructor ; [19, 12] - [19, 47]
                (field ; [19, 14] - [19, 28]
                  value: (string ; [19, 14] - [19, 28]
                    content: (string_content))) ; [19, 15] - [19, 27]
                (field ; [19, 30] - [19, 45]
                  value: (string ; [19, 30] - [19, 45]
                    content: (string_content))))) ; [19, 31] - [19, 44]
            (field ; [20, 4] - [20, 19]
              name: (identifier) ; [20, 4] - [20, 10]
              value: (string ; [20, 13] - [20, 19]
                content: (string_content))))) ; [20, 14] - [20, 18]
        (field ; [23, 2] - [23, 20]
          name: (identifier) ; [23, 2] - [23, 10]
          value: (string ; [23, 13] - [23, 20]
            content: (string_content)))))) ; [23, 14] - [23, 19]
  (function_call ; [26, 0] - [31, 2]
    name: (dot_index_expression ; [26, 0] - [26, 27]
      table: (dot_index_expression ; [26, 0] - [26, 7]
        table: (identifier) ; [26, 0] - [26, 3]
        field: (identifier)) ; [26, 4] - [26, 7]
      field: (identifier)) ; [26, 8] - [26, 27]
    arguments: (arguments ; [26, 27] - [31, 2]
      (table_constructor ; [26, 28] - [26, 53]
        (field ; [26, 29] - [26, 41]
          value: (string ; [26, 29] - [26, 41]
            content: (string_content))) ; [26, 30] - [26, 40]
        (field ; [26, 43] - [26, 52]
          value: (string ; [26, 43] - [26, 52]
            content: (string_content)))) ; [26, 44] - [26, 51]
      (table_constructor ; [26, 55] - [31, 1]
        (field ; [27, 2] - [27, 25]
          name: (identifier) ; [27, 2] - [27, 9]
          value: (string ; [27, 12] - [27, 25]
            content: (string_content))) ; [27, 13] - [27, 24]
        (field ; [28, 2] - [30, 5]
          name: (identifier) ; [28, 2] - [28, 10]
          value: (function_definition ; [28, 13] - [30, 5]
            parameters: (parameters) ; [28, 21] - [28, 23]
            body: (block ; [29, 4] - [29, 29]
              (assignment_statement ; [29, 4] - [29, 29]
                (variable_list ; [29, 4] - [29, 19]
                  name: (dot_index_expression ; [29, 4] - [29, 19]
                    table: (dot_index_expression ; [29, 4] - [29, 10]
                      table: (identifier) ; [29, 4] - [29, 7]
                      field: (identifier)) ; [29, 8] - [29, 10]
                    field: (identifier))) ; [29, 11] - [29, 19]
                (expression_list ; [29, 22] - [29, 29]
                  value: (string ; [29, 22] - [29, 29]
                    content: (string_content)))))))))) ; [29, 23] - [29, 28]
  (assignment_statement ; [33, 0] - [33, 34]
    (variable_list ; [33, 0] - [33, 28]
      name: (bracket_index_expression ; [33, 0] - [33, 28]
        table: (dot_index_expression ; [33, 0] - [33, 14]
          table: (identifier) ; [33, 0] - [33, 7]
          field: (identifier)) ; [33, 8] - [33, 14]
        field: (string ; [33, 15] - [33, 27]
          content: (string_content)))) ; [33, 16] - [33, 26]
    (expression_list ; [33, 31] - [33, 34]
      value: (nil)))) ; [33, 31] - [33, 34]

@Ssionn I'm away from my laptop so can't look too much into it right this moment, but it seems the trees are being created fine. Have you copied the queries directory from the repo into its correct place? Seems the trees are being created but the highlights are not added.

Ah, i forgot to add that.. seems like that was my mistake will do so and come back with results

I'm still getting the white unhighlighted version

@Ssionn
Ah the files just need to be called highlights.scm and injections.scm, other than that the folder structure looks correct.

Yep, it's fixed. Thanks! I'll close this issue now

That's great :) if you have any feedback or other issues that come up then please get in touch.


Add share "copy embed code" to the share modal & fix "copy embed link…

This small PR improves a few issues pointed out in feedback:

removes disabled scrollbars from the share menu,
fixes broken Copy embed URL feature (it was pointing to the page link, not embed version),
adds Copy embed code option to the share modal,

However, I discovered another bug in the Overview section - embed URL doesn't contain information about shared Section so at the end, this link redirects to the homepage. It happens because clicking on any Share button dispatches an action setShareModal that displays all three instances of the ModalShare component, one on top of the other. I'll put that as a bug to the Pivotal Tracker

We have a problem with tablet portrait as the modal shrinks and the last button goes out of the window. We could use two rows or use the mobile version before. I will go for the mobile version if its easier

hey @Bluesmile82, thanks for your feedback! I decided to use two-rows layout for tablets and desktop:
Tablet:

Desktop:


This is my first time getting this error message and idk how to fix

Describe your problem here.
![
Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
I added the holy note from the vs mami mod and whenever I try to use it I get this message

Th Is going on? 2nd message in one day

its saying that the object (holy note) is non readable or something idk


Excluding vulnerability CVE-2023-35116 {patch}

Excluding vulnerability from scan as the situation described in https://github.com/FasterXML/jackson-databind/issues/3972 should not happen during intended use of Lowkey Vault.


Check how diseases are initialized

What's this one for?

After discussion, this is just going over what we discussed earlier in spring:
How is disease probability is used when setting an individual's disease status.
Action items: @jzhu20 to set up a meeting with myself and Daniel (Franco, if he wishes) to walk through the code.


FR #173 : add subtitle for ApsAlert

I Added subtitle  Based on APS doc
#173

@chemidy can you also add a quick entry to the CHANGELOG file before I merge this?

nit, for future reference: in idiomatic Go, this should be called "APSAlert". Acronyms are uppercase.

Thanks @broady. We considered that. It's not clear from the Apple documentation whether aps is an acronym. We are fairly certain it doesn't stand for anything. It's often just referred to as the "aps dictionary". I've only seen one place where it's spelled out as APS.


java.lang.UnsupportedOperationException in com.azure.identity.implementation.IdentityClient#authenticateWithAzurePowerShell

This line fails since Array does not support List#add method.
https://github.com/Azure/azure-sdk-for-java/blob/6eb6c81fd197da4d180c613adee6748cc4d117f0/sdk/identity/azure-identity/src/main/java/com/azure/identity/implementation/IdentityClient.java#L499

Thank you for reporting this issue @mitsutaka-takeda. @g2vinay could you take a look at this.


[MultiKueue] Support Deployment Integration

What would you like to be added:
The ability to create Kubernetes deployments on remote Clusters through MultiKueue
Why is this needed:
Support for various integrations already exist i.e. Jobset, KubeFlow Jobs, MPI, Batch.
Our use case is for long running model serving deployments that can be created remotely from a Manager Cluster.
Completion requirements:
Deployments can be created/managed locally on the Manager Cluster and through MultiKueue created/managed on the Worker Cluster(s) without the risk of running on the Manager.
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

cc @mwielgus @mwysokin

In the ideal solution, I think that we need to implement the managedBy field in all workload objects like Deployment and StatefulSet.
@mimowo Do you have any concerns about implementing the managedBy feature same as the batch/v1 Job?

We don't know yet the best path forward, from the initial discussion with @mwielgus we would like to support MultiKueue for Pods. Then, Deployement and StatefulSet integrations would work for free. The users using pod integration could also benefit. The problem is how to achieve "managedBy" for pods. The initial ideas we discussed:

gate the pod on the management cluster and block status updates
gate the pod on the management cluster and support status updates
schedule the pod on the management cluster, but on a virtual MultiKueue node

1, might will work ok, but might not be transparent to the end-users. 2 is relatively simple technically, but the issue is that we update the status, while the pod is gated, which might be violating the Pod API. 3. is harder, but would allow to update the Pod status without tricks.