Support arbitrary ballots

Add support for a ballot that has arbitrary set of questions.  The vote picks one of them.

Hello @alex-voodoo, I would like to work on this issue.

You can take it if you want.  Let me know if you have any questions about the design.


Shorten type names?

RFC 356 specifies that names without prefixes should be preferred over names with prefixes - e.g., io::Error over io::IoError.
Currently, we use the latter naming convention - e.g., slab::SlabAlloc, slab::UntypedSlabAlloc, etc. We should abide by the proper, officially-accepted naming convention.
Open questions:

Should we rename ObjectAlloc? Probably not. It's in the object_alloc crate, and object_alloc::Alloc is pretty unwieldy - most people will want to use object_alloc::ObjectAlloc and then use the type as ObjectAlloc without the crate prefix.
Do we expect most people to use slab::Alloc (and other similarly-named types) as slab::Alloc or just Alloc? If it's the latter, then it may actually be more clear to leave it as is (SlabAlloc). This also avoids a conflict with the Alloc trait from the alloc crate, which is likely to be used by code that also uses a slab allocator.

I personally think you should keep the original names, if I'm importing an object to pass to as an argument, like you probably would with an allocator, I'd rather it's descriptive then perfectly follows naming conventions.


Viewer pre-full-screen event not raised on Esc from full screen

The Viewer event pre-full-screen is not raised when Esc is used to exit full screen mode, but is if the 'Toggle full page' toolbar button is used to exit.

Unfortunately, I don't think it is possible.
The fullscreenchange event is only triggered once the change has happened, which is too late to trigger the pre-full-screen event.
We are always triggering the full-screen event though.

Good point. I guess we should at least document this issue in the documentation for pre-full-screen.


Update kimchi_bindings lock files

Add missing dependencies in kimchi_bindings lock files which cause the build to fail in clean environments.
Closes #11695

Closing in favor of https://github.com/MinaProtocol/mina/pull/11679 which subsumes it


fix several flaky session tests

Codecov Report

Merging #578 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #578   +/-   ##
=======================================
  Coverage   90.81%   90.81%
=======================================
  Files          79       79
  Lines        5419     5419
=======================================
  Hits         4921     4921
  Misses        318      318
  Partials      180      180

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ff42100...83a9d0d. Read the comment docs.


Tweak RF capacity of Immersive Engineering's capacitors

My benchmark is the Hobbyist's Steam engine, filled with 4 buckets of water and 64 coal coke.
Reminder of Progression, LV is Steel, MV is Diamond, HV is Mithril.
I was not planning on changing the HV Capacitor it stores 4 MRF. Compared to the ElectriCraft RF Battery stores 60 TRF. The HV Capacitor will require Mithril but otherwise be cheaper then EleC Battery as not to require so many diamonds or a nether star.
My feeling is that a MV Capacitor should be able to store the total output of a Hobbyist's Steam Engine.
While a LV Capacitor stores 1/4 or less of that. It's primary use is to flatten any spikes in RF production, and give a small buffer.
I am currently running a test to see how much RF a Hobbyist's Steam Engine will create.

Done. LV is 80000. MV is 800000


Add compare quote section

Adds a new route quotes to the signer service. Can be called e.g. as follows {endpoint}/v1/quotes?provider=moonpay&fromCrypto=USDC&toFiat=EUR&amount=100. Supported providers are alchemypay ,moonpay, and transak
Note: while it's possible to combine the provider queries into one e.g. by allowing a parameter providers={}, I decided to keep them separate as this allows showing the results earlier in the frontend instead of having to wait for the response of all three of them on the server.
Creates a table for comparing the quotes of the different providers and shows them below the swap form

All three providers provide prices for EUR. Moonpay does not offer prices for offramping ARS while the others do.
The endpoints used are documented here:

MoonPay
Transak
AlchemyPay

We need to add 4 new secrets to the signer service. The following env variables need to be provided:

ALCHEMYPAY_APP_ID
ALCHEMYPAY_SECRET_KEY
TRANSAK_API_KEY
MOONPAY_API_KEY

I added all of them to the configuration of the signer-service in our infrastructure already.
I also changed the rateLimitWindowMinutes parameter to just 1 minute. During my testing I hit the limit quite easily so it might be better to be more forgiving with those parameters.
Closes #203.

Thanks for the comments @TorstenStueber, I'll address them later.

I could not test the actual app as the signer service on the preview deployment just returns 404 for the quote endpoints. I assume that this only becomes available after merging (?)

Yes, as we only have deployments of the signer-service for the staging and production branch but not any development branches, the deploy preview does not work. All secrets you need are accessible and shared with the team so you can also run it locally, I can point you to them if needed.

@TorstenStueber I addressed all your comments, please have another look. Thanks again for the thorough review.

Forgot about it again, my bad. You can still add comments or suggestions and we'll incorporate it in another PR @prayagd.

Something that came to my mind just now: Why do we call it "Compare fees" and not "Compare quote" (or similar). At the end this is not (just) for comparing fees but actually exchange rates.

I think both names are okay. I as a user am interested in how much the amount I offramp deviates from the 'ideal' (fiat to fiat) exchange rate for each provider. And I can consider this deviation to be a provider 'fee' or I can consider the resulting amount shown to be a 'quote'. I'm fine with both, so if you prefer using the term 'quote' in the context of this, I'm happy to change it.

Okay, let's just leave it as it is then.

You can still add comments or suggestions and we'll incorporate it in another PR

Listing down things

Replace "No hidden fees" with "You could save upto 13.94 EUR" the 13.94 EUR should be calculated based on the (Vortex quote - Best quote from competitor)
Add text to the detail section "300 USDC is all you pay, fees included", the 300 USDC should be replaced as per the user input
"Detail" text should be before the down arrow
The "Compare fees" section should always be visible, the user can scroll below and see it. For this there should be a default swap amount put in, the user can still click on the "compare fees" button, when they do they are taken to that section
In the "Compare fees" table the "Sending 200.00 USDC with" the 200 should be a input field synced with the input field of the above form

Will create a separate ticket for all these comments and suggestions so we can discuss there

In the "Compare fees" table the "Sending 200.00 USDC with" the 200 should be a input field synced with the input field of the above form

Isn't it a bit confusing to have two input fields that change the exact same value? Is the goal to improve the user experience on mobile as it's not possible to have both the table and the input field fit on the screen without scrolling?

The "Compare fees" section should always be visible, the user can scroll below and see it. For this there should be a default swap amount put in, the user can still click on the "compare fees" button, when they do they are taken to that section

So the "Compare fees" button will only make the user scroll down, nothing else?

Isn't it a bit confusing to have two input fields that change the exact same value? Is the goal to improve the user experience on mobile as it's not possible to have both the table and the input field fit on the screen without scrolling?

The reasoning is that the compare quote section might look like a static element, similar to what you would find on a landing page for marketing reasons.
To make it more obvious that this box actually determines up to date quotes dynamically based on the user input, it could make sense to just repeat the input field inside the box.


Swift Bridging Header not being generated after changing project settings

Hey guys,
I'm having troubles building the latest version of iOS mobile app.
After downloading the code and running "make pre-run" and "make run" the app launches and everything is ok.
But the second I modify anything in the XCode project settings, the build stops working giving the following error:

The following build commands failed:
CompileC /Users/dragosiancu/Library/Developer/Xcode/DerivedData/Mattermost-brtupfchwikpmkcesuxefuxedsfu/Build/Intermediates.noindex/Mattermost.build/Debug-iphonesimulator/Mattermost.build/Objects-normal/x86_64/UIPasteboard+GetImageInfo.o /Users/dragosiancu/Downloads/mattermost-mobile-1.32.0/ios/Mattermost/UIPasteboard+GetImageInfo.m normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler

This error is produced by line 11 of UIPasteboard+GetImageInfo.m because the Bridging Header is not generated and I can't figure out why.
I tried removing the Swift files and re-adding them to the project thinking the .pbxproj is missing some links. Tried restarting and cleaning a hundred of times but without any luck.
Can anyone help me, please?
Thank you,
D

The bridging header is already there https://github.com/mattermost/mattermost-mobile/blob/master/ios/Mattermost/Mattermost-Bridging-Header.h
Maybe you need to double check what is it that you are modifying

Not that one.
The Mattermost-Swift.h bridging header is not generating.
I am modifying only the app name, bundle id and Signing certificates & profiles. That's it.
Any ideas?

I am modifying only the app name, bundle id and Signing certificates & profiles. That's it.

Then why do you need it to create the bridging header I don’t really get it.
Have you tried doing that (app name, bundle id, profiles...) by building with the env variables + the command line to do so? Have you read https://developers.mattermost.com/contribute/mobile/build-your-own/ ?

Then why do you need it to create the bridging header I don’t really get it.
I don't, that's how xcode build works when you have swift code used inside obj-c code. It generates a "ModuleName"-Swift.h bridging header.

