Packages Integration Tests: video_player fails

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
The following test case fails on:

Flutter master, 3.17.0-10.0.pre.13
Flutter stable 3.16.0

First way:

Clone the  packages repository: git clone GitHub - flutter/packages: A collection of useful packages maintained by the Flutter team

Navigate to the video_player test directory: cd packages/video_player/video_player/example

Get the Flutter dependencies: flutter pub get

Navigate to the ios folder : cd ios

Run pod install: pod install

Run the test using the following command: flutter test integration_test >> logs.txt

Check the logs

Second way:

using the finder go to the ios folder: packages/packages/video_player/video_player/example/ios

open the file: Runner.xcworkspace using XCode

Run the tests using  XCode

Expected results
Running all tests should succeed.
Actual results
The following test case fails on:
Flutter master, 3.17.0-10.0.pre.13
Flutter stable 3.16.0
Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
The following TestFailure was thrown running a test:
Expected: <false>
  Actual: <true>

video_player_video_player_example-master-logs.txt

Flutter Doctor output
Doctor output
[✓] Flutter (Channel master, 3.17.0-10.0.pre.13, on macOS 14.0 23A344 darwin-arm64, locale en-UY)

Flutter version 3.17.0-10.0.pre.13 on channel master at /Users/haironchaviano/Documents/flutter

Upstream repository [GitHub - flutter/flutter: Flutter makes it easy and fast to build beautiful apps for mobile and beyond](https://github.com/flutter/flutter.git)

Framework revision ca31aa17b2 (20 hours ago), 2023-11-15 14:48:18 -0500

Engine revision 30327eae08

Dart version 3.3.0 (build 3.3.0-135.0.dev)

DevTools version 2.30.0-dev.4

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)

Android SDK at /Users/haironchaviano/Library/Android/sdk

Platform android-34, build-tools 34.0.0

Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java

Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.1)

Xcode at /Applications/Xcode-beta.app/Contents/Developer

Build 15C5059c

CocoaPods version 1.13.0

[✓] Chrome - develop for the web

Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)

Android Studio at /Applications/Android Studio.app/Contents

Flutter plugin can be installed from:

      🔨 [Flutter - IntelliJ IDEs Plugin | Marketplace](https://plugins.jetbrains.com/plugin/9212-flutter)

Dart plugin can be installed from:

      🔨 [Dart - IntelliJ IDEs Plugin | Marketplace](https://plugins.jetbrains.com/plugin/6351-dart)

Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.84.2)

VS Code at /Users/haironchaviano/Downloads/Visual Studio Code.app/Contents

Flutter extension version 3.76.0

[✓] Connected device (5 available)

SM G950U (mobile)          • 98897a314d334d504a                   • android-arm64  • Android 9 (API 28)

iPhone 15 Pro (mobile)     • 07D35B8C-CE19-4703-82F7-D0FC5AD8905F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)

iPhone 15 Pro Max (mobile) • 2D8A5E37-6BE7-4735-BBB4-9E5A5427E7D2 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)

macOS (desktop)            • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64

Chrome (web)               • chrome                               • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources

All expected network resources are available.

[✓] Flutter (Channel stable, 3.16.0, on macOS 14.0 23A344 darwin-arm64, locale en-UY)

Flutter version 3.16.0 on channel stable at /Users/haironchaviano/Documents/flutter

Upstream repository [GitHub - flutter/flutter: Flutter makes it easy and fast to build beautiful apps for mobile and beyond](https://github.com/flutter/flutter.git)

Framework revision db7ef5bf9f (20 hours ago), 2023-11-15 11:25:44 -0800

Engine revision 74d16627b9

Dart version 3.2.0

DevTools version 2.28.2

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)

Android SDK at /Users/haironchaviano/Library/Android/sdk

Platform android-34, build-tools 34.0.0

Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java

Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.1)

Xcode at /Applications/Xcode-beta.app/Contents/Developer

Build 15C5059c

CocoaPods version 1.13.0

[✓] Chrome - develop for the web

Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)

Android Studio at /Applications/Android Studio.app/Contents

Flutter plugin can be installed from:

      🔨 [Flutter - IntelliJ IDEs Plugin | Marketplace](https://plugins.jetbrains.com/plugin/9212-flutter)

Dart plugin can be installed from:

      🔨 [Dart - IntelliJ IDEs Plugin | Marketplace](https://plugins.jetbrains.com/plugin/6351-dart)

Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.84.2)

VS Code at /Users/haironchaviano/Downloads/Visual Studio Code.app/Contents

Flutter extension version 3.76.0

[✓] Connected device (5 available)

SM G950U (mobile)          • 98897a314d334d504a                   • android-arm64  • Android 9 (API 28)

iPhone 15 Pro (mobile)     • 07D35B8C-CE19-4703-82F7-D0FC5AD8905F • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)

iPhone 15 Pro Max (mobile) • 2D8A5E37-6BE7-4735-BBB4-9E5A5427E7D2 • ios            • com.apple.CoreSimulator.SimRuntime.iOS-17-2 (simulator)

macOS (desktop)            • macos                                • darwin-arm64   • macOS 14.0 23A344 darwin-arm64

Chrome (web)               • chrome                               • web-javascript • Google Chrome 119.0.6045.159

[✓] Network resources

All expected network resources are available.

@rzambroni hi, could you provide a full log with which specific test failure?

Hi @hellohuanlin, absolutely, just attached the full log file on the logs section.

All tests are passing locally for me with the stable 15.1 release; closing.


Netkvm guest announce

Hi @YanVugenfirer ,
This is the first merge commit pushed to the repo since 2014 and there's only 13 of them total. I was wondering if we want to have a merge vs. rebase policy for virtio-win.
I would personally lean towards always rebasing (i.e. no merge commits, the "Rebase and merge" option in GitHub UI) as I find it easier to work with linear history. That would also match what we've been doing until now when patches were manually applied to master/stable one-by-one.
Thanks!
Ladi

Hi,
Actually I always insisted on the rebase and that's why we don't have merge
commits.
Unfortunately in this case I relied to much on github interface.
Not sure how to force the rebase if we want to use this useful "merge"
button :)
Best regards,
Yan.
On Wed, Feb 22, 2017 at 4:43 PM, Ladi Prosek<EMAIL_ADDRESS>wrote:

Hi @YanVugenfirer https://github.com/YanVugenfirer ,
This is the first merge commit pushed to the repo since 2014 and there's
only 13 of them total. I was wondering if we want to have a merge vs.
rebase policy for virtio-win.
I would personally lean towards always rebasing (i.e. no merge commits,
the "Rebase and merge" option in GitHub UI) as I find it easier to work
with linear history. That would also match what we've been doing until now
when patches were manually applied to master/stable one-by-one.
Thanks!
Ladi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/102#issuecomment-281688276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDkWOxgubCdWUkWITob3S9-zIlUKf3Iks5rfEl6gaJpZM4MFdyW
.

Sorry, totally my fault... I missed the "rebase and merge" option.
On Wed, Feb 22, 2017 at 5:37 PM, Yan Vugenfirer<EMAIL_ADDRESS>wrote:

Hi,
Actually I always insisted on the rebase and that's why we don't have
merge commits.
Unfortunately in this case I relied to much on github interface.
Not sure how to force the rebase if we want to use this useful "merge"
button :)
Best regards,
Yan.
On Wed, Feb 22, 2017 at 4:43 PM, Ladi Prosek<EMAIL_ADDRESS>wrote:

Hi @YanVugenfirer https://github.com/YanVugenfirer ,
This is the first merge commit pushed to the repo since 2014 and there's
only 13 of them total. I was wondering if we want to have a merge vs.
rebase policy for virtio-win.
I would personally lean towards always rebasing (i.e. no merge commits,
the "Rebase and merge" option in GitHub UI) as I find it easier to work
with linear history. That would also match what we've been doing until now
when patches were manually applied to master/stable one-by-one.
Thanks!
Ladi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/102#issuecomment-281688276,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDkWOxgubCdWUkWITob3S9-zIlUKf3Iks5rfEl6gaJpZM4MFdyW
.

--
Daynix Computing LTD
Yan Vugenfirer, CEO
Email<EMAIL_ADDRESS>Phone (Israel): +972-54-4758084
Phone (USA): +1-7204776716
Phone (UK): +44-2070482938
Web: www.daynix.com


[BEAM-171] Fix JAXBCoder in the nested context

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace "<Jira issue #>" in the title with the actual Jira issue
number, if there is one.
[x] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

JAXBCoder in the nested context is broken with any coder that writes
content after the output of the XML stream, as decode will read the
entire remaining stream and fail.
In the nested context, prepend a long representing the size of the XML
while encoding, and limit the size of the returned stream while
decoding.
Replaces #112
This should not be ported to the DataflowJavaSDK

R: @dhalperi

beam issue?

Stopped flushing, as discussed, as the marshaller must have already written its contents to the stream before closed, and the stream will be flushed and closed by the actual owner.

LGTM, merging


[FEA] Take into account org.apache.spark.timeZone in Parquet/Avro from Spark 3.2

From Spark 3.2, a new metadata key org.apache.spark.timeZone is written into the the output Parquet/Avro file. That metadata is used to check and rebase datetime.
We need to check that metadata while rebasing datetime. In particular, we need to throw exception if the file was written in timezone other than UTC.
Ref: https://github.com/apache/spark/pull/34973

Scope for this issue: throw exception at runtime if we detect a non-UTC timezone.
Also, make sure to file a separate issue to track fixing this once we have timezone support fully enabled.

Reading parquet now checks for the timezone. We only need to work for Avro.

Reading parquet now checks for the timezone. We only need additional work for Avro.

I did a test on Avro in a round-trip integration test. Based on my test, currently our Gpu Avro scan didn't have timestamp or date support yet. So probably we should narrow down the scope only with Parquet and file another ticket tracking Avro part. And we can revisit it once we had some customer needs for Avro and it may have pre-requisite for Avro support in timestamp and date.
23/11/10 01:31:08 WARN GpuOverrides:
  !Exec <BatchScanExec> cannot run on GPU because not all scans can be replaced
    !Input <AvroScan> cannot run on GPU because unsupported data types TimestampType [_c0], DateType [_c1] in read for Avro
    @Expression <AttributeReference> _c0#396 could run on GPU
    @Expression <AttributeReference> _c1#397 could run on GPU

