Add Wolfmax4 and MejorTorrent

I am testing the private version of Comet in ElfHosted, to my surprise the Proxy option is separate so I would have to pay 9€ + 9€ = 18€ to use this functionality.
I am considering to take both options to share it with my family, but to do so I need Comet to give good results in Spanish and try to eliminate the Latin options. I have seen that Comet has the Torrentio scraper, it really solves the problem with Spanish, but after several tests I see that despite using Torrentio it does not use the Wolfmax4 and MejorTorrent libraries.
I would like to propose you to add them and so I will choose Comer privado as my only addon.
Thank you.

Representing ElfHosted here.. If you had a private Comet, you could pick which indexers you wanted to use, if you supplied your own Jackett. However, that'd end up as 9€ + 9€ + 9€ = 27€ :(
As an alternative.. there's a community Comet ("cometa"?) being worked on by Hayduk, and once the MediaFlow proxy is supported by comet, you'll be able to use a public comet instance with a private MediaFlow instance for ProxyStreaming (so total 9€)


[Bug] Steam Proton games default back to the old xcursor

Describe the bug
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:

Add programs.steam.enable = true; to /etc/nixos/configuration.nix
Rebuild NixOS
Set up steam and its games
Run a game using steam proton experimental
You see that the older xcursor is used instead of the desktop default, only happens in Steam Proton games.

Expected behavior
The default DE cursor is used for Proton
Screenshots

Additional context

I am using this on an NVIDIA system. Same thing happens for both XOrg and Wayland

This also happens using the steam runtime as well

Notify maintainers

This could be due to XCURSOR_PATH not being usable with the pressure-vessel env; NixOS, not using the standard paths, is probably causing pressure-vessel to not mount them in.
What's XCURSOR_PATH set to? Can you enter a pressure-vessel shell and look at it there too, and see if the paths are mounted in?

output of $XCURSOR_PATH
/home/homeuser/.icons:/home/homeuser/.local/share/icons:/home/homeuser/.local/share/flatpak/exports/share/icons:/home/homeuser/.local/share/flatpak/exports/share/pixmaps:/var/lib/flatpak/exports/share/icons:/var/lib/flatpak/exports/share/pixmaps:/home/homeuser/.nix-profile/share/icons:/home/homeuser/.nix-profile/share/pixmaps:/etc/profiles/per-user/homeuser/share/icons:/etc/profiles/per-user/homeuser/share/pixmaps:/nix/var/nix/profiles/default/share/icons:/nix/var/nix/profiles/default/share/pixmaps:/run/current-system/sw/share/icons:/run/current-system/sw/share/pixmaps

How do you even get into a pressure vessel shell? What is pressure vessel anyways too?

Pressure-vessel is essentially a dedicated bubblewrap wrapper (like flatpak) for Steam. It's where the Steam runtime runs.
Do NOT use ~/.icons or ~/.fonts; if you are, use the ~/.local/share paths instead. Just having the legacy paths installed can be VERY messy.
My best guess is that pressure-vessel isn't mounting in the appropriate paths; maybe check their docs: https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/pressure-vessel.md#assumptions

I have no idea what to do even after reading the page from the link you sent me

Can confirm this also affects me as an AMD user.

Your GPU doesn't matter; it's a pressure-vessel problem, which appears to be fixed (or attempted to be fixed) in a later version.

So who's end is it on, Valve's or Nix's package maintainers?

This seems to be fixed.

(Taken on Plasma Wayland)


Tuned regex which are used for parsing GC.com #2

simplified code
fixed not working patterns, e.g. members
added additional test data and test cases
prepartion for issue #559

Upps, the rebase+push deleted the comment from @samueltardieu ! Sorry !
@samueltardieu:

TODOs removed
javadoc adjusted
extra issue(s) will follow

One point is still open:
"Rather than use a "GC" prefix, it would probably be better to use a "cgeo.geocaching.gccom" package to put GC.com specific stuff."
It's a good idea but should be part of an extra issue, too. We should invent subclasses of Cache (implements ICache) like GCCache and OCCache and Challenge. Where'd you put those classes ? And shouldn't we ask the implementations of IConnector for a specific patter ? BTW: GCConnector can be found in the package cgeo.geocaching.connector ,-)

Calling trim() does not alleviate the need for creating a new String if we do not want to share the same storage area in getMatch(). Please re-add it until we come to a conclusion about #654.

Re-added.

Can you tell me why you didn't remove the lines with the fromHtml() calls, but instead commented them out? To me that looks like you aren't sure whether that code is needed or not.
And to answer that question: The fromHtml calls are necessary. They convert HTML entities like "ä" to the normal characters representing those entities. As we only output some fields as HTML (for performance and layout reasons) all other fields shouldn't contain HTML after parsing anymore. Please re-add those calls.

I'm merging manually...


WebSocket interface is not responding

