How to replace the'corner'in the upper left corner

hi, How to replace the'corner'in the upper left corner，I need to change corner to what I need, such as column names.Thanks for your help

can you help me

Hi @wangyangke
If you want to change your corner view, you can use different xml layout in your TableViewAdapter.
@Override
     public View onCreateCornerView() {
         // Get Corner xml layout
         return LayoutInflater.from(context).inflate(R.layout.my_table_view_corner_layout, null);
}

@evrencoskun I'm sorry.Maybe my problem description is wrong, so you didn't understand me ,i need change The upper left corner of the "corner",After setting the rows and columns, the "Corner"  in the top left corner is still displayed in the tableview, and I need to change the "Corner" in the top left corner to my label,and I'm going to label it to explain the row in the first column

Thank you very much for your help. Good luck to you


[oneDNN] Adding BF16 support for FusedPadConv2D

The CycleGAN model has too many FusedPadConv2D. This PR improves ~10% performance on this model with auto mixed precision.
This PR also enabled oneDNN version of pad_with_conv2d support.

Hi @penpornk Can you please review this PR ? Thank you!

Hi @penpornk Can you please review this PR ? Thank you!

@ezhulenev @penpornk , there is an internal failure that I can't see the details, can you help me how to resolve it?


Zooming in High Res PDFs blurs text and making them unreadable

￼When zooming in on some large drawing/floorplan/map pdfs, the zoomed text becomes unreadable.
It looks like it is rendered to the canvas only once and then upscaled.
As an example see this map:
https://public.centerdevice.de/8ddc0fe8-ecc6-456a-bdac-4e5f58b22f35
This is rendered at 400% using acrobat:

and this is how it looks in pdfjs:

This is especially a problem on large maps which require much zooming to be actually readable. if the initial drawing was too small the zooming doesnt help and only enlarges garbage

Deare team.
I am also troubled by the same event.
I attempt #4834 case about  maxCanvasPixels tunning but Nothing change.
Is there any tips/workaround for this problem?
regards.

The only good solution is the one that @yurydelendik provided above, but someone needs to implement that, so there is no solution at the moment.

Thank you for your advice.
I understand that there is no implementation now.
regards.

Blocked by #6419

Duplicate of #6419


Channel B support

Is it planned to support 2 loadcells? First on Channel A and second on Channael B?
I found out, that
Channel A is gain 128 and 64
Channel B is gain 32

Cant you just Instantiate 2 class instances then?
a = Scale(HX711(dout=5, pd_sck=6, gain=128, bitsToRead=24))
b = Scale(HX711(dout=7, pd_sck=8, gain=32, bitsToRead=24))

Oh yes, you are right.


[HUDI-2636] - made release notes more discoverable

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
The release notes were hard to find. It was tribal knowledge to know they are stored under "Downloads"
Brief change log

Renamed the Download tab to Release Notes
Minor tweak to the language on the release notes page
Updated footer

Verify this pull request
(Please pick either of the following options)

This pull request is a trivial doc cleanup

Committer checklist

[X] Has a corresponding JIRA in PR title & commit

[X] Commit message is descriptive of the change

[x] CI is green

[X] Necessary doc changes done or have another open PR

[X] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

I am honestly not sure why we need this change. Even Spark follows the same page naming https://spark.apache.org/downloads.html. If at all, one thing we should do is move the older releases to archive like Spark has done, and I have seen similar pattern in other OSS projects too. As the number of releases continue to increases, it does not make much sense to continue to list all of them on the download page. Instead we should just list the latest release.

Ya, I just researched more across many apache projects. Looks like some do "Downloads" and then have release notes within and some have "Release Notes" and "Downloads" separately. As someone new to the project I wanted to read release notes and I couldn't find them, so my intent was to make it more discoverable, but if "Downloads" is more of standard convention then I agree we can leave it.


Offer cli tool for generating http wrapper module

Considering that telefunc offers a simple solution. It would make sense to offer a simple way to build the http wrapper module easily. Currently it's tied to frameworks (which might help with popularity), but what if people want to setup their own thing. A simple bin/executable/cli tool would help those people.

It's tied to frameworks because Telefunc needs a transfomer.
But I'm thinking of a "vanilla" (i.e. without any transformer) way to use Telefunc. But you'll then loose a lot of niceties, most notably automatic runtime type check.


