Sponsorship for Cookiecutter

Opening this as a discussion area for how to help fund efforts for cookiecutter to improve and tackle things like #848.
Not sure how much "sponsorship" is needed, but here is a site for allowing the crowd to contribute as I know my organization would be interested in helping... (I have no affiliation with this site, but just found it while searching for how other projects handle this).
https://opencollective.com/

I presume that cookiecutter maintainers suffer from the usual OSS project problems of not having enough ~fresh meat from human bodies~ people who have time available who can commit to review and merge PRs. That offer of sponsorship is very valuable.
There are numerous entities which can provide fiscal management and sponsorship. They usually charge around 10% of revenue as a management fee. Many set requirements for branding, licensing, and other activities which may be too constraining. The following are potential fiscal managers, and some can also provide 501(c)(3) status, licensing, and intellectual property advice. When I investigated this for the Pylons Project, we came up with a list of potential organizations/businesses/foundations:

School Factory - http://schoolfactory.org/services#section-2
Open Collective - https://opencollective.com/
Gratipay - Perhaps in the future whenever they finalize their structure
Python Software Foundation - https://www.python.org/psf/
Free Software Foundation - http://www.fsf.org/
Apache Software Foundation - https://www.apache.org/
Software Freedom Conservancy - http://sfconservancy.org/about/

From:
https://opencollective.com/faq

Open Collective takes 10% of the money raised by the collective for managing their bookkeeping, taxes, and the admin of reimbursing their expenses. We share this commission with the fiscal sponsor (legal owner of the bank account that holds the money on behalf of the collective).
Additionally, our payment processors charge a fee - Stripe for receiving money via a Credit Card and PayPal for paying out expenses. Usually 2.9% + $0.30 per transaction. We are exploring adding other means of payments, including ACH transfers and Bitcoin, to reduce those fees.

Here's my quick vote on the options listed by @stevepiercy, plus Patreon:

Patreon is my preference
Open Collective is an option
Software Freedom Conservancy would be my third option

The ones I'm not so sure about:

The link to School Factory returns a 404
Python Software Foundation is a nice bunch of people, but the Cookiecutter maintainers would like more control over how finances would be utilized
Free Software Foundation is too tangential
Apache Software Foundation has too long a process and unfortunately has a reputation as being the place where projects go to die.

The one I won't allow:

Gratipay isn't an option due to the founder's personal views and odd reputation when it comes to payment systems. Even if I were overruled, adopting it for Cookiecutter would color this project (a female-founded project) negatively.

I created a patreon page for my work on Cookiecutter! 💵 🍪

Hey @kevindiamond! 👋
Any updates from your organization regarding sponsorship for cookiecutter development?

🔔  @kevindiamond

If you or your company want me to promote you in social media, then sponsor @hackebrot's Patreon account.


message feed: Improve Color Contrast for alert_word Highlighting in Night Mode

This pull request addresses various style enhancements in dark mode to improve readability and accessibility:

All colors used in this pull request have been suggested  in #12614(comment)
Adjusts the color and background-color of alert words for better visibility.
Modifies the link color to enhance contrast and readability.
Improves the search result background-color for a more cohesive dark mode experience.
I've ensured that the changes made for dark mode don't affect the light mode. Attached is a screenshot of the light mode that shows the adjustments made exclusively for dark mode, ensuring readability and accessibility.

Fixes: #12614
Screenshots and screen captures:

Dark Mode Before Changes for Alert Word:

Dark Mode After Changes for Alert Word:

Dark Mode Before Changes for search results

Dark Mode After Changes for search results

Light Mode:

Doesn't Effect the Changes for Search Results:

Doesn't Effect the Changes for Alert Word:

Before Changes for highlighted link text:

After Changes for highlighted link text:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Thanks for the contribution @amaranand360 !!. The maintainers will review your work shortly, but I wanted to state that your commit message and PR discription don't match Zulip's style.
You can refer to Zulip commit message guidelines  for details.It will save some review time.

@LaPulgaaa  I created a pull request for issue #12614  three days ago but I haven't received any updates from the reviewer. Please let me know if there's anything I need to do on my end.

@LaPulgaaa I have updated all commits of PR to match Zulip's style. Please let me know if there is anything else needed from my side.

This still might not be fully correct. Plus you may also want to update the PR title. Please go through the docs I linked above .

@LaPulgaaa I have updated the PR title and refined the commit message by removing generic terms like 'fix.' and let me know if there are any additional changes or actions required on my end

Thanks! Does this implement the design changes described in https://github.com/zulip/zulip/issues/12614#issuecomment-1556028086?

If so, this should be explicitly noted in the PR description. If not, please update this PR to do so, since that's the current next step for this issue.

@alya Yes, it does. I have Used the suggested color design changes described in #12614(comment). The originally provided color values were in hexadecimal format, but I have converted them to HSL format, which aligns with the color format used in Zulip.

@LaPulgaaa  and @alya , I’ve changed the description of my Pull Request based on your suggestions.  Please take a moment to review, and if there are any additional improvements  let me know. Thank you !

Thanks! The PR description is still not very clear. Were light theme colors changed?

@alya No, the light theme colors remain unchanged. I've updated the pull request description accordingly and attached screenshots to confirm. Please review the updated information. Thanks!

Thanks!
In general, making an effort to communicate as clearly as possible on your PR will make the review process go a lot quicker. :)

@alya Thank you for your insight, I have updated my PR according to the commit style guidelines. Please review the updated information.

@karlstolley I have implemented the changes as per your suggestions. Kindly review the updated information and provide your feedback.

You need to clean up your commit history with git rebase, and not just stack new commits onto the old ones.

I am

Hi @karlstolley ,
I've opened a new PR, #28973, to address Issue #12614. Following your suggestion, I've cleaned up the commit history and introduced CSS variables. Could you please review the changes?
I apologize for closing this pull request due to merge conflicts.

You shouldn't need to start a new pull request; you can reopen this one and push your changes here. This will help by keeping all the review comments in one place.

 OK, request for next time then.


container image used by the lint job doesn't contain git

Orb version
8.14.0
What happened
I wanted to publish my orb to the registry when a tag is pushed. It happened that the checkout step for the orb-tools/lint job failed systematically and I noticed that the singapore/lint-condo image doesn't have git installed.
Either git or ssh (required by git to clone through SSH) is not installed in the image. Falling back to CircleCI's native git client but the behavior may be different from official git. If this is an issue, please use an image that has official git and ssh installed.
Enumerating objects: 136, done.
Counting objects: 100% (136/136), done.
Compressing objects: 100% (74/74), done.
Total 136 (delta 45), reused 125 (delta 43), pack-reused 0

object not found

https://circleci.com/gh/simonpasquier/prometheus-orb/96
I've worked around the issue by not running the lint job on tags. Which is mostly fine as the linting already happened when merging to master.
Expected behavior
No checkout error in the lint job.

@simonpasquier you can always use pre-steps to, for example, quickly install git:
https://circleci.com/docs/2.0/reusing-config/#using-pre-and-post-steps
that said, the source of the orb-tools/lint job runs checkout automatically & this typically works for our repos—our checkout step is not actually dependent on git

@simonpasquier what does seem like a good option, though, is making the executor for lint customizable, so if you want to use a different docker image, you can. i'll do that right away.

change made in<EMAIL_ADDRESS>@simonpasquier

Thanks for the quick response! As I said, I wasn't blocked by this but having a way to override the image is always nice...


0.9.9 - don't work "network" {bandwidth*}

'Network speed' is working on 0.9.8.
I don't know why. Now (0.9.9) always static 0 bit/s (or octet). Maybe I can try something step-by-step? Let me know, please.
My config:
"network": {
    "format-wifi": " {bandwidthDowbBits}  {bandwidthUpBits} ",
    "format-ethernet": " {bandwidthDownBits}  {bandwidthUpBits} ",
    "format-linked": "(No IP)",
    "format-disconnected": "",
    "on-click": "alacritty -e nmtui",
    "tooltip": false,
    "interval": 5
}

And, and, and. When "format-wifi" - nothing is displayed (empty, even without icons).

I believe it was caused by commit 9d9f95976926d5817837d03344b9506d700cee16 which states that setting interface to "*" should result in the same as the old auto implementation. This isn't documented in the wiki though and should probably be the default since the old default no longer works.

I've done testing on that commit and setting the interface to "*" does not have the same behavior as the old auto implementation. There probably wasn't enough testing done on different configurations prior to this commit, and I'm working on a fix. In the meantime, a PR to fix the wiki and reset the default would be helpful.

I've done testing on that commit and setting the interface to "*" does not have the same behavior as the old auto implementation.

How to set up multiple interfaces?

I don't think it's just the "auto" or wildcard detection; even when I set up the interface to enp5s0, my wired connection, I still get 0o/s even though I can clearly see large numbers in /dev:
$ cat /proc/net/dev | grep enp5s0
enp5s0:<PHONE_NUMBER> 3216162    0    4    0     0          0      1262 325850572 1492065    0    0    0     0       0          0

https://github.com/Alexays/Waybar/issues/610 was the initial issue that the commit was trying to fix
https://github.com/Alexays/Waybar/issues/1327 is a duplicate issue
@ciarand Thanks for taking up the initial issue and pushing a fix! Before anyone else dives into the code, do you have an idea of why the above behavior would be happening?

