Nodes overlap on each other

Hi, thanks for this useful library. Actually i'm experiencing an issue about overlapping nodes on each other. The images shown below. How can i solve this issue? i referred to the issue #2 but didn't find any solution.
This is my configuration for BaseGraphAdapter's algorithm:
val configuration = BuchheimWalkerConfiguration.Builder()                     .setSiblingSeparation(100)                     .setLevelSeparation(300)                     .setSubtreeSeparation(300)                     .setOrientation(BuchheimWalkerConfiguration.ORIENTATION_LEFT_RIGHT)                     .build()
 algorithm = BuchheimWalkerAlgorithm(configuration)

I've tried landscape mode or change values inside the configuration but none of them solved the issue.
Thanks

I've seen the problem in the sample app of this repository too. it can be used to reproduce the problem.

Thank you for bringing this to our attention. I tried to replicate your tree, but so far I couldn't find the problem. Can you or @SaeedZhiany  post some code or the changes I should do in our sample app where the issue can be seen.

I tested the sample app a few weeks ago, so the scenario might be a little different. I remember in the sample App I opened all nodes in the tree, then tried to close and reopen one of the nodes in level 3 (or 4) then I saw that its sibling node overlapped a piece of the mentioned node.

@DennisBlock
I tested the sample app a few weeks ago, so the scenario might be a little different. I remember in the sample App I opened all nodes in the tree, then tried to close and reopen one of the nodes in level 3 (or 4) then I saw that its sibling node overlapped a piece of the mentioned node.

From @asr1994's images, it seems the problem is occurring in level 3 of the tree, so it might the same problem I mentioned. please try it in the sample app, if you couldn't reproduce it, let me know, then I'll try to make a gif as soon as I can to show how the issue happens.

From @asr1994's images, it seems the problem is occurring in level 3 of the tree too, so it might the same problem I mentioned. please try it in the sample app, if you couldn't reproduce it, let me know, then I'll try to make a gif as soon as I can to show how the issue happens.

I added, removed and re-added nodes, but still no issue. If you could make a gif, it would be a great help!

Unfortunately, I couldn't reproduce it after many tests too. this is so weird to me. I'm pretty sure that I saw the problem in the sample app but I can't remember the scenario. sorry about that. as soon as I can reproduce it I'll inform you. meanwhile, @asr1994 can you create a simple repo that recreate your tree? no need to have the details, just the overall structure of your nodes, like width and height of the node container view.

Unfortunately, I couldn't reproduce it after many tests too. this is so weird to me. I'm pretty sure that I saw the problem in the sample app but I can't remember what is the scenario. sorry about that. as soon as I can reproduce it I'll inform you. meanwhile, @asr1994 can you create a simple repo that recreates your tree? no need to have the details, just the overall structure of your nodes, like width and height of the node container view.

It seems to be some weird corner issue. But nonetheless thanks for your help.
@asr1994 Just like @SaeedZhiany said, it would be great if you could create a sample with the issue.

@DennisBlock
Here is my creation method for the graph:
`private fun Graph.drawNode(parent: NodeModel?, node: NodeModel) {
    if (parent == null) {

        mGraph.addNode(Node(node))

    } else {

        mGraph.addEdge(Node(parent), Node(node))

    }

    if (node.hasChildren) {

        for (child in node.children!!) {

            if (child.hasChildren) {

                drawNode(node, child)

            } else {

                mGraph.addEdge(Node(node), Node(child))

            }

        }

    }

}`

`private fun Graph.drawNode(parent: NodeModel?, node: NodeModel) {
    if (parent == null) {

        mGraph.addNode(Node(node))

    } else {

        mGraph.addEdge(Node(parent), Node(node))

    }

    if (node.hasChildren) {

        for (child in node.children!!) {

            if (child.hasChildren) {

                drawNode(node, child)

            } else {

                mGraph.addEdge(Node(node), Node(child))

            }

        }

    }

}`

and this is my xml layout for each node of graph (using in custom adapter) :
`

<data>
    <variable
        name="node"
        type="co.tinab.farazindsp.models.settings.orgChart.Node" />
</data>

<androidx.cardview.widget.CardView
    android:layout_width="@dimen/_120sdp"
    android:layout_height="wrap_content"
    app:cardCornerRadius="5dp"
    app:contentPadding="@dimen/spacing_small"
    app:cardBackgroundColor="@android:color/white">

    <LinearLayout
        android:orientation="vertical"
        android:layout_width="match_parent"
        android:layout_height="wrap_content">

        <LinearLayout
            android:orientation="horizontal"
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
            android:gravity="center_horizontal">

            <co.tinab.farazindsp.components.tools.UserImageView
                android:layout_width="@dimen/_35sdp"
                android:layout_height="@dimen/_35sdp"
<EMAIL_ADDRESS>
            <co.tinab.farazindsp.components.tools.TextViewNormal
                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
<EMAIL_ADDRESS>                android:textColor="@android:color/black"
                android:textSize="@dimen/_12ssp"
                android:gravity="center_horizontal"
                android:layout_gravity="center_vertical"
                android:layout_marginStart="@dimen/spacing_small" />

        </LinearLayout>

        <co.tinab.farazindsp.components.tools.TextViewNormal
            android:layout_width="match_parent"
            android:layout_height="wrap_content"
<EMAIL_ADDRESS>            android:textColor="@android:color/black"
            android:textSize="@dimen/_10ssp"
            android:gravity="center"
            android:layout_marginTop="@dimen/spacing_small" />

    </LinearLayout>

</androidx.cardview.widget.CardView>

`
i hope it could help understand my issue better. Thanks

It seems to be some weird corner issue. But nonetheless thanks for your help.
@asr1994 Just like @SaeedZhiany said, it would be great if you could create a sample with the issue.

It seems to be some weird corner issue. But nonetheless thanks for your help.
@asr1994 Just like @SaeedZhiany said, it would be great if you could create a sample with the issue.

@DennisBlock
Here is my creation method for the graph:
`private fun Graph.drawNode(parent: NodeModel?, node: NodeModel) {
if (parent == null) {

    mGraph.addNode(Node(node))

} else {

    mGraph.addEdge(Node(parent), Node(node))

}

if (node.hasChildren) {

    for (child in node.children!!) {

        if (child.hasChildren) {

            drawNode(node, child)

        } else {

            mGraph.addEdge(Node(node), Node(child))

        }

    }

}

} private fun Graph.drawNode(parent: NodeModel?, node: NodeModel) {
if (parent == null) {

    mGraph.addNode(Node(node))

} else {

    mGraph.addEdge(Node(parent), Node(node))

}

if (node.hasChildren) {

    for (child in node.children!!) {

        if (child.hasChildren) {

            drawNode(node, child)

        } else {

            mGraph.addEdge(Node(node), Node(child))

        }

    }

}

}`
and this is my xml layout for each node of graph (using in custom adapter) :
`

<androidx.cardview.widget.CardView
android:layout_width="@dimen/_120sdp"
android:layout_height="wrap_content"
app:cardCornerRadius="5dp"
app:contentPadding="@dimen/spacing_small"
app:cardBackgroundColor="@android:color/white">
<LinearLayout
    android:orientation="vertical"
    android:layout_width="match_parent"
    android:layout_height="wrap_content">

    <LinearLayout
        android:orientation="horizontal"
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
        android:gravity="center_horizontal">

        <co.tinab.farazindsp.components.tools.UserImageView
            android:layout_width="@dimen/_35sdp"
            android:layout_height="@dimen/_35sdp"
<EMAIL_ADDRESS>
        <co.tinab.farazindsp.components.tools.TextViewNormal
            android:layout_width="wrap_content"
            android:layout_height="wrap_content"
<EMAIL_ADDRESS>            android:textColor="@android:color/black"
            android:textSize="@dimen/_12ssp"
            android:gravity="center_horizontal"
            android:layout_gravity="center_vertical"
            android:layout_marginStart="@dimen/spacing_small" />

    </LinearLayout>

    <co.tinab.farazindsp.components.tools.TextViewNormal
        android:layout_width="match_parent"
        android:layout_height="wrap_content"
<EMAIL_ADDRESS>        android:textColor="@android:color/black"
        android:textSize="@dimen/_10ssp"
        android:gravity="center"
        android:layout_marginTop="@dimen/spacing_small" />

</LinearLayout>

</androidx.cardview.widget.CardView>
`
i hope it could help understand my issue better. Thanks

Unfortunately your code does not help that much, as I cant't run it myself and I don't see anything fundamentaly wrong with it. I would need a runnable sample to debug.
One question though: Do you build you graph before or after adding it to the adapter? I ask because adding new nodes/edges starts the algorithm and there could be some values left from previous iterations which maybe produce these issues.

I can confirm this may happen sometimes, and will always appear with the same graph (but I lost the graphs). Although in my case it is not that severe -- the two nodes just slightly overlap with each other. But this is still not expected, as the nodes (in the same level) are not evenly spread.
In my case the nodes are top-down, and I'm using SugiyamaAlgorithm.
(I may update with the graph layout if I happen to see the problem again.)

Any updates on this issue?


Searching for SKU not redirecting to product detail page

