build: Network Types

Goal
We should have software-level support for different network types, e.g. celestia-devent or celestia-mainnet
Current solution
In upcoming https://github.com/celestiaorg/celestia-node/pull/57 this is solved by simply extending Config with a network type field.
Desired solution
The network type should be hardcoded in binary, as different network types usually run over different software versions, and allowing users to manually change network type is a source of bugs coming from users joining a network with a software version we were not expecting.

We will also need to define and formalize a list of running network types with supporting bootstrap peers.

Need a hardcoded list of peers for DEVNET.

In upcoming #57 this is solved by simply extending Config with a network type field.

I still think the easiest is to create a directory to contain the genesis & config file. It is common that these are either in a separate repo (example: https://github.com/osmosis-labs/networks) or in the main repo itself (example1, example2).

Need a hardcoded list of peers for DEVNET.

I think a set of bootstrap peers could be part of the above directory.

@liamsi, It has to be part of the binary so its hash commits to network params

Based on my investigations over in devops-test/devnet I'd recommend we only include the genesis.json and gentx files and not the config.
See my recent PRs that moved from mounting config files to using a flag in docker-compose and k8s.
If we wanted to provide a recommendation for initial peer setup I think we should use an env file.

Actually, hard coding genesis hash only would work well enough.


Delete ProQuest code

Description
This deletes the ProQuest importer, and adds a migration to delete any references to it in the database.
Motivation and Context
The ProQuest importer has effectively been replaced by the generic OPDS 2.0 importer, and so this old ProQuest-specific code is no longer necessary. We don't want to continue maintaining it (and the test suite).
Affects: https://www.notion.so/lyrasis/Remove-Proquest-Importer-042377d14c3f4b55b6f5a88f997a8a41
How Has This Been Tested?
I configured a ProQuest collection locally and added it to a library. I then deleted all of the ProQuest code.
After the deletion, I restarted the CM. The CM started up correctly, but when navigating to the configured collection in the Admin UI, the collection showed up as being a generic OPDS 1.0 collection.
After running the migration SQL, the collection was gone, and everything continued to work.
Checklist

[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.

The proquest_import_monitor is still in the simplified crontab, otherwise looks pretty deleted to me +1

I'll delete this. I left the proquest_import_monitor script itself as a compatibility stub that tells you that you shouldn't be using it anymore. I wasn't sure if anyone would be calling this manually.
If we're OK with it, I can delete both! :hammer:

We can certainly delete the cron job, I think.
On Mon, Jan 30, 2023 at 3:44 PM Mark Raynsford @.***>
wrote:

The proquest_import_monitor is still in the simplified crontab, otherwise
looks pretty deleted to me +1
I'll delete this. I left the proquest_import_monitor script itself as a
compatibility stub that tells you that you shouldn't be using it anymore. I
wasn't sure if anyone would be calling this manually.
If we're OK with it, I can delete both! 🔨
—
Reply to this email directly, view it on GitHub
https://github.com/ThePalaceProject/circulation/pull/767#issuecomment-1408337978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVRR5S7EHP2Q5D4CO7UG64LWU6H6PANCNFSM6AAAAAAUHOQ3VA
.
You are receiving this because your review was requested.Message ID:
@.***>


devicetree: remove label property accessors

These were first deprecated in v3.2. We have kept support for them for as long as we can, but now their presence is causing CI failures in some configurations. Specifically, using the deprecated 'label' property is causing a warning which is promoted to an error in some twister runs. This is blocking other forward progress in the devicetree API.
I tried to rework the tests to avoid this, but it was too much effort for the time I had to work on the task. Removing the APIs is therefore unfortunately the best way forward to unblocking other work.
Re-work the test suite a bit to maintain coverage where we are using the label property to test other macros.
Add a migration guide section to help with the transition.

@kartben Thanks for the reminder! I think there is no problem here, though. That document states:

Hotfixes can be merged at any time after CI has passed and are excluded from most of the conditions listed above.

Where a hotfix is defined as an issue that is blocking development. This certainly qualifies. I have added the label since it was missing just for the record.

Sounds good, thank you!


Add Gamepad spec to data

https://w3c.github.io/gamepad/
We need to be able to reference it from webxr-gamepads-1

I don't know whether I ever added it to Shepherd or not, but it's in WebRef, so it's now in the database.


Advances in expressions following Simons work.

Refactors and implements many new expressions specified by @sbodorkos here in Procedures 1 - 4 as part of an on-going effort.  Also adds in an exemplar of Topsoil displaying the synthetic dataset CM2 by @noahmclean .

Good to see CM2 still gets around.


update babel and ts config, remove 'React' imports

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Steps to reproduce

Does this PR introduce a user-facing change?

Does this PR require documentation?

@sgalsaleh Need another review when you have a moment. Resolved some merge conflicts after the embedded cluster working group stuff got merged.


ADD: Make the SideBar Partial Component

Tech Required: React,  CSS
Color Scheme:

Back Ground Color : var(--main)
Text Color : var(--text)

Other Specifications Include the sidebar should be static meaning fixed upon scroll
What to do?.

Find the Side Bar Folder in the Partials Directory
Populate the file namely SideBar.jsx with the code
Use Global CSS root selectors
Name the classes for the scope of the File only
Do not use global tags such as (a, h1, h2, body, etc..) in the CSS files.

Need any help ask me here or on Discord...

i am on it , pls assign me man

This Issue is still open and now I have added a file sidebar.jsx make changes on that file only

Okay @N-coder-bot
It seems I have to complete the whole project 😞


[3.2]  Remove the unnecessary sync() and the restrictions it imposes on 3D Physics.

3.2 version of  #42167.

Thanks!


Want to use -insecureDockerRegistry when pulling docker images

Currently -insecureDockerRegistry can be used only when DIEGO_DOCKER_CACHE=true.
I think this flag should allow to launch a docker image hosted on a private registry.

Hi, @nakaji-s,
Yes, I agree that we'd like to support a whitelist of insecure private registries from which to allow staging and running Docker images on CF. I've added https://www.pivotaltracker.com/story/show/100495522 to the Diego tracker and prioritized it in our Docker-specific track, and I expect we'll get to it soon.
Thanks for the request!
Best,
Eric, CF Runtime Diego PM

Thanks for adding a story to the pivotaltracker, @ematpl.
Cheers!


Cloud Speech Ruby Veneer: @private Methods not marked a private

Several methods are documented as @private in the comment but not actually marked private in the ruby source code, should they be?  E.g. https://github.com/GoogleCloudPlatform/google-cloud-ruby/blob/master/google-cloud-speech/lib/google/cloud/speech/stream.rb#L265

These methods are documented correctly. The @private directive is used by YARD to indicate that the method is not part of the public API. It does not describe the method level of access. This is used because ruby does not have the notion of package-level access, so these methods need to be public, even though they are not part of the public API. These methods can change in future versions without breaking backwards compatibility.

@pbogle Hope this is satisfactory, please reopen if not.

Thanks for the explanation, sounds good.


Update Codecov ghaction

New test.

Codecov is now running as expected. A base report is missing which is why there's no comparison in the Codecov report comment. This should be resolved when this PR is merged (as there'll be an uploaded coverage report on this commit).


is kv cache used for inference?

Hi
I would like to use the inference code but I want to know if it uses kv cache? And can I configure the size of the kv cache for inference?
Thanks

Yes, K V cache is automatically use in our inference,
and the size of the kv cache will be automatically malloced depends on your inputs pormpt, you don't need configure any thing.

Thanks for the explanation!

Runyu

On Thu, Sep 28, 2023 at 00:44 Dong, Bo @.***> wrote:

Closed #378
https://urldefense.com/v3/__https://github.com/intel/intel-extension-for-transformers/issues/378__;!!IKRxdwAv5BmarQ!dKA2TjLYlMZIPRkUfMjHR-bYbx1s1IsnXE00NiZ1VVX5ufU8-MZC1ElhFGvf4kiqNV9FI7BPsX61m3_HAQw2iQ$
as completed.
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/intel/intel-extension-for-transformers/issues/378*event-10495690610__;Iw!!IKRxdwAv5BmarQ!dKA2TjLYlMZIPRkUfMjHR-bYbx1s1IsnXE00NiZ1VVX5ufU8-MZC1ElhFGvf4kiqNV9FI7BPsX61m3_tT17MWg$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ADMNK6TLADMTIGJJ7PL3AR3X4UTAZANCNFSM6AAAAAA5D7UDRE__;!!IKRxdwAv5BmarQ!dKA2TjLYlMZIPRkUfMjHR-bYbx1s1IsnXE00NiZ1VVX5ufU8-MZC1ElhFGvf4kiqNV9FI7BPsX61m39nW9q1aQ$
.
You are receiving this because you authored the thread.Message ID:
<intel/intel-extension-for-transformers/issue/378/issue_event/10495690610@
github.com>


Initial report for Group 7

Initial report can be found here.

Review of Group 7 from Group 4 since we couldn't find a Group 6
Things you did well:

We liked that were able to use the blocking strategy in your code to help optimize your code.
The write up was well done and showed the weak and strong scaling for the OpenMP and tuned code
Noticing that using Canon's algorithm should help in this case

Things you could improve on:

It looked like from your code that you currently aren't using any copy optimization techniques. You might want to look into this in order to reduce the amount of cache thrashing that could be going on.
Your section on the MPI implementation is a little fuzzy. It is a little hard to tell what matrix you are doing the domain decomposition on as in are you doing it on L or Lnew. If you are doing it on L be careful since all the processor's will use that matrix during their calculations if you think of how the two matrices correspond to their matrix matrix multiplication counterparts.

Review from Team 5:
Good things:

The plan to implement Canon's Algorithm to improve memory efficiency seems like a good future goal.
As you mentioned in future plans, a simple loop re-ordering in your inner kernel and a change to a k-j-i order (as opposed to the base j-i-k) is a good idea. It improved the data access pattern for us, and greatly improved the performance.
Report contains properly documented scaling studies for the tuned OpenMP implementations.

Remarks:

The pull request did not include the mentioned "path-mpi.c" file. We could not locate the repos of the other members, and therefore could not review the relevant MPI implementation.
We believe that there is gain in manual vectorization of the inner kernel. We got significant improvements over the auto-vectorized version.
After doing the proposed domain decomposition through an MPI implementation, you could also incorporate the insights gained from your experiments with OpenMP in your code.
Lastly, offloading to the phis is a very achievable target.

Review from Team 6:
Strengths

Good idea to build upon what you learned in the matmul implementation to implement Floyd-Warshall (blocking, loop ordering, etc)
Very clear scaling studies shown for the original and tuned parallel implementations
MPI strategy was well-explained

Things to Consider

Some sections in your report were a bit unclear. Particularly for me, I wasn't sure if the two parallel tuned versions you talked about in your tuned scaling studies were the aforementioned blocking and loop-ordering schemes, or something different.
Could look into other techniques from matmul, such as copy optimization, memory alignment (_mm_malloc, _mm_free), AVX instructions, etc, if you have time

Closing pull request to open final report pull request.


added dsa sheet

added dsa sheet
Pull Request
Description
i have added a dsa sheet
Closes #
Type of change

[x] Adding a new Resource
[ ] Adding a new Category
[ ] Documentation enhancement or fixes
[ ] Website enhancement or fixes

Checklist:

[x] I read carefully CONTRIBUTING.md
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Screenshots (if appropriate):
Please add screenshots to help explain your changes.
Additional

This PR is duplciate
https://github.com/jfmartinz/ResourceHub/tree/main/Data Structures and Algorithm (DSA)#practice-sheet


Bump apache-axi2 version

Purpose

$subject
Packing changes in https://github.com/wso2/wso2-axis2/pull/241

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/1685961529

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/1685961529
Status: success


Refactor McMsg implementation

Description
We currently call this rreqtable, we should change this (and improve) the implementation of this table, in order to fix possible bugs, and also, to catch up with the latest draft.
List of things to do

Rename to McMsg Set (probably with a 3 letter acronym to be more ergonomic when coding).
Catch up with the standard.
Add proper documentation.
Verify it doesn't have race conditions.

See also

draft-perkins-manet-aodvv2-03, Section 4.6. Multicast Message Set

This is done.


UserWarning: No parser explicitly specified

UserWarning: No parser was explicitly specified, so I'm using the best available HTML parser for this system ("lxml"). This usually isn't a problem, but if you run this code on another system, or in a different virtual environment, it may use a different parser and behave differently.

The code that caused this warning is on line 389 of the file /usr/local/lib/python3.6/dist-packages/wikipedia/wikipedia.py. To get rid of this warning, pass the additional argument 'features="lxml"' to the BeautifulSoup constructor.

  lis = BeautifulSoup(html).find_all('li')

First of all thanks for this wonderful Package. It is really useful for my web scraper code.
I am getting the above warning. Which is not an error or issue but it would be nice to keep your package perfect.

This issue has already been fixed, as shown here:
https://github.com/goldsmith/Wikipedia/blob/2065c568502b19b8634241b47fd96930d1bf948d/wikipedia/wikipedia.py#L389
However, @goldsmith still needs to push the updated package up to PyPI so people can use the updated version on there.
As a temporary fix for this, you can install the module directly from this repo using the following command:
python -m pip install --upgrade git+git://github.com/goldsmith/Wikipedia.git

This command replaces your current installation of the wikipedia module with the most recent version from here on GitHub.

#107


RC override in SITL not working

Sending manual control or rc override commands to the SITL through Mavros does not seem to work.
I posted a message on the forum (http://discuss.px4.io/t/sitl-remote-control-simulation/6993 ) that has more details. I found other people having a similar problem with rc override, but no real answer. I am looking for information to know if it is indeed not enabled in the SITL or if I'm doing something wrong.
I have attached the code from my node for information.
rc_simulator_node.txt
Thanks
[Update]
Using the mavlink shell I can see that the px4 SITL is indeed receiving the input_rc message.
However, it doesn't receive manual_control_setpoint (although it is being published by Mavros). I'll update again if I can figure out what's happening.
[Update 2]
I didn't pay enough attention, manual_control works great. Mavros publishes to manual_control/control (and not subscribes as I originally thought) and subscribes to manual_control/send. I published to the /send topic and the drone took off.

https://github.com/PX4/Firmware/blob/master/src/modules/simulator/simulator_mavlink.cpp does not handle RC_CHANNELS_OVERRIDE. That's why it's not processing them. If you do want it supported, you need to add the handler there.

Thanks!

Actually, no. Whatever you send through Mavros is processed independent of simulator_mavlink. The simulator module only handles communication between the simulator (e.g Gazebo) and PX4 executable.
The standard mavlink module (mavlink_receiver) handles communications with Mavros. https://github.com/PX4/Firmware/blob/master/src/modules/mavlink/mavlink_receiver.cpp#L1676-L1732.

@mhkabir right but then that means this issue is not solved, unless @Torgenn is making some mistake on the ROS side.

Do we have a resolution to this issue? A working example perhaps.


Multi-thread UDP support for statsd agent

With golang finally (1.11) supporting SO_REUSEPORT this agent could be upgraded to also support it to avoid drops off the UDP buffer.
https://groups.google.com/forum/#!msg/golang-dev/HAEaU5TakTU/ZfMLVLqEBAAJ
https://go-review.googlesource.com/c/go/+/72810

Kernel 3.9+ is required to use this so there would need to be some soft of warning or switching mechanism to turn it on/off.


Class \Hyva\Admin\Model\GridSourceType\RepositorySourceType$repo does not exist

Generate error sometimes while running setup:upgrade command.
Error: Class \Hyva\Admin\Model\GridSourceType\RepositorySourceType$repo does not exist

Which Magento version are you running?

@Vinai
Magento version is : 2.3.4-p2

@Vinai
might be duplicate of issue.
But still check once.

Ah yes, probably the same issue then.
As I've said there, I'll be happy to merge a related PR, but it will still be a little while until I get around to doing it myself.


Update virtualenv installation method.

Changes Unknown when pulling f79adedecd0329fd5f663c0cd4b6a6aad970df02 on akatsoulas:update-documentation into ** on mozilla:master**.

Not directly related to this PR but since it's more related to docs, please remove peep references from requirements/prod.txt comments.

r+


Error when using run image without bash

Only for very specific stacks, the processes are started with direct: true which doesn't require a bash to be present.
If you use a run image for another stack, bash will be used.
Expected Behavior

It should work by calling the process directly.
Current Behavior

If no bash is present on the run image, you get the error
ERROR: failed to launch: bash exec: no such file or directory

Possible Solution

I see 2 possible solutions

This is staight forward - just supprt BUILDPACK_API 0.9 like discussed in this issue. Then all processes would be started directly.

Introduce an environment variable BP_DIRECT_PROCESS (defaults to false) which controls how to set direct.

Steps to Reproduce

Unfortunately, it is not possible to reproduce with paketo images since bionic.tiny and jammy.tiny are hardcoded to work. noble.tiny would be broken too, but unfortunately, there is no builder yet released with noble (why?).
But I created this simple nodejs based sample to reproduce.
Motivations

We want to use a minimal run image and not having a bash in there for no real reason.

This sounds like a reasonable workaround until the new libcnb version is out. @dmikusa wdyt?

This sounds like a reasonable workaround until the new libcnb version is out. @dmikusa wdyt?

I agree and would also appreciate taking this workaround in while we do not have a concrete upgrade plan to libcnb@v2. In particular, because even with a plan in place, we would probably still talk about weeks if not months until the procfile would be based on v2 and the problem be fixed. @paketo-buildpacks/utilities-maintainers WDYT?

It sounds good to me. I have a few minor notes about how we phrase this, but functionality is 👍.


gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory

I encountered this error when I ran sh make.sh .
(deformable_base37) hpcstack@hpcstack:/home/shenxiaochen/Deformable-DETR/models/ops$ sh make.sh
running build
running build_py
running build_ext
/home/hpcstack/.local/lib/python3.7/site-packages/torch/utils/cpp_extension.py:370: UserWarning: Attempted to use ninja as the BuildExtension backend but we could not find ninja.. Falling back to using the slow distutils backend.
warnings.warn(msg.format('we could not find ninja.'))
building 'MultiScaleDeformableAttention' extension
gcc -pthread -B /home/hpcstack/anaconda3/envs/deformable_base37/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/shenxiaochen/Deformable-DETR/models/ops/src -I/home/hpcstack/.local/lib/python3.7/site-packages/torch/include -I/home/hpcstack/.local/lib/python3.7/site-packages/torch/include/torch/csrc/api/include -I/home/hpcstack/.local/lib/python3.7/site-packages/torch/include/TH -I/home/hpcstack/.local/lib/python3.7/site-packages/torch/include/THC -I/home/hpcstack/anaconda3/envs/deformable_base37/include/python3.7m -c /home/shenxiaochen/Deformable-DETR/models/ops/src/cpu/ms_deform_attn_cpu.cpp -o build/temp.linux-x86_64-cpython-37/home/shenxiaochen/Deformable-DETR/models/ops/src/cpu/ms_deform_attn_cpu.o -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="_libstdcpp" -DPYBIND11_BUILD_ABI="_cxxabi1011" -DTORCH_EXTENSION_NAME=MultiScaleDeformableAttention -D_GLIBCXX_USE_CXX11_ABI=0 -std=c++14
gcc: fatal error: cannot execute ‘cc1plus’: execvp: No such file or directory
compilation terminated.
error: command '/usr/bin/gcc' failed with exit code 1

Same issue here, did you find any way around it?


Serialize any object to JSON

With version 3.0, Is there any easy way to serialize an object to JSON without changing their model spec? I don't want to define columns as JSONColumn. Just want to take an object of a model and serialize it to JSON.

So in other words you'd like to flatten a SquiDB model object to a set of key-value pairs as JSON? This isn't a built-in function, but it should be very easy to implement yourself -- you can use AbstractModel#getMergedValues() on any model object to get a set of key-value pairs for the current state of that model. This will be represented as a ValuesStorage object, on which you can call valuesSet() to get a Set<Map.Entry<String, Object>>, and then write those key-value pairs to a JSON string using your favorite JSON library.
This also isn't restricted to 3.0 -- getMergedValues() exists in 2.0 as well, although it returns a ContentValues. The same idea would apply though. Hope that helps!

@sbosley Thanks! That worked!
public JSONObject modelObjectToJson(TableModel obj) {
    JSONObject jobj = new JSONObject();
    try {
        for (Map.Entry<String, Object> s : obj.getMergedValues().valueSet()) {
            jobj.put(s.getKey(), s.getValue() == null ? "" : s.getValue());
        }
    } catch (JSONException e) {
        Log.d(this.toString(), e.getMessage());
        e.printStackTrace();
    }
    return jobj;
}

I was thinking about the next step and taking a cursor and turn that into a JSONArray. But having trouble guessing the model type and iterating over the cursor.

👍 glad that worked!
In terms of guessing the model type, I'd suggest passing around the model class that you passed to SquidDatabase.query() and using that. You can then get an instance using modelClass.newInstance() and use readPropertiesFromCursor() to populating it. The cursor iteration itself is just like iterating over a standard android cursor; all the same methods are available.


Cannot import composables

any support for composables? like defineShortcuts...

As of Nuxt UI Vue v1.0.1-beta.1, you can now be able to import the defineShortcuts, useCopyToClipboard, useShortcuts and useToast composables.

Great job. I like nuxt ui a lot, but we has built a stable workflow in our project, so we cannot use nuxt at all. But I want to use the nuxt UI. So lucky to find this project. Thanks a lot.


Disconnection of AP in MQTT example ssl_mutual_auth (IDFGH-3996)

Hello guys,
Unfortunately I get a disconnection at random time delay of the esp when I am connected to the AP with MQTT. Maybe this is an error of the esp-idf? Or is it my fault?
I tested the ssl_mutual_auth example and I get the output:
...
TOPIC=/topic/qos0
DATA=data
I (6529) MQTTS_EXAMPLE: MQTT_EVENT_DATA
TOPIC=/topic/qos0
DATA=data
I (140179) wifi:state: run -> init (ce00)
I (140179) wifi:pm stop, total sleep time: 112679992 us / 138324504 us
I (140179) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:6
I (140189) example_connect: Wi-Fi disconnected, trying to reconnect...
E (140199) TRANS_SSL: ssl_poll_read select error 113, errno = Software caused connection abort, fd = 54
E (140199) MQTT_CLIENT: Poll read error: 0, aborting connection
I (140209) MQTTS_EXAMPLE: MQTT_EVENT_DISCONNECTED
I (140319) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:6
I (140319) wifi:state: init -> auth (b0)
I (140319) wifi:state: auth -> assoc (0)
I (140319) wifi:state: assoc -> run (10)
...
Thank you.
Kind Regards,
Alex

@alexanderabc Hi Alex,
Could you please share the version of ESP-IDF you use? Is the same issue reproducible also on some release branch/tab?
Do these disconnect happen also when running only the example itself or do you run some more complex application?
Could you please enable debug/verbose logging? It would be nice to see what's happening just before getting disconnected. Otherwise, looking at your log, it just looks like a normal WiFi disconnection, resulting in MQTT layer disconnection afterwards.
Thanks,
David

I am seeing the same (or a similar) issue (disconnection of AP wifi:state: run -> init (ce00)) with my project that i updated to the current esp-idf master (as of today):
I (1938) SipClient: OK :)  <-- Registering to the SIP server succeeded, no more data traffic afterwards.
I (11368) wifi:state: run -> init (ce00)
I (11368) wifi:pm stop, total sleep time: 0 us / 10330504 us

I (11368) wifi:new:<1,0>, old:<1,1>, ap:<255,255>, sta:<1,1>, prof:1
I (11468) wifi:state: init -> init (ce00)
I (11498) wifi:new:<1,1>, old:<1,0>, ap:<255,255>, sta:<1,1>, prof:1
I (11498) wifi:state: init -> auth (b0)
I (11498) wifi:state: auth -> assoc (0)
I (11508) wifi:state: assoc -> run (10)
I (11518) wifi:connected with MySSID, aid = 4, channel 1, 40U, bssid = 12:34:56:78:90:10
I (11518) wifi:security: WPA2-PSK, phy: bgn, rssi: -71
I (11518) wifi:pm start, type: 0

I (11568) wifi:AP's beacon interval = 102400 us, DTIM period = 1
I (12148) esp_netif_handlers: sta ip: <IP_ADDRESS>, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (12148) main: got ip:<IP_ADDRESS>
I (24038) wifi:state: run -> init (ce00)

My code is https://github.com/chrta/sip_call/tree/3392eac0f54ad9b779994cd62d3f655c75c3e114 (with that revision and without any power-safe-mode enabled).
Before updating my code to the current esp-idf master it ran fine and i did not have these disconnects.

For my deauth issue i did a git bisect (which was not a nice experience, since a lot of commits did not build, ./install.sh or . ./export.sh did not work):
The offending commit is https://github.com/espressif/esp-idf/commit/7cf59a8d185edecc7e000321d90c6ae76e8dd9e9 The previous commit on master works fine.

Hello,
IDF-Version: v4.2-dev-2084-g98d5b5dfd
I just adjusted the code with:
const esp_mqtt_client_config_t mqtt_cfg = {
.uri = URL,
.event_handle = mqtt_event_handler,
.cert_pem = (const char *)aws_root_ca_crt_start,
.client_id = Client_ID,
.client_cert_pem = (const char *)client_cert_pem_start,
.client_key_pem = (const char *)client_key_pem_start,
.disable_auto_reconnect = true
}
I think there should be no problems...?
If I disable MQTT there is no error, does this make sense :)?
This is the debug output:
V (28103) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (29103) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (30103) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (31103) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
I (31643) wifi:state: run -> init (ce00)
I (31643) wifi:pm stop, total sleep time: 21301691 us / 28926080 us
I (31643) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:6
I (31653) example_connect: Wi-Fi disconnected, trying to reconnect...
E (31653) TRANS_SSL: ssl_poll_read select error 113, errno = Software caused connection abort, fd = 54
E (31663) MQTT_CLIENT: Poll read error: 0, aborting connection
D (31673) MQTT_CLIENT: Reconnect after 10000 ms
I (31683) MQTTS_EXAMPLE: MQTT_EVENT_DISCONNECTED
I (31783) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:6
I (31783) wifi:state: init -> auth (b0)
I (31783) wifi:state: auth -> assoc (0)
I (31783) wifi:state: assoc -> run (10)
I (31813) wifi:connected with WIFI-123456, aid = 97, channel 1, BW20, bssid = 12:34:56:78:90:10
I (31813) wifi:security: WPA2-PSK, phy: bgn, rssi: -50
I (31813) wifi:pm start, type: 1
I (31853) wifi:AP's beacon interval = 104448 us, DTIM period = 1
I (32553) esp_netif_handlers: example_connect: sta ip: xx.xx.xx.xx, mask: <IP_ADDRESS>, gw: <IP_ADDRESS>
I (32553) example_connect: Got IPv4 event: Interface "example_connect: sta" address: xx.xx.xx.xx
I (33553) example_connect: Got IPv6 event: Interface "example_connect: sta" address: xx:xx:xx:xx type: ESP_IP6_ADDR_IS_LINK_LOCAL

