Add a plex playnext-equivalent command

Introduce a new command which acts the same as the /playnext command but for Plex. Alternatively, could add it as an optional parameter.

Has been completed in build v1.5 (https://github.com/ThatGuyJacobee/Elite-Music/commit/c14f8e24edf477db10f3090561afcbb52d0f7051). 🚀


Podman support

Problem Description
When trying to run podman on a host where I have started kubedock I get the following error
$ podman --remote --url "tcp://<IP_ADDRESS>:2475" run --name httpd -d -p 8080:8080 python python -m http.server 8080
Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM
Error: unable to connect to Podman socket: ping response was 404

And from kubedock logs

How to reproduce it
The issue can be reproduced on OpenShift Developer Sandbox (a Red Hat Developer account is required but it's free) using the following link: https://workspaces.openshift.com/f?url=https://github.com/l0rd/micronaut-sample
Video recording
https://user-images.githubusercontent.com/606959/232914999-8a171ca7-67ea-401c-83cf-a614d1f76c34.mp4

Initial work has been started where podman routes can be implemented here, adjacent to the docker api implementation.

Initial work has been started where podman routes can be implemented here, adjacent to the docker api implementation.

Amazing. I have been testing a simple podman run and the pod got created successfully. I have also tested with podman run -ti busybox and podman run -d -P httpd but the first didn't start and the second didn't expose any port (which is perfectly fine for an initial support).

Hi @joyrex2001
I noticed that 'podman generate kube' didn't work with kubedock. Kubedock logs showed 404, which suggests the feature is simply not implemented.
Since this GH issue is about general podman support, would it be OK to add "podman generate kube" requirement as part of  this ticket?

@agiertli yes, makes sense to track it in this ticket (sorry for the late reply).
I just released 0.13.0, which means for podman support:

added support for podman exec interactive mode
added support for podman restart
fixed podman cp error
fixed podman ps ports


Crash after stop recording

Device: ZenFone 3 Max
OS: Android M
03-20 17:24:52.634 11692        RequestThread-0  E  Timed out while waiting for request to complete.
03-20 17:24:52.635 11692       CaptureCollector  W  Preview buffers dropped for request: 1
03-20 17:24:52.635 11692      CameraDeviceState  E  Cannot receive result while in state: 0
03-20 17:24:52.635 11692                         E  Cannot receive result while in state: 0
03-20 17:24:52.642 11692                         E  Cannot receive result while in state: 0
03-20 17:24:52.674 11695                         I  Legacy camera service transitioning to state CAPTURING
03-20 17:24:52.675 11695                         E  Cannot call capture while in state: 0
03-20 17:24:52.682 11695                 Adreno  I  DequeueBuffer: dequeueBuffer failed
03-20 17:24:52.683 11695 CameraDeviceGLThread-0  E  Received exception on GL render thread:
03-20 17:24:52.683 11695                         E  java.lang.IllegalStateException: swapBuffers: EGL error: 0x300d
03-20 17:24:52.683 11695                         E      at android.hardware.camera2.legacy.SurfaceTextureRenderer.checkEglError(SurfaceTextureRenderer.java:530)
03-20 17:24:52.683 11695                         E      at android.hardware.camera2.legacy.SurfaceTextureRenderer.swapBuffers(SurfaceTextureRenderer.java:523)
03-20 17:24:52.683 11695                         E      at android.hardware.camera2.legacy.SurfaceTextureRenderer.drawIntoSurfaces(SurfaceTextureRenderer.java:727)
03-20 17:24:52.683 11695                         E      at android.hardware.camera2.legacy.GLThreadManager$1.handleMessage(GLThreadManager.java:105)
03-20 17:24:52.683 11695                         E      at android.os.Handler.dispatchMessage(Handler.java:98)
03-20 17:24:52.683 11695                         E      at android.os.Looper.loop(Looper.java:148)
03-20 17:24:52.683 11695                         E      at android.os.HandlerThread.run(HandlerThread.java:61)

Same as #37

We have made a pull request with this crash resolved.

I have the same problem on my custom device(API 21), i found solution at there https://stackoverflow.com/questions/27907090/android-camera-2-api/32621903#32621903,
it works for me.

plz reffer to issue #57

This sample has been migrated to a new location where we can accept Pull Requests (check README for more information).
As recommended by GitHub, we are closing all issues and pull requests now that this older repo will be archived.
If you still see this issue in the updated repo, please reopen the issue/PR there. Thank you!


[Ubuntu 20.04] PowerShell v7.1.0 is not available in the packages.microsoft.com repository

What is the status of updating powershell packages in the https://packages.microsoft.com/ubuntu/20.04/prod/pool/main/p/ repository for Ubuntu 20.04?

Likely as it was with the Microsoft store it is going through an additional cycle of internal review testing first but perhaps @SteveL-MSFT or @TravisEz13 can comment further

Duplicate of #12626

FYI @al-cheb  it is now available to install via that method as shown in the docs https://docs.microsoft.com/en-gb/powershell/scripting/install/installing-powershell-core-on-linux?view=powershell-7#installation-via-direct-download---ubuntu-2004


New Feature & Enhancement: Image to PDF Conversion and Custom File Merging Order

Proposal of two improvements to enhance the functionality of PDFFusion:

New Feature: Convert Image to PDF and Append to Merged Document

Implement the ability to convert image files (jpg, png, jpeg, gif, bmp) to PDF format
Include these converted image-PDFs in the final merged document
Ensure seamless integration with the existing PDF merging process

Enhancement: Enable File Merging in User-Specified Order

Modify the current merging mechanism to allow users to specify the order of files in the final merged PDF

These additions will significantly improve the versatility and user control of PDFFusion, making it a more comprehensive PDF manipulation tool.

Done!


Cleanup Pipeline

In the pipeline I want to differentiate between the concepts of a job and a trigger.
Job

Define exactly which secrets are required
Define exactly which inputs are required
No magic numbers
Execution of one concept with given secrets/inputs

Trigger

Define a trigger condition
Triggers one or multiple jobs
Defines only the necessary secrets/inputs for a job

Great work.


updated glue crawler tag attribute to match aws cloudformation doc

As described in this issue there is an attribute type mismatch that this patch resolves.

This issue impacts my work. Would love to see this merged.

Before I merge this change, can you show me what a working Tags looks like in the context of Glue Crawler? Outside of troposphere, how is the json/yaml different from normal Tags?

Similar situation to https://github.com/cloudtools/troposphere/issues/1045
What troposphere produces (Normal tags):
{
    "Resources": {
        "GenericCrawler": {
            "Properties": {
                "DatabaseName": "glueDatabase",
                "Role": "arn:aws:iam::12345:role/GlueRole",
                "Tags": [
                    {
                        "Key": "Environment",
                        "Value": "data"
                    },
                    {
                        "Key": "Project",
                        "Value": "tropospherefix"
                    }
                ],
                "Targets": {
                    "S3Targets": [
                        {
                            "Path": "myfancybucket"
                        }
                    ]
                }
            },
            "Type": "AWS::Glue::Crawler"
        }
    }
}

Give us the following error: "Property validation failure: [Value of property {/Tags} does not match type {Map}]"
What tropophere should produce:
{
    "Resources": {
        "GenericCrawler": {
            "Properties": {
                "DatabaseName": "glueDatabase",
                "Role": "arn:aws:iam::12345:role/GlueRole",
                "Tags": {"Environment" : "data", "Project" : "tropospherefix"},
                "Targets": {
                    "S3Targets": [
                        {
                            "Path": "myfancybucket"
                        }
                    ]
                }
            },
            "Type": "AWS::Glue::Crawler"
        }
    }
}

Thank you for the change and the details. Looks like there are Tags in other resources so I'll be fixing those up as well.

Grand, thanks!


MI user downloads "report" spreadsheet of metrics

Context
Trello 719
This PR provides an initial user-interface to download a "report" of management information. The download is in .xlsx format and is only available to users with the CAS2_MI role. It's exposed via the /reports url.
The report itself is an example placeholder report cas2-example-report.xlsx.
The purpose of this work is to implement the framework for providing downloadable spreadsheets to users.
Note that the authorisation control is implemented at the API. i.e. a user without the required role can navigate to /reports and attempt to "Download report". They will receive a 403 Forbidden response. In the future we may implement authorisation controls in the UI to prevent the /reports url from being accessed.
Screenshot

To do
This work is required for the ITHC to verify that the correct authorisation controls are in place (only users with the CAS2_MI role can download). The following are missing and will be added later as we implement the real reports:

integration tests
end-to-end tests in Playwright

Pre merge checklist

[ ] Are any changes required to the e2e tests?
[x] If you've added a new route, have you added a new -> Yes, done
[ ] Are there environment variables or other infrastructure configuration which needs to be included in this release?
[ ] Are there any data migrations required. Automatic or manual?
[x] Does this rely on changes being deployed to the CAS API? - Yes, we need to merge API PR 1255

LGTM, nice work 🙌

although that said, is it worth adding some integration tests at this point?

LGTM, nice work 🙌

although that said, is it worth adding some integration tests at this point?

Yes we ought to have integration and E2E tests but as I've said in the PR description, I'm proposing that we deliberately put that off as this work is urgently needed for the ITHC starting tomorrow...

LGTM, nice work 🙌

although that said, is it worth adding some integration tests at this point?

Yes we ought to have integration and E2E tests but as I've said in the PR description, I'm proposing that we deliberately put that off as this work is urgently needed for the ITHC starting tomorrow...

Oh, sorry! Missed that. Merge away 🙂


MiniGrid Empty Env

Hi, Minigrid environments are not in the envpool.list_all_envs(), I checked both with versions 0.8.4 and 0.8.2 whereas the documentation mentions support. How do i use these?

Any updates on this? I am trying to do the same now


mcuboot/samples/zephyr (make test-good-rsa) doesn't work

Describe the bug
Using mcuboot/samples/zephyr, overwrite test case can work fine as shown below, where slot0 is overwritten by slot1.  However, swap case(make test-good-rsa) doesn't work.
Could you let me know how I can debug it?
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=nucleo_f767zi (with flash partitions)
make
See error => No errors

Expected behavior
According to Makefile, expectation should be described below.
//# Test a good image, with a good upgrade, using RSA signatures.
//# flash_boot: Unable to find bootable image
//# flash_hello1: hello1 runs
//# flash_hello2: hello2 runs
//# reset: hello1 runs
Impact
Showstopper
Screenshots or console output
///  make test-overwrite  case (working) ////
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Swap type: none
[00:00:00.016,000]  mcuboot: Unable to find bootable image
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Swap type: none
[00:00:00.066,000]  mcuboot: Bootloader chainload address offset: 0x20000
[00:00:00.073,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-*
Hello World from hello1 on nucleo_f767zi!
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Swap type: test
[00:00:00.066,000]  mcuboot: Image upgrade secondary slot -> primary slot
[00:00:00.073,000]  mcuboot: Erasing the primary slot
[00:00:00.595,000]  mcuboot: Copying the secondary slot to the primary slot: 0x20000 bytes
[00:00:07.442,000]  mcuboot: Bootloader chainload address offset: 0x20000
[00:00:07.450,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-*
Hello World from hello2 on nucleo_f767zi!
/////////////////////////////////////////////////////////////////////////////////////////////////////////
///  make test-good-rsa  case (not working) ////
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.044,000]  mcuboot: Unable to find bootable image
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.095,000]  mcuboot: Bootloader chainload address offset: 0x20000
[00:00:00.102,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-*
Hello World from hello1 on nucleo_f767zi!
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: test
[00:00:00.109,000]  os: ***** BUS FAULT *****
[00:00:00.115,000]  os:   Precise data bus error
[00:00:00.120,000]  os:   BFAR Address: 0x20080004
[00:00:00.126,000]  os: r0/a1:  0x20080000  r1/a2:  0x0000bc71  r2/a3:  0x00003384
[00:00:00.135,000]  os: r3/a4:  0xffffc537 r12/ip:  0x00040000 r14/lr:  0x080007d3
[00:00:00.144,000]  os:  xpsr:  0x81000000
[00:00:00.149,000]  os: Faulting instruction address (r15/pc): 0x08005d5e
[00:00:00.157,000]  os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.165,000]  os: Current thread: 0x20022b74 (unknown)
[00:00:00.172,000]  os: Halting system
/////////////////////////////////////////////////////////////////////////////////////////////////////////
/// flash partition definition in zephyr/boards/arm/nucleo_f767zi/nucleo_f767zi.dts ///////
&flash0 {
/*
* For more information, see:
* http://docs.zephyrproject.org/devices/dts/flash_partitions.html
*/
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
	/* 64KB for bootloader */
	boot_partition: partition@0 {
		label = "mcuboot";
		reg = <0x00000000 0x00010000>;
		read-only;
	};

	/* storage: 64KB for settings */
	storage_partition: partition@10000 {
		label = "storage";
		reg = <0x00010000 0x00010000>;
	};

	/* application image slot: 256KB */
	slot0_partition: partition@20000 {
		label = "image-0";
		reg = <0x00020000 0x00040000>;
	};

	/* backup slot: 256KB */
	slot1_partition: partition@60000 {
		label = "image-1";
		reg = <0x00060000 0x00040000>;
	};

	/* swap slot: 256KB */
	scratch_partition: partition@a0000 {
		label = "image-scratch";
		reg = <0x000a0000 0x00040000>;
	};

};

Environment (please complete the following information):

OS: (Ubuntu 19.10 on VirtualBox 6.0.16 )
Toolchain (Zephyr SDK 0.10.3,  Zephyr 2.1.99, gcc-arm-none-eabi-9-2019-q4-major)

Additional context
Add any other context about the problem here.
Best regards,
Koji

Using mcuboot/samples/zephyr,

Are you using Zephyr's built-in MCUBoot or upstream MCUBoot?

Sorry, but please let me know what the difference is.

Since I don't change released files other than dts file, it should be followed by Makefile as shown below.  So mcuboot files are used at mcuboot/boot/zephyr
SOURCE_DIRECTORY := $(CURDIR)
boot: check
@rm -f mcuboot.bin
(mkdir -p $(BUILD_DIR_BOOT) &&
cd $(BUILD_DIR_BOOT) &&
cmake -DOVERLAY_CONFIG=$(BOOTLOADER_OVERLAY_CONFIG)
-G"Ninja"
-DBOARD=$(BOARD)
$(SOURCE_DIRECTORY)/../../boot/zephyr &&
ninja)
cp $(BUILD_DIR_BOOT)/zephyr/zephyr.bin mcuboot.bin

cc @utzig

@kkiyota Could you please paste your .config here? I remember there used to be issues with the STM32 flash driver when MULTITHREADING is disabled....

Here is mcuboot/samples/zephyr/build/nucleo_f767zi/mcuboot/zephyr/.config
If you need anything else, please let me know.
//////////////////////////////////////////////////////////////

MCUboot-specific configuration options

CONFIG_MCUBOOT=y
CONFIG_BOOT_USE_MBEDTLS=y

MCUBoot settings

CONFIG_BOOT_SIGNATURE_TYPE_RSA=y
CONFIG_BOOT_SIGNATURE_TYPE_RSA_LEN=2048
CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256 is not set
CONFIG_BOOT_SIGNATURE_TYPE_ED25519 is not set
CONFIG_BOOT_SIGNATURE_KEY_FILE="root-rsa-2048.pem"
CONFIG_MBEDTLS_CFG_FILE="mcuboot-mbedtls-cfg.h"
CONFIG_BOOT_VALIDATE_SLOT0=y
CONFIG_BOOT_UPGRADE_ONLY is not set
CONFIG_BOOT_SWAP_USING_MOVE is not set
CONFIG_BOOT_BOOTSTRAP is not set
CONFIG_BOOT_SWAP_SAVE_ENCTLV is not set
CONFIG_BOOT_ENCRYPT_RSA is not set
CONFIG_BOOT_ENCRYPT_EC256 is not set
CONFIG_BOOT_MAX_IMG_SECTORS=128
CONFIG_BOOT_ERASE_PROGRESSIVELY is not set
CONFIG_BOOT_WAIT_FOR_USB_DFU is not set
CONFIG_ZEPHYR_TRY_MASS_ERASE=y
CONFIG_BOOT_USE_BENCH is not set
CONFIG_MCUBOOT_LOG_LEVEL_OFF is not set
CONFIG_MCUBOOT_LOG_LEVEL_ERR is not set
CONFIG_MCUBOOT_LOG_LEVEL_WRN is not set
CONFIG_MCUBOOT_LOG_LEVEL_INF=y
CONFIG_MCUBOOT_LOG_LEVEL_DBG is not set
CONFIG_MCUBOOT_LOG_LEVEL=3
CONFIG_MCUBOOT_SERIAL is not set
end of MCUBoot settings
CONFIG_MCUBOOT_DEVICE_SETTINGS=y

Zephyr configuration options

CONFIG_MULTITHREADING=y
CONFIG_UPDATEABLE_IMAGE_NUMBER=1

Modules

Optional modules. Make sure they're installed, via the project manifest.

CONFIG_CANOPENNODE is not set
CONFIG_CIVETWEB is not set
CONFIG_LIBMETAL is not set
CONFIG_HAS_SEMTECH_LORAMAC is not set
CONFIG_HAS_SEMTECH_RADIO_DRIVERS is not set
CONFIG_MBEDTLS=y
CONFIG_MBEDTLS_BUILTIN=y
CONFIG_MBEDTLS_LIBRARY is not set
CONFIG_MBEDTLS_TLS_VERSION_1_0 is not set
CONFIG_MBEDTLS_TLS_VERSION_1_1 is not set
CONFIG_MBEDTLS_TLS_VERSION_1_2=y
CONFIG_MBEDTLS_DTLS is not set
CONFIG_MBEDTLS_SSL_EXPORT_KEYS is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ALL_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_PSK_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_DHE_PSK_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDHE_PSK_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_RSA_PSK_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_RSA_ENABLED=y
CONFIG_MBEDTLS_KEY_EXCHANGE_DHE_RSA_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDHE_RSA_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDHE_ECDSA_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDH_ECDSA_ENABLED is not set
CONFIG_MBEDTLS_ECDSA_DETERMINISTIC is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECDH_RSA_ENABLED is not set
CONFIG_MBEDTLS_KEY_EXCHANGE_ECJPAKE_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_ALL_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_AES_ENABLED=y
CONFIG_MBEDTLS_AES_ROM_TABLES=y
CONFIG_MBEDTLS_CIPHER_CAMELLIA_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_DES_ENABLED=y
CONFIG_MBEDTLS_CIPHER_ARC4_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_CHACHA20_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_BLOWFISH_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_CCM_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_MODE_XTS_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_MODE_GCM_ENABLED is not set
CONFIG_MBEDTLS_CIPHER_CBC_ENABLED=y
CONFIG_MBEDTLS_MAC_ALL_ENABLED is not set
CONFIG_MBEDTLS_MAC_MD4_ENABLED is not set
CONFIG_MBEDTLS_MAC_MD5_ENABLED=y
CONFIG_MBEDTLS_MAC_SHA1_ENABLED=y
CONFIG_MBEDTLS_MAC_SHA256_ENABLED=y
CONFIG_MBEDTLS_SHA256_SMALLER=y
CONFIG_MBEDTLS_MAC_SHA512_ENABLED is not set
CONFIG_MBEDTLS_MAC_POLY1305_ENABLED is not set
CONFIG_MBEDTLS_MAC_CMAC_ENABLED is not set
CONFIG_MBEDTLS_CTR_DRBG_ENABLED=y
CONFIG_MBEDTLS_HMAC_DRBG_ENABLED is not set
CONFIG_MBEDTLS_GENPRIME_ENABLED is not set
CONFIG_MBEDTLS_PEM_CERTIFICATE_FORMAT is not set
CONFIG_MBEDTLS_HAVE_ASM is not set
CONFIG_MBEDTLS_ENTROPY_ENABLED is not set
CONFIG_MBEDTLS_USER_CONFIG_ENABLE is not set
CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN=1500
CONFIG_MBEDTLS_DEBUG is not set
CONFIG_MBEDTLS_TEST is not set
CONFIG_MBEDTLS_ENABLE_HEAP is not set
CONFIG_APP_LINK_WITH_MBEDTLS=y
CONFIG_HAS_MEC_HAL is not set
CONFIG_OPENAMP is not set
CONFIG_HAS_STM32CUBE=y
CONFIG_USE_STM32_LL_UTILS=y
CONFIG_MIPI_SYST_LIB is not set
CONFIG_TINYCBOR is not set

TLS configuration

Supported TLS version

end of Supported TLS version

Ciphersuite configuration

Supported key exchange modes

Supported cipher modes

Supported message authentication methods

end of Ciphersuite configuration

Random number generators

Other configurations

end of TLS configuration
end of Modules
CONFIG_SPI is not set
CONFIG_I2C is not set
CONFIG_MODEM is not set
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_BOARD="nucleo_f767zi"
CONFIG_UART_3=y
CONFIG_UART_6=y
CONFIG_SOC="stm32f767xx"
CONFIG_SOC_SERIES="stm32f7"
CONFIG_NUM_IRQS=110
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=72000000
CONFIG_WATCHDOG is not set
CONFIG_UART_NS16550 is not set
CONFIG_GPIO=y
CONFIG_SYS_POWER_MANAGEMENT is not set
CONFIG_DEVICE_POWER_MANAGEMENT is not set
CONFIG_CORTEX_M_SYSTICK=y
CONFIG_CLOCK_CONTROL=y
CONFIG_SYS_CLOCK_TICKS_PER_SEC=10000
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_FLOAT is not set
CONFIG_TEXT_SECTION_OFFSET=0
CONFIG_FLASH_SIZE=2048
CONFIG_FLASH_BASE_ADDRESS=0x8000000
CONFIG_SRAM_SIZE=384
CONFIG_SRAM_BASE_ADDRESS=0x20020000
CONFIG_CPU_HAS_CUSTOM_FIXED_SOC_MPU_REGIONS is not set
CONFIG_TINYCRYPT is not set
CONFIG_CLOCK_CONTROL_STM32_CUBE=y
CONFIG_UART_STM32=y
CONFIG_GPIO_STM32=y
CONFIG_GPIO_STM32_PORTA=y
CONFIG_GPIO_STM32_PORTB=y
CONFIG_GPIO_STM32_PORTC=y
CONFIG_PINMUX_STM32=y
CONFIG_GPIO_STM32_PORTD=y
CONFIG_GPIO_STM32_PORTF=y
CONFIG_GPIO_STM32_PORTE=y
CONFIG_GPIO_STM32_PORTG=y
CONFIG_GPIO_STM32_PORTH=y
CONFIG_GPIO_STM32_PORTI=y
CONFIG_GPIO_STM32_PORTJ=y
CONFIG_GPIO_STM32_PORTK=y
CONFIG_BOARD_NUCLEO_F767ZI=y

Board Options

CONFIG_SOC_SERIES_BEETLE is not set
CONFIG_SOC_SERIES_MPS2 is not set
CONFIG_SOC_SERIES_MUSCA is not set
CONFIG_SOC_SERIES_MUSCA_B1 is not set
CONFIG_SOC_SERIES_SAM3X is not set
CONFIG_SOC_SERIES_SAM4S is not set
CONFIG_SOC_SERIES_SAME70 is not set
CONFIG_SOC_SERIES_SAMD20 is not set
CONFIG_SOC_SERIES_SAMD21 is not set
CONFIG_SOC_SERIES_SAMD51 is not set
CONFIG_SOC_SERIES_SAME51 is not set
CONFIG_SOC_SERIES_SAME53 is not set
CONFIG_SOC_SERIES_SAME54 is not set
CONFIG_SOC_SERIES_SAMR21 is not set
CONFIG_SOC_SERIES_PSOC62 is not set
CONFIG_SOC_SERIES_MEC1501X is not set
CONFIG_SOC_SERIES_MEC1701X is not set
CONFIG_SOC_SERIES_NRF51X is not set
CONFIG_SOC_SERIES_NRF52X is not set
CONFIG_SOC_SERIES_NRF53X is not set
CONFIG_SOC_SERIES_NRF91X is not set
CONFIG_SOC_SERIES_IMX_6X_M4 is not set
CONFIG_SOC_SERIES_IMX7_M4 is not set
CONFIG_SOC_SERIES_IMX_RT is not set
CONFIG_SOC_SERIES_KINETIS_K2X is not set
CONFIG_SOC_SERIES_KINETIS_K6X is not set
CONFIG_SOC_SERIES_KINETIS_K8X is not set
CONFIG_SOC_SERIES_KINETIS_KE1XF is not set
CONFIG_SOC_SERIES_KINETIS_KL2X is not set
CONFIG_SOC_SERIES_KINETIS_KV5X is not set
CONFIG_SOC_SERIES_KINETIS_KWX is not set
CONFIG_SOC_SERIES_LPC54XXX is not set
CONFIG_SOC_SERIES_LPC55XXX is not set
CONFIG_SOC_SERIES_EFM32HG is not set
CONFIG_SOC_SERIES_EFM32PG12B is not set
CONFIG_SOC_SERIES_EFM32WG is not set
CONFIG_SOC_SERIES_EFR32FG1P is not set
CONFIG_SOC_SERIES_EFR32MG12P is not set
CONFIG_SOC_SERIES_STM32F0X is not set
CONFIG_SOC_SERIES_STM32F1X is not set
CONFIG_SOC_SERIES_STM32F2X is not set
CONFIG_SOC_SERIES_STM32F3X is not set
CONFIG_SOC_SERIES_STM32F4X is not set
CONFIG_SOC_SERIES_STM32F7X=y
CONFIG_SOC_SERIES_STM32G0X is not set
CONFIG_SOC_SERIES_STM32G4X is not set
CONFIG_SOC_SERIES_STM32H7X is not set
CONFIG_SOC_SERIES_STM32L0X is not set
CONFIG_SOC_SERIES_STM32L1X is not set
CONFIG_SOC_SERIES_STM32L4X is not set
CONFIG_SOC_SERIES_STM32MP1X is not set
CONFIG_SOC_SERIES_STM32WBX is not set
CONFIG_SOC_TI_LM3S6965 is not set
CONFIG_SOC_SERIES_CC13X2_CC26X2 is not set
CONFIG_SOC_SERIES_CC32XX is not set
CONFIG_SOC_SERIES_MSP432P4XX is not set
CONFIG_SOC_XILINX_ZYNQMP_RPU is not set

Hardware Configuration

CONFIG_CPU_HAS_ARM_MPU=y
CONFIG_CPU_HAS_FPU_DOUBLE_PRECISION=y
CONFIG_HAS_SWO=y
CONFIG_SOC_FAMILY="st_stm32"
CONFIG_SOC_FAMILY_STM32=y
CONFIG_SOC_STM32F723XX is not set
CONFIG_SOC_STM32F746XX is not set
CONFIG_SOC_STM32F756XX is not set
CONFIG_SOC_STM32F767XX=y
CONFIG_SOC_STM32F769XX is not set
CONFIG_RPROC_RSC_TABLE is not set
CONFIG_SOC_LOG_LEVEL_OFF is not set
CONFIG_SOC_LOG_LEVEL_ERR is not set
CONFIG_SOC_LOG_LEVEL_WRN is not set
CONFIG_SOC_LOG_LEVEL_INF=y
CONFIG_SOC_LOG_LEVEL_DBG is not set
CONFIG_SOC_LOG_LEVEL=3
end of Hardware Configuration

ARM Options

CONFIG_CPU_CORTEX=y
CONFIG_CPU_CORTEX_M=y
CONFIG_ISA_THUMB2=y
CONFIG_STACK_ALIGN_DOUBLE_WORD=y
CONFIG_RUNTIME_NMI is not set
CONFIG_PLATFORM_SPECIFIC_INIT is not set
CONFIG_FAULT_DUMP=2
CONFIG_CPU_CORTEX_M7=y
CONFIG_CPU_CORTEX_M_HAS_SYSTICK=y
CONFIG_CPU_CORTEX_M_HAS_DWT=y
CONFIG_CPU_CORTEX_M_HAS_BASEPRI=y
CONFIG_CPU_CORTEX_M_HAS_VTOR=y
CONFIG_CPU_CORTEX_M_HAS_PROGRAMMABLE_FAULT_PRIOS=y
CONFIG_ARMV7_M_ARMV8_M_MAINLINE=y
CONFIG_ARMV7_M_ARMV8_M_FP=y
CONFIG_XIP=y

ARM Cortex-M0/M0+/M3/M4/M7/M23/M33 options

CONFIG_GEN_ISR_TABLES=y
CONFIG_ZERO_LATENCY_IRQS is not set
end of ARM Cortex-M0/M0+/M3/M4/M7/M23/M33 options
CONFIG_GEN_IRQ_VECTOR_TABLE=y
CONFIG_ARM_MPU=y
CONFIG_ARM_MPU_REGION_MIN_ALIGN_AND_SIZE=32
CONFIG_MPU_STACK_GUARD is not set
CONFIG_MPU_ALLOW_FLASH_WRITE=y
CONFIG_CUSTOM_SECTION_ALIGN is not set
CONFIG_CUSTOM_SECTION_MIN_ALIGN_SIZE=32
CONFIG_ARCH="arm"
end of ARM Options
CONFIG_ARC is not set
CONFIG_ARM=y
CONFIG_X86 is not set
CONFIG_NIOS2 is not set
CONFIG_RISCV is not set
CONFIG_XTENSA is not set
CONFIG_ARCH_POSIX is not set

General Architecture Options

CONFIG_ARCH_LOG_LEVEL_OFF is not set
CONFIG_ARCH_LOG_LEVEL_ERR is not set
CONFIG_ARCH_LOG_LEVEL_WRN is not set
CONFIG_ARCH_LOG_LEVEL_INF=y
CONFIG_ARCH_LOG_LEVEL_DBG is not set
CONFIG_ARCH_LOG_LEVEL=3
CONFIG_MPU_LOG_LEVEL_OFF is not set
CONFIG_MPU_LOG_LEVEL_ERR is not set
CONFIG_MPU_LOG_LEVEL_WRN is not set
CONFIG_MPU_LOG_LEVEL_INF=y
CONFIG_MPU_LOG_LEVEL_DBG is not set
CONFIG_MPU_LOG_LEVEL=3
CONFIG_HW_STACK_PROTECTION is not set
CONFIG_USERSPACE is not set
CONFIG_PRIVILEGED_STACK_SIZE=1024
CONFIG_PRIVILEGED_STACK_TEXT_AREA=256
CONFIG_KOBJECT_TEXT_AREA=256
CONFIG_STACK_GROWS_UP is not set
CONFIG_NOCACHE_MEMORY is not set

Interrupt Configuration

CONFIG_DYNAMIC_INTERRUPTS is not set
CONFIG_GEN_SW_ISR_TABLE=y
CONFIG_ARCH_SW_ISR_TABLE_ALIGN=0
CONFIG_GEN_IRQ_START_VECTOR=0
end of Interrupt Configuration
end of General Architecture Options
CONFIG_ARCH_HAS_STACK_PROTECTION=y
CONFIG_ARCH_HAS_USERSPACE=y
CONFIG_ARCH_HAS_EXECUTABLE_PAGE_BIT=y
CONFIG_ARCH_HAS_NOCACHE_MEMORY_SUPPORT=y
CONFIG_ARCH_HAS_RAMFUNC_SUPPORT=y
CONFIG_ARCH_HAS_NESTED_EXCEPTION_DETECTION=y
CONFIG_ARCH_HAS_THREAD_ABORT=y
CONFIG_CPU_HAS_FPU=y
CONFIG_CPU_HAS_MPU=y
CONFIG_MEMORY_PROTECTION=y
CONFIG_MPU_REQUIRES_POWER_OF_TWO_ALIGNMENT=y

General Kernel Options

CONFIG_KERNEL_LOG_LEVEL_OFF is not set
CONFIG_KERNEL_LOG_LEVEL_ERR is not set
CONFIG_KERNEL_LOG_LEVEL_WRN is not set
CONFIG_KERNEL_LOG_LEVEL_INF=y
CONFIG_KERNEL_LOG_LEVEL_DBG is not set
CONFIG_KERNEL_LOG_LEVEL=3
CONFIG_NUM_COOP_PRIORITIES=16
CONFIG_NUM_PREEMPT_PRIORITIES=15
CONFIG_MAIN_THREAD_PRIORITY=0
CONFIG_COOP_ENABLED=y
CONFIG_PREEMPT_ENABLED=y
CONFIG_PRIORITY_CEILING=0
CONFIG_NUM_METAIRQ_PRIORITIES=0
CONFIG_SCHED_DEADLINE is not set
CONFIG_SCHED_CPU_MASK is not set
CONFIG_MAIN_STACK_SIZE=10240
CONFIG_IDLE_STACK_SIZE=320
CONFIG_ISR_STACK_SIZE=2048
CONFIG_THREAD_STACK_INFO=y
CONFIG_THREAD_CUSTOM_DATA is not set
CONFIG_ERRNO=y
CONFIG_SCHED_DUMB=y
CONFIG_SCHED_SCALABLE is not set
CONFIG_SCHED_MULTIQ is not set
CONFIG_WAITQ_SCALABLE is not set
CONFIG_WAITQ_DUMB=y

Kernel Debugging and Metrics

CONFIG_INIT_STACKS is not set
CONFIG_KERNEL_DEBUG is not set
CONFIG_BOOT_BANNER=y
CONFIG_BOOT_DELAY=0
CONFIG_EXECUTION_BENCHMARKING is not set
CONFIG_THREAD_MONITOR is not set
CONFIG_THREAD_NAME is not set
end of Kernel Debugging and Metrics

Work Queue Options

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=1024
CONFIG_SYSTEM_WORKQUEUE_PRIORITY=-1
CONFIG_OFFLOAD_WORKQUEUE_STACK_SIZE=1024
CONFIG_OFFLOAD_WORKQUEUE_PRIORITY=-1
end of Work Queue Options

Atomic Operations

CONFIG_ATOMIC_OPERATIONS_BUILTIN=y
end of Atomic Operations

Timer API Options

CONFIG_TIMESLICING=y
CONFIG_TIMESLICE_SIZE=0
CONFIG_TIMESLICE_PRIORITY=0
CONFIG_POLL is not set
end of Timer API Options

Other Kernel Object Options

CONFIG_NUM_MBOX_ASYNC_MSGS=10
CONFIG_NUM_PIPE_ASYNC_MSGS=10
CONFIG_HEAP_MEM_POOL_SIZE=0
end of Other Kernel Object Options
CONFIG_ARCH_HAS_CUSTOM_SWAP_TO_MAIN=y
CONFIG_SWAP_NONATOMIC=y
CONFIG_SYS_CLOCK_EXISTS=y

Initialization Priorities

CONFIG_KERNEL_INIT_PRIORITY_OBJECTS=30
CONFIG_KERNEL_INIT_PRIORITY_DEFAULT=40
CONFIG_KERNEL_INIT_PRIORITY_DEVICE=50
CONFIG_APPLICATION_INIT_PRIORITY=90
end of Initialization Priorities

Security Options

end of Security Options

SMP Options

CONFIG_MP_NUM_CPUS=1
end of SMP Options
CONFIG_TICKLESS_IDLE=y
CONFIG_TICKLESS_IDLE_THRESH=3
CONFIG_TICKLESS_KERNEL=y
end of General Kernel Options
CONFIG_HAS_DTS=y
CONFIG_HAS_DTS_GPIO=y

Device Drivers

CONFIG_IEEE802154 is not set
CONFIG_LORA is not set
CONFIG_UART_CONSOLE_ON_DEV_NAME="UART_3"
CONFIG_CONSOLE=y
CONFIG_CONSOLE_INPUT_MAX_LINE_LEN=128
CONFIG_CONSOLE_HAS_DRIVER=y
CONFIG_CONSOLE_HANDLER=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_CONSOLE_INIT_PRIORITY=60
CONFIG_UART_CONSOLE_DEBUG_SERVER_HOOKS is not set
CONFIG_UART_CONSOLE_MCUMGR is not set
CONFIG_USB_UART_CONSOLE is not set
CONFIG_RAM_CONSOLE is not set
CONFIG_IPM_CONSOLE_SENDER is not set
CONFIG_IPM_CONSOLE_RECEIVER is not set
CONFIG_UART_PIPE is not set
CONFIG_UART_MCUMGR is not set
CONFIG_UART_CONSOLE_LOG_LEVEL_OFF is not set
CONFIG_UART_CONSOLE_LOG_LEVEL_ERR is not set
CONFIG_UART_CONSOLE_LOG_LEVEL_WRN is not set
CONFIG_UART_CONSOLE_LOG_LEVEL_INF=y
CONFIG_UART_CONSOLE_LOG_LEVEL_DBG is not set
CONFIG_UART_CONSOLE_LOG_LEVEL=3
CONFIG_NET_LOOPBACK is not set
CONFIG_SERIAL=y

Capabilities

CONFIG_SERIAL_HAS_DRIVER=y
CONFIG_SERIAL_SUPPORT_INTERRUPT=y
CONFIG_UART_LINE_CTRL is not set
CONFIG_UART_DRV_CMD is not set

Serial Drivers

CONFIG_UART_NSIM is not set
CONFIG_UART_1 is not set
CONFIG_UART_2 is not set
CONFIG_UART_4 is not set
CONFIG_UART_5 is not set
CONFIG_UART_7 is not set
CONFIG_UART_8 is not set
CONFIG_UART_9 is not set
CONFIG_UART_10 is not set
CONFIG_UART_ALTERA_JTAG is not set
CONFIG_UART_PL011 is not set

Interrupt Controllers

CONFIG_SWERV_PIC is not set
CONFIG_MULTI_LEVEL_INTERRUPTS is not set
CONFIG_EXTI_STM32=y
CONFIG_EXTI_STM32_EXTI0_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI1_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI2_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI3_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI4_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI9_5_IRQ_PRI=0
CONFIG_EXTI_STM32_EXTI15_10_IRQ_PRI=0
CONFIG_EXTI_STM32_PVD_IRQ_PRI=0
CONFIG_EXTI_STM32_OTG_FS_WKUP_IRQ_PRI=0
CONFIG_EXTI_STM32_TAMP_STAMP_IRQ_PRI=0
CONFIG_EXTI_STM32_RTC_WKUP_IRQ_PRI=0
CONFIG_EXTI_STM32_LPTIM1_IRQ_PRI=0
end of Interrupt Controllers

Timer Drivers

CONFIG_SYSTEM_CLOCK_DISABLE=y
CONFIG_TIMER_READS_ITS_FREQUENCY_AT_RUNTIME is not set
CONFIG_SYSTEM_CLOCK_SLOPPY_IDLE is not set
CONFIG_SYSTEM_CLOCK_INIT_PRIORITY=0
CONFIG_TICKLESS_CAPABLE=y
end of Timer Drivers
CONFIG_ENTROPY_GENERATOR is not set
CONFIG_GPIO_LOG_LEVEL_OFF is not set
CONFIG_GPIO_LOG_LEVEL_ERR is not set
CONFIG_GPIO_LOG_LEVEL_WRN is not set
CONFIG_GPIO_LOG_LEVEL_INF=y
CONFIG_GPIO_LOG_LEVEL_DBG is not set
CONFIG_GPIO_LOG_LEVEL=3
CONFIG_GPIO_SHELL is not set
CONFIG_GPIO_DW is not set
CONFIG_GPIO_INTEL_APL is not set
CONFIG_GPIO_PL061 is not set
CONFIG_SHARED_IRQ is not set
CONFIG_I2S is not set
CONFIG_PWM is not set
CONFIG_PINMUX=y
CONFIG_PINMUX_NAME="PINMUX"
CONFIG_PINMUX_INIT_PRIORITY=45
CONFIG_PINMUX_STM32_DEVICE_INITIALIZATION_PRIORITY=2
CONFIG_ADC is not set
CONFIG_CLOCK_CONTROL_LOG_LEVEL_OFF is not set
CONFIG_CLOCK_CONTROL_LOG_LEVEL_ERR is not set
CONFIG_CLOCK_CONTROL_LOG_LEVEL_WRN is not set
CONFIG_CLOCK_CONTROL_LOG_LEVEL_INF=y
CONFIG_CLOCK_CONTROL_LOG_LEVEL_DBG is not set
CONFIG_CLOCK_CONTROL_LOG_LEVEL=3
CONFIG_CLOCK_CONTROL_STM32_DEVICE_INIT_PRIORITY=1
CONFIG_CLOCK_STM32_SYSCLK_SRC_HSE is not set
CONFIG_CLOCK_STM32_SYSCLK_SRC_HSI is not set
CONFIG_CLOCK_STM32_SYSCLK_SRC_PLL=y
CONFIG_CLOCK_STM32_HSE_BYPASS=y
CONFIG_CLOCK_STM32_HSE_CLOCK=8000000
CONFIG_CLOCK_STM32_PLL_SRC_HSI is not set
CONFIG_CLOCK_STM32_PLL_SRC_HSE=y
CONFIG_CLOCK_STM32_PLL_M_DIVISOR=4
CONFIG_CLOCK_STM32_PLL_N_MULTIPLIER=72
CONFIG_CLOCK_STM32_PLL_P_DIVISOR=2
CONFIG_CLOCK_STM32_PLL_Q_DIVISOR=3
CONFIG_CLOCK_STM32_AHB_PRESCALER=1
CONFIG_CLOCK_STM32_APB1_PRESCALER=2
CONFIG_CLOCK_STM32_APB2_PRESCALER=1
CONFIG_CLOCK_STM32_MCO1_SRC_NOCLOCK=y
CONFIG_CLOCK_STM32_MCO2_SRC_NOCLOCK=y
CONFIG_PTP_CLOCK is not set
CONFIG_IPM is not set
CONFIG_FLASH_HAS_DRIVER_ENABLED=y
CONFIG_FLASH_HAS_PAGE_LAYOUT=y
CONFIG_FLASH=y
CONFIG_FLASH_LOG_LEVEL_OFF is not set
CONFIG_FLASH_LOG_LEVEL_ERR is not set
CONFIG_FLASH_LOG_LEVEL_WRN is not set
CONFIG_FLASH_LOG_LEVEL_INF=y
CONFIG_FLASH_LOG_LEVEL_DBG is not set
CONFIG_FLASH_LOG_LEVEL=3
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_SOC_FLASH_STM32=y
CONFIG_FLASH_SIMULATOR is not set
CONFIG_SENSOR is not set
CONFIG_COUNTER is not set
CONFIG_DMA is not set
CONFIG_USB is not set
CONFIG_CRYPTO is not set
CONFIG_DISPLAY is not set
CONFIG_LED_STRIP is not set
CONFIG_WIFI is not set
CONFIG_LED is not set
CONFIG_CAN is not set
CONFIG_AUDIO is not set
CONFIG_NEURAL_NET_ACCEL is not set
CONFIG_HWINFO is not set
CONFIG_ESPI is not set
CONFIG_PS2 is not set
CONFIG_KSCAN is not set
CONFIG_VIDEO is not set
CONFIG_EEPROM is not set
end of Device Drivers

C Library

CONFIG_MINIMAL_LIBC=y
CONFIG_NEWLIB_LIBC is not set
CONFIG_EXTERNAL_LIBC is not set
CONFIG_MINIMAL_LIBC_MALLOC=y
CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE=0
CONFIG_MINIMAL_LIBC_CALLOC=y
CONFIG_MINIMAL_LIBC_REALLOCARRAY=y
CONFIG_MINIMAL_LIBC_LL_PRINTF is not set
CONFIG_STDOUT_CONSOLE=y
end of C Library

Additional libraries

CONFIG_LVGL is not set

OS Support Library

CONFIG_JSON_LIBRARY is not set
CONFIG_RING_BUFFER is not set
CONFIG_BASE64 is not set
end of OS Support Library
CONFIG_POSIX_MAX_FDS=4
CONFIG_POSIX_API is not set
CONFIG_PTHREAD_IPC is not set
CONFIG_POSIX_CLOCK is not set
CONFIG_MAX_TIMER_COUNT=5
CONFIG_POSIX_MQUEUE is not set
CONFIG_UPDATEHUB is not set
CONFIG_UPDATEHUB_LOG_LEVEL_OFF is not set
CONFIG_UPDATEHUB_LOG_LEVEL_ERR is not set
CONFIG_UPDATEHUB_LOG_LEVEL_WRN is not set
CONFIG_UPDATEHUB_LOG_LEVEL_INF=y
CONFIG_UPDATEHUB_LOG_LEVEL_DBG is not set
CONFIG_UPDATEHUB_LOG_LEVEL=3
end of Additional libraries
CONFIG_BT is not set
CONFIG_CONSOLE_SUBSYS is not set
CONFIG_CPLUSPLUS is not set

System Monitoring Options

CONFIG_BOOT_TIME_MEASUREMENT is not set
CONFIG_STATS is not set
end of System Monitoring Options

Debugging Options

CONFIG_DEBUG=y
CONFIG_TRACING is not set
CONFIG_STACK_USAGE is not set
CONFIG_STACK_SENTINEL is not set
CONFIG_PRINTK=y
CONFIG_EARLY_CONSOLE=y
CONFIG_ASSERT is not set
CONFIG_FORCE_NO_ASSERT is not set
CONFIG_ASSERT_VERBOSE=y
CONFIG_ASSERT_NO_FILE_INFO is not set
CONFIG_ASSERT_NO_COND_INFO is not set
CONFIG_ASSERT_NO_MSG_INFO is not set
CONFIG_OBJECT_TRACING is not set
CONFIG_OVERRIDE_FRAME_POINTER_DEFAULT is not set
CONFIG_DEBUG_INFO is not set
CONFIG_OPENOCD_SUPPORT is not set
CONFIG_TRACING_CPU_STATS is not set
CONFIG_TRACING_CTF is not set
CONFIG_HAS_SEGGER_RTT=y
CONFIG_USE_SEGGER_RTT is not set
end of Debugging Options
CONFIG_DISK_ACCESS is not set

File Systems

CONFIG_FILE_SYSTEM is not set
CONFIG_FCB is not set
CONFIG_NVS is not set
end of File Systems
CONFIG_LOG=y
CONFIG_LOG_MINIMAL is not set
CONFIG_LOG_RUNTIME_FILTERING is not set
CONFIG_LOG_DEFAULT_LEVEL=4
CONFIG_LOG_OVERRIDE_LEVEL=0
CONFIG_LOG_MAX_LEVEL=4
CONFIG_LOG_MIPI_SYST_ENABLE is not set

Prepend log message with function name

CONFIG_LOG_FUNC_NAME_PREFIX_ERR is not set
CONFIG_LOG_FUNC_NAME_PREFIX_WRN is not set
CONFIG_LOG_FUNC_NAME_PREFIX_INF is not set
CONFIG_LOG_FUNC_NAME_PREFIX_DBG=y
end of Prepend log message with function name
CONFIG_LOG_PRINTK is not set
CONFIG_LOG_IMMEDIATE=y
CONFIG_LOG_IMMEDIATE_CLEAN_OUTPUT is not set
CONFIG_LOG_ENABLE_FANCY_OUTPUT_FORMATTING is not set
CONFIG_LOG_DOMAIN_ID=0
CONFIG_LOG_FRONTEND is not set
CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_BACKEND_SWO is not set
CONFIG_LOG_BACKEND_SHOW_COLOR=y
CONFIG_LOG_BACKEND_FORMAT_TIMESTAMP=y

Management

CONFIG_MCUMGR_SMP_BT is not set
CONFIG_MCUMGR_SMP_SHELL is not set
CONFIG_MCUMGR_SMP_UART is not set
CONFIG_MCUMGR is not set
end of Management

Networking

CONFIG_NET_BUF is not set
CONFIG_NETWORKING is not set
end of Networking
CONFIG_SHELL is not set
CONFIG_IMG_MANAGER is not set

Random subsystem

CONFIG_TEST_RANDOM_GENERATOR is not set
end of Random subsystem

Storage

CONFIG_FLASH_MAP=y
CONFIG_FLASH_MAP_CUSTOM is not set
end of Storage
CONFIG_SETTINGS is not set

Testing

CONFIG_ZTEST is not set
CONFIG_ZTEST_MOCKING is not set
CONFIG_TEST is not set
CONFIG_TEST_SHELL is not set
CONFIG_TEST_EXTRA_STACKSIZE=0
CONFIG_TEST_USERSPACE is not set
CONFIG_TEST_ARM_CORTEX_M=y
end of Testing
CONFIG_CHARACTER_FRAMEBUFFER is not set
CONFIG_JWT is not set

Controller Area Network (CAN) bus subsystem

end of Controller Area Network (CAN) bus subsystem

External Sources

HALs

CONFIG_HAS_CMSIS_CORE=y
CONFIG_HAS_CMSIS_CORE_M=y
end of HALs

Cryptography

end of Cryptography
CONFIG_FNMATCH is not set
end of External Sources

Build and Link Features

Linker Options

CONFIG_LINKER_ORPHAN_SECTION_PLACE is not set
CONFIG_LINKER_ORPHAN_SECTION_WARN=y
CONFIG_LINKER_ORPHAN_SECTION_ERROR is not set
CONFIG_CODE_DATA_RELOCATION is not set
CONFIG_HAS_FLASH_LOAD_OFFSET=y
CONFIG_USE_DT_CODE_PARTITION is not set
CONFIG_FLASH_LOAD_OFFSET=0
CONFIG_FLASH_LOAD_SIZE=0
CONFIG_HAVE_CUSTOM_LINKER_SCRIPT is not set
CONFIG_CUSTOM_RODATA_LD is not set
CONFIG_CUSTOM_RWDATA_LD is not set
CONFIG_CUSTOM_SECTIONS_LD is not set
CONFIG_KERNEL_ENTRY="__start"
CONFIG_LINKER_SORT_BY_ALIGNMENT=y
end of Linker Options

Compiler Options

CONFIG_NATIVE_APPLICATION is not set
CONFIG_SIZE_OPTIMIZATIONS is not set
CONFIG_SPEED_OPTIMIZATIONS is not set
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_NO_OPTIMIZATIONS is not set
CONFIG_COMPILER_OPT=""
end of Compiler Options
CONFIG_ASSERT_ON_ERRORS is not set
CONFIG_NO_RUNTIME_CHECKS is not set
CONFIG_RUNTIME_ERROR_CHECKS=y

Build Options

CONFIG_KERNEL_BIN_NAME="zephyr"
CONFIG_OUTPUT_STAT=y
CONFIG_OUTPUT_DISASSEMBLY=y
CONFIG_OUTPUT_PRINT_MEMORY_USAGE=y
CONFIG_BUILD_OUTPUT_BIN=y
CONFIG_BUILD_OUTPUT_EXE is not set
CONFIG_BUILD_OUTPUT_S19 is not set
CONFIG_BUILD_NO_GAP_FILL is not set
CONFIG_BUILD_OUTPUT_STRIPPED is not set
CONFIG_APPLICATION_DEFINED_SYSCALL is not set
end of Build Options
end of Build and Link Features

Boot Options

CONFIG_IS_BOOTLOADER is not set
CONFIG_BOOTLOADER_MCUBOOT is not set
CONFIG_REBOOT is not set
CONFIG_MISRA_SANE is not set
end of Boot Options

Compatibility

CONFIG_COMPAT_INCLUDES=y
end of Compatibility

@kkiyota Yeah, that ended up quite unreadable :-P You should put it in a non-formatted block of text, anyways I think the issue is with the partitions you used, I was looking how I configured them for Mynewt and since there are non-linear sector sizes I would suggest you test with the same partition structure which would be:
	/* 64KB for bootloader */
	boot_partition: partition@0 {
		label = "mcuboot";
		reg = <0x00000000 0x00010000>;
		read-only;
	};

	/* storage: 64KB for settings */
	storage_partition: partition@10000 {
		label = "storage";
		reg = <0x00010000 0x00010000>;
	};

	/* application image slot: 768KB */
	slot0_partition: partition@40000 {
		label = "image-0";
		reg = <0x00040000 0x000C0000>;
	};

	/* backup slot: 768KB */
	slot1_partition: partition@100000 {
		label = "image-1";
		reg = <0x00100000 0x000C0000>;
	};

	/* swap slot: 256KB */
	scratch_partition: partition@1c0000 {
		label = "image-scratch";
		reg = <0x001c0000 0x00040000>;
	};

@utzig I have no idea how I can paste as a plain text here.  Instead, I added it as a text file.  Please review it again.
I'll try using your partition later and let you know.
Thank you,
Koji

It is known that the samples/zephyr makefile likely will only work for the frdm_k64f. Both the flash programming, as well as assumptions about partition positions. We have it as an issue in MCUboot: https://github.com/JuulLabs-OSS/mcuboot/issues/213.

@d3zd3z Do you mean that I should wait until  https://github.com/JuulLabs-OSS/mcuboot/issues/213 will be resolved?

@kkiyota Would be nice if you could test with the suggested partition changes.

@utzig I'll work on it tomorrow due to conflict.

@utzig Could you also let me know your points?  The difference between your partition map and mine is just slots' capacity.

@kkiyota The sectors are not linear in the STM32F7, which means not all sectors have the same size, you are starting a slot in a smaller sector which can't be swapped.

@utzig In my dts file as attached below again, both slot0 and slot1 are 256KB.  Are you referring to this file?  Or anything else?
/// flash partition definition in zephyr/boards/arm/nucleo_f767zi/nucleo_f767zi.dts ///////
&flash0 {
/*

For more information, see:

http://docs.zephyrproject.org/devices/dts/flash_partitions.html
*/
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
/* 64KB for bootloader */
boot_partition: partition@0 {
label = "mcuboot";
reg = <0x00000000 0x00010000>;
read-only;
};
/* storage: 64KB for settings */
storage_partition: partition@10000 {
label = "storage";
reg = <0x00010000 0x00010000>;
};
/* application image slot: 256KB */
slot0_partition: partition@20000 {
label = "image-0";
reg = <0x00020000 0x00040000>;
};
/* backup slot: 256KB */
slot1_partition: partition@60000 {
label = "image-1";
reg = <0x00060000 0x00040000>;
};
/* swap slot: 256KB */
scratch_partition: partition@a0000 {
label = "image-scratch";
reg = <0x000a0000 0x00040000>;
};

};

/* application image slot: 256KB */
slot0_partition: partition@20000 {
label = "image-0";
reg = <0x00020000 0x00040000>;
};

The sector at 0x20000 is 128KB, which means you are using one sector plus half of the next sector (which is 256KB). MCUBoot in swap mode does not allow that.
/* backup slot: 256KB */
slot1_partition: partition@60000 {
label = "image-1";
reg = <0x00060000 0x00040000>;
};

The sector at 0x60000 is 256KB so this is one is OK.

@utzig Thank you for your reply!  Looking at Zephyr document as shown below, the first parameter is defined as offset, and second one is capacity.  Are you referring to the different spec?
//////////////////////////////////////////////////////////////////////////////////////
The content of the partitions node looks like this:
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
    partition1_label: partition@START_OFFSET_1 {
            label = "partition1_name";
            reg = <0xSTART_OFFSET_1 0xSIZE_1>;
    };

    /* ... */

    partitionN_label: partition@START_OFFSET_N {
            label = "partitionN_name";
            reg = <0xSTART_OFFSET_N 0xSIZE_N>;
    };

};
Where:
partitionX_label are device tree labels that can be used elsewhere in the device tree to refer to the partition
partitionX_name controls how defines generated by the Zephyr build system for this partition will be named
START_OFFSET_x is the start offset in hexadecimal notation of the partition from the beginning of the flash device
SIZE_x is the hexadecimal size, in bytes, of the flash partition

bug label removed as this is usage fault by incompatible partition configuration.
For get how partitions should be arranged pleas refer to mcuboot doc

@nvlsianpu Could you point out where my definition is incorrect if you think so?

I tested now with the partition configuration I have submitted earlier and I can confirm it can successfully upgrade and revert. I have built manually the bootloader and hello_word sample app, so maybe the there might exist an issue with the build system that @d3zd3z mentioned. I might try to test that tomorrow as well.

@nvlsianpu Could you point out where my definition is incorrect if you think so?

As I wrote before "The sector at 0x20000 is 128KB, which means you are using one sector plus half of the next sector (which is 256KB)", can it be more clear than this?
Maybe try reading the reference manual: https://www.st.com/content/ccc/resource/technical/document/reference_manual/group0/96/8b/0d/ec/16/22/43/71/DM00224583/files/DM00224583.pdf/jcr:content/translations/en.DM00224583.pdf
Go to page 88/1954, the sector at 0x20000 is 128KB and you can't mix sectors of different sizes; also you are describing it as 256KB in your DTS so it will use one sector + half sector. Your offsets should be updated to use the ones I have pasted here before; the size of the slots is not so important, I used 0xc0000 avoid wastings space, but it's fine if you want to stay with 0x40000.

@utzig Thank you for sending me ST document link!  I didn’t know such NAND FLASH block limitation.  I’ll try it ASAP.

@utzig I ran some experiments.

slot0_parition is set at Sector 5(256KB), slot1_partition is set at Sector 6 and scratch_partition is set at Sector 7.
It worked fine as shown below.

*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.044,000]  mcuboot: Unable to find bootable image
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.095,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:00.102,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1*
Hello World from hello1 on nucleo_f767zi!
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: test
[00:00:09.736,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:09.743,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1*
Hello World from hello2 on nucleo_f767zi!
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: none
[00:00:00.035,000]  mcuboot: Swap type: revert
[00:00:09.820,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:09.828,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1*
Hello World from hello1 on nucleo_f767zi!

slot0_parition is set at Sector 5&6(512KB), slot1_partition is set at Sector 7&8 and scratch_partition is set at Sector 9&10.
I got the following error when I loaded hello2, although I changed "--slot-size 0x80000".  Any idea how I can fix it?

////
koji@koji-VirtualBox:~/mcuboot.nucleo_f767zi/samples/zephyr$ make flash_hello2
pyocd flash -a 0x80C0000 signed-hello2.bin --pack ~/Documents/DFP/Keil.STM32F7xx_DFP.2.12.0.pack
[====================] 100%
0088446:CRITICAL:main:erase_sector(0x8120000) error: 1
Traceback (most recent call last):
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/main.py", line 344, in run
self._COMMANDSself._args.cmd
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/main.py", line 481, in do_flash
file_format=self._args.format)
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/flash/file_programmer.py", line 157, in program
self._loader.commit()
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/flash/loader.py", line 168, in commit
keep_unwritten=self._keep_unwritten)
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/flash/builder.py", line 466, in program
flash_operation = self._sector_erase_program_double_buffer(progress_cb)
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/flash/builder.py", line 863, in _sector_erase_program_double_buffer
self.flash.erase_sector(sector.addr)
File "/home/koji/.local/lib/python3.7/site-packages/pyocd/flash/flash.py", line 353, in erase_sector
raise FlashEraseFailure('erase_sector(0x%x) error: %i' % (address, result), address, result)
pyocd.core.exceptions.FlashEraseFailure: erase_sector(0x8120000) error: 1
make: *** [Makefile:194: flash_hello2] Error 1
/// Terminal screen ///
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.044,000]  mcuboot: Unable to find bootable image
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.095,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:00.102,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d*
Hello World from hello1 on nucleo_f767zi!
////
*** hello2 was not loaded here.
Best regards,
Koji