PHP Version
8.0
Shopware Version
<IP_ADDRESS>
Expected behaviour
When searching via product number and it matches with a product, i should get redirected to the product detail page.
Actual behaviour
inconsistent results. Sometimes i get redirected to the fitting product detail page but sometimes it redirects me to the search result page, showing other products. Does this have to do with my indexer not being finished? (See issue: https://github.com/shopware/platform/issues/2795) or is this a different issue?
How to reproduce

See above.

If anyone needs a quick fix - in the above linked thread a plugin got posted:
https://store.shopware.com/leopa84423787994f/artikeldetailseite-bei-eindeutigem-nummer-match-in-suche.html
I don't know if it would be nice to integrate this into Shopware Core itself, but that is not my decision to make.


Rewrite macro spec without executing a shell command

Maybe fixes #6961
Let's see if CI fails like this. I'll try to re-run it a few times.
This is probably a workaround and we should investigate why it fails for this specific spec.

Test passed. Let's do some rebuilds and see how it goes.

@bcardiff We should also try this

This can be merged as is, the intent "Rewrite macro spec without executing a shell command" is good, green if it didn't fix some other errors


0.2.0a0: problem with build setuptools documentation

I,m trying to build setuptools documentation as man page.
setuoptools has project.toml file in its root directory however look slike sphinxcontrib-towncrier` has some difficulties with find that file.
[tkloczko@barrel setuptools-57.2.0]$ SETUPTOOLS_SCM_PRETEND_VERSION=57.2.0 /usr/bin/python3 setup.py build_sphinx -b man --build-dir build/sphinx                           running build_sphinx
Running Sphinx v4.1.2
loading intersphinx inventory from https://pypa-build.readthedocs.io/en/latest/objects.inv...
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from https://docs.python.org/2/objects.inv...
building [mo]: targets for 0 po files that are out of date
building [man]: all manpages
updating environment:
Extension error (sphinxcontrib.towncrier):
Handler <bound method TowncrierDraftEntriesEnvironmentCollector.get_outdated_docs of <sphinxcontrib.towncrier.TowncrierDraftEntriesEnvironmentCollector object at 0x7f399716ae80>> for event 'env-get-outdated' threw an exception (exception: [Errno 2] No such file or directory: '../pyproject.toml')
[tkloczko@barrel setuptools-57.2.0]$

It works for setuptools as proven by the docs site being published on RTD automatically. Just invoke Sphinx as they do.


Mm 29111 search bar and search results as fc

Summary

Refactored SearchResults and SearchBar component to functional components using TypeScript.
Disconnected both components from redux-store and simplified component structure.
Implemented new connected component Search which handles state updates and renders SearchResults (when not in ChannelHeader) and SearchBar.

Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/15852
Fixes https://github.com/mattermost/mattermost-server/issues/15854
Note to @nevyangelova: Please be mild! ✨

Hello @michelengelen,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

components/search_results/search_results.tsx: our webpack configuration currently prefers .js & .jsx over .ts & tsx files meaning that when I run these changes locally, search_results.jsx is being loaded instead of search_results.tsx, which is causing issues with loading search results. Are you seeing the same thing on your end? Can we remove search_results.jsx?

No, it does not cause any errors on my side. I just missed it, because Webstorm groups files with the same name, but different endings (.js & .ts and .jsx & .tsx), which is kinda nice, but sometimes leads to these cases.
I will remove it!

@nevyangelova I did provide some fixes for the comments you made on the PR. Could you re-check again?
Thanks for the great feedback so far!

search results component appears over the hint.

FIXED

Padding seems a bit more than on master

I did not change any styles. I could not notice any changes when comparing local, test-server and production.

Search results header appears on the popover and on master its not shown

I do not really know what you mean by that. Could you elaborate a bit? that would be really helpful! 🙇♂

Cursor moves out of the quotes when searching for phrases, with " "

FIXED! (that was a nasty bug 😓 )

/update-branch

kind reminder for @jgilliam17 to check for additional UX bugs 🎉

Thank you @michelengelen
Tested search and search results - looks good
Noticed one issue with exclude search terms
See screenshot
e.g. I searched for from:sysadmin -goldfinch
Expected for roughly all the posts to display in the search results except for 1st post on Town Square that contains goldfinch and maybe one more
Observed: - fails to return any results, excludes all when used as the only search option or in combination with from:

Thank you @michelengelen
Tested search and search results - looks good
Noticed one issue with exclude search terms
See screenshot
e.g. I searched for from:sysadmin -goldfinch
Expected for roughly all the posts to display in the search results except for 1st post on Town Square that contains goldfinch and maybe one more
Observed: - fails to return any results, excludes all when used as the only search option or in combination with from:

Does not seem to be a problem with my refactoring. i did not change anything on the submitting part. I will have a look anyways and come back to you with my findings!

Does not seem to be a problem with my refactoring. i did not change anything on the submitting part. I will have a look anyways and come back to you with my findings!

@michelengelen Thanks for checking! We can definitely address this separately if it's out of scope (I can create a follow up issue). I ran few search tests to check Search Results as style/padding was mentioned in previous comments, and noticed - wasn't producing results I expected.

@jgilliam17 I did check on local, test-server and production that using - behaves differently.
First of all: requests are the same on every environment: Status 200, request params are OK as well. The only difference is that the response is not correct on the test-server and on local. Any idea what can cause this?

I checked the system console and test-server search queries are using database search, Bleve and Elasticsearch are not enabled. I'd have to re-test and see if that makes a difference in using -.

Thanks @michelengelen
Re-tested - Looks good to merge.
Note: I enabled Bleve and - worked as expected, this must be a database search issue
For some reason I am now seeing an issue with from: it does not offer sysadmin as an option or even auto-complete when typing sys.  I'll log that separately, Ogi confirmed it's happening on his test server too unrelated to this PR.

@hmhealey kind reminder to review/approve. ✨

@hanzei I did already address all requested changes from @hmhealey and @calebroseland ... is there more to do atm?

Looks good now! Thanks for changing that

@michelengelen @jgilliam17 @hmhealey there are errors in the search logic:

Search is stuck on 'Searching...' even when results are present.
Search terms aren't updated on second click.
Search terms when clicked from rhs don't display the suggestions, for example clicking on 'from:' doesn't return a list of users.

Reverting this PR for now as we will need a deeper investigations to fix those issues. I don't know how we missed those during all of our testing but it's a learning mistake for our team. Sorry Michel!
Michel would you like to pair on this and talk about the potential fixes when you have some time?

@nevyangelova sure thing. Maybe we should discuss a bigger refactoring as well. I don't know how this could happen as well.


Potential issue of different versions of dependencies

In go.mod of both osmosis and cosmos-sdk, osmosis's using google/protobuf v1.30.0, cosmos-sdk's using v1.28.1. So we should find a way to check versions of those deps and generate them separately to avoid some potential issues.

Alex: so there should be an includes/google/protobuf/ subfolder structure here:
https://github.com/osmosis-labs/osmojs/tree/main/packages/osmojs/src/codegen/osmosis
and here:
https://github.com/osmosis-labs/osmojs/tree/main/packages/osmojs/src/codegen/cosmos
instead of a single one in the root


CMake issues demos/tools/tests

On my archlinux box the .so created is actually called SDL2_gpu - the Cmake wants to link demos/tools/tests to SDL_gpu though which obviously isn't found then.
[ 16%] Linking C shared library libSDL2_gpu.so
[ 18%] Linking C executable 3d-demo
/usr/bin/ld: cannot find -lSDL_gpu
Additionally the path to the .so isn't added to the linker flags for the demos/tools/tests makefiles so the linker still can't find it unless you add -L${SDL_gpu_SOURCE_DIR}/src to the respective TEST_LIBS/DEMO_LIBS in their cmakelists.txt

This should be fixed in a57a7bb2674cf6c7a668cb91003ee1556a661eea.  Can you verify?

Same issue on Linux (Fedora 25).
I suggest instead of specifying the linker paths and library directly supply the target name (sdl_gpu / sdl_gpu_shared) and CMake will figure out dependencies and paths for you.

Thanks!  That's what ended up happening in f68b0936214dd18659ddd473b4ad97940a387af3 when I ran into this issue again.


Missing execute permissions of kitodo scripts

Atm after unzip script permissions are 444 but should be 544.

Should be solved inside the zip file (which can preserve std permissions) IINM

Not in build kitodo step to be sure?


Added method onFail and try catch at doInBackground

This solved no callback problem when doInBackground generates an exception

No such corrections. Closed.

Verdade rsr, errei no merge


[question] Any idea why the loss function is computed for output_1 and output_2?

Hey,
It seems that the loss function is computed for output_1 and output_2.
This can be seen by setting verbose to 1 and seeing the keras traning output:
  7/100 [=>............................] - ETA: 1:06 - loss: 3659.3479 - output_1_loss: 2951.3269 - output_2_loss: 703.0701

As you can see there is output_1_loss and output_2_loss. This is also computed for validation and any extra metric I add. I get metric_name_output_1 and metric_name_output_2.
I would assume there are two output layers, but it seems like in the loss the function that all the information in yolov4 is already contained in one:
        truth_xywh = y_true[..., 0:4]
        truth_conf = y_true[..., 4:5]
        truth_prob = y_true[..., 5:]

        num_classes = truth_prob.shape[-1]

        pred_xywh = y_pred[..., 0:4]
        pred_conf = y_pred[..., 4:5]
        pred_prob = y_pred[..., 5:]

Those are the 3 outputs expected from YOLOv4
source: https://github.com/hhk7734/tensorflow-yolov4/blob/master/py_src/yolov4/tf/train.py#L71

If you use tiny, Yolo head returns 2 output.
https://github.com/hhk7734/tensorflow-yolov4/blob/be7b9305fcef1d1245948c26612c31f6d3212c5e/py_src/yolov4/model/head.py#L210
TF2 calls the loss function for each output.

If you use tiny, Yolo head returns 2 output.
https://github.com/hhk7734/tensorflow-yolov4/blob/be7b9305fcef1d1245948c26612c31f6d3212c5e/py_src/yolov4/model/head.py#L210
TF2 calls the loss function for each output.

@hhk7734 Thanks!
I gather L and M are medium and large?
And that output 1 is medium and output 2 is large?

@hhk7734 Thanks!
I gather L and M are medium and large?
And that output 1 is medium and output 2 is large?


Operator (organization) admin adds/edits an operation (facility) for their operator

Description:
As Gertrude, I want to be able to add or update a facility that belongs to my operator
Assumption: Gertrude is logged in with their BCeID account that's linked to their operator's Business BCeID
The prime admin's access request has already been approved by IRC
Includes user filling out forms and submitting request to register operation.
See https://www.figma.com/file/LsDmLDCdnJqI8UahyqvOD8/Registration-app?type=design&node-id=4-2&mode=design&t=lp8DwUm6T8XDYKso-0 for wireframes
Acceptance Criteria:
Given I am logged in to the Registration app with my Business BCeID account and I have been granted "admin" role for my operator
When I navigate to the Operation (facility) Details page
Then I can view the existing operations associated with my operator
And I can edit information about those operations
And I can add a new operation associated with my operator
Development Checklist:

[x] API endpoint/(s) to POST/PUT facility data for an operator
[ ] Implement front-end according to wireframes
[ ] External user sees confirmation page when registration request is submitted (indicates that the request has been submitted successfully, not that it has been approved/denied yet)
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

Hey team! Please add your planning poker estimate with Zenhub @andrea-williams @BCerki @dleard @JoshLarouche @Sepehr-Sobhani

Includes user filling out forms and submitting request to register operation.

@hannavovk, here's a video of what this ticket includes: https://www.loom.com/share/7495eecd5329421c952384a0e4e0c528
It does not include:

approval (you'll see status is pending for everything in the table)
anything to do with auth (right now the table shows every facility in the app regardless of who the user is)

@BCerki I'm not sure what you mean by "does not include registering an operation" - clicking "submit" is equal to submitting a request to register the operation under OBPS.
You may be thinking of the scenario of adding an operatOR? In that case we would need to first approver the creation of an operator and the prime admin person (this is one step), and then they would add an operation to that operator and submit it for registration.

As discussed with @BCerki, we will look at this together later in the week for approval.  The form has changed a lot since the video as a result of #15. We won't be able to submit the form (which is one of the AC) until the devops people add some mock data.

Amazing work @BCerki! Thank you!

@andrea-williams is this ticket still relevant or can we close? looks like its' from Reg 1.

it's ancient - closing it


Navigator fails invariant when tapping during a transition

Repro:

Open the Navigator example in the UIExplorer
Tap "Float in from right"
While the new scene is animating in, tap the screen
Red box in _handlePanResponderGrant

Fixed in 0686b0147


How to set an image instead of title in buttons?

Hello,
Is it really possible to set an image in buttons as the Readme demonstrates?
I saw that there is a property image for buttons, but I'm not sure what is expected as type (string which should be the path of the image file I guess?).
I looked at the source code to see what's going on and this line makes me think that the image property of buttons (the code seems to consider the field icon instead) is not initialised and is always nil.

@Slals There's no support for it in the JS and the ObjC. Have you worked on a fix yet?


Revert "Typemap cleanup"

Reverts mono/CppSharp#1802

@tritao Please read carefully.
While indeed the introduced bug caused unnoticed problems with #1802 (and which I know about now and will resolve separately). I wasn't really aware that we should run CppSharp.Parser.Gen in order to generate bindings for the project itself.
So after reverting this PR, I regenerated the project and run the tests, which failed to compile.
I then reverted all the PR created by myself, and again regenerated and tried to compile, with errors too.
Notice, my other PRs (other than this one trying to revert), had no changes on the diff.
So apparently, some older PR submitted by someone didn't know about running CppSharp.Parser.Gen to synchronize the project's bindings.
Now the good part is, most of the diffs in the generated bindings are just:

removed extra spacing for better syntax
generation of: #pragma warning disable CS9084 // Struct member returns 'this' or other instance members by reference
generation of a routine with callNativeDtor
some __instance are now marked as ref
SourceLocation has now a default constructor

Basically 5 is generating compilation errors:
CS8773: Feature 'parameterless struct constructors' is not available in C# 9.0. Please use language version 10.0 or greater
Summary:

accept this PR which will revert #1802 which I will rework out, now I aware of project's binding regeneration.
check changes which were introduces by older PR which hasn't generated the project's bindings.

Sorry for the inconvenience. I made a mistake, but looks like others have fallen for the very same one.

Alternatively, we would need to require C# 10.0 going forward.

Indeed this is what I am thinking about. Practically speaking C# 10.0 is really new.
Lets tag @Saalvage and we see if he has an opinion here.
By the way I located the part which needs fixing in this PR, it is solely related to Std.Map, should be a very simple fix.

As you like, I can close this PR then and submit a patch which fixes it, basically this typemap should be removed as it was in the first place in the CLI backend:
https://github.com/mono/CppSharp/blob/1327971e25ea298951f64864ad3bcdecf745ca0f/src/Generator/Types/Std/Stdlib.CSharp.cs#L415-L429
Commenting/removing this will fix the issue.


goToPage seems to break Coordinate conversion

My code looks something like this:
createOverlay: function (page, cX, cY, cH, cW, panToElement) {
        viewportBounds = viewerElement.viewport.imageToViewportRectangle(cX, cY, cW, cH);
        console.log(viewportBounds);
...

This works fine. If I add goToPage, however, I break the imageToViewportRectangle function (the values returned are the original values received as parameters by createOverlay).
It goes to the correct page, but all the following function calls return wrong values. Almost like the viewport stopped working.
createOverlay: function (page, cX, cY, cH, cW, panToElement) {
        viewerElement.goToPage(page);
        viewportBounds = viewerElement.viewport.imageToViewportRectangle(cX, cY, cW, cH);
        console.log(viewportBounds);
...

If anyone has any idea of what I'm doing wrong, I'd be greatly appreciated.
Thanks in advance.

I have since discovered a solution for this. After discussing this with some colleagues, they suggested me the following code:
if (viewerElement.isOpen()) {
            createOverlay(page, cX, cY, cH, cW, panToElement);
        } else {
            viewerElement.addHandler('open', function () {
                createOverlay(page, cX, cY, cH, cW, panToElement);
                viewerElement.removeAllHandlers('open');
            });
        }

This validation seems to have solved the problem.


Can't Deploy on Server

What is wrong?
remote:        npm ERR! code ELIFECYCLE remote:        npm ERR! errno 126 remote:        npm ERR<EMAIL_ADDRESS>postinstall: opencollective postinstall
remote:        npm ERR! Exit status 126
remote:        npm ERR!
remote:        npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
remote:        npm ERR! This is probably not a problem with npm. There is likely                                                 additional logging output above.
remote:
remote:        npm ERR! A complete log of this run can be found in:
remote:        npm ERR!     /tmp/npmcache.GFxab/_logs/2018-08-30T00_34_10_063Z-d  `
Where does it happen?
Can't deploy node js REST API on Heroku because of the issue above
How important is this (1-5)?
5
Thank you for great work, this npm package is simple and powerfull
Thank you for all developers who work on this package

Resolved https://github.com/BrainJS/brain.js/pull/270
Sorry about the failure.  I didn't realize the package was essentially an ad, removed with extreme prejudice.  Please let me know if there are any other issues.

It works !!
thank you Robert


Title animation

Updated tools version and added animation on the month title

Hey @chahinem, if you page through months really fast, the title is left in a state where it's not visible until you stop paging. You should be able to fix this by adding a start delay to the animation.

@chahinem Even with the update, I still get it animating while paging, and I don't think we want to add more delay. I'm not sure what to suggest to try next :disappointed:


[Bug Fix] toggle-transaction-filters button layout

GitHub Issue : #1910
Explanation of Bug Fix:
The layout of the TK Transaction Filter buttons has been impacted by the latest YNAB web release (see #1910).
Chrome is not respecting the display: flex; CSS on the #tk-toggle-transaction-filters element.

I have used injectCSS() to explicitly set display: flex; for this element.

It's no big deal because I'm just going to squash and merge but it looks like you might want to update your fork's master to clean up all that commit history on this PR.
Thanks for the fix!

Thanks Josh. I think I've sorted it (not got much experience with GitHub, so we'll see)


chore: bump quote4

This update removes the infamous "incompatible metavariable" error.

I searched for the usual (u := Level.zero) workarounds, but I couldn't find any (pointers welcome).  But I could simplify a bit of code using the recent assumeInstancesCommute and =Q features.

bors merge


Upgrade to hyper 1.0

Hi! Sorry for the late response and thank you for the suggestion. Did not know they have reached 1.0 so I will probably look into this very soon. Of course any and contributions are welcome :)

