Your Ruby engine is jruby, but your Gemfile specified jruby

Given the following Gemfile:
ruby '2.3.0', engine: :jruby, engine_version: '<IP_ADDRESS>'

When I run bundle using the correct JRuby version, I get an unexpected error message:

Your Ruby engine is jruby, but your Gemfile specified jruby

I already found out that the error happens because I declared engine as :jruby instead of 'jruby'.  Still, I see two possible improvements in Bundler: 1) change the error message to be clear about strings vs. symbols, and/or 2) enable the use of symbols when declaring the engine, to make it consistent with for example declaring gem groups or platforms.

That's pretty confusing, thanks for reporting this! We should definitely call to_s on those arguments.

We should definitely call to_s on those arguments.

I'll work on this!


Cast not working.

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Browser and Operating System:
Google Cast, Nest Hub

Description of problem:
Card not available on Google Nest Hub "Custom element doesn't exist: big-slider-card."

Javascript errors shown in the web inspector (if applicable):
No access to web inspector.

I tried but I can't really test on the nest hub since I don't have one :(


Comments and suggestions

Hi!
As I told you I took a look to the theme, so I will leave here some comments/suggestions:

You can fix the audio of the sidebar adapting the code you used to add the Avatar (using  .File.Dir). I wanted to make a PR but for some reason HUGO generates me a wrong URL (I'm getting back slashes when using .File.Dir: /about\sidebar\audio.m4a). I think this happens on Windows but I'm not 100% sure (On my local preview I can't even see the avatar image). I tried using replace to change the slashes but It didn't work for me.
As the theme is designed for academics I think it would be great to have a section for papers (something very simple, like papers ordered by year for instance).
I don't  know if this is on your roadmap, but adding multilanguage support is always welcome.

The theme is great! Everything I tested seems to work as expected.
Best regards,
José Carlos (a.k.a R CODER)

Thank you! This is helpful feedback. I was just thinking about the publications today, as I'm porting my own over, definitely needs a custom layout: https://apero--apreshill.netlify.app/publication/
And thanks for the audio tip- I'll try to fix on my end 🔌
Multilanguage support would be awesome, but not sure when I'll be able to tackle that.


envision-unwrapped: 0-unstable-2024-09-09 -> 0-unstable-2024-09-19

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.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.

Result of nixpkgs-review pr 343089 run on x86_64-linux 1

2 packages built:

envision
envision-unwrapped

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1965

Superseded by https://github.com/NixOS/nixpkgs/pull/343089


Unresolved reference: AppUpdater

I work in kotlin and when i try to use the pacakge:
val appUpdater = AppUpdater(this)
appUpdater.start()

I have an Unresolved reference: AppUpdater and i don't find the import !
I have
repositories {
    maven {
        url "https://jitpack.io"
    }
}

and
implementation 'com.github.javiersantos:AppUpdater:2.7'

in my gradle.
I probably miss something obvious but i can't find what !

The sync was not working i fixed it and it works


Spi reader dont work for me :(

I wrote a test example for your library: https://github.com/pronvis/drawer-robot/blob/master/crates/companion/src/bin/hx711_spi_read.rs
And it reads absolutely noise:
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #26: DYMH-06 data: -221.92485
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #31: DYMH-06 data: -0.000035274
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #35: DYMH-06 data: -221.92485
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #40: DYMH-06 data: -0.000035274
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #44: DYMH-06 data: 184.93732
└─ hx711_spi_read::app::hx711_read @ src/bin/hx711_spi_read.rs:135
DEBUG #49: DYMH-06 data: 258.91226

but non-spi reader that is used here: https://github.com/pronvis/drawer-robot/blob/master/crates/companion/src/bin/hx711_read.rs
works fine. What could be wrong?
All the difference in pin connections is:
with spi:
PB13 <-> SCK
PB14 <-> DT

with non-spi:
PA7 <-> SCK
PA6 <-> DT

Hmm. Strange. I need to look into this...


[Bug] Wrong homepage was added to the InlineBallutes netkan file

I don't know who added it, but the homepage as listed is incorrect.
It should be:
https://forum.kerbalspaceprogram.com/index.php?/topic/173733-inline-ballutes-update-thread/

That was from #6750, fixed in dc139bb6dd489af3221e2915e5f62b17f45217f0

Thank you


CRUD on One-to-One relation

VERSION INFO
Sails version: 0.12.11
Node version: v6.3.1
NPM version: 3.10.3
Operating system: OS EI Capitan
ISSUE
Hi team,
I hope you guys have a great day. I stuck when I worked with Sails and I cant find a way to solve that. Searched through the internet in many hours but can't got the answer. I hope you can give me some advices.
I'm about designing API for my project. Suppose I have 2 model: User and Profile.

A User has one a Profile
A Profile belongs to a User

In the controller I leave as default. Don't add/remove line of codes.
In the model. I define as follow:
User
module.exports = {
  attributes: {
    email: {
      type: 'string'
    }
    profile: {
      model: 'profile'
    }
  }
}

Profile
module.exports = {
 attributes: {
   name: {
     type: 'string'
   }
   user: {
     model: 'user'
   }
 }
}

Is it possible if I want to do CRUD Profile with the route
/user/:user_id/profile
For example. When I wanna get Profile of given User by url
GET /user/58aab787067e9517fe001038/profile
I got an error
Specified record (58aab787067e9517fe001038) is missing relation "profile"
I have no idea how to resolve the relation. Can you help me a hand?
Thank you,
Vinh

ok, fixed!

ok, fixed!

Hi @hoangzinh,
I wasn't able to recreate this issue with the models you provided.  The error you're seeing indicates that the profile attribute of the given user isn't set at all.  I would double-check the way you're setting profile for the user.


Header already sent

Hey,
You have an output block over the php init stuff: https://github.com/lamclennan/pdnsmanager/blob/master/index.php#L17
which leads to Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/index.php:17) in /var/www/html/lib/headers.php on line 19
Chears

I am seeing this error as well through nginx.  It is making it unusable.  Any idea when this will be fixed?

I am not able to reproduce this issue. Also a warning should not render the software unusable.

I would be more than happy to set you up with access to a dev site on my server so that you can tinker with it if you like.  It does work.  Although it is filling my logs and I am unable to assign domains to users so only administrators can use the software.  Not sure if that is connected.
FYI: So far your version has been the best GUI I have seen yet.  (:  Looking forward to getting it 100% usable.

Nevermind about the users domain access.  I just worked that part out.

I tried to reproduce this on a Ubuntu Xenial (with PHP 5.6.31-1~ubuntu16.04.1+deb.sury.org+1), but I don't get any errors.
@TheFatherMind If you are still experiencing those problems and want to show them to me on your systems, please mail me at<EMAIL_ADDRESS>PGP key with the fingerprint C56B20A600EE30EE618FA6025D3C9B15D1BEE8BC is available at the usual key servers.

Have you the php.ini settings:
error_reporting = E_ALL
display_errors = On
?

The error is totally clear:
https://github.com/loewexy/pdnsmanager/blob/master/index.php starts with <!DOCTYPE html> which leads to flush the output buffer. Starting with the first flush you are note able to modify the headers.
The Line in https://github.com/loewexy/pdnsmanager/blob/master/lib/headers.php#L19 should be removed. If we need this header we have to adjust the apache / nginx config to deliver it.

@psi-4ward Thanks for beating me to see what is obvious - while I was just wondering why I can't reproduce it. I just pushed 39dd3f86c68e26b7acfb6ccf929a37ede748550a to the master, where the headers are set before the HTML block starts.
While this should fix the issue, do you have any idea why I can't reproduce that? My error_reporting is set at E_ALL and display_errors is on, so I wonder why I don't get this error?

Hmm also check your php error log and apache error log

@psi-4ward Did that, too. I'm using nginx + php-fpm with the nginx error log level set to info, doesn't give me anything, neither does the php-fpm error log (which I have set to my production values, that is workers logging to it, too).
This is really strange, I'll try to find out more about this.

@mauricemeyer I have eMailed you login information to your own area so you can see this issue and play around.  My mail server is going through a DNS switch over and it got stuck in the queue.  I will eMail you from a different account in the mean time.


[html] No Convenient Constructor for MetaElement

Dart version: Dart SDK version: 2.13.4 (stable) (Wed Jun 23 13:08:41 2021 +0200) on "macos_x64"
Machine: M1 Mac
I've been working on an AngularDart package that adds <meta> tags to the HTML document. However, I found there's no way to construct a fleshed MetaElement directly. MetaElement itself only has an empty constructor. If I want to add a MetaElement with attributes, I have to do something similar to this:
var meta = Element.tag('meta')
  ..attributes = {
    // Blah, blah, blah...
    'content': content,
  };
document.head.append(meta);

May I ask if there is a reason for not having a convenient constructor for MetaElement, like Element.meta(String name, ...), especially given that (at least in my opinion) <meta> is very common?
Thank you!

Aren't all elements from dart:html like this?


Captive portal: honour 'noconcurrentlogins'

Probably got lost during the captive portal rewrite. @jstrebel noted this also enforced MAC locking on m0n0wall.

@AdSchellevis in light of your recent commits, can we just ditch this?

@fichtner yes, lets ditch this one, the new captive portal has this one already in it.


ffmpeg.setProgress(progress) returning NaN

On Chrome 89, the method returns NaN until it returns 1 upon conversion completion. Both when using the setProgress method and passing p => console.log(p) to the options.progress.

Hi @jeromewu, anyone else experiencing this issue?

I ran into the same issue and I don't think it can be solved using the progress hook that is provided. I ended up solving it externally in two different ways depending on what command was run.

Progress = (CurrentFrame / TotalFramesInOutput) * 100
CurrentFrame can be parsed from the FFMPEG output and TotalFramesInOutput is FPS * DurationOfClip

Progress = (FFMPEGTimeStampInSeconds / OutputDurationInSeconds) * 100
FFMPEGTimeStampInSeconds can be parsed from FFMPEG output and can be converted into seconds using the following function:

const timestampToSeconds = (ts)=> {     const [h, m, s] = ts.split(":");     return parseFloat(h) * 60 * 60 + parseFloat(m) * 60 + parseFloat(s);   }

I'm facing this issue too. @yaakov123 how did you get the currentFrame and totalFrames?

@BrunoQuaresma what is your ffmpeg command ?
This code can help you I guess: https://github.com/ffmpegwasm/ffmpeg.wasm/blob/master/src/createFFmpeg.js#L50
Look at the function prog: prog({ duration: d, ratio });, prog({ ratio, time: t }); or prog({ ratio: 1 });
const ffmpeg = createFFmpeg({
                        log: true,
			progress: ({ ratio, time, duration }) => {
				console.log('ratio', ratio, 'time', time, 'duration', duration);
			},
		});

Getting Same issue :ffmpeg.setProgress(progress) returning NaN
i have used ffmpeg in React.js Project


do_after needs a refactor for prediction

Also thought about making it unique based on: user entity, target entity, target component, which might help with prediction + cleanliness.
Also probably combine DoAfterEventArgs with DoAfter as well for simplicity.

Duplicate of #3088


Error: Invalid CSS after "...			{width: 100%"

Rails 5.1.1

When Sassc used

    sass (3.5.1)
      sass-listen (~> 4.0.0)
    sass-listen (4.0.0)
      rb-fsevent (~> 0.9, >= 0.9.4)
      rb-inotify (~> 0.9, >= 0.9.7)
    sass-rails (5.0.6)
      railties (>= 4.0.0, < 6)
      sass (~> 3.1)
      sprockets (>= 2.8, < 4.0)
      sprockets-rails (>= 2.0, < 4.0)
      tilt (>= 1.1, < 3)
    sassc (1.11.4)
      bundler
      ffi (~> 1.9.6)
      sass (>= 3.3.0)
    sassc-rails (1.3.0)
      railties (>= 4.0.0)
      sass
      sassc (~> 1.9)

When Sass-Rails used
No error whatsoever
P.S. I am using https://github.com/davydotcom/retina_tag

The issue was !IMPORTANT, its gone when I changed it to !important.

I can confirm this also happening for me when compiling
@asset = Sprockets::Railtie.build_environment(Rails.application).find_asset(@tmp_asset_name)

options = {
  syntax: :scss,
  cache: false,
  read_cache: false,
  style: Rails.env.production? ? :compressed : :nested
}

@compressed_css =<EMAIL_ADDRESS>options).render

SassC::SyntaxError: Error: Invalid CSS after "...in-bottom:30px}": expected ")", was ""
        on line 12 of stdin

All css final style declaration is missing the ending semi-colon ; after the style:
.clinics-and-map{margin-bottom: 30px}
Which should be
.clinics-and-map{margin-bottom: 30px;}
When using Sass::Engine.new it renders as expected and doesn't error.

Is there any new information on this issue!?

I just ran into this, I believe this is could be an issue with https://github.com/sass/sassc-ruby , not sassc-rails


Refactor authn and ratelimit features to reuse buildXdsCluster

Description:
The ratelimit feature creates an xds cluster using https://github.com/envoyproxy/gateway/blob/4a04915e3f8b95ac54baeed6d42503324fb7af9b/internal/xds/translator/ratelimit.go#L267 and the authn feature creates an xds cluster using https://github.com/envoyproxy/gateway/blob/4a04915e3f8b95ac54baeed6d42503324fb7af9b/internal/xds/translator/authentication.go#L413
These features should instead be using the existing method to build an xds cluster defined here
https://github.com/envoyproxy/gateway/blob/4a04915e3f8b95ac54baeed6d42503324fb7af9b/internal/xds/translator/cluster.go#L22 so its easier to manage the intended cluster field values
[optional Relevant Links:]

Any extra documentation required to understand the issue.

I'm going to work on this. Could you assign it to me?


Update scala-library, scala-reflect to 2.13.7

Updates

org.scala-lang:scala-library
org.scala-lang:scala-reflect

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

Files still referring to the old version number
The following files still refer to the old version number (2.12.15).
You might want to review and update them manually.
daffodil-japi/build.sbt

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang" } ]

labels: library-update, early-semver-minor, semver-spec-minor, old-version-remains

Unfortunately, much more than a version bump is needed to get 2.13.x working with Daffodil.
See DAFFODIL-2152 and stalled work in progress PR #246
Closing.


Remove PRs with merge conflicts from the merge queue

If, when updating PRs before merge, a merge conflict is detected, add a comment about it and remove the reviewed/wait-merge label from the PR.

Could we mention the PR author?

It works!


US72513: Update colours of specific Daylight svgs that were exported …

…with the wrong greys.

@dlockhart not sure if this interferes with your icon-set work. Should I be cautious about including this in BSI?

Don't worry about it for now, I'm still not quite ready yet. All the icons are moving into new directories anyway so we can figure out how to migrate later.


test add some log in udf function when thrown exception

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 46.14 seconds
stream load tsv:          549 seconds loaded<PHONE_NUMBER>9 Bytes, about 129 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.1 seconds inserted 10000000 Rows, about 343K ops/s
storage size:<PHONE_NUMBER>7 Bytes


pdm: add non-default groups as well

I think for the integration test to use multiple groups we'd need something to consume those groups like a top-level package or a dev shell. Alternatively we could just add unit tests similar to tests/nix-unit/test_groups testing if the pdm module populates stuff correctly. Maybe that's cleaner after all.

Oh and you can build the current pdm example via:
nix build .#checks.x86_64-linux.example-repo-flake-pdm -L
and it is also built via nix flake check


wait: implement waitid()

waitid() has a number of additional features that waitpid() is missing:

WNOWAIT is only accepted for waitid() on Linux (and possibly other platforms)
Support for waiting on PID file descriptors on Linux

For now support is added for all platforms with waitid() that have proper siginfo_t support in libc. NetBSD support is currently a work in progress [1].
Tests for the signal/exit code are currently skipped on MIPS platforms due to multiple bugs in qemu-user in the translation of siginfo_t (one fixed in January [2], one currently under review [3]).
[1] rust-lang/libc#2476
[2] https://lists.nongnu.org/archive/html/qemu-devel/2021-01/msg04810.html
[3] https://lists.nongnu.org/archive/html/qemu-devel/2021-10/msg05433.html

@NeoRaider can you rebase this? It isn't conflicting on GitHub, but local testing shows the changelog will merge into the 0.23.1 patch's section, rather than the current one.

Rebased and updated commit message to reflect the current status of the mentioned qemu-user issue.

Hmm, seems I'll have to update the test code as well.

bors r+

Another PR went in first and modified the changelog in the same spot. Can you rebase?

bors r+


Ginkgo CI: messy behavior when test name conventions not followed

If the Describe of a test is not prefixed with K8s or Runtime, the Ginkgo framework does not handle it gracefully. This is due to the fact that the prefix in the Describe determines what infrastructure is launched (VMs, installation of Cilium, etc.).
For example, if you change the Describe of the K8sPolicies test to KafkaK8sPolicyTest:
• Failure in Spec Setup (BeforeEach) [1.963 seconds]
KafkaK8sPolicyTest
/Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:282
  PolicyEnforcement Changes [BeforeEach]
  /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:170

  Cannot connect to vmName  'k8s1-1.7'

  /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:41
------------------------------
•! Panic in Spec Setup (BeforeEach) [0.001 seconds]
KafkaK8sPolicyTest
/Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:282
  Policies [BeforeEach]
  /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:281

  Test Panicked
  runtime error: invalid memory address or nil pointer dereference
  /usr/local/go/src/runtime/panic.go:489

  Full Stack Trace
      /usr/local/go/src/runtime/panic.go:489 +0x2cf
  github.com/cilium/cilium/test/helpers.(*Kubectl).Apply(0x0, 0x0, 0x0, 0xc4206673f0)
      /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/helpers/kubectl.go:285 +0x91
  github.com/cilium/cilium/test/k8sT.glob..func1.2()
      /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/k8sT/KafkaPolicies.go:60 +0x70
  github.com/cilium/cilium/vendor/github.com/onsi/ginkgo/internal/leafnodes.(*runner).runSync(0xc42027bbc0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
      /Users/manalibhutiyani/go/src/github.com/cilium/cilium/test/test_suite_test.go:82 +0x1bd
  testing.tRunner(0xc420318000, 0x19f3ff0)
      /usr/local/go/src/testing/testing.go:657 +0x96
  created by testing.(*T).Run
      /usr/local/go/src/testing/testing.go:697 +0x2ca

We should enact some requirements for the test name being used so that we can gracefully handle these errors and not confuse new users of the tests with cryptic output like above.

@ianvernon any thoughts on next steps for this, or can we close it?

Changes will arrive in 2-3 weeks related to this one  ;-)

Close via this commit:
https://github.com/cilium/cilium/commit/37ea1fbe3929ad173ee0e0d95309632ad1639fa7


json.NewDecoder Decode not return err when input invalid

What version of Go are you using (go version)?

$ go version
go version go1.14.2 darwin/amd64

What did you do?

package main

import (
	"bytes"
	"encoding/json"
	"fmt"
)

func main() {
	p := "404 not found"
	var m interface{}
	dec := json.NewDecoder(bytes.NewBuffer([]byte(p)))
	dec.UseNumber()
	err := dec.Decode(&m)
        // the err is nil
	if err != nil {
		fmt.Println(err)
	}
        // 404
	fmt.Println(m)

	err = json.Unmarshal([]byte(p), &m)
        // the err is not nil
	if err != nil {
		fmt.Println(err)
	}
        // 404
	fmt.Println(m)
}

What did you expect to see?
both m is 404, but the first err is nil, and the second err is "invalid character 'n' after top-level value". Maybe both should reutrn error?

see https://github.com/golang/go/issues/36225

see https://github.com/golang/go/issues/36225

thanks

Closing as a dup.


[now dev] WIP Bundle canary builders for Now CLI canary

Closes #2641.
I'm still adding unit tests for the "filter" function since the logic is not very straightforward and there's many edge cases.

Codecov Report

Merging #2661 into canary will decrease coverage by 0.04%.
The diff coverage is 42.85%.

@@            Coverage Diff            @@
##           canary   #2661      +/-   ##
=========================================
- Coverage    7.92%   7.88%   -0.05%
=========================================
  Files         259     259
  Lines       10444   10414      -30
  Branches     1321    1322       +1
=========================================
- Hits          828     821       -7
+ Misses       9563    9538      -25
- Partials       53      55       +2

Impacted Files
Coverage Δ

src/util/dev/builder-cache.ts
33.16% <42.85%> (-0.35%)
:arrow_down:

src/util/dev/yarn-installer.ts
37.28% <0%> (-0.81%)
:arrow_down:

src/util/dev/server.ts
11.52% <0%> (-0.25%)
:arrow_down:

src/util/dev/builder.ts
12.43% <0%> (+0.26%)
:arrow_up:

src/util/get-files.ts
87.07% <0%> (+0.81%)
:arrow_up:

src/util/output/create-output.ts
29.54% <0%> (+2.46%)
:arrow_up:

src/util/dev/router.ts
80.3% <0%> (+4.58%)
:arrow_up:

src/util/metrics.ts
68.18% <0%> (+6.64%)
:arrow_up:

src/util/prefer-v2-deployment.ts
70.96% <0%> (+8.11%)
: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 257f5f2...e1e576d. Read the comment docs.

@AndyBitz I'd rather not, as there's not really a "clean" way to accomplish that without including two tarballs (one for stable and one for canary) and would make the logic more complicated.
Users can still use stable builders, the installPackages() function blocks to ensure correctness before booting up the now dev server.


[Question]: GatewayTimeout Error on sending messages to bot, after second deployment to Azure?

Hi @nwhitmont, @JasonSowers
App ID: f64f508b-b993-42cd-8add-bef12d2adc14
SDK Platform: Node.js
BOT Builder Version: 3.10.1
Description: I have published my bot some days back and its working fine and approved by MS team. Today I made some changes in my program and deployed a build to Azure but now it is giving me above error. Everything is working fine on local. Do I need to republish Bot for the above problem?
As my Bot has lived and lot's of users are using it so I can't leave it down. I have to rollback the changes and deployed the earlier build to make it work. It's working now with the previous build but not working with the latest build. Let me know if you require any other thing.
This is my bot's endpoint- http://chatterbotquo.azurewebsites.net/

Hi @ersachit - When I tested your bot just now, it was responding normally in the webchat. I did not see any problems with this bot. Are you still having issues?

Hi @nwhitmont as mentioned above, my bot was not working when I deployed the new build to Azure. But as the bot is live and in use by many people so I have to revert that build (The one which is working fine).
Please check now, I have deployed the build which is not working and Bot is not responding now and let me know what is the problem with this build.

Hi @ersachit - When I tested your bot just now it showed the following errors on the WebChat channel:
12/4/2017, 3:14:28 PM | There was an error sending this message to your bot: HTTP status code InternalServerError
-- | --
12/4/2017, 3:14:28 PM | There was an error sending this message to your bot: HTTP status code InternalServerError
12/4/2017, 3:14:28 PM | There was an error sending this message to your bot: HTTP status code InternalServerError

There is a problem with your bot code that is preventing it from responding to messages.  Maybe something to do with error handling that is crashing your bot?
Without seeing the code, it's difficult to pinpoint the issue.  Post your complete bot code here or in a shared GitHub repo if you'd like us to investigate further.

Hey, @nwhitmont thanks for the response. We have a private repository which is linked to our azure app. Though I am sharing another GitHub repo link here which is a clone of the original repository. Please check and let me know if it works for you. Here is the link to the GitHub repo.
https://github.com/sachitqt/training-feedback-test

Hey @nwhitmont , any updates on this?

reopen if you're still having issues

Hey @nwhitmont, the issue is not resolved. You were asking for the GitHub URL and I shared that in above comment but the issue is closed by you. Is there anything I need to share so that you can look into it as the same code is running on my local or other servers(Heroku) but when I deployed to Azure it is giving me an error. Please reopen this issue. Here is the link to the GitHub repository-
https://github.com/sachitqt/training-feedback-test

Hey @nwhitmont, can you please check the code that I shared in above comment that do I need to make any changes in code as there are some changes being done in the official documentation regarding state changes?

Hey @nwhitmont , @JasonSowers, I am waiting for your reply as I am still getting issue.


[5.3]custom the date format of the Many-to-Many relation's pivot table

Are you sure this is suppose to target 5.3? Laravel 5.3 is no longer supported.

ok...this pull request can be closed.


Insecure middleware over HTTP.

While adding a password and having Force HTTPS for password unchecked it didn't work out as I hoped to, I'm still having the following error:

Slim Application Error
The application could not run because of the following error:
Details
Type: RuntimeException
Code: 0
Message: Insecure use of middleware over HTTP denied by configuration.
File: /var/www/twitchautomator/vendor/tuupola/slim-basic-auth/src/HttpBasicAuthentication.php
Line: 148

i'm not sure what else it could be really, secure is set to false with the config

I couldn't find the reason for it to not work, it seems that it totally ignores that false flag for some reason.
What I did was I edited nginx.conf file to add a new SSL port (8081), added the private key/cert associated with the SSL I have and reloaded nginx. APP URL is now using the http port (8080) and I use the HTTPs 8081, everything seems to be working.

i would recommend using https whenever you can, especially since letsencrypt issues free certs

i would recommend using https whenever you can, especially since letsencrypt issues free certs

Indeed and its what I'm doing, but I did find it weird that the secure to false did not work for whatever reason.

@KurtzPT in my case, this was caused by "ProxyPreserveHost On" in apache reverse proxy. Probably because internaly its on http. After turning it off is error gone.

@MrBrax with proper reverse proxy with https now installed still having issues with this. Maybe the following can help?
https://github.com/tuupola/slim-basic-auth#allow-https-termination-and-forwarding
I have to set the Force HTTPS for password off to add a password since internally its using http only

@MrBrax it seems the secure flag is not being properly set to false.
I changed this line on public.php:
"secure" => TwitchConfig::cfg('password_secure', true) == true,
to
"secure" => false,
and now it asks for password without any problem.

Is it set to false in the config page? Can't really return true otherwise

Is it set to false in the config page? Can't really return true otherwise

Yes, I even went to config.json and its set to false:

Very strange indeed, this is probably why i should learn how to set up proper tests

I'm not a PHP guy but this seems to be working:

If I have password_secure set as false, it asks me for password (correct behavior) if it's set to true it gives me the insecure error (also "correct" behavior since internally with reverse proxy I'm using http)

true should be the default, only forceable to off. so it's inverted?

i updated the composer packages, it might have been a bug in slim/psr7

i updated the composer packages, it might have been a bug in slim/psr7

Tried out now, it's giving the same issue.

Maybe it's just intentional then, it's supposed to be set inverse?

It's not inverse, unless I'm not understanding what you mean be inverse here. If password_secure is set to false on the configs, secure is set to false with my solution.
Without my solution is always true, doesn't matter what the password_secure is set to. Feels like it's always using the default secure value which I assume is true.

I think i found the issue now, removed the duplicate empty value check for the cfg function

It's fixed! Finally I can close this almost 2 year issue ! 🥳

amazing

Thanks again for the help on both issues I raised since yesterday @MrBrax :)

good stuff, hopefully it won't break anything

i think i found the first issue, if you had timezone set it seems to have reset the eventsub secret somehow

My timezone is set to the default one and my eventsub_secret is still set (not sure if it reseted or not)

alright good, might have been some earlier testing error then

alright good, might have been some earlier testing error then
if the hooks don't fire when streams happen this is the cause

I set some channels and its already recording one when it came live so everything seems fine for now.


ci: fix ci failure(#58)

fix: #58
Currently some of the tests relied on the test bucket status. Because the test
files were created manually several months ago. We need to decouple
this to make our tests more robust.
Create test files before the tests session begin.

Thank you, @karajan1001 ! 🙏


Dynamic require of "util/" is not supported when using experimentalOptimizer

Describe the bug
Before
All tests were passing.
Added experimental optimizer
{
   experimentalOptimizer: { enabled: true },
},

After
Error in 58 tests:

It looks like the problem is related to the usage of  jest-extended matchers.
Reproduction
This is the branch where we face the issue:
https://github.com/balancer-labs/frontend-v2/tree/bump-vitest
System Info
System:
    OS: macOS 12.6.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 139.28 MB / 32.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.1 - ~/.nvm/versions/node/v16.19.1/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.19.3 - ~/.nvm/versions/node/v16.19.1/bin/npm
  Browsers:
    Chrome: 110.0.5481.177
    Safari: 16.1
  npmPackages:
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    @vitest/coverage-c8: ^0.25.3 => 0.25.8
    vite: ^4.1.4 => 4.1.4
    vitest: ^0.29.2 => 0.29.2

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Another package that seemed to produce this error for me was msw (https://github.com/mswjs/msw)

I noticed that @vitest/coverage-c8 was still at ^0.25.3 vs. ^0.29.2. What happens if you update that package to ^0.29.2 as well? In the past, I experienced this same issue when these were mismatched.

Vitest 0.31.4 changes how experimentalOptimizer works. Now Vitest only optimizes dependencies inside experimentalOptimizer.include (which can be populated by plugins), so it should not optimize actual Node.js packages unless specified.


None of the betas working on iPhone 6, iOS 10.1

I read the issue posting guidelines.
I know this isn't the spot for support, but I have exhausted support options. Have stumped just about every genius in the /r/jailbreak discord.
I can't seem to get any of the betas to work on my iPhone 6 on iOS 10.1, no matter if I'm using my Windows desktop, my MacBook, any of the betas, or with any workaround (do not disturb, turning find my iPhone off, etc.) I'm able to get the Yalu102 app on my home screen, trust it, and hit "Go". After a few seconds, my phone crashes (the screen gets glitchy then turns off, followed by the apple logo) instead of re-springing.
Was told to post an issue here, since this seems like a bigger issue than something that could be solved through troubleshooting. If anyone needs more data from me, please ask. Also, if someone wants to use me to test just in case nobody has an iPhone 6 on iOS 10.1, that's totally okay. Just hit me up on the /r/jailbreak discord, @kashuba

can you build and run from source with Xcode and provide the output from the device console?

I'll sure try. Would you mind explaining the "Include the IOKit headers, and add them to your search path." step of the setup process? I'm not an Obj-C/Xcode dev, so I'm not quite sure how to go about that let alone what it means.

#435 I made that post about the iPad mini 4 / iPad Air 2 because those devices have similar issues, please try that method on Beta 7 and let me know how it goes, thanks.

@KashubaK try this it should find IOKit for you

@mwoolweaver I'm getting tons of "Header 'libkern/arm/OSByteOrder.h' not found" errors.
@MEXX1811 Trying that now.

I'm dumb, had the 10.1 beta. Sorry for wasting all of your guys' time.


Make async resolve functions coroutines

Asyncio may be better for certain proxy types (slow I/O, many simultaneous I/O requests), and the await pattern has some code readability benefits over threads.
Need to discuss this idea in more depth before moving forward with it.

Closing this because asyncio does not fit our usage characteristics. Typically, we don't have that many asynchronous resolves occurring in a single process (rather, we more often have many separate processes on different machines resolving) so threading is okay.


Make configuration screen beautiful

What
Make changes according to design file
https://www.figma.com/file/72qJ03EOQExf12g5JTdWjQ/ACS-UI?node-id=1374%3A389

Why

How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

For speaker icon, instead of a microphone icon I would expect something that represents output instead of input e.g. maybe an icon like:

(best to check with AlexP)

Should this also be applied to the composite as well?


Updated the vscode whitespace settings.

We need these settings everywhere.  Grabbed from polymer-analyzer.

@rictic suddenly type errors showing up in travis so I added some ! to a test.

https://travis-ci.org/Polymer/polymer-bundler/builds/220755209 for reference.


Link on place checklist page showing HTML

eg https://www.inaturalist.org/check_lists/63740-City-of-Cape-Town-Check-List

Same as: https://github.com/inaturalist/inaturalist/issues/2134


vanished players

I Am Setting up featherboard but i dont want vanished players to come up how do i do that

Hi, could you explain better the problem?


Base64 encoded images saved as a data url slows down parsing a lot.

I have a payload which freeze a tab of browser for a looong time.
**Heavy payload**\n\n![color-palette.png](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAABGkAAAEMCAYAAAB3FevlAAAAAX...)\n\n*... the end of it*

As you can see this is a png image saved as base 64 encoded data url. The size of the image is 75kb, so I had to trim it to post the issue here. But the total size of payload seems 98.5kB.
Here is how performance tab looks like.

Seems it spend a loot of processing time to some regexp.
I just wonder is there a way to improve it somehow?
My env specs, just in case.

<EMAIL_ADDRESS>Google Chrome 119.0.6045.159 (arm64)
MacOS Sonoma 14.1.1
MacBook Pro 13-inch, M1, 2020

P.S. Is there a benchmarks that may show me how big payload the library can process in an adequate time frame?

There's likely some optimization potential here, haven't spent much time on images/links in a while

Hey @quantizor can you provide an update? I'm supper happy with the library, however for me this a dealbreaker 😢


[Core] provide interface for content conversion

Must handle conversion from Map, POJO to String, List and vise versa.
Will be provided by DataFormat?

added ContentConverter interface, enough for the comming release


Document query string variables for key without value becoming value without key

It is quite common to use URL query string keys without values for boolean flags, e.g. ?foo rather than ?foo=true. This page does not document how those are handled.
It seems that the returned NameValueCollection contains these key-only query variables as no-key/null-key values.
That also means multiple flags are returned as a comma separated list of values/query-var-keys as a string - which is suboptimal for handling such query variables, when more than one can occur.

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

ID: cb6855ee-43a7-3a40-bef2-8b455dd4443c
Version Independent ID: 5b1274ec-c193-769c-986e-2c95852477d0
Content: HttpRequest.QueryString Property (System.Web)
Content Source: xml/System.Web/HttpRequest.xml
Product: dotnet-api
GitHub Login: @dotnet-bot
Microsoft Alias: dotnetcontent

Thanks for submitting your feedback,, @ite-klass. We've added it to the backlog until we can gather more information.
//cc @davidsh, do you know who owns System.Web?

//cc @davidsh, do you know who owns System.Web?

@Tratcher Can you please help here?

@shirhatti


Feature Request: Like/Dislike entire band / album

[x] I have checked that there are no issues with similar or the same content

OS: Windows 10
GPMDP Version: 4.6.0
I would find it very useful to dislike songs in bulk for the purpose of skipping them in generated stations. How it might work: Click on an artist, go to all songs, menu button to like/dislike all songs. Or that could exist on the main artist page, but it's a little more awkward there.
Without doing it in bulk, it's pretty tedious, as you can see here: https://s3-us-west-2.amazonaws.com/elasticbeanstalk-us-west-2-868470985522/ShareX/2018/06/2018-06-28_21-42-01.mp4
Plus if you miss the dislike button it starts playing the song and interrupts your station! Ugh! That's easy when disliking 100's of songs at once.
I've disliked about a dozen bands by clicking dislike one-by-one. I would love the ability to just right-click on a band or use the menu button and select "Dislike artist". And perhaps just by album, though disliking one album is not a big deal. I usually dislike an entire artist if I don't like them, I don't think I've ever disliked just one album.
This might be a pretty niche feature though. And I hope that Google Play Music adds the feature itself some day. But until then, I thought I would leave another feature request for the awesome desktop player!
If you choose not to add it, no big deal either.
Thanks!!

I started to tinker with a way to do this, but there really isn't a worthwhile way to add this into the UI, and make it functional. If someone were to manage to add this I'm sure we'd consider a PR. Thanks for the request.


Limit failing listener to a configured MaxAttempts

Description
Currently the RabbitMQ container configured by the RabbitListener does not respect the configured MaxAttempts value. Adding the required PollyRetry and callback as requested by the configuration.
Fixes #1164
Quality checklist

[x] Your code complies with our Coding Style.
[x] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[x] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

I will backport to 3.x once approved.

/azp run  cleanup-code


wireguard: Add support for managed K8s

This adds support for Wireguard on Cilium installations without a per-node pod CIDR, such as managed Kubernetes.
See the commit message for the implementation details.
I have tested this on AKS (with #15533 applied). Still need to find a away to experiment with EKS and GCP as they do not have recent enough Kernel versions, but none of the changes in this PR are cloud-vendor specific.
Ref #15462

test-net-next

Marking this ready for review. It passed the connectivity check on AKS with Azure IPAM:
$ k get pods -o wide
NAME                                                     READY   STATUS    RESTARTS   AGE     IP            NODE                                NOMINATED NODE   READINESS GATES
echo-a-57cbbd9b8b-s9nc4                                  1/1     Running   0          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000000   <none>           <none>
echo-b-6db5fc8ff8-7zvrm                                  1/1     Running   0          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000000   <none>           <none>
echo-b-host-76d89978c-mmkjs                              1/1     Running   3          9m46s   <IP_ADDRESS>    aks-nodepool1-14262743-vmss000000   <none>           <none>
host-to-b-multi-node-clusterip-fd6868749-5kjk8           1/1     Running   1          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000002   <none>           <none>
host-to-b-multi-node-headless-54fbc4659f-6vwwz           1/1     Running   1          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000001   <none>           <none>
pod-to-a-648fd74787-2wqnn                                1/1     Running   0          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000002   <none>           <none>
pod-to-a-allowed-cnp-7776c879f-wzk7r                     1/1     Running   0          9m46s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000000   <none>           <none>
pod-to-a-denied-cnp-b5ff897c7-gdfp8                      1/1     Running   0          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000001   <none>           <none>
pod-to-b-intra-node-nodeport-6546644d59-zpzzb            1/1     Running   1          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000000   <none>           <none>
pod-to-b-multi-node-clusterip-7d54c74c5f-s4ckd           1/1     Running   1          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000002   <none>           <none>
pod-to-b-multi-node-headless-76db68d547-nsb6n            1/1     Running   1          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000001   <none>           <none>
pod-to-b-multi-node-nodeport-7496df84d7-vmff9            1/1     Running   1          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000002   <none>           <none>
pod-to-external-1111-6d4f9d9645-xxgxc                    1/1     Running   0          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000001   <none>           <none>
pod-to-external-fqdn-allow-google-cnp-5bc496897c-tt7wq   1/1     Running   0          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000000   <none>           <none>
wg-6d66cbb578-7wmjs                                      1/1     Running   0          9m45s   <IP_ADDRESS>   aks-nodepool1-14262743-vmss000002   <none>           <none>
$ k exec -ti wg-6d66cbb578-7wmjs -- wg
interface: cilium_wg0
  public key: iKazjpbBEME0D5MRtoKIsNF24sBR8iE/hw/hzbo28Go=
  private key: (hidden)
  listening port: 51871

peer: PCZxQyDn6Y9aZU8zE0uOs/giVErVnMd180nFFtmAB1w=
  endpoint: <IP_ADDRESS>:51871
  allowed ips: <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32
  latest handshake: 21 seconds ago
  transfer: 565.35 KiB received, 1.92 MiB sent

peer: +BDCkJuqM6cxxsRYXdp6WXzvYaPKX4y3zSojzevcHFY=
  endpoint: <IP_ADDRESS>:51871
  allowed ips: <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32, <IP_ADDRESS>/32
  latest handshake: 1 minute, 8 seconds ago
  transfer: 210.60 KiB received, 1.88 MiB sent

test-net-next

Rebased on top of #15565 to avoid conflicts.

test-net-next

Also, this PR has the title: "add support for managed k8s", in all of these environments a kvstore is never used. Thus, we could safely index CiliumEndpoints in the k8s watchers stores by node IP addresses. This would allow us to remove the function on LookupByHostRLocked and perform the lookup directly in the up to date state from the CiliumEndpoints store.

A subgoal of this PR is to remove the dependency on Pod CIDRs. Currently, the Wireguard datapath uses the IPCache BPF map to decide if a packet needs to be sent via Wireguard or not. This is why we chose IPCache here, because it uses the same mechanism as the datapath:
https://github.com/cilium/cilium/blob/aef55b138472d6ae4c3729af0db168c12c8b1957/bpf/bpf_lxc.c#L613-L629
I don't think we can get the health IPs from CEPs, which are also sent via Wireguard and therefore need to be part of AllowedIPs. I am also not sure if CiliumEndpoints will give us the IPCache representation we would see in ClusterMesh with apiserver. Therefore I don't think CiliumEndpoints are the way to go here, but I'm not super familiar with the interactions between CiliumEndpoints and the IPCache to be honest.

@aanm Thanks for the review! I believe I have addressed most of your feedback (and added a unit test which tests the described update orderings)

@gandro you can test on EKS with Bottlerocket (the new Amazon OS that uses Rust and has all sorts of cool features, including a very recent kernel).
All you really need to do is add amiFamily: Bottlerocket in nodegroup spec. Ping me on slack if anything.


service rate limit overrided by consumer

Summary
i have the api working as expected with kong, i have multiple users with a dedicated rate limiting each one,
in order to protect the api i've created a service rate limit to add an onverall limit
Steps To Reproduce

create a consumer A and add a rate limit with combination of route.id and consumer.id with 4 req/sec
curl -k -X POST https://host/plugins/
--data "name=rate-limiting"
--data "config.second=4"
--data "config.policy=local"
--data "consumer.id=03581935-829d-483e-9c28-8d22dd405e30"
--data "route.id=8d2a24aa-636d-43ee-b0aa-b0fd1d3643fd"

create a consumer B and add a rate limit with combination of route.id and consumer.id with 8 req/sec
curl -k -X POST https://host/plugins/
--data "name=rate-limiting"
--data "config.second=8"
--data "config.policy=local"
--data "consumer.id=3d45a73d-4024-4313-b356-43a14e3ea702"
--data "route.id=8d2a24aa-636d-43ee-b0aa-b0fd1d3643fd"

create on the service that host the route.id a rate limit of 10 req/sec
curl -k -X POST https://host/plugins
--data "name=rate-limiting"
--data "config.second=10"
--data "config.policy=cluster"
--data "service.id=53d35e73-b285-4eb2-ad24-853d82563ca4"
--data "config.limit_by=service"

if i run a siege with the limits of A and B i'm able to go over 10 req/sec

Additional Details & Logs

Kong version (2.1.4)

discovered the priority
Precedence
A plugin will always be run once and only once per request. But the configuration with which it will run depends on the entities it has been configured for.
Plugins can be configured for various entities, combination of entities, or even globally. This is useful, for example, when you wish to configure a plugin a certain way for most requests, but make authenticated requests behave slightly differently.
Therefore, there exists an order of precedence for running a plugin when it has been applied to different entities with different configurations. The rule of thumb is: the more specific a plugin is with regards to how many entities it has been configured on, the higher its priority.
The complete order of precedence when a plugin has been configured multiple times is:
Plugins configured on a combination of: a Route, a Service, and a Consumer. (Consumer means the request must be authenticated).
Plugins configured on a combination of a Route and a Consumer. (Consumer means the request must be authenticated).
Plugins configured on a combination of a Service and a Consumer. (Consumer means the request must be authenticated).
Plugins configured on a combination of a Route and a Service.
Plugins configured on a Consumer. (Consumer means the request must be authenticated).
Plugins configured on a Route.
Plugins configured on a Service.
Plugins configured to run globally.
Example: if the rate-limiting plugin is applied twice (with different configurations): for a Service (Plugin config A), and for a Consumer (Plugin config B), then requests authenticating this Consumer will run Plugin config B and ignore A. However, requests that do not authenticate this Consumer will fallback to running Plugin config A. Note that if config B is disabled (its enabled flag is set to false), config A will apply to requests that would have otherwise matched config B.

Thanks for the information. Were you able to find a workaround to make the general limit and the specific limits work concurrently. Meaning if, consumer B exceeds 8 requests per second or the service exceeds 10 per second, the request is not forwarded?

@cucearda I'm having the same problem, and what i will try is to add the service level rate limits to every single consumer, so that it will get moved up in priority to Service and Consumer whenever any consumer hits that service, and get applied instead of the now lower prio Consumer only rate limit of that consumer


Does not work with Suspense

Expected this to work well with Suspense (similar to a Resource) but doesn't seem to working at them moment. Any plans on doing this?

Unfortunately not at the moment since I don't have much time to spend on solid-urql. I'm open to PR's though :)


cannot find librealsense and openni2

Hi man, I run cmake, got the error cannot find librealsense and openni2 even they are installed already,
are there any problem with the/cmake/FindRealSense.cmake ?

It is trying to find them in /usr/local. Simply set variables REALSENSE_ROOT and OPENNI2_ROOT.

Hello, Have you solved this problem? as I also run into this problem, but I have changed the directory of realsense and openni2, but it still failed, I don't know whether it is because the REALSENSE_ROOT and OPENNI2_ROOT directory I have changed is wrong. can you give me a hand where is the REALSENSE_ROOT and OPENNI2_ROOT .
Thank you very much!


Feature Request - zero duration tween

It feels really strange when you set the duration of something to 0 milliseconds and it suddenly defaults to 1 second. I don't understand that thing with tweens and it becomes uncomfortable sometimes.
If I want to animate something, but in some cases I want it to happen instantly (when initializing it or respawning it for example), I have to deliberately check whether I want it to happen at once and just change it's value, or use a tween.
It's logical to have a default value of 1000 milliseconds when the input is a negative number (since you can't do something for negative time because real world physics and stuff). But why that behavior with 0 milliseconds input?
In my opinion it's going to be a lot more comfortable and logical if this:
game.add.tween(prop).to({x:10}, 0, Phaser.Easing.Cubic.InOut, true);
simply does this:
prop.x = 10;
and then calls the onComplete() functions, etc.

Thank you for taking the time to open this issue. However, official support for Phaser 2 has now ended as we focus on preparing Phaser 3 for beta release. In a bid to keep the project tidy, and avoid confusion, we are closing all v2 related issues.
This does not mean your issue won't be looked-at. In November 2016 the Phaser CE (Community Edition) project began. The aim of Phaser CE was to allow the community to continue v2 development. Since then it has gained significant traction, with many updates and releases.
If you are still interested in having your issue investigated we strongly recommend testing the latest Phaser CE release. And only if the problem persists, opening an issue on the Phaser CE repo.


Custom tracker store not found

Rasa version: 1.1.3
Python version: 3.6.8
Operating system (windows, osx, ...): Docker on OSX
Issue:
I and another user cannot get custom tracker store working as reported on the forum here. My custom tracker has been working fine in prior versions of Rasa but not under 1.0.
Error (including full traceback):
WARNING  rasa.core.tracker_store  - Store type 'f.Ff' not found. Using InMemoryTrackerStore instead

Command or request that led to error:
asa run --enable-api --model /app/data/models --endpoints /app/data/endpoints_local.yml --credentials /app/data/credentials.yml --port 5005 --log-file /app/data/logs/rasa_core.log --debug

Content of configuration file (endpoints.yml) (if relevant):
action_endpoint:
  url: "http://action:5055/webhook"
tracker_store:
    store_type: trackerArango.ArangoTrackerStore
    db: kyc-chatbot
    url: http://arango:8529
nlu:
  url: http://nlu:5000

Content of configuration file (config.yml) (if relevant):
language: "en"

pipeline: supervised_embeddings
policies:
  - name: KerasPolicy
    epochs: 200
    max_history: 1
  - name: MemoizationPolicy
    max_history: 1
  - name: FallbackPolicy
    nlu_threshold: 0.59
  - name: FormPolicy

Thanks for raising this issue, @samwill get back to you about it soon.

Not sure who you meant to tag there tobias :D
@rgstephens is it possible this issue is related to your problem? https://github.com/RasaHQ/rasa/issues/3748

Updated it :-D

I reviewed #3748. Maybe it's possible that PYTHONPATH now needs to be set in for 1.0 that was not a requirement before?  I will give this a try.

yeah your assumption is correct there, we're looking into avoiding having to set the PYTHONPATH.
Do you have an init.py in your directory?

No, it's worked before with no __init__.py.  Tried adding one and it made no difference.
We have two of us that can't get this to work.  @thom in the post had a nice short example. Can we get a 3rd person to try this out real quick?
tracker_store:
  store_type: f.Ff
  url: localhost

f.py:
from rasa.core.tracker_store import TrackerStore

class Ff(TrackerStore):

def __init__(self, url, domain):
    print("OUI")

@akelad could you please remove the more-information-needed label.  No other information is required to duplicate this problem.

@rgstephens that label is for when we're waiting for an update :) But in any case, yeah we're looking into this issue in the other issue. So i'll close this one and reference it from the other one

@akled why is this being folded into a python path issue?  I tested setting the path and it does not address this problem.
From my perspective, this is a critical issue.  Is there any sense of priority with this issue?


Probable memory leak in PHP extension 1.37.0

What version of gRPC and what language are you using?
gRPP version 1.37.0 for PHP 7.2.24
What operating system (Linux, Windows,...) and version?
Ubuntu 18.04
uname:
Linux $hostname 5.4.0-72-generic #80~18.04.1-Ubuntu SMP Mon Apr 12 23:26:25 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
What runtime / compiler are you using (e.g. python version or version of gcc)
PHP 7.2.24-0ubuntu<IP_ADDRESS> (cli) (built: Oct  7 2020 15:24:25) ( NTS )
gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Also tested on Ubuntu 20.04:
PHP 7.4.3 (cli) (built: Oct  6 2020 15:47:56) ( NTS )
gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
What did you do?
When querying GCP's Cloud Datastore using the gRPC PECL extension, it will return (in our case) 29k entities containing XML snippets, totaling for ~125 MB of XML data. We got error messages stating out-of-memory errors in our PHP application. Given the two files described below, I query GCP's Datastore. This example does depend on a preconfigured and pre-filled GCP Project though.
composer.json:
{
    "require": {
        "php": "^7.2",
        "ext-grpc": "*",
        "ext-protobuf": "*",
        "google/cloud-datastore": "^1.12"
    }
}

test.php:
<?php
require __DIR__ . '/vendor/autoload.php';
$keyFile = '...';
$kind = '...';
$parentId = '...';
ini_set('memory_limit', 250 * 1024 * 1024);

/**
 * @property string $xml_detail
 */
class TestModel extends Google\Cloud\Datastore\Entity{}

function dumpMemoryUsage(int $i): void {
    $n1 = memory_get_usage(true);
    $n2 = memory_get_peak_usage(true);
    printf(
        "<!-- Item #: %d, usage: %d MB, peak usage: %d MB -->\n",
        $i, intdiv($n1, 1024 ** 2), intdiv($n2, 1024 ** 2)
    );
}

function testMemoryLeak(): void {
    global $keyFile, $kind, $parentId;
    $client = new Google\Cloud\Datastore\DatastoreClient(['keyFilePath' => $keyFile]);
    $parentKey = $client->key($kind, $parentId);
    $query = $client->query()->kind($kind)->hasAncestor($parentKey);
    $entityIterator = $client->runQuery($query, ['className' => TestModel::class]);

    $i = 0;
    // Iterates over ~29k entities
    foreach ($entityIterator as $entity) {
        /** @var TestModel $entity */
        $i++;
        // xml_detail contains ~ 4600 bytes avg
//        echo $entity->xml_detail;
    }
    dumpMemoryUsage($i);
}
testMemoryLeak();

Script has been run using CLI.
What did you expect to see?
I expected to see reasonably memory usage.
What did you see instead?
Memory usage is very high, considering PHP output buffering in pretty small (even disabled for CLI) and no entities are being held in memory by this code. Using grpc pecl extension, memory usages is up to 204 MB:
<!-- Item #: 28702, usage: 204 MB, peak usage: 204 MB -->
Anything else we should know about your project / environment?

We use GCP Datastore using a hierarchy (parent/child entities). I did not try to query a kind without hierarchy.
GCP also uses PHP extension protobuf. It did not matter whether the protobuf extension was enabled or not.
I did not yet try to run with GRPC_VERBOSITY or GRPC_TRACE configured, as I'm not that knowledgeable in grpc
I did try to use the composer package grpc/grpc instead of the PHP extension. When using this, memory usage stays at a reasonably low level:
<!-- Item #: 28702, usage: 14 MB, peak usage: 18 MB -->
I did search for existing issues, finding issues describing memory leaks for other programming languages. Not sure if they are related.

I was quite sure protobuf did not matter... However, I did some tests again, and it seems to confirm that protobuf is indeed the culprit.
Memory usage (MB)

gRPC:

Protobuf:
Disabled
1.37.0

Disabled
16
18

3.15.8
16
214

3.16.0
16
214

However, I kept also track of required time to retrieve and process all XML data. It seems enabling gRPC increases the required time, especially when protobuf is disabled. In that case, the CPU utilization of the PHP process also reaches 100%. This was a bit of a surprise to me.
Avg time (seconds).
Average time required on at least 3 runs using the script mentioned it the issue description:

gRPC:

Protobuf:
Disabled
1.37.0

Disabled
37.09
121.65

3.15.8
37.39
49.86

3.16.0
36.02
43.95

Should I report this in a new issue?

Yes it's expected - the protobuf extension is supposed to provide a much better performance boost. It's less efficient to use the protobuf composer package.
(Btw, the 2 tables above were slightly mis-aligned - it's a bit hard to read)

The fixes in https://github.com/protocolbuffers/protobuf/pull/8614 make the protobuf C extension Valgrind-clean (except for a few edge cases involving exceptions that I was not able to figure out).
This should be released in the next week or two as a patch release of 3.17.x.

@stanley-cheung

Yes it's expected - the protobuf extension is supposed to provide a much better performance boost.

I do indeed expect less performance when disabling the protobuf extension. I did not expect an increased performance when I disable both. This should be a bit easier to read:

gRPC & protobuf enabled: 43.95s (for protobuf version 3.16.0)
only gRPC enabled: 121.65s
both disabled: 37.09s

(time required to fetch ~125 MB of XML data)


Diagrams

full addition of Cytoscape and Jupyter for graphing, layout, narration of code.

I think I've resolved the conflicts in poetry.lock.  We'll see.  ;)


feat: optionally require JWT token to access api, logs requests

If JWT_SECRET env param is specified, all routes will require a JWT token to access.
Any requests made will be logged in a JSON format for AWS cloudwatch.

I'm thinking, is there a way the actual length of the token can be reduced. I am worried about limitations in URL length


MySQL backups fail due to tablespaces

Bug Report
Describe the bug
MySQL 5.7.31 / 8.0.21 introduced a breaking change to require the PROCESS privilege to perform mysqldumps that include tablespaces. A combination of the --no-tablespaces flag and setting --column-statistics=0 can be added to circumvent the need for this PROCESS privilege, however there is no interface to django-dbbackup to allow this to happen, preventing users who do not have access to the required privilege from being able to perform database backups.
To Reproduce

Run a MySQL 8.0.21+ server
Restore some data into it via dbrestore
Attempt to dump the data back out via dbbackup, with a user account lacking the PROCESS privilege

Expected behavior
dbbackup should successfully complete without throwing any of the following errors:

mysqldump: Error: 'Access denied; you need (at least one of) the PROCESS privilege(s) for this operation' when trying to dump tablespaces
mysqldump: Couldn't execute ...: Unknown table 'COLUMN_STATISTICS' in information_schema (1109)

Versions
Django-dbbackup

pypi: 3.3.0

External tools

Python: 3.8.5
Django: 3.2.6
OS: Linux

Issue was ultimately resolved by simply utilising the DUMP_SUFFIX connector parameter, by adding the following to my Django settings:
DBBACKUP_CONNECTORS = {
    'default': {
        'DUMP_SUFFIX': '--no-tablespaces --column-statistics=0',
    }
}

fwiw, you'll see a similar issue if you use mariadb-server with mysql-client. This is easily fixed by replacing mysql-client and libmysqlclient-dev with mariadb-client and libmariadbclient-dev (or your distro equivalent packages)


[ALLUXIO-1832] Update Flink Profile and Documentation

https://alluxio.atlassian.net/browse/ALLUXIO-1832

Merged build finished. Test PASSed.

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

+1 LGTM


Default configuration path is unaligned with rpm and deb installation methods

Example:
ADD pipeline/default.conf /usr/share/logstash/pipeline/logstash.conf
In the rpm and deb, we put settings files in /etc/logstash/ and pipeline (path.config) in /etc/logstash/conf.d
I recommend we align on the way the rpm/deb do this.

See #5 for a longer discussion, but here's my synopsis:
Right now, I'm using this directory structure to adhere to the Logstash Directory Layout docs. Since we're building from the .tar.gz distribution (but see #14), we can put pipeline config anywhere without violating the docs. We can't, however, move the settings files the same way, since their location is specified for the tar.gz distribution (and in a different location to the deb/rpm versions). Thus, we can't fully satisfy the deb/rpm specification without violating the .tar.gz specification.
Maybe that doesn't matter, though. Maybe we just need a "Docker specification". I agree that having pipeline config in /etc/logstash/conf.d may be good for the "principle of least surprise" when people are coming from the deb/rpm world to the Docker image. So, I could see us making this change, but I'd want to be careful with both the Docker-specific documentation and the directory layout documentation to make sure we are not contradicting ourselves and really confusing our users.


Add helperGetApiVersionFromEnv() to get apiVersion from KUBERNETES_EX…

Got this error message when run 'kubectl get no' with this build locally.

With this commit the build goes well with v1beta1, and I was trying to test a scenario using v1 version but it seems even the most recent aks version (1.24.6) is still using v1beta1. So I did not find a way to test v1 cases with the code.

Generally looks good to me. but can you please add unit tests?

please remove the extra generated mock files...

you also need to rebase


Git Homework Oleksandr Bratushchyk-Khoma

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
@mentions of the person or team responsible for reviewing proposed changes (At least 2 people)

Checklist

[ ] I can confirm that my changes are working as intended

uoft-dsi-c3-homework-20240425
uoft-dsi-c3-homework-20240425

A more comprehensive screenshot of your terminal is needed; ie how did you create directory, markdown file etc. missing task 3, creating a branch and saving empty text files there

Should I take screenshots of each step?
I took screenshots where it was mentioned in the tasks

A more comprehensive screenshot of your terminal is needed; ie how did you create directory, markdown file etc. missing task 3, creating a branch and saving empty text files there

@juliagallucci updated. New screenshots are here


Enhancements to reflection operator

There is a request for enhancements to the reflection operator to better support GrizIt. The are two distinct but related features:1) Reflect about an arbitrary plane defined by a point and a normal vector. This is currently possible to accomplish using a user created matrix and the transform operator, however, this requires additional plots for every reflection.2) Two modes for reflection" cumulative and noncumulative. Cumulative is the way VisIt currently does reflections. Noncumulative would only reflect the original mesh. I attached an image that visually demonstrates the disctinction.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 2691
Status: Pending
Project: VisIt
Tracker: Feature
Priority: High
Subject: Enhancements to reflection operator
Assigned to: Matt Larsen
Category: -
Target version: 3.0
Author: Matt Larsen
Start: 10/18/2016
Due date:
% Done: 0%
Estimated time:
Created: 10/18/2016 05:20 pm
Updated: 10/17/2017 07:49 pm
Likelihood:
Severity:
Found in version: 2.12.3
Impact: 3 - Medium
Expected Use: 3 - Occasional
OS: All
Support Group: GrizIt
Description:
There is a request for enhancements to the reflection operator to better support GrizIt. The are two distinct but related features:1) Reflect about an arbitrary plane defined by a point and a normal vector. This is currently possible to accomplish using a user created matrix and the transform operator, however, this requires additional plots for every reflection.2) Two modes for reflection" cumulative and noncumulative. Cumulative is the way VisIt currently does reflections. Noncumulative would only reflect the original mesh. I attached an image that visually demonstrates the disctinction.
Comments:
The reflect operator should allow multiple planes and it should always be non-cumulative. Makes sense to support multiple reflect planes in the same operator as well as either do a 'reflect' operation or a 'copy' operation (which would NOT use a plane)

