URLSearchParams API should accept numbers for values

Actual implementation of URLSearchParams.constructor and URLSearchParams.prototype.set methods in the browsers will accept any value as value, including number or Integer.
TLDR:
new URLSearchParams([['foo', 1]]) and new URLSearchParams().set('bar', 1) should compile without TS errors
It works in current implementation, because numeric value will be coerced to actual USVString value, which is a string.
Unfortunately, current TS definition of type URLSearchParams in lid.dom.d.ts will only allow strings for above mentioned setters. Below are the definitions.
I can understand that the definitions are mirroring the W3C specifications but I do believe it is not the expected experience for developers.
The actual definition enforces developers to make unnecessary operations (helpers / utils / map-reduces) to overcome TS errors 👋
Can we reconsider to allow values to be numeric to mentioned setters? This won't break any current bahavior or actual implementation.
Even as per MDN examples constructor and URLSearchParams.prototype.set it should work as expected:
// Pass in a sequence
var params3 = new URLSearchParams([["foo", 1],["bar", 2]]);

//Add a third parameter.
params.set('baz', 3);

Which works in browser but doesn't work in TS.
TypeScript Version:  3.4.3
output with tsc typescript@next
a.ts:3:34 - error TS2345: Argument of type '{ foo: number; bar: string; }' is not assignable to parameter of type 'string | Record<string, string> | URLSearchParams | string[][]'.
  Type '{ foo: number; bar: string; }' is not assignable to type 'string'.

3 const url2 = new URLSearchParams({ foo: 1, bar: '1' }) // <- FAILS
                                   ~~~~~~~~~~~~~~~~~~~~

a.ts:5:34 - error TS2345: Argument of type '(string | number)[][]' is not assignable to parameter of type 'string | Record<string, string> | URLSearchParams | string[][]'.
  Type '(string | number)[][]' is not assignable to type 'string[][]'.
    Type '(string | number)[]' is not assignable to type 'string[]'.
      Type 'string | number' is not assignable to type 'string'.
        Type 'number' is not assignable to type 'string'.

5 const url3 = new URLSearchParams([['foo', 1], ['bar', '1']]) // <- FAILS
                                   ~~~~~~~~~~~~~~~~~~~~~~~~~~

a.ts:8:17 - error TS2345: Argument of type '1' is not assignable to parameter of type 'string'.

8 url4.set('foo', 1); // <- FAILS
                  ~

Found 3 errors.

Search Terms:
Typescript URLSearchParams invalid constructor
Typescript URLSearchParams won't accept numbers as value
Typescript URLSearchParams won't accept numeric values
standard lib.dom.d.ts URLSearchParams allow numbers as values
Typescript URLSearchParams coercion number to string
Code
const url = new URLSearchParams({foo: 'bar'}) // <- OK

const url2 = new URLSearchParams({ foo: 1, bar: '1' }) // <- FAILS

const url3 = new URLSearchParams([['foo', 1], ['bar', '1']]) // <- FAILS

const url4 = new URLSearchParams([['bar', '2']]) // <- OK
url4.set('foo', 1); // <- FAILS

Expected behavior:
All above cases should work, because numeric values are being coerced to strings
Actual behavior:
TS won't compile due to URLSearchParams definitions only accept string for value
interface URLSearchParams {
    /**
     * Appends a specified key/value pair as a new search parameter.
     */
    append(name: string, value: string): void;
    /**
     * Deletes the given search parameter, and its associated value, from the list of all search parameters.
     */
    delete(name: string): void;
    /**
     * Returns the first value associated to the given search parameter.
     */
    get(name: string): string | null;
    /**
     * Returns all the values association with a given search parameter.
     */
    getAll(name: string): string[];
    /**
     * Returns a Boolean indicating if such a search parameter exists.
     */
    has(name: string): boolean;
    /**
     * Sets the value associated to a given search parameter to the given value. If there were several values, delete the others.
     */
    set(name: string, value: string): void;
    sort(): void;
    forEach(callbackfn: (value: string, key: string, parent: URLSearchParams) => void, thisArg?: any): void;
}

declare var URLSearchParams: {
    prototype: URLSearchParams;
    new(init?: string[][] | Record<string, string> | string | URLSearchParams): URLSearchParams;
};

Playground Link:
link
Related Issues:
https://github.com/microsoft/TypeScript/issues/15338

I personally would prefer not to see this change.  The automatic coercion of non-strings to strings that exists in many DOM apis is very implicit and I like that typescript is more strict about it, instead forcing me to explicitly Number() or .toString() a numeric that is going to be used as a string.

I think use .toString() is better, no need to change TypeScript.

@nmain @CaptainInPHW  I truly believe that it doesn't make any sense to justify anything in this thread with a personal preference(s). If you would like to open a discussion please provide solutions to real word use cases I mentioned above

I actually agree with @artyil
This example also demonstrate the issue:
const url1 = new URLSearchParams({ foo: false, bar: '1' }) // <- FAILS
const url2 = new URLSearchParams({ foo: 'false', bar: '1' }) // <- OK

The spec of URLSearchParams doesn't specify the value type of that object,
Forcing code like this, is too strict, and weird:
const url1 = new URLSearchParams({ foo: false.toString() })

So it should support string|number|boolean

I largely agree with @nmain that the automatic coercion of non-strings to strings that exists in many DOM apis is very implicit and typescript should NOT cater to those implicit coercions.
I'm not sure that applies here. Here we are creating a new URL object. I think we can agree that a URL is a specific type of string so passing  nonString values to the constructor, append and set methods would be like calling a urlify method. You are explicitly asking for a standardized way of converting values to a url type value (string). Very similar to JSON.stringify, yes things are being casted but that's the core functionality of the method.
The underlying implementation just uses template literals to cast to a string. I'd be happy to make the pr to accept template-literable types as values here.

AFAICS, string coercion is not standardised as part of URLSearchParams, so the current types correctly reflect what is (currently) the standard.

constructor(optional (sequence<sequence<USVString>> or record<USVString, USVString> or USVString) init = "");

https://url.spec.whatwg.org/#idl-index
I would prefer URLSearchParams adheres to the standard. If people want to allow coercion, they can easily compose/wrap URLSearchParams:
const myUrlSearchParams = (init: Record<string, string | number | boolean>) =>
  new URLSearchParams(init as Record<string, string>)

Maybe coercion will be added to the standard in the future, at which point I would expect the types to also be updated.

I don't wanna be salty, but what the *** is going on? 2020 is almost over. Why hasn't this discussion been over yet?
Why are we trying to break real JavaScript behaviour with types? Is this what TypeScript was created for?

@RyanCavanaugh I don't think this is a bug:
https://url.spec.whatwg.org/#ref-for-dom-urlsearchparams-urlsearchparams specifies that URLSearchParam takes a webidl union of sequence<sequence<USVString>> or record<USVString, USVString> or USVString. In the case specified by the OP the record<USVString, USVString> is used because the webidl union resolution determines that ECMA type of a literal object is "Object", it is not null, and it does not have a @@iterator property (see https://heycam.github.io/webidl/#es-union, mainly 8.2 and 8.4). The reason a number works, is because WebIDL specifies that everything but symbols should be coerced into a string (https://heycam.github.io/webidl/#es-USVString, https://heycam.github.io/webidl/#es-DOMString & https://tc39.es/ecma262/#sec-tostring). TypeScript typings do not usually reflect the coercible types, only the strict types. The strict type for the record value here is the string, thus typings for argument 1 of URLSearchParams should be string[][] | Record<string, string> | string (or [string, string][] | Record<string, string> | string).

@jimmywarting Typescript treats USVString as a string because it is a string. It also treats ByteString or DOMString as a string, because they are also strings. There is nothing special about USVString in regards to type coercion. All types except Symbol can be coerced into USVString/DOMString/ByteString. I don't think typescript should represent this though, as the point of it is to prevent runtime coercion. new Blob([{}]) resulting in a blob with contents [object Object] is not something typescript should cater to IMO. It defeats the purpose of strict types.

new Blob([{}]) resulting in a blob with contents [object Object] is not something typescript should cater to IMO. It defeats the purpose of strict types.

Little bit of a useless example, since nobody here is trying to make the argument it should accept any. Just that it can accept the core primitives as there are no similar gotchas like you're describing.

Can we bring back this discussion? I think it's enough for it to accept primitives that we know can be converted to strings, and also any object that implements the toString() method with a string return type

I can't believe the TS team seriously went with this decision.
As an enthusiastic TS strict user, I would much rather do new URLSearchParams(({take: 15, color: false}) as any)
Instead of doing things like false.ToString()

really confusing, is anybody going to fix it?

The way to fix this is actually to update TypeScript-DOM-lib-generator with overriding types.
Here's a test case of what I'd expect to work:
export const carQuery = new URLSearchParams([
    ["query", "suv"],
    ["new", true],
    ["accidents", false],
    ["miles", 42_000],
]);

carQuery.set("used", true);
carQuery.append("year", 2023);
carQuery.append("year", 2024);

let str: string | null, strs: string[];

str = carQuery.get("query");
strs = carQuery.getAll("year");

for (const [key, value] of carQuery) {
    str = key;
    str = value;
}
for (const [key, value] of carQuery.entries()) {
    str = key;
    str = value;
}
for (const value of carQuery.values()) {
    str = value;
}
carQuery.forEach((value, key) => {
    str = key;
    str = value;
});


Support Kotlin

I would like Tornado to support Kotlin. The reason behind that is:
. Kotlin is expressive and concise, hence a good fit for data intensive / machine learning tasks, better fit than Java
. Kotlin is JVM language, might be relatively easy to support given Java is already supported

