Typed request

Hi, I'm new to Siesta.
I have api service and a bunch of methods in it. Each method returns Request, so I could further chain them or start later, what I want... Then in some place I have:
api.myMethod().onSuccess { entity in
   //here entity.content is of type Any and I must downcast, but it's a bad choice to do it here
   //how could I set type of content in response while in `myMethod()` returning a request
   // P.s. I have some transformers configured in my api service, so response by `myMethod()` request is transformed to some model type
}.onFailure { error in
   print(error)
}

See “Why doesn’t Siesta provide a typesafe Resource?” in the FAQ.
In the meantime:
api.myMethod().onSuccess { entity in
    let user: MyUserModel? = entity.typedContent()
}

(Note also that to get the full benefit of Siesta, you don’t want to be attaching onSuccess() to individual requests, but rather observing the resource.)

@pcantrell, okay but I am a bit misunderstood with siesta
What the difference between Request and Resource?
I have AuthService with signIn, signUp requests, so I could call them when pressing on button and listen whether response is succeeded or failed, don't I?
I have some TasksResource: Resource and I want to observe tasks changes? Or when I need to use a Resource.
P.S.
api.myMethod().onSuccess { entity in
    let user: MyUserModel? = entity.typedContent()
}

I do not like this case, because it could be used lots across the program and will lead to potential duplication and requires changes in many places...

@pcantrell Also I have doubts if I have resource "news" and I want to call method "all" -> I do newsResource.child("all").start(), but "news" resource won't get any updates :(

@pcantrell also why Resource marked as final class?

Each URL give a different resource so I you have new/all and news/1 you have two resources. Now if you look at the quick start in the request section for post etc there is a way that you use the result of a request to update an existing resource. I you want to perform a request without cache you should use resource.request(.get) instead resource

What the difference between Request and Resource?

Read the User Guide, especially the first 4 pages (Resources, Resource State, Observers, and Requests). This will answer a lot of your questions.
See also the API docs for Request for info on how it differs from Resource.

I do not like this case, because it could be used lots across the program and will lead to potential duplication and requires changes in many places

It doesn’t play out so badly in practice, especially if you let Swift’s type inference guide typedContent() for you. See the code in the example project.


fix(service): Create normal service when knative-service trait is disabled (1.10.x)

https://github.com/apache/camel-k/issues/3849
When knative-service and k8s service traits are enabled, the priority is to use knative-service in knative profile
(cherry picked from commit 07563546a5d04c53dab122e90bc768e08514defe)
Release Note
NONE

@christophd for review


Remove manga aspects of the app and keep only anime sections

stuff like the library section at the bottom, manga section in updates tab, and manga extensions

Agreed, most users would prefer if this app was anime only. Either removing all manga would be ideal, or an option to disable anything manga related.

idk if "most users" is accurate, because i have gotten a lot of feedback that says they like having an "all in one app". but in the future i will add this.

Agreed, most users would prefer if this app was anime only. Either removing all manga would be ideal, or an option to disable anything manga related.

This is not most users, this is your opinion. The app is fine how it is because finding an all in one app like this is practically impossible and convenient. I'd say add an option to remove the manga section if it bothers people that much

idk if "most users" is accurate, because i have gotten a lot of feedback that says they like having an "all in one app". but in the future i will add this.

idk if "most users" is accurate, because i have gotten a lot of feedback that says they like having an "all in one app". but in the future i will add this.

I prefer All in one, That is the main reason i downloaded this app

It only miss the light novel and it's an perfect app

Agreed. App name is "Aniyomi", which suggests it's for the anime, not for manga/anime/light novels.
An all in one app wouldn't be a bad idea, but it certainly doesn't fit here.

Agreed. App name is "Aniyomi", which suggests it's for the anime, not for manga/anime/light novels.
An all in one app wouldn't be a bad idea, but it certainly doesn't fit here.

https://jisho.org/search/yomi

Maybe an option to hide the Manga icon from the nav bar would be enough.

A toggle option to disable manga seems like a really good option... still waiting for it tho......

Tbh, I lost interest on Aniyomi. Feel free to either continue this or scrap the implementation entirely.
Sorry.

😂

For those seeking an anime only version, there is:
Animiru (unofficial fork of Aniyomi)


error while creating reorder primitive

I get mkldnn_unimplemented error. Could not create reorder primitive error when I tried to create reorder primitive. Only difference from simple_net implementation is that there is no data in memory during reorder constructor.
// create reorder
auto user_src_memory = memory(src_mem_desc, eng, nullptr);
auto dst_memory = memory(conv1_prim_desc.src_desc(), eng, nullptr);
auto pm = reorder(user_src_memory, dst_memory); // exception here

src_memory.set_data_handle(input_data);
dst_memory.set_data_handle(output_buffer);
pm.execute(stream,
            { { MKLDNN_ARG_FROM, src_memory }, { MKLDNN_ARG_TO, dst_memory } });

please advice

Hi @dev2y,
I tried but failed to reproduce the behavior you observe.
The only guess I have is that the logical description of src_memory doesn't match the logical description of dst_memory, e.g. src_memory.dim[0] != dst_memory.dim[0]. Though, if your example is based on the simple_net example, this is highly unlikely.
Could you please send us the whole reproducer?

@emfomenk I'm following simple_net to implement but I got this error in our code. I will try to get the whole reproducer but before that I will make sure that their logical desc match. thank you.

Closing due to the lack of activity.


Added optional reveal setting for testcase

if reveal (default true) is set to false then the test input, and expected/actual output is hidden in the feedback - shows "hidden" instead - see added note on example 2 in examples book.

merged into main - it was a simple tweak used for hiding testcases for the Christmas Challenge under Fun Challenges; has been working well on live pythonsponge for a while.


Add sample

