[bug][react-native] crash since 3.34.7+ - No QueryClient set, use QueryClientProvider to set one

Describe the bug
I was running react-query with 3.34.5 for a couple of weeks and everything worked flawlessly on React Native.
Since 3.34.7, my app is crashing with following error:
Error: No QueryClient set, use QueryClientProvider to set one

Furthermore, I get this type error now:
Type 'import("/myapp/node_modules/react-query/types/core/queryClient").QueryClient' is not assignable to type 'import("/myapp/packages/expo/node_modules/react-query/types/core/queryClient").QueryClient'.
  Types have separate declarations of a private property 'queryCache'.ts(2322)
QueryClientProvider.d.ts(10, 5): The expected type comes from property 'client' which is declared here on type 'IntrinsicAttributes & QueryClientProviderProps & { children?: ReactNode; }

My QueryClientProvider is looking like this:
    <DripsyProvider theme={colorMode === 'dark' ? theme : themeLight}>
      <QueryClientProvider client={RNQueryClient}>
        <SafeAreaProvider initialMetrics={initialWindowMetrics}>
          <GestureHandlerRootView style={{ flex: 1 }}>
            <Navigator theme={combinedTheme} />
            <Toast />
          </GestureHandlerRootView>
        </SafeAreaProvider>
      </QueryClientProvider>
    </DripsyProvider>

Your Example Website or App

Steps to reproduce
I am importing my client like so:
and the content of my service file is
import { QueryClient } from 'react-query';
// Create a client
export const RNQueryClient = new QueryClient();

import { QueryClientProvider } from 'react-query';
import { RNQueryClient } from 'app/services/react-query/query-client';

My QueryClientProvider is looking like this:
    <DripsyProvider theme={colorMode === 'dark' ? theme : themeLight}>
      <QueryClientProvider client={RNQueryClient}>
        <SafeAreaProvider initialMetrics={initialWindowMetrics}>
          <GestureHandlerRootView style={{ flex: 1 }}>
            <Navigator theme={combinedTheme} />
            <Toast />
          </GestureHandlerRootView>
        </SafeAreaProvider>
      </QueryClientProvider>
    </DripsyProvider>

Expected behavior
Should not crash.
No issues if I downgrade to 3.34.5.
How often does this bug happen?
Every time
Screenshots or Videos

Platform

OS: iOS 15.2
Browser: React Native
Version: 0.64.3

Additional context
The error triggers, as soon as this function calls:
  return useQuery(['UserDetails'], async () => {
    const response: AxiosResponse = await staffRequestService.getCharacters();
    return response.data;
  });