I had another type problem (network related) so I looked at the code.
and between 0.98 and 0.99 only 2 changes were made to network.cpp (1 of which was a comment)
the other is line 81 want_route_dump was changed from false to true, changing it back fixed my problem.
I think that the change was done to try and show initial parameters (bandwidth doesn't show immediately, but after 1st refresh)
But evidently setting want_route_dump to true creates some other issue(s).

I don't believe this solves the "auto-select" problem either
On Sat, Feb 5, 2022 at 9:20 AM droc12345 @.***> wrote:

I had another type problem (network related) so I looked at the code.
and between 0.98 and 0.99 only 2 changes were made to network.cpp (1 of
which was a comment)
the other is line 81 want_route_dump was changed from false to true,
changing it back fixed my problem.
I think that the change was done to try and show initial parameters
(bandwidth doesn't show immediately, but after 1st refresh)
But evidently setting want_route_dump to true creates some other issue(s).
—
Reply to this email directly, view it on GitHub
https://github.com/Alexays/Waybar/issues/1392#issuecomment-1030653054,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALWO5TFBKUQFQORW3ZQQ7JTUZVE37ANCNFSM5L7EJNIA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you commented.Message ID:
@.***>

I agree - it appears with regex you can ignore interfaces you don't care about, but there isn't logic to determine prioritization of networks. Maybe we could add some logic to find all interfaces matching the config file, then sort by volume of network traffic?

Ohhh, thanks to @droc12345, I've just realised what was meant by "interface" in this thread! It's a waybar config setting. So now adding the interface line makes my bandwidth show up again :)
"network": {
    "interface": "wlan0", // This is the magic line
    "format-wifi": " {bandwidthDowbBits}  {bandwidthUpBits} ",
    "format-ethernet": " {bandwidthDownBits}  {bandwidthUpBits} ",
    "format-linked": "(No IP)",
    "format-disconnected": "",
    "on-click": "alacritty -e nmtui",
    "tooltip": false,
    "interval": 5
}

Great point. Just brainstorming here. What about this - building in scroll functionality for the network module, where when you scroll on the module, it cycles through all the interfaces that match the regex? This would remove the need for interface to be a required parameter, or for us to try and guess a default.

If there is no interface specified (not sure why we really want that) then is there a way to provide an ability to show all interfaces and allow the user to select one? prog/script pops up when no interface is specified or there is more than 2 interfaces (lo and another) . To me this would be easier than trying to fit scrolling/cycing.
The reason I don't disregard lo completely is that someone, somewhere will want to see it. lol
Lets look at my case, I have lo, eth0 and when I turn on the vpn I have tun0, and when I turn the vpn off tun0 goes away.
Could that be handled by scrolling/cycling, ie would the choices be static (from when I started waybar)?

I believe that the networks would be polled and matched against the "interface" parameter on every refresh. The current default is 60s.
So it would be a matter of storing an array of interfaces with associated network information and updating the entire array each refresh period. Then having way bar select one interface from that array to display, and building a functionality to change which is displayed (whether the built in scroll ability, the click functionality, or something new) and persisting that selection across refreshes.

That might work (mine is 2 sec refresh as I like to see more or less current usage) and as long as the interface parm is still being recognized, then I see no harm.
You might want to keep a flag for interface/no-interface(or wildcard) so that easy choices could be made if this extends into more than one or two functions though.

If a function calls some other function or the code changes extends into multiple functions, and it has to make choices based on being given an interface name or finding them out, it would be nice to have a flag saying it's been given an interface vs figure out the interfaces, kind of like the want_route_dump flag, just something that's easy to use for making choices.
I could just be overthinking it too. lol
I'll mention the interface (config file) once again, whether using the interface tag or making a choice because they're offered multiple interfaces (scrolling, etc), they HAVE to make a choice. To me it's easiest to do it in the config file.
Another possible option (just off the top of my head) is if no interface specified, put all that data into something like a tooltip that shows all interfaces (and data) when hovered, rather than letting them select from scrolling/menu selection

I think just updating the wiki and describing the scroll/function is best, and leaving the current config default of "*" if no interface is specified.

Another possible option (just off the top of my head) is if no interface specified, put all that data into something like a tooltip that shows all interfaces (and data) when hovered, rather than letting them select from scrolling/menu selection

So this would entail changing the default tooltip format to being a list of possible interfaces and data. I think it would only be feasible to list the interfaces, not the data. That would be a ton of text for a tooltip otherwise. But that is a good idea - could format it like the default CPU tooltip?
Could we combine the two ideas? If no interface is specified use * as the default, have the default tooltip be a list of interfaces, and include scroll functionality by default as well?

That sounds feasible

Might mention in the docs/wiki that the interface name (config option) is the same as what is returned from
ifconfig, ip addr or netstat -i

That's really helpful, I agree.
I'm going to start work on this at https://github.com/bd-g/Waybar, you're welcome to contribute/collaborate

line 108-117 of network.cpp has an if condition to check whether the interface is up (want_route_dump_)
then either sets the flag OR sets it for link and addr. I think this is wrong.
I think that link and addr should always be set (remove them from the else) and just toggle the route flag if interface is not specified. I'm basing this on the fact that want_* are supposed to handle multiple calls.
This is off the top of my head, so I haven't tried it.

I'm not sure about compatibility with old behavior but got mine to work without explicit interface with this change to Network::checkInterface
diff --git a/src/modules/network.cpp b/src/modules/network.cpp
index 74b54d9..3b88011 100644
--- a/src/modules/network.cpp
+++ b/src/modules/network.cpp
@@ -395,7 +395,8 @@ bool waybar::modules::Network::checkInterface(std::string name) {
     return config_["interface"].asString() == name ||
            wildcardMatch(config_["interface"].asString(), name);
   }
-  return false;
+  spdlog::debug("ifname_: {}; name: {}", ifname_, name);
+  return ifname_ == name;
 }

 void waybar::modules::Network::clearIface() {

For me the bandwidth did not show up correctly on wlan0 as described here and https://github.com/Alexays/Waybar/issues/610.
I built a go custom app based on i3-netusage and uploaded it to Github. Maybe it helps you as well :)
I tried to add autodetection of the gateway interface. Not sure if it does work correctly. Just had some late night coding time :D
https://github.com/cmprmsd/sway-netusage


Allow changing of the color_theme

Can we get a pypi update after this?

No?

I added 2fa to my account, and now I need to figure out, how to use twine with that.

It's there


Add C++ wrapper for SPIFFE credentials v2

This is the first of two PR's with the goal of adding a C++ wrapper for the SPIFFE credentials in the C core (these were added in #17549 and #17979).
This PR adds the API's for the wrapper, and the second PR will fill in the wrappers for the TLS credential options. (There was an earlier PR, #19765, that had some merge conflicts. This PR resolves those conflicts.)
As this PR touches some surface-level C++ API’s, please let me know if a gRFC proposal is needed/preferred first.

@markdroth This PR modifies public headers  - include/grpcpp/security/credentials.h and include/grpcpp/security/server_credentials.h. As the API's are already marked as experimental, do we still need an gRFC for it?

Thanks Matt for the PR. I found the following two main issues:

I did not see CPP implementations of credential reload and server authorization check config. I am not sure if you plan to do it in the second PR, but since you have already placed the implementation of key_materials_config in this PR, I think it also makes sense to have the implementations of the other two configs in this PR as well.

Please add unit tests for each config and credential option that is newly added.

I will go over it again once the above two issues are addressed.

Thanks for your comments Yihua. I have added a few commits to address these issues. Also, in this comment, I'd like to clarify the scope of this PR.
This PR adds the API's, unit tests, and certain small implementations of the API's for the C++ wrapper of the SPIFFE credentials. A subsequent PR will add the rest of the implementation of the API's, and add a few more tests. To be precise, the implementations that remain to be written are the functions that convert a particular C++ data structure (e.g. the credential reload config) to the analogous C data structure.

Per discussions with Yihua, the scope of this PR has been expanded: it will now consist of the entire SPIFFE C++ wrapper project.
The PR should not be accepted at this stage - there are comments and additional tests that I'd like to add. This most recent commit exists to show Yihua some of the implementation details.
In addition, here are two small comments on the recent changes:

The same trick was often used in src/cpp/common/tls_credentials_options.cc to go between C and C++ callback, schedule, cancel, and destruct functions. For a simple instance of this trick, see the implementation of TlsCredentialReloadArg::c_callback() on lines 123-131 of this file.

This most recent commit involved a couple of small changes to src/core/lib/security/security_connector/ssl_utils.h that are part of a PR-in-progress from Yihua (they have to do with PemKeyCertPairs being movable vs. copyable). These changes will be reverted in a subsequent commit because they are no longer needed in this PR.

There are some unexpected changes?

There are some unexpected changes?

Sorry about that - my local copy was behind the master and I pushed to my branch, so it added changes to a bunch of files. It should now be fixed (i.e. the only changes are the intended ones).

Thanks Matt for the PR. Looks good overall. I left some minor comments in tls_credentials_options.h, and will go over the remaining files (i.e., .cc and tests) again.

Thanks for your comments Yihua. I replied to some comments; if I didn't reply at all, then I definitely made the change. There were a couple changes I didn't make and I left explanations as to why.
Thanks again!

The PR looks great! Only some minor comments.

Thanks Yihua for the comments. About your Delete comment: it's worth checking out the end of the TlsCredentialsOptionsCppToC unit test to see the memory management required by the user. I make the user responsible for cleaning up the key materials, and cleaning up memory they allocated in constructing any C args (it's probably the gRPC stack doing the latter).

@jiangtaoli2016, could you please take another look?

Hi Matt, I just realized that we probably need to add more comments in the options, configs, and args defined in tls_credentials_options.h as they are the ones that will be directly used by applications, and we need to tell the applications how to use them (e.g., for args, we need to tell the applications that they need to invoke the callback after finishing the schedule operation). You can briefly explain them and then point to include/grpc/grpc_security.h for more details.  Sorry for notifying it at the last minute.

Thanks for mentioning this Yihua - I added brief comments in tls_credentials_options.h, and referred to your detailed descriptions in grpc_security.h for more details.
Also, I don't have "write access" for gRPC, so once the PR is approved by Jiangtao I will need someone to initiate the merge, if possible. Thanks!

Thanks for the comments Jiangtao! I changed the naming from "SPIFFE credentials" to "TLS credentials" everywhere that it was used.

@markdroth, could please have a look when you get a chance? Thanks! :)

ps. If it is not obvious, my comments are mostly on the first config class but I believe most of them apply to the other one as well.

@yang-g Thanks for the comments! I think I've addressed them all, except for the one having to do with a possible bug in tls_credentials_options_util.cc file, for which I have left an explanation.
If you have any other comments, please let me know! Otherwise, perhaps @yihuazhang you could take another pass when you have a chance? Thanks!

