Support updating federated role

Signed-off-by: yeya24<EMAIL_ADDRESS>Fixes https://issues.redhat.com/browse/OSD-4235
Usage
osdctl federatedrole apply -u <URL>

osdctl federatedrole apply -f <yaml file>

@fahlmant One thing I am not sure, do I need to update the specified federated role cr in this command?
If not, users need to do something like oc apply -f <file> and then osdctl federatedrole apply -f <file>

@yeya24 If you look at the done criteria, that is outlined in the first point
osdctl can grab a Federated Role CR at a supplied url and apply it

I'm not sure how best to test this. @tfahlman, do you mind taking a look here again when you get a chance?

I think you tagged the wrong person :)

Doh!  I meant to tag @fahlmant!
Same question: I'm not sure how to test this - do you mind taking a look here again when you get a chance?


frozen at location verification screen

after verification of location, I receive a notification that  says, Please try again, Hotspot miner is waiting to start.
done this from two different helium apps, one an ios, the other from galaxy Tab A.
at that point miner, all lights remain active,, except blue,  but Bluetooth does not respond, cannot reconnect without restarting unit, even holding Bluetooth reset, will not function.
Apple SE and Galaxy tabA
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

This sounds like an issue with the Helium App. You will need to report that at their repo

forgot to add tried, with both direct ethernet connection, and wifi connection, to  different network router, one a cell based router, and the second router linksys, connected through a LowRan type of service.


filled in shortest paths page and changed up dijkstra's to have better explanations

woot 🎉 glad to see more 🔥 explanations


PostInstallation script

@zimbatm would you mind explaining this line to me ?
Are you sure the postinstall.sh script is executed ?
Here is my output:
    vmware-iso: building the configuration in /mnt/etc/nixos/configuration.nix...
    vmware-iso: copying channel...
    vmware-iso: installing the boot loader...
==> vmware-iso: setting up /etc...
==> vmware-iso: updating GRUB 2 menu...
==> vmware-iso: installing the GRUB 2 boot loader on /dev/sda...
==> vmware-iso: Installing for i386-pc platform.
==> vmware-iso: Installation finished. No error reported.
    vmware-iso: installation finished!
    vmware-iso: building the configuration in /mnt/etc/nixos/configuration.nix...
==> vmware-iso:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
==> vmware-iso:                                  Dload  Upload   Total   Spent    Left  Speed
==> vmware-iso: 100   618  100   618    0     0  18176      0 --:--:-- --:--:-- --:--:-- 18176
    vmware-iso: copying channel...
    vmware-iso: installing the boot loader...
==> vmware-iso: setting up /etc...
==> vmware-iso: updating GRUB 2 menu...
==> vmware-iso: installing the GRUB 2 boot loader on /dev/sda...
==> vmware-iso: Installing for i386-pc platform.
==> vmware-iso: Installation finished. No error reported.
    vmware-iso: installation finished!

The installer is running twice. Is this intended ?
Thx

If I replace the line with
curl "$packer_http/postinstall.sh" | sh

Then I see the postinstall script output.

The script is supposed to be executed within the nixos chroot. It's possible that the fix here didn't do what was intended: https://github.com/nix-community/nixbox/commit/ba8b646ada9fae88c188e05e49b310cf4c7d9065

Just submit a fix. I guess this  need to be nix-enter. See https://github.com/NixOS/nixpkgs/issues/34033

yeah good call, looks like curl "$packer_http/postinstall.sh" | nixos-enter should do the trick.


adding commons lib dependency

@zabil @rajiesh — why do we not use maven for managing deps here? Checking in such binaries seems like a slow painful process, for one we don't know which libs are actually used, which are direct vs indirect dependencies etc.
If gauge needs libs in the libs/ dir can't we mvn dependency:copy-dependencies to the libs/ dir instead before running gauge tests?
Thoughts?

I tried out with exactly that using copy-depedencies and some dependency broke the test with sahi not booting up.
I also think I did it wrong. Instead of converting all the libs we must do it one by one using the mvn depedency:.. task and once everything with the current versions work fine start upgrading the versions of the lib one by one too.
Let's try that out

@ketan Last release tried making functional test to be managed by maven, had some issues, this release am taking up this task to make functional test into maven based project, so that we dont have to run into this again


Check text of changes in UPDATING.md, make it easier to understand

https://github.com/apache/superset/pull/19480

Closing, as I've approved John's PR!


feat(runtime): ✨ Add a a new module module

What is the purpose of this Pull Request?
Adds a new module module for snippets related to modules/dependencies/packages.
Type of this Pull Request

✨ Implementing a new feature
📝 Documentation update

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

