Bring context into alignment with the API

Is your feature request related to a problem? Please describe.
Recently, we saw Merlinite's performance take a significant dive in addition to escaping its guardrails, while Granite continued to preform well. After some debugging, one of the things that rise out of the diff is that Granite seems to work with or without a system role to the endpoint, while Merlinite requires this system role. We would like to see some way that we can support a variable system role, so we can bring what we have in our repo in alignment with what is available at the API.
Describe the solution you'd like*
This solution should allow for this variable system role within the context ofilab chat -qq. This may be implemented in the config.yaml or a field name that is variable.
cc @nerdalert

@Gregory-Pereira - is this still relevant with the new ilab version release recently?

I have not looked in to this, I can try to validate it. This would have to do with the vllm serving, maybe anyone on the serving team can comment on the system roles in place with vllm there.

@alimaredia @russellb PTAL ^


Allow unpacking test data tuples into multiple arguments to the test case

Right now, if you want to pass several arguments to your test, you typically provide a tuple for each test case, and have to unpack them inside the test method, such as:
@data((1,2,3), (4,5,9))
def test_things_with_3_numbers(self, arg):
    op1, op2, addition = arg
    ...

A nice improvement could be if ddt did this unpacking for you:
@packed_data((1,2,3), (4,5,9))
def test_things_with_3_numbers(self, op1, op2, addition):
    ...

I believe this could be enhanced further.
I really would like to do somethings like this:
def get_data():
    return ( (1, 2), (2, 3,), )

@ddt
class TestMe(unittest.TestCase):
    @unpack
    @data(get_data())
    def test_func(self, first, second):
        # each tuple in the returned tuple is unpacked
        pass

I want more control of what data is passed into the test. Being able to generate all inputs for a test programmatically from a function, like TestNG does, would be a great way to go.


[1.13] Automated Bump DC/OS UI v2.82.7

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (required)
Related tickets (optional)

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

Please update CHANGES.md file (Add or update DC/OS UI line in Notable Changes section of newest version).
* Updated DC/OS UI to [1.13+v2.82.7](https://github.com/dcos/dcos-ui/releases/tag/1.13+v2.82.7).

You can edit CHANGES.md directly here: https://github.com/mesosphere/dcos/edit/dcos-ui/bump/2019-07-23-13-29-22/1.13+v2.82.7/CHANGES.md?pr=%2Fdcos%2Fdcos%2Fpull%2F5927

@mesosphere-mergebot label [Ready for Review]

-- PLEASE IGNORE THIS PR --a

Superseeded by #5957


Add new user

Description of the issue
Adding a new user ID
Ideas of solution
N/A
Workflow checklist

[x] I am aware of the workflow for this repository

How did you try to create this feature branch? You have to first clone the repository and then create locally a branch on your computer with git checkout -b feature-issueNumber-myfeature.
Unfortunately, the cloning step is not described in the CONTRIBUTING.md.
@Ludee: Can you please add a short info how to clone the OEO repo, maybe in the Prerequisites section.

I cloned the repo, rebased it to current dev, created a branch and tried to push using
git push --set-upstream origin feature-1096-adduser0028
it but I keep getting:
remote: Permission to OpenEnergyPlatform/ontology.git denied to areleu.
fatal: unable to access 'https://github.com/OpenEnergyPlatform/ontology.git/': The requested URL returned error: 403

@OpenEnergyPlatform/oeo-concept-owner : Any ideas why @areleu cannot push?

The remote origin is still pointing to the original repository, instead of your fork, for which only members of the oeo-dev team have write permissions. This occurs, if the original OEO repository was cloned instead of the fork.
Got allows you to have several remotes at once:
Run git remote add [custom name] [Clone-URL of your fork] .
Then push as you did before, but replace origin by the custom name above.

Yes, I am trying to push to the original repository, I tried to do the pull request originaly from my fork but the work flow states that it should be done from a branch of dev. Isn't that a contradiction?

@areleu I think you have to accept the intivation to the organisation first. We should add that to the documentation as well...

This is the reference to the new wiki-entry: https://github.com/OpenEnergyPlatform/ontology/wiki/Add-yourself-as-a-contributor

In PR #1324 user @areleu was added so this issue can be closed.


Xamarin.Forms for Android 8.0 (API 26)?

Quick question to see if targeting Android 8.0 is possible? I see lots of old versions available but a) don't know if they would work and b) can't quite tell which of them was used with 8.0

Hi @tleylan I haven't tried Android 8.0 specifically but as far as I know it should work fine.
I think the main thing is to go to the Android project properties in your solution and select the right target:

I believe there is a minimum version to support the current version of Xamarin.Forms which is why I was trying to locate an older version that did support 8.0
The $(TargetFrameworkVersion) for MyApp.Android (v8.0) is less than the minimum required $(TargetFrameworkVersion) for Xamarin.Forms (8.1). You need to increase the $(TargetFrameworkVersion) for MyApp.Android.	MyApp.Android

If I'm reading things correctly the MobileBlazorBindings has a dependency Xamarin.Forms (>= <IP_ADDRESS>8675) and that version of Xamarin.Forms (it seems) requires 8.1 at a minimum.

Ah interesting, I'm not super familiar with how these minimums work. I'll ask some colleagues for an assist on this one.

OK I talked to some Xamarin.Forms experts and here's what I got from them:

You can run on much older Android devices than what you're even asking for. Like much older.
The minimum supported Android target is API Level 28, but that's OK because:

That's the minimum required to even push to the Google Play Store
That's not the minimum device you run on, it's more like the SDK you're using to build

Separate from the target you also specify the minimum supported device, where you can go down to a really old version <-- this is likely the main source of confusion that I had
To guarantee that your code will work on older devices, though, you'll have to test on those (using physical device or emulator). If you want to optionally call a new API on a newer device you can do a runtime check such as this
You can find a lot more info here: https://docs.microsoft.com/en-us/xamarin/android/app-fundamentals/android-api-levels?tabs=windows

Well that helped I left the compile version at 10.0 and set the minimum and target to API 25 (turns out I needed that version). And... my Xamarin.Forms/Blazor app loaded and ran on my Oculus Quest. The hello world and counter works fine (font is small) and my tic-tac-toe game has some issues with the display but that tabs work.
I was determined to see something appear. I may be the first to have Blazor on the Quest. :-)

Wow very cool!!! Blazor running in 3D??? 😁

Closing this issue because I think everything was answered.


Doorbird connection error

It is not possible to connect to the Doorbird from a Docker container in the MACVLAN.
The log shows:
Error in testBird() Request: AxiosError: Request failed with status code 401

open docker ports in MACVLAN Container

Versions:

Adapter version: v1.3.0
JS-Controller version: 5.0.17
Node version: V18.19.0
Operating system: Synology Docker

Additional context
The instructions do not provide any information about the required ports and what exactly the DoorBird Device ID should be.

@Stefan592 any idea? I have no experience with docker.

Where can I find the DoorBird Device ID? On which ports is the adapter listening? Can more be logged out than status code 401 (Unauthorized Access)? I can log in to https://webadmin.doorbird.com/ with the user name and password.

The device id are the first 6 letters of any user. e.g. ghxxxx
Port: UDP 35344 (see at logging)

OK, that's how I entered it. Why could the test step fail? The ports that I have enabled are attached. What could I do to find the problem?

Access rights for the used user are correct? API Operator and Live Video?

I have created a new user at https://webadmin.doorbird.com/ and given this user the API Operator rights.
Now the connection test works. The Admin User account does not work!!!


CYD not working

Hi,
I flashed my CYD (usb-c) with the usual offsets.
There's no screen visible.
My fault?

Sorry for not reading your post well on Discord!

What CYD are you using if it has a micro USB and USB C on it then its not supported
only CYD's we support is the USB-C variant and the micro USB variant

im closing this issue as its not a firmware bug but a board we will support in the future


Update Azure.Identity Preview 5 with changes suggested in API Review

Tracking issue for updating Azure.Identity Preview 4 based on Java team API review feedback
/cc @schaabs as FYI

@joshfree  Can we always put a link to API Review ? Making sure that we look at right API review

https://apiview.azurewebsites.net/Assemblies/Review/5c748c0a690e4ddbb3fb344850a4ede0

There is also https://apiview.azurewebsites.net/Assemblies/Review/2a23558e091248958cbfd49125e58cb7

I am going to take of this  API  review as well now. I will create  new PR

PR :  https://github.com/Azure/azure-sdk-for-java/pull/5833

PR is merged.


Waypoint: Target HTML Elements with Selectors Using jQuery - Something is wrong - Please check !!!!

Challenge http://www.freecodecamp.com/challenges/waypoint-target-html-elements-with-selectors-using-jquery has an issue. Please describe how to reproduce it, and include links to screenshots if possible.

My solution is above - yet the editor doesnt accept it -
I dont know why?

Hey @syosoh06 thanks for posting an issue!
Please take some time to read our Bug Posting Guidelines as they should help you resolve any issues.
I was unable to replicate this so I think this issue should be closed, but if you follow the above steps and still have issues, please update this thread!

@syosoh06  I got this to work after cutting and pasting the exact code from the example.

Yes I had to do a hard refresh ( command + r ) and got it to work - thank you so much !!!!


JWKS request [question]