It seems that we don't support date/time in Avro yet. So I'm fine with closing this and we can reopen or file a new issue when it is needed.

@ttnghia Do we have a PR link this JIRA?

Yes, the config is checked since this PR: https://github.com/NVIDIA/spark-rapids/pull/9631.


Install version 3.4.0.rc testing

We are trying to install version 3.4.0 of metatron for testing. The problem is that the compilation does not work because it returns these errors:
[WARNING] npm WARN deprecated<EMAIL_ADDRESS>One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
[ERROR] npm notice created a lockfile as package-lock.json. You should commit this file.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of typescript@>= 3.3.0 || >= 3.6.0-dev || >= 3.7.0-dev but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of typescript@>= 3.3.0 || >= 3.6.0-dev || >= 3.7.0-dev but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><6.0.0 but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^4.0.0 but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
[WARNING] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
[INFO] audited 40597 packages in 22.604s
[WARNING] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
[INFO] found 21 vulnerabilities (12 low, 2 moderate, 7 high)
[INFO]   run npm audit fix to fix them, or npm audit for details
[ERROR]
I'm trying to download the final binary file since "mvn clean install -DskipTests" but I can't find it anywhere so I can't install metatron. Could you help me or know what the compilation failure might be?

@AlejandroITOP
fsevents is dealt differently in mac and other linux system. Linux system ignores fsevents whereas mac install it. As the above error message states that fsevents is optional and it is skipped in installation process.
You can run npm install --no-optional command in linux system to avoid above warning.

Even using the command that still does not work now I can not start the rpm run prod command.
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.4:npm (npm run build) on project discovery-frontend: Failed to run task: 'npm run prod' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :discovery-frontend

@AlejandroITOP
Could you provide node and npm version?


MML4 referral mapping update

Question : mmlPs:PrescriptionModule in referral appears one time?
Its occurrence is "?" in referral.adoc.

single occurrence is enough for refferal. Thank you.


[Firefox specific] Opening a tab without it in focus doesn't inject the css/js

When you open a ruqqus tab without it in focus (open link in new tab) it doesn't inject the css/js. Seems to be only happen on firefox, tried on opera and it worked as expected.
It only happens when it fully loads without focus, so if you focus on it right before it loads it works.
kinda funky bug ngl

Oh, wow, that's a crazy one. I'll look into it.

also i got it kinda wrong, if it starts loading (don't know at what point) it injects but if you "miss" that time and you don't have the tab on focus it just doesn't inject.

just found something new, it seems the extension (addon) itself doesn't load not js/css injection specifically.
also did some testing and no console error on the page itself, i think extensions run on background pages or something but i don't know how to open it so can't say there is anything there


feature/230 lqa data spinkelman

Critical Changes
Changes
Added IP security
Issues Closed
New Metadata
Unpackaged Metadata
Deleted Metadata
Testing Notes

Duplicate PR


GO CEO Join Notebook doesn't test Colab install

Conda colab can only be run in a colab notebook. See here for more information.


Added a better screenshot

Thanks so much for taking the time to raise this.
Making a change like this is quite a subjective decision. I'm not sure I agree that this improves the screenshot. It adds a lot of background noise and distracts from the screenshot. I don't feel like it adds any useful information or aesthetic.
I'm open to being persuaded though. @FabioRosado what are your thoughts?

I had a look at the picture in this PR. It looks interesting but I don't think it fits the opsdroid branding colour.
I don't think this is a needed change - mostly because most people don't use the desktop add that much. I appreciate the time and effort that it took you to create the screenshot, it does look cool!
Let us know if you think we should change our minds somehow 👍


refactor for python

leaning towards refactoring to python b/c  code for alexandria servers are configured and optimized for this.
Dependencies to be used...

flask

create new branch
git checkout -b issue/9
when done
git checkout master
git checkout -b ruby-archive make a change and push
git checkout master
git merge --no-ff issue/9
Could also use tags/releases to save a downloadable version of the ruby code
May want to do a git move to move ruby code to a separate folder
E.g.
git mv * api/ruby/

branch pyport is finished and solves this for current sqlite schema retrieves successfully & displays in same format


C# Unable to use Disconnect() with delegate Callable; gives "nonexistent connection" error

Godot version
v4.0.3.stable.mono.official [5222a99f5]
System information
Windows 10
Issue description
Using GodotObject.Disconnect() with a callable created from a delegate gives the following error:
E 0:00:01:0017   Godot.NativeInterop.NativeFuncs.generated.cs:332 @ void Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_ptrcall(IntPtr , IntPtr , System.Void** , System.Void* ): Attempt to disconnect a nonexistent connection from '<Node#26474448006>'. Signal: 'tree_exited', callable: 'Delegate::Invoke'.
  <C++ Error>    Condition "signal_is_valid" is true.
  <C++ Source>   core/object/object.cpp:1327 @ _disconnect()
  <Stack Trace>  Godot.NativeInterop.NativeFuncs.generated.cs:332 @ void Godot.NativeInterop.NativeFuncs.godotsharp_method_bind_ptrcall(IntPtr , IntPtr , System.Void** , System.Void* )
                 NativeCalls.cs:3541 @ void Godot.NativeCalls.godot_icall_2_412(IntPtr , IntPtr , Godot.NativeInterop.godot_string_name , Godot.Callable& )
                 GodotObject.cs:784 @ void Godot.GodotObject.Disconnect(Godot.StringName , Godot.Callable )
                 Main.cs:17 @ void Main._Ready()
                 Node.cs:1813 @ Boolean Godot.Node.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 Main_ScriptMethods.generated.cs:31 @ Boolean Main.InvokeGodotClassMethod(Godot.NativeInterop.godot_string_name& , Godot.NativeInterop.NativeVariantPtrArgs , Godot.NativeInterop.godot_variant& )
                 CSharpInstanceBridge.cs:24 @ Godot.NativeInterop.godot_bool Godot.Bridge.CSharpInstanceBridge.Call(IntPtr , Godot.NativeInterop.godot_string_name* , Godot.NativeInterop.godot_variant** , Int32 , Godot.NativeInterop.godot_variant_call_error* , Godot.NativeInterop.godot_variant* )

It's the same callable instance as previously given to Connect().
Using the += and -= operators work as expected if you save the delegate to an Action.
Since you must use Connect() to pass flags or specify the signal with a string,
there's no way to disconnect delegates which you'll often need for binding values.
Steps to reproduce
Create a main.tscn scene with this C# script:
// Main.cs
public partial class Main : Node
{
    public override void _Ready()
    {
        Action barf = () => GD.Print("BAR");
        //TreeExiting += barf;
        //TreeExiting -= barf; // OK

        var callable = Callable.From(barf);
        Connect(SignalName.TreeExiting, callable);
        Disconnect(SignalName.TreeExiting, callable); // ERROR
        foreach (var connection in GetSignalConnectionList(SignalName.TreeExiting))
        {
            GD.Print($"CONNECTION {connection}"); // Shows the connection that failed to be disconnected.
         I have the issue in my project, but the MRP was flawed. I'll post a new issue if I can narrow it down.


Release newest version to npm

The last time underscore was published to npm seems to be a long time ago (i.e. April).
I just ran into trouble when browserifying/babelifying an application because of this: https://github.com/jashkenas/underscore/commit/7fc15e5816dc02371517c4cb16a28e35f5b9a857
1.8.3 would tell me that root is undefined in the bundled file and throw at root._, when I pull from the github repo the build will be ok.
Could we get all this https://github.com/jashkenas/underscore/compare/1.8.3...master released to npm?

Ping @braddunbar, do you have npm access to Underscore?

To check see here.

A newer release won't likely be out for weeks or months depending on Jeremy's travel plans. You can however reference your npm dep to a commit hash. We'll track tasks for release in a dedicate issue.
"underscore": "jashkenas/underscore#616b1f8"


Cannot build the project due to invalid .pch file

Hi, I am trying to build the project but found the below errors.
error: input is not a PCH file: '/Users/kittisak/Library/Developer/Xcode/DerivedData/Mumble-dseistgcfzlkmifyiefqlrpdtbmm/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/6834873383108777343/CELT-0.7.pch.gch'

fatal error: file '/Users/kittisak/Library/Developer/Xcode/DerivedData/Mumble-dseistgcfzlkmifyiefqlrpdtbmm/Build/Intermediates.noindex/PrecompiledHeaders/SharedPrecompiledHeaders/6834873383108777343/CELT-0.7.pch.gch' is not a valid precompiled PCH file

I searched that file and this is its content.
//
// Prefix header for all source files of the 'CELT-0.7' target in the 'CELT-0.7' project
//

#ifdef __OBJC__
    #import <Foundation/Foundation.h>
#endif

I am using Xcode 13.7.
Could you suggest me how to fix them? Thank you.

Make sure you run
git submodule init
git submodule update

If you subsequently run into an issue where it complains about the PCH file being invalid, navigate to File > Project Settings and switch the build system to "Legacy Build System".


Docker Image for playing with DeltaLake

This pull request is an attempt to resolve issue #919.
This PR adds instructions in the example directory for a dockerfile.
Instructions on what the image is trying to do:
The base is derived from jupyter/minimal-notebook and it installs openjdk-8 and r-lang.
It also installs deltalake 1.1.0, and uses jupytext to convert all the sample python notebooks into example ipynb files.
spark-defaults.conf is also set to introduce delta jars and delta configurations.
The intent is after running the container you have a playground to start using delta, with some starter notebooks.
Go to examples:
cd examples

To build:
docker build -t delta-lake-playground:latest .

To run:
docker run -it -p 8888:8888 delta-lake-playground

Notes: This image uses python 3.9.x. Those are the only images provided by jupyter that are supporting both intel + arm based builds.
Access the jupyterlab instance via http://localhost:8888/lab?token=docker
Signed-off-by: Sri Tikkireddy<EMAIL_ADDRESS>

PR #1035 will provide a Docker and Binder deployment

@stikkireddy - are you going to take a stab at addressing the comments on this PR or should someone else pick up this work?

Have you looked at #1035?

In addition to @baumanab call out of #1035, I'm wondering if it would be helpful if we leveraged the proposed Spark docker per SPIP: Support Docker Official Image for Spark.

Yes, if it’s properties align with delta requirements. Misalignment has been a challenge that resulted in the custom dickefiles submitted in this PR.  If we can get official images that meet requirements, this will simplify things considerably.

On Sep 27, 2022, at 9:28 AM, Denny Lee @.***> wrote:

In addition to @baumanab call out of #1035, I'm wondering if it would be helpful if we leveraged the proposed Spark docker per SPIP: Support Docker Official Image for Spark.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.


Set webpack's compilation.warnings when glob-related options are used

R: @addyosmani @gauntface
Fixes #1380
Happy to iterate on the warning language.
This PR also includes updates to the existing test suite to ensure that warnings were not previously being set when they were not expected.

Coverage increased (+0.7%) to 88.991% when pulling ddf8d4e38b23ad9aec0396f931defbb7c97b9ec1 on webpack-glob-warnings into 807f67f088c0f9eee99264765346965f456273a5 on master.


Using mongo official image

What's implemented?
Using mongo official image
Is this feature guarded (auth needed)?

[ ] Yes
[x] No

Does it affect security?

[ ] Yes
[x] No

I'll create a new PR from a new branch


E - easy

#28

Hey. Thank you for contributing.
Can you delete the word easy and add some other word for both your PRs to be merged?
This is because Easy.json is already present in the repository.

Sure

De: Showndarya<EMAIL_ADDRESS>Enviado: sábado, 6 de outubro de 2018 01:12
Para: Showndarya/Hacktoberfest
Cc: AlefRib; Author
Assunto: Re: [Showndarya/Hacktoberfest] E - easy (#33)
Hey. Thank you for contributing.
Can you delete the word easy and add some other word for both your PRs to be merged?
This is because Easy.json is already present in the repository.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Showndarya/Hacktoberfest/pull/33#issuecomment-427544315, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AexsyTMM6vj5NcgkYwLCDP0YIKq-t2Fwks5uiC22gaJpZM4XLHHg.


bug: useNetwork's chain?.name returns "Chain 137" instead of "Polygon"

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
^0.10.14
Current Behavior
const { chain } = useNetwork();
console.log(chain?.name) // Chain 137

Expected Behavior
const { chain } = useNetwork();
console.log(chain?.name) // Polygon

Steps To Reproduce
import { useNetwork } from "wagmi";
const { chain } = useNetwork();
console.log(chain?.name)

Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
only Eth mainnet seems to return "Ethereum", other chains all return "Chain XXX" instead of the chain's actual name.

Make sure you add any Chains you are using in your app to configureChains otherwise wagmi will fall back to this format (since it doesn't know about the chain).

That does not solve the issue, I configured chains using configureChains and it still does not work.

import { arbitrum, mainnet, optimism, evmos, polygon, hardhat} from "wagmi/chains";

const chains = [mainnet, optimism, arbitrum, evmos, polygon, hardhat];
const { provider, webSocketProvider } = configureChains(chains, [
  walletConnectProvider({ projectId }),
]);

I definitely included the chains from official package and still does not work.

Please comment here with a minimal reproducible example and I will re-open the issue.

I'm running into the same issue as @hskang9, in order to reproduce @tmm, you can do so by running your wagmi-testing repository and try switching networks, the isTest you're doing before providing the configureChains is the reason for that happening.


Fix API review warnings for stream binder modules.

As title:
It's mainly about the java doc warnings.
This PR is only for these modules:

spring-cloud-azure-stream-binder-eventhubs-core.
Fix warnings in API-review page: https://apiview.dev/Assemblies/Review/cb6aadf3a4dd4c6d858f546f346e9b28

spring-cloud-azure-stream-binder-eventhubs.
Fix warnings in API-review page: https://apiview.dev/Assemblies/Review/75bcb52fc5c74dbcaa45847030d90f4b

spring-cloud-azure-stream-binder-servicebus-core.
Fix warnings in API-review page: https://apiview.dev/Assemblies/Review/01a60300646c499a8ca2527711ccfed0

spring-cloud-azure-stream-binder-servicebus.
Fix warnings in API-review page: https://apiview.dev/Assemblies/Review/c1573a0d793a4ea78ce3fa33c486fcce

spring-cloud-azure-stream-binder-test.
Fix warnings in API-review page: https://apiview.dev/Assemblies/Review/896198260f3547bba74499bae18e3e88

Please help to remove all author information in java docs of binder related classes.


Adding an example env file

In preparation for  issue raised in #131 I think doing this makes maintaining a list of keys easier and improves dev experience :+1:
Eventually we can also add GITHUB_KEY etc. to the example once key auth is implemented.

You are welcome to extend the instructions for the implementation using GITHUB_KEY.


Node throws errors while trying execute more than two page.evaluate() functions in the same method

Steps to reproduce
What is wrong?
I'm not able to execute three functions page.evaluate() in the same method due the errors. It's possible to execute one or two functions without problems, but node throws errors while I'm trying to execute three or more page.evaluate().
Tell us about your environment:

Puppeteer version: 1.4.0
Platform / OS version: MacOS
Language: Typescript
Node.js version: v9.4.0

What steps will reproduce the problem?
I have method Init being workaround for only synchronous constructors rule in Javascript. It gets values of properties of the object. Code:
    public async Init() {
        this.InstalmentsAmount = await this.api.evaluate(
            (selector) => document.querySelector(selector).children[0].children[0].children[0].textContent, this.selector)

        this.InstalmentsCost = await this.api.evaluate(
            (selector) => document.querySelector(selector).children[0].children[0].children[1].textContent, this.selector)

        this.InstalmentsInterest = await this.api.evaluate(
            (selector) => document.querySelector(selector).children[0].children[0].children[2].textContent, this.selector)
        }
    }

What is the expected result?
I should be able to execute three page.evaluate() in one method.
What happens instead?
I'm getting errors as below:
(node:10443) UnhandledPromiseRejectionWarning: Error: Protocol error (Runtime.callFunctionOn): Target closed.
(node:10443) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of anasync function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:10443) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:10443) UnhandledPromiseRejectionWarning: Error: Protocol error (Runtime.callFunctionOn): Target closed.
(node:10443) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of anasync function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:10443) UnhandledPromiseRejectionWarning: Error: Protocol error (Runtime.callFunctionOn): Target closed.
(node:10443) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of anasync function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 3)
(node:10443) UnhandledPromiseRejectionWarning: Error: Protocol error (Runtime.callFunctionOn): Target closed.
(node:10443) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of anasync function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4)

