text:
How to link external library into zig_binary/library/test

Is #15 necessary to write something like:
zig_binary(
    name = "my-bin",
    main = "my-bin.zig",
    deps = ["@FOO//:bar"],
)

where @FOO//:bar is an external C/C++ library ?
This seems indeed like a most welcome addition.
Is there any way to link in a C/C++ library into a zig_library/binary/test atm ?
In my trials I hit does not have mandatory providers: 'ZigPackageInfo'.
Thanks for the great work, looking forward to connecting my first toy programs with it!

Is #15 necessary to write something like:

Yes, that's correct. #15 was phrased as being about zig_binary specifically. But, by now the underlying implementation of zig_binary|library|test is the same. So, I've generalized the ticket to capture all of these.

This seems indeed like a most welcome addition.

I'd love to hear if you have some specific use-case and if you have any constraints about how this should work.
In particular, as #15 points out, Zig can link libraries in two different ways, either by filepath, or by -l flags. I.e. either some/path/to/libfoo.a, or -lfoo. Would your use-case have a preference for one or the other way of doing this?
Also, Bazel's cc_library targets capture both static and dynamic libraries at the same time and it is up to the downstream user to decide which to use. The cc_* rules offer control through a linkstatic attribute and otherwise prefer static linking over dynamic linking except for tests where it is the other way around. Now there is also cc_shared_library in Bazel.
Does your use-case have any constraints wrt a preference for static or dynamic linking?

At the moment my plan would be to start with a very simple implementation, exposing a cdeps attribute, passing libraries by filepath if possible, and preferring static linking.
zig_binary(
    name = "my-bin",
    main = "my-bin.zig",
    cdeps = ["@FOO//:bar"],
)

Thanks for your reply, I don't have specific use cases yet beyond kicking the tires of C / zig interop under bazel; static library is the sensible thing for me to start with.

At the moment my plan would be to start with a very simple implementation, exposing a cdeps attribute, passing libraries by filepath if possible, and preferring static linking.

This would be great!

@persososo Thanks for sharing your thoughts on this! I'll close this as a duplicate of #15. Since #15 is already intended to cover this use-case.

authors: aherrmann persososo


text:
Refactor common code.

Refactored repetitive settings loading into a utility function. I put it in a separate modules to set up my next PR.
I did some basic tests to ensure that Run, RunAsPiped and Compile were still working.

Thanks

source: gharchive/pull-request

authors: aviaryan selimb

repo: ahkscript/SublimeAutoHotkey

license: unlicense

license_type: permissive

license_source: bigquery


text:
command " corona -s cases -l 10" don't show chinese data

command " corona -s cases -l 10" don't show chinese data,
but corona china well done.

Wow. Strange. Help solve this issue?

I think I fixed it, submitted a pull request!

thanks, it's ok now.

source: gharchive/issue

repo: ahmadawais/corona-cli

license: MIT

license_source: github-api


text:
Dynamic Blocks Support

Feature Request
Is your feature request related to a problem? Please describe.
Gutenberg allows the use of the 'render_callback' in php when registering a block type.
This isn't currently in use and makes it impossible to create dynamic blocks (like latest posts).
Describe the solution you'd like
Implement a way of having a render_callback for each block.

Using a render_callback function is very welcome here as well! I can not figure out how dynamic blocks with the REST API work, the withSelect and @wordpress/data package are barely documented (like almost the entire Gutenberg repo..) so the PHP fallback is something that I could really use :)
I guess for now a solution is to make seperate plugins just for the blocks that need this. As long as CGB is only used for one block then the render_callback should work.

I can't find documentation on how to properly enqueue react to the save function, though I have seen references to it being possible.
Like here:
https://wordpress.stackexchange.com/questions/333532/how-to-add-javascript-function-in-the-save-of-gutenberg-block
https://www.youtube.com/watch?v=jauZCeLrGFA&t=1s
https://wp.zacgordon.com/2017/12/26/how-to-add-javascript-and-css-to-gutenberg-blocks-the-right-way-in-plugins-and-themes/
It would be great if this was included in create-guten-block, or at least added to documentation so it's clear on how to implement this.  The php world is foreign to me, as I am more comfortable with react/javascript.

@Jebble  I've started my own project to simplify WordPress development for myself. Not directly related to gutenberg block development, but it is also possible.
Until this dynamic block support is added to cgb, you might want to check out my wp-plugin-boilerplate.
You can simply add another entry file inside the wpds-scripts.config.js for your dynamic block and then enqueue the build script with a render_callback inside your plugin's PHP file.
This is not an advertisement, it's just to help those people who actually need to have access to the render callback, like myself 😉

I got a very simple solution that worked for me, you just need to add one more register_block_type with the same name you registered in your js and just put the render_callback option.
register_block_type(
	'custom-block/your-block', array(
		'render_callback' => 'block_render_callback'
	)
);

function block_render_callback($attributes, $content) {
	return 'Works!';
}

Did you try to do this with multiple blocks?

Did you try to do this with multiple blocks?

Yes, I have multiple blocks but just a few are dynamic.

Do you have a sample to show? I tried that but I still can't see the rendered code on the screen.

Did you put the same name in your javascript?

So... I just figure out the mistake that led to my previous question. Inside the plugin.php I can add the code that @rodrigowbazevedo showed before and, since the register_block_type has the same name as its javascript part, it works fine. My problem was a misconception about the way Create Guten Block works, I guess.

Did you try to do this with multiple blocks?

trying that now. It appears there is some extra support needed for render callback with multiple blocks. Going to investigate this now and well maybe I will figure it out and show an example.

authors: Jebble josias-r megphillips91 noahneumark olafghanizadeh rhamses rodrigowbazevedo

repo: ahmadawais/create-guten-block


text:
The automated release is failing 🚨

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

:rotating_light: The automated release from the master branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:

Usage documentation
Frequently Asked Questions
Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid npm token.
The npm token configured in the NPM_TOKEN environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/.
If you are using Two Factor Authentication for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization and writes" level.
Please make sure to set the NPM_TOKEN environment variable in your CI with the exact value of the npm token.

Good luck with your project ✨
Your semantic-release bot :package::rocket:

repo: ahmadnassri/node-glob-promise


text:
function kubectl() in README doesn't handle quoted arguments correctly

I posted on Stack Overflow about a difficult-to-diagnose error when working with kubectl here: https://stackoverflow.com/questions/54948471/jsonpath-range-not-working-when-using-kubectl
I traced the error down to having followed this repo's suggestion to overwrite kubectl with a function.  It seems the function strips quotes from arguments when in some cases they are necessary.
Instead of
function kubectl() { echo "+ kubectl $@"; command kubectl $@; }

how about this?
function kubectl() { echo "+ kubectl $@"; command kubectl "$@"; }