These features are already supported.


Fix supported Linux OS table to show SLES 12 minor versions are not supported

From the table showing supported Linux OS, it looks like SLES 12 minor versions are also supported.
Like - "Red Hat Enterprise Linux Server 7" means RHEL 7 and 7+, and they are supported.
Similarly, "SUSE Linux Enterprise Server 12" would mean that SLES 12 and 12+ are supported but that's not the case.
As per product group, SLES 12 minor versions are not supported yet, and we get the following error.
Extension Message:
        Unsupported operating system: sles 12.5
        Extension Error: 2023/07/24 15:19:53 [Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.27.2] Install,failed,51,Unsupported operating system: sles 12.5

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

ID: bd3dca2f-629d-36e9-f0f0-8c7e64cc04ab
Version Independent ID: f40ee991-6cb8-1eee-9a35-ebc5833d7c7f
Content: Azure Monitor Agent overview - Azure Monitor
Content Source: articles/azure-monitor/agents/agents-overview.md
Service: azure-monitor
Sub-service: agents
GitHub Login: @guywi-ms
Microsoft Alias: guywild

@sachinpanwar
Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@MonikaReddy-MSFT your PR has about 10k commits, not sure if it is correct or specific to this issue.
Can you please check and share a PR specific to this issue and share an ETA as well?