Hi @yijunwu.
We haven't tried to execute from Kotlin yet. Compilation in TornadoVM is from Java bytecode. However, the computation must be expressed in Java because TornadoVM exposes an API for parallel and heterogeneous programming. It would be possible to run Kotlin and call Tornado code from it.
So far, we have tried R, Ruby, Javascript, and NodeJS, using the Truffle Framework (https://github.com/beehive-lab/TornadoVM/tree/master/examples/src/main/java/uk/ac/manchester/tornado/examples/polyglot).

I will close this issue. Please, feel free to open new issues for more questions, features, and bug reports.

Compilation in TornadoVM is from Java bytecode. However, the computation must be expressed in Java because TornadoVM exposes an API for parallel and heterogeneous programming.

Which all should be usable from Kotlin, right? It just compiles to Java Bytecode as well and that same way it can also interface with Java Annotations and APIs, as again it's all just Java Bytecode in the end. I'll definitely give it a try later if I get any example to run and see whether I can get that sample to run as well when ported to Kotlin. I suspect if there are any issues the Kotlin might be generating Bytecode that isn't allowed by TornadoVM, as it seems like not everything is supported.

As you point out, I am not sure if the Java BC generated by a Kotlin program are the same as in a Java program. In the case they are the same, I think it is possible to have a compatible version for TornadoVM, but we haven't tried just yet.  If you want to try, please keep us posted in your findings. We are really curious.

I am not sure if the Java BC generated by a Kotlin program are the same as in a Java program

It's largely very similar:
@JvmStatic
fun compute(array: FloatArray) {
    for (i: @Parallel Int in 0 until array.size) {
        array[i] = array[i] + 100
    }
}

results in:
@JvmStatic
public final void compute(@NotNull FloatArray array) {
   Intrinsics.checkNotNullParameter(array, "array");
   int i = 0;
   for(int var3 = array.getSize(); i < var3; ++i) {
      array.set(i, array.get(i) + (float)100);
   }
}

I'm not quite sure what's up with the annotation disappearing, but the java bytecode also look quite "funky" in the java version (apparently the annotation isn't on i, but on some unnamed local variable or something?):
    LOCALVARIABLE i I L1 L2 1
    LOCALVARIABLE array Luk/ac/manchester/tornado/api/types/arrays/FloatArray; L0 L5 0
    LOCALVARIABLE @Luk/ac/manchester/tornado/api/annotations/Parallel;() : LOCAL_VARIABLE, null [ L1 - L2 - 1 ]
    MAXSTACK = 4
    MAXLOCALS = 2

Which in the decompiled version also just disappears:
public static void compute(FloatArray array) {
    for (int i = 0; i < array.getSize(); ++i) {
        array.set(i, array.get(i) + 100.0f);
    }
}

It doesn't get that far though:
java.lang.NullPointerException: Cannot invoke "jdk.vm.ci.meta.ResolvedJavaType.getAnnotation(java.lang.Class)" because the return value of "org.graalvm.compiler.core.common.type.ObjectStamp.type()" is null
        at tornado.drivers.opencl@1.0.2-dev/uk.ac.manchester.tornado.drivers.opencl.graal.compiler.plugins.OCLVectorPlugins.lambda$registerParameterPlugins$0(OCLVectorPlugins.java:375)
        at jdk.internal.vm.compiler/org.graalvm.compiler.java.FrameStateBuilder.initializeForMethodStart(FrameStateBuilder.java:261)
        at jdk.internal.vm.compiler/org.graalvm.compiler.java.BytecodeParser.buildRootMethod(BytecodeParser.java:1026)
        at jdk.internal.vm.compiler/org.graalvm.compiler.java.GraphBuilderPhase$Instance.run(GraphBuilderPhase.java:101)
        at jdk.internal.vm.compiler/org.graalvm.compiler.java.GraphBuilderPhase.run(GraphBuilderPhase.java:63)
        at jdk.internal.vm.compiler/org.graalvm.compiler.java.GraphBuilderPhase.run(GraphBuilderPhase.java:43)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:434)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:322)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.PhaseSuite.run(PhaseSuite.java:390)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:434)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:322)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.info.elem.InlineableGraph.parseBytecodes(InlineableGraph.java:203)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.info.elem.InlineableGraph.<init>(InlineableGraph.java:76)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.info.elem.Inlineable.getInlineableElement(Inlineable.java:38)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.info.AbstractInlineInfo.populateInlinableElements(AbstractInlineInfo.java:69)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.walker.InliningData.processNextInvoke(InliningData.java:524)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.walker.InliningData.moveForward(InliningData.java:741)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.InliningPhase.run(InliningPhase.java:97)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.common.inlining.InliningPhase.run(InliningPhase.java:40)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:434)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:322)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.PhaseSuite.run(PhaseSuite.java:390)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:434)
        at jdk.internal.vm.compiler/org.graalvm.compiler.phases.BasePhase.apply(BasePhase.java:322)
        at tornado.runtime@1.0.2-dev/uk.ac.manchester.tornado.runtime.sketcher.TornadoSketcher.buildSketch(TornadoSketcher.java:162)
        at tornado.runtime@1.0.2-dev/uk.ac.manchester.tornado.runtime.sketcher.TornadoSketcher$TornadoSketcherCallable.call(TornadoSketcher.java:262)
        at tornado.runtime@1.0.2-dev/uk.ac.manchester.tornado.runtime.sketcher.TornadoSketcher$TornadoSketcherCallable.call(TornadoSketcher.java:252)

because it doesn't seem to like that method...
Full sample is here: https://gitlab.com/cromefire/tornado-kotlin
P.S.: ROCm would probably a good idea for AMD cards, OCL just doesn't really seem to work at all as my card just idles at 5% in the benchmarks, it only seemed to spike once for a very short time. Probably not the way to get the most performance out of it. Maybe something is wrong with my setup, but then again, OCL just doesn't seem to be that great... (Even Khronos wants to replace it with Vulkan compute now...)


setup of ChatRWKV

Hey guys great stuff, can we have very easy setup step process  to install ChatRWKV on a ubuntu server for example?

There is no need to toss the environment, just use the container @bello7777
https://github.com/BlinkDL/ChatRWKV/pull/58

Thanks mate, I will do it .
for the moment I just launch it on AWS ubuntu 18.04 , I'm dealing with DefaultCPUAllocator as
I can't allocate enough memory on the server

@soulteary
i tried to access your blog and guidelines but i could not,
could you give me the steps and version of Docker container so i can deploy it on ec2 server as a still have a problem with memory

@bello7777 You probably need to adjust the strategy. If you're using the pull request:
    model = RWKV(model=model_path, strategy='cuda fp16i8 *20 -> cuda fp16')

That's around line 28 in webui.py from that pull. You didn't say what you're actually doing, so there's no way to know if you're saying it failed when trying to load the model for inference, when converting, whatever.
But the most likely solution is to find whatever is running and how it's setting the strategy and reduce the number of layers it will send to the GPU. For example, in the line above you could try using cuda fp16i8 *10 -> cuda fp16 instead which should roughly half the required GPU memory.
After you get it going, you can use other tools to see how much GPU memory you have available and adjust the setting according.

thanks solved and working

now moving to train the model

Last question here, when I want to stop the chat , what should i say or do to stop it ?


[Quest/eCBIS] - Add to Child Register

Name of feature to enhance
Description of feature
Describe the enhancement

Defining terms. The World Health Organization (WHO) defines adolescents as those people between 10 and 19 years of age. The great majority of adolescents are, therefore, included in the age-based definition of “child”, adopted by the Convention on the Rights of the Child, 4 as a person under the age of 18 years.

0-6 yrs
7-12 yrs
13-17 yrs (Teenagers)
Over 18 yrs (Adults)

CC @dubdabasoduba @AnnieMungai to validate if the above is true or if we have additional criteria. what are the different age groups for children?

@f-odhiambo

In eCBIS, and I believe most child registers, children are defined as persons between 0 - 5 years (0 - 60 months). within the child group, these are other core groupings (note that these could vary by country).

0-28days - new borns (neonate)
-Under 2 months
Under 1yr olds
Under 2 years old

I do not think we have adults defined in any of our programs. However, we have: women of reproductive age - In Liberia, these are women between 15-49years. This definition varies in different countries.
There is also the definition of young girls between 9 - 12yrs who receive HPV vaccines.

The configs here https://github.com/opensrp/fhir-resources/blob/main/ecbis/app_configurations/ecbis_cha_preview/navigation_config.json add the child register. This should be tested against this release https://github.com/opensrp/fhircore/releases/tag/v0.1.5-ecbis-rc2


Improve InterpolateAndExtrapolate performance for array valued maps

This is a first try to improve the performance of InterpolateAndExtrapolate. The current main issue is that we do a lot of unnecessary array operations to be more flexible. However, for special use cases we can improve by at least a factor 2 in small tests if we do not store the intermediate results and use Einstein summation convention.
This makes the code more complex but we can save a lot of time for any pattern map operation. I kept the behavior identical to previous implementation for all cases except the array valued maps used for S1 and S2 patterns.
I tested locally with several use cases.

coverage: 91.262% (-0.06%) from 91.317%
when pulling e14a835bbe70f8a69f63d57f7f4dca49e586c087 on itp_map_speedup
into fb1ae7681eb743854adfcb252094a86d4ef973f0 on master.

Ready for review!

Hi @l-althueser , thanks for this PR!
I tested this function and for single-dimension values the result looks consistenct between the old and new method:

However for multiple dimension values, there is a problem of the dimension of weights. Minimal example to reproduce it:
def generate_multidimensional_dataset(n_points, value_functions):
    """
    Generate a 3D dataset where each point has multiple values (e.g., temperature, pressure, humidity).

    :param n_points: Number of points along each axis.
    :param value_functions: A list of functions to generate the values for each dimension.
    :return: points, multidimensional values
    """
    axes = np.linspace(-5, 5, n_points)
    xx, yy, zz = np.meshgrid(axes, axes, axes, indexing='ij')
    points = np.vstack([xx.ravel(), yy.ravel(), zz.ravel()]).T

    values = np.stack([func(xx, yy, zz) for func in value_functions], axis=-1).reshape(-1, len(value_functions))

    return points, values

# Example value functions for each dimension
def d1_func(x, y, z):
    return x**2 + y**2 + z**2

def d2_func(x, y, z):
    return np.sin(x) + np.cos(y) + np.tanh(z)

def d3_func(x, y, z):
    return np.exp(-(x**2 + y**2 + z**2))

# Generate the dataset
n_points = 10  # Adjust based on your computational capacity
value_functions = [d1_func, d2_func, d3_func]
points, multidimensional_values = generate_multidimensional_dataset(n_points, value_functions)
new_points = points
interpolator = InterpolateAndExtrapolate(points, multidimensional_values)
interpolated_df = interpolator(new_points)

In this example I got an error:
[540](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:540) if wgt.shape[0] != a.shape[axis]:
    [541](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:541)     raise ValueError(
    [542](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:542)         "Length of weights not compatible with specified axis.")

TypeError: 1D weights expected when shapes of a and weights differ.

Also I'm not sure what does array_valued account for. Could you kindly add the docstring for it? Thanks a lot!

Hi @l-althueser , thanks for this PR! I tested this function and for single-dimension values the result looks consistenct between the old and new method:
However for multiple dimension values, there is a problem of the dimension of weights. Minimal example to reproduce it:
def generate_multidimensional_dataset(n_points, value_functions):
    """
    Generate a 3D dataset where each point has multiple values (e.g., temperature, pressure, humidity).

    :param n_points: Number of points along each axis.
    :param value_functions: A list of functions to generate the values for each dimension.
    :return: points, multidimensional values
    """
    axes = np.linspace(-5, 5, n_points)
    xx, yy, zz = np.meshgrid(axes, axes, axes, indexing='ij')
    points = np.vstack([xx.ravel(), yy.ravel(), zz.ravel()]).T

    values = np.stack([func(xx, yy, zz) for func in value_functions], axis=-1).reshape(-1, len(value_functions))

    return points, values

# Example value functions for each dimension
def d1_func(x, y, z):
    return x**2 + y**2 + z**2

def d2_func(x, y, z):
    return np.sin(x) + np.cos(y) + np.tanh(z)

def d3_func(x, y, z):
    return np.exp(-(x**2 + y**2 + z**2))

# Generate the dataset
n_points = 10  # Adjust based on your computational capacity
value_functions = [d1_func, d2_func, d3_func]
points, multidimensional_values = generate_multidimensional_dataset(n_points, value_functions)
new_points = points
interpolator = InterpolateAndExtrapolate(points, multidimensional_values)
interpolated_df = interpolator(new_points)

