How to pass data to the next tab?

hello! There are some problems in my project. I have two tab in my view, and I want to pass data to my on of tab like this:

I want to pass a data to the CheckProjectDescribe tab,
How to do that? thank you very much!!!

In the parent component of the tabs you must make the state changes, example:
`
myFunction(){
this.setState({
myVar: true
});
}
...

...
`
then in your tab component
`
componentWillReceiveProps(nextProps) {
//doSomething
}
`

@juanmanuelarze Thank you so much!!!  I got this data in my tab component, but when I first enter into the tab component ,the view is empty, unless when I enter into the tab "bbb" then into "aaa" ,
the data show! like this
In the parent component
`    constructor(props) {
super(props);
this.state = {
describeContent:''
};
}
componentWillMount() {
    const { content } = this.props;
    this.setState({
        describeContent: content
    });
}`

<ScrollableTabView                     tabBarUnderlineStyle={{backgroundColor: '#3af',height:2}}                     tabBarBackgroundColor='#FFFFFF'                     tabBarActiveTextColor='#3af'                     tabBarInactiveTextColor='#666'                     tabBarTextStyle={{fontSize: 14,marginTop:5}}                 >                     <CheckProjectDescribe tabLabel="aaa" describeContent={this.state.describeContent}/>                     <CheckProjectFile tabLabel="bbb" />                 </ScrollableTabView>
in tab component:
`constructor(props) {
super(props);
this.state = {
containerTxt:''
};
}
componentWillReceiveProps(describeContent) {
    console.log(describeContent.describeContent);
    this.setState({
        containerTxt:describeContent.describeContent
    });
}

render() {
    return (
        <View style={styles.container}>
            <Text>{this.state.containerTxt}</Text>
        </View>
    );
}`

I think maybe is thecomponentWillReceiveProps problem
I want to know how to show the data when I first enter into the tab component
thank you  soooo much!!!

ComponentWillReceiveProps does not run the first time, only when a change in the value of a parameter occurs, use componentDidMount for the first time.
ComponentWillMount is executed before the render, do not use setState there, setState calls to re-render on a (in this case) on a non-rendered component yet.
ComponentDidMount is executed after the render, there you can use a setState
I suggest you read the lifecycle of reacting the native components
Https://facebook.github.io/react/docs/react-component.html
:dango:

@juanmanuelarze I have already try it with  componentDidMount  before I reply you ,and  I try it again just now, but it have a problem in there
Cannot read property 'describeContent' of undefined

and I change my code like this
In the parent component:
constructor(props) {         super(props);         this.state = {             describeContent: ''         };     }
componentDidMount() {         const { content } = this.props;         this.setState({             describeContent: content         });     }
in tab component:
constructor(props) {         super(props);         this.state = {             containerTxt: ''         };     }
componentDidMount(describeContent) {         this.setState({             containerTxt:describeContent.describeContent         });     }

@juanmanuelarze I have change my code like this
In the parent component:
constructor(props) { super(props); this.state = { describeContent: '' }; }
componentDidMount() { const { content } = this.props; this.setState({ describeContent: content }); }
in tab component:
componentWillReceiveProps(describeContent) {
        this.setState({
            containerTxt:describeContent.describeContent
        });
    }

It works!!! strangely!!!!!
And  thank you soooo much !!!!!

It is a pleasure 😁


Update docs to use HTTPS for CDN

Per screenshot below

We should encourage developers to use the HTTPS hosted files by default. If developers plan to use Office Fabric in their Add-Ins they'll have to so as to avoid mixed content blocking.

Excellent point. There are no issues (that I'm aware of anyway) with requesting HTTPS resources on HTTP-served pages, so it would be best practice to link to the HTTPS version. I've confirmed that appsforoffice.com supports HTTPS, so we just need to update the docs.

Thanks for the update @mikewheaton :+1:

I've made this change and am working on getting it merged into the documentation site. Will leave this issue open until we've deployed the site with the updated URLs.

Usually, the protocol is not included for CDN references. It would look something like //cdn.example.com/resource/fabric.css. That way, the link can inherit the protocol from the server whether it's server HTTP or HTTPS. HTTPS on an HTTP site might show a "mixed content" warning to the user when the page loads. That said, you would run into issues when running locally.

:+1:

I actually did look at using protocol-relative URLs (e.g. //cdn.com/fabric.css) but after some research it seems that this is no longer the recommended approach. See the note at the top of this article from Paul Irish.

Interesting. Everyone should be using HTTPS now anyways. :)

We've made this change to the documentation site and it will included in the next deployment.


latest commit crashes

I'm getting the following.  I've no idea what it means
C:\Users\Micah Warren\Anaconda\Ricci\exp37\clustering\Ricci>python localricci.py
Exception in thread Thread-3:
Traceback (most recent call last):
File "C:\Users\Micah Warren\Anaconda\lib\threading.py", line 810, in __bootstrap_inner
self.run()
File "C:\Users\Micah Warren\Anaconda\lib\threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Users\Micah Warren\Anaconda\lib\site-packages\numba\dispatcher.py", line 203, in _explain_matching_error
raise TypeError(msg)
TypeError: No matching definition for argument type(s) array(float64, 2d, C), array(float64, 2d, C), array(float64, 2d, C)
Exception in thread Thread-4:
Traceback (most recent call last):
File "C:\Users\Micah Warren\Anaconda\lib\threading.py", line 810, in __bootstrap_inner
self.run()
File "C:\Users\Micah Warren\Anaconda\lib\threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "C:\Users\Micah Warren\Anaconda\lib\site-packages\numba\dispatcher.py", line 203, in _explain_matching_error
raise TypeError(msg)
TypeError: No matching definition for argument type(s) array(float64, 2d, C), array(float64, 2d, C), array(float64, 2d, C)

So I used Anaconda 2.5 and this did not happen.  The above happens in Anaconda 2.3.  I now have Anaconda 2.5 installed in Fenton.


MPS: Only write used variables to output

As a lot of solvers error out if the BOUNDS section includes unused variables, this PR updates the MPS output writer to only add variables that were actually used in the problem to the BOUNDS section.
In this PR I also added a generic anyhow::Error→MpsWriteError conversion asn "Unknown Error", but this is mostly just to make the code compile. The method used_variable_ids() returns an anyhow::Result, but it doesn't seem to be able to produce any errors at all. Still, changing that method would be an API change so I decided to leave it as is. I added the error conversion instead of unwrapping just in case.

Still, changing that method would be an API change so I decided to leave it as is.

Since this PR will be released as OMMX Rust SDK 2.0.0, this breaking change can be acceptable.

In this PR I also added a generic anyhow::Error→MpsWriteError conversion asn "Unknown Error", but this is mostly just to make the code compile.

I propose to remove MpsWriteError by replacing to anyhow::Error. There is little reason to separate this error statically.

I changed the return type on used_decision_variable_ids to remove the Result.
Regarding MpsWriteError, I think there's value in having custom error types that list the possible errors that can happen, especially in a library like ommx. In this particular case it's also a bit convenient for our code as we check the error type in write_columns to switch to a message more appropriate to the objective function (though of course we could achieve that in other ways). If you insist I'll remove MpsWriteError but I've left it for now.

If you insist I'll remove MpsWriteError but I've left it for now.

Ok, no need to remove it. Please fix test failures.

Sorry, I forgot to run the tests locally. Fixed.

Thanks a lot


Update resource-manager-template-keyvault.md

Fixed casing for PowerShell cmdlets.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair : Thanks for your contribution to the Azure documentation! The author, @tfitzmac, has been notified to review your proposed change.

@alexandair - good catch, and thanks for improving the consistency of the docs.
@tysonn - this PR can be merged


When I install shadcn then I get error

This is my command and error

what node version you're using? Try upgrading that to 18 if below that.

Also try removing your entire node_modules folder or renaming it to _bak then run npm install again.

I did all the two suggestions nothing seems to be working. My Node js v18.16.0

Same Here I  have try diffrent  ways:-

Upgrade node and npm version - Same Error
Downgrade node and npm version - Same Error
open in cmd:- Get Same Error
run on node terminal:- Same Error
uninstall node_modules:- Get Same Error
create new project of next.js dummy: Get Same Error

So, This type error are also find by me... Anyone help me I need help...
The main think is that once my friend try run same code so this commad is working on there system.
I can't resolve my issue.
Anyone help me I can give my system Throgh remotly Plz ping me

hi, i got the same error.
if you installed shadcn after installing your nextjs project check if you have a new app  folder at the root of your project. When installing shadcn, an app folder + a tailwind config and global.css file are installed. Before deleting them, add what they contain to your tailwind config and global.css files. Once done, delete.
If it persists, stop your server ctrl+C, delete .nextjs and restart your server with npm run dev

This issue has been automatically closed because it received no activity for a while. If you think it was closed by accident, please leave a comment. Thank you.

gpt the same error
C:\Users\CW\Desktop\n-ap>npx shadcn-ui@latest init
node:internal/process/esm_loader:40
internalBinding('errors').triggerUncaughtException(
^
Error: Cannot find package 'C:\Users\CW\AppData\Local\npm-cache_npx\125ee17d583c4e03\node_modules\npm-run-path\node_modules\path-key\package.json' imported from C:\Users\CW\AppData\Local\npm-cache_npx\125ee17d583c4e03\node_modules\npm-run-path\index.js
Did you mean to import path-key/index.js?
at legacyMainResolve (node:internal/modules/esm/resolve:189:26)
at packageResolve (node:internal/modules/esm/resolve:776:14)
at moduleResolve (node:internal/modules/esm/resolve:838:20)
at defaultResolve (node:internal/modules/esm/resolve:1043:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12)
at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25)
at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:228:38)
at ModuleWrap. (node:internal/modules/esm/module_job:85:39)
at link (node:internal/modules/esm/module_job:84:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
Node.js v20.9.0

had the same issue while using node v 20.9 with pnpm, but it got resolved  when i used npx

Node.js v20.9.0 same vision still error come index.Js 254:5747 something how to solve

Lenovo@DESKTOP-UA6EBDM MINGW64 ~/ecommerce-admin (master)
$ npx shadcn@latest init
node:internal/modules/cjs/loader:1225
const err = new Error(message);
^
Error: Cannot find module '@ts-morph/common'
Require stack:

C:\Users\Lenovo\AppData\Local\npm-cache_npx\d66c5096c7023bfb\node_modules\ts-morph\dist\ts-morph.js
at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
at Module._load (node:internal/modules/cjs/loader:1051:27)
at Module.require (node:internal/modules/cjs/loader:1311:19)
at require (node:internal/modules/helpers:179:18)
at Object. (C:\Users\Lenovo\AppData\Local\npm-cache_npx\d66c5096c7023bfb\node_modules\ts-morph\dist\ts-morph.js:3:14)
at Module._compile (node:internal/modules/cjs/loader:1469:14)
at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
at Module.load (node:internal/modules/cjs/loader:1288:32)
at Module._load (node:internal/modules/cjs/loader:1104:12)
at cjsLoader (node:internal/modules/esm/translators:346:17) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'C:\Users\Lenovo\AppData\Local\npm-cache\_npx\d66c5096c7023bfb\node_modules\ts-morph\dist\ts-morph.js'
]
}