@sachinpanwar - I have updated the document to add a note to reflect that for SLES12, minor versions are not supported yet.
It will be live once its merged.  If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


chore: add dependabot assignees

Thank you for contributing to golib!
Please add a summary of your change
chore: add dependabot assignees
Does your change fix a particular issue?
Fixes #(issue)
Check list:

[ ] Mark if documentation changes are required.
[ ] Mark if tests were added or updated to cover the changes.

Codecov Report

Merging #42 (e458794) into main (c349818) will not change coverage.
Report is 1 commits behind head on main.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main      #42   +/-   ##
=======================================
  Coverage   71.72%   71.72%
=======================================
  Files          22       22
  Lines         976      976
=======================================
  Hits          700      700
  Misses        200      200
  Partials       76       76

Flag
Coverage Δ

unittests
71.72% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update UI

Update UI to show product_id instead of ID for search result because ID doesn't have meaning
Update UI to include query and empty

Codecov Report

Merging #97 (2c01076) into main (36b98ac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #97   +/-   ##
=======================================
  Coverage   96.91%   96.91%
=======================================
  Files           7        7
  Lines         421      421
=======================================
  Hits          408      408
  Misses         13       13

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


Sensu fixes

@brettdh I believe I have addressed all the issues. ATM it is not easy to use docker to create a sensu client for full integration testing. The unit tests have been updated to use a raw TCP socket and the code has been tested against a real Sensu client and is behaving correctly.
Note in addition to the sensu changes a small change was added to the alert node to count triggered alerts.