In this example I got an error:
[540](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:540) if wgt.shape[0] != a.shape[axis]:
    [541](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:541)     raise ValueError(
    [542](https://vscode-remote+ssh-002dremote-002bmidway2-002dlogin2-002ercc-002euchicago-002eedu.vscode-resource.vscode-cdn.net/home/yuem/package_testers/~/.local/lib/python3.9/site-packages/numpy/lib/function_base.py:542)         "Length of weights not compatible with specified axis.")

TypeError: 1D weights expected when shapes of a and weights differ.

Also I'm not sure what does array_valued account for. Could you kindly add the docstring for it? Thanks a lot!

Hey @yuema137 . array_valued means that the result for a position is not a single value but an array.


No matching distribution for Vectorstores

pip install dspy-ai[qdrant]
zsh: no matches found: dspy-ai[qdrant]
pip install dspy-ai[pinecone]
zsh: no matches found: dspy-ai[pinecone]

Hey, this is a zsh thing. Its behaviour is to assume anything inside squared brackets is for pattern matching.
You can either escape or have the name of the package inside inverted commas, e.g.:
pip install "dspy-ai[pinecone]

or
pip install dspy-ai\[qdrant\]

thank you so much!


Update README.md

Chinese translation has been added

Can you make a separate file named README.chinese.md?

That's OK

No problem

No problem


App crash when there's another tableview in controller

i had to use context menu on multiple screens so i made
@interface UIBaseControllerForMenu : UIViewController <UITableViewDelegate,UITableViewDataSource,YALContextMenuTableViewDelegate>
and added all menu code in this controller's m file.didn't make xib file for this controller file.
and where i needed to use it, i used
@interface UIMyAppointmentViewController : UIBaseControllerForMenu
and call the action button of UIBaseControllerForMenu from child controllers to show/init menu.it works fine in controllers without tableview of there own but crashes the app when there's a other tableview in them.issue is you are getting cell from visible cells function of tableview which returns the controller's own cell not the one belonging to menu. and try to call functions defined in YALContextMenuCell protocol and app crashes as other cells are not implementing this function.
any solution to this???

sorry my mistake.i should have redirected tableview datasource calls  to superview's implementations if tableview is not equal to controller's own

@sameer4
i have same issue can you please give me brief answer?
Thanks

@sameer4
i have same issue can you please give me brief answer?
Always called sub class cellfor row not called super class cellfor row.
Thanks


Support lium sync to checkout public repository

Users cannot sync public cros repo.

https://github.com/google/lium/commit/56dd7ba971258daa6cbfe0c91670a2550761cd75
Maybe this commit in my personal-tree can help the idea!

@hikalium
Thank you for letting me know!!
Do users ever switch between checking out public/internal repo? If so, how about switching them by the is_internal flag?
029e213d5b9eb4101dbd86f0cba99898a87476bf


Auto target choose interrupt autoskill

i don't really know why but when danger enemy appear,the next autoskill doesn't happen,instead it continue to do a basic attack.

Please post your configuration file.

FGO_JP_REGULAR.zip
i just change the autoskill tho

Please post your configuration file.

@potchy this happens because the dangerous enemy is in the first position

@Mental0ut
I did modify the autotarget code for JP server's previous event(Illya).
But as I'm typing this, it worked normally in JP server when the dangerous enemy's in the first position.
The behavior's wrong in other servers?

Still can't reproduce. I'm farming Valentine's and it's working great.
#166 seems to have the same problem. Maybe one of you can share a video?


esbuild plugins are ignored

Describe the bug
I am trying to specify an esbuild plugin, but whatever I try it does not get invoked. I am using the same config as found here:
https://github.com/vitejs/vite/pull/2991/files#diff-9d1b5c49a91bfc3b9a10ab850f0bf0281c93350262cc908146dc77da4da4b7ceR17-R32
Reproduction
check out: https://github.com/capaj/vitest-esbuild-plugin-not-called-example
and run npx vitest
Expected result:
Hello from an esbuild plugin

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Suites 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

- my.spec.ts
Error: No tests found in suite my.spec.ts
 ❯ runSuite node_modules/vitest/dist/entry.js:4116:30
 ❯ async runSuites node_modules/vitest/dist/entry.js:4130:5
 ❯ async startTests node_modules/vitest/dist/entry.js:4135:3
 ❯ async node_modules/vitest/dist/entry.js:4150:7
 ❯ async withEnv node_modules/vitest/dist/entry.js:3946:5
 ❯ async run node_modules/vitest/dist/entry.js:4149:5
 ❯ async file:/home/capaj/oss/vitest-esbuild-plugin-not-called-example/node_modules/tinypool/dist/esm/worker.js:1:1309

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

Test Files  1 failed (1)
     Tests  no tests
      Time  335ms (in thread 0ms, Infinity%)

Actual result:
 DEV  /home/capaj/oss/vitest-esbuild-plugin-not-called-example

 √ my.spec.ts (3)

 Snapshots  1 written
Test Files  1 passed (1)
     Tests  3 passed (3)
      Time  466ms (in thread 3ms, 16144.17%)

System Info
System:
    OS: Linux 5.13 Ubuntu 21.10 21.10 (Impish Indri)
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 1.25 GB / 62.75 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.15 - ~/.yarn/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 96.0.4664.110
    Firefox: 95.0.1
  npmPackages:
    vite: ^2.7.6 => 2.7.6
    vitest: ^0.0.107 => 0.0.107

Used Package Manager
yarn
Logs
No response
Validations

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

Vitest does not run deps optimization. Since it's on the node, it will use node's native import/require whenever possible.

@antfu how can I apply esbuild plugin then?

This https://vitejs.dev/config/#esbuild ?

No, that doesn't allow to configure esbuild plugins. esbuild plugins are only ever defined under the optimizeDeps.

Please follow https://github.com/vitejs/vite/issues/3124


Add cffconvert.yml and CITATION.cff files

See the old annubes repository as an example.

Kamino closed and cloned this issue to neurogym/neurogym


4076 "how to do it" Code example doesn't match code in the Angular 2 Book

There is no app/article-editor.component.ts here. This code should display an input box and save button, but it doesn't. The next example "there's more" is fine.

I've forked the code written my own version. You can find it in my repository in 4076/How-to-do-it-2


License?

Hi guys,
Did you intend this project to be open source? If so, would you consider adding a license?
-Taylor

Thanks for your suggestions and we've added the apache license.


Support for webpack/browserify/other module loading

Wasn't sure how to properly structure a pr for this in coffeescript. I have something working over here https://github.com/n3-charts/line-chart/commit/90c4ab686a952fc293a6b24b6dd01d8321bb4440
Is there a better way to export the module name and wrap this directive in a closure?

Hi @eddywashere
thanks for tackling this! Your commit is quite big Showing  18 changed files  with 5,406 additions and 5,422 deletions. - maybe you could point out which steps did you do to prepare the lib for module loading. I could guide you a little to create a nice and small PR - I would be happy to merge this :)
Best,
Christoph

Hi @eddywashere
could me a guide a little through your commit, so I could help you with a structure for coffeescript.
Best,
Christoph


Assess the effort required to migrate to dashlets and chart.js

Assess the effort required to migrate to dashlets and chart.js. Here the objective is to identify how many of the reports can be migrated to dashlets and chart.js.

i. Prepared the estimations for each type required to migrate to dashlet and chart.js
ii. Integrated dashlet into cQube 4.0 and implemented a bar chart report using dashlet

Live


add upgrade section on documentation

Is your feature request related to a problem? Please describe.
The actual documentation doesn't have an "how to upgrade section"
Some people may only do 'git pull' and 'git checkout version' and 'forget pip install upgrade'
Describe the solution you'd like
this command can be added to the documentation:
  $ git pull
  $ version=$(curl -s https://api.github.com/repos/pytition/pytition/releases/latest | grep "tag_name" | cut -d : -f2,3 | tr -d \" | tr -d ,)
  $ git checkout $version
  $ source pytition_venv/bin/activate
  (pytition_venv) $ pip3 install upgrade -r requirements.txt

Also tell to:

[ ] backup database and media first somewhere, see #218
[ ] re-run : collectstatic, migrate, compilemessages


backport: Merge bitcoin#22530,(partial)21562,22322,22517

Issue being fixed or feature implemented
bitcoin backports
What was done?
Backported bitcoin changes
How Has This Been Tested?
CI Run

rebased from GH GUI to fix Merge Fast-Forward Only check

Hello @PastaPastaPasta

p2p: don't add AlreadyHave transactions to recentRejects bitcoin/bitcoin#19753
Split orphan handling from net_processing into txorphanage bitcoin/bitcoin#21148

Thanks I will add this changes in separate PR , as this change is approved state

@PastaPastaPasta requesting review.


rancher-backup  k8s 1.26 chart support

This issue is to implement the chart changes & perform the testing required to upgrade to k8s 1.26. Please perform below steps.

[x] Check whether the chart has any references to the below deprecated features of k8s 1.26. You can find information about deprecated APIs here on Kubernetes Deprecation guide.

flowcontrol.apiserver.k8s.io/v1beta1 API version of FlowSchema

flowcontrol.apiserver.k8s.io/v1beta1 API version of PriorityLevelConfiguration

autoscaling/v2beta2 API version of HorizontalPodAutoscaler

[x] Update kube-version annotation in Chart.yaml. catalog.cattle.io/kube-version: '>= 1.23.0-0 < 1.27.0-0'
Note:  If this is an upstream chart and if the upstream chart doesn't support k8s 1.26 then do not update the kube-version annotation

[ ] Perform below tests

Fresh install/uninstall/upgrade/downgrade of the charts on K8s 1.26 provisioned on Rancher. Test the chart functionality

Provision rancher on k8s 1.25 or lesser

Install chart on this cluster

Upgrade this cluster in rancher to k8s 1.26

Make sure the existing chart and the app is functional after cluster upgrade

Please note that the k8s 1.26 upgrade is targeted for the 2023-Q2-v2.7x. Please complete this task by 05/19/2023.

Verified on v2.7-head ID: 6ce75a0

Provisioned an HA cluster with Rancher Chart Version v2.7.3 and Rancher Image Tag of v2.7-head
Provisioned a downstream RKE1 cluster with k8s v1.25.9
Provisioned a downstream RKE1 cluster with k8s v1.26.4
Provisioned a downstream RKE2 cluster with k8s v1.25.9+rke2r1
Provisioned a downstream RKE2 cluster with k8s v1.26.4+rke2r1
Ran backup/restore p0 test cases and they all passed
Began migration process for upgrading the local cluster to k8s 1.26.4
Once migrated, verified all the downstream clusters were up and running
Re-ran p0 test cases on v1.26.4 local and they all passed

Worth noting as well that Rancher Chart Version 2.7.3 doesn't support k8s 1.26, so when I was migrating clusters I had to switch to the latest RC available and that worked.
helm show chart rancher-latest/rancher --version=2.7.3 --namespace cattle-system

apiVersion: v2
appVersion: v2.7.3
description: Install Rancher Server to manage Kubernetes clusters across providers.
home: https://rancher.com/
icon: https://github.com/rancher/ui/blob/master/public/assets/images/logos/welcome-cow.svg
keywords:
- rancher
kubeVersion: < 1.26.0-0
maintainers:
- email<EMAIL_ADDRESS>  name: Rancher Labs
name: rancher
sources:
- https://github.com/rancher/rancher
- https://github.com/rancher/server-chart
version: 2.7.3


restinstance 1.3.0, add pip check, maintainer

Checklist

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

Notes:

fixes #3
uses the github tarball while an sdist is unavailable

[x] https://github.com/asyrjasalo/RESTinstance/issues/127

re-sync upstream dependencies to requirements.txt
adds pip check

i had a look at running the test suite but it seemed... complicated.

adds myself as a maintainer :wave:

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

@conda-forge/restinstance ready for review

We can try uncommenting it... I think the linked upstream PR (or better,
this one that corrects some deps
https://github.com/conda-forge/flex-swagger-feedstock/pull/9) had some 3.10
issues... It may well be
As for users: yes, even with that upstream fixed,  there might be 3.10
issues. I think we're still in the phase where not all of the 3.10
incompatibilities have been found across pypi. But the test dependences
aren't going to impact users at all... it's still noarch, and no more
broken than that previous releases that the conda solver would install
instead.
Anyway, I think many acceptance test environments are pretty conservative,
though!

@conda-forge-admin please rerender

@conda-forge/restinstance ready for review

@conda-forge-admin please rerender

@conda-forge-admin please rerender

@conda-forge/restinstance ready for review

Looks good, I merged it. Thanks!


Editor anti-aliasing broken on non-retina displays (4.3.dev6.mono)

Tested versions
Looks fine in 4.2.2.mono
Rendering messed up in in 4.3.dev6.mono
System information
Mac Sonoma 14.5 — 2.3 GHz 8-Core Intel Core i9 — AMD Radeon Pro 5500M 4 GB Intel UHD Graphics 630 1536 MB
Issue description
I have an external monitor hooked up to my macbook. I've upgraded from 4.2.2 to 4.3.dev6 and the editor is now missing anti-aliasing for text and UI components.
Apple Thunderbolt Display: 27-inch (2560 × 1440)
This is what a new project looks like on my external display. Note the near-illegible text on the ruler in the scene preview, and the messed-up "Filter properties" text in the inspector:

Built-in Retina Display: 16-inch (3072 × 1920)
Dragging that same window to the built-in laptop screen display anti-aliases lines and text correctly:

I'm guessing that the difference between the two is the retina classification as I've seen that cause other differences in rendering in the past, but I don't have more non-retina monitors to confirm that.
Steps to reproduce
Open an editor on a non-retina display. Anti-aliasing is missing.
Minimal reproduction project (MRP)
Project-independent; it works with fresh projects made in 4.3.dev6

CC @bruvzg @Calinou


can't scrape with thetvdb anymore, since latest update to 2.9.17

What TMM version are you using?
2.9.17
release, pre-release, nightly, or directly from GitHub/branch?
release
What is the actual behaviour?
does nothing when using thetvdb scraper, no errors. trakt.tv does work
What is the expected behaviour?
scrape from thetvdb
Steps to reproduce:

first update to 2.9.17
second try to scrape a tv episode

Additional
Have you attached the Logfile from the day it happened?
while starting up tmm:
2019-05-15 08:06:01,138 WARN  [main] o.t.scraper.config.MediaProviderConfig:83 - Cannot load settings 'data/scraper_moviemeter.conf' - using defaults
2019-05-15 08:06:01,147 WARN  [main] o.t.scraper.config.MediaProviderConfig:83 - Cannot load settings 'data/scraper_tmdb.conf' - using defaults
while trying to scrape a episode:
2019-05-15 08:06:32,571 ERROR [tmmpool-unnamed-task-T2-G3] o.t.s.thetvdb.TheTvDbMetadataProvider:140 - TheTvDbMetadataProvider
java.net.ConnectException: Failed to connect to api.thetvdb.com/<IP_ADDRESS>:443
        at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:240)
        at okhttp3.internal.connection.RealConnection.connect(RealConnection.java:158)
        at okhttp3.internal.connection.StreamAllocation.findConnection(StreamAllocation.java:256)
        at okhttp3.internal.connection.StreamAllocation.findHealthyConnection(StreamAllocation.java:134)
        at okhttp3.internal.connection.StreamAllocation.newStream(StreamAllocation.java:113)
        at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:42)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
        at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
        at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
        at okhttp3.RealCall.execute(RealCall.java:77)
        at retrofit2.OkHttpCall.execute(OkHttpCall.java:174)
        at org.tinymediamanager.scraper.thetvdb.TheTvDbMetadataProvider.initAPI(TheTvDbMetadataProvider.java:136)
        at org.tinymediamanager.scraper.thetvdb.TheTvDbMetadataProvider.getMetadata(TheTvDbMetadataProvider.java:154)
        at org.tinymediamanager.core.tvshow.tasks.TvShowEpisodeScrapeTask.doInBackground(TvShowEpisodeScrapeTask.java:133)
        at org.tinymediamanager.core.threading.TmmTask.run(TmmTask.java:125)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
Caused by: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
        at java.net.PlainSocketImpl.socketConnect(Native Method)
        at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
        at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204)
        at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
        at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
        at java.net.Socket.connect(Socket.java:589)
        at okhttp3.internal.platform.Platform.connectSocket(Platform.java:125)
        at okhttp3.internal.connection.RealConnection.connectSocket(RealConnection.java:238)
        ... 25 common frames omitted
