Bump nodejs to 16.20.1

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] Ready to merge

Summary
Bump nodejs (16) to 16.20.1 to resolve CVE-2022-25881 in http-cache-semantics depended on by npm.
Change Log

bump nodejs to 16.20.1

Does this affect the toolchain?
NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-2022-25881

@reviewer please could you run the pipeline to add nodejs16.20.1, https://github.com/nodejs/node/releases/tag/v16.20.1 the  script SPECS/nodejs/generate_source_tarball.sh will need to be run to create a "clean" tar.

LGTM. Did you already upload the source tar?

@rmhsawyer I don't think I have permissions to run the CI job which uploads the tar.

Please change the destination branch to main.

uploaded the clean tar ball to blobstore
https://dev.azure.com/mariner-org/mariner/_build/results?buildId=387006&view=results

Hi @dsteeley , Did you build the package locally? Is the build successful?

@sindhu-karri, local build is now successful.

@sindhu-karri/@rmhsawyer  Please could you look over this and merge if you're happy.

The fix is in the version of npm associated with the version of nodejs16:
https://github.com/npm/cli/releases/tag/v8.19.4
https://github.com/npm/cli/blob/v8.19.4/package-lock.json#L6445

@dsteeley Apologies for the delay on this- looking at this now.

Looks good to me, undid a couple of iffy linter changes, running a buddy build to validate the change before merging.


[Feat]: Making Header and footer part in feedback section

Is your feature request related to a problem? Please describe.
I want to add header and footer section in feedback form so that user could easily navigate among different links.
Describe the solution you'd like.
No response
Describe alternatives you've considered.

Additional context.
No response
Show us the magic with screenshots
No response
Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

@shreyabajaj12 assigning this issue to you.
Make sure to complete this within 2 days.

@shreyabajaj12 have you done with it.

Sir actually I want to unassign this issue because I am not able to figure out the same layout as it is in the other pages.
Sorry for the delay.

Okay, @shreyabajaj12 can I close this issue.

yes sir thank u very much


gooseberry sync now produces better output

Looks good! Could you run it through cargo fmt?

Yep! Runs through cargo fmt with no problems for me!

There's still the last case to handle, i.e. when nothing changes (see the linked issue) - could be done with an if statement checking if all three are 0.

I've run the new code through cargo fmt, it builds fine too!

Do the tests pass? Here's some instructions on setting that up

Hmm... now I'm getting this:
`running 3 tests
test it_works ... FAILED
test sync ... FAILED
test tag ... FAILED
failures:
---- it_works stdout ----
Error:
0: path not found
1: path not found
thread 'main' panicked at 'assertion failed: (left == right)
left: 1,
right: 0: the test returned a termination value with a non-zero status code (1) which indicates a failure', /Users/keverne/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/src/libstd/macros.rs:16:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
---- sync stdout ----
Error:
0: path not found
1: path not found
thread 'main' panicked at 'assertion failed: (left == right)
left: 1,
right: 0: the test returned a termination value with a non-zero status code (1) which indicates a failure', /Users/keverne/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/src/libstd/macros.rs:16:9
---- tag stdout ----
Error:
0: path not found
1: path not found
thread 'main' panicked at 'assertion failed: (left == right)
left: 1,
right: 0: the test returned a termination value with a non-zero status code (1) which indicates a failure', /Users/keverne/.rustup/toolchains/stable-x86_64-apple-darwin/lib/rustlib/src/rust/src/libstd/macros.rs:16:9
failures:
it_works
sync
tag
test result: FAILED. 0 passed; 3 failed; 0 ignored; 0 measured; 0 filtered out
error: test failed, to rerun pass '--test cli'
`
I'll see if it happens without the changes too.

Haven't encountered that error before but I noticed that the tag test sometimes failed due to querying the Hypothesis API before the changes were reflected - I've added some delays to this on the main branch.
I am fine with running tests locally for now if you couldn't get them to work but in the current state the PR wouldn't pass the tests since there are still some occurrences of "Added 2 notes" and "Updated 2 notes"  that haven't been changed. Could you look into changing those?
Thanks!

I’ll give these a look tomorrow, hopefully we can solve it.

Haven't encountered that error before but I noticed that the tag test sometimes failed due to querying the Hypothesis API before the changes were reflected - I've added some delays to this on the main branch.
I am fine with running tests locally for now if you couldn't get them to work but in the current state the PR wouldn't pass the tests since there are still some occurrences of "Added 2 notes" and "Updated 2 notes" that haven't been changed. Could you look into changing those?
Thanks!

Are the occurences of "Added 2 notes" and "Updated 2 notes" in gooseberry sync? Or are you talking about the tests? Also, the error is still happening for me, still looking into the issue!

Ahh I realised I was adding the wrong cli.rs to the commit. The new cli.rs in /tests/ should be the right one.

Are you sure you've followed the instructions for setting up tests from here? It's likely that you're missing the .env file causing the tests to fail. The tests run fine for me now so I'll accept the PR.

Ahh I just realised that I lost the .env file when I re-cloned the repo. I’ll make a copy outside of the repo now!


[7.x] Fixes Http Client multipart request body params passed as key-value

This PR fixes #32058, full details to be found in the issue.
In short, when the below code is run:
$photo = fopen(public_path('/storage/') . $this->photoPath, 'r');

$response = Http::withToken($this->token)
	->withHeaders([
		'X-Header' => $this->header
	])
	->attach('photo', $photo)
	->post($url, [
		'name' => 'test'
	]);

...it generates this error:

TypeError: Argument 2 passed to GuzzleHttp\Psr7\MultipartStream::addElement() must be of the type array, string given, called in /vendor/guzzlehttp/psr7/src/MultipartStream.php on line 70 in file /vendor/guzzlehttp/psr7/src/MultipartStream.php on line 79

This PR solves the above issue bye ensuring the proper array is passed to Guzzle options array.

My first PR in Laravel, open to all kinds of criticism/suggestions! 🤓

Fixed.


Cache Redux Store

Features

Parts of the state such as token, username and the playground code persist when refreshing the browser. As a result, no need to login again when refreshing the page (!!)

TODO

There is an issue with redux-persist in the memory it uses (WebStorage). It works when running, but it is not available during tests, that are not on the web. I'll have to use a different type of storage for this.

Pull Request Test Coverage Report for Build 60

14 of 16 (87.5%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.1%) to 30.127%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/index.tsx
0
2
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/index.tsx
1
0.0%

Totals

Change from base Build 49:
0.1%

Covered Lines:
1071

Relevant Lines:
3117

💛  - Coveralls

Opened #129 for tests not working with redux-persist.


C++ Driver

What is the goal of this PR?
Introduce the C++ driver for TypeDB.
What are the changes implemented in this PR?
Driver:

Introduces the C++ driver, wrapping the C driver produced by rust.
Relies on using std::unique_ptr and move semantics to reduce the risk of memory leaks & dangling pointers to native (rust) objects.

Behaviour tests:

Introduces a minimal test framework which uses cucumber's gherkin as parser for feature files & gtest as test framework.
Implements the steps for driver behaviour tests.

(Doing)
Build
Adds the C++ driver to the release pipeline to publish an archive with (binaries & headers) to GitHub.

One more set of comments:

we can adopt a naming convention of _ in file names
we can dissolve the lib/inc folder by moving the header files next to implementations for internal dependencies. Macros can go into common
When you rebase, make sure you go back over the range of commits that you are rebasing over to make sure you include all features/bugfixes merged since you branched out


Editorial change: Link Object points to Operation Object

@char0n You are correct. Unfortunately this PR targets main and we can't accept specification changes there. We also don't plan new patch releases for the v3.0 specification.
Please open a new PR targeting branch v3.1-dev that changes file src/oas.md.
See section Pull requests in CONTRIBUTING.md.