@jpgarcia do not review this PR yet! since I look forward to adding some automatic testing using Detox, following the pattern RNN playground is tested like.
(except @ayelenmarie wants to make a collaboration since she's familiar with it 👀 😄 )
The example is working locally, so you can test a new change before updating the package on npm.
Went for a single example and not for several versioned samples because it seems cleaner & can focus on adding E2E tests to it.

It took me a while to send this PR since I had to solve some issues with my xcode and macOS system versions first

Most events are tested automatically now!
As detailed on the example's README there a couple of missing iOS +11 events tests
We should probably see to use something specific to run the E2E tests or configure circleci if possible (since that is the reason it is crashing)
There is also a minor detail that is when a detox test fail you have to scroll up through the console to see it because there is other long jest issue appearing. As I said its really minor, but worth mentioning.

@jpgarcia I'm having some issues running the E2E detox tests on CircleCI and this PR is already a big one. Maybe its best if u can review it as it is now and I'll continue what I mentioned on another PR.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Name
GoCD
Website
https://www.gocd.org/
Logos

The Legal Stuff

[X] My organization consents to their logo being displayed on the Eclipse Temurin adopters page.

Not sure if you're interested in commercial organizations only - your call 👍

Not sure if you're interested in commercial organizations only - your call 👍

Thanks for adding this @chadlwilson! I'll get the logo added to our staging page shortly.


Swift package using C sources fail to link

Hey @vgorloff thanks for all the great work here!
I am running into a linker error when importing a swift package that wraps a C library.
Package being imported: https://github.com/gshahbazian/SwiftGumbo
Exports.swift:
...
import SwiftGumbo

@_cdecl("Java_com_home_helloNDK_SwiftLib_sayHello")
public func sayHello() {
   let g = SwiftGumbo(html: #"
HEY WHATS UP

Nothing
"#)
   let text = g.root.textContent

   AndroidLogger.info("SA - SwiftCore: Works! \(text)")
   probeDispatch()
   probeOperation()
   probeSerialization()
   tester.test()
}
...

Package.swift:
// swift-tools-version:5.0

import PackageDescription

let package = Package(
   name: "HelloJNI",
   products: [
      .library(name: "HelloJNICore", type: .dynamic, targets: ["HelloJNICore"]),
      .library(name: "NDKLog", targets: ["NDKLog"])
   ],
   dependencies: [
      .package(url: "https://github.com/gshahbazian/SwiftGumbo", .exact("1.0.0")),
   ],
   targets: [
      .target(name: "HelloJNICore", dependencies: ["NDKLog", "SwiftGumbo"]),
      .target(name: "NDKLog", dependencies: ["sysNDKLog"]),
      .systemLibrary(name: "sysNDKLog"),
   ]
)

Compile error:
...
[18/19] Compiling HelloJNICore Exports.swift
<unknown>:0: error: error opening input file '/Users/gabepop/Downloads/swift-everywhere-samples-master/Android/app/build/swift-x86_64/x86_64-apple-macosx/release/CGumboParser.build/ascii.c.o' (Don't know how to extract from object fileformat)
<unknown>:0: error: swift-autolink-extract command failed with exit code 1 (use -v to see invocation)
[18/19] Linking libHelloJNICore.dylib

The debug configuration still broken. But i was able to build SwiftGumbo release configuration with following command:
export SWIFT_EXEC=/PathToDownloadedToolchain/swift-android-toolchain/usr/bin/swiftc-arm-linux-androideabi
swift build -c release --destination ./android-armv7.json

Where ./android-armv7.json is below:
{
  "version": 1,
  "sdk": "/PathToDownloadedToolchain/swift-android-toolchain",
  "toolchain-bin-dir": "/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/bin",
  "target": "armv7-none-linux-androideabi",
  "dynamic-library-extension": "so",
  "extra-cc-flags": [
    "-v",
    "-I/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include",
    "-I/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/arm-linux-androideabi"
  ],
  "extra-swiftc-flags": [
    "-v",
    "-tools-directory",
    "/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/bin",
    "-Xcc",
    "-I/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include",
    "-Xcc",
    "-I/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/include/arm-linux-androideabi",
    "-Xclang-linker",
    "--sysroot=/usr/local/ndk/20.1.5948944/platforms/android-24/arch-arm",
    "-Xclang-linker",
    "--gcc-toolchain=/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64",
    "-L",
    "/usr/local/ndk/20.1.5948944/sources/cxx-stl/llvm-libc++/libs/armeabi-v7a",
    "-L",
    "/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/lib/gcc/arm-linux-androideabi/4.9.x",
    "-L",
    "/usr/local/ndk/20.1.5948944/toolchains/llvm/prebuilt/darwin-x86_64/sysroot/usr/lib/arm-linux-androideabi/24",
    "-L",
    "/PathToDownloadedToolchain/swift-android-toolchain/usr/lib/swift/android/armv7"
  ],
  "extra-cpp-flags": [
    "-v"
  ]
}

This is an archived sample project with two build scripts (for macOS and Android).
SwiftGumbo.zip

Also possible now (fix still in develop branch) to build without --destination flag.
cd SwiftGumboProject
/...../swift-android-toolchain/usr/bin/swift-build-arm-linux-androideabi -c release

Ok. The issue with SPM Debug Builds now fixed in https://github.com/vgorloff/swift-everywhere-toolchain/releases/tag/1.0.57.
Closing issue.

Thanks for all your work on this @vgorloff!


Installation problem

Hello, I have done everything as instructed in wikis and the result is below
esptool.py
 v2.0-beta2
Connecting....
Detecting chip type... ESP8266
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 230400
Changed.
Attaching SPI flash...
Configuring flash size...
Auto-detected Flash size: 4MB
Flash params set to 0x0040
Compressed 36432 bytes to 26362...
Wrote 36432 bytes (26362 compressed) at 0x00000000 in 1.2 seconds (effective 249.8 kbit/s)...
Hash of data verified.
Compressed 391572 bytes to 283524...
Wrote 391572 bytes (283524 compressed) at 0x00014000 in 12.5 seconds (effective 249.9 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting...

but the esp8266 is not connecting to my AP although I have uncommented the user_init function and inserted my APssid and password correctly
Any ideas?

removed baud rate parameter and worked


Authenticator CRD & Operator Proposal

If I'm not wrong this is an alternative to https://github.com/heptio/authenticator/issues/34
Authenticator IAM CRD Proposal
Overview
The current structure of the Heptio Authenticator uses default Kubernetes ConfigMap primitives that allow you to add and remove IAM Roles this gives a single point of configuration for the whole lookup table and allows the authenticator to load once and cache the results. The problem is when it comes to updating if you make a change to this file and re-apply it won’t automatically be affected, admins need to reload the DaemonSet webhook backend for the new config to load. This proposal came out of the 2018-04-05 community call, The discussion was about the usage of CRDs as a way to make this better. The rest of this document will talk about the specifics of how this could work for the authenticator.
Comments - https://docs.google.com/document/d/1UgSDcMbZdMXLY1SxUtQ7r1puLFdGYF660usGW7AlGwE/edit#
/cc @nckturner @mattlandis @mattmoyer

The prometheus operator recently made a similar shift, and provided a tool to migrate existing configmaps:
go get -u github.com/coreos/prometheus-operator/cmd/po-rule-migration
po-rule-migration \
--rule-config-map=<path-to-config-map> \
--rule-crds-destination=<path-to-rule-crd-destination>

0.20 will otherwise automatically convert (upgrade) existing configmaps to crds.

Awesome @StevenACoffman that feedback is great…

This could be a nice addition wouldn't be too hard to also have it done in-cluster, so you could pass the name of the ConfigMap in most causes aws-auth as a flag, and have it pull the list, generate the objects and re-apply them to the cluster.

@christopherhein Let's discuss the feedback on this doc in sig-aws next meeting to move this forward.

Sounds good!

@christopherhein I am going to take a stab at the implementation for this feature this week.

/remove-lifecycle-stale

/remove-lifecycle stale

@christopherhein Is the CRD available in EKS cluster?

@christopherhein Is the CRD available in EKS cluster?

As far as I know not yet.
/cc @micahhausler @nckturner

@christopherhein is there any plans to make it available on EKS? If yes, is there an ETA?

@christopherhein is there any plans to make it available on EKS? If yes, is there an ETA?

/cc @tabern @nckturner @micahhausler

Any updates on the ETA?
When will be released a new aws-iam-authenticator version with the CRD as well?

We're overdue for an authenticator release so that should come relatively soon, but in terms of bringing this feature to EKS, that is TBD.  If its something you want please add it to https://github.com/aws/containers-roadmap.  I don't think we've had a lot of customers asking for it in EKS so there are currently other higher priorities.

Done @nckturner : https://github.com/aws/containers-roadmap/issues/550


Turn screen off when closing scrcpy

Fix #714

I merged the first commit fixing the log :+1:

I have pushed v2:

Let this feature be optional.
use "lock screen"

However, I found that server may be killed before screen off.
We may need to introduce some ack mechanism from server to client.

However, I found that server may be killed before screen off.
We may need to introduce some ack mechanism from server to client.

In my TODO list, I plan to implement something similar to #679 to be able to cleanup properly:

The server "forks" itself for full life cycle control (adb may kill it instead preventing required cleanup).

This will be a requirement to merge this PR.

Now that there is a real cleanup, you could implement it :wink:
(I suggest --power-off-on-close)

@npes87184 I think several people are interested:

#714
#1764
#2103
https://www.reddit.com/r/scrcpy/comments/ljzpdd/turning_off_the_display_automatically_upon/
:wink:

Ok, I will look it.

Hi, @rom1v
There is a problem about power off screen in CleanUp process. In this time, injectEvent will consider about displayId to inject to correct target. However, it is diffiuclt to allocate Device in the process of CleanUp. As an result, I cannot trigger power off screen in that stage. Do you have any good advice?
Thank you.

As a quick-and-dirty solution, maybe you could expose a static injectEvent() taking a displayId:
diff --git a/server/src/main/java/com/genymobile/scrcpy/Device.java b/server/src/main/java/com/genymobile/scrcpy/Device.java
index a8fdf677..9fb365ff 100644
--- a/server/src/main/java/com/genymobile/scrcpy/Device.java
+++ b/server/src/main/java/com/genymobile/scrcpy/Device.java
@@ -157,16 +157,20 @@ public final class Device {
         return supportsInputEvents;
     }

+    public static boolean injectEvent(InputEvent inputEvent, int mode, int displayId) {
+        if (displayId != 0 && !InputManager.setDisplayId(inputEvent, displayId)) {
+            return false;
+        }
+
+        return SERVICE_MANAGER.getInputManager().injectInputEvent(inputEvent, mode);
+    }
+
     public boolean injectEvent(InputEvent inputEvent, int mode) {
         if (!supportsInputEvents()) {
             throw new AssertionError("Could not inject input event if !supportsInputEvents()");
         }

-        if (displayId != 0 && !InputManager.setDisplayId(inputEvent, displayId)) {
-            return false;
-        }
-
-        return SERVICE_MANAGER.getInputManager().injectInputEvent(inputEvent, mode);
+        return injectEvent(inputEvent, mode, displayId);
     }

     public boolean injectEvent(InputEvent event) {

Then, you have to transmit both the displayId and the flag to NOT turn off if control is disabled.
What do you think?

As a quick-and-dirty solution, maybe you could expose a static injectEvent() taking a displayId:
diff --git a/server/src/main/java/com/genymobile/scrcpy/Device.java b/server/src/main/java/com/genymobile/scrcpy/Device.java
index a8fdf677..9fb365ff 100644
--- a/server/src/main/java/com/genymobile/scrcpy/Device.java
+++ b/server/src/main/java/com/genymobile/scrcpy/Device.java
@@ -157,16 +157,20 @@ public final class Device {
         return supportsInputEvents;
     }

+    public static boolean injectEvent(InputEvent inputEvent, int mode, int displayId) {
+        if (displayId != 0 && !InputManager.setDisplayId(inputEvent, displayId)) {
+            return false;
+        }
+
+        return SERVICE_MANAGER.getInputManager().injectInputEvent(inputEvent, mode);
+    }
+
     public boolean injectEvent(InputEvent inputEvent, int mode) {
         if (!supportsInputEvents()) {
             throw new AssertionError("Could not inject input event if !supportsInputEvents()");
         }

-        if (displayId != 0 && !InputManager.setDisplayId(inputEvent, displayId)) {
-            return false;
-        }
-
-        return SERVICE_MANAGER.getInputManager().injectInputEvent(inputEvent, mode);
+        return injectEvent(inputEvent, mode, displayId);
     }

     public boolean injectEvent(InputEvent event) {

Then, you have to transmit both the displayId and the flag to NOT turn off if control is disabled.
What do you think?

Oh, yes. This solution works. However, I am thinking about future. It may need to more and more things that need to be done in CleanUp. If we need to pass variable likes this in each time, it is very annoy and dirty.
For infrastructure, in my opinion, in CleanUp process, I prefer to prepare a environment similar to the main process.
It just needs to handle the options correctly. Maybe it can add two methods, toFile and fromFile, to the class options.
What do you think?

It just needs to handle the options correctly.

It could be great to serialize some structure between the main process and the cleanup process indeed.
However, this structure should not be the existing Options, which is neither necessary (not all fields are meaningful for the cleanup process) nor sufficient (the cleanup actions may for example depend on the initial state of the device, which is not stored in the options).
(I don't know if in the end such a structure would be helpful compared to passing each option per argument.)
But yes, it would be great to share the common part of the Device initialization between the main and cleanup process. For now, Device is quite a mess, and it's not clear semantically what this class represents.

Ok, I will pass displayId in this time. The refactoring of Device and the environment preparation of CleanUp should be another problems (or features).
Thank you for your help.

Hi, @rom1v
I have added two commits about this features.
First, I export a series static methods for powering off. Second, make CleanUp process respects the power off setting.
Thanks.

Thank you very much for your work :+1:
I just tested, and I found a problem (on a Nexus 5): the "power off" cleanup interacts badly with the "restore normal power mode" cleanup, which is executed whenever the screen is on on exit. As a result, --power-off-on-close works randomly (on this device).
I tried with these changes:
diff --git a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
index 7dda83fb..26012409 100644
--- a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
+++ b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
@@ -84,16 +84,14 @@ public final class CleanUp {
             }
         }

-        if (restoreNormalPowerMode) {
-            Ln.i("Restoring normal power mode");
-            if (Device.isScreenOn()) {
+        if (Device.isScreenOn()) {
+            if (powerOffScreen) {
+                Ln.i("Power off screen");
+                Device.powerOffScreen(displayId);
+            } else if (restoreNormalPowerMode) {
+                Ln.i("Restoring normal power mode");
                 Device.setScreenPowerMode(Device.POWER_MODE_NORMAL);
             }
         }
-
-        if (powerOffScreen) {
-            Ln.i("Power off screen");
-            Device.powerOffScreen(displayId);
-        }
     }
 }

It improves the behavior.
But I have an additional issue that can I cannot explain: if I keep touching the device (I keep one finger on the device screen) while I close the scrcpy window, it blocks and never power off the screen. It is unexpected, because if I keep one finger on the screen and press MOD+p to power off the screen, then it works. :confused:
If I add some logs (and even if I always return true) in Device.isScreenOn():
diff --git a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
index 26012409..2c54558c 100644
--- a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
+++ b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
@@ -84,7 +84,9 @@ public final class CleanUp {
             }
         }

+        Ln.i("CLEANUP #1");
         if (Device.isScreenOn()) {
+            Ln.i("CLEANUP #2");
             if (powerOffScreen) {
                 Ln.i("Power off screen");
                 Device.powerOffScreen(displayId);
@@ -93,5 +95,6 @@ public final class CleanUp {
                 Device.setScreenPowerMode(Device.POWER_MODE_NORMAL);
             }
         }
+        Ln.i("CLEANUP #3");
     }
 }
diff --git a/server/src/main/java/com/genymobile/scrcpy/Device.java b/server/src/main/java/com/genymobile/scrcpy/Device.java
index 624c9fa0..3ee248d3 100644
--- a/server/src/main/java/com/genymobile/scrcpy/Device.java
+++ b/server/src/main/java/com/genymobile/scrcpy/Device.java
@@ -212,7 +212,7 @@ public final class Device {
     }

     public static boolean isScreenOn() {
-        return SERVICE_MANAGER.getPowerManager().isScreenOn();
+        return true; //SERVICE_MANAGER.getPowerManager().isScreenOn();
     }

     public synchronized void setRotationListener(RotationListener rotationListener) {

Then it blocks:
02-21 11:24:23.251 21036 21056 D scrcpy  : Device message sender stopped
02-21 11:24:23.485 21054 21054 I scrcpy  : Cleaning up
02-21 11:24:23.485 21054 21054 I scrcpy  : CLEANUP #1

If I replace Device.isScreenOn() by true, then it prints CLEANUP #2, but and Power off screen, but does not power off the screen. :thinking:

In fact, it seems the cleanup process is killed (the process does not appear in ps).
Btw, if I add a SystemClock.sleep(1000); (even if I don't touch the device), the process is closed before CLEANUP #1.
The fact that I touch the screen is irrelevant (it probably just change the timings and makes it more probable).
It's probably due to the OMXNodeInstance: !!! Observer died:
02-21 11:45:31.420 22574 22593 D scrcpy  : Controller stopped
02-21 11:45:32.469 22592 22592 I scrcpy  : Cleaning up
02-21 11:45:32.478 28310 29411 E OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything...
02-21 11:45:32.590 28310 29411 W GraphicBufferSource: Dropped back down to Loaded without Executing
02-21 11:45:32.624 28310 29411 I OMX-VENC: Component Deinit

In fact, it seems the cleanup process is killed (the process does not appear in ps).
Btw, if I add a SystemClock.sleep(1000); (even if I don't touch the device), the process is closed before CLEANUP #1.
The fact that I touch the screen is irrelevant (it probably just change the timings and makes it more probable).
It's probably due to the OMXNodeInstance: !!! Observer died:
02-21 11:45:31.420 22574 22593 D scrcpy  : Controller stopped
02-21 11:45:32.469 22592 22592 I scrcpy  : Cleaning up
02-21 11:45:32.478 28310 29411 E OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything...
02-21 11:45:32.590 28310 29411 W GraphicBufferSource: Dropped back down to Loaded without Executing
02-21 11:45:32.624 28310 29411 I OMX-VENC: Component Deinit

(I don't have this problem on my OnePlus 7 Pro)

Hmm, I am not familiar with OMXNodeInstance: !!! Observer died.
BTW, I don't notice this problem in my note10+ with android 11.
diff --git a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
index 7dda83fb..26012409 100644
--- a/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
+++ b/server/src/main/java/com/genymobile/scrcpy/CleanUp.java
@@ -84,16 +84,14 @@ public final class CleanUp {
             }
         }

-        if (restoreNormalPowerMode) {
-            Ln.i("Restoring normal power mode");
-            if (Device.isScreenOn()) {
+        if (Device.isScreenOn()) {
+            if (powerOffScreen) {
+                Ln.i("Power off screen");
+                Device.powerOffScreen(displayId);
+            } else if (restoreNormalPowerMode) {
+                Ln.i("Restoring normal power mode");
                 Device.setScreenPowerMode(Device.POWER_MODE_NORMAL);
             }
         }
-
-        if (powerOffScreen) {
-            Ln.i("Power off screen");
-            Device.powerOffScreen(displayId);
-        }
     }
 }

I will apply this change as it is more correct.
Thank you for your test and survey.

Thank you  :+1: Merged into dev


Add NTLM Proxy Support

Add NTLM Proxy support as this has been an ongoing battle with existing plugins and lack of support.

This has been resolve and NTLM auth is now supported.


Fix set semantics bug

Fixes https://github.com/comunica/rdf-streaming-store.js/issues/6

I opened this PR for conversation on what to do.
I'm starting to doubt that this is actually possible with the rdfjs Store interface. In some way, we need to await the import of each quad into the store to continue to match a new quad to the store. I made a new test that amplifies this problem.

One solution could be to have a temporary "import store" where we can syncrounously add quads to. When checking if this quad already exists (with the match function) we check both the temporary "import store" and the actual store. If it doesn't exist yet we can add it to both stores. At the end of the stream we can delete the temporary "import store".

nvm, this would break if there are multiple import streams. If, for example, two simultaneous imports are done with identical quads you would get duplicate results.

nvm, this would break if there are multiple import streams. If, for example, two simultaneous imports are done with identical quads you would get duplicate results.

You could work around this, by halting concurrent imports until the other import is done.
But this would complicate things of course, so I'd only do this if we're certain there's no easier way :-)

Actually, what you suggest would make the logic quite clean:

Wait until other concurrent imports are done
Determine unique triples synchronously
Import unique triples to store and listeners.

This does mean that a non ending stream could block imports into the store.

True, that would be problematic indeed...
So a more fine-grained quad-per-quad approach may be needed.

I was implementing this, but I realize now that there is no way of knowing when we should free the synchronous store.

Add quad in 'synchronous store'
Import unique quads to 'actual store' and listeners
After import is done delete 'synchronous store'

When do we delete the 'synchronous store'? We don't know when the import to the 'actual store' has finished. The only way I know is continuously match the quads to the 'actual store' until the match function returns an element, but this is really inefficient.

This may be getting too complicated for what it's worth.
Maybe we should concede and just assume a synchronous quad-containment checker in the rdf store.
This would come at the cost of interoperability, but perhaps this is fine given the complexity.
As long as it's works with n3 and rdf-stores, it's fine by me :-)

So I switch from a rdfjs interface to a n3 Store interface?

Or I switch to a rdfjs dataset interface?

See branch: https://github.com/comunica/rdf-streaming-store.js/tree/fix-set-semantics-bug-with-other-interface

@maartyman This approach won't work with rdf-stores unfortunately, as that lib doesn't implement DatasetCore directly on the store, but through a separate asDataset() method.
What we could do instead, is make use of the sync countQuads method that both N3 and rdf-stores implement. We could just create a custom local interface with a copy of this countQuads method signature, so that we can pass both N3 stores and rdf-stores.


Filmora 14 crack 2024 Download

Filmora crack Download
Filmora 14 is a vibrant canvas for the modern storyteller, where every frame is an opportunity to paint with light and sound. With its sleek, intuitive interface, it invites you to weave a tapestry of creativity, from seamless transitions to cinematic color grading. Like a master’s palette, it offers a wealth of effects and tools, each brushstroke enhancing your vision. Whether you're crafting a delicate narrative or a bold visual symphony, Filmora 14 transforms your raw footage into a masterpiece, effortlessly blending artistry with technology.
Download filmora 14 crack
crack filmora 14
filmora crack download
filmora 14 crack download

Filmora 14 is a symphony of simplicity and sophistication, where every advantage feels like a stroke of genius. Here are its masterpieces:
Intuitive Interface: A blank canvas that welcomes all artists, no matter their skill. The clean, streamlined design lets your creativity flow without the distraction of clutter, offering a fluid workspace to build your vision.
Vibrant Effects Library: Like an endless palette of colors, Filmora 14 offers an expansive library of effects, transitions, and templates. You can experiment, mix, and match to bring your creations to life with a pop of style or a touch of elegance.
AI-Powered Tools: The brushstrokes of artificial intelligence help fine-tune your work effortlessly, from auto-reframing for social media to AI-driven audio enhancement. It’s like having a hidden assistant that ensures every detail is in harmony.
Seamless Multitrack Editing: Build depth and dimension in your work with the ease of multi-layer editing. Layer audio, video, and effects like a complex composition, where every element can sing its own part yet come together in perfect unison.
Speed and Performance: A well-crafted sculpture—Filmora 14 works swiftly and smoothly, even with demanding projects. The software allows you to shape your masterpiece without the frustration of lag or slow rendering.
Flexible Export Options: Your art is ready for the world, and Filmora 14 offers a wide range of export options, ensuring your creation is delivered in the highest quality for any platform, whether it's a gallery or a global stage.
Filmora 14 is not just a tool, but a creative partner, empowering you to create with ease and elevate your vision to new artistic heights.


[Proposal][QTL] unify lookup dimension spec

Today we have 2 ways to create a druid dimension based on a lookup.
The first one (old way) is as an extraction function ExtractionFn and the second is via lookup dimension spec LookupDimensionSpec.
Chronologically speaking the LookupDimensionSpec was introduced after ExtractionDimensionSpec.
The reason behind this is the fact that lookups can offer more functionalities like unApply, unApplyAll, bulk lookups or the fact that one dimension can map to multiple values use case.
IMHO This means it is better for lookup to be independent from extraction function from a design perspective. Now that we ended up with 2 way of doing things, i guess it is time to unify it.
Benefits.

-Will be able to support the case where we have a one to many  mapping as lookups
Ensure that the logic of the mapping is consistent for both filtering and aggregation. This is really important if we want to support the use case mapping one to many
-Avoid to have duplicate code where issue like this occurs https://github.com/druid-io/druid/pull/3065
-Support the bulk lookup issues https://github.com/druid-io/druid/issues/3030

To achieve that is to make filters accept dimension spec instead of just dimension as a string and extraction function.
Then make the dimensionSpec use the decorate method since getExtractionFn is deprecated anyway.
Also we have to make all the filters work with either decoration of selector or extraction function.

@gianm and @drcrallen what do you think ?

One problem with LookupDimensionSpec that exists today is that the lookup can't be chained with any other extractions. Users can use the chained extraction fn to write filters like SUBSTR(LOOKUP(foo, "mylookup"), 2, 4) = "bar" but this is not possible with dimensionSpecs by themselves.

The other kind of nesting is also possible and also useful, i.e. both of,

SUBSTR(LOOKUP(foo, "mylookup"), 2, 4) = "bar"
LOOKUP(SUBSTR(foo, 2, 4), "mylookup") = "bar"

@gianm what you are saying make sense, but this mean if a lookup is embedded under extraction function, we can do something like mapping one to many or take advantage of applyAll. Not sure which way to go, do you have suggestions ?

@b-slim not sure what you mean by that, could you give an example of what you're thinking?

@gianm For instance lookup can be mapping between one to many, how you want to support that if you do cascading ?

Currently lookups can not actually be one to many right?
But if they could, one possible way to deal with that is if you have a cascade, and layer N of the cascade generates potentially many values for every one value, then you handle that by running functions in layer N + 1 for each of those many values. So the cascade ends up returning potentially multiple values rather than just one value.

@gianm yes, it is not supported and thought it is in the road map. I am not sure why you don't like dimensionSpec doing the decoration. We can have a dimensionSpec that does cascading anyway right ? this can be chained by decorating selectors.

@b-slim nothing's wrong with dimensionSpec in principle, I just wanted to point out that there are some things extractionFns can do that dimensionSpecs can't, which would need to be addressed before they can really be unified.
In particular, some that I can think of are,

ability to chain with other extractionFns
ability to expose preservesOrdering and isOneToOne for filters and query engines
when used with filters, ability for filters like "selector" and "bound" to determine if they can use binary search of the dictionary or if they must do a full scan of the dictionary (I think preservesOrdering and isOneToOne are enough for this though)

#3091 also seems related.

@b-slim are you still planning to drive this? Shall we move to 0.10.1?

@gianm i think this need to reconcile with bunch of other PR and proposals as well will look into that ASAP.

closing this since am not looking into it.


Setup coverage in CI

To be considered:

https://github.com/marketplace/actions/pytest-coverage-commentator
https://github.com/marketplace/actions/pytest-coverage-comment


chore(api-node): version

:tada: This PR is included in version 1.33.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Will this do dbf IV as well?

It will work with version 0x8b files which are dBase IV, and it may work with others in loose mode. I'd suggest reading the README regarding supported field types, and trying it out.


@docusaurus/Head meta contains data-rh=true, which leads to verification error in Baidu.com and Sogou.com

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
 generated with @docusaurus/Head is like:
<meta name="xxxxxx-verification" content="xxxxxx" data-rh="true">

Some search engines requires
<meta name="xxxxxx-verification" content="xxxxxx">

, and they are not smart enough verify a meta with data-rh.
Reproducible demo
No response
Steps to reproduce
import Head from '@docusaurus/Head';
        <Head>
            <meta name="baidu-site-verification" content="codeva-xxxxx" />
            <meta name="sogou_site_verification" content="xxxxx" />
        </Head>

Expected behavior
Although those search engines are stupid, but we also should not add anything we won't use.
Please remove the "data-rh" property.
<meta name="xxxxxx-verification" content="xxxxxx">

Actual behavior
<meta name="xxxxxx-verification" content="xxxxxx" data-rh="true">

Your environment

Public source code:
Public site URL: https://mactoys.eusoftbank.com
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

This is not added by us. Please report to https://github.com/staylor/react-helmet-async instead. It looks like they already have https://github.com/staylor/react-helmet-async/issues/12


Breakpoint pulling not working

I found this thread in the original repo and followed the instructions there on how to pull breakpoints but I'm still not able to get breakpoints added at runtime working.
Here's my launch.json:
  "configurations": [
    {
      "type": "lua-local",
      "request": "launch",
      "name": "Debug Love2d",
      "program": {
        "command": "love",
      },
      "args": [
        "_love2d",
        "LOCAL_LUA_DEBUGGER_VSCODE"
      ],
      "scriptRoots": [
        "_love2d"
      ],
      "pullBreakpointsSupport": true, // enabled support
    }
  ]

And my main.lua:
if os.getenv("LOCAL_LUA_DEBUGGER_VSCODE") == "1" then
  lldebugger = require("lldebugger")
  lldebugger.start()
end

-- ... etc

function love.draw()
    if os.getenv("LOCAL_LUA_DEBUGGER_VSCODE") == "1" then
      lldebugger.pullBreakpoints()
    end
    -- ... etc
end

It looks like this repo's readme hasn't been updated to include the new flag, but based on commit 54262e56ab35a00775ffed111780d3a858a8e82f I think this fork has the required changes?

Yes, pull breakpoints support has been merged. I have tried to reproduce your problem, but it works for me as expected (I am on 0.3.8). Have you set the breakpoint somewhere it definitely steps over or have you tried turning stepUnmappedLines on?

Ahhh. I just tested again and I think the nuance is that, if I start the debugger without any breakpoints, it won't break on any breakpoints that I add while its running.
However starting the debugger with at least one breakpoint, then adding new breakpoints while its running works correctly :tada:

This is odd behaviour, as I also started without any breakpoints and then added new ones, which worked fine for me.
Does this issue occur also with the code provided, or do you have a more complicated setup in which this issue occurs?

Doh, it is working fine 🤦
I do have a bit more complicated setup, so it was possible that when I was testing earlier, I was probably setting the breakpoints in the wrong Lua files (I generate final Lua files from source files).

Ah actually, I just realized what the nuance was!
As mentioned in my last comment, I have source Lua files that I do some processing on before I generate final Lua files.
If I set breakpoints in the final Lua files, everything works. However, if I set breakpoints in the source Lua files, that's where things start to get wonky. It seems the primary issue is when my processing steps add lines to the final Lua files that don't exist in the source files.
I attached a simple repo project. Specifically in this example, if you start debugging with no breakpoints, then add a breakpoint to main.lua in src, the line it pauses on is incorrect:
example.zip

You will have to generate source map files, in order for LLD to match lines back to its original source. I don't know the details for that, but here a quote from the README:

scriptFiles
A list of glob patterns identifying where to find Lua scripts in the workspace when debugging. This is required for placing breakpoints in sourcemapped files (ex. 'ts' scripts when using TypescriptToLua), as the source files must be looked up ahead of time so that breakpoints can be resolved.

The README doesn't explicitly say that you need .map files, but when I fiddled arround with the debugger (which is written in TypeScript and compiled to Lua) I noticed it used .map files to map Lua lines back to TypeScript lines.
So you will need to create adjacent .map files. A short search yielded this SO post about source maps. I can't help you much with that, but since I am interested in this topic as well, I'd apreciate if you keep me posted about the progress you've made.

Got it, thank you for your transparency! I also only had limited knowledge of source maps, so I had hoped maybe this debugger was doing something magic to generate them once started 😂
Doing a brief deep dive on sourcemaps, it seems doable for my tech stack. The trouble is that I use an external tool to process the Lua files and it doesn't appear to support generating source maps, so I'll have to figure out how to add support to the tool.
I think this will be a good feature to support, so I added a ticket in my project to capture this work. I'll close this for now, and hopefully remember to circle back if I figure out how to get it working.


PLT-5494 Added at mention detection

Right now, this works as at mentions on the webapp do where we trim punctuation off of the mention to see if we find a username, but if we run out of punctuation, we just assume that user exists and we haven't seen them yet. This'll need some changes when I have the at mentions stored with their ID.
Clicking on the at mentions also doesn't do anything right now since it's blocked on adding search (or whatever we decide to have them do)
Changes made for this PR (since this is on top of the autolinking and markdown PRs):
https://github.com/mattermost/mattermost-mobile/commit/77a43e8a5cdada0b0862fed84472518a1228268c (Code to render at mentions)
https://github.com/hmhealey/commonmark.js/pull/2 (Code to find at mentions in the text)
https://github.com/hmhealey/commonmark-react-renderer/pull/1 (Code to make renderer actually do something for at mentions)
https://github.com/mattermost/mattermost-redux/pull/12
Ticket Link
https://mattermost.atlassian.net/browse/PLT-5494
Checklist

Has UI changes
Added unit tests (see commonmark.js PR)

Device Information
This PR was tested on: iOS Simulator (iPhone 6, iOS 10.1)
Screenshots

Yeah, most of that code was from the markdown PR since I'm using the markdown parser to do at mentions now


fix offset always be in [0 leastWeight]

What is the purpose of the change
XXXXX
Brief changelog
XXXXX
Verifying this change
XXXXX
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
[ ] Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
[ ] If this contribution is large, please follow the Software Donation Guide.

Codecov Report

Merging #4456 into master will increase coverage by 0.06%.
The diff coverage is 60%.

@@             Coverage Diff              @@
##             master    #4456      +/-   ##
============================================
+ Coverage     62.92%   62.99%   +0.06%
  Complexity      450      450
============================================
  Files           770      770
  Lines         33005    33008       +3
  Branches       5216     5217       +1
============================================
+ Hits          20768    20792      +24
+ Misses         9841     9819      -22
- Partials       2396     2397       +1

Impacted Files
Coverage Δ
Complexity Δ

...bbo/rpc/cluster/loadbalance/RandomLoadBalance.java
82.6% <60%> (-7.4%)
0 <0> (ø)

...pache/dubbo/registry/support/AbstractRegistry.java
80.07% <0%> (+1.53%)
0% <0%> (ø)
:arrow_down:

...he/dubbo/registry/multicast/MulticastRegistry.java
69.68% <0%> (+1.8%)
0% <0%> (ø)
:arrow_down:

...exchange/support/header/HeaderExchangeHandler.java
67.21% <0%> (+2.45%)
0% <0%> (ø)
:arrow_down:

.../org/apache/dubbo/remoting/ExecutionException.java
21.05% <0%> (+5.26%)
0% <0%> (ø)
:arrow_down:

...ng/transport/dispatcher/all/AllChannelHandler.java
57.14% <0%> (+5.71%)
0% <0%> (ø)
:arrow_down:

.../remoting/transport/netty4/NettyClientHandler.java
68.42% <0%> (+7.01%)
0% <0%> (ø)
:arrow_down:

.../remoting/transport/netty4/NettyServerHandler.java
71.42% <0%> (+9.52%)
0% <0%> (ø)
:arrow_down:

...ache/dubbo/remoting/transport/AbstractChannel.java
87.5% <0%> (+12.5%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

Please describe your issue first.

你好，实际没有遇到问题。从代码上看，会存在这个bug。或者我没有完全理解，烦请给解答一下，代码中怎么避免[0 leastweight]区间，这种情况的。 zhangweitech<EMAIL_ADDRESS>签名由 网易邮箱大师 定制 On 07/03/2019 22:42, Huxing Zhang wrote: Please describe your issue first. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

你好，实际没有遇到问题。从代码上看，会存在这个bug。

Please clearly define what the bug is, how to reproduce it, what is the expected result, and what it the actual result. I suggest to create an issue and link to this pull request. This makes the maintainers quickly to know your purpose of your pull request.
I also suggest to add unit tests for your changes.

I check the code and I think you may misunderstand the algorithm

did we reach the consensus, and can this pull request be either closed or merged?

i check the original code, the logic is correct.

image this:
4 and 8
randam: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11
weight 4 will get 0, 1, 2, 3
weight 8 will get 4, 5, 6, 7, 8, 9, 10, 11
so, weight 8 has twice chance to get invoked than weight 4.

Ok。 zhangweitech<EMAIL_ADDRESS>签名由 网易邮箱大师 定制 On 07/16/2019 17:53, Ian Luo wrote: image this: 4 and 8 randam: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 weight 4 will get 0, 1, 2, 3 weight 8 will get 4, 5, 6, 7, 8, 9, 10, 11 so, weight 8 has twice chance to get invoked than weight 4. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.


No scrolling in set selection window

Nice timer. :-)
However, I have some problems to scroll down the list in the subset selection window. I have to resize the whole browser window first. Would be cool if you could fix this.
Browser: Chrome, version 44.0.2403.155 (64-bit), Mac OS X 10.10

Hmm, I'm not too sure... I'll look into it. But so far, it's fine (at least for me)...


Question on vision encoder resolution size

Hi all, I am currently playing with the CogVLM17b model (using this checkpoint: https://huggingface.co/THUDM/cogvlm-chat-hf). What is the resizing resolution of the vision encoder? The ending resolution during the training is 490 × 490 according to the paper, I assume this is also the image resolution used during inference? Thanks!

Closing this and moving to Q&A instead.


V0.2

Description

Simulation toolkit

VM allocation environment
Dashboard for CIM and CitiBike

RL toolkit

New RL abstraction
More RL algorithms

Distributed toolkit

maro cli refactoring
maro cli support windows
maro process mode
maro grass on-promise mode

Linked issue(s)/Pull request(s)

issue_number

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[x] New feature
[x] Test
[x] Doc update
[x] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[x] Windows
[x] Mac OS
[x] Linux

Python version:

[x] 3.6
[x] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[x] New release package
[x] New docker image

Checklist

[x] Add/update the related comments
[x] Add/update the related tests
[x] Add/update the related documentations
[x] Update the dependent downstream modules usage

Codecov Report

Merging #239 (2b5bbdb) into master (6a52323) will decrease coverage by 7.16%.
The diff coverage is 44.54%.

@@            Coverage Diff             @@
##           master     #239      +/-   ##
==========================================
- Coverage   72.06%   64.89%   -7.17%
==========================================
  Files          86      111      +25
  Lines        4066     5350    +1284
==========================================
+ Hits         2930     3472     +542
- Misses       1136     1878     +742

Flag
Coverage Δ

unittests
64.89% <44.54%> (-7.17%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

maro/communication/dist_decorator.py
18.51% <0.00%> (ø)

maro/communication/utils/default_parameters.py
100.00% <ø> (ø)

...o/simulator/scenarios/citi_bike/business_engine.py
74.21% <ø> (-0.49%)
:arrow_down:

maro/simulator/scenarios/citi_bike/common.py
70.83% <ø> (+1.94%)
:arrow_up:

...simulator/scenarios/citi_bike/decision_strategy.py
42.76% <ø> (ø)

maro/simulator/scenarios/helpers.py
70.00% <ø> (-4.33%)
:arrow_down:

maro/simulator/scenarios/matrix_accessor.py
77.27% <ø> (ø)

...mulator/scenarios/vm_scheduling/business_engine.py
20.40% <ø> (ø)

maro/simulator/scenarios/vm_scheduling/common.py
57.89% <ø> (ø)

...ro/simulator/scenarios/vm_scheduling/cpu_reader.py
97.61% <ø> (ø)

... and 97 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #239 (2b5bbdb) into master (6a52323) will decrease coverage by 7.16%.
The diff coverage is 44.54%.

@@            Coverage Diff             @@
##           master     #239      +/-   ##
==========================================
- Coverage   72.06%   64.89%   -7.17%
==========================================
  Files          86      111      +25
  Lines        4066     5350    +1284
==========================================
+ Hits         2930     3472     +542
- Misses       1136     1878     +742

Flag
Coverage Δ

unittests
64.89% <44.54%> (-7.17%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

maro/communication/dist_decorator.py
18.51% <0.00%> (ø)

maro/communication/utils/default_parameters.py
100.00% <ø> (ø)

...o/simulator/scenarios/citi_bike/business_engine.py
74.21% <ø> (-0.49%)
:arrow_down:

maro/simulator/scenarios/citi_bike/common.py
70.83% <ø> (+1.94%)
:arrow_up:

...simulator/scenarios/citi_bike/decision_strategy.py
42.76% <ø> (ø)

maro/simulator/scenarios/helpers.py
70.00% <ø> (-4.33%)
:arrow_down:

maro/simulator/scenarios/matrix_accessor.py
77.27% <ø> (ø)

...mulator/scenarios/vm_scheduling/business_engine.py
20.40% <ø> (ø)

maro/simulator/scenarios/vm_scheduling/common.py
57.89% <ø> (ø)

...ro/simulator/scenarios/vm_scheduling/cpu_reader.py
97.61% <ø> (ø)

... and 97 more

Continue to review full report at Codecov.

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


Server Crashes - Failed to Initialize SteamNetworking

Hi everyone, what all do I need to install on my Mac to get this running?  I tried running it with just Docker, pulling the image and running it in docker-compose.  However upon running it I get the following crash in my stack trace:
I am running macOS Monterey with a M1 Pro chip, so I'm curious to see if perhaps docker can't run it on this chipset?
v-rising  | dbus[123]: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file ../../../dbus/dbus-connection.c line 3544.
v-rising  | This is normally a bug in some application using the D-Bus library.
v-rising  |
v-rising  |   D-Bus not built with -rdynamic so unable to print a backtrace
v-rising  | wine: Assertion failed at address<PHONE_NUMBER>A41CE1 (thread 0028), starting debugger...
v-rising  | Waited for GameServer LogOn for over 30 seconds. Fatal error.
v-rising  | RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
v-rising  | 0x000000018050f71c ((<unknown>)) EntryPoint
v-rising  | 0x0000000180514843 ((<unknown>)) EntryPoint
v-rising  | 0x00000001804fdaed ((<unknown>)) EntryPoint
v-rising  | 0x0000000180ee63a9 ((<unknown>)) EntryPoint
v-rising  | 0x000000018098aaf4 ((<unknown>)) EntryPoint
v-rising  | 0x0000000002a6165a ((<unknown>))
v-rising  | 0x00000000027bd4a6 ((<unknown>))
v-rising  | 0x00000000033b8324 ((<unknown>))
v-rising  | 0x00000000018eb85d ((<unknown>))
v-rising  | 0x00000000021e9c29 ((<unknown>))
v-rising  | 0x0000000004719952 ((<unknown>))
v-rising  | 0x000000000471a5fc ((<unknown>))
v-rising  | 0x0000000001f78af3 ((<unknown>))
v-rising  | 0x0000000001ca08f6 ((<unknown>))
v-rising  | 0x00000000021f1d91 ((<unknown>))
v-rising  | 0x00000000024ff9db ((<unknown>))
v-rising  | 0x0000000000de018c ((<unknown>))
v-rising  | 0x0000000000caae39 ((<unknown>))
v-rising  | 0x00000001808c6028 ((<unknown>)) EntryPoint
v-rising  | 0x00000001808c9092 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180776639 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180777e27 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792e32 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792211 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180793f4d ((<unknown>)) EntryPoint
v-rising  | 0x00000001807928c3 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180794f99 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180795251 ((<unknown>)) EntryPoint
v-rising  | 0x000000018079dec3 ((<unknown>)) EntryPoint
v-rising  | 0x000000018078aadd ((<unknown>)) EntryPoint
v-rising  | 0x0000000180541223 ((<unknown>)) EntryPoint
v-rising  | 0x000000018054254b ((<unknown>)) EntryPoint
v-rising  | 0x00000001400011f2 ((<unknown>)) EntryPoint
v-rising  | <Missing stacktrace information>
v-rising  |
v-rising  | Failed to initialize SteamNetworking
v-rising  | RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
v-rising  | 0x000000018050f71c ((<unknown>)) EntryPoint
v-rising  | 0x0000000180514843 ((<unknown>)) EntryPoint
v-rising  | 0x00000001804fdaed ((<unknown>)) EntryPoint
v-rising  | 0x0000000180ee63a9 ((<unknown>)) EntryPoint
v-rising  | 0x000000018098aaf4 ((<unknown>)) EntryPoint
v-rising  | 0x0000000002a6165a ((<unknown>))
v-rising  | 0x00000000027bd4a6 ((<unknown>))
v-rising  | 0x00000000018eb8a8 ((<unknown>))
v-rising  | 0x00000000021e9c29 ((<unknown>))
v-rising  | 0x0000000004719952 ((<unknown>))
v-rising  | 0x000000000471a5fc ((<unknown>))
v-rising  | 0x0000000001f78af3 ((<unknown>))
v-rising  | 0x0000000001ca08f6 ((<unknown>))
v-rising  | 0x00000000021f1d91 ((<unknown>))
v-rising  | 0x00000000024ff9db ((<unknown>))
v-rising  | 0x0000000000de018c ((<unknown>))
v-rising  | 0x0000000000caae39 ((<unknown>))
v-rising  | 0x00000001808c6028 ((<unknown>)) EntryPoint
v-rising  | 0x00000001808c9092 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180776639 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180777e27 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792e32 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792211 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180793f4d ((<unknown>)) EntryPoint
v-rising  | 0x00000001807928c3 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180794f99 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180795251 ((<unknown>)) EntryPoint
v-rising  | 0x000000018079dec3 ((<unknown>)) EntryPoint
v-rising  | 0x000000018078aadd ((<unknown>)) EntryPoint
v-rising  | 0x0000000180541223 ((<unknown>)) EntryPoint
v-rising  | 0x000000018054254b ((<unknown>)) EntryPoint
v-rising  | 0x00000001400011f2 ((<unknown>)) EntryPoint
v-rising  | <Missing stacktrace information>
v-rising  |
v-rising  | Intentionally caused fatal error
v-rising  | RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
v-rising  | 0x000000018050f71c ((<unknown>)) EntryPoint
v-rising  | 0x0000000180514843 ((<unknown>)) EntryPoint
v-rising  | 0x00000001804fdaed ((<unknown>)) EntryPoint
v-rising  | 0x0000000180ee63a9 ((<unknown>)) EntryPoint
v-rising  | 0x000000018087d7c7 ((<unknown>)) EntryPoint
v-rising  | 0x00000001809adbe7 ((<unknown>)) EntryPoint
v-rising  | 0x00000000018eb8b2 ((<unknown>))
v-rising  | 0x00000000021e9c29 ((<unknown>))
v-rising  | 0x0000000004719952 ((<unknown>))
v-rising  | 0x000000000471a5fc ((<unknown>))
v-rising  | 0x0000000001f78af3 ((<unknown>))
v-rising  | 0x0000000001ca08f6 ((<unknown>))
v-rising  | 0x00000000021f1d91 ((<unknown>))
v-rising  | 0x00000000024ff9db ((<unknown>))
v-rising  | 0x0000000000de018c ((<unknown>))
v-rising  | 0x0000000000caae39 ((<unknown>))
v-rising  | 0x00000001808c6028 ((<unknown>)) EntryPoint
v-rising  | 0x00000001808c9092 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180776639 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180777e27 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792e32 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792211 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180793f4d ((<unknown>)) EntryPoint
v-rising  | 0x00000001807928c3 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180794f99 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180795251 ((<unknown>)) EntryPoint
v-rising  | 0x000000018079dec3 ((<unknown>)) EntryPoint
v-rising  | 0x000000018078aadd ((<unknown>)) EntryPoint
v-rising  | 0x0000000180541223 ((<unknown>)) EntryPoint
v-rising  | 0x000000018054254b ((<unknown>)) EntryPoint
v-rising  | 0x00000001400011f2 ((<unknown>)) EntryPoint
v-rising  | <Missing stacktrace information>
v-rising  |
v-rising  | Crash!!!
v-rising  | SymInit: Symbol-SearchPath: '.;Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer;Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer;C:\windows;C:\windows\system32;SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 534, UserName: 'steam'
v-rising  | OS-Version: 6.1.0
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\VRisingServer.exe:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 2<IP_ADDRESS>87
v-rising  | C:\windows\system32\ntdll.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.1.7601.24059
v-rising  | C:\windows\system32\kernel32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.1.7601.17514
v-rising  | C:\windows\system32\kernelbase.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\UnityPlayer.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 2<IP_ADDRESS>87
v-rising  | C:\windows\system32\USER32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\gdi32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\advapi32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\version.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\msvcrt.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 7.0.2600.2180
v-rising  | C:\windows\system32\ole32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\rpcrt4.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\SHLWAPI.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.0.2800.1692
v-rising  | C:\windows\system32\shcore.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\SETUPAPI.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\SHELL32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.0.2900.6242
v-rising  | C:\windows\system32\OPENGL32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2082
v-rising  | C:\windows\system32\WINMM.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\msacm32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\OLEAUT32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.0.6001.18000
v-rising  | C:\windows\system32\IMM32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\WINHTTP.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\jsproxy.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\ws2_32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.5512
v-rising  | C:\windows\system32\bcrypt.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.0.6000.16386
v-rising  | C:\windows\system32\HID.DLL:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\CRYPT32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.131.2600.1243
v-rising  | C:\windows\system32\api-ms-win-core-synch-l1-2-0.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-fibers-l1-1-1.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-localization-l1-2-1.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-winrt-l1-1-0.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\combase.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-com-l1-1-1.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-winrt-string-l1-1-0.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\winex11.drv:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\GameAssembly.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\IPHLPAPI.DLL:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\baselib.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-string-l1-1-0.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-datetime-l1-1-1.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-localization-obsolete-l1-2-0.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-core-sysinfo-l1-2-1.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\mmdevapi.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\winealsa.drv:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\api-ms-win-appmodel-runtime-l1-1-2.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\VRisingServer_Data\Plugins\x86_64\lib_burst_generated.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\VRisingServer_Data\Plugins\x86_64\fmodstudio.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\wbem\wbemprox.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\winspool.drv:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | C:\windows\system32\dxgi.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.0.6000.16386
v-rising  | C:\windows\system32\wined3d.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\rsaenh.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.2180
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\VRisingServer_Data\Plugins\x86_64\steam_api64.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\steamclient64.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\imagehlp.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\PSAPI.DLL:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 5.1.2600.3264
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\tier0_s64.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\vstdlib_s64.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\MSWSOCK.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: <IP_ADDRESS>
v-rising  | C:\windows\system32\Secur32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\netapi32.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\Kerberos.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\Wlanapi.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | Z:\home\steam\Steam\steamapps\common\VRisingDedicatedServer\VRisingServer_Data\Plugins\x86_64\stun_steamnetworking.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\dhcpcsvc.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: ''
v-rising  | C:\windows\system32\dbghelp.dll:<PHONE_NUMBER>000000), size: 0 (result: 0), SymType: '-unknown-', PDB: '', fileVersion: 6.1.7601.17514
v-rising  |
v-rising  | ========== OUTPUTTING STACK TRACE ==================
v-rising  |
v-rising  | RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
v-rising  | 0x0000000180EE7265 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180EE687C ((<unknown>)) EntryPoint
v-rising  | 0x000000018087D7C7 ((<unknown>)) EntryPoint
v-rising  | 0x00000001809ADBE7 ((<unknown>)) EntryPoint
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>8EB8B2)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>8EB8B2)
v-rising  | 0x00000000018EB8B2 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>1E9C29)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>1E9C29)
v-rising  | 0x00000000021E9C29 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>719952)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>719952)
v-rising  | 0x0000000004719952 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>71A5FC)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>71A5FC)
v-rising  | 0x000000000471A5FC ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>F78AF3)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>F78AF3)
v-rising  | 0x0000000001F78AF3 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>CA08F6)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>CA08F6)
v-rising  | 0x0000000001CA08F6 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>1F1D91)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>1F1D91)
v-rising  | 0x00000000021F1D91 ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>4FF9DB)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>4FF9DB)
v-rising  | 0x00000000024FF9DB ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>DE018C)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>DE018C)
v-rising  | 0x0000000000DE018C ((<unknown>)) (function-name not available)
v-rising  |   ERROR: SymGetSymFromAddr64, GetLastError: 'Module not found.' (Address:<PHONE_NUMBER>CAAE39)
v-rising  |   ERROR: SymGetModuleInfo64, GetLastError: 'DLL initialization failed.' (Address:<PHONE_NUMBER>CAAE39)
v-rising  | 0x0000000000CAAE39 ((<unknown>)) (function-name not available)
v-rising  | 0x00000001808C6028 ((<unknown>)) EntryPoint
v-rising  | 0x00000001808C9092 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180776639 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180777E27 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792E32 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180792211 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180793F4D ((<unknown>)) EntryPoint
v-rising  | 0x00000001807928C3 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180794F99 ((<unknown>)) EntryPoint
v-rising  | 0x0000000180795251 ((<unknown>)) EntryPoint
v-rising  | 0x000000018079DEC3 ((<unknown>)) EntryPoint
v-rising  | 0x000000018078AADD ((<unknown>)) EntryPoint
v-rising  | 0x0000000180541223 ((<unknown>)) EntryPoint
v-rising  | 0x000000018054254B ((<unknown>)) EntryPoint
v-rising  | 0x00000001400011F2 ((<unknown>)) EntryPoint
v-rising  | <Missing stacktrace information>
v-rising  |
v-rising  | ========== END OF STACKTRACE ===========
v-rising  |
v-rising  | A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:
v-rising  |  * C:/users/steam/Temp/Stunlock Studios/VRisingServer/Crashes

