Recurse upward looking for .simplecov

The SimpleCov documentation states: "To avoid [duplicated configuration], you
can place a file called .simplecov in your project root." However, SimpleCov did
not actually look in the "project root" for this file, unless specially configured
to know where the project root is. Rather, it would simply look in the working
directory. Working directory != project root. (Unfortunately.)
Therefore, when looking for .simplecov, recurse upwards from the working directory
until it is found (or the root directory is reached). This is comparable to the
way that git recurses upwards looking for a .git directory, meaning that you can
use git anywhere in your project root or below.
Since there is no guarantee that you have permissions to read .simplecov, catch
exceptions and display a warning message if one occurs.

Prior art:

RSpec does not traverse up the directory tree.
Git does.

This behaviour seems ok, but I think I'd want RSpec to be consistent (since they're so often used together).

@xaviershay Note that the testing process for a Ruby project is very unlikely to involve running RSpec multiple times, from different subdirectories. git, on the other hand, is very frequently used from a subdirectory.
This patch was prompted by work being done on Racc. Its test suite runs the ./bin/racc script many times, with various inputs, and checks the output. Naturally, ./bin/racc runs with a different working directory than the Rake process which invokes it.
I think that this usecase is not entirely unique to Racc. Many test suites may run Ruby subprocesses, for one reason or another. Those subprocesses may or may not have the same working directory.

Fixed up the style errors.

Last chance for comment, I'm going to merge this later today otherwise.


on-device testing

it would be cool to be able to run automated tests on a target board using a test runner tool on the host. we could drive the tests over SerMux.
if the tests exercise functionality that can currently be accessed from Forth, this could be as simple as just opening a serial forth shell, sending a script, and making assertions about the output.

It would be really neat to get this working.  We'd need a way for our test-driver box to softwarily reset the device. there's probably some obscure ioctl or something that a linux machine could use to stop powering one of its USB ports?

there's probably some obscure ioctl or something that a linux machine could use to stop powering one of its USB ports?

ah, you can write on or off to /sys/bus/usb/devices/<BUS ADDR>/power/control because Everything Is A File. that's actually really nice!

for completeness' sake, the command sequence seems to be:
# turn off (suspend)
$ echo 0 > power/autosuspend_delay_ms
$ echo auto > power/control

# device should now autosuspend immediately
$ cat power/runtime_status
suspended

# turn back on
$ echo on > power/control

# kernel should now emit messages about resetting, disconnecting and rediscovering the device
# (...)

$ cat power/runtime_status
active

an additional unfortunate snag is that once we boot mnemOS we lose XFEL mode. In other words, for HIL we'd need to add actual power down, "push" XFEL and power up again :(


improve the boolean column's logic to more closely match PHP's boolea…

WHY
The "boolean" column's logic is unintuitive.
BEFORE - What was wrong? What was happening before this PR?
The "boolean" column logic is unintuitive, and isn't very flexible, requiring the use of custom column types (eg. "closure") for otherwise straight-forward use cases.
AFTER - What is happening after this PR?
The "boolean" column logic is more consistent with PHP's typing, so various database column datatypes can be cast to booleans more easily.
HOW
How did you achieve that, in technical terms?
Check for falsy values first.
Is it a breaking change?
Yes.
How can we test the before & after?
Before: Truthy values like 123, 'asd', etc. are cast to a falsy "No" in the UI, eg. on a list operation page.
After: Truthy values like 123, 'asd', etc. are cast to a truthy "Yes", eg. on a list operation page.
Example:
// assuming we have a model like this:
$entry->deleted_at = '2022-04-18 00:06:02';

// in PHP casting the deleted_at attribute to boolean would return true:
(bool) $entry->deleted_at; // true

// but using Backpack's "boolean" column doesn't function the same way, logically speaking
$this->crud->addColumn([
    'name' => 'deleted_at',
    'label'  => 'Deleted',
    'type'  => 'boolean',
]);

// in the blade template, the deleted_at value is not one of [true, 1, '1'] so it's assumed falsy

You could also make it completely consistent with PHP's code by using (bool) or boolval(...) directly. Is there a reason why you choose not to do so?

That's an option. The whole idea is to take what's in the database and cast it to a boolean. If your "boolean" column was strings of either true/false, what would you expect to 'false' to evaluate to, true or false?
This is sort of an aside, but if you look at the old code '1' is explicitly treated as true. I guess it's in case Eloquent doesn't cast a database's string '1' to an integer 1, but most "bool" database columns are tinyint's or a similar integer type, so I don't get why this would check for a string '1' but not other common boolean strings, like 'true' or 'TRUE'. Casting '1' to a bool is no different than any other string in my mind. If someone is storing their 0/1 flags in string columns, that's just as non-standard as string true/false or on/off, yes/no in the DB. TL;DR: there's no reason to account for string '1'. /tangent
I really don't care though about the details though. I'm mostly trying to account for a very common use-case: soft-delete columns when cast to boolean should return true for non-null values. This is logically how soft delete scopes work in Laravel.
If the consensus is that the new logic should simply use boolval() that's fine with me, but I think it's less intuitive, even if it's not perfectly aligned with PHP's logic.
I think we can all agree that the old code is the least intuitive of our options though.

Ugh... this one seems to have slipped through the cracks, thanks @joelmellon .
I agree there's an inconsistency here that we need to fix. It's not ok to evaluate '1' to true and 'true' to false - didn't even know this was happening. Your use case with deleted_at being casted to boolean also makes perfect sense to me.
I've scheduled to take a closer look at this next month (5.2), and figure out a solution if we cannot merge this as-is. The difficult part will be making this a non-breaking change (if possible at all).
Thanks again!


pixi global install does not correctly install binaries for package binaries with "." in the name, notably python

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
$ cargo run -- global install python==3.11
    Finished dev [unoptimized + debuginfo] target(s) in 0.10s
     Running `target/debug/pixi global install python==3.11`
✔ Installed package python 3.11.0 he550d4f_1_cpython from conda-forge
  These apps are now globally available:
   -  2to3
   -  2to3-3
   -  idle3
   -  idle3
   -  pydoc
   -  pydoc3
   -  pydoc3
   -  python
   -  python3
   -  python3-config
   -  python3
   -  python3
   -  python3

(note that many of these names have multiple occurrences)
Issue description
When installing binaries, the global installer strips the extension from the filename. However, for packages like python, which include files like python3.11,  python3.11-config, etc., this strips important parts of the name, not the extension, so you end up with a list of installed binaries where there might be multiple python3 entries, e.g. It may be a minor problem for downstream users to be missing python3.11 and only end up with python3, but this is a bigger problem for things like python3.11-config, which gets shortened to python3, such that depending on order, the only installed python3 you get could in fact be python3.11-config!
I think this is happening here:
// install.rs:180
        let file_name = exec
            .file_stem()
            .ok_or_else(|| miette::miette!("could not get filename from {}", exec.display()))?;

Expected behavior
This should perhaps not trim the extensions automatically (except maybe on windows)? Or at least not trim them automatically when that would lead to multiple binaries with the same name?

We're going to have a look at it, good find!


NPE when doing coverage collection in WGS

This looks like an issue in the code of SparkGenomeReadCounts
Got it when testing on large HCC1143T bam file on both cluster and standalone modes.
Failing at:  final int newEnd = Math.min(newStart + binsize - 1, sequenceDictionary.getSequence(contig).getSequenceLength());
My money is that sometimes the sequence of the contig returns null and we are not checking for that.
16/01/22 22:42:20 ERROR Executor: Exception in task 28874.0 in stage 0.0 (TID 28874)
java.lang.NullPointerException
        at org.broadinstitute.hellbender.tools.genome.SparkGenomeReadCounts.createKey(SparkGenomeReadCounts.java:148)
        at org.broadinstitute.hellbender.tools.genome.SparkGenomeReadCounts.lambda$collectReads$bc56242$1(SparkGenomeReadCounts.java:99)
        at org.broadinstitute.hellbender.tools.genome.SparkGenomeReadCounts$$Lambda$167/2095690993.call(Unknown Source)
        at org.apache.spark.api.java.JavaPairRDD$$anonfun$toScalaFunction$1.apply(JavaPairRDD.scala:1027)
        at scala.collection.Iterator$$anon$11.next(Iterator.scala:328)
        at scala.collection.Iterator$$anon$11.next(Iterator.scala:328)
        at scala.collection.Iterator$$anon$11.next(Iterator.scala:328)
        at org.apache.spark.util.collection.ExternalSorter.insertAll(ExternalSorter.scala:205)
        at org.apache.spark.shuffle.sort.SortShuffleWriter.write(SortShuffleWriter.scala:73)
        at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:73)
        at org.apache.spark.scheduler.ShuffleMapTask.runTask(ShuffleMapTask.scala:41)
        at org.apache.spark.scheduler.Task.run(Task.scala:88)
        at org.apache.spark.executor.Executor$TaskRunner.run(Executor.scala:214)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:744)

As an aside, I think the processing is faster when running on a local temp directory (as opposed to a shared filesystem location as the tmpdir).

I have a fix in the spark Jar branch for issue #317


store: Moved to math.MaxInt64 instead of random constant.

