Bug Report: No close button on the chatbot

Reproduction steps
When I click on the chatbot icon on the bottom right, it opens a chat, but there is no way to close it. Even reloading the page keeps the chat open.
Expected behavior
There should be a top bar that has a minimize or close option for the chat box.
Actual Behavior
The box stays open, no way to close it.

👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

There is a close button to close the chatbot @kaashikaagrawal ?

it is not visible on my system..but ok


PartNet models/performances with Pytorch

Dear @zeliu98 ,
Congratulation for your ECCV work and thank you for the neat code.
I was wondering why you are not sharing the PartNet models trained with Pytorch. Are you experimenting a gap in performances with respect to your Tensorflow implementation? Are you planning on releasing them soon?
Best,

Hi @SilvioGiancola
Thanks for your interest in our work!
Of course, we will sharing the PartNet models soon and we are still working on it, since the training has not finished yet. For temporary use, you can check this  checkpoint for PosPool. It has been trained for 180 epochs and can achieve 49.3/52.4 mIoU for val/test data splits, which is close to the final scores reported.

Great! Looking forward for the final models!
I was trying to train you model myself (4x v100 32GB, batch size 16) but for some reason, I only reached a best testing performances of 52.009% mmpIoU (10x voting), after exactly 400 epochs. I set the default 600 epochs for training, so that was my best performing model. Also, after 507 epochs, the loss returned NaN and broke the whole training (returning ~5% mmpIoU after that).
Any tip to reproduce your results? How much variance did you experienced?

Hi @SilvioGiancola,
We have released the pytorch models for PartNet. As for the problem you mentioned, may be the learning rate is too large, since in our initial implementation, the learning rate is linearly increasing with the batch size.  We have fixed this in our latest code.


Inconsistent CSV Inference and Parsing DateTime Handling

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

Following #3746 the CSV schema inference infers datetime strings as Timestamps, not Date64, as this was incorrect #3744.
However, the CSV reader still uses datetime_regex for Date64 columns, which is incorrect.
Following #3794 the timestamp parsing logic has got a whole lot more sophisticated, and it is unclear how to support arbitrary format strings with it.
Describe the solution you'd like

Given this functionality has been broken since #3746 and nobody has noticed, and no tests failed, I think we should just remove it
Describe alternatives you've considered

Additional context

label_issue.py automatically added labels {'parquet'} from #4133

label_issue.py automatically added labels {'arrow'} from #4133


[INLONG-2901][Manager] Fix maven tests

Title Name: [INLONG-2901][Manager] fix maven tests
Fixes #2901

Fix the exception that the manager module maven cannot run the test class, and unify the version of the maven-surefire-plugin plugin
Remove the skipTests attribute of the manager-web module pom.xml file, otherwise maven compilation will force the test to be executed

Motivation
Because of the 'Replace MySQL with PostgreSQL' #2784   feature developed, Need to unit test the manager module
Modifications
After testing, it is found that maven cannot run the test class due to the version of maven-surefire-plugin, which may conflict with other packages of the manager module. Tried multiple versions and found that only 2.21 and below can perform maven tests normally

3.0.0-M5

There is a problem with the manager unit test, which should be due to a version problem before. There may not actually be a test file that executes the manager


chore: remove unused image tag in .OwlBot-hermetic.yaml

This removes the unused image tag in this file. Part of the cleanup after enabling Hermetic Library generation in this repo.

RESOURCE_EXHAUSTED on latest kokoro CI jobs. Retrying now.


ENOENT: 'config/project-scratch-def.json'.

Hi,
Just got this error when installing on my Trial Dev Hub. Was asked to log an issue here...
Thanks
Fab
GUID: b016c28d-8ad2-83ff-8581-41dc99816b9b ERROR: ENOENT: no such file or directory, open 'config/project-scratch-def.json'.

GUID: b016c28d-8ad2-83ff-8581-41dc99816b9b ERROR: ENOENT: no such file or directory, open 'config/project-scratch-def.json'.
Set instance url to https://eu9.salesforce.com.
Successfully cloned https://github.com/wadewegner/deploy-to-sfdx.
No .salesforcedx.yaml found in repository. Using defaults.

Just being curious, from which repo did you try to deploy ?

from https://deploy-to-sfdx.com/... the BIG blue button...

Oh ok I understand. This button only works if the repo has a correct .salesforcedx.yaml file setup.
Give it a try here: https://github.com/dreamforce17/purealoe
You can look to the setup file in the repo it's pretty straightforward, or have a look to the doc here: https://deploy-to-sfdx.com/repo
I think here it's not working because the site seems to take the previous page as a parameter, and acts like if it was the repo you want to deploy.
Try to write the url yourself in a new tab, and you should see a list of the last repos deployed successfully.

Thanks for the explanation and, yes, I should have read the *@# manual!
You can close.

I'll keep it open as I think it should be made more obvious that we are not clicking on the link from a repo.


Move finance toc

Moving the Finance TOC to underneath the Canton docs.
Adding an entry to gitignore for the html folder.
Requesting tech review from @garyverhaegen-da and architecture review from @digital-asset/daml-docs

Looks OK on preview so gonna merge.