Nice, thanks. I look forward to pulling this in.


[Bug] memory crash

mage run or docker-compose up --build
mac 13.3.1  M2 chip
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x39 pc=0x100ce5690]
goroutine 87 [running]:
github.com/docker/buildx/builder.(*Builder).Validate(0x101ee58a0?)
github.com/docker/buildx@v0.10.4/builder/builder.go:111 +0x20
github.com/docker/buildx/builder.New({0x101ee58a0?, 0x14000170500}, {0x0, 0x0, 0x140003d0ab0?})
github.com/docker/buildx@v0.10.4/builder/builder.go:101 +0x290
github.com/docker/compose/v2/pkg/compose.(*composeService).doBuildBuildkit(0x140002ec840, {0x101ed4d80, 0x14000660190}, 0x0?, {0x1016872b3, 0x4})
github.com/docker/compose/v2/pkg/compose/build_buildkit.go:36 +0x68
github.com/docker/compose/v2/pkg/compose.(*composeService).build.func1({0x101ed4d80, 0x14000660190}, {0x14000427390, 0x3})
github.com/docker/compose/v2/pkg/compose/build.go:112 +0x5b4
github.com/docker/compose/v2/pkg/compose.(*graphTraversal).run.func1()
github.com/docker/compose/v2/pkg/compose/dependencies.go:127 +0x5c