[timeseries] Add native support for missing values

Issue #, if available: fixes #3886
Description of changes:

Instead of imputing all missing values in target column in TimeSeriesPredictor._check_and_prepare_data_frame, we let each model use its own logic for handling missing values.

GluonTS models (DeepAR, TFT, PatchTST, DLinear) + some local models (Average, SeasonalAverage, NPTS, Naive, SeasonalNaive) handle the missing values natively
Other local models (AutoETS, AutoCES, AutoARIMA, Theta, intermittent models) perform imputation first
MLForecast models use a mix of two strategies: missing values are imputed, but rows that originally contained NaN values are not used for training

Model properties (e.g., whether it can handle missing values) are stored using the _get_tags() mechanism
TimeSeriesPredictor now removes time series consisting of only NaN values from train_data during fit()
Missing values in covariates are still always imputed inside TimeSeriesFeatureGenerator

To do:

[x] Add tests
[x] Add missing values support to MLForecast models
[ ] Benchmark the new NaN handling strategy on datasets with missing values

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Previous CI Run
Current CI Run

Previous CI Run
Current CI Run

Previous CI Run
Current CI Run

huggingface-hub==0.21.4
huggingface-hub==0.22.0

lightning-utilities==0.11.0
lightning-utilities==0.11.1

filelock==3.13.1
filelock==3.13.2

huggingface-hub==0.21.4
huggingface-hub==0.22.0

lightning-utilities==0.11.0
lightning-utilities==0.11.1

filelock==3.13.1
filelock==3.13.2

Previous CI Run
Current CI Run

flatbuffers==24.3.7
flatbuffers==24.3.25

flatbuffers==24.3.7
flatbuffers==24.3.25

Previous CI Run
Current CI Run

Previous CI Run
Current CI Run

Previous CI Run
Current CI Run

Previous CI Run
Current CI Run

@canerturkmen just finished some benchmarking on 12 datasets with missing values / 3 folds each: This PR branch has 62.5% win rate vs. current master branch, so I guess we are good to merge once the problems with tests are resolved.


[Bug]: Eufy Door Lock T8520 not working

Add-on version
1.5.2
Architecture
aarch64
HomeAssistant version
2023.6.2
Operating System type
Linux
Operating system version
Home Assistant OS
Describe the bug
Lock and Unlock services of Eufy door lock are not working
To reproduce
After installing the addon and custom integration from HACS
the door lock is not working its reporting the correct status but lock and unlock functions are not working
Screenshots & Logfiles
No response
Additional context
No response

the addon was able to pick up the lock as MQTT
so had to specify the lock under stations

serial_number: T8520XXXXXXXXX
ip_address: 192.168.XXX.XXX
and that resolved the issue


usb_serial_jtag_ll_write_txfifo() not working with ESP_LOGI (IDFGH-11493)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
When wring a buffer through usb_serial_jtag_ll_write_txfifo() if ESP_LOGI is present it is not updating the buffer to serial.
This works
extern "C" void app_main()
{
	int cnt;
        int rxcnt;
	uint8_t rxbuf[64];
	while (true)
	{
		if (usb_serial_jtag_ll_rxfifo_data_available())
                {
                    rxcnt = usb_serial_jtag_ll_read_rxfifo(rxbuf,64);
                    // ESP_LOGI("TAG","Data %s size : %d\n",rxbuf,rxcnt);

			        if (rxcnt > 1)
			        {
				        uint8_t buff[6];
				        buff[0] = '\r';
				        buff[1] = '\n';
				        buff[2] = 'H';
				        buff[3] = 'I';
				        buff[4] = '\r';
				        buff[5] = '\n';
				        usb_serial_jtag_ll_write_txfifo(buff, sizeof(buff));
            	                        usb_serial_jtag_ll_txfifo_flush();
			        }

                }
	}

}

This Doesn't work

