usdt: path is optional when attaching to pid

This PR has two commits currently which could arguably split into separate PRs.
The first commit adds listing of usdt probes if bpftrace -l is also invoked with -p.
$ bpftrace -p 30000 -l 'usdt:*python*'
usdt:/opt/bin/python3.7:line
usdt:/opt/bin/python3.7:function__entry
usdt:/opt/bin/python3.7:function__return
usdt:/opt/bin/python3.7:import__find__load__start
usdt:/opt/bin/python3.7:import__find__load__done
usdt:/opt/bin/python3.7:gc__start
usdt:/opt/bin/python3.7:gc__done

The second commit allows for omitting the path when describing the usdt probes to instrument so long as a pid was specified for attaching. For example:
$ bpftrace -p 30000 -e 'usdt::function__entry { printf("hi: %s %s\n", str(arg0), str(arg1)); } usdt::function__return { printf("bye: %s %s\n", str(arg0), str(arg1)); }'
Attaching 2 probes...
hi: /test.py fn
bye: /test.py fn
hi: /test.py fn
bye: /test.py fn

The initial motivation for omitting the path was because I was attempting to instrument a path for a process that was running in a mount namespace (i.e. in a container) and was trying to circumvent the various stat()s that were happing.
Initially, I attempted to use /proc/<pid>/root/<path> but unfortunately that leads to EIO when attempting to write in the child /proc/<pid>/mem.
Also, it turns out that in the upstream libbcc there are still some outstanding issues relating to mount namespaces, though generally, it's well behaved.
Tests are still a TODO, though I am not sure necessarily the right way to manage the harness for testing against things in containers.
The following is from the commit message for further details.
When instrumenting a pid the path to the binary is optional since the probes can be determined by discovering the probes by attaching to the process.
Practically, the path is resolved and associated with the attach point during the semantic analyzer path, though the irbuilder must also attach to the process to resolve the arguments.
Remove GetProviderFromPath in favor of discovering the provider by attaching to the process, which is the more reliable method. The path only has a passing relationship to the provider as defined by stapsdt.
Upstream bcc_usdt_new_frompid has an issue when instrumenting a process that is in a mount namespace, so for now don't include the path when attaching to a pid.
Relatedly, the stat() that occurs in the semantic analyzer is removed since it isn't namespace aware.

Forgot to also mention, please excuse the style it's been a while since I touched c++

The TODO's can be resolved if/when iovisor/bcc#2064 is resolved

A few more comments after playing with it:

Shouldn't we specify the provider in the probe definition? In the example below we have two probes with the same name, but with different providers:

#include <sys/sdt.h>
#include <unistd.h>

int main() {
  char myStr[] = "My string";
  while (1) {
    DTRACE_PROBE2(foo, second_probe, myStr, 1);
    sleep(2);
    DTRACE_PROBE2(bar, second_probe, myStr, 2);
  }
  return 0;
}

bpftrace can't differentiate them, thus we can't attach to them:
# ./src/bpftrace -p $(pgrep main) -l 'usdt:*main*'
usdt:/home/mmarchini/lsls/main:second_probe
usdt:/home/mmarchini/lsls/main:second_probe
# ./src/bpftrace -p $(pgrep main) -e 'usdt::second_probe { printf("%s, %d\n", str(arg0), arg1); }'
Attaching 1 probe...
Two same-name probes (second_probe) but different providers
Error finding or enabling probe: usdt:/home/mmarchini/lsls/main:second_probe

A suggestion would be changing the usdt probe definition to usdt:PATH:PROVIDER:PROBE. This approach would be more accurante since we're using stapsdt as our USDT format.

Should -l list kprobes and kernel tracepoints when a PID is provided? I think it should list only usdts (also uprobes in the future?).

Thanks for the review, I'll address the nits tonight.
I wanted to enable multiple probe matching, while the map and look up models I'm using are clearly a shortfall, the deficiency here ultimately isn't in bpftrace but rather upstream with bcc https://github.com/iovisor/bcc/blob/ec3fe90b9f8116cb6d8eec940015cd4eda01df7d/src/cc/usdt/usdt.cc#L299
IMO there's some confusion with the notion of provider and probeType. Generally this isn't a problem for bcc or bpftrace because for most probeType is in fact similar to a provider in dtrace. So the 3 tuple used for bpftrace is generally fine <probeType>:<module>:<probe name>, up and until you hit the usdt case, where it really wants/needs a 4 tuple <probeType>:<provider>:<module>:<probe name> because it is in fact a direct descendent of dtrace.
So, I had considered extending the parser to support packing more information into the probe description, but since it ultimately wasn't going to work because of the upstream issues, I decided to be "as good" as bcc for now. When bcc can do it, we can make sure bpftrace DTRT.

Also, maybe I should move the list commit into its own PR, here I decided to follow what dtrace does and print all probes but just include the newly discovered probes that are found by attaching to the process (much like the pid provider does for dtrace). Ultimately though, I think bpftrace should probably grow the notion of dtrace's -P as well which would make listing only the probe types you care about far more sane.

iovisor/bcc#1527 is tracking the multiple same named probes with different providers

I've updated with the code changes, but I haven't yet done the tests, I'm hoping to get to that tomorrow.