Further up in the stack trace I noticed this too:
v-rising  | 002b:err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth >= 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.

I had the same issue when using volume bind, search for Unauthorized access on your log maybe (probably write permissions on the /saves folder)
Fixed it by using a docker volume instead.
On your docker compose:
version: '3.7'

services:
  vrising:
...
    volumes:
#      - type: bind
#        source: ./saves
#        target: /saves
      - vrisingsaves:/saves
...
...
volumes:
  vrisingsaves:

Do you have xquartz installed?  Or do I need anything installed in addition to docker?

Nothing else installed in addition to docker.
The r/w access might be related to this thread:
https://stackoverflow.com/questions/34031397/running-docker-on-ubuntu-mounted-host-volume-is-not-writable-from-container
I also had success by creating a folder outside /root
volumes:
      - /data/opt/vrising:/saves

Hi,
I just wanted to add that I was also experiencing the crash because the container runs as the user steam and doesn't seem to have the permissions to write in the /saves folder from the start.
I had to bind it to an /opt folder on the host and give that a chmod -R a+rw saves but ultimately it gets created under user 1000:1000 so a chown -R 1000:1000 saves works just as well. If anyone has a better fix I'm all ears.
Thanks,

Do you have xquartz installed? Or do I need anything installed in addition to docker?
Also, what should does your save directory look like? I simply copied over my local saves into saves