I recall that wasnt working under certain circumstances but that’s what shellcheck was recommending, too.
If you tested thoroughly, I’m happy to accept a PR.

The issue is further complicated with commands such as this -
kubectl -n istio-system port-forward $(kubectl -n istio-system get pod -l app=prometheus -o jsonpath='{.items[0].metadata.name}') 9090:9090
results in...
+ kubectl -n istio-system port-forward + kubectl -n istio-system get pod -l app=prometheus -o jsonpath={.items[0].metadata.name} prometheus-67599bf55b-sq822 9090:9090 Error: unknown shorthand flag: 'l' in -l
Not sure what the fix is. I'd recommend removing the function from the README.
BTW ahmetb. Great project. The aliases are really useful. Many thanks for your efforts.

Since it’s just in the readme and not in the code, I am ok with keeping it despite it half-works. I’d be interesting in figuring out what the actual fix would be though.
“$@“ should be working. Have you tried it @RossWhitehead?

authors: RossWhitehead ahmetb axesilo

repo: ahmetb/kubectl-aliases


text:
add artnet protocol  support

its a  brilliant software, and is well written but I am using artnet  in some of my devices, it would be fun to use ledfx with artnet , I have a setup with 3000 ws2811.

+1 I want to use resolume and it only supports artNet. So when i decide to use ledfx i always need to change the wled config and restart. it gets anoying

+1

authors: LoneWalkerWolf alexandremix johermohit


text:
🛑 Dashboard is down

