Error "tls: first record does not look like a TLS handshake" when accessing site

I set up a new drone server by downloading the .deb.  When I surf to it, my browser downloads a small binary file.
Running drone from the command line shows the following when I try to access the page:
root@tetrad:/etc/ssl/certs# cd
root@tetrad:~# droned -config /etc/drone/drone.toml
2015/09/06 19:33:54 http: TLS handshake error from <IP_ADDRESS>:36073: tls: first record does not look like a TLS handshake

I double-checked my cert files, and they both appear normal, and are used by other services on the box without problems.

I have also tried switching to a self-signed cert and get the same error.

OMG facepalm
Just silently ignore that this ticket ever existed.
My bookmark was using 'http' instead of 'https'.


Fill different colors for barchart for each bar

Hi,
I want set different color for each bar in barchart? How do i do that?

@RupaliPatwa https://github.com/codesuki/react-d3-components/issues/118

thanks . It worked.


Enforce style checks

As per our discussion in #51, this issue is to track enforcing style checkers.
I expect this to be done only on the new branch, the old code would stay as is.

I've been using Black, which is IMHO better than a style checker -- it simply forcibly re-formats your files. I think it does a nice job.
isort is also nice, enforcing style on imports.

I was personally using flake8 but black is also a viable option.
Can we enforce that no formatted code is accepted in PR though?
I will look for some pre-commit hook for Black

I think we can use Github Actions to enforce style checks and reformatting.
We can also set conditions for when the actions should be skipped. Here is an example that skips based on the commit message.
Both require us to use YAML, and I'm fine with that.
Thoughts?

Closing in favour of #56


Add Address Matching to TCPRoute and UDPRoute

What would you like to be added:
Add address matching to TCPRouteMatch and UDPRouteMatch.
Why this is needed:
TCP and UDP Routes currently only support custom matching extensions. It would be helpful to include some basic matching capabilities within the Routes. Address matching seems like a natural starting point. Although for most ingress use cases this could be covered by Gateway listeners, this concept could be quite helpful for mesh routing.
Also, see transparent proxy discussion in #727

In the case of addresses, whether matching is useful depends on having a listener that is implicitly attached to multiple addresses. The system has out-of-band knowledge of address semantics, so you can know that you want a route attached to address A and not to address B.
Can we make a similar argument for ports?

I may be misunderstanding what you're saying here, but either or both of the following scenarios are entirely possible:

Gateways listen on multiple addresses, a Route only wants to be attached to one of them
Gateways listen on multiple ports, a Route only wants to be attached to one of them

Although both of the above are possible and this addition would help, I think this addition becomes significantly more compelling when you take into account mesh implementations that may want to match requests to a given address or port and apply some kind of routing to them.

Add Address and Port to TCPRouteMatch and UDPRouteMatch.

@robscott Source or destination or both?
The following 5 things identify a byte stream on a TCP/IP networking stack:

Source IP
Source Port
Destination IP
Destination Port
Protocol

We currently capture destination port via listener and the protocol. One could argue that the destination IP is also captured indirectly via the relationship  Gateway -> Listener -> Route.
Source is not captured anywhere.
+1 to this feature. One place to define matching, rather than ensuring that a route is mapped onto the correct listener would help and make the API more user-friendly.

In the case of addresses, whether matching is useful depends on having a listener that is implicitly attached to multiple addresses.

What if the matching is based on source IP/port instead of destination IP/port?

The system has out-of-band knowledge of address semantics, so you can know that you want a route attached to address A and not to address B.

I'm not sure I understand what is the point you are trying to make here. Could you rephrase please?
@jpeach, are you trying to say that a route should not be aware of these addresses/ports because it is a leaky abstraction in that case? While it could be viewed as that, I think the same argument could be applied to the Hostname field in HTTPRoute or TLSRoute.

So, this essentially creates a similar two-directional match to the hostname field on HTTPRoute, but for address and port? That makes sense to me, with the caveat that we definitely need to be clear about what happens if things don't match.
Alternatively, matching on source address and port seems much more likely to be useful.

Good point @hbagdi! I should have clarified that I was intending to match destination IP and Port with these fields. Given the potential for source IP and port matching in the future, it does probably make sense to make the config explicit here. Maybe something like this:
matches:
  - destination:
       ip: <IP_ADDRESS>
       port: 80

this essentially creates a similar two-directional match to the hostname field on HTTPRoute, but for address and port?

That's a great way to summarize this, thanks @youngnick!

Given the potential for source IP and port matching in the future, it does probably make sense to make the config explicit here.

What is your hesitation to include source IP/port in the API right away?

What is your hesitation to include source IP/port in the API right away?

I actually haven't thought about this as much. This particular idea/feature request was targeted at dest IP and Port despite me not actually saying that :). At first glance, it seems like source IP/Port matching may have slightly less portability, but I'd need to look into it a bit more.

I actually haven't thought about this as much. This particular idea/feature request was targeted at dest IP and Port despite me not actually saying that :)

Ack.

At first glance, it seems like source IP/Port matching may have slightly less portability, but I'd need to look into it a bit more.

If portability is a concern, maybe we start with a different conformance level for it?
My motivation to add in source is to add a complete feature that takes both the ends into account rather than only one.
Also, regarding destination port/ip based match, we will need to clarify how Proxy Protocol comes into play.

@jpeach, are you trying to say that a route should not be aware of these addresses/ports because it is a leaky abstraction in that case? While it could be viewed as that, I think the same argument could be applied to the Hostname field in HTTPRoute or TLSRoute.

A route can say that it wants to only match on a specific IP address because there is some out-of-band semantics attached to that address. But what does it mean for a route to only want to be exposed on a specific port, and why would you do that? For example, I have a route and I specify a match for port "21". How is that useful? Are we talking about another programmatic mapping done by a transparent proxy?

Also, regarding destination port/ip based match, we will need to clarify how Proxy Protocol comes into play.

Did you mean source address matching?

I am not sure why port match is any less useful than SNI, hostname, ip, etc. Its just another attribute of the request. For example, maybe I want to match anything on port 22 and deny it or apply some policy.

I am not sure why port match is any less useful than SNI, hostname, ip, etc. Its just another attribute of the request. For example, maybe I want to match anything on port 22 and deny it or apply some policy.

My question is why I would care about the port. If I match on a port, then that reduces  deployment agility for the gateway owner. It's extremely common to run services on "non-standard" ports.

My question is why I would care about the port. If I match on a port, then that reduces deployment agility for the gateway owner. It's extremely common to run services on "non-standard" ports.

So does hostname. There is always a tension between generic routes attached to concrete gateways vs concrete routes attached to generate gateways. I think both are valid, they just depend on the use case.

Did you mean source address matching?

Both? Proxy protocol carries source and destination IPs involved, no?
I think the tension comes in from the ownership perspective. Who owns and decides ports, IPs, DNS names, hostnames.
We have use-cases where this control resides with Cluster Admin for the most part. But, there are some use-cases where the application developer could also be influencing these decisions, with some allow/deny from the Cluster Admin (who is also the Gateway owner in our model).

Did you mean source address matching?

Both? Proxy protocol carries source and destination IPs involved, no?

Yep you are right :)

+1 to considering destination ports like any other attribute. Being able to assign a non-standard dest port to a service (or user) is sometimes needed when dealing with L4 protocols. That may be because there isn't a hostname, or the form of security can't be used in that way. Agree with the agility concern but the cases I'm thinking look like @hbagdi's scenario (cluster admin ~= app dev)!

+1 to considering destination ports like any other attribute. Being able to assign a non-standard dest port to a service (or user) is sometimes needed when dealing with L4 protocols.

You can do this today with a gateway listener on the port you want that binds a UDP or TCP route.

So, it seems like there are two things we're talking about here:

adding fields to hold destination IP and Port on TCPRoute and UDPRoute. This would create a two-level matching scheme, similar to hostname at the Gateway level being required to match a hostname supplied at the HTTPRoute or TLSRoute level for the route to successfully be attached. If that's the case, I can see that it might be useful.
adding fields to hold source IP and Port on TCPRoute and UDPRoute. In this case the details are more like a route discriminator, in that you might have multiple TCPRoutes on a Listener's Port that routed to different backends based on the Source IP or Port. To me, this fits squarely in the purpose of TCPRoute and UDPRoute, although I'm not sure if support could be core? Is being able to route to different destinations based on source address/port common on L4 load balancers? It has been a long time since I configured one. :)

tl;dr putting Destination address/port feels like a way to match Routes to individual Listeners, while Source address/port is another form of routing discriminator that lets you have multiple Routes share an individual Listener.

tl;dr putting Destination address/port feels like a way to match Routes to individual Listeners, while Source address/port is another form of routing discriminator that lets you have multiple Routes share an individual Listener.

This sounds right to me.

Is being able to route to different destinations based on source address/port common on L4 load balancers?

I have limited expertise here, but it seems more common with applying policy (allowlist/denylist IP) than routing.

@shaneutt is adding support for source and dest address matching with GEP #735, I'm going to pull port out to another tracking issue so this one is more clearly aligned.

For anyone else that wound up here looking for the continued port matching discussion, it resulted in https://github.com/kubernetes-sigs/gateway-api/issues/1021 and GEP-957.


NSwag HTTP client generation - Command Line

The page suggests that there are several ways to generate an HTTP client but then only goes into detail about using NSwag Studio.
Ideally, I think most people would like the HTTP client to be generated when ASP.Net Core Web API project compiles.
It is my understanding that NSwag Studio uses the nswag.exe or nswag.cmd under the hood and thus you can use these commands and your NSwag configuration file to automatically generate your HTTP client.
So documentation about NSwag.MSBuild or the command-line options would be ideal.
Also, it is my understanding that NSwag Studio can generate the HTTP client from the ASP.Net Core Web API DLL and doesn't have to point that the Swagger document endpoint.  I think it would be good to include this example in the page.

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

ID: 2483813a-3c16-7ddd-3160-43e6843b55d4
Version Independent ID: 25f7fb5b-92b0-a45b-57ab-fdceab571884
Content: Get started with NSwag and ASP.NET Core
Content Source: aspnetcore/tutorials/getting-started-with-NSwag.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @zuckerthoben
Microsoft Alias: scaddie

I dont think we should repeat all documentation from the project wiki here. Otherwise it will be very hard to keep all the docs updated.

But yes, you can create the configuration with NSwagStudio and the execute it with one of the command line tools (eg nseag.msbuild, or the nswag npm package).

