text:
[TW#13570] Sniffer mode: wifi_pkt_rx_ctrl_t not showing 11n traffic?

https://github.com/espressif/esp-idf/blob/master/components/esp32/include/esp_wifi_types.h
typedef struct {
    signed rssi:8;            /**< signal intensity of packet */
    unsigned rate:5;          /**< data rate */
    unsigned :1;              /**< reserve */
    unsigned sig_mode:2;      /**< 0:is not 11n packet; 1:is 11n packet */
    unsigned :16;             /**< reserve */
    unsigned mcs:7;           /**< if is 11n packet, shows the modulation(range from 0 to 76) */
    unsigned cwb:1;           /**< if is 11n packet, shows if is HT40 packet or not */
    unsigned :16;             /**< reserve */
    unsigned smoothing:1;     /**< reserve */
    unsigned not_sounding:1;  /**< reserve */
    unsigned :1;              /**< reserve */
    unsigned aggregation:1;   /**< Aggregation */
    unsigned stbc:2;          /**< STBC */
    unsigned fec_coding:1;    /**< if is 11n packet, shows if is LDPC packet or not */
    unsigned sgi:1;           /**< SGI */
    unsigned noise_floor:8;   /**< noise floor */
    unsigned ampdu_cnt:8;     /**< ampdu cnt */
    unsigned channel:4;       /**< which channel this packet in */
    unsigned :12;             /**< reserve */
    unsigned timestamp:32;    /**< timestamp */
    unsigned :32;             /**< reserve */
    unsigned :32;             /**< reserve */
    unsigned sig_len:12;      /**< It is really lenth of packet */
    unsigned :12;             /**< reserve */
    unsigned rx_state:8;      /**< rx state */
} wifi_pkt_rx_ctrl_t;

I have set the wifi card into sniffer mode but I am not getting any 11n packets? and hence none of the 11n fields are getting populated. They are always 0. Also, the "rate" field seems to be only the values "11" or "0" for me. Only the packet length, RSSI and Channel are being populated for every packet.
I am not sure what do I have to do to capture 11n packets? and get the rest of the fields populated? Does any special mode have to be set?

Friends,
Any update on this? I am developing a product and this sadly seems to be a deal breaker. Can any of the folks working for the company please respond? We bought these chips because the manufacturer explicitly mentions "sniffer" as a mode for Wi-Fi on their website.

Maybe @TimXia or @liuzfesp can help

ＨＩ ＠anoncontrib, which kind of type the sniffer captured? WIFI_PKT_DATA? or WIFI_PKT_MISC?

Its capturing WIFI_PKT_DATA  and WIFI_PKT_MGMT.
I am not sure what we get when its is WIFI_PKT_MISC?  seems almost like an error condition to me as the header file says the payload is NULL?
Also in older versions there was a WIFI_PKT_CTRL as well? but has been removed now?

Yes, @anoncontrib WIFI_PKT_CTRL is removed because we actually don't filter the ctrl packet (such as CTS, RTS, ACK etc) to CPU and the ctrl packet is dropped in the hardware according our current design.
As the issue your referred, could you let me know the IDF commit ID please? Then I can check it...

This is the line:
https://github.com/espressif/esp-idf/blob/99d5959d8a319c26b5b907d26a4a5993a2775594/components/esp32/include/esp_wifi_types.h#L251
It says if the type is  WIFI_PKT_MISC  then the payload is NULL.  So what is this packet then?
Also, I am getting packets with WIFI_PKT_DATA & WIFI_PKT_MGMT  but it is never 11n as sig_mode is always 0.  Why is this happening?

Sorry to bug you so much but could you please let me know?  I internally championed the ESP32 in our company and I'll be in pretty hot soup if I don't get to a conclusion by this week :(

Hi @anoncontrib sorry for my late response, just a little busying....
I just test the sniffer with my device, the result:
sig_mode=0 rate=0 mcs=0
sig_mode=1 rate=11 mcs=7   =====> sig_mode 1 means 11N packets, the rate is MCS 7
sig_mode=1 rate=11 mcs=0
sig_mode=0 rate=0 mcs=0
sig_mode=0 rate=0 mcs=0
sig_mode=0 rate=0 mcs=0
sig_mode=0 rate=11 mcs=0
sig_mode=1 rate=11 mcs=7
sig_mode=1 rate=11 mcs=7
sig_mode=0 rate=0 mcs=0
sig_mode=0 rate=6 mcs=0
sig_mode=0 rate=6 mcs=0
sig_mode=0 rate=0 mcs=0

@liuzfesp Thanks! Really appreciate the help.
Can you please share the code if you don't mind. I seem to be doing everything right but still not seeing any sig_mode = 1 packets. I just want to make sure I have not left out anything.
Please looking forward to your response.

Hi @anoncontrib my promiscuous callback function void ssc_sniffer_cb(void *buf, wifi_promiscuous_pkt_type_t type) {         wifi_pkt_rx_ctrl_t *ctl = (wifi_pkt_rx_ctrl_t*)but;         switch (type) {         case WIFI_PKT_MGMT:                 g_sniffer_cnt.rx_mgmt++;                 break;         case WIFI_PKT_DATA:                 //printf the debug info here                 g_sniffer_cnt.rx_data++;                 break;         case WIFI_PKT_MISC:                 g_sniffer_cnt.rx_misc++;                 break;         }         g_sniffer_cnt.rx_total++;         return; }  Before we can get the 11N packet, we need to make sure there is 11N packets in the air...

Hi @anoncontrib , did the above suggestion help you resolve the issue?

@liuzfesp Hello, Can idf add the WIFI_PKT_CTRL frame? I just need this in my product.

authors: FayeY anoncontrib liuzfesp malaimoo negativekelvin


text:
portMAX_DELAY not leading to xStreamBufferReceive() waiting indefinitely (IDFGH-7239)

Problem Description
As stated in the documentation  setting xTicksToWait to portMAX_DELAY should result in xStreamBufferReceive blocking untill the number of bytes set by xTriggerLevel is reached.
This works fine for me untill I try to pass a stream longer than ~113 bytes received from an UART clocked at 9.6k baud. The bytes get transmitted with gaps inbitween adding up to about 397ms for the 113 bytes. Anything longer than that and the xStreamBufferReceive returns priore to reaching the trigger level.
I suspect somthing similar to this from another repository but it does not seem to be resolved.

You can test if it's the issue you linked to by defining this macro in your build (this is a workaround for the race condition):
	#define sbSEND_COMPLETED( pxStreamBuffer )											\
		vTaskSuspendAll();																\
		{																				\
			if( ( pxStreamBuffer )->xTaskWaitingToReceive != NULL && 						\
  			  prvBytesInBuffer( pxStreamBuffer ) >= pxStreamBuffer->xTriggerLevelBytes) \
			{																			\
				( void ) xTaskNotify( ( pxStreamBuffer )->xTaskWaitingToReceive,		\
									  ( uint32_t ) 0,									\
									  eNoAction );										\
				( pxStreamBuffer )->xTaskWaitingToReceive = NULL;						\
			}																			\
		}																				\
		( void ) xTaskResumeAll();

If adding that resolves the symptom, then it's the same root cause.

how much is actually returned, and what value is xTriggerLevel?

I'll have a look at that tomorrow and get you those numbers as soon as possible

@EN20M Did some tests but wasn't able to replicate this.
Any chance you can share a simple example that can reproduce this issue?
If not then some more info might help us trace down what's happening:

Like @moefear85 mentioned already: what is xTriggerLevel set to and how many bytes do receive return when it times out?
Which IDF commit are you basing your project on?

in case you are interested heres the uart config:
void uart_init(void)
{
   const uart_config_t uart_config = {
       .baud_rate = 9600,
       .data_bits = UART_DATA_8_BITS,
       .parity = UART_PARITY_EVEN,
       .stop_bits = UART_STOP_BITS_1,
       .flow_ctrl = UART_HW_FLOWCTRL_DISABLE,
       .source_clk = UART_SCLK_APB,
   };
   uart_driver_install(UART_NUM_1, RX_BUF_SIZE * 2, 0, 0, NULL, 0);
   uart_param_config(UART_NUM_1, &uart_config);
   uart_set_pin(UART_NUM_1, TXD_PIN, RXD_PIN, UART_PIN_NO_CHANGE, UART_PIN_NO_CHANGE);
}

@EN20M As far as I know xStreamBufferReceive will only block until triggerLevel if the message buffer is empty when you call the function. If there is e.g. 10 bytes there then it will return 10 bytes immediately, no matter what the trigger level is.

and triggerlevel is designed to be called in high frequency to delimit messages? i don't think that works because it assumes no data loss. one it happens, sender & reciever become desynchronized.
i use magic strings and c++ string-search & size fields. ideally uart-break should have been usable, but that is currently broken. i also tried base64 encoding. but all seem to lead to alot of loss under load, when for example, there are several freertos timers running and messages are forwarded to/from wifi.
which is the best method? i wonder now how modbus does it.

@ESP-Marius That fits perfectly to the behaviour that I am seeing. As you can see I had to wrap the call in a loop running untill the desired amont of bytes got received so I'll now treat my workaround as my solution.
I don't really understand why one would want xStreamBufferReceive to return before triggerLevel is reached but if it is like that it would be nice if its behaviour is documented like that.
Thanks for the help. If it is acually intended bahaviour than it looks like this issue can be closed.

@EN20M Closing this one then.
I agree that the upstream freeRTOS docs do a poor job of emphasizing this, I also missed it initially and only noticed after reading the code itself.

source: gharchive/issue

repo: espressif/esp-idf

license_type: permissive

license_source: github-api


text:
AttributeError: module 'esptool' has no attribute '_main' at idf5.+ (IDFGH-8149)

Answers checklist.

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

IDF version.
v5.0
Operating System used.
Windows
How did you build your project?
VS Code IDE
If you are using Windows, please specify command line type.
PowerShell
What is the expected behavior?
idf project can build with idf5.0 on vs code IDE
What is the actual behavior?
build fail with idf5.0, but use idf4.4 can build successful
in idf4.4

in idf5.+(master)

Steps to reproduce.

install idf5.0
open project
run build command

Build or installation Logs.
No response
More Information.
No response

Hi @Coloryr. Please take a look at hints posted here
Duplicate of https://github.com/espressif/esp-idf/issues/9451

build fail with idf5.0, but use idf4.4 can build successful

I think the setup of v4.4 is used with v5.0 (which is not compatible). Probably, you will have to re-run the setup so it would be re-generated for v5.0.

build fail with idf5.0, but use idf4.4 can build successful

I think the setup of v4.4 is used with v5.0 (which is not compatible). Probably, you will have to re-run the setup so it would be re-generated for v5.0.

my esp-idf uses ESP-IDF VS Code Extension to install

re-run esp-idf\install.bat can't fix

All files have been deleted and reinstalled

What about E:\workload\.espressif\python_env?

All files have been deleted and reinstalled

What about E:\workload\.espressif\python_env?

Contains two folders:

it may be a vs extension problem
idf5.+ can build successful with cmd

You could try to remove the 4.4 version. It could be one more in E:\workload\.espressif\vscode\python_env as well. That is why export.bat has no effect. If you still have an issue then please report it in https://github.com/espressif/vscode-esp-idf-extension. This relates to Vscode setup. You can get better help there.

You could try to remove the 4.4 version. It could be one more in E:\workload\.espressif\vscode\python_env as well. That is why export.bat has no effect. If you still have an issue then please report it in https://github.com/espressif/vscode-esp-idf-extension. This relates to Vscode setup. You can get better help there.

thank you.
i will report to vscode extension.

Hello, @Coloryr .
Do you solve the problem?
i am facing the same issue. i reinstall windows, reinstall VScode, it didn't work.
i wanna use idf5! it can bulid project successfully but can't flash device. and give this information in terminal.
Traceback (most recent call last):
  File "f:\ESP32\idf\esp-idf\components\esptool_py\esptool\esptool.py", line 22, in <module>
    esptool._main()  # type: ignore
AttributeError: module 'esptool' has no attribute '_main'

i have reinstall windows and vscode so many times. i install esp-idf v4.4 in VScode, it worked, can build and flash. but when i install esp-idf v5. i can't flash! it's a torture.

@kurau1 nope, but i have a better solution without use the vscode extension.

haha, me too, i edit program by vscode and flash by powershell, it can work T T

authors: Coloryr dobairoland kurau1


text:
Build error with changing the vendor and product ID (CON-763)

I have changed the vendor and product ID's for our product and tried building the project, which throws error.
Attaching the error log
deviceID_errors.txt
I have generated the Certs don't where to place exactly to solve this errors.

@SYESHASWINI Please share the details about the mfg_tool commands used and upload your sdkconfig file.

@dhrishi I have used chip cert commands for generating the certificates.
This is the sdk file:
sdk_cert.txt

@SYESHASWINI Please take a look at mfg_tool.
You have configured the VID/PID to non-test and still using the Test DAC provider and it is causing the problem. Test DAC provider only have test certs from VID:0xFFF1-0xFFF4 and PID:0x8000:0x8063.
And hence it is failing to compile. You will have to generate the manufacturing binary and flash it, then set the correct config options, build/flash firmware and that would work. All the info you need is in mfg_tool's readme.

I am closing this issue. Please refer the README and and it should help. Feel free to re-open in case of anything.

@shubhamdp I tried generating partition using the command
./mfg_tool.py -cn "My bulb" -v 0xFFF2 -p 0x8001 --pai
-k path/to/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Key.pem
-c path/to/esp-matter/connectedhomeip/connectedhomeip/credentials/test/attestation/Chip-Test-PAI-FFF2-8001-Cert.pem
-cd path/to/esp-matter/connectedhomeip/connectedhomeip/credentials/test/certification-declaration/Chip-Test-CD-FFF2-8001.der
where it throws the following error:
Traceback (most recent call last):
File "/home/ubuntu/esp-matter/esp-matter/tools/mfg_tool/./mfg_tool.py", line 630, in
main()
File "/home/ubuntu/esp-matter/esp-matter/tools/mfg_tool/./mfg_tool.py", line 623, in main
write_per_device_unique_data(args)
File "/home/ubuntu/esp-matter/esp-matter/tools/mfg_tool/./mfg_tool.py", line 360, in write_per_device_unique_data
generate_onboarding_data(args, int(row['Index']), int(chip_factory_get_val('discriminator')), int(row['PIN Code']))
File "/home/ubuntu/esp-matter/esp-matter/tools/mfg_tool/./mfg_tool.py", line 438, in generate_onboarding_data
if args.commissioning_flow == CommissioningFlow.Standard:
NameError: name 'CommissioningFlow' is not defined

authors: SYESHASWINI dhrishi shubhamdp

repo: espressif/esp-matter


text:
Matter example does not work with local control (MEGH-5010)

Answers checklist.

[X] I have read the Rainmaker documentation and the issue is not addressed there.
[X] I have updated my IDF branch (release/vX.Y) to the latest version and checked that the issue is present there. This is not applicable if you are using Rainmaker with Arduino.
[X] I have searched the Rainmaker forum and issue tracker for a similar issue and not found a similar issue.

IDF / ESP32-Arduino version.
v5.1.1
Operating System used.
Linux
How did you build your project?
Command line with idf.py
Development Kit.
ESP32_Dev
What is the expected behavior?
I have tried the matter light and switch example given in Rainmaker SDK. It works fine. I have enable the local control from the menuconfig settings and when I checked for local control the matter device does not controllable from local network.
What is the actual behavior?
Similar the Rainmaker multi_device example, local control is not working for matter_light and matter_switch.
Steps to reproduce.

Step :Enable the local control option from menuconfig
Step: Disable the internet and try to access the node within local network
Step: Node is not accessible from local network.
...

Debug Logs.
E (7697) Dynamic Impl: alloc(4437 bytes) failed
E (7707) esp-tls-mbedtls: write error :-0x7F00:
E (7707) transport_base: esp_tls_conn_write error, errno=Success
E (7707) mqtt_client: Writing failed: errno=0
E (7717) esp_mqtt_glue: MQTT_EVENT_ERROR
E (7717) mqtt_client: Error to subscribe topic=node/jFioTsikMxvhwyneEz9ScB/params/remote, qos=1
E (7727) esp_rmaker_param: Failed to subscribe to node/jFioTsikMxvhwyneEz9ScB/params/remote. Error -1
E (7737) esp_rmaker_core: Aborting!!!

More Information.
No response

@tbthaker23 matter itself is meant for local control and so, the esp local control used in other non Matter examples is not meant to co-exist with Matter.

Thanks for quick response. I know matter itself for local control. So Matter_Light is locally controllable by using Rainmaker mobile application? When we can expect the Matter Controller for RainMaker?

repo: espressif/esp-rainmaker


text:
add gitignore

files that created on build process

レポジトリに追加する.gitignoreの内容については(追加するか、どうかもふくめて)検討中です。また、あらたにContributingに関するガイドラインも公開しましたので、あわせてご確認ください。

わかりました。

source: gharchive/pull-request

authors: ShikiOkasaka h-youhei

repo: esrille/ibus-replace-with-kanji

license_source: bigquery


text:
fix: handle macro declared vars

If you declare a var inside a macro it gets a name like ::anon@0::v5. This handles that by also replacing @ and non-prefix :: with _.
Maybe don't merge until @mitchmindtree has checked this

fixes #771

Actually this doesn't handle pub vars declared in macros. Fixing this now

I'm kind of surprised we can have macros that expand to var/pub-var declarations, but looks like this PR just helps support existing stuff so :shipit:

If we couldn't do this then it greatly reduces the ability to reuse code with macros. The vars/ pub vars are still scoped to the macro so they can't be used outside the macro.

I guess it just feels a bit odd that we abstract them away in a macro in pint, but then they're revealed on the application side in ABI-gen anyways.
My intuition is that like state, var and pub var declarations should be explicit as they're all the inputs to the predicate. Having them hidden in macros kind of feels like hiding function arguments :sweat_smile:
I'm struggling to think of cases where you wouldn't want to declare a var/pub var with some type, and then pass the var ident as an input to the macro instead to do whatever other constraint expansion etc is necessary :thinking: Maybe the use-case will become clearer to me once I actually start hacking on some application stuff.

I'm struggling to think of cases where you wouldn't want to declare a var/pub var with some type, and then pass the var ident as an input to the macro instead to do whatever other constraint expansion etc is necessary 🤔 Maybe the use-case will become clearer to me once I actually start hacking on some application stuff.

Basically something like this:
https://github.com/essential-contributions/essential-integration/blob/d226ba333d1a27488589f298181a4deb84fe9961/apps/token/pint/signed/src/contract.pnt#L109

I guess if we decide to not allow declaring vars and pub vars in macros then I could not merge this PR and just change the integration apps to not do that?
@mitchmindtree another thing that this kind of fixed but might not actually be a problem is that currently if you have a name like ::foo::bar it becomes foo not foo_bar. I'm not sure if it's possible to declare a var or pub var in another file but if it is this would be a problem.

I might just merge this as it's blocking work on the integration repo. If we decide to make it not possible to declare var or pub var in macros then we can revert this change later.

I'm not sure if it's possible to declare a var or pub var in another file

I don't think it is, and I suspect we don't want to allow this. It might be odd to declare an input for a predicate somewhere outside of the predicate itself? Again, this might just be a self-imposed mental block I have by imagining vars and pub vars as function inputs for predicates, but it's the closest mental model I can think of. I feel like as someone reading the code, you want to be able to read all the inputs in one place, but this might just be personal preference.
I'll open a separate issue to discuss decision variable / transient data decls in macros :+1:

authors: freesig mitchmindtree

repo: essential-contributions/pint


text:
Sometimes the thread name is wrong in the log

The attachment test3.zip contains a rust project with two mods.
Each of these two modules has a "connect" function, which creates a named thread in which it connects to "wss: //echo.websocket.org" and sends a ping every second. The websocket server will response with the same message.
Except for the names, these two mods are almost the same.
log4rs is used in the project:
refresh_rate: 30 seconds
appenders:
  stdout:
    kind: console
    encoder:
      pattern: "[{d(%Y-%m-%d %H:%M:%S.%3f)} {T:>16.16} {M:16.16} {L:>4.4} {l}] {m}{n}"

root:
  level: info
  appenders:
    - stdout

Sometimes the thread name in the log is wrong as below. It only happens when receiving messages.

I have simplified the test project as much as I can, I'm sorry if it has not been minimized.
test3.zip

I don't have much experience with async_std but I think this is probably caused by it.
If you add println!("On thread: {}", std::thread::current().name().unwrap_or("unnamed")); before line 30 in mod1 and mod2. You will see that the info macros are running on the threads that they are reporting.

@ngugc did @SarthakSingh31's comment resolve your issue?

Yes, it's caused by asyn-std.
I though it was like C++'s coroutine, but it's not.
The task is not bound to the thread who creates it.
Thanks! @SarthakSingh31 . I'll try if tokio has the same behaviour.

Glad to hear it.

authors: SarthakSingh31 estk ngugc


text:
[Filter SIRET] perf: filter siret on the root doc to prevent ESToParentBlockJoinQuery

A déployer après cette merge request qui modifie le mapping :
https://github.com/etalab/annuaire-entreprises-search-infra/pull/203
On simplifie la recherche par SIRET et ça se traduit par un gain minime de temps d'exécution mais qui peut être significatif lorsque de nombreuses requêtes arrivent en même temps.
:warning: ce code n'a pas encore pu être testé localement

As discussed yesterday, this new mapping does not take into account the inner hits which return the matching_etablissements response field.

authors: HAEKADI MKCG

repo: etalab/annuaire-entreprises-search-api

license: MIT


text:
Controlled font scaling

Avoids the font scaling lower than 14px when a lower value is used for the host sites root (HTML) element by

Using the widget container as the parent element which provides the font size
Moving all the most important bits within it to em instead of rem

:tada: This PR is included in version 1.38.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: etchteam/recycling-locator


text:
Multiple months on the popup

Currently we are seeing only one month on the Calendar. It will be very useful if we can set an option to see multiple months. For instance if i want to see a 3 month calendar it would be very useful.

Duplicate of #1154

repo: eternicode/bootstrap-datepicker


text:
fixes window.resize bug that freezes ie7

On ie7, the call to place() would generate a new window.resize event which would in turn call place() again and so on, generating an endless loop and freezing the browser. This change checks for an actual window resizing before calling place(), fixing that problem

Can you provide a jsfiddle example showing this problem? (you can use this base jsfiddle As I can't reproduce the problem on a local vm

Closing this PR for now as I can't reproduce it. If this is still an issue on the latest master, please reopen reopen the pull request and provide a jsfiddle example!

authors: acrobat corrego


text:
Missing extern "C" in etesync.h header

When included from a C++ program, the compiler will try to lookup mangled function names in etesync.so but will fail, since the library is a C library, so the names there are not mangled in there.
The code in the generated header should be wrapped in extern "C" { ...... } to indicate to the compiler that the functions there are C functions and that it should lookup unmangled function names in linked libraries.

:man_facepalming: nice catch, pushing a fix.

authors: danvratil tasn

repo: etesync/etesync-rs


text:
Can't pass custom device_map to lmql serve_model with --cuda

Starting an LMQL server with lmql serve-model ... --cuda invokes lmql.models.lmtp.lmtp_serve. This function calls lmql.models.lmtp.utils.rename_model_args which has the following line:
if cuda:         model_args["device_map"] = "auto"
This automatically re-assigns the "device_map" parameter to "auto", even if I pass a custom value.
I have a model that fits on a single GPU, so there's no need to distribute it across multiple GPU's. To improve latency I would prefer to specify device_map: 0 so that the model is loaded on a single GPU.

Thanks for raising this. This should definitely be fixed. For now I can recommend the use of CUDA_VISIBLE_DEVICES=0 as a workaround that should limit distribution to only GPU 0.

The original issue should also be fixed in the release that just got pushed to pypi.org, 0.0.6.5.

authors: bglazer lbeurerkellner

repo: eth-sri/lmql


text:
Request: Support of InheritedWidget

I want to start by expressing my gratitude to the author for excellent work in enabling code push functionality.
The plugin has proven to be incredibly valuable for our Flutter projects, making the app update process smoother and more efficient on design part.
While the eval plugin currently supports the use of BuildContext, I would like to kindly request the addition of support for InheritedWidget.
ChangeNotifier is a widely used mechanism for managing state in Flutter applications. By enabling InheritedWidget support, we can ensure that the ChangeNotifier implemented within the eval plugin can seamlessly communicate state changes to the entire widget tree, simplifying complex state management scenarios.
InheritedWidget is also invaluable for maintaining global configurations or settings within an app. With this support, developers can use eval to dynamically update and distribute these configurations throughout the app.
Looking for any updates or solutions regarded InheritedWidget use through eval.
This will be a significant enhancement that would make the plugin even more versatile and beneficial to the Flutter community.

Hi and thanks for the kind words :)
InheritedWidget is a particularly difficult case since Dart has no mechanism for dynamically specifying type parameters. dependOnInheritedWidgetOfExactType requires specifying the type parameter T and there is no way dart_eval can do that dyamically, outside of having a giant piece of code with every single possible Widget type mapped to that function. As you can imagine, generating that for every single function that takes type parameters is unrealistic. Doing it for that one function only is more doable, but still a far-future project.
Since support for state management packages like Riverpod is much easier, that'll likely happen first.

But is it possible to make bridge to exact one component? If we don't want to build a universal solution, but some strongly typed solution for exact one native plugin?

@nosovk Of course yes, there is no restrictions on what you can do with bridging.

@bgoncharuck could we make bridge to webview only? Not a universal solution, but exactly one that required?

authors: bgoncharuck ethanblake4 nosovk


text:
Deneb: Add test cases to execution payload processing

Adds a couple of simple test cases I thought could be interesting.
I added a small comment of my understanding of the goal of the tests in this file, and based on that is what I thought was missing and added, but if this was a misinterpretation please let me know.
I'll try to think of more tests to add.

@djrtwo done!

authors: hwwhww marioevz

repo: ethereum/consensus-specs


text:
include message in goodbye

Add a descriptive message to goodbye, to describe disconnection reason
for debugging purposes. Clients may choose to leave it empty, or not
send a goodbye at all.
This has been discussed in chat and in calls - generally, it is redundant but may help in diagnosing testnet issues.
A more complex version has been proposed with  error codes for specific scenarios and accompanying expected behaviours and interactions, but the benefits are unclear, specially when considering the worse case. Generally, if peers are misbehaving, they should likely not be sent a goodbye message at all, as this wastes resources and may further exacerbate the problem.

I see you made it goodbye v2.
How do you propose we handle multi-versions to start? if both v2, use v2; else v1?

It doesn't really matter, this is a bit of an optional message - ie nothing prevents a client from just.. disconnecting. That said, clients are free to provide an overlap period should this be deemed useful.

closing this for now

authors: arnetheduck djrtwo


text:
Bug fixes and cleanups around exit_validator

Cleanups

Use state.slot over current_slot.
Specify new_status
Segregate ejection processing

Bug fixes:

Put ejections at the end of the per-slot processing (TODO: per-slot processing should come after per-epoch processing)
Immediately exit ejections
Include ACTIVE_PENDING_EXIT as an active state
Renamed two State to BeaconState

I've resolved conflicts with master.

@djrtwo We also need to:

Replace the code under # Exit validator with a call to exit_validator
Only remove validator from persistent committees and update validator_registry_delta_chain_tip if there's an actual exit event (i.e. EXITED_WITH_PENALTY or EXITED_WITHOUT_PENALTY).
Abstract away all the grunt work around status changes (e.g. regarding validator_registry_delta_chain_tip, status, latest_status_change_slot) into an update_validator_status function.

Feel free to merge this one first to avoid a huge PR.


text:
feat(fw): Add sha256 hash to fixtures

🗒 Description
Adds sha256 hash calculation to all generated fixtures, by simply converting to JSON string, with ordered keys and without _info, then hashing the string.
I benchmarked all algorithms that hashlib provides using this: https://github.com/SharkyRawr/python-hashlib-benchmark
and surprisingly sha256 was among the fastest ones (I thought it would be md5 but it turns out it's not).
It also adds a nice script that prints the hashes in several forms, the hasher entry-point (see more with hasher -h).
🔗 Related Issues
None
✅ Checklist

[x] All: Set appropriate labels for the changes.
[x] All: Considered squashing commits to improve commit history.
[x] All: Added an entry to CHANGELOG.md.
[ ] All: Considered updating the online docs in the ./docs/ directory.
[x] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[x] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[x] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

Really nice! I think I will rebase the fixture diff PR onto this branch and use the hasher to create the hash tree.
I added the info hash to some framework tests here: https://github.com/marioevz/execution-spec-tests/pull/16

authors: marioevz spencer-tb

repo: ethereum/execution-spec-tests


text:
Implement revert

What was wrong?
How was it fixed?
To-Do

[ ] OPTIONAL: Update Spec if applicable
[ ] Clean up commit history

Codecov Report

Merging #74 into master will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   88.02%   87.90%   -0.13%
==========================================
  Files          36       36
  Lines        2279     2281       +2
==========================================
- Hits         2006     2005       -1
- Misses        273      276       +3

Impacted Files
Coverage Δ

compiler/src/yul/mappers/functions.rs
0.00% <0.00%> (ø)

semantics/src/traversal/functions.rs
88.09% <0.00%> (-2.15%)
:arrow_down:

compiler/src/abi/elements.rs
89.47% <0.00%> (-1.76%)
: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 c0a6a4f...35a7c61. Read the comment docs.

Codecov Report

Merging #74 into master will decrease coverage by 0.12%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #74      +/-   ##
==========================================
- Coverage   88.02%   87.90%   -0.13%
==========================================
  Files          36       36
  Lines        2279     2281       +2
==========================================
- Hits         2006     2005       -1
- Misses        273      276       +3

Impacted Files
Coverage Δ

compiler/src/yul/mappers/functions.rs
0.00% <0.00%> (ø)

semantics/src/traversal/functions.rs
88.09% <0.00%> (-2.15%)
:arrow_down:

compiler/src/abi/elements.rs
89.47% <0.00%> (-1.76%)
: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 fc0657f...0955a27. Read the comment docs.

authors: cburgdorf codecov-commenter codecov-io

repo: ethereum/fe


text:
Extract core jsonrpc types & create trin-types

What was wrong?
Extract trin-core/src/jsonrpc/* & create trin-types workspace
Motivation. To extract our validation logic, we need to first extract some of these types so they're accessible from a different workspace without introducing a circular dependency.
...

trin_core/src/jsonrpc/endpoints.rs -> ethportal_api/src/endpoints.rs
trin_core/src/jsonrpc/service.rs -> ethportal_api/src/service.rs
trin_core/src/jsonrpc/types.rs

Params -> ethportal-api/src/types/params.rs
Request -> ethportal-api/src/types/request.rs

trin_core/src/jsonrpc/utils/rs -> trin_utils/src/bucket.rs

remove unused parse_content_item() util

trin_core/src/portalnet/types/messages.rs

SszEnr -> trin_types/src/enr.rs

trin_core/src/portalnet/mod.rs

Enr -> trin_types/src/enr.rs

trin_core/src/portalnet/types/distance.rs -> trin-types/src/distance.rs

How was it fixed?
To-Do

[x] Add entry to the release notes (may forgo for trivial changes)
[x] Clean up commit history

Going ahead with the merge on this one - since it's a blocker on extracting the validation types. But it's worth pinging @ogenev for a retrospective review on this. Mostly since I've moved some types into ethportal-api. Since they were all jsonrpc related, it felt like an appropriate home for them. But, I'd like to get confirmation on that. If you feel like they are better housed inside trin-types, I'm happy to make that change in a future pr

@njgheorghita  I think we should keep ethportal-api as encapsulated as possible and not couple it with Trin (i.e. trin specific types).
It seems for types that are Trin specific, a better place would be the newly created trin-types crate in jsonrpc.rs file for example.

authors: njgheorghita ogenev

repo: ethereum/trin


text:
transactionIndex is always 0

I started testrpc with the option -b 10 to mine a block every 10 senconds.
If I have many transactions in the same block, all transactions have the transactionIndex field equal to 0.

see PR https://github.com/ethereumjs/testrpc/pull/253

This should have been closed when Tim merged the PR. Thanks again for your contribution, @mpolci!

authors: benjamincburns mpolci

repo: ethereumjs/testrpc


text:
Integration testing GC (storage incentives)

128-node balanced cluster is started with

empty storage,
retrieval caching switched off and
reserve and localstore cache storage capacity set to a small value on all nodes (reserve=2^8, cache=2^4)

uploader buys 3 batches of postage stamps A, B and C with different impayment amounts and equal conveniently huge size (batch depth = 20)
uploader uploads random data to the storer node using batch A B C repeatedly uploading chunks (a0, b0, c0, a1, b1, c1,.... an, bn, cn)
after each upload (fk) random nodes would retrieve n uploaded chunks of batch C starting from the one that was first uploaded (c0, c1, .... cn)
until it is found that cj is no longer retrievable. after ca. 30K chunks
now go through
continue uploading

Integration testing reserve:
Assume two data blobs (both the size of the Swarm network and uniformly distributed). Blob A has lower-value postage stamps than blob B. The nodes in the network are uniformly distributed
Two scenario's:

Upload A, then B. Validate if B is retrievable and A not.
Upload B, then A. Validate if B is retrievable and A not
alternate uploading A and B. Validate if B is retrievable and A not

Integration testing cache:
Assume two data blobs (both the size of the Swarm network and uniformly distributed). Both blobs have expired postage stamps and the nodes are uniformly distributed.
Three scenario's:

Without retrieval. Upload A, then B. Validate if B is retrievable and A not.
Upload half of B (B0), then half of A (A0). Access B0, upload other half of B (B1) or other half of A (A1). Validate if B0 can be accessed.

Integration testing reserve:
Assume two data blobs (both the size of the Swarm network and uniformly distributed). Blob A has lower-value postage stamps than blob B. The nodes in the network are uniformly distributed
Two scenario's:

Upload A, then B. Validate if B is retrievable and A not.
Upload B, then A. Validate if B is retrievable and A not
alternate uploading A and B. Validate if B is retrievable and A not

Integration testing cache:
Assume two data blobs (both the size of the Swarm network and uniformly distributed). Both blobs have expired postage stamps and the nodes are uniformly distributed.
Two scenario's:

Without retrieval. Upload A, then B. Validate if B is retrievable and A not.
Upload half of B (B0), then half of A (A0). Access B0, upload other half of B (B1) or other half of A (A1). Validate if B0 can be accessed.

repo: ethersphere/bee


text:
fix cors preflight headers bug

Closes #1376.
It is not a completely clean solution, as currently, it returns all Bee's custom headers across all endpoints, while a better solution would be to return only those that the endpoint indeed supports. But that would require quite a more complex support structure in the code that I was not really keen to introduce. I think this will make the work done, but it will require having it in mind when new headers are added to propagate them in here as well.

Not sure what to do about the failing test.

@AuHau the failing tests are because this PR is from a fork, not from the ethersphere repo. Will get someone else to review this too, and we can merge it nevertheless

authors: AuHau acud


text:
fix: rename swarm key

Checklist

[x] I have read the coding guide.
[ ] My change requires a documentation update, and I have done it.
[x] I have added tests to cover my changes.
[x] I have filled out the description and linked the related issues.

Description
In a new node wallet.key will be created instead of swarm.key. In an old node the swarm.key will be renamed to wallet.key on start. Due to this, downgrading the node won't be possible because of the name change.
Open API Spec Version Changes (if applicable)

Motivation and Context (Optional)

Related Issue (Optional)
fixes #4023
Screenshots (if appropriate):

Frankly, I am not qualified/experienced enough in bee to give a proper reason for the change. I am just looking around to contribute to this project and I found https://github.com/ethersphere/bee/issues/4023 in the good first issues.


text:
EthStorage Devs Meeting #92 Agenda

Meeting Info

Aug 06, 2024, 11:00 UTC+8
Duration: 60 minutes
Meeting link
Anyone can comment on the agenda where they would like this to be discussed.

Agenda

Protocol/App/Research progress
BD/Marketing progress

Code review for disk-back cache and ethstorage-sdk (TODO: ethstorage-sdk)
On-Chain ecosystem investigation
Vitalik blog workflow

https://x.com/VitalikButerin/status/1792076476344312240
https://github.com/qzhodl/blog
https://niuhaizai.eth.limo

submitted the inbox contract spec v2 to upstream: https://github.com/ethereum-optimism/specs/pull/284
now polishing the spec for l2 blob.

Read besu parallel evm and bonsai design: link1 link2
Writing a proposal on parallel evm, summarizes and compares risechain polygon besu implementations.
Testing and add UTs for parallel evm on geth.

Spec review with Alan for inbox contract
Have a hotpot with V and share EthStorage for his blog.  Got some feedback.

https://github.com/ethstorage/es-node/pull/306#issuecomment-2268510235
https://github.com/ethstorage/es-node/issues/312
https://github.com/ethstorage/es-node/pull/310
https://github.com/ethstorage/es-node/pull/187
https://github.com/ethstorage/web3url-gateway/pull/31

https://github.com/ethstorage/optimism/pull/51
Review Bill's code

The EthStorage-SDK version has been updated to support Calldata upload files and optimize synchronization locks.
ethfs-cli integrates the latest SDK.

exchange quarterly report
upcoming event:
8/11-12 foresight hk, 8/17-18 ethshenzhen, 8/23-25 ethtokyo, 09/01-09/07 kbw, 09/12-14 ethnapul in italy (already confirmed)

authors: Akagi201 blockchaindevsh dajuguan iteyelmp qizhou qzhodl syntrust yazhenwish

repo: ethstorage/pm


text:
lowercase the config

[x] update the config to be lowercase
[x] update the test config
[x] update everywhere configs are mentioned

a new release will need to get but after this PR to update fidesops and fidesctl

@sanders41 thanks!

repo: ethyca/fideslib


text:
Incomplete OID Retrieval: SNMP Walk (nextCmd/bulkCmd) Fails to Capture All OIDs

Hi everyone,
I'm encountering an issue with PySNMP where the SNMP walk is not retrieving all the expected OIDs.
The last few OIDs that PySNMP manages to retrieve are as follows:
1.3.6.1.2.1.43.8.2.1.14.1.2 = Samsung Electronics
1.3.6.1.2.1.43.8.2.1.15.1.1 = Samsung Internal Input Tray
1.3.6.1.2.1.43.8.2.1.15.1.2 = Samsung External Media Handler
1.3.6.1.2.1.43.8.2.1.15.1.2 = No more variables left in this MIB View
...only 515 results
When I use a standard SNMP utility, it successfully retrieves 4700 results, and the point where PySNMP stops corresponds to a null value:
.1.3.6.1.2.1.43.8.2.1.14.1.1 = String: "Samsung Electronics"
.1.3.6.1.2.1.43.8.2.1.14.1.2 = String: "Samsung Electronics"
.1.3.6.1.2.1.43.8.2.1.15.1.1 = String: "Samsung Internal Input Tray"
.1.3.6.1.2.1.43.8.2.1.15.1.2 = String: "Samsung External Media Handler"
.1.3.6.1.2.1.43.8.2.1.16.1.1 = Null:
.1.3.6.1.2.1.43.8.2.1.16.1.2 = Null:
.1.3.6.1.2.1.43.8.2.1.17.1.1 = String: "0001"
...continues to rest 4700 results
At the precise moment when the SNMP Utility returns null, PySNMP prematurely stops, suggesting a potential error handling issue.
Is there a setting I am missing?
Steps to Reproduce:
#error_indication, error_status, error_index, var_binds = cmd_gen.bulkCmd(
    cmdgen.CommunityData('public', mpModel=0),
    cmdgen.UdpTransportTarget(([device_ip], 161), timeout=20, retries=2),
    0, 50,
    '1.3',  # Starting OID for the walk
    maxRows=0,
    maxCalls=0,
    lookupMib = True,
    lexicographicMode = True,
    ignoreNonIncreasingOid = False,
)
if error_indication:
    print(f"Error: {error_indication}")
    return 'Error Indication'

if error_status:
    print(f"Error: {error_status}")
    return 'Error Status'

if error_index:
    print(f"Error: {error_index}")
    return 'Error Index'

# Process the results
for var_bind_table_row in var_binds:
    for name, val in var_bind_table_row:
        print(f"{name.prettyPrint()} = {val.prettyPrint()}")`

Expected Behavior:
I expected the SNMP walk using PySNMP to retrieve all the specified OIDs.
Actual Behavior:
PySNMP retrieves less than 600 OIDs, and the SNMP walk stops at a point where there is a null value. This behavior is inconsistent with the results obtained from the standard SNMP utility.
Additional Information:
The standard SNMP utility used for comparison is SNMP Utility. - Download Utility here
No error messages are provided by PySNMP; the walk simply stops prematurely.
My environment details:
Python Version: 3.8
PySNMP Version: 4.4.12
Operating System: windows 10

There were quite a few reports on walk operations, so you need to enable debugging https://www.pysnmp.com/pysnmp/examples/#using-these-examples and then compare to those.

Hi @lextm,
Thank you for your prompt response. I have utilized the debug command as suggested and have collected the following results from my snmp walk:
When the returned value is null (observed in the standard SNMP walk results) no errors are raised. The error-status is 'noError'. But it stops everytime a null value is introduced in the walk. I conducted the walk from various angles, consistently obtaining the same results. In the alternative SNMP utility, there are over 300 null values from 4700 values, all reacting the same when I change the walk root subtree.
I am eager to contribute to resolving this issue, given that SNMP walking is a critical component of my application. I am willing to assist with development or provide any information needed for debugging. If you prefer, I am open to allowing you to log onto my machine for direct debugging.
Here is a snippet of the response for the OID with a null value:

2023-11-20 09:53:51,897 pysnmp: sendPdu: current time 5 ticks, one tick is 0.5 seconds
2023-11-20 09:53:51,897 pysnmp: sendPdu: new sendPduHandle 727660, timeout 40.0 ticks, cbFun <bound method CommandGenerator.processResponsePdu of <pysnmp.entity.rfc3413.cmdgen.BulkCommandGenerator object at 0x000002B3F98A7DC0>>
2023-11-20 09:53:51,911 pysnmp: sendPdu: MP succeeded
2023-11-20 09:53:51,915 pysnmp: receiveMessage: msgVersion 0, msg decoded
2023-11-20 09:53:51,917 pysnmp: receiveMessage: MP succeded
2023-11-20 09:53:51,917 pysnmp: receiveMessage: PDU GetResponsePDU:
request-id=2315122
error-status=noError
error-index=0
variable-bindings=VarBindList:
VarBind:
name=1.3.6.1.2.1.43.8.2.1.16.1.1
value=ObjectSyntax:
simple=SimpleSyntax:
empty=
2023-11-20 09:53:51,928 pysnmp: sendPdu: current time 5 ticks, one tick is 0.5 seconds
2023-11-20 09:53:51,936 pysnmp: sendPdu: new sendPduHandle 727661, timeout 40.0 ticks, cbFun <bound method CommandGenerator.processResponsePdu of <pysnmp.entity.rfc3413.cmdgen.BulkCommandGenerator object at 0x000002B3F98A7DC0>>
2023-11-20 09:53:51,938 pysnmp: sendPdu: MP succeeded
2023-11-20 09:53:51,940 pysnmp: receiveMessage: msgVersion 0, msg decoded
2023-11-20 09:53:51,942 pysnmp: receiveMessage: MP succeded
2023-11-20 09:53:51,943 pysnmp: receiveMessage: PDU GetResponsePDU:
request-id=2315124
error-status=noError
error-index=0
variable-bindings=VarBindList:
VarBind:
name=1.3.6.1.2.1.43.8.2.1.16.1.1
value=ObjectSyntax:
simple=SimpleSyntax:
empty=

Here is a response from a oid that returns Samsung External Media Handler:

2023-11-20 09:53:51,830 pysnmp: sendPdu: current time 4 ticks, one tick is 0.5 seconds
2023-11-20 09:53:51,843 pysnmp: sendPdu: new sendPduHandle 727659, timeout 40.0 ticks, cbFun <bound method CommandGenerator.processResponsePdu of <pysnmp.entity.rfc3413.cmdgen.BulkCommandGenerator object at 0x000002B3F98A7DC0>>
2023-11-20 09:53:51,879 pysnmp: sendPdu: MP succeeded
2023-11-20 09:53:51,892 pysnmp: receiveMessage: msgVersion 0, msg decoded
2023-11-20 09:53:51,894 pysnmp: receiveMessage: MP succeded
2023-11-20 09:53:51,895 pysnmp: receiveMessage: PDU GetResponsePDU:
request-id=2315120
error-status=noError
error-index=0
variable-bindings=VarBindList:
VarBind:
name=1.3.6.1.2.1.43.8.2.1.15.1.2
value=ObjectSyntax:
simple=SimpleSyntax:
string=Samsung External Media Handler
2023-11-20 09:53:51,897 pysnmp: receiveMessage: cache read by sendPduHandle 727659
2023-11-20 09:53:51,897 pysnmp: receiveMessage: processResponsePdu succeeded
2023-11-20 09:53:51,897 pysnmp: sendPdu: securityName s-5824012256909706693, PDU
GetNextRequestPDU:
request-id=2315122
error-status=noError
error-index=0
variable-bindings=VarBindList:
VarBind:
name=1.3.6.1.2.1.43.8.2.1.15.1.2
value=ObjectSyntax:
simple=SimpleSyntax:
empty=

I appreciate your assistance and look forward to your guidance on resolving this matter.
Best regards,
Christo

I managed to find a better solution for walking.
https://github.com/lextudio/pysnmp
@lextm thanks for forking the above and improving it :)

https://github.com/lextudio/pysnmp

Then the changes might come from pysnmp community patches (from Splunk or others) that have been integrated into 5.0 releases.
You can read #429 to learn more about the ecosystem changes.

Again appreciate the initiative @lextm!

authors: Christo-Deyzel lextm

repo: etingof/pysnmp


text:
Rework command line interface

Use subcommand instead of option arguments. This has the benefit of supporting shell wildcards.
Old usage:
checksec -f /bin/true --no-color
checksec -d /bin --json --pretty
checksec -p bash --maps
checksec --pid 1,42
checksec -P

New usage:
checksec --no-color exe /bin/true
checksec --format json-pretty exe /bin
checksec proc-name --maps bash
checksec proc-id 1 42
checksec proc-all

checksec proc-id $(pidof firefox)
checksec exe /bin/system*
dpkg -L apt | checksec

Alternative to #25

Thanks for all the PRs! I appreciate your contributions to the project.
I was planning on migrating to clap derive CLI, just haven't had time to work much on checksec.rs for the past while.
Plan is to separate things like proc-id proc-name, proc-all into their own subcommands of the proc subcommand, I'll do this work and reference your PR for the next version bump.

authors: cgzones etke


text:
Test with pylint

pylint

Canceled.

repo: etri-edgeai/nn-comp-discblock


text:
Change source folder name to target name

Swift Package Manager looks for a target’s source files at predefined search paths and in a subdirectory with the target’s name. This PR changes the subdirectory to the target name.
https://swiftinit.org/docs/swift-package-manager/packagedescription/target.path

Rename applied to main branch

Change applied to main

authors: GierlJn phisakel


text:
Update frontend nextJS to 13.4.7

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Work merged in as:
https://github.com/euanwm/OpenWeightlifting/pull/200

repo: euanwm/OpenWeightlifting


text:
Replacing only the data of the currently floating notification without generating a new notification

Hello. I am making good use of vue-notification.
I am writing an issue to explain my case and get advice to everyone who uses this library.
Problem
I'm writing a code that notify data in a notification using a custom template (slot).
// custom template
<notifications group="custom-notify" position="bottom right">
  <template slot="body" slot-scope="{ item, close }">
      // markup notify display 'name', 'price', 'quantity' from item.data
  </template>
</notifications>

// this.$notify call
this.$notify({
  group: 'custom-notify',
  duration: 3000,
  data: {
    id: '1',
    name: 'A',
    price: 30000,
    quantity: 25,
  } // example data
})

// examples of data (occured randomly)
{
    id: '1',
    name: 'A',
    price: 30000,
    quantity: 25,
},
{
    id: '2',
    name: 'B',
    price: 2000,
    quantity: 3,
},
{
    id: '3',
    name: 'A',
    price: 29990,
    quantity: 3,
},
{
    id: '4',
    name: 'B',
    price: 2500,
    quantity: 100,
}

In this case(four example datas),
If this.$notify is called with an interval of 3 seconds or more (longer than the duration) in the order of the 4 objects above, the previous notification is cleared by the duration, so a total of 4 notifications will occur.
However, when this.$notify is called 4 times within 3 seconds, I want to initialize(reset) the duration(3 seconds) of the notification with the same name and change only the price and quantity of the notification (in the end, only 2 notifications for A and B are displayed.
I wonder if there are any ways or API option for this.
If not, may I ask for feature support?
Thank you

For Someone newcomers, here's a link to the good answer to my question.(In my case)
https://github.com/kyvg/vue3-notification/issues/19

repo: euvl/vue-notification

license: mit


text:
Style error with position="bottom right" / notifications appearing outside container

Hi,
Version 1.3.7
Component code:
<notifications group="watchtower" position="bottom right"></notifications>

Resulting style applied to notification:
position: fixed;
top: 15px;
width: 300px;
transition: all 0.3s ease-in-out;
right: 15px;

Triggering code:
app.$notify({
  group: 'watchtower',
  type: e.data.type,
  title: e.data.title,
  text: e.data.text,
  duration: 10000
});

It actually seems like the notification is being placed outside of the notifications container? Any idea why this would happen? Screenshot of DOM: http://cloud.roberttolton.com/0j0b121F1z1y

Still having an issue with this - it seems like I can't override any of the defaults using the props of the component.

Closing this, as it turns out the package uiv-bootstrap added their own notifications that replicate the settings of this one, without me even realising (and they still work), and it's overriding this package. Will need to either individually import the uiv-bootstrap components that I want, or just fully switch to theirs.


text:
Test Gradle plugin shadow to generate fatjars

https://github.com/johnrengelman/shadow
Thanks @juan-medina

-rw-r--r-- 1 robot robot    184680 Jun  8 22:28 ev3dev-lang-java-0.6.1-all.jar
-rw-r--r-- 1 robot robot    184761 Jun  8 22:36 ev3dev-lang-java-all-0.6.1.jar

Fixed


text:
Add return of Youtube results

IF I search a song/artist
THEN the page displays list of results

Top 10 results?
Displays title of video and description
Add HTML of clickable results links

My branch can currently add one video based on a search result

Figured out how to display list of buttons of top ten results with title. Working on making them clickable to send you to display the video.

authors: AllysonMcGrath ggamb

repo: evalecillos/T-B-D


text:
google/gemma-7b-it

Model introduction
This model card corresponds to the 7B instruct version of the Gemma model. You can also visit the model card of the 2B base model, 7B base model, and 2B instruct model.
Model URL
https://huggingface.co/google/gemma-7b-it
Data type
float16
Additional instructions (Optional)
No response
Author
No
Security

[X] I confirm that the model is safe to run which does not contain any malicious code or content.

Integrity

[X] I confirm that the model comes from unique and original work and does not contain any plagiarism.

gemma-2b-it
HE+:

MBPP+:

gemma-2b
HE+:

MBPP+

gemma-7b-it
HE+:

MBPP+:

authors: FatPigeorz msoftware

repo: evalplus/evalplus


text:
Support for nested routes

Disclaimer: I'm new to Elm, so everything written below might make no sense, but I think a support for nested routes (pretty much how it's done in Ember) would be pretty nice.
Let's say, we have a product page, and routable tabs with relevant info, such as specs and reviews. The correspondent urls would look like /products/1/specs and /products/1/reviews. Upper half of the page would be basic product info, that comes with product data from API, while only second half changes by making a request, something like: give me reviews for this product. Meanwhile with current approach both cases would have to be described as separate paths and resolved upon visit from scratch.
Yes, it's probably possible to figure out the way to check if part of the data was already loaded and skip that part of resolution. But wouldn't it be nicer to represent the parsed path as a list of meaningful segments, like: Segment (Product 1) (Segment Reviews End) with type type Path a = End | Segment a (Path a)
That would allow to tell right away that if Segment haven't changed then resolution and call to an API is unnecessary. As well as pick the correct function for inner view. And nesting can be arbitrary.
Does it make sense?

Do you mind asking about this on https://discourse.elm-lang.org/ or http://elmlang.herokuapp.com/ and refining the question? There should be a way to do what you want, but it is pretty different than what happens in Ember as far as I can tell from what you said. (Explicitly tracking what data you have loaded.) Others on the various community forums can help you work through what that might look like and the various tradeoffs from what you did with Ember.

authors: evancz youroff

repo: evancz/url-parser


text:
broken example for file handling

Consider http://evanplaice.github.io/jquery-csv/examples/file-handling.html
Environment

Platform: Safari and FIrefox

Steps to reproduce
After the csv file is uploaded, nothing happens.
Expected behaviour
The csv data should be parsed.
Actual behaviour
Nothing happens

Thank you for the report, I'm on it

Adding
var global=window;
to helpers.js solved the issue

Fixed in v1.0.20
The JSDelivr CDN takes its sweet time to flush the cache. It should be working by tomorrow.

FWIW, the CDN still doesn't seem to be flushed.
http://evanplaice.github.io/jquery-csv/examples/helpers.js
still lacks the global declaration as of today.

authors: XenonofArcticus dntzbgh evanplaice neihcnim

repo: evanplaice/jquery-csv


text:
🛑 www.actionherojs.com is down

In 47e891b, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 8e07b66.

repo: evantahler/upptime


text:
🛑 www.actionherojs.com is down

In c03a530, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 7a047f4.


text:
🛑 www.actionherojs.com is down

In f588b8d, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 99478cb.


text:
VW eGolf --> car connected fehlerhaft

Describe the bug
EVCC zeigt dauerhaft "connected = true" und "Vehiclepresent = true". VW-ID funktioniert. Der "Plug-Status" der ID-Api funktioniert (VW-Mqtt zeigt den connect status korrekt an).
In Evcc wird dieser Status aber wohl nicht abgerufen und Status des Vehicle bleibt dauerhaft auf present, egal ob der Stecker gesteckt ist oder nicht.
Durch den fehlerhaften Status schaltet Evcc nicht korrekt ab, wenn das Fahrzeug nicht disconnected ist.
Log zeigt mit abgestecktem Fahrzeug!
Configuration details
# open evcc at http://evcc.local:7070
network:
  schema: http
  host: evcc.local # .local suffix announces the hostname on MDNS
  port: 7070

log: info
levels:
  cache: error

# unique installation id
plant: 228338ad890436cb326541d6d857494277eded7d521e1e70090ad271b127a919

interval: 10s # control cycle interval

meters:
- type: template
  template: fronius-solarapi-v1
  usage: grid
  host: 192.168.178.108
  name: grid1234
- type: template
  template: fronius-solarapi-v1
  usage: pv
  host: 192.168.178.108
  name: pv1234

chargers:
- type: template
  template: fritzdect
  uri: http://192.168.178.1/
  user: xxx
  password: xxx
  ain: xxx
  standbypower: 5
  name: wallbox1234

vehicles:
- type: template
  template: id
  title: eGolf
  user: xxx
  password: xxx
  vin: xxx
  capacity: 35.8
  name: eGolf
  #mode: pv
  #minSoC: 40
  #targetSoC: 58

loadpoints:
- title: Ladepunkt
  charger: wallbox1234
  vehicle: eGolf
  mode: pv
  soc:
    poll:
      mode: always
      interval: 60m
    estimate: true

  enable:
    threshold: -1000
    delay: 1m
  disable:
    threshold: 1000 # maximum import power (W)
    delay: 10m
  guardduration: 1m

site:
  title: Ladepunkt
  meters:
    grid: grid1234
    pv: pv1234

tariffs:
  currency: EUR # (default EUR)
  grid:
    # static grid price
    type: fixed
    price: 0.3099 # [currency]/kWh

  feedin:
    # rate for feeding excess (pv) energy to the grid
    type: fixed
    price: 0.122 # [currency]/kWh

# mqtt message broker
mqtt:
  broker: 192.168.178.103:1883
  topic: evcc # root topic for publishing, set empty to disable publishing
  # clientid: foo
  # user:
  # password:

Log details
evcc  | [main  ] INFO 2024/01/07 21:40:05 evcc 0.123.7
evcc  | [main  ] INFO 2024/01/07 21:40:05 using config file: /etc/evcc.yaml
evcc  | [main  ] INFO 2024/01/07 21:40:05 starting ui and api at :7070
evcc  | [db    ] INFO 2024/01/07 21:40:05 using sqlite database: /root/.evcc/evcc.db
evcc  | [mqtt  ] INFO 2024/01/07 21:40:05 connecting evcc-1975050073 at tcp://192.168.178.103:1883
evcc  | [lp-1  ] WARN 2024/01/07 21:40:07 poll mode '{always 1h0m0s}' may deplete your battery or lead to API misuse. USE AT YOUR OWN RISK.
evcc  | [lp-1  ] WARN 2024/01/07 21:40:07 phases not configured, assuming 3p
evcc  | [site  ] INFO 2024/01/07 21:40:09 site config:
evcc  | [site  ] INFO 2024/01/07 21:40:09   meters:      grid ✓ pv ✓ battery ✗
evcc  | [site  ] INFO 2024/01/07 21:40:09     grid:      power ✓ energy ✗ currents ✗
evcc  | [site  ] INFO 2024/01/07 21:40:09     pv 1:      power ✓ energy ✗ currents ✗
evcc  | [site  ] INFO 2024/01/07 21:40:09   vehicles:
evcc  | [site  ] INFO 2024/01/07 21:40:09     vehicle 1: range ✓ finish ✓ status ✓ climate ✓ wakeup ✓
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09 loadpoint 1:
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09   mode:        pv
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09   charger:     power ✓ energy ✓ currents ✗ phases ✗ wakeup ✗
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09   meters:      charge ✓
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09     charge:    power ✓ energy ✓ currents ✗
evcc  | [lp-1  ] INFO 2024/01/07 21:40:09 vehicle updated: unknown -> eGolf
evcc  | [site  ] WARN 2024/01/07 21:40:09 interval <30s can lead to unexpected behavior, see https://docs.evcc.io/docs/reference/configuration/interval
evcc  | [lp-1  ] INFO 2024/01/07 21:40:12 car connected

What type of operating system are you running?
Linux
Version
0.123.7

Der Connected status ist etwas das die Wallbox liefern muss und deine Steckdose kann das nicht.

Wäre es vorstellbar, dass das als neue Funktion in EVCC implementiert werden kann; also der Car-Status von extern kommen kann (MQTT oder ähnliches)? Das Problem ohne den korrekten Status ist, dass Evcc immer die Ladung anschmeißt, obwohl kein Fahrzeug angesteckt ist.

Mit einem custom charger https://docs.evcc.io/docs/devices/chargers/#manuell und mqtt Plugin https://docs.evcc.io/docs/reference/plugins#mqtt-lesenschreiben kann man da was machen. Aber bedenke bitte, dass nur weil die VW API eine Verbindung meldet es nicht an der Steckdose sein muss, sondern auch an irgendeiner anderen Wallbox sein kann.

Das Problem ohne den korrekten Status ist, dass Evcc immer die Ladung anschmeißt, obwohl kein Fahrzeug angesteckt ist.

Solange der "Verbrauch" unterhalb von standbypower liegt, wird keine Ladung gestartet (Status bleibt auf "B"). Im UI sollte dann "ladebereit, warte auf Fahrzeug" angezeigt werden.

Das hat mit dem Golf nichts zu tun sondern ist eine prinzipbedingte Einschränkung der Schaltsteckdosen. Der Verbindungsstatus kann nicht erkannt werden.

repo: evcc-io/evcc