Error deserializing avro schemas serialized with Java app

rust 1.49.0

avro-rs = { version="0.13.0", features=["snappy"]}

I can't deserialize any message , always get an error, like **GetAvroSchemaFromMap**. Before was getting Magical header error, what I solved adding this to my message:
let body_header = [[b'O', b'b', b'j', 1u8].to_vec(), body].concat();
The messages are fine using a Java avro deserializer, but not sure where is the problem with rust.
schema:
  let raw_schema = r#"
        {
          "namespace": "com.tremorvideo.dmpproducer.models",
          "type": "record",
          "name": "USyncMessage",
          "fields": [
            { "type": ["string","null"], "name": "region" },
            { "type": "boolean", "name": "incremental" },
            { "type": [ "null", { "type": "record", "name": "UserMapping", "fields": [
              { "type": "long", "name": "actionTime" },
              { "type": "string", "name": "provider" },
              { "type": "string", "name": "userIds" },
              { "type": ["string","null"], "name": "uuid" }
            ]}], "name": "userMapping", "default": null },
            { "type": [ "null", { "type": "record", "name": "DMPData", "fields": [
              { "type": "string", "name": "userId" },
              { "type": ["string","null"], "name": "deviceId" },
              { "type": "long", "name": "actionTime" },
              { "type": "string", "name": "provider" },
              { "type": ["string","null"], "name": "partner" },
              { "type": "string", "name": "segments" }
            ]}], "name": "dmpData", "default": null }
          ]
        }
        "#;

reading:
let reader_schema = Schema::parse_str(raw_schema).unwrap();
let reader =
                  Reader::with_schema(&reader_schema, &body_header[..]);

I always get an error.
Thank you

Hi,
I'm sorry to see you didn't get an answer on this. I am having the same problem myself, did you find a solution in the end ?

I ended using protobuf in the producer side. Seems like the avro schema is expected with the message, but I won't do that , another option is to use another lib that provide the schema, it's a similar dependency from crates.io, I don't want to spend more time testing another one.
Using protobuf is pretty simple.


[DRAFT] Some rudimentary version of how releasing could work

Here are some ideas how releasing could later work. It's far from finished.
In this setup, a docker image provides the base installation to use for building.
GPG keys are provided from the outside of the container by providing access to the host gpg-agent. Alternatively, we could provide keys similarly as sbt-ci-release does it by actually providing the secret as an environment value. Both options don't seem super compelling. The use of gpg-agent at least provides the possibility to also use smartcards/yubikeys for signing automatically.
The setup of gpg-agent propagation to the docker container is right now quite brittle:

it requires that the user id must match between host and container
it assumes a certain setup of how gpg-agent is connected that works on Ubuntu/Linux but might not work on other distros

GPG keys are provided from the outside of the container by providing access to the host gpg-agent. Alternatively, we could provide keys similarly as sbt-ci-release does it by actually providing the secret as an environment value. Both options don't seem super compelling. The use of gpg-agent at least provides the possibility to also use smartcards/yubikeys for signing automatically.

This is more of a long term idea, but I always imagined using sbt-pgp directly rather than sbt-ci-release since sbt-pgp just wraps over gpg so there is no reason why it should have the same problems as sbt-ci-release. In fact I think in general sbt-ci-release is not really needed for pekko projects, the only functionality we use from it is sbt-dynver considering there is broad agreement on how to do a proper release which is not going to be via pushing a git tag.


Is there a plan in place for adding support for async await?

Async-await will be added in Swift 5.5.
https://github.com/apple/swift-evolution/blob/main/proposals/0296-async-await.md

Given that Swift 5.5 is now released, will Graphiti support async-await?

Hello @cshadek, @paulofaria and @adam-fowler
For organization, I think this issue should be reopened and linked to https://github.com/GraphQLSwift/Graphiti/pull/71
It appears that support for async/await is a big undertaking. I really hope to see it implemented some day.
I've just started learning about this package from https://www.raywenderlich.com/21148796-graphql-tutorial-for-server-side-swift-with-vapor-getting-started
It's a great package, thank you all for your hard work!

Hi, thank you for your kindness. I will try to finish this by the end of the month. The async part itself is mostly done. It's just that I took the chance to improve the API so we can release a new major version and life got in the way.

I was also waiting on https://github.com/apple/swift-evolution/blob/main/proposals/0348-buildpartialblock.md to improve the API greatly. Instead of using classes and initializers for the Schema definition, we'll be able to use functions and structs, which will make the API look much closer to the GraphQL SDL.

@cshadek I have done a little thinking about subscriptions and async/await. The new AsyncSequence should be able to replace reactive drivers like GraphQLRxSwift.

This sounds amazing

Yeah I just found it earlier today.  I really wonder if there shouldn't be some strategic partnership between Pioneer and GraphQLSwift.  It's almost like they want to build Apollo Server for Swift - that would be incredible!

I have an MR into GraphQL that adds async/await support, and a followup one ready for Graphiti once that one goes through.

Woah, I hadn't seen that repo before! That's pretty awesome stuff they're doing! Yeah, it seems like we could easily bring some of the extensions they've made into this repo.

I think I can help move the async-await extensions I made from Pioneer here. The only problem with those extensions I made is that at the moment, they completely ignore the Sendable conformance which is not enforced now with Swift 5 but will be a problem later on with Swift 6 which is set to be safe-by-default and the only solution I see is @_unsafeSendable attribute but I haven't played with it yet.

I'm marking this as resolved, since async/await support was added by https://github.com/GraphQLSwift/Graphiti/pull/78


add an alias for err

We are looking into using this lib across our org and we also use pino for logging across the many services and err is treated specially due to the default serializers, in particular due to the default for objects named err to be serialized via pino's error serializer.
While we could import {err as someOtherVar} in every service using neverthrow to avoid conflicting with our error logging standard, it would be nice to have an alias name for err  in neverthrow that works in our setup.
Would you consider error(perhaps invites the same problem though for other contexts) or notOk (my personal favourite) or erroredResult as an additional alias export to err ?

Hey @naseemkullah,
You mean TransitApp when you say "our org"? I'm a long time TransitApp user!
I understand that there's an unfortunate naming collision. However, I don't think creating an alias within neverthrow is the right approach.
Have you considered perhaps creating a module in your project that renames err to whatever the team would like (such as error or notOk?
// inside of utils/result.ts or something similar

import nt from 'neverthrow'

export type Result<T, E> = nt.Result<T, E>
export type Ok<T, E> = nt.Ok<T, E>
export type NotOk<T, E> = nt.Err<T, E>

export const notOk = nt.err
export const ok = nt.ok

Then your team would only reference utils/result, and not neverthrow. Would that work?

Thanks @supermacro yep Transit :)
That's a nice idea but I was hoping to avoid adding anything extra in our projects. notOk is pretty great imho, so if you ever reconsider adding the alias in the lib itself that would be swell, if not we will either use your suggestion in all our projects or simply import {err as notOk} each time.

https://github.com/supermacro/neverthrow/pull/84 if you ever change your mind ;)

I am going to be closing this issue. On a closing note, I thought of another idea. Within your build stage you could use awk + sed and friends to inject any code into node_modules/neverthrow ... just a thought .. and it wouldn't be many lines of code!


JWT auth plugin improvements

[x] new plugin impl
[x] copy and re-do all tests from previous impl
[x] add example
[x] cookie support
[x] update docs
[x] migration guide
[x] changeset

Some tests are failing, aside from that LGTM. Let's wait with merging before we also verify the complimentary Mesh plugin.
Should the incoming GraphQL request signature checker plugin also life in this package?

I think the verification part should live in the Mesh plugin, as it's coupled with it. We can document the Mesh encryption in case someone is using something that isn't Yoga for their subgraph.


A generated module manifest contains two identicals GUID

#
# Module manifest for module 'moduleManifest-67578f84-aaeb-491b-8bb2-25acd5888678'
#
# Generated by: LaurentDardenne
#
# Generated on: 20/10/2016
#

@{
...
# ID used to uniquely identify this module
GUID = '7cd7d08e-4560-479c-92f5-ae9937d9408b'
...

Is-it correct ?

I'm not following you, where are the two identical GUIDs?  If you are referring to the fact that this guid 67578f84-aaeb-491b-8bb2-25acd5888678 is different from this one '7cd7d08e-4560-479c-92f5-ae9937d9408b, that is correct.  The first one was generated to form a temporary filename. We generate to a temp file so that we can then compare against the original PSD1 to see if there are any conflicts.  However, I can see that the auto-generated comment containing the value passed to the Path parameter should not reflect the temp filename but the permanent filename.  I'll try to get that changed tonight.

I'm not following you, where are the two identical GUIDs?
Yes,  I was wrong : two different guid
that is correct
Ok.
I I'll try to get that changed tonight
Thanks :-)


Convert $exists to in memory only

This gets all the $exist tests to work with CouchDB and makes it an in
memory operator only.
fixes #67

Thanks for this. I think I was too ambitious with the initial implementation. It is much much better to just match Cloudant/Couch's implementation exactly and then propose new operators if I think they're implemented poorly.


Infinetely generating irrelavent response when running phi3-mini in Linux Terminal

What is the issue?
I setted up a modelFile that loads PHI-3-mini-instruct, and whatever input I give it it starts to generate infinite response related to coding as shown in the screenshot.
Here is the Content of the model file:
FROM ./Phi-3-mini-4k-instruct.Q4_0.gguf
PARAMETER temperature 0.1
PARAMETER num_predict 50

Loaded by ollama create phi3 -f FileName without adding any extension to the file
Also the issue exists before adding the parameters