Signed-off-by: Bartek Plotka<EMAIL_ADDRESS>

This is clearly not enough to support 32bit systems. We (or any volunteer to fix this) need dive more into this.


Build new workflow and restructure the project

This pull request aims to establish new environment with  TypeScript and Webpack as a step to Angular 2 friendly environment.
Main points:

New workflow with Webpack
TypeScript as a main language
sm-button directive and unit tests for it were successfully migrated to TS as POC (closes #41)
Remade Karma setup
jshint replaced by tslint with sample set of rules
Updated travis.yml to run latest stable nodejs
Updated README.md (closes #47)

The npm build script doesn't appear to output anything. Is that just a placeholder for now or is there a problem with the webpack config?


Look into odd file references

https://gitdetective.io/fasterxml/jackson-core
JsonParser.nextToken() has a lot of file references that don't look correct

Not going to be able to fix this this version. Looks like an issue with Kythe.
Can recreate issues with fasterxml/jackson-core and `fasterxml/jackson-datatype-jsr353'.
Kythe simply shows:
"kythe://kythe?lang=java?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java#696ce813c09c516d7a58261ff7128fe667e41dbfe84052583190263e36c402ae" "/kythe/edge/childof" "kythe://kythe?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java" .
"kythe://kythe?lang=java?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java#696ce813c09c516d7a58261ff7128fe667e41dbfe84052583190263e36c402ae" "/kythe/loc/end" "2007" .
"kythe://kythe?lang=java?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java#696ce813c09c516d7a58261ff7128fe667e41dbfe84052583190263e36c402ae" "/kythe/loc/start" "1994" .
"kythe://kythe?lang=java?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java#696ce813c09c516d7a58261ff7128fe667e41dbfe84052583190263e36c402ae" "/kythe/node/kind" "anchor" .
"kythe://kythe?lang=java?path=src/main/java/com/fasterxml/jackson/datatype/jsr353/JsonValueDeserializer.java#696ce813c09c516d7a58261ff7128fe667e41dbfe84052583190263e36c402ae" "/kythe/edge/ref/call" "kythe://kythe?lang=java?path=%21jar%21/com/fasterxml/jackson/core/JsonParser.class#a4894f2193b1cf056e7eba40105128bc5a9c2ba29dead04217faeea85eb81389" .```

Which just says that `JsonValueDeserializer` calls `JsonParser.nextToken()`. Doesn't show any more information other than the file calls that method. Odd...

verified #45 solves these issues


Old Model Builder is displayed instead of new if extension not uninstalled

System Information (please complete the following information):

Model Builder Version:
Visual Studio Version

Describe the bug
When I installed Visual Studio 2019 16.6 Preview 2 I was very hyped for the new version of ML .NET Model Builder! 😁
Except I got only the old UI... So I ended up using a stable version of Model Builder in VS 16.5 because in the preview version the images were missing.

Figure: The issue persistent to newer preview builds.
Removing the Model Builder extension fixed the problem!
To Reproduce
Steps to reproduce the behavior:

Have Model Builder extension installed prior 16.6 Preview 2
Upgrade to 16.6 Preview 2

Expected behavior
The new and nice looking UI. 😀
Screenshots

Additional context
I got it working now and it would be great if anyone else has the same problem, that this could be resolved somehow. Maybe updating the extension and adding a warning on the old version that they should remove the extension because now it's built-in?

Thanks for the feedback! We're looking into a smooth upgrade path from the old extension to the new built-in VS version.


iterm update changed name of iterm executable from iterm to iterm2

/Applications/iTerm.app/Contents/MacOS/iTerm was renamed to /Applications/iTerm.app/Contents/MacOS/iTerm2 please also check for this one

@Brototype Thanks for your advice, and now iTerm2 is supported.


Staging environment

Is your feature request related to a problem? Please describe.
Staging environment needed for:

General QA testing can be carried out before deploying new releases to master branch
Designers can log into current development version without requiring local environment

Describe the solution you'd like

API in Heroku
Client in Netlify
Environments based on develop branch.

Hey @tristanMatthias commenting here to be added

@shane215 , we will need to think about how this fits into what you're working on in #7

@tristanMatthias Maybe a nightly build of develop branch, for example.

Yes, it will be a build on any merge

Hey @shaneSheridan, you feel like tackling this one? Would be really nice to have a staging env for testing stuff in after a PR merge :)

Ping @shaneSheridan. Would be good to have this for our launch soon 😄

I learned how to deploy a simple NodeJS app to Heroku :)
This was a useful guide:
https://www.freecodecamp.org/news/how-to-deploy-a-nodejs-app-to-heroku-from-github-without-installing-heroku-on-your-machine-433bec770efe/
I'll look into Netlify next.

Learned how to deploy a React app to Netlify.
Guide: https://www.netlify.com/blog/2016/09/29/a-step-by-step-guide-deploying-on-netlify/

I think that the next steps for me are:

Log into CM heroku/netlify accounts
Follow steps to deploy new site with develop branch

Hey @shaneSheridan, glad you got across the tech on this. I just made a couple of fixes and enabled build pipelines so we should be good to go :)
UI: https://develop--learn-codementoring.netlify.app/
API: https://staging-code-mentoring.herokuapp.com/


Error on node-statefulset.yaml when running helm install validator

Error Message: "Error: INSTALLATION FAILED: parse error at (besu-node/templates/node-statefulset.yaml:334): unexpected EOF"
terminal: "helm install validator-1 ./charts/besu-node --namespace besu --values ./values/validator.yml"
how to reproduce:
i followed https://www.zeeve.io/blog/how-to-deploy-a-hyperledger-besu-network-on-kubernetes/ tutorial to deploy private blockchain using quorum-kubernetes.
can anyone also reproduce this error?

me too. same error, i use helm lint but nothing for now.

@heryanto87 Can you please provide steps to reproduce this?

What is your environment?
Are you running local on minikube/equivalent - cloud etc?
What algorithm are you using and what changes if any have you made to the charts?


Run-From-Package creates an invalid deployment

Since yesterday, after every deployment we make to our App Service, the application fails to start. We're using Run-From-Package as deployment method and are seeing the following error in the App Service event log:
Application '/LM/W3SVC/61535351/ROOT' with physical root 'D:\home\site\wwwroot\' failed to start process with commandline 'dotnet .\Alexandria.dll' with multiple retries. Failed to bind to port '7356'. First 30KB characters of captured stdout and stderr logs from multiple retries:
Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'D:\home\site\wwwroot\Alexandria.dll'. An assertion failure has occurred. (Exception from HRESULT: 0x8007029C)
Process Id: 11020.
File Version: 13.0.19218.0. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 4a42afc5aea63750638e118560d43db04bd9ccc2

In this case, Alexandria.dll is our application entry-point. It's an ASP.NET Core 2.2 application.
Or deployment setup consists of the default production and a custom staging slot, with 2 App Service instances running at minimum. We're running theRun-From-Package deployment on the staging slot, with auto swap enabled, so the application can be deployed with zero downtime. This issue is impacting all of our customers after a deployment.
A simple restart of App Service fixes this issue.
After searching around a bit, the issue we're experiencing here seems to be very similar to https://github.com/Azure/app-service-announcements-discussions/issues/32#issuecomment-472037237
Basically two questions are open for me here:

Why is App Service unable to load our .dll?
Why would App Service auto-swap an application that isn't even able to start? That seems completely crazy to me and should be prevented by all kinds of health checks on the side of App Service.

Please let me know what useful information I can provide in addition.

Before we auto swap, we ensure 1) deployment successful 2) app is responsive and return 200 on root path access.   It seems to contradict with your 2nd question.   Best is for us to check the log and confirm.   Do share the UTC time of the most recent deployment (auto-swap) as well as the webapp name (here or indirectly) that left your production in bad stage.   We can investigate.

@suwatch WebApp name is mimo-api-production, happened the first time on Thursday ~15:15 UTC and then again on Friday ~09:45UTC

Thanks for the info .. we are taking a look and will update what we find.

@flagbug  I was wrong on swap would happen if only 200.    Swap will happen regardless of the status by default.   However, recently we made an improvement to allow the app to specify condition (expected statuses) before swapping.   Please checkout WEBSITE_SWAP_WARMUP_PING_STATUSES.

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Device shows for some seconds, then lost completely

Device: Xiaomi Mi 9
OS: Android 10
Version: 2.2.5 F-Droid

So it seems to find a device but it gets lost immediately. If i'm fast enough, i can press on the device and open it but it never gets saved, so i have to search every time.
When searching manually via IP (its available in browser on the smartphone) it seems to not find anything at all.
I add two screenshots and the second one is 4 seconds after the first one.

Is it possible you have hidden the device? Can you check in the top left menu, then "manage device" to see if you see anything?
I'll investigate the bug on my side too!

Its empty. "You don't have any devices yet"

@natrius  do you still have this issue in the latest versions (4.0.0 and above) ?

Add the github-repository and installed 4.1.1 and now the strip show up all the time, even with deactivated WLAN. Thanks for working on it!


Switch to new notation for assignment/equality

Per the results of this poll we should switch to using := for assignment (let-binding) in rules, and = for equality testing.
The following can be used to get a nicely-formatted := in LaTeX
\newcommand{\leteq}{\ensuremath{\mathrel{\mathop:}=}}

