needs update to new module-based installation

Hi there,
I will shortly be merging a PR to package git-deps as a Python module.  As a result the installation process has changed slightly, e.g.

Some files are now in different places.
The installation workflow is based on Python's popular setuptools framework.

It would be great if we could collaborate to get this repo working with the new approach :-)

@aspiers , sure, I will.
Although I am not sure if this docker project still makes sense (I created it to work around installation problems on ubuntu, which are not there any more, I hope). But it won't hurt, and it is always good to have a working automatic setup.

Thanks!  I think it probably does still make sense, because for several Linux distributions it can be challenging to find the right versions of packages for libgit2 and pygit2 which match.  And in the future it is possible that git-deps might also get more fussy about which versions of pygit2 it works with.

@aspiers , tried it just now, with python's docker image as base. But pip install git-deps is not working yet. It will, when the release is out, right?

It should work now.

@aspiers , thanks.
On a clean system, the setup still does not work as documented in your README:
    gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/usr/local/include -I/usr/local/include/python3.6m -c src/blob.c -o build/temp.linux-x86_64-3.6/src/blob.o
    In file included from src/blob.h:34:0,
                     from src/blob.c:30:
    src/types.h:36:2: error: #error You need a compatible libgit2 version (v0.27.x)
     #error You need a compatible libgit2 version (v0.27.x)
      ^
    src/types.h:82:5: error: unknown type name ‘git_worktree’
         git_worktree *worktree;
         ^
    error: command 'gcc' failed with exit status 1

Is libgit2 v.0.27.x required?

No, currently only pygit >= 0.24.0 is required but did you follow the link in INSTALL.md to http://www.pygit2.org/install.html#version-numbers ?

i.e. sounds to me like you are trying to install a pygit2 which is too new for your libgit2.

@aspiers, no, I just tried to follow your steps under https://github.com/aspiers/git-deps/blob/master/INSTALL.md#option-2-install-libgit2-from-os-packages-and-git-deps--pygit2-as-python-modules
I will try another option.


nixos/picom: add experimentalBackends option

Motivation for this change
This option is only available as a command-line flag and not from the config file, that is services.picom.settings. Therefore it is more important that it gets its own option.
One reason one might need this set is that blur methods other than kernel do not work with the old backends, see yshui/picom#464.
For reference, the home-manager picom module exposes this option too.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

@aanderse It does not look like the maintainers are available.

@axelf4 thanks for the PR and ping :tada:


Add and delete row

Resolves #98

Codecov Report
Attention: Patch coverage is 60.00000% with 114 lines in your changes missing coverage. Please review.

Project coverage is 95.98%. Comparing base (003b326) to head (1a0abe6).

Files with missing lines
Patch %
Lines

src/components/Table/hooks/useAddData.ts
32.55%
29 Missing :warning:

...components/TableAddRowEditor/TableAddRowEditor.tsx
28.57%
25 Missing :warning:

...components/editors/AddDataEditor/AddDataEditor.tsx
39.13%
14 Missing :warning:

...ents/editors/DeleteDataEditor/DeleteDataEditor.tsx
39.13%
14 Missing :warning:

src/components/Table/hooks/useDeleteData.ts
47.36%
9 Missing and 1 partial :warning:

src/hooks/useUpdateRow.ts
50.00%
8 Missing :warning:

...ents/TableDeleteRowEditor/TableDeleteRowEditor.tsx
46.15%
7 Missing :warning:

...e/components/TableActionsCell/TableActionsCell.tsx
83.33%
2 Missing :warning:

src/components/Table/Table.tsx
88.88%
1 Missing :warning:

.../components/Table/components/TableRow/TableRow.tsx
83.33%
0 Missing and 1 partial :warning:

... and 3 more

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #184      +/-   ##
==========================================
- Coverage   99.78%   95.98%   -3.80%
==========================================
  Files         174      189      +15
  Lines        2733     2990     +257
  Branches      635      686      +51
==========================================
+ Hits         2727     2870     +143
- Misses          6      118     +112
- Partials        0        2       +2

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


How to stitch microscope images with python.

i have 17x17 microscope images. i want to stitch all together but not getting how to do that. i installed ITKMontage with pip but after that not able to do anything.

If you need to do this just once, you are better off using end-user software such as DREAM.3D or Image Stitching Plugin for Fiji.
If you insist on using ITKMontage directly, you should construct TileConfiguration.txt similarly to the ones in test inputs (e.g. S200) and then use the example script to invoke the code.


Upgrade to Dart 2.12.0

Build fails probably due to infrastructure problem in GitHub Actions:
https://github.com/actions/virtual-environments/issues/2179#issuecomment-841266909


cherry pick specific commit of Envoy to 1.2 release

