Allow Secrets to be used as Access Tokens

Feature Description
Hi! The specific use case I'm bumping into is that I frequently mirror private GitHub repos to my Gitea instance. I have a single read-only access token for use with Gitea. So I often go through the flow:

New Migration
GitHub Migration
Private repo address in the URL field, then I have to dig up the same Gitea access token each time

In trying to speed this up, I saved the access token as a secret in Gitea. If I'm understanding correctly, this should mean it's usable in Actions. I'd love if this would also work in the Access Token field (and potentially, more widely?). I.e., it would be great if I could just fill in
Access Token: ${{ACCESS_TOKEN_GITEA_GITHUB}}

I've confirmed that this does not currently work at the moment (nor do ${TOKEN}, $TOKEN, or TOKEN). I have no idea if anything like this would currently work on GitHub, as I never use GitHub for this purpose.
I've done my best to look for existing/closed issues on this, and failed to find anything. It may be that I'm misunderstanding something, or that the authors aren't keen for the scope of secrets to be expanded to this; please let me know if there's a better way I should be doing this!
Thanks :)
Screenshots
No response

Have you tried ${{ secrets.ACCESS_TOKEN_GITEA_GITHUB }}? See https://docs.github.com/en/actions/learn-github-actions/contexts#secrets-context

I hadn't (thank you), but have now; can confirm that ${{ secrets.ACCESS_TOKEN_GITEA_GITHUB }} is not working either.

So I have no yaml file for this; I suppose what I'm requesting is the ability to use these secrets outside of that context. E.g., if I have a secrets page that looks like this:

I would ideally love to be able to use this secret as so:

As I say, if there's a better/more obvious approach that already exists, which I should be using, I'm all ears!

Sorry I misunderstood.
Currently, the secrets are used for Gitea Actions only. So what you need isn't supported yet.

No problem at all, I appreciate you taking a look!

This would be really nice to have. I just finished updating 73 mirror repositories one by one, going to settings of each, pasting the same token over and over, and it wasn't fun at all. And unless Gitea comes with better way how to deal with this, I'll have to do this every year, because Gitlab, which is the source, limits token validity to only one year. :(

Hi, are there any plans to do this?


Update validation.py

found a typo in the comments

Codecov Report

Merging #94 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #94   +/-   ##
=======================================
  Coverage   80.43%   80.43%
=======================================
  Files          12       12
  Lines        2024     2024
=======================================
  Hits         1628     1628
  Misses        396      396

Impacted Files
Coverage Δ

pyArango/validation.py
55.55% <ø> (ø)
:arrow_up:

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 f314570...7df5328. Read the comment docs.

Thanks!


New game screen setting discrepancy

A) Change Artwork: # of Miners should be # of Drones
or
B) Change Code: # of Miners setting should not effect drones.
Imported from trac ticket #213,  created by Imago on 08-07-2010 at 03:18, last modified: 01-08-2011 at 22:46

Tested the changes today, there were no noticeable errors.
Trac comment by pkk on 08-13-2010 at 17:04


[BUG] Some Weapons Missing Fire Modes

Description of the bug:
Some weapons which should have fire modes don't
Video of the bug:
N/A
Steps to recreate the bug:
N/A

Resolved In Release v0.2.2-beta


Core: Allow 'false' as value when overriding rules

This PR enables ability to deny or override rules via declarative HTML attributes (as it done for rules defined in .validate method).

note sure this is something which makes sense to be configurable using markup.
could you describe your use-case?

@staabm Sure! There is a popular lib for Ruby on Rails: https://github.com/plataformatec/simple_form , which creates selects (only for dates) with predefined class="date" attribute. So select will look like <select class="date" />, nothing criminal for me. By some unknown reason it breaks validation of this plugin for selects in Firefox on Windows (Firefox on Mac works as expected) and we have such selects displayed as "invalid" even if valid option was selected by user. So easy fix is to disable data validation for this inputs in way like `.

Could you build a small jsfiddle which reproduces the issue?

Programmatically based solution should always override declarative approaches, because those are considered more specific and dynamic. Therefore I will decline this feature.
Please feel free to discuss further and describe your case. I am willing to re-open the issue in case we have good reasons to do so.


fix: Better test for group ID in filename

This fixes an issue where filenames containing a period that aren't a group ID, such as some-jar.12.jar, would be mistakenly be reported as having the name "12" by syft, instead of the name "some-jar.12".
Fixes #2563.

Oh does this also fix https://github.com/anchore/syft/issues/2385?

@westonsteimel it looks like this fixes the artifact ID but not the group ID for #2385:
❯ go run cmd/syft/main.go willtmp/kafka_2.13-3.2.2.jar -o json | jq '.artifacts[0].purl'
<EMAIL_ADDRESS>
I think it's still worth getting in, and we can try to figure out the group ID issue in another PR. I'll push a unit test that prevents regression on that particular kafka jar's artifact ID.

Yeah, I didn't bother updating the groupid mapping for those since the name was too broken before.  Thanks for figuring the name bit out!


