Allow to retrieve root applications from API

There is a feature missing from the PANOS API. While you can easily retrieve all applications and all applications group, you cannot retrieve root applications.
This means that if you want to check if "Jira" is a valid application, you 'd think you can't because you would only be able to retrieve :

jira-base
jira-downloading
jira-editing
jira-posting
jira-uploading

But Jira is a valid application, which contains all 5 above-mentioned applications.

Should be able to get the container app from the Predefined object instantiated in a PanDevice
from panos.firewall import Firewall

fw = Firewall( .... )
fw.predefined.refreshall_applications()
fw.predefined.application_container_objects['jira'].applications

Worth noting that that is just a list of strings of the names though. To get the object properties of each you'd need to grab them with the application method of the Predefined object.
# Not sure if this is the easiest/best way to do this, but it does work
for app in fw.predefined.application_container_objects['jira'].applications:
    fw.predefined.application(app)

This only gives me the applications mentioned above, but not "jira"...


The expression is not callable

TypeScript Version:  3.9.5 and Nightly

Search Terms: The expression is not callable
Code
interface A {
    write(chunk: any, cb?: (error: Error | null | undefined) => void): boolean;
    write(chunk: any, encoding: string, cb?: (error: Error | null | undefined) => void): boolean;
}

interface B {
    write(chunk: string | Uint8Array, callback?: (err: Error) => void): boolean;
    write(chunk: string | Uint8Array, encoding: string, callback?: (err: Error) => void): boolean;
}

function a_b(param: A | B){
    param.write("");
}

Expected behavior:
No error
Actual behavior:
Error: The expression is not callable
Playground Link: Link
Related Issues:

And this works:

interface A {
    write(chunk: any, cb?: (error: Error | null | undefined) => void): boolean;
    write(chunk: any, encoding: string, cb?: (error: Error | null | undefined) => void): boolean;
}

interface B {
    write(chunk: string | Uint8Array, callback?: (err: Error) => void): boolean;
    //write(chunk: string | Uint8Array, encoding: string, callback?: (err: Error) => void): boolean;
}

function a_b(param: A | B){
    param.write("");
}

Only certain kinds of call signatures can be merged into a callable property in a union, and this isn't one of them

Why not?
Call signature of the first write function of A and the first write function of B are not equal but for a write("that's a string") there are a match. If i remove the second write function of B, the error is gone.

There should be no error.
But you're right, its a "Design Limitation"


After following the configuration and setup process it is unclear how to add new routes/views

I tried adding new routes but they are still being intercepted by express default routing. Perhaps, you have answered my issue in your post Isomorphic React Apps with React-Engine where you say:

"Notice how the first render method is called with a / prefix in the view name. That is key to the react-engine’s MAGIC. Behind the scenes, react-engine uses a custom express View to intercept view names and if they start with a / then it first runs the react-router and then renders the component that react router spits out or if there is no / then it just renders the view file."

However, I believe, you did not specify this in the readme nor the examples. Furthermore, it would be nice to explain how we can add more routes. People like me that are just starting to learn react won't find it easy.
Note: I did follow the examples at react-router but for some reason the only way to make it work was using express routing and I dont think this was the way it was meant to work or am I getting everything wrong?
Thank you!
EDIT:
This is what I am doing to add new routes (with react-router) and views (.jsx thanks to react-engine), please correct me if I am wrong:
If we want to add a new view, lets say users.jsx and route it to path: /users

Add the following code to the express engine index.js file (in the case of your examples, it could be called server.js):

app.get('/users', function(req, res) {
  res.render(req.url, {
    title: 'Users page',
    name: 'Frank'
  });
});

Then, add the route to the routes.jsx file as follows:

 <Route path='/' handler={App}>
     <Router.DefaultRoute name='index' handler={Index} />
     <Route name='users' path='/users' handler={Users} />
 </Route>

Is this correct?
Is there a way to avoid having to add app.get('/users'.......){}?

@gixty: yes, you can reshare the route info between react-router and express. I used this snippet and it seems to work fine. https://github.com/rackt/react-router/issues/885

@samsel Forgive my piggybacking on this question. But if I:
Remove all react routes from server file and just put this instead:
app.use(function(req, res) {
  res.render(req.url, {});
});

and then in my routes.jsx define all my routes like:
<Route path='/' handler={App}>
    <DefaultRoute name='account' handler={Account} />
    <Route path="profile/:id" handler={Profile}/>
    <NotFoundRoute handler={NotFound}/>
</Route>