I see the issue, you need to have your save files in the /saves/Saves folder. There the server will find the save files and use them (given there is write access).


Font rendering issue on Surah bakarah verse 72 (2:72)

I have noticed a font rendering issue with the current production site and also the beta one.
It only happens when I have the Uthmani Text selected.

Correct form (in king fahad version)
Wrong form (in Uthmani text version)

Assalamu alaikum brother @ahmedre, can we have any solution for this? The same issue is present in our app.

wa3laikum alsalam,
@mustafa0x any ideas here - seeing something similar when using Kitab also (though admittedly have not updated to the newest version yet).
walsalam 3alaikum

This and لِیَسُـࣳۤـُٔوا۟ are the two most difficult words in the qur'an to render. فَٱدَّ ٰرَ ٰٔۡ تُمۡ used to render fine but now it's off. فَٱدَّ ٰرَ ٰ ٔتُمۡ looks better but don't know if it's worth making the change (as it may break later too). Needs thought.

An old version of Me Quran (v1.003) font with the Quran Academy text renders perfectly

The hamzah should be over the alif, not under.

More issues with the Uthmani text:

Compared with a more readable King Fahad Complex Quran 1

From:
https://quran.com/104/7

The kasra on ل joins ع in a way it makes it non-legible.
The letters ف and أ join in a way that it looks like a ق in in the word ٱلْأَفْـِٔدَةِ