Also this output occurs in another project:
V (00:07:38.898) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (00:07:39.898) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (00:07:40.898) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
V (00:07:41.898) MQTT_CLIENT: mqtt_message_receive: transport_read(): no data or EOF
I (463643) wifi:state: run -> init (ce00)
I (463653) wifi:pm stop, total sleep time: 369217957 us / 459715630 us
I (463653) wifi:new:<1,0>, old:<1,0>, ap:<255,255>, sta:<1,0>, prof:6
D (00:07:42.232) event: running post WIFI_EVENT:5 with handler 0x400ef5f0 and context 0x3ffca820 on loop 0x3ffc0d8c
0x400ef5f0: wifi_default_action_sta_disconnected at C:/esp-idf/components/esp_wifi/src/wifi_default.c:103
D (00:07:42.234) esp_netif_handlers: esp_netif action disconnected with netif0x3ffcac34 from event_id=5
D (00:07:42.246) esp_netif_lwip: check: remote, if=0x3ffcac34 fn=0x400e8a1c
0x400e8a1c: esp_netif_down_api at C:/esp-idf/components/esp_netif/lwip/esp_netif_lwip.c:1135
D (00:07:42.258) esp_netif_lwip: esp_netif_down_api esp_netif:0x3ffcac34
D (00:07:42.261) esp_netif_lwip: esp_netif_dhcpc_cb lwip-netif:0x3ffcacb4
D (00:07:42.263) esp_netif_lwip: esp_netif_start_ip_lost_timer esp_netif:0x3ffcac34
D (00:07:42.275) esp_netif_lwip: if0x3ffcac34 start ip lost tmr: interval=120
D (00:07:42.287) esp_netif_lwip: esp_netif_start_ip_lost_timer esp_netif:0x3ffcac34
D (00:07:42.288) esp_netif_lwip: if0x3ffcac34 start ip lost tmr: already started
D (00:07:42.300) esp_netif_lwip: check: local, if=0x3ffcac34 fn=0x400e9258
0x400e9258: esp_netif_update_default_netif_lwip at C:/esp-idf/components/esp_netif/lwip/esp_netif_lwip.c:163
D (00:07:42.301) esp_netif_lwip: esp_netif_update_default_netif_lwip 0x3ffcac34
V (00:07:42.312) esp_netif_objects: esp_netif_next_unsafe 0x0
V (00:07:42.314) esp_netif_lwip: esp_netif_is_netif_up esp_netif:0x3ffcac34
V (00:07:42.325) esp_netif_objects: esp_netif_next_unsafe 0x3ffcac34
V (00:07:42.326) esp_netif_lwip: esp_netif_is_netif_up esp_netif:0x3ffca580
V (00:07:42.338) esp_netif_objects: esp_netif_next_unsafe 0x3ffca580
D (00:07:42.349) esp_netif_lwip: call api in lwip: ret=0x0, give sem
D (00:07:42.350) event: running post WIFI_EVENT:5 with handler 0x400da650 and context 0x3ffd4a58 on loop 0x3ffc0d8c
0x400da650: wifi_st_wifi_event_handler at c:\work\test\build/../components/comm/src/st_event_handler.c:15
E (00:07:42.352) TRANS_SSL: ssl_poll_read select error 113, errno = Software caused connection abort, fd = 54
E (00:07:42.376) MQTT_CLIENT: Poll read error: 0, aborting connection
D (00:07:42.389) MQTT_CLIENT: Reconnect after 10000 ms
V (00:09:42.267) esp_netif_objects: esp_netif_next_unsafe 0x0
D (00:09:42.268) esp_netif_lwip: esp_netif_ip_lost_timer esp_netif:0x3ffcac34
D (00:09:42.269) esp_netif_lwip: if0x3ffcac34 ip lost tmr: raise ip lost event