Build(deps-dev): Bump @types/react from 17.0.36 to 17.0.37 (#2008)

Pull request opened by the merge tool on behalf of #2008

Merged in 2bce97898e255f4900cfdff9ab7d77899977281c


update logging dependency

stack overflow caused by some non-strict data structure.
this should fix it.
thanks to @mrBliss for debugging.

bors r+


[Cortana Accessibility] Allow borders on containers

Platform
What platform is your issue or question related to? (Delete other platforms).

UWP

Author or host
Host
Version of SDK
1.2.0-beta1-201905.29017
Issue
For high contrast requirements, we have to be able to draw a colored border around clickable items.  We originally had this around the entire card as this was the only thing we could draw a border around (as this is all one “card” element), but have been told this is not correct and we should only be highlighting the border around the actual clickable content.  While we’ve tried to see if there is a way to break down the visual tree to allow this, it doesn’t appear there is any clean way for us to hack this to make it work as required.
Here’s the json for reference:
{
  "type": "AdaptiveCard",
  "version": "1.0",
  "body": [
    {
      "type": "TextBlock",
      "size": "small",
      "weight": "lighter",
      "isSubtle": true,
      "text": "Alarm",
      "spacing": "padding"
    },
    {
      "type": "Container",
      "items": [
        {
          "type": "TextBlock",
          "size": "extraLarge",
          "text": "3:52 PM"
        },
        {
          "type": "TextBlock",
          "size": "small",
          "weight": "lighter",
          "isSubtle": true,
          "text": "Only once",
          "spacing": "none",
          "separation": "none"
        }
      ],
      "selectAction": {
        "type": "Action.OpenUrl",
        "url": "ms-clock://alarms"
      }
    }
  ]
}

Ask:
We believe we could make this work if we were able to draw borders around containers – which is something it seems has been asked before (#2033 and #1890), but does not appear to ever been prioritized.
For now we will have to leave this accessibility issue open as we have no way to fix.  Hoping you can help prioritize this item for the next release (is there an ETA on this, btw?) so we can provide more information to that team on when we’ll be able to get  fix in place.

Assigning to you @paulcam206 to investigate. Thanks

Have not heard back from the Cortana team on this one. Removing from 1.2.3 investigations.

@matthidinger / @paulcam206 - this is now not much of a priority for Cortana at this point. More interested in #3535

This is not currently on our roadmap.

I'm super confused how "This is not currently on our roadmap" equates to "Closed as completed."


Missng parameter 'client_id'

I'm running the OAuth2 Express In-Memory Example. I'm able to request an access token via the /token endpoint:
curl -d "grant_type=password&username=jdoe&password=foobarbaz"  -u "doeclient:foobarbaz" "http://localhost:3000/token"

And I get an access token back:
{
  "access_token":"36f97e75787ca29de36406b6bacb2306240ead365736f492f8a39a4267505f9d",
  "token_type":"Bearer",
  "expires_in":3599,
  "refresh_token":"5ed54f7c41306f2bdaa375a5f7a58fd4576ab207016ddbf0254386994d6738aa"
}

But when I try to access the /secret endpoint:
curl -H 'Authorization: Bearer 36f97e75787ca29de36406b6bacb2306240ead365736f492f8a39a4267505f9d' http://localhost:3000/secret

{
  "error": "invalid_grant",
  "error_description": "Invalid grant: user credentials are invalid"
}

Am I not making the request correctly?

Hi @PopeFelix thank you for reporting this. I actually just converted the super old examples to ES6 but I found this example does not correctly implement the password grant flow. I fixed this and opened a PR #8 would you mind doing a short review? You can checkout the branch fix/database-memory-example to test this.

Yeah, I'll do a PR tonight

#8 will fix this issue


file adaptor w/ new interface

TODO:

[ ] Tests? The pipeline test does use the file adaptor, but could use unit tests as well

fixes #252

Changes Unknown when pulling d49f1322e0205ba8bd8a4a69e72ddb9c8cad26f5 on file-adaptor into ** on master**.

Changes Unknown when pulling f036ddbc114045c11fdb8e05dc624d528b53cf31 on file-adaptor into ** on master**.

some test coverage would be good but the primary purpose of the file adaptor has always been to easily test things so they are not super critical.

Coverage decreased (-0.04%) to 59.72% when pulling 67dc434fd7790f91ee50d1c4917c26979c846bc8 on file-adaptor into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

Coverage decreased (-0.04%) to 59.72% when pulling 67dc434fd7790f91ee50d1c4917c26979c846bc8 on file-adaptor into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

Coverage decreased (-0.08%) to 59.681% when pulling cc21aa396f39c733b3e91cab499a128f0086fcc7 on file-adaptor into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

Coverage decreased (-0.08%) to 59.681% when pulling cc21aa396f39c733b3e91cab499a128f0086fcc7 on file-adaptor into 0f7fd1175827fe2e72bd8dd34c79f9c1b0bbbf23 on master.

Coverage increased (+0.2%) to 59.489% when pulling 22631d8e53325c1e3c8098a9149a37232959df7b on file-adaptor into fad12d533bafb2a4103569bdf77ce06325863e1d on master.


Update docs and scheme

Looks good to me. Only remark in the file docs/_static/screenshots/option_language.png it seems that the chinese language is not working anymore. Possibly not related to these changes, but a possible bug

@acrobat Thanks! Fixed.

Hi @vsn4ik We are this date picker in one of the application. now we need to change the date prev and date next icons from

TO

something like this, can you please let me know whether is it possible or not


Let's collaborate

[apologies for early send, accidentally hit enter]
Hey there! Turns out we think on extremely similar wavelengths - I did the exact same thing as you, for the exact same reasons (libraryification), and through the use of similar abstractions: https://github.com/philpax/ggllama
Couple of differences I spotted on my quick perusal:

My version builds on both Windows and Linux, but fails to infer correctly past the first round. Windows performance is also pretty crappy because ggml doesn't support multithreading on Windows.
I use PhantomData with the Tensors to prevent them outliving the Context they're spawned from.
I vendored llama.cpp in so that I could track it more directly and use its ggml.c/h, and to make it obvious which version I was porting.

Given yours actually works, I think that it's more promising :p
What are your immediate plans, and what do you want people to help you out with? My plan was to get it working, then librarify it, make a standalone Discord bot with it as a showcase, and then investigate using a Rust-native solution for the tensor manipulation (burn, ndarray, arrayfire, etc) to free it from the ggml dependency.

Hi! Thanks for your post and for all the help so far :smile:

Turns out we think on extremely similar wavelengths

Glad to hear I'm not the only one who saw the potential in this project! I think having the potential to build something this huge and making it a CLI app is not aiming high enough, heh.

Windows performance is also pretty crappy because ggml doesn't support multithreading on Windows.

To be fair, I haven't even tested this on Windows. Maybe it builds just fine. But I didn't know what flags to set to compile with AVX and inference times without AVX are pretty bad (if you're telling me there's no multithreading on top of that, it's probably gonna be unusably slow anyway, unfortunately). I don't have a Windows machine to test this, so I didn't want to promise support for untested systems :sweat_smile:

I use PhantomData with the Tensors to prevent them outliving the Context they're spawned from.

I thought about this! Even started with this design. But didn't want to force all the code to use a 'ctx lifetime annotation, since those typically become infectious and are a bit unergonomic. So I did the Arc / Weak thing instead, since the performance of cloning or operating with tensor pointers doesn't really matter. Still, seeing how it turned out in the end, I think the lifetime annotation wouldn't have been so bad :thinking:.
That said, the "bindings" in ggml.rs do not aim to be a safe abstraction, at least not in their current state! We would need to put a bit more thought into it, because the ownership model is a bit weird there. A tensor is tied to a context, but you can then use tensors from one context to operate with tensors from another context, which makes a graph computation on one context access data from other contexts. So not even lifetime annotations would help here.

What are your immediate plans, and what do you want people to help you out with?

Very good question! So far I was most concerned with whether I could do it :rofl:  But now that the library exists, I'm thinking it would be pretty good to start improving this. A few things off the top of my head:

Library-fication: This needs to happen ASAP. Split the current llama-rs crate into two crates, llama-rs would be a library, and llama-rs-cli would be the simple example CLI app we have now. I don't have much interest in making the CLI experience better (porting things like the interactive mode or terminal colors from llama.cpp), but they're welcome in case someone wants to contribute.

Add a server mode, perhaps as an addition to llama-rs-cli that would allow spawning a long-running process that can serve multiple queries. The current usage model doesn't make any sense. You spend a lot of time loading the models from disk (especially if you're using the larger ones) only to throw all that away after a single prompt generation.

Prompt caching: Another thing that doesn't make sense with the current model is when you have a huge prompt, because you need to feed it through the network every time you want to do inference with that "pre-prompt" + some user input. This is described in an issue in llama.cpp (currently unimplemented). If I understood correctly, the gist of it is that we need to dump the contents of the memory_k and memory_v tensors to disk, and load them back, and that would be the same as feeding the model the same prompt again. Choosing a fast compression algorithm would be a good way to mitigate the cost of storing massive tensors on disk.

Another thing I have on my radar is this famous "GPTQ 4bit" quantization. It is well known (I mean, you just need to run a trivial example) that the 4-bit quantization in llama.cpp affects the results of the network. If this GPT4 quantization is capable of keeping the same quality as the f16 version as some sources claim, this would be huge. But I would need to investigate more to be sure.

investigate using a Rust-native solution for the tensor manipulation (burn, ndarray, arrayfire, etc) to free it from the ggml dependency

Yup, also considered that, I'd love to do this if possible :)  Not sure how long it would take, but none of the tensor operations I ported seem too complicated. The code should be pretty straightforward to port to a different library, and I'm sure some of the Rust options achieve a more ergonomic (and safe!) API. We just have to keep an eye on performance, but having an already working ggml version means we can just benchmark.
If that change also helps us support GPU inference, that'd be pretty cool. But I don't want to add GPU support if that means people having to mess with CUDA or rocm drivers and report all sorts of issues. Unless it's something portable that works out of the box for people, I'm not interested.
I'm not sure how crazy it would be to build a tensor library on top of wgpu compute shaders. Just throwing that out there for anyone who feels crazy and/or adventurous enough :thinking:  But that would eventually mean tensors on wasm, which is pretty darn cool I guess?
Anyway, I'm happy to have someone else on board :smile:  If there's anything I mentioned above you'd like to take the lead on, please say so! I'm not going to be making any big changes to the code in a few days.

Just something to follow w.r.t to GPTQ quantization :eyes:  https://github.com/ggerganov/llama.cpp/issues/9
Also, by linking this, I guess we just made the cpp side aware of our existence... Hi? :wave: :sweat_smile:

Also count me in for any future work!  I've been obsessed with llama for the past few weeks and getting a solid Rust implementation of a modern machine learning model like this is really impressive.  I might try tackling breaking the app into a library in the next few days (unless someone else beats me to it :smile:)

To be fair, I haven't even tested this on Windows. Maybe it builds just fine. But I didn't know what flags to set to compile with AVX and inference times without AVX are pretty bad (if you're telling me there's no multithreading on top of that, it's probably gonna be unusably slow anyway, unfortunately). I don't have a Windows machine to test this, so I didn't want to promise support for untested systems 😅

I've been testing on Windows with my patches applied and it seems to work fine. It's probably not as fast as it could be, but it's plenty fast enough!

I thought about this! Even started with this design. But didn't want to force all the code to use a 'ctx lifetime annotation, since those typically become infectious and are a bit unergonomic. So I did the Arc / Weak thing instead, since the performance of cloning or operating with tensor pointers doesn't really matter. Still, seeing how it turned out in the end, I think the lifetime annotation wouldn't have been so bad 🤔.

Yeah, I actually went back and forth on this. I started without any kind of checking, promptly got owned by accessing freed memory, fixed that, and then bolted on the PhantomData afterwards. Turns out it's not too bad, as you've noticed, because the only place where the actual borrows come up is LlamaModel with reference to the context that's created during the loading process. That's a little annoying, but I worked around it by splitting the load into two so that the model could borrow from the separately-stored context:
https://github.com/philpax/ggllama/blob/7b69eb984dc32f8bcd199eb75484c33f24f9ec1f/src/llama.rs#L157-L169
Ideally, we'd still maintain the same LlamaModel interface to the outside world - but it might get annoyingly self-referential. Will play around with it sometime!

That said, the "bindings" in ggml.rs do not aim to be a safe abstraction, at least not in their current state! We would need to put a bit more thought into it, because the ownership model is a bit weird there. A tensor is tied to a context, but you can then use tensors from one context to operate with tensors from another context, which makes a graph computation on one context access data from other contexts. So not even lifetime annotations would help here.

Huh, you're right - hadn't even thought about that. That's... pretty gnarly. I wonder if it's possible for the operands in a binary operation A + B = C to each have their own lifetimes, such that 'a A + 'b = 'c C where 'a and 'b outlive ''c? I must admit I've never really delved into that kind of lifetime trickery!

Library-fication: This needs to happen ASAP. Split the current llama-rs crate into two crates, llama-rs would be a library, and llama-rs-cli would be the simple example CLI app we have now. I don't have much interest in making the CLI experience better (porting things like the interactive mode or terminal colors from llama.cpp), but they're welcome in case someone wants to contribute.

Well... I'd actually started on this before you replied 😂 Here's the PR. I wrote a Discord bot to prove that it works, too. Hell of a thing to run a binary and be able to run a LLM with friends with an evening's work!

Add a server mode, perhaps as an addition to llama-rs-cli that would allow spawning a long-running process that can serve multiple queries. The current usage model doesn't make any sense. You spend a lot of time loading the models from disk (especially if you're using the larger ones) only to throw all that away after a single prompt generation.

Yeah, I've also thought about this. Seems easy enough to do; I'd do it as a separate application just to keep the concerns separate, and to offer up a simple "API server" that anyone can run. My closest point of comparison is the API for the Automatic1111 Stable Diffusion web UI - it's not the best API, but it does prove that all you need to do is offer up a HTTP interface and They Will Come:tm:.

Prompt caching: Another thing that doesn't make sense with the current model is when you have a huge prompt, because you need to feed it through the network every time you want to do inference with that "pre-prompt" + some user input. This is described in an issue in llama.cpp (currently unimplemented). If I understood correctly, the gist of it is that we need to dump the contents of the memory_k and memory_v tensors to disk, and load them back, and that would be the same as feeding the model the same prompt again. Choosing a fast compression algorithm would be a good way to mitigate the cost of storing massive tensors on disk.

I think this could be exposed through the API, but it's not necessarily something that should be part of the API by default. I'd break apart the inference_with_prompt function into easy-to-manipulate steps, so that users could save the state of the LLM at any given moment, and make that easy to do.
That being said, that sounds pretty reasonable to do for both the CLI and/or the API. Either/or could serve as a "batteries-included" example of how to ship something that's consistently fast with the library.

Another thing I have on my radar is this famous "GPTQ 4bit" quantization. It is well known (I mean, you just need to run a trivial example) that the 4-bit quantization in llama.cpp affects the results of the network. If this GPT4 quantization is capable of keeping the same quality as the f16 version as some sources claim, this would be huge. But I would need to investigate more to be sure.

Oh yeah, it's pretty cool. I haven't played around with it much myself, but the folks over at the text-generation-webui have used it to get LLaMA 30B into 24GB VRAM without much quality loss. Seems like it's something that upstream is looking at, though, so I'm content to wait and see what they do first.

Yup, also considered that, I'd love to do this if possible :) Not sure how long it would take, but none of the tensor operations I ported seem too complicated. The code should be pretty straightforward to port to a different library, and I'm sure some of the Rust options achieve a more ergonomic (and safe!) API. We just have to keep an eye on performance, but having an already working ggml version means we can just benchmark.

Yeah, I think most of the existing Rust ML libraries should be able to handle this. I was surprised at how few operations it used while porting it myself! It's certainly much simpler than Stable Diffusion.

If that change also helps us support GPU inference, that'd be pretty cool. But I don't want to add GPU support if that means people having to mess with CUDA or rocm drivers and report all sorts of issues. Unless it's something portable that works out of the box for people, I'm not interested.

Agreed. I have lost far too much of my time trying to set up CUDA + Torch.

I'm not sure how crazy it would be to build a tensor library on top of wgpu compute shaders. Just throwing that out there for anyone who feels crazy and/or adventurous enough 🤔 But that would eventually mean tensors on wasm, which is pretty darn cool I guess?

Check out wonnx! I'm not sure if it can be used independently from ONNX, but it would be super cool to figure out. Worth having a chat with them at some point.
You could also just run the existing CPU inference in WASM, I think - you might have to get a little clever with how you deal with memory, given the 32-bit memory space, but I think it should be totally feasible to run 7B on the web. The only reason I haven't looked into it is because the weights would have to be hosted somewhere 😅

Anyway, I'm happy to have someone else on board 😄 If there's anything I mentioned above you'd like to take the lead on, please say so! I'm not going to be making any big changes to the code in a few days.

I think we're in a pretty good place! I think it's just figuring out what the best "library API" would look like, and building some applications around it to test it. From there, we can figure out next steps / see what other people need.

Actually, I did a bit of port too lol. But I am not familiar with c bindings, and I am not so brave to port the ggml library, so I just rewrite some code and leave it there. it's the utils.cpp
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=46f060c6953d228fcb46ea67dea8e8b8
and I am also not sure whether it works properly. But it compiles.

@noeda of https://github.com/Noeda/rllama might wanna tag along here ☺
Also, a Tauri-app equivalent to https://github.com/lencx/ChatGPT would pair very well with this. Good task for anyone who wants to be involved but doesn’t quite feel comfortable with the low level internals.

I've been testing on Windows with my patches applied and it seems to work fine. It's probably not as fast as it could be, but it's plenty fast enough!

Glad to hear it! Then I said nothing :) If you're able to test things there, we can aim for good Windows support too then. This is probably going to be something where Rust makes it a lot more simple to get going than the C++ version.

I've never really delved into that kind of lifetime trickery!

Me neither, I'm not even sure it is possible :thinking: But definitely interesting! Still, I'd rather go down the route of replacing ggml with a pure Rust solution than to spend a lot of time building safe bindings to ggml.

Well... I'd actually started on this before you replied :joy:

:heart:

it's not the best API, but it does prove that all you need to do is offer up a HTTP interface and They Will Come :tm:

I think that's a very good point! As for the HTTP interface, one interesting requirement the image generation APIs don't have is that with text, you generally want to stream the outputs.
A good way to do this without complicating the protocol is use something called "chunked transfer encoding" where the server sends bits of the response one piece at a time, and a compatible client can fetch the results as they come without waiting for the end of the HTTP response. Chunked transfer is a pretty old thing and should be well supported in every HTTP client. I know @darthdeus already did a little proof of concept and this works well.

That being said, that sounds pretty reasonable to do for both the CLI and/or the API. Either/or could serve as a "batteries-included" example of how to ship something that's consistently fast with the library.

Yes :) I'm really interested in making this as simple as possible. What we could do on the library side, is to have the main inference_with_prompt returns some MemoryOut<'model> struct containing several byte slice(s) for the context memory (lifetime would make sure refs never outlive the Model). We could also make that same function take an Option<MemoryIn>, which is the same struct but with owned vecs instead of slices, and that would replace the working memory from a pre-computed cache.
By default, callers just pass in None and ignore the result, and that gives them the original experience. So it's up to the caller to manage / store / serialize / whatever this cache if they want to.

