LOSS: NAN

Hi, I'm excited about your work and I'm trying white_box_attack and  finding loss=nan and the labels are all -100, I'm wondering if this is normal. Looking forward to your reply.

Hello, the loss and labels you mentioned is abnormal. In our white box setup, we set the labels for content outside of white_box/affirmative_responses.txt to -100. You should check if the labels corresponding to the tokens of affirmative_responses are normal.

Hi @Eurek001 , the loss and labels you mentioned is abnormal. In our white box setup, we set the labels for content outside of white_box/affirmative_responses.txt to -100. You should check if the labels corresponding to the tokens of affirmative_responses are normal.


[2417] Add missing spec for FinancialIncentive

Context
pending!
Changes proposed in this pull request

Add missing spec for FinancialIncentive

Guidance to review
:ship:
Checklist

[ ] Make sure all information from the Trello card is in here
[ ] Attach to Trello card
[ ] Rebased master
[ ] Cleaned commit history
[ ] Tested by running locally

 missing test for FinancialIncentive model

Follow up to #851


Clarify the relationship to bindgen and stdweb

In my understanding, stdweb aims to only support Rust and thus can be very idiomatic, whereas bindgen aims to more or less be language independent and use webIDL. I don't know  if stdweb too is planning to use webIDL in the future.
Bindgen is mentioned regularly in the weekly updates. stdweb is only mentioned once. Is the different treatment of the libraries by accident or by design? Which library do you reccoment for which use case in the short and the long run?

Right now I definitely recommend stdweb, it's much more production ready: it has many features that wasm-bindgen lacks, and it's really stable (breaking changes are rare). I've written mediumish sized Rust programs with stdweb (~10,000 LOC).
In the long run wasm-bindgen is probably the way to go, and it's improving at a very fast pace.
P.S. There are plans to add in full WebIDL support to stdweb.

Author of stdweb here.
Basically what @Pauan said. stdweb is more Rust-y and its emphasis is on providing:
1) A few highly idiomatic bindings as opposed to a bunch of raw, unidiomatic, autogenerated ones. For example, we convert exceptions which JS methods throw to Results, and this AFAIK cannot be autogenerated from IDL as IDL is missing information what throws what.
2) Comprehensive two-way JS interop, where you can easily embed JS code in your Rust code and convert the data between the two willy-nilly.
3) cargo-like experience where you don't have to manually mess with makefiles/build scripts.
wasm-bindgen definitely has more long term potential as it's officially supported by the Rust team while stdweb is only supported by... me (+ occasional contributors), and there is only so much I can do. (:
But if we're talking about the long term I would very much like to make stdweb compatible with wasm-bindgen in the future when/if wasm-bindgen will get the features I'd need.

The Rust and WebAssembly domain working group aims to make surgically replacing hot JavaScript functions/modules/libraries with Rust-generated WebAssembly the best choice for fast, reliable code on the Web. We want to have an impact much larger and more widespread than on just the Rust community.
Rust, as a language, is ready to rise to this challenge in part because of its zero-cost abstractions. To leverage that on the Web, we need to make very sure that we aren't losing that zero-cost property, and introducing bloat and overhead.
We decided that the best way to realize these ideals was to create wasm-bindgen. It has been designed from the start such that you only pay for what you use, both at runtime and in code size. It has been designed from the start to be future compatible with the host bindings proposal, promising to eventually unlock even-faster-than-JavaScript calls into native DOM methods. It encourages using cheap handles to objects that straddle the JavaScript and wasm boundary (which will eventually become wasm anyrefs) instead of expensive deep copies and serialization.
In general, taking Rust's interoperability with C and the C ABI -- this core tenet that Rust plays well with others -- and lifting that into the JavaScript and WebAssembly domain is an educational lens for viewing the working group's efforts. It explains why wasm-bindgen emits ECMAScript modules and our collaboration with JavaScript bundlers like Webpack.
With these higher-level philosophical bits out of the way, I'll let @alexcrichton speak to some more of the technical specifics.

Thanks for the question about this! I definitely sympathize with the confusion in that these two projects exist and there hasn't been a lot of "official" communication in one way or another about the relationship between the two.
In terms of clarifying the relationship between the two projects I think this is something that we can improve on as a working group! @Pauan has been actively participating in the working group but we haven't really talked specifically much about stdweb with respect to wasm-bindgen, and we as a working group haven't reached out to @koute yet. In that sense I think there's a lot of improvement for the working group to improve communication between the two projects, we've just been very focused on making sure wasm-bindgen, wasm-pack, and the tooling are ready for the edition release so far!
It sounds like there's also a technical part to this question with various claims as well. I'm not personally too familiar with the stdweb project, but I can speak to how wasm-bindgen fits in all this! At the risk of reiterating what @fitzgen has already mentioned, the main design goals of wasm-bindgen are:

Speed. Rust is a you-only-pay-for-what-you-use language, and Rust's story for WebAssembly should be no different. wasm-bindgen's goal is like that of C++, allowing you to write high-level code that optimizes the same as (or even better!) than what you would have written by hand otherwise (in this case raw *.wast files).
Size. Not only is Rust a fast language but Rust lacks no runtime. This means that Rust is ideal for writing tiny WebAssembly modules that execute blazingly fast and fit in a tiny module. With wasm-bindgen a "hello world" of addition is just a few hundred bytes, no extra fluff necessary.
Compatibility. The main use case for WebAssembly is on the web right now where JS is king. The ecosystem of JS programmers is the largest in the world and the web is the largest platform in the world. A major goal of wasm-bindgen is productively leveraging this ecosystem both in being able to import it (e.g. importing arbitrary node packages) as well as being able to integrate into it (being able to publish Rust code on NPM as WebAssembly and have users not even be aware that Rust is being used under the hood). Using wasm-bindgen is also just the same as using any other JS package, it's all an ES module.

Historically wasm-bindgen has required nightly Rust to work as we've figured out the best way for Rust and WebAssembly to work together. With the upcoming Rust 1.30 release (scheduled for late this October) the wasm-bindgen crate and its tooling will all compile on stable Rust. Additionally wasm-pack has always compiled on stable and is quickly maturing into a first-class tool designed for Cargo-like ease-of-use, mitigating a number of issues we've encountered while developing wasm-bindgen.
Some of the comments here look to be focusing on the WebIDL story for wasm-bindgen as well, so I think it's probalby also worth diving a bit into that. The web is quite a large and broad platform, and while wasm-bindgen has the various tools for importing functionality from the web it's tedious to do by hand. To make binding of the web platform simple we're developing a web-sys crate which will contain bindings for the entire web platform. These bindings are auto-generated from WebIDL provided by Firefox, so they're easy to modify and easy to update.
Naturally, however, with auto-generated APIs it's not always a perfect match with what you would have written by hand. The goal of web-sys is not to be the most ergonomic binding to the web platform but rather guarantee correct wrappers around the web platform. Just like how most crates are rarely using libc or winapi directly, it's unlikely most crates will directly use web-sys directly. Instead they'll likely use higher-level wrappers with more precise APIs.
It's absolutely critical to web-sys that it's auto-generated. I can't emphasize enough how important this is when binding large foreign platforms. For example libc uses verification and would be a near disaster without it (and auto-generation for us is achieving the same goal as auto-verification). Additionally we're doing what all browser vendors are already doing, generating code from WebIDL (only browsers generate C++, we generate Rust). This means we can leverage host bindings, have bindings for the entire platform, and guarantee correctness all in one go!
(Note that even with that being said, using web-sys is lightyears ahead of using libc, for example. It's all memory safe to start out with!)

To reiterate, I'm not personally too familiar with the details of stdweb. From what I do know, however, (and from the goals I've read online in various places) I would recommend wasm-bindgen. Adoption of WebAssembly and Rust on the web will critically rely on not replacing JS but rather augmenting JS and the existing ecosystem. To that end interop with NPM and the JS ecosystem is a top-priority of the working group as a whole (as mentioned by @fitzgen).
As for some super-nitty-gritty technical details, I've done some local benchmarking to show where the goals of wasm-bindgen really shine. When measuring the overhead of a function call (calling into JS), wasm-bindgen is 10x faster than stdweb. This does not mean that wasm-bindgen is 10x faster, only that it's definitely delivering on its goals of as-if-you-hand-wrote-it performance. Additionally the output for that benchmark has wasm-bindgen clocking in at ~2.5k with stdweb at around 65k, again showing how wasm-bindgen's goal of staying as minimal as possible really shines.

Oh, also! As alluded to in an earlier comment, js-sys and web-sys aim to be the libc of JavaScript and the Web respectively, a conceivable path forward at some point in time could be for stdweb to stop maintaining its own set of raw bindings, use js-sys and web-sys instead, and focus solely on its higher-level APIs. That is, of course, your own decision to make @koute :)

@alexcrichton I've used stdweb quite a bit, and have tried to keep up with bindgen etc. as well.
I think stdweb should be viewed as having four components:

The ability to embed raw javascript code from rust, akin to the include! macro.
An interop/runtime layer, which automatically performs marshalling of types back and forth between javascript and rust, plus some syntax sugar via the js! macro to make interpolation of rust values particularly convenient.
A set of rust bindings to various javascript APIs, built using the above two components.
Additional tooling for building/running/testing stdweb-based projects.

What I would like to see is for part 1) to be incorporated as a feature of wasm-pack, so that both stdweb and bind-gen based projects can share a common foundation, and eventually remove the need for stdweb's custom build system (or at the very least have it use wasm-pack internally).
The main thing which stdweb provides which cannot be implemented with wasm-bindgen is the ability to work with references to javascript objects. What is needed is a global map from <integer rust ID> to  that all bindings can share, so that rust code can consistently refer to objects on the javascript heap, and this is one of the things stdweb provides out of the box.
Regarding performance, I fully expect wasm-bindgen to be much faster than stdweb. The interop/runtime layer (2) is not optimised at all right now, and also marshals data in a completely dynamic way, whereas wasm-bindgen can generate code at compile time. Stdweb also has to look up references in this global map, whereas wasm-bindgen does not support references at all.

As for some super-nitty-gritty technical details, I've done some local benchmarking to show where the goals of wasm-bindgen really shine. When measuring the overhead of a function call (calling into JS), wasm-bindgen is 10x faster than stdweb.

Yes, I'm not surprised by this at all. (: E.g. I haven't added any special casing for primitives, so currently the same codepath is used for types which are not natively serializable (like e.g. Vec<Node> for example) and for those which are, which means that everything is serialized non-natively through heap. And there are some other known inefficiencies. Those are definitely fixable - I just prioritized API features and in general figuring out how a minimal yet high level API would look like without going pedal-to-the-metal with the optimizations.