I have followed the steps shown here (https://developers.mattermost.com/contribute/mobile/developer-setup/run-on-device/)

Have you tried doing that (app name, bundle id, profiles...) by building with the env variables + the command line to do so? Have you read https://developers.mattermost.com/contribute/mobile/build-your-own/ ?

Yes, and the build still fails for the same reason. Does it work for you?
Thanks

So, for anyone encountering problems like this try using fastlane command from terminal instead of using the makefile commands cause it will give you a more specific error for you to correct.
Just run "fastlane" and then select the option you need.
Cheers,
D


[[DOCS]] Update jshint.js's path in README.md

committed as https://github.com/jshint/jshint/commit/d79ba10df03a404baef0b41102576f63c4449153 Thanks


Refurbish README

I'll address your comments, @gyorb.
Could you please elaborate on

Please check that doxygen still generates a well formatted output with the modifications into the built package.

I'm not sure what do I need to exactly check here... what do you mean by "modifications"?

I mean that we should not forget that form the markdown documentation html is generated during the package build with doxygen. It is possible that some markdown syntax changes are valid for github but not for doxygen. We should check that doxygen can process the new markdown files correctly (code blocks ...) and the generated html documentation style and content is what we expected.

Okay, did a touch-up for the user guide, now it renders well (for further reference, I have doxygen-<IP_ADDRESS> on my system).
The check and update or Ubuntu 16.04 are still on hold, for now.

I will create a new issue to test on Ubuntu LTS 16.04, after mentioning OSX support at the beginning the other changes looks good to me.

@gyorb: Sure we want to support DoxyGen (instead of GitHub Markdown) in the README? (Which described install procedures and such?)
For the rest of the files, I'm in the process of fixing some syntax in the docs/ folder.

At some point we might change to another documentation generation method or format (rst). Doxygen was used before the project was moved to github. If I remember correctly there were problems with the references between markdown files (sections) when we tried other methods, but that was long time ago.
It might be worth to try out pandoc or sphix for document generation.

My biggest issue were the syntax highlights... but GFM renders the Fenced code block rather well, and it looks neat (with some little tweak*) both in Doxy and on GitHub. I think this PR is ready now, considering that 16.04 dependencies were moved into a separate issue.
*: Did you know that you could put HTML tags into the markdown file and it works on GH and with DoxyGen? There was a slight issue with italic text in the [docs/authentication.md] section captions, but I got it.
(And this HTML also works in issue comments, see above :stuck_out_tongue_winking_eye: )


Update version: PIKCLOUD.PikPak version 2.6.2

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.9 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Resolves #199220
Resolves #199705

Microsoft Reviewers: Open in CodeFlow

[Policy] Reset Labels - not a duplicate


DatePicker doesn't show on Edge browser, scrolls the page down on IE and Edge

I'm doing a compatibility test pass and cannot get the angular-materialize datepicker to work on IE and Edge. Any workarounds here?

Any chance we could get help on this?

I can confirm that it happens. But i have no idea why it happens.
I might look at it at a later time, but don't expect anything soon.
You could also try to fix it yourself, and then send a pull-request if you manage to fix it.

Apparently IE and Edge doesn't handle it well when the popup has a parent which is not next to the input.
Fixed.


Add Node.js SDK and example - closes #538

This includes

Generated SDK pb files
SDK wrapper
Tests
Example project that uses the SDK

The example project was tested using local SDK server
Site documentation has not been added yet

I signed it!

Regarding it working, it works against the local dev server sdk-server.windows.amd64 --local but I've not tried it against our existing project so that would be worth doing. We could also mark as experimental until it has been battle tested.

Added some notes on build tooling - first step would be generation -- then probably adding the test suite to the make test command. If you have questions, pop into #development.
We will also want to add some docs :smile: to the website as well :scroll:
But this looks like a good first start!

This looks good I'll help you get that into our Makefile soon.

Just touching base - I'm guessing the things that are outstanding are (a) documentation and (b) integration with our build system?

Getting closer now :) I've added some documentation and also had a go at updating make test but not sure how to proceed on this so not committed.

This looks great to me! @Kuqd anything you wanted to touch on? (Since I know you were looking at this closely). Otherwise, I say this is good to merge.

@steven-supersolid - this will need to be squashed into a single commit please. But otherwise, I think we are good to merge this!


Can i revert this ?

Describe the bug
-Lost my Firefox history log and session with 30+ tabs
-Can't access my nerwork drives anymore
Desktop (please complete the following information):

OS: Windows
Browser Firefox
Version 89

Edit: forgot to mention, there are no system point I can restore to for some reason..

The script does not have built in restore points. If you were unsure, you should've tested in a vm or taken your own restore point.
I can tell you though, with 100% certainty, that the changes made by the script wouldn't have made you lose your Firefox history or tabs unless you also ran my Firefox privacy or security researcher script. This script only includes the STIG Firefox settings, which actually are configured to do the exact opposite of what you're having issues with.
The script disables SMB v1 and enables some SMBv2 hardening like requiring encryption and signing.
Additionally, it will disable anonymous access to any network share. All this is documented and mentioned here, which is mentioned in the readme.
I can't troubleshoot your NAS for you, but I suggest you review its settings and configure it to more secure standards.
The quickest answer here is to tell you to reinstall windows. If you're not used to running hardened versions of windows, especially so with DoD STIGs, you should know that it does disable quite a lot. Please take the time to review the documentation I have linked in the readme.
I also have another version of the script that doesn't do the hardening like in this script.
Please see here for the Optimize an Debloat script.


test: lint jest scripts

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included

Description of change
~Builds on #1558, the changes specific to this PR are in ae2bb7898553cc4356a75ebeedb0146ff87f7d94~
edit: rebased off latest develop with previous changes merged
Adds the recommended and stylistic rules from https://github.com/jest-community/eslint-plugin-jest
as well as checking that describe and it are used consistently across the tests.

Have retriggered Travis. Only had one test suite failure. Hopefully we can nurse this through. :crossed_fingers:

Rebased off latest develop


feat: allow configurable project names

This commit adds the ability to use configurable project names that are separate from the configured repo name (as in "/").
The main use case this feature enables is repositories that produce artifacts (possibly binary artifacts) which do not share the same name as the repository itself.
For example, project some-owner/some-repo may produce binary artifact abc-amd64-linux (--).

[!IMPORTANT]
Add support for configurable project names separate from repository names, with updates to src/main.ts, .github/workflows/test.yml, and README.md.

Behavior:

Allow separate configuration of project name from repo name in src/main.ts.
Update asset matching logic to include project name in src/main.ts.

GitHub Actions:

Add example job wrpc in .github/workflows/test.yml demonstrating separate project and repo names.

Documentation:

Update README.md to include usage of project parameter for different artifact names.

This description was created by  for 18451d2cb12c7a90c87c0e79aa5fc23dad70e72d. It will automatically update as commits are pushed.

Thank you @t3hmrman - this is an awesome contribution.
I'd like to make sure the project input isn't confusing, would it be possible to add an input called asset-name instead of repurposing the project variable?

Hey @jaxxstorm asset-name is about a billion times better, thanks -- I'll make that change asap.
Will also look into the failing tests!

OK, PR should be ready to go, all tests are passing on my fork and I've updated the docs!


api: options to constructor and add function should be simpler

It's currently not clear when an option should be passed to the WebTorrent constructor and when it should be passed to client.download. Consider unifying them if possible, or at least documenting this better.

Hi Feross, need help with this?


Eureka and Zookeeper SSL Configuration

Hi
I have 2 services registered with Eureka Server. One of the service has SSL certificate installed.
The rest endpoints exposed are https://.....
I want to access these endpoints from the other service that is registered with the Eureka Server via Feign Client.
What all Changes do i need to make to my feign client configuration to achieve the same.
I have seen a lot of posts saying to create a TrustingSSlSocketFactory and then create a Client Bean using the same.
But i am not able to understand is that the right way to achieve this or is there some other way of doing the same.
Spring-Boot Version : 2.1.6.RELEASE
Spring Cloud Version: Greenwich.SR2

See https://cloud.spring.io/spring-cloud-static/Greenwich.SR1/single/spring-cloud.html#_registering_a_secure_application

It worked after going through the link provided. Do we have similar something in case we are using zookeeper as discovery server?

Hi @ryanjbaxter  @spencergibb
If we want to contact a service over https which is registered with zookeeper, we can provide that by specifying the ssl-port using the below property
spring.cloud.zookeeper.discovery.instance-ssl-port=${port number}
This seems to be working in the latest version
Spring-Boot Version : 2.1.6.RELEASE
Spring Cloud Version: Greenwich.SR2
But when i try the same with the dependencies mention below, it does not work, the sslPort still shows as null on zookeeper.
compile(group: 'org.springframework.boot', name: 'spring-boot-starter', version: '1.5.2.RELEASE')
compile(group: 'org.springframework.cloud', name: 'spring-cloud-starter', version: '1.2.0.RELEASE')
compile(group: 'org.springframework.cloud', name: 'spring-cloud-starter-zookeeper-all', version: '1.0.4.RELEASE')
compile(group: 'org.springframework.cloud', name: 'spring-cloud-zookeeper', version: '1.0.4.RELEASE')
Is that a bug in release 1.2.0 of spring cloud or is there another way of doing it.

Why are you managing versions independently? What version of the bom are you using?

I believe the person who created the build.gradle in our project did not use bom or may be that version of gradle did not support bom, so that may be the reason why he did not use that.
I could see see the dependencies which i mentioned in my build.gradle for spring cloud, boot and zookeeper. and i need to enable SSl with these versions only.

Gradle has always had bom support via the spring boot Gradle plugin.

Those versions are no longer supported. Edgware.SR6 is the last boot 1.5 supported version of spring cloud

But can you please let me know if this was a bug in that version of spring cloud , as even after specifying the property spring.cloud.zookeeper.discovery.instance-ssl-port=${port number}, the ssl port is null.
Or is there a workaround for that ?

No, we don't support it anymore. If you upgrade and are still experiencing issues we can take a look and open an issue in spring-cloud-zookeeper. According to https://github.com/spring-cloud/spring-cloud-zookeeper/commit/69701d33c8d6ab74341e77209d75fc06301bdf02, instance-ssl-port was added in v1.1.2.RELEASE of spring-cloud-zookeeper and you are using 1.0.x


Spherical Area Lights

I still need to simplify and optimize the code, but here's a preliminary working version of Spherical Area Lights. See the example image below from a modified version of my cubism-demo-rs app, which you can also clone and run to see them in action.

Okay, it stopped working after merging in the PointLight changes from another branch. Need to figure out what I messed up.