2019-05-15 08:06:32,572 WARN  [tmmpool-unnamed-task-T2-G3] o.t.c.t.tasks.TvShowEpisodeScrapeTask:139 - Error getting metadata Failed to connect to api.thetvdb.com/<IP_ADDRESS>:443

Your Operating system? (win/mac/linux? version?)
Arch Linux - Kernel: 5.0.13

works for me.
Just scraped a show with TVDB

Caused by: java.net.ConnectException: Verbindungsaufbau abgelehnt (Connection refused)
Your could not connect to TMDB; in fact, the connection was refused!
Maybe some hiccup on their side?

funny coincidence, i updated, scraping didn't work anymore, i also tried to connect to api.thetvdb.org and it worked.
i didn't try to connect to https://api.thetvdb.org, i would have recognized that this wouldn't work.
i restarted my router and that did the trick.
so this issue can be closed, thanks for all your work!


Custom callbacks

The server sends back messages of type other than byte and string. I am wondering if it is possible to add custom callbacks to listener and listener manager to handle specific messages server sends back. Thanks.

 It would be better to have the feature, but priority wouldn't be so high.


im2rec documentation is lacking / buggy

im2rec.py doesn't have docstrings. The online doc that describes the RecordIO format (here) doesn't describe how to use the script. Another page does, but it could really use a full-fledged real-world example, and should either be unified with or at least linked to from the other doc page.
In addition, the im2rec.py script encodes class labels as floating point numbers:
def write_list(path_out, image_list):
    with open(path_out, 'w') as fout:
        for i, item in enumerate(image_list):
            line = '%d\t' % item[0]
            for j in item[2:]:
                line += '%f\t' % j ### <---- THIS IS THE FLOATING POINT LABEL
            line += '%s\n' % item[1]
            fout.write(line)

But the doc page has integer labels in the example. When trying to make my own test .lst file by hand I used integer labels which in fact didn't work with mx.io.ImageRecordIter. It'd be great to get a clarification on the exact required .lst file format.

Thanks for submitting the issue @kjchalup
The reason why it uses floating point is that the label value could be generated by the regression, e.g. 68.6 kg for a human body weight.
There is a page that uses im2rec with real data.
I did some experiments to change the code to %d and it works with ImageRecordIter.
Could you provide some reproducible code for me?
I would update the documentation as well.

After I traced the code from im2rec.py. The correct format is float. But if you use integer for label data, it should work fine since float(label value) return a float anyway

Fix merged - thanks @stu1130 - this can be resolved.
@kjchalup - kindly resolve, or add more details if there is still an issue. Thanks!


Explicit check of input file update times when creating weather symbols

This PR includes changes that allow the weather symbols CLI to check that at least one of the input files is more recent than an optionally provided update_time. If no files are more recent than this, the CLI returns without output, preventing the recreation of a weather symbol that includes no more recent input data.
This implementation needs the addition of tests if we were to adopt it.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

Not necessary.


Pod install

Hi,
First of all, thanks for sharing this library!
I tried to run pod install but I got:
[!] Unable to find a specification for TinderSwipeView
Can you give me any suggestion?
Thank you

mention platfrom in podfile like this
platform :ios, '10.0'
let me know the status

I tried still same, here is my pod file:
Uncomment the next line to define a global platform for your project
platform :ios, '10.0'
target 'TestApp' do
Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!
pod 'TinderSwipeView'
target 'TestAppTests' do
inherit! :search_paths
# Pods for testing
end
target 'TestAppUITests' do
inherit! :search_paths
# Pods for testing
end
end

Try pod repo update

Working now thanks!


[BUG] Could not find a part of path VariableValue.txt while generating Rect Atom

Describe the bug
DirectoryNotFoundException: Could not find a part of the path "D:\Users\IceTrooper\Documents\_Moje<EMAIL_ADDRESS>Something went wrong while generating new Atom (in this case I was trying to generate Rect). I got this file in provided directory.
To Reproduce

UnityAtoms -> Generator
Type Rect in "Type name" field.
Wait for generating files. The error will occur.

Screenshots

Environment

OS: Windows 10 x64
Unity Version 2019.2.0f1
Version of Unity Atoms: v2.0 canary branch

hmm, I think I got it. I added UnityEngine namespace to "Type namespace" field I don't have that error, but I have another:
ArgumentOutOfRangeException: StartIndex cannot be less than zero.

@IceTrooper This issue seems to be solved? Got it working on my end at least:

Should be resolved. Closing issue.


Add support for connecting to Routing API DB over TLS

We have a few environments which have strict security policies in place which only allow secure database connections regardless of the data classification or even if the data itself is encrypted.
A recent commit for the UAA release has enabled TLS connections for the UAA DB.
https://www.pivotaltracker.com/n/projects/997278/stories/145563953
Jon Price
Intel Corp

Hello @jmprice Thank you reaching out. Although we can't provide a timeline for delivery of this feature, we will keep the issue open.
@shashwathi Would the eng team take a PR for this?

@jmprice :
Yes, PR would be great. Something to keep in mind, we currently support postgres and mysql as the backends for routing API so this change should be done with for both these backends.
Regards
Shash

For reference, CAPI team has a similar story in flight to support SSL to MySQL and Postgres CCDB instances: https://www.pivotaltracker.com/story/show/132950039

Any progress on getting this implemented?

prioritized for engineering review

This was delivered in v0.166.0. Please let us know if this doesn't address your needs.


add Models\ User to fit Laravel 8

As we know in L8, User model is located in Models folder.

Hello @ramirors,
Thanks for your feedback.
PanicHD is still using App\User because at the moment we're keeping compatibility with Laravel installations that can be using laravel/ui since earlier versions of the framework. laravel/ui is also compatible with Laravel 8. There also may exist other third party user auth packages that also make use of "App\User" namespace.
So, to keep these backward compatibilities, I guess that changing the parent classname for PanicHD Member model is not a correct approach.
As of issue #28 I noticed about the problem originated in PanicHD with a fresh Laravel 8 installation using Laravel Breeze, which is In fact one of the recommended auth packages in Laravel 8. In these kind of installations, auth is using App\Models\User as you have pointed out. In that issue, I posted a manual patch for these kind of installations. Anyway, since then I'm also working on a patch that makes PanicHD compatible with both namespaces.

Hello @ramirors,
I have just published a new PanicHD release. Now PanicHD should be natively compatible with Laravel apps using App\Models\User. Check it out! https://github.com/panichelpdesk/panichd/releases/tag/v0.21.0

Yeah!! Thanks !
El dom., 28 de febrero de 2021 12:51, Xavi<EMAIL_ADDRESS>escribió:

Hello @ramirors https://github.com/ramirors,
I have just published a new PanicHD release. Now PanicHD should be
natively compatible with Laravel apps using App\Models\User. Check it out!
https://github.com/panichelpdesk/panichd/releases/tag/v0.21.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/panichelpdesk/panichd/pull/31#issuecomment-787501713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB7MVAUQQ7CFJW2VCMQCLDTBKGDRANCNFSM4YBFZNMQ
.


Update dependencies to latest

Thanks alot!

You're welcome, that's the least I can do to help ☺


useTransition not working as expected

What version of Remix are you using?
1.5.1
Steps to Reproduce
The component is located inside /app/routes/Experimental/BookingFlow.tsx
import React from 'react'
import { ActionFunction, redirect } from '@remix-run/node'
import { Form, useTransition } from '@remix-run/react'

export const action: ActionFunction = async ({ request }) => {
  const formData = await request.formData()
  console.log(`Creating booking for ${formData.get('name')} of quantity ${formData.get('quantity')}`)

  const delay = new Promise((resolve) => setTimeout(resolve, 3000))

  await delay

  return redirect('./BookingConfirmation')
}

function BookingFlow(): React.ReactElement {
  const transition = useTransition()

  return (

Booking flow

      <Form method="post">
        <fieldset disabled={transition.state === 'submitting'}>

            Name:
            <input type="text" name="name" />

            Quantity:
            <input type="number" name="quantity" />

          <button type="submit"> {transition.state === 'submitting' ? 'Processing...' : 'Submit'}</button>
        </fieldset>
      </Form>

  )
}

export default BookingFlow

Expected Behavior
With the sample code above. It is expected that once user clicks on submit, should be able see the transition state. e.g. inputs getting disabled and button text getting changed from Submit to Processing...
After 3 seconds it gets redirected to the BookingConfirmation page
Actual Behavior
Unable to see any transition state, it just redirects to the BookingConfirmation page just like a regular html form element

Maybe related to #3300

While debugging this, I noticed that the html generated by server doesn't contains any link to JS files.
Then I started having doubts that maybe I am doing something wrong.
The culprit was Root.tsx. You need to add a special component called


Maximize Child exceed Container height

When we maximize the Child windows, they exceed Container height, and the Child bottom is hided.

In file MdiContainer.cs in method MdiContainer_SizeChanged change line
mdiChildHeight = ActualHeight;
to
mdiChildHeight = InnerHeight;


Modernize pyroma