Hi @dorinclisu thank for the library, this is great and very straightforward!
I have a question/suggestion, I can see that the request for retrieving the JSON web key sets is hardcoded during the entity initialisation (https://github.com/dorinclisu/fastapi-auth0/blob/ae5256d06e8cd9bdc17c1138178be9612b24e7dc/src/fastapi_auth0/auth.py#L85)
So, in my case, my tests suit is fully running locally with a signed token that I'm generating locally instead of making external requests to Auth0; also, for uncoupling the tests suit in case I have to move out of Auth0 in the future.
Currently I avoid the issue monkey patching the entity so it works but I think that could be easy if we can extract that specific pice of code out of the initialisation.
What do you think?
Thanks again!

We can certainly extract the request as a separate function for calling it regularly (in case of tenant secret rotation), but I don't think we can remove it from initialization, and I don't understand why would you want to do something like that.
First of all, nothing prevents you from doing end-to-end testing, as communicating with auth0 servers is free and not limited in any significant way (except for M2M tokens).
Secondly, when testing your API there is no need to test the authentication, which is already thoroughly tested in this library. The auth can be cleanly decoupled by taking advantage of the clever fastapi dependency injection system.
See https://fastapi.tiangolo.com/advanced/testing-dependencies/
In this case, you would override auth.get_user with your custom function that injects a test user of your choice.

Thanks for the quick answer.

when testing your API there is no need to test the authentication,
I'm migrating custom code and I already have the specific tests for authentication, I could remove them but as it is now I have visibility of the new custom errors and responses.

See https://fastapi.tiangolo.com/advanced/testing-dependencies/
Yes I'm aware of it, I was using it. Thanks! 😄


Add workaround for spurious retransmits leading to connection resets

There is a longstanding issue over at https://github.com/docker/distribution/issues/785 where users reported connection resets trying to push to an AWS-hosted registry from inside the AWS network. After months, we've finally narrowed this down to a bad interaction between spurious TCP retransmits and the NAT rules that Docker sets up for bridge networking.
Here is a summary of what happens:

For some reason, when an AWS EC2 machine connects to itself using its external-facing IP address, there are occasional packets with sequence numbers and timestamps that are far behind the rest.
Normally these packets would be ignored as spurious retransmits. However, because the packets fall outside the TCP window, Linux's conntrack module marks them invalid, and their destination addresses do not get rewritten by DNAT.
The packets are eventually interpreted as packets destined to the actual address/port in the IP/TCP headers. Since there is no flow matching these, the host sends a RST.
The RST terminates the actual NAT'd connection, since its source address and port matches the NAT'd connection.

I think it would be hugely helpful for libnetwork to include a workaround for this. It has affected a lot of users trying to use the registry in AWS, and it presumably affects other Dockerized applications as well. While I'll reach out to AWS to point out the spurious retransmits, I don't know if they'll be able to fix them, and there may also be other environments with similar issues.
I've found two possible workarounds:

Turn on conntrack's "be liberal" flag: echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal. This causes conntrack/NAT to treat packets outside the TCP window as part of the flow being tracked, instead of marking them invalid and causing them to be handled by the host.
Add a rule to drop invalid packets instead of allowing them to trigger RSTs: iptables -I INPUT -m conntrack --ctstate INVALID -j DROP

Both of these can potentially affect non-Docker traffic. The former causes NAT to forward packets that it would otherwise err on the side of not forwarding, which seems relatively harmless, but it's a system-level setting, so it's not limited to Docker flows. The latter would drop any packets that conntrack deems invalid, system-wide, unless we added specific destination filters for the addresses/ports that Docker set up NAT rules for, which could add overhead.
It may be too late to hope for a workaround to be included in Docker 1.11, but anything we can do on this front will really improve the lives of Docker users on AWS.

@aaronlehmann I saw the linked issue turned out to be an issue with AWS, is there still something that needs to be done in libnetwork?

@thaJeztah: This issue is a suggestion to work around problems like this in libnetwork. The problem came from a combination of invalid packets generated somewhere in AWS' infrastructure, and the NAT setup used by libnetwork reacting to those invalid packets by tearing down the connection. This means the invalid packets cause problems for Dockerized applications but they are harmless for most other setups. docker/docker#19532 revealed that this problem was also seen on a residential internet connection. I think there is value in finding a workaround.

I'm being bit by this in production what more information could I provide?

Same here.. Simple docker container build on an arch linux system in residential.  Just trying to do a git clone from a https git site (bitbucket).

GnuTLS recv error (-54): Error in the pull function.
Closing connection 1
error: RPC failed; result=56, HTTP code = 200
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

Just ran into this on my office's internal network. Thankfully I found this page or all my hair would be ripped out by morning.
The iptables workaround did the trick for me, thanks very much for providing that. If it helps, I'm running Docker 1.11.2 on Ubuntu 16.04. Let me know if there's any more information I can give that would be useful.

@aaronlehmann It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926

A fix was implemented in AWS. I don't think a workaround is necessary anymore.

I will comment that this does happen on networks outside of AWS.   The iptables fix does fix it HOWEVER you first have to find this issue to learn that.  The errors are very generic, so if implementing the fix in docker is not a big deal it would probably save some people many hours of research into it:)

Any solution to this problem on a macOS host?

we have similar problem downloading file from to our docker image from nexus throws connection reset by peer, adding iptables rules fixes it

As it has been reported multiple times (@middleagedman, @BenSjoberg, @mitchcapper , @p53) the fix in the iptables resolves the issue ('connections reset by peer' or RST packet sent at TCP level).
Quick fix (ref @aaronlehmann): iptables -I INPUT -m conntrack --ctstate INVALID -j DROP
The issue is actually occurring in any container running in the default bridge network. Whether the issue occurs frequently or not depends on lot of factors (bandwidth, latency, host load). For sure, it occurs at some point. This issue is probably most of the time non-understood and incorrectly explained by a possible transient network partition, but it is not. It is a bug in the NAT setup installed by Docker.
We face this issue with a perfectly valid TCP client-server download (for instance a curl/wget from a container downloding a large http file from an external server at high throughput). Do the very same download from the host directly and all is fine, do it from the container and it breaks.
The problem as already mentionned by  @aaronlehmann is that begnin "invalid" packets to the SNAT'ed container (caused for instance by TCP window overflow due to high throughput but slow client) are assigned to the host interface and considered incorrectly martians, which causes a connection reset.
This is a limitaiton of conntrack which does not differentiate perfectly legal packets causing TCP window overflow from actually malformed packets (all get treated as INVALID). Hence the need to drop any conntrack INVALID packet seen when installing SNAT'ed virtual networks.
This is a problem references at several places, due to this netfilter/conntrack limitation:
https://serverfault.com/a/312687
https://www.spinics.net/lists/netfilter/msg51409.html
Quoting the last link from netfileter mailing list:

If NAT is enabled, never ever let packets with INVALID state pass through, because NAT will skip them.
Best regards,
Jozsef

The source NAT setup in iptables are installed by Docker for its bridge network support and are thus incomplete.
Imho it should be the responsibility of Docker to set this up correctly.
Apparently this was never fixed, hence my request to re-open this issue.
I can attempt to make a pull request if it can help, or I can open a new issue if needed, tell me.
Note that the abandoned pull request attempt #1129 does not fix the issue because the inserted rule does not drop the packets. There should be no filter on the destination because at that time the destination is not yet NAT'ed. Any conntrack invalid packets in filter INPUT chain have to be dropped as in : iptables -I INPUT -m conntrack --ctstate INVALID -j DROP.

FYI:
"/proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal" has gone since 2016-08-13 (see "netfilter: remove ip_conntrack* sysctl compat code" https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=adf0516845bcd0e626323c858ece28ee58c74455)
Now I think we should use "/proc/sys/net/netfilter/nf_conntrack_tcp_be_liberal" instead.

FYI: This is also an issue for kubernetes that they are trying to solve with similar strategies:
https://github.com/kubernetes/kubernetes/pull/74840

Hi @aaronlehmann,
I think that the issue was closed but never fixed, can you consider re-opening it.
Note that the pr #2275 solves the issue.

I'm using neither AWS nor Kubernetes, and I see the issue too between our office network (where our CI runners use) and external resource at digitalocean or maxmind.com. It generally manifests itself as
curl: (56) OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104

With tcpdumps I see lost but then reappearing packets (it reappeared after about 90ms or 200KB of data) triggering a RST. I'm not sure where the actual problem is, I'm assuming our ISP is doings something funky or a link aggregation is messing up packets. It happens mostly during quiet hours and the actual network issue is something we probably have to live with, but a 90ms packet delay shouldn't terminate connections
The liberal sysctl fixes our issue (and firewalling RST probably too), but as the issue is not AWS (or even K8S specific) I too think this issue should be reopened.

This is impacting us as well. Should this issue be reopened?

Had the same issue on GCP when downloading large file from inside container using curl. The iptables rule solve the problem for me. Another workaround was to use wget instead of curl, not this workaround might not be generally applicable to all cases

Hello. To solve this problem, I developed a kubernetes controller called node-network-manager. By simply deploying and configuring network-node-manager,  you can set iptables -I INPUT -m conntrack --ctstate INVALID -j DROP rule to all nodes of cluster. Please try this and give me feedback. Thanks.
https://github.com/kakao/network-node-manager

This issue pretty much exists in non-AWS, non-GCP world as well. We run our clusters on-prem and were able to reproduce this issue esp with requests going outbound with higher payloads. Getting into details...
Problem: We've an app team complaining about an issue with the environment. This app reaches outbound external service with certain sizes of payloads. In literal cURL world, it's nothing but passing JSON payloads in --data-raw. What was weird was that the requests went through fine with smaller payloads, but when the payload size reaches certain KB, the request goes outbound through firewall, gets executed on external service but response never reaches the container. We thought it's intermittent issue, but NO we could reproduce this issue 100% with certain request payload size.
Steps we took to narrow down:

To remove any possible bad behavior of app itself due to coding issue, we wrote a simplest client i.e. running the cURL directly from with in SSH'd container instance.
We ran the curl from worker node with smaller payload where the container is hosted, this worked
Ran the curl from worker node with larger payload, this worked
We then ran the cURL with smaller payload from within container (app instance), this worked
Ran the curl from container with smaller payload, this failed
Took packet captures on the container virtual interface (overlay networking) and eth0 default interface.
Packet captures on the virtual interface had no abnormal behavior. But pcap on eth0 showed RST connections from worker node to external service within a second or 2 of the request initiation.
We took captures on the external endpoint as well as on firewall. All of them showed symptom of the problem but not the root cause.
We tried running the same cURL on other clustered environment based on Kubernetes. We could reproduce this issue on every docker runtime. Though Cloudfoundry uses garden technology, but it still delegates the job to RunC which is the runtime for container based on Docker code.
For us running this command on the echo 1 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_be_liberal on the worker node did the trick! Thanks @aaronlehmann for taking time drafting this issue. Had we not stumbled on this issue, not sure how many man hours we would have spent around troubleshooting.

Since this is a system level setting that impacts not just docker traffic, we are still looking at best action that meets our environment needs. I am not inclined to give a resolution step, but just thought will put my thoughts/experience w.r.t this issue on how this took several man hours of effort to identify the root cause. Reading through above responses, 'am curious to know how this was fixed in AWS and why or if there exists a fix for this in the docker releases (considering this issue showed up 4 years ago).

The fact that AWS implemented a fix doesn't mean this issue disappeared. As mentioned by users above, this can still happen in some cases. I'll reopen it and I'll backport the PR submitted by @guillon into github.com/moby/moby.


helm 2.3.0 Error: grpc: received message length 11972000 exceeding the max size 10485760