Check out wonnx! I'm not sure if it can be used independently from ONNX, but it would be super cool to figure out. Worth having a chat with them at some point.

Will do!! :eyes: The idea of wgpu tensors is just so appealing in that it basically works anywhere with no driver issues and on any GPU.

I think we're in a pretty good place! I think it's just figuring out what the best "library API" would look like, and building some applications around it to test it. From there, we can figure out next steps / see what other people need.

Sounds good :)

@Noeda of https://github.com/Noeda/rllama might wanna tag along here :relaxed:
Also, a Tauri-app equivalent to https://github.com/lencx/ChatGPT would pair very well with this. Good task for anyone who wants to be involved but doesn’t quite feel comfortable with the low level internals.

Indeed! The more we are working on this, the better :smile:
As a first contact, some benchmarks comparing the ggml here and rllama's OpenCL implementations on CPU would be a good first step to evaluate whether other Rust tensor libraries would fit the bill :)

Howdy :) I am very happy too LLM stuff picking up in Rust.
rllama is currently a chimera hybrid of 16-bit and 32-bit floats, where 16-bit floats are used in OpenCL and 32-bit floats in operations not involving OpenCL.

As a first contact, some benchmarks comparing the ggml here and rllama's OpenCL implementations on CPU would be a good first step to evaluate whether other Rust tensor libraries would fit the bill :)

Currently in terms of performance or memory use rllama is not competetive with any of the ggml stuff. I have no quantization whatsoever.
I just checked my latest commit and on CPU only OpenCL I got 678ms per token. (with GPU, ~230ms). The llama.cpp project mentions in README.md that they are at around 60ms per token which is 4x faster than even my GPU version.
I have two ideas how to collaborate in near future:

Verification of results. I get reasonable text in my implementation but I don't know if it's really done all correctly, especially tokenization. Would our projects get same output if we set top_k=1, and use the same prompt?
Apples-to-apples benchmarking scripts. I currently run a shell script that tests each configuration of rllama (GPU on/off, LLaMA-7B vs LLaMA-13B). It's very ad-hoc.

I am currently working on removing more performance bottlenecks out which might improve my rllama performance and memory, but after that I can offer to make a simple verification + benchmark suite that knows how to run our projects and verify they get the same results. I also wanted to make pretty graphs showing memory or CPU utilization use over time etc. Maybe this would go into a new repository. If you have any ideas here, I'm all ears.
Excited for all us :) 👍

I just checked my latest commit and on CPU only OpenCL I got 678ms per token. (with GPU, ~230ms). The llama.cpp project mentions in README.md that they are at around 60ms per token which is 4x faster than even my GPU version.

I guess it depends on the CPU, but my times for the f16 models are closer to 230ms, so I'd be inclined to say GPU and CPU speed is comparable. This also matches my results from when I tried another gpu implementation. On the quantized models, I do get ~100ms/token.

Verification of results. I get reasonable text in my implementation but I don't know if it's really done all correctly, especially tokenization. Would our projects get same output if we set top_k=1, and use the same prompt?

That's a very good idea :)  Other than setting top_k and the same prompt, we would need to make sure rng happens in the exact same way. We're currently using whatever rand's thread_rng gives by default, which is bad for reproducibility. Sampling is done using a rand WeightedIndex, and that's the only time the rng is invoked for each of the sampled tokens:
let dist = WeightedIndex::new(&probs).expect("WeightedIndex error");
let idx = dist.sample(rng);

So my guess is that as long as we're both using the rand crate, results should be comparable.

I can offer to make a simple verification + benchmark suite that knows how to run our projects and verify they get the same results

That would be amazing! :)

It's worth noting that quantisation affects both speed and quality, so any benchmarks should be done with the original weights (which will probably limit the maximum size that can be used). Additionally, llama.cpp seems to have some existing bugs around tokenisation and inference at f16.
That is to say - let's get this benchmark on the road, but I think we'll be returning slightly incorrect results until we can address those issues.

I want to share an idea for a project that I want to start implementing after I understand a little about the topic of AI and how everything works. Perhaps something similar already exists in some way, it would be interesting to learn about it.
Project Idea:
Introducing an entertaining and engaging podcast platform where AI hosts converse not only with each other but also with human guests for fun and profit. This concept allows AI to take the lead in creating captivating and lighthearted discussions, asking questions, and maintaining conversations with guests, whether they are AI or human.
Features to Implement:

AI host: The AI will assume the role of a host, responsible for initiating and sustaining interesting and enjoyable conversations with guests (both AI and human).
Text-to-Speech (TTS) integration: AI-generated text will be converted into speech using a TTS program, providing a more natural and engaging listening experience.
Speech-to-Text (STT) integration: Human speech will be converted into text using an STT program, allowing the AI host to interpret and respond to the guest's input.
Infinite conversation loop: The AI-hosted conversations will continue in a potentially endless loop until manually stopped by a behind-the-scenes operator.
AI host and guest models: Utilize AI models based on LLaMA, which can be run locally or accessed via API to servers (e.g., GPT-4, PaLM).
Offline functionality: Ideally, the podcast platform can be run locally on any PC without an internet connection, enabling users to participate without relying on external servers.
Live streaming integrations: Integrate with popular streaming platforms like YouTube and Twitch, allowing users to broadcast their AI-hosted podcasts live to a wider audience.
User-generated content: Enable users to submit their own topics, questions, or themes for AI-hosted conversations, providing a more interactive and personalized experience.
Voice customization: Offer a range of AI-generated voices and accents for the AI host and guests, allowing users to select their preferred voice styles.
Language support: Incorporate multilingual capabilities, enabling the AI host and guests to engage in conversations in various languages and catering to a diverse audience.

This project brings to life my childhood dream of listening how to machines converse with each other and with humans. The time has come to make this vision a reality, at least to some extent!
Project name and short description
Beyond Human: A podcast platform where AI hosts converse with other AI and human guests on various topics for fun and profit, sparking intriguing and thought-provoking discussions.
So far, I have vague ideas of how this can be implemented, but I feel that it must be done :)
Repository: https://github.com/ModPhoenix/beyond-human


view.commonwl.org does not display Graph of CWL User Guide 1st-tool.cwl

Common Workflow Language Viewer does not display the Graph of user_guide/1st-tool.cwl at gh-pages · common-workflow-language/user_guide
Description

I provide the following URL to URL to workflow field and push Parse Workflow
https://github.com/common-workflow-language/user_guide/blob/gh-pages/_includes/cwl/1st-tool.cwl

But there is not graph.
Expected Behavior

Display the graph of user_guide/1st-tool.cwl at gh-pages · common-workflow-language/user_guide
Actual Behavior

Error
Error: The workflow could not be found within the repository

Looks like this

Possible Fix

I hope more messages about the cause of error.
It is better to provide more information , ex. the error line of the file or URL is wrong or something about Why this workflow is not parsed ?
Steps to Reproduce

Open https://view.commonwl.org
Fill URL of workflow with https://github.com/common-workflow-language/user_guide/blob/gh-pages/_includes/cwl/1st-tool.cwl
Push Parse Workflow

Context

I want to see the graph of CWL files of CWL User guide .
At least I hope https://view.commonwl.org can parse any CWL file on https://github.com/common-workflow-language/
because view.commonwl.org is official tool.
Your Environment

Version used:
Mac  62.0.3202.94 (Official Build) (64-bit)