60 of 66 (90.91%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 95.944%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/runtime/source/module/module.ts
60
66
90.91%

Totals

Change from base Build<PHONE_NUMBER>:
-0.2%

Covered Lines:
2086

Relevant Lines:
2138

💛  - Coveralls


check box click is not working for amount received with value as credit under invoices

check box click is not working for amount received with value as credit under invoices.but click is happening on the text "mark as fully paid"

issue fixed !


graph/spectral: need to differentiate symmetric and non-symmetric Laplacian matrices

There are currently three functions that return a Laplacian. The Laplacian type holds an embedded mat.Matrix, however, two of the functions return a symmetric Laplacian. This makes the API less than friendly for users who want to get the eigenvalues for an undirected graph, since they either need to assert the embedded matrix to a mat.Symmetric, or perform a non-symmetric Eigen decomposition and then convert all the complex values to real values.
To fix this, add SymmetricLaplacian which embeds mat.Symmetric and return this from NewLaplacian (renamed to NewSymmetricLaplacian) and NewSymNormLaplacian.

This is harder than I thought. Both types need to be consumable by the network.Diffusion* functions.


code for question 9

read additional comments

i suggest commiting the required changes then

anyways i have corrected that now.


Feature/jdw.import.pulls

Pulls in several PRs from Pablo's repo that seem to be both valid & important

Looks good

whoops, thought this was on my fork. must have missed a setting.


Found flag "nographics" with value "".

I tried more recent versions of the builder and had the following error
Found flag "nographics" with value "".
ArgumentException: An item with the same key has already been added. Key: nographics
  at System.Collections.Generic.Dictionary`2[TKey,TValue].TryInsert (TKey key, TValue value, System.Collections.Generic.InsertionBehavior behavior) [0x000c1] in <fb001e01371b4adca20013e0ac763896>:0
  at System.Collections.Generic.Dictionary`2[TKey,TValue].Add (TKey key, TValue value) [0x00000] in <fb001e01371b4adca20013e0ac763896>:0
  at UnityBuilderAction.Input.ArgumentsParser.ParseCommandLineArguments (System.Collections.Generic.Dictionary`2[System.String,System.String]& providedArguments) [0x0011b] in /github/workspace/Assets/Editor/Editor/Input/ArgumentsParser.cs:76
  at UnityBuilderAction.Input.ArgumentsParser.GetValidatedOptions () [0x00000] in /github/workspace/Assets/Editor/Editor/Input/ArgumentsParser.cs:15
  at UnityBuilderAction.Builder.BuildProject () [0x00000] in /github/workspace/Assets/Editor/Editor/Builder.cs:17

Solution was to remove customParameters: "-nographics" because it is now included by default.
Example fix to be done in your pipeline file if you encounter this:
commit c32b57adb1b22bd13b10f13a72f38c7635051a55
Author: Gabriel Le Breton<EMAIL_ADDRESS>Date:   Mon Jan 4 14:02:42 2021 -0500

    Remove extra 'customParameters: "-nographics"'

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 35163a6..c8e670f 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -97,7 +97,6 @@ jobs:
           projectPath: ${{ env.PROJECT_PATH }}
           unityVersion: ${{ env.UNITY_VERSION }}
           targetPlatform: ${{ matrix.targetPlatform }}
-          customParameters: "-nographics"
       - uses: actions/upload-artifact@v2
         with:
           name: Build

Solution was to remove customParameters: "-nographics" because it is now included by default.
Example fix to be done in your pipeline file if you encounter this:
commit c32b57adb1b22bd13b10f13a72f38c7635051a55
Author: Gabriel Le Breton<EMAIL_ADDRESS>Date:   Mon Jan 4 14:02:42 2021 -0500

    Remove extra 'customParameters: "-nographics"'

diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml
index 35163a6..c8e670f 100644
--- a/.github/workflows/main.yml
+++ b/.github/workflows/main.yml
@@ -97,7 +97,6 @@ jobs:
           projectPath: ${{ env.PROJECT_PATH }}
           unityVersion: ${{ env.UNITY_VERSION }}
           targetPlatform: ${{ matrix.targetPlatform }}
-          customParameters: "-nographics"
       - uses: actions/upload-artifact@v2
         with:
           name: Build


PieArcSeries should not have a Doughnut property

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[x] Other... Please describe:

Current behavior

The PieArcSeries has a Doughnut property which affects how the pie chart is rendered
Expected behavior

This does not really make sense, either you implicitly set the arcWidth or innerRadius or you will pass explicitly a DonutArcSeries which has the properties

What is the motivation / use case for changing the behavior?

imho it is just bad api design
Environment

Libs:
- react version: X.Y.Z
- reaviz version: X.Y.Z

Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: XX
- Platform:

Others:

I get it - its more of a shortcut for users who don't understand that. To be frank, I'm not sure I would have figured that w/o reading docs and I'm the author of the lib.


Add "pailer" type functionality to overlord console

Mesos has a really cool pailer used to handle their task logs from the master console. It would be awesome if we could borrow that functionality for the druid overlord console.
The general idea being that the task's logs can be "streamed" to an observer operating in the overlord console.

I believe that https://github.com/apache/incubator-druid/pull/7703 addresses this


Add support for nodejs module resolution

Creating a nodejs repl and importing stuff from @replit/extensions or @replit/extensions/react doesn't work since everything but nodejs module resolution works.

Have you checked type defs for @replit/extensions/react with this change? Wondering if we should add tests for both

Type definitions still work in the example folder 👍🏽

Sweet, thanks for following up!


Add cublicfm support

Add cublicfm support
Tidy up connectors.js

What would be a better way to check to see if the app has booted? At the moment I just setup a MutationObserver to watch for the injected code which works.
refs #801

I prefer MutationObservers too, so this is totally ok ;-)


docs: adding timeout to the typha server TLS handshake

Product Version(s):

Issue:

https://github.com/projectcalico/calico/issues/7908
https://github.com/projectcalico/calico/pull/7909

Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@rodrigorfk Your first contribution! Thank you for being engaged in Calico docs. I've assigned a SME to review it.

Change looks good, great of you to seek out and update the docs!  Just waiting for the code change PR to be approved before this is ready to merge.

@rodrigorfk Please copy the doc changes to calico root level folder (3.27) and then rebase. Then I'll merge it.

@rodrigorfk The change you have also apply to Calico Open Source docs. Please copy the doc changes to calico root level folder (3.27) and then rebase. Then I'll merge it.

done @bmckercher123, I hope that is the correct file for the Open Source version.


Update template.yml

Modified g512xl and 12xl to g4dn12xl instance type
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thank you for submitting this PR. We will add this functionality but in a slightly different way. Will make the instance type configurable so that the user can select from a drop down list. That ways, we don't have to replace one hardocded value with another one. Will update this PR when that functionality is available (should be very soon). Closing this for now.


ALT button activates when pressing CTRL + D

Description
Every time I look to price check an item using CTRL + D it activates my push to talk key on ALT as well.
Windows 11
Reproduction steps
CTRL + D on item. Alt also activates.
Screenshot

The application presses the alt key to get advanced item descriptions when it copies the items. At this time I am not probably going to change this. I will add this to backlog for once it is more working overall


Drop Support for Ruby 1.x

Prompted by a failing TravisCI-Build, I come to question whether we still want to support older Ruby-Versions going forward. Since the old gems are still present, I do not see any harm. Strictly speaking, we could even limit ourselves to only currently supported ruby-versions. However, since there is no technical reason to do so, I would not go that far.
What do you think, @ohadlevy @witlessbird @svenfuchs ?

Agree, no reason to support 1.x rubies. Need to take a look if there's any 1.x-specific code that can be removed as well.

Merged, thanks @kronn.


[Widget fix] Check for instance of Blob rather than File

Closes #404 Follow up to #297
Widgets can send work with either Blob or File. For instance, here blob is created. However, the previous instanceof check was checking for File only. When the instanceof Blob, the check was failing;

Closing in favour for #405


(maint) vpc_only_account? logic improvements

Clean up code to provide a more self-descriptive mechanism
for finding VPC only accounts.
With clasic accounts, account_types is ["EC2", "VPC"] while
a VPC only account has the values ["VPC"].  It's possible
that there could be other / legacy account types that have
a different list of supported-platforms, or that this
changes in the future.

@zreichert / @garethr - quick PR on how vpc account detection is being performed.  Related, I think this should be memoized, since a Puppet run will only ever be run with a single AWS account.

+1
This is a good model for determining account capabilities.  AWS may add new account types in the future.


Improve code generating kjvbible_x10.txt

Fair enough, but I dislike programming in bash so tend to opt for KISS solutions, and push programming to Python etc. :-)


When creating multiple rooms, the UI does not always update

This seems more prominent when using the /create command, rather than the button. I can create a few rooms, but once they have some messages in them it seems that when I try to go and create another room it is successful but doesn't show.
e.g.
Creating Rooms
/create a --> Success
/create b --> Success
Sending Messages
hello from b --> Success
hello again from a --> Success
Go to lobby again
/create c --> Failure (UI doesn't update)
/create c --> HubException: c already exists

Turns out this is a result of #113, as soon as you send a message that error is hit and that invalidates the execution of SignalR, so the UI can't stay up to date.
Closing this.


[ASK] enable cuda with manual compilation

Hi,
According to the llama.cpp github repo, it's now possible to use cuda from nvidia gpu by using cuBLAS build.
So you may got where I want to come, how to do Manual compilation with using make or cmake args to enable LLAMA_CUBLAS :)
greeting

Hi, I plan to support this CUDA feature in the near future. Thanks for your suggestion.

this issue is pending new llama sampling logic here https://github.com/Atome-FE/llama-node/issues/36

currently this issue is pending statically linking problem from llama.cpp cmake
https://github.com/ggerganov/llama.cpp/pull/1128#issuecomment-1531661524

I can compile with this :
let command = command
        .arg("..")
        .arg("-DCMAKE_BUILD_TYPE=Release")
        .arg("-DLLAMA_OPENBLAS=ON")
        .arg("-DLLAMA_CUBLAS=ON")
        .arg("-DLLAMA_SHARED_LIBS=ON")
        .arg("-DLLAMA_STATIC=ON")
        .arg("-DLLAMA_ALL_WARNINGS=OFF")
        .arg("-DLLAMA_ALL_WARNINGS_3RD_PARTY=OFF")
        .arg("-DLLAMA_BUILD_TESTS=OFF")
        .arg("-DLLAMA_BUILD_EXAMPLES=OFF")
        .arg("-DCMAKE_POSITION_INDEPENDENT_CODE=ON");

but as a result, openblas is not activated, and cublas seems not be activated too, it's don't use my gpu
and worst, I've compiled llama.cpp from the github source, blas work fine, but clblast and cublas don't.
it's put some data in the vram, but it's still don't use the gpu, only the cpu
So I think we should wait a little bit for an update from llama.cpp

@tchereau great work. i was stuggling for fPIC error for several hours and only solved by dynamic linking. thanks for your investigation.
but its true that cublas flag doesnt accelerate the evaluation properly. we have to wait a while.

I can compile with this :
let command = command
        .arg("..")
        .arg("-DCMAKE_BUILD_TYPE=Release")
        .arg("-DLLAMA_OPENBLAS=ON")
        .arg("-DLLAMA_CUBLAS=ON")
        .arg("-DLLAMA_SHARED_LIBS=ON")
        .arg("-DLLAMA_STATIC=ON")
        .arg("-DLLAMA_ALL_WARNINGS=OFF")
        .arg("-DLLAMA_ALL_WARNINGS_3RD_PARTY=OFF")
        .arg("-DLLAMA_BUILD_TESTS=OFF")
        .arg("-DLLAMA_BUILD_EXAMPLES=OFF")
        .arg("-DCMAKE_POSITION_INDEPENDENT_CODE=ON");

but as a result, openblas is not activated, and cublas seems not be activated too, it's don't use my gpu
and worst, I've compiled llama.cpp from the github source, blas work fine, but clblast and cublas don't. it's put some data in the vram, but it's still don't use the gpu, only the cpu
So I think we should wait a little bit for an update from llama.cpp

Hi, I think you can compile with this, but can you run it actually? I got an error related to cudaLaunchKernel. I think there should be something abnormal with static linking. As a consequence, I m going to just provide a way for dynamic linking, but will not offer it as default prebuilt binary.

I can compile with this :
let command = command
        .arg("..")
        .arg("-DCMAKE_BUILD_TYPE=Release")
        .arg("-DLLAMA_OPENBLAS=ON")
        .arg("-DLLAMA_CUBLAS=ON")
        .arg("-DLLAMA_SHARED_LIBS=ON")
        .arg("-DLLAMA_STATIC=ON")
        .arg("-DLLAMA_ALL_WARNINGS=OFF")
        .arg("-DLLAMA_ALL_WARNINGS_3RD_PARTY=OFF")
        .arg("-DLLAMA_BUILD_TESTS=OFF")
        .arg("-DLLAMA_BUILD_EXAMPLES=OFF")
        .arg("-DCMAKE_POSITION_INDEPENDENT_CODE=ON");

but as a result, openblas is not activated, and cublas seems not be activated too, it's don't use my gpu
and worst, I've compiled llama.cpp from the github source, blas work fine, but clblast and cublas don't. it's put some data in the vram, but it's still don't use the gpu, only the cpu
So I think we should wait a little bit for an update from llama.cpp

Hi, I think you can compile with this, but can you run it actually? I got an error related to cudaLaunchKernel. I think there should be something abnormal with static linking. As a consequence, I m going to just provide a way for dynamic linking, but will not offer it as default prebuilt binary.

well yes I can compile, but can't run it
pnpm build:llama-cpp

><EMAIL_ADDRESS>build:llama-cpp /root/git/llama-node
> pnpm run --filter=@llama-node/llama-cpp cross-compile

><EMAIL_ADDRESS>cross-compile /root/git/llama-node/packages/llama-cpp
> rimraf @llama-node && tsx scripts/cross-compile.mts

info: component 'rust-std' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rust-std' for target 'x86_64-unknown-linux-musl' is up to date
warning: /root/git/llama-node/Cargo.toml: unused manifest key: workspace.package.name
/bin/sh: 1: zig: not found
warning: /root/git/llama-node/Cargo.toml: unused manifest key: workspace.package.name
    Blocking waiting for file lock on build directory
   Compiling llama-sys v0.0.1 (/root/git/llama-node/packages/llama-cpp/llama-sys)
   Compiling llama-node-cpp v0.1.0 (/root/git/llama-node/packages/llama-cpp)
warning: value assigned to `id` is never read
   --> packages/llama-cpp/src/context.rs:189:17
    |
189 |         let mut id = 0;
    |                 ^^
    |
    = help: maybe it is overwritten before being read?
    = note: `#[warn(unused_assignments)]` on by default

warning: `llama-node-cpp` (lib) generated 1 warning
    Finished release [optimized] target(s) in 55.77s
   Compiling llama-sys v0.0.1 (/root/git/llama-node/packages/llama-cpp/llama-sys)
   Compiling llama-node-cpp v0.1.0 (/root/git/llama-node/packages/llama-cpp)
warning: value assigned to `id` is never read
   --> packages/llama-cpp/src/context.rs:189:17
    |
189 |         let mut id = 0;
    |                 ^^
    |
    = help: maybe it is overwritten before being read?
    = note: `#[warn(unused_assignments)]` on by default

warning: `llama-node-cpp` (lib) generated 1 warning
    Finished release [optimized] target(s) in 1m 34s

nodejs:
node .
node:internal/modules/cjs/loader:1338
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /root/git/llama-selfbot/node_modules/llama-node/node_modules/<EMAIL_ADDRESS>undefined symbol: cublasSetMathMode
    at Module._extensions..node (node:internal/modules/cjs/loader:1338:18)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/root/git/llama-selfbot/node_modules/llama-node/node_modules/@llama-node/llama-cpp/index.js:188:31)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.16.0

and with clblast:
pnpm build:llama-cpp

><EMAIL_ADDRESS>build:llama-cpp /root/git/llama-node
> pnpm run --filter=@llama-node/llama-cpp cross-compile

><EMAIL_ADDRESS>cross-compile /root/git/llama-node/packages/llama-cpp
> rimraf @llama-node && tsx scripts/cross-compile.mts

info: component 'rust-std' for target 'x86_64-unknown-linux-gnu' is up to date
info: component 'rust-std' for target 'x86_64-unknown-linux-musl' is up to date
/bin/sh: 1: zig: not found
warning: /root/git/llama-node/Cargo.toml: unused manifest key: workspace.package.name
warning: /root/git/llama-node/Cargo.toml: unused manifest key: workspace.package.name
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
   Compiling llama-sys v0.0.1 (/root/git/llama-node/packages/llama-cpp/llama-sys)
   Compiling llama-node-cpp v0.1.0 (/root/git/llama-node/packages/llama-cpp)
warning: value assigned to `id` is never read
   --> packages/llama-cpp/src/context.rs:189:17
    |
189 |         let mut id = 0;
    |                 ^^
    |
    = help: maybe it is overwritten before being read?
    = note: `#[warn(unused_assignments)]` on by default

warning: `llama-node-cpp` (lib) generated 1 warning
    Finished release [optimized] target(s) in 49.25s
   Compiling llama-sys v0.0.1 (/root/git/llama-node/packages/llama-cpp/llama-sys)
   Compiling llama-node-cpp v0.1.0 (/root/git/llama-node/packages/llama-cpp)
warning: value assigned to `id` is never read
   --> packages/llama-cpp/src/context.rs:189:17
    |
189 |         let mut id = 0;
    |                 ^^
    |
    = help: maybe it is overwritten before being read?
    = note: `#[warn(unused_assignments)]` on by default

warning: `llama-node-cpp` (lib) generated 1 warning
    Finished release [optimized] target(s) in 1m 20s

nodejs:
node .
node:internal/modules/cjs/loader:1338
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /root/git/llama-selfbot/node_modules/llama-node/node_modules/<EMAIL_ADDRESS>undefined symbol: clBuildProgram
    at Module._extensions..node (node:internal/modules/cjs/loader:1338:18)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12)
    at Module.require (node:internal/modules/cjs/loader:1141:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at Object.<anonymous> (/root/git/llama-selfbot/node_modules/llama-node/node_modules/@llama-node/llama-cpp/index.js:188:31)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.16.0

same with .arg("-DLLAMA_OPENBLAS=ON") only
undefined symbol: cblas_sgemm
in all cases, the problem seem to be library who are not linked
at this point, I can't help, because I don't have the knowledge in C/rust

oops, will reopen and leave this until static linking is ready someday...
currently only provide a self built dynamic linking version.

https://llama-node.vercel.app/docs/cuda
a manual compilation guide has been provided here


I suggest CI travis tests

Your project looks interesting, and I hope it grows to the point I can retire health_check from active development - the legacy baggage has grown.
I suggest a CI auto test that builds a rails app, includes this gem and then checks everything works.
I have added a comment " HealthBit - inspired by this gem but with a fresh start as a simpler rack only application, no travis CI tests (yet?) but looks interesting" to my health_check gem README to cross link.

This project uses github actions. HealthBit is a simple rack function, which returns status code, headers and body. There is no need to test it with rails.

I didn't twig you had Ci vi github actions. If I understand you correctly, you don't health check rails then, since you don't need to test against it.


Edit REPL line in editor

readline has this, but haskeline doesn't. When opening issues etc it'd be quite nice.
(If this ends up being an upstream change to haskeline, ghci benefits too!)
(I dream one day of functions being allowed to provide templates for their arguments, and then the editor being prepopulated with these. But that shall be done in the Future Indefinite.)

Can you provide more detail about this?  So it's some key combination that opens the current line in $EDITOR?  What's the standard binding for this.
Doesn't look like Haskeline has much support for custom keybindings, maybe.  We'll probably have to move away from it / enhance it at some point anyway.


Feature request: parse the value from masked variable

This is a great library.
Is there a convenience way to parse the masked variable?
eg.
tel = '(555) 165-1591';
any build-in method to parse it to number?
Since the RegExp is set, it is nice to have it in the same library.

solution may be
var numbers = parseInt( '(555) 165-1591'.replace(/[^\d]/g, "") );

The library does not provide built-in support for unmasking the value.
See here for previous dicussion on the subject.


Techdebt: Get regions from SSM instead of Boto3

Fixes #6078
Moto used, for the vast majority of services, the botocore.get_available_regions-method to determine in what regions a particular service is available.
This method was always a bit flaky - it would take along time for new services to be available, and every now and then a new release would break the list for an existing service.
AWS' recommendation is to use the SSM parameter store instead, to determine per-region availability - see https://github.com/aws/aws-sdk/issues/206#issuecomment-1471354853

Note that we're duplicating the regions for every service. The alternative would be that every service searches the entire SSM parameter store manually, which has a significant performance impact.

Marking this as draft, as this is a fairly large change, and I think I want to make this a minor version release (4.2.0)

Maybe I'm not understanding the issue correctly, but here are some thoughts on this:

This is only a problem for people using moto in server mode, right?  I mean, if they're using Python and botocore, they're not going to be able to create a client for a service in a particular region unless it exists in the get_available_regions method response in the first place.
If they're using a different SDK (e.g. Java) and they create a client for a service/region that is not listed in get_available_regions for whatever version of botocore is pulled in by moto, then presumably moto will raise an error.  But we already have a solution to this in the form of the MOTO_ALLOW_NONEXISTENT_REGION setting, right?
botocore already provides a method for overriding the default endpoints.json file that ships with the package.  You can drop your own JSON file (with whatever regions you want to add/customize) into ~.aws/models.  Seems reasonable for moto to require someone spinning up a moto server to drop in their own endpoints.json file if they're using new/exotic/experimental regions that aren't yet shipping with botocore (or, alternately, just spin up the server with MOTO_ALLOW_NONEXISTENT_REGION=true).
I don't see how your proposed solution actually solves what I perceive the core issue to be--namely, that the endpoints.json file that ships with botocore isn't always up-to-date.  Unless I'm missing something entirely, this solution seems to be proposing a separate, difficult-to-keep-updated file for every service!

Hey @bpandola, thanks for taking the time to look at this!
Regarding your first point: this is a problem for everyone, because botocore does not validate the region. For example, AMP (Prometheus) is not available in me-central-1, so running this code:
m_east = boto3.client("amp", "me-central-1")
m_east.list_workspaces()

Will actually try to connect to a non-existing URL:
socket.gaierror: [Errno -2] Name or service not known
During handling of the above exception, another exception occurred:
[...]
botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "https://aps.me-central-1.amazonaws.com/workspaces"

The core issue is the fact that get_available_regions may be deprecated in the future: see https://github.com/aws/aws-sdk/issues/206#issuecomment-1471354853
Most notably:
[T]he Python SDK team is currently investigating paths forward for [get_available_regions()], and deprecation is one possible outcome.
If completeness and recency of information is important for your use, switching to the SSM API is, and has been, the recommended approach.
The fact that endpoints.json is sometimes out of date, incomplete, or removes data inbetween versions is a nuisance - but if/when get_available_regions is no longer available, we will always be forced to switch to a different solution. And we may as well find a different solution now, rather then waiting for things to break!

Regarding the separate, difficult-to-keep-updated file-part: I agree that it's not particularly pretty.
However, the file is automatically generated by running scripts/ssm_get_default_params.py, which runs as a cron-job every week - so keeping it in sync is just a matter of merging an automated PR every week.

botocore already provides a method for overriding the default endpoints.json file that ships with the package. You can drop your own JSON file (with whatever regions you want to add/customize) into ~.aws/models

I didn't know this! However, if get_available_regions is deprecated, I assume that endpoints.json will also be deprecated/removed? Considering there is no region-based validation at runtime, maybe that data is only used to power get_available_regions.


texinfo: encourage @prompt{} if people want to use >> within texinfo mode

Some comments from other discussions, just consolidating as we may want to think more about this in the future.

I had thoughts to render >> grey and non-selectable

I did this once for examples in the wiki. It has been a burden to maintain. In TexInfo you could use a @prompt{} macro, but you probably have to redefine in in every function header.

Also @oheim said:

I also think we should not encourage to mix the styles. The problem that arises here (for the diary style) is that you cannot test the following without an addition @result{}:

>> disp ('=>')
=>

See this comment for explicitly how to do @prompt{}.

My title sounds more confident than I am on this topic.  Anyway, no hurry for this.

meh, I've personally stopped using >> within texinfo.  I think I'll close this.  Discussion and links are all here if anyone cares in the future.


Update zio-sbt-ci, zio-sbt-ecosystem, ... to 0.4.0-alpha.21

About this PR
📦 Updates

dev.zio:zio-sbt-ci
dev.zio:zio-sbt-ecosystem
dev.zio:zio-sbt-website

from 0.4.0-alpha.6+40-c57e764c-SNAPSHOT to 0.4.0-alpha.21
📜 GitHub Release Notes
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: sbt-plugin-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #263.


New plugins geospatial, dashboard-maps need to be added to  2.2 release

Is your feature request related to a problem? Please describe
We are adding two new plugins

geospatial (backend): https://github.com/opensearch-project/geospatial
dashboard-maps(frontend): https://github.com/opensearch-project/dashboards-maps

Describe the solution you'd like
These plugins will be used for building new Geo features. For the 2.2 release, we are launching custom geojson feature. Infra teams help needed to consider these plugins in release process from 2.2 release onwards.
Describe alternatives you've considered
No response
Additional context
No response

Please PR into the manifest!

@peterzhuamazon Can you add the current state of the on-boarding process for these plugins here?

We just approved multiple PRs:
https://github.com/opensearch-project/geospatial/pull/119
https://github.com/opensearch-project/opensearch-build/pull/2411
https://github.com/opensearch-project/opensearch-build/pull/2418
https://github.com/opensearch-project/opensearch-build/pull/2419
https://github.com/opensearch-project/dashboards-maps/pull/27
https://github.com/opensearch-project/opensearch-dashboards-functional-test/commit/b4a1f7a1cba7514eccb91a1cc5df807de5d214de
It is currently on both manifests will check results tomorrow.
Thanks.

Closing this issue as we have releases the plugins in 2.2.0 version.


eth_newFilter errors out when passing more than 1 address in the parameter

Description
This request in websocket errors out with "Invalid request", with HTTP it responds with "method not found"
{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "eth_newFilter",
    "params": [
        {
            "fromBlock": "0x473EE5",
            "toBlock": "latest",
            "address": [
                "0x2bfe6dd9585d25c5b00308f21e1b09e91604a082",
                "0xf3cb5ee98c1e60f60d99da7c240fdc0ab7668bfd"
            ],
            "topics": [
                "0x0559884fd3a460db3073b7fc896cc77986f16e378210ded43186175bf646fc5f"
            ],
        }
    ]
}```

### Steps to reproduce

{
"jsonrpc": "2.0",
"id": 1,
"method": "eth_newFilter",
"params": [
{
"fromBlock": "0x473EE5",
"toBlock": "latest",
"address": [
"0x2bfe6dd9585d25c5b00308f21e1b09e91604a082",
"0xf3cb5ee98c1e60f60d99da7c240fdc0ab7668bfd"
],
"topics": [
"0x0559884fd3a460db3073b7fc896cc77986f16e378210ded43186175bf646fc5f"
],
}
]
}```
Additional context
No response
Hedera network
testnet
Version
v0.48.1
Operating system
None

So eth_newFilter is being implemented in WS server in this PR https://github.com/hashgraph/hedera-json-rpc-relay/pull/2553.
For HTTP, when I tried the exact above request against testnet and got
{
    "error": {
        "code": -32000,
        "name": "Block range too large",
        "message": "[Request ID: 6a9d84af-7462-4817-bae0-411608b7a7d2] Exceeded maximum block range: 1000"
    },
    "jsonrpc": "2.0",
    "id": "1"
}

instead of method not found. Could you please tell me how you got method not found?


[Enhancement] Show errors

That would be great if plyr showed playback errors if it can't load the source, or can't play the video.

Errors aren't /shown/ currently but the events do bubble up so you can listen for them...
Sam

On 13 Jan 2017, at 7:56 pm, binarynos<EMAIL_ADDRESS>wrote:
That would be great if plyr showed playback errors if it can't load the source, or can't play the video.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


ipv6 lost

Hello. Just updated homebridge-config-ui-x to 4.0.2 and lost connectivity to web interface: home bridge listen only on ipv4.
tcp        0      0 <IP_ADDRESS>:443             <IP_ADDRESS>:*               LISTEN      22230/homebridge-co
but, other plugins and main program use ipv6 well.
tcp6       0      0 :::51826                :::*                    LISTEN      22203/homebridge
tcp6       0      0 :::39475                :::*                    LISTEN      22203/homebridge
Early that works fine. Please fix.

Hi @Alex7802,
Thanks for raising this issue, it has been fixed in 4.0.3.


beta generation failing because of delta function

beta weekly generation is currently failing because a delta function on directory objects was added which conflicts with the derived types delta functions.
I believe we should introduce an xsl fix that removes the functions on the derived types, only for beta, only for kiota based SDK for the time being until the service fixes their definition to unblock our generation pipeline, but I'm open to feedback here first.
CC @andrueastman @peombwa @irvinesunday

+1 to adding an XSL transform to remove the functions on the derived types (I assume OpenAPI.NET.OData will still add the function to the derived types accordingly). This XSL transform should be applied to all metadata files used by OpenAPI tools (Kiota, DevX, etc.).

+1 to adding an XSL transform to remove the functions on the derived types (I assume OpenAPI.NET.OData will still add the function to the derived types accordingly). This XSL transform should be applied to all metadata files used by OpenAPI tools (Kiota, DevX, etc.).

I agree. Implement the transform on the metadata but still eventually make the conversion library resilient to this as this seems to be valid OData according to https://github.com/microsoft/OpenAPI.NET.OData/issues/343#issuecomment-1438940862

This is currently affecting beta, do we want to be proactive and cover v1 as well?

just beta for the time being since the change hasn't rolled out to v1 at the moment. I suspect it'll eventually come to v1, and we'll update/remove the condition when it does.

Looks like this one was recently merged(yesterday) so we will need it for v1 as well.
https://msazure.visualstudio.com/One/_git/AD-AggregatorService-Workloads/pullrequest/7644692

closing since the fix is implemented in the conversion lib


optimize logging for network issues.

reason: Some guys meet the network issue like "443 error, Connect error"
@geekan PTAL

@geekan
在切断魔法上网以后的自测效果如下：

LGTM

LGTM


Documents doubts and improvements requests

Hi,
First, thanks for the initiative, i also have used the old nestjs-zod and had no idea it were fully discontinued.
Does your generator uses the same structure than nest-zod-prisma ?
Would be nice to have it better described on how to use it

Hi, I am very sorry I didn't see your Issue
Yes,It uses the same generator but I have applied some improvements described in the docs such as nullable and nullish, and repeated Enum import in schemas and so on
I actually would love to write a good description but I really don't have a lot of time for now, So I would appreciate any PR
If you needed any more information about the package you can reach me in a discord call and I would love to explain what is foggy for you so you can PR here.
appreciate it!
@yangricardo
@timseriakov

Tho I think it is more clear with this changes I made to the README
Please check that so I can close this


GPUtil is optional but required by default

GPUtil is an optional dependency although when installing mteb only (pip install mteb) and importing it seems to be required (see screenshot below).

cc @isaac-chung @KennethEnevoldsen

Good catch!


Update obsoleted target annotation query from playground

API has changed and the target annotation query does not work.
target > tractability > id
is now
target > tractability > label

Correct API query
query targetAnnotation {
  target(ensemblId: "ENSG00000169083") {
    id
    approvedSymbol
    tractability {
      modality
      label
      value
    }
    safetyLiabilities {
      event
      eventId
      biosamples {
        cellFormat
        cellLabel
        tissueLabel
        tissueId
      }
      effects {
        dosing
        direction
      }
      studies {
        name
        type
        description
      }
      datasource
      literature
    }
  }
}

@chinmehta could you please replace the existing target annotation example query with the correct one above

I just found this, checked whether it was already being tracked here and found that it was… since yesterday :joy:

@opentargets/fe-team testing would really help with these kinds of things

I can confirm that it is merged on the latest main

Hi @fedde-s , just wanted to inform you that this has been resolved in the latest Platform 23.09 release. Hence closing the issue.

Sorry for my delayed reply—I can also confirm that it's fixed, even when running the code outside of EBI's infrastructure :smile:
Nice and tidy!


Usage with other bundlers

Hi, I am excited about having a new CSS in Js library with zero runtime cost.
Does this library can be used with other bundlers or is it only webpack specific?
I would like to be able to run it on a more minimal project with esbuild for example.
Not something that can hold me back to try it, I can still try it with webpack, but I am opening a low priority issue just to let you know
Thanks for your effort, appreciate it

Interested in this as well. I'd like to use vanilla-extract with SvelteKit which uses Vite. As Markcial mentioned above, I'll still try it out regardless but it'd be neat to be able to use this with other bundlers.

Interested in using this with rollup!

Nothing concrete at this point, but we're definitely interested in support for other bundlers.

Check this out — @mattcompiles managed to get vanilla-extract working with esbuild: https://twitter.com/mattcompiles/status/1376748835947511812

We have an open PR adding esbuild support, should hopefully land soon: https://github.com/seek-oss/vanilla-extract/pull/14

I'm making good progress on a Rollup integration too: https://twitter.com/markdalgleish/status/1378898886819913731

Just shipped the esbuild plugin: https://github.com/seek-oss/vanilla-extract#esbuild

Does someone has a successful config with vite + @vanilla-extract/esbuild-plugin?
I tried:
export default defineConfig({
  plugins: [preact(), vanillaExtractPlugin({ projectRoot: path.resolve(__dirname) })],
});

Without success:

Error: New styles cannot be registered dynamically after initial boot. This is to ensure that styles are statically extractible.

@zoontek Will be looking into vite at some point soon hopefully. However, isn't rollup the primary bundler for vite? I thought esbuild was only used as a babel replacement?

Ah, maybe! I just tried it without knowing much about it.

I can confirm that the esbuild plugin works perfectly, just tested it right now. Congratulations 👏

Also interested in using this with rollup/vite - might use it in @wilsonjs.

Hopefully have something to show with vite very soon.

Just an update on the Rollup integration work—since it doesn’t have first class CSS bundling support, we're thinking it’s probably not a good target for static extraction.


Cannot Get it Running

I tried using Ubuntu 16.04 and 14.04, it failed to run. When I run the command it will just stop and do nothing, empty line. I open the browser it displayed: 404 page not found.
Then I went on to try docker, which also out of luck.

I do not think I have done something wrong unless there are dependencies/other stuff that I have missed. Thanks for the help.

Update: I just found out I can use -d to show log
After running the command, this is what it shows:
[Init] Starting Pixiecore goroutines

That's all it's supposed to do. Once the goroutines are started, that means it's listening for DHCP traffic from machines that are trying to boot. Machines should netboot from that point on. If they don't, continue running pixiecore with -d, and it should print messages if it's receiving DHCP requests but ignoring them for some reason.
If you want the browser UI that's on the homepage, you need to also pass --status-port 80, the human UI is disabled by default.
If machines still fail to netboot, and pixiecore with -d is not displaying any messages, that means the DHCP traffic is not reaching Pixiecore for some reason. Check that your firewall accepts UDP traffic coming to ports 67 (dhcp), 69 (tftp) and 80 (http). If you're in an enterprise-like network, it's possible the switches are also doing some DHCP filtering and enforcement to prevent rogue DHCP servers. If you think that might be happening, you should talk to your network admins.

Thank you. I see. I am not really familiar with pxe, what url should I use to boot?
http://ip/xxx?

It depends a lot on the machine and its firmware, but usually, if you go into the BIOS settings, one of the boot options will be something like "Network", or the name of your network card. Tell the machine to boot with that, and the rest should be completely automatic, no need to enter URLs or anything.

Have you use vultr before? I am trying pxe with vultr as it support ipxe and it is cheap enough.

Pixiecore is not really designed for your use case. Specifically, pixiecore assumes that it controls the entire bootup lifecycle of the machine. On the other hand, Vultr assumes that it controls the machine boot, and all you get to do is give it an iPXE URL. So unfortunately, I don't think Pixiecore is going to work for you :(.
As an alternative, I can recommend https://netboot.xyz/ . You can tell Vultr to boot from https://boot.netboot.xyz , and you will get a menu where you can select the OS you want to boot.

My goal was not use on vultr, I want to use it on packet.net, although I don't know if they are the same.

Thank you for bring up netboot.xyz. It works really good with packet and vultr as they are official supported by netboot.xyz.


Call to undefined method Google\Cloud\Storage\Bucket::generateSignedPostPolicyV4()

Environment details

OS: MacOS 10.15.3
PHP version: 7.4.1
Package name and version: google/cloud-storage: 1.20.1

Steps to reproduce

Call to bucket->generateSignedPostPolicyV4()

Code example
$client = new StorageClient(['keyFile' => get_option("creds")]);  // <- Working
$bucket = $client->bucket('#####');  // <- Working, removed bucket name for example
$object_name = "cat.jpg";
$policy = $bucket->generateSignedPostPolicyV4($object_name, new \DateTime('tomorrow'));

At this point, an exception is thrown "Call to undefined method Google\Cloud\Storage\Bucket::generateSignedPostPolicyV4()"
$bucket->exists() returns true in the above code example.
Is this an error on my end?

@jdpedrie

Hi @samsycamore,
That's quite odd! Your code is correct, and when I run your snippet it works fine. Are you certain that the version of google/cloud-storage you have is what you expect?

Hey John,
Yep, you are absolutely right. Stepping into ->exists() shows that I have a plugin installed that with an older version of google/cloud-storage.
My mistake, sorry!

Great! I’m glad you’ve got it figured out. 😃


adding appinfo hint to help ide figure out that the client-region ele…

…ment produces beans of type Region, without which intellij tells me it can't parse this 'custom spring bean'
hello,
when i use gemfire and setup a client region using the spring gemfire namespace, intellij idea tells me that it cannot parse this custom spring bean.  as far as i can tell i have this problem only with the gfe:client-region element.
i had a look at the xsd and noticed that the element definition does not sport the appinfo hint that tells applications that it exports a bean of type Region.
this pull request fixes this issue and makes my ide happy.
this blog does a good job of explaining the issue:
http://blog.trifork.com/2011/07/07/enhancing-ide-support-for-custom-spring-namespace-elements/

Thanks for this PR!

my pleasure.


Component.InvokeAsync add  tag

Hello,
I am using Bootstrap for my web application. All was working until I added ViewComponent.
When I use it like that :
@await Component.InvokeAsync(nameof(Plan), new { tenantId = Model.Id })
It adds a lots of <b> tag everywhere in my DOM...
For example, before my viewcomponents, I have my

Could you share your application or a minimal repro with us?

This looks like a view that your view component is running is pulling in your layout.

@toben please share a repro app on GitHub that demonstrates this and we will investigate.

Closing because there is not enough information to reproduce this problem.


💭 What is the equivalence of V2's preset="photo" in V3?

Question
I am currently upgrading the library version from "^2.15.4" to "^3.9.1", and previously I have the prop preset="photo" in my Camera component, but I see that the preset prop is no longer available in V3. I have spent a lot of time on trying out different camera formats in V3 with the goal of reproducing the image quality (e.g. exposure, image sharpness, image noise level, etc.) of setting preset="photo" in V2, but with no luck. Does anyone by chance know what is the equivalent configuration/setting/camera format in V3 that maps to preset="photo" in V2? Thanks a lot in advance!
For reference, my code in V2 looks like the following:
const devices = useCameraDevices();
const { back } = devices;
<Camera
  style={styles.camera}
  device={back}
  isActive={true}
  photo={true}
  ref={cameraRef}
  preset="photo"
  enableZoomGesture={true}
  zoom={back.neutralZoom}
/>

What I tried
I have a React Native CLI project and I am testing my app on iPhone 11, and I have tried various different camera formats in V3, such as the one in the code below: the video I see in the "preview" before taking the picture and also the taken picture itself have noticeably more noise, and higher exposure then using preset="photo" in V2, the color also appears less saturated than what I had with preset="photo" in V2. My goal is to reproduce the same image quality (both in "preview" and in the image taken) as the one from using preset="photo" in V2. Any help would be greatly apprciated!
My V3 Code:
const backDevice = useCameraDevice('back', {
  physicalDevices: [
    'ultra-wide-angle-camera',
    'wide-angle-camera'
  ]
});

const backDeviceFormat = useCameraFormat(backDevice, [
  { photoResolution: 'max' },
  { videoResolution: 'max' },
]);

<Camera
  style={styles.camera}
  device={backDevice}
  isActive={true}
  photo={true}
  ref={cameraRef}
  enableZoomGesture={true}
  zoom={backDevice.neutralZoom}
  format={backDeviceFormat}
/>

My V2 Code:
const devices = useCameraDevices();
const { back } = devices;
<Camera
  style={styles.camera}
  device={back}
  isActive={true}
  photo={true}
  ref={cameraRef}
  preset="photo"
  enableZoomGesture={true}
  zoom={back.neutralZoom}
/>

VisionCamera Version
3.9.1
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey @jackylu0124, maybe you could see what kind of device and format you get on V2 and compare that to the ones you get on V3 (just by logging them). The filter you use on V3 only maximises the resolution of the photo and video (preview). That is not the best format necessarily, it depends on your use case.
Futhermore, I think enabling HDR and setting qualityPrioritization for taking photos to quality could also help boost the results you see.

Hi @jackylu0124, good point, it's hard to log that way. It seems that preset only does something on iOS and is determined by Apple, so it's a bit hard to see what it actually does. What you could try is to alter the source code to log the format that is being used.
After this line, you could add something like this:
guard let f = device.activeFormat else { return }
let formatDict = f.toDictionary()

do {
  let jsonData = try JSONSerialization.data(withJSONObject: formatDict, options: .prettyPrinted)
  let jsonText = String(data: jsonData, encoding: .ascii)
  ReactLogger.log(level: .info, message: "Format: \(jsonText)")
} catch {
  ReactLogger.log(level: .error, message: "Error occured while serializing format to JSON")
}

I didn't test this code so there could be error in it, but I think it points you to the right direction. You could just add something like this in your node_modules/react-native-vision-camera/ios/CameraView+AVCaptureSession.swift

Hey - you could try to use useCameraFormat(device, Templates.Photo) for example. But by default, photo is already high quality.


Fix typo.

Dear Airflow Maintainers,
Please accept this PR that fixes a typo.
Let me know if I need to create an JIRA issue for that. I could not find "typo" as Types of Contribution in the guidelines for contributing.

Codecov Report

Merging #2059 into master will not change coverage.

@@          Coverage Diff           @@
##           master   #2059   +/-   ##
======================================
  Coverage    67.6%   67.6%
======================================
  Files         139     139
  Lines       10578   10578
======================================
  Hits         7151    7151
  Misses       3427    3427

Impacted Files
Coverage Δ

airflow/models.py
86.16% <ø> (ø)
:white_check_mark:

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 61fb6a5...3a7c695. Read the comment docs.

Thx for the contribution.. I'm sure you may find other such documentation fixes for your first commit. Please get familiar with our Contributor guidelines (e.g. open a jira, preface commit title with jira issue id) and add a few more doc updates (typo fixes) here. For example, I recall seeing quite a few typos and grammatical issues in UPDATING.md. You may want to fix those if they persist.
https://cwiki.apache.org/confluence/display/AIRFLOW/Contributors'+Guide

Hi,
you can close this PR. I will not open a jira issue for this nor search for other typos. Too much overhead for everbody.

@rolfschr only you can close your own PR.


Validation flow on custom fill

The extension works great overall after the last update! Great work!
I came acros this: when checking the checkbox for "manual mode" the validations kicks in imediatly and the fields are marked red with "This field is required". I am not sure this is an issue or intentional. But it might be more clean/clear to delay the validation after the customer submits the form?

This is a know issue with the Hyva Checkout. But it's their main focus point for the upcoming releases. Once they release a fix for this, we will update the module to better handle this.


Build warnings when building CocoaLumberjackSwift with Carthage

Hi,
I've been having build warnings each time I build CocoaLumberjackSwift with Carthage.  It's usually a long list of warnings.  Since CocoaLumberjack is built with multiple frameworks and it's already including the CocoaLumberjack.framework, should these warnings just be ignored?  Though, I would prefer not having any build warnings.
Here are the build warnings referring to a missing umbrella header:
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'CocoaLumberjack.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAbstractDatabaseLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogCapture.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDASLLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDAssertMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDContextFilterLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDDispatchQueueLogFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDFileLogger.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog+LOGV.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLog.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDLogMacros.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDMultiFormatter.h'
<module-includes>:1:1: warning: umbrella header for module 'CocoaLumberjackSwift' does not include header 'DDTTYLogger.h'

Thanks @rivera-ernesto
What I've found interesting is that the warnings only show up when I compile with Carthage.  I compiled CocoaLumberjackSwift with xctool and no warnings there, just like building it with Xcode...

Good to know. Closing this for now.


Python: trying to create Image from unsupported array data-type format gives cryptic error

My student was (for some reason) using float16 numpy arrays for a calculation and then trying to create/save an image from SimpleITK, it gives this cryptic error:
Traceback (most recent call last):
  File "./potential_maps3.10.py", line 421, in <module>
    awolmrf.get_potential_maps()
  File "./potential_maps3.10.py", line 249, in get_potential_maps
    singleton_image = sitk.GetImageFromArray(singleton_map)
  File "/project/m/mchakrav/quarantine/SimpleITK/1.0/build/lib/python2.7/site-packages/SimpleITK/SimpleITK.py", line 3432, in GetImageFromArray
    img = Image( z.shape[::-1], id )
  File "/project/m/mchakrav/quarantine/SimpleITK/1.0/build/lib/python2.7/site-packages/SimpleITK/SimpleITK.py", line 3683, in __init__
    this = _SimpleITK.new_Image(*args)
NotImplementedError: Wrong number or type of arguments for overloaded function 'new_Image'.
  Possible C/C++ prototypes are:
    itk::simple::Image::Image()
    itk::simple::Image::Image(itk::simple::Image const &)
    itk::simple::Image::Image(unsigned int,unsigned int,itk::simple::PixelIDValueEnum)
    itk::simple::Image::Image(unsigned int,unsigned int,unsigned int,itk::simple::PixelIDValueEnum)
    itk::simple::Image::Image(std::vector< unsigned int,std::allocator< unsigned int > > const &,itk::simple::PixelIDValueEnum,unsigned int)

Would've been helpful to complain about the datatype being passed.

Thank you for reporting this issue. Can you please provide a small snippet of code to reproduce the error message?

import SimpleITK as sitk
import numpy as np

numpy_array = np.zeros((3,3,3), np.float16)
simpleitk_image = sitk.GetImageFromArray(numpy_array)

Traceback (most recent call last):
  File "float16_error.py", line 5, in <module>
    simpleitk_image = sitk.GetImageFromArray(numpy_array)
  File "/opt/quarantine/anaconda/4.3.0-python2.7/build/lib/python2.7/site-packages/SimpleITK/SimpleITK.py", line 351, in GetImageFromArray
    img = Image( z.shape[::-1], id )
  File "/opt/quarantine/anaconda/4.3.0-python2.7/build/lib/python2.7/site-packages/SimpleITK/SimpleITK.py", line 3741, in __init__
    this = _SimpleITK.new_Image(*args)
NotImplementedError: Wrong number or type of arguments for overloaded function 'new_Image'.
  Possible C/C++ prototypes are:
    itk::simple::Image::Image()
    itk::simple::Image::Image(itk::simple::Image const &)
    itk::simple::Image::Image(unsigned int,unsigned int,itk::simple::PixelIDValueEnum)
    itk::simple::Image::Image(unsigned int,unsigned int,unsigned int,itk::simple::PixelIDValueEnum)
    itk::simple::Image::Image(std::vector< unsigned int,std::allocator< unsigned int > > const &,itk::simple::PixelIDValueEnum,unsigned int)

Thank you fro including the test case.


docs: update overview images

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 81.36%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
3003

Relevant Lines:
3691

💛  - Coveralls


Difficulty in understanding chrome android physical web scanning behavior?

Given: Physical web flag is enabled on chrome i.e., chrome on android is ready to scan for physical web
Do we have any certain rules or on the discoverability behavior of physical web on chrome?
For example, chrome on android discovers physical web from an eddystone beacon named as beacon1 . Now say a user has swapped off the physical web notification.
Q1| Will the user discover physical web from the same beacon1 again?
Q2| If yes, are there any conditions, i.e.,
» if he is in the range of beacon1 more atleast for a specific amount of time?
» or any time duration in which URL from same beacon will not appear?

I have faced this issue, so say I have discovered physical web and I have then swapped it off? I have no idea when will I get the URL back again? I keep on opening my chrome, closing it, check for location, turn on/off my bluetooth, switch my screen on/off, and then after all this, somehow magically I discover physical web again.
Hence, these things are important to know, that is the logics behind it's descoverability.

This is moving target and the rules will change and evolve as we learn more. Presently, we respect if the user swipes away the notification and will not bring it back. If the user leaves that area (all beacons are 'lost') and they return, the notification will return. If however, you have just one beacon near you and you swipe it away and just stay there, it will never come back.

Ah! That clears a lot of doubts. Thanks Scott!


Add method for calculating log_prob and its gradients

Submisison Checklist

[x] Run tests: ./runCmdStanTests.py src/test
[x] Declare copyright holder and open-source license: see below

Summary:
A common request is to add functionality comparable to rstan's log_prob and grad_log_prob functions.
This PR adds an additional method to the command-line: log_prob, which takes an input file of (unconstrained) parameter values (json or csv) with variable(s) params_r and optionally params_i (as defined by the model's log_prob function), and returns a .csv file with the log-probability and gradients with respect to each parameter.
As an example, consider the bernoulli example with two parameters:
data {
  int<lower=0> N;
  array[N] int<lower=0,upper=1> y; // or int<lower=0,upper=1> y[N];
}
parameters {
  real<lower=0,upper=1> theta;
  real<lower=0,upper=1> theta2;
}
model {
  theta ~ beta(1,1);  // uniform prior on interval 0,1
  theta2 ~ beta(1,1);  // uniform prior on interval 0,1
  y ~ bernoulli(theta);
}

To use the log_prob method a file with parameter values is created (called params.json hereafter), with contents:
{"params_r":[1,0.5]}

After the model has been compiled, the log_prob method is called as:
./bernoulli method=log_prob unconstrained_params=params.json data file=bernoulli.data.json output grad_output_file=grad.csv

The grad.csv file then contains:
# log_prob
-14.2073
# log_prob_grad
-5.7727,-0.244919

Note that this is my first foray into the IO side of things, so make sure to let me know if there's a more efficient way of handling the reading/writing here!
Intended Effect:
Simple access to the model's log-probability and its gradients for end users
How to Verify:
Side Effects:
N/A
Documentation:
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): Andrew Johnson
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Love it! Works great!
It would be great if we were able to evaluate a bunch of log_probs with a single model instantiation. Not necessarily required to do here, but we should set up the API so that it allows us to expand to that in the future.
I think a better name for grad_output_file would be log_prob_output_file? Though I think we should separate the output into two files - splitting CSV files based on comments is a tedious job. Especially if we are able to have more than 1 row if we expand to multiple evals at some point.

Is that grad.csv a well-formed CSV file? I'd rather have something like
lp__, g_theta, g_theta2
-14.2073, -5.7727, -0.244919

(g_* is how the gradients are named in diagnostic_file.)
The input being unconstrained parameters is a bit problematic when the constraining/unconstraining transform is not exposed AFAIK. Could the API looked like generate_quantities, i.e. takes in a CSV of constrained parameters?

I was about to make @nhuure's proposal, then I scrolled down.  That will be much easier to ingest into a data analysis package as it's just a CSV file with a meaningful header.
Another request would be to do this for more than one input.  That is, take something that looks like a CSV file of draws and use that.  e reason I ask this is that it will be very slow to run this one gradient at a time because of the need to reload data and recompute transformed data.  This would wind up looking a lot like standalone generated quantities.  In fact, you could even add this to the standalone generated quantities functionality as additional columns of output.
the output and run it to calculate gradients.

Yes, a server could be added to CmdStan.  I just didn't want to get involved with Stan governance in writing my own server because I've been overruled on all the other interface design decisions and want to maintain control of this one.

I think that makes sense, since they would necessarily have different goals. I think anything incorporated into cmdstan would want to stay away from the binary IO which stan-model-server will eventually need for efficiency, for instance.

As some final changes I've added some code comments, as well as an additional argument for whether or not to apply jacobian-adjustments when calculating log_prob (defaulting to TRUE).
That's the last of the changes that I can think of, so this is now ready for review

Thanks @bob-carpenter! I've updated the doc and comments, and added tests. Let me know if there are any aspects/functionalities that I've forgotten to test as well, thanks!

After updating my local checkout I've been trying to use this but most things I've tried so far have segfaulted. I'm not sure if I'm doing something wrong, the arguments need more validation checks, or something else.
Using the standard bernoulli example, I've tried
./bernoulli log_prob constrained_params=sample.csv data file=bernoulli.data.json

where sample.csv was produced by sampling; segfault. I also tried this with the same CSV but removing all the columns except for theta and all the comment rows; still segfaults.
./bernoulli log_prob constrained_params=test.json data file=bernoulli.data.json

Where test.json was {"theta": 0.2}; segfault
Where test.json was {"theta": [0.4,0.5,0.2]}; segfault.
I'd like to know 1) what I'm doing wrong, and 2) can we try to catch whatever that is earlier