We would like to see the possibility of having this PR (envoyproxy/envoy#7019)  available in 1.2 Proxy. Are proxy changes to 1.2 release acceptable? If yes, what is the way we can cherry pick that PR ?

Did we do this? do we still need it?

We can close this
On Wed, 2 Oct 2019, 03:57 John Howard<EMAIL_ADDRESS>wrote:

Did we do this? do we still need it?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/15717?email_source=notifications&email_token=AEDINKBKVRHJUJ32CX6YSELQMPFFPA5CNFSM4IF55Y3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAC6TMA#issuecomment-537258416,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEDINKERE3K2SREQRSANMATQMPFFPANCNFSM4IF55Y3A
.


Logging Improvements

Don't log elsaticsearch connection established on INFO level
as that displays to the user every time he/she runs a query.
Show it only on debug level
Remove "Could not retrieve value" logging as it logs too many
lines, even for simple queries such as "cibyl --jobs". In addition,
it's not very useful information for developer or a user
Show always from where a certain information got pulled and how
much time it took. Show which method was used only if debugging
is on as it's not something that is useful for most users.

Looks good.


Test "no_overloading.invalid.mj" should be valid

The testcase no_overloading.invalid.mj looks valid, maybe the name for the 3rd method was meant to be 'bla'?

You're correct


Can't build sqlite3 3.0.10 on OS X with Node 4.0.0

Build log: https://gist.github.com/edbrannin/342fb19b0aa10e926301
First error:
  c++ '-DNODE_GYP_MODULE_NAME=node_sqlite3' '-D_DARWIN_USE_64_BIT_INODE=1' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DSQLITE_THREADSAFE=1' '-DSQLITE_ENABLE_FTS3' '-DSQLITE_ENABLE_RTREE' '-DBUILDING_NODE_EXTENSION' '-DNDEBUG' -I/Users/ed/.node-gyp/4.0.0/include/node -I/Users/ed/.node-gyp/4.0.0/src -I/Users/ed/.node-gyp/4.0.0/deps/uv/include -I/Users/ed/.node-gyp/4.0.0/deps/v8/include -I../node_modules/nan -I./Release/obj/gen/sqlite-autoconf-3081101  -O3 -mmacosx-version-min=10.5 -arch x86_64 -Wall -Wendif-labels -W -Wno-unused-parameter -std=gnu++0x -fno-rtti -fno-exceptions -fvisibility-inlines-hidden -fno-threadsafe-statics -fno-strict-aliasing -MMD -MF ./Release/.deps/Release/obj.target/node_sqlite3/src/database.o.d.raw -I/Users/ed/Developer/include -c -o Release/obj.target/node_sqlite3/src/database.o ../src/database.cc
In file included from ../src/database.cc:5:
In file included from ../src/database.h:11:
../node_modules/nan/nan.h:261:25: error: redefinition of '_NanEnsureLocal'
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Local<T> val) {
                        ^
../node_modules/nan/nan.h:256:25: note: previous definition is here
NAN_INLINE v8::Local<T> _NanEnsureLocal(v8::Handle<T> val) {
                        ^

Can you try running npm cache clean and then re-installing again?

Oh, also you need v3.1.0 for 4.x support.

Whoops!  I didn't notice the 3.1.0 release when I was working on this.  Thanks, it's working now!


Compress resulting qcow2 image

Summary
Compress resulting image to make things lighter

Related issue :

Let's try it, looks good so far!

Ideally the build should be done as part of the pull request but that would imply that anyone sending an PR could trigger the spawning of a VM and do something "wrong"

I assumed forked repos don't get access to secrets (i.e. OIDC tokens) and therefore cannot trigger automatic builds from GitHub?

Bummer, it failed and we have no logs of the failure and the VM is gone 😫


When creating a new overlay network, only introspect nodes that are ready (Online)

Fixes #19

Will re-open cleanly, without other change dependencies


Intermittent test failures in test/mongo/connection_test.exs

It seems there are intermittent failures in the test/mongo/connection_test.exs file, for the "auth wrong" scenario on line 31.
As an example travis run:
https://travis-ci.org/ericmj/mongodb/jobs/141147103
Is it possible this is the kind of message ordering issue that should be handled using special process tests, as described here:
http://blog.carbonfive.com/2016/06/28/special-processes-in-otp/ ?

I don't know. Could be just be a timeout issue where travis is low. Can you reproduce this locally?


Updating config for Lenovo Legion 16achg6

Description of changes
In my initial submission there was a problem with X11 in hybrid mode: it failed to detect an external display. As a result I used Wayland.
A few days ago I found a way to overcome this limitation. Current version works fine both for X11 as well as Wayland.
Things done

[x] Tested the changes in your own NixOS Configuration
[x] Tested the changes end-to-end by using your fork of nixos-hardware and
importing it via <nixos-hardware> or Flake input

I confirm I tested the changes both by modifying my local config.nix and by referencing my cloned nixos-hardware repository in my flake.nix.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/what-else-can-i-try-to-make-my-optimus-nvidia-card-work-well-with-x11/36958/9

@mergify rebase


Retry rename on lock induced failures

Due to file locking on Windows it is possible for an os.Rename to fail if the files or directories are being used elsewhere.
This PR simply suggests retrying the rename again similar to how we handle the equivalent problem in os.Remove.
Fix #16427
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

If this PR succeeds at solving the problem we could/should include it in 1.15

Codecov Report

Merging #16435 (62d994f) into main (0393a57) will increase coverage by 1.18%.
The diff coverage is 46.88%.

:exclamation: Current head 62d994f differs from pull request most recent head eb9931e. Consider uploading reports for the commit eb9931e to get more accurate results

@@            Coverage Diff             @@
##             main   #16435      +/-   ##
==========================================
+ Coverage   44.24%   45.42%   +1.18%
==========================================
  Files         695      717      +22
  Lines       82341    84177    +1836
==========================================
+ Hits        36429    38237    +1808
+ Misses      40014    39791     -223
- Partials     5898     6149     +251

Impacted Files
Coverage Δ

cmd/convert.go
0.00% <0.00%> (ø)

cmd/dump.go
0.91% <0.00%> (ø)

cmd/dump_repo.go
0.00% <0.00%> (ø)

cmd/generate.go
0.00% <0.00%> (ø)

cmd/hook.go
0.00% <0.00%> (ø)

cmd/mailer.go
0.00% <0.00%> (ø)

cmd/manager.go
0.00% <0.00%> (ø)

cmd/migrate.go
0.00% <0.00%> (ø)

cmd/migrate_storage.go
0.00% <0.00%> (ø)

cmd/restore_repo.go
0.00% <0.00%> (ø)

... and 314 more

Continue to review full report at Codecov.

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


[BUG]: Python client sqlite issue

Refs: #1206
Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

Conditional import of sqlite for python client

Test plan
How are these changes tested?

[x] Tests pass locally with pytest for python

Additional test in older disto (debian buster) was run:
pip install chromadb-client
root@c26a0fadfcdc:~# python
Python 3.10.12 (main, Jun 13 2023, 12:02:28) [GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlite3
>>> print(sqlite3.sqlite_version_info)
(3, 27, 2)
>>> import chromadb
>>>

Documentation Changes
N/A

Thanks!


Add docs & examples for Flutter

I am not sure if this is the right place for this issue but docs & examples for Flutter are definitely needed. For example, in the following page, there are examples for ios, android and web but there is nothing for Flutter.
https://firebase.google.com/docs/emulator-suite
Thank you for the awesome work.

@deadsoul44 thanks for the feedback!  The best place to file this would be here:
https://github.com/FirebaseExtended/flutterfire
FlutterFire has a brand new docs site and a page on using the emulator sounds like a good idea to me.  Right now we're not adding Flutter snippets to the main Firebase docs, although we do hear you and we know that people want it!


[Request] OpenComputers functionality for Reactor Logic Adapter

Having used BigReactors for quite a while, and having several programs in OpenComputers that revolve around the mod, I was... disappointed to see that the Mekanism reactor works with ComputerCraft and not OpenComputers.
This is my formal request for OC functionality so I can begin to port my reactor software over.  I love Mekanism reactors since there's much more depth to fuelling and maintaining them than just loluraniumfordays.

Done :)

I can't find a commit fixing this.
I am using last release of Mekanism + OpenComputers + ComputerCraft (for using other mods api for CC in OC). But I can't see any component of reactor in my OC setup.
Can you please describe the mod version and the setup required to control mekanism's fusion reactor from OC?


1.20.1 version?

it doesn't work for me on that version 😞

1.20.1 is not supported by TimeLib, and there are no plans of porting it backwards.

wait, why? that’s the only version i use, and i don’t use any newer versions than that one

why? please tell me!!

Because it would require massive code changes to port the most recent TimeLib version over (as well as testing in all scenarios to make sure it works), and releasing an older version of TimeLib after a newer one is already available would mess with the changelogs.
Is there a reason you can't use 1.20.3+?


can you provide objects365 pretrain model

💡 Your Question
hello , any guys train objects365 model ?
Versions
No response

O365 pretraining was part of training process of YoloNAS but it is not going to be released as getting perfect results on this dataset was never an end goal. You are more than welcome to fine-tune YoloNAS on O365 by yourself.


Support for trackpad

The Valve Index controllers have a trackpad, which is used in games like HL:Alyx to select a weapon. It would be nice if such a feature was supported by opengloves, so that you don't have to setup a gesture to simulate it.

You can use the steamvr bindings to configure the index controller inputs for half life alyx.
Alternatively you can switch to using the lucidgloves device which has this appropriate functionality.


[MINOR][YARN] Add YARN-specific credential providers in debug logging message

What changes were proposed in this pull request?
This PR adds a debugging log for YARN-specific credential providers which is loaded by service loader mechanism.
It took me a while to debug if it's actually loaded or not. I had to explicitly set the deprecated configuration and check if that's actually being loaded.
How was this patch tested?
The change scope is manually tested. Logs are like:
Using the following builtin delegation token providers: hadoopfs, hive, hbase.
Using the following YARN-specific credential providers: yarn-test.

cc @jerryshao, not a big deal but I thought it's useful.

Test build #91327 has started for PR 21466 at commit 5a2b7c7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3719/
Test PASSed.

Test build #91327 has finished for PR 21466 at commit 5a2b7c7.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

retest this please

Merged build finished. Test FAILed.

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

Test build #91329 has started for PR 21466 at commit 5a2b7c7.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3721/
Test PASSed.

Test build #91333 has started for PR 21466 at commit 4a63f22.

Test build #91334 has started for PR 21466 at commit 046d433.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3725/
Test PASSed.

Test build #91335 has started for PR 21466 at commit 210ac14.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3726/
Test PASSed.

Test build #91329 has finished for PR 21466 at commit 5a2b7c7.

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

Merged build finished. Test FAILed.

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

Jenkins, retest this please.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3730/
Test PASSed.

Merged build finished. Test PASSed.

Test build #91340 has started for PR 21466 at commit 210ac14.

Test build #91334 has finished for PR 21466 at commit 046d433.

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

Merged build finished. Test PASSed.

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

Test build #91333 has finished for PR 21466 at commit 4a63f22.

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

Merged build finished. Test PASSed.

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

Test build #91335 has finished for PR 21466 at commit 210ac14.

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

Merged build finished. Test PASSed.

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

Test build #91340 has finished for PR 21466 at commit 210ac14.

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

Merged build finished. Test PASSed.

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

Thanks, @jerryshao.


API Gateway response headers

API Gateway lets you set some response headers in lambda. Would love to see support for this.

It looks like you can map items in the integration response to headers. We should think about Lambda returning an object like this and having API gateway parse it -
{
  "headers": {

  },
  "body": {

  }
}

Lambdafai now supports a limited set of headers -
Content-Type
Access-Control-Allow-Origin
Access-Control-Allow-Headers
Access-Control-Allow-Methods
Access-Control-Max-Age
Cache-Control

Which can be set like this -
res.set('Content-Type', 'text/html'


ENH: Use macos-13 now to avoid disruption when macos-12 is retired

The macOS 12 runner image will be removed by December 3rd, 2024. To raise awareness of the upcoming removal, jobs using macOS 12 will temporarily fail during scheduled time periods defined below:
November 4, 9:00 AM - 7:00 PM EST
November 11, 9:00 AM - 7:00 PM EST
November 18, 9:00 AM - 7:00 PM EST
November 25, 9:00 AM - 7:00 PM EST
What you need to do
Jobs using the macos-12 YAML workflow label should be updated to macos-15, macos-14, macos-13, or macos-latest. You can always get up-to-date information on our tools by reading about the software in the runner images repository. Please contact GitHub Support if you run into any problems or need help.
(cherry picked from commit ed0534498647851b0ef330d25a94b939e9fe3743)

Related to https://github.com/InsightSoftwareConsortium/ITKModuleTemplate/issues/167#issuecomment-2483533529


Couldn't get it to build under Swift Package Manager

Fixing 2 issues:

Bad syntax in Package.swift, causing

Packages/CleanroomLogger.git/Package.swift:5:1: error: unexpected ',' separator
)
^
Can't parse Package.swift manifest file because it contains invalid format. Fix Package.swift file format and try again.

Unexpected placement of Unit tests, vs. what is expected by SPM, causing:

Cloning https://github.com/maximveksler/CleanroomLogger.git
HEAD is now at deb26c0 Fixing package manager breaking the build
Resolved version: 5.0.2
error: the package has an unsupported layout, unexpected source file(s) found: /Users/maximveksler/Project/[REDACTED]/Collection/Packages/CleanroomLogger-5.0.2/Tests/LogSeverityTests.swift, /Users/maximveksler/Project/[REDACTED]/Collection/Packages/CleanroomLogger-5.0.2/Tests/LoggingTests.swift

Thanks a lot for the heads-up on these problems.

Maxim,
I didn't merge this in directly but I made the changes necessary to satisfy both Swift Package Manager and Xcode. I just released it as version 5.0.2. Thanks again for your pull request!
E.


Silverfin panel - auto-refresh when changing details

Describe the bug
When changing your default firm ID or updating the config.json of a template, this update is not automatically reflected in the sidebar panel.
To Reproduce
Steps to reproduce the behavior:

Go to the Silverfin sidebar
Go to the 'Firms' section of the sidebar
Under 'Authorized firm IDs', your currently set default firm has an 'ACTIVE' label next to it.
Press CTRL + SHIFT + p to open the VS Code command panel
Select the command 'Silverfin: set firm ID'
Set a different firm ID than your current default one.
If you go back to the Silverfin panel, the 'ACTIVE' label is still set on the old default firm, while on the background you already changed your default firm.
This 'ACTIVE' label is only updated on a full-restart of VS Code.

Same issue applies for any direct update done in the config.json of the template
Expected behavior
The information in the sidebar should always match your current configuration.
Desktop & CLI (please complete the following information):

OS: WSL2
CLI version (run silverfin --version): 1.9.1

I think point 8 is not completely correct. The ACTIVE label is (was) updated when you switched tabs in the editor.
Now I made an update that it (the firm section) should be reloaded after changing the default firm id using the command
Also, now every section in the sidebar should be reloaded when the file opened get's saved (as mentioned earlier, panels were only rendered when switching tabs / changing the 'active text editor'). This should address your issue with changes to config.json
@Woetfin you should be able to check this in v1.8.5


another reboot error

there was another reboot error on coordinate M4W6+7P9 (google coordinate)

this is 50.695687,10.111812 in geo coords

same error as #61


Supplemental Params: Az CLI implementation

Azure CLI PR: https://github.com/Azure/azure-cli/pull/27527

This will be released on 11/14: https://github.com/Azure/azure-cli/milestone/135

I have the Azure CLI v2.54.0 and the problem is still there. The inline parameters are being ignored.

@JCPuerto please could you open a new issue and provide specific details on how you're invoking Azure CLI, as well as the Bicep/Bicepparam files if relevant?

https://github.com/Azure/bicep/issues/12647 I couldn't find an issue opened from you JCPuerto... it looks like if you omit the param from the bicepparam file the inline override fails to override the default value in the bicep file. I worked around this issue but just defaulting it to an empty string in the bicepparam and now it's working

Hi @adameska,
I've been following this bug for a while now. Here are the tickets that got me to this one:
• https://github.com/Azure/bicep/issues/11305
• https://github.com/Azure/bicep/issues/11042
• https://github.com/Azure/bicep/issues/11445
They were all closed but the issue still there. The in-line parameters don't work with .bicepparam files. They used to work perfectly with .json files.
This used to work:

But regardless of the order of the parameters, it always try to take the ones in the .bicepparam file:

And since they are empty, the deployments fails but it should work since they are specified in-line.
Thank you!

@JCPuerto please open a new issue!
Does this work if you supply the -p flag multiple times? E.g.
az deployment sub create `
   ...
  -p environment=$env `
  -p productName=$product `
  -p $parametersFile `
  ...

@JCPuerto please open a new issue in the Azure CLI repo (https://github.com/Azure/azure-cli)
Does this work if you supply the -p flag multiple times? E.g.
az deployment sub create `
   ...
  -p environment=$env `
  -p productName=$product `
  -p $parametersFile `
  ...

Hi @anthony-c-martin, adding multiple -p flags worked! I didn't know we could use them like that. I won't open a new ticket for now.
Thank you!

I won't open a new ticket for now.

You should because passing multiple key-value pairs to single -p/--parameters is documented feature: Parameters may be supplied from a file using the @{path} syntax, a JSON string, or as <KEY=VALUE> pairs.
Not being able to use it for some deployment types if regression or feature inparity.

I won't open a new ticket for now.

You should because passing multiple key-value pairs to single -p/--parameters is documented feature: Parameters may be supplied from a file using the @{path} syntax, a JSON string, or as <KEY=VALUE> pairs.
Not being able to use it for some deployment types if regression or feature inparity.

Agreed - I wasn't meaning to suggest we don't also open an issue.

I'm going to lock this conversation to encourage raising new issues instead of responding via comment.


FilterNewVariants method is never called when there is a manifest update.

Have you read the FAQ and checked for duplicate open issues?:
yes
What version of Shaka Player are you using?:
master
Can you reproduce the issue with our latest release version?:
yes
Can you reproduce the issue with the latest code from master?:
yes
Are you using the demo app or your own custom app?:
demo app
If custom app, can you reproduce the issue using our demo app?:
yes
What browser and OS are you using?:
Chrome MacOS
What are the manifest and license server URIs?:

It is happening on all live stream. I tested Big Bug Bunny (Live) asset on the demo app.
What did you do?
Just started a live stream.
What did you expect to happen?
filterNewPeriods should be called when there is a manifest update.
What actually happened?
This method is never called.
This might be a potential question as I am not certain, but I would like to learn whether this is a bug or not. Shaka player calls filterAllPeriods method when initiating a live stream. As for same logic, manifest updates should also be filtered out here as you can read the comments. However, that block never gets called due to this check. Let's say, initiated manifest period id = 0. When there is a new manifest update, next manifest period id may also be 0 because period id does not necessarily have to be unique. That's why that if block would never be called.
My question is that does shaka player assume periods which have the same id would always have the same type of variants(codec profile etc)? For instance, shaka player should only filter out variants when a next manifest has an extra period or period id is changed instead of calling for all new period variants?

That is working as intended, DASH requires that all Periods have unique IDs.  If a manifest update has a Period with the same ID, it needs to represent the same content and have the same streams in it.  You can't reuse Period IDs for new Periods and can't change streams during playback.  New Periods need a new ID, but can have different streams than the previous; but an existing Period can't change streams.
Period IDs are used to associate the previous manifest update with this one.  It allows us to determine which of the Periods from the previous manifest update correspond with the Period in this update.  So the same Period needs to have the same ID and new Periods need to use different IDs.
Note that if a Period doesn't have an id attribute, we will generate an ID based on the start time of the Period.

Thank you so much for your response, @TheModMaker  The reason I asked is that there is a discussion going on #1567 . It looks like shaka player should support codec profile change during live playback. So, I was not quite sure that must period Id be changed if codec profile changes. As for your comments, it has to be. It looks like our stream also changes this periodId all the time when there is a codec profile change. Thanks a lot. We can close this ticket so.


Add support for loading environment variables from .env file

This PR adds support for loading environment variables from a .env file to improve local DX.
This is using my new Gleam package, glenvy for loading the file.
Motivation
When I first started hacking on packages I ran into some rather unhelpful error messages when trying to run gleam run server or gleam run sync:
exception error: #{function => <<"server">>,gleam_error => assert,line => 62,
                   message => <<"Assertion pattern match failed">>,
                   module => <<"packages">>,
                   value => {error,nil}}
  in function  packages:server/0 (/Users/maxdeviant/projects/gleam-packages/build/dev/erlang/packages/_gleam_artefacts/packages.erl, line 51)⏎

I eventually figured out that this was due to an assertion failing due to missing environment variables.
I've been using a local justfile (for just) while working on packages as a way to source the environment variables from my .env file:
set dotenv-load

test:
    gleam test

run:
    gleam run server

sync:
    gleam run sync

Of course, I figured it would be better if we could just support .env files out of the box 🙂

Also, I totally understand if you'd rather not pull in such a green 🌱 dependency into this project.

Closing due to inactivity, please feel free to reopen


Feature request: Webhooks for internal payments

Webhooks are only fired for backend payments. Internal payments could also have webhooks.

Duplicate of #639. Closing.


chore: Ensure the one time dev build does not incorrectly default to using the HMR frontend host

PR fulfills these requirements

[X] Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
[ ] Tests for the changes have been added/updated (for bug fixes/features)
[ ] Docs have been added/updated (for bug fixes/features)
[X] Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
[X] Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)
(check all that apply)

[ ] Product design
[ ] Backend (Database)
[ ] Backend (API)
[X] Frontend

Describe the reason for change
With the recent release to make HMR support in development for LabelStudio, there were some parts that were a bit too aggressive and were causing non HMR development builds to fail.
Which logical domain(s) does this change affect?
Webpack/Dev-tooling

:rocket:
This description was created by Ellipsis for commit bf0ec9719e92dfb968e1ebd5a83f310a6b8e45b0

chore: ensure non-HMR dev builds don't default to HMR settings
Summary:
Introduces FRONTEND_HMR to control HMR usage in webpack.config.js, ensuring non-HMR builds don't default to HMR settings.
Key points:

Behavior:

Introduces FRONTEND_HMR environment variable in webpack.config.js to control HMR usage.
Sets FRONTEND_HOSTNAME to an empty string if FRONTEND_HMR is not "true".
Sets HMR_PORT to 8010 if FRONTEND_HMR is not "true".

Configuration:

Modifies devServer configuration to use HMR_PORT and FRONTEND_HOSTNAME based on FRONTEND_HMR.

Generated with :heart: by ellipsis.dev

Bug not working

Lỗi không hoạt động

Khi xem các tập lệnh đang được tải từ mẫu Django, tôi tin rằng bạn đã thiết lập ở đâu đó trong môi trường của mình:
FRONTEND_HOSTNAME=http://localhost:8081

Và có thể là:
FRONTEND_HMR=true

Tôi vừa chạy lại lệnh này trên nhánh phát triển và có thể chạy mà không có lỗi, hãy kiểm tra các biến môi trường của bạn và xóa FRONTEND_HOSTNAMEvà FRONTEND_HMRnếu bạn định chạy bản dựng phát triển một lần hoặc chạy trình theo dõi phát triển cũ. Nếu bạn muốn bật lệnh này và chạy ở chế độ HMR, hãy đảm bảo các biến đó được đặt trong môi trường của bạn, sau đó sử dụng lệnh make frontend-devthay vì make frontend-watch(hoặc trên thư mục web không phải unix chạy : yarn dev).
https://github.com/HumanSignal/label-studio/tree/develop/web#installation-instructions

I understand this problem very well before the pull request with these environment variables created I was running according to the old steps and it still ran, the problem is I want to run but don't need to run the yarn dev command after this change I am forced to run it, I find it unnecessary, is there a way to remove it and still run?

https://github.com/HumanSignal/label-studio/pull/6376#issuecomment-2349555909
Please remove these environment variables and rerun both the yarn watch command, and your Django instance. If you want to run with yarn watch command, then these cannot be set as these will interfere with your Django instance.


Do not generate proxies.json in v4 apps

V4 no longer supports proxies.

We can also hide the proxy tree item as well

Sounds good, thank you.


Language select empty

The language select box has no entries to select, thus I cannot import the DB.

Tried v1.2.3, v1.2.2, v1.2.1 and v1.0.0. All the same.

The language list is empty because exporter failed to get a list of languages available in X4.
Please try the following steps.
1. Check input folder path.
Please make sure you have selected the correct destination folder for the X4 installation.
The correct folder path is the parent folder path of "X4.exe".

NOTE: Please replace with "￥" to "\".
I'm using the Japanese environment, so "\" is shown as "￥".

2. Disable mods. (if using mods)

When using a mod, please rename the extensions folder and check the operation again with the mod not recognized.
If work succeed when renamed extensions folder, please tell me your installed mods.

If you continue to experience problems, please contact me again.
Thank you.

Huh, after renaming it to "aextensions", it still didn't work. Looking at some random code, I found a questionable regexp that looks for folders that contain "extensions" for some reason, instead of completely matching the entire name. After scrambling the name completely it loaded the language list and import worked.
Here are my currently used mod directories:
'Average Prices Suffixes'/
Better_tractor_beam/
BetterScanColors/
BK_TurretBehavior/
data_leak_modifications/
DeadAirDynamicWars-master/
ego_dlc_split/
escape_teleport/
faction_fix_pack/
faction_fix_pack_catchup/
faction_fix_pack_econ_ai/
faction_fix_pack_econ_bal/
G_Work_Around/
infocenter/
JP_AnotherExplorerV2/
JP_DataVaultExplorer/
JP_MultiRename/
kuertee_signal_leak_hunter_increasing_range/
kuertee_station_scanner/
kuertee_ui_active_mission_button/
kuertee_ui_reset_mouse_on_menu_close/
learningallthethings/
Legacy_Music/
mej_disable_encounters/
mules_and_warehouses_extended/
No_Battle_Music/
NoMoreNotificationsSound/
NoSuperHighway/
phq-warp/
RightClickAPI/
SatNetwork/
shib_paythebuilder/
sn_asteroid_fade/
sn_better_target_monitor/
sn_extra_game_options/
sn_mod_support_apis/
sn_reduce_fog/
'Spacesuit thrust upgrade'/
spherical_long_range_scan/
TaterTrader-master/
trade_buy_notification/
Unique_Datavault_Pings/
vro/
vroicons-stable/
vxLegalInventory/
x4_fireandsmoke/

Why would the mod directories prevent this though?

Huh, after renaming it to "aextensions", it still didn't work.

I'm not sure why renaming the "extensions" folder to the "aextensions" folder doesn't work.
However, it's probably because the process that updates the language list is not called when the same folder as the last time is specified.

Why would the mod directories prevent this though?

The data extraction process tries to create a language list including in the mod folder.
At that time, if some error occurs, it will assume that the folder other than the installation folder of X4 was selected and the language list will be empty.
In this case, there was an unexpected pattern when loading the "content.xml" in the Mod folder, so it was treated as an error and the language list was empty.
Cause

Due to an unexpected pattern when loading "content.xml" into the mod folder, it was treated as an error and the language list was empty.

It failed to take into account the case where the xml declaration and other tags are on the same line.

example
The XML declaration was assumed to be in the first line by itself.
<?xml version="1.0" encoding="utf-8"?>
<content id="foo" ... />

However, the "content.xml" in "kuertee_ui_reset_mouse_on_menu_close" looks like this, and the rest of the xml declaration was unintentionally skipped.
<?xml version="1.0" encoding="utf-8"?><content id="kuerteeUIResetMouseOnMenuClose"
	name="kuertee UI: Reset mouse on menu close"
	:

Correspondence
Fixed a process to ensure only XML declarations are skipped.
I will be releasing a version that fixes this bug soon.
We'll let you know when it's released.
Thank you.

I manually fixed all the content.xml files as indicated and it now updates the DB properly! 👍

I have released a version that addresses this issue.
Please download the latest execution environment here.
If you continue to experience problems, please contact me again.
Thank you for contacting me with the bug.


feat: iOS docs

Is your feature request related to a problem? Please describe.
I've followed the readme instructions and it works for Android but not for iOS. I don't see any crash reports in firebase (I.did crash the app several times). I've tried to follow the instructions from google, but still no luck
Describe the solution you'd like
just some tips about how to make it work in iOS
Describe alternatives you've considered
Additional context

Please have a look at Test your implementation.
The Firebase Crashlytics documentation should contain sufficient information.
Among other things, the following points are important:

Add a Firebase configuration file (Guide).
Do not attach a debugger at launch.
Set the correct Debug Information Format.

It may happen that the dSYM files are not uploaded automatically. However, this does not prevent the crash from being displayed in Crashlytics.

Hi @robingenz. Thank you for the information.
I am working with @sebastianovide. The version of plugin we use is the latest (v0.4.0). I can confirm the Crashlytics has successfully been captured after running the app without attaching the debugger. I test it in iOS simulator.

Hi @joykuotw, excellent!
I will close this issue.
Reach out to me if you have any other issues.


Mech Equipment Redesign Plan

Description

Currently, mechs have a very stinky format for their equipment. You're forced to use specific interaction events on essentially duped components just for doing basic tool/item interactions.
Ideally, it'd work like this:

standard interaction events get received by MechPilotComponent
interaction system is used to make the mech itself do those same interactions using the current item selected for the item in their "hand"

The issues are thus:

InteractUsing API might need reworking to circumvent no hands
MechEquipment should cancel attempted interactions by entities that are not mechs.

This would hopefully allow us to just define an extra component on a generic item to allow it work as equipment.

 It would basically solve all the issues in point 1, however.

body

mech surgery real
you could also make mechs parts limbs
dear god this is cursed

Body prototypes really hate having empty slots so i doubt you could make it work well. Its probably for the best that you just get rid of all the weird hand dependency in interactions anyways.


[Tailwind CSS] Allow to pull colors from your own tailwind.config.js

Extension
https://www.raycast.com/vimtor/tailwindcss
Description
Hello, and thank you so much for this fantastic extension!
It will be really great if there was a way to define your own colors, since I'm sure a lot of people have adjusted these to match their branding guidelines, hence rendering this functionality useless for this use case.
I'm not even sure if it's possible, but just thought I'd throw it out there :)
Thank you!
Who will benefit from this feature?
Whoever is not using the default TailwindCSS color palette.
Anything else?
No response

Hey @alessandro-newzoo thanks for the suggestion! I like the idea but I'm not sure if there is an easy way for the user to add their own colors. Maybe copy pasting the   colors field in the tailwind.config.js?

hey @vimtor !
I'm actually not sure what can be done with Raycast's API, but I'd say one of these options might work:

let the user paste the colors object into some input box in Raycast, or
let the user upload their tailwind.config.js, or
let the user paste the path of a locally stored tailwind.config.js

My workaround currently is to clone your repo, replace /tailwind.config.js  with mine, and make these edits to /src/search-colors.tsx:
- import colors from "tailwindcss/colors";
+ import config from '../tailwind.config';
+ const colors = config.theme.extend.colors;

though this implies that the config file is using extend and also that the colors object contains no functions, or else it won't work.
So, long story short, probably a field to paste in the colors object would be the easiest?
I'm also opening another issue for some more suggestions, I hope you don't mind! ❤
Thank you,
Alessandro

Hi @alessandro-newzoo!
I have been experimenting with allowing the user to select their own file. After trying different tailwind.config.js files from the internet, I concluded that it would be better to create a separate extension to manage color palettes and search within them. There were many edge cases since it is Javascript. Some files were simple, while others imported things or looped through colors. I could consider adding an input to let the user add their own colors, but there is no easy way for Tailwind CSS users to get all the colors in a specific format.
If you don't mind, I will close this issue. If you think more people could benefit, I could create the color palette extension I mentioned.
@raycastbot close this issue.

Hi @vimtor !
That's alright, what you say makes sense, I didn't think about people having different structures in their tailwind.config.js.
I will continue using a fork of your extension in which I've added all my colors.
Thanks a lot for this and keep up the great work!


No Congestion Whatsoever

After solving 365 security constrained unit commitment problems for the ACTIVSg200r system (contingencies not considered), I realized that there is no congestion in all 365 days, and the line flows are far from the limits

solved in commit  02abbff5bc11e58a04f818f9065e5fb0e1252047


Run CI on 1.45.2 (attempt to reproduce #24)

attempt to reproduce #24

Closing as this can't reproduce #24.


movemouse not work in the virtualbox,os is windows

movemouse function doesn't not work in the virtualbox,os is windows

Closing is due to can't reproduce and non-standard.

I had the same issue as above.
Workaround:
At first the program did not worked, it was just hanging there.
Then I closed the app, turned off the "Mouse integration" feature for the VM, and started the app again, and the integration worked fine.
Let me know if I should send a PR to change this in the README or you'd prefer to reproduce this (see the details below).
P.S. Thanks for this awesome project!
Steps to reproduce:

install VirtualBox 6.1 on a Windows 10 amd64 Host machine
install Ubuntu 18.04.3 amd64 as a Guest OS
use Go 1.13.5 to compile a sample app like this:

package main

import "github.com/go-vgo/robotgo"

func main() {
	robotgo.MoveMouseSmooth(100, 200, 1.0, 100.0)
}


Trimmed whitespaces in Configuration Explorer

I had an issue with one of our apps because of having whitespace at the beginning of the value, unfortunately, it's hard to find these in Portal because in the list view these are trimmed. So in order to find it, you have to go to the edit screen or export all of them (don't know if there's any other way).

Where's in reality one of the values looks like it:

Probably these whitespaces should be shown in the list too. So it would be easier to maintain it.

@jiayi11 I remember this was a regression and fixed. Empty spaces are highlighted with dots. Can you please confirm?

@jiayi11 can this issue be closed?

Yes this is fixed


Decapitalization does not work if output is via related field

@Glottotopia Could you have a look into this, please?

no


cloudflare-warp: 2022.8.936 -> 2023.1.133, add Cloudflare Zero Trust enrollment desktop file

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 218487 run on x86_64-linux 1

1 package built:

cloudflare-warp


Some automated test for the library

AmgXWrapper has two distribution modes: as source files to be compiled by the client and as a shared library. Bundling the source files is perhaps not too onerous for an application, but wholly inappropriate for another library -- libraries cannot assume that some other part of the application won't also call AmgXWrapper. As far as I can tell, there are no examples or automated tests for the library. It's also rather complicated to determine if things are working correctly upon building the library -- you need to go out into a different directory and configure a different build (probably with the same command-line options) to build the example, then run it and parse the output (which has some terminal noise; e.g., about JSON vs AmgX input file formats). There should at least be a "make test" target that for the library that verifies that the build is working correctly.

Agree. We will create some automatic tests and make both examples use the library.


fix flaky pacing test on CIs

Fixes #1141.

Codecov Report

Merging #1142 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1142   +/-   ##
=======================================
  Coverage   90.84%   90.84%
=======================================
  Files         111      111
  Lines        7520     7520
=======================================
  Hits         6831     6831
  Misses        460      460
  Partials      229      229

Continue to review full report at Codecov.

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


Streaming dataset + interleave + DataLoader hangs with multiple workers

Describe the bug
Interleaving multiple iterable datasets that use load_dataset on streaming mode hangs when passed to torch.utils.data.DataLoader with multiple workers.
Steps to reproduce the bug
from datasets import interleave_datasets, load_dataset
from torch.utils.data import DataLoader

en_dataset = load_dataset('oscar', "unshuffled_deduplicated_en", split='train', streaming=True)
fr_dataset = load_dataset('oscar', "unshuffled_deduplicated_fr", split='train', streaming=True)
it_dataset = load_dataset('oscar', "unshuffled_deduplicated_it", split='train', streaming=True)
de_dataset = load_dataset('oscar', "unshuffled_deduplicated_de", split='train', streaming=True)
multilingual_dataset = interleave_datasets([en_dataset, fr_dataset, de_dataset, it_dataset])
multilingual_dataset = multilingual_dataset.with_format('torch')

next(iter(multilingual_dataset))  # works fairly fast

dataloader = DataLoader(multilingual_dataset, batch_size=8, num_workers=4)
for batch in dataloader:
    print(len(batch))  # prints nothing after 30 min of waiting

dataloader = DataLoader(multilingual_dataset, batch_size=8, num_workers=0)
for batch in dataloader:
    print(len(batch))  # prints right away

Expected results
It should be able to iterate the dataset with multiple workers.
Actual results
Prints with results with next(iter(multilingual_dataset))  and num_workers=0  but it prints nothing with num_workers=4 or any number above 0.
Environment info

datasets version: 2.0.1.dev0
pytorch version: 1.10.0+cu113
Python version: 3.7
PyArrow version: 6.0.1

Hi ! Thanks for reporting, could this be related to https://github.com/huggingface/datasets/issues/3950 ?

+1

Please update datasets if you're having this issue. What version are you using ?


docs(material/datepicker): add note about locale data in date-fns

Adds a note about how locale data should be provided for users that consume the date-fns adapter.
Fixes #24026.

@crisbeto - is this one ready for review?

This should be good to go @andrewseguin


Sub-step logging

There's been a little discussion in Cucumber around the idea of exposing actions within steps to formatters.
An idea for this in PHP would be to expose a Logger of some sort inside Contexts (We could use something fairly standard like the PSR-3 Logger).
We can then display any logs to users when a higher verbosity setting was used, or in something like an HTML formatter the detail could be hidden and popped open on demand
Extensions like MinkExtension, Behatch (or whatever takes its place) could hook into this and log actions automatically:
> behat -f pretty -vvv

Example: Approving invoice makes it disappear from list
Given a draft invoice for £500 exists
     Executed SQL "INSERT INTO invoices (total, date, status) VALUES ('500.00', NOW(), 'draft')
When I approve the invoice
     Navigated to /invoices/1234
     Clicked 'Approve'
Then the invoice should no longer be on the draft list
     Navigated to /invoices/drafts
     Checked xpath '//div[@id='invoice-123']' not present

The motivation is to improve debugging and transparency of test automation
To think about:

is plain text enough, or should we support richer content (e.g. JSON/XML)
which extensions would make good use of it?

The logs for each Step could be attached to the relevant existing events

I like this. It would also mean the test detail can be improved ad-hoc if desired, so the test can be readable by default, but contain enough information when ran in debug mode.

I absolutely love this idea, that would make debugging so much nicer!
How about (optional) method injection like Symfony has for controllers?
for example
/**
 * @Given something
 */
 public function something(LoggerInterface $logger): void
 {
    $logger->debug('Something happened in the past');
 }

so when there is a type hint for LoggerInterface on a step it injects a logger. That logger is probably some custom implementation that just records logs internally and can be interrogated about what it received.

@rpkamp we would need to be careful to not collide with user services (e.g. using the symfony extension) and I suppose a PSR logger is pretty common. Maybe a Behat type would make the most sense?

Yes, that would work.

As an alternative, how about a separate interface, like LoggingContext, something like
interface LoggingContext
{
    public function setLogger(Some\Behat\Logger $logger): void;
}

Then when the context is created we can detect if it implements LoggingContext and if so call setLogger with our logger. During execution we can look at this logger to see what is logged there.
If the Behat logger implements the PSR interface we can even do nice things like take the logger we get from Behat and wire it up into our application so we can get application logs in Behat.
At least this way seems more versatile than method injection to me.
What do you think?

I would definitely prefer a Behat specific logger type, this way I could request it in my contexts when using SymfonyExtension and I wouldn't get the app logger, it would make things much more clean. This also means you don't need to inject the logger into steps.

any update on this?


--config [JSON] + projects doesn't seem to work

🐛 Bug Report
When passing serialized JSON for the --config option that contains projects, I get the following error:
Error: Jest: Cannot use configuration as an object without a file path.
    at readConfig (~/github/benmvp/benmvp-cli/node_modules/jest-config/build/index.js:139:13)
    at projects.filter.map.root ~/github/benmvp/benmvp-cli/node_modules/jest-cli/build/cli/index.js:487:62)
    ....

The parsed JSON looks like:
{
    "projects": [
        {
            "moduleFileExtensions": ["ts", "js"],
            "transform": {
                "^.+\\.(ts|js)$": "babel-jest"
            },
            "testMatch": [
                "<rootDir>/src/**/*.ts"
            ],
            "runner": "jest-runner-tsc",
            "displayName": "typescript"
        },
        {
            "moduleFileExtensions": ["ts", "js"],
            "transform": {
                "^.+\\.(ts|js)$": "babel-jest"
            },
            "testMatch": [
                "<rootDir>/src/**/*.spec.ts"
            ],
            "displayName": "test"
        }
    ],
    "rootDir": "."
}

To Reproduce
Just run:
npx jest --config '{"projects":[{"moduleFileExtensions":["ts","js"],"transform":{"^.+\\.(ts|js)$":"babel-jest"},"testMatch":["<rootDir>/src/**/*.ts"],"runner":"jest-runner-tsc","displayName":"typescript"},{"moduleFileExtensions":["ts","js"],"transform":{"^.+\\.(ts|js)$":"babel-jest"},"testMatch":["<rootDir>/src/**/*.spec.ts"],"displayName":"test"}],"rootDir":"."}'

Expected behavior
I expect to be able to run the projects just like if they were defined in a config file (which does work).
Link to repl or repo (highly encouraged)
See repro command. Happy to contribute a PR, I just don't know what to fix. 😄
Run npx envinfo --preset jest
Paste the results here:
  System:
    OS: macOS High Sierra 10.13.6
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 10.12.0 - ~/.nvm/versions/node/v10.12.0/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.12.0/bin/npm
  npmPackages:
    jest: ^23.6.0 => 23.6.0

Debugging
1/ I tried moving the JSON back to a .js file and it works (my current workaround). I need the contents to be dynamic, which is why I want to pass JSON
2/ I did a whole bunch of code spelunking to try to get it to work. I narrowed down the problem to readConfigs in jest-config. It seems that after successfully parsing the JSON, it maps over each project to readConfig on each (passing configPath). The problem is that configPath is null so readConfig complains. And the reason configPath is null is because when the JSON was originally parsed (also by readConfig), I guess there is no configPath to set so it remains null. That's as far as I got since I don't understand the why of the code.

Hey @benmvp thanks for filing! Confirmed - I'll take a look

Awesome! Thanks @rickhanlonii! Lemme know if there's any way I can help

Hey @benmvp, I took a look at this and it looks like the projects need to be specified as separate cli options as npx jest --projects p1 p2 --config c (see comment here)
Can you try:
npx jest --projects '{"moduleFileExtensions":["ts","js"],"transform":{"^.+\\.(ts|js)$":"babel-jest"},"testMatch":["<rootDir>/src/**/*.ts"],"runner":"jest-runner-tsc","displayName":"typescript"}' '{"moduleFileExtensions":["ts","js"],"transform":{"^.+\\.(ts|js)$":"babel-jest"},"testMatch":["<rootDir>/src/**/*.spec.ts"],"displayName":"test"}' --config '{"rootDir":"."}'

I'm running into the same issue as @benmvp with the configPath always being null on this line: https://github.com/facebook/jest/blob/master/packages/jest-config/src/index.ts#L333
I'm in the same boat where I don't know exactly what this configPath means, but replacing that line with process.cwd() seems to fix it for me.
I'd be happy to send a PR, but I'm not 100% sure what should be the fix 😅
Additional context
In RedwoodJS you can configure multiple sides in your app that require different Jest configs (for frontend, backend, React Native, more). I'm trying to dynamically construct a project per side.

I have the same problem. When I use a serialized JSON for the --config option that contains projects, I also get the following error:
Error: Jest: Cannot use configuration as an object without a file path.

Hello, how is the progress? I'm specifying the config in the jest.config.js and still get this error 😿


Missing angular-confirm.min.js by installing via npm

Hi, James. You developed this wonderful module, thank you so much, dude. But we are confused by some strange things:

there's a line in package.json:

"main": "angular-confirm.min.js"

but! in .gitignore you specified same file - angular-confirm.min.js

By installing this module via npm we have a problem: module does not contain angular-confirm.min.js because of .npmignore which totaly matches with .gitignore. Could you please update the package in npm providing an appropriate .npmignore (which wouldn't contain angular-confirm.min.js).
We've got this error because of missing angular-confirm.min.js:
Module not found: Error: Cannot resolve module 'angular-confirm'

Hmm, main shouldn't be pointing to minified version.

@simison Can you point me to some documentation somewhere saying the main file should not be minified?

@jameskleeh good question! It's kinda just common knowledge, now that I looked into it I didn't see any mention of this at package.json's spec (but it's designed for backend stuff in mind anyway).
The problem is that if you use minified versions in development, it's quite hard to debug stuff when something breaks. Everyone should be able to minify their JS for production the way that suits them best anyway.

@jameskleeh please publish last changes on npm


Build error with Node v4.0.0

After updating to node v4.0.0 build error occured:
gyp: /usr/lib64/node_modules/npm/node_modules/node-gyp/addon-rpm.gypi not found (cwd: /mnt/Data/Projects/MailAgency/node_modules/bcrypt) while reading includes of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: gyp failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib64/node_modules/npm/node_modules/node-gyp/lib/configure.js:358:16)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.16.7-24-desktop
gyp ERR! command "/usr/bin/node" "/usr/lib64/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /mnt/Data/Projects/MailAgency/node_modules/bcrypt
gyp ERR! node -v v4.0.0
gyp ERR! node-gyp -v v3.0.1
gyp ERR! not ok
npm ERR! Linux 3.16.7-24-desktop
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "bcrypt"
npm ERR! node v4.0.0
npm ERR! npm  v2.14.2
npm ERR! code ELIFECYCLE

