remove unused black pre-commit hook and blacken docs

Summary of changes
pre-commit is configured in this repo. This means whenever I commit I automatically apply these fixes.
Because pre-commit is not run in CI the compliance has drifted, and so when I commit I get a huge number of changes!
Closes
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d/.
(See documentation for details)

@graingert Hi. I'm not the mainteiner of this repository, but I'll give you some advice.
Your commits contain too many redundant codes.
So we can't know what the purpose of this PR is and what it's modified.
If you are using VScode, I think the python linter works automatically when you save the files.
You should turn off the option in VScode settings, and then push the commits again.

@graingert Hi. I'm not the maintainer of this repository, but I'll give you some advice.
Your commits contain too many redundant codes.
So we can't know what the purpose of this PR is and what it's modified.
If you are using VScode, I think the python linter works automatically when you save the files.
You should turn off the option in VScode settings, and then push the commits again.

Hello, first thanks for the advice! However in this case I was simply running "git commit" when these automated changes were applied by the configuration in this repository

@graingert Hi. I'm not the maintainer of this repository, but I'll give you some advice.
Your commits contain too many redundant codes.
So we can't know what the purpose of this PR is and what it's modified.
If you are using VScode, I think the python linter works automatically when you save the files.
You should turn off the option in VScode settings, and then push the commits again.

Hello, first thanks for the advice! However in this case I was simply running "git commit" when these automated changes were applied by the configuration in this repository

Oops..
I thought the redundant codes was included using the linter, not Black.
But I just run Black with these files you modified, and found out you were right.
I'm not sure if it's okay to include this change because I'm not the maintainer of this repository,
but I'm sorry I gave you advice without even trying and even thinking...

@jaraco I have a question!
As I talked to @graingert  above, can unnecessary codes caused byBlack be included in the commit?
Unnecessary  here means that it is different from the original purpose that it was intended to be modified.
This repository stated that Black is used as the main linter, but there are actually files that are not applied with Black.

I'd also be happy to draft a new PR with my doc syntax error fixes, and the black configuration removed

There are many things going on here. This project derives from jaraco/skeleton, so that’s where the black configuration comes from. It’s is meant to be disabled because this project hasn’t actually adopted black yet, though I plan to do so soon. I don’t experience the problems because I haven’t opted in to pre-commit for my local checkout of this repo. Is that an option for now (opt out of pre-commit for Setuptools) or do you have another tool that automatically installs precommit?

@jaraco I use existence of .pre-commit-config.yaml as a call to action to use it

@jaraco I use existence of .pre-commit-config.yaml as a call to action to use it

Totally fair and reasonable. I guess what I'm asking is that you disregard that call temporarily for this project.

I think it's still worth applying blacken docs though

I'm slightly opposed to running pre-commit in CI. It will add a new workflow and thus noise to the UI. For example, it will double the number of lines that appear under the actions list:

And while that might seem like a minor annoyance, it's caused me real difficulty when I go to that page to check out the status of a push or tag. When I quickly glance at that page, I have to mentally filter out "pre-commit" lines. I've previously had to do this for a different workflow I'd enabled called "automerge", which I recently removed because it was not useful, and I was relieved that I no longer had to mentally filter out those unhelpful workflow results.
That said, if the best thing to do for a project that has pre-commit hooks is to run them in a workflow, I may consider doing that, but I'd want to do it in jaraco/skeleton, so I'm not having to manage it for each project separately.
I can see that I added the pre-commit hooks in https://github.com/jaraco/skeleton/commit/d0f07a4e7ad465b0935bf85da94b12b9b8cc2e77#diff-63a9c44a44acf85fea213a857769990937107cf072831e1a26808cfde9d096b9. Unfortunately, I didn't leave myself enough breadcrumbs to track what instigated me to add that. I think someone suggested in another project that it's something every project should have and so I adopted it experimentally.
I'd like to ponder this some more, but I appreciate you sharing the suggestion.

Ok I deleted the extra workflow. I still think it's worth getting doing the doc fixes here

I agree that a lot of the changes herein are worthwhile. I'm a little less certain about others. In particular, there are two changes that blacken-docs makes with which I'm uncomfortable and likely to revert:

The conversion of multi-line expressions to single-line expressions clumps the arguments together, making them less distinct and discernible. Especially with documentation, whitespace can really help to convey an idea or to set the stage for a larger block. Consider for example:

In this block, the newlines are there to express that the user should probably have their parameters one per line. Just because they happen to fit on one line is not a good approach, especially when additional parameters are probably going to force the syntax (even when black) to be on multiple lines.
For actual code, the flux of these transforms is acceptable. For docs, it's an impediment to their core purpose.

The forcing of the more heavy double-quotes (both by pixels and by keystroke) in contradiction with Python's default repr is unnatural and violates this project's specified opt-out for that change. Unfortunately, due to asotille/blacken-docs#62, blacken-docs doesn't support the few preferences that black supports. For this reason, I'm going to remove blacken-docs from the pre-commit builds (at the skeleton).

I would like to keep the other changes.

Thanks for the contrib!

For that specific example you can use ..., to force black to explode that line

It's probably worth finding an alternative to check the syntax of these docs


fix(partial-rebuild/log): don't wait for replica if we can't partial rebuild

Update rpc api to access new rebuild log flag.
If there is no IO log in the child, this means we can't partial rebuild, so there's no point waiting for the replica to return, simply fault and full rebuild.

bors merge

bors cancel

bors merge


[Runtime] Harden SWIFT_DEBUG_LIB_PRESPECIALIZED_PATH.

Have SWIFT_DEBUG_LIB_PRESPECIALIZED_PATH use dlopen with RTLD_NOLOAD. We don't want it to allow loading arbitrary dylibs. Instead, a user can use something like DYLD_INSERT_LIBRARIES to load the dylib, which we will then pick up in the runtime, and processes that deny DYLD_INSERT_LIBRARIES will not be able to work around it with SWIFT_DEBUG_LIB_PRESPECIALIZED_PATH.
rdar://123643585

@swift-ci please test


Can't move the reaction centroid

It is not possible to move the reaction centroid. Users should be able to move the centroid.

To become able to move a reaction (centroid) node, the user can right-click on that node and enable 'Independent Position' option. There was a bug with displaying the the right-click menu in this situation which is now fixed by PR #110

To become able to move a reaction (centroid) node, the user can right-click on that node and enable 'Independent Position' option. There was a bug with displaying the the right-click menu in this situation which is now fixed by PR #110


Channel shutdown when OOM(Java heap space) occured

java.lang.OutOfMemoryError: Java heap space
2019-10-11 16:42:14.161 [AMQP Connection <IP_ADDRESS>:5672] ERROR o.s.a.rabbit.connection.CachingConnectionFactory - Channel shutdown: clean channel shutdown; protocol method: #method<channel.close>(reply-code=200, reply-text=Closed due to exception from Consumer (amq.ctag-9i7C8d-eOU7xPNGdcussZQ) method handleDelivery for channel AMQChannel(amqp://admin@<IP_ADDRESS>:5672/,1), class-id=0, method-id=0)

OutOfMemoryError caused MQ channel shutdown, application returns to avaliable after a period of time without restarting, but the method witch annotated @StreamListener could not consume messages in MQ，Restarting application can resolve this problem.
Is there a way to for MQ channel open automatically after channel shutdown?

OOM is a fatal JVM condition and there is not much anyone can do about it as there is simply not enough memory to do anything. So consider investigating what causes OOM in your code.


Remove kassane/cimgui

Based on: #27
closes: #26

Maybe not an ideal fix. Although, there is no clarification about the real problem with writeFiles.Step.
However, this avoids over engineering to write a customStep.

Just had a quick look over the PR, but didn't specifically test it. LGTM.


Root directory scratch files

