make the default theme to be "dark"

Is it possible to make the default switch to the left which is the "moon" side and the theme to be dark?

Hi @ron1818  - this is a great question!  I'll be sure to update the docs too.
Here is an example of how to change the sample app in the on-line docs for the theme switch components to start with a dark theme:

When the app starts, instead of url_theme1, which is the light theme:

app = Dash(__name__, external_stylesheets=[url_theme1, dbc_css])

Change it to url_theme2, which is the dark theme:
app = Dash(__name__, external_stylesheets=[url_theme2, dbc_css])

Update the switch so it starts on False  (to the left) rather than the default True (to the right)

So instead of this:
ThemeSwitchAIO(aio_id="theme", themes=[url_theme1, url_theme2])

It's now like this:
ThemeSwitchAIO(aio_id="theme", themes=[url_theme1, url_theme2], switch_props={"value": False})

Here's the whole app with the dark theme default:

from dash import Dash, dcc, html, Input, Output
import plotly.express as px
import dash_bootstrap_components as dbc
from dash_bootstrap_templates import ThemeSwitchAIO

# select the Bootstrap stylesheets and figure templates for the theme toggle here:
template_theme1 = "flatly"
template_theme2 = "darkly"
url_theme1 = dbc.themes.FLATLY
url_theme2 = dbc.themes.DARKLY

dbc_css = (
    "https://cdn.jsdelivr.net/gh/AnnMarieW/dash-bootstrap-templates/dbc.min.css"
)
app = Dash(__name__, external_stylesheets=[url_theme2, dbc_css])

df = px.data.gapminder()
header = html.H4("ThemeSwitchAIO Demo", className="bg-primary text-white p-4 mb-2")
buttons = html.Div(
    [
        dbc.Button("Primary", color="primary"),
        dbc.Button("Secondary", color="secondary"),
        dbc.Button("Success", color="success"),
        dbc.Button("Warning", color="warning"),
        dbc.Button("Danger", color="danger"),
        dbc.Button("Info", color="info"),
        dbc.Button("Light", color="light"),
        dbc.Button("Dark", color="dark"),
        dbc.Button("Link", color="link"),
    ],
    className="m-4",
)
graph = html.Div(dcc.Graph(id="graph"), className="m-4")

app.layout = dbc.Container(
    dbc.Row(
        [
            dbc.Col(
                [
                    header,
                    ThemeSwitchAIO(aio_id="theme", themes=[url_theme1, url_theme2], switch_props={"value": False}),
                    buttons,
                    graph,
                ]
            )
        ]
    ),
    className="m-4 dbc",
    fluid=True,
)

@app.callback(
    Output("graph", "figure"), Input(ThemeSwitchAIO.ids.switch("theme"), "value"),
)
def update_graph_theme(toggle):
    template = template_theme1 if toggle else template_theme2
    return px.scatter(
        df.query("year==2007"),
        x="gdpPercap",
        y="lifeExp",
        size="pop",
        color="continent",
        log_x=True,
        size_max=60,
        template=template,
        title="Gapminder 2007: '%s' theme" % template,
    )

if __name__ == "__main__":
    app.run_server(debug=True)

Hi, thx for this super component, I really like it. I have a problem with the example presented in this thread. When I start the application the graph background is dark, as expected, but the rest of the page background is white. I have to toggle the switch to light theme and re-toggle to dark theme to have a dark background for the whole web page. Any thoughts on how to fix that?

@brogrammeur
Glad you like the component - thanks for your kind words.  :blush:
I noticed this recently as well, and it's a bug in how the theme is initially set.  The best workaround for now (until I can fix this) is to keep the switch position in the default True to start,  and change which side the icons are located.  It will also be necessary to swap which theme is updated in the callback to use the correct figure template.
Here is a complete minimal example:

from dash import Dash, dcc, html, Input, Output
import plotly.express as px
import dash_bootstrap_components as dbc
from dash_bootstrap_templates import ThemeSwitchAIO

# select the Bootstrap stylesheets and figure templates for the theme toggle here:
template_theme1 = "flatly"
template_theme2 = "darkly"
url_theme1 = dbc.themes.FLATLY
url_theme2 = dbc.themes.DARKLY

theme_toggle = ThemeSwitchAIO(
    aio_id="theme",
    themes=[url_theme2, url_theme1],
    icons={"left": "fa fa-sun", "right": "fa fa-moon"},
)

dbc_css = (
    "https://cdn.jsdelivr.net/gh/AnnMarieW/dash-bootstrap-templates/dbc.min.css"
)
app = Dash(__name__, external_stylesheets=[url_theme2, dbc_css])

df = px.data.gapminder()
header = html.H4("ThemeSwitchAIO Demo", className="bg-primary text-white p-4 mb-2")
buttons = html.Div(
    [
        dbc.Button("Primary", color="primary"),
        dbc.Button("Secondary", color="secondary"),
        dbc.Button("Success", color="success"),
        dbc.Button("Warning", color="warning"),
        dbc.Button("Danger", color="danger"),
        dbc.Button("Info", color="info"),
        dbc.Button("Light", color="light"),
        dbc.Button("Dark", color="dark"),
        dbc.Button("Link", color="link"),
    ],
    className="m-4",
)
graph = html.Div(dcc.Graph(id="graph"), className="m-4")

app.layout = dbc.Container(
    dbc.Row(
        [
            dbc.Col(
                [
                    header,
                    theme_toggle,
                    buttons,
                    graph,
                ]
            )
        ]
    ),
    className="m-4 dbc",
    fluid=True,
)

@app.callback(
    Output("graph", "figure"), Input(ThemeSwitchAIO.ids.switch("theme"), "value"),
)
def update_graph_theme(toggle):
    template = template_theme2 if toggle else template_theme1
    return px.scatter(
        df.query("year==2007"),
        x="gdpPercap",
        y="lifeExp",
        size="pop",
        color="continent",
        log_x=True,
        size_max=60,
        template=template,
        title="Gapminder 2007: '%s' theme" % template,
    )

if __name__ == "__main__":
    app.run_server(debug=True)

@brogrammeur I just published v1.0.6 with a fix - so both examples in this issue should work.  Could you please verify that it works for you?

Wow. Super quick. I confirm that it works correctly on my side.
I originally found the bug when I was trying the switch persistence attribute, and I found this thread when I was looking for a solution. I can also confirm that it works correctly when using the persistence. Thank you very much.

:partying_face:  Great news - thanks! I'll close this issue


$stateChangeStart is fired after URL & history are already updated in browser

When preventing default on $stateChangeStart, doing some work, and then resuming the state change, everything works basically as expected. However, the URL in the address bar flickers back and forth, and what appears to be an extra history entry shows up in the back button history. This is because $stateChangeStart is broadcast after the transition has been executed, then it checks for defaultPrevented, in which case $urlRouter.update() is called to redirect back to the "current" location.
I confirmed that I can get better behavior by broadcasting an event before redirecting, and actually canceling the transition before it happens.

For other folks trying to do this, here's what I did. I added in a $beforeStateChange event so that I can preventDefault without inserting the extra history entry. This is in my run() block in app.js:
var transitionTo = $state.transitionTo;
    $state.transitionTo = function(to, toParams, options) {
        var from = $state.$current,
            fromParams = $state.params;

        to = to.name ? to : $state.get(to);

        if (options.notify !== false && $rootScope.$broadcast('$beforeStateChange', to, toParams, from, fromParams).defaultPrevented) {
            return $q.reject(new Error('transition prevented'));
        } else {
            return transitionTo(to, toParams, options);
        }
    };

@mgrahamjo Can you show me what your event listener looks like. I think what you're doing here is exactly what I need to do to fix an issue I'm having in my app.
Unfortunately for me, $rootScope.$broadcast("$beforeStateChangeStart", to, toParams, from, fromParams).defaultPrevented seems to always be false for me, so the transition continues through every time.
Would love to know how you go this to work.

@dmigliorisi sorry for the wait. Here's my listener, basically. This is in a directive that handles page transition animations as well as pop-ups that alert the user if they're about to lose unsaved work.
$scope.$on('$beforeStateChange', function(e, to, toParams, from, fromParams) {

    e.preventDefault();

    transition = {
      to: to,
      toParams: toParams,
      from: from,
      fromParams: fromParams
    };

    // ... 400 ms animation, then:

   $state.transitionTo(transition.to.name, transition.toParams, { notify: false });

});

I found that using the option {location: 'replace'} did the job.

@morgs32 : could you please elaborate more how have u used this  { location: 'replace' } to prevent back button rewriting history?
I m trying to do following in run block in app.js, however this is not working for me:

$rootScope.$on('$beforeStateChange', function (e, to, toParams, from, fromParams) {
            e.preventDefault();
            debugger;
            var transition = {
                to: to,
                toParams: toParams,
                from: from,
                fromParams: fromParams,
            };
            // ... 400 ms animation, then:
            $state.transitionTo(transition.to.name, transition.toParams, { notify: true });
        });

        var transitionTo = $state.transitionTo;
        $state.transitionTo = function (to, toParams, options) {
            debugger;
            var from       = $state.$current,
                fromParams = $state.params;

            to = to.name ? to : $state.get(to);

            $rootScope.$broadcast('$beforeStateChange', to, toParams, from, fromParams);
            if (options.notify !== false && res.defaultPrevented) {
                console.log('transition prevented');
                return $q.reject(new Error('transition prevented'));
            } else {
                return transitionTo(to, toParams, options);
            }
        };

@maverick09 I believe location: replace was an option passed to $state.go or $state.transitionTo that would replace the fromState with the toState in the history. In other words, after the transition, hitting the back button would NOT take you to the fromState (from which you called the transition). The back button would go to state before that.
Is that clear? I'm not sure how it applies to your code. What isn't working?

I have this exactly same issue where I can see that $stateChangeStart is
being called twice when Back button in browser pressed. That modifies
browser's last viewed page in history to current page from where I have
clicked back button. For example:
State1: setOne.Result
State2: setOne.Availability
State3: setTwo.Sim
State4: setTwo.Boost
Page sequence is : State1 > 2> 3 > 4
However suppose I am currently on setTwo.Boost ( last state ) & press
browser back button, address bar flicks, and browser loads State3.
After that if I press Back button again , then ideally it should go to
State2 however it goes to State4 again.
Does that make sense?
On 13 October 2016 at 16:02, Morgan Intrator<EMAIL_ADDRESS>wrote:

@maverick09 https://github.com/maverick09 I believe location: replace
was an option passed to $state.go or $state.transitionTo that would replace
the fromState with the toState in the history. In other words, after the
transition, hitting the back button would NOT take you to the fromState
(from which you called the transition). The back button would go to state
before that.
Is that clear? I'm not sure how it applies to your code. What isn't
working?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/angular-ui/ui-router/issues/1780#issuecomment-253539975,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACkQi7qMd3ujapPLONPFSifAkEO0_ybFks5qzkgcgaJpZM4Dl9ZS
.

