🐛 [firebase_core] Is not compatible with headless integration testing.

Firebase fails to setup connection for integration test for headless device (It succeeds for -d macos though).
Steps to repro:

Clone PR: https://github.com/date-game-com/date-game/pull/2
cd pkgs/date_game
Run flutter test integration_test/app_test.dart -d flutter-tester
Get error.

Output for print('!!!! defaultTargetPlatform: $defaultTargetPlatform') is !!!! defaultTargetPlatform: TargetPlatform.android.
Error:
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following PlatformException was thrown running a test:
PlatformException(channel-error, Unable to establish connection on channel., null, null)

When the exception was thrown, this was the stack:
#0      FirebaseCoreHostApi.initializeCore (package:firebase_core_platform_interface/src/pigeon/messages.pigeon.dart:210:7)
<asynchronous suspension>
#1      MethodChannelFirebase._initializeCore (package:firebase_core_platform_interface/src/method_channel/method_channel_firebase.dart:29:44)
<asynchronous suspension>
#2      MethodChannelFirebase.initializeApp (package:firebase_core_platform_interface/src/method_channel/method_channel_firebase.dart:73:7)
<asynchronous suspension>
#3      Firebase.initializeApp (package:firebase_core/src/firebase.dart:43:31)
<asynchronous suspension>
#4      main (package:date_game/main.dart:10:3)
<asynchronous suspension>
#5      main.<anonymous closure> (file:///Users/polinach/_/date-game/pkgs/date_game/integration_test/app_test.dart:22:5)
<asynchronous suspension>
#6      testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:165:15)
<asynchronous suspension>
#7      TestWidgetsFlutterBinding._runTestBody (package:flutter_test/src/binding.dart:982:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

The test description was:
  Smoke
════════════════════════════════════════════════════════════════════════════════════════════════════
00:06 +0 -1: Smoke [E]
  Test failed. See exception logs above.
  The test description was: Smoke

Thanks for the report @polina-c
I do see same behavior as reported. The repo uses gradle-7.5-all.zip so https://github.com/firebase/flutterfire/issues/10825#issuecomment-1535969790 isn't related.

Thank you for checking. The same issue applies to unit testing.
To repro issue with unit tests:

Clone https://github.com/date-game-com/date-game/pull/4
cd pkgs/date_game
flutter test test/logic/shared/primitives/crud_test.dart

What would be right solution? Is it hard to implement?
May be there is workaround?
I really want to test cover user flows, so that GitHub bots could verify them on presubmit.
May be flutter-tester is wrong device for integration tests?
What is recommended device for testing features, that use firestore, on GitHub bots?

Tagging @Lyokone @russellwheatley for their input on this.

Hi @polina-c, just to clarify, presumably you still mean running integration tests on an emulator, simulator or Chrome driver without the GUI also running?

I am interested to run integration tests by github bots on presubmit.
I want to manipulate UI, i.e. to use pumpWidget, finders, gestures and so on.
Does it answer the question?

Let me make sure there is no misunderstanding.
Flutter Framework has concept of integration tests where the flutter application is run by test engine, button clicks are emulated and results are verified. Applications in such tests have access to internet and are fully functional.
However, calls to firebase backend fail, because platform is detected as android, while it is not android.
It would be very beneficial to enable Flutter integration tests to to verify user flows that work with authentication and database.
Does it change something?

thank you!
Which platform is recommended for testing interaction with Firebase on GitHub bots, instead of headless, then?

I don't know enough about GitHub bot capabilities to give you an answer on that I'm afraid. I can point you in the direction of where our e2e tests are ran via GitHub actions, this is android & this is iOS
a summary of what is happening in each action:

Setup nodejs and java to run Firebase emulators.
We cache certain elements to speed up CI run (e.g. emulator, Pod files, Firebase emulator)
Run melos boostrap to install dependencies and link packages.
Run Firebase emulator to interact with e2e tests.
Boot up emulator for android or simulator for iOS.
Run flutter test integration_test/e2e_test.dart which runs our e2e test suite here.

Thanks.
I think flutterfire documentation should contain instruction how to do presubmit integration test coverage, as it is necessary to build reliable flutter/firebase applications.

Hello @polina-c, after discussing it internally, we will not add instructions on how to integrate CI/CD with FlutterFire because we feel it would duplicate informations that can be found elsewhere and that are highly dependent on other CI platforms like GitHub Actions, Codemagic or else ... Please found the current official instructions here: https://firebase.google.com/docs/test-lab/flutter/integration-testing-with-flutter


Set up a dev server to host site for viewing and debug

We need a dev server to see what it will look like. It should set up so that git pull will get the master stuff from here.

My suggestion is to continue what we already have, just modify the docker build to copy static files instead of building the current vie project.
The current setup is the develop branch for dev, master (or tags) for production.

Sounds good. You're right about using the dev branch for the dev machine, bad thinking on my part.

GitHub actions may be of interest for automated builds? Should be pretty easy with actions such as: https://github.com/peaceiris/actions-hugo

just modify the docker build to copy static files instead of building the current vie project.

But we still need a hugo command somewhere to generate the HTML, right? Where would this be?

After quickly checking the documentation for Hugo, I'm guessing that something similar to the below Dockerfile should work:
FROM ubuntu:20.04 as build

RUN apt install hugo

COPY . /code
WORKDIR /code

RUN hugo -D

FROM nginx:alpine

COPY --from=build /code/public/ /usr/share/nginx/html/

EXPOSE 80

We have the dev page active on the cluster, automated container generation on dockerhub for develop and production, and manual deployment to k8s. I think we can close this one?


nanopolish eventalign slow processing speed