This was addressed in the ledger spec, we only need to chain the ledger spec, and the small-steps document.


Add CString16

For now the API is quite minimal; mostly it just makes interop between
regular Rust strings and EFI strings easier. You can convert from a
&str to a CString16, and since it derefs to &CStr16 you can call
the methods exposed by that type as well.
This type is gated by the exts feature since it requires allocation.

Looks good to me! This new utility type might also help the developers using the crate to build UEFI applications.
There's a minor conflict against the master branch, could you perform a rebase?

There's a minor conflict against the master branch, could you perform a rebase?

done


No license

Hello.
What is the project's license? I've seen no license mentioned so just an idea: Apache License 2.0 is a good candidate for a modern permissive license.

Thanks


Create instruments work type and pathway

Fixes #1586

I just noticed this part of the open_api.yml while working in the culminating experiences stuff:
https://github.com/psu-libraries/scholarsphere/blob/70a1606f31a1b08d04f130bfb927e05818754cb3/openapi.yml#L260-L284
We'll want instruments in here too.


Update download URLs for Enterprise InfluxDB 1.9

See https://github.com/influxdata/docs-v2/issues/2357:

Currently we have to bump version numbers on this page (on possibly others): https://docs.influxdata.com/enterprise_influxdb/v1.8/install-and-deploy/production_installation/meta_node_installation/.
Instead we should like to a download portal that provides InfluxDB Enterprise downloads.

Truly fixed in https://github.com/influxdata/docs-v2/pull/2565.


Install ghcup on windows

See https://github.com/actions/virtual-environments/pull/4016 for discussion and reasoning.
This just adds ghcup the binary to the installation. It still uses chocolatey for installation. I leave it open for discussion whether chocolatey or ghcup should be used. However, there have been some reports of chocolatey issues: https://github.com/haskell/actions/issues/70#issuecomment-913100373
I can't comment on the nature of them. I believe chocolatey is quite robust. It lacks a little bit behind in adding new GHC versions, but not significantly.
The main (or maybe only) difference between ghcup and chocolatey is the shimgen wrapper they use for emulating symlinks to ghc.exe:

Chocolatey uses a proprietary shimgen: https://github.com/chocolatey/shimgen#why-is-shimgen-closed-source
ghcup uses an open source shimgen: https://github.com/71/scoop-better-shimexe

Which one of those makes less problems, I don't know.

/azp run windows2016, windows2019, windows2022

Error seems unrelated to my change: https://github.visualstudio.com/virtual-environments/_build/results?buildId=116197&view=logs&j=50448a2f-9550-51a0-b6c4-5ec64224dd81&t=ef62147d-e6d2-576e-9194-9c40d3d74598&l=363

@hasufell thanks for your contribution! The changes will be available next week.


Support i64 emulation in the SPIR-V backend.

More users are hitting issues with the i64->i32 truncation and some actually need the i64 values even when running on 32-bit devices. Unfortunately these i64 types aren't always coming from users but being inserted by things like JAX and pytorch and we can't (easily) make them change. Currently SPIR-V is the last thing requiring this truncation and if we were able to support i64 there we could remove it entirely and never get another issue about it. It doesn't mean i64 has to be fast on 32-bit hardware - just correct - as then if there are performance issues we can redirect that to the frontends :)
Today this test is only passing because we truncate:
https://github.com/google/iree/blob/9240f1c789f7f3ac2d62701ef1c6c9856587c509/iree/test/e2e/vulkan_specific/compare.mlir#L56-L65
Removing the truncation by commenting out this block will cause it to fail to compile:
https://github.com/google/iree/blob/4a93d2569e44f53b19921e47840cf8576f87bf1d/iree/compiler/Dialect/Flow/Transforms/TypeConverter.cpp#L37-L44
->
iree/test/e2e/vulkan_specific/compare.mlir:62:13: error: failed to legalize operation 'memref.load'
  %result = "mhlo.compare"(%lhs, %rhs) {comparison_direction = #mhlo<"comparison_direction EQ">} : (tensor<i64>, tensor<i64>) -> tensor<i1>

Seems to call for a pass that takes IR using i64 and expands loads/stores/arith to emulate i32. That'd be useful for other platforms too and likely something that we can just do on standard dialects (arith/memref/etc) - shouldn't be too bad, just a bunch of 1990's bit twiddling: https://gist.github.com/csaftoiu/9194ef9ffd98b7b106b359ca55557010
CUDA unconditionally supports i64 and we already get this for free on the CPU path because LLVM does it for us, but if we did it in MLIR we could do it early in backend translation and have tile/distribute/vectorize/etc chew on everything really nicely vs doing it at the SPIR-V level.
As a workaround that would allow us to remove the truncation by default we can run the current truncation pass by flag only if targeting Vulkan and using i64 tensors, though that's a big divergence and bound to cause hard to debug issues.
Note that this is just i64 - f64 is fine to push back onto frontends.
Part of #8661.

Android i64 support is nearly non-existent (just some Tegra-like things, probably) and interestingly pre-M1 macOS never supported it (but all recent iOS and M1 macs do).


Tried to register two views with the same name RCTCamera

Device: Android 7.0
react-native: 0.50.3
react-native-camera: 0.12.0

I met the same problem. In my case, there is another library that declares react-native-camera as dependency. I fixed it by deleting the node_modules/react-native-camera folder inside that library.

is this an issue?

i meet the same problem,
"react": "16.3.1",
"react-native": "0.55.4",
"react-native-camera": "^1.1.2",

how can i fix this issue

@krizpoon my hero. I found a few instances of the package in question (in my case react-native-svg) installed in other dependencies. Removing those solved the problem. I'd imaging that version mismatches between them contribute to the issue, as I was attempting to change the version number..

RCTCamera is removed https://github.com/react-native-community/react-native-camera/issues/1890
Migrate to latest version of RNCamera


For action combos, minimize # txs by leveraging helper contract methods

Summary
We have some potentially low-hanging fruit to minimize # txs when doing (a) create_asset + post for free/priced, (b) download file, (c) maybe more. Via helper smart contract methods.
This issue is about doing that. But note that we have other things to do first. (See Priorities section.)
Motivation
Alex:  (in slack)
I would have expected this [create exchange] in ocean_assets.create, since we have a lot of helpers in the contracts factory to reduce no of tx
Trent:
I agree to the value of that. We need to walk before we run.
The first priority has been to ensure that atomic actions -- atomic from perspective of user -- are clean.
And some of these naturally bundle. Examples:

download_file() - does (1) do the order (2) do the download
create() - could do (1) create data nft (2) create datatoken (3) create ddo (4) deploy a dispenser or fixed-price. Right now it does (1)(2)(3) but we could extend to (4) too.

With those natural bundles, we can then optimize the # txs by leveraging the special smart contracts calls. (And for cases we don't have that, use Gnosis Transaction Builder.)
But it's one step at a time.
TODOs

[ ] Do bundle: ocean_assets::create() lets the user optionally set a pricing scheme (free or fixed-price) with associated parameters. Minimize # txs doing this
[ ] Do bundle: in download_file(), minimize # txs when doing this. Must work for all combos of {free, priced} x {template 1, template 2}
[ ] Identify other existing helper contract methods to identify opportunities. Add to this issue's TODOs to leverage them
[ ] Look at flows in ocean.py and predict-eth READMEs, to find any other natural bundles. Identify them here, and add to this issue's TODOs to leverage them. If we don't have existing helper contract method for a highly-used bundle, add "try out Gnosis Transaction Builder" to the TODOs
[ ] By the time we're here, we've added several TODOs. Prioritize them, and execute on them. For larger issues (eg Gnosis), perhaps create a new issue, then treat this issue like an epic.

On Priority
Priority of this issue: only do after we've fixed bugs (there are currently >5 that really matter), and done other UX cleanups.
Recently-completed UX cleanups:

#977 use brownie
#910 Streamline dispenser.py & dispenser-flow README
#1094 Improve ocean_assets::create() interface & implementation

Other UX cleanups, that are higher priority than this, include:

#1194 Streamline fixed-rate-exchange & marketplace README #1149
#1095 Streamline main README flows; harmonize main local <> remote versions
#1165  It's hard for py devs to see contract methods of DataNFT, Datatoken, etc

There is a case to be made here regardint DispenserArguments and ExchangeArguments. When we are creating objects and their pricing schemas at once, we are in fact mirroring what we do in dt.create_exchange and dt.create_dispenser, with the same defaults. We could implement DispenserArguments and ExchangeArguments in the same way we implement DataNFTArguments, DatatokenArguments etc., for a seamless way of setting these defaults.
In addition, this would improve the architecture on _create_1dt. My goal is to transform what we now have as _create_1dt to accept an optional parameter for the pricing schema. Instead of creating two functions called create_1dt_with_dispenser and create_1dt_with_fixed_rate, we could pass in an argument e.g. pricing_schema_params: Optional[DispenserArguments, ExchangeArguments] = None and call the appropriate tx combo based on the instance of the pricing schema arguments. This simplification would also bubble up nicely to create_url_asset and its siblings.

Data Nft Arguments and Datatoken arguments certainly helped in good defaults for lower level logic. But right now they are still a bit painful to use at the higher level: to create a simple data nft I have
Before we go to "improve" more arguments with more data structures,

DataNFTArguments and DatatokenArguments certainly helped wrt good defaults for lower level logic.
But right now they are still a bit painful to use at the higher level: to create a simple data nft, I have to:

import DataNFTArguments
instantiate DataNFTArguments
call nft factory "create".

It's not super-painful, though, because at the higher level, people use ocean_assets.py. At some point, we can have to data nft factory "create" calls that use either DataNFTArguments OR simple good defaults to construct DataNFTArguments.
--
Given the above for data nfts and datatokens, I do not want to create more complicated interface for exchange and dispenser. If you want to create arguments objects for them, fine, but preserve the existing interface so that users do not have to import and instantiate separate "arguments" classes.

Wrt priority of this issue: I see several other issues with higher priority. It would be good to do those first. These include:

fix breaking tests, so that we can do CI of PRs in confidence
get #1260 merged. When I ran its PR tests last week, several failed due to the bullet above
do pybundlr#7. So that people in a python flow can upload files locally into arweave permanent storage, without npm issues

There are more too. But the ones above are low hanging fruit.

@trentmc

CIs are done and can work now with them.
This issue was prioritised during one of the sprint plannings and the asset creation part is almost done.

I've added the arguments objects and I believe them to be very useful in the combo architecture. If you can review that PR, let me know if I should keep the former interface inside create_datatoken and create_exchange. I'm fine with reverting the changes I did for those interfaces. However, I think in combos it is an excellent choice and it fits the architecture and usability nicely.

I assume the PR regarding exchange and dispenser args is this one:
https://github.com/oceanprotocol/ocean.py/pull/1297/files
The interface is much harder to use than before. It's asking the user to import another class, and construct another object.

let me know if I should keep the former interface inside create_datatoken and create_exchange.

Yes. Definitely.
And, like I suggested for DataNFTArguments class in the comment above, maybe we can have both:

an easier interface, where the caller doesn't have to do the additional import and class instantiation. But, optionally, they can.
and under the hood it always uses an "arguments" class

This pattern can be used in four places, to create:

data nft
datatoken
dispenser
exchange

In essence, our issue is with the instantiation. I'll try to think of something smarter to "cover up" that instantiation. I think it's possible, but I need to think about it a bit.

OK, I have options :)
A) Using args/kwargs magic (tested)
Only for interfaces that take in ONE argument, not a combination, i.e. create_datatoken, create_dispenser, if we have the tx_dict first, we can do some magic with the arguments. I can use the *args and **kwargs magic to build the Arguments class automatically (where the arg/kwarg itself is of course NOT already an Argument class).
pros: beautiful, magical and elegant, will be compatible with the previous args and keyword args without instantiating an Argument class in the readmes
cons: I can not implement it for functions that take in multiple argument types, i.e. combos like create NFT + ERC20. There, the user will have to define the Argument objects separately
Mapping argument groups to argument objects (not tested yet)
I can derive argument groups in the following ways:

either the user separates them in tuples (no need for the import, at least. We can build the Argument class based on the tuples, but under the hood)
some convention like prefixing (i.e. data_nft_symbol kwarg to be sent to DataNFTArgument object, datatoken_symbol to DatatokenArgument object)

pros: it would encompass the case for multiple argument groups given to the same function
cons: clunky and really weird to use in either case, I don't think dropping some imports is worth it. It also breaks the interfaces in a uglier way and I personally don't like it.

Option C

Don't change dispenser and exchange creation. That is, preserve status quo. (One only has four parameters, the other only has two. So extra arguments class for each just to pass this around is pretty heavy, relatively speaking.)
Don't bother creating better interfaces to create data nft and datatoken. That is, preserve status quo. Since we already have interfaces in ocean_assets.py.

My analysis: options A and B add a lot of complexity. Option C doesn't add complexity, and already has good interfaces for users.
My choice is option C.
I lean to option

@trentmc Keeping C then. I've already started on reverting the interface changes and I'll let you know when you can re-review the changes.
In the meantime, here is my experimental commit for option A (just dataNFT changes as a PoC):
https://github.com/oceanprotocol/ocean.py/commit/5c943e91273cb99cd19630300db1dc8b25db1634
If you think we can circle back to this later, I'd be happy to implement this type of solution to make the interface more flexible. I agree it introduces some complexity, but I believe it's reasonable and clean.

If you think we can circle back to this later, I'd be happy to implement this type of solution to make the interface more flexible. I agree it introduces some complexity, but I believe it's reasonable and clean.

(I finally got a chance to sit at my desktop to look at this.)
I just took a look.
It's surprisingly clean; cleaner than I expected possible. Great stuff!!!
Therefore I'm fine if you merge the PR (once past protoype phase). And I'm fine if you propagate that pattern to the other three places. (This includes changes to "exchange" and "dispenser".) Sorry if this felt like a flip-flop; at the end we all want a good interface with low-complexity code.


To upload json file validation does't work

Laravel Version: 5.4.36
PHP Version:>=5.6.4
Database Driver & Version:

Description:
I want to validate json file with it extension only but doesn't work
these are codes i tried
` $this->validate($request, [
            'dataset_type' => 'required|file|mimetypes:application/json'
        ]);`

other way i tried
 $file = $request->file('dataset_type'); //i need this later to upload the file             $rules= [                 'dataset_type' => 'mimetypes:application/json'             ];             $x = $request->all();             $validator=Validator::make($x, $rules);             if ($validator->passes()){                 dd("Passes");             }else{                 dd("fails");             }
it doesn't work ⬆
this one works but it validate with  txt file but I need json formatt only ⬇
$this->validate($request, [                'dataset_type' => 'required|mimes:json,txt'             ]);
How could i resolve this issue ?
Thanks
Steps To Reproduce:

Laravel 5.4 is no longer supported. Also this repo is for bug fixes. If you need help, you can consult the forums or the slack channel

thank you @Dylan-DPC  could you  give slack url channel?

https://larachat.co/

Thank you


Add example directory

This repo should have an example directory so the repo's features can be tested within the repository.
Use microsoft/react-native-test-app to create an example directory to test masked view

@Naturalclar are you working on this? Otherwise, I can take a look at it

@LRNZ09 It'll be great if you can take at look at it :+1:

EDIT: one problem I see with using microsoft/react-native-test-app is that it doesn't support the Web platform yet, see https://github.com/microsoft/react-native-test-app/issues/812, maybe Expo could be a more straightforward option.

Unfortunately, expo wouldn't be suitable for an example app for a native module library as expo doesn't support adding native modules that are not supported by the framework.
I'm aware that masked-view is one of the libraries that are supported by expo but I'd like to keep the library flexible

Closed via #176


Can generated Model classes be serialisable?

It would be really helpful if there was a way to make the generated model classes serialisable (supported by Kotlinx). Or am I missing something here?
I have a KMP project with lots of serialisation/deserialisation happening while passing data across different interfaces.

we won't make the generated code serializable since that'd be a prescriptive dependency, but you can use your own models for queries by passing a mapper parameter, or implement custom serializers for sqldelight generated types.
On Cash we generally avoid putting db models anywhere where they need to be serialized, and instead pass the primary key, and then the consumer would query the database for the data it needs. If that works for you it'd be what I recommend

For folks stumbling across this now, I'm using this experimental feature of kotlinx.serialization with some success: https://github.com/Kotlin/kotlinx.serialization/blob/master/docs/serializers.md#deriving-external-serializer-for-another-kotlin-class-experimental
Requires a pretty direct 1:1 mapping of table schema to endpoint responses which is not ideal, but is pretty handy for quick projects

You can create a @Serializable mapper for your queries:
// add a new @Serializable object
@Serializable
class Vehicle(val vin: String, val serialNumber: String)

// create the mapper function for it
val vehicleMapper: ((vin: String, serial_number: String) -> Vehicle) =
    { vin, serial_number -> Vehicle(vin, serial_number) }

// query the database with this mapper
// This is already a @Serializable object
val dbVehicle = database.vehicleQueries.getVehicle(vin, vehicleMapper).executeAsOneOrNull()

Database query
getVehicle:
SELECT vin, serial_number FROM vehicle WHERE vin = ?;

For folks stumbling across this now, I'm using this experimental feature of kotlinx.serialization with some success: https://github.com/Kotlin/kotlinx.serialization/blob/1.0.0-RC/docs/serializers.md#deriving-external-serializer-for-another-kotlin-class-experimental
Requires a pretty direct 1:1 mapping of table schema to endpoint responses which is not ideal, but is pretty handy for quick projects

Not working now.

I think I'm abandonning sqldelight for future projects because of this issue. What's the point of auto-generating value classes if you have to manually map them to other classes? It breaks the idea of the sql schema being the single source of truth.

same here


track download_button

Original issue by ZA89676 on 2023-02-04 23:11:17+00:00
Tracking does not seem to be enabled for download_button. Would it be possible to add?

@ZA89676  is this still relevant?

@ZA89676
Marking this as closed as duplicate owing to this being on the roadmap and already being tracked in #46
Thank you for raising the issue :) we will add it soon, just need to write the wrapper for it