extern "C" void app_main()
{
	int cnt;
    int rxcnt;
	uint8_t rxbuf[64];
	while (true)
	{
		if (usb_serial_jtag_ll_rxfifo_data_available())
                {
                    rxcnt = usb_serial_jtag_ll_read_rxfifo(rxbuf,64);
                    ESP_LOGI("TAG","Data %s size : %d\n",rxbuf,rxcnt);

			        if (rxcnt > 1)
			        {
				        uint8_t buff[6];
				        buff[0] = '\r';
				        buff[1] = '\n';
				        buff[2] = 'H';
				        buff[3] = 'I';
				        buff[4] = '\r';
				        buff[5] = '\n';
				        usb_serial_jtag_ll_write_txfifo(buff, sizeof(buff));
            	                        usb_serial_jtag_ll_txfifo_flush();
			        }

                }
	}

}

Do you by any chance have CONFIG_ESP_CONSOLE_SECONDARY_USB_SERIAL_JTAG enabled? If yes, this would mean that you are trying to use usb_serial_jtag peripheral both via the low-level functions and at the same time via the higher-level console driver — which is a combination which is unlikely to work.

@igrr  nope i have not enable it.  this is my sdkconfig file.
sdkconfig.txt

@igrr  For me the usb_serial_jtag_read_bytes(rxbuf,64,0); didint work it was not reaidng any input thats the reason i used the low level code with log level code everything works fine if i do esp_log_level_set("*",ESP_LOG_NONE);

For me the usb_serial_jtag_read_bytes(rxbuf,64,0); didint work it was not reaidng any input

Could you post the original code (with usb_serial_jtag driver, not the LL code) which didn't work? Also, please mention the IDF version (git describe output).

@nikhil-robinson  well the LL code works for me using ESP_LOGI, see below.
I am also using CONFIG_ESP_CONSOLE_USB_SERIAL_JTAG_ENABLED
However, rxcnt returned by usb_serial_jtag_ll_read_rxfifo() never goes above 1 ( although no chars are lost)
#include "sdkconfig.h"
#include "freertos/FreeRTOS.h"
#include "freertos/task.h"
#include "esp_system.h"
#include "esp_spi_flash.h"
#include "string.h"
#include "hal/usb_serial_jtag_ll.h"

#include "esp_log.h"

static const char *TAG = "echo";

