⚠ Spryr has degraded performance

In 925a6a9, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4725 ms

Resolved: Spryr performance has improved in ac044d4 after 7 minutes.


Lightstrip Gradient

Hello :)
I search the possibility to control the Gradient Lightstrip like in the Hue app ( choose 3 Colors in 3 separate segment ... )

Someone will have to add that to this library and consumers like Home Assistant.
Although the fundaments are there for this resource type, there is no actual implementation.
PR's welcome ;-)


--watch mode does not filter out file change events that are negated as part of a set of patterns

Which packages are impacted by your issue?
@graphql-codegen/cli
Describe the bug
This is a follow-up to #9266 (which was fixed by #9267), but it's an entirely separate bug. That fix just happened to expose the bug in our repository.
In our case, we have a NextJS app which uses the generated code from graphql-codegen, which means that on most page reloads, NextJS rebuilds pages in the .next directory. We noticed that these changes were not being filtered out of watch mode, even though they didn't match any of our patterns:
Running lifecycle hook "onWatchTriggered" scripts...
[Watcher] triggered due to a file create event: /src/js/cloud/catalog/.next/cache/webpack/server-development/7.pack
Running lifecycle hook "onWatchTriggered" scripts...
[Watcher] triggered due to a file delete event: /src/js/cloud/catalog/.next/cache/webpack/server-development/7.pack_
Running lifecycle hook "onWatchTriggered" scripts...
[Watcher] triggered due to a file create event: /src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack
Running lifecycle hook "onWatchTriggered" scripts...
[Watcher] triggered due to a file delete event: /src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack_

These file names could not possibly match any of our patterns in codegen.yml, which are all either files ending with *.graphql or *.ts:

Our `codegen.yml` from our repository
This is not reproducible, but is just to show how there are no patterns that could possibly match the files triggering the rebuilds:
overwrite: true
config:
  scalars:
    Datetime: "string"
    JSON: "{ [key: string]: any }"
    UUID: "string"
  documentMode: graphQLTag

autogeneratedFileWarning: &autogeneratedFileWarning
  add: "/* DO NOT EDIT! This file is auto-generated by graphql-code-generator - see `codegen.yml` */"

generates:
  types/index.ts:
    schema:
      - "../gql-api/schema/unified_schema.graphql"
    documents:
      - "queries/*.graphql"
      # All .graphql files in catalog...
      - "../catalog/**/*.graphql"
      # ...except those that are compiled into types/search.tsx in next section
      - "!../catalog/search/**/*.graphql"
      - "../dynamic-forms/scripts/fetch-externals.ts"
    plugins:
      - *autogeneratedFileWarning
      - "typescript"
      - "typescript-operations"
      - "typed-document-node"

  # types/search.tsx
  # Typings search API, via apollo-server-micro mounted on catalog/pages/api
  types/search.tsx:
    schema:
      # Note: /**/* will NOT include catalog/search/schema/withSearchServerConfig.js
      - "../catalog/search/schema/**/*.ts":
          # Need custom loader because we need side-effects to generate schema
          loader: ./loaders/SearchLoader.js

          # don't parse the AST of the files, since SearchLoader is handling them
          noPluck: true
    documents:
      - "../catalog/search/**/*.graphql"
    plugins:
      - *autogeneratedFileWarning
      - "typescript"
      - "typescript-operations"
      - "typed-document-node"

  # Same as above, but for saving the schema to a file
  # (it would probably better to put this in SearchLoader.js)
  types/search-schema.graphql:
    schema:
      - "../catalog/search/schema/**/*.ts":
          loader: ./loaders/SearchLoader.js
          noPluck: true
    plugins:
      - schema-ast

  # Types for the Splitgraph Console
  types/console.tsx:
    schema:
      - "../gql-api/schema/unified_schema.graphql"
    documents:
      - "../console/**/*.graphql"
    plugins:
      - *autogeneratedFileWarning
      - "typescript"
      - "typescript-operations"
      - "typed-document-node"
    config:
      avoidOptionals: true

As you can see, all patterns either end with .graphql or .ts, and yet the file change events are triggering on files that end with .pack.

I believe this bug was introduced in #9051 which added this code for filtering events:
            if (!mm.contains(path, files)) return;

From the documentation of micromatch.contains:

Returns true if the given string contains the given pattern. Similar to .isMatch but the pattern can match any part of the string.

My first guess what that the correct fix is to change .contains to .isMatch, and in our repository at least, this does help somewhat, but there are some other issues (see below):
-            if (!mm.contains(path, files)) return;
+            if (!mm.isMatch(path, files)) return;

I believe the issue comes down to negation, and how it's handled when part of a set of matchers. It's possible this is a micromatch bug, I'm not sure. Let's look at some examples.
In our case, we have a set of patterns which should be evaluated together, that is, the negation pattern should not be evaluated on its own, but rather as a boolean AND with the other patterns.
First, this is how the current code evaluates, which is obviously wrong:
// This returns true, but we would expect it to return false because of the negation
require("micromatch").contains(
  "/src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack",
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql",
    "../dynamic-forms/scripts/fetch-externals.ts",
    "!../catalog/search/**/*.graphql",
  ]
);

// > true

If we remove the negation pattern, then it is false as we expect. This means that the reason .contains is evaluating to true is because it "matches" !../catalog/search/**/*.graphql. However, we want it to evaluate to false, because the negation pattern should only negate any matches from the rest of the patterns (i.e., the rules should be evaluated as a set, not individually). Note: I tried different orders of these rules and it made no difference.
// Removing the negation pattern makes it evaluate to false, indicating the problem is the negation pattern
require("micromatch").contains(
  "/src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack",
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql",
    "../dynamic-forms/scripts/fetch-externals.ts",
  ]
);

// > true

So, can we use .isMatch instead? Well, you would think so, except this has the same issue:
// This also incorrectly evaluates to true
require("micromatch").isMatch(
  "/src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack",
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql",
    "../dynamic-forms/scripts/fetch-externals.ts",
    "!../catalog/search/**/*.graphql",
  ]
);

// > true

Why do I say "you would think so"? Well, because when calling the default export with a list of files, micromatch correctly evaluates the boolean as a set, and returns an empty list as expected!
// This returns an empty list [], because none of the items in the input list match any of the patterns
require("micromatch")(
  ["/src/js/cloud/catalog/.next/cache/webpack/server-development/index.pack"],
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql",
    "../dynamic-forms/scripts/fetch-externals.ts",
    "!../catalog/search/**/*.graphql",
  ]
);

// > []

That's the behavior we want! And to be sure, let's make sure it does match an actual matching file:
// This returns a matching item, as expected
require("micromatch")(
  ["../catalog/blah/blah/blah.graphql"],
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql",
    "../dynamic-forms/scripts/fetch-externals.ts",
    "!../catalog/search/**/*.graphql",
  ]
)

// [ '../catalog/blah/blah/blah.graphql' ]

However, there is another problem here, which is that it only works when there is a relative path provided. When providing an absolute path, and even when explicitly setting cwd, it does not work as expected:
> process.cwd()
'/src/js/cloud/graphql'

// This should return a matching item, but returns an empty list instead
require("micromatch")(
  ["/src/js/cloud/catalog/blah/blah/blah.graphql"],
  [
    "queries/*.graphql",
    "../catalog/**/*.graphql", // It should match this one
    "../dynamic-forms/scripts/fetch-externals.ts",
    "!../catalog/search/**/*.graphql",
  ],
  { cwd: "/src/js/cloud/graphql" }
);

Your Example Website or App
no minimal reproduction atm, sorry
Steps to Reproduce the Bug or Issue
Sorry, no minimal reproduction atm, but I do have example micromatch rules failing in the description above.
Expected behavior
As a user, I expect that only file change events matching my specified patterns will trigger a rebuild, and I expect that a negation pattern will negate any other patterns in its same set. However, the bug is that the negation pattern is being evaluated "by itself" which means it's matching a bunch of irrelevant files.
Screenshots or Videos
No response
Platform

OS: Linux
NodeJS: 16.13.1
graphql version: 15.8.0
@graphql-codegen/cli version(s): 3.3.1-rc-20230404030530-47bcfb095, but that's only because the bug was exposed once we were listening in our root directory; it was present in 3.2.2 but we just didn't have our .next directory within the same package as our codegen config

Codegen Config File
See above description
Additional context
I'll try to fix this in a PR, but I'm still unclear if the bug is in here or micromatch

I'm not sure if this is a bug in micromatch or we're just holding it wrong. I think I have an idea for how to workaround it though, which is to use the default export, convert the absolute path to a relative path when providing it as input, and then check if the returned list is non-empty.
I'll put that in a PR later today.

Sorry, duplicate of #9177, but at least I included a bunch of examples here and I think identified the root cause. I'll work on a fix today.

@milesrichardson I was also thinking if we should load the gitignore and put those in negated paths?