Node.js v20.17.0
i've been having this issue for a while now. I downgraded from version 22.3.0 to 20.17.0 and still the same thing. I deleted and reinstalled the entire node module and had to manually install the  @ts-morph/common  module and yet nothing. This is the third time i am deleting everything and starting again.

thank u


Remove kwargs dict expansion

Ticket

Purpose
** expands a dictionary as kwargs to a fn call. In this case it is completely unneccesary as the dict is a literal defined inside the call to the fn. Here it is simpler to assign the kwarg directly.

Changes

Side effects

QA Notes

Deployment Notes

Coverage remained the same at 89.929% when pulling 5ebf471d596d7ce7fe6c6e88509ba37ed5af1c64 on birdbrained:ft/fix-unneccesary-dict into e6a82e8eabcefa740fcaa2a68f717b25e14668fd on CenterForOpenScience:develop.


Ability to run a process in the background

Was trying something like
config.trigger.after [:up, :resume] do
    run "my_long_running_process.sh &"
end

...expecting the background flag to force the trigger execution to exit, but it continues "Executing command" forever.

I got one to work like this:
config.trigger.after :up do
    `(vagrant rsync-auto &>/dev/null) &`
end

This is tricky to do right
It would be better for vagrant-triggers to provide a run_bg command so callers don't have to muddle through the formula


[release-0.58]Fix and arrange libvmi.GetPodByVirtualMachineInstance function to avoid flakiness

What this PR does / why we need it:
This PR is manual backport of  https://github.com/kubevirt/kubevirt/pull/8902/commits/7e53ea9cf346ef6f98217c1be206875a7d7924e8
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

/lgtm
/cc @enp0s3
Can you please also have a look?

@Barakmor1 Hi, I see the following error:
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   tests/vmi_gpu_test.go
no changes added to commit (use "git add" and/or "git commit -a")
make: *** [Makefile:131: build-verify] Error 1

Perhaps you need to commit make generate changes

@Barakmor1 Hi, I see the following error:
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   tests/vmi_gpu_test.go
no changes added to commit (use "git add" and/or "git commit -a")
make: *** [Makefile:131: build-verify] Error 1

Perhaps you need to commit make generate changes

Done :)


Add cacheable module

This introduces a new module, Primer::Cacheable which is extracted
from the monolith. This module provides the ability for an individual
component to opt-in to caching behavior.
When enabled, this module:

Caches component instances based on the args, kwargs, and block it
receives.
Caches the content generated by each component instance, so renders
are free after the first call.
Introduces a new method, .with which must be used instead of .new
to opt-in to the caching behavior.