Hi there, I am enjoying your plugin!
I've noticed that when running webpack with ImageminPlugin engaged, I get scratch files generated in my root directory with GUIDs for names and no extensions:
7bad0c4e-7322-4118-9d71-30b2b8ca5617
ef68099e-3ef9-4dbd-81c2-3bc4204f2cff
and the like.
For what it's worth I think it scales with the number of entry points, but I am not confident on that as fact.
My sincere apologies if it's from some combination of plugins, I've reduced it down to extract text plugin and style-loader / css-loader / sass-loader. It definitely goes away if I set disable: true, so that is what brings me here.

Hmm, I haven't noticed that, but then again I don't pay too much attention to the output folder. I can take a look at this later today or tomorrow. Would you be able/willing to post your webpack config somewhere?

I have the same problem, and people using image-loader have it too.
https://github.com/tcoopman/image-webpack-loader/issues/41


Fix MOAB canonical ordering during element splitting

Corrects implementation of MOAB canonical ordering. Changes are as follows:

Changes MOAB canonical ordering for both wedges and hexahedra to coincide with element splitting shown in ParaStell publication (Moreno, Bader, Wilson, 2024)
Adds documentation explaining MOAB canonical ordering for posterity

Closes #166

I'm not sure how we'd test canonical ordering of tetrahedra directly but one test that we should probably add is to ensure no elements with negative volume are present


Update eclipse timer

Updates to the eclipse timer so that it will show the time till totality (if in path of totality) or max eclipse, and the time left in partial eclipse, otherwise say the eclipse has passed

Looks great - thank you both!!


Error: unknown flag: --wildcard

when i run  the command line gobuster dir -u http://<IP_ADDRESS> -w /usr/share/wordlists/disbuster/director-list-2.3-medium.txt --wildcard getting error message
Error: unknown flag: --wildcard
why is that ?

because there is no wildcard flag. use the —help

thanks


flutter_openim_widget 拉取问题

如果使用 flutter_openim_widget: ^1.05 替代git url 指定，会出现
Because openim_enterprise_chat depends on flutter_openim_widget any which doesn't exist (could not find package flutter_openim_widget at https://mirrors.tuna.tsinghua.edu.cn/dart-pub/), version solving failed.

实际上 openim_enterprise_chat 这个依赖是没有的

flutter_openim_widget是ui库，目前只能通过git依赖。
flutter_openim_sdk是IM插件，目前版本是1.0.5
  flutter_openim_widget:
    git:
      url: https://github.com/hrxiang/flutter_openim_widget.git


Support .pkpasses pass combination passes

When I attempt to add a .pkpasses file with .addPassFromUrl(), I get an error "Error: The pass is invalid".
Would it be possible to add support for adding .pkpasses files?

Unfortunately, the .pkpasses format is not officially supported for adding passes to Apple Wallet. Apple Wallet was initially designed to work with .pkpass files, which contain a single pass and are signed with a certificate issued by Apple. The .pkpasses format acts as a container for multiple .pkpass files, but, as noted in discussions on the Apple Developer Forums, this format is not supported by most devices and versions of iOS for direct addition to Wallet.

Huh, that's odd that they're only supported in Safari. Thanks.

Unfortunately, the .pkpasses format is not officially supported for adding passes to Apple Wallet. Apple Wallet was initially designed to work with .pkpass files, which contain a single pass and are signed with a certificate issued by Apple. The .pkpasses format acts as a container for multiple .pkpass files, but, as noted in discussions on the Apple Developer Forums, this format is not supported by most devices and versions of iOS for direct addition to Wallet.

can you please provide us the procress to download passes


Updating records without mangling edges

I'm playing around with the pyorient driver and I've encountered a "I must be doing it wrong" problem.
Consider this sample code:
orient_client.db_open( "database", "admin", "admin" )
record = orient_client.query("select from V where some_field = 'some value'")[0]
cluster_id = parse_cluster_id(record._rid)
cluster_position = parse_cluster_position(record._rid)
record.oRecordData["some_field"] = "some other value"
orient_client.record_update(cluster_id, cluster_position, record)
When I run this code the field is updated correctly, however the IN/OUT edges get mangled. This is because the deserialization of binary data in the query result stores the edges as OrientBinaryObject (base64 strings). When the record_update() is written, the edge collections are stomped with these strings.
How do I read, update, write without tripping over the missing ridbag handling in pyorient?

Hi @ryan-stateless ,
i think this is a bug, i will investigate, thanks for reporting it.

Moved https://github.com/mogui/pyorient/issues/97


Pair Extraordinaire achievement not working

I have fulfilled the requirements for the achievement in the title of this issue, and have waited 16 hours since completing it, but it is still failing to show on my profile.

@CodeMaster7000, I think the best place to go for this issue is the GitHub community in the discussions area. The achievements here are to inform about the achievements made by GitHub themselves.

@SmashedFrenzy16 Thanks, but there is a chance someone responds and attempts to fix the issue here.

How you didn't got it. I got it see my profile..? it's confusing.

@PSGitHubUser1 Despite adding someone as a co-author to a merged PR, I still have not obtained the achievement.

Oh

In my experience, these achievements can be quite glitchy or take a long time to show up. I closed the issue I had just made and edited this one since I was having trouble with the YOLO one.


[YOLO]yolo op added in frontend and removed from topi

The yolo op is used only in darknet and since its not generic and can be acheived by frontend itself, i implemented the op in darknet.py and removed all the existing yolo_op registration, testcases and topi code.
@PariksheetPinjari909 @yzhliu  Please review. Thanks in advance.
Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from Reviewers.

As yolo, region are not generic ops and looking at the progress of darknet, moving these ops to frontend is a good idea. Thanks @siju-samuel for bringing in this PR. Let's check if we can bring region to frontend as well. Any views on this @yzhliu

@PariksheetPinjari909 I have already tried this.
But im facing a strange issue with concatenate for some specific values in graph_runtime create.
I reported an issue here
https://discuss.tvm.ai/t/graphruntimecreate-is-in-deadloop/1032
Waiting for replys.
This can be replaced with the below code and all the region op in topi/nnvm can be removed.
def _darknet_region(inputs, attrs):
    """Process the region operation."""
    num = attrs.get('n', 1)
    classes = attrs.get('classes', 1)
    coords = attrs.get('coords', 0)
    background = attrs.get('background', 0)
    softmax = attrs.get('softmax', True)
    input_shape = attrs.get('shape')

    split_size = classes + coords + 1;
    intermediate_shape = (input_shape[0], num, split_size, input_shape[2], input_shape[3])
    data_block = _sym.reshape(inputs[0], shape=intermediate_shape)
    split_res = _sym.split(data_block, indices_or_sections=split_size, axis=2)
    splits = []
    for i in split_res:
        splits.append(i)
    splits[0] = _sym.sigmoid(splits[0])
    splits[1] = _sym.sigmoid(splits[1])
    if not background:
        splits[coords] = _sym.sigmoid(splits[coords])
    if softmax:
        offset = coords + int(not background)
        softmax_input = _sym.concatenate(*splits[offset:], axis=2)
        softmax_output = _sym.softmax(softmax_input, axis=2)
        data_block_1 = splits[:offset]
        splits = data_block_1 + [softmax_output]
    concat_out = _sym.concatenate(*splits, axis=2)
    return _sym.reshape(concat_out, shape=input_shape), None

Thanks @PariksheetPinjari909 @siju-samuel this is merged


Fix 404 and point to correct document.

I was following the examples and couldn't follow this link. After a bit of code archeology I'm assuming it should point to this location.

@ciriarte Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@ciriarte Thank you for signing the Contributor License Agreement!


[ext-authz] add e2e test for ingress case

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[X] Security
[] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Pull Request Attributes
Please check any characteristics that apply to this pull request.
[X] Does not have any changes that may affect Istio users.

@xulingqing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

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

@xulingqing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
502022aabac38791609c80047593dc3c44939c00
link
/test lint_istio

gencheck_istio
502022aabac38791609c80047593dc3c44939c00
link
/test gencheck_istio

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

integ-security-k8s-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
502022aabac38791609c80047593dc3c44939c00
link
/test integ-security-multicluster-tests_istio

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