The reason of the error is that the viewer is just for CWL Workflows not CommandLineTools or ExpressionTools. I agree that the error should be improved if a CommandLineTool was provided

Thanks.
I understand why the graph is not display.
I hope to support display CommandLineTool graph 😄

@manabuishii What would you want from a CommandLineTool visualization?

@mr-c
The reason why I want to visualize CommandLineTool
The very fist example of user guide 1st-tool.cwl is CommandLintTool
Common Workflow Language User Guide: First Example
So I want to visualize it to demonstrate to other people.

Are you saying you'd like a diagram similar to the workflow visualizations with inputs at the top and outputs at the bottom with the baseCommand at the center?
Or do you want every inputBinding and argument also visualized?


⚠ Bofrost.at has degraded performance

In 9b359b5, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1765 ms

Resolved: Bofrost.at performance has improved in 53d12b9 after 15 minutes.


add deploy contract by proxy contract interface

Codecov Report

Merging #84 into release-rc4 will increase coverage by 1.96%.
The diff coverage is 4.95%.

@@                Coverage Diff                @@
##             release-rc4      #84      +/-   ##
=================================================
+ Coverage          37.72%   39.68%   +1.96%
  Complexity           369      369
=================================================
  Files                 49       48       -1
  Lines               3820     3611     -209
  Branches             334      324      -10
=================================================
- Hits                1441     1433       -8
+ Misses              2279     2077     -202
- Partials             100      101       +1

Impacted Files
Coverage Δ
Complexity Δ

.../com/webank/wecross/stub/bcos/AsyncCnsService.java
8.82% <0.00%> (+3.79%)
2.00 <0.00> (ø)

...a/com/webank/wecross/stub/bcos/BCOSConnection.java
66.01% <ø> (ø)
25.00 <0.00> (ø)

...om/webank/wecross/stub/bcos/BCOSGMStubFactory.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

.../com/webank/wecross/stub/bcos/BCOSStubFactory.java
22.72% <ø> (ø)
4.00 <0.00> (ø)

...va/com/webank/wecross/stub/bcos/abi/ABIObject.java
78.38% <0.00%> (-0.46%)
93.00 <0.00> (ø)

...ecross/stub/bcos/custom/DeployContractHandler.java
3.29% <0.00%> (+0.24%)
2.00 <0.00> (ø)

...k/wecross/stub/bcos/custom/RegisterCnsHandler.java
8.33% <0.00%> (-1.67%)
2.00 <0.00> (ø)

.../webank/wecross/stub/bcos/proxy/ProxyContract.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...cross/stub/bcos/proxy/ProxyContractDeployment.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../java/com/webank/wecross/stub/bcos/BCOSDriver.java
23.26% <25.00%> (+0.43%)
34.00 <0.00> (ø)

... and 4 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 fd058e7...12f980a. Read the comment docs.


access-control-allow-origin settings are changed by default on local environment

What is actually happening?
I have already asked a similar question, within the theme of a closed issue, the question concerns the operation of the application with CORS rules. The fact is that when I run the application locally and add the nuxt-security module to my project, it applies all the rules except CORS: Access-Control-Allow-Origin: *. Is this the default behavior of Nuxt 3, or is it happening in this particular version of the application because I'm using the latest version of Nuxt 3.7.3? I tried to run the project in the Stackblitz and CORS rules are applied correctly there and Access-Control-Allow-Origin is set to http://localhost:3000, but when I download and run this project locally, Access-Control-Allow-Origin: allows access to all resources which is set to *.
Version
nuxt-security: v0.14.4
nuxt: v3.7.3
Steps to reproduce
Run from this link: Stackblitz
And also try to test it locally on the same version Nuxt.js

@Don1k1337
Have you closed the issue because it is a duplicate or is the error gone?