Each component that includes this module must implement a method called
cache_container that returns a mutable hash. It's recommended that
this method return an attribute defined on an instance of
ActiveSupport::CurrentAttributes which allows the cache to be cleared
after each request/response.
The largest con to this approach is that component calls must be updated
to use .with instead of .new. This is intentional since it could be
difficult to track down this functionality if we kept it behind the
standard `.new.

Closing as stale


Make the @yamada-ui/avatar component headless

script: make-component-headless
package: @yamada-ui/avatar
Description
Currently, the @yamada-ui/avatar component has minimal styles set within the component's source code.
We want to make this style transferable to the theme and make the component headless, enabling more flexible UI customization.
Problem Statement/Justification
By making the @yamada-ui/avatar component headless, we can achieve more flexible styling tailored to the project.
Proposed Solution or API
The styles within the component are mostly defined by css: CSSUIObject and set to a prop named __css. We will transfer these styles to the packages/theme/src/components.
The code below is just an example and not the actual code.
packages/components/input/src/input-group.tsx
const css: CSSUIObject = {
- width: "100%",
- display: "flex",
- position: "relative",
  ...styles.container,
}

packages/theme/src/components/input.ts
baseStyle: {
  container: {
+   width: "100%",
+   display: "flex",
+   position: "relative",
  },
  field: {
    width: "100%",
    minWidth: 0,
    outline: 0,
    position: "relative",
    appearance: "none",
    transitionProperty: "common",
    transitionDuration: "normal",
    _disabled: {
      opacity: 0.4,
      cursor: "not-allowed",
    },
  },
  element: {
    color: ["blackAlpha.600", "whiteAlpha.700"],
  },
},

[!TIP]
In cases where the styles within the component are dynamically changed, there may be instances where it is not possible to transfer the styles to the theme.
In such cases, it needs to be discussed in this issue. Please feel free to send comments to this issue.

Additional Information
The @yamada-ui/avatar component exists in packages/components/avatar/src. You need to check all the components in this folder and if they contain styles internally, you need to modify them.
This change could have a significant impact on projects using Yamada UI, so we will work on it within the scope of v2.0.
Please create the branch for working on this issue from the remote branch v2.0, and direct your pull requests to the v2.0 branch as well.
Please select major for the changeset and create a pull request.

@hirotomoyamada
Hi! Can I work on this issue?

Fixed #1978


Width with breakpoints (w-lg-50 w-md-75 w-100)

There are times where on a desktop an element would look best at 50% width, while on tablet or laptop it might need a little more of the available space (say, 75% width) and on a mobile device you don't want to restrict it, so keep it at 100%
so I was hoping to have breakpoints for the width classes
w-25, w-sm-25, w-md-25, w-lg-25, w-xl-25
w-50, w-sm-50, w-md-50, w-lg-50, w-xl-50
w-75, w-sm-75, w-md-75, w-lg-75, w-xl-75
w-100, w-sm-100, w-md-100, w-lg-100, w-xl-100
very helpful if there is a small bit of content for an element, and you want it to span a couple of lines, but as the screen gets smaller the element will naturally create those breaks so the class is no longer needed

See https://github.com/twbs/bootstrap/pull/31323, unless they've changed their mind. Also, it's not hard to implement yourself, just add a property to the utilities.

Yup, the grid classes get you this for free in v5 without the need for extra utilities.

Do you mean the col-x in freeform mode (not inside a container->row).
So col-6 is like w-50, and col-4 is like w-25, etc.?

I definitely need this.

Can someone show how to do it in Bootstrap 5? This is tricky for us, non-designers. "w-md-50" is perfectly understandable, but Bootstrap 5 does not support this as stated above.

@rackycz what about this:
<div class="col-12 col-md-6 col-lg-3">
    <input class="form-control" value="12" name="username" type="text" >
</div>


Provide a convention mechanism for ingesting Data

add an "out of the box" mechanism that uses some config/schema/convention for 1:1 mapping nodes and rels

Use patterns to describe which parts of an event turn into a node/relationship.
streams.sink.topic.nodes.my-topic=:Person{name, email}


rp-pppoe-server. Openwrt 23.05. No menu services/rp-pppoe-server

-Install rp-pppoe-server, luci-app-rp-pppoe-server, reboot.
-search for a new menu item. There is nothing.
-go to url: cgi-bin/luci/admin/services/rp-pppoe-server
404 Not Found
Sorry, the object you requested was not found.

No page is registered at '/admin/services/rp-pppoe-server'. If this url belongs to an extension, make sure it is properly installed. If the extension was recently installed, try removing the /tmp/luci-indexcache file.

Unable to dispatch: /cgi-bin/luci/admin/services/rp-pppoe-server

where is?

DISTRIB_ID='OpenWrt'
DISTRIB_RELEASE='23.05.5'
DISTRIB_REVISION='r24106-10cc5fcd00'
DISTRIB_TARGET='mediatek/mt7622'
DISTRIB_ARCH='arm64'
DISTRIB_DESCRIPTION='LuCI openwrt-23.05 branch git-24.264.56413-c7a3562'
DISTRIB_TAINTS=''

Closed by c344ad02a06a92fb9d8fab237cfc878a06b71ffd and 3aa60877ea4bc47b86c3ee11448db7503a20ae01

You may need to wait a few days for the new package to roll out. Let me know how you get on with the new JS version.


Error when saving page

Describe the Bug
Probably caused by #1320. Trace:
ar 22 12:06:43 ERROR   django.request - Internal Server Error: /schneeberg/pages/de/3242/edit/
Traceback (most recent call last):
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner
    response = get_response(request)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/views/generic/base.py", line 70, in view
    return self.dispatch(request, *args, **kwargs)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/utils/decorators.py", line 43, in _wrapper
    return bound_method(*args, **kwargs)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/django/views/generic/base.py", line 98, in dispatch
    return handler(request, *args, **kwargs)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/cms/views/pages/page_form_view.py", line 262, in post
    page_translation_form.instance.page = page_form.save()
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/cms/forms/custom_model_form.py", line 132, in save
    return super().save(commit=commit)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/treebeard/forms.py", line 157, in save
    self.instance.move(reference_node, pos=position_type)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/integreat_cms/cms/models/abstract_tree_node.py", line 285, in move
    super().move(target=target, pos=pos)
  File "/opt/integreat-cms/.venv/lib/python3.9/site-packages/treebeard/ns_tree.py", line 357, in move
    if target.is_descendant_of(self):
AttributeError: 'NoneType' object has no attribute 'is_descendant_of'

Duplicate of #1320


Update special attack counter to exclude all hits on olm mage hand

Some truncated discussion in discord starting here: https://discord.com/channels/301497432909414422/419891709883973642/996904476973748414.
It's possible for the plugin to mis-identify 2 attack hitsplats from the same player, if one is a long-range attack followed by a melee special attack. Example here: https://www.twitch.tv/videos/1530201934?t=3h4m25s, which is a sang on the mage hand from far away, followed by a bgs on the melee hand. Those hitsplats land on the same tick, with the sang hitting a 30 and the bgs hitting 0, but the plugin shows it as a 30 from the bgs.
This commit doesn't fix the underlying issue, but at least prevents it in chambers by excluding all hitsplats on the mage hand from being considered. Not sure where else this is likely to occur. Some discussion in https://discord.com/channels/301497432909414422/419891709883973642/996907345214967878 and subsequent messages about a way to better track the attacks, but not needed for this fix.
I haven't actually done a run with these changes to confirm they work/don't break anything. Happy to do that if wanted for regs, probably not cm.

added in ec2d5dcbae591603a32bcefc9011c7c51443c45a


Retry limit

We've been told that TChannel does a lot less bookkeeping if retry limit is set to 0. Doing so for Ringpop, especially it's gossip protocol, should/will reduce that amount of bookkeeping done.
@uber/ringpop

lgtm

thanks for the quick "lgtm" @thanodnl


Fix grammar and use of verbs

Fix grammar like the plural form of words and use of verbs.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[ ] My changes do not use shortened URLs or affiliate links.

Closes #XXXXX

@SudhakarKuma The PR content is plagiarised according to the checkboxes you've ticked. Please remove plagiarism and reopen the PR


python.testing.pytestArgs: passing config file path when it's in a subfolder consumes 100% of a CPU

Discussed in https://github.com/microsoft/vscode-python/discussions/23386

Originally posted by pawamoy May  8, 2024
VSCode keeps spawning a pytest process to collect tests (apparently).
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--config-file=config/pytest.ini"
    ],

It runs it in my current .venv: /absolute/path/to/.venv/bin/python -m pytest -p vscode_pytest --collect-only --config-file=config/pytest.ini.
The process never stops and consumes one CPU entirely.
My pytest config:
[pytest]
python_files =
  test_*.py
  *_test.py
  tests.py
addopts =
  --cov
  --cov-config config/coverage.ini
testpaths =
  tests

# action:message_regex:warning_class:module_regex:line
filterwarnings =
  error
  # TODO: remove once pytest-xdist 4 is released
  ignore:.*rsyncdir:DeprecationWarning:xdist
  ignore:.*slated for removal in Python:DeprecationWarning:.*

If I run the command myself:
% .venv/bin/python -m pytest -p vscode_pytest --collect-only --config-file=config/pytest.ini
Traceback (most recent call last):
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 865, in import_plugin
    __import__(importspec)
ModuleNotFoundError: No module named 'vscode_pytest'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pytest/__main__.py", line 7, in <module>
    raise SystemExit(pytest.console_main())
                     ^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 206, in console_main
    code = main()
           ^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 159, in main
    config = _prepareconfig(args, plugins)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 346, in _prepareconfig
    config = pluginmanager.hook.pytest_cmdline_parse(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pluggy/_hooks.py", line 513, in __call__
    return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pluggy/_manager.py", line 120, in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pluggy/_callers.py", line 139, in _multicall
    raise exception.with_traceback(exception.__traceback__)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pluggy/_callers.py", line 122, in _multicall
    teardown.throw(exception)  # type: ignore[union-attr]
    ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/helpconfig.py", line 106, in pytest_cmdline_parse
    config = yield
             ^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/pluggy/_callers.py", line 103, in _multicall
    res = hook_impl.function(*args)
          ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1152, in pytest_cmdline_parse
    self.parse(args)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1501, in parse
    self._preparse(args, addopts=addopts)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 1384, in _preparse
    self.pluginmanager.consider_preparse(args, exclude_only=False)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 794, in consider_preparse
    self.consider_pluginarg(parg)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 817, in consider_pluginarg
    self.import_plugin(arg, consider_entry_points=True)
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 867, in import_plugin
    raise ImportError(
  File "/home/pawamoy/data/dev/griffe/.venv/lib/python3.12/site-packages/_pytest/config/__init__.py", line 865, in import_plugin
    __import__(importspec)
ImportError: Error importing plugin "vscode_pytest": No module named 'vscode_pytest'

Without the vscode_pytest plugin:
% .venv/bin/python -m pytest --collect-only --config-file=config/pytest.ini
========================================================================================= test session starts =========================================================================================
platform linux -- Python 3.12.1, pytest-8.2.0, pluggy-1.5.0
Using --randomly-seed=153736517
rootdir: /home/pawamoy/data/dev/griffe/config
configfile: pytest.ini
plugins: cov-5.0.0, randomly-3.15.0, xdist-3.6.1
collected 777 items
... (truncated)
===== 777 tests collected in 2.97s =====

Any idea why the process hangs and consumes an entire CPU?
Could be related to https://github.com/microsoft/pylance-release/issues/4218 :shrug:

As mentioned in the discussion, I isolated the issue. It only happens when my pytest config file is in a subdirectory.
This works fine:
    "python.testing.pytestArgs": [
        "--config-file=pytest.ini"
    ],

While this consumes a CPU and never finishes:
    "python.testing.pytestArgs": [
        "--config-file=config/pytest.ini"
    ],

Hello! Thanks for this detailed bug report, I will investigate. Could you include your logs from the python output channel? For your logs, can you first set your log level to trace via theDeveloper: set log level command in the command palette then rerun the tests. I am curious what point in the process it gets stuck at and if the logs.
Also are you running the command yourself from the root of the repo right?
Finally are you able to see the same behavior for an arbitrary test- ie if you just write a pytest test which always passes and run with the config arg do you get the same behavior?
Sorry for all the questions! Thanks

Thanks a lot for your help!

Could you include your logs from the python output channel? For your logs, can you first set your log level to trace via theDeveloper: set log level command in the command palette then rerun the tests.

Sure. Note that I don't even run the tests, I only try to "collect" them (refreshing them in the Testing tab).
Trace logs:
2024-05-13 19:26:58.000 [info] Discover tests for workspace name: repro23411 - uri: /tmp/repro23411
2024-05-13 19:26:58.001 [info] Running discovery for pytest using the new test adapter.
2024-05-13 19:26:58.002 [info] All environment variables set for pytest discovery for workspace /tmp/repro23411: REDACTED

2024-05-13 19:26:58.028 [info] > ./.venv/bin/python -m pytest -p vscode_pytest --collect-only --config-file=config/pytest.ini
2024-05-13 19:26:58.029 [info] cwd: .
2024-05-13 19:26:58.457 [info] ============================= test session starts ==============================

2024-05-13 19:26:58.457 [info] platform linux -- Python 3.12.1, pytest-8.2.0, pluggy-1.5.0

2024-05-13 19:26:58.457 [info] rootdir: /tmp/repro23411/config
configfile: pytest.ini

2024-05-13 19:26:58.466 [info] collected 1 item

2024-05-13 19:26:58.467 [info]
<Dir repro23411>
  <Dir tests>
    <Module test_hello.py>
      <Function test_hello>

2024-05-13 19:27:36.196 [error] Subprocess exited unsuccessfully with exit code null and signal SIGTERM on workspace /tmp/repro23411.
2024-05-13 19:27:36.196 [error] Subprocess exited unsuccessfully with exit code null and signal SIGTERM on workspace /tmp/repro23411. Creating and sending error discovery payload
2024-05-13 19:27:36.196 [error] pytest test discovery error for workspace:  /tmp/repro23411

 The python test process was terminated before it could exit on its own, the process errored with: Code: null, Signal: SIGTERM for workspace /tmp/repro23411
2024-05-13 19:27:36.196 [info] ResultResolver EOT received for discovery.
2024-05-13 19:27:36.196 [info] Disposing data receiver for /tmp/repro23411 and deleting UUID; pytest discovery.

The logs hang at <Function test_hello>, then I interrupt the pytest process and the logs continue with Subprocess exited unsuccessfully etc.

Also are you running the command yourself from the root of the repo right?

No, I'm not running anything myself: it's vscode-python which runs the pytest process to collect the tests. I can trigger it by clicking on the "Refresh tests" button in the "Testing" tab.

Finally are you able to see the same behavior for an arbitrary test- ie if you just write a pytest test which always passes and run with the config arg do you get the same behavior?

Yep, I reproduced this in a clean, minimal project:
% tree -a -L 2
.
├── config
│   ├── .pytest_cache
│   └── pytest.ini
├── tests
│   ├── __pycache__
│   └── test_hello.py
├── .venv
│   ├── bin
│   ├── CACHEDIR.TAG
│   ├── .gitignore
│   ├── lib
│   ├── .lock
│   └── pyvenv.cfg
└── .vscode
    └── settings.json

9 directories, 7 files

% cat .vscode/settings.json
{
    "files.watcherExclude": {
        "**/.venv*/**": true,
        "**/venv*/**": true
    },
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "python.testing.pytestArgs": [
        "--config-file=config/pytest.ini"
    ]
}

% cat tests/test_hello.py
def test_hello():
    assert True

Hello! I have found the issue here. One thing I do to build the test tree seen in the test explorer is create nodes between session node (root) and test nodes. In this instance you can see in your logs that the root is within the config folder rootdir: /tmp/repro23411/config while the test files are inside the tests folder. Therefore the root dir is not a parent of the tests which was an assumption the plugin made. I will update it to check if the rootdir is not a parent and if so find the closest common path and making that the root (therefore making the tree look like below). Im putting together a fix but need a bit longer to create a test for this scenario.

That's awesome, thank you so much! Take all the time you need, no worries :smile:

Hi! This is merged and will be out on vscode insiders tomorrow so you can give it a try and let me know if it is fixed or if an issue persists.

Thank you very much! Will let you know :slightly_smiling_face:

Hello! Were you able to test to see if this is working?

I just installed the insiders version, and the issue still occurs :thinking:


How to use the keys in Verify : IInAppBillingVerifyPurchase example ?

Can anyone add a few sentences about how de keys 1-3 are used in the verify purchases process
at SecuringPurchases.md-android-security
This way a developer can self decide how the verify process / key(s) can be implemented; dynamic each startup, or at app installation or as constants.
I opened a question on Stackoverflow on this; https://stackoverflow.com/questions/48660351/where-are-xor-keys-used-for-during-purchase-veryfication-in-inappbillingplugin

It literally says it in the documentation:
The simplest and easiest (not necessarily the most secure) way is to do the following:

Take your public key and break into 3 parts
Run each through the helper XOR method: Plugin.InAppBilling.InAppBillingImplementation.InAppBillingSecurity.TransformString
Save each value out and put them in your app

The idea here is not to put your public key in your application. What you are doing is breaking your key apart into 3 parts. Then you are transforming the string with the method in there, which basically scrambles it via XOR for you.
With these three XORed parts of your public key then you put those into your source code.
Then when you pass in your Verify implementation i take the signed data and run in through my VerifyPurchase method which will validate that the keys from google match up and validate the keys that you have XORed.

Got it, no self madeup keys or dynamic once.
the keys are the same every build or install because they just encoded partial keys.
Thanks for the reply.

I'm new in xamarin.forms.
Could you please help me? Is this correct?:
I add the class in my andorid and ios app:
[assembly: Dependency(typeof(InAppBillingVerify))]
namespace MyApp.Droid.Dependencies
{
public class InAppBillingVerify : IInAppBillingVerifyPurchase
{
const string key1 = @"XOR_PublicKey_Part1";
const string key2 = @"XOR_PublicKey_Part2";
const string key3 = @"XOR_PublicKey_Part3";
public Task VerifyPurchase(string signedData, string signature, string productId = null, string transactionId = null)
{
#if Android
var key1Transform = Plugin.InAppBilling.InAppBillingImplementation.InAppBillingSecurity.TransformString(key1, 1);
var key2Transform = Plugin.InAppBilling.InAppBillingImplementation.InAppBillingSecurity.TransformString(key2, 2);
var key3Transform = Plugin.InAppBilling.InAppBillingImplementation.InAppBillingSecurity.TransformString(key3, 3);
return Task.FromResult(Plugin.InAppBilling.InAppBillingImplementation.InAppBillingSecurity.VerifyPurchase(key1Transform + key2Transform + key3Transform, signedData, signature));
#else
return Task.FromResult(true);
#endif
}
}
}
And add this line before PurchaseAsync method:
var verify = DependencyService.Get();

key1Transform

yes, you are correct

@jamesmontemagno just to be 100% sure,
if for example our public RSA key is "123456789" then then in your example the key1=@"123", key2=@"456", key3=@"789"?

I am genuinely confused by the sample code and the directions.
The sample code shows a line like this:
 const string key1 = @"XOR_PublicKey_Part1";

Question: Is the string here supposed to be the unencrypted 1st part of your public key?  Or is it supposed to be already encrypted? (i.e. the output of TransformString()) ??
If it is the unencrypted part of public key -- then if someone disassembles the MSIL, they'll SEE your public see in plain text.  So I would assume that these constants should be "pre-encrypted", rather than encrypting the plain-text keys run-time.
I would have thought we'd use the TransformString() "in DEBUG mode" to produce the XOR results, and then the developer would PASTE these results directly into these  3 constants.   Thus the plain text strings would never appear in your production code.   And so in production code, we'd just concat these three constants without further run-time encryption.  (just send them to VerifyPurchase method "as is").
And so I'm suspecting that I might be misunderstanding something crucial here.

Hello, please bare with me here lol...
I am trying to make a free version of an app I have uploaded as a paid app. In the free version I will show ads, and limit the number of records the app can record and recall.
The easiest way I can think of doing this, is to have an internal flag that specifies if it's the paid version or not, When the app starts, it checks this flag, and queries the API for the purchase state. if it's changed, the app sets the flag accordingly and continues on. The logic of the app would then use this flag to show or hide the ads, and potentially limit the number of DB records it would retrieve.
This way all I have to do is add a build target in my project, that uses a PRAGMA to define build targets Debug Paid / Debug free / Release Free / Release Paid. The only difference being that I have a pair of bool flags that are set to true, bIsPaid and bIsPaidVersion (which would bypass the checking logic). I can upload this as a new app in the Play Store, and define the in app purchases for that version.
Which key should I be using for this?
Should I use my Upload certificate? the App Signing certificate? or build a new key? I assume that if it's one of the prior, all I do is download the certificate, and save the key as a file with Base-64 encoding?
At that point I just chop it into 3 chunks and use your process above XORing it from the debug code to get the encoded key that I put into the code?
I am sorry if this is a particularly dense question, I just wanted to make sure that I am on the right track and especially don't want to wind up posting a build that has broken or faulty billing logic.
Cheers!

I would read through https://jamesmontemagno.github.io/InAppBillingPlugin/SecuringPurchases.html and all of the iOS and Android documentation. I provide the information to validate the purchases.

Excellent, thanks!


fix: upgrade to version 3.0.644

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign garethjevans
You can assign the PR to them by writing /assign @garethjevans in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test vault

gsm
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test gsm

vault
fbe325c02563749f83dbb63f658d64a92c92e661
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Analyzer needs a way to merge and flush metadata during incremental compilation

Analyzer uses its own Kernel metadata, and needs to carry this metadata with newly compiled libraries into the existing Component. We solved this issue in Analyzer for now, but it CFE thinks that this is something that should be implemented by CFE itself, this issue can be used for tracking.
We also need a way to flush portions of metadata that are associated with nodes in libraries that are invalidated, so to avoid memory leak.

The CFE integration work is suspended, so this will not be addressed.


Mouse cursor offset after turning on a HiDPI monitor

Godot version: 3.2.3 beta 1 ~ rc 5
OS/device including version:
MacBook Pro (Retina, 13-inch, Early 2015)
Intel Iris Graphics 6100 1536 MB
Issue description:
With the HiDPI monitor turned off (closed the MBP lid), I opened the Godot editor using only the non-HiDPI external monitor.
After turning on the HiDPI monitor (opening the lid), the appearance of Godot editor stays normal, but the mouse cursor seems to be using a HiDPI coordinate.
Also, after turning on the HiDPI monitor, drag the editor to the HiDPI monitor, and then drag it back, the seamless display scaling fails.
Steps to reproduce:

Use only the non-HiDPI monitor, turn off the HiDPI monitor
Open the Godot Editor
Turn on the HiDPI monitor

Minimal reproduction project: Not project related

Can't reproduce, turning HiDPI monitor on (or switching monitor to HiDPI mode) do affect editor scale (without DPI independent mode implemented in the renderer, unlikely this can be fixed), but mouse input is handled correctly. Maybe internal monitor is not sending display reconfiguration events for some reason.

It's strange that I can't reproduce the mouse cursor offset now either.
All I did is changing the display arrangement (move the HiDPI monitor from the left to the bottom of the LoDPI one). But I can't reproduce after I move it back.

Nevermind... I opened the 3.2.2 version of Godot after changing the arrangement. I can still reproduce it in RC 5.
Sorry for the misinformation.

I added a NSLog to the displays_arrangement_changed function, and it was called after turning on the HiDPI monitor.
Just to make sure, is the LoDPI monitor your primary display?
If I set the HiDPI monitor to be the primary display, the mouse input issue does not exist because the window is automatically moved to the HiDPI monitor after the monitor is turned on. My primary display is the LoDPI one, so the editor window stays on the LoDPI monitor, thus the mouse input offset.

Just to make sure, is the LoDPI monitor your primary display?

With LoDPI monitor set to primary I can reproduce it.


Modify UseConfiguration to support configuration section

I'd like to be able to store hosting configuration under a section in appsettings but UseConfiguration does not currently support this. e.g.
appsettings.json
{
    "Hosting": {
        "Urls": "https://*:5000"
    }
}

Program.cs
var config = new ConfigurationBuilder()
    .AddJsonFile("appsettings.json")
    .build();

var host = new WebHostBuilder()
    .UseConfiguration(config.GetSection("Hosting"))

I think the only change needed is this:
https://github.com/aspnet/Hosting/blob/873a0e7/src/Microsoft.AspNetCore.Hosting.Abstractions/HostingAbstractionsWebHostBuilderExtensions.cs#L24
    foreach (var setting in configuration.AsEnumerable())

To
    foreach (var setting in configuration.GetChildren())

That's a breaking change though.

How come? Existing apps will have a settings file looking like this:
{
  "Urls": "https://*:5000"
}

And with this test code:
var config = new ConfigurationBuilder()
    .AddJsonFile("appsettings.json")
    .Build();

foreach (var setting in config.AsEnumerable())
{
    Console.WriteLine($"Before - Key: {setting.Key}, Value: {setting.Value}");
}

foreach (var setting in config.GetChildren())
{
    Console.WriteLine($"After - Key: {setting.Key}, Value: {setting.Value}");
}

I get this output:
Before - Key: Urls, Value: https://*:5000
After - Key: Urls, Value: https://*:5000

So we get the same behaviour before and after change. The UseConfiguration method has argument of type IConfiguration so we're not needing to change the method signature from IConfigurationRoot to IConfiguration.

Actually this is a dupe of #839.


Feature Request

Can we add links from the sample READMEs to the live demo?

I was under the impression we already did this: https://github.com/GoogleChrome/samples/blob/gh-pages/array-includes-es7/README.md
Are there samples missing the live links?

Yup; it's not enforced, but the starter template README.md includes a link with placeholders that can be replaced with the actual URLs.


The avatar doesn't show image

Laravel Version: 5.5.*
Voyager Version: ^1.0
PHP Version: 7.1.3
Database Driver & Version: MySQL

Description:
I have followed all the instruction on the internet already but none of them can solve.

php artisan storage:link
change the APP_URL: http://localhost:8000 to http://<IP_ADDRESS>:8000

Could you please propose any alternative solution to this issue?
Steps To Reproduce:

Hi! Can you tell href of image?

As @ArtemMolotov has requested, please share the URL for your site (I'm guessing http://localhost:8000/admin/) and the URL/href for the image that's broken.

Here's my URL for my site: http://<IP_ADDRESS>:8000/admin

@hourdev Can you open image if you delete /public from image href?

go to config/filesystem.php and check if the public url is same as this one.
'public' => [
            'driver' => 'local',
            'root' => storage_path('app/public'),
            'url' => env('APP_URL').'/storage',
            'visibility' => 'public',
        ],```

