[22.05] nixUnstable: switch to the latest release

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

I think we really should backport newer versions into stable NixOS, without switching the defaults.  That way people can use it more easily; even without flakes, e.g. simply nix.package = pkgs.nixVersions.foo;


[Feature][Doc] Publish blog posts on KubeVela website

Is your feature request related to a problem? Please describe.
We will need a Blog tab on KubeVela doc website to publish the tech blogs and release announcement, etc.
Describe the solution you'd like
Maybe a Blog tab here?

/cc @hongchaodeng @sunny0826

@resouer I reserved the tab of the blog /docs/en/blog/, Just remove the comment in /docs/_navbar.md
<!-- - [Blog](/en/blog/README.md) -->

You can add blog md file to /docs/en/blog/

/merge

Unsubscribe
Sent from my iPhone

On Dec 8, 2020, at 6:54 PM, guoxudong<EMAIL_ADDRESS>wrote:

/merge
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Support for class inheritance?

When testing with this file it looks like the value of person.age is zero. Is this a bug, or missing feature?
// The entry file of your WebAssembly module.

import { JSON } from "json-as/assembly";

// @ts-ignore
@json
class Aged {
  age: i32;
}

// @ts-ignore
@json
class Player extends Aged {
  // age: i32;
  firstName: string;
  lastName: string;
}

// const stringified = JSON.stringify<Player>(data);

export function add(json: string, b: i32): i32 {
  const person = JSON.parse<Player>(json);
  return person.age + b + person.firstName.length;
}

This is a missing feature due to it not being implemented in the transform. Parent type data needs to be cast to the Child data and reflected in the child methods.
I'll put this on my todo list.
Thank  you for bringing this up!

Hi @JairusSW , the example you posted doesn't work:
FAILURE TypeError: (intermediate value)(intermediate value)(intermediate value) is not iterable (cannot read property undefined)
    at AsJSONTransform.visitClassDeclaration (node_modules/json-as/transform/lib/index.js:71:47)

Thanks!

It works for me, but it looks like I didn't have an undefined check there.

@mariusa, can you send me some example code?

Hi, it's exactly the code you posted above:
import { wasi_console } from "@assemblyscript/wasi-shim/assembly/wasi_console"
import { u128 } from "as-bignum/assembly"
import {
    JSON
} from "json-as/assembly"

// @ts-ignore
@json
class Vec3 {
    x: f32 = 3.4;
    y: f32 = 1.2;
    z: f32 = 8.3;
}

// @ts-ignore
@json
class Stats extends Vec3 {
    wins: u128
    loss: u128
}

// @ts-ignore
@json
class Player {
    firstName: string
    lastName: string
    lastActive: i32[]
    age: i32
    isVerified: boolean
    stats: Stats
}

const player: Player = {
    firstName: "Emmet",
    lastName: "West",
    lastActive: [8, 27, 2022],
    age: 23,
    isVerified: true,
    stats: {
        wins: u128.fromString("443"),
        loss: u128.fromString("693")
    }
}

const serializedPlayer = JSON.stringify<Player>(player)
wasi_console.log("Serialized Player: " + serializedPlayer)
const deserializedPlayer = JSON.parse<Player>(serializedPlayer)
wasi_console.log("Deserialized Player: " + JSON.stringify(deserializedPlayer))

gives
FAILURE TypeError: (intermediate value)(intermediate value)(intermediate value) is not iterable (cannot read property undefined)
    at AsJSONTransform.visitClassDeclaration (file:///my-project/node_modules/json-as/transform/lib/index.js:71:47)
    at AsJSONTransform._visit (/my-project/node_modules/visitor-as/src/base.ts:269:14)
    at AsJSONTransform._visit (/my-project/node_modules/visitor-as/src/path.ts:13:11)
    at AsJSONTransform.visit (/my-project/node_modules/visitor-as/src/visitor.ts:34:12)
    at TopLevelDecorator.visitDecoratorNode (/my-project/node_modules/visitor-as/src/decorator.ts:39:20)
    at TopLevelDecorator._visit (/my-project/node_modules/visitor-as/src/base.ts:316:14)
    at TopLevelDecorator._visit (/my-project/node_modules/visitor-as/src/path.ts:13:11)
    at TopLevelDecorator.visit (/my-project/node_modules/visitor-as/src/visitor.ts:34:12)
    at <anonymous> (/my-project/node_modules/visitor-as/src/visitor.ts:21:31)
    at Array.map (<anonymous>)

This error is solved in current versions


deprecate TLS 1.0

deprecate use of TLS 1.0 (could almost also deprecate 1.1 at this point)
Thanks for submitting a pull request ! Please provide enough information so that others can review your changes.
For more information, see the CONTRIBUTING guide.
Description
Deprecate use of TLS 1.0 (postfix). Hasn't been updated in years and proved susceptible to POODLE and BEAST attacks in past.
Fixes # (issue)
Postfix currently uses all versions of TLS. Postfix, after implemention, would only use TLS 1.1 and 1.2
Type of change

[x] Performance improvement
[x] Refactoring (a change that neither fixes a bug nor adds a feature)

Status

[x] Ready

Todo List

[x] Implementation

How has this been tested ?
Added to postfix config override and tested by sending/receiving mail with several domains and different smtp servers. Also ran tests on htbridge.com (mymailserver.email:25)

[x] Test A
[x] Test B

Are there any stats on SSL/TLS support for mailservers?
There's good stats out there for HTTPS, but I fear that mailservers are significantly less updated, and this change risks having legitimate emails rejected from domains if that is the case.
In any case, I'm all for disabling it, but some stats on version compatibility would make me more confident.

Looks good to me, TLS 1.0 must be disabled in 2018.
Explicitly listing the protocols to include, rather than protocols to exclude, is supported, but not recommended by postfix developers.
You should use this syntax instead :
smtp_tls_protocols = !SSLv2,!SSLv3,!TLSv1
smtp_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1
smtpd_tls_protocols = !SSLv2,!SSLv3,!TLSv1
smtpd_tls_mandatory_protocols = !SSLv2,!SSLv3,!TLSv1

And for Dovecot :
ssl_protocols = !SSLv3,!TLSv1

I agree with @hardware, it is easy to negate.
What about traefik?
https://docs.traefik.io/configuration/entrypoints/
[entryPoints.http.tls]
  minVersion = "VersionTLS11"

Should do the trick.

I think for web traffic, we can safely use only TLSv1.2+
minVersion = "VersionTLS12"

https://caniuse.com/#feat=tls1-2
And this ciphers suite :
cipherSuites = [
      "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305",
      "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256",
      "TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA",
      "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA"
]

Thanks for the pointers, @hardware and @navossoc. I've corrected edits made to the postfix config and edited the respective dovecot and traefik files.

As a comment, if we're requiring tls1.2 for web traffic, we can remove two of those cipers, and have a bit better theoretical security.
The last two ("TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA" and "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA") aren't even supported within TLS1.2, so might as well remove them, and gain a bit of resilience against potential downgrade attacks, without losing any compatibility.

@1n5aN1aC, where'd you find that 1.2 doesn't use those ciphers? I ran my site (mailserver traefik page) against both ssllabs.com/ssltest and htbridge.com/ssl and both listed the two ciphers under TLS1.2...

The last two ("TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA" and "TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA") aren't even supported within TLS1.2.

This is not true, look at table above. You can check cipher compatibility with https://tls.imirhil.fr/

@reichley @hardware you are both correct.  I had a miss-configuration that was causing the ciphers to only show up under tls1.1 on ssllabs.  I have corrected that and you are indeed correct.
Sorry.

@hardware ECDSA containous/traefik#2940, containous/traefik#3319

I'm having some issues with this update.
Later I can post more details, first I need to collect more data.
Probably I will need to revert this change.

Well, this is just a sample of what I got:
2018-07-17T19:06:55.799756+00:00 mail-nyc3 postfix/smtpd[3217]: connect from 66-220-144-150.mail-mail.facebook.com[<IP_ADDRESS>]
2018-07-17T19:06:56.214877+00:00 mail-nyc3 postfix/smtpd[3217]: SSL_accept error from 66-220-144-150.mail-mail.facebook.com[<IP_ADDRESS>]: -1
2018-07-17T19:06:56.215219+00:00 mail-nyc3 postfix/smtpd[3217]: warning: TLS library problem: error:1417D102:SSL routines:tls_process_client_hello:unsupported protocol:../ssl/statem/statem_srvr.c:974:
2018-07-17T19:06:56.215581+00:00 mail-nyc3 postfix/smtpd[3217]: lost connection after STARTTLS from 66-220-144-150.mail-mail.facebook.com[<IP_ADDRESS>]
2018-07-17T19:06:56.215853+00:00 mail-nyc3 postfix/smtpd[3217]: disconnect from 66-220-144-150.mail-mail.facebook.com[<IP_ADDRESS>] ehlo=1 starttls=0/1 commands=1/2

Here is a list of some domains that could not send me emails, some are spam, but a few are legit.
66-220-144-143.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-144.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-145.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-146.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-147.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-148.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-149.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-144-150.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-135.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-136.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-137.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-138.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-139.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-140.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-141.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-142.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-143.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-144.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-145.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-146.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-147.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-148.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-149.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-150.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-151.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-152.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-153.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-154.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-155.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-156.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-157.mail-mail.facebook.com[<IP_ADDRESS>]
66-220-155-158.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-128.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-129.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-130.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-131.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-132.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-133.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-134.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-135.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-136.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-137.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-138.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-139.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-140.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-141.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-142.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-143.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-144.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-145.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-146.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-147.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-148.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-149.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-150.mail-mail.facebook.com[<IP_ADDRESS>]
69-171-232-151.mail-mail.facebook.com[<IP_ADDRESS>]
a2-smithers2.uhserver.com[<IP_ADDRESS>]
a2-smithers3.uhserver.com[<IP_ADDRESS>]
a2-smithers4.uhserver.com[<IP_ADDRESS>]
a2-smithers5-1.uhserver.com[<IP_ADDRESS>]
a2-smithers5-2.uhserver.com[<IP_ADDRESS>]
a2-socom3-1.uol.com.br[<IP_ADDRESS>]
a2-socom9-2.uol.com.br[<IP_ADDRESS>]
bn162.mta.exacttarget.com[<IP_ADDRESS>]
bv167.mta.exacttarget.com[<IP_ADDRESS>]
cliente3.email.ekonomizador.com.br[<IP_ADDRESS>]
cupom-104.cupomemail.com[<IP_ADDRESS>]
cupom-105.meucupommail.com[<IP_ADDRESS>]
cupom-106.cupomemail.com[<IP_ADDRESS>]
cupom-107.meucupommail.com[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a130.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a140.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a141.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a142.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a153.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a154.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a166.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a167.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a176.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a177.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a178.blackdelist.com.br[<IP_ADDRESS>]
d18bc8bc72e0994d45510bc5199d2a180.blackdelist.com.br[<IP_ADDRESS>]
descontos-105.descontosmail.com[<IP_ADDRESS>]
descontos-114.descontosmail.com[<IP_ADDRESS>]
email-110.emailespecial.net[<IP_ADDRESS>]
ev-131.rp.enviou.net.br[<IP_ADDRESS>]
mail.barreds.com.br[<IP_ADDRESS>]
mail.hdi-gerling.com.br[<IP_ADDRESS>]
mail.hdigerling.com.br[<IP_ADDRESS>]
mail2.hdi.com.br[<IP_ADDRESS>]
mrb99-191-103.lupadedescontos.com.br[<IP_ADDRESS>]
mrb99-191-104.lupadedescontos.com.br[<IP_ADDRESS>]
mrb99-191-105.lupadedescontos.com.br[<IP_ADDRESS>]
mrb99-191-61.lupadedescontos.com.br[<IP_ADDRESS>]
mrb99-191-62.lupadedescontos.com.br[<IP_ADDRESS>]
mta04.smpt.ekonomizador.com.br[<IP_ADDRESS>]
mta1.lmn1.cupomsivo.com.br[<IP_ADDRESS>]
mta2.lmn1.cupomsivo.com.br[<IP_ADDRESS>]
mta4.lmn1.cupomsivo.com.br[<IP_ADDRESS>]
mx65-omc2s139.ascoisa.com.br[<IP_ADDRESS>]
mx65-omc2s140.ascoisa.com.br[<IP_ADDRESS>]
mx65-omc2s141.ascoisa.com.br[<IP_ADDRESS>]
nav4l3.garantaseucupom.com.br[<IP_ADDRESS>]
nav4l4.garantaseucupom.com.br[<IP_ADDRESS>]
nav4l8.garantaseucupom.com.br[<IP_ADDRESS>]
nav4l9.garantaseucupom.com.br[<IP_ADDRESS>]
poup-104.poupcupons.com[<IP_ADDRESS>]
poup-108.poupcupons.com[<IP_ADDRESS>]
poup-114.poupmail.com.br[<IP_ADDRESS>]
roxinol83.valecupom.com[<IP_ADDRESS>]
shop-111.e-mail-shop.com[<IP_ADDRESS>]
smtp2.bradseg.com.br[<IP_ADDRESS>]
smtp21.shopback.com.br[<IP_ADDRESS>]
srvdct204a.dctcomercial.com.br[<IP_ADDRESS>]
srvdct205a.dctcomercial.com.br[<IP_ADDRESS>]
unknown[<IP_ADDRESS>]
vesta.instemaqvendas.com.br[<IP_ADDRESS>]
wnh0.wnhs.com.br[<IP_ADDRESS>]
wnh2.wnhs.com.br[<IP_ADDRESS>]

For now I will not deprecate TLS 1.0.
PS: I don't any data about outbound emails because I didn't apply this change on my mail relay.
PS2: Also got some issues with STARTTLS with PHPMailer, not sure which version now.

I think we should make it customizable with environment variables, like a TLS_LEVEL set to modern by default (TLSv1.1 and TLSv1.2) but also with an intermediate compatibility mode.
environment:
  TLS_LEVEL=intermediate # Enables TLSv1, TLSv1.1 and TLSv1.2

Looks good to me...
Another configuration issue I found:
Windows 7 SP1 + Office 2016 will not work.
You need to enable TLS 1.1 and TLS 1.2 on Windows registry.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client]
"DisabledByDefault"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client]
"DisabledByDefault"=dword:00000000


