[TypeScript] No suggestions or validation

From @TheColorRed on August 14, 2016 20:27

VSCode Version: 1.4.0
OS Version: Ubuntu 16.04 / Windows 10

I am not sure what is causing this, but when I open a file it sometimes suggests items, and other times it does not. The same happens with validation, it sometimes validates errors and other times does not.
This seems to usually happen in files that are using a .d.ts reference that is built when my project runs f5 in my gulp file I have two tasks of which builds two different .d.ts files so other projects (in the same workspace) can run their tsc without the compiler erroring because it can not find the file.
Copied from original issue: Microsoft/vscode#10524

Hello @TheColorRed. Thank you for opening this issue.
As described here, IntelliSense works in three ways.

Type inference.
JS Doc annotations.
TypeScript definition files.

A couple troubleshooting questions to run through.

Do you have a jsconfig.json file?
If you do not, please create one per instructions in this document?

This simple jsconfig.json is copied from the above doc for ease of reference.
{
    "compilerOptions": {
        "target": "ES6"
    },
    "exclude": [
        "node_modules"
    ]
}

If you do, please share it and share where is it in relation to the files that are working and to the files that are not working? (i.e. please send a screenshot of your file directory if possible, if not, please list the contents of your directories with special attention paid to the parent, sibling, child relationships among each directory).

Per the documentation (copied for ease of reference).

Make sure that you place the jsconfig.json at the root of your JavaScript project and not just at the root of your workspace.

Where are the typings files in relation to jsconfig.json?

Per the documentation (copied for ease of reference).

If your project has a jsconfig.json file, then make sure that typings is contained in the project context defined by the location of the jsconfig.json file. If you have no jsconfig.json, then you need to manually add a /// reference to the .d.ts from each JavaScript file.

If you would prefer to see a working reference please check out this repo I made a couple months ago.
For additional configuration help see this Intro Video we released today.

From @TheColorRed on August 15, 2016 19:34
@waderyan I have both a tsconfig.json and a jsconfig.json, and I still do not get any intellisense.
jsconfig.json:
{
    "compileOnSave": true,
    "compilerOptions": {
        "target": "es6",
        "module": "commonjs"
    },
    "exclude": [
        "node_modules",
        "build"
    ]
}

tsconfig.json:
{
    "compilerOptions": {
        "target": "es6",
        "module": "commonjs",
        "outDir": "./build",
        "rootDir": "./src",
        "removeComments": true,
        "experimentalDecorators": true,
        "emitDecoratorMetadata": true,
        "watch": true,
        "allowJs": true
    },
    "exclude": [
        "node_modules",
        "build"
    ],
    "compileOnSave": true
}

Not only is it not suggesting my code, but it is also not suggesting built-in javascript classes/methods/properties.
If I type: doc I would expect to have document suggested, but it is not.
if I type document. I would expect to see the items associated with document suggested, but they are not.

Do you have typescript files?
If you do not delete tsconfig.json.
If you do, delete jsconfig.json.
You do not need both files. Background on the relationship between those two files is in this document (copied below).

The jsconfig.json file corresponds to a TypeScript project tsconfig.json file with the attribute allowJs implicitly set to true.

If that doesn't work.
Send me the logs of tsserver.

Open Settings.
Set "typescript.tsserver.trace" to "verbose"
Save settings.json
Open the Developer Tools (Help -> Toggle Developer Tools)
Copy and paste what shows up in the console.

From @TheColorRed on August 15, 2016 19:57
Here is my verbose output, the only thing I see that might be causing this is that it can not find the project

Response received: quickinfo (12). Request took 1 ms. Success: false . Message: Error processing request. No Project.

Sending request: open (0). Response expected: no. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "fileContent": "const { remote, ipcRenderer } = require('electron');\r\n\r\nlet selectedColor: Color;\r\n\r\nlet oldColorDiv: HTMLDivElement = document.querySelector('div.old-color') as HTMLDivElement;\r\nlet newColorDiv: HTMLDivElement = document.querySelector('div.new-color') as HTMLDivElement;\r\nlet h: HTMLInputElement = document.querySelector('input#h') as HTMLInputElement;\r\nlet s: HTMLInputElement = document.querySelector('input#s') as HTMLInputElement;\r\nlet v: HTMLInputElement = document.querySelector('input#v') as HTMLInputElement;\r\nlet r: HTMLInputElement = document.querySelector('input#r') as HTMLInputElement;\r\nlet g: HTMLInputElement = document.querySelector('input#g') as HTMLInputElement;\r\nlet b: HTMLInputElement = document.querySelector('input#b') as HTMLInputElement;\r\nlet a: HTMLInputElement = document.querySelector('input#a') as HTMLInputElement;\r\nlet hex: HTMLInputElement = document.querySelector('input#hex') as HTMLInputElement;\r\n\r\nlet colorCanvas: HTMLCanvasElement = document.querySelector('canvas#colors') as HTMLCanvasElement;\r\nlet hueCanvas: HTMLCanvasElement = document.querySelector('canvas#hues') as HTMLCanvasElement;\r\n\r\n// If an hsv color changes\r\nh.addEventListener('keyup', onUpdateHSVValues);\r\ns.addEventListener('keyup', onUpdateHSVValues);\r\nv.addEventListener('keyup', onUpdateHSVValues);\r\n\r\n// If an rgba color changes\r\nr.addEventListener('keyup', onUpdateRGBValues);\r\ng.addEventListener('keyup', onUpdateRGBValues);\r\nb.addEventListener('keyup', onUpdateRGBValues);\r\na.addEventListener('keyup', onUpdateRGBValues);\r\n\r\n// If the hex color changes\r\nhex.addEventListener('keyup', onUpdateHexValues);\r\n\r\noldColorDiv.addEventListener('click', (event) => {\r\n    selectedColor = Color.fromHex(oldColorDiv.getAttribute('data-hex'));\r\n    updateValues();\r\n});\r\n\r\nipcRenderer.on('init', (event, colorDetails: { id: string, color: string }) => {\r\n    selectedColor = Color.fromHex(`#${colorDetails.color}`);\r\n    oldColorDiv.setAttribute('data-hex', `#${colorDetails.color}`);\r\n    oldColorDiv.style.backgroundColor = '#' + selectedColor.hex;\r\n    newColorDiv.style.backgroundColor = '#' + selectedColor.hex;\r\n    updateValues();\r\n});\r\n\r\nfunction onUpdateHSVValues(){\r\n    let hh = parseInt(h.value) > 359 ? 359 : parseInt(h.value);\r\n    let ss = parseInt(s.value) > 100 ? 100 : parseInt(s.value);\r\n    let vv = parseInt(v.value) > 100 ? 100 : parseInt(v.value);\r\n    selectedColor = Color.fromHsv(hh, ss, vv);\r\n    updateValues();\r\n}\r\n\r\nfunction onUpdateRGBValues(){\r\n    let rr = parseInt(r.value) > 255 ? 255 : parseInt(r.value);\r\n    let gg = parseInt(g.value) > 255 ? 255 : parseInt(g.value);\r\n    let bb = parseInt(b.value) > 255 ? 255 : parseInt(b.value);\r\n    let aa = parseInt(a.value) > 255 ? 255 : parseInt(a.value);\r\n    selectedColor = new Color(rr, gg, bb, aa);\r\n    updateValues();\r\n}\r\n\r\nfunction onUpdateHexValues(){\r\n    if(hex.value.length == 6){\r\n        selectedColor = Color.fromHex(`#${hex.value}`);\r\n        updateValues();\r\n    }\r\n}\r\n\r\nfunction updateValues(){\r\n    h.value = selectedColor.h.toString();\r\n    s.value = selectedColor.s.toString();\r\n    v.value = selectedColor.v.toString();\r\n\r\n    r.value = selectedColor.r.toString();\r\n    g.value = selectedColor.g.toString();\r\n    b.value = selectedColor.b.toString();\r\n    a.value = selectedColor.a.toString();\r\n\r\n    hex.value = selectedColor.hex.toString();\r\n    newColorDiv.style.backgroundColor = '#' + selectedColor.hex;\r\n    drawPicker();\r\n    drawHues();\r\n}\r\n\r\n// window.addEventListener('update-color-picker', (event: CustomEvent) => {\r\n//     drawPicker();\r\n// });\r\n\r\nfunction drawPicker() {\r\n    let colorContext = colorCanvas.getContext('2d');\r\n\r\n    let hsv = Color.fromHsv(selectedColor.h, 100, 100);\r\n\r\n    // Color Canvas\r\n    let hGrad = colorContext.createLinearGradient(0, 0, 300, 0);\r\n    hGrad.addColorStop(0, '#ffffff');\r\n    hGrad.addColorStop(1, '#' + hsv.hex);\r\n\r\n    let vGrad = colorContext.createLinearGradient(0, 0, 0, 300);\r\n    vGrad.addColorStop(0, 'rgba(0,0,0,0)');\r\n    vGrad.addColorStop(1, '#000000');\r\n\r\n    colorContext.fillStyle = hGrad;\r\n    colorContext.fillRect(0, 0, 300, 300);\r\n\r\n    colorContext.fillStyle = vGrad;\r\n    colorContext.fillRect(0, 0, 300, 300);\r\n}\r\n\r\nfunction drawHues(){\r\n    let hueContext = hueCanvas.getContext('2d');\r\n\r\n    // Hues Canvas\r\n    let hueGrad = hueContext.createLinearGradient(0, 0, 0, 300);\r\n    hueGrad.addColorStop(0.00, '#ff0000');\r\n    hueGrad.addColorStop(0.15, '#ff00ff');\r\n    hueGrad.addColorStop(0.30, '#0000ff');\r\n    hueGrad.addColorStop(0.50, '#00ffff');\r\n    hueGrad.addColorStop(0.70, '#00ff00');\r\n    hueGrad.addColorStop(0.85, '#ffff00');\r\n    hueGrad.addColorStop(1.00, '#ff0000');\r\n\r\n    hueContext.fillStyle = hueGrad;\r\n    hueContext.fillRect(0, 0, 20, 300);\r\n}\r\n\r\nlet mousedown: boolean = false;\r\n\r\nhueCanvas.addEventListener('mousedown', (event) => {\r\n    mousedown = true;\r\n    setFromHueCanvas(event);\r\n});\r\nhueCanvas.addEventListener('mouseup', (event) => {\r\n    mousedown = false;\r\n});\r\nhueCanvas.addEventListener('mouseleave', (event) => {\r\n    mousedown = false;\r\n});\r\n\r\nhueCanvas.addEventListener('mousemove', (event) => {\r\n    if(mousedown) {\r\n        setFromHueCanvas(event);\r\n    }\r\n});\r\n\r\nfunction setFromHueCanvas(event){\r\n    let rect = hueCanvas.getBoundingClientRect();\r\n    let y = event.clientY - rect.top;\r\n    selectedColor = Color.fromHsv(Math.abs((y / rect.height * 360) - 360), selectedColor.s, selectedColor.v);\r\n    updateValues();\r\n}"
}