integ-security-k8s-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

integ-security-k8s-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-pilot-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-pilot-multicluster-tests_istio

integ-security-k8s-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
d6fa9b21c1d3e34098b324c6c7be29c6f7c56deb
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
3cd417d14df35745259f35187fbef59a17d76577
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
e3c1281f9c2d4296c764129d7427861a715386f1
link
/test integ-security-multicluster-tests_istio

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

unit-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test unit-tests_istio

integ-security-k8s-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-multicluster-tests_istio

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

/retest

/retest

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
4931a07e104dd54ec5b3c949b66414e4972aae8c
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

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

/retest

/retest

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-multicluster-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-multicluster-tests_istio

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-multicluster-tests_istio

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

@xulingqing: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-k8s-tests_istio

integ-security-multicluster-tests_istio
34e40e23004f8bbc9a3c57a9a9106d6633d107cc
link
/test integ-security-multicluster-tests_istio

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


Support for custom file types

Is there a way to load a file of type other than the ones supported by format?
I'm working on a custom widget and trying to load a .tsx file (to later serialize with TS api and consume as AST), but the issue is that I cannot find a proper formatter for such use case. I can use frontmatter and set the field name to body, but then when using a nested collection it starts complaining about a missing title (which makes sense, since the formatter is not the proper one).
I had the same issue when working with .json files, since the json formatter returns a field, not the full json content.
If it's not supported currently, does it make sense to add support for registering custom formats? or maybe introducing a new formatter that treats the file content as body and doesn't attempt to parse or serialize?

At current I am not planning on expanding the available file formats, and custom formats are not yet supported.
Adding the ability to provider a custom formatter would be doable. I'll keep this in thr backlog for the future.


fix: use default indexes if non where given by the lockfile

Fixes:
/home/runner/.pixi/bin/pixi install --locked --manifest-path pyproject.toml --color always
  thread 'main' panicked at /home/runner/work/pixi/pixi/src/install_pypi.rs:611:10:
  called `Option::unwrap()` on a `None` value
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: The process '/home/runner/.pixi/bin/pixi' failed with exit code 101

cc: @pavelzw


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


File compaction in Raptor

Compaction of files that are not sorted is simply appending files
Sorted files are merge sorted
Files that represent time ranges need to be merged across time ranges (not implemented in this PR)

"Compaction for non-temporal shards"

It looks like there are test failures (see Travis)

Looks good


Add W3C Caveat to Browser Support Info

The README states that "All current browsers are fully supported", which is not technically true. As noted in the docs

When running in a browser (for example by using browserify) the browser's native WebSocket implementation is used, and thus just the first and second arguments (requestUrl and requestedProtocols) are used (those allowed by the W3C WebSocket API).

As someone who was not familiar with this, I spent a lot of time trying to debug the inconsistencies with the library between Node and the Browser.
Even better would be if there were a way to throw an error when someone tries to pass headers, etc. into the W3C client from the browser.

So this is why my 'Authorization' header was missing on server side. Is there any workaround to pass header? @baileytincher

Guys, it clear that the docs explain that limitation (which is not a limitation in this library but in the W3C WebSocket interface). What you are asking is like "make this library warn the user if he didn't read the docs". We shouldn't need to cover that. We write docs for something.

Sorry, now I've realized that this is a PR rather than an issue. Reopening and merging.


Stop credential controller from syncing in manual mode

We need this to fix syncing of credentials in manual mode.
cc @openshift/storage

/retest

/assign @bertinatto

/assign @deads2k

@deads2k moved the code to use lister for CloudCredential objects. PTAL.

/retest

/lgtm

/cherry-pick release-4.10


Angular authentication Guidelines

Login Guidelines
Refresh Token Guidelines
Auth Guard Guidelines

I do agree with @earthpyy krub, we need to draw the line between standard and feature template.

ok. I think i will remove login and authguard topic and add LocalStorage and authentication hacking prevention guidelines


Could not resolve all dependencies for configuration ':_armv7DebugApkCopy'.Could not resolve all dependencies for configuration ':_armv7DebugApkCopy'.

Error: cmd: Command failed with exit code 1 Error output:
FAILURE: Build failed with an exception.

What went wrong:
A problem occurred configuring root project 'android'.

Could not resolve all dependencies for configuration ':_armv7DebugApkCopy'.
Could not resolve org.xwalk:xwalk_core_library:24+.
Required by:
:android:unspecified
Could not resolve org.xwalk:xwalk_core_library:24+.
Failed to list versions for org.xwalk:xwalk_core_library.
Unable to load Maven meta-data from https://download.01.org/crosswalk/releases/crosswalk/android/maven2/org/xwalk/xwalk_core_library/maven-metadata.xml.
Could not GET 'https://download.01.org/crosswalk/releases/crosswalk/android/maven2/org/xwalk/xwalk_core_library/maven-metadata.xml'. Received status co
de 504 from server: Gateway Time-out

It's down again. It seems to be very unreliable. Any work aounds for this?

The problem has been solved. Thank you.


[FEATURE]: Add new @Injectable decorator.

Describe the solution you'd like
A new decorator called @Injectable which is a class-level decorator, that will mark a class as injectable, then the developer can use the constructor to inject provided classes, this would then work better for things like unit testing, and is a common approach, in frameworks like Symfony (PHP).
Additionally due to the way the above would work, variable based injecting would be impossible, so maybe offer an optional array of strings inside of the @Injectable decorator that can be used to map variables or other properties to support that and to prevent it breaking existing support for the IDE type hints from VSCode, you can use null to define a pre-configured item ignoring it allowing you to define where things would be in the order specified.
See code examples.
Describe alternatives you've considered
N/A
Additional context
Example of standard injection.
import { Injectable } from '@symbux/orm';
import { MessageBroker } from './message-broker';

@Injectable()
export class ExampleController {
    public constructor(private broker: MessageBroker) {}
}

Example of variable injection support.
import { Injectable } from '@symbux/orm';
import { MessageBroker } from './message-broker';
import { Logger } from './logger';

@Injectable(['settings', null, null, 'app.version'])
export class ExampleController {
    public constructor(
        private settings: {[key: string}: any},
        private broker: MessageBroker,
        private logger: Logger,
        private version: string
    } {}
}

Project is deprecated, in favour of @sodacore/core project.


Optional query parameters are marked as required in the UI

Using springfox 2.8.0 to generate UI out of annotations, generated by the swagger-codegen.
Generated code (actually correct, see last line):
  @ApiOperation(value = "Get all users", nickname = "getUsers", notes = "Get all users ", response = User.class, responseContainer = "List", authorizations = {
       @Authorization(value = "user_auth", scopes = {
           @AuthorizationScope(scope = "ADMIN", description = "Manage users"),
           @AuthorizationScope(scope = "USER", description = "Maintain own user")
           })
   }, tags={ "user", })
   @ApiResponses(value = {
       @ApiResponse(code = 200, message = "Success", response = User.class, responseContainer = "List"),
       @ApiResponse(code = 400, message = "Invalid ID", response = Error.class),
       @ApiResponse(code = 404, message = "User not found", response = Error.class) })
   @RequestMapping(value = "/users",
       produces = { "application/json" },
       method = RequestMethod.GET)
   ResponseEntity<List<User>> getUsers(@ApiParam(value = "Filter the list") @Valid @RequestParam(value = "$filter", required = false) String filter);

The UI insists that the filter query parameter is required:

There is no additional springfox relevant configuration in the service.
I may be wrong, but for me looks like a bug. Please let me know if I can provide any additional input to help investigating/resolving it. Thanks!

Certainly seems like it. Thanks for reporting

It looks like the problem still exists.
With version 2.9.2 and the following the code:

you can still see the params marked as required:

    @GetMapping({ "/v1.0" })
    public Flux<Post> getPosts(@RequestParam Optional<String> maxId) {

Version 3.0.

Any resolution for this issue? It still exists

Works fine in version 2.9.2 when require=true is specified in @ApiParam


Open economy option

Per a suggestion from Ken Judd, let's allow for an open economy option for OG-USA.
This means the interest rate is exogenous.  To accommodate this, we'll need to pass a boolean denoting open economy through to execute.py.  This will trigger calls of different SS and TPI scripts - ones where the "outer loops" (those that pin down prices) will now omit interest rates, since they will no longer be endogenous.

I've branched smallopen from master. I'm planning to work on this topic with @chrisrytting. Feel free to jump in and let me know if/when I'm making mistakes in workflow.

@salimfurth and @chrisrytting welcome aboard.

Could @rickecon or @jdebacker satisfy my curiosity on two aspects of the broader model?

The SS model uses 4 moments to test for convergence. Is there a theoretical or practical reason these 4 were chosen? In the small_open model, we're effectively dropping to 3 tests, since r=r_new for every iteration. If we're worried about funny business at corner solutions we can add another test or two easily.
Why is steady state immigration negative (or am I reading it wrong)?

The steady-state solution in the baseline model is really (2SJ) + 4 equations and unknowns, where S is the number of periods an individual lives and J is the number of ability types. The 2SJ variables are the S savings decisions and S labor supply decisions of each of J individuals over their respective lifetimes. The other four equations are basically characterizing equations for the interest rate (r), wage (w), lump sum transfer (T^H), and income factor (factor). These four equations are arrived at by substituting together combinations of market clearing conditions, firm's FOC's, and definitions that include those four variables (see "Integration..." paper). So the SS solution is not really four moments. It is an inner-loop that solves for the 2SJ savings and labor supply decisions of households given r, w, T^H, and factor. Then we solve for the r, w, T^H, and factor using a bisection method. @salimfurth , feel free to call me if you want to chat.

@salimfurth , to answer your second question, let me ask what you are looking at?  Immigration rates are a vector of length S.  For some ages, in the SS, these are slightly negative.  Overall, the population is growing: SS pop growth:  0.00129077232238.
While it may seem odd that any immigration rates are negative, let me add:

Immigration rates for all ages are strictly positive (net in-migration) until 120 years from the current period.  It's hard to predict that far in the future, but one could imagine some net out-migration.
If we keep fertility and mortality rates constant over time, we have to adjust immigration in order for the population to become stationary at some point.  Alternatively, one could adjust mortality or fertility in the future, but we chose to adjust immigration since its future path may be less predictably anyway.

@salimfurth . If you look at this figure of the estimated immigration rates, you'll notice three features.

Estimated immigration rates are small (most less than 0.7%), except for the very young and the very old. And there are very few people in that over-90 age category.
The adjusted immigration rates are very close to the original immigration rates.
A few adjusted immigration rates are negative for given ages, but are very close to zero. Only one original immigration rate is negative. Aggregate immigration rates are strongly positive.

@salimfurth . See Appendix A-1 of the "Integration..." paper for a detailed description of the demographics.

Well this is odd: the discrepancy is associated with shrinking S. When I set S=40, I get a choppy, mostly negative immigration rate, in both the early periods and the steady state.

Inside SS_solver (where I encountered the adjustments associated with immigration), I calculated (omega_SS*imm_rates).sum() = -0.0084.
But when I set S=80, I get a graph like the one you posted, and omega_SS*imm_rates).sum() = 0.0024. So it flips immigration's impact on demographics by a full percentage point.
I'm not sure this is a problem at all. It might resolve if I

Ignore that last incomplete sentence.

For completeness, I should note that switching between J = 2 and J = 7 makes no difference; the immigration reversal is driven by the change in S.
Over the range where it solves (20<S<81), steady state immigration appears to be a monotonic, increasing function of S that is zero at S=66. I don't know if that's worrisome. (Tagging @jdebacker & @rickecon).

@salimfurth No, not worrisome. This is a known issue with the demographics. Because the immigration rates are essentially a residual, more is required of each immigration rate i_s for a particular age when the size of each period gets larger (S gets smaller). So it is intuitive that immigration rates and mortality rates would get larger as the size of a period gets larger, because both of those rates are cumulative. That more immigration rates are negative simply means that current mortality rates and fertility rates need to be tamped down more in order to match population dynamics.

Any demographic approach has its problems. This model allows one to put in whatever demographics one wants.
The leading approach is Nishiyama and Smetters (QJE, 2007) and Nishiyama (JEDC, 2015). They use a method in which they project changing fertility, mortality, and immigration rates by age over time (this is what the Soc. Sec. Admin. does). Two problems are that it is hard to forecast how fertility and mortality rates will change, and we don't have good data on immigration rates by age.
One of the strengths of our approach is that it backs out implied immigration rates, where we might not be very confident in immigration rates taken directly from the data. One could argue that holding those rates constant over time is too strong an assumption. But we could change the model to allow for those rates to change.

I just realized that all my commits aren't showing up on GitHub online - I'm using the GitHub shell application on this computer to manage things. It seems like the problem might be that I accidentally branched from open-source-economics/OG-USA instead of from salimfurth/OG-USA as intended. Thus, it lets me "commit" on the GitHub shell but I guess that doesn't get saved on any repo. It won't let me "publish". How should I proceed, since I don't want to lose my work?

@salimfurth - what I would do is the following:

Save repos/OG-USA in another directory (e.g. repos/backup/OG-USA)
Delete repos/OG-USA
Clone your fork to repos/OG-USA : git clone https://github.com/salimfurth/OG-USA.git
from your repo, checkout the branch you want to work in (e.g. checkout -b open_econ)
Copy the files from repos/backup/OG-USA that you had changed into repos/OG-USA
Stage your files for commit: git add path\filename
Commit your changes: git commit -m "changes to start open economy model"
Push changes to remote repo: git push origin open_econ (replace open_econ with whatever your branch name is)
Open PR when ready

BTW, there's a little learning curve, but I recommend using the command line for your git workflow.

What's the advantage of command line? I find myself making constant typing errors, unable to track what's going on, etc, constantly. It also doesn't track past actions, so I'm always pretty lost when I start doing anything in it. There have to be some major advantages to overcome a setup that is so conducive to human error.

@salimfurth , look for email

Great.    Thanks!

One of the things I added was distinct firm versus household interest rates within the small_open framework. That allows households to face an unmodeled financial friction which lowers their rate of return relative to the firm's rental rate.

@salimfurth a few comments:

I was able to run your code just fine on a Mac.
SS and TPI results for the baseline seem reasonable, but it might be a good idea to compare to the same baseline without the open econ assumption.
When I run the baseline and reform and calculate percentage changes in the factor prices and economic aggregates, I get very little (essentially zero) change for all to these series.  @rickecon  - can you remind me what is in the reform tax function pickle in this repo?  The  10% cut? Something else?  My prior was that the responses to a tax cut would be larger in the open economy model.

Re the financial friction. I like this idea and it seems to fit easily in here.  But what happens to that wedge?  I suppose you model it as a real cost - the difference between what the firms pay for rent and what the households get leaves the economy.  Is there good reason to do this rather than model the wedge as being due to traditions costs - so that the income is returned to the households, but via a financial intermediary rather than from a goods producing firm?

Thanks, @jdebacker!
On the financial friction, the disappearing wedge makes sense when the financial sector is elsewhere. So for applications where the economy modeled is a state or a small country, it's sensible to assume that some intermediation is done by distant bankers and is costly, but not worth modeling in explicit detail. Obviously, a full financial sector buildout would be useful for some applications, but that would more naturally take place within the closed economy model.

And, @jdebacker, regarding the "Reform" option, I don't actually think there is a reform, at least not in the run_micro:False environment where I'm working.

@salimfurth, run_micro:False referee to whether tax functions are estimated from the micro data.  If this is false, you  can still run a reform, you just need to have tax function parameters that summarize the reform.  In your case, I'm uncommenting the reform run in run_ogusa_serial.py.  The script then looks for the `TxFuncEst_policy.pkl' file with the reform parameters.  Thing is, I can't remember what the reform was that these parameters came from.  I think it's a reform @rickecon ran recently, though.

