can not install this library

composer require "laravel/cashier":"~7.0"
roblem 1     - laravel/cashier v7.1.2 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.1.1 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.1.0 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.9 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.8 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.7 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.6 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.5 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.4 requires stripe/stripe-php ~3.0 -> satisfiable by stripe/stripe-php[v3.0.0, v3.1.0, v3.10.0, v3.10.1, v3.11.0, v3.12.0, v3.12.1, v3.13.0, v3.14.0, v3.14.1, v3.14.2, v3.14.3, v3.15.0, v3.16.0, v3.17.0, v3.17.1, v3.18.0, v3.19.0, v3.2.0, v3.20.0, v3.21.0, v3.22.0, v3.23.0, v3.3.0, v3.4.0, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.8.0, v3.9.0, v3.9.1, v3.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.3 requires stripe/stripe-php ~3.0 -> satisfiable by stripe/stripe-php[v3.0.0, v3.1.0, v3.10.0, v3.10.1, v3.11.0, v3.12.0, v3.12.1, v3.13.0, v3.14.0, v3.14.1, v3.14.2, v3.14.3, v3.15.0, v3.16.0, v3.17.0, v3.17.1, v3.18.0, v3.19.0, v3.2.0, v3.20.0, v3.21.0, v3.22.0, v3.23.0, v3.3.0, v3.4.0, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.8.0, v3.9.0, v3.9.1, v3.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.2 requires stripe/stripe-php ~3.0 -> satisfiable by stripe/stripe-php[v3.0.0, v3.1.0, v3.10.0, v3.10.1, v3.11.0, v3.12.0, v3.12.1, v3.13.0, v3.14.0, v3.14.1, v3.14.2, v3.14.3, v3.15.0, v3.16.0, v3.17.0, v3.17.1, v3.18.0, v3.19.0, v3.2.0, v3.20.0, v3.21.0, v3.22.0, v3.23.0, v3.3.0, v3.4.0, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.8.0, v3.9.0, v3.9.1, v3.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.13 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.12 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.11 requires stripe/stripe-php ~5.0 -> satisfiable by stripe/stripe-php[v5.0.0, v5.1.0, v5.1.1, v5.1.2, v5.1.3, v5.2.0, v5.2.1, v5.2.2, v5.2.3, v5.3.0, v5.4.0, v5.5.0, v5.5.1, v5.6.0, v5.7.0, v5.8.0, v5.9.0, v5.9.1, v5.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.10 requires stripe/stripe-php ~4.0 -> satisfiable by stripe/stripe-php[v4.0.0, v4.0.1, v4.1.0, v4.1.1, v4.10.0, v4.11.0, v4.12.0, v4.13.0, v4.2.0, v4.3.0, v4.4.0, v4.4.1, v4.4.2, v4.5.0, v4.5.1, v4.6.0, v4.7.0, v4.8.0, v4.8.1, v4.9.0, v4.9.1] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.1 requires stripe/stripe-php ~3.0 -> satisfiable by stripe/stripe-php[v3.0.0, v3.1.0, v3.10.0, v3.10.1, v3.11.0, v3.12.0, v3.12.1, v3.13.0, v3.14.0, v3.14.1, v3.14.2, v3.14.3, v3.15.0, v3.16.0, v3.17.0, v3.17.1, v3.18.0, v3.19.0, v3.2.0, v3.20.0, v3.21.0, v3.22.0, v3.23.0, v3.3.0, v3.4.0, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.8.0, v3.9.0, v3.9.1, v3.9.2] but these conflict with your requirements or minimum-stability.     - laravel/cashier v7.0.0 requires stripe/stripe-php ~3.0 -> satisfiable by stripe/stripe-php[v3.0.0, v3.1.0, v3.10.0, v3.10.1, v3.11.0, v3.12.0, v3.12.1, v3.13.0, v3.14.0, v3.14.1, v3.14.2, v3.14.3, v3.15.0, v3.16.0, v3.17.0, v3.17.1, v3.18.0, v3.19.0, v3.2.0, v3.20.0, v3.21.0, v3.22.0, v3.23.0, v3.3.0, v3.4.0, v3.5.0, v3.6.0, v3.7.0, v3.7.1, v3.8.0, v3.9.0, v3.9.1, v3.9.2] but these conflict with your requirements or minimum-stability.     - Installation request for laravel/cashier ~7.0 -> satisfiable by laravel/cashier[v7.0.0, v7.0.1, v7.0.10, v7.0.11, v7.0.12, v7.0.13, v7.0.2, v7.0.3, v7.0.4, v7.0.5, v7.0.6, v7.0.7, v7.0.8, v7.0.9, v7.1.0, v7.1.1, v7.1.2].

Can you share your composer.json?

Hi @kohenkatz
Something else i guess i had added stripe php lib already in my composer with version 6+ and cashier wanted 5.9, so that was making all problem. so when i removed my stripe lib and give retry to cashier it worked. Thank you

@rajjanorkar That's what I expected (and why I asked to see composer.json). Glad you figured it out.


[RN] L10n: Chinese: Search: "Очистить все" isn't translated into

Actual result: Очистить все
Expected result: 清除所有

Verified successfully on dev v.1.0.0 (941) (RN iOS)

In Android 10 it works correctly
But 'Очистить все' button should be translated into ZH

Verified successfully on  RN on production (v.1.3.5 (25) - iphone 11pro


How to Create Custom Image File Explorer in PHP

Proposed title of article
How to Create Custom Image File Explorer in PHP
Proposed article introduction
A file explorer, specially designed for showcasing image files will be a cool addition to your PHP web application when you are handling images.
Imagine an image file explorer built in PHP with options to options to browse files in icon, list and detailed view. That is what we are going to see and build in this article.
Having feature to explore image files with different modes of display will enrich your web applications. Image gallery is a popular choice but if it comes added with other views, it will be a definite win for the users.
Key takeaways
1.The Benefits of Creating a Custom Image Explorer
2.Integrate image explorer with existing PHP/jQuery libraries
3.Create an image file explorer using an HTML interface.
4.File Organization
5.Script for the database
Article quality
This article is straight to the point and it's code snippet will be understandable by both professional and novices
References
N/A
Happy coding

Good afternoon and thank you for submitting your topic suggestion. @Sammy104
Your topic form has been entered into our queue and should be reviewed (for approval) as soon as a content moderator is finished reviewing the ones in the queue before it.

@Sammy104
We're really looking for unique/original content, and based on the content provided, it seems that information that you intend to cover is already readily available through the documentation or via many other blog sites.
Could you please expand upon how your content will differ from what is already available through other websites and documentation? We lean towards content that offers an original viewpoint/approach around programming-centric topics.

My article will be more easy to understand and will go deeper than other
websites
On Sat, Oct 2, 2021, 03:13 hectorkambow @.***> wrote:

@Sammy104 https://github.com/Sammy104
We're really looking for unique/original content, and based on the content
provided, it seems that information that you intend to cover is already
readily available through the documentation or via many other blog sites.
https://www.google.com/search?q=Create+Custom+Image+File+Explorer+in+PHP&ei=pqNXYfa_I9nOtQbxgI_QDw&ved=0ahUKEwj2qvKmuKrzAhVZZ80KHXHAA_oQ4dUDCA8&uact=5&oq=Create+Custom+Image+File+Explorer+in+PHP&gs_lcp=Cgdnd3Mtd2l6EAMyBQghEKABOgcIABBHELADSgQIQRgAUMH7A1jB-wNgxv0DaARwAngAgAGBAYgBgQGSAQMwLjGYAQCgAQKgAQHIAQjAAQE&sclient=gws-wiz
Could you please expand upon how your content will differ from what is
already available through other websites and documentation? We lean towards
content that offers an original viewpoint/approach around
programming-centric topics.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/section-engineering-education/engineering-education/issues/4062#issuecomment-932643100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVW3337GFVLQGVSWN5GJTXTUEZFBFANCNFSM5E6GDFYA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

In my article I might show examples and script of the database to make differ from others

My code snippet will be very easy to understand and it will be accompanied by examples to make it much easier to understand.

My explanation will go beyond the official document and what is already covered in other articles. I will also use modern PHP version(version 8)

At the key takeaways option number five, I wrote that I will provide the script of the database. This will be accompanied by worked-out examples in the modern PHP version. I believe there is no article in other blogs that have covered this. That is how my article will be unique


ci (c sshnpd): IWYU action

See #1506

Creating the action wasn't trivial, so I'm not going to spend more time on this unless a bigger need for it comes about.


Replace all static fonts with cdn fonts and merge css files into single alicht.css

That way it's handier to use alicht in projects.

Do you mean using Google Fonts directly?

Yes, exactly.

Okay :)
Niléane Dorffer [:Nildëala]
nildeala.fr
On 13 août 2017 à 15:15 +0200, YouniS Bensalah<EMAIL_ADDRESS>wrote:

Yes, exactly.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.


[RTL bug] UART RX path broken at the chip top

Issue is in the jtag_mux instance inside chip top instances top_earlgrey_*.sv.
TdiIdx is DIO 11. It is muxing off the UART RX pin instead.
Rest of the DIO pins it should be looking at are also off by 1.
Fix coming soon.

Thanks @msfschaffner for helping me find this very quickly!


Russian translation

Hi!
I translated Cachet to russian. Can you merge it?

Hey, thanks for your pull request! I marked some missing translations, could you maybe add them?

Thanks for going through this @ApfelUser.

Fixed strings. Also in CrowdIn.com

:+1:

Thanks to you both @alexxwiz and @ApfelUser for this PR :)

@alexxwiz could you email me at<EMAIL_ADDRESS>:)

@jbrooksuk I did.

@jbrooksuk Done too.

Cheers guys :)


Temperature sensor crashes RISC-V (IDFGH-8723)

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.

IDF version.
v5.1-dev-1626-g4b6d9c8ad3
Operating System used.
macOS
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
No response
Development Kit.
ESP32-S3-MINI-1U
Power Supply used.
USB
What is the expected behavior?
The Technical Reference Manual, chapter 39.4, states how to configure and read out the temperature sensor, namely:

Started by software, i.e. by CPU or ULP-RISC-V configuring related registers:
– Set SENS_TSENS_POWER_UP_FORCE and SENS_TSENS_POWER_UP to enable the temperature sensor.
– Wait for a while, then configure SENS_TSENS_DUMP_OUT. The output value gradually approaches the actual temperature linearly as the measurement time increases.
– Wait for SENS_TSENS_READY, and read the conversion result from SENS_TSENS_OUT.

This translate roughly to this:
REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP_FORCE);
REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP);
ulp_riscv_delay_cycles(8000);
REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_DUMP_OUT);
while (REG_GET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_READY) == 0) {}
uint32_t raw_temperature = REG_GET_FIELD(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_OUT);