Hello,
I am using following command to run nanopolish eventalign but it is very slow.
nanopolish eventalign \
--reads ./index/*.fastq \
--bam ./sorted_PF_NCBI_reference.bam \
--genome ./GRCh38_latest_rna.fna \
--signal-index \
--scale-events \
--summary ./PF/sequencing_summary.txt \
--threads=48 > ./PF_CHEUI_NCBI_output_R1.txt

Here is the job script with computation allocation:
#SBATCH --nodes=1
#SBATCH --mem=128G
#SBATCH --cpus-per-task=48

I am wondering if there is anything I can do to speed up the process.
Thank you
Mohit

You can partition the BAM into smaller pieces, then merge the results. Also, https://github.com/hasindu2008/f5c may be faster.


fix(web): menu navigation UI/UX + analytics meta tags

Summary by Sourcery
Enhance the web application's navigation by introducing an ActiveLink component for better active state management and fix UI/UX issues in the session button and navigation menu. Update analytics configuration to use tokens from appConfig.
New Features:

Introduce an ActiveLink component to handle navigation links with active state styling.

Bug Fixes:

Fix UI/UX issues in the session button and navigation menu by adjusting alignment and hover effects.

Enhancements:

Refactor navigation links to use the new ActiveLink component for consistent active state management.
Improve mobile navigation icon animation for better visual feedback.

 [Bitlauncher] Development Support - Andler, September 2024


类别排序（order of categories)

Expected behavior (预期行为)
类别按照拼音字母排序
Actual behavior (实际行为)
看不出排序的规则
NexT Informations
Add the  ✔  sign before an item which is affected by this behavior.
NexT Version:
✔ -  Master

Latest Release
Old version -

NexT Scheme:

All schemes
Muse
Mist
✔  -  Pisces

Other Informations (Like Browser, System, Screenshots)

@ganyuanda dont understand u, write in English if not solved. If solved, close it please. Thank's!


closes issue #4: Restore not working in AWS and Openstack

Description: Modified the logic of copying data from encrypted backups to fix the bug in restore functionality.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


Can not filtering for empty time value with ODataV4

To reproduce,

publish the page 9318 as ODataV4 web service with name ServiceOrders
create a new service order in the web client (no need to fill anything, just get the number)
make sure the Response Time field is empty
try to filter for this record with an ODataV4 url e.g. in Postman like this (<your_url>/ServiceOrders?$filter=%28Response_Time%20eq%20%2700%3A00%3A00%27%29)
the result will be empty, the OData can't find the record

The reason is, the Response Time is initialized with 0T by default, but if you validate 000000T into the filed the previous filtering method will works.
It's really annoying, because the JSON response is 00:00:00 in both cases, so I can't differentiate in between, and I also don't know how can I filter to the empty value.

You can filter by ServiceOrders?$filter='Response_Time' eq null

You can filter by ServiceOrders?$filter='Response_Time' eq null

I've tried. Response contains the whole, unfiltered record set.
Original issue still exist. Json response has 00:00:00 in case of 12:00 AM and empty value as well.

Reactivating and creating an internal work item to follow

Oh, and this requires $schemaversion=2.1

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: .


Add missing migration

Coverage remained the same at 96.019% when pulling ce3d15fb5defdb07853fb89e0354f200118fc97d on issue-341-missing-migration into a6e6aa257e188584388779278769412864baafad on master.


Rounding power generation and load

Calculating OPF results in power injections with many decimals. This can lead to problems, e.g., buses that have 1e-10 generation. I think this especially problematic for the MILPs.
The way to fix this is to round the values. In _pp_utils, we can round the df_bus values to, say, 5 decimals. Then we should check that p_mw indeed sums to zero, i.e., we have balanced power injections. Otherwise we need more or less rounding, I'm not sure which of the two is better.

I've rounded it down to 5 decimals. This is high enough to avoid numerical errors (which are usually caused by 0's that are approximated as 1e-9) and ensures we still have near-perfect balanced power injections.


Add indexOf string functions

As mentioned in #37.

These functions seem unnecessary (as do their Ramda counterparts) given the dynamic dispatch provided by R.indexOf and R.lastIndexOf:
> R.indexOf('a', 'banana')
1
> R.indexOf('x', 'banana')
-1
> R.lastIndexOf('a', 'banana')
5
> R.lastIndexOf('x', 'banana')
-1

As a result, S.indexOf and S.lastIndexOf already provide the desired functionality:
> S.indexOf('a', 'banana')
Just(1)
> S.indexOf('x', 'banana')
Nothing()
> S.lastIndexOf('a', 'banana')
Just(5)
> S.lastIndexOf('x', 'banana')
Nothing()

I'll open a Ramda issue for further discussion.

Ah I didn't realise the indexOf functions in Ramda had dynamic dispatch. Would be nice to get rid of the string versions if that's the case.

ramda/ramda#1113 renders these functions unnecessary. :)


Extending Reply with Connection property

Could you rerun:
scripts/update-codegen.sh
and commit?  That should update things to get you past the sanity check.

Looks like you need a rebase because #357 was merged

Could you please do this as a rebase rather than merging master in?  Merging master in results in a bunch of extra files in the change and a more confusing history.  It should be the case that a rebase here would just result in one patch, that is doing the one thing of Extending Reply with Connection property... this patch has a lot of other stuff going on.

Ok, I'll fix, but I think now is easier to create new PR and remove this one :)

@lobkovilya That's cool.  If creating a new PR is easier for you, please do close this one and create a new one :)


163461032 relocate mouse indicator

Adjust position of the CollectButton React component when it is being used as the selected mouse indicator at the organism level to match UI spec.  This required changing the creation point, so we could position the CollectButton on top of other elements in the z-order (previously we were creating it in the OrganismsContainer, now we are doing so in organism space) .  I also adjusted the collect button styling (both in the left nav panel and in the organism view) so that it has styling that is up to date with the latest spec (sizing, positions, hover states, etc. had drifted from the spec updates).

Agree.  I'm not crazy about the organizational location of the CollectButton, but to visually move it up on top of everything required in the spec, we would need to change the positioning style of everything in the two-up and 4-up displays which felt like a chaotic set of changes.  I wish the mouse indicator was just part of the bottom toolbar, but we're so limited on space that that would never be an option.


change Vagrant image to ubuntu/jammy64

https://lists.ubuntu.com/archives/ubuntu-announce/2022-July/000281.html indicates July 14, 2002 as the EOL date for ubuntu Impish release, therefore change it to Jammy Jellifish one https://lists.ubuntu.com/archives/ubuntu-announce/2022-April/000279.html.

I'm still getting an error when trying to run vagrant up - let me know if you see the reason and how to fix it:
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/jammy64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/jammy64' version '20220810.0.0' is up to date...
==> default: Setting the name of the VM: tetragon_default_1660755860849_44382
==> default: Clearing any previously set network interfaces...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["hostonlyif", "create"]

Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp


Typo formatting

Here are some small typographic and grammatical fixes, markup fixes and one or two places where more idiomatic Perl 6 is being used.
No semantic changes, afaict.
On a related note, I really like what I read so far (not quite through yet)

Thanks!


Second scrollTo on I phone IOS 9.3.2

At first scrollTo works, when next run scrollTo do nothnik on other devices is ok

Hi, you need to provide a lot more information to be able to reproduce the issue.
First, try to reproduce it on the plugin's demo page. If it works there, you'll need to debug your code because the problem is likely there.
If you can, please report the steps to reproduce.
Thanks


[ERROR] your public ip doesn't match the one resolved for siteurl

Today my rocketchat-server snap did an automatic refresh from version 4.1.2 to 4.2.2. Afterwards the service was no longer available. Neither the server's IP address or the DNS settings were changed.
When I trigger a manual refresh i get the following error:
$ snap refresh
error: cannot perform the following tasks:
- Run configure hook of "rocketchat-server" snap if present (run hook "configure": [ERROR] your public ip doesn't match the one resolved for siteurl)

$ snap get rocketchat-server
Key                               Value
backup-on-refresh                 disable
caddy                             enabled
caddy-url                         https://chat.heimathafen-nf.de
db-feature-compatibility-version  3.6
https                             enabled
mongo-oplog-url                   mongodb://localhost:27017/local
mongo-url                         mongodb://localhost:27017/parties
port                              3000
siteurl
snap-refreshing                   true

Also setting the siteurl confuguration seems to have no effect:
$ snap get rocketchat-server
Key                               Value
backup-on-refresh                 disable
caddy                             enabled
caddy-url                         https://chat.heimathafen-nf.de
db-feature-compatibility-version  3.6
https                             enabled
mongo-oplog-url                   mongodb://localhost:27017/local
mongo-url                         mongodb://localhost:27017/parties
port                              3000
siteurl
snap-refreshing                   true

$ snap set rocketchat-server siteurl="https://chat.heimathafen-nf.de"

$ snap get rocketchat-server
Key                               Value
backup-on-refresh                 disable
caddy                             enabled
caddy-url                         https://chat.heimathafen-nf.de
db-feature-compatibility-version  3.6
https                             enabled
mongo-oplog-url                   mongodb://localhost:27017/local
mongo-url                         mongodb://localhost:27017/parties
port                              3000
siteurl
snap-refreshing                   true

Here my current snap info:
$ snap info rocketchat-server
name:      rocketchat-server
summary:   Rocket.Chat server
publisher: Rocket.Chat (rocketchat✓)
store-url: https://snapcraft.io/rocketchat-server
contact:   https://open.rocket.chat/channel/ubuntu-snap
license:   unset
description: |
  Have your own Slack like online chat, built with Meteor. https://rocket.chat/
commands:
  - rocketchat-server.backupdb
  - rocketchat-server.initcaddy
  - rocketchat-server.mongo
  - rocketchat-server.restoredb
services:
  rocketchat-server.rocketchat-caddy: simple, enabled, active
  rocketchat-server.rocketchat-mongo: simple, enabled, active
  rocketchat-server:                  simple, enabled, inactive
snap-id:      wdBUbiEuMNHmAHLBCXQXOcXaOCvbWS1e
tracking:     4.x/stable
refresh-date: today at 10:46 UTC
channels:
  3.x/stable:       3.18.3 2021-11-28 (1491) 289MB -
  3.x/candidate:    3.18.3 2021-11-28 (1491) 289MB -
  3.x/beta:         3.18.3 2021-11-28 (1491) 289MB -
  3.x/edge:         3.18.3 2021-11-28 (1491) 289MB -
  latest/stable:    3.18.3 2021-12-06 (1491) 289MB -
  latest/candidate: 3.18.3 2021-12-06 (1491) 289MB -
  latest/beta:      3.18.3 2021-12-06 (1491) 289MB -
  latest/edge:      4.1.2  2021-12-06 (1497) 285MB -
  4.x/stable:       4.2.2  2021-12-15 (1501) 255MB -
  4.x/candidate:    4.2.2  2021-12-15 (1501) 255MB -
  4.x/beta:         4.2.2  2021-12-15 (1501) 255MB -
  4.x/edge:         4.2.2  2021-12-15 (1502) 255MB -
  2.x/stable:       2.4.14 2020-12-23 (1453) 267MB -
  2.x/candidate:    2.4.14 2020-12-23 (1453) 267MB -
  2.x/beta:         2.4.14 2020-12-23 (1453) 267MB -
  2.x/edge:         ↑
installed:          4.1.2             (1497) 285MB -

experienced the same issue, had to revert to a backup on the latest 3.x channel

Today i noticed that the issue kind of resolved itself. This morning my RocketChat server was running at version 4.2.2 without any further interaction on my side since yesterday 🤷♂


chore: reduce size of devcontainer dockerfile

Fixes #4037
Describe the changes you have made in this PR -

Moved to ruby:3.2.1-slim
Install yarn with npm
Update the nodejs installation
Add additional packages which may not available  in slim image

Size difference
Previous Image Size - ~1.7 GB
Current Image Size - 1.02 GB
Tests
Tested on Github Codespaces, working as expected.
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

This is great


testing connecting issue [don't request assignment]

Link to issue: meshery

Hi, can I have this issue assigned to me, please?

currently working on this issue in the Layer5 repo, creating a new issue in each repo mentioned so as to effectively maintain the procedure of creating an issue and thereafter a PR that closes it.

let's discuss this item on today's website meeting,
please add this agenda in the docs: https://docs.google.com/document/d/1XczAHXVe2FIWPqiF57ospJ43zw5cZQ7ui8mn39v5EvA/edit#heading=h.69qskjv558bk


Getting an error: "No .lua files found!"

The GUI loads fine but I get a 500 error when the board is trying to reach http://localhost:3000/admin/queues/api/queues?activeQueue=&page=1&jobsPerPage=10:
{
  "error": "Internal server error",
  "message": "No .lua files found!",
  "details": "Error: No .lua files found!\n    at loadScripts (/Users/bob/web/my-project/build/server.js:69539:15)\n    at /Users/bob/web/my-project/build/server.js:69529:19"
}

I'm on esbuild. Node version v18.16.0.

Ah, apparently I need to copy the .lua scripts over to my /build dir https://github.com/OptimalBits/bull/issues/2409#issuecomment-1213322957

That works! For anyone with the same issue, you can put a simple copy script in your package.json:
"scripts": {
  "dev:bull": "cp node_modules/bull/lib/commands/*.lua build/"
}


MHelp

Mentorhelp, most likely this is going to end up as a clone of ahelp, with a different set of flags and stripped down UI.

Might be usefull if players with a certain amount of playtime could apply for mentor, then they can awnser Mhelps for newer players wile they are dead. Would be less workload for admins.

Might be usefull if players with a certain amount of playtime could apply for mentor, then they can awnser Mhelps for newer players wile they are dead. Would be less workload for admins.

I already have the application forum up when it comes in.


pip install error - conflict dependence

Hi,
I have setup a clean virtual environment using venv. There is nothing but the below

`
sam@Sams-MacBook-Pro Deepface % ls
read.me
sam@Sams-MacBook-Pro Deepface % python3 -m venv deepface
sam@Sams-MacBook-Pro Deepface % source deepface/bin/activate
(deepface) sam@Sams-MacBook-Pro Deepface % pip3 list
Package    Version

pip        21.2.4
`

When I install the deepface using pip, it gives the following error

`
(deepface) sam@Sams-MacBook-Pro Deepface % pip3 install deepface
Collecting deepface
Using cached deepface-0.0.75-py3-none-any.whl (65 kB)
Collecting pandas>=0.23.4
Using cached pandas-1.5.3-cp39-cp39-macosx_11_0_arm64.whl (11.0 MB)
Collecting Pillow>=5.2.0
Using cached Pillow-9.4.0-cp39-cp39-macosx_11_0_arm64.whl (3.0 MB)
Collecting opencv-python>=<IP_ADDRESS>
Using cached opencv_python-<IP_ADDRESS>-cp37-abi3-macosx_11_0_arm64.whl (31.1 MB)
Collecting deepface
Using cached deepface-0.0.74-py3-none-any.whl (63 kB)
Using cached deepface-0.0.73-py3-none-any.whl (63 kB)
Using cached deepface-0.0.72-py3-none-any.whl (62 kB)
Using cached deepface-0.0.71-py3-none-any.whl (62 kB)
Using cached deepface-0.0.70-py3-none-any.whl (62 kB)
Using cached deepface-0.0.69-py3-none-any.whl (62 kB)
Using cached deepface-0.0.68-py3-none-any.whl (61 kB)
Using cached deepface-0.0.67-py3-none-any.whl (61 kB)
Using cached deepface-0.0.66-py3-none-any.whl (61 kB)
Using cached deepface-0.0.65-py3-none-any.whl (59 kB)
Using cached deepface-0.0.64-py3-none-any.whl (59 kB)
Using cached deepface-0.0.63-py3-none-any.whl (60 kB)
Using cached deepface-0.0.62-py3-none-any.whl (60 kB)
Using cached deepface-0.0.61-py3-none-any.whl (60 kB)
Using cached deepface-0.0.60-py3-none-any.whl (60 kB)
Using cached deepface-0.0.59-py3-none-any.whl (60 kB)
Using cached deepface-0.0.58-py3-none-any.whl (60 kB)
Using cached deepface-0.0.57-py3-none-any.whl (60 kB)
Using cached deepface-0.0.56-py3-none-any.whl (60 kB)
Using cached deepface-0.0.55-py3-none-any.whl (60 kB)
Using cached deepface-0.0.54-py3-none-any.whl (60 kB)
Using cached deepface-0.0.53-py3-none-any.whl (59 kB)
Using cached deepface-0.0.52-py3-none-any.whl (59 kB)
Using cached deepface-0.0.51-py3-none-any.whl (57 kB)
Using cached deepface-0.0.50-py3-none-any.whl (56 kB)
Using cached deepface-0.0.49-py3-none-any.whl (55 kB)
Using cached deepface-0.0.48-py3-none-any.whl (54 kB)
Using cached deepface-0.0.47-py3-none-any.whl (55 kB)
Using cached deepface-0.0.46-py3-none-any.whl (53 kB)
Using cached deepface-0.0.45-py3-none-any.whl (52 kB)
Using cached deepface-0.0.44-py3-none-any.whl (52 kB)
Using cached deepface-0.0.43-py3-none-any.whl (51 kB)
Using cached deepface-0.0.41-py3-none-any.whl (50 kB)
Using cached deepface-0.0.40-py3-none-any.whl (51 kB)
Using cached deepface-0.0.39-py3-none-any.whl (52 kB)
Using cached deepface-0.0.38-py3-none-any.whl (52 kB)
Using cached deepface-0.0.37-py3-none-any.whl (51 kB)
Using cached deepface-0.0.36-py3-none-any.whl (51 kB)
Using cached deepface-0.0.35-py3-none-any.whl (51 kB)
Using cached deepface-0.0.34-py3-none-any.whl (51 kB)
Using cached deepface-0.0.33-py3-none-any.whl (49 kB)
Using cached deepface-0.0.32-py3-none-any.whl (50 kB)
Using cached deepface-0.0.31-py3-none-any.whl (32 kB)
Using cached deepface-0.0.30-py3-none-any.whl (33 kB)
Using cached deepface-0.0.26-py3-none-any.whl (32 kB)
Using cached deepface-0.0.25-py3-none-any.whl (32 kB)
Using cached deepface-0.0.24-py3-none-any.whl (30 kB)
Using cached deepface-0.0.23-py3-none-any.whl (29 kB)
Using cached deepface-0.0.22-py3-none-any.whl (28 kB)
Using cached deepface-0.0.21-py3-none-any.whl (27 kB)
Using cached deepface-0.0.20-py3-none-any.whl (27 kB)
Using cached deepface-0.0.19-py3-none-any.whl (26 kB)
Using cached deepface-0.0.18-py3-none-any.whl (26 kB)
Using cached deepface-0.0.16-py3-none-any.whl (26 kB)
Using cached deepface-0.0.15-py3-none-any.whl (26 kB)
Using cached deepface-0.0.14-py3-none-any.whl (26 kB)
Using cached deepface-0.0.13-py3-none-any.whl (26 kB)
Using cached deepface-0.0.12-py3-none-any.whl (26 kB)
Using cached deepface-0.0.11-py3-none-any.whl (26 kB)
Using cached deepface-0.0.10-py3-none-any.whl (22 kB)
Using cached deepface-0.0.9-py3-none-any.whl (20 kB)
Using cached deepface-0.0.7-py3-none-any.whl (20 kB)
Using cached deepface-0.0.6-py3-none-any.whl (20 kB)
Using cached deepface-0.0.5-py3-none-any.whl (19 kB)
Using cached deepface-0.0.4-py3-none-any.whl (18 kB)
Using cached deepface-0.0.3-py3-none-any.whl (17 kB)
Using cached deepface-0.0.2-py3-none-any.whl (17 kB)
Using cached deepface-0.0.1-py3-none-any.whl (12 kB)
ERROR: Cannot install deepface==0.0.1, deepface==0.0.10, deepface==0.0.11, deepface==0.0.12, deepface==0.0.13, deepface==0.0.14, deepface==0.0.15, deepface==0.0.16, deepface==0.0.18, deepface==0.0.19, deepface==0.0.2, deepface==0.0.20, deepface==0.0.21, deepface==0.0.22, deepface==0.0.23, deepface==0.0.24, deepface==0.0.25, deepface==0.0.26, deepface==0.0.3, deepface==0.0.30, deepface==0.0.31, deepface==0.0.32, deepface==0.0.33, deepface==0.0.34, deepface==0.0.35, deepface==0.0.36, deepface==0.0.37, deepface==0.0.38, deepface==0.0.39, deepface==0.0.4, deepface==0.0.40, deepface==0.0.41, deepface==0.0.43, deepface==0.0.44, deepface==0.0.45, deepface==0.0.46, deepface==0.0.47, deepface==0.0.48, deepface==0.0.49, deepface==0.0.5, deepface==0.0.50, deepface==0.0.51, deepface==0.0.52, deepface==0.0.53, deepface==0.0.54, deepface==0.0.55, deepface==0.0.56, deepface==0.0.57, deepface==0.0.58, deepface==0.0.59, deepface==0.0.6, deepface==0.0.60, deepface==0.0.61, deepface==0.0.62, deepface==0.0.63, deepface==0.0.64, deepface==0.0.65, deepface==0.0.66, deepface==0.0.67, deepface==0.0.68, deepface==0.0.69, deepface==0.0.7, deepface==0.0.70, deepface==0.0.71, deepface==0.0.72, deepface==0.0.73, deepface==0.0.74, deepface==0.0.75 and deepface==0.0.9 because these package versions have conflicting dependencies.
The conflict is caused by:
deepface 0.0.75 depends on tensorflow>=1.9.0
deepface 0.0.74 depends on tensorflow>=1.9.0
deepface 0.0.73 depends on tensorflow>=1.9.0
deepface 0.0.72 depends on tensorflow>=1.9.0
deepface 0.0.71 depends on tensorflow>=1.9.0
deepface 0.0.70 depends on tensorflow>=1.9.0
deepface 0.0.69 depends on tensorflow>=1.9.0
deepface 0.0.68 depends on tensorflow>=1.9.0
deepface 0.0.67 depends on tensorflow>=1.9.0
deepface 0.0.66 depends on tensorflow>=1.9.0
deepface 0.0.65 depends on tensorflow>=1.9.0
deepface 0.0.64 depends on tensorflow>=1.9.0
deepface 0.0.63 depends on tensorflow>=1.9.0
deepface 0.0.62 depends on tensorflow>=1.9.0
deepface 0.0.61 depends on tensorflow>=1.9.0
deepface 0.0.60 depends on tensorflow>=1.9.0
deepface 0.0.59 depends on tensorflow>=1.9.0
deepface 0.0.58 depends on tensorflow>=1.9.0
deepface 0.0.57 depends on tensorflow>=1.9.0
deepface 0.0.56 depends on tensorflow>=1.9.0
deepface 0.0.55 depends on tensorflow>=1.9.0
deepface 0.0.54 depends on tensorflow>=1.9.0
deepface 0.0.53 depends on tensorflow>=1.9.0
deepface 0.0.52 depends on tensorflow>=1.9.0
deepface 0.0.51 depends on tensorflow>=1.9.0
deepface 0.0.50 depends on tensorflow>=1.9.0
deepface 0.0.49 depends on tensorflow>=1.9.0
deepface 0.0.48 depends on tensorflow>=1.9.0
deepface 0.0.47 depends on tensorflow>=1.9.0
deepface 0.0.46 depends on tensorflow>=1.9.0
deepface 0.0.45 depends on tensorflow>=1.9.0
deepface 0.0.44 depends on tensorflow>=1.9.0
deepface 0.0.43 depends on tensorflow>=1.9.0
deepface 0.0.41 depends on tensorflow>=1.9.0
deepface 0.0.40 depends on tensorflow>=1.9.0
deepface 0.0.39 depends on tensorflow>=1.9.0
deepface 0.0.38 depends on tensorflow>=1.9.0
deepface 0.0.37 depends on tensorflow>=1.9.0
deepface 0.0.36 depends on tensorflow>=1.9.0
deepface 0.0.35 depends on tensorflow>=1.9.0
deepface 0.0.34 depends on tensorflow>=1.9.0
deepface 0.0.33 depends on tensorflow>=1.9.0
deepface 0.0.32 depends on tensorflow>=1.9.0
deepface 0.0.31 depends on tensorflow>=1.9.0
deepface 0.0.30 depends on tensorflow>=1.9.0
deepface 0.0.26 depends on tensorflow>=1.9.0
deepface 0.0.25 depends on tensorflow>=1.9.0
deepface 0.0.24 depends on tensorflow>=1.9.0
deepface 0.0.23 depends on tensorflow>=1.9.0
deepface 0.0.22 depends on tensorflow>=1.9.0
deepface 0.0.21 depends on tensorflow>=1.9.0
deepface 0.0.20 depends on tensorflow>=1.9.0
deepface 0.0.19 depends on tensorflow>=1.9.0
deepface 0.0.18 depends on tensorflow>=1.9.0
deepface 0.0.16 depends on tensorflow>=1.9.0
deepface 0.0.15 depends on tensorflow>=1.9.0
deepface 0.0.14 depends on tensorflow>=1.9.0
deepface 0.0.13 depends on tensorflow>=1.9.0
deepface 0.0.12 depends on tensorflow>=1.9.0
deepface 0.0.11 depends on tensorflow>=1.9.0
deepface 0.0.10 depends on tensorflow>=1.9.0
deepface 0.0.9 depends on tensorflow>=1.9.0
deepface 0.0.7 depends on tensorflow>=1.9.0
deepface 0.0.6 depends on tensorflow>=1.9.0
deepface 0.0.5 depends on tensorflow>=1.9.0
deepface 0.0.4 depends on tensorflow>=1.9.0
deepface 0.0.3 depends on tensorflow>=1.9.0
deepface 0.0.2 depends on tensorflow>=1.9.0
deepface 0.0.1 depends on tensorflow>=1.9.0
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts
`

May I know what should I do with this? Any help is appreciated!

duplicated: https://github.com/serengil/deepface/issues/606


SPM: Couldn’t check out revision "fd172fe3cc07572e546942cb175b16e549fc3e1a"

Details

Xcode 13.4
Framework Version 1.4
Installed via SPM

Describe the Bug
Hi Ivan,
I have encountered a strange problem. When I add Package Dependencies in Xcode's Project Setting, the SPM seems to resolve the latest SPConfetti to an incorrect revision. I use the Xcode default settings when adding dependency.

However, the revision in the Package.resolved file points to fd172fe3cc07572e546942cb175b16e549fc3e1a, but this commit seems to be incorrect. There is also a warning on GitHub page for this revision: fd172fe3cc07572e546942cb175b16e549fc3e1a.
// Package.resolved
      {
        "package": "SPConfetti",
        "repositoryURL": "https://github.com/ivanvorobei/SPConfetti.git",
        "state": {
          "branch": null,
          "revision": "fd172fe3cc07572e546942cb175b16e549fc3e1a", // <=== 🤔
          "version": "1.4.0"
        }
      },

This issue can cause SPM to fail to checkout dependencies when building with CI. I can mannually edit Package.resolve to workaround the issue. But it will be great to fix it from the repo.

@ivanvorobei I believe there is no more problem in 1.4.1. 😉


Support dark/light mode based on browser's preferences

We should start talking about how to support this and make it nice at least for the most common use cases.
Reference:

#298

I'd also appreciate if themes could provide indicators to the JS client about this, since Furo maintains its own state for these details.

@pradyunsg would https://github.com/readthedocs/addons/issues/197 and #282 would be enough for Furo? I'd like to build something where theme authors can configure easily without depending on us implementing the styles to match their themes, if possible.

It would, yes! :)


Implementing chips with angular2-materialize

I'm trying to implement the examples of materialize-css chips found here, under the "Javascript Plugin Usage" heading, with angular2-materialze. I have followed the instructions for angular-cli installation found in the docs. I'm especially interested in the following implementation:
HTML

JavaScript/JQuery
$('.chips').material_chip();
$('.chips-placeholder').material_chip({
    placeholder: 'Enter a tag',
    secondaryPlaceholder: '+Tag',
  });

How do I convert that to Angular code? What does my template and component need to have for this to work?
I have tried changing the HTML to both of these,

but it didn't work and I get an error 'Couldn't find materialize function ''chips' on element or the global Materialize object.'

See example code here: https://github.com/InfomediaLtd/angular2-materialize/blob/master/sample/src/app/components/chips.ts
This is the demo: http://angular2-materialize.surge.sh/#/Chips
In your code, you should use material_chip instead of chip:


Parameter validation tests for CCM

Description
This PR introduces unit test code the validation of the public API function parameters against NULL pointers.
Status
READY
Requires Backporting
NO
Migrations
NO
Additional comments
None
Todos

[ ] Tests
[ ] Documentation
[ ] Changelog updated
[ ] Backported

This PR has been superseded by PR #2273, so can now be closed.


feat: Simplified local build for development

Description

Updated .gitignore to exclude unnecessary files
Implemented a script to install dependencies and build the project

Usage

Make the script executable

chmod +x dev_build.sh

Run the script

source ./dev_build.sh

Impact
Reduced manual steps required to build the project locally, hopefully this facilitate consistent development env across team members.

@OmarTawfik

I wonder if you have seen our development guide? https://nomicfoundation.github.io/slang/internals/development/#infra-cli

Hi Omar, thanks for the feedback, just started on this repo today and it's quite interesting the more I explore...
Regarding the link, I didn't see it, hence my initial suggestion.
I think current links in the readme file might need to be updated to point to the doc.
(The current Slang Internals link in the main branch readme is https://nomicfoundation.github.io/slang/internals)
And about the rest, yep that definitely makes. let stick with the current setup instead.

@oxf333 thanks for letting me know! I submitted a fix in #932

@0xf333 thanks for letting me know! I submitted a fix in #932


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/81971

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/83289

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request
This extra notification is being sent because I expected a tag to exist by now, but it doesn't.
You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/85911

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/86346

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/98047

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/99051

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/120339


build: Fix AMD module names generated by bazel

Downstream users expect to require('rxjs') and require('rxjs/operators')

part of fixing https://github.com/angular/angular/issues/23005

It looks like this is failing on something new from TypeScript? Obviously doesn't have to do anything with the PR.

@benlesh do I need to get a green build here to merge? Note, this is needed before we can cut Angular 6 rc.1
Maybe the TypeScript 2.8 release got picked up somehow, despite the package-lock.json?

I have put tsc version to latest to catch new release of ts breaks current compilation while we staying master on alpha / beta stage, so explains why pkglock doesn't work.
I think build issue need to be fixed but probably in separate PR cause this PR didn't cause failure.

thanks @kwonoj - could you merge this one pls? I need to get the fix downstream.

the CI is failing because of the unpinned typescript dependency that autoupgraded rxjs to typescript 2.8 which contains breaking changes.

Merge Me @benlesh


Bugfix/interactive shell none delim

Whoops! Thought this had made the bigger merge. Sorry about that.

Coverage remained the same at 42.384% when pulling d696a2fba2e8ca0d6ccf3c047d69a048ac93f4d5 on greateggsgreg:bugfix/interactive-shell-none-delim into 76315aa597065c6c343a818c22eb43552834c914 on google:master.

Coverage remained the same at 42.384% when pulling d696a2fba2e8ca0d6ccf3c047d69a048ac93f4d5 on greateggsgreg:bugfix/interactive-shell-none-delim into 76315aa597065c6c343a818c22eb43552834c914 on google:master.


Use freedom logging module

Use freedom logging module, add logging for all socket events

:+1:

If you're going to use this freedomjs logging stuff, consider the synchronous API - it could make that initLogger_ function less scary:
https://github.com/freedomjs/freedom/blob/74713e46a8ee65abbd41d679ccdf6c3ff9e0794c/demo/advancedlogging/main.js#L14


[Snyk] Upgrade pino from 8.15.0 to 8.15.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pino from 8.15.0 to 8.15.1.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2023-09-08.

Release notes

Package name: pino

8.15.1 - 2023-09-08What's Changed

fix: replace nullish coalescing operator by @ hchangjae in #1780
adding asString to the key by @ tzviki in #1779
feat(#1595): improve stream entry type by @ Puppo in #1778
build(deps): bump pino-abstract-transport from v1.0.0 to 1.1.0 by @ dependabot in #1797
Skip writing a big file test in CI and CITGM by @ mcollina in #1800

New Contributors

@ hchangjae made their first contribution in #1780
@ Puppo made their first contribution in #1778

Full Changelog: v8.15.0...v8.15.1

8.15.0 - 2023-08-04What's Changed

docs(transports): add axiom #1753  by @ qlaffont in #1754
Add pino-opentelemetry-transport as a known plugin to transports.md by @ Vunovati in #1757
fix: example code in transports.md by @ exKAZUu in #1761
Add default levels to opts in multistream by @ tzviki in #1760

New Contributors

@ qlaffont made their first contribution in #1754
@ Vunovati made their first contribution in #1757
@ exKAZUu made their first contribution in #1761
@ tzviki made their first contribution in #1760

Full Changelog: v8.14.2...v8.15.0

    from pino GitHub release notes

Commit messages

Package name: pino

619e049 Bumped v8.15.1
8514fb8 Skip writing a big file test in CI and CITGM (#1800)
aa53b40 build(deps): bump pino-abstract-transport from v1.0.0 to 1.1.0 (#1797)
91a3505 feat(#1595): improve stream entry types (#1778)
da75c01 adding asString to the key (#1779)
4c779a4 fix: replace nullish coalescing operator (#1780)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

oppdatert i siste release


More formula related stuff in filters

Particularly, formula in ToggleFilter and logged_in user in scope:

There is now an option to pick presets for the value. This was the case previously, but a bug broke that option some time ago. This is now fixed in #2707


I can't clean the input

Hi, my problem is when I try to clean the array selected, this is my example:
<ng-select
[data]="responsables"
[multiple]="true"
[items]="items"
(data)="refreshValue($event)"
(selected)="selected($event)"
(removed)="removed($event)"
placeholder="Select">

I tried to reset this.responsables=[]; but the select still have all the items. also a tried to use ngModel to do the same but I think ngModel is not supported.
Hope can help me!

The only way I could do it was accessing from ViewChild.
@ViewChild(SelectComponent)
select:SelectComponent;
// With this you can only access to the first select
@ViewChildren(SelectComponent)
selects : QueryList;
// And with this you can access to all of the selects are in the DOM. I put an id="someID" to identify my select that I want to work it.
Hope this can help to someone.


Android Apps do not wake up anymore

The StereoKitC modification https://github.com/StereoKit/StereoKit/pull/986 must be commented back to avoid crashing the app.
see also :
https://github.com/StereoKit/StereoKit/issues/991#issuecomment-2115247054

SkClosure has now it's own sleep management


Suggestion: Add yml configuration description in the rules explanations

What problem do you want to solve?
I'm trying to configure my YML file by adding some new rules and it is being hard to find the proper configuration due to the config examples being only in JSON format.
For example, in the sort-imports rule only the JSON configuration example is provided.
The same happens in the Playground when only the JSON config file can be downloaded.
What do you think is the correct solution?
It would be really helpful to have also the YML configuration file examples and to have the ability to download it directly in the playground.
Participation

[ ] I am willing to submit a pull request for this change.

Additional comments
No response

Thanks for the feedback. We are actually going to be removing support for YAML configuration files going forward, so we're not going to be adding any new documentation or features to the playground.
In the meantime, we have YAML examples in the configuring rules documentation.

Hi @nzakas thanks for your response. I didn't know Eslint was not going to stop supporting YAML. Is there a discussion/task or similar, whith this discontinuation information, timeline etc.?

Hi @nzakas thanks for your response. I didn't know Eslint was not going to stop supporting YAML. Is there a discussion/task or similar, whith this discontinuation information, timeline etc.?

Sorry for the delay in replying. You can track the implementation here https://github.com/eslint/eslint/issues/13481.


[BUG] directories.docs not added in upgrade script

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
? Do you want to run 'mcdev upgrade' now? Yes
22:52:22 info: ⚡ mcdev upgrade
22:52:25 error: Found problems in your ./.mcdevrc.json that you need to fix first:
 - directories.docs missing. Default value (string): docs/
22:52:25 info: Here is what you can do to fix these issues:
- Run 'mcdev upgrade' to fix missing or changed configuration options
? Do you want to run 'mcdev upgrade' now? (Y/n) Y
? Do you want to run 'mcdev upgrade' now? Yes
22:53:24 info: ⚡ mcdev upgrade
22:53:27 error: Found problems in your ./.mcdevrc.json that you need to fix first:
 - directories.docs missing. Default value (string): docs/
22:53:27 info: Here is what you can do to fix these issues:
- Run 'mcdev upgrade' to fix missing or changed configuration options
? Do you want to run 'mcdev upgrade' now? (Y/n)

Expected Behavior
When upgrading, directories.docs should be added by default, but this does not happen currently
Steps To Reproduce
start with v3.1.3 of mcdev and upgrade to v4
Version
3.1.3
Environment

OS:
Node:
npm:

Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

no longer reproducable. likely caused by discontinued branch


fix(curriculum): put a verb in singular by removing a letter

Checklist:

[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 main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

I didn't test this change as the fourth point says because I don't think it's necessary (very small change in a Markdown file).

Hello there,
Please edit this PR title to match our recommended title format: https://contribute.freecodecamp.org/#/how-to-open-a-pull-request

As a new contributor, we encourage you to read our contributing guidelines.
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
Some examples of this are:

Make sure you are not editing off of GitHub (while you can, it's not a good idea).
Makes sure you actually follow the PR checklist and not just tick things off; we won't take you seriously otherwise.
Use the correct way to link PRs in the description of the PR by updating the XXXXXX.
... and similar things.

We appreciate you taking the time to help us, and we hope to see more contributions from you.
Cheers & Happy Coding!

Hello, @ShaunSHamilton and @ieahleen. Foremost, I want to apologise for checking those two checks when I hadn't read the entire guidelines (I had only read the main page and this one) and hadn't written the title of the pull request correctly.
As stated in the FAQ, when it comes to fixing a typo, I can open a pull request right away; to explain more about my change, I basically removed a "s" from the verb as the substantive is in plural.
I read the main pages of the guidelines and the ones regarding a change like this, fixed the title of the pull request and tested the change using the link Gitpod generated, so I have checked all the checks in my original message.


Support for diff editor

Adds support for left and inline diff editors. They were not colorized or only semicolorized.

Thanks


Handle provision cancelling

This one fixes canceling logic in ProvisioningManager by canceling pending RPC by calling error on their response object, remembering that it's canceled, and swallowing "Input canceled" error on the call sites.
There is a new event cancelProvision that is dispatched from componentWillUnmount in code-page component which ensures that pending provisioning is properly canceled. This is safe to do even if we do not intend to cancel, e.g. provisioning succeeded or there was another error beforehand. cancelProvision calls ProvisioningManager.maybeCancelProvision which we consider OK to call if ProvisioningManager is already done().
There are some misc fixes around error modal, but the real fix will come in Y2K-655.
cc @keybase/react-hackers @keybase/y2ksquad

For easier testing:
diff --git a/go/engine/kex2_provisioner.go b/go/engine/kex2_provisioner.go
index 298b7a9aa8..be8384d9cd 100644
--- a/go/engine/kex2_provisioner.go
+++ b/go/engine/kex2_provisioner.go
@@ -111,7 +111,8 @@ func (e *Kex2Provisioner) Run(m libkb.MetaContext) error {
                DeviceID:      deviceID,
                Secret:        e.secret,
                SecretChannel: e.secretCh,
-               Timeout:       60 * time.Minute,
+               //Timeout:       60 * time.Minute,
+               Timeout: 10 * time.Second,
        }
        parg := kex2.ProvisionerArg{
                KexBaseArg:   karg,

diff --git a/go/engine/kex2_provisionee.go b/go/engine/kex2_provisionee.go
index 488063de3c..cd13dd78d6 100644
--- a/go/engine/kex2_provisionee.go
+++ b/go/engine/kex2_provisionee.go
@@ -134,7 +134,8 @@ func (e *Kex2Provisionee) Run(m libkb.MetaContext) error {
                DeviceID:      e.device.ID,
                Secret:        e.secret,
                SecretChannel: e.secretCh,
-               Timeout:       60 * time.Minute,
+               //Timeout:       60 * time.Minute,
+               Timeout: 6 * time.Second,
        }
        parg := kex2.ProvisioneeArg{
                KexBaseArg:  karg,

@buoyad done

or should I say: done()


Why images not found

When I used "gcr.io/spark-operator/spark-py:v3.1.1" as the base image in my customized docker image I faced an error "not found". Is the image address changed?

Found same issue.  Can you confirm if apache/spark:v3.1.3 is in fact the same as gcr.io/spark-operator/spark-py:v3.1.1 for backwards compatibility purposes?  If not, is there a way to build the old gcr.io/spark-operator/spark-py:v3.1.1  locally to ensure existing systems are not impacted?

@liyinan926, Thanks for your response, but when I used your mentioned image I faced an error about the Python problem(this image must used for Java), and when used this image "apache/spark-py:v3.1.3", this is not backward compatible.
@robwithhair


Sorting upgrades not working.

Describe the bug
Sorting Upgrades seams to not work at all.
To Reproduce
The steps needed to reproduce the behavior:

Turn Upgrade sorting to PP
Wait until you have Blue-PP upgrades, and see that they not sorted before the yellow.

Screenshots
If applicable, add screenshots to help explain your problem.

Save file
SundragonCookiesBakery.txt

I loaded your save but the setting seems to work on my end. However, it does show a different upgrade in the first slot.
I also have a different building showing on top (as the screenshot shows).

I'm not quite sure what causes the differences in calculation.. Does the console show any errors? Or do you have any other mods loaded?

Seams to work when I load it in chrome, but when loading it in Firefox i get the same order as in the screenshot.

I can reproduce in firefox.
What a weird bug. The sorting is similar to the one used to sort the buildings, which seems to work fine on firefox. I did a quick check for any weird non-supported elements or css properties but did not find any on first glance.
I will have another look soon, but at the moment don't immediately know what is causing this..

@DanielNoord Not sure exactly why this would cause the issue, but I noticed that the upgrade color is not actually being stored on the upgrade objects before sorting. The payback period is stored, but not the color.
Perhaps the color needs to be stored on line ~74 of src/Disp/BuildingsUpgrades/Upgrades.js.

Good catch! I will try to see if this fixes it immediately (probably)!
Let you know in a couple of minutes!

Fixed!
I expect to push the new version (with this fix) soon(ish). Hopefully by the end of this weekend!

Indeed, all I can think is that the code was previously doing the sorting based solely on this part of the comparison (line 85):
: a.pp < b.pp
And for some reason, Firefox (only) is not reaching that part of the comparison any longer. In any case, thanks for the fix.

That was probably the case.
I noticed that there was also a problem with the ColourOrdering array, as it did not actually have the correct ordering but chrome did order like it did. I changed it as well. This also points to chrome and safari just ordering based on pp and firefox (silently) throwing an error.


Unable to reconnect paired devices with controller privacy disabled (host privacy enabled)

Description
With host privacy enabled and controller privacy disabled, it is not possible to re-connect to a paired device.
To Reproduce
Preconditions:
CONFIG_BT_PRIVACY=y
CONFIG_BT_CTLR_PRIVACY=n
Peripheral advertises constantly. Central scans, connects, disconnects and then scans and finally attempts to re-connect. At second attempt:

Scanner scans for ADV packets, sees our peripheral by random address and sends scan report
In the host layer, the advertiser address is looked up and a key is found
The random address is translated to public address and app is notified
The app takes the public address of the advertiser and initiates a connection
The scanner receives connection information containing the public address
Scanner waits forever for a match between received random address and the public address from app

Expected behavior
Central and peripheral should connect every time.
Impact
Unable to connect after devices have paired.
Environment (please complete the following information)

Zephyr 2.0 RC1

@joerchan This seems like a regression. But please remove the label if it is not.

Yes, regression from here: 45da629b24f720019355fca8e1ddddb798ac409f


YouTube: Change url to avoid cookies from YouTube.

Note: Please transform - [ ] into - (NA) in the description when things are not applicable
Related issues
NA
Description
Change our youtube url since we don't want cookies from youtube.
Motivation & Context
Have a right cookie policy
Types of change

New feature (non-breaking change which adds functionality)

Live previews

https://deploy-preview-2089--boosted.netlify.app/docs/about/cookies
https://deploy-preview-2089--boosted.netlify.app/docs/helpers/ratio

Checklist

Contribution

[x] I have read the contributing guidelines

Accessibility

[x] My change follows accessibility good practices; I have at least run axe

Design

[x] My change respects the design guidelines defined in Orange Design System
[x] My change is compatible with responsive display

Development

[x] My change follows the developer guide
(NA) I have added JavaScript unit tests to cover my changes
(NA) I have added SCSS unit tests to cover my changes

Documentation

(NA) My change introduces changes to the documentation and/or I have updated the documentation accordingly

Checklist (for Core Team only)

(NA) My change introduces changes to the migration guide
(NA) My new component is added in Storybook
(NA) My new component is compatible with RTL
[ ] Manually run BrowserStack tests
[ ] Manually test browser compatibility with BrowserStack (Chrome >= 60, Firefox >= 60 (+ ESR), Edge, Safari >= 12, iOS Safari, Chrome & Firefox on Android)
[ ] Code review
[ ] Design review
[ ] A11y review

After the merge

[ ] Manually launch Percy tests

As discussed together, it seems that the issue comes from the cookie settings of the browser (if I accept them all I don't have the issue anymore). This looks like a netlify issue.

As discussed together, it seems that the issue comes from the cookie settings of the browser (if I accept them all I don't have the issue anymore). This looks like a netlify issue.

I would add that we found this problem using Chrome in private mode. It seems to works fine with other browsers, even in private navigation.


Switch to using private hosted pool for Project Reunion Foundation (#…

Cherrpick from
https://github.com/microsoft/WindowsAppSDK/pull/1031/files

/azp run


Update cli.py

refactor with chain assignment to make code more Pythonic, concise and efficient.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @anonymousdouble,
Thanks for the contribution!
This doesn't fit the required formatting, so, can you run this following command to reformat the code in the local directory:
python3 -m black .
If you need help, I can do it for you!

Can you start a PR on develop rather than master?

Better to actually create a fresh branch from develop and add the changes from this PR into it, as this patch was branched off from master, so it's not possible to merge it into develop


SSL train on large Speaker datasets

What does this PR do?

Fixes #<issue_number>

Before submitting

[ ] Did you read the contributor guideline?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Does your code adhere to project-specific code style and conventions?

PR review

Reviewer checklist

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[ ] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[ ] Confirm that the changes adhere to compatibility requirements (e.g., Python version, platform)
[ ] Review the self-review checklist to ensure the code is ready for review

@TParcollet

Do not look at this PR yet. We are working on it -- this will be our best SPK embedding model.


spec: fix make rpm on CentOS 8

make rpm is failing on CentOS 8, solution:

python36-* packages are called python3-* in CentOS 8 - update in requirements.
Fix h_motr_version for motr requirement: it is taking the VERSION and RELEASE values from Hare instead of Motr. Fix by adding one more escape % symbol before VERSION and RELEASE.

@andriytk, the problem is not very clear, can you please elaborate the same in the commit message and the PR description?

@mssawant, is it better now?

retest this please


docs: simplify the Quickstart guide

For a true quickstart, let's direct people towards docker-compose
where they can get a multi-container instance setup with 2 shell
commands.
The current docker setup is limited and forces the user to run
an extra set of commands to load examples, create a user, ...
and they end up in a slower single-container instance.
On docker compose, we have all this setup as well as the pointer
to the latest release by default.
It also looks like the current setup is also sqlite(?) and isn't persisted (?)
Having a Postgres and some persistence in the image should be
a positive upgrade here too.

@artofcomputing @michael-s-molina @eschutho @sfirke for more opinions. I wonder if there's a place for both methods.

My take is I think we need to simplify things, use and expose higher level constructs. If people want to go lower level they can refer to the underlying scripts where all the information resides.
Also related is I would love to strip "external" information that is not Superset-specific and is better maintained elsewhere. You need to install docker on a Mac? on Ubuntu? Look at the docker docs!

I agree in the sense of simplification, which was one of the main reasons that the Quickstart was created, as users weren't able to get a instance of Superset up and running easily beforehand.
It's possible to have both installation methods in place, and let the user choose which one fits best their needs while informing the tradeoff of each.

It also looks like the current setup is also sqlite(?) and isn't persisted (?)
Having a Postgres and some persistence in the image should be
a positive upgrade here too.

That's right, currently the standalone instance uses sqlite, yet the data is persisted by stopping the container instead of removing it, as the documentation informs.

Whenever we offer more options it dilutes what is truly supported and creates confusion. "Just tell me what I should use" is the way I'd feel entering a new community. There's shouldn't be many options for a quick start.
We could factor out this method as yet another way to run Superset into the "installation and configuration" under "shaky single host docker setup with SQL lite"

Oh one more thing about the current quickstart is that AFAIK it cannot be configured easily, meaning it's a configurability dead end. If someone wanted to install a database driver to connect to their database or simply flipping a feature flag, they'd probably have to go inside the docker and mess around with things. On the docker-compose side of the house things are evolutive and well documented around configurability. There are clear prescribed ways to do these things.

Whenever we offer more options it dilutes what is truly supported and creates confusion

I can't find in the documentation what is the official installation methods, would you mind telling me where it is?
If not, "truly supported" means nothing if the user can't find it.

We could factor out this method as yet another way to run Superset into the "installation and configuration" under "shaky single host docker setup with SQL lite"

Again, simply declare the official supported installation methods and we can go from there. Only Kubernetes is supported? Let's do a Quickstart with Kubernetes. Both Kubernetes and Compose? Let's offer both.

Oh one more thing about the current quickstart is that AFAIK it cannot be configured easily, meaning it's a configurability dead end.

I agree, that was a big oversight when it was written, since Superset configuration is catered towards a declarative method. Yet, there's no mention about Superset being declarative at the start, it should be actually documented in the intro.

Oh for quickstart what I'm suggesting is in this PR (docker-compose pointing to the latest official release)
For installation there's a whole section, starting now with k8s, but getting on all sorts of nooks and crannies... ->
https://superset.apache.org/docs/installation/running-on-kubernetes

For development setups -> https://github.com/apache/superset/blob/master/CONTRIBUTING.md
What's clear is that this documentation evolved bits by bits through different generations of contributors. This quickstart re-write is a first take towards re-thinking / merging / sorting through all this.
I think it's becoming clear to me that for quickstart/sandbox/development docker-compose is the preferred way and for production Helm/k8s is the way, supported by minikube for smaller, single-host-type setups.

Oh for quickstart what I'm suggesting is in this PR (docker-compose pointing to the latest official release)
For installation there's a whole section, starting now with k8s, but getting on all sorts of nooks and crannies... ->
https://superset.apache.org/docs/installation/running-on-kubernetes
...
For development setups -> https://github.com/apache/superset/blob/master/CONTRIBUTING.md

That wasn't the question, which are the official and supported installation methods and where in the documentation they are declared? Yes, there's multiple installation pages, however Docker Compose is now declared as a method not suitable for production deployment on top of the page, would that be suitable for having a Quickstart with it? And what about PyPI? If so, there needs to be a page where users can be informed which are the methods the Superset community supports.
Again, without it, "truly supported" means nothing.

What's clear is that this documentation evolved bits by bits through different generations of contributors. This quickstart >re-write is a first take towards re-thinking / merging / sorting through all this.

That's true, IMHO Superset has advanced quite a lot throughout the years, however the documentation hasn't so far been able to keep up with the development pace, making it the least favorable selling point of Superset. There's a lot of work to be done.

I think it's becoming clear to me that for quickstart/sandbox/development docker-compose is the preferred way and for >production Helm/k8s is the way, supported by minikube for smaller, single-host-type setups.

I agree, the documentation can be definitely geared towards these methods, but they must be agreed upon by the community, and also stated on the documentation so as not to generate any confusion to the users. That was also another oversight when the Quickstart was written (which is fixed in this PR).

which are the official and supported installation methods
This is beyond the scope of this PR. This PR is about improving quick start. Can we agree that this approach is better than the previous single-docker/sqlite/5-steps approach? I'm planning on improving the rest of the docs to clarify installation, but let's start here.

Can we agree that this approach is better than the previous single-docker/sqlite/5-steps approach? I'm planning on > improving the rest of the docs to clarify installation, but let's start here.
One big assumption here is that "quick start" is about sandboxing (as in standing up something quickly that someone can play with, in a non-production environment). This fits the scope and direction I'm advocating for our usage of docker-compose...

IMHO your direction and view is much more tangible and easier to grasp now, which I fully agree. It's also possible to use this direction to rewrite other pages by having the quick start as an example/baseline to simplify instructions.

About the question that's beyond the scope of this PR of "what we support"...

I agree, there's no silver bullet. However, I think that the direction you're advocating for the quick start can be a good starting ground to provide better instructions on how to change between different solutions,


Player does not work with jest

Overview
When importing import { DotLottieReact } from "@lottiefiles/dotlottie-react";
To use the player jest will error with this:
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/juzorensen/WebstormProjects/forbole-website/node_modules/@lottiefiles/dotlottie-react/dist/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import React, { useState, useRef, useCallback, useMemo, useEffect, useLayoutEffect } from 'react';
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

Consuming repo
dotlottie-web
Labels

[ ] Add the Type: Bug label to this issue.

Hi @0x7u, we don't ship CJS for dotLottie-react, only ESM. You might want to check out how to mock the dotLottie-react module in Jest: https://jestjs.io/docs/ecmascript-modules#module-mocking-in-esm. By the way, which version of Jest are you using?

Hey @theashraf, thanks for the reply.
I am Jest version 29.7.0.
I've just tried the workaround you suggested it did not work for me, maybe I am not doing something right.
I also lazy-loaded the component with nextjs dynamic helper (to disable SSR), and I met with even more nonsense 😅.
    Warning: An update to ForwardRef(LoadableComponent) inside a test was not wrapped in act(...).

    When testing, code that causes React state updates should be wrapped into act(...):

    act(() => {
      /* fire events that update state */
    });
    /* assert on the output */