Hi @ralfhandl,
I've seen the CONTRIBUTING.md but it didn't contain info about editorial changes or a way how to approach them. Just to confirm, it is not possible to apply editorial change for current OpenAPI spec versions (it's immutable), only target next versions?

Correct, the first section says

No changes, however trivial, are ever made to the contents of published specifications (the files in the versions/ folder). Exceptions may be made when links to external URLs have been changed by a 3rd party, in order to keep our documents accurate.

@ralfhandl thank you.
This PR is superseded by https://github.com/OAI/OpenAPI-Specification/pull/4260.

@ralfhandl thank you.
This PR is superseded by https://github.com/OAI/OpenAPI-Specification/pull/4260.


Bump bindgen version

Bump the bindgen version in order to resolve conflicts with libraries that have already updated

Thanks @l1npengtul!


Generate changes texts strings in artwork

After using the plugin I discovered that many text strings in my artwork had been changed to the layer's name.
For example:
Layer named "Button / Small / Default" with the text string "Cancel"
becomes
"Button / Small / Default" with the text string "Button / Small / Default"

Thanks for reporting. Will look into it asap.


Updated blacklist

Hi @BasilFronsac, thanks for the PR! Some issues with it--

constants.js is a compiled file. Changes should be made to constants.coffee, and then gulp should be used to compile the js file, and both would then be committed together.

The way that the string matching currently works is that it matches partial strings or substrings-- e.g. "asha" would match "masha" "tasha" "sasha", etc. Thus I can't accept most of the words you've submitted here. The best strings are ones that are 99% of the time sure to be specific to GoT. Also, 'jaime lannister' is unnecessary since I already have 'lannister in there.

The following words from your list are good additions: myrcella, lannister, vaes dothrak, bloodraven, walder frey, meereen, and tower of joy.
Not sure why you removed sothoryos, that should stay.

I added most of these phrases in this commit 729a24e97f957 , so I'm closing this PR.
Thanks for your contribution!


Quaternion setFromCross is error  when vectors are opposite

Please ensure you have given all the following requested information in your report.
Issue details
Quaternion setFromCross (final Vector3 v1, final Vector3 v2)
If v1 and v2 are exactly opposite, it will return q = [0.0|0.0|0.0|1.0].
Reproduction steps/code
Quaternion q = new Quaternion();
q.setFromCross(0, 0, 1, 0, 0, -1);
System.out.println("q = "+q.toString());
Version of LibGDX and/or relevant dependencies
1.9.4
Please select the affected platforms

[x] Android

I fixed it like this :http://lolengine.net/blog/2014/02/24/quaternion-from-two-vectors-final
public Quaternion setFromCross (final Vector3 v1, final Vector3 v2) {
//		final float dot = MathUtils.clamp(v1.dot(v2), -1f, 1f);
//		final float angle = (float)Math.acos(dot);
//		return setFromAxisRad(v1.y * v2.z - v1.z * v2.y, v1.z * v2.x - v1.x * v2.z, v1.x * v2.y - v1.y * v2.x, angle);
	float norm_u_norm_v = 1f;
    float real_part = norm_u_norm_v + v1.dot(v2);

    if (real_part < 1.e-6f * norm_u_norm_v){
        /* If u and v are exactly opposite, rotate 180 degrees
         * around an arbitrary orthogonal axis. Axis normalisation
         * can happen later, when we normalise the quaternion. */
        real_part = 0.0f;
        if(Math.abs(v1.x) > Math.abs(v1.z)){
        	ans.set(-v1.y, v1.x, 0.f);
        }else{
        	ans.set(0.f, -v1.z, v1.y);
        }
    }else{
        /* Otherwise, build quaternion the standard way. */
    	ans.set(v1).crs(v2);
    }

    return set(ans.x, ans.y, ans.z, real_part).nor();
}

So what's the issue?

We need special treatment  If v1 and v2 are exactly opposit.


Adding comments/documentation

What is the recommended approach for adding comments to function apps so that others will be able to read some documentation about the developer's intentions.

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

ID: 6cf91d8c-d16b-346d-759b-f3c787dea2e5
Version Independent ID: 7e422baf-0a19-dded-ee83-a71b1c819f2f
Content: Create your first function from the Azure Portal
Content Source: articles/azure-functions/functions-create-first-azure-function.md
Service: functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

Thanks for the question. We are investigating and will update you shortly.

@DeanGross I will close this for now. If you have additional questions let me know and we can always reopen and continue.


:fire: :bug: Add dir search to _job_dir() instead of static generation

The _job_dir() function was generating a directory path statically, but instead I added a dynamic search. This fix finding the model dir when you are retraining a model or selecting one in Label Studio.

Hi @maf88
Thank you for your contribution, our team is really appreciating your effort to make the product better.
The issue with job_dir is caused with our transition to different training scheme in ML backend.
With our next Label Studio release we will work with ML backend in active learning cycle and this issue should be gone.


use globalconfig when specified (fixes ibmcloud deployments)

Builds on Cesar's PR:
https://github.com/openshift/hypershift/pull/806
and fixes the remaining areas that need to properly account for subdomains. This is necessary to get IBMCloud deployments functional again.

/retest

/lgtm
Thank you!

/approve


:bug: fix multiple tags +error logs not send + tags documentation

Errors without the .Msg("") were not correctly flushed.

@darkweaver87 2 changes to the log messages, just to keep it consistent. Otherwise it looks good.

OK, thanks :-)


Crash on startup

Hey, as one is invited to experiment with it I did so today, with mixed results. But maybe that's due to the fact that I'm trying the crazy thing on a Raspberry Pi (I want a spotify connect target on a Pi).
It took me just two days to get a working rust on the Pi but finally I was able to build librespot. My startup looks like this:
target/release/librespot --appkey ../spotify_appkey.key --username<PHONE_NUMBER> --password ******** --cache .tmp --name playpi
Authenticated !
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.front
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround21
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround40
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround41
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround50
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround51
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.iec958
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2266:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
kMessageTypeHello playpi 61672252dc61a1a7a07debc7ed0d17944194ceee 1<PHONE_NUMBER>920
kMessageTypeNotify eeehal fbffcd40ab9c48f2fbf091733a0f55a8e3b3866f 6<PHONE_NUMBER>953
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: WireError("invalid value for enum: 10")', ../src/libcore/result.rs:746
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError', ../src/libcore/result.rs:746
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: "SendError(..)"', ../src/libcore/result.rs:746

Then the process terminates. I can see the playpi target in a Spotify client for a short time. Neither linux audio nor rust are any of my strong sides but if I can be of any assistance here I'll try to be helpfull.
The output opens a couple of questions:

are unknown PCMs a bad thing?
what is this server socket he is trying to connect to? Is that a bad thing?
what is this server request channel? is it a bad thing if it can not connect?
I figured what jack is, but apparently I'm unable to run it (yet). But is it needed anyway?

I've just pushed a fix for this. Spotify have made a tiny enhancement to the protocol which librespot didn't understand.
I'm not sure about the ALSA/Jack warnings, but it should be fine.

I also always get the "Unknown PCM" and "Cannot connect to server" messages, but I ignore them and it works fine.

@plietar cool, works for me now
@herrernst I uninstalled a couple of audio related packages, first of all jackd packages and now the cannot connect and jack messages are gone.

@marcust what packages did you remove to get the jackd and "connect" errors gone?
I am running OSMC and I couldn't find  which package to uninstall (jackd / jackd2 / jack-tools etc are not installed).
While you were getting the jack errors, was librespot discovered by the clients and was spotify-connect working for you?
librespot doesn't crash for me anymore (using the latest  build from herrernst), however the spotify clients do not "see" the raspberry (I test with Android and Linux spotify clients).
I am using a HiFiBerry DAC+ on OSMC. Works fine with Kodi, and it worked just once with librespot, not sure what changed but after lots of trial and error, I can't get it to work again.

...
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm_direct.c:896:(snd1_pcm_direct_initialize_slave) slave plugin does not support mmap interleaved or mmap noninterleaved access
ALSA lib pcm_dmix.c:1034:(snd_pcm_dmix_open) unable to initialize slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
kMessageTypeHello Raspberry b7870749a82019bec25fcc2db279951e62cdbd42 1<PHONE_NUMBER>412
kMessageTypeHello Galaxy S6 b78f746216845f1309d617a88abc6e62c923d1ec 48 0
kMessageTypeNotify Galaxy S6 b78f746216845f1309d617a88abc6e62c923d1ec 49 0
...

$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ Pro HiFi pcm512x-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0

@arigit according to my apt history I uninstalled the following packages:
pulseaudio jackd jackd2 libjack-jackd2-0
and some autoremoves that removed depending packages. Then I got compile error and reinstalled
libportaudio2 portaudio19-dev
That made the warnings go away.
While I was having those errors it was discoverable for a short while before it crashed, this was due to the original bug I figure.
It has worked for me now ever since, though sometime it is not discoverable till I restart it.


Allows population of dependency_overrides

In many mono_repo setups we have a sibling packages that depends on each others.
It would be neat there was a command to generate a dependency_overrides for dependencies that are siblings packages.
I'm not sure how this would work, we'll probably need a command to add/remove the dependency overwrites, unless pub ignores them when publishing packages.

PRs welcome. 😄

With the introduction of the pubspec_overrides.yaml file, this issue is likely obsolete?

Yes I think we can close this, use pubspec_overrides.yaml instead.


fix git artifact ssh secrets

I think this is what was actually intended...

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.James Coder seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@flaviuvadan sure, just pushed an update with a test. It fails on main but passes on the branch. I also fixed a very, very minor typo in the readme. If you want that on a separate commit/pr, let me know.


Raise an error when wrong device name

Summarized and abridged comment from a different issue
# Factory name is detector_1, device name is detector_1
def detector_1() -> MyDetector:
    return MyDetector(name="detector_1")

# Factory name is detector_2, device name is pilatus_2
def detector_2() -> MyDetector:
    return MyDetector(name="pilatus_2")