And this one occurs while subscribing:
D (00:00:06.995) MQTT_CLIENT: mqtt_enqueue id: 44449, type=8 successful
D (00:00:06.996) OUTBOX: ENQUEUE msgid=44449, msg_type=8, len=79, size=79
D (00:00:07.011) MQTT_CLIENT: Sent subscribe topic=$aws/things/xx/shadow/update/delta, id: 44449, type=8 successful
E (00:00:07.031) MQTT_CLIENT: mqtt_message_receive: transport_read() error: errno=0
E (00:00:07.033) MQTT_CLIENT: mqtt_process_receive: mqtt_message_receive() returned -1
D (00:00:07.048) MQTT_CLIENT: Reconnect after 10000 ms
Thank you ;)

@chrta @alexanderabc Thanks for providing more details and finding the offending commit. Can you please share the brand and the model of your AP?
It has been confirmed that some routers don't comply with WiFi standards (specifically related to the TFS field in beacon packets) so that we are experiencing random disconnects on such devices after the 7cf59a8 been merged/backported. This issue has been reported on ASUS N66U router, so far.

I use the following setup:

https://mikrotik.com/product/hex_s firmware version 6.45.8 (as CAPsMAN manager)
https://mikrotik.com/product/cap_ac firmware version 6.45.8 (managed by CAPsMAN)

