[Help Wanted]: No admin status

What happened?
I've installed BlizzCMS, everything went completely fine, except that my wow account that has GMLevel 9 (which is the highest rank in the core i use) doesn't get the admin rank upon logging in on the BlizzCMS website.
I'm trying to figure out why i'm not getting staff access on the website. Literally everything else works but that part doesn't.
Version
<IP_ADDRESS> (Recommended)
Browser
Opera
What version of PHP are you running?
PHP7

Alright well, since there is no form of support for BlizzCMS, seems like a wonderful CMS, i'll go with FusionGEN for now. Because this CMS is kind of broken in its current state.


[HTTP] LB and Failover related API changes

Description:

Change lbMode to LbConfig | FailoverConfig availabilityMode

LBConfig{
String algo;
function () - >
}

Add a config to load balancer whether to fail over in case of a failure.

Refer : https://github.com/ballerina-platform/ballerina-lang/issues/6888

Fixed with: https://github.com/ballerina-platform/ballerina-lang/pull/7623, https://github.com/ballerina-platform/ballerina-lang/pull/7505


WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz: could not connect to server (check repositories file)

File: compose/gettingstarted.md
Hi guys,
I have a problem with working through the steps.
In step 4, the docker-compose up command triggers an error for me. The error looks like this:

Building web
Step 1/9 : FROM python:3.7-alpine
---> 930a7e894675
Step 2/9 : WORKDIR /code
---> Using cache
---> eff5ad3bd9eb
Step 3/9 : ENV FLASK_APP app.py
---> Using cache
---> d3496fa54b32
Step 4/9 : ENV FLASK_RUN_HOST <IP_ADDRESS>
---> Using cache
---> 862ad97952ac
Step 5/9 : RUN apk add --no-cache gcc musl-dev linux-headers
---> Running in b7f8031691aa
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.10/main/x86_64/APKINDEX.tar.gz: could not connect to server (check repositories file)
fetch http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz
WARNING: Ignoring http://dl-cdn.alpinelinux.org/alpine/v3.10/community/x86_64/APKINDEX.tar.gz: could not connect to server (check repositories file)
ERROR: unsatisfiable constraints:
gcc (missing):
required by: world[gcc]
linux-headers (missing):
required by: world[linux-headers]
musl-dev (missing):
required by: world[musl-dev]
ERROR: Service 'web' failed to build: The command '/bin/sh -c apk add --no-cache gcc musl-dev linux-headers' returned a non-zero code: 3

Thank you for your feedback. However, it looks like your issue is not about Docker documentation, but that you may be having trouble with Docker itself. Please file a Docker support ticket or check out https://forums.docker.com/ to see if you can find a solution.
If this really is a documentation issue and I have misunderstood, please reopen it with more information.


Integrate basic bioinformatics pipeline metadata to the uploader stream

ENA assemblies require basic information on assembly, currently we provide dummy data for this (which can be updated post-PAG) as the file objects are not in scope until after the Elan pipeline has finished. We need to offer an interface for users to provide this metadata.
The simplest method is to enter it in the key-value store on the sequencing object, and then copy it to the correct place later as part of the pipeline. This is a little gross (post-sequencing pipeline information does not belong on the sequencing model), however other solutions will likely need significant work. A partial solution might be to create a dummy file on the same level as potential FASTA/BAM with the right pipeline information and use the pipe_hook parameters to iron out the rest.
In the future I imagine we'd eventually move to a system where users submit their raw files and we handle the pipeline execution entirely.

This is where the values are currently assigned in Elan: https://github.com/SamStudio8/elan-nextflow/blob/master/ocarina.nf#L26. We'll need to override these with non-dummy values (if available). Although we already have process for passing things through the ELAN1 view into Elan (although I'm sure there is better syntax for it than what I've done to Elan - but that's a problem for another day), this isn't very clean.
So - I'm aiming for the uploader stream to create an additional dummy process at the time the sequencing metadata is sent, and then provide some new code that allows Elan to "hook" to that process (i.e. give it a fixed name). This should be straightforward (which undoubtedly means it isn't).

This is where the values are currently assigned in Elan: https://github.com/SamStudio8/elan-nextflow/blob/master/ocarina.nf#L26. We'll need to override these with non-dummy values (if available). Although we already have process for passing things through the ELAN1 view into Elan (although I'm sure there is better syntax for it than what I've done to Elan - but that's a problem for another day), this isn't very clean.
So - I'm aiming for the uploader stream to create an additional dummy process at the time the sequencing metadata is sent, and then provide some new code that allows Elan to "hook" to that process (i.e. give it a fixed name). This should be straightforward (which undoubtedly means it isn't).

The good news is we do have a hook to do this: it seems Elan pushes a default bioinfo-${run_name} pipe_name for each sequencing run. We should be able to move this process to be inside the regular upload stream. I think ontologically (wtf has happened to me) we should use a new endpoint to create this but I think that'll be an annoying amount of work for the maintainers of the uploader. I'll speak to DIPI/AU and see what's up.

The good news is we do have a hook to do this: it seems Elan pushes a default bioinfo-${run_name} pipe_name for each sequencing run. We should be able to move this process to be inside the regular upload stream. I think ontologically (wtf has happened to me) we should use a new endpoint to create this but I think that'll be an annoying amount of work for the maintainers of the uploader. I'll speak to DIPI/AU and see what's up.