Misleading documentation of UpdateImage in python lib.

HI, the comment
"""
Updates the pixel values of a specified image region and a specified set of channels.
The image parameter must be laid out in row-major format, i.e. from most to least
significant: [col][row][channel], where the channel axis is optional.
"""
in the update funtion is wrong. Row major ordering is [row][col][channel]

Good catch, thank you! Fixed on master.


[Issue-2682] Reload earning after transaction is done

Related issue:

#2682

🚀 Deployed on https://pr-2683--sw-web-runner.netlify.app


[Concurrency] Allow struct members to have isolation annotations.

The compiler was banning writing global actors or nonisolated on struct stored properties. This change removes those diagnostics.
I believe global actors were banned because it's safe to access a stored property as nonisolated if the property type is Sendable because of value semantics. We should absolutely allow that, but we should only allow it within the module (to preserve the ability for a stored property to evolve into a computed property), we should use the same mechanism that's used for allowing nonisolated access to actor lets that are Sendable, and we should formalize that semantic rule in a Swift evolution proposal.
For nonisolated, I'm not sure why the compiler banned this. nonisolated is fine on a struct stored property that is Sendable, and nonisolated(unsafe) can be used as a granular opt out for making a struct conform to Sendable without resorting to an @unchecked Sendable conformance when the property type is not Sendable.

@swift-ci please smoke test

@swift-ci please smoke test


v1.4.0

Language fixes
Add link to realtime logs
Add check to disable tracking

Closes #347
Closes #344
Closes #341


Need "shiny" ARF Armor, we currently have the 212th variant.

Need "shiny" ARF Armor, we currently have the 212th variant. Clarkey contacted.

Clarkey supplied alt texture set, I need to import and setup. Having issues with armor imports, delaying until thats figured out. I dont wanna frustrate myself.

#23


Can we hide searchMessage?

I feel, it is obvious that the user has to type something when they click dropdown. Can we not show the search message if the value is false?
searchMessage=false
Let me know if I can raise a PR for this?

Also curious about this. Any information?

Super easy. Just use .ember-power-select-option--search-message { display: none; }

Actually, I believe that if you pass searchMessage=false that should already be the behavior: https://github.com/cibernox/ember-power-select/blob/f329318ce514fb8923f035619c140ca37d5e117c/addon/components/power-select.js#L187-L192

Oh interesting! I tried using searchMessage='' and it didn't work. I didn't even try using searchMessage=false because this thread was unresolved and I assumed you couldn't. Thanks!

I didn't even try, but I though that was the default behaviour. Afaik it has been that way for ages.

Maybe I just missed it in the documentation, but I don't think I saw that in there. At any rate now I know, thanks.


Flink Connector mysql CDC sql-client模式下全库扫描，直到capturing到目标表，如果实例下库表比较多，会影响任务启动时效

CREATE TABLE mysql_company_cdc (
id bigint NOT NULL,
company STRING
) WITH (
'connector' = 'mysql-cdc',
'hostname' = 'localhost',
'port' = '3306',
'username' = 'root',
'password' = '123456',
'database-name' = 'inventory',
'table-name' = 'company'
);
select id,UPPER(company) from mysql_company_cdc;
启动任务后会创建一个，会全库扫描，capture目标表，如果实例下库表比较多，会影响任务启动时效

2021-01-07 20:23:11,794 INFO  io.debezium.util.Threads                                     [] - Creating thread debezium-mysqlconnector-mysql_binlog_source-snapshot
2021-01-07 20:23:11,798 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - Starting snapshot for jdbc:mysql://localhost:3306/?useInformationSchema=true&nullCatalogMeansCurrent=false&useSSL=false&useUnicode=true&characterEncoding=UTF-8&characterSetResults=UTF-8&zeroDateTimeBehavior=CONVERT_TO_NULL&connectTimeout=30000 with user 'root' with locking mode 'minimal'
2021-01-07 20:23:11,800 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - Starting snapshot for jdbc:mysql://localhost:3306/?useInformationSchema=true&nullCatalogMeansCurrent=false&useSSL=false&useUnicode=true&characterEncoding=UTF-8&characterSetResults=UTF-8&zeroDateTimeBehavior=CONVERT_TO_NULL&connectTimeout=30000 with user 'root' with locking mode 'minimal'
2021-01-07 20:23:11,803 INFO  org.apache.flink.runtime.state.heap.HeapKeyedStateBackend    [] - Initializing heap keyed state backend with stream factory.
2021-01-07 20:23:11,807 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - Snapshot is using user 'root' with these MySQL grants:
2021-01-07 20:23:11,808 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	GRANT ALL PRIVILEGES ON . TO 'root'@'localhost' WITH GRANT OPTION
2021-01-07 20:23:11,808 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION
2021-01-07 20:23:11,808 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - MySQL server variables related to change data capture:
2021-01-07 20:23:11,809 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - Snapshot is using user 'root' with these MySQL grants:
2021-01-07 20:23:11,810 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	GRANT ALL PRIVILEGES ON . TO 'root'@'localhost' WITH GRANT OPTION
2021-01-07 20:23:11,810 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	GRANT PROXY ON ''@'' TO 'root'@'localhost' WITH GRANT OPTION
2021-01-07 20:23:11,810 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - MySQL server variables related to change data capture:
2021-01-07 20:23:11,812 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_cache_size                             = 32768
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_checksum                               = CRC32
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_direct_non_transactional_updates       = OFF
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_error_action                           = ABORT_SERVER
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_format                                 = ROW
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_group_commit_sync_delay                = 0
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_group_commit_sync_no_delay_count       = 0
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_gtid_simple_recovery                   = ON
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_max_flush_queue_time                   = 0
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_order_commits                          = ON
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_row_image                              = FULL
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_rows_query_log_events                  = OFF
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_stmt_cache_size                        = 32768
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_transaction_dependency_history_size    = 25000
2021-01-07 20:23:11,813 INFO  io.debezium.connector.mysql.SnapshotReader                   [] - 	binlog_transaction_dependency_tracking