The error has disappeared. By default, the browser shows
access-control-allow-origin: *
``` in the "Network" tab, but when you try to knock from the outside, it prohibits access within the CORS rules, as it should be.
Strangely, it works. Thank you :)

Thanks for letting me know then :)
I will also close another issue.


How to make it work with Clipman

Hi,
How can I make it work with the Clipman clipboard https://docs.xfce.org/panel-plugins/xfce4-clipman-plugin/start ?
Thank you.

Hi @blogdemoi ,
sorry for keeping you hanging so long!
I am not immediately familiar with this 'Clipman' tool, though it seems to be a clipboard manager which is mostly there to keep a recent history of your copied selections?
If so, it should work more or less automatically. If anything is copied into one of the clipboard the tool should pick it up and show it as an entry.
You will however still need one of xclip or xsel installed on your system since they are the programs that get the selection into the clipboard in the first place.
Does this help with your question?
Let me know if you intended something else instead.

If anything new pops up let me know, but for now I would consider this issue closed.


refactor(ndt_scan_matcher): isolate align function into ndt_omp

Signed-off-by: kminoda<EMAIL_ADDRESS>Description
I would like to isolate the align function in the current ndt_scan_matcher (and also the NdtResult class) to ndt_omp.
This PR should be merged at the same time as https://github.com/tier4/ndt_omp/pull/16.
(side note: This PR may induce a build error due to the version mismatch between autoware.universe and ndt_omp, only when the newer universe used with the older ndt_omp)

Related links

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

This PR will be ready for review after https://github.com/tier4/ndt_omp/pull/16 is merged. (The CI test would not pass until then)


Clicking the Syndication Feed Icon on a community or collection results in a 404 Whitelabel Error Page

Describe the bug
Clicking the Syndication Feed Icon on a community or collection in 7.4 results in a 404 Whitelabel Error Page. Not sure if a wrong link is displayed or if the link is correct but no feed is served by the backend.
To Reproduce
Steps to reproduce the behavior:

Navigate to any community or collection, e.g. on the DSpace 7 Demo Site: https://demo7.dspace.org/collections/add23764-0671-4b11-8463-d8c60bf4c744
Click the feed icon
You will see a 404 Whitelabel Error Page

Expected behavior
I expect a valid feed that includes the publications of this community or collection

I've verified this locally & on demo7.dspace.org.  It appears, to me, that the link is incorrectly generated in the UI.
The UI is creating feed links that look like this:
${dspace.server.url}/opensearch/search/search?(params)

That throws a 404.
Instead, the correct link is this:
${dspace.server.url}/opensearch/search?(params)

I'm not sure where the extra /search is coming from yet.  I'll pull this over to our board though and flag as high priority & needing a volunteer.

Looking at the history of the RSS component, the opensearch link was hard-coded until this commit that brought in the websvc.opensearch.svccontext parameter from dspace.cfg in the REST API – https://github.com/DSpace/dspace-angular/commit/be8a8f5f6bf9359eecc8034b22c522fe9ac1389f. But the changes to the formulateRoute method don't accord with the default value of svccontext. I'll create a small PR.


Regenerate yamls

Signed-off-by: Matthias Wessendorf<EMAIL_ADDRESS>as per title, regenerated

/assign @pierDipi


router: fix dynamic weight crash

Commit Message:
fix up crash while updating weighted clusters, when the total weight is changing through runtime keys.
Additional Description:
[assert] [source/common/router/config_impl.cc:1366] panic: unexpected
[backtrace] [./source/server/backtrace.h:127] Caught Aborted, suspect faulting address 0xfffe00000001
[backtrace] [./source/server/backtrace.h:111] Backtrace (use tools/stack_decode.py to get line numbers):
[backtrace] [./source/server/backtrace.h:112] Envoy version: 16a0cedaba5335a8003c5077a07a49fafd3eea97/1.30.1/Clean/RELEASE/BoringSSL
[backtrace] [./source/server/backtrace.h:114] Address mapping: 560c90beb000-560c93592000 /usr/local/bin/envoy
[backtrace] [./source/server/backtrace.h:121] #0: [0x7f7cc0a1f520]
ActiveStream 0x55d99505500, stream_id_:<PHONE_NUMBER>973121232&filter_manager_:
  FilterManager 0x55d995055b0, state_.has_1xx_headers_: 0
  filter_manager_callbacks_.requestHeaders():
  &streamInfo():
    StreamInfoImpl 0x55d995056f0, protocol_: 1, response_code_: null, response_code_details_: null, attempt_count_: null, health_check_request_: 0, getRouteName():     upstream_info_:     null
    OverridableRemoteConnectionInfoSetterStreamInfo 0x55d995056f0, remoteAddress(): <IP_ADDRESS>:18710, directRemoteAddress(): <IP_ADDRESS>:18710, localAddress(): <IP_ADDRESS>:6032
Http1::ConnectionImpl 0x55daa38f810, dispatching_: 1, dispatching_slice_already_drained_: 0, reset_stream_called_: 0, handling_upgrade_: 0, deferred_end_stream_headers_: 0, processing_trailers_: 0, buffered_body_.length(): 0, header_parsing_state_: Field, current_header_field_: , current_header_value_:
active_request_:
, request_url_: null, response_encoder_.local_end_stream_: 0
absl::get<RequestHeaderMapPtr>(headers_or_trailers_): null
ConnectionImpl 0x55da6d047d0, connecting_: 0, bind_error_: 0, state(): Open, read_buffer_limit_: 131072
socket_:
  ListenSocketImpl 0x55db7be3ef0, transport_protocol_: raw_buffer
  connection_info_provider_:
    ConnectionInfoSetterImpl 0x55da4b54b18, remote_address_: <IP_ADDRESS>:18710, direct_remote_address_: <IP_ADDRESS>:18710, local_address_: <IP_ADDRESS>:6032, server_name_:
[backtrace] [./source/server/backtrace.h:127] Caught Segmentation fault, suspect faulting address 0x0
[backtrace] [./source/server/backtrace.h:111] Backtrace (use tools/stack_decode.py to get line numbers):
[backtrace] [./source/server/backtrace.h:112] Envoy version: 16a0cedaba5335a8003c5077a07a49fafd3eea97/1.30.1/Clean/RELEASE/BoringSSL
[backtrace] [./source/server/backtrace.h:114] Address mapping: 560c90beb000-560c93592000 /usr/local/bin/envoy
[backtrace] [./source/server/backtrace.h:121] #0: [0x7f7cc0a1f520]
Our FatalActions triggered a fatal signal.

Risk Level: Low
Testing:
We update the tests to reflect the changes which are now taking care of runtime values.
tests:

deploy a config with 2 weighted cluster weight 1/100

  "routing.cluster_weight.fooA": {
   "final_value": "1",
   "layer_values": [
    "1",
    "",
    "",
    ""
   ]
  },
  "routing.cluster_weight.fooB": {
   "final_value": "100",
   "layer_values": [
    "100",
    "",
    "",
    ""
   ]
  }

deploy the new binary
update the weight to 100/100

  "routing.cluster_weight.fooA": {
   "final_value": "100",
   "layer_values": [
    "100",
    "",
    "",
    ""
   ]
  },
  "routing.cluster_weight.fooB": {
   "final_value": "100",
   "layer_values": [
    "100",
    "",
    "",
    ""
   ]
  }

there should be no crash

some notes/open questions:

There is a similar function in utility:
https://github.com/envoyproxy/envoy/blob/570869520b69fcee00e3b834c40053d55907facb/source/common/common/utility.h#L505
We could refactor it to make use of it everywhere, but it is a much larger change. I believe this could be followed in another PR.

should we get rid of total cluster weight parameter entirely? maybe for another PR as well? https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-field-config-route-v3-weightedcluster-total-weight

this PR also fixes issue #22873

@ggreenway @alyssawilk is there any chance we can get someone assigned to review this PR?

/wait-any

Hi @tyxia
Thanks for your review and sorry for the delay to address the comments.

(1) For option 1, can we limit the re-computation of total weight when runtime_key_prefix is configured.
This re-computation introduces data plane overhead which is redundant when there is no runtime update.
(2) can you also add a test that originally will hit PANIC code. You can update it to a very small new weight range to repro this

I believe I addressed both. It makes some aspects slightly harder to read as we have to condition on runtime_key. Let me know it is good enough for you.

Before looking into code change, i think it will be good to have another API shepherd review the on the proposed direction of the fix
@adisuissa I know you have worked on weighted cluster divide-by-0 crash before, could you also take a look of direction above? Thanks!

@adisuissa let me know if I can clarify something

(1) For option 1, can we limit the re-computation of total weight when runtime_key_prefix is configured.
This re-computation introduces data plane overhead which is redundant when there is no runtime update.

I agree that recomputing the total-weight only when the runtime_key_prefix is enabled makes sense.
Regarding whether to return nullptr vs PANIC, I think it would be better to keep the PANIC.
If nullptr is returned, it requires all callers to handle that, otherwise the issue is just punted up the call stack, and makes it harder to debug. If there are other cases that cause a PANIC, they should be handled explicitly in this code.
In the context of this change:

if the total-weight is 0 because no cluster doesn't exist - I wonder if this case can even happen.
if there's overflow of the sum of all weights - would using the original weights make sense here (with an appropriate warning)?

Thanks for your reply @adisuissa

In the context of this change:

if the total-weight is 0 because no cluster doesn't exist - I wonder if this case can even happen.

I think it cannot happen with regular config: https://github.com/envoyproxy/envoy/blob/b8ae3ab32964bb200894f6fc11ffe3cfbcdd9335/source/common/router/config_impl.cc#L659
but I think it is possible with runtime keys

if there's overflow of the sum of all weights - would using the original weights make sense here (with an appropriate warning)?

I believe this might create confusion in user's mind if we start to fallback on a different behaviour they don't expect with runtime keys. I would however propose to followup this PR by removing the deprecated total_weight parameter notion from the config - this would make things more logical.

Ping @adisuissa @tyxia
/wait-any

My 2 cents is that we should avoid dateplane crash caused by invalid runtime weight.
@adisuissa WDYT about Envoy_BUG + return nullptr? Caller-side should already be able to handle nulltpr return (as if no route match) but I do agree that returning nullptr will make debugging harder. Hopefully Envoy_BUG could help debugging here.

I agree with ENVOY_BUG, but I'm just guessing that nullptr will crash somewhere else. IMHO it will make it a bit more challenging to debug. That said, I'm don't feel strongly about these approaches.
Maybe converting the return type to absl::StatusOr<> might be a better approach.

My 2 cents is that we should avoid dateplane crash caused by invalid runtime weight.
@adisuissa WDYT about Envoy_BUG + return nullptr? Caller-side should already be able to handle nulltpr return (as if no route match) but I do agree that returning nullptr will make debugging harder. Hopefully Envoy_BUG could help debugging here.

I agree with ENVOY_BUG, but I'm just guessing that nullptr will crash somewhere else. IMHO it will make it a bit more challenging to debug. That said, I'm don't feel strongly about these approaches. Maybe converting the return type to absl::StatusOr<> might be a better approach.

AFAIU, returning nullptr here == no route found, because its caller is RouteConstSharedPtr matches() ---> RouteMatcher::route. Will envoy crash when no route found? I think it will try local rely in this case, or maybe I miss something?

AFAIU, returning nullptr here == no route found, because its caller is RouteConstSharedPtr matches() ---> RouteMatcher::route. Will envoy crash when no route is found? I think it will local rely in this case, or maybe I miss something?

Ah, I think you are correct, and the uses of this method (that we are aware of) seem to be taking nullptr as an indication that  the route is not found. That said, previously this method did not return nullptr, so it seems a bit strange...
I guess this method should have a better/correct documentation.
I don't feel strongly about this, so I'll leave it up to you to decide.

Yeah, we should figure out error handling of invalid runtime weight update.

I changed it to Envoy_BUG as advised.

/assign-from @envoyproxy/senior-maintainers
This PR touches Envoy core code.

/wait-any

We are getting closer. LGTM modulo some nits. I have also added senior maintainer here since this PR touches core Envoy code.

I addressed all the remaining comments

PS: Just a note for future, please don't use force push so that the full commit history can be kept, which makes reviewer and future reader's life easier.

ah sorry, I will make sure to change that in my upcoming changes

Is it possible to add a test for the case where total cluster weight is 0 ? I see the behavior has changed but it is not clear to me returning nullptr in that case will not cause a crash.

good point, I added a test about it.

@yanavlasov for a senior-maintainer review


Initial defaults chart version tied to controller appVersion

Fix #721
The kubewarden-defaults chart install banner was not tied to the installed kubewarden-controller appVersion, in order to make this work I restructured the methods used in the Dashboard component into utilities and added a method for finding the compatible defaults chart based on the installed controller's appVersion.
https://github.com/rancher/kubewarden-ui/assets/40806497/39ccf533-9927-4966-ae42-3840ca730812

I wasn't able to reproduce this, but I added a condition to the banner dependent on the loading state, and to the chart install button to not show unless a compatible chart is found.

Now I get error in console on refresh (Install Defaults button is not visible)
fetch.client.js:79 Error in fetch(): TypeError: Cannot read properties of undefined (reading 'cluster/schemaFor')
    at o (kubewardenController.ts:9:14)
    at a.fetch (DefaultsBanner.vue:38:1)
    at a.<anonymous> (fetch.client.js:76:31)
    at p (regeneratorRuntime.js:44:17)
    at Generator.<anonymous> (regeneratorRuntime.js:125:22)
    at Generator.next (regeneratorRuntime.js:69:21)
    at r (asyncToGenerator.js:3:20)
    at s (asyncToGenerator.js:22:9)
    at asyncToGenerator.js:27:7
    at new Promise (<anonymous>)

This might be a timing issue. I can revisit this in a later issue.


Prop Anarchy support

It has been reported that this doesnt work with anarchy.
Note to self: Just make the water collision check hotkey also work for all other types of collisions.

Fixed?
Needs verifying.

I often use this tool with size 1, so it places a random tree from my tree selection. Often i get the warning space occupied, while prop and tree anarchy is enabled.
Same happens when using a larger size brush. However when i disable collision detection in the  fine road tool i think,  it works with large brushes, but still not working with brush size 1.


Cannot unit test components which use <Link /> due to missing Router context

What version of Remix are you using?
1.7.4
Steps to Reproduce
Use test setup from Blues Stack:
// setup-test-env.ts
import { installGlobals } from "@remix-run/node";
import "@testing-library/jest-dom/extend-expect";

installGlobals();

Use Vitest 0.24.4 (perhaps Jest also) and write a simple unit test for a pure react component, which uses <Link /> component from @remix-run/react.
Current test:
// tags.test.tsx
describe("<Tags />", () => {
  it("renders list of links", () => {
    render(<Tags />);
    expect(screen.getAllByRole("link").length).toBeGreaterThan(0);
  });
});

I saw that one could pass additional config to render function with the actual router component as follows:
// tags.test.tsx

// replace
render(<Tags />);

// with
render(<Tags />, { wrapper: BrowserRouter });

The problem is that in this case BrowserRouter must be imported from react-router-dom package, which we don't need in a Remix app. But even with this approach, after adding this package to dev dependency, it doesn't solve the issue. Importing RemixBrowser doesn't work either, but due to other errors.
For some reason, the second approach (wrapping component with react router's BrowserRouter) seems to work after changing environment option in vitest.config.ts from happy-dom to jsdom.
Expected Behavior
Test is green.
Actual Behavior
app/components/tags.test.tsx > <Tags /> > renders list of links
Error: useHref() may be used only in the context of a <Router> component.
 ❯ invariant ../packages/react-router/lib/router.ts:5:20
 ❯ Object.useHref ../packages/react-router/lib/hooks.tsx:32:3
 ❯ node_modules/@remix-run/react/dist/components.js:390:29
 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:16305:18
 ❯ updateForwardRef node_modules/react-dom/cjs/react-dom.development.js:19226:20
 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21636:16
 ❯ HTMLUnknownElement.callCallback node_modules/react-dom/cjs/react-dom.development.js:4164:14
 ❯ HTMLUnknownElement.dispatchEvent node_modules/happy-dom/src/event/EventTarget.ts:66:41
 ❯ HTMLUnknownElement.dispatchEvent node_modules/happy-dom/src/nodes/node/Node.ts:477:29
 ❯ Object.invokeGuardedCallbackDev node_modules/react-dom/cjs/react-dom.development.js:4213:16
 ❯ invokeGuardedCallback node_modules/react-dom/cjs/react-dom.development.js:4277:31
 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27451:7
 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26560:12
 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26466:5
 ❯ renderRootSync node_modules/react-dom/cjs/react-dom.development.js:26434:7
 ❯ recoverFromConcurrentError node_modules/react-dom/cjs/react-dom.development.js:25850:20
 ❯ performConcurrentWorkOnRoot node_modules/react-dom/cjs/react-dom.development.js:25750:22
 ❯ flushActQueue node_modules/react/cjs/react.development.js:2667:24
 ❯ act node_modules/react/cjs/react.development.js:2582:11
 ❯ node_modules/@testing-library/react/dist/act-compat.js:63:25
 ❯ renderRoot node_modules/@testing-library/react/dist/pure.js:159:26
 ❯ Proxy.render node_modules/@testing-library/react/dist/pure.js:246:10
 ❯ app/components/tags.test.tsx:26:4
     24|   it("renders list of links", () => {
     25|     // render(<Tags tags={mockTags} />, { wrapper: BrowserRouter });
     26|     render(<Tags tags={mockTags} />);
       |    ^
     27|     expect(screen.getAllByRole("link").length).toBe(3);
     28|   });

The team are working on official testing helpers on their backlog. In the meantime you should read through Ryan's createRemixStub design here and there's a sample implementation you can copy + paste here.

Closing this issue as it's already tracked in https://github.com/remix-run/remix/issues/4488


rendering bug when remove input element

Description

if click 1, then remove 1. 2 and 3 also same, and it is clear.
but. if i change some value and try to remove. then. removed it from below.
i don't know it is bug of lit or html or something..
of course it can be solve by another way with additional code but i think it is not natural.
https://github.com/lit/lit-element/issues/807
https://stackoverflow.com/a/59381119/12365658
Steps to Reproduce

Write this code
change value.
click remove event.

import { LitElement, html } from 'lit';
import { customElement, property } from 'lit/decorators.js';

@customElement('test-container')
export class TestContainer extends LitElement {
  testItems = [
    {innerId: 1, value: 1},
    {innerId: 2, value: 2},
    {innerId: 3, value: 3}
  ]

  render(){

    const items = []
    for(const item of this.testItems){
      items.push(this.renderItem(item.innerId, item.value));
    }

    return html`<div>${items}</div>`;
  }

  renderItem(id: number, value: number){
    return html`<test-item @remove=${this.clickRemoveItem} innerId=${id} value=${value}></test-item>`
  }

  clickRemoveItem(e: any){
    const remove_id = e.detail.innerId;
    for(let i=0; i < this.testItems.length; i++) {
      if(this.testItems[i].innerId == remove_id) {
        this.testItems.splice(i, 1);
        break;
      }
    }
    this.requestUpdate();
  }
}

@customElement('test-item')
export class TestItemContainer extends LitElement{

  @property()
  innerId = "";

  @property()
  value = "";

  clickRemove(){
    this.dispatchEvent(new CustomEvent("remove", {detail: {innerId: this.innerId}, bubbles: true, composed: true}))
  }

  render(){
    const countries_template:any = [];

    return html`
      <div @click=${this.clickRemove}>Remove</div>
      <input type="text" value=${this.value}>
    `
  }
}

See this output...

Live Reproduction Link

https://stackblitz.com/edit/lit-html
Expected Results

Actual Results

Browsers Affected

[x] Chrome
[x] Firefox
[ ] Edge
[ ] Safari 11
[ ] Safari 10
[ ] IE 11

This turned out to be a lot more of a fascinating issue! @AndrewJakubowicz and I dug a little into the example.
The default way that Lit handles an array of items is that it'll create DOM nodes for each item of the array, and it'll reuse them on subsequent updates. If the item count changes during update, it'll either create more, or remove the extra DOM nodes. The extra DOM node is removed from the end.
So here's where the interesting behavior comes in. When you have this in the template rendered for the <test-item>
      <input type="text" value=${this.value}>

it sets the value attribute of the input element. If the value of the input element doesn't change, the attribute drives what gets displayed in the input element. This is why, when none of the inputs are modified, removing one appears to work properly because what's displayed in the input elements are driven by the the actual state in Lit.
Once the user starts modifying the input value, the value property of the input element changes and that starts driving what gets displayed inside the input element. So of the 3, if you modify the value of the 2nd element, and remove any one of them, the 2nd element always has that modified text. Lit will update the attributes of the remaining elements to match the actual remaining items of the array, but the attribute no longer is driving what's displayed for the element whose value was changed.
So what's the solution? There are a couple options here.
Option 1: Lit can have total control of the state.
First, the binding should be a property binding like this with a .
      <input type="text" .value=${this.value}>

such that the value property of the input element is controlled by Lit. But in order to keep the internal state consistent with what's displayed, you should also then add a listener for the input event on the input element that updates the value inside the object in testItems.
      <input type="text" .value=${this.value} @input=${this.updateValue}>

And updateValue could dispatch an event similar to your clickRemove that gets picked up by the parent element to update the correct item's value in testItems.
Option 2: Use the repeat directive as you've found.
This method will mean you rely on the DOM node to keep its state. Using the repeat directive links the DOM node to a specific item of the array with an id. So if you request one of them to be removed, Lit'll specifically find and remove the DOM node associated with that, rather than removing the last and updating the rest like it normally does.
This is also explained in When to use map or repeat and this video also goes into explanations of an element's attribute and property.

I should add that the options mentioned above are not mutually exclusive and are addressing separate concerns. While each of them alone does solve the visual problem you're seeing, depending on use case, you may actually want to utilize both of them like this https://lit.dev/playground/#gist=b88b4acf39a6bd7ee2a931d3a432a6d6.
Generally, when you're collecting user data with inputs, you likely want access to that data, and perhaps have other elements react to the user input as they are happening. So making sure you do the property binding with .value and adding @input event handler for updating internal state to sync with user input is useful regardless of whether you're about to remove one of them or not.
Also, if you have a list that will be shifting, regardless of whether they're input elements or not, using the repeat directive scales better as the list gets long since it would be more efficient to reorder the DOM nodes rather than update them all.

@au'great write up. We do try to address this case in the docs on working with Lists: https://lit.dev/docs/templates/lists/#when-to-use-map-or-repeat
This would fall under the case of "If the DOM nodes have state that isn't controlled by a template expression, use the repeat directive."
@arthurevans Given that we do talk about this already, I wonder if moving this sort of guidance up in the page would be useful?


A functional menu page using JS

A simple project that I did as part of my Javascript learning

Thank you for your contribution


add: CN/TT pool

This pool was active between block height 578638 and 622859. The real entity behind the pool is unknown, however all have CN/TT as coinbase tag. All coinbase outputs were created to 3QLeXx1J9Tp3TBnQyHrhVxne9KqkAS9JSR.

This could be the pool now known as Lubian.com


feat: Add shade config for creating uber-jar without Apt related code

I am wondering if we should also include the annotation itself.

Makes sense! I also want  to include a META-INF/services file

You can't include the whole META-INF/services as it contains the definition
of the processor, so we need to make sure we exclude this.
On Fri, Feb 15, 2019 at 9:29 AM Georgios Andrianakis <
<EMAIL_ADDRESS>wrote:

I am wondering if we should also include the annotation itself.
Makes sense! I also want to include a META-INF/services file
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/ap4k/ap4k/pull/121#issuecomment-463936644, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAYiWL0VasbceLh3Zk5ENyFLW9kkakmPks5vNmHpgaJpZM4a8EDt
.

--
Ioannis Canellos http://iocanel.com

You can't include the whole META-INF/services as it contains the definition of the processor, so we need to make sure we exclude this.
…
On Fri, Feb 15, 2019 at 9:29 AM Georgios Andrianakis < @.***> wrote: I am wondering if we should also include the annotation itself. Makes sense! I also want to include a META-INF/services file — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#121 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYiWL0VasbceLh3Zk5ENyFLW9kkakmPks5vNmHpgaJpZM4a8EDt .
-- Ioannis Canellos http://iocanel.com

Yup, will do :)

To include a META-INF/services/io.ap4k.Generator I need to have a default implementation, so I will leave that for another PR (we first need to figure out which of the generators make sense to have default implementations)

@iocanel Annotations added to noapt


Upgrade to commerce 14

Hi @mattbrailsford , in Klarna provider settings, there're some properties should be grouped under Advanced section but right now they're mixed up with regular properties. i.e: Payment Page Logo Url and Payment Page Page Title.

Ahh, looks like I may not have implemented the advanced properties feature. I'll get this added to the task list.

Unable to test because we have no test account


Update Schematic Setup docs with current Schematic version

Describe the bug
In the README, the docs says to run pip install dist/schematicpy-1.0.0-py3-none-any.whl, which fails.
To Reproduce
Steps to reproduce the behavior:
(.venv) vscode@a348f83e716d:/workspaces/btc-data-models/tmp/data_curator/schematic$ poetry build
Building schematicpy (22.3.2)
  - Building sdist
  - Built schematicpy-22.3.2.tar.gz
  - Building wheel
  - Built schematicpy-22.3.2-py3-none-any.whl
(.venv) vscode@a348f83e716d:/workspaces/btc-data-models/tmp/data_curator/schematic$ pip install dist/schematicpy-1.0.0-py3-none-any.whl
WARNING: Requirement 'dist/schematicpy-1.0.0-py3-none-any.whl' looks like a filename, but the file does not exist
Processing ./dist/schematicpy-1.0.0-py3-none-any.whl
ERROR: Could not install packages due to an EnvironmentError: [Errno 2] No such file or directory: '/workspaces/btc-data-models/tmp/data_curator/schematic/dist/schematicpy-1.0.0-py3-none-any.whl'

The error occurs because of the mismatched version of Schematic built and the version that the docs ask to install.
Expected behavior
The command should be:
pip install dist/schematicpy-22.3.2-py3-none-any.whl

Note Consider making the docs robust to Schematic version changes.

Priority (select one)

[x] Minor ⬇
[ ] Major 📢
[ ] Critical 🆘

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

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Moved to JIRA: https://sagebionetworks.jira.com/browse/FDS-472


Add a ResponseConverterFunction for RxJava Observables

.. so that a user can return an Observable of a single element (or a list of elements?)
We may also want to implement some automatic registration mechanism for ResponseConverterFunctions so that the Observable converter is automatically added to the default converter list using SPI.

I think that we can make a converter for Publisher and Observable with the following specifications:

If a single object is returned by Publisher (ex. Mono.just(obj)), try to convert the returned object by the registered converters when onComplete is invoked.
If multiple objects are returned by Publisher (ex. Flux.fromArray(arr)), collect the returned objects as a list then try to convert the list when onComplete is invoked.
The conversion for the streaming response is unsupported.

I think it's too complicate to convert streaming response because we might introduce a new interface like StreamingResponseConverter. So it would be simpler to handle the streaming response by a user.
Please let us know what you think about this issue. :-)
/cc @kojilin @imasahiro


CLI: error while loading shared libraries: libproc_macro: cannot open shared object file

rustc 1.32.0-nightly (9fefb6766 2018-11-13)
Steps to reproduce:
git clone --depth 1 https://github.com/graphql-rust/graphql-client.git
cargo build && cargo build --release # Just to cover the bases
cd graphql_client_cli
cargo install # --debug makes no difference
graphql-client --help

Output:
graphql-client: error while loading shared libraries: libproc_macro-6c2e946fbc2e5b5e.so: cannot open shared object file: No such file or directory

Temporarily, you can run it with cargo run from the source directory, that works for me. I haven't used the CLI a lot so I don't have a cleaner solution. This will be permanently solved by this PR: https://github.com/rust-lang/rust/pull/49219#issuecomment-438379259
Maybe @h-michael has a better solution?

This should occur only nightly build.
So you should build cli with stable rust until that PR merged.

merged: https://github.com/rust-lang/rust/pull/49219

Great news!

This is still an issue with latest stable.
Maybe the README should mention that the CLI only supports nightly right now.

Oh, actually I just noticed: even on nightly the built binary does not work!
It only works with cargo run. Executing target/debug/graphql-client still gives the same error.

@theduke
Thank you for your report.
I 'll try it later.

Is this still an issue?

I haven't tried in a very long time! It would be nice to clarify this.


images with "h-100" not dispalyed properly on iPhones

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Hi, I have a card with an image on the left and text on the right. Because the length of the text is variable, i have to set the image height to "100%" to match the text height (I don't care if the image is distorted). This is fine with PCs and Android phones but not OK with iPhones. On iPhones, the image will take the height of the whole viewport, while on Android phones the image height matches the text on the right (that's what I want). So how can I solve this issue on iPhones? Thank you very much! I have created a reduced test case with only  2 cards on the page (please see the link below). And below is a sample piece of my code (I'm using Bootstrap 5.1.1):

multiple lines of text....

Reduced test cases
https://hujiao24.com/test
Please view it on real iPhones (not in simulation environment like Chrome inspector) to see the issue.
What operating system(s) are you seeing the problem on?
iOS
What browser(s) are you seeing the problem on?
Safari
What version of Bootstrap are you using?
v5.1.1

@mdo Thanks. But It won't work on iPhones even if there is just single layer of "h-100". I have modified the test case. Could you please check again on iPhones? Also please note that this issue only happens on iPhones not on Android phones. And thanks for suggesting using background but i don't think it meets my needs because I don't want the images cropped (they can be distorted though).


Random sort & Storing sort values per category

https://youtu.be/S5UcfiNXW-c

Did the same lint error fixes on both my open prs, should be easy to merge if they conflict tho as they are the same changes


MXNet version

How could I download this specific version MXNet@(commit 62ecb60)? It seems not an available version in MXNet?

This is a specific commit of MXNet.

@Oh233 I got it, thank you!


Update download script with new url and take license key as parameter

I've moved the license key to a separate configuration file. Thanks for the PR.


Objective C

How can we use this in objective C ?

Hi ErAshu!
Yes you would need to use a Bridge Header in order to use it, but in theory there shouldn't be any problem.
Let me know if that worked well :)
Regards, Kevin Bel.

I can't find a way to make this work in an Objective-C project. Can you include a few lines of code in Objective-C as an example?

@inPhilly Hi!
i tried to use the library in Objc but i'm using structs and enums and another data structures in swift that are not available at Objective C because their are using associated values.
So i was wrong, you cannot use this library in Objective C, this library is only for Swift usage.


[CI] Travis ARM builds often crash

Those builds often crash with a compiler crash, for example:
https://travis-ci.com/github/apache/arrow/jobs/511663690

FAILED: CMakeFiles/libprotobuf.dir/build/cpp/protobuf_ep-prefix/src/protobuf_ep/src/google/protobuf/descriptor.cc.o

/usr/bin/c++  -DGOOGLE_PROTOBUF_CMAKE_BUILD -DHAVE_PTHREAD -DHAVE_ZLIB -I. -I/build/cpp/protobuf_ep-prefix/src/protobuf_ep/src -fdiagnostics-color=always -ggdb -O0 -g -fPIC   -fdiagnostics-color=always -ggdb -O0 -g -fPIC   -std=c++11 -MD -MT CMakeFiles/libprotobuf.dir/build/cpp/protobuf_ep-prefix/src/protobuf_ep/src/google/protobuf/descriptor.cc.o -MF CMakeFiles/libprotobuf.dir/build/cpp/protobuf_ep-prefix/src/protobuf_ep/src/google/protobuf/descriptor.cc.o.d -o CMakeFiles/libprotobuf.dir/build/cpp/protobuf_ep-prefix/src/protobuf_ep/src/google/protobuf/descriptor.cc.o -c /build/cpp/protobuf_ep-prefix/src/protobuf_ep/src/google/protobuf/descriptor.cc

c++: fatal error: Killed signal terminated program cc1plus

It seems this is a problem with the Travis-CI ARM execution environment.
Reporter: Antoine Pitrou / @pitrou
Assignee: Kouhei Sutou / @kou
PRs and other links:

GitHub Pull Request #10478

Note: This issue was originally created as ARROW-12991. Please see the migration documentation for further details.

@kou  trying to run following command on mac
docker-compose --file docker-compose.yml run --rm java-jni-manylinux-2014

resulted in similar issue
FAILED: src/arrow/CMakeFiles/arrow-array-test.dir/Unity/unity_0_cxx.cxx.o
/usr/local/bin/ccache /opt/rh/devtoolset-10/root/usr/bin/c++ -DARROW_HAVE_RUNTIME_AVX2 -DARROW_HAVE_RUNTIME_AVX512 -DARROW_HAVE_RUNTIME_BMI2 -DARROW_HAVE_RUNTIME_SSE4_2 -DARROW_HAVE_SSE4_2 -DARROW_S3_HAS_CRT -DARROW_WITH_LZ4 -DARROW_WITH_RE2 -DARROW_WITH_SNAPPY -DARROW_WITH_TIMING_TESTS -DARROW_WITH_UTF8PROC -DARROW_WITH_ZLIB -DARROW_WITH_ZSTD -DAWS_MQTT_WITH_WEBSOCKETS -DAWS_SDK_VERSION_MAJOR=1 -DAWS_SDK_VERSION_MINOR=11 -DAWS_SDK_VERSION_PATCH=4 -DAWS_USE_EPOLL -DCURL_STATICLIB -DGMOCK_LINKED_AS_SHARED_LIBRARY=1 -DGTEST_LINKED_AS_SHARED_LIBRARY=1 -DURI_STATIC_BUILD -DUTF8PROC_STATIC -I/build/cpp/src -I/arrow/cpp/src -I/arrow/cpp/src/generated -isystem /arrow/cpp/thirdparty/flatbuffers/include -isystem /opt/vcpkg/installed/amd64-linux-static-release/share/rapidjson/../../include -isystem /arrow/cpp/thirdparty/hadoop/include -isystem /opt/vcpkg/installed/amd64-linux-static-release/include -isystem /build/cpp/orc_ep-install/include -isystem /build/cpp/jemalloc_ep-prefix/src -isystem /build/cpp/googletest_ep-prefix/include -Wno-noexcept-type -Wno-subobject-linkage  -fdiagnostics-color=always  -Wall -fno-semantic-interposition -msse4.2  -O3 -DNDEBUG -O2 -ftree-vectorize  -fPIE -pthread -DS2N_KYBER512R3_AVX2_BMI2 -DS2N_STACKTRACE -DS2N_CPUID_AVAILABLE -DS2N_FEATURES_AVAILABLE -fPIC -DS2N_FALL_THROUGH_SUPPORTED -DS2N___RESTRICT__SUPPORTED -DS2N_MADVISE_SUPPORTED -DS2N_CLONE_SUPPORTED -std=c++17 -MD -MT src/arrow/CMakeFiles/arrow-array-test.dir/Unity/unity_0_cxx.cxx.o -MF src/arrow/CMakeFiles/arrow-array-test.dir/Unity/unity_0_cxx.cxx.o.d -o src/arrow/CMakeFiles/arrow-array-test.dir/Unity/unity_0_cxx.cxx.o -c /build/cpp/src/arrow/CMakeFiles/arrow-array-test.dir/Unity/unity_0_cxx.cxx
c++: fatal error: Killed signal terminated program cc1plus
compilation terminated.
[143/351] Building CXX object src/arrow/compute/kernels/CMakeFiles/arrow-compute-scalar-utility-test.dir/Unity/unity_0_cxx.cxx.o

You need to allocate more memory to fix it.
Could you open a new issue instead of reusing a closed issue next time?


Collect float64 in Measurement

This reduces allocations per stats.Record operation substantially:
git describe && go test  -run=^$ -benchmem -bench=.
v0.1.0-103-g23a8069
goos: darwin
goarch: amd64
pkg: go.opencensus.io/stats
BenchmarkRecord-8   	  500000	      2239 ns/op	     392 B/op	       5 allocs/op
PASS
ok  	go.opencensus.io/stats	1.163s

Compare: https://github.com/census-instrumentation/opencensus-go/wiki/stats-Benchmarks

@ramonza perhaps in the future, it might help to include the benchmarks from before and after and then using https://godoc.org/golang.org/x/perf/cmd/benchstat for comparisons. Thank you for getting this in.

@odeke-em thanks for pointing that out, I will definitely do that next time!


parser: add new function name IsTruthWithNull (#1005)

What problem does this PR solve?
cherry-pick https://github.com/pingcap/parser/pull/1005
related pr: https://github.com/pingcap/tidb/pull/19903
What is changed and how it works?
Add a new scalar function name IsTruthWithNull.
Check List
Tests
Code changes
Side effects
Related changes

LGTM


Add -static-libstdc++ on LINKFLAGS of aarch64

I would like -static-libstdc++ on LINKFLAGS for aarch64 to fix BIGTOP-3397 (packaging failure of Spark on CentOS 7(aarch64)).

I don't understand how the release artifacts are built yet. make linux-aarch64 did not work on my env. Let me know if I need additional fix.
make test passed on my env (CentOS 7(aarch64)) with the fix.
[info] Test run finished: 0 failed, 0 ignored, 8 total, 0.296s
[info] ScalaTest
[info] Run completed in 25 seconds, 125 milliseconds.
[info] Total number of tests run: 1
[info] Suites: completed 1, aborted 0
[info] Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0
[info] All tests passed.
[info] Passed: Total 126, Failed 0, Errors 0, Passed 125, Skipped 1
[success] Total time: 55 s, completed Sep 8, 2020 8:14:28 AM

Hi, nice to see you again @iwasakims san!
Embedding libstdc++ is already enabled for Intel architectures, so adding this for arm should be ok. Let me merge it.
For building snappy-java, basically running make native or make native-all is sufficient. You will need a docker installed on your machine. I haven't tried this command on arm machine, so I guess you need to use Intel machines for running these commands because they use x64 linux images.

Thanks, @xerial -san.

@xerial san, do you have a plan to release <IP_ADDRESS> shortly? We will appreciate if the released one rather than SNAPSHOT is available for the next release of Bigtop we are preparing for now.

@iwasakims A blocker is https://github.com/xerial/snappy-java/issues/257. Docker based build (using cross compilers provided by dockcross) suddenly stopped working so I can't build a new version right now.


Change font family to Circular Std

I have just updated all screens with a new font. I am going to check if we need a license for this font (paid).
Circular.zip

Since we aren't going with Circular Std, we should either confirm that we switch to another font or revert to Source Sans Pro. Refer to https://github.com/AlphaWallet/alpha-wallet-ios/issues/4741#issuecomment-1159621515

@justindg remember, no matter whether we ship with a new font (or revert to Source Sans Pro), we can't commit Circular to master on GitHub due to licensing.

@justindg let's revert/stick to Sources Sans Pro for now.

@justindg let's revert/stick to Sources Sans Pro for now.

This done yet?

@justindg let's revert/stick to Sources Sans Pro for now.

This done yet?

Yes it has been reverted long ako👌

Thanks!


Tags not loading

Tags don't get added to blocks or items unless all supported mods are loaded.
Need to either find a way to add conditions to these, or load tags another way

Maybe try separating the different mods into different sets of brackets, then add a line that says: "required": false
Example from the Elytra Slot Mod.
{   "replace": false,   "values": [     "minecraft:elytra",     {       "id": "silentgear:elytra",       "required": false     }   ] }
On a side note, I wonder if this is what causes the problem I'm having in Issue #28.


With a large range cidr, netscan got panic!

./netscan -d --proto tcp --port 8545 <IP_ADDRESS>/17
goroutine 44247 [runnable]:
context.WithDeadline.func2()
/usr/local/opt/go/libexec/src/context/context.go:387
created by time.goFunc
/usr/local/opt/go/libexec/src/time/sleep.go:170 +0x44

I think we need a worker pool

Patches welcome
On Jun 1, 2017 20:08, "yandd"<EMAIL_ADDRESS>wrote:

I think we need a worker pool
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jessfraz/netscan/issues/1#issuecomment-305677364, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABYNbCdOUgh8R5zy5uTeuc3dTgtu-hqCks5r_3yPgaJpZM4Ntxr8
.

closed by #3


Postgresql's FTS queries and function-based indexes are not supported

The following queries fails to parse:
SELECT to_tsvector('fat cats ate fat rats') @@ to_tsquery('fat & rat');

select * from mytable where (namets @@@ plainto_tsquery('english', 'word')) OR (name % 'another')
  ORDER BY similarity(name, 'blah') DESC

CREATE INDEX name ON table USING gist(column);

Indeed fts queries are not implemented within JSqlParser. As I never needed to use this ability from Postrgresql I am not familiar with it and what time to provide a first start for it. Pull requests are as always wellcome. It is a bit busy out here, so don't expect a quick implementation.


Pick files over system explorer

Files and folders shall be picked using the regular system explorer. Too achieve this, the library "file_picker" can be used.
If it works fine, the old library "filesystem_picker" can be removed

With 85afa58dc24cb943e50a328497813493b8ad50c4 I use file_picker at version 5.3.0
Here no dialog is shown altough I ran the command flutter config --enable-linux-desktop as descibed here.
Running the same app on Firefox, the file explorer opens properly.
Possible issues:

App does not have needed access rights to start Dolphin

Use method saveFile(). This can be used to select differ and existing or new file name. It does not actually save the file

With 85afa58 I use file_picker at version 5.3.0 Here no dialog is shown altough I ran the command flutter config --enable-linux-desktop as descibed here. Running the same app on Firefox, the file explorer opens properly.
Possible issues:
* App does not have needed access rights to start Dolphin

It perfectly works if flutter app is built manually and started from command line with default user or root. The issue must be somewhere in the VScode debugging session

With 85afa58 I use file_picker at version 5.3.0 Here no dialog is shown altough I ran the command flutter config --enable-linux-desktop as descibed here. Running the same app on Firefox, the file explorer opens properly.
Possible issues:
* App does not have needed access rights to start Dolphin

It perfectly works if flutter app is built manually and started from command line with default user or root. The issue must be somewhere in the VScode debugging session

The debug session is started under my user that has dolphin permissions

With 85afa58 I use file_picker at version 5.3.0 Here no dialog is shown altough I ran the command flutter config --enable-linux-desktop as descibed here. Running the same app on Firefox, the file explorer opens properly.
Possible issues:
* App does not have needed access rights to start Dolphin

Just run this command from bash to build and run the app without debugging:
flutter build linux --release && ./build/linux/x64/release/bundle/file_tree_hasher


Cannot  set store tool

HI
How can I set Elasticsearch as Store tool, and I can't find something in wiki

Have already solved
https://github.com/twintproject/twint/issues/1040


Kiali Dark Mode Theme

** Describe the change **

Set Kiali default theme according to operating system settings (https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-color-scheme)
Set colors with PF CSS variables that are compatible with dark mode
Replace hardcode color hex codes with PF variables

Now the context menu is reloaded on theme switching and it looks ok. Only thing that it is not changed is the background (white in light theme, gray in dark mode), but we would have to reload the whole cytoscape graph and I do not know if this is feasible from outside of the graph. Since both background colors does not interfere in the user experience and it could take lots of effort to know how to reload the graph from outside, I would skip it. What do you think @josunect?


Error performing a kitchen converge with test kitchen. Chef-client cookbook not respecting version pinning constraint

Cookbook version
[Version of the cookbook where you are encountering the issue]
7.0.0.
Chef-client version
[Version of chef-client in your environment]
11.18.12
Platform Details
[Operating system distribution and release version. Cloud provider if running in the cloud]
Using AWS and attempting to run test kitchen on mac OS sierra, version 10.12.1
Scenario:
[What you are trying to achieve and you can't?]
I'm trying to perform a kitchen converge using test kitchen and receive the following error:-
   Starting Chef Client, version 11.18.12
   Compiling Cookbooks...

   ================================================================================
   Recipe Compile Error in /tmp/kitchen/cookbooks/compat_resource/libraries/autoload.rb
   ================================================================================

   RuntimeError
   ------------
   This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade.

   Cookbook Trace:
   ---------------
     /tmp/kitchen/cookbooks/compat_resource/libraries/autoload.rb:2:in `<top (required)>'

   Relevant File Content:
   ----------------------
   /tmp/kitchen/cookbooks/compat_resource/libraries/autoload.rb:

     1:  unless Gem::Requirement.new(">= 12.0").satisfied_by?(Gem::Version.new(Chef::VERSION))
     2>>   raise "This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade."
     3:  end
     4:
     5:  # If users are on old verisons of ChefDK which activates an (old) gem via cheffish before this cookbook loads, then
     6:  # we just try to monkeypatch over the top of a monkeypatch.  Its possible that we have checks in this cookbook which
     7:  # will defeat that purpose and fail to monkeypatch on top of monkeypatches -- in which case those checks should be
     8:  # removed -- this cookbook needs to win when it gets into a fight with the old gem versions.
     9:  if Gem.loaded_specs["compat_resource"]
    10:    Chef.log_deprecation "using compat_resource as a gem is deprecated;  please update cheffish and chef-provisioning gems (or use the latest Chef/ChefDK packages) or else manually pin your compat_resource cookbook version to the same version as the gem you are using to remove this warning"
    11:  end

   Running handlers:
   [2016-11-10T17:17:40+00:00] ERROR: Running exception handlers
   Running handlers complete
   [2016-11-10T17:17:40+00:00] ERROR: Exception handlers complete
   [2016-11-10T17:17:40+00:00] FATAL: Stacktrace dumped to /tmp/kitchen/cache/chef-stacktrace.out
   Chef Client failed. 0 resources updated in 8.034320193 seconds
   [2016-11-10T17:17:40+00:00] ERROR: This resource is written with Chef 12.5 custom resources, and requires at least Chef 12.0 used with the compat_resource cookbook, it will not work with Chef 11.x clients, and those users must pin their cookbooks to older versions or upgrade.
   [2016-11-10T17:17:40+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)