Ah that's because the constrained_params needs to have a single variable params_r, which is what the model's log_prob function takes

There's an example file in the tests: https://github.com/stan-dev/cmdstan/blob/develop/src/test/test-models/bern_constrained_params.R

Why wouldn't constrained_params accept something in the same format as the inits argument for sampling? E.g. using the actual parameter names and shapes?
Either way, this shouldn't segfault since I expect it will be a common thing people will try to do

That's fair enough. I was matching the rstan implementation, since I was aiming to add similar functionality for cmdstanr, but I can change it to take inputs matching the sample output, I'll do another PR

I'm thinking from the standpoint of CmdStanPy etc, we will probably want to accept the constrained parameters as a dictionary.
Instead taking in a params_r vector would be a lot of work for users and probably a source of subtle bugs - e.g. re-ordering declarations in the parameters block would make old inputs now return different outputs, which isn't the case if we do it all with the real names

Looking at the rstan documentation, I believe they handle constrained parameters as a named list and unconstrained as a vector, rather than both as a vector.

updated PR description - input files are json or rdump, not CSV.


Fix typo

python -> Python

Learn Build status updates of commit 6558818:
:bulb: Validation status: suggestions

File
Status
Preview URL
Details

articles/energy-data-services/tutorial-seismic-ddms-sdutil.md
:bulb:Suggestion