@0x7u
I see. I'll investigate further and let you know.


No Available nodes

I keep getting a no available nodes error while playing music on different servers. my bot is in almost 3k servers and the music works in some servers and doesnt in most of them. i keep getting a no available nodes error. is there some sort of limitations?? i checked the other issue posted here and it has nothing to do with the issue im facing.

is it something like if its been used in 1 server, you cant use it another one??? do i need to spawn lavalink jar for each server i have? wtf?


Telegram BOT init

-- in future if anyone want to be inspire your REPO! as IMD have tons of data and no-one interested so thanks for creating this project
Special Thanks!
@rtdtwo

Hi @prateekmaru
Great job making a Telegram Bot!
Unfortunately, I cannot merge this pull request to maintain separation of context. I envision this repo to be strictly for the API.
I highly encourage you to move this to a new repo of your own, and really thanks for the shoutout! I appreciate your words.
Cheers!


Update documentation

Link to Xilinx hyperledger fabric is incorrect. Change to this repo.
Add description about the results to be expected.
Add description about the prerequisites installation, so users can either chose to run the provided script or do it manually themselves.

Done for Fabric v1.4.


FSL FUGUE - Image Exception : #3 :: Attempted to divide images/ROIs of different sizes

Traceback (most recent call last):
  File "/usr/local/miniconda/bin/fmriprep", line 11, in <module>
    load_entry_point('fmriprep==1.0.8', 'console_scripts', 'fmriprep')()
  File "/usr/local/miniconda/lib/python3.6/site-packages/fmriprep/cli/run.py", line 267, in main
    fmriprep_wf.run(**plugin_settings)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/workflows.py", line 602, in run
    runner.run(execgraph, updatehash=updatehash, config=self.config)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/base.py", line 168, in run
    self._clean_queue(jobid, graph, result=result))
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/base.py", line 227, in _clean_queue
    raise RuntimeError("".join(result['traceback']))