It seems to work fine for all routes (although I can't access ":id" param in my Profile component.)
So, is this method fine or do I lose something?
And how do I access :id route param in my component?
Thanks

@asadm how are you trying to get access to that :id currently?

@Dindaleon closing this now.


BackGround and Butten can surpport GIF?

Is it can be done?

It supports apng and you can convert gifs to apng files.


AlterOpLayout modifies input module inplace (and other issues)

https://discuss.tvm.apache.org/t/check-failed-axes-defined-static-cast-int-axes-size-ndim-dimension-mismatch/9887
This seems a recurring issue. A Relay pass shouldn't change the input mod inplace.

Other related issues

https://github.com/apache/tvm/pull/8143
https://discuss.tvm.apache.org/t/frontend-onnx-fail-to-compile-an-onnx-model-at-opt-level-3/9926

#6624 is an old issue that was worked around by #8143

One more bug fixed in https://github.com/apache/tvm/pull/8669

I'm not aware of other outstanding issues now.


Add Russian Translation

url
https://ayuprogrammers.github.io/trust/
fork
https://github.com/AYuProgrammers/trust

Ack, someone else sent in a Russian translation yesterday! It's the one I currently have linked to from the main page: https://likzet.github.io/trust/
However, I do like your translation better, since you got a nice handwritten font that works with Cyrillic! What do you think we should do? Do you want to send a PR to https://github.com/likzet/trust to include your handwritten font? Or: I could share your translation on my Twitter? I don't want your hard work to go to waste!

My translation is better. and i think no matter who send it first.
I don't need promotions and money.
If they want to take my font, let them take all the text with him, because his text very bad.
With one condition, no advertising on the main page.

As another person who was late with Russian localization, I wouldn't say it is bad :)
But you guys can merge it to get the best result, no doubts

I was only an hour late. And don't tell me that his machine translation is better than mine.
This man did nothing in fact, I don't need his help. But he is unable even to make the font, and puts his username on the main page, that even the author does not did.

I agree, that name on the front it's kinda immodestly (but seems like all translations now have it, so probably it was added by Nicky). And some phrases are translated too literally. And font, of cause :)
But youк translation is not perfect either: different names for characters in the game and in the sand mode, rough phrases, line breaks. There was smth else, don't remember...
Well, imho it's better to create a forum page or sort of and let people suggest/vote the best phrases for translations.

In Russian language the endings of words usually changes a lot in text, so do not pay attention to it, the only place where is not the same, a Простак/Простачок, its for purpose, second variant less aggressive and more suitable to the description, rather than a name.
"rough phrases" - thats to convey a desired message. Otherwise its too bland..
"line breaks" - long words, I know.


[STORM-1170] Fix the producer alive issue in DisruptorQueueTest

Looks good to me +1

LGTM. +1.

+1 @zhuoliu  thanks for fixing this


Scan Radius

I see people talking about a scan radius. However, I cannot find an option for this. Instead the scan just keeps going further away from the original location and the original location is never re-scanned. I may just be missing something though, in which case could someone inform me how to set the scan radius?

The settings are on the opening page. Scroll down


Duplicated information in the variables object

Describe the bug
Sometimes when variables are fetched from the Data Index, there is duplicated information in the response.
Expected behavior
I'd expect simply:
"variables": {
  "workflowdata": {
    "myKey": "myValue",
    "mantra": "Serverless Workflow is awesome!",
    "greeting": "Hello World"
  }
}

Actual behavior
If you fetch the variables, you'll get:
"variables": {
  "workflowdata": {
    "myKey": "myValue",
    "mantra": "Serverless Workflow is awesome!",
    "greeting": "Hello World"
  },
  "workflowdata.mantra": "Serverless Workflow is awesome!",
  "workflowdata.greeting": "Hello World"
}

See that mantra and greeting are duplicated.
How to Reproduce?
Take the Hello World workflow as an example and execute it with additional inputs, for instance:
{
    "myKey": "myValue"
}

Output of uname -a or ver
No response
Output of java -version
No response
GraalVM version (if different from Java)
No response
Kogito version or git rev (or at least Quarkus version if you are using Kogito via Quarkus platform BOM)
No response
Build tool (ie. output of mvnw --version or gradlew --version)
No response
Additional information
No response

In addition to the problem described, internal variables should not be published


add collaborations page under "about" menu tab

https://www.pombase.org/about/collaborations

@manulera  we can add Genestorian to this page!

I've added the Collaborations link in the About menu.


Update the module to use the new module api and some other fixes

Use the new module api
Use Storyblok's index entries instead of dedicated "home" entry

This PR contains some major refactoring please review and test carfully.
Todo

[ ] Update vue-storefront to the latest version
[ ] Update theme to latest version
[ ] Update tests if necessary

https://forum.vuestorefront.io/t/problem-with-url-mappingfallback-and-404/406/5
If this issue has indeed been resolved, these changes should now work properly as that was the isuue I was running into.


Explain how to import local modules recursively

First, I want to say thank you very much for writing this package. I am using this package so well.
This PR supplements how to import local modules recursively without modifying codebases.
Background
In importmap-rails, it support functionality to import all files in a specific folder by using pin_all_from.
For example, If you want to import all javascript files under app/javascript/src you can write as below:
# config/importmap.rb
pin_all_from 'app/javascript/src', under: 'src', to: 'src'

But, this package's README does not explains how to do it. And it seems lack this feature.
What does this PR do?
I added additional explanation of how to import local modules recursively like pin_all_from, as I explained above.
I have wondered which project I contribute between bolt-import and this package. But i have no experience with contributing django-plugin and I don't know how to contribute to bolt, too. So, I made decision to explaining trick without modifying codebase.
class ImportArguments(TypedDict):
    under: str
    to: str

def import_recursive(**kwargs: Unpack[ImportArguments]):
    root_dir = settings.BASE_DIR
    source_dir: str = str(root_dir / kwargs['under'])
    source_files = glob(f"{source_dir}/**/*.js", recursive=True)

    importmap_dict = {}
    for source_file in source_files:
        source_module = source_file.split('static/')[-1]
        target_module = source_module.replace(source_dir, kwargs['to']).replace(".js", "")

        importmap_dict[target_module] = static(source_module)

    return importmap_dict

Implementing import_recursive function is not much difficult and useful trick.
If there are people who want to use SPA framework without building backend/frontend separately, this trick would be very helpful.
Links

You can take a look how I use: https://github.com/kodingwarrior/memedex-backend/blob/main/jinja.py#L53-L61
Also, you can setup auto completion by jsconfig.json: https://github.com/kodingwarrior/memedex-backend/blob/main/jsconfig.json

Hey @malkoG — thanks for your patience! Just wanted to let you know that I've seen this. I'm most likely going to "archive" this Django package and focus on the Bolt iteration, and there's a couple big changes I'm envisioning in getting that to a 1.0. I will definitely keep this in mind for when I get to that part. (Regardless of what happens, I'll keep this package and code up and available so people can continue to use it or fork it if they want.)


how do "make shadec" work in windows

since cmd has no make, i tried make shaderc in cygwin, bx, fcpp, glslang, glsl-optimizer, spirv-opt, spirv-crosss, all can be generated, but when generating shaderc, failed when link
here is the error
$ make shaderc
make[1]: Entering directory '/cygdrive/e/bkaradzic/bgfx/.build/projects/gmake-mingw-gcc'
==== Building bx (release64) ====
==== Building fcpp (release64) ====
==== Building glslang (release64) ====
==== Building glsl-optimizer (release64) ====
==== Building spirv-opt (release64) ====
==== Building spirv-cross (release64) ====
==== Building shaderc (release64) ====
Linking shaderc
../../win64_mingw-gcc/bin/libglsl-optimizerRelease.a(glcpp-parse.o): In function yyparse': /cygdrive/e/bkaradzic/bgfx/.build/projects/gmake-mingw-gcc/y.tab.c:1705: undefined reference to yylex'
../../win64_mingw-gcc/bin/libglsl-optimizerRelease.a(pp.o): In function `glcpp_preprocess':
/cygdrive/e/bkaradzic/bgfx/.build/projects/gmake-mingw-gcc/../../../3rdparty/glsl-optimizer/src/glsl/glcpp/pp.c:227: undefined reference te'
collect2: error: ld returned 1 exit status
make[2]: *** [shaderc.make:308: ../../win64_mingw-gcc/bin/shadercRelease.exe] Error 1
make[1]: *** [Makefile:77: shaderc] Error 2
make[1]: Leaving directory '/cygdrive/e/bkaradzic/bgfx/.build/projects/gmake-mingw-gcc'
make: *** [makefile:282: shaderc] Error 2

Cygwin is not supported.
See prerequisites for Windows: https://bkaradzic.github.io/bgfx/build.html#windows

prerequisites in the build doc is not enough, lack of at least x86_64-w64-mingw32-gcc.exe; FYI, i installed "mingw-w64-install.exe" and run make shaderc succesfully, so maybe the build doc can be updated~

Toolchain is expected prerequisites to compile code. Prerequisites are more things that are not commonly understood as needed.

prerequisites in the build doc is not enough, lack of at least x86_64-w64-mingw32-gcc.exe; FYI, i installed "mingw-w64-install.exe" and run make shaderc succesfully, so maybe the build doc can be updated~

For those who are having issues, using MinGW from here + Windows' CMD seemed to work.


Multi Support Not Working?

Hey there!
For a few months now, my plugin hasn't been able to use Multi-Action support. I dumbed this down to an error on my side, but after extreme debugging, I couldn't get it to work.
I went ahead & forked the latest, current branch of the Counter plugin, & can't seem to get any logs or any of the actions to work with-in a Multi-Action.
Could you take a look & let me know if I'm missing something, or if this is indeed a bug?
Thanks!

Multi-actions should work, and are enabled by default, but I don't recall if I've actually tested them, so I'll take a look.
Which version of the API are you using?

Not sure if you're talking about the StreamDeck version? If so, 5.0+. Also tested on the latest 5.3 Beta release.
As for this library, I forked the current version back in mid December, with some custom changes, for logging & learning the package.
I'm not getting any logs with the latest release. I've went ahead & attached some console logs from the December fork, as Multi-Action semi-worked...
I asked around & it appears that actions inside the Multi-Action shouldn't have coordinates?  I went ahead & attached Elgato's Manifest.json, located under ~/Library/Application Support/com.elgato.StreamDeck/ProfilesV2, & then one of your profiles.
Let me know if there's anything else you need!
ConsoleLog.txt
Exmaple_Manifest.txt

Hey, @emorydunn!
Just wanted to check in & see if you were able to dig into this. Again, if you need anything else, I can provide more info!
Thanks!

Hi @SENTINELITE Thank you for your patience! I finally found to time to do some Stream Deck updates (both the library and my own plugin) and it looks like you were right about the coordinates, marking them as optional seems to have solved the issue.
I just pushed an update to the main branch which should get multi-actions working. Let me know if it does the trick.

Hey, @emorydunn.
That's done the trick! Thanks for taking a look! 😀


[tracking] Minimal refresh of Solo5 public APIs

The Solo5 public APIs (see solo5.h) have evolved over the course of the project and suffer from various issues, including but not limited to:

Type confusion (eg. use of int rather than size_t)
Lack of const types for read-only parameters
Under-specified failure cases
Difference of opinion between target implementations (eg. virtio vs ukvm multi-sector block operations)

With the various different ports and targets progressing we need to do a minimal refresh of the APIs sooner rather than later to both ease the work on new ports/targets and avoid technical debt. This will require breaking changes to the APIs, however the intent is to keep the changes minimal as opposed to doing a full redesign of the APIs at this point.
This issue tracks the work in progress and PRs (including downstream changes in MirageOS). The changes will require new OPAM releases of Solo5 and MirageOS mid-layers the progress of which will also be tracked here.

Solo5 changes are in #201. Work in progress branches for MirageOS mid-layers are:

https://github.com/mato/ocaml-freestanding/tree/solo5-api-refresh
https://github.com/mato/mirage-solo5/tree/solo5-api-refresh
https://github.com/mato/mirage-block-solo5/tree/solo5-api-refresh
https://github.com/mato/mirage-bootvar-solo5/tree/solo5-api-refresh
https://github.com/mato/mirage-console-solo5/tree/solo5-api-refresh
https://github.com/mato/mirage-net-solo5/tree/solo5-api-refresh

These branches may be rebased, I will create PRs for them later.
/cc @hannesm This should address your Console concerns.

This is completed on the Solo5 side by #245, closing.


Connections

This is still pretty untidy but I thought I would push it for discussion.
It adds a connection status to the store, separate to the latest value for a PV.
It also pulls out the action of connecting into a wrapper component. I think that wrapper should pass an NType plus a connection state into each component but at the moment it passes a string.
I updated the simulator a bit to add a PV that periodically disconnects. We should really extend it further so we can get out alarm status etc.
Comments welcome @TimGuiteDiamond @talwrii

It's difficult to balance heavy refactoring with writing tests... I'm not sure how much it's worth writing lots of tests before we are happy with APIs.

I think that this approach makes sense for the PV connection, as it is simply wrapping the components with some particular data.
It seems to me that this is different from the CopyWrapper in that it does not actually add any html code to the final DOM. The copy wrapper will add a div and a span and we want this to be reflected in the final DOM output. Therefore, perhaps it makes more sense to keep it as a pure component.
This would lead to a standalone readback looking like, for example:
const standaloneReadback = (props) => (
    <div>
        <CopyWrapper pv={props.pv}>
            <Readback pv={props.pv} />
        </CopyWrapper>
    </div>
)

and a connecting it:
export const connectedStandaloneReadback = connectionWrapper(standaloneReadback)

This seems relatively clean to me - pure components expect a normative type and render themselves appropriately, regardless of where they sit in the hierarchy etc.

This is interesting. I had come to the conclusion that we needed higher-order compnents (see here) but I don't think that's actually the case. What Tim describes is just a container component. I think in our cases we can use container components so I will look at refactoring to use them.

After a bit more thinking I'm not sure it's possible to do anything in Tim's example that changes the props being passed down. As long as all the props are passed through to the child component (as should be the case in the CopyWrapper) it looks like it should work fine, although I've still got a TypeScript error I don't understand.

I'm going to merge this, we can fix any problems we find later!


hyphen:auto can cause unexpected character wrapping

Description
The use of hyphen:auto in .spectrum-Menu-itemDescription is causing text to wrap where it would otherwise get enough space to be displayed.
See -> https://jira.corp.adobe.com/browse/CCEX-114347
https://github.com/adobe/spectrum-css/blob/956a066a845fbb14ae0af3c19c64667ee99dc985/components/menu/index.css#L607
Steps to reproduce
Please follow instruction from CCEX bug above using "French" locale
Expected behavior
No hyphen char break should be imposed to item list
Screenshots

Environment

Version of the impacted component(s):
Browser(s) and OS(s):

Additional context

Thanks @yloubry! We're tracking this in Jira here: https://jira.corp.adobe.com/browse/CSS-799 - it's slated to be worked on in our next sprint which begins on Monday, June 17

@yloubry Does the popover where this is occurring have a set width?

I believe it does yes. But not sure. I only notice that this CSS when active was creating the issue mentioned in this bug


reload option is not working as stated in documents

In the documents, it says that if reload parameter is given as a string, it will reload the given state and all child states. However, it reloads all parents states as well and causes unintended flickers in the page.
I use this in html, it is repeated for all workspaces:
ui-sref="app.workspace.feeds({name : workspace.name})" ui-sref-opts="{reload: 'workspace'}"

States are defined like this:
.state('app.workspace', {
	abstract	: true,
	templateUrl	: 'modules/workspace/workspace.html'
})
.state('app.workspace.feeds', {
	url			: "/workspace/:name",
	templateUrl : "modules/workspace/feeds.html"
})
.state('other child states', {})

I have tried different values for reload option like:
* 'app.workspace'
* 'app.workspace.feeds'
* 'workspace.feeds'
* 'workspace'

But none of them works as expected. In my application, I want the workspace state and controller to be reloaded every time when a different workspace link is clicked to load workspace details. Without reload option, it will load the workspace controller for once and it won't be reloaded when another workspace is selected and will show the same page for all workspaces. I have to use reload. But it reloads parents states as well.

A method that force reloads the current state. All resolves are re-resolved, controllers reinstantiated, and events re-fired.

Sounds like its working to me. It does reload the current state (in your usage its reload:true) but that means all states get reloaded

It seems that you didn't read my comment properly. I don't want all states to be reloaded. I just want the app.workspace state to be reloaded with its child states. But even if I use reload : 'app.workspace it reloads all these states including the parent app state and it causes flickers on the page.
Probably state name in reload is relative rather than absolute and I cannot reach the parent state.
I solved this problem by moving /workspace/:name url part to parent state. It reloads the app.workspace when parameter changes

Your issue says its not working as stated in documents but it is. The docs say:

A method that force reloads the current state. All resolves are re-resolved, controllers reinstantiated, and events re-fired.

And that is what is happening.

As you see in my code, I don't use reload function. I use transitionTo in html. And in the documentation it says:

reload (v0.2.5) - {boolean=false|string=|object=}, If true will force transition even if the state or params have not changed, aka a reload of the same state. It differs from reloadOnSearch because you'd use this when you want to force a reload when everything is the same, including search params. if String, then will reload the state with the name given in reload, and any children. if Object, then a stateObj is expected, will reload the state found in stateObj, and any children.

From that explanation if reload is given as a string (state name) then it should only reload that state and its children. It shouldn't reload parent states and shouldn't re-execute parent controllers. Otherwise it would be no different than reload:true.
What do you say about that?

Can you paste your code into a plnkr showing it not working please?

I couldn't reproduce it in plnkr. Probably the problem was in my code.


setup-environment.sh isn't using python3.10 or higher even if it is available in PATH while creating PAG binary

Describe the bug
While trying to create binary for the PAG, I get into errors. When I run "setup-environment.sh" in debug mode (bash -x), I see that it usages default Python version on the instance (python 3.9 in case of Amazon Linux 2023) even if a newer python version (3.11) is available in PATH.
Here is the error I am getting when I run the PAG binary:
[ec2-user@ip-172-31-30-166 porting-advisor-for-graviton]$ ./dist/porting-advisor-linux-x86_64 sample-projects/java-samples
Traceback (most recent call last):
  File "porting-advisor.py", line 23, in <module>
  File "advisor/__init__.py", line 26, in main
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "advisor/main.py", line 28, in <module>
ModuleNotFoundError: No module named 'advisor.reports.report_factory'
[28175] Failed to execute script 'porting-advisor' due to unhandled exception!
[ec2-user@ip-172-31-30-166 porting-advisor-for-graviton]$

Expected behavior
setup-environment.sh should automatically identify python executable with version 3.10 or higher available in PATH or throw error if not found.
Steps to Reproduce
Steps to reproduce the behavior:

Launch AL2023 instance using AMI ami-06ca3ca175f37dd66 in us-east-1 region.
SSH to the instance and execute below commands

sudo yum install python3.11 python3-pip java-11-amazon-corretto maven git -y
pip3 install pip --upgrade
git clone https://github.com/aws/porting-advisor-for-graviton.git
cd porting-advisor-for-graviton
./build.sh
./dist/porting-advisor-linux-x86_64

The built binary throws error related to advisor while trying to execute it.
And when I try to install advisor, it also throws error:

AssertionError: Multiple .egg-info directories found

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: amazon Linux 2023
latest
Processor Architecture:  x86/x64 and ARM64
Python Version: NA
Java Version (if applicable): NA

Additional context
Add any other context about the problem here.

Thanks for reaching out @santosh-at-github. We will review the issue and your PR and merge it after doing some tests and checks.

Fixed by #33 . Thank you very much for your contribution!


fix: correct nested sets, they were missing another sets object

Description

Related Issue
Fixes #25
Motivation and Context
Incorrect object structure.
How Has This Been Tested?
Locally tested with spectrum-tokens-css
Screenshots (if appropriate):
Before:
{
  value: '8px',
  filePath<EMAIL_ADDRESS>  isSource: true,
  original: { value: '8px' },
  name: 'spectrum-corner-radius-200-sets-spectrum-desktop',
  attributes: { sets: [ 'spectrum' ] },
  path: [ 'corner-radius-200', 'sets', 'spectrum', 'desktop' ]
}

After:
{
  value: '8px',
  filePath<EMAIL_ADDRESS>  isSource: true,
  original: { value: '8px' },
  name: 'spectrum-corner-radius-200-sets-spectrum-sets-desktop',
  attributes: { sets: [ 'spectrum', 'desktop' ] },
  path: [ 'corner-radius-200', 'sets', 'spectrum', 'sets', 'desktop' ]
}

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

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

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


ion-footer does not change ion-content's margin-bottom

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[x ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

If <ion-footer> content changes after a view is loaded, <ion-content>'s margin does not adjust to factor the change ending up with hidden content.
Expected behavior:

<ion-content>'s margin would change dynamically with the height of <ion-footer>.
Steps to reproduce:

Related code:
http://plnkr.co/edit/fvwbCIKdQGabMVwm6muk?p=preview

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Cordova CLI: 6.3.1
Gulp version:  CLI version 3.9.0
Gulp local:   Local version 3.9.0
Ionic Framework Version: 2.0.0-rc.3
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
Ionic App Scripts Version: 0.0.44
ios-deploy version: 1.8.6
ios-sim version: 5.0.1
OS: Mac OS X El Capitan
Node Version: v0.12.7
Xcode version: Xcode 8.1 Build version 8B62

Hi there. This is covered in the docs
You need to call resize on the content.
http://ionicframework.com/docs/v2/api/components/content/Content/#resize
http://plnkr.co/edit/UuHavx3pQ77MYOnQXjm7?p=preview

I tried that calling content.resize(); after toggling footer but nothing happens ...


Initial yarn add lottie-react-native command broke due to Electron dependency

When i run
yarn add<EMAIL_ADDRESS>The output contains the following warning:
warning<EMAIL_ADDRESS>this beta version of electron has been removed due to a security vulnerability. To get the latest beta, run 'npm install electron@beta'
And then fails on:
Error: Failed to find Electron v1.8.0 for darwin-x64 at https://github.com/electron/electron/releases/download/v1.8.0/electron-v1.8.0-darwin-x64.zip

Running
npm i --save<EMAIL_ADDRESS>Works fine and lets you install it btw :-)

@PimDeWitte Lottie has no electron dependencies. This must be coming from another package.


update landscape.yml

Hello
we are new here as a silver member, so I am not sure if I am right here with my request.
The listing is already shown under silver members with "Airlock".
Now we want to be listed in the category "Security & Compliance". How can we change this?
Thank you for your help
MG
Pre-submission checklist:
Please check each of these after submitting your pull request:

[n] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[y] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[y ] Does it follow the other guidelines from the new entries section?
[y] Have you added your SVG to hosted_logos and referenced it there?
[y] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[y] Does your project/product name match the text on the logo?
[y] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

@GernotBekk see https://github.com/cncf/landscape#new-entries

Thank you for your reply. So this means I cannot move our entry to security, although this is what we offer with the free solution?
I do not want to be mentioned twice, I just want to be listed in the correct category.


Make Error

Thank you for always doing great research and making it public.
I tried to follow 'getting started'. But I faced some errors.
When I did the following procedures
mkdir build && cd build
cmake ..
make -j

this error has occured
In file included from /home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_train_policy_cuda.cpp:171:
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_learner.h: In constructor ‘ARSLearner<ARSVecEnvironment>::ARSLearner(ARSVecEnvironment&, const ARSConfig&)’:
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_learner.h:42:83: error: class template argument deduction failed:
         worker_ = new Worker (tmpenv,  params_dim, policy_params, deltas_, config_);
                                                                                ^
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_learner.h:42:83: error: no matching function for call to ‘Worker()’
In file included from /home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_train_policy_cuda.cpp:169:
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_vectorized_worker.h:23:5: note: candidate: ‘template<class ARSVecEnvironment> Worker(ARSVecEnvironment&, int, const PolicyParams&, const std::vector<double>&, const ARSConfig&)-> Worker<ARSVecEnvironment>’
     Worker(ARSVecEnvironment& env, int params_dim, const PolicyParams& policy_params, const std::vector<double>& deltas, const ARSConfig& config)
     ^~~~~~
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_vectorized_worker.h:23:5: note:   template argument deduction/substitution failed:
In file included from /home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_train_policy_cuda.cpp:171:
/home/onsoulkang/tiny-differentiable-simulator/examples/ars/ars_learner.h:42:83: note:   candidate expects 5 arguments, 0 provided
         worker_ = new Worker (tmpenv,  params_dim, policy_params, deltas_, config_);
                                                                                ^
examples/ars/CMakeFiles/ars_train_policy_cuda.dir/build.make:75: recipe for target 'examples/ars/CMakeFiles/ars_train_policy_cuda.dir/ars_train_policy_cuda.cpp.o' failed
make[2]: *** [examples/ars/CMakeFiles/ars_train_policy_cuda.dir/ars_train_policy_cuda.cpp.o] Error 1
CMakeFiles/Makefile2:1390: recipe for target 'examples/ars/CMakeFiles/ars_train_policy_cuda.dir/all' failed
make[1]: *** [examples/ars/CMakeFiles/ars_train_policy_cuda.dir/all] Error 2
Makefile:145: recipe for target 'all' failed
make: *** [all] Error 2

I'm using Ubuntu 18.04, gcc 8.4.0, cmake 3.22.2.
Any help on how to fix this error would be appreciated.

Upgrading gcc to version 9 solved the problem.


Trigger regular bag ingest

What is this PR trying to achieve?
Add trigger every 15 minutes for test bag ingest

I don't think that module works (e.g., not all the variables used are defined).  Perhaps I should fix it.


Subtask/boas 193 refactor create scope

Describe your changes
refactor of 'create' scope:

first 7 steps (name, sector, subsec, geo info, regions, zoom and email) are now in the create/case scope
added a new scope: `create/applicant' that'll contain the steps for the applicant information
guards (to avoid inspector to access the form) and locals (to save the application id for resume) are still global

also includes:

refactor of the fixture for the items (section, regions and zoom level)
possible fix of the auth system

Issue ticket number and link
https://pins-ds.atlassian.net/browse/BOAS-193
Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[x] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

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

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

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

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

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

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

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

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

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


style tab component on page, docsy theme

This is a Feature Request
The new tab component, introduced with the docsy theme, has some extra shading in the background. Also the folders are very square and there is little or no margin around the component on the page.
What would you like to be added
Investigate if the tab component could be styled differently.
Would the component look better with rounded edges and less background shading?
Add margins around the component.
Comments
Previous tab component:

Current tab component:

/kind cleanup
/priority backlog

/area web-development

/assign

Related to issue #22024.

Updated the tabs shortcode to use Bootstrap library.
/close


oncoplot column barplot showing total mutations in all genes rather than just what is displayed in the oncoprint

First off thanks for this amazing tool! I really appreciate you sharing it with us.
I have a minor suggestion. What I expect from an oncoprint is:

row barplot: to show the total number of mutations in a gene per row for all displayed samples in the current oncorpint
column barplot: to display the number of genes mutated per sample from the geneset that is currently diplayed in the oncoprint

This is apparent from the ComplexHeatmap's examples:

But what I am seeing from the oncoplot function in maftools is that is displays the total number of mutations in all genes per sample regardless of the geneset on display in the current oncoprint

The row barplot seems to be doing what is it supposed to but the column barplot is not. Is it possible to add a parameter such that the oncoprint's column barplot only show the total number of mutations in the currently displayed genes?
Thanks!

Hi,
Thanks for using it and I am glad you find the tool useful.
Regarding the column bars, In earlier versions of maftools it was the case. Later I changed it since it makes sense to display mutation burden per tumor rather than the displayed pathway. You can see this in most of the TCGA landmark papers, which includes total tumor burden.
But I agree with your suggestion - I will make it as an argument.

Thanks so much! This tool is really awesome!
I had been doing a lot of what this tool does ad hoc using bits and pieces of code but to have something that is this robust and best of all has amazing documentation is quite rare. Congrats on your achievement!

Also, we are investigating frequently mutated pathways in say Ovarian Cancer and Homologous Recombination Deficiency  (HRD) genes and it would make perfect sense to just view the mutation burden in the pathways.

Yes, this is something I intend to do. Also splitting oncoplot according to pathways. But it might take some time :|

Hi,
I have pushed a commit to address the issues. Could you install it from GitHub and try. Please let me know if these fixes your requirements.
To limit the column bar graph to the genes included in the plot, run oncoplot with colbar_pathway = TRUE
#eg;
oncoplot(laml, colbar_pathway = TRUE, top = 10)

Hey thanks for this!
I am away until early next week but I will test as soon as I am back.

Looks like it's working. Thanks!

Hi,
looks like the latest version of maftools has revertedd back to showing the "total mutations" in the column barplot rather than the mutations in the current pathway?
Can the "colbar_pathway" option be re-implemented? I have a lot of plots I made using the old version and updating to the new version (maftools_2.0.10) would make it difficult to compare directly :(
Thanks!


Migrate FHIR Core to the latest FHIR SDK artifacts

Describe the feature request.
FHIR SDK artifacts with the latest changes from the 'master' branch (including a few extra un-merged PRs) have been published.
We need to upgrade and refactor FHIR Core to utilize them on main.
Additional context
The artifacts have been published under the following signatures

Common - org.smartregister:common:0.1.0-alpha05-preview-SNAPSHOT
Engine - org.smartregister:engine:0.1.0-beta04-preview5-SNAPSHOT
SDC - org.smartregister:data-capture:1.0.0-preview20-SNAPSHOT
Workflow - org.smartregister:workflow:0.1.0-alpha03-preview3-SNAPSHOT
Knowledge/IG - org.smartregister:knowledge:0.1.0-alpha02-preview-SNAPSHOT

The un-merged PRs included are:

https://github.com/opensrp/android-fhir/pull/11
https://github.com/google/android-fhir/pull/1669
https://github.com/opensrp/android-fhir/pull/9
https://github.com/google/android-fhir/pull/2178
https://github.com/opensrp/android-fhir/pull/10
https://github.com/google/android-fhir/pull/2230
https://github.com/google/android-fhir/pull/2262

Newer version includes

https://github.com/google/android-fhir/pull/2270

Acceptance criteria

[ ] Migrate common library
[ ] Migrate engine library
[ ] Migrate SDC library
[ ] Migrate Workflow library
[ ] Migrate Know/IG library

Please take note, we have new versions of the following artifacts:

Engine - 0.1.0-beta05-preview-SNAPSHOT
SDC - 1.0.0-preview21-SNAPSHOT
Workflow - 0.1.0-alpha03-preview4-SNAPSHOT

@ndegwamartin FHIR Engine 0.1.0 beta05 Pre-release includes a hapifhir core dependency updated to v6.0.22 which includes the math functions we require in FHIRPathEngine.
So we no longer have to include unmerged PR https://github.com/opensrp/android-fhir/pull/10 going forward

@ellykits please take note, we have new versions of the following artifacts:

Engine - 0.1.0-beta05-preview1-SNAPSHOT
SDC - 1.0.0-preview22-SNAPSHOT
Workflow - 0.1.0-alpha04-preview-SNAPSHOT
Knowledge/IG - 0.1.0-alpha03-preview-SNAPSHOT
Common - 0.1.0-alpha05-preview-SNAPSHOT

@ellykits please take note, here are the requested artifacts:

Engine - 0.1.0-beta05-preview1.1-SNAPSHOT
SDC - 1.0.0-preview22.1-SNAPSHOT
Workflow - 0.1.0-alpha04-preview1.1-SNAPSHOT
Knowledge/IG - 0.1.0-alpha03-preview1.1-SNAPSHOT
Common - 0.1.0-alpha05-preview1.1-SNAPSHOT

We have new versions of the following artifacts:
Engine - 0.1.0-beta05-preview3-SNAPSHOT

@ellykits please take note, new versions of the following artifacts are available
Engine - 0.1.0-beta05-preview7-SNAPSHOT
SDC - 1.1.0-preview-SNAPSHOT
Workflow - 0.1.0-alpha04-preview4-SNAPSHOT
Knowledge/IG -  0.1.0-alpha03-preview2-SNAPSHOT
Common - 0.1.0-alpha05-preview2-SNAPSHOT


Front end challenges

User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36.
I was performing the weather challenge in free code camp using chrome.Then i logged in to my account using firefox and then it just takes me back to the start even though it shows that i have completed challenges till random quote machine it just doesnt take me back to weather project. Here are some screenshots: also this is my account link: https://www.freecodecamp.com/en/jay-20

We recently changed how the next challenges are loaded. It needs save your position on challenge complete before the next challenge logic will work correctly.
Sorry for the inconvenience.
Happy Coding.


ESlint plugin doesn't seem to work

I installed this extension and then did a npx eslint --init choosing Javascript, React and Json. Then I restarted Visual Studio Code, but I don't see anything underlined red in my files. My project was built with Vite with a classic src folder.  Nothing is specified in the plugin page details so I kind of assume this is not the expected behavior. Do I need to add some more things in the the generated .eslintrc.json file or in my Visual Studio Code settings?

Never mind, this code was commented in my user settings:
"eslint.probe": [
        // "javascript",
        // "javascriptreact",
        // "typescript",
        // "typescriptreact"
    ],


Bug/SK-1040: Fixing numpy version with the MONAI package

Description

This bug is related to numpy version.

Need description! Why change numpy version? What issues is being raised with latest numpy?