@ArtemMolotov that works if i delete /public

@simoebenhida already tried but nth has changed

can i see your public url on config/filesystem.php and your variable APP_ENV on .env

@simoebenhida

yes on your filesystem.php public array replace 'public' => 'url' with this
'url' => env('APP_URL').'/storage', and it will work

still doesn't work

can i see the new filesystem.php changements

yes remove public from  'local' => 'url' too

or is better to remove it you dont need url on your local driver its already called on public driver.

still doesn't work

yes. already removed, but doesn't work

did you already run php artisan config:cache by any chance ?

didn't.. haha
now, it is working. thanks a lot for your help!

i meet the same question and i did all you said,however it still doesn't work

albeit this is closed, people are still having an issue. the solution for me was to remove the symlink in the public folder, then ensure the URL was correct in the .env file
APP_URL=http://your-app.test
As this constant is used in the config/filesystems.php file
'url' => env('APP_URL').'/storage',
the storage folder is appended the URL, so a forward slash is required before storage
so the url will be http://your-app.test/storage
Then navigate to the voyager dashboard and an alert will be there to fix the symlink, once clicked it worked for me.

'disks' => [
    'local' => [
        'driver' => 'local',
        'root' => storage_path('app'),
        'url' => '/storage',
    ],

    'public' => [
        'driver' => 'local',
        'root' => storage_path('app/public'),
        'url' => env('APP_URL').'/storage',
        'visibility' => 'public',
    ],

    's3' => [
        'driver' => 's3',
        'key' => env('AWS_ACCESS_KEY_ID'),
        'secret' => env('AWS_SECRET_ACCESS_KEY'),
        'region' => env('AWS_DEFAULT_REGION'),
        'bucket' => env('AWS_BUCKET'),
        'url' => env('AWS_URL'),
    ],

],

