Does the repo still valid and active for the unet project

I have faced some issue in testing the repo, I downloaded the pretrained weight from the main repo and change your convert_wt.py file as the below and get the weights
import torch
from torch import nn
import torchvision
import os
import struct
from torchsummary import summary
from unet import UNet

def main():
    print('cuda device count: ', torch.cuda.device_count())
    net = UNet(n_channels=3, n_classes=2, bilinear=False)
    device = torch.device('cuda' if torch.cuda.is_available() else 'cpu')

    net.to(device=device)
    net.load_state_dict(torch.load(
        'unet_carvana_scale1.0_epoch2.pth',
        map_location=device))

    net = net.eval()
    print('model: ', net)
    # print('state dict: ', net.state_dict().keys())
    # tmp = torch.ones(1, 3, 224, 224).to('cuda:0')
    # print('input: ', tmp)
    # out = net(tmp)

    # print('output:', out)

    summary(net, (3, 224, 224))
    # return
    f = open("unet.wts", 'w')
    f.write("{}\n".format(len(net.state_dict().keys())))
    for k, v in net.state_dict().items():
        print('key: ', k)
        print('value: ', v.shape)
        vr = v.reshape(-1).cpu().numpy()
        f.write("{} {}".format(k, len(vr)))
        for vv in vr:
            f.write(" ")
            f.write(struct.pack(">f", float(vv)).hex())
        f.write("\n")

if __name__ == '__main__':
    main()

After that I have changed some lines as the below in the c++ file:
#define BILINEAR false

std::map<std::string, Weights> weightMap = loadWeights("/path/to/unet.wts");