It works perfectly fine when I'm executing only two functions

@marek-siemieniuk this is not actionable without a script I can run locally to reproduce the problem. Feel free to re-open with a repro.
Also, please try updating to pptr v1.5.0 - we fixed a lot of bugs there, and maybe this one is fixed as well.

I can confirm this error is still happening with v1.5.0.

@aslushnikov I'm not able to reproduce the issue in the same way as before because I've changed the code a lot, but now (puppeteer updated to v1.5.0) it's possible to execute three page.evaluate() methods in one function.
cc: @jsdevtom


[merged separately] Remove ResetDefaultEventEngine

Now that it is a weak_ptr, there's no need to explicitly reset it. When the tracked shared_ptr is deleted, the weak_ptr will fail to lock, and a new default EventEngine will be created from within GetDefaultEventEngine

Thanks Craig, closing this.


Emit fields as text associated with span rather than span name

Depends on https://github.com/nagisa/rust_tracy_client/pull/86.

This is desirable because otherwise you cannot get meaningful statistics when tracing functions:
#[cfg_attr(
    feature = "tracing",
    tracing::instrument(level = "trace", skip(contents))
)]
fn create_files(
    num_files: u64,
    offset: u64,
    file: &mut FastPathBuf,
    contents: &mut impl FileContentsGenerator,
)

will turn into separate zones which can't be analyzed as a whole:

After this change, you get nice clean zones:

And the debug data is still present:

Of course as a bonus we save an allocation and formatting time.

