dask.order over-prioritizes root tasks in some situations

In test_anom_mean—an example of a basic climatology workload that kicked off long discussion about memory overproduction—it seems that an underlying problem might actually be with how dask.order prioritizes the graph.
Compare how the scheduler traverses the graph with  queuing off and co-assignment off (i.e. scheduler behavior when the issue was first reported, prior to https://github.com/dask/distributed/pull/4967 and https://github.com/dask/distributed/pull/6614), versus with queuing on as normal:

Videos of the graphs executing
Queuing on as normal:
https://user-images.githubusercontent.com/3309802/221064109-4d00faf2-ae90-4016-80c4-378229b12387.mp4
Queuing off and co-assignment off:
https://user-images.githubusercontent.com/3309802/221064132-081ed099-cb05-4017-885a-b2f7948b9afd.mp4

Basically, the graph is prioritized such that the lowest-priority data loading task is still higher priority than nearly all of the data-consuming tasks.
Here's a mini version of the graph, with priorities:

Code to reproduce
import dask.array as da
import numpy as np
import xarray as xr
from dask.utils import parse_bytes

data = da.random.random(
    (26, 1310720),
    chunks=(1, parse_bytes("10MiB") // 8),
)

ngroups = data.shape[0] // 4
arr = xr.DataArray(
    data,
    dims=["time", "x"],
    coords={"day": ("time", np.arange(data.shape[0]) % ngroups)},
)

clim = arr.groupby("day").mean(dim="time")
anom = arr.groupby("day") - clim
anom_mean = anom.mean(dim="time")

anom_mean.data.visualize(
    "anom-mean-order.png", color="order", optimize_graph=True, collapse_outputs=True
)

The last data-loading task is priority 106 (lower-left, second circle up). Looking at the data-reducing tasks, I only count 7 / 26 of them as being < 106. So if we follow graph order exactly, ~75% of the initial data will stay in memory.
So before queueing, workers had both root tasks and reduction tasks assigned. They could have run the reduction tasks—all the dependencies were in memory—they just chose not to, because they were lower priority.
To prove this, here are the tasks & priorities assigned to a worker with queuing off:
https://user-images.githubusercontent.com/3309802/221070444-1e8f7f71-43f8-444e-a21f-7ab3e27a1dfd.mp4

Queuing effectively added a new graph-prioritization mechanism saying "I don't care what your dask.order priority is, if you look like a root task, you always run last". It seems that for test_anom_mean, this re-prioritization of the graph might have been the main thing that solved memory usage, less the scheduler<->worker race conditions that queuing also addressed.
This is the same thing @fjetter said in https://github.com/dask/distributed/pull/7526#issuecomment-1431346387:

this lets me think that a major contributing factor to the success of queuing is in fact that we are breaking priority ordering in a very specific way

The dask.order code is quite complicated, so I don't know how we'd address this there. Maybe the is_rootish heuristic is good enough and it's not worth trying? It'd be nice to understand the underlying cause though. Maybe @eriknw has ideas?

Great writeup @gjoseph92! Here are some quick reactions:
I'm interested in diving deeper to understand. I think this examples deserves a diagnostic treatment as done here: https://github.com/dask/dask/pull/7992#issuecomment-952436239. It would be great to also view these diagnostics plots with the is_rootish / queueing options enabled.

"[...] if you look like a root task, you always run last"

We may be able to add such a rule to dask.order. I think it would be easy for me to add a is_rootish-like check, but we would need to guess a reasonable default value for total_nthreads. I don't know if adding this behavior would be good to do in general, so maybe a config option to control if it's found to sometimes help and sometimes hurt 🤷♂?
I also suspect a different, simpler implementation of dask.order could handle many of the cases that suffer from over-subscribing root-ish tasks (but would be terrible for other graphs). Although I prefer to improve the default dask.order to handle known workflows, the code is quite complicated and challenging to change safely, so I'm warming up to the idea of allowing dask.order to be changeable. Generic task ordering in linear-ish time is hard, and using heuristics will always perform poorly for some graphs.
I have also long-wondered what could be improved with a second pass in dask.order. I suspect it could improve many of the poorly-behaved graphs, but at the cost of doubling the execution time of dask.order. This would be a pretty expensive addition for something that doesn't improve most graphs. OTOH, perhaps a second pass that used e.g. the output of dask.order, the number of workers, and threads per worker, could also help with task co-assignment (https://github.com/dask/distributed/issues/7555).

And if there are a lot of these possibilities in your testing, could enough be fed to a neural network to make some suggestions or think up some possibilities after the requisite work?

Reducing the above example further yields something easier to wield
import dask.array as da
import numpy as np
import xarray as xr
from dask.utils import parse_bytes

data = da.random.random((5, 1), chunks=(1, 1))

arr = xr.DataArray(
    data,
    dims=["time", "x"],
    coords={"day": ("time", np.arange(5) % 2)},
)

clim = arr.groupby("day").mean(dim="time")
anom = arr.groupby("day") - clim
anom_mean = anom.mean(dim="time")

anom_mean.data.visualize(
    "anom-mean-order.png", color="order-age"
)

In this specific example, the ordering works until we reach 16. Instead of computing 32 next which would release two tasks it is jumping right away to the next computation branch at the bottom right. This is forbidden by the distributed scheduler root-ish tasks s.t. the distributed scheduler reduces the computation as desired.
From what I can tell, larger examples show the same anti-pattern such that this is a nice minimal graph one can reason about.
The above example as a low level, raw dsk

{
        ("d", 0, 0): (f, ("a", 0, 0), ("b1", 0, 0)),
        ("d", 1, 0): (f, ("a", 1, 0), ("b1", 1, 0)),
        ("d", 2, 0): (f, ("a", 2, 0), ("b1", 2, 0)),
        ("d", 3, 0): (f, ("a", 3, 0), ("b1", 3, 0)),
        ("d", 4, 0): (f, ("a", 4, 0), ("b1", 4, 0)),
        ("a", 0, 0): (f, f, "random_sample", None, (1, 1), [], {}),
        ("a", 1, 0): (f, f, "random_sample", None, (1, 1), [], {}),
        ("a", 2, 0): (f, f, "random_sample", None, (1, 1), [], {}),
        ("a", 3, 0): (f, f, "random_sample", None, (1, 1), [], {}),
        ("a", 4, 0): (f, f, "random_sample", None, (1, 1), [], {}),
        ("e", 0, 0): (f, ("g1", 0)),
        ("e", 1, 0): (f, ("g3", 0)),
        ("b0", 0, 0): (f, ("a", 0, 0)),
        ("b0", 1, 0): (f, ("a", 2, 0)),
        ("b0", 2, 0): (f, ("a", 4, 0)),
        ("c0", 0, 0): (f, ("b0", 0, 0)),
        ("c0", 1, 0): (f, ("b0", 1, 0)),
        ("c0", 2, 0): (f, ("b0", 2, 0)),
        ("g1", 0): (f, [("c0", 0, 0), ("c0", 1, 0), ("c0", 2, 0)]),
        ("b2", 0, 0): (f, ("a", 1, 0)),
        ("b2", 1, 0): (f, ("a", 3, 0)),
        ("c1", 0, 0): (f, ("b2", 0, 0)),
        ("c1", 1, 0): (f, ("b2", 1, 0)),
        ("g3", 0): (f, [("c1", 0, 0), ("c1", 1, 0)]),
        ("b1", 0, 0): (f, ("e", 0, 0)),
        ("b1", 1, 0): (f, ("e", 1, 0)),
        ("b1", 2, 0): (f, ("e", 0, 0)),
        ("b1", 3, 0): (f, ("e", 1, 0)),
        ("b1", 4, 0): (f, ("e", 0, 0)),
        ("c2", 0, 0): (f, ("d", 0, 0)),
        ("c2", 1, 0): (f, ("d", 1, 0)),
        ("c2", 2, 0): (f, ("d", 2, 0)),
        ("c2", 3, 0): (f, ("d", 3, 0)),
        ("c2", 4, 0): (f, ("d", 4, 0)),
        ("f", 0, 0): (f, [("c2", 0, 0), ("c2", 1, 0), ("c2", 2, 0), ("c2", 3, 0)]),
        ("f", 1, 0): (f, [("c2", 4, 0)]),
        ("g2", 0): (f, [("f", 0, 0), ("f", 1, 0)]),
    }

I'm currently doing a little time travel analysis and it looks like that historic versions didn't have this flaw (I only tested 0.17.2 so far)

After https://github.com/dask/dask/pull/10535, the above example now looks like


RHVoice - Home Assistant - MQTT

Hey!
You've done a great integration!
Is it possible to send the generated 123.mp3 directly to the MQTT broker,
instead of media_player.main?
I have an ESP MQTT player (https://github.com/schmurtzm/MrDiy-Audio-Notifier),
which can play mp3 from anywhere, not only within a local network!
Could you follow the submission rate of MQTT?

=) I know, that's why I turned to you.
Perhaps as part of the RHVoice - HA integration, you can add the submit capability to MQTT? ESP as a player is a very promising thing for notifications.

How you want to use it? Call service, use GUI? May be there is other solution. TTS integrations can't send anything to clients, they just returns output to Home Assistant.

You need another integration that will request audio file and then send it to MQTT. It looks like over engineering. Why you want to use two integrations instead of MQTT Publish service ? It can be called from UI too with mini-media-player card.


X & Y Overflow

There are both x and y overflows on the gril.me homepage

Solution
I would recommend hiding the x and y overflow on the webpage by replacing your body element with this code:
body {
  /* Your normal code */
  margin: 0;
  padding: 0;
  font-family: 'Nunito', sans-serif;
  color: #121212;
  /* Hiding the x and y overflow */
  overflow-x: hidden;
  overflow-y: hidden;
}

I hope that this helps you in some way; I would have opened a PR but I don't know anything about Git version control yet!


Building docker image of camel-spring fails with docker pull issue

I am trying to build a docker image at, and run:
davsclaus:~/workspace/quickstarts/quickstart/java/camel-spring (master)/$ mvn clean install docker:build

Then I get docker pull issue:
[INFO] --- docker-maven-plugin:0.13.5:build (default-cli) @ quickstart-java-camel-spring ---
[INFO] DOCKER> ... Pulling repository docker.io/fabric8/java-jboss-openjdk8-jdk
[ERROR] DOCKER> Error while pulling image: Get https://index.docker.io/v1/repositories/fabric8/java-jboss-openjdk8-jdk/images: dial tcp: lookup index.docker.io: no such host
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 37.709 s
[INFO] Finished at: 2015-10-06T13:41:46+02:00
[INFO] Final Memory: 61M/624M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jolokia:docker-maven-plugin:0.13.5:build (default-cli) on project quickstart-java-camel-spring: Unable to pull 'fabric8/java-jboss-openjdk8-jdk:latest' -> [Help 1]

Ah wonder if its docker hub problem?
davsclaus:~/workspace/quickstarts/quickstart/java/camel-spring (master)/$ docker search fabric8
Error response from daemon: Get https://index.docker.io/v1/search?q=fabric8: dial tcp: lookup index.docker.io: no such host

Wonde if its a DNS issue of my internet provider. Trying to switch to google dns

A vagrant restart and changed to use google dns resolved it, or the fact its been 2-3h later


register BatchMatMul op flops

this commits addresses issue #22071, and add flops calculation for BatchMatMul op. The only change from the MatMul op is that the intermediate k should be from the second to last dim of the a_shape.

Seems auto-merge is not happening but the changes are now committed so we can close this. Thank you for the PR.


[Q] Is WebSocketConnectionPtr thread safe?

In other words, can I share the same WebSocketConnectionPtr with various threads which are going to call send() possibly at the same time?

Yes，It is.

Nice!:-)

In addition, the order of the messages in the socket is exactly the same as the order in which the send() method is called. This means that messages sent in the event loop thread of the connection have no special priority. This is very useful for systems where messages must be strictly ordered.


Spike: How to Implement custom GA4 tracking

Description
Investigate how to develop ticket #172

blocks #172


Anyone else having issue with LinkedIn provider ?

Today our users stopped being able to login with linked in.
Onlything I have right now from our traces at this point.
Response status code does not indicate success: 405 (Method Not Allowed).; TraceSource 'Owin.Security.Providers.LinkedIn.LinkedInAuthenticationMiddleware' event
[Thinktecture.IdentityServer.Core.Endpoints.AuthenticationController]: 4/7/2015 10:02:53 AM +00:00 -- External identity provider returned error: access_denied; TraceSource 'w3wp.exe' event

I inspect the webredirects and things seem to look fine and I suspect that its in the code to token exchange.

I am guessing this is the error: https://github.com/RockstarLabs/OwinOAuthProviders/blob/master/Owin.Security.Providers/LinkedIn/LinkedInAuthenticationHandler.cs#L238
Now, 405 could be from linked in, but i do not know at this point

I'm getting the same issue, only started today and I'm also getting the 405 (Method Not Allowed).
Still haven't figured out if it's LinkedIn or something to do with the code.
I'm looking at the requests in Fiddler now and It seems fine so far.

ye. Was just discussing this with identity server guys. Suggestion was to debug it by hand doign the http calls to see where it goes wrong.  Must be in the code 2 token exchange.
My guess is that linkedin changed something since our codebase has not changed since last week and the issue started this morning

reproduced it now:  heres the response of the token.
https://gist.github.com/s093294/cbc7c8d3a3da0226d2e2

the request headers are also there in a comment now.

Many thanks for bringing this to our attention, @s093294. I will look into this now. Do bare in mind that it was @jerriep who implemented this provider and not me - I have not touched this provider before. If you find a solution before me, please create a pull request. Cheers.

I dont think the provider is bad. I think its on linkedin https://www.linkedin.com/uas/oauth2/accessToken endpoint that is broken.

POST https://www.linkedin.com/uas/oauth2/accessToken HTTP/1.1
Content-Type: application/x-www-form-urlencoded
Host: www.linkedin.com
Cookie: bscookie="v=1&201504071234373bc02b47-9d08-477f-8375-b80b281ef416AQEptFjv8jXPI93YmF-H-3kvnwSLwBF8"; bcookie="v=2&46f6f299-6702-48bf-8634-7ba023bd5099"; lidc="b=LB23:g=218:u=215:i=1428410899:t=1428487523:s=AQH0wYHWtbTVED0CrzWvmbkbG4qIEQ3e"
Content-Length: 267
Expect: 100-continue
Connection: Keep-Alive
grant_type=authorization_code&code=AQTNeGrEj1QeV2MOudoi8T1fx1fov-05oSp5dg-HidNxpHtKJ_CkbfcsNyKvuY3eIztVtHQJb883P8QzB5vVvdjYYpR0T9eAjComHVc55quXCs6_RR8&redirect_uri=http%3A%2F%2Flocalhost%3A1729%2Fsignin-linkedin&client_id=&client_secret=
Just removed the secret/clientid, but above results in method not found.

When did you first notice the problem? I wonder if LinkedIn have made a statement yet.

started this morning. noticed the error first time 5 hours ago.
Everything looks correct according to docs: https://developer.linkedin.com/docs/oauth2
I have seen nothing from linkedin

Created this:
https://stackoverflow.com/questions/29492598/post-https-www-linkedin-com-uas-oauth2-accesstoken-http-1-1-results-in-method
Got reply on twitter: https://twitter.com/LinkedInHelp/status/585429131652894720

+1 confirm that the provider isn't the problem.
I did the oauth2 request manually and still receiving the same error:
"The remote server returned an error: (405) Method Not Allowed."
So either a problem on LinkedIn's end or they changed something and decided not to tell developers again...

Thanks for the investigation guys. Given it seems to be on the LinkedIn side I would suggest giving it a few hours and see whether it works itself out.

I want to test this out but I cannot cannot so much as register an account with LinkedIn at the moment.
It always tells me the verification failed. I had a friend test this in America and it happens for him too.

This could be related to our problem here. It looks like their authentication server is being erratic.

there was an update in an answer that might help.
http://stackoverflow.com/a/29493329/871985
When confirmed (if this is the case) How fast can we fix this and get new nugets out? (Asking to find out if i should start making a local copy of the provider to hot fix it local (when solution exists)) or just wait for new nugets.

If you can propose a fix. I will merge and update the NuGet package almost immediately.

I am not sure. What do you think, @jerriep?
I am inclined to push an updated package as soon as we have a fix.

Sorry guys, it is getting late evening already here by me, but if you get a fix for that by all means please :)