RuntimeError: Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/plugins/multiproc.py", line 68, in run_node
    result['result'] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 487, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 571, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/pipeline/engine/nodes.py", line 650, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 516, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 1023, in _run_interface
    self.raise_exception(runtime)
  File "/usr/local/miniconda/lib/python3.6/site-packages/niworkflows/nipype/interfaces/base/core.py", line 960, in raise_exception
    ).format(**runtime.dictcopy()))
RuntimeError: Command:
fugue --despike --despikethreshold=2.1 --loadfmap=/root/src/fmriprep/work/fmriprep_wf/single_subject_ACTIGLIA011BL_wf/func_preproc_task_rest_wf/phdiff_wf/demean/sub-ACTIGLIA011BL_acq-rest_phasediff_rads_unwrapped_filt_demean.nii.gz --savefmap=sub-ACTIGLIA011BL_acq-rest_phasediff_rads_unwrapped_filt_demean_fieldmap.nii.gz --mask=/root/src/fmriprep/work/fmriprep_wf/single_subject_ACTIGLIA011BL_wf/func_preproc_task_rest_wf/phdiff_wf/bet/sub-ACTIGLIA011BL_acq-rest_magnitude1_ras_corrected_brain_mask.nii.gz
Standard output:

Standard error:
Image Exception : poldracklab/fmriprep#3 :: Attempted to divide images/ROIs of different sizes
terminate called after throwing an instance of 'RBD_COMMON::BaseException'
Aborted (core dumped)
Return code: 134