Hello BlueAndi. Thank you for this very great project.
I have put together a simple 8x32 display using an esp32 devkit4.
Works wonderfully.
Now I am trying to control the Pixelix via websockets using node-red.
I am able to use the ws://echo.websocket.org as a test and I am able to connect from node-red.
However when I try connecting to the pixelix (ws://<IP_ADDRESS>/ws) I am not getting through.
I have searched the code but I am unable to understand what is going wrong.
Do you have any hints or additional information that might guide me forward?
Thank you - PabluskiNC

Thank you – that was my issue – I did try adding the auth but I got the @ and the : flipped - oops.
Have a wonderful day,
PabluskiNC
From: Andreas Merkle<EMAIL_ADDRESS>Sent: Saturday, December 19, 2020 9:04 AM
To: BlueAndi/esp-rgb-led-matrix<EMAIL_ADDRESS>Cc: PabluskiNC<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [BlueAndi/esp-rgb-led-matrix] WebSocket interface is not responding (#18)
Hi PabluskiNC,
thanks, nice to hear that you like it.
Did you consider the websocket authentication?
Use as URL<EMAIL_ADDRESS>You may replace user:password above with your configuration.
Note, the websocket supports only service stuff right now, the plugins itself spawn only REST APIs.
Bests
BlueAndi
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/BlueAndi/esp-rgb-led-matrix/issues/18#issuecomment-748479023 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AA7NHRQZIAMWKPH57OVFIJ3SVSXGXANCNFSM4VB6XNTA .  https://github.com/notifications/beacon/AA7NHRUK3XYZNVH7MWFDK4TSVSXGXA5CNFSM4VB6XNTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFSOOELY.gif


How do I set the color of the animation?

This isnt issue, but I cant find to how to change the color of animation.
If this feature doesn't exist yet, maybe it can be used as a feature request. Thanks

Hey @sed1ka you can customize the animation effect and its properties like follows
Skeletonizer(
    enabled: _enabled,
    effect: ShimmerEffect(
      baseColor:  myBaseColor,
      highlightColor:  myHighlightColor,
    ),
    child:  ...
  )

or if you want to create your own gradient
Skeletonizer(
    enabled: _enabled,
    effect: ShimmerEffect.raw(
      colors: [],
      stops: []
    ),
    child: ...
)


Versioned Query Continuation Token

Versioned Query Continuation Token
Description
This PR adds support for versioning the Pipeline Query Continuation token. For now we will support 3 versions:

V0 - Version before we started versioning ({"asdf": "asdf"})
V1 - First version of continuation tokens ({"Version":"1.0","SourceContinuationToken":"{\"asdf\": \"asdf\"}"})
V1.1 - Continuation Tokens with QueryPlan ({"Version":"1.1","QueryPlan":null,"SourceContinuationToken":"{\"asdf\": \"asdf\"}"})

The main class has support for parsing any of the continuation tokens. It also has code to convert to the latest version of the token. This means that if a user has a query with continuation token from the future we can throw a nice error message. If the token comes from the past we can convert it to the latest and run the query.
Type of change
Please delete options that are not relevant.

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

V0 is Array of CompositeContinuationToken -> [ {CompositeToken}+]
N & N + 1 support story means, we can only ship V1+ only in V4 (V3 is already out and will be a breaking change).
One more options is to make it a choice which client chooses. Client < V3 chooses V0, and nwer versions can choose later versions.


dont ask for more points than possible from kdtree

@s-good in our recent data run, I see a grand total of zero flags raised by AOML climatology. Digging in a bit, it seems that nearest_indices in util/AOMLinterpolation.py is using scipy's kdtree to ask for the 100 closest lat/long points from a pre-determined lattice closest to the profile's position, but there's no protection to make sure there are actually at least 100 points in the lattice to return. Ask for more neighbors than the lattice has, and kdtree just returns a bunch of infs (see example below). Also, why 100? It seems to only take the closest 1.
This PR forces a sensible return from kdtree, and only asks for the nearest neighbor.
Minimum example of bad behavior in kdtree:
import numpy as np
from scipy.spatial import cKDTree

ll = [[0,0],[0,0.5],[0,1],[0.5,0],[0.5,0.5],[0.5,1.0],[1.0,0],[1.0,0.5],[1.0,1.0]]
tree = cKDTree(ll)

print tree.query([0.5,0.5], 9)
print tree.query([0.5,0.5], 10)

I have our full data run database with AOML_climatology re-calculated based on these changes; if the changes look good, I'll make it available through S3, let me know.


CableCar Plugin: use response Content-Type to determine whether to perform CableReady operations

Status

Needs Review

Related Issue(s)
Additional Notes
This PR makes some adjustments to the CableCar plugin to have it use response Content-Type as the determining factor of whether to run CableReady operations. The MIME type defaults to the CR-specific application/vnd.cable-ready.json but can be changed by the configuration parameter we introduced yesterday.
This allows the client to request CableCar data from the server programatically using mrujs.fetch without registering a separate listener.
I did find that when using a custom content type, fetchResponse.isJson and fetchResponse.responseJson weren't working correctly, so I've switched to using fetchResponse.responseText.  I thought you fixed that last week but maybe there's another issue?  Thanks for fixing in main!
Note that the server must be able to respond with the correct content-type.  @leastbad and I were discussing this yesterday and it sounds like a dedicated cable_ready content type is a good idea.  It's a one-line change to have CableReady do that and I'm about to submit the PR for that as well.  I'll post the url in the comments below.
Finally, if you want to see how this all fits together, I developed it against my cable_modal proof of concept.  There's a demo branch up here.  Making these changes allows that code to focus on it's own domain and offload all operation fetching and processing to the mrujs cablecar plugin.

CableReady PR for registering the MIME type is here https://github.com/stimulusreflex/cable_ready/pull/140

here's an example of how @leastbad 's CableCar example gist would change with this modification
https://gist.github.com/existentialmutt/296f9745b17383c4549d286dc2d386dd

@existentialmutt the json issue shouldve been fixed here:
https://github.com/ParamagicDev/mrujs/blob/668991ac3b47047d3c8af18d437c823cb7174ea6/src/http/fetchResponse.ts#L79

@existentialmutt the json issue shouldve been fixed here:
https://github.com/ParamagicDev/mrujs/blob/668991ac3b47047d3c8af18d437c823cb7174ea6/src/http/fetchResponse.ts#L79

yeah that should do it.  Thanks for the pointer I'll dig around and see if I can find out why it doesn't like that.

@ParamagicDev fix in main worked great.  Back to using responseJson

Hey, forgive the drive-by code review...
respond_to do |format|
  format.cable_ready do
    render operations: cable_car.console_log(message: "Destroy #{params[:id]}!")
  end
end

<
render operations: cable_car.console_log(message: "Destroy #{params[:id]}!")

By which I mean... I'm all for options, but please don't make the respond_to block structure mandatory. So much ceremony!

@leastbad That's a fair point.  I think this approach may require some kind of format indication but I'm going to look into what our options are.

@leastbad we could make respond_to blocks optional by setting the Content Type as part of render operations:
https://github.com/stimulusreflex/cable_ready/pull/140/commits/c981d8b8d521d13849bc1035f5dcca313278a215

Cooool! I can't be the one to approve it (because again, not my wheelhouse) but LGTM. You should convert that to a PR.

I think that my fundamental hope/wish was that render operations: cable_car would be application/json unless someone also uses a respond_to block, which would set it to cable_ready. I don't know if that works! This area isn't my forte.

Fair enough @leastbad!  Yes, I'm suggesting we change the default Content Type for cablecar to application/vnd.cable-ready.json and I realize that's not a small ask.
I'm advocating this approach because Content Type is one of the few CORS/CSP approved signals a request can use to indicate a specific purpose.  This allows the mrujs cablecar plugin, cable_modal, and other general purpose utilities built around cable_car to register global event handlers on document that won't step on other json requests that could be on a complex page.
I realize this adds something to think about for anyone who wants to use cablecar with json content type and be done.  My hope is that by making application/vnd.cable-ready.json the default it should be pretty unobtrusive. Everything works as it did before, there's just a different Content Type on the response now.  If your client-side code doesn't look at response Content Type nothing needs to change (btw mrujs is smart enough to recognize application/vnd.cable-ready.json as a JSON content type so it's parsing helpers are still available)
It's also entirely possible I have an XY problem going on here and this isn't the best solution. The specific thing I'm trying to achieve is to allow the mrujs cablecar plugin to register a CableReady.perform event handler that clearly differentiates cablecar requests from other json without having those requests be tied to a specific DOM element.  I'm game for other solutions.
Finally, I'm very much on board with the idea of "CableReady, the Format" as something that can be easily ported to other languages and frameworks. I think establishing a dedicated MIME type for CableReady signals reliability and maturity on that front.  I'm also hearing there's a desire for application/json and I want to better understand where that comes from so we can make a solution that covers as many bases as possible.

Really appreciate the explainer. I'm still parsing.
I am fine with switching MIME types on the client. It seems that it would be effectively transparent to users of, say, an updated mrujs, right?
Lower level, if I'm doing a fetch call do I have to specify an Accepts header in this scheme?
On the server, I understand that we can just set the new default MIME type in the renderer for operations, which I already saw and again, I'm fine with - it seems transparent.
What I'm trying to avoid is a scenario where someone has to use the respond_to block structure in order for all of this to work - increasing the line count and cognitive complexity of sending CableReady JSON from one line to 4-5.
Hopefully, I'm just asking [another] naive question and fretting over nothing...?

So theoretically we could do what Turbo does. Turbo has their Turbo Stream mime type. So what they do under the head is add prepend it to the accept header.
If you image the Accept header usually looks like this:
{Accept: "application/html"}
With this line of code here:
https://github.com/hotwired/turbo/blob/a47e5b62646fcf4e285dbc7308e91c752aec7369/src/core/drive/form_submission.ts#L123
It goes from the above to this:
{Accept: "turbo/stream.mime, application/html"}

This means that Turbo stream responses take precendence over HTML. We could do something similar here.
Mrujs' default mime type is: "/"
We could make it: "text/cablecar.json, /" which means if the server has both CableReady and HTML views for a route, itll prioritize the cableready response with a respond_to block.

I might actually be more confused, now... sorry! I thought that maybe if I read this again, later, I'd get it. 🤦
My goal is keeping the API short and easy to use on both the client and the server. Right now, I can use fetch to request a path, and in my controller I have a 1-liner that can return a CableReady compliant JSON string that on the client, I can interpret as JSON and pass directly to CableReady. It's simple, requires no extra code, and it works great, today.
I am frustrated that we're discussing taking something that is both simple and already working, adding more complexity to it... to achieve the same fundamental outcome.
Rafe said:

I realize this adds something to think about for anyone who wants to use cablecar with json content type and be done. My hope is that by making application/vnd.cable-ready.json the default it should be pretty unobtrusive.

This is the simplest fetch GET call that works today:
fetch('/foo')
  .then(r => r.json())
  .then(CableReady.perform)

Does that have to change? If the answer is yes, then we should go back to the drawing board.
Adding optional things to the above will always be 100% fine, but fundamentally fetching JSON and feeding it to CableReady should always be this simple. In fact, this conversation makes me want to go into my Webpacker plugins and create a global function called json...
function json(data) { return data.json() }

... just so that I can...
fetch('/foo')
  .then(json)
  .then(CableReady.perform)

Moving on to the server side... thanks to the custom renderer, we can reply to our fetch request with a 1-line controller action:
render operations: cable_car.blah

I'm now going to cut-and-paste myself without shame:

Does that have to change? If the answer is yes, then we should go back to the drawing board. Adding optional things to the above will always be 100% fine, but fundamentally fetching JSON and feeding it to CableReady should always be this simple.

What do I mean by optional things? For starters, I actually don't think I care about the MIME type so long as it doesn't change the fetch call. If you want to change the MIME type because it advances the cause, I'll let you folks sort that out so long as you don't have to add headers to every fetch call until the end of time.
Another optional thing is this cable_ready format:
respond_to do |format|
  format.cable_ready do
    render operations: cable_car.blah
  end
end

Again, this looks like it could be really useful! Just... don't make this the only way to return CableReady JSON. So long as the render operations: cable_car.blah syntax still works without having to think about MIME types, I'm excited that you folks are pushing things forwards.
Heck, you could even introduce a second renderer helper, if that solves any problems:
respond_to do |format|
  format.cable_ready do
    render cable_ready: cable_car.blah
  end
end

That seems like it could make a lot of good sense, semantically. If you render operations, you get a string that can be parsed as JSON that shows up with standard application/json, but if you render cable_ready, you get a magical string that can be parsed as JSON that shows up as application/vnd.cable-ready.json or whatever it was that Rafe proposed earlier. (LGTM!)
Now, it's possible that I'm just cranky and regurgitating good ideas y'all have already said and we are in violent agreement and I'm embarrassing myself. In fact, I hope that some version of that is true. I'm fine with it, if it means that we ultimately get to keep things simple for the users. 💙

@leastbad So let me pull this back.
Lets say I have /foo I have app/views/foo/index.html.erb but I want the cableready JSON response for that instead.
Today, you would have to do this to make this happen:
mrujs.fetch('/foo', { headers: "application/json" })
  .then(response => response.json())
  .then(CableReady.perform)

Really at the end of this day this is to fix if I have 3 conflicting routes:
foo.json
foo.html
foo.cable_ready

I need some way to seperate a jbuilder json response from a cableready json response.
I could even have views that look like this:
foo.json.jbuilder
foo.html.erb
foo.cable_ready.erb

And based on the Accept header will auto send back the one I want.
God this is so confused to explain...

Okay, but it's important to differentiate that mrujs.fetch != fetch.
Right now, I can fetch exactly as I described, without needing to set an Accept header.

Let me back up, assuming you have a the following:
if you have two views (a JSON and an HTML view) on the route, the HTML will always be sent back without an Accept header to make the JSON take precedence over HTML.

Okay, I think I'm all clear, here, finally.
I left a note on https://github.com/stimulusreflex/cable_ready/pull/140 that I have since retracted.
I now understand that you only ever need to use a respond_to block if you have more than one MIME type available at a given route.

Appreciate the spirited discussion guys!
@leastbad thank you for clarifying where you stand.  The "ain't broke, don't fix it" approach makes perfect sense and I appreciate you hanging in here for a feature whose benefits aren't exactly obvious.
I want to be sure of the behavior too and I've been running some tests tonight with various combinations of Accept Headers set on the request and Content Types set on the response.  The good news is almost every combination works and will render CableReady operations!

What you're looking at is running through the matrix of request/Accept Headers X methods of setting response content_type:
The different Accept headers are:

Default ("/")
application/json
application/vnd.cable_ready.json
application/vnd.cable_ready.json, application/json
Extra-simple GET fetch (@leastbad I threw in the exact method you described above just to be sure)

The methods of setting response content type are:

Default Content Type: nothing special, just render: operations
Set Response Content Type: call response.content_type = Mime[:cable_ready] in the controller before rendering
Use Respond To Block: use a respond_to {|format| format.cable_ready {... block in the controller

As you can see, the only combination that refuses to execute cableready operations is when you specifically request json but tell the controller to only render cable_ready with a respond_to block.  That one failing to perform actually makes sense to me, and it's encouraging that everything else allows the operations to go through!
Also encouraging is that I tried switching back and forth between mrujs fetch and vanilla fetch and they have identical results.
Code is here if you want to review: https://github.com/existentialmutt/cablecar_mime_test
In general what I'm taking away from this is that browsers and Rails are both pretty forgiving around matching MIME types.

You rock, Rafe! This is high-quality rigor, not that you needed to endear yourself further.
My major conceptual stumbling block is something Konnor managed to finally break up after over a decade of blissful ignorance: none of this particularly matters unless you're serving different response types. Since I almost always use standalone routes for Ajax calls, I've just never had a proper 💡 moment with this mechanism.
Now, I see... and I suspect it would be hard to un-see. 👁

Haha, awesome! This has been educational for me as well


Port 465 (no SSL) supported?

Hi,
Jist one short question to your great Library:
Is Port 465 without SSL supported?
Best wishes
Daniel

465 is SSL port for SMTP server.


Fix typos in tractusx-connector helm chart

Thanks @florianrusch-zf! Will merge this asap and update the corresponding release page.


Add: Niraj

Description
Added myself to the contributors list.
Checklist

[x] I have read and followed the Contribution Guidelines.
[x] All new and existing tests passed.
[x] I have updated the documentation to reflect the changes I've made.
[x] My code follows the code style of this project.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

Changes made are per suggested. Thank you!

@btrezzy You have make changes on this PR. You have opened a new PR.

@btrezzy Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


Update rust-toolchain.toml

Many thanks for your efforts :)

@BurtonQin Sorry this was a WIP :).
The complete changes are here https://github.com/BurtonQin/lockbud/pull/60


Custom Hex Block Colors

This would be low-priority since it's just for fun, but since you're rewriting the parser, would it be possible to allow hex values for block colors in the following format?
block name :: #00f

Really easily. Thanks!

Example: pink! All the pink
when flag clicked
say [Hello there!] :: #ff4fc3
move (10) steps ::  #ff4fc3
forever :: #ff4fc3
stamp  :: #ff4fc3


Windows and macOS testing capabilities should not be at Randy's house

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
We've recognized long-term that the current test runners being located at Randy's house is not optimal or in-line with our goal of having the project decrease dependence on Randy.
We are fine with Linux testing, using GitHub's graciously provided GitHub Actions, but we haven't been successful with either macOS or Windows/WSL testing elsewhere.
Exceptions:

MacStadium has provided a mac M1 that works great and is properly managed. It's possible that in the future we could have more there (we probably need 3 more macOS ARM64 machines). (At current costs, about $100/month/machine, this would be cost-prohibitive with our current budget)
@seeben has provided a Windows machine that is currently deployed for WSL2 testing. Those machines cost about $42/month, and in some configurations can support more than one test at the same time.

Describe your solution
Options include:

macOS: Pay the money to MacStadium or similar vendor. This would be at least $300/month, a lot given our budget
GitHub is supposed to start providing macOS ARM64 machines this year to open-source projects, and with greater memory capacity than in the past. It's possible that our macOS testing, or at least testing for some permutations, could land in GitHub again. (In the past, we had Colima testing there, but it was abysmally slow and unreliable.)
Moving Windows testing to hetzner or another similar provider might work (Hetzner is where @seeben's provided Windows test runner is). In most cases we've tried, the lack of support (or good support) for nested virtualization has kept us from success. (It's been a few years since we tried Azure windows instances, it's worth looking at that again.
appveyor has Windows and macOS instances that just might work. It's been a long time since we checked in with htem.
Microsoft's Azure might work for Windows

Describe alternatives
Suggestions are welcome!
Additional context
No response

According to https://docs.github.com/en/actions/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#standard-github-hosted-runners-for-public-repositories windows and macos are both available for free for public repos in GitHub Actions.

We used their macOS for a year or two for Colima. It was incomprehensibly slow and unreliable. (They are promising bigger machines and arm64 later this year though, right now they have only amd64, which is essentially obsolete as far as users go.)
We have attempted Windows on several services like Github Actions, and in general because they don't have a UI and don't support nested virtualization (WSL2 and Docker) they have failed.


feat: fix coordinator cron exit issue

Purpose or design rationale of this PR
Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?
Fix when cron exit, but still some goroutine don't exit
t=2024-04-21T23:30:27+0800 lvl=eror msg="get unassigned session info failure"  error="ProverTask.GetAssignedProverTasks error:failed to connect to `host=localhost user=postgres database=test_db`: failed to receive message (unexpected EOF)"
t=2024-04-21T23:30:27+0800 lvl=eror msg="get unassigned session info failure"  error="ProverTask.GetAssignedProverTasks error:failed to connect to `host=localhost user=postgres database=test_db`: failed to receive message (unexpected EOF)"
t=2024-04-21T23:30:28+0800 lvl=eror msg="get unassigned session info failure"  error="ProverTask.GetAssignedProverTasks error:failed to connect to `host=localhost user=postgres database=test_db`: failed to receive message (unexpected EOF)"
t=2024-04-21T23:30:28+0800 lvl=eror msg="get unassigned session info failure"  error="ProverTask.GetAssignedProverTasks error:failed to connect to `host=localhost user=postgres database=test_db`: failed to receive message (unexpected EOF)"

PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[ ] build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
[ ] ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
[ ] docs: Documentation-only changes
[ ] feat: A new feature
[x] fix: A bug fix
[ ] perf: A code change that improves performance
[ ] refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
[ ] style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] test: Adding missing tests or correcting existing tests

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[x] No, this PR doesn't involve a new deployment, git tag, docker image tag
[ ] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change
[ ] Yes

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 56.11%. Comparing base (53cf265) to head (02a45fc).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #1286   +/-   ##
========================================
  Coverage    56.11%   56.11%
========================================
  Files          156      156
  Lines        12131    12131
========================================
  Hits          6807     6807
  Misses        4798     4798
  Partials       526      526

Flag
Coverage Δ

coordinator
19.93% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Error setting composition resource status field

What happened?
I want to provide values to custom composition resource status fields, similar to how patch and transform do it using ToCompositeFieldPath.  I am defining extra properties on my CompositeResourceDefinition's status property and attempting to set the property value using the below code:
_dxr = option("params").dxr
_dxr.status.myExtraProp = "sample"

However, the function fails to compile complaining of an UndefinedType:
    Message:               cannot compose resources: pipeline step "normal" returned a fatal result: failed to run kcl function pipelines: failed to compile the kcl package
EvaluationError
failed to update the dict. An iterable of key-value pairs was expected, but got UndefinedType. Check if the syntax for updating the dictionary with the attribute 'myExtraProp' is correct

How can we reproduce it?
Define a custom status property called myprop in xrd and attempt to set its value on dxr.status.myprop.
What environment did it happen in?
Function version: xpkg.upbound.io/crossplane-contrib/function-kcl:v0.3.4

Maybe the status is Undefined. I think you can do this:`
_dxr = option("params").dxr
_dxr = _dxr | {status.myExtraProp = "sample"}

It doesn't error at least :-) but no status properties other than the usual "conditions" property are shown.

Do you mean to set the status to take effect in the cluster? Currently, option("params") is readonly.

Just for clarity, a crossplane native way of what I mean is described here.  The "secondResource" in that example is what I am trying to set from the function.

Make sense. Thank you! Would you consider combining patch function with kcl function, or would I integrate the functionality of patch function into kcl function and use kcl to describe it uniformly

I'd much prefer if it were possible with kcl function entirely.  I have no intention of using patch and transform moving ahead as I'd prefer to encapsulate all resource code into one kcl function package for a given composition.  Using more than one function containing resource-aware logic seems like it will introduce friction for maintenance imo.

KCL function can already do an equivalent of P&T's MR field path mapping, and composite field to MR field.  This pseudo field-to-composite status mapping completes the set.

Thank you, in response to your recent needs and issues, I will design and implement it recently.

Thank you! I will pay attention to this point when designing and consider the use of crossplane and other functions of crossplane at the same time.

Hello @markphillips100 I've tried this composition resource and set XR status. Is this what you want?
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: function-template-go
spec:
  compositeTypeRef:
    apiVersion: example.crossplane.io/v1
    kind: XR
  mode: Pipeline
  pipeline:
  - step: normal1
    functionRef:
      name: kcl-function
    input:
      apiVersion: krm.kcl.dev/v1alpha1
      kind: KCLRun
      metadata:
        name: basic1
      spec:
        target: XR # Note set 'XR' here
        source: |
          {
              **option("params").dxr
              status.atProvider.bala = "cc"
          }

I assume target: XR is necessary in your example, whereas I would be using target: Resources?  I need to be able to set the value from within the same function package else I would be leaking knowledge of a specific resource to a separate function just to set a property on the composite.
To clarify, I don't want the composition yaml to know anything except which resources package to use hence need the required functionality available to the Resources target if possible.

Thank you! Make sense.

Wonderful.  Do you wish me to try the PR or wait for next release?  Assumes I can access a PR build of course :-)

When the PR is merged, you can try the next release v0.4.0. Of course, if possible, could you also help me review the example and code to prevent any misunderstandings in my understanding of your description. ❤

I have tried your example locally and it is working.
However, in my case, I am struggling to achieve something that works perfectly when using standard composition with patch sets and resources.
patches:
    - type: ToCompositeFieldPath
      fromFieldPath: "status.atProvider.arn"
      toFieldPath: "spec.status.arn"
    - type: ToCompositeFieldPath
      fromFieldPath: "status.atProvider.id"
      toFieldPath: "spec.status.id"

From my perspective this should be still simple to achieve with KCL function(s), but at least in my case, it is not.
I would love to see an example covering only such case, where XR status field is updated by some atProviderdata once MR is provisioned. Like in example given, from status.atProvider to composite field.

@zargor composite status properties can now be set using the Default target.  See here for an example.  And you can read any resource's atProvider property using ocds["<resource-name>"].Resource.status.atProvider.myProp.
I notice in your patches example you are writing to a spec.status property.  I'm pretty sure status on a composite is a sibling to spec rather than a child property so just use status.id.  I don't believe spec can be written to.

@markphillips100 I can confirm it works when testing locally, using beta render. However, in k8s cluster this does not work. What happens is that MR is never created and Status block of XR is not presented at all.
So this kind of tweak will spoil provisioning of the resource:
dxr = {
    **oxr
    status.id = "cool-status"
}

Would like to hear how to set it up to work in a real k8s cluster, not only using local test tools.

I hate to say it, but it works for me in a k8 cluster. Are you definitely using the Default target? It's the only target that implements the feature (I think).
Maybe @Peefy can comment more?

Thank you! @markphillips100
Hello @zargor , could you give me with more configuration information for KCLRun resources? So that I can replicate it in the cluster. The implementation of this function is referenced from the Crossplane Go template function, and I confirm that there should be no problem.

First I wanna thank you both for your efforts.
Next is I had to be sure whether this works in some realistic enviroment since I did not have any issues with local testing but in cluster.
This is basically what I try to do with https://marketplace.upbound.io/providers/upbound/provider-aws-dynamodb/v1.3.1/resources/dynamodb.aws.upbound.io/Table/v1beta1 :

dynamodb pipeline based composition
create Table resource and I have some logic therefore going for KCL
provide some status back to XR possibly in addition to status conditions

    # inserts from pipeline
    - step: xrd-parameters-mapping
      functionRef:
        name: kcl-function
      input:
        apiVersion: krm.kcl.dev/v1alpha1
        kind: KCLRun
        metadata:
          name: basic
        spec:
          target: Resources
          source: |
            oxr = option("params").oxr

            name = oxr.metadata.name
            labels = oxr.metadata.labels or {}
            annotations = oxr.metadata.annotations or {}

            # ...

            table = {
                apiVersion = "dynamodb.aws.upbound.io/v1beta1"
                kind = "Table"
                metadata.name = name
                metadata.labels = labels
                metadata.annotations = annotations
                spec.forProvider = {
                    attribute = attribute
                    billingMode = billingMode
                    region = region
                    streamEnabled = streamEnabled
               # ...
            }

            items = [table]

    - step: readiness
      functionRef:
        name: function-auto-ready

    - step: resource-status
       functionRef:
         name: kcl-function
       input:
         apiVersion: krm.kcl.dev/v1alpha1
         kind: KCLRun
         metadata:
           name: basic
         spec:
           target: XR
           source: |
             {
                 status.is_ok = True
             }

Would be awesome to learn also about target set eligible in terms of KCLRun.

I think I got it finally. It is not only about one issue.
This example is fine but in my case I did not realise the target field to patch has to be defined in XRD in the first place.
Otherwise the pipeline just does nothing, not expressing any reason/event/status why is not successful.
Secondly, if one wants to patch XR with ocds["<resource-name>"].Resource.status.atProvider.myProp this will not work, at least as long as there is no such resource provisioned/available at the time.
Meaning that the resource(s) must be created, so to be able to reach out to atProvider set.
Now the question is, how we can manage to do it in patch XR step, like to have the pipeline smart enough to wait for provisioning to complete. Is this anyhow addressed anywhere? Or differently, do we need a completely separate composition just to be able to set some status properties back to XR?
The most interesting thing is that XR status patching works like a charm when using function-patch-and-transform withing a pipeline.

I don't use the XR target for patching the composite status. I do mine in
the Default target function along with the creation of the resources. The
function will execute many times during each reconciliation loop so
eventually the ocds will contain resources with their arProvider data set
and any assignment to composite status will be resolved accordingly. This
is how normal patch and transform function works too
On Fri, 12 Apr 2024, 10:37 pm Goran, @.***> wrote:

I think I got it finally. It is not only about one issue.
This example
https://github.com/crossplane-contrib/function-kcl/blob/5f3c6c08d6a9f5ec760a1c026f327d4cedfc8d8a/examples/xr/patching/xr.yaml#L5
is fine but in my case I did not realise the target field to patch has to
be defined in XRD in the first place.
Otherwise the pipeline just does nothing, not expressing any
reason/event/status why is not successful.
Secondly, if one wants to patch XR with
ocds[""].Resource.status.atProvider.myProp this will not
work, at least as long as there is no such resource provisioned/available
at the time.
Meaning that the resource(s) must be created, so to be able to reach out
to atProvider set.
Now the question is, how we can manage to do it in patch XR step, like to
have the pipeline smart enough to wait for provisioning to complete. Is
this anyhow addressed anywhere? Or differently, do we need a completely
separate composition just to be able to set some status properties back to
XR?
The most interesting thing is that XR status patching works like a charm
when using function-patch-and-transform withing a pipeline.
—
Reply to this email directly, view it on GitHub
https://github.com/crossplane-contrib/function-kcl/issues/60#issuecomment-2051681355,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPTGNLKBV32P3G2FXZTEP3Y47IQZAVCNFSM6AAAAABFSV2TQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJRGY4DCMZVGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@markphillips100 that is very good information. Would be great to share some brief snippet around that.

@zargor I do all my kcl function compositions using oci packages so don't have an inline example off hand but I'll add the relevant bits here.
You are correct in that any property you want to surface on the XR needs to be defined on the XRD.  In this example we are surfacing myProp both as a status property on the XR and as a printed column.  In addition, we've added the property to the composite's secret.
apiVersion: apiextensions.crossplane.io/v1
kind: CompositeResourceDefinition
metadata:
  name: mycomposites.example.com
spec:
  group: example.com
  names:
    kind: MyComposite
    plural: mycomposites
  claimNames:
    kind: MyClaim
    plural: myclaims
  connectionSecretKeys:
# Add list of props to be surfaced by composite secret - NOTE: this is separate to surfacing properties on the XR.
    - myProp
  versions:
  - name: v1alpha1
    served: true
    referenceable: true
    schema:
      openAPIV3Schema:
        type: object
        properties:
          spec:
            type: object
            properties:
              id:
                type: string
                description: ID of this composite that other objects can refer.
              parameters:
                type: object
                description: Parameters used to customize the cluster
                properties:
                  inputA:
                    description: A description.
                    type: string
            required:
              - id
              - parameters
# This is required in order to surface properties on the XR.
          status:
            type: object
            properties:
              myProp:
                description: The myProp of my resource.
                type: string
# Surface some of XR's properties so user sees them when executing: kubectl get mycomposite
    additionalPrinterColumns:
    - name: myProp
      type: string
      jsonPath: ".status.myProp"

The composition should only need a single kcl function with target "Default" to create resources, set the composite secret data, and also the XR status property.  You will need to follow this up with function-auto-ready function in order to have the XR ready status be resolved.
I haven't executed this code so just take it as guidance please:
apiVersion: apiextensions.crossplane.io/v1
kind: Composition
metadata:
  name: my-composite
spec:
  compositeTypeRef:
    apiVersion: example.com/v1alpha1
    kind: MyComposite
  writeConnectionSecretsToNamespace: crossplane-system
  mode: Pipeline
  pipeline:
  - step: normal
    functionRef:
      name: kcl-function
    input:
      apiVersion: krm.kcl.dev/v1alpha1
      kind: KCLRun
      metadata:
        name: basic
      spec:
# Note: this can be omitted and Default will be used.
# Do not use "Resources" as this does not support the features we need.
        target: Default
        source: |
            import base64

            oxr = option("params").oxr

            name = oxr.metadata.name
            labels = oxr.metadata.labels or {}
            annotations = oxr.metadata.annotations or {}

            # ...

            table = {
                apiVersion = "dynamodb.aws.upbound.io/v1beta1"
                kind = "Table"
                metadata.name = name
                metadata.labels = labels
                metadata.annotations = annotations
                spec.forProvider = {
                    attribute = attribute
                    billingMode = billingMode
                    region = region
                    streamEnabled = streamEnabled
               # ...
            }

            # We must use a null referencing syntax as the resource will not exist in ocds on first pass,
            # and highly unlikely any atProvider data is provided for a while too.
            # We presume this code will execute many times and
            # eventually atProvider will contain the data we want to surface.

            # This code assumes "name" is the name given to the metadata.name property of the table resource, and
            # there will eventually be a property called "myProp" on the table resource's atProvider data.

            # Get myProp data.
            tableResource = option("params").ocds[name]?.Resource
            myProp = tableResource?.status?.atProvider?.myProp or ""

            # Apply myProp data to the desired XR.
            # NOTE: It's important to include the **oxr else kcl will not know this object is to update the XR.
            dxr = {
                **oxr
                 # We are setting the value always to either its final value or "".
                 # We could use a condition as used below in the details.
                status.myProp = myProp
            }

            # As a bonus, let's add myProp to the composite's secret.
            details = {
                apiVersion: "meta.krm.kcl.dev/v1alpha1"
                kind: "CompositeConnectionDetails"
                if myProp != "":
                    data: {
                        myProp = base64.encode(myProp)
                    }
                else:
                    data: {}
            }

            # Finally we must return not only our resources to be created but also the details and dxr.
            items = [table, details, dxr]

  - step: automatically-detect-ready-composed-resources
    functionRef:
      name: function-auto-ready

Hope that helps.

Closed by #61


Time signature: 6/8 example please

How to author a time signature 6/8 music please?
Take this Silent Night, Holy Night for example, would you give an example how to do it in jianpu-ly please @ssb22? thanks.

Take this Silent Night, Holy Night for example

title= Silent Night, Holy Night
arranger= F. Gruber

%arranger= Copyright Â© 2005 by Douglas D. Anderson
%arranger= Released to the Public Domain

6/8
%% tempo: 4=55
1=C

q5. ( s6 ) q5  c3.  | q5. ( s6 ) q5  c3.   | c2'  s2'. ( d7  ) c7. |
c1'  s1'. ( d5  ) c5.  | c6  q6  q1'. ( s7 ) q6  | q5.  s6  q5  c3.  |
c6  q6  q1'.  s7  q6  | q5.  s6  q5  c3.  | c2'  q2'  q4'.  s2'  q7  |
c1'. (  c3'. ) | q1' ( q5 ) q3  q5.  s4  q2  | c1. (  c1. )
L: Si-_ lent night! Ho-_ ly night! All is_ calm, all is_ bright. Round yon Vir-_ gin Mo- ther and Child. Ho- ly In- fant, so ten- der and mild. Sleep in heav- en ly peace,_ Sleep_ in heav- en ly peace._


SUGGESTION: Module for RDF2VEC.

It might be interesting to see if there is a Weaviate module opportunity for RDF2VEC. Especially because the Weaviate schema is RDF-inspired.
Somewhat related: #1522

CC: @heikopaulheim

The major requirement for a vectorizer module is that it can independently assign a vector to each object (or a node). E.g. in the case of the transformers module if I have two sentences "My name is John" and "Jane likes ice cream", the vectorizer sees each object in isolation and can assign a vector to each.
If this is something that works with rdf2vec then it it's a great fit for a module. (I don't know - as I haven't looked into rdf2vec thoroughly yet). If, on the other hand, the entire complete graph is the input for the rdf2vec and the output is all vectors at once then it wouldn't be compatible with the "vectorize [individually] at import time" philosophy of Weaviate modules.
Having said that it would still work well with Weaviate natively, just not through a module. In this case the process would be:

Take the entire graph
Vectorize it outside of Weaviate, so that each node gets a vector
Import each node with the vector positions into Weaviate without a vectorizer module

In this case a good place to make the process easier for the user might be the python client?

Thanks for the writeup @etiennedi

If this is something that works with rdf2vec then it's a great fit for a module.

This would be the case, isn't it @HeikoPaulheim?

It's more of the second case. RDF2vec takes an entire RDF graph and outputs vectors for each node.

It's more of the second case. RDF2vec takes an entire RDF graph and outputs vectors for each node.

Interesting, in principle this should fit but maybe not as a module.
I'll come back to this, thanks Heiko!

I also have a question related to RDF2vec:
in the 2nd case you described, if vectorization is done outside Weaviate for RDF data and then we use Weaviate vectorizer for some other type of data, would they still be compatible? or does it mean that RDF vecs cannot be used in conjunction with internal Weaviate vec?!

Not directly I guess. Embeddings created using different methods are
inherently incompatible.
However, there are quite a few approaches for learning mapping functions
between embedding spaces.
Am 05.05.2021 um 14:43 schrieb Ali Khalili:

I also have a question related to RDF2vec:
in the 2nd case you described, if vectorization is done outside
Weaviate for RDF data and then we use Weaviate vectorizer for some
other type of data, would they still be compatible? or does it mean
that RDF vecs cannot be used in conjunction with internal Weaviate vec?!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/semi-technologies/weaviate/issues/1529#issuecomment-832656652,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA3XPPCM3TRW4PPS57WLFMTTME4QXANCNFSM42SWQRSQ.

--
Prof. Dr. Heiko Paulheim
Data and Web Science Group
University of Mannheim
Phone: +49<PHONE_NUMBER>
B6, 26, Room B0.22
D-68159 Mannheim
Mail: @.***
Web: www.heikopaulheim.com

Well - in principle it should be possible. You could have Weaviate classes that represent the data and the RDF vectors and Weaviate classes that use -for example- a text vectorizer.
It's a bit abstract but a test setup should be doable.

To avoid confiusion, we need to distinguish two separate cases here:
Case 1: Single Weaviate - linked classes
This is the approach that @Bob describes. You'd have multiple Classes in Weaviate. Each class can have it's own vector space. They need not be compatible. Essentially you'd import your dataset twice, once with Text-Vectors, once with RDF-Vectors. You can then make graph-relations between the two classes. Note: These relations are not your regular edges that you already have in your dataset, these are additional cross-class edges which link the node in space 1 to the equivalent node in space 2. So whenever you do a vector search in one space, you can follow the link to the other vector space and perform a second search around the linked object. We also use this approach when linking images to text when we are using separate vectorizers for each.
Case 2: Single Weviate - single Vector Space
This is the approach that @HeikoPaulheim describes. You have two separate vector spaces, then you train a mapping function to combine them into as single vector space (So far all of this has happened outside of Weaviate). Once you have a single model you can import it as a whole into Weaviate.


Some of the tests are failing in Flutter 3.16.0 and newer versions

Bug report
Describe the bug
Just wanted to inform you that some of the tests are failing in Flutter 3.16.0 and newer versions.
Steps to reproduce
Steps to reproduce the behavior:

Use Flutter 3.16.0 or newer version.
Run tests.
Some of the tests fail.

Expected behavior
Tests should all pass.

Additional context
In Flutter 3.16.0, the ThemeData.useMaterial3 flag is true by default, which seems to possible be the root cause.
By changing the useMaterial3 boolean, tests would fail when true & succeed when false

wolt_modal_sheet.dart

Thanks for the report! Do you mind fixing the tests with a PR?

Oh actually, this PR by @mhadaily is fixing it: https://github.com/woltapp/wolt_modal_sheet/pull/315
I guess :)

Sorry for late reply!
Okay, no need then 😄


Token filters - pattern_capture [DOC]

What do you want to do?

[ ] Request a change to existing documentation
[x] Add new documentation
[ ] Report a technical problem with the documentation
[ ] Other

Create a separate page for Token filter: pattern_capture
Part of META issue: https://github.com/opensearch-project/documentation-website/issues/1483
*Version: all

@vagimeli I can take this one


Bump baseVersionForMinCompat to 2.0.0-rc.3.0.0

bumping the baseVersionForMinCompat with an intentional failure to double check summarizeIncrementally tests are really running on the pipeline. The failure will be removed once we test it once.

Expected failures in pipeline https://dev.azure.com/fluidframework/public/_build/results?buildId=248284&view=logs&j=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3&t=ddd9efee-bc1d-59c0-82a9-543538b126ce&l=4679 doble confirming tests suite using minCompat will run. Now removing the intentional error.


Get config from env vars if no config.json

It is more convenient in a docker context to use env vars...

@carlos-jenkins Can we get some eyes on this one?


Additional feature toggles

I think two sets of feature toggles are useful. One to specify if we should send to Soknadsmottaker/Soknadsfillager at all, and one to specify if we are to send to the real endpoint or the test endpoint.

If both are false, we send through Henvendelse, the old way.
If SEND_TO_SOKNADSFILLAGER is true but USE_REAL_ENDPOINT_IN_SOKNADSFILLAGER is false, we send through Henvendelse, the old way. We also send the new way, but to the test endpoints. This way, we can test connection and OAuth, without actually sending anything. If Exceptions happen, they will be caught and the user will have their Soknad sent in via Henvendelse still.
If both are true, then we send the new way and no longer send via Henvendelse.

Jeg klarer ikke å se behovet for dette.


Standardized Toggle Component

Toggle component is defined in the style guide
Just by looking at the colors/contrast, it is not clear if it is in on or off.
Updates to the toggle design were made:

A new updated toggle design helps to clarify if the feature is on or off.

closing stale issue. A style guide/system is being reviewed and updated


Incorrect types on pattern optional, oneOrMore, zeroOrMore

As discussed here: https://github.com/adlnet/xapi-profiles/issues/250
This lib can probably be updated before that, as the intention is clear

Fixed for project-pan in ea035b1f54f7317cc2b302e7ff196b999010f350, though adlnet/xapi-profiles#250 will remain open for now.


Warning when running examples

This issue is related to openjournals/joss-reviews#2685
When running an example I see the following warning printout:
> python -m de_sim.examples.phold 8 0.5 100
/.../homebrew/opt/python@3.8/bin/../Frameworks/Python.framework/Versions/3.8/lib/python3.8/codecs.py:905: RuntimeWarning: line buffering (buffering=1) isn't supported in binary mode, the default buffer size will be used
  file = builtins.open(filename, mode, buffering)

Thanks for notifying us. The warning is generated by a logging package that's outside our control. I have disabled the warning notification by ignoring it in a lower code layer.
Regards
Arthur


ML/Statistics/Graph tools now match EU's

@natefoo I created a new Pr for this (closed the previous PR). Should be easier to diff.

@galaxybot test this

It looks like the conda dependency solver never returned from:
/cvmfs/test.galaxyproject.org/deps/_conda/bin/conda create -y --quiet --override-channels --channel iuc --channel conda-forge --channel bioconda --channel defaults --name<EMAIL_ADDRESS>intervene=0.6.4

What might be causing this?

The conda dependency solver is just not great - I will try this by hand and see if I can get it to install.

I installed Mamba and it solved it pretty much instantly. Not sure why conda didn't but we can try again now.

@galaxybot test this

@galaxybot deploy this

That's odd... grasping at straws here but that node logged a memory and a SMART (disk) error so I'll try again to see if we get the same outcome on a different node.

@galaxybot deploy this

That's odd... grasping at straws here but that node logged a memory and a SMART (disk) error so I'll try again to see if we get the same outcome on a different node.

Hopefully, it will work this time.

+ rsync -ah -e 'ssh -o ControlPath=/home/jenkins/.cache/usegalaxy-tools/ssh-tunnel-g2test-cvmfs0-psu1.galaxyproject.org.sock' --stats /var/jenkins/workspace/usegalaxy-tools/776/upper/ g2test@cvmfs0-psu1.galaxyproject.org:/cvmfs/test.galaxyproject.org
rsync: write failed on "/cvmfs/test.galaxyproject.org/deps/_conda/envs/mulled-v1-793d37f5b41078fdff8ee6ba1788ec2515f80ab5cdb9dc909cf4528538c6e5f9/libexec/gcc/x86_64-conda-linux-gnu/7.5.0/cc1": No space left on device (28)
rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.2]

Ran out of space on the Stratum 1 server - this will take a bit to sort out.

Hopefully just due to the size of the CVMFS client cache, which I've cleaned up - this is a large amount of data though, we may have to split up the PR a bit more if we can't get this to work.

@galaxybot deploy this

Hopefully just due to the size of the CVMFS client cache, which I've cleaned up - this is a large amount of data though, we may have to split up the PR a bit more if we can't get this to work.

Sure. Hopefully, it gets deployed this time.

@kxk302 let's try each section separately for now.

@kxk302 let's try each section separately for now. Sorry this is causing so much trouble.

No worries @natefoo
Are you suggesting 3 separate PRs, one for ML, one for statistics, and one for graph?

Yep

@natefoo,
Created the following 3 separate PRs for ML/stats/graph section changes.
https://github.com/galaxyproject/usegalaxy-tools/pull/348
https://github.com/galaxyproject/usegalaxy-tools/pull/349
https://github.com/galaxyproject/usegalaxy-tools/pull/350
Closing this PR.


Baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions

Follow https://github.com/opensearch-project/.github/issues/125 to baseline MAINTAINERS, CODEOWNERS, and external collaborator permissions.
Close this issue when:

MAINTAINERS.md has the correct list of project maintainers.
CODEOWNERS exists and has the correct list of aliases.
Repo permissions only contain individual aliases as collaborators with maintain rights, admin, and triage teams.
All other teams are removed from repo permissions.

If this repo's permissions was already baselined, please confirm the above when closing this issue.

@dblock Regarding point 3 and 4 above, I don't think i have access for these

Closing now. Please reopen anything is pending from our side.

Permissions are incorrect. Please work with @bbarani's team to remove the group that has maintain rights, and add individuals with maintain access.

Baselined the maintainers and CODEOWNERS is green now. Closing this issue.

Verified, thx.


Update README to improve deps config

Pointing to the Hex package in deps and compiling results in this error:

$ mix deps.compile nerves_neopixel
==> nerves_neopixel
Unchecked dependencies for environment prod:
* elixir_make (Hex package)
  the dependency is not locked (run "mix deps.get" to generate "mix.lock" file)
could not compile dependency :nerves_neopixel, "mix compile" failed. You can recompile this dependency with "mix deps.compile nerves_neopixel", update it with "mix deps.update nerves_neopixel" or clean it with "mix deps.clean nerves_neopixel"

The GregMefford/nerves_neopixel repository is configured with a submodule for jgarff/rpi_ws281x. This makes compilation of nerves_neopixel from github fail without the submodules flag in deps/0.

This PR updates the README to recommend a happy path to resolution.

Thanks for taking the time to figure this out and create a PR! :rocket:
I thought I included all the source files in the Hex package so that it would be able to download and build locally. Did you try just updating the version to 0.3.0 without specifying the github and submodules options? Or is the problem that you want to be able to download the GitHub version, but the submodules option is needed to make that work.
Ideally, I'd like to distribute through Hex and not GitHub to be more standard, but I'm glad you found a way to make it work if that doesn't pan out.

I've released v0.3.1 of nerves_neopixel and it appears to all be working well now from the Hex package. Let me know if you're still having trouble with it! 🚀


documentation errors and unclarities

nowhere in the documentation you can see the groupID and artifactID of the plugin. It would be handy to add it to https://lexemmens.github.io/podman-maven-plugin/docs/index.html

https://lexemmens.github.io/podman-maven-plugin/docs/goals/build.html#buildconfig shows there is a <skipBuild> option under <build>. But this is not true. Maven will stop with config error. However, you can add it directly under <configuration>. Idem for other options, but not all. It is unclear from the documentation which ones are ok and which ones not.
For the other goals, it is also not clear that you can specify the options under <configuration> section.

there is no description or example how to use labels.

name cannot have a tag in it, but there are options for the name like %t, %v that are typically used in a tag, not in a name. (and they are not working for the <tags> attribute). Clarify this (or feature request: add these variables to the tags too)

I second that, especially (4). Or is there any other way to set the tags attribute with some variable (preferrably the version of the POM)?
Also, configuration > images > image > build > pull is not being recognized as tag: "Cannot find 'pull' in class nl.lexemmens.podman.config.image.single.SingleImageBuildConfiguration" (I'm using version 1.19.0 of the plugin).


Rename and remove items before open sourcing

Closing in favor of https://github.com/massgov/mayflower-artifacts/commit/b6b624b025e2c9c25c6bfdbf196e3e95caca55b2


404

document get 404

yes- sadly i did this late yesterday while working on our first version of a website- i filed an issue here: #357. should be fixed soon!


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/kn-plugin-operator-approvers
/assign knative-sandbox/kn-plugin-operator-approvers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/hack 128cf01...813559c:
  > 813559c [pre-1.0] Use the TAG unmodified when publishing dot releases (# 119)
  > 9f34905 Update community files (# 118)
  > 69a2295 Update community files (# 117)

/lgtm
/approve


sourceMappingURL is set to absolute path of local source map

The source maps cannot be displayed by the browser dev tools since the source map urls are absolute paths to the local resources. There should be a way to specify relative paths to the location of the source maps so that a web server can serve these.
I get this:
//# sourceMappingURL=/Users/<user>/project/dist/index.js
But want this:
//# sourceMappingURL=dist/index.js
Here are my configs:
13:06 $ cat .languagebabel
{
	"projectRoot": true,
	"babelMapsAddUrl": true,
	"babelSourcePath": "src",
	"babelTranspilePath": "dist",
	"babelMapsPath": "dist",
	"transpileOnSave": true,
	"createTranspiledCode": true,
	"createMap": true
}

15:26 $ cat .babelrc
{
	"presets": [
		["env", {
			"targets": {
				"chrome": "40",
				"ie": "11"
			}
		}]
	]
}

Can you try 2.81.1 and let me know how it goes.

Amazing @gandm. That works! Thanks for the speedy fix.


There is no proper error message when invalid project is passed in "-j"

There is no validation done for project name passed in "-j" option.

When using an invalid value for "-j" option in run command it gets stuck:

% acorn run -n sandemo3  -j acorn.io/xxx/acorn1 .
INFO[0004] Waiting for builder to start

When using an invalid value for "-j" option when creating resources , there is no indication that it failed

sangeethahariharan@sangeethas-mbp examples %  acorn secret create --data  key-name=value -j acorn.io/xx/acorn1 mytest1
mytest1

Error messages appear when invalid project is passed for -j flag. But it mentions that the namespace is not found.
 % acorn run -n myfirstapp -j newproj .
  ✗  ERROR:  namespaces "newproj" not found

acorn secret create --data  key-name=value -j newproj  mytest1
  ✗  ERROR:  namespaces "newproj" not found

Expected behavior would be to mention that project is not found.

When invalid value is passed for -p option for  list commands and exec/log commands , user is presented with resource not found error message.
Example error message:
acorn exec newtest2a.nginx-bc9d5d98-6tnn4 -j test3
  ✗  ERROR:  appinstances.internal.acorn.io "newtest2a" not found

@cjellick @ibuildthecloud Wanted to confirm that this should be the expected behavior in this case and that there is no need for any project validation in this case ?

That is fine for this case. not found is the right response.
Woudl be nice to address this one:
acorn secret create --data  key-name=value -j newproj  mytest1
  ✗  ERROR:  namespaces "newproj" not found

I'm going to move this out. i dont consider that the use of namespace vs project critical

Tested with acorn version -acorn version v0.5.1-65-ge8a480d5+e8a480d5
Proper error message about project not being found is reported when invalid project is passed in "-j" option to acorn commands
 % acorn run -n sandemo3  -j mynew .
  ✗  ERROR:  projects.api.acorn.io "mynew" not found

% acorn secret create -j mynew --data  key-name=value mysecret
  ✗  ERROR:  projects.api.acorn.io "mynew" not found

%  acorn secrets -j mynew
  ✗  ERROR:  projects.api.acorn.io "mynew" not found

 %  acorn volumes -j mynew
  ✗  ERROR:  projects.api.acorn.io "mynew" not found

 % acorn images -j mynew
  ✗  ERROR:  projects.api.acorn.io "mynew" not found


Update on Party Logos

I've done this so that the max-width and max-height SCSS rule can be removed on avatars.
Also, I slightly improve some of the parties positioning.
Here is how it looks like:
Live version:

https://d.pr/i/lrQIAa

Branch version:

https://d.pr/i/0p93GY

closing to deploy


Update Maven-Wrapper to use Maven 3.6.x in order to allow mvn --no-transfer-progress

Using the option mvn --no-transfer-progress will reduce clutter from Travis CI log output.

Closed with c9fc76eff8f4267cd174b5a4dd47f0ac3291713d.


Can't run wechaty with error log

Please run npm run doctor and paste the output here
Wechaty Doctor

Wechaty version: #git[93d1728 doc]
Darwin x64 version 15.6.0 memory 146/4096 MB
Docker: false

Expected behavior
run wechaty
Actual behavior
can't run wechaty on my mac, but can run wechaty on digital ocean
the error log as follows:

VERB Wechaty contructor()
VERB Wechaty on(scan, function)
VERB Wechaty on(logout, function)
VERB Wechaty on(error, function)
VERB Wechaty on(login, function)
VERB Wechaty on(room-join, function)
VERB Wechaty on(room-leave, function)
VERB Wechaty on(room-topic, function)
VERB Wechaty on(message, function)
INFO Wechaty v#git[93d1728 doc] initializing...
VERB Wechaty puppet: web
VERB Wechaty head: chrome
VERB Wechaty profile: demo.wechaty.json
VERB Wechaty uuid: 53108ef9-2d2e-4326-ae18-e28bd9792e7e
VERB Puppet targetState(dead)
VERB Puppet currentState(dead)
VERB PuppetWeb init() with head:chrome, profile:demo.wechaty.json
VERB Puppet targetState(live)
VERB Puppet currentState(birthing)
VERB UtilLib getPort(18788)
VERB UtilLib getPort(18788) return: 18853
VERB PuppetWeb init() getPort 18853
VERB PuppetWeb initServer()
VERB PuppetWebServer init() on port 18853
VERB PuppetWebServer createHttpsServer() listen on port 18853
VERB PuppetWebServer init()-ed
VERB PuppetWeb initServer() done
VERB PuppetWeb initBrowser()
VERB PuppetWebBrowser constructor() with head(chrome) sessionFile(demo.wechaty.json)
VERB PuppetWebBrowser targetState(close)
VERB PuppetWebBrowser currentState(close)
VERB PuppetWebBrowserCookie constructor(Browser, demo.wechaty.json)
VERB PuppetWebBrowser targetState(open)
VERB PuppetWebBrowser currentState(opening)
VERB PuppetWebBrowser initDriver() for head: chrome
VERB PuppetWebBrowser getChromeDriver()
VERB PuppetWebBrowser driver(Driver)
VERB PuppetWebBrowser open(https://wx.qq.com/zh_CN/htmledition/v2/images/webwxgeticon.jpg)
VERB PuppetWebBrowserCookie loadSession() from demo.wechaty.json
SILL PuppetWebBrowserCookie addCookies({"domain":".wx.qq.com","expiry":1477418987,"httpOnly":false,"name":"wxloadtime","path":"/","secure":false,"value":"1477375787"})
SILL PuppetWebBrowserCookie addCookies({"domain":".wx.qq.com","expiry":1477418987,"httpOnly":false,"name":"wxsid","path":"/","secure":false,"value":"4FGtPc3H2t6Zjaec"})
SILL PuppetWebBrowserCookie addCookies({"domain":".wx.qq.com","expiry":1477418987,"httpOnly":false,"name":"wxuin","path":"/","secure":false,"value":"891575575"})
SILL PuppetWebBrowserCookie addCookies({"domain":".qq.com","expiry":2147385600,"httpOnly":false,"name":"pgv_pvi","path":"/","secure":false,"value":"9225103360"})
SILL PuppetWebBrowserCookie addCookies({"domain":".wx.qq.com","expiry":1792239143,"httpOnly":false,"name":"webwxuvid","path":"/","secure":false,"value":"389a7ed41c7b9fa88205a69eff706fa7c493c8e056775cee761d67f1da927bab366cceb7b7c6a060c8dde76b81c36c0f"})
SILL PuppetWebBrowserCookie addCookies({"domain":".qq.com","expiry":1477418987,"httpOnly":false,"name":"webwx_data_ticket","path":"/","secure":false,"value":"gSfhB0Zxd6tRcLz0OwotwKIP"})
SILL PuppetWebBrowserCookie addCookies({"domain":".wx.qq.com","expiry":1477418987,"httpOnly":false,"name":"mm_lang","path":"/","secure":false,"value":"zh_CN"})
SILL PuppetWebBrowserCookie addCookies({"domain":".qq.com","httpOnly":false,"name":"pgv_si","path":"/","secure":false,"value":"s3690461184"})
VERB PuppetWebBrowserCookie loaded session(8 cookies) from demo.wechaty.json
VERB PuppetWebBrowser open(https://wx.qq.com)
VERB PuppetWebBrowser currentState(open)
VERB PuppetWeb initBrowser() done
VERB PuppetWeb initBridge()
VERB PuppetWebBridge new Bridge({puppet: PuppetWeb, port: 18853})
VERB PuppetWebBridge init()
VERB PuppetWebBridge inject()
SILL PuppetWebBrowser Browser.execute("injectioReturnValue = /** * * Wechaty - Wechat for Bot, and human who talk to  ... ")
SILL PuppetWebBridge inject() eval(Wechaty) return code[200] message[WechatyBro Inject Succ] port[18853]
SILL PuppetWebBrowser Browser.execute("return typeof WechatyBro === "undefined"")
SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
SILL PuppetWebBridge inject() Wechaty.init() return code[200] message[WechatyBro Init Succ on port: 18853] port[18853]
SILL PuppetWebBrowser Browser.execute("return typeof WechatyBro === "undefined"")
SILL PuppetWebBrowser Browser.execute(" const callback = arguments[arguments.length - 1] const isAsync = (typeof  ... ")
SILL PuppetWebBridge inject() ding success
VERB PuppetWeb initBridge() done
SILL PuppetWebWatchdog onFeed: 120000, HEARTBEAT:[inited]
SILL PuppetWebWatchdog clearWatchDogTimer() nothing to clear
SILL PuppetWebWatchdog setWatchDogTimer(120000, HEARTBEAT:[inited])
SILL PuppetWebWatchdog monitorScan(HEARTBEAT)
SILL PuppetWebWatchdog autoSaveSession()
SILL PuppetWebWatchdog memoryCheck() free: 602 MB, require: 64 MB
VERB PuppetWeb init() done
VERB Puppet currentState(live)

VERB PuppetWebWatchdog watchDogReset() timeout 120000
INFO Bot error: Error: watchdog reset after 120 seconds, last feed:[HEARTBEAT:[inited]]
VERB PuppetWebEvent onBrowserDead(watchdog reset after 120 seconds, last feed:[HEARTBEAT:[inited]])
SILL PuppetWebWatchdog onFeed: 180000, HEARTBEAT:[onBrowserDead() set a timeout of 180 seconds to prevent unknown state change]
SILL PuppetWebWatchdog clearWatchDogTimer() [0] seconds left
SILL PuppetWebWatchdog setWatchDogTimer(180000, HEARTBEAT:[onBrowserDead() set a timeout of 180 seconds to prevent unknown state change])
SILL PuppetWebWatchdog monitorScan(HEARTBEAT)
SILL PuppetWebWatchdog autoSaveSession()
SILL PuppetWebWatchdog memoryCheck() free: 297 MB, require: 64 MB
VERB PuppetWebBrowser quit()
VERB PuppetWebBrowser currentState(closing)
SILL PuppetWebBrowser quit() driver.close()-ed
SILL PuppetWebBrowser quit() driver.quit()-ed
VERB PuppetWebBrowser driver(null)
SILL PuppetWebBrowser quit() this.driver = null
SILL PuppetWebBrowser clean() retryPromise: attempt 1 time for timeout 45000
SILL PuppetWebBrowser getBrowserPids()
SILL PuppetWebBrowser getBrowserPids() child: {"PPID":"38740","PID":"38745","STAT":"S+","COMM":"node"}
SILL PuppetWebBrowser getBrowserPids() child: {"PPID":"38745","PID":"38746","STAT":"S+","COMM":"/Users/lijiarui/git/wechaty/node_modules/chromedriver/lib/chromedriver/chromedriver"}
SILL PuppetWebBrowser getBrowserPids() child: {"PPID":"38740","PID":"38771","STAT":"R+","COMM":"ps"}
VERB PuppetWebBrowser clean() retryPromise() resolved
VERB PuppetWebBrowser currentState(close)
VERB PuppetWebEvent onBrowserDead() browser quit-ed

Steps to reproduce the behavior (and fixes, if any)

could you run it 3 times, and confirm whether this problem will occour every time?
because an issue has a meaning only when it can be reproduced.

I had run it more than 10 times, I had tired deleted session .json file,  change the network, close several programs to free memory, and restart my laptop...
All failed when I was at the company...
I felt so sad, so I go back home . When  I just run it, it works!
I hope you can find the reason if you have time, thanks!

you must provide the simplest code that can reproduce the problem in order to diagnose it.
if the problem you mentioned is not reproduceable, then i can not be helpful. sorry.


feat: ModelProvider banner on pages if user isn't configured

https://github.com/user-attachments/assets/808d877c-e568-4fd3-9676-37addeb227c3

model provider banner if user isn't configured with a model provider
Note: Requires merge of https://github.com/otto8-ai/otto8/pull/774 first

Will be making some changes for banner and overall model/model providers based on discussion with Craig, Will, & Donnie. Closing this PR


App Proxy Invalid proxy signature.

Invalid proxy signature.
I am getting Invalid proxy signature. error on using app proxy
here is my ajax:
$.ajax({
url:"https://sneakersurgeapp.test/proxy",
type: "GET"
}).done(function(data) {
console.log(data);
});
here is my app proxy setting

here is my route
Route::get('/proxy', [
'uses' => 'App\Http\Controllers\CollectionProductsController@getCollectionProducts',
'as' => 'proxy.test'
])->middleware(['cors','auth.proxy']) ;
please help

You wouldn't send a AJAX request to proxy. Proxy is used to display a page on the Shopify store. It will verify the request came from Shopify and then display your view.

I am sending ajax from frontstore to laravel app.. isnt this possible?
my app url: https://sneakersurgeapp.test

So if /proxy is the route you use to display your view on the store... then you'd need to make another route to handle your AJAX requests.
/proxy => validates request from Shopify, displays your view on the shop
Make a new route /proxy/something, where you can send your AJAX requests to there, without the auth.proxy middleware.

I am unable to understand please look
Laravel:
App URL : https://sneakersurgeapp.test
Route I have create : https://sneakersurgeapp.test/proxy
Route::get('/proxy', [
'uses' => 'App\Http\Controllers\CollectionProductsController@getCollectionProducts',
'as' => 'proxy.test'
])->middleware(['cors','auth.proxy']) ;

Shopify
Store URL: https://sshk-store.myshopify.com/
Proxy : https://sshk-store.myshopify.com/apps/proxy
my ajax
$.ajax({
url:"https://sneakersurgeapp.test/proxy",
type: "GET"
}).done(function(data) {
console.log(data);
});

please correct my where I am wrong I will be really thankful

You dont send an AJAX request to your proxy URL.
Proxy page is for validation of the request from Shopify, and if validated, it will send back a view to Shopify.
I'm not sure you're understanding what proxy pages do. This is not a package issue from what I see, please move to discussions tab for help :)


Refactor waitForVolumeStatus to be generic

What this PR does / why we need it:
This PR refactors waitForVolumeStatusAvailable to be more generic.
Could be reused in other places as well.
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

NONE

/cc @jichenjc

/lgtm

/approve


Accept ownyourswarm content

I need to accept ownyourswarm content and format it correctly.

This is now working, pending some security checks 👍

done! Working on posting to micropub branch until go live.


community: CrateDB: Document Loader

About

Description: Document Loader adapter for CrateDB.
Coming from: https://github.com/crate-workbench/langchain/pull/1
Documentation: GH-27713
Addressed to: @eyurtsev, @kneth

References

Followup from: https://github.com/langchain-ai/langchain/pull/18281
Related to: https://github.com/langchain-ai/langchain/pull/27696

Remarks
Most of the ingredients of this patch have been contributed through GH-18281 already. What's inside here is what was left on https://github.com/crate-workbench/langchain/pull/1. Please advise if you think this patch is still applicable, and/or which fragments of it.

see #27710


About Keras Siamese network performance

Hello guys,
I am trying to use Siamese network to learn the similarity.
I tried mnist_siamese_graph.py on Github . After training, the accuracy on training set and on test set are very low and unstable as well.
Is the performance normal for Siamese network? Or do I misunderstand the low accuracy?
I am new in Siamese network, and sorry for asking basic questions. if anyone can explain it, I'll very appreciate it!
Thank you very much! :-)

Accuracy is not a particularly meaningful metric given the formulation of the problem and the loss function chosen, if you consider that the optimization goal is to get the siamese network to output 0 for matching pairs and high values for non-matching pairs.

@Juliachang See this issue: https://github.com/fchollet/keras/issues/4980

Actually we can get test accuracy of 99.5% by reverting the commit: 7f25a77.

@bstriner Thank you very much!! Problem fixed! :-)


Using Narrator in scan mode can crash the app when there is an invisible hyperlink in a TextBlock

Describe the bug
When a TextBlock contains a Hyperlink and there is not enough space to display this Hyperlink, using Narrator in scan mode and navigating to this element, the app will crash.
Like this:
    <StackPanel HorizontalAlignment="Center" VerticalAlignment="Center">
        <Button Content="Justin" />
        <TextBlock
            Width="200"
            Height="50"
            TextWrapping="Wrap">
            <Hyperlink NavigateUri="https://www.baidu.com/">Hello world</Hyperlink>
            <Run>Hello world wwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww</Run>
            <Hyperlink NavigateUri="https://www.baidu.com/">Hello world</Hyperlink>
        </TextBlock>
        <Button Content="Rudy" />
    </StackPanel>

I have created a demo repo to show this bug: https://github.com/h82258652/NarratorTextBlockBugDemo
Steps to reproduce the bug

Launch Narrator.
Enter scan mode.
Navigate to the TextBlock element.

Expected behavior
The app should not crash.
Screenshots
I record a video for this bug.
https://user-images.githubusercontent.com/5144550/177262857-63ba508b-8a7e-481e-a7eb-855a0acabb5c.mp4
NuGet package version
No response
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000, Windows 10 (21H2): Build 19044
Additional context
No response

:tada:Microsoft.WindowsAppSDK.1.2.221109.1 has been released which fixes this issue.
Handy links:

Release Notes
Official Nuget Release

cc: @JJBrychell


Crash when configuring configurable valve

The mod Configurable Valves (0.1.3) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event configurable-valves::configurable-valves-switch (ID 203)
__configurable-valves__/scripts/configuration.lua:49: attempt to concatenate local 'valve_type' (a nil value)
stack traceback:
	__configurable-valves__/scripts/configuration.lua:49: in function 'next_type'
	__configurable-valves__/scripts/shortcuts.lua:23: in function 'quick_toggle'
	__configurable-valves__/scripts/shortcuts.lua:53: in function 'handler'
	__core__/lualib/event_handler.lua:47: in function <__core__/lualib/event_handler.lua:45>

Above error occurs when changing the valve type with Ctrl+R
Not sure if it matters, but I've set the enable/disable based on an inventory value.

Urgh. There's was nothing wrong in the code. It was code checking that everything's correct that caused a bug.
Thanks for the report!


VictoryLine onLoad animation doesn't work

Hi,
if I use animate on VictoryLine the component disappear.
animate={{   onLoad: {     duration: 3000,   } }}
My versions are:
"react-native-svg": "^6.3.1",
"victory-native": "^0.17.3"

@cotorusso94 Unfortunately changes in<EMAIL_ADDRESS>were breaking for VictoryNative. We haven't yet updated victory native to be compatible with these breaking changes. I will make this more prominent in the README, but for now, please use "victory-native": "^0.17.3" with "react-native-svg": "^6.1.x",


Add issue_tracker entry to plugin pubspecs

There needs to be a way to find issues specific to video_player.
when I pressed the button to see View/report issues in the video_player plugin it took me here which seems quite useless.

You can find video_player issues by searching for the p: video_player label.
Setting the plugins to have issue_tracker entries in pubspec.yaml pointing to their corresponding label searches should be doable, avoiding the need to figure that out.

This was fine a while ago, and is enforced by tooling going forward.


how can i get data in json format using  @type record_transformer

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.

fluentd or td-agent version.
Environment information, e.g. OS.
Your configuration
Your problem explanation. If you have an error logs, write it together.

Fill description & reopen this issue.


Continuous crashes

C# isn't my native language so I'm not able to properly understand and debug just by looking at the error. However, my NadekoBot instance keeps crashing, I believe this is due to a logging failure (.log command) as per one of the support agents' view (https://awau.moe/8b95a6.png)
Here's the error on Hastebin: https://hastebin.com/meqoyaxaci.md

I also, seen the same error pop up in my console randomly couldn't really pinpoint the causes since everything in posts by the bot log command seem to show fine.

This is when you have presence updates enabled. Seems to be issue with your internet connection.

Oh?


My internet is too slow to download the model

What is the issue?
I keep getting the same error

ollama run llama3
pulling manifest
pulling 00e1317cbf74...   1% ▕                                                                                ▏  28 MB/4.7 GB   61 KB/s  20h58m
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/00/00e1317cbf74d901080d7100f57580ba8dd8de57203072dc6f668324ba545f29/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%!F(MISSING)20240420%!F(MISSING)auto%!F(MISSING)s3%!F(MISSING)aws4_request&X-Amz-Date=20240420T204533Z&X-Amz-Expires=1200&X-Amz-SignedHeaders=host&X-Amz-Signature=8e4efa642799d32a9e502990baa74226f9f0f740b2cdb7ed0bd6b6741e0106df": net/http: TLS handshake timeout

Is there a way to download llama3 externally and then use it with ollama?
Many thanks
OS
Windows
GPU
Nvidia
CPU
Intel
Ollama version
0.1.32

We don't currently have a formal way to do this, but you can take a look at where the models are stored and transfer the files manually.  https://github.com/ollama/ollama/blob/main/docs/faq.md#where-are-models-stored

I have also encountered the same problem, may I ask if you have solved it and have a suitable solution。

I have meet this problem too. I think cloudflare may cause this problem which China's network may be blocked.

Hi everyone, we're working on these issues and experimenting with a new solution with our partners at the edge. If you have time, please consider helping us test if this helps! We're collecting as much feedback as possible and could use your help!
https://github.com/ollama/ollama/issues/1736#issuecomment-2102983113

I have the same issue, but when I pull with Command Prompt (CMD), it reports an error: 'Error: pull model manifest: open C:\Users\Administrator.ollama\id_ed25519' - The system cannot find the file specified. After rechecking, I found that 'id_ed25519' and 'id_ed25519.pub' have been deleted accidentally.

I have the same issue, but when I pull with Command Prompt (CMD), it reports an error: 'Error: pull model manifest: open C:\Users\Administrator.ollama\id_ed25519' - The system cannot find the file specified. After rechecking, I found that 'id_ed25519' and 'id_ed25519.pub' have been deleted accidentally.

Running the command when I execute open-webui  with docker also gives the error.  All programs is window64


Connectors Migration: Check Pending PRs and Merge

[x] big_query
[x] sales_force
[x] supermetrics
[x] pass code checker
[x] create unit tests
[x] create integration tests

Create a PR for each source!

sales_force.txt
test_salesforce.txt
supermetrics.txt
test_integration_supermetrics.txt
test_unit_supermetrics.txt
bigquery.txt
test_bigquery.txt

BigQuery PR: https://github.com/dyvenia/viadot/pull/1035

Salesforce PR: https://github.com/dyvenia/viadot/pull/1036


[SMALLFIX] Use the @Nullable annotation for all methods which may ret…

…urn null in UnderFileSystemFactoryRegistry.java

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16897/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/16955/
Test PASSed.


Bugfix/numerator obs values

Pull requests into cqm-execution require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Case: When Denominator is 0 then the first index of observation_values array for that episode should be defaulted to 0.
Bug: Instead of adding 0 at the first index, we are replacing the existing value, which could be the value of Numerator Observation.
https://jira.cms.gov/browse/MAT-6623
Screenshot of the contents from This story

Submitter:

[x] This pull request describes why these changes were made.
[x] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[ ] Code diff has been done and been reviewed
[x] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

@RohitKandimalla is it possible to post the contents of the JIRA issue (https://jira.cms.gov/browse/MAT-6623 ) in this pull request?  I'm having trouble understanding what this is trying to fix.

@RohitKandimalla is it possible to post the contents of the JIRA issue (https://jira.cms.gov/browse/MAT-6623 ) in this pull request? I'm having trouble understanding what this is trying to fix.

Sure I add a screenshot, so that it will easier to understand c&p the contents. The over all issue is that Numerator Observations results are not returned by cqm-execution.
Technically, cql-execution is returning us the num_obs values, but during the construction of observation_values array, we are overriding existing values instead of unshifting the array.


[proxy] Improve no_proxy matching logic

What does this PR do?
Before this commit, the no_proxy entries would only match hosts exactly. This adds support for a lot of cases where no_proxy entries should match the request's host, for example:

a no_proxy entry that's a suffix of the target host now matches
the port of the target host is now cleaned up before matching it with
no_proxy entries
[logic that might be golang-specific] localhost and loopback addresses
never use proxies

(see the tests that were added for examples of target hosts that would stop using the configured http/https proxies)
Motivation
Make the behavior of the no_proxy setting closer to what other programs (typically, curl) would do.

The code itself is mostly copied from net/http/transport.go of go's stdlib, with a few minor tweaks for our needs (see inline comments). Unfortunately the logic there isn't usable through exported functions.

@olivielpeau should we close this ?

Yes, even though I think the purpose of the PR is still valid, the PR would require being completely re-implemented to work well with the previous planned proxy logic changes. Closing


Persist-redux interfers with debugging

Admin UI Picard uses persist-redux to save state locally. However, it is currently commented out "for debugging", as accompanying comments state. This is not ideal. Ideally, we should find out why this hinders debugging on how we can quickly enable/disable it during development if need be.

There seems to be no quick way to enable/disable persist-redux, not by restructuring code nor by using browser tools and extensions (e.g. Redux DevTools). Furthermore, the persisted store does not seem to get cleared when hard reloading or clearing cookies/cache before reloading. This deprives users of an easy way to lose unwanted changes and seems to me like a good reason to not actually activate persist-redux again for the time being.

Well apparently I lied, and it actually is possibly to clear a persisted store by clearing cookies/cache. It's just that if you clear them in Chrome through the little "Website-Information" exclamation point icon thingy, Chrome will immediately reload them. Clearing them through the settings works as expected, which seems weird to me, but I take it. Also works in Firefox. With this in mind, I think we can just merge the persist-redux code as is for now.


Tiny Typo: fix “wait unti” ➜ “wait until”.

Hey @ashfurrow and co, really enjoying watching the code review! Thanks for posting it, really interesting! :smiley:
Noticed a tiny typo.

This is great, thanks!


"TypeError: me is not a constructor" while loading via an iframe

Describe the bug
In our application, we have our own text chat and we want to add audio/video call feature to it.
So did a simple POC with your react component and everything seems to work great.
Usually our chat will be loaded into our web app via an iframe, so i was trying the same with the POC i created.
But while loaded it via an iframe i am getting the following error.
core.js:6014 ERROR Error: Uncaught (in promise): TypeError: me is not a constructor
TypeError: me is not a constructor

Steps to Reproduce the Problem

Create a simple POC following your documentation
Load the POC in a iframe and you will see the error

Specifications

Device: MacBook Pro,
OS: Catalina 10.15.3 (19D76)
Platform: Chrome 80.0.3987.163
Version:
"@voxeet/react-components": "^2.0.1",
<EMAIL_ADDRESS>"^5.1.1",
"@voxeet/voxeet-web-sdk": "^2.2.2",
"react": "^16.12.0",
"react-dom": "^16.12.0",
"redux": "^4.0.5",
"redux-thunk": "^2.3.0",

Hello @karthikarul20 sorry for the delay of response, do you still experience issue with iframe and UXKit ?


Remote read should handle down or misbehaving backends gracefully

I'm playing a bit with remote read, and it looks like any failure on the part of the remote read endpoint (e.g. down, malformed response, wrong number of result series) causes the query as a whole to fail.
When any remote read backend fails, the query should continue to work on the rest of the data available.
We may also in future want to report this out to the user via the query api, metrics etc.
FYI @tomwilkie as you mentioned this being relevant for Cortex.

Yes we have the same problem in Cortex, in that we want to return partial results in the even of partial failures (for instance, if S3 is down we still have recent data in the ingesters).  Cortex issue: https://github.com/weaveworks/cortex/issues/309
There doesn't seem to be a particularly appropriate HTTP status code for this - some references imply 207 (http://www.restpatterns.org/HTTP_Status_Codes/207_-_Multi-Status) is appropriate, others that it should be 500 with a body.  WDYT?

I'd have a standard 200, and the extra information in an warning field in the response.

DIBS

@brian-brazil just to make sure I understand the issue here is what I did
set to write and read from influxdb , than I stop the influxdb server and when running any query I am getting
{"status":"error","errorType":"internal","error":"error sending request: Post http://localhost:9201/read: dial tcp [::1]:9201: getsockopt: connection refused"}

this shouldn't happen as the local tsdb should be able to provide some samples if available and the the http header should be:
HTTP/1.1 206 Partial Content

The http response code should be 200. A 206 is something different.

This should also handle broken checksums in TSDB.

That's a bit of a different problem, but may share the warning plumbing.

@brian-brazil @krasi-georgiev
Hi,
I read about this on GSOC'18 ideas page and would like to contribute to it as part of GSOC.
After going through all references, I came to the following conclusions. Please do correct me if my interpretation is wrong.

From this, @brian-brazil proposed to handle this in fanout storage, using the primary and secondary storage .

After going through the code, I came to the following conclusions about it's implementation

In fanout Querier, if  subsequent Querier request are to remote storage, then

If primary Querier fails , report ERROR
If primary Querier succeeds but secondary fails, this is the special case.
In this special case, return an error with the data collected so far & notify user that such a case has occurred. (This case needs to be discussed further)
If both Querier succed, its a success

Is this interpretation of the issue correct ?
And if yes, is the proposed implemetation a way to solve this issue ?

@brian-brazil isn't this solved by https://github.com/prometheus/prometheus/pull/3963

@sipian Your understanding it correct.
@krasi-georgiev No, that's a bug in PromQL where it wasn't propagating errors correctly.

This issue is a major issue for us where we're trying to scale out while preserving user experience...it would be amazing if we could get it in a tagged release soon.

In order for us to move Prometheus into production, it is critical that this issue be fixed first!

Seems like it is being worked on #4832