Add Set/Get viewport

Maybe you can add this:
--- sdl2.f90.orig       2019-06-21 17:45:31.179456500 +0200
+++ sdl2.f90    2019-07-07 18:33:29.132599700 +0200
@@ -1698,7 +1698,7 @@
             integer(kind=c_int)                    :: sdl_render_draw_point
         end function sdl_render_draw_point

-        ! int SDL_RenderDrawPoint(SDL_Renderer *renderer, const SDL_Point *points, int count)
+        ! int SDL_RenderDrawPoints(SDL_Renderer *renderer, const SDL_Point *points, int count)
         function sdl_render_draw_points(renderer, points, count) bind(c, name='SDL_RenderDrawPoints')
             import :: c_int, c_ptr, sdl_point
             implicit none
@@ -2046,6 +2046,25 @@
             type(c_ptr), intent(in), value :: renderer
         end subroutine sdl_render_present

+        ! int SDL_RenderSetViewport(SDL_Renderer* renderer, const SDL_Rect* rect)
+        function sdl_render_set_viewport(renderer, rect) &
+             bind(c, name='SDL_RenderSetViewport')
+          import :: c_int, c_ptr, sdl_rect
+          implicit none
+          type(c_ptr),    intent(in), value :: renderer
+          type(sdl_rect), intent(in)        :: rect
+          integer(kind=c_int)               :: sdl_render_set_viewport
+        end function sdl_render_set_viewport
+
+        ! void SDL_RenderGetViewport(SDL_Renderer* renderer, SDL_Rect* rect)
+        subroutine sdl_render_get_viewport(renderer, rect) &
+             bind(c, name='SDL_RenderGetViewport')
+          import :: c_int, c_ptr, sdl_rect
+          implicit none
+          type(c_ptr),    intent(in), value :: renderer
+          type(sdl_rect), intent(inout)     :: rect
+        end subroutine sdl_render_get_viewport
+
         ! void SDL_RestoreWindow(SDL_Window *window)
         subroutine sdl_restore_window(window) bind(c, name='SDL_RestoreWindow')
             import :: c_ptr

Thanks (also for the Credits!)

Ooops.. forgot to say that, in your modules, for each routine interfaced, you add something like this:
...
import :: BLA BLA BLA
implicit none
...

I think just
...
import :: BLA BLA BLA
...

works if implicit none is in the module after the use(s)...
Just to make the file a bit smaller...

Thank you. Has been added with commits a3dcbca5a2339aa096305d14f5e32537ddf24dab and 524e5e40efda7ad8f6856b5ce565df2bf7f16976.

Thank you very much!
(Maybe we can close this...)


ESP32-C6 support status (IDFGH-9013)

ESP-IDF v5.1, currently in development, will include initial support for ESP32-C6 chip.
For each feature, the status (Supported/Not supported) is given. An internal issue reference (such as "IDF-1234") is listed at the end of the feature description to help us keep this list up to date.
This list will be updated as the support for ESP32-C6 is being developed.
Wi-Fi

[x] 802.11bgn, HT40 – Supported
[x] 802.11ax: 20MHz-only non-AP mode – Supported
[x] Station, SoftAP, sniffer mode – Supported
[x] UL/DL OFDMA (26/52/106/242 tone) – Supported
[x] DL MU-MIMO，DL MU-MIMO within OFDMA – Supported
[x] HE ER (HE Extended Range), DCM and ESP LR (ESP Long Range) – Supported
[x] BSS Color – Supported
[x] CSI (Channel State Information) – Supported
[x] ESP-NOW – Supported
[x] ESP-WiFi-Mesh – Supported
[x] ESP-Touch v1/v2 – Supported
[x] Wi-Fi Security – Supported
[x] DPP (Device Provisioning Protocol) – Supported
[x] Network-assisted roaming using 802.11k (Radio Measurements), 802.11v (BTM) specification and 802.11r (Fast BSS Transition) – Supported
TWT

[x] Individual TWT – Supported
[ ] Broadcast TWT – Not supported (WIFI-5215)

[x] Advanced DTIM Sleep – Supported
[x] Power Save: modem sleep, light sleep – Supported
[ ] FTM (Fine Time Measurement)  – Not supported  (WIFI-5144)

Coexistence

[x] Coexistence of Wi-Fi and Bluetooth LE - Supported
[x] Coexistence of Wi-Fi and 802.15.4 - Supported
[x] Coexistence of Bluetooth LE and 802.15.4 - Supported
[x] External coexistence - Supported

Bluetooth LE

[x] Bluetooth 5 Controller (Bluetooth 5.3 Certified) - Supported
[x] Bluedroid Host - Supported
[x] NimBLE Host - Supported
[x] ESP-BLE-MESH - Supported
[ ] BLE Modem Sleep and Light Sleep - Not supported（IDF-6528）
[x] Bluetooth Power Control - Supported
[x] HCI - Supported

802.15.4

[x] 802.15.4 Mac - Supported
[x] 802.15.4 CSL - Supported

Thread

[x] Thread FTD/MTD - Supported
[x] Thread RCP - Supported
[x] Thread Border Router - Supported

Zigbee

[x] Zigbee 3.0 Home Automation - Supported
[x] Zigbee RCP - Supported
[x] Zigbee Gateway - Supported

Peripherals

ADC

[ ] ADC Calibration - Not supported (IDF-5312)
[x] ADC continuous mode driver - Supported
[x] ADC oneshot mode driver - Supported

[x] Dedicated GPIO driver - Supported
Ethernet driver

[x] SPI Ethernet driver - Supported

[x] Event Task Matrix - Supported
[x] GDMA - Supported
[x] GPIO driver - Supported

[x] Glitch Filter - Supported
[x] RTC IO driver - Supported

[x] GPIO sigma delta driver - Supported
GPSPI

[x] SPI Master driver - Supported
[x] SPI Slave HD driver - Supported
[x] SPI Slave driver - Supported

[x] GPTimer driver - Supported
I2C

[x] I2C master driver - Supported
[x] I2C slave driver - Supported

[x] I2S driver - Supported

I2S PDM rx mode
I2S PDM tx mode
I2S STD mode
I2S TDM mode

[x] LCD driver - Supported

I2C LCD driver
SPI LCD driver

[x] LEDC driver - Supported

[x] Gamma Curve Generation - Supported

[x] MCPWM driver - Supported
[x] PCNT driver - Supported
[x] Parallel IO driver - Supported
[x] RMT driver - Supported
SD/SDIO/MMC driver

[x] SDSPI Host driver - Supported

[x] SDIO Slave driver - Supported
[x] SPI Flash driver - Supported
Systimer driver

[x] Esptimer implementation over systimer - Supported
[x] OS tick port over systimer - Supported

[x] TWAI driver - Supported
[x] Temperature Sensor driver - Supported
UART

[x] UART FIFO mode driver - Supported
[ ] UHCI (UART DMA mode) driver - Not supported (IDF-5337)

[x] USB Serial JTAG - Supported
[x] memory copy by DMA - Supported

Power management

[x] Auto Light Sleep - Supported
[x] Deep Sleep - Supported
[x] Dynamic Frequency Switch - Supported
[x] Light Sleep - Supported

Security Features

[x] AES accelerator - Supported
[x] Digital Signature driver - Supported
[x] ECC accelerator - Supported
[x] Flash encryption - Supported
[x] HMAC driver - Supported
[ ] RNG - Not supported (IDF-5352)
[x] RSA hardware accelerator driver - Supported
[x] SHA accelerator - Supported
[x] Secure boot - Supported
Trusted Execution Environment

[x] Access Permission Management - Supported
[x] TEE Controller - Supported

System Features

[x] Brownout Detector - Supported
[x] Cache - Supported
[x] Efuse controller driver - Supported
[x] MMU - Supported
MSPI

[ ] MSPI tuning (Flash & PSRAM DDR and/or over 80 MHz) - Not supported (IDF-5343)
[ ] SPI Flash auto suspend - Not supported (IDF-5344)

[ ] Timeout Module (New) - Not supported (IDF-5814)

Note: Nested features can be considered as supported, if the parent feature is shown as "Supported", and it's not explicitly mentioned as "Not supported".

Update 2023/01/02: added Wi-Fi features, ADC oneshot and continuous mode, RTC IO, SPI Master, SDSPI Host drivers.

Update 2023/01/13: added BLE features, Brownout Detector support

Update 2023/01/25: added HMAC, Digital Signature, SDIO slave, Bluetooth Power Control.

Update 2023/02/20: added RSA, Secure Boot, Flash Encryption, APM.

I've confirmed wolfSSL encryption libraries work with the ESP-IDF v5.1 and the ESP32-C6. It is operational on my fork and I plan to submit a PR soon to address https://github.com/wolfSSL/wolfssl/issues/6163 for full support.

Update 2023/03/15: added Coexistence of Wi-Fi and Bluetooth LE, and Coexistence of Bluetooth LE and 802.15.4

Update 2023/03/15: added Coexistence features and Power save features.

Is it be possible to ZigBee / Matter, BLE and WiFi coexist?

Will it be possible ZigBee / Matter, BLE and WiFi to coexist?

Wondering this too about Zigbee and Thread? However as I understand it, Zigbee and Thread will intially be mutually exclusive, so can not currently use Zigbee and Thread simultaneously (at the same time)?
Not sure if feasable nativly on a single-core MCU but perhaps in future Zigbee and Thread could instead be timeshifted/timesliced to run concurrently using RCP (Radio Co-Processor) architecture design in where the Zigbee and Thread libraries/processes are off-loaded from the 802.15.4 SoC radio SoC to a host computer?
https://openthread.io/platforms/co-processor
That is anyway how Silicon Labs and some others support using two different protocols at the same time on its 802.15.4 SoC radios.
PS: Off-topic but FYI; Home Assistant has experimental add-on for a such Zigbee and Therad implementation using off-loading running concurrently on their Silicon Labs based Home Assistant SkyConnect USB dongle with 802.15.4 SoC radio (and Home Assistent Yellow onboard radio based on the same 802.15.4 SoC radio SoC) in RCP mode.

Hello,
Unfortunately I am not able to use my ESP32-C6 DEVKITC-1. That is because I am not able to install ESP-IDF V5.0.1 which is the only version that supports C6 targets. Please find attached the error message and the log file.
Anyone could give support please?
BR
ADH Setup Log 2023-03-21 #001.txt

Hello, Unfortunately I am not able to use my ESP32-C6 DEVKITC-1. That is because I am not able to install ESP-IDF V5.0.1 which is the only version that supports C6 targets. Please find attached the error message and the log file.
Anyone could give support please? BR
ADH Setup Log 2023-03-21 #001.txt