Cool. I am still unable to create a LinkedIn account :angry:. @s093294, if you submit a pull request, I will be very grateful. I promise I will tend to it promptly.

Sure. Right now I dont think the fix is in the provider.  According to the SO answer, if the header is the issue, it is not set by this library sadly :( so not something that can be fixed easily.

In .NET, we were able to work around this by explicitly disabling the Expect: 100-Continue for the LinkedIn API URI.  Something like this:
protected void Application_Start()
{
var servicePoint = System.Net.ServicePointManager.FindServicePoint(new Uri("https://www.linkedin.com/uas/oauth2/accessToken";));
servicePoint.Expect100Continue = false;
}

I'm not proud of this but it's working locally.

Just tested it also and noticed that it actually worked once and then after deploying it didnt work after all. Might be missing something.

What happens when you use @jlcj1974's branch? I just tested it on localhost and it works.

Looks to be working here also.
Should we push out some new nugets based on this to help people using the provider? Would be nice

Awesome :smile:. Can you confirm that it works after deploying too?

Either i need to distribute local dlls to do so or wait for updates nugets. Can we generate prerelease packages?  But I dont see any reason why it would not work in production also with the change made.

I am being mindful of this comment:

Just tested it also and noticed that it actually worked once and then after deploying it didnt work after all. Might be missing something.

I interpreted that as "the solution works locally but not remotely." I will create a prerelease package now.

I can understand that. I might just have been a little to fast in deploying and could have found out locally that it didnt work as expected.
I still think its a good idea to add this as a prerelease until linkedin comes with a statement. This allows us to update and get a fix that work until we know if linkedin reverts anything or do further changes to the endpoint.

I agree. Working on it now.

OK folks. I just published a pre-release with the proposed fix. You can find it here. Please report back.

Deployed to our staging deployment and sofar no issues. Deploying to production now also

I posted the prerelease as a answer also to my SO question: http://stackoverflow.com/questions/29492598/post-https-www-linkedin-com-uas-oauth2-accesstoken-http-1-1-results-in-method/29499394#29499394

Nice one.
I hope @LinkedIn acknowledge this apparent breaking change soon.

Has anyone heard anything from @LinkedIn? (@s093294 @NoelOC @jerriep @jlcj1974)
I am wondering whether I should keep the LinkedIn-Fix in a seperate branch or merge into master and release with 1.17 (opposed to 1.17-pre). It depends if this temporary or not.

Havent heard anything yet.
I would consider the fix stable. But there is always the chance that linkedin changes something again and that could be considered a new fix.
I would keep it as a prerelease for a few days or until @LinkedIn gives a statement, since this will alert users of the lib to pay attention. If you release 1.17 and linkedin fixes/change something that yet again require a new update of the nugets, this change will reflect badly on the lib instead of on linkedin.
Just my 2cent.

I totally agree.
:bear:

Hey guys, thanks for all these fixes.
From past experience, I think waiting for any official response from LinkedIn is futile, as communicating with developers is not their strong point ;)
That being said, I am totally cool with keeping it in pre-release mode. I am busy working my way through some pull requests, so hanging on before releasing it gives me more time to do that.

Hiya everybody,
I have the same issue with LinkedIn, but unfortunately Expect100Continue fix doesn't work for me (at least now). So for now I'm Authorization parameters (like grant_type, code, client_secret etc.) in query part of URI (instead of body of POST request to https://www.linkedin.com/uas/oauth2/accessToken endpoint).
Sad, but it works. Please checkout mine commit https://github.com/CrazyMORF/OwinOAuthProviders/commit/70d0f22d6480817f7fe03eb964357b28a497f41c

The prerelease package we created do still work here. (Just tested it).

Hi All,
I am also continuing to get the same error even after upgrading to pre release package. i.e access_denied. What should I check for?

@nikesh-thinkbridge Have you followed this guide exactly?http://www.oauthforaspnet.com/providers/linkedin/guides/aspnet-mvc5/

Another tip I can propose is to look at the network traffic in Chrome Developer tools. Make sure though that you have "Preserve Log" enabled so the requests does not clear everytime there is a redirect. A lot of time the clue is hidden somewhere inside the network traffic - you just need to go hunting...

yes it was all working till yesterday morning, suddenly stopped working last evening. Then I installed the pre release version as suggested, but I am still getting the same error.

Sure...but the token call would be made by the middleware and not visible in the log right?
just an fyi..i am using an angular app as front end.

It depends on what is wrong and when the error happens. When LinkedIn redirects back to your redirect URL it will happen in the browser, and it can happen that it includes more info inside that redirect URL.
Typically if redirect URLs does not match, scopes are incorrect, or other cases you will be able to see more details.
So don't just dismiss it out of hand. It is just one way to try and track down the problem. If you do not see anything in the network traffic then we can eliminate that and move on to try something else.

Of course if it does happen on the middleware level then you can always try and use Fiddler to monitor network traffic as well.
Seeing as it does work for some people we need to track this down on your end.
I will install it quickly on my side and see whether I get the same issue.

Yeah guys, it works 100% on my side as well. You will need to monitor the network traffic on your side with something like Fiddler to see whether you can get a clue about what may be wrong.
Is there anything "strange" about your cinfigurations? Maybe a non-standard callback URL, or non standard scope or anything like that?

Thanks jerrie...My bad....Had changed the url for testing it on local which is on a different key than the production one. Changed it and all works like charm!!!
Sorry for the goof up...but thanks a lot. You guys saved a lot of heartburn!!!!!!

No problem :) Glad you're sorted