Dose not working please help

After deleting the public/storage folder run the command
php artisan storage:link
php artisan config:cache
It works for me .
@prasathkarnan

php artisan storage:link
php artisan config:cache
re-run the server

It worked for me. Thank you @arshomashohag


renamed file, included name space and added in project file.

have you merged this code ? did you find any issue ?

There was 2 pull request with same changes. So I closed this one since our discussions has been on the other one.
Will do the review on the weekend when I have time.


Ribbon grey doesn't have the correct color

Feature Request
Problem description
I have noticed that the grey colored ribbon inherits the brown color. You can view the color at this class ".ui.ribbon.label:after" on key "border-right-color: inherit".
Proposed solution
You can replace the brown color by this color #a9a9a9
MVP
https://codesandbox.io/s/v333v58193

Please post CSS related issue in the main repo: https://github.com/Semantic-Org/Semantic-UI

OK sorry :)


request for forecasting scenario in model builder

Do you want to add this "vote" to the epic? https://github.com/dotnet/machinelearning-modelbuilder/issues/609

Referenced this bug in the epic.


wasm-builder stalls build

While working (mostly cargo check) on polkadot I've stumbled on a problem where the kusama-runtime (only it) build hangs. According to cargo build -vv kusama-runtime starts building in the very start and the waits for the lock on build directory.
Here is the excerpt
[kusama-runtime 0.8.25]     Blocking waiting for file lock on package cache
[rococo-v1-runtime 0.8.25]     Blocking waiting for file lock on package cache
[polkadot-test-runtime 0.8.25]     Blocking waiting for file lock on package cache
[polkadot-runtime 0.8.25]     Blocking waiting for file lock on package cache
[westend-runtime 0.8.25]     Blocking waiting for file lock on package cache
[kusama-runtime 0.8.25]     Blocking waiting for file lock on build directory