Issues like this can cause misreading.


tauri-shared-memory 如何读写共享内存数据

Describe the bug
tauri-shared-memory 如何读写共享内存数据找不到相关文件信息
Reproduction
tauri-shared-memory 如何读写共享内存数据找不到相关文件信息
Expected behavior
No response
Platform and versions
tauri-shared-memory 如何读写共享内存数据找不到相关文件信息

Stack trace
No response
Additional context
No response

I recently answered this in the wry repo: https://github.com/tauri-apps/wry/issues/1035#issuecomment-1762779578 - tldr: It's not possible yet but something we'd love to see.


fix: missing virtualenv prompt

i am using the bakke theme and just noticed that it does not display a potential virtual environment in the prompt. this pull request fixes this issue; it’s just a minimal change.

Great - thanks!


Feature Request/Idea: implement Semantic Layer

Semantic Layer helps to automatically select context saved into vector database based on user prompt and are more suitable for individual functions guardrailing LLM to better work with the function.

Hi @qdrddr could you give some pseudocode or a description of a use case to illustrate what this would do and how you would use it? Thanks

Closing this to tidy issues, but feel free to reopen.


Size Classes removed from spectrum-Tabs class

Description
The spectrum-Tabs class definition at<EMAIL_ADDRESS>has removed all of the size classes spectrum-Tabs--size* for -<EMAIL_ADDRESS>The style classes are in<EMAIL_ADDRESS>The end result is that the styling for the tabs is incorrect.- the left and right margins for each tab are 0px.