I believe this may be specific to the M2 chip, since I've run the same command on my M1 with no issue.
Are you using Docker Desktop? https://tutorials.tinkink.net/en/mac/how-to-use-docker-on-m1-mac.html

yes docker desktop

also whats the recommended server to use? AWS
Amazon 2
Ubuntu
?

gui docker no longer exists either in compose yaml
gui:
build:
context: ../
dockerfile: build/Dockerfile-gui

@jdutchak you might need to try docker-compose stop &&docker-compose up --build --remove-orphans again since the error seems related to docker-compose itself
the GUI is being removed here - https://github.com/TBD54566975/ssi-service/pull/450
as for where to run - we're planning on supporting all major clouds. have tested on AWS internally

are the swagger docs being removed too?

more accurately I should say the streamlit gui is deprecated in favor of https://github.com/TBD54566975/ssi-admin-ui
we have yet to integrate that into our docker-compose here https://github.com/TBD54566975/ssi-service/issues/454
swagger was moved to be served from the service itself, so need for a special binary. docs could be better perhaps. you can view it as of https://github.com/TBD54566975/ssi-service/commit/817610d1ff91ea1061b7328c752df273a91e757e by sending a request to /swagger


ENH: allow SlidingEstimator and gat to get **fit_params at fit

such that one can do e.g.
clf = SlidingEstimator(LinearModel())
clf.fit(X, y, sample_weights=np.random.rand(len(X))

Use directly sample_weights and avoid kwargs

Use directly sample_weights and avoid kwargs

will break if estimator is a pipeline.
This is sklearn API

I think Travis' errors are unrelated (but perhaps should be fixed? I don't understand them)

