Arrow type in a method's type argument constraint causes a failed assertion

class Foo
  fun foo[X: box->Y, Y](x: X) => None

Building builtin -> /Users/paul/Projects/ponyc/packages/builtin
Building . -> /private/tmp/a
src/libponyc/type/typeparam.c:336: cap_from_constraint: Assertion `0` failed.

Backtrace:
  0   ponyc                               0x00000001048b25e1 ponyint_assert_fail + 161
  1   ponyc                               0x00000001048a87ce cap_from_constraint + 430
  2   ponyc                               0x00000001048a85ee typeparam_set_cap + 158
  3   ponyc                               0x000000010486f486 flatten_typeparamref + 150
  4   ponyc                               0x000000010486f68e pass_flatten + 462
  5   ponyc                               0x000000010487238d ast_visit + 685
  6   ponyc                               0x00000001048722c4 ast_visit + 484
  7   ponyc                               0x00000001048722c4 ast_visit + 484
  8   ponyc                               0x00000001048722c4 ast_visit + 484
  9   ponyc                               0x00000001048722c4 ast_visit + 484
  10  ponyc                               0x00000001048722c4 ast_visit + 484
  11  ponyc                               0x00000001048722c4 ast_visit + 484
  12  ponyc                               0x00000001048722c4 ast_visit + 484
  13  ponyc                               0x00000001048722c4 ast_visit + 484
  14  ponyc                               0x00000001048722c4 ast_visit + 484
  15  ponyc                               0x0000000104872c4c visit_pass + 156
  16  ponyc                               0x000000010487265b ast_passes + 443
  17  ponyc                               0x0000000104872495 ast_passes_program + 37
  18  ponyc                               0x000000010488e23e program_load + 190
  19  ponyc                               0x00000001047d8faf compile_package + 47
  20  ponyc                               0x00000001047d8ddf main + 1103
  21  libdyld.dylib                       0x00007fff98fe2255 start + 1
  22  ???                                 0x0000000000000001 0x0 + 1
fish: '~/Projects/ponyc/build/debug/po…' terminated by signal SIGABRT (Abort)

This is the same as https://github.com/ponylang/ponyc/issues/1694, but in a method's type parameters rather than a class. My guess is because of the (opt->check.frame->method == NULL) check in libponyc/pass/syntax.c#L451
Removing the check makes the snippet above cause the expected error. However it breaks collections/map.pony#L241, which uses H2: HashFunction[this->K!] val.
This kind of constraint is currently disallowed on type level generics due to the check in syntax.c. For example :
trait Bar[X]
class Foo[X: Bar[box->Y], Y]
  fun foo() => None

Error:
main.pony:3:21: arrow types can't be used as type constraints
class Foo[X: Bar[box->Y], Y]

My guess is that arrow types should be allowed in constraints, but only as a type argument, not at the top level. I don't see a reason for there to be a difference between methods and class arguments.