produces

Steps to reproduce

Go to http://opensource.adobe.com/spectrum-css/
Click on ...
Observe ...

Expected behavior

Screenshots

Environment

Spectrum CSS version:
Browser(s) and OS(s):

Additional context

👋🏻 Hi @mscherotter,
Thanks for reporting this. This issue should be corrected in the latest release of the Tabs component, which is: 3.2.59.


Update configure-wd-app-guard.md

@chintanpatel,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Tools: bucket rewrite tool doesn't work with dry run and multiple block IDs

Thanos, Prometheus and Golang version used: main

When using bucket rewrite tool with dry run mode and specifying multiple blocks, it only processes the first block and the process exits.
From the code https://github.com/thanos-io/thanos/blob/main/cmd/thanos/tools_bucket.go#L1137, it returns nil when dry run mode is enabled. It should continue execution in this case.

Just to double check. For each specified block, rewrite tool will rewrite it separately. Is this intended or should it rewrite all specified blocks into a larger one?
cc @bwplotka

Close this for now.


Sax cleanup

Use dynamic dispatch for nessus_sax_listener.rb.
Converted some of the instance variables to private class constants as they were acting like constants anyway. <- for nessu_sax_listener.rb and simple_nexpose.rb parsers.
Will probably refactor the dispatch methods into modules later on.
All specs passing.