I have similiar problem as @maverick09, but for me the sequence ends up like this:
State 4 > State3 (without params in url) > State 3 (with params in url) > state 2 > state 1
Also, when I go back from state 4 to state 3, I can't go forward to state 4 again.

@whiterockerart @maverick09 are you making $state.go redirects in resolves or in statechangestart? or transitionTo - I've experienced odd things when I try redirecting or adding params during state changes.

@morgs32, neither. Using ui-sref and updates the url with params with $location.url() and $location.search().
Our company are over one year into this development and has a lot of special cases, which isn't easy to change without breaking whole application.

i think that might be it. i'd be very wary of using $location to do any setting - just getting. ui-router wants you to use $state.go and set params. http://stackoverflow.com/questions/29176566/location-search-setter-not-causing-reload-in-ui-router
perhaps...

@morgs32 I did change $location.url() to $state.go('state'. params) and sure it works, but I can't traverse the application back or forward with the browser buttons.
history.state gives null all the time.
Running angular 1.5.8 and ui-router 0.31

really... that comes out of the box. such as, if you compare your app to their sample app, do you notice any significant inconsistency? are you using $locationProvider in any weird way? or $urlMatcherFactoryProvider?

actually. just checked. my history.state is also null but that doesn't prevent me from using the back/forward buttons.

After using $state.go() I could use this solution: http://stackoverflow.com/a/22402285
It works, but for some reason I loose one parameter (that actually is set). But, I have to solve that on my own.

Interesting, $state.go() messes up everything, one important part of the application stops working properly and it daosn't matter if I set options {location: false/true/"replace" } - it won't work!
The idea of this state is that it can take multiple params and updates itself depending on which params is used or set. think of a filetree in an explorer os something like that.
I have to use $location.url() - unfortunately.

In case this helps anyone: A workaround I found was to reinsert the state I was coming from when the transition is stopped. Like this:
$rootScope.$on( '$stateChangeStart', function( event, toState, toParams, fromState, fromParams ) {
  var answer = window.confirm( 'You sure?' );
  if( !answer ) {
    event.preventDefault();
    $state.go( fromState, fromParams );
  }
}

@mgrahamjo Great suggestion appreciate very much. But can you elaborate this a bit. why
$state.transitionTo = function (to, toParams, options)   is getting called before stateChangeStart and overriding exiting method.


Add member table to cargo config

This PR attempts to fix #7004. While I intend to get this merged eventually I am aware that this implementation is somewhat ugly right now since I avoided major refactorings. Any feedback is appreciated. I have discussed the implementation options here.
This introduces [member.'name'] tables into .cargo/config. The tables right now have the single member target which defines the target of a member crate if it is set. For the member crate this key takes precedence over the build.target value and the --target CLI argument. This is useful for crates where differing targets do not really make sense such as for WASM or UEFI binaries.
I am not sure if this needs an RFC. IIRC past RFCs mainly concern themselves with the manifest format so I assume .cargo/config.toml format is not covered by the RFC process. Is this correct?
The new functionality is marked unstable (-Z member-configs).

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @ehuss (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks for the PR!  Almost all major changes to Cargo typically go through the RFC process, though sometimes we allow nightly-only changes if the design is well understood.
I think in this case there is a bit of design space to explore. Generally we haven't allowed workspace-specific settings in config files. Config files are intended more for local-system settings (although admittedly that doesn't always follow in practice). I think for specifying things like this, it would probably want to lean more towards placing settings in Cargo.toml, such as in the [package] table, maybe as a default-target key (or default-targets now that Cargo supports multiple targets?). Additionally, there's some uncertainty about how more sophisticated target settings might be expressed. For example, there is a desire to be able to specify the supported targets of a package or cargo-target (#6179).
These may or may not have some interaction, but I'm not clear on how they might.

:umbrella: The latest upstream changes (presumably #8799) made this pull request unmergeable. Please resolve the merge conflicts.
Note that reviewers usually do not review pull requests until merge conflicts are resolved! Once you resolve the conflicts, you should change the labels applied by bors to indicate that your PR is ready for review. Post this as a comment to change the labels:
@rustbot modify labels: +S-waiting-on-review -S-waiting-on-author

@ehuss

I think for specifying things like this, it would probably want to lean more towards placing settings in Cargo.toml, such as in the [package] table, maybe as a default-target key (or default-targets now that Cargo supports multiple targets?).

I really like this idea and I think that it would fix most issues I have with .cargo/config files today. What do you think would be the process to implement something like this? Would it require an RFC directly or would it be ok to implement it as an unstable feature for experimentation first (to find out which .cargo/toml keys are useful in Cargo.toml)?

A default-target field would be nicer than this.
One of the reasons I did this in config in the first place was that I was certain changes to Cargo.toml would need to go through the RFC process while I thought the config was treated as an implementation detail. I guess this was not correct.

@Richard-W I just created a related proposal to replicate all package-specific .cargo/config settings in Cargo.toml files: https://internals.rust-lang.org/t/proposal-move-some-cargo-config-settings-to-cargo-toml/13336.

Closing because there are better approaches than this one.


HttpJsonCallContext equals() & hashCode are incorrect

Currently all instances of HttpJsonCallContext have the same hashCode & are equal to each other. I think those methods were never updated after new fields were added

Oops, looks like I already filed this #479


javax.annotation,version -- Cannot be resolved

Hi, I'm working with Archetype 15 and AEM 6.4 version. When deploying the snapshot I got this error

Do anyone know if I need to add some other dependency to my mvn project?

I tried adding javax.annotation dependency version 1.3 and 1.2 to parent POM file, still the same issue exist

+1, how do we fix the org.apache.sling.api.resource 2.11 issue shown above?

I found the fix, I put the right version on the core/pom file:
https://youtu.be/lKWHsVh1hRA

@mowadigital

javax.inject;version=0.0.0,
javax.annotation;version=0.0.0,
org.apache.sling.api.resource;version="[2.10,3)"

Is this the only thing need to be added to core/pom file? or some other dependencies needed

Thank you so much @mowadigital
The solution worked for me


when I run the code this error apeared

NameError                                 Traceback (most recent call last)
 in
12 # from tqdm import tqdm_notebook as tqdm
13
---> 14 from arctor import create_raw_lc_stddev, Arctor, run_multiple_pymc3#, setup_and_plot_GTC
15 from arctor.utils import setup_and_plot_GTC, compute_delta_sdnr
16 # from arctor.utils import fit_2D_time_vs_other
~/.local/lib/python3.8/site-packages/arctor/init.py in
1 from . import *
----> 2 from .arctor import Arctor
3 from .utils import *
4 from .dwt import *
5
~/.local/lib/python3.8/site-packages/arctor/arctor.py in
23 from tqdm import tqdm
24
---> 25 from .utils import (
26     center_one_trace,
27     fit_one_slopes,
~/.local/lib/python3.8/site-packages/arctor/utils.py in
1006                        do_mcmc=False, save_as_you_go=False,
1007                        injected_light_curve=1.0, working_dir='./',
-> 1008                        base_name=f'{planet_name}_fine_grain_photometry_208ppm'):
1009
1010     decor_set = [xcenters, ycenters, trace_angles, trace_lengths]
NameError: name 'planet_name' is not defined

Hello @MohammadEftekhar, I just got around to seeing this issue. Thank you for posting it.
You have to define planet_name = <name of directory> or base_name = <filename for saving>
I will set a default planet_name="planet_name" to make up for that though.
Thank you for work

I also changed the master branch name to "main"


Edit and apply the config map

Please add the ability to edit and update the config map

@dinar-dalvi, I'd like to collect other requests in regards with configuration and making changes to the cluster before jumping in to solution. Currently Kubevious only requests read-only access to the cluster. Requesting write permissions at this stage might significantly affect adoption rate.
Please tell more about your use case. Do you want to modify any config map? Are those mapped as volumes or used as environment variables? If there are other environment variables set on pod specs, would you like to modify those as well?
Based on your and others' use-cases the solution might be a extension would let ones to edit the cluster, or download a patch file to be applied through kubectl, or something else.

My use case as follows, we have a need to modify the config-map on the fly for some services. Post modify I can sale the pods down and back up so the change is picked up. For now i can do that doing kubectl but want to see if it's possible from the ui.

ok, got that. Transition from viewer to editor as major change. I'll keep the ticket open for some time to collect other feedback. Based on other use cases will be able to generalize. Thanks

If you give the opportunity to edit a config map you also need to give the opportunity to kill a pod as the config map is only loaded during start

@obeyler, good poing. We have a different solution for that. We are going to show the pods/deployments that are "out-of-sync" from configmaps. That should work regardless how the configmap was modified. But that is different from this feature request

@dinar-dalvi, @obeyler, while Kubevious is still using a read-only access to Kubernetes, we added capability to sanitize the YAML files (remove generation, uid, selflink, status, etc files), edit the file in place, and download edited file ready to be applied with kubectl or to be checked in to git (of you use something similar to GitOps). Kubevious also creates the kubectl command to be copy-pasted to terminal for quick execution.
Here is a quick screen recording of the capability: https://cln.sh/Ecr1u6
helm upgrade --atomic -i -n kubevious \
    --version 0.7.4 \
    --set ingress.enabled=true \
    kubevious kubevious/kubevious

[2020-08-07 15:55:01.635 +0000] INFO  (LocalLoader/1 on kubevious-parser-696d46c7bd-88489): [setupApiGroup] Lease :: coordination.k8s.io :: v1 :: leases...
***** ERROR *****
{
status: 503,
message: 'Service Unavailable',
method: 'GET',
baseURL: 'https://<IP_ADDRESS>:443',
url: '/apis/metrics.k8s.io/v1beta1'
}
[2020-08-07 15:55:01.640 +0000] ERROR (Context/1 on kubevious-parser-696d46c7bd-88489):
status: 503
message: "Service Unavailable"
method: "GET"
baseURL: "https://<IP_ADDRESS>:443"
url: "/apis/metrics.k8s.io/v1beta1"
So I think the pb is not on your part it may due to my last coredns version fix ;-)
Thanks ruben for the log who help me understand

@obeyler, thanks for trying out. Looks like your response was related to https://github.com/kubevious/parser/issues/4
Did you have a chance to take a look to editing capability? Does it help with making changes to configs?

i do not think kubevious (cluster one) should manage resources.... At least as it is right now. In our case, ie, we have a multitenant cluster where we have users who can use kubevious to check their workloads together with cluster admins. Allowing the UI to do changes on the fly would require a security layer in top probably based on rbacs, etc.

i do not think kubevious (cluster one) should manage resources.... At least as it is right now. In our case, ie, we have a multitenant cluster where we have users who can use kubevious to check their workloads together with cluster admins. Allowing the UI to do changes on the fly would require a security layer in top probably based on rbacs, etc.

Letting Kubevious to modify resources would change the use model and would potentially conflict with existing processing like GitOps, etc.
@pedroparraortega, did you have a change to take a look to convenience capability to allow to modify the config in UI for download and copy-paste purposes. UI also sanitizes the config removing unnecessary props like uid, generation, selflink, status, etc.

i do not think kubevious (cluster one) should manage resources.... At least as it is right now. In our case, ie, we have a multitenant cluster where we have users who can use kubevious to check their workloads together with cluster admins. Allowing the UI to do changes on the fly would require a security layer in top probably based on rbacs, etc.

Letting Kubevious to modify resources would change the use model and would potentially conflict with existing processing like GitOps, etc.
@pedroparraortega, did you have a change to take a look to convenience capability to allow to modify the config in UI for download and copy-paste purposes. UI also sanitizes the config removing unnecessary props like uid, generation, selflink, status, etc.

i do not see any issues by allowing the UI do modifications always that those are not applied to the cluster.
@obeyler maybe for what you want to do, you can check this project Wave which allow you to configure dependent resources and the this will trigger the auto update of those objects

Resolved in v0.7.


Fix/agriculture feedback

This PR implements three subtasks from Agriculture feedback:
PIVOTAL
1. On Agriculture Drivers: show the name of the indicator on the legend, for instance, "Total Emissions" or something else that represents what we are seeing in the chart
BASECAMP

2. On Agriculture Drivers of Emissions remove two sectors from the pie chart: "Total including LUCF" and "Total Excluding LUCF", as these would cause a double counting, so should not be there.
BASECAMP

3. On the dropdown menu for Sectors in the header, add an extra "option" that is not selectable saying "Other Sectors Coming Soon"
BASECAMP

that was quick :) thanks @simaob