There are A LOT of settings possible. Most of them are left in default, but i can change them if you provide some hints.

@chrta @alexanderabc Thanks for providing more details and finding the offending commit. Can you please share the brand and the model of your AP?
It has been confirmed that some routers don't comply with WiFi standards (specifically related to the TFS field in beacon packets) so that we are experiencing random disconnects on such devices after the 7cf59a8 been merged/backported. This issue has been reported on ASUS N66U router, so far.

You can try to  check disconnected reason once you got WIFI_EVENT_STA_DISCONNECTED:
wifi_event_sta_disconnected_t *disconnected = (wifi_event_sta_disconnected_t *) event_data;
ESP_LOGI(TAG,"Disconnect reason: %d", disconnected->reason);

I cannot reproduce this problem any more. The current esp-idf master seems to work fine now. The only thing that changed on my side is that i compiled and flashed from another PC. The router and AP did not reboot since the problem appeared. Maybe it was some issue with my development environment/esp-idf clone.

I (463643) wifi:state: run -> init (ce00)
I (463653) wifi:pm stop, total sleep time: 369217957 us / 459715630 us

This disconnect reason is WIFI_REASON_AP_TSF_RESET.
This is similar to https://github.com/espressif/esp-idf/issues/5915
What is your router/ap model?

@chrta @alexanderabc Thanks for providing more details and finding the offending commit. Can you please share the brand and the model of your AP?
It has been confirmed that some routers don't comply with WiFi standards (specifically related to the TFS field in beacon packets) so that we are experiencing random disconnects on such devices after the 7cf59a8 been merged/backported. This issue has been reported on ASUS N66U router, so far.

