ref(scheduler): fetch object storage credentials from API instead of local secret

For now fetch the minio credentials from the API
ref #458
ref #521
Note: I can change it to to object-storage if someone points me to the doc what to use instead

Current coverage is 82.90%

Merging #523 into master will not affect coverage as of 7484d78

@@            master   #523   diff @@
=====================================
  Files           32     32
  Stmts         1919   1919
  Branches       271    271
  Methods          0      0
=====================================
  Hit           1591   1591
  Partial         61     61
  Missed         267    267

Review entire Coverage Diff as of 7484d78

Powered by Codecov. Updated on successful CI builds.

is this going in for beta? object storage secret is not yet implemented in slugrunner

This can go into beta if I just keep it as minio-user which is what slugrunner expects based on what you said

Also this requires a change in helm charts removing secret volume mount in controller rc

https://github.com/deis/charts/pull/168

Ref https://github.com/deis/workflow/issues/97

@helgi has this been tested?

if this is going in we should hold off the current testing and wait for the new images

Looks like it's already merged :)

Already merged and master for it was already built https://travis-ci.org/deis/controller/builds/116716881

oops my bad


Ideas to improve header visualization

Hello!
I have some ideas for improving the display of headers in HTTPie.  Please let me know which ones you agree with and I'll see if I can implement them right away.

If the value of any header matches the RFC 2616 allowed date formats, add a parenthetic, colored message at the end of the header stating how long ago/how long from now the date is, e.g.:
Date: Sun, 14 Feb 2021 18:47:43 GMT
Expires: Tue, 16 Mar 2021 18:47:43 GMT  (30 days from now)

Color the values of the Cookie/Set-Cookie headers because developers frequently inspect them

Add a colored, parenthetic, formatted version of the value of Content-Length headers:
Content-Length: 5934  (5.93 kB)

What do you think @jakubroztocil @Almad?

@bl-ue I like your ideas. They add a nice human touch, which is an important principle behind httpie’s design.
To summarize, there’re two broader ideas here:

Provide deeper, header-specific syntax highlighting (e.g., for Cookie and Set-Cookie).
Humanize header data (e.g, lengths & dates).

Improving the syntax highlighting should be quite straightforward (please feel free to create a new issue for this).
Simply adding humanized versions of headers with data, though, would break backward-compatibility and also the current principle of not altering the message structure.  So there’s some product design thinking on my part to be done here.

and also the current principle of not altering the message structure.

I wondered if there was something like that behind HTTPie.  That's actually why I added two spaces before the parentheses, I know that's a great way to distinguish between the original text and the added text!
What would you do in that case?  Add a --humanize option that adds humanization with a warning/info in the help that the output will not be the exact output?
Techinically, with colors, the output is already completely athwart the original, because the ANSI escape codes used to output color are not included in the HTTP spec :smile: but I know, you mean visually.

Improving the syntax highlighting should be quite straightforward (please feel free to create a new issue for this).

You mean to discuss/advertise this change?

I wondered if there was something like that behind HTTPie. That's actually why I added two spaces before the parentheses, I know that's a great way to distinguish between the original text and the added text!

The idea is to make it easy for the user to copy the output and paste it, for example, into their API documentation. So although the spaces help visually, the extra output still breaks this use case.

What would you do in that case? Add a --humanize option that adds humanization with a warning/info in the help that the output will not be the exact output?

The toggle should be based on --format-options (which I completely forgot about for a moment).
Something like: --format-options headers.humanize:true.
Additionally, we could introduce a more general --humanize as a shortcut similar to --sorted / --unsorted (which toggles both headers.sort:true and json.sort_keys:true).
Separately decide what should the default be.

Techinically, with colors, the output is already completely athwart the original, because the ANSI escape codes used to output color are not included in the HTTP spec 😄 but I know, you mean visually.

You can still copy the output and paste it into your API documentation without any cleanup.

Improving the syntax highlighting should be quite straightforward (please feel free to create a new issue for this).

You mean to discuss/advertise this change?

The syntax highlighting improvement is a separate topic so it should have its own GitHub issue.


crud functionalities for question service

added crud functionalities for questions service

able to find question by id
able to find question by title
able to create question
able to update question by id
able to delete question by id

@chiewyx LGTM, maybe for the routing, I can add authentication middleware to ensure only authorized users can modify question data?

@chiewyx LGTM, maybe for the routing, do we add authentication middleware to ensure only authorised users can modify question data?

yep can, do we merge first or do it in the same pr?

Oh nice, added in this PR right? LGTM


Implement equality in the parsed Datalog syntax

For any of these cases
ans(x):-Q(x, y), y==2
ans(x):-Q(x, y), (y==2)
ans(x):-Q(x, y), (y=2)

@Jbat1Jumper if you could help with this, it would be great

Solved in #621


switchLocalePath() doesn't work in plugins

Version
v5.3.0
Reproduction link
https://codesandbox.io/embed/nuxt-i18n-switchlocalepath-bug-dbi7h
Steps to reproduce
Create a Nuxt plugin and try using switchLocalePath() in it.
What is expected ?
Function working: returning the locale path for the desired locale.
What is actually happening?
Function crashes with error:

Cannot destructure property params of 'undefined' or 'null'.
const { params, ...routeCopy } = this.$route

Additional comments?
I'm using nuxt 2.10.0 and nuxt-i18n 6.3.0

This bug report is available on Nuxt community (#c318)

Hey @rchl, any update on this? :)
If you have a workaround, it would be very helpful 🙏

No workarounds. It needs a proper fix that requires some refactoring. Seems like this was never supported so it's not a trivial bug fix


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Google Icon

Icon name
Google
Use cases
I need this icon for login with google button.
Design ideas
It should be like the other minimal google icon logo
Checklist

[X] I have searched if someone has submitted a similar issue before and there weren't any. (Please make sure to also search closed issues, as this issue might already have been resolved.)
[X] I have searched existing icons to make sure it does not already exist and I didn't find any.
[X] I am not requesting a brand logo and the art is not protected by copyright.
[X] I am not requesting an icon that includes religious, political imagery or hate symbols.
[X] I have provided appropriate use cases for the icon(s) requested.

This is a brand icon

Removing Icons is a breaking change, we are not rolling out breaking changes until the preparations for v1 are done.
https://lucide-studio.vercel.app/?value=<svg++xmlns="http://www.w3.org/2000/svg"++width="24"++height="24"++viewBox="0+0+24+24"++fill="none"++stroke="currentColor"++stroke-width="2"++stroke-linecap="round"++stroke-linejoin="round">++<path+d="M20.945+11a9+9+0+1+1-3.284-5.997l-2.655+2.392A5.5+5.5+0+1+0+17.125+14H13v-3z"+/></svg>


Merge ampform notebooks

All example notebooks for amplitude analysis have been isolated under tensorwaves.rtfd.io/en/latest/amplitude-analysis. Examples under usage show more general expressions.
Closes #379

Note that the AmpForm notebooks could in theory be moved to a separate website or package now, like compwa-org.rtfd.io.


operators [CI] sosivio (1.2.1)

Signed-off-by: Dan Arlowski<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

hey @J0zi  & @mvalarh
getting the same error on both here and the openshift community repo
can you help me understand? cant figure it out.
Thanks!

/unhold

/merge possible

/merge possible

/merge possible

Waiting for @etaysosiv,@EthanSosivio to approve

approve

/merge possible


GlosSI cannot use internet shortcuts

Expected Behavior
Launching game via wemod shortcut to autolaunch game with WeMod Trainer active
Actual Behavior
GlosSI does not see the game and fails to start
Steps to Reproduce the Problem

Make a shortcut to desktop with WeMod
Add the shortcut to GlosSI and add to steam
Launch newly made GlosSI shortcut in steam

General Information

The shortcut is a web url. It has no targets.

Then use the URL directly as path, as that is also supported ;P


Import-autocompletion ignores import prefix config

mod foo {
    pub mod bar {
        pub struct Item;
    }
}

use crate::foo::bar;

fn main() {
	$0
}

Fuzzy importing Item causes the following, with importPrefix set to by_crate:
// <snip>
use bar::Item;

use crate::foo::bar;

fn main() {
    Item
}

On the other hand the import assist gives us the expected use crate::foo::bar::{self, Item};
Similarly without the existing import we get the import use foo::bar::Item; which is also incorrect as it is missing the crate prefix.

cc @SomeoneToIgnore


How does MINT get all accounts?

I have tried everything I could think of, changing scopes, adding parameters to the authorize url, and it still only returns one account.
Does MINT have special privileges or access to a beta SDK?

They use the old API key system which we are told NOT to use.


Helm V3 support

For various reasons, the use of Helm v2 is not recommended for new installations - especially for security reasons.
I saw on other issue that the support of Helm V3 was not planned before the end of the year ( https://github.com/mattermost/mattermost-helm/pull/132#issuecomment-576564457 ).
It is also mentioned in this issue that "Helm v3 can happily install APIVersion v1 charts, the only issue is with CRDs but we don't use that".
This doesn't seem to be the case anymore on last versions of K8S and Helm v3.
I am getting the following error :
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"

Thanks for your reply.
If you talk about the last version published (3.11.3) , it does not work on K8S 1.17.5 as you can see bellow.
$ helm search repo mattermost
NAME                                            CHART VERSION   APP VERSION     DESCRIPTION
mattermost/mattermost-enterprise-edition        1.3.0           5.23.1          Mattermost Enterprise server with high availiti...
mattermost/mattermost-push-proxy                0.3.0           5.9.0           Mattermost Push Proxy server
mattermost/mattermost-team-edition              3.11.3          5.23.1          Mattermost Team Edition server.
stable/mattermost-team-edition                  3.1.2           5.9.0           Mattermost Team Edition server.
bitnami/kubewatch                               1.0.14          0.0.4           Kubewatch notifies your slack rooms when change...
stable/kubewatch                                1.0.9           0.0.4           DEPRECATED Kubewatch notifies your slack rooms ...
$ helm upgrade --install mattermost stable/mattermost-team-edition --namespace mattermost --values mattermost/values.yaml
Release "mattermost" does not exist. Installing it now.
WARNING: This chart is deprecated
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "Deployment" in version "extensions/v1beta1"
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-11T18:14:22Z", GoVersion:"go1.13.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.5", GitCommit:"e0fccafd69541e3750d460ba0f9743b90336f24f", GitTreeState:"clean", BuildDate:"2020-04-16T11:35:47Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}