Once switched to helm 2.3.0 we started hitting an issue with one of gate jobs which deploy a very large chart. It was working ok with version 2.2.3 though.
It seems 2.3.0 has added some additional info which trigger crossing this limit.

Change here fixed the issue. Should do PR for this change?
pkg/tiller/server.go
var maxMsgSize = 1024 * 1024 * 20

Closed by #2262

Check if you Chart directory does not contain unnecessary large files.


Sample Hello World app does not appear in sideloaded list

Step 2 says:
Select Manage your apps. Your app is listed in the sideloaded apps.

  This part is not clear.
I go to Apps > Manage your apps, but don't see the Hello World app anywhere.  There's no "sideloaded apps" list and searching for the app finds nothing.  I've tried tearing things down and re-doing, but I cant' get this tutorial to work.

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

ID: b1321426-bc5d-1b04-bcf6-5b6ae6100673
Version Independent ID: b1321426-bc5d-1b04-bcf6-5b6ae6100673
Content: Hello World with Node.js - Teams
Content Source: msteams-platform/sbs-gs-nodejs.yml
Product: msteams
GitHub Login: @surbhigupta
Microsoft Alias: lajanuar

@pawoolley - Have you enabled the sideloading option?
In prerequisites its mention to enable the sideloading option.
After clicking on Preview in Teams its redirected to the Teams and shown the popup for Adding App like below image

Could you please try to enable the sideloading option and check again.

As far as I know, yes, I did follow the steps to enable sideloading.  The screenshots in the docs don't match what I see exactly, but I do see the option to update a customer app.  Under Apps > Manage your apps, I see:

@pawoolley - Could you please check if your application is available in Apps > Build for org.
If it is not available try to publish your application and upload manually vai App > Manage your app > upload custom app.

Could you please check if your application is available in Apps > Build for org.

There is no Apps > Build for org.  I only see Apps > Built by your colleagues.

If it is not available try to publish your application and upload manually vai App > Manage your app > upload custom app.

I tried this.  A dialog pops up asking me to Add the app.  I click on the Add button, then I get a dialog saying "Something went wrong" with no further explanation.

Also, during the import process, I was seeing an error about the incorrect sizing of the icon files.

I fixed this by creating a blank 192x192 png to replace the colour icon and a blank 32x32 png to replace the icon outline.  It made that error box go away, but hasn't fixed the larger issue of not seeing this Hello World app getting loaded.

@pawoolley - Could you please share your manifest to try at our end?

Sure.  I'm not sure how useful it will be because it is just the one that comes with the hello world app nodejs sample:
helloworldapp.zip
Interestingly, if I try to import/create an app through the developer portal, and then click on Publish > App package, I don't see the app's manifest shown to me.  This happens on both the desktop app (MacOS Monterey) and the browser client (Chrome v97).

Hi @Nivedipa-MSFT ,
Is there any update to this issue?
Thanks.

@serv - We have informed Engineering team about the same and they are currently working on the fix. We will inform you once we have further update. Thanks!

Came here to report the same issue.  Doesn't look like this has been fixed.  All of the getting started demos walk through this same scenario to "Preview in Teams" and tell the user to find their app in the sideloaded apps .... which doesn't exist anywhere in the UI.  I get the confirmation it has been sideloaded okay, but can't find it anywhere in the UI or App List.  People go through the entire demo to end up with something that doesn't work in the docs.  Please fix this or update the docs.

@breakpoint7 - We are checking with the engineering team. We will let you know once we have any update.

Hello, all. I have the same problems.

@VladMilyutin - We are checking with the engineering team. We will let you know once we have any update.

@pawoolley - Engineering team is currently working on the fix.  We will inform you once we have any updates.