I found this thread while searching for a similar error from some of our subjects. I would understand if this is a field map issue because we have some other problems from with Philips fieldmaps. The question is, how do we know what is the source of the problem, and what could be a solution?
Here is the crash log:
Node: fmriprep_wf.single_subject_S12345678_wf.func_preproc_ses_07_task_restingstate_run_01_wf.sdc_estimate_wf.phdiff_wf.fmap_postproc_wf.cleanup_wf.Despike
Working directory: /DATA/dorian/fmriprepdata/STUDY/data/processed/fmriprep-1.5.5/work_sub-S12345678/fmriprep_wf/single_subject_S12345678_wf/func_preproc_ses_07_task_restingstate_run_01_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/cleanup_wf/Despike

Node inputs:

args = <undefined>
asym_se_time = <undefined>
despike_2dfilter = True
despike_threshold = 2.1
dwell_time = <undefined>
dwell_to_asym_ratio = <undefined>
environ = {'FSLOUTPUTTYPE': 'NIFTI_GZ'}
fmap_in_file = <undefined>
fmap_out_file = <undefined>
forward_warping = False
fourier_order = <undefined>
icorr = <undefined>
icorr_only = <undefined>
in_file = <undefined>
mask_file = <undefined>
median_2dfilter = <undefined>
no_extend = <undefined>
no_gap_fill = <undefined>
nokspace = <undefined>
output_type = NIFTI_GZ
pava = <undefined>
phase_conjugate = <undefined>
phasemap_in_file = <undefined>
poly_order = <undefined>
save_fmap = True
save_shift = <undefined>
save_unmasked_fmap = <undefined>
save_unmasked_shift = <undefined>
shift_in_file = <undefined>
shift_out_file = <undefined>
smooth2d = <undefined>
smooth3d = <undefined>
unwarp_direction = <undefined>
unwarped_file = <undefined>
warped_file = <undefined>

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
    result["result"] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 516, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 635, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 741, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 397, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 792, in _run_interface
    self.raise_exception(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 723, in raise_exception
    ).format(**runtime.dictcopy())