An opt-in flag seems reasonable though? But more important seems to be making visible to user why a match is happening, so maybe it would be nice if --debug output included not only the file that it matched (as it does now), but also the pattern (or set of patterns!) that caused the match.

Today you can do DEBUG=1 yarn generate  this will print all the debugLogs we put in

Yeah, I saw that (--debug also works). And it helpfully shows which file changed to trigger the event, which is how I found this bug in the first place, but it doesn't show which pattern(s) it matched (makes sense, as that's harder to decide how to render).

Just a note, another thing a fix for this will need to consider is that the negation should only apply to the "local" set of patterns that it's part of, rather than the "global" set of patterns which is what we look at now (the files array is a concatenation of all patterns in the config file).
e.g. If you have two sections of config, each with their own pattern sets, and each of those contains a negation, then each negation should only AND with the patterns in its own config section, rather than all the config sections in the file.
e.g. In our case:
generates:
  types/index.ts:
    documents:
      - "queries/*.graphql"
      - "../catalog/**/*.graphql"
      - "../dynamic-forms/scripts/fetch-externals.ts"
      - "!../catalog/search/**/*.graphql"
  types/search.tsx:
    documents:
      - "../catalog/search/**/*.graphql"

We only want "!../catalog/search/**/*.graphql" to negate any matching patterns in the generates[types/index.ts][documents] section, because if it also negated any matching patterns in generates[types/search.tsx][documents], then this would incorrectly cause types/search.tsx not to rebuild when its documents change.
This shouldn't be too difficult, but it just requires a bit more careful coding.

