rename ModelResult > ResultStructure to match README schema description

Description
The schema and README refer to a Result Structure but the class in stac-model calls it ModelResult. This updates the name in stac-model for consistency.
Related Issue

Type of Change

[ ] :books: Examples, docs, tutorials or dependencies update;
[ ] :wrench: Bug fix (non-breaking change which fixes an issue);
[ ] :clinking_glasses: Improvement (non-breaking change which improves an existing feature);
[ ] :rocket: New feature (non-breaking change which adds functionality);
[x] :boom: Breaking change (fix or feature that would cause existing functionality to change);
[ ] :closed_lock_with_key: Security fix.

Checklist

[x] I've read the CONTRIBUTING.md guide;
[ ] I've updated the code style using make check;
[ ] I've written tests for all new methods and classes that I created;
[ ] I've written the docstring in Google format for all the methods and classes that I used.

@rbavery If still relevant, rebase against https://github.com/stac-extensions/mlm


variable sourcePrivateKey is not define

https://github.com/XRPLF/xrpl4j/blob/eabbafeb8db092fff845b7f3a5c86a348b14e57c/README.md?plain=1#L210
senderPrivateKey ?
Why
Seed seed = Seed.ed25519Seed(); // <-- Generates a random seed.
Transactions signed with a randomly generated key? What nonsense?

// Construct a Payment
Payment payment = ...; // See V3 ITs for examples.

where to watch it?

Hi @Relect - thanks for your post.

Transactions signed with a randomly generated key? What nonsense?

It's unclear what you're asking here -- in the example you're referencing, a Seed is generated with random entropy, but this is simply for example purposes. Once you have a Seed, you can then construct an in-memory private key deterministically (You can read more about Seeds here).
There are a variety of ways to construct a Seed. You can construct one randomly (as you point out), though that's typically used for testing or examples. You can also construct one from a passphrase, or even from a base58-encoded "secret", such as what you'll get from a testnet faucet. For example, see fromBase58EncodedSecret or ed25519SeedFromPassphrase/secp256k1SeedFromPassphrase.
In general, it's best to not use in-memory private keys, if possible (that functionality is intended to satisfy mobile use-cases). For backend usage, it's best to use something like an HSM or otherwise. For a simulated example of this, see DerivedKeySignatureServiceTest which mocks a service that would do actual signing.

where to watch it?

Can you clarify this question, too? If you want to see an example in action, try running this integration test (SubmitPaymentIT.java) in your IDE and step-through it with a debugger so you can see what it's doing?

In general, it's best to not use in-memory private keys
this is obvious, but in the example given, you might think that transactions are signed each time with a different randomly created private key.
It is not clear where to get the index value for ledger_entry method ;
the index !=  ledger hash.
And how can I get all transactions one block using  method ledger_entry?

Tell me, here I am generating an address and a private key in xrp4j, adding 10 xrp to this address.
What are the guarantees that someone else will not generate a similar address with a different private key and will not be able to manage this address?
Generating addresses is just a matter of having the appropriate power.

What are the guarantees that someone else will not generate a similar address with a different private key and will not be able to manage this address?

The XRPL rAddress is derived from hashing the public key that corresponds to an account's private key. So, there's almost no chance of two people generating the same address (in xrpl4j or otherwise) unless they (1) use the same Seed or (2) rely upon a poor  Entropy generator/instance to then construct a new Seed.
For clarity, this is the chain of data needed for an XRPL address (in xrpl4j, but this roughly mirrors other language libraries):
Randomness --> Entropy.java -> Seed.java -> PrivateKey.java -> PublicKey.java -> AccountId -> rAddress
(The rippled/generic version is described well here).
In the case of xrpl4j, in order to create a new ranomly generated Entropy (to create a random private key), we rely on SecureRandom to ensure good entropy/randomness, and then rely upon that to create a Seed. There are caveats here, so google around for things to consider with SecureRandom and if you don't like what xrpl4j is doing, you can implement your own solution that conforms to the Seed interface).
Keep in mind that Seeds deterministically yield a key-pair, which then yields an address -- so if you create a Seed with poor randomness (e.g., via a Passphrase or poor JVM/system entropy or whatever) then you might have problems.


No color in JSPM 0.17-beta branch

So far can't tell is it solely JSPM issue, or grunt-shell's too.
Ref: https://github.com/jspm/jspm-cli/issues/2068

Fixed in https://github.com/LotusTM/Kotsu/commit/8ed56d330b287d76fc19190da3c8c8b1d0a731e0 by providing FORCE_COLOR=true environment variable.


ECDSA signature verification fails when u1 == 1

coincurve 13.0.0 fails when u1 is equal to 1. You can check this
with the following teste vectors from Google Wycheproof:
{
  "algorithm" : "ECDSA",
  "generatorVersion" : "0.8r12",
  "numberOfTests" : 380,
  "header" : [
    "Test vectors of type EcdsaVerify are meant for the verification",
    "of ASN encoded ECDSA signatures."
  ],
  "notes" : {
    "BER" : "This is a signature with correct values for (r, s) but using some alternative BER encoding instead of DER encoding. Implementations should not accept such signatures to limit signature malleability.",
    "EdgeCase" : "Edge case values such as r=1 and s=0 can lead to forgeries if the ECDSA implementation does not check boundaries and computes s^(-1)==0.",
    "MissingZero" : "Some implementations of ECDSA and DSA incorrectly encode r and s by not including leading zeros in the ASN encoding of integers when necessary. Hence, some implementations (e.g. jdk) allow signatures with incorrect ASN encodings assuming that the signature is otherwise valid.",
    "PointDuplication" : "Some implementations of ECDSA do not handle duplication and points at infinity correctly. This is a test vector that has been specially crafted to check for such an omission."
  },
  "schema" : "ecdsa_verify_schema.json",
  "testGroups" : [
    {
      "key" : {
        "curve" : "secp256k1",
        "keySize" : 256,
        "type" : "EcPublicKey",
        "uncompressed" : "04feb5163b0ece30ff3e03c7d55c4380fa2fa81ee2c0354942ff6f08c99d0cd82ce87de05ee1bda089d3e4e248fa0f721102acfffdf50e654be281433999df897e",
        "wx" : "00feb5163b0ece30ff3e03c7d55c4380fa2fa81ee2c0354942ff6f08c99d0cd82c",
        "wy" : "00e87de05ee1bda089d3e4e248fa0f721102acfffdf50e654be281433999df897e"
      },
      "keyDer" : "3056301006072a8648ce3d020106052b8104000a03420004feb5163b0ece30ff3e03c7d55c4380fa2fa81ee2c0354942ff6f08c99d0cd82ce87de05ee1bda089d3e4e248fa0f721102acfffdf50e654be281433999df897e",
      "keyPem" : "-----BEGIN PUBLIC KEY-----\nMFYwEAYHKoZIzj0CAQYFK4EEAAoDQgAE/rUWOw7OMP8+A8fVXEOA+i+oHuLANUlC\n/28IyZ0M2CzofeBe4b2gidPk4kj6D3IRAqz//fUOZUvigUM5md+Jfg==\n-----END PUBLIC KEY-----",
      "sha" : "SHA-256",
      "type" : "EcdsaVerify",
      "tests" : [
        {
          "tcId" : 306,
          "comment" : "u1 == 1",
          "msg" : "313233343030",
          "sig" : "3045022055555555555555555555555555555554e8e4f44ce51835693ff0ca2ef01215b8022100bb5a52f42f9c9261ed4361f59422a1e30036e7c32b270c8807a419feca605023",
          "result" : "valid",
          "flags" : []
        }
      ]
    }
  ]
}

and proof of concept:
from coincurve.keys import PrivateKey, PublicKey
from coincurve.utils import bytes_to_int, int_to_bytes_padded, verify_signature

from cryptography import exceptions
from cryptography.hazmat.backends import default_backend
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives.asymmetric import ec
from cryptography.hazmat.primitives.asymmetric import utils

from hashlib import sha256

#  u1 = (h(m) * w) mod n

import json

def main():

    with open("ecdsa_secp256k1_sha256_test_u1.json", "r") as read_file:
        secp256k1_sha256_test = json.load(read_file)

    for test_group in secp256k1_sha256_test["testGroups"]:
        comp_str = test_group["key"]["uncompressed"]
        co_x = test_group["key"]["wx"]
        co_y = test_group["key"]["wy"]

        public_key = PublicKey(bytes.fromhex(comp_str))

        for test in test_group["tests"]:
            print("Loading test", test["tcId"], "with result:", test["result"], "\n")

            ### using python coincurve

            signature = bytes.fromhex(test["sig"])
            message = bytes.fromhex(test["msg"])
            print("\tcoincurve: ", public_key.verify(signature, message))

            ### using python cryptography

            curve = ec.SECP256K1()
            algo = ec.ECDSA(hashes.SHA256())

            pubnum = ec.EllipticCurvePublicNumbers(int(co_x, 16), int(co_y, 16), curve)

            data = bytes(bytearray.fromhex(test["msg"]))
            public_key_2 = pubnum.public_key(default_backend())
            signature = bytes(bytearray.fromhex(test["sig"]))

            try:
                public_key_2.verify(signature, data, ec.ECDSA(hashes.SHA256()))

            except exceptions.InvalidSignature:
                print("\tcryptography.io: False")
            else:
                print("\tcryptography.io: True")

if __name__ == "__main__":
    main()

where I compare the output of coincurve with the python cryptography
library.

@adelapie Thanks for opening all of these issues!!! Have you found a fix? I'm pretty sure these would be better directed at libsecp256k1 since we are just wrapping that.
cc @gmaxwell @jonasnick @real-or-random Any thoughts?

They pointed me to the restrictions on ECDSA https://github.com/google/wycheproof/issues/70 I think the issues can be closed then

Okay, thanks again!


EntityManager injection broken >5.1.2 with custom factory using PinoLogger and built via ncc

Describe the bug
EntityManager (MongoEntityManager) dependency injection cannot be resolved when using @mikro-orm/nestjs >5.1.2 with .forRootAsync and PinoLogger. It works fine without injecting the logger into custom useFactory. Happens only when executing built code.
Stack trace
$ node ./dist/index.js
[Nest] 28664  - 07/18/2023, 11:02:59 AM     LOG [NestFactory] Starting Nest application...
[Nest] 28664  - 07/18/2023, 11:02:59 AM     LOG [InstanceLoader] AppModule dependencies initialized +97ms
[Nest] 28664  - 07/18/2023, 11:02:59 AM     LOG [InstanceLoader] MikroOrmModule dependencies initialized +0ms
[Nest] 28664  - 07/18/2023, 11:02:59 AM   ERROR [ExceptionHandler] Nest can't resolve dependencies of the MongoService (?). Please make sure that the argument MongoEntityManager at index [0] is available in the MongoModule context.