It's hard to find all the various CLI options in the wiki. Perhaps MS Docs should have more links NSwag wiki.

Actually, I see that NSwag wiki hasbeen updated recently to be more comprehensive.

For anyone needing the link, its https://github.com/RicoSuter/NSwag/wiki/CommandLine


Direkt Link must contain http or https

When creating a Row > Button > Style = Direct Link the Web App tells you that it is necessary to add an http:// or https:// within the URL.
Because of this feature it is impossible to add URLs which are redirecting to specific apps.
Example steam://connect/ip
The example URL is trying to connect you to a game server on steam.
The error message displayed says "Invalid URL"

This is a discord limitation, not a bot.

The only way to do this is to setup a webserver that redirects to the application link so you can link to the webserver inside Discord.


[Feature Request] Support for multiple keyboards at the same time

Issue details
I'd like to have the ability in my games for the multiplayer to be playable with multiple keyboards. The Android APIs are setup really good for this. I don't know if this would work good on other platforms. I do know this is not possible on JavaScript.
Possible Setup
InputProcessor.keyDown and InputProcessor.keyUp could report a keyboard object in addition to the keycode. They keyboard object would have a deviceID and display name.
Their should be a way to get an array of all the connected keyboards.
There should also be a way to listen for when a keyboard is connected/disconnected.
Version of LibGDX and/or relevant dependencies
libGDX v1.9.9

I would vote against this. It is not supported on any of the other platforms and a very niche feature request. To support this in your game, you should add your own event hook like the controller extension does.

I was hoping this would work on Lwjgl as well. I added this for Android to my fork and will maintain it there. Now I'll need to add multi-mice support and capturing the cursor.


Copy new Dashboard items not supported

Dear colleagues,
I wanted to copy dashboards within portals. Unfortunately this is currently not supported. Any plans to do so?
Thanks,
philip

This was enabled in #223, but I see that it's not working now.
@apulverizer @rwmajor2 The dashboard type is listed in isSupported. Any thoughts on why it wouldn't be working?

@ecaldwell When I build it locally with latest master branch it works as expected.
On the hosted app, it doesn't work (the dashboard is not enabled for copying).

@apulverizer The hosted app usually lags the master repo a bit so that makes sense. Thanks for tracking that down. I'll check with @rwmajor2 on getting an updated version pushed up.

@rwmajor2 Can you verify that the latest released version on GH is hosted on S3 as well?

Still running into this issue over a year later. Any updates or estimated timeline? @ecaldwell @rwmajor2

I have also had this problem. Is there any known workaround?

Still not working. Is there a work around? Maybe through the Python API.

@brotherpup you can try the clone_items method in the python api, though that would clone all of the underlying maps and services as well.
https://esri.github.io/arcgis-python-api/apidoc/html/arcgis.gis.toc.html#arcgis.gis.ContentManager.clone_items
There is also an example showing how to just copy the item and not the underlying data:
https://developers.arcgis.com/python/sample-notebooks/clone-portal-users-groups-and-content/#Copy-Items
You can also just Save As in the Dashboard web app to make a copy


Create MANIFEST.in