Added same report to
https://bugzilla.opensuse.org/show_bug.cgi?id=948733

I'm sensing a little bit of irritation on the README for reporting bugs. NodeJS bcrypt will not build using Node v4.0.0. That version is stable. Since node-gyp

only works with stable/released versions of node

and

the bcrypt module uses node-gyp to build and install you'll need a stable version of node to use bcrypt

I'm not following how this issue is closable. I don't see a duplicate open right now, so that can't be it.

1 Same issue on Heroku


Add redis to the openstack-operator

This patch adds support for deploying redis through the openstack-operator. It is currently disabled by default.

/test all

/test all

@beagles: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
Test name 	Commit 	Details 	Required 	Rerun command
ci/prow/openstack-operator-build-deploy-kuttl 	c655a4d link 	true 	/test openstack-operator-build-deploy-kuttl
Full PR test history. Your PR dashboard.

@beagles The KUTTL test is failing because the .spec.redis.templates is missing:
           redis:
             enabled: false
        -    templates:
        -      redis:
        -        replicas: 1

Maybe since Redis is disabled by default, we just should drop its templates block from it in the assert-sample-deployment.yaml?

/retest-required


Method authorization

Hi,
I want to know if there is a way to do some method authorization via annotations, like you do in Java, checking the role or the user group.
Thanks in advance!