Thanks to you! But what can we expect from our friends at Linked in......more surprises???!!

Most probably ;) These companies aren't always very good with communicating changes to developers... :(

Hey everyone. I release 1.17 by mistake without LinkedIn fix, but realised my mistake and released 1.17.1 with LI fix included.
I tested and all works fine. I will close this issue.
If anything else comes up feel free to reopen or create a new issue

Hi everyone,
We applied the patch yesterday and it worked fine.
But around 7 hours ago, we received back an "access denied" error when we try to have an authentification using Owin.
Is there anyone with same problem ?

I cannot confirm the problem. Our linkedin sign on has worked since the updated package was added.

We deployed yesterday and the patch is still working for us.
On Apr 9, 2015, at 11:36 AM, trotin <notifications<EMAIL_ADDRESS>wrote:
Hi everyone,
We applied the patch yesterday and it worked fine.
But around 7 hours ago, we received back an "access denied" error when we try to have an authentification using Owin.
Is there anyone with same problem ?
—
Reply to this email directly or view it on GitHubhttps://github.com/RockstarLabs/OwinOAuthProviders/issues/87#issuecomment-91285334.

Hi @trotin,
Many thanks for bringing another potential issue to our attention. Once I saw your comment I tested the patched LinkedIn provider on localhost (version 1.17.1) and it still works. Can you please provide more detail? Could be this a human error, as was the case for another user?
I will leave this issue closed for now, as it seems to be working for everyone else.


Send info to slave which is syncing from master will make it crash

Master and slave are both ardb.
when slave is loading backup synced from master, if send a info command to slave, it will crash.
It happen after log: Start loading snapshot:/mnt/ardb/backup/sync-rocksdb-backup.1835145290.58744817534011532.1487750314
If send get a to slave, it will return LOADING Ardb is loading the snapshot file. normally.

any found in gdb stack trace?

#0  0x000000000056cc9e in ardb::RocksDBEngine::Stats (this=0x7fa45b72b900, ctx=..., all="rocksdb_version:5.0.2\r\n") at db/rocksdb/rocksdb_engine.cpp:1313
#1  0x00000000004c154b in ardb::Ardb::FillInfoResponse (this=this@entry=0x7ffca344f830, ctx=..., section="default",
    info="# Server\r\nardb_version:0.9.4\r\nredis_version:2.8.0\r\nengine:rocksdb\r\nardb_home:/home/vagrant/test1\r\nos:Linux 4.4.0-38-generic x86_64\r\ngcc_version:5.4.0\r
\nprocess_id:28756\r\nrun_id:cbd4d830254bed7fe3c16418"...) at command/server.cpp:230
#2  0x00000000004c2f9a in ardb::Ardb::Info (this=0x7ffca344f830, ctx=..., cmd=...) at command/server.cpp:449
#3  0x000000000053b84a in ardb::Ardb::DoCall (this=this@entry=0x7ffca344f830, ctx=..., setting=..., args=...) at db/db.cpp:1395
#4  0x0000000000541017 in ardb::Ardb::Call (this=0x7ffca344f830, ctx=..., args=...) at db/db.cpp:1557
#5  0x00000000004746bd in ardb::RedisRequestHandler::MessageReceived (e=..., ctx=..., this=0x7fa45b73c600) at network.cpp:130
#6  ardb::ChannelUpstreamHandler<ardb::codec::RedisCommandFrame>::HandleStreamEvent (e=..., ctx=..., this=0x7fa45b73c600)
    at ./common/channel/channel_upstream_handler.hpp:133
#7  ardb::ChannelPipeline::SendUpstream<ardb::codec::RedisCommandFrame> (ctx=<optimized out>, e=..., this=<optimized out>) at ./common/channel/all_includes.hpp:89
#8  0x0000000000479420 in ardb::ChannelHandlerContext::SendUpstream<ardb::MessageEvent<ardb::codec::RedisCommandFrame> > (this=0x7fa454087810, this=0x7fa454087810, e=...)
    at ./common/channel/all_includes.hpp:164
#9  ardb::fire_message_received<ardb::codec::RedisCommandFrame> (destructor=0x0, message=0x7fa4451fea00, ctx=...) at ./common/channel/channel_helper.hpp:91
#10 ardb::codec::StackFrameDecoder<ardb::codec::RedisCommandFrame>::CallDecode (this=0x7fa4540a68c0, context=..., channel=0x7fa45b747b80, cumulation=...)
    at ./common/channel/codec/stack_frame_decoder.hpp:102
#11 0x0000000000479f68 in ardb::codec::StackFrameDecoder<ardb::codec::RedisCommandFrame>::MessageReceived (this=0x7fa4540a68c0, ctx=..., e=...)
    at ./common/channel/codec/stack_frame_decoder.hpp:157
#12 0x000000000047c5c3 in ardb::ChannelUpstreamHandler<ardb::Buffer>::HandleStreamEvent (e=..., ctx=..., this=<optimized out>)
    at ./common/channel/channel_upstream_handler.hpp:133
#13 ardb::ChannelPipeline::SendUpstream<ardb::Buffer> (ctx=<optimized out>, e=..., this=0x7fa45b747bb8) at ./common/channel/all_includes.hpp:89
#14 0x000000000047d882 in ardb::ChannelPipeline::SendUpstream<ardb::MessageEvent<ardb::Buffer> > (event=..., this=0x7fa45b747bb8) at ./common/channel/all_includes.hpp:128
#15 ardb::fire_message_received<ardb::Buffer> (destructor=0x0, message=0x7fa45b747be8, channel=0x7fa45b747b80) at ./common/channel/channel_helper.hpp:83
#16 ardb::Channel::OnRead (this=0x7fa45b747b80) at common/channel/channel.cpp:560
#17 0x000000000047c62d in ardb::Channel::IOEventCallback (eventLoop=<optimized out>, fd=<optimized out>, clientData=0x7fa45b747b80, mask=1) at common/channel/channel.cpp:53
#18 0x00000000004bc377 in aeProcessEvents (eventLoop=eventLoop@entry=0x7fa45b6dd0c8, flags=flags@entry=3) at common/channel/redis/ae.c:429
#19 0x00000000004bc7cb in aeMain (eventLoop=0x7fa45b6dd0c8) at common/channel/redis/ae.c:485
#20 0x00000000004aa3f0 in ardb::Thread::ThreadFunc (data=0x7fa45b728b20) at common/thread/thread.cpp:38
#21 0x00007fa45ce316ba in start_thread (arg=0x7fa4451ff700) at pthread_create.c:333
#22 0x00007fa45bc9482d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Not much.
A easy way to reproduce the problem.
Two empty ardb. A(port 16379) and B (port 16380)
set some data on A (set a 1, set b 2....)
loop check  on B :  while [ 1 ] ; do redis-cli -p 16380 info ;done
Make B slave of A: redis-cli -p 16379 slaveof <IP_ADDRESS> 16379
After a while, B will crash

Awesome! fixed now


Version 0.2.0

Landed in https://github.com/metarhia/metavm/commit/c0a5da198ab27587704709fe6ff26f88da6c9cae


Add port for imgui library