Conversely, it is commonplace in tracing to use KVs extensively to construct semantically distinct spans, to the point where message field is omitted entirely (in which case after your PR we're looking at combining multiple spans that have no business being combined.)
Even in your case I would possibly see create_files{num_files=1000} as having meaningfully distinct performance characteristics compared to create_files{num_files=10000}, to the point where I might be interested in in having the two be separated in order to aid insights between the different sizes of batches. Unfortunately tracy does not provide tools to aid in such investigation out of the box. It is either the one extreme we have implemented right now, or the other extreme that your PR suggests (it is also what has been implemented in the past way back.) These kinds of considerations unfortunately only serve to highlight the many different ways where tracing’s view of… tracing is just much more complex than what tracy is willing to accommodate.
That said, I don’t disagree that in some applications the suggested rendition might be preferable, but I suspect it will need to be a setting/option to land, rather than a sweeping change as proposed.

Great points, you're absolutely right that the current behavior is still desirable. I went ahead and added a flag at the Layer level. This is somewhat unfortunate in that you can't decide per span whether or not you want combining, but having a layer level default is still useful and so if we do figure out how to do per span flags that feature will be in addition to this one.


Support for bolt+routing protocol

Supporting a Neo4j Causal Cluster (https://neo4j.com/docs/operations-manual/3.3/clustering/causal-clustering/introduction/), support for retrieving routing tables using bolt+routing is needed (https://neo4j.com/docs/developer-manual/3.3/drivers/client-applications/#_routing_drivers_bolt_routing) (https://neo4j.com/docs/developer-manual/3.3/terminology/#term-bolt-routing-protocol).
I was going to implement cluster support as a part of the higher-level driver I built on top of this library (https://github.com/AO-StreetArt/NeoCpp).  However, after some research, the architecture of Neo4j clusters makes the routing tables accessible from a Core Server, which should be utilized in order to bring cluster support in line with official drivers.
As far as I can tell, the best way to use them is retrieving those tables using bolt, and then using them with a load balancing strategy (example https://github.com/neo4j/neo4j-python-driver/blob/1.6/neo4j/v1/routing.py).

Hi @AO-StreetArt,
As you've noted, the bolt+routing in neo4j is based on:

Connecting to a "core" server using BOLT
Sending a query (stored proc call) and retrieving the result table, which contains host+port, role, etc, for other neo4j servers in the cluster.
Disconnecting from the "core" server.
Establishing connections to appropriate servers from the list, based on the queries presented.
Updating/maintaining the list of known neo4j-servers whenever connections fail, etc.
???

Thus far, neo4j-client has just focussed on implementing the bolt protocol and handing everything needed for establishing a connection to a server, sending it queries and obtaining results, leaving the higher level details, like determining server addresses, to the developer consuming this library.
However, there's no reason support for this "higher-layer" of interaction couldn't be developed in this codebase and made available as an additional API. I just haven't had the time or motivation to do so myself :) Happy to discuss and help guide anyone interested in implementing this.
Cheers,
Chris

Thanks for the reply @cleishm , I'd be happy to implement this, would love your thoughts.
I think it makes sense to allow the consumer to handle the higher-level details, with one caveat.  The actual communication with the core server to retrieve the result table.  To me, it makes sense conceptually that libneo4j abstracts away the BOLT protocol, with other implementation details left to the consumer.
With that in mind, basically the changes to libneo4j would basically entail supporting access to the return results from the query "CALL dbms.cluster.routing.getRoutingTable({context})", as well as figuring out how to access the routing context to pass in (still need to figure out exactly where that comes from).
I don't think that libneo4j should really do much beyond that.  What do you think?

I had a couple of more requests for this lately. Shall we discuss some more and consider some work on it?

Sounds great.  Are you aiming to enable full routing support within the command line client, or just provide for retrieving the routing table?
We can get on IRC/Slack to discuss at some point if you'd like.

Hey @AO-StreetArt: Full support, whatever that means ;-) Retrieving the routing table can already be done: it's just a cypher query to a stored proc (which is what makes it Neo4j specific, rather than anything to do with the bolt protocol).

Sorry for the delay, I took some time today to think about this and pulled together a preliminary design.  A few notes before I dump what I'm thinking:

I've mostly been working with c++11, so my C API design may not be perfect.  Please comment where you think it could be improved.

This is the design for library support for the routing protocol.  Of course, once this is done, the command line client will also need to be extended to use the new functionality.

I tried to base the design on the Python driver (https://github.com/neo4j/neo4j-python-driver/blob/1.7/neo4j/v1/routing.py)

Connection Pool responsible for maintaining neo4j_connection's

Support bolt+routing, should same connection pool support bolt as well?

End user can utilize neo4j_connection directly, or make calls to neo4j_connection_pool to retrieve
connections for each transaction.

Pool is likely array of structs to store data, functions to access (inline with current API)

Pool should be thread-safe (what synchronization primitives to use?), or
are clients expected to synchronize calls to retrieve connections?

Configurable routing strategies with round-robin default

Function Pointers

neo4j_routing_strategy - define functions which select a connection from a list
-- Function needs to be passed neo4j_connection_pool to access pool state

New structs

neo4j_connection_pool

New methods

int neo4j_connection_pool_init(neo4j_connection_pool *pool)
neo4j_connection* neo4j_retrieve_connection(neo4j_connection_pool *pool, neo4j_routing_strategy *strategy)
int neo4j_release_connection(neo4j_connection_pool *pool, neo4j_connection *connection)
int neo4j_release_connection_pool(neo4j_connection_pool *pool)
int neo4j_round_robin_routing_strategy(neo4j_connection_pool *pool)

neo4j_retrieve_connection logic

Update Routing Table
-- Retrieve routing table from Neo4j Cluster Manager node
-- Compare to existing connections, add/remove as is necessary
-- May involve releasing existing connections, not creating new ones
Assemble list of available connections, only those currently not in use
Call neo4j_routing_strategy to retrieve connection info
Generate neo4j_connection, if not existing, store in array of active connections, return

neo4j_release_connection logic

make connection available to be returned on another request
do not release actual connection itself

neo4j_release_connection_pool logic

Release all active connections

Hi @AO-StreetArt,
Thanks for making this initial foray!
I think this sounds like a good initial scope. My only comment is that I'd prefer not to expose it using a name like "connection pool", as that feels like an implementation detail. I'd probably just call it a "driver", from when you can start a session (i.e. obtain a connection) with a server.
We can also avoid the neo4j_release_connection method by overloading neo4j_close so that it returns to a pool rather than actually closing. I use OO constructs in many parts of the codebase for doing this (e.g. neo4j_close_results), and it wouldn't be hard to do the same here.
By doing that, we'd make it such that it wouldn't matter if the connection was obtained via a driver interface, or using neo4j_connect(...) directly - usage after that point would be the same.
Cheers,
Chris

Hey!
Before you get too far ahead, it'd be good to share your code and get some feedback. I'd hate to ask to rework a lot after you'd written a significant amount. Do you have a branch you're working to? Can you do some incremental steps?
As for the specific question, I agree you'll need to differentiate the type of connection you need. However, rather than embed that in the function name, I'd follow the previous statement: make it a "type" argument. In this case, I'd use an int and add a couple of #defines that bitmask together, so you can retrieve any connection with a type that matches that mask.

(also, it's not "retrieve". It's just "connect". That it might be an already open connection should be opaque to the caller.)

Here's the API I'd suggest:
neo4j_driver_t *driver = neo4j_driver("bolt+routing://....", config, flags);
neo4j_connection_t *connection = neo4j_session(driver, NEO4J_WRITE_SESSION);
neo4j_result_stream_t *results =
            neo4j_run(connection, "RETURN 'hello world'", neo4j_null);

(obviously with error handling in addition)

I have a fork that I'm working on, but not much coding done there yet.  I'm still trying to get a feel for the required steps by playing with an actual cluster.
You can find my docker-compose.yml file to start a Causal Cluster here:
https://gist.github.com/AO-StreetArt/8dd744b9acdf3a9458006ed50abc899e
You can find a basic script which uses libneo4j-client to view the routing table here:
https://gist.github.com/AO-StreetArt/047a2b254e5e1f0f3ca685fe1a03dbfc
I like the API you outlined, and I'd be happy to do some incremental work and let you review.


Add colorization of expressions

The current colorization here is designed so that it affects all .json and .jsonc files - therefore it has to be careful to only change the colorization of actual ARM template files. This is done by using injection to add rules to the built-in JSON/JSONC rules that detect the ARM schema and switch to our grammars if it's found (see detect-arm.injection.tmLanguage.json). This will go away when we switch to using our own language ID.
The change in tests from asdf -> asdg is simply because I use asdf as an easy keyword to search for UNDONEs while I code so I keep finding these. :-)
Known issues:

Currently while typing in a function call, you get red until you enter the parentheses. Working on changing that because it's annoying.
Having tested much with multi-line
Could use more testing while typing an entire expression

I like the contrast between "[ and resourceGroup and wish variables had a similar amount of contrast with "[. Perhaps if "[ was always the same color as "Microsoft.Network/virtualNetworks"?

Unfortunately I don't have that level of control - I've only got so many scopes that are actually targeted by the current themes (and the themes vary in their contrast).  I hesitate to use the same color as "Microsoft.Network/virtualNetworks", because that's the normal string color, and Brian and I like that expression strings stand out as being different.  But I'll put this in the list to consider improvements after we've played around with it more.
Thanks!


Add an error message when failing to find a build branch to publish

Change-type: patch

@balena-ci I self-certify!


[CORE] Add custom cost evaluator for optimize buildSide of shuffled hash join

What changes were proposed in this pull request?
Split from #6093 .
Add custom cost evaluator for use the smaller table to build hashmap in shuffled hash join.
How was this patch tested?

cc @zhztheplayer @ulysses-you thank you.

Thank you for review. @ulysses-you @zhztheplayer


Enhancement - functions should specify OS constraints

Expected Behaviour
Deploying a function on a mixed-OS cluster should be possible - where a Windows container is scheduled correctly.
Current Behaviour
The task will be scheduled randomly - possibly on a Linux host.
Possible Solution
Add a default constraint to Linux and allow this to be overridden in the deploy function endpoint. A change to the CLI may also make sense later down the line.
Checkpoints:

encompasses the RESTFul schema

Schema https://github.com/alexellis/faas/blob/master/gateway/requests/requests.go#L7

Includes an update to the swagger API

Covers both Kubernetes and Swarm

I can try and take on this issue :)

I think @rgee0 started work on this.. is that still in-progress?
@glyif thanks very much for the offer of help, much appreciated. Can you get in touch with your email address for an invite to Slack?

@alexellis my email is<EMAIL_ADDRESS>:)

@rgee0 @glyif what's your bandwidth like for this week?

In lieu of this being completed #160 makes the default experience better by ensuring Linux containers are scheduled on Linux nodes.

Now available in the FaaS-CLI by passing --constraint or using a constraints element for a function. @glyif @rgee0 fancy writing a quick guide/blog?


updated dependencies to the latest version

:+1: Thanks!

that's quick :) :+1:

Published the package. Updated dependencies in the nuspec file to use ranges instead of specific versions, that should fix the dependency issue.

ok great!


New 2.0 branch

Since we're now on 1.0 and already have some PRs which are not compatible with the current version, we should make a 2.0.0 branch which only contains features which will be merged once 2.0.0 is ready. The current master branch would be for all 2.X.X features which are little changes + backwards compatible

You guys would rather need a separate release branch. You know Sourcetree and gitflow? Those two make versioning a piece of cake. :)

True, using the gitflow workflow in other projects with success (you don't need SourceTree for that, works just fine manually =) ). Did the necessary steps.

Freak ;-)

TortoiseGit ;)

Yep great tool. Even better than Sourcetree for certain more in-depth tasks. However I like how you can manage all repos/projects on a single page and how it collaborates with BitBucket. Give it a shot. Both are free of charge. :)


Update iceberg-spark to use HiveTables

This PR enables support for HiveTables in IcebergSource and resolves #8.

@Parth-Brahmbhatt @rdblue

@aokolnychyi, nice work! It is ready other than the connection problem. I think we need to add a static cache to avoid creating too many HMS connections.

@aokolnychyi, I merged #240, so could you rebase and update this to use HiveCatalog?

@rdblue @rdsr ready for another review round.


Adds tokengated-storefront example

WHY are these changes introduced?
After the build a tokengated storefront tutorial series shipped and a tweet was shared about the tutorial, I was asked by @benjaminsehl to include this example in the /examples directory. I thought about adding a submodule to the repository, but it makes the most sense to include the example in this repository instead of keeping it as a remote repository or as a submodule.
HOW to test your changes?