Details

articles/energy-data-services/tutorial-seismic-ddms-sdutil.md

Line 30, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/windows/wsl/install' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@changeworld - thank you!


feat(API): JIRA-5751 Add API provider

This is related to an internal task I've bee working on. Part of the logic, is being moved to the package instead.

Fake provider and test are WIP. Coming shortly.

We can ignore the Windows test failure, it's an issue with Windows only, and doesn't reflect actual conditions. 😬


Question: Where are the address of the deployed contracts?

Where are the address of the deployed contracts?

You can find it here https://github.com/dydxprotocol/protocol_v1/blob/master/migrations/deployed_addresses.md


Android build fails

e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (23, 95): No value passed for parameter 'p1'
e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (33, 124): Type mismatch: inferred type is KeyEventChannel but View was expected
e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (33, 141): Type mismatch: inferred type is TextInputPlugin but KeyEventChannel was expected
e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (33, 156): No value passed for parameter 'p2'
e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (34, 18): Return type of 'onKeyDown' is not a subtype of the return type of the overridden member 'public open fun onKeyDown(@NonNull p0: KeyEvent): Boolean defined in io.flutter.embedding.android.AndroidKeyProcessor'
e: /Users/jstillwell/Code/flutter/.pub-cache/hosted/pub.dartlang.org/flutter_gamepad-0.3.2/android/src/main/kotlin/com/example/flutter_gamepad/FlutterGamepadPlugin.kt: (41, 18): Return type of 'onKeyUp' is not a subtype of the return type of the overridden member 'public open fun onKeyUp(@NonNull p0: KeyEvent): Boolean defined in io.flutter.embedding.android.AndroidKeyProcessor'