This code, however, is an infinite loop at while which effectively crashes the coprocessor. From the ESP-IDF driver one can see that also SENS_TSENS_CLK_EN and SENS_TSENS_XPD_FORCE need to be enabled, that is,
REG_SET_BIT(SENS_SAR_PERI_CLK_GATE_CONF_REG, SENS_TSENS_CLK_EN);
REG_SET_BIT(SENS_SAR_TSENS_CTRL2_REG, SENS_TSENS_XPD_FORCE);

need to be set, too. The documentation also misses that SENS_TSENS_DUMP_OUT should be reset after making a readout.
While this fixes the infinite loop, the read out values are wrong in deep sleep, always returning the value 1 or 127. I tried various register settings and compared various register values when running during deep sleep and during normal operation, but cannot find what needs to be set to read out the correct temperature during deep sleep; the technical reference manual is too lacking to be of much help.
What is the actual behavior?
An infinite loop when following the documentation. Wrong values after making the required fixes to not have an infinite loop.
Steps to reproduce.
Here's a minimal code that reads the temperature and pauses for about 1s in total ten times and then wakes up the main cpu:
#include <stdio.h>
#include <stdint.h>
#include <stdbool.h>
#include <soc/rtc_cntl_reg.h>
#include <ulp_riscv.h>
#include <ulp_riscv_utils.h>
#include <ulp_riscv_gpio.h>

#define N 10

static int i = 0;
static int j = 0;

int which;
uint32_t data0[N];
uint32_t data1[N];

int main()
{
    uint32_t temperature;

    REG_SET_BIT(SENS_SAR_PERI_CLK_GATE_CONF_REG, SENS_TSENS_CLK_EN);
    REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP_FORCE);
    REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP);
    REG_SET_BIT(SENS_SAR_TSENS_CTRL2_REG, SENS_TSENS_XPD_FORCE);

    ulp_riscv_delay_cycles(8000);

    REG_SET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_DUMP_OUT);
    while (REG_GET_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_READY) == 0) {}
    REG_CLR_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_DUMP_OUT);
    temperature = REG_GET_FIELD(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_OUT);

    REG_CLR_BIT(SENS_SAR_TSENS_CTRL2_REG, SENS_TSENS_XPD_FORCE);
    REG_CLR_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP_FORCE);
    REG_CLR_BIT(SENS_SAR_TSENS_CTRL_REG, SENS_TSENS_POWER_UP);

    if (j == 0) {
        data0[i] = temperature;
    } else {
        data1[i] = temperature;
    }

    if (++i < N) {
        REG_SET_FIELD(RTC_CNTL_ULP_CP_TIMER_1_REG, RTC_CNTL_ULP_CP_TIMER_SLP_CYCLE, 150000);
        REG_SET_BIT(RTC_CNTL_ULP_CP_TIMER_REG, RTC_CNTL_ULP_CP_SLP_TIMER_EN);
    } else {
        which = j;
        j = j == 0 ? 1 : 0;
        i = 0;
        ulp_riscv_wakeup_main_processor();
    }
    return 0;
}

Debug Logs.
No response
More Information.
No response

Hi @NoNullptr,
Your basic steps seem correct to me. I have an internal test branch for adding support that does the same, but unfortunately we discovered that the results seems to be incorrect after entering deep sleep. The current theory is that we might need to adjust some sleep parameters to be able to correctly use the temp sensor during sleep, so right now the support for ulp temp sensor is blocked on that.
The team responsible for the RTC part of the SW is looking at it, so as soon as this is resolved on their end we will be able to add support for it in IDF.

Thank you for your response and looking into it, I am looking forward to having it resolved.

This has been stale for quite some time now – is there any progress on this issue?

Hi @NoNullptr,
Your basic steps seem correct to me. I have an internal test branch for adding support that does the same, but unfortunately we discovered that the results seems to be incorrect after entering deep sleep. The current theory is that we might need to adjust some sleep parameters to be able to correctly use the temp sensor during sleep, so right now the support for ulp temp sensor is blocked on that.
The team responsible for the RTC part of the SW is looking at it, so as soon as this is resolved on their end we will be able to add support for it in IDF.

@ESP-Marius So how is the status now? Any update?

Hi, I am also very much interested in the topic. I also wasn't able to get it running.
Is there any update?
Best regards,
Christian

Seems you not set REGI2C_WRITE_MASK(I2C_SAR_ADC, I2C_SARADC_TSENS_DAC, tsens_dac);. Please check how esp-idf temperature sensor driver did.

Some confidential information is not ready to be shown in trm.. Please refer to espressif driver. As for this issue we will close it because it's not an esp-idf issue. Feel free to comment it or reopen it if you got any update. Thanks!