Hi, any updates?

Hey @DaniPopes. I havent gotten to it yet (been reading over the docs of the changes) but should be getting to it soon. If you would like to take up on updating hyper you are more than welcome to as well :)


Requirements

Hi @hiroharu-kato
Thanks for the code. I am testing it for my further research. Can you please provide the requirements.txt

My computer's settings:
Ubuntu 16.04 + cuda 8.0 + python 2.7
Remember to include CUDA_PATH=xxxxxxxx/cuda-8.0 in your ~/.bashrc. The CUDA_PATH is used for compiling chainer/cupy package.
virtual environment:
(N3MR) pip list:
backports.functools-lru-cache 1.5
chainer                       4.2.0
cloudpickle                   1.0.0
cupy                          4.2.0
cycler                        0.10.0
dask                          1.2.2
decorator                     4.4.0
fastrlock                     0.4
filelock                      3.0.10
kiwisolver                    1.1.0
matplotlib                    2.2.4
networkx                      2.2
neural-renderer               1.1.3
numpy                         1.16.3
Pillow                        6.0.0
pip                           19.1.1
protobuf                      3.7.1
pyparsing                     2.4.0
python-dateutil               2.8.0
pytz                          2019.1
PyWavelets                    1.0.3
scikit-image                  0.14.2
scipy                         1.2.1
setuptools                    41.0.1
six                           1.12.0
subprocess32                  3.5.3
toolz                         0.9.0
tqdm                          4.32.1
wheel                         0.33.4

Has this repo been tested with Cupy and chainer version 4.4.0 for CUDA 9.0. These were the minimum versions of cupy and chainer that I could install based on the cupy-cuda90==Version wheel installation process.
Or does it require Cupy and chainer version 4.2.0?


spanlogger: fix double logging of caller information

What this PR does:
This PR fixes an issue with the changes introduced in https://github.com/grafana/dskit/pull/547.
That PR added logging correct caller information for code that used SpanLogger, however, it would log both the correct caller as well as caller=spanlogger.go:xxx.
I incorrectly believed that github.com/go-kit/log would use the last value if multiple caller keys were logged for the same message. It turns out that is incorrect: if multiple duplicate keys are logged for the same message, both are included in the output.
The fix for this is to introduce a spanlogger.Caller that returns the correct caller information, ignoring any SpanLogger methods. It should be used in place of github.com/go-kit/log's Caller when creating the logger at application startup.
There is a small performance penalty (~1% additional latency for logging) when logging with spanlogger.Caller instead of Caller:
           │ SpanLoggerAwareCaller/with_go-kit's_Caller-10 │ SpanLoggerAwareCaller/with_dskit's_spanlogger.Caller-10 │
           │                    sec/op                     │              sec/op                vs base              │