Hi, is there any updates to this please? The walkthrough was working (although the walkthrough does not match the UI most of the time) then about 2 weeks ago it just stopped. If you follow it through (I am following the Microsoft.Teams.Samples.HelloWorld.Web), I cant view the app package under publish (you get a message saying ‘Nothing to see here yet. In order to edit this aspect of the app, it needs to be more complete. Resolve any validation issues shown in the Overview and try again‘ or side load (all you get is the behaviour mentioned in the threads above). If you don’t have a fix, is there a way to workaround this so we can get on with developing our app? It seems to have happened when version 1.13 of the manifest was released… thanks!

Hello @surbhigupta12 - Can you please help us here to update the documentation?

This peer needs to be closed and no further action needed.


CI: Add clang configs for Engflow's remote execution

Signed-off-by: Luis Fernando Pino Duque<EMAIL_ADDRESS>Description:
CI: Add clang configs for Engflow's remote execution.
This change is a no-op that will be used for switching more CI workflows to Engflow's remote execution.
See https://github.com/envoyproxy/envoy-mobile/pull/1745 for preliminary results.
Risk Level: Low
Testing: Manually tested
Docs Changes: N/A
Release Notes: N/A

/cc @goaway


more robust PATH handling

init_*.go is concatenating path lists and directory names using simple string operations. This is not always correct and can in some situations lead to security issues.
More specifically, on Windows, when the executable path contains a semicolon ";", instead of adding the directory to the list, it adds two unrelated directories to the list, which is both incorrect and potentially unsecure. On Unix, if the user unsets PATH for extra security, the program sets it to "/sbin:/usr/sbin:/bin:/usr/bin:" (note the colon at the end), which includes the current working directory at the end, that was probably not intended, and again potentially unsecure.
Shameless plug: both issues can be avoided by using gopkg.in/pathlist.v0 which was designed to prevent these kinds of issues. See https://godoc.org/gopkg.in/pathlist.v0 for detailed explanation.
Implementation note: In both cases it's safe to use pathlist.Must in this situation: on Windows it only panics if the directory name is quoted but the result from os.Executable() should be raw (unquoted) filepath, and on Linux it only panics if the directory name contains the separator ":" (which is a valid character in directory names on Unix, but such directories cannot be added to PATH).

@speter
Thank you for pointing out and sending patch.

More specifically, on Windows, when the executable path contains a semicolon ";", instead of adding the directory to the list, it adds two unrelated directories to the list, which is both incorrect and potentially unsecure. On Unix, if the user unsets PATH for extra security, the program sets it to "/sbin:/usr/sbin:/bin:/usr/bin:" (note the colon at the end), which includes the current working directory at the end, that was probably not intended, and again potentially unsecure.

Right.  We should handle PATH more carefully as you mentioned.
But introducing additional external library is too much, since required changes are small enough if we handle them by mackerel-agent itself. (See #501 ).
Therefore, I'd like to close this p/r and handle the problem in #501.
Thank you again for your suggestion and patch.


[Event Request] Report 5197 "Remove Contacts - Reduce" - OnPreReport(): Need a new event OnBeforeRunReduceRefineSegment #19144

Please check the request https://github.com/microsoft/ALAppExtensions/issues/19144.
It has been approved but not implemented yet.
Thank you!

Hello,
For changing accessibility of variable, please open new request.
Thank you

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11415.


excludee null fields in _construct_relations

In the method NewBaseModel._construct_relations if some relations are null, expand_relationship will return None. This None values will cause the following AttributeError when they are passed to model._orm.add as parent
ormar/relations/relation_manager.py", in add
    parent_relation = parent._orm._get(child_name)
AttributeError: 'NoneType' object has no attribute '_orm'

Codecov Report

Merging #870 (d13ff36) into master (8c57f37) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##            master      #870    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files          188       188
  Lines        16038     15599   -439
==========================================
- Hits         16038     15599   -439

Impacted Files
Coverage Δ

ormar/models/newbasemodel.py
100.00% <ø> (ø)

tests/test_types.py
100.00% <0.00%> (ø)

ormar/queryset/clause.py
100.00% <0.00%> (ø)

ormar/models/excludable.py
100.00% <0.00%> (ø)

ormar/fields/foreign_key.py
100.00% <0.00%> (ø)

tests/test_signals/test_signals.py
100.00% <0.00%> (ø)

tests/test_queries/test_order_by.py
100.00% <0.00%> (ø)

tests/test_queries/test_or_filters.py
100.00% <0.00%> (ø)

tests/test_queries/test_pagination.py
100.00% <0.00%> (ø)

tests/test_relations/test_cascades.py
100.00% <0.00%> (ø)

... and 96 more

Awesome, thanks!
Can you please add one test with None as one of the relations so it will be checked from now on?


Encoding in Expression Editor differ from Properties

When adding special character in M partitions or Dax Expression it is shown correct in properties, tooltips ect but not in the Expression Editor
To Reproduce

add a Dax Measurement or M Expression like “ /* 🤐😟 */ SUM(Data[Sales])“ to a Power BI Report
Open in Tabular Editor 2 and click on the measurement

Expected behavior
Show the same encoding as Properties
Tested in Tabular Editor 2.18.1

The text editor component used by TE2 unfortunately does not support wide-char (unicode) characters, such as emojis. We don't currently have any plans to switch to another editor component.


Move internal log messages to DEBUG

During CWL runs, there are extra messages in the INFO log
relating to internal processes, which obscure useful messages. This
moves these to DEBUG:

Internal jobs releated to CWL
Cache access and read messages
Deletion of cached files
Adding files to be deleted from cache

Fixes #1061

@chapmanb thanks for the PR, just a couple minor changes!

Christopher -- great suggestions, thank you. I swapped over to logging job start/stop in INFO for non-internal CWL job using the pointers in leader you suggested. The disk usage metrics are now all in DEBUG. This is great, the output is now much cleaner and we have messages when jobs start and finish. Thank you again and please let me know if you have any other suggestions.

+1 Excellent change


missing remove authentication providers option

I can't see the remove authentication providers option in the setup.js. I am using version 3.0.2

There were a lot of issues with it so I decided to remove that functionality.


SSH and Node Connectivity Disruption During Cilium Upgrade to v1.16.1

Is there an existing issue for this?

[X] I have searched the existing issues

Version
equal or higher than v1.16.0 and lower than v1.17.0
What happened?
During upgrade of Cilium with kube-proxy v1.14 to v1.16.1 without kube-proxy. This command iptables-save | grep -v KUBE | iptables-restore which is listed in the upgrade steps, breaks the SSH connectivity to the VM and overall k8s node connectivity, I managed to find that in particular iptables mangle table causes the issue and flushing it 'iptables -t mangle -F' then 'k rollout restart ds/cilium' fixes the issue. OS is RHEL 8.10
How can we reproduce the issue?

kubectl -n kube-system delete ds kube-proxy
kubectl -n kube-system delete cm kube-proxy
iptables-save | grep -v KUBE | iptables-restore

Cilium Version
1.16.1
Kernel Version
4.18.0-553.16.1.el8_10.x86_64
Kubernetes Version
1.27.16
Regression
No response
Sysdump
cilium-sysdump-20240822-140752.zip
Relevant log output
No response
Anything else?
No response
Cilium Users Document

[x] Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for the observation. Do you think we just need to improve the docs to include those instructions? Would you be open to submitting a PR to fix that?

Sure, I will submit PR.

These sorts of things are notoriously finicky to diagnose. Would you be able to provide the set of iptables chains before and after? A sysdump before and after migration would help.
I'm curious why node traffic would have been affected; Cilium and kube-proxy can co-exist somewhat without getting in to too much trouble.

FWIW I experienced this going from 1.14.3 > 1.16.5 on Debian 12 physical nodes as well.
I also experience this when upgrading Kube itself, and needing to restart the CRIO daemon, for major releases. This has led to me doing a full node reboot instead of daemon restarts.
As I have physical nodes, once the behaviour starts it's difficult to diagnose it - however I will get some keyboard/console connections going on the next upgrade cycle and see if I cannot get more details - and I'll try the extra step suggested by @GyurkanM to see if it prevents it.


TypeError FIX

I dont know if this bug or not but I got a problem during migrate.
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'ContentType'

Hi @dbmkin, it's definitely a bug, thanks for the PR!


website is nice!

website is nice! but there are some different at home page between local and remote.

Hi, thanks for the compliments. This repo is the "Core edition" that is a little different from fossdroid.com; for more info read the README.md.


[RFR] timeout is in seconds

Hi
PR related to issue https://github.com/M6Web/AmqpBundle/issues/15
For reference : https://www.rabbitmq.com/heartbeats.html

:+1:

:+1:


source: csv: Add config to load data from filename

https://github.com/intel/dffml/blob/c0899bc063ec6c2d3f32919db5a62305ccd4f2ec/dffml/source/csv.py#L46-L50
Add a config option which is a list of strings, which are the column names which should have their data replaced with the contents of the file for which they had the filename of as their value initially.
https://github.com/intel/dffml/blob/c0899bc063ec6c2d3f32919db5a62305ccd4f2ec/dffml/source/csv.py#L192-L194
If key (column name) is in the new config (files or something) then do
row[key] = pathlib.Path(value).read_bytes()

Make sure there is a testcase for it.

@sakshamarora1 is working on this as a part of #272

@pdxjohnny this issue has been solved by #399 ?

It has been solve by that indeed! Thank you @ sakshamarora1!


Unable to activate Windows store app.

I'm trying to build sample iOs project for Universal Windows.
If I select 'Start debugging', I get "debuggerutils.h not found. You need to find debuggerutils.h to view the source for the current call stack frame"
If I select 'Start without debugging' I get "Unable to activate Windows Store app. The activation request failed with error 'Operation not supported'"
Am I missing something?

It is hard to say without knowing your exact installation situation. I believe that "Unable to activate Windows Store app" type issues are a generic problem with Visual Studio. If you have the Community Edition installed then you might try logging into your Microsoft developer account to activate the development keys. A clean build would not hurt either. I've encounter this situation a handful of times and it seems to be a hit or miss solution, but I've always been able to overcome this issue in the past with VS projects.

@edvv, thank you for your answer. I've tried clean install several times, even clean install of Windows. Also I'm able to build and run Blank App on Visual C# for Universal Windows. That made me think that something is wrong with WinObjC.

Hey @Artelas what is your VS and winobjc versions you are using for building. Did you try to update your developer/store keys?

Ah, now I remember what this means: This is a false message. What really happened is that your app silently terminated (maybe by a console abort(), i.e.: crashed ) and when the app failed to launch (aborted) the front end gave that message. You need to look at the Windows Console window in VS while in debug mode.


Add examples of using _preValidatePurchase in Crowdsale.sol

While reading through the Crowdsale.sol smart contract, I am wondering if someone can explain to me what this portion of the comments mean:

Use super to concatenate validations.

What can be a reason for concatenating validations, and can we have an example of doing this?
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/92b695f2fb258a5669181d1d8cf8e73aa756f22c/contracts/crowdsale/Crowdsale.sol#L110-L123
Thank you!

Thanks for bringing this up @vertangelx!
The inline documentation is lacking in this regard, it should have an example or use clearer language.
For an example, see CappedCrowdsale:
https://github.com/OpenZeppelin/openzeppelin-solidity/blob/5daaf60d11ee2075260d0f3adfb22b1c536db983/contracts/crowdsale/validation/CappedCrowdsale.sol#L38-L46
A precondition is added to the existing ones by overriding the function and using super.


Replace Notes blocks with Github alerts

This pull request replaces the notes blocks in the documentation with Github alerts.

coverage: 99.894%. remained the same
when pulling 85af6824322a7dfbbaa68e0555f774a6e36e85b9 on replace_notes_blocks_with_github_alerts
into 544be89fba263411ee4a92d061b789bdd430e06b on master.


[UI-context]: fixes #402 create new context

issue #402
[X] Deprecate Modal Context and move into UI context
[X] Add theme context

The CI test suite failed. Did you pull changes from the dev branch before you pushed.

Yeah, I changed deprecated the modal context for the new context so all the
tests written for the former modal context keeps crashing the test suite.
The test suites need to be written.
On Thu, 9 Sept 2021 at 15:54, Denedo Oghenetega Joseph <
@.***> wrote:

The CI test suite failed. Did you pull changes from the dev branch before
you pushed.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zurichat/zc_plugin_reminder/pull/443#issuecomment-916174585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKNBX4WGP775DG7TJXVZUMLUBDDATANCNFSM5DU7J4BQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Yeah, I changed deprecated the modal context for the new context so all the tests written for the former modal context keeps crashing the test suite. The test suites need to be written.
…
On Thu, 9 Sept 2021 at 15:54, Denedo Oghenetega Joseph < @.***> wrote: The CI test suite failed. Did you pull changes from the dev branch before you pushed. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#443 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKNBX4WGP775DG7TJXVZUMLUBDDATANCNFSM5DU7J4BQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I understand the situation better now. I'll refactor the tests from your fork and when it's finalized Andrew will merge this PR.

I understand the situation better now. I'll refactor the tests from your fork and when it's finalized Andrew will merge this PR.


Peering Request

Full Name
Fabio Escorpioni
ASN
999
PeeringDB Integration

[X] My PeeringDB Entries are current
[ ] Peer at ALL EXCHANGES (and skip the Peer Address(es) field below)

Peer Address(es)
IX.BR Sao Paulo
<IP_ADDRESS>
2001:12f8::210:69
Multihop

[ ] Multihop Peering Request

Hi Fabio,
Thanks very  much for your peering request at IX.br Sao Paulo... Unfortunately our Sao Paulo collector is full.However, I see you are at IX.br in Rio. Would you be interested in peering with RouteViews there instead? Our details are in our PeeringDB entry: https://www.peeringdb.com/asn/6447. Please let us know, and I'd be happy to set this up.
Thanks!

Now completed, thanks for supporting the RouteViews project!


Evaluate codellama-instruct family

https://huggingface.co/TheBloke/CodeLlama-7B-Instruct-fp16
https://huggingface.co/TheBloke/CodeLlama-13B-Instruct-fp16
Need to reverse-engineer prompt format from https://github.com/facebookresearch/codellama/blob/main/example_instructions.py

Its the same instruction format as llama2-chat, which makes this one straightforward hopefully.

Experimenting with some prompt formats.
No-system prompts work the best so far and sometimes result in this interesting response template:
 [INST] Write a python function factorial(n) with input n that returns the factorial of n using recursion. [/INST]  [PYTHON]
def factorial(n):
    if n == 0:
        return 1
    else:
        return n * factorial(n-1)
[/PYTHON]
[TESTS]
# Test case 1:
assert factorial(0) == 1
# Test case 2:
assert factorial(1) == 1
# Test case 3:
assert factorial(5) == 120
[/TESTS]

Extractor will have to be updated to understand this.  Haven't seen a JS version yet.

Caught a bug in the transformers interview for templates that start with <s> since this token is not decoded the interviewer failed to remove from the prompt from the answer which breaks downstream extraction.
Will need to re-evaluate Llama2-Chat with this fix

Narrowed it down to the two best prompt variants and the recommended sampling params from upstream.
7B looks quite good, but 13B scores lower on both languages.  This evaluation has been anything but smooth tripped several bugs so in case there are still more bugs I'm reserving judgement.

7B vs 13B compare posted, remaining bugs fixed but in general 13B is indeed worse on some of the tests
34B will be done as part of #80 once it's available.

in general 13B is indeed worse on some of the tests

That is indeed surprising.


Call for ideas! 🔥

🚀 Feature
We'd like to expand the component set in Bolts, aiding the community in using lightning with other cool projects. If you have any suggestions please list them below in the comments!
Even if the library does not require any form of component, I think it would be nice to have a place to store documentation on using said library with Lightning (if the maintainers of the library do not include this).
Some suggestions from the PyTorch Ecosystem
Model Interpretability
https://github.com/pytorch/captum
https://torchdrift.org/
Federated Learning/Differential Privacy
https://opacus.ai/

Let's first list/link interesting issues from our Bolts's backlog :rabbit:

Hi @SeanNaren, My idea for Bolts is to have paper implementations and add pre-trained models for various use cases.
cc: @Borda


Mod stops server from stopping

When stopping the server with this mod installed it stops it from stopping
I use fabric 1.19.2
Here are the mods used:

Here is the log:
[13.01 10:33:11] [Multicraft] Stopping server!
[13.01 10:33:11] [Server] [Server thread/INFO]: Saving the game (this may take a moment!)
[13.01 10:33:11] [Server] [Server thread/INFO]: Saved the game
[13.01 10:33:11] [Server] [Server thread/INFO]: Stopping the server
[13.01 10:33:11] [Server] [Server thread/INFO]: [BisectHosting] Cleaning up scheduled tasks.
[13.01 10:33:11] [Server] [Server thread/INFO]: [Dynmap] Unloaded 11 components.
[13.01 10:33:11] [Server] [Server thread/INFO]: [Dynmap] Stopping map renderer...
[13.01 10:33:12] [Server] [Server thread/INFO]: [Dynmap] Disabled
[13.01 10:33:12] [Server] [Server thread/INFO]: Shutting down Geyser.
[13.01 10:33:12] [Server] [Server thread/INFO]: Geyser shutdown successfully.
[13.01 10:33:12] [Server] [Server thread/INFO]: Stopping server
[13.01 10:33:12] [Server] [Server thread/INFO]: Saving players
[13.01 10:33:12] [Server] [Server thread/INFO]: Saving worlds
[13.01 10:33:12] [Server] [WebSocketConnectReadThread-147/INFO]: The skin uploader has been closed
[13.01 10:33:13] [Server] [Server thread/INFO]: Saving chunks for level 'ServerLevel[world]'/minecraft:overworld
[13.01 10:33:14] [Server] [Server thread/INFO]: Saving chunks for level 'ServerLevel[world]'/minecraft:the_end
[13.01 10:33:14] [Server] [Server thread/INFO]: Saving chunks for level 'ServerLevel[world]'/minecraft:the_nether
[13.01 10:33:14] [Server] [Server thread/INFO]: ThreadedAnvilChunkStorage (world): All chunks are saved
[13.01 10:33:14] [Server] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM1): All chunks are saved
[13.01 10:33:14] [Server] [Server thread/INFO]: ThreadedAnvilChunkStorage (DIM-1): All chunks are saved
[13.01 10:33:14] [Server] [Server thread/INFO]: ThreadedAnvilChunkStorage: All dimensions are saved
[13.01 10:33:15] [Server] [Server thread/INFO]: Unloading addons...
[13.01 10:33:15] [Server] [Server thread/INFO]: Unloaded addons
[13.01 10:33:15] [Server] [Server thread/INFO]: Unloading instance: net.dv8tion.jda.internal.JDAImpl@ee1ae4e
[13.01 10:33:15] [Server] [Server thread/INFO]: Unloading listener: de.erdbeerbaerlp.dcintegration.common.DiscordEventListener@4d1eb0ec

these are the same log messages for me, HOWEVER the Server has stopped after those without issue. this seems to be normal that way.

Mainly older versions have this lockup issue
that issue also mostly happens randomly with no pattern
The log is totally normal tho

This actually happens every time the server is stopped, the server will eventually stop (after ~7 mins) but I usually kill the server without any corruption or similar

Closing as I fixed it already


Strategies for WISP <-> LFE?

Would wisp support be a separate project or can it be done in this project?
https://archive.fosdem.org/2019/schedule/event/experiencewithwisp/attachments/slides/2979/export/events/attachments/experiencewithwisp/slides/2979/wisp_fosdem_2019.pdf

I'd recommend a new project.
Even if was something as simple as a minor tweak in syntax that removed the majority of parens and substituted them with syntactic whitespace, you'd be presenting a very confusing story for users, with syntax that would tend to draw from two very different backgrounds/proclivities/whathaveyou, to a project that's already struggling to keep up documentation with just one syntax ;-)
It might be a good exercise to fork LFE, examine the reader functionality, and explore a means of translating from whitespace syntax to LFE's syntax. For now, forking would be required; however, Robert and I have been talking about doing some more abstraction around the reader and evaluator functionality that would essentially transform LFE into a language laboratory for any conceivable syntax ;-) That's a ways off, though ...