In 795cb53, Dashboard (https://guard-bot.ahq-alt.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dashboard is back up in 3c1320f.


text:
🛑 Bot is down

In fa77ea2, Bot (https://ahq-miness.ahqsecret.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bot is back up in d6a46d8.


text:
🛑 Dashboard is down

In b70f3b8, Dashboard (https://guard-bot.ahq-alt.repl.co/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dashboard is back up in 12eb032.


text:
cat instead of echo

ahrasis,
line 54
cat "root" > /etc/incron.allow
should be
echo "root" > /etc/incron.allow

You are correct, it shoule the latter. It fixed now.


text:
Put new chat button same level as the send button

Describe the feature
As what the title suggests, it would be a better user experience(otherwise i need to click more and new chat) and reasonable implementation considering how the api works which needs to append old message so i have to clear conversation quite often.

Hi - having the Start a new chat button right next to Send message button could be easily destructive and cause unwanted user experience (i.e. accidentally clicking it while trying to send a message)
Did you see the controls up at the toolbar for Genie: Start a new chat command?

There is also a command for Genie: Start a new chat, for which you could assign a keyboard shortcut if you find yourself creating new chats very often, that'd be very useful.

I see. ty for the tip. Didn't notice that plus button upper there before.
I still think it could be better to put that feature besides the send button, it works like Bing chat. Maybe autofocus can add to this also.  I don't know, your product,  it's just a personal opinion.
Anyway, gj on this extension.

repo: ai-genie/chatgpt-vscode

license: ISC


text:
Merge stable back into master

We can merge this but avoid deleting the branch in order to apply the tidying up changes to master efficiently.

Unnecessary since the cleanup branch was created from stable.


text:
Contact details

Add contact details for any queries

Those who have not been provided with my contact details personally can use GitHub to post issues

repo: aidan-parkinson/anonymous-feedback


text:
[1.9.4] - Rendering block entity crash

The portable tank causes a crash when put into a tinker's construct crafting station.
We believe the issue is a rendering issue due to the fact that the crafting station renders items on top of the table.
https://gist.github.com/Lazarix/006ac9201aeffdd2cb1c31458b634734

What Mekanism release are you using?

latest code from today, 1.9.4

TiCon's crafting stations are known to crash with mod items, you should probably disable the render.

Fixed, thanks

authors: Lazarix Xiaminou aidancbrady

repo: aidancbrady/Mekanism


text:
bug: Typescript files are not being compiled, when I add million.webpack() to my webpack 5 configuration

Hi @aidenybai
Filing this issue again.  The original can be seen here. #476
I tried with both  v2.5.0 and latest which installed 2.5.2-beta.0 and get the following errors.

using windows 11, VS Code and:
"million": "^2.5.2-beta.0",
"typescript": "^5.1.6",
"webpack": "^5.88.2",
"webpack-cli": "^5.1.4",
"webpack-dev-server": "^4.15.1"

Can we get a repro please @TerrySlack? It'll be easier to help us set see the issue and then figure out possible solutions to it.

@tobySolutions
Here you go:
https://github.com/TerrySlack/millionjs-bug

@tobySolutions were you able to detect the issue(s) in the repo I provided?

@tobySolutions ?

@tobySolutions @TerrySlack @aidenybai any updates on this?

@norbertorok92 I've pinged them a few times, since providing a repo and no response.
I'd love to use this library, but at this point, I'm moving on.  If they ever decide to put out an update, I'll revisit.  I can't wait any longer

Hmm, sorry about this @TerrySlack and @norbertorok92.
Can you install the latest version please and then retry this. Also, I'd love to see your configuration file to see how you set up Million.

@tobySolutions
You can view it in the repo you requested, amd I provided in the comment from Aug 1

Really sorry for the late response. Nobert brought it up with the team too and I'm looking into it.
I'll keep you updated as I might not be able to look at this myself at the moment. I'm a bit under the weather.
Thanks for responding!

@tobySolutions How is it going?  Any progress?

@tobySolutions How is it going?  Any progress?

Hey Terry! Yep! Nobert was able to fix his bug, but, I'm not sure if the same thing can apply to you.
I'll share it here soon so you can have a read through of hos solution

Hey Toby,
Well, that's ambiguous :)
So are you saying it doesn't work with Windows? Or Webpack?  If it's a webpack thing, I can give it a try on Vite if necessary.
If it's my configuration in Webpack, I'm open to any suggestions your team has.  I really like what I have read about million and can see a perfect use for it in an upcoming project.

I'm going to be hitting a hard deadline on whether to use millions or not.
Do you have a solution for windows, typescript and webpack 5?
If the repo I provided needs tweaks that can happen.  Is this a lib that works cross platform?  If so, what tweaks need to be made to have ot work with webpack 5 and typescript?
I love the concept of this lib and hope there is a solution.

@tobySolutions Well, when I get a github bot pointing out how stale this issue is, I realize that a solution isn't coming.
To bad.  Really love the concept.

Hey there @TerrySlack; that's just github actions being weird though. The issue is still actively under review

Hey @tobySolutions , culd I get an update on what is happening?

Are you still getting this @TerrySlack? 🤔🤔

I can't answer for @TerrySlack, but I'm noticing the same error in https://github.com/NDLANO/h5p-editor-topic-map/pull/641. By setting the transpileOnly: true option on ts-loader, the errors disappeared from the build, but the browser console is now saying that React is not defined.

Thanks for looking into this!

@tobySolutions
I haven't tried using your library since I filed this bug. I haven't heard of any uodates regarding it.  Have things been fixed?  Curious, did you use the repo I provided to test things out?
Terry

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine.
Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",

webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine. Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",

webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Hey there! Thanks for this, I think a reproduction will be much better actually. Thank you!

Im having the same issue. It happens in auto and manual mode. Without this plugin it runs fine. Im executing
"start": "NODE_ENV=development webpack-dev-server --mode development",

related packages
```
   "webpack": "^5.60.0",
    "webpack-bundle-analyzer": "^4.5.0",
    "webpack-cli": "^4.9.1",
    "webpack-dev-server": "^4.3.1",
    "webpack-server": "^0.1.2",
    "million": "^2.6.4",
    "typescript": "^4.4.4",
```
webpack.config.js
const dotenv = require('dotenv').config()
const Dotenv = require('dotenv-webpack')
const HtmlWebpackPlugin = require('html-webpack-plugin')
const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederationPlugin')
const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer')
const MiniCssExtractPlugin = require('mini-css-extract-plugin')
const path = require('path')
const TerserPlugin = require('terser-webpack-plugin')

const webpack = require('webpack')
const million = require("million/compiler");

const APP_MODE = process.env.NODE_ENV || 'development'
const APP_PORT = process.env.APP_PORT || '3000'
const isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  entry: './src/index.tsx',
  mode: APP_MODE,
  output: {
    filename: '[name].chunk.js',
    path: path.join(__dirname, 'build'),
    clean: true,
  },
  devServer: {
    port: APP_PORT,
    client: {
      overlay: {
        errors: true,
        warnings: false,
      },
    },
    allowedHosts: ['*', 'dev.cor.com', 'cor.com'],
  },
  module: {
    rules: [
      {
        /* The following line to ask babel
             to compile any file with extension
             .js */
        test: /\.js?$/,
        /* exclude node_modules directory from babel.
            Babel will not compile any files in this directory */
        exclude: [/node_modules/],
        // To Use babel Loader
        loader: 'babel-loader',
        options: {
          presets: ['@babel/preset-env' /* to transfer any advansed ES to ES5 */, '@babel/preset-react'], // to compile react to ES5
        },
      },
      {
        test: [/\.tsx?$/, /\.ts?$/],
        use: 'ts-loader',
        exclude: /node_modules/,
      },
      {
        // The following rule is set to add all css compiler rules
        test: /\.css$/i,
        use: [isProduction ? MiniCssExtractPlugin.loader : 'style-loader', 'css-loader'],
      },
      {
        test: /\.svg$/,
        use: [
          {
            loader: 'svg-url-loader',
            options: {
              limit: 10000,
            },
          },
        ],
      },
    ],
  },
  resolve: {
    extensions: ['.jsx', '.js', '.ts', '.tsx', '.json', '.css', '.jpg', '.jpeg', '.png', '.svg'],
    fallback: { 'process/browser': require.resolve('process/browser') },
    alias: {
      react: path.resolve('./node_modules/react'),
    },
  },
  plugins: [
    million.webpack(),
    // Dot env plugin to get .env variables to npm process
    new Dotenv(),
    new webpack.ProvidePlugin({
      Buffer: ['buffer', 'Buffer'],
      process: 'process/browser',
    }),
    new MiniCssExtractPlugin({
      filename: isProduction ? `static/css/[name].[contenthash].css` : '[name].css',
      chunkFilename: `static/css/[id].[contenthash].css`,
    }),
    new HtmlWebpackPlugin({
      template: './public/index.html',
    }),
  ],
  optimization: {
    minimize: true,
    minimizer: [new TerserPlugin({ parallel: true })],
    splitChunks: {
      // include all types of chunks
      chunks: 'all',
      cacheGroups: {
        vendor: {
          name: 'node_vendors',
          test: /[\\/]node_modules[\\/]/,
          chunks: 'all',
        },
      },
    },
  },
}

isProduction && (module.exports['devtool'] = 'source-map')
isProduction && module.exports['plugins'].push(new webpack.optimize.AggressiveMergingPlugin())

Hey there! Thanks for this, I think a reproduction will be much better actually. Thank you!

Forget it! just add transpileOnly: true, and it builds. Thanks ❤

Hmm, thank you very much @9gustin!! I should definitely document this. I'll put a tab on this.

repo: aidenybai/million


text:
Asciidoc setup with docToolchain container

the docToolchain submodule has been replaced with a container
./gradlew generateDocs

will now generate the docs through the docToolchain container.
the project now also has its independent htmlSanityCheck-task back:
./gradlew htmlSanityCheck

PS: the docToolchain container is pulled from the docker hub - it is defined in this repository https://github.com/docToolchain/docker-image and build on the docker hub - on change.
It already contains all dependencies which makes the execution quite fast (when it is already downloaded)

I will look into this - but currently (April 2019) I don't find the time ... so please be patient...

since this is outdated, let's close it. ...and you can also remove the source branch to clean up the repo.

authors: gernotstarke rdmueller


text:
403 Error when aiohttp resources are not fully merged

Aiohttp merges resources, when they are added in the correct order:

When using aiohttp-cors, resources have to be fully merged, or you end up having 2 resources for the same path, one for the GET method one for the POST, but the latter will not be considered when aiohttp-cors answers the OPTIONS request. It seems that aiohttp-cors supports only a single resource per path.
It would be nice if a hint about this could be added to the docs, if the support of multiple resources for the same path is too complex.
Requirements:
aiohttp==3.0.6
aiohttp_cors==0.7.0

Replicate:
def handler():
    pass

app.router.add_route('POST', '/a', handler)
app.router.add_route('GET', '/b', handler)
app.router.add_route('PUT', '/a', handler)

# Configure default CORS settings.
cors = aiohttp_cors.setup(app, defaults={
    "*": aiohttp_cors.ResourceOptions(
    allow_credentials=True,
    expose_headers="*",
    allow_headers="*")
})

# Configure CORS on all routes.
for route in list(app.router.routes()):
    cors.add(route)

@FabianElsmer we faced with the same issue, allow_methods="*" - could help you.
you could try this:
cors = aiohttp_cors.setup(app, defaults={         "*": aiohttp_cors.ResourceOptions(             allow_credentials=True,             expose_headers="*",             allow_headers="*",             allow_methods="*"         )     })

authors: FabianElsmer IgorKuzmenko

repo: aio-libs/aiohttp-cors


text:
Broken connections are reused in connection pools

Describe the bug
If an application has a connection break with the network, it accumulates broken connections with the Redis server and tries to reuse them to execute commands. This is due to the fact that the connect() methods do not check whether an exception is set in the StreamReaders:
class Connection:
    async def connect(self):
        """Connects to the Redis server if not already connected"""
        if self.is_connected:   # <-- self._reader may contain an exception (e.g. OSError No route to host).
            return

class SentinelManagedConnection:
    async def connect(self):
        if self._reader:  # <-- self._reader may contain an exception (e.g. OSError No route to host).
            return  # already connected

This cases should be handled.
To Reproduce

Initialize base Redis client or Sentinel client, connect to Redis server
Send pings periodically
Turn off wi-fi
Look at ping errors
Turn on wi-fi
Look at ping errors

Expected behavior
There should be no errors in step 6
Logs/tracebacks
https://gist.github.com/evgenymarkov/1af3a5cb12887068cb9c6a72c09168ea

Python Version
3.9.10

aioredis Version
2.0.1

Additional context
No response
Code of Conduct

[X] I agree to follow the aio-libs Code of Conduct

https://github.com/aio-libs/aioredis-py/pull/1313

My issue can be related with https://github.com/aio-libs/aioredis-py/issues/1174

repo: aio-libs/aioredis-py


text:
Hierarchical planning notebook

Colab link (works as long as the hierarchical-notebook branch exists)
https://colab.research.google.com/github/aiplan4eu/unified-planning/blob/hierarchical-notebook/notebooks/Hierarchical_Planning.ipynb

@alvalentini You can use the notebook here for the hands-on session. A colab link is provided in the initial comment. I will update this branch to fix a few remaining inconsistencies in the notebook.

@arbimo Perfect, thanks!

@alvalentini This is now ok to be merged I believe.

authors: alvalentini arbimo


text:
Connecting to https://dapp.robonomics.network/ with the wrong network selected on Metamask

Issue:
When connecting to https://dapp.robonomics.network/ with the wrong network selected on metamask (such as the Moonriver network being selected), an error message pops up:

The issue is that many users do not notice / understand the current error message "For work, you need to switch the network", and people have been asking how to solve this simple issue.
I think that the error text should be changed to be a bit more descriptive, and maybe the error message text should be a larger font.
An example of how the text can be changed:
"Your wallet is currently connected to the wrong network, please switch to the Ethereum network to continue."

Thanks for the suggestion! We are working now on improving this error handling

Ready! Thanks a lot for your contribution 🤖🦾🙏


text:
Project 1 Review (Scapsulators)

Just ran your project, It was not clear how to run the project, had to figure out the branch myself.
I'm running the project from feature/3-user-management-service.
On build getting this error : -
Error: Unable to access jarfile target/UserManagement-0.0.1-SNAPSHOT.jar
Do I need to have some prerequisite setup? Let me know if I am doing something wrong.
Reviewed by Team Scapsulators (https://github.com/airavata-courses/scapsulators)

Hello Shubham,
Thank you for the review. We haven't merged all the branches to main yet. Have you tried already remote docker images?.
Let me know if you are able to run.

Hello, I tried to run your project now. I also found it difficult to follow through the WIKI document https://github.com/airavata-courses/DCoders/wiki/local-runbook as mentioned by @shubhpatr
Can you provide steps to run remote docker images ?
Thanks.
Team Garuda

The commands are given on the same page. You need to have the docker installed on your machine (That's the prereq).
https://github.com/airavata-courses/DCoders/wiki/local-runbook#follow-the-below-steps-to-run-the-application-locally

User Management: Replace {docker_host} with the docker hostname
Rest of the applications runs as it is (copy and paste the command).

Got it, thanks.
Maybe a note about which branch to checkout before each module might be helpful on https://github.com/airavata-courses/DCoders/wiki/local-runbook
Had to refer other parts of WIKI to figure it out.
Thanks,
Team Garuda

Got it. Thanks for the review. Will make the changes. 👍

Just ran your project, It was not clear how to run the project, had to figure out the branch myself.
I'm running the project from feature/3-user-management-service.
On build getting this error : -
Error: Unable to access jarfile target/UserManagement-0.0.1-SNAPSHOT.jar
Do I need to have some prerequisite setup? Let me know if I am doing something wrong.
Reviewed by Team Scapsulators (https://github.com/airavata-courses/scapsulators)

Fixed the docker-compose issue. Could you please check if it is working for you now?.

Resolved the docker-compose, and Mapbook M1 chip docker issue.

authors: pranavacharya shubhpatr vinayakasg18

repo: airavata-courses/DCoders


text:
When enforcing version_limit, order the version records by created_at

The details of the issue are in #940.
I split the commits out into visible, obvious parts. If you checkout the middle commit, db4c586, you can see the failure by running rake spec. I'm more than happy to squash these down, if the maintainers would like.

Thanks Dan. Initial review:

Please add a changelog entry under Unreleased -> Fixed
I think that the SQL generated by sibling_versions should not change, should remain unordered.
Unless you feel strongly about keeping it, I don't think we need the "here comes the crazy part" spec. It's a bit hard to follow. If we can replace it with a simpler spec, perhaps by inserting specific values of created_at, that'd be fine.

I think that the SQL generated by sibling_versions should not change, should remain unordered.

So, move the order call to the call site, in enforce_version_limit!? I can do that.

...replace it with a simpler spec, perhaps by inserting specific values of created_at, that'd be fine.

I'll give that a try. Agreed, that'll be much simpler.

@jaredbeck, I made the changes - the CHANGELOG, and moving the order out of sibling_versions.
I also changed the spec to create fake Version records. It's definitely shorter, but I'm not sure if it's easier to understand. Let me know what you think.

Looks good, thanks Dan!

Squashed offline into 300a16c

Thank you @jaredbeck! When do you think this fix will reach rubygems?

We're very close to the next release, 7.0.0. It could happen this week if all goes well.

authors: danbernier jaredbeck

license: mit


text:
Inspectable WebContents

After a blank setup I recieve this message? Anyone else has the same?
Caravel Tag 0.10.0
Thanks Philipp

Which browser is this? Looks like some remote debugging options of your browser than something related to caravel.

Seems invalid, not enough details, closing

authors: mistercrunch philippfrenzel xrmx

repo: airbnb/caravel


text:
Add spanish translation link

Hi!, I've translated this to Spanish, could you add the link?

Absolutamente, gracias!

authors: ismamz ljharb

repo: airbnb/css


text:
TypeError: Cannot read property 'Events' of undefined

setup.js
var Enzyme = require('enzyme')
var Adapter = require('enzyme-adapter-react-16')
Enzyme.configure({ adapter: new Adapter() })

When I run jest, it got this error:
TypeError: Cannot read property 'Events' of undefined

Version
"react": "~16.8.6",
"react-dom": "~16.8.6",
"enzyme": "^3.10.0"
"jest": "^24.5.0",
"enzyme-adapter-react-16": "^1.15.1"
"react-addons-test-utils": "^15.6.2",

Why are you using react-addons-test-utils? That shouldn't even be installed if you're using react 16.
Can you provide more info about the error? Is there a stack trace? Are you getting it running tests, or even with no tests at all?

The question is where is Events being used?

Hopefully the stack trace would reveal that.
Closing for now, happy to reopen if it can be reproduced or if more info is provided.

authors: SarpongAbasimi ljharb yanxiaosong0902

repo: airbnb/enzyme


text:
Pycocotools alternative

Pycocotools is causing a lot of problems. It's currently mainly used for calculating metrics, it would be nice to find an alternative.
This is a strong alternative. Please comment if you have a candidate =)

I have seen this. It is a good alternative but still lacks an API. See the readme for usage, there is no way we can actually compute metrics and add them.
Best alternatives against PyCoco are, lightning metrics, raise a feature request for metrics package in torch. They had this request before too.

pycocotools is currently also being used on Polygon.to_mask, we also need to find an alternative way of doing that.

Because of #510 masks are now heavily dependent on pycocotools because of the heavy use of "Encoded RLE"

We don't have any bandwidth to think about removing this dependency for the time being

authors: FraPochetti lgvaz oke-aditya

repo: airctic/icevision


text:
关于台湾的行政区划代码有重复的

"710300": {     "710301": "仁爱区",     "710302": "信义区",     "710303": "中正区",     "710304": "暖暖区",     "710305": "安乐区",     "710307": "七堵区"   },   "710400": {     "710301": "中区",     "710302": "东区",     "710303": "南区",     "710304": "西区",     "710305": "北区",     "710306": "北屯区",     "710307": "西屯区",     "710308": "南屯区"   },
下方的中区是否应该是710401

确实是个 bug。

"710300": { "710301": "仁爱区", "710302": "信义区", "710303": "中正区", "710304": "暖暖区", "710305": "安乐区", "710307": "七堵区" }, "710400": { "710301": "中区", "710302": "东区", "710303": "南区", "710304": "西区", "710305": "北区", "710306": "北屯区", "710307": "西屯区", "710308": "南屯区" },
下方的中区是否应该是710401

催更催更

台湾这些区域规划有问题吧， 比如  南投县 不在列表中
这个数据源自哪儿？我是搞错了么

这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。

去民政部查了下，台湾省资料暂缺，懂了，统一后再查询

repo: airyland/china-area-data


text:
⚠ Turnos 24x7 has degraded performance

In 767fa9a, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 968 ms

Resolved: Turnos 24x7 performance has improved in 37aab87.

repo: aisa-status/status-upptime-dev


text:
⚠ Turnos 24x7 has degraded performance

In 1fb3273, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 957 ms

Resolved: Turnos 24x7 performance has improved in acd9d5a.


text:
⚠ Turnos 24x7 has degraded performance

In 73dbf74, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1423 ms

Resolved: Turnos 24x7 performance has improved in f356a05.


text:
Make function std::ping::ping concurrency safe

The function ping so far did not check the ident received. As a consequence the function ping might returned wrong results when used simultaneously from different threads, see https://github.com/aisk/ping/issues/6 for more details.
This commit fixes the issue by checking the ident of the reply and comparing it with the expected ident.
Changes:

Changed type of timeout from Option<Duration> to Duration. This avoids an additional error check in new code.
Receive echo in a loop until either the correct ident was received or a timeout occured.

I have tested the changes and they seem to work for me. Let me know if something still needs to be changed.

Great work! I have only a small issue which is pointed out up here. And it should be better to add a mutiple thread test case like what you posted on #6

Thanks for the review, sounds fine. I am currently a bit occupied, give me a couple of days to update the PR.

These commits is already merged in #9.

authors: aisk michael-hartmann

repo: aisk/ping


text:
Sending request headers

We have a use case where it is required to set certain request headers, based on a key or value from Kafka.
Would it be possible to add this feature? I can see several ways to do it.

Automatically use fields in the record key as headers. This may make sense but it is prone to sending unnecessary headers.
Specify a certain prefix for headers in the record key, e.g. http_header_*. When a field matches this pattern, send it as a request header, removing the http_header_ prefix.
Instead of sending the value as a request body, use nested fields "headers" and "body" to describe the payload.

Hi @Oduig
Thank you. Such functionality makes sense. I've added it to our backlog and we'll think how to best implement it.

Hello @ivanyu,
I am also getting this issue when using authentication type that is not STATIC, It appears that the content type is only being added on the AUTH_HTTP_REQUEST_BUILDER that is used when the authentication type is STATIC.
I think the solution would be to add this on the DEFAULT_HTTP_REQUEST_BUILDER (requires confirmation also on the oauth one).

authors: Oduig arcmmartins ivanyu

repo: aiven/http-connector-for-apache-kafka


text:
feat: add fetch chunk transform

Depends on #187

@jeqo can you rebase this one to fix the test failures?

authors: AnatolyPopov jeqo

repo: aiven/tiered-storage-for-apache-kafka


text:
Added algorithm for Doubly Linked List in C

📥 Pull Request
Description
Added a Doubly linked list in C Language
Fixes # 358
Type of change

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@ajay-dhangar done changes.

repo: ajay-dhangar/algo


text:
add Hard Problem Merge K Sorted list

Submit a New Problem of Merge K Sorted List using easy method as Possible
Time Complexity O(n)
Space O(n)

Thank you for this Question Indeed this is a hard Question Please share this repo with your friends so that they can also contribute to this repository
Happy coding and Learning
LGTM


text:
🛑 MONGOLIA is down

In 4fde687, MONGOLIA (https://www.bricks4kidz.mn) was down:

HTTP code: 0
Response time: 0 ms

Resolved: MONGOLIA is back up in 6899514.


text:
Primary/secondary color picker and background input

Category
Feature
Overview

Added two color selectors to the common settings page, which allow you to change the application's theme with the primary selector and change the logo text's gradient with a combination of primary/secondary selector

This has been updated to edit the MantineProvider's theme property and works globally across the app without having to read the config for what colors to use in individual components

Added a background image input to the advanced settings (set to cover, centered, and no-repeat) to address #32

Issue Number
#32
New Vars

config.settings.primaryColor
config.settings.secondaryColor
config.settings.background

Screenshot

Code Quality Checklist

[x] All changes are backwards compatible
[x] There are no (new) build warnings or errors
[x] Attribute is outlined in the schema and documented
[ ] Package is essential, and has been checked out for security or performance
[ ] Bumps version, if new feature added

I was able to edit the theme prop of MantineProvider by using React's context API and have pushed a new commit that removes the need to check config.settings.primaryColor in all of the colored components.
I'll be adding a bit more like a color tone selector and tile opacity slider before I open the PR for review again.

If you guys have any other suggestions of things I can add, let me know.

Not sure how to fix this if I'm being honest. There are only a couple of ways to handle backgrounds in CSS. We can either use the original size which results in the image being cut off or scale it to the browser window which results in the image not filling the screen if it's a different resolution.

The image is 1920x1080, and so is my browser window. So we can definitely fix this.

I will try some things.

Can't get it to work. But the issue is occuring on every image I try, so the feature is not ready for release yet.

IMO, app opacity should change the opacity of Modals, Drawers, and Item, backgrounds, etc. Not the icons (and text?).

See c0c816d

Can't get it to work. But the issue is occuring on every image I try, so the feature is not ready for release yet.

      styles={{
        body: {
          backgroundImage: `url('${config.settings.background}')` || '',
          backgroundPosition: 'top',
          backgroundSize: 'cover',
          backgroundRepeat: 'no-repeat',
        },
      }}

Changing the position to top makes it full width.

This should be fixed by giving the body min-height: 100vh.

I've make a PR from this PR 🤯 adding modules on left.
I'm almost ok, just need to check to add a params on each modules to know if it's a full width module or if it's a "widget".

Finished, just need to let @Aimsucks my PR in his branch to get it there.

authors: Aimsucks Darkham42 walkxcode

repo: ajnart/homarr


text:
run LINTUL3 for potato

Dear developer,
Thanks for the great documentation and the easy-to-use python packages.
I followed all the examples and they ran smoothly without any trouble.
So now I am trying to run the LINTUL3 model for a potato crop by following the 03 notebook.
But got some error message about a parameter called DVSDR
File c:\Users\cflfcl\.conda\envs\py3_pcse\lib\site-packages\pcse\engine.py:228, in Engine.run_till_terminate(self)
    225 """Runs the system until a terminate signal is sent."""
    227 while self.flag_terminate is False:
--> 228     self._run()

File c:\Users\cflfcl\.conda\envs\py3_pcse\lib\site-packages\pcse\engine.py:208, in Engine._run(self)
    205 self.drv = self._get_driving_variables(self.day)
    207 # Agromanagement decisions
--> 208 self.agromanager(self.day, self.drv)
    210 # Rate calculation
    211 self.calc_rates(self.day, self.drv)

File c:\Users\cflfcl\.conda\envs\py3_pcse\lib\site-packages\pcse\agromanager.py:916, in AgroManager.__call__(self, day, drv)
    914 # call handlers for the crop calendar, timed and state events
    915 if self.crop_calendars[0] is not None:
--> 916     self.crop_calendars[0](day)
    918 if self.timed_event_dispatchers[0] is not None:
    919     for ev_dsp in self.timed_event_dispatchers[0]:
...
     64 value = parvalues[parname]
     65 if isinstance(getattr(self, parname), (Afgen)):
     66     # AFGEN table parameter

ParameterError: Value for parameter DVSDR missing.

What I did

I modified the data\agro\lintul3_springwheat.agro to a fake potato crop.

Version: 1.0
AgroManagement:
- 2021-10-01:
    CropCalendar:
        crop_name: 'potato'
        variety_name: 'potato01'
        crop_start_date: 2021-10-15
        crop_start_type: emergence
        crop_end_date: 2022-03-20
        crop_end_type: harvest
        max_duration: 300
    TimedEvents: null
    StateEvents: null

Downloaded weather data from the NASA Power project and modified it to the nl1.xlsx format with the right input value and units. The ExcelWeatherDataProvider function parsed the file correctly.
Used the example site and soil files. I had to fake a value for the parameter ROOTDI to make the soil file parser pass. Not sure what this parameter does.

crop = CABOFileReader(os.path.join(data_dir, "crop", "POT701.CAB"))
soil = PCSEFileReader(os.path.join(data_dir, "soil", "lintul3_springwheat.soil"))
site = PCSEFileReader(os.path.join(data_dir, "site", "lintul3_springwheat.site"))

Wondering what I've missed here.
Note: I've forked the repository and commit the changes I made back to my forked repository if you'd like to reproducible the error I got.
A bit of background about what I try to achieve.
I'd like to run some simulations for potato growth and development in India to see if the LINTUL model can help me make some decisions on the experiment design (e.g cultivar selection) and key dates to make observations on potato traits.
Thank you very much in advance for any feedback.

Dear Frank034,
sorry for the very late reply. Is this still relevant?
Allard

hi Allard, I am able to use wofost potato. so I will close this now.


text:
Make the http.Client customizable

Needed to allow changing the http.Client, 0 value is missing defaults on timeouts and proxy config.

Dear, @japettyjohn
Thanks for your merge request !

authors: AstinCHOI japettyjohn

repo: akamai-open/NetStorageKit-Golang


text:
Fix #44 Allow generation of native launcher for products

Hi
Please, can you review my work on generation of native launcher. At this stage, it is not complete, but I would like to know if I'm on the good way and what refactor you would like to see before merging.
Note :

windows launcher is ok (which was the primary request of issue #44 )
OSX launcher in still a WIP (I don't understand why it don't work)
I don't have a linux box under the hand to test it, I'll setup a VM this week end to check it out.

Note change :

OSX launcher is ok
Linux launcher is tested

Hi Yann,
Thanks a lot for your great contributions!
There were some little bugs, which I fixed:

issue #63: incorrect passing of jvmargs in EquinoxProductConfigurer.customizeIniFile.
issue #64: getEclipseBundleSymbolicName is invoked "too early" for rcp apps.
issue #65: EquinoxProductConfigurer generates eclipse.ini, although it should be ${project.name}.ini

please update your fork and do your tests/builds. If everything works with you, I'll make a release.

As I said on twitter, It's a pleasure to try to improve Wuff.
I saw your fixes. Thanks to you for spotting 'my' bugs. Hard to think about all usecases.
I'll check with your version of the repository tomorrow evening and I come back to you.

Nope there is problem. (I test your master + my pending PR). The "companion library" can't be found. The native counterpart of org.equinox.launch is not in plugins dir after product creation. I'll investigate tonight.

I just tried to reproduce this, without success.
Could you, please try:
git clone git@github.com:akhikhl/wuff.git
cd wuff
gradle build
cd examples/RcpApp-1/MyRcpApp
gradle build

Expected result: MyRcpApp/build/output/MyRcpApp-1.0.0.0-xxx/plugins contains unpacked org.eclipse.equinox.launcher with os-specific part (dll, so, ...).

Ok, I reproduce my problem. If you add a name to the product :
products {
product name: "foo", platform: 'windows', arch: 'x86_64'
}
Then the platform specific launcher is not there.

I used the product name to build different "flavored" version. Maybe it was not intended for this usage.
If it's a correct usage, It seem there is a missmatch, in EquinoxProductConfigurer:60
configName = "${productConfigPrefix}${productNamePrefix}${platform}_${arch}${languageSuffix}"
And defaultConfig.groovy (which don't include productNamePrefix)

Good, I'll try that.

I confirm: adding "name" attribute removed native launcher. Will have a look.

I fixed the issue with native launchers and named products.
Could you, please, test the fix on snapshot?

Good news. I made the test, it work for me :)

authors: akhikhl ylemoigne

repo: akhikhl/wuff


text:
support multiple

as player,it must be nice.

I don't understand your suggestion at all. What do you request?

authors: akjava x-a-n-a-x

repo: akjava/BVH-Motion-Creator


text:
Windows. eval $(ssh-agent)

Hello, I'm working on Windows and have to make in each git-bash session commands:
eval $(ssh-agent)
ssh-add
Just then I have access for repo.
How can I execute this commands in Atom?
Now I have no access to repo with git-plus :-(

I have solved it with .bash_profile
Put into that file (located in home directory ~/)
evalssh-agent -s  ssh-add

repo: akonwi/git-plus


text:
Fix wrong test input data for dropping leading spaces

A test case in textformatter lacked the leading spaces it was supposed to test
for.

Coverage increased (+0.3%) to 30.598% when pulling 892078b7c6e5a94fd4f8ecc5c72a7a1a4c6e7363 on tsipinakis:test-drop-whitespace into 3241e10f3955fce9f48a6031799952fca1f50cc7 on akrennmair:master.

Coverage increased (+0.3%) to 30.598% when pulling 892078b7c6e5a94fd4f8ecc5c72a7a1a4c6e7363 on tsipinakis:test-drop-whitespace into 3241e10f3955fce9f48a6031799952fca1f50cc7 on akrennmair:master.

Coverage increased (+0.3%) to 30.598% when pulling 892078b7c6e5a94fd4f8ecc5c72a7a1a4c6e7363 on tsipinakis:test-drop-whitespace into 3241e10f3955fce9f48a6031799952fca1f50cc7 on akrennmair:master.

Coverage increased (+0.3%) to 30.598% when pulling 892078b7c6e5a94fd4f8ecc5c72a7a1a4c6e7363 on tsipinakis:test-drop-whitespace into 3241e10f3955fce9f48a6031799952fca1f50cc7 on akrennmair:master.

Coverage increased (+0.005%) to 30.42% when pulling e89b0e2804f64ab895347cc7a3c296fc15808a9f on tsipinakis:test-drop-whitespace into 1fa890123580556846e57dd2b8343faed1c7de96 on akrennmair:master.

For the record: me and @tsipinakis discussed this PR on IRC last night. The main takeaway is that test description could be worded better. What I meant when I wrote it is that after wrapping, lines don't start with space; i.e. if space doesn't fit onto a line and is going to be put at the beginning of a new line, it should just be ignored. The test case actually demonstrated that, but suboptimal wording confused people (including me—it's been only 3 months since I wrote it but on the first glance, I decided that the test is useless).
Yesterday I also voiced an idea: if first line of wrapped text ends up consisting solely of whitespace, it should be dropped. @tsipinakis kindly updated the code and the test to reflect this behaviour, but after some sleep I no longer believe it's really necessary ._.
A situation where whitespace takes up a whole line is extremely unlikely unless we're working on an extremely narrow screen (think a dozen columns wide). I don't believe it makes sense to complicate our code to make a marginal improvement in such an unlikely scenario.
So I'd like to change the scope of this PR to updating the test description. @tsipinakis, do you agree? Do you have any ideas about better wording for the test?

Agreed.
Perhaps

When wrapping, ignore leading whitespace wrapped to the next line from the end of the previous one

would be a better description for the current test.

Don't think we need "When wrapping" part at all, we're mentioning the function name (wrap_line) already. The rest of it seems a bit too complicated to me. Maybe "ignore whitespace that's going to be wrapped onto the next line"?
Or maybe we should use your wording and just write an extensive comment like one that I wrote in the previous post, explaining what naive function will do and how wrap_line intelligently deviates?

ignore whitespace that's going to be wrapped onto the next line

Indeed sounds a lot better. To avoid any confusion a comment with an example would be a good idea either way.

So… you'll update the PR, right? :)

Coverage remained the same at 30.401% when pulling 289e054adcfedd2067d4ba7bfb750922d212d049 on tsipinakis:test-drop-whitespace into 765b053d7ed535244cfd093de04c6911611a4b86 on akrennmair:master.

That looks perfect, thank you!

authors: Minoru coveralls tsipinakis

repo: akrennmair/newsbeuter


text:
TextInput keyboard auto disappears in few seconds.

Version

react-native-router-flux v4.0.0-beta.24
react-native v0.50.4

this issue is similar to #2442, and still exist in latest version.
Dose someone have a workaround to fix this ?

@syq7970 I got the same issue. How did u solve?

@munkhorgil Answer in #2442 , In my case, IndicatorViewPager or something like ViewPager with autoPlay will trigger this issue

repo: aksonov/react-native-router-flux


text:
Restore statem

Restore statem logic used with previous Switch

@sarovin could you please check if it still works for you :)

LGTM

authors: aksonov sarovin


text:
feat(webhook): detect duplicate warehouse subs

Fixes: #1583
This adds validation to ensure a Warehouse does not contain multiple subscription entries pointing to the same URL, or in the case of a HTTP/S Helm chart, to the same URL and chart name.
$ kubectl apply -f warehouse.yaml
The Warehouse "my-warehouse" is invalid:
* spec.subscriptions[2].image: Invalid value: "nginx": subscription for image repository already exists at "spec.subscriptions[0].image"
* spec.subscriptions[4].git: Invalid value: "https://github.com/example/kargo-demo.git": subscription for Git repository already exists at "spec.subscriptions[1].git"
* spec.subscriptions[5].chart: Invalid value: "https://example.com/charts/": subscription for chart "nginx" already exists at "spec.subscriptions[3].chart"
* spec.subscriptions[7].chart: Invalid value: "oci://foo": subscription for chart already exists at "spec.subscriptions[6].chart"

One possible issue and looks good otherwise.

authors: hiddeco krancour

repo: akuity/kargo


text:
feat: custom PR title (#3063)

closes #3063

@krancour Please let me know your thoughts on testing here. My thinking here is that we can both assume expressions in promotion steps are evaluated properly (likely tested elsewhere), and that if I pass any title to a Git provider's CreatePullRequest, the pull request will be created with the given title.

@muenchdo correct on both counts. 😄

@muenchdo I think if you re-run codegen, this looks g2g.

authors: krancour muenchdo


text:
How edit boilerplate into Android Studio ?

Android 3.1.4
Win 7

Hi @alejandri ,
What do you mean with 'boilerplate'?

Hi Artyorsh, Thanks. I want import and use this PACKAGE into ANDROID STUDIO project.

authors: alejandri artyorsh

repo: akveo/kittenTricks


text:
Error when try to follow the Getting Started Guide

Hi, I'm sorry for this noob question. But when I try to follow the smart table Getting Started and integrate with Angular basic template using ng new exchange-ws syntax to understand how smart table work.
I've got this error when I run ng serve.

Here's my Angular version

Any help will be appreciated so much. Thanks

npm install ng2-completer --save

authors: ariebrainware naveednazarali


text:
error in npm install ngx-admin 7.0.0

Issue type
I'm submitting a ...  (check one with "x")

[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Issue description
I'm having dependencies error in npm install. I deleted package.lock.json and node_modules before doing npm install
Current behavior:

Expected behavior:

Npm install will run without error
Steps to reproduce:

Npm install
Related code:

Other information:

Same problem with ngx-admin 8, lots of dependencies resolve pbs.

Use the node version 14.15.0 to resolve this issue

Use the node version 14.15.0 to resolve this issue

Thanks bro, it worked for me

Use the node version 14.15.0 to resolve this issue

Thank you so much!

Use the node version 14.15.0 to resolve this issue

Thanks bro its done work for me @udhayakumar-yavar

it works also with 14.21.3
It does not work with other lts gallum and hydrogen
I'm using nvm

authors: JohannesH1998 PYRO-DRANE amielmendoza biggosh mahdiqnbi reedlex98 udhayakumar-yavar

repo: akveo/ngx-admin


text:
Mi Smart Power Plug 2 (chuangmi.plug.212a01) power consumption sensor wrong

power consumption value should have two decimal points. in this case actual power consumption is 78.25W while its being reported as 7825:
[{'did': 'electric_power', 'piid': 6, 'siid': 5, 'value': 7825 'code': 0}]
verified with the app and independent power meter

[{'did': 'electric_current', 'piid': 2, 'siid': 5, 'value': 5, 'code': 0}] and [{'did': 'power_consumption', 'piid': 1, 'siid': 5, 'value': 100, 'code': 0}] are stuck at these values even the plug is switched off

Duplicate https://github.com/al-one/hass-xiaomi-miot/issues/101#issuecomment-856406591

Wouldn't it make more sense for the device to work out of the box by customising the W sensor automatically instead of requiring manual .yaml editing?

This value and unit are from miot-spec. Under normal circumstances, the component will not be changed for a specific model of device, unless the entity is unavailable or affects the use.

authors: al-one blakadder

repo: al-one/hass-xiaomi-miot


text:
Yeelight语音助手没有Play Control conversation的实体，如何添加？

Device model / 设备型号
yeelink.wifispeaker.v1
Component version / 插件版本
0.7.11
HA core version / HA版本
2023.8.2
Integrated mode / 集成方式
Automatic (自动模式)
The problem / 问题详情
我有个Yeelight语音助手，是第三方的小爱音箱，通过miot auto集成到ha，里面没有Play Control conversation的实体，就是判断语音文字作联动的那个。但是我看米家产品库里面，这个语音助手和小爱音箱一样，是有text-content的Properties的（SIID: 5
，PIID：1），想问一下怎么修改集成，自己添加这个实体进去？
Entity attributes / 实体属性
Play Control conversation
Home Assistant Logs / 系统日志
No response

text-content属性是作为intelligent-speaker服务下play-text及execute-text-directive方法的入参，无法读取其属性值。
conversation实体需要该音箱在小爱音箱APP内可以看到对话记录才能支持。

text-content属性是作为intelligent-speaker服务下play-text及execute-text-directive方法的入参，无法读取其属性值。 conversation实体需要该音箱在小爱音箱APP内可以看到对话记录才能支持。

这款音箱通过米家的设备卡片进入后有对话记录，但是无法显示在小爱音箱App内

这个问题解决了吗？我也有同款音箱

authors: LiYefei al-one jasdkc


text:
add get_secure_socket method

Add method for producing always-secured sockets and modify existing code to consume it.

Codecov Report
Attention: Patch coverage is 19.04762% with 34 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (protodrg@232d67f). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files

@@             Coverage Diff             @@
##             protodrg      #16   +/-   ##
===========================================
  Coverage            ?   76.66%
===========================================
  Files               ?       75
  Lines               ?     5339
  Branches            ?        0
===========================================
  Hits                ?     4093
  Misses              ?     1246
  Partials            ?        0

Files
Coverage Δ

smartsim/_core/launcher/dragon/dragonLauncher.py
26.53% <19.04%> (ø)

smartsim/_core/launcher/dragon/dragonSockets.py
34.48% <19.04%> (ø)

authors: ankona codecov-commenter

repo: al-rigazzi/SmartSim


text:
Earlgrey: yosys fails to parse aes_key_expand

Parsing aes_key_expand.sv file results in error in yosys:
aes_key_expand.sv:164: ERROR: Can't resolve function name `\aes_circ_byte_shift'.

Blocked by: https://github.com/alainmarcel/Surelog/issues/1109

Surelog problem is resolved, but now generated bitstream is not working on HW.

repo: alainmarcel/uhdm-integration


text:
MFA Evaluation sans Break Glass Accounts

Currently the controls for MFA evaluation validate that the Break Glass accounts are excluded from the MFA Conditional Access Policy.
Would you be able to exclude them from being evaluated entirely. i.e., if the Breakglass has MFA it's a pass or if the BreakGlass doesn't have MFA it's a pass? All accounts outside of the BG accounts require MFA?

The new ItemName would be MFA Enforcement (M).

CORRECTION/ Adjusted Request
Two ideas to test
Control Name: Global Admins MFA Enablement (M)

Upload a list as a .txt to the storage account following a specific format to list the GA’s that require MFA. Departments can add the BG accounts if they’d like those to also have MFA enabled. Otherwise they would omit the BG Accounts.
o	The check would take the UPN’s listed and verify if MFA is enabled. If yes, then they pass the control. If not, then they fail the control.
OR use similar logic to the BG account check and add multiple inputs for GA’s in the config.json. Departments can add the BG accounts if they’d like those to also have MFA enabled. Otherwise they would omit the BG Accounts.
o	The check would take the UPN’s listed and verify if MFA is enabled. If yes, then they pass the control. If not, then they fail the control.

Short Term fix
Attestation for control Global Admins MFA Enablement (M) is uploading GlobalAdminsHaveMFAEnabled.txt to the storage account. If the file exists than it’s a pass for the control. If not, it fails the control.


text:
Update README.md

Bonsoir,  j'ai corrigé le README.md dans lequel tout était écrit en anglais sauf le mot "prépositions".
Bonne continuation
Adsam39

Merci @Adsam39 !

repo: alan-eu/french-departments