可以通过缩小数据库权限避免扫描全库
-- 授予REPLICATION Slave权限
GRANT RELOAD,REPLICATION SLAVE, REPLICATION CLIENT on *.* to 'username';

-- 授予目标库的访问权限
GRANT SELECT ON `your_single_database`.* TO 'username'@'%';

-- 刷新权限
FLUSH PRIVILEGES;

Closing this issue because it was created before version 2.3.0 (2022-11-10). Please try the latest version of Flink CDC to see if the issue has been resolved. If the issue is still valid, kindly report it on Apache Jira under project Flink with component tag Flink CDC. Thank you!


Missing '-p-' scan option to scan all ports

-p- is a commonly used option and seems to be missing.

Can close this, PR already has been merged. 👍


Cucumber suite improvements

Cucumber suite improvements. Also includes a contribution from #1033.
Some stats:
# master
20 scenarios (3 pending, 17 passed)
103 steps (2 skipped, 3 pending, 98 passed)

# this branch:
20 scenarios (1 pending, 19 passed)
104 steps (1 pending, 103 passed)

I tried to write detailed commit messages example to "preserve the knowledge" about how these scenarios work.
The contributing guidelines say we should squash the commits, but I have refrained from doing so because we would loose some of the info from the commit messages.
Other than that, I think I'm in compliance with the guidelines.

Looks like these commits were merged in. Closing.


[SPARK-40269][CORE] Randomize the orders of peer in BlockManagerDecommissioner

What changes were proposed in this pull request?
Randomize the orders of peer in BlockManagerDecommissioner
Why are the changes needed?
Avoid migrating data to same nodes
Does this PR introduce any user-facing change?
No
How was this patch tested?
Manually tested

Can one of the admins verify this patch?

@dongjoon-hyun Could you help take a look?

Thank you for pinging me, @warrenzhu25 . Could you try to add a test case for this please?

if want to verify the newPeers is randomized, we might need to expose newPeers  as val. Do you think it's acceptable? Or should we skip this straightforward unit test instead of introducing one method?
I checked other usage of Utils.randomize in ShuffleBlcokFetchIterator. It seems it also don't have unit test to cover this.

@Ngone51 Thanks for reviewing this. Will you merge this into master?


SEGV when QUIC configuration is invalid

Motivation:
When QuicheConfig.createNativeConfig() throws, for example if the server certificate and/or private key are invalid or missing, a SEGV later happens when QuicheQuicCodec frees the nativeConfig object.
Modifications:
Check if nativeConfig is zero before calling Quiche.quiche_config_free().
Result:
No more SEGV.

test this please

test this please

@thomdev thanks a lot

@thomdev thanks a lot


Correct outdated statement in generate-schema.md

This statement is quite old and, at least in my usage, is incorrect. I had to explicitly set these options to true before they had any effect.
/label docs

Thank you very much! Looks like this was missed during https://github.com/apollographql/graphql-tools/pull/183.


Add number codes as aliases for debian images

Number codes are often used instead of Debian release names. Ej, Debian 8 == Debian Jessie. Since images can have aliases, could you add these number codes to the Debian images in "images:"?
So we can make lxc launch images:debian/8 instead of lxc launch images:debian/jessie

That should be possible, at least for the simplestreams image server, will need to tweak our scripts a bit though.

stgraber@castiana:~$ lxc launch images:debian/8 c3
Creating c3
Starting c3
stgraber@castiana:~$

Awesome! Thanks!


Container lose interactivity after calling removeInteractive and setInteractive

version 3.11.0
Actually i didn't find a proper way to change container input hitArea after first setSize -> setInteractive, maybe i missed something ?
https://jsfiddle.net/zp7ky4fe/, i tried to reset interactivity with shape (same behaviour with setSize), if i do in way container.removeInteractivity and immediately container.setInteractivity(shape, callback) interactivity lost anyway. But if i call container.removeInteractivity -> setTimeout(() => container.setInteractivity(shape, callback), 1000) - everything works as expected.
So i checked the source code and found that condition for insertion this._pendingInsertion.indexOf(child) === -1 && this._list.indexOf(child) === -1 is false when i call  container.removeInteractivity and immediately container.setInteractivity(shape, callback) -  because current container still exist in  the _list and this part of code
for (var i = 0; i < toRemove; i++)
        {
            var gameObject = removeList[i];

            var index = current.indexOf(gameObject);

            if (index > -1)
            {
                current.splice(index, 1);
                this.clear(gameObject);
            }
        }

executes after queueForInsertion() finished, also i dont really understand why do we call this.clear(gameObject) when we already cleared gameObject here:
this.scene.sys.input.clear(this);
    this.input = undefined;
    return this;

Sorry for my not perfect english, kinda hard to explain :0

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

What is it you're trying to actually achieve?
When you call removeInteractive it queues the Input Handler for removal, it doesn't happen immediately. Which is why you can't set it right away again. One game step needs to have happened before you could do that. Also, it's a bit of a strange thing to do: Why remove something only to immediately add it again? Why not just edit the hit area if you want to change its size?

@photonstorm for example i set container size(100, 30) and call setInteractive, after game resize container size changed to 80x30 and i call setSize(80, 30), how should i change hitArea to 80x30 ?

container.input.hitArea.setSize(80, 30) assuming your hit area is a Rectangle, which it is by default.
Usually, you'd scale things to manage game resizing, not actually give them a new size, in which case you don't need to change the hit area because it uses the parents scale already.

@photonstorm thanks, didn't try to change hitArea like this. sorry for your time


Debugging a Chrome Extension in development mode

I followed the instructions to start the development server in debug mode:
NODE_ENV=development npm run start
However, when I look at the source code in Chrome DevTools, everything seems to be bundled and optimized, and I don't even find some bundles:

From the image you can tell that the code is optimized, and that some bundles (like popup.bundle.js and options.bundle.js) don't even show up.
Any idea if there's a way around this to allow dynamic debugging?
Thanks :)

This code isn't the optimized code, this is the code that webpack generates in order to allow the hot reload compilation.
I don't understand exactly what do you want to mean with "dynamic debugging" but if you, for example, put a console.log('hello') on your code and click in the file line in the right, you get the code before the transpilation.


Create e2e tests for hello-eks-anywhere application

Create automated end-to-end tests for hello-eks-anywhere application. This test should focus on making sure the various actions of the controller work.

installation

configuration

update

upgrade

delete

Phase 1: Just the minimum

[X] installation
[X] validate functionality

Phase 2: Expanded lifecycle (currently in progress)
Each step is assumed to include validation

[ ] configuration
[ ] update
[ ] upgrade
[ ] delete

Phase 3: Expanded environments
Each combination is assumed to include validation

Provider
OS
Kubernetes Version

vSphere
Bottlerocket
1.22

1.21

Ubuntu
1.22

1.21

1.20

Docker
Bottlerocket
1.22

1.21

Ubuntu
1.22

1.21

1.20

https://github.com/aws/eks-anywhere/pull/2801 actually implements phase 3. So phase 2 still needs work.


Unable to connect in remote scenarios

Environment:

VS Code stable @ latest
Remote - SSH extension @ latest
Remote - WSL extension @ latest
Edge Chromium on Dev channel @ latest
Windows 10 Insiders (18922) with WSL 2 Ubuntu (unlikely but may be related to why this isn't working)

The extension is installed as a UI extension and I'm using the default launch config:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Launch Microsoft Edge and open the Elements tool",
      "request": "launch",
      "type": "vscode-edge-devtools.debug",
      "url": "http://localhost:8080"
    }
  ]
}

Working on a vue.js app.
WSL

Open the integrated terminal and run $ npm run serve to start the app
Launch into the debugger

Result:
The browser launches and loads the page. In VS Code, an empty quick pick shows up along with the following error:

Couldn't attach to http://localhost:8080.
onDidNotificationChange @ workbench.main.js:2379

SSH
I'm using an Azure VM with Ubunt 16.04.

Connect to VM and forward ports 8080 and 9222 to localhost (see below)
Open the integrated terminal and run $ npm run serve to start the app
Launch into the debugger

Results in the same behavior as WSL:
The browser launches and loads the page. In VS Code, an empty quick pick shows up along with the following error:

Couldn't attach to http://localhost:8080.
onDidNotificationChange @ workbench.main.js:2379

Feel free to ping me on teams with any questions, I'm happy to help however I can!

@fiveisprime Thanks for the feedback! We haven't done testing with WSL or VMs yet.
We'll follow up to understand your specific workflows. Thanks!

I'll take a look into this and see if I can figure out what is going on here.

This looks to be another case of the browser not launching with the --remote-debugging-port set if you already have an instance open.
The workaround is to close all instances of Edge before you launch via VS Code.
I'll leave the issue open until we can find a better fix for this.

@fiveisprime What would you expect the default behavior to be for the "Launch Microsoft Edge and open the Elements tool" configuration? Launch a new instance every time?
We're having a similar discussion about the default behavior on Issue #57 😊

I'll comment on #57 and close this one


Improvements

Apart from the changes I suggested in the previous issue, I have a few ideas to improve package quality:

[ ] Coding Standard/Style:

[ ] Add CS checking
[ ] Docblocks