I labeled this as "answered" and am going to close it -- but feel free to ask any additional questions either here in the ticket, on the LFE mail list, or on our Slack!


chore: Add BTC mainnet ZRC-20

No longer relevant due to https://github.com/zeta-chain/protocol-contracts/pull/10


add config validation as admission controller

/lint

/lint

/assign @mattmoor

/ok-to-test
@nimakaviani could you actually fill in the description. The title is mostly self-explanatory, but it's good to have more detailed context of the changes within.

/retest

/hold
while merging https://github.com/knative/pkg/pull/653

/hold cancel

/lint
updated based on @mattmoor 's suggestions

/approve

/lgtm
/approve


Wrong synthesis result

For the following problem
type nat = Z | S of nat

let rec odd = function
  | Z -> false
  | S x -> even x
and even = function
  | Z -> true
  | S x -> odd x

let rec query x = odd x && odd(S (S x))

let rec f x = [%synt fi]

assert (f = query)

I get the following result:
let fi  = false

let rec f x = fi

which is obviously false as query(S Z) = true

Yes, there is a problem in the way the tool initializes its state when the function to synthesize doesn't decompose its input (by pattern matching).  I will fix this as soon as possible.
In the meantime, you can try rewriting the benchmark as follows:
type nat =
  | Z
  | S of nat

(* Group the functions defining your reference function. *)
let rec query x = odd x && odd (S (S x))

and odd = function
  | Z -> false
  | S x -> even x

and even = function
  | Z -> true
  | S x -> odd x

let rec f x = [%synt fi]
;;
assert (f = query)

And use the -c option when invoking Synduce (this turns off the optimized initialization that causes the problem).
Synduce should then answer that there is no solution.


Fix #468: Add support for single parameter quasiquote

Quasiquotes can now pattern match on a single parameter in a primary constructor or function parameter list.

CI still failing because of git error.

👏  Excited to get this in ^_^

See two suggested changes to the tests in comments. Otherwise LGTM.

Done.

LGTM


[ScrollView] [UIExplorer] Fixes #3060

This pull request fixes a glitch that occurred when scrolling horizontally, as described in the #3060.

Signed, I thought I did it already.

Could you also set automaticallyAdjustContentInsets={false} while you're at it since we never want to set a top inset on this view anyway?

Sure. No probs.

(And squash commits :)

Yeah, I am on it :dash:

Done :) CC: @ide

Thanks for the fix!

@facebook-github-bot shipit


Is this bug related to SDK or Supabase backend?

When I try to create new user accounts using "signInWithOTP" method it throws error consistently.
(FYI, no issues with login - it is just with sign up)
I've reached out to Supabase team but no reply yet.

Hi @pradeepb28
Do you have any trigger running on sign up? It seems like it is throwing an error due a missing cid field on the new record

Thanks for confirming, I have added a trigger but it seems like it saying there is no table users when I use
Drop trigger on_credits_insert on users; (FYI, users is auto-generated table from Supabase based on the user authentication I think)


Add repo SECURITY.md

See https://github.com/kubernetes/security/issues/105

/lgtm
/assign @madhusudancs @pmorie

Closing since the security policy is now defined org-wide - https://github.com/kubernetes/org/issues/2081
For this repo, it can be seen at https://github.com/kubernetes/cluster-registry/security/policy


How can I continuously listen events from AMI ?

If I have an incoming call how can I detect that there is an incoming call on asterisk from my php server using PAMI? Please help.
I tried with  $a->registerEventListener(new A());. It only listen current action event not listening other event

Hello!
You may use this code below:
`$running = true;
// Main loop
while($running) {
$pamiClient->process();
usleep(1000);
}`

That’s busy-waiting, which can potentially be CPU-intensive.
Does PHP have any select/poll support?


fix #301 - broken imports in node environment

this fixed #301 for me
the env condition in the .babelrc was never met, see babel env option

Oh, that was a silly mistake on my end, thanks for this fix, much appretiated! I'm going to release that immediately.

Released as v0.7.2

That was fast, thanks!


The FAQ page on AJAX and APIs should be refactored to use hooks

The FAQ page describing how to interact with APIs via AJAX still uses class components. This should probably be updated to use hooks

👍 PR welcome to add a hooks version

@alexkrolick more than happy to do so.


Make auto use run on program start

on the current version, the auto use will run after a short time after the program started, this meant that if the user doesn't have a life saver in inventory and turned on auto use apple, it will have a chance to die and lose items when an apple is not used.

Fixed in 81f4d2f although there is still a 10 second cooldown to auto use


Unable To update VSCode

vscode-inno-updater-1559835663.log

Please fully uninstall VS Code and reinstall the user setup once more.


C#: fix subchannel sharing for secure channels

Tentative fix for https://github.com/grpc/grpc/issues/15207
The idea is that for the same ChannelCredentials instance, we need to cache the native credentials object once created, because passing a different grpc_channel_credentials* creds when creating a channel in C core will result in C core acting as if the channel args were different (and thus subchannels are not shared).
Keeping the ChannelCredentialsSafeHandle around can lead to using extra memory, but the native object will get cleaned up by finalizer once (and if) ChannelCredentialsSafeHandle gets garbage collected.

CC @evildour

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

 No significant differences in binary sizes

***************FRAMEWORKS****************
  New size                      Old size
10,665,709      Total (>)     10,665,704

 No significant differences in binary sizes

@mehrdada  can you review?


Hi @osandadeshan, I solved the problem in the following way.

Hi @osandadeshan, I solved the problem in the following way.

RestAssured.given().config(RestAssured.config().encoderConfig(EncoderConfig.encoderConfig().encodeContentTypeAs("multipart/form-data", ContentType.TEXT)))
.contentType("multipart/form-data; boundary=--MyBoundary")
.queryParams(params)   // formParams does not working
.post(url)

Originally posted by @comtizen in https://github.com/rest-assured/rest-assured/issues/1003#issuecomment-533027048

Hi,
Could you please help out, I am struck with the similar kind of issue, and when I pass in .contentType("multipart/form-data; boundary=--MyBoundary"), what value I need to pass in the MyBoundary

Hi @osandadeshan, I solved the problem in the following way.
RestAssured.given().config(RestAssured.config().encoderConfig(EncoderConfig.encoderConfig().encodeContentTypeAs("multipart/form-data", ContentType.TEXT)))
.contentType("multipart/form-data; boundary=--MyBoundary")
.queryParams(params)   // formParams does not working
.post(url)

Originally posted by @comtizen in #1003 (comment)

Hi, I tried your solution but I am getting status 400, while it's working fine in postman. Can you please help?


Livewire update does not apply middlewares set up in the configuration

Pulse Version
v1.0.0-beta9
Laravel Version
10.40.0
PHP Version
8.3.1
Livewire Version
3.3.5
Database Driver & Version
postgres:16-alpine3.19 (Docker linux amd/64)
Description
Working on a solution with two different user's guards, we notice that the POST /livewire/update requests does not use the intended guard for pulse. Indeed, the auth:other_guard middleware is set up in the Pulse config file, but it seems that the POST livewire/update request does not use the middleware in the pulse config and instead, only the web middleware, thus using the default user guard.
Steps To Reproduce

Set up a second Auth provider (admin_session in this example)

Add another user guard in config/auth.php.

<?php

use App\Models\User;

return [
    'defaults' => [
        'guard' => 'web',
        'passwords' => 'users',
    ],

    'guards' => [
        'web' => [
            'driver' => 'session',
            'provider' => 'users',
        ],
        'admin' => [
            'driver' => 'admin_session',
            'provider' => 'users',
        ],
    ],
   // ...
}