#.kitchen.yml
driver:
name: ec2
...
require_chef_omnibus: 11.18.12
#Berksfile
source "https://supermarket.chef.io"
metadata
cookbook 'partial_search'
cookbook 'java'
cookbook 'nginx'
cookbook 'chef_handler'
cookbook 'chef-client', '~> 7.0.0'
cookbook 'apt'
cookbook 'filesystem'
#metadata.rb
...
depends 'java'
depends 'nginx'
depends 'partial_search'
depends 'chef_handler'
depends 'chef-client'
depends 'apt'
depends 'filesystem'
#Gemfile
source 'https://rubygems.org'
    gem 'berkshelf', '~> 4.0', '>= 4.0.1'
    gem "test-kitchen"
    gem "kitchen-vagrant"
    gem "kitchen-ec2"
    #gem "dep-selector-libgecode", '~> 1.0'
    gem "chef"

ruby version:
ruby 2.2.5p319
Steps to Reproduce:
[If you are filing an issue what are the things we need to do in order to repro your problem? How are you using this cookbook or any resources it includes?]
Expected Result:
[What are you expecting to happen as the consequence of above reproduction steps?]
I'm expecting to see a successful kitchen converge
Actual Result:
[What actually happens after the reproduction steps? Include the error output or a link to a gist if possible.]