Does it make sense to put it into something else than PointLight?
I looked at the five first APIs google showed me when searching PointLight and I'm just wondering about the semantics of radius on a struct with Point in it. None of those APIs used such a field:

roblox
apple
threejs
processing
p5js

Does it make sense to put it into something else than PointLight?
I looked at the five first APIs google showed me when searching PointLight and I'm just wondering about the semantics of radius on a struct with Point in it. None of those APIs used such a field:

roblox
apple
threejs
processing
p5js

Yes it makes sense for Point Lights as well as, eventually, Spot Lights. To the best of my knowledge, that's how Unreal Engine does it. Those light types just describe the cutoff behavior for the area lights, such as the range and/or the cone.

So in my cubism-demo-rs project I removed the code that used my new Spherical Area Lights and tested it with both bevy 0.5.0 and the latest directly from its github main branch. Here's what I observed:
0.5.0

latest

As you can see the latest appears broken even without my Spherical Area Light code. There appears to have been a lighting related PR that broke it within the last 24 hours. I believe this one is the culprit:
https://github.com/bevyengine/bevy/commit/5c4f3554f9db400cee6f5de67d06977ce0e99a97
Does anyone have any thoughts on how I should proceed?

There was an issue introduced in #1778 when having more than one light, it should be fixed by #1940

It sounds like it would be a good idea to add some kind of lighting demo that allows us to easily test 1-n light setups with different colors/sizes/etc. to prevent issues like this in the future.

I've applied the uniforms packing fix to my code and moved the radius value into that new vector rather than hijacking the color alpha channel. The PR should now be ready to go.


Point light : View frustum culling

Remove ambient from point light as they are view frustum culled.

Is this bug solved with using 0 ambient for point lights?

Closing in consultation with @LarsIngo; this is no longer a bug.


customFilterContainer cannot be passed custom options.

Hi,
I noticed a few of the customContainers provide ways to pass custom options to them but others do not.
eg: customPaginationContainer is able to be passed customPagerComponentOptions but customFilterContainer provides no such option.

Sorry about the delay in responding to this! We've recently released Griddle 1.0 and we've revamped the customization options. Please see the customization options documentation for more information.
I'm going to close this one for now but please feel free to open a new issue if any problems are encountered. 👍


Bot Command not working

Idk why the commands are not working help me or I did it wrong

Wait let me cheack again


[Release] Update Package.swift with 10.16.0 RC0 Firestore binaryTarget

Updated the URL to point to the Firestore 10.16.0 binary
Updated the checksum to match the new binary artifact

#no-changelog

Investigated the CI failure, see comment in https://github.com/firebase/firebase-ios-sdk/issues/11264.


searchAccounts can't handle<EMAIL_ADDRESS>search

The "@" case calls finger without prefixing with "acct:" (done in the url case) leading to an error.
I see also an issue when you transform the ActivityPub URI https://somedomain.org/someuser into web finger URI<EMAIL_ADDRESS>as there might not be a direct match. Serving_a_different_domain covers part of it.

<EMAIL_ADDRESS>might be handled by domainA.org webfinger (.well-known/host-meta).
domainA.org webfinger might return https://domainB.org/user_example_org

(example might equal domainA which might equal domainB. Who knowns?)
Imagine a world where, like email, the account is handled by google. host-meta is like DNS MX.
I dug a little bit further: On the « official » mastodon server, accounts have 2 aliases domain.org/users/user and domain.org/@user, the id being the first. Both URLs json having the first one as the id (which is also webfinger's application/activity+json), how about querying the account's json to get the id even if provided with an alias URL?
my 2¢

Thank you. The search function is pretty rudimentary at the moment, it’s just enough to support Toot!’s follow/favorite across accounts feature (long press) which is how I populated the follow graph in my instance.
It’s on my list to improve.


Broken line issue

Hi !
I would like to tell you that I encountered issues with use of bash-it.
First, when I write a command which not fits into the displayed width of terminal. As you can see on picture below, characters are erased at the beginning of the line by the end of new command.

Second one, when I want to use history with the upper arrow key, it seems to erase previous displayed lines on terminal and make it unreadable.

I didn't find someone which has same issues. If I made a mistake do not hesitate to give the link !
Thanks in advance,
Jérôme.

Isn't this similar to #1133?

Thanks for your answer!
Indeed, it seems to be the same issue. I use 'powerline-multiline' theme and it works better. I have just a little issue when I have a very long path such as example below :

Perhaps this issue already exists.

I had the same problem and I fixed it enabling 'checkwinsize' because it was disabled:
$ shopt checkwinsize
checkwinsize   	off

After activating it the problem disappears:
$ shopt -s checkwinsize

So I put the command in .bashrc

hey @jbuisine
Does the issue still exists?

Hey @NoahGorny !
It seems to be fixed now !


Error Upstream leads to correct downstream

Expected Behavior / New Feature
HttpStatus 404, page not found
Actual Behavior / Motivation for New Feature
Returns actual answer from API Server
Steps to Reproduce the Problem

i have the following config:

{
  "ReRoutes": [
    {
      "Priority": 1,
      "DownstreamPathTemplate": "/api/v{apiVersion}/cards",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
          "Host": "some_server",
          "Port": 5002
        }
      ],
      "UpstreamPathTemplate": "/api/v{apiVersion}/cards",
      "UpstreamHttpMethod": [
        "Get"
      ],
      "QoSOptions": {
        "ExceptionsAllowedBeforeBreaking": 2,
        "DurationOfBreak": 40000,
        "TimeoutValue": 15000
      }
    },
    {
      "Priority": 0,
      "DownstreamPathTemplate": "/notfound",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
          "Host": "other_server",
          "Port": 6000
        }
      ],
      "UpstreamPathTemplate": "/",
      "UpstreamHttpMethod": []
    }
  ]
}

i send  curl with right url request to ocelot and get httpstatus 400 with validation errors. It's ok.
Request:
curl -X GET ocelot_service_url:port/api/v1/cards
This request redirects to proper url

Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware[0]
      => ConnectionId:0HLFRNJ53L4DT => RequestId:0HLFRNJ53L4DT:00000001 RequestPath:/api/v1/cards
      requestId: 0HLFRNJ53L4DT:00000001, previousRequestId: no previous request id, message: Downstream url is http://some_server:5002/api/v1/card

then i send curl request with wrong url:
curl -X GET ocelot_service_url:port/api/v1/rsacs/cards
It also redirects to proper url and return answer...

Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware[0]
      => ConnectionId:0HLFRNJ53L4DS => RequestId:0HLFRNJ53L4DS:00000001 RequestPath:/api/v1/rsacs/cards
      requestId: 0HLFRNJ53L4DS:00000001, previousRequestId: no previous request id, message: Downstream url is http://some_server:5002/api/v1/cards

In solution i'm just using:
services.AddOcelot(_cfg);
What am i doing wrong?
P.s. can send full log for steps 2 and 3
Specifications

Version: ocelot 8.0.6
Platform: debian
Subsystem: docker

@Mar4eli I have been away on a business trip for the last week so haven't had time to help with issues! Sorry for slow response.
Try this configuration..it worked OK for me! I got an error about invalid json when starting Ocelot.
{
  "ReRoutes": [
    {
      "Priority": 1,
      "DownstreamPathTemplate": "/api/v{apiVersion}/cards",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
          "Host": "some_server",
          "Port": 5002
        }
      ],
      "UpstreamPathTemplate": "/api/v{apiVersion}/cards",
      "UpstreamHttpMethod": [
        "Get"
      ],
      "QoSOptions": {
        "ExceptionsAllowedBeforeBreaking": 2,
        "DurationOfBreak": 40000,
        "TimeoutValue": 15000
      }
    },
    {
      "Priority": 0,
      "DownstreamPathTemplate": "/notfound",
      "DownstreamScheme": "http",
      "DownstreamHostAndPorts": [
        {
          "Host": "other_server",
          "Port": 6000
        }
      ],
      "UpstreamPathTemplate": "/",
      "UpstreamHttpMethod": []
    }
  ]
}

If it still doesnt work please send me, program.cs, startup.cs and the full logs at trace level if possible.

Yes, my bad. I forgot one "}" in example config for ticket.
But it is not working.
I have launched locally project with this configuration.
Test 1. Correct url
result: correct downstream url
Logs:
Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware:Debug: requestId: 0HLG1SNBA0U0B:00000002, previousRequestId: no previous request id, message: Downstream url is **http://some_server:5002/api/v1/cards**
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0B:00000002, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: OutputCacheMiddleware; /api/v1/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0B:00000002, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: HttpRequesterMiddleware; /api/v1/cards
Ocelot.Requester.HttpClientHttpRequester:Debug: requestId: 0HLG1SNBA0U0B:00000002, previousRequestId: no previous request id, message: Cache key for request is **GET:http://localhost:59219/api/v1/card**s