output.txt                                     936.0n ± 1%                         945.1n ± 6%  +0.97% (p=0.015 n=6)

           │ SpanLoggerAwareCaller/with_go-kit's_Caller-10 │ SpanLoggerAwareCaller/with_dskit's_spanlogger.Caller-10 │
           │                     B/op                      │                  B/op                   vs base         │
output.txt                                      733.0 ± 1%                               735.0 ± 6%  ~ (p=0.143 n=6)

           │ SpanLoggerAwareCaller/with_go-kit's_Caller-10 │ SpanLoggerAwareCaller/with_dskit's_spanlogger.Caller-10 │
           │                   allocs/op                   │              allocs/op                vs base           │
output.txt                                      9.000 ± 0%                             9.000 ± 0%  ~ (p=1.000 n=6) ¹
¹ all samples are equal

This cost is only paid when a log line is actually logged, and not if the log line is filtered out (eg. if the log line is at debug level but the application is configured to emit info level and above, using spanlogger.Caller makes no difference).
This change also improves the performance of SpanLogger in general, as we no longer need to allocate a new spanLoggerAwareCaller for each instance. And the behaviour above when the log line is filtered also applies, which can be seen in the info_and_above_allowed/level.Debug benchmark below:
                                                               │ original.txt │             final.txt              │
                                                               │    sec/op    │   sec/op     vs base               │