kruise-rollout 0.4.1, fix the bug that MutatingWebhookConfiguration i…

…s not updated when upgrading charts.
Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:

[ ] I have bumped the chart version according to versioning
[ ] I have updated the chart changelog with all the changes that come with this pull request according to changelog.
[ ] Any new values are backwards compatible and/or have sensible default.
[ ] I have signed off all my commits as required by DCO.

Changes are automatically published when merged to master. They are not published on branches.

/approve


Adding file uploading to server directories

This pr adds functionality to upload files to servers defined directory instead of database.
adds more file types for content type.
also adresses this issue of 2562
to use this functions you must define storageId  as 'file' in your endpoint and the other usage are same as DatabaseCloudStorage.
Pre-launch Checklist

[ x ] I read the Contribute page and followed the process outlined there for submitting PRs.
[ x ] This update contains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[ x ] I read and followed the Dart Style Guide and formatted the code with dart format.
[ x ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[ ] I added new tests to check the change I am making.
[ ] All existing and new tests are passing.
[ ] Any breaking changes are documented below.

If you need help, consider asking for advice on the discussion board.
Breaking changes
If you have done any breaking changes, make sure to outline them here, so that they can be included in the notes for the next release.

I have read the CLA Document and I hereby sign the CLA

recheck

Do not consider pubspec.yaml updates. All reverted to original one.

Hey @xyzbilal!
Thanks for this great contribution.
We will try to get around to review this soon!


Better support for zero-entry trees

Hi,
I am enjoying trying out uproot.  In trying to look at the dask support, I ran into the following when trying to read a file with an empty tree (one can of course get these occasionally when running on the output of skim jobs):
>>> t.numentries
0
>>> t.lazyarrays(branches=['RunNumber', 'EventNumber'])
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/eos/user/p/ponyisi/.local/lib/python2.7/site-packages/uproot/tree.py", line 514, in lazyarrays
    lazyarrays = [(branch.name, branch.lazyarray(interpretation=interpretation, limitbytes=limitbytes, cache=cache, basketcache=basketcache, keycache=keycache, executor=executor)) for branch, interpretation in branches]
  File "/eos/user/p/ponyisi/.local/lib/python2.7/site-packages/uproot/tree.py", line 1427, in lazyarray
    return LazyArray._frombranch(self, interpretation, cache, basketcache, keycache, executor)
  File "/eos/user/p/ponyisi/.local/lib/python2.7/site-packages/uproot/tree.py", line 1742, in _frombranch
    self._chunksize = max(onlybranch.basket_numentries(i) for i in range(onlybranch.numbaskets))
ValueError: max() arg is an empty sequence
>>>

As far as I can tell, replacing the expression by "max() if onlybranch.numbaskets > 0 else 1" makes things work.
ETA: it seems for uproot.daskframe() to work, the chunksize() function in lazyarrays() needs to be fixed too.
Best,
Peter

You get revision 100!


[BEAM-6324] - Cassandra reader with query implemented

CassandraIO.Read doesn't support using WHERE to filter the input at the source (In Cassandra) which might provide great performance boost.
This PR adds the ability to provide a filter to the query.
Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

Implements https://issues.apache.org/jira/browse/BEAM-6324

@timrobertson100 , @echauchot I think the best place to add a test for this is ./sdks/java/io/cassandra/src/test/java/org/apache/beam/sdk/io/cassandra/CassandraIOIT.java
However it seems like the integration tests are no longer being run.
gradle build certainly doesn't and the comment at the head of the file only mentions how to run them using maven.
Can you please tell me if I can use these at all? If so how? thx.

@echauchot Re. size estimation - I can't see ./sdks/java/io/jdbc/src/main/java/org/apache/beam/sdk/io/jdbc/JdbcIO.java doing any such thing. Can you maybe point the line numbers out?

Can you please tell me if I can use these at all? If so how? thx.

You should be able to run them in gradle similar to this approach:
https://github.com/apache/beam/blob/master/sdks/java/io/elasticsearch-tests/elasticsearch-tests-5/src/test/java/org/apache/beam/sdk/io/elasticsearch/ElasticsearchIOIT.java#L41
Assuming it works, can you please update the JDoc as well? I don't know if you are aware but a few months ago Beam moved to gradle from maven and we're still cleaning up a few things like that documentation as it is found.
Thank you.

@timrobertson100 , @echauchot  Test was added. Please review.

Run Java PreCommit

The build logs show:
13:59:27 > Task :beam-runners-java-fn-execution:test
13:59:27
13:59:27 org.apache.beam.runners.fnexecution.data.GrpcDataServiceTest > testMessageReceivedBySingleClientWhenThereAreMultipleClients FAILED
13:59:27     java.lang.AssertionError at GrpcDataServiceTest.java:105
Seems unrelated to any of my changes. WDYT?

FYI: You can trigger a build by entering a comment like "Run Java PreComit", "Run Java..." here. You don't need to commit a "touch". The failure is a flakey test unrelated to your commits as far as I can see.

FYI: You can trigger a build by entering a comment like "Run Java PreComit", "Run Java..." here. You don't need to commit a "touch". The failure is a flakey test unrelated to your commits as far as I can see.

Thx :) Didn't know that. Your comment didn't seem to run it I think. Anyway the 'touch' commits seem to have run the build again and it looks like the code is good but maybe the tests aren't deterministic.
Anyway it looks like all tests are passing now.
Did you perhaps look at the code? Does it look good?

Regarding using the ITests to test cassandra, I think it would be better to do it in UTests. I understand why you chose ITests, because you wanted a proper cassandra instance to test against. This is why I pointed out using an embedded cassandra instance. I'm precisely refactoring CassandraIO to include such an embedded instance in UTests and also to remove CassandraService which was mainly there to enable injecting FakeCassandraService mock.

@srfrnk ok to make your tests in ITests. I will move them to UTests later on when I'm ready. I did not take a precise look at the code, I just wanted to discuss general directions. I'm ok to proceed with this PR as long as @timrobertson100 is ok. I'll let Tim finish his review.
Regarding rewriting the Reader it is out of sope of this PR but definitely promising ! I see that you replace the source with a Pardo, I think that it deserves a general project discussion on whether we generalize this approach.

Thanks.
Re. the Pardo approach - I found this saying that "ParDo is the recommended option".
Also I think "Splittable DoFn" would be the thing to replace both unbounded and bounded sources.
So that's why I was thinking of going that way. If there is such a discussion I'd be happy to see it.

LGTM.
Thank you for the changes @srfrnk

Can you please squash your commits into a single one and I will merge it @srfrnk
If you prefer I do it, I will do so on Wednesday (sorry, travelling and with little time right now)

I've tried to squash them but it got wierd. I suspect because I merged from main repo between commits it may not be possible and since I'm new to squashing I prefer not to create any damage.
Hopefully you can manage that when possible.
Thanks.

@srfrnk
Can you please grant me commit access to your repo? I need to do a force push after the rebase and fixup and have never done that on a PR branch directly in the master project. I feel safer doing that on your branch in your repo if you don't object.

@timrobertson100 You should be able to now. Please confirm.

 It needs a rebase to latest master, and then to fix the one conflict (accept the imports if I remember correctly). I will do it as soon as I can unless someone beats me to it.

On 6 Feb 2019, at 15:48, Srfrnk<EMAIL_ADDRESS>wrote:
@timrobertson100 You should be able to now. Please confirm.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks @timrobertson100! No rush - be well!

I'll try to get PR https://github.com/apache/beam/pull/7751 merged before so that you can use the embedded in your test

Can you please take a look @srfrnk and just confirm I didn't miss anything please?
I am afraid I had to rebase against master fixup and then do a force commit. I think it reflects your original intentions but is now a single commit and the branch in line with the current beam/master.
In the future, it will be easiest if you periodically rebase against master avoiding merge commits (git fetch upstream master, git checkout <your_branch>, git rebase origin/master). Following this approach makes it easy for you to finish with a squash of the last N commits into a single one.

@timrobertson100 Thanks. Will test it on the weekend and let you know.

run java precommit

@srfrnk @timrobertson100, hi guys, please wait a bit for my other PR to be merge (with 2 days I think). That would allow you to better test the filter/query in UTests.

Thanks @echauchot - will do.
@srfrnk I can imagine this is frustrating for you. Are you happy to adjust the tests when PR #7751 is merged or would you like me or @echauchot to tackle that?

@echauchot - Sure no prob.
@timrobertson100 - frustration level == 0 :) Will do that.

@srfrnk thanks for your understanding! I know, that this PR as taken too long to start the review (because no reviewed picked it up automatically) at least we did our best to avoid scope creeping :) and took care of the embedded cassandra problem :)
By the way, FYI the experience with this PR not been assigned a reviewer has helped the community improve by changing the template PR to remind contributors to chose a reviewer and help them in that action.

@echauchot I'm glad it helped.
I believe we all share the goal of making Beam better.
Please update me on when your PR is merged so that I can redo the tests.

@srfrnk I just merged my PR, please rebase, refactor (there is no more CassandraService and CassandraServiceImpl) and adapt your UTests to the new embedded Cassandra instance

Thanks @echauchot - I hope to have to time this weekend. Will update.