Hi,
You can write annotation macro like follows.
@authority(Admin)
def index = Action {
  ...
}

convert to
def index = StackAction(AuthorityKey -> Admin) {
  ...
}

Best


Update dv--display-local-variables-.md

Add missing /r option to dv.

@lzybkr - Looks like this ready to go live?
Thanks for thinking of the docs! :)

@DOMARS - yes, this can go live.


Add ucpe-oneos

The Ekinops uCPE is a CPE with a hypervisor, allowing service providers to deploys individual VNFs or service chains on the edge.
The license is tied to UUID, so we also support injecting a static UUID.
Tested with 3.7.5 and 3.8.1.

The xrv9k test that is failing here is not related to the changes in this PR.


The system cannot find message text for message number 0x%1 in the message file for %2

Error: The system cannot find message text for message number 0x%1 in the message file for %2.
\?\D:\demo\server*node_modules\sharp\build\Release\sharp.node*
please help me its urgent
working fine in browser but not in electron js
maybe i am using a 64bit build but building that module as 32-bit.

Hello, only 64-bit node.exe is supported on Windows.
http://sharp.pixelplumbing.com/en/stable/install/#windows-x64

i have installed 64 bit in my PC but sharp working proper in browser but not in electron

i have installed 64 bit in my PC but sharp working proper in browser but not in electron.
please tell what i need to change or add?