We talked during the sync about lifting the "no arrow" restriction all together.
There's one concern I see, which is it can lead to constraints with no "reduced form".
For example :
class Foo[X: box->Any #any]

The constraint box->Any #any allows Any val, Any box and Any tag. There's no capability constraint which includes all three caps. We could add more constraints to make them closed under viewpoint adaptation. I'm not sure how many are needed.
I think this is similar to #alias. The documentation mentions that #alias is only used by the compiler. My understanding is it was added to allow #any! to have a reduced form.

Fixed by #1870.
Thanks, @plietar!


RuntimeError: CUDA error: invalid device ordinal

When I load model I have this error.
Traceback (most recent call last):
File "", line 1, in
File "test/env/lib/python3.9/site-packages/galai/init.py", line 39, in load_model
model._load_checkpoint(checkpoint_path=get_checkpoint_path(name))
File "test/env/lib/python3.9/site-packages/galai/model.py", line 63, in _load_checkpoint
load_checkpoint_and_dispatch(
File "test/env/lib/python3.9/site-packages/accelerate/big_modeling.py", line 366, in load_checkpoint_and_dispatch
load_checkpoint_in_model(
File "test/env/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 701, in load_checkpoint_in_model
set_module_tensor_to_device(model, param_name, param_device, value=param)
File "test/env/lib/python3.9/site-packages/accelerate/utils/modeling.py", line 124, in set_module_tensor_to_device
new_value = value.to(device)
RuntimeError: CUDA error: invalid device ordinal
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

Trying this with
model = galai.load_model("base")

it looks like there is a device map that expects 8 GPUs, if I'm seeing this right:
{'decoder.embed_tokens': 0,
 'decoder.embed_positions': 0,
 'decoder.layer_norm': 0,
 'decoder.layers.0': 0,
 'decoder.layers.1': 0,
 'decoder.layers.2': 0,
 'decoder.layers.3': 1,
 'decoder.layers.4': 1,
 'decoder.layers.5': 1,
 'decoder.layers.6': 2,
 'decoder.layers.7': 2,
 'decoder.layers.8': 2,
 'decoder.layers.9': 3,
 'decoder.layers.10': 3,
 'decoder.layers.11': 3,
 'decoder.layers.12': 4,
 'decoder.layers.13': 4,
 'decoder.layers.14': 4,
 'decoder.layers.15': 5,
 'decoder.layers.16': 5,
 'decoder.layers.17': 5,
 'decoder.layers.18': 6,
 'decoder.layers.19': 6,
 'decoder.layers.20': 6,
 'decoder.layers.21': 7,
 'decoder.layers.22': 7,
 'decoder.layers.23': 7}

Confirmed. Had same error and num_gpus = 1 resolved it.

Please mention that in your documentation / readme.

A model size between base and standard would be nice. I barely can't fit standard on my RTX 3090, I think.

Do you offer 8 bit versions/compatibility, like BLOOM?

I see, dtype='float16' does the job sorry. Please mention in readme. Many folks will want to try on a local gpu as well.

Hmm.. 8 bit would still be handy to play with larger models. Is that possible?

Num of GPUs defaults to None.

If you have less than the default number of GPUs (8)

Who has a default number of 8 GPUs?

people that work at Meta AI, probably XD

If you have less than the default number of GPUs (8), you have to specify how many when you load the model. Try: model = gal.load_model(name = 'base', num_gpus = 1)

why this isnt written on main page

galai 1.1.0 uses all available GPUs by default which should fix the issue. One can still manually specify the number of GPUs using num_gpus parameter. Setting num_gpus=0 (or keeping the default None if no GPUs are available) will load the model to RAM. 8 bit inference is not supported yet. Please reopen if you still experience any issues.


Implement protocol combinator for hard forks

We want to be able to combine two protocol, for example, pbft and praos, into a single protocol, where the first hard forks to the other. We should be able to do this in a generic way using a protocol combinator, which calls into the two protocols' definitions.
Setting up the general infrastructure is fairly simple, but the complexity lies in dealing with interaction between the hard fork, chain selection, and rollback. Functions from OuroborosTag such as preferCandidate have non-trivial semantics, and may even depend on the exact hard fork in some way. We should examine each of these tricky scenarios in turn to arrive at a principled mechanism for switching protocols.

Obsoleted by #946.


[opencv3] build failure

Host Environment

OS: [Windows 10 Pro 1909]
Compiler: vs2019

To Reproduce
Steps to reproduce the behavior:
./vcpkg install opencv3
install-x86-windows-dbg-out.log
Failure logs
PS C:\vcpkg> .\vcpkg update                                                                                Using local portfile versions. To update the local portfiles, use `git pull`.                                           No packages need updating.

PS C:\vcpkg> .\vcpkg upgrade
All installed packages are up-to-date with the local portfiles.

PS C:\vcpkg> .\vcpkg.exe install opencv3                                                                                Computing installation plan...
The following packages will be built and installed:                                                                         opencv3[core,dnn,flann,jpeg,opengl,png,tiff,webp]:x86-windows                                                       Starting package 1/1: opencv3:x86-windows                                                                               Building package opencv3[core,dnn,flann,jpeg,opengl,png,tiff,webp]:x86-windows...                                       -- Using cached C:/vcpkg/downloads/opencv-opencv-3.4.7.tar.gz                                                           -- Using source at C:/vcpkg/buildtrees/opencv3/src/3.4.7-76c703aeb9                                                     -- Using cached C:/vcpkg/downloads/opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz
-- Configuring x86-windows
-- Building x86-windows-dbg                                                                                CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:136 (message):                                               Command failed: C:/vcpkg/downloads/tools/cmake-3.14.0-windows/cmake-3.14.0-win32-x86/bin/cmake.exe --build . --config Debug --target install -- -v                                                                                Working Directory: C:/vcpkg/buildtrees/opencv3/x86-windows-dbg                                                          See logs for more information:                                                                                C:\vcpkg\buildtrees\opencv3\install-x86-windows-dbg-out.log                                                                                Call Stack (most recent call first):                                                                                scripts/cmake/vcpkg_build_cmake.cmake:91 (vcpkg_execute_build_process)                                                  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)                                                          ports/opencv3/portfile.cmake:305 (vcpkg_install_cmake)                                                                  scripts/ports.cmake:90 (include)                                                                                Error: Building package opencv3:x86-windows failed with: BUILD_FAILED                                                   Please ensure you're using the latest portfiles with `.\vcpkg update`, then                                             submit an issue at https://github.com/Microsoft/vcpkg/issues including:                                                   Package: opencv3:x86-windows                                                                                Vcpkg version: 2020.02.04-nohash                                                                                Additionally, attach any relevant sections from the log files above.                                                    PS C:\vcpkg>

Hi @linmonsv, thanks for reporting this issue!
Please provide install-x86-windows-dbg-err.log.
Thanks.

@JackBoosY Hi ,The file is empty ( 0 KB)

Seems related to #9585.

Thank you, I execute the the command that you mentioned.
Then the result is that :
The code execution could not continue because libprotoc.dll was not found. Reinstalling the program may resolve this issue
And I read the similar problem in the #9585
I try to copy the libprotoc.dll and libprotobuf.dll from C:\vcpkg\installed\x86-windows\bin to C:\vcpkg\installed\x86-windows\tools\protobuf and try to execute the command .\vcpkg.exe install opencv3
Everything is OK !

Does libprotobuf.dll and libprotoc.dll exist in C:\vcpkg\installed\x86-windows\tools\protobuf?

Yes, there are nothing except protoc.exe in C:\vcpkg\installed\x86-windows\tools\protobuf
and the problem is solved!

Does libprotobuf.dll and libprotoc.dll exist in C:\vcpkg\installed\x86-windows\tools\protobuf?
If these 2 libraries are not found, please remove libprotobuf and re-install it.

I re-install the libprotobuf and the dll is still not exist in C:\vcpkg\installed\x86-windows\tools\protobuf.
I manually copy it ,and the opencv install can be worked!

@linmonsv Could you provide install log C:/vcpkg/buildtrees/protobuf/install-x86-windows-rel-out.log ?

Okay, I do these command now, and the log is here
.\vcpkg remove protobuf
.\vcpkg install protobuf
install-x86-windows-rel-out.log

Seems vcpkg_copy_tool_dependencies doesn't work.

And will you repair this problem?
Or I ignore it ?

Digging deeper into this issue... that's why this issue is still open.

I still don't know why this issue happened. If anyone encounters this issue again, please ping me.


Document the configurable-env unstable option

Add a section to the unstable doc describing the -Z configurable-env option and the [env] section in the config.toml file.

Thanks!
@bors r+

:pushpin: Commit 4d7a29b759abda07aa45490eb4d947a6b920dc90 has been approved by ehuss

:hourglass: Testing commit 4d7a29b759abda07aa45490eb4d947a6b920dc90 with merge 970bc67c3775781b9708c8a36893576b9459c64a...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 970bc67c3775781b9708c8a36893576b9459c64a to master...


Cloud SOAR and Automation Service first release notes

PLEASE READ
Following a recent back-end update, all contributors with a local clone or fork of our repository are required to run yarn install. This does not apply to direct page edits.

[x] Yes, I've run yarn install
[ ] No, does not apply to me

Purpose of this pull request
This pull request...
To reflect Cloud SOAR and Automation Service content update, updated also structure adding specific entry to Automation Service
Select the type of change:

[ ] Minor Changes - Typos, formatting, slight revisions
[x] Update Content - Revisions and updating sections
[x] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@fzampori, we will add you to our list of contributors with PR #3242.


add more docker label choices

Make it easier for users to subscribe to monthly Grist releases, rather than the daily latest. Fixes https://github.com/gristlabs/grist-core/issues/569

Tried this on a fork and it did add a stable tag.


Couldn't add component: "test"

Hi,
When I try to create a file using the context menu or command pallette, I get an error message. I can create them using nuxi from CLI.

Log:
without file extension:
env: node: No such file or directory

with file extension:
["SanitizeInput"]: Input "test.vue" has an extension. Sanitizing now -> "test"
env: node: No such file or directory

Hey @ozum ! Thanks for reporting!. I just tested it within my environment and it seems to work as intended. Can you possible send over a video of the steps to reproduce.
Things I might need to know to better understand where the error is occurring:

OS System
Node Version
VS Code on the latest with latest update with nuxt-vscode ?

https://user-images.githubusercontent.com/6619884/217263665-a2f93b31-e25e-4230-a294-816d58ac9050.mov


[model] Harmonize update, prerelease, and snapshot sections

Turn update and prerelease into their own sections, such that
release:
  github:
    update:
      enabled: true
      sections:
        - ASSETS
     prerelease:
       enabled: true

Affects model and auto-config release.
Related to https://github.com/jreleaser/jreleaser/issues/335
Follow up to https://github.com/jreleaser/jreleaser/issues/307

@gsmet @maxandersen please watch out for this breaking change when upgrading to 1.0.0-M2 or later.


small typo in chapter_2_5.md

the capability variable shows up in 2 code blocks -- in the first one it is capability and in the 2nd it's _capability. This PR changes the first occurrence to match the 2nd.

@frankmcsherry tagging you in case you missed this

Sorry! I totally did see it and should have ack'd. I had some random thought that I should collect commits together to minimize churn for others (we end up with PRs when timely master changes). But, I'll figure that out later!

Thanks very much for the thorough reads!


Update README.md

Hello, just wanted to add a plugin which uses piper that I recently started working for a game client. It was a huge success! Thank you so much for this amazing project.

Very nice! You're welcome 🙂


WIP: Issue/#83 release annotations

Hello @ceckoslab
Here is latest changes required to achieve dynamic release annotations
Kindly review and let me know
P.S. Also need to update test to reflect latest changes

Hello @ceckoslab
I fixed currently existing tests and prepared to implement dynamic releases tests. I guess we need some tests for that.
Also I think we need to implement releases for other types of diagram, am I right?
So I hope tomorrow we will have tests and releases implemented for all kind of diagrams

Hello @korzol
I think that it looks fine for now. Please do not implement more things for other diagram types because I am planning to do some refactoring around the view logic.
Could you go in to details about what and where you plan to implement more tests?

Hello @ceckoslab
I thought about adding another file into /tests/BasicRum/DiagramBuilder/ directory. Lets say DevicePerformaceTest.php or DevicePerformaceDesktopTest.php which will test diagram building for device performance (desktop) which is time_series and where dynamic releases is applicable

Hello @korzol
Could you write one more when the Data Layer returns empty result set? I remember that we were getting a notice for undefined variable in this case and our tests were failing.

Hello @korzol
Is this PR still a WIP? If not, could you remove the WIP part of the title?


[glslang] Add support for rtti in glslang port

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[X] The "supports" clause reflects platforms that may be fixed by this new version
[X] Any fixed CI baseline entries are removed from that file.
[X] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

This adds support for using the ENABLE_RTTI option in the glslang port.

Feature rtti is tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static

Ping @omartijn

Well, I'm not sure whether or not it should be an alternative. AFAIU building the library without RTTI can lead to linker errors if you then end up needing those symbols (e.g. for a dynamic_cast), but building the library with RTTI and then not using them is not an error.
Of course, building with RTTI willl lead to a bigger library, which might in some cases end up causing trouble, but I guess that goes for practically all feature flags, wouldn't it?

Well, I'm not sure whether or not it should be an alternative. AFAIU building the library without RTTI can lead to linker errors if you then end up needing those symbols (e.g. for a dynamic_cast), but building the library with RTTI and then not using them is not an error.

The point is, is it possible that a downstream customer breaks if the library was built with RTTI? If that's impossible then the PR as written is OK.

Ping @omartijn

I don't know what else to say. I don't think adding RTTI when not needed can cause trouble, except for the fact that it creates a slightly larger library. It might have some runtime overhead as well.

/azp

Mark info:reviewed for further review.


JSDoc type for blocksToMarkdown's mdBlocks

In the blocksToMarkdown definition, the mdBlocks argument JSDoc hint is "Defines max depth of nesting," but I think this is a typo and it should read "Array of markdown blocks" as in toMarkdownString.
* @param {MdBlock[]} mdBlocks - Defines max depth of nesting
to
* @param {MdBlock[]} mdBlocks - Array of markdown blocks

Hi! Thank you for raising this issue.
We're currently working on notion-to-md v4 which includes significant architectural improvements so this can be sorted along the way.
I'd love your insights on this. Please checkout the GitHub discussion #114  to discuss how we can best solve your use case? Your feedback would be really valuable in shaping v4's development.


Create a standard for Systematic Updates

When and how to update systematic studies?
Some pointers:

Mendes et al., When to update systematic literature reviews in software engineering
Garner et al., When and how to update systematic reviews: consensus and checklist
Wohlin et al., Guidelines for the search strategy to update systematic literature reviews in software engineering

We are working on breaking the systematic review standard into several more specific standards - for meta-analysis, meta-synthesis, case survey, etc. Once we know what that looks like, we can come back to how to deal with updates.


Use fluent api to set DebugLocation

I would prefer this to be added in IRBuilder instead as a running state, so that every new instruction is emitted with the last location set. (I believe this would make it easier to emit instructions with proper/coarse location tracking from an AST visitor perspective.)
We probably also need an overload that takes DebugSourceLocation?, mainly to allow null for setting "hidden" sequence points, and for copying existing locations.
Maybe we should also rename that property to DebugLocation while we have the chance, but otherwise I don't see why not keep the setter as public?

Thanks for your PR, I went ahead and implemented this as my IRBuilder proposal in 0bcc0cc4.
When creating new instructions, I believe propery initializers may be enough to roughly mirror this feature: new Instruction(...) { DebugLocation = ... }


[boost-build] Build error on x64-windows

Package: boost-build:x64-windows -> 1.83.0
Host Environment

Host: x64-windows
Compiler: Clang 17.0.3
vcpkg-tool version: 2023-11-16-4c1df40a3c5c5e18de299a99e9accb03c2a82e1e
vcpkg-scripts version: a42af01b7 2023-11-20 (7 months ago)

To Reproduce
vcpkg install --x-feature=suyu-tests --x-feature=web-service
Failure logs
-- Using cached boostorg-build-boost-1.83.0.tar.gz.
-- Cleaning sources at C:/Users/86017/cuda/suyu/externals/vcpkg/buildtrees/boost-build/src/ost-1.83.0-93738d0a3a.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/86017/cuda/suyu/externals/vcpkg/downloads/boostorg-build-boost-1.83.0.tar.gz
-- Applying patch 0002-fix-get-version.patch
-- Applying patch 0003-fix-emscripten.patch
-- Applying patch 0004-workaround-MSVC-codegen-bug-in-17.5-on-ARM64.patch
-- Using source at C:/Users/86017/cuda/suyu/externals/vcpkg/buildtrees/boost-build/src/ost-1.83.0-93738d0a3a.clean
-- Using cached boost_LICENSE_1_0.txt.
-- Using cached boost-1.83.0-boostcpp.jam.
-- Installing: C:/Users/86017/cuda/suyu/externals/vcpkg/packages/boost-build_x64-windows/share/boost-build/copyright
-- Bootstrapping...
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: C:/Users/86017/cuda/suyu/externals/vcpkg/packages/boost-build_x64-windows/tools/boost-build/bootstrap.bat msvc
    Working Directory: C:/Users/86017/cuda/suyu/externals/vcpkg/packages/boost-build_x64-windows/tools/boost-build
    Error code: 1
    See logs for more information:
      C:\Users\86017\cuda\suyu\externals\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
      C:\Users\86017\cuda\suyu\externals\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log

Call Stack (most recent call first):
  buildtrees/versioning_/versions/boost-build/bd9d972c221f9e5bdd839246960791cdcfe80524/portfile.cmake:65 (vcpkg_execute_required_process)
  scripts/ports.cmake:170 (include)

C:\Users\86017\cuda\suyu\externals\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-err.log
'"cl"' is not recognized as an internal or external command,
operable program or batch file.
File Not Found

C:\Users\86017\cuda\suyu\externals\vcpkg\buildtrees\boost-build\bootstrap-x64-windows-out.log
Building the B2 engine..
Call_If_Exists "bin\VCVARS32.BAT"
###
### Using 'msvc' toolset.
###

C:\Users\86017\cuda\suyu\externals\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine>"cl" /nologo /MP /MT /TP /Feb2 /wd4996 /O2 /GL /EHsc   -DNDEBUG  builtins.cpp class.cpp command.cpp compile.cpp constants.cpp cwd.cpp debug.cpp debugger.cpp execcmd.cpp execnt.cpp execunix.cpp filent.cpp filesys.cpp fileunix.cpp frames.cpp function.cpp glob.cpp hash.cpp hcache.cpp hdrmacro.cpp headers.cpp jam.cpp jamgram.cpp lists.cpp make.cpp make1.cpp md5.cpp mem.cpp modules.cpp native.cpp object.cpp option.cpp output.cpp parse.cpp pathnt.cpp pathsys.cpp pathunix.cpp regexp.cpp rules.cpp scan.cpp search.cpp jam_strings.cpp startup.cpp subst.cpp sysinfo.cpp timestamp.cpp variable.cpp w32_getreg.cpp modules/order.cpp modules/path.cpp modules/property-set.cpp modules/regex.cpp modules/sequence.cpp modules/set.cpp /link kernel32.lib advapi32.lib user32.lib

C:\Users\86017\cuda\suyu\externals\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine>dir *.exe
 Volume in drive C is Windows
 Volume Serial Number is 2069-CE9F

 Directory of C:\Users\86017\cuda\suyu\externals\vcpkg\packages\boost-build_x64-windows\tools\boost-build\src\engine

Failed to build the B2 engine.

Additional context
vcpkg.json
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "name": "suyu",
  "builtin-baseline": "a42af01b72c28a8e1d7b48107b33e4f286a55ef6",
  "version": "1.0",
  "dependencies": [
    "boost-algorithm",
    "boost-asio",
    "boost-bind",
    "boost-config",
    "boost-container",
    "boost-context",
    "boost-crc",
    "boost-functional",
    "boost-heap",
    "boost-icl",
    "boost-intrusive",
    "boost-mpl",
    "boost-process",
    "boost-range",
    "boost-spirit",
    "boost-test",
    "boost-timer",
    "boost-variant",
    "fmt",
    "lz4",
    "nlohmann-json",
    "zlib",
    "zstd"
  ],
  "features": {
    "suyu-tests": {
      "description": "Compile tests",
      "dependencies": [
        "catch2"
      ]
    },
    "web-service": {
      "description": "Enable web services (telemetry, etc.)",
      "dependencies": [
        {
          "name": "openssl",
          "platform": "windows"
        }
      ]
    },
    "android": {
      "description": "Enable Android dependencies",
      "dependencies": [
        {
          "name": "oboe",
          "platform": "android"
        }
      ]
    }
  },
  "overrides": [
    {
      "name": "catch2",
      "version": "3.3.1"
    },
    {
      "name": "fmt",
      "version": "10.1.1"
    }
  ]
}

vc140  replace vc144


Error: The camera must be a PerspectiveCamera to orbit controls work

Im using r3f-native library which works as charm, but the thing is that I want to change the camera to orthographic instead of Perspective but gets me the following error:
Error: The camera must be a PerspectiveCamera to orbit controls work
Here is my code:
<Canvas orthographic camera={{ zoom: 50, position: [0, 0, 100] }}>

<pointLight position={[10, 10, 10]} />
{*

*}

Thanks!:)