@echauchot - I rebased the code. Had to manually re-add the changes but I think it was worth it. Your PR makes the tests much better IMHO.
@timrobertson100 - I hope this time I got everything right - the code, single commit, docs and tests. Could you please review?

@srfrnk Thanks for rebasing, and also for adding your test as UTest !
Also, I just overlooked the PR (leaving the review to Tim) 2 coments:

would it be complicated to add a more general withQuery instead of only withWhere?
if too complicated I would advice to update the withWhere javadoc with a link to cassandra doc to warn the user that he should query on a primary/clustering column and tell him about the exception he will get otherwise.

I considered using the term Query rather then Where - however I suspect it may confuse users.
We are just injecting a partial filter to the Where clause of the cassandra Query here.
It will not allow setting the full Query.
It even doesn't allow setting the full Where clause indeed.
That's why I finally decided to use Where rather then Query in the property name.
WDYT?

@srfrnk why not just allow the user to pass the query as a String like it is done in ElasticsearchIO.Read.withQuery() for ex ?

@echauchot I would like that of course - however I don't know how that can be achieved at this time. I was hoping at the beginning to be able to create an API similar to BigQueryIO which I used a lot and liked very much. It also has a .withQuery function similar to ElasticsearchIO. However with the current method where a query is buing built for the splits in CassandraIO I can't think of a safe and comfortable way of allowing the user bring his own query while managing the query for the splitting.
I finally settled on having the user supply a filter in the form of a partial Where clause.
Can you think of a better way?

Run JavaPortabilityApi PreCommit

@srfrnk @echauchot
I am running a workshop in Australia for the next week and a half and won't have much time to Beam. The code appears similar to the previous commit which was reviewed and changes were all applied - thank you! If @echauchot is ok with the tests I recommend this gets merged.

Thanks @timrobertson100, except for the new Unit Tests the rest is indeed identical.
I would be glad to merge and get this over with myself :)

@srfrnk, basically split query only adds where token >= startToken AND token <= endToken so we could have a String builder that concatenates these split filters with the query provided by the user. But this can be done in a future PR. So please just add the javadoc user warning (cf above) and I will merge the PR as Tim is unavailable and he is ok with the PR.

@echauchot Could you please review the javadoc comment I added?

@echauchot Thanks. Can you explain "checkstyle fix"?
Will squash once you approve everything.

@srfrnk yes, the current build fails because of checkstyle violations: see gradle build scan

@echauchot - Rebased. Hopefully all passes this time.

@srfrnk checkstyle now passes but cassandraIO javadoc is incorrect: see https://scans.gradle.com/s/y4f3d4jbyzdcw/console-log?task=:beam-sdks-java-io-cassandra:javadoc

@echauchot - Looks like it's passing now.


weather-icons: use mkDerivation & fetchFromGitHub

Motivation for this change
personally I think this is better to read and maintain. I know more packages that use a similar structure, but first of all I want to hear some comments about the changes.
Things done

Built on platform(s)

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

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

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

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

[x] Fits CONTRIBUTING.md.

Therefore we could not use the pname&version and fetchFromGitHub. So I guess this change is not wanted.


Embed string literal in string literal

That sounds insane!
Except maybe for this case.
You are writing documentation for a class and want to be able to use a string literal in your example code... You can't and are forced to do awful things like...
https://github.com/ponylang/ponyc/pull/615/files

Assigning myself to this so I remember to open an RFC for this.

Open RFC request. Closing this:
https://github.com/ponylang/rfcs/issues/52


Add permission checking based on Attribute.type

I want to merge this change because adds validation if user has permissions to create/update/delete AttributeValue based on Attribute.type.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases

Refactor of those changes https://github.com/saleor/saleor/pull/13650


[python-package] No warning if single alias of num_boost_round is passed

I see a misleading warning log line when I pass a 'num_iterations' argument my training params. There should be no alias warning in that case, only when more than one alias for the number of boosted trees is passed.
By picking the last of the alias in the possibles (available in params), the "tie breaking behaviour" should be conserved.

Thanks for the welcome, feedback and advice @jameslamb
First, I just pushed a possible fix for the failing tests 🤞
About the aim of the MR, at my work I use LightGBM extensively in some AWS Sagemaker instances (thanks for contributing to this awesome package!). When I set the parameter n_estimators my screen is populated with the UserWarning line (because of repeated training instances). There may some non-repeat warning config missing on that cloud instance (because locally I cannot reproduce the message to show more than one time), but I also find that the warning message is not helpful. I had to go through the docs and code to be sure my parametrization was working as intended (why warn if I am using a single alias?).
Here are the before/after screenshots:

I read the discussion in https://github.com/microsoft/LightGBM/issues/6324 with interest. I would defend that a warning should be raised even if the value of two+ aliases is the same. The reason being, on such instance, the user is most likely mis-using the parametrization and should be made aware of the redundant input information.

In your case the warning is showing up because the train function has an argument num_boost_round, which defaults to 100, so LightGBM is seeing n_estimators=1, num_boost_round=100 and warning you that it's choosing n_estimators. I believe in this case the warning is correct.

@jmoralez I will check it tomorrow =) Will let you know!

@vnherdeiro there is still quite a bit to do to implement the plan agreed to in #6458. For example, cv() needs to be updated with similar behavior as train(), and tests covering those 2 functions and the scikit-learn interface need to be added.
I would really like to fix this as part of the next release (thank you for reminding us!), and we are under some time pressure to get that release out in the next 2 weeks (see #6522).
In this interest of time, would it be ok with you if I close this and put up a separate pull request addressing this? We would really love to have you contribute to LightGBM, but I think this particular change might just be a difficult first contribution.

@jmoralez Have tested your point, indeed I had tried using different aliases, even 'num_boost_round' but always inside params, hence I couldn't get rid of the warning. Thanks for the help!
@jameslamb I am not familiar with the API and never used cv. I believe you this change needs a bigger scope. Agreed to close this PR. I do want to contribute to this project. Do you have any lower hanging fruit to suggest?

I believe you this change needs a bigger scope. Agreed to close this PR.

Thanks very much for understanding!
I'm working on this in #6579, so I'll close this PR.

I do want to contribute to this project. Do you have any lower hanging fruit to suggest?

Thanks very much, we appreciate it! #6361 or #6498 would be good places to start. You can @-mention me on those (or on a draft pull request you open) if you want any help.
When you do that, please use a branch other than master on your fork. I think you'll find that easier to work with, especially if you have multiple pull requests open at the same time.

@vnherdeiro if you're interested in seeing how I implemented + tested this, please see #6579.
Thanks again for your work here and for bringing this issue back to our attention. It's long overdue for a fix.

@jameslamb Thanks for suggesting the changes above as possibilities of contributing. I checked your MR for this issue btw, the new behaviour looks good to me!


feat(shortsAndBigDecimals): add shorts and big decimals

Signed-off-by: dark0dave<EMAIL_ADDRESS>Closes #1673

@yirutang tests added, ready for review


[Suggestion] [Shortcut Guide] Show the keyboard shortcuts for all programs

Summary of the new feature/enhancement
Currently you can hold the Windows key to bring up the Shortcut Guide overlay, which shows you the many keyboard shortcuts available using the Windows key for managing window location and other operating system features. This is great, no need to memorise everything! I wish this awesome feature worked on all other programs where keyboard shortcuts can speed up your workflow.
My suggestion is to extend this helpful overlay for all other programs and applications.
Either through a super pretty overlay like the one above, or to simply bring up the program's own in-built shortcuts menu (as present in some popular programs such as Adobe Premiere or MS Word).
Shortcuts are not always intuitive across programs; it is sometimes hard to find where the programs specifies their list of available shortcuts; it would be quicker and very useful to have shortcuts appear on screen using the single button you need to memorise.
Proposed technical implementation details (optional)
The way I think it could work is to either:
a) provide an optional "hook" for those program developers to launch their own pretty overlay when the Win key is held;
or b) Power Toys itself could make an index of popular programs, and when we hold the Windows key in these specific programs, somewhere on the screen (say top-left) there is a button like "Show [Program]-specific shortcuts" which brings up that programs own in-built shortcuts menu/editor.
Bringing up that menu might also be invoked by a more direct shortcut (like say Win+Shift+W).
Thank you for your consideration, and I apologise in advance if this has already been suggested!

Hi @jimitirimi
the tracker for this feature request is https://github.com/microsoft/PowerToys/issues/3577
Feel free to add your comments there.
Closing this as duplicate.
Thanks.

Thank you, I will join the conversation in #3577


refactor: rename const to expr