Apparently, it never actually releases this lock. Removing wbuild and wbuild-runner didn't help and has lead to inclusion failures. Removing locks across the target directory didn't help as well, but probably I missed the right one.
cargo clean saved the day, but it's really annoying to wait for the rebuild.

Is this reproducible?

just got that the second time
here is my current workflow in detail: i do cargo check --all --tests a lot (doing many changes across codebase), and when I get the first error, I ^C the build. I suspect that it is related.
Meanwhile I tried to do
find ./target -iname '.cargo-lock' -exec rm {} \;

to remove all the locks and it helps.


Stopping criterion for test_mosi.py

Hi,
In 'test_mosi.py', there is no exit criterion for the while loop. When does it stop then?
Thanks,
VR

@vandana-rajan, feel free to add one ;), this is a reimplementation of the original theano code (now theano is deprecated)


rules_* modules broken with Bazel 8.0.0rc8

The following modules are broken with<EMAIL_ADDRESS>(Updated Dec 9):
BCR Bazel Compatibility Test:  https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/103
<EMAIL_ADDRESS>Maintainers:  @ted-xie, @ahumesky

<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets with bzlmod
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets with bzlmod
<EMAIL_ADDRESS>- :windows: Windows - Verify build targets with bzlmod

<EMAIL_ADDRESS>Maintainers:  @bazelbuild/bcr-maintainers

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets with bzlmod
<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets with bzlmod on MacOS
<EMAIL_ADDRESS>- :windows: Windows - Verify build targets with bzlmod on Windows

<EMAIL_ADDRESS>Maintainers:  @lalten

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 22.04 LTS -

<EMAIL_ADDRESS>Maintainers:  @keith

<EMAIL_ADDRESS>- :darwin: macOS - Run test module

<EMAIL_ADDRESS>Maintainers:  @srikrsna-buf

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @matts1

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module
<EMAIL_ADDRESS>- :windows: Windows - Run test module

<EMAIL_ADDRESS>Maintainers:  @kczulko

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @pjk25

<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets (macos)
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets (ubuntu2004)

<EMAIL_ADDRESS>Maintainers:  @sgammon

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Build test module
<EMAIL_ADDRESS>- :darwin: macOS - Build test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Build test module

<EMAIL_ADDRESS>Maintainers:  @avdv, @aherrmann

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Verify build targets
<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets
<EMAIL_ADDRESS>- :darwin: macOS arm64 - Verify build targets
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets

<EMAIL_ADDRESS>Maintainers:  @luispadron

<EMAIL_ADDRESS>- :darwin: macOS arm64 - Verify Build targets on macOS with Bazel 6
<EMAIL_ADDRESS>- :darwin: macOS arm64 - Verify Build targets on macOS with Bazel 7

<EMAIL_ADDRESS>Maintainers:  @EdSchouten

<EMAIL_ADDRESS>- :centos: CentOS 7 - Run example test module
<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run example test module
<EMAIL_ADDRESS>- :darwin: macOS - Run example test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run example test module

<EMAIL_ADDRESS>Maintainers:  @Bencodes, @restingbull, @nkoroste

<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets

<EMAIL_ADDRESS>Maintainers:  @benradf, @aherrmann

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 22.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @alexeagle, @thesayyn

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module
<EMAIL_ADDRESS>- :darwin: macOS - Run test module