Hi @Osmanity, thanks for creating the issue!
I have released a new version that adds support to OrtographicCamera's.

Thanks for the quick reply, will try it later this evening!:)


Support for One Call API 3.0

With support for one call API 2.5 ending on April 15, 2024. Support for one call API 3.0 would be needed to keep the app working with open weather map.
https://openweathermap.org/api/one-call-api

@jacobgonzales20 it should be already possible. You should be able to select it from the providers settings

@jacobgonzales20 it should be already possible. You should be able to select it from the providers settings

I found it, though the popup for refresh is quite annoying.

@jacobgonzales20 what refresh popup are you talking about?

@jacobgonzales20 what refresh popup are you talking about?

@jacobgonzales20 It comes from OpenWeather. It means your key is not compatible with 3.0


Is the data on hugging face complete?

dear developer, I noticed that the video data you provided on the hugging face platform -- LanguageBind/Open-Sora-Plan-v1.0.0, contain 1 mixkit package, 00-05 pexels package, and 00-19 pixabay package. Are these the whole data uploaded? (especially the pixabay data, I want to ensure if there exist any more increments)

Complete now.


[Feature-Request] Homepage - Expand content section

Background
As this site is a demo, the homepage should inform and engage users
User Story

As a stakeholder
I want to provide users with a comprehensive homepage experience
So that users are engaged

Acceptance Criteria

Given (this feature)
When I view the homepage
Then I am provided with a comprehensive homepage experience

Additional context
This will require an update to the Homepage user story.

This update should include a description of the following:
project management
production infrastructure
testing


Issue 4546: Refactor FD with a general I/O Handle

Description:
Introduce an abstract I/O Handle and one derivative for sockets, the IoSocketHandle.
Preserve fd semantics in all socket-related system calls with ioHandle->fd(). In this
initial PR, all calls which take an fd retain their same parameters.
Risk Level:
Low
Testing:
Everything covered by bazel test //test...

@mattklein123 It looked like the circle:mac test passed. I couldn't view the cicrleci:ipv6 test, so Im not sure what the issue is there. Please review.

@sbelair2 it seems there have been a lot of PRs opened/closed for this patch. It's kind of hard to reason across this chain; can you try and stick to one PR per change? If you need git assistance, happy to help out here or on Slack.

