Use a streaming request to download cookbook

fixes #4549

so how did the bug show up and are there any more occurrences?

:+1:
@lamont-granquist I checked the code for other uses of sign_on_redirect and only found it in specs or as attributes on a class

That's the only place we try and do a streaming request with noauth_rest (which used to be get(path, true). I'm checking everything else through.
I stumbled upon this because I happened to have a post 12.6.0 chefdk installed and needed to download a cookbook from supermarket.

@chef/client-core this is ready for review

@thommay I'm not seeing (here or in the other bug) how precisely this caused the issue to happen and how this fixes it. Can you elaborate?

Chef::REST#get: https://github.com/chef/chef/blob/7755b93c72ef33d5041b6a9c4b53bcf29814579d/lib/chef/rest.rb#L116
Chef::HTTP#get: https://github.com/chef/chef/blob/7755b93c72ef33d5041b6a9c4b53bcf29814579d/lib/chef/http.rb#L109

So it looks at first glance that we just missed this in the mass switch from REST->HTTP. Though I would have expected to get a more type-related error (probably NoMethodError) when passing true instead of a Hash.
This covers all the instances I am able to find with git grep '\.get' -- lib |grep ',' (that finds more false positives than not but gets the job done.
:+1: though I'd be in favor of someone else independently looking for instances of this error and making sure we got them all.

:+1:

@danielsdeleo so we did a NoMethodError ([] for true) once that was no longer masked by sign_on_redirect being missing.
@jkeiser as Dan says, this was just overlooked in the move to Chef::HTTP  - mainly I was looking for instances of get_rest and relying on tests to catch the rest.

Got it, :+1:

But wait!  There's more!!!
knife supermarket show -VV -m 'https://chefstore.chq.ei' -c ~/.chef/knife_prod.rb expd_infrastructure INFO: Using configuration from /home/chq-anthonyr/.chef/knife_prod.rb /home/chq-anthonyr/.chefdk/gem/ruby/2.1.0/gems/knife-supermarket-0.2.1/lib/chef/knife/supermarket_show.rb:38:in get_cookbook_data': undefined method get_rest' for #<Chef::HTTP::SimpleJSON:0x000000022815e8> (NoMethodError) 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/knife/cookbook_site_show.rb:28:in run'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/knife.rb:416:in block in run_with_pretty_exceptions' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/local_mode.rb:44:in with_server_connectivity'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/knife.rb:415:in run_with_pretty_exceptions' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/knife.rb:214:in run'
from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/lib/chef/application/knife.rb:148:in run' 	from /opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.7.2/bin/knife:25:in <top (required)>'
from /opt/chefdk/bin/knife:50:in load' 	from /opt/chefdk/bin/knife:50:in '`
This with 0.11.0 chefdk, and knife-supermarket 0.2.1.  Granted, supermarket isn't here, but i thought I should mention here since we're talking chef-client innards.

@tyler-ball, I'm unclear if i should have posted this above, or a better place, but at the time it seemed to make sense here.  If i'm wrong, happy to put in better place.  I'm advising you of this as my timing with daniel's branch deletion might have obscured my comment...

@SolverDude please raise a bug against knife-supermarket with this.


Error On Headless Instance: WebGL2 is required but not supported.

Environment (please complete the following information):

OS (e.g., Windows 10): MacOS Sonoma Version 14.5 (23F79)
Extension version (e.g., 1.2.3):  2.1.5

Describe the bug:

When running a project that uses WebGL2, the headless instance (the non headless works) fails with the error:
"WebGL2 is required but not supported."
Repro steps:

Create a React Project and use a library that required WebGL2, for example I am using ArcGIS API for Javascript.
Expected behavior:

The webpage should load the component using WebGL2
Additional context:

AB#52139019

Thanks for filing this. I'll mark this as tracked so that it's part of our dev team backlog. I don't know if this will be easy to technically fix however.

As mentioned this has technical limitations for the embeded version (screencast) but should work fine for the full browser (non headless). Should be partially fixed by:
https://github.com/microsoft/vscode-edge-devtools/pull/2432


Initial version for .NET SDK 7.0.302

Same feature set as the .NET 6 images, but with .NET 7 SDK.

Pending tasks

[ ] https://github.com/swissgrc/.github/pull/48 needs to be merged
[ ] https://github.com/swissgrc/docker-azure-pipelines-dotnet/pull/115 needs to be merged
[ ] Sonar Cloud Setup
[ ] Update this PR again


add hadolint support

Hi @Jubblin Sorry I didn't see this until now, it seems like you wanted to merge some updates? Is there a reason why you closed this?


Update dependencies

Codecov Report

Merging #769 (fa22643) into main (8024d08) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #769   +/-   ##
=======================================
  Coverage   85.33%   85.33%
=======================================
  Files         311      311
  Lines       29006    29006
=======================================
  Hits        24753    24753
  Misses       4253     4253

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 8024d08...fa22643. Read the comment docs.


API review for Security modules

Parent issue: #24356

Closing this issue, because we will not release spring-security-azure-oauth2-client.

Reopen this issue, because 4.0 version include spring-cloud-azure-starter-(keyvault-secrets|active-directory|active-directory-b2c)

Closing issue, because related PRs have been merged.


Python SDK

For tools like the Flux Restful API (or flux-cloud) I'd like to be able to easily export a port, or submit a job, or do just about anything. This is technically kind of different than the flux-restful-api because it will be intending to interact with our kubernetes objects, and be used by the previously mentioned. I've never done this before but will look into how other operators do it.

This is done! It will need more work to add examples and other functionality I want, but this is coming soon.


Typescript

Rewrite to utilize Typescript.

how about docs, can they still be generated?

While running npm test in this branch without a rabbitmq server running i get 17 failed and one unhandled rejection. while in the main branch i only get 17 failed, no unhandled rejections.

also in main:
 can publish and consume

  Rejected promise returned by test

this branch:
can publish and consume

  Error: Promise returned by test never resolved

  › process.emit (node_modules/source-map-support/source-map-support.js:495:21)

Missing types on basicQos and basicPrefetch method arguments

how about docs, can they still be generated?

Yes. Might need to tweak it, but i'd prefer to have this and #3 merged before, to not have to care about the dist files.

While running npm test in this branch without a rabbitmq server running i get 17 failed and one unhandled rejection. while in the main branch i only get 17 failed, no unhandled rejections.

Why would you want to run the test suite without RabbitMQ running?

also in main:
 can publish and consume

  Rejected promise returned by test

this branch:
can publish and consume

  Error: Promise returned by test never resolved

  › process.emit (node_modules/source-map-support/source-map-support.js:495:21)

Is this with/without RabbitMQ running? I have 17 passes and 1 skipped on both main and this branch, CI also passes.

Missing types on basicQos and basicPrefetch method arguments

The method arguments have types. If a default value, eg. prefetchSize = 0 is set, the typescript compiler knows that this is of type number.
https://github.com/cloudamqp/amqp-client.js/pull/1/files#diff-663dae8bbcf9718ab8a7ac19e5296ecafa56b738b6c2d2e76a3214b24048b5daR54
https://github.com/cloudamqp/amqp-client.js/pull/1/files#diff-663dae8bbcf9718ab8a7ac19e5296ecafa56b738b6c2d2e76a3214b24048b5daR394

Missing types on basicQos and basicPrefetch method arguments

also in main:
 can publish and consume

  Rejected promise returned by test

this branch:
can publish and consume

  Error: Promise returned by test never resolved

  › process.emit (node_modules/source-map-support/source-map-support.js:495:21)

Solved in: d9cf64c

i see, it seems like it's the documentation thingy that get's confused where it's number? and then converts to any

i see, it seems like it's the documentation thingy that get's confused where it's number? and then converts to any

@carlhoerberg  Yeah, the hardened eslint config does not want me to write prefetchSize: number = 0 as the type number is automatically inferred by the typescript compiler. But it seems like the documentation tool does not catch that. But i'd like to work on solving that after this and #3 is merged. Either by adding the type back to the JSDoc comments or if I manage to find something that figures it out like the compiler does.

FYI, I tried installing this branch using NPM and it worked as expected.
import AMQPClient from '@cloudamqp/amqp-client'

async function run() {
  try {
    const amqp = new AMQPClient("amqp://localhost")
    const conn = await amqp.connect()
    const ch = await conn.channel()
    const q = await ch.queue()
    const consumer = await q.subscribe({noAck: true}, async (msg) => {
      console.log(msg.bodyToString())
      await consumer.cancel()
    })
    await q.publish("Hello World", {deliveryMode: 2})
    await consumer.wait() // will block until consumer is canceled or throw an error if server closed channel/connection
    await conn.close()
  } catch (e) {
    console.error("ERROR", e)
    e.connection.close()
    setTimeout(run, 1000) // will try to reconnect in 1s
  }
}

run()

Added typescript definitions, but just by extending the jsdocs, in #12, but it was good, typescript caught a lot of subtle bugs we had


The type 'IIdentityAdminService' is defined in an assembly that is not referenced. You must add a reference to assembly 'IdentityAdmin, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.

the type IdentityAdminCoreManager implements the interface IIdentityAdminService which cannot be found.
I use the packages "IdentityServer3.Admin" 1.0.0-beta6 and "IdentityServer3.Admin.EntityFramework" 1.0.0-beta5.
I check if there was an update but didn't find any.
Is there something I do wrong?

Hi, I am aware of this issue, this is already solved in the git repo, ijust need to build a new nuget package. i am also updating the project with the new Identityserver3.Entityframwork binaries.
This will normally be resolved in a couple of days


Prometheus Queries are very slow

What is the issue?
Prometheus queries are very slow. We have a retention time of 72hours and the queries we pretty much fast for the first two months. Now we see that the same queries are taking so long up to 50 seconds. When i keep executing the same query again and again , i see that the response time varying every time. The number of metrics has also not increased.
Does this has something to do with Rule evaluation.
Because i see that 'prometheus_evaluator_duration_seconds' has gone upto 100 seconds.
What did you expect to see?
Prometheus Queries to be fast.

Prometheus version:
1.6.1

If your retention is 72h, there should be now slowdown creeping up over the course of 2 months. Is it possible that you are putting more querying load onto it than in the past, e.g. via dashboards and more rules?

Yes we re doing a lot with queries and alerting. We did a restart for one of the instance and it worked fine after where the 'prometheus_evaluator_duration_seconds'  has come down to 23 seconds.  Is the rule evaluation causing the slowness or is it just a symptom of some other issue.

I also have problems with slow queries.
But my problem is a little bit more strange.
There is only one metric that is very slow to query. There is no function used in the query.  The metric name and tag are used only in the query.
It takes 30 seconds to query.
(Load time: 32445ms
Resolution: 14s ;
Total time series: 19;)
Then I used other metric name (metrics size same)to query very quickly, all in milliseconds.
(Load time: 77ms
Resolution: 14s
Total time series: 16)

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.


matomo: 5.2.0 -> 5.2.1

https://matomo.org/changelog/matomo-5-2-1/
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

nixpkgs-reviewd workflow started

Extra args: ``
Free space: true
Who asked: lucasew

TARGETS

x86_64-linux: true
x86_64-darwin: true
aarch64-darwin: true

Status and logs: https://github.com/nixosbrasil/nixpkgs-reviewd/actions/runs/12449920361

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366895

x86_64-linux

:white_check_mark: 2 packages built:

matomo
matomo-beta

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366895

aarch64-darwin

:white_check_mark: 2 packages built:

matomo
matomo-beta

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 366895

x86_64-darwin

:white_check_mark: 2 packages built:

matomo
matomo-beta


Install Plex

Install Plex and deploy to production

Test Plex with Firesticks
Test with Browsers
Test with Android
Test with Iphone
Test with nvidia shields

Plex installed, Setting up library and permissions before exposing for UAT


Object.assign not available in older Node versions

It looks like that is the only incompatibility with Node 0.12 so it might make sense to change that and/or use a polyfill.

Do we care about supporting node 0.12? I guess we should talk about what versions make sense to support, especially since versions in Node are rolling along like God damn freight train right now.

True but there's still many people on older versions and since it would only be a minor change in this case we might want to consider it. In general I would say that every official plugin should support every Node version the latest Feathers release it is compatible with supports.

:+1: I'm down with that.

It is actually pretty easy to add the Polyfill to Babel like this: https://github.com/feathersjs/feathers-configuration/commit/b21b066f74bdf158353c88b2aeb8e03d7a166148 (this repo might need to be updated to latest Babel though)


Add AC filter status support (FR #375)

@SN0WTR00PER,
Pls move to #375 and attach your diagnostic so that I can analyze returned value.


Works on latest rust

I needed to use some traits

Ah sorry, I forgot to commit the changes that made it work, it works on master now.

Cool, thanks


Documentation is running in Quirks Mode

Problem description
The documentation appears to be running in Quirks Mode, at least in Firefox. This is due to there being a comment with the page generation date preceeding the <!DOCTYPE html> which is disallowed for HTML5 standard.
Just happened to have devtools open while browsing and noticed this.

same for Microsoft Edge:

Is that really a problem tho? I read about Quirks Mode and it doesn't seem to have any disadvantages for the documentation.

Thanks for reporting; I knew "old browsers" were picky about this, but didn't know current browsers still did. I opened a PR to move the comment after the doctype, which should (hopefully) fix this; https://github.com/docker/docker.github.io/pull/14484
Preview of that PR is available at https://deploy-preview-14484--docsdocker.netlify.app


R119 gemm fallback

DO NOT MERGE
Optional gemm as aggregate for fallback.

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished. No test results found.

Refer to this link for build results (access rights to CI server needed):
/job/libnd4j_PR/182/

Build triggered. sha1 is merged.

Build started sha1 is merged.

Build finished. No test results found.

Refer to this link for build results (access rights to CI server needed):
/job/libnd4j_PR/183/


Enable assignment of a dictionnary to the layout attribute

This enables things like
Button(layout={'width': '500px'})

b = Button()
button.layout = {'width': '500px'}

@jasongrout

This looks good to me. Waiting for tests to pass...


Update README.md for Carthage support.

PR for https://github.com/ashleymills/Reachability.swift/pull/55#issuecomment-154091762

Thank you!

@uny Thanks for the PR!
Cheers
Ash


[nrf fromtree] modules: openthread: radio: OT now uses standard TX timestamp

Synchronizes with the new upstream RX/TX timestamp definition in OpenThread based on the standard's SFD.
This change is synchronized with the upstream OpenThread implementation via west.yml.
(cherry picked from commit e2005b6e48d3b578f83fdfaaff547d1f8082ce35)

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

openthread
https://github.com/zephyrproject-rtos/openthread/commit/f7690fe7e9d638341921808cba6a3e695ec0131e
https://github.com/zephyrproject-rtos/openthread/commit/d62167ee34b091e7025c9ec2820aae71e17a3944 (main)
<EMAIL_ADDRESS>

Note: This message is automatically posted and updated by the Manifest GitHub Action.


KAFKA-5094: Replace SCRAM credentials in broker logs with tag hidden

@ijuma Can you take a look? Thank you...

Merged to trunk after removing unused java.util.Properties import.


Using multiple YubiKey with same GPG keys

It's not possible to use multiple YubiKeys containing the same GPG Keys with GnuPG as the serial number of the first used yubikey is stored by GnuPG. Here is a workaround I found, could be use-full for those you have this usage until GnuPG fixes this issue.

Excellent contribution!


start imgui implementation

The actual imgui implementation discussed with @clewis7

Started implemetning ImguiFigure, kinda alright so far.
tasks:

[x] BaseGUI
[x] complete ImguiFigure

[x] manages imgui rendering
[x] manages standard right click menu
[x] manages EdgeWindows

[x] subplot toolbar
[x] standard right click menu
[x] allow adding custom GUIs to edges of canvas, these are managed by ImguiFigure
[x] allow graphics to "request" starting their own right click menu on the next render cycle

[x] right click menu for hlut/colorbar tool

[x] ImageWidget, along with play button etc. Maybe we can use time.perf_counter() and actually display a specific FPS?
[ ] tests :D
[x] image widget imgui example with EdgeWindow
[x] a basic imgui example with EdgeWindow
[x] move image widget examples from notebook to main docs
[x] make sure non-imgui use is not affected!
[x] remove ipywidget and qt toolbars, cleanup anything else that needs cleaning up, remove output contexts!

closes #494 , closes #260 , closes #360

Should be possible to dynamically add and remove GUIs to edges if the BaseGUI subclass implements a cleanup method.

depends on #574

cmap picker, last thing I'm making before the sliders for ImageWidget :smile:
https://github.com/user-attachments/assets/4ed95cf1-cd70-4645-9ffa-9aa0d9e7fbc5
@clewis7 @apasarkar

Might make more sense to subclass Subplot and add the toolbar to it directly

image widget working well with all required functionality
https://github.com/user-attachments/assets/03695b1f-c333-46e2-9b21-93674d921cfe

basic example of how to make a custom GUI with imgui and place it next to a Figure
https://github.com/user-attachments/assets/0e2a1c00-15eb-4ba1-816f-2904c821f670
@lauraporta

Beautiful 😱 looking forward imgui!

need to make the imgui renderer scale w.r.t. pixel ratio of canvas:

See if this is already in wgpu-py, if not probably makes sense to directly add it to wpgu-py

I should also move the conditional import to top level, so that users can still do from fastplotlib.layouts import Figure to get the non-imgui figure if they have imgui installed. I also want to benchmark to make sure imgui doesn't affect performance.

Should make the subplot toolbar optional because it can add clutter when it's not required, and the right click menu offers the same options.

@clewis7 So if someone has imgui installed, they can still use the non-imgui Figure like this, what do you think:
If you have imgui:
import fastplotlib as fpl

# defaults to imgui figure
fig = fpl.Figure()

# uses basic Figure
fig2 = fpl.layouts.Figure()

# imgui figure again
fig3 = fpl.layouts.ImguiFigure()

This commit is how it's implemented: https://github.com/fastplotlib/fastplotlib/pull/571/commits/1c823e5735616b94bc4f3d1174d3df5d1258d49e
If imgui is not installed then it just uses the basic Figure, i.e. fpl.Figure is the basic figure.

@clewis7 any further comments? otherwise I will upload new test screenshots and fix the merge conflicts, and then we can merge and figure out what is up with CI. Latest wgpu really threw in a wrench :melting_face:

@clewis7 So if someone has imgui installed, they can still use the non-imgui Figure like this, what do you think:
If you have imgui:
import fastplotlib as fpl

# defaults to imgui figure
fig = fpl.Figure()

# uses basic Figure
fig2 = fpl.layouts.Figure()

# imgui figure again
fig3 = fpl.layouts.ImguiFigure()

This commit is how it's implemented: 1c823e5
If imgui is not installed then it just uses the basic Figure, i.e. fpl.Figure is the basic figure.

I think this is fine to me. My suspicion is that most people will always use imgui. We can think of doing something else later if it becomes a nuisance flipping between figure types.

@clewis7 any further comments? otherwise I will upload new test screenshots and fix the merge conflicts, and then we can merge and figure out what is up with CI. Latest wgpu really threw in a wrench 🫠

LGTM

The heatmap RAM issue is a very annoying problem. Let's wait until I can figure out #610 and just keep a small single heatmap example for now.

I should set the slider flag imgui.SLIDER_FLAGS_NO_INPUT until jupyter_rfb supports the char event.
https://pyimgui.readthedocs.io/en/latest/guide/slider-flags.html#slider-flag-options

Tests are finally completing without running out of RAM! This is with the bigmem machine we pay for, will check if it runs on regular free github servers. These are the limits I set:
backend test: 1024, set in conftest.py
screenshot example tests: 2048, set in the test_examples.py for screenshots and conf.py for sphinx docs. The limit is here here since the screenshot dims are actually 1400 (pixel ratio=2)

ok after adding back the selector examples the rtd build is taking forever, this makes no sense :angry:

see if simpler linear selectors example with only lines will build on rtd, this makes zero sense this example has a minimal memory footprint :shrug:

OK I think I understand the issue now, RAM usage builds up over time as it goes through all the examples, so the more examples we have the more RAM usage. Need to figure out how to tell sphinx to cleanup examples as it goes through them. :facepalm:

ok now after subsampling the cockatoo video memory consumption when I build locally remains < 1.5GB. Before it was ~2.7 GB.

ALL TESTS FINALLY PASSING AND RTD BUILD IS BUILDING :partying_face: :partying_face: :partying_face: :partying_face:
I didn't expent the hardest thing about this would be dealing with rtd limits and sphinx gallery memory leak :facepalm:
@clewis7 few final comments up here just to get you up to speed, and if you could do a final check on that TextureArray test stuff I pointed out at the bottom. Other than that good to go!!

I updated the user guide with imgui images, need to figure out why the vids are not looping, I used imageio to make them :thinking:

LGTM!

This looks amazing Kushal!!!


Disabling scroll restoration when doing history.back() after pushState()

Describe the problem
I'm trying to use the new shallow routing feature to make it possible for users to close an app-like sidebar by using the back button, which I'd presume is the quintessential use case for this feature.
Things are working well apart from the fact that closing the sidebar (i.e. history.back()) often changes the document's scroll position, similar to how it's done upon page navigation, but in this particular case it's annoying and very much feels disruptive and inappropriate UX-wise.
You can see a basic example of this happening in the video below. Notice how the page underneath the sidebar is suddenly scrolled up as soon as the sidebar is closed (i.e. history.back() is invoked):
https://github.com/sveltejs/kit/assets/26527405/bbcfd888-1f3a-46a2-b21a-0c14baa890a1
Describe the proposed solution
I'm not quite sure if it's the browser doing this on its own (apparently not since SvelteKit seems to set history.scrollRestoration to manual) or if it's something SvelteKit is internally doing or at least has control over; if it's the latter, then it would be useful if, for example, pushState received an option similar to goto's noscroll, which disables this behavior. This can be desirable in cases where shallow routing is being used for opening and closing components such as modals and sidebars and so forth, where one normally doesn't expect the document's scroll position to change when closing the component.
Alternatives considered
No response
Importance
nice to have
Additional Information
No response

This should be fixed by #11421

@PatrickG No, I don't want ANY scroll restoration. This is not the same as #11355.

I'm having the same issue when using replaceState.  I am capturing a product carousels scroll x position beforeNavigate and replacing the current state then on history.back() recalling that state and scrolling the carousel back to its last know position.
When using pushState for modals and drawers I am locking the body of the site by pushing a


More inline examples in documentation pages

One of our users requested more inline examples in the documentation. This should be easy to do, but will take a while. I will treat this as in incremental issue.

Addressed by improvements to documentation.


Fix licensing comment appearing thrice in main CSS file

Description

Fixes #119
The comment appearing thrice was because /*! Checka11y.css v1.3.3 | MIT License | github.com/jackdomleo7/Checka11y.css */ appeared in a few separate sass files:

src/warnings/checka11y-warnings.scss
src/errors/checka11y-errors.scss
src/checka11y.scss

Then we we compile all the SCSS together, those comments appear in the compiled CSS file based on the order of each @use rule in checka11y.scss.
Flow:

checka11y.scss is the main SCSS file that loads the /warnings/* and /errors/* files.

@use "./warnings/checka11y-warnings.scss";
@use "./errors/checka11y-errors.scss";

Since the warnings are loaded first, we can now look at the @use order in checka11y-warnings.scss.

@use "./variables" as *;
@use "./customisation" as *;
@use "../shared/variables" as *;
@use "../shared/customisation" as *;
@use "../shared/helpers" as *;
@use "../shared/messages/" as *;
@use "./features/" as *;

The _customisation.scss partial gets loaded first (after _variables) so that partial is what appears first when compiling checka11y.css. There isn't anything special about _customisation.scss, its just first in the @use "loading" order when compiling the main css file, if we put the comment instead into _variables, then we would have to make sure its not loaded in many files otherwise the comment would appear multiple times like the original state.
tldr; add the comment into the partial that gets loaded first into the main file, then it can appear once at the top of checka11y.css as expected.

/*! Checka11y.css v2.3.0 | MIT License | github.com/jackdomleo7/Checka11y.css */
:root {
  --checka11y-text-warning: #856404;
  --checka11y-bg-warning: #ffffd8;
  --checka11y-border-warning: #ff6;
}

:root {
  --checka11y-space: 0.25rem;
...

I only added it to /warnings/* because if we add it to customisation.scss in /errors/* then we will see two comments in the compiled file like this:

/*! Checka11y.css v2.3.0 | MIT License | github.com/jackdomleo7/Checka11y.css */
:root {
  --checka11y-text-warning: #856404;
  --checka11y-bg-warning: #ffffd8;
  --checka11y-border-warning: #ff6;
}

/*! Checka11y.css v2.3.0 | MIT License | github.com/jackdomleo7/Checka11y.css */
:root {
  --checka11y-space: 0.25rem;
  --checka11y-space-0: calc(var(--checka11y-space) * 0);
...

Why is this important?

Fixes an annoying bug that was encountered awhile ago while working on another ticket.
Covered test cases

No test cases modified. Tests still pass as expected with npm run test.
Did you test on all major browsers?

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari

Other details

T&Cs

[x] I confirm I have read and understand the contributing guidelines
[x] I understand the work in this pull request will not be released straight away and will appear in a future release (if approved)
[x] I confirm the work in this pull request is true and valid to the best of my knowledge
[x] I have updated the README, features.md and codes.md files where applicable

@tannerdolby so I didn't think of this when looking at your PR, but I created a shared/_license.scss file that gets imported vua @use into checka11y.scss, errors/checka11y-errors.scss and warnings/checka11y-warnings.scss.
I saw your comment regarding only using this comment in the warnings file because otherwise it'd be duplicated... well, it turns out that a nice feature of @use is that it won't duplicate, so even though I have written @use './shared/_license.scss 3 times, it only gets imported once, causing it to render as we expect for all 3 stylesheets.
No doubt though your PR got us closer to what we wanted, I was struggling to figure out what you found it.
See commit: https://github.com/jackdomleo7/Checka11y.css/commit/ab3856f1e96c5890a570c4b3bd23a219a5c895d1

@jackdomleo7 I'm glad to have been helped! Nice one using the _license.scss partial instead of the "hackish" solution I proposed. I just had a look at ab3856f and that is a much better approach. Stoked we were able to track this down. Feel free to ping me about any other issues in this project if you need an extra hand in the future.
Also, thanks for your review @alvaromontoro :)


LibWeb: Allow keyboard input to alter email inputs

Previously, theHTMLInputElement.selectinStart and HTMLInputElement.selectionEnd IDL setters, and the setRangeText() IDL method were used when updating an input's value on keyboard input. These methods can't be used for this purpose, since selection doesn't apply to email type inputs. Therefore, this change introduces internal-use only methods that don't check whether selection applies to the given input.
Fixes #3054

This fixes email input on google services, such as gmail login page


chore: fix typos and style

Hey,
Thanks for your PR!!
Can you create a PR that merges to next_build instead of main?

Can you create a PR that merges into next_build instead of main?

done


Add README to https://github.com/cncf/cnfs

[x] Add README to https://github.com/cncf/cnfs

https://github.com/cncf/cnfs/blob/master/README.md

Update content to High-level README:

[ ] Short description (one line: ie “Comparing performance of VNFs vs CNFs”)

[ ] What is this project about?

[ ] Document aspirational message

[ ] What we are aiming for: the aspiration of test bed is you only need an API key from Packet/bare metal to deploy and replicate results

[ ] High-level goals (eg. helm charts, all open source, fully reproducible from bare-metal to full deployment)

[ ] Write up short descriptions of different comparisons

[ ] Add Links to comparisons
[ ] ie. https://github.com/cncf/cnfs/blob/master/comparison/kubecon18-chained_nf_test/README.md

This is the Markdown test area, will be formatted and posted to https://github.com/cncf/cnfs/blob/master/README.md
Draft -
Short Description:
The CNF project provides reference code and test comparisons of Cloud-native Network Functions.
What is the CNCF CNF project?
The CNF project will help facilitate the transition in the NFV world from virtualized hardware running network functions to lightweight, network functions following cloud-native methodologies running on Kubernetes in public, private, or hybrid clouds. For the NFV world moving to cloud-native network functions includes integrating CI/CD, orchestration and service mesh practices from the start.
The reference code and comparisons from the CNF project support the claim that CNFs orchestrated by Kubernetes will provide 3 major benefits to service providers:
Cost savings (capex/opex)
Improved resiliency
Higher development velocity
Note that the CNF project is still in the prototype stage. Additional reference code and benchmarking tests will be added incrementally.
The ideal outcome of the CNF project is that with an API key and a couple of CLI commands, a third party developer can run the provided CNF reference code/benchmarking tests. Furthermore, a developer can re-use some or all of the software in their own environment with minimal, or at least isolated modifications.
CNF project goals
The CNF project includes the following high-level goals:
Comparing Virtual Network Functions (VNFs) vs Cloud-native Network Functions (CNFs)
Providing easily reproducible test cases and use cases
Providing Helm charts for CNFs
Using 100% open source software
Supporting automated deployment from bare-metal up
Building the software in working composable parts
Let’s see some of the test cases
So far the project has been focused on provisioning of the infrastructure to support dataplane CNF test cases that a service provider would be interested in.  This included building up from minimal single NFs running on KVM and Docker to OpenStack and K8s.
Current Test Cases:
CNF chained nf test code
Box-by-box KVM and Docker
Baseline NF Performance on CSIT
Baseline NF Performance on Packet
Getting Involved and Contributing
Are you interested in contributing to CNFs? We, the maintainers and community,
would love your suggestions, contributions, and help! The
maintainers can be contacted at any time to learn more about how to get
involved.
We would love to add more "official" maintainers, so show us what you can
do!
What this means:
Issues

Point out issues that are duplicates, out of date, etc.

Pull Requests

Read and review the code. Leave comments, questions, and critiques.
Download, compile, and run the code and make sure the tests pass.

Also verify that the tests follow best architectural patterns and include tests.


Support configuring additional attributes for traces and metrics (see OTEL_RESOURCE_ATTRIBUTES)

Feature Request
Support configuration to add attributes to traces, similar to OTEL_RESOURCE_ATTRIBUTES (here).
Example use cases

Qualify better the Jenkins instance
Elastic needs a "transaction.type" (here)

Solved supporting the OTEL_RESOURCE_ATTRIBUTES environment variable and the -Dotel.resource.attributes jvm property


Override createRouteSpecificFilterConfig in kill_request http filter

When kill_request http filter is passed in as the route level typed_filter_config, the error below is detected:

As per the troubleshooting result, createRouteSpecificFilterConfig needs to be overriden in https://github.com/xiaobinxbw/envoy/blob/main/source/extensions/filters/http/kill_request/kill_request_config.cc to avoid this error.

cc @stevenzzz

cc @stevenzzzz

Seems this ticket was completed with https://github.com/envoyproxy/envoy/pull/15503 ?


Aqara in different subnet not reachable

Hi,
I have ioBroker running with homekit-controller and successfully paired an Aqara (FP2) device with both iobroker and aqara being in the same network "A".
I want to use Aqara at another location "B" with an own network. Both networks A (<IP_ADDRESS>/24) and B (<IP_ADDRESS>/24) are connected trough a constant VPN tunnel and can communicate among each others. Also both locations A and B have WiFi with the same SSID and password.
The Aqara device successfully connects to the WiFi at location B, it also shows as available and functioning in the Aqara app. ioBroker/homekit-controller can't find it though.
I changed the IP-value [.../info/addess] of the object in ioBroker - which didn't seem to make any difference, connection was still made to the .178.xx IP of network A which was stored after pairing the device. So I hardcoded the new IP address .22.xx of network B in node_modules\iobroker.homekit-controller\build\main.js to try it out, debug log shows that the connection is going out to the correct IP from network B. But - it times out.
So my question is now, whether I am missing something or if what I want to achieve isn't possible at all. I understand this is more of a support request than an issue/bug, but I hope I can get some help or at least a pointer in the right direction here.
Cheers
Michael

The whole Homeklit discovery of devices works via MDNS ... So you need to make sure that this is roiuted between your two networks (which is not default case).

I see, thank you a lot for the pointer. Need to find out if I can make my Vigors pass mDNS.
Yes, noticed that the port changed (had to portscan the device to find the open port), but that made no difference, either.
But I have a clue now in which direction to look, so thanks again.


[Feature request] Full variational Bayes

In algorithm 2 and eqn 24 of the appendix of their paper Kingma & Welling give the details for the estimator of the full VAE.
Could I request this to be implemented to enhance the performance of the package? I'm not aware that there are any torch packages which have done this yet?
Since the Adam optimizer is now available for the optim package, it should be possible to obtain the published negLL of approx 87, in the paper of Rezende, Mohamed & Wierstra.

So the idea of algorithm 2 is to perform variational inference on the parameters of the decoder too.
To implement this, it is necessary to create a new module that reparametrizes theta and then sets the parameters of the decoding layer or perhaps add ζ as parameter to each module in the decoding layer. This would not be a trivial change to the code and I have my doubts if it will improve the negLL by much. Feel free to submit a PR and I will help you out where necessary.

Hi Joost,
thanks alot for the helpfull reply!
I am working on this now, there's some nicely documented theano code which does what you describe. It's not so bad as I have some background in stochastics/Monte Carlo. I'll a submit a PR in the next few days.
Pylearn2 has'nt implemented the adam optimizer yet, so that Theano code only gets negLL of about 94. So it seems that stochastic sampling (full VB), gets an improvment of 7, and adam gets a further improvement of about 7.
There's a new paper DRAW, which uses a recurrent encoder network to selectively read patches of the input, and a recurrent decoder network to selectively write/deposit probability mass to regions of a canvas matrix. The canvas matrix can then be used to generate/reconstruct output. They state they get a negLL of 81 - which is the world best at the moment. Without selective read/write the DRAW model is basically the same as the Welling/Kingma model, except with LTSM encoder/decoder networks, and it gets 87 negLL.
With your experience with your Variational Recurrent Auto-Encoders work, you have much of the background needed to produce the DRAW result? So perhaps we could work on this together, if you are interested?
Coding a variational recurrent auto-encoder which uses importance sampling to perform VI on the parameters of both the encoder/read mechanism and decoder/write mechanism seems like the first step in building this?
Feel free to email me if you like?
All the best,
Aj


Support for multiple source dir/files in blackbox

I would like to add agent (/var/vcap/bosh/log/current) and monit logs (/var/vcap/monit/monit.log) to what gets sent to syslog.  It doesn't appear that is possible today unless agent and monit logs were symlinked into /var/vcap/sys/log?

Sorry it's taken us a while to look at this, thanks for the issue.
We think we'd like to follow these logs. It might be easy to just add them to the paths blackbox cares about, but symlinking them is a not-terrible idea that would get us proper app naming for free, which we'd otherwise have to figure out how to resolve. We're discussing it with the bosh team.
Do you just want these logs, or do you think the general "arbitrary source dir" feature is necessary?

@youngm what's your use case for forwarding those files? monit.log i guess may be useful for debugging some start/stop information, however, agent log is very unlikely to be useful in most cases.

Thanks @anEXPer today those are the only logs I wanted to add to my drain.  I think if bosh chose to symlink or move those logs into /var/vcap/sys so blackbox can pick them up then that would be a perfectly acceptable to me.

Hi @cppforlife I don't have any really strong use cases for agent.log  In the past when debugging various problems we found ourselves wanting to inspect the agent.log to see what the agent was doing and perhaps give us some hint to the problem we're looking into.  That said, I cannot recall any issues we've run into where agent.log helped find a specific problem.  But, I do recall being frequently frustrated that agent.log had rolled so we couldn't inspect it if we wanted to.
Anyway, wanting to drain agent.log is more of a "it could come in handy" type of thing so why not?  But if there are issues with draining agent.log I won't fight not being able to get it.

We don't currently really have a reasonable articulable philosophy for what logs should and shouldn't be forwarded. We're forwarding kernel and audit logs, and job logs; up until these two, there wasn't actually a source of logs on the system that I was explicitly aware we weren't forwarding.
So to the extent we have an implicit philosophy, it's kind of maximalist: "forward everything that normal linux stuff sends to syslog, plus everything written down in the log-place by bosh." Monit and the agent fall outside our current implementation of that structure, but there's no clear reason to me that they should, and it seems like if they log at all, well, they're part of the system and our revealed design goal of "forward everything" seems like it would encompass them.
Not that "forward everything that looks like a log" is the right design goal necessarily, but it's a good place to be able to ratchet back from with custom rules and configuration. We forward lots of stuff that's probably never useful as it is.
Is there a particular volume or content concern with the agent log in particular? We didn't see anything alarming when we briefly inspected it, but we were not thorough.

We're playing around with this and man, that agent logs... all the properties for everything deployed every thirty seconds? So we've developed our own volume concerns around this. Sill interested in other information, but we're leaning towards not forwarding agent logs.

We've investigated this some more, and other things occasionally create/log to /var/vcap/sys/log/monit; our first thought was to symlink to there.
We're coming back around to thinking maybe custom watch-path support would be a reasonable way to enable this, though you'd be constrained by permissions if we were to implement it in rsyslog or capabilities-dropped blackbox, which is definitely the direction we're wanting to go.
At this point, I'm thinking for the monit logs in particular, we might want to ask bosh to write them to a place and permissions level we can read, rather than trying to read from where they are. @cppforlife, is this something y'all might be interested in adjusting?

Having investigated what's involved and the contents of these files, we're back to thinking not forwarding them is probably right for most people. However, there is a workaround if you want to forward from arbitrary files using rsyslog directly, rather than reconfiguring blackbox.
module(load="imfile")

input(type="imfile"
      File="/var/vcap/monit/monit.log"
      Tag="monit"
      StateFile="monit")

in your custom_rules section should allow you to forward logs from monit.
Please let us know if this works for you.
Also, just out of curiosity, do you find the volume of logs emitted by cloud foundry to be a problem? One of the reasons we hesitate to add to the things we're forwarding is that more of our users seem to be concerned that they are receiving too many logs. You are perhaps the first to be concerned that they are receiving too few, and that's interesting.

@anEXPer @Benjamintf1 I think that workaround works for us.
We do think many of the CF components' logging is too verbose.  But we've worked around that issue by building a syslog proxy component that allows us manage CF component syslog output before sending it to our splunk server.  We've had so many problems with CF logging in the past that we decided a custom proxy, where we can work around logging problems ourselves, was the best approach for us.
Our proxy allows us to:

Filter messages and components via regex.
Properly parse all of the different date formats in events sent through syslog so that splunk will have accurate dates and event demarcation without having to use splunk config to detect the dates.
Combine json log messages too large to fit into a single event so it will show up in splunk as a single json event.
Combine java multi-line log message so they will show up as single splunk events.
Rate limit and monitor logging from a given components/host so that a component that goes crazy doesn't eat up our splunk bill.
Aggregate custom information gathered from syslog and re-publish as loggregator metrics/log messages.
Cache events when splunk indexers are down for upgrade
etc

Let me know if you have any other questions we're happy to share.

@youngm Any reason you arn't doing filtering using syslog-release? Does it have to do, with the line splitting/recombining?

@Benjamintf1 Yeah, we already needed some kind of proxy to do the splitting/recombining, rate limiting, setting splunk meta-data, etc.  So, we decided to just do the filtering in the proxy as well.
Another benefit of doing it in the proxy is simpler deployment config.  We could put all of our filters in one runtime config which would be simple from a config standpoint.  However, if we needed to change any filters for any jobs it would require an update of all our instance_groups including our cells.  Or we could localize the syslog-release config for every instance_group independently but that was a little harder to manage from a deployment configuration standpoint since some config is spread across instance groups and some is not.  Doing it all in one place on the proxy puts config all in one place with the added benefit of not having to update all instances_groups for a filter change.
Plus since we control the proxy we could make more complex custom filter rules if we needed too.
Make sense?

@Benjamintf1 Yeah, no problems with load.  We have our proxy clustered for failover.  We're using TCP so a simple DNS LB is sufficient.

@Benjamintf1 If you're going to be at Summit I'd be happy to chat more with you about the problems we have with system component logging and what we're doing now to work around them.  Are you doing office hours?  LMK

@youngm I'm at Summit. We don't have office hours planned, but if you drop by the syslog channel in CF slack we can definitely arrange some impromptu office hour style availability.


Add probe argument to ForcedResponseResults

Replace dof by probe argument
probe is a list of tuples. Each tuple refers to a probe, which must include de node and the orientation.
The orientation units is set by probe_units argument.
in plot() method, data.showlegend is turn off to avoid repetitive legend marks on graphs

@raphaeltimbo, I did a generic modification to api_report.py, only to run the tests, since we're moving this file and it's pretty behind from what we have on ROSS_Report repository.


Make sure there is a val to be set for existing filters

Found a bug on having filter set in the explore view effecting renders in the dashboard. Added a safe check to make sure val is an actual key before throwing an KeyError exception in the dashboard
@mistercrunch

Codecov Report

Merging #5257 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master    #5257   +/-   ##
=======================================
  Coverage   63.28%   63.28%
=======================================
  Files         259      259
  Lines       19689    19689
  Branches     1968     1968
=======================================
  Hits        12461    12461
  Misses       7219     7219
  Partials        9        9

Impacted Files
Coverage Δ

superset/utils.py
87.8% <100%> (ø)
:arrow_up:

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 eb67651...83ea4a7. Read the comment docs.


Fix PLpgSQL heuristic rule

Fixes the PLpgSQL heuristic rule as discussed in #2384.

:+1: many thanks @pchaigno


Probability challenge dataset is not available

Describe the bug
Dataset for challenge is not available.
To Reproduce
Steps to reproduce the behavior:

Go to /1-Introduction)/04-stats-and-probability/](https://github.com/microsoft/Data-Science-For-Beginners/blob/main/1-Introduction/04-stats-and-probability/notebook.ipynb)
Click on 'SOCR MLB Height/Weight Data'
See no download available for required dataset.

Expected behavior
Download link for dataset should be available.
Desktop (please complete the following information):

OS: Windows10
Browser: Chrome
Version 101.0.4951.67 (Official Build) (64-bit)

hi, it's available on that web page as an embedded table, but maybe it should be exported with attribution

Thanks for your response, Jen.
What is attribution? I've tried googling and am only seeing results related to marketing. Could you clarify?

Attribution refers to the set of rules that determine which ad gets credit for a sale or a conversion.

hi @NathanielPather  - sorry, I wasn't clear. I meant that we can scrape the dataset from the page and link it, but I want to make sure to credit the original author, thus to give attribution so we don't lose sight of the source. thanks!


onFriendRequest() not working

# -*- coding: UTF-8 -*-

from fbchat import log, Client

class user1script(Client):
    def onFriendRequest(self, from_id, **kwargs):
        print "FReq"

cl = user1script("myEmail@domain.extention","myPassword")
cl.listen()

But nothing print when someone send me a request. Please help

Thanks for opening this issue! I looked into it, and i found that it has been disabled for quite a while, apparently by @Dainius14, though this isn't mentioned anywhere.
I will investigate this, and if it's actually broken, attempt to fix the issue

I un-commented the code and it seems to work just fine. I can make a PR if you'd like


Point the build status link to statrs

Happened upon this when clicking around.

Thanks, appreciate it!


Use lenses in undo buttons

Per this comment, make DebatePanel.scala's undo buttons uses lenses for cleaner code

Thought about it a bit more and I have another idea which I think should be cleaner, I’ll look into it at some point

Finished as of b6e312eb30f07c8382de7fae38c61c9c38bce579.
Didn't actually use lenses/optics — I produced objects explicitly corresponding to the state transitions available at the current debate state.


Consider using rustc_lexer

rustc_lexer
rustc_lexer is now the lexer used by rustc and is on crates for reuse. rust-analyzer is already using it. It would make sense for proc-macro2 to also use rustc_lexer and only have to do bracket matching and trivia stripping.
I spent a little time trying to do so, but I'm not familiar enough with the current fallback parser to do so. I can attempt just ripping everything out and building from scratch on rustc_lexer, but I'd prefer to have a go-ahead before putting time into that.

That's good to know! This would probably help fix #126 and related issues as well.
FWIW you probably wouldn't need to rip out the entire fallback parser as it exists today. The only entry-point to it (if I remember correctly), which is the FromStr impl for TokenStream.
This code then goes on to lex the entire input string & generate a TokenStream out of it. With the new API, you'd iterate over the tokenize output and generate the corresponding TokenTree instances. Once it's gone you can drop the strnom module and about ~600 lines of fallback.

Unfortunate news: rustc_lexer uses std::iter::from_fn, which was stabilized in 1.34.0, which is later than the current MSRV of 1.31.0.


Separate instrument manufacturer and instrument model.

Instrument manufacturer and model need to be separated in the vocabulary to be compliant with PIDINST.

To be implemented. Introduce categories of instrument manufacturer and instrument model.


Activate Per Tenant Settings Feat and use ACA-Py 0.8.2 image

Follow-up to #580

@shaangill025 can run npm run lintfix in frontend folder to get the Tenant UI build to pass

(some tenants for testing)
Issuer:
260f147e-1d98-4488-b6ec-dd47b1c6d64f
fd967634-d290-4f54-a3ec-3469a15d4ff7
Not an issuer:
a60cc559-d273-4245-b1f6-577d6eeed8eb
ac27f6df-97a5-4b7c-9dce-2fec85ef3a21

Altering the settings through the UI seems to be working well from what I understand from testing out.
I have some questions about how default state should be handled (sorry if already discussed and I missed it).
Using the Auto Respond message field as the example here but I think it applies to all, depending on default values...
Right now if you pull up the settings on a new Tenant you'll see there is no settings property in the response for something that hasn't been 'set' yet
Going into a new Tenant, all the settings are unset (false for the switches)

Because nothing comes back from the wallet settings endpoint for these extra settings unless the user has already set one of the fields

So it looks like Auto Respond to Messages is false, but if I send the tenant a message the tenant does auto-respond

This would be because that's the system default I assume?
Toggling it on and then off and saving does then set the setting for that Tenant

So I think this is a possible confusion for Tenants if these settings appear 'turned off' but then they're actually possibly 'on' if that's the default system setting?
If I have that assumption correct...
So if this is the case I could see handling it in a couple ways

Purely in the Tenant UI? Use a tristate checkbox? https://primevue.org/tristatecheckbox/
Some other UX to display that the defaults are being used and opt in to setting yourself?
Maybe when a tenant is created, have the settings persistence set to the current state of the fields defaults? Not sure if possible or other knock-on effects.
If the setting is not set, then the api still returns the setting value, but pull from the default.

Option 1 is probably easy, could make another ticket to address that.
Questions for @esune about how we want Tenants to deal with this case.
Tagging @shaangill025 and @usingtechnology if they had any thoughts from the aca-py PR 2233. IE should this just be the Tenant UI's problem, or does this need default situation need any more consideration in the core?

good work integrating that and your analysis.
the simplest thing (i think) would to ALWAYS return the full (tenant) set of effective settings.

My $0.02CDN — if I’m understanding the issues:

ACA-Py allows tenants to update settings, get settings.  I assume there are endpoints for those already.
Traction instances are configured (or hardcoded?) to have default settings for a new Tenant, applies the settings on/after creation of each tenant.  These might include ACA-Py settings as well as Traction settings — e.g. “Is Issuer” Traction setting, “Has Public DID".
The Traction UI always uses get settings when settings need to be displayed.
The Traction UI to update settings updates the ACA-Py settings for the tenant.

Could we just make the settings explicit on tenant creation? i.e.: the tenant settings are set to what the instance defaults are on creation of a new tenant.
This would cause calls to the get settings endpoint to reflect the actual state, rather than return undeined and potentially lead to confusion. This might need to be a change in the multitenancy code - @shaangill025 can you chime in?

Could we just make the settings explicit on tenant creation? i.e.: the tenant settings are set to what the instance defaults are on creation of a new tenant. This would cause calls to the get settings endpoint to reflect the actual state, rather than return undeined and potentially lead to confusion. This might need to be a change in the multitenancy code - @shaangill025 can you chime in?

That makes the most sense to me as an API consumer I think. I create a Tenant, I ask it for what the current settings for that Tenant is, and it tells me the settings, same as if they'd been set by the user.
Unless it's that the settings are meant to only be overrides of the defaults. IE consider what happens if you create a Tenant, don't touch settings, and then re-set the system defaults (if that's possible)
Not sure if there's downsides on the ACA-Py side or anything.

That makes the most sense to me as an API consumer I think. I create a Tenant, I ask it for what the current settings for that Tenant is, and it tells me the settings, same as if they'd been set by the user. Unless it's that the settings are meant to only be overrides of the defaults. IE consider what happens if you create a Tenant, don't touch settings, and then re-set the system defaults (if that's possible) Not sure if there's downsides on the ACA-Py side or anything.

I think we should make the API as straightforward as possible, which means return whichever value that setting is for the tenant - even if it is an override of the defaults, I will need to know what the default values are.

it's only a small set that the user/tenant can self-manage. i think that complete set should get returned all the time. i guess the decision would be whether what is stored in wallet are just the changes (overrides) and those get layered on top of the system settings or if you do as @esune suggests and copy the current system settings into the wallet and that is what the tenant manages.  that is probably the simplest way.  could add a method to reset to system defaults too (remove all your customizations). it may make it difficult to add new settings (or remove) to the tenant but you could probably figure a way to "sync" the allowable set when the wallet is queried for it's extra_settings.

@shaangill025 also FYI see discussion here https://chat.developer.gov.bc.ca/group/ditp-products-teams?msg=i5bN84Q7hZiyreeW7
about ACA-Py image version using askar-only image
Sherman has updated in this PR as well to test it out https://github.com/bcgov/traction/pull/684

Sorry not sure how but I deleted this branch accidentally while cleaning another one 😱 in my Git browser. Restored and reopened PR.

See review comments above, but another question (forgive me if I missed this earlier, was only ever looking at the initial specification for the PUT /multitenancy/wallet before) I have is about the difference between the field naming for editing these settings vs fetching them.
When a consumer calls
GET https://pr-682-traction-tenant-proxy-dev.apps.silver.devops.gov.bc.ca/tenant/wallet
to see the subwallet, all these settings come back in this form

But when updating with
PUT https://pr-682-traction-tenant-proxy-dev.apps.silver.devops.gov.bc.ca/tenant/wallet
it's extra_settings instead of settings and the field names are the env var style

Not sure if could be adjusted or if it's an ACA-Py limitation or anything, but just raising that it's confusing from a REST standpoint IMO.

@loneil The settings in the response schema are settings already saved to the wallet_record. This is different than the extra_settings in the request schema, where configurable per tenant settings can be provided and saved to the wallet_record.
Re env_var, the following objects provide the association keys to configurable settings in ACA-Py:
ACAPY_LIFECYCLE_CONFIG_FLAG_MAP = {
    "ACAPY_LOG_LEVEL": "log.level",
    "ACAPY_INVITE_PUBLIC": "debug.invite_public",
    "ACAPY_PUBLIC_INVITES": "public_invites",
    "ACAPY_AUTO_ACCEPT_INVITES": "debug.auto_accept_invites",
    "ACAPY_AUTO_ACCEPT_REQUESTS": "debug.auto_accept_requests",
    "ACAPY_AUTO_PING_CONNECTION": "auto_ping_connection",
    "ACAPY_MONITOR_PING": "debug.monitor_ping",
    "ACAPY_AUTO_RESPOND_MESSAGES": "debug.auto_respond_messages",
    "ACAPY_AUTO_RESPOND_CREDENTIAL_OFFER": "debug.auto_respond_credential_offer",
    "ACAPY_AUTO_RESPOND_CREDENTIAL_REQUEST": "debug.auto_respond_credential_request",
    "ACAPY_AUTO_VERIFY_PRESENTATION": "debug.auto_verify_presentation",
    "ACAPY_NOTIFY_REVOCATION": "revocation.notify",
    "ACAPY_AUTO_REQUEST_ENDORSEMENT": "endorser.auto_request",
    "ACAPY_AUTO_WRITE_TRANSACTIONS": "endorser.auto_write",
    "ACAPY_CREATE_REVOCATION_TRANSACTIONS": "endorser.auto_create_rev_reg",
    "ACAPY_ENDORSER_ROLE": "endorser.protocol_role",
}

ACAPY_LIFECYCLE_CONFIG_FLAG_ARGS_MAP = {
    "log-level": "log.level",
    "invite-public": "debug.invite_public",
    "public-invites": "public_invites",
    "auto-accept-invites": "debug.auto_accept_invites",
    "auto-accept-requests": "debug.auto_accept_requests",
    "auto-ping-connection": "auto_ping_connection",
    "monitor-ping": "debug.monitor_ping",
    "auto-respond-messages": "debug.auto_respond_messages",
    "auto-respond-credential-offer": "debug.auto_respond_credential_offer",
    "auto-respond-credential-request": "debug.auto_respond_credential_request",
    "auto-verify-presentation": "debug.auto_verify_presentation",
    "notify-revocation": "revocation.notify",
    "auto-request-endorsement": "endorser.auto_request",
    "auto-write-transactions": "endorser.auto_write",
    "auto-create-revocation-transactions": "endorser.auto_create_rev_reg",
    "endorser-protocol-role": "endorser.protocol_role",
}

@loneil The settings in the response schema are settings already saved to the wallet_record. This is different than the extra_settings in the request schema, where configurable per tenant settings can be provided and saved to the wallet_record. Re env_var, the following objects provide the association keys to configurable settings in ACA-Py:

Ok, thanks for the explanation @shaangill025 . Yeah just that what results in the REST shape for the multitenancy endpoints I think could end up confusing for a Traction consumer (PUTing and GETing on the same endpoint). I'm fine with it as it is if there is a difference between the two concepts as you said, I think most usage of this would be through the Tenant UI anyways which abstracts consumers really needing to know about it.

moved to review/qa as per feedback from @shaangill025

I think it looks good. I don't know enough about all the settings to test them out but I tried a couple on and off and got the expected results.
Did basic regression testing on the deployed PR and could create tenants and connect and issue and all that.
👍


Rapid Document Write through FOXX causes timeout

I think this is a unique situation but would like to get feedback.
I'm doing some data mining project and I create documents dynamically and write them to ArangoDB through FOXX. I need to do this one at a time so that my app can get the created _key from arango and assign it to that bit of data.
When I do this I can write to ArangoDB at about 300 posts per second. Yay!
After around 16000 documents ArangoDB times out. I then have to wait for 5 minutes (or restart Arango) to continue the process.
I've tried playing with index bucket size and journal size but the result is always the same.
I'm running ArangoDB 2.8.4 on Mac OS X.
Documents are tiny but I have nearly a million of them:
{
    "_from" : "foxxapp_datacol/2073050929375",
    "history" : {
        "2016-03-31" : 2
    },
    "rating" : 10,
    "popularity" : 2,
    "_key" : "2262876573202",
    "_to" : "foxxapp_datacol/2087500641663"
}

you're not by accident using the homebrew version compiled with clang?

That is a strong possability. I can't remember how I initially installed ArangoDB but it may well have been using brew.
I should perhaps try the downloaded binary?
Anything I can try/do?

With el capitans clang release ArangoDB performance on MacOSX came to a grinding halt, which is why the package strongly sugests to use gcc instead. You can try either that and rebuild ArangoDB,
Or download one of the binary packages available on https://arangodb.com/downloads and retry with those.

Looks like I'll have to wait. That link shows me [php snippet=3]
Someone doing site maintenance?
When I do get it right, I'll come back with whether it worked.

ooouuups, fixed. Thanks for reporting.

Ok, using the downloaded version, set up my FOXX app and began writing.
16340 document(s) and it stops. I checked logs and nothing.
Just times out. Any more ideas?!
I can enable sync and let it run over night. Enabling Sync has a massive performance impact (Obviously).

How is the disk activity during the first 10k writes and how shortly before
the timeout? Does it constantly grow to a point at which it would have to
sync more data to disk than the storage device is capable of? How is the
RAM utilization at the same time? Does the OS start to swap at some point
because of insufficient main memory?
I can imagine that there's a point at which the server should reject writes
because of high load, instead of accepting them and eventually fail.

Does it constantly grow to a point at which it would have to sync more data to disk than the storage device is capable of?

I presume you mean in terms of performance, but i doubt this as my latest test slows the write speed to one tenth (about 10 documents a second) and it still times out after around 16 000 documents. It just takes longer.
I will run tests for ram and disk utilization and get back.
FYI: The machine does have 8GB of ram.

Okay, so it's apparently not the SSD/HDD that chokes on the data, but the database. We will investigate this further.
Is there any chance that you provide us with the data to try to reproduce the error?
Even if not, please describe the data and your setup in more detail (total size of data to write in gigabytes, average document size and structure, what secondary indexes you created...)

@riverdusty If you're using Foxx with Model and Repository, try using raw schemas and collections.
You can pass a joi schema directly to the bodyParam method instead of a Foxx Model and it will pass on the validated object instead of a Foxx Model instance. You can then write that to the collection directly (if you don't know how to get a reference to the collection, just use the collection property of the Foxx Repository instance).
When using Model and Repository there is some overhead wrapping and unwrapping the document as it travels through Foxx. That shouldn't explain the magnitude of slowdown you're experiencing but it might magnify the underlying performance problem.

Interesting.
Mac OS X My Virtual Memory (From the Web Interface) sits around 6GB.
Windows VM sits at 0.2GB.
I just ran this against ArangoDB 2.8.7 on Windows Server 2008r2 x64.
It didn't do a time out and my 15-min-avg Virtual Size was 0.18.
Also, where is my prevous message? (sigh, I blame South African Internet).
Anyway, @pluma I don't get a slowdown. I get a sudden stop. One second posting 300 docs, next nothing, just stops. Always around 16000 document mark, which leads me to think its Virtual Size limit.
@Simran-B data is what I posted in the first post, with only key's changing.
Its a standard edge collection:
ID 	Type 	Unique 	Sparse 	Selectivity Est. 	Fields
0 	primary 	true 	false 	100.00% 	_key
3730254115 	edge 	false 	false 	100.00% 	_from, _to
The behaviour happens with a document collection as well, so I doubt its a collection specific thing.
Figures from the Windows setup that completed.
Type 	Count 	Size 	Info
Datafiles 	1 	32 MB
Journals 	1 	32 MB
Compactors 	0 	0 B
Shape files 	0 	0 B
Indexes 	1 	4.4 MB
Type 	Count 	Info
Shapes 	2130
Attributes 	8
Uncollected 	12737
References 	0
Type 	Count 	Size 	Deletion 	Info
Alive 	46095 	60.05 MB 	-
Dead 	0 	0 B 	0
58832 document(s)

Figures from the same collection with the same docs (Identicle) but on the Mac.
Type 	Count 	Size 	Info
Datafiles 	2 	64 MB
Journals 	1 	32 MB
Compactors 	0 	0 B
Shape files 	0 	0 B
Indexes 	1 	4.4 MB
Type 	Count 	Info
Shapes 	2234
Attributes 	8
Uncollected 	6866
References 	0
Type 	Count 	Size 	Deletion 	Info
Alive 	51966 	67.78 MB 	-
Dead 	0 	0 B 	0

I've added a dummy app based on the description: foxxapp1803.zip

Have you been able to reproduce this issue with ArangoDB 3.0.0-rc2? We haven't been able to reproduce the problem with the provided dummy service so I'm not sure whether the underlying issue is still present.

Hi,
seems I got the same issue on 3.1.3 (both brew and official packages).

This was related to the MMFiles storage engine, which isn't supported anymore.
Closing.


Add AuctionHouse loading and lowest BIN endpoint

Requires new .env key SKYHELPER set to true to enable AuctionHouse loading through Redis

We changed our minds and are not going to make this endpoint public


[rbac] Group roles test

Issue: AAH-1616
This test includes:

testing of assigning roles to groups

should add a new role to group
should test filtering of assigned roles
should test filtering of roles in "Add roles" wizard
should correctly select and preview roles
should be able to remove role from group
should not display deleted role in group detail
should show group empty state
- moving permissions to the permissions.js file for reusability

adding cy.commands:  createRole, addRoleToGroup, deleteRole => using galaxykit now
removed removeAllPermissions and addAllPermissions
fixed group_management.js test
removed group_permissions.js (rbac.js test does the job now)
removed permissions.js file, which is not useful with new galaxykit commands.

Fixed double data-cy conflict and merging.


Colombian holidays

There are three kinds of Holidays in Colombia.

Fixed dates holidays: They are always observed on the exact date and are never observed on a weekday if they happen to fall on the weekend; e.g. christmas, new year's eve, etc.
Emiliani law holidays: These are mostly religious holidays that are always observed on the following Monday, unless they happen to fall on a Monday.
Easter based: These are also religious holidays, but the date is based on Easter. Some like "Good Friday" always occur on a Friday, but others like Corpus Christi are observed on the following Monday, unless it falls on a Monday.

Observed feature supported

For the fixed date holidays, if observed=True and they fall on a weekend they are not observed.
If observed=False there are 18 holidays in total.

No idea why it stills fails for Python 3.2.

This is great. Thank you!


Export experience.ts from index file

Related Issues

[none]

Security Implications
[none]
System Availability
[none]

Currently importing like so

Oh don't forget to bump the package version also


Unable to control scenes

I can setup a simple control with a Device and send TRUE and FALSE to turn on a DEVICE.  However when I do the same thing with a Scene nothing appears to happen.
Using the Websocket I see that when I send the Scene a TRUE or FALSE payload that Status messages appear but no command message appears.  I assume this is an issue on my end but not clear how to resolve.

Was looking at the code and in the isy-scene.js the method runCmd(), should probably look exactly like the runCmd() in isy-node.js

Note I was testing my ISY side to make sure it was working correctly.  If I send this http://XXXX/rest/nodes/25623/cmd/DON then that scene at 25623 turns on.  I pulled the node address from node red to make sure the scene id was correct.

Maybe change this in isy-scene.js
 var url = '/rest/nodes/' + this.address + '/cmd';         for (i = 0; i < arguments.length; i++) {             cmd += ('/' + arguments[i]);         }
to
if (Array.isArray(cmd) && cmd!= []) {             params.forEach(function (value, index) {                 url += ('/' + value);             });         } else {             url += '/' + cmd.toString();         }
I am new to node.js and nodered, so not sure if the way this method is getting called if arguments is defined.  That may only work from command line call and not from another method call.  Again though never used node.js.

FYI - just applied this to my local copy and it does seem to resolve the issue.

I can't control Scenes or Programs. I tried your edit but that didn't help and caused a url error in debug. I have node.js 8.xxx and node-red .19.5 Could you send me your files to I may compare and see if it will get it working on my setup?


Modification Subquery is not passthrough

Modification subqueries cannot be treated as passthrough.
They need to perform all subquery executions even if the result is skipped, so they are expected to produce less output then input on skip situations.
Jenkins:
http://jenkins.arangodb.biz:8080/view/PR/job/arangodb-matrix-pr/10241/

Included in https://github.com/arangodb/arangodb/pull/11754/
Will close this now and instead please take the other one.
They are too tightly coupled and the other is ready to merge.


BNGBlaster counts rx-packets when disabling qdisc-bypass

Describe the bug
When configuring qdisc-bypass: false and a downstream-only stream, BNG-Blaster shows rx-packets on the network-interface, although no rx-packets are received:

This wrongly counted rx-packets are included in the report, too:
Interface: veth1.1
------------------------------------------------------------------------------
  TX:                     66034 packets         18876671 bytes
  TX Polled:                  0
  RX:                     66086 packets         18881052 bytes
  RX Protocol Error:          0 packets
  RX Unknown:                 0 packets
  RX Polled:                945

A10NSP Interface: veth1.1
  TX:                     66034 packets         18549487 bytes
  RX:                     66086 packets         18881052 bytes
  TX Stream:              66021 packets
  RX Stream:                 33 packets                0 loss
  Session-Traffic:
    TX IPv4:                 33 packets
    RX IPv4:                 33 packets                0 loss
    TX IPv6:                  0 packets
    RX IPv6:                  0 packets                0 loss
    TX IPv6PD:                0 packets
    RX IPv6PD:                0 packets                0 loss

Interface: veth1.2
------------------------------------------------------------------------------
  TX:                        54 packets             4655 bytes
  TX Polled:                  0
  RX:                     66087 packets         18617162 bytes
  RX Protocol Error:          0 packets
  RX Unknown:                 0 packets
  RX Polled:                945

Access Interface: veth1.2
  TX:                        54 packets             4655 bytes
  RX:                     66087 packets         18617162 bytes
  RX Multicast:               0 packets                0 loss
  TX Stream:                 33 packets
  RX Stream:              66021 packets                0 loss
  Session-Traffic:
    TX IPv4:                 33 packets
    RX IPv4:                 33 packets                0 loss
    TX IPv6:                  0 packets
    RX IPv6:                  0 packets                0 loss
    TX IPv6PD:                0 packets
    RX IPv6PD:                0 packets                0 loss

When setting qdisc-bypass: true the rx-packets are not counted:

To Reproduce
Use the PPPoE Quick-Start guide and disable qdisc-bypass.
Version (bngblaster -v):
Version: DEV
Compiler: GNU (11.4.0)
GIT:
  REF: HEAD (0.8.23)
  SHA: 2aba470164a8b779579f10c329e7a9790cb9f454
IO Modes: packet_mmap_raw (default), packet_mmap, raw, dpdk

JSON configuration:
{
    "interfaces": {
        "qdisc-bypass": false,
        "a10nsp": [
            {
                "__comment__": "PPPoE Server",
                "interface": "veth1.1"
            }
        ],
        "access": [
            {
                "__comment__": "PPPoE Client",
                "interface": "veth1.2",
                "type": "pppoe",
                "outer-vlan-min": 1,
                "outer-vlan-max": 4000,
                "inner-vlan": 7,
                "stream-group-id": 1
            }
        ]
    },
    "pppoe": {
        "reconnect": true
    },
    "dhcpv6": {
        "enable": false
    },
    "session-traffic": {
        "ipv4-pps": 1
    },
    "streams": [
        {
            "stream-group-id": 1,
            "name": "S1",
            "type": "ipv4",
            "direction": "downstream",
            "priority": 128,
            "length": 256,
            "pps": 2000,
            "a10nsp-interface": "veth1.1"
        }
    ]
}

Steps to reproduce the behavior:

Configure qdisc-bypass: false
Run BNG Blaster and observe rx-packets

Additional context
We want to bypass qdisc in egress to apply tc netem rules for simulating network issues like packet loss, latency etc.

Hi @GIC-de, the issue still exists on 0.9.7. Do you have any idea, what is the reason for it?


Default limit for listObjects not working

We have a default limit of 100 here but it is not being taken into account
https://github.com/supabase/supabase/discussions/996

Fixed in https://github.com/supabase/supabase-js/commit/45780d4a18ded75d616546b7b89995ba995bda05


Release, please :)

Getting error in 0.4.1 on test collection:
.../site-packages/schemathesis/extra/pytest_plugin.py:53: in collect
    filter_endpoint=self.schemathesis_case.filter_endpoint,
.../site-packages/schemathesis/extra/pytest_plugin.py:50: in <listcomp>
    item
.../site-packages/schemathesis/schemas.py:88: in get_all_endpoints
    prepared_parameters = self.get_parameters(parameters, definition)
.../site-packages/schemathesis/schemas.py:102: in get_parameters
    self.process_parameter(result, parameter)
.../site-packages/schemathesis/schemas.py:117: in process_parameter
    self.process_body(result, parameter)
.../site-packages/schemathesis/schemas.py:131: in process_body
    if body["type"] == "object":
E   KeyError: 'type'

As I can see, it was fixed in #50 (thanks to mutmut). When the release is going?

Hello :) not near my laptop - will do this evening

Done!

Please, let us know if it solves the issue :)


Add TechTreeKompacted

Has CKAN badge on SD but no PR. Author confused why not indexed yet on thread.

https://spacedock.info/mod/2600/TechTree Kompacted?ga=<Game+3102+'Kerbal+Space+Program'>
https://forum.kerbalspaceprogram.com/index.php?/topic/199096-111x-techtree-kompacted-13/

The instructions in the ZIP say CommunityTechTree is required, but the forum thread says that is no longer the case:


Constant redirect

Describe the bug
when loginUrl is /app and rootUrl app/admin it always redirects to the login when there is redirectUrl in the response - frontend thinks that user has been logout - we have to change match to endWith
Installed libraries and their versions

<EMAIL_ADDRESS>
Expected behavior
It should redirect only when the redirectUrl match exactly to loginUrl

the error doesn't occurs anymore

the error doesn't occurs anymore

Am having issues trying to make use of my own login page  with addmin bro

I need help please


Adding frontend testing

@damienbod @FabianGosebrink
I added Angular testing:

I created angularApp/tests folder for .spec.ts files: but all the specs files in angularApp will be used if they will be put next to the things they test
I added karma.conf.js for Karma test runner
I created config folder in the root of the project, and I added there webpack.test.js file used by Karma to build the test and spec.bundle.js that contains its context: I think we should move other configuration files in this folder, because they are growing...
I updated the README with an essential explanation of the tests (feel free to extend it!)

Greetings,
Roberto

excellent, thanks a million

Looks great, thanks a lot @robisim74 !!!


Update supported NIF API version to 2.16

Fixes #357.

Is there anything holding back this change from being merged?

Nope :)

Thanks @filmor!  Is there a planned release date for v0.22?  This fix will hold my project back from moving to OTP 24.


tests: Add integration test for KBS encrypted OCI image

Current unit tests in pull module only covered the tests for container
image encrypted by a public key file.

The integration test verify the container images encrypted by an KBS.
How to create KBS encrypted container image is documented in:
test_data/generate_test_data.md

It will first launch an attestation-agent daemon build
with sample KBS support. Then it will try to pull an KBS encrypted
container image to verify pull_image API.

Hi @arronwy , I gave just a couple suggestions. Overall it looks great!


style(report): Fix typo

Please read the Pull Request Checklist to ensure you have everything that is needed to get your contribution merged.

Already made upstream. Closing.

But that's in develop! Did it also go into hotfix?

Yes, it did.

Pull Request Test Coverage Report for Build 407

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

Totals

Change from base Build 405:
0.0%

Covered Lines:
17620

Relevant Lines:
38707

💛  - Coveralls


Add Docker Containerization to the Project

Description: This issue proposes adding Docker containerization to the project to standardize the development and deployment environment. Containerizing the application will ensure that contributors and users can run the project with consistent dependencies and configurations across different machines.

Create a Dockerfile that builds and runs the project.
Ensure the Dockerfile is efficient and uses multi-stage builds (if necessary).
Use an appropriate base image (Node.js, etc.).

Benefits:

Simplifies project setup for contributors.
Ensures consistent environment configurations.
Easier deployment to cloud platforms that support Docker.

please assign me this issue under gssoc-extd and hacktoberfest


In Cloud Formation; -- Request limit exceeded. (Service: AmazonEC2; Status Code: 503; Error Code: RequestLimitExceeded; Request ID: 7fd6cf20-2880-4845-a2f5-3fa30583767f)

Hi, I'm trying to create the stack in Cloud formation with 15 beanstalk applications. I've successfully added 13 app and tested with CF and also got the successful result. But if I'm going to add 14th app, then I'm getting the below error randomly.
19:32:04 UTC+0550 | CREATE_FAILED | AWS::ElasticBeanstalk::Environment | envsocureactionauditprod1515 | Request limit exceeded. (Service: AmazonEC2; Status Code: 503; Error Code: RequestLimitExceeded; Request ID: 7fd6cf20-2880-4845-a2f5-3fa30583767f)
I've checked and already increased the EC2, ASG and CLB limit. But I don't know why I'm getting this error. Anyone help me on this issue.

@sureshbabur seems like you ended in repo by mistake as it sounds like you have a cloud formation question. i would recommend contacting aws support with a request to up your quota.

@cppforlife, I already increased the EC2, ASG and CLB limit. But still I'm getting the an error

@sureshbabur the error is not for a specific product limit, but the API usage in general. You'll need to follow up with AWS Support or reduce the rate at which your CloudFormation is provisioning resources.


Stackable prefixes

An issue i've had with not just this plugin, but almost all permission plugins, is the fact that Group prefixes don't seem to stack,
This is a small suggestion it would just require two lines in the config
a); a string that allows you to set a Suffix / prefix between the prefixes (Like a space)
b); And an option to enable this feature ;)

My thoughts are that you could just specify in the config how many prefixes you want to show, and it will pick the highest x prefixes from all of the ones a user has.
For example, if a user has/inherits the following prefixes:
100 - [Mod]
50 - [Builder]
20 - [Some high level donator]
10 - [Some low level donator]
5 - [Member]
And the config is just set to pull the top 3, they'd get:
[Mod] [Builder] [Some high level donator] Luck: Hello

Great to know!
My idea on the matter, By idea i hope you just mean how to format that chat rather than backend running code.
user: Tau has main group Mod, Inherits Platinum, Premium, (Inherits sub staff ranks via group inheritance tree)
The Primary group's prefix should be first, irrelevant of the prefix priority.
[Mod] [Platinum] [Premium]
There should be a string in the config that looks like this (This is a pattern)
SuffixPrefixSpacer: " " // This is here so users can apply a spacer between group/user prefix/suffixs
SuffixSuffixSpacer: " "
PrefixPrefixSpacer: " "
PrefixSuffixSpacer: " "
applyPrefixSpacerAfterLastPrefix: false // This denotes if the above spacers will be applied after the last prefix/suffix in chat.
applySuffixSpacerAfterLastSuffix: false
enableStackablePrefixes: true
'%gmainprefix% %uprefixs% gprefrixs'
gmainprefix is the placeholder for Primary Group.
uprefix is the placeholder for a users prefixs. (By priority)
gprefix is a placeholder for one of the users groups (By priority)
uprefixs is a placeholder for ALL of the users prefix(s)
gprefixs is a placeholder for ALL of the group prefix(s)
(gsuffix etc)
example 2:
'%gmainprefix% gprefrixs(1-20) uprefixs gprefixs'
In this example only prefixes with the priority of 1-20 will be shown in that area.

I'm thinking something like:
meta-options:
   prefix:
      format:
        - "highest_own_prefix"
        - "highest_prefix_donor"
        - "highest_prefix_staff"
      start-spacer: ""
      end-spacer: ""
      middle-separator: " "

and then obviously the same for suffix.
The default would just be this, which is backwards compatible with the current system.
meta-options:
   prefix:
      format:
        - "highest_prefix"
      start-spacer: ""
      end-spacer: ""
      middle-separator: ""

The name of a track can be included at the end of "highest_prefix" to filter results by track.


[cmake] Get the default value for LLVM_ENABLE_ASSERTIONS from LLVMCon…

What's in this pull request?

Resolved bug number: (SR-)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

…fig.cmake.
rdar://26154980

@swift-ci Please smoke test and merge

@swift-ci Please smoke test


Update short description and logo

Questions
Answers

Description?
update short description and logo

Type?
improvement

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes {https://github.com/PrestaShop/PrestaShop/issues/15858}.

How to test?
Please check that short description and logo are updated.

Hello @Julievrz
I have the new description but the logo that I found https://drive.google.com/drive/folders/1vaoyYz4LFRJr1cPM_T4D1cw4sI_cmneS is not updated for me.
See screenshot below:

Thank you

@ngodefroy It's probably because the old image has been cached by your browser. You should try to force reload the page.

Hello @Julievrz
I have the new description but the logo that I found https://drive.google.com/drive/folders/1vaoyYz4LFRJr1cPM_T4D1cw4sI_cmneS is not updated for me.
See screenshot below:

Thank you

I don't know why the logo didn't update as I changed it with the good one on the file.

It's a browser cache issue. Keep in mind when you test a pull request to fully clear your browser cache, or use different subdomain/directory path each time you run a new test.
This one doesn't require QA and can be merge without it.

Thank you @Julievrz


Update the flutter create pubspec.yaml template to use the google_fonts package

This section: https://github.com/flutter/flutter/blob/3c37db0520793a513eda481c3e020dbe9bd68d1c/packages/flutter_tools/templates/app/pubspec.yaml.tmpl#L74
should be modified to show how to more easily include fonts with the google_fonts package. It should still link to https://flutter.dev/docs/cookbook/design/fonts for advanced cases.

Can I work on this issue?

@bharat-1809  Yes!

@bharat-1809 Yes!

Thanks. I'll start working on it

Hi @clocksmith, I have opened a PR for this issue. Please have a look.

Closing given that the PR was not accepted.


Drop compatibility section from the documentation

Description
Part of https://github.com/inmanta/irt/issues/1982
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[x] Attached issue to pull request
[x] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
[x] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
- [ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in 6db91126b2417520ecc2f47175b6491b4791db4e

Processing #7438.

Processing #7439.

Processing #7439.


download for x did not complete, please try again

Firstly thanks for this awesome tool. secondly, I was testing how it works with a specific page for anime that came to my mind Sword Art Online.
For some reason with the first season it error with
python .\src\__main__.py -i https://www.wcostream.com/anime/sword-art-online
Settings Loaded.
Downloading show
[wco-dl] - Downloading Sword-Art-Online-Extra-Edition-English-Dubbed-2-S01E00-
0it [00:00, ?it/s]
[wco-dl] - Download for Sword-Art-Online-Extra-Edition-English-Dubbed-2-S01E00- did not complete, please try again.

[wco-dl] - Downloading Sword Art Online-S01E25-English Dubbed 2
[wco-dl] - Download for Sword Art Online-S01E25-English Dubbed 2 did not complete, please try again.

I spent ages going through the code could not work out why it was failing, then went to issues and could see people were trying other stuff so I tried SAO 2 and it worked perfectly, so not sure why it's failing on a specific page after much testing it's the only one I can find that has that problem.

I've noticed to have that problem as well with some other Anime's and Cartoon's. I'm not sure if the traffic is being stopped or if the website realizes that it's a Scrapper bot and kills the connection.
I have been fighting with this since I've made this little script haha. My other script (MyAnimeDownloader) has the same problem.

https://github.com/EpicUnknown/wco-dl/blob/8f90d0d558e80f74dbea8feb2c3e68db6718cf56/Lifter.py#L242
I've encountered the same issue, I don't know what the real issue is but the backup url works for me.

I'm not sure i used an online downloader and found that the backup URL was working but the primary was not, perhaps instead of just erroring and stopping on the failure to download it fails then tries the backup URL to see if that works?
Just a possible fix

Sounds good. I'll make it try the backup URL when I get home tonight and hopefully push out a fix.
Thank you for using it and providing feedback! It's greatly appreciated!

This issue is finally resolved and I uploaded a new EXE with the working version.


Translate /docs/tutorials/configuration/_index.md in Japanese.

This is a Feature Request

What would you like to be added

/docs/tutorials/configuration/_index.md Japanese translation.
Why is this needed
No /docs/tutorials/configuration/_index.md in Japanese.
Comments

Copy from en content and Update content/en/docs/tutorials/configuration/_index.md.

/language ja

/assign

/close