Merged this with my 1.7.3 dev branch, so far all is well. Going to Close the PR for now, this will be in the next release.


UI for the showing/hiding/dismissing/accessing the survey

Task/Issue URL: https://app.asana.com/0/0/1207179707350729/f
Description
Adds an autofill survey to the autofill management screen. The survey will be available for a few app versions and removed after a few weeks.

We decided to hardcode it for the first one on the assumption we wouldn't use this much again.
If it seems like something we'd do more often then will tie it into remote config

Screenshot

Steps to test this PR
Check the survey prompt shows up

[ ] Visit autofill management screen (Settings -> Passwords)
[ ] Verify you see the survey prompt
[ ] Verify m_autofill_management_screen_visit_survey_available pixel fires

Check that it keeps showing up

[ ] Leave the screen and return; verify prompt is still there

Check dismiss behaviour

[ ] Tap the ❌ on the survey; verify it disappears
[ ] Leave the screen and return; verify it does not come back

Check you can take the survey

[ ] Reset app data, and return to autofill management screen
[ ] This time, choose to take the survey; verify the survey loads in a tab and you can complete it
[ ] Return to autofill management screen; verify the survey prompt is gone

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4476
#4475  👈
#4474
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CDRussell and the rest of your teammates on  Graphite

re onboarding prompts, will discuss in Do we need to wait until user has finished onboarding prompts?