They are sklearn errors that should be fixed. The 3.6 runs use sklearn 0.19 whereas the 2.7 runs use 0.18.1 so it's probably a scikit-learn API problem. I can try to look this week unless @agramfort beats me to it

indeed  LGTM then.
+1 for MRG if travis failure is unrelated

Thanks @kingjr


Kafka output writer formatter

I've updated the KafkaOutputWriter to allow override of the JSON format.
You can now write your own class to convert the results into your format.
I've also updated the Producer to use the official KafkaProducer Class.
See the README.md for more information about changes.
PS : Thanks @elludo for his help.

This pull request is now managed with CodeReviewHub. Refresh.

PR #586 contains an interface named ResultSerializer which is similar in purpose to KafkaMessageFormatter

Close as #586  has been merged


Enable custom CA for specified server names

Allow usage of custom Certification Authority for specified host names.

@knative-sandbox/kn-plugin-func-approvers PTAL

This is needed for OpenShift internal registry push.

@zroubalik can you lgtm?


Bugfix: Texture smoothing

only mark texture as dirty when scaleMode differs from previous value
This PR (choose one or more, ✏ delete others)

is a bug fix

Please include a summary in Change Log: Unreleased and thank yourself.
Describe the changes below:
Commit 7ea0dd2 a fix for #432 but marks texture always as dirty. Even if the smoothed value doesn't change at all. This fix now checks if the previous value actually differs to current. If it does, it marks the texture as dirty. This fixes some performance regressions for our framework that the commit introduced.