electron-rebuild will probably be required if the system version of Node doesn't match the Electron version of Node. Make sure the Electron executable is 64-bit also.

I had the same issue on Windows x64 with node v8.11.1 and on Electron with node v10.2.0.
electron-rebuild fixes this issue for me.


Fuzz testing round 4: Roundtrip followup

Follow up to #8. Found some failures when running the roundtrip and roundtrip_huffman fuzzer:
flate-fuzz-roundtrip-20230210-1.zip
flate-fuzz-roundtrip-huffman-20230210-1.zip
The failures can be reproduced by running the inputs through https://github.com/ianic/flate/blob/main/bin/roundtrip.zig (since it tests all compression levels + huffman only + store only).

Great finding.
I was mishandling  bit stream byte boundary during flushing. Resulted in adding few bits of padding if not at byte boundary.
Thanks.


Estimated airtime in TTN Console's gateway traffic and application/device data do not match

This is a bug report for the console.

What do you want to do?

Get the correct estimated airtime of a packet in TTN Console.

What steps did you take?

Sent a 21 bytes packet (8 bytes application payload) on SF7. For this, the LoRaWAN air time calculation sheet at https://www.thethingsnetwork.org/forum/t/spreadsheet-for-lora-airtime-calculation/1190 shows 56.576 ms airtime. Also, the gateway's traffic page shows: "airtime (ms) = 56.6 ms".
(When repeating with 17 bytes total, being 4 bytes application payload, the sheet calculates 51.456 ms, and the gateway then shows 51.5 ms too.)