I have no idea why make flash_hello2 failed but you have to make it run without fails to actually load hello2 correctly into the slot and be able to run an upgrade.

I have no idea why make flash_hello2 failed but you have to make it run without fails to actually load hello2 correctly into the slot and be able to run an upgrade.

The Makefile that builds hello2 hardcodes everything about the partition, both when calling imgtool.py and when flashing the image. If this doesn't match the frdm-k64f, the upgrade won't likely work.

@d3zd3z  I just changed "--slot-size" assuming that it's the same as slot0 and slo1 partition size.  Is it correct understanding?
////////////////////////////
Build and sign "hello1".
hello1: check
(mkdir -p $(BUILD_DIR_HELLO1) &&
cd $(BUILD_DIR_HELLO1) &&
cmake -DFROM_WHO=hello1
-G"Ninja"
-DBOARD=$(BOARD)
$(SOURCE_DIRECTORY)/hello-world &&
ninja)
$(IMGTOOL) sign
--key $(SIGNING_KEY)
--header-size $(BOOT_HEADER_LEN)
--align $(FLASH_ALIGNMENT)
--version 1.2
--slot-size 0x80000
$(BUILD_DIR_HELLO1)/zephyr/zephyr.bin
signed-hello1.bin
Build and sign "hello2".
This is the same signing command as above, except that it adds the
"--pad" argument.  This will also add the trailer that indicates
this image is intended to be an upgrade.  It should be flashed into
the secondary slot instead of the primary slot.
hello2: check
(mkdir -p $(BUILD_DIR_HELLO2) &&
cd $(BUILD_DIR_HELLO2) &&
cmake -DFROM_WHO=hello2
-G"Ninja"
-DBOARD=$(BOARD)
$(SOURCE_DIRECTORY)/hello-world &&
ninja)
$(IMGTOOL) sign
--key $(SIGNING_KEY)
--header-size $(BOOT_HEADER_LEN)
--align $(FLASH_ALIGNMENT)
--version 1.2
--slot-size 0x80000
--pad
$(BUILD_DIR_HELLO2)/zephyr/zephyr.bin
signed-hello2.bin