Adapt pulse config (config/pulse.php) to use the intended guard

use Laravel\Pulse\Http\Middleware\Authorize;

return [
    'middleware' => [
        'auth:admin',
        'web',
        Authorize::class,
    ],
]

Connect to both user systems, and notice that the main pulse page uses the admin guard as intended, whereas POST livewire/update uses the default webguard. It can be easily noticed using the viewPulse Gate.

use Illuminate\Support\Facades\Gate;
use App\Models\User;

Gate::define('viewPulse', function (?User $user) {
    if ($user->login !== 'theoneconnectedtotheadmin') {
       throw new \Exception('Wrong one');
    }
    return true;
});

Just noticed https://github.com/laravel/pulse/issues/269, will have a look if issue is indeed the same later today.

I'm unable to replicate this problem. Below is what I am using against a fresh laravel application.
I am seeing all the expected logging and not experiencing exceptions for the initial request or subsequent requests.
Can you please create a minimal reproduction for this and we take a closer look?
laravel new bug-report --github="--public"

Service provider
class AppServiceProvider extends ServiceProvider
{
    public function register(): void
    {
        //
    }

    public function boot(): void
    {
        Auth::extend('admin_session', function () {
            Log::info('Using auth via custom guard.');

            return new class implements AuthGuard {
                public function check()
                {
                    return true;
                }

                public function guest()
                {
                    return false;
                }

                public function user()
                {
                    return User::first()->setAttribute('from_custom_guard', true);
                }

                public function id()
                {
                    return $this->user()->id;
                }

                public function validate(array $credentials = [])
                {
                    return true;
                }

                public function hasUser()
                {
                    return true;
                }

                public function setUser(Authenticatable $user)
                {
                    //
                }
            };
        });

        Gate::define('viewPulse', function (?User $user) {
            if ($user->from_custom_guard !== true) {
                throw new Exception('Wrong one!');
            }

            Log::info('Able to view Pulse.');

            return true;
        });
    }
}

Auth Config
'guards' => [
    'web' => [
        'driver' => 'session',
        'provider' => 'users',
    ],
    'admin' => [
        'driver' => 'admin_session',
        'provider' => 'users',
    ],
],

Pulse Config
'middleware' => [
    'auth:admin',
    'web',
    Authorize::class,
],

Thanks for the quick reply. I had a look with my team this morning and we identified what's missing here to reproduce. We simplified too much the context of the issue (and we are sorry for that 🙏).
The missing step is that we have a custom Authenticate middleware for admins in order to redirect to another route.
<?php

namespace App\Http\Middleware;

use Illuminate\Auth\Middleware\Authenticate;
use Illuminate\Http\Request;

class AdminAuthenticate extends Authenticate {
    protected function redirectTo(Request $request)
    {
        return '/';
    }
}

So our middleware configuration in pulse.php looks like this :
<?php
use App\Http\Middleware\AdminAuthenticate;

return [
    'middleware' => [
        AdminAuthenticate:class . ':admin',
        'web',
        Authorize::class,
    ],
]

We changed it to this and everything works fine.
<?php
return [
    'middleware' => [
        'auth:admin',
        'web',
        Authorize::class,
    ],
]

As a workaround, we changed the middleware in pulse, so the issue is not as critical for us, but we still think it could be usefull to be able to use custom authentication middlewares in pulse later. Perhaps, something to do with livewire configuration ? I'm not familiar with it.
We will provide you a minimal repo tomorrow to easily reproduce.

I've been able to replicate this issue. Looks like an issue with Livewire.
I'm investigating a fix.

Opened a fix for this one: https://github.com/laravel/pulse/pull/283
I'll close this and we can follow along in that PR.


feat(combobox, dropdown): dt7 style update

Update Combobox style

I previously made updates Dropdown, but Combobox needed updates to align.
Updated Chip icon size.

:hammer_and_wrench: Type Of Change

[ ] Fix
[x] Feature
[ ] Refactoring
[ ] Documentation

:pencil: Checklist

[x] I have reviewed my changes
[ ] I have added tests
[ ] I have added all relevant documentation
[ ] I have validated components with a screen reader
[x] I have validated components keyboard navigation
[x] I have considered the performance impact of my change
[x] I have checked that my change did not significantly increase bundle size
[ ] I am exporting any new components or constants in the index.js in the component directory
[ ] I am exporting any new components or constants in the index.js in the root

Pretty sure this was not a result of this specific change but the items in multi select appear quite low. This can be a separate ticket, I think they are calculated via javascript not just css since the height changes dynamically.

...items in multi select appear quite low...

The Input component updates I had made resulted in some magic numbers being out of sync, which assumed the specific heights of the input and Chips — though some of it is indeed appropriate (namely padding-left).
This was actually the reason I started this branch hoping it'd be an quick fix, but I pulled back realizing the conditional styles wasn't a super quick thing.


convert some service classes to static props, run [gem gerrit]

Warnings

:warning:
This PR modified service code for gerrit but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for gem but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against b7737d44aaf8bc22539e00b521d23acfc9c97c46


Labels and extension meta data in containers

I would like to discuss ability to attach application-specific meta data to container images. Here are a couple of examples that come to mind:

bookeeping of versions of libraries included in the image that can be later inspected by security audit tools to update containers with obsolete/vulnerable libraries
adding application-specific information that can be used by implementation to execute custom actions, e.g. host restrictions (this container can only run on a host with > 60 GB or RAM)
adding custom signatures to the app-specific content in the image

For example, app container spec adresses this use-case by introducing labels:

labels (list of objects, optional) used during image discovery and dependency resolution. The listed objects must have two key-value pairs: name is restricted to the AC Identifier formatting and value is an arbitrary string. Label names must be unique within the list, and (to avoid confusion with the image's name) cannot be "name". Several well-known labels are defined:
version when combined with "name", this SHOULD be unique for every build of an app (on a given "os"/"arch" combination).
os, arch can together be considered to describe the syscall ABI this image requires. arch is meaningful only if os is provided. If one or both values are not provided, the image is assumed to be OS- and/or architecture-independent. Currently supported combinations are listed in the types.ValidOSArch variable, which can be updated by an implementation that supports other combinations. The combinations whitelisted by default are (in format os/arch): linux/amd64, linux/i386, freebsd/amd64, freebsd/i386, freebsd/arm, darwin/x86_64, darwin/i386. See the Operating System spec for the environment apps can expect to run in given a known os label.

After trying to use labels in practice, I can say that ACI's labels have the following limitations:

Value of the label is limited to string, what makes it hard to include structured data in the value
Label names are unique, but not enforced in the data structure that is presented as a list.

The useful part about labels is namespaces, that helps to identify the purpose of meta data and avoid collisions.
It would be very helpful to include the mechanism of adding meta data to the open container images that addresses some of the limitations listed above.

Some additional discussion can be found here:

https://groups.google.com/a/opencontainers.org/d/msg/dev/RF6qm-75IJ0/Jcz-CC_2DwAJ
https://groups.google.com/a/opencontainers.org/d/msg/dev/RF6qm-75IJ0/5zZ7VM73DwAJ

I second Solomon 1 in feeling like this is a useful feature, but
separate enough from “launching a container” to be worth keeping in a
separate place.  Can't folks who want labels just put them in
label.json (or wherever they like) in the bundle?
.
├── config.json
├── label.json
└── rootfs
 From: Solomon Hykes
 Subject: Re: Open Container Weekly Meeting - Aug 12, 2015
 Date: Tue, 11 Aug 2015 12:40:58 -0700
 Message-ID<EMAIL_ADDRESS> Cc: dev<EMAIL_ADDRESS>…

@wking FYI, we have decided to use the mailing list for discussion of features that don't exist yet.

On Tue, Aug 11, 2015 at 03:44:07PM -0700, Brandon Philips wrote:

@wking FYI, we have decided to use the mailing list for discussion
of features that don't exist yet.

Right, sorry.  It may take me a few iterations to break my fingers ;).
This discussion has moved to 1.
 From: Alexander Klizhentas
 Subject: Labels and extension meta data in containers #108
 Date: Tue, 11 Aug 2015 14:14:04 -0700
 Message-ID<EMAIL_ADDRESS> To: dev<EMAIL_ADDRESS>


[CI/Build] fix pip cache with vllm_nccl

the vllm_nccl package must be installed from source distribution
pip is too smart to store a wheel in the cache, and other CI jobs
will directly use the wheel from the cache, which is not what we want.
we need to remove it manually

@simon-mo please take a look and see if the modification of dockerfile is good. The test seems to be ok with the modification.

Yes. Also also manually test the openai image locally to ensure it has all the necessary dependencies.
We want to avoid using the devel image for testing and production in general

Ideal case:
nvidia/cuda:12.1.0-devel-ubuntu22.04 --> dev (install requirements) --> build (for building vllm wheels) and flash-attn-builder (for building flash-attn wheels)
nvidia/cuda:12.1.0-base-ubuntu22.04 --> vllm-base (install vllm from wheel) --> test ( for testing, only need to copy tests folder), and vllm-openai (for openai server, only need to install accelerate hf_transfer modelscope and start the server)

plz confirm locally that the openai server still work as expected.

don't get it. I think we have tests for api server 👀

Similar to release process, can you build the final container locally (DOCKER_BUILDKIT=1 docker build . --target vllm-openai --tag vllm/vllm-openai --build-arg max_jobs=1) and confirm the server works (docker run --runtime nvidia --gpus all -p 8000:8000 vllm/vllm-openai). Our CI uses the test container but not the openai server container.

Okay, confirmed it works.


Python bindings produce incorrect results for arrays in Fortran order

I realized that I'm getting very weird results when I read numpy arrays from csv files via the as_matrix() function of Pandas dataframes. Then, I found out that it's because of the order the matrices are stored in memory:
import nmslib as nn
import numpy as np

np.random.seed(42)
X = np.random.rand(1000, 50)

index = nn.init(method='vptree', space='l2')
index.addDataPointBatch(X)
index.createIndex()
print(index.knnQueryBatch(X, k=5)[0][0])

X2 = np.asfortranarray(X)
print(np.allclose(X, X2))

print(index.knnQueryBatch(X2, k=5)[0][0])
print(index.knnQuery(X2[0], k=5)[0])  # knnQuery works well

X3 = np.ascontiguousarray(X2)
print(index.knnQueryBatch(X3, k=5)[0][0])

Produces following output:
[  0  13 694 168 895]
True
[247 784  11 243 986]
[  0  13 694 168 895]
[  0  13 694 168 895]

