Prevent column resize when changing pages

Depending on the displayed content, page changes may cause column width resizes which may be a bit disorienting.
A good example for a nicer behavior is DataTables - column sizes are retained across page changes, regardless of content.
This doesn't seem like something that knockout-datatable should handle per-se (being a view-model rather than a view), but I believe the proper html/JS code for this should be in the demo.html page (not quite sure how that code should look ATM).

Closing this due to inactivity.


Tabs interface enhancement

for more comfortable image-browsing using grabber with many tabs I suggest three things.

Add a tablist button on the right corner of the tabs bar to fast and easyer viewing and changing tabs. After it's pressed, opens pop-up menu with list of currently opened tabs, so you can change tabs from it. This feature has many browsers like Opera, Firefox etc.
Add a counter of the opened tabs in the right corner of tabs bar, or tabs counter can be on tablist button.
add a popup menu to tabs bar with "open new tab" and "restore closed tab" items

Those three things will greatly improove using grabber with many tabs.
example of 1 and 2 suggestions:

maybe you will add it to v5.5.3 milestone? it's very important functional for me, so needed >_<


appmarket-worker for simple OVA import without a market

Author Name: Carlo Daffara (Carlo Daffara)
Original Redmine Issue: 3195, https://dev.opennebula.org/issues/3195
Original Date: 2014-09-19

The Appmarket-worker functionality is in itself extremely interesting even without a market- that is for import and conversion directly in templates and images. Since many users are really not that interested in running their own market, it may be worthwhile to consider if the worker functionality can be adapted to import only- directly as local one templates and images.

Original Redmine Comment
Author Name: Florian Heigl (Florian Heigl)
Original Date: 2017-11-07T23:55:43Z

That would have been a helpful feat. And it seems 3 years of backlog has made sure it's had time to rest.
Can we think about it? :-)


UI for adding a grouping

One major piece of functionality for this application is creating groupings, which can then be associated with rights shells. his form should include all fields in the Grouping model.

Quick wireframe:


There seems to be a bug when a restart occurs

I have observed if you restart the raspberry pi the service works, however the TACHO reading shows 0 throughout and although the PWM pin shows RPM reading

the fan doesn't seem to come on at all.
This is despite waiting for several minutes to an hour
If you manually stop and start the service it works, But I do not think this is designed in that manner.
I tried this using v1.4
Screenshot with TACHO

FYI: The taco seems to give just 1 reading at the start up and the fan shuts off and doesn't come on again until you manually restart the service
I have tried setting this up from scratch 3-4 times and see the same behavior
So in order to mitigate it, I have added this crontab
@reboot sleep 60 && sudo systemctl restart fan-control

How do you know the fan is not running? Did you look at the fan when it was showing "PWM-PIN .... RPM: 1500" in the logs? Were you even tailing the log [OR] just printed the status?
What fan you are using?
What OS you are using?
What is the raspberrypi model?
Paste the ouput of these cmds here:

ls -l /opt/gpio/fan/
cat /opt/gpio/fan/params.conf
cat /etc/systemd/system/fan-control.service

Here is the log I recorded right now after a fresh reboot of rp4 with Tacho enabled and a brief stress test to increase temperature:

Yes I looked at the fan when it shows PWM-PIN with RPM 1500 and the fan did not turn on and the temperature exceeded 50 deg C, I checked the log and the status as well
I am using the Noctua 5V PWM
OS:

Raspberry Pi Model is: 4B
Here is the information you requested in the form of a screenshot

and here it is in the form of text
eltonajmenezes@eltonsraspberrypi:~ $ ls -l /opt/gpio/fan/
total 20
-rwxr-xr-x 1 root root 15600 Nov 10 17:08 fan-control
-rw-r--r-- 1 root root   145 Nov 10 17:11 params.conf

eltonajmenezes@eltonsraspberrypi:~ $ cat /opt/gpio/fan/params.conf
PWM_PIN=18
TACHO_PIN=23
RPM_MAX=5000
RPM_MIN=1500
RPM_OFF=0
TEMP_MAX=70
TEMP_LOW=40
WAIT=5000
THERMAL_FILE=/sys/class/thermal/thermal_zone0/temp

eltonajmenezes@eltonsraspberrypi:~ $ cat /etc/systemd/system/fan-control.service
[Unit]
Description=Fan Speed Control Service
Before=sysinit.target
After=local-fs.target
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=sysinit.target

I will give you marks for making the effort. This comment explains things in a much better way.

FYI My /etc/systemd/journald.conf I have set to retain only these values
Could that be the cause? (just a speculation)

It has nothing to do with journald.conf. You can keep any settings in it according to your preference. It is just logging.
So based on what you have mentioned so far. When you restart the service through cronjob or manually after system reboot fan-control works as expected. It has something to do with service unit (fan-control.service). Fan-control service is supposed to be started after mounting the filesystem. There is something different about your mount unit.
Are you using sd-card [OR] SSD [OR] HDD?
Make sure you are running the v1.4 binary in /opt/gpio/fan/ folder. You can use newly built binary with Tacho enabled later if everything works fine. Inspect the fan visually.

Try this, edit your fan-control.service:
sudo nano /etc/systemd/system/fan-control.service
Remove lines Before=sysinit.target and After=local-fs.target. fan-control.service will look like below:
[Unit]
Description=Fan Speed Control Service
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=sysinit.target

Save fan-control.service. Execute below cmds and then reboot:
sudo systemctl disable fan-control
sudo systemctl enable fan-control

If above change does not work. Try this, edit your fan-control.service:
sudo nano /etc/systemd/system/fan-control.service
Use below service unit in it:
[Unit]
Description=Fan Speed Control Service
After=network.target
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=multi-user.target

Save fan-control.service. Execute below cmds and then reboot:
sudo systemctl disable fan-control
sudo systemctl enable fan-control

For me all 3 work fine including v1.4 fan-control.service. I use SSD.

I have also found this article which is less in depth than yours and that's why I would like to use your code. Anyway this is the article: https://www.the-diy-life.com/connecting-a-pwm-fan-to-a-raspberry-pi/
In this article the author mentions to use GPIO 14 but I am using the PWM_PIN 18 to check and see if it is defective or something is wrong on my side.
So I deployed it and the to my sigh of relief nothing is wrong with my firmware I guess. The only difference between your code and the code from the article that I see is that he is directly running a script and you have a service.
So he invokes the code using a crontab. The fan started and stopped after rebooting and then started and stopped when the temperature reached the set value. This is the code: https://github.com/mklements/PWMFanControl/blob/main/FanProportional.py
Also he doesn't take care of the minimum RPM which you do and that's why I would prefer that I can get this code working the way you intended it to work.

Biggest difference between python scripts and this C source code is the usage of system resources. Python script based fan controllers use a lot more system resources (memory and cpu usage). You can test this out later with htop or top cmd by running them individually and check the memory and cpu usage they are consuming.
RP4 supports hardware PWM on GPIO pins 12, 13, 18 & 19. If you use any other GPIO pin apart from these ones they will use software PWM that is less efficient. I mentioned that in the source code and documentation.

Stick to the basics if you want to resolve this issue. Do not switch binaries between the pre-built v1.4 binary and the one you built with Tacho. When you are posting screenshots with Tacho output it means you switched the binary.
If after reboot fan-control service is starting fine with cronjob or manually. There is no issue with your hardware pin.
I did some testing with sd-card and all 3 fan-control.service files work fine. I have very strong feeling this is self inflicted issue.  Make sure you DO NOT have any other fan controlling script/binary running on your system, that includes any python script or any other binary of fan-control. There should be only 1 binary on your system and that is the fan-control pre-built v1.4 (without Tacho enabled).
Do this exactly as mentioned below:

Disable the cronjob to start fan-control after reboot
Use the pre-built binary from v1.4
Use the default params.conf avaialble in v1.4
Use below /etc/systemd/system/fan-control.service. (This is the one I was planning to update in the repo as well in the future after some testing):[Unit]
Description=Fan Speed Control Service
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=sysinit.target

Save fan-control.service. Execute below cmds:sudo systemctl disable fan-control
sudo systemctl enable fan-control

Do not start fan-control.
Reboot the system

Post these outputs here:

Visually inspect the fan. Fan should start at full speed when the system is booted and either it will turn off or switch to lower speed depending on your system temperature when fan-control service starts. Post the result of your visual inspection in the comment. (No screenshot nothing else is needed)
When system is booted run this cmd:
sudo journalctl -u fan-control -n 200 -f
Post the result of this command (screenshot).
Visually inspect if the fan is not running, Is the log printing a line after every 5 seconds? (mention it here)
Run this cmd:
raspi-gpio get 18
Post the output of this cmd here. (screenshot)
Run this cmd:
htop -p "$(pgrep -d, fan-control)"
Post the output of this cmd here. (screenshot)

Do NOT start fan-control service manually or with cronjob during this whole test.

The fan after a cold boot started and then stopped, then started for 1 second and stopped completely. Then I removed all traces of the installed tool. and I at least saw that it started to come on and go off by itself! But; it only turned itself on when the temp reached closer to 50deg and not when it was above 40deg which is not expected.
Result of the command: sudo journalctl -u fan-control -n 200 -f

Result of the command: raspi-gpio get 18

Result of the command: htop -p "$(pgrep -d, fan-control)"

And I did not start the fan-control service manually or with cronjob.
FYI: As I mentioned earlier, if you restart the service the fan runs perfectly with the given temperature settings above 40deg ...

Then I removed all traces of the installed tool and I at least saw that it started to come on and go off by itself!

I specifically mentioned remove everything before starting this test.

then started for 1 second and stopped completely.

My guess was write you have something else that is trying to control the fan or gpio pin 18. It is your self inflicted issue. It seems like you tried too many things to control fan and most probably you do not even remember what else you did on your system for controlling fan. You might even have it enabled from raspi-config as well.

Result of the command: sudo journalctl -u fan-control -n 200 -f

You did not mention that log was moving or not when fan was not running?

FYI: Also now if you edit the temperature on the HIGH side to be 70deg and not 50deg then you do not see the fan turning on at all. It's like it only senses the max temperature boundary and even if it does sense the lower temp bound it is not turning on unless you restart the service manually or using a cron

It works perfectly fine for any temperature range. I have tested it for 30-60 | 30-70 | 40-60 | 40-70 | 40-80 | 40-90 degree ranges. The minimum RPM is 1500 so it should fire up as soon as you hit TEMP_LOW.

I am using it for almost 2 yrs on multiple rp4 and it works perfectly fine. This repo has biweekly hit of around 50+ and no one have complained about it. Documentation is written in the easiest possible way that newbies can understand it.
Only you can figure out what else you did with your system

sudo journalctl -u fan-control -n 200 -f
So when I ran this the fan moved only when it reached around 50deg celsius but not when it was above 40deg (It stopped then)

So I just wiped my entire SD-Card and reinstalled a fresh copy of Raspberry Pi.
I tested it and unsurprisingly the same behavior. The fan stopped and did not turn on after crossing 41deg celsius.
I followed step by step and even tested with TACHO but nothing