I might misunderstand, do you mean no such disconnect issue before 7cf59a8 ?
It seems there are several models of AP have such issue (https://github.com/espressif/esp-idf/issues/5915),
so I'm not sure if it's AP's problem or ESP32's problem.

Hi @chrta @alexanderabc ,
Abort this issue I (31643) wifi:state: run -> init (ce00)
We have solved this issue. Fix commit is  3c3bff6eb

Thanks for reporting, feel free to reopen.

Hi @chrta @alexanderabc ,
Abort this issue I (31643) wifi:state: run -> init (ce00)
We have solved this issue. Fix commit is 3c3bff6

Was this fix merged into release 4.3?

i have the same error, the disconnect reason is WIFI_REASON_ASSOC_LEAVE. this happens only when i output a lot of info in the serial for debugging purposes. can the reason be in a task hanging?

i have the same error, the disconnect reason is WIFI_REASON_ASSOC_LEAVE. this happens only when i output a lot of info in the serial for debugging purposes. can the reason be in a task hanging?

i have the same error, the disconnect reason is WIFI_REASON_ASSOC_LEAVE. this happens only when i output a lot of info in the serial for debugging purposes. can the reason be in a task hanging?

@ogghst
Please create a new issue with detail log and your esp-idf version (git describe --tags)

E (100120) TRANS_TCP: tcp_poll_read select error 113, errno = Software caused connection abort, fd = 54
E (100120) MQTT_CLIENT: Poll read error: 119, aborting connection
I (100130) MQTT_TEST: MQTT_EVENT_DISCONNECTED
I (100130) MQTT_CLIENT: Client force reconnect requested
I (100140) MQTT_TEST: Other event id:7
I am using esp-idf version 4.3.4

Please provide me the solution


RHIROS-388 - fixed store already initialized error

Background:
We were facing 'store already initliazed' error on ROS service page while switching between ROS service and other services. This PR fixes the issue.
Jira Card: https://issues.redhat.com/browse/RHIROS-388

Codecov Report

Merging #71 (7ffa7b3) into main (0eb4945) will increase coverage by 0.02%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main      #71      +/-   ##
==========================================
+ Coverage   12.20%   12.23%   +0.02%
==========================================
  Files          28       28
  Lines         418      417       -1
  Branches       92       92
==========================================
  Hits           51       51
  Misses        340      340
+ Partials       27       26       -1

Impacted Files
Coverage Δ

src/AppEntry.js
0.00% <0.00%> (ø)

src/store/index.js
0.00% <0.00%> (ø)

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 0eb4945...7ffa7b3. Read the comment docs.

Thank you @PreetiW for a fix!
Thank you @karelhala for details and review.


Result form: Make form buttons consistent with indicator form

Issue
With Satsuma, we introduced a new convention of form buttons to the Indicator add/setup form that we'd like to make consistent throughout the product.
Acceptance criteria
Adding a result

[ ] 1. Replace "Save changes" button with "Save and close" button identical to the one on the indicator form. Clicking it has the following effects:

[ ] 1.1. Result is saved and appears as expected on the program page.

[ ] 1.2. Auto-dismissing green Pnotify appears in the lower left corner of the screen that says:

Success
Result was added to [RFTier] indicator [indicatorNumber].

[ ] 2. Replace "Reset" button with "Cancel" button identical to the one on the indicator form.

[ ] 3. In between the "Save changes" and "Cancel" buttons is a "Save and add another" button identical to the one on the indicator form. It has the following effects:

[ ] 3.1. Result is saved and appears as expected on the program page.

[ ] 3.2. New "Add result" form is loaded, with the same three buttons at the bottom.

[ ] 3.3. Auto-dismissing green Pnotify appears in the lower left corner of the screen, identical to the one described above for the "Save and close" button.

[ ] 4. All form field validation is preserved.

[ ] 5. All confirmation and rationale prompts are preserved.

Editing a saved result

[ ] 1. Only the "Save changes" and "Cancel" buttons appear. There is no "Save and add another" button.

Random UI detail

[ ] 1. Please add an asterisk to the form label inside the evidence section, "Link to file or folder". It is a required field, so it needs this symbol.

Housekeeping (where applicable)

[ ] Unit test/s written
[ ] i18n strings included
[ ] Is accessible to people using screen readers

Looking into this, I think it will require Reactifying this modal and the Program page. This is probably more work than I anticipated & a better task for @sanjuroj or @camgnostic

I'd also like to emphasize that this is NOT a must have for Satsuma follow-up release... certainly if it is risky from a regressions standpoint and will be a medium to high level effort from a development and QA testing standpoint.

It's not risky & it isn't even particularly difficult. But what I thought would be a <4hr task is more like 1–2 days for me


CI: update bart cli release asset

Currently the bart cli release asset is for linux amd64 but its name doesn't signify this.  Consider updating the name to add the arch extension... and perhaps add other arch combos 😉

@karthik2804 and I are thinking of tackling this when we add support for Mac and Windows CLIs, either via cross-compilation or via build hosts.

The bart cli release section has been updated with Linux, macOS and Windows. We compressed each of the bart files and named them accordingly and then also performed the shasum and also added those checksum values to the checksum test file.
I was just not able to build on macos-aarch64 for now. Perhaps we can look at that one also down the track.
For now the naming convention on all of the files (using separate architecture) and the hashing is all sorted.


Update python-packages.csv for machine learning packages

These are not Azure SDK packages.
They are not open-source, nor are published under open-source licenses. They have no open customer support channel (e.g. github issues).
Publishing their docs alongside Azure SDK package gives implication that these packages would meet the same guidelines as an Azure SDK package.
So I would be very uncomfortable with this.

@danieljurek
Packages not released through engsys are still eligible to use this pipeline, and as we mentioned in the GH issue, these are supplementary packages to azure-ai-ml. From an organization standpoint, it is certainly easier for our customers if all AzureML packages have their reference docs in one place rather than being scattered across various MSDocs pages.


SW - Failed to parse end node produceEvents

Describe the bug
For an end node with produceEvents in one of the states like below, build fails to parse the produceEvent element.
{
"name": "ErrorWithCompensation",
"type": "operation",
"actions": [
{
"functionRef": "logProcessContext"
}
],
"end": {
"terminate": true,
"compensate": true,
"produceEvents": [{
"eventRef": "FailureEvent",
"data": {
"error": ".error",
"replay": true
},
"contextAttributes": {
"correlationid": ".someId"
}
}]
}
}
Expected behavior
Build should pass and event produced at end node should contain the data object as defined.
Actual behavior
Build fails parsing the sw definition with following error.
Failed to build quarkus application: io.quarkus.builder.BuildException: Build failure: Build failed due to errors
[ERROR]         [error]: Build step org.kie.kogito.quarkus.common.deployment.KogitoAssetsProcessor#generateSources threw an exception: org.kie.kogito.codegen.process.ProcessCodegenException: Processes with errors are Invalid process: 'xxx.sw.json'. Found error: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "error" (class io.serverlessworkflow.api.produce.ProduceEvent), not marked as ignorable (3 known properties: "eventRef", "data", "contextAttributes"])
[ERROR]  at [Source: UNKNOWN; byte offset: #UNKNOWN] (through reference chain: io.serverlessworkflow.api.Workflow["states"]->java.util.ArrayList[1]->io.serverlessworkflow.api.states.OperationState["end"]->io.serverlessworkflow.api.produce.ProduceEvent["error"])
How to Reproduce?
No response
Output of uname -a or ver
Windows 11
Output of java -version
java 17
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
999-snapshot
Build tool (ie. output of mvnw --version or gradlew --version)
gradle 8.6
Additional information
No response

@deepakkapoor23 There is a mismatch between the spec and the Java SDK. The spec mentions that data might be an object or a string but here data is defined as string https://github.com/serverlessworkflow/sdk-java/blob/2.0.x/api/src/main/resources/schema/events/eventref.json
I think this should be fixed in the SDK. Please open the issue there
In the meantime, as a workaroung, use
{
"name": "ErrorWithCompensation",
"type": "operation",
"actions": [
{
"functionRef": "logProcessContext"
}
],
"end": {
"terminate": true,
"compensate": true,
"produceEvents": [{
"eventRef": "FailureEvent",
"data":  "{
error: .error,
replay: true
}",
"contextAttributes": {
"correlationid": ".someId"
}
}]
}
}

@fjtirado I have noticed that the data element does not honor either the string or an object, it always attempts to publish entire workflow data as "data" element regardless of what's define in the workflow definition.


improve use of alternate socket location

Stops mpvc from getting caught in the grep when using --socket

Thanks!


pgadmin4: 7.7 -> 7.8

Description of changes
Update of pgadmin4. Release notes
Includes fixes from #262702
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 262707 run on x86_64-linux 1

8 packages built:

pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
python310Packages.flask-security-too
python310Packages.flask-security-too.dist
python311Packages.flask-security-too
python311Packages.flask-security-too.dist

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2804

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 262707 run on x86_64-linux 1

8 packages built:

pgadmin4
pgadmin4-desktopmode
pgadmin4-desktopmode.dist
pgadmin4.dist
python310Packages.flask-security-too
python310Packages.flask-security-too.dist
python311Packages.flask-security-too
python311Packages.flask-security-too.dist

applied changes from #262702

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2936

rebased due to above mentioned fix being merged

Superseded by #269432.


'amplify update auth' is broken for new projects for new<EMAIL_ADDRESS>?

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v14.17.1
Amplify CLI Version
7.6.4
What operating system are you using?
Ubuntu 20.04
Amplify Categories
auth
Amplify Commands
update
Describe the bug
I've recently had two issues, one has something to do with the date and time, when I'm manually configuring cognito the amplify api settings, the second which is occurring now has to do with the amplify update auth:
I've followed the instruction verbatim, however I may be worried I've deleted a role or policy on my account by accident that may allow for using parts of the amplify cli. I'm not sure.
When I get to the stage where I amplify add api, I can make the generic taskapp without issue, it will generate the tables, and I can run mutations and queries. However when I try to run 'amplify update auth' and utilize cognito user pools for the next part, where auth is included, I get the following:
amplify update api? Select from one of the below mentioned services: GraphQL
🛑 Cannot read property 'serviceType' of undefined
TypeError: Cannot read property 'serviceType' of undefined
    at getResourcesToBeCreated (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:220:65)
    at AmplifyToolkit.getResourceStatus [as _getResourceStatus] (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:117:35)
    at updateWalkthrough (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/service-walkthroughs/appSync-walkthrough.ts:439:50)
    at updateNonContainerResource (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/index.ts:260:63)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Object.executeAmplifyCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/index.ts:223:5)
    at executePluginModuleCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:204:3)
    at executeCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/index.ts:205:5)

a similar result follows if I try amplify update auth
Expected behavior
Before, I had no problems, and I was able to go through the workflow, and make my user groups, and add auth to the application.
Right now there's something very frustrating and unexplained happening. I'm not sure if I've somehow deleted a key permission or role. Something is wrong.
Reproduction steps
verbatim
GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line
$amplify update api

Select from one of the below mentioned services: GraphQL
🛑 Cannot read property 'serviceType' of undefined
TypeError: Cannot read property 'serviceType' of undefined
    at getResourcesToBeCreated (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:220:65)
    at AmplifyToolkit.getResourceStatus [as _getResourceStatus] (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:117:35)
    at updateWalkthrough (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/service-walkthroughs/appSync-walkthrough.ts:439:50)
    at updateNonContainerResource (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/provider-utils/awscloudformation/index.ts:260:63)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at Object.executeAmplifyCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-api/src/index.ts:223:5)
    at executePluginModuleCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:204:3)
    at executeCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/index.ts:205:5)

$amplify update auth
Please note that certain attributes may not be overwritten if you choose to use defaults settings.

You have configured resources that might depend on this Cognito resource.  Updating this Cognito resource could have unintended side effects.

Cannot read property 'serviceType' of undefined
TypeError: Cannot read property 'serviceType' of undefined
    at getResourcesToBeCreated (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:220:65)
    at AmplifyToolkit.getResourceStatus [as _getResourceStatus] (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/extensions/amplify-helpers/resource-status-data.ts:117:35)
    at getAuthResourceName (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-auth/src/utils/getAuthResourceName.ts:4:50)
    at Object.run (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-auth/src/commands/auth/update.ts:58:49)
    at Object.executeAmplifyCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/node_modules/@aws-amplify/amplify-category-auth/src/index.js:421:23)
    at /home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:222:45
    at executePluginModuleCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:204:9)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at executeCommand (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/execution-manager.ts:30:5)
    at Object.run (/home/papi/.nvm/versions/node/v14.17.1/lib/node_modules/@aws-amplify/cli/src/index.ts:205:5)