@utzig Yes, I can compile it with no errors.  When signed-hello2.bin was loaded, I just got the error which looks error for erase.

Hi,
Looking at my error message in case of 2 x 256KB sectors for slot1 (Sector 7 and 8) , erase error seems to occur at 0x8120000 which is in Sector 8.   pyocd option for erase is set as sector erase as a default.  However, it seems that there is no way to specify the 2 sectors erase.  And it's not clear how erase and program operations are proceeded.
There is the description in pyocd document that pyocd doesn't run erase operation in "pyocd flash" command, but it looks erase operation was run.
Does anyone know how I can specify arguments for "pyocd flash" command or anything else?
In case of single sector dts configuration, it works fine.  So I guess there may be additional cares required for >2 sectors case.
Regards,
Koji
/////////////////////

koji@koji-VirtualBox:~/mcuboot.nucleo_f767zi/samples/zephyr$ make flash_hello2
pyocd flash -a 0x80C0000 signed-hello2.bin --pack ~/Documents/DFP/Keil.STM32F7xx_DFP.2.12.0.pack
[====================] 100%
0088446:CRITICAL:main:erase_sector(0x8120000) error: 1
Traceback (most recent call last):

Referring to the log file, this flash may be configured as dual bank mode which is defined in Table 4 below instead of single bank mode in Table 3.
So in my last case with the following slot1_partition, it would be overlapped to Bank 2.  I need to check it furthermore, though.