Create helm-upgrade-failure.md

Adds the troubleshooting folder and helm-upgrade-failure.md to the SMP docs.
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s) https://harness.atlassian.net/browse/DOC-2625

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-816

Preview environment: https://ci.pr.harness.io/pr-816

Preview environment: https://ci.pr.harness.io/pr-816

Preview environment: https://ci.pr.harness.io/pr-816

Preview environment: https://hdh.pr.harness.io/pr-816

@kapilgarg1996 Thanks for your comments. The edit/rewrites were not ready for tech review but I think I'm done now. I'll go back and look at the comments you've already made to make sure they were addressed. I see there was a note about adding information on troubleshooting self-signed certs -- should that information still be added from the provided link?
Thanks.

Preview environment: https://hdh.pr.harness.io/pr-816

Preview environment: https://hdh.pr.harness.io/pr-816

@pratmit I was going to put them into a Troubleshooting section in SMP. Then it can grow.

@kapilgarg1996 This is ready for you to take a look, if you have time. It would be good to know the categories you think should exist for SMP troubleshooting. We could eventually at metadata for problems associated with specific products or types of errors. Docusaurus -- the doc tool -- has some metadata tag potential that I hope we can start to use to "index" content.

Hey @kat-enos , the headings are formatting is a bit off. I have commented on specific parts.
Also, We can categorize the pages in the following manner

Database Issues
a. Check mongo db health
Network Issues
a. CI build pods error of filter_chain_not_found
Helm Install Failure
a. Ingress-controller port already allocated
Helm Upgrade Failure
a. Set Minio password
License Issues
a. License is not reflected on UI
i. Check license in DB
ii. Restart ng-manager pods
ii. Refresh License Cache

Thanks @kapilgarg1996 . Do you think those are the best categories to create for SMP? Seems like the Helm failures would come under Install and Upgrade issues or Install issues and then Upgrade issues, and then Helm-related failures would be a subcategory of that. Let me know.

@kat-enos we are de-commissioning KOTS so I am not sure if we should maintain troubleshoot documents for them. Can you check with Prateek Mittal for the same.

Also, can we capitalise the directory name, instead of troubleshooting, Troubleshooting

Preview environment: https://hdh.pr.harness.io/pr-816

@kapilgarg1996 and @pratmit I'm trying to wrap up the PRs that Katherine was working on. Can you take another look at this one and let me know if you think it's ready to be published? I think I addressed the most recent comments.

@kapilgarg1996 can you verify that the commands are still relevant?

@pratmit @KimberlyFields
We have reviewed the PR completely now. There are 2-3 minor comments post which we can merge this PR. Thanks

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


[FIX]: Wrong Feedback on first login attempt

Summary
When user try make your first login attempt with wrong data (email or password), appears a "Connection Error" instead of "Credential Error".
User story it relates to
#14

Solution
The toastr message is an enum and is used a useState to "save" the response error and get a message from enum.
The problem is, when show the toastr, this state contain the value -1. So the best approach it's create an useEffect to show the toastr (only show when have a change on this state)
	useEffect(() => {
		if (loginErrorCode !== -1) {
			setToastState({
				open: true,
				type: ToastStateEnum.ERROR,
				content: getAuthError(loginErrorCode)
			});
		}
		// eslint-disable-next-line react-hooks/exhaustive-deps
	}, [loginErrorCode]);


Fix move after free bug in connection pool

This fixes a relatively subtle use-after-free bug in the connection
pool. It only showed up in a specific cluster failure test and only
if the glibc malloc (as opposed to jemalloc) was used. A lock guard
destructor was using already freed memory and destroyed some
glibc/malloc internal thread local data structures.

Fix a use-after free.
CHANGELOG.

The fix speaks for itself and does not need any additional tests. It
was manually verified that this fixes the observed problem.
This is a backport of #14110 from 3.8 to 3.7.

The test failure is unrelated to this PR, see BTS-392. This is good to go.


Consider supporting YAML for hydra configs

This might be useful.
https://www.npmjs.com/package/node-yaml

I see PR#166 in theory handles this Issue .. but nothing on the PR request has happened??

The issue I raised privately (@taurenk and I work together) is that of adding another dependency. At one point I was on a crusade to slim Hydra (core) in size. My reason was that I wanted us to be able to claim that Hydra is a light-weight library.
I routinely use cost-of-modules to check on size.
$ npm install -g cost-of-modules
/Users/cjustiniano/.nvm/versions/node/v8.9.4/bin/cost-of-modules -> /Users/cjustiniano/.nvm/versions/node/v8.9.4/lib/node_modules/cost-of-modules/lib/index.js
+<EMAIL_ADDRESS>added 16 packages in 1.677s

$ cost-of-modules

Making sure dependencies are installed
npm install --production

up to date in 2.044s

Calculating...

┌──────────────┬────────────┬───────┐
│ name         │ children   │ size  │
├──────────────┼────────────┼───────┤
│ bluebird     │ 0          │ 0.59M │
├──────────────┼────────────┼───────┤
│ redis        │ 3          │ 0.26M │
├──────────────┼────────────┼───────┤
│ redis-url    │ 1          │ 0.17M │
├──────────────┼────────────┼───────┤
│ debug        │ 1          │ 0.06M │
├──────────────┼────────────┼───────┤
│ route-parser │ 0          │ 0.05M │
├──────────────┼────────────┼───────┤
│ umf          │ 0          │ 0.03M │
├──────────────┼────────────┼───────┤
│ uuid         │ 0          │ 0.02M │
├──────────────┼────────────┼───────┤
│ 7 modules    │ 4 children │ 1.01M │
└──────────────┴────────────┴───────┘

One way to support this might be to build a HydraPlugin (https://github.com/flywheelsports/hydra/blob/master/plugins.md) that adds yaml to json conversion.
The following are examples of HydraPlugins:

https://github.com/ecwyne/hydra-plugin-rpc
https://github.com/jkyberneees/hydra-plugin-http
https://www.npmjs.com/package/hydra-event-bus-plugin

Personally I don't have a "dog in this hunt" as it were -- I'm a TOML fan :)  The reason I bring this up though is because for those looking from the outside -- seeing "old" PR requests apparently "ignored" is not a good sign for an Open Source project.  The goal should be to merge or reject PR's ASAP .. and not leave them lingering .. But that's my opinion ..

@sjmcdowall thanks for the feedback. I've asked @taurenk to review here.


make default model of  a constant class variable

Why are these changes needed?
It involves interactions with OpenAI's API, managing configurations, and handling assistant threads and messages, incorporating a class-level constant for the default model name improves maintainability and clarity of the code. This change allows for a centralized point of reference for the default model, making updates or modifications simpler and more straightforward.

Related issue number
Closes #1777

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 8.33333% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 20.60%. Comparing base (fb2b412) to head (b205ca4).

Files
Patch %
Lines

autogen/agentchat/contrib/gpt_assistant_agent.py
8.33%
11 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1780       +/-   ##
===========================================
- Coverage   36.79%   20.60%   -16.19%
===========================================
  Files          62       62
  Lines        6477     6480        +3
  Branches     1432     1557      +125
===========================================
- Hits         2383     1335     -1048
- Misses       3899     4980     +1081
+ Partials      195      165       -30

Flag
Coverage Δ