RuntimeError: Command:
fugue --despike --despikethreshold=2.1 --loadfmap=/DATA/dorian/fmriprepdata/STUDY/data/processed/fmriprep-1.5.5/work_sub-S12345678/fmriprep_wf/single_subject_S12345678_wf/func_preproc_ses_07_task_restingstate_run_01_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/demean/sub-S12345678_ses-07_run-03_phasediff_rads_unwrapped_recentered_filt_demean.nii.gz --savefmap=sub-S12345678_ses-07_run-03_phasediff_rads_unwrapped_recentered_filt_demean_fieldmap.nii.gz --mask=/DATA/dorian/fmriprepdata/STUDY/data/processed/fmriprep-1.5.5/work_sub-S12345678/fmriprep_wf/single_subject_S12345678_wf/func_preproc_ses_07_task_restingstate_run_01_wf/sdc_estimate_wf/phdiff_wf/magnitude_wf/bet/sub-S12345678_ses-07_run-03_magnitude1_avg_corrected_brain_mask.nii.gz
Standard output:

Standard error:
Image Exception : #3 :: Attempted to divide images/ROIs of different sizes
terminate called after throwing an instance of 'RBD_COMMON::BaseException'
Aborted (core dumped)
Return code: 134

Hi @dorianps, could you confirm whether the dimensions of the magnitude file match those of the phase difference?