This port adds imgui. It's a small library for creating user interfaces for applications rendered in immediate mode.
The only compile time dependency is STB and there are no runtime dependencies.
There is one thing in this PR which I'm not sure about, whether it could be handled in a better manner. imgui offers the possiblity to provide an imconfig.h. If non is present, the build will break, so the empty example config is copied to the include directory. However patching the imgui.h doesn't seem to be a satisfying solution.
And does forcing the library being a statically linked library with add_library(imgui STATIC have any side effects?

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

Thanks for the PR!

There is one thing in this PR which I'm not sure about, whether it could be handled in a better manner. imgui offers the possiblity to provide an imconfig.h. If non is present, the build will break, so the empty example config is copied to the include directory. However patching the imgui.h doesn't seem to be a satisfying solution.

I think both are acceptable solutions; we do regularly patch installed headers to handle things such as dllexport macros so it's not unusual.

And does forcing the library being a statically linked library with add_library(imgui STATIC have any side effects?

No side effects other than ensuring it's built statically, however while merging I moved that out into the portfile.
While merging, I made a few tweaks:

Using the newer vcpkg_from_github() call enables vcpkg install imgui --head to grab the latest bleeding edge
(Not harmful, just a touch-up) throwing the public imgui.h files into target_include_directories() doesn't actually do anything, so I've removed them as superfluous.

Thank you!


I want to add my Project @swapnilsparsh

I want to add my Portfolio Project @swapnilsparsh

@aryangupta008 Please describe your project.


Bug trying to render styles during local development, works fine on production.

Environment
System:

OS: macOS 10.15.4
CPU: (4) x64 Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz
Memory: 47.85 MB / 8.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:

Node: 12.14.1 - ~/.asdf/installs/nodejs/12.14.1/bin/node
npm: 6.13.4 - ~/.asdf/installs/nodejs/12.14.1/bin/npm

npmPackages:

styled-components: ^5.0.1 => 5.0.1

Reproduction
Unable to reproduce the issue.
An example of how what our code looks like can be found inside the code sandbox.
https://codesandbox.io/s/sweet-curie-n91fp?file=/src/App.js
Steps to reproduce
See above
Expected Behavior
The (styled) component to render the styles in both production and local.
Actual Behavior
Component renders with proper styling, only in production.
Returns small piece of code instead of those styles, during development.
Screenshots

Having the same problem. Similar environment, running OSX 10.15 with styled-components: 5.1.0.
Styles are not rendered for random components.
If I put in a dummy component directly above the misbehaving component the issue resolves. Example below. The first instance does not render styles correctly, whereas the second instance does:
<Link to="/">
   <Logo src={logo} />
 </Link>

<div style={{ display: "none" }} />
<Link to="/">
   <Logo src={logo} alt="Tempo" />
 </Link>

Full component:
import React from "react";
import Col from "react-bootstrap/col";
import Row from "react-bootstrap/row";
import { Link } from "react-router-dom";
import styled from "styled-components";

import logo from "assets/img/logo.svg";

const StyledHeader = styled.section`
  padding: 15px 0;

  @media only screen and (min-width: 768px) {
    padding: 30px 0;
  }
`;

const NavLinks = styled.div`
  text-align: right;

  & > a {
    margin: 0 20px;
  }
`;

const Logo = styled.img`
  max-width: 100px;
  margin-left: 15px;

  @include only screen and (min-width: 768px) {
    max-width: 200px;
  }
`;

export const Header = () => {
  return (
    <StyledHeader>
      <Row>
        <Col md={{ span: 3 }}>
          <Link to="/">
            <Logo src={logo} alt="" />
          </Link>
        </Col>
        <Col md={{ span: 6, offset: 3 }}>
          <NavLinks>
            <Link to="#about">About</Link>
            <Link to="#get-started">Get Started</Link>
          </NavLinks>
        </Col>
      </Row>
    </StyledHeader>
  );
};

Same problem here but Styled components 5.1.0. It can be reproduced here:
https://codesandbox.io/s/crazy-mountain-4t73k?file=/src/App.js

I'm really struggling to understand what the issue that's being described here is, since the description is a little vague and the reproductions aren't available anymore. Sorry! But I'm closing this due to inactivity. That said, I haven't really seen anything similar in any other issues so far.


Skyconnect gives error setting up after update to HA 2023.1.6

After updating, setup error arised. deleted skyconnect integration, tried to reinstall other error showed up
First error:
2023-01-20 13:09:20.053 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry SkyConnect v1.0 for zha
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/__init__.py", line 111, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 189, in async_initialize
raise exc
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 169, in new
await app.startup(auto_form=auto_form)
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 104, in initialize
await ezsp._startup_reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 95, in _startup_reset
await self.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/__init__.py", line 124, in reset
await self._gw.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 251, in reset
return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

after restart of HA, skyconnect found, but could not complete installation.
Error:
Kon het USB apparaat niet onderzoeken
Could not investigate the usb device
Could not find a specific log entry for this generated error.

Is this still an issue for you? Did you maybe migrate to the Multi-PAN firmware?

Hi!
Still an issue. Installed latest ha core stable 2023.1.07. Could not find the stick again when rebooting. Will upload latest logs in a moment.

Logger: homeassistant.config_entries
Source: components/zha/core/gateway.py:174
First occurred: 14:49:13 (1 occurrences)
Last logged: 14:49:13
Error setting up entry SkyConnect v1.0 for zha
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/init.py", line 111, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 189, in async_initialize
raise exc
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 169, in new
await app.startup(auto_form=auto_form)
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 104, in initialize
await ezsp._startup_reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 95, in _startup_reset
await self.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 124, in reset
await self._gw.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 258, in reset
return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

Additionally:
Logger: zigpy_deconz.api
Source: components/zha/radio_manager.py:171
First occurred: 10:02:13 (1 occurrences)
Last logged: 10:02:13
No response to 'Command.read_parameter' command with seq id '0x02'

Seems to happen everytime I update the core, I have to remove the integration, physically disconnect the stick and when I reconnect it, then HA can configure it correctly again.

HA OS can find the usb stick, however the integration keeps failing.
DEVLINKS: >-
/dev/serial/by-id/usb-Nabu_Casa_SkyConnect_v1.0_6e8a6e57ac14ed11a036bc8be054580b-if00-port0
/dev/serial/by-path/pci-0000:01:1b.0-usb-0:1:1.0-port0
DEVNAME: /dev/ttyUSB0
DEVPATH: >-
/devices/pci0000:00/0000:00:1e.0/0000:01:1b.0/usb2/2-1/2-1:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS: usb
ID_MODEL: SkyConnect_v1.0
ID_MODEL_ENC: SkyConnect\x20v1.0
ID_MODEL_ID: ea60
ID_PATH: pci-0000:01:1b.0-usb-0:1:1.0
ID_PATH_TAG: pci-0000_01_1b_0-usb-0_1_1_0
ID_REVISION: '0100'
ID_SERIAL: Nabu_Casa_SkyConnect_v1.0_6e8a6e57ac14ed11a036bc8be054580b
ID_SERIAL_SHORT: 6e8a6e57ac14ed11a036bc8be054580b
ID_TYPE: generic
ID_USB_DRIVER: cp210x
ID_USB_INTERFACES: ':ff0000:'
ID_USB_INTERFACE_NUM: '00'
ID_VENDOR: Nabu_Casa
ID_VENDOR_ENC: Nabu\x20Casa
ID_VENDOR_ID: 10c4
MAJOR: '188'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '1796005'

Same problem here with 2023.2.1
With Conbee2 and Deconz it was very stable, now with ZHA and Skyconnect it's quite unstable.
Error setting up entry SkyConnect v1.0, s/n: 32fc8748fe8cec11b39d6ce883c5466d - Nabu Casa for zha
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 382, in async_setup
result = await component.async_setup_entry(hass, self)
File "/usr/src/homeassistant/homeassistant/components/zha/init.py", line 111, in async_setup_entry
await zha_gateway.async_initialize()
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 189, in async_initialize
raise exc
File "/usr/src/homeassistant/homeassistant/components/zha/core/gateway.py", line 174, in async_initialize
self.application_controller = await app_controller_cls.new(
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 169, in new
await app.startup(auto_form=auto_form)
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 105, in initialize
await ezsp.version()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 128, in version
ver, stack_type, stack_version = await self._command(
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

Still the same issue, every time there is a reboot of home assistant core, the integration gets broken with a start up error. I’m still on zigbee firmware. Is it useful to switch to multi pan to see if it behaves differently?
Logger: zigpy.application
Source: /usr/local/lib/python3.10/site-packages/zigpy/application.py:148
First occurred: 10:41:16 (3 occurrences)
Last logged: 10:41:32
Couldn't start application
Traceback (most recent call last):
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 456, in wait_for
return fut.result()
asyncio.exceptions.CancelledError
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/zigpy/application.py", line 145, in startup
await self.connect()
File "/usr/local/lib/python3.10/site-packages/bellows/zigbee/application.py", line 124, in connect
self._ezsp = await bellows.ezsp.EZSP.initialize(self.config)
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 104, in initialize
await ezsp._startup_reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 95, in _startup_reset
await self.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/ezsp/init.py", line 124, in reset
await self._gw.reset()
File "/usr/local/lib/python3.10/site-packages/bellows/uart.py", line 258, in reset
return await asyncio.wait_for(self._reset_future, timeout=RESET_TIMEOUT)
File "/usr/local/lib/python3.10/asyncio/tasks.py", line 458, in wait_for
raise exceptions.TimeoutError() from exc
asyncio.exceptions.TimeoutError

@AOskam are you running ZHA (Zigbee Home Assistant) and deCONZ (the add-on) at the same time? You can't do that, only deCONZ or ZHA can control a single SkyConnect radio.

I completely removed that integration and addon, now it's working fine.

Make sure to use the SkyConnect only from one integration, and that no add-on is using the same radio. If the issue still persists, please open an issue in the Core repo along exact information of your setup (type of installation etc.): https://github.com/home-assistant/core


In english

Hi,
I creating grafana plugin based on mxgraph.
I try to integrate an editor, i found you project but i cant understand chinese.
How to put it in english ?
Best regards,
Arnaud

Hi,
I have supported english in newest commit.
Thanks for suggestion.
If have any other question, please issue it, I will respond as soon as possible.
Best regards,
Korbin

Thx Korbin
I ll try it

its work
Nice work !
Congratulation


Remove "node" types for test-runtime-utils and node-host packages

These were added explicitly in #3329.  They were previously inherited from runtime-utils, but runtime-utils was cleaned of its node types and these downstream packages still require them.

node-host is an example with nothing depending on it, and test-runtime-utils is only used as a devDependency or in terminal examples, so i don't think this needs to be fixed


Can't install with Composer

When I try to install from Packagist I get the following message:
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install phpdocumentor/phpdocumentor v2.8.5
    - Conclusion: don't install phpdocumentor/phpdocumentor v2.8.4
    - Conclusion: don't install phpdocumentor/phpdocumentor v2.8.3
    - Conclusion: don't install phpdocumentor/phpdocumentor v2.8.2
    - Conclusion: don't install phpdocumentor/phpdocumentor v2.8.1
    - Conclusion: remove pimple/pimple v3.0.2
    - Installation request for phpdocumentor/phpdocumentor ^2.8 -> satisfiable by phpdocumentor/phpdocumentor[v2.8.0, v2.8.1, v2.8.2, v2.8.3, v2.8.4, v2.8.5].
    - Conclusion: don't install pimple/pimple v3.0.2
    - phpdocumentor/phpdocumentor v2.8.0 requires cilex/cilex ~1.0 -> satisfiable by cilex/cilex[1.0.0, 1.0.1, 1.1.0].
    - cilex/cilex 1.0.0 requires pimple/pimple 1.0.* -> satisfiable by pimple/pimple[1.0.0, v1.0.1, v1.0.2].
    - cilex/cilex 1.0.1 requires pimple/pimple 1.0.* -> satisfiable by pimple/pimple[1.0.0, v1.0.1, v1.0.2].
    - cilex/cilex 1.1.0 requires pimple/pimple ~1.0 -> satisfiable by pimple/pimple[1.0.0, v1.0.1, v1.0.2, v1.1.0, v1.1.1].
    - Can only install one of: pimple/pimple[1.0.0, v3.0.2].
    - Can only install one of: pimple/pimple[v1.0.1, v3.0.2].
    - Can only install one of: pimple/pimple[v1.0.2, v3.0.2].
    - Can only install one of: pimple/pimple[v1.1.0, v3.0.2].
    - Can only install one of: pimple/pimple[v1.1.1, v3.0.2].
    - Installation request for pimple/pimple == <IP_ADDRESS> -> satisfiable by pimple/pimple[v3.0.2].

It would seem that you have a dependency on Pimple 3 in your own project; since phpDocumentor 2 uses Pimple 2 that conflicts. I would suggest to consume phpDocumentor using the PHAR as that will allow you to circumvent such conflicting dependencies

Yes, I use Slim as my miniframework. Is it in the works to change to Pimple 3 in a later version, or …? (Either way, I’ll go with other ways of the dependency)

16 feb. 2016 kl. 11:55 skrev Mike van Riel<EMAIL_ADDRESS>It would seem that you have a dependency on Pimple 3 in your own project; since phpDocumentor 2 uses Pimple 2 that conflicts. I would suggest to consume phpDocumentor using the PHAR as that will allow you to circumvent such conflicting dependencies
—
Reply to this email directly or view it on GitHub https://github.com/phpDocumentor/phpDocumentor2/issues/1738#issuecomment-184627023.

phpDocumentor 3 will no longer use Cilex and Pimple; there we will start using PHP-DI 5 with no framework. So there may be other dependency conflicts but not with Pimple 3.
With phpDocumentor 3 we are also going to make the PHAR installation the preferred route and tell people that installing with composer is a bit of 'at your own risk' as an installation using Composer has various caveats and runs the risk of conflicts; as a project we would prefer to focus on fixing issues in the other installation channels and adding new features and hope that the community will pick up on the composer caveats if they really want to install phpDocumentor using Composer.

Alright, thank you.
You can close this.

16 feb. 2016 kl. 11:55 skrev Mike van Riel<EMAIL_ADDRESS>It would seem that you have a dependency on Pimple 3 in your own project; since phpDocumentor 2 uses Pimple 2 that conflicts. I would suggest to consume phpDocumentor using the PHAR as that will allow you to circumvent such conflicting dependencies
—
Reply to this email directly or view it on GitHub https://github.com/phpDocumentor/phpDocumentor2/issues/1738#issuecomment-184627023.


[V6] In contrast to the docs, values object not passed to form props

a reduxForm wrapped component isn't passed the current values object.
Looked at the code, it seems to  be removed from the passable props:
https://github.com/erikras/redux-form/blob/v6.0.0-alpha.15/src/reduxForm.js#L274

You're correct, the documentation is not up to date.
I'll be happy to review any PR fixing this!

sounds good! Will submit a PR over the weekend.

What's the problem here? The current values are not passed. Does it say in the docs somewhere that they are?

@erikras in the docs under instance api, there's a values property that needs to be removed since this has gotten replaced by formValueSelector.
http://redux-form.com/6.0.0-rc.1/docs/api/ReduxForm.md/

I think you're confusing props with instance variables/methods. The docs are correct. What they mean is that you can something like:
render() {
  return (
    <div>
      <MyDecoratedForm ref="theForm"/>
      <button
        type="button"
        onClick={() => console.log(this.refs.theForm.values)}>
        Log Values
      </button>
    </div>
  )
}

ah! my bad. "on an instance" vs "in an instance". subtle one. I'll go ahead and close. :)


fix: allow false values to keepLambdaLogs

Thanks for the plugin!
keepLambdaLogs would only accept true values, this should fix it!

Thanks! As soon as you cut a release I'll implement this in my project :)

Thanks! As soon as you cut a release I'll implement this in my project :)

We published 1.0.1, @perrin4869, check it out and let me know if you find anything else. Thanks again!

@jduncan-xoi thanks!
I did have further problems using this plugin.The reason is that I need to keep the logs based on the environment, so do something like keepLambdaLogs: ${param:keepLambdaLogs}, but this plugin checks the param in the plugin contstructor, before it is evaluated - this is referred to in the docs:
Note: configuration values are only resolved after plugins are initialized. Do not try to read configuration in the plugin constructor, as variables aren't resolved yet. Read configuration in lifecycle events only.

I could fix this, but then the tests would break... And would require a rather extensive test rewrite, maybe similar to https://github.com/theBenForce/serverless-rollup-plugin/blob/master/test/index.ts


[Config] Add buildImportDom.js

buildImportDom.js is made of functions that will be used to make DOM related to one-import
ONE-vscode-DCO-1.0-Signed-off-by: TaeKyuRyu<EMAIL_ADDRESS>

from issue #58
from draft #117


Wait commit through pachctl not printing and / or returning commits.

Wait commit through pachctl does not appear to return commits with the <repo>@<commit-id> or <commitset-id> format. The commitset appears to be setup properly after digging into the state, but the commits are not appearing in the output of pachctl.

playing with it now, I cannot reproduce the buggy behavior. Was this fixed in the last week? @brycemcanally @nitinjainsj

the output now seems to behave as expected. Closing this issue


Refactor wrappers to subclass gym.Wrapper

This makes the purpose clearer and reduces code duplication (plus it makes type checking a lot easier).

Hi @Danmou, I appreciate the effort. However, I consider inheritance harmful where it is not necessary, so I actually prefer the proxy pattern that is currently used. Thanks again!


disabled process clean (#370)

Overview
This PR is a workaround for issue #370.
It disables the process.clean() call to avoid removing the workdir before the process job has started.
It is probably not a solution to #370 and there is more work do be done for process cleaning.
Related Issue / Discussion
See #370 and #358.
Additional Information
Contribution Agreement
(as per https://github.com/geopython/pywps/blob/master/CONTRIBUTING.rst#contributions-and-licensing)

[x ] I'd like to contribute [feature X|bugfix Y|docs|something else] to PyWPS. I confirm that my contributions to PyWPS will be compatible with the PyWPS license guidelines at the time of contribution.
[x ] I have already previously agreed to the PyWPS Contributions and Licensing Guidelines

Coverage decreased (-0.9%) to 71.905% when pulling 30982f38eca5016fb3472bef6153ac01158758a6 on bird-house:issue-370-disable-process-clean into b66ac7e8bf062740cd7edd62d070fcddedb055d1 on geopython:master.

@gschwind I pull this workaround into master to have a working pywps. Please complain or provide a new PR if you don't like this.


Updating extensionGallery.json for ML 0.10.0

VSIX from the release build: https://mssqltools.visualstudio.com/_apis/resources/Containers/3115191/drop?itemPath=drop%2Fextensions%2Fmachine-learning-0.10.0.vsix

@v-srinisa @chayaverma7 Please merge this in and update the gallery when you get a chance, I've already uploaded the VSIX.

The gallery has been updated.

@chayaverma7 I noticed you said gallery has been updated prior to merging the PR. did you use the files from Leila's branch? if so, it could lead to errors, her branch might not be up to date.

We discussed this, I've updated the doc instructions to be more clear about this to avoid such situations in the future =)


[uriparser] updated to 0.9.2

uriparser has native CMake support that works well with vcpkg. The CMakefiles.txt port was removed and the portfile was updated according.

Fantastic. Thanks for the update, @david-antiteum!


[Anime|Manga] Parse breaking for aired and published field.

Due to last implementation. Regex checks for a pattern of (.*) to (.*) for examples such as Apr 3, 1998 to Apr 24, 1999
But failed to realize that movies and one shots don't follow that format and may return simply Sep 1, 2001.

Fixed & Tested. Should also be checking for empty dates - yes, MAL sometimes does that...


disabled attribute is deprecated

I get this message in the console:
Use of "disabled" attribute has been deprecated, please use "disable"
Reference:
https://github.com/angular-ui/bootstrap/tree/master/src/tabs/docs

Look like, in the version of ui-bootstrap you are using... the use of "disabled" attribute has been deprecated, please use "disable" :)
Can you tell me what version of ui-bootstrap you are using (i'm guessing not master :) and i'll look at a version bump of this when we include this change (as it breaks existing behaviour).
Keep in mind it's a warning, not an error.

I'm using:
"name": "angular-ui-bootstrap",
"version": "0.13.3",

"name": "angular-ui-router-tabs",
"version": "1.4.2",

Fixed in v1.6.0


are these the same process? rescue of stalled ribosome/ ribosome-associated ubiquitin-dependent protein catabolic process

rescue of stalled ribosome GO:0072344
Biological Process
DEF
A process of translational elongation that takes place when a ribosome has stalled during translation, and results in freeing the ribosome from the stalled translation complex.
ribosome-associated ubiquitin-dependent protein catabolic process GO:1990116
Biological Process
DEF
The chemical reactions and pathways resulting in the breakdown of a protein or peptide encoded by an aberrant message and associated with a stalled ribosome. Degradation is initiated by the covalent attachment of a ubiquitin group, or multiple ubiquitin groups, to the ribosome-associated protein.
Synonyms
Both seem to be  different  ways of describing the  process or "ribosome quality control" performed by
Ribosome quality control complex
The RQC complex is a 60S ribosomal subunit-associated complex involved in ubiquitin proteasome mediated degradation of polypeptides whose translation is stalled on the ribosome. Rkr1 is an E3 enzyme believed to modify the stalled polypeptide, while the Cdc48 subcomplex is thought to extract the ubiquitinated polypeptide from the ribosome. Tae2 signals the 'translational stress' to the Hsf1 (P10961) transcription factor.

Hi Harold, did you have any thoughts on this?
best
val

@hdrabkin  when this is addressed can it be made clear in the def that this term is related to cytosolic ribosome/translation.


editableList resize() and resizeItem() callbacks not getting called when items are added or removed from the list

Current Behavior
It appears that the resize() and resizeItem() callbacks on editableList do not get called as they should when an item is added or removed from the list, unless I am misunderstanding the docs.
resize() does get called when the node dialog is initially opened, but not thereafter and resizeItem seems never to be called at all.

See also forum post https://discourse.nodered.org/t/problem-with-editablelist-resize-callback/88263 where @marcus-j-davies confirms the behaviour (of resize at least).
Expected Behavior
No response
Steps To Reproduce
No response
Example flow
paste your flow here

Environment

Node-RED version: 3.1.9 and 4.0.0-beta.3
Node.js version: 20.5.1
npm version:
Platform/OS:
Browser: Edge on Ubuntu

The documentation is not entirely correct - resize() and resizeItem() are called when:

the list is created - $("ol.list").editableList({})
the width changes - $("ol.list").editableList("width", "100px")
the height changes - $("ol.list").editableList("height", "100px")

OK, thanks.  Yes, the docs are at least ambiguous.

Right - these callbacks are related to the physical space of the list, rather than changes to how many items are in the list. I'll transfer this over to the website repo so we remember to update the docs.


Transferred tokens went to the wrong tokens

Hi , I transferred 833 rat dao tokens from one sub nami wallet to another.  The tokens were placed into RADtoken and replaced the already tokens which were there so the RADtoken says 833 instead of 100000. There were 3 transfers but the 833 rats dao tokens went into RADtoken. Addr: addr1q8p3sdj9ffn7ucjdgr8u2r2r3w72xyzlt3cdz8jmjjng090s7ptx85fgtec4n2ktlrnxk9qu33xhufe7kea57az4zcps5wddg6. Do advice on correction. Thanks

The statement should say RADtoken 833. The transfer created a new token RADtoken 833 went it should go into rats dao with the rest of tokens. Thanks

Figured out what happened.


Syntax Highlighting for code examples

Is your feature request related to a problem? Please describe.
Documentations have poor readability for the code examples when they are all pretty much the same color. Especially when in this day and age, pretty much all programming software has syntax highlighting and most sites for sharing them
Describe the solution you'd like
Color the code examples with similar to Visual Studio's highlighting syntax

After some messing around and site screenshots from other people, I found out the problem of the poor site view and functionality was Chrome automatically blocking cookies and thus somehow breaking 95% of the site functionality.


Create AWS AMI for 0.4.3

The AWS AMI's aren't updated for the 0.4.3 release. This means that Docker 1.10.x isn't available out of the box. While it is possible to use ros os upgrade, this significantly slows down the setup time.
Also, clarify the cloud-config when using:
  upgrade:
    url: https://releases.rancher.com/os/releases.yml
    image: rancher/os

Does this force an update on first boot? Do I need to set the image to rancher/os:v0.4.3?

+1

You can try building your own: https://forums.rancher.com/t/how-to-build-rancheros-amis/1672

@ryansch
did you know the packer way to build the ami image: https://github.com/rancher/os-packer

@SydOps That's quite old and hasn't been updated since 0.3.0.

Published the v0.4.3 AMIs.

Thanks @denischannon. could you please update the packer reopsitory and share us the template to us as well?


[FEATURE] Implement Personalized Book Recommendations Based on User Search History

Is this feature already requested?

[X] I have checked "open" and "closed" issues, and this is not a duplicate.

Problem or Missing Functionality
Currently, the system lacks personalized recommendations for users based on their interests and search behavior. Without targeted suggestions, users might struggle to discover new books relevant to their preferences, reducing engagement and retention. This feature aims to address this gap by tracking user search history and providing book recommendations based on previously searched genres, thereby enhancing the user experience and promoting book discovery.
Feature Description
The Personalized Book Recommendation feature suggests books based on a user’s past searches, primarily focusing on the last-searched genre. It enhances user engagement by offering relevant recommendations and promotes book discovery. If no search history is available, the system defaults to popular books, ensuring continuous functionality with minimal changes to the existing system.
Screenshots
No response
Would you like to work on this feature?
Yes
Implementation Plan
Implementation Plan

Create User Search History Entity: Add a UserSearchHistory table to store user ID, searched genre, and timestamp.
Implement Search Logging: Modify the search API to log each user's search with the genre and time.
Update Repository Layer: Create methods in UserSearchHistoryRepository to retrieve the last-searched genre for a user.
Build Recommendation Logic: Add a method in BookService to fetch books based on the user’s last-searched genre or return popular books if no history is found.
Create API Endpoint:Add a new /recommendations/{userId} endpoint in BookController to serve the recommendations.
Test and Verify: Use tools like Postman to test search logging and validate that appropriate recommendations are returned based on search history.

@ajaynegi45 I would like to work on this issue as well. Can you please assign it to me.

@ajaynegi45
i would like to work on issue would you assign me this issue .

@ajaynegi45 I would like to work on this issue as well. Can you please assign it to me.

Start working on it

@ajaynegi45  i would like to work on this issue please assign me this


Reland "sliverGridDelegate mainAxisExtent add assert (#148470)"

Reland: https://github.com/flutter/flutter/pull/148470
Fixes https://github.com/flutter/flutter/issues/138871

This was reverted after https://ci.chromium.org/ui/p/flutter/builders/prod/Linux web_canvaskit_tests_7_last/14617/overview failed in postsubmit.
Previously it passed in presubmit, and it passing again in presubmit now. If it fails again and this is reverted again, we should file an infra ticket to investigate.

Hmm, it looks like some tests are still failing here.

Hmm, it looks like some tests are still failing here.

 I refer to other assertion test methods, but they still fail. My local test can pass normally (packages/flutter).
The code of reland has not changed much from before. It appeared after merging the latest master code. I have been busy with work recently, so I will take time to deal with it.
Thank you for your guidance. I will reply to you after confirming that it has been handled.

@Piinks
I changed the error content matcher. The previously pushed code could not be passed. It should be Linux that escaped the single quotes in "'mainAxisExtent == null || mainAxisExtent >= 0' ", and finally became "'mainAxisExtent == null || mainAxisExtent >= 0' "
I removed the single quotes


After downloading llava-v1.5-7b locally, then I uploaded it to my cloud server, but it didn't load successfully [Question]

Question
excuse me, I need your help very much, when I load llava-v1.5-7b to the web side in the third terminal, I changed the path, why does it keep showing in the request huggingface connection, I can't connect huggingface, so I download the model to the local and upload it to my cloud server. The directory where the model files in the server are located is: /opt/data/private/models/LLaVA/liuhaotian/llava-v1.5-7b/。Is it problem about model path?

Please remove the leading / for --model-path, like '--model-path liuhaotian/llava-v1.5-7b'

Thank you very much, but the result is still the same，Do I need to change the config.json file?

Is this an offline server?

Sorry, I didn't quite understand what you meant, but I opened the global proxy and the proxy test was normal.

Is this an offline server?
Thank you very much, this is online.

Thank you very much, but the result is still the same，Do I need to change the config.json file?
The server can't find clip-336 model locally , and can't download it from huggingface.co

非常感谢，但是结果还是一样，我需要更改config.json文件吗？

服务器无法在本地找到clip-336型号，也无法从 huggingface.co 下载

Thank you, but may I ask what is the reason for this? Or are there any good solutions? I just can't access the model I've already downloaded.

非常感谢，但是结果还是一样，我需要更改config.json文件吗？

服务器无法在本地找到clip-336型号，也无法从 huggingface.co 下载

Thank you, but may I ask what is the reason for this? Or are there any good solutions? I just can't access the model I've already downloaded.

缺模型文件，下载复制过来：https://huggingface.co/openai/clip-vit-large-patch14-336

"2023-10-20 10:52:28 | ERROR | stderr | OSError: We couldn't connect to 'https://huggingface.co' to load this file, couldn't find it in the cached files and it looks like openai/clip-vit-large-patch14-336 is not the path to a directory containing a file named config.json.
2023-10-20 10:52:28 | ERROR | stderr | Checkout your internet connection or see how to run the library in offline mode at 'https://huggingface.co/docs/transformers/installation#offline-mode'."
I have a similar problem

Dear Haotian, can you sleep well, I can't, cause I have a similar problem 2 :-(

“2023-10-20 10：52：28 |错误 |斯特德尔 |OSError：我们无法连接到“https://huggingface.co”来加载此文件，在缓存文件中找不到它，看起来openai/clip-vit-large-patch14-336不是包含名为config.json的文件的目录的路径。 2023-10-20 10：52：28 |错误 |斯特德尔 |在'https://huggingface.co/docs/transformers/installation#offline-mode'查看您的互联网连接或查看如何在离线模式下运行图书馆。
我有类似的问题
If you can't find the model clip-vit-large-patch14-336 , you can download this model at the download address: https://huggingface.co/openai/clip-vit-large-patch14，and change the name to clip-vit-large-patch14-336

If you can't find the model clip-vit-large-patch14-336 , you can download this model at the download address: https://huggingface.co/openai/clip-vit-large-patch14，and change the name to clip-vit-large-patch14-336

download the model  clip-vit-large-patch14-336


[Update] Add improved error message for buffer allocation failure in HE-MEM

Description
Addresses this case.
When not enough/no hugepages are allocated, the memory host exerciser simply fails similar to the following:
    starting test run, count of 1
API version: 2
AFU clock: 470 MHz
Allocate SRC Buffer
    Test mem(1): FAIL

With this change, it instead fails like so, notifying the user that enough hugepages might not be reserved:
    starting test run, count of 1
API version: 2
AFU clock: 470 MHz
Allocate SRC Buffer
SRC Buffer allocation failed. Please check that hugepages are reserved.
    Test mem(1): FAIL

The implementation specifically catches opae::fpga::types::except as that is what gets thrown from the VFIO plugin's fpgaPrepareBuffer implementation when its internal opae_vfio_buffer_mmap call is unsuccessful (such as when there are no hugepages).
Collateral (docs, reports, design examples, case IDs):
Tests added:
Tests run:
Tested manually on n6001

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 64.508%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
15809

Relevant Lines:
24507

💛  - Coveralls


Minor Fixes - Found while writing code documentation

A bunch of small fixes that I found while going through and writing documentation, I'm cutting this PR before the documentation is done in the idea that I'll start developing a bit more correctly and cut a branch per fix.
Some fixes include:

initialize object attributes with undefined if they're defined later. this is a V8 runtime optimization.
removed the definitions of noop in favor of using _.noop
added expireSeconds to the collection / model store so we can start taking advantage of expiring the cache
removed all the postInitialize functions since they have been deprecated
minor whitespace issues where tabbing was off
biggest change - removed the checkFresh code and all it's surrounding attributes / helper functions. This is because checkFresh current doesn't work (it created an infinite loop). This change is to favor the idea of setting an expireSeconds rather than invoking checkFresh for a specific model.

Coverage increased (+0.79%) to 81.76% when pulling 9fc9897a72a589f74f6c3bbefd9f3d24abf42543 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.78%) to 81.74% when pulling 34bb45f401aa7177c142cb663c0dd46d858a19d2 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.76%) to 81.73% when pulling e167ee175baf8f7219b8292e2bdacb87bc7fa5ed on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.75%) to 81.71% when pulling a11550a874b3f60f90cb9c67ac2a1e4672c94e38 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.73%) to 81.7% when pulling 2472d58632e1c36d9623c60483b7ba009457e77f on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.72%) to 81.68% when pulling fb4360d1413b73f58824b6e26f8d09fda423cfd9 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.72%) to 81.68% when pulling 0689479e326aef1483953a2268da20d88790ef68 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