@yang-g Thanks for your comments! I have addressed them all. The only requested change I did not implement was removing Release (see my comment for the reason), and also please have a look at my solution to the bug you pointed out (in brief, adding unique_ptr's).

@yihuazhang The changes we discussed offline have been implemented in the most recent commit, and the PR is ready for you to take a second look at.

Thanks Matt for the changes. It looks good overall and I left some minor comments.
I think it will be useful to document/explain rationale behind some specific changes in this PR, which will be applicable to other SPIFFE wrapped language implementations. Given below is my brief summary:

In C++ wrapper, we need to provide C++ versions of different configs (e.g., TlsServerAuthorizationCheckConfig) and corresponding args (e.g., TlsServerAuthorizationCheckArg).

We need to provide a conversion from C++ configs to C-core configs, which is needed in order to pass it to C-core stack (via grpc_channel_credentials -> grpc_security_connector). In this PR, this conversion is done in tls_credentials_options_util.{h, cc}. C++ configs should maintain a field that points to the converted C-core config.

When C-core stack invokes API's in C-core configs, it will eventually need to invoke C++ config API's implemented by user applications, which requires to access C++ config from a C-core arg. In order to do that, we added a new field in C-core arg that points to a corresponding C-core config, and added a new field - context in C-core config that points to C++ config. Then, the last thing that remains is to create a C++ arg from C-core arg, and passed it to C++ config API. C++ arg should maintain a field that points to the C-core arg, which is necessary to return the result of C++ config API back to C-core.

We added a new field - context to C-core arg that points to the C++ arg to make C++ arg have the same lifetime as that of C-core arg. By doing that, we are able to map C-core arg that is passed to Cancel API to a corresponding C++ arg that is understood by user applications so that it can remove the previously scheduled request from a processing queue if needed. @yang-g I believe it will resolve the issue we discussed offline last week.

Thanks for the review @yang-g .
@yihuazhang For the 5 failing tests,

Basic Tests C/C++ MacOS: appears to be known issues 19422 and 20116.
Basic Tests Node MacOS: second target failure appears to be issue 20545 and fourth target failure appears to be known issue 19422; the first and third target failures appear to be related to the other two.
Basic Tests Python Linux: first target failure appears to be issue 20459; the other two target failures appear to be unrelated to this PR.
Bazel RBE Windows Opt C/C++: appears to be known issue 20519.
Interop Cloud-to-Prod Tests (Internal CI): appears to be issue 20502.

Thanks @matthewstevenson88. All failed tests do not seem to related to this PR.


Overlay support spec doc

add a folder for specs and add the first spec doc for overlay support.

We should add some discussion of the developer experience of applying an overlay. Is this a separate OverlayService class? Is it an extension method on OpenAPIDocument? Does it change the existing document or create a new patched document? Is it in a different project? If not, how do we handle the YAML dependency?

Maybe use this issue to add onto some of the use cases or scenarios where overlays would come in handy https://github.com/microsoft/OpenAPI.NET/issues/615

We should add some discussion of the developer experience of applying an overlay. Is this a separate OverlayService class? Is it an extension method on OpenAPIDocument? Does it change the existing document or create a new patched document? Is it in a different project? If not, how do we handle the YAML dependency?

@darrelmiller I have added a section on 'User Journey' to start the discussion. Have a look at it and continue the discussion.


New version: WriteVTK v1.2.3

Registering package: WriteVTK
Repository: https://github.com/jipolanco/WriteVTK.jl
Created by: @jipolanco
Version: v1.2.3
Commit: 3ad10a93eaa569d88a73ff4d9cb452312b5da174
Reviewed by: @jipolanco
Reference: https://github.com/jipolanco/WriteVTK.jl/commit/3ad10a93eaa569d88a73ff4d9cb452312b5da174#commitcomment-36337022

Should be 1.3 since it includes new functionality?

I guess you're right. The new functionality is very minor and not even documented for now, that's why I chose 1.2.3. I'll document it and push 1.3.0.


metanorma/metanorma-cli#273 do samples/templates testing on site

metanorma/metanorma-cli#273

This is failing, so I can't merge it @CAMOBAP

@opoudjis yep, I will move it to draft, sorry for confusion

@ronaldtse based onhttps://github.com/metanorma/metanorma-cli/pull/295#issuecomment-1415285229  and https://github.com/metanorma/metanorma-cli/pull/295#issuecomment-1420750690 I have implemented templates, samples testing on all OS/ruby versions
It takes more time than usual because missing cache for ruby-setup, but once we got merged it will still take few hours to run 1-3h. And release will happen after it
Should we go with these matrices or cut/optimize them?

@CAMOBAP I am fine with the current setup. Any thoughts @opoudjis ?

@ronaldtse for now in the matrix we have 2.7, 3.0, 3.1, 3.2 (experimental)
Maybe we can skip 3.0?
@opoudjis I would like to get your feedback too because I will apply this workflow to all metanorma-* repos

We could skip 3.0 for the final release since we already test it in the gems.

In fact, @CAMOBAP, which is needed is some sort of automated cascade of releases, because of the time lag:

I will release the utility gems outside the cascade: because they are dependencies, they need to release outside the fortnightly cycle
The cascade is: isodoc, then metanorma, then metanorma-standoc, then the flavours as shown above
isodoc, metanorma, metanorma-standoc are direct dependencies for each other. Standoc processing can only initiate once isodoc is released, and the gem is available to standoc. (Metanorma gem circular dependency is very rarely an issue, and if it becomes one, I will be manually releasing it.)
Similarly, iso can only release once standoc is released and available; iec once iso is available
... But all that needs a script your side.
And this will still prove unworkable, because GHA is monstrously unreliable, and fails for all sorts of reasons (as you know very well, @CAMOBAP, because you're who I complain about it to). But without some sort of automated release schedule, it will be so unworkable that I simply won't do it...

Test each gem locally, because that's how I identify and propagate changes resulting from dependencies of gems.
Does it mean that only one OS was covered during local testing, docker also tests only Linux. How does this protect us from issues on other platforms?

It does mean only one OS is covered, and the entire point of the remote testing is to discover the issues on other platforms. That's how it is already, and that's how it's going to remain. I only program in one platform, so this is not a new issue.

....When I have concluded going through all the gems, check their status on GHA.
To be on the same page, what exactly are you checking just that test passing or anything else?

Yes, just that. Again, that's all I do now.

Remote testing such as you are proposing is going to take tens of minutes of dead time during which I am waiting idly for things to be resolved
You mean the time that you need to wait between one gem release in progress and starting a release of the next gem, right? Ideally, we have a ticket that can address this metanorma/metanorma-release#21

Yes, in cases of direct dependency, I expect the released gem to be available IMMEDIATELY; that is the case for html2doc > isodoc, isodoc > metanorma > metanorma-standoc. Even with delayed dependency, I am very worried that metanorma-iso might not be online by the time I come to release metanorma-iec. But if all the releasing is done by a remote script, at least I'm not left waiting around.

From your perspective, it will look like a workflow where each job will responsible for the release of a particular gem. Dependencies between these jobs will the same as you listed in the comment above. So you will not have to wait to start next release, workflow will do it

So, to understand:

I hit release of html2doc
I compile html2doc locally <== I still have to do that, because the dependencies have to be tested for locally
I start debugging of isodoc
I hit release of isodoc
If html2doc testing is still running, isodoc testing and release process will wait until the updated version of html2doc is available
And the remote isodoc test will know that an html2doc job is underway or has failed, as opposed to me deciding not to release a new version of html2doc this fortnight

... You understand why I'm hesitating: there are a lot of moving parts.

This update is apparently going to introduce a whole lot of remote testing dead time between release of individual flavours, as templates and samples are tested in each successively.
Unfortunatelly yes, but on another side, it will keep it more stable and safe.

Yes. That's all true. And I reiterate, if this ends up meaning that a release is spread over three days, or that I have to wait until 3 AM for a release to finish processing, then I will refuse to be involved in releases at all. That's why I'm offering the option of all-local testing followed by all-remote testing as a way of me not doing so.

Currently our metanorma-* also trigger builds for mn-samples-* and mn-templates-* (was done in the scope of metanorma/metanorma-cli#149) but how useful this approach? Those build just triggers but I'm not sure if someone checks the status of those builds. This PR is just a "evolution" of this approach

I tuned them out a long time ago. Not least because of constant false alarms.

The only way forward is:

Test each gem locally, because that's how I identify and propagate changes resulting from dependencies of gems.
Compile each gem as I go locally. No releases.
Hit some button to release all gems in the suite successively at the end
Walk away, and wait for separate remote compilation the following day
If any issues are identified in the process, fix, and re-hit the button.

According to my understanding, metanorma/metanorma-release#21 will be a such button. Probably the one difference is that it will do it in serial.
In case some issue happens (in the middle for example) this workflow it will fail. The fix needs to be applied, and workflow can be re-executed starting from failed gem and continued

Yeah, that's going to be pain, especially if the failure is a false alarm. Me actively monitoring this while at my day job the following day is an unreasonable request. This is at best an overnight glance.

And this will still prove unworkable, because GHA is monstrously unreliable, and fails for all sorts of reasons
Nothing is perfect, unfortunately, let's see how it will works on small subset of gems

I'm hearing this a lot from people lately. There's a difference between "not perfect" and "completely useless", and the former does not license the latter. The only way to find out which applies is to try it. I can only repeat that, if GHA remains as unreliable as it has been, this is not going to work. I'm not going to wait for days instead of hours because GHA jobs become unavailable; and that's the risk this is introducing.

Ok, @CAMOBAP, I think we're now on the same page...

@opoudjis could you please ping me when it is safe to merge this release this PR (to not interfere with current release)

@opoudjis could you please ping me when it is safe to merge this release this PR (to not interfere with current release)

@CAMOBAP Safe to merge, though I'll let you do the merging.

This PR was just for testing, https://github.com/metanorma/ci/pull/105 - is merged


starter integration tests and convenience init function

Any interest in merging this? can close if not

TBH, not really. I think it would be better if the thread count issue was handled in the gcd code path instead.

Sounds good, will close then


CSS animations trigger on initial render due to more digest cycles

Angular waits two digest cycles before enabling the animations and that's great, but it results in unwanted behaviour if you have more than two cycles before first render(e.g. due to using templateUrl, routing etc).
What is the best practice to avoid the animations on initial render? Having everything animate in on first render becomes pretty tiresome.

Before waiting for two digests, Angular waits until all remote templates (views & directives) have been fully downloaded. So it should never result in this happening.
Do you have an example of this in action?

I've made a plnkr showing the issue. The view slides in on load.
http://plnkr.co/edit/f4kfHqHSfJKjlWvY2Ghf?p=preview
Fullscreen: http://run.plnkr.co/E5q2mUlCWknaSMJM/#/

I'm seeing similar issues since updating to c8700f04fb6fb5dc21ac24de8665c0476d6db5ef on ng-hide elements that are nested within an ng-repeat which in turn is nested within an ng-if. I'm working around the issue by whitelisting via $animateProvider.classNameFilter('animated') and deferring the addition of the animated whitelisted class until after I know that initial render has completed.

@booleanbetrayal can you please provide an plnkr example? This may be a new issue entirely.

By the way, I'm currently dealing with my issue like so:
ng-click="animations.enableAnimations()" class="{{::animationStatus}}" on the body-tag.
Combined with a simple service with if($rootScope.animationStatus !=='animations') set animationStatus to 'animations'(which triggers my styling and enables the animations). It seems rather hacky and slobbish, but at least it works for now.

@matsko - Here's a plnkr of the isolated issue. It looks to be related to an asynchronous route resolver. The expected behavior is that any element with a ng-hide="false" should never be rendered visible. Let me know if I should create a new issue.
http://plnkr.co/edit/uk2Y0u?p=preview

Wondering if you saw this, and if it's still relevant @matsko. ^

This is expected - ngAnimate must decide to run animations at some point, and the current way of waiting for 2 digests works fine for most applications. You should use one of the ways described in the guide to disable animations until you need them, or where you don't need them: https://code.angularjs.org/snapshot/docs/guide/animations#how-to-selectively-enable-disable-and-skip-animations.
For example, in your applications .run block, you could call $animate.enabled(false), and only after your application has finished all initial async functions, call $animate.enabled(true) (wrapped in a timeout for good measure). Quick and dirty example: http://plnkr.co/edit/ds3fxW?p=preview


Unticking 'enable updates' doesn't fully pause updates

Moving the mouse over the charts causes some progression

Fixed by 0d41f7b56d52b894f5db0a77eba45baa533682e9 and be2cf76884e47e4b560e28bd3eb1e1da1a30d8cb


Outdated non-POSIX FreeBSD API used by tests

setgrent returned an int two years ago, but now (as of https://github.com/freebsd/freebsd/commit/786c3926a65879b5dd6c301ca9ccdfda486fd195 ) returns void. We're testing against the outdated API, which became an issue in #934
Thanks to @gnzlbg for finding the issue.

Note that setgrent did not get a new symbol version in FreeBSD for the changed ABI.

@asomers IIUC this function still returns an int in FreeBSD 11, that is, we can't change its prototype to specify that it does not return anything.
In FreeBSD12, the return value is invalid, and creating an invalid value is UB in Rust. I agree that, as long as FreeBSD library is always dynamically linked, that is, as long as LTO is not possible, this UB cannot break code that ignores the return value.


[Question]: After enabling the keyword, the parsing block is lost.

Describe your problem
When I was editing the parsing block, after adding a keyword and checking the enable box below, the entire parsing block disappeared after I clicked confirm. I am certain that the total number of parsing blocks decreased by one. Is this a bug?

I guess it's still in the chunk list but not in original order.

I checked the total number of blocks, and indeed there has been a reduction. The relevant parsing blocks are also missing, and this issue can be reliably reproduced.

Pull the latest dev version of docker image.


Enhance remote data

Related Issue
#457
Description
See #457
I have added an example demonstrating a remote data use case using RTK query, without messing with Promise and tableRef.onQueryChange. It should also work with other similar query-state-management libraries like Apollo Client.
Impacted Areas in Application
package.json --note: I am not updating package.lock.json because I am using M1 Mac for development and I cannot have esbuild in the dependency. Pushing the package.lock.json file will likely break current setup for other users.
material-table
data-manager
demos

May I have any feedback on this enhancement item?

I'm currently using redux-saga, I'm having trouble fetching data and rendering in a table, from recent fixes to the data parameter. Pagination doesn't work :-(

I'm currently using redux-saga, I'm having trouble fetching data and rendering in a table, from recent fixes to the data parameter. Pagination doesn't work :-(

Are you referring to the current release or referring to this PR? If it is about the current release version, you may file a new issue. If you found this pull request breaking your current setup, please provide an example.


jfsutils: fix cross compilation

Motivation for this change
Fixes https://github.com/NixOS/nixpkgs/issues/51126
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

I'd merge, but this can go to master?

Merged in 98a2a5b5370


Error related to ffmpeg

Thank you for nice work!
When I run demo.py file, python demo.py --video examples/IMG_9732.mov --visualize
The following error occurs. I have tried setting environment variables for ffmpeg and various other solutions, but to no avail.
How can I solve this problem?
Traceback (most recent call last):   File "/home/minjung/WHAM/demo.py", line 223, in <module>     run(cfg,    File "/home/minjung/WHAM/demo.py", line 177, in run     run_vis_on_demo(cfg, video, results, output_pth, network.smpl, vis_global=run_global)   File "/home/minjung/WHAM/lib/vis/run_vis.py", line 89, in run_vis_on_demo     writer.append_data(img)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio/core/format.py", line 590, in append_data     return self._append_data(im, total_meta)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio/plugins/ffmpeg.py", line 587, in _append_data     self._initialize()   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio/plugins/ffmpeg.py", line 648, in _initialize     self._write_gen.send(None)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_io.py", line 508, in write_frames     codec = get_first_available_h264_encoder()   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_io.py", line 124, in get_first_available_h264_encoder     compiled_encoders = get_compiled_h264_encoders()   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_io.py", line 58, in get_compiled_h264_encoders     cmd = [get_ffmpeg_exe(), "-hide_banner", "-encoders"]   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_utils.py", line 28, in get_ffmpeg_exe     exe = _get_ffmpeg_exe()   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_utils.py", line 44, in _get_ffmpeg_exe     exe = os.path.join(_get_bin_dir(), FNAME_PER_PLATFORM.get(plat, ""))   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/site-packages/imageio_ffmpeg/_utils.py", line 69, in _get_bin_dir     ref = importlib.resources.files("imageio_ffmpeg.binaries") / "__init__.py"   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/importlib/resources.py", line 147, in files     return _common.from_package(_get_package(package))   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/importlib/_common.py", line 14, in from_package     return fallback_resources(package.__spec__)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/importlib/_common.py", line 18, in fallback_resources     package_directory = pathlib.Path(spec.origin).parent   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/pathlib.py", line 1082, in __new__     self = cls._from_parts(args, init=False)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/pathlib.py", line 707, in _from_parts     drv, root, parts = self._parse_args(args)   File "/home/minjung/anaconda3/envs/wham/lib/python3.9/pathlib.py", line 691, in _parse_args     a = os.fspath(a) TypeError: expected str, bytes or os.PathLike object, not NoneType

Hi @minjung98 , it seems like there is some error in the path setting. Is your writer set to the correct path (i.e., the base folder exists?)

Hi, I have same issue. Did you solve it?


Upgrade to Kotlin 2.0

Upgrade the project to the latest Kotlin and KSP versions.

Just a clarification, does that mean that the project can still be used on Kotlin 2.0+, just that its build version is not that high?

I think that's the case, but I haven't tried it myself. Note that KSP2 will very likely not work due to the many bugs.

This was solved in #51


Vickel: Watch biggbosslive.live

Vickel requests the watch of the watch_keyword biggbosslive\.live. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

biggbosslive\.live has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Generalise Nondeterminism over any Foldable

Not sure if this is what 'TODO Can probably generalize over any foldable.' envisaged, but here it is anyway!
Potentially something not-entirely-thought-out could be of use:
runMaybe :: (Monad m, Foldable f) => Eff f m a -> m (Maybe a)
runMaybe = runNondeterminism (const Just) Nothing

Sure, why not :)


User creates a PR  Normal Mode - Significant CLA Not Signed_Apr6

Hi @brilliomsinterop, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla-ppe.dotnetfoundation.org.

TTYL, DNFBOT;

@brilliomsinterop, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;


Annotation cwl

Codecov Report

:exclamation: No coverage uploaded for pull request base (dev@d910ab3). Click here to learn what that means.
The diff coverage is 81.81%.

@@          Coverage Diff           @@
##             dev      #20   +/-   ##
======================================
  Coverage       ?   68.39%
======================================
  Files          ?       15
  Lines          ?      889
  Branches       ?        0
======================================
  Hits           ?      608
  Misses         ?      281
  Partials       ?        0

Impacted Files
Coverage Δ

tooldog/main.py
45.18% <100%> (ø)

tooldog/biotool_model.py
92.3% <100%> (ø)

tooldog/annotate/cwl.py
81.69% <71.42%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d910ab3...01dce12. Read the comment docs.


[pngpp] build failure

Host Environment

OS: Windows
Compiler: MSVC

To Reproduce
Steps to reproduce the behavior:
./vcpkg install pngpp
Failure logs
Starting package 5/5: pngpp:x86-windows
Building package pngpp[core]:x86-windows...
-- Downloading http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz -> png++-0.2.10.tar.gz...
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz
[DEBUG] Download failed -- retrying after 1000 ms.
[DEBUG] Download failed -- retrying after 2000 ms.
[DEBUG] Download failed -- retrying after 4000 ms.
Error: Failed to download from mirror set:
http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz: WinHttpReceiveResponse() failed: 12030
http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz: WinHttpReceiveResponse() failed: 12030
http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz: WinHttpReceiveResponse() failed: 12002
http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz: WinHttpReceiveResponse() failed: 12002

[DEBUG] D:\a\_work\1\s\src\vcpkg\base\downloads.cpp(705)
[DEBUG] Time in subprocesses: 0 us
[DEBUG] Time in parsing JSON: 2 us
[DEBUG] Time in JSON reader: 0 us
[DEBUG] Time in filesystem: 7898 us
[DEBUG] Time in loading ports: 0 us
[DEBUG] Exiting after 4.67 min (280193280 us)

CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:84 (message):

      Failed to download file with error: 1
      If you use a proxy, please check your proxy setting. Possible causes are:

      1. You are actually using an HTTP proxy, but setting HTTPS_PROXY variable
         to `https://address:port`. This is not correct, because `https://` prefix
         claims the proxy is an HTTPS proxy, while your proxy (v2ray, shadowsocksr
         , etc..) is an HTTP proxy. Try setting `http://address:port` to both
         HTTP_PROXY and HTTPS_PROXY instead.

      2. You are using Fiddler. Currently a bug (https://github.com/microsoft/vcpkg/issues/17752)
         will set HTTPS_PROXY to `https://fiddler_address:port` which lead to problem 1 above.
         Workaround is open Windows 10 Settings App, and search for Proxy Configuration page,
         Change `http=address:port;https=address:port` to `address`, and fill the port number.

      3. You proxy's remote server is out of service.

      In future vcpkg releases, if you are using Windows, you no longer need to set
      HTTP(S)_PROXY environment variables. Vcpkg will simply apply Windows IE Proxy
      Settings set by your proxy software. See (https://github.com/microsoft/vcpkg-tool/pull/49)
      and (https://github.com/microsoft/vcpkg-tool/pull/77)

      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Thanks for posting this issue. Could you please try to download the attached file manually and put the archive file into VCPKG_ROOT/downloads folder, then rebuild this?
png++-0.2.10.tar.gz
This error due to your proxy didn't set correct, you need use proxy to download those files:
Error: Failed to download from mirror set:
http://download.savannah.nongnu.org/releases/pngpp/png++-0.2.10.tar.gz: WinHttpReceiveResponse() failed: 12030

It works. Today it also works normally without that downloading the file manually. Not sure what changed.


Type safety on Workflow Launch Args

Is your feature request related to a problem? Please describe.
It's unfortunate that when I launch a Workflow the arguments I pass to launch it are not typed. So I don't get a compiler check.
Describe the solution you'd like
The short version? I want launch to be smart enough to know what the first item in the Workflow expects for its WorkflowInput and have that type be what I pass as args. Additionally if that type is Never I want to be forbidden from passing args and if that type is not Never I want to be forced to pass args.
Potential solution:
Combine has Publishers that end up chaining in an interesting way with Generics that we could rip off. For example
Workflow(FR1.self) creates a Workflow. But Workflow(FR1.self).thenProceed(with: FR2.self) creates Workflow<FR2, Workflow<FR1>> or...something like that? The solution is not totally ironed out in my head, but the premise is that you'd be able to backtrack through all the nested Workflows until you got to the first one, thus knowing the FlowRepresentable type that comes first and asserting launch happens with the correct input.
Describe alternatives you've considered
I suppose there's a simpler approach that is a little less consumer friendly where they just pass the FlowRepresentable type that is going to be launched and we steal the WorkflowInput from it. I'm not really a fan because it adds an unneeded parameter.

This is an absolutely insane example but it showcases a little of how this might be able to work. It's heavily inspired by Combine and not quite right still, but I think it demonstrates how this could be accomplished at all.
import Foundation

protocol PThing {
    associatedtype Upstream = Never
    associatedtype T
}

enum AllThings {

}

extension PThing {
    func then<V>(_ v: V) -> AllThings.CThing<Self, V> {
        AllThings.CThing<Self, V>(v)
    }

    func firstType<U>() -> U.T.Type where U: PThing, U == Upstream {
        U.T.self
    }

    func firstType() -> T.Type where Upstream == Never {
        T.self
    }
}

extension AllThings {
    class CThing<Upstream, T>: PThing {
        typealias Upstream = Upstream
        typealias T = T
        init(_ t: T) { }
    }
}

class Thing<T>: PThing {
    typealias Upstream = Never
    init(_ t: T) { }
    func then<PT: PThing>(_ pt: PT) -> PT where PT.Upstream == Upstream {
        return pt
    }
}
var a = Thing<String>("")
print(a.then(true).firstType()) // prints "String"

This seems like a great idea, not sure when it will be a focus for us, but we're keeping an eye on it! 👍🏻

Update: The SwiftUI approach we've taken (or even alternative paths we've considered) tends to give us this, the issue isn't all the way closed since it'd be nice to see it in UIKit too.

I feel like this might be part of a bigger issue request to convert workflow UIKit to the more fluent API in SwiftUI. I'm thinking the change would be breaking though so we may want to batch a couple of changes together and do it all at once.


CFP: Gateway API - add ALPN negotiation to cilium-envoy for gRPC support

Cilium Feature Proposal
cilium-envoy is currently missing ALPN config section in the DownstreamTlsContext which results in envoy not exposing ALPN altogether.
The reason why we even need ALPN config is because as per gRPC protocol, clients must use HTTP2 and they must negotiate ALPN. While the requirement for HTTP2 is understandable, it's not clear to me why doesn't gRPC allow http2-prior-knowledge (HTTP/2 over a plain TCP connection). grpc/grpc-java#5167 grpc/grpc-java#7201 grpc/grpc-java#5543 This is reproducible throughout most of the platforms: I tried Java, Go, Python, PHP, and all of them fail sending gRPC tls client requests without ALPN.
Supporting ALPN is a very trivial patch to cilium-operator:
Index: operator/pkg/model/translation/envoy_listener.go
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/operator/pkg/model/translation/envoy_listener.go b/operator/pkg/model/translation/envoy_listener.go
--- a/operator/pkg/model/translation/envoy_listener.go	(revision 93d4f151799025dfe50b290e2c8f249773f13f9c)
+++ b/operator/pkg/model/translation/envoy_listener.go	(date<PHONE_NUMBER>616)
@@ -277,6 +277,7 @@
 	downStreamContext := envoy_extensions_transport_sockets_tls_v3.DownstreamTlsContext{
 		CommonTlsContext: &envoy_extensions_transport_sockets_tls_v3.CommonTlsContext{
 			TlsCertificateSdsSecretConfigs: tlsSdsConfig,
+			AlpnProtocols:                  []string{"h2,http/1.1"},
 		},
 	}

It will unbreak gRPC support, but will break backends that do not serve dual HTTP1.1/HTTP2-H2C.
Since envoy is set up with useDownstreamProtocolConfig for connecting to upstream backends (i.e pods), it works fine for regular browser requests because without ALPN, browser will choose HTTP1.1 and receive the expected response.
However, if ALPN protocols setting is present (we will need h2,http/1.1), then browser will prefer HTTP2 over HTTP1.1, so requests to backends only serving HTTP1.1 will effectively fail with '502 protocol error'.
To address that, I have a suggestion to solve #30452 first.

Would love this to be fixed, currently struggling getting Vault to function without this. Where we have to fall back to using Traefik to serve this.

@dhaugli I'm planning to work on #30452 before we can bring this in.

Patiently waiting for this.

Not stale.


Disable cache for secrets

This PR removes the cached client and disables caching of Secrets to prevent a memory spike.

/hold


Could I create a mapping file for classes?

Question
There is any way to map my final compiled value with the real classname? Example:
.myClass {

}

<div className={styles['myClass']} />

At the end my classname will be a "randomically name", example: i28esa-sp. I want to create a .json file with something like:
{
  "myClass": "i28esa-sp"
}

I'm not really sure what the full question here is, sorry!


lastmod automatic conversion to date format recognized by Google crawler failed

Describe the bug
Google's crawler cannot parse date and time strings containing milliseconds, so when I return a date in this format of 2023-12-21T13:49:27.963745, Google's crawler fails to parse lastmod correctly.
However, as early as version 3.4.0, lastmod can be automatically converted into the 2023-12-21T13:49:27+00:00 format that can be parsed. Are there any major changes in this regard in version 4.0?
Using the example in dynamic url in<EMAIL_ADDRESS>the lastmod format is automatically converted

Reproduction
No response
System / Nuxt Info
------------------------------
- Operating System: Windows_NT
- Node Version:     v16.19.1
- Nuxt Version:     3.8.2
- CLI Version:      3.10.0
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      modules, ssr, runtimeConfig, app, css, devServer, devtools, device, experimental, gtm, nitro, pwa, site, sitemap
- Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>- Build Modules:    -
------------------------------

Hi @lxccc812, thanks for the issue.
I've pushed up a fix for this that will be released shortly. I think it got removed by accident with the refactoring.


fix(csharp): fix timestamp case in AdbcStatement.GetValue

Fixes #1278

⚠ Please follow the Conventional Commits format in CONTRIBUTING.md for PR titles.

You'd think I would have absorbed this by now :(.

⚠ Please follow the Conventional Commits format in CONTRIBUTING.md for PR titles.

You'd think I would have absorbed this by now :(.

Frankly, I've been meaning to improve it because it's not super friendly. And also, trying to settle on some sort of convention/tagging for issues too.


karma test error

when running npm test I get this error, though I already got karma installed globally and try to run with verbose mode, still I don't know where to find this bug.
'.' is not recognized as an internal or external command

ok solved it, doesn't have to use .bin on windows


i18n(fr): fix tutorial/5-astro-api wording

Description (required)
In French and in this context, tag should be translated with étiquette and not with balise. Also, this word is mostly used in 3.mdx so we should be consistent.

Related issues & labels (optional)

Suggested label: i18n, consistency/formatting

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
tutorial/5-astro-api/2.mdx
Localization changed, will be marked as complete.

fr
tutorial/5-astro-api/3.mdx
Localization changed, will be marked as complete.

fr
tutorial/5-astro-api/index.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


HDDS-10140. [hsync] Rebase HDDS-7593 branch onto master

What changes were proposed in this pull request?
Rebase HDDS-7593 branch onto master.
DO NOT MERGE! Once it is reviewed and pass tests I'll force push it to HDDS-7593, not master.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-10140
How was this patch tested?
unit tests.

/pending "DO NOT MERGE"

Pushed to HDDS-7593 manually. Close this one. Thanks for the reviews!


Integration with base OpenSearch 2.0 [PREVIEW]

Signed-off-by: Martin Gaievski<EMAIL_ADDRESS>Description
Initial integration with base OpenSearch 2.0. Using Alpha1 version of OpenSearch 2.0 as it's the only version with support of Lucene 9.1.
Creating draft PR to check if CI works. This is more like a draft at the moment, but feel free to leave early feedback.
Issues Resolved
No master issue yet, aiming 2.0 release
Check List

[X] New functionality includes testing.

[X] All tests pass

[X] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #328 (7711d48) into main (a45dc81) will decrease coverage by 0.35%.
The diff coverage is 83.26%.

@@             Coverage Diff              @@
##               main     #328      +/-   ##
============================================
- Coverage     83.74%   83.38%   -0.36%
- Complexity      885      923      +38
============================================
  Files           126      132       +6
  Lines          3801     3979     +178
  Branches        360      378      +18
============================================
+ Hits           3183     3318     +135
- Misses          457      492      +35
- Partials        161      169       +8

Impacted Files
Coverage Δ

...nsearch/knn/index/codec/KNN80Codec/KNN80Codec.java
30.00% <0.00%> (ø)

...nn/index/codec/KNN80Codec/KNN80CompoundFormat.java
95.23% <ø> (-4.77%)
:arrow_down:

...n/index/codec/KNN80Codec/KNN80DocValuesFormat.java
71.42% <ø> (-28.58%)
:arrow_down:

...nsearch/knn/index/codec/KNN87Codec/KNN87Codec.java
75.00% <ø> (-25.00%)
:arrow_down:

...nsearch/knn/index/codec/KNN84Codec/KNN84Codec.java
30.00% <33.33%> (ø)

...nsearch/knn/index/codec/KNN86Codec/KNN86Codec.java
28.00% <33.33%> (ø)

...c/main/java/org/opensearch/knn/index/KNNQuery.java
83.33% <66.66%> (+5.55%)
:arrow_up:

...n/index/codec/KNN91Codec/KNN91DocValuesFormat.java
71.42% <71.42%> (ø)

...n/index/codec/KNN91Codec/KNN91DocValuesReader.java
75.00% <75.00%> (ø)

.../main/java/org/opensearch/knn/index/KNNWeight.java
78.94% <75.38%> (+3.60%)
:arrow_up:

... and 13 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a45dc81...7711d48. Read the comment docs.

@martin-gaievski Does this take care of #303?

@martin-gaievski Does this take care of #303?

I may fix some compilation/failing tests issues while working on this change, but I didn't target #303 specifically. In scope of my PR I've fixed all integTests and BWC tests.

Created issue for core build project to address failing build #1817


Index Base

Describe the feature
Create a new indexer black to index Base
Expected outcome

Setup config for Base
setup indexer for these 2 collection

https://opensea.io/assets/base/0x26a1f8813df5a318ed7aa1091c30db0f25727a18/53692
https://opensea.io/assets/base/0x55e8749aa336d30df466078b9535cd97b5024dcf/1184

Let it roll

Reference

https://github.com/kodadot/ops-internal/issues/792

Additional context
Probably we can release a GenSol art.

#13


What will happen to this application when Inbox dies?

I, like many others, love Inbox and I am very sad to see it go (in March 2019). I'm now on the search for a new email client. This application came up in several searches but I'm wondering what will happen when Inbox goes offline. If you use their services will you suffer the same fate?

This client will probably die too.
However, it depends on what @jonorozcoc will decide about it. I think it's possible to reimplement all Inbox features using Gmail's API.

I'd be willing to help with development of an "Inbox" clone. I thought this repo was that, until I looked at the source code and saw that it just loads the official website in an Electron wrapper.

@byronigoe you're welcome. Ask me if you need something.


Cannot add O2M Composition item

TC

Open entity list for an entity that has a O2M Composition attribute
Click Create
Find O2M Composition attribute and click + Add entities
Click Create
Populate the editor fields
Click OK

AR
Nothing happens
ER
Child editor closed, create item added to child entity list

The ticket's problem appears inside @haulmont/jmix-addon-user-management addon's screens.
If we generate editors in our application O2M Composition attributes works correctly.

fixed with updating frontend model in front-demo-r2

TC:

Open the attached project -> Run app
Sales -> Product List -> Create any product
Sales -> Order List
Create a new instance -> try to add an OrderLine

AR:

frontdemo.zip


Add Ptr::try_cast_into method

try_cast_into attempts to cast a Ptr<[u8]> into a Ptr<U> where U: ?Sized + KnownLayout, and will be built upon in future commits as a building block of TryFromBytes.
Because try_cast_into performs a runtime check to validate alignment, this requires disabling Miri's "symbolic alignment check" feature. While it would be possible to run both with and without that feature in order to still test other code using symbolic alignment checking, I don't think that the benefit is worth a) the complexity of passing the information necessary for certain tests to not run under symbolic alignment checking and, b) the extra CI time to run Miri tests twice.
Makes progress on #29

Implemented in #406


kll size mismatch error possible in whylogs-sketching

Description
In certain scenarios if empty and single item kll sketches were serialized and then merged, this resulted in a kll sketch that reported a preamble of 2 but contained multiple items. This would cause serialization to fail as the single item format uses less bytes than multi item sketch serialization.
fix is in whylogs-sketching in 3.4.1.dev3 and higher.

fixed in: https://pypi.org/project/whylogs-sketching/3.4.1.dev3/


Incorrectly suggest you can select master' size

This article suggests that AKS will create a master node using the size specified; in fact, masters are run under the scene by Azure and not affected by the choice of agent node size.

@RothJa, Hi Jason, Can you please take a look at this GitHub Issue 1326.  Thanks.
.
https://github.com/MicrosoftDocs/sql-docs/blob/live/docs/big-data-cluster/deploy-on-aks.md#create-a-kubernetes-cluster
.
"Configure Azure Kubernetes Service for SQL Server 2019 (preview) deployments"
https://docs.microsoft.com/sql/big-data-cluster/deploy-on-aks.md#create-a-kubernetes-cluster
.
(GitHub Issues, Process info)
sqlcontentshiproom Notebook  >  sql-docs-pr  >  GitHub-ISSUES-Plan,-Rogue1
.
GeneMi ,  2018/11/26  10:50am  Monday
.
CC: @ams0

@ams0 I'm going to confirm this and then make the change to the article based on what I find. Thanks for the feedback!

@ams0 I've confirmed your understanding and will be correcting this shortly. Thanks for catching this mistake!


Issue #200, Resolve .jsx extension in webpack

Coverage increased (+0.2%) to 37.403% when pulling 4f3151413e9b0c25f982dace5a59c9a117010e87 on salmanmanekia:master into b4ccb126d98b13fee364842d4c8467d4d40ffbf9 on zeit:master.

Thanks for this. Related: https://github.com/zeit/next.js/pull/163
Actually, we allow you to customize webpack config as you like in the future.
So, you could do this yourself.
See: https://github.com/zeit/next.js/pull/222


Improve the homepage for signed-in users

On #2544 we changed the homepage. For anonymous users a static homepage is fine. For signed-in users we need some sort of dynamic timeline or whatevs at /.

Want to back this issue? Place a bounty on it! We accept bounties via Bountysource.

Closing in favor of #3183 and #3184.


Can't find variable yml file from non .github folder  in V 3.0.0

We have two repositories such as reusable workflow actions which is called workflow, and another repository is the end user which is
caller workflow.
We have used<EMAIL_ADDRESS>latest 3.0.0 version in our workflows and facing below issue where variable.yml is unable to identify the path.
we have placed under ./variables/dev/variables.yml
Error: Fail to retrieve files ./variables/dev/kafka.yml: Not Found - https://docs.github.com/rest/repos/contents#get-repository-content

Could you please help in resolving this issue.
Note: Please treat this issue at highest priority.

We have two repositories such as reusable workflow actions which is called workflow, and another repository is the end user which is caller workflow. We have used<EMAIL_ADDRESS>latest 3.0.0 version in our workflows and facing below issue where variable.yml is unable to identify the path.
we have placed under ./variables/dev/variables.yml
Error: Fail to retrieve files ./variables/dev/kafka.yml: Not Found - https://docs.github.com/rest/repos/contents#get-repository-content
 Could you please help in resolving this issue.
Note: Please treat this issue at highest priority.

@lindluni  -  could you please take a look

Hi @lindluni   - Could you please treat the above request at highest priority?

Hi @lindluni   -   Could you please take this as a priority. We are blocked in production actually. I would be great if you could take a look once. @joshjohanning

Hi @lindluni   -  Any update on the above issue. It would be great if you take this as a priority

I am unable to recreate this problem, and the large enterprises I have that are using this, are not seeing an issue.
Do you have a minimal scenario that I can use to recreate this problem?

Hi @lindluni  -  can we get into the teams or zoom call to troubleshoot this issue.

Hi @lindluni  - can we get into the teams or zoom call to troubleshoot this issue.

Hi
@lindluni  -   Can we have a live troubleshooting session. Please let me know if this is feasible for you

Hi @lindluni  - minimal scenario that I can use to recreate this problem -   please create a variable group file in non .github folder and refer that filepath in your workflow


Installation procedure

Hi, I'm trying to install it locally. I installed using the local.txt requirements:
pip install -r requirements/local.txt

And then I called:
python manage.py check_filenames

and I got this error:
  File "/Users/chper/Desktop/sct_web/sct_testing_management/sct_annotation/taskapp/celery.py", line 3, in <module>
    from celery import Celery
ImportError: cannot import name Celery

I think it would be nice to have an installation procedure that we can reproduce locally. Another question, am I supposed to use Python 2 or 3 ?

The python version tested is 3.6. Will look into the missing import.

Can you run pip freeze to see if celery is installed?

In pip freeze I have celery==4.1.0. However, it might be the Python version issue because I used Python 2.x. It would be nice to add that to the docs (to state that it was written/tested in Python 3) because the installation for Python 2 works fine.


fix: change import of @yamada-ui/lucide in disclosure of Storybook to *Icon

Closes #3387
Description
Changes import of @yamada-ui/lucide in disclosure of Storybook to *Icon.
Current behavior (updates)

New behavior

Is this a breaking change (Yes/No):
No
Additional Information

Got it! I removed the file


Select dialog overflow issue

If you localize your app to a language with long words for the phrases COPY, PASTE, SELECT ALL and others from the clipboard controls, the text will overflow when selecting anything that causes the controls to appear.
That's how the controls appear on Android in ua_UA/ru_RU:
DEVISES:
Samsung Galaxy S10+

MEIZU M6T

You're right, this is a major problem that we need to fix.
I'm going to close this as a duplicate of https://github.com/flutter/flutter/issues/35826 so we can focus the discussion over there.  Please give that issue a 👍!


Add apis-list/apis-list

Add https://github.com/apis-list/apis-list
It is community maintained, human and machine readable list of Public APIs.

Looks good, I'll just have to resort the list which is not an issue. Thanks Yevhen!

Looks good, I'll just have to resort the list which is not an issue. Thanks Yevhen!


Adding zoom to the editing canvas

It should be possible to zoom in, zoom out and pan up/down and left/right in the editing canvas. This will include adding scroll bars to the right and bottom of the canvas.
Specification:
Four buttons should be added to the bar above the canvas.
Zoom-in: https://material.io/resources/icons/?icon=zoom_in&style=outline
Zoom-to-fit: https://material.io/resources/icons/?icon=zoom_out_map&style=outline
Zoom-to-standard: https://material.io/resources/icons/?icon=crop_original&style=outline
Zoom-out: https://material.io/resources/icons/?icon=zoom_out&style=outline
Keyboard shortcuts
Ctrl++ Zoom-in
Ctrl+- Zoom-out
Ctrl+= Zoom-to-fit
Ctrl+1 Zoom-to-standard

Ctrl+0 Zoom-to-standard


License is being installed to /usr/LICENSE

python setup.py build
python setup.py install --optimize=1 --skip-build

This generates a LICENSE file in /usr which is super weird.

Haha, yes that does sound wierd. Must be some pip behavior.
Does it still happen if you remove this line?

Nop, as we expected.
usr
 ├─LICENSE
 └─lib
    └─python3.7
       └─site-packages
          ├─Qt.py
          ├─Qt.py-1.2.0b3-py3.7.egg-info
          │  ├─PKG-INFO
          │  ├─SOURCES.txt
          │  ├─dependency_links.txt
          │  ├─not-zip-safe
          │  └─top_level.txt
          └─__pycache__
             ├─Qt.cpython-37.opt-1.pyc
             └─Qt.cpython-37.pyc

I'm having trouble reproducing this under Ubuntu 16.
I do however spot a message with regards to he License file.
warning: install_data: setup script did not provide a directory for 'LICENSE' -- installing right in 'build/bdist.linux-x86_64/egg'

Here's the full stack.
/Qt.py# python setup.py install --optimize=1 --skip-build
/usr/lib/python2.7/dist-packages/setuptools/dist.py:397: UserWarning: Normalizing '1.2.0.b3' to '1.2.0b3'
  normalized_version,
running install
running bdist_egg
running egg_info
writing Qt.py.egg-info/PKG-INFO
writing top-level names to Qt.py.egg-info/top_level.txt
writing dependency_links to Qt.py.egg-info/dependency_links.txt
reading manifest file 'Qt.py.egg-info/SOURCES.txt'
writing manifest file 'Qt.py.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
copying build/lib.linux-x86_64-2.7/Qt.py -> build/bdist.linux-x86_64/egg
byte-compiling build/bdist.linux-x86_64/egg/Qt.py to Qt.pyc
writing byte-compilation script '/tmp/tmpoJvkdf.py'
/usr/bin/python -O /tmp/tmpoJvkdf.py
removing /tmp/tmpoJvkdf.py
installing package data to build/bdist.linux-x86_64/egg
running install_data
warning: install_data: setup script did not provide a directory for 'LICENSE' -- installing right in 'build/bdist.linux-x86_64/egg'

copying LICENSE -> build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying Qt.py.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying Qt.py.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying Qt.py.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying Qt.py.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying Qt.py.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
creating 'dist/Qt.py-1.2.0b3-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing Qt.py-1.2.0b3-py2.7.egg
removing '/usr/local/lib/python2.7/dist-packages/Qt.py-1.2.0b3-py2.7.egg' (and everything under it)
creating /usr/local/lib/python2.7/dist-packages/Qt.py-1.2.0b3-py2.7.egg
Extracting Qt.py-1.2.0b3-py2.7.egg to /usr/local/lib/python2.7/dist-packages
Qt.py 1.2.0b3 is already the active version in easy-install.pth

Installed /usr/local/lib/python2.7/dist-packages/Qt.py-1.2.0b3-py2.7.egg
Processing dependencies for Qt.py==1.2.0b3
Finished processing dependencies for Qt.py==1.2.0b3
root@af4ce03431b8:/Qt.py# ls /usr/
bin  games  include  lib  local  sbin  share  src
root@af4ce03431b8:/Qt.py#

Here my build process: https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/python-qt.py
As you see I have to manually remove the LICENSE file.

There's actually no need for that file to even exist. The licence has since been embedded into the Python module and remains around mostly to let GitHub fill in that nice little field in its GUI.

I'd be happy to either remove this file or remove any reference to it from the setup.py. Did you say you tried that, and it still happened? That would be sparta. I mean madness.
Alternatively, if it helps, the only relevant file for any distribution is that Qt.py file itself; so if your build-system permits it, you could merely download that file and skip any build/install step provided by setuptools.

Just FYI, including LICENSE in data_files is likely the issue, or at the very least an issue; data_files is a a long deprecated, discouraged and unsafe way of distributing files outside the package tree that will eventually be fully removed, whereas the license_files, license_file and MANIFEST.in (in that order) are all much more appropriate solutions, never mind that reasonably modern packaging tools (thanks to a feature I helped add) will include LICENSE as a license_file automatically. So I suggest simply removing it, as there's no need for it anymore and it can only cause problems.

Done, thanks.


ValueError: filedescriptor out of range in select()

My hue instance runs for about two days, the following errors will appear.
[25/Sep/2020 00:10:58 -0700] connection   ERROR    Unhandled exception in connection loop
Traceback (most recent call last):
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/protocol/connection.py", line 516, in _connect_attempt
read_timeout, connect_timeout = self._connect(host, port)
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/protocol/connection.py", line 592, in _connect
connect_result, zxid = self._invoke(client._session_timeout, connect)
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/protocol/connection.py", line 241, in _invoke
self._submit(request, timeout, xid)
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/protocol/connection.py", line 286, in _submit
self._write(int_struct.pack(len(b)) + b, timeout)
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/protocol/connection.py", line 294, in _write
s = self.handler.select([], [self._socket], [], timeout)[1]
File "/opt/hue/build/env/lib/python2.7/site-packages/kazoo-2.0-py2.7.egg/kazoo/handlers/threading.py", line 250, in select
return select.select(*args, **kwargs)
ValueError: filedescriptor out of range in select()
Environment:

hue version: open source 4.8.0
OS: CentoOS 7.3
Python2.7.5
hive2.1.1

It seems that upgrade kazoo can fix this issue. But how? Who can help me?
The related issue is https://github.com/python-zk/kazoo/pull/448

You could delete https://github.com/cloudera/hue/tree/master/desktop/core/ext-py/kazoo-2.0 and replace it by https://pypi.org/project/kazoo/#files
And also change 2.7.0 to 2.8.0 https://github.com/cloudera/hue/blob/master/desktop/core/requirements.txt#L32
Then make clean, make apps or fresh clone/git clean.
Feel free to send a pull request too!

@romainr Thanks a lot! I will.


add section on saving data/plots/maps

This PR implements #14, which was inspired by https://github.com/davidcarslaw/openair/issues/374.
In short, it adds a brief section at the very end of the "openair package" chapter that details saving data, plots, and HTML widgets (maps).
This is a useful reference as it is a core R skill needed for "minimal R" openair users.

Thanks Jack


Code Commenting

@JBlond
I've forked the repo and did some cleanup/optimization and much code commenting.
Still trying to understand the scripts completely, I've refactored a lot of variables and made a lot of code commenting. Lot's of things are still unclear though.
If you're interested, I can add you as a contributor of my fork so we can both make effort to refactor/comment/optimize the code. This way we don't have to litter your repo, trying to understand the code.

@DigiLive I could add you to my repo ;)

That's also fine for me. 😉
My intention was just to prevent littering your repo with many commits. That's why I didn't do a PR yet.
But I'm happy to contribute to yours directly.

@DigiLive I added you to the repo. Feel free to contribute.


rtd.js is blocked by uBlock

Sorry, I wasn't watching this project anymore. I'm rewriting this to a JSON/SPA template. The current styling is too much of a hassle to maintain. I will rename this to a more sensible name while I'm at it.


on html

Type: Bug
while i am writeing html code. The tags are not applying .
html code is not comng to apply please  clear this issue
VS Code version: Code 1.88.1 (e170252f762678dec6ca2cc69aba1570769a5d39, 2024-04-10T17:41:02.734Z)
OS version: Windows_NT x64 10.0.22631
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.79GB (9.74GB free)

Process Argv
C:\Users\bctej\OneDrive\Desktop\javascript\js.html --crash-reporter-id 880add52-62c9-48b4-9344-5f8d5fa9076f

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

templ
a-h
0.0.24

ng-template
Ang
17.3.1

armview
ben
0.4.6

django-html
bib
1.3.0

php-built-in-server
dav
0.0.3

l13-built-in-extensions
L13
0.13.1

vscode-edge-devtools
ms-
2.1.5

debugpy
ms-
2024.4.0

python
ms-
2024.4.1

vscode-pylance
ms-
2024.4.1

powershell
ms-
2024.2.1

sublime-keybindings
ms-
4.1.10

LiveServer
rit
5.7.9

jinja
who
0.0.8

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
ccp2r3:30993541
dsvsc020:30976470
pythonait:31006305
666c4381:30973075
gee8j676:31009558
showvideot:31016892
chatpanelc:31018788
dsvsc021:30996838
945dj816:31013170

What do you mean by 'the tags are not applying'?
Please give step by step instructions how to reproduce the issue.
Here is what I tried. Please provide your steps, describe what you see and what you expect. Screenshots also help.

open an editor on the file test.html with the following content

<html>
</html>

after <html> type `<`` and press Ctrl + space
you see all tags, select one e.g. address. Verify it is applied

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


perf: memoize the extensions in code editor to reduce expensive calculations

Prerequisites checklist

[x] I have read the contributing guidelines.

What is the purpose of this pull request?

Memoize the extensions in code editor to reduce expensive calculations on every re-render

What changes did you make? (Give an overview)
Used useMemo to wrap the extensions array to keep the reference.
Is there anything you'd like reviewers to focus on?

Ref: https://www.npmjs.com/package/@uiw/react-codemirror?activeTab=readme

Seems to work for me? 🤔 @kecrily

After some investigation I think this is a problem with the preview component of netlify

Open the preview page, I found an error message at the bottom

Open the console, I found that the error report came from under netlify.com.

I have also tested locally and everything works fine locally.

@harish-sethuraman Can you verify if my research is correct?

These errors do not look like its coming from our app? Its coming from netlify's deploy preview menu in the bottom I guess?

These errors do not look like its coming from our app? Its coming from netlify's deploy preview menu in the bottom I guess?

Yes, that's what I thought. Just wanted to make sure.


Update notice when new version is live

Hi!
I was looking into the option to notify users when a new version is available, and add a little bit of code to do just that. It uses the GitHub API to retrieve data about releases, and compares the tag_name to the version of the running instance (via process.env.VERSION).
When a new version is available, a banner is displayed on top of pages when logged in. As I'm writing this I notice a Toast-component as well, but I don't know what's the right trade-off between the importance of updating, user-friendliness and visibility.
At the moment, although it's wrapped in useMemo, it will pretty much fetch the GitHub API on every render, which of course is a tad overkill. Storing the last time it checked for a new version, and the latest version at that moment in Local- or Sessionstorage to check once every session or day, would probably be a better option. I have never worked with Redux however, so I didn't implement it as of now.
Consider this PR more of a proof of concept as of now! Would love to hear some thoughts.
Edit: this uses v3 of the GitHub API, which is still REST. I assume this will be supported for some time, although they seem to be actively pushing to using the GraphQL version. GitHub states you should explicitely state the version in an Accept header, this is not implemented here, but it still works.

I'll pull this in and make some changes later. Will probably use redux or localStorage so we don't keep checking. This should also be configurable in Settings, maybe opt-out by default. Also this should only display to the admin since other users won't have any control over the installation.


Fill $model->_related property on eager load

Hi, I was taking a look at
https://github.com/stibiumz/phalcon.eager-loading/blob/master/src/EagerLoading/EagerLoad.php#L157
the property _related where the relationships are stored is not filled.
This is causing me a problem. When I want to check if a relationship is already loaded, (by any way) if not, then I check caché or fetch db.
On pseudocode:
$instances = Loader::from($instances, ['relationshipAlias']);

foreach($instances as $instance) {
    print_r($instance->getRelationshipAlias());
}

// on the model for $instance I have
public function getRelationshipAlias() {
     if(!isset($this->_related['relationshipAlias']) || $this->_related['relationshipAlias'] === null) {
           // get from cache or fetch from db using getRelated('relationshipAlias');
     }
}

The problem here is that on that case, the eagerloaded relationships are wasted. Of course, if I try to check if the relationship is loaded using the property relationshipAlias, in case that the relationship is not loaded it will make a lazy loading "automatically", runining my chance to insert the caché.

The problem here is that _relatedis a protected property :(


support for SSL?

Hi, Are there any plans to support an SSL encrypted connection to Redis?
Thanks.

There's quite an old pull request which I've done to make hiredis use SSL: https://github.com/redis/hiredis/pull/570

Hi. It would be great to see the SSL support merged into master. I've had some success testing the SSL updates rebased onto 0.14.0, talking to redis via stunnel. Happy to try and assist if there's anything I can do to help take this forward.

This is currently under consideration in #570

Merged

Hi @mnunberg
Will there be another minor release 0.15 which has SSL support ?
Thanks,
Pradeep


fix(links): add links loading support from NAVBAR_DATA.json with all attributes support

Fixes non working links in help section of navbar
Describe the changes you have made in this PR -
binded the attributes from NAVBAR_DATA.json to the links made by dropdown.vue component
Screenshots of the changes (If any) -
N/A can be easily checked through the netlify preview build linked below
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

closed by #170


Support arbitrary regions

Grapl hardcodes the us-east-1 region in a lot of places.
The cdk script needs to check for the aws environment, or allow an override in the .env file, and Grapl services need to dynamically determine which region to use based on this.

In the short term, setting up grapl with a profile that's set up for us-east-1 is the way to get around this issue.


Support base64-encoded data

This change accompanies https://github.com/apple/swift-openapi-runtime/pull/55 and relies on it for the OpenAPIRuntime.Base64EncodedData type.
Motivation
OpenAPI supports base64-encoded data but to this point Swift OpenAPI Generator has not (https://github.com/apple/swift-openapi-generator/issues/11).
Modifications
A data type specified as type: string, format: byte will now result in a generated type which is Codable and backed by a OpenAPIRuntime.Base64EncodedData type which knows how to encode and decode base64 data.
Result
Users will be able to specify request/response payloads as base64-encoded data which will be encoded and decoded transparently
Test Plan
Unit tested locally.

@swift-server-bot add to allowlist

@rnro As a last thing, can you add a base64 property to an object of your choice in the file-based reference tests? I'm a little paranoid that this PR is passing even though we haven't released the update runtime yet, which means we're not testing that it all builds and works together. Add a property, and make sure PetstoreConsumerTests are updated to also populate and verify the value both on client and server side. Otherwise lgtm.

Thanks for the review, I've added an endpoint to upload audio of your pet in base64-encoded binary format. I'm not sure if that's the best API design for an actual pet app but I think it's plausible to get the new code in there.

Also, you can now update to 0.3.2 of the runtime library in Package.swift of swift-openapi-generator, all that should hopefully make the CI green on this PR.


Issue installing plugin on Kibana 7.1.1

Hi, I've just installed the plugin with Kibana 7.1.1 and Elasticsearch 7.1.0 and get the following issue:

The only thing I changed was the path in the uiExports field to "enhanced-table/public/enhanced-table-vis"

Well, why did you change "uiExports" field?
Normally, you don't need to change anything to install the plugin.
Did you try to install the plugin without changing anything?

I tried it again without changing anything and ran kibana-install, and the same issue occurred. Here is my file structure if it helps at all.

Thanks for the details, I will try to reproduce the issue.

Hi,
I just tried to reproduce the issue, with exactly the same Kibana version and plugin version (enhanced-table-1.3.0_7.1.1.zip), and it works fine for me, without changing anything in zip file available on github.
To be sure, can you delete "optimize" and "plugins" folder, and then re-install official zip file using "kibana-plugin install file:///"?

By the way, normally, your Elasticsearch version should be equals to or greater than Kibana version.

Hi,
Thanks for your help! Deleting the optimize folder and running again
worked.
On Tue, Jun 25, 2019 at 11:18 AM Fabien Baligand<EMAIL_ADDRESS>wrote:

Hi,
I just tried to reproduce the issue, with exactly the same Kibana version
and plugin version (enhanced-table-1.3.0_7.1.1.zip), and it works fine for
me, without changing anything in zip file available on github.
To be sure, can you delete "optimize" and "plugins" folder, and then
re-install official zip file using "kibana-plugin install file:///"?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fbaligand/kibana-enhanced-table/issues/46?email_source=notifications&email_token=ACSKKM4CC32LP4ZWC3G3CCLP4IZMDA5CNFSM4H3CMYMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYQTFLQ#issuecomment-505492142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACSKKM4AO6ECRVGVYCBSBKLP4IZMDANCNFSM4H3CMYMA
.

Nice to see it solves your problem!
Hope you will enjoy the plugin!


Add support for django-autocomplete-light

Hi there,
I hope you're doing well. this project is really great, I wanted to suggest adding support for django-autocomplete-light. It would be a fantastic addition to an already amazing project.
Thanks in advance!

To be honest I don't have an experience with this application. Can you tell me how exactly it is used in the admin? Because Django admin has own implementation of autocomplete.


Raise full HTTPError if something goes wrong in HTTP instead of wrapping it with an EnvironmentError that hides some info.

Use requests-mock package for testing.

This change is

Review status: :shipit: complete! undefined

Comments from Reviewable


what do the params pixel_means and pixel_stds mean?

and why operating the image tensor as following, in RetinaFace.detect():
for i in range(3):
        im_tensor[0, i, :, :] = (img[:, :, 2 - i] / pixel_scale - pixel_means[2 - i]) / pixel_stds[
            2 - i]
net_out = self.model.predict(im_tensor.transpose(0, 2, 3, 1))

I understand why this is unclear.
In reality this step does 3 things :

switch from BGR to RGB (i -> 2-i)
add a dimension to fit he input shape of the neural network
subtract scale and divide by standard deviation of the training dataset. In our case, scale is 0 and std is 1, so this step actually makes no difference. I left it there as a habit

I will try to divide this step into 3 distinct steps so it is clearer in the coming days. Or feel free to make a PR for this :)


Fix symmetric contraction weight loading test

This fixes the test for SymmetricContraction with weights from pytorch version, the issue was parameter naming (and a shape squeeze which might be relevant)

Thanks!


Topic/dogstatsd support

Thanks for updating to support PHP8/Symfony 6 recently. :)
This PR relates to: https://github.com/BedrockStreaming/Statsd/pull/30
Needs to be merged after the above is merged + released and assumes the above PR will be released as 1.4.0.

the CI wasn't configured to run on PR from forks
now that it's fixed, could you fix the PR build, please?

The CI process will fail until https://github.com/BedrockStreaming/Statsd/pull/30 is merged and released due to composer not being able to resolve m6web/statsd ^1.4 (this PR assumes the m6web/statsd changes will be released as 1.4).
I've run the CI steps against my forked repo in an alt branch which points to my forked m6web/statsd library:

https://github.com/raing3/StatsdBundle/compare/topic/dogstatsd_support...topic/dogstatsd_support_alt
https://github.com/raing3/StatsdBundle/actions/runs/1924658846

Will fix up any issues which do appear once the other PR has been completed but I think there should be none/minimal.

Thanks, looks like CI is passing now. Let me know if anything else is needed from me to get this PR merged and released as well.

released in v4.2.0

Thanks very much. :)