Can you change to !== ?

@samme
of course. Just applied the change.


Finalise applications without profile picture

We have a finalised applicant without a profile picture which should not have been allowed.
Can someone investgate and fix quickly?

Making the profile picture optional was an explicit request from the Students' Council.
(the reasoning being that this was pointed out as a potential problem while reviewing the Privacy Policy).
This change was made in https://github.com/EotvosCollegium/mars/commit/6496bb3dff590f69bf20ede37a036ca0bfdfbcc0


Pin Nebari dependencies, set k8s version for GKE

Reference Issues or PRs

Fixes #1623
What does this implement/fix?
Put a x in the boxes that apply

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds a feature)
[ ] Breaking change (fix or feature that would cause existing features not to work as expected)
[ ] Documentation Update
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[x] Build related changes
[ ] Other (please describe):

Testing

[ ] Did you test the pull request locally?
[ ] Did you add new tests?

Any other comments?

I also removed environment-dev.yaml, I couldn't find anywhere in the Nebari org (including the integration test repo) it's used.

@iameskild can you run IT on this branch just to make sure its deployable? I don't see any problems with just pinning (I do suppose we pinned with the current versions we were already using in the recent deployments) so this looks good to go


Specify compiler pipeline for futhark-test

For me it would be handy to be able to add -s --flattening to test if flattening actually does work :)

So would this apply to every test being done (type-checking, interpretation, compiled code generation)?

Also, when would this new stage be inserted?  The full pipeline is quite long.  And actually, for futhark-c and friends it is by design not possible to change the pipeline at all...

As long as it works with -t, -i, and --run, I would be happy :)

But where in the pipeline?  Why not just modify the futhark-c pipeline to run this pass in your branch?

These are the constraints: futhark-i, futhark-c, futhark-opencl and others we make in the future do not suppport modification of the compiler pipeline, possibly with the exception of disabling optimisation.  They are intended as concrete demonstrations of the compilation technique and are very rigid in order to avoid some problems with some compiler research (which I will freely rant more about if necessary).  futhark-test must at least in some mode run these programs or else it is not really an integration test.
What we can do: add a new flag to futhark-test that allows one to specify an entire new command to run for a test program.  For example, we can imagine futhark-test --compiler=futhark-flatten, where futhark-flatten is some shell script that calls futhark and gcc as appropriate.  This should be sufficient for testing transformations before they make it into the main pipeline (which is the intended destination of your flattening work), whilst not doing violence on the overall design in the meantime.

Why not a futhark-test [-i|-t|--run] --pipeline="-s --flattening" which simply runs futhark with this specific pipeline?

If you want to actually generate code, -s is only half the story - after that comes sequentialisation, adding allocations, optimising said allocations, and then deciding on a backend.  This is why it is in general not easy to decide when and where to insert an extra pass.  Besides, I really want futhark-test to use the "end-user compilers", at least in its default configuration.  Perhaps a special "custom" test action can be added that uses just futhark and is near-magical in how it deals with the pipeline.


Tree entries table returns too many entries