There is no guarantee that the function name and device name will match up. The question is, if you want to use the second device in a plan, should you pass "detector_2" or "pilatus_2" as a parameter? We should consider the case of nested devices too. Do we want detector_2.exposure, pilatus_2.exposure or pilatus_2-exposure. The latter is the name automatically assigned to the signal on device connection.
Raise an error, either in blueapi or dodal, if the names do not match up. Force them to be the same. This would be potentially annoying when writing devices but would make debugging easier.
It just includes hidden coupling, the knowledge is exposed to the user through an exception.
Originally posted by @callumforrester in https://github.com/DiamondLightSource/dodal/pull/597#discussion_r1703958097
The current behavior is that devices are keyed by name and it is ignored in blueapi.

Should we do this and/or automagically set the device name to the function name by default? I think @coretl and @DominicOram are now in favour of that.

Yes, I think setting them the same automatically is good.


waffle.io Badge

Merge this to receive a badge indicating the number of issues in the ready column on your waffle.io board at https://waffle.io/supriyantomaftuh/auth0-angular
This was requested by a real person (user supriyantomaftuh) on waffle.io, we're not trying to spam you.

 You should sign our Contributor License Agreement in order to get your pull request merged.


This migration can be removed in case of squashing

Codecov Report

Merging #133 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #133   +/-   ##
========================================
  Coverage    94.41%   94.41%
========================================
  Files           31       31
  Lines         1056     1056
  Branches        45       45
========================================
  Hits           997      997
  Misses          49       49
  Partials        10       10

Continue to review full report at Codecov.

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


Build bot should add a warning to a pr if it doesn't content the close issue directive in the description

Closing due to the fact that it's not related to TestCafe (see build bot repo)


Pinned directory

You can pin a directory but there is no use case for the pinned directories. I would expect that the pinned directory can be used for fast navigation.
Switch to the pinned directory, move with key to a pinned dir and select. Main window would the the target

https://github.com/yorukot/superfile/assets/107802416/6fad67ba-9477-47d4-b1aa-80e3626b11a9
There seems to be no problem with my test, or have I misunderstood you?
Please provide more information if I misunderstood you. Thanks!

What should be the use case of the pinned directory? I can Pin a directory but how it can be used in any way? I would expect I can go to the pinned files/dir and use this as a quick navigation

Would you mean a shortcut key to take you right to the pinned section? Or are you expecting when you go to the list on the left it start at pinned and you move from there?

idk what the author meant, but it seems to me that using hotkeys for the sidebar would be convenient. I use fedora and here you can open applications from dock (panel at the bottom of the screen, see screenshot) using the hotkey super + 1-9
:eyes: Screenshot