What went wrong or what is missing?

For 21 bytes, the application's and device's data pages show "Estimated Airtime = 51.456 ms" instead of 56.5 ms like the gateway does.
It seems 2 bytes too few are taken into account for the estimation? For 19 bytes, the calculation sheet indeed shows 51.456 ms.
(When repeating with 17 bytes, the application and device data show 46.336 ms, while the gateway shows 51.5 ms. Again: like 2 bytes fewer were used for the calculations, as for 15 bytes the sheet indeed shows 46.336.)

Do you have Screenshots?

Gateway:

Device:

...after scrolling down:

Airtime calculator:

What kind of OS/Browser/Gateway are you using? Which version?

Mac OS X, Chrome, single-channel test gateways.

What are the IDs and EUIs of your Device/Gateway? (if applicable)

Gateways: eui-b827ebffff5fe05c and eui-5ccf7ff42f1970ec
Device: arjanvanb-bb-2/EUI 0004A30B001B1874

What do your configuration files look like?

n/a

What do your log files look like?

n/a

Can you fix this yourself and submit a pull request?

Maybe, if you open source the code ;-)

@jpmeijers Can you have a look why this is wrong?

Isn't this fixed @Ragnn @romeovs ?

Not yet. I'll work on it soon. @Ragnn added the backend part, but the front-end needs to be updated to reflect that.

This should be fixed by fe151b7f53. Can you confirm @avbentem?

@romeovs: This issue is still not resolved (as far as I can see on the PCN console).
Take as an example the office-app. Our sensor at HQ should show an airtime of 51.456. The gateway view shows the correct value, but the Data view doesn't.
Today I started with the implementation of #682, which adds the airtime to uplink (and downlink event) metadata. When deployed, that value can be displayed in the console.

The estimated airtime shown in the console is calculated by the github.com/TheThingsNetwork/ttn/utils/toa package. Could it be that the parameters are interpreted wrongfully?

Both values are calculated by the console. One is correct, another isn't.

Coule it be that the console gives the wrong parameters to the toa package? https://github.com/TheThingsIndustries/console/blob/master/server/api/events/app_subscription.go#L302-L305
Difference between PHY payload and application payload could be the cause?

Likely. In that case it can be resolved when https://github.com/TheThingsNetwork/ttn/commit/0f795e39c6f00b663f70212595de09cf4f2c92a4 is live

Is this still unsolved? I'm seeing some differences and I think both, gateway and application estimated airtimes are wrong.
Sending 38 byte of app payload, resulting in 51 byte payload in the gateway overview:

In the application:

And this is calculated with the Semtech LoRa Model Calculator Tool (51 bytes):

And with 38 bytes:

So, we do have 4 different airtimes, none matching the TTN airtimes.
Which one is the correct one?

I recently had The Things Network stop the movement of all my data from my gateway to my apps due to going over the 30-second daily limit (not just the offending app/device, but all of my apps, even the ones not exceeding 30 seconds/day). This was due to using the App airtime estimate. Using the gateway airtime, data began appearing in my apps again. I see reporting incorrect airtime (or calculation) as a significant bug.
Additionally, is it expected behavior for data from all apps to cease operating when one device exceeds the daily transmission limit?

Hi @kizniche, the 30-second daily limit is not enforced; we don't even have any code to do that, so I can with 100% certainty say that the lack of traffic was not caused by this.

Thank you for the clarification. Perhaps it's just a coincidence they all stopped. I'll have to investigate further.


build: Fix translation pull action

@Ian2012 this should fix the translations cla error, here's a run off this branch: https://github.com/openedx/tutor-contrib-aspects/pull/647


Can't use the PRIVATE part of api

UnhandledPromiseRejectionWarning: TypeError: First argument must be a string, Buffer, ArrayBuffer, Array, or array-like object.
at Function.Buffer.from (buffer.js:183:11)
at new Buffer (buffer.js:158:17)
at Signature._createSignature (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Signature.js:52:52)
at Signature.signBody (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Signature.js:75:41)
at Bitstamp._getOptions (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Bitstamp.js:68:39)
at Promise (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Bitstamp.js:90:34)
at Promise._execute (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/node_modules/bluebird/js/release/debuggability.js:313:9)
at Promise._resolveFromExecutor (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/node_modules/bluebird/js/release/promise.js:488:18)
at new Promise (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/node_modules/bluebird/js/release/promise.js:79:10)
at Bitstamp.call (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Bitstamp.js:79:16)
at Bitstamp.balance (/Users/justinnothling/Code/nibit/node_modules/node-bitstamp/lib/Bitstamp.js:198:21)
at test (/Users/justinnothling/Code/nibit/bitesting.js:23:36)
at Object. (/Users/justinnothling/Code/nibit/bitesting.js:40:1)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)

Can anyone help me understand what I'm doing wrong?

never mind, I was being dumb


Bicep language server for VS Code Insiders fails to launch

Does this occur consistently? Yes
Repro steps:

Open a *.bicep file
Error message appears "Couldn't start client bicep". The language server fails to launch, and no syntax highlighting or other bicep features appear.

The following output is logged in the output terminal.
2021-02-09T17:12:01.153Z info: Current log level: debug.
2021-02-09T17:12:01.155Z info: Launching Bicep language service...
2021-02-09T17:12:01.155Z info: Acquiring dotnet runtime...
2021-02-09T17:12:01.357Z debug: Found dotnet command at '/Users/sihde/Library/Application Support/Code - Insiders/User/globalStorage/ms-dotnettools.vscode-dotnet-runtime/.dotnet/5.0.2/dotnet'.
2021-02-09T17:12:01.357Z debug: Found language server at '/Users/sihde/.vscode-insiders/extensions/ms-azuretools.vscode-bicep-0.2.328/bicepLanguageServer/Bicep.LangServer.dll'.
2021-02-09T17:12:01.370Z info: Bicep language service started.
[Error - 9:12:01 AM] Starting client failed
Launching server using command ./dotnet failed.
Error: Launching server using command ./dotnet failed.

The issue seems related to recent builds of VS Code Insiders:

VS Code Insiders + bicep extension 0.2.328: fails
VS Code Insiders + bicep extension 0.2.212: fails
VS Code 1.52.1 + bicep extension 0.2.328: works
VS Code 1.53 + bicep extension 0.2.328: works

It used to work OK for me with VS Code Insiders; probably it broke within the past two weeks.
Action: bicep.activate
Error type: string
Error Message: Launching server using command ./dotnet failed.
Version: 0.2.328
OS: darwin
OS Release: 20.3.0
Product: Visual Studio Code - Insiders
Product Version: 1.54.0-insider
Language: en

Thanks for reporting this - I can also repro on OSX with VSCode insiders. It doesn't repro on Windows.

I'm able to fix this on OSX by changing:
https://github.com/Azure/bicep/blob/fe902b6cdd49931c4b5d478b1c3fecc2efedd9d7/src/vscode-bicep/src/language/client.ts#L44-L50
To:
 const serverExecutable: lsp.Executable = {
   command: dotnetCommandPath,
   args: [languageServerPath],
 };

So seems like some interaction between using spawn with a relative path + cwd on OSX.

Confirmed this works now with Bicep extension 0.3.1 and Code 1.54.0-insider 2021-03-02.


Add the Kubernetes DaemonSet

This PR adds the Kubernetes DaemonSet I'm using in order to have this container running on all the nodes of my cluster.

Thanks for this contribution! Just a small question, there's a mention of cassandra in the template, is this needed or perhaps a copy-paste artifact? I.e. this fragment
+    metadata:
+      labels:
+        app: cassandra

@mikljohansson it was a typo, updated.


add test for ntsa::Ipv4Address::less()