@htuch Yes, I totally botched previous PR attempts. I then hit issues with check_repositories, which I did post on slack. As of this posting of this PR last night, there were no conflicts and the diffs presented were final. I really am not sure how you would prefer the next steps to be- I thought that the state of the PR was fine in that the diffs represent the final outcome of the PR. What would you suggest?

@sbelair2 I think we are just trying to understand whether you have figured out your workflow issues before we start reviewing. This PR already needs a master merge. Can you do that to make sure that workflow works for you? Thanks.

@mattklein123 I have basically figured out my workflow issues, thanks to Ed Warnicke's help (don't know his GitHub handle). I am working on the master merge as we speak. The several consecutive pushes to my fork were a result of my fetching upstream, merging upstream changes with my changes, and then pushing. Once pushed, I see that I was out of sync again, and again. Is the issue for the reviewers that there were several pushes to my fork? In which case, a squash is required? My code changes are indeed in a final state, but I appear to be chasing the parade of changes here. Feel free to advise- thank you.

@mattklein123 Understood. Closing this PR and coming back with another correct one.

@sbelair2 you didn't need to close this PR ... Just merge master ... I would really commend syncing up with someone a little bit about git or maybe looking at a GitHub tutorial?

@mattklein123 I did as you suggested: merged with master and eventually pushed. Hopefully the DCO will still be ok after the merge.

@mattklein123 As suspected, there was an issue with DCO after the merge. I tried "git commit --amend --signoff" after the merge completed, but it has no affect. Note that the DCO was correct previously. Please advise.

@sbelair2 I don't think you actually did a merge commit. Can I kindly ask that you find someone to help you with git and GitHub? Unfortunately we don't have the resources to help with this.

/sub

@mattklein123 I do have someone I can ask, I'm not going it alone here. I did a "git merge upstream/master", which worked fine except for the signoff (It appears that the --signoff flag can now be included with merge). Is the only issue the missing DCO signoff, or are there other issues that you see? If other issues, I can close the PR and open a new one that fixes them, Thank you.

I have a higher level question on the plan with this PR -- there have been a few other attempts to abstract network handles, and I think it's a very achievable, beneficial project.  However there are a couple of complexities that at first glance this PR does not tackle:

on some OS's an 'int' is not the most appropriate representation for a network handle, and it should not be exposed on the abstract interface.
There are some interactions with libevent that would need to be abstracted as well, since libevent has knowledge of int FDs.

It might be helpful to start with a design doc and iterate on that.

Ah I see that you were one of the authors of the earlier PRs: #4579 -- sorry for the confusion.

@sbelair2 I'm sorry I'm not sure where you went wrong with the DCO. You can fix by rebasing and force pushing. Please do not open new PRs.

I don't think DCO is the only remaining issue.   If you look at the files view, I see many changes which aren't yours, which indicates something else has gone wrong :-/

@alyssawilk Correct! I see 89 files. changed, whereas my commit involved 41 files. Can this PR be salvaged?

Yep, if you git rebase correctly (normally strongly discouraged but no one has reviewed this so it should be fine) and force push per Matt's earlier advice you should be able to correct this.

@alyssawilk I've been looking at the extra files in this PR, and those are all the files that have been pulled from upstream/master and are being pushed into my fork- it would be incorrect to exclude them. I do think that DCO is the only apparent issue. Do you agree?

@alyssawilk Got it- makes sense. Thanks!

@sbelair2, envoy quic also need this IoHandle interface. Do you mind to add some interfaces we need into this PR? Please check https://github.com/envoyproxy/envoy/pull/5171 for your reference.


Conditional operator: when the condition and first expression are the same, OR could be used instead

This should (partially) fix https://github.com/google/closure-compiler/issues/180.
When using the ? operator the following can be transformed:
x ? x : y
to a shorter equivalent:
x || y.
I added a Unit test to verify that the change works. However the transformation only works for conditionals now, e.g. in an if statement. It does not work for example in an assignment statement yet.

This is not a safe optimization in the general case. Folding x() ? x() : y() to x() || y() is incorrect if x() has side effects. Even folding x.y ? x.y : x.z is unsafe if x.y triggers a getter with side effects.
I think this should be restricted to NAME accesses.

Right, I see what you mean, I'll try to restrict this to NAME accesses.

I guess I can squash the commits later into a single commit, right?

@lbercken Yes, please squash and rebase.

I'll bring this in and test it.

@lbercken I've submitted this internally and it should be synced externally later today. I changed the condition to !mayHaveSideEffects(condition) && !mayHaveSideEffects(trueNode) && condition.isEquivalentTo(trueNode) so it folds function calls that are deemed side-effect free by the compiler, and also for GETPROPs, which are assumed to be side-effect free: https://github.com/google/closure-compiler/wiki/Compiler-Assumptions#details.

@Dominator008 Alright, thanks! Also thanks for your support and help. Didn't know about the mayHaveSideEffects method and the assumption detail page. By the way, we might have to change the comments (I added) saying:
//   Only when x is NAME, hence x does not have side effects
//   x ? x : y        --> x || y
accordingly.

@lbercken I think the documentation in the unit test suffices :)


Compatibility of shared_examples with Ruby 3

Subject of the issue
Compatibility of shared_examples with a "Real" keyword argument from upcoming Ruby 3
Your environment

Ruby version: 2.7.0preview3
rspec-core version: 3.9.0

Steps to reproduce
RSpec.describe 'ruby 2.7.0.preview3 warning' do
  shared_examples 'expects hash' do |hash|
    it { expect(hash[:input].reverse).to eq(hash[:output]) }
  end

  shared_examples 'expects keywords' do |input:, output:|
    it { expect(input.reverse).to eq(output) }
  end

  include_examples 'expects hash', input: 'afla', output: 'alfa'
  include_examples 'expects hash', { input: 'ovarb', output: 'bravo' }

  include_examples 'expects keywords', input: 'eilrahc', output: 'charlie' # Warning
  include_examples 'expects keywords', { input: 'atled', output: 'delta' } # Warning
end

Expected behavior

charlie example should not produce any warning
alfa should not be supported to follow Ruby 3 changes (?)

Actual behavior
Following warning is being printed for charlie and delta case
/home/wojciechko/.rbenv/versions/2.7.0-preview3/lib/ruby/gems/2.7.0/gems/rspec-core-3.9.0/lib/rspec/core/shared_example_group.rb:36: warning: The last argument is used as the keyword parameter
/home/wojciechko/dev/sample_spec.rb:6: warning: for method defined here

Work here is needed to figure out what they've changed and why this is issuing a warning, I suspect we just haven't considered keyword argument at all and they've just worked due to their hash like nature. The implementation should be agnostic to what is passed in and just pass through the arguments. (Meaning the "alfa" example will not work on ruby 3, but continue to work everywhere else).

This also affects rspec-expectations: https://github.com/rspec/rspec-expectations/issues/1150
and rspec-mocks: https://github.com/rspec/rspec-mocks/issues/1306
I was beginning to prepare PRs for these things that simply pass **kwargs trough all participating methods. This does fix these issues. However, in rspec-core that produced some other problems with example metadata being lost, which apparently passes through the same code paths. While I looked into that I noticed to my amazement that you still support ruby 1.9 and even 1.8, so that whole approach won't even work (at least without a lot of insane, RUBY_VERSION-based eval'ing).
Perhaps this is a sensible time to stop supporting these versions?

Metadata is a hash, so its not going to work treating it as keyword arguments everywhere, as we expect it to be a hash. So this warning is actually a symptom of mis-using the implementation.... So I'm kind of tempted to issue an explicit warning explaining that rather than trying to add this.

While I looked into that I noticed to my amazement that you still support ruby 1.9 and even 1.8, so that whole approach won't even work (at least without a lot of insane, RUBY_VERSION-based eval'ing).
Perhaps this is a sensible time to stop supporting these versions?

I'm afraid that won't happen until the next major version due to semver.

Wondering if the change to:
-      def self.include_examples(name, *args, &block)
-        find_and_eval_shared("examples", name, caller.first, *args, &block)
+      def self.include_examples(name, *args, **kwargs, &block)
+        find_and_eval_shared("examples", name, caller.first, *args, **kwargs, &block)