[ ] Remove "noise" (like: string $url The URL <- Makes no sense IMO)
[ ] Add dockblocks when missing
[x] Fix dockblocks where something is wrong (like Entitymanager instead of RouteInterface

[ ] Add editorconfig

[ ] Code

[x] Array typehints (setImages, setVideos)
[x] Drop Interface suffix: Symfony, Zend and the FIG still pushes it, but fortunately more and more developers realize, it's evil (reference: http://verraes.net/2013/09/sensible-interfaces/)
[ ] Separate AbstractProvider into smaller components: extract route generation logic
[ ] Remove BaseFormatter

[ ] Package

[ ] Add a Changelog
[x] Add a CONTRIBUTING guide
[ ] Remove unnecessary defaults from PHPUnit config
[ ] Add the Contributor Code of Conduct
[x] Change to PSR-4 autoloading (and remove unnecessary custom ones)
[ ] Separate components requiring external dependencies into separate packages (doctrine, propel)
[ ] Unit test against lowest dependencies

[ ] New Features

[ ] Add support for custom types: http://www.sitemaps.org/protocol.html#extending
[ ] Add support for setting sitemap options directly in route options (RouteCollectionProvider)
[ ] Add a caching layer for providers with expensive calculations
[x] Add a ChangeFrequency class/interface with common change constants
[ ] Introduce streaming somehow to improve memory efficiency

These are the things I have in my mind so far.
I marked BC breaking changes with italic. In these cases TODOs and deprecation warnings should be triggered.
Ultimately I think this project could also have it's own organization. Like sitemaphp (which I immediately registered, just in case :D, can invite you if interested)
There are many others as well, but I found yours to have the most decent API and workflow (actually I started to develop exactly the same)

I referenced the improvements you listed here in a new issue that will contain the things I want to see in a new version. I also have created separated issues for some of the items listed here.
Feel free to contribute if you're interested :)

Will do, thanks for reply and consideration.


What completion params to use with EvtIoRead and EvtIoWrite completions?

I looked through MSDN, didn't find anything (at least, not easily). Could you publish exactly how to return the #bytes read or written for each of these APIs?

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

ID: f2b6f03e-25a2-08a7-5f55-5b1eaef879d8
Version Independent ID: 1d941f6c-10c0-e4ed-99b2-ea23332c6102
Content: Completing I/O Requests
Content Source: windows-driver-docs-pr/wdf/completing-i-o-requests.md
Product: windows-hardware
GitHub Login: @windows-driver-content
Microsoft Alias: windowsdriverdev

@Shyamal-V @wm1 any thoughts?

Use WdfRequestCompleteWithInformation(Request, status, bytesCopied);

Thanks @wm1!  Closing this out, @andyraf, let us know if we can help otherwise.


Support npm

@spite is there anything blocking you from publishing it to npm and bower?
It would be very nice to get the lib from there.

I don't usually use npm modules, but I published ccapture to npm some time ago: https://www.npmjs.com/package/ccapture.js
I'm not sure it works as expected. Could you try using it and report back any issues?

The npm package looks good to me.


KSCrash UndefinedBehaviorSanitizer

Pods/KSCrash/Source/KSCrash/Recording/KSCrash.m:482:23: runtime error: variable length array bound evaluates to non-positive value 0
UndefinedBehaviorSanitizer: undefined-behavior xxxx/Pods/KSCrash/Source/KSCrash/Recording/KSCrash.m:482:23 in

Thanks for the report, @crossle. Which version of bugsnag-cocoa are you using? Can you link to an example error report?

5.7.0, The lastest version 5.10 work well, thanks


aerospike client c sdk for Ubuntu 20

The artifacts website doesn't have the version 20 so when it tries to download it with the naming that's described in the shell scripts it doesn't find it and gets a corrupted file with the same name the solution is simple which is renaming the deb package from 'aerospike-client-c-devel-4.6.9.ubuntu18.04.x86_64.deb' to 'aerospike-client-c-devel-4.6.9.ubuntu20.04.x86_64.deb' that will do the work locally but a version for ubuntu 20 needs to be uploaded to the artifacts server https://artifacts.aerospike.com/aerospike-client-c/ or the shell script be edited to work around it but I can't do it because I am not good with bash.

Debian 11 is the same problem
info: downloading 'https://artifacts.aerospike.com/aerospike-client-c/4.6.9/aerospike-client-c-devel-4.6.9.debian11.x86_64.deb'
error: 'aerospike-client-c-devel-4.6.9.debian11.x86_64.deb' is not a Debian format archive

hotfix workaround is overload script /src/scripts/os_version.sh to fixed value. This working for me for building on Debian 11 from debian10 deb package.


Z5 v5.0.22: manual refresh of dynamic keys -> no citation key change when changing large set of items

Report ID: YFXDIIGX
When changing a large set of items (2441), the citation keys don't seem to change. I don't know if it's a a performance issue, personal issues with impatience or something else... I've let it run for some minutes (and zotero effectively uses CPU for that it seems, around 120 %) until it drops to a 'normal' level of around 3-5 %.
Report ID actions:

Changing 10 references : visible change (both in column + sidepane)
Changing around 15 references : visible change (both in column + sidepane)
Changing all the references (2441 items) in the database: no visible change (both in column + sidepane) after around 4 minutes (drop in zotero CPU usage)

Looking at the logfile I think it may be caused by the same problem of #738. Can you try to reproduce with 4316, and if it still occurs, submit a new debug log?

Good news, that's indeed the case. After a refresh of all the bibtexkeys, they all change accordingly..


Measure eth1 voting period in epochs instead of slots

While debugging beacon chain code hit this minor spec issue: SLOTS_PER_ETH1_VOTING_PERIOD is measured in slots while the beaconState.eth1_data_votes list is reset during epoch processing.
The condition for reset is
if (state.slot + 1) % SLOTS_PER_ETH1_VOTING_PERIOD == 0:

This implies that the constant should be the multiple of SLOTS_PER_EPOCH. May be it makes sense to nominate this constant in epochs to avoid malformed values for a custom genesis?

I will apply changes to tests and phase-1 spec if this PR has any positive feedback

Another option is to change the reset condition to
if len(state.eth1_data_votes) + SLOTS_PER_EPOCH > SLOTS_PER_ETH1_VOTING_PERIOD

this way eth1_data_votes would not overflow during the next epoch, but that doesn't prevent from setting SLOTS_PER_ETH1_VOTING_PERIOD < SLOTS_PER_EPOCH by mistake in a custom config

Anyone feel strongly about getting this into the next release or not?

if we are going to change it then the sooner the better :)


Agnostic comparisons to zero?

Consider the following code:
#include <vector>
template<typename T>
class polynomial {
public:
     polynomial(std::vector<T>&& coeffs) : c_{std::move(coeffs)} {
         while (c_.size() > 1 && c_.back()==T(0)) {
             c_.resize(c_.size() - 1);
         }
     }

     size_t degree() { return c_.size() - 1; }
private:
    std::vector<T> c_;
};