Additional information
No response

Hi @peter-greekbase
Can you paste amplify-meta.json file here , will help in debugging the issue?
Make sure to redact any secret info present in the file

@peter-greekbase if you're still having problems, please open a new issue or provide the requested information here and we can reopen.


add inspirations:honey fluid to data tags forge/tags/fluids/honey for…

For processing fluid recipes, and as shown in F3, this adds the honey fluid to the forge tag for compatibility
Lower right side

Added in 9c313c7


Scene/preset support

Feature Request
MC could have the ability to save the current display settings (or some aspects of the display settings) as a scene/present and an option to invoke it both via keyboard shortcuts and the app menu (alternatively there could be a scene editor where the user could change which aspects of controls and values are part of a scene).
(note: it is debatable whether such a functionality should be a scope of MonitorControl or not).

@cprcrack wrote in https://github.com/MonitorControl/MonitorControl/issues/795

Before opening the issue, have you...?

[X] Searched for existing issues

Is your feature request related to a problem? Please describe
Having used different brightness settings, this is what I use every day:
During the day: integrated LCD at 100%, external monitor at 50%
During the night: integrated LCD at 50%, external monitor at 0%
Instead of manually moving two sliders every few hours, I would like being able to create and quickly switch to simple presets.
Describe the solution you'd like
I want to be able to create presets for the current brightness configuration. Basically a button that saves the current brightness configuration and allows me to give it a custom name, for example "DAY" or "NIGHT". Then a menu option to quickly switch to those presents from the popup. That way I can simply click on "DAY" or "NIGHT" every day when I want (I'm not interested in anything that automates this, I really prefer to switch manually but in a click).
Describe alternatives you've considered
Haven't found alternative software that does this, just presets that are too fancy or depend on apps opened, day or time or things I'm not interested.
Anything else?
I can imagine a good place for this feature would be an extra "Presets" tab on the Preferences window, where current presets are listed in a simple list view with a + and - buttons. With + you can create a new one from the current config, and with - you can delete Presets you don't want anymore. No need to being able to edit them, you can simply choose a current present from the popup and create a new one based on that from the Presets tab. It could be limited to 4 presets for example so that the popup menu is never too big, because that's were you should be able to select the presets you want to apply, so that it's very quick to do.
Let me know if I can help in any way!


Add Reactions API

Add the following methods:

reactions_add
reactions_get added in #139
reactions_list
reactions_remove

Implementation should be similar to the chat methods in chat.rs. Most, if not all, of the models already exist (e.g. SlackApiReactionAddRequest would be composed of SlackChannelId, SlackReaction, and SlackTs).

I cannot currently assign myself to this issue or push a new branch to create a pull request. Does someone need to grant me permissions?

Hey, @jtmichelson
It seems you want to propose some PR and the changes which is great ❤
In order you do that you just need to follow common GitHub flow:

Fork a repository
Create a feature branch
Create a PR from your fork to this repository with the changes

Let me know if you need help with this.

Awesome updates, release in v1.3.3 🎉


Unstable_TrapFocus.js is causing Maximum call stack size exceeded. (4.0.0-alpha.10)

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
I have:

"@material-ui/core": "4.11.0", (upgraded from 4.10.0)
"@material-ui/pickers": "4.0.0-alpha.10", (upgraded from 4.0.0-alpha.5)

After fixing the adaptations with props in pickers (autoOk, invalidDate, error removal etc), I saw that while my FormComponent wrapper works OK in a normal page -> but it causes the maximum call stack size exceeded if the form control is displayed in a ModalDialog from material-ui and results with fast open/closing of the Popover from the DatePicker.
I also noticed that if I put a debug point in Unstable_TrapFocus.js at the line that's causing the infinite calls, the DatePicker Popover display properly. (debug point on rootRef.current.focus();)
      if (rootRef.current && !rootRef.current.contains(doc.activeElement)) {
        rootRef.current.focus();
      }

Expected Behavior 🤔
The DatePicker popover should not cause maximum call stack size exceeded and should display. :)
Steps to Reproduce 🕹
I will try to create a sample codesandbox issue later.
Context 🔦
Unstable_TrapFocus.js:77 Uncaught RangeError: Maximum call stack size exceeded.
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at HTMLDocument.contain (Unstable_TrapFocus.js:77)
    at Day.tsx:174
    at commitHookEffectListMount (react-dom.development.js:19731)
    at commitPassiveHookEffects (react-dom.development.js:19769)
    at HTMLUnknownElement.callCallback (react-dom.development.js:188)
    at HTMLUnknownElement.dispatchEvent (<anonymous>)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:237)
    at invokeGuardedCallback (react-dom.development.js:292)
    at flushPassiveEffectsImpl (react-dom.development.js:22853)

Duplicate of #1852


Consider removing tests for install instructions

The instructions to install the library (in INSTALL.md) include the dependencies necessary to run the tests.  While it is nice to run the tests for our own peace of mind, it makes the installation more difficult for our users, we can remove 2 steps from the installation instructions if we remove the tests.
We do need to test that the installation works, i.e., that one can create a working program from the installed libraries. But I am not sure running the unit and integration tests helps all that much.

FWIW, I vote for simplifying the installation instructions as much as possible. Likely, the only folks who need to run our tests will be folks who are developing in our repo, and they'll be working from a git clone, not installed binaries.


os.args() and passthru from CLI

i'll try to update this PR with some tests.

updated. see what you think

@edhemphill - this all looks good. Just this one little update to do:
https://github.com/risor-io/risor/pull/102/files#r1321470932
After that I think this is good to go. I'll give it a try just to sanity check.

yeah - i see what you're saying... will try to fix. It's not executing the script.

so in my testing this works:
(test.tm)
#!/usr/bin/env /home/ed/work/risor/cmd/risor/risor

os.args()

As well as some other variations with and without env. The issue is the script arg of the file with the #! is added after the --  so it gets passed to the risor script.
With the above, you can pass args to the risor script like:
 ./test.tm -- 1 2 3

[
  "1",
  "2",
  "3"
]

To get around having to pass args behind a -- you could have a wrapper script for risor. As an example:
#!/bin/bash

exec /home/ed/work/risor/cmd/risor/risor "${1}" -- "${@:2}"

$ ./test.tm 1 2 3

[
  "1",
  "2",
  "3"
]


Add simple end2end testing with playwright

Got following error:
browserType.launch: Executable doesn't exist at /root/.cache/ms-playwright/chromium-1055/chrome-linux/chrome

Full output:
sudo just e2e-test
# Setup
cd docker && docker compose up -d
[+] Running 8/0
 ✔ Container ol-live-mempool-web-1   Running                                                                                0.0s
 ✔ Container ol-live-electrs-1       Running                                                                                0.0s
 ✔ Container ol-live-bitcoin-core-1  Running                                                                                0.0s
 ✔ Container ol-live-ord-1           Running                                                                                0.0s
 ✔ Container ol-live-fixtures-1      Running                                                                                0.0s
 ✔ Container ol-live-mempool-db-1    Running                                                                                0.0s
 ✔ Container ol-live-mempool-api-1   Running                                                                                0.0s
 ✔ Container ol-live-nginx-proxy-1   Running                                                                                0.0s
just watch > /dev/null 2>&1 & echo $! > pidfile # record pid to kill process later
sleep 5 # Wait for just watch finish starting
# test
node test/end2end/runner.ts
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

browserType.launch: Executable doesn't exist at /root/.cache/ms-playwright/chromium-1055/chrome-linux/chrome
╔═════════════════════════════════════════════════════════════════════════╗
║ Looks like Playwright Test or Playwright was just installed or updated. ║
║ Please run the following command to download new browsers:              ║
║                                                                         ║
║     npx playwright install                                              ║
║                                                                         ║
║ <3 Playwright Team                                                      ║
╚═════════════════════════════════════════════════════════════════════════╝
    at ordilabs/repos/live/test/end2end/runner.ts:4:34
    at Object.<anonymous> (ordilabs/repos/live/test/end2end/runner.ts:22:3) {
  name: 'Error'
}

Node.js v18.15.0
error: Recipe `e2e-test` failed on line 173 with exit code 1

Notes:

npx playwright install did not help
I have to run just e2e-test with sudo. In other case I got a permission issue:just watch > /dev/null 2>&1 & echo $! > pidfile # record pid to kill process later
sh: 1: cannot create pidfile: Permission denied

Test on Ubuntu 22.04.2 LTS

Update #test section with following works to me (Note: node vs. node-ts):
    # test
    npx playwright install
    npx ts-node test/end2end/runner.ts