SDK 5.1 supports esp32c6, but it is not ready. You can use master brach for start of project to use esp32c6, but you will need to make some manuals manupulations to add for examples esp32c6 support in eclipse (as example).

Hello, Unfortunately I am not able to use my ESP32-C6 DEVKITC-1. That is because I am not able to install ESP-IDF V5.0.1 which is the only version that supports C6 targets. Please find attached the error message and the log file.
Anyone could give support please? BR
ADH Setup Log 2023-03-21 #001.txt

SDK 5.1 supports esp32c6, but it is not ready. You can use master brach for start of project to use esp32c6, but you will need to make some manuals manipulations to add for examples esp32c6 support in eclipse (as example).

Thanks for you fast response @RuslanSpartak . would you kindly send me the link to the master branch with the needed manual manipulations for C6? do you have any idea on the date SDK 5.1 will begin supporting esp32c6, anytime soon?
BR
Achraf

Hello, Unfortunately I am not able to use my ESP32-C6 DEVKITC-1. That is because I am not able to install ESP-IDF V5.0.1 which is the only version that supports C6 targets. Please find attached the error message and the log file.
Anyone could give support please? BR
ADH Setup Log 2023-03-21 #001.txt

SDK 5.1 supports esp32c6, but it is not ready. You can use master brach for start of project to use esp32c6, but you will need to make some manuals manipulations to add for examples esp32c6 support in eclipse (as example).

Thanks for you fast response @RuslanSpartak . would you kindly send me the link to the master branch with the needed manual manipulations for C6? do you have any idea on the date SDK 5.1 will begin supporting esp32c6, anytime soon? BR Achraf

I'm also a customer that uses ESP32C6 module . You can get master branch from github. Which IDE you use, depends on that I can try to help you. About SDK5.1 I really don't know as I'm not emedded engineer of espressif.

I use IAR. I have no problem to use another one.
all I need is to flash my C6 and send commands to connect the C6 wifi to an access point. I don't really need to developpe any SW or FW.
thanks again for your kind support.

I use IAR. I have no problem to use another one. all I need is to flash my C6 and send commands to connect the C6 wifi to an access point. I don't really need to developpe any SW or FW. thanks again for your kind support.

Are you able to install master branch instead of 5.0.1?

Hello @rotilho, @Hedda, @loraahd and @RuslanSpartak,
this issue tracks only ESP32-C6 support status and for better visibility of update comments specifying what support was added, I had to hide your comments.
If you have any questions or need support, please feel free to open new issues here on GitHub or on esp32.com forum. Our developers and support team will be happy to help you.
Thank you for understanding,
Tomas

Don't know how to install it. Do you have a link to it?
On Tue, Mar 21, 2023, 12:11 RuslanSpartak @.***> wrote:

I use IAR. I have no problem to use another one. all I need is to flash my
C6 and send commands to connect the C6 wifi to an access point. I don't
really need to developpe any SW or FW. thanks again for your kind support.
Are you able to install master branch instead of 5.0.1?
—
Reply to this email directly, view it on GitHub
https://github.com/espressif/esp-idf/issues/10423#issuecomment-1477650499,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A6UER62YO65ITOHZCK4VAWTW5GEFHANCNFSM6AAAAAATFTD2ZY
.
You are receiving this because you commented.Message ID:
@.***>

Update 2023/03/15: added Coexistence of Wi-Fi and Bluetooth LE, and Coexistence of Bluetooth LE and 802.15.4

Hi, can Wi-Fi, BLE and 802.15.4 coexist?

Update 2023/03/15: added Coexistence of Wi-Fi and Bluetooth LE, and Coexistence of Bluetooth LE and 802.15.4

Hi, can Wi-Fi, BLE and 802.15.4 coexist?

hi @mrninhvn , coexist of three modems together is not scheduled yet

Hi @Espressif-liuuuu does it mean that once the modems will coexist together we could have a Thread Border Router just with the ESP32-C6?

@a-d-r-i-a-n-d please see https://github.com/espressif/esp-thread-br/issues/9#issuecomment-1506402241 and leave a comment there if you have further questions regarding the Border Router solution.

Update 2023/04/18:  802.15.4 CSL, Thread Border Router, Parallel IO driver, LEDC gamma curve, systimer, cache and MMU are now supported.

Hello,
I am not able to use my ESP32-C6 DEVKITC-1. That is because ESP-IDF V5.0.1 still does not supports C6 targets. Please find attached the error message.
Is there an upgrade that support C6 targets? any workaround?

BR,

@loraadh Espressif have stated that support for the C6 will debut with ESP-IDF 5.1. You can check out the release/5.1 branch and it will already work pretty well with the C6.

@loraadh Espressif have stated that support for the C6 will debut with ESP-IDF 5.1. You can check out the release/5.1 branch and it will already work pretty well with the C6.

thanks @mickeyl
is the 5.1 version the same as the master version?
BR

is the 5.1 version the same as the master version?

No, 5.1 is the "release/v5.1" branch -> https://github.com/espressif/esp-idf/tree/release/v5.1

is the 5.1 version the same as the master version?

No, 5.1 is the "release/v5.1" branch -> https://github.com/espressif/esp-idf/tree/release/v5.1
PS: Also follow espressif/arduino-esp32#7852 and espressif/arduino-esp32#7713 for updates on ESP-IDF 5.1 and ESP32-C6

thanks @Hedda,
in previous versions I used to do the installations via the online installer: https://dl.espressif.com/dl/esp-idf/?idf=4.4
Version ESP-IDF 5.1 is still not supported by that installer. Is there a user guide on how to install, flash/upload, and command the c6?
thanks
BR

For end-user questions and want support then you should post them to the esp32.com forum instead -> https://www.esp32.com

Might be off-topic, but why c6's riscv trace support isn't on this table?

@Headcrabed indeed we did not include CPU Trace support into the plan, as we saw relatively few people using the similar feature on the previous Xtensa chips. It will get supported, eventually, especially if more users express interest.

Why was https://github.com/espressif/esp-idf/issues/10423#issuecomment-1549680635 marked as being offtopic?

I Cant see the option to choose the ESP32-C6 Dev Kit in the very first VS code blink example. I am used to Program Texas Instruments And Microchip devices with C compilers and the approach is so different. It is my first time attempting with a ESP device that I just bought, so far this issue is really unfriendly already.. any help on this?

@Renatomusica it is possible that the version of IDF you are using is one which doesn't contain C6 support. (For example, v5.0.x doesn't support C6). Please check that you have v5.1-rc1 installed, as that's the latest release candidate of v5.1. If you still run into an issue with VS Code after installing v5.1-rc1, please open an issue here: https://github.com/espressif/vscode-esp-idf-extension/issues

@Renatomusica it is possible that the version of IDF you are using is one which doesn't contain C6 support. (For example, v5.0.x doesn't support C6). Please check that you have v5.1-rc1 installed, as that's the latest release candidate of v5.1. If you still run into an issue with VS Code after installing v5.1-rc1, please open an issue here: https://github.com/espressif/vscode-esp-idf-extension/issues

Thank you I downloaded v5.1-rc1 and i can see device listed..
Now trying to build an example i run into all kinds of problems like asking for container location (i already set the folder where in this case the blink example should be set )  and also this
"Unable to determine what CMake generator to use. Please install or configure a preferred generator, or update settings.json, your Kit configuration or PATH variable." message that i tried to solve generating files from CMake extension but not working... do you have any source of guidance in order to accurately build an example w this system?

TWAI is marked as supported but actually only 1 of 2 TWAI controllers is supported.

updated coexistence part, sorry since external coexistence is not supported in v5.1

With release-v5.1 or master I see 10-15ºC with the temperature sensor example, at a room at about 25ºC.

updated coexistence part, sorry since external coexistence is not supported in v5.1