unittests
20.60% <8.33%> (-16.19%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Final Fantasy XIV: VK_ERROR_DEVICE_LOST

There was a patch https://github.com/doitsujin/dxvk/commit/16a51f3c03d5bc52ba67101fb5a5cd5b8d96fa94 to help reduce issues with FFXIV and Nvidia Drivers 450.66 and possibly above but this just seems to have made the issue occur less. After about 12 hours strait of having the FFXIV client running I once again got the dreaded VK_ERROR_DEVICE_LOST. I see other games in the issues list are having this problem too with the same driver versions. I'm starting to think Nvidia just messed up version 450.66. I can confirm I never got this error with 440.100 so I am pretty sure this is a Nvidia driver issue.
Software information
Final Fantasy XIV
System information

GPU: GeForce GTX 960
Driver: 450.66
Wine version: lutris-5.7-10-x86_64
DXVK version: 1.7.2

Log files

d3d11.log: ffxiv_dx11_d3d11.log

I've patched and downgraded to 440.100 but with Kernel 5.8. I'll try to find a moment to leave the game running for at least 24 hours and see if I can replicate this bug. If I can't get this to happen again I'm really of the strong opinion Nvidia has introduced a bug into their drivers between the 44X and 45X series. Hopefully this information is useful for the dxvk devs.

We're aware of this but there's not an awful lot we can do about it on the DXVK side of things at this point.

So I tested 440.100 for 3 days (never restarted the client) and 0 issues 0 crashes. So if people want to continue using DXVK they should hold onto 440.100 as long as possible.

Is 450.66 the first version where this issue was introduced? The Nvidia website also has 450.57 and 450.51. Knowing the exact version might be helpful for a bug report.

450.66 was the first version to have this issue from what I tested. Thankfully I've tested the latest long lived version and this issue appears to be fixed. I ran the tests again for 3 days continuous game client usage. I experienced no errors with the following:
Software information
Final Fantasy XIV
System information

GPU: GeForce GTX 960
Driver: 450.80.02
Wine version: lutris-5.7-10-x86_64
DXVK version: 1.7.2

Apitrace file(s)
None
Log files

d3d9.log: None
d3d11.log: ffxiv_dx11_d3d11.log
dxgi.log: ffxiv_dx11_dxgi.log

I am unsure if the current short lived version (455.38 as of this post) has been fixed.

Hmm that's interesting because 450.80.02 does not mention any fixes but only support for some new GPUs. Though i have no idea how consistent nvidia it with their changelog. I'm pretty sure i saw the issue pop up on 455.38 when testing something unrelated though. But that may have been triggered by something else. Going to keep an eye out for it if it pops up again.

Nvidia is aware of the problem and looking into it.

Nvidia is aware of the problem and looking into it.

Do you have a link about it?

Any updates on this issue?

That's generally not a very useful question to ask; if there was then someone would likely have posted it already. Unless Nvidia figure out whatever it is that's causing their driver to crash, this will not get fixed.

My vk_error_device_lost error disappeared after i disable harddisk advanced power management.

Occurs on 460.27.4 as well

455.45.01 also broken, this really makes me want to switch from nvidia to amd...

A possible fix but this is completely anecdotal. Try either clearing out your ~/.nv/GLCache/ or doing export  __GL_SHADER_DISK_CACHE=0 with whatever way you're using wine. I haven't had a crash in awhile and this is the only thing I can think that I did lately that might affect DXVK.

There's now a post over at the Nvidia forums about this issue but I don't really have a high confidence in Nvidia fixing this (at least not with the replies I'm seeing on the post from them): Vk_error_device_lost in many game titles.

There's now a post over at the Nvidia forums about this issue but I don't really have a high confidence in Nvidia fixing this (at least not with the replies I'm seeing on the post from them): Vk_error_device_lost in many game titles.

460.32.03 broken as well

460.32.03 broken as well

Just to let everyone know I haven't had any issues since using export  __GL_SHADER_DISK_CACHE=0. Currently on 460.32.03. Can others here test that?

Just to let everyone know I haven't had any issues since using export  __GL_SHADER_DISK_CACHE=0. Currently on 460.32.03. Can others here test that?

Still broken 460.39.0.
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

~Just to let everyone know I haven't had any issues since using export __GL_SHADER_DISK_CACHE=0. Currently on 460.32.03. Can others here test that?~
Okay I had another crash so that doesn't work either, at this point I give up. People seeing this bug report need to go to the thread posted on the nvidia forums and actually post or this is never going to get fixed.
So please go add your voice to Vk_error_device_lost in many game titles.

Hello im facing the same bug for about 6 months. I tried many blind workarounds to no avail lastly ive installed lutris added wine 6.0 and built my kernel and out of tree modules with clang. I couldnt reproduce it for 2 weeks still so early to talk but i just wonder if there are any changes in the dxvk code that may fix that or my blind tries finally gave me a solution. And i built nvidia-drivers with dynamic libraries. I hope this helps, I use Gentoo Linux where those workarounds are very easy to apply.

It's fun when you find out mpv also has the same problem with nvidia drivers: https://github.com/mpv-player/mpv/issues/8360

I still havent got any vk_error_device_lost yet with my shot but i sure ill get it at some time. Did you read the driver recommendation there? Once i get that error again ill try one of those drivers. Now no errors yet for 2 weeks.
January 27th, 2021 - Windows 457.88, Linux 455.50.04
Fixed a bug in a stencil-buffer optimization that could occasionally result in VK_ERROR_DEVICE_LOST

@arabcian my results are posted throughout this thread, multiple people are still having the issue and my driver version is far higher than yours sitting at 460.39.0 so I am pretty sure the fix your listed has nothing to do with the problem as was also mentioned on the mpv bug report where they don't make use of stencil-buffers either. I also clocked up 3 days of continuous play time only to have the bug randomly come back when I thought it was fixed.

@konomikitten
Driver 460.39.0 is not necessarily "newer" than 455.50.04. The 455.50.xx driver series is of the "vulkan beta" series, and contains a lot more "vulkan fixes" than the "release driver" from the 460.xx series.
To simplify: 455.50.04 can contain a vulkan fix, the 460.39 driver does NOT contain since they are from two different branches.
When it comes to iffy nVidia random crashes + DXVK - Its always best to try the latest "vulkan beta" driver branch from here: https://developer.nvidia.com/vulkan-driver

@SveSop I stand corrected, that's some confusing version numbering.

@arabcian how many hours of FFXIV have you played to test for the crash by the way?

Just to let everyone know I am currently testing 455.50.04 as @arabcian recommended, it's looking good so far but considering the difficult nature of replicating this bug I'm going to be testing for a few weeks or more to make sure it is in fact fixed. If anyone else could test too that would be helpful.

Still broken. 455.50.04
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

@arabcian how many hours of FFXIV have you played to test for the crash by the way?

I couldnt test it yet with FF since  dont have the game but i was having same error with thief 2014 and World of Warcraft + Skyrim + Fallout 4,somehow bug is not around for a month. Still having mpd bug tho but im not if both are related.

Currently testing 455.50.07...

Still broken. 455.50.07
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

This should be fixed with 455.50.10:

Fixed a bug with the host-visible device-local memory heap, where if an allocation failed due to space constraints, it could cause the application to crash on future Vulkan function calls

@doitsujin oh thank god, I'll test it asap.

What is shown in syslog? (dmesg |grep -i nvrm ... or dmesg|grep -i xid)

$ sudo dmesg | grep -Ei 'nvrm|xid'
[    1.209379] r8169 0000:08:00.0 eth0: RTL8168g/8111g, e0:d5:5e:a6:68:bb, XID 4c0, IRQ 44
[    4.804576] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  455.50.10  Thu Mar  4 20:25:58 UTC 2021

It could be a faulty card maybe.

440.100 never crashed not even once and I can happily downgrade my kernel and nvidia drivers and never see this crash, which I have done multiple times.

I remember you giving a code to videos with vulkan in mpv and resizing windows was reproducing the same bug we experience. What was that command?

I remember you giving a code to run videos with vulkan in mpv and resizing windows was reproducing the same bug we experience. What was that command?

I never gave any command related to mpv I did link to https://github.com/mpv-player/mpv/issues/8360 where people using the vulkan backend with mpv were having similar crashes. As to why they get a kernel log involving Xid I imagine it's due to doing video playback, but I'm not entirely sure, the DXVK crash in this thread has never produced any error messages in the kernel log for me.

I remember you giving a code to run videos with vulkan in mpv and resizing windows was reproducing the same bug we experience. What was that command?

I never gave any command related to mpv I did link to mpv-player/mpv#8360 where people using the vulkan backend with mpv were having similar crashes. As to why they get a kernel log involving Xid I imagine it's due to doing video playback, but I'm not entirely sure, the DXVK crash in this thread has never produced any error messages in the kernel log for me.

Interesting thing is with mpv i get vk_error_device lost error with my intel igpu upon resizing and cant reproduce it with nvidia using 455.50.10

Still Broken 465.19.01.
ffxiv_dx11_d3d11.log
ffxiv_dx11_dxgi.log

I've downgraded all the way to 440.100 again and I'll be tested that for a good month or so.

I think I have the same problem with another (so far not listed) game: Project Wingman.
So as I understand it, there is nothing we can do about it except hope that the Nvidia devs will fix the problem.
However, I didn't want to miss the "fun" of sharing my logs of some of my crashes, even if it won't really help.
These frequent crashes (after 15-60 minutes) are especially frustrating in this game, since there are only save points after finishing missions.
Software information
GOG version of "Project Wingman" installed via Lutris <IP_ADDRESS>.
Config: set ENV "__GL_SHADER_DISK_CACHE_PATH" & "__GL_SHADER_DISK_CACHE_SKIP_CLEANUP: '1'", fsync tried on & off
System information

GPU: 1070
Driver: 460.67
Kernel: 5.11.10-1
OS: Manjaro Linux (KDE)
Wine version: tried multiple versions, all with the same result. Tested: lutris-4.21-x86_64, lutris-5.7-11-x86_64, lutris-6.4-x86_64
DXVK version: tried multiple versions, all with the same result. Tested: v1.5, v1.6.1+, v1.7.1, v1.7.3-4-g03f11baf, v1.8.1

More system infos
[System]
OS:              Manjaro Linux 21.0.1 Ornara
Arch:            x86_64
Kernel:          5.11.10-1-MANJARO
Desktop:         KDE
Display Server:  x11

[CPU]
Vendor:          AuthenticAMD
Model:           AMD Ryzen 7 2700X Eight-Core Processor
Physical cores:  8
Logical cores:   16

[Memory]
RAM:             31.4 GB
Swap:            34.5 GB

[Graphics]
Vendor:          NVIDIA Corporation
OpenGL Renderer: GeForce GTX 1070/PCIe/SSE2
OpenGL Version:  4.6.0 NVIDIA 460.67
OpenGL Core:     4.6.0 NVIDIA 460.67
OpenGL ES:       OpenGL ES 3.2 NVIDIA 460.67
Vulkan:          Supported

System:
  Kernel: 5.11.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.11-x86_64
  root=UUID=576659b2-353b-43cc-9510-aa3ac55bd386 rw quiet apparmor=1
  security=apparmor resume=UUID=d4c036ba-fcfd-415b-8df9-f4bf690b2aa7
  udev.log_priority=3
  Desktop: KDE Plasma 5.21.3 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
  Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: Micro-Star model: X470 GAMING PRO CARBON (MS-7B78)
  v: 1.0 serial: <filter> UEFI: American Megatrends v: 2.80 date: 03/06/2019
Memory:
  RAM: total: 31.37 GiB used: 10.9 GiB (34.8%)
  RAM Report: permissions: Unable to run dmidecode. Root privileges required.

Use of uninitialized value in concatenation (.) or string at /usr/bin/inxi line 2391.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    13  100    13    0     0     54      0 --:--:-- --:--:-- --:--:--    54
Network:
  Device-1: Intel I211 Gigabit Network vendor: Micro-Star MSI driver: igb
  v: kernel port: f000 bus-ID: 18:00.0 chip-ID: 8086:1539 class-ID: 0200
  IF: enp24s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
  broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: global
  IP v6: <filter> type: temporary dynamic scope: global
  IP v6: <filter> type: mngtmpaddr noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
  type: USB driver: r8152 bus-ID: 1-10:2 chip-ID: 2357:0601 class-ID: 0000
  serial: <filter>
  IF: enp3s0f0u10 state: down mac: <filter>
  WAN IP: <filter>
Bluetooth:
  Message: No Bluetooth data was found.
Logical:
  Message: No LVM data was found.
RAID:
  Message: No RAID data was found.
Drives:
  Local Storage: total: 4.55 TiB used: 24.07 TiB (529.3%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
  size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
  lanes: 4 rotation: SSD serial: <filter> rev: 2B2QEXE7 temp: 39.9 C
  scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
  size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
  rotation: SSD serial: <filter> rev: 1B6Q scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: HGST (Hitachi) model: HDN724040ALE640
  size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  rotation: 7200 rpm serial: <filter> rev: A5E0 scheme: GPT
  Optical-1: /dev/sr0 vendor: HL-DT-ST model: DVDRAM GH20NS15 rev: IL00
  dev-links: cdrom
  Features: speed: 48 multisession: yes audio: yes dvd: yes
  rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 430.95 GiB size: 423.18 GiB (98.20%)
  used: 356.21 GiB (84.2%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  label: Local Disk 1 uuid: 576659b2-353b-43cc-9510-aa3ac55bd386
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
  used: 280 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
  uuid: 71D1-C987
  ID-3: /data/nfs/Documents raw-size: N/A size: 20.95 TiB
  used: 20.63 TiB (98.5%) fs: nfs4 remote: <IP_ADDRESS>:/volume1/Documents
  label: N/A uuid: N/A
  ID-4: /home/<filter>/mount/Local Disk 2 raw-size: 465.76 GiB
  size: 457.45 GiB (98.22%) used: 405.69 GiB (88.7%) fs: ext4 dev: /dev/sda1
  maj-min: 8:1 label: Local Disk 2 uuid: 340457fe-a771-4dfa-933b-6a4fcdd5b794
  ID-5: /run/timeshift/backup raw-size: 3.64 TiB size: 3.58 TiB (98.40%)
  used: 2.7 TiB (75.4%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17
  label: Local Disk 3 uuid: 750c820d-d1e6-4d1f-a8d7-1772fde1ec50
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 34.52 GiB used: 0 KiB (0.0%) priority: -2
  dev: /dev/nvme0n1p3 maj-min: 259:3 label: N/A
  uuid: d4c036ba-fcfd-415b-8df9-f4bf690b2aa7
Unmounted:
  Message: No Unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: Full speed (or root) Hub ports: 14 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 1-10:2
  info: TP-Link UE300 10/100/1000 LAN (ethernet mode) [Realtek RTL8153]
  type: Network driver: r8152 interfaces: 1 rev: 2.1 speed: 480 Mb/s
  power: 180mA chip-ID: 2357:0601 class-ID: 0000 serial: <filter>
  Device-2: 1-11:3 info: MCT Elektronikladen farbwerk type: HID
  driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 2mA
  chip-ID: 0c70:f00a class-ID: 0300 serial: <filter>
  Device-3: 1-12:4 info: Logitech G Pro Gaming Mouse type: Mouse,HID
  driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s
  power: 300mA chip-ID: 046d:c085 class-ID: 0300 serial: <filter>
  Device-4: 1-13:5 info: Atmel WootingOne type: HID,Keyboard
  driver: hid-generic,usbhid interfaces: 7 rev: 2.0 speed: 12 Mb/s
  power: 400mA chip-ID: 03eb:ff01 class-ID: 0300 serial: <filter>
  Hub-2: 2-0:1 info: Full speed (or root) Hub ports: 8 rev: 3.1 speed: 10 Gb/s
  chip-ID: 1d6b:0003 class-ID: 0900
  Hub-3: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0
  speed: 480 Mb/s chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 speed: 5 Gb/s
  chip-ID: 1d6b:0003 class-ID: 0900
Sensors:
  System Temperatures: cpu: 41.8 C mobo: N/A gpu: nvidia temp: 50 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 19%
Info:
  Processes: 462 Uptime: 2h 15m wakeups: 0 Init: systemd v: 247
  tool: systemctl Compilers: gcc: 10.2.0 alt: 8/9 clang: 11.1.0 Packages: 2628
  pacman: 2595 lib: 585 flatpak: 12 snap: 21 Shell: Bash v: 5.1.0
  running-in: konsole inxi: 3.3.03

Logs
project_wingman-crash1.log
project_wingman-crash2.log
project_wingman-crash3.log
project_wingman-crash4.log
project_wingman-crash5.log
🥲
Greetings

That's probably not the same problem. Make a separate issue.

That's probably not the same problem. Make a separate issue.

Are you sure about that? My logs from 455.50.10 look a lot like @Retardium's...

Unfortunately yes, else I would be a happy gamer. But maybe the problem lies with the specific game (panzer corps 2) . I will try some other games next week and see if I have the same issue
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 440.100      Driver Version: 440.100      CUDA Version: 10.2     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 770     Off  | 00000000:07:00.0 N/A |                  N/A |
| 30%   49C    P8    N/A /  N/A |    184MiB /  1994MiB |     N/A      Default |
+-------------------------------+----------------------+----------------------+

Unfortunately yes, else I would be a happy gamer.

I guess @K0bin was right then sorry about that K0bin.

Unfortunately yes, else I would be a happy gamer.

I guess @K0bin was right then sorry about that K0bin.

Well I will try to do a full purge of nvidia and everything and install 440.100 from command line so I can more properly track what's going on because I found so many different versions of nvidia packages in my installation.
give me a bit more time

2 hours of clusterfuck and driver parts here and there and I managed to load a proper clean 440.100 installation (no 32bit support and no DKMS though) . I managed to actually play for more time than I ever managed on this game (like an hour) but it eventually crashed to our usual issue. I have to go to work now I will try some more with frostpunk tonight to see if it a reaccuring thing.

I've downgraded all the way to 440.100 again and I'll be tested that for a good month or so.

So it's been a month now and no crashes, I'm just going to stick with this kernel and driver version. I've pretty much given up on trying to update the Nvidia Driver and not have this issue occur.

But you should be using: 455.50.19
I can highly recommend purging the 4xx drivers entirely, make sure you clean up the dkms folder as well and then do a manual install. You will probably lose video if you try this, so do it from a SSH console.
This driver gives by far the best performance on my GTX970 and zero crashes thus far.

I upgraded my laptop now i have RTX 3060 mobile GPU and i can confirm errors are no more with any driver ive tried. This error is called xid31 by nvidia and latest 470 drivers have a fix for it.

Just found out about this issue and reported it on ticket 2253
I have drivers 470.57.2 and this issue is NOT fixed.

That's most likely an unrelated issue.
DEVICE_LOST just means the driver encountered an error for one reason or another.

Still Broken with 470.63.01

@doitsujin considering people are still reporting this is broken, and https://github.com/doitsujin/dxvk/pull/1963 made the major version check for the nvidia work around 465, shouldn't this just default to being back on for all Nvidia versions? As far as I know this bug was the reason the work around existed in the first place. It doesn't seem like Nvidia actually fixed it.

There's still a problem somewhere regarding high HVV use but I've never seen it crash since.

I'm currently testing 470.74 if I still manage to end up making the game crash (could take a month or more) but I've still never in at least a year of playing FFXIV had 440.100 crash, where does that ultimately put things? Is this just a rare bug that will never be fixed? Do you have any theories on this at all? I would've just escaped this by switching to an AMD card but with the whole market the way it is it hasn't been an option.
Do you have any thoughts on this at all? It's driving me nuts.

Interesting note on the 470.74 tho:

Fixed a regression which resulted in very-high system memory usage for Direct3D 12 games when run through vkd3d-proton.

Could be useful for DXVK too maybe? (Ie. high-memory related issue).
That said, nVidia hardware CAN sometimes be throwing those random XID errors when different manufacturers are pushing the limits on their "factory clocks" (Eg. Asus/MSI++ with their "OC" models and whatnot). Could be worth TRYING to underclock or powerlimit the gpu just to see.
You can check your powerlimit with nvidia-smi Then if it has like 215W (like my RTX2070 has), then you could try to use
sudo nvidia-smi -pl 200
Just mentioning this because i had a nVidia (260Ti card back when) that was really unstable - but it was one of those "OC Twin Frozr Whatever" cards, and ended up just downclocking it a tad, and issue went away :) Loads of factors playing in here - especially since XID(DEVICE LOST) errors MAY not be driver/dxvk related at all.

Could be useful for DXVK too maybe? (Ie. high-memory related issue).

No, the issue was specifically caused by the way vkd3d-proton uses Vulkan pipeline caches. DXVK does not trigger this problem in any way.

Honestly at this point I'll willing to concede this might just be a game bug. I've looked through the tracker and see other games that will crash with an in game bug but still have the DXVK log producing VK_ERROR_DEVICE_LOST. There are multiple numerous reports from Windows users on the FFXIV forums about DX11 crashes. I also play with my significant other who has had both the DX11 crash and sometimes a freeze while playing the game and they use Windows and AMD.
I think the biggest problem here is VK_ERROR_DEVICE_LOST is just too much of a generic error, is there anyway DXVK can give a better error code?
I think it's probably time to close this bug, I personally after all this time don't think this is a Nvidia or DXVK bug. Thoughts?

I don't think that the crashes on Windows are related to this. I have several friends using Nvidia cards (including RTX 3xxx) on Windows that afk all day in-game and never mentioned anything about the game crashing. And if this was actually a widespread issue there'd be a lot more noise about it with the current login queues. The people on windows having crashes more likely is borked installations, hardware or overclocks.
And even on Linux only newer Nvidia drivers are affected by it reproducibly, older ones and AMD cards run rock solid. Since switching to a 6900 XT I haven't had a single crash in the game. So from my point of view this still looks like a bug in Nvidias driver on Linux.
As far I know Nvidia devs also browse through these issues once in a while so keeping the issue open might make sense for the small chance of them looking into it one day, but more practically this would belong on the Nvidia forums or whatever they use for bug reports.

And if this was actually a widespread issue there'd be a lot more noise about it with the current login queues. The people on windows having crashes more likely is borked installations, hardware or overclocks.

There is an extensive thread over on the Final Fantasy Forums though: https://forum.square-enix.com/ffxiv/threads/448687-Directx11-error
User have the following hardware in that thread:
AMD Ryzen 6600XT
AMD Ryzen 7 5800X
AMD Ryzen 7 5800X 8-Core Processor
AMD Radeon RX 6600 XT
AMD Ryzen 5 3600 6-Core Processor
AMD Radeon RX 5700 XT
AMD Ryzen 5 3600 6-Core Processor
Radeon RX 580 Series
Intel(R) Core(TM) i7-8700 CPU
NVIDIA GeForce RTX 2070
AMD Ryzen 7 5700G with Radeon Graphics
NVIDIA GeForce GTX 1080
AMD Ryzen 5950x
AMD Radeon 6900x
As one user on the thread states:

Nothing has fixed this issue. Sometimes we can play all day with no problems, the next day the DirectX 11 11000002 error comes up over and over. If you lookup that error number, you'll see MILLIONS of posts online (not just on these forums) about this FF14 issue. This is not an obscure thing, A LOT OF PEOPLE have this problem.

And another user said it's been there since Stormblood:

A large part of the community have been waiting for an answer regarding this issue since Stormblood release, so I'm not sure if we are going to get one anytime soon if we didn't get one so far.

Apart from the VK_ERROR_DEVICE_LOST I also randomly get complete nvidia driver crashes with this game. I first thought my GPU is probably defect, but Xid 16 means “Display engine hung” and “Driver Error” according to nvidias own list and I do play other games, sometimes for hours and I have never seen such a crash outside of FFXIV.
This is with a NVIDIA GeForce GTX TITAN X card.
[11303.224211] NVRM: GPU at PCI:0000:01:00: GPU-0b4cda80-07b2-13fb-9c08-f03bf0381c28
[11303.224213] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1ef6
[11311.534091] NVRM: Xid (PCI:0000:01:00): 16, pid=16, Head 00000000 Count 000b1ef7
[11319.853967] NVRM: Xid (PCI:0000:01:00): 16, pid=6226, Head 00000000 Count 000b1ef8
[11328.183850] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1ef9
[11336.503749] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1efa
[11344.813634] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1efb
[11353.133512] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1efc
[11361.463408] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1efd
[11369.783297] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1efe
[11378.093175] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1eff
[11386.413068] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f00
[11394.732946] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f01
[11403.062837] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f02
[11411.372721] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f03
[11419.692602] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f04
[11428.022469] NVRM: Xid (PCI:0000:01:00): 16, pid=0, Head 00000000 Count 000b1f05
[11463.772567] nvidia-modeset: WARNING: GPU:0: Timeout while waiting for idle.
[11465.772637] nvidia-modeset: ERROR: GPU:0: Idling display engine timed out: 0x0000957d:0:0:428

Made a post on their forums, sent a bug report to the "support" address, never even got an answer back.
Also should mention that the driver crash is 100% not a DXVK bug, since it also happens with pure wine (only tested once, because the performance is horrible). I'm not sure if this is related at all to the original bug here, but I just wanted to add that information, in the hope it may help. If this confuses things more, please just disregard.

I first thought my GPU is probably defect, but Xid 16 means “Display engine hung” and “Driver Error” according to nvidias own list and I do play other games, sometimes for hours and I have never seen such a crash outside of FFXIV.

And that's the problem I play other games outside of FFXIV and they never crash either, we have a bunch of windows users reporting the same thing on different GPUs and if you take a look at other bug reports like this one https://github.com/doitsujin/dxvk/issues/2349 you'll see that bugs in games can definitely cause VK_ERROR_DEVICE_LOST and not just problems with Nvidia or DXVK.
As I said I've played this game a lot and so has my significant other I've watched their PC running Windows have all the same crashes I do on DXVK and Nvidia and they're using Windows and AMD.
I believe the bug is in the game itself for this reason, I also believe that depending on hardware/driver versions the bug can occur less or more frequently. I only wish I had the money to experiment with different GPUs and end this debate for once and all.

@konomikitten How is this behaving with the 515 drivers if you are still testing this from time to time.

@Blisto91 I switched from my GTX 960 to a RX 6600 about 4 months ago and I haven't had this crash since. My significant other switched from an RX 570 to a RX 6600XT and now gets this issue on Windows 10.
I still see frequent posts from Windows users on the Final Fantasy Forums about DirectX Error 11000002. As far as I am concerned this is a game bug that Square need to fix.

@konomikitten How is this behaving with the 515 drivers if you are still testing this from time to time.

No issues with 515.48.07 (as stable as 440.100)

@konomikitten How is this behaving with the 515 drivers if you are still testing this from time to time.

No issues with 515.48.07 (as stable as 440.100)

I no longer use a Nvidia Graphics card as per my previous post so I cannot answer that question.

I think they are stating that the 515 drivers are stable.


Dashboard

Overview

Add dashboard route
Add dashboard to navbar
Create dashboard view
Display all tasks in dashboard (both as creator and helper)
Add modal for each task
Add edit and delete buttons for creator tasks (logic works)
Add undo application button for helper tasks (logic works)

Notes

I wasn't able to add the carousel, we can do it later if you want.
I wasn't able to refactor the helper modal (if I create a partial for it, the undo button stops working).

 Tasks dashboard


All changes I found nessicary to build to ROS2 Jazzy.

Some headers changed their extension from .h to .hpp.

Also, the python file really intensely hated the \i escape sequence.  I added an additional backslash, but I'm not really sure what's going on with all that.

Thanks again for your contributions!


Links between to containers in different stack in Docker Swarm mode enabled

we are trying to create the swarm cluster with One Leader and Two workers.
it is done both nodes are up and running.
Requirement:
we try to create compose file(v3) with two images in it, when we run the docker stack deploy command it should deploy the containers with Links and communication between the container should happen via links.
Actual Result:
When we try to launch the two container via same compose file with swarm mode enabled it is not allowing us to launch two different containers as part of single Stack.
I tried one more thing like create two stack one for my web container and otheris db , but in that case also links are not working.
Need Solution:
In this cases i need to establish the communication between web container to DB container because of the link issue commication not happening.
Could you please check and let me if you any solution for that or any other work around.
Docker version: Latest
Docker Compose: Latest

Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

https://forums.docker.com
the Docker community Slack channel
StackOverflow

I'm going to close this issue because this is not a bug.
If you think there's a bug, provide the information that's requested in the issue template (https://raw.githubusercontent.com/docker/docker/master/.github/ISSUE_TEMPLATE.md) that was shown when you opened this issue; "latest version" is not sufficient to verify what you're running.
Also make sure to include the exact steps to reproduce, and, for example a docker-compose files to reproduce, and the commands you ran

Thanks for your guidance.


[Microsoft.DigitalTwins] Revert fixing typo after SDK review

Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
During the SDK review of 1.1.0, it was determined that the change fixing a typo in a function (decomissionModel) should be reverted, since it was deemed confusing to have both side by side.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-digital-twins-core


Ukrainian Localization Coordination

Hi! This thread is now closed because it lives here: microsoft/TypeScript-Website-Localizations#8

This issue is for keeping track of the localization effort for uk. You can learn about the whole roadmap in #100. If you see an un-ticked area below, that means there isn't an version of that file in this language.
For this language there are 774 translated files, with 832 TODO.
tsconfig
Done: 0, TODO: 120.

[ ] intro.md
[ ] Additional_Checks_6176.md
[ ] Advanced_Options_6178.md
[ ] Basic_Options_6172.md
[ ] Command_line_Options_6171.md
[ ] Experimental_Options_6177.md
[ ] Module_Resolution_Options_6174.md
[ ] Project_Files_0.md
[ ] Source_Map_Options_6175.md
[ ] Strict_Type_Checking_Options_6173.md
[ ] Watch_Options_999.md
[ ] allowJs.md
[ ] allowSyntheticDefaultImports.md
[ ] allowUmdGlobalAccess.md
[ ] allowUnreachableCode.md
[ ] allowUnusedLabels.md
[ ] alwaysStrict.md
[ ] assumeChangesOnlyAffectDirectDependencies.md
[ ] baseUrl.md
[ ] charset.md
[ ] checkJs.md
[ ] composite.md
[ ] declaration.md
[ ] declarationDir.md
[ ] declarationMap.md
[ ] diagnostics.md
[ ] disableReferencedProjectLoad.md
[ ] disableSizeLimit.md
[ ] disableSolutionSearching.md
[ ] disableSourceOfProjectReferenceRedirect.md
[ ] downlevelIteration.md
[ ] emitBOM.md
[ ] emitDeclarationOnly.md
[ ] emitDecoratorMetadata.md
[ ] esModuleInterop.md
[ ] exclude.md
[ ] experimentalDecorators.md
[ ] explainFiles.md
[ ] extendedDiagnostics.md
[ ] extends.md
[ ] fallbackPolling.md
[ ] files.md
[ ] forceConsistentCasingInFileNames.md
[ ] generateCpuProfile.md
[ ] importHelpers.md
[ ] importsNotUsedAsValues.md
[ ] include.md
[ ] incremental.md
[ ] inlineSourceMap.md
[ ] inlineSources.md
[ ] isolatedModules.md
[ ] jsx.md
[ ] jsxFactory.md
[ ] jsxFragmentFactory.md
[ ] jsxImportSource.md
[ ] keyofStringsOnly.md
[ ] lib.md
[ ] listEmittedFiles.md
[ ] listFiles.md
[ ] locale.md
[ ] mapRoot.md
[ ] maxNodeModuleJsDepth.md
[ ] module.md
[ ] moduleResolution.md
[ ] newLine.md
[ ] noEmit.md
[ ] noEmitHelpers.md
[ ] noEmitOnError.md
[ ] noErrorTruncation.md
[ ] noFallthroughCasesInSwitch.md
[ ] noImplicitAny.md
[ ] noImplicitReturns.md
[ ] noImplicitThis.md
[ ] noImplicitUseStrict.md
[ ] noLib.md
[ ] noPropertyAccessFromIndexSignature.md
[ ] noResolve.md
[ ] noStrictGenericChecks.md
[ ] noUncheckedIndexedAccess.md
[ ] noUnusedLocals.md
[ ] noUnusedParameters.md
[ ] out.md
[ ] outDir.md
[ ] outFile.md
[ ] paths.md
[ ] plugins.md
[ ] preserveConstEnums.md
[ ] preserveSymlinks.md
[ ] preserveWatchOutput.md
[ ] pretty.md
[ ] reactNamespace.md
[ ] references.md
[ ] removeComments.md
[ ] resolveJsonModule.md
[ ] rootDir.md
[ ] rootDirs.md
[ ] skipDefaultLibCheck.md
[ ] skipLibCheck.md
[ ] sourceMap.md
[ ] sourceRoot.md
[ ] strict.md
[ ] strictBindCallApply.md
[ ] strictFunctionTypes.md
[ ] strictNullChecks.md
[ ] strictPropertyInitialization.md
[ ] stripInternal.md
[ ] suppressExcessPropertyErrors.md
[ ] suppressImplicitAnyIndexErrors.md
[ ] target.md
[ ] traceResolution.md
[ ] tsBuildInfoFile.md
[ ] typeAcquisition.md
[ ] typeRoots.md
[ ] types.md
[ ] useDefineForClassFields.md
[ ] watchDirectory.md
[ ] watchFile.md
[ ] compilerOptions.md
[ ] top_level.md
[ ] watchOptions.md

playground
Done: 0, TODO: 74.

[ ] sections.json
[ ] Big number literals.ts
[ ] Const to let.ts
[ ] Infer From Usage Changes.ts
[ ] Flattened Error Reporting.ts
[ ] Nullish Coalescing.ts
[ ] Optional Chaining.ts
[ ] Assertion Functions.ts
[ ] Recursive Type References.ts
[ ] Uncalled Function Checks.ts
[ ] Checking Unions with Index Signatures.ts
[ ] Accessibility Modifiers.js
[ ] Export Modules From.ts
[ ] Private Class Fields.ts
[ ] Type Imports.tsx
[ ] Class Constructor Code Flow.ts
[ ] JSDoc Deprecated.ts
[ ] Logical Operators and Assignment.ts
[ ] Nullish Coalescing.ts
[ ] Named Tuples.ts
[ ] Unknown in Catch.ts
[ ] Variadic Tuples.ts
[ ] New JSX Support.ts
[ ] See in JSDoc.ts
[ ] Intro to Template Literals.ts
[ ] Mapped Types with Template Literals.ts
[ ] String Manipulation with Template Literals.ts
[ ] TypeScript with Deno.ts
[ ] TypeScript with Node.js
[ ] TypeScript with React.tsx
[ ] TypeScript with Web.js
[ ] TypeScript with WebGL.js
[ ] Function Chaining.ts
[ ] Generic Functions.ts
[ ] Typing Functions.ts
[ ] Errors.ts
[ ] Quick Fixes.ts
[ ] Code Flow.ts
[ ] Functions.ts
[ ] Hello World.ts
[ ] Objects and Arrays.ts
[ ] Async Await.ts
[ ] Immutability.ts
[ ] Import Export.ts
[ ] JSDoc Support.js
[ ] Classes 101.ts
[ ] Generic Classes.ts
[ ] Mixins.ts
[ ] This.ts
[ ] JavaScript Playgrounds.js
[ ] New Compiler Defaults.ts
[ ] Automatic Type Acquisition.ts
[ ] Fixits.ts
[ ] Mobile Support.ts
[ ] Sharable URLs.ts
[ ] TypeScript Versions.ts
[ ] Soundness.ts
[ ] Structural Typing.ts
[ ] Type Guards.ts
[ ] Type Widening and Narrowing.ts
[ ] Enums.ts
[ ] Nominal Typing.ts
[ ] Types vs Interfaces.ts
[ ] Conditional Types.ts
[ ] Discriminate Types.ts
[ ] Indexed Types.ts
[ ] Mapped Types.ts
[ ] Any.ts
[ ] Literals.ts
[ ] Union and Intersection Types.ts
[ ] Unknown and Never.ts
[ ] Built-in Utility Types.ts
[ ] Nullable Types.ts
[ ] Tuples.ts

app
Done: 0, TODO: 9.

[ ] community.ts
[ ] documentation.ts
[ ] dt.ts
[ ] handbook.ts
[ ] head-seo.ts
[ ] index.ts
[ ] nav.ts
[ ] playground.ts
[ ] tsconfig.ts

docs
Done: 0, TODO: 26.

[ ] Nightly Builds.md
[ ] Creating DTS files From JS.md
[ ] Intro to JS with TS.md
[ ] JSDoc Reference.md
[ ] Configuring Watch.md
[ ] Project References.md
[ ] tsconfig.json.md
[ ] Declaration Merging.md
[ ] Decorators.md
[ ] Iterators and Generators.md
[ ] JSX.md
[ ] Mixins.md
[ ] Module Resolution.md
[ ] Modules.md
[ ] Namespaces and Modules.md
[ ] Namespaces.md
[ ] Symbols.md
[ ] Triple-Slash Directives.md
[ ] Type Compatibility.md
[ ] Type Inference.md
[ ] Utility Types.md
[ ] Variable Declarations.md
[ ] Babel with TypeScript.md
[ ] DOM Manipulation.md
[ ] React.md
[ ] TypeScript Tooling in 5 minutes.md

In progress:
docs
tsconfig.json.md
Project References.md

Hey folks, I'm about to press the buttons moving localizations to a new repo, and so I'm closing this thread - this issue has a replacement over at https://github.com/microsoft/TypeScript-Website-Localizations/issues/8


CB-10636 Add JSHint for plugins

Jira issue
Fixed file.spec.115

Mostly LGTM apart from a few minor comments/


Allow prog diags to run if verification time range is non overlapping

If the verification time range doesn't overlap with the prognostic data, differencing the two datasets leads to a zero-length time dimension, which in turn leads to various errors in other functions that take in the bias data. The "DivisionByZero" error that pops up in the zonal mean bias is due to this issue. This PR adds some if/else statements in diagnostic functions that used to assume a nonzero time dimension.
Some of the repeated if/else checks could be avoided if the bias function used with xr.set_options(arithmetic_join="outer"). However, I think this would result in a lot of unnecessary reads of both the prognostic and verification data to just end up with a final diagnostic full of NaNs.
Coverage reports (updated automatically):

test_unit: 83%

maybe it would be cleaner to simply not call the bias and rmse functions if the verification is empty

I think right now there's no option for 'no verification'- if the flag isn't provided it defaults to the 40 day SHiELD verification data. Maybe the default should be changed to an empty verification.


[BUG] The bridge MTU is not changed

Describe the bug

To set the MTU to 9000, but the Harvester is defaulting to 1500.

To Reproduce
Steps to reproduce the behavior:

Create a cluster network and add a network config where the MTU of the uplink is set as 9000.
Create a VM network under this cluster network.
Create a VM using the VM network.
Check the related bridge. You will see the MTU of the bridge is still 1500 but the bond's is 9000.

Expected behavior

The bridge MTU should be the configured value.
Support bundle

Environment

Harvester ISO version:  v1.1.2
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal with Dell PowerEdge R630

Additional context
Add any other context about the problem here.

@yaocw2020 please help create a new enhancement issue to track the proposed design changes in v1.3.0(may consider backporting to v1.2.1)

@yaocw2020 please help create a new enhancement issue to track the proposed design changes in v1.3.0(may consider backporting to v1.2.1)

https://github.com/harvester/harvester/issues/4355

Workaround:
Case1: select the cluster network as the storage network.

stop all VMs since we need to update the storage network
save the storage-network settingkubectl get [settings.harvesterhci.io](http://settings.harvesterhci.io/) storage-network -oyaml > storage-setting.yaml

check its NAD name and save the related NAD to a yaml file. The NAD name is like storagenetwork-xxxxx.kubectl get network-attachment-definition -n harvester-system | grep storagenetwork
kubectl get network-attachment-definition -n harvester-system $nad -o yaml > storage-nad.yaml

disable storage network
a. wait for the longhorn-system's instannce-manager-e ,  instannce-manager-r and backing image pods to be ready after restart
b. wait for the pod on cattle-monitoring-system  to be ready
c. the MTU should be reset back to 9000 and you can check it on the host
modify the file storage-nad.yaml. Add the MTU to the spec.config and apply the file. The value will be like:'{"cniVersion":"0.3.1","type":"bridge","dns":{},"bridge":"test-br","mtu":9000,"promiscMode":true,"vlan":1,"ipam":{"type":"whereabouts","range":"<IP_ADDRESS>/24"}}

kubectl apply -f storage-nad.yaml

delete the fields metadata.creationTimestamp,metadata.generation,metadata.resourceVersion,metadata.uid and status in storage-setting.yaml. Then apply storage-setting.yaml.kubectl apply -f storage-setting.yaml

wait for the longhorn-system and cattle-monitoring-system pods are restarted successfully, and check the host MTU again by ip a| grep storage

Case2: The cluster network is only used for VMs

Stop all the VMs.
Modify all the VM networks under the cluster network to add MTU value in the spec.config filed.
Restart all the VMs.

Tested in v1.2.0-rc5, close as fixed.

Warning
Test do not cover 1.1.3 backport since not merge yet.
Ref. https://github.com/harvester/harvester/issues/4364

Environment

Harvester

Version: v1.2.0-rc5
Profile: QEMU/KVM, 3 nodes (8C/16G/250G)
ui-source: Auto

Test Cases

Note Click "►" to expand details.

Create a cluster network and network config uplink w/ customized MTU.
${~~~\color{green}\textsf{V}}$

Create a VM network (VLAN & Untagged) under this cluster network.
${~~~\color{green}\textsf{V}}$

VLAN 1 & Untagged

Create vm1/vm2 using the VLAN/Untagged network.
${~~~\color{green}\textsf{V}}$

vm1

vm2

Check the MTU of the bridge should be the customized value
${~~~\color{green}\textsf{V}}$

vm1

vm2


Use coordinate-aware routing

A* routing can take advantage of the x and z properties to compute shorter journies. Right now, the ERS optimizes for the fewest switches, which can occasionally be suboptimal.

901f0f454181b9f446bf156bd8ef44577b46fd2e


Fix the bug in VCSolver

Besides the unnecessary ok = false, there is another bug will harm the correctness in Mirror Reduction.
In mirror reduction, you need to check the conditions $w \in N^2(v)$ and $N(v) \setminus N(w)$ is a clique.
For each $u2 \in N(v) \setminus N(w)$, you should count its neighbor whose color is not w, i.e., $ps[w2] != w$, but not $ps[w2] == w$.

Thank you.
This improves the performance against several inputs.


Fix rounding errors for NUMA memory allocation

What this PR does / why we need it:
The NUMA mapping code did some miscalculations when it came to mapping memory to hugepages per node. Instead of just doing all calculations with bytes, the memory was converted to MiB. The conversion function had rounding issues which led to undividable MiB numbers.
For instance setting a memory of 2780Gi led to this calculation:
requested memory can't be divided through the numa page size: 2846719 mod 1024 != 0

The issue is that 2780Gi should be 2846710 and not 2846719. This PR fixes the conversion function QuantityToMebiByte but in addition just stops doing the conversion at all and instead does all calculations directly with bytes where no in accuracy can occur  at all. The bandwidth setting for migrations requires MiB/s, therefore the function QuantityToMebiByte will still be used for the migration parameter.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:
NONE

/cc @davidvossel
/cc @jean-edouard

/retest

/approve
Just one suggestion, I think big numbers are hard to read, so I would replace occurrences of:

1048576 by 1024*1024
2846720 by 2780*1024
2985002270720 by 2780*1024*1024*1024
Assuming the go compiler can do math of course

Just one suggestion, I think big numbers are hard to read, so I would replace occurrences of:

good suggestion. Will do that.

@jean-edouard done.

/retest

Just one suggestion, I think big numbers are hard to read, so I would replace occurrences of:

Done. Made a push mistake yesterday. Now the changes are really there.

/cherrypick release-0.43


[Backport 1.x] Add Service Monitor Resource

Description
It would add a prometheus serviceMonitor resource.
Check List

[x] Commits are signed per the DCO using --signoff

For any changes to files within Helm chart directories:

[x] Helm chart version bumped
[x] Helm chart CHANGELOG.md updated to reflect change

PR sponsored by Obmondo

Thanks @VILJkid should we wait until this fix is pushed https://github.com/opensearch-project/helm-charts/issues/579#issuecomment-2306751619 ?
@getsaurabh02 @peterzhuamazon

Thanks for the update, @prudhvigodithi!
I'll keep an eye on that, and update this PR accordingly.

Pending fix:

https://github.com/opensearch-project/helm-charts/pull/581

Pending fix:
* [[Fix] OpenSearch and OpenSearch Dashboards Service Monitor Bug #581](https://github.com/opensearch-project/helm-charts/pull/581)

Since this is merged now would you mind update this PR to include above changes?
Thanks @VILJkid !

Thanks @peterzhuamazon, I'll update this PR with the changes shortly.

@peterzhuamazon, kindly review the changes and let me know if it needs any improvement.
Thanks!

Thanks @VILJkid , adding @prudhvigodithi to take a second pass.

Waiting for @prudhvigodithi to give a second approval.
Thanks.

There is a new bug created https://github.com/opensearch-project/helm-charts/issues/588, @VILJkid can you please take a look before we merge this?
Thank you

Thanks @prudhvigodithi, @peterzhuamazon for highlighting the issue.
Here's the fix PR: https://github.com/opensearch-project/helm-charts/pull/589
Let me know if it needs any improvements.

Thanks @prudhvigodithi, @peterzhuamazon for highlighting the issue. Here's the fix PR: #589 Let me know if it needs any improvements.

Thanks @VILJkid I have merged that PR now.
Please go ahead and backport the changes here as well.
Thanks!


Latest version of app doesn't seem to be available for everyone

Description
As per the 6.0.0 update 'Victory for Local Control' (congratulations by the way), we've regained access.
However (and I realise it's only 14th December) version '3.8.103' is not available, even for beta testers in every country.
As you have some communications with TP-Link, could you possibly ask them very nicely to update it for Europe?
Reproduction Steps
Install in Europe? (Android)
Expected behavior
Version '3.8.103'
If applicable, add error logs.
No response
Device Firmware
1.3.14
Integration Version
?
Using stream component
No
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Proxmox
Search for similar issues
Yes
Additional information
No response

Thank you!
Personally I expect a staged rollout. It should come out soon in next few days or a week or two, if not, I will consider reaching out.
Alternative is using iOS device (temporarily) to switch the setting if you cannot wait.
Please continue discussion at https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/discussions/752 .

Okay so Version 3.8.103 seems to be iOS: https://apps.apple.com/us/app/tp-link-tapo/id1472718009

Thank you! Personally I expect a staged rollout. It should come out soon in next few days or a week or two, if not, I will consider reaching out.
Alternative is using iOS device (temporarily) to switch the setting if you cannot wait.
Please continue discussion at #752 .

Will do!


Reset does not rotate image to original position

Hi, the lib is great, but I found some issue - for me If I pressed reset, I will want to rotate image original position.
For fix I suggest next code to add to 'reset' function before calling "this.renderCanvas();":
"     his.image.rotate = 0;
this.rotated = true;"
It fixed this problem.

Thank you, works like a charm! I was missing this feature in v0.9 too. You have a little typo in your code, here is the corrected version:
this.image.rotate = 0;
this.rotated = true;

It's my fault. Thank you very much!


Make it possible to upgrade cert-manager resources to v1 and old API versions from CRDs with cmctl

Is your feature request related to a problem? Please describe.
In cert-manager 1.6 all legacy API versions were removed. Users have to ensure that all cert-manager resources are stored in etcd at v1 and that all cert-manager CRDs only have v1 marked as the stored version. Doing this involves some manual steps - see here. It would be nice if this could be done with cmctl instead.
Additionally, it might also be nice if this command could update api versions on owner references of CertificateRequests to ensure that any CRs created for legacy versions of Certificates get garbage collected correctly.
/kind feature

/assign @munnerz
(cf. slack discussion)

Still requires some updates to the documentation explaining when to run cmctl upgrade migrate-api-version


EXTRAFLAGS appears in AFLAGS three times

I only checked sim. but others might have similar issues.
when you do "make EXTRAFLAGS=foobar",
foobar appears in eg. AFLAGS three times.
it's a problem because some options are not idempotent.
eg. the following example was with EXTRAFLAGS="-fsanitize=address -mllvm -asan-stack=0 "
AS:  sim/up_setjmp64.S
/usr/local/Cellar/llvm/10.0.1/bin/clang -c -Wall -Wstrict-prototypes -Wshadow -Wundef -g -fstack-protector-all -fno-builtin -fno-common -isystem "/Users/yamamoto/git/nuttx/nuttx/include"  -D__KERNEL__ -fsanitize=address -mllvm -asan-stack=0  -pipe -I "/Users/yamamoto/git/nuttx/nuttx/arch/sim/src" -I "/Users/yamamoto/git/nuttx/nuttx/arch/sim/src/chip" -I "/Users/yamamoto/git/nuttx/nuttx/sched" -D__KERNEL__ -fsanitize=address -mllvm -asan-stack=0  -D__ASSEMBLY__ -I "/Users/yamamoto/git/nuttx/nuttx/arch/sim/src" -I "/Users/yamamoto/git/nuttx/nuttx/arch/sim/src/chip" -I "/Users/yamamoto/git/nuttx/nuttx/sched" -D__KERNEL__ -fsanitize=address -mllvm -asan-stack=0   sim/up_setjmp64.S  -o  up_setjmp64.o
clang (LLVM option parsing): for the --asan-stack option: may only occur zero or one times!
clang (LLVM option parsing): for the --asan-stack option: may only occur zero or one times!

@yamt I think I solved this in https://github.com/apache/incubator-nuttx/pull/1776
can you verify this removes your case of repeated flags in AFLAGS? The fix should apply to all *FLAGS.


Content methods

Added canBeShown method and restore content job and api ednpoint

Coverage increased (+1.3%) to 60.802% when pulling ae053eb00e60c70babb0cba47a206a513944ed5a on content_methods into 97842f939bd02d521b5aff9c8f6da098244f0e06 on master.

Coverage increased (+3.1%) to 62.654% when pulling b0d812d52bb8cd31f1b3d68e4a48cd776b5c74da on content_methods into 97842f939bd02d521b5aff9c8f6da098244f0e06 on master.


Rename LoadedZipline to LoadAttempt and emit on failure

[CLOSES #693]

[x] Update to LoadResult name instead
[x] Use Sealed classes and pass back exception

Going to land this as is and then address channelFlow and #724 in a follow up PR


python311Packages.knx-frontend: 2<IP_ADDRESS>839 -> 2<IP_ADDRESS>712

Changelog: https://github.com/XKNX/knx-frontend/releases/tag/2<IP_ADDRESS>712
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 239789 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.knx
python310Packages.knx-frontend
python310Packages.knx-frontend.dist
python311Packages.knx-frontend
python311Packages.knx-frontend.dist


Pass dap-server-path as a list

It seems that passing just a plain string fails in make-process with Emacs 28.

Thanks! merging :)


[Wallet] Add TransactionReview screen for CELO rewards

Description
Adds a "content" on the TransactionReview screen for the CELO rewards transfers. If the transaction comes from an address we know is used for CELO rewards, we show this content instead of the standard transaction one.

The "Learn More" button opens a WebView with a yet not implemented webpage.
Other changes

The UserSection can be non-expandable now and doesn't render the phone number text if there is no phone number (it was rendered empty before).

Tested
Yes
Related issues

Fixes #6136

Backwards compatibility
N/A

Updated designs with slight copy changes

Updated designs with slight copy changes

Updated to follow the changes to the UI and the copy changes

Updated to follow the changes to the UI and the copy changes

Hi @gnardini We are block to get the rewards &  not able to buy the cUSD because user should redirect to add funds page by tapping on buy cUSD button on simplex page
However. we are using mainnet for valora here user redirecting to simplex page for buying cUSD So, we are blocked to buy the cUSD
Can you please do the needful that how we can buy the cUSD.
Thanks!

Hi @gnardini We are block to get the rewards &  not able to buy the cUSD because user should redirect to add funds page by tapping on buy cUSD button on simplex page
However. we are using mainnet for valora here user redirecting to simplex page for buying cUSD So, we are blocked to buy the cUSD
Can you please do the needful that how we can buy the cUSD.
Thanks!

Hi @gnardini We are block to get the rewards & not able to buy the cUSD because user should redirect to add funds page by tapping on Add cUSD button on simplex page.
Can you please help us how to Add cUSD.
Thanks!

Hi @gnardini We are block to get the rewards & not able to buy the cUSD because user should redirect to add funds page by tapping on Add cUSD button on simplex page.
Can you please help us how to Add cUSD.
Thanks!


Detailed description
A sitemap is a file that lists all the pages of a website, helping search engines understand its structure and content.
Context
It enhances search engine optimization (SEO) efforts by improving website visibility and indexing. I believe adding sitemap would be a perfect addition to this project.
Possible implementation
No response
Additional information
No response
Checklist

[X] I have read the Contributing Guidelines
[X] I have checked the existing issues
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@Anmol-Baranwal  Can you assign me this issue.

@Killer2OP
I have assigned you the issue. Please proceed with it, and don't hesitate to tag me if you require any assistance.


Hono Client infer types

What version of Hono are you using?
4.4.9
What runtime/platform is your app running on?
Nodejs
What steps can reproduce the bug?
Create a pnpm mono repo, make a simple api with hono and a react project with vite
What is the expected behavior?
I expect to be able to import AppType and have it typed on react project as shown in the docs
What do you see instead?
everything is typed incorrect like:
) type AppRoutes = OpenAPIHono<HonoEnv, {
    [x: `/api/workflows/${string}`]: {
        [x: `$${Lowercase<string>}`]: {
            input: Partial<ValidationTargets>;
            output: any;
            outputFormat: string;
            status: StatusCode;
        };
    };
} & {
    ...;
}, "/api">

Additional information
if I create a hc instance in the hono index.ts file it is typed correct, but when I import the AppType to react client it does not, I have strict: true in both react/hono project, it is weird because in the backend the interface is perfect.
type AppRoutes = OpenAPIHono<HonoEnv, {
    "/api/workflows/version/:versionId/step/:stepId": {
        $patch: {
            input: {
                param: {
                    versionId: string;
                    stepId: string;
                };
            } & {
                json: {
                    status?: "Failure" | "Pending" | "Success" | undefined;
                    definition?: Record<...> | ... 1 more ... | undefined;
                    actionId?: string | undefined;
                    stepOrder?: number | undefined;
                };
            };
            output: {
                ...;
            };
            outputFormat: "json";
            status: 422;
        } | {
            ...;
        };
    };
    ... 4 more ...;
    "/api/workflows": {
        ...;
    };
} & {
    ...;
}, "/api">

Hi @leognmotta
This may be caused by the fact that they may not be able to refer to the same hono package. We can investigate if you share a minimal project to reproduce it. This may be related to https://github.com/honojs/hono/issues/2955

This is a known TS limitation, in a monorepo, if you use alias in your backend package, you must use TS Project Reference, i.e: enable composite in the package where you exports hono and add reference in the package that you consume it.

This is a known TS limitation, in a monorepo, if you use TS alias, you must use TS Project Reference, i.e: enable composite in the package where you exports hono and add reference in the package that you consume it.

Thanks for letting me know, I was not aware of this, so I believe we may close this issue since it is not related to hono

This is a known TS limitation, in a monorepo, if you use TS alias, you must use TS Project Reference, i.e: enable composite in the package where you exports hono and add reference in the package that you consume it.

Due, your comment saved me couple of days figuring out why types are not working in my repo. MANY THANKS