Even though it's marked as a bug, it's more of a discussion to see if this is a bug or not.
This is the result of the tree_entries table over github.com/git-fixtures/basic:
[[3bf5d30ad4f23cf517676fee232e3bcb8537c1d0 278871477afb195f908155a65b5c651f1cfd02d3 100644 .gitmodules]
[3bf5d30ad4f23cf517676fee232e3bcb8537c1d0 b4f017e8c030d24aef161569b9ade3e55931ba01 100644 README.md]
[8ac3015df16d47179e903d0379b52267359c1499 278871477afb195f908155a65b5c651f1cfd02d3 100644 .gitmodules]
[c4db5d7fc75aa3bef9004122d0cf2a2679935ef8 278871477afb195f908155a65b5c651f1cfd02d3 100644 .gitmodules]
[efe525d0f1372593df812e3f6faa4e05bb91f498 97b013ecd2cc7f572960509f659d8068798d59ca 100644 .gitmodules]
[a39771a7651f97faf5c72e08224d857fc35133db 880cd14280f4b9b6ed3986d6671f907d7cc2a198 100644 example.go]
[5a877e6a906a2743ad6e45d99c1793642aaf8eda 49c6bb89b17060d7b4deacb7b338fcc6ea2352a9 100644 long.json]
[5a877e6a906a2743ad6e45d99c1793642aaf8eda c8f1d8c61f9da76f4cb49fd86322b6e685dba956 100644 short.json]
[586af567d0bb5e771e49bdd9434f5e0fb76d25fa 9a48f23120e880dfbe41f7c9b7b708e9ee62a492 100644 crappy.php]
[cf4aa3b38974fb7d81f367c0830f7d78d65ab86b 9dea2395f5403188298c1dabe8bdafe562c491e3 100644 foo.go]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c 880cd14280f4b9b6ed3986d6671f907d7cc2a198 100644 go/example.go]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c 49c6bb89b17060d7b4deacb7b338fcc6ea2352a9 100644 json/long.json]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c c8f1d8c61f9da76f4cb49fd86322b6e685dba956 100644 json/short.json]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c 9a48f23120e880dfbe41f7c9b7b708e9ee62a492 100644 php/crappy.php]
[a8d315b2b1c615d43042c3a62402b8a54288cf5c 9dea2395f5403188298c1dabe8bdafe562c491e3 100644 vendor/foo.go]
[fb72698cab7617ac416264415f13224dfd7a165e 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[fb72698cab7617ac416264415f13224dfd7a165e d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[fb72698cab7617ac416264415f13224dfd7a165e c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[fb72698cab7617ac416264415f13224dfd7a165e d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[fb72698cab7617ac416264415f13224dfd7a165e 880cd14280f4b9b6ed3986d6671f907d7cc2a198 100644 go/example.go]
[fb72698cab7617ac416264415f13224dfd7a165e 49c6bb89b17060d7b4deacb7b338fcc6ea2352a9 100644 json/long.json]
[fb72698cab7617ac416264415f13224dfd7a165e c8f1d8c61f9da76f4cb49fd86322b6e685dba956 100644 json/short.json]
[fb72698cab7617ac416264415f13224dfd7a165e 9a48f23120e880dfbe41f7c9b7b708e9ee62a492 100644 php/crappy.php]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 7e59600739c96546163833214c36459e324bad0a 100644 README] [dbd3641b371024f44d0e469a9c8f5457b0660de1 d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 880cd14280f4b9b6ed3986d6671f907d7cc2a198 100644 go/example.go]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 49c6bb89b17060d7b4deacb7b338fcc6ea2352a9 100644 json/long.json]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 c8f1d8c61f9da76f4cb49fd86322b6e685dba956 100644 json/short.json]
[dbd3641b371024f44d0e469a9c8f5457b0660de1 9a48f23120e880dfbe41f7c9b7b708e9ee62a492 100644 php/crappy.php]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd 49c6bb89b17060d7b4deacb7b338fcc6ea2352a9 100644 json/long.json]
[4d081c50e250fa32ea8b1313cf8bb7c2ad7627fd c8f1d8c61f9da76f4cb49fd86322b6e685dba956 100644 json/short.json]
[eba74343e2f15d62adedfd8c883ee0262b5c8021 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[eba74343e2f15d62adedfd8c883ee0262b5c8021 d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[eba74343e2f15d62adedfd8c883ee0262b5c8021 c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[eba74343e2f15d62adedfd8c883ee0262b5c8021 d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[c2d30fa8ef288618f65f6eed6e168e0d514886f4 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[c2d30fa8ef288618f65f6eed6e168e0d514886f4 d3ff53e0564a9f87d8e84b6e28e5060e517008aa 100644 CHANGELOG]
[c2d30fa8ef288618f65f6eed6e168e0d514886f4 c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[8dcef98b1d52143e1e2dbc458ffe38f925786bf2 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore]
[8dcef98b1d52143e1e2dbc458ffe38f925786bf2 c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]
[8dcef98b1d52143e1e2dbc458ffe38f925786bf2 d5c0f4ab811897cadf03aec358ae60d21f91c50d 100644 binary.jpg]
[aa9b383c260e1d05fbbf6b30a02914555e20c725 32858aad3c383ed1ff0a0f9bdf231d54a00c9e88 100644 .gitignore] [aa9b383c260e1d05fbbf6b30a02914555e20c725 c192bd6a24ea1ab01d78686e417c8bdc7c3d197f 100644 LICENSE]]

As you can see, there are some "example.go", "crappy.php" and so on that don't exist and never did, because they were added directly in a subdirectory. This may lead to a lot of repeated entries and entries that are not true (there's never been a file called "example.go" in that repo, for example).
Do we want to output this as is?
If we do not, which tree would appear in tree_hash, the main one or the direct parent of that entry?
Background
This happens because we iterate all files in all tree objects in the repo without taking into account that we should only iterate the main tree.
Thoughts @src-d/data-retrieval?

I think this was originally by design, since tree_entries were meant to be joined with trees?
Maybe we want tree_entries_raw for plain git behaviour and tree_entries with a more high-level behaviour such as the one in src-d/engine?

I think the actual behavior is correct. As @jfontan said, If we want to get the data from git as is then the actual output is fine.


Instrumentation fails for strings containing urls

Summary
This is a bug regarding Stryker 4 beta 3.
When instrumenting an object definition with as below:
const object = {
    foo: '',
    bar: 'file://',
};

Stryker throws the following error
12:46:51 (23900) ERROR DryRunExecutor One or more tests resulted in an error:
        SyntaxError: Invalid or unexpected token
{{projectRoot}}\.stryker-tmp\sandbox475018\src\{{sourceFile}}.js:32
  bar: __global_69fa48.__activeMutant__ === 685 ? "" : (__global_69fa48.__coverMutant__(685), 'file:
                                                                                ^^^^^^

SyntaxError: Invalid or unexpected token
    at wrapSafe (internal/modules/cjs/loader.js:1117:16)
    at Module._compile (internal/modules/cjs/loader.js:1165:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)
    at Module.load (internal/modules/cjs/loader.js:1050:32)
    at Function.Module._load (internal/modules/cjs/loader.js:938:14)
    at Module.require (internal/modules/cjs/loader.js:1090:19)
    at require (internal/modules/cjs/helpers.js:75:18)
    at Object.<anonymous> ({{projectRoot}}\.stryker-tmp\sandbox475018\src\{{sourceFile}}.js:40:21)
    at Module._compile (internal/modules/cjs/loader.js:1201:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1221:10)

This only happens with a URL string (including protocol) that is preceded by an empty string. When the second string does not contain *:// this does not happen.
Additional note. It does not matter if the empty string is nested. The following throws the same error:
const object = {
    fizz: {
        buzz: '',
    },
    bar: 'file://',
};

const object = {
    fizz: [
        '',
    ],
    bar: 'file://',
};

Stryker config
module.exports = function(config) {
    config.set({
        // Empty strings in array due to https://github.com/stryker-mutator/stryker/issues/2305
        mutate: [
            'src/**/*.js',
            '!{src,lib}/**/*.+(spec|test).js?(x)',
            '',
            '',
        ],
        packageManager: 'npm',
        reporters: [
            'html',
            'progress',
        ],
        testRunner: 'mocha',
        mochaOptions: {
            spec: [
                './test/**/*.js',
                './src/**/*.test.js',
            ],
        },
        thresholds: {
            high: 80,
            low: 60,
            break: 50,
        },
    });
};

Test runner config
module.exports = {
    spec: [
        'test/**',
    ],
    reporter: 'mocha-multi-reporters',
    'reporter-option': [
        'configFile=.mocha-reporterrc.js'
    ],
    recursive: true,
    exclude: [
        '.git',
        'node_modules',
        'test/**/resources/**',
    ],
    ui: 'BDD-bundle',
    require: [
        'choma',
        'chai/register-expect',
        'mocha-bundle-ui',
        './test/setup.js',
    ],
    'watch-files': [
        'test/**/*',
        'src/**/*',
    ],
};

Stryker environment
    "@stryker-mutator/core": "^4.0.0-beta.3",
    "@stryker-mutator/javascript-mutator": "^3.3.1",
    "@stryker-mutator/mocha-runner": "^4.0.0-beta.3",

    "chai": "^4.2.0",
    "chai-arrays": "^2.0.0",
    "chai-as-promised": "^7.1.1",
    "chai-string": "^1.5.0",
    "choma": "^1.2.1",
    "mocha": "^8.0.1",
    "mocha-bundle-ui": "^3.0.0",
    "mocha-multi-reporters": "^1.1.7",
    "nyc": "^15.1.0",
    "proxyquire": "^2.1.3",
    "sinon": "^9.0.2",
    "sinon-chai": "^3.5.0"

Test runner environment
    "test": "mocha",
    "test:mutation": "stryker run .strykerrc.js",

Your Environment

software
version(s)

node
v14.5.0

npm
6.14.5

Operating System
Windows 10 2004

Add stryker.log
stryker.log

I'll have a look at this issue tomorrow

I can't reproduce this. Running on express crashes with this error:
14:13:35 (26924) ERROR DryRunExecutor One or more tests resulted in an error:
        SyntaxError: Invalid or unexpected token
C:\z\github\stryker-mutator\stryker-2\perf\test\express\.stryker-tmp\sandbox4426232\test\app.router.js:690
      app.get('/file
              ^^^^^^

SyntaxError: Invalid or unexpected token
    at wrapSafe (internal/modules/cjs/loader.js:1072:16)
    at Module._compile (internal/modules/cjs/loader.js:1122:27)

If you then look at the file, (test/app.router.js), you'll see something interesting:
    it('should require a preceding /', function(done){
      var app = express();

      app.get('/file

There the test ends. End of file.
The problem is with the strip-comments dependency. I've created an issue: https://github.com/jonschlinkert/strip-comments/issues/60
Disabling stripping of comments solves it:
  "sandbox": {
    "stripComments": false
  }

We're using strip-comments to remove // @ts-expect-error or // @ts-check from test and production code files. This is needed for typescript compilation to work (we're adding // @ts-nocheck on top of each file, where your own // @ts-expect-error and // @ts-check might interfere with). More info: https://github.com/stryker-mutator/stryker/pull/2365
I was hoping that strip comments would (almost) always be safe to do. But I see it has some unfortunate side effects and now this bug. @brodybits isn't happy with this solution either (#2407).
Any ideas on how to solve this issue better would be much appreciated. I'll open a new discussion issue and closing this one for now.


OS X support

We're hard coding a lot of iOS stuff in here right now, specifically with testing. We should be better about making that part dynamic and let people test OS X apps and frameworks.
This is also going to be important with watchOS/tvOS.

Ran into this last night working on Runes. the scheme selected was the OS X framework, which meant that testing threw all kinds of errors.

I think we should probably be able to use the output from xcodebuild -showBuildSettings here. If we look for SDK_NAME we should be able to get the info we need to pass to the -sdk flag.
❯ xcodebuild -project Runes.xcodeproj -scheme Runes-Mac -showBuildSettings | grep SDK_NAME
    SDK_NAME = macosx10.11
    SDK_NAMES = macosx10.11
❯ xcodebuild -project Runes.xcodeproj -scheme Runes-iOS -showBuildSettings | grep SDK_NAME
    CORRESPONDING_SIMULATOR_SDK_NAME = iphonesimulator9.0
    SDK_NAME = iphoneos9.0
    SDK_NAMES = iphoneos9.0

We can go simpler: If we just look for CORRESPONDING_SIMULATOR_SDK_NAME, we can use the exit code to determine iOS/OS X. Then we can use that to switch between -sdk iphonesimulator and -sdk macosx.
This is a really simple solution, and probably needs to be fleshed out further, but it'd be a nice MVP.


Building deb pkg fails

I'm probably doing something wrong:
$ dpkg-source --before-build .
$ dpkg-buildpackage -us -uc
dpkg-buildpackage: info: source package qubes-video-companion
dpkg-buildpackage: info: source version 1.0.0-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Elliot Killick<EMAIL_ADDRESS>dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
        make -j8 clean
make[1]: Entering directory '/home/user/src/qubes/qubes-video-companion'
make -C doc clean
make[2]: Entering directory '/home/user/src/qubes/qubes-video-companion/doc'
rm -f qubes-video-companion.1.gz
make[2]: Leaving directory '/home/user/src/qubes/qubes-video-companion/doc'
make[1]: Leaving directory '/home/user/src/qubes/qubes-video-companion'
   dh_clean
 dpkg-source -b .
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../qubes-video-companion_1.0.0.orig.tar.{bz2,gz,lzma,xz}
dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 255

Where is the source for qubes-video-companion, if any?

To build a Debian package you must first create at tarball of it one directory up from where the cloned repo itself is located. This is standard procedure for building any Debian package not a bug in this project.
Please look up a guide on how to build Debian packages.

If project seeking for support from community then README and associated documentation for testing should be robust, even if it points to external resources. There are too many assumptions about tester knowledge to attract casual testers.
This small thing stopped me from continue testing this for more then month.

100% agree, I actually intended on creating a script that would install all the necessary development packages and build the package for you. However, I was very busy at the time and then it slipped out of my mind.
I appreciate you taking the time to try and test despite insufficient support from me.


Add guidance materials and communication package

Add video guidance - to Help or homepage?
Add guidance pdf - to Help
Add a link to the communication package file collection - where? About?

#121