Potential solutions:
- Is MongoModule a valid NestJS module?
- If MongoEntityManager is a provider, is it part of the current MongoModule?
- If MongoEntityManager is exported from a separate @Module, is that module imported within MongoModule?
  @Module({
    imports: [ /* the Module containing MongoEntityManager */ ]
  })

Error: Nest can't resolve dependencies of the MongoService (?). Please make sure that the argument MongoEntityManager at index [0] is available in the MongoModule context.

Potential solutions:
- Is MongoModule a valid NestJS module?
- If MongoEntityManager is a provider, is it part of the current MongoModule?
- If MongoEntityManager is exported from a separate @Module, is that module imported within MongoModule?
  @Module({
    imports: [ /* the Module containing MongoEntityManager */ ]
  })

    at Injector.lookupComponentInParentModules (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:254:1)
    at Injector.resolveComponentInstance (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:207:1)
    at resolveParam (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:128:1)
    at async Promise.all (index 0)
    at Injector.resolveConstructorParams (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:143:1)
    at Injector.loadInstance (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:70:1)
    at Injector.loadProvider (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/injector.js:97:1)
    at /Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/instance-loader.js:56:1
    at async Promise.all (index 3)
    at InstanceLoader.createInstancesOfProviders (/Users/akieltyka/RubymineProjects/DeepCrawl/mikro-orm-nestjs-bug/webpack:/mikro-orm-nestjs-bug/node_modules/@nestjs/core/injector/instance-loader.js:55:1)
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

To Reproduce
package.json
{
  "name": "mikro-orm-nestjs-bug",
  "version": "1.0.0",
  "main": "index.js",
  "license": "MIT",
  "scripts": {
    "compile": "tsc",
    "build": "ncc build --out dist --source-map ./reproduction.ts",
    "run:ts-node": "yarn ts-node ./reproduction.ts",
    "run:built": "node ./dist/index.js"
  },
  "resolutions": {
    "mongodb": "4.1.4"
  },
  "dependencies": {
    "@mikro-orm/core": "5.7.13",
    "@mikro-orm/mongodb": "5.7.13",
    "@mikro-orm/nestjs": "5.2.0",
    "@nestjs/common": "10.1.0",
    "@nestjs/config": "3.0.0",
    "@nestjs/core": "10.1.0",
    "nestjs-pino": "3.3.0",
    "pino-http": "8.3.3",
    "reflect-metadata": "0.1.13",
    "source-map-support": "0.5.21",
    "tslib": "2.6.0"
  },
  "devDependencies": {
    "@nestjs/cli": "10.1.4",
    "@nestjs/schematics": "10.0.1",
    "@nestjs/testing": "10.0.5",
    "@types/node": "18.16.19",
    "@vercel/ncc": "0.36.1",
    "ts-node": "10.9.1",
    "typescript": "5.1.6"
  }
}

tsconfig.json
{
  "compilerOptions": {
    "target": "es2021",
    "lib": ["es2021"],
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "module": "commonjs",
    "esModuleInterop": true,
    "forceConsistentCasingInFileNames": true,
    "strict": true,
    "skipLibCheck": true
  }
}

reproduction.ts
import "reflect-metadata";

import { BaseEntity, Entity, PrimaryKey, SerializedPrimaryKey } from "@mikro-orm/core";
import { EntityManager, ObjectId } from "@mikro-orm/mongodb";
import { MikroOrmModule } from "@mikro-orm/nestjs";
import { INestApplicationContext, Injectable, Module, Scope } from "@nestjs/common";
import { NestFactory } from "@nestjs/core";
import { LoggerModule, PinoLogger } from "nestjs-pino";

@Entity({ collection: "entities" })
export class MongoEntity extends BaseEntity<MongoEntity, "id"> {
  @PrimaryKey()
  public _id!: ObjectId;

  @SerializedPrimaryKey()
  public id!: string;
}

@Injectable({ scope: Scope.TRANSIENT })
export class MongoService {
  private entityManager: EntityManager;

  constructor(entityManager: EntityManager) {
    this.entityManager = entityManager.fork();
  }
}

@Module({ providers: [MongoService] })
export class MongoModule {}

@Module({
  imports: [
    LoggerModule.forRoot(),
    MikroOrmModule.forRootAsync({
      inject: [PinoLogger],
      useFactory: (logger: PinoLogger) => {
        logger.setContext("MikroOrm");

        return {
          type: "mongo",
          clientUrl: "mongodb://<IP_ADDRESS>:27017/dbName", // run a local dockerized MongoDB v3 instance
          dbName: "dbName",
          entities: [MongoEntity],
          debug: ["query"], // Log all queries
          logger: message => logger.info(message),
        };
      },
    }),
    MongoModule,
  ],
})
class AppModule {}

let applicationContext: INestApplicationContext;

if (require.main === module) {
  (async () => {
    applicationContext = await NestFactory.createApplicationContext(AppModule);
    applicationContext = await applicationContext.init();
    await applicationContext.resolve(MongoService);
    await applicationContext.close();
    process.exit(0)
  })().catch(async error => {
    await applicationContext?.close();
    throw error;
  });
}

yarn install
yarn build
yarn run:built

Expected behavior
I expect the EntityManager to get injected correctly and work as it was working before in version 5.1.2.
Additional context
The error happens only when running a built .js file. It does not occur when running .ts file via ts-node. The mongodb dependency is locked to version 4.1.4 because of an old MongoDB v3 instance that needs to be connected to.
Versions

Dependency
Version

node
18.16.1

typescript
5.1.6

mikro-orm
5.7.13

mongodb
4.1.4

Can you please provide a complete repro as a GH repository?
Have you tried it without ncc? Could be some issue in there rather than here, since things seem to be working fine with regular tsc build on my end.

constructor(entityManager: EntityManager) {
this.entityManager = entityManager.fork();
}

This is a pretty bad idea, you are just getting around the validation, but still using a single global EM fork. This will almost certainly have unwanted side effects.

The reproduction above is complete (package.json, tsconfig.json, reproduction.ts). You'd find nothing more in a repository. The only thing that can be added is any MongoDB v3 instance which can be easily created via Docker:
docker-compose.yml
version: "3.7"
services:
  db-mongo:
    image: "public.ecr.aws/docker/library/mongo:3"
    healthcheck:
      test: ["CMD-SHELL", 'mongo --eval ''db.runCommand("ping").ok'' localhost:27017/test --quiet']
      interval: 10s
      timeout: 2s
      retries: 10
    ports:
      - "27017:27017"

If the version 5.1.2 works fine with ncc and any version above does not, then I'm inclined to say some change here may be at fault.
This reproduction merely shows the error and how to cause it. It does not show the actual business use case which is AWS EventBridgeEvent lambda that gets/resolves various services using cached and initialized application context assigned to let.

The reproduction above is complete (package.json, tsconfig.json, reproduction.ts). You'd find nothing more in a repository. The only thing that can be added is any MongoDB v3 instance which can be easily created via Docker:

I am asking because I want to spare my time, as I have a huge amount of other issues I need to review these days. I don't want to copy past things and create files.
Sounds like you value your time more than mine. That's fine, but don't expect me to also put more value on yours...

https://github.com/AndKiel/mikro-orm-nestjs-issue-128

Thanks!
Maybe this one is related? https://github.com/vercel/ncc/issues/776

Doesn't seem related. I have no issues with decorators in different projects using exactly the same ncc version and other dependencies but with sequelize instead mikro-orm. And @mikro-orm/nestjs v5.1.2 worked fine before.

You keep talking about @mikro-orm/nestjs v5.1.2, but this package hasn't been released for quite some time, so I guess you mean the ORM packages, not the nest adapter?

No, I mean exactly what I said above and I wrote the same in the issue description. @mikro-orm/nestjs v5.1.2 works. Upgrading to a higher version breaks built code execution.

Oh ok, so the problem is in this package. I was suspecting some changes I did in v5.7.13 released a few days ago. Will try to look into this later this week.

It appears that the issue is that it is calling the useFactory method without actually injecting any of the injected values.  I ran into this with the config service not being injected after updating.  I am not sure why it broke only on 5.7.13 (for me).

I've added an alternative reproduction to the reproduction repository - one using InjectRepository instead of EntityManager. This variant throws the error even when using ts-node to execute the file.

constructor(entityManager: EntityManager) {
this.entityManager = entityManager.fork();
}

This is a pretty bad idea, you are just getting around the validation, but still using a single global EM fork. This will almost certainly have unwanted side effects.

Regarding this, what would be the proper way of doing things for applications using NestFactory.createApplicationContext? What I mean is for example EventBridgeEvent lambdas where there are no HTTP requests so there is also no request context. This manual forking was my "workaround" because with InjectRepository it threw ValidationError. Is passing the scope property to the forRootAsync the proper way?

Is passing the scope property to the forRootAsync the proper way?

I am not sure if that would help, it controls the nestjs DI scopes, and since there are no requests, I'd expect there won't be any request context in the DI either, but maybe I am wrong, haven't used nest in a long time.
You could create the context explicitly via RequestContext.createAsync() or use the @UseRequestContext decorator.
https://mikro-orm.io/docs/usage-with-nestjs#request-scoped-handlers-in-queues

The second test is missing forFeature call, which registers the repositories to the DI. If you import that in the MongoModule where you are using it, then it starts to work (including the built version).
@Module({
  providers: [MongoService],
  imports: [
    MikroOrmModule.forFeature([MongoEntity]),
  ],
})
export class MongoModule {}

Ah, you're right, silly mistake.
I fiddled with scope a bit and found out that:

If scope is not passed, using the repository throws ValidationError. More or less expected because there is no request scope as mentioned in previous comments.
If scope is passed:

applicationContext.get works but repository becomes undefined (it's not injected) and .resolve must be used instead. This seems like a bug.
Each resolved MongoService instance gets EntityManager with _id incremented by 1. This seems correct and wanted behaviour so that application behaves as if there was a request context even if there isn't one.

It seems to be working fine both with ts-node and with code built via ncc. Maybe usage with NestFactory.createApplicationContext should be documented somehow if the above is how it's supposed to work.
Now, should the initial reproduction be considered an actual bug or an incorrect usage due to the above?

The thing is I am not completely sure how it is supposed to be working in nest di, it's been years since I used it in an actual project (same for any web app, I no longer develop those). I checked how the official nest/typeorm adapter registers things, and it feels pretty much the same as we do here, especially when it comes to exports field.

It seems to be working fine both with ts-node and with code built via ncc. Maybe usage with NestFactory.createApplicationContext should be documented somehow if the above is how it's supposed to work.

That's good news, could you PR that somewhere? e.g. the readme here, I can propagate it to mikro-orm.io myself.

For example, if I make the whole MongoService in my reproduction have a scope but skip it in MikroOrmModule.forRootAsync, then I still get ValidationError when using the repository. As if injection ignored the fact that the whole service is scoped.

I am more than sure you need to use the scope option of the forRoot call, otherwise the services are registered as singletons, its not relevant that your MongoService (which is a leaf, not a dependency of those) is request scoped - you don't import that into the ORM services, so they don't have to he request scoped at all.


Array.concat() is missing overload for non-Array arguments

TypeScript Version:  Nightly

Search Terms:
Array.concat
Expected behavior:
Code sample should not be marked as erroneous, since non-Array arguments are valid.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/concat#Description
Actual behavior:
Code compiles, but argument in code sample is marked erroneous:
No overload matches this call.
  Overload 1 of 2, '(...items: ConcatArray<never>[]): never[]', gave the following error.
    Argument of type '"foo"' is not assignable to parameter of type 'ConcatArray<never>'.
  Overload 2 of 2, '(...items: ConcatArray<never>[]): never[]', gave the following error.
    Argument of type '"foo"' is not assignable to parameter of type 'ConcatArray<never>'.(2769)

Related Issues:
Some loosely related, but none that covers the problem at hand.
Code
[].concat('foo')

Output
"use strict";
[].concat('foo');

Compiler Options
{
  "compilerOptions": {
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "strictPropertyInitialization": true,
    "strictBindCallApply": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "useDefineForClassFields": false,
    "alwaysStrict": true,
    "allowUnreachableCode": false,
    "allowUnusedLabels": false,
    "downlevelIteration": false,
    "noEmitHelpers": false,
    "noLib": false,
    "noStrictGenericChecks": false,
    "noUnusedLocals": false,
    "noUnusedParameters": false,
    "esModuleInterop": true,
    "preserveConstEnums": false,
    "removeComments": false,
    "skipLibCheck": false,
    "checkJs": false,
    "allowJs": false,
    "declaration": true,
    "experimentalDecorators": false,
    "emitDecoratorMetadata": false,
    "target": "ES2017",
    "module": "ESNext"
  }
}

Playground Link: Provided

Bogus report, adding a type declaration resolves the issue.
([] as string[]).concat('foo')

Still valid as of today!

Still not fixed

Still not fixed

@willydee would you mind to re-open the issue.
The fact that there is a workaround does not make it resolved.

@seelts no because it was indeed a bogus report. By instantiating an empty array without explicit type annotation, an array of never is inferred. And a string cannot be added to the inferred array type. The compiler error message is revealing the problem when it is read and understood by the developer — which I obviously didn't back in the day. My closing comment is not a workaround but the correction of my preceding misunderstanding.


Builds tab suggestions

First thing, I want to thank you for this great tool, really helpful.
The "builds" tab is good, but it would be even better if there was an option for Loading the build (and not just send it to the chat).
Another option that can be nice is to organize the builds with categories (Such as "Fowsc", Doasc", "dungeons"... etc).
What do you think?

Thanks.
I'll see if I can add a build to load a build.
I'd say no to groups, as it would need a change in how the existing builds are saved. I suggest to use empty builds and just put some name like ==== FoW ==== as separators

implemented loading in https://github.com/HasKha/GWToolboxpp/commit/9393dfa5c635165bba272741898789ce11e940d0


Let other variables use $HOME variable instead of requiring to rewrit…

…e all of them when only $HOME is different

This doesn't work... But neither does the original variant...


16 UNAUTHENTICATED in nodejs server

I get the following error at random in my nodejs server It doesn't happen when in my local environment.
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Environment details

OS: Linux
Node.js version: 12.x
@google-cloud/firestore version: ^4.9.2

Code
class FirestoreService {
  private static firestore: Firestore;

  constructor() {
    if (!FirestoreService.firestore) {
      FirestoreService.firestore = new Firestore({
        projectId: process.env.FIREBASE_PROJECT_ID,
        credentials: { client_email: process.env.FIREBASE_CLIENT_EMAIL, private_key: process.env.FIREBASE_PRIVATE_KEY },
        ssl: true,
        maxIdleChannels: 2,
      });
    }
  }
}

Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Are you able to use keyFilename and directly point to a the service-account.json file you downloaded from the Console? See https://github.com/googleapis/nodejs-firestore/blob/ab057f7b362a2929ebffa19e570d3e9cd23bc964/types/firestore.d.ts#L130
What you have should work, but it does have a higher likelihood of introducing misconfigurations and unfortunately, we cannot debug them here since we would need access to your credentials.
If keyFilename does not solve your issue, please file a support request. We can then take a look at the permissions associated with your service account: https://cloud.google.com/support-hub


[UPDATE] Adding code to store logs

Description

TESTING STAGE

Types of changes

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

Checklist:

[ ] I have read CONTRIBUTING.md
[ ] I fully understand Github Flow.
[ ] My code adheres to the code style of this project.
[ ] I have updated the documentation in /docs if I have changed the config, arguments, logic in how the bot works, or anything that understandably needs a documentation change.
[ ] I have updated the config file accordingly if my change requires a new configuration setting or changes an existing one.
[ ] I have tested the bot with no issues for 24 continuous hours. If issues were experienced, they have been patched and tested again.

@utdrmac can you maybe clarify how should you use journalctl to view the bots log in the service scenario? (I have to admit Unix isn't my domain) maybe add that to the docs?

Since systemd became process 1 in all major linux operating systems, things like auto-restarting crashed applications, handling logs, rotating logs, etc, all of that is built-in to systemd. You simply launch your application and systemd does the rest. You don't need to code in external logging logic. Just print everything to stdout and systemd captures it all automatically and sends it to journald. You can view the logs like journalctl -u lendingbot

vinnfs's patch is essentially redirecting stdout and stderr away from systemd capture, and sending to a separate file. It's a simple solution to have ONLY the lendingbot logs in a separate file. You can get the same exact info by letting systemd handle it and use the journactl command to view the logs, albeit learning how to properly use journalctl.

Thanks @utdrmac!


Compatibility with native Leaflet fitBounds() or flyToBounds()

I've been using this plugin to manage active map area, however it seems to disrupt native Leaflet funcs fitBounds and flyToBounds.
When using either func alongside this plugin, the map zooms out all the way (entire world). Disabling usage of this plugin, the two funcs work as expected. Both have padding options (which I don't recall seeing in the past) which I'm going to explore now to manually manage active area.
I don't have a readily available demo (yet), but I'm interested to hear initial thoughts on this.
For the time being I'm disabling this plugin and going further with Leaflet's native capabilities.

I spoke too soon; issue is my own logic.


Required ports and addresses for AKS clusters should list UDP:123 in the summary

In the section titled "Required ports and addresses for AKS clusters" the summary bullet list at the top should include opening port 123 for NTP traffic. It's listed in the details below, just missing from the summary.

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

ID: a38439d0-0125-3445-1c0a-a03b940e315d
Version Independent ID: c6436a35-94b9-6396-3b13-9291f0a17b21
Content: Restrict egress traffic in Azure Kubernetes Service (AKS)
Content Source: articles/aks/limit-egress-traffic.md
Service: container-service
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

Thanks for the feedback! We are currently investigating and will update you shortly.

@doug-fish
Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

I am not fully convinced that info provided is correct. For instance, how can UDP association be made with a FQDN? e.g. ntp.ubuntu.com | UDP:123 as mentioned in the page.


top-level/python-packages: add zip support to fetchPypi

Motivation for this change
Currently, fetchPypi only supports tar.gz source distributions. This commit adds support for zip source distribution which can be enabled by passing tgz = false; to fetchPypi. Tested with 3to2 and fonttools (both packages with new versions only available in zipped form).
@FRidh fetchPypi only supporting sha256 checksums seems weird, is there any reason for that?
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Because there are still older archives out there that use other extensions, like bz2, I suggest having an extension ? "tar.gz" instead.

@FRidh fetchPypi only supporting sha256 checksums seems weird, is there any reason for that?

Because that is what https://pypi.org/ offers. But restricting to that is not necessary though.

fixed.

Thanks. I pushed https://github.com/NixOS/nixpkgs/commit/65477dcd341dcdcdc58b01e362e18a903bf94874.


Error is produced when RubyTerraform.configure is not run

When I don't run RubyTerraform.configure in the beginning the first invocation fails with the following error:
     NoMethodError:
       undefined method `binary' for nil:NilClass
     # ./vendor/bundle/ruby/2.0.0/gems/ruby-terraform-0.5.0/lib/ruby_terraform/commands/base.rb:9:in `initialize'
     # ./vendor/bundle/ruby/2.0.0/gems/ruby-terraform-0.5.0/lib/ruby_terraform.rb:24:in `new'
     # ./vendor/bundle/ruby/2.0.0/gems/ruby-terraform-0.5.0/lib/ruby_terraform.rb:24:in `get'
     # ./spec/main_spec.rb:5:in `block (2 levels) in <top (required)>'

This happens because @configuration is set by running RubyTerraform.configure and before that it is still nil.
If I add the following snippet at the top of the file all works like expected:
RubyTerraform.configure {}

Thanks for the detailed issue - I'll take a look now.

Ok, I just release 0.5.1 which resolves this issue.
I'll close this issue now but feel free to reopen if you are still having problems.

Seems to work fine for me, thank you for the quick fixing!


Add the ability for OperationalSessionSetup to retry a few times automatically.

The basic idea is that if CASE establishment fails we try again, after a brief backoff.

@g-coppock


Finalizing V1

Codecov Report

Merging #5 (d76a7d7) into main (847fc0a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   66.07%   66.07%
=======================================
  Files           8        8
  Lines          56       56
  Branches        8        8
=======================================
  Hits           37       37
  Misses         19       19

Continue to review full report at Codecov.

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


Debugging Javascript on Windows

This is an awesome tool ... thanks for sharing.
I thought you might want to include a reference to this tool which can be used for debugging your web pages on Windows.
https://docs.microsoft.com/en-us/office/dev/add-ins/testing/debug-add-ins-using-f12-developer-tools-on-windows-10

Sorry, I will probably close this.
I admit that debugging tools are much needed. As soon as we resolve #85 and get Edge up and running - this issue is likely to be resolved as well. But with MSHTML there is no easy way to do debugging except for the old Firebug (as mentioned in the readme).


Hyperparameters for 48K sample rate dataset.

Hello,
Has anyone tried this repo with 48K sample rate dataset?
I am training English(Indian accent) dataset which has 48000-16bit-Mono sample rate wave files. I have modified the following hyperparameters for the dataset in hparams.py

modified hyperparameters in hparams.py
use_all_gpus = True,  #False
num_gpus = 8,  #1
num_freq = 1201, #513 ()
use_lws=False, #True
#Mel spectrogram
n_fft = 2400, #Extra window size is filled with 0 paddings to match this parameter
hop_size = 600, # For 48000, 600~=12.5ms, For 22050Hz, 275 ~= 12.5 ms
win_size = 2400, # For 48000, 2400 ~= 50ms, For 22050Hz, 1100 ~= 50 ms (If None, win_size = n_fft)
sample_rate = 48000, #48000(my dataset), 22050 Hz (corresponding to ljspeech dataset)
frame_shift_ms = None,
outputs_per_step = 1,
prenet_layers = [128, 128], #number of layers and number of units of prenet
decoder_layers = 2, #number of decoder lstm layers
decoder_lstm_units = 512, #number of decoder lstm units on each layer
max_iters = 2500, #Max decoder steps during inference (Just for safety from infinite loop cases)
mask_encoder = False, #whether to mask encoder padding while computing attention
mask_decoder = False, #Whether to use loss mask for padded sequences
predict_linear = True, #Whether to add a post-processing network to the Tacotron to predict linear spectrograms (True mode Not tested!!)
tacotron_batch_size = 16, #number of training samples on each training steps

After 25K steps of training, the loss is at 0.75474, and the alignment plot is like this

The mel-spectrogram is like this

To me the mel-spectrogram looks fine. The audio samples are fine but robo voice. The alignment plot seems different than others seen in this repo? What's wrong in alignment plot?
Regards,
SRHyd

I am not sure 48KHz is OK for Tacotron or not. I suggest you can transfer all you wav files into 22050KHz by FFmpeg and try again. For me 16KHz is all right.
Your hyper parameter seems no question except that the n_fft is not power of 2. I am not sure this would be a problem. So please try resampling into 22050KHz. If it still fails to convergence, then there might be problems in your transcript symbols.

@begeekmyfriend,  Thanks for reaching out. I will try with the sample_rate=16000, and param as below
nfft = 1024
hop_size = 256,
win_size = 1024,
sample_rate = 16000,
frame_shift_ms = None,
trim params
trim_fft_size = 512,
trim_hop_size = 128,
outputs_per_step = 1,
Also,  I want to use LWS for faster inversion of the spectrogram. I will not be using the wavenet vocoder.
use_lws=True # Does not work if n_ffit is not multiple of hop_size!!'
Will it work?
Why is it required to transfer all wave file to 16000KHz? I think the resampling is done by default in audio.py during the preprocessing. (Please refer to audio.py in line 10,  librosa.core.load(path, sr=sr).

try set outputs_per_step =3, where encoder steps is close to decode step

Thank you @azraelkuan.
I have changed outputs_per_step=3, now I am getting the alignment after 6K steps.

Hello, bigger "outputs_per_step" indeed makes alignments easier, but your batch size was small that was the problem. Also if you want to use 48kHz, you should the following parameters.
num_freq = 2049, # (= n_fft / 2 + 1) only used when adding linear spectrograms post processing network

#Mel spectrogram
n_fft = 4096, #Extra window size is filled with 0 paddings to match this parameter
hop_size = 600, #For 22050Hz, 275 ~= 12.5 ms
win_size = 2400, #For 22050Hz, 1100 ~= 50 ms (If None, win_size = n_fft)
sample_rate = 48000, #22050 Hz (corresponding to ljspeech dataset)
frame_shift_ms = None,
This keeps consistency with the 12.5ms 50ms window and shift. You can also set n_fft = 2400 and num_freq=1201. There's no problem with that as well.
Closing the issue, feel free to reopen if there is anything else :)


EF core's new features of batch insert do not take effect on Postgres

when i test with sqlserver by insert many columns once, the sqlserver profiler catch one sql like "insert into table values('xx'),('xx')" , but postgresql side : it execute "insert into table values('xx')" Many times

@humanww hmm, I'll take a look - but as surprising as it seems there's a good chance that sending many INSERTs is actually more efficient then sending a single one here... First, the INSERT statements are batched into a single roundtrip - you should be able to see this with wireshark. And doing each insert in a separate statement allows Npgsql to prepare the statement and reuse it N times (assuming autoprepare is on). Of course this needs to be benchmarked properly.

Thank you for your reply


µmamba: no version string

While reporting #386 I noted that µmamba does not appear to show any version string.
--version, -V, etc. options don't exist.
Something along those lines might be useful for future bug reports :slightly_smiling_face:

Thanks for the bug report. Indeed, I just recently added the necessary magic to copy the version number from _version.py to version.hpp.in so that we'll have it available in the full-C++ build.
https://github.com/TheSnakePit/mamba/blob/master/src/version.cpp
If you wanted to it should be quite straight forward to make a PR that adds this functionality to main.cpp:
https://github.com/TheSnakePit/mamba/blob/master/src/main.cpp


Capped global recipient set and global max float

The latest iteration of the PM candidate construction described in #15 involves the following:

Os define their personal maxFloat values. An O will accept winning tickets with a cumulative value up to maxFloat before redeeming all the winning tickets on-chain
Bs commit to a recipient set by submitting a Merkle root on-chain
B's reserve should be equal to the maxFloat values of all of its committed Os
If B exhausts its deposit, a committed O can draw on B's reserve up to maxFloat. Thus, a committed O is always guaranteed at least maxFloat. As long as O does not hold on to winning tickets past that value before redeeming, O does not risk losing money

The biggest downside of this construction is the requirement for B to commit to a recipient set - this means that whenever B wants to add a new recipient or remove a recipient it would need to submit an on-chain transaction.
An alternative to consider is to remove recipient set commitments and instead to allow B to work with all members of a capped O set. There would also be a globally defined maxFloat value. B's required reserve would then be calculated as size of O set * maxFloat.
However, while B would not need to update its recipient set, it would still have to increase its reserve whenever the size of the O set increases. To avoid this, B can set its reserve as max size of O set * maxFloat. The downside here is that B's reserve requirement might not reflect the actual number of Os if the size of the O set is less than the max size i.e. B is basically over collateralized. Furthermore, this only works if the max size of the O set is known i.e. it would only work if there was a fixed # of Os on the network

While transcoding pricing will vary depending on the orchestrator, we can try to use a fixed transcoding price that represents an overestimate of what the actual costs of the network might be to help decide on appropriate values for the global max # of Os and the global max float.
For the purposes of this discussion let's refer to example 5 presented in the AWS Elastic Transcoding docs. In this example, a source file is being transcoded into 3 SD outputs and 2 HD outputs in US West (N. California).
The price for an hour long stream would be: (3 * 60 * .017) + (2 * 60 * .034) = 7.14
With 2 second segments, the price per segment (for simplicity let's assume we are paying per segment) would be: 7.14 / 30 = .238.
Let the gas cost of an on-chain winning ticket redemption be 100000. In practice, we might be able to optimize the implementation to lower gas costs, but 100000 should be a safe overestimate for this discussion.
Given the gas cost of an on-chain winning ticket redemption, we can compute the transaction cost (denominated in both ETH and USD) at varying gas prices.

GP = 2 gwei
GP = 5 gwei
GP = 10 gwei
GP = 20 gwei
GP = 30 gwei

ETH Cost
.0002
.0005
.001
.002
.003

USD Cost (ETH/USD = 150)
.03
.075
.15
.3
.45

We will use the transaction cost for a gas price of 20 gwei to reflect that an O could calculate its required ticket face value so that redeeming winning tickets can be profitable even when gas prices rise from 2 gwei to 20 gwei.
The ticket face value should compensate an O for all non-winning tickets received. So, we can calculate the face value as: (pricePerSegment / winProb) + transactionCost. Let's say winProb = .2. Then, we have: faceValue = (.238 / .2) + .3 = 1.09333.
We can multiply the face value by 3 (a lower value means O has to redeem more often, a higher value increases B reserve requirements - other than these considerations this value is arbitrarily selected) to get the max float value: 1.09333 * 3 = 3.28.
Now, suppose that the max number of Os is 100. Then, B's reserve requirement is 100 * 3.28 = 328

The previous comment set winProb = .2 which was an arbitrary value. In practice, this value is unrealistic for a few reasons:

On average, it would result in a winning ticket every 10 seconds which is too frequent
It would result in a high % payment overhead. With transactionCost = .3 and faceValue = .31983333, the % payment overhead would be .3 / .31983333 = .937988545. The transaction cost represents ~93% of the winning ticket face value! This is a non-starter.

Find below some data that is a bit more realistic:
# Send a ticket every segmentsPerTicket segments
segmentsPerTicket = 3
# Desired payment for segmentsPerTicket segments
# The base cost per segment represents 50% of the AWS cost referenced in the previous comment
desiredPayment = (.003966667 / 2) * 3 = .00595
# The float per recipient will represent faceValueMultiplier times the ticket face value
faceValueMultiplier = 2
# The winning probability of a ticket targets a winning ticket every 4 hours
winProb = 1 / (4 * (3600 / (2 * 3)) = .000416667

With a 20 gwei gas price:
transactionCost = .24
faceValue = (.00595 / .000416667) + .24 = 14.52
float = 2 * 14.52 = 29.04
reserve = 100 * 29.04 = 2904
paymentOverhead = .24 / 14.52 = .016

With a 30 gwei gas price:
transactionCost = .36
faceValue = (.00595 / .000416667) + .36 = 14.64
float = 2 * 14.64 = 29.28
reserve = 100 * 29.28 = 2928
paymentOverhead = .36 / 14.64 = .024

With a 50 gwei gas price:
transactionCost = .6
faceValue = (.00595 / .000416667) + .36 = 14.88
float = 2 * 14.88 = 29.76
reserve = 100 * 29.76 = 2976
paymentOverhead = .6 / 14.88 = .04

With a 100 gwei gas price:
transactionCost = 1.2
faceValue = (.00595 / .000416667) + 1.2 = 15.48
float = 2 * 15.48 = 30.96
reserve = 100 * 30.96 = 3096
paymentOverhead = 1.2 / 15.48 = .077


how i get service worker id ?

i want use snowflake  algorithm ，but it need set worker id,how i get it?
snowflake:
+------------------------+--------------------------+-----------------+
| 43bits timestamp in ms | 8bits worker(machine) ID | 12bits sequence |
+------------------------+--------------------------+-----------------+

I'm not sure how this is relevant to micro. What would constitute a service worker Id? You can get the Id of the server itself from options.
service.Server().Options().Id


Feature 5197 - Generalizing Docker Configurations

Description

Adds additional configuration options for run_docker.sh to allow for either mounting or copying local files
Related Issue

#5197
Motivation and Context

Ease of use, especially w.r.t. having a locally-available PythonNet and Mono install without restrictions.
Requires Documentation Change

No
How Has This Been Tested?

TBD
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[ ] My code follows the code style of this project.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Thanks @aarjaneiro we're migrating to a lean pip package and will deprecate these runners to have a 1) standard well documented, 2) cross-platform, 3) complete solution.


Ha nginx controller updates

#7554

Deploy preview for docsdocker ready!
Built with commit 703a9fb314dd7949ea8155a067c6e056aa709bc3
https://deploy-preview-8346--docsdocker.netlify.com

@nicolaka PTAL - I think I got everything - thanks very  much for the quick response!

I think this looks good!

@nicolaka - Thank you! Merging...


tabulate dep missing from rpm

Describe the bug
Using the built rpms from a PR and installing them locally results in a tabulate module not found error when you attempt to bootstrap
To Reproduce
Steps to reproduce the behavior:
[stack@task-core-0 directord]$ sudo dnf localinstall -y ~/directord/directord*.noarch.rpm ~/directord/python3-ssh-python-0.9.0-1.el8.x86_64.rpm
[stack@task-core-0 directord]$ directord --debug bootstrap --catalog ~/task-core/examples/directord/basic/directord_catalog.yaml --catalog /usr/share/directord/tools/directord-dev-bootstrap-zmq.yaml
Traceback (most recent call last):
  File "/usr/bin/directord", line 33, in <module>
    sys.exit(load_entry_point('directord==0.11.3', 'console_scripts', 'directord')())
  File "/usr/bin/directord", line 25, in importlib_load_entry_point
    return next(matches).load()
  File "/usr/lib/python3.6/site-packages/importlib_metadata/__init__.py", line 105, in load
    module = import_module(match.group('module'))
  File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 994, in _gcd_import
  File "<frozen importlib._bootstrap>", line 971, in _find_and_load
  File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/usr/lib/python3.6/site-packages/directord/main.py", line 28, in <module>
    from directord import bootstrap
  File "/usr/lib/python3.6/site-packages/directord/bootstrap.py", line 27, in <module>
    from directord import utils
  File "/usr/lib/python3.6/site-packages/directord/utils.py", line 25, in <module>
    import tabulate
ModuleNotFoundError: No module named 'tabulate'

closed via #352 352


Getting the wasm-opt version programatically

Hey! Thanks for these bindings 😄
I want to be able to get programmatically the version of the underlying version of
wasm-opt which was built by the library. So something like wasm_opt::VERSION
or wasm_opt::version(). From what I can tell the only way to do that right now is to
either parse the crate version number, or use a locally installed wasm-opt binary.
I'd be happy to implement this myself if you point me to the right area of the codebase.

@HCastano I am happy to include this feature, though I am interested to know your use case if you can tell me what you will be doing with the version number.
The binaryen version can take two different forms, depending on whether it is being built from git or from a redistributable package. Our build script attempts to reproduce the same logic for extracting the version number as binaryen's on build system.
Here is the build script code for finding the version: https://github.com/brson/wasm-opt-rs/blob/edcdb739fe954d4954dc67e763dbc4d1bbd49231/components/wasm-opt-sys/build.rs#L332-L369
That version is written as a string to the PROJECT_VERSION define in config.h.
Exposing this to the Rust API should entail:

Modifying components/wasm-opt-cxx-sys/src/shims.h to add a function to return this value. It can probably live with the grab bag of misc functions at the end of the file.
Modifying components/wasm-opt-cxx-sys/src/lib.rs to add the cxx bindings
Adding a wrapping function to components/wasm-opt/src/base.rs
Probably that function will have a signature of fn() -> String. In that case it can be reexported from lib.rs

I'd like to call the function binaryen_version to distinguish it from the crate version.
It might be possible to arrange for the function signature to be fn() -> &'static str, but I don't know offhand how to do it. It would probably involve defining a C++ static to hold the value, and carefully defining all the FFI functions. I am fine with either String or &'static str.

It would also be possible to expose this as a static value BINARYEN_VERSION, though it would require emitting some Rust code from the wasm-opt-sys build script, including it in the wasm-opt-sys crate, possibly with include!, and then reexporting it from wasm-opt.
This method might actually require less code.
I am ok with either way.


openra: 20181215 -> 20190314…

…, openraPackages.engines.playtest: 20190106 -> 20190302, openraPackages.engines.bleed: 9c9cad1 -> 07dc2a1

Motivation for this change
version bump
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

@fusion809 @msteen @rardiol building openraPackages.engines.bleed fails when I build locally:
~/nixpkgs> nix-build -A openraPackages.engines.bleed
these derivations will be built:
  /nix/store/bmwmbb5rw0xy9l92r3qp2g8dmwr1205a-openra-bleed-07dc2a1.drv
building '/nix/store/bmwmbb5rw0xy9l92r3qp2g8dmwr1205a-openra-bleed-07dc2a1.drv'...
unpacking sources
unpacking source archive /nix/store/92ab04n0wz5kfcfjmx8zp63by3c7mb7v-source
source root is source
patching sources
configuring
building
build flags: SHELL=/nix/store/x0mlaj4z4ciycaycfwc36l1932mwywfj-bash-4.4-p23/bin/bash prefix=\$\(out\) DEBUG=false default man-page
make: *** No rule to make target 'default'.  Stop.
builder for '/nix/store/bmwmbb5rw0xy9l92r3qp2g8dmwr1205a-openra-bleed-07dc2a1.drv' failed with exit code 2
error: build of '/nix/store/bmwmbb5rw0xy9l92r3qp2g8dmwr1205a-openra-bleed-07dc2a1.drv' failed

Any thoughts?

There were a few commits where in the man-page make target depended on the 'default' make target, which no longer existed—you're building one of them. This issue was fixed in OpenRA/OpenRA#16511. Now, man pages need to be built with the all make target and installed (i.e. moved to their appropriate locations) with the install-man-page target. But, sadly, that won't fix all the build problems recently introduced, as now OpenRA requires the MSBuild Mono package and Mono 5.10.x or later (preferably 5.12.x or later). Not sure if NixOS presently uses Mono 5.12.x or later, probably does.

Related: #61394

As mentioned by @c0bw3b I already made a PR (#61394) to update the OpenRA engine releases and mods, so I vote to close this PR. Due to the things mentioned by @fusion809 the bleeding version has been updated to the latest commit before the changes were made to the build process.

@msteen don't I feel silly now... thanks for taking care of this!


Issue when restarting SIA UI

A critical error loading Sia has occured: Siad unexpectedly exited. Error log: Loading...
(0/6) Loading siad...
(1/6) Loading gateway...
(2/6) Loading consensus...
(3/6) Loading transaction pool...
(4/6) Loading wallet...
(5/6) Loading host...
Closing wallet...
Closing transaction pool...
Closing consensus...
Closing gateway...
error while loading contract manager atomic data: error loading the contract manager settings file: unable to read persisted json object from disk: unable to read header from persisted json object file: EOF
Bug Report
Check to see if a bug report already exists.  If you still want to create a new issue please include the information below.
Stack Trace or error message
Environment

Sia version:
OS:

Any useful logs
Feature Request
Check to see if the feature is on the roadmap.  If it is not on the roadmap then clearly describe your feature request and why it would benefit Sia.
Sia roadmap

Looks like contractmanager.json is corrupted. There may be a contractmanager.json_temp file in the same folder. If so, you can try replacing contractmanager.json with contractmanager.json_temp. If that also fails, you will need to delete the contractmanager folder entirely.


Update New-AdaptiveScope.md

Issue #10289

Learn Build status updates of commit 3930867:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/New-AdaptiveScope.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


{ServiceConnector}: fix AttributeError with --no-wait

Related command

Description

Fix https://github.com/microsoft/azure-container-apps/issues/1296
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

ServiceConnector


Format files under lib/farmbot/bot_state/*

and update formatted_files

@pdgonzalez872 i kind of forgot about this. If you rebase i'll pull in :+1:


Move lineCounter app to azure-sdk repo

Changes from https://github.com/pakrym/LineCounter

Use EventHubs Preview 6
Use App Insights instead of Zipkin
append .html to end of view file path to avoid server error involving accessing path with extensions like .cs

FYI @jongio @kaerm


Create neovim

Learning Neovim can seem daunting at first, but there are plenty of resources available to help you get started. Here’s a curated list of resources, including tutorials, documentation, and community links:
Official Resources

Neovim Official Documentation:

Neovim Documentation
This is the primary source for learning about Neovim's features and configuration.

Getting Started Guide:

Getting Started
A concise guide to help you set up Neovim and understand its basic usage.

Tutorials and Guides

Open Source Society University:

OSSU: Computer Science
Includes a section on Neovim as part of its programming curriculum.

ThePrimeagen's Neovim Configuration:

ThePrimeagen's YouTube Series
A series of videos that cover Neovim configuration and plugins.

Neovim From Scratch:

Neovim from Scratch
A guide that walks you through setting up Neovim from the ground up.

Configuration and Plugins

Awesome Neovim:

Awesome Neovim
A curated list of plugins and resources for enhancing your Neovim experience.

LunarVim:

LunarVim
A Neovim configuration that comes with a set of pre-installed plugins and sensible defaults.

Community and Support

Neovim Reddit Community:

r/neovim
A community where you can ask questions and share tips.

Neovim Discord:

Neovim Discord Server
Join the community to chat and get help in real time.

Stack Overflow:

Neovim Questions
A place to ask specific questions and find answers related to Neovim.

Additional Learning Platforms

FreeCodeCamp:

Look for articles and tutorials about Neovim on FreeCodeCamp or YouTube.

YouTube:

Search for "Neovim tutorials" on YouTube for a variety of video tutorials from different creators.

By exploring these resources, you can gradually become proficient in Neovim. Don't hesitate to experiment and customize your setup as you learn!

Please read docs/CONTRIBUTING.md guidelines!
we have subject "IDE and editors" with neovim resources


Add vm_destroy event to MiqEventDefinition.

Add missing vm_destroy event.
For clarity, vm_delete is the policy event when a VM is removed from inventory from MIQ UI.
vm_destroy is the policy event raised when a VM is deleted from disk from VMware side.
vm_unregister is the policy event raised when a VM is removed from inventory from VMware side.
Includes https://github.com/ManageIQ/manageiq-content/pull/223.
https://bugzilla.redhat.com/show_bug.cgi?id=1506520
@miq-bot assign @gmcculloug
@miq-bot add_label bug, fine/yes, gaprindashvili/yes

@lfu Thanks for the clarification in the description.  Want to note that vm_delete is commented out in miq_event_definitions.csv which makes sense as the VM object would no longer exist.


Add check for knative when waiting for runtime

Add check for knative when waiting for runtime

Codecov Report

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

@@           Coverage Diff           @@
##           master     #451   +/-   ##
=======================================
  Coverage   82.29%   82.29%
=======================================
  Files          29       29
  Lines         864      864
  Branches       65       65
=======================================
  Hits          711      711
  Misses        109      109
  Partials       44       44

Continue to review full report at Codecov.

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


Support Container App Jobs

I want to use service connector in container app jobs as well.

Thanks for feedback. we're looking at it.

According to this issue: https://github.com/microsoft/azure-container-apps/issues/1032
It's supported but there's some backend authorization still to do. @yungezz could you have a look?

hi @brycechen1849 , could you pls provide update? thanks


Improvements and fixes for "flutter build aar"

I attempted to use flutter build aar for a presentation and ran into a few issues that we should address.

[ ] Document all possible configurations of flutter build aar in the wiki guide, explain the implications of each, and even point out that we don't support certain configurations, e.g., building an AAR for release as x86

[ ] Document the distinction and independence between debugImplementation/releaseImplementation in build.gradle vs the AAR path string, e.g., flutter_debug and flutter_release.

[ ] Catch bad flutter build aar requests in the tool and output error messages that tells the user that the given configuration is invalid.

CC @xster @blasten

Anything left here @blasten?

Same here. Should we close this?

This is done


Implement IsWhitelistedRuntimeValue for Swift

IsRuntimeSupportValue in value object was changed to
IsWhitelistedRuntimeValue in upstream lldb.
See also:
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@364845
91177308-0d34-0410-b5e6-96231b3b80d8

cc reviewers of the upstream patch: @xiaobai @labath @JDevlieghere @dcci @compnerd


Continuous integration ;)

Changed assemblies path to help use continuous integration tools.
Since now all game dlls could be located in TLM/dependencies folder.
You can still use reference paths set in *.csproj.user
BTW I hope it won't fail CI building process

Now it should pass... 😄


docs: Add developer docs

Summary
Add developer docs
Why
We want contributions
What

Create developer doc one pager in the vuepress docs
link to it in the contributing.md
polish contributing.md

How

create a diagram of how the runtime works
create a diagram of how the build works
create docs about how to create a plugin
keep any repo specific docs like how to set up repo in the github repo off the docs

Developer docs currently deployed here https://evmts-monorepo-docs.vercel.app/reference/execute.html

Worked on this last weekend.   The highest level docs for the core library are written.   Still need to write the plugin docs

Polished the getting started
Changing the API to a more ergonomic client.query and client.mutate.  Docs are not converted yet except in a few spots
Started adding guides such as cheat-codes ethers.js usage best practices ect.

broke up smaller tickets.  After I land all of them I will close this

Hey, may I work on this? Can you please assign this to me?

@yoursmanjunad sorry didn't see this comment til now! There are plenty of issues to work on including documentation. Reach out if you are interested in anything


Bug - points command: Symbols aren't escaped

Complete the following REQUIRED checkboxes:

[x] I have thoroughly read and understand The Odin Project Contributing Guide

[x] The title of this issue follows the Bug - location of bug: brief description of bug format, e.g. Bug - points command: Extra whitespace causes command to not be called

The following checkbox is OPTIONAL:

[x] I would like to be assigned this issue to work on it

1. Description of the Bug:

When people have special/punctuation characters in their names it causes unexpected side effects because of Discord's message formatting. For example I added "`test`" into my name and that caused the points command to show my name as "name test" instead of "name `test`".
That can happen with other symbols as well(the 2 examples are shown in the screenshots below). The second example shows that adding || into ones name triggers the spoiler format(if there is another set of || after) which hides lines of the message in between the vertical lines.

2. How To Reproduce:

Use the points command
Find a name where there is Discord formatting or rename your server name to include Discord formatting

3. Expected Behavior:

Use the points command
You see your name with the characters not formatted, instead they are escaped

4. Desktop/Device:

Device: Laptop and mobile so far(probably a problem on all devices)
OS:
Browser:
Version:

5. Additional Information:

This should be a relatively easy fix since discord.js has its own built-in escaper, escapeMarkdown, which is included in the discord.js package, so it should be as simply as calling that on any string that might contain markdown where it isn't wanted

Yep, escapeMarkdown from the discord.js package is all we'll need for this.
services/points/points.service.js has stuff that deals with .displayName e.g. interaction.guild.members.cache.get(user.id).displayName that should be escapeMarkdown(interaction.guild.members.cache.get(user.id).displayName), or member.displayName which should be escapeMarkdown(member.displayName).
Various methods in services/rotations/rotation.service.js also deal with extracting display names that currently don't have markdown escaped.
Both of these have their corresponding .test.js files that would need any mock data amended to include an example of a display name that should be escaped.
@T0nci is this still something you wish to work on?

@MaoShizhong Yes, I'd love to work on this! Although since this is my first contribution involving code that isn't HTML or markdown lol, if I can't finish the task I'll ask for help or ask for it to be reassigned to someone that can complete it.

@MaoShizhong Yes, I'd love to work on this! Although since this is my first contribution involving code that isn't HTML or markdown lol, if I can't finish the task I'll ask for help or ask for it to be reassigned to someone that can complete it.

Assigned. Feel free to ask about any problems or uncertainties. Local bot setup instructions are in this repo's wiki.
I think for the points stuff you won't be able to directly test some points things in your test discord server since there's an intermediary bot that I don't think we have a dev version for (not too familiar with that part myself but it was mentioned at some point in our staff channels), but the Jest tests for those should still run fine, hence we need them amended to test the escaped behaviour.

@T0nci just a courtesy check in on this in case you need any help or clarification?

@MaoShizhong Will get on it in the next few days! Had a break from coding for a while and just got into the flow again, so I'll look into it. My apologies for the long period it's taking me to complete this contribution.

No worries, real life comes first and breaks are important :+1: Let me know here if you need any assistance at any points.

@MaoShizhong So while fixing the leaderboard subcommand, I noticed that there is an extra backslash when there is a `, although I'm guessing that's because jest is using template literals and needs to escape all `s. Is it fine if I leave this test(and possibly all other tests that will include `) like this? All other markdown is escaped correctly.

The line in question is where user103 is ^

As long as the visual output from the command is correct and all tests pass with the appropriate snapshots, that's fine. If the snapshot requires additional backslashes, then it needs them.
\\\` would be needed in this case because the discord embed needs to enter \`, so we need to escape the backtick to prevent clashing with the template literal, and also escape the first blackslash so it doesnt end up escaping the backtick's backslash instead.

@MaoShizhong I have a problem with completing the second part of the task. I'm confused how the code works, and in turn don't know what and how to test. I may have pinpointed the part where I'm supposed to include the escapeMarkdown function(line 35 and 37), but in any case I might not be able to continue with the contribution.

I have successfully completed integrating the escapeMarkdown function in the points commands. The commits are located on the points_escape_markdown branch for review.

@T0nci Yep, you've isolated the correct function. You can actually test the rotation commands locally in your test server since you'll be an admin in that.
/triage add and add yourself (change your server name to include some sort of markdown like spoilers), and you can use /triage rotate to view the output. escapeMarkdown() on both username returns will do the trick. Tests will then need amending so that at least one markdown username is included and tested to be escaped properly on output.
We could probably even change that map callback's returns to
    this.displayNames = members.map(async (memberId) => {
      const member = await server.members.fetch(memberId);
      return escapeMarkdown(member.nickname || member.user.username);
    });

@MaoShizhong That's great, I'll try to implement this too once I get better from my illness.
The part that was bugging me and still is, is that I don't really know how the command works so I can change the tests correctly. I've tried using it in my discord server with an odin-bot setup(through the steps in the docs) but crashes after the points leader and user commands and the rotation commands(not too sure about all rotation commands that's why I'll try to use them again tommorow) so I couldn't use the commands to try to see how it works.

The points commands won't work because it relies on a separate bot we don't have a dev version for (which we have an issue open about it - waiting on a reply from others who know more).
The /triage commands are what you want for the rotation stuff and I can confirm on my private test server, /triage add and /triage rotate work perfectly fine (they're not tied to a database or anything unlike the points stuff, that's why - they're just part of an internal staff queue). The rotation tests get their dummy data not from botCommands/mockData.js like the points stuff, but I think somewhere in utils/. Should be traceable from the imports in the rotations test file.
No rush - recover well! Health comes first.

@MaoShizhong So while I was starting to work on the last part of this issue, I ran into a problem. I launched the bot on my server to see how the triage commands worked and there was no problem. But then I fetched upstream to sync the new commits while I was unavailable, merged them on main and my branch and the triage commands started throwing an error. I don't know if it's something I messed up in my fork or something that affected everyone.

Played around with this locally, and I think this is being caused by you not having any people in the triage queue. Try adding yourself and then try again

Just tried it and the same error shows up for every triage command - even the add command. I might just have to start over on a new fork.


Add DocumentID and ImageUniqueID to exiftool and XMP output

          Found it.

The field that should be set is ImageUniqueID. Right now PhotoPrism only reads this field from exiftool and not XMP but I guess it can't hurt to set it in both for future proofing.
ImageUniqueID must be a UUID for this to work, I believe that is the case with Apple Photos Identifiers, correct?
This worked for me:
exiftool -overwrite_original -ImageUniqueID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.edited.jpeg
exiftool -overwrite_original -ImageUniqueID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.jpg
exiftool -overwrite_original -ImageUniqueID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.nef

Edit: It appears that DocumentID field is also supported.
I ran the following commands on the 3 (original) output files and it got them stacked in PhotoPrism:
exiftool -overwrite_original -DocumentID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.edited.jpeg
exiftool -overwrite_original -DocumentID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.jpg
exiftool -overwrite_original -DocumentID="51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25" Film0103.nef

Originally posted by @odedia in https://github.com/RhetTbull/osxphotos/issues/1508#issuecomment-2049372678

The fields are:
  "EXIF:ImageUniqueID": "51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25",
  "MakerNotes:ImageUniqueID": "51b2fbb7d7d5ad4d41d99c8de96e1a1a0f25",
  "XMP:DocumentID": "51b2fbb7-7d5a-4d41-99c8-e96e1a1a0f25",

MakeNotes cannot be written by exiftool if it doesn't already exist. I didn't set MakerNotes so it got set because -ImageUniqueID was specified so exiftool set both matching tags.
MakerNotes should probably be updated but this requires custom code if it doesn't already exist (see makelive).


Node.js  TypeScript team Meeting 2025-01-01

Time
UTC Wed 01-Jan-2025 16:30 (04:30 PM):

Timezone
Date/Time

US / Pacific
Wed 01-Jan-2025 08:30 (08:30 AM)

US / Mountain
Wed 01-Jan-2025 09:30 (09:30 AM)

US / Central
Wed 01-Jan-2025 10:30 (10:30 AM)

US / Eastern
Wed 01-Jan-2025 11:30 (11:30 AM)

EU / Western
Wed 01-Jan-2025 16:30 (04:30 PM)

EU / Central
Wed 01-Jan-2025 17:30 (05:30 PM)

EU / Eastern
Wed 01-Jan-2025 18:30 (06:30 PM)

Moscow
Wed 01-Jan-2025 19:30 (07:30 PM)

Chennai
Wed 01-Jan-2025 22:00 (10:00 PM)

Hangzhou
Thu 02-Jan-2025 00:30 (12:30 AM)

Tokyo
Thu 02-Jan-2025 01:30 (01:30 AM)

Sydney
Thu 02-Jan-2025 03:30 (03:30 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+TypeScript team+Meeting+2025-01-01&iso=20250101T1630
or https://www.wolframalpha.com/input/?i=04PM+UTC%2C+Jan+01%2C+2025+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1sUJIQv2yLZwkKonR8tLK47qhAPbr_gL0_gHUNqpQXk8/edit

Agenda
Extracted from typescript-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/typescript

Unflag --experimental-strip-types #17

Invited

Typescript team: @nodejs/typescript

Observers/Guests
Notes
The agenda comes from issues labelled with typescript-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting
https://zoom.us/j/95749675148

link for participants: <>
For those who just want to watch We stream our conference call straight to YouTube so anyone can listen to it live, it should start playing at https://www.youtube.com/c/nodejs+foundation/live when we turn it on. There's usually a short cat-herding time at the start of the meeting and then occasionally we have some quick private business to attend to before we can start recording & streaming. So be patient and it should show up.
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

Invitees
Please use the following emoji reactions in this post to indicate your
availability.

:+1: - Attending
:-1: - Not attending
:confused: - Not sure yet

This falls on a public holiday. Shall we cancel?

As U2 say every year "All is quiet, on New Year's Day" (source)
I think this is a good day to skip the meeting.


Migrates alert actions

Recording:
https://user-images.githubusercontent.com/54092533/188440653-150919a6-696f-462d-b88f-ca50133facb9.mp4
Signed-off-by: Bipul Adhikari<EMAIL_ADDRESS>

Depends on https://github.com/openshift/console/pull/12018

/hold

/lgtm

/lgtm cancel

/hold cancel

/lgtm


Get 404 on pages

Hello,
everything work fine but if I visit any pages I get a 404.
Posts, categories,... everything else is working correctly.

@colbyfayock I've fixed removing the baseurl form the uri:
  const paths = pages
    .filter(({ uri }) => typeof uri === 'string')
    .map(({ uri }) => {
      const segments = uri
        .replace('http://localhost:3000', '')
        .split('/')
        .filter((seg) => seg !== '' && seg !== undefined);
      return {
        params: {
          slugParent: segments.shift(),
          slugChild: segments,
        },
      };
    });

how did you make this working without this fix?

hey i'm not really sure about this one? could it be a custom setting you have for permalinks or how URLs are returned? haven't seen this issue before

@colbyfayock yes it was my fault. I've had this:
function custom_frontend_url($permalink, $post)
{
  $custom_permalink = str_replace(home_url(), HEADLESS_URL,  $permalink);
  return $custom_permalink;
};

add_filter('page_link', 'custom_frontend_url', 10, 2);
add_filter('post_link', 'custom_frontend_url', 10, 2);
// If you use custom post types also add this filter.
add_filter('post_type_link', 'custom_frontend_url', 10, 2);

in order to change the links from the WP be, but this affects also the uri in the grapqhl queries.

ah thanks for sharing, glad you were able to figure it out! is this something that can be avoided in the starter? i tend to think that's a custom feature that wouldn't make sense in the starter beyond this issue that people can search for. thoughts?


Support for SSD-1B

Hello kohya,
I've been making use of your wonderful repository for my projects, and I wanted to inquire if there's a possibility to introduce support for training the SSD-1 model. The inclusion of SSD-1 would benefit many users like me who are interested in leveraging its capabilities.
https://huggingface.co/segmind/SSD-1B
SSD-1 is known for its training speed faster than SDXL.
I understand that integrating a new model can be a significant undertaking, and I appreciate all the work that has gone into this repository so far. If there's any way the community can assist in this endeavor, please let us know.
Thank you for considering this request, and I look forward to any updates on this matter.
Best regards,
Alfredplpl

Maybe this will be helpful:
huggingface/diffusers: Added support to create asymmetrical U-Net structures #5400
https://github.com/huggingface/diffusers/pull/5400

The checkpoint we're using for the SDXL distillation is asymmetrical.

I found that it is hard to finetune SSD-1B.
I will test the distillation code:
https://github.com/segmind/SSD-1B/blob/main/distill_sdxl.py

I found that we can finetune SSD-1B with large batch size such as 128.
But, the diffusers script have not aspect ratio baskets option.


Omnisharp fails to start when dependency version contains "*"

If you declare a dependency in your .csproj file like this:
<PackageReference Include="Microsoft.AspNetCore" Version="1.1.*" />

After restoring the dependencies, omnisharp will fail to start with the message:
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        The "ResolvePackageDependencies" task failed unexpectedly.
This is an unhandled exception from a task -- PLEASE OPEN A BUG AGAINST THE TASK OWNER.
System.FormatException: Input string was not in a correct format.
  at System.Text.StringBuilder.AppendFormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) [0x00306] in <12e050e5b3d34326a1b4e2e7624e75da>:0
  at System.String.FormatHelper (System.IFormatProvider provider, System.String format, System.ParamsArray args) [0x00026] in <12e050e5b3d34326a1b4e2e7624e75da>:0
  at System.String.Format (System.IFormatProvider provider, System.String format, System.Object arg0, System.Object arg1, System.Object arg2) [0x0000b] in <12e050e5b3d34326a1b4e2e7624e75da>:0
  at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.GetDependencyDiagnostics () [0x0017a] in <44c250c7557f45749e194fbbdb4b9145>:0
  at Microsoft.NET.Build.Tasks.ResolvePackageDependencies.ExecuteCore () [0x00012] in <44c250c7557f45749e194fbbdb4b9145>:0
  at Microsoft.NET.Build.Tasks.TaskBase.Execute () [0x00000] in <44c250c7557f45749e194fbbdb4b9145>:0
  at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute () [0x0002a] in <bdf083ca20c84af487947992fd9a4a29>:0
  at Microsoft.Build.BackEnd.TaskBuilder+<ExecuteInstantiatedTask>d__26.MoveNext () [0x002bf] in <bdf083ca20c84af487947992fd9a4a29>:0

The problem only occurs after restoring the dependencies, just changing the .csproj file does not generate any problem.

@livioribeiro: This looks like it's failing in one of the MSBuild tasks the .NET Core SDK. Could you provide the information below to help me investigate?

What operating system (and version) are you using?
At a command prompt, run dotnet --info and provide the output
What editor (and version) are you using OmniSharp (e.g. VIM, VS Code, Emacs, etc.)?

Thanks!

Note: My suspicion is that you are trying to use a nightly 2.0-preview2 .NET Core SDK build. Those nightly builds have known issues that are broken with OmniSharp (https://github.com/OmniSharp/omnisharp-roslyn/issues/865). However, if that's not the case let me know.

I tested in two computers, home and work, both running Ubuntu 16.04 x64, and using VS Code 1.12.2.
First I tested at work, running sdk 1.0.4, and noticed the problem.
And now tested at home, tested with sdk 2.0-preview, all worked, then installed sdk 1.04, and it worked as well!
I will test again at my work computer to try to give more info on this.

Just tested again at my work computer, problem still happening.
$ dotnet --info
.NET Command Line Tools (1.0.4)

Product Information:
 Version:            1.0.4
 Commit SHA-1 hash:  af1e6684fd

Runtime Environment:
 OS Name:     ubuntu
 OS Version:  16.04
 OS Platform: Linux
 RID:         ubuntu.16.04-x64
 Base Path:   /usr/share/dotnet/sdk/1.0.4

Does it still happen with the 2.0-preview that you also tried on your home computer?

Yes, happens for both versions.

Hmmm... that is very strange. Both machines are running the same OS, one fails and the other works. I'll get Ubuntu 16.04 set up and see if I can repro.

I set up Ubuntu 16.04 and still could not repro. On the VM I have the following installed to try and replicate your machine.

Visual Studio Code 1.12.2.
.NET Core SDK 1.0.4sudo sh -c 'echo "deb [arch=amd64] https://apt-mo.trafficmanager.net/repos/dotnet-release/ xenial main" > /etc/apt/sources.list.d/dotnetdev.list'
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 417A0893
sudo apt-get update
sudo apt-get install dotnet-dev-1.0.4

C# for Visual Studio Code 1.10.0 (using the Extensions pane in VS Code).

Then, I did the following in a Terminal window to create a new project and open it in VS Code.
mkdir test
cd test
dotnet new console
code .

In VS Code, I opened Program.cs and and waited until I received two prompts:

There are unresolved dependencies from 'Test.csproj'. Please execute the restore command to continue. (I clicked 'Restore')
Required assets to build and debug are missing from 'test'. Add them? (I clicked 'Yes')

At this point, I have no squiggles in Program.cs.
Next, I opened test.csproj and added the following:
<ItemGroup>
  <PackageReference Include="Microsoft.AspNetCore" Version="1.1.*" />
</ItemGroup>

Then, I saved the project and received another prompt to restore. (Again, I clicked 'Restore')
After the restore completed, I opened Program.cs and verified that I could get IntelliSense when typing Microsoft.AspNetCore.Builder.IApplicationBuilder builder; inside Main(..).

Does that look similar to what you did?

Sorry! Closed accidentally.

Yes, that is what I did.
It seems that the problem is on my machine. I'll close this issue until I can figure out what was causing the problem.
Thanks a lot.

OK. Let me know if you learn anything. I'm very curious!


Adds islist() and list2params()

Both survived basic testing, but it's probable that the latter has cases I haven't considered.

Addressed.


Support for the 'new' Chrome-based Microsoft Edge

I guess this is a request for enhancement, or for information about work-arounds?
Just like traditional Chrome, the (relatively) new Chrome-based Edge requires a webdriver to be downloaded, see:
https://docs.microsoft.com/en-us/microsoft-edge/webdriver-chromium/?tabs=c-sharp
(ignore the c-sharp bit in the url...)
Once one has the edgedriver, configuration (in Geb/Grails, for my situation) is familiar:
import org.openqa.selenium.Dimension
import org.openqa.selenium.edge.EdgeDriver
import org.openqa.selenium.edge.EdgeOptions

environments {

    edge {
        driver = {
            EdgeOptions options = new EdgeOptions()
            options.addArguments("headless")

            EdgeDriver driver = new EdgeDriver(options)

            //Resize current window to the set dimension
            driver.manage().window().setSize(new Dimension(1450,1024));

            println "EDGE driver created"
            driver
        }
    }
}

Can this be supported, please.

I've just published 2.3 which contains support for this. Thanks for submitting the request., @transentia.


Beam Search

Could you add a beam search parameter for high level API generation? Thanks.

Any news ?


[REQUEST] - Can graphrag support other free LLMs like qwen2?

Reference Issues
No response
Summary
support other free LLMs like qwen2
Basic Example
support other free LLMs like qwen2
Drawbacks
support other free LLMs like qwen2
Additional information
No response

Please check the latest version and instruction for setting up GraphRAG here https://github.com/Cinnamon/kotaemon#setup-graphrag.


[ROCKETMQ-104] Make MQAdmin commands throw exceptions

JIRA issue: https://issues.apache.org/jira/browse/ROCKETMQ-104

Coverage increased (+0.02%) to 31.538% when pulling 426b3f37686e6df05563d654493efc72e374ec40 on shroman:ROCKETMQ-104 into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.02%) to 31.538% when pulling 426b3f37686e6df05563d654493efc72e374ec40 on shroman:ROCKETMQ-104 into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Coverage increased (+0.02%) to 31.538% when pulling 426b3f37686e6df05563d654493efc72e374ec40 on shroman:ROCKETMQ-104 into 573b22c37806a21543b90707bcce6022243a62da on apache:master.

Hi @shroman ,
LGTM, but why do we add so many @Ignore annotations in this PR? All the he unit tests of tools module have been skipped in tools/pom.xml. We may forget to remove these annotations after this issue[1] has been resolved.
[1]. https://issues.apache.org/jira/browse/ROCKETMQ-77

@zhouxinyu Thanks for checking it!
Well, @Ignore is there just for finer granularity -- we remove it one by one when implementing each test. If you think we don't need it, I can remove ;)

please @vongosling @lizhanhui help review.

@shroman IMO, we can let the tool module unit-test passed once someone polish here. thoughts?

@vongosling Thanks for reviewing!
Sure, unit tests can be completed after we improve this module.

Hi, @shroman  this PR will be merged to develop branch firstly as our new branching model: http://rocketmq.incubator.apache.org/docs/branching-model

@shroman Could you help to close this PR and Jira issue:-)


Properties are not being substituted

Search first

[X] I searched and no similar issues were found

Description
Properties are not being substituted when used on changes using the ${parameter} format - they get passed to the changes as the literal string "${parameter}".
git bisect tracked the issue to 6f8a113ad
Steps To Reproduce
Set a parameter on the defaults file:
parameter.a_parameter=asd

Use the parameter on a change:
<changeSet author="joserebelo" id="test.change">
    <createTable tableName="${a_parameter}">
        <column name="user_id" type="VARCHAR(40)"/>
    </createTable>
</changeSet>

Expected/Desired Behavior
It was expected that a table with the name "asd" would have been created. However, a table with the literal name "${a_parameter}" gets created.
The same issue applies to args in the executeCommand change and params on customChanges.
Liquibase Version
4.21.0
Database Vendor & Version
PostgreSQL 9.6
Liquibase Integration
cli
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

Came here while debugging the same issue. Some more info:
Works when specifying properties on the command line as -Dname=value. Fails when specifying them in the defaults file (liquibase.properties) as parameter.name=value.
The failure affects both the SQL generated (as evidenced by liquibase update-sql run against a blank database/schema) and the changeset checksum (as evidenced by the failures we’re getting from update and by manual liquibase calculate-checksum).

Version 4.21.1 is also affected.
Database: Oracle 19c
Liquibase throws the exception Oracle non supported sql92 token  when trying to parse the property.

Same with 4.21.1 and postgresql 14

It's only when you are setting properties from the liquibase.properties file, correct?  Or are there other ways anyone is setting them and it's also not working?

I validated the fix for this issue using a changelog that has changesets that use parameters defined in the changelog, parameters defined in the liquibase.properties file and a table that uses a combination of changelog and liquibase.properties parameters. I tested using the CLI against a Postgres 12.6; the Liquibase build is https://github.com/liquibase/liquibase/actions/runs/4874060226.
In all cases, the correct substitution was executed using the fix build.

The Changelog (liquibase.properties values listed in comment)
<?xml version="1.1" encoding="UTF-8" standalone="no"?>
<databaseChangeLog xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
xmlns:ext="http://www.liquibase.org/xml/ns/dbchangelog-ext"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:pro="http://www.liquibase.org/xml/ns/pro"
xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog-ext http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-ext.xsd
http://www.liquibase.org/xml/ns/dbchangelog http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-latest.xsd">

<!-- Properties and Preconditions -->
    <property  name="clob.type"    value="clob"  dbms="oracle,postgresql"/>
    <property  name="clob.type"    value="longtext"  dbms="mysql"/>
	<property  name="clob.type2"   value="foo"  dbms="postgresql"/>
    <property  name="table.name"   value="cltable"/>
	<property  name="column1.name" value="clcol1"/>
	<property  name="column2.name" value="clcol2"/>

<!-- ====================================================== -->
<!-- CHANGESETS THAT SUCCESSFULLY DEPLOY                    -->
<!-- ====================================================== -->

<!-- SIMPLE TABLE (No Substitution) -->
	<changeSet author="erz"  id="1::createTable-success" contextFilter="ctx,ctx2" labels="tblsuccess,anotherlabel">
		<comment>Comment for 1::createTable-success</comment>
		<createTable tableName="table_1">
            <column name="name" type="CHAR(20)"/>
        </createTable>
	</changeSet>

<!-- CHANGELOG PROPERTY SUBSTITUTION -->
<!-- Substitution properties defined in changelog -->
    <changeSet author="erz" id="2::substitution-changelog"  dbms="postgresql">
         <createTable  tableName="${table.name}">
             <column  name="id"  type="int"/>
             <column  name="${column1.name}"  type="${clob.type}"/>
             <column  name="${column2.name}"  type="int"/>
         </createTable>
    </changeSet>

<!-- Substitution properties defined in liquibase.properties file.
parameter.table_name: lbproptable
parameter.table_name2: clandlbproptable
parameter.clob_type: clob
parameter.column1_name: lbpropcol1
parameter.column2_name: lbpropcol2
-->
    <changeSet author="erz" id="2::substitution-properties"  dbms="postgresql">
         <createTable  tableName="${table_name}">
             <column  name="id"  type="int"/>
             <column  name="${column1_name}"  type="${clob_type}"/>
             <column  name="${column2_name}"  type="int"/>
         </createTable>
    </changeSet>

<!-- Mix of changelog and properties file substitution -->
    <changeSet author="erz" id="2::substitution-mixed"  dbms="postgresql">
         <createTable  tableName="${table_name2}">
             <column  name="id"  type="int"/>
             <column  name="${column1.name}"  type="${clob_type}"/>
             <column  name="${column2.name}"  type="int"/>
         </createTable>
    </changeSet>
</databaseChangeLog>

Thank you for submitting this issue, @joserebelo!


Open door/window still activate alarm

Alarmo Version
1.9.3
HA Version
2022.5.5
Bug description
Hi,
even if none of the sensors (doors or windows) are set to "bypass automatically" they are excluded when system arm both on night and away.

Steps to reproduce
No response
Relevant log output
No response

Are you arming with force option active?
Otherwise the bypassing should not occur.

hi, thank you for your super fast replay. Where i can check "force option"? Thank you :)

no bug. only a config error from my side. Thank you :)


Folder-List Items must show alt/title message with folder name

Requirements

All folder-items must show alt message with complete folder name


Allow ResourceAction#fqname=nil to clear ae_*

Now that resource actions can have either embedded_automate ae_* values or a configuration_script_id it is helpful to clear the ae_* values for an existing resource action.


make NativeMenuBar showing the Icons

What does the pull request do?
make NativeMenuBar showing Icons under Windows
What is the current behavior?
Under Windows 10 the NativeMenuBar is not showing the Icons. Using OSX the Icons are visible.
In the Control-Template the property "Icon" is missing. But NativeMenuItem.Icon is a IBitmap. MenuItem.Icon should be an Image
So i intruduced a converter from IBitmap to Image. Both Default and Fluent theme
What is the updated/expected behavior with this PR?
Icons are shown under Windows

You can test this PR using the following package version. 0.10.999-cibuild0020160-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 0.10.999-cibuild0020160-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

Perfect! Thanks for building. Now i can work on my litte Programm with Icons in the Menu 👍

Perfect! Thanks for building. Now i can work on my litte Programm with Icons in the Menu 👍

this is just a bot showing you the link for testing. There is no little guy sitting and doing this for you 😉
Have a great weekend.

this is just a bot showing you the link for testing. There is no little guy sitting and doing this for you 😉

🙄 ahhh. ok
Like i said. I'm new to git and how it works in open source

You can test this PR using the following package version. 0.10.999-cibuild0020203-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]