Add test case comparing IPv4 addresses to alleviate concerns that result depends on CPU endianness. This test was confirmed passing on x86_64 and sparc
Issue number of the reported bug or feature request: #
Describe your changes
A clear and concise description of the changes you have made.
Testing performed
Describe the testing you have performed to ensure that the bug has been addressed, or that the new feature works as planned.
Additional context
Add any other context about your contribution here.

Consolidated into https://github.com/bloomberg/ntf-core/pull/186


ci: merge coverage job

Motivation
Merges the code coverage job to the existing ci flow for better visibility.
Description

Test Plan

TODO

[ ] Explain motivation or link existing issue(s)
[ ] Test changes and document test plan
[ ] Update documentation as needed
[ ] Update changelog as needed

bors merge


Userstamp fix

https://ci.solanolabs.com/reports/1856226
https://github.com/coupa/coupa_development/pull/20686

Fix is for "undefined method to_sym for NilClass". This may have been caused by the fix to not make ActiveRecord::Base stampable, which was needed for Enterprise Rails 4.1.


for webpack4 builds, including req'd "foundation-explicit-pieces.js" causes fatal eslint build fail

when setting up Foundation-sites
yarn list | grep -i foundation-sites
	├─<EMAIL_ADDRESS>
for use in webpack 4.1.1, it's currently 'necessary' to manually/locally include an instance of "foundation-explicit-pieces.js"
https://github.com/zurb/foundation-zurb-template/blob/master/src/assets/js/lib/foundation-explicit-pieces.js
the final line in that instance,
module.exports = Foundation;

eslints, as seen in browser console as:
TypeError: "exports" is read-only[Learn More]   foundation-explicit-pieces.js:85

./assets/js/lib/foundation-explicit-pieces.js/< foundation-explicit-pieces.js:85
./assets/js/lib/foundation-explicit-pieces.js   foundation-explicit-pieces.js:1
__webpack_require__                             bootstrap:74
./assets/js/main.js/<                           https://example.com/build/js/main.js:308:89
./assets/js/main.js                             https://example.com/build/js/main.js:306:29
__webpack_require__                             bootstrap:74
[0]                                             https://example.com/build/js/main.js:467:1
__webpack_require__                             bootstrap:74
checkDeferredModules                            bootstrap:43
webpackJsonpCallback                            bootstrap:30
<anonymous>                                     universalModuleDefinition:11
webpackUniversalModuleDefinition                universalModuleDefinition:7
<anonymous>                                     universalModuleDefinition:1

at Gitter, @sokra commented
https://github.com/webpack/webpack/issues/4039#issuecomment-273804003

You can mix require and export. You can't mix import and module.exports.

Unless I exclude that file from eslint, the webpack build fails/bails as an error, not a warning.
What I do not yet know, is what problems that causes, if any, by ignoring ...

Did you try to use export {Foundation}; ?

The next release will be compatible.
See https://github.com/zurb/foundation-sites/blob/4e21634356da296edd2f1c3e65d91140f991008b/js/foundation.core.js#L337 and https://github.com/zurb/foundation-sites/pull/10930 regarding bundling.
foundation-explicit-pieces.js shows just one way to use Foundation.

Slight confusion ...
that reference has
Package up 6.4.3
develop (#1)       v6.4.4-rc1 v6.4.3
@kball committed on Aug 18, 2017

and I'm on 6.4.4-rc1.
so I do NOT need the explicit-pieces.js bit?

fwiw, simply
-	module.exports = Foundation;
+	export {Foundation};

both
(a) eliminates the lint/console error
&
(b) fixes a bunch of pesky artifacts I was seeing in my site frontend
And, it all webpack4 builds & watches with no apparent, related issues.
So if that's "the fix", worksforme. (tho, haven't tested thoroughly by any strecth)

so I do NOT need the explicit-pieces.js bit?

You can still use it. It is part of the templates and shows how you can import just the components that you need.
You can write your own solution and change the last line if you want to. It is just an example implementation of the Foundation framework.

Like I wrote =) https://github.com/zurb/foundation-sites/issues/11068#issuecomment-373940058
If you want you can share your setup with us and the problems that you face(d).
You can close the issue if it is working now for you.

You can close the issue if it is working now for you.

Appears to be, thx.  Still unclear what the recommended install is, or will be.

@hal869 see https://github.com/zurb/foundation-zurb-template/pull/84


Screen value (mobile number) is not visible in the UI for Federated SMS OTP connector

Describe the issue:

When trying SMS OTP flow with Federated SMS OTP connector, the screen value is not visible in the UI even though the configurations are added.
How to reproduce:

Setup federated SMS OTP through the management console. (You have to enable the identity providers menu)
Add it to an application's login flow as the second factor.
Add the following config to the deployment.toml

[authentication.authenticator.sms_otp.parameters]
screenUserAttribute = "http://wso2.org/claims/mobile"
noOfDigits = 4

Restart the server and try login flow with the application.
Observe the OTP verification page.

Expected behavior:

Masked mobile number should be visible in the OTP verification page.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 7.0 and latest
OS: Mac
Database: H2

Support for both authenticators will be given with;

https://github.com/wso2/identity-apps/pull/6338


[Doc] Document that AUC and AUCPR are for binary classification/ranking

Addresses #5662.

Will add an error message after 1.2.0

Merging this now to update the docs. I've filed #6474 to remind myself to add an error message in the C++ code.


CLI for Maps API

This is a CLI for the Maps API.  I would be happy to make changes to the code, tests, etc.  Thank you!

@critical-path Thanks! I've put this on the 0.9.0 milestone so we have some time. Tag me if you need any help with the tests or resolving this merge conflict.

@perrygeo
I have resolved the merge conflict and removed unnecessary code from the features and metadata commands.  Please let me know if you would like additional changes.  Thank you!

@perrygeo
This is ready for review.  Thank you!


Fixing CreateResponseChoice text option for GPT4

Updating CreateResponseChoice to support gpt-4o model's responses

What:

[x] Bug Fix
[ ] New Feature

Description:
Using the new GPT 4o model, you can't use the completion()->createStreamed() method since response is now different.
A) The base API Url needs to be manually set to https://api.openai.com/v1/chat when declaring a new client.
B) The response from the completion includes "choices", but using GPT-4o model the text result now comes from $attributes['delta']['content'] instead of $attributes['test']

Hi @Dlas1212
The completions() endpoint is outdated and you have to use the chat() endpoint now. See: https://platform.openai.com/docs/api-reference/completions


[Feature Request] Postponed evaluation of stringified type hints

from beartype import beartype
from typing import Generic, TypeVar

T = TypeVar("T")

class Foo(Generic[T]):
    @beartype
    def bar(self) -> "Foo[T]":
        return self

Foo().bar()
# beartype.roar.BeartypeDecorHintForwardRefException: Forward reference "__main__.Foo[T]" syntactically invalid as module attribute name.