TypeError: this[#client].defaultMutationOptions is not a function

I installed Tanstack query 5, and when trying to create a post request i got this error
TypeError: this[#client].defaultMutationOptions is not a function

I guess it does not work with Tanstack query 5

the package does not support Tanstack Query 5 yet


grpc: 1.44.0 -> 1.45.2

Description of changes
https://github.com/grpc/grpc/releases/tag/v1.45.0
https://github.com/grpc/grpc/releases/tag/v1.45.1
https://github.com/grpc/grpc/releases/tag/v1.45.2
Required for #166489

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build murmur bear
@GrahamcOfBorg build sysdig libtensorflow

GRPC support in murmur is optional since c267e9ce37dd2f2f9975ab83c538a624f1fede50


Slow initialization of GLFW and OpenCL

Hi all,
My application performs computations for data on a geographical grid using OpenCL. GLFW is then used for displaying the results (pixel colors that represent the data values) in a window and for retrieving keyboard and mouse input.
I noticed that it took several seconds for the application to start up and I investigated what could be done to make it faster. It turned out that initializing OpenCL and GLFW took about 2 seconds. It's not really a big deal, but if I also add the time needed to e.g. (down)load data it becomes a bit noticeable. Remarkably, initializing only OpenCL takes 0.6 seconds and only GLFW 0.1 seconds (which is almost instantaneous), but initialiazing both amounts to 2 seconds and not 0.7 seconds. Is there anything that can be done to speed up the initialization?
Here is a minimal (no error checking or cleanup) example to reproduce the problem, using only OpenCL.lib and glfw3.lib. It is just an OpenCL function call and a call to glfwInit and glfwCreateWindow. Commenting out either the OpenCL call or the GLFW calls leads to the above observation.
#include <iostream>
#include <chrono>

#include <CL/cl.h>
#include <GLFW/glfw3.h>

int main()
{
	std::chrono::steady_clock::time_point begin = std::chrono::steady_clock::now();

	// OpenCL call
	clGetPlatformIDs(NULL, NULL, NULL);

	// Initialize GLFW and create window
	glfwInit();
	GLFWwindow* window = glfwCreateWindow(1920, 1080, "Test", NULL, NULL);

	auto startup_time = std::chrono::duration_cast<std::chrono::microseconds>(std::chrono::steady_clock::now() - begin).count() * 1e-6;
	std::cout << "Time difference = " << startup_time << " s" << std::endl;

	getchar();

	return 0;
}

Specs:

OS: Windows 10 Home 64 bit - version 22H2 - build 19045.3086
IDE: Microsoft Visual Studio Community 2022 (64-bit) - version 17.4.1
GLFW: version 3.3.8
OpenCL SDK: version v2023.04.17 (from https://github.com/KhronosGroup/OpenCL-SDK)
CPU: Intel(R) Core(TM) i7-4710MQ CPU
GPU: Intel HD Graphics 4600 + NVIDIA Quadro K1100M (last one is used in application)

Any advice/help is greatly appreciated.

Unplug/Re-plug your keyboard and mouse and any other usb device without restarting your pc, then run the app. You're welcome.

I don't think there's much we can do with this, as the performance impact is almost certainly in the OS or driver.
The only think I can think of which might help would be to initialize GLFW and create the window, then initialize OpenCL on a separate thread to avoid any impact on your user interface.


cleaned up grin-miner.toml

As I understand from the code the formerly sync mode for the miner doesn't exist anymore. Cleaned up the comment in grin-miner.toml. Also deleted one comment about activating the miner in the server.

Didn't find out how to commit changes to one file only... (yet)


Array method definition revamp: Use case collection

We've gotten numerous issue reports and PRs to change the methods of Array, particularly reduce, map, and filter. The built-in test suite doesn't cover these very well, and these methods interact with each other and the surrounding contextual type in fairly subtle ways.
@jablko has done a great job at #33645 collecting a variety of issues into a single PR; we need to augment this PR (or something like this) with a proper test suite so we can be sure about what's being changed.
I'd like to create a clearinghouse issue here to collect self-contained (I CANNOT POSSIBLY STRESS THIS ENOUGH, SELF-CONTAINED, DO NOT IMPORT FROM RXJS OR WHAT HAVE YOU) code samples that make use of the array methods.
Please include with your snippet:

Compiler settings
Compiler version you were testing with
The expected behavior (examples that should and should not produce errors are both useful)
No imports or exports; snippets need to be self-contained so that we can put them into our test suite without extra complications

Once we've established a critical mass of code snippets, we can start combining the existing PRs into an all-up revamp and assess its impact to real-world code suites to figure out which changes don't result in unacceptable breaking changes.
ｓｅｌｆ－ｃｏｎｔａｉｎｅｄ

([] as any[]).reduce(() => 0, 0); // Expected: number, Actual: any
([] as unknown[]).reduce(() => 0, 0); // Expected: number, Actual: unknown
([] as never[]).reduce(() => 0, 0); // Expected: number, Actual: number

@RyanCavanaugh This is caused by a mistake of the order of overloads. I made #36570 and looks like it makes no regression.

From a real-world code suite broken by #33645:
// Should not error
function add<A>(arr: Array<A>, el: A): Array<A> {
    return arr.concat(el)
}

@RyanCavanaugh Shouldn't it? If A is string[], arr is [["a"]] and el is ["b"] then add(arr, el) will return [["a"], "b"], which doesn't match the return type Array<A>?
Should that implementation be updated -> return arr.concat([el])?

@jablko good point. The actual code was in fp-ts and indeed they've removed it; the implementation now uses a loop instead https://github.com/gcanti/fp-ts/blob/master/src/Array.ts#L373

From a real-world code suite broken by #33645:
// Did not error; probably shouldn't in the future either
class A {
    flattenTree(option: any, changeOnSelect: any, ancestor = []) {
        let flattenOptions: any = [];
        const path = ancestor.concat(option);
        flattenOptions = flattenOptions.concat(this.flattenTree(option, changeOnSelect, path));
   }
}

This one should be simpler to demonstrate exactly what aspect of things got broken

@RyanCavanaugh I think this should be an error? The reason it currently doesn't error is because option: any is assignable to ConcatArray<never> (at const path = ancestor.concat(option)). However the only way the return type never[] is accurate is if option is [].
I think the flattenTree() signature needs to be ancestor: any[] = [], to be callable with the const path = ancestor.concat(option), where option can be something other than []? That, or the signature must be option: never[].

TypeScript Version:  3.8.x
Code
interface Bar {
    property: boolean;
}

let foo: ReadonlyArray<string> | Bar;
if (Date.now() === 0) {
    foo = { property: true};
} else {
    foo = ['Hello'];
}

if (Array.isArray(foo)) {
    console.log(foo[0]);
} else {
    console.log(foo.property); // <-- error
}

Expected behavior:
The else branch correctly understands that foo is of type Bar
Actual behavior:
TypeScript still thinks foo is ReadonlyArray<string> | Bar
Playground Link: link

@bpasero This has nothing to do with Array stuff:
let foo: boolean | string;
if (Date.now() === 0) {
	foo = true;
} else {
	foo = "hello";
}
foo; // still of type: boolean | string

Not possible without defining a specialized type "positive number" (no zero and even no negative value, no decimal points)

@HolgerJeromin I just did what @DanielRosenwasser suggested in https://github.com/microsoft/TypeScript/issues/37129#issuecomment-593661062 and posted my usecase here.

A lot of people use Array.reduce() to build mappings from lists:
type MyMapping = { [id: string]: 'A' | 'B' | 'C' }

const aMap: MyMapping = [1, 2, 3].reduce((acc, n) => {
  return { ...acc, [`id_${n}`]: 456 }
}, {})

I would expect this to not typecheck since 456 isn't of the type 'A' | 'B' | 'C'.
This currently typechecks with no errors in Typescript v3.8.3.

const a = [[1, 2, 3]].flat(); // number[]
const b = ([[1, 2, 3]] as const).flat(); // unknown[]

Also , we need Infinity literal type. Here is an example we use:

type Element<T> = {
  isArray: ArrayElem<T extends ReadonlyArray<infer E> ? E : never>;
  notArray: T;
}[T extends ReadonlyArray<any> ? 'isArray' : 'notArray'];

type ArrayElem<T> = T extends ReadonlyArray<any> ? Element<T> : T;

declare function flatInfinity<T>(x: T): Array<ArrayElem<T>>;

const c = flatInfinity(['foo', 1, 2, null, [5, [2], [3, {}, 4]]] as const); // ("foo" | 1 | 2 | 5 | 3 | 4 | {} | null)[]

map erases "tuple-ness" of an array (#29841):
type Vec3D = [number, number, number];
let vec: Vec3D = [1, 2, 3];
let scaledVec: Vec3D = vec.map(x => 2 * x); // error: Type 'number[]' is missing the following properties from type '[number, number, number]': 0, 1, 2

The following overload using mapped tuples can be defined as workaround (as seen in #29841):
declare interface Array<T> {
    map<U>(callbackfn: (value: T, index: number, array: T[]) => U, thisArg?: any): { [K in keyof this]: U };
}

Suggestion:
declare global {
  interface Array<T> {
    filter(filter: BooleanConstructor): Exclude<T, null | undefined | 0 | "" | false>[]
  }
}

In addition to @HoldYourWaffle's map use case, it would be great to support generic tuples of arbitrary arity:
interface Box<T> { value: T }
type BoxTuple<T> = { [K in keyof T]: Box<T[K]> }

const forBoxes = <T extends any[], TValue> (...boxes: BoxTuple<T>) => ({
  useValues: (callback: (v: T) => TValue) => {
    // Argument of type 'any[]' is not assignable to parameter of type 'T'.
    //   'any[]' is assignable to the constraint of type 'T',
    //   but 'T' could be instantiated with a different subtype of constraint 'any[]'.
    return callback(boxes.map((box) => box.value))
    // (Asserting the map call 'as T' fixes the error)
  }
})

const values = forBoxes(
  { value: 'Dog' },
  { value: 1 },
  { value: true }
).useValues(
  ([str, num, bool]) => `My boxes contain ${str}, ${num}, and ${bool}`
)

(Playground Link)

I would like concat.apply in _getEvents to work without the typecast of [] to ReadonlyArray.

export function _getEvents(
  nameSpec: string | RegExp | Array<string | RegExp>
): ReadonlyArray<string> {
  if (Array.isArray(nameSpec)) {
    const allStrings = ([] as ReadonlyArray<string>).concat.apply([], nameSpec.map(a => _getEvents(a)));
    const allUniqueStrings = Array.from(new Set<string>(allStrings).values());
    return [
      ...allUniqueStrings
    ];
  } else {
   // ...
  }

  return [];
}

I created #39259 . It appears that 2 of the signatures for reduce are colliding, which breaks inference for the return type of reduce in certain situations. It appears that the conflicting signatures are:
    reduce(callbackfn: (previousValue: T, currentValue: T, currentIndex: number, array: readonly T[]) => T, initialValue: T): T;
    reduce<U>(callbackfn: (previousValue: U, currentValue: T, currentIndex: number, array: readonly T[]) => U, initialValue: U): U;

It looks like the first can be dropped in favor of the second, as signature of the second covers the first.
Here is a playground link demonstrating the issue.

@jimador and I were looking at this one together.  Here is an even shorter repro path (playground link):
type SomeParamType = { hello: string; world: string; }

function broken<T>(arg: SomeParamType): boolean {
  // This is what's throwing the TypeError, seems like an inference issue here
  return Object.keys(arg).reduce(
    (previousValue, currentValue) => previousValue && !!currentValue,
    true
  )
}

function works(arg: SomeParamType): boolean {
  return Object.keys(arg).reduce<boolean>(
    (previousValue, currentValue) => previousValue && !!currentValue,
    true
  )
}

function alsoWorks(arg: SomeParamType): boolean {
  const value = Object.keys(arg).reduce(
    (previousValue, currentValue) => previousValue && !!currentValue,
    true
  )
  return value
}

I'm very interested to know what mechanism causes the first and third (broken and alsoWorks) examples to behave differently.

This has piqued my interest as well.

@julian-sf That's interesting, it looks like TS is downcasting (or just plain inferring) the return type as true and not boolean. If it's an inference problem, this should be reproducible.

Perhaps I'm missing something here, I'm not super experienced with more complex types, but this case looks impossible with TS right now.
I have a const array of strings. I want an object with those strings as keys.
const myKeys = ["foo", "bar"] as const
type TMyTypeWithMyKeys = {
    [key in typeof myKeys[number]]: string
}

//Type '{}' is missing the following properties from type 'TMyTypeWithMyKeys': foo, bar
const myObjWtihMyKeys: TMyTypeWithMyKeys = myKeys.reduce((obj, key) => ({ ...obj, [key]: "initialValue" }), {})

Desired behavior is for TS to infer the return type instead of just using the initial value as the return type.

@AndrewMorsillo,
The signature for reduce declares the return type of reduce as the type of the initial value ({} in this case). TS would have to execute the reduce function to infer the return type (kind of like a const exp?). If TS could do something like that, the type of the result would probably be { foo: 'initialValue'; bar: 'initialValue'} which still wouldn't match { foo: string; bar: string}

Perhaps I'm missing something here, I'm not super experienced with more complex types, but this case looks impossible with TS right now.
I have a const array of strings. I want an object with those strings as keys.
const myKeys = ["foo", "bar"] as const
type TMyTypeWithMyKeys = {
    [key in typeof myKeys[number]]: string
}

//Type '{}' is missing the following properties from type 'TMyTypeWithMyKeys': foo, bar
const myObjWtihMyKeys: TMyTypeWithMyKeys = myKeys.reduce((obj, key) => ({ ...obj, [key]: "initialValue" }), {})

Desired behavior is for TS to infer the return type instead of just using the initial value as the return type.

Technically you can achieve it with this:
const myKeys = ["foo", "bar"] as const
type TMyTypeWithMyKeys = {
    [key in typeof myKeys[number]]: string
}

const myObjWtihMyKeys = myKeys.reduce<TMyTypeWithMyKeys>((obj, key) => ({ ...obj, [key]: "initialValue" }), {} as any)

In Typescript 3.9.7.
function toStringArray(a: string[] | number[]) {
    return a.reduce((acc, v) => acc.concat(v.toString()), [] as string[]);
}

v should be inferred as string | number but ends up as any. Likewise, acc should be string[] but is any.
reduce has the error

Each member of the union type '{ (callbackfn: (previousValue: string, currentValue: string, currentIndex: number, array: string[]) => string): string; (callbackfn: (previousValue: string, currentValue: string, currentIndex: number, array: string[]) => string, initialValue: string): string; (callbackfn: (previousValue: U, currentValue: string, ...' has signatures, but none of those signatures are compatible with each other.ts(2349)

I believe that .map(…) operations on tuple types should still produce a tuple type.

Typescript version 4.0.5
This one is a little longer than other examples here (I'm sorry), but I haven't been able to recreate this with a simpler function.
The behaviour is very interesting though. Type inference for my groupBy utility works as I'd expect as long as the type of list elements don't have properties that are of type Array.
const groupBy = <K extends string, V>(func: (el: V) => K) => (
  acc: Record<K, V[]>,
  el: V
): Record<K, V[]> => {
  const key = func(el);
  return { ...acc, [key]: (acc[key] || []).concat(el) };
};

type A = { a: string; b: number };
const listA: A[] = [];
// 'el' is inferred to be of type 'A' as expected
const a = listA.reduce(groupBy(el => el.a), {});

type B = { a: string; b: string[] }; // Note that 'b' is a list
const listB: B[] = [];
// 'el' is inferred to be of type 'string | B'
const b = listB.reduce(groupBy(el => el.a),  {}); // Type error:  Property 'a' does not exist on type 'string | B'

The el argument is also inferred to be string | T if T has properties of type Record or indexed types (and maybe others)
I also found that manually deleting the following override from lib.es5.d.ts makes inference work as expected for both cases:
    reduce(callbackfn: (previousValue: T, currentValue: T, currentIndex: number, array: T[]) => T, initialValue: T): T;

With .split, it'd be nice if the return type reflected that the method always (with two caveats) returns an array with at least one string in it.  So the return type could be [string, ...string[]] instead of string[].
This would make code like this function better with the noUncheckedIndexedAccess flag:
// currently head is `string | undefined`, but in practice, it's always `string`
const [head, ...rest] = someString.split("/");

There are, AFAIK, two caveats:

someString.split(sep, 0); will return [], because to the limit being 0.
"".split("") returns []  not [""], because... "Life is pain, highness; anyone who tells you differently is selling something" or something.

Technically, those could be addressed with overloads, but at least the second one feels like a reasonable sacrifice of soundness for the sake of pragmatism.

TypeScript 4.1.2
except give a ts error, such as Type 'string' is not assignable to type 'string[]'.ts(2322)
let list:string[][] = [["a"]];
list = list.concat(["l"]);
// SHOULD ERROR, the actual content of list is
// [ [ 'a' ], 'l' ];

TypeScript 4.1.2
except give a ts error, such as Type 'string' is not assignable to type 'string[]'.ts(2322)
let list:string[][] = [["a"]];
list = list.concat(["l"]);
// SHOULD ERROR, the actual content of list is
// [ [ 'a' ], 'l' ];

@Retsam If we had a nice way to define a non-empty string (like we can with arrays) then you could address the soundness issue by overloading on non-empty input.

@Retsam If we had a nice way to define a non-empty string (like we can with arrays) then you could address the soundness issue by overloading on non-empty input.

@icecream17 [..._2Darray[a]] works, fwiw

Related to above, I'd expect slice() to clone an array and keep its type, but it doesn't keep type when min number of items is specified.
const array_one_or_more:[number, ...number[]] = [1, 2, 3]
const clone = array_one_or_more.slice()
clone[0].toString()  // Error because clone has become `number[]`

Related to the above, this old issue #33200 wasn't solved yet, instead, a workaround was offered, but it creates discomfort.
I've created the following PR to fix it (also, a better explanation about the problem was mentioned here): PR 45767.

Adding an interaction between flat and Promises
https://www.typescriptlang.org/play?target=8#code/IYZwngdgxgBAZgV2gFwJYHsI1JKAxAG2GQFlgAHAHgGUAaGAFQD4AKAKBhgDdgCEBTEAC4YAJX7AAJpgJgAggCcFwMDSa0OMALYURLHn34jqAShgBeJjAAKC9FtQh+lBjAA+YidIizFy1cxMbCYitvaOzuJSMvJKKi5MVgDemlCYIMgw5HYOTiAW3LwCIAB0OuQs5SYA3KnpmYgEcKgEBPySAGpFggXAAO7AqJlhufwlvAQs2eF5NZoK-MgICliNza3tXYalcETILHMAvkA
async function asyncFlatMap<S, T>(
  values: ReadonlyArray<S>,
  map: (value: S) => Promise<T | ReadonlyArray<T>>
): Promise<ReadonlyArray<T>> {
  const promises = values.map(map);
  const fulfilledValues = await Promise.all(promises);
  return fulfilledValues.flat(); // Type system doesn't realize this should be Array<T>
}

@kwasimensah That's a problem with the typing of the external function; T could be, for example, number[], in which case the .flat() would return a (number | number[])[]. You should instead type it like flat:
async function asyncFlatMap<S, T>(
  values: ReadonlyArray<S>,
  map: (value: S) => Promise<T>
): Promise<(T extends ReadonlyArray<infer U> ? U : T)[]> {
  const promises = values.map(map);
  const fulfilledValues = await Promise.all(promises);
  return fulfilledValues.flat();
}

I think we could introduce changes to some of these methods in a backwards-compatible way. Here's a definition of concat that I believe satisfies this:
declare interface Array<T> {
    concat<U>(this: Array<U>, ...items: ConcatArray<U>[]): Array<U>;
    concat<U>(this: Array<U>, ...items: (U | ConcatArray<U>)[]): Array<U>;
}

[1].concat('x')  // error as expected
[1].concat<number | string>('x')  // No error since type is explicitly widened

Playground: https://tsplay.dev/wXkDJW
I think this approach should work for most the Array methods in question.

I don't know if this is appropriate here, but i have just been bitten by this.
Imho, filter(), some(), every()... should only accept a predicate returning a boolean.
//strict compiler settings

const arr = [1, 2, 3];

const onlyPositives = arr.filter(num=>{
  num > 0 //forgot return, TS doesn't mind
});

console.log("onlyPositives", onlyPositives); // []  empty array

//isPositive has type (num:number)=>void
const isPositive = (num:number)=>{
  num > 0;
}

//filter should not accept a predicate not returning a boolean
const onlyPositives2 = arr.filter(isPositive);//no error that way either

Instead, the predicate type is actually returning unknown in the definitions.
Sorry if this has already been discussed to death, but i find this very unsound and i havn't been able to find a duplicate.

Imho, filter(), some(), every()... should only accept a predicate returning a boolean.

This would be a pretty big breaking change, as many people will use e.g. .filter(x => x) to remove falsy values (e.g. to remove null or empty strings).
Perhaps, instead, the type could be modified in some way to allow unknown but ban void? Perhaps an overload expecting a void return type with @deprecated You probably meant to return something?

@vjau You can also add the @typescript-eslint/no-unnecessary-condition lint rule - it tries to find dead conditionals and checks these array predicates.

This would be a pretty big breaking change, as many people will use e.g. .filter(x => x) to remove falsy values (e.g. to remove null or empty strings).

I was under the impression that it was idiomatic TS to write .filter(x => !!x) instead but after some research it seems i am probably confusing with another language.

Hey @RyanCavanaugh, please could I get https://github.com/microsoft/TypeScript/issues/41708 added to this so that #44216 can finally get merged/fixed.

playground link
Array methods such as splice, map, etc. when called on a subclass of Array, return a new instance of the subclass.
This might be related to Tuples losing their Tuple-ness when calling map, etc., but I'm not sure if that's the same issue. Tuples exist only in the type system, while a subclass exists at runtime, so I could see this potentially being a separate issue from the tuple issue.

Ah, I was not aware of that.

After looking further into https://github.com/tc39/proposal-rm-builtin-subclassing, it appears that support for "Type II: subclass instance creation in built-in methods" support is unlikely to be possible to remove without significant webcompat issues. One of the champions has even responded that the removal of type II is highly unlikely: https://github.com/tc39/proposal-rm-builtin-subclassing/issues/21#issuecomment-851566785.
In light of that, and the fact that the proposal is only stage 1, perhaps it would be prudent for Typescript to try to match the current behavior, rather than anticipate what seems to be a rather unlikely future behavior change?

lib.es2016.array.include.d.ts should not produce error when testing existence of an element that comes from a wider set of values that intersects with Array<T>.
playground link
declare const test1: 1
declare const test2: 1 | 2
declare const test3: 2 | 3
declare const test4: number

declare const array: (0 | 1)[]

array.includes(test1) // OK
array.includes(test2) // Argument of type '1 | 2' is not assignable to parameter of type '0 | 1'. Type '2' is not assignable to type '0 | 1'.(2345)
array.includes(test3) // Argument of type '2 | 3' is not assignable to parameter of type '0 | 1'. Type '2' is not assignable to type '0 | 1'.(2345)
array.includes(test4) // Argument of type 'number' is not assignable to parameter of type '0 | 1'.(2345)

In this example, the result of test2 and test4 is undesired as the test potentially can yield true value, much like the following snippet.
array.findIndex((v) => v === test1) // OK
array.findIndex((v) => v === test2) // OK
array.findIndex((v) => v === test3) // This condition will always return 'false' since the types '0 | 1' and '2 | 3' have no overlap.(2367)
array.findIndex((v) => v === test4) // OK

Disputably, some people may even argue that even test3 should not produce an error. ¯\(ツ)/¯

@ackvf See discussion in https://github.com/microsoft/TypeScript/issues/14520.

I hope this is not out of scope, but when one of the mentioned methods is called on a tuple of length n, the index parameter could be inferred as 0 | 1 | … | n -1 instead of just number. TS already knows the tuple length, and this really could be really useful when accessing other tuples of the same length and noUncheckedIndexedAccess is set to true.
Compiler settings: default, but with noUncheckedIndexedAccess set to true
Compiler version: 5.2.2
Example:
const aTuple = [ "a", "b", "c"] as const
const bTuple = [ "x", "y", "z"] as const

// These are both correctly inferred as exactly 3
const aLength = aTuple.length
const bLength = bTuple.length

type range = 0 | 1 | 2
const possibleIndex = 2 as range // This could be something like getRandomNumber(0,2)
// This is inferred as x | y | z and doesn't include undefined, as expected
const possibleAccess = bTuple[possibleIndex]

// This causes an error, because the return array could contain undefined
const test: string[] = aTuple.map((_, i) => {
  // With noUncheckedIndexedAccess=true access is inferred as possibily undefined,
  // but TS could/should know that the the index will always be 0 | 1 | 2, as above
  const access = bTuple[i]
  return access
})

Here is the playground

I would appreciate if Array.includes would behave like this:
interface Array<T> {
  includes(searchElement: unknown, fromIndex?: number): searchElement is T;
}

interface ReadonlyArray<T> {
  includes(searchElement: unknown, fromIndex?: number): searchElement is T;
}

it depends, the most you can guarantee is searchElement is T ? boolean : false since even if the type matches it's still possible for includes to return false:
const abcs: String[] = "abcs".split('')

abcs.includes("d") // > false, even though "d" matches type String

@karlismelderis-mckinsey Yeah this has been suggested before e.g. #31018 and there's some issues.  One is, like @icecream17 said it can return false even when searchElement actually is T- which would require #15048: a false result on the includes check can't be used to prove that searchElement isn't T.

But also, I think widening searchElement from T to unknown is problematic for other use cases.  There's two reasons to use includes:

You're using the string to check something about the array. e.g. if(colorArray.includes("red"))
You're using the array to check something about the string. e.g. if(["red", "blue", "green"].includes(maybeColor))

The type-guard signature you suggest is useful for #2, but makes #1 worse: if type Color = "red" | "blue" | "green" and colorArray is Color[], it's not great if colorArrray.includes("read") is accepted: that's a typo that's currently caught but wouldn't be if includes took unknown as its argument.

Personally, I suggest making a utility function for #2 and using it in place of arr.includes(val):
function includes<const S>(haystack: readonly S[], needle: unknown): needle is S {
    const _haystack: readonly unknown[] = haystack;
    return _haystack.includes(needle)
}

(For convenience type Sister = "Louisa" | "Isabella" | "Mirabel")
@dsongman Are you saying that the sisters array should be typed as Sister[] (which is the current type), but somehow remember that it was defined as satisfies Characters[] and change the signature of includes?
I don't think there's any plausible mechanism for that - ultimately the methods of arrays are defined by normal type system definitions:
interface Array<T> {
    includes(searchElement: T, fromIndex?: number): boolean
}

In this case T is Sister and so trying to pass Characters as searchElement doesn't work, for the reasons specified above, and satisfies can't change that.  Either T is Sister (as in the above code) or you can do const sisters: Characters[] = /*...*/ to have TbeCharacters`, but I don't think there's a way to have both.

Are you saying that the sisters array should be typed as Sister[] (which is the current type), but somehow remember that it was defined as satisfies Characters[] and change the signature of includes?

Yeah, that's right. Backing up to make sure I'm stating the problem and not necessarily the solution…
I find that in the application codebases I've worked in, a very frequent issue that comes up is wanting to define a list of values via a union and then iterating over those values in the UI somewhere. If you're okay with duplication, you can make a type that ensures an array contains all values of a union. If you want a single source of truth, though, the general consensus seems to be to define an array of thing things, add as const to it, and then you can derive the union via typeof myThing[number].
If, however, you want to define a subset of a union that is iteratable, there isn't a great solution. Using satisfies SuperType[] does a lot:

It ensures that your values conform to SuperType as you type them.
The subtype array or one of its values can be passed to functions that want SuperType[] or SuperType.  This seems to imply that the satisfies predicate holds, since the same is not true for the as const version of the same array (see this playground).

But while you can pass the subtype to functions that accept SuperType, you can't use includes to see if a member of SuperType is in the subtype, which seems odd.


Fix all tour examples from part 1

Fix all the Go examples for the Tour of Beam all the way until "Core Transformations". A subsequent PR will fix the rest of the examples.
beam.Init was missing on all the files making it impossible to run in the Playground.
Also, go fmt format wasn't respected on a lot of the files.
This fixes #30477 (partly)

R: lostluck

R: @lostluck

Only just saw this today. The original ping happened while I was on a boat. Thank you for your patience. Taking a look now.


Feature questions

Briefly summarize your issue:
Not a bug, just a question:
On the previous alexa-sample-app you said the Wakeword, Alexa, you would get a tone feedback indicating that it heard you and is listening for the question/command. Is there anything like this on the SDK? I liked having that feedback.
Thanks!
Tell us about your environment:
What version of the AVS Device SDK are you using?

Tell us what hardware you're using:

[ ] Desktop / Laptop
[X] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[X] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

Hi @rdoebler,
Thanks for asking. Our SDK currently does not support wake word notification. It's in our radar though.
Best,
Celina


Add section to links page about opening links in new tabs/windows

You want it to be a different template section or just an h4 tag and then the code block?

A new template section would be great


[BUG] commitInfo fields format's are not treated as optional

Bug
Describe the problem
Based on this comment from delta-io/delta-rs#1017 it would appear that the delta-spark implementation does not adhere to the protocol document with regards to the commitInfo field:

Implementations are free to store any valid JSON-formatted data via the commitInfo action.

Steps to reproduce
See linked comment above

Observed results

Expected results
I would expect that the commitInfo with any value JSON data to be read correctly.

Further details

Environment information

Delta Lake version:
Spark version:
Scala version:

Willingness to contribute
The Delta Lake Community encourages bug fix contributions. Would you or another member of your organization be willing to contribute a fix for this bug to the Delta Lake code base?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance from the Delta Lake community.
[x] No. I cannot contribute a bug fix at this time.

cc @ryan-johnson-databricks

AFAICT this is a bug. The Delta spec is very clear on this point.

That said, we probably need to update the Delta spec to be more clear: The commit info, if present, should be a JSON object rather than a primitive or array (today it just says "valid JSON-formatted data").
That way, parsers like spark know what to expect, since the six JSON data types all correspond to different spark types, and the spark read schema must choose just one since they are mutually incompatible:

JSON type
Spark type

string
StringType

number
DoubleType

object
MapType

array
ArrayType

boolean
BooleanType

null
NullType


Move .dll from lib to bin

The cupti build places both .dll and .lib in lib directory. Need to move .dll to bin so they can be detected when building downstream recipes.
Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender


Data Table

Epic
No response
Description

Acceptance Criteria
Data Table:

[x] Flexible framework to enable customisation of row content
[x] Render boolean values as ff-check
[x] Column Sorting (with toggle parameter to switch on/off)
[x] Actions slot, e.g. "Register Device"
[x] Optional search bar

That should filter on all columns? Configurable?

[ ] Pagination

How do we handle searching/pagination and async API calls?

Text Input:

[x] Allow for injection of icon via a via for the text-input (to be used for the search icon)

Updates to the docs so far:
https://user-images.githubusercontent.com/99246719/179993402-2a898b6e-a34c-43b3-a654-2693a0cf29d8.mov
Still need to add sorting & pagination

Sorting, ff-check and improved docs:
https://user-images.githubusercontent.com/99246719/180192921-0b1a595c-3eeb-4261-ab1b-473f0385f9e4.mov

Loading & No Data States:

"Load More" state


Editor config

We need a way to use the same code formatting without using any Resharper / VS files.
Of course, we need .editorconfig.

Great idea. Two things to remember here, on top of my head :

Include an install.ps1 script to deal with the existing .editorconfig file in the target project, if any. (Replace, merge, abort)
Make sure not to set these configs as root

@thatfrankdev I think there is a misunderstanding here. This issue is targeting this repository to ensure the uniformity of the whole Spk.Common codebase.
But yeah, it's also a good idea to bring a new package, let's say Spk.Common.EditorConfig that upon installation call the install.ps1 file and import configurations to a given repository. It would be neat.

@gabrielrobert Makes a lot more sense

#3 There we go @thatfrankdev!

Solved by #3


Wallet import form validation on address and passphrase

Hi, what do you think about adding form validation in wallet import for address and passphrase ? So that the user can see directly if he mistyped something or if there is anything wrong with the input.
I created form validators in a new folder src/validators, tell me if you think it belongs somewhere else.
Looking forward to hear your opinion on this ! Thanks.

I updated the word number validation.
Screenshots :

Invalid passphrase

Invalid address

Valid address


Cache key does not match, what problem could it be?

Hi, I've been using this library for a while, I created a celery task that runs every day at every hour sends an email if one of the checks fails.
It's always the "Cache Backend" that fails, but what do you mean it's not ok? why the check on the "Database Backend" is successful?

I'm having some problems with celery, I was trying to implement gevent for a performance optimization because with the base pool it eats too much ram and I'm afraid it will close my processes at random, running everything on Docker.
I cannot access the pc on which this healthy check is installed, I can only do it via VNC, remotely, and very often I notice that after the email arrives with the failing cache, the pc is no longer reachable via VNC, as if was crashed or frozen.
I opened a question about on stackoverflow but got no answer:
https://stackoverflow.com/questions/76357078/synchronousonlyoperation-from-celery-task-using-gevent-execution-pool-on-django

The cache backend is trying to set a key and get that key. If it's not able to do so, it will raise an exception.
        try:
            cache.set(self.cache_key, "itworks")
            if not cache.get(self.cache_key) == "itworks":
                raise ServiceUnavailable(f"Cache key {self.cache_key} does not match")

should print self.cache_key, but it just writes Cache key does not match. Could it be that it hasn't set any keys?

Yes, that is correct :)

ok but then the problem is not that he hasn't set any key to db, but that self.cache_key has no value

The value of the key is shown in the code above. "itworks" is the value being set to "self.cache_key".

It's saying that the value of the cache key does not match what was supposed to have been set, it's not trying to list the key's name at all.
You don't need to set it, by default it uses the key "djangohealthcheck_test".
Based on the issues you're describing at the top of the post:

You don't have Django's caching framework configured at all, if that is the case then you should not include the cache health check as it's always going to fail.
You do have cache setup, but it's configuration is broken or the cache (Redis, memcache, etc.) is not running


Nightly homebrew check

Test PRs into develop and nightly test of develop built using the Homebrew formula.
Nightly tests of develop built on macOS using Homebrew's build "formula" for OpenBLAS. This emulates the Homebrew binary build and distribution process so you will know if changes in Homebrew adversely impact OpenBLAS, and if changes in OpenBLAS will impede a quick release in Homebrew before minting a new release.

Is this using gcc or clang?

@isuruf

Is this using gcc or clang?

This is using whatever the instructions in the latest Homebrew formula are for openblas and building the develop branch only. Actually, come to think of it, this is not actually checking PRs and I should remove the PR condition. This will only check develop.
Currently/historically this was using the latest stable GCC and will continue to do so until https://github.com/Homebrew/homebrew-core/pull/50252 is merged into homebrew-core, at which point it will switch to native apple clang (unless the maintainers thing there is a good reason to stay with GCC, at which point we'll apply the patch you committed fixing the aarch64 issue or wait for the next release of OpenBLAS).
This nightly testing is effectively a light-weight emulation of our binary build process in Homebrew prior to releasing a new version of a package.

Once these workflows finish running on my fork, and I can see that they didn't have any issues I'll remove the draft status of this PR and mark ready for review.

If that's the case, then issues like https://github.com/xianyi/OpenBLAS/issues/2421 will not be uncovered right?

If that's the case, then issues like #2421 will not be uncovered right?

Guess I'll just refrain from causing such issues in the future if I can , one kind of useful nightly build is certainly much better than none. (And the original issue behind what caused #2421 was ultimately related to iOS compilation, which I think this PR does not address anyway)

one kind of useful nightly build is certainly much better than none

Definitely. I think if both gcc and clang builds can be added, that'll be more useful.

@martin-frbg

If that's the case, then issues like #2421 will not be uncovered right?

I am not sure I understand what you're asking.
This PR is designed to test develop, so that when a new release is tagged (based on develop, right?) there won't be any surprises when homebrew maintainers go to upgrade OpenBLAS to the latest release. This is what I was doing when I discovered #2421. So my entire purpose in opening this is to help you guys see when something on your end would break distributing the next release of OpenBLAS with Homebrew. Likewise, if a package OpenBLAS depends on i.e., gfortran (part of gcc in homebrew) or libomp does something to break OpenBLAS, or someone modifies the formula and causes breakage then you guys can report it to us over at Homebrew/homebrew-core. (And feel free to tag me.)
@isuruf

I think if both gcc and clang builds can be added, that'll be more useful.

As I explained above, my primary goal was to detect when there might be an otherwise undetected interaction between changes in OpenBLAS with Homebrew packaging and distribution of OpenBLAS, or upstream dependency or Homebrew issues  breaking OpenBLAS.
Nevertheless, if you really want me to, I can add an additional nightly test that builds OpenBLAS' develop branch using the other C/C++ compiler and Homebrew's formula. This may end up being fragile, and a wacky thing to do, because we don't officially support compilation with a compiler that's different than the one specified in the formula.
So, assuming we decide to merge https://github.com/Homebrew/homebrew-core/pull/50252 as is and switch to using Apple Clang, then the tests I added as they currently stand will automatically switch to using what Homebrew uses. If you really want me to, I can add testing that is similar to this, but builds OpenBLAS with either the latest stable GCC---assuming the OpenBLAS upgrade PR goes through in its current state---or Apple Clang if it is decided that Homebrew wants to keep building OpenBLAS with GCC for some reason. i.e., what is here now tests the way homebrew builds OpenBLAS and I'll add a build using homebrew with whatever the other C compiler would be. Note that all Fortran is built with gfortran.
Let's wait and see what happens with https://github.com/Homebrew/homebrew-core/pull/50252. If it goes through in its current state and you would like me to add macOS testing of OpenBLAS built with the latest GCC using the homebrew "formula" then I will add it at that time.

The action running on my branch looks good: https://github.com/zbeekman/OpenBLAS/actions/runs/40818440
I'll mark this as ready for review to remove the draft status. Once it's running, I can submit a PR to add a status badge, if that's of interest.

@zbeekman I was just quoting isuruf's comment , that was not a question from me.
FYI releases currently get tagged on the 0.3.0 branch (after merging changes from develop), not on develop itself. This oddity came about as xianyi put me in control of the release process, back then a 0.3.0 branch was created for this purpose (also resulting in master gathering dust).

PPC test failure on Travis-CI, but must have been present before since I did not touch any code.

Yep, that is a pre-existing bug uncovered by a new test merged earlier today. #2427 will take care of it.

Appveyor seems to be sleeping but would not be affected by this commit anyway, so merging now.

Unfortunately the homebrew check is now failing with "Error: your xcode(11.3.1) is outdated" and I have no idea how to fix this as xcode itself is not mentioned anywhere in the script @zbeekman ?

Tried to address this in 4412ee1 by setting the DEVELOPER_DIR variable to the latest version (11.4) that is installed rather than the default 11.3.1, so hopefully fixed for now.


Frontpage design

IANAD (I am not a designer)
Let's try with some open-source style designing of the initial website.

Inspiration

CopenhagenJS
js.la
sandiego.js
Manila.js
Berlin.JS
FranceJS
LyonJS
NantesJS
PragueJS
JavaScript Zagreb
Kopi.JS

I quite like the simplistic approach that CopenhagenJS, Kopi.JS, js.la and Berlin.JS takes, basically just the following views:

Frontpage

Logo, description
Next meetup details(time, location, attendees and agenda)
Organizers(contact info) and sponsors
Meta data(twitter, GitHub, etc.)

List of past events
Single meetup/event view

Details about the particular event(time, location, etc.)

I'm okay with just doing a quick prototype for the frontpage, but it would be great if anybody has some kind of creative skills (I definitely don't :stuck_out_tongue_winking_eye:)
@javascriptmy/core am I missing any important info?

I just quickly did a small mashup of [CopenhagenJS] and [Kopi.JS]:

It's just a quick Balsamiq file, if anybody wants to play around with it.

Comic. Sans. Do you have a death wish or something?

@soggie haha, it's actually not Comic Sans - and just the basic Balsamiq sketch mockup format.
Quite like the low fidelity of Balsamiq mockups, very easy to quickly piece things together.

Are we missing anything from that mockup?
Like super important features?

Looks fine so far, but I'd have the map in full width, front and center. I actually quite like BerlinJS' design, with empty slots as a call for action for speakers. I can do that actually. Maybe we need to integrate Ghost as well.

I think it would be cool to have speaker profile as well that would link to their personal github/fb/twitter pages.

Yeah I like the slots for speakers and profiles with social media links is a great idea!
For older events, it would also be cool to link to speakerdeck/slideshare or whatever if the slides are public.

+1 on speakerdeck/slides/video

Perhaps adding a slack room to allow attendees have some discussion?

@huei90 we're already on slack. Ask access from @soggie.

@huei90 or check out: https://javascriptmy-slack.herokuapp.com/ - (completely untested)


Drawing  ui - circle settings in a dialog;

Description
Layer Drawing UI
Circle drawing current settings are displayed in a dialog when the button in the drawing panel is hit.
They can be changed or reused before drawing interaction starts - or can be cancelled.
Putting these settings within an expandable panel is not clear that anything important is nested there
so showing default/recent settings to the user is a possible solution to both accessibility and clear layout in the panel.

GitHub Issue
Provide the link to the relevant GitHub issue it addresses.
Type of Change
Please delete options that are not relevant, and select all options that apply.

✅ Bug fix (non-breaking change which fixes an issue)
✅ New feature (non-breaking change which adds functionality)

An issue needs to be created or assigned to this pr


IDF 5.0 Docker image doesn't contain led_strip common component or blink example (IDFGH-9258)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I generated the blink example program from the ESP-IDF VSCode plugin and it doesn't seem to be supported by common_components libraries provided in this docker image: link

The led_strip component was uploaded to the Espressif Component Registry since 5.0. Check this out for how to use the component manager in your project.
FYI, the official blink example is also using this way: https://github.com/espressif/esp-idf/blob/master/examples/get-started/blink/main/idf_component.yml#L2


FORBID WORDS

How can I do so that each rank can use certain forbidden names, even though they all have the same forbidden names in common

@gyeyoqu This question is similar to https://github.com/Megabyte918/MultiOgar-Edited/issues/187, the code from there should also add what you are asking.

not help me.

That code allows admins/mods to use specific words or tags that normal players cannot, that's what you wanted, right?


[5863] Backfill trainees with old specialist subject

Context
For 2023 to 2024 we are removing the concept of Specialist teaching from Register. This generally means Primary with mathematics. We need to sort out trainees in the database with the old subject and move them to the new one.
Changes proposed in this pull request

Data migration to sort out old trainees who have their subject set to specialist teaching (primary with mathematics)
Recalculates their subjects and allocation subject

Guidance to review

Pull down prod dump and run the migration separately then check the records

We are still waiting for confirmation on how far back we should go with cleaning the records.

Closing in favour of https://github.com/DFE-Digital/register-trainee-teachers/pull/3568


Support LLVM 15.0.0 and 15.0.6.

Support LLVM 15.0.0 and 15.0.6. Also fix a failure in utils/llvm_chec…ksums.sh on Ubuntu.

The test failure doesn't seem related to my PR.  Is it a known issue?

The test failures seem to be separate. I will look into them later. They are meant to fail when we are not compatible with changes in external dependencies.
For your note on compression support in wget, I have removed it. I may have been experimenting with something when I added those lines, but because the download archive is already compressed, that flag should not have much of an effect. There were some other leftovers in that commit from my experimentation. Thanks for noticing it and taking the time to say something.

The failing tests are now fixed on master through 6e282e9b760520b238a1564989141106a1b7b794.

0.8.1 is now out and has this change.


Consistent in printing errno messages (IDFGH-6447)

Thanks for your contribution.

@Caffreyfans Thanks for contribution again, the changes have been merged with https://github.com/espressif/esp-idf/commit/2c0d7608160e042d566fd85d6dacb78edea14c2f, feel free to reopen.


Metadata API: Root.consistent_snapshot should be optional

Spec:

Finally, the root metadata should write the Boolean "consistent_snapshot" attribute at the root level of its keys of attributes. If consistent snapshots are not written by the repository, then the attribute may either be left unspecified or be set to the False value. Otherwise, it must be set to the True value.

Metadata API (tuf/api/metadata.py) seems like it would fail to read json that does not contain "consistent_snapshot"

Doesn't that mean that consistent_snapshot should be an optional attribute in the spec?
It is not at the minute.

Yes you're right I think, although it should probably be phrased so that new implementations should include it in new versions of metadata but that old metadata may exist without it


Ability to prevent yum -y update execution during node driver provisioning of RHEL/CentOS hosts

What kind of request is this (question/bug/enhancement/feature request):
Enhancement
Steps to reproduce (least amount of steps as possible):
The rancher-machine provisioner code for RHEL/CentOS hosts currently performs sudo -E yum -y update -x docker-* during node provisioning (https://github.com/rancher/machine/blob/f675ca219acb7402720f060432bc81e9032f6e85/libmachine/provision/redhat.go#L155). Where users are pre-configuring an OS template with Docker and dependencies pre-installed and want a deterministic package state, according to the configured OS template, the yum update here prevents this.
(This is noted in https://github.com/rancher/rancher/issues/22048 which is a single issue for two separate enhancement requests).
Environment information

Rancher v2.4.3

gz#10649
gz#13674
gz#13530

Discussion today about this, basics here should be a skip provision for the create command which will bypass all provisioning and docker installation. needs to be documented that the expectation is the user has already pre-installed everything they need to have installed docker themselves.

To test this, you will need an image that has docker pre-installed (ideally using our script https://releases.rancher.com/install-docker/19.03.sh). I have 2 AMIs already setup for ubuntu and redhat, so if you want to use those let me know.
Additionally, you will need to enter "none" as the Docker Install URL in the Engine Options when creating a node template.

To test this, you will need an image that has docker pre-installed (ideally using our script https://releases.rancher.com/install-docker/19.03.sh). I have 2 AMIs already setup for ubuntu and redhat, so if you want to use those let me know.
Additionally, you will need to enter "none" as the Docker Install URL in the Engine Options when creating a node template.

I was able to test the following on rancher v2.5-head (e3128c99ce74dc41ce319a42b21ebc829c74a84d):

custom RHEL with docker v20.10, Docker Install URL left as default value ->  provisioned successfully
custom RHEL with docker v20.10, changed Docker Install URL to none -> provisioned successfully
Ubuntu with docker 19.03., Docker Install URL = none -> unable to provision successfully (expected)
Ubuntu with docker 19.03 , Docker Install URL left as default value -> provisioned successfully

I was able to test the following on rancher v2.5-head (e3128c99ce74dc41ce319a42b21ebc829c74a84d):

custom RHEL with docker v20.10, Docker Install URL left as default value ->  provisioned successfully
custom RHEL with docker v20.10, changed Docker Install URL to none -> provisioned successfully
Ubuntu with docker 19.03., Docker Install URL = none -> unable to provision successfully (expected)
Ubuntu with docker 19.03 , Docker Install URL left as default value -> provisioned successfully

Reopening for validation to be done on master-head

Reopening for validation to be done on master-head

I also was able test the following on rancher master-head (68f4fa8e06d5d3850d68e8489691a7efbc612982):

custom RHEL with docker v20.10, Docker Install URL left as default value -> provisioned successfully
custom RHEL with docker v20.10, changed Docker Install URL to none -> provisioned successfully
Ubuntu with docker 19.03., Docker Install URL = none -> unable to provision successfully (expected)
Ubuntu with docker 19.03 , Docker Install URL left as default value -> provisioned successfully

I also was able test the following on rancher master-head (68f4fa8e06d5d3850d68e8489691a7efbc612982):

custom RHEL with docker v20.10, Docker Install URL left as default value -> provisioned successfully
custom RHEL with docker v20.10, changed Docker Install URL to none -> provisioned successfully
Ubuntu with docker 19.03., Docker Install URL = none -> unable to provision successfully (expected)
Ubuntu with docker 19.03 , Docker Install URL left as default value -> provisioned successfully


Removing self from no-modules target

Some JS targets don't have self, so this removes self from the no-modules target.
The behavior should be the same, it still creates a global wasm_bindgen variable and assigns to it.
This is accomplished by creating the variable outside of the function and then assigning to it inside the function.

Thanks!


Fail to found unittest in hello-stackoverflow folder.

Environment data

Steps to reproduce:
Git clone https://github.com/qubitron/pydemo
Open Anaconda Prompt window
Cd pydemo
Run py -3 setup.py
Open hello-stackoverflow folder
Press "Ctrl+Shift+p" to select "Run All Tests"
Make sure a prompt is popup
Click "Enable and configure a Test Framework"
From the menus select "Unittest framework->Tests folder->Test_*.py" file
Expected behaviour
The unittest should be found successfully.
Actual behaviour
No test discovered error message pops up.

At the same folder, we create a new file and input some code. It can find unittest successfully.

Thanks for the bug report! We just wanted to quickly acknowledge we received it and we will triage this as soon as we can.


Mypipe with AmazonRDS

Can I use mypipe to extract logs from Amazon RDS.If its possible,how can I achieve that.Any reference links will be highly helpfu

See also https://github.com/shyiko/mysql-binlog-connector-java/issues/78.

I don't use Amazon RDS myself, but perhaps someone else does and can help you out. Let us know what you find out if you try it out, you can use the mailing list.


chainlit_ui.py ERROR: Connection pool is full

Error as below. Not sure it's from crewai or praisonai. Need help, thanks!!
2024-06-21 12:16:31 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:31 - Context impl SQLiteImpl.
2024-06-21 12:16:31 - Will assume non-transactional DDL.
2024-06-21 12:16:32 - Context impl SQLiteImpl.
2024-06-21 12:16:32 - Will assume non-transactional DDL.
2024-06-21 12:16:32 - Context impl SQLiteImpl.
2024-06-21 12:16:32 - Will assume non-transactional DDL.
2024-06-21 12:16:32 - Context impl SQLiteImpl.
2024-06-21 12:16:32 - Will assume non-transactional DDL.
 [2024-06-21 12:16:32][DEBUG]: == Working Agent: Concept Researcher
 [2024-06-21 12:16:32][INFO]: == Starting Task: Research existing literature, articles, and real-world scenarios of AI and human interactions to uncover potential conflicts and resolutions.
2024-06-21 12:16:33 - HTTP Request: POST https://api.openai.com/v1/chat/completions "HTTP/1.1 200 OK"
2024-06-21 12:16:33 - 'generator' object does not support the context manager protocol
Traceback (most recent call last):
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/chainlit/utils.py", line 44, in wrapper
    return await user_function(**params_values)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/free/chainlit-gongan/app.py", line 194, in main
    result = agents_generator.generate_crew_and_kickoff()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/praisonai/agents_generator.py", line 269, in generate_crew_and_kickoff
    response = crew.kickoff()
               ^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/crew.py", line 271, in kickoff
    result = self._run_sequential_process()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/crew.py", line 357, in _run_sequential_process
    output = task.execute(context=task_output)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/task.py", line 187, in execute
    result = self._execute(
             ^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/task.py", line 196, in _execute
    result = agent.execute_task(
             ^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/agent.py", line 243, in execute_task
    result = self.agent_executor.invoke(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain/chains/base.py", line 163, in invoke
    raise e
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain/chains/base.py", line 153, in invoke
    self._call(inputs, run_manager=run_manager)
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/agents/executor.py", line 128, in _call
    next_step_output = self._take_next_step(
                       ^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain/agents/agent.py", line 1138, in _take_next_step
    [
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain/agents/agent.py", line 1138, in <listcomp>
    [
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/crewai/agents/executor.py", line 192, in _iter_next_step
    output = self.agent.plan(  # type: ignore #  Incompatible types in assignment (expression has type "AgentAction | AgentFinish | list[AgentAction]", variable has type "AgentAction")
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain/agents/agent.py", line 397, in plan
    for chunk in self.runnable.stream(inputs, config={"callbacks": callbacks}):
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 2875, in stream
    yield from self.transform(iter([input]), config, **kwargs)
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 2862, in transform
    yield from self._transform_stream_with_config(
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 1881, in _transform_stream_with_config
    chunk: Output = context.run(next, iterator)  # type: ignore
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 2826, in _transform
    for output in final_pipeline:
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 1282, in transform
    for ichunk in input:
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 4736, in transform
    yield from self.bound.transform(
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/runnables/base.py", line 1300, in transform
    yield from self.stream(final, config, **kwargs)
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/language_models/chat_models.py", line 249, in stream
    raise e
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_core/language_models/chat_models.py", line 229, in stream
    for chunk in self._stream(messages, stop=stop, **kwargs):
  File "/home/songz/miniconda3/envs/free-cl-gongan/lib/python3.11/site-packages/langchain_openai/chat_models/base.py", line 480, in _stream
    with self.client.create(messages=message_dicts, **params) as response:
TypeError: 'generator' object does not support the context manager protocol
2024-06-21 12:16:34 - Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10
2024-06-21 12:16:34 - Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10
2024-06-21 12:16:34 - Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10

I am also getting this error, but it doesn't seem to break anything. I didn't notice it the first time I tried to get the app to complete a task, but now I see it every time.
2024-06-21 11:27:22,507 -<PHONE_NUMBER>6 - connectionpool.py-connectionpool:329 - WARNING: Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10
2024-06-21 11:27:22,528 -<PHONE_NUMBER>0 - connectionpool.py-connectionpool:329 - WARNING: Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10
2024-06-21 11:27:22,534 -<PHONE_NUMBER>8 - connectionpool.py-connectionpool:329 - WARNING: Connection pool is full, discarding connection: us-api.i.posthog.com. Connection pool size: 10

Agree, the problem suddenly shows up from nowhere, then it's everywhere now.

@yiouyou I have fixed this in the latest release
pip install -U "praisonai[ui]"
Please let me know if you still find any issues. Thanks


Backup Copy Job error "Could not find a handler for job type ''

I'm using this script to check the status for 2 Backup Jobs and 1 Backup Copy Job running on Veeam 12
Both the Probe and the Backup Server are 2019 in the same domain.
I have no Problem with the backup Jobs and I'm getting the corrct results in PRTG
Howerver I can't figure out the Problem with the Backup Copy Job and keep getting the error  "Could not find a handler for job type"
1st I thought the Problem is because the Backup Copy Job is set to run after one of the backup Jobs (as new restore Point appears) so I changed the setting and set it to run separately on a different day, but that didn't solve the problem.
Any Idea how to solve this?

Is that the complete text of the error message?
The error message is supposed to include the name of the job type in it as well
https://github.com/lordmilko/PrtgSensors/blob/d5e1ebfb960cc4bd2fe5b85b4c81490345b3bf75/scripts/Get-VeeamBackupStatus.ps1#L609
If it's not including the job type, this may indicate that the structure of Veeam's objects have changed and that there *is no jobType` field anymore. If this is the case, I can't remember whether we're using Veeam 11 or 12 at my workplace, but I'll be back at work in 2 weeks, and can investigate then

running the script from cmd using PSx64.exe results in the same error:
C:\Program Files (x86)\PRTG Network Monitor\Custom Sensors\EXEXML>PSx64 -f=Get-VeeamBackupStatus.ps1 -p=backup1.mydomain.local BCJ-DC1
DEBUG: Entered Main
DEBUG: Entered [VeeamBackupStatus]::GetStatus
DEBUG: Entered [VeeamBackupStatus]::GetStatusInternal
DEBUG: -Loading Veeam PSSnapIn
DEBUG: -Connecting to Veeam Backup Server
DEBUG: Entered [VeeamBackupStatus]::GetBackupsToProcess
DEBUG: Entered [VeeamBackupStatus]::GetBackupHandler
DEBUG: -Using backup handler [UnknownJobTypeBackupHandler]
DEBUG: Entered [UnknownJobTypeHandler]::GetStatus
DEBUG: -Testing Backup as Tape Job

1
Could not find a handler for job type ''

Sensor results

Hello,
I just wanna check if there are any Updates regarding this error

I checked and saw we're using Veeam 11 at work, and due to some other things going on don't currently have the bandwidth to upgrade to Veeam 12, ensure everything still works, etc and then investigate this issue. When we do upgrade to Veeam 12 the script will probably break for me and I'll investigate what's up
As noted on the readme

This script can and will break with any given Veeam update

be prepared to get your hands dirty when it breaks.

If you open the script up in the PowerShell ISE, set a breakpoint on line 60 in the Main function and then step in (PowerShell ISE sometimes freaks out when you try and set breakpoints inside classes) you may be able to inspect the $backup variable when you get to line 172, which may provide some clues to whether the JobType property still exists or has been renamed, etc


Update mounted check to support symlink paths

Description
This change modifies the mounted check to resolve any symlinks so the grep on /proc/mounts will find any mounted devices.
Issues Resolved
#129 - filesystem tries to run mkfs every time when /dev/disk/by-id device path is used
Check List

[x] A summary of changes made is included in the CHANGELOG under ## Unreleased
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable.

Taking #132 over this, thanks for your PR!


The model to consider.
Hi. Could you add support to mistralai/Codestral-22B-v0.1?
Thanks!
The closest model vllm already supports.
https://huggingface.co/meta-llama/CodeLlama-7b-hf
https://huggingface.co/mistralai/Mistral-7B-v0.3
What's your difficulty of supporting the model you want?
Can't load Codestral-22B-v0.1 using OpenAI server API
ORG="mistralai"
MODEL="Codestral-22B-v0.1"
API_KEY=XXXXXXXXXXXXXXXXXXXXXX

python -m vllm.entrypoints.openai.api_server \
       --tokenizer $ORG/$MODEL \
       --model $ORG/$MODEL \
       --served-model-name $MODEL \
       --tensor-parallel-size 4 \
       --gpu-memory-utilization 0.9 \
       --max-model-len 4096 \
       --enforce-eager \
       --api-key $API_KEY

@eduardozamudio can you please share the version of vLLM used and the error of why the model won't load? It is a MistralForCausalLM, so I would expect it to run as Mistral models do.

Hi @eduardozamudio (Hola Eduardo!)
mistralai/Codestral-22B-v0.1  worked for me using vllm 0.4.3.
Regards
Matias

Hi @eduardozamudio (Hola Eduardo!)
mistralai/Codestral-22B-v0.1 worked for me using vllm 0.4.3.
Regards Matias

Does it work for "fill in the middle" https://huggingface.co/mistralai/Codestral-22B-v0.1#fill-in-the-middle-fim? I image there would be some work required to support that.

@eduardozamudio can you please share the version of vLLM used and the error of why the model won't load? It is a MistralForCausalLM, so I would expect it to run as Mistral models do.

I've updated to v0.4.3 and still getting the error.

The model to consider.
Hi. Could you add support to mistralai/Codestral-22B-v0.1?
Thanks!
The closest model vllm already supports.
https://huggingface.co/meta-llama/CodeLlama-7b-hf https://huggingface.co/mistralai/Mistral-7B-v0.3
What's your difficulty of supporting the model you want?
 Could it be a dependency problem?
[rank0]: Traceback (most recent call last):
[rank0]:   File "<frozen runpy>", line 198, in _run_module_as_main
[rank0]:   File "<frozen runpy>", line 88, in _run_code
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/entrypoints/openai/api_server.py", line 196, in <module>
[rank0]:     engine = AsyncLLMEngine.from_engine_args(
[rank0]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/engine/async_llm_engine.py", line 395, in from_engine_args
[rank0]:     engine = cls(
[rank0]:              ^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/engine/async_llm_engine.py", line 349, in __init__
[rank0]:     self.engine = self._init_engine(*args, **kwargs)
[rank0]:                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/engine/async_llm_engine.py", line 470, in _init_engine
[rank0]:     return engine_class(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/engine/llm_engine.py", line 235, in __init__
[rank0]:     self._initialize_kv_caches()
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/engine/llm_engine.py", line 312, in _initialize_kv_caches
[rank0]:     self.model_executor.determine_num_available_blocks())
[rank0]:     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/executor/distributed_gpu_executor.py", line 38, in determine_num_available_blocks
[rank0]:     num_blocks = self._run_workers("determine_num_available_blocks", )
[rank0]:                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/executor/ray_gpu_executor.py", line 246, in _run_workers
[rank0]:     driver_worker_output = self.driver_worker.execute_method(
[rank0]:                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/worker/worker_base.py", line 149, in execute_method
[rank0]:     raise e
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/worker/worker_base.py", line 140, in execute_method
[rank0]:     return executor(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/worker/worker.py", line 154, in determine_num_available_blocks
[rank0]:     self.model_runner.profile_run()
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/worker/model_runner.py", line 833, in profile_run
[rank0]:     self.execute_model(seqs, kv_caches)
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
[rank0]:     return func(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/worker/model_runner.py", line 738, in execute_model
[rank0]:     hidden_states = model_executable(
[rank0]:                     ^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/model_executor/models/llama.py", line 371, in forward
[rank0]:     hidden_states = self.model(input_ids, positions, kv_caches,
[rank0]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/model_executor/models/llama.py", line 288, in forward
[rank0]:     hidden_states, residual = layer(
[rank0]:                               ^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/model_executor/models/llama.py", line 223, in forward
[rank0]:     hidden_states = self.input_layernorm(hidden_states)
[rank0]:                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1532, in _wrapped_call_impl
[rank0]:     return self._call_impl(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/nn/modules/module.py", line 1541, in _call_impl
[rank0]:     return forward_call(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/model_executor/custom_op.py", line 13, in forward
[rank0]:     return self._forward_method(*args, **kwargs)
[rank0]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/model_executor/layers/layernorm.py", line 62, in forward_cuda
[rank0]:     ops.rms_norm(
[rank0]:   File "/home/jovyan/ezamudio/vllm/vllm/_custom_ops.py", line 132, in rms_norm
[rank0]:     torch.ops._C.rms_norm(out, input, weight, epsilon)
[rank0]:     ^^^^^^^^^^^^^^^^^^^^^
[rank0]:   File "/root/miniconda3/envs/vllm/lib/python3.11/site-packages/torch/_ops.py", line 921, in __getattr__
[rank0]:     raise AttributeError(
[rank0]: AttributeError: '_OpNamespace' '_C' object has no attribute 'rms_norm'

@eduardozamudio it seems like you have built vllm from source, so it is possible your environment has not built the library correctly. Could you try installing the pre-built package from pypi to confirm you don't see this issue on the actual release?

@eduardozamudio it seems like you have built vllm from source, so it is possible your environment has not built the library correctly. Could you try installing the pre-built package from pypi to confirm you don't see this issue on the actual release?

Excellent!
I confirm that the issue is not present anymore using the pre-built package.
Thanks @mgoin!


[Feature]: diable auto add header temporarily

I am wondering whether the plugin can provide a command to temporarily disable auto add header for this buffer.
Could be useful when editing small files that will be placed at places that won't prefer a header, like latex or ppt.

I was thinking about this as well. This plugin saves me time overall, though, I have found that I do not need/want it more often than I do. The solution to this was to set the following option accordingly.
let g:header_auto_add_header = 0

The problem
The problem here is that I often forget that I have this plugin installed and end up writing headers by hand when I want them in a specific file. Another thing I noticed, when g:header_auto_add_header = 0 the timestamps on existing headers do not automatically update on close, which makes sense when you look at how the timestamps are implemented in the source code (It's done by calling :AddHeader on file save, which is smart because that is more or less what you want to do).
Technically the [Feature:] you are requesting is already implemented. There is a:

command to temporarily disable auto-add header for this buffer

There is no issue with the way it is implemented other than laziness of us users, we don't want to have to manually enable and disable the auto-add-header feature in our .vimrc dependant on when we want to use it. That said there are alternate ways to implement this in a more automatic feeling way.
Possible solutions
Given that the implementation itself is present already, it doesn't make a lot of sense to modify the project itself. I thought about maybe adding the functionality to check if a header is currently present on save; if it is, update it; if it is not, do nothing; then you could manually add the header when you want them and they would be automatically updated when the file is changed, but while thinking about it I cam up with a few alternate solutions. That said here are a few solutions I have come up with:

Add auto-cmd cases for specific filetypes in your .vimrc to run AddHeader on the creation of files with specific extentions. There will still be the occasional situation where this ends up being wrong, but at least you can minimize the number of times you need to manually add/remove headers.
Implementation:
Add the following to your .vimrc:

    let g:header_auto_add_header = 0

    " Add all file extensions that you want the headers to be auto-added
    autocmd BufRead,BufNewFile *.sh,*.cpp,*.h,*hpp :AddHeader

Add the headers manually and don't use the modified time module. Given that the places where a date last modified are valuable/required, you are likely using git, which will keep track of all that information for you (and a whole lot more). In my experience when I actually want to know this information about a file, the last place I check is in the actual file header, under the basis that not everyone uses headers, therefore using ls of git is the only way to guarantee to get that information. I, like many other people, save every file I open before closing it. That means that every time you save a file, :AddHeader is being run, which means that the "Last Modified Date:" is being updated even if no actual changes were made.

Create a vim function that checks for the "Last Modified Date" line and updates that to the current date on file save.

Remember to manually run :AddHeader each time a change is made.

Conclusion
The correct solution heavily depends on your personal preference.


Is there any way to get it to work with START_PRINT instead of PRINT_START

Simply put, my creality K1 uses START_PRINT instead of PRINT_START, but the extruder and bed temp g-code are the same. I'm just wondering if there's a workaround to this because I would like to try this out

you can change the name of this macro easily in the Firmware!
Do you have any restrictions in your printer's firmware?

Maybe I should include in the next version a field to give the user the possibility to choose the name of this macro!

Yeah, that would be nice after digging through configs I have found the macro and I have duplicated it and changed the name, but it would be nice to keep it stock.

@skullbone Could you confirm if this issue can be Closed ?


Ability to toggle storeRootToken from CR (#1497)

Q
A

Bug fix?
yes

New feature?
yes

API breaks?
no

Deprecations?
no

Related tickets
fixes #1497, fixes #1516

License
Apache 2.0

What's in this PR?
Ability to set storeRootToken in CR.
Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

To Do

[x] Update docs
[x] Possibly identify that the same Cobra-related issue is not referenced elsewhere

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

will this option be available in the next '1.14.5' release only?

Yes I will compile a release today!


[BUG] Invalid shape when multiplying lake_masks and gdal

Describe the bug
When I try to run this command: ariaTSsetup.py -f ../products/\*.nc -b 29.8459\ 29.8506\ -98.2566\ -98.247 -nt all --mask Download, I run into a bug which prevents me from downloading the water masks.
To Reproduce
Steps to reproduce the behavior:

Download the files using ariaDownload.py --track 107 -b "29.8459 29.8506 -98.2566 -98.247" --start 20210101.
Command used: Feed the downloaded products to ariaTSsetup.py with the same bounding box and try to download the water masks
Error Output:

/home/arampal/tools/miniforge/envs/ARIA-tools/bin/ariaTSsetup.py:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  __import__('pkg_resources').require('ARIAtools==1.1.6')
ARIA-tools Version: 1.1.6
*****************************************************************
*** Time-series Preparation Function ***
*****************************************************************
Shapefile ./user_bbox.json created for input user bounds
Multi-core version
All (127) GUNW products meet spatial bbox criteria.
Group GUNW products into spatiotemporally continuous interferograms.
All (127) interferograms are spatially continuous.
User specified use of all 64 threads for gdal multiprocessing
Thread count specified for gdal multiprocessing = ALL_CPUS
Download/cropping DEM
Downloading glo_90 tiles: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████| 12/12 [00:40<00:00,  3.37s/it]
Applied cutline to produce 3 arc-sec SRTM DEM: ./DEM/glo_90.dem
***Downloading water mask... ***
Traceback (most recent call last):
//
// removed a lot of vscode python debugger traceback calls
//
  File "/home/arampal/tools/miniforge/envs/ARIA-tools/bin/ariaTSsetup.py", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/arampal/ARIA-tools/tools/bin/ariaTSsetup.py", line 18, in <module>
    main(inps)
  File "/home/arampal/ARIA-tools/tools/ARIAtools/tsSetup.py", line 470, in main
    inps.mask = prep_mask(**mask_dict)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/arampal/ARIA-tools/tools/ARIAtools/mask_util.py", line 107, in prep_mask
    mask_array = lake_masks*gdal.Open(maskfilename).ReadAsArray()
                 ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ValueError: operands could not be broadcast together with shapes (7,13) (6,12)

Expected behavior
Not really sure, this is my first time using this program
Desktop (please complete the following information):

ARIA-tools git tag: [e.g. git show --summary]

commit 32018d59312f0267e077aba1e16de4f1c70a98d9 (HEAD -> dimension, dev)
Merge: 35c01cd 60ea380
Author: BB<EMAIL_ADDRESS>Date:   Wed Sep 6 13:48:34 2023 -0700

    Merge pull request #381 from aria-tools/sss_latsortbug

    Sort pairs by latitude

OS
Running on Ubuntu server over SSH

Hi @aaryan-rampal -- I'm able to reproduce this issue. Forcing GDAL to be 3.8.3 seems to resolve this issue. We will update the requirements.txt and environment.yml to specify this shortly

my gdal is 3.8.4 yet it still doesn't work

If I run this without --mask Download, I get this issue:
/home/arampal/tools/miniforge/envs/A/bin/ariaTSsetup.py:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  __import__('pkg_resources').require('ARIAtools==1.1.6')
2024-04-22 13:37:07,147 - ARIAtools.util.dem - WARNING - Cannot proceed with VRT format, using ENVI format instead
/home/arampal/tools/miniforge/envs/A/lib/python3.11/site-packages/dem_stitcher/stitcher.py:146: UserWarning: The directoryglo_90_tiles exists; We are writing new files to this directory
  warn(f"The directory{tile_dir} exists; " "We are writing new files to this directory", category=UserWarning)
Downloading glo_90 tiles: 100%|██████████████████████████████████████████████████████████████████████████████████████| 12/12 [00:37<00:00,  3.16s/it]
/bin/sh: 1: parallel: not found
Traceback (most recent call last):
  File "/home/arampal/tools/miniforge/envs/A/bin/ariaTSsetup.py", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/arampal/ARIA-tools-v3v4/ARIA-tools/tools/bin/ariaTSsetup.py", line 628, in <module>
    main()
  File "/home/arampal/ARIA-tools-v3v4/ARIA-tools/tools/bin/ariaTSsetup.py", line 532, in main
    ARIAtools.util.vrt.dim_check(ref_arr_record, prod_arr_record)
  File "/home/arampal/ARIA-tools-v3v4/ARIA-tools/tools/ARIAtools/util/vrt.py", line 575, in dim_check
    raise Exception(
Exception: Inconsistent product dims between products ./unwrappedPhase/20220115_20220103 and None: check respective width (25, None) and height (15, None) and geotrans ((50.8924796429999, 0.000833332999999999, -0.0, 25.264989894, -0.0, -0.000833333), None)

I added code which implemented parallel processing for ARIA-tools, but it was written off of the dev branch. I noticed that the TODO in extractProduct.py export_products had been acted on in the new v2v3 branch, but it doesn't work as it gives the error above. I'd like to contribute my code if it helps since it works currently right off of the dev branch

GDAL 3.8.4 introduced an inconsistency between the behavior of gdal.Rasterize and gdal.Warp which leads to the observed mismatch in array sizes. We are working on a improved water mask generation process to address that issue. This particular issue will manifest with GDAL 3.8.4 until we implement our improved water mask.
The branch you used also needs the gnu parallel utility installed but did not contain updated specs in requirements.txt / enviorment.yaml

ARIA-tools Version: 1.1.6
*****************************************************************
*** Time-series Preparation Function ***
*****************************************************************
Shapefile ./user_bbox.json created for input user bounds
Multi-core version
All (45) GUNW products meet spatial bbox criteria.
Group GUNW products into spatiotemporally continuous interferograms.
All (45) interferograms are spatially continuous.
Thread count specified for gdal multiprocessing = 2
Download/cropping DEM
Downloading glo_90 tiles: 100%|███████████████████████████████████████████████████████████████████████████████████████████████| 12/12 [00:30<00:00,  2.57s/it]
Applied cutline to produce 3 arc-sec SRTM DEM: ./DEM/glo_90.dem
***Downloading water mask... ***
Traceback (most recent call last):
  File "/home/arampal/tools/miniforge/envs/ARIA-tools/bin/ariaTSsetup.py", line 7, in <module>
    exec(compile(f.read(), __file__, 'exec'))
  File "/home/arampal/ARIA-tools/tools/bin/ariaTSsetup.py", line 18, in <module>
    main(inps)
  File "/home/arampal/ARIA-tools/tools/ARIAtools/tsSetup.py", line 470, in main
    inps.mask = prep_mask(**mask_dict)
                ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/arampal/ARIA-tools/tools/ARIAtools/mask_util.py", line 104, in prep_mask
    mask_array = lake_masks*gdal.Open(maskfilename).ReadAsArray()
                 ~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ValueError: operands could not be broadcast together with shapes (16,26) (15,25)

It still doesn't work when I force gdal to be 3.8.3

I have tested this and it does work with GDAL 3.8.3. In any case this will be closed by work we are doing now. I will close this issue with that PR when we are ready.

this has been fixed under the latest release. Now also available on conda


Angular Sanitize with some problems

I'm submitting a ...

[x] bug report
[ ] feature request
[ ] other

Current behavior:

After execute bower install -f and downloaded angular-sanitize#1.7.4
I got this error in browser console:
Failed to instantiate module kscFinaluserApp due to:
Error: [$injector:modulerr] Failed to instantiate module ngSanitize due to:
TypeError: lowercase is not a function
    at arrayToMap  [...]

Expected / new behavior:

The correct behavior it's without this error on calling this function.
Minimal reproduction of the problem with instructions:

Update any project with angular-sanitize#1.7.4
AngularJS version: 1.6.10

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome 69.0.3497.92 (Official Build) (64-bit)

See https://docs.angularjs.org/misc/faq#what-is-the-version-compatibility-between-angularjs-main-and-optional-modules-.


TROJ_GEN.R002V01JA23 named trojan file .

System Details

OS: Windows 10 Pro 64bit
Thorium Version 117.0.5938.157

Problem
Hi, I did a scan through virustotal, there was no problem in the folder, but when I scanned through the .exe file, I encountered this problem. What is the cause?
Screenshots

#254

I couldn't find the reason where you directed me, I found it in the Thorium-Win repo but there was no explanation.


Make GetGradient concurrent

Learn how to use channels to make the calls to getInterpolatedColor concurrent.

The current implementation took 96.1µs to render the sample. A concurrent implementation took 5.6321ms, and would require sorting to maintain the palette order. Won't implement.


Revert "[kotlin2cpg] JvmClasspathRoot without an actual temporary file (#5097)"

This reverts commit 16f9541eb84605053e9c5484830b4b05e72364a7.
See source code comment for further details.
cc @xavierpinho

If we have org.apache.commons.io already as dependency we could do IOUtils.copy(resourceStream, tmpFile)
or with plain java something like Files.copy(resourceStream, tmpFile.path, StandardCopyOption.REPLACE_EXISTING).
So no manual while loop stuff.

@xavierpinho Yes, the compiler library silently drops the triggered NoSuchFileException.
@max-leuthaeuser Optimization will be done separately.