This cookbook requires Chef 12 so you can't pin to 11 in Test Kitchen. You'll need to upgrade the chef-client daemon in your environment before using the latest releases of this cookbook.


Remove version: Kiwix.Wikivoyage version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

For moderators or/and anyone else

[!Caution]
As a result of several personal problems I've had over the last few months + my final exams coming up very soon, I'm currently unable to look at my GitHub notifications every day and maintain my executions correctly.
If you detect a certain problem on a certain pul request:

Either you can close the pull request directly without mentioning me.
Or you can send me a message on X (Twitter): @Exorcism0666

Thank you for your understanding, and I'm sorry if some pull requests can't be approved due to the situation I'm in.

This account is automated by Github Actions and the source code was created by CoolPlayLin. If you have any questions about any pull request, don't hesitate to ping Exorcism0666.

[!warning]
With the new version of Komac, numerous Pull Requests may contain bugs or unwanted elements. If such issues arise, please tag russellbanks so that these bugs can be addressed in future updates.

[!important]
Please carefully review these Pull Request before merging. If it is a Pull Request for removing incorrect content and the URLs are issue, free upon manual checking, please close this Pull Request directly. (It is best to inform Exorcism0666 of the closure.)

良い一日をお過ごしください！

URL: https://github.com/kiwix/kiwix-js-pwa/releases/download/v3.3.6-Wikivoyage/Wikivoyage-by-Kiwix-3.3.6-E.appx
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 913)


Fix static files issue on Toolforge

Static files not loading on Toolforge due to which swagger docs and DRF browsable APIs are loading HTML only.

also add api docs to root url

closed with #39 #40 #41