OS
Linux
GPU
Intel
CPU
Intel
Ollama version
0.1.39

The model is working fine when I use it with GPT4ALL so It is not a problem with the model file


Always guessing zero on Handwriting Recognition

Brian sometimes gets to a point in the training when he always guesses zero. I don't know why this is yet, but I'm working on it and will be fixing it soon hopefully.

I think I found the error. When this happens, every single value inside of Brian becomes null. I don't know why yet or how to fix it, but there where yer problems at.

I fixed the problem. It was because the MNIST training data I was using had an extra line at the bottom that was being indexed randomly. Whenever it got indexed, it would pull nothing, and JavaScript would see that as a NaN and plug that in to network, effectively killing it.


Remove stats in hnsw

Signed-off-by: liliu-z<EMAIL_ADDRESS>stats is not thread safe in Knowhere. Delete it in case of crash.

\lgtm

/lgtm


Consider adding CollectionCondition.texts(List) and CollectionCondition.texts(List)

Sometimes "texts data to be asserted for collection" comes as List<String> not String[]
This leads to such ugly code:
headers().shouldHave(exactTexts(listOfTexts.toArray(new String[0])));

The idea is to add additional conditions which can accept List<String> instead of String.../String[]
so code from above becomes:
headers().shouldHave(exactTexts(listOfTexts)));

Agree. Let's use Lists!

@yashaka implemented by @pavelsmolensky in PR #425
Merged to Selenide 4.1


Change to keep in sync with latest cni config

This commit contains change to pick the latest cni config from the configured CNIConfDir.
With this change any changes made to the cni config file will be picked up on the kubelet's runtime status check call.
Ofcourse this would lead to undefined behavior when the cni config change is made in parallel during pod creation. However its reasonable to assume that the operator is aware of the need to drain the nodes of pods before making cni configuration change. The behavior is currently not defined in kubernetes. However I see that similar approach being adopted in the upstream kubernetes with dockershim. Keeping the behavior consistent for now.
Signed-off-by: Abhinandan Prativadi<EMAIL_ADDRESS>

/retest

This breaks the test.

@abhi Why you have a branch in upstream?

@Random-Liu my bad. Will close the PR and reopen


chore(deps): update dependency esbuild to v0.19.2

This PR contains the following updates:

Package
Type
Update
Change

esbuild
devDependencies
minor
^0.17.17 -> 0.19.2

Release Notes

evanw/esbuild
v0.19.2
Compare Source

Update how CSS nesting is parsed again
CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting:
.foo {
  div {
    color: red;
  }
}

Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all.
Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax.