I started coding this and it turned into a big mess, so I tried to figure out the logic and put it into a flow chart, which you can see at the bottom of this comment. Now that I figured out the logic, I'll (re-)start coding this tonight and hopefully finish it tomorrow. Please let me know if you see any logic that I overlooked in the flow chart.
I tried to simplify it without depending too much on (apparently somewhat unreliable) micromatch magic. It's possible that we could re-use some logic from graphql-config, but I'm not familiar with it, and besides, there are enough idiosyncrasies specific to watch mode (e.g. watchPattern for each generation target's local config, and config.watch for the global config) that it seems worthwhile to implement an algorithm specifically for watch mode.
Background
Basically, both "localConf" (one for each generates target) and "globalConf" each have a set of patterns for watch, schemas, and documents. Within each set of patterns, each pattern is either "affirmative" (non-negated) or "negated."
Basic Idea
The algorithm loops over every localConf section, and follows the flow chart, which aims to answer the question: "should path trigger a rebuild for localConf? A rebuild is triggered as soon as the algorithm in this flow chart returns true for any localConf. Note that negation priority still works, and if a path is globally negated, the algorithm will return true for every localConf entry.
Negations take priority, and globalConf negations take priority over all patterns
Within each localConf, the highest priority negations are localConf.watchPattern and globalConf.watch. If any of those negations match the path, then the algorithm returns false (do not trigger a rebuild) for that localConf. And within each of localConf.documents and localConf.schemas, any negations from globalConf.documents and globalConf.schemas take priority over any affirmative matches in either of localConf.documents or globalConf.documents, or localConf.schemas or globalConf.schemas, respectively.
That is: any "negated" pattern in localConf.watchPattern takes priority over all other patterns from localConf (i.e., if there is a match in localConf.documents or localConf.schemas, but it's negated in localConf.watchPattern, then it does not trigger a rebuild). And similarly, any "negated" pattern in globalConf.watch takes priority over any match in any localConf, i.e. if any path matches a pattern in  localConf.documents or localConf.schema, but also matches a negation in globalConf.watch, or globalConf.documents or globalConf.schema respectively, then it will never trigger rebuild.
If this sounds confusing, you can understand why I made the flow chart. 😅
Terminology
The flow chart references a few functions, here are their definitions:

pluckAffirmativePatterns: Filter a list of patterns to include only non-negated patterns, i.e. patterns.filter(p => !micromatch.parse(p).negated)
pluckNegatedPatterns: Filter a list of patterns to include only negated patterns, i.e. patterns.filter(p => micromatch.parse(p).negated)
invertNegatedPatterns: Map a list of negated patterns to their inverse, i.e. strip the leading ! from each pattern (this makes it easy to "match" a negation)

Flow Chart (SVG, see below for PNG)
To read the flow chart, start from the top left.

PNG Version

Also, point of clarification:
When listing paths inside the config file, are relative paths always interpreted relative to process.cwd(), or does it depend on the config file type? If the config file is codegen.yml (or any non TS) are paths interpreted relative to the directory containing the config file rather than process.cwd()?
My understanding was that paths are always interpreted relative to process.cwd(), and so the reason ./dev-test is specified for every path in ./dev-test/codegen.ts is simply because the yarn generate:* scripts are called with a CWD of ./ (the repo root).
But the reason I ask is because dev-test/alt-codegen.yml has paths that specify  test-schema (a subdirectory of dev-test) without the ./dev-test prefix that's used in dev-test/codegen.ts, implying that relative paths in YML config are interpreted relative to the config file. But that file also hasn't been edited in two years so maybe it's outdated. Or maybe whatever code calls that file does it from within the dev-test directory.

I've also discovered a separate bug which I can fix here too, but I also need clarification on what the intent of onWatchTriggered(path) expects: a relative path or an absolute path? Currently, we are passing it an absolute path, but it's apparently accidental:
Parcel Watcher provides path as an absolute path (ctrl+f absolute). However, we then construct fullPath by calling path.join(watchDirectory, path):
const fullPath = join(watchDirectory, path);

Since #9267 watchDirectory is the "longest common prefix directory" instead of process.cwd(), but in both cases, that's an absolute path.
So this means fullPath is an invalid path that concatenates two absolute paths, e.g. /Users/oss/blah/Users/oss/blah/dev-test.
This seems like a minor bug, because we only use it for comparing to configFilePath.
However, this bug implies that the intention of the code assumed that path was a relative path. And we do pass path to lifecycleHooks(config.hooks).onWatchTriggered(eventName, path); So it's possible that there was a regression in #9051 that started passing an absolute path to onWatchTriggered hooks, instead of a relative path. I'm not sure what people expect it to be - the docs don't specify whether it's relative or absolute.

Thanks @milesrichardson for the detailed write up. Basically what is being suggested that negation will take priority always, given a global and local negation, a global negation will take precedence.
Let's say I have follow tree structure

In my global config I have !./foo/some-foo-path/part-a which means everything on that path is not going to get watched. Then in my local config for where some-foo-path is the process.cwd() I have the ./part-a , !./part-b which means basically nothing in ./some-foo-path/** will trigger the watch?

When listing paths inside the config file, are relative paths always interpreted relative to process.cwd()

I think it should be relative to the working directory.

Parcel Watcher provides path as an absolute path (ctrl+f absolute). However, we then construct fullPath by calling path.join(watchDirectory, path):

We should be working with absolute path, imo it will make it simpler to work instead of having some relatives and some absolute. So everything that gets triggered today in watch mode with parcel will have an absolute path and I think it is okay, unless you feel otherwise.

In my global config I have !./foo/some-foo-path/part-a which means everything on that path is not going to get watched. Then in my local config for where some-foo-path is the process.cwd() I have the ./part-a , !./part-b which means basically nothing in ./some-foo-path/** will trigger the watch?

Yes, basically. Although I'm a little confused because your comment implies there is support for two config files, one "global" and one "local." In my earlier comments, when I said "global" I was referring to the top level of the config file, and by "local" I meant the local stanza to each output target.
Am I missing something about features related to multiple config files?

I think I've gotten this working, albeit without any tests yet. I'll push it up soon.

Oh, one other question: Do we support defining patterns using absolute paths, or should patterns all use relative paths (which seems to be the more common case)?

Yes, basically. Although I'm a little confused because your comment implies there is support for two config files, one "global" and one "local." In my earlier comments, when I said "global" I was referring to the top level of the config file, and by "local" I meant the local stanza to each output target.

yeah you had the correct assumption there. Sorry for confusing.

Do we support defining patterns using absolute paths, or should patterns all use relative paths (which seems to be the more common case)?

In almost all cases I have seen paths being relative. I am fine just supporting relative for now and we can revisit in future but don't see a real use case why one chooses a full path.

Ok. PR incoming in < 5 minutes.

I am fine just supporting relative for now

Cool. I added some code to print a warning if absolute patterns are detected, but otherwise the failure mode is just that rebuilds might not be triggered for that path.

I opened #9275 and left an initial self-review there, to point out what's happening


Provide tutorial for debug in Webstorm/Phpstorm

gitter seems to be to much messy to get these kind of information...
repro steps:

Installed Phpstorm (improved Webstorm)
installed angular-cli beta.17
created new app using ng new
builded app using ng build

my app works, but I cannot get debugger work with original typescript files

installed jetbrains IDE extention into chrome
created debug config

new javascript debugger
www.example.com // url where my app is - I CAN'T use ng serve
since there is no way to select a file I just keep the default project dir which was created by ng new

after debugger was started, the chrome window opened and app worked but debugger didn't stop on breakpoint in app.component.ts. Chrome only showed an info bar "Jetbrains IDE support" is debugging this browser, Cancel?

any idea how to get it work? Btw similar tips for Visual Studio 2015 will come handy as well (another project)

There's a similar thread going on for VSCode where the community has been awesome and found a config that works. I can't provide you one for Phpstorm/Webstorm/VS2015 but I'll leave the issue open and flagged for help.

I'm successfully using intellij idea to debug an angular-cli app. The way it works should be similar if not same with Webstorm.
I followed the guide here [https://stackoverflow.com/questions/34254820/intellij-idea-typescript-webpack-debugging-only-works-with-javascript-breakpoint]
Basically you have to link the sources within the debug->elements tab with the correct location of your projects files. What you have to do is:
*run the project with ng serve
*start the debug configuration
*in the debug->elements tab underneath "scripts" locate the correct folder which contains your sources. In my case it's "webpack:///src". Right click on that folder and chose "Specify Local Path".

in the popup choose your project's location which corresponds to the webpack folder
now your breakpoints should show the tick and the debugger should stop at them

add last point to tutorial:

refresh browser

@jwoehrle Thank you very much!
I still have some use cases to test but so far it seems working

I am not sure this is the same as @jwoehrle solution but here is goes:

Create a new run/debug configuration for "Javascript Debug"
In URL set: `http:.//localhost:4200'
Choose the project's dir in the panel underneath and set remote URL: http://localhost:4200
Now choose the src dir and set as remote URL: webpack://

Here is also a screenshot of the configuration:

Now run in debug mode the configuration and voila, your breakpoints work as expected.

I wrote this blog post some time ago. I can adapt it to fit the Angular CLI documentation.

@prigara thanks for sharing the blog post! I think we can use it as a reference. Closing the issue for now :)


Bounty: Starjacker stuck at stage 700

In the starjacker bounty quest, stage 700 has you board the decoy ship. When I board the ship, the stage does not progress and I see an action to sit in the seat. When I sit in the seat, a new activity appears in the upper left side of the screen, as can be seen in this video clip: https://youtu.be/jsCLtpR8pJQ. It reads, "Mission Updated ACTIVITIES Visit the London Landmark On Earth". When I take off and get into orbit of the planet we just left, nothing happens; the game does not progress. I have tried many things but none of them resolve this. I am stuck and cannot play most of this quest.

Details
In the starjacker bounty quest, stage 700 has you board the decoy ship. When I board the ship, the stage does not progress and I see an action to sit in the seat. When I sit in the seat, a new activity appears in the upper left side of the screen, as can be seen in this video clip: https://youtu.be/jsCLtpR8pJQ. It reads, "Mission Updated ACTIVITIES Visit the London Landmark On Earth". When I take off and get into orbit of the planet we just left, nothing happens; the game does not progress. If you fly to the correct planet, nothing happens. The snitch never speaks or updates the mission. If I load the game onto Windows 10 and look at the stages, it shows all complete except for this stage. If I set stage to 800 in orbit of the planet we left, the snitch then does dialogue and the mission now shows the correct planet to fly to. However, when you fly there, the game still does not progress. When I pull up the console again, it shows that 700 is still incomplete. I can set stage to 810, 850, 900 etc. but none of those make the chop shop visible. I am unable to progress.
I have tried a few things. First, I have disabled all mods and that does not fix the issue. 2nd, I have gone back to my own ship instead of boarding the decoy to try and trigger the London Mission but it does not trigger it. I have gone back several saves and loaded in the frontier (I have had other bugs occur in the game where you had to be in the frontier to progress) and I still experience the same issue. I have gone back weeks in my game saves and still run into the same issue.
My belief is that the game triggers this new mission instead of triggering stage 800. It then then thinks we are no longer on the other mission even though it shows active. I have never had the london mission come up, ever, in game play and this is the only time I have seen it. I have also tried the london activity but then the snitch is stuck on earth and refuses to leave. I am not aware of a stage completion command other than completing all stages at once.
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
No
Reproduction Steps
I have not tried it on a new game. I have recreated it multiple times on my saves but haven't tried recreating it other ways.

I went through the unity to start NG+ and this resolved the bug. I think overarchingly, my entire game was bugged because I had plenty of other issues including: Mantis ship not going to surface and not being able to board it, UC missions to find and destroy ships and those ships would never spawn, I was never given the star eagle after becoming a freestar marshal, magsniper not working, and plenty of other bugs. I have noticed that in NG+ the magsniper actually works but this play through I didn't try anything other than starjacker.

Does sound like an issue with your save, but I wanted to thank you for the detailed report before closing.


Migrate alpha.5 tutorials

This PR migrates five tutorials from substrate.dev to substrate.io
The five tutorials are the same five that were updated in https://github.com/substrate-developer-hub/substrate-developer-hub.github.io/pull/517
There are more tutorials to port, I'm opening followup issues for that work.

Also requesting review from @danforbes

hey @JoshOrndorff i removed a trailing comma from the /config.json file – it was breaking the build. it will probably be good to find some other images so each featured image can be unique. otherwise, everything else seems great!


Add series alias

Add possibility to add alias for a series. Useful for simpler, possibly unambiguous, searches.
For example, "tm" for "Taskmaster", or "ds9" for "deep space nine".
I guess it should be a separate command? alias and unalias ?
epm alias tm=123

If a search exactly matches an alias it should return unambiguously, even though there were other matches. (it could hint about the other matches, however)

Superceded by #63


When Bar Graph graphs both positive and negative values graph does not show negative Y axis

I'm trying to make a bar graph that resembles this one:

I'm not even worried about the line graph in the middle, I'm concerned about the fact that when I graph the bar graph using the config option scaleBeginAtZero: true , ChartJS doesn't take into account displaying a negative scale but just shows the negative bar graphs running off the page.
Any help or updates that would allow this would be fantastic.

Duplicate of #669


Crash when placing a slab on the upper half of a block

crash-2020-06-21_02.47.14-client.txt

Just as the title says here. I place a slab on the upper half of this block, and the game hard crashes.
This crash is 100% consistent, and happens every single time.
Judging by the log, this could be a FoamFix issue, but I'm not very experienced at reading these things. Haven't yet tried it without FoamFix.
Edit: The crash still occurs without FoamFix enabled.
crash-2020-06-21_02.54.03-client.txt

Hmm. That is very strange. I'll take a further look and see if I can fix this

Please try this in the latest version as I think I may have fixed it :)

Please try this in the latest version as I think I may have fixed it :)

Really sorry I didn't get back to you sooner- very distracted- but it does seem to have worked!
Very cool stuff. I'll be glad to include this mod in my pack!

Glad it is fixed! Sorry about that :)


Failed to update cabal-install on a fresh Arch Linux installation

On a fresh Arch Linux installation, I'm following the instruction in README:
# install the last known "best" GHC version
ghcup install
# install a specific GHC version
ghcup install 8.2.2
# set the currently "active" GHC version
ghcup set 8.4.4
# install cabal-install
ghcup install-cabal
# update cabal-install
cabal new-install cabal-install

And there is an error raised while processing the last command line task:
$ cabal new-install cabal-install
cabal: ghc-pkg dump failed: dieVerbatim: user error (cabal:
'/home/kaizhao/.ghcup/bin/ghc-pkg' exited with an error:
ghc-pkg: /home/kaizhao/.cabal/store/ghc-8.4.4/package.db:
getDirectoryContents:openDirStream: does not exist (No such file or directory)
)

$

The error insists after running the cabal new-update command to download the latest package list.
Tree of directories and files in ~/.cabal:
$ tree .cabal/
.cabal/
├── bin
├── config
└── packages
    └── hackage.haskell.org
        ├── 01-index.cache
        ├── 01-index.tar
        ├── 01-index.tar.gz
        ├── 01-index.tar.idx
        ├── 01-index.timestamp
        ├── hackage-security-lock
        ├── mirrors.json
        ├── root.json
        ├── snapshot.json
        └── timestamp.json

3 directories, 11 files

Yes, it's a known cabal bug https://github.com/haskell/cabal/issues/5516
Solution is to mkdir -p ~/.cabal/store/ghc-8.4.4/package.db

Yes, it's a known cabal bug haskell/cabal#5516
Solution is to mkdir -p ~/.cabal/store/ghc-8.4.4/package.db

Oh. Thanks! After the solution applied it works now. <3


[bug] Using Chinese characters in the options parameter of the invoke method causes the type returned by request.body() to be not Raw.

Describe the bug
I encountered an issue when using the writeFile method. If Chinese characters are present in the options parameter of the invoke method, it causes the type returned by request.body() to be not Raw.
Reproduction
#[tauri::command]
async fn test(
    request: tauri::ipc::Request<'_>,
) -> Result<(), String> {
    println!("{:?}", request.body());
    println!("{:?}", request.headers().get("path"));

    if let tauri::ipc::InvokeBody::Raw(data) = request.body() {
        println!("{:?}", data);
    } else {
        println!("failed");
    }

    Ok(())
}

const data = new TextEncoder().encode("H");
invoke("test", data, {
    headers: {
        path: "a测试"
    }
})

Json(Array [Number(72)])
Some("aa\xe6\xb5\x8b\xe8\xaf\x95")
failed

Expected behavior
Make request.body() return the type as Raw.
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.19044 X64
    ✔ WebView2: 128.0.2739.42
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.82.0-nightly (100fde524 2024-08-28)
    ✔ cargo: 1.82.0-nightly (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: nightly-x86_64-pc-windows-msvc (default)
    - node: 20.15.0
    - pnpm: 9.4.0
    - npm: 10.8.1
    - bun: 1.1.17

[-] Packages
    - tauri [RUST]: 2.0.0-rc.7
    - tauri-build [RUST]: 2.0.0-rc.7
    - wry [RUST]: 0.42.0
    - tao [RUST]: 0.29.1
    - tauri-cli [RUST]: 2.0.0-rc.5
    - @tauri-apps/api [NPM]: 2.0.0-rc.3
    - @tauri-apps/cli [NPM]: 2.0.0-rc.7

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite

Stack trace
No response
Additional context
No response

This is just how headers work, only ISO-8859-1 strings is accepted as valid header. To workaround this, you can use encodeURIComponent and then use percent_encoding crate on Rust side to decode the value.


Validate robots.txt

Either use Gem to generate robots.txt, or validate txt output so it is known it is correct

Done via Google webmaster tools


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Clarify param upgrade process + make backup

Clarifies upgrade process for users, making it harder for them to mess up.
Makes a backup of mod regulation.bin during param upgrade process.

@katalash Can I get some feedback on this? The reason behind it was to stop users very-frequently reporting param upgrading not working (which was ultimately caused by them being confused by the process), which is something I'd very much like to avoid with AC6

I'll look at it more closely soon

Making a new PR that does this (without the conflicts)


Local pull request success status testing

Docs Build status updates of commit 633561e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

E2E_DocsBranch_Dynamic/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


It is not working for me only the first led is turning green ,its connecting to wifi but no output

try rolling back the version of FastLED, I am on 3.2.X


Don't reinstall already installed version

scalaenv install doesn't seem to check if the version has already been downloaded.

resolved by https://github.com/scalaenv/scalaenv/commit/4a6df15560da98512fe81b7d9aa24558fecd94ad


Don't display beta tags for symbols with availability items without introduced version.

Bug/issue #, if applicable: 139245007
Summary
Don't display beta tags for symbols with availability items without introduced version.
This change makes symbols without introduced version to not be marked as beta.
Dependencies
Describe any dependencies this PR might have, such as an associated branch in another repository.
Testing
Availability.docc.zip
Steps:

Preview the attached documentation catalog.
Assert that the symbols are not marked as beta in the curation.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[X] Added tests
[X] Ran the ./bin/test script and it succeeded
[ ] Updated documentation if necessary

@swift-ci please test


exp/services/soroban-rpc: Add LedgerEntry in-memory storage

Use a history archive checkpoint + captivecore txmeta to maintain an in-memory storage for the ledger entries needed for:

Obtaining preflight information (see #4692 ) for the simulateTransaction method
Implementing the getContractData method
Implemeting getAccount method.

Using this storage (together with #4692) we should be able to completely remove the existing Soroban RPC dependencies on

Core's getledgerentry endpoint
Horizon (used for the getAccount method)

https://github.com/stellar/go/pull/4694 could also piggyback onto the txmeta stream of captive core to remove its Horizon dependency.
The PR has only been very mildly on futurenet.
TODO:

Test on pubnet to check feasibility:

whether the memory consumed is overkill
whether the initialization time is overkill

Fix tests
Address code TODOs
Make the code production ready (more robust/readable)

I have tested it against pubnet on my mac and the memory consumption is pretty high (around 20GB for soroban-rpc):

Note that this is without ContractData ledger entries, which don't yet exist in pubnet.
Processing the first checkpoint took ~3 minutes.
As expected, starting up (also in-memory) captive core took ~7 minutes to initialize (catchup to the checkpoint, sync and start emitting txmeta)
I am going to try to use compressed  ledger keys to see if the memory consumption goes down, but I don't think we will be able to get away with having everything in memory due to the memory consumption.

Using compressed ledger keys only reduced the memory usage by 3GB.

@tsachiherman quite the opposite, I am going to migrate this to the tools repo and use it as the basis of the Soroban RPC storage work (which needs to rely on captive core)

@tsachiherman quite the opposite, I am going to migrate this to the tools repo and use it as the basis of the Soroban RPC storage work (which needs to rely on captive core)

yes, that was what I meant. We won't be needing this here, but may consider porting that.


Add dumping services to dumpK8Env in the mixer e2e test

This will allow, in particular, checking the LoadBalancer public IP of istio-ingress, and comparing it with the IP that is used to access the tested application via Istio Ingress.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: costinm
Assign the PR to them by writing /assign @costinm in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/test e2e-suite-rbac-auth

@vadimeisenbergibm: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-suite-rbac-auth

/test istio-pilot-e2e

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-e2e

/test e2e-suite-rbac-auth

@douglas-reid each test has a different problem:

prow/istio-pilot-e2e.sh: fails on accessing httpbin.org. Either httpbin.org has some DNS issues or it started to filter our requests to prevent DOS. We can consider to cancel Egress tests, or to access our own servers, or to try some other external service like cnn.com.
prow/istio-pilot-e2e-envoyv2-v1alpha3,  ci/circleci: e2e-pilot-noauth-v1alpha3-v2, ci/circleci: e2e-pilot fail on multiple GRPC tests, and TestControllerCacheFreshness, TestControllerClientSync, TestControllerEvents.
prow/e2e-suite-rbac-auth.sh failed on upgrade test, it should be fixed by https://github.com/istio/istio/pull/5316
prow/e2e-bookInfoTests-v1alpha3.sh will be fixed by https://github.com/istio/istio/pull/5055

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid I have updated my previous comment:

prow/istio-pilot-e2e.sh: fails on TestRBAC

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-simpleTests.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-simpleTests.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-simple

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-bookInfoTests-v1alpha3.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-simpleTests.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-simple

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-simpleTests.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-simple

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/e2e-bookInfoTests-v1alpha3.sh
57b10c825468dd6dbd948436b43b7a359e640b7d
link
/test e2e-bookInfo-envoyv2-v1alpha3

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@vadimeisenbergibm: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-auth.sh
4ddecb9e1a721d41ea0b741edd76a880839a8760
link
/test e2e-suite-rbac-auth

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/istio-pilot-e2e.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test istio-pilot-e2e

prow/e2e-bookInfoTests-v1alpha3.sh
da8c238e4da8655aa2df3a39806b0dc43c63a0ec
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

(and maybe ramp down the different ways to get logs and dumps after tests - consolidating on the tool, since the tool will be what we'll recommend to users to generate debug info)

There is a script ( called from make dumpsys ) - can we call that at the end, so all tests get consistent logs ?

@costinm Good idea, let me do it.


Re-render on changes

Currently, if you set a favorite or hidden, you need to leave settings and go back in to see the changes. If its possible it would be nice to have it re-render the lists after edits without needing to leave settings

dont think thats possible 🤔

Bd-like settings does it. And I believe disable/enable plugins does as well.
It rerenders them on click of an item in the sidebar, which is probably the best you can do.

next update is going to include re render on clicking an item on the sidebar

to add to this, re rendering without clicking on a sidebar would require dom (not applicable to favorites, that cant be updated on save) and im trying to remove dom from the plugin, i might keep dom on save might not time will tell


clarification for issue #48

updated clicintip description to clarify only xnxti writes affect clicintip
added detail to mtvec section that edge-triggered interrupt pending bits are cleared by hardware after successful trap handler function address fetch.
same updates as pull #174 but with merge issue fixed.

Hello Dan,
Can you give more detail about why the interrupt pending bit is cleared after the successful trap handler fetch and not before? I don't think this feels right (or perhaps some extra detail is needed).
If the trap handler fetch fails, some other handler will run that will eventually return via the code snippet later in this section:
if (xcause.inhv) //xcause here refers to the cause CSR of the previous privilege mode
    pc := M[xepc]
else
    pc := xepc

This resumes execution at the trap handler address but doesn't clear the interrupt pending bit. This means the interrupt will trigger again when the interrupt handler returns.
I think that either the interrupt pending bit should be cleared before the trap handler fetch or there needs to be some extra logic to clear the bit in the first branch of the above snippet.
Thanks.

The ip bit should be cleared once the hart has committed to taking the interrupt, which happens before table fetch.


Creating source package

Creates a new NuGet source package to reference from benchmarked applications and clients in order to record measures.

Why a source package?

I was expecting this question. And apart from not having to publish another dll I don't remember. But I have that solution in mind for some time for a reason. Trying to figure out now ... If you think there are issues with it then I'll change it.

Not using a source package anymore.


Docs for SystemState should mention using apply() to effect Commands

https://docs.rs/bevy/latest/bevy/ecs/system/struct.SystemState.html
This detail pulled from the Bevy Cheat Book should appear in the Basic Usage section for SystemState:

If you are using Commands, you can choose when you want to apply them to the world. You need to manually call .apply(world) on the SystemState, to apply them.

Sorry I haven't been very active recently. I was wondering if you just want me to add this line to the documentation of SystemState or if there is something more from #6184 that I should also consider?

@zeroacez you can just make the doc changes, no need to worry about #6184.


new order use_all_available parameter not allowed

Is there any reason for use_all_available being out of the valid parameters list while placing orders?

Good question. Has anybody a reason for that?

It's been added in :)


kf-views throws 'relation "read_only_user" does not exist' when running in vagrant

When running views inside the Vagrant VM, it throws an error at the end as per the title.

This also causes issues when testing

Vagrant does not run the upgrade-database steps - that should fix this problem.

 Kingfisher Vagrant Issues raised during docs work

Think now done


Failed to build from sdist with 1.1.15

https://ci.appveyor.com/project/pombreda/thirdparty/build/job/yp3w6bahsokx2swn
 creating build\temp.win32-3.6
  creating build\temp.win32-3.6\Release
  C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -DAHOCORASICK_UNICODE= -IC:\Python36\include -IC:\Python36\include "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE" "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.14393.0\winrt" /Tcpyahocorasick.c /Fobuild\temp.win32-3.6\Release\pyahocorasick.obj
  pyahocorasick.c
  c:\users\appveyor\appdata\local\temp\1\pip-build-mbzdwcr8\pyahocorasick\windows.h(14): fatal error C1083: Cannot open include file: 'msinttypes/stdint.h': No such file or directory
  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\cl.exe' failed with exit status 2

  ----------------------------------------
  Failed building wheel for pyahocorasick
  Running setup.py clean for pyahocorasick
Failed to build pyahocorasick
ERROR: Failed to build one or more wheels

This is missing in the MANIFEST.in

@pombredanne  thank you for the fix

Sure thing!


Fixed the issue that agent keeps sending bundles

Signed-off-by: myan<EMAIL_ADDRESS>Ref: https://issues.redhat.com/browse/ACM-7028

、retest

/retest

/retest

/test test-e2e

/test test-e2e

/test test-e2e

/retest

/test test-e2e

/test test-e2e

/test test-e2e

/retest

/hold
Need to check why the complete compliance bundle was not processed on the conflation unit.

/unhold

we can find that the completeComplianceBundle is processed by the conflation unit

/cc @clyang82


test: update cwebp

Brief Information
This pull request is in the type of:

[ ] bug fixing
[ ] new feature
[x] others

What does this PR do?
Update cwebp to latest version which is 8.0.0
Fixed issues

Details
Before: What was the problem?

After: How does it behave after the fixing?

Document Info
One of the following should be checked.

[ ] This PR doesn't relate to document changes
[ ] The document should be updated later
[ ] The document changes have been made in apache/echarts-doc#xxx

Misc
ZRender Changes

[ ] This PR depends on ZRender changes (ecomfe/zrender#xxx).

Related test cases or examples to use the new APIs
N.A.
Others
Merging options

[ ] Please squash the commits into a single one when merging.

Other information

@susiwen8 Please add the background of this PR. Thanks!


homeassistant-pyozw==0.1.2 installation failed on macOS

Home Assistant release with the issue: 0.85.1 and 0.86.0

Last working Home Assistant release (if known): 0.84.6
Operating environment (Hass.io/Docker/Windows/etc.): macOS / Python 3.6.2

Component/platform: Zwave

Description of problem:
Zwave not working upon upgrade to hass 0.85.1
Traceback (if applicable):
2019-01-12 12:11:57 ERROR (SyncWorker_12) [homeassistant.util.package] Unable to install package homeassistant-pyozw==0.1.2: Command "/Users/josh/.pyenv/versions/3.6.2/bi
n/python3.6 -u -c "import setuptools, tokenize;__file__='/private/var/folders/cj/gm9hq24s2k75n_1spplts7x00000gn/T/pip-install-cy1t38l2/homeassistant-pyozw/setup.py';f=get
attr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /private/var/folders/cj/gm9hq
24s2k75n_1spplts7x00000gn/T/pip-record-03jo9xvm/install-record.txt --single-version-externally-managed --prefix  --compile --user --prefix=" failed with error code 1 in /
private/var/folders/cj/gm9hq24s2k75n_1spplts7x00000gn/T/pip-install-cy1t38l2/homeassistant-pyozw/
2019-01-12 12:11:57 ERROR (MainThread) [homeassistant.requirements] Not initializing zwave because could not install requirement homeassistant-pyozw==0.1.2
2019-01-12 12:11:57 ERROR (MainThread) [homeassistant.setup] Setup failed for zwave: Could not install all requirements.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

zwave:
  usb_path: /dev/cu.usbmodem14101996
  network_key: !secret zwave_network_key

Additional information:
Tried installing homeassistant-pyozw==0.1.2 manually using pip, but hass still wanted to install it, so rolled back to 0.84.6

Back with pyozw==0.1.3 and hass 0.91.0, guess it's time for another manual upgrade

@pvizeli Got any ideas on this one?


incompatible Crossplane version: package is not compatible with Crossplane version (v1.16.0-rc.0.38.gdd131a7a)

What happened?
     Message:               incompatible Crossplane version: package is not compatible with Crossplane version (v1.16.0-rc.0.38.gdd131a7a)

Warning

This function relies on functionalities only available in Crossplane 1.15 and later. It will not work with earlier versions.

How can we reproduce it?

What environment did it happen in?
Function version:  xpkg.upbound.io/crossplane-contrib/function-environment-configs
v0.0.4
v0.0.5

This works with 1.15.0 thought (tested with v0.0.5)

looks like this is a Crossplane issue, the underlying library doesn't handle prereleases as I would have expected: https://github.com/Masterminds/semver/blob/10ab64a0cd83ee20d259b6c0ecdfd785733ea2ee/constraints.go#L411-L416 🤔 you'll have to set ignoreCrossplaneConstraints: true when deploying the Function.


TensorFlow C API vs. TensorRT: "Op type not registered 'TRTEngineOp' in binary running on ..."

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04.1 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): docker image (binary)
TensorFlow version (use command below): v2.3.0-rc2-23-gb36436b087 2.3.0
Python version:
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 11.0
GPU model and memory: GTX 1660 Ti, mobile, 6GB

Describe the current behavior

I have a SavedModel that I convert to a TensorRT-optimized model using trt.TrtGraphConverterV2
I try to load the resulting model via the TensorFlow C API
My C++ program displays the following error and exits:
Op type not registered 'TRTEngineOp' in binary running on [docker container]. Make sure the Op and Kernel are registered in the binary running in this process. Note that if you are loading a saved graph which used ops from tf.contrib, accessing (e.g.) 'tf.contrib.resampler' should be done before importing the graph, as contrib ops are lazily registered when the module is first accessed.'

Describe the expected behavior
I expect the model to be loaded and to be able to use it for inference, as I can with a non-TensorRT-optimized model.
Standalone code to reproduce the issue
I'm happy to post code but it seems all you have to do is load a model with TF_LoadSessionFromSavedModel (which doesn't exit) and then, in my case, when I call TF_GraphOperationByName, it prints the error and exits.
Other info / logs
If you google this error message, a lot of people have encountered this problem over the last 2 years.
Some people were able to solve it with much earlier versions of TensorFlow by calling:
TF_LoadLibrary("_trt_engine_op.so", status);
But this does not work for me, the docker image doesn't even seem to have this .so file anywhere, and other people online claim the call is unnecessary.
It seems that TensorRT has been folded into TensorFlow version 2, but maybe somebody forgot to put it into the C API libraries?

I have the same exact problem with tf 2.4, cuda 11.2, trt 7... did someone solve it?

@jappoz
For cuda 11.2 please use tf 2.5 or nightly and let us know.

@jappoz
For cuda 11.2 please use tf 2.5 or nightly and let us know.

Done. Switching to tf 2.5.0-rc1 did not solve the problem.

tf.contrib module has been deprecated, as the error message suggests, use the OP which does not make use of OP from deprecated tf.contrib.


Table checkbox - remove aria-label

The following element has an aria-label attribute that is meant for the expand/collapse button:
<td class="pf-c-table__check">
  <input type="checkbox" name="checkrow1" aria-labelledby="expandable-table-node1" aria-label="Details">
</td>

The aria-label="Details" should not be included on .pf-c-table__check > input.
In this case, aria-labelledby references the row header to provide an accessible label.

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How can I get spectrum waveforms?

I want to drow spectrum of signal, not a oscillogram. Is it possible to do it?

Could you please provide more info on exactly what you wanna achieve? any visual aid will be helpful.

Sorry for delay with answer.

That what I meant.
Graph with frequency and amplitude.

yes i need some thing like this too ,  get the current playing audio amplitude , i mean getting the exact amplitude or energy of the audio in that specific time.
for example : we have 3 min audio i want to get the exact amplitude of each 100 millisecound,
i think we could get it now but the problem is we are getting it as list but i want to get the double while playing the audio


Invalid RedirectURI for Docker Container

Describe the bug
Sadly currently the state of the documentation of how to deploy the docker container is quite the mess with a bunch of dead links (i.e. here https://hub.docker.com/r/isaaclevin/presencelight the link for "Cross Platform Blazor/Docker Version" points to a non-existing endpoint) and conflicting information. I was able to figure out that the ports should be 5001 for https (not 443) and 5000 for http (not 80) after digging around for a while. Sadly both 443 and 80 are mentioned somewhere as the ports inside the container.
It would be very nice if there was a dedicated step by step guide on how to get the container up and running without detours on how to handle ssl outside of docker and whatnot.
Finally I was able to get it somewhat running but when I try to get to my containers endpoint at https://<docker_hosts_hostname>:5001/ I get a message stating that the reply URL specified in the request does not match the reply URLs configured for the application: 'f8119f58-4523-44c1-ab72-b2e0c815bd6a'.
To Reproduce
Steps to reproduce the behavior:

deploy a container
configure the parameters as shown below and trust the certificate on the host level
configure for example https://localhost:5001 as the "AzureAd_RedirectHost" Env variable
visit https://<docker_hosts_hostname>:5001
See error

Expected behavior
I would like to be able to sign in to the application
Screenshots
referenced in "To Reproduce":

Further details

OS: [e.g. iOS]
PresenceLight App Type Docker
PresenceLight Build Latest
PresenceLight Version Unable to reach application
Did you clear settings.json? (C:\Users\username\AppData\Local\Packages\37828IsaacLevin.197278F15330A.SomeValue\LocalState\settings.json) blank docker deployment
ASP.NET Core version 5.0.11

I agree the docs are confusing, apologies for that. For the redirect URI, it needs to be one of the below, as that are the ones that are registered in Azure AD

If you can configure your container to run under one of those urls, let me know. I do have plans to update the docs as well.

I now tried the following three values for the env var AzureAd_RedirectHost: https://<IP_ADDRESS>:4433, http://<IP_ADDRESS>:4433 and <IP_ADDRESS>:4433 but for all I get the message AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'f8119f58-4523-44c1-ab72-b2e0c815bd6a'. Am I even changing the correct setting?

can you remote into the container and update the value in the appsettings.json? I wonder if the mapping in the container is not happening

The value inside the appsettings.json was "https://localhost:5001/" even though I configured "https://<IP_ADDRESS>:4433" as the value in the env var. I changed it to "https://<IP_ADDRESS>:4433" in the appsettings.json and tried it with and without restarting the container but I still get the same message.

@isaacrlevin is there any further information I could provide you to solve this?

I have a version of this working, but it is in this branch
https://github.com/isaacrlevin/presencelight/tree/blazor-wpf
I have made a ton of changes to consolidate PresenceLight to run one app and I took the opportunity to fix the docker setup as well. If you want to test it for me, that would help.
if you checkout that branch, and docker build the default docker file and then run
 docker run --rm -it -p 5000:80 -p 5001:443 -e ASPNETCORE_URLS="https://+;http://+" -e ASPNETCORE_HTTPS_PORT=5001 -e ASPNETCORE_Kestrel__Certificates__Default__Password="presencelight" -e ASPNETCORE_Kestrel__Certificates__Default__Path=/https/presencelight.pfx -v $env:USERPROFILE\.aspnet\https:/https/ presencelightweb

You should have localhost:5001 work (you may have to go to 5000 and have the https redirect kick in initially)
Let me know

@Xyolyp get a chance to look at this?

@isaacrlevin thank you for continously investing time and effort!
I just got around to it and sadly building the Dockerfile fails with the following output:
jonathan@iobroker:~$ git clone https://github.com/isaacrlevin/presencelight.git
Cloning into 'presencelight'...
remote: Enumerating objects: 6698, done.
remote: Counting objects: 100% (527/527), done.
remote: Compressing objects: 100% (386/386), done.
remote: Total 6698 (delta 327), reused 238 (delta 138), pack-reused 6171
Receiving objects: 100% (6698/6698), 8.96 MiB | 6.66 MiB/s, done.
Resolving deltas: 100% (4816/4816), done.
jonathan@iobroker:~$ cd presencelight/
jonathan@iobroker:~/presencelight$ git checkout blazor-wpf
Branch 'blazor-wpf' set up to track remote branch 'blazor-wpf' from 'origin'.
Switched to a new branch 'blazor-wpf'
jonathan@iobroker:~/presencelight$ git pull
Already up to date.
jonathan@iobroker:~/presencelight$ docker build .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/jonathan/presencelight/Dockerfile: no such file or directory
jonathan@iobroker:~/presencelight$ sudo !!
sudo docker build .
unable to prepare context: unable to evaluate symlinks in Dockerfile path: lstat /home/jonathan/presencelight/Dockerfile: no such file or directory
jonathan@iobroker:~/presencelight$ sudo docker build src/PresenceLight.Web/
Sending build context to Docker daemon  241.7kB
Step 1/18 : FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base
 ---> 8d32e18b77a4
Step 2/18 : WORKDIR /app
 ---> Using cache
 ---> 7216957c8ac7
Step 3/18 : FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
 ---> e86d68dca8c7
Step 4/18 : WORKDIR /src
 ---> Using cache
 ---> 15aae41219b7
Step 5/18 : COPY ["PresenceLight.Web/PresenceLight.Web.csproj", "PresenceLight.Web/"]
COPY failed: file not found in build context or excluded by .dockerignore: stat PresenceLight.Web/PresenceLight.Web.csproj: file does not exist

sorry, should have been more clear, you need to point at the docker file
/presencelight/src/PresenceLight.Web/Dockerfile

@isaacrlevin I recognized that you merged the branch and therefore decided to pull the latest docker image.
This sadly still fails with the same error as before when trying to login. But it was very easy to get it up and running with the command you posted in this thread. Now only the RedirectHost quirk has to be ironed out and I would like to assist you with writing the documentation once it's up and running.
Maybe a sitenote worth mentioning as I'm unsure if it hinders the default config to work: my docker host is running headlessly and I'm using a different workstation to access the website hosted by the container.

Set an environment variable like this
AzureAd__RedirectHost=some url

Notice 2 underscores

@Xyolyp this work for you?

@isaacrlevin sorry for letting you wait. I didn't get it to work with any of the following values for the containers Env Var: AzureAd__RedirectHost:
localhost:5001, https://localhost:5001, https://localhost:5001/
I still get the same error message as I got at the beginning:
AADSTS50011: The reply URL specified in the request does not match the reply URLs configured for the application: 'f8119f58-4523-44c1-ab72-b2e0c815bd6a'.

Hold on, let me get a clear picture of what you are doing.

You have PL running in a container on a remote device
You are accessing it from some other machine
You set the AzureAd__RedirectHost value to localhost and you get a failure
Have you tried to set it to the IP of the remote machine? The IP HAS TO BE <IP_ADDRESS>

I've deployed the PL container on a server in my local network with the hostname iobroker and the ip <IP_ADDRESS>.
I'm accessing the webpage from my desktop workstation with the ip <IP_ADDRESS>
I've set the AzureAd__RedirectHost to these exact values one after the other and tried accessing the page each time: localhost:5001, https://localhost:5001, https://localhost:5001/
I didn't try to set any other values for the env var AzureAd__RedirectHost

That won't work. For PL to work, I have to register EVERY REDIRECTHOST in Azure AD, which is not feasible. I have one IP registered and it is <IP_ADDRESS>. So if you want to run PL remotely, that has to be the IP of the machine it is running on, host or not.
I assume you can't update your IP address for that machine, but that is the only option at this point

Thank you for the explaination. I'm unexperienced with custom docker networks: could the following setup work?
Create a custom docker network like this:

Configure the container to use the custom network and set the ip to the value you specified:

Set the env var like so:

You would need to update the host IP, aka the one on your network
On Thu, Jan 27, 2022 at 2:23 PM Jonathan @.***> wrote:

Thank you for the explaination. I'm unexperienced with custom docker
networks: could the following setup work?
Create a custom docker network like this:
[image: image]
https://user-images.githubusercontent.com/13995942/151453329-802e89e8-c928-40ba-b872-7d0cd53f7f2a.png
Configure the container to use the custom network and set the ip to the
value you specified:
[image: image]
https://user-images.githubusercontent.com/13995942/151453513-d246b8aa-dfde-4f7b-8443-cdac6cd99dc6.png
Set the env var like so:
[image: image]
https://user-images.githubusercontent.com/13995942/151453443-9bef7e9f-cd10-4253-9d5f-dd34c233f76a.png
—
Reply to this email directly, view it on GitHub
https://github.com/isaacrlevin/presencelight/issues/502#issuecomment-1023697341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACDXTJRHAMOQMZORQVYC6PTUYHAWRANCNFSM5IH5DJWA
.
You are receiving this because you were mentioned.Message ID:
@.***>

An idea just crossed my mind but I can't tell if it would be possible:
Could there be a tiny cloud service to which one get's redirected for authentication and this cloud service performs the request towards the azure api with it's own redirect uri. Once the user gets returned to the cloud service after successfully logging in he would need to be redirected from the cloud service to the local service again or something like this.
Would this comply with azure policies and requirements and could this be a feasable solution for the authentication issue?

I don't think so also who would build that service? I apologize that the current Docker configurations work for your environment but I am limited to how much support I can have for custom domain/IP for redirects. Are you not able to update the IP Address of the server on your local network to <IP_ADDRESS>?

@Xyolyp is there anywhere to go with this issue? If not, can I close?

I am also facing a similar issue.
I tried setting variables like AzureAd__RedirectHost and tried editing appsettings.json etc.
I want to be able to at least use a different host instead of just localhost. I am OK with port being 5001.
Is it possible to add a placeholder like
https://my-redirect-host:5001
And I can make my-redirect-host resolve to any local IP using /etc/hosts.

The Uri has to be localhost sadly


Interesting string

Could you please remove this string http://prntscr.com/a4tbgz
Thanks ;)

oh! It's very dangerous! alarm!!!


enable multiple class in schema definition

Hi Chad,
I very little contribution I've need for my project.
best regards,
Hugues

Hi Hugues! Thanks for bringing this to my attention. I thought about making this possible a while back then forgot about it. This feature requires a change in a few spots actually, one in the LdapObjectSchema (just an object representation of the actual ldap object type definition in the YML file) and then an update to the LdapObjectHydrator and the LdapQueryBuilder, as they both used the schema object to build up certain filters.
This should now be possible on master per this commit https://github.com/ldaptools/ldaptools/commit/8ebbc8dc1afde08d15bf702df01fe7fbf2f0ba03. I'm unsure as to when I'll tag a new version at the moment. Could you let me know if it works OK for you?

Closing this one out. Please use version v0.15.0 as it includes this feature.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-2.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 701

Questions ?
Please refer to the Backport tool documentation


Increment version for appconfiguration releases

Increment package version after release of azure-app-configuration

N/A as the master branch as already moved on
@HarshaNalluru Please keep any eye on the automated PR that gets created after the next release

Please keep any eye on the automated PR that gets created after the next release

I didn't take this because the changelog had deletions and Dozie was working/experimenting on it. :)


bug: letsql backend does not respect the case of table names

import ibis
import letsql as ls

db_con = ibis.duckdb.connect()
db_t = db_con.create_table("lowercase", schema=ibis.schema({"A": "int"}))

con = ls.connect()
t = con.register(db_t, "UPPERCASE")
t.execute()

results in Exception: Table not found: UPPERCASE
subsequently running con.tables results in
Tables
------
- uppercase

Closed via #77


Allow multiple scripts per version

Original author<EMAIL_ADDRESS>(March 25, 2013 15:02:15)
I have a large schema with a large seed data set. It is unmanageable (I can barely open an editor) to have this in one file. We have traditionally broken this up into one sql file per table. However, Flyway doesn't support this.
I know I can work around this by versioning each script as a pre-1.0 script, but that's not accurate. Ideally, Flyway would support multiple files at the same version, but with different names, so that we can migrate to a 1.0 and have the scripts match.
Original issue: http://code.google.com/p/flyway/issues/detail?id=460

Is there anyone interested in a fork of this project?

Has something happened here? I think the idea from post before the last is very good.
Is this introduced?

we've "solved" this by abusing flyway's numbering scheme :
we create files like :
com/mycompany/moduleA/1.0.0__Aggregate_A.sql
...
com/mycompany/moduleA/1.0.0__Aggregate_Z.sql
...
com/mycompany/moduleZ/1.0.0__Aggregate_A.sql
...
com/mycompany/moduleZ/1.0.0__Aggregate_Z.sql
and then use a maven build plugin to transform these into names like :
com/mycompany/moduleA/<IP_ADDRESS>.01__Aggregate_A.sql
...
com/mycompany/moduleA/<IP_ADDRESS>.99__Aggregate_Z.sql
...
com/mycompany/moduleZ/<IP_ADDRESS>.01__Aggregate_A.sql
...
com/mycompany/moduleZ/<IP_ADDRESS>.99__Aggregate_Z.sql
this allows for 99 modules, each with 99 sql files. obviously :

it's ugly as hell, but hey it works...
module numbers would need to be preassigned (unless everything lives in a single build tree)
the history db get's blown up like crazy, however if a migration fails the offending file is right there
as a bonus, if sql files need to be ordered, it can easily be achieved


[Feature] global variables in Application definition

I want to define a bunch of env variables in Application definition which can be used across all the components defined in that application.

Can you describe more about your scenario, in which case you need this global variable?

For instance this is my manifest, I am creating an rds and elasticache redis in dev env and  frontend account. How can i reuse the env and account variable.
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
name: argocd-test-cloud-resources
spec:
components:
- name: frontend-dev-rds-aws-argocd-test-01
type: rds-aws
properties:
service_name            :  argocd-test
rds_instance_class      :  db.t3.small
rds_engine_type         :  mysql
rds_engine_version      :  8.0.15
tech_family             :  platform
environment             :  development
account                 :  frontend
- name: frontend-dev-elasticache-redis-argocd-test-02
type: elasticache-redis
properties:
service_name            :  argocd-test
node_type               :  cache.t3.small
cluster_mode_enabled    : 'false'
engine_version          :  5.0.6
tech_family             :  platform
environment             :  development
account                 :  frontend

It seems the envBinding Object can solve your needs. https://github.com/oam-dev/kubevela/issues/1881
apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: argocd-test-cloud-resources
spec:
  components:
    - name: frontend-dev-rds-aws-argocd-test-01
      type: rds-aws
      properties:
        service_name            :  argocd-test
        rds_instance_class      :  db.t3.small
        rds_engine_type         :  mysql
        rds_engine_version      :  8.0.15
    - name: frontend-dev-elasticache-redis-argocd-test-02
      type: elasticache-redis
      properties:
        service_name            :  argocd-test
        node_type               :  cache.t3.small
        cluster_mode_enabled    : 'false'
        engine_version          :  5.0.6
  policies:
  - type: EnvBinding
    properties:
      env-develop:
        patch:
          components:
          - name: frontend-dev-rds-aws-argocd-test-01
            properties:
                tech_family             :  platform
                environment             :  development
                account                 :  frontend
          - name:  frontend-dev-elasticache-redis-argocd-test-02
            properties:
                tech_family             :  platform
                environment             :  development
                account                 :  frontend
      env-production:
        ...

Hi @vijay-dcrust . If you just want to use the global variables, it would be easier to just plugin Argo Workflow as a Component or Workflow Task into KubeVela. Would that work?
On the other hand, if you could provide more details on what you want to do, we can have more specific solutions targeted at the prolem.


E2E : Add end to end test on the mock http plugin

Change description
After performing manual test on the mock http, i realized that it is not working well....
Type of change

[ ] Bug fix (fixes an issue)
[ ] New feature (adds functionality)

Checklists
Development

[ ] Lint rules pass locally
[ ] Application changes have been tested thoroughly
[ ] Automated tests covering modified code pass

Security

[ ] Security impact of change has been considered
[ ] Code follows project security practices and guidelines

Code review

[ ] Pull request has a descriptive title and context useful to a reviewer. Screenshots or screencasts are attached as necessary
[ ] Changes have been reviewed by at least one other contributor
[ ] Pull request linked to issue tracker where applicable

Hey @olivierodo What do you think about adding to put the mock case into another scenario?
I could do it myself.

@tony-go Agree, let's have 2 different scenario


Garage 0.8+ do not build on Darwin

Steps To Reproduce
Steps to reproduce the behavior:

build garage_0_8 introduced in this PR https://github.com/NixOS/nixpkgs/pull/196195 on Darwin (x86 or aarch64)
failed tests

Build log

failures:

---- k2v::item::test_items_and_indices stdout ----
thread 'k2v::item::test_items_and_indices' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- admin::test_admin_bucket_perms stdout ----
thread 'admin::test_admin_bucket_perms' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- k2v::poll::test_poll stdout ----
thread 'k2v::poll::test_poll' panicked at 'Command exited with code 1: Could not assign garage node layout', src/garage/tests/common/ext/process.rs:46:31
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

---- k2v::batch::test_batch stdout ----
thread 'k2v::batch::test_batch' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- bucket::test_bucket_all stdout ----
thread 'bucket::test_bucket_all' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- k2v::item::test_item_return_format stdout ----
thread 'k2v::item::test_item_return_format' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- k2v::errorcodes::test_error_codes stdout ----
thread 'k2v::errorcodes::test_error_codes' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- k2v::simple::test_simple stdout ----
thread 'k2v::simple::test_simple' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::list::test_listmultipart stdout ----
thread 's3::list::test_listmultipart' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::list::test_listobjectsv1 stdout ----
thread 's3::list::test_listobjectsv1' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::list::test_listobjectsv2 stdout ----
thread 's3::list::test_listobjectsv2' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::multipart::test_uploadlistpart stdout ----
thread 's3::multipart::test_uploadlistpart' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::multipart::test_uploadpartcopy stdout ----
thread 's3::multipart::test_uploadpartcopy' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::objects::test_deleteobject stdout ----
thread 's3::objects::test_deleteobject' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::objects::test_getobject stdout ----
thread 's3::objects::test_getobject' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::objects::test_putobject stdout ----
thread 's3::objects::test_putobject' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::simple::test_simple stdout ----
thread 's3::simple::test_simple' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::streaming_signature::test_create_bucket_streaming stdout ----
thread 's3::streaming_signature::test_create_bucket_streaming' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::streaming_signature::test_put_website_streaming stdout ----
thread 's3::streaming_signature::test_put_website_streaming' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::streaming_signature::test_putobject_streaming stdout ----
thread 's3::streaming_signature::test_putobject_streaming' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::website::test_website_s3_api stdout ----
thread 's3::website::test_website_s3_api' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

---- s3::website::test_website stdout ----
thread 's3::website::test_website' panicked at 'Once instance has previously been poisoned', src/garage/tests/common/garage.rs:215:19

Additional context
I discussed with upstream and got this information:

Once instance was poisonned indicatez that the garage server launched for the tests stopped unexpectedly
Can be because the garage binary in $PATH isn't the correct one
(The integration tests spawns a separate process that acts as a garage server, the garage server itself is not embedded in the task so it uses exec)
If you want to debug more througklthoroughly, you can instrument the code of the integration testing framework in src/garage/tests

Notify maintainers
@NickCao @0x4A6F @teutat3s

The tests seem to work fine on my machine (aarch64-darwin, with sandbox enabled):
running tests
Executing cargoCheckHook
++ cargo test -j 8 --release --features=k2v,kubernetes-discovery,bundled-libs,sled,metrics,telemetry-otlp,lmdb,sqlite --target aarch64-apple-darwin --frozen -- --test-threads=8
   Compiling num-integer v0.1.44
...
   Compiling garage v0.8.0 (/private/tmp/nix-build-garage-0.8.0.drv-0/source/src/garage)
    Finished release [optimized + debuginfo] target(s) in 6m 53s
     Running unittests main.rs (target/aarch64-apple-darwin/release/deps/garage-e571c83ab15e8949)

running 0 tests

test result: ok(B. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running tests/lib.rs (target/aarch64-apple-darwin/release/deps/integration-9b7f6eeaea098d0a)

running 22 tests
test k2v::simple::test_simple ... ok(B
test k2v::poll::test_poll ... ok(B
test bucket::test_bucket_all ... ok(B
test admin::test_admin_bucket_perms ... ok(B
test k2v::errorcodes::test_error_codes ... ok(B
test k2v::item::test_item_return_format ... ok(B
test k2v::batch::test_batch ... ok(B
test s3::multipart::test_uploadlistpart ... ok(B
test s3::objects::test_getobject ... ok(B
test s3::list::test_listmultipart ... ok(B
test s3::simple::test_simple ... ok(B
test s3::streaming_signature::test_create_bucket_streaming ... ok(B
test s3::objects::test_putobject ... ok(B
test s3::streaming_signature::test_put_website_streaming ... ok(B
test s3::objects::test_deleteobject ... ok(B
test s3::streaming_signature::test_putobject_streaming ... ok(B
test s3::website::test_website ... ok(B
test s3::list::test_listobjectsv2 ... ok(B
test s3::list::test_listobjectsv1 ... ok(B
test s3::website::test_website_s3_api ... ok(B
test s3::multipart::test_uploadpartcopy ... ok(B
test k2v::item::test_items_and_indices ... ok(B

test result: ok(B. 22 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 19.15s

Finished cargoCheckHook
checkPhase completed in 7 minutes 13 seconds
installing
Executing cargoInstallHook
Finished cargoInstallHook
post-installation fixup
strip is /nix/store/fb4rdxr69sy1vsi98z3njxjzdq3rj3ah-clang-wrapper-11.1.0/bin/strip
stripping (with command strip and flags -S) in  /nix/store/fdb9ic1ivz5ni87g07zqixxpzlmybl6z-garage-0.8.0/bin
patching script interpreter paths in /nix/store/fdb9ic1ivz5ni87g07zqixxpzlmybl6z-garage-0.8.0
/nix/store/fdb9ic1ivz5ni87g07zqixxpzlmybl6z-garage-0.8.0

I think this can be closed with #218843.


⚠ Presupuesta.me has degraded performance

In 4973035, Presupuesta.me (https://staging.presupuesta.me/up) experienced degraded performance:

HTTP code: 200
Response time: 2070 ms

Resolved: Presupuesta.me performance has improved in 950e599 after 13 minutes.


open classes dialog box at mouse pointer location

[Feature request]: After closing rectangular box, a dialog with available classes pops up in the middle of the screen. It is extremely tiring for the eye to repeatedly wander here and there to get back to this dialog box to click the class label. It would be much more efficient to have this dialog box popping up exactly next to mouse pointer where the object is being annotated.
A typical set-up is to have one hand on mouse and other one on W button. Additional to that, if classes dialog box could open there where image is being annotated, it would dramatically speed up things I believe.
I tried to figure out how I could adapt this in present source code using qt, but I am not expert here... any suggestion ? Or would it be difficult for the developer to add this feat ?
Thank you very much

SOLUTION: keyboard buttons can be customized by editing the source code (labelImg.py). For instance, in my case I change button "w" to "+", which is next to Enter key and allows me a much quicker combo open-window-draw-bow-confirm-class, not having to move my eyes away from annotation target too often. Also, holding mouse with left hand you can quickly switch to ctrl-+ to zoom in. In order to edit source code you must install by source:
python3 -m venv
source /bin/activate
cd
git clone  https://github.com/tzutalin/labelImg.git
pip install pyqt5==5.12.1 lxml
cd labelImg
make qt5py3
python3 labelImg
Now custom-edit the key-strokes in labelImg.py and git-commit your changes.


multiple statements

can i query with multiple statements?  just like module 'mysql'

I'm not sure what you mean. Like:
const result = connection.query('SELECT * FROM TABLE; SELECT * FROM OTHERTABLE');

ODBC does have batch support: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/batches-of-sql-statements?view=sql-server-ver15
Unfortunately this package doesn't yet have support for returning multiple result sets in the result object: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/multiple-results?view=sql-server-ver15

I'm not sure what you mean. Like:
const result = connection.query('SELECT * FROM TABLE; SELECT * FROM OTHERTABLE');

ODBC does have batch support: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/batches-of-sql-statements?view=sql-server-ver15
Unfortunately this package doesn't yet have support for returning multiple result sets in the result object: https://docs.microsoft.com/en-us/sql/odbc/reference/develop-app/multiple-results?view=sql-server-ver15

that's what i mean ,thanks


[jvm-packages] Large-scale dataset make executors cannot find address

I hava a dataset, which has more than 1000 partition. I set the "num-executor=40".
From the source code, it will run trainingData.coalesce(numWorkers).
However, from the log, many executors cannot find address and finally the job failed. I have test many times, the results are the same.
I test the same code with samller partition(5), the job succeeds. So I think the reason maybe coalesce function without shuffle. So I change the source code--> trainingData.coalesce(numWorkers, true)
Then, the job succeeds.
@CodingCat Do you know the reason

val partitionedData = {
      if (numWorkers > trainingData.partitions.length) {
        logger.info(s"repartitioning training set to $numWorkers partitions")
        trainingData.repartition(numWorkers)
      } else if (numWorkers < trainingData.partitions.length) {
        logger.info(s"repartitioning training set to $numWorkers partitions")
        trainingData.coalesce(numWorkers)
      } else {
        trainingData
      }
    }

I also set the num-executor=100, but still failed

I think you're right, we shall impose shuffle when creating training RDDs

addressed in https://github.com/dmlc/xgboost/issues/1529

@CodingCat  Thank you for your response. Can you tell me the reason why shuffle should be done in here?