implement "safe" versions of macros that will work outside repos (fixes #10)

I called them git_describe_safe and git_version_safe.  It's a pretty simple fix, and I tested it locally, but don't see an easy way to create a cargo test that is not inside a git repository.

Hey, thanks for the PR.
I can see a use case for a git_version! that doesn't error if no information is available, but I'm not entirely sure if falling back to the version from Cargo.toml is a good idea.
It really depends on the final use-case. If it would suffice, we could just have a version that gives a None or Some("...") instead of a compile error. Then a library can embed that and the version from cargo and decide which to use at runtime. Would this work for your use case?
I would also avoid the name safe, since it sounds like its somehow related to safe/unsafe code.
If we go with a version that gives a Option<&'static str>, we could call them git_version_maybe or something similar.

I don't like safe either, but didn't come up with anything better.
For the (probably?) common use case of wanting cargo install to work, I think trusting cargo is perfect, and would maybe go for git_or_cargo_version?
I don't care for the Option-returning option, because it seems like forcing everyone to duplicate the same code, for what is ideally a very simple task.  It also precludes using the output in a const or static, I think.

_safe might be a bit confusing, as in this case it is not the opposite of what's usually called unsafe.
I'd go for:

A try_ version that returns an Option or Result, and
Separate functions for this specific use case: git_or_cargo_version (and/or git_describe_or_cargo_version).

Other ideas:

Have the try_ macros return a custom type on which one can call .or_cargo_version() (or some other useful functions), or
Add some extra syntax in the current macros, like: git_describe!("--always", fallback: cargo)

Open question: Should it always take the CARGO_PKG_VERSION environment variable literally (e.g. "1.2.3"), or should there be an option to add a prefix/posfix like "v1.2.3" or "cargo:1.2.3" or "1.2.3-release"?

I like the idea of adding some informative bit to the cargo version, like "1.2.3-cargo", but would lean against it being an option. Nicer to use a simpler and "good enough" API.

One could argue that the Cargo version is more the 'real' version than the Git one, in which case no prefix/suffix for Cargo, and a 'git-' prefix for the Git version might make more sense. I guess it depends on the project. Not sure how to make it flexible without making the usage too complicated.
Any ideas?
const VERSION: &str = try_git_version!().unwrap_or(concat!(env!("CARGO_PKG_VERSION"), "-cargo"));

Could work for the Cargo-with-suffix case (though a bit unwieldy), but the other way around is going to be trickier.
We could also add named parameters to the macro syntax to support prefixes/suffixes and a fallback:
const VERSION: &str = git_version!(prefix="git-", fallback=env!("CARGO_PKG_VERSION"));
const VERSION: &str = git_version!(fallback=env!("CARGO_PKG_VERSION"), fallback_prefix="cargo-");
...

Or combined with a seperate macro for the 'Git or Cargo' case, to keep things a bit more readable:
const VERSION: &str = git_version!();
const VERSION: &str = git_version!(args=["--dirty", "--abbrev=10"]); // instead of git_describe!() ?
const VERSION: &str = git_or_cargo_version!();
const VERSION: &str = git_or_cargo_version!(git_prefix="git-");
const VERSION: &str = git_or_cargo_version!(cargo_prefix="cargo-");
const VERSION: &str = git_or_cargo_version!(cargo_prefix="cargo-", args=["--dirty", "--abbrev=10"]);
...

@de-vri-es @droundy What do you think?

I prefer the simpler approach of not giving extra options.  I just renamed the macros, but haven't added any extra flags.  I further appended "-cargo" to the version when it comes via cargo.  I think it's important to add some sort of signifier, because I expect that it is very common to have a cargo version that matches a git tag.  Now ideally the two would be identical (you'd tag exactly what you upload to crates.io), but the point of this crate (for me) is to be able to always track down which version is in use, even if I make a mistake.
I'm absolutely open to bike shedding on the extra tag.  I put it at the end, because that is pretty common, and is also how we tag dirty versions.

Now ideally the two would be identical (you'd tag exactly what you upload to crates.io), but the point of this crate (for me) is to be able to always track down which version is in use, even if I make a mistake.

Thats the point for use too :)
I'm fine with a trailing -cargo. It's a bit more human readable compared to a cargo: prefix, but I'm fine with either. The version string is mostly for human consumption, so we don't need to make it easily parsable.
If we really want to support things like custom prefixes and suffixes, then I would opt for an additional macro that returns a custom struct with an Option<&str> for the git version and a &str for the cargo version. The user can then do whatever they want at runtime.
But that doesn't need to be done in this PR, and maybe not at all :)

We could also add named parameters to the macro syntax to support prefixes/suffixes and a fallback

Implemented this in #12
@droundy @de-vri-es What do you think of this solution? Also makes it easier to add more options later.

I don't like the idea of adding named parameters, since I think they make the macro more complicated, harder to explain, and harder to use.  I think it's best to keep our macro as close as we can to the syntax of rust.

Closing this, since another PR was merged to solve the issue.


Esc not working on trusted workspace dialog

Testing #174784
This might just be a desired workflow since the window was just opened but wanted to identify it anyways.

Open a new workspace (done via the open new folder dialog on a new vscode window)
see the workspace trust dialog
esc key doesn't work

Yes, I should have been explaining this better in the TPI: very few dialogs actually prevent cancellation. For trust you must make a decision, there is no alternative. So great that we validated this is still the case!


Morning session: Peer-to-peer code review

This issue is opened for the peer-to-peer code review by the morning session team.

@AbeeraTahir Your code is clean :small_airplane:
No issue found: :slightly_smiling_face: :+1: kudoz :trophy: happy codding :100:

Good job
Great job with the project.
Highlights

The code is well organized
The README file looks professional

There is nothing I could improve.


Fixed kubeflow docs

Describe changes
This was wrong:
@pipeline(
    settings={
        "orchestrator": kubeflow_settings
    }
)

orchestrator.kubeflow <- this is the proper way.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
[ ] If my changes require changes to the dashboard, these changes are communicated/requested.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@AlexejPenner looks like this was based off of main and not develop. please make another PR ;-)

Also @AlexejPenner this PR is anyway wrong, from the last  release on "orchestrator.kubeflow": kubeflow_settings is not needed and "orchestrator": kubeflow_settings works

@htahir1 i thought we would hotfix directly on main and rebase develop on top of this - but I'm happy to change this to be based off of develop


Karma webserver fails to properly serve mp3 files

For a few of our unit tests I tried to set up audio elements and play them. The promise that Chrome returns on HTMLAudioElement.play() returns always rejects with a 'no available source' error. As far as I can tell the Karma web server that I configured to serve my mp3 files using the files pattern and required proxy does not properly serve the file.
I then kept the karma webserver alive using the singleRun: false flag and tried to access the file directly from Chrome at http://localhost:9876/audio/{filename}.mp3.
Expected behavior
The browser should be able to play the sound.
Actual behavior
The mp3 file is found. Webserver therefore seems to be properly configured. It is never able to play the file though. Audio.readyState stays at 0: HAVE_NOTHING.
Comparing the request to the mp3 file with one to our regular dev environment that is opening up the server via grunt-contrib-connect  I notice a few differences. The response headers include connection: closedespite a request for keep-alive. It is missing a content-length header but contains transfer-encoding: chunked.
Also the nocache option of the file pattern seems to be ignored as the mp3 is served with cache-control: no-cachand pragma: no-cache headers.

Enviroment Details

Karma version 1.2.0
Relevant part of your karma.config.js file

browsers: ['Chrome'],
files: [
      {pattern: 'audio/*.mp3', included: false, served: true, nocache: false}
    ],
proxies: {
      '/audio/': '/base/audio/'
},
singleRun: false

I have the same issue and fixed this in #2315. More information in #2310. It doesn't work for Chrome.

@kahwee Indeed. Missed your issue as it was already closed. Thanks for pointing me to your fix. For now until your fix is part of a release I have downgraded Karma and my tests run just fine.

Looks like this has already been released, so this can probably be closed now.

Close as duplicate https://github.com/karma-runner/karma/issues/2310
Feel free reopen
Thanks


Provisioning with Plesk must be outdated.

Hi. In installed BoxBilling at: https://billing.ltt-server.com on my Plesk Obsidian (newest version) on Centos 7 vps server. SUCCESSFUL.
I got the Plesk.php file contents from GitHub here... I then put the extension for Plesk in the /bb-library/servers/managers folder...
I then went into my BoxBilling admin to create a NEW SERVER so I could connect my Plesk server to BoxBilling. I got the following error when I tested the connection:
Plesk error: 1014 - Parser error: Request is invalid. Error in line 2: Element 'client': This element is not expected. Expected is one of ( request-settings, server, customer, webspace, subdomain, dns, db_server, mail, certificate, site-alias ).
It the Plesk.php or Boxbilling too outdated for my newest version of Plesk. I have Version 18.0.41 of plesk obsidian and centos 7. Any help here would surely be appreciated. I can't find anything on this. Plesk support says that this error is from your "Billing" components of your software... not to do with Plesk configuration. So... ???
Thanks.
Jeff.

Would be awesome if the Plesk API would be updated to support Plesk Obsidian.

Hello @lighttouchtech ,
I have a similar issue to yours. The BoxBilling is able to connect to the server however when I click on the which is on the left side of the test connection button(go to panel) it returns a 1003 wrong request XML error.

Also except for this, I have the hosting service issue. I'm defining the hosting packages in BoxBilling as the same as what I have on the server however whenever I make a test purchase in BoxBilling it's assigning a custom subscription to the customer account on the server side.
Is there anyone who can help with these issues?
Thanks in advance,

I have set up a test environment on Plesk Obsidian 18.0.43.  I do not have the issues that were mentioned in the original bug report. If you could provide me with exact steps to reproduce this error, I can take a further look.
@lighttouchtech's issue with the login URL is able to be fixed very easily, this is just a misconfigured URL in the Plesk API.
The issue with the custom subscriptions will need more work and looking at the state of some of these hosting modules, might be worth waiting for a more drastic rethink to everything before tackling.


Enable docker push CI

Hi @bluejekyll
could you set up the CI for publishing docker images ?

https://github.com/trust-dns/docker/settings/environments/new

Use "docker-hub" and save

Go to the environment "docker-hub" page from the list on https://github.com/trust-dns/docker/settings/environments

Add DOCKER_HUB_USER env and set the value to the docker hub account username
Add DOCKER_HUB_PASSWORD and set the value to a docker hub token for the account (https://docs.docker.com/docker-hub/access-tokens/)

Re-launch https://github.com/trust-dns/docker/actions/runs/1907593839

Ok, I just tried all of that, let's see what happens.

btw, we may not want to enable mDNS, I don't have a lot of faith that it's functioning properly.

Oh okay, I can remove it in the next release. Am I missing any other functionality ?

Ok, I just tried all of that, let's see what happens.

It works, thank you so much !
Ref: https://github.com/trust-dns/docker/runs/5362518557?check_suite_focus=true#step:6:13

Hi @bluejekyll
Can we add some kind of better aspect and linking to https://hub.docker.com/r/trustdns/trust-dns
It currently looks terrible, maybe in the settings you can link the GitHub repository ?
Let me know and I can provide a README for the homepage, that said you can copy the README.md contents for now

I've promoted you to admin, btw, on this github repo.
Does that give you enough privileges to update the credentials?

Copy the README to docker hub and connect this repository so users see it's linked. Just do not enable auto builds

Added.

Ok, I just tried all of that, let's see what happens.

It works, thank you so much ! Ref: https://github.com/trust-dns/docker/runs/5362518557?check_suite_focus=true#step:6:13

Quote one of my previous messages..
Sorry for bothering about the token then
I checked and it seems like it was already done: https://github.com/trust-dns/docker/settings/environments/418584772/edit
So we are all good 🎉
Is it a password or a token that you had put into the variable?

I've promoted you to admin, btw, on this github repo.

Thank you, that will be easier to maintain this repo

Added.

Thanks, it looks way better
Maybe I should try building the image multi arch now


Update cocoon_config.dart dir to reflect cocoon config rather than datastore config

cocoon_config.dart was originally designed to support datastore config only. But now it has been extended to support other features like GitHub services, gold status refreshes, etc.
To avoid confusion, the directory needs to be updated to reflect that.

https://github.com/flutter/cocoon/pull/1196


[DEV] iOS 10.2.1

//I read the issue posting guidelines.
Hello guys, just to know..
I was looking for
allproc_offset = 0x000000 & rootvnode_offset = 0x00000;
for (iPhone 4.7 10.2.1 [14D27] ).
Then I used lzssdec from xdadevtools to decript the kernelcache.release.n71 but i can't decompile the file using "Hooper Disassembler v4". ( So i can't get the correct offsets ).
( i uploaded the kernelcache.release.n71 -> here )
( bytes [0x1B7] > are this correct ) ?
./lzssdec -o 0x1B7 < kernelcache.release.n71 >kernelcache1.decrypted
xxd kernelcache1.decrypted | head -1
file kernelcache1.decrypted

Can anyone help me find this offsets?

Guide from match_portal

for >= iOS 10 unzip the ipsw and hexdump the kernel.release.* file like this:

$ hexdump -C kernelcache.release.n51 | head
00000000  30 83 b5 9b 0d 16 04 49  4d 34 50 16 04 6b 72 6e  |0......IM4P..krn|
00000010  6c 16 1c 4b 65 72 6e 65  6c 43 61 63 68 65 42 75  |l..KernelCacheBu|
00000020  69 6c 64 65 72 2d 31 31  36 32 2e 32 30 2e 31 04  |ilder-1162.20.1.|
00000030  83 b5 9a de 63 6f 6d 70  6c 7a 73 73 83 13 7d ae  |....complzss..}.|
00000040  01 64 80 00 00 b5 29 5e  00 00 00 01 00 00 00 00  |.d....)^........|
00000050  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
000001b0  00 00 00 00 ff cf fa ed  fe 0c 00 00 01 d5 00 f6  |................|
000001c0  f0 02 f6 f0 14 f6 f0 38  0e 9a f3 f1 20 f6 f1 00  |.......8.... ...|
000001d0  19 ff f1 f5 f0 5f 9f 5f  54 45 58 54 09 02 1c 03  |....._._TEXT....|