Test2. Wrong url
result: still correct downstream url 0_o
Log:
Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/1.1 GET http://localhost:59219/api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: no request id, previousRequestId: no previous request id, message: MiddlewareStarting: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: no request id, previousRequestId: no previous request id, message: MiddlewareStarting: Microsoft.AspNetCore.Cors.Infrastructure.CorsMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: no request id, previousRequestId: no previous request id, message: MiddlewareStarting: TransitionToOcelotMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: no request id, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: ExceptionHandlerMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Errors.Middleware.ExceptionHandlerMiddleware:Debug: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: ocelot pipeline started
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: ResponderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: DownstreamRouteFinderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.DownstreamRouteFinder.Middleware.DownstreamRouteFinderMiddleware:Debug: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Upstream url path is /api/v1/aaaaaaaaa/cards
Ocelot.DownstreamRouteFinder.Middleware.DownstreamRouteFinderMiddleware:Debug: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: downstream templates are /api/v{apiVersion}/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: HttpHeadersTransformationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: DownstreamRequestInitialiserMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: ClientRateLimitMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.RateLimit.Middleware.ClientRateLimitMiddleware:Information: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: EndpointRateLimiting is not enabled for /api/v{apiVersion}/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: ReRouteRequestIdMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: AuthenticationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Authentication.Middleware.AuthenticationMiddleware:Information: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: No authentication needed for /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: ClaimsBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: AuthorisationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Authorisation.Middleware.AuthorisationMiddleware:Information: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: /api/v{apiVersion}/cards route does not require user to be authorised
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: HttpRequestHeadersBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: QueryStringBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: LoadBalancingMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: DownstreamUrlCreatorMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware:Debug: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Downstream url is **http://some_server:5002/api/v1/cards**
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: OutputCacheMiddleware; **/api/v1/aaaaaaaaa/cards**
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareStarted: HttpRequesterMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Requester.HttpClientHttpRequester:Debug: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Cache key for request is GET:http://localhost:59219/api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: HttpRequesterMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: OutputCacheMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: DownstreamUrlCreatorMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: LoadBalancingMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: QueryStringBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: HttpRequestHeadersBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: AuthorisationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: ClaimsBuilderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: AuthenticationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: ReRouteRequestIdMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: ClientRateLimitMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: DownstreamRequestInitialiserMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: HttpHeadersTransformationMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: DownstreamRouteFinderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: ResponderMiddleware; /api/v1/aaaaaaaaa/cards
Ocelot.Logging.OcelotDiagnosticListener:Trace: requestId: 0HLG1SNBA0U0C:00000001, previousRequestId: no previous request id, message: Ocelot.MiddlewareFinished: ExceptionHandlerMiddleware; /api/v1/aaaaaaaaa/cards

I'm expicting that wrong url would return 404 and not some cached(?) correct url.

@Mar4eli cool thanks for the extra info I will take a look ASAP.

@TomPallister @Mar4eli I reproduced this problem and found, that regexp of variable named RegExMatchOneOrMoreOfEverything in UpstreamTemplatePatternCreator class has a value ".+". In this case we accept any value, but i think , we should ignore /(slash) when passing values in url

@MikeBogsy awesome, please submit the PR and I will take a look!!!


Add manual bindings for async functions

[x] I agree that my contribution may be licensed either under MIT or any version of LGPL license.

Added:

Gtk.FileDialog.OpenAsync
Gtk.FileDialog.SaveAsync
Gtk.FileDialog.SelectFolderAsync
Gtk.FileLauncher.LaunchAsync
Gtk.FileLauncher.OpenContainingFolderAsync
Gtk.UriLauncher.LaunchAsync

I don't think that throwing an exception on error like it's done in WebView is desired behavior, error is set even if a dialog was simply cancelled by the user, which is definitely not a critical error and I think just checking for null/false makes more sense:
Related: #900

/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Public/FileDialog.cs(1,1): error CHARSET: Fix file encoding. [/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Gtk-4.0.csproj]
/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Public/FileLauncher.cs(1,1): error CHARSET: Fix file encoding. [/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Gtk-4.0.csproj]
/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Public/UriLauncher.cs(1,1): error CHARSET: Fix file encoding. [/home/runner/work/gir.core/gir.core/src/Libs/Gtk-4.0/Gtk-4.0.csproj]

Ugh... What does that mean? 😓 Files are just ASCII text.

You should be able to run dotnet format GirCore.Libs.slnf in folder src which should fix those things. If it does not work you can try to specify the csproj from GTK directly to only Format the GTK project.