So when I ran this the fan moved only when it reached around 50deg celsius but not when it was above 40deg (It stopped then)

I did not ask about fan running or not. The log was still printing statements or not after every 5 seconds when the fan was not running after reboot. This is the third time I asked this. If the log is still printing statements with cmd "sudo journalctl -u fan-control -n 200 -f" when the fan is not running after reboot, it means something on your system has pulled down the gpio pin or changed its mode.
Further proof is when you restart fan-control manually or with cronjob everything works fine. BTW screenshots in your first closed issue indicate everything was working fine without any cronjob.
I am not sure why you are so obsessed with enabling Tacho while trying to resolve the issue. It is not controlling your fan speed or anything. It only tells you the approx fan rpm that you can visually inspect as well.
One last thing you can check is that you are using latest WiringPi lib version 2.70.
Sorry can't help you further on this. You can use the one that you can make.

@ar51an  Yes the log was printing every 5 seconds even when the fan was not running.
But the fan didn't turn on above 40deg and only when it hit 50deg.
I cannot understand why!
I have now tried this after setting up the raspberry pi from scratch and I see without TACHO the same behavior and with TACHO.
That's my observation.

Make sure you have latest WiringPi lib. Installation is just 2 step process mentioned in my documentation.
https://github.com/WiringPi/WiringPi/archive/refs/heads/master.zip
You can check the WIringPi version with this cmd on rp4:
gpio -v
Here are few things you can try.
Test 1:

Connect only ground pin, 5v pin (make sure you connect it to RP4 5 volt AND NOT 3.3 volt) and PWM pin (To GPIO 18). DO NOt connect tacho pin.
Install the pre-built binary from v1.4.
Do not copy params.conf in /opt/gpio/fan/ dir. This dir should have only pre-built v1.4 binary.
Reboot the system.
Do not do anything else during this whole test. Observe the behavior visually.

If it is same as you previously replied? (fan runs at full speed, then runs for 1 second and then stops)
Test 2:

Disable fan-control service. Reboot the system. Observe the behavior visually.

Does the fan runs on full speed and keeps on running?

I tried every scenario that you have mentioned and other possibilities. I am not able to replicate your issue.

So the version is
eltonajmenezes@eltonsraspberrypi:~ $ gpio -v
gpio version: 2.70
Copyright (c) 2012-2018 Gordon Henderson
This is free software with ABSOLUTELY NO WARRANTY.
For details type: gpio -warranty

Raspberry Pi Details:
  Type: Pi 4B, Revision: 05, Memory: 8192MB, Maker: Sony
  * Device tree is enabled.
  *--> Raspberry Pi 4 Model B Rev 1.5
  * This Raspberry Pi supports user-level GPIO access.

So now to your 2 asks.

Connected only GRND PIN, 5V, PWM to GPIO 18, DISCONNECTED TACHO
Used v1.4 of binary
did not copy params only used prebuilt and deleted the downloaded file so as to not have any potential conflicts after I copied to the directories.
Rebooted the system.
Observing the fan, yes it runs at full speed then for a second and then only when it approaches 50deg and not above 40deg

Test 2
Disabled the fan-control service and the fan runs at full speed and keeps on running.

Keep it simple and use the pre-built v-1.4 binary without connecting Tacho wire and without params.conf. Till everything works fine using one of the below services, then you can move on from their and use Tacho and params.conf.
Option 1:
Use below service in "/etc/systemd/system/fan-control.service" it will start fan-control very late in the systemd chain.
[Unit]
Description=Fan Speed Control Service
After=multi-user.target
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=multi-user.target

Option 2:
If first option does not give you desired results. You can further delay start of systemd service by using this service in "/etc/systemd/system/fan-control.service" . It has "ExecStartPre" which can further delay the start of only fan-control service using sleep parameter.
Adjust sleep parameter accordingly, gradually increase sleep value with increments of 1 to find the optimal sleep value at which fan-control service will start without any issue.
Downside of ExecStartPre is whenever you will restart service manually it will add that delay in the service start.
[Unit]
Description=Fan Speed Control Service
After=multi-user.target
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStartPre=/bin/sleep 1
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure

[Install]
WantedBy=multi-user.target

During testing both options, keep in mind that fan will run at full speed much longer at the startup so system temperature will be lower when the fan-control service will start. Do not rush to the conclusion that it did not work, give it some time to make sure it worked (may be few minutes).

There are other options as well like using custom target [OR] use systemd timer, but they will be an overkill for this simple delay and have their own downsides.

Do you have any extra temp monitor/sensor packages or software installed? (that are not part of default OS)
Do you use lite version of OS or full version?

The service is starting prematurely before it can get the band of temperatures and cannot make a clear determination of when to turn on the fan.

The fan-control service is reading system temperatures at every 5 second interval. Unless you have some extra package or software for sensor monitoring that is interfering with the default retrieval of system temperatures. Answers to above questions may give some clue.

Do you have any extra temp monitor/sensor packages or software installed? (that are not part of default OS)
Nothing else

Do you use lite version of OS or full version?
Full Bullseye 64Bit OS of Raspberry Pi official

The referenced Option 1 DID THE TRICK!!

[Unit]
Description=Fan Speed Control Service
After=multi-user.target
DefaultDependencies=no

[Service]
Type=simple
User=root
ExecStart=/opt/gpio/fan/fan-control
ExecStop=/bin/kill -s SIGINT $MAINPID
Restart=on-failure
[Install]
WantedBy=multi-user.target
THANK you so much for this. I rebooted and tested with and without TACHO and it worked!


Best place to set carbon-aggregator  in a graphite cluster ( rules vs consistent hashing)?

Hi guys.
I'm planning a big graphite cluster and I've tested with relay (now configured with rules) in front of carbon caches, but I need now to add a carbon-aggregator  daemon and I have doubts on the best place to put it.
we are considering a load  balancer in front of carbon daemons doing a RR balancing for all carbon clients.
So If CA=carbon-aggregator/CR=carbon-relay/CC=carbon-cache/LB=load balancer
Config 1

      +->(node1)  [CR1]->[CA1]->[CC1]
     |
[LB]-+
     |
      + ->(node2) [CR2]->[CA2]->[CC2]

This can be good if
RELAY_METHOD = rules ( ^env1 =>node 1 ^env2 => node2)
REPLICATION_FACTOR = 1
so I can assure that all metric beginning with the same metric name ( same environment)  can be aggregated independent of what is the receiver node of the metric.
Doubts
what happens if I configure   RELAY_METHOD = consistent-hashing ?
Which is the best approach for this layout ?

What C-H basically means is that the sender maps out each metric to a specific target in an effort to distribute all metrics evenly throughout the "hash ring". This works well with one large caveat; any time the hash ring changes (e.g. adding a new node), that map gets blown away and all of the metric destinations change. You're responsible for moving the existing data around to their new homes.

I'm not certain if this was the case as of the time of the original writing, and if so it was not a proper implementation of a consistent hashring, but as of today the bolded statement is incorrect.
If the number of nodes in a cluster changes only a subset of metrics move from an existing node to the newly added node. No metrics will shuffle between the pre-existing nodes.
Eg: Assuming an ideally-distributed hashring in a cluster of 2 nodes [A and B], adding a third node [C] would cause 1/3 of all metrics destinations on nodes A and B to move to node C, however no metric destinations would move between nodes A and B.
Posted for the sake of clarity.


Set up tests with generated controller tests

Hello!
I hope you can help me out, because I cannot figure out how to set up my controller tests after integrating Pow and banging my head against the wall for two evenings already ouch.
When I "mix phx.gen.html ...", tests are generated like this one, where I can put the setup for Pow

describe "create organisation" do
    setup %{conn: conn} do
      user = %User{email<EMAIL_ADDRESS>      conn = Pow.Plug.assign_current_user(conn, user, otp_app: :paper)
      {:ok, conn: conn}
    end

    test "redirects to show when data is valid", %{conn: conn} do
      conn = post(conn, Routes.organisation_path(conn, :create), organisation: @create_attrs)

      assert %{id: id} = redirected_params(conn)
      assert redirected_to(conn) == Routes.organisation_path(conn, :show, id)

      conn = get(conn, Routes.organisation_path(conn, :show, id))
      assert html_response(conn, 200) =~ "Show Organisation"
    end

    ...
  end

When I run the tests, I get this error:
test create organisation redirects to show when data is valid (PaperWeb.OrganisationControllerTest)
     test/paper_web/controllers/organisation_controller_test.exs:52
     ** (RuntimeError) expected response with status 200, got: 302, with body:
     "You are being redirected."
     code: assert html_response(conn, 200) =~ "Show Organisation"
     stacktrace:
       (phoenix) lib/phoenix/test/conn_test.ex:369: Phoenix.ConnTest.response/2
       (phoenix) lib/phoenix/test/conn_test.ex:383: Phoenix.ConnTest.html_response/2
       test/paper_web/controllers/organisation_controller_test.exs:63: (test)

I did a lot of IO.inspecting the conn in various location, did "refute conn.halted" and even compared the count of items in the table before and after create, but everything looks like the implementation is working. So I am sure that with the error in the test I am receiving a false negative.
If I remove the ":protected" from the routes, the error is gone. So I am assuming that some redirection happens within Pow.
Can you help me to understand what is going on and how to set up the tests to follow the redirection?
Thanks a lot!
Yours,
Volker

It's because the pow config gets overridden with the resulting conn. Instead you should do something like this:
    test "redirects to show when data is valid", %{conn: authed_conn} do
      conn = post(conn, Routes.organisation_path(authed_conn, :create), organisation: @create_attrs)

      assert %{id: id} = redirected_params(conn)
      assert redirected_to(conn) == Routes.organisation_path(conn, :show, id)

      conn = get(conn, Routes.organisation_path(authed_conn, :show, id))
      assert html_response(conn, 200) =~ "Show Organisation"
    end

Thank you, Dan!
Two conns needed to be changed to "authed_conns", too. Then the tests were passing as expected.
👍
    test "redirects to show when data is valid", %{conn: authed_conn} do
      conn =
        post(**authed_conn**, Routes.organisation_path(authed_conn, :create),
          organisation: @create_attrs
        )

      assert %{id: id} = redirected_params(conn)
      assert redirected_to(conn) == Routes.organisation_path(conn, :show, id)

      conn = get(**authed_conn**, Routes.organisation_path(authed_conn, :show, id))
      assert html_response(conn, 200) =~ "Show Organisation"
    end

Thanks @volkerholloh and @danschultzer 😁.
💅🏽
test "redirects to show when data is valid", %{conn: conn} do
-    conn = post(conn, Routes.organisation_path(conn, :create), organisation: @create_attrs)
+    result_conn = post(conn, Routes.organisation_path(conn, :create), organisation: @create_attrs)

-    assert %{id: id} = redirected_params(conn)
+    assert %{id: id} = redirected_params(result_conn)
-    assert redirected_to(conn) == Routes.organisation_path(conn, :show, id)
+    assert redirected_to(result_conn) == Routes.organisation_path(conn, :show, id)

-    conn = get(conn, Routes.organisation_path(conn, :show, id))
+    result_conn = get(conn, Routes.organisation_path(conn, :show, id))
-    assert html_response(conn, 200) =~ "Show Organisation"
+    assert html_response(result_conn, 200) =~ "Show Organisation"
end


Date/timestamp type parsing

Hi,
I’m having an issue with the timestamp type. It seems like it is not being parsed properly. Below, I have the 'created' column set as a timestamp, but the output file types it as a string. The same issue occurs with the date type.
Any help would be greatly appreciated.
I’m using v0.12.2 and PostgreSQL.
(
    user_id        serial primary key,
    email          varchar(255) not null unique,
    passwordHashed varchar(255) not null,
    created        timestamp
);

public readonly record struct GetUserArgs(string Email);
    public async Task<GetUserRow?> GetUser(GetUserArgs args)
    {
        {
            await using var connection = NpgsqlDataSource.Create(connectionString);
            await using var command = connection.CreateCommand(GetUserSql);
            command.Parameters.AddWithValue("@email", args.Email);
            var reader = await command.ExecuteReaderAsync();
            if (await reader.ReadAsync())
            {
                return new GetUserRow
                {
                    User_id = reader.GetInt64(0),
                    Email = reader.GetString(1),
                    Passwordhashed = reader.GetString(2),
                    Created = reader.IsDBNull(3) ? null : reader.GetString(3)
                };
            }

            return null;
        }
    }

Working on a fix

Fixed in release v0.12.3 :)