The only change in 3.34.6 was something stylistic in the devtools, so it's unlikely that this caused it: https://github.com/tannerlinsley/react-query/compare/v3.34.5...v3.34.6
please show all involved components, especially GetUserDetails, or even better, provide a reproduction (e.g. in https://snack.expo.dev/)

The only change in 3.34.6 was something stylistic in the devtools, so it's unlikely that this caused it: https://github.com/tannerlinsley/react-query/compare/v3.34.5...v3.34.6
please show all involved components, especially GetUserDetails, or even better, provide a reproduction (e.g. in https://snack.expo.dev/)

This is my user.ts
import { useQuery } from 'react-query';
import { AxiosResponse } from 'axios';
import { ApiService } from 'app/services/ApiService';
// import { useStore } from 'app/store';

/**
 *
 * @returns Deals with my request details api
 * Caching handled by react query
 */
export const GetUserDetails = () => {
  const staffRequestService = ApiService.createInstance();
  // const userId = useStore(state => state.userId);

  return useQuery(['UserDetails'], async () => {
    const response: AxiosResponse = await staffRequestService.getCharacters();
    return response.data;
  });
};

Which is being called in my Home Component (this first route opened by react-navigation).
And this is my Home Component
import React from 'react';
import { View, FlatList, RefreshControl } from 'react-native';
import { useStore } from 'app/store';

import styles from './styles';
import { GetUserDetails } from 'app/services/react-query/queries/user';
const Home: React.FC = () => {
  const setIsLoggedIn = useStore((state) => state.setIsLoggedIn);
  const { isLoading, isFetching, data = { results: [] } } = GetUserDetails();

  const onLogOut = () => {
    setIsLoggedIn(false);
  };

  const renderItem = ({ item }) => <View />;

  return (
    <View style={styles.container}>
      <FlatList
        data={data.results}
        renderItem={renderItem}
        keyExtractor={(item) => item.id}
        refreshControl={
          <RefreshControl
            refreshing={isLoading || isFetching}
            onRefresh={() => {}}
          />
        }
      />
    </View>
  );
};

export default Home;

This is my user.ts
import { useQuery } from 'react-query';
import { AxiosResponse } from 'axios';
import { ApiService } from 'app/services/ApiService';
// import { useStore } from 'app/store';

/**
 *
 * @returns Deals with my request details api
 * Caching handled by react query
 */
export const GetUserDetails = () => {
  const staffRequestService = ApiService.createInstance();
  // const userId = useStore(state => state.userId);

  return useQuery(['UserDetails'], async () => {
    const response: AxiosResponse = await staffRequestService.getCharacters();
    return response.data;
  });
};

Which is being called in my Home Component (this first route opened by react-navigation).
And this is my Home Component
import React from 'react';
import { View, FlatList, RefreshControl } from 'react-native';
import { useStore } from 'app/store';

import styles from './styles';
import { GetUserDetails } from 'app/services/react-query/queries/user';
const Home: React.FC = () => {
  const setIsLoggedIn = useStore((state) => state.setIsLoggedIn);
  const { isLoading, isFetching, data = { results: [] } } = GetUserDetails();

  const onLogOut = () => {
    setIsLoggedIn(false);
  };

  const renderItem = ({ item }) => <View />;

  return (
    <View style={styles.container}>
      <FlatList
        data={data.results}
        renderItem={renderItem}
        keyExtractor={(item) => item.id}
        refreshControl={
          <RefreshControl
            refreshing={isLoading || isFetching}
            onRefresh={() => {}}
          />
        }
      />
    </View>
  );
};

export default Home;

https://github.com/tannerlinsley/react-query/compare/v3.34.5...v3.34.7

https://github.com/tannerlinsley/react-query/compare/v3.34.5...v3.34.7

Could also be related: https://github.com/tannerlinsley/react-query/issues/3069
Sounds exactly like my issue, but he closed it without further notice unfortunately.

Could also be related: https://github.com/tannerlinsley/react-query/issues/3069
Sounds exactly like my issue, but he closed it without further notice unfortunately.

Are you sure that Home is inside a QueryClientProvider? You haven't shown that as far as I can see

Are you sure that Home is inside a QueryClientProvider? You haven't shown that as far as I can see

@TkDodo yes, it is a import and component of Navigator

@TkDodo yes, it is a import and component of Navigator

const { isLoading, isFetching, data = { results: [] } } = GetUserDetails();

this seems invalid. Either make it a custom hook, or render GetUserDetails as a react component.

const { isLoading, isFetching, data = { results: [] } } = GetUserDetails();

this seems invalid. Either make it a custom hook, or render GetUserDetails as a react component.

@TkDodo I found the issue. I am using a Yarn Workspace (monorepo) and Lerna. react-query was updated in packages/expo but not packages/app (usally you should only install in one workspace but the only way to get autocomplete working was to install it in every package [I've double confirmed this with vscode devs] and this was the error.
The type error is gone and also the crash is gone. Not sure what was happening internally...

@TkDodo I found the issue. I am using a Yarn Workspace (monorepo) and Lerna. react-query was updated in packages/expo but not packages/app (usally you should only install in one workspace but the only way to get autocomplete working was to install it in every package [I've double confirmed this with vscode devs] and this was the error.
The type error is gone and also the crash is gone. Not sure what was happening internally...


Internal release for Auth API

This release should provide enough functionality for usage with carto.js.

Internal communication.

Tomorrow I plan to review the Redis output generated by the Backend (issue)

I've just reviewed the generated Redis keys #13474, and it LGTM!

I'll put this issue back in TODO, we can consider it done once we have:

Windshaft in production (after fallback is done https://github.com/CartoDB/Windshaft-cartodb/issues/867)
Public/Master keys installed for team members


Roc corrupts own memory

roc --version
roc nightly pre-release, built from commit faaa466 on Fr 16 Dez 2022 09:07:40 UTC

uname -a
Linux vali 6.0.8-arch1-1 #1 SMP PREEMPT_DYNAMIC Thu, 10 Nov 2022 21:14:24 +0000 x86_64 GNU/Linux

Reproduce with the files in the attached zip, by running:
roc dev -- sample.txt

roc-mem-corruption.zip
The output I see is the following:
[main.roc 82:9] ["AA", "0", "tunnels", "lead", "to", "valves", "DD", "II", "BB"]
[main.roc 92:9] 0
[main.roc 95:9] ["DD", "II", "BB"]
[main.roc 82:9] ["BB", "13", "tunnels", "lead", "to", "valves", "CC", "AA"]
[main.roc 92:9] 13
[main.roc 95:9] ["CC", "AA"]
[main.roc 82:9] ["CC", "2", "tunnels", "lead", "to", "valves", "DD", "BB"]
[main.roc 92:9] 2
[main.roc 95:9] ["DD", "BB"]
[main.roc 82:9] ["DD", "20", "tunnels", "lead", "to", "valves", "CC", "AA", "EE"]
[main.roc 92:9] 20
[main.roc 95:9] ["CC", "AA", "EE"]
[main.roc 82:9] ["EE", "3", "tunnels", "lead", "to", "valves", "FF", "DD"]
[main.roc 92:9] 3
[main.roc 95:9] ["FF", "DD"]
[main.roc 82:9] ["FF", "0", "tunnels", "lead", "to", "valves", "EE", "GG"]
[main.roc 92:9] 0
[main.roc 95:9] ["EE", "GG"]
[main.roc 82:9] ["GG", "0", "tunnels", "lead", "to", "valves", "FF", "HH"]
[main.roc 92:9] 0
[main.roc 95:9] ["FF", "HH"]
[main.roc 82:9] ["HH", "22", "tunnel", "leads", "to", "valve", "GG"]
[main.roc 92:9] 22
[main.roc 95:9] ["GG"]
[main.roc 82:9] ["II", "0", "tunnels", "lead", "to", "valves", "AA", "JJ"]
[main.roc 92:9] 0
[main.roc 95:9] ["AA", "JJ"]
[main.roc 82:9] ["JJ", "21", "tunnel", "leads", "to", "valve", "II"]
[main.roc 92:9] 21
[main.roc 95:9] ["II"]
[main.roc 22:9] [{ flow:<PHONE_NUMBER>1894189799, id: "AA", links: ["�>", "II", "BB"] }, { flow: 13, id: "BB", links: ["�>", "AA"] }, { flow: 2, id: "CC", links: ["�>", "BB"] }, { flow: 20, id: "DD", links: ["�>", "AA", "EE"] }, { flow: 3, id: "EE", links: ["�>", "DD"] }, { flow: 0, id: "FF", links: ["�>", "GG"] }, { flow: 0, id: "GG", links: ["�>", "HH"] }, { flow: 22, id: "HH", links: ["�>"] }, { flow: 0, id: "II", links: ["�>", "JJ"] }, { flow: 21, id: "JJ", links: ["�>"] }]
AA:<PHONE_NUMBER>1894189799 -> �>, II, BB
BB: 13 -> �>, AA
CC: 2 -> �>, BB
DD: 20 -> �>, AA, EE
EE: 3 -> �>, DD
FF: 0 -> �>, GG
GG: 0 -> �>, HH
HH: 22 -> �>
II: 0 -> �>, JJ
JJ: 21 -> �>
found 10 valves

The initial dbg lines demonstrate that Roc has read, and maintains, the correct data in memory. However, the dbg in the main function demonstrates that the parsed data has been corrupted:

The first flow value should be 0, but is<PHONE_NUMBER>1894189799.
The first element of every links list has been replaced by some arbitrary string content (apparently of the same byte length), and has a different appearance every program run.

The output from the valvesToStr function demonstrates that this isn't an issue with dbg, and that Roc is, probably, reusing memory that it mistakenly identified as free.

with #4796, I think this should run correctly when you remove the dbgs. I'll tackle the dbg problem next.


Do not overwrite the tokens.csv file when re-rendering credentials

Closes #810.

Codecov Report

Merging #867 into master will increase coverage by 0.03%.
The diff coverage is 81.48%.

@@            Coverage Diff             @@
##           master     #867      +/-   ##
==========================================
+ Coverage   34.61%   34.65%   +0.03%
==========================================
  Files          57       57
  Lines        3909     3919      +10
==========================================
+ Hits         1353     1358       +5
- Misses       2398     2401       +3
- Partials      158      160       +2

Impacted Files
Coverage Δ

core/controlplane/config/encrypted_assets.go
69.66% <81.48%> (-0.49%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update adf172e...a42cdde. Read the comment docs.

/lgtm
Thanks for the improvement 👍

Why tokens.csv is special? Re-rendering ca.pem is even more dangerous, as it causes etcd rotation when replaced nodes are not trusted by not yet replaced ones causing all sorts of trouble.

The tokens.csv file is not special in that sense. The issue was that kube-aws render credentials was truncating this file, so any information put there by the user was inadvertently lost, causing tokens previously specified there to be "revoked" in case the user updates the cluster afterwards.

Also, kube-aws render credentials do not replace the CA unless you specify --generate-ca, so running it and then running kube-aws update will not (supposedly) mess a running cluster.


Enhancement: orgDefaults

Apologies if there is a way to do this & I'm missing how, but is there a way to enforce orgDefault's similar to spaceDefaults?
Here's a rough outline of my layout:
spaceDefaults.yml
orgs.yml
cf-mgmt.yml
config
├── asgs
│   └── default_security_group.json
├── cf-mgmt.yml
├── ORG_1
│   ├── dev..
│   ├── orgConfig.yml
│   ├── spaces.yml
│   └── test..
├── ldap.yml
├── orgs.yml
├── spaceDefaults.yml
├── ORG_2
│   ├── dev..
│   ├── orgConfig.yml
│   ├── spaces.yml
│   └── test..
└── ORG_3
    ├── dev..
    ├── orgConfig.yml
    ├── spaces.yml
    └── test..

I'd like to be able to set default org quotas & org managers. Is that something which can currently be done / been concerned as a feature enhancement?

There currently is not a way to set defaults for orgs like we have for spaces.  We have been discussing if how it is done for spaces makes sense or if we should be more explicit about how we manage config for these.  Almost like an inheritance model where a space can say it inherits it's config from a space template and then anything it provides is an override of that template.  Interested to hear ideas on how we can simplify this.  We have also do somethings to move security groups to named security groups and plan to do the same with quotas to remove the duplication in the space/org configs.


CLWP Emulators only predicts values equal to zero

For the emulators trained to predict CLWP (cloud liquid water path), no matter what set of values they are given for the features, they always predict meanResponses of zero. They also seem to predict a constant value for the standard deviation of the response. This can be seen here:

Some testing has been done to observe if this problem is related to the kernel selected for training. So far Matern and RBF have been tested and both seem to display the same problem.

@vasanchez16 ,
I updated some routines to fully implement the capability of centering and normalizing the target data.  I applied these changes, created a new technique and trained on clwp.  However, the results indicate something is still off, as all variants give the same result:

@vasanchez16 ,
After investigating some more,  I decided to try the Matern kernel again, but change the nu parameter to 1.5 (or maybe 2.5).  All previous training has been done using Matern with nu=0.5.  According to the
Matern kernel doc
nu=0.5 is equivalent to RBF.
My initial testing indicated that nu=1.5 was helping.  Running the full training job now, the technique id is 'TECH-J'
Here is an example prediction:

@dadamsncsa ,
I tested this process manually by isolating the features and target for just one gstp, and in doing so I found that playing the arguments for GaussianProcessRegressor and the Matern kernel help sometimes but not consistently. Specifically, the 'n_restarts_optimizer' for the 'GaussianProcessRegressor' and the 'length_scale_bounds' for the Matern Kernel. I didn't tweak the nu value so hopefully this fixes the problem. Thanks for the updates

@vasanchez16 ,
Okay, I think that the nu setting is definitely an issue.   The default is 1.5 and we had been using 0.5 which is the same as RBF.  The TECH-J technique is also using the centering and normalization options, not sure if they are really needed, but probably can't hurt.  The training job is done so feel free to try out predictions.  Let me know how it looks...
tech_clwp = model_clwp.createTrainingTechnique(
    kernelName = 'Matern',
    #change kernel name this may be the issue
    serializedKernel = c3.PythonSerialization.serialize(sklKernel_clwp),
    targetName='clwp',
    centerTarget=True,
    standardizeTarget=True
)

@dadamsncsa,
It appears this change has fixed the problem, thanks darren! I will think of some ways to test the performance and accuracy of these emulators.

Issue resolved. As a note for the future, the initial length scale values given to the optimizer through the training technique are very important to building proper models.
CLWP initial length scales: [0.1]*12
AOD initial length scales: [1]*12


Move default tokens to another repo ?

However, i see many and many PR regarding implementing new default tokens in MeW. It even leads to some childish fights about the currency names sometimes.
MeW is a great tool but PR list should be mainly focused onto its own development and not onto implementing new ERC20 tokens, moreover that we'll see more and more new tokens as time passes.
In order to keep things clean, wouldn't moving the current default tokens file to a different repo from which people will be able to propose new tokens without affecting the PR pile of the main repo ?
Also, at some point, listing hundreds of tokens overloads the main website. A solution that could be explored could be to build a tool that allow each user to build its own token list configuration from a website hosted on subdomain ( or another domain ) and then have a tool to allow import from user on MeW website.
Any critics welcome, obviously ( mainly from main devs of the repo ).
Much datalove

Totally agreeing with this suggestion, especially that MEW doesn't load token balances by default anymore. Token creators may simply give instructions to users on how to add new tokens.

Tokens will be moved to external repo upon migration to v4
https://github.com/myetherwallet/ethereum-lists

You can see the new MEW v4 of tokens here: MyEtherWallet/MyEtherWallet#538
And provide any feedback here: MyEtherWallet/MyEtherWallet#494

Great news ! Thanks for the info, i had alreaddy digged into the v4 code but haven't been checking there how it was going to be handled. Sorry for the inconvenience !
I'll close the issue.


Arh Linux 安装记录 - Hexo

https://yuzhi535.github.io/2021/06/30/Arh-Linux-安装记录/
We will meet in a place where there is no darkness.

尝试一下评论功能


disabling dask cli tests

[ ] I have added the tests to cover my changes.
[ ] I have updated the documentation and CHANGELOG accordingly.
[ ] I have read the CONTRIBUTING document.

Bug report for these tests: https://github.com/AgnostiqHQ/covalent/issues/846


About the 2D segmentor

Hi, thanks for your nice work!
I'm interested in the 2D segmentor that you used in CAMA. The paper mentions that you use Mask2Former to get road and lane segmentation masks. May I ask which specific model & results are ued in CAMA (Mapillary Vistas Model and Semantic Segmentation results? or the Panoptic Segmentation results?)
Looking forward to your reply!

Thanks for the interets, Mask2Former trained on Mapillary is good, no need for panoptic segmentation.


Move InputValidator to Utils

This PR has two

Moving InputValidation implementation to Utils namespace so that other services can make use of it
Initialize & add validators for JSONRPC. TextToSpeechImplementation.cpp & TextToSpeechJsonRpc.cpp belong to different processes and dont share the same InputValidation::Instance(). The previous implementation adds validators only in TextToSpeechImplementation, leaving any validations from JsonRPC ineffective

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/4731/rdkcentral/rdkservices

Commit: 68e5bb8dc8f1ba630348b962e0570d8c8b533c77

Report detail: gist

Hi Vivek: There isn't a Blackduck problem here but please will you put a header on the new file (RDK Apache).  I will clear off the check if it fails again.


resources/Rethinking_2/Chp_05.ipynb

5.13 (In [23])

the observation variable is 'Marriage_std', so its name should have been 'Marriage_std' instead of 'divorce_std'.
below is the code 5.13.

with pm.Model() as m_5_4:
    a = pm.Normal("a", 0, 0.2)
    bAM = pm.Normal("bAM", 0, 0.5)
    sigma = pm.Exponential("sigma", 1)

    mu = pm.Deterministic("mu", a + bAM * data["MedianAgeMarriage_std"])

    marriage_std = pm.Normal(
        "divorce_std", mu=mu, sigma=sigma, observed=data["Marriage_std"].values
    )
    prior_samples = pm.sample_prior_predictive()
    m_5_4_trace = pm.sample()

5.15 (In [25])

this cell is about posterior predictive check for the observation variable 'divorce_rate_std' whose model number is m_5_3 (as indicated m5.3 in the book)
so, 5_4 in the whole cell should be replaced by 5_3
and 'divorce_std' must be replaced by 'divorce_rate_std' as defined in model m_5_3
below is 5.15

# We can skip most of the code with the posterior predictive plot functionality in pymc3
with m_5_4:
    m_5_4_ppc = pm.sample_posterior_predictive(
        m_5_4_trace, var_names=["mu", "divorce_std"], samples=1000
    )

mu_mean = m_5_4_ppc["mu"].mean(axis=0)
mu_hpd = az.hpd(m_5_4_ppc["mu"], credible_interval=0.89)

D_sim = m_5_4_ppc["divorce_std"].mean(axis=0)
D_PI = az.hpd(m_5_4_ppc["divorce_std"], credible_interval=0.89)

Hope I am making a correct suggestion.
Many thanks for sharing the wonderful pymc3 codes for the book

Thanks for reporting this @yongduek ! Do you feel like doing a PR to fix it?


Fixing download_data.py file after it stopped working

This pull request addresses the issue with the download_data.py file, which had stopped functioning properly. The fix involves resolving bugs and implementing improvements to ensure seamless data downloads. The changes made in this pull request aim to restore the functionality of the script, providing a reliable solution for users to download data without interruptions.

Sorry I think issue was related to some network setting


hyprland/window: rename .hidden to .swallowing (and fix grouped windows)

Sorry, I know I submitted #2307 just half an hour ago, but I changed my mind. Rather than renaming .hidden to some other class name, I have renamed it to .swallowing. After some more discussion in the comments to https://github.com/Alexays/Waybar/commit/cdece498c1e3849ea6e8ff7795ddce1ca8265803#commitcomment-121410267 I realized that instead of excluding so many edge cases for it, it's easier to check specifically for window swallowing, as that's the only use case that makes sense and is not covered by other means.

Don't worry, thx!


Fix arg position typo in docs for terragrunt debug mode

Addresses https://github.com/gruntwork-io/terragrunt/issues/1281

Thanks for review! Merging this in now.


Allow to disable a specific command

Is your feature request related to a problem? Please describe.
I am building a platform that allows persons to write maths, but I would like to disable some commands such as \color or \textcolor.
Describe the solution you'd like:
I would like an option similar to trust.

You can use the existing macro infrastructure to blank out the definitions of \color and \textcolor, e.g., via macros: {color: '', textcolor: ''}.  (It won't eat the arguments, but it will prevent colors from working.)  Is that sufficient?

Okay, thanks! It is quite nice, and it would be sufficient for me for the moment, but I would prefer showing the command in red like as it is the case for untrusted commands.
Anyway, thank you for all your work!!

This would look similar:
macros: {
  color: '\\textcolor{#cc0000}{\\text{\\textbackslash color}}',
  texcolor: '\\textcolor{#cc0000}{\\text{\\textbackslash textcolor}}',
}

This is a bit complicated, though.  We could certainly make this easier with a macro that defines how to format trust violations (which would be nice to make more configurable anyway? or is that a security hole?), and then you could call that more easily.

If there could be something like allow(context) { ... } as there is for trust trust(context) { ... }, it would be great!

Would it be complicated to implement what I suggest? If it is okay, I could do a PR.

@edemaine The solution you gave me with
macros: {
  color: '\\textcolor{#cc0000}{\\text{\\textbackslash color}}',
  texcolor: '\\textcolor{#cc0000}{\\text{\\textbackslash textcolor}}',
}

is not working.
If you try this code with the latest version of KaTeX:
console.log(
  katex.renderToString('\\color{blue} x^2', {
    output: 'html',
    macros: {
      color: '\\textcolor{#cc0000}{\\text{\\textbackslash color}}',
    },
  })
);

You will get this:
x2

Hence, the text is still blue. It seems like macros cannot be overloaded.

I found how to make it working. It should be:
macros: {
  '\\color': '\\textcolor{#cc0000}{\\text{\\textbackslash color}}',
  '\\textcolor': '\\textcolor{#cc0000}{\\text{\\textbackslash textcolor}}',
}

The macro's name should start with \\.

Oops, sorry about the typo. I also realize that these macros will lead to infinite macro expansion because of the recursive use of \textcolor. So simulating the red color won't be so easy.

Indeed, I get this error. But it is okay for me for the moment


Make wording in overview more in line with the description

The description talks about the server one way and the overview text talks about it a bit differently.
This change aligns them and make them easier to understand in my opinion.

Submitted CLA

Hello @bradtopol and @chenopis. Wondering if there was anything I could do to get this small change merged.
Thanks!


Cannot install via npx - npm ERR! cb.apply is not a function

This project looks promising and I'd love to add our business to the partners, but sadly I cannot get it installed through the instructions.
node -v
v15.12.0

npm -v
7.6.0

npx -v
10.2.2

Cloned the repo
npx @statusfy/cli init
Returns...

npm ERR! cb.apply is not a function

npm ERR! A complete log of this run can be found in:
npm ERR!     /logpath/log.log
Install for [ '@statusfy/cli@latest' ] failed with code 1

[x] I confirm that this is a issue rather than a question.

Bug report
cat /etc/os-release
...
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian

Version
Latest as of 3/25/2021
Steps to reproduce
See above
What is expected?
Error message regarding cb.apply
What is actually happening?
Errors out, log file attached
2021-03-25T18_45_06_781Z-debug.log
Other relevant information

Your OS: Debian
Node.js version: 15.12.2
Browser version: Chromium 89
Is this a global or local install? global
Which package manager did you use for the install? apt / npm

same issue can't run the npx command cb.apply not a function im running node 14...
on synology nas


autograd-gamma 0.6.0

Changelog: https://github.com/CamDavidsonPilon/autograd-gamma/releases
License: https://github.com/CamDavidsonPilon/autograd-gamma/blob/master/LICENSE
Requirements: https://github.com/CamDavidsonPilon/autograd-gamma/blob/master/setup.py
Actions:

Apply an initial percy patch and run locally a script to:

Remove noarch python
Skip py<37
Add flags --no-deps --no-build-isolation to script
Add missing setuptools and wheel to host
Fix python in host and run

Notes:

lifelines requires it https://github.com/conda-forge/lifelines-feedstock/blob/532bab4fccd8407f9e4e4010ab6733951ef254e8/recipe/meta.yaml#L36

Before merging I'll remove https://github.com/AnacondaRecipes/autograd-gamma-feedstock/blob/479ce10226eecd797e14c3ce16af1ffa36c68a6e/abs.yaml

forgot to add all other changes to meta.yaml ?

forgot to add all other changes to meta.yaml ?

Ah, no. I've mistakenly pushed changes to the main branch before creating a new branch autograd-gamma-_0.6.0 and opening the PR :(


Initial implementation of serial stream

Initial PR for streams serial port implementation

Hi ChrisEAlfred, I changed the import sequence, so module is only required, if it is mentioned in config.yml.
And my smartmeter talks "hex", so I added a encoding value. If it is set, the serial read data is encoded for proper sending via mqtt.
May you test, if it is still working for your project?
Thank you

Just wanted to say that this is a really nice idea, and thanks for submitting the PR, @ChrisEAlfred ! I'll hang on until you've tested out the changes made by @BenjiU before merging.

I have tested @BenjiU changes and all is fine by me.
I commented out the debug messages as they can be verbose.

Hey, I changed the printfs to _LOG system traces, because I like traces, that can be switched on by the user without touching source code :-)
@flyte: may be merged, if you don't see anything.

Cool, thanks guys! I'll add it to the growing list of things to test out before the next release!


Switch mvICA  to dependency

Move Multiview ICA to being a pip dependency (https://github.com/hugorichard/multiviewica) w/ wrapper function.

This might be restrictive for the conda installation, since multiviewica isn't available on conda-forge

The code for mvica is still in a very early stage, and will very likely change. I think we will ultimately move the code to this repository.


Add skip_plq_interface_oper_status_check deviation in PLQ test for Arista

This PR sets the existing skip_plq_interface_oper_status_check deviation to true for Arista for the packet link qualification test.

Pull Request Functional Test Report for #2429 / 6d71019b9127dac93e1b203ceeb0f19e4839eb4b
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

gNOI-2.1: Packet-based Link Qualification

Cisco 8000E

gNOI-2.1: Packet-based Link Qualification

Cisco XRd

gNOI-2.1: Packet-based Link Qualification

Juniper cPTX

gNOI-2.1: Packet-based Link Qualification

Juniper ncPTX

gNOI-2.1: Packet-based Link Qualification

Nokia SR Linux

gNOI-2.1: Packet-based Link Qualification

Openconfig Lemming

gNOI-2.1: Packet-based Link Qualification

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

gNOI-2.1: Packet-based Link Qualification

Cisco 8808

gNOI-2.1: Packet-based Link Qualification

Juniper PTX10008

gNOI-2.1: Packet-based Link Qualification

Nokia 7250 IXR-10e

gNOI-2.1: Packet-based Link Qualification

Help


🌱Uplift IPAM release-1.2 tag v1.2.2

Uplift IPAM

/test-ubuntu-integration-release-1-2
/cc @kashifest
/cc @tuminoid

/test-ubuntu-integration-release-1-2

/lgtm

/test-ubuntu-integration-release-1-2

/approve


investigate datadog golang integration for metrics

We are using Datadog for some of the Docker Hub metrics and monitoring (along with systems metrics and monitoring). It may be useful to incorporate their Golang integration for gathering statistics about Go memory usage or exposing other variables that are not accessible by parsing logfile output. Contact me for more info.

@avinson Base Go metrics (expvar), as well as others, are already exposed on a separate http server. They also expose notification statistics, which we'll need to monitor. We are also adding a health-check system.


Add maximum and minimum quality values to config

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Currently you can add a ratio for preferred qualities, but it would be good if you could add either a ratio for min and max, or declare absolute values for these.
I would be fine with ratios applying to all my quality profiles but this may not work for others.
The preferred quality setting is almost pointless if you use custom formats because it seems to not do anything useful since it's the last thing Radarr/Sonarr uses to weight choices. If you're using custom formats these will take precedence over any preferred quality settings.
Setting a maximum setting would make it act in a more useful way. I set all my minimums to match trash guides but I manually bring down my maximums so I don't grab wildly oversized releases.

I am likely not going to make this change. It's simple enough right now to just not sync quality definitions with Recyclarr and instead manage the settings yourself directly in Radarr/Sonarr. Furthermore, the number of people that want to do this is very very small so it will be difficult to prioritize it.


KNOWN: Finish line counts backwards crossing as finished lap

Describe the bug
In any race mode, crossing the finish line is counted as a "lap", regardless of whether you actually completed a lap or not.
To Reproduce
Steps to reproduce the behavior:

Enter any race mode
Cross the finish line moving forward to start the race
Reverse across the finish line
Cross the finish line again
Observe lap count

Expected behavior
The finish line should only count full laps.
Screenshots
(none needed)
Desktop (please complete the following information):

OS:

[x] PC
[x] Android

Program Version
Using TiltFive?

[x] Yes
[ ] No

Input Method:

[x] Keyboard
[x] Gamepad
[x] Android touchscreen
[x] TiltFive wand

Additional context
(none)

This behavior is unlikely to be fixed in this "teaching version" of the game. Without leaderboards or multiplayer, this behavior isn't really an "exploit" so much as "something the player could do if they felt like it".


Adds proof harnesses for aws_byte_cursor_from_* functions

Description of changes:

Updates implementation of aws_byte_cursor_from_* functions with pre- and post-conditions;
Adds proof harnesses for aws_byte_cursor_from_* functions;

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR depends on the #360

@justinboswell @JonathanHenson @ColdenCullen @graebm could you review the changes in byte_buf.h and byte_buf.c?


Exact Status of "Configure role-based access control with Data Access Policy" preview or GA?

Hi,
The documentation doesn't contain the usual preview warning altought it still handle the fact that the portal indicates that advanced data access configuration if prefixed with (PREVIEW).
Hence the need for clarification: is the feature in preview or GA?
Cédric

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

ID: b9fcf066-1623-8219-cf57-2f125c148f59
Version Independent ID: d988024f-3672-09c1-c061-25f231a09925
Content: Configure role-based access control with Data Access Policy - Azure Cache for Redis
Content Source: articles/azure-cache-for-redis/cache-configure-role-based-access-control.md
Service: cache
GitHub Login: @flang-msft
Microsoft Alias: franlanglois

Hi @cblomart ,
Thanks for sharing this feedback.
We will look into this and update as appropriate.
Hi @flang-msft,
Could you please look into this, thanks.

Hi @flang-msft,
Do you think this can be clarified? When doc doesn't mention preview and the portal still has (PREVIEW) prefix, i tend to think about a pending or missed update on the portal but would very much be sure of the status.
Cédric

@flang-msft any news?

@cblomart - Thanks for your input. I will clarify more broadly that this feature is in preview because it intersects with using Microsoft Entra ID, which is currently in preview. Once Micrsoft Entra ID is generally available the preview tag will be removed.

We just published some clarifications about Microsoft Entra ID in the documentation and have a few more updates in our backlog.  I'll now proceed to close this issue. If you have further information or would like to continue the discussion, please tag me and or reopen the issue. Thank you!
#please-close


Fix debugging in VSCode

Debugging does not seem to work in VSCode.  If I set a breakpoint in a function and then run a test that know will execute that line, the debugger does not stop in that function, but simply runs to completion.
Breakpoints DO work inside the test code, just not in the functions called for rules.

Fixed with Spectral V6


Update index.rst

Fix two broken links.
Couldn't find link to repo in the docs => went to check the source, found the sciPy link at the top didn't render.
Similarly, the link to commercial license lead to http://honnibal.github.io/spaCy/license.rst which is a 404.

Thanks!


Fails to package native images from Docker

Version(s)
Please provide the version(s) of Scala CLI that is affected by this bug
1.0.0-RC1
Describe the bug
An attempt to package the application fails (this feature).
To Reproduce
Given hello world test.scala:
@main def hello: Unit = println("Hello, World!")

The regular packaging works well (scala-cli --power package test.scala --native-image -o dist/native).
Unfortunately, this command fails:
docker run -v $(pwd)/test.scala:/test.scala virtuslab/scala-cli package --native-image /test.scala

I get an error as follows:
Compiling project (Scala 3.2.0, JVM)
Compiled project (Scala 3.2.0, JVM)
Error: java.lang.Exception: coursier.jvm.JvmCache$JvmNotFoundInIndex: JVM graalvm-java17:22.2.0 not found in index: JVM graalvm-java17 not found
For more details, please see '/.scala-build/stacktraces/1683201456-7466099423917604350.log'

It's still the same issue as in earlier closed ticket: https://github.com/VirtusLab/scala-cli/issues/1580.
I see the commit and test (https://github.com/VirtusLab/scala-cli/pull/1961/files), but unfortunately something goes wrong in reality.
The container also doesn't support the dep directive and requires using lib. Seems to be outdated.
Maybe some fixes were not published?
Would you please have a look.
Expected behaviour
It should allow packaging native images from Docker as stated in Release Notes.

Please also find additional error details here https://github.com/VirtusLab/scala-cli/issues/1580#issuecomment-1531886287

It looks like the latest image is not published.
This works:
docker run -v $(pwd)/test.scala:/test.scala virtuslab/scala-cli:1.0.0-RC1 --power package --native-image /test.scala

Note that there is a bug in documentation (at least in Release Notes). The lack of --power .

🤦  OMG I did pull wrong. So it works. The only problem left is the lack of --power in docs.
You haven't seen that ticket. Closing it now! 🤣


Enabled TLS between identity and keycloak

With #127 we added Identity to the charts. Per default TLS is not enabled for the authentication (communication between keycloak and identity).
We should investigate how we could enable the TLS setting. It seems that we either need to bring a certificate or keycloak can create a self-signed cert.
https://github.com/bitnami/charts/blob/master/bitnami/keycloak/values.yaml#L144-L203

I'm closing this issue since it's out of the scope of the default setup and we found that many users use a Service Mesh to fix handle that out of the Helm config.


Add light mode

I noticed that none of the built-in color palettes work well with my light mode terminal (I use solarized light). It would be nice to add in at least one light mode palette!

Not a problem. I can add a light solarized theme. Since you are asking I will let you tell me what number you want it associated with. Also, you may already know this but you can define any color scheme you want in a config.

Not a problem. I can add a light solarized theme. Since you are asking I will let you tell me what number you want it associated with.

Thanks! Maybe it can be (6)solarized_light, assuming that the current highest number is (5)uncolor.

Also, you may already know this but you can define any color scheme you want in a config.

I had tried to define a Solarized Light color scheme based on the palette shown on Wikipedia:
meta_color = [108, 113, 193]
header_color = [88, 110, 117]
std_color = [131, 148, 150]
na_color = [220, 50, 47]
neg_num_color = [42, 161, 152]

I threw these into $HOME/Library/Application\ Support/tv.toml but that didn't seem to work for me. (Note that I didn't rebuild tv so perhaps that was the issue?)

I will add those colors to ship with tv!

I used your colors with a solarized theme. How does this look.

Thanks for the update. It looks great to me!


Saving the buffer twice…

I have an issue that started to happen after #12, most of the time I need to save the buffer twice. The first will run the formatter as expected but then because it updates the buffer with the new formatted content, the buffer becomes modified again & I have to save it again to be saved with the formatted content.
I'm still trying to debug & see if that has anything to do with my setup (very unlikely because I didn't change much after I modified my config to match the changes in #12)
This is my formatter config.

How are you triggering the formatting on save?

Looking at your config, you're using just Format
https://github.com/ahmedelgabri/dotfiles/blob/0e99abf5422a5e2521e9c54c99f9bd7c7befb691/roles/vim/files/.vim/plugin/autocmnds.vim#L38
Should be able to swap out Format with FormatWrite

I didn't know that FormatWrite existed…, thanks


Duplicate text-summary or text coverage report

Describe the bug
When running vitest with coverage reporting using either text or text-summary reporter, the reported coverage is duplicated in the terminal.
><EMAIL_ADDRESS>test /home/mkman/dev/my-app
> vitest run --coverage

 RUN  v0.31.1 /home/mkman/dev/my-app
      Coverage enabled with c8

 ✓ src/app.test.ts (1)

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  18:55:31
   Duration  656ms (transform 38ms, setup 0ms, collect 8ms, tests 2ms, environment 0ms, prepare 99ms)

 % Coverage report from c8

=============================== Coverage summary ===============================
Statements   : 0% ( 0/42 )
Branches     : 100% ( 0/0 )
Functions    : 0% ( 0/2 )
Lines        : 0% ( 0/42 )
================================================================================
-----------|---------|----------|---------|---------|-------------------
File       | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-----------|---------|----------|---------|---------|-------------------
All files  |       0 |      100 |       0 |       0 |
 App.tsx   |       0 |      100 |       0 |       0 | 1-27
 index.tsx |       0 |      100 |       0 |       0 | 1-15
-----------|---------|----------|---------|---------|-------------------

=============================== Coverage summary ===============================
Statements   : 0% ( 0/42 )
Branches     : 100% ( 0/0 )
Functions    : 0% ( 0/2 )
Lines        : 0% ( 0/42 )
================================================================================
-----------|---------|----------|---------|---------|-------------------
File       | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-----------|---------|----------|---------|---------|-------------------
All files  |       0 |      100 |       0 |       0 |
 App.tsx   |       0 |      100 |       0 |       0 | 1-27
 index.tsx |       0 |      100 |       0 |       0 | 1-15
-----------|---------|----------|---------|---------|-------------------

Reproduction
Run the test script in this repo
System Info
System:
    OS: Linux 5.19 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (12) x64 AMD Ryzen 5 5600U with Radeon Graphics
    Memory: 9.12 GB / 13.51 GB
    Container: Yes
    Shell: 3.6.1 - /usr/bin/fish
  Binaries:
    Node: 18.13.0 - /run/user/1000/fnm_multishells/15846_1684918295743/bin/node
    npm: 8.19.3 - /run/user/1000/fnm_multishells/15846_1684918295743/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 113.0.5672.126
  npmPackages:
    @vitest/coverage-c8: ^0.31.1 => 0.31.1
    vite: ^4.1.1 => 4.1.1

### Used Package Manager

pnpm

### Validations

- [X] Follow our [Code of Conduct](https://github.com/vitest-dev/vitest/blob/main/CODE_OF_CONDUCT.md)
- [X] Read the [Contributing Guidelines](https://github.com/vitest-dev/vitest/blob/main/CONTRIBUTING.md).
- [X] Read the [docs](https://vitest.dev/guide/).
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vitest/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vitest/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

When the vite-plugin-solid is removed, coverage results are not duplicated.
export default defineConfig({
-  plugins: [solidPlugin()],

The vite-plugin-solid seems to duplicate config.test. Removing this line from the plugin resolves the issue. https://github.com/solidjs/vite-plugin-solid/blob/66955a81de1e6b84e02271e4f8603500b45656cb/src/index.ts#L328

Thanks for looking into this and writing a fix so quickly @AriPerkkio 🙏

I can confirm the same thing! And as @AriPerkkio alluded to, it is not just duplicating the report itself but it is actually running all the unit tests twice! The way to test is to add beforeEach() and/or afterEach() to a few tests and add a console log and you will see they duplicate all the tests themselves.
See here where I show my initial example/issue: https://github.com/solidjs/vite-plugin-solid/issues/112#issuecomment-1698476208

Fixed by https://github.com/solidjs/vite-plugin-solid/pull/101. Please wait for Solid to publish new release and test whether it fixes the issue.


DCOS-49352 - Add metrics for Zones

JIRA - https://jira.mesosphere.com/browse/DCOS-49352

I know about this issue @urbanserj, I should have mentioned that. I am testing by building dashboards on grafana.

By those two graphs, one can see that there are zones where we can see the size but there is no duration metrics.
I opened this PR with the help wanted label because of my issue with the tests. I looked at your lashup PR, and at other places but I was unable to find any instance where we had to deal with Prometheus and the ETS tables in the test. Do you have any suggestions there? Do you think it is related to my issue of missing push duration?

I know instrumented all calls to the push_prepared_zone.

@urbanserj, @ichernetsky could you give another pass?

I fixed (I guess) both style error @urbanserj

@Fabs LGTM, could you please squash all the commits?


Pylint

Untitled9.ipynb
Hy @sharmistharanit
You have mentioned 'Untitled9.ipynb' this file in your pylint. Is this the file with real code ? I am just curious whether it is the real code file of our work or not?

Can you link the file you’re talking about, I cannot find it

Sure I can attach the file from google collab. @laserlab

I have already attached the file separately. The file name is Workdone_Pylint. @poojashresthacode @laserlab
Is that ok?

I have attached the file in the documentation. Is it ok now @poojashresthacode
Can you please check and let me know?

Can you link the file you’re talking about, I cannot find it

Prof. we have sorted out the problem. You can go through the link : https://github.com/ubsuny/23-Homework3G4/blob/main/final_original_code_with_pylint.ipynb

Can you link the file you’re talking about, I cannot find it

Prof. we have sorted out the problem. You can go through the link : https://github.com/ubsuny/23-Homework3G4/blob/main/final_original_code_with_pylint.ipynb

I still see no Untitled9 in that file

workdone_pylint
I am talking about this file. Actually, I think that unknowingly our team member @sharmistharanit who did the documentation part while running the pylint test, she forgot to rename the file to workdone_pylint
And it came with the default Untitled9.ipynb. @laserlab

You can check out it in the above-mentioned link on the pylint test.


Incorrect azure functions quickstart url

There are Incorrect url on azure functions quickstart index page
Create your first function (C#) links to Quickstart: Create your first function in Azure using Visual Studio.
Also others are link to Quickstart: Create a C# function in Azure using Visual Studio Code irrespective of language
These look like to should fix each link-url create-first-function-vs-code-{language}
ScreenShot

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

ID: 6e88ea08-81ef-2b5a-b9d6-539e85592672
Version Independent ID: f2d8b7b4-906a-d1f5-5201-fc22a7890955
Content: Quickstart: Create your first function in Azure using Visual Studio
Content Source: articles/azure-functions/functions-create-your-first-function-visual-studio.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@roharon Thanks for your question. We are checking on this and will respond to you soon.

Hello @roharon, Thank you for pointing out the issue and fixing it as well. The fix proposed was merged and is live now. We really appreciate the help provided. Thank you!


home-assistant: 2021.12.4 -> 2021.12.5

Motivation for this change
https://github.com/home-assistant/core/releases/tag/2021.12.5
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

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

1 package failed to build:

home-assistant

8 packages built:

python38Packages.aiohue
python38Packages.aiopvpc
python38Packages.pytile
python38Packages.xknx
python39Packages.aiohue
python39Packages.aiopvpc
python39Packages.pytile
python39Packages.xknx

homeassistant/components/august/manifest.json
5:  "requirements": ["yalexs==1.1.13"],

❯ nix-instantiate --eval --strict --attr python3Packages.yalexs.version
"1.1.15"

1971949910733daabb431c78bbde3e6b0408a50d

The yalexs bump shouldn't have been part of #151329.

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

9 packages built:

home-assistant
python38Packages.aiohue
python38Packages.aiopvpc
python38Packages.pytile
python38Packages.xknx
python39Packages.aiohue
python39Packages.aiopvpc
python39Packages.pytile
python39Packages.xknx


find node in tree with a given value

fixes #7
traverse the tree and compare the value of the node with the value we're searching, going left or right. if it matches, then we've found the node and we return it.
tests
setup:
//index.mjs
import createTree from "./createTree.mjs";

const testArray = [1, 7, 4, 23, 8, 9, 4, 3, 5, 7, 9, 67, 6345, 324];
const tree = createTree(testArray);

tree.buildTree();
tree.prettyPrint();

console.log(`
FINDING...
`);
tree.find(-6969); // expected: not found
tree.find(67); // expected: node object with .data=67

output 1: searching for -6969

output 2: searching for 67

i will keep the console.log statements for demonstration purposes


1257 add last four pages of flow

Context
Last PR to add the candidate satisfaction survey.
Previous PRs #1806, #1811 and #1820
This adds the free text questions, asks if we can contact them and thanks them.
Changes proposed in this pull request

Adds page asking them how they would improve the service

Adds page that asks if they want to say anything else

Adds page that asks if we can contact them

Adds page that thanks them for filling the survey in

Guidance to review
Have a click through the whole flow. Try the backlinks etc.
Link to Trello card
https://trello.com/c/tO5B8iK1/1257-dev-survey-to-candidates-when-they-have-submitted-an-application
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Seems that the pages here are quite similar - what would you view be on creating a component and passing in arguments the for where the forms differ? (link paths, min max args, label vals etc.)
I think its good as it is though - just a thought 👍


ArtifactCollection.getArtifacts() doesn't respect artifact's capabilities

In AGP, we are implementing testFixtures for android libraries. Since we depend on the artifact's variant, attributes and capabilities, it's important that the information is correct for both the plugin and Android Studio.
In ResolvedArtifactCollectingVisitor, the artifacts are identified by ResolvableArtifact.getId(), so in case of ComponentFileArtifactIdentifier the artifact is identified by the componentId and fileName which could be the same for artifacts in the same module (the same ProjectComponentIdentifier) and producing the same fileName (but the path is different).
The problem exists only for artifacts with different capabilities as a node in the dependency graph has to have all the artifacts attributes matching, but they could have different capabilites, and so it's important to use the capability when identifying the artifact.
A fix could be to add the capabilities in addition to the artifact id as the key that is used in the seenArtifacts set.

It appears that the issue only occurs for ArtifactTransform outputs, here is a project that reproduces the issue by running ./gradlew :app:printArtifacts.
Expected behaviour is that there will be two artifacts, one with the testFixtures capability, which is the behaviour when not applying the artifact transform (setting it.attribute(transformed, false) in the task). But instead there will be only one artifact.

Hey @AmrAfifiy,
Sorry it took so long to properly look into this issue and the proposed pull request.
Unfortunately, the proposed fix creates another issue.
By adding variant selection information into the artifact identifier, we end up duplicating artifacts in cases where different artifact variant selections are at play but they end up resolving the same file.
This can be seen by running the test DependencySubstitutionRulesIntegrationTest#can substitute a classified dependency with a non classified version for the iteration that uses the withoutClassifier.
With your changes, we end up selecting twice the same lib-1.1.jar file.
I believe the proper solution is to:

Include the full path into determining if the artifacts are the same or not
Enhance ResolvedArtifactResult to have a getVariants() method that returns all the variants that ended up selecting the artifact. It also means that getVariant() should be deprecated and documented as returning only the first variant.

Would you be willing to try this approach?
Making it in time for 7.6 is unlikely, so I have moved this issue tentatively to 8.0, but I cannot commit the Gradle team to fixing it in time at this point.

I believe the root cause is the same as for #17213

Side note: Here are the PRs mentioned in the previous comment: https://github.com/gradle/gradle/pull/18788, https://github.com/gradle/gradle/pull/22048 ("Add the variant identity to the seenArtifacts key").


systemd version not documented?

Description
It'd be helpful to know at a glance what systemd version is present, so I can know what all is supported without having to run a task. Filing it as a bug since systemd is clearly present and just not documented.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[X] Ubuntu 18.04
[X] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
N/A - it's a docs bug
Is it regression?
No
Expected behavior
Docs list the systemd version.
Actual behavior
No systemd version is listed.
Repro steps
N/A

Hello @dead-claudia . Thanks for your report, we will investigate this.

It was added to the readme and will be a part of readme starting next week.


Is it possible to implement sprite looping animation?

const guideLine = Matter.Bodies.rectangle(
      render.options.width / 2,
      render.options.height / 2,
      5,
      render.options.height / 2,
      {
        name: 'guideLine',
        isStatic: true,
        isSensor: true,
        collisionFilter: { group: -1 },
        render: {
          sprite: {
            texture: dotted[0].image,
            xScale: game_wrap.clientWidth / 450,
            yScale: game_wrap.clientHeight / 1226
          }
        }
      }
    )

I made a guideLine object which is a dotted line image, i want to make the sprite animate like a infinite swiper.
Is it possible?

Please see matter.js: is there any way to animate my sprite on Stack Overflow.


[FLOC-3111] Remove used_ports from NodeState, since it is not used and creates extra traffic

This looks good but creates some dead-code in flocker.network. Please remove that and address the other point and the resubmit.

Reviewed 11 of 11 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

flocker/control/_model.py, line 880 [r1] (raw file):
:question: This attribute is a no-op now. I'm not sure if it should be removed now, but if it isn't, then possibly the related test should stick around.

flocker/control/test/test_model.py, line 392 [r1] (raw file):
:question: If _APPLICATION_ATTRIBUTES is sticking around, then perhaps this test should stick around as well, even if it is trivial.

flocker/node/_deploy.py, line 781 [r1] (raw file):
:exclamation: Since this is the only caller, all the related code should also be removed now.

flocker/node/test/test_loop.py, line 373 [r1] (raw file):
:exclamation: This should probably get a non-trivial application.

Comments from the review on Reviewable.io

This looks good. One minor comment, then merge once buildbot is happy.

Reviewed 8 of 8 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

flocker/control/_model.py, line 885 [r2] (raw file):
:exclamation: Either get rid of the loop or use the loop variable.

Comments from the review on Reviewable.io


How to use immer to update Input fields ?

🙋♂ Question
How to use immer to update Input fields ? in other words is code example 1 is same as code example 2 ? I really appreciate any help here.
ex:
1)
<Input type="text" name="address1" id="garageaddress1" placeholder="Garaged Address Line 1"
value={this.state.person.address1}
onChange={e => produce(this.state, s => { s.person.address1 = e.target.value })}/>

handleChange(e) {
const target = e.target;
const value = target.value;
const name = target.name;
    this.setState({
        person: {
            [name]: value
        }

    })

}
Link to repro
Please provide a CodeSandbox demo to clarify your question if possible.
Environment
We only accept questions against the latest Immer version.

Immer version:
[ ] Occurs with setUseProxies(true)
[ ] Occurs with setUseProxies(false) (ES5 only)

Please provide a reproduction in a code sandbox or at least format the message properly. The question is unclear in its current form.


Make all services optional

What
Make all services optional
Why
To make it possible to run lighter weight versions of quickstart with just what you need, such as just with soroban-rpc.

Tests failing appear to be related to Horizon starting up, for pubnet specifically, so I'm guessing this is a scale issue. Investigating...

TODO:

[ ] Fix the test so it passes through the value to start specifics services or not

But, in local mode a core mode is needed. I hope it’s not optional then.

Only request would be to remember to update the README. Might be good to do a full pass over it to ensure it's all still accurate and covers all the flags and meaningful cases

remember to update the README

Thanks, great call. I just pushed some updates to the readme for adding the new command and removing comments that no longer made sense.

@stellar/ops-team @mollykarcher The one functional difference for existing users, is that as part of this change the RPC becomes on by default. It can be turned off by specifying that only core and horizon run with --enable core,horizon, but folks using it won't discover that in any meaningful or obvious way, unless they're looking at the logs and see that the RPC starts up. I don't think we have a great way to address that. The image is primarily intended for dev and testing, and for dev and testing having RPC on by default makes sense. Please let me know if you have any concerns.

@leighmcculloch ack. The only downside to having soroban-rpc started by default I can think of isextra resource usage. But I think it shouldn't be a big problem.

I think that's fine. We can actively advise those we know of that are using it for production use of this change as well.
cc @aditya1702


Not able to add a Front Load Washer

HA core version
2024.10.4
Current integration version
0.6.5
Last known working integration version
0.6.5
Device type and model
Front Load Washer<PHONE_NUMBER>05063
Working mobile app
SmartHome
The detail description of bug/problem

description the device type and name（you may have multiple devices）

Error when adding new device. Front Load Whasher
150633093905063
The logs
2024-10-30 15:16:25.883 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] user input login matched
2024-10-30 15:16:26.587 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Using account<EMAIL_ADDRESS>login to SmartHome cloud pass
2024-10-30 15:16:28.883 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 1 token/key failed
2024-10-30 15:16:29.043 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 2 token/key failed
2024-10-30 15:16:29.044 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Unable to connect device with all the token/key
2024-10-30 15:16:29.045 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Can't get valid token with input account in SmartHome server
2024-10-30 15:16:29.714 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Using account<EMAIL_ADDRESS>login to SmartHome cloud pass
2024-10-30 15:16:30.288 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 1 token/key failed
2024-10-30 15:16:30.443 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] connect device using method 2 token/key failed
2024-10-30 15:16:30.443 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Unable to connect device with all the token/key
2024-10-30 15:16:30.444 DEBUG (MainThread) [custom_components.midea_ac_lan.config_flow] Can't get any available token with device<PHONE_NUMBER>05063
...

you don't provide the full debug log, but from the part log, it should be the same issue as #275
there is still no any new progress with this fix or solution.
as we will use #275 issue to track all these related issue, so I will close this issue, sorry.
once we have solution with it in future, we will update you with this closed issue or new issue in #275.
as this issue will be connected with our exist #275 issue.


add some change to style

Slider component

[ ] This user story is developed on branch 12-Slider-v1.
[ ] create a slider component
[ ] let that component fetch 3 random recipes from the API
[ ] display the following info on it (photo, title)
[ ] add a button to go and display the single recipe

ok


reduced image size

reduced filesize from 1.7mb to 600k to speed up initial load times

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Duplicate macros produced

$meta_10.tar.gz

But those are macros from two different meta actions, no?


api: add extension configuration to EnvoyGateway

Companion to https://github.com/envoyproxy/gateway/pull/1074. This adds the configuration necessary in EnvoyGateway to register an extension
Relates to https://github.com/envoyproxy/gateway/issues/20

Codecov Report

Merging #1163 (6d1f11d) into main (aadebca) will increase coverage by 0.38%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main    #1163      +/-   ##
==========================================
+ Coverage   62.42%   62.81%   +0.38%
==========================================
  Files          72       72
  Lines        9430     9644     +214
==========================================
+ Hits         5887     6058     +171
- Misses       3136     3172      +36
- Partials      407      414       +7

see 19 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

just one small question, should Extension be a slice?

good point, either we make it Extensions and add a limit of 1 or deprecate this field in favor of Extensions when we support multiple

ok, let's review that later, LGTM for now.

As stated in https://github.com/envoyproxy/gateway/pull/1074 we made the decision to not support multiple extensions at the same time:

Too difficult to make sure extensions wouldn't step on each other's toes or conflict
Realistically few people would be running multiple extensions at the same time. Smaller extensions to Envoy Gateway can be accommodated later via https://github.com/envoyproxy/gateway/issues/24 and https://github.com/envoyproxy/gateway/issues/71 which can co-exist with this form of extensions

@arkodg should get #1074 merged?

we discussed this in the community meeting, and @AliceProxy and @haq204 mentioned they will raise some PRs for the Hooks API to make sure it is in line with the design doc contents


AttributeError: 'NoneType' object has no attribute 'cuda'

你好，请问我这个问题是什么原因？ 显卡是3060 12G，torch1.10，CUDA11.1，但报错并不是因为爆显存
PatchWorkpp::PatchWorkpp() - INITIALIZATION COMPLETE
Decoder(
(pe): Same()
(pts_linears): ModuleList(
(0): Linear(in_features=16, out_features=256, bias=True)
(1): Linear(in_features=256, out_features=256, bias=True)
)
(sdf_out): Linear(in_features=256, out_features=1, bias=True)
)
******* initializing first_frame: 0
initializing the first frame ...
PatchWorkpp::PatchWorkpp() - INITIALIZATION COMPLETE
******* tracking process started! *******
tracking frame:   0%|                                    | 0/99 [00:02<?, ?it/s]
Process Process-3:
Traceback (most recent call last):
File "/home/hlldy/anaconda3/envs/nerf/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/home/hlldy/anaconda3/envs/nerf/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/hlldy/NeRF-LOAM/src/tracking.py", line 83, in spin
self.do_tracking(share_data, current_frame, kf_buffer)
File "/home/hlldy/NeRF-LOAM/src/tracking.py", line 101, in do_tracking
decoder = share_data.decoder.cuda()
AttributeError: 'NoneType' object has no attribute 'cuda'
^C^CTraceback (most recent call last):

Hello,
Because we need the relative pose between t-1 and t-2 frames, which is inaccessible for first frame, so we do more tracking iteration for the first frame.
In your case, it seems that the tracking for the first frame is still running while the mapping need the tracked results.
So you may need wait more time for the first frame. You can adjust the  the code here to wait, e.g., 60s.
Hope this can solve your problem!

Hello, Because we need the relative pose between t-1 and t-2 frames, which is inaccessible for first frame, so we do more tracking iteration for the first frame.
In your case, it seems that the tracking for the first frame is still running while the mapping need the tracked results.
So you may need wait more time for the first frame. You can adjust the the code here to wait, e.g., 60s.
Hope this can solve your problem!

Thank you for your help!
I adjust 90s for the wait of code,but now there is the same problem,and the code is stuck at "insert keyframe" without moving.
Looking forward to your reply.
******* initializing first_frame: 0
initializing the first frame ...
PatchWorkpp::PatchWorkpp() - INITIALIZATION COMPLETE
******* tracking process started! *******
tracking frame:   0%|                                    | 0/99 [00:02<?, ?it/s]
Process Process-3:
Traceback (most recent call last):
File "/home/hlldy/anaconda3/envs/nerf/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap
self.run()
File "/home/hlldy/anaconda3/envs/nerf/lib/python3.8/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/home/hlldy/NeRF-LOAM/src/tracking.py", line 83, in spin
self.do_tracking(share_data, current_frame, kf_buffer)
File "/home/hlldy/NeRF-LOAM/src/tracking.py", line 101, in do_tracking
decoder = share_data.decoder.cuda()
AttributeError: 'NoneType' object has no attribute 'cuda'
mapping process started!!!!!!!!!
frame id 1
trans  tensor([0., 0., 0.], device='cuda:0')
insert keyframe

Great! Happy to hear that!

By the way, you can uncomment all the torch.cuda.empty_cache() in files "src/variations/render_helpers.py" and "src/variations/voxel_helpers.py" to gain some efficiency. While this will centainly add some GPU memory.

By the way, you can uncomment all the torch.cuda.empty_cache() in files "src/variations/render_helpers.py" and "src/variations/voxel_helpers.py" to gain some efficiency. While this will centainly add some GPU memory.

Thanks for your advice,if I have enough GPU memory,I will try to uncomment it. : )


Changed initialDelaySeconds to 120 and set CPU to 1vcpu and memory to 4G

Changes to get LocalStack to deploy nicely on AWS EKS.

Ok. These fields are overridable in values.yaml. Closing the PR.


[Bug] Cartesian Join based deletion is causing performance problems when it hits a certain scale for microbatch models

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Cartesian Join based deletion is causing data spilling to disk which heavily bogs down performance
The delete statement looks like:
delete from analytics_dev.dbt_aescay.my_model DBT_INTERNAL_TARGET
    using analytics_dev.dbt_aescay.my_model__dbt_tmp DBT_TMP_TARGET
    where (
    DBT_INTERNAL_TARGET.event_at >= TIMESTAMP '2024-10-14 00:00:00+00:00'
    and DBT_INTERNAL_TARGET.event_at < TIMESTAMP '2024-10-15 00:00:00+00:00'

    );

But we are not doing anything with my_model__dbt_tmp in the where clause.
We can simplify this logic and improve the performance, by instead doing:
delete from <existing> where <date range>;
insert into <existing> from <new data for same date range>;

One advantage of microbatch is that we know in advance the exact boundaries of every batch (time range, cf. "static" insert_overwrite).
In a world where we support "microbatch merge" models (= update batches by upserting on unique_key, rather than full batch replacement), then we would want to join (using) based on unique_key match, like so:
delete from analytics_dev.dbt_aescay.my_model DBT_INTERNAL_TARGET
    using analytics_dev.dbt_aescay.my_model__dbt_tmp DBT_TMP_TARGET
    where DBT_INTERNAL_TARGET.event_id = DBT_TMP_TARGET.event_id
    and (
    DBT_INTERNAL_TARGET.event_at >= TIMESTAMP '2024-10-14 00:00:00+00:00'
    and DBT_INTERNAL_TARGET.event_at < TIMESTAMP '2024-10-15 00:00:00+00:00'

    );

But this shouldn't be the default assumption.
Expected Behavior
We should delete this line.
Steps To Reproduce
See here.
Relevant log output
No response
Environment
- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

This seems like a decent deal-breaker at the moment - unless I'm facing some other config issue.
To put some numbers in perspectives (on Snowflake, based on a X-Small warehouse):

Take one table with ~30 millions records (~0.5GB) roughly spread over 30 days
Lookback of 3 days
Delete query takes more than 10 minutes (I cancelled it after that), and this has to be done for each lookback period

Hoping we can get this one prioritized 😊


DataDescription.data_level needs a validator for valid tags

Is your feature request related to a problem? Please describe.
Users are currently still uploading data which includes outdated data_level tags, which need to be then updated manually (via a script that is already written) to our current tag standards.
Describe the solution you'd like
Introduce a validator to DataDescription that checks whether the tag input is valid or not, and converts it to a valid analog if not. If there is no valid analog, reject the model.
Describe alternatives you've considered
We could also solve this via running the data_description_upgrade over all DataDescriptions regularly, but this requires a lot of oversight.

The current version of aind-data-schema uses enums, which validate the inputs. A few thoughts:

People use older versions of aind-data-schema. We can convince people to upgrade, but there will always be a lag between when aind-data-schema is updated and users upgrade their dependencies
I think the overall idea of using a semi-structured Document Store vs. rigid relational databases, was to allow users some flexibility in describing the metadata. @dyf can add some extra context.
There were early discussions on whether every schema update should require a corresponding script that migrates the previous version to the current version. I think we settled on just writing upgrade scripts as needed. I'm happy to revisit the discussion though.

I agree with @jtyoung84, and I think it makes sense to centralize this logic in the upgrader classes.

@jtyoung84 Convert this to user story


Fix replication module variable

Replication module destination_bucket_name has default instead of description.

:tada: This issue has been resolved in version 2.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Enable Request Supplemental even when the Report has been accepted

#1587
Changelog:

Request Supplemental for Compliance Report should be available even when the status is accepted

 Supplemental Reporting | Request Supplemental Report button remains visible to analyst and manager throughout governments review process |2|


Use Annotated to Indexed to complete type hints

Discussed in https://github.com/roman-right/beanie/discussions/637

Originally posted by hudrazine August  4, 2023
If you define Indexed as a type hint for a field, the type checker will complain :
class Task(Document):
    title: Indexed(str)  # I get complaints from pylance

    class Settings:
        name = "inbox_tasks"

This is due to the use of a direct call expression in the type.
Also, the type checker cannot parse this as a specific type (in this case, str), so the type hint is not reflected in the IDE either.
This way, they won't complain :
IndexedTitle = Indexed(str)  # Define outside

class Task(Document):
    title: IndexedTitle  # pylance also smiles
    ...

But the IDE does not reflect the correct type hints; above all, this is not smart.
So, use typing.Annotated :
class Task(Document):
    title: Annotated[str, Indexed(str)]
    # or like this
    title: Annotated[str, Indexed()]
    title: Annotated[str, Indexed(index_type=pymongo.TEXT)]
    ...

In this way, metadata of indexing can be added to the field while providing type hints.
In the current beanie(1.21.0), the type hint works, but it is not marked as Indexed.
I think this method is well proven and has been incorporated in Pydantic and FastAPI, do you think it would be beneficial for beanie?

Hi,
Should this issue be closed?


Issue Template Needs Updating :-)

Heya!
The issue template currently ends with this text:
Finally, we're going to put someone's name here, so they get alerted to the new issue and can assign it to the right person. @robmyers @little-wow
It should be updated to remove me and add a more up-to-date contact. :-)

@robmyers thanks for reporting! We've updated the template to remove you. I'm watching the repo and I get emails about any new issues that are created so I did not explicitly add myself.


apns:connect error

Erlang 22. gun - master, apns4erl - master.
I do all as in the example.
But:
apns:connect(#{name => another_cert, apple_host => "api.push.apple.com", apple_port => 443, certfile => "priv/aps.pem", keyfile => "priv/AuthKey.pem", type => cert}).
and
apns:connect(cert, another_connection).
{ok, pid()}
19:43:32.909 [error] gen_statem another_connection in state open_common terminated with reason: {{badmatch,{error,{options,{transport_opts,[{certfile,"./keys/aps.pem"},{keyfile,"./keys/AuthKey.pem"}]}}}},state_functions}
19:43:32.909 [error] CRASH REPORT Process another_connection with 0 neighbours crashed with reason: no match of right hand value {error,{options,{transport_opts,[{certfile,"./keys/aps.pem"},{keyfile,"./keys/AuthKey.pem"}]}}} in apns_connection:open_common/3 line 254
19:43:32.910 [error] Supervisor apns_sup had child apns_connection started with {apns_connection,start_link,undefined} at <0.2390.0> exit with reason no match of right hand value {error,{options,{transport_opts,[{certfile,"./keys/aps.pem"},{keyfile,"./keys/AuthKey.pem"}]}}} in apns_connection:open_common/3 line 254 in context child_terminated
If I call apns:connect(token, another_connection) I get:
19:48:30.123 [error] gen_statem another_connection in state open_common terminated with reason: {{badmatch,{error,{options,{transport_opts,[]}}}},state_functions}
19:48:30.123 [error] CRASH REPORT Process another_connection with 0 neighbours crashed with reason: no match of right hand value {error,{options,{transport_opts,[]}}} in apns_connection:open_common/3 line 254
19:48:30.123 [error] Supervisor apns_sup had child apns_connection started with {apns_connection,start_link,undefined} at <0.3103.0> exit with reason no match of right hand value {error,{options,{transport_opts,[]}}} in apns_connection:open_common/3 line 254 in context child_terminated.
What am I doing wrong?

https://github.com/inaka/apns4erl/blob/master/src/apns_connection.erl
Line 233 must be:
tls_opts => TransportOpts

@Akick do you mind sending a pull request with that change?
Thanks.

@elbrujohalcon Done


Dependency EC utils: MinioDatastore needs to be able to set SSL false

MinioDatastore needs to be able to set SSL false

requirements.txt updated with:
earthcube-utilities @ git+https://github.com/earthcube/earthcube_utilities@ed9ce10
until we create a new version


The insaller is not updated for version5

The installer document is not yet updated to be used. It still refers to old versions. It should be modified as
"require": {
    "ypnos-web/cakephp-datatables" : "dev-master"

}

My fork https://github.com/umer936/cakephp-datatables/ works for CakePHP 5
https://packagist.org/packages/umer936/cakephp-datatables
    "umer936/cakephp-datatables" : "@stable"


Fix a typo with new bounding box code

See https://forum.babylonjs.com/t/pg-crashes-an-example-of-playing-vats-on-instances/51768.
We should consider adding a test for this.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15257/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15257/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15257/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15257/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15257/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15257/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15257/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15257/merge#BCU1XR#0

Visualization tests for WebGPU (Experimental)
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15257/merge/testResults/webgpuplaywright/index.html

WebGL2 visualization test reporter:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/15257/merge/testResults/webgl2playwright/index.html


⚠ Bofrost.be has degraded performance

In a2e5baa, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 951 ms

Resolved: Bofrost.be performance has improved in a0168d9.


Reverting the catalogSoruce to openshift-marketplace

Signed-off-by: Ankit Kurmi<EMAIL_ADDRESS>py-mtcli
Description
Reverting catalogSource to openshift-marketplace. Might be handy for the transient_failure

/ok-to-test

/ok-to-test

Real fix is in setting up a NetworkPolicy for network access.
This change stays for now.


Add the possibility to redirect specific smartcard readers

Until now, /smartcard: had the behaviour to redirect every connected readers. It didn't matter what you used after the parameter /smartcard:xxxx:yyyy.
With this patch you can:

use /smartcard: "as is" (without argument) to continue to redirect every readers
use /smartcard:"Reader name" (you have to repeat that for every reader you want to redirect)

The reader name is exactly the one returned by libpcsclite, e.g.
root@host:# opensc-tool -l
Detected readers (pcsc)
Nr.  Card  Features  Name
0    Yes             Xiring Leo V2<PHONE_NUMBER>5036) 00 00
1    Yes             Xiring Leo V2<PHONE_NUMBER>4712) 01 00
(Thanks to A. Aing for this PR)

@freerdp-bot test.

@bmiklautz so what do you think about this PR?
Thanks!

@HenryJacques This pull looks nice, but when I try to connect with a specific name, the smartcard channel gets loaded twice. This does not happen when using /smartcard without argument.

@akallabeth will check into that.

@akallabeth
I've just checked what you said.
Until this PR, using /smartcard or /smartcard: (with the colon) didn't make any difference.
With this PR, /smartcard has no effect anymore (that's why you don't see the channel loaded).
If you want to redirect all readers, you'd have to use /smartcard:
Anyway, even without this PR, the behaviour you're describing was already there. The PR didn't introduce that.
Can you check that?

@HenryJacques Ok, can confirm this behavior. Would suggest to change the commandline handling back to the old one again (the : is a argument delimiter, so it is bad behavior for /smartcard and /smartcard: to behave differently).

@akallabeth I've changed the command line handling in my branch.
However since I've forked the FreeRDP master branch, some changes have been made in the same files.
How can I rebase with master (using the github web interface)?
Or should I make a new PR?
Thanks

@HenryJacques You can rebase your branch locally with git fetch --all and git rebase upstream/master assuming you have configured the freerdp repository at upstream. Then you have to force push the branch and you should be set. Using the web interface I don't know if it can be done.

@akallabeth thanks for the hint.
However I am not used to the git command line and I'm more used to work directly on the web interface.
Anyway this is what I got:
user@host:~/git/FreeRDP# git branch -a
  master
* remotes/origin/smartcard
  smartcard
  remotes/origin/HEAD -> origin/master
  remotes/origin/channels
  remotes/origin/master
  remotes/origin/smartcard
  remotes/origin/stable-1.0
  remotes/origin/stable-1.1
  remotes/origin/tsg
  remotes/origin/winpr
  remotes/origin/winpr_cleanup
  remotes/origin/xrdp-ng
user@host:~/git/FreeRDP# git fetch --all
Fetching origin
user@host:~/git/FreeRDP# git rebase origin/master
warning: refname 'remotes/origin/smartcard' is ambiguous.
Current branch remotes/origin/smartcard is up to date.

Not sure what to do :/
Sorry for asking basic questions, I've done some research on Internet but didn't found a satisfactory answer...
Thanks in advance.

@HenryJacques Ah, well in that case you first have to add freerdp to your remotes git remote add upstream https://github.com/freerdp/freerdp that adds upstream to your remotes. After that git fetch upstream and git rebase upstream/master

@akallabeth
almost there, thanks for the tip.
I've been able to rebase (with a conflict that I've been able to resolve)
user@host:~/git/FreeRDP# git rebase --continue
client/common/cmdline.c: needs merge
You must edit all merge conflicts and then
mark them as resolved using git add
user@host:~/git/FreeRDP# git add client/common/cmdline.c
user@host:~/git/FreeRDP# git rebase --continue
Applying: keep original behaviour with empty smartcard argument
user@host:~/git/FreeRDP# git push -f
Username:
Password:
Everything up-to-date

I suppose I have to do something else now because there is no change on my github repository...
Thank you for your help

@HenryJacques Sorry for the delay, missed your response. Looks like something did not work. Have a look at the git manual here: https://git-scm.com/book/en/v1/Git-Branching-Rebasing

@akallabeth no problem at all. You're not here to teach me git ;)
I'll look into that.

@akallabeth hum.... I did something. Was that ok?

@HenryJacques No, looks like you did a merge...

@akallabeth  That's what I was afraid of.... Will do another PR.

@akallabeth I did another PR #3126
I hope this time it is ok ;)