Instead of doing something like
type Foo {
  bar: Bar @const(data: "{{vars.bar}}"
}

Do this:
type Foo {
  bar: Bar @expr(body: "{{vars.bar}}"
}

Basically rename const to expr and the data field to body.
Technical Requirements

Ensure unit tests are updated
Ensure documentation is updated

/bounty 50$

/attempt #1640


Switch from Markdown to XML

Anthropic recommends XML, and in testing other models, XML comes out ahead, especially for complex prompts. I'll work on converting and testing jar3d with XML.
Comparison of RAW, Markdown, XML, and JSON prompt formatting

Sounds like an interesting approach. I've found that it works well with Markdown, and is easy to read/update however it would be interesting to see results with XML.


chore: move .storybook config folder to packages/storybook

@chanar no info on why this is better?

@lkraav commented on gitter.
"I moved .storybook config folder to packages/storybook to simplify dependency management".

Indeed, it's just not obvious to a noob like me how did it become simpler.

I was thinking about putting all the Storybook stuff into its package, so definitely 👍

Right. I wasn't sure if the current toolchain setup somehow required .storybook sit at root, etc


Drop Python 2, drop Django<2.2

Fixed Django 4.0 deprecation warning (resolves #24)

Codecov Report

Merging #25 into master will decrease coverage by 0.46%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
- Coverage   62.67%   62.21%   -0.47%
==========================================
  Files           6        6
  Lines         217      217
==========================================
- Hits          136      135       -1
- Misses         81       82       +1

Impacted Files
Coverage Δ

sphinxcontrib_django/docstrings.py
45.63% <100.00%> (-1.35%)
:arrow_down:

sphinxcontrib_django/tests/test_docstrings.py
98.07% <0.00%> (+1.92%)
:arrow_up:

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 5417a32...65ecf65. Read the comment docs.

@therefromhere Thanks a lot for your PR, I now took over maintenance for this package and merged the changes of my fork back into this repo. These changes also include 66703432c8b5704b5bcbeca13a3fc93fa93e19fc which fixes the original issue.


Upgrade package to Umbraco v8

Updated .NET version to 4.7.2
Removed old Umbraco version and installed UmbracoCms.Web v8.0.0
Update .nuspec file to reflect min version

Thanks for contributing @samgooch! We'll review it on Monday probably and get back to you with eventual feedback. Looks good from initial check 👌👍


Fix empty state for PIN

What

Why

Test Plan

✅ | ❌ I've added unit tests for this change.
✅ | ❌ The reviewer should manually test the changes in this PR.

Demo

How

Current dependencies on/for this PR:

main

PR #133

PR #134

PR #136   👈

This stack of pull requests is managed by Graphite.


Initial value not selecting radio button

I set the value here:
https://github.com/QuantumInformation/Javascript-code-generation-tools/blob/master/src/reducers/jsonCodeTools.js#L13
but it doesn't select the input that has the same value:
https://github.com/QuantumInformation/Javascript-code-generation-tools/blob/master/src/features/codeControls/CodeControls.js#L28

I'll have a look at this as have some free time and see if I can raise a PR, if someone else can confirm the issue..


Multi-tenant service isolation (again!)

OK, resubmitting the service isolation stuff. You can diff against danwinship/openshift-sdn service-isolation-old to see what's changed; basically it's just adding the service network to StartMaster and WriteNetworkConfig, which is needed in the origin osdn plugin to get that into the ClusterNetwork.

@rajatchopra @pravisankar PTAL

@rajatchopra Please check the OF rules


How to handle key vault integration in named parameters for multiple environments

Hi there,
I'm not seeing a way to allow for handling key vault integration in the named parameters in the configuration..yaml between environments.  For example, it looks like the only properties available to set on named parameters in the config file are:
name:
displayName:
value:
If you have your named value tied to a key vault there are a few different properties that need to be available:
keyVault (object): {secretIdentifier:}
secret (bool?):
Is this something that could be added to your backlog?
Thanks!

https://github.com/Azure/apiops/issues/62
Thanks for bringing this up. We would be tracking this as part of the above enhancement to ensure keyvault identifiers are included in config.yaml as well.


Support increase and decrease of datasets on the componentWillReceiveProps

Assign nextProps.data.datasets to chart.data.datasets simply, to support increase and decrease of datasets.
This fix is for #128

This change is mistake.
When data is updated same data, the chart is redrawed.
It is the same behavior with redraw option.


Error getting account info

Description
Enter the information required to get an account info for 0.0.45912927 on testnet and sign with the fee payer key. Nothing returns or no error message shown.
Steps to reproduce
See above
Logs:
2022-06-06 23:21:27.943 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.remote.RemoteFilesMap.getRemoteFileList(RemoteFilesMap.java:200) - Could not load remote file from info due to error Hedera Client: Unrecognized type UNKNOWN
2022-06-06 23:21:27.943 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.remote.RemoteFilesMap.getRemoteFileList(RemoteFilesMap.java:201) - com.hedera.hashgraph.client.core.exceptions.HederaClientException: Hedera Client: Unrecognized type UNKNOWN
2022-06-06 23:21:28.183 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.remote.BundleFile.loadMaps(BundleFile.java:123) - Unexpected value: testFile.json
2022-06-06 23:21:28.183 [JavaFX Application Thread] ERROR com.hedera.hashgraph.client.core.remote.BundleFile.loadMaps(BundleFile.java:123) - Unexpected value: testFile.bin

Additional context
No response
Hedera network
other
Version
0.11.0-alpha.1
Operating system
No response

used nickname from the account memo that was set. Not a bug.


Can not install through pip

Thanks for this great library, but I could not really install it through pip. I have cmake installed in my ubuntu system, and when I try to install through pip3.8 install pqkmeans the error that I get :
(env_38) user@user-LPC:~/projects/tmp$ pip3.8 install pqkmeans
Collecting pqkmeans
  Using cached pqkmeans-1.0.5.tar.gz (161 kB)
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Installing backend dependencies ... done
  Preparing metadata (pyproject.toml) ... done
Collecting scipy
  Using cached scipy-1.10.1-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (34.5 MB)
Collecting numpy
  Using cached numpy-1.24.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (17.3 MB)
Collecting texmex-python==1.0.0
  Using cached texmex_python-1.0.0.tar.gz (2.5 kB)
  Preparing metadata (setup.py) ... done
Collecting pipe
  Using cached pipe-2.0-py3-none-any.whl (8.8 kB)
Collecting six
  Using cached six-1.16.0-py2.py3-none-any.whl (11 kB)
Collecting scikit-learn
  Using cached scikit_learn-1.2.2-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (9.8 MB)
Collecting lshash3
  Using cached lshash3-0.0.8.tar.gz (9.4 kB)
  Preparing metadata (setup.py) ... done
Collecting joblib>=1.1.1
  Using cached joblib-1.2.0-py3-none-any.whl (297 kB)
Collecting threadpoolctl>=2.0.0
  Using cached threadpoolctl-3.1.0-py3-none-any.whl (14 kB)
Collecting bitarray
  Using cached bitarray-2.7.3-cp38-cp38-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (271 kB)
Building wheels for collected packages: pqkmeans
  Building wheel for pqkmeans (pyproject.toml) ... error
  error: subprocess-exited-with-error

  × Building wheel for pqkmeans (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [86 lines of output]
      running bdist_wheel
      running build
      running build_py
      creating build
      creating build/lib.linux-x86_64-cpython-38
      creating build/lib.linux-x86_64-cpython-38/pqkmeans
      copying pqkmeans/evaluation.py -> build/lib.linux-x86_64-cpython-38/pqkmeans
      copying pqkmeans/__init__.py -> build/lib.linux-x86_64-cpython-38/pqkmeans
      creating build/lib.linux-x86_64-cpython-38/test
      copying test/__init__.py -> build/lib.linux-x86_64-cpython-38/test
      creating build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      copying pqkmeans/clustering/__init__.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      copying pqkmeans/clustering/cpp_implemented_clustering_sample.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      copying pqkmeans/clustering/pure_python_clustering_sample.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      copying pqkmeans/clustering/bkmeans.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      copying pqkmeans/clustering/pqkmeans.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/clustering
      creating build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      copying pqkmeans/encoder/encoder_sample.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      copying pqkmeans/encoder/__init__.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      copying pqkmeans/encoder/itq_encoder.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      copying pqkmeans/encoder/encoder_base.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      copying pqkmeans/encoder/pq_encoder.py -> build/lib.linux-x86_64-cpython-38/pqkmeans/encoder
      creating build/lib.linux-x86_64-cpython-38/test/clustering
      copying test/clustering/test_pqkmeans.py -> build/lib.linux-x86_64-cpython-38/test/clustering
      copying test/clustering/__init__.py -> build/lib.linux-x86_64-cpython-38/test/clustering
      copying test/clustering/test_cpp_implemented_clustering_sample.py -> build/lib.linux-x86_64-cpython-38/test/clustering
      copying test/clustering/test_pure_python_clustering_sample.py -> build/lib.linux-x86_64-cpython-38/test/clustering
      copying test/clustering/test_bkmeans.py -> build/lib.linux-x86_64-cpython-38/test/clustering
      creating build/lib.linux-x86_64-cpython-38/test/encoder
      copying test/encoder/__init__.py -> build/lib.linux-x86_64-cpython-38/test/encoder
      copying test/encoder/test_pq_encoder.py -> build/lib.linux-x86_64-cpython-38/test/encoder
      copying test/encoder/test_encoder_sample.py -> build/lib.linux-x86_64-cpython-38/test/encoder
      copying test/encoder/test_itq_encoder.py -> build/lib.linux-x86_64-cpython-38/test/encoder
      running build_ext
      Traceback (most recent call last):
        File "/home/user/projects/tmp/env_38/bin/cmake", line 5, in <module>
          from cmake import cmake
      ModuleNotFoundError: No module named 'cmake'
      Traceback (most recent call last):
        File "/home/user/projects/tmp/env_38/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/home/user/projects/tmp/env_38/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/user/projects/tmp/env_38/lib/python3.8/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 251, in build_wheel
          return _build_backend().build_wheel(wheel_directory, config_settings,
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 413, in build_wheel
          return self._build_with_temp_dir(['bdist_wheel'], '.whl',
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 398, in _build_with_temp_dir
          self.run_setup()
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/build_meta.py", line 335, in run_setup
          exec(code, locals())
        File "<string>", line 76, in <module>
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/__init__.py", line 108, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 1221, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-5x4zvxen/normal/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 343, in run
          self.run_command("build")
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 1221, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/command/build.py", line 131, in run
          self.run_command(cmd_name)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/dist.py", line 1221, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-5x4zvxen/overlay/lib/python3.8/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "<string>", line 37, in run
        File "/usr/lib/python3.8/subprocess.py", line 415, in check_output
          return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
        File "/usr/lib/python3.8/subprocess.py", line 516, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['cmake', '--version']' returned non-zero exit status 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for pqkmeans
Failed to build pqkmeans
ERROR: Could not build wheels for pqkmeans, which is required to install pyproject.toml-based projects

How to fix it?

thanks for your reply


Updating from v6.0.0 to v7.4.0

PUBG Changelog
v6.0.0

Fixed bug related to bestRankPoint being spelling as bestRankPoints

v7.0.0

Added xbox-sa as a valid region
Added a status api in order to get the status of the api and its ping/heartbeat.

v7.1.0

Added LogPlayerAttack.fireWeaponStackCount

v7.4.0

Added LogPlayerPosition.vehicle

Misc

Added XBOX as a PlatformRegion since endpoints from now on will support it.
Added PSN and psn-{region} to the PlatformRegion enum

@martinsileno I went ahead and updated this library to be compatible with v7.4.0 of PUBG's api.
I've added changes, relevant tests, and ensured that the project is error free and passes all tests,

@martinsileno Is there any update on this?

Hi @Tdortiz, sorry for the delay.
I'm on vacation at the moment, so I don't have much time and can't release new versions on NPM until the 24th of November.
Let me know if this is ok to close, I quickly looked at the changes and it seems OK!

@martinsileno No problem! Enjoy your vacation :)
I've been running my Discord Bot with these changes locally for a few days and everything is working as expected. I think it should be good to close 👍

@martinsileno I went ahead and added support for Playstation

Merged and released as 1.6.0, thanks!

please, anyone know the topic or video explaining how I can use this (pubg document), please?
i use node js and typescript not professional
Thanks


[FormRecognizer] Remove US receipts

While at it I also did some refactoring around FormField.

Fixes #9231

/azp run js - formrecognizer - tests

I could add some verifications on the returned fields like verifying the form type etc. Testing of receipt field is gone because related product code is gone.

/azp run js - formrecognizer - tests


Fails to build with Bazel 8.0.0

Required information
Operating system
macOS Sequoia 15.2
Compiler version:
$ clang --version
Homebrew clang version 19.1.1
Target: arm64-apple-darwin24.2.0
Thread model: posix
InstalledDir: /opt/homebrew/Cellar/llvm/19.1.1/bin

Eclipse iceoryx version:
main
Observed result or behaviour
First, I get an error about both --enable_bzlmod and --enable_workspace being disabled:
$ bazel build //...
Starting local Bazel server and connecting to it...
WARNING: ignoring JAVA_TOOL_OPTIONS in environment.
ERROR: Error computing the main repository mapping: error loading package 'external': Both --enable_bzlmod and --enable_workspace are disabled, but one of them must be enabled to fetch external dependencies.

If I set --enable_bzlmod, I get the following errors:
$ bazel build --enable_bzlmod //...
WARNING: For repository 'rules_cc', the root module requires module version<EMAIL_ADDRESS>but got<EMAIL_ADDRESS>in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
WARNING: Couldn't auto load rules or symbols, because no dependency on module/repository 'rules_android' found. This will result in a failure if there's a reference to those rules or symbols.
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_hoofs/test/stresstests/BUILD.bazel", line 49, column 16, in <toplevel>
                srcs = glob([
Error in glob: glob pattern '*.hpp' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_platform/test/BUILD.bazel", line 21, column 16, in <toplevel>
                srcs = glob([
Error in glob: glob pattern 'moduletests/*.hpp' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_hoofs/test/BUILD.bazel", line 48, column 16, in <toplevel>
                srcs = glob([
Error in glob: glob pattern 'integrationtests/*.hpp' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_posh/BUILD.bazel", line 118, column 16, in <toplevel>
                srcs = glob(
Error in glob: glob pattern 'source/log/**' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: package contains errors: iceoryx_platform/test
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_hoofs/BUILD.bazel", line 34, column 16, in <toplevel>
                srcs = glob([
Error in glob: glob pattern 'design/source/*.cpp' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: package contains errors: iceoryx_hoofs/test/stresstests
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_posh/test/BUILD.bazel", line 28, column 16, in <toplevel>
                data = glob(["input/**"]),
Error in glob: glob pattern 'input/**' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: package contains errors: iceoryx_hoofs/test
ERROR: package contains errors: iceoryx_posh/test
ERROR: package contains errors: iceoryx_hoofs
ERROR: package contains errors: iceoryx_posh
ERROR: Traceback (most recent call last):
        File "/Users/dzc/Repos/github/eclipse-iceoryx/iceoryx/iceoryx_binding_c/test/BUILD.bazel", line 53, column 16, in <toplevel>
                srcs = glob([
Error in glob: glob pattern 'integrationtests/*.hpp' didn't match anything, but allow_empty is set to False (the default value of allow_empty can be set with --incompatible_disallow_empty_glob).
ERROR: package contains errors: iceoryx_binding_c/test
WARNING: Target pattern parsing failed.
ERROR: Skipping '//...': Error evaluating '//...': error loading package 'iceoryx_binding_c/test': Package 'iceoryx_binding_c/test' contains errors
ERROR: Error evaluating '//...': error loading package 'iceoryx_binding_c/test': Package 'iceoryx_binding_c/test' contains errors
INFO: Elapsed time: 6.459s
INFO: 0 processes.
ERROR: Build did NOT complete successfully

Expected result or behaviour
Build succeeds
Conditions where it occurred / Performed steps:

Update Bazel to 8.0.0 LTS
bazel build //...

Additional helpful information
None

@davidzchen we are aware of this. We support only bazel up to 7.4 - porting iceoryx to the newest bazel version requires some effort and is currently not on our top prio list.
We would happily receive some support and a pull request here.


Failed to parse stablehlo program

Testing with mlir files: https://github.com/openxla/stablehlo/blob/main/stablehlo/tests/interpret/collective_broadcast.mlir
Resulting in RuntimeError: INTERNAL: Unable to parse module

It's failed at this step: https://github.com/google-ai-edge/model-explorer/blob/main/src/builtin-adapter/model_json_graph_convert.cc#L362
Could you help take a look at this issue here? @jpienaar

Hey, this looks like a mismatch in the textual format. StableHLO doesn't guarantee compatibility there. One of the ops may have changed and needs updating the file

Can I be able to generate MLIR based graphs using this tool? How complete is the support currently?

Hi @Sameeranjoshi, we currently do not support general MLIR. We do generally support StableHLO. Which is why this is an issue. Thanks.


Add UUID generator to JobClient.

Changes proposed in this PR

Make temporal UUID code in our JobClient API that can be used by our customers.

Why are we making these changes?

Investigation found that random ID's could be a bottleneck in job submission.
Using temporal UUID's would let us increase the job submission rate by 10x-30x, to 1000-3000 jobs/second, if used for commitlatch and by client code.
This includes code that customers can call that makes appropriate UUID's.

Yes. This doesn't change any performance --- the code here is technically dead as Cook doesn't use it. But its part of a set of changes that will improve performance to the described level.


NOJIRA Removed a couple of unused vars

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy


3.8 compatibility

The installed version of the Kirby Roomle plugin is not compatible with Kirby 3.8.0-rc.2

I will test the plugin with Kirby 3.8 soon and then release an update that unlocks support.


Convert test-protocol template to form

Description
Changes proposed in this pull request:
Test protocol could be a form.

Form:

Rendered:

Related issue(s)

https://github.com/kyma-project/application-connector-manager/pull/303

One of the cons of this solution is separated issue from checkbox (although we could remove "What went wrong" and just add issues manually after filling the form - it can be edited as regular markdown).
Another is lack of completion in fields.


AtlasBuilder.cs not compiling with Unity 2018.3

Unity moved the TextureCompressionQuality enumeration to the editor namespace in 2018.3.
The following call to CompressTexture():
https://github.com/leapmotion/UnityModules/blob/127374083128adbe6699c1ca96784a6d15d508f8/Assets/LeapMotion/Modules/GraphicRenderer/Scripts/Utility/AtlasBuilder.cs#L343
needs to be changed to:
UnityEditor.EditorUtility.CompressTexture(tex, _format, UnityEditor.TextureCompressionQuality.Best);

This should be fixed as of the 4.5.0 release.