@jdebacker, I ran the code on both TxFuncEst_policy.pkl and TxFuncEst_baseline.pkl (with small_econ:False and guid:'' in both cases) and got identical steady states. When I leave guid:'mtr_38' in the reform, it looks for another path and can't find the pickle file it wants.

@salimfurth . The current versions of TxFuncEst_baseline.pkl and TxFuncEst_policy.pkl are currently identical. The guid' is a dictionary item that adds suffixes to those files so that multiple reforms can happen at once and still be differentiated from one another. So for any current runs, leave guid:''. Also, I will e-mail you a TxFuncEst_policy.pklthat is different from the currentTxFuncEst_baseline.pkl`. This file comes from the experiment that we ran in the "Integration..." paper.

@salimfurth Try this pickle for the policy.  It's a 10% reduction in all marginal rates on ordinary income and a doubling of the standard deduction.  I think a good check is to run the baseline and reform through (so make sure lines 86-97 and line 107 are uncommented in run_ogusa_serial.py.  Also, add: np.savetxt('OpenEconPctChanges.csv',pct_changes,delimiter=",") after line 48 in postprocess.py to save the percentage changes to a csv file.  We can then compare to the closed economy version.

@rickecon ^

@jdebacker , @salimfurth . We had left those two baseline and policy tax function pickles the same because they were only used for the Travis CI automatic testing of pull requests.

Here are the results of reforms in Closed and Open economies, and the difference between Closed and Open with r=0.033.
![deltas](https://cloud.githubusercontent.com/assets/16611986/18970965/53db8e4a-8661-11e6-882a-
a5fb2acdfcb8.png)

That didn't work; trying again. This used @jdebacker's reform above, btw.

@salimfurth - why no change in wages with the open economy model?

I think that's just a standard open-economy result, @jdebacker.
From the firm's FOC for capital, the capital-labor ratio can be expressed as a function of r and parameters.
Combining the two FOC's, the wage rate can be expressed as a function of parameters, K/L, and r. Importantly, labor taxes don't enter into the labor demand curve. Thus, when r is fixed by world markets, pretax wages are fully determined by world markets.
A linear increase in capital taxes is easy to include, since it just shifts the exogenous r. But taxes levied at the firm level in nonlinear fashion can clearly distort this nice representative-firm math.

@salimfurth Thanks for the explanation.  This make sense.

@salimfurth Do we have any outstanding questions here?  If not, want to go ahead and open a PR?

@jdebacker, I don't know what questions to ask. I'm happy to open a PR if you guys are satisfied, but I don't feel qualified to say I have confidence in the model.

Closed via PR #249


Fix nits in the change runtime containerd page

There are two commits in the PR. The first one fixes a link. The second one applies some line wrapping changes and fixes some trivial nits.

/lgtm

@divya-mohan0209 would you be happy to see these changes merge as-is? We could open a good-first-issue follow up that describes the extra tidying.

@sftim : Absolutely! Not a problem at all :)

/approve


Fail to parse YAML content in latest version

I'm getting the same error like in same issue, but with latest version "asyncapi-docgen": "^1.10.3". Please help.

Looking into it. Thanks for reporting!

Hey @mikekekekeke. I just released a new version of the package with the examples on the README fixed. Check it out: https://github.com/asyncapi/docgen#as-a-module-in-your-project.

It working now. Thanks.


Remove unnecessary files from npm package

This adds a files property to the package.json that whitelists what files you want in the published npm package. This reduces unnecessary files installed on the machine when the package installed. I also removed the unused directories property.

yay!

Thanks @dougwilson :+1:


Cost models description should be held in a pop up link similar to overview

Describe the bug
Cost models description should be held in a pop up link similar to overview
To Reproduce
Steps to reproduce the behavior:

Go to 'Cost models'
See description below title

Expected behavior
This description should probably sit in a pop up similar to what we have on the overview page
Screenshots

Desktop (please complete the following information):

OS: Fedora
Browser Firefox
Version 70

Additional context
Noticed this testing against CI Beta

@nlcwong - in the mock I don't remember seeing popover to display the description. Is this necessary here?

Spoke with @nlcwong and it was one of the things we had to take care of in the "fit and finish" phase.
I will be working on this today.
Thanks for your ticket.


⚠ Samsung has degraded performance

In b8864a9, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2110 ms

Resolved: Samsung performance has improved in e4b219e.


level of parallelism in eventalign

Trying to understand the effects of '-t' options. The only use I can find is:
omp_set_num_threads(opt::num_threads);
but the main loop seems to be single thread if I'm not mistaken.
Should for example '-t 8' be any faster than default?

Threading is not implemented yet, sorry. I'll keep this open as a reminder to do this. Thanks for testing nanopolish and the bug reports

On Jun 16, 2015, at 8:31 AM, Vadim Zalunin<EMAIL_ADDRESS>wrote:
Trying to understand the effects of '-t' options. The only use I can find is:
omp_set_num_threads(opt::num_threads);
but the main loop seems to be single thread if I'm not mistaken.
Should for example '-t 8' be any faster than default?
—
Reply to this email directly or view it on GitHub.

Now implemented: 5309c1aee58


Read meh kyoto ako

ShinyBubble kyot

who r u

tf HAHAHAHAHA

https://lycol50.github.io/web/
@ShinyBubble hahaha


Cases where neq==0 with pytorch 0.4.1

Need a fix for cases without equality constraints with pytorch 0.4.1.
For example:
import torch
from qpth.qp import QPFunction, QPSolvers

N, D = 4, 16
v = torch.randn(D)
L = torch.randn(N, D)
x = QPFunction(solver=QPSolvers.PDIPM_BATCHED)(
    torch.matmul(L, L.t()),
    torch.matmul(v, L.t()),
    torch.eye(N),
    torch.zeros(N),
    torch.Tensor(),
    torch.Tensor()
)

Stack trace:
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-1-c5f8050018cf> in <module>()
     11     torch.zeros(N),
     12     torch.Tensor(),
---> 13     torch.Tensor()
     14 )

___/lib/python3.6/site-packages/qpth/qp.py in forward(self, Q_, p_, G_, h_, A_, b_)
     92             zhats, self.nus, self.lams, self.slacks = pdipm_b.forward(
     93                 Q, p, G, h, A, b, self.Q_LU, self.S_LU, self.R,
---> 94                 self.eps, self.verbose, self.notImprovedLim, self.maxIter)
     95         elif self.solver == QPSolvers.CVXPY:
     96             vals = torch.Tensor(nBatch).type_as(Q)

___/lib/python3.6/site-packages/qpth/solvers/pdipm/batch.py in forward(Q, p, G, h, A, b, Q_LU, S_LU, R, eps, verbose, notImprovedLim, maxIter, solver)
    176         rs = ((-mu * sig).repeat(nineq, 1).t() + ds_aff * dz_aff) / s
    177         rz = torch.zeros(nBatch, nineq).type_as(Q)
--> 178         ry = torch.zeros(nBatch, neq).type_as(Q)
    179
    180         if solver == KKTSolvers.LU_FULL:

RuntimeError: sizes must be non-negative

Suggestions?

Thanks, I've fixed this and uploaded a new version to pypi.

Awesome!  Same fix for CVXPY as well please:
qpth/qp.py, line 99: nus = torch.Tensor(nBatch, self.neq).type_as(Q)