will do the job.
Still, define_nested_shared_group_method and include_context needs to be tweaked the same way.
Please correct me if I'm wrong, it seems there's no way around eval and adding strict_kwargs? to rspec-support.
A temporary measure around warnings can be the usage of ruby2_keywords macro (also needs to be wrapped, to only be called when it's available).

Related https://github.com/rubocop-hq/rubocop/pull/7584

Yeah I mean you should be able to remove the warnings by just accepting the hash as is...

We fixed this in #2716 but adding further specs in #2719, closing.


#12605: Add governor notes and move models steps into separate steps

Ticket
#12605
Problem description
@mbahnasTT requested instructions on perf governor for models.
What's changed
Add separate models section for installation.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

@mbahnasTT Please review these changes for perf governor.

Thanks @tt-rkim !


SyntaxError: await is only valid in async function

my code:
const { QAClient } = require("question-answering"); // If using vanilla JS

const text = `
  Super Bowl 50 was an American football game to determine the champion of the National Football League (NFL) for the 2015 season.
  The American Football Conference (AFC) champion Denver Broncos defeated the National Football Conference (NFC) champion Carolina Panthers 24–10 to earn their third Super Bowl title. The game was played on February 7, 2016, at Levi's Stadium in the San Francisco Bay Area at Santa Clara, California.
  As this was the 50th Super Bowl, the league emphasized the "golden anniversary" with various gold-themed initiatives, as well as temporarily suspending the tradition of naming each Super Bowl game with Roman numerals (under which the game would have been known as "Super Bowl L"), so that the logo could prominently feature the Arabic numerals 50.
`;

const question = "Who won the Super Bowl?";

const qaClient = await QAClient.fromOptions();
const answer = await qaClient.predict(question, text);

console.log(answer); // { text: 'Denver Broncos', score: 0.3 }

Error :
SyntaxError: await is only valid in async function
at wrapSafe (internal/modules/cjs/loader.js:1063:16)
at Module._compile (internal/modules/cjs/loader.js:1111:27)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1167:10)
at Module.load (internal/modules/cjs/loader.js:996:32)
at Function.Module._load (internal/modules/cjs/loader.js:896:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
at internal/main/run_main_module.js:17:47

Update:
I put it in an async function but now I get this error:
Error: The specified module could not be found.
<EMAIL_ADDRESS>

It seems your problem is related to the underlying TensorFlow library. Can you try running npm i @tensorflow/tfjs-node in your project to be sure it's correctly installed and try again?

I get the same issue as @alikabeer32
I've run the npm i above and have the following package.json
    "@tensorflow/tfjs-node": "^1.7.4",
    "question-answering": "^2.0.1"

Any sugggestions?

I'm on node version v10.13.0 btw

Which issue are you referring to exaclty @braaannigan? The one from the first message or the second message?

Hi @Pierrci I think I fixed this by updating all my versions of node/npm etc. Have had a computer rebuild in the interim, so can't provide any more detail unfortunately.

Great! Closing this for now, feel free to reopen if needed.


Add include to whitelist editable files

It would be great to have some sort of whitelist instead of the blacklist provided by ignore. Often I may only have one or two directories which should be editable using prose.io.

In that case I think you'd want to set a rooturl in _config.yml to specify which directory your prose-editable files live in. It might take a bit of adjusting your directory structure if you have two directories instead of one.

Closing as wont-fix.


document is err

look http://pulsar.apache.org/docs/zh-CN/administration-pulsar-manager/
the  docker command  no  -- link,

@sixhj Could you please give more details about the problem? Or if you are interested in fix this issue you can push a PR for it.

docker run -it
-p 6650:6650
-p 8080:8080
--mount source=pulsardata,target=/pulsar/data
--mount source=pulsarconf,target=/pulsar/conf
apachepulsar/pulsar:2.6.2
bin/pulsar standalone
no.  --name.
docker pull apachepulsar/pulsar-manager:v0.2.0
docker run -it
-p 9527:9527 -p 7750:7750
-e SPRING_CONFIGURATION_FILE=/pulsar-manager/pulsar-manager/application.properties
apachepulsar/pulsar-manager:v0.2.0
no  --link  , so    pulsar manager  new environment   ,  the service URL    , what is input ?

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


Disable process scanning on AIX

On an AIX 6.1 box, setting CFLAGS="-D_ALL_SOURCE -D_LINUX_SOURCE_COMPAT" was necessary, otherwise proc.c cannot be compiled.
libtool: compile:  gcc -DPACKAGE_NAME=\"yara\" -DPACKAGE_TARNAME=\"yara\" -DPACKAGE_VERSION=\"3.6.3\" "-DPACKAGE_STRING=\"yara 3.6.3\""<EMAIL_ADDRESS>-DPACKAGE_URL=\"\" -DPACKAGE=\"yara\" -DVERSION=\"3.6.3\" -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DWORDS_BIGENDIAN=1 -DHAVE_LIBM=1 -DHAVE_LIBM=1 -DHAVE_MEMMEM=1 -I. -I../../libyara -Wall -Wno-deprecated-declarations -std=gnu99 -I../../libyara/include -O3 -fvisibility=hidden -D_LINUX_SOURCE_COMPAT -D_THREAD_SAFE -MT proc.lo -MD -MP -MF .deps/proc.Tpo -c ../../libyara/proc.c -o proc.o
In file included from /usr/include/sys/thread.h:37:0,
                 from /usr/include/sys/ptrace.h:28,
                 from ../../libyara/proc.c:187:
/usr/include/sys/var.h:128:2: error: unknown type name '__cptr64'
  __cptr64  ve_lock; /* RO: ptr to end of recordlock table*/
  ^~~~~~~~
[...]
/usr/include/sys/ptrace.h:191:2: error: unknown type name 'offset_t'
  offset_t pt_watchpoints_offset; /* offset to _pt_watchpoint's */
  ^~~~~~~~
gmake[1]: *** [Makefile:650: proc.lo] Error 1

I don't know yet whether yr_rules_scan_proc works with those defines, but I suppose it may be best to disable it on AIX...

Do you have files /proc/XX/maps and /proc/XX/mem on AIX? Does they have the same structure than in Linux? If not, we should completely disable process scanning in AIX or implementing something specific for AIX.

There is a /proc filesystem, but it is different enough that it would require special support, so I think that disabling it may be a good idea. All the necessary bits seem to be there and instead of parsing lines of data, one can use predefined structs from <sys/procfs.h>, how about that! And it is very well documented.

If you would like to have support for process scanning on AIX go ahead, that would be a nice addition.

In case you decide to implement it, I think it would be better to split the proc.c file into multiple files (one per platform) under a /proc directory.

I don't think I am going to have the time for this in the near future, so it would be better to disable process scanning -- actually for all unrecognized systems.
I see that there FreeBSD and OpenBSD seem to be explicitly supported (although a later comment only mentions Linux ... https://github.com/VirusTotal/yara/blob/984ee76caba8cff35222fc7b564cdfb19ca457f1/libyara/proc.c#L338
Has process scanning actually been tested on those systems?

Why are you surprised? The PR was good :)


Update VO information

Summary

Get ready for validation of the VO information
Update all known VOs for now

Related issue :

Linting error are due to https://github.com/github/super-linter/issues/2128

Linting errors are due to github/super-linter#2128

Should we try to apply this: https://github.com/github/super-linter/issues/2128#issuecomment-968202245 or wait untill they fix the missing image?

It was reported last Friday so I guess it could be fixed "soon". Basically it depends on the urgency level for merging this. I leave it up to you, both are fine with me.

@enolfc you won a few new points to be addressed :)

@enolfc you won a few new points to be addressed :)

wow, this linter can be picky:

23:31  ✓ error  Incorrect usage of the term: “repo”, use “repository” instead  terminology

@enolfc you won a few new points to be addressed :)

wow, this linter can be picky:

23:31  ✓ error  Incorrect usage of the term: “repo”, use “repository” instead  terminology

Yes but I tend to agree with him :)


Add filter "Is Published " on source datasets tab

With values yes/no depending on if the source dataset has a DOI.
Group with "in cellxgene" filter.

Coomplete


chore: jx-go-v13 to 0.0.4

chore: Promote jx-go-v13 to version 0.0.4

@jezreelcn-g: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

promotion-build
402b835593382e91bf94ac1b41248f802babb583
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Screenshot or Demo?

I'm interested in quickly seeing what this looks like.

@geirman uploaded screencast gif and an example project

Looks great! Thanks for adding additional detail to the readme too!


Added Note in #3093

Added note Please validate with the author before merging.
Copy review @nenonix @JohanFreelancer9 is required on this one guys.
Thank you in advance!
Issue #3093

@LanaChin PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Closing this PR as it's been addressed in #3460. Thanks.


Add mysql templates

Issue 1: kubernetes-mysql template
connection output does not match generated kubernetes service:

[alicloud-mysql]
Enable Publicly Accessible. Output endpoint of a deployed instance is an internal address and is not publicly accessible.

[x] kubernetes mysql
[x] static mysql
[x] alicloud mysql
[x] aws mysql

Verified in main


Move away from DialogFragment and try using a custom view or maybe a proper dialog

Should mention that I will explore this idea. Not sure if worth the trouble given the simplicity of the view.


Edit session - Account selector

Testing #153386
I am seeing weird behaviour related to the account selector when trying to create and result edit sessions. the behaviour is pretty random but I am signed in to VS Code Desktop with both GitHub and Microsoft, and I am signed in to https://insiders.vscode.dev with GitHub:

On web, I am asked to pick an account to use for the edit session even though I am signed in with one account
On desktop, there are times when I am asked to pick an account when creating an edit session and there are times when that does not happen
On desktop, i have seen a case when I tried to restore an edit session, the account picker showed up, even though I was seeing in the background that the edit session was successfully restored

Apologies if this is not helpful, but I am happy to either set up a screen share, or collect additional logs if available.

On web, I am asked to pick an account to use for the edit session even though I am signed in with one account

Do you mean that after signing into edit sessions once on web, you are asked to sign in again to apply edit sessions on web?

On desktop, there are times when I am asked to pick an account when creating an edit session and there are times when that does not happen

This should happen the first time that you do anything with edit sessions on desktop, or any subsequent occasion when auth fails (e.g. an expired token). If you see this happen unexpectedly, the Log (Window) channel might help.

On desktop, i have seen a case when I tried to restore an edit session, the account picker showed up, even though I was seeing in the background that the edit session was successfully restored

This definitely shouldn't happen, again I would love to see the logs if this happens again.

Verification steps:

Sign out of edit sessions via the accounts menu on insiders.vscode.dev and desktop VS Code Insiders
Store an edit session from desktop, sign in when prompted
Restore edit session from web, sign in when prompted
Store edit session from web, ensure you are not prompted to auth
Restore edit session from desktop, ensure you are not prompted to auth as well


🐛 photoResolution: 'max' not the same as native camera photo.

What's happening?
I wanted to take a picture using react-native-vision-camera that has the same resolution as the native device's camera app.
Currently, I have been experimenting with photoResolution: 'max' and was expecting to see the same resolution as the native camera.
Currently, the react-native-vision-camera produces photos:  12MP, 3024x4032, whereas the device camera takes photos at 24MP, 4284 x 5712 (both are using the 'main camera').  I had thought the photoResolution: 'max' would force it to use the same high resolution as the native device's camera.
Device is:  iPhone 15 max
Any insight on how to force it to use the maximum resolution available?
Thank you so much,
Reproduceable Code
const device = useCameraDevice('back');
const format = useCameraFormat(device, [
    { photoResolution: 'max'},  // use max resolution possible.
    { photoHdr: true }  // High Dynamic Range
]);

<Camera
        ref={camera}
        style={StyleSheet.absoluteFill}
        device={device!}
        format={format}
        enableHighQualityPhotos={true}
        isActive={isActive}
        onTouchStart={handleFocus}
        enableZoomGesture
        photo
      />

const takePhoto = useCallback(async () => {
    const photo = await camera.current?.takePhoto({
      qualityPrioritization: 'quality',
      flash: 'auto',
      enableShutterSound: true
    });

Relevant log output
N/A

Camera Device
"id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "position": "back",
  "hardwareLevel": "full",
  "minFocusDistance": 20,
  "hasTorch": true,
  "sensorOrientation": "landscape-right",
  "supportsLowLightBoost": false,
  "maxExposure": 8,
  "maxZoom": 123.75,
  "supportsRawCapture": false,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "neutralZoom": 1,
  "minZoom": 1,
  "isMultiCam": false,
  "formats": [],
  "hasFlash": true,
  "name": "Back Camera",
  "minExposure": -8
}

Device
iPhone 15 pro max
VisionCamera Version
3.9.2 (v4)
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[X] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

hi,
Thank you for your help.  So, I've experimented with the different physical devices ('ultra-wide-angle-camera', 'wide-angle-camera', 'telephoto-camera' and various multi-cam configurations.  Still can't seem to capture pictures that are of the same high-resolution as a native device's camera.  Here's a brief breakdown:
Using an iPhone 15 pro max, the example app in 'react-native-vision-camera iOS example', the result is:   8MP, 2160x3840
Using an iPhone 15 pro max, my react-native-vision-camera app and
const device = useCameraDevice('back', {
physicalDevices: ['wide-angle-camera']
});
the result is: 12MP, 3024 x 4032
Using an iPhone 15 pro max, my react-native-vision-camera app and
const device = useCameraDevice('back', {
physicalDevices: ['ultra-wide-angle-camera', 'telephoto-camera']
});
the result is: 12MP, 3024 x 4032
Using an iPhone 15 pro max, my react-native-vision-camera app and
const device = useCameraDevice('back', {
physicalDevices: ['ultra-wide-angle-camera', 'wide-angle-camera', 'telephoto-camera']
});
the result is:  12MP, 3024x4032
Using an iPhone 15 pro max, my react-native-vision-camera app and
const device = useCameraDevice('back', {
physicalDevices: ['ultra-wide-angle-camera', 'wide-angle-camera']
});
the result is:  12MP, 3024x4032
Using the iPhone 15 pro max's camera:
the result is: 24MP, 5712 x 4284
[The scene was exactly the same for all of the above picture taking]
So, the question is, how can I configure react-native-vision-camera to use the same high-resolution as the default camera (i.e, 24MP, 5712 x 4284)?
Thank you so much for your help
kind regards

I think the default Camera shoots ProRAW or HEIF or something where it can do higher resolution. VisionCamera doesn't have support for that yet (see https://github.com/mrousavy/react-native-vision-camera/issues/1851)

Uhm.. did you read the issue I linked ?
It is currently a feature request I'm raising money for to fund it - I don't plan on developing this for free in my free time

Could you explain how the process works, please?

People donate some funds, and once the pool is full I will implement it.

how long does it generally take for the funds to reach the appropriate level?  how long will it take to implement the feature?  what if more funds are needed (ie., it is more complex than originally assessed)?

I don't know, I don't have a lot of experience with that.
But generally people don't like paying money for open source, so it's hard to raise funds.
If it takes longer, no more money will be requested, that's my risk.


Login failed for user 'sa'

Hi,
Sorry to open another issue of this type but I couldn't find a resolution in the previous issues. I use the following statement to run mssql in my container:
docker run -d --name sql_server_thib -e 'ACCEPT_EULA=Y' -e MSSQL_SA_PASSWORD=‘Xx12Xxxxx12’ -p 1433:1433 microsoft/mssql-server-linux
My password has capitale letter, small letter, digits and is 11 character long therefore conforms to the recommendations. I get the mssql running fine in my container but am unable to connect using:
mssql -u sa -p Xx12Xxxxx12
I got the error (from container logs):
2018-05-07 22:48:05.11 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <IP_ADDRESS>]
I tried to solve the issue for hours yesterday, tried many different password, simple/double quote around it but nothing works. How could I make sure I start with a clean slate for the sa password ? I think the first run string I used wasn't correct and the very first password set considered more characters than expected so I can't determine this password anymore. Removing /var/opt/mssql folder inside my container didn't solve either.
Thanks in advance.
Regards,
Thibault

Are you using a -v volume mount?

Try this instead:
mssql -s <IP_ADDRESS> -u sa -p Xx12Xxxxx12

Same result using this.. The only reason I can see is that the password is not updated upon stopping container -> deleting container -> docker run. I looked extensively for ways to change this password (but you need the current one to do so) or reset it but through docker and command line I didn't find any answer..

I have this sneaking suspicion it's the mssql client that you are using.  Maybe try using sqlcmd or mssql-cli?
https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools?view=sql-server-linux-2017#macos
https://github.com/dbcli/mssql-cli/blob/master/doc/installation/macos.md#macos-installation
I recommend mssql-cli.

@ThibaultGrg if you end up using sqlcmd, the connection string needs to have the tcp in it, like so:
(See here to learn more about forcing protocol types)
$ sqlcmd -S tcp:<IP_ADDRESS> ..

My container was started as:
$ docker run -d -p 1433:1433 -e sa_password=HelloWorld10 -e ACCEPT_EULA=Y microsoft/mssql-server-windows-express:2017

Hope that helps.

Finally works! Weirdly enough it was the quote around my password in the docker run command that were causing the password to be considered wrongly. I had tried simple and double quote and it never worked but removing them completely solves the issue. Thanks for the help!

For me, I only put my password after -e:
-e 'mystrongpwd'
completely missing the SA_PASSWORD! This fixed it (with a valid pwd)
-e 'SA_PASSWORD=mystrongpwd'
PEBKAC

I have this same issue after successfully connecting yesterday.  After connecting, I deleted the container.  Then I created a new instance using the same command/password.  Now it is saying login failed for 'sa', 'Password did not match for login provided'.

Are you using a -v volume mount?

What if yes? I used it
docker run -e ACCEPT_EULA=Y
    -e MSSQL_SA_PASSWORD=****
    --name mssql
    -p 1433:1433
    -v /c/Users/serhi/mssql/data:/var/opt/mssql/data
    -v /c/Users/serhi/mssql/log:/var/opt/mssql/log
    -v /c/Users/serhi/mssql/secret:/var/opt/mssql/secrets
    -d mcr.microsoft.com/mssql/server:2017-latest

Cannot connect Azure Data Studio. I am in a Docker run on Windows, container started from WSL.