Is there any other progress update for C6?
Last update was 2 Months ago (https://github.com/espressif/esp-idf/issues/10423#issuecomment-1512679789),
I'm surprised the only update here is to mention that external coexistence is not supported.
@igrr

@AxelLin Follow the status of ESP-IDF v5.1 as that upcoming will be first  ESP-IDF version to have initial support for the ESP32-C6:
https://github.com/espressif/arduino-esp32/issues/7713
https://github.com/espressif/arduino-esp32/issues/7852
Espressif ESP-IDF v5.1 RC 1 (ESP-IDF version 5.1 Release Candidate 1) was tagged in this GiHub repository just two weeks ago:
https://github.com/espressif/esp-idf/releases
https://github.com/espressif/esp-idf/releases/tag/v5.1-rc1
As both ESP32-C6 and ESP32-H2 are at the very top of the list of major features in that I think that you can safely assume that when the final ESP-IDF v5.1 release (i.e. "GA" release for "General Availability") is released as available then it will be officially supported by Espressif in that ESP-IDF v5.1 release. That is at least the industry standard for most software release life cycles:
https://en.wikipedia.org/wiki/Software_release_life_cycle

ADC Calibration is now also supported on ESP32-C6.
The remaining features which aren't yet marked as supported will not be available in IDF v5.1 release. We will update the support plan for the remaining features before the next v5.1.1 release. In the meantime, if your project requires any of the features not listed as supported, please contact Espressif via business support channels.

Are there any plans to support also the second twai controller any time in the near future?

With release-v5.1 or master I see 10-15ºC with the temperature sensor example, at a room at about 25ºC.

@nunojpg Please create a new issue to track this.

Missing from feature list: OpenThread Sleepy End Device (SED)

updated:

[x] External coexistence - Supported
[x]  BLE Modem Sleep and Light Sleep - Supported

Sorry if I am repeating the same question as already asked by 2 other guys,
What are your plans for implementing the drivers for 2nd TWAI (TWAI1) port on ESP32C6? This could be a breakthrough in my opinion if 2nd TWAI port gets working sooner.

@embenix sorry for confusing you, a new suit of TWAI driver is coming, 2nd TWAI will supported on new driver in new version of IDF at end 2023. sorry for long time waiting.

Hi, Do you have any plan for the coexistence of Wifi-BLE-Zigbee?

Hi,
Not really. Most likely we will be using the BLE. Since now we are at product development stage, we want to have the option of having more than one communication protocol, in case we want to go for another option. You  are very welcome if you have any suggestion.
Kind regards,
Israel Mekonnen
From: @.>
Sent: 28 September 2023 10:11
To: @.>
Cc: Mekonnen @.>; @.>
Subject: Re: [espressif/esp-idf] ESP32-C6 support status (IDFGH-9013) (Issue #10423)
Hi, Do you have any plan for the coexistence of Wifi-BLE-Zigbee?
—
Reply to this email directly, view it on GitHubhttps://github.com/espressif/esp-idf/issues/10423#issuecomment-1738601770, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BAUCJCTJFTTAYPFDYVM7QADX4UPKTANCNFSM6AAAAAATFTD2ZY.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

Please refer to espressif/arduino-esp32#7713 regarding the BLE unified provisioning, so that the issue can be fixed. Thanks.

@igrr @jack0c
Do you have update for the upcoming 5.1.2 release?
Do you have target timeline for feature complete? (Only 6 items are not yet supported)

Hi,
I would like to know when the support for the LP UART will be available because I don't see the code in the v5.2 but only on the master branch.
Thanks

Above it says I2S support is complete, but not working for me in current dev branch

Happy to announce wolfSSL Hardware Acceleration Support for the ESP32-C6!  See wolfSSL #6990.
I also have a wolfSSL Managed Component update in the works that will include this change once the PR is merged. The wolfSSH and wolfMQTT Espressif Managed components be added soon as well.

@igrr @jack0c
Do you have update for the upcoming 5.1.2 release? Do you have target timeline for feature complete? (Only 6 items are not yet supported)

The features supported in v5.1.2 were updated.
Here are some comments for the features not supported:
Broadcast TWT – Not supported (WIFI-5215) - Still WIP, will support in IDF v5.3.
FTM (Fine Time Measurement) – Not supported (WIFI-5144) - Still WIP, doing an ECO to support it, plan to support in IDF v5.3
MSPI tuning (Flash & PSRAM DDR and/or over 80 MHz) - Not supported (IDF-5343) - Still WIP, not sure when to release
SPI Flash auto suspend - Not supported (IDF-5344) - looks done, looks already in master 66bba5694e611980d2671b10ad0839ff1ad6e3e4
Timeout Module (New) - Not supported (IDF-5814) - No plan yet

Could you please add Zigbee NCP Host to the list? See -> https://github.com/espressif/esp-zigbee-sdk/issues/124

RTC Watchdog issues:
in menuconfig there is this option and description:

As far as I can tell there rtc_wdt_disable() and rtc_wdt_feed(), do not apply to anything but the ESP32 and ESP32-S2 as those functions seem to be guarded by ifdefs for those devices.
Will this API ever be supported on other devices?

Update 2024/01/17:

SPI Flash auto suspend - is supported
Broadcast TWT - is in progress

Only remaining items are:

FTM (Fine Time Measurement)
UHCI (UART DMA mode) driver
MSPI tuning (Flash & PSRAM DDR and/or over 80 MHz)
Timeout Module (New)

These remaining items will be supported based on customer requests. We are closing the issue and unpinning it. Please open new issue if you have a feature request, question or any other problem.

Woohoo! Congratulations to everyone that contributed to this massive update for ESP32C6!!

I'm wondering if all the supported features of C6 will be back port to 5.1 and 5.2 releases? (People mainly use release branches for real projects)

Hi, I'm using the relase/5.2 branch and I'm trying to use the ADC_ONESHOT with light sleep.
On boot, I initialize the ADC:

adc_oneshot_new_unit
adc_oneshot_config_channel
adc_cali_create_scheme_curve_fitting

Periodically, it wakes up from deep sleep and read the voltage:
4) adc_oneshot_read
5) adc_cali_raw_to_voltage
Unfortunately, only the first read is correct (in my case 1.8v); reads the occurs after light sleep are totally wrong (4v).
Is calibrated oneshoot adc supported after light sleep 1for esp32-c6?

@tom-borcin sorry for tagging you but can you please take a look at my previous comment? We have already produced some prototype pcbs and if adc is usable in light sleep we must find alternative solutions as soon as possible, thank you

Hi @Suxsem, please open a new issue. We won't be able to track the progress of your issue here. Once you have an issue opened, we will triage it and assign engineer who will help you. Thank you!

This post (issue) says Zigbee Home Automation is supported. Where can I find examples/documentation for that ?
I want to make a simple sensor using this. But I can't find any examples for joining a hub and communicating.

@ilker-aktuna Please check https://github.com/espressif/esp-zigbee-sdk/tree/5f70b2f/examples/esp_zigbee_HA_sample and https://docs.espressif.com/projects/esp-zigbee-sdk/en/latest/esp32/developing.html

@igrr:
Those examples are for connecting between two of the ESP devices (one as end-device, one as coordinator) directly. They do not appear to show connecting to an existing ZigBee network/mesh that might be operated by a hub/controller (such as a Home Assistant or Hubitat). I think that is what @ilker-aktuna is looking for, ie: an end device that can communicate the data to that hub.

The readmes reference two ESP devices for simpler setup, but they can also be used with off-the-shelf hardware. For example, see https://github.com/espressif/esp-zigbee-sdk/issues/149. If you have further questions about ZigBee, please open an issue in esp-zigbee-sdk repository.

The readmes reference two ESP devices for simpler setup, but they can also be used with off-the-shelf hardware. For example, see espressif/esp-zigbee-sdk#149.

@igrr
I want to try these examples but I don't have development environment for these (VS)
Is it possible to have an Arduino version of these ?
In fact, I see that this Arduino example:
https://github.com/P-R-O-C-H-Y/arduino-esp32/blob/Zigbee-examples/libraries/ESP32/examples/Zigbee/Zigbee_Light_Bulb/Zigbee_Light_Bulb.ino
is the ported version of this:
https://github.com/espressif/esp-idf/blob/master/examples/zigbee/light_sample/HA_on_off_light/main/esp_zb_light.c
is that correct ?
if so, there is really not much difference.
Can we also use the example from here , to port to Arduino:
https://github.com/espressif/esp-zigbee-sdk/tree/main/examples/esp_zigbee_HA_sample/HA_on_off_light
I just don't understand where the include files below will be found by Arduino IDE :
#include "esp_zigbee_core.h"
#include "ha/esp_zigbee_ha_standard.h"

there is PSRAM on C6 ?

there is PSRAM on C6 ?

@diplfranzhoepfinger , sadly not: https://esp32.com/viewtopic.php?t=33703

UHCI (UART DMA mode) driver
Is there any timline for the UHCI implementation?

@MichaelUray UHCI is implemented, we are testing it right now and it should be available in one month.


Modal: document is not defined with NextJS SSR

Describe the bug
When going to a page with a modal for the first time, it returns http code 500 and throws ReferenceError: document is not defined in the console.
However, if navigating to the page with Link element from next/link, everything is ok.
The error comes from here.
To Reproduce
Steps to reproduce the behavior:

Go directly to a page with a modal.

Expected behavior
Normal page load without any errors.
System information:

Device: laptop
Resolution: 1920x1080
OS: Linux pcdjoh 5.15.0-58-generic #64~20.04.1-Ubuntu SMP Fri Jan 6 16:42:31 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Browser: Chrome 109.0.5414.119
Version: ???

Project information:

Tailwind: 3.2.4
Flowbite: 1.6.3
Flowbite React: 0.3.8
Type: CRA (?)

whoops didn't see #573 my bad


BUG: GrouperNotFound for TimeGrouper with df.group_by()

Modin version checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest released version of Modin.

[X] I have confirmed this bug exists on the main branch of Modin. (In order to do this you can follow this guide.)

Reproducible Example
import modin.pandas as pd
data = {'id': [1,2],'time_stamp': ["2022-03-24 23:53:09", "2022-03-24 21:53:09"], 'count':[5,5]}
data_frame = pd.DataFrame(data)
data_frame['time_stamp'] = pd.to_datetime(data_frame['time_stamp'])
print(data_frame.dtypes)
daily = data_frame.groupby(pd.Grouper(key='time_stamp', freq='D')).mean().reset_index()
print(daily)