Hi @mythbuster5,
thanks very much for your answer. I already tried including "REGI2C_WRITE_MASK(I2C_SAR_ADC, I2C_SARADC_TSENS_DAC, 15)";
Problem is that I get a linker error that REGI2C_WRITE_MASK is not found (undefined reference to `regi2c_ctrl_write_reg_mask')
Do you know how to solve that?
Best,
Christian

The way to solve that is refer to idf driver *_ll.h function tells you how to use esp chip register.


[RELAY]Reduce ops sum/max/min/mean/prod

#1799
Level 4 Ops

sum
max
min
mean
prod

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from others in the community.

please rebase against master after #1934 to make use of the newly introduced API and add test-case to make sure text format works.


SageMaker pipeline

Dear @Yukiya-Umimi,
We have been training your models, but unfortunately ran into some issues. We would like to propose the following changes to your codebase:

Bugfix mha2nnunet settings to resample to 3.0x0.5x0.5 and crop to [24, 384, 384]: https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/commit/443f703298ac3fc5a953d192ab57d8e51b30c858
Make repository pip-installable for easier importing of functions: https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/commit/446ebc688fbcf0cbbf1c8ff13a89fb771273211c
Restructure Docker container definition: https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/commit/a479e03d6fd118a1bc73122bcab68e428935fa8d
Add training code for segmentation model: https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/commit/29d8416b8d3201a4064d652a9ca772bed8fa466b

Additionally, I would like to propose some minor changes:

Cleaned up Python cache files
Created __init__.py files for making the repo pip-installable
Change imports, e.g. from utils import ... to from segmentation.utils import ...  for making the repo pip-installable
Fix version of scikit-image to 0.20.0 to ensure skimage.metrics exists
Remove unused imports

I've put all of these proposed changes in this PR. Could you go through the changes, and if your agree, merge them into main?
Thanks!

Hi,
It is OK,  I have great confidence in your work!
Best,
Honey K
| |
yukiya
|
|
@.***
|
---- Replied Message ----
| From | Joeran @.> |
| Date | 3/26/2023 20:22 |
| To | @.> |
| Cc | @.> ,
@.> |
| Subject | [Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge] SageMaker pipeline (PR #10) |
Dear @Yukiya-Umimi,
We have been training your models, but unfortunately ran into some issues. We would like to propose the following changes to your codebase:
Bugfix mha2nnunet settings to resample to 3.0x0.5x0.5 and crop to [24, 384, 384]: 443f703
Make repository pip-installable for easier importing of functions: 446ebc6
Restructure Docker container definition: a479e03
Add training code for segmentation model: 29d8416
Additionally, I would like to propose some minor changes:
Cleaned up Python cache files
Created init.py files for making the repo pip-installable
Change imports, e.g. from utils import ... to from segmentation.utils import ... for making the repo pip-installable
Fix version of scikit-image to 0.20.0 to ensure skimage.metrics exists
Remove unused imports
I've put all of these proposed changes in this PR. Could you go through the changes, and if your agree, merge them into main?
Thanks!
You can view, comment on, or merge this pull request online at:
https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/pull/10
Commit Summary
8b436b9 Cleanup
4449bac Bugfix
7503fda Safer with file permissions
1780970 Cleanup
29d8416 Supervised segmentation training script
bbede2f Cleanup imports
df290cb Cleanup imports
9c905a5 Docker container for segmentation training
65e3468 Update scikit-image
3f82db4 Cleanup imports
8ff71f1 Add missing dependency
4c37241 Cleanup imports
ed52843 Cleanup imports
1bc1ab3 Bugfix
443f703 Bugfix preprocessing resampling
a878c2b Move Docker container definitions
b88a08d Add preprocessing Docker container
4845190 Temporarily use this branch
cea67e5 Cleanup
a073b20 Cleanup & init files
446ebc6 Make repository pip-installable
a479e03 Cleanup Docker containers & bugfix
File Changes
(34 files)
R.dockerignore (0)
ADockerfile (18)
Abuild.sh (4)
Aclassification/init.py (0)
Dclassification/pycache/config.cpython-37.pyc (0)
Dclassification/pycache/trainer.cpython-37.pyc (0)
Dclassification/pycache/utils.cpython-37.pyc (0)
Apreprocess/init.py (0)
Mpreprocess/preprocess.py (9)
Apyproject.toml (22)
Arequirements.txt (16)
Asegmentation/init.py (0)
Dsegmentation/pycache/config.cpython-37.pyc (0)
Dsegmentation/pycache/data_loader.cpython-37.pyc (0)
Dsegmentation/pycache/loss.cpython-37.pyc (0)
Dsegmentation/pycache/metrics.cpython-37.pyc (0)
Dsegmentation/pycache/model.cpython-37.pyc (0)
Dsegmentation/pycache/trainer.cpython-37.pyc (0)
Dsegmentation/pycache/utils.cpython-37.pyc (0)
Msegmentation/config.py (5)
Msegmentation/data_loader.py (9)
Msegmentation/predict_2d.py (15)
Msegmentation/requirements.txt (3)
Msegmentation/run.py (11)
Msegmentation/trainer.py (33)
Msegmentation/utils.py (8)
Asetup.cfg (54)
Asetup.py (18)
Dsubmit_result/pycache/old_unet.cpython-37.pyc (0)
Msubmit_result/process.py (20)
Mtrain_1_classification.py (8)
Mtrain_2_segmentation.py (56)
Dtraining_dockers/1_classification/Dockerfile (23)
Dtraining_dockers/1_classification/build.sh (4)
Patch Links:
https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/pull/10.patch
https://github.com/Yukiya-Umimi/ITUNet-for-PICAI-2022-Challenge/pull/10.diff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>


Implement Custom Exception Subclass for Enhanced Error Handling

Closes: #3
This PR introduces a new base exception class, JsonFixError, to improve error handling in accordance with PEP 352, which advises against raising generic Exception directly. By subclassing JsonFixError, we can provide more specific error information and make it easier for users to handle different types of errors effectively.
Changes include:

Creating a JsonFixError class as the base class for all custom exceptions.
Modifying existing error raising instances to use these new custom exceptions instead of the generic Exception.

This approach not only aligns with best practices for Python error handling but also enhances the library's usability by allowing more targeted exception handling and clearer error messages for all users.
Passes all tests

Thanks very much for your contribution and explanation around exceptions!
Best regards

Happy to help


Tracking when object is out of frame

Hi! Thanks for the great model, when I first run it I was pretty much impressed by the quality \ FPS trade-off.
However, in my scenario, object is not always in the frame (i.e. it can disappear and appear again after several seconds \ minutes). I've slightly modified the code so that tracker.track returns also a classification score, but this does not help much. When the object is out of frame, tracker can stick to the wrong object with high enough confidence.
I'm considering now implementing a classification head (that will classify is search object is present on the template) with corresponding changes in the training procedure and would like to know other thoughts how to deal with such scenario.
Thanks!

This is a typical long-term tracking problem. You can add a classification head or refer to some previous long-term tracking methods (see VOT challenge report for more details).


Issue with Creating soca-jobs* Index for SOCA Dashboard

Hello,
On the SOCA web page under "My Activity," I am getting the following message:
"Unable to retrieve index ID for soca-jobs*. To do the initial setup, follow instructions available on https://awslabs.github.io/scale-out-computing-on-aws/analytics/monitor-cluster-activity/"
However, when I follow the instructions in the documentation, I am unable to create the soca-jobs* index. Instead, I can only create the soca_jobs* index, which results in the Dashboard not displaying correctly.
Version: OpenSearch 2.11
Thank you for your help.

Context: https://github.com/awslabs/scale-out-computing-on-aws/discussions/128
Index are not retrieved correctly when using OpenSearch. OpenSearch is still fully operational and can be accessed via the OpenSearch dashboard URL, however, reporting from the SOCA console is currently broken.
Fix: Query OpenSearch API to returns the list of index. This is a low priority task as there is currently a workaround, and I'm planning to fix that in the upcoming release for Q3 this year. Let me know if you need to expedite this before.


Add virtual destructor to micro_context

Some platforms generate warnings/errors that a class that has
virtual functions should have virtual destructor
BUG=observe in internal presubmit

How does this relate to TF_LITE_REMOVE_VIRTUAL_DELETE? If it’s different then this looks fine.

IIUC, they serve different purpose and both are needed. explicit empty virtual destructor() is needed to make some compiler not to spit out warnings/errors when it sees a class has virtual function, but no virtual destructor.  TF_LITE_REMOVE_VIRTUAL_DELETE removes the default virtual "delete" operator only, which is used by the C++ itanium abi to correctly implement "delete" on destruction of virtual class.


[SRP] Introduce 2020-08-01-preview version.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

The PR should be be merged before the server deployment is ready with this API version.

Please clarify which regions has finished the deployments, and I will test on it.

@blueww deployment of SRP won't be complete for at least another two weeks or so, due to Code Yellow. This PR is mostly requested by ARM (@pilor) for reviewing / approving SRP manifest change that introduces a new resource type "deletedAccount".
For now there is no need to test this or to work on SDK publication.

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

Hi @blueww, are you aware of .Net failures? If you are fine, please let me know.
@huizlAzure we will recommend customer to use https://portal.azure-devex-tools.com/branch/create to create new API version, which will help us review what you actually do besides copied files.

@Juliehzl
The .net SDK failure seems caused by some auto rest issue, but not for the swagger

2020-09-03T18:55:32.826Z: [Azure/azure-sdk-for-net][AutoRest]    Installing AutoRest extension<EMAIL_ADDRESS>(2.3.55)
[
'##[error]2020-09-03T18:55:33.820Z: [Azure/azure-sdk-for-net][AutoRest] realpath(): Permission denied'
]

Would you please help to see how to fix it?

/azp run automation - sdk


docs: add popular package managers installation

Added tabs for popular package manager in the package installation section.
Also, I fixed a little typescript type warning in ts-rest-express.ts.

https://user-images.githubusercontent.com/7936061/216814679-321bbfc2-db85-455d-867a-1e4781ae2963.mov

My bad, just realized that it might be in conflict with PR #163

Codecov Report

Merging #165 (486c739) into main (478471f) will not change coverage.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main     #165   +/-   ##
=======================================
  Coverage   62.93%   62.93%
=======================================
  Files          11       11
  Lines         286      286
  Branches       69       71    +2
=======================================
  Hits          180      180
  Misses         96       96
  Partials       10       10

Impacted Files
Coverage Δ

libs/ts-rest/express/src/lib/ts-rest-express.ts
11.84% <0.00%> (ø)

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

This looks great! Thanks for the PR @rifaldhiaw
@all-contributors add @rifaldhiaw for documentation

@rifaldhiaw love this change. Great contribution mate! ♥


cleanup Gruntfile.js to be more maintainable

Broke the large grunt file into separate files in the grunt folder. This should be more maintainable going forward. I was able to run most of the tasks; except grunt docs.

Gulp is much faster, and the benefits of gulp are not just speed, its also much more tightly integrated with nodejs, which means you can use the same modules as for nodeJS. So this custom functionality your talking about might already have been solved. And if not the tight integration with nodejs should make the issues quite easy to solve.
(but maybe we could make a list of functionality that the grunt handels right now. Then people might have the interest in changing it for their own purpose.
It does give a much better and more seamless workflow to swap.

@sp90, if you're up for it, convert all grunt tasks to gulp tasks, open a PR, and we can then test-drive that.

I would be glad to do it, i already have some draw ups of some great gulp setups,
If you can provide me with a list of functionality i will with out a doubt start working on it :)

@sp90 it's all in the gruntfile ;)

@javorszky Okay will look into it :+1:

Ghost already has a large user base who would be affected by this change. For that reason, there needs to be demonstrable, clear & significant benefits to gulp over grunt for us to make the switch. So far all of the benefits mentioned have been intangible, other than speed, which as @javorszky has already said, won't really affect us as the speed of our tasks is affected by things other than grunt.

@ErisDS so even if i convert it all into gulp, it wont be used because you dont wanna trouble the userbase to swap from grunt init & grunt prod with gulp init and gulp prod, the speed is significantly faster, and the modules that you have to write for gulp is probably already in there if not very easy to create

Btw stuff like this would be more appropriate to run in npm postinstall so when you run npm install it would run it afterwards.
 // #### Run bower install
                // Used as part of `grunt init`. See the section on [Building Assets](#building%20assets) for more
                // information.
                bower: {
                    command: path.resolve(cwd + '/node_modules/.bin/bower --allow-root install'),
                    options: {
                        stdout: true,
                        stdin: false
                    }
                },

@ErisDS so even if i convert it all into gulp, it wont be used because you dont wanna trouble the userbase

Not unless there are "demonstrable, clear & significant benefits".

the speed is significantly faster

Which tasks will run faster? How much faster? Who will it benefit?

The modules that you have to write for gulp is probably already in there if not very easy to create

We already have all of the functionality we need written and working! I would so much rather you spent your time helping us fix a bug or add a new feature than rewriting stuff that already works without a clear reason for doing so. Unless you can demonstrate a measurable advantage, this really is little more than a religious debate.

@ErisDS Everyone will benefit because:

According to Six Revisions, (Gulp processes tasks ~4x faster than Grunt)[http://sixrevisions.com/web-development/grunt-vs-gulp/] (Do a Find in Page for "Measuring Task-Execution Speed" and see tests they've done)
Configuration is much easier to read for maintainers, contributors, and newbies

I am very interested in using Ghost as a platform to develop sites with my company and for my own clients but I find Grunt configs very difficult to look at. Any thoughts on the link above?


Incorrect device config for ZWN-RSM2-PLUS

https://github.com/zwave-js/node-zwave-js/blob/master/packages/config/config/devices/0x011a/zwn-rsm2.json
https://github.com/zwave-js/zwavejs2mqtt/discussions/985#discussioncomment-568172

0x011a:0x0111:0x0606 is called ZWN-RSM2-PLUS
Association groups 2/3 (Switch Binary Report EP1 / 2) need to be auto-assigned

If any more logs or info are needed from me, I'm happy to provide more details.


chore: bdd-spring-1574945509 to 0.0.1

chore: Promote bdd-spring-1574945509 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add a check to see if a spin item is in the way of the installer succeeding (before we even download the spin tarball)

Signed-off-by: tpmccallum<EMAIL_ADDRESS>I was finally able to reproduce an error that has been flagged in an issue. This update closes https://github.com/fermyon/developer/issues/748 by adding a new step in the installer, which checks to see if a spin item is in the way of the installer succeeding (before the user’s end expends any resources on downloading the tarball).

If any items exist (that should not be there), it lists all of them in a group once, so the user knows what to do (entirely) before trying the installer again.
The exit is conditional (based on if one or more items (that should not be there).

New logic, check only for spin directory.


add occi-infra.xml to malmoz.lizenn (or somewhere accessible online)

In order to illustrate the possibilities of http://occinterface.herokuapp.com/, I need to access to occi-infra.xml. Indeed, the default schema with author, blog, article does not let me show one of the main feature of occinterface : navigate through links between resources. I also already have samples to populate occi-infra.xml with a simple click on the application.
I also tried to deploy erocci to heroku on my own, but it doesn't work, even with the https://github.com/erocci/heroku-buildpack-erlang that I saw you modified to make it work, but unfortunately it does not work.

heroku-buildpack-erlang was a unfinished attempt.
I've heard of many erlang apps being deployed on heroku but have not done it myself :/


chore: lock asset icon to pre-lfs

#182  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @AngelOnFira and the rest of your teammates on  Graphite


Godot segfaults silently if Opengl 2.1 support is missing

(gdb) backtrace
#0  0x0000000000000000 in ?? ()
#1  0x0000000000514154 in RasterizerGLES2::init (this=0x7ffff2878040) at drivers/gles2/rasterizer_gles2.cpp:7666
#2  0x0000000000f82e23 in VisualServerRaster::init (this=0x7ffff2856040) at servers/visual/visual_server_raster.cpp:5624
#3  0x0000000000f30a30 in VisualServerWrapMT::init (this=0x7ffff2815040) at servers/visual/visual_server_wrap_mt.cpp:152
#4  0x00000000004080a7 in OS_X11::initialize (this=0x7fffffffdeb0, p_desired=..., p_video_driver=0, p_audio_driver=0) at platform/x11/os_x11.cpp:306
#5  0x0000000000410b1b in Main::setup2 () at main/main.cpp:706
#6  0x000000000040ff64 in Main::setup (execpath=0x7fffffffe668 "/data/Proggen/git/config/scripts/godot", argc=1, argv=0x7fffffffe370, p_second_phase=true)
    at main/main.cpp:661
#7  0x00000000004064c8 in main (argc=2, argv=0x7fffffffe368) at platform/x11/godot_x11.cpp:36

Running on an old intel graphics chip, should print a little error message along the lines of "need opengl2.1 support to run" before segfaulting.

related to: https://github.com/okamstudio/godot/issues/1283

If this still valid in the current master branch? If yes, a check for the OpenGL version should probably be added to provide a meaningful error message and close Godot without segfaulting.

Unfortunately I no longer have the hardware that was causing the problems in my possession.

Related to #1162.

Closing as a "won't fix" bug as there is nothing we can do to fix this issue. On the other hand #1162 proposes to catch the error before a segfault and to display a friendly error message, which should make this kind of errors easier to understand for the user.


CNV-42087: Improve sysprep section when the answer file is added

📝 Description
🎥 Demo
Before:

After:

/hold
Until #1998 is merged

/retest

/lgtm

/unhold

/cherry-pick release-4.16


FieldWithButtons space issue

Fixes #114

@balizok -- does this fix your issue?

Yes that's all good, thanks !


Multiple email notifications for cert expiry

I woke up to 3 duplicate certification expiry email notifications from prod today:

It looks like we still need to do more work on this.  It looks like they all came at the same time.

I am assuming we are still creating unique queues, which is why we are still getting dupe emails. I could start to look into this later today.

It could also be due to running multiple instances in prod (i.e., we have 2 instances of our server running, both using the same Redis backend).  But having 3 of them is interesting, since that means it's potentially more than 1 thing.


Easy address/port changing for example code

Some systems will already have something listening on 8000. For these systems, it would be nice to have an easy way to set the server port for the example.
runserver <IP_ADDRESS>:port
sets the server listening port, but the script still assumes port 8000

This was fixed some time ago. Now both server and cli scripts have parameters for setting the url and port of the server


When perform backup, the log won't print immediately

When perform backup, the log won't print immediately
I have a very large database on mongodb about 10 GB. When I perform backup, it takes a long time and the log doesn't print immediately. I cant see any thing before the process finished.
I see run utilities method uses Open4. popen4. Here  https://github.com/backup/backup/blob/master/lib/backup/utilities.rb#L175 . May be this is the issue.

Operating system: Ubuntu Server 14.04.5
Ruby version: 2.2.3
Tools or services used by backup: mongodump

Correct. Backup only prints when a command has completed. We can't really change that right now.  Sorry about that


ARIA-437: ARIA does not support some of the combinations for requirement declarations (at the node type) and some for requirement assignments (at the node template)

Thanks for the comments. Let me incorporate the comments and have a separate pull request later.

Were we going to discuss the PR this morning?
BTW I see you withdrew the earlier one. When are you planning to push the
updated?
--Tom
On Thu, Feb 22, 2018 at 1:29 AM, VenkatesanVenugopal <
<EMAIL_ADDRESS>wrote:

Thanks for the comments. Let me incorporate the comments and have a
separate pull request later.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-ariatosca/pull/223#issuecomment-367580689,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae9t9eqO--hc2NHxUnN_tPdu3Axx3Wpjks5tXQlDgaJpZM4RXwx_
.


Get the movie cards done. Need some css styling. Next step: fix the r…

…untime error. Also saved movie data in local storage for future use.

I will start CSS tomorrow during class time
On Wed, Nov 30, 2022 at 10:35 PM RicenUdonLover @.***>
wrote:

@RicenUdonLover https://github.com/RicenUdonLover requested your review
on: #6 https://github.com/matt530bailey/renameLater/pull/6 Get the
movie cards done. Need some css styling. Next step: fix the r….
—
Reply to this email directly, view it on GitHub
https://github.com/matt530bailey/renameLater/pull/6#event-7928645222,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3O3VH5CK6LMLJBXDXWPDITWLBBMLANCNFSM6AAAAAASQNTBUI
.
You are receiving this because your review was requested.Message ID:
@.***>


multiple .das files plots wrong track as 'most recent'

If there are two new .das files to run (e.g., it wasn't uploaded the day before or the processing computer was off over the weekend, etc) they are processed in reverse order of when they were uploaded to Google Drive (so most recent is processed first). That tricks the map into thinking the 'most recent' track is the 'oldest' uploaded 'new' .das file.
Can figure out how to sort the newIdx das files by the date at the end of their name and process in correct order.

sorted by name column
Tested with full re-run of everything and correct final leg was bright pink.
Then manually 'removed' the 7/27 and 7/28 from all dasList and all compiled data frames and re-ran. It DID process 7/27 first!


Convert to scripts & include Makefile

Scripts to include

[x] eda plots
[x] data cleaning & feature engineering
[x] transformations &  data splitting
[x] models
[x] hyperparameter optimization
[x] rfecv model
[x] feature importances
[x] model evaluation (training & cv)
[x] shap values

Thanks Nicole for breaking down the report into scripts!


cosmic-randr: 1.0.0-alpha.2 -> 1.0.0-alpha.3

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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/)
24.11 Release Notes (or backporting 23.11 and 24.05 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354776

x86_64-linux

:white_check_mark: 2 packages built:

cosmic-randr
cosmic-settings


Infinite death loop

So i accidentally removed both my arms, so i had to kill myself to get them back. I did /kill and when i respawn i die instantly with the message "Idiot101300's body took revenge". this happens every time i respawn from the previous death creating a frustrating infinite loop.
is this supposed to happen?

Most likely not, you're probably going to have to reset your .dat file or remove the mod, load the world then reinstall.
To reset your .dat file you're going to have to create another world, go to world's said save and copy the .dat file into your current world (MAKE A BACKUP OF THE OLD .dat FILE). The .dat file stores all of the player information, so the world will be fine, but anything in your inventory or ender chests will be gone. Then again your items dropped on the ground when you died so that shouldn't be a problem.

Damn okay. It's not that important but thanks for the reply


Add allowed values for list options

Extend the current behavior with respect to option.type to option.element.type as well. This e.g. gets the allowed values for list options, analogous to other options. The only current affected option is lib: This change keeps its allowed values up to date.

:+1: Makes sense, and no rush. Is this mergeable with the latest revision: Restore the lib.md and hide the lib allowed values? What's left is the refactoring, without actually affecting any current options.

It is 👍🏻


runtime detection for avaliable libtcti-tabrmd.so

"libtcti-xxx.so" may be available on current system which builds "libtpm2-pk11", but not available on many new systems that uses "/dev/tpmrm0" as kernel-space TPM resource manager. So currently I have to build two "libtpm2-pk11.so"  RPM packages, one of which compiled with TCTI_TABRMD_ENABLED while the other one not.
Linking against "libtcti-tabrmd.so" at compile-time is simpler for an demo project, but less flexible for final products.
Maybe it's better to implement a probe function "tcti_probe()" so that we may load "libtcti-tabrmd.so" as an dynamic-linked lib at run-time.

Requiring libtcti-tabrmd.so to be available at runtime doesn't seem to me as a very big barrier. It isn't even required that the tpm2-abrmd is running.


Link problems

Three of these do not link to any page. It should link to some page, right?

Thank you for your questions, I apologise for the delay in replying.
The deployed site doesn't have a page that you mentioned, now we finish all of that page it will be available by Friday.

I've implemented in PR above. Please wait for deployment site. Thank to y'all 👍


How to change the response data on paho_iot_hub_methods_sample on azure SDK to be variable data?

Hello
I am working on Azure IOT samples and on example paho_iot_hub_methods_sample  and I want to make this variable
static az_span const method_ping_response = AZ_SPAN_LITERAL_FROM_STR("{"response": "pong"}");
can take any data from unsigned of char to able to display on azure CLI request as the response should be like this AZ_SPAN_LITERAL_FROM_STR("{"response": "pong"}"); but I want to put data array of unsigned char instead of pong
so can anyone help me to make this?
Thanks,

This issue seems to be about paho samples, and places like these which use static az_span values based on string literals:
https://github.com/Azure/azure-sdk-for-c/blob/9f5a6334863ebbf214c6e2fbd5d6e3fce52fe0de/sdk/samples/iot/paho_iot_hub_methods_sample.c#L33
You could use other macros or functions to create the span you need from an array rather than a string literal. For example, you have:
AZ_SPAN_FROM_BUFFER()
OR
az_span_create_from_str()
https://github.com/Azure/azure-sdk-for-c/blob/9f5a6334863ebbf214c6e2fbd5d6e3fce52fe0de/sdk/inc/azure/core/az_span.h#L136-L161
@yosefgouda2020 Is your char array null terminated? Is it actually char*, or can it be a uint8_t*?
@danewalton, @momuno Is this something we should adjust in the sample?

@ahsonkhan Thank you for your replay and my data will be something like this  unsigned char ARR[4] = { 0x01, 0x02, 0x03, 0x04 } and this data can be modified during the run time and to get the right span from running CLI az iot hub invoke-device-method  the response must be like this
static az_span const method_ping_response = AZ_SPAN_LITERAL_FROM_STR("{\"response\": \"pong\"}");
so how make my variable unsigned char ARR[4] works with static az_span const method_ping_response with same shape of response.

Closing this for inactivity. Please let us know if you would like it reopened.


Custom App Service Name detection when adding new services

These changes significantly enhance the configurational flexibility of Laravel Sail's Docker Compose setup, particularly in environments with distinct service naming requirements.
Custom App Service Name Support:
A mechanism is introduced to detect the application service (APP_SERVICE). The code initially attempts to retrieve the service name from Laravel's default environment file. In the absence of a custom service name, the default laravel.test is retained. When adding a new service or devcontainer, the warning message has been enhanced. It now indicates the customized application service name (if applicable), ensuring clarity and context for integrated system scenarios.

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


BaseLoader now also used by loadresources.

Fixes #76
Moved baseloader to utils/ folder.

ping @JackMorganNZ


Finalized list of form requirements for application submission

{
  "user_name" : "Name of user",
  "user_id" : "ADEPT internal id",
  "user_email" : "User email address (auto popuplated?)",
  "app_name": "Name of application",
  "app_description" : "Short summary of the goal(s) of the application",

  "docker_image" : "...",
  "docker_image_checksum" : "...",

  "resource_cpu" : "Required number of CPUs (default: 1)",
  "resource_memory" : "Required amount of memory (default: 4GB)",

   "github_repo" : "Link to github repo", -- Optional
  "resource_runtime" : "Estimated/expected runtime" -- Optional
}

Looking more closely at the list provided by @iross I feel that there is a lot missing here that should be included. Particularly when comparing it to the instructions provided in the xDD docker recipe readme. Almost none of the questions those instructions ask are answered by the form.

The first step in the process is to communicate the application behavior to the xDD team.
What does the application do?
What data product(s) are needed for an input?
How is the target corpus defined? (keyword, set of keywords, defined list of DOIs, specific journal, etc.)
What are the approximate resources required for the application?
Does the application require access to all desired data at once, or can it be split into smaller datasets?

Here are my suggestions for improvements.

The Applications description text-box displays as very tiny. I think the textbox should be much larger and possibly extendable to encourage users (or at least let them know that it is permissable) to write application descriptions that are longer than a few words.
Optional vs required fields should be visually flagged in some way.
The *Resources Required to Execute field should be changed to Estimated Computing Requirements to specify that that the user doesn't need to know exactly what will be required.
There should be a field for users to specify the default ADEPT saved-set that should be paired with the application.

@iross please evaluate these suggestions and let me know right away if you agree.

Add output_link field to database table user_app_instance and also make sure said field displays in application.

added output_link to the result field and added test set to register application form


GCS Support, annotated tag, delete rework

Add support for GCS in both from_bucket and from laptop
Add option when calling dataset.add() to specify annotated=False to ignore this in versioning for the FE until it is annotated
Rework updating attributes based on instance_id and add a function to annotate an instance once annotated

Please review in the morning @kozlov721 . I'll try to review this tomorrow as well @conorsim .


Enhance KaTeX

There are two modifications:

Use .Param as switch of KaTeX to enable KaTeX for whole site or for single post. Sample configuration is available in README.md.
Enable rendering KaTeX in code block.

Hi @ShivaHuang, thanks for the PR.

The per-page switch is nice.
Could you explain why this is needed?

<script>for (element of document.getElementsByClassName("language-katex")) { renderMathInElement(element); }</script>

I thought all katex expressions inside document.body would be auto detected.

Yeah, I mean  block.
Actually, I was not sure which is a better behavior. But since this behavior is designed by katex, I think following upstream is more reasonable.

I changed the description of the param you added. Thanks for the PR!


Model training

I see that the label_nc in the train_pose.py is 25. When the model is trained, are there 21 key points of the hand?

Hi, @jasonwongw, thanks for your interest! We don't use the hand keypoints because they are not very accurate.

Thanks for your reply.
In video frames, it is difficult to extract hand keys.


fix: deployment succesfull.

Althought the project is now deployed, we still need to fix the functionality and ui as a lot of features broke just trying to deploy the project

Deploys on my end :-
https://luminedeploy.vercel.app/

@Nexusrex18 Pushing to prod.


timeline on completion of libtaxii

I'm interested in using cti-taxii-client. Is it possible to estimate when the majority of the implementation will be completed?
Thanks!

Hi, @vinayreddy123, I'm hoping we get basic functionality for all of the TAXII endpoints completed in the next week or so. Some of the more advanced features (like pagination) will likely take longer, but should still be in the next few weeks.


pypodman port: -l/--last is not implemented and "pypodman port $ctn $port" does not work well

Is this a BUG REPORT or FEATURE REQUEST?:
kind bug
Description
As the title says.

Ones work fine:

pypodman port -a/--all
pypodman port $ctn

Which not work:

pypodman port -l/--last
pypodman port $ctn $port

Steps to reproduce the issue:

pypodman port -l

pypodman port test-port 80

pypodman port test-port 80/tcp

Describe the results you received:
1.
[root@localhost ~]# ~/.local/bin/pypodman -l root --host <IP_ADDRESS> port -l
2018-12-11 16:29:39 CST | ERROR    | pypodman: unrecognized arguments: -l
2018-12-11 16:29:39 CST | ERROR    | Try 'pypodman --help' for more information.

[root@localhost ~]# ~/.local/bin/pypodman -l root --host <IP_ADDRESS> port test-port 80
Container "80" not found
8111ad77c3551c8672a9dd7906787e4bf6eef530f9ae6aab134063ff50d623d7
[{'host_port': '80', 'host_ip': '', 'protocol': 'tcp', 'container_port': '80'}]

[root@localhost ~]# ~/.local/bin/pypodman -l root --host <IP_ADDRESS> port test-port 80/tcp
Container "80/tcp" not found
8111ad77c3551c8672a9dd7906787e4bf6eef530f9ae6aab134063ff50d623d7
[{'host_port': '80', 'host_ip': '', 'protocol': 'tcp', 'container_port': '80'}]

We don't want to support --last for remote API, since it opens up the chance of race conditions to too large.

@rhatdan Yes sir, it makes sense.
I think pypodman port $ctn $port should be implemented, it seems no other risks included.


Bar freezes under certain circumstances

According to a video by Brodie Robertson, there is an issue that can freeze up Lemonbar and/or succade when mouse actions (in quick succession) are being used on a block. I haven't been able to reproduce this bug, neither do I know what causes it. More information is required at this point, but we should definitely try and get to the bottom of this.

I suspect the issue lies within a bug in libkita, which seems to be fixed now. Maybe this fixes this issue as well, but more tests (especially by users who ran into the issue before) have to be done.

User XDream8 on YouTube reports that the version with the above mentioned fix does solve the freezing issue for them. I'll therefore mark this as solved. Can always re-open if someone sees this still / again.


Support publishing of javadocs to gh-pages (in googleapis) as part of grpc package generation

This depends on https://github.com/googleapis/artman/issues/55 .

Added a target named updateDocsWithCurrentVersion to the generated build.gradle of each grpc package in https://github.com/googleapis/packman/pull/158 ; as of now, this still needs to be invoked manually.

This is already done: https://github.com/googleapis/toolkit/blob/master/src/main/resources/com/google/api/codegen/metadatagen/java/grpc/package.snip#L152


Fix --classpathEntry CLI option name in README.md

thanks!
and looks like something's wrong with the ci windows runner..


istio contribfest 2024

Please provide a description of this PR:

Hi @jzhn. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@jzhn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

integ-pilot_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

integ-pilot_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot

unit-tests_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

integ-pilot_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot

unit-tests_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests

integ-pilot-istiodremote_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-istiodremote

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

integ-pilot_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot

unit-tests_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests

integ-pilot-istiodremote_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jzhn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test release-notes

lint_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test lint

integ-basic-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-basic-arm64

integ-operator-controller_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-operator-controller

integ-distroless_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-distroless

unit-tests-arm64_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests-arm64

integ-cni_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-cni

integ-pilot_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot

unit-tests_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test unit-tests

integ-pilot-istiodremote_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-istiodremote

integ-pilot-multicluster_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-multicluster

integ-telemetry-mc_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-telemetry-mc

integ-telemetry_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-telemetry

integ-security_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-security

integ-ambient_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-ambient

integ-pilot-istiodremote-mc_istio_release-1.23
dcbae138dd1bdc344e0227e56f043e1ab945d458
link
true
/test integ-pilot-istiodremote-mc

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

what is this for?

what is this for?

this is part of KubeCon NA 2024 istio contribfest event, to submit a minor patch to istio 1.23 as a practice for new potential contributors. Since the event is over, I'll just close it.

Thank you for coming to our contribfest! Let me know if I can help you get started contributing to Istio!


Tie up important loose-end from ye olde 12am March 26 Sheet-Refactor

When refactoring the Google Sheet on the night of 3/25-26, we made the address-of-record the "Final Address" column.
The entries in that column were formerly Column ~"N",  and were auto-generated from API calls.
Prior to the refactor, the addresses-of-record were those located in the "Street address for dropoffs" field. Those should be copied into to the Final Address Field for rows prior to the refactor.
This sounds trivial, but some rows, mostly moderated-off, would lose most meaning if the copy were performed as a bulk action.  @susanashlock  is probably the right person to make the copy, if not @4kbt.

This will involve rows 3-1822.
Will need to skim through and make sure all addresses look good before copying them into 'Final Address' column.
Would also be good to pause scripts before doing this, just in case.

At this point, we're never going to do this.


Licenses for imported photos

As an importer from Flickr (or other sources) I want to set the correct license for each photo.

Part of https://github.com/edent/openbenches/blob/master/www/flickr.php


[Bug] Use a new api key to .env.local but still load old key?

Bug Description
I upgrade into the newest version, got some issue
I change the OPENAI_API_KEY into new one (the key work in another client well),
but after I yarn install && yarn start, It seems to be using an old KEY with no balance.
How can I refresh the key?
Steps to Reproduce
1.Change API-key
Expected Behavior
Use new key successfully
Screenshots
No response
Deployment Method

[ ] Docker
[ ] Vercel
[X] Server

Desktop OS
No response
Desktop Browser
No response
Desktop Browser Version
No response
Smartphone Device
No response
Smartphone OS
No response
Smartphone Browser
No response
Smartphone Browser Version
No response
Additional Logs
{
  "error": {
    "message": "Your account balance is less than 0.8, which is not enough to use the gpt-4 model. Please visit https://peiqishop.me/buy/18 to recharge.",
    "type": "chatanywhere_error",
    "param": null,
    "code": "403 FORBIDDEN"
  }
}

This seems to have nothing to do with the project code. Please try starting the service again or check whether your api key is available.


type guards strangeness

TypeScript Version:
1.8.0
Code
const enum AsNonBlank {}
export function isNonBlank(value: string) : value is string & AsNonBlank {
    return !/^\s*$/g.test(value);
}
let value: string;
if (isNonBlank(value)) {
    doThis(value); // expected value to be string & AsNonBlank, actual: string
} else {
    doThat(value);
}
function doThis(value: string & AsNonBlank): void {
}
function doThat(value: string) : void {
}

Expected behavior:
value should either be string & AsNonBlank
or there must be a message saying that the type guard is invalid or something
Actual behavior:
value is a string

@aleksey-bykov I'm also finding that user-defined type guards often don't work the way I intuitively expect. Your example makes intuitive sense to me and I would have expected it to work.
However, since you haven't started with a union type, I suspect you are working outside the bounds of what tsc can currently do with type guards. I got your example to work by changing the declaration of value to:
let value: string | (string & AsNonBlank);

This seems to satisfy the compiler, and the narrowing happens as expected in both the if and else branches.

Interestingly, the following version of your code does work as you would expect without needing a union type:
const enum AsUnaryFunc {}
export function isUnaryFunc(value: Function) : value is Function & AsUnaryFunc {
    return value.length === 1;
}
let value: Function;
if (isUnaryFunc(value)) {
    doThis(value); // expected value to be Function & AsUnaryFunc, AND IT IS
} else {
    doThat(value);
}
function doThis(value: Function & AsUnaryFunc): void {
}
function doThat(value: Function) : void {
}

It's the same code as yours, just with Function/AsUnaryFunction instead of string/AsNonBlank.

@yortus thanks!

@yortus just checked with the union, it doesn't work either
const enum AsNonBlank {}
export function isNonBlank(value: string | string & AsNonBlank) : value is string & AsNonBlank {
    return !/^\s*$/g.test(value);
}
let value: string;
if (isNonBlank(value)) {
    doThis(value); // expected value to be string & AsNonBlank, actual is *STILL* a string
} else {
    doThat(value);
}
function doThis(value: string & AsNonBlank): void {
}
function doThat(value: string) : void {
}

Sorry I wasn't clear - this one works for me:
const enum AsNonBlank {}
export function isNonBlank(value: string) : value is string & AsNonBlank {
    return !/^\s*$/g.test(value);
}
let value: string | (string & AsNonBlank);    // <-- union here
if (isNonBlank(value)) {
    doThis(value); // expected value to be string & AsNonBlank
} else {
    doThat(value);
}
function doThis(value: string & AsNonBlank): void {
}
function doThat(value: string) : void {
}

Thanks! That's a great help!


⚠ Bofrost.nl has degraded performance

In 27b05f5, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 1372 ms

Resolved: Bofrost.nl performance has improved in 32c5a47.


Preview/Streaming is rotated upside down on Nexus 6P

I have found that specifically on Nexus 6P camera is rotated upside down for some reason.

In portrait or lanscape?
Front or back camera?
Which view are you using? SurfaceView, TextureView, LightOpenGlView or OpenGlView?

OpenGlView, front and back camera, portrait/landscape, livestream/preview

If this is only with nexus 6P you can do it in onCreate method:
if (is6p) {
    openGlView.setCameraFlip(false, true);
}

I would like to add that with the Nexus 5X we experience the same behavior. As far as I have been able to tell, this is in the preview only, using a SurfaceView.

Try use openglview with camera1 and camera2 and use setCameraFlip. Other way could be change rotate in prepareVideo method only with nexus 5x and with camera2.
I had a nexus 5x years ago and I know that camera is rotated for some reason(I think this is a hardware problem). Unfortunately I haven't this device anymore so I can't find a valid solution to work with all devices (Maybe it is not possible with surfaceview).
If the problem persist the only way is develop a method to rotate only preview with openglview and lightopenglview.

Thanks for the quick reply. I followed your advice and changed my standard surface view to the OpenGLView. I then check for the model type and apply the vertical flip if necessary. Am I correct in that this is necessary? Or should it work out of the box with the OpenGL View. As a note, I am using RtmpCamera1 for compatibility reasons.

Also, I don't know how much the emulator differs. But I use a 5X image in the emulator and the preview there is fine. So probably hardware issue?


pkg_resources: Runtime fixes to make typing annotations work

Summary of changes
Should fix the last errors in #4246. These are all actual code changes, please review carefully.

Pull Request Checklist

[ ] Changes have tests
[x] News fragment added in newsfragments/.
(See documentation for details)

Thank you very much @Avasam.


e2e: Add additional check to verify injector and controller readiness

There's been some cases where injector was not ready after osm install
in some very specific situations and environments.
To avoid and ensuring it's not a situational timing issue or a helm --wait
related problem (see #3665), this commit adds an additional check to make
sure osm-controller and osm-injector apps are marked as ready by
kubernetes before proceeding.
Signed-off-by: Eduard Serra<EMAIL_ADDRESS>Affected area:

Functional Area

Tests
[x]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project?

Did you notify the maintainers and provide attribution?
no

Is this a breaking change?
no

Codecov Report

Merging #3696 (6a97d53) into main (4322766) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #3696      +/-   ##
==========================================
+ Coverage   67.46%   67.48%   +0.02%
==========================================
  Files         181      181
  Lines        8772     8772
==========================================
+ Hits         5918     5920       +2
+ Misses       2821     2819       -2
  Partials       33       33

Flag
Coverage Δ

unittests
67.48% <ø> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/k8s/announcement_handlers.go
77.14% <0.00%> (+5.71%)
:arrow_up:

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 4322766...6a97d53. Read the comment docs.


exception.StackTrace is truncated when using Interceptors

@cshung wrote:
Consider the following code snippet
using Microsoft.Practices.Unity;
using Microsoft.Practices.Unity.InterceptionExtension;
using System;
using System.Collections.Generic;
namespace ConsoleApplication1
{
public interface IService
{
void work();
}
   public class Service : IService
   {
       public void work() { a(); }
       private void a() { b(); }
       private void b() { c(); }
       private void c() { throw new NotImplementedException { }; ; }
   }

   public class Interceptor : IInterceptionBehavior
   {
       public bool WillExecute { get { return true; } }
       public IEnumerable<Type> GetRequiredInterfaces() { return Type.EmptyTypes; }

       public IMethodReturn Invoke(IMethodInvocation input, GetNextInterceptionBehaviorDelegate getNext)
       {
           Console.WriteLine("Enter invoke");
           var result = getNext()(input, getNext);
           Console.WriteLine("Exit invoke");
           return result;
       }
   }

   public class UnityStackTraceMain
   {
       static void Main(string[] args)
       {
           var container = new UnityContainer { };
           container.AddNewExtension<Interception>();
           //container.AddNewExtension<AppContainerExtension>();

           container.RegisterType<IService, Service>(
               new ContainerControlledLifetimeManager(),
               new Interceptor<InterfaceInterceptor>(),
               new InterceptionBehavior<Interceptor>());

           try
           {
               container.Resolve<IService>().work();
           }
           catch (System.Exception ex)
           {
               Console.WriteLine(ex.ToString());
               Console.WriteLine(ex.InnerException);
           }

           Console.ReadLine();
       }
   }

}
We expect the ex.ToString() has the frames a(), b() and c(), but instead, it only have the dynamic generated function.
The root cause of this is because the exception is caught and thrown again. .NET does not preserve the stack trace in the exception in that case and is clearly documented.
The proper way to fix this is to wrap the exception. In order to make existing code work with the fix. I wrap the exception with the same type and same message, that should allow most code to work with it.
Since the interceptor code is not available in this repo, I created the pull request to fix this in CodePlex instead.
https://unity.codeplex.com/SourceControl/network/forks/cshung/unity/contribution/8726

This issue has been fixed in  63a2f1645749f81c942ad66ecfc7949996d5a949 and should be merged from experimental branch.


Test properties overwrite the project properties

Disabling the init-script of SHOGun by setting the property init.shogunInitEnabled to false in the file src/main/resources/META-INF/{{my-project}}-init.properties does not work. The reason is that a property with the same name is defined in the file src/main/resources/META-INF/shogun2-webapp-test-init.properties. You have to set the property init.shogunInitEnabled to false in this file to really disable the init-script.
I guess this is no wanted behaviour?

This is interesting and surely not wanted behaviour. I'll soon try to reproduce this. If you have a smart solution for this, just open a PR :wink:


Changed modPow to also handle negative exponents

Allow modPow to also handle negative exponents as a modular inverse followed by a normal modular exponentiation.
Right now modPow returns 0 which is unexpected behaviour since then (a^b mod n)*(a^(-b) mod n) mod n != 1. With the proposed changes modInv can throw an error if a has no multiplicative inverse but it is a more descriptive error than simply letting modPow return 0. Applying the changes results in the same behaviour as implementations of other languages such as Java's BigIntegers's modPow, PHP's bmodpow and python's pow.
For a reference on how to calculate negative exponents, see for example:
https://ipfs.io/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Modular_exponentiation.html
See also #184

Coverage increased (+0.02%) to 94.235% when pulling c0f80af2c2834d791100c834eedf44ea648e5b3d on pepijno:feature/modpow-negative-exponents into 2e0619371f90aedb8e44cb3ab983b18a5ac699aa on peterolson:master.

Coverage increased (+0.02%) to 94.235% when pulling c0f80af2c2834d791100c834eedf44ea648e5b3d on pepijno:feature/modpow-negative-exponents into 2e0619371f90aedb8e44cb3ab983b18a5ac699aa on peterolson:master.

Coverage increased (+0.02%) to 94.235% when pulling c0f80af2c2834d791100c834eedf44ea648e5b3d on pepijno:feature/modpow-negative-exponents into 2e0619371f90aedb8e44cb3ab983b18a5ac699aa on peterolson:master.

Thanks


[Gradle Plugin] Use relative strings for the rootFolder input property so as not to break cacheability

Closes #2293

Should we merge this too?


intro 4 confusion

in intro 4 there is a line that lead me to believe you could use greater than / smaller than operators on vec2's:
for example: a < b == lessThan(a, b)

'for example' and the style of writing leads me to believe that this is code

@puckey I am stuck at this point. If possible, help me solve an example! Thank you.


ignoring compile errors

This is Optional, but its drop horrible error when code is not lint free

I'm not sure we need this at this point. We included linting in order to show these errors.


(bug) main router blocking intermediately of upnp traffic.

Expected behavior
upnp traffic allowed though out network
Encountered Behaviour
dlna and upnp drops packets
Change Request
Enable upnp and dlna on main router and firewall so media center devices can transfer files from NAS more readily.

Status:

Router upgraded and traffic is allowed.


Language injection PyCharm warning message

Hello noEmbryo,
I would like to ask for your help.
Have you seen this kind of warnings?

Language injection only colors the words or it should also hint avaliable attributes (like in a kv file)?

Because I have no hint when I use language injection (# kv_start, # kv_end).
Thanks for your help!

Have you seen this kind of warnings?

Yes.
In YAML (the language that is been used for the injection) its not allowed to have duplicate keys.
If you click on the affected key, then on the red light-bulb, then navigate the drop-down menu using the arrow keys "Remove" > "Suppress for statement", a # noinspection YAMLDuplicatedKeys comment will be added to the beginning of the string and the warnings will disappear. ;o)
You can also add it manually yourself.

Language injection only colors the words or it should also hint available attributes (like in a kv file)?

Unfortunately, only coloring.. :o(

Thanks for your kind help.
So all the questions have been answered, I am going to close this issue.
Thanks again, I hope once we have some kind of support on behalf of JetBrains...


Setting jdownloader 2 for QNAP 253B

Hello,
I have a problem, so far the program works fine except I need to change the download folder which is on another hard drive of my QNAP 253B NAS.
The source folder
Hard disk 1/Container/output
I would like the files to be uploaded to the following folder
Hard disk 2 /Download
Could you tell me the steps or file to modify to achieve this?
Thank you for your help.

If you are using the Container Station to create the container, you just need to specify a "Shared Folder", where the host folder is /Download and the container folder is /output.

Sorry, I'm not sure to understand what you are trying to say.  Could you share the settings of your container ?
With what I said in my previous comment, the /output folder inside the container will be mapped to your "Hard disk N°2 / Download" folder.  This means that in JDownloader, everything downloaded to /output will end up in your "Hard disk N°2 / Download" folder.

Hello,
thank you for your answer, you are right with a screen it will be easier.
The /output must be in the second hard drive or I could access any folder. If this is not possible then only in the directory hard disk 2 /Shared Videos/Télécharger #

Ok, then in the Container Station, can you set a shared folder that maps /output to / Shared Videos/Télécharger ?
Here is a random example I found to show you what I'm talking about:

I can't modify anything, everything is blocked.

Same thing if the container is stopped ?
I'm not a QNAP user, but you may have to delete the container and re-create it.  Note that even /config doesn't seem to be mapped correctly.

unfortunately even by stopping the docker I cannot modify it. Is it possible to modify the configuration file?
I'm not a programming expert how can I recreate the docker? Is there a particular setting to do?

I understand, I had a permission problem. Which file should I modify to put the correct path?

can I modify the file in this location?

I put the config file just in case.
Thanks in advance

I finally succeeded, I had to delete the application and install it again. Thank you for taking the time to explain to me how to install it.
Anyway great job! Thanks again ;)

If you use the Container Station, you need to use the UI to manage the container.  The other way is to not use it and instead use shell and run docker commands yourself.
Happy to know that you were able to install it!


Introducing the Dutch language (Nederlands)

Introducing the Dutch language to NEOSCAN.
Because of the lack of a PR template i'll take another one from another repo.
What current issue(s) from Github does this address?
None
What problem does this PR solve?
The lack of a language
How did you solve this problem?
By translating to Dutch
How did you make sure your solution works?
Testing and running
Are there any special changes in the code that we should be aware of?
No
Is there anything else we should know?
No

[ ] Unit tests written?

So i'm not sure why Travis halted. Since i didnt edit any code on the gettext part.


Specify Expected Behavior for Username/Password Setting

As an Intune SE, we receive a lot of cases for this OMA-URI setting. Customers use it to create a local admin account for Intune enrolled devices but it always reports as failed.
By including this information, we can set the expectation and prevent future cases.

CC @JohanFreelancer9 for copy editing.

🤔 Oh well. I guess the readers will get (pun intended) the added message clearly enough. 😉


Fix direct link to GeoLite2 database

Ah, I didn't realise that "GeoLite2" is a different scheme than before. As a result, updating the link doesn't make any sense at all 😊
Related https://github.com/Miserlou/django-easy-timezones/issues/20


Just thought would be cool to add twin.macro features to this great template work

I've been looking for this type of feature to eventually make use of things like: Styled-components & TailwindCss simultaneously and make code more concise, uncluttered and more pleasing to an eye.
Here's an example: github.com/ben-rogerson/twin.examples/tree/master/next-stitches-typescript which i think i like most.
Many thanx for this awesome template work :)

Hi @NetLancer, thanks for the nice words :)
I can understand the appeal of twin macro, but I would probably be sticking with tailwindCSS for this project. There are under efforts current under way to reduce the boiler plate and make things less cluttered in terms of the overall code base and maintenance overhead.

Yeah, many thanks


spec with mocked api

test validate logic.

refactored for client capsuling.
not performed mocking io test this time.


WIP: Make bin directory AppImage ready

This at least skips the manual step of moving the files over into the directory. Not sure if the lovr.ico is supported.

Could these resource files exist directly inside src/resources instead of inside a subfolder?

I'm wondering if moving the appimage-related resources (and, later, potentially building the appimage itself) should be gated by the existing LOVR_BUILD_BUNDLE option.  It currently causes macOS to create a .app bundle instead of a lone executable, and maybe it would make sense for linux builds to use the same flow.

Could these resource files exist directly inside src/resources instead of inside a subfolder?

Sure if you prefer that, I put them to organise them and make it clear what they were used for.

I'm wondering if moving the appimage-related resources (and, later, potentially building the appimage itself) should be gated by the existing LOVR_BUILD_BUNDLE option. It currently causes macOS to create a .app bundle instead of a lone executable, and maybe it would make sense for linux builds to use the same flow.

That makes sense.

AppImage didn't like the lovr.ico file, so that's a no go.

Ok, I would still like to lift the files into the toplevel resources folder before merge.  I do think organizing the resources folder could be good but I'd prefer to tackle it in a holistic way.

It's great to finally have official Linux builds, thank you!

Thanks for merging :)


add quick start for dm deployment

What is changed, added or deleted? (Required)

add quick start for dm2.0 deployment
Which TiDB Data Migration (DM) version(s) do your changes apply to? (Required)

[ x ] master (the latest development version, including v2.0 changes for now)
[ ] v1.0 (TiDB DM 1.0 versions)

What is the related PR or file link(s)?

This PR is translated from:
Other reference link(s):

PR target branch is incorrect


Using Windows

Audit https://docs.celo.org/developer-guide/start/develop-on-windows

Add Using Mac

Add Using Remix

Need someone with windows to check


The definition could not be found “HAVE_SDIO”

The code needs to define HAVE_SDIO before I can enter the function, but I can't find the corresponding open position。

I found it. It is not a system-level macro-defined switch, just a debugging macro-defined switch.Defined in, boards/arm/stm32/stm32f4discovery/src/stm32f4discovery.h


Adding .bzh and .nc TLDs support, tested with bretagne.bzh and congres.nc

Hello,
I added support for .bzh and .nc TLDs.
These are not well famous, I hope it won't be a problem.

thanks


show inherited interfaces in tooltips

fixes https://github.com/Microsoft/visualfsharp/issues/2646
Before

After

Does this produce a valid fsi file? I think I'm right in saying that this same code is used to generate signature files by the compiler.

@saul @cloudRoutine Looking at the code fix it only applies to .NET (IL) type definitions, not to F# type definitions.  I'm not sure how this relates to the screen shot above though which are for F# type definitions - I think those are already shown?
@cloudRoutine I'm pretty sure you will want to avoid showing implemented interfaces if the interface type is internal to an assembly and is inaccessible from the point of use.  Some of the WinForms types are good examples of this IIRC.
Really, the NicePrint code should should not differ for "IL" and "F#" types, but instead should be written in a neutral way over any TyconRef.  This would make many things more orthogonal.
@saul Re signature files - as the fix is only for .NET (IL) type definitions we don't generate signature files for this.

@dsyme you're right that already worked for F# types, I should have posted
Before

After

But the cases I'm most interested in are ones like

Where the inherited interfaces are used to classify the service as this will be helpful while working on VFT

thank you for this change.
Kevin


added multi-word filter to recognize phrases

Something like this should work to look for full phrases to react to. How do I go about testing it locally to make sure it works?

Ok I tested this locally and it's working! I added "all hallows eve" as a phrase you can test

Thanks for this fix!