Value 0 has no mapping for key class org.spacehq.mc.protocol.data.game.world.block.value.GenericBlockValueType

I experienced this on 1.9.2 server
Full crashlog: http://pastebin.com/9LXgxNML
To reproduce, place a piston within render distance of the player and extend it

#169 should fix it.


After seven years of development [..]

After seven years of development, Avast open-sources its machine-code decompiler for platform-independent analysis of executable files.

I'm sorry this blog post indicates after seven years of development.
But how on earth 11 commits?

The internal git history doesn't seem to be made available with the public release.
The commit message of rev d9230cbc943783701ba9917c794910a0f3a6f730 states "Initial commit.", version 3.0, and includes 245 032 lines of code.
To peek an interest in the development that lead up to the version 3.0 release, it would be very interesting for the prior git history to be shared with the public. If that's possible or not is up to the authors to decide.

To open-source RetDec, we had to completely re-structure our original repository. Now, the code spans 26 repositories, where all of them are here on GitHub. Also, we had to replace some parts in our original code that would prevent us from open-sourcing the decompiler. Thus, we were unable to preserve our entire commit history (circa 35 000 commits).
Believe me that the initial commit did not happen overnight ;-). Also, even though I am listed as the commiter of the initial commit, the code represents work of 20-30 people. I hope this is fairly obvious, given the size of the code base.

@s3rva Thanks for clarification.


socket.accept() out of system resource

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
@app.post("/coagulantPrediction")
async def create_item(item: Item):
    starttime = time.strftime("%a %b %d %H:%M:%S %Y", time.localtime())
    print('starttime', starttime)
    rawjon = item.dict()
    all_pool_data = rawjon['dataInput']
    all_pool_result = []
    for i in range(0, len(all_pool_data)):
        one_pool_data = all_pool_data[i]
        one_pool_result = doPrediction(one_pool_data, MODEL_COA, MODEL_TUR)
        one_pool_result_dict = unparse_result(one_pool_result, one_pool_data)
        all_pool_result.append(one_pool_result_dict)
    rawjon.update({"dataOutput": all_pool_result})
    gc.collect()
    return rawjon

Description
I started post api and tested successed in postman. I write a timed program to call it.
But after 24 to 48 hours, the error happened
"
socket.accept() out of system resource
OSError: [Errno 24] Too many open files
"
I checked that all the IO stream is closed and I don't know  how to fix it.
The solution on google tells me to modify the number of ulimit in linux system.
But this way just append the error from 48 hours to 72 hours.
Could you help me ,thank you .
Operating System
Linux
Operating System Details
LINUX
FastAPI Version
0.70.0
Python Version
3.8
Additional Context
empty

Maybe you need check the file IO status again.
I can't get more info from you example code. : (


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-29-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4600

Questions ?
Please refer to the Backport tool documentation


Add Rootstock Network

Description
This PR adds support for Rootstock Network in uniswap sdk. Uniswap v3 contracts are deployed on Rootstock.
Uniswap v3 deployed on Rootstock
The addresses can be verified from the proposals here:
RFC:
https://gov.uniswap.org/t/deploy-uniswap-v3-on-rootstock-bitcoin-sidechain/22466
Rootstock Vote
https://www.tally.xyz/gov/uniswap/proposal/56?chart=2
ChainID: 30
Rootstock RPC: https://public-node.rsk.co
Deployed Contracts
v3CoreFactory	0xaF37EC98A00FD63689CF3060BF3B6784E00caD82
nftDescriptor	0xA231609CF5ee20b3FF9bd8bBfD1928737E6e6264
nonfungibleTokenPositionDescriptor	0x1519ab9C0bF7C8f261aCa6c58d59A152C95B3Ebc
nonfungibleTokenPositionManager	0x9d9386c042F194B460Ec424a1e57ACDE25f5C4b1
v3Migrator	0x16678977CA4ec3DAD5efc7b15780295FE5f56162
Multicall2	0x996a9858cDfa45Ad68E47c9A30a7201E29c6a386
proxyAdmin	0xE6c623e32eD33f29b4D7C002C01DebDA629e4604
tickLens	0x55B9dF5bF68ADe972191a91980459f48ecA16afC
descriptorProxy	0x2AECbeE0dc58e3419A52EEaF6Ea16C498BAeE24F
v3Staker	0x96481062BfAA29AdaaeBfC5FA6F46d9556F0150c
quoterV2	0xb51727c996C68E60F598A923a5006853cd2fEB31
swapRouter02	0x0B14ff67f0014046b4b99057Aec4509640b3947A
Permit2	0xFcf5986450E4A014fFE7ad4Ae24921B589D039b5
Universal Router	0x244f68e77357f86a8522323eBF80b5FC2F814d3E
Message Sender	0xf5F4496219F31CDCBa6130B5402873624585615a
Message Receiver	0x38aE7De6f9c51e17f49cF5730DD5F2d29fa20758
More About Rootstock
Website: https://rootstock.io/
Dev portal: https://rootstock.io/develop/
Explorer: https://explorer.rsk.co/ | https://rootstock.blockscout.com/
TVL: https://defillama.com/chain/RSK
Marketcap: https://coinmarketcap.com/currencies/rsk-infrastructure-framework/
Please consider the pull request i am working on Rootstock addition into uniswap interface. Merging this PR will help to move forward.
Let me know if anything needs to be changed i will promptly fix and reply. Many thanks Uniswap team 🙏
cc:
@jsy1218
@zzmp
@hensha256

@ahsan-javaiid I approved, but I didn't double check the deploy addresses. I trust you got them right :)

@ahsan-javaiid you can ignore lint failure and let us know if you can merge the PR.

@ahsan-javaiid you can ignore lint failure and let us know if you can merge the PR.

@jsy1218 Thank you so much for reviewing the pull request.
Yes. I double checked the addresses are correct.
I do not have merge permission in the repo so i would request for the merge.

@ahsan-javaiid do you also need Rootstock network to be routable? If so, you need to add another PR like https://github.com/Uniswap/smart-order-router/pull/501


adding control to slots not working properly

I'm using view_component 2.43.1 and view_component_storybook 0.10.1
Here is my sample code:
class ExampleModule::ExampleComponentStories < ViewComponent::Storybook::Stories
  story :example_slots do
    example_slot(
      example_text: text('example text 1')
    ).content(text('example content 1'))
  end
end

where example_slot is a collection. When I try to run rake view_component_storybook:write_stories_json, it gives me an error Validation failed: Param can't be blank. I traced it back to the slot story config control for example_text not being assigned a param.
Anyway, I tried going around this issue by manually assigning a param to the control by doing example_text: text('example text 1').param('example_slot1__example_text'). This made the rake task complete successfully. However, changing the value of the control doesn't reflect on the rendered component.  I traced this back to the text config param being appended by a prefix example_slot1__example_slot1__example_text.
My current workaround is to generate the json files with the param method call and then remove the param method call when I run storybook.
Let me know if you need more information. Thanks!

just getting back to this. I'm going to need to spend a bit if time walking through the use case and the PR.


Problem with UDP streams

Reality configs don't work with apps like Clubhouse. I'm using this config with the Shadowrocket app on iPhone.

Test other transports such as http and grpc


Error compiling sample project:  rcl/rcl.h: No such file or directory  #include <rcl/rcl.h>

Ubuntu 20.04
ROS Distro: Foxy
would you mind providing the answer for this?  I followed the example here and am still getting the same error you are getting.
I am in the project folder, and have included the micro_ros_espidf_component folder
Project:
- components
- -micro_ros_espidf_component
- CMakelists.txt
- main.c

Originally posted by @wegunterjrFIrefly in https://github.com/micro-ROS/micro_ros_espidf_component/issues/27#issuecomment-810404986
Also, tried it by going into the examples/int32_publisher and am getting the same error.

I have replicated this with a simple project and it works:
https://asciinema.org/a/G39IxQZkzipXSxrnbqepXh6iF

What version of esp-idf are you downloading? release4.2, release v4.3?
Do you delete the .espressif folder and run install.sh again when you switch versions of esp-idf?

In this video I'm on v4.3 but as you can see in our CI we support v4.1, v4.2 and v4.3: https://github.com/micro-ROS/micro_ros_espidf_component/actions/runs/703714929

this was helpful.  Not sure what I was doing wrong, but I am sure it was a combo of things.
If I follow the example on github and in the video you shared