license/cla Pending — Contributor License Agreement is not signed yet.

URL to the linked Repo/Org:
https://github.com/Comcast/kuberhealthy
Steps to reproduce the problem:

sign cla with legal name instead of email
submit
PR shows license/cla pending
signature unable to be changed

What is the expected result?
accept signature, show error as invalid string, or add text instructing the signature format req'd
What happens instead?
signature text box is locked with presumably invalid signature for github user, project owner unable to merge fork

Your signature is valid. CLA assistant doesn't change the status because you have signed the PR as @cdbitz but not as @chadbitzer . CLA assistant expects that the committer signs the CLA, not the author of the PR. In your case you (@cdbitz) are the author of the PR and @chadbitzer is the committer.

Very helpful lead, hadn't noticed that, thank you @KharitonOff !


Upgrade version running on server?

Whoever runs @CoredumpFlameBot seems to be running an older version - it still can't do cyber, and also still seems to have the typos fixed in 3a80e80047eccf09c6cdfd92a1a596dea0952e48 (November 2017).
Any chance that could be upgraded? :wink:

That would be @netzhuffle :slightly_smiling_face:

Looks like this happened in the meantime - thanks!

Currently we deploy using Ansible, but we could also set up something like Watchtower to auto-deploy when new images are pushed to Dockerhub.


Feature - limit drag between minimum and maximum value

I needed a feature that didn't exist, limiting the slip between the minimum and maximum value, example:
0, 1, 2, 3, 4, 5, 6, 7;
the limit passed as a parameter = 4;
the user can only drag from 0, 1, 2, 3, 4, but 5, 6, 7 are still present.

Thank you for the contribution! I will take a look at it :)

May I ask in which use-case you're using the feature? Just to understand it :)

example:

Today is Monday, I can only drag until Monday.
If it was Tuesday, I could only drag until Tuesday.
If it was Wednesday, I could only drag until Wednesday.
I search for data from the past and the present day, but never from the next days;

Ah I see! Cool. Thanks


CPU/Memory leak issue caused by go routines that never completes

I was running a load/stress test to allocated 10K gameservers every 30 minutes (gameservers shutdowns in 10 minutes after allocation). The performance of the Agones was deteriorating with everyone run. It turns out the 10K+ go routines that are created with every run never completes. In about 7 hours around the total number of go routines reached 400K.

The issue id being caused because of WaitForCacheSync call in gameserver creation. Under huge number of calls, cache never syncs and all the go routines continue to wait indefinitely.
This can be related to #414 .
Working on a fix now. Will submit a PR.

Hello @ilkercelikyilmaz , this seems the same old issue, but reopened after dep ensure execution and I suppose was fixed in as previously
https://github.com/GoogleCloudPlatform/agones/commit/1bdd5a5083c9f732c58f8be9521505b7fb37a764
So please update and rerun your test, at least starting part. 😄

Hi @aLekSer ,
You are right this fixes the issue. However I got it fixed locally by removing the call WaitForCacheSync.
I've tested with the fix only (without removing the WaitForCacheSync). There is no more leak but the GS creation with the WaitForCacheSync and it takes longer under the load test.
Do you think we can close the #414 ?
Thanks,
ilker

Thanks @ilkercelikyilmaz  for checking it with updated master.
Regarding this Memory leak ticket I think you should close this and open new ticket or Pull Request with different description if you see some other problem with WaitForCacheSync() function.
WaitForCacheSync() uses WaitFor() undernearth through next function:
func PollUntil(interval time.Duration, condition ConditionFunc, stopCh <-chan struct{}) error {
	return WaitFor(poller(interval, 0), condition, stopCh)
}

So fixing WaitFor helps here also.

Since the cpu/memory leak issue fixed with 1bdd5a5 closing this issue.


CTYPE= errors RANGE types

In particular, (ctype= (ctype 'single-float) (ctype 'single-float)) results in:
The value
  NIL
is not of type
  NUMBER
when binding SB-KERNEL::X
   [Condition of type TYPE-ERROR]