Unless there's a strong reason otherwise, I'd suggest instead of spending more time maintaining the classifier fetch code, fetching fresh classifiers each release, and leaving users stuck with the vendored classifiers until Pyroma updates to a new version, just using the drop-in compatible set of classifiers in the canonical trove-classifiers package. As mentioned in #71 , it should be a two-line change (besides removing all the no longer needed code in fetch_classifiers.py and classifiers.py): just add trove_classifiers to install_requires in setup.cfg, and change from pyroma.classifiers import CLASSIFIERS to from trove_classifiers import classifiers as CLASSIFIERS on line 26 of ratings.py.
Also, as to the license identifier mapping, it appears to use the rather arbitrary bespoke scheme (with internally inconsistent use of hyphens and other punctuation) used by in the legacy Trove license classifiers, rather than a well-defined, understood and used standard like SPDX (which it superficially resembles). Given most projects I'm aware of that bother to use the license field for a common license covered by the tags use standard SPDX identifiers (if anything at all), I'd suggest using that as the mapping instead (or at least in addition to such), as defined in this comment on pypa/packaging-problems#41, and as further discussed in my PEP 639.
To note for the future, part of PEP 639 will officially deprecate the legacy license classifiers due to their many problems as discussed on the aforementioned thread, which are ambiguous, limited and out of date, in favor of proper SPDX identifiers in the new License-Expression core metadata field specified in that PEP (and the former has already been effectively frozen in favor of the latter), while (potentially) backfilling the License field with the SPDX identifier. Once that is live, pyroma should be revised accordingly (I can help if desired), since including any License classifier(s) along with a License-Expression field value will be considered an error, the opposite of Pyroma's current behavior, so it might be worth considering just dropping that for now to simplify the codebase and ensure forward-compatibility, given the identified issues with it.

Also, just to note, I'm not sure if it was intended, but without the critical build-system section in the pyproject.toml,
[build-system]
requires = ["setuptools>=42"]
build-backend = "setuptools.build_meta"

Pyroma is still using legacy, non-PEP 517 builds by default, with direct setup.py invocation and no build isolation.

The lack of build_meta builder is intentional, as a part of the one step at a time process. I don't want to break everything at once.
That's also why I didn't even get to the bit about trove-classifiers in your comment yet. :-) Yes, using that seems like a good idea.
Same thing about the version. I do have a vague feeling I tried to use that check before and it didn't work for some reason, but if that is the case it's when the package was all new.
I don't think I will be finished with all this this weekend, but I hope a beta could be out in a few weeks.

Turns out zest.releaser doesn't like a non-setup.py package yet, so I'll skip adding the build-backend bit to Pyromas packaging, because that would be a lie. :-D

The lack of build_meta builder is intentional, as a part of the one step at a time process. I don't want to break everything at once.

I'm a little confused—did the build somehow break when you migrated off the deprecated legacy backend to the modern PEP 517 one? Since your setup and configuration is now purely declarative, the only plausible way I'm aware of that could this would happen is an edge-case bug in Setuptools, which given its PEP 517 support has had several years to fully stabilize, and your [options] are all fairly standard, seems rather unlikely. Otherwise, not only should the build succeed, but resulting wheel should be verifiably identical or very nearly so (assuming matching versions of Setuptools).

That's also why I didn't even get to the bit about trove-classifiers in your comment yet. :-) Yes, using that seems like a good idea.

I can totally understand not getting to it, but what confused me was why this PR went to the effort of updating the current bespoke code doing that, rather than either leaving it be or tweaking the ~two lines needed to use the canonical set of classifiers.

Same thing about the version. I do have a vague feeling I tried to use that check before and it didn't work for some reason, but if that is the case it's when the package was all new.

I'm a little confused what you're referring to here, sorry—would you mind clarifying?

Turns out zest.releaser doesn't like a non-setup.py package yet, so I'll skip adding the build-backend bit to Pyromas packaging, because that would be a lie. :-D

I don't follow, sorry, I leave a stub setup.py in place for the moment for legacy tools, and most other projects I'm aware of that have migrated to modern PEP 517 do the same, as is generally recommended for now. Not doing so has no direct bearing on properly specifying your build backend in [build-system] (the latter merely happens to be one of the necessary prerequisites for the former, not the converse) or supporting PEP 517 builds in general, so I'm not sure why that should be a blocker. Setuptools certainly doesn't have to be used with declarative setup and config, after all, but that has no direct bearing on its support for PEP 517 builds.
Its possible that there could be some other issue with zest.releaser and PEP 517 builds, since it appears it is only recently catching up with the times on a lot of other things. However, at least based on the above statement, its not clear that's the case, and some Googling has not turned up any obvious issues (with PEP 517 builds at least, as opposed to adding configuration settings in pyrproject.toml, which is generally orthogonal), so simply trying it seems to be the way to go, if you could...?

zest.releaser currently gets the version number in several different ways, one being actually executing the setup.py. It turns out that it will not read it directly from setup.cfg, at least not by default. I looked at the code, and there seems to be a configuration workaround, I might try that.

Nah, didn't work. I looked into fixing it in zest.releaser, but there is no trivial way. I think zest.releaser should probably start using build as well, but it's a pretty major operation.

Gotcha. Again, though, doesn't it work right now if you don't drop the stub setup.py for legacy compat (which most modern PEP 517-supporting projects using Setuptools keep around for now)? If zest.releaser is not PEP 517-aware, then the PEP 518 build-system block in the pyproject.toml won't make any difference to it. So, it will work exactly as it did before until it is updated to support modern packaging standards, while not blocking the enablement of modern PEP 517 builds for everything else.

Right, I can put in the block in pyproject.toml, but it wouldn't make a difference. I guess I could add it and as build-backend just say "zest.releaser.fullrelease:main" but I have no idea what other tools would make of that.

Right, I can put in the block in pyproject.toml, but it wouldn't make a difference.

I'm a little confused—what makes you think that, sorry? Any modern Python build frontend (whether build on your end, or pip on the user's end) will recognize a PEP 518 config block, set up a build environment with supported versions of the specified build-time dependencies (e.g. setuptools>=42, wheel) and invoke the specified PEP 517 build backend (e.g. the modern setuptools.build_meta). Otherwise, without that, tools will fall back to the old implicit legacy behavior of just directly executing the setup.py in the current environment, triggering the deprecated setuptools.build_meta.__legacy__ builder, and hoping a supported version of the project's backend is installed.

I guess I could add it and as build-backend just say "zest.releaser.fullrelease:main" but I have no idea what other tools would make of that.

That could theoretically work if zest.releaser had support for being a PEP 517 build backend, i.e. it had a submodule that exposed the required hooks, as top-level attributes, e.g. build_sdist, build_wheel, etc. PEP 518 is for specifying the project's build backend, i.e. what gets executed on a developer or user machine to build a source tree into a sdist, or a sdist into a wheel, that can be installed by a wheel-compatible installer (i.e. pip, installer, etc).
However, that is almost certainly not what you want. Based on reading their docs, zest.releaser is a release orchestration system, not a build system; it neither should nor is required to run every single time you, a developer or a user attempts to install pyroma from a non-built (wheel) distribution, only when you, as maintainer, want to release a new public version.
Setuptools is your build backend, and thus is what should be specified in the [build-system] section (as in the snippit above). zest.releaser should then just call python -m build or build.ProjectBuilder().build_sdist() and .build_wheel(), though it appears per their docs that still directly executes setup.py, which as they mention is deprecated and they plan to migrate away from.
Therefore, you should specify the PEP 518 [build-system] section regardless as mentioned above, and then at release time, either:

Run the fullrelease command as normal (which, until zest.releaser is updated to support modern packaging practices, will still itself use the deprecated direct setup.py as before, but everything/one else will now use the modern PEP 517 approach)
Run prerelease and postrelease individually, and in between, run git tag -a vX.Y.Z && python -m build && twine upload dist to replicate what release does for you, just using modern Python packaging practices (you can also throw in a twine check --strict dist to check the Description field using the correct modern parser).


Hello world not work (404 - NotFound)

I long time not use this project.  I try get simple page with text "Hello world".  I use self host project on Windows 7. Run as admin.
 class HelloModule : Nancy.NancyModule
    {
        public HelloModule()
        {
            Get["/"] = x => { return "Hello World"; };
       }
   }

static void Main(string[] args)
        {
            using (var host = new NancyHost(new Uri("http://localhost:8888")))
            {
                host.Start();
                Console.WriteLine("Running on http://localhost:8888");
                Console.ReadLine();
            }
        }

Make your module public
On Thu, 26 Jan 2017 at 21:43, Radzhab<EMAIL_ADDRESS>wrote:

I long time not use this project. I try get simple page with text "Hello
world". I use self host project on Windows 7. Run as admin.
class HelloModule : Nancy.NancyModule
{
public HelloModule()
{
Get["/"] = x => { return "Hello World"; };
}
}
`
static void Main(string[] args)
{
using (var host = new NancyHost(new Uri("http://localhost:8888")))
{
host.Start();
Console.WriteLine("Running on http://localhost:8888");
Console.ReadLine();
}
}
`
[image: image]
https://cloud.githubusercontent.com/assets/2556411/22351546/93b50660-e429-11e6-8348-ec7e7d72d735.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NancyFx/Nancy/issues/2690, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGapgYF8bPKmBtAKo1fGfKvbCeLSsMmks5rWRN3gaJpZM4LvLQ0
.

I was just typing the same thing 😁


License of package versus license of source/project and propagation of licenses

Describe the bug
In the meta.license of a package we typically state the licenses that apply to the source, not the licenses that apply to the built project.
Additional context
The actual licenses that apply to the built package can be different. Exactly which apply is difficult to say as it depends entirely on the licenses of the source, as well as other (native) build inputs. This makes it impossible to reason about at evaluation time and near impossible by inspecting build artifacts.
Even so, it is possible to take a cautious approach by propagating licenses. This allows for example organizations to block software that may be GPL-licensed.
In my opinion meta.licenses as we have now should be part of the src derivation, and meta.license of a package should be taken from there by default. Additionally, I think we could have a config.meta.propagateLicenses to propagate licenses of all build inputs. I think there could be an additional switch for native build inputs.
I imagine this could need an RFC.
Notify maintainers
Note I have no need for this myself and merely wrote this because it again came up on IRC.
Related issues