I don't believe any testing is necessary for these changes as it's adding an example. However, if you would like to run through the tutorial and set up a gated storefront to test the implementation feel free 🙂
Post-merge steps

[ ] Update shopify.dev references to gated-hydrogen-example repository to reference the example directory added in this pull request.

Checklist

[x] I've read the Contributing Guidelines
[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[ ] I've added a changeset if this PR contains user-facing or noteworthy changes
[ ] ~I've added tests to cover my changes~ N/A
[ ] ~I've added or updated the documentation~ POST-MERGE

Moving example to awesome-hydrogen since this example makes use of the unstable api version.


Not really an issue, but  a question.

My R9 280 recently died and I can't use waifu2x anymore, I have an Nvidia Quadro FX 580 laying around here but  when I try to upscale something using this video card waifu2x crashes.. My question is, is this GPU incompatible with Waifu2x libraries? (probably it is) if yes, can you make it compatible (or tell me a way to do this)? . Please.
I wasn't expecting this, (this video card is 1 year and 3 months old)

The issue is, that this build has no nVidia support (as I have no nVidia card)
And what do you mean by waifu2x libraries?

You remember that i changed some files and making possible to use waifu2x through koroshell's interface? I was thinking about downloading OpenCV 2.xxx.dll and pasting on the folder and see if it works.
So it's impossible to make this compatible with nVidia video cards? I've seen a waifu2x build CUDA compatible, but the minimum requeriments are an GPU compatible with GPU Computing 3.0.
My R9 280 have OpenCL 1.2 support and OpenGL 4.5 support.
My nVidia Quadro has OpenCL 1.0 support and OpenGL 3.3 support.

You should switch to waifu2x-caffe since it have much faster CUDA speed and use newer model with improve both speed and quality: https://github.com/lltcggie/waifu2x-caffe
And nVidia isn't update OpenCL for a very long time ago so it much slower than AMD GPU

Ok the page it says: requeriment:GPU computing 2.0, which I belive it's CUDA 2.0.
In short, it's not compatible with my current GPU. I've tried making it work in the past ironically because I was concerned about the lifespan of my R9 280.

You can not use OpenCV 2 with this build. use max20091's build, i switched to v3 in mine, for nVidia support, use caffe like max said its using a newer model too

Both me and DeadSix don't use nVidia GPU so we don't build any version that include CUDA
So just use OpenCL instead :)

As i said:
lltcggie CUDA Version dont work.
Your version dont work.
The version by Max 20091 dont work too.
Can you guys explain me why i cant use OpenCL with this GPU even though it has OpenCL support?

@GiRaFa-SM It's probably because I did not compile it with the nvidia SDK, I have no idea, I just can't test it without an nVidia GPU, if someone with cmake & c++ knowledge wants to fix it, he can just add a pull request and ill merge it in.

Nope, it just shows "scaling 1x, scaling 2x" and seconds after this it just shows a pop up saying that the applicaton stopped working. Yes, no errors, just FC.
Can i locate logs of this somewhere on my system?

@GiRaFa-SM its just a crash, I just wondered if it would say something specific.
Can you just try building it yourself with the nvidia sdk? https://github.com/DeadSix27/waifu2x-converter-cpp/blob/master/BUILDING.md

Sorry for the delay, but i have some doubts..
nVidia doesnt have a OpenCL/GL toolkit, they have an CUDA Toolkit, i really need to download CUDA Toolkit or i need to download just the tools you provided in the link above and try to compile? (even tho looks like this are tools meant to be used on AMD video cards)
I'm asking because my internet isnt that fast and download the Visual Studio will take some time for me.
Thank you for the patience, as you see my english isnt great and sometimes its complicated to transmit my messages.

the guide is fully meant for AMD; yes not nVidia, but based on the guide you can try out using the (in this case apparently CUDA toolkit, (which I hope contains OpenCL libraries)) to compile it.

HI, its been 4 months? I wanted to give a look on this again but because of reasons i didnt. I have few questions..
I tried to compile what you sent me above through command line, no luck, tried with CMake and got these errors:
The C compiler identification is MSVC 19.10.25019.0
The CXX compiler identification is MSVC 19.10.25019.0
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
CMake Warning (dev) at CMakeLists.txt:22 (link_directories):
This command specifies the relative path
OFF/lib

as a link directory.
Policy CMP0015 is not set: link_directories() treats paths relative to the
source dir.  Run "cmake --help-policy CMP0015" for policy details.  Use the
cmake_policy command to set the policy and suppress this warning.
This warning is for project developers.  Use -Wno-dev to suppress it.
Looking for C++ include opencv2/opencv.hpp
Looking for C++ include opencv2/opencv.hpp - not found
Adding OFF/includeopencv2/opencv.hpp not found, you can try compiling with OVERRIDE_OPENCV set to true then make sure to set OPENCV_PREFIX as well
Looking for CL_VERSION_2_0
Looking for CL_VERSION_2_0 - not found
Looking for CL_VERSION_1_2
Looking for CL_VERSION_1_2 - found
Found OpenCL: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v8.0/lib/Win32/OpenCL.lib (found version "1.2")
Found CUDA: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v8.0 (found version "8.0")
CMake Warning at CMakeLists.txt:68 (message):
VC14 found, which is NOT FULLY tested.
CMake Warning (dev) at CMakeLists.txt:90 (link_directories):
This command specifies the relative path
OFF/x86/vc14/lib

as a link directory.
Policy CMP0015 is not set: link_directories() treats paths relative to the
source dir.  Run "cmake --help-policy CMP0015" for policy details.  Use the
cmake_policy command to set the policy and suppress this warning.
This warning is for project developers.  Use -Wno-dev to suppress it.
Configuring done
Generating done
I'm using VS Community 2017
Using nVidia SDK 8.0
Using OpenCV 3.2.
What am i doing wrong? Also, nVidia Driver didnt detected VisualStudio Integration (Nsight) even though i have the latest version installed on my sistem ( I got a Quadro 600)
Thanks.

@GiRaFa-SM Hi, GiRaFa-SM
You have to follow BUILDING.md to build this project.
It seems to be you didn't set proper OPENCV_PREFIX.
OPENCV_PREFIX is has to be set to your OpenCV 3.2's Directory.

@GiRaFa-SM Please report back if @YukihoAA 's PR fixed it.

YukihoAA was right, i wasnt setting the OpenCV prefix correctly.
Now i get these errors:
The C compiler identification is MSVC 19.10.25019.0
The CXX compiler identification is MSVC 19.10.25019.0
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
Check for working C compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe
Check for working CXX compiler: C:/Program Files (x86)/Microsoft Visual Studio/2017/Community/VC/Tools/MSVC/14.10.25017/bin/HostX86/x86/cl.exe -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done
Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Looking for C++ include opencv2/opencv.hpp
Looking for C++ include opencv2/opencv.hpp - not found
Adding I:/Waifu2X/opencv/includeopencv2/opencv.hpp not found, you can try compiling with OVERRIDE_OPENCV set to true then make sure to set OPENCV_PREFIX as well
Looking for CL_VERSION_2_0
Looking for CL_VERSION_2_0 - not found
Looking for CL_VERSION_1_2
Looking for CL_VERSION_1_2 - found
Found OpenCL: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v8.0/lib/Win32/OpenCL.lib (found version "1.2")
Found CUDA: C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v8.0 (found version "8.0")
CMake Warning at CMakeLists.txt:68 (message):
VC14 found, which is NOT FULLY tested.
Configuring done
I believe this has something to do with the fact that CMake isnt detecting OpenCV binaries, right?

@GiRaFa-SM It seems you didn't Pull new cmake scripts from master brench. My PR#13 will show "Found OpenCV" message if you choose proper OpenCV directory. My new scripts will not show "VC14 is not fully tested" message also.

and You have to run msbuild on Visual Stuio X64 Native cmd Tools which is not X86 cmd Tool (this is might be not related to your problem, this is just a tip)


data migration from localStorage to browser.storage (chrome.storage)

Add migration script from localStorage to browser.storage (chrome.storage)
Set/Get value from browser.storage
Add storage permission
Add activeTab permission
Add "https://github.com///pull/*" permission
background persistent

refs #357
refs #334
fixes #361

background persistence will fix #336


Table component docs overflow container

Describe the bug
Per this issue in the rimble-storefront repo, the Table example in the docs and one in the Do's & Dont's overflows its container at smaller viewports.
It was decided that it was out of scope for the rimble-storefront repo and should be brought over to here.
To Reproduce
Steps to reproduce the behavior:

Go to https://rimble.consensys.design/components/rimble-ui/Table
Reduce your browser window consistently to see the bug.

Expected behavior
The Table should be set to overflow-x: scroll in order to scroll horizontally when in danger of overflowing its container.
Padding should also be made responsive, with smaller amounts of padding on all table headings and cells at smaller viewports to avoid vertical text.
Screenshots
https://user-images.githubusercontent.com/797290/68433312-72604500-0173-11ea-86d6-56106783bb36.png
https://user-images.githubusercontent.com/797290/68433365-8e63e680-0173-11ea-9ced-17895fc66275.png
Rimble UI Version

0.7.1 (latest)

Desktop (please complete the following information):

OS: MacOSX 10.13.13
Browser: Chrome
Version 78

Thanks for submitting @as-dr. Sounds like this is related to #406 in our backlog.


Double-check example on the DNA/substitution page.

The DNA/substitution page lists the following question and answer:

"How can I shorten the descriptions of SNPs in a manuscript?"
Publications reporting linkage or association studies often use a range of different markers/SNPs. Such publications should contain at least once an unequivocal description of all markers used linking them to a reference sequence, preferably a genomic reference sequence. When this has been done, simplified descriptions can be used like
- NM_004006.1 3G>T, using a GenBank coding DNA reference sequence
- GJB2 76A>C, using a HGNC-approved gene symbol as reference
- rs2306220 T>C, using a dbSNP-identifier as a reference
- DXS1219 CA[18];[21] (or AFM297yd1 CA[18];[21]), using a marker DXS1219 (AFM297yd1) as reference

Shouldn't the top two suggestions be NM_004006.1:c.3G>T and GJB2:c.76A>C, respectively? Should we really recommend notations without prefixes?