FAILURE: Build failed with an exception.

Latest Android Studio.
Very simple project that just uses your example code.
MacOS

@dragonfax
Here's what you can do as a temporary measure:

Fork the flutter_gamepad package.
From the Android part of the package remove all code that causes problems and leave just barebones skeleton of the plugin (or "do nothing plugin") so that it registers instead of throwing an exception (which is what happens if you remove everything) when your app loads.
Use the functionality provided by the package for iOS only
Use RawKeyboardListener on Android as it can handle all the keys from gamepad controllers (RawKeyboardListener functionality is not implemented on iOS).

I'm using this on Android.

Go for RawKeyboardListener then! It has it all.

Does the example app build for you?

Oh I think perhaps we just haven't updated pub.dev in a while. The latest code in the master branch of our repo will build though.

The example in the master branch doesn't compile either.
I get the same error messages as dragonfax.

https://github.com/flutter/flutter/issues/50789#issuecomment-870514415


MiddlewareRegexPipe class.

What about regex support ? It can be more functional optionally if its support regex.
$app = MiddlewarePipe('/api', $callable);

or i can use MiddlewareRegexPipe class.

$app = new MiddlewareRegexPipe('/admin/.*,  $callable)

We have no plans to add dynamic riding to Stratigility; this is a
middleware foundation only. Instead, we delegate that to applications or
third party projects; one such is zend-expressive.
On Oct 20, 2015 8:31 AM, "Ersin Guvenc"<EMAIL_ADDRESS>wrote:

What about regex support ? It can be more functional optionally if its
support regex.
$app = MiddlewarePipe('/api', $callable);or i can use MiddlewareRegexPipe class.$app = new MiddlewareRegexPipe('/admin/.*,  $callable)
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-stratigility/issues/33.


added name

Related issue

What changes does this PR do?
Screenshots (If any)
Questions

moved it up


TabsNext - overflow menu items name issue

Latest version

[X] I have tested the latest version

Description
When Tabs overflow the menu does not show appropriate tab names. This is also happening in official Salt DS website.
Steps to reproduce

make screen smaller so that Tabs overflow into an overflow menu.
open menu.
Check out names of the menu items

Expected behavior
No response
Package name(s)
Lab (@salt-ds/lab)
Package version(s)
latest
Browser

[X] Chrome
[ ] Safari
[ ] Firefox
[ ] Microsoft Edge

Operating system

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS
[ ] Android

Are you a JPMorgan Chase & Co. employee?

[X] I am an employee of JPMorgan Chase & Co.

Duplicate of #4207. Should be fixed in https://github.com/jpmorganchase/salt-ds/releases/tag/<EMAIL_ADDRESS>


Replace plus from version number?

I'm using setuptools_scm to upload non-release master builds to Test PyPI.
However, the local version part of the default version number (the +xyz bit of 0.6.1.dev4+gdf99fe2) isn't compatible with PyPI, and gives an error:
HTTPError: 400 Client Error: '0.6.1.dev4+gdf99fe2' is an invalid value for Version. Error: Can't use PEP 440 local versions. See https://packaging.python.org/specifications/core-metadata for url: https://test.pypi.org/legacy/

https://travis-ci.org/hugovk/pypistats/builds/543062857
Is it possible to configure setuptools_scm so local versions are not used to allow upload to Test PyPI?
For example, maybe do something like 0.6.1.dev4.gdf99fe2 instead of 0.6.1.dev4+gdf99fe2?

I tried this:
+def version_scheme(version):
+    from setuptools_scm.version import guess_next_dev_version
+
+    version = guess_next_dev_version(version)
+    return version.replace("+", ".")
+
+
 setup(
-    use_scm_version=True,
+    use_scm_version={"version_scheme": version_scheme},

But it made no difference; I see the local version is already stripped from this, and then later added elsewhere:
https://github.com/pypa/setuptools_scm/blob/b5f79dc9af96892d48243c45a3583c0b2ea4f480/src/setuptools_scm/version.py#L208-L215

you can simply use a different local version scheme to turn it off, its however not the suggested path

Thanks, this gives a version like 0.6.1.dev8, which allows uploading to Test PyPI:
+def local_scheme(version):
+    return ""

 setup(
-    use_scm_version=True,
+    use_scm_version={"local_scheme": local_scheme},

Is there a better suggested path? Thanks!

Currently not, the usage of local versions is intended to prevent accident release uploads

Okay, thanks for the help!
This is just fine for me, the huge benefit is not having to edit and commit the version number at all in code, and it's also good there's a different version for Test PyPI.
Thank you for the library!

Thanks! This helped.

I don't have an opinion on the proper solution to this problem, but I think it would great for the maintainers to recommend an approach for users. The pypi-publish GitHub Action is right now recommending the use of setuptools_scm for running test releases. That sounds like a great idea and it's something I'd like to implement. But, with the bug documented here, I'm unsure of how to do it in accordance with best practices.

a feature for intentional overrides is planned for a feature release within the next 4-6 weeks

That's great. So glad to hear it, @RonnyPfannschmidt!

Did this get solved?

For me, yes, by using https://github.com/pypa/setuptools_scm/issues/342#issuecomment-502668474

@palewire I missed https://github.com/pypa/setuptools_scm/pull/405 which added no-local-version. So you can do:
# setup.py
from setuptools import setup

setup(
    use_scm_version={"local_scheme": "no-local-version"},
)

Or:
# pyproject.toml
[tool.setuptools_scm]
local_scheme = "no-local-version"

@connortann So what is the current recommended way to do this to facilitate using testpypi releases?
Is it
setup(
    use_scm_version={"local_scheme": "no-local-version"},
)

Or something else?

I can't speak to what is recommended by the maintainers of setuptools-scm, but for me the pattern suggested in https://github.com/pypa/setuptools-scm/issues/342#issuecomment-1233118020 worked fine.


add xml support as xq (from python yq)

The idea it to add xml support the same as xq (installed with python yq).
It supports multiple xml inputs, that xq does not allow.
On read, much faster than original xq.
On write, many times faster than json2xml.
I'm opened to ideas.

hello, I'm still doing havy tests on our servers, I let you know when it is ready for publishing

If anyone is interested, a binary built called "xjq" is available here; https://github.com/momiji/xjq.
It is build using the updated forked gojq code, which is near up-to-date: https://github.com/momiji/gojq/compare/main...itchyny:gojq:main


Phoenix 1.3 compatibility

There's one test that fails: test/mix/tasks/phoenix.gen.html.slime_test.exs:18
The test is expecting the generated slime file to use the date_select helper for the born_at field, instead the text_input form helper is used.
This is strange because the first_login field uses the date_select helper. I'm a little too new to Elixir/Phoenix to promise I can fix it, but I did manage to fix 3/4 failures from the upgrade. 😅

Closed in favour of #37.


Fix v1.6 issues for AC object model

Description

Card.Metadata definition is missing - Added AdaptiveMetadata class
ChoiceSet missing DataQuery property - Added AdaptiveDataQuery class and modified ChoiceSet to serialize it.
Implied types for TableRow/Cell broken - added attribute
Visitor class doesn't support all element types - Fixed visitor class to visit new schema types
WPF renderer has bogus methods added which break the WPF visualizer - removed those methods, they never should have been added.
Bumped Supported card version to 1.6
Implement AdaptiveWidth and AdaptiveWidthConverter for parity with AdaptiveHeight
add missing horizontal aligment for collections
Property name VerticalAndHorizontal cell content alignment to align with docs
Add missing XmlElement to Background image.
Fix Refresh, it can be ActionExecute OR Submit. (Teams will barf on preview if you actionexecute)
add Rtl that was missing on Table
Fix Table Column Width that should allow double values, not integers for parity with javascript designer.
removed duplicate Style property from TableRow
Added missing XmlElement(AdaptiveExecuteAction)  to inline actions
Removed duplicate ientries in typed element types
Added TableColumnWidth with converter
added unit tests
Disabled XmlSerializationTests so it is clear that they are not running, they have been broken for years and silently "succeeding'.  XmlSerialization is very broken, but it's not me.

How Verified
Unit Tests disabled for 1.4, 1.5, .16 -- enabled and fixed all issues

@microsoft-github-policy-service agree

/azp run uwp-ci.yml

/azp run

[like]  Joseph Woo reacted to your message:

From: Paul Campbell @.>
Sent: Tuesday, April 30, 2024 8:27:46 PM
To: microsoft/AdaptiveCards @.>
Cc: Joseph Woo @.>; Review requested @.>
Subject: Re: [microsoft/AdaptiveCards] Fix v1.6 issues for AC object model (PR #8878)
Merged #8878https://github.com/microsoft/AdaptiveCards/pull/8878 into main.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AdaptiveCards/pull/8878#event-12663591042, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA7MCOHQ3FJTOSANTEQEBLLY775EFAVCNFSM6AAAAABGN2ZFDOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSGY3DGNJZGEYDIMQ.
You are receiving this because your review was requested.Message ID: @.***>


Whitelist as last rule

Hi,
Currently the whitelist is the first rule checked, but in some cases, the whitelist can be dynamic and requires a lookup.  In fact, I'm storing whitelisted ip/users in memcached since it can't be predetermined in advance.
I would like to check if the user is whitelisted only if the request going to be rejected (throttle), so in normal situations it won't hit the cache at all.

Hmm, the check order is a pretty core part of the library right now and switching it around would probably create a lot of issues.
For your use case, I'd recommend a workaround of monkey-patching Rack::Attack#call: https://github.com/kickstarter/rack-attack/blob/master/lib/rack/attack.rb#L93
class Rack::Attack
  # Monkey-patch to only check whitelist if a request is throttled
  def call(env)
    req = Rack::Attack::Request.new(env)

    if blacklisted?(req)
      self.class.blacklisted_response.call(env)
    elsif throttled?(req) && !whitelisted?(req)
      self.class.throttled_response.call(env)
    else
      tracked?(req)
      @app.call(env)
    end
  end
end

the check order is a pretty core part of the library right now and switching it around would probably create a lot of issues. Most importantly, users expect whitelists to supersede blacklists.

Yup.
@antlegrand Maybe add a check for your whitelist to each of your throttles? E.g.:
throttle('ip', limit: 10, period: 10) {
  req.ip unless Rails.cache.get('whitelisted_ips').include?(req.ip)
}


Update the default head elements

They feel very "2015". Update them to reflect current best-practices, perhaps a manifest (if well-supported), and, perhaps, look at https://realfavicongenerator.net/, as they seem to get a lot correct.

Done in ed8aa33101bda91cea14831c21ee849c2428c7e7.


Update readme, prep for cutting a<EMAIL_ADDRESS>

I think everything is compatible, so we only need a patch release 0.23.1, and only for the -sys. This just fixes the bundled-sqlcipher and -vendored-openssl logic so that it
Thanks to @douloiha for (even unintentionally) reminding me about the fact I this should get into a followup https://github.com/rusqlite/rusqlite/pull/860#issuecomment-853304210, and to @BlackHoleFox for actually doing the work after I whined about nonesense elsewhere online.
(Also thanks to @dubiousjim for doing the initial version of the feature, and sorry its so long before it became usable)

Published libsqlite3-sys version v0.23.1 https://crates.io/crates/libsqlite3-sys/0.23.1


ENH Rendering scalars in ArrayList in templates

Issue https://github.com/silverstripe/silverstripe-framework/issues/11196

Have created changlog entry

if (is_scalar($on) || is_null($on)) {
            $on = $this->convertPrimitiveToDBField($on);
        }

Still not done?

It was updated