```
works now.

In case use `sudo` can't find `node`, `nvm` and/or `npx` aliases are needed

```bash
sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/node" "/usr/local/bin/node"
sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/nvm" "/usr/local/bin/nvm"
sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/npx" "/usr/local/bin/npx"
```
^ https://github.com/nvm-sh/nvm/issues/43#issuecomment-818700757

Only (last) issue now:
# Teardown
kill $(cat pidfile) && rm pidfile # kill watch process
sh: 1: kill: No such process

error: Recipe `e2e-test` failed on line 173 with exit code 1

@sectore Did you try running just install first? I added playwright in the npm dependencies and that was enough on my setup. I have added a note in the readme on typescript as an additional dependency.

Only (last) issue now:
# Teardown
kill $(cat pidfile) && rm pidfile # kill watch process
sh: 1: kill: No such process

error: Recipe `e2e-test` failed on line 173 with exit code 1

Looks like a second order effect when the watch process wasn't actually started. Did the test pass on this run?

cat /etc/hosts

I have the same, for me it wasn't needed. Can you suggest changes that make it work in your environment?
<IP_ADDRESS> mempool-ol.local
::1 mempool-ol.local
<IP_ADDRESS> ord-ol.local
::1 ord-ol.local
<IP_ADDRESS> live-ol.local
::1 live-ol.local

So is this in general the setup that we want conceptually and I can remove the draft mode? @FelixWeis

Aproach ACK. few ideas

[ ] docker compose should a testing namespace to not tear down less ephemeral dev fixtures
[ ] instance just watch on a different port than :3000 using LEPTOS_SITE_ADDR  env
[ ] these setting probably should all just be in a testing.env that just loads

@fjahr Trying to answer your questions here:

Did you try running just install first?

Yes

Can you suggest changes that make it work in your environment?

I've just added http://live-ol.local:3000 to include port 3000 in line 8 of test/end2end/runner.ts

Looks like a second order effect when the watch process wasn't actually started. Did the test pass on this run?

Yes, tests did pass.

@sectore addressed your comments as far as I could without breaking my own environment, please give it another try.
But I guess @FelixWeis is right, this should be dockerized. I haven't worked with docker for a while so this would take me some time. How about you @sectore ? Are you familiar with Docker and want to take it over from here?

How about you @sectore ? Are you familiar with Docker and want to take it over from here?

Sorry, I'm not that deep into Docker as well.

Thanks until here! Assigning this to myself now to explore the dockerization.


The pre-filled (org./project/repo) name is still shown after collapsing the 'Add new' pop-up

The input field should be empty after re-clicking on the "Add new" button while creating a new organization, adding a new project or creating a new repository, if any name had been entered before.
Stets to reproduce:

Open the desktop client.
Go to the 'Organization' screen.
Press the 'Add new' button.
Enter some text into 'Organization name' field.
Minimize the 'Add organization' pop-up.
Press the 'Add new' button once again.
Expected result: the 'Organization name' field is empty.
Actual result: the 'Organization name' field is pre-filled with just entering text.

Checked


added filter for loguru

resolves #180 using a filter for loguru

regarding this:

@abrichr should be good now


logger crate catches Clion stop signal

Passing this issue, here.
I'm using Clion developing in a remote environment.
When I'm stoping the process from the clion stop the logs stops but the process not.
fn init_logger() -> Result<(), String> {
    env_logger::Builder::new()
        .format(|buf, record| {
            writeln!(
                buf,
                "{}:{} {} [{}]: {}",
                record.file().unwrap_or("unknown"),
                record.line().unwrap_or(0),
                chrono::Local::now().format("%Y-%m-%d %H:%M:%S.%3f"),
                record.level(),
                record.args()
            )
        })
        .filter(None, LevelFilter::Debug)
        .init();
    Ok(())
}

fn main() -> Result<(), String>  {
    let _ = init_logger();
    info!("Hello, world!");
    for i in 0..10 {
        info!("{}", i);
        // spdlog::info!("{}", i);
        // println!("{}", i);
        thread::sleep(Duration::from_secs(1));
    }
    return Ok(());
}

In this example when I'm stopping the process in the middle the logs will stop but the loop will run to the end, the full 10 seconds and the process will exit successfully.
If I change from log::info! to spdlog::info! or from log::info! to println! or adding .is_test(true) to log init, it works as expected, exits imidietly with fail code.
If I run in regular Clion run on my machine compiler log works fine the same as the other loggers but I would expect it to work the same in my remote environment.
Is there a reason for this behavior?
What is the .is_test(true) flag?

By "exit immediately", you are referring to a panic from a broken pipe?  That is not expected behavior and we try to avoid it (e.g. #221).
println panics on a broken pipe error.  It is generally best to use writeln and handle the broken pipe error as works best in your application.  For example, a tool like ripgrep might decide that it should exit early with a success exit code on a broken pipe.
.is_test(true) is a hack to take advantage of a hack in std / test.  The default test harness, test, uses an unstable hook into std to capture the output from print/println so that it can hide it by default and then only print it along with the test failure.  .is_test(true) forces env_logger to go through println so logged messages from a test can be captured with the test.
As this is working as expected, I'm going to go ahead and close this.


Use full standard cmake export from llvm/mlir

LLVM/MLIR exports the information needed for external builds in a consistent and standard way.  It is generally preferred to use this mechanism, rather than replicating it.  It seems that onnx-mlir currently uses some of the information exported by LLVM, but not MLIR.  It also seems that there are direct references into the LLVM source tree, which shouldn't be necessary.  I'd be happy to work to improve this, but it would probably go faster if someone who is familiar with the current system would also contribute.

Let me check who would be the right person on our end.

I wrote the first version of cmake to link with mlir/llvm. Then Tian made lots of modifications. Back then, mlir did not have a clear export structure.  I will be glad to work with @stephenneuendorffer to update our cmake.

Great!  Thanks!

@chentong319 Can you review this?  https://github.com/onnx/onnx-mlir/pull/558  I don't even have permission to add you as a reviewer, it seems.

Please see #613

Updated patch is: #631

I think #718 addresses any remaining issues by incorporating HandleLLVMOptions. Can you have a look and see if anything else is missing?


Capture specific view on window

I want to capture a specific view only .I did not found any documentation on it . Is this function available ?
Thank you

Do you need a function to get a screenshot just from view? This can be done like it.
public static Bitmap shot(View view) {
view.setDrawingCacheEnabled(true);
Bitmap bitmap = view.getDrawingCache();
view.setDrawingCacheEnabled(false);
return bitmap;
}
Or do you need an option to get view region with all dialogs above?

thanks i got it i was wondering if it was possible using this library


docs: POC with StackBlitz or CodeSandbox

The idea is to show the code and example side by side
e.g.

Soon we will have Storybook, do we still need this component?
@shairez @nnelgxorz @gilf

☝  @shairez

Yep, nice call.I close It.


DockerException: Error while fetching server API version: Not supported URL scheme http+docker

On main after pip install . and running composer-dev create, got the error:
DockerException: Error while fetching server API version: Not supported URL scheme http+docker

Looks like this is related to https://github.com/docker/docker-py/issues/3256
Upgrading to docker==7.1.0 inside setup.py and reinstalling fixed the issue for me.
Context:
pip 24.1.1
python 3.10

we can add "requests==2.31.0", in setup.py

we can add "requests==2.31.0", in setup.py

This solved my issue. Thanks.

I followed this but still getting the same error. Any ideas?

I made both adjustments to the setup.py, changing from docker 6.* to 7.* and added the "requests==2.31.0" to the dependencies and this resolve the error.

Fix merged into the development branch, a new version will be released soon with this and more fixes/improvements. Use the development branch meanwhile if needed.


fix(menu): prevent user from accidentally opening a sub-menu while animating

Makes the menu panel non-interactive while it is animating, preventing the user from accidentally triggering a sub-menu.
For reference, here's what it used to look like if the user moved their cursor while animating:

That's a good UX fix! Thanks


[Theme] spacing function

I'd like to propose the following additive change to theme.spacing:
import warning from 'warning';

const unit = 8;

const spacing = (...args) => {
  if (process.env.NODE_ENV !== 'production') {
    warning(
      args.length <= 4,
      `Too many arguments, exepected 1..4, got ${args.length}`,
    );

    args.forEach((arg, index) => {
      warning(
        typeof arg === 'number',
        `Expected argument ${index + 1} to be a number, got ${arg}`,
      );
    });
  }

  return args
    .map((multiplier = 0) => multiplier && `${unit * multiplier}px`)
    .join(' ');
};

spacing.unit = unit;

export default spacing;

This is a backward compatible change that allows you to then:
Single value:
Example
padding: theme.spacing(1)

Result
padding: 8px;

Multiple values:
Example
padding: theme.spacing(1, 2)

Result
padding: 8px 16px;

Example
padding: theme.spacing(.5, 1, 2, 3)

Result
padding: 4px 8px 16px 24px;

I'd like to open a pull request for this if we're onboard.

 Otherwise you could just create your own transformer that handles auto separately. Since there's only a single keyword it might be a better idea to handle this internally? @oliviertassinari

We could support it with a minor change. But should we 🤔?

We could support it with a minor change. But should we ?

I guess this can become pretty "ugly" if it's used very often e.g.
${theme.spacing(2, 3)} auto ${theme.spacing(2)} instead of "just" theme.spacing(2, 3, 'auto', 2). But then again every custom theme transformer would have to catch that case to not blindly use multiplication on strings. I think it's ok to not support it and wait for upvotes. This wasn't supported before anyway, right?

@valoricDe If you want to push for the addition of this feature, I would encourage you to open an issue dedicated to it. We will add the waiting for upvotes issue label.

#16163


Allow requests to be made correctly

1⃣ Is this something that is wanted/needed? Did you create a feature-request issue first?
Yes.
2⃣ Does it contain multiple, unrelated changes? Please separate the PRs out.
No. However this is linked to #86
3⃣ Does it include tests if possible? (Not a deal-breaker, just a nice-to-have)
No
4⃣ Please include a thorough description of the feature/fix and reasons why it's useful.
Currently requests made to /livewire/ will 404 when the livewire app is not being served from the root folder of a webserver or being run with php artisan serve
This fix allows the request to be made to the correct root path of the app irrespective of the hosting path

This has been addressed in the latest release: v0.1.1

Thanks for the contribution though!


Try to replace Path.home() with use of None internally

Makes a start on #56

No longer working on this project, closing


Add wait-for-ready semantics

#6770

Related gRFC #16919

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,966,345      Total (=)      1,966,345

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,909,772      Total (>)     10,909,771

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,966,345      Total (=)      1,966,345

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,909,775      Total (>)     10,909,770

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,966,345      Total (=)      1,966,345

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,909,773      Total (>)     10,909,771

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,238      Total (=)      1,997,238

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,651      Total (>)     11,021,648

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,238      Total (=)      1,997,238

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,756      Total (<)     11,021,762

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,238      Total (=)      1,997,238

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,763      Total (>)     11,021,757

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,238      Total (=)      1,997,238

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,764      Total (>)     11,021,763

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,762      Total (>)     11,021,759

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,759      Total (=)     11,021,759

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,762      Total (<)     11,021,763

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,761      Total (<)     11,021,762

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,764      Total (>)     11,021,759

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 1,997,294      Total (=)      1,997,294

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,021,756      Total (<)     11,021,766

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,196      Total (<)     11,116,200

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,015,649      Total (=)      2,015,649

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,116,197      Total (>)     11,116,196

 No significant differences in binary sizes

@apolcyn Can you take a look of updated code? I have updated them according to your feedbacks (thanks again).

****************************************************************

libgrpc.so

     VM SIZE              FILE SIZE
 ++++++++++++++ GROWIN ++++++++++++++

 -+-+-+-+-+-+-+ MIXED  +-+-+-+-+-+-+-
  -0.0%     -64 [None]    +552  +0.0%

  -0.0%     -64 TOTAL     +552  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,944      Total (<)     11,180,948

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,938      Total (<)     11,180,946

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,944      Total (>)     11,180,939

 No significant differences in binary sizes

Corrupt JSON data (indicates timeout or crash):
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.new: 10
    bm_call_create.BM_IsolatedFilter_ClientChannelFilter_NoOp_.counters.old: 10

[microbenchmarks] Performance differences noted:
Benchmark                                                                 locks_per_iteration
------------------------------------------------------------------------  ---------------------
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/0           -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/1           -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/2097152     -6%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/262144      -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/32768       -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/4096        -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/512         -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/64          -7%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/8           -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/0        -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/1        -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/2097152  -6%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/262144   -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/32768    -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/4096     -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/512      -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/64       -7%
BM_StreamingPingPongMsgs<MinInProcess, NoOpMutator, NoOpMutator>/8        -7%

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,020,616      Total (=)      2,020,616

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,939      Total (>)     11,180,938

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,386      Total (=)      2,019,386

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,036      Total (>)     11,180,033

 No significant differences in binary sizes

@gnossen @apolcyn Thanks for pointing out the subscribe mechanism, I removed the time.sleep(2) and use a wait group to block the thread.

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,386      Total (=)      2,019,386

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,032      Total (<)     11,180,036

 No significant differences in binary sizes

Objective-C binary sizes
*****************STATIC******************
  New size                      Old size
 2,019,390      Total (=)      2,019,390

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
11,180,031      Total (<)     11,180,035

 No significant differences in binary sizes


Logs on Testnet 22.0.2 contain non-ASCII characters

Logs on Testnet 22.0.2 contain non-ASCII characters:
{"caller":"basic_host.go:414","level":"debug","module":"libp2p:basichost","msg":"protocol
negotiation took 27.948<C2><B5>s","ts":"2022-03-23T09:38:44.015536269Z"}

It's UTF-8 for U+00B5 (lower case mu), because Go's default time.Duration string s11n routine  does that for micro seconds.

Closing, this is working as intended (and yes, I would rather the Go developers used u instead).


New SNX and sUSD Addresses

PR to update new token proxy addresses for https://www.synthetix.io/

SNX
sUSD

These new contracts are already on MAINNET.
Please see public announcement https://blog.synthetix.io/proxy-contract-cutover-on-may-10/
Added new entries for popular synths https://dashboard.synthetix.io/

sETH
sBTC

DApps

https://synthetix.exchange/
https://l2.synthetix.exchange/trade/sBTC-sUSD
https://mintr.synthetix.io/

Lite Paper
https://www.synthetix.io/litepaper

Hi @rekmarks. We've completed this Token proxy address migration. I would like to support our holders who use MetaMask to get the new token updates.

Hey @hav-noms, we're about to do another round of merges in this repo, and Synthetix definitely makes the cut. However, we're considering what to do with holders of tokens at the old addresses. Have you guys gone through a migration process? Are the tokens at the old addresses still valuable/useable?

@rekmarks its already taken care of. It's not a token migration. The token balances are in an external state so we just assign the new proxy for the token address. All of the old token balances at the old address are already dead balances that have no value and are not usable.
https://docs.synthetix.io/integrations/guide/#proxy-deprecation


Change video for demo

Description
Change video for demo

Coverage: 93.766%. Remained the same when pulling c585011ed143137fcd9391b0c6e3f606da691d78 on edit-demo-link into 3d510d50deb17fa892e5594fab232a8e90e2a735 on main.


Update variables.tf

Description

Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

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

GitHub release
v4.13.5

Your semantic-release bot :package::rocket:


Add python API for managing vineyard operator and relevant k8s components

Describe your problem
Upstream users(GraphScope) mainly deploy vineyard through python API. To better integrate vineyard into upstream on kubernetes, we need to support deploying the vineyard operator and relevant components(CRDs, such as Vineyardd、Backup、Operation、Sidecar、Recover、Sidecar, etc). Mainly includes the following work:

Support managing vineyard operator by python API. (Deploy and Delete)
Support managing vineyard relevant k8s components. (Create、Update and Delete)

Thanks for the design of @sighingnow , closed via https://github.com/v6d-io/v6d/pull/1216 , https://github.com/v6d-io/v6d/pull/1231


no-memory error issue with Kong DB-less

Summary
On high traffic on the Admin API or a lot of change in configuration values of entities in Kong in DB-less mode, worker-events runs out of shm memory.
Error logs:
```2019/06/26 04:04:24 [notice] 40#0: *68534 [lua] cache.lua:317: purge(): [DB cache] purging (local) cache, client: <IP_ADDRESS>, server: kong_admin, request: "POST /config?check_hash=1 HTTP/1.1", host: "localhost:8444"
<IP_ADDRESS> - - [26/Jun/2019:04:04:24 +0000] "POST /config?check_hash=1 HTTP/1.1" 201 7242 "-" "Go-http-client/1.1"
2019/06/26 04:04:25 [error] 33#0: *68787 [lua] events.lua:254: post(): worker-events: failed posting event "targets" by "balancer"; no memory, context: ngx.timer
2019/06/26 04:04:25 [error] 33#0: *68787 [lua] handler.lua:265: failed broadcasting target create to workers: failed posting event "targets" by "balancer"; no memory, context: ngx.timer
2019/06/26 04:04:25 [error] 39#0: *68788 [lua] events.lua:254: post(): worker-events: failed posting event "targets" by "balancer"; no memory, context: ngx.timer
2019/06/26 04:04:25 [error] 39#0: *68788 [lua] handler.lua:265: failed broadcasting target create to workers: failed posting event "targets" by "balancer"; no memory, context: ngx.timer
2019/06/26 04:04:25 [error] 37#0: *68758 [lua] balancer.lua:581: on_target_event(): target create: balancer not found for nginx-ingress-controller-live.events.svc, context: ngx.timer
2019/06/26 04:04:25 [error] 33#0: *68787 [lua] balancer.lua:581: on_target_event(): target create: balancer not found for nginx-ingress-controller-live.events.svc, context: ngx.timer```

The error logs suggest that the kong_worker_events shm is full.
Further looking at the shm metrics from Kong's /status endpoint gives the following information for the shm used for this library:
   "allocated_slabs": "5.00 MiB",
        "capacity": "5.00 MiB"

In conversation with @thibaultcha and @Tieske, it was noted that this is due to fragmentation issue inside the shm due to insertion of tables of varied sizes into the shm. The shm actually might have space for insertion but requires multiple evictions to find a single slab to allocate the table being inserted. This possibly requires using shm_set_tries in lua-resty-mlcache.
Reproduction steps:

Spin up Kong (>=1.1) in dbless mode
Use /config endpoint to change Kong's configuration. Make sure that plugins, upstreams and targets are also changed in each reload.

This should result in shm getting fragmented over time and expose this problem

for reference, the mlcache implementation: https://github.com/thibaultcha/lua-resty-mlcache/pull/41

hi,I exposed the same problem.When is the problem expected to be fixed? @Tieske


Are there plans to support other data formats

Are there plans to support other data formats

Such as  kryo, protobuf, avro, msgpack

Duplicate of #555
Almost there. Thanks for the advice.