According this https://helm.sh/docs/topics/version_skew/ , Helm V2 does not support new version of K8S (<= 1.16).

I can confirm this work perfectly. Thank you.
To avoid my mistake which makes me waste time, can you change any reference to stable/mattermost-team-edition in https://github.com/mattermost/mattermost-helm/blob/master/charts/mattermost-team-edition/README.md

are you willing to open a PR to fix that? @geonux

fixed here: https://github.com/mattermost/mattermost-helm/pull/165/files


Is there a c++ version of cvxpy?

Is your feature request related to a problem? Please describe.
Hi, first thansk for your great job. I wonder
Is there a c++ version of cvxpy? if the answer is cvxcore inside the library, how to use it and is there any example or document for  it?

No, there is no C++ version of CVXPY.


doc(conf) add declarative_config_encryption_mode in kong.conf

FT-2613
Summary

Add the new EE option declarative_config_encryption_mode.

Reason
https://github.com/Kong/kong-ee/pull/3312
Testing

@Guaris @lena-larionova This is an interesting one for Vale. The content comes from a generated file. In this instance, should the autodocs source contain our docs-specific variables, or should we exclude autogenerated files from this substitution?

and to follow-up - @fffonion , can you please make these changes in the source file (https://github.com/Kong/kong-ee/blob/master/kong.conf.default)  instead of here? We'll generate the doc on the docs site from there.

@lena-larionova , the config is already in kong.conf.default. In that case I'm closing this as no actions is needed. Thanks for the input on this on!


"Application Error"

Application Error

An error occurred in the application and your page could not be served. Please try again in a few moments.

If you are the application owner, check your logs for details.

https://platform-status.mozilla.org/ is working for me. What do you mean, @timdream ?

It didn't work when I file this issue.


AlertLevel in hierarchical version of AffirmIf() not used

In the hierarchical version of AffirmIf() procedure, the AlertLevel parameter isn't propagated to the called AlertLogStruct.Alert() procedure. It is instead replaced by hard coded ERROR level. Which I assume is an bug, because in the not hierarchical version, the AlertLevel is propagated.
The bug occurs in line 2081

AlertLogStruct.Alert(AlertLogID, Message, ERROR) ; -- signal failure

in line 2081 in the AffirmIf() body should be replaced by
AlertLogStruct.Alert(AlertLogID, Message, AlertLevel) ; -- signal failure

Thanks.  I just pushed the fix into the current release.


Variable fallback

When using the systemd service, it is impossible to set any flags.
Using a variable fallback would allow a user to set the flag settings without having direct access to the command and without hard-modification.
For example: (export being optional depending on circumstances)
export BETTERLOCKSCREEN_STYLE="dimblur"  # May be too verbose...
betterlockscreen -l

would be equivalent to:
betterlockscreen -l dimblur

Thoughts?

eh, why not edit the .service file? can't really think of a usecase where I'd want to change the behavior of systemd sleep that often


Fix trim-related warning in EventStream.cs

Fix warning: IL2087: 'type' argument does not satisfy 'DynamicallyAccessedMemberTypes.PublicConstructors' in call to 'System.Activator.CreateInstance(Type, params Object[])'.
Description

This is a fix for a trim warning enabled by
EnableTrimAnalyzer>true</EnableTrimAnalyzer>
This declaration seems to have an unvoidable dependency on reflection, so DynamicallyAccessedMembers seems to be needed:
TE : EventStreamException, new()
Motivation and Context

Testing

Screenshots (if appropriate)
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

Wil

Will redo the PR, thanks @normj


Documentation on exposing c classes to berry as class

Are there any documentations on how to expose c class as berry class? I'm still confused how to do this. Im trying to expose esp8266 library classes to be used in berry as a class. Thank you for this great library.

The easiest way if it is not performance sensitive is to use https://github.com/berry-lang/berry_mapping
Otherwise you need to do it the hard way.
There are plenty of examples in Tasmota https://github.com/arendst/Tasmota/tree/development/lib/libesp32/berry_tasmota/src

@s-hadinger
I hope to extend the function of tasmota's berry by adding a custom xxx.be in embedded. but encountered a problem
I can't generate solidified_xxx_xxx.h in solidify.
I tried to compile the berry of this project into bin format, and then put it under /usr/local/bin/
But I can't generate solidified_xxx_xxx.h file with berry -s -g or cat solidify_all.be | berry -s -g.
May I ask how to generate solidified_xxx_xxx.h.
thanks

You just need to compile a local version of Berry. Use make in lib/libesp32/berry. Then change directory to lib/libesp32/berry_tasmota and use ./solidify_all.be

You just need to compile a local version of Berry. Use make in lib/libesp32/berry. Then change directory to lib/libesp32/berry_tasmota and use ./solidify_all.be

After I execute it, I get an error

error: cannot open file '-s -g'.

@s-hadinger
thanks
I have successfully executed with cat solidify_all.be | ../berry/berry -s -g and obtained the solidifed_xxx.h file
But I found that the four files i2c_axp192.be / i2c_axp202.be / lv_tasmota_widgets.be / lv_tasmota.be cannot be compiled
For the two files of i2c, it is prompted that the I2C_Driver class cannot be found during compilation. I couldn't get both files to compile after i2c_driver.be, had to remove
The two files of lv cannot be compiled. an error message

Parsing:  python_compat.be
Parsing:  zigbee_zcl_frame.be
Parsing:  energy.be
Parsing:  test_crypto.be
Parsing:  animate_module.be
Parsing:  trigger_class.be
Parsing:  lv_tasmotaa_widgets.be
syntax_error: string:96: '_lvgl' undeclared (first use in this function)
stack traceback:
: in native function
: in function parse_file
: in function main

Another error showing

Parsing:  python_compat.be
Parsing:  zigbee_zcl_frame.be
Parsing:  energy.be
Parsing:  test_crypto.be
Parsing:  animate_module.be
Parsing:  trigger_class.be
Parsing:  dyn.be
Parsing:  persist.be
Parsing:  zigbee_zb_coord.be
Parsing:  lv_tasmota.be
syntax_error: string:29: 'lv_clock' undeclared (first use in this function)
stack traceback:
: in native function
: in function parse_file
: in function main


Add ready signal to Node

Closes #15889

it's time to change my custom signal ready to something else like signal ready_to_use...


3.6.0-RC2 / MQTT not reconnecting when AP/Router is down voor 2-3min on power outage

Describe the bug
MQTT doesn't reconnect after power outage since 3.6.0-RC2
To Reproduce
Steps to reproduce the behavior:
Cut power to your wifi AP/Router and SmartEVSE's at the same time. Then put power on same time SmartEVSE and Network AP/Router. Your AP/Router will need some time to reboot and the SmartEVSE's but you will see they will not automatically come back online.
I tested by reverting to 3.5.1 and then to RC1, worked like expected. Updated to RC2, power cycled the router and EVSE's and they remain offline. HTTP interface is accessible, so I can reboot via the webinterface and then MQTT is connected.
Expected behavior
Same as in 3.5.1 and 3.6.0-RC1

Bit weird that it connected with RC1, because the only major MQTT code changes where from 3.5.1 to 3.6.0.
https://github.com/dingo35/SmartEVSE-3.5/commit/83f1c70f41024448900a46f83c5bed3783455cd0
Or it was by accident? That RC1 sometimes connects and sometimes doesn't. On RC2 it never reconnects, for multiple hours (tried it overnight). Modem/Router/WiFi network is back online after +- 3min.

Maybe it has something to do with DHCP, since a fix between these 2 versions was the fact that incorrect DNS servers were used. <IP_ADDRESS> instead of the one supplied via DHCP.

That would be easy to test, if you put ip address in the MQTT host fields dns is excluded....

Aha yes, that makes sense. I use a DNS name "xxxxx.dyndns.org" because I monitor installs that are not in my own network.

So your dhcp server is not (completely) up when wifi connection is established?
That would be a problem.....

Looks like it, or we can increase the 1000ms delay to 5 or 10s?
            // //load dhcp dns ip4 address into mongoose
            // static char dns4url[]="udp://<IP_ADDRESS>:53";
            // sprintf(dns4url, "udp://%s:53", WiFi.dnsIP().toString().c_str());
            // mgr.dns4.url = dns4url;

Commenting it out solves my problem.

Delaying to 5 or 10s wouldnt be good practice, and block the entire thread.
What brand/model AP are you using?

Your AP probably hands out its own ip as dns server (and then is too late to service it).
It would probably be solved if you instruct your DHCP server explicitly to hand out <IP_ADDRESS> directly, so SmartEVSE doesnt have to wait.

Teltonika, so probably need to add some DNS servers in a txt file

Didn't manage to get the router config sorted. Commented out the code for now so the <IP_ADDRESS> is used.
So kind of "closed" "solved" but maybe interesting to see if I'm the only one or others with other router HW have this.

@fluppie can you find out which delay you need? If you need a delay(2000) or delay(3000) this might be acceptable if other users experience the same problem.....

That  is too bad. You might want to try this one, I had to change some timeout params of the mongoose webserver to prevent a reboot on losing the wifi connection, its changed behaviour might influence your dhcp problem:
7aa8aff3.zip

@dingo35 this is even worse, they are not reconnecting to the wifi network anymore. Both after a power cycle (only EVSE's) and one even stopped connecting after the update to this 7aa8aff3 build. So I would not recommend this change.


Remove implicit window dependency

I'm working on NativeScript + Angular2 integration with ngrx and would like to use this reducer.
Ironically before I knew this existed (just came across it today), I ended up coding something almost identical here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/master/src/frameworks/core.framework/state/route.reducer.ts
Used here:
https://github.com/NathanWalker/angular2-seed-advanced/blob/master/src/frameworks/core.framework/common/route-common.component.ts
To use this reducer successfully with NativeScript however, we need to remove the dependency on window or at least grab window via DI so an appropriate substitute could be provided for in a native environment where window doesn't exist.
Problem:
https://github.com/CodeSequence/ngrx-store-router/blob/master/src/reducer.ts#L4
Any ideas?

This is something I have been thinking about also. What I was trying to avoid was dispatching a Navigated action on initial load but their may not be away around it since their isn't the router URL is being emitted at the end of the navigation cycle. This is why I was using the window.location to compare it against the initial URL emitted by the router subscription. I would be fine to just let it dispatch the initial action with the current URL using location.path(). This would eliminate the dependence on window and would still allow for navigating back to the initial URL.

I pushed version 0.0.6 without a dependency on window and stores the initial URL in an init action. If you have any issues with it, let me know.

Thanks! I'll try that soon.

@brandonroberts works great in NativeScript now :+1:  Thanks.
Btw, I am now using your plugin completely integrated here:
https://github.com/NathanWalker/angular2-seed-advanced
I'm sure you already know this, but the state to handle navigating: true is never called.
We may be able to add a handler that would hook into something like this:
routerCanDeactivate(next: ComponentInstruction, prev: ComponentInstruction) {
    this.store.dispatch({ type: RouterActions.navigating, payload: {url: next.url} });
    return true;
  }

Comes from a Components CanDeactivate lifecycle hook. Not sure how best to integrate something like that here.

Cool! My intention for that action was that it could be used to trigger navigation since the router doesn't  emit that information when navigation begins. It could be used it with a directive and dispatch an navigating action when router.navigating changes to true, but there isn't currently a way to get the attempted url without patching the router to generate the URL from in instruction.


Bug: Radio button don't show :focus state

What MDL Version are you using? (please be specific, e.g. major.minor.patch)

1.3.0

What browser(s) is this bug affecting (including version)?

Chrome 58.0.3029.81

What OS (and version) are you using?

Linux - Ubuntu 16.04

What are the steps to reproduce the bug? Can you create a plunker/codepen/jsfiddle which reproduces it?

Tab through to any radio button, they don't show any indication of being in focus, as defined here.
The behaviour can be observed on the MDL website here

What is the expected behavior?

The radio button in focus should have a light, wider ring around it (same as when pressed)

What is the actual behavior?

No ring. The radio button shows the same behaviour as in default selected/un-selected state.

Any other information you believe would be useful?

The checkboxes and switches, based on same base elements, do show the correct :focus behaviour. Only the radio buttons don't.

Look at MaterialRadio.prototype.init:
 this.boundFocusHandler_ = this.onChange_.bind(this);
change it to
 this.boundFocusHandler_ = this.onFocus_.bind(this);
this will set the correct class "is-focused" to the element

There's another problem with the CSS here - the focus is not visible when the radio button is unchecked, because it has
https://github.com/google/material-design-lite/blob/60f441a22ed98ed2c03f6179adf460d888bf459f/src/radio/_radio.scss#L104
so the style set for .is-focused makes no difference
https://github.com/google/material-design-lite/blob/60f441a22ed98ed2c03f6179adf460d888bf459f/src/radio/_radio.scss#L119-L121


Improvements to STParsedJSON:

Cleanups and reduction of copying
Add STArray::back, operator[], push_back(&&)
Add make_stvar
Rework STParsedJSON
Fix code and unit tests that use STParsedJSON
STTx move constructor

LGTM.  I see a significant rebase of the m-of-n branch in my future.
:+1:

A few space quibbles, but great stuff.  :+1:

LGTM :+1:

There's a missing include on OS/X - you need to merge this tiny change:
https://github.com/HowardHinnant/rippled/commit/308ad4c9845b11281ed3268128b5e992f21ab530

I put the missing #include in place.  Travis is happy.  So I'm removing the Hold label.

LGTM again :+1:

I left a few questions, suggestions, and nitpicks, but no show stoppers. I have not had a chance to build under Windows yet, but I'll sign off once I verify it works there.

Builds under Windows. As promised: :+1:

:+1:


Privacy Portal (SideMenuGroup): Cannot change the background color of group heading when its child is current

Reported by Chase from Privacy Portal team.

Based on the above comparison (left side is the previous revision before we used design token) and right side is after, we have a single value for a group a.heading when its child link is selected, which value is #cedfee, hence, we came up with a single new CSS token which is --goa-side-menu-parent-color-bg-hover and apply both cases.
Now, the design from PP team is a bit different, there are 2 colors applied, the group heading (a.heading) background color should be different from when it is hovered.

:tada: This issue has been resolved in version 5.0.0-alpha.13 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 3.0.0-alpha.9 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Window Resizes When Using Editor

If the player attempts to edit a value for a transform in the editor window, typing any of the window resize shortcut keys will cause the window to resize.
Assuming we can detect when an editor field is being edited, we should temporarily disable the resize shortcuts until the player clicks off the editor window

It's too much work to determine if we are writting in an ImGUI window for now. The best thing is to just remove those keyboard shortcuts for the window and replace them with an IMGUI dropdown or something


CHIP-tool SEGFAULTS on master when trying to provision ESP32

Problem
Valgrind sees a 'use after free' when we encounter a pairing error:
CHIP:TOO: Secure Pairing Failed
CHIP:TOO: Pairing Failure: Error 4047 (0x00000FCF)
==949307== Thread 6:
==949307== Invalid read of size 8
==949307==    at 0x1CAFB6: chip::RendezvousSession::UpdateState(chip::RendezvousSession::State, int) (RendezvousSession.cpp:271)
==949307==    by 0x1CAF66: chip::RendezvousSession::OnRendezvousError(int) (RendezvousSession.cpp:262)
==949307==    by 0x1CAA7A: chip::RendezvousSession::OnSessionEstablishmentError(int) (RendezvousSession.cpp:163)
==949307==    by 0x1C9CE7: chip::PASESession::HandlePeerMessage(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (PASESession.cpp:828)
==949307==    by 0x1CB469: chip::RendezvousSession::HandlePairingMessage(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (RendezvousSession.cpp:393)
==949307==    by 0x1CB2AF: chip::RendezvousSession::OnRendezvousMessageReceived(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (RendezvousSession.cpp:365)
==949307==    by 0x1CFBE6: chip::Transport::BLE::OnBleEndPointReceive(chip::Ble::BLEEndPoint*, chip::System::PacketBufferHandle) (BLE.cpp:197)
==949307==    by 0x1F6E8F: chip::Ble::BLEEndPoint::Receive(chip::System::PacketBufferHandle) (BLEEndPoint.cpp:1434)
==949307==    by 0x1F867A: chip::Ble::BleLayer::HandleIndicationReceived(void*, chip::Ble::ChipBleUUID const*, chip::Ble::ChipBleUUID const*, chip::System::PacketBufferHandle) (BleLayer.cpp:500)
==949307==    by 0x1A8CE9: chip::DeviceLayer::Internal::BLEManagerImpl::HandlePlatformSpecificBLEEvent(chip::DeviceLayer::ChipDeviceEvent const*) (BLEManagerImpl.cpp:282)
==949307==    by 0x1A8B2E: chip::DeviceLayer::Internal::BLEManagerImpl::_OnPlatformEvent(chip::DeviceLayer::ChipDeviceEvent const*) (BLEManagerImpl.cpp:254)
==949307==    by 0x1AC410: chip::DeviceLayer::Internal::BLEManager::OnPlatformEvent(chip::DeviceLayer::ChipDeviceEvent const*) (BLEManager.h:171)
==949307==  Address 0x5d04550 is 48 bytes inside a block of size 2,560 free'd
==949307==    at 0x48399AB: free (vg_replace_malloc.c:538)
==949307==    by 0x1A5036: chip::Platform::MemoryFree(void*) (CHIPMem-Malloc.cpp:132)
==949307==    by 0x1A025B: void chip::Platform::Delete<chip::RendezvousSession>(chip::RendezvousSession*) (CHIPMem.h:187)
==949307==    by 0x19FA25: chip::Controller::DeviceCommissioner::RendezvousCleanup(int) (CHIPDeviceController.cpp:738)
==949307==    by 0x19FADF: chip::Controller::DeviceCommissioner::OnRendezvousError(int) (CHIPDeviceController.cpp:763)
==949307==    by 0x1CAF52: chip::RendezvousSession::OnRendezvousError(int) (RendezvousSession.cpp:260)
==949307==    by 0x1CAA7A: chip::RendezvousSession::OnSessionEstablishmentError(int) (RendezvousSession.cpp:163)
==949307==    by 0x1C9CE7: chip::PASESession::HandlePeerMessage(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (PASESession.cpp:828)
==949307==    by 0x1CB469: chip::RendezvousSession::HandlePairingMessage(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (RendezvousSession.cpp:393)
==949307==    by 0x1CB2AF: chip::RendezvousSession::OnRendezvousMessageReceived(chip::PacketHeader const&, chip::Transport::PeerAddress const&, chip::System::PacketBufferHandle) (RendezvousSession.cpp:365)
==949307==    by 0x1CFBE6: chip::Transport::BLE::OnBleEndPointReceive(chip::Ble::BLEEndPoint*, chip::System::PacketBufferHandle) (BLE.cpp:197)
==949307==    by 0x1F6E8F: chip::Ble::BLEEndPoint::Receive(chip::System::PacketBufferHandle) (BLEEndPoint.cpp:1434)
==949307==  Block was alloc'd at
==949307==    at 0x483877F: malloc (vg_replace_malloc.c:307)
==949307==    by 0x1A4FAC: chip::Platform::MemoryAlloc(unsigned long, bool) (CHIPMem-Malloc.cpp:112)
==949307==    by 0x1A4F7D: chip::Platform::MemoryAlloc(unsigned long) (CHIPMem-Malloc.cpp:106)
==949307==    by 0x1A027B: chip::RendezvousSession* chip::Platform::New<chip::RendezvousSession, chip::Controller::DeviceCommissioner*>(chip::Controller::DeviceCommissioner*&&) (CHIPMem.h:168)
==949307==    by 0x19F49D: chip::Controller::DeviceCommissioner::PairDevice(unsigned long, chip::RendezvousParameters&) (CHIPDeviceController.cpp:612)
==949307==    by 0x131C43: PairingCommand::Pair(unsigned long, chip::Transport::PeerAddress) (PairingCommand.cpp:74)
==949307==    by 0x13191A: PairingCommand::RunInternal(unsigned long) (PairingCommand.cpp:58)
==949307==    by 0x131754: PairingCommand::Run(PersistentStorage&, unsigned long, unsigned long) (PairingCommand.cpp:35)
==949307==    by 0x12C61D: Commands::RunCommand(PersistentStorage&, unsigned long, unsigned long, int, char**) (Commands.cpp:118)
==949307==    by 0x12BC05: Commands::Run(unsigned long, unsigned long, int, char**) (Commands.cpp:49)
==949307==    by 0x166A8E: main (main.cpp:41

Bisected and it seems like 93b6456850f74c49b2e39a94f67e0d90e651e290 is the first commit to fail (#5081)
I suspect that the PR just injects a failure however that should not make us use freed memory, so we seem to absolutely have a ownership/lifetime issue here.

Apparently our current salt size (at least for my runs) is 25, which is an error after that PR (min 8, max 16).
I will look into fixing the invalid memory access first and only then fixing the salt size.

error is because "SPAKE2P Key Exchange Salt" is longer than the expected max.
Did not figure out the crash yet

Apparently #5081 also changed the salt string to be within bounds. For me however, I had a old flash of ESP32, so the device sends a long salt.
To reproduce:

flash a pre #5081 build of ESP32
run chip-tool to provision

I think this one, #4965 and #4356 does have the same root cause.
Following the steps to reproduce, it does not crash for me.
But looking at the code those lines seems suspicious:
https://github.com/project-chip/connectedhomeip/blob/dcb711136e006e59258d07a60dbdaac60e1f2bba/src/transport/RendezvousSession.cpp#L245
So when there is an error, the code calls the delegate method OnRendezvousError, then  the commissioner calls DeviceCommissioner::RendezvousCleanup which itself does:
    if (mRendezvousSession != nullptr)
    {
        chip::Platform::Delete(mRendezvousSession);
        mRendezvousSession = nullptr;
    }

But RendezvousSession is not done yet, and it tries to continue to do some clean up after it has been free'd...

Reproduction steps:
Build a ESP32 that sends a long salt:
git checkout 2454d646
# build esp32
./examples/all-clusters-app/esp32/build/chip-all-clusters-app.flash.py --erase

followed by trying to provision that using a new chip-tool (this will error out in chip-tool because of invalid key lenght):
checkout master
# build chip-tool
./out/chip_tool/chip-tool pairing ble ssid password 12345678 3840


Basis is missing the IDENTITY and ortho constants

Godot version: 3.1 beta 10
OS/device including version: All
Issue description:
While Vector3 has constants such as ONE and UP, Basis is missing the IDENTITY constant and the otho constants. These constants are already present in C# here, but not in GDScript. Related PR: https://github.com/godotengine/godot/pull/14704
I will fix this later if nobody else does, but it will have to wait for 3.2. It's very non-critical.

Isn't Basis() the same as Identity?

@neikeq Yes, you're right, it is! Though, there should still be an IDENTITY property to avoid confusion, just as Vector3 has ZERO. Also, I noticed that in C#, there is no parameterless Basis constructor.

C# doesn't allow value types to have parameterless constructors (I think CLR does allow it though).


conditional validation based on value of dropdown

Problem: I want an input field to be conditionally required if the selected country value in the dropdown is  "US" (as shown below).
This is the current value/requirement being passed to the validator:
data-parsley-conditionalrequired="['reg_country', 'US']"
clearly that's not correct, I've tried several variations, none succeeded.
Is it possible to do this? If so, what should be passed?
any insight here would be helpful.  Thanks!
If it's not a dropdown, but a checkbox, then the conditionalrequired custom validator works (as it does earlier in the form)... but for a dropdown I can't figure out the selector that should be used.
window.ParsleyValidator.addValidator('conditionalrequired', function (value, requirement) {
  if (requirement[1] == $(requirement[0]).val() && '' == value) {
    return false;
  }
  return true;
}, 32);

<select data-parsley-required="true" id="reg_country"
  name="dev_partner[client]" data-parsley-id="3006" class="parsley-success">
<option value="AE">United Arab Emirates</option>
<option value="GB">United Kingdom</option>
<option selected="selected" value="US">United States</option>
<option value="UM">United States Minor Outlying Islands</option>
<option value="UY">Uruguay</option>
<option value="UZ">Uzbekistan</option>
<option value="VU">Vanuatu</option>
<option value="VE">Venezuela, Bolivarian Republic of</option>
<!-- removed non-relevant code for brevity-->

<input data-parsley-conditionalrequired-message="You must enter your business name"
  data-parsley-conditionalrequired="['reg_country', 'US']"
  data-parsley-minlength="2"
  data-parsley-success-class=""
  data-parsley-trigger="blur"
  data-parsley-validate-if-empty="true" id="biz_name"
  type="text" data-parsley-id="7884" class="">

doh - the argument passed to the conditionalrequired validator shouldn't be 'reg_country' but rather '#reg_country'


how to remove filename from top?

I want to get rid of the file name that appears on the very first line, I was able to make certain changes but can't figure out where this option is.
Thanks

https://github.com/amix/vimrc/issues/392#issuecomment-393748155
I can help u


Intermittent 502 Errors

I just updated my Azure Functions project to .NET 8, and since then, I've been getting intermittent 502 errors with my HTTP-triggered functions.
Watching the log stream, I've discovered that the 502 error always seems to be returned after DrainMode mode enabled pops up.
2023-11-18T04:11:35.832 [Information] DrainMode mode enabled
2023-11-18T04:11:35.832 [Information] Calling StopAsync on the registered listeners
2023-11-18T04:11:35.833 [Information] Stopping the listener 'Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener' for function 'ComputeTopCompaniesStats'
2023-11-18T04:11:35.852 [Information] Stopped the listener 'Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener' for function 'ComputeTopCompaniesStats'
2023-11-18T04:11:35.854 [Information] Call to StopAsync complete, registered listeners are now stopped
2023-11-18T04:11:38.922 [Information] Host Status: {"id": "appName","state": "Running","version": "<IP_ADDRESS>49","versionDetails": "4.27.5+096e48198ef4cc3259d9ad0f45891a74992825a6","platformVersion": "<IP_ADDRESS>7","instanceId": "e09f620ecddc73363f5b6301cd6bcd1b8cf51ffcc5d31d10303d898464685ffb","computerName": "10-30-3-172","processUptime": 332716,"functionAppContentEditingState": "Unknown"}
2023-11-18T04:12:04.315 [Information] Could not resolve CoreCLR path. For more details, enable tracing by setting COREHOST_TRACE environment variable to 1
2023-11-18T04:12:04.325 [Error] Exceeded language worker restart retry count for runtime:dotnet-isolated. Shutting down and proactively recycling the Functions Host to recover
2023-11-18T04:12:09.433 [Information] Stopping JobHost
2023-11-18T04:12:09.434 [Information] Stopping the listener 'Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener' for function 'ComputeTopCompaniesStats'
2023-11-18T04:12:09.454 [Information] Stopped the listener 'Microsoft.Azure.WebJobs.Host.Listeners.SingletonListener' for function 'ComputeTopCompaniesStats'
2023-11-18T04:12:09.457 [Information] Job host stopped

** 502 error when attempting to call an HTTP-triggered function.

2023-11-18T04:12:55.583 [Information] Worker process started and initialized.
2023-11-18T04:13:17.289 [Information] Executing 'Functions.GetTopCompanies' (Reason='This function was programmatically called via the host APIs.', Id=dc4f3180-8ae0-4ffb-b505-5d9ee525842f)

** No more 502 error, and my function returns 200.

I've tried using the diagnosing tool within Azure Functions and I can't seem to figure out the root cause. Here are the two top errors that seem to be happening when the 502.
System.Exception | 91 | Language Worker Process exited. Pid=4704.https://aka.ms/dotnet/app-launch-failed | 11/18/2023 3:08:50 AM

Exceeded language worker restart retry count for runtime:dotnet- | 90 | Exceeded language worker restart retry count for runtime:dotnet-isolated. Shutting down and proactively recycling the Functions Host to recover | 11/18/2023 3:09:00 AM

I am using:

.NET 8 Isolated
Windows 64-bit
Azure Functions v4

Here are the packages that I am using.
<ItemGroup>
	<FrameworkReference Include="Microsoft.AspNetCore.App" />
	<PackageReference Include="Azure.Identity" Version="1.10.4" />
	<PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.0" />
	<PackageReference Include="Microsoft.Azure.Cosmos" Version="3.36.0" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.20.0" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.CosmosDB" Version="4.4.2" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.1.0" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Storage.Queues" Version="5.2.0" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.3.0" />
	<PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.16.2" />
	<PackageReference Include="Microsoft.Extensions.Http" Version="8.0.0" />
	<PackageReference Include="Microsoft.Graph" Version="5.35.0" />
	<PackageReference Include="Microsoft.Identity.Client" Version="4.57.0" />
	<PackageReference Include="Microsoft.Identity.Web" Version="2.15.3" />
</ItemGroup>

Please let me know if you need any more information. Thank you

The app-launch-failed error usually happens when your app is set as a 64 bit app and your deployed payload is 32 bit.
Can you make sure you are publishing & deploying win-x64 version of your payload?
dotnet publish -c release -r win-x64 --no-self-contained

Hey @kshyju, thank you for your quick response. So, I am deploying the payload through Visual Studios and confirmed that everything is set to 64-bit. I also tried using 32-bit, and I was having the same issue.
I just downgraded my project and packages back to .NET 7, and everything is working as expected—no more 502 errors.
While looking using the diagnose and solve problems page, I am seeing these exceptions below when I got my last 502 error around 11/18/2023 at 4:41 PM. It seems to happen every time the drain mode is kicked off.

I have same issue.
Runtime can recognize the HTTP Trigger function, but frequently fail in invocation.
Azure Functions Consumption Windows Runtime version <IP_ADDRESS>49
Deployed in Japan East region.
csproj.
 <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <AzureFunctionsVersion>V4</AzureFunctionsVersion>
    <OutputType>exe</OutputType>
  </PropertyGroup>
~~~
 <ItemGroup>
    <PackageReference Include="Microsoft.ApplicationInsights.WorkerService" Version="2.21.0" />
    <PackageReference Include="Azure.Storage.Blobs" Version="12.19.1" />
    <PackageReference Include="Azure.Storage.Queues" Version="12.17.1" />
    <PackageReference Include="Azure.Extensions.AspNetCore.Configuration.Secrets" Version="1.3.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker" Version="1.19.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.ApplicationInsights" Version="1.1.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Http" Version="3.1.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Extensions.Timer" Version="4.3.0" />
    <PackageReference Include="Microsoft.Azure.Functions.Worker.Sdk" Version="1.15.1" />
    <PackageReference Include="Microsoft.Extensions.Http" Version="8.0.0" />
    <PackageReference Include="Azure.Identity" Version="1.10.4" />
  </ItemGroup>

Ping.cs
public static class Ping
{
    [Function("Ping")]
    public static HttpResponseData Run([HttpTrigger(AuthorizationLevel.Function, "get", Route = null)] HttpRequestData req)
    {
        var response = req.CreateResponse(HttpStatusCode.OK);
        response.WriteString("Pong");
        return response;
    }
}

Azure Functions Log stream (Filesystem Logs)
Connected!
2023-11-19T23:04:34  Welcome, you are now connected to log-streaming service. The default timeout is 2 hours. Change the timeout with the App Setting SCM_LOGSTREAM_TIMEOUT (in seconds).
2023-11-19T23:04:57.171 [Information] Executing 'Functions.Ping' (Reason='This function was programmatically called via the host APIs.', Id=25053997-38e3-48c7-9c96-3e984ed4ca8e)
2023-11-19T23:04:58.279 [Error] Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'SFDCIntegrationFunctions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
2023-11-19T23:04:58.335 [Error] Exceeded language worker restart retry count for runtime:dotnet-isolated. Shutting down and proactively recycling the Functions Host to recover
2023-11-19T23:05:42.920 [Information] Executing 'Functions.Ping' (Reason='This function was programmatically called via the host APIs.', Id=0f38840c-b474-4293-8aa7-e4f54aa02af2)
2023-11-19T23:05:47.989 [Error] Unhandled exception. System.IO.FileLoadException: Could not load file or assembly 'SFDCIntegrationFunctions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
2023-11-19T23:05:48.060 [Error] Exceeded language worker restart retry count for runtime:dotnet-isolated. Shutting down and proactively recycling the Functions Host to recover

eventlog.xml
<?xml version="1.0" encoding="UTF-8"?>
<Events>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:13Z" />
         <EventRecordID>77369906</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-13-238</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1005</EventID>
         <Level>2</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:13Z" />
         <EventRecordID>365559875</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Failed to gracefully shutdown application 'MACHINE/WEBROOT/APPHOST/MAWSFNPLACEHOLDER465_F_V4_NODE_16_X64'.</Data>
         <Data>Process Id: 3292.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1033</EventID>
         <Level>4</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:14Z" />
         <EventRecordID>77371296</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-13-238</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application 'MACHINE/WEBROOT/APPHOST/[REDACTED]FUNCTIONS' has shutdown.</Data>
         <Data>Process Id: 5292.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:47Z" />
         <EventRecordID>365594062</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1032</EventID>
         <Level>4</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:48Z" />
         <EventRecordID>365594406</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application 'C:\Program Files (x86)\SiteExtensions\Functions\4.27.5\64bit\' started successfully.</Data>
         <Data>Process Id: 5692.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:04:58Z" />
         <EventRecordID>365604593</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1033</EventID>
         <Level>4</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:05:03Z" />
         <EventRecordID>365609828</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application 'MACHINE/WEBROOT/APPHOST/MAWSFNPLACEHOLDER465_F_V4_NODE_16_X64' has shutdown.</Data>
         <Data>Process Id: 5692.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:05:37Z" />
         <EventRecordID>365643750</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1032</EventID>
         <Level>4</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:05:37Z" />
         <EventRecordID>365644093</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application 'C:\Program Files (x86)\SiteExtensions\Functions\4.27.5\64bit\' started successfully.</Data>
         <Data>Process Id: 5536.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:05:47Z" />
         <EventRecordID>365654296</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1005</EventID>
         <Level>2</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:05:58Z" />
         <EventRecordID>365664406</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Failed to gracefully shutdown application 'MACHINE/WEBROOT/APPHOST/MAWSFNPLACEHOLDER465_F_V4_NODE_16_X64'.</Data>
         <Data>Process Id: 5536.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name="IIS AspNetCore Module V2" />
         <EventID>1032</EventID>
         <Level>4</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:06:32Z" />
         <EventRecordID>365698781</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application 'C:\Program Files (x86)\SiteExtensions\Functions\4.27.5\64bit\' started successfully.</Data>
         <Data>Process Id: 7096.</Data>
         <Data>File Version: 16.0.23292.24. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 2aa401550574f93402eba13ff9a4827ef01a2f3a</Data>
      </EventData>
   </Event>
   <Event>
      <System>
         <Provider Name=".NET Runtime" />
         <EventID>1026</EventID>
         <Level>1</Level>
         <Task>0</Task>
         <Keywords>Keywords</Keywords>
         <TimeCreated SystemTime="2023-11-19T23:06:32Z" />
         <EventRecordID>365698812</EventRecordID>
         <Channel>Application</Channel>
         <Computer>10-30-2-84</Computer>
         <Security />
      </System>
      <EventData>
         <Data>Application: dotnet.exe
CoreCLR Version: <IP_ADDRESS>103
.NET Version: 8.0.0
Description: The process was terminated due to an unhandled exception.
Exception Info: System.IO.FileLoadException: Could not load file or assembly '[REDACTED]FUNCTIONS, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.</Data>
      </EventData>
   </Event>
</Events>

I am having the same (or at least similar) issue, except that my host is not starting at all. I can't see as much data in the eventlog.xml file as @recumbented but I can see events with EventID '02000780' which according to err.exe is 'ERROR_CANT_ACCESS_FILE - The file cannot be accessed by the system'.
I'm deploying using exactly the same settings I was used before for .NET 7 isolated. I double checked and it's x64.
The most frustrating bit is that I can't find anything useful in any of the log files, even after setting 'fileLoggingMode' to 'always'.

Home page:

We have the same problem with 502's for a couple of minutes after a new instance is started. We use Consumption Plan on Windows.
I've deployed a sample function app with just one http trigger on both a Consumption Windows and a Consumption Linux and the one using Windows always fails with 502 for a couple of minutes. The Windows version got the following logs:

Clearly stating that the dotnet8 runtime isn't installed.
We are in contact with the support and they say this is not a bug, but that dotnet8 is still in "Early Access" and nog readily available on every instance but instead JIT downloaded/installed on startup.
But for us, it's not ok with about 3 minutes of 502's until the runtime is installed when using consumption plan, because we get new instances frequently.
I would say that .NET8 not ready to use for Consumption plan on Windows yet.

We have the same problem with 502's for a couple of minutes after a new instance is started. We use Consumption Plan on Windows.
I've deployed a sample function app with just one http trigger on both a Consumption Windows and a Consumption Linux and the one using Windows always fails with 502 for a couple of minutes. The Windows version got the following logs:
Clearly stating that the dotnet8 runtime isn't installed.
We are in contact with the support and they say this is not a bug, but that dotnet8 is still in "Early Access" and nog readily available on every instance but instead JIT downloaded/installed on startup.
But for us, it's not ok with about 3 minutes of 502's until the runtime is installed when using consumption plan, because we get new instances frequently.
I would say that .NET8 not ready to use for Consumption plan on Windows yet.

Interesting, this sounds like it is the main issue because I only experienced the 502 errors for a couple of minutes as well, and then magically, everything is working.

@MikeWhalenIII can you confirm things are in a good state now?
We'll look at the details so we can root cause here, but it's possible this was caused by a temporary issue during the rollout for some of your workers.

@fabiocav Can not answer for @MikeWhalenIII, but as I mentioned in this thread, we're also experiencing "intermittent" 502:s on Azure Functions running on Windows Consumption Plan. We're still having this issue and was forced to roll back all our .net8 upgrades. Here are some screenshots from a test just made on a sample Azure Function app on both Linux Consumption Plan and Windows Consumption plan. The test is a complete cold start (idle for about 12 hours):

The Linux version wakes up and responds in ~4 seconds, but the Windows version had a really hard time this morning... 9 times in a row it responds with a 502 after about 48 seconds each time. Here's a screenshot from the logs during this period (local time is UTC+1):

It took around 7 minutes for the instance to start working. This is hardly anything we can use in a production environment.
We thought that the Azure instances would be ready to use by the time .net8 was finally released on November 14th, but that doesn't seem to be the case.
Unless we're missing something... In our support ticket they say that .net8 is only released as an "early access" but we thought that the preview versions and perhaps the GA versions could be thought of as "early access" but not the final version?

Currently, dotNet8 runtime is available as part of the early access program on App Services. This can be considered as GA...

and

...behavior won’t be occurred in the future once dotNet8 final released as GA to the public.

Please correct me if I'm wrong, but isn't .NET 8.0.0 (8.0.100) a "final release to the public"?

Sorry about the rant, but we're just confused about what's "final" and what's "eary access" and should not have been updating our services if the November 14th release was just an "early access".

I believe this post means .NET 8 is supposed to be working: https://azure.microsoft.com/en-us/updates/ga-azure-functions-supports-net-8-in-the-isolated-worker-model/
It does seem wrong to say that ".NET 8 is the new recommended default for .NET function apps" only a few lines after "Windows apps might experience additional impact from cold starts".

In any case, we are not just experiencing "additional impact from cold starts".
The absence of comments from the team in these tickets tells me they are probably working hard to solve it, but it would be great to get anyone to say something here (or anywhere else!)

I am having the same (or at least similar) issue, except that my host is not starting at all. I can't see as much data in the eventlog.xml file as @recumbented but I can see events with EventID '02000780' which according to err.exe is 'ERROR_CANT_ACCESS_FILE - The file cannot be accessed by the system'.
I suspect this is the issue: EventID 2294 Each application pool has a managedRuntimeVersion attribute that contains the version of the common language runtime (CLR) that the application pool preloads. If the value in the attribute does not match the installed runtime, the worker process may fail to load

Interestingly I am seeing the same error albeit not in functions but in my Azure App Service after trying to update to .net8.
They appear one after the other and no real other log seems to be written.
  <Event>
        <System>
            <Provider Name="W3SVC-WP"/>
            <EventID>2294</EventID>
            <Level>1</Level>
            <Task>0</Task>
            <Keywords>Keywords</Keywords>
            <TimeCreated SystemTime="2023-11-21T08:18:27Z"/>
            <EventRecordID>-1668458702</EventRecordID>
            <Channel>Application</Channel>
            <Computer>WN1MDWK0000DV</Computer>
            <Security/>
        </System>
        <EventData>
            <Data>v8.0</Data>
            <Binary>02000780</Binary>
        </EventData>
    </Event>

I reckon since Azure Functions and App Services use similar tooling the source of the problem is the same. I had to roll back to .net7 for now on my App Service. For App Services there seems to be no real bug-reporting anywhere on github so I hope once this is solved the App Service problems will be solved as well.

Yes, @ChristophHornung. As far as I know, Azure Functions runs on App Services, and it's App Services which owns the IIS/w3p process.
Those logs we are seeing come from the IIS service. Fingers crossed for a prompt resolution.

Hi all - yes, we are continuing to work on things here. Thank you for sharing details of what you're seeing!
To provide some additional context, the "early access" framing from App Service and Azure Functions indicates that the runtime is available on Windows, with a strict requirement on having the site's netFrameworkVersion property set properly so that everything can be installed for the app. The system goes through a performance optimization process that gets kicked off right away on GA day, and that's what determines the "early access" period. Basically, it's baking the runtime in as a more universal assumption.
The optimization process is nearing completion, and it should resolve most of the issues that folks are seeing. It is likely that the "early access" tag will linger a bit past that point just due to timing (UX won't be updated right away due to holidays in the US). Regardless, we'll post back here once things are optimized in full.
We're really looking forward to seeing more apps light up on .NET 8. Thanks for your excitement and for engagement with us on this issue!

To provide some additional context, the "early access" framing from App Service and Azure Functions indicates that the runtime is available on Windows, with a strict requirement on having the site's netFrameworkVersion property set properly so that everything can be installed for the app.

Thank you for your reply, much appreciated. So with the strict requirement on having netFrameworkVersion property set properly, it should work?

The tests from this morning:

Perhaps not related, but after 8 tries with 502 after ~40+ seconds each, I tried again and at the same time went to the Azure Portal just to check that something wasn't fishy with the function app there. As soon as the portal loaded the app, I got a 200 OK... Probably just a coincidence... 🤷🏼♂

@mattchenderson Anything I can do to work around the problem in Azure App Service? The Configuration->.net Version is set to .net8, do I need to set the netFrameworkVersion somewhere else?

Facing the same issue with Azure Function on Consumption plan on Windows.
And in east us 2 region there no more label that it's Early Access.

UK South region, Consumption Windows plan, still having the same issues.
Is this still expected? It's been 10 days after the official .NET 8 release.

It could be unrelated, but it seems things are getting worse. Our production instances have been stopped and can't be restarted now. We have made no changes to it: no settings changed, no deployments, still running on .NET 7.

The troubleshooting process sends me to this page: https://learn.microsoft.com/en-gb/dotnet/core/runtime-discovery/troubleshoot-app-launch?pivots=os-windows

The Overview in the Portal is not loading:

What's going on?!

Hi - I'm catching up on our deployment state. It remains ongoing, and we're seeing what can be done to get it closed out ASAP. Again, thanks for reporting everything you're seeing.
@jenspettersson That may be a coincidence. But if netFrameworkVersion was set, we would expect it to work, albeit with a higher cold start. Though what you've described seems to exceed the expected impact. The portal loading is similar to a request in terms of warming up the site, so I suspect the test requests at that same time would have had the same result.
@ChristophHornung That is the correct place. That UX maps to the netFrameworkVersion property on the underlying resource definition. Technically that property is on the /sites/<siteName>/config/web object in the Azure Resource Manager.
@Tiktack I'll have to double-check on that UX element. To my knowledge, no UX update has occurred, so it's possible that dropdown wasn't properly updated to add "Early Access" in the first place. We are still in the "Early Access" period, and you should still see "Early Access" if attempting to create a new app, at least.
@rodolfograve Any issues with .NET 8 would unfortunately still be expected. Regardless, an existing .NET 7 should not have been impacted. Please open a support ticket for your production apps if you haven't already.

Hi - I'm catching up on our deployment state. It remains ongoing, and we're seeing what can be done to get it closed out ASAP. Again, thanks for reporting everything you're seeing.

Thanks again for the reply. Our test app in region East US has now been working correctly for a couple of days, around 3-4 second cold start on first request. Perfectly fine.
But the same app on region West Europe still gets several 502's after 40+ sec each, so I guess the ongoing deployment hasn't reached all locations yet.
Out of curiosity, was this an error or was it expected behavior, just not very well documented? Would be good to know on the next major .NET release if we should wait a couple of weeks/months after the release to suggest to our clients to upgrade to latest LTS.

Yes, @jenspettersson. I feel like the real issue here is not that .NET 8 is not yet supported by Azure Functions but that the Azure Functions team said it was: https://azure.microsoft.com/en-us/updates/ga-azure-functions-supports-net-8-in-the-isolated-worker-model/
Setting the right expectations and better communication would have avoided all of us from wasting time on this and would have given more space to the Azure Functions team to finish whatever it is they need to finish.

Just a quick update: the process I outlined earlier is now complete for pubic regions. This should address most of the issues that folks are seeing related to .NET 8 installation. Hopefully, if you try again, you should see things working. Please let us know the results.
Apps still could be seeing issues for other reasons beyond the "Early Access" issue we've been discussing here. Right now, one main one I'd flag is that I'd recommend using version 1.15.1 of the worker SDK while we address some issues that can situationally occur using 1.16.*, for example. Those are more edge case, but if you are still seeing issues, I'd double-check the version there and consider a temporary downgrade.
Again, thanks all for engaging, for providing details of what you're seeing, and for your patience as we've been working through this.
This issue is to remain open so that we can collect any further reports.

@MikeWhalenIII Hey there! Wondering if you're still facing the same issues? If you are, could you let us know and mention the region it's happening in? We're here to help and appreciate your ongoing patience!

Same issue in Central US

We think we have identified a common cause and are actioning it. I'm posting this before I have an ETA. We know other regions to be impacted beyond those listed in this thread already. Fix will cover all.

@mattchenderson Any update on this issue? I am experiencing same problems mentioned above. Thanks!

@MikeWhalenIII Hey there! Wondering if you're still facing the same issues? If you are, could you let us know and mention the region it's happening in? We're here to help and appreciate your ongoing patience!

 I will check again once the issue @mattchenderson identified above is resolved. My function app is in East US. Thanks

I'm happy to report that things are working OK for me since yesterday, both on Consumption Plan and Elastic. UK South.

Glad to hear! I unfortunately still see the issue in UK South, but the situation there (and in most regions) has improved. You would be less likely to hit it than at time of my last message, but it is still possible to encounter right now.

Not sure if related at all, but I have just upgraded our .NET 6 Web App to .NET 8 and deployed to Azure App Services (Central US) and appear to be getting exactly the same issues and errors as stated above. I realize this thread is targeting Azure Functions but any chance there is overlap here? If I set the .NET version to .Net 7 it runs fine, if I set to .NET 8 (early release) I get all the errors and behavior as you are getting above for Functions. I can create a new thread if better separated.

Not sure if related at all, but I have just upgraded our .NET 6 Web App to .NET 8 and deployed to Azure App Services (Central US) and appear to be getting exactly the same issues and errors as stated above. I realize this thread is targeting Azure Functions but any chance there is overlap here? If I set the .NET version to .Net 7 it runs fine, if I set to .NET 8 (early release) I get all the errors and behavior as you are getting above for Functions. I can create a new thread if better separated.

I had the same issue and was forced to bin-deploy the .net 8 to get the app to work. I have not been able to go back, and retry without the bin-deploy to see if the issue is still happening.

East US, a little bit better but still host often fails to start randomly. Rolling back

This is indeed expected to impact Web Apps as well. The issue sits at a core layer below Functions, and the fix being tracked addresses all app types.

This is indeed expected to impact Web Apps as well. The issue sits at a core layer below Functions, and the fix being tracked addresses all app types.

Thanks for confirming.

Thanks - do you have an ETA for the other regions? i.e. are they hours, days or weeks away? Thanks!

@GitDaBytes I am limited in the forward-looking statements I am authorized to make. Some regions will certainly close out faster than others. Unfortunately, I do expect Central US to be one of the slower ones, though we are making good progress there, so I could end up wrong on that.
Brazil South should no longer present the issue in question.

@mattchenderson ok thanks v much.  Central US is the one i am after. I have fingers crossed it goes smoothly :)

Australia Central 2, Australia Southeast, Germany West Central, Southeast Asia, and Switzerland West should no longer present the issue.
At this point, only East US, Central US, and some ASE setups should be able to run into this.

East US should no longer present the error.
As a heads-up, our plan is to resolve this issue after Central US completes and folks here have been able to confirm. Updates may still be rolling for App Service Environment (ASE) setups, but for those, a support ticket is going to be the best way to track any ongoing issues.

@mattchenderson I upgraded my function app to .NET 8 nine hours ago, and I have not received any 502 errors! It looks like East US is good. Thank you for all of your help!

@mattchenderson just checking if there was any update on Central US? Thanks!

@GitDaBytes Apologies for missing this. The update is ongoing but has made great progress. While significantly less likely, at the moment it's still possible to encounter the issue, though.

@mattchenderson thank you so much for the update! I just tried .net 8 web app on Central US and it does indeed appear to be working. Thank you so much for the hardwork!

Central US should no longer present this issue.
This is now true for all public regions, with the noted exception for ASEs. Again, if anyone encounters this for an ASE, we ask that you open a support ticket, as that will lead to the fastest resolution.
We will now consider this resolved, though we will leave this issue open for a little while (into the beginning of January) so that folks can confirm.
I want to reiterate my sincere thanks for everyone's engagement and patience. These kinds of issues are especially frustrating when they take away from the excitement about new things like .NET 8. But the thread here was super helpful in tracking things down, validating, and celebrating incremental progress. Thank you, and I hope all of you have a wonderful end of year. Here's to a 2024 full of .NET 8!

I wasn't sure if this warranted a separate issue but my function app is in East US 2 (using FUNCTIONS_WORKER_RUNTIME = dotnet-isolated + netFrameworkVersion = v8.0 + use32BitWorkerProcess = false) and exhibiting the exact same error exceptions described by the OP in #9686
I managed to get around this by using <FunctionsEnableWorkerIndexing>False</FunctionsEnableWorkerIndexing> in my Functions csproj
Mentioning here as 9686 was closed with a request to follow on here.

I'm experiencing this same issue in the Azure Gov US Virginia Region with a consumption plan .NET8 Isolated process. Is there any information about if this being tracked in the USGov area, or should it be fixed already over there too?
I have my azure function set to .NET 8 Isolated. But when I run dotnet --info I see that its on RC2, not the GA version.

@vexingpos If that workaround is helping, I think it's something separate from the issue we've been tracking here. I just created https://github.com/Azure/azure-functions-dotnet-worker/issues/2185 - let's track it there. I'll ask for a bit more info in that thread as well.
@Quintinon I'm following up with colleagues to get clarity on the state there, but my understanding so far is that deployments are underway that should address things for Azure Government. Since you're seeing RC2 installed, it is either still in the fully rc2 state or the "early access" state described above. But again, the GA update should be happening, as should the update that was being tracked here for public regions after that point.

Hello! I have been seeing similar 502 errors on cold start with a .net 8 / isolated function on a consumption plan in Australia East. Is it possible that this issue is still ongoing? Reverting to .net 7 appears to have resolved it.

@TomCharman We do not see any ongoing impact in public regions, although some App Service Environment setups could still see it. This may be some different issue. I think a support ticket will probably be the best course of action for getting an answer on your specific app.

We're going to close this issue as the root cause was resolved, and folks in the thread were able to verify this for public regions. Thank you all again!
The rollout may still be ongoing for some non-public regions and ASEs, but if you continue to see issues regarding this, please engage Azure support, who will be best equipped to help with that.


A couple of presentation corrections

Fixes

forced_matches was a set of strings, not a dict - I missed that
Analysts have requested that the Variant level matching tooltip is updated to also be a person. Little Man = match priority, Star = gene is new
There was an issue whereby some PanelApp entries were dumped onto panels with only semi-structured activity log entries. This has caused some old entries to appear new

Proposed Changes

update the report icons, and edit the colours and tooltips
expand PanelApp activity search to catch earlier unstructured entries
Correct how forced_matches is being processed

We just dropped the Phenotype Match column, which was asked for here https://github.com/populationgenomics/automated-interpretation-pipeline/issues/435
I like where the phenotype match icon is at the moment, so we could add a separate column at the far edge which just had a simplified Y/N for filtering on. I'm not sure if the HTML columns we're using at the moment will allow filter on by default? If they do that's simple.
At the moment we produce 2 final reports, one restricted down to just phenotype matches, the other with everything. We probably don't want to use the match-only here as it would limit searching


[Bug]: Titling being done by chat model

Contact Details
No response
What happened?
I originally noticed the issue when sending prompts via gpt-4-32k. I could see in my API usage that I was getting doubled charged from this API for every new chat I would start. It was clear that the second charge was due to the use of gpt-4-32k to choose the title. Now I begrudge paying $0.5-1 for a single prompt anyway, but doubling it for the chat title is too much. I originally thought this was intended behaviour as to deal with very large prompts that don't fit in the gpt-3.5-turbo context. (Even so, my preferred behaviour in this instance is to leave the chat untitled if it is too big to fit). However, I noticed that it will use gpt-4-32k for titling even with a small prompt, so I figured something is wrong that it is always using the active chat model.
I chased the bug down to the following source. OpenAIClient.titleConvo() tries to pass gpt-3.5-turbo-0613 (or gpt-3.5-turbo) to  setOptions() (via sendPayload()). But   setOptions() fails to update the class property appropriately, code here:
const modelOptions = this.options.modelOptions || {};
    if (!this.modelOptions) {
      this.modelOptions = {
        ...modelOptions,
        model: modelOptions.model || 'gpt-3.5-turbo',
        temperature:
          typeof modelOptions.temperature === 'undefined' ? 0.8 : modelOptions.temperature,
        top_p: typeof modelOptions.top_p === 'undefined' ? 1 : modelOptions.top_p,
        presence_penalty:
          typeof modelOptions.presence_penalty === 'undefined' ? 1 : modelOptions.presence_penalty,
        stop: modelOptions.stop,
      };
    }

If this.modelOptions already exists (which it will once any message is sent I assume), it will not be updated. That means the model used for titling cannot differ from the model used for chatting, which seems suboptimal. To fix this I will be submitting a PR with a small change to add an else clause that simply updates the model. This is a bit of hack and doesn't fix the wider issue of letting the user decide what model to use, and for very long gpt-4-32k prompts (there will be an error and the chat will remain untitled in that case). But it will prevent people getting a fright from much larger than expected API costs, which seems most pressing.
Steps to Reproduce

For chatting, choose a model other than those in the gpt-3.5-turbo-* family.
Check API calls and see that the chosen chat model is being double called for every new chat created.

What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Thanks for reporting this, I'll look into this soon, as it's definitely not intended.
Also, the newer title method using langchain tries to limit the entire title prompt to under 100 characters or less, regardless of the size of the prompt, because it only uses snippets, but I can also update the older method to behave the same way, which is a fallback. It may be that the fallback method is being used here, maybe a symptom of openrouter or the particular model you selected. I also use openrouter so I can test with your exact configuration.

Thanks for reporting this, I'll look into this soon, as it's definitely not intended.
Also, the newer title method using langchain tries to limit the entire title prompt to under 100 characters or less, regardless of the size of the prompt, because it only uses snippets, but I can also update the older method to behave the same way, which is a fallback. It may be that the fallback method is being used here, maybe a symptom of openrouter or the particular model you selected. I also use openrouter so I can test with your exact configuration.

No worries. My PR is there if you want to take a look. It is quite a simplistic fix. It's my first ever PR in a repo other than my own, so apologies if it isn't up to scratch.

No worries. My PR is there if you want to take a look. It is quite a simplistic fix. It's my first ever PR in a repo other than my own, so apologies if it isn't up to scratch.

Any PR is a good PR in my book! Thanks for doing that. I plan to approve and do the bit of work to minimize token usage further for titling while also making the model configurable and and the whole feature optional


Send also the old state to the onStateChanged() callback

Problem
Listeners of the onStateChanged() callback cannot know the previous state the behavior was in. Knowing the old state is useful to perform one time operations.
For example, while the new state isSTATE_DRAGGING the onStateChanged() callback will be called ~several times~ and there is no way of knowing where it came from before. But we might be interested in performing an action only when the state is changing from STATE_COLLAPSED to STATE_DRAGGING.
Solution
We add the param oldState to the callback.

explicitly checks whether mState == state.

True. I missed that. Still, the problem applies. I updated the PR description.

Also, the same could be achieved by caching the latest value of newState externally, e.g.

Sure. That's how I'm currently doing. Just felt like it belonged in the lib instead.

@justasm Could you merge this?


Question about how to use elucidated_diffusion

I apologize in advance for this very naive question, but could you possibly provide an example (or the basics) of using elucidated_diffusion, similar to how you provided an example of using Unet and GaussianDiffusion from the denoising_diffusion_pytorch library in the readme ?

I agree with the comment above. It would be great to have some examples or documentation about how to use each of the replicated models. Could you add some to the README @lucidrains ?
I would love to see an example on how to use the new model in repaint.py, specially on how to use the ground-truth image and a mask to reconstruct the masked region as in the original paper.
Thank you for your time :)


Create issues for features of the roadmap

IMHO it's better to track issues in a GitHub issue than a roadmap in the Readme.
PS: Citadel looks so great! Just wow!

Hmm, you might be right - I'll most likely move them over to issues marked as enhancements.
That way I can reference them in my commits and PRs.
Thanks for the suggestion!


rename models --> plugins in manifest files

Story
As a user I want to see consistent naming across the repositories.
Rationale
We refer to plugins now instead of "models", but we still require the initialize/models field to exist in manifest files. We should update this to initialize/plugins
Implementation details
Update all example manifest files to use plugins instead of models in the initialize section.
Update the IF source code to expect plugins instead of models.
Priority
3/5
Scope
Will affect the IF source code and the example manifest files.
Size
0.5 day
What does "done" look like?
Field renamed plugins, all example manifests run as expected and all unit tests pass
Does this require updates to documentation or other materials??
Yes, any example manifests in READMEs and docs website should be updated to use the plugins term
What testing is required?
All test manifests should run correctly and all unit tests pass
Is this a known/expected update?
Not previously discussed

Closing as complete


Weird scrolling behavior

Describe the issue
When scrolling with an external mouse slowly, you may have to turn the wheel 2-4 times before the scrollbar reacts. This happens on every app I tried, both GUI and TUI. This does not happen with the trackpad --- you can drag slowly and the scrollbar will still react.
Configuration

UTM Version: 4.4.0
macOS Version: 11
Mac Chip (Intel, M1, ...): M1

Crash log
Debug log
Upload VM

Yeah this is a side effect of how SPICE sends the scroll events. It translates them to button presses (up or down) and sends the button presses to QEMU which gets sent to the guest and the guest re-intreprets them as scroll. My guess is that in this process, the guest does not see the scroll until a few "presses" in a single direction.

I think a proper fix would be to pass the scroll events directly to QEMU as HID events. Or a new SPICE channel to send the scroll events directly.

I also suffer from this problem.
Processor: Intel Core i5
O.S.: MacOS Ventura 13.6.1
UTM version: 4.4.4 (92)
Mode: Virtualized and with QEmu Engine
Guest O.S.: Debian 12.2.0 x64
I just recently migrated from VirtualBox.
It really strikes me that, until now (2 months ago), no one has reported this REAL problem.
Please fix it as soon as possible because, in this case, the use of UTM becomes practically unfeasible.

Any workarounds on this mouse issue?

I was forced to buy magic trackpad, it works excellent.

Last comment in the other ticket has a working workaround: https://github.com/utmapp/UTM/issues/3417#issuecomment-2139633302
In the Mos program (which is the fix), I had to set "Step", "Speed", and "Duration" to minimum values though, and it still scrolls more than I would like, but at least it scrolls immediately now.

Hold on, "Duration" has to be set to maximum value, not minimum value. But now the mouse wheel scrolls far too slow in the host. Well, I guess it's possible to configure both host and client to be decent somehow.

If you own a fancy mouse you can set app-specific scroll speed in your mouse software's settings. Or alternatively brew install mos and cross the fingers that it does not steal your passwords.


Getting “A Script on this page may be busy, or it may have stopped responding” issue in jspdf.debug.js only in firefox

I'm trieng to create html content to PDF. I'm using thes two files (jspdf.debug.js,  html2canvas.min.js).
In chrome i can download the pdf. But in firefox throwing stop script issue.
This way i'm passing my html content.
$(".power_of_acc_submit").click(function() {
var doc = new jsPDF('p', 'pt', 'a4');
var options = {
pagesplit: true,
};
doc.addHTML($j('#form_preview'), 0, 0, options, function() {
doc.save('Account Opening Document.pdf');
});
});
Single page content working perfectly. This issue happening only for  mutiple pages.
Any help or guidance would be much appreciated.

Hi there,
There's now a html2pdf example which much better supports generating documents from HTML.
Get the latest master and try:
npm install
npm start

Then visit localhost:8000/examples/html2pdf/showcase.html
Hope this works well for you :)
Many thanks,
James


Update da.js

Should add the firstDayOfWeek option to 1 since it's in Denmark.

Coverage remained the same at 83.948% when pulling 048e7c6f39e5fe21b564470615083bce33d75262 on sebastianks:patch-1 into 1dadfb9f561700183b0b14d6b78457437779c731 on chmln:master.


Whitelist

Heyo,
I really like this project. I have set it up today in 3 hours with docker-compose, and it is super cool. The only thing I miss is a whitelist functionality to be able to use whitelists addtionally to blocklists.
I guess why that makes sense is obvious.
Best regards,
simwai

Glad you like leng!
Did you try the config Blocking.whitelist? Or are you looking for something else?
For example:
[Blocking]
    # comment for reference
    whitelist = [
        # "getsentry.com",
    ]


editColumn escaping HTML

Summary of problem or feature request
I'm looking to edit a column to include a link.  It's working, except the HTML is being escaped therefore rendered as text instead of HTML.
Not sure what I am missing to have the HTML not be escaped.  I have passing a template as the second argument and placing the HTML::linkRoute call in the template file, but same result.
Code snippet of problem
return Datatables::of($people)
    ->editColumn('firstname', '{!! HTML::linkRoute("person.show", $firstname, $userid) !!}')
    ->make(true);

And it returns:
firstname: "SomeFirstName"

System details

Debian 8
7+
5.4
7.2

Answering my own question.  Solution was using the well documented raw columns.
return Datatables::of($people)
    ->editColumn('firstname', '{!! HTML::linkRoute("person.show", $firstname, $userid) !!}')
    ->rawColumns(['firstname'])
    ->make(true);

for versions above 8, u have to go to config/datatables.php file....and add your column name in ....raw => ['name_of your_column']

How to resolve this in Datatables 6.0?
Somehow, i need this on Laravel 5.1.
Thanks


argparse.hpp

A great work! when I try to make ,and argparse.hpp :No such file.I have installed argparse in python3,could you please tell me why?

Please try updating the submodules as follows:
git submodule update --init --recursive


Support GTFS feeds

Do a bbox intersection with the feeds from mobilitydata.org, then download the ones that intersect, I guess? That makes sense for now, but if people do larger installations they may want to pick and choose which ones they download.

It looks like a lot of transit feeds require API keys so what I'll probably end up needing to do is writing a little cache layer that headway instances can talk to for transit data. This cache layer would keep custody of the API keys I receive and limit upstream request rate to something reasonable. But it looks like completely automated GTFS feed downloads aren't in the cards.

This is implemented now


Update Style/RedundantSort to be unsafe

In an array where there are multiple elements where a <=> b == 0, or where the transformation done by the block has the same result, there will be a different element returned between sort.last and max (or sort_by.last and max_by), because sort.last will take the last element but max will return the first element. As such, this is not a safe change, as the specific element returned will change.
Honestly, we should probably revert #10062 as well because that adds a special case for size that doesn't really exist in reality. In that issue, size was the catalyst, but the exact same issue would happen with length, or any other transformation that results in multiple elements having the same value. If we revert #10062, then #10119 can be closed as well. If this is desired, I'll update this PR to include the revert and add the test case from #10119 which is still valueable.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

@koic are you ok with reverting your change like I proposed?

@bbatsov any thoughts?

I'm fine with your proposal and reverting the extra commit that attempted to fix this before.

@bbatsov the special case for size is now reverted in addition to the cop being made unsafe.


Feature: Switch settings dialog to tab

Summary
As the title.

[x] test what happens if settings is opened in multiple tabs

Working very well!!

[ ] disable dual pane mode
[ ] hide the status bar & preview pane
[ ] create a colored icon to use for the tab
[ ] settings is currently disabled in compact overlay mode, we'll need to figure out how to handle this
[ ] decide if we should move the settings icon from the address bar to the sidebar

PR Checklist

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[x] Did you implement any design changes to an existing feature?

[x] Was this change approved?

[ ] Are there any other steps that were used to validate these changes?

Screenshots

This is still just a proof of concept to test if we can dive into tabs. We plan to use our own custom icons called OpacityIcon, which can be set multiple colors like accent color and secondary/tertiary colors.