You can see the below report from the running the program:
Loading weights: /home/saeed/Documents/IRIS-PROJECT/projects/Pytorch-UNet/unet.wts
[05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] set name out
Building engine, please wait for a while...
[05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] [05/20/2022-22:52:54] Build engine successfully!
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 3: (Unnamed Layer* 28) [Convolution]:kernel weights has count 4718592 but 2359296 was expected
[E] [TRT] 4: (Unnamed Layer* 28) [Convolution]: count of 4718592 weights in kernel, but kernel dimensions (3,3) with 512 input channels, 512 output channels and 1 groups were specified. Expected Weights count is 512 * 3*3 * 512 / 1 = 2359296
[E] [TRT] 4: [convolutionNode.cpp::computeOutputExtents::39] Error Code 4: Internal Error ((Unnamed Layer* 28) [Convolution]: number of kernel weights does not match tensor dimensions)
[E] [TRT] 4: [network.cpp::validate::2835] Error Code 4: Internal Error (Could not compute dimensions for (Unnamed Layer* 0) [Convolution]_output, because the network is not valid.)
unet: /home/saeed/Documents/IRIS-PROJECT/projects/unet-tensorrt/unet.cpp:216: void APIToModel(unsigned int, nvinfer1::IHostMemory**): Assertion `engine != nullptr' failed.

Could you please help about the issue?

I have also changed the logging file to be able to use latest tensorrt api such as the below(because the base class has marked this function as a noexcept we should have mark the virtual function as noexcept)
    virtual void log(Severity severity, nvinfer1::AsciiChar const* msg) noexcept
    {
        LogStreamConsumer(mReportableSeverity, severity) << "[TRT] " << std::string(msg) << std::endl;
    }

This repo is valid for the old version of pytorch-unet v1(2020) https://github.com/milesial/Pytorch-UNet/tree/v1.0, and you can download pretrained weights from https://github.com/milesial/Pytorch-UNet/releases/download/v1.0/unet_carvana_scale1_epoch5.pth, I tried the old version pretrained weight and it succeed.

I have checked out the pytorch-unet to v1 tag.
$ git checkout v1.0

Also, I have created new environment and run
pip install -r requirements.txt

But there was an issue in gen_wts.py as the below:
cuda device count:  1
Traceback (most recent call last):
  File "/home/saeed/Documents/IRIS-PROJECT/projects/Pytorch-UNet/gen_wts.py", line 38, in <module>
    main()
  File "/home/saeed/Documents/IRIS-PROJECT/projects/Pytorch-UNet/gen_wts.py", line 12, in main
    net = net.to('cuda:0')
AttributeError: 'collections.OrderedDict' object has no attribute 'to'

I was able to solve this as I have mentioned the code in my first comment but in running the tensorrt now I can see that the previous error not shown but the generating engine is crashed in the below line:
https://github.com/YuzhouPeng/unet-tensorrt/blob/a7a6d81ddf1ed553a87d1bdbd83075c6b892dacb/unet.cpp#L216
It seems that the engine is nullptr and is not created correctly.

I can confirm that works and the problem was in the below line:
https://github.com/YuzhouPeng/unet-tensorrt/blob/a7a6d81ddf1ed553a87d1bdbd83075c6b892dacb/unet.cpp#L15
I have changed it to false but after a simple git stash I can see that everything works. Thanks for the help @YuzhouPeng

I can confirm that the specified weight works and the problem was in the below line:
https://github.com/YuzhouPeng/unet-tensorrt/blob/a7a6d81ddf1ed553a87d1bdbd83075c6b892dacb/unet.cpp#L15
I have changed it to false but after a simple git stash I can see that everything works. Thanks for the help @YuzhouPeng

Yes, the md5 is 8d160e0ec171340bd1b80f3096cbd5c9.

@aiLover2 Did you make it with the which pretrained model? v3.0 or v1.0? I checkout to v1.0 code in Pytorch-UNet, and used your gen_wts.py code for the v1.0 pretrained model. But I got:
 torch.Size([2, 64, 1, 1]).
	size mismatch for outc.conv.bias: copying a param with shape torch.Size([1]) from checkpoint, the shape in current model is torch.Size([2]).


Add more details to early career

This one line doesn't feel like enough to cover 15 years!  What did you do? What did you find out about what kind of work you like / dislike?
https://github.com/ndorfin/cv/blob/b116bf61170f344f602d9df86d70a1ca45e9d33b/CV-ShaunO'Connell.html#L352

I wanted to show an entry point. The next entry contains the 14 years of info :)


Manual control/offboard not working

I have tried(a lot) to remotely control my drone using MavSDK. Either there is a bug or I have missed something.
What I want to do is

to control the drone with inputs akin to a controller. (increase thrust, pitch, yaw. etc). Or even better just to say. Go up/down/forward,strafe left, Yaw x degrees.
To be able to increase thrust while on the ground (just as you can do with the RC).
To be able to yaw/increase thrust/pitch/etc without gps signal

I do not want to use GPS-based/location aware metrics like go forward x meters.
I have tried many different things including

the manualcontrol example found here https://github.com/mavlink/MAVSDK-Python/blob/main/examples/manual_control.py
the offboard example found here, https://github.com/mavlink/MAVSDK-Python/blob/main/examples/offboard_velocity_body.py
The cpp version of manual control

If I do not have my rc activated the manualcontrol-example executes without any errors but nothing happens with the propellers when the set_manual_control_input calls are made. The drone are armed (in the script) and then disarmed while the other code is executing, again without any errors (I have not understood why it is disarmed - I do not get any errors anywhere I can find.)
With the offboard examples it is a similar thing. It executes without any errors but nothing happens on the drone.
Takeoff, land and navigationbased scripts works fine.
The virtual joysticks in QGC works so I do not see why the python version would not work.
I have read some mentions of different parameters to set but I have none of these (I'm running Mateksys F406-HDTE and Ardupilot 4.4.4). For example:
COM_RC_IN_MODE
Maybe there are some Px4 exclusive parameters?
My setup
FC, Mateksys F406-HDTE <-- serial ---> RPi Zero 2W, 64 Bookwork, Python3.9, MavSdk-Python 2.1.0 <--wifi--> pc with QGC

The pythonscript is executed on the RPi.
I do not get any errors if I run the mavsdk server by it self (aside from a lot of loading unknown module, but those have the debug label)
The telemetry data from the drone is perfectly healthy. I have good (20+ satellites) gps fix. The drone is calibrated and works fine when flying with the RC.
I would like to manage to get a script that oscillates between 5% and 10% thrust (will not lift the drone but I can see/hear that the script works)
So, is this a bug or am I missing something obvious? What steps are required to be able to run the manual_control.

Thanks for the issue. I think this hasn't been tested on ArduPilot. I'm not entirely sure what is missing.
Do you see the output of mavsdk_server, maybe that will give us a clue?

No errors there as far as I can see but I get a lot of these debug-messages, maybe they can help us in the right direction? But I do not get any messages marked as errors.
....
[09:49:21|Debug] New system ID: 150 Comp ID: 64 (mavsdk_impl.cpp:737)
[09:49:21|Debug] Component Unsupported component (64) added. (system_impl.cpp:389)
[09:49:22|Debug] New system ID: 127 Comp ID: 166 (mavsdk_impl.cpp:737)
[09:49:22|Debug] Component Unsupported component (166) added. (system_impl.cpp:389)
[09:49:22|Debug] Component Unsupported component (82) added. (system_impl.cpp:389)
[09:49:22|Debug] New system ID: 159 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:49:22|Debug] New system ID: 179 Comp ID: 243 (mavsdk_impl.cpp:737)
[09:49:22|Debug] Component Unsupported component (243) added. (system_impl.cpp:389)
[09:49:22|Debug] New system ID: 172 Comp ID: 129 (mavsdk_impl.cpp:737)
[09:49:22|Debug] Component Unsupported component (129) added. (system_impl.cpp:389)
[09:49:22|Debug] New system ID: 234 Comp ID: 253 (mavsdk_impl.cpp:737)
[09:49:22|Debug] Component Unsupported component (253) added. (system_impl.cpp:389)
[09:49:23|Debug] Discovered 5 component(s) (system_impl.cpp:564)
[09:49:23|Debug] New system ID: 186 Comp ID: 9 (mavsdk_impl.cpp:737)
[09:49:23|Debug] Component Unsupported component (9) added. (system_impl.cpp:389)
[09:49:23|Debug] New system ID: 45 Comp ID: 13 (mavsdk_impl.cpp:737)
[09:49:23|Debug] Component Unsupported component (13) added. (system_impl.cpp:389)
[09:49:23|Debug] New system ID: 77 Comp ID: 6 (mavsdk_impl.cpp:737)
[09:49:23|Debug] Component Unsupported component (6) added. (system_impl.cpp:389)
[09:49:24|Debug] New system ID: 225 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:49:24|Debug] New system ID: 82 Comp ID: 83 (mavsdk_impl.cpp:737)
[09:49:24|Debug] Component Unsupported component (83) added. (system_impl.cpp:389)
[09:49:24|Debug] Component Unsupported component (30) added. (system_impl.cpp:389)
[09:49:24|Debug] Component Unsupported component (232) added. (system_impl.cpp:389)
[09:49:25|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:49:25|Debug] Component Unsupported component (244) added. (system_impl.cpp:389)
[09:49:25|Debug] Component Unsupported component (87) added. (system_impl.cpp:389)
[09:49:25|Debug] New system ID: 16 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:49:25|Debug] Component Unsupported component (112) added. (system_impl.cpp:389)
[09:49:25|Debug] Component Unsupported component (73) added. (system_impl.cpp:389)
....

How many systems are connected? That's odd. One drone should generally be "one system" and have the same system ID.

I only have one drone connected. I also use mavproxy to communicate with qgc (but mavproxy is either shut down by me before I try to run the script or, if left running, just loses the connection while the script is running and then regains the connection afterwards)

I have tried another thing.
If i just run the example and let it start the mavsdk server it executes the script but nothing happens (it arms and then disarms again)
If I start the mavsdk server first and then run the script, it gets stuck on the check for good telemetry health (even though I have good gps fix)
I get these errors
[09:05:40|Debug] New system ID: 253 Comp ID: 113 (mavsdk_impl.cpp:737)
[09:05:40|Debug] Component Unsupported component (113) added. (system_impl.cpp:389)
[09:05:40|Warn ] sending again after 0.508073 s, retries to do: 3  (512). (mavlink_command_sender.cpp:312)
[09:05:40|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:318)
[09:05:40|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:40|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:40|Warn ] sending again after 1.01195 s, retries to do: 2  (512). (mavlink_command_sender.cpp:312)
[09:05:40|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:318)
[09:05:41|Debug] New system ID: 112 Comp ID: 112 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (112) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 108 Comp ID: 84 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (84) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 130 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:41|Warn ] sending again after 1.5156 s, retries to do: 1  (512). (mavlink_command_sender.cpp:312)
[09:05:41|Warn ] Request was for msg ID: 242 (mavlink_command_sender.cpp:318)
[09:05:41|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:41|Debug] New system ID: 77 Comp ID: 205 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (205) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 216 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 73 Comp ID: 13 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (13) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 84 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:41|Debug] New system ID: 61 Comp ID: 220 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (220) added. (system_impl.cpp:389)
[09:05:41|Debug] New system ID: 118 Comp ID: 138 (mavsdk_impl.cpp:737)
[09:05:41|Debug] Component Unsupported component (138) added. (system_impl.cpp:389)
[09:05:41|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:41|Error] Retrying failed (512) (mavlink_command_sender.cpp:339)
[09:05:42|Debug] New system ID: 52 Comp ID: 24 (mavsdk_impl.cpp:737)
[09:05:42|Debug] Component Unsupported component (24) added. (system_impl.cpp:389)
[09:05:42|Debug] New system ID: 132 Comp ID: 57 (mavsdk_impl.cpp:737)
[09:05:42|Debug] Component Unsupported component (57) added. (system_impl.cpp:389)
[09:05:42|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:42|Debug] New system ID: 162 Comp ID: 222 (mavsdk_impl.cpp:737)
[09:05:42|Debug] Component Unsupported component (222) added. (system_impl.cpp:389)
[09:05:42|Debug] New system ID: 4 Comp ID: 255 (mavsdk_impl.cpp:737)
[09:05:42|Debug] Component Unsupported component (255) added. (system_impl.cpp:389)
[09:05:42|Debug] Component Unsupported component (54) added. (system_impl.cpp:389)
[09:05:42|Debug] New system ID: 79 Comp ID: 140 (mavsdk_impl.cpp:737)
[09:05:42|Debug] Component Unsupported component (140) added. (system_impl.cpp:389)
[09:05:42|Info ] heartbeats timed out (system_impl.cpp:279)
[09:05:42|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:42|Error] Error: Param for gyro offset_x failed. (telemetry_impl.cpp:1906)
[09:05:43|Debug] New system ID: 222 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:43|Debug] New system ID: 137 Comp ID: 138 (mavsdk_impl.cpp:737)
[09:05:43|Debug] Component Unsupported component (138) added. (system_impl.cpp:389)
[09:05:43|Debug] New system ID: 21 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:43|Debug] New system ID: 123 Comp ID: 110 (mavsdk_impl.cpp:737)
[09:05:43|Debug] Component Unsupported component (110) added. (system_impl.cpp:389)
[09:05:43|Debug] New system ID: 12 Comp ID: 126 (mavsdk_impl.cpp:737)
[09:05:43|Debug] Component Unsupported component (126) added. (system_impl.cpp:389)
[09:05:43|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:43|Debug] Component Unsupported component (254) added. (system_impl.cpp:389)
[09:05:43|Debug] New system ID: 53 Comp ID: 31 (mavsdk_impl.cpp:737)
[09:05:43|Debug] Component Unsupported component (31) added. (system_impl.cpp:389)
[09:05:43|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:44|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:44|Debug] New system ID: 169 Comp ID: 59 (mavsdk_impl.cpp:737)
[09:05:44|Debug] Component Unsupported component (59) added. (system_impl.cpp:389)
[09:05:44|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:44|Debug] New system ID: 9 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:44|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:44|Debug] New system ID: 3 Comp ID: 3 (mavsdk_impl.cpp:737)
[09:05:44|Debug] Component Unsupported component (3) added. (system_impl.cpp:389)
[09:05:45|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:45|Debug] New system ID: 182 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 228 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 55 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:45|Debug] New system ID: 82 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:45|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:45|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 90 Comp ID: 81 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (81) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 110 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 57 Comp ID: 179 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (179) added. (system_impl.cpp:389)
[09:05:45|Debug] New system ID: 107 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:45|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:46|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:46|Error] Error: Param for gyro offset_y failed. (telemetry_impl.cpp:1921)
[09:05:46|Debug] New system ID: 168 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:46|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:46|Debug] New system ID: 234 Comp ID: 59 (mavsdk_impl.cpp:737)
[09:05:46|Debug] Component Unsupported component (59) added. (system_impl.cpp:389)
[09:05:46|Debug] New system ID: 245 Comp ID: 129 (mavsdk_impl.cpp:737)
[09:05:46|Debug] Component Unsupported component (129) added. (system_impl.cpp:389)
[09:05:46|Debug] Component Unsupported component (83) added. (system_impl.cpp:389)
[09:05:46|Debug] New system ID: 181 Comp ID: 114 (mavsdk_impl.cpp:737)
[09:05:46|Debug] Component Unsupported component (114) added. (system_impl.cpp:389)
[09:05:46|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:47|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:47|Debug] New system ID: 47 Comp ID: 82 (mavsdk_impl.cpp:737)
[09:05:47|Debug] Component Unsupported component (82) added. (system_impl.cpp:389)
[09:05:47|Debug] New system ID: 120 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:47|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:47|Debug] New system ID: 92 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:48|Debug] New system ID: 93 Comp ID: 19 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (19) added. (system_impl.cpp:389)
[09:05:48|Debug] New system ID: 60 Comp ID: 64 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (64) added. (system_impl.cpp:389)
[09:05:48|Debug] New system ID: 109 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:48|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:48|Debug] New system ID: 172 Comp ID: 64 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (64) added. (system_impl.cpp:389)
[09:05:48|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:48|Debug] New system ID: 31 Comp ID: 89 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (89) added. (system_impl.cpp:389)
[09:05:48|Debug] New system ID: 100 Comp ID: 84 (mavsdk_impl.cpp:737)
[09:05:48|Debug] Component Unsupported component (84) added. (system_impl.cpp:389)
[09:05:49|Debug] New system ID: 126 Comp ID: 124 (mavsdk_impl.cpp:737)
[09:05:49|Debug] Component Unsupported component (124) added. (system_impl.cpp:389)
[09:05:49|Debug] Component Unsupported component (51) added. (system_impl.cpp:389)
[09:05:49|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:49|Error] Error: Param for gyro offset_z failed. (telemetry_impl.cpp:1936)
[09:05:49|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:49|Debug] New system ID: 149 Comp ID: 84 (mavsdk_impl.cpp:737)
[09:05:49|Debug] Component Unsupported component (84) added. (system_impl.cpp:389)
[09:05:49|Debug] Discovered 1 component(s) (system_impl.cpp:564)
[09:05:49|Debug] Component Unsupported component (179) added. (system_impl.cpp:389)
[09:05:49|Debug] New system ID: 205 Comp ID: 5 (mavsdk_impl.cpp:737)
[09:05:49|Debug] Component Unsupported component (5) added. (system_impl.cpp:389)
[09:05:49|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:50|Debug] New system ID: 33 Comp ID: 13 (mavsdk_impl.cpp:737)
[09:05:50|Debug] Component Unsupported component (13) added. (system_impl.cpp:389)
[09:05:50|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:50|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:51|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:51|Debug] Component Unsupported component (47) added. (system_impl.cpp:389)
[09:05:51|Debug] Component Unsupported component (84) added. (system_impl.cpp:389)
[09:05:51|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:51|Debug] New system ID: 28 Comp ID: 165 (mavsdk_impl.cpp:737)
[09:05:51|Debug] Component Unsupported component (165) added. (system_impl.cpp:389)
[09:05:51|Debug] Discovered 1 component(s) (system_impl.cpp:564)
[09:05:52|Debug] Component Unsupported component (208) added. (system_impl.cpp:389)
[09:05:52|Debug] New system ID: 49 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:52|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:52|Error] Error: Param for accel offset_x failed. (telemetry_impl.cpp:1861)
[09:05:52|Debug] New system ID: 173 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:52|Debug] New system ID: 23 Comp ID: 57 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (57) added. (system_impl.cpp:389)
[09:05:52|Debug] New system ID: 153 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:52|Info ] heartbeats timed out (system_impl.cpp:279)
[09:05:52|Debug] New system ID: 184 Comp ID: 57 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (57) added. (system_impl.cpp:389)
[09:05:52|Debug] New system ID: 34 Comp ID: 124 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (124) added. (system_impl.cpp:389)
[09:05:52|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:52|Debug] New system ID: 232 Comp ID: 3 (mavsdk_impl.cpp:737)
[09:05:52|Debug] Component Unsupported component (3) added. (system_impl.cpp:389)
[09:05:52|Debug] Component Unsupported component (51) added. (system_impl.cpp:389)
[09:05:53|Debug] New system ID: 204 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:53|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:53|Debug] Component Unsupported component (21) added. (system_impl.cpp:389)
[09:05:53|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:53|Debug] Component Unsupported component (204) added. (system_impl.cpp:389)
[09:05:53|Debug] New system ID: 166 Comp ID: 193 (mavsdk_impl.cpp:737)
[09:05:53|Debug] Component Unsupported component (193) added. (system_impl.cpp:389)
[09:05:53|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:54|Debug] New system ID: 76 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:54|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:54|Debug] New system ID: 183 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:54|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:54|Info ] heartbeats timed out (system_impl.cpp:279)
[09:05:55|Debug] New system ID: 185 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:55|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:55|Error] Error: Param for accel offset_y failed. (telemetry_impl.cpp:1876)
[09:05:55|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:56|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:56|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:05:57|Debug] New system ID: 26 Comp ID: 132 (mavsdk_impl.cpp:737)
[09:05:57|Debug] Component Unsupported component (132) added. (system_impl.cpp:389)
[09:05:57|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:05:57|Debug] New system ID: 114 Comp ID: 143 (mavsdk_impl.cpp:737)
[09:05:57|Debug] Component Unsupported component (143) added. (system_impl.cpp:389)
[09:05:57|Debug] New system ID: 101 Comp ID: 85 (mavsdk_impl.cpp:737)
[09:05:57|Debug] Component Unsupported component (85) added. (system_impl.cpp:389)
[09:05:57|Debug] New system ID: 195 Comp ID: 20 (mavsdk_impl.cpp:737)
[09:05:57|Debug] Component Unsupported component (20) added. (system_impl.cpp:389)
[09:05:57|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:05:58|Debug] New system ID: 196 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:05:58|Debug] New system ID: 51 Comp ID: 60 (mavsdk_impl.cpp:737)
[09:05:58|Debug] Component Unsupported component (60) added. (system_impl.cpp:389)
[09:05:58|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:05:58|Error] Error: Param for accel offset_z failed. (telemetry_impl.cpp:1891)
[09:05:58|Debug] New system ID: 198 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:58|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:05:59|Warn ] sending again, retries to do: 5 (mavlink_parameter_client.cpp:1058)
[09:05:59|Debug] Component Unsupported component (160) added. (system_impl.cpp:389)
[09:05:59|Debug] New system ID: 35 Comp ID: 249 (mavsdk_impl.cpp:737)
[09:05:59|Debug] Component Unsupported component (249) added. (system_impl.cpp:389)
[09:05:59|Warn ] sending again, retries to do: 4 (mavlink_parameter_client.cpp:1058)
[09:05:59|Debug] New system ID: 5 Comp ID: 5 (mavsdk_impl.cpp:737)
[09:05:59|Debug] Component Unsupported component (5) added. (system_impl.cpp:389)
[09:05:59|Debug] Component Unsupported component (8) added. (system_impl.cpp:389)
[09:05:59|Debug] New system ID: 154 Comp ID: 61 (mavsdk_impl.cpp:737)
[09:05:59|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:06:00|Warn ] sending again, retries to do: 3 (mavlink_parameter_client.cpp:1058)
[09:06:00|Debug] Component Unsupported component (34) added. (system_impl.cpp:389)
[09:06:00|Warn ] sending again, retries to do: 2 (mavlink_parameter_client.cpp:1058)
[09:06:00|Debug] New system ID: 8 Comp ID: 38 (mavsdk_impl.cpp:737)
[09:06:00|Debug] Component Unsupported component (38) added. (system_impl.cpp:389)
[09:06:00|Debug] New system ID: 160 Comp ID: 0 (mavsdk_impl.cpp:737)
[09:06:01|Debug] Component Unsupported component (61) added. (system_impl.cpp:389)
[09:06:01|Warn ] sending again, retries to do: 1 (mavlink_parameter_client.cpp:1058)
[09:06:01|Debug] New system ID: 70 Comp ID: 235 (mavsdk_impl.cpp:737)
[09:06:01|Debug] Component Unsupported component (235) added. (system_impl.cpp:389)
[09:06:01|Debug] New system ID: 56 Comp ID: 134 (mavsdk_impl.cpp:737)
[09:06:01|Debug] Component Unsupported component (134) added. (system_impl.cpp:389)
[09:06:01|Error] retrying failed (mavlink_parameter_client.cpp:1074)
[09:06:01|Error] Error: Param for mag offset_x failed. (telemetry_impl.cpp:1816)
[09:06:01|Debug] Component Unsupported component (253) added. (system_impl.cpp:389)

I cannot see why the behavior would differ, I only have one mavsdk server installed and one version of mavproxy

I have successfully removed all of the weird debug messages by explicitly setting both sysid and compid to 1. Both when I start the mavsdk-server and in the python code. However, the commands still do not work

Ok good. So now the question is whether or how manual control works with ArduPilot.

will giving commands in mavproxy shell directly will help?
Try giving 'arm throttle' and 'takeoff' commands.

Commands(like arm, takeoff, status gps_raw_int) directly in mavproxy work. Though I do not know how the Mavlink command to do manual/joystick input looks like (I've tried to find an example but haven't found any good one). If you know how the command looks like to increase the thrust to 30% for example  I can test it (without props :D ).
Also the joystick in QGC works (and QGC commmunicates over udp to the zero/mavproxy).

About "So now the question is whether or how manual control works with ArduPilot". Do you know about any firmware for a 30x30mm stack that works better with mavsdk than Ardupilot?

Try giving 'arm throttle' and 'takeoff' commands.

Pi4B Ubuntu 22.04 64-bit
Arducopter v4.2.3
takeoff FAILED Action failed
Name: mavsdk
Version: 2.1.0
Summary: Python wrapper for MAVSDK
Home-page: https://github.com/mavlink/MAVSDK-Python
Author:
Author-email:
License: UNKNOWN
Location: /home/pi/.local/lib/python3.10/site-packages
Requires: aiogrpc, grpcio, protobuf
Required-by:
$
Main in
System server b4
System server done
Pi4B Waiting for drone to connect...
-- Connected to drone!
Version: [flight_sw_major: 4, flight_sw_minor: 2, flight_sw_patch: 3, flight_sw_vendor_major: 56, flight_sw_vendor_minor: 52, flight_sw_vendor_patch: 97, os_sw_major: 0, os_sw_minor: 0, os_sw_patch: 0, flight_sw_git_hash: 376130633 , os_sw_git_hash:<PHONE_NUMBER>30383 , flight_sw_version_type: RELEASE]
Flight mode: UNKNOWN
-- Arming
Arming error:  None
Battery: 9600.0
Battery_v: 16.33100128173828
Is_armed:  True
arm_event.is_set() =  True
set_takeoff_altitude:  None
Battery: 9600.0
Battery_v: 16.33500099182129
Is_armed:  True
Battery: 9600.0
Battery_v: 16.32900047302246
Is_armed:  True
-- Taking off
print_battery CancelledError
print_status_text CancelledError
print_altitude CancelledError
print_is_armed CancelledError
print_flight_mode CancelledError
Traceback (most recent call last):
File "/home/pi/backup/mavsdk/mavsdk_test_20240315.py", line 214, in
asyncio.run(run())
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete
File "/home/pi/backup/mavsdk/mavsdk_test_20240315.py", line 84, in run
actionerr = await drone.action.takeoff()
File "/home/pi/.local/lib/python3.10/site-packages/mavsdk/action.py", line 376, in takeoff
raise ActionError(result, "takeoff()")
mavsdk.action.ActionError: FAILED: 'Failed'; origin: takeoff(); params: ()

In my opinion, takeoff and land only works with GPS mode, if you're working in GPS denied environment, then you should try working on Offboard mode.

takeoff and land only works with GPS mode

Yes, I went out to test. the takeoff returns no error, the only problem is
if health.is_global_position_ok and health.is_home_position_ok: keeps failing even though MissionPlanner reports GPS healthy, Ardupilot acquired home position. I have to comment off the check for now.
Main in
System server b4
System server done
Pi4B Waiting for drone to connect...
-- Connected to drone!
Version: [flight_sw_major: 4, flight_sw_minor: 2, flight_sw_patch: 3, flight_sw_vendor_major: 56, flight_sw_vendor_minor: 52, flight_sw_vendor_patch: 97, os_sw_major: 0, os_sw_minor: 0, os_sw_patch: 0, flight_sw_git_hash: 376130633 , os_sw_git_hash:<PHONE_NUMBER>30383 , flight_sw_version_type: RELEASE]
Flight mode: LAND
Waiting for drone to have a global position estimate...
Battery: 9200.0
Battery_v: 15.653000831604004
-- Global position state NOT good for flying.
 Check in QGC for any errors before running.

In my opinion, takeoff and land only works with GPS mode, if you're working in GPS denied environment, then you should try working on Offboard mode.

I would like to run without GPS but during the current tests I do have GPS. Also, I have tried the offboard scripts as well.

@arpitpara  @julianoes Any ideas/proposals on how I can check if it is Ardupilot that is the problem? I could flash the FC to INav instead, do you think that is a test worth doing?

I would dig into whatever source code (e.g. ArduPilot) and check what's happening.


treewide: batched rust cargoSha256 upgrades

This batches together a handful of relatively straightforward upgrades. Since
there's a lot of compilation and fixed-output merge conflict risk, I think this
is too big to build and test in one huge treewide PR, but also want to be
conscientious about not spamming the PR inbox for NixPkgs by sending them all
1-by-1. Let me know what you'd prefer.

Motivation for this change
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Eh, not a big fan of this approach; aside from it going into conflict (which it now has), and causing a lot of rebuilds all at once for something that's fine being an incremental gradual upgrade, there's a bystander effect on testing/approving/merging when it's a big pile of packages.  I think I'll stick to individual PRs that are more digestible, unless you prefer otherwise @jonringer.

individual is fine by me. It does make the build times a lot shorter
plus, rustc take an ungodly amount of RAM to build stuff. I go from ~2Gb used, to 30Gb+ used when kicking off many rust projects


XCode Error

Hi,
sometimes XCode shows me this error:
/Base.lproj/Main.storyboard: error: IB Designables: Failed to render instance of CompactPhoneIdLoginButton: Rendering the view took longer than 200 ms. Your drawing code may suffer from slow performance.
Alessandro

Thanks for reporting. I will investigate this issue.


How can i upload to Testflight by adding entitlements and resign mac app

Discussed in https://github.com/fastlane/fastlane/discussions/21246

Originally posted by deventheguy May  3, 2023
I am trying to upload Mac App for Safari extension but the build is failing to upload to testflight with the below error, after some research i understand that you have sign the app after its packaged with entitlements again, but the only resign option in fastlane is ios, is there a way i can achieve this?
ERROR [2023-05-03 11:32:56.68]: fastlane finished with errors
11:32:57  /Users/tools/jenkins/workspace/my_pipeline/vendor/bundle/ruby/2.5.0/gems/fastlane-2.205.2/fastlane_core/lib/fastlane_core/ui/interface.rb:141:in `user_error!': [!] Error uploading pkg file:  (FastlaneCore::Interface::FastlaneError)
11:32:57   [Transporter Error Output]: Asset validation failed - App sandbox not enabled. The following executables must include the com.apple.security.app-sandbox entitlement with a Boolean value of true in the entitlements property list: [( com.myapp.new.pkg/Payload/myapp.app/Contents/MacOS/myapp )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. - STATE_ERROR.VALIDATION_ERROR.90296
11:32:57  [Transporter Error Output]: c068285d-a560-4f26-9b4e-23ab69ff69.pkg2095459618157827-swinfo.plist (1) - Could not commit reservation: c3b88d21-20eb-45b9-8fa3-91a82d646f6b
11:32:57  [Transporter Error Output]: ERROR ITMS-90296: App sandbox not enabled. The following executables must include the com.apple.security.app-sandbox entitlement with a Boolean value of true in the entitlements property list: [( com.myapp.new.pkg/Payload/myapp.app/Contents/MacOS/myapp )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app.
11:32:57  [Transporter Error Output]: Return status of iTunes Transporter was 1: Asset validation failed - App sandbox not enabled. The following executables must include the com.apple.security.app-sandbox entitlement with a Boolean value of true in the entitlements property list: [( com.myapp.new.pkg/Payload/myapp.app/Contents/MacOS/myapp )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app. - STATE_ERROR.VALIDATION_ERROR.90296
\nc068285d-a560-4f26-9b4e-2344ab69ff69.pkg2095459613458157827-swinfo.plist (1) - Could not commit reservation: c3b88d21-20eb-45b9-8fa3-91456d638f6b
\nERROR ITMS-90296: App sandbox not enabled. The following executables must include the com.apple.security.app-sandbox entitlement with a Boolean value of true in the entitlements property list: [( com.myapp.new.pkg/Payload/myapp.app/Contents/MacOS/myapp )] Refer to App Sandbox page at https://developer.apple.com/documentation/security/app_sandbox for more information on sandboxing your app.
``` </div>

are you refereeing to the output before the lane starts?
------+---------------------------+-------------+
20:33:11  |                fastlane summary                |
20:33:11  +------+---------------------------+-------------+
20:33:11  | Step | Action                    | Time (in s) |
20:33:11  +------+---------------------------+-------------+
20:33:11  | 1    | default_platform          | 0           |
20:33:11  | 2    | app_store_connect_api_key | 0           |
20:33:11  | 3    | keyman_unlock             | 1           |
20:33:11  | 4    | increment_build_number    | 4           |
20:33:11  | 5    | build_mac_app             | 46          |
20:33:11  | 6    | keyman_restore            | 0           |
20:33:11  +------+---------------------------+-------------+

it fail during upload_to_testflight
+------+---------------------------+-------------+
20:34:21  |                fastlane summary                |
20:34:21  +------+---------------------------+-------------+
20:34:21  | Step | Action                    | Time (in s) |
20:34:21  +------+---------------------------+-------------+
20:34:21  | 1    | default_platform          | 0           |
20:34:21  | 2    | app_store_connect_api_key | 0           |
20:34:21  | 3    | keyman_unlock             | 1           |
20:34:21  | 💥   | upload_to_testflight      | 62          |
20:34:21  | 5    | keyman_restore            | 0           |
20:34:21  +------+---------------------------+-------------+

ENV file
FL_PROJECT_TEAM_ID=XYZNQAS
FASTLANE_TEAM_ID=XYZNQAS
FL_ENDPOINT=http://upload.com
FL_REPO=maven-publicfacing
FL_REPO_PATH=/my/app/extension/
FL_PROJECT_PATH="macos.xcodeproj"

# Signing
SIGH_TEAM_ID=XYZNQAS
SIGH_PROFILE=com.macos.main
SIGH_EXTENSION_PROFILE=com.macos.main.extension
SIGH_CERTIFICATE_ID=GH45FSDF

# Test Flight upload settings
; PILOT_WAIT_PROCESSING_INTERVAL=180
; PILOT_APP_IDENTIFIER=com.macos.ext
; PILOT_DISTRIBUTE_EXTERNAL=true
; PILOT_CHANGELOG='Test'
; PILOT_GROUPS=External

# Zip
FL_ZIP_PATH="myapp.app"
FL_ZIP_OUTPUT_PATH="myapp.app.zip"


Logging at DEBUG level will freeze the terminal

If we tails the log and try to do something like transfer files between plugin and skygear. Current config is to log the whole transferred payload, which cause the freeze of a terminal

Skygear Server Date/Version: v0.12.1
Application Platform: OSX

Expected Results

While debug message is useful during development, the log of large meaningless payload is annoying. Expecting the logs will truncate itself when it larger than a specific amount.

Same apply for the websocket logs. It just spam the logs currently.


lxml.etree.XMLSyntaxError: Premature end of data in tag

Error when updating spectra count through lxml, possibly caused by improper closing of XML file/tags.

Fixed by commit c53713c


Fields should not be suffixed with 'List', 'Dictionary' or 'Collection'

Fields should not be suffixed with 'List' or 'Dictionary' as that is already indicated by their type.

Same applies for Collection.

Same applies for Array or HashSet.


[1.1.1][test][15-test_genec] Improve EC tests with genpkey

Test separately EC parameters and EC key generation.
For some curves we have had cases in which generating the parameters
under certain conditions failed, while generating and serializing a key
under the same conditions did not.
See https://github.com/openssl/openssl/issues/12306 for more details.

This is related to #12307 (does the same thing for master) but is opened against 1.1.1 because the backport is not trivial due to the need for TODO: {} annotations until #12102 is fixed.
Checklist

[x] tests are added or updated
[x] #12312 is approved
[x] #12305 is approved

Rebased on top of #12312 , #12305 .
#12312 and #12305 fail the tests (intentionally) if the changes from this PR are not merged on top.

@mattcaswell can you spare some time to look at this as well?

This was approved at

Fri, 3 Jul 2020 13:51:00 +0000

It will be ready to merge at
Fri, 4 Jul 2020 13:51:01 +0000

24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set.  Please review the updates and set the label manually.

Merged to 1.1.1 as:

e1c246bd7682fd1b0fcbba5a224f3cacc1ba278d [test][15-test_genec] Improve EC tests with genpkey

Thanks!


networkErrorCode limitations

From the documentation of the HCHttpCallResponseGetNetworkErrorCode
// <param name="networkErrorCode">The network error code of the HTTP call. Possible values are S_OK, or E_FAIL.</param>
It is being claimed that possible return values are OK or ERROR but in reality, other states may come out such as E_HC_NO_NETWORK. Is that an error in the documentation?
Why does networkErrorCode is so limited in possible return values? It is losing its purpose if you cannot fetch a meaningful cross-platform error out of it and will have to derive the error from platformNetworkErrorCode.
Looking for more information and usages about this feature.

Ping for update, it has been a month

What would you like to see beyond E_HC_NO_NETWORK?   In our usage of LHC we don't do anything differently based on the type of network failure as we just treat all network failures the same.  For debugging, we log platformNetworkErrorCode to track down real cause but don't take different logical actions based on it.


Feature: Modifying streaming data

I see that #88 added the ability to stream large files instead of downloading them upfront and then parsing them, but - and correct me if I'm wrong - it seems like there is no way to modify such files with mitmproxy.

Does something exist outside mitmproxy that allows one to modify these files?
Would you guys be interested in a feature that allows you to modify data as it streams?

I think this use case is particularly interesting when the user it downloading a large executable file, a song, a movie, or even a compressed file with any of those.
For an example of what I'm talking about, I have a proof of concept in c that injects code into a file in a streaming way: https://github.com/vikstrous/binder_full_of_elves/blob/master/stream_bind.c (linux x86-64 LE only for now)
I'm particularly excited about injecting into streaming video :)
I understand that mitmproxy was not designed for this, but I think it would be a great feature and I'm interested in contributing to make this happen.

+1 for this feature. :) But it seems not yet to exist in 0.11.3, correct? Are you planning this in e.g. 0.12.x or later?
# cat test-issues319.py
def dump_content(chunks):
    for prefix, content, suffix in chunks:
        print content
        yield prefix, content, suffix

def responseheaders(ctx, flow):
    flow.response.stream = dump_content

# mitmproxy --version
mitmproxy 0.11.3

# mitmdump -v --stream 32 -s test-issues319.py

Thank you.

This feature is not planned for any release yet - we're happy to accept contributions from the community though. After all, this shouldn't be too difficult to implement - I laid out the basic steps in my previous post.
Cheers,
Max

This will ship with the next release - thanks to @sakurai-youhei for providing the initial PR!


Panel control border

Running guna theme with sublimelinter plugins panel doesn't look great for the panel because it blends into code and what not, really needs a border (in my opinion).
Sure it's possible to play with theme file, but some fix would be nice, at least an option in user settings file.

I updated for panel control border. The border can be seen on any color scheme.
You can check v1.7.8 version for it.

Sweet fix, thanks!


feat: workload labels

Implement go/gmp:expand-target-labels.

did you intend to change AlertingConfig?

Nope. That was my mistake. Should be fixed now.

FYI - we're still awaiting final word on if these labels are sufficient cc @xichen2020

@pintohutch Is this blocking?

I don't think it's blocking this PR per se. We may want to wait final labels before a release though


Add support for NULL elements in arrays

PostgreSQL arrays can have NULL elements, but this is not supported by the
current type conversion machinery of LibPQ.jl. This commit adds support for NULL
array elements, by changing the Julia element type for PostgreSQL arrays from
T to Union{T, Missing}. Though this is a breaking change, I think it is more
in line with the behavior of PostgreSQL arrays. It also fixes problems I
encounter when using queries that return arrays with NULL elements.
Since this is a big change, I am not 'fleshing out' this change with tests until
I get some feedback on whether this would be a welcome change.

I don't understand why these changes would affect the parsed type when the result should be an OffsetArray.

I don't think https://github.com/invenia/LibPQ.jl/pull/85/commits/0a37cca143288064328feac901baf2d54c70c4a1 is necessary

In https://github.com/invenia/LibPQ.jl/pull/85/commits/64bdc98f66f7b6d3dad9eb07e2b49dc18c9ad935 you need to make the arrays missing-inclusive after you reshape, or reshape will make a ReshapedArray.
Also you should go ahead and add a test or two for the behaviour with NULL. Thanks for this!

I have an idea:
If you set it up so you keep https://github.com/invenia/LibPQ.jl/commit/0a37cca143288064328feac901baf2d54c70c4a1#diff-0f5f2c643546fb8d14be2b38c08d84f9R328 but change the other method to:
function parse_numeric_array(eltype::Type{T}, str::AbstractString) where T
    eq_ind = findfirst(isequal('='), str)

    if eq_ind !== nothing
        offset_str = str[1:eq_ind-1]
        range_strs = split(str[1:eq_ind-1], ['[',']']; keepempty=false)
        ranges = map(range_strs) do range_str
            lower, upper = split(range_str, ':'; limit=2)
            return parse(Int, lower):parse(Int, upper)
        end
        arr = OffsetArray{T}(undef, ranges...)
        el_iter = eachmatch(r"[^\}\{,]+", str[eq_ind+1:end])
    else
        arr = Array{T}(undef, array_size(str)...)
        el_iter = eachmatch(r"[^\}\{,]+", str)
end

then you can have NULL support by default but add this for supporting arrays without nulls:
    @eval function Base.parse(::Type{AbstractArray{$jl_eltype}}, pqv::PQValue{$array_oid})
        parse_numeric_array($jl_eltype, string_view(pqv))
    end

Yeah, my intent with 0a37cca was to leave the door open for arrays without NULL elements. I don't quite understand your suggestion for parse_numeric_array (I think it may have been clipped), is it to just make array with the specified element type, and then try to assign missing to it regardless of whether the element type includes Missing? If so, that seems ok to me: if the element type is erroneously specified to not include Missing and there really are NULLs, then assigning the elements seems like as good of a place as any to throw an error.

Yep, that's exactly it

Tests finally passed. I squashed the commits and fixed up the commit message.

Looks like the DataFrames.jl no longer supports DataStreams (JuliaData/DataFrames.jl#1783)?

Also see JuliaData/DataFrames.jl/#1773

Yep, sorry I looked into it but apparently never hit send on my comment. I have a PR incoming that will just cap DataFrames until I have time to remove DataStreams here too. Once that's in we can retrigger CI (I expect tests to pass).

Sorry for the problem.
Is removing DataStreams.jl support a huge problem. If I understand the design trend that @quinnj implements correctly its support should not be continued in DataFrames.jl as it should not be needed.
But if it is essential to keep it we can move it to deprecated section for the time being and release a patch v0.18.1.
CC @quinnj , @nalimilan

A deprecation would be much appreciated! That would allow us to more easily identify cases where we need to replace DataStreams with Tables for use with DataFrames (in our internal packages, of which there are many). But it's not the end of the world, and we could cap DataFrames at 0.17.x for a time.

@quinnj - what do you think is best to do (maybe there is an easy way to move to Tables.jl so there is no need to add the deprecation). But if it is not simple I would revert it to deprecated (as we have many other major changes in 0.18 so it would be better if they are tested against in real world 😄).

I think if we need to make a change for all of our packages that do this we might as well switch them to using Tables.jl. We're really only ever using a simple Data.stream! call so it won't be too hard. Things can be upper-bounded for a short time (like a week or two).

OK - so I understand that for the time being we can wait with reverting the change in DataFrames.jl, but if you find that things are more nasty please let me know and I will make a patch release reverting them as deprecated.

Sure, thanks!


Neighbor tiles loaded not patterned

Issue Type
[ ] Question
[x ] Bug
[ ] Improvement
[ ] Build system related
[ ] Performance
[ ] Documentation
##Using a different Tile Source
We have dedicated a private server to our map view, and we have set the below codes for arranging the tiles, however at the loading and loaded points, it shows tiles irrelevant to the ones surroundings:
    mapView?.setTileSource(object : OnlineTileSourceBase(
            "USGS Topo", 0, 18, 256, ".png",
            arrayOf("http://<IP_ADDRESS>/tile/")
        ) {
            override fun getTileURLString(pMapTileIndex: Long): String {
                Log.d("Address : ", "TST")

                var address =
                    baseUrl + MapTileIndex.getZoom(pMapTileIndex) + "/" + MapTileIndex.getY(
                        pMapTileIndex
                    ) + "/" + MapTileIndex.getX(pMapTileIndex) + mImageFilenameEnding

                Log.d("Address : ", address)

                return (address)
            }
        })

Please find attached the screenshot of the issue.

Environment
If it's a bug, version(s) of android this affects:
All
Version of osmdroid the issue relates to:
6.0.2

looks a lot like your url is uses a different pattern. Default is Z/X/Y, however yours may be Z/Y/X or some other variant. I'd suggest clearing the map tile cache and zooming all the way out and observe what parts of the world are in the wrong place. It may help you figure it out

thanks, it work for me,
but on this page its wrong and use Z/Y/X , please make it correct


[WIP] Add online swagger api

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

/close

/reopen

/close


Fix slack user task 4 utility function's key error

In the Slack user task 4, when the LLM agent executes get_webpage(COMPANY_URL) without executing post_webpage(COMPANY_URL), the COMPANY_URL is appended to post_environment.web.web_requests. However, post_environment.web.web_content does not get a key COMPANY_URL, leading to a KeyError during subsequent checks that access post_environment.web.web_content[COMPANY_URL].
To prevent this error, I added a check to verify if COMPANY_URL exists in post_environment.web.web_content.keys(). This ensures that the key is present before any access attempt, thus avoiding potential runtime errors.

I put these changes in #28 to introduce a new benchmark minor version and have everything in one PR. Please double check that they are correct!

Thanks a lot for spotting the bugs and opening the PRs btw!


Only show materially changed files in the diffs

What was wrong?
Right now every file appears in the Hardforks Index, even if the changes are minimal like just changing the hardfork name.
Related to Issue #508
How was it fixed?
First check if there are meaningful differences between documents and publish a diff only if there are any.
The PR in its current form depends on another PR that I have created on the rstdiff repo. That PR will have to be merged first and a new release of rstdiff will have to be created.
Build docs for this PR will FAIL until that point.
Cute Animal Picture

Codecov Report

Merging #515 (15a0ee4) into master (1b2291b) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #515   +/-   ##
=======================================
  Coverage   86.56%   86.56%
=======================================
  Files         258      258
  Lines       14571    14571
=======================================
  Hits        12613    12613
  Misses       1958     1958

Flag
Coverage Δ

unittests
86.56% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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


Unity include Standard Assets

Would it somehow be possible to add the download of "Stadard Assets"?
Or make flags when installing (like brew cask install unity --include-standard-assets (maybe a bad name)).

I don't think so, but maybe you could create a new Cask called unity-standardassets or something like that?

Cool, PR is made: https://github.com/caskroom/homebrew-cask/pull/26721


Workaround kubectl exec and kubectl logs issues with k3s

Closes #59. I'd like to cut 3.0.1 with this.
I hesitated applying this workaround before as I hoped it would be fixed quickly in k3s, but it has been around for a long while now and progress to resolve it seems very slow.
The patch will only influence k3s version 1.21+ for users that doesn't already specify --egress-selector-mode and should be non-breaking.
Related

Test failure in kubespawner because of this: https://github.com/jupyterhub/kubespawner/runs/7737736963?check_suite_focus=true.
Test failures worked around in z2jh because of this: https://github.com/jupyterhub/zero-to-jupyterhub-k8s/pull/2800

I made this labelled "bug" instead of "maintenance". It wasn't a bug with this action, but its a bug managed in k3s which this action is all about so i figure its more helpful to have it sorted like this.


EXD-116: Create and modify tag description field validation

Please re-open this PR on this repo: https://github.com/Excali-Studio/excali-front-wrapper @KamilSilk


[Bug] A potentially dangerous Request.Path value was detected from the client (:)

Describe the bug
I'm trying to download Maven package from artifacts with name "android-builds.dev:corp"
To Reproduce
Azure Cli Version:
azure-cli (2.0.57)
Azure-Devops extension version:
azure-devops (0.12.0)
Steps to reproduce the behavior:

login using az devops login
Run command.: az artifacts universal download --organization "https://dev.azure.com/xxx" --feed "android-loading-app" --name "android-builds.dev:corp" --version "1.10.10" --path .
See error:

An error occurred on the service. A potentially dangerous Request.Path value was detected from the client (:).

Expected behavior
Package should be downloaded

The command you're using is only for downloading "Universal Packages" packages, and not for Maven packages.
To download Maven packages, use the mvn (or gradle) tools.

Closing this as it looks like Phil gave a solid response and we haven't heard back :)


meta node is unresponsive when no master available

./cmd -c meta.json
If no master in "masterAddrs" can be reached, cmd becomes unreponsive (no ctrl-c) and can only be killed with kill -9
In addition metaNode_error.log and metaNode_debug.log rapidly fill up until no more disk space is left.
maybe cmd can just quit if no master is available or try to reach a master for a certain time before it quits

started as a datanode, has the same problem.

it is a good idea.   We will change in the next version.

It is ok that the master has to start first.
I the design is that the master needs to start first, then the metanode should not start when the master is not started.


Pushing multiple values for the same metric sequentially

Perhaps I'm misunderstanding some fundamental concept here, but it seems to me there is a bug in the way metrics are handled by provided adapters. I would expect that setting the value of the gauge metric to two different values in sequence would result in both those values being present in the MetricFamilySamples object. Instead, the second value overwrites the first one. Also, no timestamp seems to be included with any of the metrics, so I'm guessing Prometheus will assign the timestamp when scraping. This all means that, in order to have accurate metrics, you need to configure Prometheus to scrape your data once every second, which does not seem very efficient.
Here's a test case I wrote to demonstrate what I'm saying: https://github.com/pavlepredic/prometheus_client_php_test/blob/master/src/GaugeTest.php. In the test, I use InMemory adapter (because it's easier to set up), but I'm getting the same behaviour with Redis adapter.
Am I missing something or is there a design flaw in the library?

i run also in this problem... there is currently no workaround for me...

try to add an label with current datetime. you will get new entry for any new combination of label-values...

But that label will not act as the metric timestamp, right? Prometheus will still assign the same timestamp to all those metrics based on the time of scraping. Or am I wrong?

yes, prometheus use the scraping timestamp. but i have also an PR (https://github.com/endclothing/prometheus_client_php/pull/54) to handle this, so you can set your own TS.
on the other hand, you have to strip this datetime-label so that prometheus/grafana can better handle this samples and recognize that this is one stream:
scrape_configs:
  - job_name: 'XXXXXXXX'
# ...
    metric_relabel_configs:
      - regex: 'datetime'
        action: labeldrop


Last modified time should be skipped when etag check fails.

It is possible that a change to file/directory causes a etag change and no last modified time change. For example:

Create folder A.
Create folder B.
Visit folder B.
Rename folder B to C, and then A to B.
Visit folder B (previous folder A).

At step 5, the client sents HTTP_IF_MODIFIED_SINCE header with the last modified time of folder B in step 2. Since the last modified time of folder A is less than B, the server will send 304 back, which is an error since the folder is actually changed.
To fix this, we should skip checking for 304 if the client already sends an etag which does not return 304. Here's a patch to fix this:
diff --git a/bottle.py b/bottle.py
index 0b22f2e..9ac9ee5 100755
--- a/bottle.py
+++ b/bottle.py
@@ -2914,11 +2914,12 @@ def static_file(filename, root,
         if check and check == etag:
             return HTTPResponse(status=304, **headers)

-    ims = getenv('HTTP_IF_MODIFIED_SINCE')
-    if ims:
-        ims = parse_date(ims.split(";")[0].strip())
-    if ims is not None and ims >= int(stats.st_mtime):
-        return HTTPResponse(status=304, **headers)
+    if not (etag and check):
+        ims = getenv('HTTP_IF_MODIFIED_SINCE')
+        if ims:
+            ims = parse_date(ims.split(";")[0].strip())
+        if ims is not None and ims >= int(stats.st_mtime):
+            return HTTPResponse(status=304, **headers)

     body = '' if request.method == 'HEAD' else open(filename, 'rb')

I think this is right. Other frameworks do the same things, like Tornado
https://github.com/tornadoweb/tornado/blob/8e5ecad25ea86d52245a9587fd454613f03c7fb8/tornado/web.py#L2707-L2709
And I think I can reslove it.


rename "intent" to "input" in resources?

May be more understandable.
E.g.
https://github.com/namespacelabs/examples/blob/main/multitier/03-withresources/apibackend/server.cue#L28-L31
@nicolasalt @n-g @nichtverstehen @szferi for thoughts.

Resource providers have two ways of depending on other resources. In-line (called resources) and provided externally (called inputs).
We should revisit the names of these fields in the same refactor.


'Hero Widget' Exception is thrown when using ticket

When using a ticket, the Hero widget causes an exception to be thrown:
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
The following assertion was thrown during a scheduler callback:
There are multiple heroes that share the same tag within a subtree.
Within each subtree for which heroes are to be animated (i.e. a PageRoute subtree), each Hero must
have a unique non-null tag.
In this case, multiple heroes had the following tag: 1
├# Here is the subtree for one of the offending heroes: Hero

Works on my machine. Are you using Flutter 3.10.0?
Try showing the output of running flutter doctor.


Add pull_request_review_comment trigger to run GitHub Actions Tests

To trigger the GitHub Actions called Tests just create a new comment on the review with the text:
github-actions-workflow: tests

github-actions: tests

github-actions: tests

github-actions-workflow-tests

github-actions-workflow-tests

github-actions-workflow: tests

github-actions-workflow: tests

github-actions-workflow: tests

github-actions-workflow: tests

github-actions-workflow: tests


Export shadows to Icon

Use case
Recently I saw a "Flutter Tip" in my LinkedIn timeline:

I found it quite unnecessarily complex, as a Icon is nothing more than a Text, so I proposed in the comments the following:
  return Text(
    String.fromCharCode(icon.codePoint),
    style: TextStyle(
      fontSize: 24.0,
      fontFamily: icon.fontFamily,
      package: icon.fontPackage,
      shadows: [
        Shadow(
          color: Colors.black54,
          offset: const Offset(1.0, 1.0),
          blurRadius: 1.0,
        )
      ],
    ),
  );

Turns out that the Icon class is almost this (but, of course, with some additional features), and it would quite easy to simply export the shadows parameter to the Icon class.
Proposal
I am going to open a PR regarding this.
The proposal is to simply add a shadows parameter to Icon class that will be forwarded to the inner TextSpan.

@mateusfccp
Can you check if this open request is similar to yours ?

@darshankawar
Yes, this is indeed what I am proposing. I am going to close this in favor of #79274 and quote it in my PR.


roundcubePlugins.carddav: 4.4.4 -> 4.4.6

Description of changes

Update roundcube plugin to v4.4.6 according to latest release available at this time: https://github.com/mstilkerich/rcmcarddav/releases/tag/v4.4.6
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Successfully tested it on an nginx virtualhost using:
root = pkgs.roundcube.withPlugins (plugins: with plugins; [ carddav ]);

Backporting because this also contains a PHP8 compat fix :)

there's one in 4.4.5 already: https://github.com/mstilkerich/rcmcarddav/releases/tag/v4.4.5


Why I think people continue to ask if it's safe to update

So even with the warnings, we still get people asking if it's safe to update and/or deliberately skipping the step and then asking why they can't inject FBI...
Even though the guide says "Yes, just do it," I feel it isn't enough to convince some people, because they were earlier told that if they update, they'll lose their hacks, and ask anyway for an immediate answer, than a written guide, for verification.
Can you clarify in the steps directly that their version string should say "Sys" and that an official system would otherwise say "Ver"? I think that would alleviate any doubt of updating the system, and they'll stop asking. For good measure, also add that if they don't see "Sys" or "Ver" then they need to either restore their NAND or redo Section III

I think it would be easier to say that when a user installs A9LH, he is protected from updates, since Luma3DS blocks any updates that modify the firm where the hacks are installed. Telling the users this kind of info might make people more wary of what is going on and worry less.

Added an explanation

Thanks for the amendment! Though I was actually hoping you could mention the version string thing, because I think some people don't even realize they're booting into Luma despite having configured it. Would you mind adding that little bit too?


API expansion and gitignore additions

The expanded functions look great. Thanks!
I'm hesitant to include the changes to .gitignore. There's a lot of stuff in those changes that have no need in this repository (grunt for example, plus a lot more). I think it's best to have a project .gitignore cover what's needed for the project and nothing more. If you use Jetbrains and want certain Jetbrains files excluded from a git repository, use .gitignore_global. I don't use Jetbrains and don't want to see Jetbrains specific rules in some random open source project's .gitignore. That all being said, I'm happy to be persuaded that the change is useful if you have a strong argument for it.

Agreed, I've reverted the changes.


Can't reference DLL from GAC

We currently assume all #r directives are file paths.

@bjorkstromm is this still relevant since we bumped to .NET 3.1/5/6?

@bjorkstromm is this still relevant since we bumped to .NET 3.1/5/6?

Dunno, need to verify if this is still relevant. There's no GAC anymore, and additional System.* libs should be pulled via NuGet.


Added steps to the CONTRIBUTING.md describing when to use Kani and how to write tests that will help Miri catch UB.
FIXES: #501
Apologies for the inconveniences caused.
Thank you

@joshlf please review.

Hey @IndranjanaChatterjee, thanks for this! Unfortunately this isn't one of the issues we're looking for outside contribution for, but if you're interested in contributing, check out any issue that's labeled with https://github.com/google/zerocopy/labels/help wanted.

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.

@joshlf thankyou so much for your reviews, but I have already done the CLA , don't know why it is showing like that. Apologies for the inconveniences caused.


Colouring of the bullet threading plugin

Hi there,
there is a problem with the colour of the specified path of the bullet threading plugin. The highlighted specified line goes through the highest bullet point. It seems like the bullet point is a tad too low and differs from the other bullets. I use the quattro font.

I don't get the same output you do (thread going beyond the bullet), but the threaded bullet for headings is too high. Do you have other custom css or plugins interacting?
Bullet threading is clever, but makes certain assumptions that aren't valid for all themes. I don't have time to look for a fix right now. If you find a fix that roughly maintains heading spacing, I'd be happy to incorporate it.

I had to reinstall my OS and everything new and somehow the thread going beyond the bullet disappeared. The custom css was not the reason, but maybe some plugin? Right now the plugins I reinstalled do not cause the problem again.  I'll write here again if I get this again and maybe know the cause of this.


Colors do not change anymore in Spotify

Describe the bug
Color does not change dynamically anymore
To Reproduce
Steps to reproduce the behavior:

Open Spotify
Play any song
Skip to the next song

Screenshots

Versions
OS: Osx v12.3.0
Spotify: v<IP_ADDRESS>4
Spicetify: v2.9.2
Dribbblish: v4.1.3-8c5a45c
Extensions

dribbblish-dynamic.js
fullAppDisplay.js

Settings
{
    "EXPORTED_WITH": "4.1.3",
    "showLoadingScreen": true,
    "openSettingsInfo": true,
    "showSearchBox": true,
    "rightBigCover": true,
    "roundSidebarIcons": false,
    "sidebarHoverAnimation": true,
    "sidebarGapLeft": 5,
    "sidebarGapRight": 32,
    "winTopBar": "none-padding",
    "playbarShadow": false,
    "playbarTransition": true,
    "playerControlsStyle": "dribbblish",
    "showAlbumInfoInPlaybar": false,
    "showGenreInfoInPlaybar": false,
    "hideAdsOrPremium": "none",
    "fadeDuration": 0.5,
    "customCss": "",
    "colorSelectionAlgorithm": "colorthief",
    "colorOverride": "#02deed",
    "colorSelectionMode": "default",
    "lightModeLuminance": 0.6,
    "darkModeLuminance": 0.2,
    "theme": "dark",
    "darkModeOnTime": "20:00",
    "darkModeOffTime": "06:00",
    "bgTheme": "bw"
}

Can confirm, same versions, also doesn't work for me

I'm having the same issue on Windows 10.

same

same for me but there is a very random delay most of the time. sometimes it changes halfway into the next song or just gets stuck on one color

Reopening this issue because this now occurs in
OS: macOS v12.3.1
Spotify: v<IP_ADDRESS>6
Spicetify: v2.9.6
Dribbblish: v4.1.4-239033a


Merge the latest WaterfallMC commit

It solves the 1.11 > versions compatibility because of the Title packet.

Fixed by a4745d8e6dc8a5bb5538692fb9c03fd715102f48 😉

:D

Would you mind updating to the latest waterfall commit again?


0.3.7-rc0 does not work with wlan0, only eth0

Hi!
Following up on https://github.com/nerves-project/nerves_examples/pull/85#issue-186513505 here as it pertains to this repo.
0.3.7-rc0 seems to work correctly with eth0 but not with wlan0. The fix to have it work was to use 0.3. I tested with (rpi3) and 0.3.6 works correctly, so it stopped working in the current .7-rc0.
cc: @deanchouinard, @ConnorRigby

Good to know. I hit a couple regressions with this version that i'm going to be taking a look at this week.


Define the VISION

This is an overview of what the shape of hyper looks like, but also somewhat zoomed out, so that the vision can survive while the exact minute details might shift and change over time. It starts with what is hyper, defines a framework for how we make decisions, includes use cases we've considered, and then shows how the library can ideally fulfill its purpose.
There's two documents here. The VISION is the main document, and includes a list of prioritized tenets inside it. The TENETS document is supplemental, and goes more in-depth on what the principles mean, and examples of how they've been used before.
This is the first step in the hyper 1.0 timeline.
This blog post includes background and motivation for defining a VISION for hyper.
Feedback very much welcome!

I don't seem to be able to comment on the lines for some reason, so quoting here:

If a message has a content-length, enforce only that many bytes are read or written.

Is this the sort of thing that might be able to be overridden? I've had experiences where I've had to interact with HTTP servers that would send incorrect content-length headers before (I believe if you just accepted all bytes until they closed the connection it would work).

If a message has a content-length, enforce only that many bytes are read or written.

Is this the sort of thing that might be able to be overridden?

I suppose it's possible, but that's a really really big bug. Message length discrepancies are the basis of message smuggling vulnerabilities. But to the point of this document, hyper is Correct first, but if something is really needed, Flexible allows us to provide options to turn some things off.

Exciting stuff! Thanks sean


[$500] Web - Tricky emoji is displaying as black square and not easy to delete it

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: <IP_ADDRESS>
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR https://github.com/Expensify/App/pull/31259
Action Performed:

Go to staging.new.expensify.com
Log in with any account
Go to Setting - Workspace
With workspace selected go to Settings,
Try input with emojis, especially tricky ones (e.g. 😶🌫, 🏴),

Expected Result:
Tricky emoji is not displaying as black square
Actual Result:
Tricky emoji is displaying as black square
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/93399543/42787369-b323-4bca-92de-80044426f6d1
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~017082a343b966e0fd
Upwork Job ID:<PHONE_NUMBER>366795264
Last Price Increase: 2023-11-15

Proposal

Please re-state the problem that we are trying to solve in this issue.
The emojis, especially 🏴 is displayed as black square in system, this is not correct.
What is the root cause of that problem?
The root cause of this problem is the font family Windows Segoe UI Emoji.
What changes do you think we should make in order to solve the problem?
Remove Windows Segoe UI Emoji from font family or replace it with another font will solve this problem.
Result
Effect with Windows Segoe UI Emoji in font-family:

Effect without Windows Segoe UI Emoji in font-family:

What alternative solutions did you explore? (Optional)
If the font Windows Segoe UI Emoji is neccessary and can not be removed or replaced, there is a compromise plan, just remove it from desktop web, because this problem only happens in desk web.

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~014062a6096bb8dac5

This issue is related to Windows Segoe UI Emoji font which was added for Windows.

As you can see, the black square is 🏴 in this font.
I think we can hold this and related issues till we find a suitable font for Windows

Based on https://github.com/Expensify/App/issues/31393#issuecomment-1817182124, should this be closed too?

Agreed, @situchan - closing!


[Bug]: incorrect Unix Timestamp value when updating a Date type column

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When I update a Date type column in a table with data extracted from a database, the Unix timestamp value returned is incorrect.
E.g., when setting 2024-08-13 in the datepicker, the updated value internally is 8iAug 13, 2024i02con20.
This makes impossible the update of the date for any table row.
Steps To Reproduce

Create a table widget.
Extract data from a DB with any date column.
For that date column, set type as Date, date format as Unix Timestamp (ms) and display format as YYYY-MM-DD
Make the column editable.
Change the value of the column using the datepicker.
Now, if you check the computed value, it is incorrect.

Public Sample App
No response
Environment
Production
Severity
High (Blocker to building or releasing)
Issue video log
No response
Version
Appsmith v1.31.1

@simonfvr it's possible the unix timestamp format being supplied as the data may be incorrect. Can you share a sample of the data that the table widget has?

The unix timestamp in the data is correct as you can see in the following image.

The first row has been updated to show the incorrect timestamp format.

Hello, what's the status of this?

Thanks for reporting this @simonfvr. We'll analyze this and get back to you as soon as possible.

@carinanfonseca Hello Carina, this is a high severity error since users are not able to update the dates in a column with Date type. Please, solve it ASAP.

@simonfvr I will pick this up this week. Sorry for the delays.

@simonfvr This PR will be available in the next release - 1.44