To include LICENSE in the sdist, as is requested by conda-forge
(yes, I'm working on a conda-forge package :))

We've already fixed this problem in #17 – all you need to do is update setuptools.

Nice!

The sdist on PyPI doesn't include LICENSE though

Yes, we fixed it after 0.2 unfortunately. Should we push a hotfix?

Yes, we fixed it after 0.2 unfortunately. Should we push a hotfix?

Not necessary, thank you!


Update npm dependencies (#42)

Coverage remained the same at 92.13% when pulling 7ddaa73c612471246d27a2930c5f395a5a8b1de8 on develop into f9af9e28eb0c39468fca0e554002194651006949 on master.


PARQUET-1583: [C++] Remove superfluous parquet::Vector class

This class which is a syntactic sugar layer on arrow::ResizableBuffer was only being used in one place, for dictionary decoding. I don't think we need to maintain this, and it also features possible instantiated template symbol issues

@majetideepak @xhochy any reason to keep this around?


Bug 1583587 - lower loglevel to debug, wrap others

When deprovisioning, we can't find a state because we have deleted it.
That is expected but our logs show an error log. This really isn't an
error in this scenario. In other scenarios it might be an error, but we
return the err to the caller which will either handle or log it
themselves. So keeping the message as a debug log is useful for us.
There are a couple other methods that were logging errors used by the
broker's recovery feature. The recovery feature handles the NotFound
error case, so we don't want to print errors during those scenarios. If
something other than NotFound is occurs, it would be helpful to log the
error.

Before we would log an error during deprovision that we could not find the job state that was deleted during the deprovision.
time="2018-08-03T03:24:21Z" level=debug msg="service_id: 1dda1477cace09730bd8ed7a6505607e"
time="2018-08-03T03:24:21Z" level=debug msg="plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff"
time="2018-08-03T03:24:21Z" level=debug msg="operation:  7084f8d1-7937-4f54-89cc-37822632bc5e"
time="2018-08-03T03:24:21Z" level=error msg="Could not find instance 54b7b619-96cc-11e8-9244-0242ac11000a associated with job state 7084f8d1-7937-4f54-89cc-37822632bc5e - bundleinstances.automationbroker.io \"54b7b619-96cc-11e8-9244-0242ac11000a\" not found"
time="2018-08-03T03:24:21Z" level=warning msg="unable to find job state: [54b7b619-96cc-11e8-9244-0242ac11000a]. error: [bundleinstances.automationbroker.io \"54b7b619-96cc-11e8-9244-0242ac11000a\" not found]"
<IP_ADDRESS> - - [03/Aug/2018:03:24:21 +0000] "GET /automation-broker/v2/service_instances/54b7b619-96cc-11e8-9244-0242ac11000a/last_operation?operation=7084f8d1-7937-4f54-89cc-37822632bc5e&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 410 37

We still log it but now as debug since the information is useful for developers and potentially troubleshooters. But it won't show up on a normal installation of the broker operating normally.
time="2018-08-03T22:11:01Z" level=debug msg="service_id: 1dda1477cace09730bd8ed7a6505607e"
time="2018-08-03T22:11:01Z" level=debug msg="plan_id: 7f4a5e35e4af2beb70076e72fab0b7ff"
time="2018-08-03T22:11:01Z" level=debug msg="operation:  f2a632b2-c6e7-4e43-b838-79a38cd56592"
time="2018-08-03T22:11:01Z" level=debug msg="Could not find instance e7b0b163-9769-11e8-8283-0242ac110006 associated with job state f2a632b2-c6e7-4e43-b838-79a38cd56592 - bundleinstances.automationbroker.io \"e7b0b163-9769-11e8-8283-0242ac110006\" not found"
time="2018-08-03T22:11:01Z" level=warning msg="unable to find job state: [e7b0b163-9769-11e8-8283-0242ac110006]. error: [bundleinstances.automationbroker.io \"e7b0b163-9769-11e8-8283-0242ac110006\" not found]"
<IP_ADDRESS> - - [03/Aug/2018:22:11:01 +0000] "GET /automation-broker/v2/service_instances/e7b0b163-9769-11e8-8283-0242ac110006/last_operation?operation=f2a632b2-c6e7-4e43-b838-79a38cd56592&plan_id=7f4a5e35e4af2beb70076e72fab0b7ff&service_id=1dda1477cace09730bd8ed7a6505607e HTTP/1.1" 410 37

Fixes Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1583587

Coverage remained the same at 40.562% when pulling 9cfc9236c65c981864877f9c0b8075583b5bcf27 on bz1583587 into f8ddaf2416849c19f3417ed64bc2577cf781805d on master.


Fix #2214 : Handle very large puts that may not fit the cache

Avoid the effect of clearing the cache if the user tries to put an object that is bigger than the cache.

@henri-tremblay done with all review comments. Pls take a look and approve if found ok..

test this please


Broken links in README

Hello,
The README.md refers to interesting blog articles:

The source from this blog post: https://airbus-cyber-security.com/the-oxid-resolver-part-1-remote-enumeration-of-network-interfaces-without-any-authentication/
Part 2 of that blog post: https://airbus-cyber-security.com/the-oxid-resolver-part-2-accessing-a-remote-object-inside-dcom/

But these links now redirect to https://www.cyber.airbus.com/ directly. The articles are available at https://www.protect.airbus.com/blog/the-oxid-resolver-part-1-remote-enumeration-of-network-interfaces-without-any-authentication/ and https://www.protect.airbus.com/blog/the-oxid-resolver-part-2-accessing-a-remote-object-inside-dcom/ , but the images do not work, because they still refer to https://airbus-cyber-security.com/wp-content/uploads/2020/04/...
To prevent such issues, it would be nice to host this blog on a more long-term website, or to update README.md with links to some archives (for example https://web.archive.org/web/20220625011947/https://airbus-cyber-security.com/the-oxid-resolver-part-1-remote-enumeration-of-network-interfaces-without-any-authentication/ and https://web.archive.org/web/20220417063110/https://airbus-cyber-security.com/the-oxid-resolver-part-2-accessing-a-remote-object-inside-dcom/ ). What do you think?

1 ^

Thanks, just saw this issue due to a pull request. I'll get them updated.

Looks like they changed again:

https://www.cyber.airbus.com/the-oxid-resolver-part-1-remote-enumeration-of-network-interfaces-without-any-authentication/
https://www.cyber.airbus.com/the-oxid-resolver-part-2-accessing-a-remote-object-inside-dcom/


Update bundle, cloudwatch, sdk-core, ses, sns, ... to 2.25.32

About this PR
📦 Updates

software.amazon.awssdk:bundle
software.amazon.awssdk:cloudwatch
software.amazon.awssdk:sdk-core
software.amazon.awssdk:ses
software.amazon.awssdk:sns
software.amazon.awssdk:sqs
software.amazon.awssdk:ssm

from 2.25.15 to 2.25.32
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "software.amazon.awssdk" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #3174.


Don't fallback to building from source with HOMEBREW_INSTALL_FROM_API

Fixes https://github.com/Homebrew/brew/issues/13824
We already block --build-from-source when installing with HOMEBREW_INSTALL_FROM_API, but a source install can still be triggered in certain cases (as seen in https://github.com/Homebrew/brew/issues/13824). As soon as we know that this is going to happen, let's fail with an appropriate error message.

Review period skipped due to critical label.


Xcode 12 Carthage update

I just installed Xcode 12, and run the
carthage update --platform iOS Alamofire
I'm getting the following error:
*** Building scheme "Alamofire iOS" in Alamofire.xcworkspace
Build Failed
	Task failed with exit code 1:
	/usr/bin/xcrun lipo -create .../Library/Caches/org.carthage.CarthageKit/DerivedData/12.0_12A7209/Alamofire/5.2.2/Build/Products/Release-iphonesimulator/Alamofire.framework/Alamofire -output .../Carthage/Build/iOS/Alamofire.framework/Alamofire

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/70/r33z6h3x10n3bqxr45td4j080000gn/T/carthage-xcodebuild.qh5jyd.log

Any solutions?

I managed to compile Alamofire following this: https://github.com/Carthage/Carthage/issues/3019#issuecomment-693381253

I managed to compile Alamofire following this: Carthage/Carthage#3019 (comment)

Thank you for the solution.
I tried also this one, and it worked, I did it! 🥳
https://github.com/Carthage/Carthage/issues/3019#issuecomment-664099506


Crop picture to shape

Need to crop pictures to shapes. Specifically a top rounded rectangle
The following is found within a p:pic created by one of our designers:
<p:spPr>
    <a:xfrm>
        <a:off x="4185868" y="1372955"/>
        <a:ext cx="3815133" cy="387350"/>
    </a:xfrm>
    <a:prstGeom prst="round2SameRect">
        <a:avLst>
            <a:gd name="adj1" fmla="val 22122"/>
            <a:gd name="adj2" fmla="val 0"/>
        </a:avLst>
    </a:prstGeom>
</p:spPr>

A possible new API to crop picture:
var pres = new Presentation("pre.pptx");
IPicture picture = pres.Slide(1).Picture("Picture 1");

picture.Crop(left:0.1, right:0.1, top:0.2, bottom:0.2); // Left and Right Crop is 10%, Top and Bottom Crop is 20%

The picture.Crop API noted above would allow for setting the crop frame, which is good. However, it's not enough for this issue. We need to be able to specify the geometry and corner size for this crop also.

Hmm, I didn't know that PowerPoint has feature "Crop to Shape". I think that's what you're talking about:

Yup, that's the one. User can still set the cropping frame, as well as apply preset geometry. And if you choose a rounded rectangle, you'll notice there is a corner size handle as well.

Updated: I now think the clipping frame comes from a:srcRect within the p:blipFill
<p:blipFill rotWithShape="1">
    <a:blip r:embed="rId3">
        <a:alphaModFix amt="20000"/>
    </a:blip>
    <a:srcRect l="59" t="-295" r="19636" b="81332"/>
    <a:stretch/>
</p:blipFill>

Side note: As discussed in #804, the range of the cropping frame should be changed from 0.0-1.0 to 0-100 instead.


How to use cublas in a non-root bazel module?

I'm using rules_cuda in a bazel MODULE A, and some of my cuda_library needs to link with -lcubas and -lcublasLt.
Naturally, I'm defining local_cuda like examples/cublas/BUILD.bazel. . In my MODULE.bazel of module A:
bazel_dep(
    name = "rules_cuda",
    version = "0.2.1",
)

cuda = use_extension("@rules_cuda//cuda:extensions.bzl", "toolchain")
cuda.local_toolchain(
    name = "local_cuda",
    toolkit_path = "",
)
use_repo(cuda, "local_cuda")

And in my BUILD.bazel, I have the cuda_library target:
cuda_library(
    name = ...,
    srcs = ...,
    deps = [
       "@local_cuda//:cublas",
    ],
    ...
)

This works fine when I build my module A. However, when I have another bazel module B that depends on module A, I cannot build module B, because the local_cuda can only be declared in a root module. I got this error:

ERROR: Traceback (most recent call last):
File "/private/var/tmp/_bazel_dev/67de6cda420db4eb86e6ad3f1fd2b6e4/external/rules_cuda~/cuda/extensions.bzl", line 15, > column 21, in _init
fail("Only the root module may override the path for the local cuda toolchain")
Error in fail: Only the root module may override the path for the local cuda toolchain

This is from this line: https://github.com/bazel-contrib/rules_cuda/blob/8f2f2e6d64d38e46d09538c921304c7c902a2564/cuda/extensions.bzl#L15.
Is it possible to use rules_cuda in a bazel module that other modules can depend? I don't really need to customize my cuda path, as the default path works fine with me. Is there a way to avoid the above error?

With current impl, it is not possible.
But it is very reasonable to let upstream projects expose targets that depend on rules_cuda, say, kernels wrapped in a c library with c public interfaces. Current project and downstream projects should be able to use it without pain.
I'll see how we should improve the situation.

Thanks for looking into this! Really appreciated.
Do you mean that my upstream module A uses cuda_library internally, and exposes it with cc_library, and my downstream module B depends on it?
This doesn't seem to work -- it looks as long as I use cuda_library rule in module A, I need to add local_cuda to the MODULE.bazel of module A, and this forces A to be a top-level module.
I tried to remove everything that's referring to local_cuda in module A, so in A's MODULE.bazel file I only have:
bazel_dep(
    name = "rules_cuda",
    version = "0.2.1",
)

and I use coda_library in A's BUILD.bazel file:
load("@rules_cuda//cuda:defs.bzl", "cuda_library")

cuda_library(
    name = "kernel",
    srcs = ["kernel.cu"],
    hdrs = ["kernel.h"],
)

then A cannot compile by bazel. bazel build kernel gives this error:

Analysis of target '//my_project:kernel' failed; build aborted: module extension "toolchain" from "@@rules_cuda~//cuda:extensions.bzl" does not generate repository "local_cuda", yet it is imported as "local_cuda" in the usage at https://bcr.bazel.build/modules/rules_cuda/0.2.1/MODULE.bazel:10:26

This is referring to https://github.com/bazel-contrib/rules_cuda/blob/8f2f2e6d64d38e46d09538c921304c7c902a2564/MODULE.bazel#L10
Adding local_cuda to A's MODULE.bazel would make bazel compile A, but then module B cannot depend on it.

Oh, didn't see a fix is in the making! Looking forward to it 👍

I think its possible to just do:
cuda = use_extension("@rules_cuda//cuda:extensions.bzl", "toolchain")
use_repo(cuda, "local_cuda")

in B's MODULE.bazel which will make local_cuda available to B - its not ideal but I think this works - I have something similar in one of my projects.

yes, this would work to compile B. The problem is that this won't compile A if A has some cuda_library target. This can be annoying, e.g., all the compilation and testing of the cuda code in A now has to be done through module B.

You would leave your A module with the use_repo that you had above. the above snippet makes local_cuda visible in B and you can use cuda_library in A or B.

Thanks for your response! I kind of get it work for my purpose, by using different MODULE.bazel files in my local bazel registry and in the repo_a. Here's a summary of what I have found so far.
My setup:

A bazel_registry folder that serves as my local bazel registry. It has a module repo_a using local_path (https://bazel.build/external/registry#index_registry), so that my repo_b can find repo_a. The bazel registry doesn't serve repo_a's source files, instead it just points to the actual source code directory of repo_a using the local_path feature. Specifically, my bazel_registry contains the subfolder bazel_registry/modules/repo_a/1.0.0 as the registry for repo_a, and especially there is this file bazel_registry/modules/repo_a/1.0.0/MODULE.bazel.

A repo_a, which has the repo_a's source code, BUILD.bazel files, and a different MODULE.bazel file.

A repo_b, which depends on repo_a through my local bazel_registry.

Now this is the complete file content of bazel_registry/modules/repo_a/1.0.0/MODULE.bazel:
"""repo A."""

module(
    name = "repo_a",
    version = "1.0.0",
)

bazel_dep(
    name = "bazel_skylib",
    version = "1.5.0",
)

bazel_dep(
    name = "rules_cc",
    version = "0.0.9",
)

bazel_dep(
    name = "rules_cuda",
    version = "1.0.0",
)

cuda = use_extension("@rules_cuda//cuda:extensions.bzl", "toolchain")
use_repo(cuda, "local_cuda")

This is the complete content of repo_b/MODULE.bazel:
"""repo_b"""

module(
    name = "repo_b",
    version = "1.0.0",
)

bazel_dep(
    name = "bazel_skylib",
    version = "1.5.0",
)

bazel_dep(
    name = "rules_cc",
    version = "0.0.9",
)

bazel_dep(
    name = "repo_a",
    version = "1.0.0",
)

bazel_dep(
    name = "rules_cuda",
    version = "1.0.0",
)

cuda = use_extension("@rules_cuda//cuda:extensions.bzl", "toolchain")

cuda.local_toolchain(
    name = "local_cuda",
    toolkit_path = "",
)
use_repo(cuda, "local_cuda")

This works, and bazel build under repo_b succeeds. Note:

The coda.local_toolchain is declared in repo_b/MODULE.bazel, and not in bazel_registry/modules/repo_a/1.0.0/MODULE.bazel. Adding it to the latter will lead to the " fail("Only the root module may override the path for the local cuda toolchain")" error.

Whether or not bazel_registry/modules/repo_a/1.0.0/MODULE.bazel has the line use_repo(cuda, "local_cuda") doesn't make a difference.

Now repo_b works fine, but I also want repo_a to work, i.e., doing bazel build  under repo_a should succeed. If I use the exact content of bazel_registry/modules/repo_a/1.0.0/MODULE.bazel as repo_a/MODULE.bazel, I will get the following error when I bazel build  under repo_a:

failed; build aborted: module extension "toolchain" from "@@rules_cuda~//cuda:extensions.bzl" does not generate repository "local_cuda", yet it is imported as "local_cuda" in the usage at /home/dev/temp/cuda_test/repo_a/MODULE.bazel:23:21

To workaround this, I need to use a slightly different MODULE.bazel content under repo_a. This is the complete content of repo_a/MODULE.bazel:
"""repo A."""

module(
    name = "repo_a",
    version = "1.0.0",
)

bazel_dep(
    name = "bazel_skylib",
    version = "1.5.0",
)

bazel_dep(
    name = "rules_cc",
    version = "0.0.9",
)

bazel_dep(
    name = "rules_cuda",
    version = "1.0.0",
)

cuda = use_extension("@rules_cuda//cuda:extensions.bzl", "toolchain")

cuda.local_toolchain(
    name = "local_cuda",
    toolkit_path = "",
)
use_repo(cuda, "local_cuda")

Note that I add cuda.local_toolchain in it. This makes bazel build  under repo_a work without any issue. This won't break the build under repo_b, since the latter uses a different MODULE.bazel file for repo_a.
So far I got both repo_a and repo_b work, by leveraging different MODULE.bazel files between the one in my local bazel registry, and the one in the actual repo, to bypass the requirement that toolchains must be defined at the top-level module.
Not sure if this is the canonical way of setting up local dependencies, and it feels like a hack. It will be nice if we can remove the limitation of toolchains declaration, and that avoids all these tricky situations and the MODULE.bazel files won't have to diverge between the one in the repo vs. the one in the bazel registry.
(PS: I'm using the head version of rules_cuda in this GitHub repository. The rules_cuda in Bazel Central Registry https://registry.bazel.build/modules/rules_cuda is 5 months behind the head version here. To avoid confusion I point to the head version of rules_cuda in my local bazel registry as well, and this is why you can see the version of rules_cuda is 1.0.0 above. I also tried the published version 0.2.1, and the result is the same).


SIGINT-2338: Pending items for project sierra migration

Added backward compatibility for checkForIssues step
Updated group ID for jenkins-common and jenkins-annotations-processor
Removed EULA.txt

Added some comments. Kindly have a look.
Also, looking at the code it seems that we will not error out in case there is an error finding the version of the CoP CLI, but we will default to locating the cli-scan.json file under the .blackduck sub directory. This looks good to me. Could you please re-confirm from your end?

Yes that's correct. For error/invalid scenarios the default sub directory will be ".blackduck"


Support popper.js' offset modifier with unstable_offset

Adds support for two-axis offset positioning via an unstable_offset prop. Turns existing single-axis offset positioning (gutter) into a special case of unstable_offset.
Closes #511
Does this PR introduce a breaking change?
No

Thanks for the TypeScript advice. Marking unstable_offset as a readonly tuple allows as const at the callsites, which is much more ergonomic. I also found I was able to assign a type to the unstable_offset default value, which means I was able to stop re-annotating the destructure from useSealedState().
Please let me know if you there's anything else you'd like done before this is good to go.


test:MM-T125 Copy Link can be used from channel LHS

Summary

Ticket Link

Fixes https://github.com/mattermost/desktop/issues/1891
Checklist

[x] Added or updated unit tests (required for all new features)
[x] Has UI changes
[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Device Information
This PR was tested on:
Screenshots

Release Note

NONE

Hello @codedsun,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@M-ZubairAhmed @devinbinnie This is passing on my machine, i am afraid what's causing issue in CI.

Ok this will not pass as teams and channels are not setup in CI. @devinbinnie @M-ZubairAhmed

/update-branch

Yes we do, but I don't think the test user is in the Off-Topic channel by default, so it won't show up in the sidebar. I would try and use Town Square instead

What are the default channels @devinbinnie and how do I see it in code can you refer me?

@codedsun You can generate sample data using mmctl (https://docs.mattermost.com/manage/mmctl-command-line-tool.html#mmctl-sampledata) and those will be the default channels. Town Square always exists unless changed in the DB so that's the channel you can use here.

@devinbinnie I need 2 channels for this right? Also like do we have this file in the project e2e folder?

@codedsun Yes you do, sorry. You can run the sampledata command against your local instance and it'll tell you there.

@devinbinnie Where do I find the file
Upload session successfully created, ID: om6ka364otg68kpb8un8hgc37y
Import file successfully uploaded, name: mmctl-sampledata.zip
Import process job successfully created, ID: qjdm88ybt3dcxmgdjz1fcm3d5o
Sampledata successfully processed

@devinbinnie Finally 🎉

Thanks a lot team 👍 💯


Posted Data doesn't appear in FleetManager

After agent and iot-model (asset) has been mapped I tried to post data. I first tried to do so with PostData() after that I tried BulkPostData. In both cases the function returned true and I didn't receive any errors but the data doesn't appear in the Fleet Manager.
        this.motorSpeed= dataValue1.value.value as number;
        let val = dataPointValues.find(el => el.dataPointId === myId);

        val.value = this.motorSpeed.toString();
        val.qualityCode = 'true';

        const bulkData: TimeStampedDataPoint[] = [
            {
                timestamp: new Date().toString(),
                values: dataPointValues
            }
        ]

        let posted = await myMindConnectLib.agent.BulkPostData(bulkData);

have you taken a look at the diagnostic in the diagnotic app in mindsphere if there is a problem?
the library unfortunately can't know if there is a problem with the mappings b/c the mindsphere endpoint returns 200 ok when the data arrives and the rest of the processing is asynchronous.
https://opensource.mindsphere.io/docs/mindconnect-nodejs/troubleshooting.html#tab1anchor2

Thanks for the advice to use the Diagnostic tool. The data has been dropped due to a invalid timestamp!


Changelog 1.0.0

Merges in master to pull in the changelog from the 0.14.1 release and to fix the imaginary merge conflict in PR #1392
Adds the changelog for the 1.0.0 release. And yes, it's massive..... careful scrutiny appreciated.

I've processed @GaryJones' feedback and added the changes in a separate commit. Commits should be squashed on (or before) merge.

I've processed @JDGrimes' feedback and added the changes in a separate commit. Commits should be squashed on (or before) merge.

Thanks @Ismail-elkorchi for the review. I've processed your feedback and added the changes in a separate commit.
N.B.: Commits should be squashed on (or before) merge.

Anyone up for giving the second approval for this PR ? @JDGrimes ?
No need to merge, I'll squash and merge when doing the release.

Rebased & squashed. Also added a line about the newly merged PR #1430 in the Changed section:
- CI: The rulesets will now also be tested on each change to ensure no unexpected messages are thrown.
Once the builds have passed I'll merge this.


add cv.floodFill, move findHomography to calib3d

fix: #235

add cv.floodFill and cv.floodFillAsync
move findHomography to calib3d

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 97.61905% with 1 line in your changes missing coverage. Please review.

Project coverage is 91.18%. Comparing base (e40c871) to head (cd6a95f).

Files with missing lines
Patch %
Lines

lib/src/calib3d/calib3d.dart
87.50%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #236      +/-   ##
==========================================
+ Coverage   91.14%   91.18%   +0.04%
==========================================
  Files          57       57
  Lines        8478     8506      +28
==========================================
+ Hits         7727     7756      +29
+ Misses        751      750       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


focus style covers up pressed style

Godot version:
3.2.3
OS/device including version:
GLES3 possibly 2 as well
Issue description:
the focus style covers up the pressed style making some gui styles unable to be made
Steps to reproduce:

download project
run Debug.tscn
click on button
realize the focus of the button covers the pressed style

Minimal reproduction project:
FocusBug.zip
Notes:
I have brought up this issue before and it was shut down from people misunderstanding the issue
basically styles for controls should be layered like the following..

normal
focus
hover
pressed
disabled

this assures that people can use transparent styles if needed or opaque styles if needed.
right now its impossible to use opaque focus styles because it covers up everything.
this makes things like a win95 theme impossible

I believe this is done by design. This way, the focus style is still displayed if you press the button (and doesn't magically disappear when you press it).

I honestly think there should be two focus styles.
one for the focus overlay and one for the actual control style
the win32 api does this...

the first one is the normal state, the second one is the focus state, and the third one is the pressed state.
however you can see that I have a focus rectangle drawn over the pressed and focused styles

@Calinou Where should I mention this in the docs? In the StyleBox or Control class reference?

@theoway Probably both for completeness' sake :slightly_smiling_face:

I honestly think there should be two focus styles.
one for the focus overlay and one for the actual control style
the win32 api does this...

the first one is the normal state, the second one is the focus state, and the third one is the pressed state.
however you can see that I have a focus rectangle drawn over the pressed and focused styles
its a hack and is not ideal but its the best I can do in godot right now

I've been searching, but couldn't understand the difference between hover & focus

@akien-mga  This doesn't fix the issue though!
what are we suppose to use for a actual focus style then?
what your using it for is more for a focus overlay not a style
I feel like your ignoring this issue


Add Portable Node.js guide

Practical guide on how to write portable/cross-platform Node.js code: https://github.com/ehmicky/portable-node-guide
There are currently very few guides about this important topic. The only ones covering the topic in full I found are https://github.com/ehmicky/portable-node-guide#further-reading, i.e. only 3 other links.
The guidelines were tested on Windows, Mac and Linux.
By submitting this pull request, I promise I have read the contribution guidelines twice and ensured my submission follows it. I realize not doing so wastes the maintainers' time that they could have spent making the world better. 🖖 yes I did.

Very useful!

Thanks!
@sindresorhus You have many projects aimed at solving lack of cross-platform support in Node.js. Actually many links in that guide are of your projects. Your knowledge in that area might be very useful to other developers and help them improve by writing more cross-platform Node.js.
So if you wanted to spot any errors or missing information in that guide, your feedback would be very appreciated!

Sure, I will take a closer look when I have some time and do a PR if I see anything to improve.


Provide access to request from HttpRequestBody

With code like this:
        ..serve('/register', method: 'POST')
          .transform(new HttpBodyHandler()).listen(registerPlayer)
The registerPlayer callback only gets a HttpRequestBody. There's no getter for request in HttpRequestBody. I need to set something in the session, for example.

This issue has been moved to dart-lang/http_server#9.


Use_amp:true causes  Nan

Hello, when I set use_amp to true I am getting  "SILog is NaN, Stopping training" after some batch
Nan SILog loss input: torch.Size([651751]) target: torch.Size([651751]) G tensor(2284, device='cuda:0') Input min max tensor(nan, device='cuda:0', grad_fn=<MinBackward1>) tensor(nan, device='cuda:0', grad_fn=<MaxBackward1>) Target min max tensor(3.8516, device='cuda:0') tensor(226.5352, device='cuda:0') Dg tensor(True, device='cuda:0') loss tensor(True, device='cuda:0')
Do you have any idea how to fix this

I encountered NaN problem when I tried to support fp16 inference.
The cause is that some of MiDaS outputs are very large values, and that turns into inf in float16.
A workaround is to clip MiDaS output within float16 range.
https://github.com/nagadomi/ZoeDepth_iw3/commit/384f3255157a8613793b72aaed1669fa7a38258a
Also, running DPTDepthModel.head with float16 degraded the accuracy, so it was better to use float32 for that one.
https://github.com/nagadomi/MiDaS_iw3/commit/2e398c9ad51b9aa262b4c6c3e181c1aa95dcd8ef
Note that I tried this only for inference.
--use_amp 0
{'a1': 0.954, 'a2': 0.995, 'a3': 0.999, 'abs_rel': 0.075, 'rmse': 0.27, 'log_10': 0.032, 'rmse_log': 0.095, 'silog': 7.034, 'sq_rel': 0.03}
654/654 [02:27<00:00,  4.42it/s]

--use_amp 1
{'a1': 0.954, 'a2': 0.995, 'a3': 0.999, 'abs_rel': 0.075, 'rmse': 0.271, 'log_10': 0.033, 'rmse_log': 0.095, 'silog': 7.039, 'sq_rel': 0.03}
654/654 [01:50<00:00,  5.90it/s]


Backport dashboard proxy to 1.18

@joedborg this PR does not do anything in the installer, just adds the dashboard proxy.


Asciinema presentation will be archived

When clicking on the asciinema video, there is a warning about the future archiving of this video, end of january 2019.
https://blog.asciinema.org/post/archival/

It says "This recording has been archived" now. Would be great to have the video re-uploaded and claimed :+1:


Issues in en-GB dictionary

We are facing issue in “en-GB” dictionary, there we couldn’t find the word “ability” in aff file. So, the issue occurs all the words related to the word “ability” in suffix. So, can you please provide the definition for that or any other alternative solutions.

This project compiles many dictionaries from many sources. Qs can go to the original sources.
Furthermore: affixes are not words.


Fail to start api for todo-python-mongo when default terminal is bash in Windows

Describe the issue:
In Windows, when the default terminal is bash, starting the api fails and the terminal reports the following error message:

Repro Steps:

Login in with command: azd auth login.
Execute command: azd init -t todo-python-mongo -b staging or azd init -t todo-python-mongo -b pr/3976 .
Run azd up.
Hit F1 -> Run Task -> Start API.

Environment:

Template: todo-python-mongo
Branch: staging or pr/3976
OS: Windows
Azd version: azd version 1.10.0-beta.1-daily.3947259 (commit 5bf8568b1566723be8bc2259c578df4f931cf430)

Expected behavior:
The api can be successfully started when the default terminal is bash in windows.
@jongio for notification

Do you mean the default VS Code terminal is bash?  Is that a project setting?  In Windows it would be Git Bash, not bash directly.

Do you mean the default VS Code terminal is bash? Is that a project setting? In Windows it would be Git Bash, not bash directly.

@jongio The default VS Code terminal is not Git Bash. When it is changed to Git Bash, this issue will occur. This is not a project setting.
In Windows, should we consider both pwsh and Git Bash to support running command tasks? Or is just pwsh enough?

@rajeshkamal5050 Is there someone that can help figure out what is happening here?

@rajeshkamal5050 and @jongio In the latest round of azd manual testing, this issue still exists.

Template: todo-python-mongo, todo-python-mongo-terraform.
Branch: staging.
OS: Windows.
Azd version: azd version 1.10.3-pr.4243081 (commit 2c05c152915bdfd82e20d3350f249b22accd3deb) and azd version 1.11.0-beta.1-daily.4244391 (commit 8fc9d80640aa6f45f1a7d7631087c4a5f54e9e63).


Install cancelled by user

I'm obviously no expert, so I'm not going to be able to provide much details about the problem. I've enabled developer settings “USB Debugging”, “USB Debugging (Security Settings)” and “Wireless Debugging”, but it still doesn't seem to work. Is there anything else I have to do?

(The apk is incompatible with my device, and I've been told this app would help with it.)

You can try enable "Install via USB"

You can try enable "Install via USB"

I was getting the same error and enabling this worked for me.


Improve the implementation of the Node.toString() method

We are working on a new syntax tree API with the new parser implementation. This tree model maintains everything in the source code, even the minutiae of nodes such as newlines, comments, and whitespaces. Therefore you can always get the original source text from the syntax tree.
TextDocument textDocument = TextDocuments.from("function add(int a, int b) returns int {return a + b;}");
SyntaxTree syntaxTree = SyntaxTree.from(textDocument);
ModulePartNode modulePartNode = syntaxTree.modulePart();
System.out.println(modulePartNode);

The implementation of the current toString() method is a sub-optimal one that creates StringBuilder instances recursively when descending the tree. Ideally, we should be using a single StringBuilder instance.
https://github.com/ballerina-platform/ballerina-lang/blob/b43871b5d3987742df7f0d4b635fa61c310dcc64/compiler/ballerina-parser/src/main/java/io/ballerinalang/compiler/syntax/tree/Node.java#L128

Lets create a singleton in STNode
https://github.com/ballerina-platform/ballerina-lang/blob/b43871b5d3987742df7f0d4b635fa61c310dcc64/compiler/ballerina-parser/src/main/java/io/ballerinalang/compiler/internal/parser/tree/STNode.java#L86


Sorry, that didn’t work. Try again? Appears for Shortcut event after sending ack and temp message ephemeral

I am looking for documentation on Posting as Ephemeral for Slack Shortcut i am seeing a unusual behavior, either my understanding is wrong or something i am missing

I am using the latest BoltJS SDK with AWS lambdaReceiver
Here is my listener code shortcut

const {ack, payload, body, client} = args;
ack(); // Avoid await to avoid wait time

const channelID = body.channel.id;
const messageTS = body.message.ts;

const result = await getConversationsInThread(client, channelID, messageTS);

// ephemeral Message as temp message to avoid 3 sec delay
// Avoid await again to avoid wait time
postAsOnlyVisibleToUser(client, channelID, userId, messageTS, 'Working  .... ');

const response = await callTimeConsumingService(result);

return await postAsOnlyVisibleToUser(client, channelID, userId, messageTS, response);

In My slack i am getting this UX in bottom corner Sorry, that didn’t work. Try again?  Between temporary message and response message
My Understanding,

ack should send 200 status, so slack shouldn't wait for 3 sec after ack is received.
if my understanding is wrong about ack and 3 sec, then by posting ephemeral message how slack knows still another message is coming?
To double confirm Sorry, that didn’t work. Try again?  is not due to error response i checked my logs, i didn't see any error.

Hope i gave enough data points.
It will be great if you could provide an explanation why this UX appears every-time after temp message got posted and before real message posting.
Reproducible in:
The Slack SDK version
"@slack/bolt": "^3.12.2",
Node.js runtime version
16
OS info
AWS cloud
Steps to reproduce:
(Share the commands to run, source code, and project settings)

Expected result:
(Tell what you expected to happen)
Actual result:
(Tell what actually happened with logs, screenshots)
Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @sanjay1909 - Hm I am wondering whether this behavior is due to your app being deployed in Faas environment, in this case AWS Lambda. I can't tell from your code whether you're using the AWSLambdaReceiver. If not, then it seems as though you might need to set processBeforeResponse property to true in receiver options.
This option will defer sending back the acknowledgement until after your handler has run to ensure your function isn't terminated early by responding to the HTTP request that triggered it.

Edit: I do see know that you mentioned AWS lambdareceiver, so processBeforeResponse is set to true by default. However, I do see that you have in your code:
const response = await callTimeConsumingService(result);

Note:  ack() in this case is being deferred to AFTER you're done with your handler processing. That's in place to avoid lambda shutting down too early. So that means that you still have a total of 3sec to complete all your work including the above time consuming service. You're probably seeing the ephemeral message post just fine, BUT the bolt app isn't sending the 200 OK in the time frame Slack expects because your function is still awaiting a later expensive async call.

Hi Sarah, this make sense   the ack() in this case is being deferred to AFTER you're done with your handler processing why i am getting the UX error. Thank you
I was thinking about using response_url for these time consuming process. But i noticed its not part for shortcut args either.
If i understand correct

moment deferred ack gets invoked after the handler, lambda terminates.
So even if i use app.use() to call ack and
call next() where i handle the shortcut in next middleware wont be working, as ack would terminate Lambda

@sanjay1909 - Yes, this is a difficulty of working in the FaaS environment. Basically, if you have some time-confusing tasks in response to Slack events, your app needs to have an asynchronous execution mechanism (say, have a queue for your tasks, or invoke a different offline service to run long operations, etc).
From looking into out of the box alternative options here a little more, bolt-python does offer a Lazy Listener feature, which lets developers to more easily run the longer functions with Bolt listener arguments.
As best I understand, we are not planning to implement the same functionality in bolt-js at this time, due in large part to a limitation in the bolt-js framework design.
I'm afraid I don't have an out-of-the box workaround for you in this, but hopefully that's some context and directions to consider in terms of getting around the FaaS difficulty.


[feature] Add capability to download and extract files

I'm working on photomaps and would like to be able to download files and extract it to a location.
Github repo: https://github.com/protomaps/basemaps-assets/
Here is the file I would like to download: https://github.com/protomaps/basemaps-assets/archive/refs/heads/main.zip
  download_basemaps_assets:
    url: 'https://github.com/protomaps/basemaps-assets/archive/refs/heads/main.zip'
    outputs: 'dest_dir/basemaps-assets.zip'

  extract_basemaps_assets:
    deps:
      - download_basemaps_assets
    zip: 'dest_dir/basemaps-assets.zip'
    outputs: 'public/basemaps-assets'

It is possible to have a native task in moon to download and extract zip and tar.gz files as OS might not have curl/wget or unzip/tar installed by default.

In 1.20, you can now download using extensions: https://moonrepo.dev/docs/guides/extensions#download
However, unpacking isn't a thing. WASM doesn't support file permissions, so this isn't possible right now.

Hit another use case where I needed to use pdfjs. Their npm package contains the javascript libs but doesn't ship with viewer.html files.
https://www.npmjs.com/package/pdfjs-dist
Have to manually download from https://mozilla.github.io/pdf.js/getting_started/#download which is a zip file.
Might be using something like wasm-flate can be useful here.

The problem is that WASM doesn't support file permissions, so I'm not sure how wasm-flate gets around that. Or maybe it just ignores it entirely.

You could expose partial WASI. Specifically the WASI FileSystem apis.

We use WASI but Rust only supports the preview1 spec, which doesn't support permissions. We'll have to wait for the next spec to land.


adding import image from url

you can use this function to grab images by url and store it. You just need to invoke the importFromUrl with an url or set of urls and that's it :)

Thanks for your contribution.
However at the moment I won't include this functionality, as I think it's rather out of scope of this project.

omg

No need to freak out, you know you can always continue to maintain your code in your own fork.

that's true bat what's going on with the current?

Are you referring to the security patch?
This refers to this patch here:
https://github.com/blueimp/jQuery-File-Upload/commit/5ee639504cb144aba4d04c9379fa670ed4ff8c44
Please also refer to my comment here:
https://github.com/blueimp/jQuery-File-Upload/pull/3381#issuecomment-69641256

that's cool, I mean the security, but I didn't get how does it relate to this patch


vacuum-go: 0.11.1 -> 0.12.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/daveshanley/vacuum/releases.
meta.description for vacuum-go is: The world's fastest OpenAPI & Swagger linter
meta.homepage for vacuum-go is: https://quobix.com/vacuum
meta.changelog for vacuum-go is: https://github.com/daveshanley/vacuum/releases/tag/v0.12.0
Updates performed

Golang update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.12.0 with grep in /nix/store/93c47yb136c9753fjil333hjra6m7mcy-vacuum-go-0.12.0
found 0.12.0 in filename of file in /nix/store/93c47yb136c9753fjil333hjra6m7mcy-vacuum-go-0.12.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

vacuum-go

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/93c47yb136c9753fjil333hjra6m7mcy-vacuum-go-0.12.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A vacuum-go https://github.com/r-ryantm/nixpkgs/archive/6406037ebdd7226f54db63ed2c817d82d4dc8ae6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6406037ebdd7226f54db63ed2c817d82d4dc8ae6#vacuum-go

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/93c47yb136c9753fjil333hjra6m7mcy-vacuum-go-0.12.0
ls -la /nix/store/93c47yb136c9753fjil333hjra6m7mcy-vacuum-go-0.12.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

vacuum-go

Maintainer pings
cc @konradmalik for testing.

Result of nixpkgs-review pr 332897 run on x86_64-darwin 1

1 package built:

vacuum-go


TILA-620 | Application status api mass edit bugfix and some minor refactor

Stumbled on some flickering test for capacity and I skipped them for now. Fixing those in separate PR since in this the main bug fix is urgent for UI.


Add FindChoiceOptions.NoIndex

At the moment in ConfimrPrompt the second attempt (based on ChoiceRecognizers) is made only if ChoiceOptions's IncludeNumber is true. So if it's false there won't be a chance to recognize the choice based on its synonyms.
I think this option (NoIndex) naturally complement the existing NoValue and NoAction options.

@stevenic can you comment

Thanks for the PR but we don't want to extend the behavior of the core prompts at this time. They are only intended as basic prompts. It is relatively easy to write your own custom prompts and we plan to improve the samples and docs around how to effectively do that.
We also need to write unit test and port this to Node, Java and Python.
There is also significant work being done around making dialogs easier to author all up. Plus we have just done a significant rev on the samples repo.


Fix ecosystem partners table

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR removes the import of Table from lucide-react in partners-table.tsx.
Detailed summary

Removed import of Table from lucide-react in partners-table.tsx

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#4508  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MananTank and the rest of your teammates on  Graphite


[BEAM-14103][Playgrounf][Bugfix] Fix google analytics id

Fix google analytics id

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Rename  google analyze  id account

LGTM thanks!


Databrew job error handling in S3 trigger workflow

Issue #, if available:
If a brew job is triggered while another job is running, state machine execution (States.TaskFailed) fails as DataBrew only allow one running at a time for a particular job.
Description of changes:

Add DataBrew job error handling in S3 trigger workflow

The Launch Brew Job task catches States.TaskFailed error, then enter Databrew Job Fail Notification task to send a databrew job fail notification email.

Add unit tests for S3 trigger workflow

Test generated template

S3 trigger workflow behaviour for Launch Brew Job task:

If brew job is successfully launched, enter Databrew Job Done Notification task sending a databrew job is done email. If brew job is fail to launch, enter Databrew Job Fail Notification task sending a databrew job is fail email. In both case, the workflow finally enter Pass and mark its execution status as succeed.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Since we're expanding our use of SNS notifications, can we consider setting some message attributes that will help subscribers filter and process these? This would be in addition to the message we're already sending.
https://docs.aws.amazon.com/sns/latest/dg/sns-message-attributes.html
We can set an attribute to specify an error or successful result. Maybe a subscriber is only concerned with errors. Or, an attribute that indicates the source component of the SNS within our solution, like "Inbound", "Transform", and "Outbound" for example. I would like to read your suggestions on adding these.

Thanks Jim, it's a great idea to add message attributes.
Subscribers could assign a filter policy to receive the messages they interested in, like success ones or fail ones.
The notifications (SnsPublish) in s3 trigger workflow are triggered by invoking a brew job successfully or fail to invoke (async_callback sends invoking brew job task results). So we can indicates the source component is databrew and reason is a job is running.


"Timer with event" nodes defaulted after 1.7 update

Possible cause: node name for "timer with event" changed to "timer with volume event", making them reverting to default.
Folly.zip

Obsolete and most likely fixed


Unknown error still persists (others closed by bot for nothing)

Version of flutter_inapp_purchase
2.3.2 and 2.1.5 give the same results
(flutter 1.22.x)
(iOS 13.3.1)
Platforms you faced the error (IOS or Android or both?)
iOS did not test Android
Expected behavior
To handle purchase
Actual behavior
Throw unknown error
Tested environment (Emulator? Real Device?)
Real device hooked to a computer. Testflight or App center not tested!
Steps to reproduce the behavior
1. Run
await FlutterInappPurchase.instance.initConnection;
2. Run
await FlutterInappPurchase.instance.getSubscriptions(
productIds,
);
OR
await FlutterInappPurchase.instance.getProducts(
productIds,
);
3. Run
await FlutterInappPurchase.instance.requestSubscription(
productId,
);
OR
await FlutterInappPurchase.instance.requestPurchase(
productId,
);
They both yield the same results:
responseCode: null, debugMessage: SKPaymentTransactionStateFailed, code: E_UNKNOWN, message: An unknown or unexpected error has occured. Please try again later.

Facing the same issue. 😥

This seems to be a device-specific issue. Try reset settings and use a new tester account. Should work fine after that.

Although it was stated in the issue I want to leave a note for my future self:
In app purchases only work on a real device. Not a simulator!

@saarikivit  Also please check that you've signed all Paid Apps agreements on App Store Conect: https://appstoreconnect.apple.com/agreements/#/
I was facing lots of errors until I realized that I haven't signed agreements. Hope this helps!

@saarikivit  Also please check that you've signed all Paid Apps agreements on App Store Conect: https://appstoreconnect.apple.com/agreements/#/
I was facing lots of errors until I realized that I haven't signed agreements. Hope this helps!

Well... I was facing the same issue for weeks. I've started using flutter_inapp_purchase (where I found this error) and then I've migrated to in_app_purchase (where I another error with UNKNOWN_ERROR_CODE). It seems that both packages's errors are the same. They are related with the test enviroment...
I've solved this by registering an account on the sandbox test environment of the app and testing the purchase with this account. I've NOT tested this in flutter_inapp_purchase... but I really think they are related
Hope it helps

Well... I was facing the same issue for weeks. I've started using flutter_inapp_purchase (where I found this error) and then I've migrated to in_app_purchase (where I another error with UNKNOWN_ERROR_CODE). It seems that both packages's errors are the same. They are related with the test enviroment...
I've solved this by registering an account on the sandbox test environment of the app and testing the purchase with this account. I've NOT tested this in flutter_inapp_purchase... but I really think they are related
Hope it helps

@saarikivit  Also please check that you've signed all Paid Apps agreements on App Store Conect: https://appstoreconnect.apple.com/agreements/#/
I was facing lots of errors until I realized that I haven't signed the agreements. Hope this helps!

These were not the problem as I had a same-kind-of working setup with revenuecat's package: purchases_flutter.

@saarikivit  Also please check that you've signed all Paid Apps agreements on App Store Conect: https://appstoreconnect.apple.com/agreements/#/
I was facing lots of errors until I realized that I haven't signed the agreements. Hope this helps!

These were not the problem as I had a same-kind-of working setup with revenuecat's package: purchases_flutter.

With sandbox and debug I do not have this error.
However I can't pass App Store review, because they get this error for some reason


feat : polish entity specification to make more dynamic and scalable

Summary by CodeRabbit
Release Notes

New Features

Introduced a new utility class for managing filter attributes and dynamic query generation.
Added support for various query operators in building predicates for JPA criteria queries.

Improvements

Upgraded the PostgreSQL Docker image version for enhanced performance and security.
Enhanced application properties for better thread management and connection pooling.

Bug Fixes

Removed deprecated properties to streamline configuration.

Refactor

Restructured the ActorService for clearer dependency management and specification building.
Updated the implementation of the EntitySpecification class for improved dynamic query capabilities.
Updated the FilterAttributesProvider to optimize filter attribute management.

@coderabbitai, can you please summarize about these changes and module


How difference value is calculated

For tumor-only mode, how difference in the output file is calculated for each locus?
Thank you!

For each locus, we use the information entropy theory to perform microsatellite instability analysis.
Thank you!


Datastore does not preserve dependency_info

When saving a CompatibilityResult to datastore, dependency_info is required/included to the save, but when reading from datastore, the dependency_info field of the resulting CompatibilityResults are not set.

Just curious, are we still using datastore in the latest version of the badge server?

Yes we are.

Per offline discussion, dependency_info is stored in the release_time_for_dependencies table in our MySQL database. And the issue here is that the save_compatibility_statuses function in compatibility_store is writing data to all the three tables we have in MySQL, thus it required dependency_info in the CompatibilityResult passed in to that function. But when writing tests, in some cases the CompatibilityResult doesn't contain the dependency_info, which makes the read and write to MySQL looks inconsistent.
A possible improvement could be restructure the save_compatibility_statuses function to split to three sub methods that writes to the three different tables.

Thanks for the explanation!


[Task]: Handle Empty regex in Ballerina

Description

[] #39795
[] #39794

Describe your task(s)
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

So the discussed plan is to handle empty regex in following way.
Scenario 1
public function main() {
    string:RegExp b = re ``;
}

This will gives a compile time error. Ballerina will not allow to define empty regex in compile time.
Scenario 2:
public function main() {
    string a = "";
    string:RegExp b = re `abc${""}`;
    string:RegExp c = re `abc${a}`;
}

These codes are handle in runtime. The regex pattern will replace with non capturing group in runtime.
So the runtime convert abc${""} to ?: and execute the code.

The first task is addressed in #39848.

Fixed in #39848


Tweaks for periodic commands (allow periodic command without predefined channel)

I've mentioned this in the original JIRA plugin issue to some degree - I am planning (one final) feature that would query JIRA for issues that were created/resolved in given project and announce them to a channel.
To do this I was planning to use periodicCommands. However - looking at the code the way they work means the JIRA query would be run for every channel (even if multiple channels receive notifications of the same project).
What I would instead like to do is have a periodicCommand (v2?) that runs the queries (in JIRA case configured by ENV vars) and can send a message to any channel depending on which new/resolved issues it found.  I was thinking of doing something like this:
// PeriodicConfig holds a cron specification for periodically notifying the configured channels
type PeriodicConfig struct {
        Version     int     <---- NEW
        CronSpec string                               // CronSpec that schedules some function
        Channels []string                             // A list of channels to notify
        CmdFunc  func(channel string) (string, error) // func to be executed at the period specified on CronSpec
        CmdFuncV2 func() ([]CmdResult, error) <--- NEW
}

And of course, tweak the bot.go to account for this so that when V2 func is called it will send all messages. There are other ways to do this of course so before I go down that road - any preferences/ideas?

Thanks for merging. I'll close this one out then


Add support for caching SdkRunnableTask

TL;DR
Add support for caching SdkRunnableTask
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
This PR should enable caching in java/scala implementations of SdkRunnableTask.

#122 was merged, so this PR is not needed anymore


First stab at a grammar definition

@lee-dohm I took a pass at converting some of the examples over to this syntax to see what it would look like. You want to check it out and see if that matches what you had in mind?

Tossing an idea out there, I'm more of a fan of YAML. I know you looked at this previously, but I wanted to incorporate some of the ideas from here.
- Require use of issue template:
  - on: issue
  - when:
    - opened
  - if:
    - any:
      - body !matches /### Prerequisites.*### Description.*### Steps to Reproduce.*### Versions/
      - body matches /- [ ]/
  - then:
    - comment from "https://github.com/atom/issue-triage/blob/master/.github/MISSING_ISSUE_TEMPLATE_AUTOREPLY.md"
    - label with "insufficient-info"
    - close

- Post welcome message for new contributors on issues:
  - on: issue
  - when:
    - opened
  - if: #defaults to any for top-level
    - first_time_contributor #implemented via plugin
  - then:
    - comment from https://github.com/atom/issue-triage/blob/master/.github/MISSING_ISSUE_TEMPLATE_AUTOREPLY.md;

The examples are a bit more verbose, but I find it easier to visually parse then natural language.

After experimenting and exploring some options this week, I decided to go with JavaScript for configuring the bot. It's not without tradeoffs, but I feel like that will be the most flexible for now.
Thanks to @mcolyer for doing the initial implementation of the JS API in #58
As patterns for configuring the bots emerge, maybe we can re-introduce a higher-level language.


loadBalancerIP in service - Kibana

Describe the feature:
Add loadBalancerIP in service for Kibana. This feature was added for Elasticsearch but not Kibana.
Describe a specific use case for the feature:
I use loadBalancerIP to specify static load balancer IP address using GCP internal load balancing. This internal IP address will be added as a record in CloudDNS to allow connection in private VPC.

Hi @alexgordonpandera,
Thanks for submitting this request.
LoadBalancerIP was implemented in #539 for Elasticsearch.
Would you be interested to create a PR based on #539 for Kibana?

/assign
Can I work on this issue? If it is not merged.

Closed by #726


New branch

Q
A

Is bugfix?
yes/no

New feature?
yes/no

Breaks BC?
yes/no

Tests pass?
yes/no

Fixed issues
comma-separated list of tickets # fixed by the PR, if any

@CedricYii
I changed my mind since yesterday night. I apologize but after trying, with an open mind, to come to you way of translating, I found things more confusing and I could not resolve myself to do that way. It is above my strength.
I admit that class names should no be translated at all, and it is what I did (never translated class name), but when referring to the concept of Active Record, I don't understand why I could not translate it. Being consistent with you point of wiew I could never call a query requête, or a model modèle and I think things turn out to be a little crazy.
The only important thing in my opinion is to help the reader localize Active Record if he is used to using the English word when thinking. Thus I keep a reference to Active Record in the title of the section.

As I said, it is difficult to change one's opinion on translation.
However note that you are not always complying to your own rule as in:
1. Créer un nouvel objet *query* (requête) en appelant la méthode [[yii\db\ActiveRecord::find()]] ;
2. Construire l'objet *query* en appelant des [méthodes de construction de requête](db-query-builder.md#building-queries);

Or
La seule différence est que, au lieu d'utiliser l'opérateur `new` pour créer un objet *query* (requête), vous appelez la méthode [[yii\db\ActiveRecord::find()]] pour retourner un nouvel objet *query* qui est de la classe [[yii\db\ActiveQuery]].

In my opinion these two extracts are offering an excellent useful easy to understand and to follow translation. Unfortunately they are not consistent with the other sections.
Anyhow, I appreciate your work on this translation and I hope it will be useful for newcomers.

I will sleep a while on it and then see. Thank you for your comments


Storage path name problem in restart

We try to use emqtt in kubernetes with glusterFs by using storage_type=disc but folder is created differently as 'emqtt@' in restart of service because Ip address changes.
So we try to give IP address as <IP_ADDRESS> so that it would be same after every restart but still we cannot use retain folder after reboot,
Is there something we are doing wrong or is there a way to reuse retain messages on restart of emqtt

We do not recommend storing messages on disk in kubernetes.

my colleague have recently managed to store in disk via GlusterFs and was able to recover after recreating statefulSet, can you elaborate why you do not recommend this, what problems can we encounter?

First, in kubernetes, if you want to save the message to disk in emqx crash, you only need to save the last crash pod, but you can't know which pod will crash in advance.
Second, if you want to reuse the reserved message when you restart emqx, you must ensure that the information such as nodeName is the same, but the IP of each pod in the kubernetes deployment is different, so the consistency of nodeName cannot be guaranteed.
So, if you want to keep messages in kubernetes, you can bridge to third-party services, or use our enterprise version of the solution, emqx Enterprise Edition supports mysql, pgsql, mongoDB, kafka, redis and other message storage solutions
In addition, this is my understanding, if your colleagues have a better solution, welcome to share with us.

I learnt that he made it possible by giving dns name provided by kube-dns which resolves into internal IP of emqtt pod, we couldnt produce emqtt pod crash case otherwise it works very well, thanks for the help


_apply_theme problem?

Hey there,
Was wondering if you could help me. When I use the package I end up having an issue where the statusline disappears sometimes and other times it stacks on itself after a few seconds (so I have multiple status lines covering the bottom part of my screen. I've isolated the issue to within the _apply_theme but am not sure how to move forward since I'm not even sure what's happening. It's probably related to status line but I think there might also be issues with just the encoding and all that

Why OS and which version of tmux are you using?

I'm using arch Linux and my tmux is 2.3-1 from the official repository

If you can, I would appreciate a video or gif of what's going on.
I didn't put energy into circling down what's going on exactly yet, but likely it's tied to Unicode symbols (see other issues). Typically on my mac, U+2328 consumes the width of 2 "regular characters.
What you can try is removing those from your .tmux.conf.local copy. (see the non-unicode-symbols branch). This should solve your issue while giving you a slightly less cool status bar.
Keep me posted.

Hey thank you :) The non-unicode-symbols branch helped me debug. Turns out it was a problem with rendering
#tmux_conf_battery_status_charging='⚡'     # U+26A1
#tmux_conf_battery_status_discharging='🔋'  # U+1F50B
Thank you so much for your help!

Good to know. I'm still unsure who's responsible for the breakage: tmux, VTE, else?
Are you using Termite by chance?

I am not. I'm using terminator if you know of it.
I'm really not sure unfortunately

I know terminator. It's a bit redundant with tmux :) On Archlinux I'm using terminology-git

BTW, can you please take a screenshot of U+1F50B and  in y U+26A1 in your setup? Does any of the two take more than 1 character when displayed?

Sorry what does that mean? I tried pasting that into the terminal and it just popped up as the code. I'm a little new to this.

E.g. a screenshot of cat ~/.tmux.conf.local | grep charging

Alright it looks like U+26A1 (charging) puts the rendering off. It's a VTE problem, see https://bugzilla.gnome.org/show_bug.cgi?id=772812#c7

I tried it I think both of them are broken :p I'll close the issue now anyways. Thank you so much for your help!


Add Windows and Mac Os to tests

So we'll find problems faster for that OSes.
I think that will be good to also add test for each event-loop system(event, swoole, revolt, ...)

Seems that exist a problem with Guzzle

It's working, but it'll fail in the future.
I'll try to fix it.

@walkor if you want, you can merge it in another branch, till we fix the code or tests.

In Mac only fail the UdpConnectionTest.
In windows can't install posix and pcntl, and it's normal

And 5 failed tests.

@walkor you can check the Adapterman tests working with Ubuntu, MacOS and Windows.
https://github.com/joanhey/AdapterMan/actions/runs/6094582441/job/16536405869#step:5:11


Add grpc.default_authority option for authorization

Some hostie server don't use different port for service,It can use the authority to identify user.

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

I can use the authority to identify current user in gRPC server.

Yes, I understand that we can use the authority to identify the current user in the gRPC server.
Could you please confirm that, does this new feature will introduce any breaking changes from our previous version?

const puppet = new PuppetHostie({ endpoint:'localhost:7777', token:'2615f5b7498c80406a27bed8d411ddfd' })

Yes, I understand that we can use the authority to identify the current user in the gRPC server.
Could you please confirm that: does this new feature will introduce any breaking changes from our previous version?

Because the default gRPC server ignore the option, it can't break any previous version.

Thank your very much for the recommendation, and it is great to know that this new feature will not break any previous code!
I'd love to merge this great new feature to the grpc service for testing. However, could you please add some documentation to our README so that other developers will be able to learn this new feature easily?
We will merge this PR after it is documentated, appreciate for your effort for make this module better!

I had added some documentation for  version 0.10.4.

Merged. Cheers!

@huan Thank you very much!Now bot can use the version 0.10.4  to connect our new gRPC server.The examples/ding-dong-bot works well!!!! Cheers!

BTW: it will be better if we can create an issue for any pull requests, and then link all related issues/prs to that issue, instead link to a Pull Request.
Because the issue is created for discussing the problem, but the PR is created for discussing the specific code.


Two-to-one aggregation circuits

Add two circuits to AllRecursiveCircuits:

two_to_one_aggregation that aggregates two unrelated aggregation proofs.
two_to_one_block that aggregates two unrelated block proofs.

For the record, I am actually developing on this branch: https://github.com/0xPolygonZero/zk_evm/tree/two_to_one_aggregation_local_friendly


Trait code failing when using bit vector type

When using bit vectors in Trait, the Dafny compiler throws an exception.
Bug report (and example) created see issue 549

Fix in [commit] (https://github.com/RustanLeino/dafny/commit/0663186211bcf2d7792e9e1e182459f72be6266d)


Add examples

Work is currently being done on the shapes for WebID Profiles, and in this regard it's useful to have some examples to compare against.
I propose at least two examples:

Minimal: No optional fields, only required fields with the least complex values used
Maximum: All optional fields used, with all shapes of values used

In addition, it might be useful to have some variants that cover some alternative shapes for values (if applicable - I don't have a complete overview of what a profile might contain).

I've realized that I'm not able to prioritize this task anytime soon, so I'm posting this in hope that someone else have the time and knowledge to take this task on. If not, I'll try to get to this in the future, but no promises on when.


using relative directory as dags_folder no longer works in Airflow >= 1.7.0

Dear Airflow Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Version of Airflow: 1.7.0
Airflow components and configuration: running a scheduler with local executor
Example code to reproduce the bug:
airflow.cfg:

[core]
airflow_home = ~/airflow
dags_folder = dags

Operating System: Linux ubu91 3.13.0-83-generic #127~precise1-Ubuntu SMP Fri Mar 11 12:53:08 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Python Version: Python 2.7.3

Now that you know a little about me, let me tell you about the issue I am having:
Description of Issue

What did you expect to happen?

When I configure a relative path as dags_folder in airflow.cfg, I expect dags in this folder to be found, scheduled, and executed, as it used to be the case in Airflow 1.6.2.
Or, at the very least, if relative paths are not supposed to be used, this should be documented and an error message given that the configuration is invalid.

What happened instead?

The dags where found and scheduled, but the execution failed. The command the scheduler passes to the executor seems to be confused by the relative path and mixes things up, resulting in a wrong path to the dag passed to the executor. I find the following in the scheduler output:
[2016-04-06 14:44:31,680] {sequential_executor.py:27} INFO - Executing command: airflow run notify_wsgi notify_wsgi 2016-02-26T14:56:01.750588 --local -sd DAGS_FOLDER//home/PHI-TPS/amerkel/airflow/dag.py
[2016-04-06 14:44:32,058] {__init__.py:36} INFO - Using executor SequentialExecutor
Traceback (most recent call last):
File "/home/PHI-TPS/amerkel/venv/airflow/bin/airflow", line 15, in <module>
    args.func(args)
  File "/home/PHI-TPS/amerkel/venv/airflow/local/lib/python2.7/site-packages/airflow/bin/cli.py", line 167, in run
    raise AirflowException(msg)
  airflow.utils.AirflowException: DAG [notify_wsgi] could not be found in /home/PHI-TPS/amerkel/airflow/dags/home/PHI-TPS/amerkel/airflow/dag.py

(please note the duplication of the home directory in the path given in the last line of the traceback)

Here is how you can reproduce this issue on your machine:

Reproduction Steps

configure dags_folder using a relative path
put a DAG in the folder you configured
run airflow scheduler

To be honest I'm not sure if we have ever "officially" supported relative directories. It's a messy proposition given that Airflow uses many subprocesses in its execution and while they will probably share a working directory, I'm not sure that's guaranteed. In any case git bisect shows the commit that broke it was 8f06cf8 by @mistercrunch and I actually modified that code further in #1271.


Configurable package repository URL for nuget/dotnet analyzers

Package repository for Nuget package repository URL should be configurable or being read from a configuration file. At the moment it is hard coded in analyzer/src/main/kotlin/managers/utils/DotNetSupport.kt at
https://github.com/heremaps/oss-review-toolkit/blob/5f3bc12f16cd34b60d158b1f6af5865229943dfe/analyzer/src/main/kotlin/managers/utils/DotNetSupport.kt#L277-L280
and search API at
https://github.com/heremaps/oss-review-toolkit/blob/5f3bc12f16cd34b60d158b1f6af5865229943dfe/analyzer/src/main/kotlin/managers/utils/DotNetSupport.kt#L338-L341

Thanks for the suggestion. Do you happen to know where a regular (Visual Studio?) build picks up custom registries from?

@sschuberth no, I do not know that yet. We have a workshop this week about compliance automation topics and this is one point that we'll be working on. I will update the progress here.

That file would be nuget.config, see example (from https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file):
<packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
    <add key="Contoso" value="https://contoso.com/packages/" />
    <add key="Test Source" value="c:\packages" />
</packageSources>

Not sure how search API URL is constructed, though. Or why does it point to different URL anyway? Will keep investigating...

Thanks @kallesoranko for the info, @julscha will be looking at implementing this.

That file would be nuget.config, see example (from https://docs.microsoft.com/en-us/nuget/reference/nuget-config-file):
<packageSources>
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" protocolVersion="3" />
    <add key="Contoso" value="https://contoso.com/packages/" />
    <add key="Test Source" value="c:\packages" />
</packageSources>

Not sure how search API URL is constructed, though. Or why does it point to different URL anyway? Will keep investigating...

So, for now, I grasped as much: "For projects using the PackageReference format, NuGet uses local sources first, then sources on network shares, then HTTP sources, regardless of the order in the configuration files. NuGet always ignores the order of sources with restore operations." But what I haven't found out yet is where the "packageSources" information is stored when only using dotnet as a package manager. @kallesoranko  Do you happen to know that too?

@julscha sorry about delay in reply, but I have to say that I am not so familiar with Nuget/Dotnet.
My best guess would be .csproj file since that file is used with Dotnet.
There is some information at https://stackoverflow.com/questions/52996560/how-to-register-new-nuget-package-source-on-net-core

@kallesoranko I implemented the support for the configured repository URLs (See: #3176).
Anyways, there are some constraints:

The format of the catalog entry must be the same as the packages from https://api.nuget.org/v3/index.json (see #3190)
Authenticated package sources are not yet supported (see #3188)

Does this implementation work for your use case?


Added initial version of extension "flypy-code-query"

Description
Double-Pin is an input method based on Pinyin input method, which can be regarded as an improvement of Full Pinyin. By mapping each sound or rhyme containing multiple letters in Hanyu Pinyin to a certain key, each sound can be typed with two keys, which greatly improves the input speed of Pinyin input method.
flypy(Xiaohe Double-Pin) is a Chinese character input method. It is characterized by a phonetic and morphological scheme; each single character code is divided into four codes, the first two codes are for double spelling and the last two codes are for double form. flypy(Xiaohe Double-Pin) can be used only in the Double-Pin scheme, using the shape as a secondary code, and hooking up the single character code in the Pinyin input method, using it to assist you in quickly finding the single character you want to input.
This is an extension for quickly looking up the flypy(Xiaohe Double-Pin) code of Chinese characters.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

😭can you help me ? i dont know how to fixed it....

Hi @absir1949
Although I don't know the reason why your project build failed.
But the easiest fix is for you to recreate a new extension of the same name, then copy the source file in /src over and replace the code in this PR with the new extension code.
If you have any questions feel free to contact me in slack

Hi @absir1949 👋
I fixed your empty state flicker and added some actions, I hope it's okay 😄
Can you test it out and let me know if you're okay with the changes 💪

@pernielsentikaer  😄 thank you for the review and optimize,i has checked  it.
now it is okay.

Hi @absir1949 👋
I updated the screenshots since they was not in the right format, do you have a wish for the screenshot text (send me two texts) or is it okay as I did them?

@pernielsentikaer ok
the eg:
text:小鹤音形
text:小鹤双拼

Last this @absir1949 - can you add a better description, I don't think that the end-user will understand what this is for 😄

Last this @absir1949 - can you add a better description, I don't think that the end-user will understand what this is for 😄

oh..i update the description in this issue. Do you think it makes sense now?

I was actually thinking about this one, sorry for not being clear enough

I was actually thinking about this one, sorry for not being clear enough

OK，i update the des.now i think it is clear


Removed the problematic Python 2.7.18 version

Removed the problematic Python 2.7.18 version, since Python 2.7 is no longer supported and the specific version 2.7.18 was not found.
I removed it from the python-versions list.
Reference: https://github.com/actions/setup-python/issues/672

Reference: https://github.com/actions/setup-python/issues/672

Thanks, @stasfilin!


Always starts with 4 tab indented lines when initialized with empty value

When i try to initialize the editor without any content/value as empty string it sets the value to \n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t\n\t\t\t\t\t. It also fires a valueChanged event with that value.
If i give it a value like - than it only shows that.

I think I have a related issue, and maybe the cause of this issue.  If I add custom toolbars like this:
<Toolbar>
    <MarkdownToolbarButton Action="MarkdownAction.Bold" Icon="fi fi-text-bold" Title="Bold" />
    <MarkdownToolbarButton Action="MarkdownAction.Italic" Icon="fi fi-text-italic" Title="Italic" />
    <MarkdownToolbarButton Action="MarkdownAction.Strikethrough" Icon="fi fi-text-strikethrough" Title="Strikethrough" />
    <MarkdownToolbarButton Action="MarkdownAction.Heading" Icon="fi fi-text-header-1" Title="Heading" />
</Toolbar

It initializes a line for each <MarkdownToolbarButton /> along with any whitespace in front of the line.

I wonder if it's because the toolbar is inside of the <textarea></textarea> tags:
https://github.com/erossini/BlazorMarkdownEditor/blob/308e446dbbdbd5ad2f34c3a1d2cf09b75bfa40b4/PSC.Blazor.Components.MarkdownEditor/MarkdownEditor.razor#L5-L10

I'll check this issue asap.
Enrico

Today, I updated the full repository. There is a new EasyMDE managed by myself.  There is a lot of fixes in this new version.

Thanks for updating, but it didn't address this issue.

I faced the same problem. My solution was to wrap the toolbar's markup code in a hidden element.
<Toolbar>
    <div style="display: none;">
        ...
    </div>
</Toolbar>