note down the offset of the ff cf fa ed fe byte sequence (in this case it's 0x1b4)

compile lzssdec from http://nah6.com/~itsme/cvs-xdadevtools/iphone/tools/lzssdec.cpp

run a command like: lzssdec -o 0x1b4 < kernel.release.n51 > kernel.decompressed

open the decompressed kernelcache in a recent version of IDA Pro (with support for iOS kextcaches)

say yes when IDA asks to split by kext

let the auto-analysis run - depending on how fast your computer is this might take a while! (it takes my 2013 MBP about 30 minutes)

go view -> open subviews -> segments and find the __TEXT:HEADER segment, the start should be FFFFFFF007004000
if it isn't note this down as you'll need to work out a couple of offsets relative to this

go view -> open subviews -> names and find the kernproc data symbol.

subtract the __TEXT:HEADER value from that, this is the kernproc offset
eg for iPhone 5S 10.1.1 kernproc is at FFFFFFF0075AE0E0 making the offset: 0x5AA0E0

now the harder one! We need to find allproc which isn't exported so is harder to find:

go view -> open subviews -> strings and find the string "pgrp_add : pgrp is dead adding process"

hit 'x' on the autogenerated string symbol name; you should see this symbol referenced from two functions

open the smaller of those functions in the IDA graph view

this is pgrp_add in the XNU source

scroll to the bottom of the CFG, the final three nodes all reference the same global variable with code like this:
ADRP  X8, #qword_FFFFFFF0075A8128@PAGE
LDR   X9, [X8,#qword_FFFFFFF0075A8128@PAGEOFF]

that's the address of allproc - subtract the kernel base to get the offset, in this case it's: 0x5A4128`

https://github.com/kpwn/yalu102/issues/64

and its already been stated 10.2.1 wont work

@GusToughSon @Mila432 , i know but if someone can give me them it will be nice.

#162
iOS 10.2.1 fixes exploits used by Yalu; you cannot add support for it.

As @lolman8776 stated, you can't use Yalu with 10.2.1, for Apple patched the exploit Yalu used.

Hey @Derewith use can use joker to decompress kernelcache automatically.
BTW Yalu is fixed on 10.2.1+

Thanks to @lolman8776 , @TheLukeGuy , @matteyeux


Add RealWorld example app to projects

Noticed all the RealWorld Blazor implementations had seemed to be all abandoned, so I decided to build it in my spare time. Hopefully this will serve as an example repository for newcomers to .NET Core/Blazor to reference in the future. Also, updated references to my username on the previous article I added (updated it recently).

Thanks


*-client packages should update peerDependencies with bump script

the tinylicious-client and azure-client have peer dependencies on the fluid-framework packages. These versions should automatically bump to stay in sync with the latest.

@heliocliu Do you have a sense for how hard this is to do? Asking you since you've been working on the version bump tool recently.

@tylerbutler Pretty easy, I guess that we've decided peerDependencies are the correct thing to use we probably want to get this done in March/April?


how to reproduce results for SWE-Bench lite?

how to reproduce results for SWE-Bench lite?
how to run it for the whole SWE-Bench?
Can I run it with Claude 3 ?

Steps to run are provided in the README.
Use --dataset_name to change the dataset to SWE Bench.
Yes it can run with Claude 3 if you are using Opper.


wire-desktop: mac 3.32.4589 -> 3.35.4861, linux 3.32.3079 -> 3.35.3348

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is the second time I've updated this version bump. I'll leave it for a bit longer but if no one's interested in reviewing I'll go ahead and self-merge this one.


Error

The bot token you entered is incorrect or the bot has its intents off

Check the bot token to see if it is correct and make sure that you have activated the intents on the Discord development site for your bot.


Fullscreen usage for all modules

Fullscreen overviews for M1 and M2 added (M3 left out because it is too minimalistic at the moment)


WIP: 3-cockpit-9: [no-test] Check for NPM dependency updates

Check for any outstanding update of point version of any outstanding NPM package dependency

[ ] npm-update

npm-update in progress on 3-cockpit-9.
Log: https://<IP_ADDRESS>:8493/logs/npm-update-754-20190805-142222/


feat: add date component and text height

resolve https://github.com/JDFED/drip-table/issues/202 https://github.com/JDFED/drip-table/issues/152


Not easy to use with Docker containers - feature request

Hello,
the only way I can think of to make this work would be to issue the influx commands via ssh to the influx container.
Is this possible, do you think?
There is no way I can install influx in the same container as node red.

Perhaps you could write a script in the node red container, with the same
name as influx, and in there pass the command on to wherever you have
installed influx.
On Wed, 11 May 2022, 18:10 bwims, @.***> wrote:

Hello,
the only way I can think of to make this work would be to issue the influx
commands via ssh to the influx container.
Is this possible, do you think?
There is no way I can install influx in the same container as node red.
—
Reply to this email directly, view it on GitHub
https://github.com/colinl/node-red-contrib-influxdb-backup/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAJLI7E2XRF2ILDMSSUE6DVJPLV7ANCNFSM5VVO3Z7A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Ah, now I understand - I should have looked at what your code does first!  I had not realised it was mainly spawning a command line.  I was fooled by the requirement to provide a port number.  I had imagined that influx provided some sort of api to kick off the backups via a sort of url, which would have worked, as I can easily write to the database.
Ok, never mind.  I don't think there is a solution.
Thanks!


parser: add additional attributes and preserve describe/it block names

This PR updated parser to expose more and accurate attributes for the NamedBlock to help consumers matching the jest test results better:

preserve the "name" of the NamedBlock. It was using markers before, which might not be helpful when we want to show users what block it is. (this might be a breaking change if people are using the markers for something...)
added a new optional attribute lastProperty to help identify if the block is a each block for example. The "last property" is the "each" in describe.skip.each() or "only" in it.only().
added a new optional attribute nameType to help identify the block's "name" type, such as 'Literal', 'TemplateLiteral', 'CallExpression'. This not only helps identify if the name is a static literal string that should match the test results' name, it also helps people that used to rely on the type-marker used in the "name" field before.
upgraded dependency @babel/parser to the latest 7.x

@firsttris I think you are using this package as well. Would like to hear your opinion on the potential breaking change for the "name" of the describe/it blocks... do you have any concern?

ok, I made the change to record the name "type" so the information is not lost after this PR. It should be functional-compatible with the previous version, that removed one of my main concern for this change.
@stephtr or @firsttris do you have some time to review this? There are other fixes waiting for on these changes, appreciate it if we can move forward on this sooner than later...

Looks like you guys are busy, that's all right. Feel free to let me know if you object to this change, otherwise, I will merge this in and cut a major release to be safe and give people time to upgrade.

all good from my side!


[utils] Allow nested imports in @mui/utils to speed up build

Part of #35840

[x] I have followed (at least) the PR section of the contributing guide.

See https://github.com/mui/mui-x/pull/9172 for context
I also took the opportunity to migrate some files to TS
One step toward #35840

@flaviendelangle previously, a lot of the exports had the unstable_ prefix but with the way the files/folders are after this PR it’s possible to import @mui/utils/useEventCallback without the unstable_ prefix - is that a concern?

Do you have an import from the same endpoint that has changed?
Or is it just on the new endpoints (@mui/utils/useEventCallback for example) that you don't have the unstable_ prefix?
If so, maybe @michaldudak can give his point of view :+1:

IMO we should discourage developers from importing from @mui/utils directly and treat this as an internal package. Individual functions that could be made public should be reexported from other packages.

Or is it just on the new endpoints (@mui/utils/useEventCallback for example) that you don't have the unstable_ prefix?

This :) what I mean is that in index.js there is aliasing happening that re-exports some of the utils with that prefix, but the nested imports don’t follow that convention currently.


CVSSP full models download link down?

Hi Patrik,
with the version v0.12.0 you said:
"There are some breaking changes in this release and models have to be re-downloaded in the new format."
However, I can't download the high resolution models from the cvssp server... link is down.
How can I download models?
Thanks,
Andoni.

Hi,
Sorry to hear the server is down! That is unexpected, thank you for reporting it. Can you please write to<EMAIL_ADDRESS>I think most people are already on Easter holidays, so it might be a while until you will get a reply.
In the meantime, I hope the 3448 model on the repo will work for you.

Yes, 404 Not Found. I'll have to wait...
Thanks,
Andoni.

The link is up from our side and I've also just verified and it looks all fine. It looks like it was never down actually. If you continue experiencing problems regarding the download, please contact<EMAIL_ADDRESS>Thanks.


Sensors: detection of device_class for binary_sensor group incorrect

Alarmo Version
v1.9.8
HA Version
2022.4
Bug description
consider following binary sensor group definition:
    binary_sensor:
    - platform: group
      name: verschluss_og
      device_class: opening
      entities:
      - binary_sensor.kontakt_elternbad_state
      - binary_sensor.kontakt_kinderbad_state

then the sensor list in Alarmo shows this sensor as Tamper instead of Opening
Fenster OG : Tamper
binary_sensor.verschluss_og

When looking up the sensors definition it definitely shows Opening as the device_class. Guess this doesn't impact the functionality but thought I report this anyhow.
Steps to reproduce
configured as above, observed result.
Relevant log output
No response

I noticed this same behavior when using the Aqara Contact Sensors.

This should be fixed in v1.9.9.
@mleiber Could you please update to the new version and confirm it's working OK now? You can close the issue if this is the case.

Thanks for looking into this. I installed v1.9.9 The sensor list now shows the binary_sensor groups as device class: door. Not as the more generic class opening. That's somewhat ok but I still would prefer if opening would also be explicitely supported. My usecase is the definition of groups with multiple sensors that together represent the state of e.g. the "hull" of the house. This includes both doors and windows.
Another observation is that if you now go into the details (click on a sensor in one of the modes definitions) it still shows Tamper as the device_class. You can change it to either door or window and it seems to stick to that. So probably the existing sensor definition didn't get updated in the upgrade and have to be manually adjusted later on. No big problem.
I keep the issue open until you respond re the opening support request - I can close it and re-open it as a feature request if you think that would be the right approach.
Again thx for the swift reaction - and the fabulous Alarmo integration !

@mleiber Alarmo supports 5 different sensor types as is described in the documentation.
This is intended as a means to simplify the setup, by automatically assigning appropriate settings.
The types in alarmo are not the same as device_classes in HA.
I don't see a need for adding a new type 'opening', I would say it should be set as either a door or a window in Alarmo.

fair enough. I'll close the issue as fixed/done.


Is it possible to fetch an endpoint which has a set of colors and then use them in config-overrides.js

I've an API endpoint which returns a set of colors. Now, consider my config in config-overrides.js:
config = rewireLess.withLoaderOptions({
    modifyVars: { "@primary-color": "#1DA57A" }
  })(config, env);

Is it possible to fetch an API and use that data to update the @primary-color attribute's value?

I haven't seen anything like that done before.


Backups do not start on run

Need to check that:

Buckets are being created appropriately
Buckets are being filled
If empty most recent bucket, backup needs to be triggered
Waits until successful backup for most recent bucket
Deletes old backups

This issue seems fixed, backups will run on start. I am having issues that the system attempts to do multiple backups as the current time does not seem to change, but I will open a new issue about that specifically.


pull request for e2e test at 12/25/2016 22:26:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


tsc-strict doesn't work with --watch flag

Documentation mentions that all tsc flags are supported by tsc-strict. But when I try to run tsc-strict with --watch I get the command stuck on ⠏ Looking for strict files....
Running the command in non watch mode works correctly. And the IDE also show errors correctly.
Any ideas if that is some sort of limitation of tsc-strict command?
I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Yes, tsc-strict wasn't designed to work with --watch in mind and it wont work. It basically runs tsc twice, one time with strict flag and compares the outputs after tsc ends, and if you run with --watch flag the output will never be collected because tsc will never end

You could potentially create a PR to add this. There is an example of an incremental program watcher inside of the typescript docs, and you'd just filter out errors coming from strict files.
Here's what I rigged up, though it's not directly usable because it uses internal tools, maybe a good starting place. The strictify command is just generating a tsconfig.strict.json which is a copy of the base tsconfig.json but with strict enabled. There's definitely a way to handle that programatically.


Change the structure of the page & improve code structure

if you want to enable the second element on the main page, You can disable comment tags in css files with the class name ".hero-section".

Share the Screenshot of your changes.

Give the access to view the video.


Parquet support

The main purpose of this PR is to add support for writing output in Parquet format. Currently this requires that data be sent to the Kafka topic in the Avro format, and the corresponding schema file be present.
This brings additional configuration properties, which are all optional and, if not present, ensure legacy connector behaviour.
Additional changes:

Update build file to Gradle 6.8.
Address vulnerability and other issues flagged by SonarQube.
Add support for direct COS endpoints.

Hi there,  is there any status on the review for this PR?


Checksum Mismatch - SHA512 on Linux.yml

Hi
I ran a standard check on the SHA512 listed on linux.yml against the latest linux x86_64_AppImage.
Returns a checksum validation mismatch.. confirmed on 2 different validation apps.
I checked the other SHA & MD5 codes to see if this has been a typo in the YML, however none also match.  Can you please check the file validity in case of issues with the package?
Rgds
Al

@ADun3306x you mean latest-linux.yml?

Hi...@mrgodhani
Yes, I found that the SHA512 string in the latest-linux.yml doesnt authenticate when running an SHA512 checksum validation on the x86_64 Linux Appimage.
Something is either definitely up with this file, or an error has been made with the original checksum in the latest-linux.yml file
Here are the steps followed for your reference.. I performed 2 tests using different controls, but both resulted in the same information.
Rgds
Al

1. Downloaded the latest x86_64 version for Linux (for Build 0.4.1)
2. Downloaded the latest-linux.yml file
3. Reviewed the YML:
SHA512 listed as tV6omX2ifC7jrz4ytvLGSiasHNd540gwa2QPCJa/eVMeEiRXvIa3sqhkYBST5uJH68oCJi/y3/3YbZDcDIDhXw==
4. Accessed the x86_64 file properties using Ubuntu's Digest Tab and checked against SHA512
Results:
SHA512 = b55ea8997da27c2ee3af3e32b6f2c64a26ac1cd779e348306b640f0896bf79531e122457bc86b7b2a864601493e6e247ebca02262ff2dffdd86d90dc0c80e15f
Results in checksum validation mismatch
5. Cross validated results using app Checksum Validator (_https://github.com/alexanderwe/checksum-validator_)
a. Dragged x86_64 file into the validator target area
b. Entered the Checksum contained within the YML
b. Selected SHA512 from the list & Executed
Result = Error Checksum Mismatch
{"checksum":"b55ea8997da27c2ee3af3e32b6f2c64a26ac1cd779e348306b640f0896bf79531e122457bc86b7b2a864601493e6e247ebca02262ff2dffdd86d90dc0c80e15f","algorithm":"SHA512"}],
"checkString":"tV6omX2ifC7jrz4ytvLGSiasHNd540gwa2QPCJa/eVMeEiRXvIa3sqhkYBST5uJH68oCJi/y3/3YbZDcDIDhXw==",
"checkAlgorithm":"SHA512","didMatch":false,

https://github.com/mrgodhani/raven-reader/releases/tag/v0.4.5 This should be fine now


README improvements. (#28)

Rename pg-browser to runtime

Rename title in README.

Stylize main repo.

More pretty.

Even more pretty.

What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
What is the current behavior?
Please link any relevant issues here.
What is the new behavior?
Feel free to include screenshots if it includes visual changes.
Additional context
Add any other context or screenshots.

new readme


Replace content with link to new repository

A simple way to redirect to the current repository.
It is not easy to create an automatic redirect in this environment. This solution has the advantage of being simple, self-explanatory and does not confuse the visitor.
Also see: https://github.com/trustoverip/toip/pull/5

https://trustoverip.github.io/toip/glossary -> that one has to be redirected

Challenges:
1: Point obsolete glossary to new glossary.
2: Redirect existing URLs (anchors) that point to the current glossary to corresponding URLs (anchors) in the new glossary
3: Create the new glossary location
ad 1: Done
ad 2: To Do (via JS)
ad 3: To Do (via CNAME (?))
There are three glossaries/repos in play:
A: OLD
glossary: https://trustoverip.github.io/toip/glossary
repo: https://github.com/trustoverip/toip
currently exists, but obsolete
B: CURRENT
glossary: https://trustoverip.github.io/ctwg-main-glossary/
repo: https://github.com/trustoverip/ctwg-main-glossary
glossary currently exists, to be phased out
C: NEW
glossary: https://trustoverip.github.io/glossary/
repo: https://github.com/trustoverip/ctwg-main-glossary
glossary to be created, new location
===
A:

This is the old glossary
Should stay online
Should have a redirect to https://trustoverip.github.io/glossary/ (or https://trustoverip.github.io/ctwg-main-glossary/ as long as the first one is not online)

===
B:

This is the current glossary
Links on the internet that point to this glossary and anchors inside the glossary should still work by redirecting to C
Instead of the glossary, there should be a provision (via JS) that redirects these anchors

===
C:

Final location of the glossary
The glossary URL should exist without a corresponding repo since the current repo (B) will keep functioning as the source for this glossary

Possible solutions by chatGPT: https://chatgpt.com/share/cb0896a1-fdda-42e3-ae5d-6805f03cf0be :
Option 2: Use a Redirect in index.html
==> In this option, the target (https://trustoverip.github.io/glossary) does not exist, and it is not made clear how to achieve that
Option 3: GitHub Pages Subdirectory
==> This is not a solution since https://trustoverip.github.io/ctwg-main-glossary/glossary/ is not the URL we are looking for
Option 1: Custom Domain (use CNAME)
I still need to get this working.
Testing here: https://github.com/kordwarshuis/test-cname/blob/main/testdir/CNAME

This PR is only applicable to point A. mentioned above by @kordwarshuis , request at @m00sey : could you accept & merge the PR?


TimeseriesGraph: mark intervals

@edeno says: It would be nice to be able to label specific time periods with a color in the background. Similar to what you can do with axvspan in matplotlib.

This is related to the annotations PR #135


[5.2] add shuffleAssociative to Collection

Shuffle an associative collection while maintaining the keys

Tests?

I didn't see any tests for the existing shuffle functionality. Any recommendations as to how to approach it?

Since the result is a random collection. Maybe a simple test is to make sure the result of the collection is not the same as the input collection. There could be a very small off chance that the shuffle actually generates the same result as the initial collection, but that is infinitesimal

but that is infinitesimal

Not really, depending on the input size. For a size of 3, it's quite likely tbh.

For a size of 2, it's 1/2.

yea because it is random there is the chance that tests fail because the off chance exists that it could return the same input.
I was assuming thats why there was no tests for the current shuffle function.
How is this data set size to test on?
        $c = new Collection([0, 1, 2, 3, 4, 5, 6, 7, 8, 9]);

Since the result is a random collection. Maybe a simple test is to make sure the result of the collection is not the same as the input collection. There could be a very small off chance that the shuffle actually generates the same result as the initial collection, but that is infinitesimal

I would also test that the value for a specific key is the same in the input and in the result.

@lucasmichot array_diff should cover that part:

    public function testShuffleAssociative()
    {
        $c = new Collection([
            0 => 'zero',
            1 => 'one',
            2 => 'two',
            3 => 'three',
            4 => 'four',
            5 => 'five',
            6 => 'six',
            7 => 'seven',
            8 => 'eight',
            9 => 'nine'
        ]);

        $s = $c->shuffleAssociative();
        $this->assertEmpty(array_diff($c->toArray(), $s->toArray()));
        $this->assertNotEquals(array_keys($c->toArray()), array_keys($s->toArray()));
    }

@gibtang do you think using array_keys is sufficient to test the order is different? @GrahamCampbell is that set size large enough to not cause issues?

Going to hold off on this. You can define it in your own project if needed.

@taylorotwell any feedback? Would you prefer an associative array be handled by a separate class altogether?

No.

You can define it in your own project if needed.


spirv-fuzz: Handle invalid ids in fact manager

Fixes #3741.
This PR fixes two bugs:

Segfault in https://github.com/KhronosGroup/SPIRV-Tools/blob/4c239bd81bf79337e4a0cfe1c9da9caf1b25108a/source/fuzz/fuzzer_util.cpp#L574-L576 when result_id doesn't exist in the module. The bug is triggered in https://github.com/KhronosGroup/SPIRV-Tools/blob/4c239bd81bf79337e4a0cfe1c9da9caf1b25108a/source/fuzz/fact_manager/data_synonym_and_id_equation_facts.cpp#L290 when representative->object() doesn't exist in the module. This can happen in certain cases if we apply TransformationMergeBlocks first.
Segfault in either https://github.com/KhronosGroup/SPIRV-Tools/blob/4c239bd81bf79337e4a0cfe1c9da9caf1b25108a/source/fuzz/fact_manager/data_synonym_and_id_equation_facts.cpp#L769 or https://github.com/KhronosGroup/SPIRV-Tools/blob/4c239bd81bf79337e4a0cfe1c9da9caf1b25108a/source/fuzz/fact_manager/data_synonym_and_id_equation_facts.cpp#L772 happens if either dd1.object() or dd2.object() doesn't exist in the module. This can happen when AddDataSynonymFactRecursive is called recursively from ComputeConversionDataSynonymFacts. This bug is described in #3741.

@afd, I've updated the description. Regarding the points mentioned in your previous comment:

All changes in the PR fix the issue.
I've updated the test from #3741. The new test uses both TransformationMergeBlocks and KillDef to test two bugs as mentioned in the description comment accordingly.

Let me know if you need any clarification.


Blobs

Here at Silk Labs we've had a Blob implementation for React Native for a while. We want to contribute it back upstream. This issue discusses the API and implementation and tracks progress.
Motivation
Like in the browser, Blobs are opaque lumps of (usually binary) data that can be read into TypedArrays or strings, but don't have to be. Concretely in React Native that means that the binary data lives in native and not in JS, unless you explicitly request it. Why is this useful? Say you're receiving some data via XHR, WebSocket, or WebRTC, or some custom method that you've implemented and you want to display it in an <Image> view. Or you want to send it along through some other means without looking paying the cost of transferring it to the JS thread and back.
We already have something somewhat similar to this for images on iOS (RCTImageStoreManager). This would be a generalization of that.
API
The web has an API for Blobs. It's not particularly pretty or anything, but it's kind of a standard, so I think we should use that, or at least a pretty good subset.
Creating
Blobs typically get created when JS is receiving data, e.g. via XHR, WebSocket, etc. I am planning on making
xhr.responseType = 'blob';

and
websocket.binaryType = 'blob';

work so that when you specify those settings, the XHR and WebSocket responses will return Blob objects and not transfer the data to the JS thread. This works exactly like on the web.
Mutating
A subset of mutation operations will be supported:
let combinedBlob = new Blob([existingBlob, anotherBlob]);
let halfBlob = blob.slice(0, blob.size / 2);

I'm not planning on supporting creating a blob in JS from JS data (e.g. a string or TypedArray), though it should be easily implementable.
Consuming
Like in the browser, you'll be able to map Blobs to URIs that you can then use in things that eat URIs, e.g. the  view:
let url = URL.createObjectURL(blob);

Also like in the browser, you'll be able to read the blob into a TypedArray or string. I am planning on simply implementing the web's FileReader API.
Freeing
The following method is part of the Blob standard, but is currently not implemented by browsers. However, because we can't automatically garbage collect our blobs like browsers can, it will be necessary to provide a manual way of freeing blobs, so that consumers can make use of it when appropriate:
blob.close();

Here's a complete example of how consuming blobs would work: https://gist.github.com/philikon/4592efd153673f3e64dec353046af7a8
Implementation
Proposal
React Native already has a loose concept of a "blob", in other words, a lump of data that's not directly accessible by JS. The iOS (RCTImageStoreManager) mentioned above is an example.
XHR and most notably the <Image> tag already have a way to express a reference to a blob:
{uri: "some://uri/that/gets/resolved"}

How does some://uri/that/gets/resolved get resolved? On iOS, it gets resolved through a RCTURLRequestHandler. On Android, it gets resolved through a ContentProvider.
For instance, you can upload binary data provided by a system resource in the following way:
const xhr = new XMLHttpRequest();
xhr.open(...);
xhr.send({uri: "some://big/blob/of/binary/data"})

As long as some://big/blob/of/binary/data is resolvable by a RCTURLRequestHandler or ContentProvider, this will Just Work(tm) already.
On this basis, I'm proposing to implement Blobs as simply another way of URI-addressable binary data. Our implementation does exactly that.
Progress
Prep work:

[x] Make XMLHttpRequest and XMLHttpRequest.upload proper EventTargets so that we can receive progress events even when we're not receiving data to JS, because we're receiving it into a blob (#7017)
[x] Add responseType as a concept to RCTNetworking, so that we can add 'blob' later (#8324)

Implementation work, most likely by porting silk-react-native-blobs:

[ ] Provide native blob storage with NativeModule API, and JS implementation of Blob class
[ ] Provide URI integration (RCTURLRequestHandler on iOS, ContentProvider on Android)

Future implementation work:

[ ] XHR integration: allow xhr.responseType = 'blob' and xhr.send(blob)
[ ] WebSocket integration: allow websocket.binaryType = 'blob' and websocket.send(blob)
[ ] Implement FileReader API for reading blobs into JS e.g. as TypedArrays. This can just be a thin wrapper around XHR, yay!

Can you coordinate with @satya164, he has a Blob implementation almost ready I believe.

Yep, that's the reason for this issue :), so that we can coordinate. I believe he's uplifting our Blob implementation.

Hey! Yeah, so I've been working to port changes from @philikon's implementation to RN master.
I've only worked on Android part so far.
My focus was to first get it working with firebase so people could upload files to firebase. This has slightly different requirements since we need to create a blob locally from a file before uploading.
So I think in addition to the proposed APIs, we need two more non-standard methods,
Blob.fromURI(uri: string, options: { type: string }): Promise<Blob>
File.fromURI(uri: string, options: { type: string }): Promise<File>

I just copied @philikon's implementation for the blob module and with minor changes, and writing some code to support XHR I've been able to get the following working,

[ ] Create blobs when data is received via XHR
[ ] Create blobs from a local file URI
[ ] Upload blobs to a server (e.g. - firebase) via XHR

I couldn't get URL.createObjectURL working from the current implementation, looking into it right now.
I've not yet tested the WebSocket implementation yet, but since that was already implemented I guess shouldn't take much time to get it working.
So things I need to do are,

[ ] Get content provider working
[ ] Get the WebSocket implementation working

What I'd like to explore is, right now when you create a blob from URI, I read it to memory as bytes. But we could probably just store the uri and read the bytes when needed (we'd need get the bytes length though, so we'd need to read it twice!)
I also want to know if there's a full test suite available to test my implementation against.

So I think in addition to the proposed APIs, we need two more non-standard methods,

Blob.fromURI(uri: string, options: { type: string }): Promise
File.fromURI(uri: string, options: { type: string }): Promise

I don't understand the need for File. What use cases does File solve that aren't covered by Blob?
What specific use cases does Blob.fromURI(...) solve? If I have a URI, why wouldn't I make an informal {uri: ...} blob object? If there's an RCTURLRequestHandler / ContentProvider for the URI in question, it'll already work with XHR! The only thing that we gain with Blob support is concatenation and slicing, but as you say, that's really hard to do if we don't at least know the size of each part. I'm not familiar with Firebase, but I'd like to hear more about why a generic URI-based Blob is a good idea. For now it seems pretty hard to implement Blob semantics around any lump of data that's not already stored in memory. Maybe a different API that also happens to expose uri for XHR-compatibility would be better suited for Firebase integration?
It also sounds like you might be thinking about this backwards. If people want to create blobs from some sort of datasource, the datasource should return Blob objects, e.g. someFirebaseAPI.get(options).then((blob) => ...). Or would Blob.fromURI() be an API that's meant only for React Native modules, much like the non-standard Blob.create() I introduced?

I don't understand the need for File. What use cases does File solve that aren't covered by Blob

File implements the File API from the spec. It's just a thin wrapper around blob.

What specific use cases does Blob.fromURI(...) solve? If I have a URI, why wouldn't I make an informal {uri: ...} blob object? If there's an RCTURLRequestHandler / ContentProvider for the URI in question, it'll already work with XHR! The only thing that we gain with Blob support is concatenation and slicing, but as you say, that's really hard to do if we don't at least know the size of each part. I'm not familiar with Firebase, but I'd like to hear more about why a generic URI-based Blob is a good idea. For now it seems pretty hard to implement Blob semantics around any lump of data that's not already stored in memory. Maybe a different API that also happens to expose uri for XHR-compatibility would be better suited for Firebase integration?

Libraries like firebase expect a blob or file object for uploading. We cannot pass a { uri: string } object to firebase. So allowing to create a file/blob object from an URI is the only way people can use firebase for now. I don't like it much, but I don't think there are any options.

It also sounds like you might be thinking about this backwards. If people want to create blobs from some sort of datasource, the datasource should return Blob objects, e.g. someFirebaseAPI.get(options).then((blob) => ...). Or would Blob.fromURI() be an API that's meant only for React Native modules, much like the non-standard Blob.create() I introduced?

This is so that we'll be able to pass blob objects to libraries which don't accept uris. I think in general this should be discouraged though, and libraries can internally use this API if they need.

File implements the File API from the spec. It's just a thin wrapper around blob.

Meh ok. Seems unnecessary, unless there's demand from 3rd party libraries out there. (Perhaps Firebase?)

Libraries like firebase expect a blob or file object for uploading.

Ok, so then just do
const response = await fetch(uri);
const blob = await = response.blob();
someFirebaseAPI.consume(blob);

Or in XHR spelling:
const xhr = new XMLHttpRequest();
xhr.open('GET', uri);
xhr.responseType = 'blob';
xhr.onload = () => {
  const blob = xhr.response;
  someFirebaseAPI.consume(blob);
};
xhr.send();

Either variant will load the data from the URI into a Blob that can then be passed to Firebase. Though, I still don't quite understand what Firebase is going to do with it? Upload it to the server?

Meh ok. Seems unnecessary

It's very tiny amount code to polyfill a web API, which makes sure libs which need File constructor will work.

Either variant will load the data from the URI into a Blob that can then be passed to Firebase.

I didn't know I can do fetch from local URI. Or are you proposing to implement this API?

I didn't know I can do fetch from local URI.

Yep, should already work!

It's very tiny amount code to polyfill a web API, which makes sure libs which need File constructor will work.

Sure, ok.

It also sounds like you might be thinking about this backwards. If people want to create blobs from some sort of datasource, the datasource should return Blob objects, e.g. someFirebaseAPI.get(options).then((blob) => ...). Or would Blob.fromURI() be an API that's meant only for React Native modules, much like the non-standard Blob.create() I introduced?

I had the same thought, the issue that @satya164 pointed out to me is that if the datasource API (let's say ImagePicker which lets you pick an image from your camera roll or take a photo) returns a Blob every time then people who are not interested in the Blob but rather in other other values like the URI might just forget to close the Blob. We could make it an optional parameter on those APIs:
let imageBlob = ImagePicker.launchImageLibraryAsync({
  allowsEditing: false,
  aspect: [1, 2],
  responseType: 'blob',
})

Thoughts @satya164 @philikon?

Another approach would be to write a separate module that creates a Blob from a URI -- BlobLoader.loadFromURIAsync(uri). This would keep the function out of the Blob/FileSystem namespace but still let you work with any API that gives you back a local URI.
That said, one thing I like about libraries that return Blobs (like Brent's ImagePicker example) is that you either get back a valid Blob (assuming it's eagerly loaded) or the call fails. There's no uncertain state halfway where you get back a valid URI but then the file on disk gets deleted before you load the Blob from the URI.
So we might want both -- Blob-aware APIs that give you back Blobs in a more atomic way, and a generic URI-to-Blob loader that works with any URI-aware API.

Another approach would be to write a separate module that creates a Blob from a URI

Separate module for creating blobs from URI sounds good to me

We could make it an optional parameter on those APIs

That could work, it only saves one line of code of code though (not really since you've to specify responseType: 'blob' anyways).
While the blob-aware APIs seem nice to me in a general sense, in case of RN I'm not super happy about them since the user always has to manually free the blob. . One thing I wanted to explore is to lazy-load URI based blobs. But this negates the case @ide mentioned about not having to deal with uncertain state.

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.

@hramos  Please reopen , blob support is very critical to my current issue. https://github.com/facebook/react-native/issues/16034#issuecomment-333385849

Theres no point in re-opening. There's already a WIP PR implementing it.

Can you post that here and on the ticket I've opened? ETA on completion etc.?

There's no ETA. https://github.com/facebook/react-native/pull/11573

So how can we get this issue prioritized, it appears that PR has been in limbo for almost a year

Only way is to help me with the iOS code and then wait for review.

@satya164 What is needed on IOS side?


IMU Accel and Gyro coordinate frames

I am using a VLP 16 Puck to input data to the Horizontal Lidar input. Everything seems OK but I think I still don't have the coordinate frames or the units right. Can anyone tell me the Accelerometer and Gyro coordinate frames and the units of measurement? Is there any relevant documentation I can look up?

The coordinate frames are configured in your URDF. I suggest reaching out to http://answers.ros.org/ for help with that.


adfree doesn't mute add on Android 5.1 in a ID2ME phone

I can't seem to mute the audio when ads are playing. Any chance of an update of this wonderful app since there's no official version of Lineage for this device yet?

i am not planning to add support for lower API levels in the near future. I tagged this as a feature-request.


test: add regression test for using route in template

🔗 Linked issue

📚 Description
We have a weird issue with latest vue-router now that we don't de-default routes (https://github.com/nuxt/nuxt/pull/28912). When using route in template, it throws a hard error:
Cannot convert object to primitive value

  at String (<anonymous>)
  at Object.replacer (@vue/shared#cjs:488:12)
  at JSON.stringify (<anonymous>)
  at Module.toDisplayString (@vue/shared#cjs:466:196)
  at setup (pages/index.vue#cjs:18:41)
  at _sfc_main.setup (pages/index.vue#cjs:37:23)
  at callWithErrorHandling (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js#cjs:200:19)
  at setupStatefulComponent (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js#cjs:7757:25)
  at setupComponent (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js#cjs:7718:36)
  at renderComponentVNode (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js#cjs:645:15)

https://stackblitz.com/edit/github-38rsyf-1zb3ja

To be fair, this is not something users should ever do on a live site, but it's common in development or debugging and the error is very confusing.
The reason occurs because, since<EMAIL_ADDRESS>the entire imported module is stored on the route object for use with data loaders (https://github.com/vuejs/router/commit/5ff2cd09d656a6f5ff38517c87d48b89f41ff49b).
That is fine, except that toDisplayString from vue (used to stringify objects in template) basically now can't handle displaying a route in the template. That is because toDisplayString handles stringifying more complex objects like Modules like this:
if (isObject(val) && !isArray(val) && !isPlainObject(val)) {
  // native elements
  return String(val)
}

https://github.com/vuejs/vue-next/blob/0126cfff9d93bcec70e5745519f6378e3cd3f39c/packages/shared/src/toDisplayString.ts#L57-L60

A workaround is to partially revert https://github.com/nuxt/nuxt/pull/28912 and de-default route components for now, until this is resolved either in vue (by adding the ability to log Modules) or in vue-router.

This will probbaly not fix the issue you mentioned, it had to be fixed in vue router. I just released a patch version

I will have to add the toDisplayString test to Vue router 😅
thanks for finding out about it