Worth a mention, but make sure that if you have an instance of SQL Server installed on the host, that you have it (and all related sql services) stopped.  This caused login issues for me and took far to long to figure out.
In my case the services had been stopped previously when the image was built, but was set to auto start so the next time I rebooted my host, I could no longer log into the docker SQL database.  I could shell into the container and sqlcmd login just fine and other docker containers could log into sql, just not from the host.

 I couldn't resolve this for a week! then I opened SQL Server Configuration, stopped the service and IT WORKS... Sorry for the uppercase but I'm just so happy right now. Thank you!

Yep, 2 solid days of banging my head against the wall.
never crossed my mind to stop the service.
THANK YOU !!!!

Are you using a -v volume mount?

What if yes? I used it
docker run -e ACCEPT_EULA=Y
    -e MSSQL_SA_PASSWORD=****
    --name mssql
    -p 1433:1433
    -v /c/Users/serhi/mssql/data:/var/opt/mssql/data
    -v /c/Users/serhi/mssql/log:/var/opt/mssql/log
    -v /c/Users/serhi/mssql/secret:/var/opt/mssql/secrets
    -d mcr.microsoft.com/mssql/server:2017-latest

Cannot connect Azure Data Studio. I am in a Docker run on Windows, container started from WSL.
And I can confirm that I can connect without mounts

If you used bind mount volume to persist your data you could also persisted your SA_PASSWORD. If you would then create a new mssql container using the same bind mount and the different new SA_PASSWORD, the new password could be overriten by the old stored on disk. This could cause some unexpected login error.

Good call abramadams.  I changed the externally exposed port to 14330 and now both Docker SQL container and locally installed SQL Server run together.
ExposedPorts = new Dictionary<string, EmptyStruct> { { "1433", default },  },
HostConfig = new HostConfig
{
PortBindings = new Dictionary<string, IList>
{
{"1433", new List{new PortBinding{HostPort = "14330"}}}
}
},

-e MSSQL_SA_PASSWORD=‘Xx12Xxxxx12’
Likely the quotes are part of the password... for vars, quote the whole string including the left side of the assignment.
-e "MSSQL_SA_PASSWORD=Xx12Xxxxx12"

Thank you @abramadams ! worked like a charm after a good amount of time troubleshooting before finding this issue.
In my case, I didn't want to restart the host after disabling host instances of SQL server, so I modified the port mapping for docker run with -p 1435:1433 per Docker Docs:
docker run -d -e ACCEPT_EULA=Y -e MSSQL_SA_PASSWORD=12345678 -p 1435:1433 --name myDB mcr.microsoft.com/mssql/server:2019-latest

Are you using a -v volume mount?

Yes, I am
docker run -it --rm --name sql_container --hostname sql_container -e "ACCEPT_EULA=Y" -e "MSSQL_SA_PASSWORD=Str0ngPa$$w0rd" -v mysql:/var/lib/mysql -d -p 1433:1433 mcr.microsoft.com/mssql/server

On trying to connect to the container through Azure data studio using the following credentials:

I am getting the following error:

Finally works! Weirdly enough it was the quote around my password in the docker run command that were causing the password to be considered wrongly. I had tried simple and double quote and it never worked but removing them completely solves the issue. Thanks for the help!

THANK YOU VERY MUCH!!! Today I was completing 3 days trying to find why I couldn't connect!!!
DO NOT PASS QUOTES!!

Are you using a -v volume mount?

What if yes? I used it
docker run -e ACCEPT_EULA=Y
    -e MSSQL_SA_PASSWORD=****
    --name mssql
    -p 1433:1433
    -v /c/Users/serhi/mssql/data:/var/opt/mssql/data
    -v /c/Users/serhi/mssql/log:/var/opt/mssql/log
    -v /c/Users/serhi/mssql/secret:/var/opt/mssql/secrets
    -d mcr.microsoft.com/mssql/server:2017-latest

Cannot connect Azure Data Studio. I am in a Docker run on Windows, container started from WSL.
And I can confirm that I can connect without mounts

If you used bind mount volume to persist your data you could also persisted your SA_PASSWORD. If you would then create a new mssql container using the same bind mount and the different new SA_PASSWORD, the new password could be overriten by the old stored on disk. This could cause some unexpected login error.

This helped me. Turns out during testing the wrong sa password was persisted. I deleted my volumes and then it worked!

You can look at the link below
https://stackoverflow.com/questions/52052494/login-fails-for-sa-sql-server-linux-docker/75245069#75245069


[Bug]: RHEL8 yum/dnf repo: Bad GPG signature

Describe the bug
Repository metadata for https://artifacts.opensearch.org/releases/bundle/opensearch-dashboards/2.x/yum currently has an apparently invalid GPG signature, as far as DNF on RHEL8 is concerned.
To reproduce

Set up the yum repo
Import the gpg key with rpm --import
Attempt to utilize the repository

Expected behavior
Normal function
Screenshots
No response
Host / Environment

Red Hat Enterprise Linux release 8.7 (Ootpa)
x86_64

Additional context
The repomd.xml i know to find (https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/yum/repodata/repomd.xml) appears to have a good signature from the appropriate key? I have no idea what's wrong, unless there's a different repo metadata file DNF is complaining about (i wish it would give URLs when complaining, lol)
draeath@ginnungagap:~> wget https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/yum/repodata/repomd.xml https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/yum/repodata/repomd.xml.asc https://artifacts.opensearch.org/publickeys/opensearch.pgp
# output snipped

draeath@ginnungagap:~> file opensearch.pgp repomd.xml repomd.xml.asc
opensearch.pgp: PGP public key block Public-Key (old)
repomd.xml:     XML 1.0 document, ASCII text
repomd.xml.asc: PGP signature Signature (old)

draeath@ginnungagap:~> gpg --import ./opensearch.pgp
# output snipped

draeath@ginnungagap:~> gpg --verify repomd.xml.asc
gpg: assuming signed data in 'repomd.xml'
gpg: Signature made Mon 01 May 2023 03:57:43 PM EDT
gpg:                using RSA key C2EE2AF6542C03B4
gpg: Good signature from "OpenSearch project<EMAIL_ADDRESS>[unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: C5B7 4989 65EF D1C2 924B  A9D5 39D3 1987 9310 D3FC
    Subkey fingerprint: 2187 3199 B103 0FCD 49DA  83F8 C2EE 2AF6 542C 03B4

draeath@ginnungagap:~> cat opensearch.pgp | gpg --with-colons --import-options show-only --import
pub:-:4096:1:39D319879310D3FC:1620766954:::f:::scSC::::::23::0:
fpr:::::::::C5B7498965EFD1C2924BA9D539D319879310D3FC:
uid:-::::1620766954::09D151299DD6D3D114D0A3558C1AB8329B4AE259::OpenSearch project <opensearch@amazon.com>::::::::::0:
sub:-:2048:1:C2EE2AF6542C03B4:1620767456:1715546574:::::s::::::23:
fpr:::::::::21873199B1030FCD49DA83F8C2EE2AF6542C03B4:

Relevant log output
[root@REDACTED ~]# dnf --verbose --disablerepo=* --enablerepo=opensearch-2.x makecache
Loaded plugins: builddep, changelog, config-manager, copr, debug, debuginfo-install, diff, download, generate_completion_cache, groups-manager, kpatch, needs-restarting, playground, product-id, repoclosure, repodiff, repograph, repomanage, reposync, subscription-manager, uploadprofile
Updating Subscription Management repositories.
DNF version: 4.7.0
cachedir: /var/cache/dnf
Making cache files for all metadata files.
opensearch-2.x: has expired and will be refreshed.
repo: downloading from remote: opensearch-2.x
OpenSearch 2.x                                                  1.2 kB/s | 498  B     00:00
OpenSearch 2.x                                                  122 kB/s | 4.2 kB     00:00
repo opensearch-2.x: 0x39D319879310D3FC already imported
OpenSearch 2.x                                                  5.6 kB/s | 498  B     00:00
Error: Failed to download metadata for repo 'opensearch-2.x': repomd.xml GPG signature verification error: Bad GPG signature

My local repo config, should it matter or be incorrect:
[opensearch-2.x]
name=OpenSearch 2.x
baseurl=https://artifacts.opensearch.org/releases/bundle/opensearch/2.x/yum
enabled=1
repo_gpgcheck=1
gpgcheck=1
gpgkey=https://artifacts.opensearch.org/publickeys/opensearch.pgp
type=rpm-md

This was working as-of at least a few weeks ago. The host currently has opensearch-2.7.0-1.x86_64 installed, if that helps narrow down when the repo broke.