Sending request: geterr (1). Response expected: no. Current queue length: 0
Arguments: {
    "delay": 0,
    "files": [
        "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts"
    ]
}

Sending request: change (2). Response expected: no. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 1,
    "endLine": 23,
    "endOffset": 1,
    "insertString": "d"
}

Sending request: completions (3). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 2
}

Response received: completions (3). Request took 1 ms. Success: false . Message: Error processing request. No Project.
Sending request: geterr (4). Response expected: no. Current queue length: 0
Arguments: {
    "delay": 0,
    "files": [
        "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts"
    ]
}

Sending request: change (5). Response expected: no. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 2,
    "endLine": 23,
    "endOffset": 2,
    "insertString": "o"
}

Sending request: change (6). Response expected: no. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 3,
    "endLine": 23,
    "endOffset": 3,
    "insertString": "c"
}

Sending request: geterr (7). Response expected: no. Current queue length: 0
Arguments: {
    "delay": 0,
    "files": [
        "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts"
    ]
}

Sending request: occurrences (8). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 1
}

Response received: occurrences (8). Request took 1 ms. Success: false . Message: Error processing request. No Project.
Sending request: change (9). Response expected: no. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 23,
    "offset": 1,
    "endLine": 23,
    "endOffset": 4,
    "insertString": ""
}

Sending request: geterr (10). Response expected: no. Current queue length: 0
Arguments: {
    "delay": 0,
    "files": [
        "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts"
    ]
}

Sending request: quickinfo (11). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 31,
    "offset": 39
}

Response received: quickinfo (11). Request took 1 ms. Success: false . Message: Error processing request. No Project.
Sending request: quickinfo (12). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "c:/Users/rnaddy/Documents/vscode/projects/game-engine/src/GameEditor/controllers/color.ts",
    "line": 7,
    "offset": 39
}

Response received: quickinfo (12). Request took 1 ms. Success: false . Message: Error processing request. No Project.

Hmmm, I commented everything out in a non-working file and I started to get suggestions from the server... I then restarted vscode, and completion stopped again. Commenting out the file didn't work the second time...

@TheColorRed can you share a project we can look at to reproduce this? what version of TS are you using? do you have a "typescript.tsdk" set in your vscode user or workspace settings file?

The project I am using is here: https://github.com/TheColorRed/game-engine
The files that don't seem to work are src/GameEditor/*.ts I haven't tried them all, but I know I am having issues with this file: src/GameEditor/controllers/main.ts
The files in src/Editor and src/Engine seem to work fine.

there is something else going on here then. i cloned your project, opened it in VSCode 1.4, with the built in TS version and things seem to work just fine.

is there a special setup that i need to be aware of? what is the OS? any set of actions that i need to take?

I opened my project up today, and it started working for me too all of a sudden....
I wonder if it was a plugin that was causing it...
I will keep an eye see if it goes away again...

It is now gone again, and no you shouldn't need any special setup.
It happens on both my Windows 10 and Ubuntu 16.04

so what happened before it got to this state?

I have no Idea what happened. I did however create a fresh clone of the project and then opened it. I was able to get intellisense on the file that wasn't working for me.
Here are steps I did and was able to reproduce the issue multiple times:

Clone Repo
Open in vscode
Autocomplete works
run npm install
Restart vscode
Autocomplete still works
Build and run the project
Autocomplete still works
Restart vscode
Autocomplete is now broken

does building the project generate other .ts or other .d.ts files?

Yes, it also creates an asar file.

If I delete just the .d.ts files it still doesn't work.
If I delete just the asar file it works.

So, Is the asar file blocking suggestions? Why would it work without the asar file and break if it is not there?

where is that file created? how can i reproduce that?

Preparation:

Pull in my latest changes it has an updated package.json file.
Install the npm modules npm install
In vscode press F5 build then run, or press Ctrl+Shift+B to build it (launch.json only has support for linux or windows)

The gulp file should do the following:

Remove any previous builds
Compile the src/Engine folder into a file build/gameEngine.js
Compile the src/Editor folder into a file build/gameEditor.js
Compile the src/GameEditor folder into multiple files and place them in build/Editor
Copy the src/GameEditor/resourecs resources into the build/Editor/resources folder
Copy the Reflect.js from the node_modules into the build folder
Finally create a bin/GameEditor.asar file

Once that is complete, suggestions stop (Might have to restart vscode).

I see the same behavior now. thanks for the repro.
So looks like node thinks the .asar file is a folder, and then we try to add a watch to the contents of this folder, then we fail. we are not handling the exception correctly, and that breaks the server operations from that point on. that is something that we should be able to fix.
For now, if you add bin to your excludes in tsconfig.json should get it to work again.

@zhengbli can you take a look..

I can no longer repro this issue, even after npm install, build and generate the .asar file.

Could it be because I removed the /// <reference> items from the code?

Okay, after testing, I am still able to reproduce the issue with the latest code from the repo...

@TheColorRed can you try use the nightly TS version?

I installed it, how do I know if the editor is using that version?

@TheColorRed you can see it in the bottom right. Follow instructions here. https://code.visualstudio.com/docs/languages/typescript#_using-newer-typescript-versions

After trying with the nightly build it works it works and suggests items.

Awesome. Closing this.


keypair: keynames will not match if user sets different keyname in YAML

The keyname stanza of the YAML defaults to the username, e.g.:
keyname: smithfarm

The generate-keys.sh script assumes the default and uses $(whoami) as the basis of the keyname.
If the user changes the keyname in the YAML to any value other than the username, node instantiation will fail.

This one could be closed as it was fixed in the meanwhile

Fixed by #31


SSO devops/pipeline improvement

Describe the issue
We encounter several issues from CICD pipeline during SSO resource update:

pipeline have some major issue, need to revisitError: command: oc --namespace=devops-sso-test apply -f - --output=name
stderr:The routes "sso-test" is invalid: metadata.resourceVersion: Invalid value: 0x0: must be specified for an update

prod SSO have different pod count, which would not be included in oc template (integer numbers), need to consider converting to jinja
the new oidc routes are not yet automatically created

As a result, we'll need to try out other cicd options. A good starting point is to create a maintenance/upgrade pipeline.
Options:

debug and fix issues with bcdk
migrate to use raw oc
ansible playbook

Definition of done

explore on different options
plan on update/fix

we should bring @j-pye into the conversation about future proofing our pipeline refactor so that it can blend with Argo or Tekton


Support for openSuse MicroOS

Is your feature request related to a problem? Please describe.
K3OS does not get updates anymore. OpenSuse MicroOS seems to be the natural successor.
Describe the solution you'd like
Upgrading openSuse MicroOS from within K3S. So I can fully manage my cluster(s) using Rancher UI.
Describe alternatives you've considered
Rely on different upgrade mechanisms described by Suse. All of them need additional workflows.
Additional context
As K3S upgrades using system-upgrade controller, and K3OS did that too, it seems natural to follow this way.

Is this a problem with SUC or a problem with assumptions baked into https://github.com/k3s-io/k3s-upgrade/blob/a78cfaf2446b8d6b014a76c2812a1349e1738e37/scripts/upgrade.sh ?
Likely more appropriate to bring this up with the k3s project directly: https://github.com/k3s-io/k3s/issues

There is an example available at https://github.com/rancher/system-upgrade-controller/blob/master/examples/openSUSE/microos.yaml


Add convenience methods for asserting table contents

A common pattern in our tests is to call some application code and then verify
that the database was updated correctly. This usually looks something like
assertEquals(
    listOf(
        SomeTableRow(col1 = "foo", col2 = "bar"),
    ),
    someTableDao.findAll().map { it.id = null })

This pattern is an occasional source of spurious test failures when we forget
that findAll() doesn't guarantee any particular order of results.
Introduce a new set of methods in DatabaseBackedTest that are more succinct to
call, offer more flexibility, and avoid the possibility of test failures due to
assumptions about result order.

#2418  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sgrimm and the rest of your teammates on  Graphite


example

hello, i am very interested in your component, its looks really promising
but i have some questions

how to avoid self closing after click in last level
stop at specific level, perhaps if  :title ['A', 'B', 'C'] - dont go further, also when C has childs
can we jump to a specific level
can we get the  filtering over all levels
there are some fixed chinese placeholder, messages

thank you very much
marc

For its possible to jump to a specific level in the tree ,its a awesome feature.
But search over all items is breaks the current structure，
And i dont know why data is changed, I think it should be a fixed value unless you set the remote and remote-method props


Bug with list of pickups awaiting feedback accross groups

The list of pickups awaiting feedback is not group-bound. All the pickups I made on two different groups are showing on the feedback page of each group.
As I write this I noticed that after changing groups back and forth the list of pickups awaiting feedback has doubled in both groups (14 now instead of 7). I guess this is related but I haven't tested more.
Edit: indeed, after changing groups again and checking the list, it has tripled

Closed by https://github.com/yunity/karrot-frontend/commit/cfa1769142dff44acf0ff2e01ca8b4ac1d68fce5


Art: Silk Worms

These will be the first enemies the player encounters, in the BR fields.
They have a drop chance for SILK on kill. They should also feel like enemies, but not be overly scary - more of a farmable mob.

Initial concept

https://user-images.githubusercontent.com/80061436/142674192-48267b61-ef48-4046-8ab0-658c54f90e8b.mp4
This is mostly complete on the modelling end, has a simple rig - the blend is in drive for animating and further tweaks, which will come after engine tweaks to shaders.


Add startReplyChain to UniversalBot and IConnector

At the moment the following connectors implement the startReplyChain:

botbuilder-teams
(https://github.com/OfficeDev/BotBuilder-MicrosoftTeams)
botbuilder-slack (https://github.com/suttna/botbuilder-slack)

On both cases, the current solution at the connector level breaks the
usage of middlewares. In both cases, the "send" middleware is not called
when sending a message using the startReplyChain api.
We want to standarize the startReplyChain since a lot of clients support
it and is very useful operation. The idea would be to get this merged so
that both previously mentioned libraries can update the implementation
to match the new signature.

Closing this PR because the code for this repository has been moved to https://github.com/Microsoft/BotBuilder-V3  If you think this PR is still relevant, please re-submit on the new repository.


windows_registry::find_tool can report the Tool as being in the gnu family

windows_registry::find_tool should surely return a MSVC family tool as that's the point of the function. However, although it finds the tool correctly, is_like_msvc() is returning false.
use cc::windows_registry;

fn main() {
    let linker = windows_registry::find_tool("x86_64-pc-windows-msvc", "link.exe").unwrap();
    println!("{}", linker.path().to_string_lossy());
    dbg!(
        linker.is_like_msvc(),
        linker.is_like_gnu(),
    );
}

Output:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.25.28610\bin\HostX64\x64\link.exe
[src\main.rs:6] linker.is_like_msvc() = false
[src\main.rs:6] linker.is_like_gnu() = true

As far as I can tell it falls back to the default tool family detection code, which in turn seems to mostly assume it's GNU unless it's cl. But I'm still finding my way round the code so I could be wrong.

Definitely seems like a bug! A PR would be most welcome to help and fix.


Avalon: Not showing all evil

Bug found:
it.knownThumbs = it.character!!.seesThumbs().mapNotNull { ch -> game.players.find { pl -> pl.character == ch } }.toSet()
it.character!!.seesThumbs() returns a Set of characters who's thumbs you are supposed to see, and this is then mapped to a player that matches this character. It's a 1-1 mapping and not 1-many mapping which is the problem.


Help

Not working where to find my
url

Because you haven't replaced the repl url.

6.Replace your website URL at index.js

Because you haven't replaced the repl url.

6.Replace your website URL at index.js

How how can i get an url

Watch the video again specially at 01:35

I guess not , because if you have followed all the steps correctly then it should have worked. Also do send me the screenshot of your index.js file.

Ok give me yours talegram link


How to use composer with phpbrew?

I installed phpbrew to use php 5.4 in Ubuntu 14.04. It works fine, except when I try to use composer, which ignores phpbrew and installs dependencies related to php 5.5.
Is there a way to force composer to be compatible with phpbrew config? I trying to add: php: "5.4" in my composer.json, but it says that this requirement is not possible with my php version.

Hi,
What do you get when you run phpbrew list? Don't forget that you must run phpbrew use <php-version> before running composer. You are probably still using the system php version.

solved it: it was because of my composer.lock : I replaced it by the one on my server (php 5.4) and now I have no more errors in my vendor libraries.
thx!


Unreported internal failure at gen_box

Compiling following code ends in internal failure:
type U is (Bool | C)

class C
  fun apply(): (I32, U) =>
    (0, false)

actor Main
  new create(env: Env) =>
    C()

Output:
Building builtin -> /home/ta3ta1/Code/ponyc/packages/builtin
Building . -> /home/ta3ta1/Code/issue
Generating
 Reachability
 Selector painting
 Data prototypes
 Data types
 Function prototypes
 Functions
Error: internal failure not reported

Compiler version:
0.18.0-6fdd5dbb [release]
compiled with: llvm 3.9.1 -- cc (Debian 6.3.0-18) 6.3.0 20170516

While codegen, failure(returning NULL) happens at here.
I guess something goes wrong while "Reachability" process.

Following code is successfully compiled: (change Bool to I32)
type U is (I32 | C)

class C
  fun apply(): (I32, U) =>
    (0, 1)

actor Main
  new create(env: Env) =>
    C()

I bisected to dec7b7bf9dddf4c4bcff0876b59b1fba3d464041.
I don't understand codegen, but following patch seems fix this issue.
@Praetonus Is this correct?
--- a/src/libponyc/codegen/genbox.c
+++ b/src/libponyc/codegen/genbox.c
@@ -17,7 +17,7 @@ LLVMValueRef gen_box(compile_t* c, ast_t* type, LLVMValueRef value)
   pony_assert(t != NULL);
   compile_type_t* c_t = (compile_type_t*)t->c_type;

-  if(l_type != c_t->primitive)
+  if(l_type != c_t->primitive && l_type != c_t->mem_type)
     return NULL;

   value = gen_assign_cast(c, c_t->mem_type, value, t->ast_cap);

The problem is that gen_box expects a value with value type, but assign_to_tuple in genexpr.c will pass a value with memory type.
@ta3ta1 That would be a correct fix. Would you be up to do a pull request with that fix?

Yes, I'll open it.
Thank you.


Uploading cookbook version 0.2.2 to chef throws compile errors

Trying to upload the cookbook to chef shows the following errors:
knife cookbook upload resource
Uploading resource       [0.2.2]
FATAL: Cookbook file  has a ruby syntax error:
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:14: syntax error, unexpected keyword_nil, expecting keyword_do or '{' or '('
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:19: syntax error, unexpected '}', expecting keyword_end
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:23: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :identity_defined         { default }
FATAL:                                               ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:24: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :fully_defined        { default }
FATAL:                                           ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:25: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :updating     { default }
FATAL:                                   ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:26: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :updated        { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:27: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :not_updated    { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:28: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :updated      { default }
FATAL:                                   ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:29: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :update_failed  { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:30: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :debug          { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:31: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :info           { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:32: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :warn           { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:33: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :error          { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:34: syntax error, unexpected '{', expecting keyword_end
FATAL:           property :fatal          { default }
FATAL:                                     ^
FATAL: /<removed>/chef-repo/cookbooks/resource/files/lib/chef_resource/output/nested_converge.rb:93: syntax error, unexpected end-of-input, expecting keyword_end

I'm a newby to both chef and ruby so very much just trying to get my head around how to create my own cookbooks etc.  Trying to use this cookbook but getting the same errors you report.  Anyone any idea what the underlying issue is?

+1
I've got the same issue

I am also having the same issue.

I am having this same issue. Is there a workaround to be able to upload this cookbook to a Chef server?

I am also having same issue with berks upload to chef server provided by opscode. I tried to upload version 0.2.1 of resource cookbook and no luck. I have following versions installed on work station. I added C:/users//chefdk/embedded/bin to my PATH environment variable.
Chef Development Kit Version: 0.6.2
chef-client version: 12.3.0
berks version: 3.2.4
kitchen version: 1.4.0
Please suggest if there is a way to upload this.

Closing this as this repository is now deprecated


Compile error on SPStorkPresentationController.swift

I've added the pod (version 1.6) and when compiling the app I get a compile error in SPStorkPresentationController.swift.
The error is: Type 'CAMediaTimingFunctionName' (aka 'NSString') has no member 'easeOut'
Thank you!

Probably it is my fault, because the app was using Swift 4.0. Sorry


more quantize testing

In light of @czender recent discovery of issue #2441, I think I need to beef up quantize testing.

OK, so with PR #2457 all the existing quantize tests were extended to test:

With and without NC_CLASSIC_MODEL
All three quantize algoritms.

@DennisHeimbigner I don't think this will impact the way you are using tst_quantize to test nczarr. And all my tests pass, so please let me know if there is a problem.


Fix remove original director

Description
As a title.
Changes

Removed a original director.

Impact range
N/A
Operational Requirements
N/A
Related Issue

Supplement

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 83.21%. Comparing base (8f75c5d) to head (52c55c6).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #54   +/-   ##
=======================================
  Coverage   83.21%   83.21%
=======================================
  Files           6        6
  Lines         137      137
=======================================
  Hits          114      114
  Misses         22       22
  Partials        1        1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Create example showing code node created inside and outside board, and anonymously

Add example showing the code node being used that is created inside and outside a board, and anonymously.
The created sample will need to be added to the breadboard mono-repo, and then referenced and linked in the Breadboard README doc (in the "Creating code nodes" section of packages/breadboard/README.md).
A sample has been created:
import { base, board, code } from "@google-labs/breadboard";

// Created outside board
const split = code(({ toSplit }) => {
	if (typeof toSplit !== "string") return {};
	return { split: toSplit.split("") };
});

const reverserBoard = board(() => {
	const input = base.input();
	const output = base.output();

	const splitNode = split();
	input.message.as("toSplit").to(splitNode);

	// Created inside board
	const reverse = code(({ toReverse }) => {
		if (!Array.isArray(toReverse)) return {};
		return { reversed: toReverse.reverse() };
	});

	const reverseNode = reverse();
	splitNode.split.as("toReverse").to(reverseNode);

	// Anonymous
	const concat = reverseNode.reversed.as("arr").to(
		code(({ arr }) => {
			if (!Array.isArray(arr)) return {};

			return { concatenated: arr.join("") };
		})()
	);

	concat.concatenated.to(output);

	return output;
});

console.log(await reverserBoard({ message: "Hello World!" })); // { concat: '!dlroW olleH' }

Discussed with Joe and going to write this up into a fuller doc

This applies to the old syntax.


Add template files

Ref: https://github.com/kubernetes/steering/issues/28 (for CONTRIBUTING.md) and https://github.com/kubernetes/community/issues/3053 (for CoC) and https://github.com/kubernetes/steering/issues/57#issuecomment-450132738 (for LICENSE)
The content is as per https://github.com/kubernetes/kubernetes-template-project
/assign @andrewsykim @cheftako @mcrute

Thanks!
/lgtm
/approve

/lgtm

Thanks @nikhita


observe transform should be usable from pub

 Issue by jmesserly
Originally opened as dart-lang/sdk#14888

quoting siggi to web-ui list:
Almost, but not quite, we should open a bug for this.
By default pub would let you say 'observe' to mean "observe/transformer.dart', but in package:observe this file doesn't exist. Pub let's you specify a specific path, so instead of 'observe' you can say:
transformers:

observe/transform.dart

However, the file you specify needs to have a plugin API (a transformer with a constructor named .asPlugin). We have these in polymer, but not in observe. You can add one yourself in your package instead:
mypackage/lib/observe_transformer.dart:
class WorkAround extends ObservableTransfomer {
   WorkAround.asPlugin() : super();
}
Then use this instead in your pubspec:
transformers:

mypackage/observe_transformer.dart   # skip the 'lib' here, this is like a package: import

 Comment by sigmundch

The proper fix is simple:

rename observable/transform.dart to obserable/transfomer.dart,
add the asPlugin constructor to ObservableTransfomer

Then you can just say:
transformers:

observe

Changed the title to: "observe transform should be usable from pub".

 Comment by munificent

mypackage/observe_transformer.dart   # skip the 'lib' here, this is like a package: import

You don't need the ".dart" there either. :)

 Comment by jmesserly

Removed Priority-Unassigned label.
Added Priority-Medium label.

 Comment by anders-sandholm

Removed Library-Observe label.
Added Pkg-Observe label.

 Comment by sigmundch

fix landed in dart-lang/sdk@536f92456dc123ee61f3d268ac0d6cfef22fa625

Added Fixed label.

 Comment by sigmundch

FYI, I needed this for another bug fix, so it's coming in soon. See:
https://codereview.chromium.org/63173009/


Allow to pass logout redirect url to the client

Alternatively, would it make sense to automatically pass the logout URL from the security (through the LogoutUrlGenerator)?

any updates on the pull request?


[BUG] Rancher deployed charts respect Rancher min/max version and k8s min/max version. (Webhook)

This can be addressed by https://github.com/rancher/rancher/issues/40159

Webhook doesn't need to check k8s version, because it is tied directly to rancher, and rancher has its own k8s matrix which handles that case.

I think we can close and rely on 40159 to solve

This is an issue for hosted providers operators as well
https://github.com/rancher/rancher/issues/41123


[Store] UI issue in response download button

Issue
In download button,button text is out of button field.

fixed in 3.0.0 beta


Register MetaAnalysis.jl

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/88314
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 074b703163dbcbff33a5604c9c0628e1b4bf93aa
git push origin v0.1.0


Cannot resolve parameter MediatR.SingleInstanceFactory singleInstanceFactory

I thought I'd give MediatR a try but keep getting autofac errors.
None of the constructors found with 'Autofac.Core.Activators.Reflection.DefaultConstructorFinder' on type 'MediatR.Mediator' can be invoked with the available services and parameters:
Cannot resolve parameter 'MediatR.SingleInstanceFactory singleInstanceFactory' of constructor 'Void .ctor(MediatR.SingleInstanceFactory, MediatR.MultiInstanceFactory)'.

Autofac registration
builder.RegisterSource(new ContravariantRegistrationSource());
builder.RegisterAssemblyTypes(typeof(IMediator).Assembly).AsSelf().AsImplementedInterfaces();

My controller
 public class PeopleController : Controller
    {
        private readonly IMediator _mediator;

        public PeopleController(IMediator mediator)
        {
            _mediator = mediator;
        }
...

I've fixed the error by changing the registration to this
builder.RegisterSource(new ContravariantRegistrationSource());
builder.RegisterAssemblyTypes(typeof(IMediator).Assembly).AsSelf().AsImplementedInterfaces();
builder.Register<SingleInstanceFactory>(ctx =>
{
	var c = ctx.Resolve<IComponentContext>();
	return t => c.Resolve(t);
});
builder.Register<MultiInstanceFactory>(ctx =>
{
	var c = ctx.Resolve<IComponentContext>();
	return t => (IEnumerable<object>)c.Resolve(typeof(IEnumerable<>).MakeGenericType(t));
});

But now it doesn't work with async actions
The requested service 'MediatR.IAsyncRequestHandler`2[[OfficeManager.Features.People.Edit+Query, OfficeManager, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null],[OfficeManager.Features.People.Edit+Command, OfficeManager, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null]]' has not been registered. To avoid this exception, either register a component to provide the service, check for service registration using IsRegistered(), or use the ResolveOptional() method to resolve an optional dependency.

Hi @TDK1964
you need to also register on Autofac your handlers. Try adding the following line after:
        builder.RegisterAssemblyTypes(assembly)
            .AsClosedTypesOf(typeof(IRequestHandler<,>))
            .AsImplementedInterfaces();

        builder.RegisterAssemblyTypes(assembly)
            .AsClosedTypesOf(typeof(IAsyncRequestHandler<,>))
            .AsImplementedInterfaces();

        builder.RegisterAssemblyTypes(assembly)
            .AsClosedTypesOf(typeof(INotificationHandler<>))
            .AsImplementedInterfaces();

        builder.RegisterAssemblyTypes(assembly)
            .AsClosedTypesOf(typeof(IAsyncNotificationHandler<>))
            .AsImplementedInterfaces();

@kappy thanks for the feedback.
I actually did this while I was waiting for replies and it seemed to work. Is this acceptable?
 builder.RegisterAssemblyTypes(AppDomain.CurrentDomain.GetAssemblies())
               .Where(t => t.Name.EndsWith("Handler"))
               .AsImplementedInterfaces()
               .InstancePerRequest();

That is more a Autofac related case other than MediatR.
I don't know all the considerations about using  the name string compare vs the type.

@kappy, on a seprate note, do you know how to convert this the autofac?

private static IElementGenerator<T> GetGenerator<T>(T model) where T : class
{
      var library = StructuremapMvc.ParentScope.CurrentNestedContainer.GetInstance<HtmlConventionLibrary>();
      return ElementGenerator<T>.For(library, t => StructuremapMvc.ParentScope.CurrentNestedContainer.GetInstance(t), model);
}


the first item will flash when the second loop start, only appear in android

Which OS ?
android only
Version
Which versions are you using:

react-native-swiper v1.6.0
react-native v0.61.2
huawei honor 30s
android 10

Expected behaviour
loop does not flash
Actual behaviour
when i set loop={true}, the first item will flash when the second loop start, only appear in android
How to reproduce it>
To help us, please fork this component, modify one example in examples folder to reproduce your issue and include link here.

https://user-images.githubusercontent.com/26846424/111100787-7bd99880-8583-11eb-9860-c60f690f940e.mov

Steps to reproduce
1.use the demo which provide in README.md
2.set horizontal={false}
3.the issues will appear in android

+1

+1

+2

The same issue

+1

+1

I have same issue the first screen flashes before render the second screen

+1

This issue can refer to #1200
That works for me.

Bug iOS same.

+1

After read the soruce code, I think it's not easy to fix this, because when loop=true.
Because the inner is a ScrollView. And the loop effect is by add a fake view to the first and the last. And quick scroll to the right place when scrool to the fake view.
For example, if the child view is ["1", "2", "3"], when loop=true, the child view is ["3", "1", "2", "3", "1"], and when scroll to the first "3"[index = 0], then scroll to the "3"[index=3] quickly, so the flash happed.

+1

removeClippedSubviews={false}
u r welcome!

removeClippedSubviews={false} u r welcome!

it works for me , thanx

removeClippedSubviews

It works!!!!!!!

Thanks a bunch, it works for mw

me too

removeClippedSubviews={false} u r welcome!

it works for me , thanx

tks,deal


Arch package fails to install

Cannot install rivalcfg-git from the AUR. Fails with the following error:
Traceback (most recent call last):
  File "setup.py", line 7, in <module>
    from setuptools import setup, find_packages
ModuleNotFoundError: No module named 'setuptools'

Installing rivalcfg-git works successfully after installing the python-pip Arch package. Seems like a missing dependency?

Hello,
setuptools is actually required to make setup.py working, but I cannot add it to dependency of my python package as the dependencies are listed in the setup.py file that cannot be used if setuptools is not installed...
We should ask the maintainer of the Arch package to add this dependencies to the PKGBUILD file (makedepends=('git' 'python-setuptools'))  (cc @defkeh, @Thiblizz).
Currently you can workaround by installing the python-setuptools package manually :)

So sad, someone took the ownership of the package just after I asked to maintain it :(.

I commented on AUR to tell the maintainer to update :)

Hey, current maintainer here. I updated the package accordingly.
I took ownership a while ago for some reason I can't remember, probably wanted to update it a bit.
@Thiblizz if you'd like ownership just tell me. Could also add you as a co-maintainer if you'd like, just tell me your AUR username.

AUR package was updated to include python-setuptools as a dependency and is now working as intended


Seedy-Threepio.Theseus2000 version 1.2C

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

If the URL is invalid, how was Winget-Create able to gather metadata about the installer file? As far as I know, no bot filters are in place, unless cloudflare is blocking something.

The bot is unhappy because the domain doesn't appear to be associated with the publisher or package name.  As definitely a human, I was able to determine that everything does appear to be good.

@wingetbot waivers Add Validation-Domain

How can I get around such an error in future? I really don't fancy getting a new domain.


IPC Server: borrowed A/B/W buffers should outlive futureobj

Currently, for IPC, a function that looks like this:
    [0] launch_title(array<u8, 9> title_name, array<u8, 9> args) -> u64 pid;

Generates a trait method that looks like this:
    fn launch_title(&mut self, _workqueue: WorkQueue<'static>, title_name: &[u8], args: &[u8]) -> FutureObj<'_, Result<u64, Error>>

This is unnecesarily restrictive. The trait prevents putting title_name and args inside the Future, as it does not guarantee that FutureObj outlives them. And yet in practice, they do! The A/B/W buffers will only be unmapped after the FutureObj resolves, and as such they outlive the FutureObj.
This is problematic because it prevents writing something like this (taken from loader):
        FutureObj::new(Box::new(async move {
            let title_name = str::from_utf8(title_name).or(Err(LoaderError::ProgramNotFound))?;
            boot(&*BOOT_FROM_FS, title_name, args)
        }))

As a workaround, since this specific function doesn't need async, I implemented it this way instead:
        let res = (|| -> Result<u64, Error> {
            let title_name = str::from_utf8(title_name).or(Err(LoaderError::ProgramNotFound))?;
            boot(&*BOOT_FROM_FS, title_name, args)
        })();
        FutureObj::new(Box::new(async move {
            res
        }))

This is clearly suboptimal.

Note about whether this extends to C/X buffers: I am unsure. C buffers are currently unsupported and I'm not sure how to approach them anyways. X buffers depend on where the server's C buffer is allocated. If it's allocated by-session, then sharing it should be fine.


Upgrades Laravel Zero Framework & Adds Collision

This PR addresses:

Upgrade of the Laravel Zero Framework.
Adds Collision: The new default error handler of Laravel Zero.

Nice! Thanks! :+1:


初始的时候最大化窗口，再setFullScreen(false)的时候，窗口异常

在waitUntilReadyToShow的时候，设置fullScreen为true。这个时候发现setFullScreen(false)恢复的时候，窗口只有背景色，无任何内容，也任务栏图标也消失。windowManager.minimize();这个调用也无任何反应。
平台为windows。

In english vis google translate:
When waitingUntilReadyToShow, fullScreen is set to true. At this time, when setFullScreen(false) is restored, the window only has the background color, no content, and the taskbar icon disappears. The call windowManager.minimize() also has no response. The platform is Windows.

@ibaoyun  Can you close here since you re-reported in english in #458 ?

与 https://github.com/leanflutter/window_manager/issues/458 重复，先关闭了


Codeclimate/HoundCI configuration

Added the same HoundCI configurations as we already have for all other crowbar components
Updated the Codeclimate configuration to the same as all other crowbar components are following

:+1:

:+1:


Merge pull request #1 from jeffshek/master

Update my fork from the master fork.

Sorry. Got this direction wrong.


timeout when trying with the test backend

Hi,
I am trying to run your proxy locally, and I always see the following error message:
ERROR:alacrity: Error trying proxy - Error { repr: Custom(Custom { kind: TimedOut, error: StringError("Pool connection timeout") }) }

The test server outputs:
Read 0 bytes
Wrote 0 bytes

I am running on Mac.
If I can help find this issue, please tell me! ;)

Some more log:
RUST_LOG=alacrity=trace cargo run --bin alacrity
    Finished debug [unoptimized + debuginfo] target(s) in 0.0 secs
     Running `target/debug/alacrity`
INFO:alacrity::pool: Load balancing server V4(<IP_ADDRESS>:12345)
INFO:alacrity: Listening on: <IP_ADDRESS>:8080
DEBUG:alacrity: Incoming connection on <IP_ADDRESS>:57013
DEBUG:alacrity::pool: Pool is cloaning (hehe) out <IP_ADDRESS>:12345
ERROR:alacrity: Error trying proxy - Error { repr: Custom(Custom { kind: TimedOut, error: StringError("Pool connection timeout") }) }

I will take a look in about 1 hour.

One guess (I'm quite new to rust and futures):
        let connect_timer = futures::finished(timeout).map(Err);

creates a Future that is already finished, but we'd like a Future that terminates after the timeout, no?
Instead, we could directly use the timeout future, like let connect_timer = timeout.map(Err);?
With that change, I do not have this error anymore.
But I don't know how to test the timeout, if it's working or if I totally broke it.

@yanns that is a solid fix. it took me a while to figure out why this was ever working. apparently, when i was in full debug mode the timeout would not fire, but it would fire if i lowered the debug mode.
you are right about the way futures::finished worked too


[geotrans] Passes now on Android.

https://dev.azure.com/vcpkg/public/_build/results?buildId=91681&view=logs&j=185c373b-2f55-539e-a6cb-ef2677cc0d97&t=bd42ae40-c428-56e6-fb3d-bb973ea0084d
PASSING, REMOVE FROM FAIL LIST: geotrans:arm-neon-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: geotrans:arm64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).
PASSING, REMOVE FROM FAIL LIST: geotrans:x64-android (/vcpkg/scripts/azure-pipelines/../ci.baseline.txt).

Previously was changed from skip to fail in https://github.com/microsoft/vcpkg/commit/6b8459636c7ab9f2ccb638697b2ac990e1fd64b1

This issue fixed by PR https://github.com/microsoft/vcpkg/pull/32519, the current CI error(openvino failed) is not related to my changes, I think you can directly merge the PR.


Failed to obtain reader

Describe the bug
First-time user, I am trying to create a workspace (docker-local).
Just using a public repo: https://github.com/maxday/lambda-perf
❯ daytona create
 WORKSPACE   | ✓ Request submitted
 WORKSPACE   | ✓ Creating workspace lambda-perf (28635ab5651c)
 lambda-perf | Creating project lambda-perf
 lambda-perf | Pulling image...
 lambda-perf | Pulling from daytonaio/workspace-project
 lambda-perf | Digest: sha256:adf39125cf348f8801b8e1d9be37d0693eade0602344b42908433b5c9be1c7ad
 lambda-perf | Status: Image is up to date for daytonaio/workspace-project:latest
 lambda-perf | Image pulled successfully
 lambda-perf | Group with GID exists (dialout=20).
 lambda-perf | Updating UID:GID from 1000:1000 to 501:1000.
 lambda-perf | Cloning into '/workdir/28635ab5651c-lambda-perf'...
 lambda-perf | Updating files: 100% (936/936), done.
 lambda-perf | Group with GID exists (dialout=20).
 lambda-perf | Updating UID:GID from 1000:1000 to 501:1000.
 lambda-perf | Project lambda-perf created
 WORKSPACE   | ✓ Workspace creation complete. Pending start...
 WORKSPACE   | ✓ Starting workspace
 lambda-perf | Starting project lambda-perf
 lambda-perf | Found devcontainer.metadata label
 lambda-perf | Executed entrypoint for feature ghcr.io/devcontainers/features/docker-in-docker:2.11.0
 lambda-perf | Executed entrypoint for feature ghcr.io/devcontainers/features/nix:1.2.0
 lambda-perf | Downloading Daytona from http://host.docker.internal:3986/binary/v0.42.0/daytona-linux-arm64
 lambda-perf | Daytona downloaded successfully
 lambda-perf | Installing server to /usr/local/bin
 lambda-perf | Starting Daytona Agent
 lambda-perf | Failed to obtain reader, write /home/daytona/.daytona-agent.log: file already closed
FATA[0068] failed to create workspace: Starting Daytona Agent
Failed to obtain reader, write /home/daytona/.daytona-agent.log: file already closed

To Reproduce
Steps to reproduce the behavior:

daytona create
select "Enter a custom repository URL"
Enter: https://github.com/maxday/lambda-perf
Choosing a workspace name: "lambda-perf"
Selecting "local (default) │ docker-provider"

Expected behavior
Workspace created.
Screenshots

Desktop (please complete the following information):

OS: MaxOS Sonoma 14.7 (23H124)
Daytona Version: v0.42.0

Hi @soundstep,
Thanks for raising the issue.
Can you please do the following:

Run docker ps
Locate the container that has the "daytonaio/workspace-project" image
Run docker exec <CONTAINER-ID> daytona agent

And let me know the output.

Hi @Tpuljak, thanks fort the quick replay.
I found the issue... my company is using zscaler, so there is something blocked.
Is Daytona reaching something that might be blocked? Any domain used?
If we are to use Daytona, we will probably need to allow the domains you are using.

Ah, that might be the issue.
If you run daytona server config you'll notice the public domain of your Daytona server. The server registers on our reverse proxy so it's available from the workspaces Daytona creates.
The revrse proxy domain you should whitelist is either
try-us.daytona.app or try-eu.daytona.app depending on what was closer when you started Daytona for the first time.

That's great, that's what I need, I'll test all that. Feel free to close the ticket meanwhile, thanks for your help.

That's great, that's what I need, I'll test all that. Feel free to close the ticket meanwhile, thanks for your help.

No problem. Closing the issue. If this doesn't resolve it, let me know and I can reopen and help out further.


Update checkout for swift-syntax to release tag.

tensorflow-0.9 cherry-pick of https://github.com/apple/swift/pull/31494.
Fixes macOS toolchain builds.

Merging to unblock progress.


Failed to execute 'matches' on 'Element': '@media only screen and (max-width : 480px)

Theese are some errors that I am getting after trying to use Tailwind CSS in my React project. I am using the tailwindcss-container-query plugin https://github.com/dgknca/tailwindcss-container-query.

Did you manage to resolve this @Enebz ?

Yes @th0th!
You have to use this as a local package though: https://github.com/lilles/container-query-polyfill/tree/skip-at-rules-20220402
It has been sent as a PR here: https://github.com/GoogleChromeLabs/container-query-polyfill/pull/33


Uncaught (in promise) CodeError: Too many outbound protocol streams for protocol

This is a bug report
Problem
After running a while in the browser I see plenty of similar errors (see the attached screenshot) where the protocol is different every few seconds. It is unclear if the error is because js-waku cannot reconnect and this is just a side effect of it or this indicates the real problem, but when I see this no messages can be sent. Basically nothing works until I reload the page.
Notes

js-waku version: 0.0.19
Environment (browser software and version, system software and version): Firefox and Chromium on Linux
Nodes connected to too (e.g. Status test fleet): private go-waku cluster, latest version

Was able to observe myself. Looking into it.

Reason why it happens:

too many send requests are made e.g lightPush.send

My guess it that in local development environment it happens due to page being reloaded due to changes and no conditions applied on .send operation.
<EMAIL_ADDRESS>or<EMAIL_ADDRESS>are safe agaist this error

@weboko do note the error also appeared in filter. Are we doing preemptive stream opening for it too?


[feature request] design of qos-plugin-manager

What would you like to be added:
Add a new module for koordlet, which provides a general framework to manage QoS strategy.
Why is this needed:

/assign stormgbs

/assign zwzhang0107

/area koordlet


Not an issue

This is not an issue. This me saying thank you as I have been looking for something like this long time ago.

Haha! No problem!

More cool stuff for my CMS
https://github.com/tomwalder/php-gds/issues/29


Get proper testing working

There's some testing of various parts, although arguably not as much as there should be


Created documentation for arrow functions

Showed with example about how arrow functions can reduce the lines of code we have to write.

I want to keep contributing to it.

@pkkrsingh877 Thank you for contributing :), keep contributing.


Why TestOptions incompatible when gradle api  changed  from 4.0.1 to 7.01

Expected Behavior
For Gradle api 4.0.1

TestOptions  import com.android.build.gradle.internal.dsl
But for gradle api 7.0.1
TestOptions  import com.android.build.api.dsl.TestOptions' which is marked unstable with @Incubating
functionality of TestOptions.UnitTestOptions should be same
Current Behavior
because of change of package from
com.android.build.gradle.internal.dsl
to
com.android.build.api.dsl.TestOptions
it's not possible to implement below code
@Suppress("UNCHECKED_CAST")
private fun TestOptions.UnitTestOptions.all(run: Test.() -> Unit) = all(closureOf(run) as Closure<Test>)

Context
Ultimately I want to implement below chunks of code
// TODO: Not compatible when updated the AGP version from 4.0.1 to 7.0.1
        testOptions {
           unitTests.all {
                jacoco {
                    isIncludeNoLocationClasses = true
                }
            }
        }

Here I would like to specify option for how the Android plugin should run local and instrumented tests.
Steps to Reproduce

Your Environment

Gradle 7.0.1
Build time:   2021-05-10 16:08:58 UTC
Revision:     67e618faef187783dadd03a34fdab9dc71b85b19
Kotlin:       1.4.31
Groovy:       3.0.7
Ant:          Apache Ant(TM) version 1.10.9 compiled on September 27 2020
JVM:          11.0.12 (Oracle Corporation 11.0.12+8-LTS-237)
OS:           Mac OS X 11.5 x86_64
Build scan URL:
https://scans.gradle.com/s/rzc5yxrxewqac/activate

Thank you for your interest in Gradle!
This is an issue with the Android Gradle Plugin which is developed by Google and cannot be addressed in the core of the Gradle Build Tool.
Please open such Android-related issues on the Android Issue Tracker at https://source.android.com/source/report-bugs


Additional checks for input existence in transactions

Issue Number
It turns out there are no checks for that.
A bit related to #2327.
Overview

2605a9f1071aad41bca21d8ef98210c117f7cfb9
Additional checks for inputs in incoming and outgoing transactions in integration tests

1247f9a75598a3b3f44d6b7631645868fac272a4
Additional checks for inputs in join/quit pool transactions

bd2916b0423811b85328edb60ae427f2e4b4dee4
remove redundant cases & fix fixture wallet sharing common funding UTxOs
It's a bit fucked up. Since the scenario is using fixtureWallet, the
UtxO from the wallet comes from one of the fixture transaction made
when initializing the cluster. There are many pre-funded fixture
wallets with 10 UTxO, but in order not to spend 10 days funding them
all, the cluster generate pretty large transaction with ~100
outputs. So a single fixture transaction funds about 10 fixture
wallets.
Now it means that, a particular fixture wallet will know the value
of all inputs of its funding fixture transaction and therefore, when
picking two fixtureWallet one after the other, it may likely happen
that both wallets are able to resolve inputs of any UTxO coming from
their original fixture transaction.
I fixed it by simply using fixtureWalletWith [...] which generates
completly new and uncorrelated UTxOs.

cdf556ac20da1ca7afe12c831a0876633f704317
Add input check for multi-address pending tx

Comments

bors merge

bors merge

bors r+

bors r+


Load correct sysconfig for RAK

@marvinmarnold the RAK works already with the standard RasPi config doesn't it?

@shawaj Possibly yeah. We just want to create 'template tasks' for enabling new hardware so we have good step-by-step tasks.

Checked the required steps and seen that it is compatible with our default sys.config. Right now we're dealing with LoRa stage issues, but this is not related to this topic. We can close this issue as Done.

Yeah feel free to close this out.


Remove mention about opensourcing

Remove point about opensourcing from README, as it looks unnecessary.

Codecov Report
Attention: 517 lines in your changes are missing coverage. Please review.

Comparison is base (7477bfd) 87.02% compared to head (81d1c08) 87.24%.
Report is 192 commits behind head on master.

Files
Patch %
Lines

...tion/coordinator/plugins/clickhouse/test_plugin.py
17.04%
73 Missing :warning:

...gration/coordinator/plugins/clickhouse/conftest.py
56.09%
54 Missing :warning:

astacus/coordinator/plugins/base.py
79.11%
47 Missing :warning:

...cus/coordinator/plugins/cassandra/restore_steps.py
67.59%
35 Missing :warning:

astacus/node/api.py
66.34%
35 Missing :warning:

astacus/node/download.py
54.00%
23 Missing :warning:

...dinator/plugins/clickhouse/async_object_storage.py
75.29%
21 Missing :warning:

astacus/node/memory_snapshot.py
90.55%
17 Missing :warning:

astacus/client.py
38.46%
16 Missing :warning:

astacus/node/cassandra.py
81.60%
16 Missing :warning:

... and 39 more

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #159      +/-   ##
==========================================
+ Coverage   87.02%   87.24%   +0.22%
==========================================
  Files         122      141      +19
  Lines        7648     9984    +2336
==========================================
+ Hits         6656     8711    +2055
- Misses        992     1273     +281

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


archive/zip: does not allow local filename encoding

I making zip file with local filename encoding for compatibility on japanese Windows.
Below codes was working fine with go 1.8.4 windows/amd64.
package main

import (
  "archive/zip"
  "fmt"
  "os"

  "golang.org/x/text/encoding/japanese"
  "golang.org/x/text/transform"
)

func main() {
  f, err := os.Create("test.zip")
  if err != nil {
    panic(err)
  }

  myZip := zip.NewWriter(f)
  defer myZip.Close()

  jpnName, _, err := transform.String(japanese.ShiftJIS.NewEncoder(), "日本語.txt")
  if err != nil {
    panic(err)
  }

  header := zip.FileHeader{
    Name:   jpnName,
    Method: zip.Deflate,
  }

  writer, err := myZip.CreateHeader(&header)
  if err != nil {
    panic(err)
  }

  fmt.Fprintln(writer, "hello")
}

With go 1.9.1 windows/amd64, CreateHeader() overwrites utf8 flag to 1. So there is no way to create zip with local encoding.
Even today, Windows 7 can't extract utf-8 encoded zip by default.
User needs to manually download and install HOTFIX to extract correctly.
Windows 8 and later can extract utf-8 encoded zip without problems.
But Windows zip tool doesn't make any utf-8 encoded zip file. it always uses local encoding.
If you try to compress files that includes unicode only characters like emoji in filename, error dialog popups and it says like "you can't use this filename, please change it."
Also 7zip for Windows uses local encoding by default. you can make utf-8 encoded zip with -mcu=on option.
I think current implementation is intended to set utf8 flag only if filename is valid utf-8 string. But hasValidUTF8() function returns true for non ascii string even if its not valid utf-8.
https://github.com/golang/go/blob/2da8a16cbcd5fc6fc04e1fd8a157cfa21f6d18bc/src/archive/zip/writer.go#L218-L230
see also #10741

CC @mattn

Closing as duplicate of #10741. I have finished all planned improvements to archive/tar. I'll look to improving and cleaning up archive/zip. Probably won't be able to get much done in the remainder of this cycle, though.


Rancher UI environment variables interpolation order

Rancher versions:
rancher/rancher:v2.0.6
Environment Template: Kubernetes
Steps to Reproduce:
Rancher ui order (and reorder) environment variables as simple (value=x) first then special (that use valueFrom) at the end.
If you define a simple variable that use interpolation of a special variable like:
- name: MEMCACHED_HOST
  valueFrom:
    fieldRef:
      apiVersion: v1
      fieldPath: status.hostIP
- name: MEMCACHED_URL
  value: $(MEMCACHED_HOST):5000

the order (that is necessary for the interpolation to work) is preserved if you Edit YAML, but when you Upgrade via the UI, the YAML will become:
- name: MEMCACHED_URL
  value: $(MEMCACHED_HOST):5000
- name: MEMCACHED_HOST
  valueFrom:
    fieldRef:
      apiVersion: v1
      fieldPath: status.hostIP

Results:
The interpolation fail and the container will see: MEMCACHED_URL="$(MEMCACHED_HOST):5000" without interpolation
gz#9725
gz#10539
gz#16638
gz#16888

@StrongMonkey is this a UI issue or a backend catalog issue?

@cjellick most likely a type mapper issue in workload api. we don't sort the map base on name.

Looks like this was an issue in kubectl as well, but was fixed, see here: https://github.com/kubernetes/kubernetes/issues/40373
According to that issue, constant ordering of env variables is part of the kubernetes API spec.

I could also reproduce it, still an issue in 2.2.1

It's still an issue on v2.2.3.
After saving environment variables from the UI, the order changes.
Then k8s cannot use $(SOME_ENV_VAR) (because the it's decelerated above)

Still an issue in v2.2.4

Will this ever be fixed?

Still in issue on 2.3.2

I think it fell off our radar. Thanks for the bump. I'll ping the necessary ppl to try to get this prioritized.

@vincent99 @westlywright do you know of some technical reason why we have to reorder these?

@cjellick Environment is a map in the API.  So there isn't really an order to reorder, but JS preserves key order so I would guess it's probably Go breaking it-as-a-service.

@vincent99 @westlywright do you know of some technical reason why we have to reorder these?

@cjellick sorry to bump into the conversation, but the technical reason in my opinion is that if not correctly ordered, this can break environment values assignment, giving them incorrect values. This may make containers that are working in other environments not to work in Rancher without customization.
A simple example would be to compose a URI var from a list of environment variables stored into a config map or a secret. In the default ordering, as it is now, config maps and secrets are posted AFTER the container environment variables in the .yaml file, so by the time the environment vars are being defined in the container, variables from config maps and secrets do not exist yet, so variables dependency has to be taken into consideration when writing the .yaml file, as kubernetes  doesn't do that automatically.
Look at the attached nosqlclient-clone.yaml file for this exact situation: I simply cloned a working workload (where I had customized the variables order so that it worked) and it doesn't works anymore because of the ordering variables were defined does not allow it to work.

if it's not possible to preserve the order of the environments, is it possible atleast to sort the environment variables that has fieldPath  to be first in the env: list?
such as: fieldPath: metadata.namespace,fieldPath: metadata.name, fieldPath: status.podIP, fieldPath: status.hostIP and etc...
in that case it will fix the issue above:
- name: MEMCACHED_HOST
  valueFrom:
    fieldRef:
      apiVersion: v1
      fieldPath: status.hostIP
- name: MEMCACHED_URL
  value: $(MEMCACHED_HOST):5000

Craig was asking if there's a reason that we are reordering them, and the answer is no, but the data structure it's exposed as is a map which has no actual "order".  To fix it it needs to be expressed in our API as an array (and therefore ordered) of objects instead of a map.

@vincent99, thanks a lot for the clarification and sorry for the misinterpretation of Craig's question - It is hard for us outside the project and without knowledge of the actual code to clearly understand those. In this case I could have understood but I missed it completely...
Still trying to contribute and in order to be 100% fail proof, besides keeping the order you'll need to check for dependencies between all env vars / secrets / config maps in order to discover the proper declaration order.
Again, thanks for the hard work and for the amazing product - From now on I'll do my best to help and stay away from the tech talks so I don't disturb you guys anymore!

Once it's an array, it would be up to the user to express them in an order that resolves the way they want (as it is in the normal k8s API).  There's no reason for us to get involved trying to detect and dependencies and reorder things.
I do not think that is actually even possible in the general case, because I think you can technically redefine a variable midway through, like (pseudo-syntax)
- A=foo
- B=$A
- A=bar
- C=$A

should eventually result in A=bar, B=foo, C=bar being given to the pod.

Got it, and you're of course right. The only thing I would like to point out is about secrets and config maps. As far as I'm aware of, those never have any inputs coming from environment vars. If that assumption is correct, both should be declared always PRIOR to environment vars also as ordered lists as you suggest, and if I may, secrets should always be declared FIRST as they can be used by both config maps and env vars but have no dependencies at all.

I excactly hit what @ecarlotti said.... It would be cool to have first secrets, configs then envs as a first step (feature). Then maybe a custom ordering where user could choose.

Is there a workaround for this issue?

@fbrbovic you can edit the yaml directly and order the env entries manually but if you then edit again with the ui, the order will be reset (and you'll need to edit the yaml again)

Please fix this. We ended up breaking our LinkerD deployment by pressing the re-deploy button.

Still a LARGE issue with RabbitMQ HA in 2.3.6 ( cannot upgrade to 2.4.x-2.4.4 due to memory issues)
Redeploy will kill this.
containers:
    - env:
        - name: HOSTNAME
          valueFrom:
            fieldRef:
             apiVersion: v1
             fieldPath: metadata.name
         - name: RABBITMQ_NODENAME
            value: rabbit@$(HOSTNAME).rabbitmq-internal.fluffle.svc.cluster.local

This issue has been moving from milestone to milestone. I hope it'll land on 2.4.12.

The original proposed fix was not the proper solution. The most recent proposal is to change the Norman API to handle the correct type for environment variables, but this would end up breaking the API for any users using it for workloads, so trying to find the right release vehicle to make this breaking API change.

The original proposed fix was not the proper solution. The most recent proposal is to change the Norman API to handle the correct type for environment variables, but this would end up breaking the API for any users using it for workloads, so trying to find the right release vehicle to make this breaking API change.

haven't tried it myself, but got a report that the environment variables are also reordered when a "Pause Orchestration" is selected for a deployment and is later unpaused.

@dnoland1  Any update to the workload in the Ui is going to send a complete copy of the definition and cause this, it doesn't really matter what action you're talking.
The problem here is fixing this is a breaking API change (changing a field's type), which we can't just make in a patch release.  And any mitigation for that to preserve backwards compatibility means any client using the original style will re-break the order without knowing it.
In 2.6 the "Cluster Explorer" is going to be the default UI, and it uses an API that doesn't have this problem in the first place (including the version shipping now). But the old behavior still has to be dropped from the /v3/workloads API to prevent users of it from breaking things.

@dnoland1 Any update to the workload in the Ui is going to send a complete copy of the definition and cause this, it doesn't really matter what action you're talking.
The problem here is fixing this is a breaking API change (changing a field's type), which we can't just make in a patch release. And any mitigation for that to preserve backwards compatibility means any client using the original style will re-break the order without knowing it.
In 2.6 the "Cluster Explorer" is going to be the default UI, and it uses an API that doesn't have this problem in the first place (including the existing 2.5.x versions). But the old behavior still has to be dropped from the /v3/.../workloads API to prevent users of it from breaking things.

@vincent99 does that mean it should already work in the explorer view? I agree on actions like "redeploy", but using "Edit Config" destroys my order all the time when saving ...

I also have the same issue.
I agree with @dorsany,
if rancher always put all value "valueFrom" before environment variable in the yaml, it should solve the problem easily without need to upgrade the web interface.

The API fields environment and environmentFrom has been deprecated in favor of Kubernetes' native fields env and envFrom to fix this issue. What this means is that anything within Rancher that uses the mappers (maps our custom type to k8s and vice versa) for workload environment variables will be affected, and therefore validated so that the k8s native fields are used instead.
What's affected:

UI (text fields in the UI) - The Ember UI needs to be updated to use the k8s types (issue for this here). Once that's done, the UI shouldn't really ever hit the validator because the user can't make the change to use the deprecated fields in the UI.
API view or requests - Using the old environment and environmentFrom fields will go through the validation and result in failure. The expectation is to use the k8s native fields env and envFrom moving forward.

What's unaffected:

UI (Edit as YAML) - This doesn't go through the mappers, or our validation. The interaction is with k8s directly and k8s will validate that the k8s native fields env and envFrom are being used. So the behavior should remain unchanged.
kubectl - Same as above

Upgrading from Rancher v2.5 to v2.6 with existing workloads - the expectation in this case is that the workload's environment variables will not be mapped into our custom types anymore and will instead come straight from k8s with its type unchanged. Here an example:
Workload's env vars in Rancher v2.5 before upgrading

Same workload's env vars in Rancher v2.6 after upgrading

cc @Sowmya (This info might be useful for testing this issue).

There's forthcoming discussion about changing how the UI handles this. @nwmac will setup a meeting shortly to go over options so UI won't work on this until then.

Verified on rancher server master-head c1151f6
Fresh install:

Create an rke2 cluster from dashboard with 3 worker, 1 etcd, 1cp
Create a config map from the cluster with a key=key and value=bar
Deploy a workload in the cluster
In the workload deployment → general → Environment variables → select the config map that was created in the above step from the API .
Add the key pair created above in the containers:
{"envFrom":[{"configMapRef":{"name":"au-cm"}}],"image":"ranchertest/mytestcontainer","name":"au-correct-config"}
Environment variables are created with env
Edit as yaml of the workload and change the env to environment and envFrom to environmentFrom
The workload did not result in any error. If we redeploy the workload, the environment values will be disregarded and no environment variables are added in the pod.
Deploy a workload with environment and environmentFrom variables as follows for config maps:
{"environmentFrom":[{"configMapRef":{"name":"au-cm"}}],"image":"ranchertest/mytestcontainer","name":"au-incorrect-config"}
In the yaml file add the variables environment and environmentFrom with the env data present and click on save
Verified the workload creation failed with an error: "message": "field `environmentFrom` is deprecated, please use Kubernetes native fields `env` and `valueFrom` for the container's environment variables"

Verified the above scenarios for secrets and key-pair. works as expected
Fresh install interpolation order:

deploy a workload, from default project with rancher image=ranchertest/mytestcontainer from API
once the workload is deployed, from the API added the variables as follows:

- env:
  - name: MEMCACHED_HOST
    valueFrom:
      fieldRef:
        apiVersion: v1
        fieldPath: status.hostIP
  - name: MEMCACHED_URL
    value: $(MEMCACHED_HOST):5000

Redeployed the workload  → multiple times
Verify the order is not changed and is reflected as presented above.
Edit as yaml and change the env to environment and envFrom to environmentFrom.
Verify that the saving the yaml file will not result in an error as mentioned in the above configmap scenario and the environment variables are disregarded
Deployed anotehr workload from the API and added the same values as above by replacing env to environment and envFrom to environmentFrom.
Verified the deployment errored out:  "message": "field `environmentFrom` is deprecated, please use Kubernetes native fields `env` and `valueFrom` for the container's environment variables"

Upgrade Scenario:
Waiting on the issue https://github.com/rancher/rancher/issues/33221 to be resolved.

Verified upgrade test case on v2.5.8 and pst-upgrade: master-head ad099ee

Create an rke1 cluster from emberUI with 3 worker, 1 etcd, 1cp on rancher server v2.5.8
Create a config map c1 and secret s1 from the cluster with a key=key and value=bar -wk1
Deploy a workload in the cluster
In the workload deployment → general → Environment variables → select the config map that was created in the above step.
Verified from the API requests for the fields environment variables are environment and environmentFrom
In workload - wk2, add the secret s1 created from step2
Add interpolation order  to the workload - wk3 with the config as follows and redeployed the workload and verified the order changed:

- env:
  - name: MEMCACHED_HOST
    valueFrom:
      fieldRef:
        apiVersion: v1
        fieldPath: status.hostIP
  - name: MEMCACHED_URL
    value: $(MEMCACHED_HOST):5000

Add a key-pair in the environment variables in a workload and create - wk4
Import yaml in a workload with environment variables: environment and environmentFrom - wk5
Create 3 secrets and 3 config maps in the cluster before upgrade
Upgrade rancher server to latest master-head and verify by redeploying all the workloads multiple times.
Verified no error is seen and all the workloads have the env variables applied with the prefix env
Verified the pods of the workloads and see the env variables.

kubectl exec wk1-85bcd875c4-jfg98 -- printenv

key=secret1

Verified the interpolation order in the workload by redeploying multiple times and see the order is reflected as present before the upgrade.
Changed the interpolation order of the env variables and redeployed it multiple times.
Verified the order is not changed

Thank you for your efforts. What is important to know, is if you REDEPLOYED this with cluster manager or cluster explorer???
With cluster explorer, this has worked since Rancher 2.5.7.
For me, with cluster manager in Rancher 2.5.8 it does NOT work. I am fully aware that cluster manager is legacy and will be discarded in the future. So, in order to redeploy this from the GUI, I always use cluster explorer now.
If you only use kubectl, this is never a problem however.

Hi @jeroenhartgers I redeployed it via postman using v3 API as the cluster manager button is hidden and the workload creation will not be fixed for ember UI  from 2.6


ImportError: cannot import name 'cross_validation' from 'sklearn'

hello,
i ran across your 2017 paper about PyMut recently. i decided to give the code a try today (06jun2023). however, i ran into an import statement issue from the getgo and could not go further.
i did a bit of searching and learned that cross_validation in sklearn was deprecated a while ago. do you guys have a newer version of the code that i can use. also, are you aware of other github packages that will do things similar to PyMut?
best regards,
fred

i was able to run PyMut in a virtual environment using older packages. therefore, i will close this issue. thanks very much.


Footnotes in tables rendered out of order

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
When footnote references appears inside tables, the order and numbering does not match what's intended.
I tried the code below in https://mdxjs.com/playground/, as suggested in a comment of #4647, but over there the rendered output is correct.
Steps to reproduce
I have the following code in one of my pages:

Format        | Main Media Type                     | Parser
--------------|-------------------------------------|------------------
HTML forms    | `application/x-www-form-urlencoded` | [FormParser]
MIME messages | `message/*`[^1]                     | [MessageParser]
Text          | `multipart/*`[^2]                   | [MultiPartParser]

[^1]: This parser is primary for `message/rfc822` (E-mail) messages, but can actually handle most other `message`
      subtypes too (not `message/http`, though).
[^2]: This parser handles MIME multi-part messages as well as `multipart/form-data`, used by web forms.

[FormParser]:      ../api/classes/divine_uri.FormParser.md
[MessageParser]:   ../api/classes/divine_uri.MessageParser.md
[MultiPartParser]: ../api/classes/divine_uri.MultiPartParser.md

Expected behavior

Format
Main Media Type
Parser

HTML forms
application/x-www-form-urlencoded
FormParser

MIME messages
message/*[1]
MessageParser

Text
multipart/*[2]
MultiPartParser

This parser is primary for message/rfc822 (E-mail) messages, but can actually handle most other message subtypes too (not message/http, though).
This parser handles MIME multi-part messages as well as multipart/form-data, used by web forms.

Actual behavior

Format
Main Media Type
Parser

HTML forms
application/x-www-form-urlencoded
FormParser

MIME messages
message/*[1]
MessageParser

Text
multipart/*[2]
MultiPartParser

This parser handles MIME multi-part messages as well as multipart/form-data, used by web forms.
This parser is primary for message/rfc822 (E-mail) messages, but can actually handle most other message subtypes too (not message/http, though).

Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Reproducible demo
No response
Self-service

[ ] I'd be willing to fix this bug myself.

Hi! I've already reported it here: https://github.com/remarkjs/remark-gfm/issues/35
Unfortunately, the fix will only be applied in the latest version of Remark/MDX, which is not compatible with Docusuarus v2 (see #4029 and #3668). In the meantime, you would have to manually reorder it yourself, or find a way that doesn't put the footnotes in the table.

Not totally happy with this answer, I forked the last cjs version of the module and am now using "mdast-util-to-hast": "Divine-Software/mdast-util-to-hast#0e709bd254f07bad424d74a1d98e727d1d7926e4" as an override. Docusuarus v3 must be years away? Can't wait for that.
Anyway, problem solved. Thanks for the direction to where the bug was.

Docusaurus v3 is planned immediately after v2. See #6113 and the 3.0 milestone for things we plan to do. In the future, because we will be sticking to semver conventions, major version bumps are going to happen much more frequently.

Any update on this? Still seems to be an issue in v2.4.1, despite https://github.com/facebook/docusaurus/issues/4029 being complete.

@amacneil #4029 is for Docusaurus 3. You would need to use the canary version to try it.

I see, thanks. Will wait for official release.
For now I worked around it by using 1 and creating manual footnotes.


perl-BSD-Resource: init at 1.2911

Motivation for this change
Add BSD::Resource module from CPAN.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build perlPackages.BSDResource

Success on aarch64-linux (full log)
Partial log (click to expand)
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/hgjhamq94iwnikfg7389mrw7s1ps8fyl-perl-BSD-Resource-1.2911/lib
patching script interpreter paths in /nix/store/hgjhamq94iwnikfg7389mrw7s1ps8fyl-perl-BSD-Resource-1.2911
checking for references to /build in /nix/store/hgjhamq94iwnikfg7389mrw7s1ps8fyl-perl-BSD-Resource-1.2911...
shrinking RPATHs of ELF executables and libraries in /nix/store/5mzm2d3l3gj58q1fracivzrjg445vams-perl-BSD-Resource-1.2911-devdoc
gzipping man pages under /nix/store/5mzm2d3l3gj58q1fracivzrjg445vams-perl-BSD-Resource-1.2911-devdoc/share/man/
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
patching script interpreter paths in /nix/store/5mzm2d3l3gj58q1fracivzrjg445vams-perl-BSD-Resource-1.2911-devdoc
checking for references to /build in /nix/store/5mzm2d3l3gj58q1fracivzrjg445vams-perl-BSD-Resource-1.2911-devdoc...
/nix/store/hgjhamq94iwnikfg7389mrw7s1ps8fyl-perl-BSD-Resource-1.2911

Success on x86_64-linux (full log)
Partial log (click to expand)
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/nz5r0x66hzrb97gx85ifkw2y7widcz1i-perl-BSD-Resource-1.2911/lib
patching script interpreter paths in /nix/store/nz5r0x66hzrb97gx85ifkw2y7widcz1i-perl-BSD-Resource-1.2911
checking for references to /build in /nix/store/nz5r0x66hzrb97gx85ifkw2y7widcz1i-perl-BSD-Resource-1.2911...
shrinking RPATHs of ELF executables and libraries in /nix/store/yz6fc6fz5lpqhqcj0w4h6akfgmgix8fh-perl-BSD-Resource-1.2911-devdoc
gzipping man pages under /nix/store/yz6fc6fz5lpqhqcj0w4h6akfgmgix8fh-perl-BSD-Resource-1.2911-devdoc/share/man/
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
patching script interpreter paths in /nix/store/yz6fc6fz5lpqhqcj0w4h6akfgmgix8fh-perl-BSD-Resource-1.2911-devdoc
checking for references to /build in /nix/store/yz6fc6fz5lpqhqcj0w4h6akfgmgix8fh-perl-BSD-Resource-1.2911-devdoc...
/nix/store/nz5r0x66hzrb97gx85ifkw2y7widcz1i-perl-BSD-Resource-1.2911

Success on x86_64-darwin (full log)
Partial log (click to expand)
post-installation fixup
Moving /nix/store/kj5ip1hczl02alc5n20an9wnpmzr5zvg-perl-BSD-Resource-1.2911/share/man/man3 to /nix/store/6q91vp2j09q07wibqsl5rlyyml1yjg0y-perl-BSD-Resource-1.2911-devdoc/share/man/man3
Removing empty /nix/store/kj5ip1hczl02alc5n20an9wnpmzr5zvg-perl-BSD-Resource-1.2911/share/man/ and (possibly) its parents
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/kj5ip1hczl02alc5n20an9wnpmzr5zvg-perl-BSD-Resource-1.2911/lib
patching script interpreter paths in /nix/store/kj5ip1hczl02alc5n20an9wnpmzr5zvg-perl-BSD-Resource-1.2911
gzipping man pages under /nix/store/6q91vp2j09q07wibqsl5rlyyml1yjg0y-perl-BSD-Resource-1.2911-devdoc/share/man/
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/6q91vp2j09q07wibqsl5rlyyml1yjg0y-perl-BSD-Resource-1.2911-devdoc
/nix/store/kj5ip1hczl02alc5n20an9wnpmzr5zvg-perl-BSD-Resource-1.2911

Thanks!


Register glass on TestPyPI

TestPyPI is a standalone server which allows one to double-check the package works as expected before pushing to PyPI. However, you need to specifically sign up to it (with a different API key) to benefit from it. Having PyPI alone doesn't guarantee you the appropriate TestPyPI.

Registered on TestPyPI now.

Registered on TestPyPI now.

Cheers! Will incorporate in a workflow soon


clang-tidy: Apply fixes "performance-for-range-copy"

Problem
Unnecessary copies in range based loops.

Summary of Changes
Add const&.

@saurabhst @BroderickCarlin @jelderton @hawk248 ?


Add x-ms-api-version for resource

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

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[x] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[x] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
[ ] Ensure to copy the existing version into new directory structure for first commit (including refactoring) and then push new changes including version updates in separate commits. This is required to review the changes efficiently.
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Java is good. "x-ms-api-version" is already in newer versions.

@allenjzhang, @weidongxu-microsoft, @qiaozha, @ArcturusZhang, please help review to insure this change doesn't affect your SDK.

No objections from Go SDK. Track 1 Go SDK generator does not know this extension therefore it will just ignore this. I am not sure how Go SDK track 2 generator will handle this extension, but it is in preview hence open to any kind of changes.
Is there any documentation explaining what does this extension do? I did not find it here: http://azure.github.io/autorest/extensions/

@weidongxu-microsoft @zhoxing-ms Is there any documentation explaining what does this extension do? I did not find it here: http://azure.github.io/autorest/extensions/

I see the general purpose of this extension from the PR #8803

modelerfour need the x-ms-api-version extention to notify it that this api-version does not need special handling (which happens for most api-version paramter)

@lmazuel Could you please help to explain in detail what dose x-ms-api-version do?

@zhoxing-ms
There are indicators to let modelerfour know that these api-version need to be provided by user (i.e., not from swagger e.g. "version": "2016-02-01").
If you check the API path, you can see it calls another RP /{resourceProviderNamespace}/{parentResourcePath}/{resourceType}/{resourceName}, not the current Microsoft.Resources RP. Hence a different api-version is required from user.

@allenjzhang, @qiaozha, @ArcturusZhang
Could you please help to review this PR? If this change has no effect on your SDK, please help to approve it~

@allenjzhang , can you please review this if there is any impact on dotnet SDK? Thanks.

@allenjzhang , can you please review this if there is any impact on dotnet SDK? Thanks.

Confirmed with @jsntcy , dotnet SDK failures are not caused by this PR changes.


[PE-D][Tester C] Links in developer guide points to AB3

There are multiple links in the developer guide like the ones that I underlined that points to AB3 instead of Edututu.

Labels: type.DocumentationBug severity.High
original: ZweZeya/ped#19

Resolved


ApplicationDbRepository.ApplySpecification => only use mapster when no selector is defined

this to still support regular specifications with a selector defined.

@fretje
Can you provide more details about this change, when is it useful?
I would like to understand this but I do not know what is a selector. Is it maybe related to the entity framework select statement?

I needed it for a specific query to retrieve the some aggregates (counts and sums) for a specific table (actually sub-table in this case):
public class UploadDataRunCountsSpec : Specification<CommandRun, UploadDataRunCounts>, ISingleResultSpecification
{
    public UploadDataRunCountsSpec(int commandRunId) =>
        Query
            .Select(r => new UploadDataRunCounts
            {
                TotalTableCount = r.UploadDataRunTables.Count(),
                InProgressTableCount = r.UploadDataRunTables.Count(
                    t => t.TableStatus != UploadDataTableStatus.Finished
                      && t.TableStatus != UploadDataTableStatus.Queueing
                      && (t.ErrorMessage == null || t.ErrorMessage.Length == 0)),
                FinishedTableCount = r.UploadDataRunTables.Count(t => t.TableStatus == UploadDataTableStatus.Finished),
                ErrorTableCount = r.UploadDataRunTables.Count(t => t.ErrorMessage != null && t.ErrorMessage.Length > 0),
                TotalRecordsRead = r.UploadDataRunTables.Sum(t => t.RecordsRead),
                TotalRecordsAffected = r.UploadDataRunTables.Sum(t => t.RecordsAffected)
            })
            .Include(r => r.UploadDataRunTables)
            .Where(r => r.Id == commandRunId);
}

So a selector is when you add a "select" clause in your specification. This is normally a requirement when using a specification with a T and a TResult. But with our override of the ApplySpecification in the repository, this gets handled automatically by mapster (so the object from the database gets mapped by the dto immediately from the database). But there was no option anymore to make your own specification with a T and a TResult that doesn't use mapster behind the scenes. Like I needed for the spec above. This is what this PR is bringing back (it only does the mapster thing when there is no "select" defined in the specification).
I hope this answers your question?


Asakatsu Progress

Happy New Year!!! I am back.

Welcome back @AryaCodesAI, good to have you back. let's go hard and stay consistent.
It's good to be back! Thank you, Philips!


Create Song “2023-10-20/index”

Automatically generated by Netlify CMS

👷 Deploy Preview for symphonious-entremet-c2831a processing.

Name
Link

🔨 Latest commit
9122b7da48635b602e9b9cca863583313a30e610

🔍 Latest deploy log
https://app.netlify.com/sites/symphonious-entremet-c2831a/deploys/653359aaf1df3a0008fafbef