Oh, also! As alluded to in an earlier comment, js-sys and web-sys aim to be the libc of JavaScript and the Web respectively, a conceivable path forward at some point in time could be for stdweb to stop maintaining its own set of raw bindings, use js-sys and web-sys instead, and focus solely on its higher-level APIs. That is, of course, your own decision to make @koute :)

I'd definitely like to do that! However I still need to be able to emit raw JS snippets from inside of the Rust code.
If wasm-bindgen supported that I could probably port stdweb quiet easily (possibly with some extra elbow grease on wasm-bindgen's side?), even though it might be slightly inefficient, and then convert it to web-sys piece by piece. If I could strip away most of my runtime and rely on wasm-bindgen then perhaps we could have high-er level Web APIs of stdweb with the speed/minimalism of wasm-bindgen. (:

Don't have time for a proper reply right now, but I will make one on Tuesday.

The main thing which stdweb provides which cannot be implemented with wasm-bindgen is the ability to work with references to javascript objects.

This is very much possible, see JsValue and js_sys::Object and importing custom JS classes. Is this not what you mean? Could you clarify?

I think it's probably unlikely for wasm-bindgen itself to grow a js! macro, but it's definitely intended to have enough support to construct such a macro as a library! If wasm-bindgen is missing features to define js! as a library, it's definitely worth having issues for and tracking.

This is very much possible, see JsValue

Ah, I'm sorry, I didn't see this get added. Yes the internal slab allocator for objects covers what I was thinking of. In that case this is another area where stdweb could move to using the same underlying machinery as wasm-bindgen.

I think it's probably unlikely for wasm-bindgen itself to grow a js! macro, but it's definitely intended to have enough support to construct such a macro as a library!

Of course I didn't mean that wasm-bindgen should support a fully blown js! macro (as that is probably out of its scope); what I meant is something low-level and minimal like Emscripten's emscripten_asm_const_int.
Ideally we'd have a macro with a prototype of fn(&str, ...) -> T where the first &str argument is the raw JS snippet and the rest are WASM-native arguments.
let result: i32 = js_raw!("return $0 + $1;", 1, 2);
assert_eq!(result, 3);

This could result in the following import on the JS side:
let imports = {
    // ...
    "env": { // Or whatever else namespace.
        // ..
        "snippet_04d4c172203e9e30c9a301547926c07ffe64457f": function($0, $1) {
            return $0 + $1;
        }
    }
}

Is such a macro out-of-scope too?
I guess maybe this could be implemented right now with a procedural macro which would output the snippet into its own file in $crate/target/ and generate a #[wasm_bindgen(module = "/absolute/path/to/$crate/target/snippet_04d4c172203e9e30c9a301547926c07ffe64457f.js")] on Rust's side?

@koute I think that's probably covered by https://github.com/rustwasm/wasm-bindgen/issues/224 in the sense that what we'd like to do is have a more principled approach at importing local JS snippets (which isn't supported well today). I think it's reasonable though to consider alternative strategies before that's figured out though! In that sense I don't really know if such a macro is in or out of scope, but we could definitely scope it out and see how it goes!
It's definitely a goal of wasm-bindgen to support a js!-like macro that stdweb uses one day. We may have to figure out what the best way to do that is, but if it can't be done today that's definitely a bug in wasm-bindgen we'd like to fix.

Ok so correct me if I'm wrong, but it sounds like this issue is technically resolved in that it sounds like stdweb would like to move towards a future which is built on top of wasm-bindgen and/or wasm-pack. This means that stdweb and all its features will likely continue to exists, only the veneer on the fringes may differ (such as the output of the cargo web subcommand I think?). The wasm-bindgen crate in the meantime needs to grow features necessary to support the js! macro in stdweb.
Does that sound right? If so is this perhaps resolved enough to close?

Yes! Perfectly resolved for me. Thank you everyone, for taking the time and explaining the philosophy, motivation and technical side of the relation between wasm-bindgen and stdweb. It made very clear to me that I can use stdweb shortterm and profit longterm all the work that goes into wasm-bindgen.


[Bug] outputTypes flag does not work in Search method

Describe the bug A clear and concise description of what the bug is.
Cannot use outputTypes flag in the sail search query execution
To Reproduce Steps to reproduce the behavior:
Execute:
sail search query "name:a*" --indices identities --outputTypes json
Expected behavior

Actual behavior A clear and concise description of what actually happens.

Documentation has been updated to remove outputTypes flag as it is not supported and the only valid type is JSON.


Fix up macOS build

Fix the macOS build by not defining strndup for it; it's already in the standard library.
/cc @lildude

Thank you!


Step 3

Hi, its not clear that Step 3: Create the extension manifest file should be done in the home directory (NOT BuildAndReleaseTask) folder
I think if you make it clear VSO should be opened from the home folder and not the buildAndReleaseTask this would prevent the issue
You also dont state that the images folder with extension-icon.png needs created and this causes an issue when running  tfx extension create --manifest-globs vss-extension.json

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

ID: 44581f4a-93df-7507-3844-eadedf9a6cc4
Version Independent ID: 33c7bcf0-1512-975f-5ef8-9f2a192a84ad
Content: Add a Build or Release Task - Azure DevOps
Content Source: docs/extend/develop/add-build-task.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

Hi @whatisthejava, Thank you for your feedback. I've created a user story for my backlog to address this. Thanks again!

I'm closing this issue, however please @mention me if you have any further feedback or questions. Thanks.

Adding @jtpetty for further guidance/assistance, thank you!

I've just published an update, which should be live shortly. Thanks!


Add test cases while Jenkins job is running for Auth Services

Add to docker file  and running the test cases while building the image


Conv Transpose 1d not Implemented for CUDA.

Hey!
Just trying to reimplement something in Candle from the ground up for inference (no need for training). It's a fairly chunky model but I'm at the last hurdle.
So first of all thank you for all the work done so far. I think despite the docs not being fleshed out yet, it has actually been fairly intuitive to get around the crate for my purposes - so kudos to that!
I've hit a wall just now with the conv-transpose1d being not implemented on a CUDA backend. I saw that this PR added some boilerplate for it (https://github.com/huggingface/candle/pull/1251).
I am wondering how difficult would it be to populate it or if there are any work arounds right now for a CUDA backend?
I have had a look at the crate a tiny bit and would love to do a PR for it, but I don't really know where to start, both in terms of Candle, and actually what the OP should do in practice, so I will go off now and have a look/read, but any advice on how to proceed is really appreciated.

I've had a play with it and implemented my own ConvTranspose1d kernel as a custom op. I think it's simple to just copy the 2D Naive one and tweak the dimension. Had a bit of a chat about this on the discord.
I think in the end it is a pretty poor kernel, but also performance isn't yet comparable to Python (800 GPU ms in Rust, vs 400 GPU ms for Python after checking when the last kernel finishes). #1139 notes down some kernels I also saw coming up hot in nsys and I think none of this part of the kernels uses CUDNN either (not sure if theres anything in there that could help).


Princess Luna: Blacklist t-nation.com

Princess Luna requests the blacklist of the website t-nation\.com. See the Metasmoke search here and the Stack Exchange search here.

Coverage remained the same at 65.558% when pulling 9647a72b7e4799b76a85dcea02011f9b9a859519 on auto-blacklist-1522953774.7869546 into 8fca7688397ef2b2e0b2ff784196c46b2d95d612 on master.

!!/approve


ignore_missing not showing mapping with "desc" field

I'm using Lunarvim, one thing that the LSP module in lvim set buffer keys using
local opts = { buffer = bufnr, desc = remap[2], noremap = true, silent = true }
vim.keymap.set(mode_char, key, remap[1], opts)

The opts can only have desc but not label, here remap[2] is really the value for a label.
This turns out in which-key.keys#get_mappings method, some of the mappings we get only have value.desc but not value.label
If we use ignore_missing option here, these keybindings will be skipped by which-key
I propose a PR which add the following logic
if not value.label and value.desc then
  value.label = value.desc
end

Thanks for the MR, because your MR got closed, I opened mine to fix the issue.


Just save verified donations in totalDonations in project entity

Now we save projects donations amount in a field name totalDonations, and we have some sorting in our system based on totalDonations but there is a bug there because a user can saveDonation with a huge amount on some projects ( without really donating) and this project will come first in this sorting, I suggest we should just count verified donations ( I mean the donations that got verified with blockchain network data)
PS if we want to implement this , we should not call updateTotalDonationsOfProject() after creating new donations, and we should call it when changing donation's status to verified in processVerifyDonationsJobs()
@MoeNick
As it has UX side effects I need your approval to start implementing this ( because we show unVerified + verified donations in donations list, and if we just show sum of verified donations in totalDonations it can be different and may confuse the users

It's done


Switch from balenaCI to flowzone

Changelog-entry: Switch from balenaCI to flowzone
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@balena-ci rebase

Flowzone master has been fixed by the test is caching


Validate v1 and v2 charts for SLES 15 SP1

Validate v1 and v2 charts for SLES 15 SP1.

Deploy rancher 2.5-head
Deploy v1 charts and verify the P0 usecase (note down the chart version)
Deploy v2 charts and verify the P0 usecase (note down the chart version)

Test environment:

rancher:v2.5-head 9b0058c with k8s v1.20.5 on AWS t2.medium instance type and us-east-2 region
1x master (control-plane + etcd) and 3x worker
using official aws image for SLE15SP1 suse-sles-15-sp1-chost-byos-v20210304-hvm-ssd-x86_64, ami-014b2be5492b26b99

Few v1 charts validated so far:
v1 charts logging - used fluentd - rancher-logging 0.2.4
:+1: cluster level
:+1: project level
:+1: edit as yaml
v1 alerting - no version
:+1: minimum - webhook
:+1: :boom: high cpu with enabled v1 monitoring - webhook
... due broken v1 monitoring (needed for high cpu alert) - pod prometheus-proxy pod says ImagePullBackOff: Back-off pulling image "rancher/library-nginx:1.19.9-alpine", workaround is to use rancher/library-nginx:1.19.2 instead, https://github.com/rancher/rancher/issues/32010
v1 pipeline - no version
:+1: simple testcase with example repo and without Github Oauth

Test environment:

Tested on rancher:2.5.8-rc12
the rest is as before

v2 charts validation report:
:+1: monitoring - 14.5.100 - installed in System project
:+1: logging - 3.9.400 - clusterOutput (cluster level), Output (namespace level)
:+1: istio - 1.9.300 - demoapp deployed and tested
:+1: OPA Gatekeeper - 3.3.001 - a namespace without label cannot be created
:-1: :boom: FAILED CIS Benchmark - 1.0.400 - scan with rke-profile-permissive-1.6 - NEW https://github.com/rancher/rancher/issues/32428
:+1: fleet/Continous Delivery - rancher/fleet-agent:v0.3.5-rc6 - Guestbook app deployed
SKIPPED Backup and Restore - local cluster only


Is there possibility to mount prl_fs /Users with suid enabled?

Confirm the problem. SUID-bit is not supported in prl_fs at the moment.

@romankulikov When will SUID-bit and SGID-bit be supported in prl_fs? I failed to run gitlab-ce docker in Mac EI Capitan because of this problem, the data directory was shared between Mac Host and Linux Guest. I logined in Linux Guest, then executed "chmod 2770" on that shared directory, but the command  failed and reported "permission denied."

@zouguangxian unfortunately I'm not allowed tell you when. But I'm really curious why GitLab wants SUID-bit data files. For what purpose?!

@romankulikov I'm not sure why Gitlab wants SGID-bit data directory. I've resolved this problem by mounting a data only volume.


Please package patchwork

Issue description
I'm not a npm/js/node/whatever guy, so I cannot do this, but I really would love to have this packaged for nixpkgs: https://github.com/ssbc/patchwork. Can someone please do that?

Oh, I thought you meant http://jk.ozlabs.org/projects/patchwork/ :-)

#61530


Win 64 libcurl-4.dll is missing

Environment

Tesseract Version: 5.0.0-alpha
Commit Number:
Platform: Win 7, 64 bit

Current Behavior:
Unable to start, complains of missing libcurl-4.dll
Expected Behavior:
starts
Suggested Fix:
provide missing dll in win installer.

Thank you for reporting this. I replaced the installer with the same files plus the missing DLLs (libcurl-4.dll requires 3 more DLLs). The new Tesseract executable supports an image URL as input for the OCR.

It happens with a https URL (try http://tesseract.projectnaptha.com/img/eng_bw.png). curl_easy_perform fails with error 60:

CURLE_PEER_FAILED_VERIFICATION (60)
The remote server's SSL certificate or SSH md5 fingerprint was deemed not OK.

So the root certificates are missing or not found.

I still don't know where the root certificates are searched, so I am currently unable to fix the problem with https URLs. If someone finds a solution that would be welcome.

From memory, there may be an option to not verify ssl urls

Sure, but is that desirable? I don't think so. At least it should not be enabled by default. So perhaps adding a parameter which can disable the certificate verification might be a possible solution.

I close this issue because libcurl-4.dll is no longer missing. The latest version from today also reports curl errors instead of raising an assertion.


Basic Prometheus metrics exported

Fixes Issue
#29

Changes proposed
Prometheus metrics exposed by the application for monitoring

[x] basic done
[] Correct; marked as done

[ ] - Not correct; marked as not done
Screenshots

Note to reviewers

Preview for the App
iphonerocketpartying_face
Provider	Status	Link
 https://pdf-web.herokuapp.com/

go to https://pdf-web.herokuapp.com/metrics


Adds open, onOpenChange, and anchorRef props to DropdownMenu

This extends DropdownMenu to allow:

externally controlling the open state (via open and onOpenChange props
setting an anchorRef prop to control the positioning of the overlay.

Closes #1369.
Screenshots

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[x] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge

Take a look at the What we look for in reviews section of the contributing guidelines for more information on how we review PRs.

Let me know if yall think this merits a test!


Revisit use of simple_root

The construction of simple_root as a link back to itself appears to be a very odd construction and does not work on all environments. We should revisit why we did this and see if we can come up with more stable implementations.
Came up while testing #113

@dr-rodriguez try replacing simple_root in your windows env with ln -s simple_app/ simple_root; that's what it is on reclaim


"Check For Updates" menu option not hidden on MacOS when "disable-remote-interaction" flag is set

Describe the bug
On MacOS, when the disable-remote-interaction flag is set to true, the Check for Updates menu item is still visible.

This is unlike in Windows where both the 'Check For Updates' and 'Privacy Preferences' are disabled under the Help menu when the flag is set to true.

(Notice 'Check for Updates' and 'Privacy Preferences' are missing when flag is set)
Steps to reproduce

Create a flags.json file with content

{
  "disable-remote-interaction": true
}

add flags.json file to resources folder
Launch Camunda Modeler
From Menu bar select   'Camunda Modeler'

Notice that 'Check for Updates'  is still a visible option.
Expected behavior
'Check for Updates' option should not be visible when disable-remote-interaction flag is set to true.
Environment

OS: MacOS 12.6.1
Camunda Modeler Version: 5.7.0
Execution Platform: Camunda Platform
Installed plug-ins:  []

Additional context
Help menu code in menu-builder.js  checks for the disable-remote-interaction and hides them appropriately.
There is no such check in the mac-menu-builder.js

disable-remote-interaction does prevent interaction automatically initiated by the tool. It does not prevent manual update check by the user.

Yes. Happy to make the change!

Closed via https://github.com/camunda/camunda-modeler/commit/47ef3192bd79f938304fb749796ab281119d8978.


Adds "Relay n (API failsafe only)" to button's actions

Solves #23

Summary by CodeRabbit

New Features

Added failsafe action text options for four buttons in the configuration.

Improvements

Enhanced button action definitions with failsafe options for better flexibility.
Streamlined logging and connection checks for relay toggling actions.
Improved clarity in operational flow with additional logging for relay actions.

Actionable comments posted: 0
🧹 Nitpick comments (1)

ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_relays.yaml (1)> 208-243: Consider refactoring the relay toggle logic for better maintainability.

While the implementation is functionally correct, the code structure could be improved to reduce repetition and enhance maintainability.
Consider refactoring using a map or helper function:
- switch (button) {
-   case ${BUTTON_1_ID}:
-     select_state = sl_button_1_action->state;
-     toggle_relay = (select_state == "${BUTTON_1_ACTION_TEXT}" or
-                     (api_disconnected and select_state == "${BUTTON_1_ACTION_FAILSAFE_TEXT}"));
-     if (toggle_relay)
-       sw_relay_1->toggle();
-     break;
-   // ... similar cases for buttons 2-4
- }
+ const std::map<uint8_t, std::tuple<select::Select*, switch_::Switch*, const char*, const char*>> button_map = {
+   {${BUTTON_1_ID}, {sl_button_1_action, sw_relay_1, "${BUTTON_1_ACTION_TEXT}", "${BUTTON_1_ACTION_FAILSAFE_TEXT}"}},
+   {${BUTTON_2_ID}, {sl_button_2_action, sw_relay_2, "${BUTTON_2_ACTION_TEXT}", "${BUTTON_2_ACTION_FAILSAFE_TEXT}"}},
+   {${BUTTON_3_ID}, {sl_button_3_action, sw_relay_3, "${BUTTON_3_ACTION_TEXT}", "${BUTTON_3_ACTION_FAILSAFE_TEXT}"}},
+   {${BUTTON_4_ID}, {sl_button_4_action, sw_relay_4, "${BUTTON_4_ACTION_TEXT}", "${BUTTON_4_ACTION_FAILSAFE_TEXT}"}}
+ };
+
+ if (auto it = button_map.find(button); it != button_map.end()) {
+   auto [action_select, relay_switch, action_text, failsafe_text] = it->second;
+   select_state = action_select->state;
+   toggle_relay = (select_state == action_text or
+                   (api_disconnected and select_state == failsafe_text));
+   if (toggle_relay)
+     relay_switch->toggle();
+ }

This refactoring:

Reduces code duplication
Makes it easier to maintain and modify button-relay mappings
Centralizes the toggle logic

📜 Review details
Configuration used: CodeRabbit UI Review profile: CHILL Plan: Pro
📥 Commits
Reviewing files that changed from the base of the PR and between ec528ec and 60a3248.
📒 Files selected for processing (2)
🔇 Additional comments (3)

I liked the suggestion, but I'm not gonna implement this now as this triggers a warning in ESPHome compiler:
INFO ESPHome 2024.12.2
INFO Reading configuration /config/esphome/tx-ultimate-us.yaml...
WARNING GPIO5 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
WARNING GPIO15 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
See https://esphome.io/guides/faq.html#why-am-i-getting-a-warning-about-strapping-pins
INFO Detected timezone 'Europe/Stockholm'
INFO Generating C++ source...
INFO Compiling app...
Processing tx-ultimate-us (board: esp32dev; framework: arduino; platform<EMAIL_ADDRESS>--------------------------------------------------------------------------------
HARDWARE: ESP32 240MHz, 320KB RAM, 4MB Flash
 - toolchain-xtensa-esp32 @ 8.4.0+2021r2-patch5
Dependency Graph
|-- AsyncTCP-esphome @ 2.1.4
|-- WiFi @ 2.0.0
|-- FS @ 2.0.0
|-- Update @ 2.0.0
|-- ESPAsyncWebServer-esphome @ 3.2.2
|-- DNSServer @ 2.0.0
|-- ESPmDNS @ 2.0.0
|-- ArduinoJson @ 6.18.5
|-- NeoPixelBus @ 2.7.3
|-- WiFiClientSecure @ 2.0.0
|-- HTTPClient @ 2.0.0
|-- ESP32-audioI2S @ 2.0.7
|-- Improv @ 1.2.4
Compiling .pioenvs/tx-ultimate-us/src/main.cpp.o
/config/esphome/packages/edwardtfn/TX-Ultimate-Easy/ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_relays.yaml: In lambda function:
/config/esphome/packages/edwardtfn/TX-Ultimate-Easy/ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_relays.yaml:213:11: warning: init-statement in selection statements only available with -std=c++17 or -std=gnu++17
           if (auto it = button_map.find(button); it != button_map.end()) {
           ^~~~
/config/esphome/packages/edwardtfn/TX-Ultimate-Easy/ESPHome/TX-Ultimate-Easy-ESPHome_core_hw_relays.yaml:214:14: warning: structured bindings only available with -std=c++17 or -std=gnu++17
             auto [action_select, relay_switch, action_text, failsafe_text] = it->second;
              ^
Linking .pioenvs/tx-ultimate-us/firmware.elf
RAM:   [=         ]  14.3% (used 46780 bytes from 327680 bytes)
Flash: [====      ]  36.1% (used 1420617 bytes from 3932160 bytes)
Building .pioenvs/tx-ultimate-us/firmware.bin
Creating esp32 image...
Successfully created esp32 image.
esp32_create_combined_bin([".pioenvs/tx-ultimate-us/firmware.bin"], [".pioenvs/tx-ultimate-us/firmware.elf"])
Wrote 0x16c3d0 bytes to file /data/build/tx-ultimate-us/.pioenvs/tx-ultimate-us/firmware.factory.bin, ready to flash to offset 0x0
esp32_copy_ota_bin([".pioenvs/tx-ultimate-us/firmware.bin"], [".pioenvs/tx-ultimate-us/firmware.elf"])
========================= [SUCCESS] Took 35.29 seconds =========================


Remove unused lodash packages

This project uses semver, please check the scope of this pr:

[ ] #none# - documentation fixes and/or test additions
[X] #patch# - backwards-compatible bug fix
[ ] #minor# - adding functionality in a backwards-compatible manner
[ ] #major# - incompatible API change

CHANGELOG

Removed unused ember-lodash-shim package
Removed unused lodash-es package

👍


Fix #1316: Exclude component-libaries.xml file when package collector jar

Please answer these questions before submitting pull request

Why submit this pull request?

[x] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues
#1316

Coverage remained the same at 24.028% when pulling 577ce948662975f2b9fb27d890fec6b914497273 on ascrutae:fix/dulipcate-packaging-files into 2c822363cb8ea469c04760117bc953ec4b6e5a16 on apache:master.


fix: prevent update race in workflow cache (Fixes #9574)

Fixes #9574
Motivation
When running high volumes of parallel workflows with high per-workflow node counts (300+ workflows, >100 nodes per workflow), ~1% of workflows will fail or get stuck with a few different errors which have changed over time with previous attempts to fix the problem:

originally, segfault when dereferencing a null pointer.  updated to panic: "no Node found" in Argo 3.4.0
if a child node is lost, workflow gets "stuck" waiting forever

Given the random nature of the problem that only surfaces when large numbers of large workflows are running concurrently, I suspected and went looking for a possible race condition in the Workflow cache.
Modifications
I found a few areas where a reference to a workflow is acquired before locking and not re-acquired after locking, or where a lock was not acquired but should have been.
Instead of re-acquiring the workflow after locking I changed the logic to acquire the lock first before fetching the workflow to simplify, on the assumption that this race is rare enough that rarely waiting on the lock should be better than always hitting the cache twice.
In places that weren't locking but should have been, I added some logic to do so.
Verification
For the past 6 months, we have been running a modified version of Controller with the changes in this PR.  Not a single further occurrence of the above mentioned problems have occurred whilst running 500-1000 concurrent workflows.  At the far end of the extreme, we experienced etcd timeout problems but at least no more random workflow processing failures.

@juliev0 / @sarabala1979  could you take another look?

Still happy with this. @terrytangyuan, could you take a look?

@sarabala1979 any chance you could take another look? We would love to to get this MR (or equivalent fix) merged. Thanks!

For posterity, I suspected a (potentially different kind of) race in https://github.com/argoproj/argo-workflows/pull/11451#issuecomment-1702926394 and couldn't quite find it, I wonder if this might have been it

can dis be backported to 3.4?

It's a fix, so it should be by default unless there are many conflicts. But #11851 would be the right place to ask.

was backported to 3.4.17


Desktop Peek button bottom edge broken after using TaskbarX (persists after closing)

The Peek button to the right of the Tray, on the taskbar doesn't quite work right after Taskbar X has been launched.
Under normal conditions, the mouse can be 'whacked' into the very corner of the screen and a mouse click will show the desktop. Importantly, the cursor can be on the very edge of the monitor and the button still works.
After launching TaskbarX, however, it seems that the very bottom row of pixels no longer can be clicked on to show the desktop; instead, one must 'whack' the mouse into the corner, then raise it upwards fraction to enable the Peek button to be clicked (it changes colour when the cursor is over it and clickable).
This issue persists even after stopping TaskbarX from the configurator, and so far the only way I have found to restore normal Peek behaviour is to disable TaskbarX from launching on startup and rebooting the PC.
The issue goes away in Safe Mode, but then is immediately back again after manually running TaskbarX.exe, and does not return to normal after stopping the program.
The version of TaskbarX I am using is <IP_ADDRESS>.

i was having the same issue too, so i tried installing different versions and <IP_ADDRESS> works fine for me atm

Same thing for me here. Peek button seems to be broken in newer versions. Just tried <IP_ADDRESS> and it works fine here too. Thanks for the info!

ur welcome lol

I'm also facing the same issue. Going to stick to <IP_ADDRESS> until this bug gets fixed!

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870
I hope you understand ❤


Credit card form errors break input labels

Steps to reproduce the problem

Go through checkout to the Payment Method step.
Leave credit card fields empty and submit the form.

Labels are not rendered in the proper place and as a result, they clash with error messages.
Screenshots

Actually, when I provide valid test values the form fails anyway. E.g. if I have Braintree configured, this form would send credit card data to Braintree to get the token of payment, and this token would be passed to our API. But the request which is sent to Braintree has the following input:
creditCard: {
  number: "",
  expirationMonth: "",
  expirationYear: "",
  cvv: "",
}

Which looks like data from our inputs wasn't passed to Braintree call at all.


Link problem of readme file

In readme, the line for vim-tmux-clipboard  is wrong, it should be https://github.com/roxma/vim-tmux-clipboard.

This is fixed by #20.


Fixed typos

Multiple instances of "directory" were misspelled as "director". Fixed plural spellings.

Ups, thank you :)


Binary and container image for linux+arm and darwin+arm

Build arm arch container image for raspberry pi and MacOS support.

Darwin excluded. ARM included. Darwin not in scope


I have used url_launcher: ^6.1.6 to open url in web browser in readers app but ios has rejected app stated this reasons in the mail

Steps to Reproduce
Your "reader" app uses the External Link Account entitlement to link out for account creation and management but does not meet all requirements for using this entitlement.
Specifically, we found that your app does not meet the following requirement(s):
Your app does not use the External Link Account API to populate the modal sheet before every instance of linking out for account creation and management.
Url for External Link Account
Configure the SKExternalLinkAccount property list key.
Use the ExternalLinkAccount type’s canOpen property and open() method.
**The link shows there is 2 things to implement first one we have done and second one is Use the ExternalLinkAccount type’s canOpen property and open() method I am not able to find this same thing in flutter in url launcher library can anyone help me how to implement canOpen and open() like iOS in flutter. I am sharing code of flutter were we open url **
Expected results: how can I get approval from iOS support as they found library not using canopen() and open() in iOS code as they found code not complying with there requirement
Actual results: I want to know is their way to implement the ExternalLinkAccount type’s canOpen property and open() method in flutter as asked by Apple support to get approval for app.(note: code is working fine able to open url in iOS in browser)

_launchURL() async `{`
    const url = 'https://www.bonusround.ca/signup';
    if (await canLaunchUrl(Uri.parse(url))) {
      Navigator.pop(context);
      await launchUrl(Uri.parse(url), mode: LaunchMode.externalApplication);
    } else {
      throw 'Could not launch $url';
    }
  }

Logs

Use the ExternalLinkAccount type’s canOpen property and open() method I am not able to find this same thing in flutter in url launcher library

This is a separate API unrelated to the functionality that url_launcher provides access to, so it's not part of this plugin.

I want to know is their way to implement the ExternalLinkAccount type’s canOpen property and open() method in flutter

You would need to either implement it directly in your application, or find/write a plugin that wraps that API.
Closing as this is not in scope for url_launcher.


ValueError: Could not load model databricks/dolly-v2-12b with any of the following classes: (, ).

Running the model on a Windows computer with RTX 4090
python version == 3.10.10
code run:
import torch
from transformers import pipeline
generate_text = pipeline(model="databricks/dolly-v2-12b", torch_dtype=torch.bfloat16, trust_remote_code=True, device_map="auto")

Error
--> 266         raise ValueError(f"Could not load model {model} with any of the following classes: {class_tuple}.")
    268 framework = "tf" if model.__class__.__name__.startswith("TF") else "pt"
    269 return framework, model

ValueError: Could not load model databricks/dolly-v2-12b with any of the following classes: (, ).

pip freeze:
accelerate==0.18.0
aiohttp==3.8.4
aiosignal==1.3.1
asttokens==2.2.1
async-timeout==4.0.2
attrs==22.2.0
backcall==0.2.0
certifi==2022.12.7
charset-normalizer==3.1.0
colorama==0.4.6
comm==0.1.3
datasets==2.11.0
debugpy==1.6.7
decorator==5.1.1
dill==0.3.6
executing==1.2.0
filelock==3.11.0
frozenlist==1.3.3
fsspec==2023.4.0
huggingface-hub==0.13.4
idna==3.4
ipykernel==6.22.0
ipython==8.12.0
jedi==0.18.2
Jinja2==3.1.2
joblib==1.2.0
jupyter_client==8.2.0
jupyter_core==5.3.0
MarkupSafe==2.1.2
matplotlib-inline==0.1.6
mpmath==1.3.0
multidict==6.0.4
multiprocess==0.70.14
nest-asyncio==1.5.6
networkx==3.1
numpy==1.24.2
packaging==23.1
pandas==2.0.0
parso==0.8.3
pickleshare==0.7.5
Pillow==9.3.0
platformdirs==3.2.0
prompt-toolkit==3.0.38
psutil==5.9.4
pure-eval==0.2.2
pyarrow==11.0.0
Pygments==2.15.0
python-dateutil==2.8.2
pytz==2023.3
pywin32==306
PyYAML==6.0
pyzmq==25.0.2
regex==2023.3.23
requests==2.28.2
responses==0.18.0
scikit-learn==1.2.2
scipy==1.10.1
six==1.16.0
stack-data==0.6.2
sympy==1.11.1
threadpoolctl==3.1.0
tokenizers==0.13.3
torch==2.0.0+cu117
torchaudio==2.0.1+cu117
torchinfo==1.7.2
torchvision==0.15.1+cu117
tornado==6.2
tqdm==4.65.0
traitlets==5.9.0
transformers==4.25.1
typing_extensions==4.5.0
tzdata==2023.3
urllib3==1.26.15
wcwidth==0.2.6
xxhash==3.2.0
yarl==1.8.2

Can you try adding task="text-generation" to the pipeline()? That's worked for a few other people. @matthayes I think this task instruction-following thing might be causing this issue.

@srowen @matthayes still getting the same error
ValueError: Could not load model databricks/dolly-v2-12b with any of the following classes: (, ).

I downloaded the model just yesterday so I'll bet it's using the new config, but that doesn't seem to be the problem. I also see other people's error included the "AutoTokenizer" and stuff, but mine is just (, ), which is strange.
PS. just in case, I only have 32GB memory and wonder if that might be an issue since this model itself is 23GB big?

Tried databricks/dolly-v2-7b and this worked.
So my guess is in the RAM size. Do you have any recommended memory size for each model?

I think your guess is correct. At first, I tried on V100-32gb and encountered the same error as you did. Then I switched to A100-40gb, and the pipeline was successfully initialized. However, it still ran out of memory during runtime. After using bfloat16, it ran successfully.

As a rule of thumb, because this model is stored in 16-bit, you will need 2 x num parameters bytes of mem, plus memory for the data and so on. 12B won't quite work on 24GB; should work on 32GB. 8bit requires half the memory.
If you're accidentally using fp32, then memory requirements double.

@LuckyyySTA @srowen okay so it's still mainly the GPU not the regular RAM? (I'm using my personal rig, not a cloud platform here). So if I upgrade my GPU further, I can still get away with like 32GB regular RAM?
And this might be a dumb question as I'm new to a lot of this, if I were to finetune dolly-v2-7b, would it require a few times more memory in the GPU?

No, you need GPU RAM. Fine tuning is a pretty different question but broadly it will take more resources than inference.


Unable to rollback during performing ADA

What happened:
Pushing the Cancel button then gets stuck for a while. After that, the rollback stage ends with failure leaving this log:
[2020-11-24 10:30:13 +09:00]
Preparing deploy source at running commit (ae32a73ec9b24470e83b9ec8d263de6936ca34d6)
[2020-11-24 10:30:13 +09:00]
Failed to prepare running deploy source data (failed to fetch: context canceled)

What you expected to happen:
How to reproduce it:
Prepare the pipeline with ANALYSIS stage:
apiVersion: pipecd.dev/v1beta1
kind: KubernetesApp
spec:
  pipeline:
    stages:
      - name: K8S_CANARY_ROLLOUT
        with:
          replicas: 20%
          createService: true
      - name: ANALYSIS
        with:
          duration: 20m
          metrics:
            # Error rate
            - provider: prometheus-dev
              interval: 5m
              failureLimit: 1
              expected:
                max: 0
              query: |
                rate(http_requests_total{status=~"5.*", job="podinfo-canary"}[5m])
                /
                rate(http_requests_total{job="podinfo-canary"}[5m])
      - name: K8S_PRIMARY_ROLLOUT
      - name: K8S_CANARY_CLEAN

Do cancel when performing the ANALYSIS stage.
Environment:

piped version:
control-plane version:
Others:

/assign @nakabonne

/unassign @nakabonne

A note on what's happening in detail.

Push the Cancel button
I don't know why but the next stage fails
The ANALYSIS stage is still running
After a while, the ROLLBACK stage starts and fails immediately


Adding temporary record for zone .in?

Hi there-
I seem to be having a similar issue to some others, but not exactly the same as anything I've seen.
here are my relevant logs:
ERR | ts=1705397799.0994973 logger=tls.obtain msg=could not get certificate from issuer identifier=ha.bepste.in issuer=acme-v02.api.letsencrypt.org-directory error=[ha.bepste.in] solving challenges: presenting for challenge: adding temporary record for zone "in.": got error status: HTTP 400: [{Code:6003 Message:Invalid request headers}] (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/130971514/13714026544) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)

INF | ts=1705397803.159895 logger=tls.issuance.zerossl.acme_client msg=trying to solve challenge identifier=ha.bepste.in challenge_type=dns-01 ca=https://acme.zerossl.com/v2/DV90

INF | ts=1705397803.1830766 logger=tls.issuance.zerossl.acme_client msg=trying to solve challenge identifier=auth.bepste.in challenge_type=dns-01 ca=https://acme.zerossl.com/v2/DV90

ERR | ts=1705397803.2720013 logger=tls.issuance.zerossl.acme_client msg=cleaning up solver identifier=ha.bepste.in challenge_type=dns-01 error=no memory of presenting a DNS record for "_acme-challenge.ha.bepste.in" (usually OK if presenting also failed)

ERR | ts=1705397803.3844292 logger=tls.issuance.zerossl.acme_client msg=cleaning up solver identifier=auth.bepste.in challenge_type=dns-01 error=no memory of presenting a DNS record for "_acme-challenge.auth.bepste.in" (usually OK if presenting also failed)

ERR | ts=1705397804.189924 logger=tls.obtain msg=could not get certificate from issuer identifier=ha.bepste.in issuer=acme.zerossl.com-v2-DV90 error=[ha.bepste.in] solving challenges: presenting for challenge: adding temporary record for zone "in.": got error status: HTTP 400: [{Code:6003 Message:Invalid request headers}]
(order=https://acme.zerossl.com/v2/DV90/order/E4fGXkeprL9I6fehPXnXJA) (ca=https://acme.zerossl.com/v2/DV90)
ERR | ts=1705397804.1899967 logger=tls.obtain msg=will retry error=[ha.bepste.in] Obtain: [ha.bepste.in] solving challenges: presenting for challenge: adding temporary record for zone "in.": got error status: HTTP 400: [{Code:6003 Message:Invalid request headers}] (order=https://acme.zerossl.com/v2/DV90/order/E4fGXkeprL9I6fehPXnXJA) (ca=https://acme.zerossl.com/v2/DV90) attempt=2 retrying_in=120 elapsed=87.84178459 max_duration=2592000

...
ERR | ts=1705397924.6950674 logger=tls.obtain msg=could not get certificate from issuer identifier=ha.bepste.in issuer=acme-v02.api.letsencrypt.org-directory error=[ha.bepste.in] solving challenges: presenting for challenge: adding temporary record for zone "in.": got error status: HTTP 400: [{Code:6003 Message:Invalid request headers}] (order=https://acme-staging-v02.api.letsencrypt.org/acme/order/130971514/13714058164) (ca=https://acme-staging-v02.api.letsencrypt.org/directory)

ERR | ts=1705397924.8005202 logger=tls.issuance.acme.acme_client msg=cleaning up solver identifier=auth.bepste.in challenge_type=dns-01 error=no memory of presenting a DNS record for "_acme-challenge.auth.bepste.in" (usually OK if presenting also failed)

etc.. etc...

This has been going on for months and I've been trying to troubleshoot to no avail. Shouldn't it be adding a record for zone "bepste.in"?? I'm very confused at this point and am not sure what I'm doing wrong.

Invalid request headers means that your API key is incorrect or has the wrong permissions I think.

Is this correct?

 Sorry for wasting your time! Thanks for the assist!


Remove version: igoogolx.lux version 1.4.1

This version is older than what has been set in max-versions-to-keep by the publisher.
Microsoft Reviewers: Open in CodeFlow

/azp run

URL: https://github.com/igoogolx/lux/releases/download/v1.4.1/lux-1.4.1+1.4.1-windows-setup.exe
OK
(Automated message - build 911)


context-minimals: 2023.09.04 19:10

Updated patches: https://github.com/bb010g/context/tree/nix-reproducibility

Appreciate the patches! Thanks!!


Catalog/Apps: values.yaml preview blank in UI

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):
Start process to create an app from the library, cert-manager works. You'll notice after filling out the form and click preview there is nothing there.
Other details that may be helpful:
It is populated when using the drop down to view a different file from the chart and then go back to values.yaml.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.2.4

Verified on 2.2.4 -- seems to be just an initial render/load issue.

Version: v2.2.4
Reproduced the issue. values.yaml is not rendered.
Version: master-head (8/6/19)
Values.yaml is now rendered in the UI:

This works upon create app or upgrade without any issues. No JS errors.


[Bug]: tsp-openapi3: automatic doc newlines break code spans

Describe the bug
the tsp-openapi3 tool (as of<EMAIL_ADDRESS>automatically breaks long documentation lines into newlines.
For example, the following description:
"description": "An array containing the type names of the sections of this text. The length of sectionNames gives the depth of the structure of this text. For example, Kohelet `([\"Chapter\", \"Verse\"])` has depth 2, while Mishneh Torah `([\"Book\", \"Topic\", \"Section\", \"Law\"])` has depth 4. Comparing this depth to the depth of sections will show if the request was for the lowest level, or a higher level, of the text.",

results in this output:
/**
* An array containing the type names of the sections of this text. The length of
* sectionNames gives the depth of the structure of this text. For example,
* Kohelet `(["Chapter", "Verse"])` has depth 2, while Mishneh Torah `(["Book",
* "Topic", "Section", "Law"])` has depth 4. Comparing this depth to the depth of
* sections will show if the request was for the lowest level, or a higher level,
* of the text.
*/

This results in an error being thrown during the conversion because one of the code spans has been split between two different lines:
error: {
    code: 'unterminated',
    severity: 'error',
    message: 'Unterminated doc code span.',
    target: { file: [Object], pos: 9845, end: 9855 }
  }

I personally don't think this long-line-breaking is desirable behavior for a migration (at the very least, it should be optional for people who need maximum fidelity for a tool like ReadMe), but at the very least, it should either (a) be disable-able, or (b) be smart enough to not break code spans.
Reproduction

Download https://github.com/Sefaria/Sefaria-Project/blob/6faae1e92f428c05daae64d256b891f2e055dd2e/docs/openAPI.json
Run npx -p @typespec/openapi3@next tsp-openapi3 openAPI.json --output-dir tsp

Checklist

[X] Follow our Code of Conduct
[X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

@Arithmomaniac Thank you for opening up this issue!
#3839 should address this. The tool will no longer automatically add line breaks but will still honor line breaks that exist in the original documentation string.


feat: Can the preheating capability be added to newly created pods?

Description
For the application of Java technology stack, directly accepting the full amount of traffic after the pod is healthy will cause excessive timeout problems. Can the initial weight be set smaller for newly created pods (including elastic expansion or rolling updates), and every certain interval Time increases until it returns to the default weight.

@Donghui0 This slow start capability is currently not supported


chore: updating dependabot groups

Description
As title says. Cleaning up old deps and rules that are not triggering properly.
Issue linked
No issue linked
Checklist

[X] I have reviewed my changes before submitting this pull request.
[X] I have assigned this PR to myself.
[X] I have made sure that the title of my PR follows Conventional commits style (e.g. feat: extrude circle to cylinder)

@AlejandroFernandezLuces can you approve?


Generate static yamls on release

With each release, we should generate the static manifests from the helm and place them under deploy/manifests.
Perhaps we need to extend the functionality of the existing workflow

Hi @davidkornel, if I get this right, this would be very helpful, as I'd be able to use the manifests through Kustomize (kubectl apply -k) without Helm. Not sure if the static manifests are up-to-date right now.

hi @davidknezic, my bad I forgot to update them with the latest release, they are still at v0.15.0. I'll try to update them tonight. Feel free to send a ping if I forget to update.

@davidknezic they should be up-to-date know. As it was stated in the commit message by default the legacy dataplane mode is used, however a sample Dataplane CR is also provided. If you wish to use the dataplane mode:

change the dataplane-mode flag to managed in the stunner-gateway-operator-manifests.yaml file
remove the stunner-manifests.yaml file


"Bad state: Redis needs to be enabled to use this method" Error on SessionManager.signOut()

Describe the bug
Since the update to 2.1.0 i recognized an issue, when i want to logout an User.
To Reproduce
Steps to reproduce the behavior:

Go to 'Sign in a user with the SessionManager'
Click on 'Signout with the SessionManager.signOut() Method'
See error:
CALL: serverpod_auth.status.signOut duration: 8ms numQueries: 1 authenticatedUser: 1 Bad state: Redis needs to be enabled to use this method 0      MessageCentral.postMessage (package:serverpod/src/server/message_central.dart:52:9) 1      MessageCentralAccess.authenticationRevoked (package:serverpod/src/server/session.dart:639:43) 2      UserAuthentication.signOutUser (package:serverpod_auth_server/src/business/user_authentication.dart:51:10) <asynchronous suspension> 3      StatusEndpoint.signOut (package:serverpod_auth_server/src/endpoints/status_endpoint.dart:21:5) <asynchronous suspension> 4      Server._handleUriCall (package:serverpod/src/server/server.dart:494:20) <asynchronous suspension> 5      Server._handleRequest (package:serverpod/src/server/server.dart:293:18) <asynchronous suspension> 6      Server._handleRequestWithErrorBoundary (package:serverpod/src/server/server.dart:182:5) <asynchronous suspension>

Expected behavior
Don´t get this Exception.
Screenshots
If applicable, add screenshots to help explain your problem.
Serverpod versions

_CLI Version: 2.1.0
_Library version: 2.1.0

Platform information
On which platforms do you experience the issue. Please provide as much information here as you can. Where are you running the server, which front end device are you using?
Additional context
I think the problem is in the session.dart on line 642. Here it call postMessage with the fixed variable global = true. As i can read in the Documentation, this should cause the error. I am new as dev and i think anyone else can evaluate it better than me.

I've upgraded CLI and all serverpod packages to 2.1.1 .  but still get the same error when trying to log out.
I/flutter ( 7521): Failed call: serverpod_auth.status.signOut
I/flutter ( 7521): ServerpodClientException: Internal server error, statusCode = 500

Server logs
CALL: serverpod_auth.status.signOut duration: 9ms numQueries: 1 authenticatedUser: 3
Bad state: Redis needs to be enabled to use this method
#0      MessageCentral.postMessage (package:serverpod/src/server/message_central.dart:52:9)
#1      MessageCentralAccess.authenticationRevoked (package:serverpod/src/server/session.dart:639:43)
#2      UserAuthentication.signOutUser (package:serverpod_auth_server/src/business/user_authentication.dart:51:10)
<asynchronous suspension>
#3      StatusEndpoint.signOut (package:serverpod_auth_server/src/endpoints/status_endpoint.dart:21:5)
<asynchronous suspension>
#4      Server._handleUriCall (package:serverpod/src/server/server.dart:494:20)
<asynchronous suspension>
#5      Server._handleRequest (package:serverpod/src/server/server.dart:293:18)
<asynchronous suspension>
#6      Server._handleRequestWithErrorBoundary (package:serverpod/src/server/server.dart:182:5)
<asynchronous suspension>


Automatically discover build task files in the app directory?

https://github.com/hydephp/develop/blob/6c08e2c33b35dea8064494d5ab0d0e897e4b2961/packages/framework/src/Services/BuildHookService.php#L33

Fixed in https://github.com/hydephp/develop/pull/458


[Analyze External Table] Support analyze external table to collect statistics

Feature request
we are working on support analyze external table, iceberg first.
there are several step to do.

[x] refactor native analyze. https://github.com/StarRocks/starrocks/pull/23326
[x] collect external table statistics of table level. https://github.com/StarRocks/starrocks/pull/23493
[x] query external table statistics of table level. https://github.com/StarRocks/starrocks/pull/23881
[ ] cache of iceberg.
[ ] collect external table statistics of partition level

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

Don't external tables support column statistics, such as ndv?

Can the exterior also support the hll algorithm, for example hive should not support hll, how to calculate ndv in this case

Yes, SR could compute external table's ndv by hll algorithm, and store these statistics as SR native table


[Bug]: upgrade to 2.3.0 failing

The problem
Something after upgrade to 2.3.0 stopped working, directly after upgrade I see errors in log related to multiple entities (climate and tiles).
What version of Tech Controllers integration has the issue?
v2.3.0
What version of Home Assistant Core has the issue?
core-2025.5.2
What was the last working version of Tech Controller integration?
v2.2.1
Diagnostics information
No response
Anything in the logs that might be useful for us?
2024-05-07 10:58:09.561 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up tech platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/binary_sensor.py", line 45, in async_setup_entry
    entities.append(RelaySensor(tile, coordinator, config_entry))
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tech/binary_sensor.py", line 92, in __init__
    TileBinarySensor.__init__(self, device, coordinator, config_entry)
  File "/config/custom_components/tech/entity.py", line 38, in __init__
    if self._config_entry.data[INCLUDE_HUB_IN_NAME]:
       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'
2024-05-07 10:58:09.659 ERROR (MainThread) [homeassistant.components.climate] Error while setting up tech platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/climate.py", line 46, in async_setup_entry
    TechThermostat(zones[zone], coordinator, config_entry) for zone in zones
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tech/climate.py", line 69, in __init__
    if not self._config_entry.data[INCLUDE_HUB_IN_NAME]
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'
2024-05-07 10:58:09.841 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up tech platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/sensor.py", line 87, in async_setup_entry
    TileTemperatureSignalSensor(
  File "/config/custom_components/tech/sensor.py", line 1182, in __init__
    TileSensor.__init__(self, device, coordinator, config_entry)
  File "/config/custom_components/tech/entity.py", line 38, in __init__
    if self._config_entry.data[INCLUDE_HUB_IN_NAME]:
       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'
2024-05-07 10:58:57.325 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up tech platform for binary_sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/binary_sensor.py", line 45, in async_setup_entry
    entities.append(RelaySensor(tile, coordinator, config_entry))
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tech/binary_sensor.py", line 92, in __init__
    TileBinarySensor.__init__(self, device, coordinator, config_entry)
  File "/config/custom_components/tech/entity.py", line 38, in __init__
    if self._config_entry.data[INCLUDE_HUB_IN_NAME]:
       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'
2024-05-07 10:58:57.399 ERROR (MainThread) [homeassistant.components.climate] Error while setting up tech platform for climate
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/climate.py", line 46, in async_setup_entry
    TechThermostat(zones[zone], coordinator, config_entry) for zone in zones
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tech/climate.py", line 69, in __init__
    if not self._config_entry.data[INCLUDE_HUB_IN_NAME]
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'
2024-05-07 10:58:57.561 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up tech platform for sensor
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 356, in _async_setup_platform
    await asyncio.shield(awaitable)
  File "/config/custom_components/tech/sensor.py", line 87, in async_setup_entry
    TileTemperatureSignalSensor(
  File "/config/custom_components/tech/sensor.py", line 1182, in __init__
    TileSensor.__init__(self, device, coordinator, config_entry)
  File "/config/custom_components/tech/entity.py", line 38, in __init__
    if self._config_entry.data[INCLUDE_HUB_IN_NAME]:
       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^
KeyError: 'include_hub_in_name'

Additional information
No response

@anarion80  I think upgrade failed becuase INCLUDE_HUB_IN_NAME is not filled and config flow doesnt require to triggered again as I dont adding new integration so this default value is not passed into whole object:
https://github.com/mariusz-ostoja-swierczynski/tech-controllers/blob/67084eb630d16592db8df1d47809b95581aca317/custom_components/tech/config_flow.py#L56
what you think?

Yes, I was too quick with the release and forgot to remove the migrations. They are too complex anyway and don't account for the latest change. So the release notes will need a statement that migration is not supported and we need to remove the integration and add again.


Added missing props containerStyle

Thank you for making a good module.
I think containerStyle is not work as you intended.

+1 on this PR, can we get this in?


Angular 13 CORS on localhost

Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
After updating Angular 12 to Angular 13 we are no longer able to access our app served on localhost from outside of it, the request is being blocked by CORS.
this is what worked in Angular 12
ng s --project app-search --disable-host-check --port 4207 --deploy-url  https://localhost:4207/ --ssl --public-host https://localhost:4207/
and stopped working in Angular 13.
When in development mode we are accessing our https://localhost:4207 app from https://app-staging.cognism.com/
We were looking into the docs around Webpack 4 and Webpack 5 and we can see that the disableHostCheck flag is removed from webpack 5 doc but is in webpack 4 docs. We tried playing around with disable host check and allowed hosts passing it to ng serve per official docs (https://angular.io/cli/serve) but with no luck.
The reason why we need to access localhost is we are using single-spa as a javascript router for front-end microservices. We also tried it on a clean Angular 13 project without any modifications but we get the same behavior.
Not quite sure if this is a bug or do the flags have to be passed in a different way to enable the same behavior that we had before.
Thank you
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Access to XMLHttpRequest at 'http://localhost:4200/assets/test.csv' from origin 'https://app-dev.cognism.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.

Please provide the environment you discovered this bug in (run ng version)
Angular CLI: 13.3.2
Node: 14.15.0
Package Manager: npm 6.14.8
OS: darwin x64

Angular: 13.3.2
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1303.2
@angular-devkit/build-angular   13.3.2
@angular-devkit/core            13.3.2
@angular-devkit/schematics      13.3.2
@schematics/angular             13.3.2
rxjs                            7.5.5
typescript

Anything else?
No response

The error seems to indicate that you are trying to access a different host http://localhost:4200 from the one you mentioned initially https://localhost:4207.
Can you please provide the configuration the extract of angular.json for the mentioned application and also the command that you are running including all arguments?

Hello, thanks for the prompt answer.
The error I posted in the Please provide the exception or error you saw section is the one I got when retesting this issue with a brand new Angular 13 application.
The one we are getting in our actual dev environment looks pretty much the same
Access to XMLHttpRequest at 'https://localhost:4207/assets/files/industries-classification.json?cache$=true' from origin 'https://app-dev.cognism.com' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: It does not have HTTP ok status.
Here is the angular.json and package.json and extra-webpack config that we are using in our app. Just to mention it once again, we did test this on new app, where the angular json and package json are the default ones that the cli provides, without using custom webpack etc, and still got the same issue.
angular.json
{
  "$schema"<EMAIL_ADDRESS>  "cli": {
    "analytics": "5e1e2dd7-84aa-4127-94cf-549190794bdc",
    "defaultCollection": "@angular-eslint/schematics",
    "cache": {
      "enabled": false
    }
  },
  "version": 1,
  "newProjectRoot": "projects",
  "projects": {
    "app-search": {
      "projectType": "application",
      "schematics": {
        "@schematics/angular:component": {
          "changeDetection": "OnPush",
          "skipTests": true,
          "style": "scss"
        },
        "@schematics/angular:class": {
          "skipTests": true
        },
        "@schematics/angular:directive": {
          "skipTests": true
        },
        "@schematics/angular:guard": {
          "skipTests": true
        },
        "@schematics/angular:module": {},
        "@schematics/angular:pipe": {
          "skipTests": true
        },
        "@schematics/angular:service": {
          "skipTests": true
        },
        "@schematics/angular:resolver": {
          "skipTests": true
        }
      },
      "root": "",
      "sourceRoot": "src",
      "prefix": "app-search",
      "architect": {
        "build": {
          "builder": "@angular-builders/custom-webpack:browser",
          "options": {
            "outputPath": "dist",
            "index": "src/index.html",
            "main": "src/main.single-spa.ts",
            "polyfills": "src/polyfills.ts",
            "tsConfig": "tsconfig.app.json",
            "preserveSymlinks": true,
            "assets": ["src/favicon.ico", "src/assets"],
            "styles"<EMAIL_ADDRESS>"src/styles.scss"],
            "scripts": [],
            "customWebpackConfig": {
              "path": "extra-webpack.config.js",
              "libraryName": "app-search",
              "libraryTarget": "umd"
            },
            "deployUrl": "https://localhost:4207/"
          },
          "configurations": {
            "production": {
              "fileReplacements": [
                {
                  "replace": "src/environments/environment.ts",
                  "with": "src/environments/environment.prod.ts"
                }
              ],
              "budgets": [
                {
                  "type": "initial",
                  "maximumWarning": "2mb",
                  "maximumError": "5mb"
                },
                {
                  "type": "anyComponentStyle",
                  "maximumWarning": "6kb",
                  "maximumError": "10kb"
                }
              ],
              "outputHashing": "all"
            },
            "development": {
              "buildOptimizer": false,
              "optimization": false,
              "vendorChunk": true,
              "extractLicenses": false,
              "sourceMap": true,
              "namedChunks": true
            }
          },
          "defaultConfiguration": "production"
        },
        "serve": {
          "builder": "@angular-builders/custom-webpack:dev-server",
          "configurations": {
            "production": {
              "browserTarget": "app-search:build:production"
            },
            "development": {
              "browserTarget": "app-search:build:development"
            }
          },
          "defaultConfiguration": "development"
        },
        "extract-i18n": {
          "builder": "@angular-devkit/build-angular:extract-i18n",
          "options": {
            "browserTarget": "app-search:build"
          }
        },
        "test": {
          "builder": "@angular-devkit/build-angular:karma",
          "options": {
            "main": "src/test.ts",
            "polyfills": "src/polyfills.ts",
            "tsConfig": "tsconfig.spec.json",
            "karmaConfig": "karma.conf.js",
            "assets": ["src/favicon.ico", "src/assets"],
            "styles": ["src/styles.scss"],
            "scripts": []
          }
        },
        "lint": {
          "builder": "@angular-eslint/builder:lint",
          "options": {
            "lintFilePatterns": ["src/**/*.ts", "src/**/*.html"]
          }
        },
        "e2e": {
          "builder": "@angular-devkit/build-angular:protractor",
          "options": {
            "protractorConfig": "e2e/protractor.conf.js",
            "devServerTarget": "app-search:serve"
          },
          "configurations": {
            "production": {
              "devServerTarget": "app-search:serve:production"
            }
          }
        }
      }
    }
  },
  "defaultProject": "app-search"
}

package.json
{
  "name": "app-search",
  "version": "0.517.0",
  "scripts": {
    "ng": "ng",
    "start": "npm run serve:single-spa:app-search",
    "build": "npm run build:single-spa:app-search",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e",
    "build:single-spa:app-search": "cross-env NODE_ENV=production ng build app-search --configuration production --deploy-url /search/",
    "serve:single-spa:app-search": "cross-env NODE_ENV=development ng s --project app-search --disable-host-check --port 4207 --ssl --public-host https://localhost:4207/"
  },
  "private": true,
  "husky": {
    "hooks": {
      "prepare-commit-msg": "jira-prepare-commit-msg"
    }
  },
  "jira-prepare-commit-msg": {
    "messagePattern": "$J $M",
    "jiraTicketPattern": "(\\w+-\\w+-\\d+)"
  },
  "dependencies": {
    "@angular/animations": "~13.2.5",
    "@angular/common": "~13.2.5",
    "@angular/compiler": "~13.2.5",
    "@angular/core": "~13.2.5",
    "@angular/flex-layout": "^13.0.0-beta.38",
    "@angular/forms": "~13.2.5",
    "@angular/localize": "~13.2.5",
    "@angular/platform-browser": "~13.2.5",
    "@angular/platform-browser-dynamic": "~13.2.5",
    "@angular/router": "~13.2.5",
    "@cognism/app-library": "0.0.586",
    "@fortawesome/angular-fontawesome": "^0.10.2",
    "@fortawesome/fontawesome-svg-core": "^6.1.1",
    "@fortawesome/free-brands-svg-icons": "^6.1.1",
    "@fortawesome/pro-duotone-svg-icons": "^6.1.1",
    "@fortawesome/pro-light-svg-icons": "^6.1.1",
    "@fortawesome/pro-regular-svg-icons": "^6.1.1",
    "@fortawesome/pro-solid-svg-icons": "^6.1.1",
    "@ng-bootstrap/ng-bootstrap": "^10.0.0",
    "@ng-select/ng-select": "^8.1.1",
    "@ngneat/cashew": "^1.3.2",
    "@ngneat/until-destroy": "^9.0.0",
    "@ngx-loading-bar/core": "^6.0.2",
    "@types/lodash": "^4.14.179",
    "awesome-phonenumber": "^2.69.0",
    "bootstrap": "^4.6.1",
    "class-transformer": "^0.5.1",
    "install": "^0.13.0",
    "lodash": "^4.17.21",
    "ng-zorro-antd": "^13.1.1",
    "ngx-ellipsis": "^3.1.6",
    "ngx-pagination": "^5.1.1",
    "npm": "^7.24.0",
    "rxjs": "~7.5.4",
    "rxjs-web-observers": "^1.0.2",
    "single-spa": "^5.9.3",
    "single-spa-angular": "^6.0.2",
    "tslib": "^2.3.1",
    "xng-breadcrumb": "^7.2.0",
    "zone.js": "~0.11.5"
  },
  "devDependencies": {
    "@angular-builders/custom-webpack": "^13.1.0",
    "@angular-devkit/build-angular": "~13.2.5",
    "@angular-eslint/builder": "^13.1.0",
    "@angular-eslint/eslint-plugin": "^13.1.0",
    "@angular-eslint/eslint-plugin-template": "^13.1.0",
    "@angular-eslint/schematics": "13.1.0",
    "@angular-eslint/template-parser": "^13.1.0",
    "@angular/cli": "~13.2.5",
    "@angular/compiler-cli": "~13.2.5",
    "@angular/language-service": "^13.2.5",
    "@tailwindcss/aspect-ratio": "^0.4.0",
    "@tailwindcss/forms": "^0.4.0",
    "@tailwindcss/line-clamp": "^0.3.0",
    "@tailwindcss/typography": "^0.5.0",
    "@types/jasmine": "~3.6.0",
    "@types/node": "^14.14.22",
    "@typescript-eslint/eslint-plugin": "5.1.0",
    "@typescript-eslint/parser": "4.28.2",
    "autoprefixer": "^10.4.0",
    "cross-env": "^7.0.3",
    "eslint": "^8.0.0",
    "eslint-plugin-import": "latest",
    "eslint-plugin-jsdoc": "latest",
    "eslint-plugin-prefer-arrow": "latest",
    "husky": "^4.3.7",
    "jasmine-core": "~3.6.0",
    "jasmine-spec-reporter": "~6.0.0",
    "jira-prepare-commit-msg": "^1.5.2",
    "karma": "~6.3.17",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage": "~2.0.3",
    "karma-jasmine": "~4.0.0",
    "karma-jasmine-html-reporter": "^1.5.0",
    "ngx-tailwind": "^3.0.0",
    "postcss": "^8.4.5",
    "postcss-import": "^14.0.2",
    "postcss-loader": "^6.2.1",
    "postcss-scss": "^4.0.3",
    "protractor": "~7.0.0",
    "styles-loader": "^3.0.0",
    "tailwindcss": "^3.0.23",
    "ts-node": "~10.7.0",
    "typescript": "~4.5.5",
    "webpack-merge": "^5.8.0"
  }
}

webpack config
const singleSpaAngularWebpack = require('single-spa-angular/lib/webpack').default;
const webpackMerge = require('webpack-merge');

module.exports = (angularWebpackConfig, options) => {
  const singleSpaWebpackConfig = singleSpaAngularWebpack(angularWebpackConfig, options);

//https://github.com/single-spa/single-spa-angular/issues/328
  singleSpaWebpackConfig.entry.main = [...new Set(singleSpaWebpackConfig.entry.main)];

  singleSpaWebpackConfig.externals = [/^@cognism\/app-common/];

  const merged = webpackMerge.merge(singleSpaWebpackConfig, {
    module: {
      rules: [
        {
          test: /\.scss$/,
          loader: 'postcss-loader',
          options: {
            postcssOptions: {
              ident: 'postcss',
              syntax: 'postcss-scss',
              plugins: [
                require('postcss-import'),
                require('tailwindcss'),
                require('autoprefixer'),
              ],
            },
          },
        },
      ],
    },
  })
  return merged
};

Is there any additional work we can do to further investigate this issue?
We did reach out to Webpack with an opened issue https://github.com/webpack/webpack/issues/15752 and it seems we instead of disableHostCheck we should set allowedHosts: "all". We have not managed to solve it.

When using disableHostCheck, Webpack's allowedHosts is set to all. https://github.com/angular/angular-cli/blob/1c634cd327e5a850553b258aa2d5e6a6b2c75c65/packages/angular_devkit/build_angular/src/webpack/configs/dev-server.ts#L277-L281
Providing a reproduction would definitly help us investigate and resolve the issue. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.
This might be related to your directory structure so its really important to get an accurate repro to diagnose this.

I'm sorry, but we can't reproduce the problem following the instructions you provided.
If the problem persists, please open a new issue following our submission guidelines.
A good way to make a minimal repro is to create a new app via ng new repro-app and add the minimum possible code to show the problem. Then you can push this repository to github and link it here.

Unfortunately we still have not found the solution.
Its hard to make a minima repro since the issue is related to accessing resources from an outside domain that are served on localhost. So putting it up on stackblitz does not really help. Plus we have to setup single-spa to reproduce the issue, or make a similar setup where another domain is accessing localhost.
As we did zero code changes other than upgrading from angular 12 to angular 13 it seems to indicate that the issue lies somewhere in angular or how they setup/use webpack or whatnot.
We plan to investigate it a bit further as we are now stuck on angular 12 because of this, so if we find anything ill paste it here.

We did have other similar reports recently and appears that this issue only occurs when using  occurs when using the non official @angular-builders/custom-webpack builders.


Using pipenv installed under pipx gives "Pipenv found itself running within a virtual environment"

Issue description
I have pipenv installed using pipx, which means that it's installed in a venv. This is deliberate, as I do not want to install pipenv and all its dependencies in my system Python, and there's no other recommended approach in the pipenv docs for how to install pipenv standalone.
When I run pipenv, I get the error "Pipenv found itself running within a virtual environment". However, I see no evidence that pipenv didn't create a virtual environment, nor do I see any problems resulting from running pipenv in this way.
Note There are a number of duplicates for this issue, but they all refer to MacOS and (as far as I can see) the Homebrew version of Python. This report is for Windows using the normal python.org installer. Please do not close this as a duplicate without ensuring that whichever issue is being treated as the "master" is updated to note that it is not a MacOS specific problem.
Expected result

Not to get a "Courtesy Notice" that is neither helpful nor, as far as I can see, accurate.
Not to have to set environment variables to use pipenv normally.

Actual result
When possible, provide the verbose output (--verbose), especially for locking and dependencies resolving issues.
PS 17:30 {00:01.134} D:\Work\Scratch\pypidata
>pipenv run python -c "import sys; print(sys.executable)"
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
C:\Users\Gustav\.virtualenvs\pypidata-OL7vfyqD\Scripts\python.exe

Note that sys.executable is in a pipenv-created directory, so it apparently did create one...
Steps to replicate
See above.
$ pipenv --support
Pipenv version: '2020.6.2'
Pipenv location: 'c:\\users\\gustav\\.local\\pipx\\venvs\\pipenv\\lib\\site-packages\\pipenv'
Python location: 'c:\\users\\gustav\\.local\\pipx\\venvs\\pipenv\\scripts\\python.exe'
Python installations found:

3.8.5: C:\Users\Gustav\AppData\Local\Programs\Python\Python38\python.exe

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.8.5',
 'os_name': 'nt',
 'platform_machine': 'AMD64',
 'platform_python_implementation': 'CPython',
 'platform_release': '10',
 'platform_system': 'Windows',
 'platform_version': '10.0.19041',
 'python_full_version': '3.8.5',
 'python_version': '3.8',
 'sys_platform': 'win32'}

System environment variables:

ALLUSERSPROFILE
APPDATA
COMMONPROGRAMFILES
COMMONPROGRAMFILES(X86)
COMMONPROGRAMW6432
COMPUTERNAME
COMSPEC
DRIVERDATA
GIT_INSTALL_ROOT
HOMEDRIVE
HOMEPATH
LOCALAPPDATA
LOGONSERVER
NUMBER_OF_PROCESSORS
ONEDRIVE
ONEDRIVECONSUMER
OS
PATH
PATHEXT
POWERSHELL_DISTRIBUTION_CHANNEL
PROCESSOR_ARCHITECTURE
PROCESSOR_IDENTIFIER
PROCESSOR_LEVEL
PROCESSOR_REVISION
PROGRAMDATA
PROGRAMFILES
PROGRAMFILES(X86)
PROGRAMW6432
PSMODULEPATH
PUBLIC
SYSTEMDRIVE
SYSTEMROOT
TEMP
TMP
USERDOMAIN
USERDOMAIN_ROAMINGPROFILE
USERNAME
USERPROFILE
VIRTUAL_ENV_DISABLE_PROMPT
WINDIR
WORK_DIRECTORY
WSLENV
WT_PROFILE_ID
WT_SESSION
PIP_DISABLE_PIP_VERSION_CHECK
PYTHONDONTWRITEBYTECODE
PIP_SHIMS_BASE_MODULE
PIP_PYTHON_PATH
PYTHONFINDER_IGNORE_UNSUPPORTED

PipenvÔÇôspecific environment variables:
DebugÔÇôspecific environment variables:

PATH: C:\Program Files\PowerShell\7;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\PowerShell\7\;C:\Program Files\Docker\Docker\resources\bin;C:\ProgramData\DockerDesktop\version-bin;C:\Users\Gustav\scoop\apps\cyg\current\bin;C:\Users\Gustav\scoop\shims;C:\Users\Gustav\AppData\Local\Microsoft\WindowsApps;C:\Users\Gustav\.local\bin;C:\Users\Gustav\.local\scripts;C:\Users\Gustav\AppData\Local\Microsoft\WindowsApps;C:\Users\Gustav\AppData\Local\Programs\Microsoft VS Code\bin

Contents of Pipfile ('D:\Work\Scratch\pypidata\Pipfile'):
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
requests = "*"
mousebender = "*"

[requires]
python_version = "3.8"

Contents of Pipfile.lock ('D:\Work\Scratch\pypidata\Pipfile.lock'):
{
    "_meta": {
        "hash": {
            "sha256": "6d4c907ebdbb3297b0bd85f38e0c82f7ae7d5097192f1c8b85ce25de8c7abff2"
        },
        "pipfile-spec": 6,
        "requires": {
            "python_version": "3.8"
        },
        "sources": [
            {
                "name": "pypi",
                "url": "https://pypi.org/simple",
                "verify_ssl": true
            }
        ]
    },
    "default": {
        "attrs": {
            "hashes": [
                "sha256:08a96c641c3a74e44eb59afb61a24f2cb9f4d7188748e76ba4bb5edfa3cb7d1c",
                "sha256:f7b7ce16570fe9965acd6d30101a28f62fb4a7f9e926b3bbc9b61f8b04247e72"
            ],
            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3'",
            "version": "==19.3.0"
        },
        "certifi": {
            "hashes": [
                "sha256:5930595817496dd21bb8dc35dad090f1c2cd0adfaf21204bf6732ca5d8ee34d3",
                "sha256:8fc0819f1f30ba15bdb34cceffb9ef04d99f420f68eb75d901e9560b8749fc41"
            ],
            "version": "==2020.6.20"
        },
        "chardet": {
            "hashes": [
                "sha256:84ab92ed1c4d4f16916e05906b6b75a6c0fb5db821cc65e70cbd64a3e2a5eaae",
                "sha256:fc323ffcaeaed0e0a02bf4d117757b98aed530d9ed4531e3e15460124c106691"
            ],
            "version": "==3.0.4"
        },
        "idna": {
            "hashes": [
                "sha256:b307872f855b18632ce0c21c5e45be78c0ea7ae4c15c828c20788b26921eb3f6",
                "sha256:b97d804b1e9b523befed77c48dacec60e6dcb0b5391d57af6a65a312a90648c0"
            ],
            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3'",
            "version": "==2.10"
        },
        "mousebender": {
            "hashes": [
                "sha256:a6f9adfbd17bfb0e6bb5de9a27083e01dfb86ed9c3861e04143d9fd6db373f7c",
                "sha256:c5953026378e5dcc7090596dfcbf73aa5a9786842357273b1df974ebd79bd760"
            ],
            "index": "pypi",
            "version": "==2.0.0"
        },
        "packaging": {
            "hashes": [
                "sha256:4357f74f47b9c12db93624a82154e9b120fa8293699949152b22065d556079f8",
                "sha256:998416ba6962ae7fbd6596850b80e17859a5753ba17c32284f67bfff33784181"
            ],
            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3'",
            "version": "==20.4"
        },
        "pyparsing": {
            "hashes": [
                "sha256:c203ec8783bf771a155b207279b9bccb8dea02d8f0c9e5f8ead507bc3246ecc1",
                "sha256:ef9d7589ef3c200abe66653d3f1ab1033c3c419ae9b9bdb1240a85b024efc88b"
            ],
            "markers": "python_version >= '2.6' and python_version not in '3.0, 3.1, 3.2'",
            "version": "==2.4.7"
        },
        "requests": {
            "hashes": [
                "sha256:b3559a131db72c33ee969480840fff4bb6dd111de7dd27c8ee1f820f4f00231b",
                "sha256:fe75cc94a9443b9246fc7049224f75604b113c36acb93f87b80ed42c44cbb898"
            ],
            "index": "pypi",
            "version": "==2.24.0"
        },
        "six": {
            "hashes": [
                "sha256:30639c035cdb23534cd4aa2dd52c3bf48f06e5f4a941509c8bafd8ce11080259",
                "sha256:8b74bedcbbbaca38ff6d7491d76f2b06b3592611af620f8426e82dddb04a5ced"
            ],
            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2'",
            "version": "==1.15.0"
        },
        "urllib3": {
            "hashes": [
                "sha256:91056c15fa70756691db97756772bb1eb9678fa585d9184f24534b100dc60f4a",
                "sha256:e7983572181f5e1522d9c98453462384ee92a0be7fac5f1413a1e35c56cc0461"
            ],
            "markers": "python_version >= '2.7' and python_version not in '3.0, 3.1, 3.2, 3.3, 3.4' and python_version < '4'",
            "version": "==1.25.10"
        }
    },
    "develop": {}
}

Can you please have a try against the master branch to see if the issue is gone? Will cut a new release shortly if so.

No, it still happens in master, I'm afraid.
>pipenv --version
pipenv, version 2020.6.2.dev0
>pipenv
Courtesy Notice: Pipenv found itself running within a virtual environment, so it will automatically use that environment, instead of creating its own for any project. You can set PIPENV_IGNORE_VIRTUALENVS=1 to force pipenv to ignore that environment and create its own instead. You can set PIPENV_VERBOSITY=-1 to suppress this warning.
Usage: pipenv [OPTIONS] COMMAND [ARGS]...

Just to clarify here - I do have pipenv running in a virtualenv. So the initial part of the "courtesy notice" is correct. What is not correct, as far as I can see, is the statement that it will "automatically use that environment". It doesn't, and furthermore I don't want it to. I want to be able to install pipenv in an isolated environment, not in my system (or user) site-packages, and have it work.
In practice, the issue here is that the message and the behaviour don't match - and what I want is the current behaviour, but not the (incorrect) message.
I'm not clear why anyone would want pipenv to automatically use an existing virtual environment. And in practice, nothing I've tried has been able to provoke it to do so...

Update: Looking through the source, I see that one difference which may be relevant here is that I run pipenv using my virtualenv Python, but I do not activate that virtualenv. So sys.executable is in a virtualenv, and is_in_virtualenv will therefore be true, but the virtualenv is not on PATH, and VIRTUAL_ENV is not set (so Project.virtualenv_location won't see the environment pipenv is installed in).