Fixed there too and uploaded to pypi (but I didn't test it so let me know if I need to change anything else)


Issue with documentation

I just saw that the docs at http://browser-update.org/customize.html contain an error. The option is called: shift_page_down not shift_down_page.

Thank you.
This is fixed.


OpenId for Sunstone

Author Name: VIVOSS company (VIVOSS company)
Original Redmine Issue: 2675, https://dev.opennebula.org/issues/2675
Original Date: 2014-01-24

This patch adds OpenID feature for OpenNebula 4.4.0 Sunstone server.

Gem requirements

omniauth
omniauth-openid
ruby-openid

Third party software
Jquery-ui is required for OpenID login page.
It should be placed into sunstone/public/vendor/4.0/jquery-ui-1.10.3
Visual theme is smoothness. If any other version or theme is to be used,
corresponding changes should be made to the login.erb

Installations
This patch adds some new files, but OpenNebula setup is not modified.
So these files have to be copied to due places manually.

sunstone/
.
├── etc
│   └── sunstone-server.conf
├── public
│   ├── js
│   │   └── openid.js
│   └── vendor
│       └── 4.0
│           └── jquery-ui-1.10.3
├── sunstone-openid.rb
└── views
├── _login_standard_new.erb
├── _openid_check.erb
└── _openid.erb

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2014-01-30T20:37:59Z

We have also to devise a general method to easily add new extensions, and/or contribute this as an addon.

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2014-07-21T14:47:36Z

This will be considered for the next release, after 4.8

Original Redmine Comment
Author Name: Daniel Dehennin (Daniel Dehennin)
Original Date: 2014-07-19T15:08:11Z

Ruben S. Montero wrote:

We have also to devise a general method to easily add new extensions, and/or contribute this as an addon.

+1 for pluggable authentication.

Original Redmine Comment
Author Name: VIVOSS company (VIVOSS company)
Original Date: 2014-07-21T06:16:38Z

Daniel Dehennin wrote:

+1 for pluggable authentication.

Omniauth that used in the attached patch already uses authentication plugins. But some specific changes for GUI, plugin activation and query processing are also required.

implemented in https://github.com/OpenNebula/one/issues/3591


Support for Lua as a rules language

I was wondering if you have any plans to support Lua for the definition of rules and implementation of the Alpha nodes. This is a different question/recommendation than was raised in #53.
The three supported languages are obviously much more popular than Lua, but Lua is the go-to choice for embedding. There are at least two data processing tools that use a Lua sandbox that could take advantage of Durable Rules (https://github.com/mozilla-services/heka and https://github.com/mozilla-services/hindsight).
Most languages have some support for embedding Lua so it might give those using other languages an option as well (#130).
I'm interested to hear your thoughts. Thanks for the awesome project.

Hi, thanks for posting the question. I'm sorry for the delay in my reply. I have focused on supporting Python, Ruby and node.js because of the large audience. I haven't considered supporting Lua though. In fact I was thinking of implementing the Beta tree as a redis C extension and making redis optional. Offering the rules engine through Lua for embedded sandboxing sounds very interesting.

I saw you talk a little about that during the Q&A in your redisconf 17 talk: https://youtu.be/aRT8kfPmt-0?t=29m23s. Which you should add to the README by the way.
Thanks again for your thoughts. I've really enjoyed watching this project progress.


Kendalltau calculation variance

My issue is about bug in the variance calculation and therefore incorrect p-values
####original code
elif method == 'asymptotic':

    # con_minus_dis is approx normally distributed with this variance [3]_

    var = (size * (size - 1) * (2.*size + 5) - x1 - y1) / 18. + (

        2. * xtie * ytie) / (size * (size - 1)) + x0 * y0 / (9. *

        size * (size - 1) * (size - 2))

    pvalue = special.erfc(np.abs(con_minus_dis) / np.sqrt(var) / np.sqrt(2))``

Multiplication by 2xtieytie in second line of var formulae above is icorrect. It should be as below according to wikipedia:
    var = (size * (size - 1) * (2.*size + 5) - x1 - y1) / 18. + (

        xtie * ytie) / (2.* size *(size - 1)) + x0 * y0 / (9. *

        size * (size - 1) * (size - 2))

    pvalue = special.erfc(np.abs(con_minus_dis) / np.sqrt(var) / np.sqrt(2))..

xtie is sum(t[i]*(t[i] - 1))/2 (note the division by 2); ytie is defined similarly.  If you take that division by 2 into account, the formulas work out to be equivalent.
And as a sanity check, we can compare the p-values computed by scipy.stats.kendalltau and by cor.test in R.
Here's SciPy:
In [16]: x = np.array([1, 3, 5, 7, 9, 9, 10])

In [17]: y = np.array([0, 1.5, 1.5, 1.5, 4, 5, 9])

In [18]: kendalltau(x, y)
Out[18]: KendalltauResult(correlation=0.8959786703810408, pvalue=0.0070524199492218)

And here's R:
> x <- c(1, 3, 5, 7, 9, 9, 10)
> y <- c(0, 1.5, 1.5, 1.5, 4, 5, 9)
> cor.test(x, y, method='kendall')

	Kendall's rank correlation tau

data:  x and y
z = 2.6944, p-value = 0.007052
alternative hypothesis: true tau is not equal to 0
sample estimates:
      tau
0.8959787

Warning message:
In cor.test.default(x, y, method = "kendall") :
  Cannot compute exact p-value with ties

They compute the same value for tau and for the p-value.
I'm closing the issue, but let us know if I missed something and you think there is still a problem.


HADOOP-17732. Keep restrict-imports-enforcer-rule for Guava Sets in hadoop-main pom

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
16m  7s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m  0s

trunk passed

+1 :green_heart:
compile
22m 49s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
compile
18m 48s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
mvnsite
26m 42s

trunk passed

+1 :green_heart:
javadoc
7m 40s

trunk passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
7m 55s

trunk passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
shadedclient
134m 31s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 39s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
32m 23s

the patch passed

+1 :green_heart:
compile
21m 43s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javac
21m 43s

the patch passed

+1 :green_heart:
compile
19m 28s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
javac
19m 28s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
21m 13s

the patch passed

+1 :green_heart:
xml
0m 15s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
7m 44s

the patch passed with JDK Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04

+1 :green_heart:
javadoc
7m 38s

the patch passed with JDK Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

+1 :green_heart:
shadedclient
30m 14s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
795m 23s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
1m 26s

The patch does not generate ASF License warnings.

1060m  5s

Reason
Tests

Failed junit tests
hadoop.tools.fedbalance.procedure.TestBalanceProcedureScheduler

hadoop.tools.fedbalance.TestDistCpProcedure

hadoop.cli.TestErasureCodingCLI

hadoop.mapred.uploader.TestFrameworkUploader

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3049/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3049

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml

uname
Linux 1808e9a69b5d 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d8564793e166ac3bc42650f46f731ab744c8de34

Default Java
Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.10+9-Ubuntu-0ubuntu1.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_282-8u282-b08-0ubuntu1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3049/1/testReport/

Max. process+thread count
3385 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms hadoop-hdfs-project/hadoop-hdfs hadoop-hdfs-project/hadoop-hdfs-httpfs hadoop-yarn-project/hadoop-yarn hadoop-mapreduce-project/hadoop-mapreduce-client hadoop-tools/hadoop-distcp hadoop-hdfs-project/hadoop-hdfs-rbf hadoop-tools/hadoop-dynamometer hadoop-tools/hadoop-aws . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3049/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Add excludeOverriden to QueryOptions

Currently I'm running into an issue with the Polymer.dart 0.17 port, https://github.com/dart-lang/polymer-dart/issues/531, where smoke will return multiple instances of a field when said field is declared in a superclass.
I would like to add an option that excludes duplicated fields/methods from the query results.

Considering the connection to reflectable, I'll inject a comment here:
Adding an excludeOverridden feature to smoke queries may be a perfectly valid choice, but there is a reason why overridden declarations are not excluded in dart:mirrors and (due to the compatible-unless-we-really-want-otherwise policy we have) in reflectable. The point is that there are two alternative points of view on the target substance that reflection may deal with: Runtime entities, and source code. From the runtime entity point of view, an object has no fields, but it may have getters and setters, including some getters and setters which have been created implicitly, based on a field declaration; from the runtime entity point of view there is no inheritance hierarchy, there is only an instance that has a certain behavior (consequently, overridden members are not available). From the source code point of view fields do exist, and each class along an inheritance chain up to Object is treated separately . Hence, with declarations (which uses the source code point of view) you get fields, no hierarchy, no hiding-of-overridden, etc.; and with instanceMembers you get no fields, only methods (including getters and setters, possibly generated).
The concept of excludeOverridden inherently mixes the two points of view, which makes me think that maybe you don't want it.  ;-)


Function run_process should be propagating stderr

Currently, when we make subprocess calls, the stderr is silently dropped, which leads to warnings printed by K being ignored.
We should be propagating it instead: https://github.com/runtimeverification/k/pull/2763#discussion_r937034967

We have a similar issue in the front-end: https://github.com/runtimeverification/k/issues/2731
We should maintain the same behavior between our tools so these two issues should be handled in a similar way.


Update README.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 85.879%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
298

Relevant Lines:
347

💛  - Coveralls


Dynamic radio options

Description
This pull request allows the options of a radio group to be injected via msg.options, similar to the dropdown node.  I used the dropdown node as a reference, because @joepavitt mentioned in this discussion that the dropdown node had the best implementation.
Example flow:
[{"id":"abe9724949be673f","type":"ui-radio-group","z":"0bff6d05f60fe1e6","group":"f90f857366c11ce8","name":"Dynamic","label":"Dynamic options","order":0,"width":0,"height":0,"columns":1,"passthru":false,"options":[{"label":"Option A","value":"A","type":"str"},{"label":"Option B","value":"B","type":"str"},{"label":"Option C","value":"C","type":"str"}],"payload":"","topic":"topic","topicType":"msg","className":"","x":2000,"y":60,"wires":[["bad4c408ebc7dffa"]]},{"id":"a370322f29aafcc3","type":"inject","z":"0bff6d05f60fe1e6","name":"Array<String>","props":[{"p":"options","v":"[\"D\", \"E\", \"F\"]","vt":"json"},{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"E","payloadType":"str","x":1790,"y":60,"wires":[["abe9724949be673f"]]},{"id":"ab8809585948e0db","type":"inject","z":"0bff6d05f60fe1e6","name":"Array<{value: String}>","props":[{"p":"options","v":"[{\"value\":\"G\"},{\"value\":\"H\"},{\"value\":\"I\"}]","vt":"json"},{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"H","payloadType":"str","x":1760,"y":100,"wires":[["abe9724949be673f"]]},{"id":"eb867ae2ec4bdf4c","type":"inject","z":"0bff6d05f60fe1e6","name":"Array<{value: String, label: String}>","props":[{"p":"options","v":"[{\"value\":\"I\",\"label\":\"option I\"},{\"value\":\"J\",\"label\":\"option J\"},{\"value\":\"K\",\"label\":\"option K\"}]","vt":"json"},{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"J","payloadType":"str","x":1720,"y":140,"wires":[["abe9724949be673f"]]},{"id":"bad4c408ebc7dffa","type":"debug","z":"0bff6d05f60fe1e6","name":"Selection","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":2180,"y":60,"wires":[]},{"id":"f93f76ca2489f270","type":"inject","z":"0bff6d05f60fe1e6","name":"Clear selection","props":[{"p":"payload"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","payload":"","payloadType":"str","x":1780,"y":180,"wires":[["abe9724949be673f"]]},{"id":"dd85a83308905382","type":"inject","z":"0bff6d05f60fe1e6","name":"Clear options","props":[{"p":"options","v":"[]","vt":"json"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"","x":1790,"y":220,"wires":[["abe9724949be673f"]]},{"id":"f90f857366c11ce8","type":"ui-group","name":"Demo","page":"8604ea49340f9d41","width":"6","height":"1","order":1,"showTitle":true,"className":"","visible":"true","disabled":"false"},{"id":"8604ea49340f9d41","type":"ui-page","name":"Home","ui":"be29745a6e568f30","path":"/page1","icon":"home","layout":"grid","theme":"092547d34959327c","order":-1,"className":"","visible":"true","disabled":"false"},{"id":"be29745a6e568f30","type":"ui-base","name":"UI Name","path":"/dashboard","includeClientData":true,"acceptsClientConfig":["ui-notification","ui-control"],"showPathInSidebar":false},{"id":"092547d34959327c","type":"ui-theme","name":"Theme Name","colors":{"surface":"#ffffff","primary":"#0094ce","bgPage":"#eeeeee","groupBg":"#ffffff","groupOutline":"#cccccc"}}]

Remarks:

I have NOT checked whether existing nodes in flows are somehow influenced by this new feature.  I am not sure whether their selection will be resetted.  Not enough Vue and D2 knowledge for that currently...
Please sqash the commit history.  I noticed at the last moment that I had another (ui-notification related) change in my branch, so I had to do some extra commits to revert those changes.  One file still pops up in my diff, but cannot get rid of it unfortunately...

Related Issue(s)

Checklist

[ X ] I have read the contribution guidelines
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

[ ] Upgrade instructions
[ X ] Configuration details
[ ] Concepts

[ ] Changes flowforge.yml?

[ ] Issue/PR raised on FlowFuse/helm to update ConfigMap Template
[ ] Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

[ ] Backport needed? -> add the backport label
[ ] Includes a DB migration? -> add the area:migration label

Ah damn I forgot to run the unit tests.  Will have a look to fix it as soon as I have time.

Tests fixed.  Ready for review.
After Joe is back from his holidays of course :-)


drivers: clock_control: clock_control_ra.c: clock divider fix

The clock divider value is not being applied as the address of the register to which it is being written is incorrect. A check of all RA MCU datasheets confirms that, in all cases, the SCKDIVCR register is at an offset of 0x20 (and not 0x21).

@nordic-krch, would you mind taking a look at this when you get time. thanks!

@henrikbrixandersen, do I need to do something else to get this merged? I see one of the tests failed but I believe this was due to a lack of resources, rather than anything in this fix.... Should I rebase and push again just to get the tests to re-run (although I think that will require people to approve again)?

@iandmorris  yes you can try to rebase. and yes that will require another round of approvals.


ImportError: cannot import name 'url' from 'django.conf.urls'

django.conf.urls.url() was deprecated in Django 3.0, and is now removed in Django 4.0+.

Covered through MR https://github.com/OmniDB/OmniDB/pull/1311


[RESOLVED] High ICMP ping response time

Problem started at 09:41:14 on 2023.06.09
Problem name: High ICMP ping response time
Host: MF-FG
Severity: Warning
Operational data: Value: 418ms
Original problem ID: 28463
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23132&eventid=28463

Problem has been resolved in 6m 0s at 09:47:14 on 2023.06.09
Problem name: High ICMP ping response time
Host: MF-FG
Severity: Warning
Original problem ID: 28463


[WIP] try to remove 'any' in the StoreValue union type

Thanks for flagging this! definitely something to figure out especially if there are logic errors as a result.

I might have misinterpreted some errors, I think the only problem is not handling the number case. (will push an updated commit soon)

I have updated the PR. What should we do with numbers? Previously there where given as rootId which we normally expect to be a string.

Wouldn't this only happen if the query has a sub selection and the store had a number for the reference id? That just seems like a condition that should never happen if we guarantee that reference IDs are always strings. So we should throw an error if we end up with a number in this case - it means either our code is wrong or the result doesn't match the query.


Initialize the Library

The first version of our Components Library is just this: A basic library, with the components and dependencies we do need to start building products.
It's only dummy content, and it isn't usefull as is. But is, literally, the step from 0 to 1. From nothing, to a library that extends vuetify.

This is such a good starting point. But, for me, it still needs more work to be moved to dev.
What do I think it needs? This:

[ ] 1. Add images / static files to the library (i.e: logo).
[ ] 2. Auto-export all the new components.
[ ] 3. Define the component structure  (atoms, molecules, and organisms; by functionality).
[ ] 4. Define the library naming (vuetify: v-element; quasar: q-element).
[ ] 5. Document how to use it in a project.
[ ] 6. Discover if, as a npm dependency, we will stop having the linting issues.

This is an open list, and an open discussion. In case someone think I'm missing something, or overthinking, or overengineering something, just comment it, so we can move faster and safer.

About the linting issues:
When importing the library as a local lib (import components from '../../components'), sometimes the file got linted, and (as is a minified file) it throws tons of errors.
I've moved (just to try) the project inside node_modules in the example, repo, and loaded as if there was an npm module. It works like a charm. No errors, no linting... So, it should work smoothly when we upload it to npm.

I've thougth that the points 1, 3 and 4 are not part of this version.
Why?
1. Add images / static files to the library (i.e: logo).
Actually, we don't need to add any image to a component, for now, so when we do, we will face that issue,.
3. Define the component structure (atoms, molecules, and organisms; by functionality).
We're not adding components yet in this phase. This is from 0 to 1, which means that only having a library that extends vuetify is in the scope of this branch.
4. Define the library naming (vuetify: v-element; quasar: q-element).
As we're not adding yet a components structure, it's not needed to work in component naming yet.


2: Add Password to Datastore

https://sites.google.com/codeustudents.com/main/projects/project-1-adding-a-registration-page/2-add-password-to-datastore

ETA: Friday, March 9th


feat: Replaced kapa.ai with Cookbook Onboard (AI Assistant)

Preview
Preview link: https://wormhole-docs-cookbook.vercel.app
Ask Cookbook AI Assistant
Cookbook's Ask Cookbook AI assistant and co-pilot is trained on all existing Wormhole resources (source code, docs website, etc.) and is available as a standalone modal, embeddable as a button on any page (recommended for technical docs). It answers developer questions about using Wormhole, acting as an enhanced and streamlined technical documentation search tool as well as a Solidity coding co-pilot.
Ask Cookbook AI can also access context from thousands of data sources indexed by Cookbook.dev in addition to Wormhole-specific data sources, providing the best blockchain developer-focused answers of any chatbot on the market. Cookbook will assist in the tuning and calibration of the AI assistant to ensure the highest answer quality.

Hey @ClockRide! Thanks for opening the PR! 💜 I'll take a look at this today!

Could we keep the old button location please?

I noticed that the button currently loads after the page is fully loaded, which is particularly noticeable in the header due to the shifting content. Once it's moved out of the header, this won't be an issue. However, I'm curious why it's loading in the body instead of the header, especially since block libs typically handles rendering JavaScript in the header. Is this something that's configurable? It definitely works as is, but I'm asking just to better understand 🙂

That’s the case because we have the "defer" attribute in the script tag that loads our integration. We’ve added it to ensure we don’t impact your website’s load time, even if it introduces a slight delay in loading the chatbot. Happy to swap it for "async" though if you’d prefer to load it asynchronously instead of after the web page is loaded, but this might result in worse page load times on devices with low internet bandwidth.
That’s the code snippet I’m talking about, by the way:
<script defer<EMAIL_ADDRESS>
As far as rendering the script in the body goes, that’s a good point—thanks! My guess is that the  tag we put in the head makes browsers move it and everything after it to the body of the page. In the raw HTML layout, both the div and script tags are in the head section, but in Chrome DevTools they are not. Anyway, it should be fixed now, and I made sure to squash my changes to keep it clean. Also moved the button to where you had it before (cc @evgeniko)
Let me know if there are any more questions or requests :)

I noticed that the button currently loads after the page is fully loaded, which is particularly noticeable in the header due to the shifting content. Once it's moved out of the header, this won't be an issue. However, I'm curious why it's loading in the body instead of the header, especially since block libs typically handles rendering JavaScript in the header. Is this something that's configurable? It definitely works as is, but I'm asking just to better understand 🙂

By the way, the button position can be adjusted in the future through the portal you should already have access to. It's adjustable at cms.cookbook.dev > Bot Configuration (in the header) > Appearance (in the sidebar).

Thanks for the responses! No need to change it to async; I was just curious 🙂
@evgeniko I'll merge this into a local branch and play around with the styling to align it with the mockup I received from the Sp-ce team. So once I get that completed, I'll open up a new PR there and request your review


bug: high critical hit rate moves

http://bulbapedia.bulbagarden.net/wiki/Category:Moves_with_a_high_critical-hit_ratio

data format now supports this, but need battle mechanics to take this into account


Expose event venue information

Events may include venue information. These changes expose it on the event using the already provided Location class that is used with Pages.

@alejo90 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


Cargo is not applicable to the toolchain

I ran cargo generate --git https://github.com/Rahix/avr-hal-template.git to create a new project
and then i ran cargo build command and it gave this error
$ cargo build
error: the 'cargo' binary, normally provided by the 'cargo' component, is not applicable to the 'nightly-2022-07-10-x86_64-unknown-linux-gnu' toolchain

not only for cargo build but running any cargo command gives the same error

Try reinstalling the toolchain with rustup, e.g.
rustup toolchain uninstall nightly-2022-07-10
rustup toolchain install nightly-2022-07-10

It worked thanks


Transition CRDs from v1beta1 to v1

What this PR does / why we need it:
Transitions all the CRDs defined in the kubefed chart and sub-charts as well as those generated through kubefedctl from apiextensions.k8s.io/v1beta1 to v1.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1296
Special notes for your reviewer:

@jimmidyson @hectorj2f @xunpan the CI checks are passing now (finally 🎉). Would you mind having a look at this PR, please?

Good point @jimmidyson. I will have a look into the upgrade behaviour. Do you know off the top of your head whether there's any upgrade testing in the e2e tests already?

@makkes I can confirm, there is not any upgrade testing.

/lgtm

@jimmidyson: I was finally able to test the upgrade from a former version of kubefed:

checked out current master
ran make deploy.kind
attached another kind cluster
created a Deployment and federated it using kubefedctl
checked out this PR's branch and ran make deploy.kind again, updating the CRDs and controllers/webhooks
created a 2nd Deployment and federated it using the new kubefedctl binary

No interruption of the federated resources was observed and all new resources are federated properly.

Thanks @makkes for testing so thoroughly.

/lgtm


Fix and update GA workflow

Resolves #183

Tests don't pass yet but the workflow works now as expected.


Disney Epic Mickey : Disney Epic Mickey 2: The Power of Two [PCSF00309]

App summary

App name: Disney Epic Mickey : Le Retour des Héros (PCSF-00309)
App serial: PCSF00309
App version: 1.00

Vita3K summary

Version: v0.1.8
Build number: 3158
Commit hash: https://github.com/vita3k/vita3k/commit/60a68325
CPU backend: Dynarmic
GPU backend: OpenGL

Test environment summary

Tested by: Zangetsu38
OS: Windows 11
CPU: AMD Ryzen 3900X
GPU: Nvidia RTX 2070 Super
RAM: 16 GB

Issues

Spam log in boot with cpu error

Log
vita3k.log

Vita3K summary

Version: v0.2.0
Build number: 3691
Commit hash: https://github.com/vita3k/vita3k/commit/31826697
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: Slade
OS: Microsoft Windows 10 Professional (build 19045)
CPU: Intel(R) Core(TM) i7-3770K CPU @ 3.50GHz
GPU: NVIDIA GeForce GTX 1060 6GB
RAM: 16 GB

Issues

No changed compared to previous report.
The game still has significant texture issues, especially in the first level (Yen  Sid's house).

Screenshots

Log
vita3k.log


Add CO2 formula values to Report

Follow up from #12
example output:

All extra calculation values are added as "metadata".

Closing in favour of https://github.com/qbic-pipelines/nf-co2footprint/pull/28


feat(pull_reqeust): :sparkles: When pull request is closed add closed label and remove ready for review or approved label

Description
When pull request is closed add closed label and remove ready for review or approved label
Closes #27
Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (postman)

Screenshots

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


molget silently fails if OpenBabel is not installed

Right now molget fails in silence in case obabel -i ... 2> /dev/null fails, due to the error redirection.
Can this be considered a "bug"?

Added error checks for the curl and obabel command, so should be fixed.