As users may not really know about the order of the matrix, nmslib bindings must call np.ascontiguousarray() explicitly in addDataPointBatch and knnQueryBatch  without assuming that matrices are in C order.

@gokceneraslan thank you for looking into this, do I get it correctly that np.ascontigousarray() does help?

Yes, because it changes the order from Fortran to C.


Onboarding fail with 404

When starting for the first time the user-journey is great, but it ended for me at least, in a 404 page.
Of course is not a big deal because you can just reload the console and all was correctly created.

hi @hernan826 , could you mention when did you exactly see the 404 page?

Yes of course. I think my path was:

Login using Gmail into https://console.thenile.dev/
A form popups with the workspace.

I don't quite recall if it was when creating the workspace of my first database.
I thinks it was only a case of a bad redir, because the workspace or database was created.

The links in the readme also 404

Thanks for reporting. we fixed it


feat(style): pull in theme service and pre-loader

Description
What's included?

Pull in theme and pre-loader from ui-platform

Test Steps

[ ] npm ci
[ ] npm run serve
[ ] Login and test this view

Definition of Done

[ ] Adheres to Covalent, Angular-Material & Material Design patterns
[ ] All user-facing strings are properly stored in /src/assets/i18n/en-US.json
[ ] Changes are a11y compliant
[ ] Responsiveness is handled
[ ] npm run lint passes (runs tslint, stylelint, prettier)
[ ] npm run test (unit tests)
[ ] npm run e2e (e2e tests)
[ ] npm run build:prod (AOT, product build test)

Animated Gif

Also, we really need to change how the theme works to more observable based returning the object we need with the logo, monaco theme and what not. (separate thing tho)

Also, we really need to change how the theme works to more observable based returning the object we need with the logo, monaco theme and what not. (separate thing tho)

Opened an issue for this in UI platform since it needs more planning.

Waiting on https://github.com/Teradata/vantage-ui-platform/pull/54

Addressed both pre-loader and theme comments in ui-platform PRs: teradata/vantage-ui-platform#51 teradata/vantage-ui-platform#54, so ready for re-review.


Change the long commit message for PR#31

Yes Dan, it didn't fix it. I made an attempt to fix it, but there is a difference between merge and pick.  The github documentation spoke about changing 'pick' to 'reword', but the concerned commit message came as part of 'merge'.
Can you PTAL.

Abandoning it now.


fix: marimo edit with absolute path to directory

Fixes a bug in which marimo edit /abs/path/ would fail to open notebooks due to incorrect slicing.
Fixes a bug in which marimo edit /abs/path/ or /abs/path would fail when run in a directory other than /abs/path
Fixes #1895.

@mscolnick added unit tests


Added train by epoch for Trainer and added support for texts

Trainer

Added train function that will train with epochs instead of steps
- Added option to display graph (maybe remove since it requires matlib?)
Added checkpoint_every_epoch to init so checkpoints can be saved every X.

Data.py

Modified custom_collate so it wont pad if the data isn't a tensor

MeshAutoencoder

Was crashing if texts was in the args, added dummy parameterto prevent this.

Setup.py

The setup file was missing a comma

this is awesome Marcus! will take a look at it tomorrow morning and get it merged!

Btw since I don't really think grad_accum_every is very useful I removed it from the train function, what is your option?
I forgot and left grad_accum_every in the loss function, so if it wont be used in the train function it should be removed from:
self.accelerator.backward(loss / self.grad_accum_every)

Btw since I don't really think grad_accum_every is very useful I removed it from the train function, what is your option?
I forgot and left grad_accum_every in the loss function, so if it wont be used in the train function it should be removed from:
self.accelerator.backward(loss / self.grad_accum_every)

i'm sure researchers will want to stretch to the next level if this approach pans out (multiple meshes, scenes etc)
probably good to keep it for the gpu poor

Another thing :) I'm not very experienced in using github forks but it seems like the pull request added later commits then when I made the request.
I made bit of a error and replaced entire meshgpt_pytorch.py since there was some weird stash thing and I wanted to ensure it was up to date.  I reverted but it seems like that stash thing messed it up bit, please double check if this is the case

hey sorry, the caching stuff took up my entire morning
will revisit this PR tomorrow!

Hi! Thanks for your amazing job! May I ask why in MeshGPT_dem.ipynb has a
AttributeError: module 'meshgpt_pytorch.mesh_render' has no attribute 'combind_mesh_with_rows'


Disabled static route removes routes with same network learned from another service