default value for packages that have no license https://github.com/NixOS/nixpkgs/issues/43231
building of unfreeRedistributable packages https://github.com/NixOS/nixpkgs/issues/83884

Considerations

propagating licenses may impact evaluation severely
not propagating licenses of build tools will encourage the users of this feature to fix separation of native versus non-native inputs which is also good for cross-compilation

Are there examples of other distributions that have attempted to deal with this type of problem?

If we're going in that direction: I think it would also be good to have some sort of tagging not only in the expressions that define a package, but to propagate this info to the outputs instead. I'm not sure if we need modifications to nix for that or if putting a file in $out/nix-support would be sufficient for this…

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/generating-software-bill-of-materials-from-derivation/14089/2

It'd probably be best to not propagate a certain license but license properties: i.e. unfree or GPLInfected, thus creating a new cumulative "license" for the entire closure.

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/petition-to-build-and-cache-unfree-packages-on-cache-nixos-org/17440/12

Related: https://github.com/NixOS/nixpkgs/issues/283706


[Errno 2] No such file or directory

Hello, I am using sigprofilerExtractor version 1.1.21 and plotting version 1.3.14. I encountered the following error and would like to know the cause. Thank you.
KeyError                                  Traceback (most recent call last)
/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/sigProfilerPlotting/sigProfilerPlotting.py in plotSBS(matrix_path, output_path, project, plot_type, percentage, custom_text_upper, custom_text_middle, custom_text_bottom, savefig_format, volume)
   2640             buf = io.BytesIO()
-> 2641             fig_orig = make_pickle_file(
   2642                 context="SBS96", return_plot_template=True, volume=volume

/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/sigProfilerPlotting/sigProfilerPlotting.py in make_pickle_file(context, return_plot_template, volume)
    150     if os.path.exists(path):
--> 151         return pickle.load(open(path, "rb"))
    152

/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/matplotlib/axes/_base.py in __setstate__(self, state)
    759         # Merge the grouping info back into the global groupers.
--> 760         shared_axes = state.pop("_shared_axes")
    761         for name, shared_siblings in shared_axes.items():

KeyError: '_shared_axes'

During handling of the above exception, another exception occurred:

FileNotFoundError                         Traceback (most recent call last)
<ipython-input-5-10c17304bfa3> in <module>
      1 input_data = '/data/project/Alzheimer/Main/00.Neurogenesis/04.analysis/01.SGZ_whole/01.SNV/Mutational_landscape/02.sigprofilerExtractor/vcf'
      2 output ='/data/project/Alzheimer/Main/00.Neurogenesis/04.analysis/01.SGZ_whole/01.SNV/Mutational_landscape/02.sigprofilerExtractor/result'
----> 3 sig.sigProfilerExtractor("vcf", output, input_data, reference_genome="GRCh38",
      4                          minimum_signatures=1, maximum_signatures=5, nmf_replicates=3, make_decomposition_plots=True)

/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/SigProfilerExtractor/sigpro.py in sigProfilerExtractor(input_type, output, input_data, reference_genome, opportunity_genome, cosmic_version, context_type, exome, minimum_signatures, maximum_signatures, nmf_replicates, resample, batch_size, cpu, gpu, nmf_init, precision, matrix_normalization, seeds, min_nmf_iterations, max_nmf_iterations, nmf_test_conv, nmf_tolerance, nnls_add_penalty, nnls_remove_penalty, initial_remove_penalty, collapse_to_SBS96, clustering_distance, export_probabilities, make_decomposition_plots, stability, min_stability, combined_stability, allow_stability_drop, get_all_signature_matrices)
    791
    792             ################################# Export the results ###########################################################
--> 793             sub.export_information(loopResults, mutation_type, layer_directory, index, colnames, wall=wall, sequence=sequence)
    794             all_similirities_list.append(all_similarities)
    795             current_time_end = datetime.datetime.now()

/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/SigProfilerExtractor/subroutines.py in export_information(loopResults, mutation_type, output, index, colnames, sequence, wall)
   1108         if m.startswith("SBS"):
   1109             tmp_m = m[3:]
-> 1110         plot.plotSBS(signature_subdirectory+"/"+mutation_type+"_S"+str(i)+"_Signatures"+".txt", signature_subdirectory+"/Signature_plot", "S"+str(i), tmp_m, True, custom_text_upper=stability_list, custom_text_middle=total_mutation_list)
   1111     else:
   1112         custom_signatures_plot(processes, signature_subdirectory)

/opt/Yonsei/python/3.8.1/lib/python3.8/site-packages/sigProfilerPlotting/sigProfilerPlotting.py in plotSBS(matrix_path, output_path, project, plot_type, percentage, custom_text_upper, custom_text_middle, custom_text_bottom, savefig_format, volume)
   2919         except:
   2920             print("There may be an issue with the formatting of your matrix file.")
-> 2921             os.remove(os.path.join(output_path, "SBS_96_plots_" + project + ".pdf"))
   2922
   2923     elif plot_type == "192" or plot_type == "96SB" or plot_type == "384":

FileNotFoundError: [Errno 2] No such file or directory: '/data/Mutational_landscape/02.sigprofilerExtractor/result/SBS96/All_Solutions/SBS96_1_Signatures/Signatures/Signature_plot/SBS_96_plots_S1.pdf'

Hi @KANGseungseok,
I believe the issue occurs when the version of matplotlib to write and load the template file is different. To resolve the issue the templates need to be removed. You can find the templates here:
import sigProfilerPlotting as sigPlt
import os
sig_path = os.path.join(os.path.dirname(sigPlt.__file__), "references/templates/")

Please let me know if this resolves your issue. Thanks!

Hi, @mdbarnesUCSD
Thank you very much for your help. The sigprofilerExtractor was successfully running. However, the template is recreated at the specified path. Do I need to delete it periodically? What is the role of this template?

Hi @KANGseungseok,
The template is generated to speed up the plotting, since many plots are created during a run. A template contains a plot containing the x-axis labels and other plotting components that do not change. The issue occurs when the template is being loaded in. It seems this is because the version of matplotlib used to generate the plot template is different than the version of matplotlib that was used to load the template. It is necessary to remove the templates when the version of matplotlib changes in your environment.


LSPS0: underscores in method names

Use underscores in method names in LSPS0, for consistency throughout the spec.
Main edit: Changes lsps0.listprotocols to lsps0.list_protocols

100%

Added:
method names MUST be in snake_case, i.e. words are lower
case and separated by _ characters.

This seems an uncontroversial change, OK with merging even outside of LSPS meeting.


running es 5.2.2 in docker per documentation on elastic.co site does not work

docker info output:

alec@Alecs-MBP / $ docker info
Containers: 10
 Running: 0
 Paused: 0
 Stopped: 10
Images: 451
Server Version: 17.03.0-ce
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 515
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 977c511eda0925a723debdc94d09459af49d082a
runc version: a01dafd48bc1c7cc12bdb01206f9fea7dd6feb70
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.9.12-moby
Operating System: Alpine Linux v3.5
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 1.952 GiB
Name: moby
ID: XXEV:R3TK:Q4Z7:5Z34:M625:5RH7:2K3U:3EIS:44UK:VIU3:KHRM:4DHC
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 17
 Goroutines: 28
 System Time: 2017-03-18T03:58:26.757918501Z
 EventsListeners: 1
No Proxy: *.local, 169.254/16
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false
alec@Alecs-MBP / $

docker-compose version:

alec@Alecs-MBP / $ docker-compose -v
docker-compose version 1.11.2, build dfed245

Host OS and version:
OSX 10.11.6

Bug description
documentation here: https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html
says to run the following:
docker run -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" docker.elastic.co/elasticsearch/elasticsearch:5.2.2

This fails on my system as follows:
alec@Alecs-MBP / $ docker --version
Docker version 17.03.0-ce, build 60ccb22
alec@Alecs-MBP / $ docker run -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" docker.elastic.co/elasticsearch/elasticsearch:5.2.2
OpenJDK 64-Bit Server VM warning: Insufficient space for shared memory file:
   1
Try using the -Djava.io.tmpdir= option to select an alternate temp location.

[2017-03-18T03:57:03,945][WARN ][o.e.b.Natives            ] unable to load JNA native support library, native methods will be disabled.
java.lang.UnsatisfiedLinkError: Failed to create temporary file for /com/sun/jna/linux-x86-64/libjnidispatch.so library: No space left on device
	at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:866) ~[jna-4.2.2.jar:4.2.2 (b0)]
	at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:826) ~[jna-4.2.2.jar:4.2.2 (b0)]
	at com.sun.jna.Native.<clinit>(Native.java:140) ~[jna-4.2.2.jar:4.2.2 (b0)]
	at java.lang.Class.forName0(Native Method) ~[?:1.8.0_92-internal]
	at java.lang.Class.forName(Class.java:264) ~[?:1.8.0_92-internal]
	at org.elasticsearch.bootstrap.Natives.<clinit>(Natives.java:45) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.initializeNatives(Bootstrap.java:104) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:203) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:112) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.Command.main(Command.java:88) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:89) [elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:82) [elasticsearch-5.2.2.jar:5.2.2]