Merge activity

May 9, 5:30 PM EDT: @CDRussell started a stack merge that includes this pull request via Graphite.


More missing keywords

Hello,
Was testing the plugin and seems there are some important keywords missing to be highlighted:
request
assert
read()
Also found these other ones that are not that mandatory but can come handy
headers
cookie
cookies
params
response
eval
Mostly I was testing the official karate github page, there is a table for the keywords

Thanks, i will get a release out soon!

Thanks, seems working!


Stops on mobile with apply error

Hi
I seem to be running into the issue below when running on mobile within the chrome browser
I am testing with this url.
https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/423905808/Sport5&ciu_szs&gdfp_req=1&env=vp&output=xml_vmap1&unviewed_position_start=1&cust_params=sample_ar=premidpostpod&deployment=gmf-js&cmsid=496&vid=short_onecue&correlator=3775340396490042&ad_rule=1&sdkv=h.3.156.0&sdki=3c09&scor=294187626513507&adk=2588068644&osd=2&frm=1&sdr=1&mpt=videojs-ima&mpv=0.2.0&url=http://qa-m.sport5.co.il/articles.aspx?FolderID=378&docID=146627&lang=He&ged=ve4_td20_tt2_pd20_la20000_er499.0.499.0_vi400.0.880.320_vp0_eb16619
Uncaught TypeError: Cannot read property 'apply' of undefined
    at Jq (ima3.js:303)
    at Hq.K (ima3.js:304)
    at Zg (ima3.js:82)
    at tq.h.dispatchEvent (ima3.js:80)
    at tq.w (ima3.js:294)
    at Wg (ima3.js:77)
    at Sg (ima3.js:78)
    at ima3.js:76

I am using video js setup like this.
var videoPlayer = videojs("video");
videoPlayer.ima({
    id: "video",
    adTagUrl: "https://pubads.g.doubleclick.net/gampad/ads?sz=640x480&iu=/423905808/Sport5&ciu_szs&gdfp_req=1&env=vp&output=xml_vmap1&unviewed_position_start=1&cust_params=sample_ar=premidpostpod&deployment=gmf-js&cmsid=496&vid=short_onecue&correlator=3775340396490042&ad_rule=1&sdkv=h.3.156.0&sdki=3c09&scor=294187626513507&adk=2588068644&osd=2&frm=1&sdr=1&mpt=videojs-ima&mpv=0.2.0&url=http://qa-m.sport5.co.il/articles.aspx?FolderID=378&docID=146627&lang=He&ged=ve4_td20_tt2_pd20_la20000_er499.0.499.0_vi400.0.880.320_vp0_eb16619"
});

videoPlayer.ima.initializeAdDisplayContainer();
videoPlayer.ima.requestAds();

videoPlayer.one("click", function() {
    videoPlayer.play();
});

"video.js": ">= 5.15.1",
Any suggestions where i might be going wrong?
Thanks ;)

Hey there,
Thanks for the details info. It looks likes something funky is happening in the IMA SDK. I've sent this info to the rest of the team for debugging.
Thanks,
Shawn Busolits
IMA SDK Team

@shawnbuso thanks for the update ;)

Hello guys,
I'm having the same issue, the line which seems to be generating the issue is in the "Fq" function:
return document.createTouchList.apply(document, a)
I looked up the function document.createTouchList and it seems to be depricated:
https://developer.mozilla.org/en-US/docs/Web/API/Document/createTouchList
Any thoughts?

Hey Shawn,
Do you happen to know if this issue was addressed / solved?
Thanks a bunch!

Hi all,
This is indeed an IMA bug, but it's currently limited to the mobile emulator on desktop Chrome. If you're seeing this issue on the mobile browser on a mobile device let us know. In the meantime we'll continue to look into a resolution for the issue on the mobile emulator.
Thanks,
Shawn

Hi All,
Is there any workaround for this issue yet?

I'm seeing similar behavior:
Uncaught TypeError: Cannot read property 'apply' of undefined
at gp (ima3.js:723)
at ep.M (ima3.js:724)
at Ag (ima3.js:492)
at Q (ima3.js:490)
at Ro.B (ima3.js:714)
at xg (ima3.js:488)
at ug (ima3.js:489)
at ima3.js:486

any update?

Are you seeing this on device? Up to this point we had only seen this when emulating a mobile device in Chrome. If you're seeing this on-device can you give us a sample page and device info so we can reproduce on our end?

In the videojs.ima.css file you should locate the .ima-ad-container class and remove the "height" parameter. It worked for me.

Hi, unfortunately we can‘t reproduce the bug again.
Probabbly it was only for a specific VPAID2 ad creative.
@renewj did you removed "width" from this block ?
videojs.ima.css
.ima-ad-container {
	top: 0px;
  	position: absolute;
  	display: block;
  	width: 100%;
  	height: 100%;
}

Does removing the width makes really sense ?

Empirically made sense. I followed the GLStephen hint by removing small parts of the css file until it worked. And, you can reproduce the error by opening this page: https://googleads.github.io/videojs-ima/examples/simple/ (inspect with Chrome mobile version)


Percentage Calculator

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
I can add a percentage calculator to CalcDiverse. Kindly assign me this under SWOC.
Screenshots
No response
Code of Conduct

[X] I follow Contributing Guidelines of this project.

Please assign me this issue. I want to contribute.

Assigning you, Proceed!! @Shreyansh-333

Same issue already exist @Shreyansh-333


Support Key Vault Referencing for Azure Function Java Local Development

The Azure Functions Java project located here https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-java-maven is extremely helpful but when doing local development it unfortunately doesn't support Azure Key Vault referencing in local.settings.json as documented here https://azure.microsoft.com/en-us/blog/simplifying-security-for-serverless-and-web-apps-with-azure-functions-and-app-service/ and https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references.  Key Vault referencing works fine when the function app is deployed in Azure.
Is it possible to add this support for local development?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e656bde5-b5d8-8d80-b7b3-ab430e57613e
Version Independent ID: 329eb12f-7302-4ecf-c1bf-a50ba3f34bdf
Content: Create your first function in Azure with Java and Maven
Content Source: articles/azure-functions/functions-create-first-java-maven.md
Service: azure-functions
GitHub Login: @rloutlaw
Microsoft Alias: routlaw, glenga

@edavedian Thanks for your feedback! We will investigate and update as appropriate.

@edavedian The key vault references feature requires RBAC permission to the key vault which won't work for local development. Also, note that key vault references currently only support system-assigned managed identities.
This feature is only meant for the applications hosted in Azure. You can write custom code to retrieve secrets from key vault instead if possible.

@KetanChawda-MSFT Thank you very much.  System-assigned managed identities work for local development when the identity of the user is authorized in the key vault.  I have already been doing this for a while in other projects.  Please refer to the second paragraph in https://docs.microsoft.com/en-us/azure/key-vault/service-to-service-authentication on how a developer's credentials are used for local development when using system assigned managed identities.  Additionally it is not efficient to maintain additional code that is only necessary for local development.  Any possibility that this feature can be supported as described in the documentation I pasted above.

Unfortunately, this isn't supported yet for local development. Work for it is underway, No ETA currently.
Here is a PR for supporting Key Vault in the Functions Host and the issue for tracking its integration with core tools.
Since there is no doc update required, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


How to set the "Authorization callback URL" within Github

I used the docker image drone:drone:0.4.0, and set the Application callback URL as
http://drone.linoxide.com/api/auth/github.com , as the official user guide says.
But I get an error respond from trying to  retrieve the URL : http://drone.linoxide.com/api/auth/github.com?error=redirect_uri_mismatch&.....
What should I do， please give some advice, thanks.

@qq511700505 please read the official drone documentation (anything referring to api/auth/github.com is very outdated). http://readme.drone.io
also per the issue template, please use the gitter room for questions and reserve the issue tracker for bugs


Upgrade versions of redoc and swagger plugins

Use latest versions of the swagger plugin and redoc plugin.
Fixes vulnerable dependencies from maven:org.webjars:swagger-ui:3.52.5
CVE-2021-46708 6.1 Improper Restriction of Rendered UI Layers or Frames vulnerability with Medium severity found
CVE-2018-25031 4.3 Improper Input Validation vulnerability with Medium severity found

We're keeping the same versions on purpose, they're introducing breaking changes quite often and these CVEs are usually not really an issue for us. Did you test these 2 new versions? :thinking:

these CVEs are usually not really an issue for us

Are you sure they are not an issue? I have to write a justification for a security exception on this and it would be nice if there was an official statement from the project that these vulnerabilities do not apply.

It's not the issue, but I've got some time to test it on my own & submit a patch. Let's jump the latest version for both, Swagger & ReDoc :ok_hand:

Released as 6.3.1-SNAPSHOT :)

Nice! I just tested the Swagger plugin locally. Looks good! Thank you!

Great! It'll be available in the next stable build alongside new Javalin version.