[x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I am convinced that mine is new.

Describe the bug
Adding a disabled route and saving or
disabling a route and saving
or saving with a disabled route already configured deletes routes with the same network but different gateways.
This means it deletes routes otherwise used/configured, for example routes from/to openvpn or wireguard peers.
To Reproduce
Steps to reproduce the behavior:

Have an existing route, like a wireguard peer with allowed IP
Go to System->Routes->Configuration and add a disabled route with this IP, Save

After restarting the VPN the route gets added again, until someone hits the save button in the static route configuration.
Expected behavior
Not removing existing routes that were not manually added under System->Routes->Configuration
Or not removing routes that have the same destination-network but different gateways.
Relevant log files
root@home:~ # netstat -rn | grep <IP_ADDRESS>
<IP_ADDRESS>/32      wg1                US          wg1
steps to reproduce
root@home:~ # netstat -rn | grep <IP_ADDRESS>
root@home:~ #
disabling and enabling wg1 Local
root@home:~ # netstat -rn | grep <IP_ADDRESS>
<IP_ADDRESS>/32      wg1                US          wg1
just clicking save in the static routes screen still having the disabled route configured
root@home:~ # netstat -rn | grep <IP_ADDRESS>
root@home:~ #
Software version used and hardware type if relevant, e.g.:
OPNsense 20.7.8-amd64
FreeBSD 12.1-RELEASE-p12-HBSD
OpenSSL 1.1.1i 8 Dec 2020
OPNsense 20.1.8_1-amd64
FreeBSD 11.2-RELEASE-p20-HBSD
OpenSSL 1.1.1g 21 Apr 2020

the core system doesn't add disabled routes, only deletes them.
https://github.com/opnsense/core/blob/9121ee88cecfbad31e35fe4353a497c1d235f034/src/etc/inc/system.inc#L554-L556

Here is an easier way for reproducing: Just adding two Hostroutes to something like <IP_ADDRESS>/32
If tried adding them in different orders.
Also, confirmed on 21.1, bug exists:
OPNsense 21.1-amd64
FreeBSD 12.1-RELEASE-p12-HBSD
OpenSSL 1.1.1i 8 Dec 2020
The expected behavior would still be that opnsense wouldn't delete routes with the same destination-net and different gateways.
This configuration successfully adds a route:
root@home:~ # netstat -rn | grep <IP_ADDRESS>
<IP_ADDRESS>/32         <IP_ADDRESS>        UGS         re1

This configuration removes the top route:

This configuration adds the route to the routing table:
The routes are added to the configuration as seen in the screenshot, the disabled route was added first.
So on clicking "Save" opnsense is trying to delete routes to <IP_ADDRESS>/32 and afterwards the route to <IP_ADDRESS>/32 is added

the core system doesn't add disabled routes, only deletes them.
https://github.com/opnsense/core/blob/9121ee88cecfbad31e35fe4353a497c1d235f034/src/etc/inc/system.inc#L554-L556

Thanks for your response, just to be clear, I think the delete in line 556 needs to include the gateway ip for it to stop deleting routes of openvpn or wireguard. or other static routes like in my screenshots

that's probably the misunderstanding here, in FreeBSD (without using fibs), you can only have a single destination set, when defining it twice, there's no guarantee which one it will use. adding a constraint to prevent duplicates might be a good idea, but obviously won't fix your issue.

that's probably the misunderstanding here, in FreeBSD (without using fibs), you can only have a single destination set, when defining it twice, there's no guarantee which one it will use. adding a constraint to prevent duplicates might be a good idea, but obviously won't fix your issue.

I am not trying to have two routes with the same destination.
Imagine this scenario:
You have two gateways (DefaultGW & ExpensiveFallbackGW) to reach a destination.
DefaultGW is rather cheap, ExpensiveFallbackGW uses a path that charges a ridiculous amount of money per MB.
Your boss prohibits some kind of autofailover because of fear of costs.
So you add the static route using DefaultGW and you add the route using ExpensiveFallbackGW but check the disabled-checkbox, so some other tech just needs to disable the route using the DefaultGW and un-disable (enable) the route using the ExpensiveFallbackGW.
When you add the two static route in the order "DefaultGW" and then "ExpensiveFallbackGW", no route gets added to the system. The second route deletes the first route, even though it is disabled.
If you add the routes in reversed order, first the disabled and then the enabled route, the "default" works, but when trying to failover (enable the first, disable the second) no route gets added.
And the problem is not having a enabled(!) static route that deletes the route of some other process, but having a disabled(!) route doing this.

I wouldn't advise doing this, but if the problem is that the system can't always keep track if the differences, this is a duplicate of https://github.com/opnsense/core/issues/4621.
To keep it safer, we should probably prevent duplicates from being added (we can't just keep system and static ones in sync since it will interfere with dynamic routing protocols which are more suitable for the job anyways).
I'll leave the ticket open marked support for now, in case anyone else would like to discuss this further.

https://github.com/opnsense/core/commit/d24eeea7de7953fafd68a0e88b2d418aee33ed91 solves https://github.com/opnsense/core/issues/4621, let's close this issue as well with it.


Quick navigate: classes and symbols

Hi!
My library contains thousands of ActionScript classes. Is there any way to quickly navigate to a class/function/property (the same as the QuickNavigate plugin of FlashDevelop)?
Thank you!

 Alternatively, the keyboard shortcut is Ctrl+T (or Command+T on macOS).

Thank you!


[SMALLFIX] Prevent UFS access on journal replay for delete entries

@aaudiber @madanadit

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16665/
Test PASSed.


Wolvic 1.1 cannot launch after being forced closed when leaving security zone

When testing Wolvic 1.1 with Harmony OS <IP_ADDRESS> cannot launch again after being forced closed when user leaves the security zone.
The app will start but cannot reenter VR mode and bring up the launch screen. Just the Wolvic logo is shown for a brief moment and then your back in HVR Launcher. You can try this over and over again but app will not be allowed to launch again.
You need to leave VR by disconnecting the VR Glass, close the Apps in the 2D UI and then start over again.
Note even for normal launch as you just have started Huawei VR you may need 1-3 launch attempt before it can start.

The following are some info & log regarding the crash issue that happened when using HarmonyOS 3.0:
The 3dof app and 6dof app crashed 2 times after clicking, and can enter app the third try (Exit and enter again,  the crash recurred several times)
There are changes for the third party app. to use exact alarm ，need to add permission for this:
https://developer.android.com/about/versions/12/behavior-changes-12#exact-alarm-permission
In general, if app uses setAlarmClock(), setExact(), setExactAndAllowWhileIdle(), Exact Alarm is used. In Android 12, if there is no permission for SCHEDULE_EXACT_ALARM, APP will crash. ( you can test this before you make any code change, if there is no crash before code change, then you should be fine. )
Solution:

Add permission:

Return to the authorized UI:
The process logic of Google Pixel: Once App is started, it will check the permission; if no SCHEDULE_EXACT_ALARM permission, use toast to remind user to go to permission setting; if user does not enable the setting for alarm clock, there will be issues. (Suggestion is to use popup dialog, if user refuses to enable the permission, exit directly to avoid further problems)

We don't use any of the setAlarmClock(), setExact(), setExactAndAllowWhileIdle() directly in Wolvic. It might be however that android code that we call started to use that. We'll add that permission then.

We don't use any of the setAlarmClock(), setExact(), setExactAndAllowWhileIdle() directly in Wolvic. It might be however that android code that we call started to use that. We'll add that permission then.

Please give us a test apk for this as soon as possible, thanks very much.

Wolvic is now able to gets its launch parameters from a custom data URI that begins with "wolvic://com.igalia.wolvic", without the need for any extra values.
For example, this URI will open moonrider.xyz in kiosk mode:
wolvic://com.igalia.wolvic/?kiosk=true&url=moonrider.xyz
In Java code:
Intent intent = new Intent(Intent.ACTION_VIEW); intent.setData("wolvic://com.igalia.wolvic/\kiosk=true&url=moonrider.x
yz" );
context.startActivity(intent);
This functionality can also be tested from the command line:
adb shell am start -a android.intent.action.VIEW -d "wolvic://com.igalia.wolvic/?kiosk=true&url=moonrider.xyz"
Regards
PS: we're sending the 3DoF version as we did previously. We'll generate a 3dof&6dof version once we verify that the SDK fixes allows us to do so.

"Wolvic 1.1 cannot launch when leaving security zone"--This problem cannot reproduce in our demo with the latest .79 SDK(Test version) . If you still have this problem, please share the log.

Please give us a test apk for this as soon as possible, thanks very much.

We'll send an APK for testing with the AndroidManifest changes. But I insist, we are not directly using those APIs, so there must be a bug somewhere else.

Tested the 3DOF build shared with HOS2 and HOS3 and with SDK 78 and SDK 79 test (https://github.com/hms-ecosystem/OpenXR-SDK/blob/main/demos/HVR_demo/HVRSDK-v79-0923.apk)
Based on my testing there is no issue with relaunching 3DOF version from main launcher under HOS3.
However their is a regression with regards to back button and the popup UI to Quit Wolvic. Now when you press Quit nothing will happen. Only way to now exit Wolvic is by using the short press on the Home button on the 3DoF Controller.

Tested with latest HOS version <IP_ADDRESS> and SDK .79 (https://github.com/hms-ecosystem/OpenXR-SDK/blob/main/demos/HVR_demo/HVRSDK-v79-0923.apk) and using the latest 3DOF build that has been updated to support Android 12 AOSP.
With this setup the app can successfully be relaunched again after having been forced quit due to leaving safety zone.
So with these Android 12 AOSP fixes this issue can be solved.
However the BIG issue with Safety zone blue grid not being shown correctly is still open, and is tracked here:
https://github.com/hms-ecosystem/OpenXR-SDK/issues/30


Feature: data letter queue

This PR resolves Issue #55 .

Implemented Dead Letter Queue handler.
Adds last_job_status to job metadata.
Runs and Tests needs to spin up appropriate queues.
Test for handle_job_failure.

We should probably add some tests for the edge cases where it would fail ?
Also I'm correct that in this PR the DLQ is implemented but is never used by the orchestrator right ?

Please feel free to mention the edge case to run the tests on.
And yes this PR is for adding support of DLQ, after which we would setup DL-queue to be used in the future.
@apoorvsadana feel free to add more!
Thanks

@EvolveArt the DLQ is being used. You need to set it up on SQS/RabbitMQ etc. and when messages fail, they automatically go to the DLQ and they are moved to the failed state.


Remove Utils.appendMany

This pull request includes a

[ ] Bug fix
[ ] New feature
[ ] Translation
[x] Cleanup

The following changes were made

Utils.appendMany
Update jquery test version from 1.7.2 to 1.12.4

Utils.appendMany is used to support jquery version 1.7 which is long outdated. jquery v1 is still supported by the latest 1.x version

I have put this in the 4.1.0 milestone because this is slightly backwards-incompatible and I would rather have it go out in a patch version.

Marking this as needing a rebase but it's slated to roll into the 4.1.0 release again.


Python Question

So I am trying to use Kameleo in my python script that goes to a website and logs into it. I am saving the profile and then loading back when executing the script next time. I want a functionality check if the profile was deleted from Kameleo during the last execution of the script and if it still exists then the script will first delete it and then load it again...

Try to load the profile with a try-catch statement. If you catch an exception you can check for the error. If the returned HTTP Status Code is 409 (Conflict - already loaded), then you can delete it and load again.
Something like this:
    client.load_profile("YOUR_PATH")
except ProblemResponseException as e:
    if (e.status_code == 409)
         # delete and reload

To check if a configuration file has been deleted from Kameleo during the last script execution, you can perform the following steps:

Retrieve the list of available configurations from Kameleo using the Kameleo API or command-line interface.
Check if the configuration file that you are looking for is present in the list.
If the configuration file is found, delete it using the appropriate API or command-line command.
Reload the configuration file for further use in your script.

Here is an example to perform these steps using the Kameleo API in Python:
import requests

def check_and_delete_configuration(configuration_id):
    # Retrieve the list of available configurations
    response = requests.get('https://kameleo.local/api/v1/configurations')
    configurations = response.json()

    # Check if the desired configuration is present
    for config in configurations:
        if config['id'] == configuration_id:
            # Delete the configuration
            requests.delete(f'https://kameleo.local/api/v1/configurations/{configuration_id}')
            print('Configuration deleted.')

            # Reload the configuration for further use
            reload_configuration(configuration_id)
            break
    else:
        print('Configuration not found.')

def reload_configuration(configuration_id):
    # Your code to reload the configuration file goes here
    pass

# Call the function with the desired configuration ID
check_and_delete_configuration('12345')

Make sure to replace 'https://kameleo.local/api/v1' with the appropriate URL of your Kameleo instance. Also, implement the reload_configuration function according to your specific requirements.


Release Beta

Describe your changes
This release has mainly fixes and secondary indexes supporting ordering based on type.
How best to test these changes
Issue ticket number and link

Codecov Report
Patch coverage: 84.71% and project coverage change: +2.80 :tada:

Comparison is base (6463466) 62.37% compared to head (9df6b80) 65.18%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             beta    #1011      +/-   ##
==========================================
+ Coverage   62.37%   65.18%   +2.80%
==========================================
  Files         196      197       +1
  Lines       22041    22153     +112
==========================================
+ Hits        13749    14440     +691
+ Misses       7135     6480     -655
- Partials     1157     1233      +76

Impacted Files
Coverage Δ

value/secondary_value_order.go
77.77% <77.77%> (ø)

value/value.go
73.94% <78.33%> (-0.64%)
:arrow_down:

server/search/hits.go
79.31% <87.50%> (-14.81%)
:arrow_down:

server/services/v1/database/secondary_indexer.go
73.17% <90.90%> (+0.44%)
:arrow_up:

query/filter/key_builder.go
85.28% <100.00%> (-0.13%)
:arrow_down:

schema/fields.go
83.46% <100.00%> (+0.70%)
:arrow_up:

server/metadata/tenant.go
66.69% <100.00%> (+1.92%)
:arrow_up:

...ver/services/v1/database/secondary_index_reader.go
60.36% <100.00%> (ø)

... and 25 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Validators and Groups SBAT manage URL and metadata

[ ] call to modify validator URL in smart contract
[ ] Take name out of smart contract
[ ] reference format for metadata maintained at well known URLs
[ ] CLI changes
[ ] documentation

Actually gonna reopen this one to remind me to move out the data from the Validators contract


[Enhancement Request] Add Support For All Default iOS Default Browsers

Hi,
This is a great extension which is helping to customize Safari’s search engine.
Issue:
CSE lists DuckDuckGo, Sogou and Yandex
CSE does not list Google, Yahoo, Bing or Ecosia.
Request:
It would be greatly appreciated if an enchantment can be made to include all these (or more) in the available list.
I would be more than happy to contribute such an enchantment to this repo via PR, if that would be helpful.
Thanks and feedback will be appreciated

Suggestion:
In file content.js the following logic could be added:
if (Domain.includes('google')) {
// The current URL is in any .google. domain
}

This is not possible.
The domain must be specified in manifest.json first.
https://github.com/Cizzuk/CSE/blob/571526b75363e1096df5c1960670285cf5fcbb1d/Custom Search Engine Extension/Resources/manifest.json#L24
I could set this to all domains ("matches": [ "<all_urls>" ]) but CSE should work with minimal permissions.

Thanks for sharing that information.
I wasn’t aware that the manifest.js was used for the permission enabling.
It’s does seem that ccTLDs is supported.
(Per documentation I found from Mozilla and chrome https://developer.chrome.com/docs/extensions/develop/concepts/match-patterns#special https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns)
It does seem the only available options are:

List <all_urls> - not ideal
Limit support to specific TLD of google / yahoo / bing / ecosia - not ideal either
Specify every single localized TLD of google / yahoo / bing / ecosia - would require a user to enable each one manually and finds all existing TLDs of these domains

I could be missing something

https://github.com/Cizzuk/CSE/commit/b48d3061ce32a372b950c8108642c53595fc1a4b
I have tested with the regional settings for the United States, Japan, Mainland China, Taiwan, Hong Kong, and Russia.
I have added Google, Yahoo, Bing, Ecosia, Baidu, and 360 Search as options.
This should cover everything needed.

Thanks again for making these great enhancements.
Small follow up question:
When do you think this change would be released and made available in the App Store?

We will have to wait for Apple's review.
It should take a few days at most.