Restarts:
 0: [RETRY] Retry SLIME REPL evaluation request.
 1: [*ABORT] Return to SLIME's top level.
 2: [ABORT] abort thread (#<THREAD "repl-thread" RUNNING {10015383B3}>)

Backtrace:
  0: (SB-KERNEL:TWO-ARG-= NIL NIL) [external]
  1: (SB-VM::GENERIC-=)
  2: ((:METHOD CTYPE= (RANGE RANGE)) #<RANGE SINGLE-FLOAT> #<RANGE SINGLE-FLOAT>) [fast-method]
  3: ((SB-PCL::EMF CTYPE=) #<unused argument> #<unused argument> #<RANGE SINGLE-FLOAT> #<RANGE SINGLE-FLOAT>)

I think the problem is parse-interval-designator returning NIL, which then gets used by the ctype= method, but sure if there are other ways to fix this:
https://github.com/s-expressionists/ctype/blob/563a287bce26ac69d8eb2306e71ffa0794716f84/parse.lisp#L69-L75
https://github.com/s-expressionists/ctype/blob/563a287bce26ac69d8eb2306e71ffa0794716f84/range.lisp#L35-L41

Every implementation I know of uses IEEE 754 floats, which have infinities and NaNs that may be part of the unbounded type but not the bounded type.


[cxx-interop] Conform std::string to ExpressibleByStringLiteral

This allows std::string to be constructed implicitly from a String literal, which is convenient e.g. when calling C++ APIs that take std::string as a parameter.

@swift-ci smoke test


Change return type for some errors:

Use OK for ApplicationError
Use BadRequest for DeveloperError

Description
Use 502 BadGateway seems not suitable for ApplicationError and DeveloperError
Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[ ] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[ ] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[ ] I updated the documentation where necessary.

@jiangpengcheng Please see https://github.com/apache/openwhisk/issues/645#issuecomment-234782050. I support this change in general but this should be alerted on the dev list at least. Also instead of 200 OK, 207 as suggested in the issue might be more appropriate (or a 40x).

@jiangpengcheng Please see https://github.com/apache/openwhisk/issues/645#issuecomment-234782050. I support this change in general but this should be alerted on the dev list at least. Also instead of 200 OK, 207 as suggested in the issue might be more appropriate (or a 40x).

@rabbah  thans for mentioning, I will check that issue

@rabbah  thans for mentioning, I will check that issue

Codecov Report

Merging #5047 (10ab739) into master (6686820) will decrease coverage by 11.11%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           master    #5047       +/-   ##
===========================================
- Coverage   82.35%   71.23%   -11.12%
===========================================
  Files         206      199        -7
  Lines       10006     9741      -265
  Branches      445      442        -3
===========================================
- Hits         8240     6939     -1301
- Misses       1766     2802     +1036

Impacted Files
Coverage Δ

...org/apache/openwhisk/core/controller/Actions.scala
90.78% <50.00%> (ø)

...che/openwhisk/core/invoker/LogStoreCollector.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/RxObservableImplicits.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedConsumer.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0.00% <0.00%> (-95.85%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0.00% <0.00%> (-93.90%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0.00% <0.00%> (-92.31%)
:arrow_down:

...a/org/apache/openwhisk/http/BasicHttpService.scala
3.33% <0.00%> (-86.67%)
:arrow_down:

...la/org/apache/openwhisk/http/BasicRasService.scala
16.66% <0.00%> (-83.34%)
:arrow_down:

... and 51 more

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 6686820...10ab739. Read the comment docs.

Codecov Report

Merging #5047 (10ab739) into master (6686820) will decrease coverage by 11.11%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##           master    #5047       +/-   ##
===========================================
- Coverage   82.35%   71.23%   -11.12%
===========================================
  Files         206      199        -7
  Lines       10006     9741      -265
  Branches      445      442        -3
===========================================
- Hits         8240     6939     -1301
- Misses       1766     2802     +1036

Impacted Files
Coverage Δ

...org/apache/openwhisk/core/controller/Actions.scala
90.78% <50.00%> (ø)

...che/openwhisk/core/invoker/LogStoreCollector.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/RxObservableImplicits.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedConsumer.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0.00% <0.00%> (-95.85%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0.00% <0.00%> (-93.90%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0.00% <0.00%> (-92.31%)
:arrow_down:

...a/org/apache/openwhisk/http/BasicHttpService.scala
3.33% <0.00%> (-86.67%)
:arrow_down:

...la/org/apache/openwhisk/http/BasicRasService.scala
16.66% <0.00%> (-83.34%)
:arrow_down:

... and 51 more

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 6686820...10ab739. Read the comment docs.

Has anyone yet looked at the interaction with the npm openwhisk client and the CLI?


Reduce permissions asked for login

This level of access seems quite extreme:

Could you at least explain why those permissions are needed?

Thanks for the PR.
I'm really sorry about that, Contributor-ninja shouldn't require any special information from GitHub (maybe only your public email address).
The code is here https://github.com/contributor-ninja/contributor.ninja/blob/master/src/Components/Login.js#L6 and it seems that it has a bug in it.
Would you be open to make a PR to fix that?

cc @qZzQ1 if you'd like to look at it

Thanks for the fast response. Unfortunately I don't have any experience interfacing with Github's permissions system, and at the moment don't have the availability to research the topic. But if you give me some pointers on what the correct code should be, I'd be happy to submit a PR :)

Thanks for the fast response. Unfortunately I don't have any experience interfacing with Github's permissions system, and at the moment don't have the availability to research the topic. But if you give me some pointers on what the correct code should look like, I'd be happy to submit a PR :)

Ok, it's live (modulo the browser/CDN cache).
This is what it looks like now:

Probably less scary :smile:


How can I remove/add columns using the Table Storage?

I read on one of the tickets how to add custom columns, but what about the ones that are created by default? I can't find a way to delete them.

Hi,
Is it possible without fork ?


Energy monitoring

Trying to add a sonoff s31 for energy monitoring but it doesn’t show up. My tazmotized ones do, but I hoped the original firmware would as well. Homeassistant says it’s a bug and to send you this link. Thanks for what you do!
https://developers.home-assistant.io/docs/core/entity/sensor#long-term-statistics

I have the S31TPB, and I get energy monitoring right after I start the integration, but it stops after a few minutes.

Download device diagnostics

I have the same issue, here is my diagnostic
 {
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.3.6",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.10",
    "docker": true,
    "arch": "aarch64",
    "timezone": "America/Los_Angeles",
    "os_name": "Linux",
    "os_version": "5.15.90",
    "supervisor": "2023.03.3",
    "host_os": "Home Assistant OS 9.5",
    "docker_version": "20.10.22",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {
    "smartthinq_sensors": {
      "version": "0.31.4",
      "requirements": [
        "pycountry>=20.7.3",
        "xmltodict>=0.12.0",
        "cchardet>=2.1.7"
      ]
    },
    "teamtracker": {
      "version": "0.1",
      "requirements": [
        "arrow",
        "aiofiles"
      ]
    },
    "mail_and_packages": {
      "version": "0.3.10",
      "requirements": [
        "beautifulsoup4",
        "Pillow>=9.0"
      ]
    },
    "hacs": {
      "version": "1.31.0",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "eufy_security": {
      "version": "6.2.0",
      "requirements": [
        "websocket-client==1.1.0",
        "aiortsp==1.3.6"
      ]
    },
    "adaptive_lighting": {
      "version": "1.7.0",
      "requirements": []
    },
    "sonoff": {
      "version": "3.5.1",
      "requirements": [
        "pycryptodome>=3.6.6"
      ]
    },
    "sonos_cloud": {
      "version": "0.3.5",
      "requirements": []
    },
    "o365": {
      "version": "v4.2.8",
      "requirements": [
        "O365==2.0.26",
        "BeautifulSoup4>=4.10.0"
      ]
    },
    "alexa_media": {
      "version": "4.6.2",
      "requirements": [
        "alexapy==1.26.5",
        "packaging>=20.3",
        "wrapt>=1.12.1"
      ]
    }
  },
  "integration_manifest": {
    "domain": "sonoff",
    "name": "Sonoff",
    "config_flow": true,
    "documentation": "https://github.com/AlexxIT/SonoffLAN",
    "issue_tracker": "https://github.com/AlexxIT/SonoffLAN/issues",
    "codeowners": [
      "@AlexxIT"
    ],
    "dependencies": [
      "http",
      "zeroconf"
    ],
    "requirements": [
      "pycryptodome>=3.6.6"
    ],
    "version": "3.5.1",
    "iot_class": "local_push",
    "is_built_in": false
  },
  "data": {
    "version": "122751c",
    "cloud_auth": true,
    "config": null,
    "options": {},
    "errors": [],
    "device": {
      "uiid": 32,
      "params": {
        "bindInfos": "***",
        "version": 8,
        "only_device": {
          "ota": "success"
        },
        "sledOnline": "on",
        "ssid": "***",
        "bssid": "***",
        "fwVersion": "3.5.0",
        "staMac": "***",
        "rssi": -56,
        "init": 1,
        "alarmType": "pcv",
        "alarmVValue": [
          -1,
          -1
        ],
        "alarmCValue": [
          -1,
          -1
        ],
        "alarmPValue": [
          -1,
          -1
        ],
        "switch": "off",
        "startup": "stay",
        "pulse": "off",
        "pulseWidth": 500,
        "power": "0.00",
        "voltage": "120.96",
        "current": "0.00",
        "oneKwh": "start",
        "timeZone": -7,
        "uiActive": 120,
        "hundredDaysKwh": "get",
        "endTime": "",
        "startTime": "2022-10-03T04:40:12.999Z",
        "demNextFetchTime":<PHONE_NUMBER>000
      },
      "model": "S31TPB(US)",
      "online": true,
      "local": true,
      "localtype": "enhanced_plug",
      "host": "<IP_ADDRESS>:8081",
      "deviceid": "10014f7ce5"
    }
  }
}

So S31 has POW2 firmware. Energy sensor disabled by default. You need to enable it manually.

Did you ever get this to work? I'm not sure where to enable it


Jumpdest analysis

PR description
Adds ability to cache Code objects and use them for future calls which will avoid the re-computing of JUMP destinations.
No additonal tests have been added to demonstrate performance improvement. The correct place for those remains an open question.
Fixed Issue(s)

fixes #2607
Changelog

[X] I thought about the changelog and included a changelog update if required.

What is the performance improvement observed? Is there a possibility to also persist the cache across restarts? Is there a way to add meters to see cache hits and misses?

What is the performance improvement observed? Is there a possibility to also persist the cache across restarts? Is there a way to add meters to see cache hits and misses?

The test provided was a pathological case run against London, Berlin, and Istanbul protocol spec. Runtime was reduced for the specific case tested.  Caution, napkin math:
London   14%
Berlin      21%
Istanbul    5%
So nothing to write home about, but it's an improvement. Sure we could measure cache hits and misses. I think in hindsight with what I learned doing this, I would just add the bitmap of the jumpdestinations to AccountState the first time it is run, and store it.

21% is pretty cool. I guess you’re talking about execution time.

Yeah, thats on a pretty pathological case so I don't expect it to be the same improvement in regular mainnet usage. However, it was interesting to me that on a daily basis, there are less than 10k unique contracts being used on mainnet. Given tx volume, that should be a lot of redundant jumpdest analysis that is eliminated.


Suggested improvements for models/demos/tg/llama3_70b/README.md

Remove export WH_ARCH_YAML=wormhole_b0_80_arch_eth_dispatch.yaml line in the README.md file because galaxy is unharvested.
README makes reference to models/demos/t3000/llama2_70b/scripts/repack_weights.py and would be nice if this was part of a common llama utility scripts folder or repackaged under models/demos/tg/llama3_70b/scripts/repack_weights.py. Same thing goes for the referenced requirements.txt file.

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


moveTo api will create a full screen svg shadow

can't click highlighted part if called movedTo api, because the svg draw the whole screen

It's working fine for me. Here's the working example (code). Click Activate button to activate and then click moveTo to move to specific step. Could you provide a reproducing example?

my  case is call moveTo directly

You should use .drive(index) instead with the index to start tour with. moveTo is used when the driver is already active.


#751 fix - Replaces decimals from backend with decimals from blockchain

Closes #751
Description

As described in the ticket, we found that some decimals from the backend where wrong, so we decided to fix this taking the decimals from the blockchain.

Travis automatic deployment:
https://pr755--safereact.review.gnosisdev.com/app

I wouldn't merge this until we figure out where incorrect values were coming from.

I wouldn't merge this until we figure out where incorrect values were coming from.
Also

we found that some decimals from the backend where wrong

there's no evidence of that in ticket's discussion

Agree.

Travis automatic deployment:
https://pr755--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr755--safereact.review.gnosisdev.com/app

Ok after doing some research for a while with @fernandomg, we found that the problem was when we JSON.stringify the token object, to store it in localStorage. It happens that truffle-contract returns a BN (bn.js) instance for numeric values. BN handles values internally as hex values but without the leading 0x, so when it's stringified the toJSON method is called, and it returns the hex value without the leading 0x giving us a 12 instead of an 18 (0x12).
When that value was recovered from the localStorage, it was treated as a valid string representation of the decimal value.
In order to fix this, we converted the BigNumber object to a number (using toNumber method) before calling makeToken. Also, for the tokens that are already stored in the user's localStorage, we removed them from then list checking the type of the object.
> decimals = web3Utils.toBN('18')
<BN: 12>
> JSON.stringify({ decimals })
'{"decimals":"12"}'
> JSON.parse(JSON.stringify({ decimals }))
{ decimals: '12' }
> new bn(JSON.parse(JSON.stringify({ decimals })).decimals, 16).toNumber()
18

@francovenica in order to test this, you need to look for a token that's not present on the backend, like 0xEc0B6AFb3F9a609CEEd67e2CA551A4c573fd45F7 . You can see that on both localStorage and redux, the decimals for that tokens is was 12. Now should be 18, must also update data from localStorage's with 12 decimals.

@fernandomg @Agupane

Travis automatic deployment:
https://pr755--safereact.review.gnosisdev.com/app

@fernandomg @Agupane
I've tried by using the safe where I reported the issue initially.
Went to the Transaction tab and then switched to the 2nd page (25 rows per page) and the site crashed throwing a ton of errors.
Can you tell me if those are related to this ticket?
The safe:
https://pr755--safereact.review.gnosisdev.com/app/#/safes/0xc3214e72A53695faC3A124C92FcA3f161D193299/transactions
Snapshot:

@francovenica this is related to the safe apps @nicosampler

@mikheevm gotcha. Thanks. I'll ignore it for this ticket
I've created a new safe and transferred some funds to it: BAT, REP, ZRX
They now show the right values:
The safe:
https://pr755--safereact.review.gnosisdev.com/app/#/safes/0x4816Fae09FdFaF6927E785EFe68E5D68f5740840/transactions
Snapshot:

Also as Agu Pane told me I've checked in the redux and they now show 18 decimals:

Looks good to me


Update Unity.gitignore

Add .idea/ for the Rider cache directory. it's exactly the same interest as the visual studio cache directory.
Reasons for making this change:
Because Rider is used by a lot of Unity Developers and has a cache directory too. Like Visual Studio.

I always manually add this, would be a good addition.

See: https://github.com/github/gitignore/pull/3529#issuecomment-810453567

Duplicate of #3529


Some models have a performance degradation of approximately 20 times on the iPhone Pro Max compared to running on M1 Pro Macbook while standard Stable Diffusion 2.1 is just ~1.5x degradation on iPhone.

I have tested the following models on my iPhone 14 Pro Max:
1: coreml-stable-diffusion-2-1-base
https://huggingface.co/pcuenq/coreml-stable-diffusion-2-1-base
https://huggingface.co/pcuenq/coreml-stable-diffusion-2-1-base/blob/main/coreml-stable-diffusion-2-1-base_split_einsum_compiled.zip
took ~15s on Mackbook M1 Pro
took ~ 20s on iPhone 14 Pro Max
2: coreml-8528-diffusion
https://huggingface.co/coreml/coreml-8528-diffusion
https://huggingface.co/coreml/coreml-8528-diffusion/blob/main/split_einsum/8528-diffusion_split-einsum_compiled.zip
took ~15s on Mackbook M1 Pro
took ~5min on iPhone 14 Pro Max
and the memory usage is alot more than the first model.
here is my configuration:

#if targetEnvironment(macCatalyst)
let runningOnMac = true
#else
let runningOnMac = false
#endif

let configuration = MLModelConfiguration()
configuration.computeUnits = runningOnMac ? .cpuAndGPU : .cpuAndNeuralEngine
let pipeline = try StableDiffusionPipeline(resourcesAt: url,
configuration: configuration,
disableSafety: false,
reduceMemory: !runningOnMac)

var config = StableDiffusionPipeline.Configuration(
    prompt: "string1"
)
config.negativePrompt = "string2"
config.stepCount = numInferenceSteps // 15
config.seed = UInt32(seed) // 32
config.guidanceScale = Float(guidanceScale) // 7.5
config.disableSafety = disableSafety // true
config.schedulerType = .dpmSolverMultistepScheduler

Hi @jo32, sorry for the delay in getting back to you. Are those results consistent across runs? I've seen some erratic behaviour on iPhone myself – sometimes it's very fast and sometimes it's slow, with no changes in model or configuration whatsoever. When generation is slow, the phone heats up a lot. I believe in those cases the ANE is not engaged and all the work is done on CPU. It could be because of additional system load, memory pressure or other reasons.
This is my go-to list when that happens:

Detach from Xcode. I think I've observed slowness more frequently when running the app from Xcode, but I'm not positive that could be a factor.
Wait a few minutes for the device to come back to normal temperatures.

I'll take a look at that particular model you mention to see if I can replicate the issue.

Hi @jo32, sorry for the delay in getting back to you. Are those results consistent across runs? I've seen some erratic behaviour on iPhone myself – sometimes it's very fast and sometimes it's slow, with no changes in model or configuration whatsoever. When generation is slow, the phone heats up a lot. I believe in those cases the ANE is not engaged and all the work is done on CPU. It could be because of additional system load, memory pressure or other reasons.
This is my go-to list when that happens:

Detach from Xcode. I think I've observed slowness more frequently when running the app from Xcode, but I'm not positive that could be a factor.
Wait a few minutes for the device to come back to normal temperatures.

I'll take a look at that particular model you mention to see if I can replicate the issue.

Yes, this problem persist, actually this model consistently crashes on my iPhone 14 Pro Max no matter whether I detached the iPhone or cool it down:
https://huggingface.co/coreml/coreml-8528-diffusion/blob/main/split_einsum/8528-diffusion_split-einsum_compiled.zip

I have tested the following models on my iPhone 14 Pro Max:
1: coreml-stable-diffusion-2-1-base https://huggingface.co/pcuenq/coreml-stable-diffusion-2-1-base https://huggingface.co/pcuenq/coreml-stable-diffusion-2-1-base/blob/main/coreml-stable-diffusion-2-1-base_split_einsum_compiled.zip
took ~15s on Mackbook M1 Pro took ~ 20s on iPhone 14 Pro Max
2: coreml-8528-diffusion https://huggingface.co/coreml/coreml-8528-diffusion https://huggingface.co/coreml/coreml-8528-diffusion/blob/main/split_einsum/8528-diffusion_split-einsum_compiled.zip
took ~15s on Mackbook M1 Pro took ~5min on iPhone 14 Pro Max
and the memory usage is alot more than the first model.
here is my configuration:
#if targetEnvironment(macCatalyst)
let runningOnMac = true
#else
let runningOnMac = false
#endif

let configuration = MLModelConfiguration()
configuration.computeUnits = runningOnMac ? .cpuAndGPU : .cpuAndNeuralEngine
let pipeline = try StableDiffusionPipeline(resourcesAt: url,
configuration: configuration,
disableSafety: false,
reduceMemory: !runningOnMac)

var config = StableDiffusionPipeline.Configuration(
    prompt: "string1"
)
config.negativePrompt = "string2"
config.stepCount = numInferenceSteps // 15
config.seed = UInt32(seed) // 32
config.guidanceScale = Float(guidanceScale) // 7.5
config.disableSafety = disableSafety // true
config.schedulerType = .dpmSolverMultistepScheduler

Could you share your iOS app project? How are you compiling your app with this config and running it?


add bachitter.dev

I like how the site is consistent in both mobile and web with the same layout, :D

I like how the site is consistent in both mobile and web with the same layout, :D

Thanks, I saw a tweet about a concept app and used that as inspiration.


Complete Code Exploration team formation

This PR:

Adds the Code Exploration Vision in our strategy folder
Adds ownership overview for the Code Exploration team
Removes the frontend platform and integration teams

I reviewed the content of the pages and decided that the goals etc all don't apply in their current form. It's all in the Git history, if we ever want to bring it back.
The only page worth keeping is the browser extension release process, which I'm going to create a separate PR to sourcegraph/sourcegraph for since it really belongs more into our dev docs https://github.com/sourcegraph/sourcegraph/pull/44693

@sourcegraph/code-exploration feel free to open a PR to bring back any processes you liked from the old teams!

I created a new page for the Frontend Crew in a new folder guilds/ (adjacent to teams/), and pointed some things that FPT owned before to be owned collectively by the Frontend Crew

I also moved the Release Guild into this folder for consistency

Added our weekly sync as a process
Removed the hardcoded VS Code theme that was in settings.json for some reason and was driving me crazy

I am going to merge this since I'm going on PTO after today, but please still give it a look everyone @sourcegraph/code-exploration

🚀  Awesome! Thank you @felixfbecker!

Thanks for the details @felixfbecker everything looks good and makes sense to me.


Switch buttons would be great to have

Hello,
Having a new input field "switch" would be great to have(ie: On, Off).
Thanks,

I'll add a switch on the next push.

Added to version 1.0.1.


Just thank you!

I know this is not really the place. But I just wanted to say thank you for this awesome library. Really makes my life easier.
Thanks for the library, thank you for the documentation, thank you for all your personal time into this library.

Thank you so much. I am glad the library helps you. really appreciate this :)


chore: add skeleton files for MDC-based implementation of chips

Thanks for the feedback! I pushed the requested changes.


Css Updates

Following changes have been made:

Global box-sizing added
Accordion expand/collapse animation added
Header top/bottom padding removed. Added a fixed height. Logo has been enlarged a little
Footer was broken after setting box-sizing for all elements. Fixed that

Thanks @meghsohor - appreciate the work on this. Apologies for such a slow merge, I've been moving and work has been hectic.

Thank you very much @karlhadwen. I hope everything is going fine. Have a great Christmas!


ML.Net ARM : Could not assembly 'Microsoft.ML.ModelBuilder.AutoMLService'

System Information (please complete the following information):

Model Builder or CLI Version: 16.2.0 ML.Net
System: NVIDIA Jetson Nano, Ubuntu 18.04.5 LTS, JetPack 4,.4.
Visual Studio Version (if applicable):

Describe the bug

On which page of the tutorial did you run into an issue (URL):
https://dotnet.microsoft.com/learn/ml-dotnet/get-started-tutorial/train
Clear description of the problem:
Could not load file or assembly 'Microsoft.ML.ModelBuilder.AutoMLService, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. An attempt was made to load a program with an incorrect format.

To Reproduce
Steps to reproduce the behavior:
mlnet classification --dataset "yelp_labelled.txt" --has-header false --label-col 1 --train-time 20
Expected behavior
Ml Model should get trained
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

@LittleLittleCloud ,cloud have any idea why is this issue?

Hi @crazyoutlook
MLNet currently doesn't support ARM device because some of its libraries can only run on x64/86 platform. But as I know, @michaelgsharp in MLNet team is working on replacing those libraries with arm-compatible ones. So maybe in the next release this error will gone.

Close due to no response, feel free to reopen it if you have any other questions.


[iOS] Create Favorites Screen Frame

Kind (Required)

Improvement

Overview (Required)

This issue can work after #443 merged.
Please implement Favorites Screen Frame.

It's ok to implement items(Cards) with empty views.

Links

Figma

I wanna take this!

Thanks! Assigned 👍🏼


Emit/output error when using += operator with Delegates

A severe output error happens whenever an Delegate is bound using the += operator.
The bug was reported here Delegate Compilation Bug
For instance:

broken: test.Delegate += Callback;
works: test.Delegate = test.Delegate + Callback;

This issue might be related to #407.


Pete

added the 3 band images and associated the file to the banduser

I think I have a better idea


Application setup instructions are inaccurate/confusing

This issue is generally about the POA setup docs, which make it difficult to set up the application for deployment.  Here are two instances of confusing documentation:
ARM template for applications
The Platform Orchestration App(POA) suggests using an ARM template to manage the application.  The ARM template for applications refers to an application and applicationType resource.  The link between the two does not seem to match.
In the following doc page:https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-application-arm-resource#add-a-new-application-to-your-resource-manager-template
The applicationType resource appears to use the following property for the name:"name": "[concat(parameters('clusterName'), '/', parameters('applicationTypeName'))]"
The application resource appears to use the following property for its typeName:"typeName": "[parameters('applicationTypeName')]"
The default value for applicationTypeName is "ApplicationType", which appears different.
In addition, there's no description anywhere for what these fields mean.  A lot of meaning needs to be inferred.
Location of POA package
On the following page:https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-application-arm-resource#add-a-new-application-to-your-resource-manager-template
Bullet 3 indicates to create a zipped package and place it in a file share.  In the next sentence it states this file share must be accessible via a REST call.  These two sentences are incongruent.

Thanks for the feedback! We are currently investigating and will update you shortly.

Thanks @jeff-ng
@dkkapur can you take a look and see if we can address these concerns with the doc?

@athinanthny, I updated you to be the assignee for this issue because you are listed as the current document owner in the article metadata. Could you please work to address the feedback and close the issue? See these instructions.

#reassing @khandelwalbrijesh please review

#reassign @khandelwalbrijesh  please review this doc issue related to POA

Great suggestions, thank you. I've updated the doc with recommended clarifications. Also, there's a more recent doc with more details on application deployment process: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-concept-resource-model
(I've filed a task to consolidate these two articles, hopefully in the near future).
#please-close


add DOM diffing/patching category containing virtual-dom and morphdom

Those are mainly for the browser. This list is for awesome Node.js stuff.
Also, in the future please review the diff before submitting a PR. Lots of incorrect changes in there.

Noted. Yeah that PR was borked. Apologies.


getVertexDataframe() does not handle no data being returned

getVertexDataframe() does not handle no data being returned from the REST API.

Fixed in #12 (released in v0.0.8)


Dev server error when opening more than 3 tabs on chrome

Hi,
Currently, when I open more than 3 tabs in development mode (SPA) on chrome, the new opened tab and the hot-reload will not working, the tabs were freezing a while and then showing the error below:
Uncaught (in promise) Error: Manifest request to /dashboard/_nuxt/2fab9335f71ae93c4c97.hot-update.json timed out.
    at XMLHttpRequest.request.onreadystatechange (runtime.js:92)

If I only open 3 tabs or less, everything worked fine. The error occurs even with the fresh created nuxt app.
It seems that the problem doesn't occur on Safari.
Recorded video:
https://user-images.githubusercontent.com/27690861/124388347-b91d8e00-dd0c-11eb-8c52-f240fdf8184f.mov
Versions

nuxt: 2.14.12 (I also tried the latest version - v2.15.7)
node: 12.14.0

Reproduction

Repository: https://github.com/bahung1221/nuxt-dev-server-error-reproduce

Thanks a lot!

Okay I found something in https://github.com/nuxt/nuxt.js/issues/6007.
It seems this is the problem of webpack dev server, it weird that I never faced this problem before (maybe the last time I working with nuxt is one year ago, I don't remember exactly the version).
The need to open multiple tabs is important because I need to compare and preview my GUI on multiple devices size (simulators). And our designer also needs to do that, too.
Is there any workaround for this problem on chrome?
Thanks a lot 🍺

I had this problem as well recently and got "chunkloaderror" and "failed to load component" due to it. I do wish the documentation would give a very explicit warning about this, as opening multiple tabs is a common task.

It seems that this issue doesn't occur on Nuxt SSR mode, only occurs on SPA mode.

This is no longer reproducible in Nuxt 3.


Some source and project file cleanup

Remove unused CAS files
Remove experimental Evo API
Remove experimental cevobuild projects
Move Tritium framework headers to products

@swift-ci please smoke test


Android Oreo (8.0) Support

Apps targeting Android 8.0 (API level 26) cannot use TYPE_SYSTEM_OVERLAY  and TYPE_SYSTEM_OVERLAY . Targeting 26 will cause the app to crash when in DEV_MODE.
https://developer.android.com/about/versions/oreo/android-8.0-changes.html#cwt
This PR replaces uses of these overlay flags with the new TYPE_APPLICATION_OVERLAY when running on a device with Android 8.0 or later.
When using TYPE_APPLICATION_OVERLAY it still requires the SYSTEM_ALERT_WINDOW permission, just like previous android versions.
https://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#TYPE_APPLICATION_OVERLAY
Test Plan
https://github.com/AndrewJack/react-native-android-oreo tested here

Without the changes in this PR you will see the following crash:
08-22 12:30:22.707 25262-25262/com.androido E/AndroidRuntime: FATAL EXCEPTION: main
                                                              Process: com.androido, PID: 25262
                                                              android.view.WindowManager$BadTokenException: Unable to add window android.view.ViewRootImpl$W@4e96541 -- permission denied for window type 2006
                                                                  at android.view.ViewRootImpl.setView(ViewRootImpl.java:789)
                                                                  at android.view.WindowManagerGlobal.addView(WindowManagerGlobal.java:356)
                                                                  at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:92)
                                                                  at com.facebook.react.devsupport.DevLoadingViewController.setVisible(DevLoadingViewController.java:150)
                                                                  at com.facebook.react.devsupport.DevLoadingViewController.access$100(DevLoadingViewController.java:39)
                                                                  at com.facebook.react.devsupport.DevLoadingViewController$1.run(DevLoadingViewController.java:71)
                                                                  at android.os.Handler.handleCallback(Handler.java:789)
                                                                  at android.os.Handler.dispatchMessage(Handler.java:98)
                                                                  at android.os.Looper.loop(Looper.java:164)
                                                                  at android.app.ActivityThread.main(ActivityThread.java:6541)
                                                                  at java.lang.reflect.Method.invoke(Native Method)
                                                                  at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
                                                                  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:767)

@shergin Looks good to me if you want to ship.

Any update on this? Definitely seeing this crash and the patch looks good. The CI failure seems to be unrelated to this code unless I am missing something

Thanks @AndrewJack for the PR and @shergin for shipping 🎉

@AndrewJack @janicduplessis   Any update on this?? I'm facing this issue.

@rekha110254 What version are you using? This was only shipped in RN 0.50.

@AndrewJack thanks for this PR, this bug is kicking my project in the shins. I am using RN 0.41 and wondering if there is a recommended way to incorporate this fix outside of 1) upgrading to RN 0.51 and possibly upsetting my other dependencies and 2) manually updating the source files for RN creating an unsupported unique version of the RN codebase just for me :/? Basically I am hoping and wondering if there is a way to just incorporate these changes related to the overlay or do I just need to take the upgrade plunge?
Thanks

is navigator.geolocation.getCurrentPosition working in Android 8?  Could someone with actual device test it?

@AndrewJack  RN 0.51.1


Implement folded traversals for MSSQL

This PR implements folded traversals for the MSSQL backends. A new integration test for folded traversals has been added, and all relevant test_compiler tests have been updated.

Also, as I remember we don't have _x_count and multiple fold outputs for mssql, so there's no interactions to worry about. Correct me if I'm wrong here.

This is correct! _x_count and multiple fold outputs are not yet implemented for MSSQL.


JAMES-33775 RSpamDListener

jira https://issues.apache.org/jira/browse/JAMES-3775

If we are interestead about consistency we can propose on the mailing list to move all spamassassin stuff in a new thrid-party/spamassassin module.

Yes,
<EMAIL_ADDRESS>

Rebase master & squash fixup


JRuby nokogiri incorrectly include xml declaration for html transformation

Using the following code:
input_xml = <<-EOS
<?xml version="1.0" encoding="utf-8"?>
<report>
  <title>My Report</title>
</report>
EOS

input_xsl = <<-EOS
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:template match="/">

        <title><xsl:value-of select="report/title"/></title>

<xsl:value-of select="report/title"/>

  </xsl:template>
</xsl:stylesheet>
EOS

require 'nokogiri'

xml = ::Nokogiri::XML(input_xml)
xsl = ::Nokogiri::XSLT(input_xsl)

puts xsl.apply_to(xml)

expected behavior:

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>My Report</title>

My Report

actual behavior:
<?xml version="1.0" encoding="UTF-8"?><title>My Report</title>
My Report

Hey everyone! Just wanted to give you a heads up that I'm actively working on this issue and putting in my best effort to find a solution.

I'm not an expert on xslt, but shouldn't the method be set by an xsl:output element?

To follow up on this, I think our jruby XSLT processor is incorrectly determining the default method. Here's what the standard  has to say:

The default for the method attribute is chosen as follows. If

the root node of the result tree has an element child,

the expanded-name of the first element child of the root node (i.e. the document element) of the result tree has local part html (in any combination of upper and lower case) and a null namespace URI, and

any text nodes preceding the first element child of the root node of the result tree contain only whitespace characters,

then the default output method is html; otherwise, the default output method is xml. The default output method should be used if there are no xsl:output elements or if none of the xsl:output elements specifies a value for the method attribute.

It's not clear to me why this is failing. The UNKNOWN method's description doesn't match what the standard says, but it seems like it should still be serializing this as html.
To get the output you want, I think you just need to use an xsl:output element. I've added a line to your example:
input_xml = <<-EOS
<?xml version="1.0" encoding="utf-8"?>
<report>
  <title>My Report</title>
</report>
EOS

input_xsl = <<-EOS
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <xsl:output method="html" encoding="utf-8" />
  <xsl:template match="/">

        <title><xsl:value-of select="report/title"/></title>

<xsl:value-of select="report/title"/>

  </xsl:template>
</xsl:stylesheet>
EOS

require 'nokogiri'

xml = ::Nokogiri::XML(input_xml)
xsl = ::Nokogiri::XSLT(input_xsl)

puts xsl.apply_to(xml)

The output I get is

<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>My Report</title>

My Report

root@e350b53df4bf:/usr/src/myapp# jruby --version
jruby <IP_ADDRESS> (3.1.4) 2023-06-07<PHONE_NUMBER> OpenJDK 64-Bit Server VM 25.372-b07 on 1.8.0_372-b07 +jit [aarch64-linux]
root@e350b53df4bf:/usr/src/myapp# nokogiri --version
/usr/local/bundle/gems/nokogiri-1.15.2-java/lib/nokogiri/xml/node.rb:1007: warning: method redefined; discarding old attr
# Nokogiri (1.15.2)
    ---
    warnings: []
    nokogiri:
      version: 1.15.2
    ruby:
      version: 3.1.4
      platform: java
      gem_platform: universal-java-1.8
      description: jruby <IP_ADDRESS> (3.1.4) 2023-06-07<PHONE_NUMBER> OpenJDK 64-Bit Server VM
        25.372-b07 on 1.8.0_372-b07 +jit [aarch64-linux]
      engine: jruby
      jruby: <IP_ADDRESS>
    other_libraries:
      isorelax:isorelax: '20030108'
      net.sf.saxon:Saxon-HE: 9.6.0-4
      net.sourceforge.htmlunit:neko-htmlunit: 2.63.0
      nu.validator:jing: 20200702VNU
      org.nokogiri:nekodtd: 0.1.11.noko2
      xalan:serializer: 2.7.3
      xalan:xalan: 2.7.3
      xerces:xercesImpl: 2.12.2
      xml-apis:xml-apis: 1.4.01

I agree with @stevecheckoway's take that Xalan should be handling this case correctly, looking at the code for ToUknownStream.java.
If someone could throw this into a java debugger and tell us what's going on in Xalan that would be extremely helpful. I just spent an hour trying to get jdb to work on my system and couldn't figure it out.


fix: Delete empty values iterates through nested arrays

Proposed Change

Added implementation for iterating through slices in telemetry
Cleans value depending on value in array, whether empty, map, slice,  or str.
Add unit tests to handle

Testing

Unit testing
Test agent locally in bp to see proper processor behavior

Logs sent in

### Result seen in recent telemetry

Couple nits otherwise this is working well for me...
These attributes:
Get converted to this after the processor:

Pretty sure we want to keep this behavior. As an array, not sure how it would be possible to make the array layout array[0], array[1], array[3]. Because it is an array, I think moving up that value to the position of the deleted one makes sense.

Yea the behavior is correct, I was just posting that there showing it working.


Revisit verification and type inference tests as part of conformance suite

When writing the spec and then when implementing the interpreter, we put a lot of effort into adding structure to verification and type inference tests, but I still find them somewhat hard to wrap my head around. For example, some things that immediately come to mind are:

Verifiers for some ops are in ops_stablehlo.mlir and for other ops are in separate verify_foo.mlir files. I think we should have separate verify_foo.mlir tests for all ops, similarly to how we have separate interpret_foo.mlir tests.
In these files, should we also explicitly call out the constraints which are not covered by ODS as deliberately out of scope? Right now, we just skip them and don't mention them at all.
We don't have crisp guidelines for type inference tests, so things are hectic there overall.
Positive tests don't have crisp guidelines either. Do we even need to have them?

Related ticket: #1004.

On a related note, because of #1571, we may end up skipping another round of audits / introducing additional structure for most of the Not in HLO and Miscellaneous ops. These ops, if they end up staying in the StableHLO opset, could use extra attention.


Automatically parse long form emails in from field

We had a ticket submitted from a customer that could not send due to non-ASCII characters in the from:
'from'=>'Gérard Depardieu<EMAIL_ADDRESS>This caused an error in the transmissions API. There are tickets in flight to address, but there are two workarounds:

Use the longer format of name and email being separate keys in a sub-associative array
Put double quotes around the email name

We should just take whatever the user submits to from and parse it to use the name and email format.

Withdrawing: see this comment


test_balancer_updates_scans: fixture 'setup_with_healthmonitor' not found

Test fails because of missing fixture.
/Users/longstaff/Projects/f5-openstack-lbaasv2-driver/test/functional/test_balancer_updates_scans.py:270
_____________ ERROR at setup of TestHealthMonitorUpdateScenarios.test_healthmonitor_update_configs[id-e198f4bf-fb6d-4790-8d7c-840eae3d5459_test] _____________
file /Users/longstaff/Projects/f5-openstack-lbaasv2-driver/test/functional/test_balancer_updates_scans.py, line 270
def test_healthmonitor_update_configs(self,
fixture 'setup_with_healthmonitor' not found
available fixtures: setup_with_pool, tmpdir_factory, pytestconfig, setup_with_pool_member, cov, setup_with_loadbalancer, cache, recwarn, polling_neutronclient, bigip, monkeypatch, setup_with_listener, nclientmanager, setup_with_nclientmanager, record_xml_property, capfd, capsys, tmpdir
use 'py.test --fixtures [testpath]' for help on them.

Tests were updated but not merged into repo before tests were run. Now fixed.


The HTTP auth methods do not work

I just tried this lib and I cannot seem to get the AUTH_HTTP* methods to work. Any ideas what might be wrong?
I keep getting a 401 error and I tried the PASSWORD and the TOKEN method with no success. Has HTTP support been removed? I cannot seem to find any record of it...

In my case AUTH_HTTP_PASSWORD works fine.

@zanmoskotevc make sure the action(s) you're trying to do after authentication are indeed correct and/or allowed in the given auth context.. the authentication method itself only stores your credentials  for the actions taken afterwards (correct my if i'm wrong). So your auth might be correct in terms of credentials, but still a following action might not be allowed, and you'll get a 401..


Disabling a randomly failing test.

What type of PR is this?
Disabling a randomly failing test while it is being debugged and fixed.

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

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.925%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
182

Relevant Lines:
424

💛  - Coveralls

Since this PR disables a flaky test blocking other PRs, you have my approval to merge prior to the completion of the e2e tests.


@tanstack/react-query-devtools v5.0.0 doesn't work out-of-the-box on Next.js

Describe the bug
The server error issue is raised when running yarn dev of Next.js when importing ReactQueryDevtools:
ReferenceError: document is not defined
    at template (file:///Users/my_user/my_project/node_modules/@tanstack/query-devtools/build/esm/index.mjs:809:13)
    at file:///Users/my_user/my_project/node_modules/@tanstack/query-devtools/build/esm/index.mjs:5042:31
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:526:24)
    at async importModuleDynamicallyWrapper (node:internal/vm/module:438:15) {

This is raised because there's no document on the server side. This can be currently worked around by using dynamic import:
import dynamic from 'next/dynamic'

const ReactQueryDevtools = dynamic(
  () => import('@tanstack/react-query-devtools').then(({ReactQueryDevtools}) => ReactQueryDevtools),
  {
    ssr: false,
  },
)

ReactQueryDevtools could be imported in next.js normally and without issue in v4.
Your minimal, reproducible example

Steps to reproduce
in a next.js app:

run yarn add<EMAIL_ADDRESS>add import {ReactQueryDevtools} from '@tanstack/react-query-devtools' to _app.tsx
add <ReactQueryDevtools /> to the render
run yarn dev
open the localhost app
see the error

Expected behavior
no error
How often does this bug happen?
Every time
Screenshots or Videos

Platform
macOS, Chrome. shouldn't matter
Tanstack Query adapter
react-query
TanStack Query version
5.0.0-alpha.26 for query, 5.0.0-alpha.30 for devtools
TypeScript version
5.0.4
Additional context
No response

Hi @ardeora , I've troubleshooted this a bit.
It seems like the solidjs build adds its own internal library logic at the top of the build output, followed by your package's logic which starts at ~line 5000. The specific document reference which is causing an error is one added by solid rather than your code. You can reproduce this in development in the examples/react/nextjs example which uses the local monorepo build output.
Since I don't get this issue in the svelte adapter, this could probably be fixed at the react adapter level. I'm not sure if there's something as easy as esm-env which works with react/nextjs?

I hit that in my live-stream yesterday as well 😅

@ardeora @TkDodo I wonder if this SSR workaround is an unavoidable change that will need to be made for Next.js and other React SSR metaframework users - I can confirm the next/dynamic solution works. The Solid compiler is always going to put server-breaking document and window in, and I don't think there's a built-in React way to disable running on a server ("use client" still hydrates on the server right? The package already uses this anyway)

Thanks @lachlancollins I think there are two options here.

One is that we can use SolidJS.lazy https://www.solidjs.com/docs/latest/api#lazy that will lazily load the framework agnostic devtools on mount. This will put all the document and window related code in a separate entry file that will not run on the server.
Second approach is to implement the we implement the lazy load on the framework adapter level. So just like Svelte Query devtools imports them on the client, we can do the same for React Query devtools. I have a working prototype for it lying around somewhere that I'll try to dig up today/tomorrow

Both approach seems fine I feel the lazy import on the framework agnostic devtools might make it easier to create other framework adapters but I cant think what other side effects it might have. Would love to hear your thoughts on this

Yeah option 1 sounds good 👍

@ardeora I agree, building it into the agnostic adapter sounds better 👍
I did try using React.lazy within the react adapter and that didn't work, but solidjs might do things differently!

This is fixed in #5527 🎉 thanks @ardeora ! I think there are some things that throw errors in Next.js but it doesn't crash the app, I'll close this issue and they can be looked into separately.


can't sync after 4721900

Description
cant't synced after height 4721900, there are error messages in the log.

ERROR CONS [sync-ib]: Attempting to add INVALID block.

PS:  the Fork.properties and genesis.json file have been modified exactly as the Migration guide.
System Information
I'm running:

Which Aion version?: 1.0.674e4b5
Which operating system?: Linux
Which distributor and version?: Ubuntu 18.04
How installed?: via binaries
Are you fully synchronized?: no
Did you try to restart the node?: yes

The issue is due to an incorrect setting of the 1.0 fork. Please ensure that the fork file that was updated is mainnet/config/fork.properties. It must contain the line fork1.0=4721900.
As you start the kernel it should print out <Protocol name: fork1.0 block#: 4721900 if the fork was set correctly. The USED PATHS messages allow you to locate the exact file that is read from disk, in case the fork message is still incorrect or missing.


Expose controls on workgroup size in the public API

Currently halfway implemented, but making some assumptions that might be invalid in some use-cases, so it should at least be overrideable.

This was done a while ago and I forgot to close this issue.


Restore the assist icons when a builder is selcted

When the mod is active and you select a Builder, you don't see the icons there to assist you in selecting what you should build.  For instance you'd see a farm icon, a mine icon, a Seaside resort icon, etc.  Those are gone with the mod active.

In the future, I suggest using the issue search. You would have seen that this is documented in ticket #134. Just to reassure you: there is currently work being done on this in PR #412


Got an error when i published on ubuntu

Os:  Ubuntu 20.04 X64
nginx version: nginx/1.18.0 (Ubuntu)
exceptionless-api: label v709
I use nginx to proxy https://exceptionless-api.domain to http://localhost:4901 which is run by dotnet Exceptionless.Web.dll.
dotnet version:
.NET SDK (reflecting any global.json):
 Version:   5.0.102
 Commit:    71365b4d42

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  20.04
 OS Platform: Linux
 RID:         ubuntu.20.04-x64
 Base Path:   /snap/dotnet-sdk/107/sdk/5.0.102/

Host (useful for support):
  Version: 5.0.2
  Commit:  cb5f173b96

.NET SDKs installed:
  5.0.102 [/snap/dotnet-sdk/107/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 5.0.2 [/snap/dotnet-sdk/107/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 5.0.2 [/snap/dotnet-sdk/107/shared/Microsoft.NETCore.App]

To install additional .NET runtimes or SDKs:
  https://aka.ms/dotnet-download

error messgae:
System.ApplicationException: Error creating the index prod-events-v1-2021.02.03: Original: (400 - ElasticsearchClientException) Request failed to execute. Call: Status code 400 from: PUT /prod-events-v1-2021.02.03. ServerError: Type: mapper_parsing_exception Reason: "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters:  [_size : {enabled=true}]" CausedBy: "Type: mapper_parsing_exception Reason: "Root mapping definition has unsupported parameters:  [_size : {enabled=true}]""
Server: (400) Type: mapper_parsing_exception Reason: "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters:  [_size : {enabled=true}]" CausedBy: "Type: mapper_parsing_exception Reason: "Root mapping definition has unsupported parameters:  [_size : {enabled=true}]""

 ---> Elasticsearch.Net.ElasticsearchClientException: Request failed to execute. Call: Status code 400 from: PUT /prod-events-v1-2021.02.03. ServerError: Type: mapper_parsing_exception Reason: "Failed to parse mapping [_doc]: Root mapping definition has unsupported parameters:  [_size : {enabled=true}]" CausedBy: "Type: mapper_parsing_exception Reason: "Root mapping definition has unsupported parameters:  [_size : {enabled=true}]""
   --- End of inner exception stack trace ---
   at Foundatio.Repositories.Elasticsearch.Configuration.Index.CreateIndexAsync(String name, Func`2 descriptor)
   at Foundatio.Repositories.Elasticsearch.Configuration.DailyIndex.EnsureDateIndexAsync(DateTime utcDate)
   at Foundatio.Repositories.Elasticsearch.ElasticRepositoryBase`1.IndexDocumentsAsync(IReadOnlyCollection`1 documents, Boolean isCreateOperation, ICommandOptions options)
   at Foundatio.Repositories.Elasticsearch.ElasticRepositoryBase`1.AddAsync(IEnumerable`1 documents, ICommandOptions options)
   at Exceptionless.Core.Pipeline.SaveEventAction.ProcessBatchAsync(ICollection`1 contexts) in C:\workspaces\Exceptionless\src\Exceptionless.Core\Pipeline\040_SaveEventAction.cs:line 32

event content:
[{"Id":"601a4d215025ca0b1e332743","OrganizationId":"601a3f68795b7a0dca0c8a0a","ProjectId":"601a3f68795b7a0dca0c8a0b","StackId":"601a4814895c5f0957dafc06","IsFirstOccurrence":false,"CreatedUtc":"2021-02-03T07:13:47.9388466Z","Idx":{"session-r":"601a4d215025ca0b1e332676"},"Type":"log","Source":"Microsoft.AspNetCore.Authorization.DefaultAuthorizationService","Date":"2021-02-03T15:13:37.961694+08:00","Tags":["Info"],"Message":"Authorization was successful.","Geo":null,"Value":null,"Count":null,"Data":{"@level":{"name":"Info","ordinal":2},"@version":"10.0.0","@environment":{"ProcessorCount":16,"TotalPhysicalMemory":0,"AvailablePhysicalMemory":0,"CommandLine":"*","ProcessName":"*","ProcessId":"28648","ProcessMemorySize":753233920,"ThreadName":null,"ThreadId":"25","Architecture":"X64","OSName":"Microsoft Windows 10","OSVersion":"10.0.18363","IpAddress":"<IP_ADDRESS>","MachineName":"*","InstallId":"34a0e55d380e4fb7b6576aa1fa62ad9e","RuntimeVersion":"5.0","Data":{"FrameworkDescription":".NET 5.0.2","ProcessArchitecture":"X64","ApplicationBasePath":"*","ApplicationName":"*","RuntimeFramework":".NETCoreApp,Version=v5.0"},"@user":{"Identity":"admin","Name":null,"Data":{}},"@request":{"UserAgent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4385.0 Safari/537.36","HttpMethod":"GET","IsSecure":true,"Host":"localhost","Port":44302,"Path":"*","Referrer":"*","ClientIpAddress":"::1","Cookies":{"mongoMachineId":"7017974",".AspNetCore.Antiforgery.5VAU0jLELQ8":"CfDJ8KdZfGDaIP9JllR6Qhh2jFINlDc7ZPR0iLAaYpWzbfAPUrBeX6m0-hje_5NXBvQNDZ4VZjtgnb_k30rTGQeYJ5IZAoN-Wt0rF9rjDPD0BWAntB_IBhZ5YoC6k1ABxYIlgLawnRv8Me3fdkwWotH5_o8","idsrv.session":"1CD555F03F537123222A9CE9BDE33793","XSRF-TOKEN":"CfDJ8KdZfGDaIP9JllR6Qhh2jFJUcfAm9kj_aoaflbd3VTW1xCc2LSAQfa5WK7kuuWa-oZYKdFbjdvnUULvj-Bh7CeCBTQvBNdmJ0GSyAdNozxQI3rAo-0hPpySWbLk7PQ4yK-Ink62lJFphTx7OU4mRjBR9ivg5YJUWVUUc0wNzNUdxnUpJl5Kji9AI43z-uBRiQA",".AspNetCore.Identity.Application":"Value is too large to be included."},"PostData":null,"QueryString":{},"Data":{"@browser":"Chrome","@browser_version":"89.0.4385","@browser_major_version":"89","@os":"Windows","@os_version":"10","@os_major_version":"10","@is_bot":false}},"@submission_client":{"IpAddress":"<IP_ADDRESS>","UserAgent":"exceptionless","Version":"<IP_ADDRESS>"},"@ref:session":"601a4d215025ca0b1e332676"},"ReferenceId":"601a4d215025ca0b1e33269a"}}]

df -h
Filesystem      Size  Used Avail Use% Mounted on udev            1.9G     0  1.9G   0% /dev tmpfs           394M  1.1M  393M   1% /run /dev/vda1        40G  8.4G   29G  23% / tmpfs           2.0G   12K  2.0G   1% /dev/shm tmpfs           5.0M  4.0K  5.0M   1% /run/lock tmpfs           2.0G     0  2.0G   0% /sys/fs/cgroup /dev/loop0       50M   50M     0 100% /snap/certbot/889 /dev/loop1       50M   50M     0 100% /snap/certbot/952 /dev/loop2       98M   98M     0 100% /snap/core/10583 /dev/loop3       56M   56M     0 100% /snap/core18/1944 /dev/loop5      129M  129M     0 100% /snap/dotnet-sdk/107 /dev/loop4       62M   62M     0 100% /snap/core20/904 tmpfs           394M     0  394M   0% /run/user/0

appsettings.yml
`
Serilog:
Using:

Serilog.Sinks.Console
MinimumLevel:
Default: Information
Override:
Microsoft: Warning
Microsoft.Hosting.Lifetime: Information
Microsoft.AspNetCore.Hosting.Diagnostics: Warning
System: Warning
Exceptionless.Web.Security.ApiKeyAuthenticationHandler: Warning
Foundatio.Utility.ScheduledTimer: Warning
Foundatio.Metrics: Warning
#Exceptionless.Core.Repositories.EventRepository: Verbose
#Exceptionless.Core.Repositories.StackRepository: Verbose
#Exceptionless.Core.Repositories: Verbose
WriteTo:
Name: Console
Enrich:
FromLogContext
WithMachineName
WithThreadId

Storage: 'provider=folder;path=../storage'
'false' should config a redis
RunJobsInProcess: true
Controls whether users can signup.
EnableAccountCreation: false
AuthOptions:
EnableAccountCreation: false
Kestrel:
Endpoints:
Http:
Url: "http://localhost:4901"
`

Hello,
Thanks for reaching out to us. This is a duplicate of https://github.com/exceptionless/Exceptionless/issues/681. You need to ensure the mapper-size plugin is enabled or disable it via configuration as shown in #681


Correctly determine the zone for CNAME domains pointing to another zone

Fix for https://github.com/xenolf/lego/issues/248

Thank you for the fix! ;)


Format of item data in list

Hey, can I display only value without an id of an item? If I have [{id: 1, name: 'name'}], and I need only to display name without (id), what should I do? Thank you.

there is list-formatter as yo see in README.md
list-formatter, function variable name, custom list formatting function.e.g. 'myListFormatter', not 'myListFormatter()'

Oh, ok. Thank you.


Add serialization library, add JSON serializer

so i might hit merge now and just rename the files later so it isn't help up while i make up my mind on naming

so i might hit merge now and just rename the files later so it isn't help up while i make up my mind on naming

I wouldn't mind moving it rn, I could even start a new standard lib on my own (that would be designed around using opend.exe)

Moved to a separate repository


Fix a typo in Util class

Lucky find, huh?

@Nickersoft You might want to check this PR. The typo is making your entire Util.isNull function useless.
CC @theLufenk

Well is my PR really not fixing a major flaw? How is something not breaking with that error in isNull function.


[SPARK-48035][SQL][FOLLOWUP] Fix try_add/try_multiply being semantic equal to add/multiply

What changes were proposed in this pull request?

This is a follow-up to the previous PR: https://github.com/apache/spark/pull/46307.
With the new changes we do the evalMode check in the collectOperands function instead of introducing a new function.

Why are the changes needed?

Better code quality and readability.

Does this PR introduce any user-facing change?
No
How was this patch tested?

Existing unit tests.

Was this patch authored or co-authored using generative AI tooling?

No

cc: @cloud-fan

Merged to master for Apache Spark 4.0.0-preview.


should exit != 0 when it finds something

otherwise it's hard to add to a pipeline

Hey @dcu, thanks for the issue. I completely agree (a lot of my other newer linters now include an exit_status flag. In the interim, I'd recommend you use golangci-lint as a wrapper to nakedret. For example: golangci-lint run --issues-exit-code --disable-all --enable=nakedret`

we don't use any metalinters but I was able to find a workaround using bash


[S2GRAPH-34] Provide option to select which field in edge's properties to run timeDecay function.

provide options on query to specify property for timeDecay calculations.

+1

+1

+1


Add Super-Linter Github Actions

Need to fix
some error can be ignore (via add .github/linters/....)

Can you explain what this is for please? There is no context here. Thanks

Hi @LifeOfBrianOC
it is for linter code markdown (lint), powershell (PSSA), json (lint)...
You need to enable GitHub Action, you can look a example of output here ->

Hi,
Do you have look ?


Vanilla JS version?

I am looking for lighter alternatives for isotope.js and found this little thing. Now wondering if you plan on a plain Javascript version anytime soon.
I am also interested in teaming up and developing such a version.

hello @thednp unfortunately there are no such plans for the foreseeable future, perhaps down the road but Filterizr was developed to be a jQuery plugin

I know. However, the code is lightweight, very suitable for high performance apps. Also it's size makes it easy to do the transition. I will probably fork this later and will let you know about it.


Sanket slc history

Description
This is a draft PR to replace #709 which addresses some of the main issues with the original PR:

There are three major blocking issues with this PR:

Not properly based on the poc-slc branch

This PR is a proper extension of the poc-slc branch. The code was not rebased but instead is in a single new commit here:

deletes the whole cicero-transform package, instead importing a fixed version (why?!)

This PR properly depends on the cicero-transform package which is still present instead of deleted

tests are not passing (not sure why they aren't triggered on this PR). Below is a log

Two different issues with testing were fixed (with minimal knowledge of the intent):

some tests fails when the contract archive does not have history. this has been fixed by making history optional in the following commit:
Cicero-server tests fail due to a missing directory. This has been fixed by adding that directory back in the following commit:

As discussed during the last Tech WG call, I'm looking into recreating this PR properly.

Changes

Changes from #709 for storing contract state in .slc archives
Fixes issues with archives with no history
Fixes testing issues with cicero-server changes needing a missing directory
Fixes dependency issues with @accordproject/cicero-transform

Flags

Could not do a proper rebase due to a dirty git history and the large number of changes, this version loses authorship and individual commits from @sanketshevkar
Because of the testing issues and "hard reset" of the code, I have a somewhat lower confidence that this is a proper reflection of the original code and intent from its author. I will leave this leave this as a draft PR until I can get a review from @sanketshevkar and @martinhalford and confirmation that this is right

Coverage decreased (-0.4%) to 96.905% when pulling b21ce11baccb77c61a9507266ae7b6a565089892 on sanket-slc-history into 719594c11be69db165fbdb6a95bc917d991da49c on master.


⚠ Bofrost.at has degraded performance

In f43e4dd, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1925 ms

Resolved: Bofrost.at performance has improved in 959d0eb.


THREEDS_MISSING_VERIFY_CARD_OPTION

General information

SDK version: 3.83

Issue description
I get an error on 3D Secure Verify Card
code: "THREEDS_MISSING_VERIFY_CARD_OPTION"
details: undefined
message: "verifyCard options must include an onLookupComplete function."
name: "BraintreeError"
type: "MERCHANT"
Yet in the docs, onLookupComplete ->
Can you please advice, it doesn't seem I can use this with an await...

See https://braintree.github.io/braintree-web/current/ThreeDSecure.html#verifyCard for examples for how to structure your verifyCard call. You must either use the event listener:
// set up listener after initialization
threeDSecureInstance.on('lookup-complete', function (data, next) {
  // use `data` here, then call `next()`
  next();
});

Or pass it directly to verifyCard:
// call verifyCard after tokenizing a card
threeDSecure.verifyCard({
  amount: '123.45',
  nonce: hostedFieldsTokenizationPayload.nonce,
  bin: hostedFieldsTokenizationPayload.details.bin,
  onLookupComplete: function (data, next) {
    // use `data` here, then call `next()`
    next();
  },
  // other options

I expect you are missing that.
If you need further help, reach out to our support team with your integration code: https://developer.paypal.com/braintree/help