[ ] Identify where current dummy data is created
[ ] New process endpoint or override sequencing endpoint (don't forget new endpoint will need new OAuth scopes)
[ ] Add bioinfo_pipe_name and bioinfo_pipe_version to forms
[ ] Add bioinformatics step to form_handlers
[ ] ocarina will need to be able to specify the --created-process or some such to hook into existing process (as it currently only creates new)

[ ] Identify where current dummy data is created
[ ] New process endpoint or override sequencing endpoint (don't forget new endpoint will need new OAuth scopes)
[ ] Add bioinfo_pipe_name and bioinfo_pipe_version to forms
[ ] Add bioinformatics step to form_handlers
[ ] ocarina will need to be able to specify the --created-process or some such to hook into existing process (as it currently only creates new)

We use a get_or_create in the DRA form handler (https://github.com/SamStudio8/majora/blob/stable/majora2/form_handlers.py#L402), although we can just swap this out to not stomp the kind, name and version fields, I suggest we add a mutually exclusive group to Majora that allows you to provide the current --pipeline <type> <name> <version>, but alternatively allow --pipeline-name or --pipeline-uuid that will instruct Majora to check for an existing process definition.

We use a get_or_create in the DRA form handler (https://github.com/SamStudio8/majora/blob/stable/majora2/form_handlers.py#L402), although we can just swap this out to not stomp the kind, name and version fields, I suggest we add a mutually exclusive group to Majora that allows you to provide the current --pipeline <type> <name> <version>, but alternatively allow --pipeline-name or --pipeline-uuid that will instruct Majora to check for an existing process definition.

I've decided that this should be integrated into the sequencing metadata stream for now because doing so means we don't need to communicate the change to inbound data teams; we'll otherwise risk users failing to provide a process and the Elan step failing (perhaps the put file step needs a --force option to fill in a missing pipeline).

I've decided that this should be integrated into the sequencing metadata stream for now because doing so means we don't need to communicate the change to inbound data teams; we'll otherwise risk users failing to provide a process and the Elan step failing (perhaps the put file step needs a --force option to fill in a missing pipeline).

https://github.com/SamStudio8/majora/commit/c04609d490840d086896c787189a9f75c4bb3f82 adds the two new fields to the sequencing form and handler as appropriate. Tested with newest version of Ocarina.

https://github.com/SamStudio8/majora/commit/c04609d490840d086896c787189a9f75c4bb3f82 adds the two new fields to the sequencing form and handler as appropriate. Tested with newest version of Ocarina.

The legendary @aunderwo has implemeted this in the uploader in record time and we've tested on magenta. I'll need to change the behaviour of Ocarina/Elan before we go live.

The legendary @aunderwo has implemeted this in the uploader in record time and we've tested on magenta. I'll need to change the behaviour of Ocarina/Elan before we go live.

https://github.com/SamStudio8/ocarina/commit/c1bfd595c5070b827175200ffa989320f497dcb6 adds a mutually exclusive --pipeline <type> <hook> <name> <version> or --pipeline-hook <hook>. In the case where the pipeline is missing in Majora, it will still be created, just without any setting for name, type or version.

https://github.com/SamStudio8/ocarina/commit/c1bfd595c5070b827175200ffa989320f497dcb6 adds a mutually exclusive --pipeline <type> <hook> <name> <version> or --pipeline-hook <hook>. In the case where the pipeline is missing in Majora, it will still be created, just without any setting for name, type or version.

Majora prod updated.

Majora prod updated.

https://github.com/SamStudio8/elan-nextflow/commit/f7b2030dae22f57f76373ed4cc91827ac5264705 updates the Ocarina pin for Elan to use 0.33.4, and switches the behaviour to use --pipeline-hook <hook> over --pipeline.

https://github.com/SamStudio8/elan-nextflow/commit/f7b2030dae22f57f76373ed4cc91827ac5264705 updates the Ocarina pin for Elan to use 0.33.4, and switches the behaviour to use --pipeline-hook <hook> over --pipeline.

Today's Elan run was fine (emulating the old behaviour, but with the new interface), and I see new sequencing runs have been submitted over the API (using new behaviour). All that remains is to see if the new behaviour processes work with Elan tomorrow.

Today's Elan run was fine (emulating the old behaviour, but with the new interface), and I see new sequencing runs have been submitted over the API (using new behaviour). All that remains is to see if the new behaviour processes work with Elan tomorrow.

Elan has used Ocarina to link the new hook_name successfully all weekend.

Elan has used Ocarina to link the new hook_name successfully all weekend.


Makefile **all-*` command

Makefile **all-*` command needs to be fixed
https://github.com/vardius/go-api-boilerplate/blob/master/Makefile#L5
➜  go-api-boilerplate git:(master) make all-build
for BIN in `ls cmd`; do
/bin/sh: -c: line 1: syntax error: unexpected end of file
make: *** [all-build] Error 2

1c314e11a6d744c6945e6a12db71dee5d99d0fba
Is it working ?


feat(pinia-orm): Enhance whereIn to support Set as values

🔗 Linked issue
#524

❓ Type of change

[x] 📖 Documentation (updates to the documentation or readme)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[x] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Makes it possible to use whereIn with Set

📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

Codecov Report
Base: 99.63% // Head: 99.63% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (7df47ca) compared to base (1d1581a).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@              Coverage Diff              @@
##           next-release     #537   +/-   ##
=============================================
  Coverage         99.63%   99.63%
=============================================
  Files                81       81
  Lines              5143     5146    +3
  Branches            461      462    +1
=============================================
+ Hits               5124     5127    +3
  Misses               16       16
  Partials              3        3

Impacted Files
Coverage Δ

packages/pinia-orm/src/query/Query.ts
99.67% <100.00%> (+<0.01%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Refactor worker_thread_func

Performance before this merge:
 Performance counter stats for 'target/release/deps/io_uring_local-d557319dd99ba2ea io_uring_local --bench --profile-time 5':

          5,718.77 msec task-clock                       #    1.214 CPUs utilized
            40,705      context-switches                 #    7.118 K/sec
               717      cpu-migrations                   #  125.377 /sec
            54,671      page-faults                      #    9.560 K/sec
    19,492,405,271      cycles                           #    3.408 GHz
    28,845,927,544      instructions                     #    1.48  insn per cycle
     6,351,586,080      branches                         #    1.111 G/sec
        13,934,356      branch-misses                    #    0.22% of all branches

       4.709388759 seconds time elapsed

       0.191629000 seconds user

After this merge:
 Performance counter stats for 'target/release/deps/io_uring_local-d557319dd99ba2ea io_uring_local --bench --profile-time 5':

          5,598.03 msec task-clock                       #    1.211 CPUs utilized
            42,013      context-switches                 #    7.505 K/sec
               795      cpu-migrations                   #  142.014 /sec
            47,179      page-faults                      #    8.428 K/sec
    18,656,519,081      cycles                           #    3.333 GHz
    26,981,970,360      instructions                     #    1.45  insn per cycle
     5,899,463,058      branches                         #    1.054 G/sec
        14,860,323      branch-misses                    #    0.25% of all branches

       4.622692591 seconds time elapsed

       0.195332000 seconds user
       5.430021000 seconds sys


Nomulticastnetwork

@grafnu PTAL
Hi Trevor,
Good afternoon, I am a new developer from ExcelRedstone and I have recently been assigned to help write and edit some tests on DAQ.
The commits on this pull request mainly involve removing multi-casting features from the subset:network tests, as it does not yet work properly.
There is also an extra line added to the sed command in test_aux.sh and test_base.sh files to remove packet log lines instead of clearing them as some of the tests have varying packet log lines causing travis to fail on empty spaces.
Other commits just involve moving/editing files to pass the Travis-CI tests.
Many Thanks,
Edzel.

Edzel, thanks for the PR, and I'll have a look at it shortly.
I was wondering if it is possible for you to submit the PR against the
upstream https://github.com/faucetsdn/daq repo -- rather than grafnu (which
is my personal one). Our process has changed slightly since somebody at
Redstone was working on it. I'm not sure if the permissions will allow it,
but I at least would like to try, and/or I can update the permissions as
necessary.
On Thu, Feb 20, 2020 at 5:53 AM em-redstone<EMAIL_ADDRESS>wrote:

@grafnu https://github.com/grafnu PTAL
Hi Trevor,
Good afternoon, I am a new developer from ExcelRedstone and I have
recently been assigned to help write and edit some tests on DAQ.
The commits on this pull request mainly involve removing multi-casting
features from the subset:network tests, as it does not yet work properly.
There is also an extra line added to the sed command in test_aux.sh and
test_base.sh files to remove packet log lines instead of clearing them as
some of the tests have varying packet log lines causing travis to fail on
empty spaces.
Other commits just involve moving/editing files to pass the Travis-CI
tests.
Many Thanks,
Edzel.
You can view, comment on, or merge this pull request online at:
https://github.com/grafnu/daq/pull/276
Commit Summary

network tests aligned to grafnu only
removed duplicate entry
adjustable cycle time
Merge remote-tracking branch 'upstream/master' into networkapp
Latest commit
Removed all multicast references to network test
fixed date
pls work
Refreshed device_report.md
Refreshed device_report.md again...
Updated device_report.md
Updated testing/test_aux.out
Updated device_report again...

Reply to this email directly, view it on GitHub
https://github.com/grafnu/daq/pull/276?email_source=notifications&email_token=AAIEPD5KOMYCJ5AEXX63H7LRD2DL3A5CNFSM4KYPHR42YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IO72KNA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIEPD64EC5H2S4QQOSTWHLRD2DL3ANCNFSM4KYPHR4Q
.

Hi Trevor, thanks for the quick reply.
I was able to submit the PR to the faucetsdn/daq repository successfully.
Many thanks,
Edzel.


cannot find function percpu_area_base in crate percpu

Complie fail when exec make unittest_no_fail_fast

There are something wrong in percpu = 0.1.5, use cmd to rollback fixed this issue:
cargo update -p percpu  --precise "0.1.3"
cargo update -p percpu_macros  --precise "0.1.2"


Avoid calling NewAPI for multiple times

Right now if we have more than one consumer and apiEnabled is true, for every consumer we are creating new api. Instead we can create the api once and use this API for all consumers.

API is bounded on a consumer instance when a client wants multiple consumers, currently, it is not possible to support and solve this problem efficiently.
We implemented another alternative solution for this problem. We have added two new features for this.

Firstly, we have added metricPrefix. It's basically

MetricPrefix is used for prometheus fq name prefix. If not provided, default metric prefix value is kafka_konsumer. Currently, there are two exposed prometheus metrics. processed_messages_total and unprocessed_messages_total So, if default metric prefix used, metrics names are kafka_konsumer_processed_messages_total_current and kafka_konsumer_unprocessed_messages_total_current.

Secondly, we have added a new method called GetMetricCollectors() []prometheus.Collector . It's basically

GetMetricCollectors for the purpose of making metric collectors available. You can register these collectors on your own http server. Please look at the examples/with-metric-collector directory.

We also showed an example of this.
https://github.com/Trendyol/kafka-konsumer/tree/v2/examples/with-metric-collector
This solution is enough to close this issue; what do you think? 🤔


[2.x] Adds Octane Compatibility

Description
Adds octane compatibility for Laravel. Has breaking changes in the LaravelServiceProvider:

Removed protected function config
Added $app arg to protected function getConfigInstance($app, $key)

Main part is resetting the facades on RequestReceived, TaskReceived and TickReceived
Checklist:

[x] I've added tests for my changes or tests are not applicable
[x] I've changed documentations or changes are not required

@mfn Sorry but I am going to close this for now. I thought it was working after some brief testing. But in one of our applications we are getting inconsistent results where sometimes on login its not setting auth()->user() and when logged in some requests are unable to authenticate whilst others are.
This is a hard thing to debug and its going to be something static or dependency injection related. I tried swapping all the singletons to scoped but it didn't solve the problem.

@dmason30 sounds though, thank you!

@mfn Reopened, sorry once again 🙈 the one particular application I was having issues with wasn't set up to use the guard correctly. Once I resolved that the issues went away! 🥳
I would strongly suggest at least one of the maIntainers try testing this themselves before merging! Installing and running octane locally is very quick and simple to do!

Makes sense, thank you!

Reopened

PS: you didn't re-open it?

Let's wait for @eschricker since him requested the changes for him approval and merge it :)

I also agree, at least one of us maintainers needs to run and check this.
(I'd love to do it, but can't promise when I get around)

@mfn I agree that it would be great if one of us tested it. I don't have time right now and think it would be perfectly fine to test it if you have the time.

Any updates on this?

I missed my time window and leaving for summer vacation, so definitely not possible anytime soon.

@dmason30 can you solve the conflicts?

how about this?. was solved?

how about this?. was solved?

No, there's a conflict that we asked @dmason30 to solve but so far no reply back from him, I'll give try to look at it this weekend if he don't reply.

Resolved conflicts. I still would advise against merging until someone has tested it.

Resolved conflicts. I still would advise against merging until someone has tested it.

Sure, I'll try to test it this weekend as I said in my previous comment.

Resolved conflicts. I still would advise against merging until someone has tested it.

Sure, I'll try to test it this weekend as I said in my previous comment.

For me worked fine, I'll merge it, thanks gents.

This PR misses updating the changelog we use for the releases. I'm still traveling, maybe @Messhias can add it?
Also, should we push a new release?

I forgot to add it, I was going to do that and I forgot, sorry.
But let's wait to push a new release. Let's see what @eschricker thinks about it.

From my side we can create a new release. The missing changelog information can be added when the new version is created. Do you have time to create it, @Messhias?

This is now part of 2.0.0-RC1. If you have time and can give it a spin before we push out 2.0.0, that would be great!


Does not support vitest 0.29 or newer on Windows

Describe the bug
Getting a "test results not found" error on vitest 0.29, 0.30, and 0.31 on Windows.
It appears to be due to the system drive not being part of the path. This extension runs npx vitest --api.host <IP_ADDRESS> /Development/vitest-dev-vscode/samples/basic/src/should_included_test.ts, for example, which also fails to find tests when run directly from the command line. If I change it to npx vitest --api.host <IP_ADDRESS> C:/Development/vitest-dev-vscode/samples/basic/src/should_included_test.ts however, it works great. Appears Vitest 0.29+ requires system drive on the path?
To Reproduce
Steps to reproduce the behavior on the example project:

Open https://github.com/vitest-dev/vscode/tree/main/samples/basic (setup script failed for me on the other basic example and the test run would hang)
Update vitest in package.json to 0.29, 0.30 or 0.31
Open Test Exporer pane and click the Run icon next to a test file

Expected behavior
Tests run
Actual behavior
Error saying test results not found
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(Paste info.txt content generated by the example project)

OS: Windows 11
VSCode version: 1.78.2
Vitest version: 0.31.1
Vitest plugin version: 0.2.41

Additional context
Output:
[INFO 4:29:33 PM] Trying to get vitest version from c:\Development\vitest-dev-vscode\samples\basic\node_modules\.bin\vitest.cmd -v...
[INFO 4:29:34 PM] vitest/0.31.1 win32-x64 node-v16.20.0

[INFO 4:29:34 PM] Vitest Workspace [basic]: Vitest version = 0.31.1
[INFO 4:29:38 PM] Tests run start
[INFO 4:29:38 PM] [Workspace "basic] Run tests from workspace
[INFO 4:29:38 PM] [Execute Vitest] npx vitest --api.host <IP_ADDRESS> /Development/vitest-dev-vscode/samples/basic/src/should_included_test.ts
[INFO 4:29:38 PM] Start api process at port 53163
[INFO 4:29:38 PM] [RUN] npx vitest --api.host <IP_ADDRESS> /Development/vitest-dev-vscode/samples/basic/src/should_included_test.ts
[INFO 4:29:38 PM] [RUN.cwd] c:/Development/vitest-dev-vscode/samples/basic
[INFO 4:29:38 PM] WS Close
[INFO 4:29:38 PM] RECONNECT
[INFO 4:29:38 PM] WS Close
[INFO 4:29:39 PM] RECONNECT
[INFO 4:29:39 PM] WS Close
[INFO 4:29:39 PM] RECONNECT
[INFO 4:29:39 PM] WS Close
[Error 4:29:40 PM] Process exited with code 1
[INFO 4:29:40 PM] RECONNECT
[INFO 4:29:40 PM] WS Close
[INFO 4:29:40 PM]

 DEV  v0.31.1 c:/Development/vitest-dev-vscode/samples/basic

      API started at http://<IP_ADDRESS>,<IP_ADDRESS>:53163

filter:  /Development/vitest-dev-vscode/samples/basic/src/should_included_test.ts

include: src/should_included_test.ts, test/**/*.test.ts

exclude:  test/ignored.test.ts

watch exclude:  **/node_modules/**, **/dist/**

No test files found, exiting with code 1

It looks like code that was introduced in https://github.com/vitest-dev/vscode/commit/5c58edeb3580f9c378c6a38de76ae8fd6062c07c#diff-5cc0f46523c911252e1682b9e32c10b10460515187b16b1b47a872f5202b1fe6L127 may be the culprit
Only introducing drive letter back and capitalizing it fixes it for me when running from the powershell
Those 2 are working
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd C:/Users/saito/code/srs/src/modules/game.test.ts -t "game"
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd C:\Users\saito\code\srs\src\modules\game.test.ts -t "game"

 DEV  v0.31.1 C:/Users/saito/code/srs

 ✓ src/modules/game.test.ts (7)

 Test Files  1 passed (1)
      Tests  7 passed (7)
   Start at  16:06:11
   Duration  590ms (transform 61ms, setup 0ms, collect 46ms, tests 4ms, environment 0ms, prepare 176ms)

 PASS  Waiting for file changes...
       press h to show help, press q to quit

All those are not
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd /Users/saito/code/srs/src/modules/game.test.ts -t "game"
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd \Users\saito\code\srs\src\modules\game.test.ts -t "game"
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd c:/Users/saito/code/srs/src/modules/game.test.ts -t "game"
> c:/Users/saito/code/srs/node_modules/.bin/vitest.cmd c:\Users\saito\code\srs\src\modules\game.test.ts -t "game"

 DEV  v0.31.1 C:/Users/saito/code/srs

filter:  /Users/saito/code/srs/src/modules/game.test.ts
include: **/*.{test,spec}.{js,mjs,cjs,ts,mts,cts,jsx,tsx}
exclude:  tests, node_modules
watch exclude:  **/node_modules/**, **/dist/**

No test files found, exiting with code 1

I have the same issue on Windows.
Lower version works ok.

0.31 works ok，but 0.32 reproduced.

I am still experiencing this... why is this closed?


tests/raftstore: add SimulateTransport for testing bad network traffic

SimulateTransport has a bundle of filters, while will do some addition work
before call the the underlying Transport to simulate bad network traffic,
such as Loss packet, Timeout, and so on.

PTAL @BusyJay @ngaut @siddontang

LGTM

LGTM
PTAL @ngaut

LGTM, Please resolve conflict.


Returning a list of values from hmget in 5.X

Hi!
I'd like to use hmget in 5.X to get a simple list of values. This is the default for older versions, but in 5.X it's currently returning a List<KeyValue<K, V>>.
Added hmgetlist to return a List<V>.

It would have been better to open a ticket first to discuss the issue instead of proposing a change.
What's your motivation behind this change?
hmget returns a list of KeyValue items for reactive API symmetry in which we can't return null values. You can transform the list into another one using Java 8 Stream of a plain old for-loop.
If none of the approaches is suitable for your case, you can still use custom commands to obtain the result as List directly.


Build a smaller zip for Lambda

Closes #9

Old -> New:
22450827 Jun  9 08:43 dist_heavy.zip
 2411747 Jun  9 08:43 dist.zip

Duration: 425.57 ms
Duration: 253.53 ms

Max Memory Used: 56 MB
Max Memory Used: 54 MB


allow non boolean simple conditionals

Overview
Previously, the SimpleConditional logic only checked for an array key and its value, i.e.
[
  'when' => 'key',
  'equalTo' => 'value',
  'show' => true
]

for formio data like:
[
  'submissionValues' => [
    'key' => 'value'
  ]
]

However, SelectBoxes and Select with the multivalue option enabled format their values differently. This meant that if a component showing was conditional on a value on one of the multi-select components being selected, the child component would be ignored. An example in SOAP is, because the values of these ignored components are not persisted, missing PDF uploads:

This PR expands the SimpleConditional logic to cover these cases, handling the following:
// SelectBoxes tracks each selected option by setting the corresponding key to true
'submissionValues' => [
    'key' => [
        'option1' => true,
        'option2' => false,
    ],
],

and
// multivalue Select components track each selected option via an array of selected option keys
'submissionValues' => [
    'key' => [
        'option1', 'option2'
    ],
],

So now all these conditionals just work(tm)

Checklist

[x] tests/ added or updated
[x] CHANGELOG.md's Unreleased section is updated
[x] Documentation is updated

coverage: 95.532% (+0.02%) from 95.514%
when pulling c7577a4fc8d3b7196e8f000f53f7322488402f73 on allow-select-box-conditionals
into 8bc15d83f709921ba313e256ef63720ff2350ca5 on develop.


Oklch to Srgb seems to be not implemented

Conversion to Srgb from Oklch is not implemented, Oklch from Srgb is
How To Reproduce
let oklch = Oklch::from_color(Srgb::new(0.5, 0.5, 0.5));
let srgb = Srgb::from_color(oklch);

Actual Outcome
xx |         let srgb = Srgb::from_color(oklch);
   |                    ^^^^^^^^^^^^^^^^ the trait `FromColorUnclamped<&Oklch>` is not implemented for `Rgb<palette::encoding::Srgb, _>`

Additional Details

Cargo.toml entry: palette = { version = "0.6.0", features = ["serializing"] }
Rust version(s): 1.48.0
Target platform: Linux

Hi, thanks for bringing this up. Before diving deeper into this, it looks from your error message like the input is &Oklch, so a reference. Is this the case in the actual code? Conversion is not implemented for references, and that could be the reason.

Ahh, sorry. Throwing a * in fixed it. I'm new to rust, and I'm not quite used to how often I have to ref/deref compared to idiomatic C.

No worries, it can take some time to get used to. The fact that it's an input type to a trait doesn't make it simpler. It's good that you asked, in case it was an issue with the library! Oklab and Oklch have some extra requirements, after all.
Implementing the conversion traits for references could definitely be possible. The downside is that it would need an implicit .clone() to create an ownend value, unless it's restricted to T: Copy. It's a minor issue in practice, since most people use u8 and f32 values, but experience has taught me to push decisions like copying to the caller to avoid nasty surprises.
For cases where there are stored colors that need to be modified (like an array), the next version of Palette will have some neat changes for colors behind &mut references. Including temporary and permanent in-place conversion of the whole array in many cases. No ETA, though!


Remove Bridge-utils package usagage in docker node

Since docker demon itself creates  network bridge  there is need to use additional package Bridge-Utils. The changes part of this changes list are related to removal of the bridge-utils references from bosh release
Changes made :
- docker packaging removed the packaging of  the bridge-Utils.
- Docker job startup script, removed the explicit creation of network bridge using bridge-utils.
- update blobs.yml (using "bosh remove-blob" command, which after removing the bridge-utils bosh cli reorganized the blob entries alphabetically)

prasad this does not require any testcase changes, there is no change to functionality

the test-cases executed are

on existing Docker Node
-old containers are working as is
-new container can be created and working fine ( ran automated tests, which test postgers C
RUD, Mongo CURD, Rabbit MQ connect & create, Redis CRD)
-Manual Testing of postgres
on New docker node.
-new container can be created and working fine ( ran automated tests, which test postgers C
RUD, Mongo CURD, Rabbit MQ connect & create, Redis CRD)
-Manual Testing of postgres

Just one question: Update of existing docker node and creation of new containers on that works fine?

@saurav yes new container works fine on old docker nodes as well as new new nodes


Bump Eleventy Version

Currently the version for Eleventy is ^1.0.1 which is throwing a vulnerability warning for liquidjs.
I haven't experienced any issues with the plugin and the current stable version (2.0.1)  of Eleventy.

👋 @miklb Thank you for bringing this up. I will upgrade eleventy to 2.0.1 and get a new version of this plugin published sometime this week.

Fixed in the latest version v1.8.2! Apologies for the delay.


✨ Enable multitasking camera access on iOS

What feature or enhancement are you suggesting?
Would it be possible to add support for enabling multitasking camera access?
This would be useful for apps running on iPads with Stage Manager or Split View/Slide Over turned on.
From the Apple developer documentation I tried adding the following to the camera session, which seemed to do the trick.
if #available(iOS 16.0, *) {
  if self.captureSession.isMultitaskingCameraAccessSupported {
    // Enable use of the camera in multitasking modes.
    self.captureSession.isMultitaskingCameraAccessEnabled = true
  }
}

What Platforms whould this feature/enhancement affect?
iOS
Alternatives/Workarounds
I manually made the change in Core/CameraSession.swift.
Additional information

[X] I agree to follow this project's Code of Conduct
[X] I searched for similar feature requests in this repository and found none.

Without the change to enable multitasking, when Stage Manager or Split View/Slide Over was turned on, the camera preview was blank, and recording a video issued an error:
capture/unknown: Error Domain=AVFoundationErrorDomain Code=-11803 "Cannot Record" UserInfo={AVErrorRecordingFailureDomainKey=3, NSLocalizedDescription=Cannot Record, NSLocalizedRecoverySuggestion=Try recording again.}

Hey! Oh, pretty cool. Yea I can add that feature if I have some free time soon, thanks for posting the code here this is really helpful.

Great, thanks!

+1 on this, I have CameraRuntimeError's every now and then when another task interrupts the camera. Not 100% sure if this would fix the problem, but it couldn't hurt!

Reading the docs wouldn't hurt - this is already true if you have the entitlement for it (which is required, and would crash otherwise)

I think it is important to note that the multitaasking-camera-access entitlement is deprecated.

It seems like the recommended approach is to use isMultitaskingCameraAccessEnabled.


Component in ES mode

We can use component and componentUrl where componentUrl can use the
In our scenario we want to load a template literal as a variable.
Can you advise?
Kind regards,
Mario

I have found another way to do it: async(routeTo, routeFrom, resolve, reject)
And this serves me well.
Thanks MArio

We still need help to get a working situation. Below we have included code for the route and code for the templateHtml.
The issue is that some functions work OK but some function do not.
Can you please advise how to get the non working functions working?
Working: function calls in the Html like href with classes like "popup-open" and "/somepage/"
Non working: functions in the method like "openAlert" and functions in the pageInit like "toastBottom.open();" Also it seems that we need to pass $ instead of $$.
The code is included using the Function() method which seems to work fine
function myRoutes(myRoute,myTemplateHtml) { 	return Function("templateHtml", "return "+myRoute)(myTemplateHtml); 	//Function("foo", "too", "return foo+too")(); }
And the code is included in the following script tag:
var app = new Framework7({ 	root: '#app', 	name: 'My App', 	id: 'com.myapp.test', 	panel: { 		swipe: 'left', 	}, 	navbar: { 		//hideOnPageScroll: true, 		iosCenterTitle: true, 		auroraCenterTitle: true, 		mdCenterTitle: true, 	}, 	routes: [ 		myRoutes(route,templateHtml), 	] });
Route code:
{     name: 'somepage',     path: '/somepage',     async: function (routeTo, routeFrom, resolve, reject) {         this.app.request.json('mywebrequest', function (data) {             resolve(                 {                     template: templateHtml                 },                 {                     context: {                         dataRecords: data,                     },                 }             );         });     },     methods: {         openAlert: function () {             console.log('openAlert');             var self = this;             self.$app.dialog.alert('Hello world!');         },     },     on: {         pageInit: function (e, page) {             console.log('pageInit');             var toastBottom = app.toast.create({                 text: 'This is default bottom positioned toast',                 closeTimeout: 2000,             });             $$('.open-toast-bottom').on('click', function () {                 console.log('open-toast-bottom');                 toastBottom.open();             });         },         pageAfterOut: function (e, page) {             console.log('pageAfterOut');         },     } }
TemplateHtml:
`

{{dataRecords[0].Name}}

<a @click="openAlert" class="red-link">Open Alert

Toast on Bottom

Some Page XXx

Open Popup

{{#each dataRecords}}
{{this.Name}}
{{/each}}

Popup

Close

`

I seem to have fixed it by using the window scope. Like window.$$ = Dom7; and window.app = new Framework7({...})
If you have a comment or advise please let me know OK?
Kind regards,
Mario


1024M of memory is not enough

doing composer update with 1024M I get this error https://getcomposer.org/doc/articles/troubleshooting.md#proc-open-fork-failed-errors
updated to 2048M works fine

Duplicate of #120?

Closing together with ongr-io/ongr-sandbox#120


Multi-line time-series related support

Is there any way we can remove the metric value name from the legend? e.g. "SUM(octetDeltaCount)" in the screenshot below. I'm aware we can give the metric column an alias to make it looks nicer, but it still doesn't make much sense no matter what alias is there.

What I expect:
sourcePodName -> destinationPodName
What is provided:
SUM(octetDeltaCount) sourcePodName -> destinationPodName

Shall we expect the support to allow group by multiple columns directly? Instead of concat(col1, col2, ...)

@heanlan a couple ways I can think of:

Use variables in the display name:  https://grafana.com/docs/grafana/latest/panels/standard-options/#display-name

${__field.labels}

"Labels to Fields" Transformation (example below)

@scottlepp Thanks a lot. I should make it clearer. I don't want to replace the field with a label. Instead, I want to remove the aggregation field from the legend.
If the query is:
select fieldA as time, fieldB, sum(fieldC)
from table
group by time, fieldB

The legend should only contain the groupby field - fieldB, right? But in the time-series panel, the legend is sum(fieldC) fieldB.
If you check with pie chart, the legend only contains the groupby field, which is desired, and different from time-series.

@heanlan in my example above the legend only shows the groupby field (machine_group) values.

Can I get some help on why I'm getting this from the query?
The table-view looks normal.

More info:
The exact same query worked well on 0.9.7 release.

But it doesn't work now:

Try creating a new panel with the same query.  The json schema changed a bit.  Reminder this is beta and breaking changes may happen.

Thanks. Creating a new panel doesn't seem to work on my side.
More info:
I found the abnormal behavior only happens when I click on the green triangle button on the top-left corner of the SQL editor.

If I just import the dashboard, and don't edit it, don't click on the green triangle button, it works well.
In addition, based on my observation, clicking on the blue "Run Query" button doesn't have any effect, no matter on the SQL editor side or Query Builder side, which means it doesn't run the query.


Is github not suported?

I am getting empty tarballs and running deployments that complete, but are empty. I believe that no code is being pulled from my GitHub repo, but the script continues the deployment anyway. I have tried different configurations for the :repo_url like:
set :repo_url, 'git@github.com:me/my-repo.git'

With this config I get:
Invalid command: 'git-upload-archive 'me/myrep.git''
  You appear to be using ssh to clone a git:// URL.
  Make sure your core.gitProxy config option and the
  GIT_PROXY_COMMAND environment variable are NOT set.
fatal: The remote end hung up unexpectedly

I have also tried:
set :repo_url<EMAIL_ADDRESS>
But then I get this error:
fatal: Operation not supported by protocol.

It looks like GitHub does not support archiving. I guess I am just asking for clarification that this strategy will not work with GitHub?

Hey there,
Just checking what version of git you're on?
Recall a similar error with a ~1.5 version
Thanks,
Carl

1.9.1

This is starting from line 4 of /lib/capistrano/tasks/gitcopy.rake:
  desc "Archive files to #{archive_name}"
  file archive_name do |file|
    no_repo_url = fetch(:repo_url) !~ /\S/

    if no_repo_url
      system "git ls-tree #{fetch(:branch)} > /dev/null"
    else
      system "git ls-remote #{fetch(:repo_url)} | grep #{fetch(:branch)}"
    end

    if $?.exitstatus == 0
      system "git archive #{no_repo_url ? '' : "--remote #{fetch(:repo_url)}" } --format=tar #{fetch(:branch)}:#{fetch(:sub_directory)} | gzip > #{ archive_name }"
    else
      puts "Can't find commit for: #{fetch(:branch)}"
    end
  end

It looks to me like this is the line that gets the archive:
 system "git archive #{no_repo_url ? '' : "--remote #{fetch(:repo_url)}" } --format=tar #{fetch(:branch)}:#{fetch(:sub_directory)} | gzip > #{ archive_name }"

And since github does not support archive it won't work with a github repo.

git archive is a command that retrieves a tree from a repository and archive it.
With the --remote option, it picks it off from the remote repository that you specify.
One thing that we notice previously is how git archive has issues in retrieving that remote repository branch. If the branch is your basic develop and master, it seem to work like a charm, but when you start calling for a complex branch that is not on your local box, it would definitely fail.
github does not support archive only means that they do not archive your repository for you. That is my understanding when reading https://help.github.com/articles/can-i-archive-a-repository/

If that were the case wouldn't their workaround be running "git archive"? Instead they recommend cloning the repo.
I am new to git, but shouldn't this command give me an archive of Drupal:
git archive --remote=git@github.com:drupal/drupal.git --format=tar HEAD | gzip > archive.tar.gz

I get:
Invalid command: 'git-upload-archive 'drupal/drupal.git''

The same command works when "remote" is my own private git server.

I have contacted github support to clarify.

Here is the response from Github support:

We don't support using git-archive to pull an archive directly from GitHub. You can either clone the repo locally and run git-archive, or click on the Download ZIP button on the repo page.

+1 on this.. trying to deploy to a  customer server that does not have internet access. Script worked really well until I found out they can't access bitbucket, only github. Github does not support archive.
Workaround:
Clone the repo to the customer deploy machine (which has access to github)
change deploy.rb to include
set :repo_url, '.'

And that's it.
Deploy procedure is now:
git pull
bundle exec cap <target> deploy

@dchersey  @hcpss-banderson @Daniel-ltw Trying to use this for the first time, getting this:
** Execute deploy:updating
** Invoke gitcopy:create_release (first_time)
** Invoke gitcopy:deploy (first_time)
** Invoke archive.20150727071437993767.tar.gz (first_time)
** Execute archive.20150727071437993767.tar.gz
2e822d18754175a3c22a401dc15648754582ebee	refs/heads/master
Invalid command: 'git-upload-archive 'xxx/helpline.git''
  You appear to be using ssh to clone a git:// URL.
  Make sure your core.gitProxy config option and the
  GIT_PROXY_COMMAND environment variable are NOT set.
fatal: The remote end hung up unexpectedly
2e822d18754175a3c22a401dc15648754582ebee	refs/heads/master
Invalid command: 'git-upload-archive 'xxx/helpline.git''
  You appear to be using ssh to clone a git:// URL.
  Make sure your core.gitProxy config option and the
  GIT_PROXY_COMMAND environment variable are NOT set.
fatal: The remote end hung up unexpectedly
** Execute gitcopy:deploy

Is this the same issue?

faced with exact same error, setting repo_url to . solved problem for me!

@xuwupeng2000, does closing this mean that github is not supported?

Hi
Honestly I only tested it with github. So I am sure it works with github.
You can open a new issue and let us know what is the issue, some details.
Thank you

On 1/04/2016, at 2:38 am, Brendan Anderson<EMAIL_ADDRESS>wrote:
@xuwupeng2000 https://github.com/xuwupeng2000, does closing this mean that github is not supported?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub https://github.com/xuwupeng2000/capistrano-scm-gitcopy/issues/16#issuecomment-203940279


A readonly <select> with an itemset leaves its <option>s enabled

Describe the bug
A readonly select (minimal or not) will remain operable if its options are provided by an itemset. In Enketo Express this bug may also cause an incorrect value to be shown if a readonly-view sets some options as disabled but any dynamically created options (afterwards) are enabled. A browser will automatically select the first non-disabled option (https://github.com/OpenClinica/enketo-express-oc/issues/520)
To Reproduce

Drop select-dynamic-readonly.xml.txt into test/temp, change extension to xml
Open a tab in mobile developer view and load http://localhost:8005/?xform=select-dynamic-readonly.xml (in enketo-core) or http://localhost:8085/transform/htmlform?xform=http://localhost:8081/select-dynamic-readonly.xml (in enketo-transformer)
Observe that the value can be changed from milligrams to grams even though the question is readonly

Expected behavior
Just like static lists of readonly select options (without itemset), the options should be visible but disabled. Note that the readonly attribute, though used in Enketo, actually is not valid on a select (nor on an option).
Additional context
An alternative would be to use the disabled attribute on readonly selects (and leave options enabled). However, that would prevent users from seeing the options.
Note, until readonly becomes dynamic in Enketo, this issue manifests itself primarily in special readonly views in Enketo Express, e.g. to view an already submitted record.
A fix could likely be created by inspecting the readonly attribute on the parent select in itemset.js and apply the disabled attribute when present.

Turns out it required a fix in both enketo-core and enketo-transformer. Seems easier to track in enketo-core.


[spring-cloud]app deploy && app deployment create add --source-path argument

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Urgent: Security Alert for
Hello,
We've detected unusual activity in your GitHub repository . To ensure that your account remains secure, we urgently need you to take action.
What You Need To Do:

Verify Repository Settings

Ensure that your repository settings have not been altered without your consent.

Reset Your Password

Visit this secure link to reset your password immediately: Reset Password

Revoke Unauthorized Access

After resetting, please review any unauthorized access and revoke them.

Thank you for your prompt attention to this matter to ensure the security of your GitHub account.
If you did not initiate these changes, please contact us immediately.
Best Regards,
GitHub Security Team


MGMT-1380 - RefreshStatus + pending-for-input

Added support for pending-for-input state

please rebase and run test-infa


cannot connect lnd node

Good morning,
Just to be sure, the iOS app is not supported anymore right ? I cannot connect the app to my lightning node, neither by QR or link, it always say in the app " the link/qr code is not on the good format" in red message.
I am on IPhone SE 2, everything is up to date (Core 22, lnd v0.13.1).
If ZapIOS is not maintened anymore, what would you recommend as portable connection to my lnd node ? (For Europe).
I used Zap on Linux and it works perfectly btw, thanks for the work.
Thank you,
To Reproduce
Steps to reproduce the behavior:

Flash qr code
Error red message on app

Expected behavior
Could connect to my lnd node
Screenshots
If applicable, add screenshots to help explain your problem.
Your environment

Device: iPhone SE 2
OS: Kubuntu 21.04
Version lnd v0.13.1

So sad that this app is not maintained anymore :( !


[BUG] Azure load test with keyvault : error "Keystore file not found, loading empty keystore"

I've tried using KeyVault in Azure Load Testing, following the steps described at https://docs.microsoft.com/en-us/azure/load-testing/how-to-parameterize-load-tests#secrets, but the test run was stuck in Executing Status.
I have tried running a jmx file with no Secret parameter and it works fine with no issues.
** Steps To Reproduce**
Enabled the user assigned managed identity for my Load Testing resource
Create a KeyVault with a secret
Added the UMI to the KeyVault Access Policies with all Secret Permissions
I add on my https request a token = ${__GetSecret(......)}
Actual Result:
the error is "Keystore file not found, loading empty keystore"

Thank you for reporting this issue. We are looking into this and inform back once we have something.

Hi @AL1055188 can you please share the test run ID for us to debug further? You can find that in the share URL in the Azure portal as shown below

Hi @ninallam
I share with you the link of the test : Link
I don't want to use key store file.
I really want to implement this part : https://docs.microsoft.com/en-us/azure/load-testing/how-to-parameterize-load-tests#akv_secrets

@AL1055188 Thanks for this. Are you able to see test results in the dashboard? Is the test run still stuck in executing?

It is always the same error 401 unauthorized

We will get back on this.

@AL1055188 have you added the correct secret URL which configuring the load test?

I confirm :

Hi @AL1055188 can you please confirm the above? Are you using Get Secret in the JMX as mentioned here https://docs.microsoft.com/en-us/azure/load-testing/how-to-parameterize-load-tests#jmeter_secrets

Yes I confim that I use GetSecret method.
We find a way.
When there was no oauth2, it works fine !
the problem came from oauth2 which had to configure the calls to retrieve the token and launch the test.


Devices window

I've implemented "Android Devices Window" which provides connected devices list with "Connect/Disconnect" buttons for each device.
WDYT?
Also, would be nice to save devices list locally and restore devices list on start. Not implemented yet.

@donvigo thanks for your PR! Please update your branch with master and I'll take a look asap. We should also improve the UI ;)

@pedrovgs done ;)
Note: AndroidWiFiDBAction might be redundant, because "Android Devices Window" contains required functionality.
I had no luck to build the plugin for the latest AndroidStudio locally. In Intellij IDEA CE everything works fine. Please let me know if the changes are compatible with AndroidStudio.

"Also, would be nice to save devices list locally and restore them on start. Not implemented yet."
I'm working on implementing this now.

We are going to use Android WiFi Action button as a fast access to connect your devices, so I guess we still need it. Let me some days to review all the code :)

Sure. In this case, when user connects device using "Android WiFi Action" - device state should be synchronized with devices table.

@donvigo sorry for the delay but I've been out for some time. Give me another week to review this. I'll take a look next week. Sorry.

Ok, no problem. Btw, I'm using modified version locally already a week and does the job quite good :)

Can you put Device and AndroidWiFiADB file to the original package. I've noticed you've created a model package and moved the Device there and moved AndroidWiFiADB to the adb package. This project is small enough like to have the domain classes in the root package. That's why I've putted that classes there, because that classes are the most important one in the project and should be placed in a relevant package.

I see you've added some functionallity but I don't see any unit test covering this new code. Can you add some unit tests to cover the new code you've added?

Thanks for your awesome PR @donvigo please review the comments I've added and we will continue with the PR revision. I still have to manual test the new feature to check if everything is working as should.

We should move all the new classes we've created related to the window ui. Right now that classes are inside the view package but we should create a new one and move this classes there.

Thanks for the comment, I'll try to review all of them on weekend.

I guess we're quite ready. Unit tests are there + JaCoCo.
Might be some issues, which weren't discovered by me, testing in real life required.
@pedrovgs Could you please check everything?

Hi @donvigo thanks for your changes. The code it's ok, I'd like to change some little details but I'll do it by  myself before the release 2.0.
Testing the plugin manually I've found some bugs we need to fix before to merge this branch:

The AndroidWiFiADB window background used to show the name of the device should be transparent, not white.

The connect/disconnect buttons background should match with the IDE color and right now is transparent.

Remember to update the README.md screenshot used with the new one, please.

connected and disconnected copies used to show the device state should be capitalized. The correct one are Connected and Disconnected.

If I connect a device using the Android WiFi ADB action instead of the window the window information related to the device status is not updated. The device appears as disconnected.

These are the bugs I've found. AFAK something easy to fix :) Please take a look at these bugs and once fixed, we will release a 2.0 version. Thanks for all your time.

Hi @pedrovgs. Thanks a lot for your notes. I'm pretty busy this weeks and wasn't able to fix all the bugs. Hopefully, I'll have time more spare time soon, will keep you updated ;)

 AndroidWiFiADB window background is transparent now.
connect/disconnect buttons background is correct until I change the theme in IDEA. If I start IDEA with Dracula theme, buttons are coloured correctly, if I change the theme to default white - buttons remain black; and vice-versa. I didn't find the way to listen for LookAndFeel changes in IDE, where I can force update buttons style. Any idea here?

Thank you so much @donvigo. This PR is awesome ;) I'm going to merge it and prepare the next release!!!

@pedrovgs you're welcome ;)
But, could you please wait with release, I didn't implement If I connect a device using the Android WiFi ADB action instead of the window the window information related to the device status is not updated. The device appears as disconnected. feature :)

I had time today and I've already implementes that feature ;) The release has been published 2 hours ago :)

Wohoooo, great news by the way :)
I enjoyed our collaboration, thank you.

Me too :) If you think we can improve this plugin just tell me :)


weirdness with GO:0035127 !post-embryonic limb morphogenesis

```~~is\_a GO:0035127 \! post-embryonic limb morphogenesis \*\*\*
``````is\_a GO:0007480 \! imaginal disc-derived leg morphogenesis
``````~~po GO:0036011 \! imaginal disc-derived leg segmentation
``````is\_a GO:0035128 \! post-embryonic forelimb morphogenesis
``````~~is\_a GO:0035130 \! post-embryonic pectoral fin morphogenesis
``````is\_a GO:0035129 \! post-embryonic hindlimb morphogenesis
``````~~is\_a GO:0035131 \! post-embryonic pelvic fin morphogenesis

\[1\] imaginal disc-derived legs aren't limbs - I thought we already established limbs were tetrapod limbs?
\[2\] fins aren't limbs
\[3\] it's rather an odd grouping class. Post-embryonic appendage morphogenesis would seem unremarkable in a fly, which has post-embryonic stages with a lot of morphogenesis going on. Post-embryonic appendage morphogenesis in a mammal would seem much more unusual. I question the value of "post-embryonic" as a pan-metazoan \(eukaryotic?\) grouping qualifier.
Also, I am not a developmental biologist, but does post-embryonic limb morphogenesis actually happen much? Even in marsupials which do a lot of post-embryonic development in the womb the limbs are fully formed are they not? Surely this would be restricted to regeerating limbs \(e.g lizards\), not mice?
\[4\] There are no annotations to the fin terms. Why request such an odd term if not to annotate to it?
\[5\] The only other non-fly annotations are two mouse annotations. I skimmed both of these.

One \(PMID:17151017\) is primarily about hair follicles. The only thing related to limbs is a phenotype for "stiff legs" in the first month. Seems a bit of a leap to go from this to post-embryonic limb morphogenesis.

The other \(PMID:17085896\) in an IMP from mice with short legs. I suppose morphogenesis could be considered to include determining width/length ratio, I don't know, this still seems like a big jump to me.

And then there are the usual slew of mammalian hangers-on.

This should be reviewed by a developmental biologist. My recommendation would be mass obsoletion

Reported by: cmungall

Original Ticket: [geneontology/ontology-requests/9067](https://sourceforge.net/p/geneontology/ontology-requests/9067)

I just played around in Protege with making logical defs for all of these post_embryonic terms the genus plus the differentia of part_of post-embryonic development. This seems to have worked ok with respect to classification of the post-embryonic bits. The rest of the classification is done by the new logical defs between cell and anatomy and the core development terms. Does it work for everyone if I just make these logical defs and then let the terms sort themselves out based on UBERON?

We should probably have a dedicated ticket for post-embryonic
I feel bad about you manually adding these I thought we had a separate xp file to be merged in but no time to look right now

I think this ticket is now obsolete because we do create logical defs with the Uberon terms.


"limits.h" problem

A project I'm trying to compile includes limits.h.  It looks like lljvm is intended to support this, but does so incompletely.  Consider the following, in the Docker described in the README (which I appreciate, btw - assuming there's not a heap of other gotchas past this one I'm running into, providing a pre-built docker will have been the easiest way of getting this to run, out of the several c->jvm projects I've tried.)
root@ebb1c6a0a0c2:/test# cat test.c
#include <limits.h>

int main(int argv, char ** argc) {
    return 0;
}
root@ebb1c6a0a0c2:/test# lljvm-cc -o test test.c
In file included from test.c:1:
In file included from /usr/local/lib/lljvm/include/newlib/limits.h:130:
/usr/local/lib/clang/1.1/include/limits.h:35:15: fatal error: 'limits.h' file not found
#include_next <limits.h>
              ^
1 diagnostic generated.

I commented out #include <limits.h> in the project I'm compiling, and it seems like that problem's gone away for now, so...maybe I'm ok on this front.  It may still be relevant for anybody that actually DOES depend on this header.


Feature/day18 mailbox

@gavinbarron @BrianTJackett  Please merge this pull request with the master branch as this sample is ready to be used for Day 18.
@gavinbarron - since you are backing up Brian, can you  please IM me on Teams when you are available so that this is taken care of. Thank you for your help!

@svarukala no need to keep this pull request open now that we've merged to master, correct?  I have a later PR for Day 22 that should include these officially as well.


delete the prerequisites part in the readme

The usage rules of destinationrule should be placed in the document, and users can understand its meaning only if it is placed close to the place where it is used.
The restriction on configuring the port name for the service has been removed.

destinationrule的使用规则应该放在文档中，只有放在靠近使用它的地方用户才能明白其含义
给服务配置port name的限制已经去除了

/lgtm
/approve


Prepare for upcoming react deprecations introduced in 16.3

Suggestion: begin migration to new react lifecycles while retaining backwards compatibility via react-lifecycles-compat
Example: https://www.youtube.com/watch?v=G9S1IghlkCI
Steps

Use new lifecycle methods introduced in react 16.3 in a component that renders react-semantic-ui components.

Expected Result

React does not log errors/warning about upcoming deprecations to the console.

Actual Result

React IS logging errors/warning about upcoming deprecations to the console.

Version
0.79.1
Testcase

@justinobney this is great, could you start a PR for this?

Is this up for grabs? I'm happy to do it.

@joshuaobrien that would be great. I doubt I could get to it for a few weeks.

@joshuaobrien if you need any help let me know.

I'm on it. Will get started on the weekend :)

I would like to start on this, Couple of life cycle methods are marked as UNSAFE in 16.3 and two new methods getDerivedStateFromProps, getSnapshotBeforeUpdate got introduced. @levithomason what exactly do we need to do?

Hi @msrikanth508, I am working on this at the moment. What we need to do is refactor the components that use the deprecated methods so that they no longer use them. Functionality that was in these deprecated lifecycle methods needs to be moved into other lifecycle methods.
My experiences so far is that these changes are not always clean cut. Also, changes to tests are likely required to accommodate the new methods.

Is this still needed I would be happy to hop on it this upcoming weekend and take a gander?

Yep, feel free to pickup 👍

I would love to work on this if it's still needed?

It's still needed. I haven't got around to it.

Hey is this still open to work on @justinobney @joshuaobrien

Hi,
I found out today that the use of the old lifecycle methods might be the cause for some of the open bugs, I'm sure that it's the case for at least the one I referenced above.
To be more precise: If people are using componentDidMount and componentDidReceiveProps in their projects as recommended together with SUI components that still use componentWillMount and componentWillReceiveProps to handle their internal component state (like Dropdown), the internal component state of the MUI components are not getting updated as expected.
Unfortunately I didn't have the time today to fix that in the Dropdown component today, so I'm just putting this here as a note to bump up the issue

componentWillMount()
Docs

[ ] docs/src/components/ComponentDoc/ComponentDoc.js - can be replaced with constructor/didMount()
[ ] docs/src/components/ComponentDoc/ComponentExample/ComponentExample.js- can be replaced with constructor/didMount()
[ ] docs/src/examples/modules/Dropdown/Usage/DropdownExampleRemote.js - replace with constructor()
[ ] docs/src/examples/modules/Search/Types/SearchExampleCategory.js - replace with constructor()
[ ] docs/src/examples/modules/Search/Types/SearchExampleStandard.js - replace with constructor()

Components

[ ] src/modules/Dropdown/Dropdown.js - can be replaced with constructor/didMount()
[ ] src/modules/Search/Search.js  - can be replaced with constructor/didMount()

componentWillUpdate()

[ ]  docs/src/components/CarbonAd/CarbonAdNative.js - replace with didMount()

componentWillReceiveProps()
Docs

[ ] docs/src/components/ComponentDoc/ComponentDoc.js replace with getDerivedStateFromProps()
[ ] docs/src/components/ComponentDoc/ComponentExample/ComponentExample.js replace with getDerivedStateFromProps() & didUpdate()
[ ] docs/src/components/ComponentDoc/ComponentExample/ComponentExampleRenderEditor.js replace with getDerivedStateFromProps()
[ ] docs/src/components/ComponentDoc/ComponentProps/ComponentProps.js replace with getDerivedStateFromProps()
[ ] docs/src/components/ComponentDoc/ComponentSidebar/ComponentSidebarSection.js replace with getDerivedStateFromProps()

Components

[ ] src/addons/TransitionablePortal/TransitionablePortal.js replace with getDerivedStateFromProps()
[ ] src/behaviors/Visibility/Visibility.js replace with getDerivedStateFromProps(), complicated deal with this.firedCallbacks 🤔
[ ] src/modules/Transition/Transition.js replace with getDerivedStateFromProps(), complicated deal with this.nextStatus 🤔
[ ] src/modules/Transition/TransitionGroup.js replace with getDerivedStateFromProps()

Components in single move

[ ] src/lib/AutoControlledComponent.js replace with getDerivedStateFromProps()
[ ] src/modules/Dropdown/Dropdown.js replace with getDerivedStateFromProps()/didUpdate()
[ ] src/modules/Search/Search.js replace with getDerivedStateFromProps()

Needs work

[ ] src/modules/Sticky/Sticky.js - replace with didUpdate(), but move to <EventStack /> before

Absent from here is the replacement of components using findDOMNode by way of passing non forwarded ref components to <Ref /> :) That will also need to be changed

to be returned - this uses findDOMNode, which is also a violation of StrictMode.

@danpantry It's unfixable as there are no alternative, so we are not going to fix. Once the feature from https://github.com/reactjs/rfcs/pull/97 will be released, we will update to it.

@layershifter: Hello, from the future :)
It appears that https://github.com/reactjs/rfcs/pull/97 has been closed and while there are two proposed approaches, it seems unlikely that either will land before Suspense ships.

What does this mean for now ?  I'm a day into development for a small ui application at work now with semantic-ui and I am hitting this deprecation warning.  If this won't be fixed I can't put code in production with warnings in the console popping up.  Will it get fixed eventually ?

@Celludriel The deprecation warnings are nothing to worry about unless you intend to upgrade to a version of React which removes the unsupported lifecycle methods. It doesn't appear that React will be removing them for a long time, but you should be aware that certain components that you're using within Semantic, for the time being, will not support concurrent mode and so may have subtle bugs.
If you're not using concurrent mode, it's probably not an issue.
As for whether or not it will get fixed, I imagine it will, but there problems that prevent the fix from happening right now.

@danpantry
Thanks for the information, I disabled strict mode for now so the warning doesn't pop up since our security department is pretty strict when it comes to warnings in the console.  Even if it's non sensical they should worry about it.
I'll await the future if it will get fixed later on.  Just glad I don't have to switch ui libraries since this one is working just fine for me now

Addressing .findDOMNode() will be a complicated issue as all components should start to use forwardRef().
I am fixing UNSAFE_ warning under #3919, .findDOMNode() will be a next point.

Hi guys. Do you need any help with this?

I believe the rest of these deprecated methods are being resolved in #3956, after which I believe this issue can be closed.

Any more updates on this? This feature is highly anticipated, semantic ui react in its current version throws so many warnings related to this.

Progress is tracked #3919 and a lot of work was already done:

#3956 is remaining to fix lifecycle warnings completely. It's quite complicated as requires tons of refactoring.

Until this will be funded in any way I can't allocate more time for this.

Short update: #3919 was completed and all changes in master should be shipped soon.
Refs handling is a separate thing and work will be tracked under #3819.

Fixes for lifecycles were released in<EMAIL_ADDRESS>🎉


Update to run on Nx ~> 0.6

I am using the Ortex lib to do object detection using the Yolov8 model.
I need to use Nx.vectorize/2 but it is only available from Nx 0.6 onwards.
And Ortex still uses Nx 0.5

Thanks for opening this, bumping the Nx version should be straightforward. I'll update this issue when it's finished.

Updated Nx and other related deps, you should be able to update ortex to 0.1.8 in your project and be good to go!


Remove version: qBittorrent.qBittorrent version 4.6.4

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/qbittorrent/files/qbittorrent-win32/qbittorrent-4.6.4/qbittorrent_4.6.4_x64_setup.exe/download
OK
(Automated message - build 923)

Close with reason: Package still available.;


sys/linux: add netlink seg6 descriptions

sys/linux: add netlink seg6 descriptions

CI build is broken:
https://travis-ci.org/google/syzkaller/jobs/493572050
says that some files are not formatted:
0.01s$ git diff --name-only
executor/defs.h
executor/syscalls.h
sys/linux/socket_netlink_generic_seg6.txt

Please run make generate again and add all changed files to the PR.

Otherwise looks good to me.


Remove indefinite wait for ACM Pods

Use kubectl wait against pods labeled app in (grc,policyreport,multicluster-operators-standalone-subscription) rather than waiting for all pods (so that a flaky non-GRC pods don't block our tests from running).
Also bumps the propagator version and cleans up some Shellcheck identified issues.

/test remaining-required

/test remaining-required

/override ci/prow/test-e2e-grc-framework
Failed as expected at Expected metrics for config_policy_evaluation_seconds_total

/test remaining-required

/retest

/test remaining-required

/retest

/test remaining-required

/test remaining-required

/test remaining-required

/retest

/retest

/retest
I'm not sure why this is failing:
 GRC: [P1][Sev1][policy-grc] Test install Operator When all defaults are used on the subscription test-op-47229 should be created and become compliant [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:459
  STEP: Verifying that the policy policy-test/test-op-47229 is Compliant @ 08/02/24 23:16:39.396
  [FAILED] in [It] - /go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:463 @ 08/02/24 23:18:39.397
  STEP: Cleaning up the operator installation @ 08/02/24 23:18:39.397
  STEP: Verifying that the policy policy-test/cleanup-grcqeoptest-ns is Compliant @ 08/02/24 23:18:41.406
• [FAILED] [123.480 seconds]
GRC: [P1][Sev1][policy-grc] Test install Operator When all defaults are used on the subscription [It] test-op-47229 should be created and become compliant [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:459
  [FAILED] Timed out after 120.001s.
  The function passed to Eventually failed at /go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:897 with:
  Expected
      <string>: NonCompliant
  to equal
      <string>: Compliant
  In [It] at: /go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:463 @ 08/02/24 23:18:39.397

Seems to be either that or this one:
 GRC: [P1][Sev1][policy-grc] Test the compliance history API Creates a policy with a noncompliant and compliant operator policy [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:714
  STEP: Creating the namespace @ 08/02/24 22:08:04.914
  STEP: Verifying that the policy has created the namespace @ 08/02/24 22:08:05.639
  STEP: Verifying that the policy open-cluster-management-global-set/ch-operator-prereq-policy is Compliant @ 08/02/24 22:08:05.639
  STEP: Creating the Policy @ 08/02/24 22:08:06.649
  STEP: Verifying that the policy open-cluster-management-global-set/op-compliance-api is NonCompliant @ 08/02/24 22:08:07.251
  STEP: Verifying that there are NonCompliant compliance events for the Operator parent policy @ 08/02/24 22:08:08.259
  STEP: Patch operator Policy to be Compliant @ 08/02/24 22:08:08.274
  STEP: The Policy should be Compliant on all clusters @ 08/02/24 22:08:09.66
  [FAILED] in [It] - /go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:834 @ 08/02/24 22:09:09.661
  STEP: Deleting the policy-uninstall-gk policy @ 08/02/24 22:09:09.661
  STEP: Deleting Postgres @ 08/02/24 22:09:09.742
  STEP: Deleting the service account in the default namespace @ 08/02/24 22:09:09.894
  STEP: Unsetting the governance-policy-framework ClusterManagementAddOn to use the AddOnDeploymentConfig @ 08/02/24 22:09:09.997
  STEP: Deleting the AddOnDeploymentConfig @ 08/02/24 22:09:10.008
  Cluster local-cluster current compliance message: NonCompliant; the policy spec is valid, the OperatorGroup matches what is required by the policy, the Subscription matches what is required by the policy, no InstallPlans requiring approval were found, ClusterServiceVersion (quay-operator.v3.8.15) - intersecting operatorgroups provide the same apis, there are CRDs present for the operator, no existing operator Deployments, CatalogSource was found
  Cluster managed-1 current compliance message: Compliant; the policy spec is valid, the OperatorGroup matches what is required by the policy, the Subscription matches what is required by the policy, no InstallPlans requiring approval were found, ClusterServiceVersion (quay-operator.v3.8.15) - install strategy completed with no errors, there are CRDs present for the operator, all operator Deployments have their minimum availability, CatalogSource was found
  STEP: Deleting the operator policy @ 08/02/24 22:09:10.013
  STEP: Deleting the namespace policy @ 08/02/24 22:09:10.104
• [FAILED] [65.293 seconds]
GRC: [P1][Sev1][policy-grc] Test the compliance history API [It] Creates a policy with a noncompliant and compliant operator policy [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:714
  [FAILED] Timed out after 60.001s.
  The function passed to Eventually failed at /go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:897 with:
  Expected
      <string>: NonCompliant
  to equal
      <string>: Compliant
  In [It] at: /go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:834 @ 08/02/24 22:09:09.661

/retest

/retest
 GRC: [P1][Sev1][policy-grc] Test install Operator When all defaults are used on the subscription test-op-47229 should be created and become compliant [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:459
  STEP: Verifying that the policy policy-test/test-op-47229 is Compliant @ 08/03/24 02:04:20.113
  [FAILED] in [It] - /go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:463 @ 08/03/24 02:06:20.114
  STEP: Cleaning up the operator installation @ 08/03/24 02:06:20.114
  STEP: Verifying that the policy policy-test/cleanup-grcqeoptest-ns is Compliant @ 08/03/24 02:06:20.686
• [FAILED] [122.202 seconds]
GRC: [P1][Sev1][policy-grc] Test install Operator When all defaults are used on the subscription [It] test-op-47229 should be created and become compliant [BVT]
/go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:459
  [FAILED] Timed out after 120.001s.
  The function passed to Eventually failed at /go/src/github.com/stolostron/governance-policy-framework/test/integration/compliance_history_test.go:897 with:
  Expected
      <string>: NonCompliant
  to equal
      <string>: Compliant
  In [It] at: /go/src/github.com/stolostron/governance-policy-framework/test/integration/policy_install_operator_test.go:463 @ 08/03/24 02:06:20.114

/cherry-pick release-2.11


[Fix #3578] Fix safe navigation counting in Metrics/AbcSize

This cop wasn't correctly counting method calls that happen with the safe navigation operator (x&.y), it has been changed so that they are treated the same as other method calls (like x.y).
Adds a test which checks the score of a method with the safe navigation operator. The test would fail without the change in the cop. I'm not sure if it needs a parallel cop with a regular method call scoring the same thing right next to it...

Before submitting the PR make sure the following are checked:

[x] Wrote [good commit messages][1].
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests are passing.
[x] The new code doesn't generate RuboCop offenses.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.

I'm not sure if it needs a parallel cop with a regular method call scoring the same thing right next to it...

I don't quite understand what you mean here. Apart from this - the change looks good to me.

I don't quite understand what you mean here.

Oops typo. I meant "parallel test". And by that I mean do you also want something like this next to the new test so that we check it counts x.y method calls in exactly the same way:
      it 'treats regular method calls like safe navigation method calls' do
        inspect_source(cop,
                       ['def method_name',
                        '  object.do_something',
                        'end'])
        expect(cop.messages)
          .to eq(['Assignment Branch Condition size for method_name is too ' \
                  'high. [2/0]']) # sqrt(0 + 2*2 + 0) => 2
      end

Oops typo. I meant "parallel test". And by that I mean do you also want something like this next to the new test so that we check it counts x.y method calls in exactly the same way:

Seems redundant to me. The bigger question is whether it's really the best idea to treat safe navigation like regular method calls. Anyways, this will do for now. Just rebase on top of the current master.

Just rebase on top of the current master.
Done.


fix: keep highlight on item with the menu open

Description
This adds some logic to the ProjectTree and TreeItem components to let them keep track of which, if any, tree item is selected. This lets us visually "lock" the highlight in place when we have a menu open; if any menu is open, that one will be shown as highlighted. If not, the highlight will be on whichever item is actively shown.
Task Item
closes #4810
Screenshots
(note: my cursor is over on another item during this screenshot)

I have a try on this, seems on context menu open, current item turn out to be 'selected' style (blue) , not 'hover' style (gray) ,

Is it by design ?

It's possible I misunderstood the issue, and on reading it again, that would make more sense (to keep the gray highlight in place, not the blue one which shows which one is active). I'll change this to do that instead.

A screenshot of the new behavior:

The gray highlight now stays in place while the menu is out, even when the cursor moves.


Automatically remove invisible characters in the Markdown editor

Is your feature request related to a problem? Please describe.
I made a website for my mom, and she copied some text from Word into the Markdown editor, and managed to add a line separator into the text.
This in turn broke Jekyll.
Is there a way to remove invisible characters automatically? If not, could this be added?
Describe the solution you'd like
Automatically remove invisible characters in the Markdown editor.
Describe alternatives you've considered
Automatically removing those characters with a Jekyll plugin. Though I'd prefer it if they weren't in the source in the first place.

Hi @TheOddler, I believe you can sanitize fields using the preSave event.
See https://www.netlifycms.org/docs/beta-features/#registering-to-cms-events
Closing. Please comment if that doesn't solve your use case

That worked! I'm now removing all whitespace except space and newline in the preSave event for my body! Works like a charm.
Thanks!


UI: Fix change offering type

Description
This PR fixes the service offering wizard
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

@blueorangutan ui

@blueorangutan ui

@blueorangutan ui

@blueorangutan ui

@blueorangutan ui

@nvazquez a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6135 (SL-JID-1267)


verify buildId in testBreadCrumb

Signed-off-by: OscarQQ<EMAIL_ADDRESS>

In the page of testPerPlatforms and deepHistory, we render the testBreadCrumb before we set the value of buildId. (buildId is set up in componentDidMount) So /api/getParents?id=undefined will be called, which gives an error in the back end.
Error: Argument passed in must be a single String of 12 bytes or a string of 24 hex characters
at new ObjectID (path/TestResultSummaryService/node_modules/bson/lib/bson/objectid.js:59:11)


SMS Code Autofill in iOS Apps

When receiving codes in iOS they are not populating from the message. This feature enables the user:

Less mistakes when entering codes
Maintain feature parody in iOS

I don't have any SIM for my test iOS device so this isn't something I've been able to play with. According to the description of the Flutter 'sms_autofill' package:

For iOS, this package is not needed as the SMS autofill is provided by default, but not for Android, that's where this package is useful.

So there must just be some annotation missing for linking the OTP field to incoming OTP SMS messages. That plugin comes with field widgets though so maybe just switching to that will make it work. I'm not able to test it though—maybe a good first issue for a contributor on iPhone :-)

Looks like it can't be done right now on Android with Twilio Verify: https://github.com/supabase/auth/issues/1235
And it sounds like there's no setup to be done for helping make it work on iOS—iOS should pop up the code as pasteable by the user if it automagically detects that that's a good idea. I feel like I've seen it happen on people's screens before with SquadQuest. Maybe the way the current OTP text field is set up doesn't make it work consistently though and using a more dedicated 6-digit pin field like the one sms_autofill comes with would help iOS know to do it

@MooseQuest see if this is improved by 71f2abf3bf2f43b2617454845a2a4ae9c6dace57—you'll have to wait for v1.9.1 to hit the app store later today

This can't work on Android right now because Twilio Verify only lets you select from a small set of preexisting templates for the verification text messages—and for some reason none of them match the format Android requires

Verified that it works on iOS 17.6.1

Awesome, closing


digikam: improvements

Now usable in non kde desktop environments.
Build a immutable sycoca database and use
wrappers to tie programs to this
database and avoid interference from the
outside by specifying a fixed KDELIBS
and fixed/empty XDG_DATA_DIRS.
Added missing dependencies to syscoca
database so that the program is complete.
Added all build time optional packages.
Kipi-plugins now properly detected. Added
almost all optional dependencies so that
almost all plugins are usable.
Now with vlc phonon backend for video playback.
Now with ffmpeg thumbnailer for video items
thumbnail creation.
Now run without any error log.

Tests:

Ran most features of the standard program. Everything
work perfectly without error logs.
Ran some of the kipi plugins. Work fine there too.
Ran face detection and fingerprint generation
successfully.
Oxygen icons are now displayed properly.
Ran other wrapped executable successfully.

@goibhniu @viric @urkud

I just tested the build at work using nix on top of ubuntu 14.04.
The application runs same as on top of nixos.
Only glitch/impurity it flushed out is the following:
building path(s) ‘/nix/store/a9rfxa0hryy9zsa2zdadhgk3i6a30hf2-digikam-sycoca-4.12.0’
kbuildsycoca4 running...
kbuildsycoca4(373)/kdecore (services) KServicePrivate::init: The desktop entry file  "/usr/share/applications/unity-scope-gdrive.desktop"  has Type= "Application"  but no Exec line

kbuildsycoca4(373) KBuildServiceFactory::createEntry: Invalid Service :  "/usr/share/applications/unity-scope-gdrive.desktop"
kbuildsycoca4(373)/kdecore (services) KServicePrivate::init: The desktop entry file  "/usr/share/applications/unity-lens-photos.desktop"  has Type= "Application"  but no Exec line

kbuildsycoca4(373) KBuildServiceFactory::createEntry: Invalid Service :  "/usr/share/applications/unity-lens-photos.desktop"
kbuildsycoca4(373)/kdecore (services) KServicePrivate::init: The desktop entry file  "/usr/share/applications/evolution-data-server-uoa.desktop"  has Type= "Application"  but no Exec line

kbuildsycoca4(373) KBuildServiceFactory::createEntry: Invalid Service :  "/usr/share/applications/evolution-data-server-uoa.desktop"
building path(s) ‘/nix/store/8lx2g1w4g5sm2ka94wzq7jpcq0q7zc0s-digikam-4.12.0’
building path(s) ‘/nix/store/c02ar6kqs9b3yhc51frpa3v4hadcqd21-user-environment’

We should definitly patch this kbuildsycoca4 program  so that it does not search in /usr/share unless this directory is part of KDELIBS.

As a general strategy, emptying $XDG_DATA_DIRS doesn't seem good. We use it on quite a few places, moreover the freedesktop standard says:

If $XDG_DATA_DIRS is either not set or empty, a value equal to /usr/local/share/:/usr/share/ should be used.

... so to get purity we should better set it to something fixed (and nixos already defines it by default, but there you typically don't have the /usr/{local,share} paths anyway).

I did some testing and it is possible to remove the wrapper's XDG_DATA_DIRS="" and digikam would run successfully. What I did like with the wrapper's nullification of XDG_DATA_DIRS is
that it would guarantee the soft would run the same way in one context or another. It also
removed a free variable when trying to debug what goes wrong with KDELIBS env.
The  XDG_DATA_DIRS="" from the sycoca build merely guarantee to get the same build in
non pure nix-shell as you get in pure (as XDG_DATA_DIRS is not set in pure env).
Specifying only XDG_DATA_DIRS in the sycoca build result in the following runtime error:
digikam(13183)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "PhononBackend"  not found
digikam(13183)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "KIPI/Plugin"  not found
digikam(13183)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "Digikam/ImagePlugin"  not found

Specifying only XDG_DATA_DIRS in the wrapper and build result in the following runtime error:
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/srgb-d65.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/srgb-d65.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/widegamut.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/prophoto.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/srgb-d65.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/srgb-d65.icm" cannot be found. Check your installation.
digikam(14217)/digikam (core): The bundled profile "libkdcraw/profiles/srgb-d65.icm" cannot be found. Check your installation.
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no objectName ) to  Phonon::AudioOutput ( no objectName ).
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
WARNING: Phonon::createPath: Cannot connect  Phonon::MediaObject ( no objectName ) to  Phonon::VideoWidget ( no objectName ).
WARNING: bool Phonon::FactoryPrivate::createBackend() phonon backend plugin could not be loaded
digikam(14217)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "KIPI/Plugin"  not found
digikam(14217)/kdecore (trader) KServiceTypeTrader::defaultOffers: KServiceTypeTrader: serviceType  "Digikam/ImagePlugin"  not found
digikam(14217)/digikam (core) Digikam::DNotificationWrapper: parent is null

Specifying both XDG_DATA_DIRS at sycoca build to same location (/share for xdg) seem fine.
However, this is redundant information and as such complicates debug.

Also specifying both to same locations at both place also work fine. Same redundancy argument hold.

Could be improve with #10308.

I think someone had changes in the pipe to make kde apps able to run without kde, in a more generic way. @ttuegel I think it was you?

@cpages I have nothing for KDE 4.

Hi @cpages, yes I drew my inspiration from @ttuegel work (immutable syscoca db). However,
to generalize to all kde4 packages in the same way as he did would take far more build time,
test time and nix fu that I actually can offer (which would be really great to do by the way)
so I tried to limit damage to this single package so as to avoid breaking any other.
One thing that this brings tough is that it proves the immutable sycoca database technique
is applicable to kde4 pakages (this is most likely one of the most complex kde4 package) as
well if anyone is ready to take the time required and as a  bonus (which is what I needed in
the first place), a fully functional digikam application.

One thing that this brings tough is that it proves the immutable sycoca database technique
is applicable to kde4 pakages (this is most likely one of the most complex kde4 package) as
well if anyone is ready to take the time required and as a bonus (which is what I needed in
the first place), a fully functional digikam application.

I actually had to abandon the immutable-sycoca part of my project (for now). It seems most applications want to update the sycoca database at startup; maybe because the timestamp is so far in the past? This may not be a problem for KDE 4, YMMV.

It seems most applications want to update the sycoca database at startup

That shouldn't be hard to patch out, should it? AFAIK it's kded who's responsible for keeping it up to date.

@vcunat It's probably not hard to patch out, but it also doesn't matter as much for KDE 5. In KDE 4, the sycoca database tracks available plugins and services; there are many more of the former than the latter. In KDE 5, it only seems to track services; plugins are resolved by looking at QT_PLUGIN_PATH (automated through a setupHook). As long as the required services are in propagatedUserEnvPkgs and kbuildsycoca5 is available (again, automated through a setupHook), everything will work at runtime. Yes, immutable-sycoca would be ideal, but as long as everything actually works, it's not a priority for me.

I see.

@ttuegel: When launched from cli, the program indeed report an error in attempting at creating the
sycoca db when no other kde4 program have been started on the machine (i.e: no pre-existing kdeinit4 process). The error is:
kbuildsycoca4 running...
kbuildsycoca4: ERROR creating database '/nix/store/8b317fl841x6wfws9pzdy6wdlgdaymzp-digikam-sycoca-4.12.0/var/lib/kdesycoca/digikam-4.12.0.sycoca'! Insufficient permissions in target directory.

but seem harmless.
When I quit the application and start it again, I get no error.
I dug a little deeper at first and found out that this is an error thrown by the kdeinit4: kded4 [kdeinit] service launched by kdeinit4. This can be observed by launching the application
in the following way:
kdeinit4 --no-kded +digikam

which prevent the launch of the kded4 service.
I tried to patch the kded service in the following way:
diff --git a/kded/kded.cpp b/kded/kded.cpp
index e76b614..510bd07 100644
--- a/kded/kded.cpp
+++ b/kded/kded.cpp
@@ -84,6 +84,10 @@ extern QDBUS_EXPORT void qDBusAddSpyHook(void (*)(const QDBusMessage&));

 static void runBuildSycoca(QObject *callBackObj=0, const char *callBackSlot=0, const char *callBackErrorSlot=0)
 {
+   const bool skipSycocaBuild = true;
+   if (skipSycocaBuild)
+      return;
+
    const QString exe = KStandardDirs::findExe(KBUILDSYCOCA_EXENAME);
    Q_ASSERT(!exe.isEmpty());
    QStringList args;

to no avail (had the same problem).

Rebased on top of latest master branch.
Now that kde applications for kde4 are no longer available, libkface and libkgeomap dependencies
could no longer be retrieved. Made those two optional via flags. When requested and
dependencies null, provide proper flags to cmake so that they are built by the digikam package.
Built and used. Everything still work fine.

@jraygauthier are you happy to merge ? There are still some possible improvements but it seems to be working and better than before so that could be done in another round of development.

@zimbatm, I think it would be nice if it was merged now and as you suggest improve it further with
other round of dev.

Thanks a lot :)


Generating with mbart-large-cc25: which special tokens to use?

I am trying to figure out how to use the posted cc25 model for generation.
When I port the model to huggingface/transformers, I can perfectly copy the state dict. However, when I try to translate, using the same special token setup as mbart-large-en-ro, my english-romanian translator just generates english text.
Is this special tokens setup correct:
english/src: end src sentence with [lang_id, eos], so [250004, 2]
I tried to start decoding with the romanian langid, 250020, and got back english.
If I start decoding without a prefix token, I get back gibberish.
Alternatively, if anyone has a working fairseq-generate command that uses cc25 to generate (for any language pair), I could get to the bottom of which special tokens to use by setting breakpoints.
here is a broken attempt at a fairseq-generate command, the solutions proposed in #1758 do not seem to fix it.
Thanks in advance!

@myleott I am trying to use the mBART generative interface to generated output in the Hindi language (from English). I fine-tuning the model with English-Hindi parallel dataset and results are good.
For my ongoing work, what I want is: "can we generate the Hindi output such that the order of sentences should not be change after generation? (i.e., English sentence order and generated Hindi sentence order should be same, there should not be any shuffling)" How can we achieve the same? Waiting for your response. Thank you!


Invalid Field Name Error Tied to Missing Package

Hello,
When creating a rule where I used the 'pe' module to review the number of signatures in a file, I had Yara throw the following message 'invalid field name "number_of_signatures"'. My rule was working on other machines, but not for the one I was developing on which I found odd. After a bit of troubleshooting I found that I needed to install the package openssl-devel on my CentOS box (libssl-dev for Ubuntu) and recompile and install Yara. Once I did this, my rule worked as desired.
I found it strange that I was able to successfully compile and install Yara without this package, which seems necessary in order to use some of the features of the pe module.
I'd like to suggest looking into a way to make it more obvious to a user they might be missing this  requirement when installing Yara.
Thanks,
Jason

It seems reasonable to dump out what will and won't be built after configure finishes detecting things. In your particular case it isn't finding OpenSSL properly.

I agree with that too

Rock on :)

Interesting - I get this error using the prebuilt 3.5.0 package for Windows. (Python 2.7)

./configure now warns you when OpenSSL wasn't found in your system.


Toss logo

Yeah, probably just me who will ever use it, in profile, but still…
toss (Wikidata) is somewhat like… South Korean edition of Venmo in US. They have toss.me as user-configurable URL to transfer money.
Have SVG here with the logo AND the wordmark. Shouldn't be that hard to remove the wordmark, I think.

It’s live now! Any profile item that includes a toss.me URL (either directly or in Markdown) should display the correct icon as of now.