Oh, and we are not using FIPS mode (and can't, it breaks things on us)
[root@REDACTED ~]# fips-mode-setup --check
Installation of FIPS modules is not completed.
FIPS mode is disabled.

Hi @draeath not sure why it is invalid?
It is showing as a good signature.
gpg: Good signature from "OpenSearch project<EMAIL_ADDRESS>[unknown]

# dnf --verbose --disablerepo=* --enablerepo=opensearch-2.x makecache
DNF version: 4.7.0
cachedir: /var/cache/dnf
Unknown configuration option: autorefresh = 1 in /etc/yum.repos.d/opensearch-2.x.repo
Making cache files for all metadata files.
opensearch-2.x: has expired and will be refreshed.
OpenSearch 2.x                                                                                4.3 kB/s | 498  B     00:00
reviving: 'opensearch-2.x' can be revived - repomd matches.
opensearch-2.x: using metadata from Mon 01 May 2023 07:57:06 PM UTC.
User-Agent: constructed: 'libdnf (CentOS Linux 8; generic; Linux.x86_64)'
Metadata cache created.

CentOS Linux release 8.5.2111
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:8"
HOME_URL="https://centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-8"
CENTOS_MANTISBT_PROJECT_VERSION="8"
CentOS Linux release 8.5.2111
CentOS Linux release 8.5.2111

Can you do these things to clean your repo key and rpm key before trying again?
sudo yum clean all
sudo rm -rf /var/cache/dnf/*
rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}\n'
rpm -e <keyid of opensearch>
sudo yum repolist

Then run your yum or dnf to install or cache to local

Thanks.

It's working now. Either that fixed it, or it was a transient issue?


Releasing the Yelp Dataset

Amazing work! We are interested in building on this work. Are there any plans for releasing the long-form sentiment reversal Yelp datatset in this work? Thanks!

Done!

Thanks Madaan! This is super helpful. Would you also be able to share the evaluation dataset for Acronym Generation? We are running some preliminary experiments, and are looking for a task that's shorter and faster to iterate over.

Done here!


Allow localhost services on dev environment to be seen by containers

E.g. In docker compose, which I believe nhost uses indirectly, the following is needed
extra_hosts:
      - "host.docker.internal:host-gateway"

Use-case, I have some non-dockerized services as part of my stack. I want hasura to be able to target them and test remote schemas locally before I proceed to production

host.docker.internal should be already available in your containers to resolve to the host machine. See https://docs.docker.com/desktop/networking/#i-want-to-connect-from-a-container-to-a-service-on-the-host

@dnk8n do you use Linux? Apparently host.docker.internal seems to be not available on Linux, I didn't know that. I'll make sure it's added in the next release

Yes, I use Linux. That might be the issue. I was sure I didn't have access
but will check again as soon as I can
On Tue, 3 Jan 2023, 19:03 Siarhei Lipchyk, @.***> wrote:

@dnk8n https://github.com/dnk8n do you use Linux? Apparently
host.docker.internal seems to be not available on Linux, I didn't know
that. I'll make sure it's added in the next release
—
Reply to this email directly, view it on GitHub
https://github.com/nhost/cli/issues/501#issuecomment-1370008727, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAZHR2PTVYUFKAUTIHPYJJTWQRLURANCNFSM6AAAAAATDJW6QY
.
You are receiving this because you were mentioned.Message ID:
@.***>

@dnk8n please check the latest CLI release and let me know if the issue is fixed for you.

I upgraded to Nhost CLI v0.8.21 for linux-amd64 and it works!
E.g. of an environment variable I have in my .env.development file:
SENDFORM_URL=http://host.docker.internal:8000/api/sendform

@dnk8n awesome! Closing the issue.


Keyboard does not work

TTGO VGA 1.4, Keyboard and mouse installed. Keyboard does not work. Greetings Axel

It is explained in the documentation that this test version does not use the PS/2 keyboard, but a remote UART keyboard, i.e. from the VStudio debug console or COMx telnet (putty):
https://www.putty.org

Ok, so you must connect the USB Device to the Computer and then you can use Putty. Thank you for the information. Greetings Axel


update tools doc to include select VSCode extensions

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/media/node-azure-tools/icon-azure-app-service.png
:white_check_mark:Succeeded

docs-ref-conceptual/media/node-azure-tools/icon-azure-functions.png
:white_check_mark:Succeeded

docs-ref-conceptual/media/node-azure-tools/icon-cosmos-db.png
:white_check_mark:Succeeded

docs-ref-conceptual/media/node-azure-tools/icon-docker.png
:white_check_mark:Succeeded

docs-ref-conceptual/node-azure-tools.md
:white_check_mark:Succeeded

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

#sign-off


Dividing up io.digdag.core package

This is one step to implement remote agent.
Remote agent can't access backend database directly. Instead, they access backend through REST API. To guarantee it, remote agent code shouldn't depend on backend interfaces (e.g. shouldn't use ProjectStore interface).
io.digdag.core package includes many packages that depend on each other. It is making hard to guarantee isolation of agent code. Idea here is to divide io.digdag.core package into backend-only stateful packages ("backend") and shared stateless packages ("core").
Project dependency:
core
     <- backend
     <- agent
                <- server
                          <- cli

(server depends on agent because server has local agent).
Plan:

io.digdag.backend

schedule
workflow
session
repository rename to project
database
Resource{NotFound,Conflict,LimitExceeded}Exception (moved from repository)

io.digdag.core

(most of packages of io.digdag.core: archive, config, crypto, notification, plugin, storage)
ModelValidator (moved from repository)

io.digdag.agent

log

io.digdag.server

rs
local (LocalAgentManager, InProcessTaskServerApi, InProcessTaskCallbackApi, etc.)

io.digdag.cli

client

Close the old issue. Please reopen or file new one if you need.


docs: add a simple playwright example, fix bad imports

fwiw I wasn't able to get waitForResponse working for me and it's not clear from the docs why you need it in the evaluate block.
The default evaluate function does not use it.

Thank you!


Develop -> Main

Codecov Report

Merging #49 (85d0222) into main (1edba43) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #49   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines            4         4
=========================================
  Hits             4         4

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 1edba43...85d0222. Read the comment docs.


Set the non-"none" display value for tables in certain redirects, like fadeIn/Out

It seems like getDisplayType() was defaulting HTML tables to be assigned "display:block;" after a fadeIn. I found that we were getting some weird display issues because of this. I think it makes sense to default to "display:table;" instead.
Is there any reason not to?

 I am super sorry about this. This will be making it into tomorrow's release, however, and I'll be giving you a  mention in the comments.


[tool_crash] ProcessException: The system cannot find the file specified. Command: E:\flutter\bin\cache\dart-sdk\bin\pub.bat, OS error code: 2

Command
flutter create meriPehliApp

Steps to Reproduce

...
...
...

Logs
ProcessException: The system cannot find the file specified.
Command: E:\flutter\bin\cache\dart-sdk\bin\pub.bat, OS error code: 2

[✓] Flutter (Channel stable, 1.22.0, on Microsoft Windows [Version 10.0.18362.1082], locale en-US)
    • Flutter version 1.22.0 at E:\flutter
    • Framework revision d408d302e2 (7 days ago), 2020-09-29 11:49:17 -0700
    • Engine revision 5babba6c4d
    • Dart version 2.10.0

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\hp\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/windows#android-setup for more details.

[✓] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[!] Connected device
    ! No devices available

! Doctor found issues in 2 categories.

Flutter Application Metadata
No pubspec in working directory.

@nihalsarwar17 does the file E:\flutter\bin\cache\dart-sdk\bin\pub.bat exist in your flutter checkout?

Also could you please include the full stack trace?

let me see

E:\flutter\bin\cache\dart-sdk\bin\pub.bat

it does exist but not working.unnu

@nihalsarwar17 does the file E:\flutter\bin\cache\dart-sdk\bin\pub.bat exist in your flutter checkout?

It does exist but not working.

Also could you please include the full stack trace?

Will soon..

What happens if you type E:\flutter\bin\cache\dart-sdk\bin\pub.bat in the command line? Does the program run or does it complain about a file not found?

Without a response we're unable to make any progress. I'm closing the issue, but don't hesitate to file a new one if you have the time.


Add an event that is emitted when a new FireFly transaction begins on the local node

See https://discord.com/channels/905194001349627914/935885156391223336/935943327721852938

Add a new event type that is local_transaction_submission (or similar) that is emitted on a node, when it instigates a new transaction, but you only get that event on your local node
Allows the UI to have a left-column of the events/activity view showing only those (rather than trying to reverse engineer which events are "ours")

When implementing this, I think it's worthwhile to add the batch optimization fields to the Database layer for transactions, as that piece of work fits well with needing to evaluate each codepath that creates a transaction to determine if it should emit this event.

@awrichar - feels like there's an overall documentation exercise that this fits into, where we describe the overall transaction/event model more helpfully to users. I wonder if the artefacts created for that should be rolled up into a FIR?

I would propose transaction_submitted, to fit more with the "thing_verbed" structure of other events.

And yes, once we figure out what the Transaction / BlockchainEvent / Event model is, we should definitely write it down 🤪 ongoing discussions on Discord for that.


exploitdb: 2023-06-10 -> 2023-06-14

Diff: https://gitlab.com/exploit-database/exploitdb/-/compare/refs/tags/2023-06-10...2023-06-14
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

1 package built:

exploitdb