[2017-03-18T03:57:03,957][WARN ][o.e.b.Natives            ] cannot check if running as root because JNA is not available
[2017-03-18T03:57:03,958][WARN ][o.e.b.Natives            ] cannot install system call filter because JNA is not available
[2017-03-18T03:57:03,959][WARN ][o.e.b.Natives            ] cannot register console handler because JNA is not available
[2017-03-18T03:57:03,967][WARN ][o.e.b.Natives            ] cannot getrlimit RLIMIT_NPROC because JNA is not available
[2017-03-18T03:57:03,967][WARN ][o.e.b.Natives            ] cannot getrlimit RLIMIT_AS beacuse JNA is not available
[2017-03-18T03:57:04,280][WARN ][o.e.b.ElasticsearchUncaughtExceptionHandler] [] uncaught exception in thread [main]
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unable to access 'path.scripts' (/usr/share/elasticsearch/config/scripts)
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:125) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.execute(Elasticsearch.java:112) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.SettingCommand.execute(SettingCommand.java:54) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.Command.mainWithoutErrorHandling(Command.java:122) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.cli.Command.main(Command.java:88) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:89) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:82) ~[elasticsearch-5.2.2.jar:5.2.2]
Caused by: java.lang.IllegalStateException: Unable to access 'path.scripts' (/usr/share/elasticsearch/config/scripts)
	at org.elasticsearch.bootstrap.Security.addPath(Security.java:379) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.addFilePermissions(Security.java:251) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.createPermissions(Security.java:215) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.configure(Security.java:121) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:236) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) ~[elasticsearch-5.2.2.jar:5.2.2]
	... 6 more
Caused by: java.nio.file.FileSystemException: /usr/share/elasticsearch/config/scripts: No space left on device
	at sun.nio.fs.UnixException.translateToIOException(UnixException.java:91) ~[?:1.8.0_92-internal]
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) ~[?:1.8.0_92-internal]
	at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) ~[?:1.8.0_92-internal]
	at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) ~[?:1.8.0_92-internal]
	at java.nio.file.Files.createDirectory(Files.java:674) ~[?:1.8.0_92-internal]
	at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) ~[?:1.8.0_92-internal]
	at java.nio.file.Files.createDirectories(Files.java:767) ~[?:1.8.0_92-internal]
	at org.elasticsearch.bootstrap.Security.ensureDirectoryExists(Security.java:421) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.addPath(Security.java:377) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.addFilePermissions(Security.java:251) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.createPermissions(Security.java:215) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Security.configure(Security.java:121) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:236) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:333) ~[elasticsearch-5.2.2.jar:5.2.2]
	at org.elasticsearch.bootstrap.Elasticsearch.init(Elasticsearch.java:121) ~[elasticsearch-5.2.2.jar:5.2.2]
	... 6 more
alec@Alecs-MBP / $

I think this may be related to the "Docker for Mac" defaults to 2GB ram.
Since you are running ES in the "dev mode" bypassing bootstrap checks, you could try limiting the memory using something like:
docker run -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" -e "ES_JAVA_OPTS=-Xms512m -Xmx512m" docker.elastic.co/elasticsearch/elasticsearch:5.2.2

and see if that works.
If you can afford giving more ram to the linux vm that "Docker for Mac" creates, please increase the amount of RAM by following the instructions here in the section Preferences/Memory (e.g. try 3GB).

It's not the memory.  The issue is:
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Unable to access 'path.scripts' (/usr/share/elasticsearch/config/scripts)
the docker image is missing the config/scripts directory
in addition if I fix that as follows:
docker run --rm -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" -v /tmp/esconfig/scripts:/usr/share/elasticsearch/config/scripts docker.elastic.co/elasticsearch/elasticsearch:5.2.2
then it complains about:
org.elasticsearch.bootstrap.StartupException: java.lang.IllegalStateException: Failed to created node environment
Caused by: java.nio.file.FileSystemException: /usr/share/elasticsearch/data/nodes: No space left on device

If I debug that by getting shell access to the container it seems that there is a data dir but container thinks there is no space left on the device?  Never seen that before with docker.  Is this something to do with the elasticsearch user permissions?
docker run -ti --rm -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" -v /tmp/esconfig/scripts:/usr/share/elasticsearch/config/scripts docker.elastic.co/elasticsearch/elasticsearch:5.2.2 /bin/bash
bash-4.3$ ls -l
total 224
-rw-r--r--    1 elastics elastics     11358 Feb 24 17:24 LICENSE.txt
-rw-r--r--    1 elastics elastics    172700 Feb 24 17:24 NOTICE.txt
-rw-r--r--    1 elastics elastics      9108 Feb 24 17:24 README.textile
drwxr-xr-x    3 elastics elastics      4096 Feb 28 15:04 bin
drwxr-xr-x    4 elastics elastics      4096 Mar 20 13:30 config
drwxr-sr-x    2 elastics elastics      4096 Feb 28 14:49 data
drwxr-xr-x    2 elastics elastics      4096 Feb 28 14:49 lib
drwxr-sr-x    2 elastics elastics      4096 Feb 28 14:49 logs
drwxr-xr-x   12 elastics elastics      4096 Feb 28 14:49 modules
drwxr-xr-x    3 elastics elastics      4096 Feb 28 14:49 plugins
bash-4.3$ cd data/
bash-4.3$ ls
bash-4.3$ echo "blah" >> alec.txt
bash: echo: write error: No space left on device
bash-4.3$ df
Filesystem           1K-blocks      Used Available Use% Mounted on
none                  61893412  59529192         0 100% /
tmpfs                  1023388         0   1023388   0% /dev
tmpfs                  1023388         0   1023388   0% /sys/fs/cgroup
/dev/vda2             61893412  59529192         0 100% /etc/resolv.conf
/dev/vda2             61893412  59529192         0 100% /etc/hostname
/dev/vda2             61893412  59529192         0 100% /etc/hosts
shm                      65536         0     65536   0% /dev/shm
osxfs                244277768 163973092  80048676  67% /usr/share/elasticsearch/config/scripts
tmpfs                  1023388         0   1023388   0% /proc/kcore
tmpfs                  1023388         0   1023388   0% /proc/timer_list
tmpfs                  1023388         0   1023388   0% /proc/sched_debug
tmpfs                  1023388         0   1023388   0% /sys/firmware

So this works:
docker run --rm -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" -v /tmp/esconfig/scripts:/usr/share/elasticsearch/config/scripts -v /tmp/esdata:/usr/share/elasticsearch/data docker.elastic.co/elasticsearch/elasticsearch:5.2.2
But strangely this does not:
docker run --rm -p 9200:9200 -e "http.host=<IP_ADDRESS>" -e "transport.host=<IP_ADDRESS>" -v es_scripts:/usr/share/elasticsearch/config/scripts -v es_data:/usr/share/elasticsearch/data docker.elastic.co/elasticsearch/elasticsearch:5.2.2
again it fails with the "failed to create node because it can't write to the data dir" error.  So my secondary question is why do host mapped volumes work but named volumes do not.  And by the way the docker compose.yml file that uses named volumes on the elastic.co site fails to start for me too.  Really strange?  So these docker containers work for you?

Sorry I skimmed through your logs too quickly and misread the lack of disk space for lack of mem.
Yes the images are working fine e.g. on Docker for Mac 1.13.0 or the latest 17.03.0-ce.
As suggested by my colleague @mentat you could be running out of disk space in your MobyLinux VM (created by Docker for Mac). You could try doing some docker rm and docker rmi for stopped containers/unused images.
Also note that if you use named (or anonymous) docker volumes you don't need to bother with the permissions/ownership but if you -v <local_dir>:/usr/share/elasticsearch/data you need to make sure the local dir is readable/writeable by uid/gid 1000:1000.

yep.  that was it.  I removed my ~/Library/Containers/com.docker.docker/Data/com.docker.driver.amd64-linux/Docker.qcow2 and restarted docker and that fixed the issue and I guess that explains why the anonymous volumes weren't working for me either.  Thanks.


Build ubuntu 22 arm rpi on cncf runners

by mistake the release of arm standard was removed from the master branch, this pr re-introduces it and usese the cncf workers to build those images since the ubuntu 22 arm rpi are simply to big to build on gh free runners
fixes #2611

cancelled runners since the changes only affect other pipelines, but the changes were tested on the pr pipeline


Localize https://k8s.io/docs/contribute/ to Bahasa Indonesia

This is a localization request
What would you like to be added
Localize https://k8s.io/docs/contribute/ into Bahasa Indonesia
Why is this needed
Readers who are looking at the Indonesian (Bahasa Indonesia) documentation, and who might want to contribute (for example, by reviewing changes) should see pages about how to contribute.
Comments
This issue is resolved once https://k8s.io/id/docs/contribute/ exists and contains at least stub pages.
/language id
/priority backlog

I'll kickstart the index page.
Let's put these pages into our backlog and discuss it in our next meeting @girikuncoro @irvifa @danninov @wahyuoi

Understood, let’s discuss this in the next meeting.
On Sat, 4 Jan 2020 at 4.32 PM Yudi A Phanama<EMAIL_ADDRESS>wrote:

I'll kickstart the index page.
Let's put these pages into our backlog and discuss it in our next meeting
@girikuncoro https://github.com/girikuncoro @irvifa
https://github.com/irvifa @danninov https://github.com/danninov
@wahyuoi https://github.com/wahyuoi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/18336?email_source=notifications&email_token=ABYYJZRYADH5ZLKGVAP2SVDQ4BJR5A5CNFSM4J774422YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEICUKSI#issuecomment-570770761,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYYJZWSVXHQAKF3VKYOC63Q4BJR5ANCNFSM4J77442Q
.

Understood, we will discuss this in our next meeting. Thank you @sftim for raising this issue.

/remove-lifecycle stale
Done
/close