Although this does not answer the question (the description is not short), my top suggestion would be:
NC_000023.11(NM_004006.3):c.3G>T,
as it conveys both the reference sequence used to find the variant in the first place, as well as a user friendly projection on the transcript of interest.
I would discourage using a bare transcript identifier as a reference, unless this reference was used to call the variant in the first place. There are multiple issues when converting to and from these reference sequences, some of which cannot be solved by mapping or using MANE transcripts.
The other three suggestions I do not recognise as valid HGVS descriptions as they violate the following rule:

a sequence identifier must only ever identify one reference sequence, and the sequence referred to by a sequence identifier may not be deleted or changed

Although this does not answer the question (the description is not short), my top suggestion would be:
NC_000023.11(NM_004006.3):c.3G>T,

I'm afraid this is a completely different subject, as this would require a significant part of the HGVS nomenclature documentation to be adapted, and, most importantly, we need to figure out this discussion: https://github.com/HGVSnomenclature/hgvs-nomenclature/discussions/4

The other three suggestions I do not recognise as valid HGVS descriptions as they violate the following rule:

a sequence identifier must only ever identify one reference sequence, and the sequence referred to by a sequence identifier may not be deleted or changed

The Q&A that I copied here is about shortening descriptions where the reference sequence has already been mentioned elsewhere in the text (for tables, for instance). So there is already a reference sequence defined; it's just not connected to the variant description everywhere. This is, as far as I understand, and as the answer shows, acceptable. The question is just whether I should add the prefix there, because it's removed and I don't think removing the c. is a good idea, ever.

we need to figure out this discussion: #4

Agreed.

The Q&A that I copied here is about shortening descriptions

The answer could be that there are no possibilities for this within the HGVS nomenclature. I would not mention these seemingly random suggestions at all.

Regarding Jeroen's question, please note this part:
"Such publications should contain at least once an unequivocal
description of all markers used linking them to a reference sequence,
preferably a genomic reference sequence."
So based on this, whatever description is used after this, a correct
HGVS description will be in the paper. I therefore think this Q&A is OK.
However, when we think the example is debatable, I suggest we keep it
simple and delete this Q&A.
Johan
On 17/01/2024 11:22, Jeroen F.J. Laros wrote:

we need to figure out this discussion: #4
<https://github.com/HGVSnomenclature/hgvs-nomenclature/discussions/4>

Agreed.
The Q&A that I copied here is about shortening descriptions

The answer could be that there are no possibilities for this within the
HGVS nomenclature. I would not mention these seemingly random
suggestions at all.
—
Reply to this email directly, view it on GitHub
https://github.com/HGVSnomenclature/hgvs-nomenclature/issues/135#issuecomment-1895510040, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6EB73OLLU7P4YWIAUAHCDYO6Q47AVCNFSM6AAAAABB5IYSUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJVGUYTAMBUGA.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have seen the paragraph you mentioned, so perhaps this is a bit of hair splitting on my part, but I think we should focus on the HGVS nomenclature in these pages. So removing non-HGVS suggestions of variant descriptions would be preferable in my opinion.

So removing (all) non-HGVS compliant suggestions for variant descriptions would be preferable in my opinion.

I'm afraid that if c.3G>T in the context of a reference sequence which is not directly physically attached to the variant description (i.e., NM_004006.1:c.3G>T) is no longer considered HGVS compliant, then half the examples in the documentation should be updated. I can't find any requirement to directly attach the reference sequence to all variant descriptions, and we often don't in the documentation. I just see the requirement that the variant descriptions should be in relation to a reference sequence. Not requiring the physical attachment and endless repetition of the reference sequence in texts allows providing the reference sequence in, e.g., the header of a table, and variant descriptions (c.3G>T etc) in the table body.

I understand that it will become cumbersome if we have to use full descriptions in all of our examples. Perhaps we should distinguish between partial descriptions (like c.123del) and non-HGVS suggestions (like DMD:123del). My comments above apply to the latter.

I opened this issue, reporting the lack of prefixes. For some reason, the discussion became about reference sequences. My suggestion was to simply change GJB2 76A>C to GJB2:c.76A>C or, also fine, "GJB2 c.76A>C". I think we now agree that the latter is acceptable, right? Because in that case, I'll fix the page and close this issue.

I would say that c.76A>C or even 76A>C are acceptable partial descriptions in running text, provided the context is made clear and full descriptions are provided elsewhere. I would also have no problem with other solutions like a lookup table to name variants, as long as a link to the full descriptions can be made.
My problem with the given suggestions is that they hint to a hidden nomenclature; there seems to be a reference, alluded to by the phrase "using a ... reference", followed by an HGVS-like variant notation. Adding more syntax like coordinate systems and colons will only strengthen this idea.
Perhaps an adaptation of the first paragraph of this comment could serve as an answer to the original question, following Johan's suggestion is also fine with me.

the answer was, and remains, when the official HGVS description is
given, anything description format may be used to "shorten the
descriptions of SNPs in a manuscript".
On 17/01/2024 20:59, Jeroen F.J. Laros wrote:

I would say that |c.76A>C| or even |76A>C| are acceptable partial
descriptions in running text, provided the context is made clear and
full descriptions are provided elsewhere. I would also have no problem
with other solutions like a lookup table to name variants, as long as a
link to the full descriptions can be made.
My problem with the given suggestions is that they hint to a hidden
nomenclature; there seems to be a /reference/, alluded to by the phrase
"using a ... reference", followed by an /HGVS-like variant notation/.
Adding more syntax like coordinate systems and colons will only
strengthen this idea.
Perhaps an adaptation of the first paragraph of this comment could serve
as an answer to the original question, following Johan's suggestion is
also fine with me.
—
Reply to this email directly, view it on GitHub
https://github.com/HGVSnomenclature/hgvs-nomenclature/issues/135#issuecomment-1896594760, or unsubscribe https://github.com/notifications/unsubscribe-auth/AD6EB75X5AZRFTR2SHQ4FETYPAUS7AVCNFSM6AAAAABB5IYSUKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJWGU4TINZWGA.
You are receiving this because you commented.Message ID:
@.***>

That sounds like a perfectly fine answer to me.


Knowledge Build-up 'Gardener Components'

Description
We have to invest into building up knowledge in the team around the Gardener Components.
Good starting points should be:

https://gardener.cloud/documentation/concepts/architecture/ and
https://gardener.cloud/documentation/concepts/core-components/

This is relevant in general to get up-to-speed with the core concepts of the Gardener, and especially if we want to start building landscaper-components for those Gardener Components.

We enabled ourselves as much as possible regarding gardener components. Closing this issue.


Add caching to tests

There are some opportunities to cache the tests in the CI. This should save some 1.5 minutes off the tests.
I also noticed that the CI runs tests twice in a PR, because it is configured to run on every push as well as on a PR. We can scope this to master to avoid it.

[x] Python installation
[x] SOCRATES compilation
[x] Avoid running the same tests twice in pull requests

There is still a significant penalty for downloading the data files. Might be worth caching the FWL_DATA directory too.


Modular - Upgrade to Elm 0.17

Just playing with the new Elm, hope you enjoy.

So, the 'modular' structure is almost just like pods in ember, whereas the structure on master is the 'classic' mvc ember/rails style structure. Because ember is all about reconciling differences, the project is moving towards this project layout which unified the good parts of each strategy: https://github.com/dgeb/rfcs/blob/module-unification/text/0000-module-unification.md
I think I should make a version using this unified module layout and see how it goes (Anyone interested in pairing maybe?)
Footnote: to see this pattern of change, I had to navigate to the Files Changed tab, find the "42 files changed" dropdown, and search 'Control', 'Main', 'TaskList' and 'Task' to see how these 4 central objects' model/view/controller code is being re-arranged.

Once we get this structure figured out for elm's case, and it looks good, we should like, make a proposal for elm

So, on second thought, would one of you guys be interested in pairing with me to try using this unified module layout?

So I have a small handful of changes inspired by ember to make for a more generic project layout with more generic names (also got rid of this nasty "TodoApp." prefix everywhere) https://github.com/rogeriochaves/structured-elm-todomvc/pull/4
I haven't moved very close to the new ember layout, however. I'm not sure what's the easiest way to move towards that layout, or if it even makes the most sense. Really, I think we'd be talking about mixing these two layouts in this simple way: Keep all Models in the Models folder, just like the classic structure (this projects master branch) and then have the rest of the project follow the Modular structure, references models in the top level Models directory.


[VS Code] Starting collaboration session: Invalid root scheme: vsls, expected 'file'

Error:
Starting collaboration session: Invalid root scheme: vsls, expected 'file'
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.1182

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.31.1

platformName
Linux

platformVersion
4.9.0-8-amd64

Hey @shethmanan, thanks for reporting the issue! Could you share some details to get it fixed, - is the error blocking you from having a Live Share session or it just pops up without a big impact? Is it consistent, e.g. do you have rough steps that will help us to reproduce it?
Thanks!

Closing this as a duplicate of #1568.


Making JS mentions Node-specific

Also added a link to our security / data handling policy

:tada: This PR is included in version 0.45.6 :tada:
The release is available on:

v0.45.6
GitHub release

Your semantic-release bot :package::rocket:


Cache hit/miss should be visible in hook context

I might just not be able to find it, but I think that in a hook, there is no way to check if results come from the cache or not?
For debugging and profiling, it is valuable to know this...

You're right. I think this is not possible atm. Are you up to add a PR for this?

I am not yet really up to the task, I am afraid... Hopefully I can learn more and be back with a Pull Request ))


[!] The 'Pods-TTCore' target has frameworks with conflicting names: crashlytics.framework and fabric.framework.

[!] The 'Pods-TTCore' target has frameworks with conflicting names: crashlytics.framework and fabric.framework.

I'm getting this during the pod install phase, how can I debug this?

It's because the generated fabric framework is duplicated with the framework it contains natively. I think there should be an improvement.
Workaround: add :binary => false to fabric


Lot's of retry_later errors, how to increase maximum sessions and pipline size?

I see a lot of retry_later errors in production.
Searching a bit, I found that I need to set maximum number of sessions and pipeline size (right?).
How can I set that using HTTPotion? I found the api to do that in ibrowse here, but I'm not sure where to put them.
Also, those functions let me increase it for a specific domain/port. How can I set globally?

There's an example of passing ibrowse options in the readme:
HTTPotion.get "https://check-tls.akamaized.net", [ ibrowse: [ ssl_options: [ versions, [:'tlsv1.1'] ] ] ]