SpanLoggerWithRealLogger/info_and_above_allowed/Log-10            1.941µ ± 1%   1.775µ ± 1%   -8.55% (p=0.002 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/level.Debug-10    570.3n ± 4%   161.8n ± 0%  -71.63% (p=0.002 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/DebugLog-10       2.865n ± 1%   2.911n ± 1%   +1.61% (p=0.006 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/Log-10                1.941µ ± 2%   1.769µ ± 1%   -8.86% (p=0.002 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/level.Debug-10        1.941µ ± 1%   2.656µ ± 3%  +36.84% (p=0.002 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/DebugLog-10           2.231µ ± 1%   2.029µ ± 0%   -9.03% (p=0.002 n=6)
geomean                                                           546.5n        446.9n       -18.23%

                                                               │  original.txt   │               final.txt                │
                                                               │      B/op       │     B/op       vs base                 │
SpanLoggerWithRealLogger/info_and_above_allowed/Log-10            1072.0 ± 21%       952.0 ± 34%  -11.19% (p=0.013 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/level.Debug-10     720.0 ±  0%       400.0 ±  0%  -44.44% (p=0.002 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/DebugLog-10        0.000 ±  0%       0.000 ±  0%        ~ (p=1.000 n=6) ¹
SpanLoggerWithRealLogger/all_levels_allowed/Log-10                1072.0 ± 21%       952.0 ± 16%  -11.19% (p=0.011 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/level.Debug-10       1.305Ki ±  0%     1.430Ki ±  0%   +9.58% (p=0.002 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/DebugLog-10          1.312Ki ±  0%     1.133Ki ±  0%  -13.69% (p=0.002 n=6)
geomean                                                                        ²                  -13.66%               ²
¹ all samples are equal
² summaries must be >0 to compute geomean

                                                               │ original.txt  │              final.txt              │
                                                               │   allocs/op   │ allocs/op   vs base                 │
SpanLoggerWithRealLogger/info_and_above_allowed/Log-10            15.00 ± 0%     11.00 ± 0%  -26.67% (p=0.002 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/level.Debug-10   10.000 ± 0%     5.000 ± 0%  -50.00% (p=0.002 n=6)
SpanLoggerWithRealLogger/info_and_above_allowed/DebugLog-10       0.000 ± 0%     0.000 ± 0%        ~ (p=1.000 n=6) ¹
SpanLoggerWithRealLogger/all_levels_allowed/Log-10                15.00 ± 0%     11.00 ± 0%  -26.67% (p=0.002 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/level.Debug-10        18.00 ± 0%     15.00 ± 0%  -16.67% (p=0.002 n=6)
SpanLoggerWithRealLogger/all_levels_allowed/DebugLog-10           17.00 ± 0%     13.00 ± 0%  -23.53% (p=0.002 n=6)
geomean                                                                      ²               -25.47%               ²
¹ all samples are equal
² summaries must be >0 to compute geomean

There is a regression in the all_levels_allowed/level.Debug benchmark, as now we need to read multiple stack frames for each log call. This is unavoidable, applications that are sensitive to this regression could use SpanLogger.DebugLog() rather than wrapping SpanLogger with level.Debug(...).
Which issue(s) this PR fixes:
(none)
Checklist

[x] Tests updated
[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

I'd like to investigate and understand the regression in the SpanLoggerWithRealLogger/all_levels_allowed/level.Debug benchmark, but I'm going to share this for feedback on the approach first.

I'd like to investigate and understand the regression in the SpanLoggerWithRealLogger/all_levels_allowed/level.Debug benchmark, but I'm going to share this for feedback on the approach first.

I've investigated this and addressed it in the main PR description. This PR is good to go now.

This is unavoidable, applications that are sensitive to this regression could use SpanLogger.DebugLog() rather than wrapping SpanLogger with level.Debug(...).

@charleskorn does this regression only apply to debug level?

This is unavoidable, applications that are sensitive to this regression could use SpanLogger.DebugLog() rather than wrapping SpanLogger with level.Debug(...).

@charleskorn does this regression only apply to debug level?

It applies to other levels too, if they are used when wrapping a SpanLogger.
However, at least in Mimir, it seems that the vast majority of logging to a SpanLogger is at the debug level, so that the logs appear only as events on trace spans and not in logs running at the default info level, so I don't think this regression is a big issue.

However, at least in Mimir, it seems that the vast majority of logging to a SpanLogger is at the debug level, so that the logs appear only as events on trace spans and not in logs running at the default info level, so I don't think this regression is a big issue.

Ah good point.


[DO NOT MERGE] design preview

The purpose of this PR is just to generate a stable Netlify preview deployment that shows the latest efforts on the new design implementation.

@thomasheyenbrock the canary release tags change on every push fyi!

@B2o5T thanks for reviewing this 🙏  I'll probably split this huge PR up into smaller increments though to make the individual changes even more reviewable 😉

All changes have been split up and reviewed incrementally. We collected all of them on the graphiql-v2 branch, this PR is basically succeeded by #2523.

Marvelous work thank you!


Populating the patient synopsis panes via individual REST requests

When you select a patient in the PHR UI, the Home screen displays a set of 6 panels showing the latest 4 records for:

Problems
Contacts
Allergies
Medications
Vaccinations
Top 3 Things

Currently PulseTile asks the back-end for the data to populate these panels via a single REST API, eg:
GET /api/patients/9999999000
The problem is that this presents the back-end with a very large and quite time-consuming task, the details of which I won't bore you all with, but the main problem is that the middle tier cannot respond with the data for the panels until it has received, processed and assembled all the results for all 6 headings from all the back-end OpenEHR machines.
I'd like to propose that we switch to populating each panel separately via its own API,
GET /api/patients/{patientId}/synopsis/{heading}
eg:
GET /api/patients/9999999000/synopsis/allergies
In other words, for PulseTile to fire off 6 requests to the middle tier asynchronously and at the same time, with each panel displaying its 4 records when the response is returned for its specific heading.  This will improve the perceived responsiveness of the UI at this stage of its data presentation, and also will allow the middle tier to distribute its load across multiple Node.js worker processes which should improve the overall time taken to retrieve and process all the headings.
The API heading names would be:

problems
contacts
allergies
medications
vaccinations
top3things

One additional change related to this - another set of data returned by the original single API is the demographics data for the patient.  The UI will need to fetch this using another API:
GET /api/demographics/{{patientid}}
eg GET /api/demographics/9999999000
This returns the info to populate the patient banner (name, address, GP details etc)

task is done

thanks @juliashulga
Suggest we make sure this is working as requested soon, then we can consider closing this issue
T

New adjustment:
optimization in file src/components/pages/PatientsSummary/separate-selectors.js
Create one selector to replace it with current 6 selectors

thanks Julia
That adjustment remains TODO

@juliashulga  please check with @robtweed  that he is happy this can be closed

Hi @robtweed can this task be closed now ? is everything ok here ?

Yes it seems to work OK now


ActionForm does not submit when an input has name="host"

It's been a while since I got a bug like that. Wasted about 10 hours tracking why my first ever ActionForm would not submit.
I was able to reproduce in my own repo, go to http://localhost:3000/form : https://gitlab.com/jeangabriel-gc/testleptos
And also by modifying the todo example :
diff --git a/examples/todo_app_sqlite/src/todo.rs b/examples/todo_app_sqlite/src/todo.rs
index 7dc728a2..66df0f96 100644
--- a/examples/todo_app_sqlite/src/todo.rs
+++ b/examples/todo_app_sqlite/src/todo.rs
@@ -81,6 +81,7 @@ pub async fn add_todo(title: String) -> Result<(), ServerFnError> {
 #[server(DeleteTodo, "/api")]
 pub async fn delete_todo(id: u16) -> Result<(), ServerFnError> {
     let mut conn = db().await?;
+    println!("delete_todo {}", id);

     sqlx::query("DELETE FROM todos WHERE id = $1")
         .bind(id)
@@ -171,6 +172,7 @@ pub fn Todos(cx: Scope) -> impl IntoView {
                                                             {todo.title}
                                                             <ActionForm action=delete_todo>
                                                                 <input type="hidden" name="id" value={todo.id}/>
+                                                                <input type="hidden" name="host" value={todo.id}/>
                                                                 <input type="submit" value="X"/>
                                                             </ActionForm>
                                                         </li>

As soon as the input with name="host" is added the form won't submit. The client will enter in a loop that seems to have something to do with looking up values in wasm from javascript but I didn't dig much in that direction other than adding a console.log in getStringFromWasm0 that output this forever in loop when it hangs
getStringFromWasm0 1103068 8
getStringFromWasm0 1103076 4
getStringFromWasm0 1103068 8
getStringFromWasm0 1103076 4
getStringFromWasm0 1103068 8
getStringFromWasm0 1103076 4

Let me know if I can help, I might be able to find some time to look into this in the upcoming weeks.

This is very strange. I wasn't able to figure out why host in particular was causing this issue, but was able to break out of the infinite loop. Could you please test the branch in PR #762 against your actual example and let me know if it fixes the issue for you?


Adding a product gives a JavaScript error

Attempting to add a "Databases" product, this JavaScript error is thrown.

Note to fixer:
The new UX is expecting the product_type custom fields to be in a different place. It'll be easier to have UX look in the right place.

@AllenBW can you please take a look here

Awaiting a product_type fix from Stack! Will retouch after his changes go through.


AssociatedDocumentLineDocument is incorrectly expected with BASIC profile

Hi,
when validating an BASIC invoice built with konik, the error Element 'ram:AssociatedDocumentLineDocument' must occur exactly 1 times. is shown. I openend Issue https://github.com/konik-io/konik/issues/89, where the konik team stated that AssociatedDocumentLineDocument should not exist in Basic Profile according to the ZUGFeRD specification.
My XML, the validation report and the specifiation reference are included in this issue.

In zf2 it's required as of and including basic (not in basic wl nor minimum) and in zf1 there is a mismatch between the schematron file (where it is required) and the spec (where it is not required for basic), I'll try to get a statement what's correct


IOS issue

On my mobile samsung everything works fine but on IOS is having issues fully animating.

Safari desktop also has same problems animating.

my mistake,  diff browsers require -moz- -webkit-

I tried breaking out the animation names from 1 liner to each item such as this but no luck:
-webkit-animation-name: rotate; -webkit-animation-duration: 2s; -webkit-animation-iteration-count: infinite; -webkit-animation-timing-function: linear; -webkit-animation-fill-mode: infinite;

looks like ios & safari has rotation issues, "The workaround for Safari is to never rotate more than 179 in either direction, then complete the rest of the rotation in another segment."


python38Packages.josepy: 1.9.0 -> 1.10.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python38Packages.josepy is: "JOSE protocol implementation in Python"
meta.homepage for python38Packages.josepy is: "https://github.com/jezdez/josepy"
meta.changelog for python38Packages.josepy is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

/nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0/bin/jws passed the binary check.

/nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0/bin/.jws-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 1.10.0 with grep in /nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0

found 1.10.0 in filename of file in /nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0

directory tree listing: https://gist.github.com/c3f14e7f7f9ac7333fc0d2cc79a87f5f

du listing: https://gist.github.com/2bc349183d80c5aec4153503893c452d

Rebuild report (if merged into master) (click to expand)

67 total rebuild path(s)

18 package rebuild(s)

18 x86_64-linux rebuild(s)
17 i686-linux rebuild(s)
15 x86_64-darwin rebuild(s)
17 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
certbot
certbot-full
home-assistant
python38Packages.acme
python38Packages.certbot
python38Packages.certbot-dns-cloudflare
python38Packages.certbot-dns-rfc2136
python38Packages.certbot-dns-route53
python38Packages.hass-nabucasa
python38Packages.josepy
python39Packages.acme
python39Packages.certbot
python39Packages.certbot-dns-cloudflare
python39Packages.certbot-dns-rfc2136
python39Packages.certbot-dns-route53
python39Packages.hass-nabucasa
python39Packages.josepy
simp_le

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python38Packages.josepy https://github.com/r-ryantm/nixpkgs/archive/7b40f0026360e4f6c24b9d0e589d3b4be2793a6e.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0
ls -la /nix/store/wkfm7abd5bp09p957jcy5894ss62yxri-python3.8-josepy-1.10.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

9 packages failed to build:

certbot (python39Packages.certbot)
certbot-full
python38Packages.certbot
python38Packages.certbot-dns-cloudflare
python38Packages.certbot-dns-rfc2136
python38Packages.certbot-dns-route53
python39Packages.certbot-dns-cloudflare
python39Packages.certbot-dns-rfc2136
python39Packages.certbot-dns-route53

8 packages built:

home-assistant
python38Packages.acme
python38Packages.hass-nabucasa
python38Packages.josepy
python39Packages.acme
python39Packages.hass-nabucasa
python39Packages.josepy
simp_le

Maintainer pings

@ofborg eval

Certbot needed 1.20.0 bump for https://github.com/certbot/certbot/pull/9045


Cumulative hours when codam's monitoring system is disabled.

 The percentage can be removed though.

Just a heads-up, I'm still thinking about implementing this, but it would require a lot of work internally so I haven't started on it yet. It's still on the todo-list though!


Add UoW pattern

It would be good to off good Unit of Work pattern support. Including start/end method and scope disposal for batch mode

This can be implemented using filters


Default flags from environment variables

It's common to default some command line arguments from the environment, where command line overrides the environment variables, which in turn overrides any config file.
Absl doesn't support this but I don't see an explanation of why - is it a design choice?
It is of course possible to do something like this:
flags.DEFINE_string('foo', os.getenv('FOO', 'Some default'), '')

but it's also quite common to have multiple environment variables, which starts getting quite repetitive. Is there any fundamental argument against adding some support for using environment variables, regardless of how that surfaces in the API?

IMHO:

We haven't seen a case where all flags need this. We do have several flags that get default value from environment variables, but we just explicit call os.getenv (or equivalent). e.g. the --test_srcdir flag in absl.testing.
argparse doesn't support it.
Prefer explicit than implicit. If a flag / application needs to get value from environment variables, it's better to explicitly do that. If repetition is a concern, one can always define wrapper functions on top of absl.flags in their own application/library. absl.flags can be viewed as a lower level API.
Flags are case sensitive and it's not uncommon to define different flags with same letters but different cases (common with single letter flags). But environment variables are usually all upper case. There isn't an undebatable way to map between flag names and environment names and avoid conflicts.

Hope this explains things.


add plugin documentation to the main pages

What does this PR do?
Documentation for the Plugin API
Checklist

[ ] This is an enhancement of existing features, or a new feature in existing plugins

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] I have made corresponding changes to the documentation

[ ] This is a bugfix

[ ] I have updated CHANGELOG.asciidoc
[ ] I have added tests that would fail without this fix

[ ] This is a new plugin

[ ] I have updated CHANGELOG.asciidoc
[ ] My code follows the style guidelines of this project
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I have updated supported-technologies.asciidoc
[ ] Added an API method or config option? Document in which version this will be introduced
[ ] Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident.

[x] This is something else

[ ] I have updated CHANGELOG.asciidoc

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-06-14T16:14:15.350+0000

Duration: 3 min 13 sec

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@elasticmachine run elasticsearch-ci/docs


Commutator in Quantum Mechanics

https://github.com/Quantum-Software-Development/Q-Star/assets/113218619/054dd0d7-4104-4741-a369-3791b3686d72

Commutator in Quantum Mechanics


Errors during RegTest: ERROR: CheckProofOfWork() : hash doesn't match nBits

I was running the Gradle :omnij-rpc:regTest task directly from IntelliJ (via the Gradle projects window) on Mac OS X 10.10.4 with commit ad189d67b6c2af10820066600cd2dab4f182a351 and my system slowed down and I noticed the ERROR: CheckProofOfWork() : hash doesn't match nBits being repeated rapidly and apparently endlessly.
This may have been the problem I saw while running RegTest last week. Because the problem seemed to be about to crash my machine, I immediately hit Command-Q in IntelliJ which was running the tests. When IntelliJ and therefore the test client exited, the message stopped repeating.
Omni Core handler: new confirmed transaction [height: 2015, idx: 0]
Omni Core handler: block connect end [new height: 2015, found: 0 txs]
2015-07-06 06:47:26 update_tally_map(mpexoDuSkGGqvqrkrjiFng38QPkJQVFyqv, 1=0x1, +0, ttype=0) ERROR: amount to credit or debit is zero
  - Connect postprocess: 100.69ms [238.44s]
- Connect block: 100.86ms [239.04s]
keypool keep 3669
ThreadRPCServer method=getblockcount
ThreadRPCServer method=getblockhash
ThreadRPCServer method=getblock
ThreadRPCServer method=gettxout
ThreadRPCServer method=setgenerate
keypool added key 3770, size=101
keypool reserve 3670
CreateNewBlock(): total size 1000
  nActualTimespan = 139476644  before bounds
GetNextWorkRequired RETARGET
Params().TargetTimespan() = 1209600    nActualTimespan = 4838400
Before: 207fffff  7fffff0000000000000000000000000000000000000000000000000000000000
After:  1e09debb  000009debbc99a778556334111eefccdaab889667445223000ddebbc99a77855
  nActualTimespan = 139476644  before bounds
GetNextWorkRequired RETARGET
Params().TargetTimespan() = 1209600    nActualTimespan = 4838400
Before: 207fffff  7fffff0000000000000000000000000000000000000000000000000000000000
After:  1e09debb  000009debbc99a778556334111eefccdaab889667445223000ddebbc99a77855
  nActualTimespan = 139476644  before bounds
GetNextWorkRequired RETARGET
Params().TargetTimespan() = 1209600    nActualTimespan = 4838400
Before: 207fffff  7fffff0000000000000000000000000000000000000000000000000000000000
After:  1e09debb  000009debbc99a778556334111eefccdaab889667445223000ddebbc99a77855
      - Connect 1 transactions: 0.01ms (0.007ms/tx, 0.000ms/txin) [0.11s]
    - Verify 0 txins: 0.02ms (0.000ms/txin) [0.41s]
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits

... snip ... (1000's of occurrences of the CheckProofOfWork() error message)
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckProofOfWork() : hash doesn't match nBits
Checking mempool with 0 transactions and 0 inputs
  - Load block from disk: 0.00ms [0.00s]
      - Connect 1 transactions: 0.01ms (0.006ms/tx, 0.000ms/txin) [0.11s]
    - Verify 0 txins: 0.02ms (0.000ms/txin) [0.41s]
    - Index writing: 0.08ms [0.25s]
    - Callbacks: 0.03ms [0.04s]
  - Connect total: 0.18ms [0.58s]
  - Flush: 0.03ms [0.02s]
  - Writing chainstate: 0.01ms [0.01s]
Omni Core handler: block connect begin [height: 2045]
estimates: for confirming within 0 blocks based on 100/3 samples, fee=0.00039525 BTC/kB, prio=-1
Checking mempool with 0 transactions and 0 inputs
UpdateTip: new best=00000064baa55013e7c99116bb365f74f0f99164a70c3ed3b3af7e676fc53b56  height=2046  log2_work=25.65125  tx=4854  date=2015-07-06 06:50:22 progress=1.000000  cache=554
Flushed wallet.dat 110ms
AddToWallet f225ffc14c3ce698de3fc3cc2a29e9a1739b74ea9cc968e1c2bf7c99d901e239  new
Omni Core handler: new confirmed transaction [height: 2046, idx: 0]
Omni Core handler: block connect end [new height: 2046, found: 0 txs]
  - Connect postprocess: 166.35ms [243.72s]
- Connect block: 166.57ms [244.33s]
keypool keep 3772
Flushing wallet.dat
Flushed wallet.dat 65ms

This seems to be reproducible on the 2nd time I run the tests after starting Omni Core. (Note that I use a shell script that removes the Omni state files to start omnicored)

Interesting...
Is this new?
Do you see the same CheckProofOfWork() regularly or is this something
you've only started seeing recently?
FYI, our Omni Code doesn't usually touch underlying Bitcoin stuff (eg such
as block generation and validation) so my first guess is this is something
we've inherited from upstream.
On Mon, Jul 6, 2015 at 5:42 PM, Sean Gilligan<EMAIL_ADDRESS>wrote:

This seems to be reproducible on the 2nd time I run the tests after
starting Omni Core. (Note that I use a shell script that removes the Omni
state files to start omnicored)
—
Reply to this email directly or view it on GitHub
https://github.com/OmniLayer/omnicore/issues/115#issuecomment-118760941.

In regtest mode the mined blocks must satify a certain level of difficulty, which is low, but still given. In setgenerate it loops until sufficient difficulty is reached:
https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/src/rpcmining.cpp#L181-L184:
while (!CheckProofOfWork(pblock->GetHash(), pblock->nBits)) {
    // Yes, there is a chance every nonce could fail to satisfy the -regtest
    // target -- 1 in 2^(2^32). That ain't gonna happen.
    ++pblock->nNonce;
}

Each time it's not sufficient, a log entry is written:
https://github.com/OmniLayer/omnicore/blob/omnicore-0.0.10/src/pow.cpp#L93-L95:
// Check proof of work matches claimed amount
if (hash > bnTarget)
    return error("CheckProofOfWork() : hash doesn't match nBits");

If it becomes too much, and the regtests slow down, it helps to clear the whole regtest dir. The block reward decreases over time, also in regtest mode, so more mining is required, the more tests you run. :)
Feel free to reopen, if there is something else.


Upgrade CDNs Traffic Portal view to use AG-Grid tables

This closes #6471.
This updates the "CDNs" Traffic Portal page to use AG-Grid instead of JQuery datatables. It's mostly a drop-in replacement, except for two things.

A column for CDN ID and another for "Last Updated" have been added - the data was always available but just not shown previously. They're both hidden by default to preserve the old table's structure a bit more.

Which Traffic Control components are affected by this PR?

Traffic Portal

What is the best way to verify this PR?
Make sure all the TP tests pass, make sure the new table looks okay. There are a lot of context menu options, so I checked a few of those out, they seem to all be working okay.
PR submission checklist

[ ] This PR has tests
[ ] This PR has documentation
[x] This PR has a CHANGELOG.md entry
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY

Rebase please (has CiaB fix)


feature-  add CLI options to init command

Currently, executing fablo init initializes a small network configuration file. However, it would greatly enhance user experience if I could specify the number of organizations and peers directly from the command line interface (CLI). This would enable the generation of the configuration JSON file based on the inputs provided via CLI options.

hey @dzikowski any thoughts over this? I may raise PR to add this feature soon then.

I think it might be a bit tricky to implement, but you can start it if you want

This one is indeed a tricky one cause its such a difficult task to identify where exactly the fablo-config.json is getting created. Turns out that, this line - https://github.com/hyperledger-labs/fablo/blob/cbd4ed0049d1b0876927cdbea80ee10531bbc7ba/fablo.sh#L122
initializes a temporary directory which has fablo as starting name and then some random string eg. fablo.34dfgrt
and this is created at tmp/fablo.xxxxxx. I understand this gets created but from where are we getting this sample config file already defined in this folder. basically it should initialise the temp folder but from where do am I getting this sample config file?

What I am guessing is that when I do init everything gets mounted to a docker container and that container and log statements and everything gets executed from there and that container gets destroyed after the execution, again I am not sure, I am guessing from this command - https://github.com/hyperledger-labs/fablo/blob/cbd4ed0049d1b0876927cdbea80ee10531bbc7ba/fablo.sh#L145C1-L150C9

@dzikowski  @Hejwo you guys have done a lot of engineering and encapsulation while setting up this sample fablo-config.json :disappointed_relieved:


Properly handle scenes in Find in Files

Closes #33320
It's not perfect, because it just opens the scene, but not sure if there is a way to open a specific built-in script (without resorting to hacks like partial parsing of the scene). Still better than the old behavior that resulted in bad things happening.

Thanks!

Cherry-picked for 3.5.


[FIX] no backdrop coming in friends' movies in carousel.

Hey @daccotta please assign me this task.


Clumping GWAS Catalog top hits

GWAS Catalog top-hits don't have any clumping strategy. If a GWAS catalog study reports many associations within an region/haplotype we have no way to control. This might result on an artificially high number of credible sets resulted from PICS.
Next, an example on GCST90321118

We want to perform clumping on these credible sets, but we still need to scope the technical strategy to implement this.

I think the best person to implement this is @DSuveges

As a related issue, it has been identified that the large number of credible sets in the PICSed GWAS Catalog curated dataset can be partially explained by a bug in the LD clumping method. However after fixing that issue, there are still a relatively high number of associations on chromosome 7 of this study:
+---------------------------------------------------------------------------------------------------------------------+------------+----------+---------+--------------+--------------+------------------------------------------------------------------+
|variantId                                                                                |studyId     |chromosome|position |pValueMantissa|pValueExponent|qualityControls                                                   |
+---------------------------------------------------------------------------------------------------------------------+------------+----------+---------+--------------+--------------+------------------------------------------------------------------+
|7_37918687_G_A                                                                                |GCST90321118|7         |37918687 |1.0           |-8            |[]                                                                |
|7_38060307_C_CT                                                                                |GCST90321118|7         |38060307 |5.0           |-18           |[]                                                                |
|7_38109854_T_TA                                                                                |GCST90321118|7         |38109854 |6.0           |-12           |[Variant not found in LD reference]                               |
|7_38113261_A_G                                                                                |GCST90321118|7         |38113261 |2.0           |-16           |[]                                                                |
|7_96514529_A_AC                                                                                |GCST90321118|7         |96514529 |2.0           |-9            |[]                                                                |
|7_121084734_C_T                                                                                |GCST90321118|7         |121084734|6.0           |-10           |[]                                                                |
|7_121117073_C_T                                                                                |GCST90321118|7         |121117073|2.0           |-11           |[Variant not found in LD reference]                               |
|7_121241062_G_GAATTGGATGGAAAAATAAGCACTTTTGAGGAAGATAATCTTTATTTTGCCATTCAAAAACCAGCATCTCTCCTAAATTTTCTGTTGTTTCTTTTAGCAGTAC|GCST90321118|7         |121241062|1.0           |-34           |[Variant not found in LD reference]                               |
|7_121241063_G_GGATGGAAAAATAAGCACTTTTGAGGAAGATAATCTTTATTTTGCCATTCAAAAACCAGCATCTCT                                     |GCST90321118|7         |121241063|1.0           |-34           |[Variant not found in LD reference]                               |
|7_121241065_C_CATTCAAAAACCAGCATCTCTCCTAAATTTTCTGTTGTTTCTTTTAGCA                                                      |GCST90321118|7         |121241065|1.0           |-34           |[Variant not found in LD reference]                               |
|7_121241065_C_T                                                                                |GCST90321118|7         |121241065|1.0           |-34           |[Variant not found in LD reference]                               |
|7_121251832_A_G                                                                                |GCST90321118|7         |121251832|3.0           |-32           |[Variant not found in LD reference]                               |
|7_121313702_G_A                                                                                |GCST90321118|7         |121313702|1.0           |-14           |[]                                                                |
|7_121320217_G_C                                                                                |GCST90321118|7         |121320217|1.0           |-126          |[Palindrome alleles - cannot harmonize]                           |
|7_121325298_C_T                                                                                |GCST90321118|7         |121325298|1.0           |-19           |[]                                                                |
|7_121325508_A_G                                                                                |GCST90321118|7         |121325508|7.0           |-13           |[]                                                                |
|7_121327159_A_T                                                                                |GCST90321118|7         |121327159|3.0           |-25           |[Palindrome alleles - cannot harmonize]                           |
|7_121364935_G_A                                                                                |GCST90321118|7         |121364935|6.0           |-15           |[]                                                                |
|7_121373353_T_G                                                                                |GCST90321118|7         |121373353|2.0           |-12           |[]                                                                |
|7_121386694_T_C                                                                                |GCST90321118|7         |121386694|6.0           |-9            |[LD block does not contain variants at the required R^2 threshold]|
+---------------------------------------------------------------------------------------------------------------------+------------+----------+---------+--------------+--------------+------------------------------------------------------------------+
only showing top 20 rows

Some of these credible sets were included with the flag: lead not found in credible set, however when this flag is absent, the returned LD sets were not overlapping.
This observed behaviour justifies the application an extra, window based clumping on the GWAS Catalog curated associations.

Test dataset showing a StudyLocus dataset before and after window based clumping:
+-------+----------+--------+--------------+--------------------+--------------+---------+
|studyId|chromosome|position|pValueExponent|        studyLocusId|pValueMantissa|variantId|
+-------+----------+--------+--------------+--------------------+--------------+---------+
|     s1|        c1|       1|            -1|<PHONE_NUMBER>81534521|           1.0|       v1|
|     s1|        c1|       3|            -3| -206100010007302174|           1.0|       v4|
|     s1|        c1|       2|            -2|-4721564960210010127|           1.0|       v2|
|     s1|        c2|       2|            -2|-2919469633967748933|           1.0|       v3|
|     s3|        c2|       2|            -2|<PHONE_NUMBER>174414045|           1.0|       v1|
+-------+----------+--------+--------------+--------------------+--------------+---------+

In [2]: sl.window_based_clumping(3).df.show()
+-------+----------+--------+--------------+--------------------+--------------+---------+------------------------------------------------------------+
|studyId|chromosome|position|pValueExponent|studyLocusId        |pValueMantissa|variantId|qualityControls                                             |
+-------+----------+--------+--------------+--------------------+--------------+---------+------------------------------------------------------------+
|s1     |c1        |1       |-1            |1740131172091600674 |1.0           |v1       |[Explained by a more significant variant in the same window]|
|s1     |c1        |2       |-2            |-6342038754064840370|1.0           |v2       |[Explained by a more significant variant in the same window]|
|s1     |c1        |3       |-3            |-3040002280507636093|1.0           |v4       |[]                                                          |
|s1     |c2        |2       |-2            |8923642814302707841 |1.0           |v3       |[]                                                          |
|s3     |c2        |2       |-2            |-218747710423759089 |1.0           |v1       |[]                                                          |
+-------+----------+--------+--------------+--------------------+--------------+---------+------------------------------------------------------------+

(The studyLocus Id is changed, but that's fine)


Added actual parser.

The other one was unreliable and unrealistic. This one has an array of tokens. It will append a keyword to parsedCode when it detects one outside of a string (I am sort of a hobbyist programming language desgner so seeing that implementation of a parser hurt me. Don't merge it yet, it hasn't been tested for errors
I'll do all that in the morning.

Thank you for your pull request. However, I don't see the point of this parser. You said the other one was unreliable. How?

Thank you for your pull request. However, I don't see the point of this parser. You said the other one was unreliable. How?

It splits by spaces. I just tested this out and it works perfectly. You can now say 8+2, 8+ 2 or 8 +2 or even 8          +      2 and it works fine, rather than saying 8 + 2 mandatory.

Thank you for your pull request. However, I don't see the point of this parser. You said the other one was unreliable. How?

It splits by spaces. I just tested this out and it works perfectly. You can now say 8+2, 8+ 2 or 8 +2 or even 8 + 2 and it works fine, rather than saying 8 + 2 mandatory.

Oh okay. Thank you for the PR. I'll merge in a second.


Crate succeeds to build, but some modules are unreachable

Crate name
rmatrix_ks
Build failure link
https://docs.rs/crate/rmatrix_ks/0.3.7/builds/1313071
Additional details
I used cargo doc --all-features to compile the document locally, and everything was displayed normally.

However, when I uploaded it to docs.rs, I found that some module pages were not displayed, specifically the serde module.

I don't know why. My configuration is as follows:
[package.metadata.doc.rs]
features = ["rand_mat", "rayon_mat", "serde_mat"]
all-features = true
no-default-features = true

serde module has config #![cfg(serde_mat)]

I initially thought it was caused by doc_cfg, but when I removed doc_cfg and tried to solve this, nothing changed.

I'm not sure how I didn't see this in the beginning.
I think this is just a typo.
The section has the wrong name, you used [package.metadata.doc.rs], correct is [package.metadata.docs.rs].

See also https://docs.rs/about/builds for more details

I'll close this issue because I'm quite sure this is the problem.
Feel free to comment / reopen if not, then I'll dig into it again.

I'm not sure how I didn't see this in the beginning.
I think this is just a typo.
The section has the wrong name, you used [package.metadata.doc.rs], correct is [package.metadata.docs.rs].

Thank you so much, I didn't even realize this typo myself.


try to ignore AVAudioSessionErrorCodeIsBusy

the session should be deactivated, so just ignore this error.
Some references:
https://stackoverflow.com/questions/16439767/error-domain-nsosstatuserrordomain-code-560030580-the-operation-couldn-t-be-com
https://github.com/csdcorp/speech_to_text/issues/241

Does not work.


Add fnune/recall.nvim

Hi! I've spent some time creating https://github.com/fnune/recall.nvim/
It does exactly what I needed in terms of managing marks in an easier way in Neovim, and focusing on global marks (the only ones I care about).
This PR adds it to the Marks section.
Repo URL:
https://github.com/fnune/recall.nvim
Checklist:

[x] The plugin is specifically built for Neovim, or if it's a colorscheme, it supports treesitter syntax.
[x] The lines end with a .. This is to conform to awesome-list linting and requirements.
[x] The title of the pull request is Add/Update/Remove `username/repo`  (notice the backticks around `username/repo`) when adding a new plugin.
[x] The description doesn't mention that it's a Neovim plugin, it's obvious from the rest of the document. No mentions of the word plugin unless it's related to something else.
[x] The description doesn't contain emojis.
[x] Neovim is spelled as Neovim (not nvim, NeoVim or neovim), Vim is spelled as Vim (capitalized), Lua is spelled as Lua (capitalized), Tree-sitter is spelled as Tree-sitter.
[x] Acronyms should be fully capitalized, for example LSP, TS, YAML, etc.

Thanks for the PR!


Flame Graph Report - Build a legend of Frameworks

For every color used by Flame graph, build a legend say in upper-right hand corner

Fixed by e6f79c497f8f3eb6290a91859821ddb9dd8fcffc


WIP: Using promise queue instead of for loop

Using promise queue instead of for loop

Closed by #35


Use PostCSS 5.0 API

I don't know why cli: defaults and cli: formatter test case is failed.

Thanks. :+1:


cd back to original directory for the buildpack to work

Some underlying buildpacks expect the current directory to be that of the app and not the /tmp/buildpackXYZ directory that this changes into. This fixes that.

Hi! I was about to comment on this PR but it was merged before I had a chance. The former Lifecycle team and/or languages team mostly own buildpacks like this -- our bad for not having a codeowners.
Could you explain more about what buildpacks don't work prior to this change? Whilst it's likely a sensible change to make, iirc the buildpack API makes no guarantee as to working directory (even though it really should), so in general buildpacks should not make assumptions about it :-)

Ah, sorry about that @edmorley . I wasn't aware that Lifecycle owned this.
The one we're specifically concerned about is https://github.com/weibeld/heroku-buildpack-run.git. I guess I can fork that to the heroku org as well. The problem is the compile step from this expects a buildpack-run.sh file in the current directory (which is the app directory) but when run in the context of the multi buildpack, that current directory is different.
Ideally speaking, a buildpack is usually expected to have the current directory as the app's root directory so that its detection phase works.

No worries!

The problem is the compile step from this expects a buildpack-run.sh file in the current directory (which is the app directory)

So that buildpack does an explicit cd, so I'm not sure this is the issue?
https://github.com/weibeld/heroku-buildpack-run/blob/dd648d6988f490dc1d896ae12ea79a17a5753af7/bin/compile#L23
Also, when not using the multi buildpack, the working directory is set to the buildpack, not the app/build dir:
https://github.com/heroku/cytokine/blob/2357eb8e56e0f7d0bcc55e8b1d27af1cec3a73dc/buildpack/buildpack.go#L312
So I think the issue must be due to another reason?

I guess I can fork that to the heroku org as well

For compliance reasons I would strongly recommend not using buildpacks not owned by the Heroku github org (or heroku / heroku-community buildpack registry namespace).

Ideally speaking, a buildpack is usually expected to have the current directory as the app's root directory so that its detection phase works.

The detect phase is different from the compile phase. For detect, when not using the multi buildpack, the working directory is set to the buildpack not the app/build dir:
https://github.com/heroku/cytokine/blob/2357eb8e56e0f7d0bcc55e8b1d27af1cec3a73dc/buildpack/buildpack.go#L112
Which is why most buildpacks use $1 (the build dir path) when checking for file presence during detect, eg:
https://github.com/heroku/heroku-buildpack-multi/blob/be85414f9c01ee87c955fd4d13a86982623a970d/bin/detect#L3
https://github.com/heroku/heroku-buildpack-apt/blob/a338a17d1fc5dc444162939630e0c46f368ce787/bin/detect#L4
https://github.com/heroku/heroku-buildpack-go/blob/072fd3a4020a3ac3905b4272fe9abc5d59c6c349/bin/detect#L5-L12
As such it's starting to seem like this change may not be required and perhaps should be reverted, as it actually diverges from how non-multi builds work?

Unfortunately this has broken customer builds, eg:
https://heroku.support/966104
A such I've reverted it in #21.

Dang! Apologies. We discussed this further and decided to take a different approach to make progress. Sorry for causing grief and thanks for reverting this, @edmorley .


[Triton-MLIR][Backend] Revert a bug of smem allocation for non-scratch cvt_layout

@goostavz This PR has been merged and modified by https://github.com/openai/triton/pull/692


Chapter 9: RuntimeError: torch.cuda.FloatTensor is not enabled.

Hi. I got an error when following the tutorial and ran python main.py train --ploy-every=150 --batch-size=128 --pickle-path='tang.npz' --lr=1e-3  --env='poetry3' --epoch=50
It throws an error: RuntimeError: torch.cuda.FloatTensor is not enabled.
I tried both python 2.7.10 and python 3.6.5 but no luck.
Thanks!

I just upgraded pytorch to 0.4.0 the same error was thrown. Maybe you need to downgrade the version of pytorch to 0.3.0 or something else.

Could you give a more detail traceback？ I wanna know which line code raises the error.

Here is the full log:
Traceback (most recent call last):
  File "main.py", line 231, in <module>
    fire.Fire()
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/fire/core.py", line 127, in Fire
    component_trace = _Fire(component, args, context, name)
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/fire/core.py", line 366, in _Fire
    component, remaining_args)
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/fire/core.py", line 542, in _CallCallable
    result = fn(*varargs, **kwargs)
  File "main.py", line 149, in train
    model.cuda()
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/torch/nn/modules/module.py", line 249, in cuda
    return self._apply(lambda t: t.cuda(device))
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/torch/nn/modules/module.py", line 176, in _apply
    module._apply(fn)
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/torch/nn/modules/module.py", line 182, in _apply
    param.data = fn(param.data)
  File "/Users/blurred/private/PyTorch-book/env/lib/python2.7/site-packages/torch/nn/modules/module.py", line 249, in <lambda>
    return self._apply(lambda t: t.cuda(device))
RuntimeError: torch.cuda.FloatTensor is not enabled.

If you suspect this is an IPython bug, please report it at:
    https://github.com/ipython/ipython/issues
or send an email to the mailing list at<EMAIL_ADDRESS>
You can print a more detailed traceback right now with "%tb", or use "%debug"
to interactively debug it.

Extra-detailed tracebacks for bug-reporting purposes can be enabled via:
    %config Application.verbose_crash=True

You maybe run only model.cuda() to try to know where is the error. or t.cuda.is_available() to check out your  cuda is good or bad?

model.load_state_dict(state_dict, strict=False)这样就可以了


VCIO does not collect some Severity (cvssv3.1) scores for a CVE

For a recent Vulnerability report of approximately 250 purl-CVE vulnerabilty combinations almost half were missing a Severity score (field value = NA) which is a critical deficiency for prioritizing investigation or remediation of vulnerabilities. A few cases are legitimate because the CVE has been rejected - see https://github.com/nexB/vulnerablecode/issues/1221, but in the other cases I checked there is one or more cvssv3.1 scores in the NVD (NIST:NVD and/or CNA: Google etc.). In a few cases it appear the the original CVE record did not have a cvssv3.1 value but in most cases the cvssv3.1 data is part of the original record based on the Change History. Note the cvssv3.1 data is the set of metrics not the derived numeric score.
We need to improve our CVE data collection to ensure that we capture the current Severity data and enable some tracking for adding Severity data if it was not available when we first collected a CVE or changed after we collected it.

I have some queries about this issue:

do we need to add a separate script to track the severity scores rather than coding for every single importer.
do we require routine checks to check any kind of update in the severity data.

@ambuj-1211
re:

is this issue available for contribution?
yes

@mjherzog would you have a few examples of such PURLs and vulnerabilities on hand?
@ambuj-1211 to pick a fix you would first nee to find out why and what happened.

@ambuj-1211
Let's tackle this in four steps:

[ ] Identify Missing Scores:

create Python or SQL query that finds vulnerabilities with severity information but lacking a CVSSv3 score. We'll prioritize focusing on recent vulnerabilities,
as they're more likely to have a CVSSv3 assigned.

[ ]  Manual Search:

randomly sample a subset of these vulnerabilities and manually search for their missing CVSSv3 scores on public resources like the National Vulnerability Database (NVD).

[ ] Document Findings (Issue Comment) that analyze the causes of missing CVSSv3 scores (importer type, recent discovery, .... )
Analyze why some vulnerabilities lack CVSSv3 scores

[ ] Write an improver or importer to get all missing CVSSv3

@ziadhany

create Python or SQL query that finds vulnerabilities with severity information but lacking a CVSSv3 score. We'll prioritize focusing on recent vulnerabilities, as they're more likely to have a CVSSv3 assigned.

correct me if I am wrong, for this I need to make a func in models.py and call it using custom management command?

@ambuj-1211 No,  just a Django or SQL query  like this
https://docs.djangoproject.com/en/5.0/topics/db/queries/#retrieving-specific-objects-with-filters

@pombredanne yes have done some work on this and will try to complete it soon.

@ambuj-1211 gentle ping, to get some closure on this topic.


firmware: Clarify structure and content.

Make overall structure more clear:

Intro
Getting firmware
Building from source
Preparing to Install
Flashing new firmware
Configuring system after installation
Resetting configuration

Move "Features" to the very top of the doc, that's what most people
are interested in, followed by list of supported platforms (even if
some platform is not supported currently, users are supposed to get
orientation by the list of features, and help to drive support for
more platforms).
Add more detailed phrases here and there, to help understanding by
novice and intermediate users.
Signed-off-by: Paul Sokolovsky<EMAIL_ADDRESS>

This is a bigger change than before. @ZigFisher, let me know if something in changes is factually incorrect and needs tweaking.

Sure, thanks !


Explorer file order reversed for files with underscores _.

Does this issue occur when all extensions are disabled?: Yes

Version: 1.83.1 (user setup)
Commit: f1b07bd25dfad64b0167beb15359ae573aecd2cc
Date: 2023-10-10T23:48:05.904Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Steps to Reproduce:
Open a blank/new folder.
Add files:

hello.txt
hello_1.txt
hello_world.txt

On the explorer window, the order displayed is:

hello_1.txt
hello_world.txt
hello.txt

Open the terminal (Powershell).
> ls
Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
-a----         11/8/2023   1:22 PM              0 hello.txt
-a----         11/8/2023   1:22 PM              0 hello_1.txt
-a----         11/8/2023   1:23 PM              0 hello_world.txt

The order in the explorer window is wrong. the shorter file is last, while it should be first.
This reproes in Ubuntu/WSL as well.

please also note that multiple underscores in the name will compound the effect and hello_1_world will come before hello_1 as well.

Please try changing the lexicograpahic sort options and let me know if that doesn't work

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

Yes this works - thanks

@lramos15 you can mark as solved


Fix CI timeouts using npm install --verbose

Summary
Edit: I've changed the solution to use --verbose, as CI was still timing out with the git config changes.
Inspiration taken from https://community-daily.mattermost.com/core/pl/5kec7ujznpf79nx49n4bjctchw. This solution is an alternative to adding --verbose to the npm install command. This solution more directly addresses the timing out issue.
Ticket Link
Fixes https://mattermost.atlassian.net/browse/MM-44776

Closing per https://github.com/mattermost/circleci-orbs/pull/30#issuecomment-1250536896


Update README.rst to include bower install step

Fixes https://github.com/sloria/cookiecutter-flask/issues/62

Thanks!


Handle missing/null repeated optional fields when converting Json messages to Protobuf

Problem encountered / steps to reproduce
For repeated columns in the BigQuery TableSchema, the JsonToProtoMessage.convertJsonToProtoMessage converter [here] requires that the input Json object both contains

the array field, and
it is not null.

If either of those things are not true, it fails with an error, before sending it to BigQuery
Investigations:
We tracked the cause of the error down to the fillRepeatedField method inside that converter, specifically [this line] which throws an error if the Json field is null or missing: jsonArray = json.getJSONArray(exactJsonKeyName);
Therefore it would be great to get this issue fixed.
Many thanks.

Fixed.


VS2015 Extension

I am planning on updating the extension to be a VS2015 compatible VSIX package and am creating this issue as an enhancement request, in anticipation of the pull request, in case anyone has any queries/issues.

Sounds like a good plan.

OK - Got it working with VSIX.  Less painful than I expected.  Testing now.
Could do with abstracting the common stuff between the vs2010 and vs2015 extensions in to a new library, so it is easier to maintain, as there is a lot of duplication.  :relaxed:

Hey, I updated the pull - is it OK now?

I am testing it. Will merge it soon if there is no problem.

I have tested it on VS2015 and it basically worked. Thanks for making this effort!
But there are a couple of issues to be fix before I can merge it into the master branch:

[feature] The description of the extension should be changed to something like "an automated unit test generation tool for .NET" (a screenshot is attached)

[feature] A simple user manual may be included to describe how to install the extension and how to use the tool
[feature] Make the .vsix compatible with VS2012, VS2013, VS2014.
[bug] When the "RandoopTestPrj" is removed from the Solution Explorer but remains in the project folder, an error occurs when the tool tries to create the testing project --- this may also be a bug for VS2010. (a screenshot is attached)

Also, I totally agree that "Could do with abstracting the common stuff between the vs2010 and vs2015 extensions in to a new library, so it is easier to maintain, as there is a lot of duplication."
--- once the problems mentioned above are fixed, we can create a new issue for this.
Thanks!

Thanks for reviewing it.  I will take a look at those issues soon. They shouldn't bee too hard to address.

Hi - I have resolved some of the issues (1 & 3).  I have also fixed the issue with running the extension without a solution loaded.
I am working on some documentation but want to get the coding out of the way first.
I think number 4 will have been an issue in 2010 too, as the objects havent changed much.  It looks easy enough to resolve.  The error comes from curSolution.AddFromTemplate(csTemplatePath, testPrjPath, prjName, false);, when csTemplatePath already exists.  Would you rather I prompt or just overwrite without asking?

Following what was already being done I have not added a warning when removing the directory when trying to create a new project.  It silently deletes it.  Issue 4 with this resolved!

@SJMakin, before directly delete the project folder, "Directory.Delete(testPrjPath);" (as committed in the "update"), you may want to check if the testPrjPath exists, otherwise it may invoke "DirectoryNotFoundException".

Is this working now in Visual Studio 2015 as a plugin? The ticket is still open!

@ancgate thank you for your interest. I will close the issue and feel free to use/test it. :)


problem import google kali linux FIXED

I have a problem in kali linux for module google 2.0.1 in crawler.py
Traceback (most recent call last):
File "iptv.py", line 2, in
import Crawler
File "/root/Bureau/IPTV/iptv/Crawler.py", line 2, in
import google
ImportError: No module named google

I have found the problem

just install : search-google

http://tvservice.pro/get.php?username=911283583508&password=dz9TQYkcE12yDoE&type=m3u_plus&output=mpegts

thanks
Le dim. 16 juin 2019 à 01:45, italiaforza3<EMAIL_ADDRESS>a
écrit :

http://tvservice.pro/get.php?username=911283583508&password=dz9TQYkcE12yDoE&type=m3u_plus&output=mpegts
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/Pirate-Crew/IPTV/issues/57?email_source=notifications&email_token=AGXJSOHG64BCO4MI5ZZV5ZTP2V5IJA5CNFSM4F624IXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXZCCTQ#issuecomment-502407502,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGXJSOH35L2Z5PY6IAQGM2DP2V5IJANCNFSM4F624IXA
.

How to install 'search-google' ?  Web search only comes back with googler.

what about [DEPRECATED] you all don't get


Added toFile

Using the toFile method you can easily attach the signature to a FormData instance and avoid parsing.

We are trying to keep signature_pad limited in scope to drawing the signature and since this is already possible without needing access to private methods I don't think we will implement this change.


[Core] Add and use PySharedPtr

WIP

I decided to just squash everything together since the number of "squash:" and "fixup:" commits were getting rather unwieldly (and since this, until now, was in Draft state).