Fix a scope-related bug with --drop-labels= (#3311)
The recently-released --drop-labels= feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release.

Make renamed CSS names unique across entry points (#3295)
Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled.

Fix CSS ordering bug with @layer before @import
CSS lets you put @layer rules before @import rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the @import rules and then joining files together in the right order. But with @layer, CSS files may now need to be split apart into multiple pieces in the bundle. For example:
/* Original code */
@layer start;
@import "data:text/css,@layer inner.start;";
@import "data:text/css,@layer inner.end;";
@layer end;

/* Old output (with --bundle) */
@layer inner.start;
@layer inner.end;
@layer start;
@layer end;

/* New output (with --bundle) */
@layer start;
@layer inner.start;
@layer inner.end;
@layer end;

Unwrap nested duplicate @media rules (#3226)
With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested @media rules:
/* Original code */
@media (min-width: 1024px) {
  .foo { color: red }
  @media (min-width: 1024px) {
    .bar { color: blue }
  }
}

/* Old output (with --minify) */
@media (min-width: 1024px){.foo{color:red}@media (min-width: 1024px){.bar{color:#00f}}}

/* New output (with --minify) */
@media (min-width: 1024px){.foo{color:red}.bar{color:#00f}}

These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS.

v0.19.1
Compare Source

Fix a regression with baseURL in tsconfig.json (#3307)
The previous release moved tsconfig.json path resolution before --packages=external checks to allow the paths field in tsconfig.json to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the baseURL field from tsconfig.json. This release moves these path resolution rules around again in an attempt to allow both of these cases to work.

Parse TypeScript type arguments for JavaScript decorators (#3308)
When parsing JavaScript decorators in TypeScript (i.e. with experimentalDecorators disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example:
@foo<number>
@bar<number, string>()
class Foo {}

Fix glob patterns matching extra stuff at the end (#3306)
Previously glob patterns such as ./*.js would incorrectly behave like ./*.js* during path matching (also matching .js.map files, for example). This was never intentional behavior, and has now been fixed.

Change the permissions of esbuild's generated output files (#3285)
This release changes the permissions of the output files that esbuild generates to align with the default behavior of node's fs.writeFileSync function. Since most tools written in JavaScript use fs.writeFileSync, this should make esbuild more consistent with how other JavaScript build tools behave.
The full Unix-y details: Unix permissions use three-digit octal notation where the three digits mean "user, group, other" in that order. Within a digit, 4 means "read" and 2 means "write" and 1 means "execute". So 6 == 4 + 2 == read + write. Previously esbuild uses 0644 permissions (the leading 0 means octal notation) but the permissions for fs.writeFileSync defaults to 0666, so esbuild will now use 0666 permissions. This does not necessarily mean that the files esbuild generates will end up having 0666 permissions, however, as there is another Unix feature called "umask" where the operating system masks out some of these bits. If your umask is set to 0022 then the generated files will have 0644 permissions, and if your umask is set to 0002 then the generated files will have 0664 permissions.

Fix a subtle CSS ordering issue with @import and @layer
With this release, esbuild may now introduce additional @layer rules when bundling CSS to better preserve the layer ordering of the input code. Here's an example of an edge case where this matters:
/* entry.css */
@import "a.css";
@import "b.css";
@import "a.css";

/* a.css */
@layer a {
  body {
    background: red;
  }
}

/* b.css */
@layer b {
  body {
    background: green;
  }
}

This CSS should set the body background to green, which is what happens in the browser. Previously esbuild generated the following output which incorrectly sets the body background to red:
/* b.css */
@layer b {
  body {
    background: green;
  }
}

/* a.css */
@layer a {
  body {
    background: red;
  }
}

This difference in behavior is because the browser evaluates a.css + b.css + a.css (in CSS, each @import is replaced with a copy of the imported file) while esbuild was only writing out b.css + a.css. The first copy of a.css wasn't being written out by esbuild for two reasons: 1) bundlers care about code size and try to avoid emitting duplicate CSS and 2) when there are multiple copies of a CSS file, normally only the last copy matters since the last declaration with equal specificity wins in CSS.
However, @layer was recently added to CSS and for @layer the first copy matters because layers are ordered using their first location in source code order. This introduction of @layer means esbuild needs to change its bundling algorithm. An easy solution would be for esbuild to write out a.css twice, but that would be inefficient. So what I'm going to try to have esbuild do with this release is to write out an abbreviated form of the first copy of a CSS file that only includes the @layer information, and then still only write out the full CSS file once for the last copy. So esbuild's output for this edge case now looks like this:
/* a.css */
@layer a;

/* b.css */
@layer b {
  body {
    background: green;
  }
}

/* a.css */
@layer a {
  body {
    background: red;
  }
}

The behavior of the bundled CSS now matches the behavior of the unbundled CSS. You may be wondering why esbuild doesn't just write out a.css first followed by b.css. That would work in this case but it doesn't work in general because for any rules outside of a @layer rule, the last copy should still win instead of the first copy.

Fix a bug with esbuild's TypeScript type definitions (#3299)
This release fixes a copy/paste error with the TypeScript type definitions for esbuild's JS API:
 export interface TsconfigRaw {
   compilerOptions?: {
-    baseUrl?: boolean
+    baseUrl?: string
     ...
   }
 }

This fix was contributed by @privatenumber.

v0.19.0
Compare Source
This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.18.0 or ~0.18.0. See npm's documentation about semver for more information.

Handle import paths containing wildcards (#56, #700, #875, #976, #2221, #2515)
This release introduces wildcards in import paths in two places:

Entry points
You can now pass a string containing glob-style wildcards such as ./src/*.ts as an entry point and esbuild will search the file system for files that match the pattern. This can be used to easily pass esbuild all files with a certain extension on the command line in a cross-platform way. Previously you had to rely on the shell to perform glob expansion, but that is obviously shell-dependent and didn't work at all on Windows. Note that to use this feature on the command line you will have to quote the pattern so it's passed verbatim to esbuild without any expansion by the shell. Here's an example:
esbuild --minify "./src/*.ts" --outdir=out

Specifically the * character will match any character except for the / character, and the /**/ character sequence will match a path separator followed by zero or more path elements. Other wildcard operators found in glob patterns such as ? and [...] are not supported.

Run-time import paths
Import paths that are evaluated at run-time can now be bundled in certain limited situations. The import path expression must be a form of string concatenation and must start with either ./ or ../. Each non-string expression in the string concatenation chain becomes a wildcard. The * wildcard is chosen unless the previous character is a /, in which case the /**/* character sequence is used. Some examples:
// These two forms are equivalent
const json1 = await import('./data/' + kind + '.json')
const json2 = await import(`./data/${kind}.json`)

This feature works with require(...) and import(...) because these can all accept run-time expressions. It does not work with import and export statements because these cannot accept run-time expressions. If you want to prevent esbuild from trying to bundle these imports, you should move the string concatenation expression outside of the require(...) or import(...). For example:
// This will be bundled
const json1 = await import('./data/' + kind + '.json')

// This will not be bundled
const path = './data/' + kind + '.json'
const json2 = await import(path)

Note that using this feature means esbuild will potentially do a lot of file system I/O to find all possible files that might match the pattern. This is by design, and is not a bug. If this is a concern, I recommend either avoiding the /**/ pattern (e.g. by not putting a / before a wildcard) or using this feature only in directory subtrees which do not have many files that don't match the pattern (e.g. making a subdirectory for your JSON files and explicitly including that subdirectory in the pattern).

Path aliases in tsconfig.json no longer count as packages (#2792, #3003, #3160, #3238)
Setting --packages=external tells esbuild to make all import paths external when they look like a package path. For example, an import of ./foo/bar is not a package path and won't be external while an import of foo/bar is a package path and will be external. However, the paths field in tsconfig.json allows you to create import paths that look like package paths but that do not resolve to packages. People do not want these paths to count as package paths. So with this release, the behavior of --packages=external has been changed to happen after the tsconfig.json path remapping step.

Use the local-css loader for .module.css files by default (#20)
With this release the css loader is still used for .css files except that .module.css files now use the local-css loader. This is a common convention in the web development community. If you need .module.css files to use the css loader instead, then you can override this behavior with --loader:.module.css=css.

v0.18.20
Compare Source

Support advanced CSS @import rules (#953, #3137)
CSS @import statements have been extended to allow additional trailing tokens after the import path. These tokens sort of make the imported file behave as if it were wrapped in a @layer, @supports, and/or @media rule. Here are some examples:
@import url(foo.css);
@import url(foo.css) layer;
@import url(foo.css) layer(bar);
@import url(foo.css) layer(bar) supports(display: flex);
@import url(foo.css) layer(bar) supports(display: flex) print;
@import url(foo.css) layer(bar) print;
@import url(foo.css) supports(display: flex);
@import url(foo.css) supports(display: flex) print;
@import url(foo.css) print;

You can read more about this advanced syntax here. With this release, esbuild will now bundle @import rules with these trailing tokens and will wrap the imported files in the corresponding rules. Note that this now means a given imported file can potentially appear in multiple places in the bundle. However, esbuild will still only load it once (e.g. on-load plugins will only run once per file, not once per import).

v0.18.19
Compare Source

Implement composes from CSS modules (#20)
This release implements the composes annotation from the CSS modules specification. It provides a way for class selectors to reference other class selectors (assuming you are using the local-css loader). And with the from syntax, this can even work with local names across CSS files. For example:
// app.js
import { submit } from './style.css'
const div = document.createElement('div')
div.className = submit
document.body.appendChild(div)

/* style.css */
.button {
  composes: pulse from "anim.css";
  display: inline-block;
}
.submit {
  composes: button;
  font-weight: bold;
}

/* anim.css */
@keyframes pulse {
  from, to { opacity: 1 }
  50% { opacity: 0.5 }
}
.pulse {
  animation: 2s ease-in-out infinite pulse;
}

Bundling this with esbuild using --bundle --outdir=dist --loader:.css=local-css now gives the following:
(() => {
  // style.css
  var submit = "anim_pulse style_button style_submit";

  // app.js
  var div = document.createElement("div");
  div.className = submit;
  document.body.appendChild(div);
})();

/* anim.css */
@keyframes anim_pulse {
  from, to {
    opacity: 1;
  }
  50% {
    opacity: 0.5;
  }
}
.anim_pulse {
  animation: 2s ease-in-out infinite anim_pulse;
}

/* style.css */
.style_button {
  display: inline-block;
}
.style_submit {
  font-weight: bold;
}

Import paths in the composes: ... from syntax are resolved using the new composes-from import kind, which can be intercepted by plugins during import path resolution when bundling is enabled.
Note that the order in which composed CSS classes from separate files appear in the bundled output file is deliberately undefined by design (see the specification for details). You are not supposed to declare the same CSS property in two separate class selectors and then compose them together. You are only supposed to compose CSS class selectors that declare non-overlapping CSS properties.
Issue #20 (the issue tracking CSS modules) is esbuild's most-upvoted issue! With this change, I now consider esbuild's implementation of CSS modules to be complete. There are still improvements to make and there may also be bugs with the current implementation, but these can be tracked in separate issues.

Fix non-determinism with tsconfig.json and symlinks (#3284)
This release fixes an issue that could cause esbuild to sometimes emit incorrect build output in cases where a file under the effect of tsconfig.json is inconsistently referenced through a symlink. It can happen when using npm link to create a symlink within node_modules to an unpublished package. The build result was non-deterministic because esbuild runs module resolution in parallel and the result of the tsconfig.json lookup depended on whether the import through the symlink or not through the symlink was resolved first. This problem was fixed by moving the realpath operation before the tsconfig.json lookup.

Add a hash property to output files (#3084, #3293)
As a convenience, every output file in esbuild's API now includes a hash property that is a hash of the contents field. This is the hash that's used internally by esbuild to detect changes between builds for esbuild's live-reload feature. You may also use it to detect changes between your own builds if its properties are sufficient for your use case.
This feature has been added directly to output file objects since it's just a hash of the contents field, so it makes conceptual sense to store it in the same location. Another benefit of putting it there instead of including it as a part of the watch mode API is that it can be used without watch mode enabled. You can use it to compare the output of two independent builds that were done at different times.
The hash algorithm (currently XXH64) is implementation-dependent and may be changed at any time in between esbuild versions. If you don't like esbuild's choice of hash algorithm then you are welcome to hash the contents yourself instead. As with any hash algorithm, note that while two different hashes mean that the contents are different, two equal hashes do not necessarily mean that the contents are equal. You may still want to compare the contents in addition to the hashes to detect with certainty when output files have been changed.

Avoid generating duplicate prefixed declarations in CSS (#3292)
There was a request for esbuild's CSS prefixer to avoid generating a prefixed declaration if a declaration by that name is already present in the same rule block. So with this release, esbuild will now avoid doing this:
/* Original code */
body {
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}

/* Old output (with --target=safari12) */
body {
  -webkit-backdrop-filter: blur(30px);
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}

/* New output (with --target=safari12) */
body {
  backdrop-filter: blur(30px);
  -webkit-backdrop-filter: blur(45px);
}

This can result in a visual difference in certain cases (for example if the browser understands blur(30px) but not blur(45px), it will be able to fall back to blur(30px)). But this change means esbuild now matches the behavior of Autoprefixer which is probably a good representation of how people expect this feature to work.

v0.18.18
Compare Source

Fix asset references with the --line-limit flag (#3286)
The recently-released --line-limit flag tells esbuild to terminate long lines after they pass this length limit. This includes automatically wrapping long strings across multiple lines using escaped newline syntax. However, using this could cause esbuild to generate incorrect code for references from generated output files to assets in the bundle (i.e. files loaded with the file or copy loaders). This is because esbuild implements asset references internally using find-and-replace with a randomly-generated string, but the find operation fails if the string is split by an escaped newline due to line wrapping. This release fixes the problem by not wrapping these strings. This issue affected asset references in both JS and CSS files.

Support local names in CSS for @keyframe, @counter-style, and @container (#20)
This release extends support for local names in CSS files loaded with the local-css loader to cover the @keyframe, @counter-style, and @container rules (and also animation, list-style, and container declarations). Here's an example:
@keyframes pulse {
  from, to { opacity: 1 }
  50% { opacity: 0.5 }
}
@counter-style moon {
  system: cyclic;
  symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@container squish {
  li { float: left }
}
ul {
  animation: 2s ease-in-out infinite pulse;
  list-style: inside moon;
  container: squish / size;
}

With the local-css loader enabled, that CSS will be turned into something like this (with the local name mapping exposed to JS):
@keyframes stdin_pulse {
  from, to {
    opacity: 1;
  }
  50% {
    opacity: 0.5;
  }
}
@counter-style stdin_moon {
  system: cyclic;
  symbols: 🌕 🌖 🌗 🌘 🌑 🌒 🌓 🌔;
}
@container stdin_squish {
  li {
    float: left;
  }
}
ul {
  animation: 2s ease-in-out infinite stdin_pulse;
  list-style: inside stdin_moon;
  container: stdin_squish / size;
}

If you want to use a global name within a file loaded with the local-css loader, you can use a :global selector to do that:
div {
  /* All symbols are global inside this scope (i.e.
   * "pulse", "moon", and "squish" are global below) */
  :global {
    animation: 2s ease-in-out infinite pulse;
    list-style: inside moon;
    container: squish / size;
  }
}

If you want to use @keyframes, @counter-style, or @container with a global name, make sure it's in a file that uses the css or global-css loader instead of the local-css loader. For example, you can configure --loader:.module.css=local-css so that the local-css loader only applies to *.module.css files.

Support strings as keyframe animation names in CSS (#2555)
With this release, esbuild will now parse animation names that are specified as strings and will convert them to identifiers. The CSS specification allows animation names to be specified using either identifiers or strings but Chrome only understands identifiers, so esbuild will now always convert string names to identifier names for Chrome compatibility:
/* Original code */
@keyframes "hide menu" {
  from { opacity: 1 }
  to { opacity: 0 }
}
menu.hide {
  animation: 0.5s ease-in-out "hide menu";
}

/* Old output */
@keyframes "hide menu" { from { opacity: 1 } to { opacity: 0 } }
menu.hide {
  animation: 0.5s ease-in-out "hide menu";
}

/* New output */
@keyframes hide\ menu {
  from {
    opacity: 1;
  }
  to {
    opacity: 0;
  }
}
menu.hide {
  animation: 0.5s ease-in-out hide\ menu;
}

v0.18.17
Compare Source

Support An+B syntax and :nth-*() pseudo-classes in CSS
This adds support for the :nth-child(), :nth-last-child(), :nth-of-type(), and :nth-last-of-type() pseudo-classes to esbuild, which has the following consequences:

The An+B syntax is now parsed, so parse errors are now reported
An+B values inside these pseudo-classes are now pretty-printed (e.g. a leading + will be stripped because it's not in the AST)
When minification is enabled, An+B values are reduced to equivalent but shorter forms (e.g. 2n+0 => 2n, 2n+1 => odd)
Local CSS names in an of clause are now detected (e.g. in :nth-child(2n of :local(.foo)) the name foo is now renamed)

/* Original code */
.foo:nth-child(+2n+1 of :local(.bar)) {
  color: red;
}

/* Old output (with --loader=local-css) */
.stdin_foo:nth-child(+2n + 1 of :local(.bar)) {
  color: red;
}

/* New output (with --loader=local-css) */
.stdin_foo:nth-child(2n+1 of .stdin_bar) {
  color: red;
}

Adjust CSS nesting parser for IE7 hacks (#3272)
This fixes a regression with esbuild's treatment of IE7 hacks in CSS. CSS nesting allows selectors to be used where declarations are expected. There's an IE7 hack where prefixing a declaration with a * causes that declaration to only be applied in IE7 due to a bug in IE7's CSS parser. However, it's valid for nested CSS selectors to start with *. So esbuild was incorrectly parsing these declarations and anything following it up until the next { as a selector for a nested CSS rule. This release changes esbuild's parser to terminate the parsing of selectors for nested CSS rules when a ; is encountered to fix this edge case:
/* Original code */
.item {
  *width: 100%;
  height: 1px;
}

/* Old output */
.item {
  *width: 100%; height: 1px; {
  }
}

/* New output */
.item {
  *width: 100%;
  height: 1px;
}

Note that the syntax for CSS nesting is about to change again, so esbuild's CSS parser may still not be completely accurate with how browsers do and/or will interpret CSS nesting syntax. Expect additional updates to esbuild's CSS parser in the future to deal with upcoming CSS specification changes.

Adjust esbuild's warning about undefined imports for TypeScript import equals declarations (#3271)
In JavaScript, accessing a missing property on an import namespace object is supposed to result in a value of undefined at run-time instead of an error at compile-time. This is something that esbuild warns you about by default because doing this can indicate a bug with your code. For example:
// app.js
import * as styles from './styles'
console.log(styles.buton)

// styles.js
export let button = {}

If you bundle app.js with esbuild you will get this:
▲ [WARNING] Import "buton" will always be undefined because there is no matching export in "styles.js" [import-is-undefined]

    app.js:2:19:
      2 │ console.log(styles.buton)
        │                    ~~~~~
        ╵                    button

  Did you mean to import "button" instead?

    styles.js:1:11:
      1 │ export let button = {}
        ╵            ~~~~~~

However, there is TypeScript-only syntax for import equals declarations that can represent either a type import (which esbuild should ignore) or a value import (which esbuild should respect). Since esbuild doesn't have a type system, it tries to only respect import equals declarations that are actually used as values. Previously esbuild always generated this warning for unused imports referenced within import equals declarations even when the reference could be a type instead of a value. Starting with this release, esbuild will now only warn in this case if the import is actually used. Here is an example of some code that no longer causes an incorrect warning:
// app.ts
import * as styles from './styles'
import ButtonType = styles.Button

// styles.ts
export interface Button {}

v0.18.16
Compare Source

Fix a regression with whitespace inside :is() (#3265)
The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

v0.18.15
Compare Source

Add the --serve-fallback= option (#2904)
The web server built into esbuild serves the latest in-memory results of the configured build. If the requested path doesn't match any in-memory build result, esbuild also provides the --servedir= option to tell esbuild to serve the requested path from that directory instead. And if the requested path doesn't match either of those things, esbuild will either automatically generate a directory listing (for directories) or return a 404 error.
Starting with this release, that last step can now be replaced with telling esbuild to serve a specific HTML file using the --serve-fallback= option. This can be used to provide a "not found" page for missing URLs. It can also be used to implement a single-page app that mutates the current URL and therefore requires the single app entry point to be served when the page is loaded regardless of whatever the current URL is.

Use the tsconfig field in package.json during extends resolution (#3247)
This release adds a feature from TypeScript 3.2 where if a tsconfig.json file specifies a package name in the extends field and that package's package.json file has a tsconfig field, the contents of that field are used in the search for the base tsconfig.json file.

Implement CSS nesting without :is() when possible (#1945)
Previously esbuild would always produce a warning when transforming nested CSS for a browser that doesn't support the :is() pseudo-class. This was because the nesting transform needs to generate an :is() in some complex cases which means the transformed CSS would then not work in that browser. However, the CSS nesting transform can often be done without generating an :is(). So with this release, esbuild will no longer warn when targeting browsers that don't support :is() in the cases where an :is() isn't needed to represent the nested CSS.
In addition, esbuild's nested CSS transform has been updated to avoid generating an :is() in cases where an :is() is preferable but there's a longer alternative that is also equivalent. This update means esbuild can now generate a combinatorial explosion of CSS for complex CSS nesting syntax when targeting browsers that don't support :is(). This combinatorial explosion is necessary to accurately represent the original semantics. For example:
/* Original code */
.first,
.second,
.third {
  & > & {
    color: red;
  }
}

/* Old output (with --target=chrome80) */
:is(.first, .second, .third) > :is(.first, .second, .third) {
  color: red;
}

/* New output (with --target=chrome80) */
.first > .first,
.first > .second,
.first > .third,
.second > .first,
.second > .second,
.second > .third,
.third > .first,
.third > .second,
.third > .third {
  color: red;
}

This change means you can now use CSS nesting with esbuild when targeting an older browser that doesn't support :is(). You'll now only get a warning from esbuild if you use complex CSS nesting syntax that esbuild can't represent in that older browser without using :is(). There are two such cases:
/* Case 1 */
a b {
  .foo & {
    color: red;
  }
}

/* Case 2 */
a {
  > b& {
    color: red;
  }
}

These two cases still need to use :is(), both for different reasons, and cannot be used when targeting an older browser that doesn't support :is():
/* Case 1 */
.foo :is(a b) {
  color: red;
}

/* Case 2 */
a > a:is(b) {
  color: red;
}

Automatically lower inset in CSS for older browsers
With this release, esbuild will now automatically expand the inset property to the top, right, bottom, and left properties when esbuild's target is set to a browser that doesn't support inset:
/* Original code */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* Old output (with --target=chrome80) */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* New output (with --target=chrome80) */
.app {
  position: absolute;
  top: 10px;
  right: 20px;
  bottom: 10px;
  left: 20px;
}

Add support for the new @starting-style CSS rule (#3249)
This at rule allow authors to start CSS transitions on first style update. That is, you can now make the transition take effect when the display property changes from none to block.
/* Original code */
@starting-style {
  h1 {
    background-color: transparent;
  }
}

/* Output */
@starting-style{h1{background-color:transparent}}

This was contributed by @yisibl.

v0.18.14
Compare Source

Implement local CSS names (#20)
This release introduces two new loaders called global-css and local-css and two new pseudo-class selectors :local() and :global(). This is a partial implementation of the popular CSS modules approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to something completely different and now CSS modules is an overloaded term.
Here's how this new local CSS name feature works with esbuild:

Identifiers that look like .className and #idName are global with the global-css loader and local with the local-css loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier .button, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions.

It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example:
// app.js
import { outerShell } from './app.css'
const div = document.createElement('div')
div.className = outerShell
document.body.appendChild(div)

/* app.css */
.outerShell {
  position: absolute;
  inset: 0;
}

When you bundle this with esbuild app.js --bundle --loader:.css=local-css --outdir=out you'll now get this (notice how the local CSS name outerShell has been renamed):
// out/app.js
(() => {
  // app.css
  var outerShell = "app_outerShell";

  // app.js
  var div = document.createElement("div");
  div.className = outerShell;
  document.body.appendChild(div);
})();

/* out/app.css */
.app_outerShell {
  position: absolute;
  inset: 0;
}

This feature only makes sense to use when bundling is enabled both because your code needs to import the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions.

If you are in a global CSS file (with the global-css loader) you can create a local name using :local(), and if you are in a local CSS file (with the local-css loader) you can create a global name with :global(). So the choice of the global-css loader vs. the local-css loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example:
:local(.button) {
  color: red;
}
:global(.button) {
  color: blue;
}

Processing this CSS file with esbuild with either the global-css or local-css loader will result in something like this:
.stdin_button {
  color: red;
}
.button {
  color: blue;
}

The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an import statement in JS that is bundled with esbuild, as demonstrated above. For example, when --minify is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS).

You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass --loader:.css=global-css and --loader:.module.css=local-css to esbuild so that .css files still use global names by default but .module.css files use local names by default.

Keep in mind that the css loader is different than the global-css loader. The :local and :global annotations are not enabled with the css loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since the css loader is currently the default for CSS files). The :local and :global syntax may be enabled by default in a future release.

Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement:

The composes pragma
Tree shaking for unused local CSS
Local names for keyframe animations, grid lines, @container, @counter-style, etc.

Issue #20 (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction.

Parse :is, :has, :not, and :where in CSS
With this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example:
/* Original code */
div {
  :where(.foo&) {
    color: red;
  }
}

/* Old output (with --target=chrome90) */
:where(.foo:is(div)) {
  color: red;
}

/* New output (with --target=chrome90) */
:where(div.foo) {
  color: red;
}

v0.18.13
Compare Source

Add the --drop-labels= option (#2398)
If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the --define: flag along with a specially-named global variable. For example, consider the following code:
function main() {
  DEV && doAnExpensiveCheck()
}

You can build this for development and production like this:

Development: esbuild --define:DEV=true
Production: esbuild --define:DEV=false

One drawback of this approach is that the resulting code crashes if you don't provide a value for DEV with --define:. In practice this isn't that big of a problem, and there are also various ways to work around this.
However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the --drop-labels= flag implements. For example, consider the following code:
function main() {
  DEV: doAnExpensiveCheck()
}

With this release, you can now build this for development and production like this:

Development: esbuild
Production: esbuild --drop-labels=DEV

This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The --drop-labels= flag takes comma-separated list of multiple label names to drop.

Avoid causing unhandledRejection during shutdown (#3219)
All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if SIGINT is sent to the parent node process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a custom SIGINT handler that extends the lifetime of the node process without esbuild's internals causing an early exit due to an unhandled promise rejection.

Update browser compatibility table scripts
The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:

Converted from JavaScript to TypeScript
Fixed some bugs that resulted in small changes to the table
Added caniuse-lite and @mdn/browser-compat-data as new data sources (replacing manually-copied information)

This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:

JS table changes
CSS table changes

v0.18.12
Compare Source

Fix a panic with const enum inside parentheses (#3205)
This release fixes an edge case where esbuild could potentially panic if a TypeScript const enum statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:
(() => {
  const enum E { a };
  () => E.a
})

Allow a newline in the middle of TypeScript export type statement (#3225)
Previously esbuild incorrectly rejected the following valid TypeScript code:
export type
{ T };

export type
* as foo from 'bar';

Code that uses a newline after export type is now allowed starting with this release.

Fix cross-module inlining of string enums (#3210)
A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.

Rewrite .js to .ts inside packages with exports (#3201)
Packages with the exports field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importing foo/bar to get foo/bar.js). And TypeScript has behavior where you can import a non-existent .js file and you will get the .ts file instead. Previously the presence of the exports field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite .js to .ts even inside packages with exports.

Fix a redirect edge case in esbuild's development server (#3208)
The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting /about redirects to /about/ if /about/index.html would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting //about redirected to //about/ which the browser turns into http://about/. This release fixes the bug by canonicalizing the URL path when doing this redirect.

v0.18.11
Compare Source

Fix a TypeScript code generation edge case (#3199)
This release fixes a regression in version 0.18.4 where using a TypeScript namespace that exports a class declaration combined with --keep-names and a --target of es2021 or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to X2._Y vs. X2.Y):
// Original code

// Old output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2._Y = _Y;
})(X || (X = {}));

// New output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2.Y = _Y;
})(X || (X = {}));

v0.18.10
Compare Source

Fix a tree-shaking bug that removed side effects (#3195)
This fixes a regression in version 0.18.4 where combining --minify-syntax with --keep-names could cause expressions with side effects after a function declaration to be considered side-effect free for tree shaking purposes. The reason was because --keep-names generates an expression statement containing a call to a helper function after the function declaration with a special flag that makes the function call able to be tree shaken, and then --minify-syntax could potentially merge that expression statement with following expressions without clearing the flag. This release fixes the bug by clearing the flag when merging expression statements together.

Fix an incorrect warning about CSS nesting (#3197)
A warning is currently generated when transforming nested CSS to a browser that doesn't support :is() because transformed nested CSS may need to use that feature to represent nesting. This was previously always triggered when an at-rule was encountered in a declaration context. Typically the only case you would encounter this is when using CSS nesting within a selector rule. However, there is a case where that's not true: when using a margin at-rule such as @top-left within @page. This release avoids incorrectly generating a warning in this case by checking that the at-rule is within a selector rule before generating a warning.

v0.18.9
Compare Source

Fix await using declarations inside async generator functions
I forgot about the new await using declarations when implementing lowering for async generator functions in the previous release. This change fixes the transformation of await using declarations when they are inside lowered async generator functions:
// Original code
async function* foo() {
  await using x = await y
}

// Old output (with --supported:async-generator=false)
function foo() {
  return __asyncGenerator(this, null, function* () {
    await using x = yield new __await(y);
  });
}

// New output (with --supported:async-generator=false)
function foo() {
  return __asyncGenerator(this, null, function* () {
    var _stack = [];
    try {
      const x = __using(_stack, yield new __await(y), true);
    } catch (_) {
      var _error = _, _hasError = true;
    } finally {
      var _promise = __callDispose(_stack, _error, _hasError);
      _promise && (yield new __await(_promise));
    }
  });
}

Insert some prefixed CSS properties when appropriate (#3122)
With this release, esbuild will now insert prefixed CSS properties in certain cases when the target setting includes browsers that require a certain prefix. This is currently done for the following properties:

appearance: *; => -webkit-appearance: *; -moz-appearance: *;
backdrop-filter: *; => -webkit-backdrop-filter: *;
background-clip: text => -webkit-background-clip: text;
box-decoration-break: *; => -webkit-box-decoration-break: *;
clip-path: *; => -webkit-clip-path: *;
font-kerning: *; => -webkit-font-kerning: *;
hyphens: *; => -webkit-hyphens: *;
initial-letter: *; => -webkit-initial-letter: *;
mask-image: *; => -webkit-mask-image: *;
mask-origin: *; => -webkit-mask-origin: *;
mask-position: *; => -webkit-mask-position: *;
mask-repeat: *; => -webkit-mask-repeat: *;
mask-size: *; => -webkit-mask-size: *;
position: sticky; => position: -webkit-sticky;
print-color-adjust: *; => -webkit-print-color-adjust: *;
tab-size: *; => -moz-tab-size: *; -o-tab-size: *;
text-decoration-color: *; => -webkit-text-decoration-color: *; -moz-text-decoration-color: *;
text-decoration-line: *; => -webkit-text-decoration-line: *; -moz-text-decoration-line: *;
text-decoration-skip: *; => -webkit-text-decoration-skip: *;
text-emphasis-color: *; => -webkit-text-emphasis-color: *;
text-emphasis-position: *; => -webkit-text-emphasis-position: *;
text-emphasis-style: *; => -webkit-text-emphasis-style: *;
text-orientation: *; => -webkit-text-orientation: *;
text-size-adjust: *; => -webkit-text-size-adjust: *; -ms-text-size-adjust: *;
user-select: *; => -webkit-user-select: *; -moz-user-select: *; -ms-user-select: *;

Here is an example:
/* Original code */
div {
  mask-image: url(x.png);
}

/* Old output (with --target=chrome99) */
div {
  mask-image: url(x.png);
}

/* New output (with --target=chrome99) */
div {
  -webkit-mask-image: url(x.png);
  mask-image: url(x.png);
}

Browser compatibility data was sourced from the tables on https://caniuse.com. Support for more CSS properties can be added in the future as appropriate.

Fix an obscure identifier minification bug (#2809)
Function declarations in nested scopes behave differently depending on whether or not `"use str

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: package-lock.json
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving<EMAIL_ADDRESS>npm WARN Found<EMAIL_ADDRESS>npm WARN node_modules/esbuild
npm WARN   dev<EMAIL_ADDRESS>from the root project
npm WARN   4 more (@nx/esbuild, @yarnpkg/esbuild-plugin-pnp, ...)
npm WARN
npm WARN Could not resolve dependency:
npm WARN peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm WARN node_modules/@nx/esbuild
npm WARN   dev<EMAIL_ADDRESS>from the root project
npm WARN   1 more (@nrwl/esbuild)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@yarnpkg/esbuild-plugin-pnp
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@storybook/builder-manager
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!       node_modules/@storybook/core-server
npm ERR!         dev<EMAIL_ADDRESS>from the root project
npm ERR!   2 more (bundle-require, esbuild-register)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/@nx/esbuild
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nrwl/esbuild
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/esbuild
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@nx/esbuild
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!     node_modules/@nrwl/esbuild
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /var/folders/6v/c06plt297s75l4yjpgd_zfvr0000gn/T/renovate/cache/others/npm/_logs/2023-09-08T07_59_09_800Z-eresolve-report.txt

npm ERR!


no command in command palette when using notebooks

opened a jupyter notebook in python language in vscode, want to sort import, but there is no such command in command palette

I can confirm this work flawlessly in normal python file
vscode version: 1.79.0-insider (user setup)
isort extension version: v2022.8.0

This currently is not supported in notebooks. Waiting on this to be implemented in an underlying library: https://github.com/openlawlibrary/pygls/issues/311

This currently is not supported in notebooks. Waiting on this to be implemented in an underlying library: openlawlibrary/pygls#311

Actually this used to work fine in v2022.8.0, it's only as of 2023.10.0 that this doesn't work anymore! So this is a bug and not a feature request...

There are two parts to this bug:

The Cell import sorting stopped showing up is a regression.
The full notebook support is still the one I mentioned in my comment above.

@torext thanks for reporting the issue. the fix should be in pre-release.

Thanks, will install pre-release!
On Wed, 12 Jul 2023, 21:53 Karthik Nadig, @.***> wrote:

There are two parts to this bug:

The Cell import sorting stopped showing up is a regression.
The full notebook support is still the one I mentioned in my
comment above.

@torext https://github.com/torext thanks for reporting the issue. the
fix should be in pre-release.
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-isort/issues/281#issuecomment-1633121158,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACMMLW2IWBKTVVNU2L6ZRBLXP36DRANCNFSM6AAAAAAYIYSNXA
.
You are receiving this because you were mentioned.Message ID:
@.***>

The Cell import sorting stopped showing up is a regression.

I've installed pre-release version v2023.11.12711013, but I can't find the sort import command in command palette.

@TTTPOB The command is Organize Imports

Previously, python extension contributed a custom command Sort Imports. This did not integrate with VS Code's internal mechanism to fix import organization issues. The isort extension integrates with the Organize Import feature.

@TTTPOB The command is Organize Imports

Thank you! I didn't know that.


⚠ Bofrost.fr has degraded performance

In a7114a7, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Bofrost.fr performance has improved in e12041d after 6 minutes.


PGVector#update_texts

This commit implements (tentative) pgvector support for upsert functionality, which as far as I can understand is all that is required to make it work correctly with the Rails integration.
This is open to discussion and modification - please let me know if there's anything to improve here.

@dcluna Please run standardrb --fix and commit. Thank you for your contribution here!

@andreibondarev Also, not sure if CI did not trigger due to me force-pushing the branch or if it's actually manually triggered by you - in any case, could you please make it run so this PR can be merged?

@dcluna No, at least at add_texts() the IDs are not required because if you don't pass IDs they should be created automatically.


Serious error

TES3Merge.log

I have what appears to be the same issue
TES3Merge.log

Similar issue
TES3Merge.log

Same error message
TES3Merge.log

This should be fixed in v0.8. If not, please post an updated TES3Merge.log.


Update unsafe.txt

Hello, thanks for the PR! Everything looks good to merge.

the video streaming sites too? and seo spam
I mean its not wrong, but unnecessary for a gaming wiki

We do have a fair bit of content which are loosely related to gaming piracy, but other than that, this should be fine.
Also, I did mention in the FMHY to-do channel to PR if anyone wants to, since we had forked this from rust's gist but didn't progress much. It can come useful in the future if we give it some care.


docs: updated cloudywithachanceofbigdata.com blog showcase

Motivation
updated showcase item metadata for cloudywithachanceofbigdata.com

added a tag as a personal blog; and
updated screenshot to remove browser frame and scroll bar

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
N/A
Related PRs
N/A

thanks ;)


Implement basic tree functions

Validated

[x] hasChildren
[x] path
[x] length -> breadth
[x] level
[x] depth

Considering
*With functions that accept an iteratee function.

[x] cloneWith
[ ] deepEqualWith
[ ] equalWith
[ ] pathWith

*With will accept an optional function as last parameter. For now it avoids cluttering the api. Later we might separate both implementations for clarity/performance reasons.


Flake node announcement threadsafe

Coverage decreased (-0.06%) to 73.799% when pulling e34d34b5f2e0822ca35d40eef35d92d3251702cc on halseth:flake-node-announcement-threadsafe into f13c81eb6a82f2489325939cc5df047b779d4477 on lightningnetwork:master.


Replace private and deprecated _lookupFactory with public & performant factoryFor

No API surface has changed. _factoryFor will be removed in 2.13.

@cibernox thank you for this. Can you move the code to a util file? Something like:
// addon/utils/lookup-class.js
export default function lookupClass(owner, type) {
  let klass;
  if (owner.factoryFor) {
        let maybeKlass = owner.factoryFor(type);
        klass = maybeErrorMessages && maybeErrorMessages.class;
      } else {
        klass = owner._lookupFactory(type);
      }
return klass;
}

sure

@cibernox thanks! Also, is there a need to fallback to _lookupFactory? Shouldnt the getOwner polyfill take care of that?

@offirgolan It is needed. getOwner gives you an applicationInstance, but ApplicationInstance#factoryFor was added in 2.12.

@offirgolan I added it in -private, because it's for internal usage only.

@cibernox released with v3.2.2. Thanks again for the help 😸


freebsd: 14.0 -> 14.1

Description of changes
version bump.
Notable new features:

new version of libcxxrt (the old version was incompatible with the version of libcxx that is already getting used for cross builds on the staging branch)
llvm 18
kldxref now builds with compat, allowing us to run during cross builds
rc package now puts its services into a separate output, since more of them mysteriously started "working" when I booted nixbsd but the environment was not set up to handle them
mount and fsck (new) packages now provide their helper binaries as part of the base derivation, with feature flags

FreeBSD changelog: https://www.freebsd.org/releases/14.1R/relnotes/

Built on platform(s)

[x] x86_64-linux (cross)
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin
[x] x86_64-freebsd

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[x] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Suggestions should be applied. I split fsck and mount, which means a few duplicate object compiles but not many.


debugger truncates strings

This issue was originally filed by<EMAIL_ADDRESS>
What steps will reproduce the problem?

Create a class with a reasonably long return value from the toString() method
Insert a breakpoint in the editor at some point where an instance of the object is in scope
Inspect the instance in the debugger.

What is the expected output? What do you see instead?
Expected: The full dprint of the object
{Intersection (edge1:0)&(edge2:0)=(0.0, 0.0, NaN), Intersection (edge1:5)&(edge2:5)=(40.0, 40.0, NaN), Intersection (edge1:0)&(edge2:9)=(0.0, 0.0, NaN), Intersection (edge1:1)&(edge3:0)=(20.0, 5.0, NaN), Intersection (edge1:2)&(edge3:0)=(20.0, 5.0, Na
<more intersections follow this>
Observed:
A truncated dprint:
{Intersection (edge1:0)&(edge2:0)=(0.0, 0.0, NaN), Intersection (edge1:5)&(edge2:5)=(40.0, 40.0, NaN), Intersection (edge1:0)&(edge2:9)=(0.0, 0.0, NaN), Intersection (edge1:1)&(edge3:0)=(20.0, 5.0, NaN), Intersection (edge1:2)&(edge3:0)=(20.0, 5.0, N...
Please provide any additional information below.
Due to the length of the output, this information is difficult to inspect manually, but it could be copied out into a separate window and formatted. It can't, however be copied out and pasted if the string is truncated. In some cases (eg. Lists) the instance can be drilled into to find the data you're looking for. In others (eg. Hashsets) there are too many levels to look for each item, and the tree collapses and you have to drill down every time the object you'd like to inspect goes out of scope, (eg. the object was created in a loop).
The only option is to insert a print statement and use the output of that to obtain the information, which might
a) not actually be the information you're looking for
b) Require you to restart the debugger to load the new code (with prints) and proceed back to where you left off.
This is obviously intentional functionality, but I'd like to know why the debugger is allowed to throw away potentially useful debugging information.

Legacy debugging protocol removed in 6249c2bcf3cb4a2241dd27caf087f07ea05147b3


Show tooltip if user has the bet size to odds display set too high and odds for that outcome are hidden due to being out of range

Decrease ‘Bet Size to Odds Display’ in settings to show available odds

went with titles after exploring using real tooltips, it's slightly off mock but doesn't severely reduce our performance for changing odds or bet sizes (would take 3-4 seconds to update with just a freeze up on the UI based on the user's experience) so I abandoned that idea for now and went with a compromise that gives some hint instead of no hint at all.


Problems with syncing files having named and default exports

Describe the bug
sb-mig have problems with files that are using named and defualt exports
file.sb.cjs
exports.BPWrapperLayoutSchema = BPWrapperLayoutSchema;
exports["default"] = TextSchema;

file.sb.js
export const BPWrapperLayoutSchema = ...
export { TextSchema as default };

Expected behavior
should sync without problems files that exports both named and defaults export, and basically should select only default (becasue that is the content of actual schema)

fixed with: https://github.com/sb-mig/sb-mig/commit/240d8184b6d32c73b17cd6268cb53fb33bf42c0d


Throws error when button is inside the form

When applying ladda to the button which is within the form then its throws error
TypeError: r[0].querySelector is not a function
at link (http://localhost/loopin/bower_components/angular-ladda/dist/angular-ladda.min.js:2:880)
at ka (http://localhost/loopin/bower_components/angular/angular.min.js:79:16)
at u (http://localhost/loopin/bower_components/angular/angular.min.js:66:326)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:136)
at u (http://localhost/loopin/bower_components/angular/angular.min.js:66:270)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:136)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:153)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:153)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:153)
at g (http://localhost/loopin/bower_components/angular/angular.min.js:58:153)
When button is outside the form everything works fine.

Can you tell me browser name and version?


Fix RangeSlider.rangeChange emit type bug

Description
This fixes the TypeError that Juan found and mentioned on zulip.  I'm also taking the opportunity to normalize the API within the class (I regret making .range a property when .values() is a method).  Since it's a QWidget, I'm making it a getter method rather than a prop.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)

This looks good to me, but I will let @jni test as I was unable to reproduce the original bug

I can confirm that this works for me. Still unable to reproduce in a test. It looks like a PyQt5 vs PySide2 thing:
jni@jni-x1c6 Wed Jan 08 14:07
 ~/projects/napari (master)
 $ QT_API=pyside2 python examples/add_image.py
(f7)
jni@jni-x1c6 Wed Jan 08 14:07
 ~/projects/napari (master)
 $ python examples/add_image.py
Traceback (most recent call last):
  File "examples/add_image.py", line 11, in <module>
    viewer = napari.view_image(data.astronaut(), rgb=True)
  File "/home/jni/projects/napari/napari/view_layers.py", line 137, in view_image
    path=path,
  File "/home/jni/projects/napari/napari/components/viewer_model.py", line 521, in add_image
    self.add_layer(layer)
  File "/home/jni/projects/napari/napari/components/viewer_model.py", line 386, in add_layer
    self.layers.append(layer)
  File "/home/jni/projects/napari/napari/utils/list/_model.py", line 56, in append
    self.events.added(item=object, index=len(self) - 1)
  File "/home/jni/projects/napari/napari/utils/event.py", line 508, in __call__
    self._invoke_callback(cb, event)
  File "/home/jni/projects/napari/napari/utils/event.py", line 529, in _invoke_callback
    cb_event=(cb, event),
  File "/home/jni/projects/napari/napari/utils/event.py", line 523, in _invoke_callback
    cb(event)
  File "/home/jni/projects/napari/napari/_qt/qt_controls.py", line 49, in _add
    controls = create_qt_controls(layer)
  File "/home/jni/projects/napari/napari/_qt/layers/util.py", line 34, in create_qt_controls
    controls = layer_to_controls[type(layer)](layer)
  File "/home/jni/projects/napari/napari/_qt/layers/qt_image_layer.py", line 9, in __init__
    super().__init__(layer)
  File "/home/jni/projects/napari/napari/_qt/layers/qt_image_base_layer.py", line 34, in __init__
    self.layer.contrast_limits, self.layer.contrast_limits_range
  File "/home/jni/projects/napari/napari/_qt/qt_range_slider.py", line 78, in __init__
    self.setRange((0, 100) if data_range is None else data_range)
  File "/home/jni/projects/napari/napari/_qt/qt_range_slider.py", line 96, in setRange
    self.rangeChanged.emit(values)
TypeError: QRangeSlider.rangeChanged[tuple].emit(): argument 1 has unexpected type 'list'
(f7)
jni@jni-x1c6 Wed Jan 08 14:07
 ~/projects/napari (master)
 $ napari --info
napari: 0.2.8+14.g89d2f125.dirty
Platform: Linux-4.15.0-29-generic-x86_64-with-debian-buster-sid
Python: 3.7.3 | packaged by conda-forge | (default, Jul  1 2019, 21:52:21)  [GCC 7.3.0]
Qt: 5.13.0
PyQt5: 5.13.1
VisPy: 0.6.4
NumPy: 1.17.0
SciPy: 1.3.1
scikit-image: 0.17.dev0
Dask: 2.5.2

GL version:  3.0 Mesa 19.0.8
MAX_TEXTURE_SIZE: 16384
(f7)
jni@jni-x1c6 Wed Jan 08 14:08
 ~/projects/napari (master)
 $ QT_API=pyside2 python examples/add_image.py
(f7)
jni@jni-x1c6 Wed Jan 08 14:08
 ~/projects/napari (master)
 $ QT_API=pyside2 napari --info
napari: 0.2.8+14.g89d2f125.dirty
Platform: Linux-4.15.0-29-generic-x86_64-with-debian-buster-sid
Python: 3.7.3 | packaged by conda-forge | (default, Jul  1 2019, 21:52:21)  [GCC 7.3.0]
Qt: 5.13.1
PySide2: 5.13.1
VisPy: 0.6.4
NumPy: 1.17.0
SciPy: 1.3.1
scikit-image: 0.17.dev0
Dask: 2.5.2

GL version:  3.0 Mesa 19.0.8
MAX_TEXTURE_SIZE: 16384

btw, link to the zulip discussion: https://napari.zulipchat.com/#narrow/stream/212875-general/topic/Range.20slider.20error
I'm merging now so that we don't have something critical holding up the release. Probably there are differences between Qt5 and qtbot that mean the error won't be triggered with qtbot. The medium-term solution is to get back to running our examples in testing. We should also test both PyQt5 and PySide2, not sure whether we are doing this currently.

Thanks @jni! We have an issue #768 for testing both and should make sure this gets covered then

ah, interesting... maybe that's another reason to try to get a CI pyqt test working on at least one OS... or are you saying that even if pyside2 is completely uninstalled, pytest/qtbot still won't catch it?

there's that issue!  I knew @kne42 opened that somewhere :)

correct, even after uninstalling PySide, I couldn't get this test to fail.

💻 🔨


Edge case "touch-and-remove" events

I would propose to include *Removed events for edge case "touch-and-remove".

Sorry, it is partially duplicates https://github.com/skmgoldin/tcr/pull/21

Thank you for this @hodkov
Related:
https://github.com/skmgoldin/tcr/issues/45
https://github.com/skmgoldin/tcr/pull/21/commits/a7c798d4d9c520f1fc9a2f957c0f8e9af1c59620

Resolved: cab98ed1f8fb9746dd4f1afb7149bbd86db0f6fe


Use Karma and webpack to test gringotts

Remove Grunt, RequireJS, and related dependencies
Use ES modules
Configure Karma and webpack
TODO: Add a release script and rebase to include
Eugene's recent changes

@bzalasky can we configure karma to use "dot" reporter in "development" mode, but the full reporter in "production" (travis) mode?
Also, can we rename those modes to just "dev" and "prod"? =)

I would suggest creating a folder templates/progress-dialog/ and put everything in there having partials on the same dir level as views.

@eugenet8k Regarding dev and prod, NODE_ENV will need to be production for React to switch to it's optimized build in prod.

That doesn't matter so much here, but I'm just in the habit I suppose.

@bzalasky if there is expectations on "production" to have as full word, I don't mind using "development" and "production" as is then.

@bzalasky what version of NodeJS we need to use to rely on package-log.json? If it's higher than 6.9.2 which is set in .nvmrc then we need to update the version in that file as well.

@eugenet8k i'm using 7.4.0, but it should work with LTS.

@bzalasky so, do you think we should update version in .nvmrc?

Will there be a way, to just build the project? I see now the build command actually triggers unit tests run. I am not sure if we even need to consider building as we are going to distribute gringotts in coffeescript format. In that case it's not clear to me the idea behind moving files into dist/ folder? Shouldn't we just publish npm package with root pointed to gringotts/src folder?

@bzalasky it seems somehow the file .nvmrc still has old version of node 6.9.2, where I guess we want it 8.4.0.


a --fast option for program command

if specified wont check flash is erased, won't verify, set max clockspeed? no printing to output, no error checking

no need. program already is fast as can be if options like --verify and --erase are not specified.


Add ngxs

Hi!
Thanks for opening this issue!
For some reason, I'm not really sure about adding this to the checklist. This is a library and I think we would like to keep this really focussed on angular core.
I know we added NGRX. And NGRX is also a library so it clashes with what I'm saying above. But for some reason, NGRX is kind of the de facto non official solution. So NGRX is kind of the exception here I would say.
Basically, what I'm saying is that I'm not sure NGXS should belong here as it is a library.

What do you think @d3lm.

I would agree that NGRX is more or less an exception and that I would not create categories per library. While NGRX is not officially a first class citizen of the Angular repo, it's very commonly used. I'd like to stick to NGRX here.
Maybe at some point we can think about making the checklist a little bit more sophisticated. For example having sub-categories. This would allow us to create a category such as State Management and have a sub-category for both NGRX and NGXS.
Just thinking out loud. But I don't want to make this too complex. It should stay simple because it was meant to be a tool that you can use to somewhat quickly check if you are on the right track or if there's anything you still need to work on. The more complexity we add to this app, the more time it takes to browse through the list. And the list is already naturally growing when items are being added.


Python Errors

Plugin doesn't function at all.
Installed using install.sh.
Tried both vanilla Arch and ChimeraOS.
Versions
Linux 6.6.3-arch1-1 (Arch Linux)
glibc 2.38-7
Python 3.11.6
Decky Loader 2.10.5
PowerControl 2.0.13
Device
Ayaneo Air Plus (6800U)
Logs
PowerControl Log: /tmp/PowerControl_py.log
[2023-11-30 22:55:05,367 | main.py:18:<module>] ERROR: name 'e' is not defined
[2023-11-30 22:55:05,367 | main.py:22:_main] INFO: PowerControl main.py
[2023-12-01 12:07:38,363 | main.py:39:get_cpuMaxNum] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:07:38,409 | main.py:46:get_tdpMax] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:07:38,415 | main.py:53:get_gpuFreqRange] ERROR: name 'gpuManager' is not defined
[2023-12-01 12:07:38,435 | main.py:104:get_fanMAXRPM] ERROR: name 'fanManager' is not defined
[2023-12-01 12:07:38,450 | main.py:111:get_fanIsAdapted] ERROR: name 'fanManager' is not defined
[2023-12-01 12:07:38,459 | main.py:66:get_language] ERROR: name 'sysInfoManager' is not defined
[2023-12-01 12:07:38,464 | main.py:118:set_fanAuto] ERROR: name 'fanManager' is not defined
[2023-12-01 12:07:38,466 | main.py:174:set_smt] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:07:38,467 | main.py:167:set_cpuOnline] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:07:38,467 | main.py:181:set_cpuBoost] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:07:38,467 | main.py:160:set_cpuTDP] ERROR: name 'cpuManager' is not defined

Decky Loader: systemctl status plugin_loader
Nov 30 22:55:05 ayaneo PluginLoader[1234]: 19:55:05 [INFO] Logging level: Info
Nov 30 22:55:05 ayaneo PluginLoader[1234]: 19:55:05 [INFO] Listening on <IP_ADDRESS>:33220
Nov 30 22:55:05 ayaneo PluginLoader[1202]: can't add watch for <ctypes.c_char_Array_46 object at 0x7fa1c38b9740>>
Nov 30 22:55:05 ayaneo PluginLoader[1238]: Logging to: "/tmp/powertools.log"
Nov 30 22:55:05 ayaneo PluginLoader[1238]: Starting back-end (powertools v1.4.0)
Nov 30 22:55:05 ayaneo PluginLoader[1238]: Current dir `/home/abdullah/homebrew/services`
Nov 30 22:55:15 ayaneo PluginLoader[1191]: [loader][INFO]: Hot reload enabled
Nov 30 22:55:36 ayaneo PluginLoader[1191]: [updater][INFO]: Updated remote version information
Dec 01 06:42:39 ayaneo PluginLoader[1191]: [updater][INFO]: Updated remote version information
Dec 01 12:07:32 ayaneo PluginLoader[1191]: [main][INFO]: Loading Decky frontend!

Is there any specific Python libraries or glibc version are required to make it work?

Same issue with Steam Deck.
Versions
Linux 6.1.52-valve9-1-neptune-61
Python 3.11.3
Decky Loader 2.10.5
PowerControl 2.0.13
Logs
PowerControl: /tmp/PowerControl_py.log
[2023-12-01 12:52:17,858 | main.py:18:<module>] ERROR: name 'e' is not defined
[2023-12-01 12:52:17,859 | main.py:22:_main] INFO: PowerControl main.py
[2023-12-01 12:52:58,674 | main.py:39:get_cpuMaxNum] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:58,776 | main.py:46:get_tdpMax] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:58,836 | main.py:53:get_gpuFreqRange] ERROR: name 'gpuManager' is not defined
[2023-12-01 12:52:58,898 | main.py:104:get_fanMAXRPM] ERROR: name 'fanManager' is not defined
[2023-12-01 12:52:58,951 | main.py:111:get_fanIsAdapted] ERROR: name 'fanManager' is not defined
[2023-12-01 12:52:58,972 | main.py:66:get_language] ERROR: name 'sysInfoManager' is not defined
[2023-12-01 12:52:58,985 | main.py:118:set_fanAuto] ERROR: name 'fanManager' is not defined
[2023-12-01 12:52:58,992 | main.py:174:set_smt] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:58,994 | main.py:167:set_cpuOnline] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:58,995 | main.py:181:set_cpuBoost] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:58,997 | main.py:132:set_gpuAuto] ERROR: name 'gpuManager' is not defined
[2023-12-01 12:52:59,540 | main.py:160:set_cpuTDP] ERROR: name 'cpuManager' is not defined
[2023-12-01 12:52:59,544 | main.py:160:set_cpuTDP] ERROR: name 'cpuManager' is not defined

Decky Loader: systemctl status plugin_loader
Dec 01 12:52:17 SteamDeck PluginLoader[11023]: [loader][INFO]: Loaded DeckSettings
Dec 01 12:52:17 SteamDeck PluginLoader[11069]: Logging to: "/tmp/powertools.log"
Dec 01 12:52:17 SteamDeck PluginLoader[11069]: Starting back-end (powertools v1.4.0)
Dec 01 12:52:17 SteamDeck PluginLoader[11069]: Current dir `/home/deck/homebrew/services`
Dec 01 12:52:17 SteamDeck sudo[11073]:     root : PWD=/home/deck/homebrew/services ; USER=root ; COMMAND=/usr/bin/sh /home/deck/homebrew/plugins/PowerControl/backend/sh_tools.sh get_cpuID
Dec 01 12:52:17 SteamDeck sudo[11073]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=0)
Dec 01 12:52:17 SteamDeck sudo[11073]: pam_unix(sudo:session): session closed for user root
Dec 01 12:52:27 SteamDeck PluginLoader[11023]: [loader][INFO]: Hot reload enabled
Dec 01 12:52:48 SteamDeck PluginLoader[11023]: [updater][INFO]: Updated remote version information
Dec 01 12:52:52 SteamDeck PluginLoader[11023]: [main][INFO]: Loading Decky frontend!

Try updating the the Decky loader to the prerelease version.

Using Decky Loader prerelease version.
Same issue:
[2023-12-10 14:04:35,167 | main.py:18:<module>] ERROR: name 'e' is not defined
[2023-12-10 14:04:35,167 | main.py:22:_main] INFO: PowerControl main.py
[2023-12-10 14:04:44,034 | main.py:39:get_cpuMaxNum] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,050 | main.py:46:get_tdpMax] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,107 | main.py:53:get_gpuFreqRange] ERROR: name 'gpuManager' is not defined
[2023-12-10 14:04:44,167 | main.py:104:get_fanMAXRPM] ERROR: name 'fanManager' is not defined
[2023-12-10 14:04:44,225 | main.py:111:get_fanIsAdapted] ERROR: name 'fanManager' is not defined
[2023-12-10 14:04:44,274 | main.py:66:get_language] ERROR: name 'sysInfoManager' is not defined
[2023-12-10 14:04:44,301 | main.py:118:set_fanAuto] ERROR: name 'fanManager' is not defined
[2023-12-10 14:04:44,310 | main.py:174:set_smt] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,312 | main.py:167:set_cpuOnline] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,314 | main.py:181:set_cpuBoost] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,315 | main.py:132:set_gpuAuto] ERROR: name 'gpuManager' is not defined
[2023-12-10 14:04:44,848 | main.py:160:set_cpuTDP] ERROR: name 'cpuManager' is not defined
[2023-12-10 14:04:44,850 | main.py:160:set_cpuTDP] ERROR: name 'cpuManager' is not defined

I have the same issue with the ROG Ally using ChimeraOS.
PowerControl_py.log

A strange issue. We haven't reproduced it here. Further investigation may be needed.

A strange issue. We haven't reproduced it here. Further investigation may be needed.

Looking at the code and comparing it with the log, I discovered that the issue with the code is in this line:
https://github.com/mengmeet/PowerControl/blob/cf4b74cc94378fc671bd9dd02b1cc0a3609389dd/backend/gpu.py#L293
It doesn't define the variable 'e'. I replaced it with except Exception as e: and it seems to work. However, when I reverted it, it messed up with the clocks, setting both the GPU and CPU cores to 0. This completely froze my Rog Ally. I had to activate the cores via SSH with the following commands:
echo 1 > /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu2/online
echo 1 > /sys/devices/system/cpu/cpu3/online

And now I receive in the log:
[2023-12-10 13:25:13,528 | gpu.py:290:fix_gpuFreqSlider] ERROR: [Errno 30] Read-only file system: '/usr/bin/steamos-polkit-helpers/steamos-priv-write'

But it doesn't seem to be a problem.
Now everything seems to be working fine.I will test more when I have time.

Check Plugin Compatibility:
Ensure that the plugin you're trying to use is compatible with the versions of the operating system, Python, and other relevant dependencies. Check the plugin documentation or repository for compatibility information.
Review Logs:
Examine the logs for any error messages or warnings that might provide clues about what's going wrong. You mentioned logs, but you didn't provide any content. Look for error messages or stack traces that indicate where the issue might be.
Verify Dependencies:
Confirm that all required dependencies for the plugin are installed and up-to-date. Sometimes, missing or outdated dependencies can cause issues.
Update Software:
Ensure that your system, Python, and other relevant software components are up-to-date. Outdated software may have compatibility issues with newer plugins.
Community Support:
Reach out to the community associated with the plugin or the platform you are using. Forums, GitHub issues, or community chat channels can be valuable resources for troubleshooting help.
Check Configuration:
Double-check the configuration settings for the plugin. Sometimes, misconfigurations can lead to unexpected behavior.
Reinstall the Plugin:
Try reinstalling the plugin. Remove the existing installation and install it again, following the installation instructions provided by the plugin developer.
Contact Plugin Developer:
If you've tried the above steps and the issue persists, consider reaching out to the developer or community associated with the plugin. Provide detailed information about the problem, including logs and any error messages you've encountered.


Clean split lazy

Sorry for this late response. I have been travelling some months.
This is basically the same as before - but the different color icon select divs are created lazily.
This solves loading all images on startup  - and reduces traffic overall.
Are you still interested in this approach in general?
Do you have other ideas, styling issues,...? Let me konw - I would be happy to contribute and make this work. I will try to add comments in the code this week.

Thanks 👍


Add ARO to the Java web app containerization and migration docs

Customers having Java workloalds potentially need to use this tool to migrate to Azure RedHat OpenShift aka ARO, a first-party managed OpenShift on Azure.

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

ID: 2029115a-26c2-06c0-6340-fa2d8e5afb33
Version Independent ID: 10746a0b-866a-1de9-df02-94b3a20baf97
Content: Azure App Containerization Java; Containerization and migration of Java web applications to Azure Kubernetes. - Azure Migrate
Content Source: articles/migrate/tutorial-app-containerization-java-kubernetes.md
Service: azure-migrate
GitHub Login: @rahugup
Microsoft Alias: rahugup

the tool wizard should propose both options to use ACR and ARO buil-in Registry (azure BLOB storage)

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@ezYakaEagle442 The capability to support migrations to ARO is in our roadmap. I would request you to get in touch with us to discuss more about your scenario by writing to<EMAIL_ADDRESS>

@rahug1190  - Thank you for providing your insights.
@ezYakaEagle442  - I hope @rahug1190 has answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Application crash

Microsoft PowerToys version
<IP_ADDRESS>
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
General
Steps to reproduce
I don't know, I was using my computer in the usual way when it crashed.
✔ Expected Behavior
None
❌ Actual Behavior
function normally without causing graphical bugs or crashes
Other Software
2024-03-26.txt
Error
Version: <IP_ADDRESS>
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 26/03/2024 14:46:52
Exception:
System.Runtime.InteropServices.COMException (0x80263001): {Desktop composition is disabled} The operation could not be completed because desktop composition is disabled. (0x80263001)
at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
at System.Windows.Shell.WindowChromeWorker._ExtendGlassFrame()
at System.Windows.Shell.WindowChromeWorker._UpdateFrameState(Boolean force)
at System.Windows.Shell.WindowChromeWorker._HandleDwmCompositionChanged(WM uMsg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Shell.WindowChromeWorker._WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

/dup https://github.com/microsoft/PowerToys/issues/31226