:(

...gah. You can't put anything over on @patrick-kidger. @beartype currently only supports the stricter (and ostensibly lamer) variety of forward references standardized by PEP 484: that is, forward references to a simple type that has yet to be declared.
Even though I'm pretty sure that full-blown postponed evaluation of arbitrarily complex stringified type hints was never standardized, the truth is irrelevant! @beartype should do this regardless. If we don't do this, then everyone will just use PEP 563 (i.e., from __future__ import annotations) instead. But nobody should use PEP 563, because PEP 563 fundamentally breaks Python in dark ways that are profoundly difficult (and costly) to repair at runtime.
That said... this is non-trivial. This isn't infeasible, because @beartype already does something like this to resolve arbitrarily complex type hints implicitly stringified by PEP 563. Still, we are surely enabling Hard Mode here. Let's ponder this as I stroke my beard stubble thoughtfully.

What makes this different to the existing PEP563 support?
I opened two separate issues for completeness but I was guessing this was just a different version of #218. (With stringification of only some annotations, rather than stringification of all of them.)

:sweat_smile:
Much apologies for my belated reply. It's been one of those weeks. Surprisingly, this feature request, #219, and #222 are all distinct issues. Submitting one issue for each was perfect on your part. We'll iteratively resolve each one until we exhaust ourselves and quietly give up.
Hard things are the things worth doing. Thankfully, this is probably the most important and easiest to fix of these issues. If we lightly rewrite your lead example as...
from beartype import beartype
from typing import Generic, TypeVar

T = TypeVar("T")

@beartype
class Foo(Generic[T]):
    def bar(self) -> "Foo[T]":
        return self

Foo().bar()

...then @beartype already has all of the local and global attributes it needs to fully resolve the stringified type hint "Foo[T]". Since Foo has already been declared by the time the @beartype decorator is invoked, there's no need for @beartype to defer the resolution of "Foo[T]". Instead, @beartype can just trivially resolve that hint immediately with an eval() call and generate the requisite type-checking code.
Let's tentatively slate this for beartype 0.14.0 – to be released sometime this Summer, surely! Who could doubt my words? We'll obsessively knuckle down on forward references and stringified type hints for that dev cycle.
Thanks yet again for all these stupendous issues, @patrick-kidger. Thumbs are way up. :+1:

Ah-ha! The recently released @beartype 0.14.0 effectively resolves this without actually resolving this. This isn't what anyone was expecting or actually wanted. @beartype surprises us all, because...
@beartype now fully supports PEP 673 (i.e., typing.Self) – the new gold standard for doing exactly what you want to do here. typing.Self is dramatically preferable to forward references and PEP 563 (i.e., from __future__ import annotations). typing.Self is a far faster, stabler, and more convenient API for type-checking classes self-referentially. We shill for typing.Self.
Take it away, minimal reproducible example (MRE)!
from beartype import beartype
from typing import Generic, TypeVar
from typing import Self  # <---------------- if Python ≥ 3.11.0
# from typing_extensions import Self   # <-- if Python < 3.11.0

T = TypeVar("T")

@beartype  # <-- "Self" requires @beartype on classes rather than methods.
class Foo(Generic[T]):
    def bar(self) -> Self:  # <-- That's what I'm talkin' 'bout, yo. Blam!
        return self

Foo().bar()

At runtime, @beartype now type-checks Foo.bar() as returning an instance of Foo. At static analysis time, mypy and friends type-check Foo.bar() as returning an object satisfying Foo[T]. Everyone is happy. No one is sad. This is surely the road to world peace in our time.
Thanks so much for your venerable patience, @patrick-kidger. @beartype will get you and the JAX community sorted "pronto." 1 :sweat_smile:
1. Definitions of "pronto" may vary by open-source supplier.

@beartype summons the ultimate destructive force to deal with this long-standing issue: apocalyptic anime exploding girl, go!

Resolved by 4f7115919c... but actually by a18d9a5a5da, which this issue turned out to be a duplicate of. I shall now summon my younger self circa last Friday night, who personally witnessed the tragic chain of events that ultimately lead to @beartype's redemption and this final resolution:
Younger Self Witnesses All, Now Tells Sad Story (Only on GitHub)
omg! OMG! OMGGGGG!!! @TeamSpen210: Your brilliant five-sentence abstract on the nature of Python vis-a-vis forward references actually worked! It actually worked, bro! Punch the air like you just don't care, 'cause that's what we're doin'.

Naturally, your "simpler approach" was horrifying.  I spent the entirety of my vacation doing this – and I don't even need this in production code. It just became a titanic struggle of @leycec versus @beartype versus Python: a three-way untelevised cage match that could only end with one man hurtling fifty feet onto another man lying prostrate on a table perched on top of another man curled in the fetal position while bleeding out live on GitHub.

...dat the best u can do, python?

wat is even happening here

When your masterplan only ends in tragedy for everybody.
Seriously. I've got five hundred-line comments devsplaining single one-liners. I've got 100KB of incomprehensible pure-Python isolated to four new submodules sprawled across a new subpackage devoted exclusively to inchoate madness. I've got abstract base classes, abstract metaclasses, dynamic type factories, dunder methods on sunder methods on abstract cached properties. I've got friggin' metaclass __getattr__() methods performing deferred module attribute importation via dynamic class attribute lookups of attributes that don't actually physically exist anywhere. I've got two whole dict.__missing__() implementations that don't even really have anything to do with one another. This is inchoate madness.
I don't even know how any of this works anymore. I've already jettisoned all knowledge pertaining to this topic so I can just sleep tonight without fitfully crying out in the night for my childhood stuffed octopus. I wish to awaken from the real-world nightmare I have unwittingly exposed myself to. It turns out Bloodborne is more a state of mind rather than a mere video game.

Python. It do be like that.
Forward references: do not go there, lest this animated reenactment of @leycec's life corrupt your once-pure essence.
I'm pretty sure (but not certain) that I may have inadvertently summoned the Eldritch She-God Shub-Niggurath, The Black Goat of the Woods with a Thousand Young, during the resolution of this feature request. I apologize, humanity. I'm so sorry! I didn't mean to open that portal. It just opened of its own accord while the guard cat – a fat Maine Coon named Nekali, of course – was indolently passed out on the shag carpeting.


Re-render with conda-smithy version 1.0.0

This is a re-rendering generated with conda-smithy version 1.0.0.
It provides a fix so that the Travis CI build will be skipped in this feedstock as this is Linux only.
Also it starts using conda-forge-build-setup to handle standard CI setup like what version of conda-build is used. This should allow us to more quickly get out in front of build issues that generally affect feedstocks.
Letting you know @pelson that I'm taking this for a spin.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


helm.sh/helm/v3 should use custom errors

In a perspective of a not supervised usage of the library, for example in an unattended flow where I would like to achieve idempotency, that is multiple calls to the application leads to the same result, the helm library should use custom errors, otherwise, I can't tell the difference between a network error or a release name conflict error.
For example, I would like to call multiple times helm.sh/helm/v3/pkg/action.Run with the same args, and then catch and manage this error cannot re-use a name that is still in use, since it is a built-in error all I can do is
helmDuplicateReleaseNameError := errors.New("cannot re-use a name that is still in use")
if _, err := myCallToActionRun(); err != nil || err.Error() == helmDuplicateReleaseNameError.Error() {
  // go ahead, do nothing bru, the chart is already installed
}

and that is really awful.

Enhancements to improve the SDK's usage in the form of a PR are always welcome. In this case it should be simple to create a concrete NameError similar to chart.ValidationError.
https://github.com/helm/helm/blob/f5ef87b96e791ca9971231699fc5af687f748bae/pkg/action/install.go#L435


Add usi support to strategy worker

Description
Add new "true constraint" on strategy worker to remove need for QBI.
Add self constraint on GSM worker to remove last QBI query.
The GSM was previously getting interest in the SKELETON_ENTITY_MANIFEST_COMPONENT_ID entities via a component constraint on the GSM entity. This has been reworked to give the GSM worker authority over a new tag component we add to the skeleton entity manifest entities, and then uses self-interest to gain interest in the rest of the entity.
I'll leave the QBI queries within the snapshot entities for now, until we fully shift to USI.

generally lgtm although I'm not sure I understood where the replacement USI queries for the previous unreal server QBI is defined here

Updated PR description to detail what's going on in more detail. Let me know if you want further clarification.


utils: make isEmptyObject check prototype #940

Before submitting a pull request, please verify the following:

[x] If you've added code that should be tested, please add tests.
[x] Ensure your code lints and the test suite passes (npm test).

Happy hacktoberfest 🎃

Thanks @shakeelmohamed! :)


Implement the controller logic for cloud-init output

/kind feature
Describe the solution you'd like
The output of this can be deduced from this paragraph in the cluster api proposal:

Upon receiving a Machine event, a reconcile request is enqueued for the associated KubeadmBootstrapConfig. Next, it retrieves the Machine, Cluster, and generates a cloud-init based bootstrap configuration which is then stored in KubeadmBootstrapConfig.Status.BootstrapData. It also sets KubeadmBootstrapConfig.Status.Phase to “Ready”. A non-nil value in KubeadmBootstrapConfig.Status.BootstrapData is indicative to the Cluster API Machine Controller that the bootstrap provider has completed its work.

This means cloud-init is the first output. This does NOT mean cloud-init is the only output but it's a good way for us to get started.
Anything else you would like to add:

Lets split this up in 2 parts:

[ ] Controller Logic
[ ] Generating cloud-init configuration

We can use this issue to just track the progress of the controller logic part.

/lifecycle active

/assign @amy

/assign

/milestone v0.1


stub supports void type return value

Hello!

Type: bug fix | new feature
Link to issue: https://github.com/phalcon/ide-stubs/pull/50
https://github.com/phalcon/zephir/issues/1977

In raising this pull request, I confirm the following:

[x] I have checked that another pull request for this purpose does not exist
[x] I wrote some tests for this PR
[ ] I updated the CHANGELOG

Small description of change:
I added it because I didn't consider the case where the return value is void type.
Thanks

https://github.com/phalcon/zephir/pull/2124/files#diff-65cb45c8a088c80568a2ac59ba3d3af54b18dea0bef35a757ac5d12db433f306R304-R309
Should I also erase this?

https://github.com/phalcon/zephir/blob/development/Library/Stubs/Generator.php#L304-L309
Should I also remove this?

No, It should be removed with small refactoring later. Thank you.

okay. Thank you.

Thank you


Email notifications: clicking workflow attachments doesn't work if you aren't logged in

I received the following email notification for a task that had been rejected:

Resource name
Knitting koramns

Owner
Internal Demonstration System Administrator (int.demosysadmin)

Rejected task
Redundant Turkeys

Rejection reason
"See me after class.One of the worst things i have ever seen. I quit, sick of this tom foolery" by Internal Demonstration System Administrator (int.demosysadmin)

Rejection attachment
http://charliedesk:8080/vanilla/workflow/message/d4e639b5-9494-4b8b-8a9e-6390ab4e41ad/selma%26^ sandwich.png

Current task
Clean litterbox

Moderate

Due date
22/09/2017

When clicking the rejection attachment link you have to be logged in already for it to work. If you aren't logged in it should be redirecting you to the equella login screen

Best workflow and rejection message ever :)

Fixed


Content between TOC and next header gets removed

If you have content between the TOC header and the next header, the plugin will remove it.
Exemple:
## Table of Contents

Some text here...

## First title

In this example, Some teext here... will get removed.
I think this can be fixed by changing this line:
node.children.slice(result.index)
to
node.children.slice(result.endIndex)

Why do you think that’s a bug? IMO it’s a feature 🤷♂ What else would you like to put in a toc?

I think I was not clear enough...
Let's say you have this markdown:
## Table of Contents

This is my intro text, explaining what is on this page, lorem ipsum dolor sit amet.

## Title One
### Sub title A

Some text from Sub title A

### Sub title B

Some text from Sub title B

I would expect, with the ToC plugin, to end up with something like this:
## Table of Contents
## Title One
### Sub title A
### Sub title B

This is my intro text, explaining what is on this page, lorem ipsum dolor sit amet.

## Title One
### Sub title A

Some text from Sub title A

### Sub title B

Some text from Sub title B

But I end up with:
## Table of Contents
## Title One
### Sub title A
### Sub title B

## Title One
### Sub title A

Some text from Sub title A

### Sub title B

Some text from Sub title B

The intro text gets remove.

Hmm, from all the tables of contents I’ve seen I think that they only house a list of the content. I don’t think I’ve seen alternative content being used.
Why not go with:
...

This is my intro text, explaining what is on this page, lorem ipsum dolor sit amet.

## Table of Contents

* Title One
  * Sub title A
  * Sub title B

## Title One
### Sub title A

Some text from Sub title A

### Sub title B

Some text from Sub title B

...

Well, this can be done this way of course. But I still think this is a bug, and it can be fixed quite easily.
Paragraphs between ToC and first title should not simply disappear IMO.

Currently we’re looking for a heading and replacing the whole content of that “section”. The same is done for remark-usage and remark-license. It’s used throughout the ecosystem.
Alternatively, we could look for comments, called “ranges”. See mdast-zone for more info. I believe that would be able to do what you want. I’m sure a PR to BarryThePenguin/mdast-util-toc for that support would be OK (this plugin is just a small wrapper around that).

Feel free to open a PR there if you’d like to add this new feature.
I don’t see your report as a bug though.

I have the same problem right now. I want to have some intro text after the ToC without its own heading. Is there a way to achieve this?

My workaround, for now, is to add an "Intro" header to the intro section, let remark-toc skip it:
.use(remarkToc, {skip: 'Intro'})

And then I hide the h2 tag with CSS (I wanna keep the empty space):

.blogPostContainer :global(h2#intro) {
    visibility: hidden;
}

The same response (https://github.com/remarkjs/remark-toc/issues/18#issuecomment-406615797) still holds.

@pascal-mugnier-sonarsource I created my won function to use as a plugin and shared it here: https://github.com/remarkjs/remark-toc/issues/40#issuecomment-1721880079