adding the components folder  mkdir components
and cloning the micro_ros_esp_idf
-- cd components
-- clone the micro_ros_esp_idf
cd to main folder cd ..
source esp-idf (make sure you have added the pip3 install catkin_pkg lark-parser empy
idf.py

I find that if you have been changing versions of esp-idf, it is necessary to delete the ~/.espressif folder.

hate to reopen an issue, but planning to use microros and having similar issues:

idf.py version ESP-IDF v4.2.2-383-g125cf671e7
microros - foxy c0c003dc1d3c46410603b7879e819f94b25bf529 (HEAD -> foxy, origin/foxy)
pwd components/micro_ros_espidf_component/examples/int32_publisher
I did ensure all required software and the installation was followed...including the colcon and empy

It is failing at /main/main.c:11:10: fatal error: rcl/rcl.h: No such file or directory

ah..hmmm... The solution is that it wasn't completely downloading the micro_ros_src and other libraries which contain things like rcl.h   I deleted the entire micro_ros_espidf_component and tried again with the docker container and success.

I have replicated this with a simple project and it works:
https://asciinema.org/a/G39IxQZkzipXSxrnbqepXh6iF

In this video, you already start with a folder named int32_publisher. Could you show the steps you followed before this video started, please? I assumed the previous steps but I must have done something wrong because I am getting errors.

The folder is this one: https://github.com/micro-ROS/micro_ros_espidf_component/tree/humble/examples/int32_publisher

The folder is this one: https://github.com/micro-ROS/micro_ros_espidf_component/tree/humble/examples/int32_publisher

Thank Pablo, for your quick reply. So I downloaded the folder int32_publisher into my esp-idf folder. Then I followed the instructions exactly as in the video but when I run idf.py build it throws command not found. Then I go back to the esp-idf folder and run ./install.sh and . ./export.sh and pip3 install catkin_pkg lark-parser empy colcon-common-extensions . Then I go to the int32_publisher folder again and run idf.py set-target esp32 or idf.py menuconfig or  idf.py build and they all throw errors. I must be doing something wrong but I don't know what.

. ./export.sh
I tried repeating the steps a few times, also with other examples but this is the error I get.

What I don't know if I'm doing right is that I copy the example folder, in this case int32_publisher_custom_transport, from the repository. Then I follow the video, which clones the repository in the components folder which also copies again the examples.
Am I doing something wrong?

I am able to build these examples on Ubuntu 22.04, i am getting error while building in Ubuntu 20..


Jolokia client should use pod's hostname instead of ip address

Currently jolokia client uses pod ip to contact broker for managment operations.
This doesn't work when broker web console is configured with ssl + sniHost check.
The pod IP is dynamically allocated and is not suitable for such a case. Instead it should
be using host name.

What is the workaround here? For me this means the operator cannot do anything on the broker.

In next release the sniHostCheck will be disabled by default. See this commit https://github.com/artemiscloud/activemq-artemis-broker-kubernetes-image/commit/ba5d069c5e1927a69f6c132c24f3e0332fbbf317
right now you can manually do it using custom init image.


wont migrate

hi.. hoping you can help with this problem trying to start the migrate command
greg@ubuntuvm:~/laice$ python manage.py migrate
Traceback (most recent call last):
File "manage.py", line 22, in
execute_from_command_line(sys.argv)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/init.py", line 367, in execute_from_command_line
utility.execute()
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/init.py", line 359, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/base.py", line 294, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/base.py", line 342, in execute
self.check()
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/base.py", line 374, in check
include_deployment_checks=include_deployment_checks,
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/commands/migrate.py", line 62, in _run_checks
issues.extend(super(Command, self)._run_checks(**kwargs))
File "/home/greg/.local/lib/python2.7/site-packages/django/core/management/base.py", line 361, in _run_checks
return checks.run_checks(**kwargs)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/checks/registry.py", line 81, in run_checks
new_errors = check(app_configs=app_configs)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/checks/urls.py", line 14, in check_url_config
return check_resolver(resolver)
File "/home/greg/.local/lib/python2.7/site-packages/django/core/checks/urls.py", line 24, in check_resolver
for pattern in resolver.url_patterns:
File "/home/greg/.local/lib/python2.7/site-packages/django/utils/functional.py", line 35, in get
res = instance.dict[self.name] = self.func(instance)
File "/home/greg/.local/lib/python2.7/site-packages/django/urls/resolvers.py", line 313, in url_patterns
patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
File "/home/greg/.local/lib/python2.7/site-packages/django/utils/functional.py", line 35, in get
res = instance.dict[self.name] = self.func(instance)
File "/home/greg/.local/lib/python2.7/site-packages/django/urls/resolvers.py", line 306, in urlconf_module
return import_module(self.urlconf_name)
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/home/greg/laice/laice/urls.py", line 25, in
url( r'^api/', include( 'api.urls' ) ),
File "/home/greg/.local/lib/python2.7/site-packages/django/conf/urls/init.py", line 50, in include
urlconf_module = import_module(urlconf_module)
File "/usr/lib/python2.7/importlib/init.py", line 37, in import_module
import(name)
File "/home/greg/laice/api/urls.py", line 5, in
from stories.views import (
File "/home/greg/laice/stories/views.py", line 7, in
from laice.core.viewsets import ViewMappingMixin
ImportError: No module named core.viewsets

ahh worked it out
the laice/core directory did not have a init.pyc file


Add a demo framework.

Add a demo framework using pymesos and addict.
@windreamer feel free to close this PR if it is not appropriate.

LGTM


ci: cannot run Jest tests via IDE Webstorm

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Refactoring
[X] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Run any Jest test-file via Webstorm GUI:

It throws
Error: Jest: Failed to parse the TypeScript config file /Users/n.barsukov/WebstormProjects/taiga-ui/jest.config.ts
Error: Cannot find module '/Users/n.barsukov/WebstormProjects/taiga-ui/projects/kit/tsconfig.json'

What is the new behavior?
No error

Strange, everything works for me now

@splincode could you also check new version of configurations from this branch, please?
Does it work for your machine ?


email OTP Verification not signing user in on verification success.

Describe the bug

The OTP plugin does not automatically issue a verification email on signup when the sendVerificationOnSignup option is set to true.

When successfully verifying the OTP, the user is not automatically signed in.

To Reproduce
Steps to reproduce the behavior:

No automatic OTP email sending

Setup the OTP plugin.
Create an account with email & password
// no email is sent

No automatic login.

add the sendVerificationOtp func to the 1st setup, and repeat steps in 1)
enter received Otp code into emailOtp.verifyEmail
// user is not logged in

Expected behavior
A clear and concise description of what you expected to happen.
I would expect that setting sendVerificationOnSignup to true would automatically send an OTP to the users email when they submit a new username and password for a new account.
I would expect that the user is automatically logged in when the verification is successful.

I think neither conventional token verification performs automated sign-in after verification. This may be a bug we are carrying on since pre v1

I think it's probably because emailVerified is null. The plugin strictly checks for a false value. We should patch that.
sendVerificationOTP doesn't sign in the user automatically. You should use authClient.signIn.emailOTP instead, which will sign in the user upon verification.

I think it's probably because emailVerified is null. The plugin strictly checks for a false value. We should patch that.
sendVerificationOTP doesn't sign in the user automatically. You should use authClient.signIn.emailOTP instead, which will sign in the user upon verification.

The sendVerificationOTP is fine, but if you send a verification email using sendVerificationOTP and then attempt to use authClient.signIn.emailOTP, you get invalid otp error. Using authClient.emailOtp.verifyEmaill works with the otp but the user is not signed in when they verify.

I think neither conventional token verification performs automated sign-in after verification. This may be a bug we are carrying on since pre v1

automated-sign in after verification works with the standard email verification method using the following options:
emailVerification: {
  sendOnSignUp: true,
  autoSignInAfterVerification: true,
  //...
}


[Hexagon] Make pytest use a random port if not running in CI

This makes it so that when running tests locally you are able to get a random port. This is needed because the ports take a bit of time to free before they can be used again so repeated tests started to fail.
cc @masahi @mehrdadh

@tvm-bot rerun

@tvm-bot rerun


add doc compat entries

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

Comparison is base (e0cce3e) 80.44% compared to head (2c2d964) 80.44%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #163   +/-   ##
=======================================
  Coverage   80.44%   80.44%
=======================================
  Files           5        5
  Lines         721      721
=======================================
  Hits          580      580
  Misses        141      141

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


Allow compiling lib.rs code without main

Often I paste code from forum discussions or IRC into the playground to quickly look at an error message or check that it works. In these cases I need to throw a fn main() {} at the bottom.
If there is no main function, I would like it if the Run button could change into a Compile button and compile the code as a lib.rs.
This would be mutually exclusive with #169.

I assume adding #![crate_type="lib"] at the top is equally distasteful?

Correct. I think this issue is about doing what the user intended. Imagine if the playground were a snail-mail service where users mail in an envelope of Rust code, a person opens it and handwrites a response (error message or runtime output) and mails it back. If I mail in this program:
fn invoke(f: fn(&'static i32)) {
    f(&42);
}

No sentient human would send back a response saying "haha loser you forgot the main function." What I probably wanted to see was whether a reference to a literal can be 'static, so a better response would be:
error[E0597]: borrowed value does not live long enough
 --> src/main.rs:2:8
  |
2 |     f(&42);
  |        ^^ - temporary value only lives until here
  |        |
  |        does not live long enough
  |
  = note: borrowed value must be valid for the static lifetime...
  = note: consider using a `let` binding to increase its lifetime

what the user intended

My main concern is that there are many types of users. Two primary ones that I believe exist for the playground:

People just starting with Rust that want to see what it's all about.
People more experienced with Rust that want to do "expensive linting".

I think you and I are in the second category, but I wonder what experience the people in the first category would have with such a proposed UI change. I'd be worried about losing them by having their valid code compile and apparently do nothing.
There's also the "hey, I'm rustdoc / the Rust homepage / etc. and I want you to run some code" but those seem irrelevant to this concern.

No sentient human would send back a response saying "haha loser you forgot the main function."

I think I know what you might say, but why couldn't the same logic be applied to rustc and/or cargo itself?

One possible solution is to have another config option that changes the existing logic that looks for the crate_type attribute. It could then behave as you are suggesting.
Another is to add the semi-dreaded dropdown on the Run button that allows people to forcibly choose if they want to run / build / test.
Both of these would add overhead for the advanced users.

In rustc's case it really is an error if you write main.rs without a main function. In the playground it is less clear-cut that what you are writing is a main.rs. Rust code goes in and compiler output comes out. I agree that there could be ways to improve that experience on rustc's end but I think there is value in handling this better in the playground regardless of what happens in rustc and/or cargo.
I would prefer no config option or dropdown just because we don't need the user to tell us whether or not they wrote a main function -- we should be able to tell (with some caveat for a main function generated by a macro, but still I think it is a solvable problem).
I wouldn't worry about losing newcomers by having their valid code compile and apparently do nothing. There are some UI aspects to figure out but I don't think that is a real risk if done right. For example a message:

Your code compiled successfully! Add a `main` function to make it runnable.

Clicking the link appends an empty main and puts the cursor in the right place.
fn main() {
    ▓
}

This would be mutually exclusive with #169.

If we followed #169, would it have a similar outcome? A quick check shows it would produce the same error (modulo line / column numbers!):
fn main() {
fn invoke(f: fn(&'static i32)) {
    f(&42);
}
}

Yes in that case but not in general, such as for this code:
#[macro_use]
extern crate serde_derive;

#[derive(Serialize)]
struct Shepmaster;

error[E0468]: an `extern crate` loading macros must be at the crate root
 --> src/main.rs:3:1
  |
3 | extern crate serde_derive;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^

+1, I'd like to be able to just copy paste a function into the playground and generate the ASM code without having to write fn main() { } and then try to avoid the function from being eliminated completely in release.


Update Nomad to 0.10.x

To support host volumes in jobspecs.

I've taken a look at this and tried to update the vendored Nomad to 0.10.1. But now levant fails to build due to compile errors on vendor/github.com/hashicorp/nomad/nomad/structs/structs.generated.go. Might be related to https://github.com/hashicorp/nomad/issues/6537.
@jrasell perhaps you can take a look?

@rkettelerij I am also getting this on another build; so will be looking into it.

this should now be resolved.


Remove implicit object from the base class

Description
This Pull Request removes implicit object from the Base Class.
The Issue seems to be very minor but it improves the readability of the Code and since Python 3 inserts it for us behind the scenes, I suggested that its best remove them up.

thanks a lot, merged.


Ability to use ES6: rollup+babel transpilation

This change gives the opportunity to use ES6 for src/flow.js

karma.conf.js : Test the transpiled bundle instead of ES6 code.
babel: use bable-env + browserlist to transpile for a wider range of browsers.
For that purpose, switch to rollup with way handier and more modern than browserify.
In order to keep the toolchain backward-compatible (and reduce the PR surface), use grunt:exec to wrap rollup execution.

Also update to karma-coverage v2 needed for async support as discussed and anticipated in https://github.com/flowjs/flow.js/pull/304.

You are doing a huge upgrade and that's great. Would you like to be added as a maintainer of this project?

As long as someone keeps reviewing PR, I've no problem with this but I can't guarantee long-term involvement.
Still, about that specific PR, I don't understand why the CI fails, is this something you could fix to get this green?

It looks like it can't generate karma coverage report because coverage plugin is missing. Though all the tests pass.
You can see the log here: https://travis-ci.org/github/flowjs/flow.js/jobs/723863503

I guess the plugin is not loaded (anymore) because node can't parse node_modules/karma-sauce-launcher. Updating the version of node in .travis.yml may do it?

https://travis-ci.org/github/flowjs/flow.js/jobs/724987732
now we are getting different error
/home/travis/.nvm/versions/node/v14.9.0/lib/node_modules/codeclimate-test-reporter/formatter.js:33
      throw parseError;
      ^
Unknown input coverage format
(Use `node --trace-uncaught ...` to show where the exception was thrown)
The command "$TRAVIS_BUILD_DIR/travis.sh" exited with 1.

It looks like coverage was created, but with different format or empty file.

can you test if grunt karma:coverage generates a valid coverage report? e.g. it should create coverage/*/lcov.info files

Could you set your CC_TEST_REPORTER_ID if different from CODECLIMATE_REPO_TOKEN?
Note: These variables (like SAUCE_ACCESS_KEY) should probably be secret and stored inside GitHub configuration.
It's not doing coverage reporting (0-size file). But I don't understand which tool is actually in charge of code instrumentation?

Great job, it works! I have added you to the maintainers of this project. Once finished, your branch will be released as v3.0.0 flowjs since it supports promises. Please don't forget documentation too 🥇

Does not work. lcov.info is 0 bytes.

code-coverage fixed.
 Or on a v3 branch if you prefer such solution the time being?

Yes please, squash it and push it to v3 branch. Feel free to do it yourself, you have all the permissions you need. We need some time to release it to master once it's tested.

Note: The update to karma-coverage v2 caused start --single-run=false to stop functioning.
(https://github.com/karma-runner/karma-sauce-launcher/issues/217)
Will fix this in a subsequent commit.


JSON Coordinates Not Matching Actual Annotations in QuPath

Hello QuPath Community,
I'm encountering an issue with the annotation coordinates in QuPath (0.4.3), when annotations are made at different zoom levels (which cannot be avoided), the json and subsequent mask do not match with the actual annotation.
Attached is an example image with annotations:
(the actual annotation should be those deeply stained cells next the green mask)

I have tried it both in MacOS and windows system, and for different versions, though the problem can't be solved.
I've been performing annotations on histopathological images at various zoom levels. However, when I export these annotations to a JSON file, the coordinates in the JSON do not seem to match the actual positions where I made the annotations in the QuPath viewer.
The code I exported json from the image are:
import qupath.lib.objects.PathObject
import qupath.lib.objects.hierarchy.PathObjectHierarchy
import qupath.lib.regions.RegionRequest
import qupath.lib.roi.ROIs
import qupath.lib.roi.interfaces.ROI

import java.awt.Color
import java.awt.Graphics2D
import java.awt.Shape
import java.awt.image.BufferedImage
import java.io.File
import javax.imageio.ImageIO

def viewer = qupath.lib.gui.QuPathGUI.getInstance().getViewer()
def server = viewer.getServer()
def hierarchy = viewer.getHierarchy()

if (!server || !hierarchy) {
print("Error: No image or hierarchy loaded.")
return
}

def scaleFactor = 0.2
def width = (server.getWidth() * scaleFactor) as int
def height = (server.getHeight() * scaleFactor) as int

def img = new BufferedImage(width, height, BufferedImage.TYPE_BYTE_BINARY)
Graphics2D g2d = img.createGraphics()
g2d.setColor(Color.WHITE)
g2d.scale(scaleFactor, scaleFactor)

for (PathObject annotation : hierarchy.getAnnotationObjects()) {
ROI roi = annotation.getROI()
Shape shape = roi.getShape()
g2d.fill(shape)
}

g2d.dispose()
\
def originalFilename = server.getMetadata().getName()
def outputFilename = originalFilename.replaceAll('(?i)\\.[^.]+$', '.png')

//
def outputDirectory = new File('path')
def outputFile = new File(outputDirectory, outputFilename)
ImageIO.write(img, "PNG", outputFile)

print("Mask saved to " + outputFile.getAbsolutePath())
}
Expected Behavior:
I expect the coordinates in the JSON file to accurately reflect the positions of my annotations, regardless of the zoom level at which they were made.
Actual Behavior:
The exported JSON coordinates do not align with the actual annotated positions, especially noticeable when annotations are made at varying zoom levels.
Queries:

Is this a known issue with coordinate handling at different zoom levels in QuPath?
What are the recommended steps to ensure consistent and accurate coordinate mapping across different zoom levels?

I would appreciate any guidance or suggestions on how to resolve this issue. If additional information is needed, I am happy to provide it.
Thank you for your assistance.
Best regards,
Lily

Hello @Lililily0918,
Are you sure this is an issue related to this repository ? Quickly looking at your issue, I'd recommend:
1 - to post your issue on forum.image.sc with the QuPath tag
2 - it looks like you are issue very low level graphical Java (awt, Graphics2D). I'm pretty sure it's not the correct way to add overlays in QuPath. You'd rather have to use higher level function of the QuPath API - but you'll get better answers on forum.image.sc


Initial work to align service controller API with CF, not yet working.

This is a work in progress, but has broad changes affecting the controller and all storage interfaces, so wanted to make sure it's out there for awareness.
References #28

LGTM


Access data collect and ingest

It is easy to collect the relevant data from CrossRef, but some of these scholarly articles might already be freely available. We don't want to duplicate work, so we can collect access information from oaDOI and Zenodo.
Zenodo

[x] Figure out API calls to check DOI records
[x] Collect raw availability of DOIs collected from CrossRef
[ ] Ingest availability into database

oaDOI

[x] Download raw JSON for all CrossRef ingested DOIs

Had contact with oaDOI, allowed to do 600k calls over three days, but preferably data dump that is forthcoming.

[ ] Ingest whether freely available or not (one variable in data table indicating 0 or 1)

Just need to ingest over the weekend! Same as #2


Renaming RHODS to OpenShift AI

Closes: #2044
Description

Renames RHODS references to OpenShift AI.
Notes:

Limited impact on areas that impact the stack (logo file name has not changed)
Need to do an ODH-Manifests update to ISV resource references

How Has This Been Tested?

Manually in each area. Still need to test more to make sure everything looks good.
Test Impact

None, it's text changes.
Request review criteria:

Self checklist (all need to be checked):

[ ] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit tests & storybook for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

activeQuickStartID and allQuickStartStates needs to be changed
https://github.com/andrewballantyne/odh-dashboard/blob/06acbbf762bc14938aaea90970346d2d576e813c/frontend/src/app/QuickStarts.tsx#L12

/lgtm

Tested after the latest merge to main. No rhods wording found in user facing text.
/lgtm

Given Gauge and Dana have both looked over this, I'm rubber stamping this.
/approve

/lgtm


Shift-Tab to reduce indent/remove tab or space.

Is your feature request related to a problem? Please describe.
It's a common task of mine, by selecting a block of text and shift-tab to reduce their indent.
Describe the solution you'd like
Select a block of text, Shift-Tab to reduce the indent/remove tab or space.

You can assign keymap for outdent yourself in settings


Stabilizing last part of transcript

I have a situation where the last few words of the transcript shouldn't change as much.
For example if I would say 400 044 right now system could return 400 000 and a few instants later correct itself to 400 044.
But for my situation it would be better that the system doesn't correct itself at all. A small extra delay of about a second or so is allowed.
Any ideas of how I can achieve this? I assume it can be done by tweaking the transcription parameters but not sure which ones to change to achieve this in the best way.
Thanks

Hello, thanks for your interest in WhisperLive.
So, we consider the last segment returned from whisper as incomplement because of high possibility of a word being cut in between in the input audio. To get the transcript and not have it changed in the next response you could consider testing the following:

On the client side, Consider increasing the chunksize to at least 1 second i.e. 16000 here:
https://github.com/collabora/WhisperLive/blob/9d29b08cea2fc6224cf3d27cf97fbeef55b137a7/whisper_live/client.py#L97
On the server side, you could change the update_segment method to run the for loop over all the segments, currently it skips the last segment because we consider it as incomplete here:
https://github.com/collabora/WhisperLive/blob/9d29b08cea2fc6224cf3d27cf97fbeef55b137a7/whisper_live/server.py#L776
Next, in the update_segment method you should consider removing the processing of last segment because you already have it included i.e. remove these lines:
https://github.com/collabora/WhisperLive/blob/9d29b08cea2fc6224cf3d27cf97fbeef55b137a7/whisper_live/server.py#L788C9-L815C45
Lastly, the update_segments method shouldnt return anything because everything you need is in the self.transcript so, you can use that to return the responses.

Hope that gives you an idea about how to stabilise the last part.

just a CRUDE idea -> add an other layer of ai, to tell "if it is a whole word", only then process.
seen as human: it does not matter if i dont know the (any) language, but i clearly can tell/distinguish individual words, no matter who (any) speaks it. It's just the question if i understand the words, to transcribe it to text. But this is already covered with whisper, nothing needed to change.
seen as computer: we just need a more clever way of sending individual chunks, maybe with an idividual chunk-size which gets from the supposed additional lower-ai-layer "how long a word lasts" in a clever way, so there is NO problem of "truncation of single words"  anymore or at least very more seldom. the lower layer does not need to understand the words, only the start and end of each individual word. then transfer "word-chunks", instead of "bare-metal-chunks"
idea? i can program quite a bit, but this is way above my head to do it on my own. hope some more ppl like this idea, to make the transcription "more clean" <3


Did you see that paper ?

https://www.semanticscholar.org/reader/93d3b14ac1c5b86dc7ea2eef54d4541e4e2df57f
This work seems to be very similar.
Did you take inspiration of it ?
How do you think do you perform vs this work ?
If you release the code open source, it already make a huge difference.
Anyway, your paper is very insightful !

@oliviernguyenquoc, many thanks for your question. This is a very inspiring work, and indeed the two methods are pretty close since both develop an SSL training process using a similar set of augmentations. Therefore, we have included the published version of this work, i.e. the VRL [31] method, in our comparison to the state-of-the-art in Table 1. Yet, there are some key differences between the two approaches:

In VRL, the authors build based on SSL for representation learning to train the backbone network for feature extraction and an aggregation network that extracts clip-level representations. The similarity function is a variant of the handcrafted Chamfer Similarity tailored for hashed vectors, which is non-parametric. In contrast, in our work, we opt to use SSL for similarity learning, so we train a parametric similarity function without altering the representation space. To this end, our backbone network remains frozen during training, and we train a ViSiL-based network on top.
Another thing is that, in VRL, they build a training dataset offline, which means that the video pairs used in training are static, so fixed variations are seen by the network. Instead, we dynamically generate the video pairs online during training; hence our model is exposed to a larger variety of combinations.
Also, the research problem that VRL target to address is near-duplicate video retrieval. However, we tailor our method to tackle a wide range of similarity-based problems, including copy (near-duplicate), incident and event video retrieval, and their detection counterparts.
Finally, as noted, we plan to release our implementation to the public, including the training processed and pretrained models. Additionally, we rely solely on publicly available datasets to build our models.

I am closing this issue since it is not directly related to this repo. Feel free to ask anything if there are further queries.

Very inspiring. Thank you for releasing your code.
Congratulation !


"set INLINE_RUNTIME_CHUNK=false && react-scripts build" not working (depending on spacing)

Describe the bug
Spaces seem to affect whether set INLINE_RUNTIME_CHUNK=false works in the package.json in my environment.
The npm run build command will not error, but it doesn't remove the inline script from the index.html file that is produced.
Most set vars work just fine with spacing in my environment, i.e. these work as expected  for "start" and "test":
 "scripts": {
    "start": "set PORT=3002 && react-scripts start",
    "citest": "set CI=true && react-scripts test",
 }

However, INLINE_RUNTIME_CHUNK (and "build") does NOT work using the same spacing around "&&".
i.e. this does NOT work as expected:
 "scripts": {
    "build": "set INLINE_RUNTIME_CHUNK=false && react-scripts build"
}

Removing the spaces around "&&" makes it work correctly:
 "scripts": {
    "build": "set INLINE_RUNTIME_CHUNK=false&&react-scripts build"
}

This also works:
 "scripts": {
    "build": "set INLINE_RUNTIME_CHUNK=false&& react-scripts build"
}

Did you try recovering your dependencies?
I can observe this behaviour with a freshly created react app (see steps to reproduce).
Which terms did you search for in User Guide?
INLINE_RUNTIME_CHUNK
Environment
Environment Info:
current version of create-react-app: 3.4.1
running from C:...\node_modules\create-react-app
System:
OS: Windows 10 10.0.17763
CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
Binaries:
Node: 12.14.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.2 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: 44.17763.831.0
Internet Explorer: 11.0.17763.771
npmPackages:
react: ^16.13.1 => 16.13.1
react-dom: ^16.13.1 => 16.13.1
react-scripts: 3.4.1 => 3.4.1
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
The problem may/may not be Windows specific.
The below steps assume windows:

npx create-react-app my-app
cd my-app
notepad package.json
edit the build line to read as follows:
"build": "set INLINE_RUNTIME_CHUNK=false && react-scripts build",
save the file
npm run build
notepad build\index.html
observe that inline script is created in the index.html file, i.e. "

Same here I'm using craco to overwrite and this is not just working
"build": "INLINE_RUNTIME_CHUNK=false craco build"


Unable to build on Ubuntu 20.04

I am on Pop OS (Ubuntu) 20.04, with system opencv and default llvm/clang installed.
Trying to build without buildtime-bindgen fails with linking error, while with bindgen I get some problem on bindgen itself.
OpenCV is 4.2.0
Short version:
$ cargo build
   Compiling opencv v0.41.0
error: failed to run custom build command for `opencv v0.41.0`

Caused by:
  process didn't exit successfully: `/home/rongcuid/Projects/CVLive/target/debug/build/opencv-8ea17675d8494eee/build-script-build` (exit code: 101)
--- stderr
=== Crate version: Some("0.41.0")
=== Environment configuration:
===   OPENCV_HEADER_DIR = None
===   OPENCV_PACKAGE_NAME = None
===   OPENCV_PKGCONFIG_NAME = None
===   OPENCV_CMAKE_NAME = None
===   OPENCV_CMAKE_BIN = None
===   OPENCV_VCPKG_NAME = None
===   OPENCV_LINK_LIBS = None
===   OPENCV_LINK_PATHS = None
===   OPENCV_INCLUDE_PATHS = None
===   OPENCV_DISABLE_PROBES = None
===   OPENCV_CLANG_STDLIB_PATH = None
===   CMAKE_PREFIX_PATH = None
===   OpenCV_DIR = None
===   PKG_CONFIG_PATH = None
===   VCPKG_ROOT = None
=== Enabled features:
===   BINDING_GENERATOR
===   BUILDTIME_BINDGEN
===   CLANG
===   DEFAULT
===   JOBSERVER
===   OPENCV_4
=== Probing OpenCV library using pkg_config
=== OpenCV library configuration: Library {
    include_paths: [
        "/usr/include/opencv4/opencv",
        "/usr/include/opencv4",
    ],
    version: "4.2.0",
    cargo_metadata: [
        "cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu",
        "cargo:rustc-link-lib=opencv_stitching",
        "cargo:rustc-link-lib=opencv_aruco",
        "cargo:rustc-link-lib=opencv_bgsegm",
        "cargo:rustc-link-lib=opencv_bioinspired",
        "cargo:rustc-link-lib=opencv_ccalib",
        "cargo:rustc-link-lib=opencv_dnn_objdetect",
        "cargo:rustc-link-lib=opencv_dnn_superres",
        "cargo:rustc-link-lib=opencv_dpm",
        "cargo:rustc-link-lib=opencv_highgui",
        "cargo:rustc-link-lib=opencv_face",
        "cargo:rustc-link-lib=opencv_freetype",
        "cargo:rustc-link-lib=opencv_fuzzy",
        "cargo:rustc-link-lib=opencv_hdf",
        "cargo:rustc-link-lib=opencv_hfs",
        "cargo:rustc-link-lib=opencv_img_hash",
        "cargo:rustc-link-lib=opencv_line_descriptor",
        "cargo:rustc-link-lib=opencv_quality",
        "cargo:rustc-link-lib=opencv_reg",
        "cargo:rustc-link-lib=opencv_rgbd",
        "cargo:rustc-link-lib=opencv_saliency",
        "cargo:rustc-link-lib=opencv_shape",
        "cargo:rustc-link-lib=opencv_stereo",
        "cargo:rustc-link-lib=opencv_structured_light",
        "cargo:rustc-link-lib=opencv_phase_unwrapping",
        "cargo:rustc-link-lib=opencv_superres",
        "cargo:rustc-link-lib=opencv_optflow",
        "cargo:rustc-link-lib=opencv_surface_matching",
        "cargo:rustc-link-lib=opencv_tracking",
        "cargo:rustc-link-lib=opencv_datasets",
        "cargo:rustc-link-lib=opencv_text",
        "cargo:rustc-link-lib=opencv_dnn",
        "cargo:rustc-link-lib=opencv_plot",
        "cargo:rustc-link-lib=opencv_ml",
        "cargo:rustc-link-lib=opencv_videostab",
        "cargo:rustc-link-lib=opencv_videoio",
        "cargo:rustc-link-lib=opencv_viz",
        "cargo:rustc-link-lib=opencv_ximgproc",
        "cargo:rustc-link-lib=opencv_video",
        "cargo:rustc-link-lib=opencv_xobjdetect",
        "cargo:rustc-link-lib=opencv_objdetect",
        "cargo:rustc-link-lib=opencv_calib3d",
        "cargo:rustc-link-lib=opencv_imgcodecs",
        "cargo:rustc-link-lib=opencv_features2d",
        "cargo:rustc-link-lib=opencv_flann",
        "cargo:rustc-link-lib=opencv_xphoto",
        "cargo:rustc-link-lib=opencv_photo",
        "cargo:rustc-link-lib=opencv_imgproc",
        "cargo:rustc-link-lib=opencv_core",
    ],
}
=== Found OpenCV library version: 4.2.0 in headers located at: /usr/include/opencv4
=== Using OpenCV headers from: /usr/include/opencv4/opencv2
=== Generating code in: /home/rongcuid/Projects/CVLive/target/debug/build/opencv-d6f399e5d38808f5/out
=== Placing generated bindings into: /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.41.0/bindings/rust/opencv_4
=== Clang command line args: [
    "-isystem/usr/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9",
    "-isystem/usr/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/x86_64-linux-gnu/c++/9",
    "-isystem/usr/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/backward",
    "-isystem/usr/local/include",
    "-isystem/usr/lib/llvm-10/lib/clang/10.0.0/include",
    "-isystem/usr/include/x86_64-linux-gnu",
    "-isystem/usr/include",
    "-I/usr/include/opencv4",
    "-I/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.41.0/src_cpp",
    "-DOCVRS_PARSING_HEADERS",
    "-includeocvrs_resolve_types.hpp",
]
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread 'note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>thread '' panicked at 'a `libclang` shared library is not loaded on this thread<unnamed>', ' panicked at 'a `libclang` shared library is not loaded on this thread/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs::1618:1618:11

thread 'thread '<unnamed><unnamed>' panicked at '' panicked at 'a `libclang` shared library is not loaded on this threada `libclang` shared library is not loaded on this thread', ', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs1618::11618
:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread 'thread '<unnamed><unnamed>' panicked at '' panicked at 'a `libclang` shared library is not loaded on this thread', a `libclang` shared library is not loaded on this thread/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:', 1618/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1:
1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', thread '/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:<unnamed>1618' panicked at ':a `libclang` shared library is not loaded on this thread1
', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread 'thread '<unnamed><unnamed>' panicked at '' panicked at 'a `libclang` shared library is not loaded on this threada `libclang` shared library is not loaded on this thread', ', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs::16181618::11

thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread 'thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this threadthread '', <unnamed>/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs' panicked at ':a `libclang` shared library is not loaded on this thread1618', :/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs1:
1618:1
thread 'thread '<unnamed><unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread' panicked at '', a `libclang` shared library is not loaded on this thread/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs', :/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs1618::11618
:1
thread 'thread '<unnamed>' panicked at '<unnamed>a `libclang` shared library is not loaded on this thread' panicked at '', a `libclang` shared library is not loaded on this thread/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs', :/home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs1618::11618
:1
thread 'main' panicked at 'Can't join thread: Any', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.41.0/build.rs:172:13
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1
thread '<unnamed>' panicked at 'a `libclang` shared library is not loaded on this thread', /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/clang-sys-0.28.1/src/lib.rs:1618:1

Full version is too long for comment. I can post it if needed.

It is due to dependency of my other deps (gdnative) which pulls in bindgen-0.51. I am posting an issue on their side now.

Please enable the clang-runtime feature to work this around

Please enable the clang-runtime feature to work this around

Unfortunately, doing so results in a different error:
   Compiling opencv v0.41.0
error: failed to run custom build command for `opencv v0.41.0`

Caused by:
  process didn't exit successfully: `/home/rongcuid/Projects/CVLive/target/debug/build/opencv-ccd07e4bfe8301e5/build-script-build` (exit code: 1)
--- stdout
running: "/home/rongcuid/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo" "build" "--release" "--package" "opencv-binding-generator" "--bin" "binding-generator"

--- stderr
=== Crate version: Some("0.41.0")
=== Environment configuration:
===   OPENCV_HEADER_DIR = None
===   OPENCV_PACKAGE_NAME = None
===   OPENCV_PKGCONFIG_NAME = None
===   OPENCV_CMAKE_NAME = None
===   OPENCV_CMAKE_BIN = None
===   OPENCV_VCPKG_NAME = None
===   OPENCV_LINK_LIBS = None
===   OPENCV_LINK_PATHS = None
===   OPENCV_INCLUDE_PATHS = None
===   OPENCV_DISABLE_PROBES = None
===   OPENCV_CLANG_STDLIB_PATH = None
===   CMAKE_PREFIX_PATH = None
===   OpenCV_DIR = None
===   PKG_CONFIG_PATH = None
===   VCPKG_ROOT = None
=== Enabled features:
===   BINDING_GENERATOR
===   BUILDTIME_BINDGEN
===   CLANG
===   CLANG_RUNTIME
===   DEFAULT
===   JOBSERVER
===   OPENCV_4
=== Probing OpenCV library using pkg_config
=== OpenCV library configuration: Library {
    include_paths: [
        "/usr/include/opencv4/opencv",
        "/usr/include/opencv4",
    ],
    version: "4.2.0",
    cargo_metadata: [
        "cargo:rustc-link-search=native=/usr/lib/x86_64-linux-gnu",
        "cargo:rustc-link-lib=opencv_stitching",
        "cargo:rustc-link-lib=opencv_aruco",
        "cargo:rustc-link-lib=opencv_bgsegm",
        "cargo:rustc-link-lib=opencv_bioinspired",
        "cargo:rustc-link-lib=opencv_ccalib",
        "cargo:rustc-link-lib=opencv_dnn_objdetect",
        "cargo:rustc-link-lib=opencv_dnn_superres",
        "cargo:rustc-link-lib=opencv_dpm",
        "cargo:rustc-link-lib=opencv_highgui",
        "cargo:rustc-link-lib=opencv_face",
        "cargo:rustc-link-lib=opencv_freetype",
        "cargo:rustc-link-lib=opencv_fuzzy",
        "cargo:rustc-link-lib=opencv_hdf",
        "cargo:rustc-link-lib=opencv_hfs",
        "cargo:rustc-link-lib=opencv_img_hash",
        "cargo:rustc-link-lib=opencv_line_descriptor",
        "cargo:rustc-link-lib=opencv_quality",
        "cargo:rustc-link-lib=opencv_reg",
        "cargo:rustc-link-lib=opencv_rgbd",
        "cargo:rustc-link-lib=opencv_saliency",
        "cargo:rustc-link-lib=opencv_shape",
        "cargo:rustc-link-lib=opencv_stereo",
        "cargo:rustc-link-lib=opencv_structured_light",
        "cargo:rustc-link-lib=opencv_phase_unwrapping",
        "cargo:rustc-link-lib=opencv_superres",
        "cargo:rustc-link-lib=opencv_optflow",
        "cargo:rustc-link-lib=opencv_surface_matching",
        "cargo:rustc-link-lib=opencv_tracking",
        "cargo:rustc-link-lib=opencv_datasets",
        "cargo:rustc-link-lib=opencv_text",
        "cargo:rustc-link-lib=opencv_dnn",
        "cargo:rustc-link-lib=opencv_plot",
        "cargo:rustc-link-lib=opencv_ml",
        "cargo:rustc-link-lib=opencv_videostab",
        "cargo:rustc-link-lib=opencv_videoio",
        "cargo:rustc-link-lib=opencv_viz",
        "cargo:rustc-link-lib=opencv_ximgproc",
        "cargo:rustc-link-lib=opencv_video",
        "cargo:rustc-link-lib=opencv_xobjdetect",
        "cargo:rustc-link-lib=opencv_objdetect",
        "cargo:rustc-link-lib=opencv_calib3d",
        "cargo:rustc-link-lib=opencv_imgcodecs",
        "cargo:rustc-link-lib=opencv_features2d",
        "cargo:rustc-link-lib=opencv_flann",
        "cargo:rustc-link-lib=opencv_xphoto",
        "cargo:rustc-link-lib=opencv_photo",
        "cargo:rustc-link-lib=opencv_imgproc",
        "cargo:rustc-link-lib=opencv_core",
    ],
}
=== Found OpenCV library version: 4.2.0 in headers located at: /usr/include/opencv4
=== Using OpenCV headers from: /usr/include/opencv4/opencv2
=== Generating code in: /home/rongcuid/Projects/CVLive/target/debug/build/opencv-07137c2b26fb7f9f/out
=== Placing generated bindings into: /home/rongcuid/.cargo/registry/src/github.com-1ecc6299db9ec823/opencv-0.41.0/bindings/rust/opencv_4
error: package ID specification `opencv-binding-generator` matched no packages
Error: "Failed to build the bindings generator"

warning: build failed, waiting for other jobs to finish...
error: build failed

Hm, that’s weird, I’ll investigate, thanks for the report!

FYI, the godot developers bumped the bindgen version on master, but here comes a dependency issue:
    Updating crates.io index
    Updating git repository `https://github.com/godot-rust/godot-rust.git`
error: failed to select a version for `clang-sys`.
    ... required by package `bindgen v0.54.0`
    ... which is depended on by `gdnative-sys v0.8.1 (https://github.com/godot-rust/godot-rust.git#4f6fd5e1)`
    ... which is depended on by `gdnative-bindings v0.8.1 (https://github.com/godot-rust/godot-rust.git#4f6fd5e1)`
    ... which is depended on by `gdnative v0.8.1 (https://github.com/godot-rust/godot-rust.git#4f6fd5e1)`
    ... which is depended on by `cvlive-gdnlib v0.1.0 (/home/rongcuid/Projects/CVLive/cvlive-gdnlib)`
versions that meet the requirements `^0.29` are: 0.29.3, 0.29.2, 0.29.1, 0.29.0

the package `clang-sys` links to the native library `clang`, but it conflicts with a previous package which links to `clang` as well:
package `clang-sys v0.28.0`
    ... which is depended on by `clang v0.23.0`
    ... which is depended on by `opencv v0.41.0`
    ... which is depended on by `cvlive v0.1.0 (/home/rongcuid/Projects/CVLive/cvlive-rs)`
    ... which is depended on by `cvlive-viewer v0.1.0 (/home/rongcuid/Projects/CVLive/cvlive-viewer)`

failed to select a version for `clang-sys` which could resolve this conflict

It might be a good idea to relax version constraints if possible.

I notice the "error: package ID specification opencv-binding-generator matched no packages" issue occurs only when I try to use a version from crates.io. If I clone the repo locally and checkout the release tag, this error does not show.

It might be a good idea to relax version constraints if possible.

This is unfortunate, but I don’t have to much options in this case. This is caused by transitive dependency. The crate depends on the latest clang, which depends on clang-sys 0.28, but some other dependency requires 0.29

Currently I work around version issue by using a local copy and [patch] directive. However, I think the package error might be a separate issue.

The original issue has been worked around by keeping a local version. I opened a new issue for the new error: #145


Do Android build in CI

Fixes #772.
(Started as a draft PR, because I wasn't sure if more setup was needed in ci.yml in order for this build to work. Indeed some was.)

Thanks, LGTM! I'll hold off merging until @rajveermalviya has a chance to look.

The other day I remarked:
https://github.com/zulip/zulip-flutter/pull/718#discussion_r1667976403
that when we handle #772, we should include running the linter. It turns out that the type of issue that we were discussing there was a warning from the Kotlin compiler — so the last commit in this PR, telling the Kotlin compiler to treat those warnings as errors, does the job.
There's also an Android linter, but it has a different job. I'll send a separate PR for running that.

I tried this with macOS M1 runner (macos-latest), but surprisingly it didn't make much difference: https://github.com/rajveermalviya/zulip-flutter/actions/runs/9852479999

Thanks for trying that. Yeah, it's a shame that this adds so much to the time CI requires — about 4 minutes. It'd be good to find a way to reduce that, but I'm not sure there will be a good way; I think building an Android app is just slow compared to what we do in flutter test, and the worker machines we get from GitHub Actions are low-powered, and so on net it's slow.


Updating the app.php documentation for the latest Laravel

'providers' => [
PragmaRX\ZipCode\Vendor\Laravel\ServiceProvider::class,
]
'aliases' => [
'ZipCode' => PragmaRX\ZipCode\Vendor\Laravel\Facade::class,
]

Let me try to understand: is this missing in the docs? For the latest Laravel that should not even be necessary, we now have the artisan package:discover command, which is supposed to boot those things (service provider and aliases) automatically.
I think we may need a PR to fix all those stuff. :)

added a PR to fix this


Migrate Storage Samples to the samples/ folder

Fixes #8152  for blobs, queues and files

[x] Got completely rid of test framework dependency

[x] Remove assert Statements (if any)
[x] Rename test_* to *
[x] Get rid of setup and teardown
[x] Remove Recordings

[x] All the samples are inside the samples/ folder and not anywhere else
[x] Update the literal includes
[x] Updated the links in the README
[x] Added samples to MANIFEST
[x] Verified Docs in sphinx are generated properly

Can one of the admins verify this patch?

It good for me if all tests passed, since this pr's purpose is not to modify the logic of code ^_^


If insecure registry is configured the deployment fails

When contrail-ansible-deployer is used for deploying it expects the CONTRAIL_REGISTRY at the global level outside the ‘contrail_configuration’ when executing step 3.4 in this wiki https://github.com/Juniper/contrail-ansible-deployer/wiki/Contrail-all-in-one-setup-with-Openstack-Kolla-Ocata
CONTAINER_REGISTRY: "<IP_ADDRESS>:6666"
contrail_configuration:
CONTRAIL_VERSION: "10000-1-centos7-ocata"
When actually deploying the Contrail containers using Step 5 it expects it under contrail_configuration like this:
contrail_configuration:
CONTAINER_REGISTRY: "<IP_ADDRESS>:6666"
If you have insecure registry configured... you look into the yaml /root/contrail-ansible-deployer/playbooks/roles/configure_container_hosts/tasks/insecure_registry.yaml
It expects CONTAINER_REGISTRY to be at the top level and not under 'contrail_configuration'

Issue fixed


Update UI. Fix #11

I think you misunderstood my drawing.

The notification label should be between the Spreadsheet and Workspace sections. We'll use this to tell the user what's going on.
The refresh button should be to the right of Key Columns section. It should have a square shape; do this by using setPreferredSize as I did with the webcamButton
The webcam label is not below the Start Webcam button. Try clicking on the Start Webcam button, you'll see a new window appear with the webcam. Put the label right below the area that shows the picture.

For some reason, I cannot close the webcam panel by clicking the close icon or Ctrl+C in Terminal and have to Force Quit to exit. Could you help me with that?

Here is the screenshot. Is this what you meant?

It seems I have done something wrong with Git again :)) I pull --rebase from upstream master, update my branch then fail to push to my origin:feature_branch. I try to rebase from my feature_branch and it let me push things up to origin. But then Git doesn't let me rebase and merge (but only squash and merge). Could you give me an advice? Thanks. @ctring

If you do pull --rebase then rebase correctly, the branch, update-ui here for example, would connect to the master branch indicated by the blue mark, without the 2 duplicated commit on top.
I can imagine that you only do pull --rebase while on the update-ui branch. Going back to the document, in section Fetch + Rebase local master, I listed 2 steps:

First you go back to the master branch and call pull --rebase there to update the master branch.
Then you go back to your feature branch and rebase it onto the new master branch.

Your current repo should look similar to this.
In case you wonder how to get the log view like that, run:
git log --graph --decorate --oneline --all


Test classes should not have parent classes

I suggest to introduce a check, that will prohibit JUnit test classes to have a parent class. Here is why:

https://www.petrikainulainen.net/programming/unit-testing/3-reasons-why-we-should-not-use-inheritance-in-our-tests/
https://ncorti.com/blog/junit-rules
https://coderanch.com/t/698727/engineering/bad-practice-test-classes-extend
https://www.testingdocs.com/disadvantages-of-using-inherited-tests-in-junit/

@volodya-lombrozo please, consider this feature

@yegor256 It's a good suggestion. Thank you!

@yegor256 the puzzle #318 is still not solved.

@yegor256 The feature should be added in the '1.0.2' version

@volodya-lombrozo thanks!


Remove detail property as required from json schemas

It's not always that there exists a failure message for a failed test case, which has been used to set the property "detail" in the json files. This property has been "required" in the json schemas, which makes the "checking branches" to fail on branches that the failed test cases do not have failure message. This PR removes the obligatoriness of this property in the json files.

Pull Request Test Coverage Report for Build 2134

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.458%

Totals

Change from base Build 2130:
0.0%

Covered Lines:
2753

Relevant Lines:
5248

💛  - Coveralls


Update react-slick to 0.14.10

Attempt to fix failing production build due to recent changes to
dependencies in the react-slick package

Guess that didn't fix it

Failing build seems to be caused by enquire.js 2.1.6

The latest version of react-slick 0.14.10 includes enquire 2.1.6 which
adds window as a global var and breaks the production build. 0.14.4
is the last known version that works, so this prevents the patch version
from updating every time a new build is started.


OnEnter triggers twice and OnExit is not triggered

Bevy version
0.13.2
[Optional] Relevant system information
Ubuntu 22.04.4 LTS 64-bit
Minimal project with the issue
use bevy::prelude::*;

fn main() {
    App::new()
        .add_plugins(DefaultPlugins)
        .insert_state(AppState::A)
        .insert_state(AppState::B)
        .add_systems(OnEnter(AppState::A), setup_a)
        .add_systems(OnEnter(AppState::B), setup_b)
        .run();
}

#[derive(States, Debug, Clone, PartialEq, Eq, Hash)]
enum AppState {
    A,
    B,
}

fn setup_a() {
    info!("setting up A");
}

fn setup_b() {
    info!("setting up B");
}

fn cleanup_a() {
    info!("cleaning up A");
}

fn cleanup_b() {
    info!("cleaning up B");
}

The Output
2024-06-14T14:30:43.872719Z  INFO minimalstateissue: setting up B
2024-06-14T14:30:43.872759Z  INFO minimalstateissue: setting up B

Expected Output
2024-06-14T14:30:43.872719Z  INFO minimalstateissue: setting up A
2024-06-14T14:30:43.872719Z  INFO minimalstateissue: cleaning up A
2024-06-14T14:30:43.872759Z  INFO minimalstateissue: setting up B

OR
2024-06-14T14:30:43.872759Z  INFO minimalstateissue: setting up B

depending on the intended behaviour (I can say that what happens now is not intended behaviour).

States have been significantly reworked for 0.14, so it would be worth testing with 0.14.0.rc-2.
I am seeing something entirely different in 0.14.0.rc-2:
2024-06-14T14:38:11.676864Z  INFO i13844: setting up A

I think this could possibly be a bug with insert_state -- it seems to be behaving like init_state, not doing anything if the state is already present.

Pinging @MiniaczQ

This patch results in the behavior I personally expect, but folks more familiar with states should weigh in.
diff --git a/crates/bevy_state/src/app.rs b/crates/bevy_state/src/app.rs
index 2ff97f6ee..5fc7e8f49 100644
--- a/crates/bevy_state/src/app.rs
+++ b/crates/bevy_state/src/app.rs
@@ -76,19 +76,24 @@ impl AppExtStates for SubApp {
     }

     fn insert_state<S: FreelyMutableState>(&mut self, state: S) -> &mut Self {
-        if !self.world().contains_resource::<State<S>>() {
+        let already_initialized = self.world().contains_resource::<State<S>>();
+
+        self.insert_resource::<State<S>>(State::new(state.clone()));
+
+        if !already_initialized {
             setup_state_transitions_in_world(self.world_mut(), Some(Startup.intern()));
-            self.insert_resource::<State<S>>(State::new(state.clone()))
-                .init_resource::<NextState<S>>()
+
+            self.init_resource::<NextState<S>>()
                 .add_event::<StateTransitionEvent<S>>();
             let schedule = self.get_schedule_mut(StateTransition).unwrap();
             S::register_state(schedule);
-            self.world_mut().send_event(StateTransitionEvent {
-                exited: None,
-                entered: Some(state),
-            });
         }

+        self.world_mut().send_event(StateTransitionEvent {
+            exited: None,
+            entered: Some(state),
+        });
+
         self
     }

What's the use case behind initializing the same state twice?
If we don't have one I don't see why we'd support this if we want to fully overwrite the first call anyways.
Using the first call and ignoring subsequent ones seems reasonable to me, but a warning for initializing it multiple times is something we should do.

It looks like insert_state exists to support initializing a state with a particular state value, and overwriting states wasn't considered.
https://github.com/bevyengine/bevy/issues/10731
So I was making an assumption based on the name insert and how other parts of the engine function.

I can imagine state overwriting being useful when using external modules, which initialize state by themselves.
But that can be considered an architectural issue instead.
Unless we have a proper use-case I don't think we need the overwrite support.

Okay, so my assumption also seems in line with what the docs actually say about how that function behaves:
https://dev-docs.bevyengine.org/bevy/prelude/trait.AppExtStates.html#tymethod.insert_state
If we are going to officially stop supporting overwriting, we should make sure to update the docs.

What's the use case behind initializing the same state twice? If we don't have one I don't see why we'd support this if we want to fully overwrite the first call anyways. (Just remove the first call)

I have a main menu which takes you to a game. There is state AppState{Game, MainMenu} and state PauseScreen(bool) for when the app is in AppState::Game. By default, the App goes into state AppState::MainMenu and PauseScreen(false) by default. I was making a plugin which would take me to the AppState::Game straight away. In doing this, the state was initialised twice.

If we already promise we support this then we should probably keep it that way, otherwise it's a breaking change :/
The use case seems pretty reasonable, I didn't consider debug tools :)
I'll see if we can get overwrite running, biggest problem is ensuring we get only one event after all setups


i18n support for installer

Branch: master
Expected Behaviour: Able to support i18n in our installer.
Current Behaviour: The current  installer built doesn't support  i18n.

This will be fine, but the Kolibri installer should probably have i18n.
Created https://github.com/learningequality/kolibri-installer-osx/issues/1
CC: @mrpau-eduard @mrpau-richard @cpauya


Sorting of authors in composer.lock

Hey,
First off - really loving Dependabot. It saves us so much time! 👏🏼
I'm wondering why Dependabot is changing the order of authors in composer.lock file? Is there any way to disable that or what do we have to change on our side to be in sync with Dependabot's configuration?

@rihardssceredins 👋 which version of composer are you running locally? We're on 1.9.0 so maybe this is the cause. We're pretty much just doing a composer update.

@feelepxyz just validated that everyone on our team is using composer 1.9.0. 🤷🏼♂

@rihardssceredins ah it's probably because we use this https://github.com/localheinz/composer-normalize - we also set sort-packages to true: https://getcomposer.org/doc/06-config.md#sort-packages

@feelepxyz nice!
We also have sort-packages set to true in composer.json. We don't however use the composer-normalize package you mentioned. I'll look into it but I would say this creates unnecessary changes in composer.json for those not using normalizer. Maybe you can check if composer.json contains normalizer package and only then apply normalizer? Or make normalizing configurable?

@greysteil it looks like we require comooser-normalize in dev, do you know if it always gets run on composer updates?

That's just run on our own composer.json file.
The changes to our users' lockfiles are likely due to a change by packagist (they re-indexed their packages). If users clear their caches locally then they will see the same changes when running composer update. As a result I don't think this is a Dependabot bug, just a slightly annoying transition period for Composer users.

@greysteil nice one! Looks like that will do it. @rihardssceredins could you confirm clearing your composer cache fixes the issue?

@feelepxyz just tried it but the only change in composer.lock after following the instructions was a minor package update. No changes to authors for existing packages were made.
Output of composer diagnose:
Checking composer.json: OK
Checking platform settings: OK
Checking git settings: OK
Checking http connectivity to packagist: OK
Checking https connectivity to packagist: OK
Checking github.com rate limit: OK
Checking disk free space: OK
Checking pubkeys:
Tags Public Key Fingerprint: 57815BA2 7E54DC31 7ECC7CC5 573090D0  87719BA6 8F3BB723 4E5D42D0 84A14642
Dev Public Key Fingerprint: 4AC45767 E5EC2265 2F0C1167 CBBB8A2B  0C708369 153E328C AD90147D AFE50952
OK
Checking composer version: OK
Composer version: 1.9.0
PHP version: 7.3.9
PHP binary path: /usr/local/Cellar/php/7.3.9_1/bin/php

Maybe you have to do the same thing on your end?

Closing this as it's unlikely we'll get to it in the foreseeable future. Please feel free to reopen if this work is critical to your scenario.


dynamic models with irregular lengths

Currently we have no very good way of dealing with packed sequences, such as time series of irregular lengths which have been packed into tensors with zero-padding to be able to do minibatch sgd while masking them out.
Pytorch has helper functions for packed sequences, but we need to see how we intend to support such irregularities efficiently without having to process each sample separately.
This may interface weirdly with the mapdata issue I brought up ( https://github.com/uber/pyro/issues/33 ).
Discuss!

I'm also looking into nested iaranges with very sparse tensors. I believe PyTorch's sparse tensors could be a viable alternative to masking for very sparse tensors.

Closing since I believe this can now be done by a combination of:

nested irange/iarange as of #780 and
masking via my_dist.mask(my_mask) as of #821
Feel free to re-open if I've misunderstood.

@fritzo Would love if you could give an example.

@PhSteel here's an example with a batch of time series with different lengths. I haven't tried to run it.
def model(batched_series, lengths):
    mean = pyro.param("mean", torch.tensor(0.0))
    batch_size, max_length = batched_series.shape
    assert lengths.shape == (batch_size,)
    with pyro.iarange('batch', batch_size):
        mask = torch.arange(max_length) < lengths.unsqueeze(-1)
        pyro.sample("series",
                    dist.Normal(mean, 1)
                        .reshape(batched_series.shape)  # expand to the full batch
                        .mask(mask)                     # mask out unwanted terms
                        .reshape(extra_event_dims=1),   # declare time index as dependent
                    obs=batched_series)


update authzed/spicedb logo, description, links

Pre-submission checklist:
Just updating the listenings for us, thanks!
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?

@jzelinskie company name is the name of the project now? just to confirm :)

The company name is authzed and one of our open source projects is SpiceDB.
I probably made a mistake if you think they've converged. Please let me know what I need to change.

@jzelinskie we only allow one entry in a sub landscape for a project


Replace ServiceLoader

Seems like ServiceLoader doesn't work well at all with user projects

In fact, it appear #87 was an architectural error which impact is this bug. So I'll have to rollback that change fast.


Introduce regression test caching

Until now, regressions tests always needed downloaded kernels in the kernel/ directory. We used the tests/regression/kernel_modules directory for storing the analysed IR and C files but that was intended for manual inspection only.
This refactors regression tests in a way that they can completely run on data stored in this directory. The directory has been renamed to tests/regression/test_data as it better reflects its new purpose. See commit message for the first commit for implementation details on how this is done.
In addition, this refactors pytest unit tests (tests/unit_tests/*.py) such that they only require one kernel version (3.10.0-957.el7).
Thanks to the above changes, CI can now cache only the test_data directory. In case it can be restored from cache, we only download kernel 3.10.0-957.el7 for unit tests, otherwise we download all the kernels and cache the test_data directory after the tests are run. The cache key is composed of the LLVM version and a hash of all test spec files. This way, we cache separate test data for each LLVM version and it gets invalidated whenever the set of test cases changes.
Unfortunately, this means that we no longer build all LLVM IR files in every CI run. But since we still have tests for building them in unit tests, I believe that this is a compromise that we should do for the sake of faster CI runs. Also, I haven't found a way to invalidate the caches in case we do a change in the build process so #321 is still an issue.
Overall, this significantly speeds up the CI. With cached test_data, CI runs in ~9 minutes.
This resolves #295 but see comment in that issue to learn about alternatives which can be considered. Since the amount of cached data is significantly lower (~100 MB per LLVM version), we should also get rid of #337 once we delete the old cache entries containing entire kernels.

I tried to review the changes, but somebody else should probably look at this also, because I am not yet much familiar with this part of DiffKemp.

Thanks for the review! I addressed the comments, I also found that we need to rename the task directories in tests/regression/test_data as there may be same functions in different task specs (for different kernel versions) so the task name must also contain the spec name, too.

I have gone through the changes and everything I have found is only nitpicking, but I am also not confident in my knowledge of this part of diffkemp.

The CI is passing and it look that it works correctly, then I think that it is safe to assume that this pull request is working as expected. And the test data are loaded from the cache. From my side there are no objections.


Transfer Publication Processes from Notion to here

Need to review the process first.
private URL: https://www.notion.so/meilisearch/Publication-Processes-136bd45cda3a494e927ee3e9861bd592
Add information for tutorials, video content, newsletter, demos, integrations, new MeiliSearch releases...

Actually, it's the Contact US page in the doc https://docs.meilisearch.com/learn/what_is_meilisearch/contact.html


Signal strength is different

Two devices are close to each other but one got positive signal strength (too close case), one got negative (ok case). Negative one runs on Lenovo PB2-690M, Android 6.1.
I think, we need to handle this error in BLEClient.kt, var rssi: Int = scanResult.rssi. Some devices returns negative strength signal. We need to normalize this one.

Hey.  You are the second person reporting this.  I'm pretty sure I know what the issue but it's going to be hard for me to debug.  The device uses the Bluetooth 4.0 chip set and I think it reports transmission strength differently.  The collection is done here...
https://github.com/kunai-consulting/OpenTrace/blob/f95a580a92edb8f1cc892f2db9d03ca92147ce7a/app/src/main/java/ai/kun/socialdistancealarm/alarm/BLEClient.kt#L132
and then the value for signal strength is done in a bunch of places in the code like this one...
https://github.com/kunai-consulting/OpenTrace/blob/f95a580a92edb8f1cc892f2db9d03ca92147ce7a/app/src/main/java/ai/kun/socialdistancealarm/dao/DeviceRepository.kt#L31
The calculation is always the same.  What I can't tell is what the values are on different devices.  For the ones that I have the value for txPower is always the same: 127, but I think for the 4.1 and 4.0 BLE devices it's different.  Can you run with logcat and send me a log?  There's a line that starts with +++++++++++++ Traced: that should show me the value.  If I have values for both of your phones we can do some math and fix the issue.
Also are you interested in contributing?  We'll accept help even if it's just the occasional story or bug fix<EMAIL_ADDRESS>if you want to help.

I think this is fixed in the develop branch.


can't interact with ui on windows 11. MacOS is fine.

I can't  click any button at all. Quickstart page opens default and stays at that page forever:) Any help?

yes, me too, can't click button just star on quick start

I ran into this problem today.  To fix it go to the .eslintrc file, and update the "rules" part to look like this:
"rules": {     "react/react-in-jsx-scope": "off",     "react/prop-types": "off",     "react/jsx-key": "off",     "react/no-unescaped-entities": "off",     "prettier/prettier": ["off", { "singleQuote": true }]   }
just add that last line that begins "prettier ...

This issue is related to different endings of code line on different OS. LF/CRLF.
You can disable this rule by adding to the .eslint:
'linebreak-style': 0,

@captvicky Have you tried yarn format?

You should include this in the install instructions.


Store XSS in post title and context

Pagekit version: 1.0.11
Webserver: Apache
Database: MySQL
PHP Version: 7

Login user who has "Manage own posts" privilege can inject arbitrary web script or HTML via post editor, XSS vulnerability will be triggered by visiting /blog or /blog/{post_id}.
PoC

An XSS leak describes the injection of untrusted code in to a trusted context by (usually) somehow bypassing access control. This is not the case for your described scenario.
Pagekits posts and pages provide HTML support as a feature (like Wordpress, Joomla and many other CMSs), which implies that code injection is always possible for users with write permissions. I won't consider this a problem since write permissions should only be granted to trusted parties (users with write permissions can cause a lot of harm anyway, even besides code injection).
For potential further security issues please send a mail to<EMAIL_ADDRESS>so that we are able to evaluate and patch the vulnerability before it is disclosed to the public.

👍


Announcement:  Intel OneAPI for build, test and deploy across multiple hardware targets

Hi everyone,
Intel has introduced its "write once, run anywhere" oneAPI toolkit, which has a base kit and add-on kits.
https://software.intel.com/en-us/oneapi

@dorodnic are there plans to port the CUDA based stream alignment to oneAPI / SYCL? That sounds like a pathway to support stream alignment support on ARM devices without CUDA.

Hi @compiaffe  The RealSense SDK 2.0 does not have any connections to OneAPI or SYCL.  From the time of its launch in late 2017, the SDK was designed with the philosophy of having minimal third-party integrations in its core in order to make it compatible with as wide a range of different hardware and software platforms as possible so that RealSense could be anywhere and everywhere.
The SDK already has an alternative graphics acceleration system called GLSL Processing Blocks that supports pointcloud, alignment and more and is 'vendor neutral ', meaning that it can work with any brand of GPU.  It is built into the SDK and can be enabled simply by changing rs2:: instructions (such as rs2:: align) to rs2::gl::
For example, rs2::align becomes rs2::gl::align, rs2:: pointcloud becomes rs2::gl::pointcloud, etc.
https://github.com/IntelRealSense/librealsense/pull/3654 has a very good pros and cons analysis of GLSL processing blocks and when it can be used.
There is also a C++ example program for a GLSL-equipped pointcloud called rs-gl here:
https://github.com/IntelRealSense/librealsense/tree/master/examples/gl

Cool, thanks for the pointer!


The 'manage locations' page has 'important points' related to bookmarks

Here are some important points regarding the template file:
Never edit data in these fields: Id, Last Modified, and Last Modified By
If you include the Id of an existing bookmark, it will be replaced with the information in the import file.
If there is an existing bookmark with the same title or URL, the bookmark will be updated with information in the import file.
Not all fields in the template file are required and required fields vary depending on the bookmark state.
Based on the State field, bookmarks will be saved as draft, suggested, scheduled, or they will be published automatically.
For partners who manage multiple organizations, you can export your bookmarks from one org and import them into another. But you must remove the data in the Id column before you import.

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

ID: 79763408-6d1b-3ae3-39cb-064cbb329109
Version Independent ID: ac060ac0-2938-ed28-0b65-a7b04802d575
Content: Manage locations
Content Source: MicrosoftSearch/manage-locations.md
Service: mssearch
GitHub Login: @dawholl
Microsoft Alias: dawholl

Thanks for reporting this; we will get the docs updated.

The doc have been updated.


Add atol option to contrib.reduce_on_plateau()

This PR swaps the threshold argument in the current implementation of reduce_on_plateau() with the two arguments rtol and atol.  The change is added to  reduce_on_plateau.py and reduce_on_plateau.ipynb where needed to retain the current behaviour.
The behaviour in the current implementation corresponds to the case atol = 0 and rtol  > 0 in the new one, and is kept as the default. The addition of atol allows to set an absolute tolerance for measuring a new best loss, or to mix relative and absolute tolerances by choosing a value greater than zero for both rtol and atol.
In order to implement this change, I've modified the inequality has_improved = jnp.where((loss / state.best_loss - 1) < -threshold, 1, 0) to has_improved = jnp.where(loss < (1 - rtol) * state.best_loss - atol, 1, 0). Notice that moving the term state.best_loss from the denominator of the left-hand side in the first inequality to the right-hand side in the second one has the added benefit of correctly handing losses that can attain negative values (e.g. ELBOs with continuous distributions) when rtol = 0 and atol > 0.

Thanks @stefanocortinovis ! Having a relative tolerance makes a lot of sense to me. The only downside I see is that it no longer follows the pytorch implementation (not that we have to), so I think that's fine.
Any opinion on this @vz415 @vroulet since you contributed the reduce_on_plateau implementation and review respectively?

Nice catch! This does handle negative losses correctly but I'd just suggest adding having an assert statement or some other safety measure to ensure users set rtol > 0 and atol > 0. Hate to be that guy but it might also help to have a warning if a user's loss is negative and rtol = 0 and atol > 0 isn't set.

Thanks for the comments! I added validation checks for atol and rtol. However, I haven't seen runtime warnings raised from within the update_fn of any other GradientTransformation. How would you suggest to proceed?

I suggest we use the warnings module in the Python standard library (https://docs.python.org/3/library/warnings.html) since that seems to be what jax uses (see for instance https://github.com/google/jax/blob/f539187c053bf1819f05d0f8e9e66e45da2af17b/jax/_src/array.py#L456)

Thanks for the suggestion @fabianp. However, I'm still not convinced raising warnings based on the value of loss would be a good idea.
In theory, raising such a warning would involve adding something like
if loss < 0.0 and some_other_condition:
    warnings.warn('some warning')

to the update_fn of reduce_on_plateau.
Howeover, update_fn will usually be called within a jitted block. Something like:
@jit
def make_step(params, transform_state):
    updates = {"params": 1.0}
    loss = jnp.asarray(-1.0)

    updates, _ = transform.update(updates=updates, state=transform_state, loss=loss)
    params = optax.apply_updates(params, updates)

    return params, loss

params = {"params": 2.0}
transform = contrib.reduce_on_plateau()
transform_state = transform.init(params)

make_step(params, transform_state)

Hence, if update_fn involves warnings based on the sign of loss, make_step will raise the usual TracerBoolConversionError because loss is a traced array.
Am I missing something here?

Thanks for the contribution @stefanocortinovis !


$all on array of nested documents does not work

Using query: { 'order.items.product': { $all: ['poster', 'frame'] } }

const items = [{
	"order" : {
		"id" : "or_0001",
		"amount" : 6000,
		"items" : [
			{
				"product" : "poster",
				"sku" : "P18x24",
				"quantity" : 1,
				"amount" : 3000
			},
			{
				"product" : "frame",
				"sku" : "P18x24",
				"quantity" : 1,
				"amount" : 3000
			},
			{
				"product" : "shipping",
				"sku" : "shipping",
				"quantity" : 1,
				"amount" : 5000
			}
		]
	}
}];

items.filter(sift({ 'order.items.product': { $all: ['poster', 'frame'] } });

This query works using mongo, but not sift.

I second that. But it has nothing to d with $all. It doesn't properly filter complex array values.
This also fails:
`const obj = {
array: [
{value: 1},
{value: 2},
],
};
const query  = {
"array.value": 1
};
const filter = sift(query);
    const res = filter(obj);

    assert.isTrue(res);`

Sorry for not getting to this sooner, this bug required a whole bunch of refactoring. Issue should be fixed in 11.0.0 👍.


Unit Testing Definition update

Added further meaning to the description of unit testing in the Spanish section.

[x ] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[x ] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Just trying to contribute with the little knowledge I have of unit tests. If it's unnecessary, please remove it. No hard feelings.

What would make it clearer is another example, this time of something that is not a function (since the explanation mentions it). Like ensuring a class member is of a certain type, immutable or even defined

Thank you for opening this pull request.
This is a standard message notifying you that we’ve reviewed your pull request and have decided not to merge it. We would welcome future pull requests from you.
Thank you and happy coding. ✈


The dropdown does not have positioning options

Expected Behavior
The dropdown "ul" list should be able to be positioned anywhere in the screen, depending on the necessity of the designer.
Current Behavior
The "ul" dropdown-content, upon initialization of the wholedropdown via
$('.dropdown-trigger').dropdown({constrainWidth: false });
has all it's styling information erased, which gets substituted by something like
display: block;
width: 180.467px;
left: 1344.9px;
top: 0px;
height: 336px;
transform-origin: 100% 0px 0px;
opacity: 1;
transform: scaleX(1) scaleY(1);

by the materialize library. The effect is that often the dropdown will be directly over, and not below, the dropdown-trigger. Indeed, the docs have nothing about positioning: https://materializecss.com/dropdown.html
Possible Solution
Allow the user to pass parameters such as top: 10px, or those kind of styling information to not be overwritten. Or some more intelligent way to avoid the dropdown to be directly over the dropdown trigger, occupying the same space in the screen.

You mean like this?

$('.dropdown-trigger').dropdown({
coverTrigger: false
});

https://materializecss.com/dropdown.html#options

What if it is a side navbar and you want the dropdown to appear to the right of the trigger for example?

Ok that would be handy but you specifically asked about the dropdown covering the trigger:

Or some more intelligent way to avoid the dropdown to be directly over the dropdown trigger, occupying the same space in the screen.

In this case it is a good idea and should be easy to do, something like:
dropdownPosition: right
With the options being left, right, top, bottom, and still retaining coverTrigger.

@doughball you saved my day, really appreciate! :smile:
I just want not to cover the title of navitem, and this option is enough. Thank you for pointing out the document I missed.


Use smaller upload files for mint

Changed SDK tests to use data files from a common directory that is generated at the time of docker image build. Using smaller files to speed up execution of tests

can you remove the binary files from the commit? also move initData.sh to buildscripts dir?

If there is nothing pending, can you pls approve it @harshavardhana

@poornas can you pls update the README.md with the data_dir file details, i.e.
For each file, just add these two details.

File name:
Size in MB:

This will be helpful others adding tests cases.


Community guidelines: add a feature request template

See https://github.com/erlef/otp_builds/issues/6#issuecomment-2362122210

Same as the other reply.

Closing as per discussion in linked pull request.


Parser

Choose a parser library for C data structures.
See

https://wiki.python.org/moin/LanguageParsing
http://stackoverflow.com/questions/1951421/parsing-a-c-header-file-in-python

I'll try PLY.


fix some bugs

2 fgtile tweaks in a-03 to fix everest freeze thingy
set down hole in e-13 to none because of instant death

I missed this at the time, but for future reference: when removing fgtiles you have to say Tile: 0 instead of Remove: true since there's no such thing as there not being a fgtile somewhere, it's just the null tile when there's empty space