The dimensions are the same.

I looked at the files further. Even though the original magnitude and phase difference files match, the two input files to the fugue command that threw the error have "different" sizes. I put that in quotes because the difference is in orientation, they do have the same size in the anatomical axis. See below c3d output:
func_preproc_ses_07_task_restingstate_run_01_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/demean/sub-R41851958X_ses-07_run-03_phasediff_rads_unwrapped_recentered_filt_demean.nii.gz -info
Image #1: dim = [64, 64, 48];  bb = {[77.644 -116.206 -94.8365], [289.644 95.7936 63.7555]};  vox = [3.3125, 3.3125, 3.304];  range = [-4.02648, 5.25277];  orient = AIL
and
func_preproc_ses_07_task_restingstate_run_01_wf/sdc_estimate_wf/phdiff_wf/magnitude_wf/bet/sub-R41851958X_ses-07_run-03_magnitude1_avg_corrected_brain_mask.nii.gz -info
Image #1: dim = [48, 64, 64];  bb = {[77.644 92.4811 -94.8365], [236.236 304.481 117.164]};  vox = [3.304, 3.3125, 3.3125];  range = [0, 1];  orient = LPI

@oesteban We are still stuck with this problem. Any suggestion of how to figure out what might be the problem? Note, this happens with fmriprep 1.5.X, we have processed the rest of the data with that version and are hoping not to need 20.0.X just for 3 subjects.
Thank you for helping out.

To be clear, the original fieldmaps have a common orientation, but they've been changed by the time they get to demean/bet? Or we're failing to normalize to correct orientations?

The original fieldmap mag/phassediff files have identical orientations/sizes. These are the c3d outputs for those files:
c3d sub-R12345/ses-07/fmap/sub-R12345_ses-07_run-03_phasediff.nii.gz -info
Image #1: dim = [64, 64, 48];  bb = {[77.644 -116.206 -94.8365], [289.644 95.7936 63.7555]};  vox = [3.3125, 3.3125, 3.304];  range = [-4096, 4092];  orient = AIL
c3d sub-R12345/ses-07/fmap/sub-R12345_ses-07_run-03_magnitude1.nii.gz -info
Image #1: dim = [64, 64, 48];  bb = {[77.644 -116.206 -94.8365], [289.644 95.7936 63.7555]};  vox = [3.3125, 3.3125, 3.304];  range = [1, 2219];  orient = AIL
c3d sub-R12345/ses-07/fmap/sub-R12345_ses-07_run-03_magnitude2.nii.gz -info
Image #1: dim = [64, 64, 48];  bb = {[77.644 -116.206 -94.8365], [289.644 95.7936 63.7555]};  vox = [3.3125, 3.3125, 3.304];  range = [1, 1888];  orient = AIL
The two input files have different orientation as I said in the previous post. brainmask is LPI, which is also the orientation of the T1:
c3d sub-R12345/ses-07/anat/sub-R12345_ses-07_run-01_T1w.nii.gz -info
Image #1: dim = [208, 256, 256];  bb = {[113.727 99.4097 -134.682], [342.527 381.41 147.318]};  vox = [1.1, 1.10156, 1.10156];  range = [0, 1324];  orient = LPI
I don't know how the brainmask is being generated -- whether using the magnitude fieldmap or the T1, but thought the T1 being LPI might be related.

Hmm. That could be the source. It would be good to validate/normalize input orientations at the entrance to the workflow, to avoid potential mismatches. It looks like FUGUE is orientation-agnostic (otherwise it would be normalizing internally), so it probably makes sense to normalize to RAS or perhaps the BOLD orientation.
I won't have time to look into this more deeply until next week at the earliest, in case anybody else does.

Thanks @effigies  for looking into this when you can.

@effigies just pinging this thread one more time, hoping we can find a fix. With most people working from home, things may not flaw as before, but I am hoping on my end to close this work once the last 3 subjects are processed with fmriprep.
Thanks again.
Dorian

Thanks for the ping. I haven't had a chance to look into this, but it is still on my list. I'm down to half time due to childcare responsibilities.

@dorianps Is there any chance that you have a pair of subjects (one passing, one failing) that you could share to help reproduce the issue?

Sorry @effigies , for some strange reason I am not receiving emails from this thread.
Our data are strictly guarded with legal agreements, we can't share them without a DUA. Is there something else we can try (headers, check of temp data, etc.). I think @ins0mniac2  checked a few things on the temporary data without success.

Checking on the status of this issue. Best I can tell, I'm getting the same error:

Node: fmriprep_wf.single_subject_C01_wf.func_preproc_ses_01_task_rest_wf.sdc_estimate_wf.phdiff_wf.fmap_postproc_wf.cleanup_wf.Despike
Working directory: /tmp/work/fmriprep_wf/single_subject_C01_wf/func_preproc_ses_01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/cleanup_wf/Despike

Node inputs:
args = <undefined>
asym_se_time = <undefined>
despike_2dfilter = True
despike_threshold = 2.1
dwell_time = <undefined>
dwell_to_asym_ratio = <undefined>
environ = {'FSLOUTPUTTYPE': 'NIFTI_GZ'}
fmap_in_file = <undefined>
fmap_out_file = <undefined>
forward_warping = False
fourier_order = <undefined>
icorr = <undefined>
icorr_only = <undefined>
in_file = <undefined>
mask_file = <undefined>
median_2dfilter = <undefined>
no_extend = <undefined>
no_gap_fill = <undefined>
nokspace = <undefined>
output_type = NIFTI_GZ
pava = <undefined>
phase_conjugate = <undefined>
phasemap_in_file = <undefined>
poly_order = <undefined>
save_fmap = True
save_shift = <undefined>
save_unmasked_fmap = <undefined>
save_unmasked_shift = <undefined>
shift_in_file = <undefined>
shift_out_file = <undefined>
smooth2d = <undefined>
smooth3d = <undefined>
unwarp_direction = <undefined>
unwarped_file = <undefined>
warped_file = <undefined>

Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
    result["result"] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 516, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 635, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 741, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 397, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 792, in _run_interface
    self.raise_exception(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 723, in raise_exception
    ).format(**runtime.dictcopy())
RuntimeError: Command:
fugue --despike --despikethreshold=2.1 --loadfmap=/tmp/work/fmriprep_wf/single_subject_C01_wf/func_preproc_ses_01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/demean/sub-C01_ses-01_phasediff_rads_unwrapped_recentered_filt_demean.nii.gz --savefmap=sub-C01_ses-01_phasediff_rads_unwrapped_recentered_filt_demean_fieldmap.nii.gz --mask=/tmp/work/fmriprep_wf/single_subject_C01_wf/func_preproc_ses_01_task_rest_wf/sdc_estimate_wf/phdiff_wf/magnitude_wf/bet/sub-C01_ses-01_magnitude1_avg_corrected_brain_mask.nii.gz
Standard output:

Standard error:
Image Exception : #3 :: Attempted to divide images/ROIs of different sizes
terminate called after throwing an instance of 'RBD_COMMON::BaseException'
Aborted
Return code: 134

Thanks for bumping this. The big holdup is finding a suitable test dataset (and finding the time).
The Midnight Scan Club dataset has phasediffs, so I'm going to make a pared down version of one of their subjects with data rotated into your orientations. You have LPI for T1w and AIL for your fieldmaps. In case it's relevant, what about your BOLD series?

Thanks @effigies . So you were able to reproduce the error on your test data ?

Yup:
200415-18:07:12,751 nipype.workflow INFO:
	 [Node] Setting-up "fmriprep_wf.single_subject_MSC01_wf.func_preproc_ses_func01_task_rest_wf.sdc_estimate_wf.phdiff_wf.fmap_postproc_wf.cleanup_wf.Despike" in "/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/cleanup_wf/Despike".
200415-18:07:12,755 nipype.workflow INFO:
	 [Node] Running "Despike" ("nipype.interfaces.fsl.preprocess.FUGUE"), a CommandLine Interface with command:
fugue --despike --despikethreshold=2.1 --loadfmap=/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/demean/sub-MSC01_ses-func01_phasediff_rads_unwrapped_recentered_filt_demean.nii.gz --savefmap=sub-MSC01_ses-func01_phasediff_rads_unwrapped_recentered_filt_demean_fieldmap.nii.gz --mask=/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/magnitude_wf/bet/sub-MSC01_ses-func01_magnitude1_avg_corrected_brain_mask.nii.gz
200415-18:07:13,95 nipype.workflow WARNING:
	 Storing result file without outputs
200415-18:07:13,96 nipype.workflow WARNING:
	 [Node] Error on "fmriprep_wf.single_subject_MSC01_wf.func_preproc_ses_func01_task_rest_wf.sdc_estimate_wf.phdiff_wf.fmap_postproc_wf.cleanup_wf.Despike" (/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/cleanup_wf/Despike)
200415-18:07:13,932 nipype.workflow ERROR:
	 Node Despike failed to run on host 9edc547b3d73.
200415-18:07:13,936 nipype.workflow ERROR:
	 Saving crash info to /out/fmriprep/sub-MSC01/log/20200415-180636_874ae2f4-d1b2-47c9-84e2-b08c96721001/crash-20200415-180713-root-Despike-9bf45840-5736-4c2b-adbd-10227276b23b.txt
Traceback (most recent call last):
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/plugins/multiproc.py", line 67, in run_node
    result["result"] = node.run(updatehash=updatehash)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 516, in run
    result = self._run_interface(execute=True)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 635, in _run_interface
    return self._run_command(execute)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/pipeline/engine/nodes.py", line 741, in _run_command
    result = self._interface.run(cwd=outdir)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 397, in run
    runtime = self._run_interface(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 792, in _run_interface
    self.raise_exception(runtime)
  File "/usr/local/miniconda/lib/python3.7/site-packages/nipype/interfaces/base/core.py", line 723, in raise_exception
    ).format(**runtime.dictcopy())
RuntimeError: Command:
fugue --despike --despikethreshold=2.1 --loadfmap=/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/fmap_postproc_wf/demean/sub-MSC01_ses-func01_phasediff_rads_unwrapped_recentered_filt_demean.nii.gz --savefmap=sub-MSC01_ses-func01_phasediff_rads_unwrapped_recentered_filt_demean_fieldmap.nii.gz --mask=/scratch/fmriprep_wf/single_subject_MSC01_wf/func_preproc_ses_func01_task_rest_wf/sdc_estimate_wf/phdiff_wf/magnitude_wf/bet/sub-MSC01_ses-func01_magnitude1_avg_corrected_brain_mask.nii.gz
Standard output:

Standard error:
Image Exception : #3 :: Attempted to divide images/ROIs of different sizes
terminate called after throwing an instance of 'RBD_COMMON::BaseException'
Aborted (core dumped)
Return code: 134

One difference is that the brainmask appears to be in RAS, rather than LPI, so I'm not sure what's different there. Hopefully we can come up with a solution that will make it robust to any such quirks.

@oesteban @mattcieslak I'm not finding it documented. Does anything downstream of the fieldmap tools care about orientation? Would it be reasonable to reorient everything coming in to RAS?

I was only able to get the fsl pipeline working if everything was in the standard FSL orientation (LAS+).

@mattcieslak In the sense that you had to manually reorient the images before runnig the pipeline, or the pipeline had to be written to reorient its inputs?
In either case, I would be wary of that, as we have been reorienting the magnitude images to RAS+ but not the phasediff. As RAS+ and LAS+ will have the same dimensions and voxel sizes, we would not see the error in this issue, but I think you'll be masking an LAS image with an RAS brain mask and getting bad results, because of the magmrg setting I'm fixing in #98.

Ah, I was thinking of the topup pipeline in qsiprep. The phasediff shouldn't need this reorientation

Okay. We should make sure, though, that if the TOPUP pipeline is potentially permuting or flipping axes of input images, that PhaseEncodingDirection gets adjusted in the same way. Should be pretty easy to build a test for if we have known good LAS+ images.

@tragus1 @dorianps This should be resolved in fMRIPrep 1.5.10 and 20.0.6. Please let us know if it fails.
Thanks very much for your patience, and also your persistence in prodding us to resolve this issue. It was quite a subtle bug that all previous versions of fMRIPrep were subject to. I would highly recommend re-running your earlier subjects, though you can safely reuse the working directories.

Appreciate your effort @effigies . Thanks much!

@effigies Thank you for fixing this. I will see to rerun the 3 subjects that had this issue.
P.s. I am assuming this is the only thing changing 1.5.9 -> 1.5.10, so it is safe to drop my old singularity container and keep only the last one together with the processed data.

Yes. This is the only change: https://github.com/poldracklab/fmriprep/compare/1.5.9...1.5.10

Just checking on this - I noticed in the release notes for fmriprep 20.0.6 it says that there is a critical bug in earlier versions for phasediff fieldmaps. Is this the issue that is referenced?
And the release note also says that there may be subtle errors in SDC for earlier versions. Has this been confirmed or is it only a possibility? We aren't sure if we should re-run all our phasediff data

@mattcieslak Yes.

Just to confirm: if the fieldmap data is in LAS+ orientation, an RAS+ mask gets applied without being flipped, causing the displacements to be potentially misshapen?

Yes. If the fieldmap is in any orientation, an RAS+ mask gets applied without being reoriented. In LAS+ it's likely to be somewhat subtle.

Ah, that's a tricky one. Was there an announcement to fMRIPrep users about this? I imagine a lot of users will want to re-run their phasediff studies. Thanks for the quick replies!

It was in the release notes and there is a mechanism in fmriprep that will warn users of older versions, but we don't have a mailing list where we make these outlines.


Externalize Components/Tooling/Templates storage

Right now the process of adding a component/tooling/template is a bit of a hassle:

Creator need to fork the project
Creator need add the data in one of 3 JSON files
Creator have to ensure that all (mandatory) fields are filled
Creator have to ensure that fields are correctly set (typos, no unnecessary new tags, categories, etc.)
Creator have to open a PR
Maintainer+Community have to validate that all (mandatory) fields are filled
Maintainer+Community have to validate that all fields are correctly set
Maintainer have to merge PR
Maintainer have to create a PR from staging to main
Maintainer have to merge PR

And not data can be dynamic (mainly repository stars)

Maybe the data should be saved in a "database" ℹ (so no more PR) and a form to submit a new component/tooling/template (with data validation during submission).
It would reduce the process to:

Creator fill the form (which have validation)
Creator submit the form
Maintainer review the submission
Maintainer validate the submission

It will offer a way to update dynamic data without the need to do a commit. (By running a script that will update the database directly or by fetching the data directly when reading the databaseℹ)
It can maybe also provided so more advanced search abilities

The drawback is that we lose the community aspect of validation, and the communication between the Creator and Maintainer/Community

We'd also have to code up email notifications to let maintainers know when there's something to review and the contributor to know when there's updates on their submission. Ideally we'd have some way to ask question or leave comments. It would add significant complexity to the application, so while it'd be a nicer workflow, I wonder if it's worth it. Especially with https://github.com/svelte-society/sveltesociety.dev/pull/108 which already addresses the biggest pain points

Creator have to ensure that all (mandatory) fields are filled
Creator have to ensure that fields are correctly set (typos, no unnecessary new tags, categories, etc.)

Have you seen https://github.com/svelte-society/sveltesociety.dev/pull/108? It addresses this

Creator need to fork the project
Creator need add the data in one of 3 JSON files
Creator have to open a PR

Did you know you can edit files directly in the GitHub UI? It will automatically fork the repo as needed and is pretty user-friendly

Maintainer have to create a PR from staging to main
Maintainer have to merge PR

Personally I'd drop these steps and just deploy directly to main as I think it just creates extra overhead https://github.com/svelte-society/sveltesociety.dev/issues/12#issuecomment-917259634, but that's sort of a separate discussion

Have you seen #108?

My bad! I didn't do my job correctly and search for similar issue

Did you know you can edit files directly in the GitHub UI? It will automatically fork the repo as needed and is pretty user-friendly

I know, but still I found that the need of forking the project can be somewhat a barrier for some people (and yes, I know, ours users are dev 😅 )

As it's a bit of a duplicate of #108 I will close it for now.
If the idea is still relevant, the issue can be reopen


perf: Performance issues with ion-checkbox and *ng-For

Type: perf
Ionic Version: 2.x
Platform: android 6.0 webview
This was tested in android device running 6.0 and 4.1, the computer web browser 'ionic-serve', genymotion emulator running android 4.4 and windows 10 platform.
Here is the app I did using this:
https://github.com/Bandito11/cibum2/blob/master/app/pages/main/ingredientes.html
Issue:
When iterating through the array list (which have over a 100 items) using an ion-checkbox the performance is ridiculously bad. When taking out the ion-checkbox and using  it iterates as fast as expected.
More details here:
https://forum.ionicframework.com/t/ngfor-performance-issues-when-getting-a-long-list-of-items/43010

I was able to reproduce this issue in the current version of ionic (RC3) using the tabs template.
Same behavior happens to me after about 100 ion-checkbox elements. The page will be laggy as well as the touch effect.
I did the same tests from the issue description and using a normal input type checkbox the screen will render fast.
Is there any chance we can reopen this issue please?
Thanks!

This is somehow still an issue for us... Using the ion-checkbox makes our scroll list unusable even with virtual scroll.