Coverage increased (+0.72%) to 81.68% when pulling 57a71cb9382c74b7b8e933e35d4f5a5bf7646300 on fixes-while-documenting into 1dc9e1477525561c2ad73e2cc40b99489679511b on master.

LGTM

:+1:


GH-34937: [R] Minimal build failing due to new test which relies on snappy being installed

Closes: #34937

@github-actions crossbow submit test-r-offline-minimal


Privacy policy doesn't exist

The link to privacy policy on the legal page doesn't go anywhere. As the beginning of GDPR looms, would be good to get the Monero privacy policy sorted. 👍

The privacy policy is at the bottom of the legal page. The old pages were removed a while ago https://github.com/monero-project/monero-site/pull/455#issuecomment-339360972.
Where did you find a link to one of the old pages?

@mattcode55 The legal page doesn't have a privacy policy on it, it instead has a paragraph which links to a non-existent page (with an #anchor). Please go and look: https://getmonero.org/legal/

Yes, it does not link to a different page, it links to a different part of the same page. Scroll the bottom of the Legal page and you will see a Copyright segment and a Privacy Policy segment after the long Terms of Service section.
Everything is as it should be.

@rehrar with the current version of the site, I only see the copyright section. Not the privacy policy section.

Check on mobile? Checking desktop.