This code cannot operate with mp-units types due to the constraint documented here, and a workaround is documented here.
Nonetheless, I wonder if it is possible to make this code work for double and float whenever the mp-units library is not available, yet works in the expected way when mp-units types are provided. (Perhaps some __has_include work is possible, but it feels like a more elegant solution is available with more thought.)
I have tried to use the std functions via
#include <vector>
#include <compare>
template<typename T>
class polynomial {
public:
     polynomial(std::vector<T>&& coeffs) : c_{std::move(coeffs) {
         while (c_.size() > 1 && std::Is_sq(c_.back())) {
             c_.resize(c_.size() - 1);
         }
     }

     size_t degree() { return c_.size() - 1; }
private:
    std::vector<T> c_;
};

but no joy on clang-17.

Value initialization will work, and in many ways it's an elegant solution.  That said, I think the downside is that it reduces clarity of intent: it relies on the knowledge that T{} produces a value of zero.  This is indeed true for all numeric types, and for mp-units quantity types, but T{} simply lacks the clarity of an alternative that says "0" or "zero" in some way.
As a counterpoint, Au is deliberately paranoid and standoffish about the value of T{} for its quantity types.  That said, I have to admit that --- spoiler alert! --- we do produce a zero value from our default constructor, and despite our protestations that we reserve the right to change it, I find it hard to imagine producing any other value.  Perhaps I'm tilting at windmills here.  :slightly_smiling_face:
I guess as an alternative that preserves intent, you could write something like this?
constexpr auto ZERO = T{};
// ...

If T{} equals 1 and addition is a

set of two elements 0 and 1 with addition modulo 2

that static assertion passes.


Can't add a custom domain

When trying to add a custom domain to the Static Web App I just created, everything seems to work :

"Validate" gives a green mark
"Add" takes a bit of time
I receive a bit later the notification "Successfully created custom domain"

Except that it doesn't ! The list of custom domains stays empty, and of course browsing to the domain fails (with a 404, from Azure I guess).
No idea if it is related, but I couldn't make SignalR to work either (see #164), and while investigating, I added an App Insight reporting, and I see this error a few times, apparently around the time I made my attempt :
The BlobChangeAnalysisStateProvider requires the default storage account 'Storage', which is not defined.
System.InvalidOperationException:
   at Microsoft.Azure.WebJobs.Script.ChangeAnalysis.BlobChangeAnalysisStateProvider+<GetCurrentAsync>d__5.MoveNext (Microsoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=nullMicrosoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /src/azure-functions-host/src/WebJobs.Script.WebHost/BreakingChangeAnalysis/BlobChangeAnalysisStateProvider.csMicrosoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: 49)
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult (System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e)
   at Microsoft.Azure.WebJobs.Script.ChangeAnalysis.ChangeAnalysisService+<TryLogBreakingChangeReportAsync>d__12.MoveNext (Microsoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=nullMicrosoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: /src/azure-functions-host/src/WebJobs.Script.WebHost/BreakingChangeAnalysis/ChangeAnalysisService.csMicrosoft.Azure.WebJobs.Script.WebHost, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null: 92)

Also note that the errors I got with SignalR also hinted at something to do with the storage.

@anthonychu can comment on the signalR issue.
Do you mind sharing the details of the custom domain addition? Specifically if you have the time, domain, and the name of your static web app (i.e. red-field-1234) then I can take a look.

@anthonychu can comment on the signalR issue.
Do you mind sharing the details of the custom domain addition? Specifically if you have the time, domain, and the name of your static web app (i.e. red-field-1234) then I can take a look.

Sure, it's thankful-smoke-07e578103, that I tried to bind to it-for-ops.famille-lafay.fr, around 2020-09-30T20:30:00+02:00. The CNAME entry is still there.

Hey @lanfeust69 , we are seeing that we are unable to provision the underlying certificate because this domain has CAA records on it that do not allow DigiCert to create certificates. Can you remove those records or allow DigiCert?

That was indeed the reason, it worked as expected after allowing DigiCert.
Perfectly legit reason to fail, perfectly unlegit not to tell anything about it 🙂. But no problem, this is all what previews are about !
Do you prefer the issue to be closed, or keep it open to track the real issue (bad reporting) ?

@pragnagopa Do you know anything about the The BlobChangeAnalysisStateProvider requires the default storage account 'Storage' message above? This is a Node.js app. I think I've seen this as well if a storage account doesn't exist.

The BlobChangeAnalysisStateProvider requires the default storage account 'Storage', which is not defined. System.InvalidOperationException: is only a warning and can be ignored as it does not impact the app itself.

Closing due to no traction. Feel free to reopen if required!


AT模式部分节点二阶段异步提交不执行

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
seata-server有五个节点，执行一段时间之后，部分节点二阶段异步提交停止执行
通过搜索“Committing global”相关日志，无搜索结果，判定该节点异步提交停止执行
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
请教下是什么原因会导致类似问题的发生？
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version :1.8
Seata version:  1.3.0
OS :
Others:

Asynchronous tasks can only be executed by one node at the same time, and the execution node is determined by distributed lock.

Our seata-server version number is 1.3.0, which does not use distributed locks @slievrly

I understand that in AT mode, asynchronous commit in two phases, multiple node services will cause data competition problems, and in a scenario with a large amount of concurrency, will cause nodes to interrupt each other's asynchronous commit global transactions, resulting in performance loss in two phases


iOS scrollTo possible bug - inconsistent blank page

Hey,
Lately I have been playing a lot with Clusterizejs as I am trying to avoid switching my project to React and use Virtual Lists.
I actually managed to make it work as expected on mobile/tablet devices but am experiencing an 1 somewhat critical issue.
On iPad, when I use the add to home screen functionality & open the "web app" from the home screen, I experience an issue where the scrolling is not always working as expected.
As it is quite difficult to explain why and how it works, I have also made a video of ~30 seconds that shows the bug (almost at the end of the video). Generally you will see that after clicking the links on the right side in the example I made, sometimes the view becomes blank and the items are not shown anymore.
The video is available at https://youtu.be/t3OXbd5geKo
UPDATE #1:
I think that the bug happens when I click on a link which suppose to scroll to a top value which is already shown in the current cluster, so clicking on the links A & Z seems to always work as expected but clicking on A & B might help you to reproduce the problem.
I would be happy to provide any information needed.
Thank you
Shaked

Hey
I can't reproduce this on iphone :(
and I don't have ipad to test this

Can I help somehow? Maybe test things you would have tested?

Seems like this issue is also happening with ReactJS:
https://www.youtube.com/watch?v=KIDnUovmGVo&feature=youtu.be
https://pymwymi.io/clusterizejs/reactjs/index.html
Maybe it's related to the way iOS is rendering homescreen webapps?

@NeXTs I think that the reply from @clauderic is summarizes this issue quite good.

I don't believe this is specifically an issue with react-tiny-virtual-list. It looks like a performance issue, where the device cannot render the requested rows fast enough since your rows are quite heavy to render (multiple images per row).
The difference in behaviour between when you look at your app in Safari vs an app added to the Home Screen is because the webviews used by both are different. When you look at the app in Safari, it uses WKWebView, which is significantly more performant than UIWebView, which is the webview used for web pages added to the home screen. I don't believe you can specify for a web page added to the home screen to run using WKWebView
You could look into bundling your app using Cordova instead, which would allow you to specify which webview is used and select WKWebView.

Therefore, I am closing this issue.
Thank you!


ckanext-ytp-requests fails with Attribute Error on CKAN 2.4

Hey!
I've got a ckan 2.4 instance installed with datacats and get the error AttributeError: 'module' object has no attribute 'ytp_common_js/ytp_form.js' after installing ytp-requests an trying to open an organisation on my ckan.
I've got ckanext-hierarchy installed, which allows for the creation of hierarchical organisations. Not sure if there's a potential conflict or if I maybe missed installing a dependency? Nothing specific was mentioned in the install instructions though.
Here's the full traceback:
URL: http://energydata.uct.ac.za/organization/sanedi
File '/usr/lib/ckan/local/lib/python2.7/site-packages/weberror/evalexception.py', line 428 in respond
  app_iter = self.application(environ, detect_start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/dec.py', line 147 in __call__
  resp = self.call_func(req, *args, **self.kwargs)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/dec.py', line 208 in call_func
  return self.func(req, *args, **kwargs)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/fanstatic/publisher.py', line 234 in __call__
  return request.get_response(self.app)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/request.py', line 1053 in get_response
  application, catch_exc_info=False)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/request.py', line 1022 in call_application
  app_iter = application(self.environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/dec.py', line 147 in __call__
  resp = self.call_func(req, *args, **self.kwargs)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/dec.py', line 208 in call_func
  return self.func(req, *args, **kwargs)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/fanstatic/injector.py', line 54 in __call__
  response = request.get_response(self.app)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/request.py', line 1053 in get_response
  application, catch_exc_info=False)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/webob/request.py', line 1022 in call_application
  app_iter = application(self.environ, start_response)
File '/project/ckan/ckan/config/middleware.py', line 389 in inner
  result = application(environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/beaker/middleware.py', line 73 in __call__
  return self.app(environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/beaker/middleware.py', line 155 in __call__
  return self.wrap_app(environ, session_start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/routes/middleware.py', line 131 in __call__
  response = self.app(environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/wsgiapp.py', line 125 in __call__
  response = self.dispatch(controller, environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/wsgiapp.py', line 324 in dispatch
  return controller(environ, start_response)
File '/project/ckan/ckan/lib/base.py', line 296 in __call__
  res = WSGIController.__call__(self, environ, start_response)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/controllers/core.py', line 221 in __call__
  response = self._dispatch_call()
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/controllers/core.py', line 172 in _dispatch_call
  response = self._inspect_call(func)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/controllers/core.py', line 107 in _inspect_call
  result = self._perform_call(func, args)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/controllers/core.py', line 60 in _perform_call
  return func(**args)
File '/project/ckan/ckan/controllers/group.py', line 228 in read
  extra_vars={'group_type': group_type})
File '/project/ckan/ckan/lib/base.py', line 175 in render
  return cached_template(template_name, render_template)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/pylons/templating.py', line 249 in cached_template
  return render_func()
File '/project/ckan/ckan/lib/base.py', line 129 in render_template
  return render_jinja2(template_name, globs)
File '/project/ckan/ckan/lib/base.py', line 86 in render_jinja2
  return template.render(**extra_vars)
File '/usr/lib/ckan/local/lib/python2.7/site-packages/jinja2/environment.py', line 894 in render
  return self.environment.handle_exception(exc_info, True)
File '/project/ckanext-ytp-request/ckanext/ytp/request/templates/organization/read.html', line 1 in top-level template code
  {% ckan_extends %}
File '/project/ckan/ckan/templates/organization/read.html', line 1 in top-level template code
  {% extends "organization/read_base.html" %}
File '/project/ckanext-hierarchy/ckanext/hierarchy/templates/organization/read_base.html', line 1 in top-level template code
  {% ckan_extends %}
File '/project/ckanext-datarequests/ckanext/datarequests/templates/organization/read_base.html', line 1 in top-level template code
  {% ckan_extends %}
File '/project/ckan/ckan/templates/organization/read_base.html', line 1 in top-level template code
  {% extends "page.html" %}
File '/project/ckan/ckan/templates/page.html', line 1 in top-level template code
  {% extends "base.html" %}
File '/project/ckanext-pages/ckanext/pages/theme/templates_main/base.html', line 1 in top-level template code
  {% ckan_extends %}
File '/project/ckan/ckan/templates/base.html', line 103 in top-level template code
  {%- block page %}{% endblock -%}
File '/project/ckan/ckan/templates/page.html', line 19 in block "page"
  {%- block content %}
File '/project/ckan/ckan/templates/page.html', line 22 in block "content"
  {% block main_content %}
File '/project/ckan/ckan/templates/page.html', line 57 in block "main_content"
  {% block primary %}
File '/project/ckan/ckan/templates/page.html', line 70 in block "primary"
  {% block primary_content %}
File '/project/ckan/ckan/templates/page.html', line 85 in block "primary_content"
  {% if self.page_primary_action() | trim %}
File '/project/ckanext-ytp-request/ckanext/ytp/request/templates/organization/read.html', line 6 in block "page_primary_action"
  {% resource 'ytp_common_js/ytp_form.js' %}
File '/project/ckan/ckan/lib/jinja_extensions.py', line 315 in _call
  h.include_resource(args[0], **kwargs)
File '/project/ckan/ckan/lib/helpers.py', line 1436 in include_resource
  r = getattr(fanstatic_resources, resource)
AttributeError: 'module' object has no attribute 'ytp_common_js/ytp_form.js'

ytp_form.js resides in our main plugin ckanext-ytp-main, but installing it also installs lots of our instance specific customatization. I'll remove the dependancy once I have time for it.

Thanks, would be great to be able to use your extension.

Fixed in https://github.com/yhteentoimivuuspalvelut/ckanext-ytp-request/commit/650c1e075c5f3a65b9baefa0a892be401ffe1673


Add Cloud Bindings for Mistral AI

Introduce Cloud Bindings support to configure the Mistral AI integration
Update the Cloud Bindings documentation accordingly

thanks, merged in 6e62ff7d83161a24fd98d01568d8921f9febcd8a


CDI-471 Clarified the behavios of Annotated and repeatable annotation…

…s.  Provide a default implementation in case there are custom implementations out there.

http://lists.jboss.org/pipermail/cdi-dev/2016-November/009294.html

@johnament @antoinesd Guys, we really need this to be fixed ASAP so that we can release a new CDI API Alpha and align Weld afterwards.

@johnament if you don't have time, feel free to give us right on the PR by checking "allow edits from maintainers" checkbox.

@johnament @antoinesd I've re-read the JLS and to be honest I don't understand why the default Weld implementation should not be portable accross JVMs.
See also 9.7.5 Multiple Annotations Of The Same Type:

If a declaration context or type context has multiple annotations of a repeatable
annotation type T , then it is as if the context has no explicitly declared annotations
of type T and one implicitly declared annotation of the containing annotation type
of T .
The implicitly declared annotation is called the container annotation, and the
multiple annotations of type T which appeared in the context are called the base
annotations. The elements of the (array-typed) value element of the container
annotation are all the base annotations in the left-to-right order in which they
appeared in the context.

John which part of the Weld default impl is problematic?

@mkouba You may want to read through section 9.6.3 to see where the full list of bugs are with your method.  http://docs.oracle.com/javase/specs/jls/se8/html/jls-9.html#jls-9.6.3
The ones I see right off:

Its not handling Container-Containers
You're missing the check that the annotations of the container are actually the right annotations

IMHO the new proposed solution is better even if it doesn't handle all cases.  I can't think of a scenario where someone has implemented AnnotatedCallable or AnnotatedMember directly and its done something useful.

Its not handling Container-Containers

Good point! I wonder if there is a use-case for repeatable containing annotation though ;-)
Ok, the current defailt implementation looks good.

Looks good, +1


Ref docs

Pull request
Description
Move the reference documentaiton into the codebase.
This is a (nearly) no code impact change aside of some re-organization and cleanup.
It bases reference documentation on the mod comment for the respective file. This has the advantage that it is significantly easier to keep documentation and code in sync if they are co-located in the same place.

[x] codecs
[ ] connectors
[x] extractors
[x] operators
[x] postprocessors
[x] preprocessors

Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance
-/-

I left connectors out to do them in a separate PR as we already have 83 files changed and connectors will require significant restructuring of the module heary.  I don't want the review worthy changes in that get obscured by the rather simple copy&paste ones in this RP


What version of Sails to use? 0.11.0? 0.11.1? 0.11.1-rc1?

I'm wondering if the version 0.11.1 and 0.11.1-rc1 are stable enough to be used.
I believe the 0.12.0-rc1 is still under development?
Similar question asked there but didn't get any answer: https://groups.google.com/forum/#!topic/sailsjs/1Fi74H3zw6U

I'll find out for sure and update when I get the answer~

Yes, 0.11.0 is the latest stable release.

great tip from @sgress454
The latest stable version of Sails is v0.11.0.  You can always tell the latest version by doing npm show sails and looking at the "latest" tag version, or by going to https://github.com/balderdashy/sails/tree/stable and checking the version there.

There have been a number of questions on this topic I think because only the release candidate was listed in the Github release page. I've since updated this: https://github.com/balderdashy/sails/releases


Telemetry on AI usage

We should have a metric on host start up for whether a given Function App is using the App Insights feature.
We should have the settings from the host.json available in the host logs. @fabiocav might already be doing this.

Metric is already available, as is the host.json settings.


Support for WSL

Hi,
This tool is great! Thank you @Andy2244 for it! :+1:
However, it has troubles when running in:

Windows 10 with WSL and Docker for Windows in Linux mode.

 I prefer to use Bash in WSL.
To run the builder.ps1 in Windows 10 you need to execute first powershell Set-ExecutionPolicy Unrestricted, and this isn't documented!
When running the powershell script with Docker for Windows (and not with Windows Containers) then you found this error:
Error response from daemon: invalid mount config for type "bind": invalid mount path: 'C:/Users/me/openwrt/openwrt-package-builder-1.0.2' mount path must be absolute
I can't switch to Windows Containers as my current environment uses Docker for Windows using the regular mode for running other docker images. So the switch is impossible.
When executing the script builder.sh inside WSL you have troubles with sudo as it doesn't exists.
When executing the script builder.sh inside WSL you have troubles as the command "docker" doesn't call to "docker.exe" (the native executable). You need to declare alias docker=docker.exe.
When executing the script builder.sh inside WSL you have troubles as the script detects some syntax errors.

So, in this enviroment these scripts are useless.
I suggest to improve it in one of these ways:

Add support for WSL with a new builder-wsl.sh script.
OR, add support in builder.ps1 for Docker for Windows and document the powershell Set-ExecutionPolicy Unrestricted requirement.
OR, enhance the builder.sh script to support: different docker binary, Windows host, etc.
OR, move the script to a docker image with docker-in-docker.

I don't know what's the best. I hope you will consider at some point to implement one of them.
Thank you for this project!

Yeah WSL was really buggy when i started the package builder, as workaround you should be able to easily switch between windows/linux containers via tray icon, build the package and switch back. Last time i tried this it worked without problems.
PS: I already have to test 3 versions (Win10, Linux, Mac) and since i don't use WSL would like to avoid having to maintain/test a extra version. As you noticed invoking the native windows docker version from within WSL is kinda tricky and the native linux version does not work in WSL as far as i know.

Hi @Andy2244 ,
Thank you very much for your clear and gentle explanation.
I don't want to push more effort for you going to 4 versions. I feel it will be useless.
However, as an enchancement, think on the scenario 4 for the future: a dockerized version of the script.
I feel the problem is the permanent storage for the cache. I'm right?


add extraKey to useRpcEndpoint

Luca found getter in useQuery(['rpcEndpoint', getter], can only be serialized as a null. So there's no difference between multi-chain endpoints, when switching between chains things wouldn't be changed automatically. So Luca suggested adding an extra key for better react query usage, like:
export const useRpcEndpoint = <TData = string | HttpEndpoint>({
    getter,
    options,
    extraKey
}: UseRpcEndpointQuery<TData>) => {
...useQuery(['rpcEndpoint', getter, extraKey],
}

Would be nice to use a better option name, besides that LGTM!

I reconsidered this.
I removed flag. If user left extraKey null, the behavior of the function remain the same query key as before('["rpcEndpoint",null]'). If user input an extraKey, user will get '["rpcEndpoint", "extraKey"]'.

There's a requirement from @marslavish :
some of customized hooks should have extraKey too. So I added needExtraQueryKey option in ReactQuery option, but currently, only useEndpoint is changed into this logic. I'll make another PR on other customized hooks.


Waiting for another flutter command to release the startup lock...

Waiting for another flutter command to release the startup lock...

Do you have flutter packages pub build_runner watch running?
Kill all dart processes and try again or restart the computer.

@sathishbalan is this still an issue?

Might be a dup of #14703

yes, get it; it is work

Kill the terminal using the delete (trash) icon if you are using a Visual Studio Code editor

Hi!
i'm still having the same issue and @zoechi didn't work for me.
What I noticed is that there is an issue with the 'pub' tool ==> 'build_runner is not found' and that there is an exit code 64 for involved (what ever that means) I looked it up in the documentation, but without any success...
Hopefully, this will be useful for some one to solve the solution!

You can: rm ./flutter/bin/cache/lockfile

This issue also occurs due to internet proxies ,make sure that you have full network access .

you can open flutter/bin/cache/lockfile ,and delete this lockfile ,I solve this problem by this

On OSX:
rm /Applications/flutter/bin/cache/lockfile

On OSX:
rm /Applications/flutter/bin/cache/lockfile

delete 'lockfile',It is work

This issue also occurs due to internet proxies ,make sure that you have full network access .

And what about if we have a proxy. What can we do to fix it?

In my case, there was an flutter packages get command running in the background. As it was looking for package that did not exist due to incorrect name, changing this package name fixed the issue.
` [eamper-app] flutter packages get
Running "flutter packages get" in eamper-app...
Because eamper depends on ffirebase_core any which doesn't exist (could not find package ffirebase_core at https://pub.dartlang.org), version solving failed.
pub get failed (69) -- attempting retry 1 in 1 second...
Because eamper depends on ffirebase_core any which doesn't exist (could not find package ffirebase_core at https://pub.dartlang.org), version solving failed.
pub get failed (69) -- attempting retry 2 in 2 seconds...
Because eamper depends on ffirebase_core any which doesn't exist (could not find package ffirebase_core at https://pub.dartlang.org), version solving failed.
pub get failed (69) -- attempting retry 3 in 4 seconds...
Because eamper depends on ffirebase_core any which doesn't exist (could not find package ffirebase_core at https://pub.dartlang.org), version solving failed.
pub get failed (69) -- attempting retry 4 in 8 seconds...
Running "flutter packages get" in eamper-app...                    23,0s
exit code 0
[eamper-app] flutter packages get
Running "flutter packages get" in eamper-app...                     1,4s
exit code 0
`

Find the folder where flutter is installed, and delete flutter/bin/cache/lock file

run flutter clean

flutter clean won't run either. If I delete the flutter.bat.lock file, it will run clean, but the "Waiting ..." message still comes up when I restart the idea.  Have to reboot my computer to be able to delete lockfile, even when the IDE is shut down. Doesn't fix the problem.

flutter clean, changing networks, deleting lockfile, killing dart processes and restarting computer did not work for me. I'm starting to think maybe this happens on specific devices. Going to try that.

I suspect flutter would get more corporate adoption if it were easier to use in a corporate environment. Might want to figure out a way to remove all the proxy hoops that need to be jumped through to use it.

Restarting the terminal worked for me.

Still having this problem, nothing seems to clear it.

killall -9 dart

delete lock file not worked for me.

You can: rm ./flutter/bin/cache/lockfile

that'is it,thx

I had tried all the solution mentioned above, and nothing works for me and creating flutter application dialog goes forever, but what I did is, end AS task and open it again but this time instead of creating a new project, I just opened the project I just exit from it, and it opens fine,
what causes this problem, I think when I tried to load a picture from image.asset
after creating a new dir asset/images/pic.jpg and add the asset in pubspec.ymal
when getting the package or something, that's when all this happened
Conclusion:
just create a new project, and when Creating flutter project dialog appear close Android studio from Task manager, then open it again but this time open an existing project which is the previous one
hope that works for you

there may be a way to resolve this problem
just install another version of dart
update environment variables
it will be fixed

just delete the flutter/bin/cache/lock file and then do flutter upgrade in ide and it will resolve your problem.

just delete the flutter/bin/cache/lock file and then do flutter upgrade in ide and it will solve your problem.

just remove lock file and restart my Mac work for me

I solved the problem by opening task manager and killing the 'dart.exe' process(es)

You can: rm ./flutter/bin/cache/lockfile

Work for me,
thank you

@CompileYouth That's wored for me. Thanks

In my case, following command in Terminal or cmd helped (as suggested by Günter):
killall -9 dart

On Windows (as suggested by upupming):
taskkill /F /IM dart.exe

or remove this file
<YOUR FLUTTER FOLDER>/bin/cache/lockfile

This releases the occupied lock and makes you able to run other commands.

On Mac, open Activity Monitor, search dart, then quit all dart process


Use color to support colored ouput for windows

As titled https://github.com/fatih/color

yeah this isnt working for me either - i am doing this instead:
package main
import "github.com/labstack/gommon/log"
func main() {
   log.EnableColor()
   log.Info("aaaaa bbbbb")
}

Workaround:
package main
import (
   "github.com/apex/log"
   "github.com/apex/log/handlers/text"
   "github.com/mattn/go-colorable"
)
func main() {
   aa := colorable.NewColorableStdout()
   log.SetHandler(text.New(aa))
   log.Warn("bb")
}

Or:
package main
import "github.com/labstack/gommon/log"
func main() {
   log.EnableColor()
   log.Warn("bb")
}


[BUG] No report generated when thresholds fail the scan

Describe the bug
Introduced in version 2.0.19
When we use scan command with

thresholds
report format to summaryJSON
the scan failed because of thresholds

There is no report generated but in the case where the scan passed there is report.
Expected behavior
I think report must be generated even if scan fail because of thresholds like in version 2.0.18.
Actual behavior
Unlike in version 2.0.18 the scan will not generate report if thresholds fail the scan.
Steps to reproduce

Create a project with a security issue SAST High for example
Run a scan with --report-format summaryJSON and --threshold sast-high=0 options
Notice there is no cx_result.json generated in .
Re run the scan without --threshold sast-high=0 or after SAST High issue fixed
Notice there is a cx_result.json generated in .

Environment

2.0.19
Linux

Additional comments
Here is my analyse:
The BUG was introduced in 2.0.19 in:
| Ast 12482 add summary html for async scans (https://github.com/Checkmarx/ast-cli/pull/405)
The file internal/commands/scan.go was modified and the createReportsAfterScan method call was moved from the handleWait method to the end of the runCreateScanCommand method.
The problem here is the block
err = applyThreshold(cmd, resultsWrapper, scanResponseModel)
if err != nil {
    return err
}

before the call of createReportsAfterScan.
Here is the lines:
https://github.com/Checkmarx/ast-cli/blob/c7a33215fbde596638016f29737e8d2a395c9563/internal/commands/scan.go#L1102-L1121
To fix it we may use this code:
AsyncFlag, _ := cmd.Flags().GetBool(commonParams.AsyncFlag)
if !AsyncFlag {
    waitDelay, _ := cmd.Flags().GetInt(commonParams.WaitDelayFlag)
    err = handleWait(cmd, scanResponseModel, waitDelay, timeoutMinutes, scansWrapper, resultsWrapper)
    if err != nil {
        return err
    }

    err = createReportsAfterScan(cmd, scanResponseModel.ID, scansWrapper, resultsWrapper)
    if err != nil {
        return err
    }

    err = applyThreshold(cmd, resultsWrapper, scanResponseModel)
    if err != nil {
        return err
    }
} else {
    err = createReportsAfterScan(cmd, scanResponseModel.ID, scansWrapper, resultsWrapper)
    if err != nil {
        return err
    }
}

return nil

Logs
2022/06/20 09:02:55 Scan status:  Running
2022/06/20 09:03:01 Scan status:  Running
2022/06/20 09:03:06 Scan Finished with status:  Completed
Threshold check finished with status Failed : sast-high: Limit = 0, Current = 1 |
Program exits with code:  1
Scan Failed

Thanks for the report ! I have the same problem !

Hi @Thomgrus  Thanks for your awesome analysis. We will include this in the next releases.
Next time, please feel free to open a PR with your change.
Thanks!

Hi @pedrompflopes,
Thank you, i can do a PR with this changes, references this issue ; no problem.
Ok i'll do it next time 🙂 (i just followed the documentation https://github.com/Checkmarx/ast-cli/blob/main/docs/contributing.md#getting-started)
Thanks !


apimanagement: flattening document to a proper object

This PR fixes a regression in the API Management version 2019-01-01 where the field was a concrete type in the previous API version (2018-01-01), but now returns a dictionary, which makes this field less usable:
https://github.com/Azure/azure-sdk-for-go/blob/v29.0.0/services/apimanagement/mgmt/2018-01-01/apimanagement/models.go#L8710
https://github.com/Azure/azure-sdk-for-go/blob/v29.0.0/services/apimanagement/mgmt/2019-01-01/apimanagement/models.go#L9269

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

I'm running our test suite for API Management against the generated Go SDK to confirm this works as expected 👍

I can confirm this fix fixes our broken acceptance tests (when using this commit, rather than v29.0.0 of the Go SDK):

Please refer to code which will explain it to you. We will need to do something similar in the terraform sdk.

@solankisamir so then shouldn't the Swagger be updated to use a Discriminator to expose the correct objects?

@solankisamir gentle ping

@solankisamir - Any updates on this?

@amarzavery @dsgouda I believe the autorest generator cannot generate .NET and other clients when using anyOf construct. That is the reason why I am against merging this PR. I have already shown @tombuildsstuff way we are handling responses in different clients.

@solankisamir I might be wrong, but it seems to generate fine for other Resource Providers?
For example the following Swagger: https://github.com/Azure/azure-rest-api-specs/blob/master/specification/streamanalytics/resource-manager/Microsoft.StreamAnalytics/stable/2016-03-01/inputs.json#L733-L792
generates the following C#/.net SDK:
https://github.com/Azure/azure-sdk-for-net/blob/master/src/SDKs/StreamAnalytics/Management.StreamAnalytics/Generated/Models/Serialization.cs#L20-L37
https://github.com/Azure/azure-sdk-for-net/blob/master/src/SDKs/StreamAnalytics/Management.StreamAnalytics/Generated/Models/JsonSerialization.cs#L23-L70
which also generates the following Go SDK structs:
https://github.com/Azure/azure-sdk-for-go/blob/master/services/streamanalytics/mgmt/2016-03-01/streamanalytics/models.go#L300-L305
https://github.com/Azure/azure-sdk-for-go/blob/master/services/streamanalytics/mgmt/2016-03-01/streamanalytics/models.go#L2867-L2872
and this conversion helper: https://github.com/Azure/azure-sdk-for-go/blob/master/services/streamanalytics/mgmt/2016-03-01/streamanalytics/models.go#L4071-L4076
As such I believe it should be possible to take this same approach here - WDYT?
Thanks!

ping @solankisamir

As discussed with autorest sdk team x-ms-discriminator will not resolve this issue. It was meant to be used for polymorphism case. But the response of this contract is
application/vnd.ms-azure-apim.swagger.definitions+json
{
   "properties" : {
    "contentType": "application/vnd.ms-azure-apim.swagger.definitions+json",
    "document" : "json schema here"
    }
}

But for application/vnd.ms-azure-apim.xsd+xml or application/vnd.oai.openapi.components+json or application/vnd.ms-azure-apim.wadl.grammars+xml
{
   "properties" : {
    "contentType": "application/vnd.ms-azure-apim.swagger.definitions+json",
    "document" : {
          "value" : "api schema here"
         }
    }
}

I agree this is a weirdness in the API and I have opened an issue https://github.com/Azure/azure-rest-api-specs/issues/6372 to fix this in the next version of the API

@solankisamir thanks for confirming; is there a (rough) timeframe for the next version of the API being available containing the fix?
@jhendrixMSFT since this API is going to require custom code to support it properly,  whilst we can add this to Terraform - since this affects any consumers, would it make sense for the Go SDK to handle this?

hi @tombuildsstuff  @chlahav can we close the PR for now since it's not ready for review and merge,  the PR is over several months. Pls create new PR when you're ready for review and merge.

Hi @tombuildsstuff @chlahav , the PR will be closed in 2 days since no update. Pls let us know if any comments.


docs(chore): copy the Readme to root as well

GH-116
Description
Copy the Readme to root as well
Fixes #116
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Intermediate change (work in progress)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Performed a self-review of my own code
[ ] npm test passes on your machine
[ ] New tests added or existing tests modified to cover all changes
[ ] Code conforms with the style guide
[ ] API Documentation in code was updated
[ ] Any dependent changes have been merged and published in downstream modules

:tada: This PR is included in version 7.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[ CREATE ] - Navbar

Create a navbar similar to the one below:

IF YOU WISH TO WORK ON THIS, PLEASE CHECK NO ONE HAS CLAIMED IT BELOW, IF NOT CLAIM IT BY COMMENTING

I want to Claim this task. I will start right away

Update on the task
I started the project with the main part based on the mock layout. Later today i will finish the navbar and work on responsivity

@MattCSmith can i work on this?

Will do a navbar

@subho2107 Its already being worked on. I will be creating more tasks shortly, however feel free to create your own task.

Update 2
I will just do the js part and then do the pull request :)


Add (de)serialize_optional_geometry helpers.

Before
#[derive(Deserialize)]
struct MyStruct {
    count: usize,
    geometry: Option<GeometryWrapper>,
}

#[derive(Deserialize)]
#[serde(transparent)]
struct GeometryWrapper(#[serde(deserialize_with = "deserialize_geometry")] Point<f64>);

After:
#[derive(Deserialize)]
struct MyStruct {
    count: usize,
    #[serde(deserialize_with = "deserialize_optional_geometry")]
    geometry: Option<Point<f64>>,
}

[x] I agree to follow the project's code of conduct.
[x] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

Hmmm... I haven't worked with this code for a bit, but I'm surprised that you'd need a custom deserialization method for this.
You can already do an Option<Geometry> with vanilla serde derive, right? I wonder why that wouldn't work for Point or the other Geometry enums 🤔

I'm sorry, I missed that this was about geo-types. I think the approach makes sense. 👍

Sounds good 😊

Note to self and other maintainers... the merge queue (which we recently adopted) seemed to merge this branch immediately without waiting for tests to complete (though the tests ultimately did pass, so no worries).
I updated a couple settings which I think we were missing, so it should work next time. 🤞
Most importantly the "require status checks" setting:

I also enabled "require PR before merging" like we do in geoerust/geo.:


Bump deps

So I am really just trying to fix #1193, but it seems like the Glide deps are woefully out of date, so just trying to run a simple make update-glide ends up doing all of this. I think several people have added deps without running update-glide which prunes a lot of code.
This ends up superceding the work in #1180.
Description
Fix #1193 by bumping gonetsh and go-powershell
Release Note
Not clear if we want to have a release note for all the packages that were bumped.

Let's hold for #1195 to be merged first


Consumes Mime-types not getting validated

I have a path with "consumes": ["application/json"] defined. When API is called with "Content-Type: application/json, application/x-www-form-urlencoded" the JSON objects show up as undefined. Is this something which swagger-tools validator middleware should be validating?

Your Content-Type is invalid.  Based on HTTP rfc2613 section 14.17, one content type is provided at a time so what is happening is that when swagger-tools gets your application/json, application-x-www-form-urlencoded, it does not match application/json and so we do not process the value.  You can still use req.swagger.params.{yourParamName}.original to get the original value if you don't want to change your Content-Type.


Warning is not appearing for enums

Hello,
I have an exported component with an exported enum in one file, but I do not get a ESLint warning. But I do get a warning if I add an exported string into file. Shouldn't the enum be highlighted with error as well?

Screenshot

Thanks

Thanks for the report, fixed in 0.4.3!


feat(select): search locale support for  #830

I added toLocaleLowerCase method for the search function of select.
Also created a util method for getting locale. I'm not sure why we are not exporting getLocale from "configureLocalization"

I couldn't link but issue: 830

Also, would you be able to document this behavior in Storybook?
Thanks for your contribution btw

Closed this as completed in #857. If there is something missing, we can open an issue separately. Thank you 🙏 @cenarturkmen


The Recent Autoware Docker Image Compile Autoware.Universe Failed

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
I pulled the latest CUDA image from the Autoware official docker image repository, image tag is universe-devel-cuda-20240921-amd64, and clone the latest autoware code (20240923), I used the following command to start the container and mount the code to the container.
docker run -it --name 20240923_autoware --gpus all --net=host --privileged  -v $HOME/autoware_ws/autoware_20240923:/autoware_20240923 -w /autoware_20240923 -e DISPLAY  -e QT_X11_NO_MITSHM=1 -e NVIDIA_VISIBLE_DEVICES=all -e NVIDIA_DRIVER_CAPABILITIES=all --device=/dev/dri:/dev/dri -v /tmp/.X11-unix:/tmp/.X11-unix e5a5bf46ce7a /bin/bash

The environment information in Docker is as follows:
nvidia-smi

$nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Nov_22_10:17:15_PST_2023
Cuda compilation tools, release 12.3, V12.3.107
Build cuda_12.3.r12.3/compiler.33567101_0

$dpkg -l | grep cudnn
hi  libcudnn8                                         <IP_ADDRESS>-1+cuda12.2                     amd64        cuDNN runtime libraries
ii  ros-humble-cudnn-cmake-module                     0.0.1-3jammy.20240728.201041            amd64        Exports a CMake module to find cuDNN.

$dpkg -l | grep nvinfer
hi  libnvinfer-plugin8                                <IP_ADDRESS>-1+cuda12.0                      amd64        TensorRT plugin libraries
hi  libnvinfer8

When I build packages, the packages related to TensorRT, CUDNN will return：
$colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --continue
Starting >>> tensorrt_common
--- stderr: tensorrt_common
CMake Warning at CMakeLists.txt:19 (message):
  cuda, cudnn, tensorrt libraries are not found

---
Finished <<< tensorrt_common [2.67s]

When I comment on the following part in CMakeLists.txt, and build  tensorrt_common again, get the following error
if(NOT (CUDAToolkit_FOUND AND CUDNN_FOUND AND TENSORRT_FOUND))
  message(WARNING "cuda, cudnn, tensorrt libraries are not found")
  return()
endif()

$colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release --packages-up-to tensorrt_common
Starting >>> tensorrt_common
--- stderr: tensorrt_common
In file included from /autoware_test2409/src/universe/autoware.universe/common/tensorrt_common/src/simple_profiler.cpp:15:
/autoware_test2409/src/universe/autoware.universe/common/tensorrt_common/include/tensorrt_common/simple_profiler.hpp:18:10: fatal error: NvInfer.h: No such file or directory
   18 | #include <NvInfer.h>
      |          ^~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/tensorrt_common.dir/build.make:90: CMakeFiles/tensorrt_common.dir/src/simple_profiler.cpp.o] Error 1
gmake[2]: *** Waiting for unfinished jobs....
In file included from /autoware_test2409/src/universe/autoware.universe/common/tensorrt_common/src/tensorrt_common.cpp:15:
/autoware_test2409/src/universe/autoware.universe/common/tensorrt_common/include/tensorrt_common/tensorrt_common.hpp:22:10: fatal error: NvInfer.h: No such file or directory
   22 | #include <NvInfer.h>
      |          ^~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/tensorrt_common.dir/build.make:76: CMakeFiles/tensorrt_common.dir/src/tensorrt_common.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:137: CMakeFiles/tensorrt_common.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
---
Failed   <<< tensorrt_common [3.00s, exited with code 2]

Expected behavior
All packages can be compiled successfully.
Actual behavior
All packages related to TensorRT and CUDNN cannot be compiled successfully.
Steps to reproduce
none
Versions

OS amd64
ROS2 humble
Autoware 20240923

Possible causes
No response
Additional context
No response

cc: @youtalk
This issue is already reported here: https://github.com/autowarefoundation/autoware/issues/5219
I suggest to use 20240903-devel-cuda image tag before fix release.

@amadeuszsz  Thanks your replay.
I will pull 20240903-devel-cuda image and try build the latest autoware.universe project.
The previous experience was that the old version of the image could not compile successfully the new version code.

@cyn-liu

The previous experience was that the old version of the image could not compile successfully the new version code.

AFAIK there was no core dependency change yet, therefore before colcon build just call rosdep install --from-paths src --ignore-src -y and it should be OK.

20240903-devel-cuda tag image is ok!


Delete tools from pharo 6 and 7 images

Pull Request Test Coverage Report for Build 957

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

Totals

Change from base Build 955:
0.0%

Covered Lines:
7946

Relevant Lines:
7946

💛  - Coveralls


Bump ko version to v0.10.0

It looks like after this PR ko resolve step in our CI became very unstable

@tzununbekov Indeed, the resource usage went over the roof.
I see three options:

Revert (drawback: this is buying us time but doesn't fix the problem)
Reduce ko's build concurrency
Use larger worker nodes in CircleCI

Which one do you prefer?

@antoineco depending on our CircleCI account credits usage I'd first try switching to the beefier node and if it doesn't help, adjust ko's concurrency

@tzununbekov not an option:

I opened https://github.com/google/ko/issues/642 and I'm reverting this PR right now.


Nested binding properties not supported?

Trying to bind a cosmosDb query to an input based on a json payload from event grid
{
"data" : { "username" : "fred" }
…. rest of event grid stuff
}
Can only bind to the outer properties. This is different to the description earlier in the document that talks about using dot notation to bind to nested properties.
Needs to be clarified, or alternatively, have the bug fixed.

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

ID: fa5bcb79-2af8-3b0e-c78c-0c89a2535e15
Version Independent ID: 31b87687-7841-f46f-8c97-38898e7b97db
Content: Azure Cosmos DB bindings for Functions 2.x
Content Source: articles/azure-functions/functions-bindings-cosmosdb-v2.md
Service: azure-functions
GitHub Login: @craigshoemaker
Microsoft Alias: cshoe

Hmm - seems to be the case.
https://github.com/Azure/azure-webjobs-sdk/issues/1726

@piquet-h , Thank you for your feedback. We will investigate and get back to you shortly.

@piquet-h Thanks for the feedback! I believe the underlying issue should be resolves as part of the issue that you've mentioned. In the meantime, I guess a note in the doc should help customers hitting the same issue.
We are assigning this issue to the content author for further review.

@piquet-h Thanks for the feedback! I believe the underlying issue should be resolves as part of the issue that you've mentioned. In the meantime, I guess a note in the doc should help customers hitting the same issue.
If you are using C#, I believe you could use runtime binding to overcome this. This also supported for CSX functions.
We are assigning this issue to the content author for further review.

Instead of C#, is there a solution for javascript? Thanks

@wisesimpson Because of the way non-C# languages work in Azure Functions, runtime binding is not possible.
Alternatives would be

Directly use the native SDKs as required
Send the required data in a queue message (using the output binding) and let this message trigger another function where you can directly use the data as needed

@PramodValavala-MSFT
If I want to build a simple page, triggered by http request and response with some data from cosmos db. Is it still possible to using the second alternative (using queue message)? I don't know if it's possible to carry the http response to the following function?

@wisesimpson You'd want to serve the page statically and have JavaScript make the call to fetch the data as required. You can use patterns like Async HTTP APIs to achieve something like that.

@PramodValavala-MSFT Thanks for your reply. I follow your link and started to create durable functions. Another issue popped up but please forgive me if it's not specific to this topic. Here's the issue:
In the Orchestrator, I called context.df.callActivity("Action1", {"keywords":"test","top":2})
In the "Action1"'s function.json, I added a cosmosDB binding with sqlQuery as SELECT TOP {top} * FROM e WHERE CONTAINS(e.content,{keywords}).
I got error messages "The count value provided for a TOP clause must be an integer.".
I've searched and tried using udf like SELECT TOP udf.toInteger({top}) *...
or built-in function like SELECT TOP StringToNumber({top}) *...
None of them works. Can you help me out? Thanks
ps: The other argument keywords is well received and usable to sqlQuery.

@wisesimpson I believe it would be best to create a thread on MSDN or StackOverflow with your last query, so that the discussion is visible to a larger audience.

#please-close please refer to linked feature request issue https://github.com/Azure/azure-webjobs-sdk/issues/1726