slot1_partition: partition@c0000 {
label = "image-1";
reg = <0x000C0000 0x00080000>;

I also confirmed by register read that flash controller in stm32f767zi was configured as single bank mode.  However, pyocd log info showed erase operation was performed by 128KB(target sector size in dual bank mode) instead of 256KB(target sector size in single bank mode).
So I guess my problem is related to pyocd.  Since my board files for nucleo-f767zi doesn't work with pyocd, I'm currently using Keil.STM32F7xx_DFP.2.12.0.pack which was downloaded from ARM site.
Any idea?

I use almost exclusively this tooling with STM32s: https://github.com/texane/stlink

@utzig Thank you!  Is it different from ST supplied tools?

@utzig Thank you! Is it different from ST supplied tools?

I don't know what tools ST are supplying these days, but stlink is open-source and works on 100% of the boards I use (with no configuration required).

@utzig Thanks!  In your case, does stlink work fine with 2 sectors of slot0 and slot1 like 256KB x2 in single bank mode?

@utzig Thanks! In your case, does stlink work fine with 2 sectors of slot0 and slot1 like 256KB x2 in single bank mode?

Yes, I have absolutely no issues, I use a lot of STM32 boards (20 or more) and everything works 100%.

@utzig Sounds good!  I'll implement and run with it.

@utzig I installed stlink thru Ubuntu Software store.
In case of slot0=slot1=scratch=256KB, swap case works fine.
However, in case of slot0=slot1=scratch=512KB or slot0=slot1=768KB/ scratch=256KB, hello1 was executed although flash write operation was performed well.  Expected result is that hello2 is run temporally and revert it on reset.
My set-flash command for hello2 is listed below.  Is it correct command?
Any idea why only 256KB case could work?

flash_hello2:
st-flash --reset --format binary write signed-hello2.bin 0x080C0000  <= 512KB case(Sector 7/8)
st-flash --reset --format binary write signed-hello2.bin 0x08100000  <= 768KB case(Sector 8/9/10)

@utzig Looks like I forgot to change --slot-size during imgtoo.py execution.  After I fixed it, everything looks fine as shown below in case of slot0=slot1=768KB and scratch=256KB.
Appreciated your help!

*** Booting Zephyr OS build z*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.044,000]  mcuboot: Unable to find bootable image
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.039,000]  mcuboot: Swap type: none
[00:00:00.095,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:00.102,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
Hello World from hello1 on nucleo_f767zi!
FLASH_OPTCR register= ffffaafd
*** *** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: primary slot
[00:00:00.040,000]  mcuboot: Swap type: test
[00:00:10.598,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:10.605,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
Hello World from hello2 on nucleo_f767zi!
FLASH_OPTCR register= ffffaafd
*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
[00:00:00.005,000]  mcuboot: Starting bootloader
[00:00:00.011,000]  mcuboot: Primary image: magic=good, swap_type=0x2, copy_done=0x1, image_ok=0x3
[00:00:00.021,000]  mcuboot: Scratch: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
[00:00:00.030,000]  mcuboot: Boot source: none
[00:00:00.035,000]  mcuboot: Swap type: revert
[00:00:15.926,000]  mcuboot: Bootloader chainload address offset: 0x40000
[00:00:15.933,000]  mcuboot: Jumping to the first image slot�*** Booting Zephyr OS build zephyr-v2.1.0-1214-g22326f6d99e8  ***
Hello World from hello1 on nucleo_f767zi!
FLASH_OPTCR register= ffffaafd


fix for JS totalling bug

Pivotal
Before the columns weren't totalling if the user's cursor was still in a value entry field. This fixes that.
Before

After

Looks okay... I'd say merge and set your code free! :-)


Make test.sh use REDIS_SERVER everywhere

Fedora is moving to valkey (see https://fedoraproject.org/wiki/Changes/Replace_Redis_With_Valkey).  This allows use to use valkey-server for the tests.

This probably requires someone at Redis Inc to weigh in.


How can I use different Neural Voice styles when synthesizing my audio files?

In this doc I've seen that the PT-BR-FranciscaNeural language support multiple voice styles.

Is there any way to get this list of supported styles with the SDK?
I didn't find any documentation with the full list of supported voice styles for FranciscaNeural.

How can I synthesize Francisca's voice using a calm or cheerful style, for example?
Here's my actual code:
speech_key, service_region = "***REDACTED***", "southcentralus"

speech_config = speechsdk.SpeechConfig(subscription=speech_key, region=service_region)
speech_config.speech_synthesis_voice_name = "pt-BR-FranciscaNeural"

file_config = speechsdk.audio.AudioOutputConfig(filename="output.wav")

speech_synthesizer = speechsdk.SpeechSynthesizer(speech_config=speech_config, audio_config=file_config)

## Calling the Speech Sythesizer
text = "Muito obrigado!" #Portuguese text
result = speech_synthesizer.speak_text_async(text).get()

I've based on this script to synthesize my wav files: speech_synthesis_sample.py

It is a pain point I share, that I can't query the list of supported voiced, or translation languages via the client SDK.
I have a work item in our backlog to add this functionality to the SDK API surface.
For now, you can get the list via the web, and in your program via a rest API.
General info: http://docs.microsofttranslator.com/languages.html
TTS Specific: https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/rest-text-to-speech#get-a-list-of-voices
And a REST example in Python: https://docs.microsoft.com/bs-latn-ba/azure/cognitive-services/speech-service/quickstart-python-get-text-to-speech-voices
As to the "Speaking Style" you probably want to look at the documentation on SSML support.
This gives you the most flexibility in adjusting prosody, pitch, or selecting a style using <mstts:express-as style="cheerful">
https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/speech-synthesis-markup
Let me know if you need more detail that this, and I will ask someone on our TTS team to give a more detailed response.
Brian.

Thanks Brian for the quick answer.
Some comments about the links you've shared:
This link is not working for me:
General info: http://docs.microsofttranslator.com/languages.html
I've used the third link to retrieve the full list of languages, and here I found all the styles for pt-BR-FranciscaNeural:
{'Name': 'Microsoft Server Speech Text to Speech Voice (pt-BR, FranciscaNeural)',
  'DisplayName': 'Francisca',
  'LocalName': 'Francisca',
  'ShortName': 'pt-BR-FranciscaNeural',
  'Gender': 'Female',
  'Locale': 'pt-BR',
  'StyleList': ['cheerful', 'calm'],
  'SampleRateHertz': '24000',
  'VoiceType': 'Neural'}

Regarding the SSML link, initially it wasn't clear for me how to use the SpeechSynthesizer.read_ssml_async() method. But I've managed to make it work!
speech_key, service_region = "***REDACTED***", "southcentralus"

speech_config = speechsdk.SpeechConfig(subscription=speech_key, region=service_region)
file_config = speechsdk.audio.AudioOutputConfig(filename="output.wav")

speech_synthesizer = speechsdk.SpeechSynthesizer(speech_config=speech_config, audio_config=file_config)

#SSML with Portuguese text
text = """
    <speak version="1.0" xmlns="http://www.w3.org/2001/10/synthesis" xmlns:mstts="https://www.w3.org/2001/mstts" xml:lang="pt-BR">
        <voice name="pt-BR-FranciscaNeural">
            <mstts:express-as style="calm">
                Muito obrigado!
            </mstts:express-as>
        </voice>
    </speak>"""

## Calling the Speech Sythesizer
result = speech_synthesizer.speak_ssml_async(ssml=text).get()

Feel free to close this issue thread. As a final feedback, I didn't find any documentation about sending SSML strings using the SpeechSynthesizer.read_ssml_async() method on this GitHub repo. It would be great to have a more clear documentation about creating audios with voice styles, using the Python SDK (and/or other SDKs).**

Thanks for the feedback on the documentation. I'm going to close this now since we took care of the original request.


Any ways to supply custom ChanelPipeline?

Hey Netty team,
Started to extend the DefaultChannelPipeline and found out that it is not possible due to:

AbsractChannel relies on DefaultChannelPipeline class rather than ChannelPipeline interface
DefaultChannelPipeline is 'effectively final' (all interface methods are implemented as final)

I would suggest either one of the following options:

Change AbstractChannel to depend on ChannelPipeline instead of DefaultChannelPipeline (the same as 'Idea 1' in #7484)
I've found just 2 usages of DefaultChannelPipeline specific methods: estimatorHandle() and invokeHandlerAddedIfNeeded() which can be pulled-up to the interface (with maybe slight redesign)
Relax DefaultChannelPipeline and remove final modifiers
At least add pipeline modification callbacks (like handlerAdded/Removed) to the DefaultChannelPipeline

Background use case: https://github.com/libp2p/jvm-libp2p/issues/39
Closely relates to #7484

While I think in general this is a good idea I don't think we can make this happen with the suggestions you made without breaking the API. Which means this can not happen in 4.1.x

@normanmaurer thanks for prompt response!
May be you give any advice on how to track handlers add/remove with the current API?

what exactly you need to track ? Just when a handler is added and removed ?

Just when a handler is added and removed ?
Yep.
The general idea is always add a tailing handler which should cache all events (which would be dropped by pipeline else) and replay them to a new handler upon addition

@Nashatyrev I didn't digest your problem in detail but might ChannelPipeline::replace help here?

@njhill Nope. I want to be notified on adding/removing handlers to pipeline

@Nashatyrev I see... I mean what you could do is fire user events through the pipeline on each remove / add.


dead link for mri checklist

In this section : https://bids-specification.readthedocs.io/en/latest/modality-specific-files/magnetic-resonance-imaging-data.html#common-metadata-fields
2 dead links:

https://winnower-production.s3.amazonaws.com/papers/977/v4/pdf/977-a-checklist-for-fmri-acquisition-methods-reporting-in-the-literature.pdf
https://winnower-production.s3.amazonaws.com/papers/977/assets/993e199d-6bc3-4418-be3a-f620af1188b7-Parameter_Reporting_V1p3.pdf

winnower is dead and now replaced by authorea
New links should be:

https://d197for5662m48.cloudfront.net/documents/publicationstatus/133946/preprint_pdf/9c16a17d73aaf6c264a269bb9c48def8.pdf

https://www.authorea.com/doi/full/10.15200/winn.143191.17127

Maybe worth having a github action to run on the website once a month:
npm install broken-link-checker -g

blc -rof  \
  --exclude https://doi.org/ \
  --exclude https://twitter.com/ \
  --exclude https://www.loni.usc.edu/research/atlases \
  --exclude https://www.protocols.io/ \
  https://bids-specification.readthedocs.io/en/latest/

tried to exclude some of the false positive
did catch another dead link to the starter kit:
https://github.com/bids-standard/bids-starter-kit/blob/main/templates/README


Implement configuration saving functionality

Add a basic implementation for saving configuration to a file, including error handling for various scenarios. A corresponding test case verifies the functionality.

Codecov Report
Attention: Patch coverage is 58.33333% with 25 lines in your changes missing coverage. Please review.

Project coverage is 93.51%. Comparing base (54d1eaa) to head (9b3032e).
Report is 4 commits behind head on main.

Files with missing lines
Patch %
Lines

pkg/cmd/init.go
37.50%
14 Missing and 1 partial :warning:

pkg/config/svc.go
68.42%
4 Missing and 2 partials :warning:

pkg/cmd/cfg.go
76.47%
3 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #125      +/-   ##
==========================================
- Coverage   94.76%   93.51%   -1.25%
==========================================
  Files          39       39
  Lines        1699     1759      +60
==========================================
+ Hits         1610     1645      +35
- Misses         62       83      +21
- Partials       27       31       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


[collection] add frontend scope

https://jira.sng.sk/browse/MG-53

I'm just writing these down so that I don't forget when we discuss them.

Right now, I believe the editor role has the permission to publish. I'd keep using this role instead of creating a new publisher role
I would also keep role as a singular attribute, so that we don't mix up role-based and permission based access models. The frontend would narrow down permissions for non-administrator roles (e.g. editors)
I think editors could be restricted to a single frontend for now (just to keep things simpler when filtering -- it's a minor sugestion)
When creating (or editing) a new editor user, I am required to specify a frontend
When viewing as an editor, I can only see resources from my frontends
When viewing as an administrator, I can see all resources
When editing as an administrator, I can specify frontends for a resource (have to pick at least one)
When editing as an editor, I'm not able to change frontends of the resource
Only administrators would have the options to change frontends when creating/editing resources (collections, articles, ...). - When creating as an editor, the resource will automatically my frontend
When creating as an administrator, I will be able to specify the frontends (but ['webumenia'] is probably a good default)

Right now, I believe the editor role has the permission to publish. I'd keep using this role instead of creating a new publisher role

As discussed with @mcudrnak it seems that we don't want editors to have permissions to publish.

I would also keep role as a singular attribute, so that we don't mix up role-based and permission based access models. The frontend would narrow down permissions for non-administrator roles (e.g. editors)

I would prefer to switch to multiple roles, because a user should be to edit/publish/import and there is no inherent hierarchy in it.

I think editors could be restricted to a single frontend for now (just to keep things simpler when filtering -- it's a minor sugestion)

Filtering in the admin panel is currently based on ownership of the resource.

When creating (or editing) a new editor user, I am required to specify a frontend

👍

When viewing as an editor, I can only see resources from my frontends

We can also keep the filter based on ownership, I think there'e no need to change this now.

When viewing as an administrator, I can see all resources

👍

When editing as an administrator, I can specify frontends for a resource (have to pick at least one)

👍

When editing as an editor, I'm not able to change frontends of the resource

👍

Only administrators would have the options to change frontends when creating/editing resources (collections, articles, ...). - When creating as an editor, the resource will automatically my frontend

This is a great point, I'm all for it!

When creating as an administrator, I will be able to specify the frontends (but ['webumenia'] is probably a good default)

👍


Javascript client marks state as connected before the handshake response has been received

The .NET client waits for the handshake to complete before marking the connection as usable but this isn't the same for the javascript client.
https://github.com/aspnet/SignalR/blob/f42f4c56e61c5891a851907cf4639575dbbc8df4/clients/ts/signalr/src/HubConnection.ts#L123

I agree it's wrong, but what's the actual customer impact here? Won't the user sends be queued behind the handshake messages and still work?

Not sure, I was reviewing the java client and saw this bug and noticed it was in the javascript client as well. I'm guessing it can result in more failures than necessary since we're exposing the state now in 1.1.

Ok cool. You're right, it's backwards and we should fix it, just wanted to understand it fully. I'll put it in 2.2 for now.

Fixed in #3068


How to set SSL certs for Web side

How am i able to set the SSL certs for the webpage as continually getting.
ERRO http: TLS handshake error from <IP_ADDRESS>:50298: acme/autocert: host "(Censored)" not configured in HostWhitelist  stck="http.(*Server).logf:server.go:3159"

Did you google for the solution before opening this ticket? Creating and SSL certificate can be done for free for a domain ( LetsEncryprt gives free ssl certificates).
If you don't have a domain, try running the bot on http instead of https.
Do not open another issue here, try asking questions in the support server instead.


consensus: Disallow contract revision after proof window opens

Slightly worrisome that I missed this check when porting siad... 👀
This demonstrates why it's insufficient to rely on the fact that core can sync the existing chain: those are all valid blocks. Syncing mainnet tells us nothing about whether core will behave the same as siad with respect to invalid blocks. So we should probably use the fuzzer to pass blocks to both core and siad, checking that either they both accept or both reject.

Can you add a regression test with some examples of good and bad blocks?

done


Display Single Item Profit in logs

Prerequisites

[X] I have searched for existing issues that already include this feature request, without success.

Describe the Feature Request
Currently the message looks like
[12:13:02 PM]  ($$$) Townsend       [328633359765] -- Selling for: 1700

It would be great if the profit of the specific item is displayed beside the selling price. e.g.
[12:13:02 PM]  ($$$) Townsend       [328633359765] -- Selling for: 1700, Profit: 435

Describe the Use Case
More visibility to profits
Describe Preferred Solution
Append the profit number into the log
Describe Alternatives
No response
Additional Information
No response

Added in new release,


"Apața" commune is listed in the drop-down menu

Description:
The commune is listed in the drop-down menu according to the law
Preconditions: the website (https://peviitor-ro.github.io/ui.orase/) is up and runing.
After every step delete the text you typed from the search bar.

Step 1
Type "Apața" in the search bar.
Expected results
The location is listed in the drop-down menu as "Apața, Bacău"


SAK-33408: Dropbox > Group/Section filter visibility is hard-coded to true; should be based on permissions

https://jira.sakaiproject.org/browse/SAK-33408
SAK-14625 introduced a drop down control to filter the list on groups or sections. The boolean value that determines if this control is rendered was hard-coded to true. The correct approach is to conditionally render this control based on if the user has one of two permissions (dropbox.maintain or dropbox.maintain.own.groups). If the user doesn't have either of these permissions, it's not appropriate to display the drop down filter.

Code cleanup commit can be dropped if necessary.


remove unused static nodeType

remove unused static nodeType

What would be the benefit?

no benefit beyond the fact that it's just not used, and deadcode complains about it.
~/go/src/github.com/julienschmidt/httprouter $ deadcode .
deadcode: tree.go:35:1: static is unused

Another option would have been to make root the default nodeType:
const (
	root nodeType = iota // default
	param
	catchAll
)

PING


feat(chain-adapters): require Cosmos SDK bip44Params

Description
This PR does:

accept non-optional bip44Params in buildDelegateTransaction(), buildUndelegateTransaction() and buildRedelegateTransaction(), buildSendTransaction and getAddress. Note that for the two last ones, it is not enforced at type-level yet not to break other areas, and will be enforced in a follow-up PR with bip44Params passed everywhere down the line in lib and web

This PR does not:

make bip44Params required down the line, as there are swapper ramifications which are out of the scope of enforcing bip44Params for Cosmos DeFi opportunities - TBD in follow-up PRs in lib and web

Current dependencies on/for this PR:

main

PR #1021   👈

This comment was auto-generated by Graphite.

closed by https://github.com/shapeshift/lib/pull/1057


Merging index-v7.md

No changes
Issue #1931

Hey @DEBSUBHRO I'm not sure this was intentional but this PR is for your own repo rather than the upstream to https://github.com/umbraco/UmbracoDocs/
If this is on purpose then ignore this message :) Have a great time contributing :+1:

Hey @DEBSUBHRO I'm not sure this was intentional but this PR is for your own repo rather than the upstream to https://github.com/umbraco/UmbracoDocs/
If this is on purpose then ignore this message :) Have a great time contributing 👍

Sorry, Sir. It was unintentional. I'll pull a request on the official site.


[Feature Request] Support --upgrade-package with a specific version

pip-compile --upgrade-package allows you to upgrade a specific package to a specific version instead of the latest version. For example, you can use the following command to update the django package to the latest version and requests to version 2.0.0:
pip-compile --upgrade-package django --upgrade-package requests==2.0.0

Currently, when using uv pip compile --upgrade-package requests==2.0.0, it produces the following error:
❯ uv --version
uv 0.1.10
❯ uv pip compile --upgrade-package requests==2.0.0
error: invalid value 'requests==2.0.0' for '--upgrade-package <UPGRADE_PACKAGE>': Not a valid package or extra name: "requests==2.0.0". Names must start and end with a letter or digit and may only contain -, _, ., and alphanumeric characters.

For more information, try '--help'.

Additionally, pip-compile also supports the following form:
pip-compile --upgrade --upgrade-package 'requests<3.0'

It would be great if uv supports this feature as well.

Seems reasonable, thanks for the clear request :)

I don’t think I fully understand what the semantics of this are, especially for the variant that’s a bound rather than a specific version. What happens if the resolution can’t succeed using the given range / version? Is it ignored? (I’m hesitant to support the variant that takes a bound, it just adds a lot of complexity. Should that not be a constraint provided via a constraint file?)

I was also wondering if constraints could / should be used for this purpose. It does seem weird to provide arbitrary bounds on a single invocation.

In my scenario, this need often arises due to security reasons: the dependency package has discovered security vulnerabilities and needs to be upgraded, but we hope to stay as close as possible to the version already deployed in production in order to avoid introducing faults.

But, should / could that not be provided as a constraint file?

should it? for me I tend to do something like
pip-compile --output-file out.txt in.txt -P package~=X.Y
Where I treat the existing out.txt as the current state of the venv. When I run a command like this, I'm kinda asking a question:

what package if any fits this constraint, given my current venv?

sometimes the answer is yes, with no issues (and write a new out.txt)
sometimes the answer is no, unpin other packages (and fail to write a new out.txt)
and maybe it's "irredeemable constraints" (and fail to write a new out.txt)
Usually my in.txt doesn't usually have version pins (that's what out.txt is for), unless I know for certain new versions would break something. Are you suggesting alternative to using bounded -P args is to temporarily add bounds to in.txt?

Any update on this one?

No updates right now.

What is the expected workflow for upgrading a package?
I'm in the process of migrating pip-tools to uv workflows. Previously, I'd use pip-compile requirements.in --upgrade-package boto3==x, which would take requirements.txt (as constriants) into account and make sure that boto3 is upgraded. If it can't be, it would upgrade necessary transient packages to make boto3 upgradeable to the version I had.
Right now, I use uv pip compile -c requirements.txt requirements.in -P boto3, but it does nothing (there is newer version). If I remove boto3 manually from requirements.txt, it also does nothing (probably because of some transitive deps).

Conceptually, is this the same as --upgrade-package boto3 with boto3==x as a constraint? I'm trying to understand the semantics of --upgrade-package boto3==x.

Not quite, -U allows all requirements in the output to be updated but -P specifically operates the new constraint and updates only the minimal set of requirements in the output to satisfy that additional constraint. If the new constraint can’t be satisfied with existing input constraints, pip compile errors.

Thanks! Though I'm wondering specifically about the use of -P with a version specifier.

Yep, so expectation of -P foo==1.2.3 is:

apply an additional constraint of “foo==1.2.3”
allow only output requirements necessary to meet this constraint to upgrade

Hi, just driving by to mention that this shows up when we try to have dependabot run updates using uv instead of pip-compile so a potential big impact from having it work exactly the same as pip-compile
https://github.com/astral-sh/uv/issues/1964

Dependabot will try to do exactly this
uv pip compile --build-isolation --output-file=requirements.txt \
    --no-emit-index-url \
    --no-annotate \
    --no-header \
    -P attrs==18.0.1 pyproject.toml

and uv complains with
error: invalid value 'attrs==13.0.1' for '--upgrade-package <UPGRADE_PACKAGE>': Not a valid package or extra name: "attrs==13.0.1". Names must start and end with a letter or digit and may only contain -, _, ., and alphanumeric characters.

That’s helpful to know, thanks. We should probably support it then.

It is my first time dearing to even look at a rust codebase but I would like to help. If you have a sample PR in which similar work has occurred, a few pointers or any guidance you think would help me find a way to send a PR for this, I'll take a shot at it. The carbon footprint of dependabot using pip-tools makes this work any effort.

My initial thinking is something like: change Upgrade in package_options.rs to Packages(FxHashSet<Requirement>) rather than Packages(FxHashSet<PackageName>). Then, at some point, iterate over those requirements and add them to constraints, then proceed as usual.


iOS: Increase max simultaneous touches to 32

Increased the max touches for ios to support more than 8 simultaneous touches, because modern ios devices can support more than 8 simultaneous touches.
Bugsquad edit:

Fixes #34424

#34424

Thanks! And congrats for your first merged Godot contribution :tada:

Cherry-picked for 3.6.

Cherry-picked for 3.5.2.


Use Official Google Photos API

New Photos API finally announced!
https://developers.google.com/photos/library/reference/
It's still in preview so somewhat limited, but should be great once fully baked.

Thanks for reporting!
I'll rewrite with new Google Photos API.

https://developers.google.com/photos/library/guides/api-limits-quotas

All media items uploaded to Google Photos using the API are stored in full resolution at original quality. They count toward the user’s storage.

Oops. I want to upload photos as high quality mode (not count toward storage).
I decide not to use this API at present, sorry.

Yeah, like I said above it's limited right now since it's still in preview:

Note: The Google Photos Library API is currently in developer preview. These limits are set low to enable you to try out the API and its features. The limits aren't for production launch, and will be increased once the API enters general availability.

I see.
However, Preview API is not necessary for me, so I have no plan to develop with preview API.

Hi,
Please would you like to reconsider your choice and using official google photo API
I think you can use the high quality mode just by uploading photos less than 16 megapixels.
Just testing photo weight and resize it before uploading.
Need help because your script not working for me anymore.

I tried upload 400 images (which size is 651 x 1024 pixels, it's less than 16MP) with "Original quality" option.

BEFORE

AFTER

(Screenshot is Japanese.) It reduce Google Drive quota by 0.04GB.
I would like to use Google Drive quota via "High quality" option.
So, I have no plan to use Google Photos API.
If you want to use Google Photos API, please consider other cli tools.

LIST OF OTHER TOOLS USING OFFICIAL API

nmrshll/gphotos-uploader-cli: Command line tool to mass upload media folders to your google photos account(s) (Mac OS / Linux)
mholt/photobak: Back up your content from Google Photos
int128/gpup: A command to upload photos and movies to Google Photos Library
eshmu/gphotos-upload: Simple but flexible script to upload photos to Google Photos and add to a particular album. Useful if you have photos in a directory structure that you want to reflect as Google Photos albums.

Hi Masahiro,
Thank you very well for looking for.
I would like use "High quality" option too.
My only solution is to use flickr by it's with lower options.
Thanks again

I have seen that it is possible to upload photos with "Original Quality" and then use the Recover storage (https://photos.google.com/settings) to convert them


Question around state colors when state contains a space character

As part of your documetation I see the following
type: custom:history-explorer-card
stateColors:
  sensor.Dry: tan
  sensor.Wet: green

Works super well for most cases, but I'm trying to set the state color based off of an input select, which contains the following options:

Off
'Heat up'
'Keep warm'
'Cool down'

Wondering how (if possible) I can set the colors for these, without changing the values themselves.  I've tried input_select.Heat Up input_select.['Heat Up'] and input_select.Heat+Up, but no luck.  Guessing it might not be possible, but can't hurt to ask 🤷 🤞
Thanks!

stateColors:
  input_select.Heat up: red

or
stateColors:
  'input_select.Heat up': red

will both work. Careful about case (Heat up vs Heat Up). Case is important.

Does this solve your problem ? Can this issue be closed ?

No worries, thanks for confirming.


Amides in macrocycles

It seems as thought amides are not held to a planar geometry when they are part of a macrocycle.  6 and smaller member rings seem to be fine, but 7 and up give me rotated amide bonds unless I use --rigid_macrocycles while preparing ligand pdbqt files.
Is this a known issue?  I tried using the --rigidify_bonds_smarts flag while preparing ligands to rigidify all amides (which should be the default behavior I thought), but that flag gave me trouble.
Any work arounds?

Amide bonds are made rotatable only when the amide nitrogen has two non-hydrogen substituents and those substituents are different. While this lead to non-planar amides, which is bad, it allows both planar conformers to be sampled. Whether or not the amide N-C bond is part of a macrocycle does not affect the rotatable/non-rotatable status. To always keep amides rigid, use:
--rigidify_bonds_smarts "O=[CX3][NX3]" --rigidify_bonds_indices 2 3
If this doesn't work, or if I misunderstood the problem, please provide an example so I can reproduce the issue.


[CI] Update Multi Platform build and Release workflow

Current Behavior

Currently, the multiplatform.yml file is sending unwanted build arguments to docker build process because of which release tag and commit_sha are not being passed over to the image and hence the version of meshery adapter are not visible on-hovering adapters chips on Meshery UI Dashboard.
Desired Behavior

This would be fixed when correct build args are passed to the docker build step inside multiplatform workfow.
Required Args:

VERSION
GIT_COMMITSHA

Check this commit for reference:
https://github.com/meshery/meshery-consul/commit/446ad170c938c9bfe22e6e8710459d63395b9148
related to: https://github.com/meshery/meshery/issues/6245

Contributor Guides and Resources

📝 Meshery Adapters Spreadsheet
🛠 Meshery Build & Release Strategy
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Hi , I would like to work on this issue. Please assign it to me . Thanks :)


PCAP Conversion not working

Hi,
I have set the PCAP Analyzer in my Splunk enterprise software. After setting up PCAP file location, I could see that the CONF file inputs.conf has been created. However, PCAP conversion is not working and there are no new files created inside PCAPConverted and PCAPcsv folder. Any idea why this might be happening ?
With thanks ,
Mo

New Version 5.0.0 is online on the splunkbase.
For troubleshooting there is also a new sourcetype defined sourcetype=pcap:analyzer:debug which can help you to understand where your problem is.


docs: codebase architecture and general documentation

Closes #450

This is looking good.
Can you add a section on Projectless validation and a paragraph on "claiming files when the project load fails".

Added !


feat: support dynamic components

feat: support dynamic components using <component is="...">
test: dynamic component render fn

fixes #114

Codecov Report

Merging #119 (12b7abe) into master (039ee98) will increase coverage by 0.26%.
The diff coverage is 88.67%.

@@            Coverage Diff             @@
##           master     #119      +/-   ##
==========================================
+ Coverage   55.20%   55.47%   +0.26%
==========================================
  Files          82       82
  Lines        5472     5507      +35
  Branches     1946     1960      +14
==========================================
+ Hits         3021     3055      +34
- Misses       2451     2452       +1

Impacted Files
Coverage Δ

...es/compiler-tsx/src/transforms/transformElement.ts
65.85% <83.33%> (+2.13%)
:arrow_up:

packages/compiler-tsx/src/index.ts
95.18% <100.00%> (+1.06%)
:arrow_up:

...features/completions/TemplateCompletionProvider.ts
58.38% <100.00%> (ø)

...iagnostics/InferredComponentDiagnosticsProvider.ts
75.00% <0.00%> (+2.50%)
: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 039ee98...12b7abe. Read the comment docs.


Vc/add kv to nats

This adds a lightweight wrapper around the NATS KV functionality to facilitate the sorts of access Firmware-Install needs.

I'm going to do a deep refactor here taking into account the feedback so far and I'll re-open a new PR. I don't think maintaining this partial-work in the history is useful, so closing this allows a cleaner review next time.


error

hi
can you help me please
i get this error. i have tryied so many times but i dont know why. i am using windows 11 with python 312
C:\Python312>python.exe AtoZ-Bot.py
Traceback (most recent call last):
File "C:\Python312\AtoZ-Bot.py", line 177, in
main()
File "C:\Python312\AtoZ-Bot.py", line 165, in main
browser.login()
File "C:\Python312\AtoZ-Bot.py", line 53, in login
uname = self.driver.find_element(By.XPATH, "//input[@id='login']")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python312\Lib\site-packages\selenium\webdriver\remote\webdriver.py", line 748, in find_element
return self.execute(Command.FIND_ELEMENT, {"using": by, "value": value})["value"]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Python312\Lib\site-packages\selenium\webdriver\remote\webdriver.py", line 354, in execute
self.error_handler.check_response(response)
File "C:\Python312\Lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 229, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: no such element: Unable to locate element: {"method":"xpath","selector":"//input[@id='login']"}
(Session info: chrome=129.0.6668.71); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#no-such-element-exception
Stacktrace:
GetHandleVerifier [0x00FA6AB3+25587]
(No symbol) [0x00F39C54]
(No symbol) [0x00E32113]
(No symbol) [0x00E76F62]
(No symbol) [0x00E771AB]
(No symbol) [0x00EB7852]
(No symbol) [0x00E9ABE4]
(No symbol) [0x00EB5370]
(No symbol) [0x00E9A936]
(No symbol) [0x00E6BA73]
(No symbol) [0x00E6C4CD]
GetHandleVerifier [0x01284C63+3032483]
GetHandleVerifier [0x012D6B99+3368153]
GetHandleVerifier [0x01038F62+624802]
GetHandleVerifier [0x010407DC+655644]
(No symbol) [0x00F4260D]
(No symbol) [0x00F3F6D8]
(No symbol) [0x00F3F875]
(No symbol) [0x00F31CA6]
BaseThreadInitThunk [0x76EA7BA9+25]
RtlInitializeExceptionChain [0x77DDC11B+107]
RtlClearBits [0x77DDC09F+191]

Change the URL in the code to: "https://atoz-login.amazon.work/"

@Lauro112 I updated the code. Itshould be working again.

Hi
I am not able to do it 😊
Can i conatact you in private to help me
Thanks

Hi I am not able to do it 😊 Can i conatact you in private to help me Thanks

Did you follow me the updated instructions?
Send me a DM

I can't send you DM

I can't send you DM

Did you folllow the updated instructions?
What is the issue/error?


Events firing in different order on iOS and Android

I have a component where I use snapPoints and alertAreas to rearrange Interactable.Views via drag and drop. When I drag a component and then release it to snap, the events fire in the following order:
iOS:

onDrag   with {state: 'end'}
onAlert   with {'alertAreaOverSnapPoint': 'enter'}
onSnap   with {index: 'snapPointInAlertArea' }

Android:

onSnap   with {index: 'snapPointInAlertArea' }
onDrag   with {state: 'end'}
onAlert   with {'alertAreaOverSnapPoint': 'enter'}

The order in iOS makes sense to me. Do you have any idea what causes the events to fire in a different order based on the OS?

I put in a pull request (#103) that fixes the order of onSnap and onDrag(end).


Can I run U-Mamba on Win 11 instead of Ubuntu?

as title

hi @baoyi-A ,
Thanks for your question. Unfortunately, we didn't have a win11 workstation to test it. Welcome to pull requests.


look me

query := DB.Table(TP+"total").Select(TP+"total.id,sum(day_price) as total_price").
Joins("left join "+TP+"store as store on store.id = "+TP+"total.store_id").
Joins("left join "+TP+"channel as cha on cha.id = "+TP+"total.channel_id").
Where(TP+"total.day_time between ? and ?", TimeStart, TimeEnd).
Having("total_price>0").
Group(TP + "total.store_id," + TP + "total.is_valid," + TP + "total.day_time,cha.id").
Count(&info)
if query.Error != nil && query.Error != gorm.ErrRecordNotFound {
log.Error(query.Error)
}
// SELECT count() FROM ( SELECT count() as name  FROM pro_total left join pro_store as store on store.id = pro_total.store_id left join pro_channel as cha on cha.id = pro_total.channel_id WHERE  (pro_total.day_time between '1545235200' and '1545753600') GROUP BY pro_total.store_id,pro_total.is_valid,pro_total.day_time,cha.id ) AS count_table HAVING (total_price>0)
tell me why?

Tell you went what @bingoladen? Please add more detail or issue will be closed.

'count'and'having' appear in the wrong place...
SELECT count() FROM ( SELECT count() as name FROM pro_total left join pro_store as store on store.id = pro_total.store_id left join pro_channel as cha on cha.id = pro_total.channel_id WHERE (pro_total.day_time between '1545235200' and '1545753600') GROUP BY pro_total.store_id,pro_total.is_valid,pro_total.day_time,cha.id ) AS count_table HAVING (total_price>0)

Please provide what SQL you expect to see. Please edit your comments to use the code wrapper formatting.

the between and seems to be a bug to gorm


Git LFS not pulling

While testing the downloader I noticed that it doesn't pull LFS. Would be great if there was an option to do so.

I’m afraid, I’ve not enough time to add some features. But you can contribute, this’s open source project.


Bug when using two characteristics with the same identifier

When I create two different characteristics with the same 'identifier'
BLEUUID((uint16_t)0x2A3D
it looks like the onWrite handlers are not assigned correctly. Both values report
"SSID: BLE received on ESP32/write : %s",
but the passwordhandler should respond with
"Password: BLE received on ESP32/write: %s". It worked one time, but I didn't even change anything, I just rebooted the ESP32.
Using two different characteristics fixes this, but is there any way I can use two (or more) of the same characteristic?
BLEDevice::init(name);
	BLESecurity *pSecurity = new BLESecurity();
	pSecurity->setAuthenticationMode(ESP_LE_AUTH_REQ_SC_MITM_BOND);
	pSecurity->setCapability(ESP_IO_CAP_OUT);
	pSecurity->setInitEncryptionKey(ESP_BLE_ENC_KEY_MASK | ESP_BLE_ID_KEY_MASK);
	BLEServer *pServer = BLEDevice::createServer();
	BLEDevice::setEncryptionLevel(ESP_BLE_SEC_ENCRYPT);
		// Required in authentication process to provide displaying and/or input passkey or yes/no butttons confirmation
	BLEDevice::setSecurityCallbacks(new GenericSecurity());
	// https://www.bluetooth.com/specifications/gatt/services
	BLEService *pService = pServer->createService(BLEUUID((uint16_t)0x180A));
	// https://www.bluetooth.com/specifications/gatt/characteristics
	BLECharacteristic *ssidCharacteristic = pService->createCharacteristic(
		BLEUUID((uint16_t)0x2A3D),
		BLECharacteristic::PROPERTY_WRITE);

	BLECharacteristic *passwordCharacteristic = pService->createCharacteristic(
		BLEUUID((uint16_t)0x2A3D),
		BLECharacteristic::PROPERTY_WRITE);

	ssidCharacteristic->setAccessPermissions(ESP_GATT_PERM_WRITE_ENCRYPTED);
	ssidCharacteristic->setCallbacks(new BleCallbackSSID());

	passwordCharacteristic->setAccessPermissions(ESP_GATT_PERM_WRITE_ENCRYPTED);
	passwordCharacteristic->setCallbacks(new BleCallbackPassword());
	// https://www.bluetooth.com/specifications/gatt/descriptors
	BLE2902 *ssid2902Descriptor = new BLE2902();
	BLE2902 *password2902Descriptor = new BLE2902();
	ssidCharacteristic->addDescriptor(ssid2902Descriptor);
	passwordCharacteristic->addDescriptor(password2902Descriptor);

// SSID
void BleCallbackSSID::onWrite(BLECharacteristic *pCharacteristic)
{
    std::string msg = pCharacteristic->getValue();
    ESP_LOGI(tag, "SSID: BLE received on ESP32/write: %s", msg.c_str());
}

void BleCallbackSSID::onRead(BLECharacteristic *pCharacteristic)
{
    std::string msg = pCharacteristic->getValue();
    ESP_LOGI(tag, "BLE read: %s, %i", msg.c_str(), msg.length());
}

// Password
void BleCallbackPassword::onWrite(BLECharacteristic *pCharacteristic)
{
    std::string msg = pCharacteristic->getValue();
    ESP_LOGI(tag, "Password: BLE received on ESP32/write: %s", msg.c_str());
}

void BleCallbackPassword::onRead(BLECharacteristic *pCharacteristic)
{
    std::string msg = pCharacteristic->getValue();
    ESP_LOGI(tag, "BLE read: %s, %i", msg.c_str(), msg.length());
}

It may be issue with your client app. If you have 2 characteristics with the same UUID it requires to access characteristics with handle, but your client app can access it with UUID and sends value randomly.

For now I'll stick to 2 different UUID's, when I've written my own client I'll report back. My client being buggy could definitely be the case.

It may be issue with your client app. If you have 2 characteristics with the same UUID it requires to access characteristics with handle, but your client app can access it with UUID and sends value randomly.

How to write data to characteristics with handle?