<EMAIL_ADDRESS>Maintainers:  @opicaud

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module
<EMAIL_ADDRESS>- :windows: Windows - Run test module

<EMAIL_ADDRESS>Maintainers:  @oxidase

<EMAIL_ADDRESS>- :debian: Debian 11 Bullseye (OpenJDK 17, gcc 10.2.1) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @aaliddell

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Verify build targets
<EMAIL_ADDRESS>- :darwin: macOS - Verify build targets
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Verify build targets
<EMAIL_ADDRESS>- :windows: Windows - Verify build targets

<EMAIL_ADDRESS>Maintainers:  @jvolkman

<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS arm64 - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module
<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS arm64 - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @avdv, @aherrmann

<EMAIL_ADDRESS>- :windows: Windows - Run test module

<EMAIL_ADDRESS>Maintainers:  @jmmv

<EMAIL_ADDRESS>- :centos: CentOS 7 - Run test module
<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run test module
<EMAIL_ADDRESS>- :darwin: macOS - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run test module

<EMAIL_ADDRESS>Maintainers:  @cgrindel

<EMAIL_ADDRESS>- :darwin: macOS - Run test module

<EMAIL_ADDRESS>Maintainers:  @chickenandpork

<EMAIL_ADDRESS>- :ubuntu: Ubuntu 22.04 LTS - Run linux crosstool tests

<EMAIL_ADDRESS>Maintainers:  @aherrmann

<EMAIL_ADDRESS>- :darwin: macOS - Run test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 22.04 LTS - Run test module

FYI: rules_contest has been fixed - the failure was due to the flag flip of --incompatible_disallow_empty_glob.

rules_ruby are fixed in 0.14.1, the issue was usage of --incompatible_remote_results_ignore_disk in tests.

rules_wasm fixed: https://github.com/bazelbuild/bazel-central-registry/pull/3268.
Filed https://github.com/bazelbuild/bazel/issues/24499 to discuss a better solution, but was able to just duplicate some  as a workaround. The breaking change stems from https://github.com/bazelbuild/bazel/commit/27487cf11f61eb23108f8df129dc1a00ee1a4370 which causes the patch tool for http_archive to always receive a -p option, even when patch_args is empty. Is that an issue for anybody else? Or was that just because of my abuse of patch_tool.

<EMAIL_ADDRESS>Maintainers: @EdSchouten

<EMAIL_ADDRESS>- :centos: CentOS 7 - Run example test module
<EMAIL_ADDRESS>- :debian: Debian 10 Buster (OpenJDK 11, gcc 8.3.0) - Run example test module
<EMAIL_ADDRESS>- :darwin: macOS - Run example test module
<EMAIL_ADDRESS>- :ubuntu: Ubuntu 20.04 LTS - Run example test module

It looks like all of these breakages are caused by jsonnet, not rules_jsonnet. Unfortunately, I am not able to make able to make contributions to that repository directly. Sorry!
Once these build failures are addressed on the jsonnet side, I'd be more than happy to cut a new release of rules_jsonnet that depends on it.

@EdSchouten Yes, jsonnet is also identified in https://github.com/bazelbuild/bazel-central-registry/issues/3056
@mortenmj Can you help fixing this since you contributed the initial BCR module.

rules_sh, rules_nixpkgs and rules_haskell all fail with the same error:
	File "/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/2bbac50a5364a2d14c5e3065383ed7e2/external/rules_sh+/sh/posix.bzl", line 11, column 55, in <toplevel>
		load("@bazel_tools//tools/cpp:lib_cc_configure.bzl", "get_cpu_value")
Error: file '@bazel_tools//tools/cpp:lib_cc_configure.bzl' does not contain symbol 'get_cpu_value'

We were relying on this macro, but apparently it has been removed and the one in rules_cc is private. We are going to vendor a copy of this macro into our rules to solve this, but maybe others are also having this issue and copying this code around seems not very maintainable. WDYT?

@avdv I think we could expose this in https://github.com/bazelbuild/rules_cc/blob/8395ec0172270f3bf92cd7b06c9b5b3f1f679e88/cc/toolchains/toolchain_config_utils.bzl#L22
Sent https://github.com/bazelbuild/rules_cc/pull/283

rules_flex fix: https://github.com/bazelbuild/bazel-central-registry/pull/3285

rules_Synology will take a few days to fix: I butchered the bcr template and I’m afk 3 days. I can’t reproduce the failure but have a fix for a guess of the cause into v0.0.3

After some templating issues, #3330 brings in v0.1.1 (via chickenandpork/rules_synology#176) which might have a fix for rules_synology -- unfortunately, I cannot repro, so I'm guessing based on the error message.

@meteorcloudy can we pass --check_direct_dependencies=off in this CI job? in my case it's a bcr module where that as an error is checked in to the .bazelrc, so it's a false positive https://buildkite.com/bazel/bcr-bazel-compatibility-test/builds/72#019367c7-9404-453f-9c57-66b13aca10d9

@meteorcloudy what would be a procedure to remove<EMAIL_ADDRESS>from this check? I don't plan to add support for Bazel >=8 to the package


Grammar issue/typo in "Windows Sybsystem for Linux" section in whats-new-windows-10-2021.md

There seems to be a typo in Section Windows Subsystem for Linux:

Windows Subsystem for Linux (WSL) is be available in-box.

Should be either is available or will be available?

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

ID: a25d0f32-d5a9-0a30-21f2-3ae1beaaf3c1
Version Independent ID: a25d0f32-d5a9-0a30-21f2-3ae1beaaf3c1
Content: What's new in Windows 10 Enterprise LTSC 2021 - What's new in Windows
Content Source: windows/whats-new/ltsc/whats-new-windows-10-2021.md
Product: w10
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