@rehrar yes, I see it one mobile right now.

Will fix.

I can see it on desktop just fine

@mattcode55 weird, I reset my cache right before viewing it :/

It's too private for some to be able to see.

I just archived the site on archive.is and I can see it there so it isn't a caching thing, it also is there when I use my phone. Very spooky.

After a good amount of testing, I simply cannot reproduce the Privacy Policy not appearing. @wgx can you share your OS and browser? Try on another computer as well. Still the same problem? Mobile?

Firefox 58, MacOS 10.13

@rehrar if I view source, I can see the policy is in the markup but a CSS rule is likely preventing it being shown for some reason.

Is this issue still relevant?

Still not fixed for me - no privacy policy visible in firefox

I can see it properly on Linux with Firefox 60.0.2 64-bit. Anybody else able to test this on MacOS?

This issue is old and was discussed and closed on gitlab. Please reopen if you feel it's still relevant.


Upgrade money dependency

I need to update the version of dependency ": money" to be compatible with phoenix 1.4.
Closes #5 .

Thanks for your PR. Can you please not reformat the code?
This package depends on the major version one of the money library. Can you therefore only loosen the requirement to ~> 1.2 which also covers 1.3.1?

Sorry for that . I already revert.

Coverage remained the same at 89.474% when pulling 9fece08aca3dd6c35479773e2e9d7905878d472b on coletiv:hotfix/upgrade_money_dep into 3765076eba6c1ddbe7d8f21f83554fd03c4ddd21 on jshmrtn:master.