And you can use the default_ibrowse config option to set them globally:
https://github.com/myfreeweb/httpotion/blob/c79314b91df2cc8e43835b509efd682820d87fb4/config/config.exs#L5

Using config :httpotion, :default_ibrowse, [max_sessions: 5000, max_pipline_size: 5000] in my config file.
Unfortunately, this does not fix my retry_later errors.
Am I using the options right?

Yes, that should be how you set them.
max_pipline_size is a typo though.
You can also try direct mode. Or throttle your requests with something like ex_rated.
references: #21 https://github.com/cmullaparthi/ibrowse/issues/147

I don't get how direct mode works. I spawn a worker for myself, and use it whenever I want. Right?
Does this worker have a life span or something? How do I know when it is working, or I should spawn another one?
Also, can I somehow not use pool or sessions or anything from ibrowse or HTTPotion? I already have a pool of workers, and I am load balancing my requests (and parsing responses) between them. It would be good if I can somehow bypass session and pipeline limit here.

not use pool or sessions

That's what direct mode does. It skips ibrowse's pool.
You probably need to spawn a worker on every request.


Incomplete extraction

Incomplete extraction

Useiden tiedostojen epätäydellinen poiminta vain yhdellä rivillä

Are you sure the target rpy file has enough extractable contents to extract
Or can you upload the gameUI.rpy file for me to have a test
As I mentioned on the last  FAQ
It depends on the original code , extraction may not completely covered if the original code is not quite translation-friendly
To avoid extra useless extraction , the extraction function in this tool will not extract sentences match the following style :
the length of sentences (space and special synbol will be counted as zero length)  lower than 8
for example :
"I know [special symbol]"

the actual effect content is
Iknow

the length is only 5 , so it will not be extracted by the extraction from the tool

Besides the contents in ConditionSwitch() will also not be translated due to switch code may contained in it

Yes

Yeah, more than a folder. Folders can extract duplicates and cause errors. A single rpy. It's the source file that's being extracted. Not the default tl file.


Support runtime-sized arrays

Let's say I have the following WGSL code, which is then used by a compute shader:
struct Data {
    some_param_1: u32,
    some_param_2: u32,
    data: array<u32>,
}
@group(0) @binding(0)
var <storage, read_write> data: Data;

The way this works is that WGSL will calculate the actual array length from the binding size.
Unfortunately wgsl_to_wgpu generates a zero length array from this, which makes encase unhappy and is also kind of unusable Rust-side. Fortunately encase has functionality to handle this case; by marking the field with the #[size(runtime)] pseuodo-attribute. Then the field can be a Vec and that is correctly handled by the encase read and write functions.
Of course this breaks bytemuck or raw casting, but the current zero-length array thing doesn't work that well anyway.
Now the question is, is it a good idea to special-case this (derive_encase == true and the array is runtime-sized)? Or something else should be done? I'd be happy to make a PR, but not until we agree on a solution.

We already support the case where a runtime-sized array is used directly like var<storage, read> data: array<u32>. The case where runtime-sized arrays are used in a struct isn't handled correctly. The length calculation requires the runtime-sized array in a struct to be the last field. I'm not sure if there's a way to encode this safely in Rust with bytemuck since the type would be dynamically sized. This sounds like it should probably just be an error when using bytemuck.
We could allow this when using encase and not bytemuck. Does encase give a compile error if the #[size(runtime)] attribute is missing?
https://www.w3.org/TR/WGSL/#buffer-binding-determines-runtime-sized-array-element-count

Does encase give a compile error if the #[size(runtime)] attribute is missing?
Yes:

error[E0080]: evaluation of `encase::types::array::<impl encase::ShaderType for [shaders::ffd::FfdKeypoint; 0]>::METADATA` failed
  --> /home/alex/.cargo/registry/src/github.com-1ecc6299db9ec823/encase-0.5.0/src/types/array.rs:31:18
   |
31 |             0 => panic!("0 sized arrays are not supported!"),
   |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the evaluated program panicked at '0 sized arrays are not supported!', /home/alex/.cargo/registry/src/github.com-1ecc6299db9ec823/encase-0.5.0/src/types/array.rs:31:18

The offending struct looks like this:
#[repr(C)]
#[derive(Debug, Copy, Clone, PartialEq, encase::ShaderType)]
pub struct FfdKeypoints {
    pub num: u32,
    pub points: [FfdKeypoint; 0],
}

What I would generate instead is this:
#[repr(C)]
#[derive(Debug, Copy, Clone, PartialEq, encase::ShaderType)]
pub struct FfdKeypoints {
    pub num: u32,
    #[size(runtime)]
    pub points: Vec<FfdKeypoint>,
}

And throw a compile error if encase is not used (or bytemuck is). Oh, and at that point #[repr(C)] can be dropped, since it shouldn't be casted anyway.
(IIRC Bytemuck can handle DST arrays (raw [T]), but that would make the struct itself ?Sized, which is kind of a pain to use (e.g. no copy, no clone, no way to instantiate on stack, etc.).)

Now the question is, is it a good idea to special-case this (derive_encase == true and the array is runtime-sized)? Or something else should be done?

I think this is fine. The current code doesn't support runtime-sized arrays at all. I'm not sure why I chose to emit a zero length in that function. We can just modify the array_length and rust_type functions to return Vec with the appropriate attribute when deriving encase. I think we also need to drop the derive for Copy in this case because of Vec. It should be easy enough to add test cases in structs.rs for this.

And throw a compile error if encase is not used (or bytemuck is). Oh, and at that point #[repr(C)] can be dropped, since it shouldn't be casted anyway.

Yeah. This should only work when deriving encase and not bytemuck. I don't think there's any advantage to having repr(C) without bytemuck.

I'd be happy to make a PR, but not until we agree on a solution.

That would be great if the points discussed above look ok to you.

Yeah, sounds good, I'll prepare a PR in the following days.


feat(spanner): Support directed read options

Support directed_read_options at client creation
Pass on the options to session when session is created from client
Support directed_read_options at per request level for streaming_reads and streaming_query_execution
Options set at request level takes precedence at the session
Add units to assert the option passing and precedence
Add acceptance test to test one happy path passing directed_read_options

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea.
[ ] Follow the instructions in CONTRIBUTING. Most importantly, ensure the tests and linter pass by running bundle exec rake ci in the gem subdirectory.
[ ] Update code documentation if necessary.

closes: #<issue_number_goes_here>

Benchmarking failure is unrelated to the changes, it has to be handled separately.  Samples PR is in another repo https://github.com/GoogleCloudPlatform/ruby-docs-samples/pull/1193


Must ONNX be used to convert the pytorch model?

Thank you very much for the work of the great God. Cross deployment platform, cross depth learning framework, is really a great job. However, I have a question about how I didn't see relay directly loading the pytorch model. Relay has not yet implemented support for the python model. Must onnx be used to convert the pytorchmodel?

Yes, we have to go through ONNX at the moment. A direct Pytorch to TVM route is being discussed right now.

That's really something to look forward to. I hope this day will come soon.


benchmark couchdb [solved]