![Screenshot_20211025_170330_com sec android app sbrowser~2](https://user-images.githubusercontent.com/94048360/143272886-747472db-e09d-4b37-b787-5e4c84cea491.jpg)

@cuiwc You are welcome to fix the typo by editing the article here: https://github.com/MicrosoftDocs/windows-itpro-docs/blob/public/windows/whats-new/ltsc/whats-new-windows-10-2021.md
The article is going to be updated by independent contributors otherwise.
Thanks.

Thanks, @e0i .
I'd be happy to submit a PR if I know for sure which statement, "is available" or "will be available", holds true for this topic. Unfortunately I don't have the answer, and actually that's why I came across this issue in the document when I try to look for WSL support in Windows 10 LTSC 2021.
Anyway, I don't prefer picking one randomly, hope someone from Microsoft would help clarify that.
Thanks
Wenchao


integration-cli: add missing err check

Signed-off-by: Antonio Murdaca<EMAIL_ADDRESS>

@runcom I think commit message looks like controversial to code(even if it's not). Maybe something about dockerCmd

@LK4D4 damn I was going to add it but thought not to lol

@LK4D4 updated

LGTM

LGTM


Feature/postcode

added new biuitils.jar to libs
updated IntegrationSpec to account for PostCode being returned
added full postcode to the sample.csv file

I have 1 failed test.

[info] - should check if elasticsearch analyzers works *** FAILED ***
[info]   java.lang.RuntimeException: error while parsing data from elastic: {}

LGTM.


Create an application/service in the new environment and push configuration to GitOps repository

Is your task related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Add e2e test script for - https://github.com/redhat-developer/kam/tree/master/docs/journey/day2#create-an-applicationservice-in-the-new-environment and https://github.com/redhat-developer/kam/tree/master/docs/journey/day2#commit-and-push-configuration-to-gitops-repoository
Additional context

/area testing


How to run/are there any updates to this?

Hi creators,
Thank you so much for your work. As someone with disabilities myself, I have recently run into so many problems that are exactly addressed by your tool.
I know it was already a bit of time ago, but I wanted to ask if

there are any newer versions, or other work being done on this or other similar projects?
and
Do you have a how-to to show me how to run it myself (either locally, or host a web version for my own private use)??

I'd really really appreciate it, or any other leads you have!
(or any other suggestions for transcribing some medical appointment recordings I have - I can't afford to pay lots of money for the transcriptions/I would like to do it myself, and I also don't feel comfortable using any of the "free" services out there, as it is my sensitive medical data on the recordings!!)
Sincerely,
Jon

Hi Jon,
Thanks for your interest in our project.
We made this project in a hackathon and have used AssemblyAI API for the transcription purpose.
This link contains a video of the demonstration - https://devpost.com/software/vid2text
About Assembly AI - https://www.assemblyai.com/
P.S. - We have not developed the model ourselves and using the free version of the API, so you might want to consider about the sensitive medical data on the recordings. However AssemblyAI data policies should be favourable in your case.
Regards,
Aditya


Fix redirect warnings

Brakeman detected the following vulnerabilities.
Confidence: High
Category: Redirect
Check: Redirect
Message: Possible unprotected redirect
Code: redirect_to("#{shib_login_url}?#{shib_callback_url}&#{"entityID=#{Identifier.by_scheme_name("shibboleth", "Org").where(:identifiable => Org.where(:id => shib_params["shib-ds"][:org_id])).first.value}"}")
File: app/controllers/orgs_controller.rb
Line: 126

Confidence: High
Category: Redirect
Check: Redirect
Message: Possible unprotected redirect
Code: redirect_to(Plan.deep_copy(Plan.find(params[:id])), :notice => success_message(Plan.deep_copy(Plan.find(params[:id])), _("copied")))
File: app/controllers/plans_controller.rb
Line: 364

See the following for possible solutions: https://brakemanscanner.org/docs/warning_types/redirect/

I've inspected the first redirect and I'm confident it's not unprotected.
The shib_login_url comes from the request's URL plus /Shibboleth/SSO/ and the shib_callback_url and the only user-input data is used to select a relevant organisation from the db's IDP url (and is in the querystring of the redirect)
We also used to have it in our config/brakeman.ignore, but the line number has changed.

the 2nd redirect should also be protected.
The user-supplied credentials here is the params[:id] and the redirect occurs after the authorization check.
It was also in the existing ignore file but the line had moved.

👍 Cool. thanks for investigating. Looks like we just need to update that brakeman.ignore file then


Debug Console does not appear when using internalConsole

Environment data

VS Code version: 1.34.0 (1.34.0)
Extension version (available under the Extensions sidebar): 2019.5.17059
OS and version: macOS 10.14.5
Python version (& distribution if applicable, e.g. Anaconda): Python 3.7.3 Homebrew
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): virtualenv
Relevant/affected Python packages and their versions: N/A

Expected behaviour
When running a debug configuration with "console": "internalConsole", the Panel should appear (if it's not already toggled on), and the current tab of the Panel should switch to DEBUG CONSOLE (if it's not already the current tab).
In other words, the behaviour should be the equivalent of the behaviour when "console": "integratedTerminal", which does show the Panel if it's not already shown, as does set the current tab to TERMINAL.
Actual behaviour
When running a debug configuration with "console": "internalConsole", the Panel is not shown (if it's not already toggled on), and the current tab of the Panel is not  switched to DEBUG CONSOLE (if it's not already the current tab).
Steps to reproduce:

Open launch.json by clicking on the cog in the top right of the Debug tab in the Side Bar
Add the following debug configuration to launch.json:

{
    "name": "Python: Current File (Internal Console)",
    "type": "python",
    "request": "launch",
    "program": "${file}",
    "console": "internalConsole"
},

Set the current debug configuration to this new Python: Current File (Internal Console) configuration.
Start Debugging (or Start Without Debugging) any Python script.
If the Panel is not currently shown, it does not appear, and if the current tab of the Panel is not DEBUG CONSOLE, it is not switched to DEBUG CONSOLE.

Thanks for letting us know about this, @dhthompson. To reproduce the problem I created a simple project with a single file in it:
print('hello!')

I also set up my launch.json like this:
{
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal"
        },
        {
            "name": "Python: Current File (internal console)",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "internalConsole"
        }
    ]
}

I ran the debugger with both those configs and it ran correctly both ways.  However, the panel behavior went much as you described it.
When using the internal console:

with no panel open, no panel popped up
with one of the panels open, it did not switch to any other panel
setting a breakpoint did not change the behavior
after running, the "Debug Console" pane showed the expected output

When using the integrated terminal:

with no panel open, the "Terminal" panel opened, where the debugger command was run
with one of the panels open, it always switched to the "Terminal" panel

Then I added "internalConsoleOptions": "openOnSessionStart" to my workspace settings.json.  After that, running with the internal console would open the "Debug Console" panel, like you wanted.
Give that a try and let us know if it doesn't work for you.  In the meantime I'm going to close the issue.
Thanks again!

Weirdly, adding "internalConsoleOptions": "openOnSessionStart" to my workspace settings.json as you suggest didn't quite work for me. The first time I ran the code the debug console appeared. But then I closed it, ran the code again, and this time it didn't reappear. Additionally, I'm getting the "Problem" that "internalConsoleOptions" is an "Unknown configuration setting".
However, if I simply add "internalConsoleOptions": "openOnSessionStart" to the relevant debug configuration in my launch.json file, the behaviour is exactly as I want it (the same as the integrated terminal).
So, in short: in order to get "console": "internalConsole" to behave the same way as "console": "integratedTerminal", you also need to set "internalConsoleOptions": "openOnSessionStart" in the relevant debug configuration in your launch.json file.
Thanks for your help!

I'm glad we got to the right answer in the end! :)


Apply require-jsdoc

What this PR does / why we need it?
Apply require-jsdoc
*Note: This pr is draft. After we finish discussing the js-doc rules, I will start to add docs!
Any background context you want to provide?
Currently, in the typescript-eslint we have used, I think the document suggests to use another plugin(jsdoc/require-jsdoc)

I added some options for jsdoc.
'jsdoc/require-jsdoc': [
      'error',
      {
        contexts: ['MethodDefinition:not([accessibility="private"])'], <-- this option is for not requiring a comment for the `private` methods
        require: {
          ClassDeclaration: true, <-- this option is for requiring a comment for `class` declaration
        },
        checkConstructors: false, <-- this option is for not requiring a comment for `consturctor`
      },
],

[x]  api/ - dc7303
[x]  core/client - dc7303
[x]  document/change + checkpoint - hackerwins
[x]  document/json - soeun
[x]  document/key + operation: ppeeou
[x]  document/proxy + time + document.ts - soeun
[x]  util -soeun

Please feel free to comment on the jsdoc rules!
What are the relevant tickets?

Fixes #118
Checklist

[x] Added relevant tests or not required
[x] Didn't break anything

@mojosoeun Thanks for the contribution. I have one question.
I thought errors would occur in CI after putting this rule. Is there any reason it doesn't happen?

@hackerwins hmm in my view, It seems that this eslint's --fix option make CI passed 🤔

@mojosoeun Is it okay if I comment on the api/ and core/client packages?

@dc7303 sure thanks!

@mojosoeun Could I comment on the document/key + operation ??

@ppeeou sure thank you do much!

Thank you. It is finally over. 🍻


adding merging for helm defaults args and --args, adding tillernamspace and kubecontext to helmdefaults

this pul request adds tillernamespace and kubecontext to helmdefaults also added merging of args capability.
made it possible if more people want to add key defaults they can add field to helmdefaults and add arg tag so merger can append to args

Made changes. Let me know if others are needed as well. Thanks.


Update base images reference page

Connects-to: #1902
Dynamically generate content from api v6/device_type endpoint
Change-type: patch
Signed-off-by: Trong Nghia Nguyen<EMAIL_ADDRESS>

Please make sure to read the CONTRIBUTING document before opening the PR for relevant information on contributing to the documentation. Thanks!

@thgreasi @vipulgupta2048 I updated all your comments, can you please check them again?

hey @thgreasi @vipulgupta2048, can you please check this PR again?

@nghiant2710 for the changes suggested above^^

@balena-ci rebase

@balena-ci rebase

@vipulgupta2048, I rebased it again, should be good now.