@marinho10 Since this was such an easy change, I did it myself. It is already published as v0.3.3.


Update Reducers.md

Remove un-necessary comma

This is more consistent with the rest of the dog from what I see. Thanks!


Time slider always shows 0 if cycle information cannot be determined

If the cycle information cannot be determined from either filename or information in the file for multiple files in a .visit file, the time slider always shows "0". In this case it would be more useful if the time slider showed the time step number.(I am listing this as bug because I believe that this used to be VisIt's behavior a while back, and this no longer seems to work.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 800
Status: Pending
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Time slider always shows 0 if cycle information cannot be determined
Assigned to: Mark Miller
Category: -
Target version: -
Author: Gunther Weber
Start: 07/28/2011
Due date:
% Done: 0%
Estimated time:
Created: 07/28/2011 12:53 pm
Updated: 09/12/2011 10:55 pm
Likelihood: 3 - Occasional
Severity: 2 - Minor Irritation
Found in version: 2.3.0
Impact:
Expected Use:
OS: All
Support Group: DOE
Description:
If the cycle information cannot be determined from either filename or information in the file for multiple files in a .visit file, the time slider always shows "0". In this case it would be more useful if the time slider showed the time step number.(I am listing this as bug because I believe that this used to be VisIt's behavior a while back, and this no longer seems to work.
Comments:
Does it help to switch on the 'Try harder to get accurate times/cycles' option in Options -> Preferences before opening the database? It does not help. I had actually already tried that. The problem are files where it is not possible at all to get time/cycle information either from the file or the filename.Jakob van Bethlehem wrote:Does it help to switch on the 'Try harder to get accurate times/cycles' option in Options -> Preferences before opening the database? Gunther Weber wrote:It does not help. I had actually already tried that. The problem are files where it is not possible at all to get time/cycle information either from the file or the filename.Jakob van Bethlehem wrote:Does it help to switch on the 'Try harder to get accurate times/cycles' option in Options -> Preferences before opening the database?Ok, then I think I know what the basic problem is. When it is not possible to get time/cycle information either from filename or from file, I think we default to setting that information to all zeros. Instead, what I think this ticket is requesting is that we default to setting it to state index. I think that should be easy to do down in the format or interface (I can't remember which) classes.And, if that was VisIt's behavior in the past and we somehow lost that behavior, we should probably try to find out why.

0811_wave_example.tar.gz


x/tools/godoc: Method's Fragment link is invalid

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.8.1 darwin/amd64

What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/i178inaba/work/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.8.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.8.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8b/5j9t64vs0sg_n1jjfkkrg88m0000gn/T/go-build329351097=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"

What did you do?
I referred to the following documents.
https://golang.org/pkg/net/http/#Client.Get
https://golang.org/pkg/net/http/#Header.Get
What did you expect to see?
The Fragment link should be as follows.
#Client.Get
#Header.Get

func (c *Client) Get(url string) (resp *Response, err error)

func (h Header) Get(key string) string

What did you see instead?
The function name link of the part displaying the signature of the method is invalid.

func (c *Client) Get(url string) (resp *Response, err error)

func (h Header) Get(key string) string

I've investigated this. This issue is actually 2 issues, and the correct fix is different from what's suggested above. One is a deploy/release issue (what's running at golang.org), and the other is a code issue in latest master of tools subrepo. Both need to be resolved.
The version of cmd/godoc that's running at http://golang.org/pkg/ is weird. I can't easily tell what version exactly it is, but I can tell it's not the version that's a part of go1.8.1 release (which didn't have this bug), and it's not the latest master of tools subrepo (which has this bug, but the fix is different from what the issue suggests). So, I'm going to ignore it below and discuss what I can reproduce locally with latest master version of cmd/godoc in tools subrepo.
This bug was actually introduced in https://github.com/golang/tools/commit/e1bdc76d0461f7041136c70e0a1356ea0f5e01d0 (similar to https://github.com/golang/go/issues/19894#issuecomment-292761048). /cc @jayconrod
With the parent commit (https://github.com/golang/tools/commit/00f7cd5589365aa8eb6e88f55d845eea9ca39f25), the generated HTML looked like this:

With https://github.com/golang/tools/commit/e1bdc76d0461f7041136c70e0a1356ea0f5e01d0, it becomes:

Notice that the Get method name was not linked before, but it becomes linked after. And the link is wrong.
So, the correct fix is to remove the link, not to fix the URL. The link wasn't meant to be added, it was an unintentional regression caused by https://github.com/golang/tools/commit/e1bdc76d0461f7041136c70e0a1356ea0f5e01d0. Its commit message confirms it was meant to be a fix for composite literals anchors only.
(The link doesn't make sense in this context, because it points to the same location as the function/method. There's already a heading that does that too. That's why it should be removed.)

Thank you so much for review!
I'm going to fix it according to your review.


Issue facing while Adding extra columns in existing table.

I am getting one error while adding columns in existing table. its not updating in the replica table. I will share you some screen shot for the same.

It seems like the issue is when force merging a schema change is occurring for a column addition/removal.
Force merge should be used when modifying a column(changing data type)

I updated with latest version but again i am getting Error


Please add HD Helper

https://civitai.com/models/110071/hd-helper

Hi, Comfyui loads Lycoris as Loras, you can put it in the loras folder and load it with the Load Lora node as far as I know.

Cool, I've added this now
https://github.com/fofr/cog-comfyui/commit/21bff979c3750b4b98595a4e56521df14d8ad0a1


Can I use your VI-SVC and ViSinger(VI-SVS) as the backbone of my project and can I credit you in the credits and references?

Can I use your VI-SVC and ViSinger(VI-SVS) as the backbone of my project and can I credit you in the credits and references?

yes, you can

yes, you can

Thanks you so much


Fix broken circleci job for macOS

This PR updates the openssl version to be installed for testing macOS builds
The circleci config file currently points to<EMAIL_ADDRESS>to install openssl for macOS. This change was made as part of the following PR, where previously openssl@3 pointed to openssl v3.0.x which was causing errors trying to build oqs-provider. So the change was made to specify<EMAIL_ADDRESS>OpenSSL v3.2 was released last week and the circleci jobs for macOS started failing since<EMAIL_ADDRESS>is no longer available to install using homebrew. Instead the following are the options: openssl@3 (which points to the current stable version, v3.2<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Changes made in this PR include:

pointing the openssl version back to openssl@3 since it now points to the latest 3.2
a small doc change to the CONTRIBUTING doc to update the circleci command to run a specific job locally. (This command no longer accepts the --job option)

Thank you for figuring out the failing test issue. I was having a hard time figuring that out.

Well, apologies for having you try to do this. This should not have happened to begin with.

that doesn't have the --log option for circleci local execute command

Ah, OK. Thanks for the explanation. And more importantly, it also doesn't have the --job option. What about just adding "[" "]" around --job then?

Yes, that makes sense. Will do that. Thanks @baentsch

Thank you for figuring out the failing test issue. I was having a hard time figuring that out.

Well, apologies for having you try to do this. This should not have happened to begin with.

No worries, its always good learning.

(fyi @SWilson4 @dstebila to help implement the things we write in liboqs PR: Pretty much at the time of merging such algorithm changes we ought to have downstream PRs available).

Noted, will do in the future. (In the near future, hopefully, for Falcon.)

Please rebase to latest main and CI should turn green.


NMA is no longed operational

NMA is no longer operational link

Might as well remove the code, too.
If you're up for it, add to this PR. If not, I'd be happy to make the patch tomorrow.

@dgw Done, please have a second look

Cheers!


Refactor City resources

avoid return City entity to clients
consolidate all related resources -> simplification

The point 1 is not closed yet, but let's close it for now.


[Snowflake] | Metadata extraction fails with errors.

Affected module
Does it impact the UI, backend or Ingestion Framework?
Ingestion
Describe the bug
A clear and concise description of what the bug is.
Snowflake metadata extraction seems to fail with the below error upon SHOW /* sqlalchemy:get_table_names */ TABLES IN "<schema>"
{OMetaAPI:288} - (snowflake.connector.errors.ProgrammingError) 002043 (02000): 01a3e60f-0404-09c7-0000-37851fb62ada: SQL compilation error:
Object does not exist, or operation cannot be performed.

To Reproduce
Screenshots or steps to reproduce
Start Snowflake ingestion with a user with at-least 2 roles (I feel like that might be the issue)
Expected behavior
A clear and concise description of what you expected to happen.
Able to extract and ingest Snowflake metadata
Version:

OS: [e.g. iOS]
Python version:
OpenMetadata version: [e.g. 0.8]
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==XYZ]
openmetadata-ingestion==0.10.0
openmetadata-ingestion-core==0.10.0

Additional context
Add any other context about the problem here.
NA

@ayush-shah lets fix this today.

Fixed in #4653


Enhancement: Spells

I was writing spells in modules and noticed that it doesn't support markdown in the app. It would be greatly appreciated if they had markdown/html support in the descriptions of the spell. As of now, they work fine for PDF generation.

PDF:

App:

@jacobjohnston Any updates to this enhancement? I would love to use this for my future campaigns.

Hey @PiSaucer
1.) The proper way to do this is to not use
 tags, but instead, use multiline strings in YAML. That should look like this (be aware of the indentation and extra lines added):
description: "This legendary quarterstaff has thwacked many a foe.

    This is a multiline item

    More lines"

2.) The request, as written, requires a change to EncounterPlus itself, which I don't have the power to make.

The multiline strings in YAML work in the PDF and the app. Thank you for your time and help. Do you have any idea if YAML could hold bold text?

It turns out that the app supports  and  tags for bolding and italicize. However, it doesn't support both at once. Again, thank you for your time and help.


Remove shebang multiple parameter in script

Using multiple parameters in shebang has been indicated as error prone across multiple platforms, more here https://www.shellcheck.net/wiki/SC2096 we should follow due practice across all our scripts. Bash scripts that use multiple parameters are
https://github.com/build-trust/ockam/blob/01e90778abb6a1c53afc6dcb47feafecfc972c90/tools/scripts/release/crates-to-publish.sh#L1
https://github.com/build-trust/ockam/blob/01e90778abb6a1c53afc6dcb47feafecfc972c90/tools/scripts/release/changelog.sh#L1
https://github.com/build-trust/ockam/blob/01e90778abb6a1c53afc6dcb47feafecfc972c90/tools/scripts/release/crate-bump.sh#L1
https://github.com/build-trust/ockam/blob/01e90778abb6a1c53afc6dcb47feafecfc972c90/tools/scripts/release/crate-publish.sh#L1

I would like to work on this

Closed in https://github.com/build-trust/ockam/pull/3697
Thank you @HyperNova114 🥳


Fix player metadata not working in Plasma KDE

Plasma KDE is ignoring non-standards compliant players.
See here: https://github.com/KDE/plasma-workspace/commit/8eec2cfd36c4ecf9e2b13f4226ed49495271a1e2#diff-19867a87b2583d81920acad1cf500a89
This PR adds properties to make FeelUOwn recognized by KDE Plasma.

LGTM


npm install: installs<EMAIL_ADDRESS>

just did a fresh install via npm, got version 1.9.1, expected v 3.0
this is a continuation of closed issues #648 & #624
solution that can only be done by owners:
npm dist-tag add<EMAIL_ADDRESS>latest

just saw that 1.9.x was recently updated, npm install should install 3.x by default

@MikeSperone this is just how NPM works. Unfortunately NPM decides that it is going to install the 'newest' version, not by version number but by release date.  An update to version 3 will be released this week but if ever a minor change to 1.X is made. this issue will resurface.

@whmii you can tell npm what to consider latest!

@whmii https://docs.npmjs.com/cli/dist-tag

@eballeste updated https://www.npmjs.com/package/bourbon-neat


Semantic consumer acknowledgements

On RPCs, we should make sure these errors would not trigger retries and the message should be (negatively, when appropriate) acknowledged immediately:

TypeError
RangeError
ReferenceError
SyntaxError
assert.AssertionError

https://github.com/openrm/hato/blob/aff5a27/plugins/retry/errors.js#L31


FoundationEssentials: correct file writing on Windows

Ensure that we open the file in binary mode to avoid line ending conversion. Without this, writing any 0xa byte would translate to writing 0xd 0xa. This improves the test coverage pass rate.

@swift-ci please test


Fixed a bug that caused an empty list of previous WorkUnitStates to pass into SourceState

In pull request #65, a new Constructor is added to SourceState that takes a previous SourceState and calls SourceState.getPreviousWorkUnitStates() to populate the SourceState.previousTaskStates. However, it turns out previousTaskStates is always empty and therefore the empty list gets passed into the current SourceState. This is the root cause for the issue with gobblin-stand-alone.
Signed-off-by: Yinan Li<EMAIL_ADDRESS>

LGTM


Data is not indexing to database

Do you want to request a feature or report a bug?
BUG
What is the current behavior?
Indexer starts but do not index any data into local database
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
I tried to build graph-node locally and successfully deployed several subgraphs (Uniswap, Bancor).
But indexer reports such warning and nothing is indexed to database.
 graph-node log
Oct 21 18:53:02.226 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x5fa77eb917376d67d72a7fae42b286a6a11e6e7e11d1f73dfae009b1bfc6cb76 (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.411 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x97564b226f1742d9d073994d3d664208d95e859a9a4dac2c62ac903a5268587e (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.414 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0xa3ee1b6def05ceab6c35880a665164880d60637de471eda6a5aedf741b46eba3 (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.465 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0xc276868064fe701b091176b2246ceb87747db07ca1e8f58d997a26da6ff8b2ba (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.478 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x9886ba26bdb9f7fb2f803c5d60d544cdaf7b035e77c2405d8c48797d00b153ba (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.485 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x0cd0deee59ab5b671659a11eec037a6b5c00fb6243c89aa469559b74db35e310 (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.491 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x665586bdd5aefc860f8ff2d186617544d5aa6e5ae7203bf54b26f310be372e91 (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.533 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x5f81bfa69fc8acbf14e8c301f3269dac88298f52abbf80edd151703aff8cbf9a (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.552 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0xfd07e36cfaf327801e5696134b36678f6a89fb1e8f017f2411a29d0ae810ab8b (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.657 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0xe0c7c0b46e116b874354dce6f64b8581bd239186b03f30a978e3dc38656f723a (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.658 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0xe9fb121a7ee5cb03b33adbf59e95321a2453f09db98068e1f31f0da79860c50c (2 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.665 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 1 for block 0xe9fb121a7ee5cb03b33adbf59e95321a2453f09db98068e1f31f0da79860c50c (2 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer
Oct 21 18:53:02.671 WARN Trying again after eth_getUncleByBlockHashAndIndex RPC call failed (attempt #10) with result Err(ErrorMessage { msg: "could not get uncle 0 for block 0x3d6122660cc824376f11ee842f83addc3525e2dd6756b9bcf0affa6aa88cf741 (1 uncles): Decoder error: Error(\"missing field `transactions`\", line: 0, column: 0)" }), subgraph_name: network/ethereum/mainnet, subgraph_id: network_ethereum_mainnet_v0, component: NetworkIndexer

There are environment variables I set:
 Environment variables
DISABLE_BLOCK_INGESTOR=true
GRAPH_ETHEREUM_CLEANUP_BLOCKS=true
ETHEREUM_RPC=mainnet:https://mainnet.infura.io/v3/{here_is_my_key}
POSTGRES_URL=postgresql://{myuser}:{mypass}@<IP_ADDRESS>:5432/{mydb}
THEGRAPH_STORE_POSTGRES_DIESEL_URL= postgresql://{myuser}:{mypass}@<IP_ADDRESS>:5432/{mydb}
IPFS=http://<IP_ADDRESS>:5001

I started the node with the command:
graph-node --network-subgraphs 'ethereum/mainnet'

What is the expected behavior?
I expect to see some data associated with the events of the contracts in my database, but actually there is nothing .
         table_name         | pg_relation_size
----------------------------+------------------
 event_meta_data            |                0
 ethereum_blocks            |                0
 eth_call_meta              |                0
 pg_stat_statements         |                0
 __graph_node_global_lock   |                0
 ens_names                  |                0
 unneeded_event_ids         |                0
 eth_call_cache             |                0
 large_notifications        |             8192
 deployment_schemas         |             8192
 __diesel_schema_migrations |             8192
 db_version                 |             8192
 ethereum_networks          |             8192
(13 rows)

For anyone else who stumbled on this confused that ethereum_blocks is empty, check the other schemas in the DB. The real data for me was in the blocks table under the chain1 schema.


Add postgres testcontainer closes #71

Codecov Report

Merging #100 (30f6995) into main (42f55e6) will increase coverage by 14.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##              main     #100       +/-   ##
============================================
+ Coverage     0.00%   14.05%   +14.05%
- Complexity       0       38       +38
============================================
  Files           43       43
  Lines          918      918
  Branches       116      116
============================================
+ Hits             0      129      +129
+ Misses         918      786      -132
- Partials         0        3        +3

Flag
Coverage Δ

unittests
14.05% <ø> (+14.05%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...in/com/innopolis/innoqueue/service/QueueService.kt
2.84% <0.00%> (+2.84%)
:arrow_up:

...nnopolis/innoqueue/service/NotificationsService.kt
8.65% <0.00%> (+8.65%)
:arrow_up:

...com/innopolis/innoqueue/service/SettingsService.kt
9.25% <0.00%> (+9.25%)
:arrow_up:

...com/innopolis/innoqueue/service/ToDoTaskService.kt
11.29% <0.00%> (+11.29%)
:arrow_up:

...e/service/FirebaseMessagingNotificationsService.kt
13.33% <0.00%> (+13.33%)
:arrow_up:

.../innopolis/innoqueue/controller/QueueController.kt
14.28% <0.00%> (+14.28%)
:arrow_up:

...nopolis/innoqueue/configs/FirebaseConfiguration.kt
23.07% <0.00%> (+23.07%)
:arrow_up:

...com/innopolis/innoqueue/service/DatabaseService.kt
25.00% <0.00%> (+25.00%)
:arrow_up:

...opolis/innoqueue/controller/ToDoTasksController.kt
28.57% <0.00%> (+28.57%)
:arrow_up:

...otlin/com/innopolis/innoqueue/model/QueueQrCode.kt
33.33% <0.00%> (+33.33%)
:arrow_up:

... and 15 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature request: Fetch client

Using meta frameworks like SvelteKit sometime fetch calls to be made via the special fetch provided by the framework in load files. It would be nice if there is an API that allows the pocketbase instance to use an explicitly provided fetch function.

This will be implemented soon as part of the planned JS SDK refactoring (together with the custom headers and request options).
I'll keep the issue open for easier tracking.

Closing as it was implemented in v0.17.0-rc1.
For details and feedback please check the discussion in the main repo - https://github.com/pocketbase/pocketbase/discussions/3134.


Redesigned the updater, added a "test mode" bade and a few misc fixes

Changes

Truncated the GUID in the new follower notification panel
Truncated the GUID in the new follower desktop notification
Add testing badge (we need logic behind this to hide/show when in production/testing)
Add tooltip to truncated GUID in followers list
Added custom scrollbars to transaction modal
Redesign the update software badge

@jjeffryes ready for review