Issue Description
Issue is thrown with the newest Modin version when installed from Github Master.
Expected Behavior
Modin should group data and aggregate data by date.
Pandas gives the following output for daily:
time_stamp   id  count
0 2022-03-24  1.5    5.0
Error Logs
Traceback (most recent call last):
File "/jupyter/performance_queries/test.py", line 6, in
customer_list_df = my_pe.extract_data("system",["2084aa60-0d42-11eb-b15a-9f52e7d4f854"],"SYSTEM","daily")
File "/jupyter/performance_queries/performance_extraction.py", line 65, in extract_data
granularity_df = self.__granularity(aggregated_df, granularity)
File "/jupyter/performance_queries/performance_extraction.py", line 136, in __granularity
granularity_df = data_frame.groupby([pd.Grouper(key='timestamp', freq='D'),'system_id','customer_id']).mean().reset_index()
File "/usr/local/lib/python3.9/site-packages/modin/logging/logger_decorator.py", line 128, in run_and_log
return obj(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/modin/_compat/pandas_api/latest/dataframe.py", line 116, in groupby
return self._groupby(
File "/usr/local/lib/python3.9/site-packages/modin/logging/logger_decorator.py", line 128, in run_and_log
return obj(*args, **kwargs)
File "/usr/local/lib/python3.9/site-packages/modin/pandas/dataframe.py", line 509, in _groupby
raise KeyError(next(x for x in names if x not in self))
KeyError: TimeGrouper(key='timestamp', freq=, axis=0, sort=True, dropna=True, closed='left', label='left', how='mean', convention='e', origin='start_day')
Installed Versions
INSTALLED VERSIONS
commit           : 7871c7bc5adeeaca9b6fc4b88482be8b18333faa
python           : 3.9.10.final.0
python-bits      : 64
OS               : Linux
OS-release       : 5.14.0-70.26.1.el9_0.x86_64
Version          : #1 SMP PREEMPT Fri Sep 2 16:07:40 EDT 2022
machine          : x86_64
processor        : x86_64
byteorder        : little
LC_ALL           : None
LANG             : en_US.UTF-8
LOCALE           : en_US.UTF-8
Modin dependencies
modin            : 0.15.0+171.g7871c7bc
ray              : 2.0.0
dask             : 2022.01.1
distributed      : 2022.01.1
hdk              : None
pandas dependencies
pandas           : 1.5.0
numpy            : 1.23.2
pytz             : 2022.2.1
dateutil         : 2.8.2
setuptools       : 53.0.0
pip              : 21.2.3
Cython           : 0.29.32
pytest           : None
hypothesis       : None
sphinx           : None
blosc            : None
feather          : None
xlsxwriter       : None
lxml.etree       : 4.6.5
html5lib         : None
pymysql          : 1.0.2
psycopg2         : 2.9.3
jinja2           : 3.1.2
IPython          : 8.4.0
pandas_datareader: None
bs4              : 4.11.1
bottleneck       : None
brotli           : None
fastparquet      : None
fsspec           : 2022.7.1
gcsfs            : None
matplotlib       : 3.5.3
numba            : None
numexpr          : None
odfpy            : None
openpyxl         : None
pandas_gbq       : None
pyarrow          : 6.0.1
pyreadstat       : None
pyxlsb           : None
s3fs             : None
scipy            : 1.9.0
snappy           : None
sqlalchemy       : 1.4.40
tables           : None
tabulate         : 0.8.10
xarray           : None
xlrd             : None
xlwt             : None
zstandard        : None
tzdata           : None

Updated Issue for reproducible code

@benaurelschill thanks for reporting this issue. Your script reproduces the error for me. I'm taking a look to see what's going wrong and whether this can be fixed quickly.

The chain of events producing the bug:

we don't compute drop correctly in modin.pandas.DataFrame._groupby when the by is a Grouper object. In the case from the reproducer, we should know we're going to drop the one column in the Grouper object
Because self._drop is wrong, _internal_by thinks there are no by columns: https://github.com/modin-project/modin/blob/621bc10e16c21ca4270a4c2a25aa05f814f2686b/modin/pandas/groupby.py#L377
... although even if self._drop were correct, _internal_by might not be able to deduce the by columns from the grouper.
When dropping non-numeric columns, we assume we can drop the non-numeric key column, because we don't think it's in the by: https://github.com/modin-project/modin/blob/621bc10e16c21ca4270a4c2a25aa05f814f2686b/modin/pandas/groupby.py#L1078-L1089
We try to do the groupby by defaulting to pandas because of the Grouper, and the key column is missing.

It looks like we need to fix _drop and the _internal_by.
Meanwhile, doing groupby on timestamp, but without a grouper, fails, but that's separate issue #5099. #5099 might be a dependency for fixing this bug, too.
@benaurelschill the modin contributors will try to fix this bug soon. Meanwhile, you can work around this bug by doing the entire groupby step in pandas, then converting the result to modin, e.g. as follows (for details see #896):
daily = pd.DataFrame(data_frame._to_pandas().groupby(pd.Grouper(key='time_stamp', freq='D')).mean().reset_index())


Publish a new release

Zbus 2.0 didn't end up coming as fast as I personally expected given the speed of the alpha releases (this is not a bad thing, though). However, I think it would be beneficial to publish a new release in order to do a few things for downstream users:

Establish the higher MSRV and make it less of a surprise to anyone who updates later on.
Remove deprecated dependencies (aesni and aessoft) from downstream user's trees.

This would probably be version 2.1.0, as to avoid breaking anyone with a lower Rust compiler in a SemVer patch release.
@hwchen is this something you have time to look at soon?

I've traced a outdated dependency to this crate, would also love a new release.

@hwchen friendly ping on this

@hwchen Another ping on this, sorry. We've updated to zbus 2.0 so it would be a good time to look at publishing an update.

@hwchen A ping from us as well for a deps update.

Sorry for the delay everyone. I spoke with Walther in private about this and sorted everything out. I'll make sure that a release is out by the end of the week 😄. Sorry for the delay and silence.

Just want to give a big thanks to @complexspaces!

I would really appreciate a release with zbus 2. Currently switching to secret-service = { git = "https://github.com/hwchen/secret-service-rs" } is required to e.g. build Fragments on FreeBSD (as only zbus 2.x includes my portability patches).

For everyone using gtk-rs anyways, there are now bindings (i.e not rust native) for libsecret available.

Not wanting to step on anyone's toes here but I wrote a successor of secret-service-rs that is available at https://github.com/bilelmoussaoui/oo7. Still an alpha release but should work in most use cases

In case you're looking for a dirty workaround, adding this to your Cargo.toml will override the potential dependency other crates are having towards secret-service (in particular, keyring-rs:

[patch.crates-io]
secret-service = { git = "https://github.com/hwchen/secret-service-rs" }

I've also encountered the problem with the outdated nix dependency. @complexspaces @hwchen , any way I can help do some work here to unblock this?

I've filed a PR bumping the version to 2.1.0: https://github.com/hwchen/secret-service-rs/pull/45 .

Hey there @bstrie, thanks for the putting the PR up.
I apologize for taking so long to get around to this. The conversation in #42 threw me off for quite a while and made me doubt some things. I've been kind of confused trying to figure out what the future of this crate is, especially now that oo7 was released with async support. IMO, its internals are a lot cleaner then what secret-service-rs has today.
There seems to be (at least, in public) split between users who want a purely synchronous implementation and those who want async, following along with zbus 2. The downside of the later being, notably, that it requires a dependency on the libdbus C library. It just hasn't been high on my priority list to add that synchronous backend to accompany the zbus update.
With all that being said, if people still want to use this crate, I'd be happy to help get some updates merged and released while slowly working on the synchronous backend to "bring back" what some parties seem to be missing.

Unfortunately 2.0.2 does not work for people indirectly depends on it via the keyring crate.
❯ cargo update -p secret-service --precise 2.0.2
    Updating crates.io index
error: failed to select a version for `bitflags`.
    ... required by package `nix v0.20.2`
    ... which satisfies dependency `nix = "^0.20.2"` of package `zbus v1.9.2`
    ... which satisfies dependency `zbus = "^1.9.2"` of package `secret-service v2.0.2`
    ... which satisfies dependency `secret-service = "^2.0.1"` of package `keyring v1.1.2`
    ... which satisfies dependency `keyring = "^1.1.2"` (locked to 1.1.2) of package `maturin v0.13.0-beta.7 (/Users/messense/Projects/maturin)`
versions that meet the requirements `>=1.1.0, <1.3.0` are: 1.2.1, 1.2.0, 1.1.0

all possible versions conflict with previously selected packages.

  previously selected package `bitflags v1.3.2`
    ... which satisfies dependency `bitflags = "^1.3.2"` of package `security-framework v2.6.1`
    ... which satisfies dependency `security-framework = "^2.6.1"` (locked to 2.6.1) of package `keyring v1.1.2`
    ... which satisfies dependency `keyring = "^1.1.2"` (locked to 1.1.2) of package `maturin v0.13.0-beta.7 (/Users/messense/Projects/maturin)`

failed to select a version for `bitflags` which could resolve this conflict

Yes, next I want to see about getting the zbus folks to do a 1.9.3 release to bump their nix dependency to a more recent version in order to resolve the bitflags issue.

@messense (and anyone else blocked by this issue), I've managed to convince the zbus maintainers to produce a 1.9.3 release that updates their nix dependency, so the bitflags issue should no longer be a problem.


Meta tweaks

Make spoken languages file extensions consistent.

Would it be better to just remove the .ext extension on each of the files since it doesn't really do anything?

Ok


permit port 111 on sap images

Proposed update to security test to permit port 111 on SAP images

/lgtm

/unhold


gen types typescript changes table ordering on unrelated changes

Feature request
I'd like the output of supabase gen types typescript --db-url blah > my_database_types.ts to produce a file that doesn't have lots of changes due to reordering of the tables.
Is your feature request related to a problem? Please describe.
I made some changes via the web GUI/dashboard, and then wanted to regenerate my types.
However, the changes (as shown by, e.g. git diff) are many, most of which are due to the tables being reordered.
Describe the solution you'd like
Provide the same output for each call of supabase gen types typescript, regardless of --local or --db-url, so long as the database being referenced is the same.
Describe alternatives you've considered
Manually reordering the generated types file. Undesireable, especially if repeatedly required.
Additional context
Example changes:

and

caused by removing some nullable types on a different table.
Given that these are only used for typing with TypeScript (and not directly for database migrations, etc) I'd be fine with any static ordering, e.g. alphabetical by table/function name etc.

P.S. the fix isn't out on the latest CLI version yet, but will be soon once we update the typegen's Docker image version.


[DEMO] Pull request showing linting output for bugs

This is a demonstration PR to show how our CI tools now behave when bugs are found, by either CodeClimate or GitHub Actions.
This is a companion to the actual PR, which should be considered at #20.

Closing this as unneeded now that #20 has merged.


Add subresource integrity hashes

We could add subresource integrity hashes to scripts (and stylesheets?).
Related:

#20
#303

Does this even matter anymore since everything is now self-hosted? The scenario where an attackers hacks into the scripts is at the same threat level as an attacker hacks into the website.

I think it’s a lot less important, certainly. I don’t know if there’s a compelling use case if everything is self-hosted, but we could in theory still support it.


Test on Mono

add a testing scheme in Travis which uses Mono
(still has to be enabled in Travis)

That would be a very nice addition, thanks! Can you please check my comment above and fix the PR before merging it? Cheers!

Ondra, this is great, thanks!


Fix: In Snowflake adapter return the DataFrame as is without modifying its column names.

Closes #842

@eakmanrq yes we know this was done to make sushi/wursthall work on snowflake, but we think it's better to just do that in the model code
this was causing problems with select * in snowflake, which @vchan ran into

@eakmanrq yes we know this was done to make sushi/wursthall work on snowflake, but we think it's better to just do that in the model code
this was causing problems with select * in snowflake, which @vchan ran into

What does doing this in the model code mean and why isn't it implemented in this PR?


Upgrading to the latest Azure SDK version 1.2.30 ?

Please provide us with the following information:

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

I'm trying to run the Service Bus samples with the new Service bus emulator. Unfortunately, with the current Azure SDK version (<azure.bom.version>1.2.3</azure.bom.version>) the connection string (Endpoint=sb://localhost;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=SAS_KEY_VALUE;UseDevelopmentEmulator=true;) is not recognized. I've tried with the latest 1.2.30 version and the connection string is recognized.
What about updating the Azure SDK version ?

Go for it!


Indy: Vault structure has to reflect public and private crypto clearly

All crypto in Vault has to be clearly divided into public and private.

Closed by #9


Not support Linux？

Not support Linux？
It seems can't run on Linux.

hPyT is only meant to work on windows as it uses the official Windows DWM API to modify the GUIs.. If there I find a way to do that in Linux and if there is a demand for it, I would add custom functions for Linux too

hPyT is only meant to work on windows as it uses the official Windows DWM API to modify the GUIs.. If there I find a way to do that in Linux and if there is a demand for it, I would add custom functions for Linux too

Thank you very much, I will wait for your Linux version.


Cleanup

Whats Fixed

The highest block value is updated correctly (Fixes ghost shadows when breaking blocks)
Possibly fixed the exit dumper. Will need confirmation on this since I don't run a system that's affected.

Whats Changed

Components now require a proper entity type in their constructors. No more default constructors.
Entity classes now have their components instantiated in protected void setupComponents()
Stone is lower contrast
Dirt wall is darker
Stone wall is darker
All sent messages reset the history index now

> codebeat — 5 issues resolved and 2 introduced (net +3 resolved)
> gpa decreases

Ok codebeat, you do you... :man_facepalming:


bad version number in latest release

is there an error in version number v1.4.0 for tag v2.0.4 ?

Thanks for pointing this out -- has been fixed!


Badge callback is stale due to LRU cache and side effects

Hi there,
I noticed that when using the "badge" entry in the navigation config as a callback (in my case trying to provide a dynamic count of certain records) that the callback is called once and then cached indefinitely.
I traced this back to the following sequence of events:

In get_sidebar_list, we start of by calling get_config(self.settings_name)["SIDEBAR"].get("navigation", [])
Initially, this returns the config dictionary (default + user config) wrapped in a @lru_cache decorator.
We iterate the navigation items, but in some places, we mutate the contents of the cached dictionary. Due to the way @lru_cache works, this actually modifies (pollutes) the cached record, meaning that the next call to the decorated get_config function returns the modified dict.
Continuing down the function, we iterate each item and examine its badge entry. If it's a string, we try to import it as a module path using Django's import_string function. If successful, we execute the imported function and assign it's return value to item['badge']. This not only returns the badge callback result for the current request, but as a side effect also modifies the cached record as noted above.
On the next request, item['badge'] has been replaced with the callback result from the last step, so it will never** call the badge function again unless the process is restarted or the LRU cache is somehow otherwise evicted.

** unless the return value happens to be a string, in which case we'll continue to try to import it even if its not a module path!
To me, this behavior seems unintentional, but I thought I'd open to discuss and double check. Is it desirable to use badge callbacks to report dynamic values? If so I have some ideas on how to improve this function, but let me know!

Thanks for report. I just merged a fix for this.


Tagger Script syntax highlight

Summary
This is a…

[ ] Correction
[x] Addition
[ ] Restructuring
[ ] Minor / simple change (like a typo)
[ ] Other

Reason for the Change
Provide syntax highlighting for Picard Tagger Script in code examples.
Description of the Change

Add a Sphinx extension that registers a custom Pygments lexer for the Tagger Script syntax
Add a stylesheet to highlight taggerscript with the same colors as Picard does
Mark all code blocks explicitly for taggerscript

Need to check how to make the RST linting happy.

Need to check how to make the RST linting happy.

I just pushed a code change to take care of that.  Hope you don't mind.

Thanks a lot for fixing this, much appreciated.

I fixed the formatting for comments. Just to give a feeling how this looks like for a more complex script:


Remove <:Real restrictions on type parameters and allow non-Float64 results

I've separated the changes into two commits. See commit messages for details.

Codecov Report

Merging #48 (f955580) into main (12164f5) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #48      +/-   ##
==========================================
- Coverage   99.63%   99.62%   -0.01%
==========================================
  Files           6        6
  Lines         276      270       -6
==========================================
- Hits          275      269       -6
  Misses          1        1

Impacted Files
Coverage Δ

src/estimator.jl
100.00% <100.00%> (ø)

src/eventtimes.jl
100.00% <100.00%> (ø)

src/kaplanmeier.jl
100.00% <100.00%> (ø)

src/nelsonaalen.jl
100.00% <100.00%> (ø)

src/cox.jl
99.21% <0.00%> (-0.07%)
:arrow_down:

Continue to review full report at Codecov.

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


V10 update

Update for version 10 in the works or planned at all?

Yes! Thanks for the reminder!
I probably won't be able to get to it this week, but I will try the upgrade next week

Added V10 support in version2.0.3 with #15


Remove Client and Server traits

Removes the experimental Client and Server traits. We won't be using Server for Tide, and the chance is slim we'll use Client for Surf. So it may be best to remove them from the project. Thanks!

@Fishrock123 pointed out that this is not semver-major because it was unstable, so merging. My mistake!


nbSaveBlocks

in a site like adventofnim any change to the html template require to rerun all individual documents to be applied.
one possible solution is to introduce a nbSaveBlocks api that save only the content of the blocks (they change much less frequently). For example a document.nim with nbSaveBlocks, it will save only the content of blocks to a document.htm file instead of document.html (this convention might turn out not to be a good idea). Some other api should allow then to rebuild the site starting from the blocks output (we will likely need to dump other context information to a document.json in order to do that).
Other solution might be actually to dump some kind of full representation of the document (again, a json?) and from there reconstruct the full document using the additional templates.

also there should be an compile option to make nbSave behave like nbSaveBlocks (so that a bunch of documents can automatically switch to this mode) and there should be an easy way to rebuild the complete site (I guess the shared context of #17 should play a role).


circadian-setup is very heavy

When I execute (circadian-setup), Emacs is suspended a few minutes, lot of I/O. (why circadian-setup has heavy I/O?)
So I take a profiling with Emacs profiler:
CPU profiler report
- timer-event-handler                                          103854  70%
 - apply                                                       103846  70%
  - circadian-enable-theme                                     103772  70%
   - load-theme                                                 53783  36%
    - apply                                                     53783  36%
     - #<compiled 0x2267db>                                     53783  36%
      - enable-theme                                            53707  36%
       - apply                                                  53707  36%
        - ad-Advice-enable-theme                                53707  36%
         - #<compiled 0x226a5f>                                 53703  36%
          - custom-theme-recalc-face                            53690  36%
           - face-spec-recalc                                   53553  36%
            - face-spec-set-2                                   48746  32%
             - apply                                            48733  32%
              - set-face-attribute                              48638  32%
               - internal-set-lisp-face-attribute               47961  32%
                - frame-set-background-mode                     47876  32%
                 - face-attr-match-p                            23974  16%
                    face-attribute                              23078  15%
                 - face-spec-recalc                             23150  15%
                  - face-spec-reset-face                        20658  13%
                   - apply                                      20639  13%
                      set-face-attribute                        19378  13%
                  - face-spec-set-2                              1954   1%
                   - apply                                       1918   1%
                      set-face-attribute                         1672   1%
                  + face-spec-choose                              158   0%
                 + face-spec-choose                               167   0%
                 + face-list                                       37   0%
            + face-spec-reset-face                               4555   3%
            + face-spec-choose                                    101   0%
             facep                                                 91   0%
      + eval-buffer                                                64   0%
      + insert-file-contents                                        6   0%
        #<compiled 0x22688b>                                        3   0%
   - mapc                                                       49937  33%
    - disable-theme                                             49937  33%
     - apply                                                    49937  33%
      - ad-Advice-disable-theme                                 49937  33%
       - #<compiled 0x226b77>                                   49931  33%
        - face-set-after-frame-default                          27319  18%
         - face-spec-recalc                                     23514  15%
          - face-spec-reset-face                                20963  14%
           - apply                                              20922  14%
              set-face-attribute                                19707  13%
          - face-spec-set-2                                      1993   1%
           - apply                                               1933   1%
              set-face-attribute                                 1650   1%
          - face-spec-choose                                      162   0%
           + face-spec-set-match-display                           58   0%
         + face-list                                               19   0%
        - set-frame-parameter                                   22492  15%
         - modify-frame-parameters                              22226  15%
          - frame-set-background-mode                           22075  14%
           - face-attr-match-p                                  10966   7%
              face-attribute                                    10505   7%
           - face-spec-recalc                                   10512   7%
            - face-spec-reset-face                               9309   6%
             - apply                                             9293   6%
                set-face-attribute                               8870   5%
            + face-spec-set-2                                     925   0%
            + face-spec-choose                                     84   0%
           + face-spec-choose                                      80   0%
             face-list                                             19   0%
             color-values                                           6   0%
        + custom--frame-color-default                              12   0%
   + run-hook-with-args                                            52   0%
  + auto-revert-buffers                                            14   0%
  + beacon--dec                                                    13   0%
  + save-some-buffers                                               3   0%
 + timer-activate-when-idle                                         3   0%
- command-execute                                               41670  28%
 - call-interactively                                           41670  28%
  - funcall-interactively                                       40939  27%
   - eval-expression                                            38589  26%
    - eval                                                      38580  26%
     - circadian-setup                                          38580  26%
      - circadian-activate-latest-theme                         38551  26%
       - circadian-enable-theme                                 38529  26%
        - mapc                                                  36074  24%
         - disable-theme                                        36074  24%
          - apply                                               36074  24%
           - ad-Advice-disable-theme                            36074  24%
            - #<compiled 0x226b77>                              36074  24%
             - set-frame-parameter                              22388  15%
              - modify-frame-parameters                         22282  15%
               - frame-set-background-mode                      22105  14%
                - face-attr-match-p                             10916   7%
                   face-attribute                               10487   7%
                - face-spec-recalc                              10568   7%
                 - face-spec-reset-face                          9307   6%
                  - apply                                        9288   6%
                     set-face-attribute                          8825   5%
                 + face-spec-set-2                                981   0%
                 + face-spec-choose                               133   0%
                + face-spec-choose                                107   0%
                + face-list                                        10   0%
             - face-set-after-frame-default                     13651   9%
              - face-spec-recalc                                11833   8%
               - face-spec-reset-face                           10482   7%
                - apply                                         10455   7%
                   set-face-attribute                            9881   6%
               - face-spec-set-2                                 1087   0%
                + apply                                          1066   0%
               + face-spec-choose                                  80   0%
              + internal-merge-in-global-face                      17   0%
              + face-list                                          15   0%
             + custom--frame-color-default                         10   0%
        + load-theme                                             2432   1%
        + run-hook-with-args                                       23   0%
       + circadian-filter-inactivate-themes                        22   0%
      + mapc                                                       29   0%
   + counsel-M-x                                                 2340   1%
   + handle-focus-in                                               10   0%
  + byte-code                                                     731   0%
+ ...                                                            2286   1%
+ redisplay_internal (C function)                                  33   0%
+ sp--save-pre-command-state                                       11   0%
  global-project-shells-mode-check-buffers                          4   0%

Memory profiler report:
- timer-event-handler                                      55,590,275  52%
 - apply                                                   55,535,640  52%
  - circadian-enable-theme                                 54,416,671  51%
   - mapc                                                  28,572,095  26%
    - disable-theme                                        28,572,095  26%
     - apply                                               28,572,095  26%
      - ad-Advice-disable-theme                            28,572,095  26%
       - #<compiled 0x226b77>                              28,572,095  26%
        - face-set-after-frame-default                     18,777,534  17%
         - face-spec-recalc                                17,779,558  16%
          - face-spec-reset-face                           14,994,446  14%
           - apply                                         14,990,222  14%
            - set-face-attribute                               23,534   0%
               purecopy                                         9,022   0%
          - face-spec-set-2                                 1,361,184   1%
             apply                                          1,361,184   1%
          - face-spec-choose                                   58,520   0%
             face-spec-set-match-display                       19,448   0%
           face-list                                          505,824   0%
        - set-frame-parameter                               9,793,505   9%
         - modify-frame-parameters                          8,996,117   8%
          - frame-set-background-mode                       8,926,421   8%
           - face-spec-recalc                               8,234,773   7%
            - face-spec-reset-face                          7,101,485   6%
             - apply                                        7,101,485   6%
              - set-face-attribute                            981,629   0%
                 purecopy                                       4,514   0%
            - face-spec-set-2                                 529,056   0%
               apply                                          529,056   0%
            + face-spec-choose                                 67,784   0%
             face-list                                        545,952   0%
             face-attr-match-p                                114,048   0%
           + face-spec-choose                                  27,216   0%
             color-values                                       2,112   0%
   - load-theme                                            25,839,296  24%
    - apply                                                25,839,296  24%
     - #<compiled 0x2267db>                                25,839,296  24%
      - enable-theme                                       25,549,490  24%
       - apply                                             25,549,490  24%
        - ad-Advice-enable-theme                           25,549,490  24%
         - #<compiled 0x226a5f>                            25,539,986  24%
          - custom-theme-recalc-face                       25,535,762  24%
           - face-spec-recalc                              25,366,802  23%
            - face-spec-set-2                              19,467,860  18%
             - apply                                       19,467,860  18%
              - set-face-attribute                         18,821,588  17%
               - internal-set-lisp-face-attribute          17,939,906  16%
                - frame-set-background-mode                17,936,738  16%
                 - face-spec-recalc                        16,728,674  15%
                  - face-spec-reset-face                   14,146,706  13%
                   + apply                                 14,146,706  13%
                  + face-spec-set-2                         1,286,256   1%
                  + face-spec-choose                           30,624   0%
                   face-list                                  963,072   0%
                   face-attr-match-p                          203,808   0%
                 + face-spec-choose                            35,904   0%
                   color-values                                 5,280   0%
            + face-spec-reset-face                          5,091,102   4%
          + enable-theme                                        4,224   0%
         + cider-scale-background-color                         1,056   0%
      + insert-file-contents                                  216,472   0%
      + eval-buffer                                            46,816   0%
      + #<compiled 0x22688b>                                    6,336   0%
        generate-new-buffer                                     2,122   0%
        custom-theme--load-path                                 1,684   0%
   + run-hook-with-args                                         5,280   0%
  + beacon--dec                                             1,104,656   1%
  + auto-revert-buffers                                        11,120   0%
    jit-lock-context-fontify                                    2,112   0%
  + save-some-buffers                                           1,081   0%
 + timer-inc-time                                              19,008   0%
   timer-until                                                  7,558   0%
 + timer-activate-when-idle                                     4,224   0%
 + timer-activate                                               3,168   0%
- command-execute                                          50,308,500  47%
 - call-interactively                                      50,308,500  47%
  - funcall-interactively                                  48,293,474  45%
   - counsel-M-x                                           30,625,261  28%
    - ivy-read                                             29,484,034  27%
     - ivy-call                                            24,273,592  22%
      - #<compiled 0x39b9921>                              24,273,592  22%
       - command-execute                                   24,273,592  22%
        - call-interactively                               24,273,592  22%
         - funcall-interactively                           24,273,576  22%
          + profiler-report                                24,273,576  22%
     + read-from-minibuffer                                 5,004,550   4%
     + ivy--reset-state                                       200,520   0%
    + require                                                   2,048   0%
      counsel--M-x-prompt                                       2,043   0%
   - eval-expression                                       17,416,317  16%
    - eval                                                 17,415,225  16%
     - circadian-setup                                     17,415,225  16%
      - circadian-activate-latest-theme                    17,278,509  16%
       + circadian-enable-theme                            17,152,997  16%
       - circadian-filter-inactivate-themes                   124,488   0%
        - cl-remove-if                                        124,488   0%
         - apply                                              124,488   0%
          - cl-remove                                         124,488   0%
           - #<compiled 0x366f1dd>                            124,488   0%
            - circadian-match-sun                             124,488   0%
             - circadian-sunset                                62,776   0%
              - sunrise-sunset                                 62,776   0%
               - solar-sunrise-sunset-string                   62,776   0%
                - solar-sunrise-sunset                         62,776   0%
                 + solar-sunrise-and-sunset                    60,648   0%
                 + solar-exact-local-noon                       1,064   0%
                 + solar-sidereal-time                          1,064   0%
             + circadian-sunrise                               61,712   0%
       + circadian-now-time-string                              1,024   0%
      + mapc                                                  136,716   0%
    + prin1                                                     1,092   0%
   + handle-focus-in                                          251,896   0%
  + byte-code                                               2,015,026   1%
+ redisplay_internal (C function)                             152,136   0%
+ ...                                                           8,188   0%
+ winner-save-old-configurations                                4,136   0%
+ yas--post-command-handler                                     3,360   0%
+ sclang-document-post-command-hook-function                    3,156   0%
  xselect-convert-to-targets                                    2,112   0%
+ xselect-convert-to-string                                     1,048   0%

Thanks for reporting, I'll try to dive deeper into the performance of circadian, as soon as I can

@stardiviner On which platform do you run Emacs? And which version did you use? I can't quite reproduce that memory/CPU consuming behaviour. Profiling (circadian-setup) an my MacBook Air (Late 2010) needs under 1% each 🤔

I'm on Arch Linux, and Emacs version 27 (compiled from latest master branch source code).

I've just had another look at this (sorry for taking so ultra long, haven't actively used/developed this package for a while):
Results from using Emacs-Lisp Profiler:
circadian-setup  1           0.00229       0.00229

also added a test to the test suite using benchmark.el: test/circadian.el-test.el#L117, plesae try to run the test on your system, if this is still a persistant issue.

macOS Big Sur 11.7
MacBook Pro (Retina, 15-inch, Mid 2014)
Emacs 29.0.60 (emacs-plus)


Unhandled promise rejections are deprecated

Hi there.
I've been using dialogflow-fulfillment-nodejs library for a few days now, so far, so good.
But when trying to request data from an external API within the fulfillment handler, I've been facing a tenacious error:
(node:67018) UnhandledPromiseRejectionWarning: Error: No responses defined for platform: DIALOGFLOW_CONSOLE
    at V2Agent.sendResponses_ (/Users/x99/Documents/Repositories/PROJECT/functions/node_modules/dialogflow-fulfillment/src/v2-agent.js:243:13)
    at WebhookClient.send_ (/Users/x99/Documents/Repositories/PROJECT/functions/node_modules/dialogflow-fulfillment/src/dialogflow-fulfillment.js:505:17)
    at /Users/x99/Documents/Repositories/PROJECT/functions/node_modules/dialogflow-fulfillment/src/dialogflow-fulfillment.js:316:38
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at emitUnhandledRejectionWarning (internal/process/promises.js:168:15)
    at processPromiseRejections (internal/process/promises.js:247:11)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

Here's the code:
const { response } = require('express');
var https = require ('https');

function httpRequest(params, postData) {
	return new Promise(function(resolve, reject) {
		var req = https.request(params, function(res) {
			// reject on bad status
			if (res.statusCode < 200 || res.statusCode >= 300) {
				return reject(new Error('statusCode=' + res.statusCode));
			}
			// cumulate data
			var body = [];
			res.on('data', function(chunk) {
				body.push(chunk);
			});
			// resolve on end
			res.on('end', function() {
				try {
					body = JSON.parse(Buffer.concat(body).toString());
				} catch(e) {
					reject(e);
				}
				resolve(body);
			});
		});

		// reject on request error
		req.on('error', function(err) {
			// This is not a "Second reject", just a different sort of failure
			reject(err);
		});

		if (postData) {
			req.write(postData);
		}

		// IMPORTANT
		req.end();
	})
	.catch(function (error) {
		console.error("Promise rejected");
	});
}

exports.howManyTasks = function(agent) {
	console.log("[INFO] howManyTasks");

	const host = "myapihost.com"
	const path = "/api/users/myusertoken/task_lists";
	const bearerToken = "mybearertoken";

	var params = {
        hostname: host,
        port: 443,
        path: path,
        method: 'GET',
        headers:{
            Authorization: ' Bearer ' + bearerToken
       }
	};

	httpRequest(params).then(function(body) {
		console.log(body);
	})
	.catch(function () {
		console.error("Promise Rejected");
	});

	console.log("[INFO] I'm out!");
}

From what I see in the logs, the error comes from the library itself? Knowing that beyond the error, my code successfully retrieves the needed data from the API.

I have this error too, my code worked before when I deploy it. But after few hours (or other trigger, I don't know for sure) Dialogflow fulfillment's requests have changed and now it come with "originalDetectIntentRequest" field. And I stuck here for 3 days.
Are you found any solution for this? Or alternative library to use with dialogflow fulfillment? Since this library is deprecated.


⚠ Bofrost.lu has degraded performance

In 384b696, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 2147 ms

Resolved: Bofrost.lu performance has improved in 62fe863 after 37 minutes.


Web driver version issue between local and Azure build agent

Hello,
We are facing chrome web driver version difference and facing error. Using Selenium chrome web driver nuget package version 79 to run test in local, but when we run against Azure build hosted agent, it has only chrome browser version of 77.xxx.
Due to version conflicts,we are unable to find the solution to this issue. Please suggest any ideas

For "windows-2019", "vs2017-win2016" Microsoft-hosted agent next code can be used for generating correct WebDriver folder path for hosted MS Agents

Thanks @Shakevg for sharing this solution.
@VasanthChidambaram - This is a limitation of the current feature branch that we are looking to update soon, but the option shared above is a good one for now.
With recent changes to the ChromeDriver requiring version parity between Driver and Browser, this caused some difficulties with the version we were including within the branches. We made a decision to try and maintain the latest driver version in the branches, but this does present issues when using Azured DevOps Hosted Agents.
This link shows the options for Microsoft Hosted Agents. Each agent type has a link which shows the software versions included on the agent. This includes detail about which Chrome Browser version is installed, as well as the varying WebDrivers for Chrome, Firefox, and IE.
Thanks,
Tyler


Fix: header search focus timeout

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

14 of 14 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 99.674%

Totals

Change from base Build<PHONE_NUMBER>9:
-0.01%

Covered Lines:
13487

Relevant Lines:
13488

💛  - Coveralls


Enforce OAuth

Hi,
I have modified all Network Functions to properly request and validate OAuth tokens from the NRF's authorization server. This will be part of a larger pull request to free5GC as there are a few repositories to which I need to make pull requests.
This pull request modifies the NSSF to request and validate OAuth tokens sent and received. I added a new configuration variable "OAuth" which determines if OAuth is enforced or not. Please review the changes on this pull request.
NRF Pull Request: https://github.com/free5gc/nrf/pull/8
OpenAPI Pull Request: https://github.com/free5gc/openapi/pull/7
When these three PR's are merged, I will create other pull requests for the rest of the Network Functions. Please let me know if you have further questions.
Thanks!

@swthorn
We use https://github.com/free5gc/nssf/pull/16 instead, and will close this PR, thanks.


Release Review Approved for Public Released files via upload

Release Review Approved for Public Release
~65% of STIG Rules green when starting from a default PostgreSQL 9.5 Install and running this PostgreSQL Lockdown Ansible role

Thanks for the contribution!  Bear with me while I sort it out.

This has been merged into master.  Thanks again!


Add "Configure Unit Tests" Command

(task from #1983)
The "Configure Unit Tests" command will allow user to force configuration of unit tests if for whatever reason it can't be done automatically.  A test will need to be added.

validated


srb init fails on Ruby 2.7 because of argument delegation

Input
srb init fails when used on Ruby 2.7 with Capybara. I'm fairly certain it's because of code like this, which uses the new ... syntax: https://github.com/teamcapybara/capybara/blob/5d24424b135be8539810f4e65b7bc920b40ede8f/lib/capybara/rack_test/node.rb#L122-L139
You can reproduce this issue pretty simply, like so:

git clone https://github.com/connorshea/sorbet-capybara-27
Make sure you're on Ruby 2.7, e.g. rbenv local 2.7.0
bundle install
bundle exec srb init
See that it crashes

Observed output
It ends up crashing when generating the reflection.rbi`
Printing /var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-21062-gaqeqd/reflection.rbi's symbol table into /var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-21062-gaqeqd/reflection.json
Traceback (most recent call last):
	6: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/bin/srb-rbi:237:in `<main>'
	5: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/bin/srb-rbi:196:in `main'
	4: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/bin/srb-rbi:121:in `init'
	3: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/bin/srb-rbi:232:in `block in make_step'
	2: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/lib/hidden-definition-finder.rb:38:in `main'
	1: from /Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/lib/hidden-definition-finder.rb:47:in `main'
/Users/connorshea/.rbenv/versions/2.7.0/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5439/lib/hidden-definition-finder.rb:149:in `write_constants': /var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-21062-gaqeqd/reflection.rbi had unexpected errors. Check this file for a clue: /var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-21062-gaqeqd/reflection.json.err (RuntimeError)

reflection.json.err has lines like this:
/var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-20791-17d8u9b/reflection.rbi:19468: unexpected token tCOLON https://srb.help/2001
       19468 |      *: ::T.untyped,
                     ^

/var/folders/2n/6l8d3x457wq9m5fpry0dltb40000gn/T/d20200314-20791-17d8u9b/reflection.rbi:19473: unexpected token tAMPER https://srb.help/2001
       19473 |  def [](**, &&); end
                            ^

And generates methods like this in reflection.rbi:
  sig do
    params(
      *: ::T.untyped,
      &: ::T.untyped,
    )
    .returns(::T.untyped)
  end
  def [](**, &&); end

Expected behavior
I'd expect this to be generated the same as it looks in the actual code, like def method_name(...); end. Unfortunately, there's not currently a way of distinguishing between (*args, &blk) and (...) via the parameters method because of this upstream issue: https://bugs.ruby-lang.org/issues/16456
We could determine it by checking for Method#parameters returning something like this:
def foo(...); end
p method(:foo).parameters
# => [[:rest, :*], [:block, :&]]

See also #2618, which reported this issue a few weeks ago.

Unfortunately, we're not yet working on 2.7 support at Stripe.
We will love to review PRs implementing 2.7 support, but we're not putting effort into it just yet

I got the same error with the latest sorbet (currently 0.5.5622) and ruby 2.7:
Traceback (most recent call last):
	6: from /Users/.../sorbet-0.5.5622/bin/srb-rbi:237:in `<main>'
	5: from /Users/.../sorbet-0.5.5622/bin/srb-rbi:196:in `main'
	4: from /Users/.../sorbet-0.5.5622/bin/srb-rbi:121:in `init'
	3: from /Users/.../sorbet-0.5.5622/bin/srb-rbi:232:in `block in make_step'
	2: from /Users/.../sorbet-0.5.5622/lib/hidden-definition-finder.rb:38:in `main'
	1: from /Users/.../sorbet-0.5.5622/lib/hidden-definition-finder.rb:47:in `main'
/Users/.../sorbet-0.5.5622/lib/hidden-definition-finder.rb:149:in `write_constants':
/var/folders/sb/69c3...t6qms0/reflection.rbi had unexpected errors.
Check this file for a clue: /var/folders/sb/69c3drbd4pl_0j0xydlssh200000gn/T/d20200514-22232-t6qms0/reflection.json.err (RuntimeError)

Unfortunately, we're not yet working on 2.7 support at Stripe.

Can you please clarify, it sounds like people using sorbet should stay on 2.6 for now?
FYI, https://sorbet.org/docs/faq#what-platforms-does-sorbet-support says:

Ruby 2.7 should mostly work, but feel free to open issues for it.

But, if srb init crashes, we should probably rephrase it.

FWIW I was able to fix a lot of the deprecation warnings from tracer.rb:40 (except one) when running srb init by changing this bit of code in tracer.rb:
module ClassOverride
  def new(*)
    result = super
    Sorbet::Private::GemGeneratorTracepoint::Tracer.on_module_created(result)
    result
  end
end

to this:
module ClassOverride
  def new(*)
    result = super
    Sorbet::Private::GemGeneratorTracepoint::Tracer.on_module_created(result)
    result
  end

  ruby2_keywords(:new) if respond_to?(:ruby2_keywords, true)
end

Before this fix I was getting a ton of warnings like this:
/Users/connorshea/.rbenv/versions/2.7.1/lib/ruby/gems/2.7.0/gems/sorbet-0.5.5737/lib/gem-generator-tracepoint/tracer.rb:40: warning: Using the last argument as keyword parameters is deprecated

Now I only get one, not really sure how to fix that last one.


⚠ Minecraft has degraded performance

In 39cbb1d, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1251 ms

Resolved: Minecraft performance has improved in 1b84680.


Migration from version 1.? to latest

Hi guys,
Any possibilities for you to provide us with a migration guide to your latest version?
Thanks in advance

no :(
sorry, the code changed a lot.. so there is no guide to migrate old projects to new 2.X projects.
But you will find the new code cleaner and easier, and the documentation is there, so I expect that you will have no issues at all.


No package revision found for: PackageName "ghc"

I am on Windows 10, with HIE up to date to commit 239d07da8a3a7f80a4f0acef287256aae4cc2361 and trying to install HIE for GHC 8.6.2 with stack --version Version 1.10.0, Git revision 48f4befb67860a24fc8c3310e6d55ace9fd35dfe (dirty) (6868 commits) x86_64 hpack-0.31.1. Command
stack --stack-yaml=stack-8.6.2.yaml install

yields error:
No package revision found for: PackageName "ghc"
CallStack (from HasCallStack):
  error, called at src/Stack\Build\ConstructPlan.hs:434:42 in stack-1.10.0-Gyq3czmxkWV9B1iWoXQn3F:Stack.Build.ConstructPlan

I note that the only versions of the ghc package currently on Hackage are 8.2.1, 8.2.2, 8.4.1, 8.4.3, and 8.6.1 and this same error seems to occur only when trying to install HIE for versions of ghc not on Hackage (eg 8.4.2 or 8.4.4).

I'm not able to recreate this on stack 1.9.3, so we should probably take a look at this before stack 1.10 is released.
It is worth noting that the version of GHC on stackage is more recent (8.6.3) than hackage, I'm not sure as to why this is though

This was a stack problem that has now been fixed.


Remove view count

Fixes

Fixes #540 by @aldenstpage
Description

Removed view_count column of image table and its references in codebase.
Technical details

view_count column in image table was used to perform analytics on image views. We used arcane mechanism to capture and analyse image view count. This is now deprecated.
Now that we have a dedicated mechanism of analytics, we no longer require this column and feature. A related cron job was also deleted.
Tests

Screenshots

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added tests for the changes I made (if applicable).
[x] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

It looks like there's a new build error, take a look at the Travis CI logs

Ran the same on local. Worked fine.
The error says that it did not get response from
http://localhost:8000/v1/images?q=test in stipulated time.
Can you help me as where to look for more information to fix this?

If you expand the load_sample_data.sh logs, you can see that something has gone wrong:
INSERT 0 2

ERROR:  extra data after last expected column

CONTEXT:  COPY image, line 5001: "10494466,2018-09-11 13:06:48.062657+00,2018-10-19 14:20:07.92795+00,97f9ee0a-4f08-4027-85ca-a60e2f39..."

{"message": "Successfully scheduled task", "task_id": "dfcca007-548e-4627-b5f6-dcbb40cc3665", "status_check": "http://localhost:8001/task/dfcca007-548e-4627-b5f6-dcbb40cc3665"}{"message": "Successfully scheduled task", "task_id": "e8056bd5-b178-46a5-9d6e-73ae0b354925", "status_check": "http://localhost:8001/task/e8056bd5-b178-46a5-9d6e-73ae0b354925"}(integer) 1

$ bash -c 'while [[ "$(curl --insecure -s -o /dev/null -w ''%{http_code}'' http://localhost:8000/v1/images?q=test)" != "200" ]]; do sleep 5; done'

load_sample_data was successful. But no output received by Travis. Build terminated.

@aldenstpage Can you please suggest on how to proceed from here?

Debugging Travis issues can be difficult; I hope it's a little easier now that we've switched to GitHub Actions (which will be a little more explicit about what step failed and run the tests much faster). Even with that change, end-to-end tests are difficult to work with because you often have to sift through a sea of application logs to find what went wrong.
Rather than figure out what's wrong with the build, I opted to start from scratch and open a new PR https://github.com/creativecommons/cccatalog-api/pull/597.


Hot fix on no cookies in response header

Disable session strorage and check in

Hmm, sorry for the late reply.
I've checked your commit, how to keep the check_expired function?

Problem
The URL https://public-api.secure.pixiv.net/v1/ios_magazine_banner.json in check_expired function is not available right now.
It will response with a 404 not found head and fails the whole process.
Solution
Maybe you can try to use another URL for validation or just skip this process ?


Make NSNumberFormatter configurable

https://github.com/hyperoslo/NSManagedObject-HYPPropertyMapper/blob/b1430dbc9e96d177cad6d1d9016bdd1069ed949c/Source/NSManagedObject%2BHYPPropertyMapper.m#L118

This problem is related to using , and . when parsing strings as numbers. PropertyMapper should be smart enough to understand both.

This is still an issue. I'm going to close it since it's just a convenience, we don't officially support parsing strings as numbers.


Use DependencyContext to find assembly path and version

Hey @baor
I did some changes on top of your PR.
Can you please check if they work? Unfortunately I wasn't able to reproduce the issue you had with assembly resolving, so I can't test it.
I will describe my changes on the PR.

@baor
Please, feel free to refactor on top of my changes. Or to don't merge and implement something similar.
The main thing I want to ensure is that we load the correct assembly from nuget/packages.


Is there anyway to download the pretrained weights?

The pretrained weights can be downloaded from Google Drive.


[Feature Request] Mount Journal & Krowi Achievement Filter skins

Hello,
Is it possible to request skinning for the following addons?
Mount Journal
https://www.curseforge.com/wow/addons/mountsjournal
(sample skinning for ElvUI https://github.com/sfmict/MountsJournal-ElvUI-Skin)
Krowi Achievement Filter
https://www.curseforge.com/wow/addons/krowi-achievement-filter
(sample skinning for ElvUI https://github.com/TheKrowi/Krowi_AchievementFilter/blob/main/Plugins/ElvUI.lua)

I'll take a look at the Mount Journal later this week.
As for the Krowi Achievement Filter, NDui (mainline) already includes its skin, see Krowi_AF.lua

Oh about Krowi Achievements i did not see any setting to active/deactivate so I though its not there.
Do you maybe know if I need to activate something or it just loads?

just load Krowi Achievement Filter

Using alpha build getting the below error. Removing the function on line 180 fixes the issue.
6x NDui_Plus: ...aceNDui_Plus/Modules/Skins/MountsJournal.lua:180: hooksecurefunc(): ADDON_LOADED is not a function
[string "=[C]"]: in function hooksecurefunc' [string "@NDui_Plus/Modules/Skins/MountsJournal.lua"]:180: in function <...aceNDui_Plus/Modules/Skins/MountsJournal.lua:171> [string "=[C]"]: ? [string "@NDui_Plus/Core/Core.lua"]:255: in function CallLoadedAddon'
[string "@NDui_Plus/Core/Core.lua"]:325: in function Initialize' [string "@NDui_Plus/Core/Core.lua"]:340: in function InitCallback'
[string "@NDui/Init.lua"]:144: in function `func'
[string "@NDui/Init.lua"]:23: in function <NDui/Init.lua:18>
Locals:

fixed and finished in 11.0.3-alpha-3


application gateway zone redundancy

[Enter feedback here]
Hi. I wonder where can i find configuration about zone redundancy?
If i create app gateway v2, does it support zone redundancy by default? or do you support additional configuration for that?
Thanks.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 702c4c56-9e3c-9234-841a-5618e8d78138
Version Independent ID: 27df9871-e2a7-9746-32e1-991d0bafa169
Content: Tutorial: Improve web application access - Azure Application Gateway
Content Source: articles/application-gateway/tutorial-autoscale-ps.md
Service: application-gateway
GitHub Login: @vhorne
Microsoft Alias: victorh

@junpark12 , Appreciate your patience. APPGW v2 has zone redundancy by default and all you need to do is just specify the zones while deploying APPGW.

Zone redundancy is available only where Azure Zones are available. In other regions, all other features are supported. For more information, see Regions and Availability Zones in Azure

It's clear. Thanks :)

@junpark12 , Appreciate your patience. APPGW v2 has zone redundancy by default and all you need to do is just specify the zones while deploying APPGW.

Zone redundancy is available only where Azure Zones are available. In other regions, all other features are supported. For more information, see Regions and Availability Zones in Azure

@SubhashVasarapu-MSFT How difficult it is to change the zones of an application gateway after being deployed?


License

Any plans on adding a license on this repo? Thanks in advance!

Yes, I'm going to add MIT license as soon as possible.
On Mon, 26 Oct, 2020, 1:59 pm Steve C<EMAIL_ADDRESS>wrote:

Any plans on adding a license on this repo? Thanks in advance!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Arvindcs/SwiftUI-Animation/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE77NIJ54CU6623RVCDEUMTSMUXNDANCNFSM4S7B3KLA
.

Hey, I have added licens
Please check

Awesome! Thanks! :)


AMP-84095 add description of Braze User Alias Label

Amplitude Developer Docs PR
Requested by NBA and RBI to be able to customize their user alias label so that it matches up with their alias cohort sync label
Description
Description added for new field in Braze event streaming
Deadline
When do these changes need to be live on the site?
By EOD when corresponding code changes are merged
Change type

[ ] Doc bug fix. Fixes #[insert issue number]. Amplitude contributors include Jira issue number.
[X] Doc update.
[ ] New documentation.
[ ] Non-documentation related fix or update.

PR checklist:

[X] My documentation follows the style guidelines of this project.
[ ] I previewed my documentation on a local server using mkdocs serve.
[ ] Running mkdocs serve didn't generate any failures.
[X] I have performed a self-review of my own documentation.

@amplitude-dev-docs

Hmm. It looks like linter and spell checker are failing but it doesn't look related to my changes?

Hmm looks like spell check is not failing for my changes, it's due to formatguide.md

@sina-jamshidi Ah, yes, sorry about that. I just added that this morning.
Let me update those so they aren't checked. If this is ready to go, (I just approved it), I can also force push to get around it.

Hmm looks like spell check is not failing for my changes, it's due to formatguide.md


rmb gives twin not found error for valid twin

Quoting @muhamadazmy

if u send a message to remote twin, then u waited some time (say until the cache of the twin is cleared), and then u tried to send a message again, u will get a twin not found error, I guess that's a cache implementation issue!

It gives the following error
2022-08-04T14:29:42.013Z DEBUG [rmb::http_workers::work_runner] can not retrieve twin from substrate for this id '114' because of Rpc error: The background task been terminated because: Networking or low-level protocol error: WebSocket connection error: connection closed; restart required

The reason was clear that websocket connection is dropped, I tried to see why it's dropped nearly after 1min, I tried to check the subtx or even jsonrpsee-client but didn't reach anything, wither the client or even the server who closes the connection (I thought there should be something to keep this connection alive)
anyway, I'll go for the easy solution, which is reconnecting again manually as this feature is not yet implemented for subxt, see this issue here.

After some trials, the same connection is dropped in case it was idle for sometime. I added a simple reconnecting client where it would build a new substrate client in case it's not connected.

Verified on devnet.
I sent a message first then i left rmb idle for about 25 minutes i sent another message and as seen in the screenshot below the client was disconnected and a new one was rebuilt automatically and the message was received  sucessfully.


Develop

Codecov Report

Merging #26 into master will increase coverage by 3.85%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #26      +/-   ##
==========================================
+ Coverage   93.97%   97.82%   +3.85%
==========================================
  Files           7       13       +6
  Lines          83      322     +239
==========================================
+ Hits           78      315     +237
- Misses          5        7       +2

Impacted Files
Coverage Δ

Tests/LogNDT7Tests.swift
100% <0%> (ø)

Tests/SystemConsoleLoggerTests.swift
100% <0%> (ø)

Tests/QueueTests.swift
100% <0%> (ø)

Tests/NDT7Tests.swift
100% <0%> (ø)

Tests/FileLoggerTests.swift
94.28% <0%> (ø)

Tests/DateExtensionTests.swift
100% <0%> (ø)

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 3aee703...2c7b87a. Read the comment docs.


bump wasmtime

this pulls in an updated wasmtime to fix our dependence on rand_core that recently had a RUSTSEC advisory. it also updates raw-cpuid to 9.0.0 to fix a few soundness issues: these were in functions we don't use (as_string/processor_brand_string and cpuid_count), but cargo audit is a hammer that strikes all nails.

cut corners warning: a full cargo update includes bumping criterion from 0.3.3 to 0.3.4. this includes deprecation warnings for the various Lucet benchmarks, but i'm pretty uncertain how to rewrite them to the BenchmarkGroup API.


Fix address case sensitivity to prevent duplicate claiming

I have implemented a fix to prevent attacks where users attempt to use inconsistent casing for the same address, such as 0x1f31938747f84fc96c94E6cd04589eEDF2Bb98eb and 0x1f31938747f84fc96c94e6cd04589eedf2bb98eb.
It is possible to use the sendTransaction function with wallet addresses in all lowercase, and I have also tested modifying the casing of other characters but found that it does not work. : )

thanks for the pr!


Unable to load custom font using satori options

Describe the bug
In nuxt.config.ts
ogImage: {
  fonts: ['Manrope:500'],
  satoriOptions: {
    fonts: [{
      name: 'optieinstein',
      style: 'normal',
      weight: 800,
      data: fs.readFileSync('./public/fonts/OPTIEinstein_black.woff'),
    }]
  },
}

Above code does not add a custom font. Instead, I am met with this system log
seo-image unknown or invalid utility

How can one use custom fonts that are in the project directory and not Google Fonts-based?
Reproduction
No response
System / Nuxt Info
------------------------------
- Operating System: Windows_NT
- Node Version:     v18.15.0
- Nuxt Version:     3.4.2
- Nitro Version:    2.3.3
- Package Manager<EMAIL_ADDRESS>- Builder:          vite
- User Config:      runtimeConfig, typescript, extends, ogImage, css, vite, modules, app
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Hey @Bumbleboss, thanks for the issue.
Custom font loading wasn't supported before.
I've now implemented it in the latest beta, see the Custom Fonts documentation on implementation details.

This error keeps showing up despite following the documentation.

Would it also be possible to have custom font and google font added together?
I am currently using 2.0.0-beta.23

@Bumbleboss Would you share your config? I'm using the below and it's working as expected
  ogImage: {
    fonts: [
      'Inter:400',
      'Inter:700',
      {
        name: 'optieinstein',
        weight: 800,
        path: '/OPTIEinstein-Black.otf',
      }
    ],
  }

On version 2.0.0-beta.27. Error changed and image is no longer being rendered. The difference is .woff
  ogImage: {
    fonts: [
      'Manrope:500',
      {
        name: 'optieinstein',
        weight: 800,
        path: '/fonts/OPTIEinstein_black.woff',
      }
    ],
  }

This is what appears on terminal:

And image itself is not being rendered, it becomes transparent.

Is the white screen and error only there when using the .woff?
Also can you double check you're using the latest, in the newest version all json extractions have a try / catch with them :thinking:

Actually I can replicate this atm, looking into a fix

Was able to reproduce issue. I even tried having the image only show a simple text but the issue still persists. You will need to test it locally since StackBlitz causes an issue with retrieving Manrope font.
https://stackblitz.com/edit/github-ocxs1d?file=pages/index.vue
Issue still exists after removing custom font, it was rendering fine on stable release (without using custom local font)

Thanks for the reproduction!
This was an interesting bug, for whatever reason the # from your props wasn't being encoded properly so the json payload was being cut short.
Fixed in 2.0.0-beta.29

Can confirm, it works now! Thanks!