void mytask1(void *pvParameter)
{
    uint8_t *rxbuf;
    int cnt;
    rxbuf = (uint8_t *)malloc(64);
    int rxcnt;

    while (1)
    {
        if (usb_serial_jtag_ll_rxfifo_data_available())
        {
            rxcnt = usb_serial_jtag_ll_read_rxfifo(rxbuf,64);
            ESP_LOGI(TAG, "got %d\n", rxcnt);
            vTaskDelay(pdMS_TO_TICKS(10));
            cnt = (int)usb_serial_jtag_ll_write_txfifo((const uint8_t *)rxbuf, rxcnt);
            usb_serial_jtag_ll_txfifo_flush();
            // printf("Send %d characters to host \n", cnt);
        }
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
    free(rxbuf);
    vTaskDelete(NULL);
}

void app_main(void)
{
    esp_log_level_set("*", ESP_LOG_INFO);
    ESP_LOGI(TAG, "App started!");
    xTaskCreate(mytask1, "mytask1", 1024 * 5, NULL, 1, NULL);
}

well the LL code works for me using ESP_LOGI, see below. I am also using CONFIG_ESP_CONSOLE_USB_SERIAL_JTAG_ENABLED

@jetpax Sorry for not being clear. When I wrote that this is unlikely to work, I meant that you are doing something that is unsupported. Although it might end up working in some scenarios, but in general we don't guarantee it will.
Essentially you have two pieces of code in the system accessing the same underlying layer without any coordination:

the console implementation, calling usb_serial_jtag driver, which in in turn calls usb_serial_jtag LL
your mytask1 function, which also calls usb_serial_jtag LL.

As I wrote in https://github.com/espressif/esp-idf/issues/12605#issuecomment-1817449614 — you have to decide whether you want to control the USB_SERIAL_JTAG peripheral using the higher-level stdio functions or using the driver, and use just one of the two approaches.
Also it is highly recommended to use the usb_serial_jtag driver instead of the underlying LL functions.

My original usb_jtag_code.

#include <stdio.h>
#include "driver/usb_serial_jtag.h"
#include "esp_vfs_usb_serial_jtag.h"
#include "esp_vfs_dev.h"
#include <fcntl.h>

static void initUart() {

    /* Disable buffering on stdin */
    setvbuf(stdin, NULL, _IONBF, 0);
    setvbuf(stdout, NULL, _IONBF, 0);

    /* Enable non-blocking mode on stdin and stdout */
    fcntl(fileno(stdout), F_SETFL, 0);
    fcntl(fileno(stdin), F_SETFL, 0);

    usb_serial_jtag_driver_config_t usb_serial_jtag_config;
    usb_serial_jtag_config.rx_buffer_size = 4096;
    usb_serial_jtag_config.tx_buffer_size = 4096;

    esp_err_t ret = ESP_OK;
    /* Install USB-SERIAL-JTAG driver for interrupt-driven reads and writes */
    ret = usb_serial_jtag_driver_install(&usb_serial_jtag_config);
    if (ret != ESP_OK) {
        return;
    }

    /* Tell vfs to use usb-serial-jtag driver */
    esp_vfs_usb_serial_jtag_use_driver();

}

static void Receive_callback(void *argument)
{

    uint8_t rxbuf[4096];
    size_t idx = 0;
    char ch;
    for (;;)
    {
        idx = usb_serial_jtag_read_bytes(rxbuf, 4096, 0);
        if(idx)
        {
            rxbuf[idx] ='\0';
            printf("RECIVED [%d] bytes: %s\n",idx, rxbuf);
        }
        vTaskDelay(1);
    }
}

void app_main(void)
{

    initUart();
    xTaskCreate(Receive_callback,"UART receive callback",4096 *2,NULL,5,NULL); // receiving commands from main uart

}

This was not working on this idf version :
idf version ESP-IDF v5.1.1-dirty
but i recently update my idf to latest release 5.1 (v5.1.2-89-g5c61c89308) and there it works

@igrr  regarding usb_jtag_serial i am also facing one issue with the esp32h2 module.
sleep_modes.c: In function 'light_sleep_uart_prepare':
/home/nikhi/idf5/esp-idf/components/esp_hw_support/sleep_modes.c:153:61: error: 'CONFIG_ESP_CONSOLE_UART_BAUDRATE' undeclared (first use in this function); did you mean 'CONFIG_ESP_CONSOLE_UART_NUM'?
  153 | #define UART_FLUSH_US_PER_CHAR              (10*1000*1000 / CONFIG_ESP_CONSOLE_UART_BAUDRATE)
      |                                                             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

sdkconfig.txt


Application won't reply to user requests based on channel-toggle configuration

Issue

When channel-toggle is set to true, conversations in Public and Private Threads will cease to work without reply.
When channel-toggle is set to false, conversations in GuildText channels will cease to work without reply as well.

Steps to reproduce

Configure the channel-toggle server preference to be true
Open up a new public chat thread by running the Slash Command /thread
Attempt to query the bot using @<bot_username> and it should not reply
This also happens in GuildText channels when channel-toggle is set to false

Solution(s)

Implement a solution that will notify, based on the channel-toggle, that the bot cannot respond so users know to change the configuration.
Another solution can be to do away with the toggle at all and allow the bot to chat anywhere as it poses no problem in general. If this course of action is taken, maintain how filename formats are created/edited as it makes the most sense for what is a channel chat history and what is a thread chat history.

References

Refer to commands/channelToggle.ts here and events/messageCreate.ts here  for usage.

I am in favor of the second solution as it will be 1 less configuration to worry about.
If it becomes too complex, the first solution is a lot faster to implement

I am in favor of the second solution as it will be 1 less configuration to worry about.
If it becomes too complex, the first solution is a lot faster to implement

I think this is the best course of action.

Now realizing that if we just make it universal that "<channel_id>-<username>.json" universal then it makes sense no matter the context.

Private threads should only ever have 1 person as it is private.
The threadDelete event will now have to handle possible multiple chat histories if for SOME reason multiple people talk in that channel.
In a general channel, a user's history should still only be autonomous from other users.

This shouldn't be crazy but it makes sense. Have a universal chat history name but treat them by case on how they are Created, Read, Updated, Deleted (CRUD).
cc: @JT2M0L3Y

Upon testing out Private Threads I have found this. Keep this commend below in mind when implementing a solution for this bug.