One more thing is necessary. If the ...Finish method can return null (see documentation) then it is necessary to check the return value for IntPtr.Zero after the GLib.Error.ThrowOnError`:
Rough sample:
if(result == IntPtr.Zero)
{
tcs.SetResult(null);
}
else
{
//here original code to get and set the result in the task completion source.
}

Added Gtk.FileLauncher.OpenContainingFolderAsync

Looks good to me. Thanks for your contribution :rocket:


Updates reference assemblies, since the nuget packages are not up to date

Updates reference assemblies, since the nuget packages are not up to date
We'll switch back to the nuget packages once they have the correct bits in them.

👍  if you've verified they are signed

I have


Test on ARM failed

I'm currently using a Surface Pro X and tried your arm build.
It fails like this:
Installing...
ERROR:Installation Failed!
HRESULT:0x8007019e
Press any key to continue..

Don't hesitate to ask if you need any help or test on my side ! Thank for your work :D

Wow! Thats amazing!
Thank you!
But, I think the error code is when the WSL function is not enabled.  Please check again.

Ahaha, I feel really dumb. I'll test again and let you know :D

I tested works on ARM64


Looking for various statistical operations

Hi, I'm wondering if median (not average) or standard deviation are available as alasql query aggregators or would I need to build them (or use other libraries for this)? If so, any tips would be appreciated, since the documentation on aggregators seems a bit slim. Thanks!

You can use:

AVG()
MEDIAN()
VAR()
STDEV()
VARP()
STD()

Please, let us know if you need other functions.

I will expand the wiki with this info

Great, thanks for the prompt reply. I had tried those - but I apparently also had some data problems. Now that I've corrected them it's working!


Improve Magento 2 Varnish VCL

Allow MAGENTO_MODE to be passed in.
Support additional IP addresses for PURGE

Fixes #155

Looks good to me 👍


No way to ignore specific clients in new UniFi device tracker integration

Home Assistant release with the issue:
0.97
Last working Home Assistant release (if known):
0.96b5
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io
Component/platform:
https://www.home-assistant.io/components/unifi/
Description of problem:
Before the UniFi device tracker was merged into the integration, devices would be added to known_devices.yml which would allow them to be ignored per device. There was also the option to set "track_new_devices" to "false" to ignore all new devices. There doesn't seem to be a way to do this now.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
device_tracker:
  - platform: unifi
    host: unificontroller.mynetwork.local
    username: !secret unifi_username
    password: !secret unifi_password
    verify_ssl: false
    ssid_filter:
      - 'MyCoolSSID'
    track_new_devices: false

Traceback (if applicable):

Additional information:

Having the same problem after upgrading today.

Same here... Super annoying to have like 40-50 entities I don't care to see in HA now.

So I found a PR for this in one of the betas for 0.97, but it looks like something is wrong with the documentation as that change isn't showing up.
Adding dont_track_wired_clients: true kind of works, but I still have a few devices showing up.

@dummptyhummpty Did you add it to your config and it worked? Does not appear to work for me unless I need to manually delete the "wired" entities

@glassbase I added it, removed all of the wired entities from the entity registry and rebooted. Some of them still came back, but less than before. So yeah, seems like it's not working 100% correctly.

If you get wired entities then maybe your configuration isn't mapped to your config entry. A common mistake seems to be not using the site name rather than the site is previously supported by the device tracker

@Kane610 I'm using the same site name in the Integration configuration and in my configuaration.yml

This isn't just wired devices, it tracks all new wifi devices and adds cards for them in the UI and entities in Entity Registry. Now I have 20 wifi devices all showing up in the UI.
Previously we could set "track_new_devices: false" and then on specific devices we could use "track: true".
This way I could track only mobile phones on wifi and wouldn't get the clutter of the other 20 devices.

Yeah I have 60 wifi devices on my network. Just want to track 2 of them, rest is just cluttering up the UI 😕

@nicr4wks That’s a good point. I got confused and forgot about that.

The reason this is happening is that each device is now an entity.  So far the only way I've found to remove them is to use the customize functionality to hide them from the UI but this is quite cumbersome if you have a lot of clients on your network.

I think the primary purpose of the UniFi integration is presence detection with device_trackers.  Not as some sort of discovery and network management tool.  I just don't see how, for most people, spontaneously generating new entities for each random WiFi device is expected or desired behavior.
Please restore the old behavior as a default.

Yes, please make default to track NOTHING unless i tell it to!  I don't need a device tracker for every. single. person. that's ever connected to my wifi.... pretty sure no one needs a device_tracker for their thermostat (or light switches, or refrigerator, or bathroom scale, or...)

I second the default to NOT track devices (@steve28); I'd rather tell it which ones I want tracked since those are fewer (just 2) than the 60 devices on my network.

Since I am a heavy user of this integration, I would also like to voice my concern with known_devices.yaml being removed from the Presence Detection via UniFi.
I currently have 45 devices tracked by Home Assistant with the UniFi integration,  2 of which I actually need tracked.
Please do integrate known_devices.yaml again, or allow us to set a default to not track the entities it creates and to disable tracking for the entities it has already created.
I really hope this gets fixed someday, UniFi tracking was the best alternative for Owntracks in my scenario, and it has worked flawlessly ever since.

To handle ignoring of entities of UniFi which you don't want visible in hass Paulus shared this on the 0.97 release blog post.

Disabling entities is no longer going to be the responsibility of integrations but of Home Assistant core via the entity registry. Disabled entities will no longer be added to the state machine.
As a user you should not aim to manage what is in the state machine. With Lovelace you pick and choose the entities that you want to see.

https://community.home-assistant.io/t/0-97-apache-kafka-fortigate-twente-milieu/130480/90?u=robban
I will talk to him during the upcoming week about me implementing this in the core.

I think the main issue here is that even transient entities on your network get created as device_trackers.  I understand the philosophy of not trying to manage what goes into the state machine... I just think that this can lead to lots of garbage in the state machine.
For example, I don't save every phone number I have ever called or that calls me in my phone book.

Ok, so how do you suggest we solve this going forward?

The main reason I have an issue with this breaking change, is the fact it makes all of my POE enabled devices act as a switch. I have an automation setup to turn off all switches, lights, etc to turn off at 2:00 a.m. every night, which in turn makes my VoIP phone and all my security cameras to turn off. I ended up removing the integration completely until there is an option to exclude devices on your network.

@kane610 To answer your question, we need a way to not add all devices as default and only include the ones we want. I can honestly deal with them showing in the integration as inactive, but I don’t want them anywhere else in HA. They’re would also need to then be some kind of cleanup for devices that haven’t been seen in X amount of days.
I really appreciate the work you’ve done, but it seems as if this change shouldn’t have been made until these questions had answers.

Perhaps a sort of white-list on the device tracker or part of the entity core if that's where hass is headed? If it's on the core then I think there should be an option to apply per tracker type (one white-list for unifi-tracker, separate white-list for nmap, etc).
We can approve devices via MAC, entity.id, etc that hass will pay attention to and everything else can automatically be disabled or not even entered in the first place.
Computers I'm repairing, devices I'm testing, devices i'll never see again, devices belonging to friends. Things constantly moving on and off wifi have no purpose whatsoever being added in to hass so it can track them forever and a day.

I'm all for a whitelist as well. When it comes to network devices we all have a lot of transient ones so using an all-in network tracker just doesn't make sense.... The only problem is how to make this fit into the future of HASS as @Kane610 mentioned.

How do other integrations handle this problem? Unifi can’t be the only integration that needs the ability to whitelist devices.

There's two things that contribute to this problem that are related

the deprecation of the known_devices.yaml file (probably related to...)
the adoption of this architectural principal  that's used to justify the nature of this change; that integrations ought not to make decisions on what data is exposed, but that the user should via the UI

Personally, I think that either that architectural principal is too broad or wrong; that probably what was intended was something like not forcing the integration to choose which of the myriad set of data should be available from some, e.g., weather API -- leave that to the user.
As I've tried to argue in another forum, I think this architectural principle is a fine thing to apply when the set of data that's exposed is relatively static and bounded.  And that at the time the integration is installed/configured, all the  information needed is available for the user to then decide what to expose or not.
The problem here is that it's not the types of information that needs to be selected by the user for use, but which of the unbounded number of instances are useful.  And this is why this generalized mechanism needs some generalized whitelisting capability.  Consider how much worse this all falls down if you had a bluetooth-based tracker that generates all these entities.  And you're operating Home Assistant in a high population density environment with a lot of people walking by with their phones.  And in that case, it's not authentication is a barrier to a bluetooth device being visible while scanning..
In the mean time, I'm moving to yet another docker container running a python script that polls the UniFI API and selectively publishes data to MQTT; and I'll just configure MQTT device_trackers.  Until that breaks.

@rkreterfield do you use anything but device tracker? Setting the user to a viewer account would disable the POE control. Or create a group to filter what you want to control.

I just gotta say, reading through https://github.com/home-assistant/architecture/blob/master/adr/0003-monitor-condition-and-data-selectors.md i'm disappointed to see that similar concerns that are being raised here were also raised there but appear to have been simply ignored without any explanation.

We can probably have config options to include and exclude as we do for other integrations. Users can then include the mac-address of the devices that should be included/excluded from HA.

Except that there needs to be a way to do the inclusion/exclusion from the GUI.

Why not have the ability to turn on or off tracking of new devices in the integration itself especially now that known_devices is now defunct?
The other option I can see would be a workaround, but if you delete an entity from the integration it no longer comes back unless you remove and re-add the integration or even click a "re-scan" button or something similar?
Basically, as it is it's flawed as I do not agree you need anything in the state machine.
Like others I have many devices that come and go on my network that I really do not want to see appear in the entities list - the only reason I use the UniFi integration was device tracking - of which most if not all people will only ever want to track one or two devices anyway!

I just want to add that this also causes unwanted functionality for other lovelace cards that have dynamic inclusions of entities. e.g. fold-entity-row or monstercard

Why not have the ability to turn on or off tracking of new devices in the integration itself especially now that known_devices is now defunct?

This is what I was expecting to exist when I started using this integration.
To clarify: Not only new devices, but for every device. Just a toggle that works the way track: false worked with known_devices.yaml
For me the most annoying thing is to see these event in logbook that I don't care about. I know there are ways to customize this, but it seems quite cumbersome to to exclude all device_tracker entities that I don't want to show up in logbook

I've been talking to balloob and will start looking at a hass generic way to config disabling new entities

@Kane610 Here is what would make sense to me:

Keep discovered devices for x number of days after "last seen" -> purge after x.
Do not track by default; do not add bubble to UI.
If device is added to a Person - start tracking but do not add bubble to UI -> Person has a bubble.
If device is added to a Person - pause "x days purge".

Our first step is to utilise the block functionality of entity registry;
We will introduce an option to config entries that will allow the user to disable creation of new entities. They will only pop up in the entity registry as disabled entities. The user can then control what entities are wanted from each config entry

@kane610 Thank you for coming up with a solution to this issue!

I'm still experiencing issues with this in the latest homeassistant version 101.3.
Unifi Integration, despite my unchecking of the settings area as well as disabling the option for tracking new entities still continues to mark all the devices on my network as "not_home" or "home".
I cannot get it to ignore these items and only track two of our devices on the network.

You mean you have selected to not track any client?

Currently I have like 20+ device_tracker entities:

I have the setting to "track network clients" on currently

and the other "enable newly added entities" is disabled

Prior to upgrading I had all of these entities disabled and turn ALL of these options off, only to enable two specific phones manually to track. However after upgrading and seemingly despite turning this options off and/or on, it continues to track a multitude of devices.
What would be the proper method for only tracking two clients on the network? I don't mind doing it again, I just can't seem to reproduce the same thing I had working already.

Disable track clients and enable those you want

Thanks, my apologies I thought it was strange though because I had this setup prior to upgrading home assistant and it seemed like it got re-enabled for all entities again.
I went and disabled "track network clients" then went to the entity registry and re-enabled the two phones. Waited a minute or so and those are the only ones being tracked now in the integration.

Great! I think there is enough information in this issue to lock it. I will improve documentation for integration.


Login process improvement

After login, the user is provided an option to log in as a user, seller, or admin.
I think It is useless to ask it in case a user is not an admin, as selecting user or seller is same, we should redirect him to the home page directly without asking,
If the user is an admin, we should give an option to log in as admin or user.

What are your thoughts on this @Mrhb787

I have Fixed all related issues regarding this.


need doc on migrating dnx unit test projects to dotnet unit test projects

@cesarbs

do we still need this @Rick-Anderson?

@danroth27  @cesarbs  do we need doc on migrating dnx unit test projects to dotnet unit test projects

At this point I believe this is low priority and is just going to get to less important. I think we should just close this one out.


Is cpus_limit related with cpu usage?

I am confused about cpus_limit.
1、May I ask what is cpus_limit really means?
2、I want to calculate the cpu usage of each container/task, so I use prom statement like:
irate(cpu_user_seconds_total{id=~"$busi.*"}[5m])*100,
but I get some result that is more than 100. That's my number two confusion.
3、Is cpus_limit related with cpu usage?

hi~ do you finally to know how to calculate the cpu usage?


[FEATURE] Automatic online RWX volume expansion

Is your feature request related to a problem? Please describe (👍 if you like this request)

Now we could only do expansion manually for RWX volume. https://longhorn.io/docs/1.5.4/volumes-and-nodes/expansion/#rwx-volume
Describe the solution you'd like

When doing an RWX volume expansion by applying a modified manifest of the PVC or Longhorn UI, it could also automatically expand the volume filesystem on the shared manager pod.
We might be able to add a new ShareManagerClient API FilesystemExpand as FilesystemTrim,
https://github.com/longhorn/longhorn-share-manager/blob/master/pkg/rpc/smrpc.proto#L7-L11
Describe alternatives you've considered

Additional context

Per the investigation at https://github.com/longhorn/longhorn/issues/6216#issuecomment-2220812095, https://github.com/longhorn/longhorn/issues/6216#issuecomment-2220861850, and https://github.com/longhorn/longhorn/issues/6216#issuecomment-2293835724, we should also make NodeExpandVolume a no-op for RWX volumes to avoid weird behaviors.

This is accomplished by the changes in https://github.com/longhorn/longhorn/issues/9736

Closing in favor of #9736


Fix duplicated code introduced in affed43e461106afcf4dcaaf500fe0763dbf5f88

Hello,
It seems you missed something here : https://github.com/eternicode/bootstrap-datepicker/blob/master/js/bootstrap-datepicker.js#L214
This PR should fix it, I ran the tests suite, nothing failed, but I'm not sure this part is covered.
Have a nice day.

Thanks for the PR, I'm gonna figure out what has caused this duplicate line and what it should be! Will reply later on to this PR when I've found the cause!

Hi,
Sorry I was wrong, I deleted the wrong line, I kept the commit author intention but it was wrong.

There is nothing wrong there, both lines are used to keep startView in range between minViewMode  and maxViewMode.
This PR should not be merged and closed.

Ping @acrobat  ;-)

1 Packet lost. try again ;-)
ping @acrobat  :-)

oh sorry :D I guess @Azaret is right, as the 2 lines do some different logic


Roll Packages from 75ede70ca5f0 to b0a58d551cbf (7 revisions)

https://github.com/flutter/packages/compare/75ede70ca5f0...b0a58d551cbf
2023-04-10<EMAIL_ADDRESS>[in_app_purchase_android] Implement BillingClient connection management and introduce BillingClientManager (flutter/packages#3303)
2023-04-09<EMAIL_ADDRESS>Roll Flutter from 3ea2d72446c6 to c55d713ca885 (4 revisions) (flutter/packages#3668)
2023-04-08<EMAIL_ADDRESS>Roll Flutter from aa6a0a9dea63 to 3ea2d72446c6 (18 revisions) (flutter/packages#3666)
2023-04-07<EMAIL_ADDRESS>[various] Update Pigeon in Obj-C plugins (flutter/packages#3662)
2023-04-07<EMAIL_ADDRESS>[various] Enable warnings as errors, and all warnings, for Android lint (flutter/packages#3648)
2023-04-07<EMAIL_ADDRESS>[pigeon] Remove version from most test code (flutter/packages#3660)
2023-04-07<EMAIL_ADDRESS>Roll Flutter from a086c640dcc4 to aa6a0a9dea63 (25 revisions) (flutter/packages#3661)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-packages-flutter-autoroll
Please CC flutter-ecosystem<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


splice annotations

From Sarah Hunt (seh@ebi.ac.uk):
Matt Hurles group at Sanger have been looking into the impact of variants on splicing and observed:

that there is some heterogeniety within the canonical splice sites; the donor +5 site is under stronger purifying selection and is more enriched for pathogenic mutations than all other non-canonical splice sites variation at the donor +2 site is typically less damaging than the other 3 canonical splice sites.

that the polypyrimidine stretch flanking the acceptor site extends beyond the ‘splice_region’ window and that mutations from pyrimidine to purine are more damaging than other changes.

They requested we annotate these regions more precisely in VEP. We discussed the suggestion on a VATT call and there was broad concensus this would be useful. We already have the term 'splice_donor_5th_base_variant', so would like to propose 2 additional terms:
splice_polypyrimidine_tract_variant
Definition: variant falls in polypyrimidine tract at 3' end of intron, between the 17 and 3 bases from the end
(acceptor -3 to acceptor -17)
Parent: splicing_variant
splice_donor_region_variant
Definition: variant falls in the region between the 3rd and 6th base after splice junction (5' end of intron)
Parent: splice_site_variant
These are draft suggestions, of course - any improvements would be welcome! It might make sense to make splice_donor_5th_base_variant an child of splice_donor_region_variant, but I don't know if it's too disruptive to introduce new parents.
What do you think?

We have added the following terms:
SO:0002169 splice_polypyrimidine_tract_variant
SO:0002170 splice_donor_region_variant
The definitions are the same as the ones you proposed. We made splice_donor_region_variant a child of splice_region_variant since the definition includes the 3rd and 6th base after the splice junction.
Let us know if these terms and their placement in the ontology work for you.
Nicole


Add graphs to team modals

If Kalahari can do it, we can too.

For reference: the relevant library is chartist-js.


Does not work in Astro

Describe the bug
Get an error in Astro whhen using a component containing  or any other component from this repo.
Tried both client:load and client:only. Would seem to me that client:only should work, because it is just svelte, but maybe my knowlegde in lacking here.
onMount function is not fired at all.
error:
[HMR][Svelte] Unrecoverable HMR error in <SvelteStripe>: next update will trigger a full reload
Reproduction

Create an astro project
create an astro page
create a svelte component with the following code:

Hello svelte stripe

<form on:submit|preventDefault={confirmPayment}>
  <Elements
    stripe={stripePublic}
    {clientSecret}
    bind:elements
  >
    <PaymentElement />
  </Elements>

  <button>Pay</button>
</form>

import it with  or

Severity
blocking all usage
Additional Information
Astro version 3.0.7

Unfortunately I was just testing some stuff out and refactored the code to using the native javascript stripe elements. I will leave this open for once I get back to working with stripe on my astro project

Looking into the issue further, it appears Astro is geared towards server-side rendering. But svelte-stripe is based on @stripe/stripe-js, which is a client rendered.
So adding svelte-stripe as a dependency to an Astro project directly wouldn't work.
Instead, you can build a separate .js that you can load in your Astro page on the client:

Create a new vite project pnpm create vite payment-page
Choose the svelte template (without SvelteKit)
Add a component for your payment section, ie MyPaymentCard.svelte
Place some components from svelte-stripe in your payment component
Configure src/main.js to specify where to mount the MyPaymentCard component
Build the project pnpm build and copy the build to your Astro project's /public folder
Import the script in your Astro payment page


remove all 'set -e' bash options from test-lib

This commit is considered a hotfix. Some more thorough analysis needs to be done in the future.

[test]

[test]


Create a demo on Hugging Face Hub

Hi!
Very cool work! It would be nice to create a demo on the Hugging Face Hub!
This is a step-by-step guide explaining the process in case you're interested.
Please let us know if you would be interested and if you have any questions. 😊

Hello, thank you for your interest! We are currently working on enhancing training speed and aim to develop a demo as you suggested in the near future!

or replicate.com

Would this code work on 16GB VRAM 4060 ti ? There is 20GB VRAM written on the main page and that excludes anything beside 4090.

it will never happens, since it cost 20GB of VRAM and even the fast process consume 40 mins to generated first mesh

it will never happens, since it cost 20GB of VRAM and even the fast process consumes 40 mins to generate first mesh

@york-yu-ctw
40 mins? Have you personally tried it?

Hello, thank you for your interest! We are currently working on enhancing training speed and aim to develop a demo as you suggested in the near future!

Well @MrTornado24, nine months have passed! Any good news coming soon?

yes esp since 5s AI3D has been SOTA for the last 6 months - surely the amazing team behind deepseek can do 500ms AI3D?


[HUDI-5891] Fix clustering on bootstrapped tables

Change Logs
Fixes clustering on bootstrapped tables. There are two issues:

Clustering strategy added bootstrap as well as source paths to the glob paths. This was causing an error, as mentioned in HUDI-5891, while building file index. There is no need to add source path as that is handled in HoodieBootstrapRDD.
Sometimes the path will have scheme and sometimes it will be without scheme, so getting the relative partition path based was buggy. Corrected that in HoodieBootstrapRelation.

Impact
No public API change. A bug fix for the bootstrap path.
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

Tested with the scripts that surfaced this issue and they now succeed.

just like this：

@KnightChess The issue seems to be present in master and this patch does not cover it. I have created HUDI-5987 to track this issue. #8289 attempts to fix this but it only works for Spark 3.2+ versions. @jonvex is investigating it. Would appreciate any inputs on that PR.


Clarify documentation on list_models's sort attribute

It is possible to use the sort parameter from list_models with a duration, as in (excerpt from this example):
HfApi().list_models(filter="text-generation-inference", sort="likes7d", limit=5)
Currently the doc does not mention this option with duration: https://huggingface.co/docs/huggingface_hub/main/en/package_reference/hf_api#huggingface_hub.HfApi.list_models
The key with which to sort the resulting models. Possible values are the properties of the [huggingface_hub.hf_api.ModelInfo](https://huggingface.co/docs/huggingface_hub/main/en/package_reference/hf_api#huggingface_hub.ModelInfo) class.
It would be nice to add this mechanism to the doc with all possible values.

wdym by "duration"?

You can sort by "createdAt" if that's what you are looking for :)


$mount programmatically does not work with nested $slots.default components

Version
2.6.7
Reproduction link
https://codesandbox.io/s/kxw0xn61jo
Steps to reproduce
Just wait and watch.
What is expected?
Element should be transfered correctly into second Box.
What is actually happening?
$mounting does not work correctly for nested components in $slots.default

Elements disapear if they are mounted with $mount() method manually. It is example changed for @posva https://github.com/vuejs/vue/issues/9666.

Hey, this is still not enough for a bug report either, you are giving no information about where to look at with still quite some code. I still gave it a look and checked the moveChild function. You are manually plugging things into Vue and expect it to pick them up, that won't work. For example, you shouldn't change $slots nor appendChild as Vue will rewrite things on top on next render.
Remember you can use the forum or the Discord chat to ask questions!


Need to be able to define default lat/lon for CLIENT_STEERING DSs

Currently the UIs (TO and TP) do not allow you to enter a default lat/lon for CLIENT_STEERING DSs.  This means that if there are no geo restrictions but a user ends up being a miss, the user will receive a 503 instead of being sent to some default location.

@dneuman64 - same with just STEERING DSs?

Yeah

for the Traffic Portal, take a look at form.deliveryService.DNS.tpl.html. you probably just need to add the appropriate html fields to form.deliveryService.Steering.tpl.html

So I dug into this a bit, and the Geo Miss Lat/Lon for a STEERING or CLIENT_STEERING Delivery Service is never actually used. Only the Geo Miss Lat/Lon from the steering targets are used.
For STEERING DSes, the Geo Miss Lat/Lon of the chosen target is used. For CLIENT_STEERING DSes, I think it will use the Geo Miss Lat/Lon of the first target (I'd have to dig a bit deeper to confirm this) when creating the list of target URLs. But, the point is this isn't a necessary field for either steering type.

Yeah, I think I figured that out after I submitted this issue and then forgot to close it.  I will close now, thanks for the input @rawlinp


Update actions/checkout to v4 and replace docker-compose with docker compose

Replaces actions/checkout@v3 with actions/checkout@v4 due to Node 12 deprecation
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Also replaces the deprecated docker-compose with docker compose

Thank you @Niggggggo for this changes. Merged!


ARROW-15190: [C++] Upgrade bundled zstd version

@github-actions crossbow submit -g cpp

@github-actions crossbow submit -g linux

@kou Is this ok to you?

@github-actions crossbow submit -g cpp -g linux


Add Home Assistant Glow

Insert URLs to the project here: https://github.com/klaasnicolaas/home-assistant-glow

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All projects listed will be posted on our Mastodon channel

@klaasnicolaas


fix: match bug

Fix some minor bugs in the SimpleIndexer and MinRanker which crashed the examples.

I will fix the tests until the end of the week.

I actually do not think this PR makes any more sense

I actually do not think this PR makes any more sense

That is not right. I misinterpreted some details but this PR still fixes two bugs:

The name of the scores when using the lambda function is incorrect. It needs to be retrieved by doc.scores[<lambda>] instead of scores[cosine]
The min ranker sorts the wrong way around (it currently expects scores not distances)

I actually do not think this PR makes any more sense

That is not right. I misinterpreted some details but this PR still fixes two bugs:

The name of the scores when using the lambda function is incorrect. It needs to be retrieved by doc.scores[<lambda>] instead of scores[cosine]
The min ranker sorts the wrong way around (it currently expects scores not distances)

The lambda function is not used anymore

I actually do not think this PR makes any more sense

That is not right. I misinterpreted some details but this PR still fixes two bugs:

The name of the scores when using the lambda function is incorrect. It needs to be retrieved by doc.scores[<lambda>] instead of scores[cosine]
The min ranker sorts the wrong way around (it currently expects scores not distances)

The lambda function is not used anymore

Then somebody else must have fixed that already. Then, only the minranker bug remains. I will create a new PR for that.


System Fonts Question

Hello !
I just wonder if we could use a local / google font instead of system fonts please ?

Hi @Celibioux, We could technically add the font-family to the theme so that it can be extended. But the question will be more about "How you'll load the custom font?".
Do you need the custom font for a Strapi App customization or is it an app or is it for an application that has no relation with Strapi?
@soupette @gu-stav @ronronscelestes I would love to have your thought on it.

I think we could add the font-family to the font-family to the theme for the moment so it can be extended. Wdyt ? @ronronscelestes @gu-stav

@HichamELBSI Technically speaking this could be a good solution, yes. I'm not sure if we want to have this kind of customization in Strapi though, because changing the font family might have huge implications on the design and issues coming up because of this because different families render at different widths and heights. Since in some parts of the UI the space is very limited this could become a problem. Before we open this customization path, I'd like to have approval from @maevalienard - if she does, the solution of allowing the font-family sounds ok to me.

Hi! We could wait for the designer's opinion on it I agree. Just so you know, it was discussed in our squad to add in-app font customization - so it might fit this future need actually!

@HichamELBSI any updates on this please ? thanks

Oh sorry, the delay is on me because I was discussing the idea with the other designers of the team :D
I actually don't think opening the font style to any type of font would be scalable, because they couldn't be adapted to the interface (papyrus, comic sans ms, etc.). However, I think we could open the interface to the most popular Google fonts, but I'd rather see an interface in Strapi to do so. I don't know how complex that would be though, @HichamELBSI do you have any opinion?

It is technically possible but by loading the fonts dynamically we may have some perf issues on the Strapi app, some UI flickering as we had at some point on the v3. Event more since we may have to load a font name from a local storage or from a user profile before loading the font itself 🤷🏽♂ .

Hum I see. Would that be the same if we only allow it in the code? (the solution you suggested above)

hello folks ! any updates on this one ?

This is not currently on our roadmap. I would open a request in Canny – https://strapi.canny.io/ to get some traction and visibility. There are product implications we need to consider such as UI breaking etc. therefore it can't just be implemented on a development level.
It's not impossible but would most likely require us to also add the customisation feature to the main strapi app to make it work easier for users.

Related to this feature request: https://feedback.strapi.io/feature-requests/p/primary-color-fonts-customization
Closing


RuntimeError: There is no current event loop in thread 'Thread-7 (process_request_thread)'.

I use the visualiser for specific cases to debug flows but for usage of my API, I don't want the visualisation. However, simply importing the langchain_visualizer causes an error during agent.run (presumably because it's not wrapped in visualize).
  File "/home/me/emu/org/my-api/.venv/lib/python3.10/site-packages/langchain/chains/base.py", line 290, in run
    return self(args[0], callbacks=callbacks, tags=tags)[_output_key]
  File "/home/me/emu/org/my-api/.venv/lib/python3.10/site-packages/langchain_visualizer/hijacking.py", line 74, in overridden_call
    return asyncio.get_event_loop().run_until_complete(
  File "/home/me/emu/org/my-api/.venv/lib/python3.10/site-packages/nest_asyncio.py", line 45, in _get_event_loop
    loop = events.get_event_loop_policy().get_event_loop()
  File "/usr/lib/python3.10/asyncio/events.py", line 656, in get_event_loop
    raise RuntimeError('There is no current event loop in thread %r.'
RuntimeError: There is no current event loop in thread 'Thread-7 (process_request_thread)'.

Interesting, I am unable to reproduce this. Could you please tell me what version of langchain and OS you're running this on, and whether you're doing it from Jupyter or some other similar notebook?
Thanks!

Sure, so when I run this from the command line it is all fine but when run as part of a flask API, it gives the error described.
I am using Ubuntu, langchain 0.0.216 and flask 2.2.2.
But I've actually realised I don't need the visualizer imported in this file at all. Instead, I now have a wrapper at a higher level that imports it specifically for command line use.
Previously I was doing this in a file that was being executed as part of the flask app and that was causing the problem:
import langchain_visualizer

# ... functions for my web app

if __name__ == "__main__":
    langchain_visualizer.visualize(chat(sys.argv[1]))

Ahh interesting, thanks for letting me know! This doesn't yet support Flask out of the box, although I think others have gotten it to work :P


chore: update marked to version 0.6.0

The new release includes https://github.com/markedjs/marked/pull/1383.
Would it be possible to also release a new version of redoc and redoc-cli?
Thank you.

Coverage decreased (-23.1%) to 59.084% when pulling 6aec9808c8e12a42d08ed4dbb55508285b51d914 on lpinca:update/marked into ab943a8dd5e8c103743669d67e2984d8facd824a on Rebilly:master.

Opened https://github.com/DefinitelyTyped/DefinitelyTyped/pull/31834 to address the failures, will update accordingly here when possible.

Hi there! Can this PR be merged? What else needs to be reviewed so that this PR can be successfully closed out? I am very much looking forward to this change here: https://github.com/Rebilly/ReDoc/commit/809e7f2841b4cb034e8d23e92a3ebfef23580022
As I really want to integrate this wonderful open source tool into my project. Thanks so much guys for being such a cool community.


Added support for upgrading<EMAIL_ADDRESS>projects

Added support for upgrading<EMAIL_ADDRESS>projects

Coverage remained the same at 100.0% when pulling 2d6c2f365325322d05052df9ee511fc62450fa42 on waldekmastykarz:spfx-171 into c4bd2bb4529b599079d561416170c939ad8702a9 on pnp:dev.


Can't see mux/demux board pin connections.

Say I have a project and was looking how to use that black mux/demux board.
There is a lot of hot glue and I can't see how that black breakout board is connected to your sub board to match pins up.
Do you have any more details on this or the usage of that smaller black board or do you have some pictures with less glue :D?

Hi @sethstenzel
Will this be enough: https://github.com/luk6xff/usbmux/blob/master/docs/schematics/usbmux_bb.png ?

If you labeled the diagram it would be. There are some non-standard colors being used for the wires, and the fritz diagram of the demux break looks completely different then the real one so without the wires labeled it's hard to know what's going on. I suppose I can read through the code and try to work it out if you labeled this pretty clearly in code.


Use it in react native

As i am getting a issue. I am not able to use it in the react-native. So anybody have idea about it to use in react native to play .m3u8 format.

why not use react-native-video?
https://github.com/react-native-video/react-native-video


service idempotency not correct in AIX

When using an LWRP like the following on AIX with Chef 12:
service "xntpd" do
 supports :restart => true
 action [ :start ]
end

The recipe will always report it is starting the service, even when the service is already running.  Idempotency seems to not be functioning properly.

Does it only affect this particular service, xntpd? How about other ones?

I have tried so far on xntpd and sshd service, with the same result.  I did see in the code where it calls the function that uses "lssrc -s" to check if running.  And, I've confirmed that it should see both of those services as active.

This appears to be an issue with shell_out possibly, specifically the "is_resource_group?" in the provider/service/aix.rb file.  I say this because I did was able to get the services recognized as active if I removed the is_resource_group? check.  Also, interestingly, I noticed that the output of lssrc commands is being displayed on the terminal as chef-client is being run.  Below is an output of what I see from a normal chef-client run without the modified code.  You can see the output of "lssrc -g", which is to determine if the service is actually a service group, and the output of the "startsrc -s " command.
* service[xntpd] action start0513-086 The xntpd Group is not on file.
0513-029 The xntpd Subsystem is already active.
Multiple instances are not supported.

    - start service service[xntpd]
  * service[sshd] action start0513-086 The sshd Group is not on file.
0513-029 The sshd Subsystem is already active.
Multiple instances are not supported.

    - start service service[sshd]

I have been able to "patch" the problem to an extent on my test system.  This isn't the correct way however, because the problem seems to stem from the shell_out! not handling the output of "lssrc -g" command when the service_name is not, in fact, a group.  Whenever I rely on just "lssrc -g<EMAIL_ADDRESS>to try and determine if the resource is a service group, the code executes the rescue block in my code (below).  When actually executed from the command line the output is:
# lssrc -g xntpd
0513-086 The xntpd Group is not on file.

Here is the replacement function that I currently have working.  As I'm fairly new to Chef and Ruby, this may not be the most elegant way, but so far it is what I have come up with.  The actual fix, I think, will have to be in the shell_out command.
        def is_resource_group?
         Chef::Log.debug "Determining if #{@new_resource} is a resource group"
         begin
          group = shell_out!("lssrc -a|grep #{@new_resource.service_name}").stdout
          Chef::Log.debug ("#{group}")
          if group.split(' ')[1] ==<EMAIL_ADDRESS>            Chef::Log.debug<EMAIL_ADDRESS>is a resource group"
            @is_resource_group = true
          else
            Chef::Log.debug<EMAIL_ADDRESS>is not a resource group"
            @is_resource_group = false
          end

           # ShellOut sometimes throws different types of Exceptions than ShellCommandFailed.
           # Temporarily catching different types of exceptions here until we get Shellout fixed.
           # TODO: Remove the line before one we get the ShellOut fix.
         rescue Mixlib::ShellOut::ShellCommandFailed, SystemCallError
            Chef::Log.debug<EMAIL_ADDRESS>service group status is undertermined, defaulting to false"
           @status_load_success = false
           @is_resource_group = false
           nil
         end
        end

@alanwthatcher What version of the Chef Client are you using? Some of that code looks like it dates from pre-12.4.0, which is when I made a few changes to the service group parsing mechanism to solve unreliability issues.

Chef version:
 # chef-client --version
Chef: 12.4.1

When "lssrc -g " is called for a non-service group name, the shell_out fails.  That is why I switched it for the "lssrc -a | grep".  I added the rescue block for testing.  In the original code logic, this caused it to default back to the service not being started, and therefore always issuing the startsrc command.

I'm firing up an LPAR to see if I can repro this but... apparently IBM Power Development Platform has a backlog on reservations for several days so it's going to take a while :frowning:

I will try and look more into it this week. Debug level of logs didn't
produce any informative messages, except when I modified the function call
to log a message that confirmed that the shell_out bombed. When I tried
spit out the contents of the variable holding the shell_out output, it was
just blank.
The problem must reside down at that level, I am just trying to work
backwards, but am new to Ruby. So.
Let me know any way I might be able to assist. Thanks for your efforts!
On Mon, Aug 3, 2015 at 12:18 PM Julian C. Dunn<EMAIL_ADDRESS>wrote:

I'm firing up an LPAR to see if I can repro this but... apparently IBM
Power Development Platform has a backlog on reservations for several days
so it's going to take a while [image: :frowning:]
—
Reply to this email directly or view it on GitHub
https://github.com/chef/chef/issues/3730#issuecomment-127297020.

Yeah, if you can figure out a repro case just outside of Chef with only mixlib-shellout and the original lssrc -g call to see what's happening, that'd be splendid.

To be honest, I don't know how to go about doing that.  If you can point me toward an example, I would be more than happy to make it happen.

You can do this right within a pry session on the LPAR like so:
$ /opt/chef/embedded/bin/pry
[1] pry(main)> require 'mixlib/shellout'
=> true
[2] pry(main)> s = Mixlib::ShellOut.shell_out!("lssrc -g ... ")
=> <something>

and then seeing what exception is being thrown and/or inspecting the s object to see what it looks like. Thanks Alan!

Ok.  So here is what I ended up with.  I couldn't run the commands as you have above on either aix or linux.  So I searched around a bit, and the best I could come up with so far is what I am pasting below.
I started with just using the command "hostname" (cmd variable, line 3 for output), to get an idea of what the output should look like.  The next command is for a subsystem group that does exist (cmd2, line 5).  And the third for the subsystem group that does not exist (cmd3, line 7).
There were no errors raised during my testing.  The things I see of note are the output about "less" not being installed, which it is not.  And that the command for the subsystem group that does not exist (cmd3) exits with a status of 1, but the output is in stdin, and not stderr. I forced a bad command with the same method on a linux system and confirmed that stderr is where the output went on that system.  So I am not sure if that could be part of the cause?
I am going to continue to poke around.  Best way to learn.
/ # /opt/chef/embedded/bin/pry
[1] pry(main)> require 'mixlib/shellout'
which: 0652-141 There is no less in /usr/bin /etc /usr/sbin /usr/ucb /usr/bin/X11 /sbin /usr/local/bin.
=> true
[2] pry(main)> cmd = Mixlib::ShellOut.new("hostname")
=> <Mixlib::ShellOut#2288063720: command: 'hostname' process_status: nil stdout: '' stderr: '' child_pid: nil environment: {} timeout: 600 user:  group:  working_dir:  >
[3] pry(main)> cmd.run_command
=> <Mixlib::ShellOut#2288063720: command: 'hostname' process_status: #<Process::Status: pid 15597692 exit 0> stdout: 'savdclvbox01aix1.nfcutest.net' stderr: '' child_pid: 15597692 environment: {} timeout: 600 user:  group:  working_dir:  >
[4] pry(main)> cmd2 = Mixlib::ShellOut.new("lssrc -g ras")
=> <Mixlib::ShellOut#2285387240: command: 'lssrc -g ras' process_status: nil stdout: '' stderr: '' child_pid: nil environment: {} timeout: 600 user:  group:  working_dir:  >
[5] pry(main)> cmd2.run_command
=> <Mixlib::ShellOut#2285387240: command: 'lssrc -g ras' process_status: #<Process::Status: pid 15597694 exit 0> stdout: 'Subsystem         Group            PID          Status
 syslogd          ras              4653206      active' stderr: '' child_pid: 15597694 environment: {} timeout: 600 user:  group:  working_dir:  >
[6] pry(main)> cmd3 = Mixlib::ShellOut.new("lssrc -g xntpd")
=> <Mixlib::ShellOut#2284014100: command: 'lssrc -g xntpd' process_status: nil stdout: '' stderr: '' child_pid: nil environment: {} timeout: 600 user:  group:  working_dir:  >
[7] pry(main)> cmd3.run_command
=> <Mixlib::ShellOut#2284014100: command: 'lssrc -g xntpd' process_status: #<Process::Status: pid 16777456 exit 1> stdout: '0513-086 The xntpd Group is not on file.' stderr: '' child_pid: 16777456 environment: {} timeout: 600 user:  group:  working_dir:  >
[8] pry(main)>

While I couldn't produce an actual error in the pry session, I did tinker with the actual command being executed in service/aix.rb and it does seem that any command that exits with exit code 1 (maybe others, not sure) does seem to cause the same kind of behavior.

Thanks.  I made the change locally and it works great.  I also learned something about shell_out vs shell_out!.


test async call not effectiveness in asp.net core

I want to test effectiveness async request vs sync request in asp.net core 2.0. For this in Program file set Kestrel ThreadCount option to 1.
public class Program
{
    public static void Main(string[] args)
    {
        var host = new WebHostBuilder()
            //.UseKestrel(options =>  //core 1.1
            //{
            //  options.ThreadCount = 1;
            //})
            .UseLibuv(options=> options.ThreadCount = 1) //core 2.0
            .UseContentRoot(Directory.GetCurrentDirectory())
            .UseIISIntegration()
            .UseStartup<Startup>()
            .UseApplicationInsights()
            .Build();

        host.Run();
    }
}

Then write simple code in the controller for call async method. in Index action set the start time to ViewBag, then call Doing function async, finally set end time to ViewBag.
public class HomeController : Controller
{
    public async Task<IActionResult> Index()
    {
        ViewBag.Start = DateTime.Now;

        await Doing();

        ViewBag.Finish = DateTime.Now;

        return View();
    }

    public async Task Doing()
    {
        await Task.Delay(5000);
    }
}

View Code is:

    Start: @ViewBag.Start

    Finish: @ViewBag.Finish

After run app and browsing page in two browsers Simultaneously, I expected that two request start time be approximately equal. but in the result, after the first request finished, second is started.
Output in two browsers for
Start: 10/10/2017 10:16:36 AM
Finish: 10/10/2017 10:16:43 AM

Start: 10/10/2017 10:16:43 AM
Finish: 10/10/2017 10:16:50 AM

What is wrong in my test or concept?

FYI this was posted here as well: https://stackoverflow.com/questions/46661499/async-call-not-effectiveness-in-asp-net-core

Hi @MohammadAkbari.
Is this issue still relevant? Are you still facing this issue, or should we close it?

I cannot actually reproduce this anymore with 2.0. I believe I could confirm OP’s observation before but I cannot anymore.

Thanks @poke.
We'll close this issue then. Given that this was filed a while ago, it is probably fixed now.


Local build errors

I cloned the repo and started playing with the code locally but I ran into some problems just getting it to build. Perhaps this isn't causing a problem for anyone currently, but I suspect if you were to remove the node_modules/ folder and globally remove your versions of babel-eslint you might encounter the same problems I ran across.
It seems there was a bug in babel-eslint that doesn't play well with Flow, but it was corrected in version 8.1.1. For me it was causing the npm test command to fail. Anyway, a simple upgrade of that package fixed it.
Additionally, I ran into an error when building Spected that looked like a simple CommonJs failure to recognize the Object rest spread operator. I fixed it by moving the rollup commonjs() call (in the rollup.config.js) so that it comes after the babel() transpile step.
Hope this is helpful.

Thanks for the very valuable feedback @arizonatribe
Will try to reproduce the error in the coming days.


Stop writing realm roles back to Keycloak on user profile creation/updation and provider approval

We can now lower privileges of the keycloak-admin client that is configured during set up

Have lowered the privileges for keycloak-admin in the integration test realm to only have query-users, view-realms. Let's see if tests pass

tests might fail because in master u have done flyway migration and both branches uses same postgres db? @ThorodanBrom

tests might fail because in master u have done flyway migration and both branches uses same postgres db? @ThorodanBrom

Yes, you're right. Will create a new schema containing the old data, config would need to be updated then

Have only added view-users privilege to the keycloak-admin client

Failing tests are due to the cat API update
Seems like only view-users role/privilege is required


cashaccounts unit tests

Pull Request Test Coverage Report for Build 2363

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 70.816%

Totals

Change from base Build 2312:
0.5%

Covered Lines:
2175

Relevant Lines:
2872

💛  - Coveralls


Update eslint dependency to remove Moderate vulnerability

What
npm audit found a moderate vulnerability Prototype Pollution with this projects current dependency eslint version.
Fixed in eslint >=4.17.11
More info:  https://nodesecurity.io/advisories/782

I've started this.