I've added a new interface layer for couchdb and the command "mvn clean package" worked fine. When i try to start ycsb with the command "./bin/ycsb load couchdb -P workloads/workloada" it says, the database "couchdb" doesnt exit. I've installed couchdb and it works, also the interface layer worked fine when i resolved the dependencies.
(I've got the folder couchdb in the folder YCSB. the folder couchdb contains the folder YCSB-couchdb-binding-master from arnaud123, the folder "org.ektorp" and a pom.xml)
Can someone help me? Thanks
Solved: see github/arnaud123

closing for now. please reopen if you are still having problems.


Simpler test cases for metadata to avoid failing

I fixed #32. To avoid failing of test cases, I used only id to check value from /model/metadata endpoint.

This looks good to me. Thanks!

@kastentx Thank you for your reviewing it.


Add Selections constants

Pertains to GDK_SELECTION_*, GDK_TARGET_*, and GDK_SELECTION_TYPE_* reference.
I think these should go in src/selections.rs, and I'd implement them manually, but unlike other constants already exposed by gdk, these do not already exist in gdk_ffi. What's the proper procedure here then? Should these somehow be exposed in gdk_sys first and then re-exported with better names here?
This was broken out of gtk-rs/gdk#148.

In gdk/src/lib.rs I already see:
pub use crate::atom::SELECTION_CLIPBOARD;
pub use crate::atom::SELECTION_PRIMARY;
pub use crate::atom::SELECTION_SECONDARY;
pub use crate::atom::SELECTION_TYPE_ATOM;
pub use crate::atom::SELECTION_TYPE_BITMAP;
pub use crate::atom::SELECTION_TYPE_COLORMAP;
pub use crate::atom::SELECTION_TYPE_DRAWABLE;
pub use crate::atom::SELECTION_TYPE_INTEGER;
pub use crate::atom::SELECTION_TYPE_PIXMAP;
pub use crate::atom::SELECTION_TYPE_STRING;
pub use crate::atom::SELECTION_TYPE_WINDOW;
pub use crate::atom::TARGET_BITMAP;
pub use crate::atom::TARGET_COLORMAP;
pub use crate::atom::TARGET_DRAWABLE;
pub use crate::atom::TARGET_PIXMAP;
pub use crate::atom::TARGET_STRING;

Are we missing anything?

Looks like an old issue that was never closed.


perf: check global cache before extracting from reserved memory

The allocator should check the global cache for an available span before extracting a span of memory from the reserved memory to avoid cache bloating. Besides, extracting from reserved memory eagerly may also increase the degree of memory fragmentation.

Increases contention on the global cache, but yes, it's probably a better strategy.


Connects to #135. QC Data Monitor migration from ShinyApp.

Technical Notes:

In this initial version of the migration, the data source are static JSON files derived from the pipeline-generated .txt files.
The JSON data files are, for now, embedded in the app rather than making them publicly accessible via Google Drive or GCS bucket.
In the attempt to mirror ShinyApp's functionalities, there are further UI modifications given the feedback received upon reviews and testing.

Steps to test:

Sign into the data hub portal
In the sidebar, click on the QC Data Monitor button link and expect the PASS1B tissue submission "grid/heatmap" to be shown.
Click through the phase tabs (e.g. PASS1A/1C, Human) and expect to see respective grids representing the phases.
Now click on the Metabolomics button in the upper-right and expect to see the sample data table to be shown.
Verify the sorting, filtering, paging, and navigating functionalities against the data in the table.
Repeat the above step for other data tables (Proteomics, RNA-seq, etc.).
Now logout and sign in again as a registered external user.
Upon signing in, expect to see the QC Data Monitor button link disabled in the sidebar.

@cteng585 In the interest of time, I would appreciate it if you can review this PR today. Thank you.

All of the functionality that I tested worked. I did notice that there didn't appear to be a consistent way in which the search results were sorted when browsing through the omics tables (metabolomics, proteomics, etc), but I'm not sure how relevant this is. Also, logging out from the portal didn't work as expected, but I'm not sure if this is because it's a demo or if the auth service is actually broken.

I would also note that there isn't a color code for a sample that has both PASS1A and PASS1C in the phase column (this entry can be found in the Metabolomics tab if you search PASS1A-06|PASS1C-06.
Other than that, everything looks great.

@cteng585 Thanks for testing and reporting the issues you came across. The logout behavior is pertinent to the demo instance. For the other 2 observations, please create new GitHub issues for further investigation.


Auction view prototype

This is still pretty rough, but the hard part (the Relay support) is done.

Requires related metaphysics change: https://github.com/artsy/metaphysics/pull/795
Also refactors InfiniteScrollGrid to move away from icky queryKey towards a function-oriented approach.
Paired with @orta on getting Relay to work.
Related to: https://github.com/artsy/auctions/issues/682
Skip New Tests.

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

Missing Test Files:

src/lib/Components/Artist/Artworks/__tests__/index-tests.tsx
src/lib/Components/ArtworkGrids/RelayConnections/__tests__/SaleArtworksGrid-tests.tsx
src/lib/Components/Sale/__tests__/Header-tests.tsx
src/lib/Containers/__tests__/Sale-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Fails

:no_entry_sign:

No CHANGELOG added.

:no_entry_sign:

Missing Test Files:

src/lib/Components/Artist/Artworks/__tests__/index-tests.tsx
src/lib/Components/ArtworkGrids/RelayConnections/__tests__/SaleArtworksGrid-tests.tsx
src/lib/Components/Sale/__tests__/Header-tests.tsx
src/lib/Containers/__tests__/Sale-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

This is good for review+merge (it's not used in production yet, so there's no harm in having it master). I added some basic test scaffolds so that as we develop out the container/components, it's obvious where the tests go.

Fails

:no_entry_sign:

No CHANGELOG added.

Warnings

:warning:

Missing Test Files:

src/lib/Components/Artist/Artworks/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS

Warnings

:warning:

Missing Test Files:

src/lib/Components/Artist/Artworks/__tests__/index-tests.tsx

If these files are supposed to not exist, please update your PR body to include "Skip New Tests".

  Generated by :no_entry_sign: dangerJS


docs(readme): corrected description of serviceVersion option

serviceVersion had the same description as loggerName

Thank you for the contribution, appreciated 👍🏻


Consider re-integrating Leaflet, along with the overall UI

Leaflet had really good on-the-fly tile loading when I first tried, but it wasn't working in panel. This issue is now resolved so I plan to try the leaflet-stash fork again with that update applied.
There is also the ChatBox panel widget that would be interesting as either a modal or the main UI. In the latter case, I would imagine new holoviz views or leaflet views streaming into the chat as they are requested. This could also allow for "give me a histogram/ timeseries of XXX smaller AOI within the current view I am looking at."
I'm not really sure what the best solution is here, open to thoughts!

Definitely punting on this til after contest. May integrate some in-chatbox functionality towards the end of the month.

Alright... looks like it's actually working for folium so this could be used for basic previews of footprints, ground tracks, etc. But we won't be able to add layers, just single-shot. Probably better to start with. Maybe it'll work with ipyleaflet next week... idk anymore. 😅
https://gist.github.com/lalligagger/4e518956d1f9226c8d5aad8f30a8aa6f


[Stage2D] Adjust Stage mouse input

Adjusts mouse input y-coordinate to be relative to the viewport's height instead of the window's height.  This was a necessary change to my own game where I render a stage to a framebuffer at a constant screen and world size, so as to prevent distortion from texture filtering on individual actors due to my assets being extremely low resolution.  Since there are times when my window might be a larger height than the framebuffer's resolution, and consequently the stage's resolution, the input would be incorrectly positioned and handled if not for this change.

Going to close this since this change would break the correct behavior.
It looks like you are trying to solve the wrong problem. If you want to use a fbo then you'll have to scale your input coordinates accordingly. E.g. by encapsulating the stage and adjusting the arguments to be something like: x * fbo.getWidth() / Gdx.graphics.getWidth(), y * fbo.getHeight() / Gdx.graphics.getHeight()

I already am scaling the input from the screen down to the fbo/viewport's scale.  However, because those methods do a check against the window's size it instantly considers the positions invalid.  Something to note, touchedDragged does not perform those same checks, even though it should more or less exhibit the same behavior as mousemoved.  So while every other method is invalidating my input, it still works on touchedDragged.

Touch coordinates are always based on the physical screen size, not the size of the viewport on the screen. The part you are changing converts those into screen coordinates and then checks to make sure it is within the viewports screen area. Changing that conversion to use the viewports screen area height will break when the viewport does not fit in height (e.g. when there are black bars at the top or bottom of the screen).
For example: when the screen physical size is 480 and the viewport area is 400 in height, then the touch coordinate of y = 430 converted to screen coordinate should be 50 and not -30 (note that it actually should be one less, but that's another thing).


Pin angular dependencies to 1.4.4 explicitly

Previous version had wildcards, and mismatch circa 1.4.7 caused bower not to be able resolve a version. See issue #83.

:+1:

:+1:


Unable to use Graphql-Modules files as schema source for Houdini

Hello,
I was wondering if there is support in Houdini for compiling Graphql schemas from Graphql-Modules files. Typically partial schemas are expressed as tagged template literals using the gql tag supplied by Modules. Graphql-Code-Generator has no issue picking these up, and KitQL worked with them also. However when I tried using a glob pattern as the schema source for Houdini I was hitting an error, something about saying it didn't like the import keyword at the beginning of the file which tells me it isn't parsing the file as expected.
If there is a recommended way to work with this, that would be awesome. In the meantime I found a workaround, using Codegen to generate in introspection file and pointing Houdini to the introspection file as the schema.
Let me know what you think. I also tried to post this in Discussions instead of issues but GIthub wasn't having it for some reason.

What you are putting together is exactly the point of KitQL (using Houdini for the client part and Yoga for the server part).
Check out this Demo2, I think that it's exactly what you want to setup.
For schema files, instead of putting them in a ts files, you can put them in a .graphql files.
Like this, in the Houdini config, you will do:
demo2 - houdini.config.js
{
    schemaPath: 'src/**/*.graphql',
    sourceGlob: 'src/**/*.{svelte,gql}',
}

Maybe we can have a direct chat on DIscord or so?


Compile error. Unable convert form nullptr to nullptr&&

I can not compile json.hpp.

error C2664: "BasicJsonType *nlohmann::detail::json_sax_dom_parser::handle_value(Value &&)": невозможно преобразовать аргумент 1 из "nullptr" в "nullptr &&"

problem code:
    bool null() override
    {
        handle_value(nullptr);
        return true;
    }

What code do you try to compile? Which compiler are you using? What version of the library are you using?

visual studio 2015 (vc140). library downloaded from develop branch (last version)
#include <nlohmann/json.hpp> // single include

using namespace std;

using json = nlohmann::json;

int main( void )
{
	json j = "{ \"happy\": true, \"pi\": 3.141 }"_json;
	return 0;
}

Is that compiler supported? From the README: Microsoft Visual C++ 2015 / Build Tools 14.0.25123.0 (and possibly later)

Microsoft Visual Studio Enterprise 2015
Версия 14.0.25431.01 Update 3
Microsoft .NET Framework
Версия 4.7.03056

Could you try to remove using namespace std?

Nothing has changed

That is strange as we use MSVC 2015 with AppVeyor in your CI suite.

Can any macro be defined? Or any compilation option? Can you sln the file?

Maybe related: #987.

Can any macro be defined? Or any compilation option? Can you sln the file?

What do you mean by that?

I'm interested in Build Tools. 140 or 141?

AppVeyor uses Microsoft (R) Build Engine version 14.0.25420.1, MSVC 19.0.24215.1. What do you mean?

It is very strange.

I don't know how to proceed here. To summarize, it seems as if you are using the exact compiler version as we are doing on AppVeyor. Could you make sure that you run the exact same commands as here?

The problem was solved by disabling the CRL in the compiler settings

Thanks for checking back!


Access Roborock in Guest Wifi

Hi,
I used to leave my Roborock S5 in the Guest Wifi. This worked well as I could access through App via Internet despite local wifi and keep Xiaomi out of my actual wifi.
Is there any way to use the plugin via http despite local IP?
This way I use my Robonect as it supports a web service address as well.
Thank you in advance!
Fakio

Hi @fakio87,
AFAIK, as long as homebridge has access to that local IP, I don't see why it wouldn't work.

It looks like the question was answered... I'll close this issue. Feel free to reopen if there are any follow up questions.


Is it possible to change the buffer size?

I want to keep watching a log file where one line could be ~100KB and it seems the first 65536 bytes are read now.
Is is possible to change the maximum buffer size?

It sounds like you're wanting to change the highWaterMark for the read stream?  Based on your short description, it's hard to tell what is or is not happening.  The high water mark is a backpressure mechanism for node internals, so it should still output a line that's 100KB.  You shouldn't have to tweak that based on your line size, but I might be missing something.
In any case, if you want to try and change that, the readStreamOpts can be set to use a different high water mark.

I have changed my code after making this issue and now each of my lines is shorter than 65536 bytes, but basically, it was something like this:
const tail = new TailFile(path, {
  encoding: "utf8",
  pollFileIntervalMs: 100,
});

tail
  .on("data", async (data) => {
    console.log(data.length); // 65536 even when a line contains more
  })
  .start();

But thank you for your suggestion. If there is any need for the option in the future I will set it.


GoogleAnalytics on by default

that's fine for foaas.com, but should not be in publix/index.html or the spec files in general.

True, will remove.