We should merge this soon before the code changes too much. @tjfontaine did you have time to add some tests, or look at some? We merged runtime tests (#288), which might be the easiest way to test these, although doing runtime usdt means having some usdt probes handy on the system (libc? ld? I see probes in my  /lib64/ld-linux-x86-64.so.2 ).

We can just build a simple binary with USDT probes. IIRC runtime tests already build one fixture binary for uprobes.

stumbled across this when looking at a fix to #328 - would be really helpful to have this merged, especially being able to dynamically list the available usdt probes.
I can take a look at rebasing, but perhaps the probe list functionality should just be cut out into a separate PR? It's fairly simple and immediately useful, negating the need for tplist.
It would also seem that there is an erroneous check that has been introduced (semantic_analyser.cpp), that attempts to validate if the path exists but doesn't attempt to do it from the mount namespace of the pid, causing it to incorrectly fail in a number of cases as it's not checking the correct mount namespace for the path. This PR will probably need a way of working around that path handling issue as well.

I can get this fixed up tomorrow, sorry work got in the way

@tjfontaine heads-up that #413 might conflict with this too, sorry to step on your toes :grimacing:

@dalehamel no problem, I'll comment on your other pull request as I have some thoughts there

@tjfontaine I rebased to fix the conflicts, let me know if I can force push to your branch.
I opened a draft PR to diff the rebased version: https://github.com/iovisor/bpftrace/pull/444. I'll close it once we update this PR.

@mmarchini i tried your rebase and it seems to work well!
I can confirm that your rebase allows me to list user probes (yay!) as in the original description, and also allows for attaching to usdt probes by PID.
The following works, to list usdt probes for a ruby process:
bpftrace -l 'usdt:*ruby*' -p 2602719

Unfortunately, I think that i'm having issues specific to my environment. No probes actually seem to be firing (ruby on rails process behind unicorn, trying to trace rails processes directly as well as the forking unicorn server). I would expect at least method__entry to be fired, but i'm getting nothing. I'm going to try and dig into why this is, and try to come up with a minimal test case.
bpftrace -e 'usdt::ruby:method__entry { @++ }' -p 2602719

The above attaches, but never fires as the map is never incremented...
If it's working for other languages / frameworks with USDT probes though then it's probably specific to the environment I'm trying to probe. I'll file a bug if relevant once I figure it out, but otherwise i think the rebase is good :+1:

Merged in #444. Thank you @tjfontaine!


bitcoin-unlimited: <IP_ADDRESS> -> <IP_ADDRESS>

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/bitcoin-unlimited/versions.
meta.description for bitcoin-unlimited is: "Peer-to-peer electronic cash system (Unlimited client)"
meta.homepage for bitcoin-unlimited is: "https://www.bitcoinunlimited.info/"
meta.changelog for bitcoin-unlimited is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bitcoind passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bitcoin-cli passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bitcoin-tx passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bitcoin-miner passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/test_bitcoin passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bench_bitcoin passed the binary check.

Warning: no invocation of /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/bitcoin-qt had a zero exit code or showed the expected version

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/test_bitcoin-qt passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bitcoind-wrapped passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bitcoin-cli-wrapped passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bitcoin-tx-wrapped passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bitcoin-miner-wrapped passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.test_bitcoin-wrapped passed the binary check.

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bench_bitcoin-wrapped passed the binary check.

Warning: no invocation of /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.bitcoin-qt-wrapped had a zero exit code or showed the expected version

/nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin/.test_bitcoin-qt-wrapped passed the binary check.

14 of 16 passed binary check by having a zero exit code.

0 of 16 passed binary check by having the new version present in output.

found <IP_ADDRESS> with grep in /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>

found <IP_ADDRESS> in filename of file in /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>

directory tree listing: https://gist.github.com/af1971dd66e365518cc9ac5b4767f50c

du listing: https://gist.github.com/9dc34c9ac0b386d7549abfdb248b0279

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bitcoin-unlimited
bitcoind-unlimited

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS> \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bitcoin-unlimited https://github.com/r-ryantm/nixpkgs/archive/e9cb66f98acce1487c930d95e978f673bcbb6d5a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>
ls -la /nix/store/xjd2byyyal65c68jyr76rh6q20r7k3zm-bitcoin-unlimited-<IP_ADDRESS>/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

bitcoin-unlimited
bitcoind-unlimited

Maintainer pings
cc @DmitryTsygankov for testing.

Result of nixpkgs-review pr 120880 at e9cb66f9 run on x86_64-linux 1

1 package skipped due to time constraints:

bitcoind-unlimited

1 package built successfully:

bitcoin-unlimited

1 suggestion:

warning: build-tools-in-build-inputs
util-linux is a build tool so it likely goes to nativeBuildInputs, not buildInputs.
Near pkgs/applications/blockchains/bitcoin-unlimited.nix:21:3:
   |
21 |   buildInputs = [ openssl db48 boost zlib
   |   ^


Option to disable join_verb_parts in WordTokenizer?

Hello dear authors.
Is there a way I can set the join_verb_parts flag to False for the WordTokenizer?
I want the tokenizer to tokenize "نوشته می‌شود" into two separate tokens 'نوشته' and 'می‌شود', instead of the one token 'نوشته_می‌شود'.
Currently I am able to modify the source code in order to achieve my desired result, but I am looking for a way to set this flag as an option instead.
Thank you.

This feature is now implemented.
You can pass join_verb_parts to WordTokenizer:
>>> WordTokenizer(join_verb_parts=True)
	.tokenize('این کتاب به دست چه کسی نوشته می‌شود؟.')

Read more.


koordlet: add close for querier

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

#1981
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/approve


Couldn't retrieve Skype token from login response

Hi! I am novice in python, but I really liked you API, I used it successfuly in September-October, but now I am facing some issues when trying to run it, here's traceback:
Traceback (most recent call last):
File "zabbix-parsing.py", line 23, in
sk = Skype("my_login", "my_password") # connect to Skype
File "/usr/local/lib/python2.7/dist-packages/skpy/main.py", line 70, in init
self.conn.getSkypeToken()
File "/usr/local/lib/python2.7/dist-packages/skpy/conn.py", line 259, in getSkypeToken
self.login(user, pwd)
File "/usr/local/lib/python2.7/dist-packages/skpy/conn.py", line 392, in login
raise SkypeApiException("Couldn't retrieve Skype token from login response", loginResp)
skpy.core.SkypeApiException: ("Couldn't retrieve Skype token from login response", <Response [200]>)
Thanks in advance

Seems like my bad, I panicked too early. Just updated skpy and seems like it's working. Sorry


fastify.requireAuthentication()

https://github.com/patrickpissurno/fastify-esso/blob/6d4e04ac5ab0dcc32338947717d5698d86090b62/lib/index.js#L152
Hello
I'm a bit confused with the fastify plugin pattern (and with JS as well sometimes), but why do you need to inject the server instance into "requireAuthentication" ?
You seem to already have this instance injected above : https://github.com/patrickpissurno/fastify-esso/blob/6d4e04ac5ab0dcc32338947717d5698d86090b62/lib/index.js#L98
So I'm not sure, but is there a way to call  fastify.requireAuthentication() from a method defined with no param at all ?

Could the full example work like this ?
(with auth route defined above the plugin registration )
// register our private routes
fastify.register(() => {
    fastify.requireAuthentication()
    fastify.get('/order-drink', async (req, reply) => {
        return { message: 'Hello ' + req.auth.user + '. Here is your drink!' };
    });
});

Honestly, I don't know if it would be possible to improve usability by not requiring you to pass fastify into the requireAuthentication function.
The reason you need to pass it right now is that even tho it appears that requireAuthentication is a method of fastify, it is currently not bound to it, so the this variable is not set, and thus if you don't pass it like that (again even tho it looks redundant), it wouldn't be possible to access fastify from inside it to do what needs to be done.
But from a practical perspective, don't worry about that. Just call fastify.requireAuthentication(fastify) and it will work fine.
Cheers!


Filtering not working as expected for multiple columns with same accessor

What version of React-Table are you using?
6.6.0
What bug are you experiencing, or what feature are you proposing?
If displaying multiple columns with the same accessor setting filterable: false on one column disabled filtering on all of them, but the filter input is rendered.
The use case here is having different renderers for the same data in the columns - e.g. one of the columns is a button that is bound to the value.
Sandbox
https://codesandbox.io/s/9z1x0wko6p
What are the steps to reproduce the issue?

Add two columns with same accessor
Set first one to filterable: false
Try to filter by second column

Note that the workaround here is to turn:
{
  Header: "First Name",
  accessor: "firstName",
  filterable: false,
},
{
  Header: "First Name #2",
  accessor: "firstName"
},

into
{
  Header: "First Name",
  accessor: item => item.firstName,
  id: 'no-filter-column'
  filterable: false,
},
{
  Header: "First Name #2",
  accessor: "firstName"
},

Given that filters work on the id of the column (which by default is the accessor if it is a string and no id is provided) and not specifically on a column position, then the behaviour is working as it is designed to work. Your "solution" is working because you have given the column a different id.
I think the use-case is an edge one and providing a different id accomplishes the goal so this is not considered a bug.

Yep, I guessed that this was the case and I agree that this is a not a common scenario, but I still think there's an issue here.
While the filtering behavior might be bound to a column id, the filtering display is not, i.e. while the other column becomes non-filterable it still renders the filter text input.

I've had a look at your codesandbox and the column that has filterable set to 'false' does not have the filter input box showing.  So maybe I am misunderstanding what you mean.
The columns are still separate.  But it is the id that is used to filter the data.  Clearly, there'd be no point in creating the column at all if everything worked identically between the two.  At some point there has to be rationale for picking how a column contributes to filtering (especially given the developer can inject filter criteria from outside ReactTable).
It might seem strange but I still don't believe there is any discrepancy here that needs any action taken.

Let me put it a different way: If you want to use the same accessor on more than one column (which still seems an edge case just by itself), then the id needs to be set differently for everything to work consistently.
If you are talking about wanting to render data differently, then it is better to use the Cell prop. The accessor is used to get "raw" data that can be used for internal state use but the Cell can render any sort of text or component into what the user sees and has access to the whole row (not just the value returned by the accessor).


Video Filters and Save Video

I added the ability to set video filters to the video player. This can be passed as a prop to the Component.
I also added the ability to save the video with the current filter using a saveAsync method that returns a promise.
I am open to changes and suggestions.

@n1ru4l Thanks! Yeah not a problem. AppCode kept reformatting it for me, but it should be good to go now.

Hi @nickgzzjr, thanks for submitting this. Having save functionality will be great, a lot of people want it!
I did a few minor updates to the docs and function names. Imo, calling is save() is ok since you cover that in the docs it doesn't need to be saveAsync().
On the filters, can we name them the same as they are on iOS (Noir, Sepia, Posterize, etc)? I'm a big fan of not modifying APIs so that if someone is looking at the iOS docs to figure out which filter they want, they don't have to translate names. I'd also like to support as many of the filters on the list as possible. I would put all of the filters in a FilterType.js file so that you just go FilterType.SEPIA like you can with TextTrackType.
I would also add a link to the iOS docs so developers can see what the filters look like:
https://developer.apple.com/library/archive/documentation/GraphicsImaging/Reference/CoreImageFilterReference/index.html
For saving, that needs a lot of documentation for it to be useful to other developers. A couple questions I'd have if I was using the API:

Does it work for non-MP4 content like HLS streams? How about .mov files?
Where is the file saved and how to do I play it back once saved?
When can I save? If there is a long video and it's not completely buffered, will it still work?
How do I remove the video when I no longer want it to be stored?
@n1ru4l recently added caching for iOS. Will this work when caching is enabled?

Can you update the docs to cover this and any other implementation details that you think people need to know.

Hi @cobarx, thanks so much for you feedback, and your doc changes.

I went ahead and renamed saveAsync() to save().
I added the FilterType.js file with most of the filters from Apple as recommended. (I did not add the filters that required extra parameters)
I renamed the filter names to match the iOS docs
I updated the docs for both filter and save

I need to do further research and testing when saving videos that are buffering and cached. My guess is that it works just fine since it grabs the video from the player asset item.

@cobarx I can confirm that saving cached videos works, as well as videos that are buffering. I have updated the docs to reflect my findings. I modified the video-caching example to test. Let me know if there are any other suggestions.

@nickgzzjr Thanks for taking the time to make the changes I requested. I finally had a chance to test the filters, those are very cool!
I ran into a couple issues with the filters. First, when I play a video with the filter turned on in the iOS Simulator, it's very jerky and is maxing out the CPU on my machine. Activity Monitor shows 200% cpu vs. 30% cpu with it off. Have you seen this when testing? Can you see if you can figure out what might be causing this?
Second, the filters don't appear to work for HLS playlists. If I play an MP4, the filter works but for HLS nothing happens. Here is a sample stream you can use for testing:
http://devimages.apple.com/iphone/samples/bipbop/bipbopall.m3u8
You will need to turn off App Transport Security since it's http:
https://github.com/react-native-community/react-native-video#ios-app-transport-security
If possible, I'd like to get this fixed as most companies doing video delivery are using HLS not mp4s and I'm trying to avoid having features that work in some scenarios but not others. However, if it can't be done, we can ship as is, just make sure to add a note to the docs.

Just an idea: Maybe saving the videos could replace the video cache implementation that I made and the video caching could be completely done in userland?

Do I understand correctly that if I save the video it appears on my Camera Roll/Photo App? if I am building a social network app (like instagram), I would prefer that not every single video is saved to the CameraRoll. If someone wanted this he could use CameraRoll (https://facebook.github.io/react-native/docs/cameraroll). I think this might be out of scope!


Added audio examples. Fix bug in raylib textFormat.

Implemented raylib's (audio mixed processor example)[https://github.com/raysan5/raylib/blob/master/examples/audio/audio_mixed_processor.c].
I copied the audio files from raylib's repository and added them to this one under resources. Whenever someone gets around to implementing zig build examples, they will need to include that resources directory with the executable for this example to work properly.
Below is an image of the results of running zig build mixed_processor

I compared to the original example. I have much more distortion. I will iron out these issues.

I figured out there was a bug in raylib.zig. textFormat was switching on .Struct, which was throwing an error. I looked at some of the innards and found @"struct" is an alias for Struct, so I switched on that instead.

All of the audio examples have been added. Here's the list
zig build mixed_processor
zig build module_playing
zig build music_stream
zig build raw_stream
zig build sound_loading
zig build sound_multi
zig build stream_effects

The only issues I notice:

Allocation in stream_effects should instead pass the allocator as a parameter rather than hardcoding it in.
stream_effects seems to be slightly distorted when using LPF filter compared to native C build. Not sure why that is.

This should be two PRs. One for the fix, one for the examples. Also take some time to read through CONTRIBUTING.md.
zig build examples is implemented, so any build steps should work with this PR (should as in, you should make them work if they don't).


Labstarter fix messaging emulator

Fix error popup on messaging emulator
Fix UI to have the same styles as main spring petclinic app

LGTM


Data argument not sent to output binding when calling DaprClient.invoke_binding

Expected Behavior
The data argument of the invoke_binding method on the DaprClient class is sent to the output binding.
Actual Behavior
The data argument is not sent to the binding. The metadata is sent correctly.
Steps to Reproduce the Problem
I noticed this behavior when using the SMTP output binding. When executing the following code:
with DaprClient() as client:
    client.invoke_binding(
        binding_name="sendmail",
        operation="create",
        data=message_body,
        binding_metadata=message_properties
    )

The client sends the metadata to the correct binding with the correct operation. However, when I check the generated email, the body of the email is empty. After some more debugging I found out that when I send a POST request to the same binding it works. I've checked this with the following code:
message_data = {
    "data": message_body,
    "operation": "create",
    "metadata": {
          "subject": "Fine for exceeding the speed limit.",
          "emailTo": vehicle.ownerEmail,
          "emailFrom"<EMAIL_ADDRESS>    }
 }

 response = requests.post("http://localhost:3601/v1.0/bindings/sendmail", json=message_data)

This leads me to believe that the DaprClient isn't sending the data to the binding.
Release Note

RELEASE NOTE:

I've looked into this some more and discovered that the data argument is passed to the output binding. I replaced the email binding with a local file binding and that one works correctly with the invoke_binding method.

Found it! It's actually not in the python-sdk but rather in the SMTP binding :)
I posted a fix here: https://github.com/dapr/components-contrib/pull/1254


Option to set string based on hightlighted entry in a ComboBox

If you quickly want to select options for a string property, it is easier to set the string based on the currently highlighted item. No need to open the ComboBox several times to select one choice after the other.
This is only done if the Option "highlightActiviation" is set.

You could also use the up and down arrow keys while the combo box is active.

Arrow keys also work, however the option to do the same thing with the mouse offers faster and more precise navigation through a long list of choices, as the arrow keys depend on the character repeat rate. Also "scanning" through the list and changing direction with the mouse feels easier.


Right sidebar overflow into content component

Describe the bug
Noticed that with the default settings, pages that have a graph, table of contents, and backlink components have an unfortunate habit of overflowing a bit into the main content page. This is a minor visual bug, probably due to some CSS chicanery.
To Reproduce
Steps to reproduce the behavior:

Create a quartz with default settings
Add note so that it'll have a graph, table of contents, and backlinks component (Pretty much plain old note)
Build and serve the note
Noticable when intersecting the rightmost edge of text/callout/code block/image

Expected behavior
For the right sidebar to not spill over into the content component.
Screenshots
Example from the Quartz docs.

ation)
Desktop (please complete the following inform
:

OS: Windows 10
Browser: Chrome 118, Mozilla Firefox 119

I'll try and tackle the issue myself, if anyone beats me to the punch, I'll be disappointed 😄

haha, I've been busy as of late so I haven't had a chance to work on this! duplicate of #516 so I'll close this in favour of that but would appreciate a fix :)


Update protobuf

To 3.20.3 for TensorFlow 2.15 .

Cf. #12

I thought someone had a working version newer than this? Latest is 5.27.x, should we try to find something later that works so we don't keep having to update so often?

I think it's best to be flexible here and just track the TensorFlow requirements.


support numpy>=2

Is your feature request related to a problem? Please describe.
not yet support numpy>=2
Describe the solution you'd like
in pyproject.toml, numpy = "^1.9.0" -> numpy = ">=1.25"
(Since version 1.25, numpy does not support python<=3.8.)
References or alternative approaches
If this feature was described in literature, please add references here. Additionally, feel free to add descriptions of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Are you able and willing to implement this feature yourself and open a pull request?

[X] Yes, I can provide this feature.

Hi @phi-friday,
thanks for creating this issue. I'm a bit confused, the title of the issue refers to numpy 2.0.0 but the content is about supporting numpy <1.9.0. Can you clear this up for me maybe?

Regarding the former, I haven't had the time to check what, if any, adjustments would need to be made to the code.
Regarding the latter, I think we intentionally dropped python 3.8 support. @bwheelz36 do you remember why?

I think numpy or some other dependency was no longer supporting it. But I don't remember very clearly tbh.

changes to be made: maybe none. So far the only issues I've had switching to numpy 2 has been in typing (they dropped some deprecated types). someone could check quickly if all our tests pass with numpy 2
BUT. I'm not sure it's a good idea to be supporting both numpy 1.x and 2.x as is proposed by @phi-friday. There presumably will be breaking changes between these versions even if they don't currently break this code. Eventually we will have to move to 2, but at that point we should drop support for 1, which will be breaking for most users.

It's definitely possible right now for users to use this package with numpy 2 with a bit of fiddling. I'd probably prefer to hold off a little longer until upgrading to 2. But I'm open to counter arguments.

Oh, just saw that indeed all tests are passing. Thanks @phi-friday!

Found it!
I think it's probably not necessary to support 3.8. IF we want to enable numpy 2.0.0, I would opt for numpy = ">1.9.0".

I'd probably prefer to hold off a little longer until upgrading to 2.

I agree.

Hi @phi-friday,
thanks for creating this issue. I'm a bit confused, the title of the issue refers to numpy 2.0.0 but the content is about supporting numpy <1.9.0. Can you clear this up for me maybe?

Regarding the former, I haven't had the time to check what, if any, adjustments would need to be made to the code.
Regarding the latter, I think we intentionally dropped python 3.8 support. @bwheelz36 do you remember why?

According to https://python-poetry.org/docs/dependency-specification/,
^1.9 does not support >=2.0.0.

Found it!
I think it's probably not necessary to support 3.8. IF we want to enable numpy 2.0.0, I would opt for numpy = ">1.9.0".

I'd probably prefer to hold off a little longer until upgrading to 2.

I agree.

If you're not going to support python<=3.8, why not limit it to >=1.25?

I think numpy or some other dependency was no longer supporting it. But I don't remember very clearly tbh.

changes to be made: maybe none. So far the only issues I've had switching to numpy 2 has been in typing (they dropped some deprecated types). someone could check quickly if all our tests pass with numpy 2
BUT. I'm not sure it's a good idea to be supporting both numpy 1.x and 2.x as is proposed by @phi-friday. There presumably will be breaking changes between these versions even if they don't currently break this code. Eventually we will have to move to 2, but at that point we should drop support for 1, which will be breaking for most users.

It's definitely possible right now for users to use this package with numpy 2 with a bit of fiddling. I'd probably prefer to hold off a little longer until upgrading to 2. But I'm open to counter arguments.

numpy>=2 has been in the works for a very long time. If you haven't encountered a DeprecationWarning, you should be fine in most cases.

agreed @phi-friday , I think if both versions are being explicitly tested via CI we could support both.
If we just change to numpy = ">=1.25" as proposed, I think we'd have to do some manual fiddling to make sure numpy <2.0.0 is tested, since I think poetry would install 2.0 for every python version > 3.8.
So, we could:

run the tests as normal
then pip uninstall numpy
pip install "numpy<2.0.0"
then run the tests again

note that I haven't checked that would work but I think it would

You can handle different version with a matrix. There's actually an example for exactly this case in snok/install-poetry's docs.

You can handle different version with a matrix. There's actually an example for exactly this case in snok/install-poetry's docs.

https://github.com/bayesian-optimization/BayesianOptimization/pull/491#issuecomment-2213772825
I added new action, and it passed all tests.


Uncaught Error in example for dropdown menu

Steps to reproduce

visit Dropdown Menu documentation
in the first example bring the the second dropdown menu, labeled icons, in focus.
start typing with the mouse hovered over the field
when the mouse is moved outside the field the error shown below appears

Expected results
No errors
Actual results
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

Hi @bibaswan-bhawal, can you check on the master channel to see if you still experience this issue? I can't seem to reproduce this on the master channel. It may have been fixed on that channel. I tested on 3.28.0-1.0.pre.125

This is on the website

@danagbemava-nc any chances of this landing on the stable channel as a hotfix?

Hi @bibaswan-bhawal, can you check on the master channel to see if you still experience this issue? I can't seem to reproduce this on the master channel. It may have been fixed on that channel. I tested on 3.28.0-1.0.pre.125

On the official Flutter page the error appears
https://api.flutter.dev/flutter/widgets/Form-class.html    Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"
Uncaught Error, error: Error: Assertion failed: org-dartlang-sdk:///lib/_engine/engine/pointer_binding/event_position_helper.dart:70:10
targetElement == domElement
"The targeted input element must be the active input element"

Hi @bibaswan-bhawal, @93jose93  api.flutter uses the stable channel. To use the master channel docs, you can use https://main-api.flutter.dev.

@danagbemava-nc any chances of this landing on the stable channel as a hotfix?

@Macacoazul01, if we know the commit that fixed it, we can file a cherry-pick request, it will then be evaluated.
Can you confirm if this is fixed on the master channel?

@danagbemava-nc its possible to get the same error on the material docs:
https://api.flutter.dev/flutter/material/SearchAnchor-class.html

You just need to keep opening and closing the search anchor from the first sample.
Searching in the master to find the commit

related to:
https://github.com/flutter/flutter/issues/160155 and https://github.com/flutter/flutter/issues/156842

@danagbemava-nc
Originally posted by @Reprevise in https://github.com/flutter/flutter/issues/160155#issuecomment-2547219197

Hi All, this has been fixed on the master channel and there's a cherry-pick being considered.
@Macacoazul01, thanks for finding the links.
Given that this has been fixed and is already being considered for cherry-picking, I'll be closing this.
Thank you

@danagbemava-nc its possible to get the same error on the material docs:
api.flutter.dev/flutter/material/SearchAnchor-class.html

PS: api.flutter.dev uses the stable channel, so the bug is expected there since the bug is on 3.27.0/1.


[projmgr] make optimize and warnings types more generic

Contributed by STMicroelectronics
Signed-off-by: Tarek BOCHKATI<EMAIL_ADDRESS>

this is reflecting my shared thoughts in https://github.com/Open-CMSIS-Pack/devtools/issues/179#issuecomment-1128786775


Allow assert module to provide $traceurRuntime.type.* and $traceurRuntime.genericType

When transpiling AtScript to ES6, the only reference to $traceurRuntime are $traceurRuntime.type.* and $traceurRuntime.genericType(...). However, those references are very closely related to the assertion module, so it would be great to have an option to use the implicitly imported assert module instead.
Traceur 0.0.82

The goal is to make the assertion module non configurable. Things like type semantics is an important part of the goal, making that pluggable defeats that.

True, but the code that is generated right now looks like this:
assert.argumentTypes(a, $traceurRuntime.type.string);

So what a type really means is defined by the assertion module. Whether the token is stored inside of $traceurRuntime or assert does not change/control the semantics.

For builtins I think we can change to strings. The generics is a bit worse.

Agree, strings for builtins would be great. How about just using an object literal for generics?
E.g.
{ type: List, args: ['string']}


Fix #1704. Shrink statistics table and grow cake diagram

It now looks like this instead, much more room for the glorious cake 🍰 .

sick work m8
💯 💯 👌


kamel run --dev examples/resources-route.groovy issues Cannot find resource

Fixes #697

@aldettinger it depends on the runtime you are using, so with the latest runtime this fix is needed as the platform stream handler is not more used

Ok, thanks for explanation. :+1 Then


SU Documentation mentions non-existing SceneQuad API GetOcclusionMask

The documentation mentions a GetOcclusionMask() SceneQuad method, but doesn't describe what it does.  Also this method doesn't appear on the SceneQuad.
There is a SceneQuad::GetSurfaceMask, but again the documentation doesn't describe this method.
Please remove reference to SceneQuad::GetOcclusionMask and add reference to SceneQuad::GetSurfaceMask.  And provide a description for SceneQuad::GetSurfaceMask

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e11ada88-8eb6-0e07-0b90-02b8b87179bf
Version Independent ID: 9bb41118-53ab-73c6-5908-83f0c2334536
Content: Scene understanding SDK - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/platform-capabilities-and-apis/scene-understanding-SDK.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @SzymonS
Microsoft Alias: szymons

@SzymonS, is this something you can assist with or ping someone who can?

Hi @AMollis, this doc has been updated! For reference - https://github.com/MicrosoftDocs/mixed-reality/pull/140


Strikethrough regression

Completing your currently focused habit used to mark the habit label with a strikethrough, but that has ceased to be the case since v2.2.0.
Working in v2.1.0:

Broken in v2.2.0:

Also caused by the switch to pancurses, wow I did not test that release properly :p
I will be tracking this over at #50 if you don't mind.


Plotting update parallel down

Catch more errors in the download function
Fix double-counting of failed downloads
Drop-in the parallel download function to plotting.py
Add type hints to plotting.make_lightcurve

@masek014 take a peeksie 👀


Is it production ready ?

Amazing project. Just wonder whether is it fully tested and production ready ?

production ready?

Well that might just depend on your usage.

fully tested

Have your played around with the examples, made changes, what's not working as expected?
But the real answer is just going to open up a bag of worms. I'm more on the side of the science of things, in which case, one can always add, there will be many more rabbit holes to go down.
The current status is integrating libuv, no hurry. How big is that, how many people involved on that project?
My perspective it's an event loop abstraction that needs structuring here in an way that it can be replaced with custom setup if need be. If there was no libuv, I would be building that too.
The actual coroutine part here is done, how that behaves, and in making an release, I would need feedback on how things working/not working in ones environment.


[SPARK-27876][CORE] Split large shuffle partition to multi-segments to enable transfer oversize shuffle partition block

What changes were proposed in this pull request?
There is a limit for shuffle read.
If a shuffle partition block's size is large than Integer.MaxValue(2GB) and this block is fetched from remote, an Exception will be thrown.
    2019-05-24 06:46:30,333 [9935] - WARN [shuffle-client-6-2:TransportChannelHandler@78] - Exception in connection from hadoop3747.jd.163.org/<IP_ADDRESS>:7337
    java.lang.IllegalArgumentException: Too large frame:<PHONE_NUMBER>
    at org.spark_project.guava.base.Preconditions.checkArgument(Preconditions.java:119)
    at org.apache.spark.network.util.TransportFrameDecoder.decodeNext(TransportFrameDecoder.java:133)
    at org.apache.spark.network.util.TransportFrameDecoder.channelRead(TransportFrameDecoder.java:81)
    at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:362)

Then this task would throw a fetchFailedException.
This task will retry and it would execute successfully only when this task was reScheduled to a executor whose host is same to this oversize shuffle partition block.
However, if there are more than one oversize(>2GB) shuffle partitions block, this task would never execute successfully and it may cause the failure of application.
In this PR, I propose a new method to fetch shuffle block, it would fetch multi times when the relative shuffle partition block is oversize.
The simple brief introduction:

Set a shuffle fetch threshold(SHUFFLE_FETCH_THRESHOLD) to Int.MaxValue(2GB)
Set a parameter spark.shuffle.fetch.split to control whether enable fetch large partition multi times
When creating mapStatus, caucluate the segemens of shuffle block (Math.ceil(size /SHUFFLE_FETCH_THRESHOLD )), and only record the segment number which is large than 1.
Define a new BlockId type, ShuffleBlockSegmentId, used to identifiy the fetch method.
When spark.shuffle.fetch.split is enabled,  send ShuffleBlockSegmentId message to shuffleService instead of ShuffleBlockId message.
For a ShuffleBlockId, use a sequence of ManagedBuffers to present received blocks instead of a ManagedBuffer.
In ShuffleBlockFetcherIterator,  create a PriorityBlockQueue for a ShuffleBlockId to store the fetched SegmentManagedBuffer, when all segments of a ShuffleBlockId are fetched,  take  relative sequence of managedBuffers(which are ordered by segmentId) as a successResult for a ShuffleBlockID.
In the shuffle serivice side, if the blockId of openBlocks is a ShuffleBlockSegmentId,  response a segment managedBuffer of block , if the blockId is a ShuffleBlockId response a whole managedBuffer of block as before.

How was this patch tested?
manual test

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

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/testing-k8s-prb-make-spark-distribution-unified/11194/
Test PASSed.

Test build #105942 has started for PR 24740 at commit 256b3c8.

Test build #105942 has finished for PR 24740 at commit 256b3c8.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class ShuffleBlockSegmentId(shuffleId: Int, mapId: Int, reduceId: Int, segmentId: Int)
      case class SegmentManagedBuffer(
 case class FetchRequest(address: BlockManagerId, blocks: Seq[(BlockId, (Long, Int))])

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105942/
Test FAILed.

I will check it and resolve the unit test. Thanks.

@squito ?

Test build #105952 has started for PR 24740 at commit ae36c12.

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/testing-k8s-prb-make-spark-distribution-unified/11204/
Test PASSed.

Test build #105952 has finished for PR 24740 at commit ae36c12.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105952/
Test FAILed.

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/testing-k8s-prb-make-spark-distribution-unified/11206/
Test PASSed.

Test build #105954 has started for PR 24740 at commit 03deb3a.

Test build #105954 has finished for PR 24740 at commit 03deb3a.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105954/
Test FAILed.

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/testing-k8s-prb-make-spark-distribution-unified/11211/
Test PASSed.

Test build #105959 has started for PR 24740 at commit 534f376.

Test build #105959 has finished for PR 24740 at commit 534f376.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105959/
Test FAILed.

I am confused that the test thrown javadoc exception.

Test build #105961 has started for PR 24740 at commit d905608.

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/testing-k8s-prb-make-spark-distribution-unified/11213/
Test PASSed.

Test build #105961 has finished for PR 24740 at commit d905608.

This patch fails to generate documentation.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105961/
Test FAILed.

Test build #105962 has started for PR 24740 at commit 8ff522d.

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/testing-k8s-prb-make-spark-distribution-unified/11214/
Test PASSed.

Test build #105962 has finished for PR 24740 at commit 8ff522d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/105962/
Test FAILed.

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/testing-k8s-prb-make-spark-distribution-unified/11215/
Test PASSed.

Test build #105963 has started for PR 24740 at commit 2edfc95.

Test build #105963 has finished for PR 24740 at commit 2edfc95.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/105963/
Test PASSed.

You shouldn't have this limit anymore (from spark 2.4 onwards) as long as you're also running a recent shuffle service.  this uses fetching shuffle blocks to disk, instead of memory, which should be enabled by default for large blocks (https://issues.apache.org/jira/browse/SPARK-24297).
But if you're seeing a failure with that, can you share some more details?

You shouldn't have this limit anymore (from spark 2.4 onwards) as long as you're also running a recent shuffle service. this uses fetching shuffle blocks to disk, instead of memory, which should be enabled by default for large blocks (https://issues.apache.org/jira/browse/SPARK-24297).
But if you're seeing a failure with that, can you share some more details?

Thanks. I see this failure with spark-2.3.2. I'm sorry for that I had not notice your PR, which set
maxRemoteBlockSizeFetchToMem to a value little than 2GB.
But when resources are available, I think we can set this value large than 2GB and reduce the I/O overhead.

Can one of the admins verify this patch?

Is this still an issue?

For current master branch, it set spark.maxRemoteBlockSizeFetchToMem=Int.MaxValue - 512, which is little than 2GB(https://issues.apache.org/jira/browse/SPARK-24297).
So, it would not touch this issue.
But if you set spark.maxRemoteBlockSizeFetchToMem to a value large than 2GB, you will still meet this issue.

shall we close it? I don't think this an issue now.

ok, closed


Complete group decoding support.

There is a small additional check without the loop for field parsing but the cost according to the perf_runner.sh seems to be within the range of noise.
The other approach would seem to be to make a GroupBinaryDecoder that just wraps the BinaryDecoder forwarding everything to the wrapped one with the extra checks adding to nextFieldNumber().  That would mean the cost of looking for the .groupEnd only happens when parsing fields within a group, but would come at some more code cost since we'd be adding another Decoder.
Thoughts?


Constructive criticism

A criticism I think constructive, the mod is still heavy, takes a lot of fps, if you can optimize it / improve I appreciate it.

What are your PC specs huh? I literally have no issues at all.

yeah it take some fps, like if the UI wanted to show all time, then it like loop, or is because it add many features like the weapon wheel, and idk what more
my pc is not the best
windows 8.1, 4gb ram, HD Graphics 4000(yeah its old, 2014), I3 2.4ghz(quad core, but game only use 1)


subprocess.CalledProcessError: Command '['/usr/bin/make', '-j12', 'retro']' returned non-zero exit status 2.

Issue summary
When I try to install gym-retro with the command pip3 install gym-retro, the make task appears to fail when compiling Genesis Plus GX. Something about multiple definitions of the config and zbank_memory_map symbols.
System information

[Operating system] Linux (POP! OS 22.04)
[Python version] 3.7, 3.8, 3.11
[Gym Retro version] 0.7.11

Whoops, forgot to attach logs. Hopefully this is enough.
stderr.txt

Hey, I've got the same error and issue. But I'm not sure if the build crashes at the same identical build.
Running debian-bullseye with python 3.9


Part 1: Giant Brains - unavailable

It's not available in youtube.

Appears it's been blocked due to a copyright claim by BBC. I was able to find it on via another youtube playlist but I will refrain from linking to it for the time being.

All videos of the miniseries is sadly gone


ionic serve -l chrome blank screen issue

@alakra @alexbbt Below is the ionic info

I'm getting blank screen in chrome and working in safari browser.

This issue was moved to ionic-team/ionic-cli#2400


[SDK] Relax the requirement for LazyMint

I think this change makes sense but would still want a @thirdweb-dev/product review before we merge this

This makes sense to me, as long as none of the classes depending on these extensions use functions that are part of the LazyMintAbi extension - which I think might be the case. Would be good to double check this

This makes sense to me, as long as none of the classes depending on these extensions use functions that are part of the LazyMintAbi extension - which I think might be the case. Would be good to double check this

I assume this should fail build / get caught in tests?


fixes apollo debug & warn log, control log out by slf4j xml file.

fixes apollo debug & warn log, control log out by slf4j xml file.

Pull Request Test Coverage Report for Build 976

0 of 0   changed or added relevant lines in 0 files are covered.
73 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.009%) to 68.791%

Files with Coverage Reduction
New Missed Lines
%

sharding-jdbc/sharding-jdbc-core/src/main/java/org/apache/shardingsphere/shardingjdbc/jdbc/core/context/ShardingRuntimeContext.java
1
96.67%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/text/sctl/utils/SCTLUtils.java
1
85.71%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/sql/execute/SQLExecuteCallback.java
5
0.0%

sharding-proxy/sharding-proxy-backend/src/main/java/org/apache/shardingsphere/shardingproxy/backend/schema/LogicSchema.java
16
0.0%

sharding-core/sharding-core-execute/src/main/java/org/apache/shardingsphere/core/execute/metadata/TableMetaDataLoader.java
50
0.0%

Totals

Change from base Build 571:
0.009%

Covered Lines:
11680

Relevant Lines:
16979

💛  - Coveralls


Check to see if Credential Guard is enabled on server - Dev3.0.0

Include check for credential guard in dev3.0.0
#303

Added in 543cad74d4b8f27860263f28580c54b130b68947

Added to Dev3.0.0


IndexError when deleting from lists

Problem:
When deleting multiple values from lists using dpath.util.delete(...) the line cur = cur[item[0]] throws an index error, because indices of subsequent paths aren't adjusted when a previous path deletion modified the list.
Simple solution:
Remove paths in inverse order, by inserting paths.reverse() at line 62 of util.py.
 Please try with the latest version and let us know if this persists.


Rename creds rbac CRs for agent platform

What this PR does / why we need it:
"Cloud Credentials" for the Agent platform are given as RBAC CRs which enable the capi provider to watch and bind agents from a specific namespace. With current naming if the hostedControlPlane namespace happens to be the same than hostedCluster.Spec.Platform.Agent.AgentNamespace RBAC naming might clash.
This PR sets RBAC naming for Agent platform consistent with other references and add unit tests.
Which issue(s) this PR fixes (optional, use fixes #<issue_number>(, fixes #<issue_number>, ...) format, where issue_number might be a GitHub issue, or a Jira story:
Fixes #934
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/lgtm

/lgtm


How do I shake the controller to recharge my flashlight?

I never played a PlayStation game before, so I am not familiar with controllers at all.  In The Last of Us, I am supposed to shake the controller or something to recharge the flashlight.  But I don't know how to do that.  I found a forum thread that said something about six-axis, whatever that means.  Is there a way to do this in DualShock4 Emulator?  And if not, can you implement that feature in the near future?  Thank you.

Hi, unfortunately this feature is not supported. In Last of Us, this feature is not very important and you can complete the game without it.


[Bug]: Passing '--port' flag breaks communication with Chromadb in Docker Compose setting

What happened?
When deploying ChromaDB in a Docker Compose setting, specifying the --port flag, even when supplying the default port of 8000, causes attempts at connecting to the db from other containers to fail.
To see this in action, launch the compose and exec into the streamlit container and run
"curl -f http://chromadb:8000/api/v1/heartbeat"
when the offending 'command' line in the compose file is removed, this command succeeds, otherwise it fails
services:
  chromadb:
    build:
      context: chroma
      dockerfile: Dockerfile
    image: chromadb_speed:latest
    container_name: speed-db
    volumes:
      -  ${CHROMA_DB_DIR}:/chroma/chroma
    environment:
      - IS_PERSISTENT=TRUE
      - ANONYMIZED_TELEMETRY=TRUE
    healthcheck:
      test: [ "CMD", "curl", "-f", "http://<IP_ADDRESS>:8000/api/v1/heartbeat" ]
      interval: 5s
      retries: 2
      start_period: 5s
      timeout: 10s
    command: "--port 8000" # if you comment out this line this, the Streamlit container succeeds in connecting to chroma, leave it in and it fails
    expose:
    - 8000
  streamlit:
    depends_on:
        chromadb:
          condition: service_healthy
    image: streamlit_speed:latest
    container_name: speed-frontend
    environment:
      - CHROMA_IP=chromadb
      - CHROMA_PORT=8000
      - CHROMA_COLLECTION=${CHROMA_DB_COLLECTION}
      - CHROMA_DATABASE=${CHROMA_DB_DATABASE}
      - CHROMA_TENANT=${CHROMA_DB_TENANT}
      - AZURE_OPENAI_API_KEY=${AZURE_OPENAI_API_KEY}
    ports:
      - ${STREAMLIT_PORT}:${STREAMLIT_PORT}
    command:
      - --server.port
      - ${STREAMLIT_PORT}
    build:
      context: frontend
      dockerfile: Dockerfile
    healthcheck:
      test: ["CMD", "curl", "-f", "http://<IP_ADDRESS>:${STREAMLIT_PORT}/healthz"]
      interval: 5s
      timeout: 2s
      retries: 3

Versions
chromadb 0.4.24
python 3.10.12
WSL2 Ubuntu 22.04.4 LTS
Relevant log output
speed-frontend  | 2024-04-18 07:33:23.696 Uncaught app exception
speed-frontend  | Traceback (most recent call last):
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 198, in _new_conn
speed-frontend  |     sock = connection.create_connection(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 85, in create_connection
speed-frontend  |     raise err
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/util/connection.py", line 73, in create_connection
speed-frontend  |     sock.connect(sa)
speed-frontend  | ConnectionRefusedError: [Errno 111] Connection refused
speed-frontend  |
speed-frontend  | The above exception was the direct cause of the following exception:
speed-frontend  |
speed-frontend  | Traceback (most recent call last):
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 793, in urlopen
speed-frontend  |     response = self._make_request(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 496, in _make_request
speed-frontend  |     conn.request(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 400, in request
speed-frontend  |     self.endheaders()
speed-frontend  |   File "/usr/local/lib/python3.10/http/client.py", line 1278, in endheaders
speed-frontend  |     self._send_output(message_body, encode_chunked=encode_chunked)
speed-frontend  |   File "/usr/local/lib/python3.10/http/client.py", line 1038, in _send_output
speed-frontend  |     self.send(msg)
speed-frontend  |   File "/usr/local/lib/python3.10/http/client.py", line 976, in send
speed-frontend  |     self.connect()
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 238, in connect
speed-frontend  |     self.sock = self._new_conn()
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connection.py", line 213, in _new_conn
speed-frontend  |     raise NewConnectionError(
speed-frontend  | urllib3.exceptions.NewConnectionError: <urllib3.connection.HTTPConnection object at 0x7f42b90425f0>: Failed to establish a new connection: [Errno 111] Connection refused
speed-frontend  |
speed-frontend  | The above exception was the direct cause of the following exception:
speed-frontend  |
speed-frontend  | Traceback (most recent call last):
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 486, in send
speed-frontend  |     resp = conn.urlopen(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py", line 847, in urlopen
speed-frontend  |     retries = retries.increment(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/urllib3/util/retry.py", line 515, in increment
speed-frontend  |     raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
speed-frontend  | urllib3.exceptions.MaxRetryError: HTTPConnectionPool(host='chromadb', port=8000): Max retries exceeded with url: /api/v1/tenants/default_tenant (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f42b90425f0>: Failed to establish a new connection: [Errno 111] Connection refused'))
speed-frontend  |
speed-frontend  | During handling of the above exception, another exception occurred:
speed-frontend  |
speed-frontend  | Traceback (most recent call last):
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/api/client.py", line 438, in _validate_tenant_database
speed-frontend  |     self._admin_client.get_tenant(name=tenant)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/api/client.py", line 486, in get_tenant
speed-frontend  |     return self._server.get_tenant(name=name)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/telemetry/opentelemetry/__init__.py", line 127, in wrapper
speed-frontend  |     return f(*args, **kwargs)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/api/fastapi.py", line 197, in get_tenant
speed-frontend  |     resp = self._session.get(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 602, in get
speed-frontend  |     return self.request("GET", url, **kwargs)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 589, in request
speed-frontend  |     resp = self.send(prep, **send_kwargs)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/requests/sessions.py", line 703, in send
speed-frontend  |     r = adapter.send(request, **kwargs)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/requests/adapters.py", line 519, in send
speed-frontend  |     raise ConnectionError(e, request=request)
speed-frontend  | requests.exceptions.ConnectionError: HTTPConnectionPool(host='chromadb', port=8000): Max retries exceeded with url: /api/v1/tenants/default_tenant (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f42b90425f0>: Failed to establish a new connection: [Errno 111] Connection refused'))
speed-frontend  |
speed-frontend  | During handling of the above exception, another exception occurred:
speed-frontend  |
speed-frontend  | Traceback (most recent call last):
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/streamlit/runtime/scriptrunner/script_runner.py", line 584, in _run_script
speed-frontend  |     exec(code, module.__dict__)
speed-frontend  |   File "/app/src/0_🤖_Chat.py", line 44, in <module>
speed-frontend  |     chroma_client = chromadb.HttpClient(
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/__init__.py", line 197, in HttpClient
speed-frontend  |     return ClientCreator(tenant=tenant, database=database, settings=settings)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/api/client.py", line 144, in __init__
speed-frontend  |     self._validate_tenant_database(tenant=tenant, database=database)
speed-frontend  |   File "/usr/local/lib/python3.10/site-packages/chromadb/api/client.py", line 440, in _validate_tenant_database
speed-frontend  |     raise ValueError(
speed-frontend  | ValueError: Could not connect to a Chroma server. Are you sure it is running?

@MathiasToftas, thanks for the example and elaborate explanation. We recently changed the Dockerfile so that any params given in command are passed to uvicorn. Testing it locally, I can tell that it won't work with just --port
uvicorn chromadb.app:app --port 9001

INFO:     Started server process [6295]
INFO:     Waiting for application startup.
INFO:     Application startup complete.
INFO:     Uvicorn running on http://<IP_ADDRESS>:9001 (Press CTRL+C to quit)

See https://github.com/chroma-core/chroma/blob/729e6578d5649e2c9a8f586b35d33629e52c61e4/docker-compose.yml#L18 for all params that should be passed to uvicorn (called in docker entry point).

Okay, so you need to add all of the possible arguments if you want to change any single one? Tried it and it works, so issue solved, thanks.


Updated Solid Queue erro

Hi,
When trying to run my app (with the puma plugin), I get this error:
SolidQueue-0.6.0 Error registering Supervisor(fork) (44.5ms)  pid: 12111, hostname: "d43b4061bd6a", name: "supervisor(fork)-8be0856b46aaed9d389a", error: "ActiveModel::UnknownAttributeError unknown attribute 'name' for SolidQueue::Process."
11:56:05 web.1  | SolidQueue-0.6.0 Started Supervisor(fork) (51.9ms)  pid: 12111, hostname: "d43b4061bd6a", process_id: nil, name: "supervisor(fork)-8be0856b46aaed9d389a"

Any ideas?

Hey @rctneil, yes! It looks like you're missing a migration. Could you try the instructions here to fix the problem?

Thankyou @rosa !


Could we have an IF-ELSE-END block

I'm currently using the WHILE block (to which I cannot find documentation), but this is awkward and unwieldy. My specific use case: It is cheaper to determine whether some process should be augmented with a google search, than doing the search in every instance. I'd like to execute that chain of blocks only if a google search is deemed necessary.

Hi @mholtzhausen. Will release the documentation of the while block :+1:
Can you describe your use-case to better understand if it would be best covered by such blocks or the ability to run Dust apps from code blocks?

Hi. @spolu. I am busy with a fact-checking bot, that uses a bunch of agents to do different things. some of those agents may have conditional application -- not all facts should be verified by going online (math proofs etc) I am was hoping to use simple conditional statements to slectively apply a block of actions.

The plan here is to allow executing an another Dust app from a Code block which is something we plan to build but are not focused on right now.


⚠ Site ANTS has degraded performance

In c48a136, Site ANTS (https://ants.gouv.fr) experienced degraded performance:

HTTP code: 200
Response time: 6104 ms

Resolved: Site ANTS performance has improved in 6426018.


refactor(reactivity): encapsulate reactive handlers in class

encapsulate reactive handlers in class:

BaseReactiveHandler: has the get function that all reactive objects use
MutableReactiveHandler: extend BaseReactiveHandler with set, deleteProperty, has, ownKeys
ReadonlyReactiveHandler: extend BaseReactiveHandler with set & deleteProperty warners

/ecosystem-ci run

Thank you for your excellent work! I would like to know what motivated your PR. Does it have any impact on performance? If so, could you please provide benchmark results to validate this point? I am also concerned about whether it will increase the size of the bundle. It seems that classes are more difficult to tree-shake compared to functions.
If you can provide some evidence that your PR will make Vue better, we would be more than happy to merge it!

Thanx for the replay, this my first contribute to vue and I was trying to understand how the core works. My main motivation here is to organize the code to make it easier to understand and work with.
Before this PR createGetter & createSetter returned functions with different parameters, so they kinda worked like a new class initializer, I thought it would be better to encapsulate them in a class that also implements the ProxyHandler needed.
As for impact on performance, I'm not a JS expert, but I believe this code should allocate and use less memory, if you can guide me how, I would like to test it and get some benchmark results to validate this point.
As for bundle size concern, this was the main reason I separated them to 3 classes, if only readonlyHandlers was used, MutableReactiveHandler would be tree-shaked, (sample with rollup).

I did a simple benchmark test via https://github.com/basvanmeurs/vue-next-benchmarks:
Based on the latest version
Use Vue3: https://cdnjs.cloudflare.com/ajax/libs/vue/3.3.4/vue.global.js
Benchmarks: reactiveObject
Available: ref,computed,watch,watchEffect,mix,reactiveObject,reactiveMap,reactiveArray
vue.global.js:10552 You are running a development build of Vue.
Make sure to use the production build (*.prod.js) when deploying for production.
Benchmark: reactiveObject
create reactive obj x 183,736 ops/sec ±164.46% (5 runs sampled)
write reactive obj property x 4,866,484 ops/sec ±0.42% (68 runs sampled)
write reactive obj, don't read computed (never invoked) x 4,872,878 ops/sec ±0.26% (69 runs sampled)
write reactive obj, don't read computed (invoked) x 3,021,506 ops/sec ±0.25% (66 runs sampled)
write reactive obj, read computed x 2,183,469 ops/sec ±0.18% (67 runs sampled)
write reactive obj, don't read 1000 computeds (never invoked) x 4,812,272 ops/sec ±0.20% (67 runs sampled)
write reactive obj, don't read 1000 computeds (invoked) x 42,809 ops/sec ±0.24% (69 runs sampled)
write reactive obj, read 1000 computeds x 6,859 ops/sec ±0.34% (66 runs sampled)
1000 reactive objs, 1 computed x 11,690 ops/sec ±0.58% (63 runs sampled)
Based on this PR
Use Vue3: ./vue.global.js
Benchmarks: reactiveObject
Available: ref,computed,watch,watchEffect,mix,reactiveObject,reactiveMap,reactiveArray
vue.global.js:10552 You are running a development build of Vue.
Make sure to use the production build (*.prod.js) when deploying for production.
Benchmark: reactiveObject
create reactive obj x 574,722 ops/sec ±51.86% (13 runs sampled)
write reactive obj property x 4,636,881 ops/sec ±0.25% (69 runs sampled)
write reactive obj, don't read computed (never invoked) x 4,620,616 ops/sec ±0.24% (69 runs sampled)
write reactive obj, don't read computed (invoked) x 2,687,439 ops/sec ±3.70% (61 runs sampled)
write reactive obj, read computed x 2,051,574 ops/sec ±1.19% (68 runs sampled)
write reactive obj, don't read 1000 computeds (never invoked) x 4,495,859 ops/sec ±0.34% (67 runs sampled)
write reactive obj, don't read 1000 computeds (invoked) x 41,264 ops/sec ±2.62% (66 runs sampled)
write reactive obj, read 1000 computeds x 6,645 ops/sec ±2.37% (38 runs sampled)
1000 reactive objs, 1 computed x 11,758 ops/sec ±0.32% (68 runs sampled)

We need some more objective reasons to refactor existing code, such as improvements on performance or maintainability and need to ensure the refactoring doesn't introduce negative impacts on performance.

I've done some benchmark tests (same by @edison1105) and got similar results:

reactive obj create has a huge positive impact (200% - 700%)
get/set reactive obj props has small negative impact (1% - 5%)

Benchmark
Result (this PR)
Result (commit 623ba51)
Ratio

create reactive obj
1,152,329 ops/sec ±57.45% (15 runs sampled)
156,139 ops/sec ±126.78% (7 runs sampled)
+638.01%

write reactive obj property
4,224,204 ops/sec ±0.29% (68 runs sampled)
4,398,603 ops/sec ±0.20% (68 runs sampled)
-3.96%

write reactive obj, don't read computed (never invoked)
4,240,543 ops/sec ±0.31% (68 runs sampled)
4,391,671 ops/sec ±0.25% (67 runs sampled)
-3.44%

write reactive obj, don't read computed (invoked)
2,879,259 ops/sec ±0.77% (67 runs sampled)
2,968,753 ops/sec ±0.23% (68 runs sampled)
-3.01%

write reactive obj, read computed
2,034,185 ops/sec ±0.23% (67 runs sampled)
2,103,718 ops/sec ±0.21% (68 runs sampled)
-3.31%

write reactive obj, don't read 1000 computeds (never invoked)
4,195,139 ops/sec ±0.42% (67 runs sampled)
4,306,288 ops/sec ±0.24% (69 runs sampled)
-2.58%

write reactive obj, don't read 1000 computeds (invoked)
57,195 ops/sec ±0.58% (66 runs sampled)
57,932 ops/sec ±0.63% (66 runs sampled)
-1.27%

write reactive obj, read 1000 computeds
8,353 ops/sec ±0.30% (68 runs sampled)
8,378 ops/sec ±0.27% (67 runs sampled)
-0.3%

1000 reactive objs, 1 computed
16,125 ops/sec ±0.56% (67 runs sampled)
16,963 ops/sec ±0.47% (64 runs sampled)
-4.94%

[!NOTE]
I did multiple runs for the benchmark, the table above is the average results I got that was also close to @edison1105 test, following is the best result I got for create reactive obj:

this PR: 5,439,439 ops/sec ±8.71% (48 runs sampled)
commit 623ba51: 638,106 ops/sec ±89.24% (10 runs sampled)

As for the build size impact, there is a small build increase (~0.05kb) for this PR:
compiler-dom.global.prod.js min:56.57kb / gzip:21.32kb / brotli:19.15kb
reactivity.global.prod.js min:12.01kb / gzip:4.42kb / brotli:4.08kb
runtime-dom.global.prod.js min:83.82kb / gzip:31.80kb / brotli:28.71kb
vue.global.prod.js min:128.50kb / gzip:48.14kb / brotli:43.18kb
vue.runtime.global.prod.js min:83.82kb / gzip:31.80kb / brotli:28.73kb

commit 623ba51:
compiler-dom.global.prod.js min:56.57kb / gzip:21.32kb / brotli:19.15kb
reactivity.global.prod.js min:11.96kb / gzip:4.44kb / brotli:4.09kb
runtime-dom.global.prod.js min:83.76kb / gzip:31.84kb / brotli:28.72kb
vue.global.prod.js min:128.45kb / gzip:48.17kb / brotli:43.27kb
vue.runtime.global.prod.js min:83.77kb / gzip:31.83kb / brotli:28.77kb


Loader is detected as malware by windows smartscreen

Hi, as the title says.
I tried to run the latest release and smartscreen blocked the loader and listed it as malware.
Is it because of the anti-cheat feature or unintended?

See #148 for more info. tl;dr - It's a heuristic based false positive, there isn't anything we can really do about it.


Additional info for EndDateForRetentionHold

We had an escalation where customer used the EndDateForRetentionHold parameter and after the end date saw that RetentionHoldEnabled was still set to True. Wanting to add this disclaimer that using this parameter does not flip it back to True.

Docs Build status updates of commit 71ae55b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 89ef390:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Set-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Rate Limit on Kavita APIs

Komf can sometimes call series update apis quite fast and uncontrolled when reacting to new media added. However this API is quite heavy due to the scope of all the tables needing to be updated or new entities created. Users have reported that komf can spike their CPU to 100% for an extended time.
It would be great if komf could rate limit itself on calling the API to give Kavita time to properly perform the actions. Let me know your thoughts @Snd-R, I'd be happy to reach a middle ground.

What do you think would be a good wait interval? Would 2 requests per second be good?

I think that would be great.

Let me chime in and say that i would like this to be configurable in the application.yml.
kavita:
  baseUri: "http://localhost:5000" #or env:KOMF_KAVITA_BASE_URI
  apiKey: "ft34tg5uzredu4tz5e34qwz5eqw5" #or env:KOMF_KAVITA_API_KEY
  ratelimit: 2 #Max calls to Kavita API per Second (Keep between 2-5)

Thanks Snd-R, I think this is going to be great for a lot of users with large libraries. @DieselTech :)


[release-v1.2] Add services to controller cluster role

Part of https://github.com/openshift-knative/serverless-operator/pull/1527 and Matthias's thread on Slack

/cherry-pick release-v1.3

/retest

/retest

/retest-required
{  "e2e-aws-ocp-410" test steps failed: "e2e-aws-ocp-410" pod "e2e-aws-ocp-410-test" failed: the pod ci-op-j1i9gi96/e2e-aws-ocp-410-test failed after 1h22m34s (failed containers: test): ContainerFailed one or more containers exited

Perhaps a container in knative-eventing namespace is coming up?

/retest

/retest

Wonder why this does not go in :-(

/retest-required

/retest

some error creating buildah builder

... error creating buildah builder
/retest

/retest
buildah

/retest
/retest
GO IN!!!!! 11!!!

/joke

/retest

/retest

/test 410-images
error: build error: error creating build container: initializing source docker://image-registry.openshift-image-registry.svc:5000/ci-op-jf5g9tsp/pipeline@sha256:4250fa7c9aa6517cc7145839247a6d70f3fe4d5df72ed91767ee0edc6538affa: pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: lookup image-registry.openshift-image-registry.svc on <IP_ADDRESS>:53: no such host

error: build error: error creating build container: initia...penshift-image-registry.svc on <IP_ADDRESS>:53: no such host

/test 410-images

/retest
Trying to pull image-registry.openshift-image-registry.svc:5000/ci-op-4r9v59dd/pipeline@sha256:aa9ba17502f6c1d1fe6587ef9275437fa51030ec5a3981704d8bcb7a5f51af92...
error: error creating buildah builder: initializing source docker://image-registry.openshift-image-registry.svc:5000/ci-op-4r9v59dd/pipeline@sha256:aa9ba17502f6c1d1fe6587ef9275437fa51030ec5a3981704d8bcb7a5f51af92: pinging container registry image-registry.openshift-image-registry.svc:5000: Get "https://image-registry.openshift-image-registry.svc:5000/v2/": dial tcp: i/o timeout

/retest

/close
most of this was merged in here:
https://github.com/openshift-knative/eventing-kafka-broker/pull/230


Update sbt to 1.4.6

Updates org.scala-sbt:sbt from 1.1.6 to 1.4.6.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

labels: library-update, semver-minor

Superseded by #82.

Superseded by #82.


feat: multi-line templ/script/css function params syntax highlighting

Overview
This adds more verbose regex patterns to templ and script function begin patterns as well as adds support for multi-line params on each of these function types.
Templ Functions
Before

After

Script Functions
Before

After

I just pushed a third commit that addresses css functions with params/multi-line params. With this I also refactored the old organization to instead have one large object with nested patterns for the internals of the function to avoid duplicate patterns for css property names.
Before

After

Perfect, thanks for all the support on this!


Add in coveralls badge

Because I like badges.

Added and working. Need to work on that Code Coverage though.


feat: add ability to manually define asset descriptions

closes https://github.com/shapeshift/lib/issues/345
Tested the feature with the Ethereum caip19:

descriptions.json
{
  "eip155:1/slip44:60": "Description test override"
}

Tests seem to pass too, even if I have a lot of errors in my environment

hey @NeOMakinG - thanks for the PR, looks great.
i updated your PR title so it'll pass commitlint in CI, and a suggested to slightly more strongly type the file definition - our asset descriptions should always be strings.
if you accept the suggestion, CI should rerun with your new PR title and should pass.
so we can compensate you for your contribution - how long did you spend on this?

Hey @0xdef1cafe, thanks for the great suggestion, did accept it!
Took me around 1 hour, including installing the project, configuring, and testing

But I'll contribute on other things, don't worry about this one if you want :)
Feel free to contact me if you've some front and integration stuff, it will be a pleasure!

But I'll contribute on other things, don't worry about this one if you want :)
Feel free to contact me if you've some front and integration stuff, it will be a pleasure!

thanks ser. i wasn't expecting this to get picked up over the weekend so quickly before i had the chance to create a bounty for it. i'm going to create a gitcoin bounty, can you please apply for it, i'll accept you, you can mark the work as done, and when @0xean is back next week he'll send you a tip so you get the reputation/record on gitcoin.

Waiting for it! Thanks

@0xdef1cafe I'm not at home, tried to fix the import in order to unblock the CI, but maybe it's not enough, overwise I'll run lint-fix when at home!

Should be fixed @0xdef1cafe if you rerun the CI I think so

Details

you got past lint but failed tests in CI 🥲

Details

you got past lint but failed tests in CI 🥲

Damn! Gonna take a look tomorrow, the strange thing is that the test ran well on my env


feat: check for active messages in StatusModule.active

Fixes #19

My last changes are in here too. Forgot to rebase, but merging woudl still work :)

Hum, not sure that it's the proper way of doing it

Closing as invalid following the discussion in #19


Unable to resolve jws/lib/sign-stream.js

Just installed<EMAIL_ADDRESS>and required the module, then immediately got the error "Cannot find node_modules/jws/lib/sign-stream.js"
Context: Running this on React Native

I am not familiar with React Native, but the file is there. Try rm -rf node_modules && npm i

Having the same issue as @calclavia. I tried reinstalling the node module but still no luck. It seems like several dependencies are missing. I manually stream, only to see that more modules were missing.

@jfromaniello Tried that as well. Did not fix it.

Any update on this issue? Still having this problem...

Just got this problem today trying to use 7.2.1.
Using React-Native 0.41

According to this https://github.com/facebook/react-native/issues/3874#issuecomment-167150393

Node core modules cannot be used inside React Native as it's a completely different environment

I only needed to decode the token and switched to using this https://github.com/auth0/jwt-decode
In any case, this issue can be closed.  It isn't really applicable to node-jsonwebtoken itself.

Is there any React-Native alternative that can performsign() with HMAC SHA256?
Can't find any that would work.

@anders-g-hansen could you please let me know how you managed to make it work with jwt-decode https://github.com/auth0/node-jsonwebtoken/issues/221#issuecomment-283108676

You can try this module react-native-pure-jwt

@anders-g-hansen could you please let me know how you managed to make it work with jwt-decode #221 (comment)

didn't see passing the key to decrypt in this package. Wonder how it decodes.

jwt does not need secret key to decode content, secret key is for validation


Fix: search result page refreshing all items

This pull request includes significant refactoring and improvements to the SearchPage component and related services. The most important changes include the removal of the loading spinner, the separation of media and person search functions, and the simplification of the pagination logic.
Refactoring and Simplification:

src/frontend/src/pages/SearchPage.jsx: Removed the loading spinner and the filter functionality, and separated the media and person search functions into performMediaSearch and performPersonSearch. This improves readability and maintainability. [1] [2] [3] [4] [5]

Pagination Logic:

src/frontend/src/components/Pagination/Pagination.jsx: Updated the handlePageChange function to prevent redundant page changes by checking if the new page is different from the current page.

Service Updates:

src/frontend/src/services/personService.js: Updated the fetchPersons function to accept a single query object and log query parameters, simplifying the function and improving debugging capabilities.

That is a backend issue, if you search with capital letters, a search should be done with lower case letters.

There is still no titles and there is a error or something weird is happening here

And the person on best match jennifer aniston is not relevant, can that be fixed

https://github.com/RUC-MSc-CS-CIT-2024/portfolio_subproject_3/pull/154?new_mergebox=false#issuecomment-2545660816


Edge case of / inside string

const test = {
  test() {
    what('ACCEPTS */*...')
  }
}

const test = {
  'test'() {
    what('ACCEPTS */*...')

    const ohno = 'what'
  }
}

Looks like so:

Not sure is
const test = {
  'test'() {
    what('ACCEPTS */*...')

    const ohno = 'what'
  }
}```

Will follow the spec. But need to look into it first.

String is ok
PropertyName[Yield] :
  LiteralPropertyName
  ComputedPropertyName[?Yield]

LiteralPropertyName :
  IdentifierName
  StringLiteral
  NumericLiteral

Supports string as method name now.


Updating all the colab notebooks

Problem
As of now, colab is having TensorFlow 2.x by default but Tensorflow Lucid works on Tensorflow 1.x .
But in the colab notebooks, there is no installation of TensorFlow 1.x. So, it might causes errors and It's a big issue.
Solution
I'll love to address this issue by proper documentation and code which implies the installation of TensorFlow 1.x and the Tensorflow Lucid as of now supports only Tensorflow 1.x.
Please assign me this task.

Hey, @colah would you please assign me this task

@abhinavsp0730 : A PR on this would be very appreciated!
(1) %tensorflow_version 1.x can be used to get colab to use TF version 1.x
(2) While you are at it, it would be great if notebooks could also be ported to use the most recent version of lucid!

@colah I'll love to do this task.
(1) I'll do the first task
(2) Would you please tell me how to update all the notebooks for the latest version of lucid.
!pip install !pip install quiet lucid will these do the task?

Maybe !pip install --quiet --upgrade-strategy=only-if-needed lucid?
There have been some API changes, so some notebooks may break once you do this.

Okay then lemme do the task 1 first .
And for task 2 I'll  add this !pip install --quiet --upgrade-strategy=only-if-needed lucid and then I'll run all the cell if it works fine I'll send PR for that notebook.
what are you thoughts in this?

Sounds great!

Okay, I'll start doing work in this.


Add/Specify License

As a developer employed to develop, for any "company" (in the US anyways) to use this software legally, you have to have a license specified, attached, or referenced.
Please specify, declare, attach, or reference which license this software is under somewhere in your README, or create a LICENSE file for the repo.
Can't wait to use it!

Done! Added MIT license.

Awesome! Thanks!


Weird errors trying to start using fastparse

Hi!
I'm very newbie to Scala and a total newbie using fastparse.
I've created a very simple SBT project and tried to compile and run some simple parsers from the web examples, but I get a lot of compilation errors on sbt like this:
[error] /home/freinn/parsertests/src/main/scala/Main.scala:30: No implicit view available from String => fastparse.core.Parser[V].
[error]     val ab = P( "a".rep ~ "b" )
[error]                 ^
[error] one error found
error Compilation failed
Or another one:
[error] /home/freinn/tecsisaDSL/src/main/scala/Main.scala:22: value ~ is not a member of String
[error]     val ab = P("a" ~ "b")
[error]                    ^
[error] /home/freinn/tecsisaDSL/src/main/scala/Main.scala:41: too many arguments for method println: (x: Any)Unit
[error]         println(ParserSet.val1, ParserSet.val2)
[error]                ^
[error] two errors found
I'm using 0.3.7 with the following line on build.sbt:
libraryDependencies += "com.lihaoyi" %% "fastparse" % "0.3.7"
I did the import (import fastparse.all._) in the beginning of my file and created an object ParserSet { ... } with all the copied/pasted code from the web examples.

Probably the same as https://github.com/lihaoyi/fastparse/issues/72, upgrading to scalaVersion := "2.11.8" should make it go away i think...

I'm getting this error using scala 2.13. I could work around it by surrounding the first string with P(). So instead of:
val ab = P("a" ~ "b")

I have:
val ab = P(P("a") ~ "b")

you are probably missing import fastparse._


hlin011 ceda-cc report for GEM-NEMO v20221004

The data passed checks except comments below:

variables (hus, pr, prc etc.) missing cell_methods attribute in all files,  for example:
C4.002.005: [variable_ncattribute_mipvalues]: FAILED:: Variable [hus] has incorrect attributes: cell_methods="Attribute not present" [correct: "area: mean time: point"]
Need to specify cell_methods from the corresponding snapsi table

time coordinate units need to be 'days since 1970-01-01' rather than 'seconds since 1970-01-01'.
Error:
C4.003.001: [time_attributes]: FAILED:: time units [seconds since 1970-01-01 00:00:00.0 0:00] attribute not set correctly to "days since ....."
C4.003.001: [time_attributes]: FAILED:: Time: required attribute calendar missing

Please change the global attributes 'realization_index', 'initialization_index' and 'physics_index' from strings to tuples on all files.
For example, currently:
realization_index = "1LL"
when it should be:
realization_index = 1LL
Error:
C4.002.006: [global_ncattribute_cv]: FAILED:: Global attributes do not match constraints: [('realization_index', '1LL', "Value is not instance of required class (<class 'tuple'>): 1LL -- <class 'str'>"), ('initialization_index', '06', "Value is not instance of required class (<class 'tuple'>): 06 -- <class 'str'>"), ('physics_index', '1LL', "Value is not instance of required class (<class 'tuple'>): 1LL -- <class 'str'>"), ('forcing_index', '1LL', "Value is not instance of required class (<class 'tuple'>): 1LL -- <class 'str'>")]

Add attribute missing_value for variables with _FillValue attribute:
missing_value = 1e+20
For data with _FillValue attribute, the _FillValue should be 1e+20 and is currently 9.96921e+36(variables tntnd and utntnd) or 9.999e+20. Please change so that _FillValue = 1e+20
This error applies to:
all files with variables tntnd and utntnd in '/control/' and '/nudged/' directories and
filenames with XX replaced with ensemble number in '/nudged/' directory:
ps_6hrPt_GEM-NEMO_nudged_s20191001_r1iXXp1f1_gr_20191001-20191115.nc
psl_6hrPt_GEM-NEMO_nudged_s20191001_r1iXXp1f1_gr_20191001-20191115.nc
rlut_6hrPt_GEM-NEMO_nudged_s20191001_r1iXXp1f1_gr_20191001-20191115.nc
tas_6hrPt_GEM-NEMO_nudged_s20191001_r1i10p1f1_gr_20191001-20191115.nc
Error:
C4.002.005: [variable_ncattribute_mipvalues]: FAILED:: missing_value must be present if _FillValue is [tntnd]
C4.002.005: [variable_ncattribute_mipvalues]: FAILED:: Variable [tntnd] has incorrect attribute _FillValue=9.96921e+36 [correct: 1e+20]

New errors from second CEDA-cc check:

The mip_era global attribute needs to be set to 'CMIP6' and is currently 'SNAPSI' for all files.
Error:
C4.002.006: [global_ncattribute_cv]: FAILED:: Global attributes do not match constraints: [('mip_era', 'SNAPSI', "['CMIP6']")]

Files for variables 'siconca' and 'tos' have a missing attribute error. The the attribute missing_value must be added when the _FillValue attribute is present. Please could you add variable attribute e.g. tos:missing_value = 1.e+20f.
Error:
C4.002.005: [variable_ncattribute_mipvalues]: FAILED:: missing_value must be present if _FillValue is [tos]

Files for variable 'va' have the incorrect cell_methods attribute. The cell_methods attribute needs to be changed from "time: point" to "longitude: mean time: point".
Error:
C4.002.005: [variable_ncattribute_mipvalues]: FAILED:: Variable [va] has incorrect attributes: cell_methods="time: point" [correct: "longitude: mean time: point"]

Just to confirm what Hai mentioned in his email regarding the mip_era attribute - we did make the late decision to switch the mip_era to 'SNAPSI'.