not able to write text at bottom of file

Hi,
I am using pdfkit successfully and able to write text to multiple coordinates as shown in attached pdf.
I am having issues writing to the bottom/right side/edges of the pdf.
when writing to the right side of the page - it has a tendency to wrap and go to next line even if I see plenty of space in right side.
Similarly, when writing to the bottom, it goes to next page even if sufficient space is available at the bottom.
As you see in the pdf attached, the image has plenty of space at the bottom where I want to write.  But after certain coordinates (712 on Y-axis) text moves to next page.
`var doc = new pdf({
size: 'letter',
layout  : 'portrait',
	margin : {
		top : 0.095 * 72,
		left: 0.2 * 72,
		right: 0.2 * 72,
		bottom: 0
	}
});

doc.pipe(fs.createWriteStream(__dirname + "/pdf/" + name));
// doc.pipe (fs.createWriteStream('foo.pdf'));
// doc.pipe(fs.createWriteStream(__dirname + "/pdf/" + name));

//add background image
doc.image(__dirname + "/cms1500.png", {
	x: 0.2 * 72,
	y: 0.095 * 72,
	width: (612 - 2 *0.2 * 72),
	height: (792 - 2  *0.095 * 72)
});

doc.font('Times-Roman');
doc.fontSize(8);

for (var i=0; i< 713; i++){
doc.text (i + " => do you see me ", 380, i);
}
//-
doc.on('end', function() {
	console.log("pdf created");
	return cb(true);
});
//--

doc.end();

58bdcd68b84b6c14900c1471.pdf
`

I am seeing the same exact thing, and it is not at all expected.

Hi @prescottprue , I was able to fix this problem by removing margin properties.
please reset your marging property.
main issues :
margin : {
top : 0.095 * 72,
left: 0.2 * 72,
right: 0.2 * 72,
bottom: 0
}

That got me on the right track, but I had to pass the settings to the constructor when creating the doc like so:
const pdfDoc = new PDFDocument({
  margins: {
    bottom: 0,
  }
});

Sweet. Thank you

I am having the same issue. When i try to write text to the bottom of the page, a new page is created with the text in the wrong position.
var doc = new PDFDocument({
    size: [5 * 72, 3 * 72],
    margin: {
        top: 0,
        left: 0,
        right: 0,
        bottom: 0
    }
});

var stream = doc.pipe(blobStream());

doc.text('20', 10, 20);
doc.text('50', 10, 50);
doc.text('80', 10, 80);
doc.text('110', 10, 110);
doc.text('131', 10, 131);

As soon as i try to add text beyond 130 pt, a new page is added. As you can see I am working with an index size sheet.
Here is the result:

@kbrock84 thank you for your EDIT section. commenting out this stuff does the trick for me (rendering large text at the bottom of the document without adding a new page). i think it would be nice if there would be an option for that instead of hacking :-).

doc.text(text, x, y, {height: doc.page.height}) works for me. However I cannot change the color of the font


[ANDROID] The animation object crashes the engine when splitting the spritesheet into its individual frames.

http://stackoverflow.com/questions/40022729/monogame-on-android-crashes-when-cutting-a-spritesheet

Added a workaround for this in version 0.71, it still doesn't work but at least will not crash the game.

The problematic line of code is actually textureAtlas.Image.GetData(0, FrameRect, FrameData, 0, FrameData.Length);

https://github.com/MonoGame/MonoGame/issues/5229

Fixed in version 0.75.


#6137 add -Pquick option

Signed-off-by: Nigel Jones<EMAIL_ADDRESS>

Description
Adds -Pquick maven build option
Skips many build checks
See #6137 for details
How Has This Been Tested?
Build
Any additional notes for reviewers?

Currently you must use this option in conjunction with -DskipFVT otherwise FVTs will fail

Still looking at how to resolve this user impact - see #6137 for discussion
Leaving as draft..

I'm inclined to stick with this simple option for the first PR, it at least reduces the number of parks
needed
I'd rather not do further changes just prior to release
Gradle is already quick, and probably where we should focus moving forward
cc: @mandy-chessell


[Question] Remote Config doesn't build on M1

[REQUIRED] Please fill in the following fields:

Unity editor version: 2020.3.45f1
Firebase Unity SDK version: 10.5.0
Source you installed the SDK: .unitypackage(.unitypackage or Unity Package Manager)
Problematic Firebase Component: Remote Config (Auth, Database, etc.)
Other Firebase Components in use: Analytics and Cloud Messaging (Auth, Database, etc.)
Additional SDKs you are using: FacebookSDK, Appsflyer, IronSource (Facebook, AdMob, etc.)
Platform you are using the Unity editor on: Mac M1 (Mac, Windows, or Linux)
Platform you are targeting: Android and iOS (iOS, Android, and/or desktop)
Scripting Runtime: IL2CPP (Mono, and/or IL2CPP)
Pre-built SDK from the website or open-source from this repo: from official website

[REQUIRED] Please describe the question here:
Hey. I'm trying to implement Firebase into my project. Seems like it works all fine on both Android and iOS. It builds on my MacOS(intel) but when I try to build it on cloud machine which is MacOS M1 it fails. Errors from the log:
▸ Linking UnityFramework

❌  Undefined symbols for architecture arm64
> Symbol: _Firebase_RemoteConfig_CSharp_FirebaseRemoteConfigInternal_App_get
> Referenced from: _FirebaseRemoteConfigInternal_get_App_m6BAB3BFD1C6EBF076C15281D4EA70FE699C2EBA7 in Firebase.RemoteConfig.o
❌  ld: symbol(s) not found for architecture arm64
❌  clang: error: linker command failed with exit code 1 (use -v to see invocation)

** ARCHIVE FAILED **
The following build commands failed:
Exit status: 65

Any ideas what could be the problem?

Hi @EAdemov,
Thanks for bringing this to our attention. Could you confirm if the issue persists with just the Firebase SDK in your implementation? You may try out our quickstart so that we can isolate whether the SDK is causing this behavior.

Hey. I tried to build with Analytics and it seems it worked fine on M1. But when imported Remote Config it pretty but started this issue.

Thanks for the additional input, @EAdemov. I've utilized the quickstart, but I was able to build with no issue. Could you provide a minimal, reproducible example that demonstrates your issue so we can identify what's causing this behavior? Additionally, could you try if updating your Unity editor makes any difference? 2021.3.19f1 is the latest LTS version of the editor.

I will try to update the Unity editor. I'm pretty outdated.

Okay sorry for the late reply it was something really stupid by my side. Apparently I forgot to add some of the files in the Plugins folder to .gitignore. It works fine right now.


Make use of new box types

The documentation has multiple box types:

Note
Warning
Tip
Bestpractice
Deprecated

There are approximately 200 boxes plus some inline deprecation warnings. We should go through the docs and update the box types / apply them to the text where possible.

Fixed via #2290


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 878

Questions ?
Please refer to the Backport tool documentation


Nightly K8s Matrix CI 2023-07-25: Failed

action url: https://github.com/spidernet-io/spiderpool/actions/runs/5661331216

The reasons for failure in ci are as follows:

The ipv6 abbreviation problem is similar to the #2070 problem.
Randomize to overlapping IP addresses, will be fixed in #2073
Deleted multus cr but didn't rebuild automatically?

{"level":"INFO","ts":"2023-07-25T20:38:28.058Z","logger":"MultusConfig-Informer","caller":"multuscniconfig/multusconfig_informer.go:337","msg":"try to create net-attach-def &{{ } {test-multus-1a20fec71f  ns-98242f597f    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [{spiderpool.spidernet.io/v2beta1 SpiderMultusConfig test-multus-1a20fec71f 2cb8ffd1-4ac3-448b-939e-8be980f5c046 0xc001691f99 0xc001691f98}] [] []} {{\"cniVersion\":\"0.3.1\",\"name\":\"test-multus-1a20fec71f\",\"plugins\":[{\"type\":\"macvlan\",\"ipam\":{\"type\":\"spiderpool\"},\"master\":\"eth0\",\"mode\":\"bridge\"},{\"type\":\"coordinator\",\"ipam\":{},\"dns\":{},\"detectGateway\":false,\"tunePodRoutes\":true,\"mode\":\"disabled\",\"hostRuleTable\":500,\"detectIPConflict\":false}]}}} for MultusConfg ns-98242f597f/test-multus-1a20fec71f"}

If the Multus net-attach-def was deleted, the SpiderMultusConfig informer would recreate it after 1 minute. So, the e2e case need to improve the check duration.
@ty-dc


Upgrade bashio to v0.7.1

Proposed Changes
Upgrade bashio to v0.7.1 to up to date.

Thank you, for helping, but this is not enough and not that easy.

@frenck Thanks for looking at this.
Can you elaborate on what is missing?

For starters, this is a drive-by PR (as it is called). Done from the browser.
Bashio has backward-incompatible changes, the fact this is a drive-by PR and the backward changes are not handled, makes this PR untested and incomplete.
That is not helping, but adding a risk. Hence, me closing.

That adds more context to it. Thanks.


How does this benefit me vs using the standard Twig autoloader?

Not really an issue I guess, but a clarification as I decide to move forward on a new development project... what does the do to benefit a developer over simply installing Twig and using it from the core Twig_Loader?

I'm also interested in this. Additionally, is it safe for production use, or are there a lot of breaking changes with plugin updates.

Hi @webivation @christianmagill the big benefit of using Timber versus directly using the Twig auto loader is access to native WordPress items inside of an object that's prepared for Twig. For example, if you wanted to write a conditional based on the size of a post thumbnail...
Timber
{% if post.thumbnail.width > 500 %}

{ % else %}

{% endif %}

Could you do this all with PHP + Twig? Sure. But you'd basically be duplicating the work that's already been done here.
In terms of production: Timber is being used in Production on tons of sites. I'm very actively working on an official 1.0 release which will contain some breaking changes; but these are focused on removing some functions/properties that have been deprecated for a long time. The 1.0 release isn't about any big new features, but cleaning up the code base so that the gunk is gone (and more thorough documentation exists) and you can feel better about using in production.

@jarednova Much thanks, looking forward to jumping in!


Expose type AbortableAsyncIterator

Stream-based responses like the one that is returned from the ollama.chat call below are of type AbortableAsyncIterator.
const response = await ollama.chat({ model: 'llama3.1', messages: [message], stream: true });

However, the type AbortableAsyncIterator is unfortunately not exported, so we cannot use it directly to specify the type of such values (when writing TypeScript).
Would be great if AbortableAsyncIterator would be exposed in index.d.ts/browser.d.ts.

Looks like a duplicate of https://github.com/ollama/ollama-js/issues/135

right, closing in favor of #135


I will do it

no not in single program add 4-5 different program or in single


Tarball URL erased when compiled

# requirements.in
#dramatiq[rabbitmq,watch]~=1.11
https://github.com/AstraLuma/dramatiq/archive/refs/heads/injectables.tar.gz#egg=dramatiq[rabbitmq,watch]
flask-melodramatiq

becomes a few different wrong things.
(This is a modified fork because I've been waiting for the PR to be reviewed for several months.)
Environment Versions

OS Type: Mac
Python version: 3.9.7
pip version: None (installed with pipx, not using pip-sync)
pip-tools version: 6.4.0

Steps to replicate

Use the above requirements.in snippet
Compile

Expected result
Both extras and URL are preserved.
Actual result
One or the other has been dropped.

Let me know if you disagree, but I think there are a two separate things going on here:

The URL requirement for dramatiq is missing its extras in the output. This looks like a potentially intentional change in https://github.com/jazzband/pip-tools/pull/1453/files#r671595549.
The dependencies introduced by the extras are missing. I still believe this is fixed by #1519 , which produces the following output:

#
# This file is autogenerated by pip-compile with python 3.8
# To update, run:
#
#    pip-compile
#
click==8.0.3
    # via flask
dramatiq @ https://github.com/AstraLuma/dramatiq/archive/refs/heads/injectables.tar.gz
    # via
    #   -r requirements.in
    #   flask-melodramatiq
flask==2.0.2
    # via flask-melodramatiq
flask-melodramatiq==0.3.9
    # via -r requirements.in
gevent==21.8.0
    # via watchdog-gevent
greenlet==1.1.2
    # via gevent
itsdangerous==2.0.1
    # via flask
jinja2==3.0.2
    # via flask
markupsafe==2.0.1
    # via jinja2
pika==1.2.0
    # via dramatiq
prometheus-client==0.12.0
    # via dramatiq
watchdog==2.1.6
    # via
    #   dramatiq
    #   watchdog-gevent
watchdog-gevent==0.1.1
    # via dramatiq
werkzeug==2.0.2
    # via flask
zope.event==4.5.0
    # via gevent
zope.interface==5.4.0
    # via gevent

# The following packages are considered to be unsafe in a requirements file:
# setuptools

Notice that pika et al are here, even though the extras are not mentioned in the dramatiq requirement. Only the output formatting is missing the extras.
Regarding the URL requirement's formatting, it looks like the grammar in https://www.python.org/dev/peps/pep-0508/ supports extras, if we want to add them. The test in https://github.com/jazzband/pip-tools/pull/1453/files#r671595549 fails with that change, so we should decide what behavior is preferred. @atugushev ?

Yeah, those seem to be the reproducible issues.
I should probably start from the un-reduced requirements.in file and see where it stopped doing the "drop the url" thing.

References with #1608


InfluxDB binding as stable candidate

Describe the proposal
Create certification tests for InfluxDB binding and mark it as stable candidate:
https://docs.dapr.io/reference/components-reference/supported-bindings/influxdb/

Test Plan Draft
Proposed tests (Certification)

Test sending /receiving data between single partition

Start an app with 1 sender and 1 receiver
Provide multiple partitions but store data in one partition
Receiver should only receive message from one partition
Sends 100+ unique messages
Simulates periodic errors
Confirm that all expected messages were received
Confirm that receiver does not receive messages from other than one partition

Test sending /receiving data multiple partitions/sender and receivers

Start an app with 1 sender and 1 receiver
Send data from 2 partitions
Sends 100+ unique messages
Simulates periodic errors
Confirm that all expected messages were received
Confirm  messages were received from all partitions

Test reconnection

Start an app with 1 senders and 1 receivers
Send 100+ unique messages from 1 sender
Interrupt the connection
Confirm that all expected messages were received by respective receiver

@tanvigour Please change test plan to reflect the operations in the binding being tested create and query. When you say receiving I am assuming querying? Is that correct? And sending is create operation?
Also a side note docs need to be updated to include request response pattern for create operation.

Removing this from all milestones. Nobody has mentioned this component.. ever. And nobody is working on it.
We might even want to consider not further investing in this component.


🐛 Building android with React Native 0.71

What were you trying to do?
Hello,
I am trying to build my application for android.
On iOS, it builds well and launches.
I use react-native-reanimated : 2.14.1.
I get these warings and errors on the android build :
> Configure project :react-native-vision-camera
VisionCamera: node_modules/ found at: /Users/***/node_modules
VisionCamera: Building with JSC...
Warning: The 'kotlin-android-extensions' Gradle plugin is deprecated. Please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with View Binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.
VisionCamera: Frame Processors are enabled! Building C++ part...
WARNING:DSL element 'dexOptions' is obsolete and should be removed.
It will be removed in version 8.0 of the Android Gradle plugin.
Using it has no effect, and the AndroidGradle plugin optimizes dexing automatically.

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/***/node_modules/react-native-vision-camera/android/build.gradle' line: 279

* What went wrong:
A problem occurred evaluating project ':react-native-vision-camera'.
> Expected directory '/Users/***/node_modules/react-native/android' to contain exactly one file, however, it contains no files.

Any idea if vision-camera is ready for react-native 0.71?
Thank you for your work!
Reproduceable Code
No response
What happened instead?
I get a gradle build error.
Relevant log output
No response
Device
Any
VisionCamera Version
^2.15.2
Additional information

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

I also face with this issue. :(

I guess this is the reason (from node-modules/android/README.md):
Starting from React Native 0.71, we're not shipping the `/android` folder inside the React Native NPM package
anymore due to sizing constraints on NPM.
...
If you're a library author and you're manipulating the React Native .aar files, to extract headers,
extract `.so` files or do anything with it, you're probably doing something wrong.

Suggested fix is to replace
ReactNativeWebView_kotlinVersion=1.5.30
with
ReactNativeWebView_kotlinVersion=1.7.0
https://github.com/mrousavy/react-native-vision-camera/blob/ae2c28a2c27a2ef6afa276b1b2d2034d2651027c/android/gradle.properties#L16
And also temporary disable frame processors for Android only until proper fix will be available.
PS Disabling Frame Processors cause losing some functionalities like bar code scanner.

+1

+1

Note: this only happens if frame processors are enabled. With no frame processor one can bump kotlinVersion to 1.6.20 (or higher) and be done with it.
I'd say we should stay clear of 0.71 for a few months since a bunch of libs (I made 5+ patch-package to make my app build with 0.71, haven't tested functionalities yet) are broken because RB moved android artifacts to Maven.
Some of those broken libs can get away with a simple patch package(i.e. don't build RN from source, but use the implementation("com.facebook.react:react-android") provided), others, like this one, requires some more effort.
On my side both reanimated and vision-camera has no support for Fabric so I'll stick to 0.67. I see no point upgrading RN since 1) we can't have React 18 features  2) we can't have Fabric 3) that's a ton of trouble upgrading RN.

3rd party libraries - updates and requests, if anyone is interested
https://github.com/reactwg/react-native-new-architecture/discussions/6
Note that I still had to make patch-package for some of those marked as "complete" to work with Fabric + 0.71, react-native-safe-area-context and react-native-screens included.

same issue for me

An rather crude (and dumb) solution would be
modify build.gradle to:

download RN aar from maven https://mvnrepository.com/artifact/com.facebook.react/react-android
download hermes aar from maven https://mvnrepository.com/artifact/com.facebook.react/react-native-artifacts
place them back to where they were on 0.69/0.70, also change the filenames if necessary

This solution SHOULD enable people with almost zero knowledge about how the build process of react-native-vision-camera to use frame processors with RN 0.71.
To be clear: I didn't test it, I just pulled it from under my chair by looking at changelogs from RN0.69 to RN0.71 and some digging in mvn repo. It could work, or it could break things further.

It appears that both https://mvnrepository.com/artifact/com.facebook.react/react-native and https://mvnrepository.com/artifact/com.facebook.react/hermes-engine were abandoned after the incident on Nov 4, 2022.
So if someone went there and wondering why there's only rc0 but no stable version - you went to the wrong place :)

hello, I tried to see the 2 links, but not obvious where to find a "aar" file in all tht a, a more précide link would be expected. I am not geek enough to find that.
And also "place them back to where they were on 0.69/0.7", I do not know where they were before... it is as if you have a book to guide you in the mountains that tells you " at the cross, take the right path." ;-)

hello, I tried to see the 2 links, but not obvious where to find a "aar" file in all tht a, a more précide link would be expected. I am not geek enough to find that. And also "place them back to where they were on 0.69/0.7", I do not know where they were before... it is as if you have a book to guide you in the mountains that tells you " at the cross, take the right path." ;-)

If you have no idea what those links are about then your best choice is to use a different version of react native, say 0.69.
From my perspective, at this time point, everyone should stay clear of 0.71 unless they have a very good reason.

thks, yes I stay on 0.69, but just work ahead to prepare next versions stacks.

thks, yes I stay on 0.69, but just work ahead to prepare next versions stacks.

Just wait for library maintainers to catch up with RN, it could take a few months though.

Same issue here

Starting from React Native 0.71, we're not shipping the /android folder inside the React Native NPM package
anymore due to sizing constraints on NPM. The Android artifacts are distributed via Maven Central.
You can read more about it in this RFC:
https://github.com/react-native-community/discussions-and-proposals/pull/508

+1

Starting from React Native 0.71, we're not shipping the /android folder inside the React Native NPM package
anymore due to sizing constraints on NPM. The Android artifacts are distributed via Maven Central.
You can read more about it in this RFC:

It would be nice patch to be added for android artifacts to be retrieved from maven instead of node_modules as currently this change is breakable for upgrading to 0.71. The 0.70.x version has issues with hermes build and this issue is breaking the upgrade  to 0.71 where it is fixed.

+1

Just tried the crude approach I suggested and I'm not hitting strange blockers.
In file included from ../../../../src/main/cpp/VisionCameraScheduler.cpp:5:   ../../../../src/main/cpp/VisionCameraScheduler.h:8:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found   #include <ReactCommon/CallInvokerHolder.h>
I couldn't find anything related to changes in C++ parts in RN0.70 vs 0.71. The file was of course intact and sits where it should be.

Ok I think I got it.
Here's how you do library patching wrong, step by step:

Since RN0.71 remove the local maven repos, we need to download them from maven and place them back to where they were. Namely, https://mvnrepository.com/artifact/com.facebook.react/react-android and  https://mvnrepository.com/artifact/com.facebook.react/hermes-android. For vision-camera you only need the aars (both debug and release varient), so go grab them.
Reconstruct the local mvn repo (or least reconstruct the parts we need) by creating the following two paths within your project's node_modules
node_modules/react-native/android/com/facebook/react/react-native/${RN_FULL_VERSION}
node_modules/react-native/android/com/facebook/react/hermes-engine/${RN_FULL_VERSION}
RN_FULL_VERSION could be 0.71.0 or 0.71.1 depends on your project dependency
move the react-android aars into node_modules/react-native/android/com/facebook/react/react-native/${RN_FULL_VERSION}, then replace the react-android filename prefix with react-native.
move the hermes-android aars into node_modules/react-native/android/com/facebook/react/hermes-engine/${RN_FULL_VERSION}, then replace the hermes-android filename prefix with hermes-engine.
I would recommend you build a script or something to do step 1 through 4
Next we patch your project. You'll need to modify several files. We'll start with top-level build.gradle - set kotlinVersion =  "1.6.20" in top-level build.gradle
We also need to modify app/build.gradle - add the following lines wherever you please
project.ext.react = [ enableHermes: true, ]
Finally we start modify react-native-vision-camera, navigate to the react-native-vision-camera folder within your node_modules and open CMakeLists.txt
Add the following line in target_include_directories - "${NODE_MODULES_DIR}/react-native/ReactAndroid/src/main/jni/react/turbomodule"

Now you should be able to use react-native-vision-camera as before.
I'll say this again: The above steps are how you do library patching wrong. It is "With Enough Thrust Pigs Fly Just Fine" in action and you should definitely do library patching in the other direction - patch the library, not the framework, and definitely don't patching the framework to make it closer to an older version.

Ok I think I got it. Here's how you do library patching wrong, step by step:

Since RN0.71 remove the local maven repos, we need to download them from maven and place them back to where they were. Namely, https://mvnrepository.com/artifact/com.facebook.react/react-android and  https://mvnrepository.com/artifact/com.facebook.react/hermes-android. For vision-camera you only need the aars (both debug and release varient), so go grab them.
Reconstruct the local mvn repo (or least reconstruct the parts we need) by creating the following two paths within your project's node_modules
node_modules/react-native/android/com/facebook/react/react-native/{RN_FULL_VERSION}/
node_modules/react-native/android/com/facebook/react/hermes-engine/{RN_FULL_VERSION}/
Replace RN_FULL_VERSION with the version you're using, say 0.71.0
Move the react-android aars into node_modules/react-native/android/com/facebook/react/react-native/{RN_FULL_VERSION}/, then replace the react-android filename prefix with react-native.
Move the hermes-android aars into node_modules/react-native/android/com/facebook/react/hermes-engine/{RN_FULL_VERSION}/, then replace the hermes-android filename prefix with hermes-engine.
I would recommend you build a script or something to do step 1 through 4
Next we patch your project. You'll need to modify several files. We'll start with top-level build.gradle - set kotlinVersion =  "1.6.20" in top-level build.gradle
We also need to modify app/build.gradle - add the following lines wherever you please
project.ext.react = [   enableHermes: true, ]
Finally we start modify react-native-vision-camera, navigate to the react-native-vision-camera folder within your node_modules and open CMakeLists.txt
Add the following line in target_include_directories - "${NODE_MODULES_DIR}/react-native/ReactAndroid/src/main/jni/react/turbomodule"

Now you should be able to use react-native-vision-camera as before.
I'll say this again: The above steps are how you do library patching wrong. It is "With Enough Thrust Pigs Fly Just Fine" in action and you should definitely do library patching in the other direction - patch the library, not the framework, and probably never patch the framework to make it closer to an older version.
I made this post just to highlight where things have changed and maybe provide some insights about how one could patch react-native-vision-camera in the right way to support RN0.71. So I won't disclose a repo or anything that automates the steps above.
Fun fact: I was never a fan of Java/Gradle/Maven or anything that's Java-bounded so there is zero chance I'll make a proper fix for this issue.

Thanks a lot of! This solution is great! I only have one problem in compilation:
  ../../../../build/third-party-ndk/folly/folly/dynamic.h:63:10: fatal error: 'boost/operators.hpp' file not found
My stack is RN 0.71.1 and vision 2.15.2
Do you know what can be happend?

Ok I guess Java wins this round.
Here's a (kinda) improper patch-package I made, which makes<EMAIL_ADDRESS>BUILD with frame processors enabled. I didn't fully test functionality, so use at your own risk.
You'll still need to step 6 and 7 though, but I figure you only need to do that once.
https://github.com/zzz08900/vision-camera-071-fix/blob/main/react-native-vision-camera%2B2.15.2.patch

@zzz08900 thanks for this work, any reason why you can't submit these changes as a PR?

Because the fix is half-baked.
I only wanted to modify minimum amount of code so I downloaded the aars into node_modules/react-native/android, which is where the aar files were on older react native versions. Thus I didn't have to touch anything else and they would just work.
I don't think modifying node_modules/react-native from react-native-vision-camera is a good idea since it has the potential to break many, many other things. I guess @mrousavy would agree.
And the patch-package could break things if you are not using hermes(no test was done there, but I guess it could).
So the patch-package is at best a temporary workaround, if you feel like it you can make it into a proper PR. I got my hands full of other problems for now.

thks,It took two days until the answer was found here.The method of adding a remote dependency library is invalid, only aar can be used

Suggested fix is to replace
VisionCamera_kotlinVersion=1.5.30
with
VisionCamera_kotlinVersion=1.7.0
https://github.com/mrousavy/react-native-vision-camera/blob/ae2c28a2c27a2ef6afa276b1b2d2034d2651027c/android/gradle.properties#L16
And also temporary disable frame processors for Android only until proper fix will be available.
PS Disabling Frame Processors cause losing some functionalities like bar code scanner.

It worked for me using kotlinversion=1.6.20
But i changed also sdk and buildtools to 33

I do confirm for 1 week ago I change kotlin version to more , see https://github.com/mrousavy/react-native-vision-camera/issues/1460#issuecomment-1612655719
but sorry , where did you "changed also sdk and buildtools to 33" please?

Just tried the crude approach I suggested and I'm now hitting strange blockers. In file included from ../../../../src/main/cpp/VisionCameraScheduler.cpp:5: ../../../../src/main/cpp/VisionCameraScheduler.h:8:10: fatal error: 'ReactCommon/CallInvokerHolder.h' file not found #include <ReactCommon/CallInvokerHolder.h>
I couldn't find anything related to changes in C++ parts in RN0.70 vs 0.71. The header file was of course intact and sits where it should be. Any suggestions? Hints? Random thoughts?

I am having the same problem, did you manage to solve it?


Help?

@tefra, please excuse the use of "Issues" for this communication but I didn't see an email.  Anything you are looking for help with on the xsdata or xsdata-pydantic projects?

Hi @ryanwclark1
It's getting there, I still have to solve a couple of failures I am gonna need you for testing 👍

What's the current status of this project and what is to be done?

It's been a while, I tried some months ago to push this one for release but I got a few blocking issues from pydantic with the w3c test suite and some of my samples. I haven't checked since then to be honest
Currently it's not the top priority but in #8 someone managed to make it work for them, but If I don't resolve these issues with pydantic I can't really release it.

The first release is live, not everything works, the most complex test suite in the samples repo is still broken but the rest work as expected!!


No such file "tensorflow/c/tf_tstring.h" in C API.

When I unzip the C lib, which is download from :https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-gpu-windows-x86_64-2.4.0.zip
But there is no file  "tensorflow/c/tf_tstring.h" . And it cause an error when compiling. Can anyone know how to fix it? Or send me a C lib which can be used?

Hi,
I don't know why this is happening, but the provided include code for the windows-2.4.0 and the linux-2.4.0 are different. And it looks like the windows version is missing some files like tf_string.h.
I suggest you to use a previous version, you can just change the version number in the link that you provided. For instance, the 2.3.0 version:
https://storage.googleapis.com/tensorflow/libtensorflow/libtensorflow-gpu-windows-x86_64-2.3.0.zip
Hope it helps

Hi serizba, thanks for your reply. I do find the tf_tstring.h in lib in Linux version. It works well if we copy the include folder to replace the original one.
And I also find another way to avoid errors,  if Model::restore() and Model::save() are not in user code.

Comment the part of codes for functinos Model::restore() and Model::save().
Comment #include "tensorflow/c/tf_tstring.h"  in c_api.h

And I also have another question. The model is loaded sucessfully when I avoid the tf_tstring.h error. But prediction result is diffient from the result form python.
I use the EfficientPoseI.pb from daniegr/EfficientPose. The prediction result should be a confidence map with 16 channels. When a 256x256 color image is feeded into the model, the output should be a confidence map with size of 256x256x16, which the vaules should be from 0 to 1.
But the values from cppflow break the boundary, out of range [0,1].

here is my test code:
#include "cppFlow\Model.h"
#include "cppFlow\Tensor.h"
#include <opencv2\opencv.hpp>"
#include<chrono>

cv::Mat preprocess_input(cv::Mat& inMat)
{
	cv::Mat outMat(inMat.rows, inMat.cols, CV_32FC3);
	for (int i = 0; i < inMat.rows; i++)
	{
		uchar *p = inMat.ptr<uchar>(i);
		float *d = outMat.ptr<float>(i);
		for (int j = 0; j < inMat.cols; j++)
		{
			d[j * 3 + 0] = (((float)p[j * 3 + 0] / 255.0F) - 0.485F) / 0.229F;
			d[j * 3 + 1] = (((float)p[j * 3 + 1] / 255.0F) - 0.456F) / 0.224F;
			d[j * 3 + 2] = (((float)p[j * 3 + 2] / 255.0F) - 0.406F) / 0.225F;
		}
	}
	return outMat;
}

int main()
{
	printf("Hello from TensorFlow C library version %s\n", TF_Version());
	Model m("EfficientPoseModel/EfficientPoseI.pb");
	//m.init();
	Tensor input_tensor{ m, "input_res1" };
	Tensor output{ m, "upscaled_confs/BiasAdd" };

	cv::Mat img = cv::imread("sift.jpg", cv::IMREAD_COLOR);
	//cv::cvtColor(img, img, cv::COLOR_BGR2RGB);
	cv::Mat img2;
	cv::resize(img, img2, cv::Size(256, 256));
	cv::Mat img_f = preprocess_input(img2);

	std::vector <float> img_data;
	img_data.assign(img_f.data, img_f.data + img_f.total()*img_f.channels());

	input_tensor.set_data(img_data, { 1,256,256,3 });
	m.run(input_tensor, output);

	for (float f : output.get_data<float>()) {
		std::cout << f << " ";
	}
	std::cout << std::endl;

	getchar();
    return 0;
}

The output in cppflow is shown as:

The output in python code is showns as:

Hi @busyyang ,
I would think that this has something to do with feeding the data wrongly.Could you please send the image you are using?
Also, have you tried to use the cppflow2 version? With that version is easier to read an image and convert it to float, you won't need opencv.

Hi @serizba ,
Here is the simple picture which I use (name as sift.jpg). I would think I follow the pipeline to preprocess the feed data. The preprocess code is as below:
......
    if mode == 'torch':
        x /= 255.
        mean = [0.485, 0.456, 0.406]
        std = [0.229, 0.224, 0.225]

......

I have not try CppFlow2 yet as I thought it only work for tensorflow2.x. I will have a try on CppFlow2, but could you please have some time to see the reason for prediction difficience which I mentioned above.

How are you using the same network in python? Can you provide a small piece of code running in python to compare with?

Hi @serizba, I use the sample code from daniegr/EfficientPose.
git clone https://github.com/daniegr/EfficientPose
cd EfficientPose
python track.py --path "path_for_test_image" --model "I" --framework "tensorflow" --visualize

and in debug mode, we could infer the confidence map from the output of function infer(batch, model, lite, framework).
In another way, I also tried the Cppflow2, but it seem to run with C++17 support. I wish it can be run in standard C++ lib.

Hi @serizba , I have fixed the problem of difference output from C API and python.  It seems that we could not use the sample codes for CV_32F Mat inputs. we need serialize the model input by hand. Here it maybe reference code for followings.
#include "cppFlow\Model.h"
#include "cppFlow\Tensor.h"
#include <opencv2\opencv.hpp>
#include <chrono>

#define Model_Input_Size 256

void preprocess_input(cv::Mat & inMat, std::vector<float>& input_data)
{
	int inMat_row = inMat.rows;
	for (int i = 0; i < inMat_row; i++)
	{
		uchar *p = inMat.ptr<uchar>(i);
		for (int j = 0; j < inMat.cols; j++)
		{
			input_data.at((i * inMat_row + j)*3 + 0) = (((float)p[j * 3 + 0] / 255.0F) - 0.485F) / 0.229F;
			input_data.at((i * inMat_row + j)*3 + 1) = (((float)p[j * 3 + 1] / 255.0F) - 0.456F) / 0.224F;
			input_data.at((i * inMat_row + j)*3 + 2) = (((float)p[j * 3 + 2] / 255.0F) - 0.406F) / 0.225F;
		}
	}
}

int main()
{
	printf("Hello from TensorFlow C library version %s\n", TF_Version());
	Model m("EfficientPoseModel/EfficientPoseI.pb");
	//m.init();
	Tensor input_tensor{ m, "input_res1" };
	Tensor output{ m, "upscaled_confs/BiasAdd" };

	std::chrono::time_point<std::chrono::system_clock> startTP = std::chrono::system_clock::now();
	cv::Mat img = cv::imread("David.jpg", cv::IMREAD_COLOR);
	cv::Size input_size = img.size();
	//cv::cvtColor(img, img, cv::COLOR_BGR2RGB);
	cv::Mat img2;
	cv::resize(img, img2, cv::Size(Model_Input_Size, Model_Input_Size));

	std::vector<float> img_data(Model_Input_Size * Model_Input_Size * 3);
	preprocess_input(img2, img_data);

	input_tensor.set_data(img_data, { 1,Model_Input_Size,Model_Input_Size,3 });
	m.run(input_tensor, output);

	std::chrono::time_point<std::chrono::system_clock> finishTP = std::chrono::system_clock::now();
	std::cout << "Time Taken in forward pass = " << std::chrono::duration_cast<std::chrono::milliseconds>(finishTP - startTP).count() << " ms" << std::endl;

	getchar();
    return 0;
}

Thanks for this awsome project and kindly reply again. As for Cppflow2, if it can run in standard C++ lib instead of C++ 17 support, it can be spread more widely.

@busyyang
Glad that you finally fixed it.
I appreciate your suggestion, but I think for the moment I will keep the current implementation.


Box Shadow Genrator is twice at Home Page

Describe the bug
The box shadow generator at Home Page can be seen twice.
Expected behavior
There has to only one at that Page.
Screenshots

Thanks for raising the issue i will fix it


Should --keep-locked be allowed for lock/unlock subcommands?

Good question - I think it doesn't make any sense.


Move TableStats into PlannerContext

Summary of the changes / Why this improves CrateDB
This moves the TablesStats from the LogicalPlanner into the PlannerContext and cleans up the JoinTest based on this change. The reason for this change is to be able to have access to the TableStats inside the build method of the LogicalPlans because stats are used to decide on the execution plan of the join. It also makes the TableStats handling a bit simpler in the tests because the stats can easily be accessed and updated.
This is a pre-requisite for introducing statistics for plans and finally moving more logic into optimizer rules.
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

The reason for this change is to be able to have access to the TableStats inside the build method

Why is it needed in the build method if the goal is to move more logic to rules (which already have access to the TableStats)?
(Not against the change, just curious)
I wonder if it would fit into NodeContext

Why is it needed in the build method if the goal is to move more logic to rules (which already have access to the TableStats)?

Stats of Tables and Plans are useful to decide which execution model a LogicalPlan should become. E.g. the build method of NestedLoopJoin uses stats if a nl-block join can be applied.
https://github.com/crate/crate/blob/915814d2eec020ae3b0f10dac557bb24edb56bba/server/src/main/java/io/crate/planner/operators/NestedLoopJoin.java#L185

I wonder if it would fit into NodeContext

NodeContext would also be an option. I would like to also add PlanStats next and that would fit better into PlannerContext.

Stats of Tables and Plans are useful to decide which execution model a LogicalPlan should become. E.g. the build method of NestedLoopJoin uses stats if a nl-block join can be applied.

Shouldn't that also eventually become a rule, as we'll likely want to consider costs in such decisions as well?

I removed setTableStats from the Builder. I think it's easier to use in the tests, but i am ok with both approaches.

How about I merge this to a feature branch, and add the additional pr's next to get the big picture before we merge to master ?

How about I merge this to a feature branch, and add the additional pr's next to get the big picture before we merge to master ?

Sounds good. Thinking about this a bit more I'm a bit against this change as keeping stats away from build helps nudge us towards writing rules instead of adding planning decisions into build. So it would help a lot to see the bigger picture.

Sounds good. Thinking about this a bit more I'm a bit against this change as keeping stats away from build helps nudge us towards writing rules instead of adding planning decisions into build. So it would help a lot to see the bigger picture.

Ok, let's do this. I am also not 100 % sure yet about the design.


Code should use Path() class as a replacement for os.path function

Implemented in b0d59c1. Closing ticket.


Demo App Build Documentation

Create demo app documentation to guide a user through building and deploying the demo apps onto an emulator

Android SDK is not updated with the latest SDK changes, will wait to build and do instructions until then (especially because we suspect it might not build at all right now).


Update unblocking-a-user-from-your-orga.nization.md

Why:
Closes [issue link]

What's being changed:

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[x] This pull request impacts the contribution experience

[x] I have added the 'writer impact' label
[x] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

atay

ar

a


feat/doc (IAC-1270) the documentation says we don't create PG DB during infra setup but the code creates the SharedServices DB.

From https://github.com/sassoftware/viya4-iac-k8s/blob/main/docs/CONFIG-VARS.md :
PostgreSQL Servers
When setting up external database servers, you must provide information about those servers in the postgres_servers variable block. Each entry in the variable block represents a single database server.
This code only configures database servers. No databases are created during the infrastructure setup.
However, the task "https://raw.githubusercontent.com/sassoftware/viya4-iac-k8s/main/roles/kubernetes/database/postgres/create_databases/tasks/main.yaml" creates the SharedServices DB when the postgres_server_name is "default".

We are currently evaluating the action we will take on this

Is this issue already taken care of?
also we used iac project to deploy infrastrucutre and also external postgres server but we see that when it creates the postgres server, in tfstate file, it creates its own FQDN and we use this FQDN or server name, sas deployment throws error while regsitering the postgres server.


possible to hide unencrypted remote source ?

Hi, Is the a way to hide my "unencrypted" profile and just keep the "type = crypt" visible in the RcloneBrowser
I like to use this on a USB stick as Portable Version, so that I can share this with friends, but I do not like that they see the decrypted source account.
I know the pw is encrypted on the Main account, but the username for example NOT.
user =<EMAIL_ADDRESS>If I set a password, on the config, its still possible to remove the password if its known (and they need to knwo it to use the Application.)
Any idea ?

https://github.com/kapitainsky/RcloneBrowser/issues/178#issue-1014079170

Thx will reply there

By the way I don't think this is the job of a software that designed as just a GUI for an another tool...


⚠ Bofrost.lu has degraded performance

In a9f043a, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1205 ms

Resolved: Bofrost.lu performance has improved in 0ba18b4.


Use the Minimum Autosize property as size property when autogrow is set to grow

There is an issue with autosize set to grow and the size property on a volume.
When a volume is growing due to autosize then this new size is compared with the size defined in puppet. As a result puppet will revert the size to the defined size and the netapp will resize it again.
If autosize is set to grow the minimum size is set to the initial size, so this property can be used to compare the size property.

This is obviously a bug, but something else seems incorrect about this too.
The docs for initsize do say "The initial volume size" which would indicate to me that a volume that already exists should not have its size modified by puppet, but it looks like it can. Should the behavior be changed so that the size can only be set on create? Is this a dangerous operation? Should the initsize attribute be renamed to just size and document that it only manages minimum-size when autogrow is on?

@hunner I would prefer the latter option. We should be able to change the size of a volume with puppet and use the autogrow option.


make release-0.20 failed

What did you do?
git clone https://github.com/openshift/prometheus-operator.git -b release-0.20
cd prometheus-operator
mkdir -p gopath/src
cd gopath/src/
ln -s ../../vendor/* .
cd -
mkdir -p vendor/github.com/coreos/prometheus-operator/
cd vendor/github.com/coreos/prometheus-operator/
ln -s ../../../../* .
ln -s ../../../../.header .
cd -
export GOPATH=`pwd`/gopath
make build

What did you expect to see?
no error report and build proccess execute ok.
What did you see instead? Under which circumstances?
# make build
 >   operator
# github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/clientset.go:59:59: cannot use &configShallowCopy (type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config) as type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config in argument to v1alpha1.NewForConfig
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/clientset.go:64:67: cannot use &configShallowCopy (type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config) as type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config in argument to "github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/v1".NewForConfig
# github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/k8sutil
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/k8sutil/k8sutil.go:187:24: cannot use "github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/v1".GetOpenAPIDefinitions (type func("github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/kube-openapi/pkg/common".ReferenceCallback) map[string]"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/kube-openapi/pkg/common".OpenAPIDefinition) as type crdvalidation.GetAPIDefinitions in field value
# github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/clientset.go:59:59: cannot use &configShallowCopy (type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config) as type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config in argument to v1alpha1.NewForConfig
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/clientset.go:64:67: cannot use &configShallowCopy (type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config) as type *"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/client-go/rest".Config in argument to "github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/v1".NewForConfig
# github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/k8sutil
gopath/src/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/k8sutil/k8sutil.go:187:24: cannot use "github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/pkg/client/monitoring/v1".GetOpenAPIDefinitions (type func("github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/kube-openapi/pkg/common".ReferenceCallback) map[string]"github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/github.com/coreos/prometheus-operator/vendor/k8s.io/kube-openapi/pkg/common".OpenAPIDefinition) as type crdvalidation.GetAPIDefinitions in field value
!! command failed: build -o /mnt/OKD-3.11/prometheus-operator/operator -ldflags -X main.Version=0.20.0 -extldflags '-static' -a -tags netgo github.com/coreos/prometheus-operator/cmd/operator: exit status 2
make: *** [build] Error 1

Environment
CentOS 7 with go1.10.2 linux/amd64

Prometheus Operator version:
572348b1d6979de92d42727152cca9bf6838cab3

There is a same build error with https://github.com/coreos/prometheus-operator.git release-0.20.

build ok with following cmds:
mkdir -p `pwd`/prometheus-operator/gopath/src/github.com/coreos
export GOPATH=`pwd`/prometheus-operator/gopath
cd `pwd`/prometheus-operator/gopath/src/github.com/coreos
git clone https://github.com/openshift/prometheus-operator.git -b release-0.20
cd prometheus-operator
make build


Rename "genes" to ...? Or add new field called ...?

The data we have for CODEX is not genes per se, but the names of channels:
,ci:DAPI-002:mean,ci:CD31:mean,ci:CD8:mean,ci:CD45:mean,ci:DAPI-003:mean,ci:CD20:mean,ci:Ki67:mean,ci:CD3e:mean,ci:DAPI-004:mean,ci:Actin:mean,ci:Podoplanin:mean,ci:CD68:mean,ci:DAPI-005:mean,ci:PanCK:mean,ci:CD21:mean,ci:CD4:mean,ci:DAPI-006:mean,ci:EMPTY:mean,ci:CD45RO:mean,ci:CD11c:mean,ci:DAPI-007:mean,ci:EMPTY:mean.1,ci:E_CAD:mean,ci:CD107a:mean,ci:DAPI-008:mean,ci:EMPTY:mean.2,ci:CD44:mean,ci:HistoneH3:mean,ni:DAPI-002:mean,ni:CD31:mean,ni:CD8:mean,ni:CD45:mean,ni:DAPI-003:mean,ni:CD20:mean,ni:Ki67:mean,ni:CD3e:mean,ni:DAPI-004:mean,ni:Actin:mean,ni:Podoplanin:mean,ni:CD68:mean,ni:DAPI-005:mean,ni:PanCK:mean,ni:CD21:mean,ni:CD4:mean,ni:DAPI-006:mean,ni:EMPTY:mean,ni:CD45RO:mean,ni:CD11c:mean,ni:DAPI-007:mean,ni:EMPTY:mean.1,ni:E_CAD:mean,ni:CD107a:mean,ni:DAPI-008:mean,ni:EMPTY:mean.2,ni:CD44:mean,ni:HistoneH3:mean

(The "EMPTY" ones will be dropped.)
For now, I plan to just use the genes we have in our schema, but should we rename it to something more generic? Or should we keep the biologically precise names, and add a new one?
Unless we need to handle different kinds of things differently, I'd be reluctant to hard-code this, and would favor a generic name.
@ngehlenborg : Do you have an opinion?

From Nils:

I second that. Genes (currently an entity associated with a quantity per cell) should be molecules or molecular entities. I know that this clashes with our current definition of molecules (an entity associated with an x/y coordinate). It might be worthwhile to refactor this and come up with a unified data model for these in the medium term but we can also just rename “genes” into QuantifiedMolecules and “molecules” into LocalizedMolecules in the short term.
The userfacing names for those should be defined when the dataset is configured

Changing this is breaking change - in the UI, though, we can add an override to allow for overriding the label.

@ilan-gold @mccalluc Can this be closed?

Closing this now that we have featureType (http://vitessce.io/blog/obs-by-feature-update/)


Add a format check to github workflow

Was tested with unformated change, CI was failing.
Added commit to fix formatting and then CI passed.


feature/mx-1563 use type-discriminator in backend

PR Context

Added

Changes

Deprecated

Removed

Fixed

Security

this PR has gone stale, and ticket is back in backlog. closing.


Clean up test data organization

Right now there are 7 data_dir/data_path method definitions:

binstar_client/CLITestCasedefinesdata_dirmethod, locates all test files inbinstar_client/tests/data`
binstar_client/inspect_package/tests/*.py each define a data_path function, relative to __file__
binstar_client/utils/notebook/tests/*.py each define a data_dir method, relative to __file__

@dsludwig can you estimate some story points for this?


How can I use Middleware?

I am currently using EntityGraphQL with .NET 6.
I would like to set up a middleware structure in my project. I reviewed the documentation, but I couldn’t find how to do this.
We are using JWT, and we have different validations for requests. I would like to use middleware to handle these validations in between. How can I achieve this?
Thank you in advance for your response.

EntityGraphQL isn't a web sever itself. Assuming you are using ASP.NET, you can follow its docs and tutorials to add JWT auth etc.
MapGraphQL just adds a middleware to handle the URL endpoint. It will be author etc if you turn that on with the dotnet UseAuthentication and UseAuthorization middleware.
Is there something more specific you are having issues with?

Thank you for your help. I have resolved the issue; we can close it now


Remove activationLagThreshold to fix 0->1 scaling

Fixes Kafka source tests when KEDA is enabled (hopefully).
From discussion here, we shouldn't be using activationLagThreshold unless we want to initially scale form 0 to n>1. Hence, our scaling 0 -> 1 was not working.

Proposed Changes

Remove activationLagThreshold parameter (letting it default to 0)

Release Note

Docs

/test

/test reconciler-tests-keda

/cc @pierDipi

/retest-required

/cherry-pick release-1.12

/cherry-pick release-1.11

/test reconciler-tests


Missing zero-key NCCH support

NCCHReader does not use the proper keys to decrypt zero-key encrypted files.

Related issue: https://github.com/ihaveamac/custom-install/issues/18

Now supported with https://github.com/ihaveamac/pyctr/commit/1bf6355cdc236b6f0f0068bb995e41fa8be2ce15 and https://github.com/ihaveamac/pyctr/commit/f04bc5a09b448605b7c69a7cffec54540b80c0d8


Please define acronym "ATC"

[Enter feedback here]

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

ID: c918dd65-3761-be6b-6e5b-199255402a27
Version Independent ID: 7c33b8ea-f2f5-11f7-f478-42d2d80a220a
Content: Network ATC overview - Azure Stack HCI
Content Source: azure-stack/hci/concepts/network-atc-overview.md
Service: azure-stack
Sub-service: azure-stack-hci
GitHub Login: @dcuomo
Microsoft Alias: jgerend

This is a proper noun and not an acronym. The name of the feature is "Network ATC."

#please-close


Reverse cred hub

Reversing credhub changes.

@jagadish-kb Please have a look in this PR. Got to know from @mayanktiwari09 that this was done in consultation with you, hence merged to release the code.


Build custom outputter

A basic custom outputter than consumes parquet-dotnet and writes all files to parquet

I have this in my repo in some really simple form, will get it migrated here ;)

Committed via @aloneguid a few issues raised but this can be closed now


Getting MappingException when reading TINYINT value from H2 database

Bug Report
Versions

Driver: io.r2dbc:r2dbc-h2:0.8.4.RELEASE (Spring boot 2.3.2.RELEASE)
Database: H2
Java: 11
OS: Mac

Current Behavior

Stack trace
org.springframework.data.mapping.MappingException: Could not read property @org.springframework.data.relational.core.mapping.Column(value="is_active")private boolean com.by.eso.foodprepsvc.persistence.entities.PrepTaskEntity.isActive from result set!
	at org.springframework.data.r2dbc.convert.MappingR2dbcConverter.readFrom(MappingR2dbcConverter.java:172) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException:
Error has been observed at the following site(s):
	|_ checkpoint ⇢ Handler com.by.eso.foodprepsvc.controllers.PrepTaskController#getPrepTasksForGivenBU(String) [DispatcherHandler]
	|_ checkpoint ⇢ com.by.eso.foodprepsvc.filters.TenancyContextFilter [DefaultWebFilterChain]
	|_ checkpoint ⇢ HTTP GET "/sites/BU-002/prepTasks" [ExceptionHandlingWebHandler]
Stack trace:
		at org.springframework.data.r2dbc.convert.MappingR2dbcConverter.readFrom(MappingR2dbcConverter.java:172) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
		at org.springframework.data.r2dbc.convert.MappingR2dbcConverter.read(MappingR2dbcConverter.java:133) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
		at org.springframework.data.r2dbc.convert.MappingR2dbcConverter.read(MappingR2dbcConverter.java:116) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
		at org.springframework.data.r2dbc.convert.EntityRowMapper.apply(EntityRowMapper.java:46) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
		at org.springframework.data.r2dbc.convert.EntityRowMapper.apply(EntityRowMapper.java:29) ~[spring-data-r2dbc-1.1.2.RELEASE.jar:1.1.2.RELEASE]
		at io.r2dbc.h2.H2Result.lambda$map$0(H2Result.java:67) ~[r2dbc-h2-0.8.4.RELEASE.jar:0.8.4.RELEASE]
		at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:100) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]

Table schema

Input Code
CREATE TABLE `prep_task` (
  `id` SERIAL,
  `external_id` VARCHAR(45) NOT NULL,
  `name` VARCHAR(45) NOT NULL,
  `description` VARCHAR(100) NULL,
  `is_active` TINYINT,
  PRIMARY KEY (`id`)
);

Steps to reproduce

Input Code
@Table("prep_task")
public class PrepTaskEntity implements Persistable<Long> {
  @Id
  @Column("id")
  private Long id;

  @Column("external_id")
  private String externalId;

  @Column("name")
  private String name;

  @Column("description")
  private String description;

  @Column("is_active")
  private boolean isActive;

  public Long getId() {
    return id;
  }

  public void setId(Long id) {
    this.id = id;
  }

  public String getExternalId() {
    return externalId;
  }

  public void setExternalId(String externalId) {
    this.externalId = externalId;
  }

  public String getName() {
    return name;
  }

  public void setName(String name) {
    this.name = name;
  }

  public String getDescription() {
    return description;
  }

  public void setDescription(String description) {
    this.description = description;
  }

  public boolean isActive() {
    return isActive;
  }

  public void setActive(boolean active) {
    isActive = active;
  }

  @Override
  public boolean isNew() {
    return id == null;
  }

}

Expected behavior/code
Should be able to read the is_active column value in the boolean isActive.
Additional context
H2 Connection Config (using Routing Connection Factory because of multi-tenancy)
@Configuration
@Profile(Application.Profiles.INTEGRATION_TEST)
public class H2ConnectionConfig extends AbstractR2dbcConfiguration {

  private final R2dbcConfigProperties r2dbcConfigProperties;

  @Autowired
  public H2ConnectionConfig(R2dbcConfigProperties r2dbcConfigProperties) {
    this.r2dbcConfigProperties = r2dbcConfigProperties;
  }

  @Override
  @Bean
  public ConnectionFactory connectionFactory() {
    RoutingConnectionFactory connectionFactory = new RoutingConnectionFactory();
    Map<String, ConnectionFactory> factories = new HashMap<>();
    H2ConnectionConfiguration.Builder configurationBuilder = H2ConnectionConfiguration.builder()
        .property(H2ConnectionOption.MODE, "MySQL")
        .property(H2ConnectionOption.DB_CLOSE_DELAY, "-1")
        .property(H2ConnectionOption.DB_CLOSE_ON_EXIT, "false");
    for (String tenant : r2dbcConfigProperties.getTenants()) {
      String databaseName = r2dbcConfigProperties.getDbPrefix() + tenant;
      factories.put(tenant, new H2ConnectionFactory(configurationBuilder.inMemory(databaseName).build()));
    }
    connectionFactory.setTargetConnectionFactories(factories);
    connectionFactory.setDefaultTargetConnectionFactory(factories.get("default"));
    return connectionFactory;
  }

}

Can you please attach the cause of MappingException?

@mp911de You mean stacktrace? It's there.

No, I mean the cause of MappingException.

@mp911de  I just updated the description. Probably it's now a bit more clearer?

I have difficulties to understand why it's not possible to attach the cause of MappingException. Instead the stack trace is truncated and showing mostly Spring Data stack elements. You're not required to debug the code nor investigate the underlying issue. Just providing the full error context is sufficient.

@mp911de  My bad. Missed that in the stacktrace. Thought to omit the unnecessary ones (which had the trace from Reactor classes). Adding that.

Thanks a lot, ConverterNotFoundException is what we were looking for.
That being said, there's nothing we can do on the driver level as the conversion is related to Spring Data. Please register a @ReadingConverter Converter<Byte, Boolean> that implements your conversion logic and register it with R2dbcCustomConversions. See https://docs.spring.io/spring-data/r2dbc/docs/current/reference/html/#mapping.configuration for further reference.
Closing this ticket as that's not a driver issue.

Thanks @mp911de  for the guide.


Capistrano prints Ruby 2.7.0 keyword parameters warnings

Running the Capistrano feature test suite under Ruby 2.7.0 prints the following warning:
lib/capistrano/dsl.rb:36: warning: Using the last argument as keyword parameters is deprecated; maybe ** should be added to the call
ruby/gems/2.7.0/gems/i18n-1.8.2/lib/i18n.rb:195: warning: The called method `t' is defined here

Fixed at #2060


Enable Dependabot updates to Poetry, fix tests and docs build

This PR focuses on long-term sustainability for this project by enabling Dependabot to automatically update the Poetry lockfile. Normally this is a task which must be performed manually. By enabling this change we can have Dependabot automatically update the dependency references (which still fall into the constraints of the pyproject.toml file).
Thanks for any feedback!
Should be merged after #4

Thanks @jenna-tomkinson for the review here! I'm going to interpret your review as an approval for #4, as it goes through code which this branch was based on. I'll merge #4 and then this PR to keep the git history clean and descriptive. Related issues were created or referenced to help make sure we address what you mentioned in the comments.

Added changes which are more related to #4 which weren't apparent until after a merge (automated tests were prevented and a docs build failed after merge). I'm trying to keep things succinct by appending the changes here.


virustotal warnings

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go1.11.1 windows/amd64
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
amd64 windows
What did you do?
here is my program source code
file dnsleaktest.go
package main
func main() {
}
I built it with this command line
go build -o dnsleaktest.exe dnsleaktest.go
What did you expect to see?
I've expected to see the green rating on virustotal.com
What did you see instead?
https://www.virustotal.com/#/file/af6bc9900800a41c10338edfae19066b49f919df0e49892f1d25010324e4d729/detection

Hi @macvk - Thank you for reporting the issue. Unfortunately issues like this are seen frequently with Windows systems. Please see - https://golang.org/doc/faq#virus
To confirm whether your GO distribution is affected or not, you can always check the checksum from the site.
Thank you.

Hi, @agnivade
The checksum is match. I've used travis-c for building and the result is the same. Sorry, I am not going to email every of antivirus vendor because it will take a lot of time which I don't have. This is totally your issue and you should sort it out. Moving this issue to FAQ - is the worst scenario. MS visual studio, mingw, borland c haven't experienced such issue.

is it possible to not close the unresolved issues?

I've built the binary on Linux rather than Windows.

This issue is with the vendor of your virus scanner, not Go.  It is on the vendor to not use patterns that produce false positives.

But you can go this way. Remove all the modules from golang and try to build the empty application without any modules. Then add modules one by one and test them on virustotal. All in all you can find out which module bring about the antivirus warnings. I think you understand my idea.

using avira antivrus, Created an exception on c:\users[yourusername]\appdata\local\temp... or specifically where the build happened. which fixed the warnings and also the slowness every time go built anything.


about me formatting

Born and raised in Seattle, I have run competitively for more than fifteen years.  After years of teaching History, Outdoor Science, and Spanish, I am looking to do something different - perhaps in computer programming.


Give 4 points access to usage reports

Four points needs access to AWS usage reports to generate cost summery level reports.
from  four points...
Good morning.  I have accessed the account to complete our first month of billing.
I just realized we don’t have access to the usage report that we need.
I will only be able to provide summary level reporting this month.
Can we get the detail billing report and a CUR report setup for our use?
I can provide details on what we need if needed.

I'm not quite sure what Four Points is asking for. We already have a CUR configured to export into the bucket cost-and-usage-reports.sagebase.org, and they should already be able to access that bucket.

@jesusaurus

I'm not quite sure what Four Points is asking for.

i'm guessing that they want to view usage from the AWS console.
@brucehoff

Have you confirmed with Four Points that this is the additional access they are asking for when they say, "detail billing report and a CUR report "?

No, i have not.

Does Four Point need access to that bucket?

I have no idea.

Can you please take another look @jesusaurus and @brucehoff ?

@jesusaurus

I'm not quite sure what Four Points is asking for.

i'm guessing that they want to view usage from the AWS console.
@brucehoff

Have you confirmed with Four Points that this is the additional access they are asking for when they say, "detail billing report and a CUR report "?

No, i have not.

Does Four Point need access to that bucket?

I have no idea.

@zaro0508 Here's some follow on correspondence to help you decide if the proposed permissions are correct.  They sent this after I asked them to create their own CUR using their current permissions:
Good morning. As expected, I don’t have the needed permissions to setup a CUR report. AWS’ new granular permissioning is not making this easy. :) It might be easier to just provide access to data exports and CUR broadly at least temporarily.  I believe I can setup the legacy detailed billing reports (which are our preference) but cannot create an S3 bucket in either case.  So would need you to either give me appropriate S3 permissions or create a bucket for me.  Below is the additional permissions I think I need (excluding the change to S3):

{

              "Version": "2012-10-17",

              "Statement": [

                             {

                                           "Sid": "VisualEditor0",

                                           "Effect": "Allow",

                                           "Action": [

                                                          "bcm-data-exports:*",

                                                          "cur:*",

                                           ],

                                           "Resource": "*"

                             }

              ]

}

Let me know if you have any thoughts and concerns.  I am trying to complete July’s invoicing, but I don’t know have access to the details needed to apply CloudFront and S3 special pricing.

@brucehoff yes, i saw the email.  I have already incorporated 4point's request into this PR.  can you please take another look?


Add -skip-oidc-discovery option

Description
This PR adds the option to skip OIDC discovery by go-oidc and instead manually configure Authorization, Token and JWKS URI endpoints.

Motivation and Context
Fixes #27
Some OIDC providers either do not have a discovery endpoint (non-standard Enterprise solutions) or require additional URL parameters for specific user journey policies to be supplied (Microsoft Azure AD B2C).
go-oidc calls the fixed /.well-known/openid-configuration endpoint of the configured OIDC issuer. When there is no issuer or when there are multiple policies defined via additional parameters, this method cannot be relied upon.
Fortunately, go-oidc provides the possibility to use a custom HTTP client via a client context. With this, we supply go-oidc with a "fake" HTTP client that always returns the manually configured Auth,Token and JWKS endpoints in a JSON response when it calls the discovery endpoint.

How Has This Been Tested?

I tested this with Microsoft Azure AD B2C as OIDC Provider which uses an additional URL parameter for custom User Journeys. Manually setting the OIDC endpoints to a particular policy returns the proper user journey
Checklist:

[x] My change requires a change to the documentation or CHANGELOG.
[x] I have updated the documentation/CHANGELOG accordingly.
[x] I have created a feature (non-master) branch for my PR.

@tlawrie care to test this PR in your environment?

rebased to master, using oidc.NewVerifier now (which was actually pretty simple and already documented with an example in go-oidc itself).
@tlawrie care to test the new changes?

Fantastic. Myself and my colleague @costelmoraru will test

@tlawrie did you have any chance to test yet?
@JoelSpeed when @tlawrie finished his tests, this should be good to merge?

Hey @marratj , we tested out the -skip-oidc-discovery option on a ICP <IP_ADDRESS> and ICP 3.1.1 and it works correctly.
Thank you for your help and contribution.

@JoelSpeed @costelmoraru @tlawrie
I guess we are good to go then?

@marratj Thanks for your work on this! 🎉

@marratj does this mean oauth2_proxy fully supports Azure AD B2C now? Is there any documentation on how I can setup oauth2_proxy to work with B2C? Or should I just refer the documentation for the Azure AD provider at https://pusher.github.io/oauth2_proxy/auth-configuration#azure-auth-provider

@harindaka yes, this fully works now, provider to use is the OIDC one, here is a config that we use:
provider = "oidc"
oidc_issuer_url = "https://login.microsoftonline.com/{tenant-id}/v2.0/"
scope = "{B2C-app-id} openid offline_access"

skip_oidc_discovery = true
login_url = "https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize?p=b2c_1a_policyname"
redeem_url = "https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token?p=b2c_1a_policyname"
oidc_jwks_url = "https://login.microsoftonline.com/{tenant-id}/discovery/v2.0/keys?p=b2c_1a_policyname"

For {tenant-id}, use the ID of the tenant (the long UUID one), not the tenant domain (although the latter should work, but we had some issues with that in the past).


Strange results about baseline

Hi! I made only a few changes to the code to adapt it to the environment and then ran the training program to get the results shown in the figure, getting many predictions on non-existent speech events, which resulted in low accuracy and error rates, but other metrics were normal.

Class-wise metrics
Event label  | Nref    Nsys  | F        Pre      Rec    | ER       Del      Ins    | Sens     Spec     Bacc     Acc
------------ | -----   ----- | ------   ------   ------ | ------   ------   ------ | ------   ------   ------   ------
metro leav.. | 0       1390  | nan%     0.0%     nan%   | 6260..   0.00     6260.. | 0.0%     87.6%    43.8%    87.6%
birds_sing.. | 0       2517  | nan%     0.0%     nan%   | 1133..   0.00     1133.. | 0.0%     77.5%    38.7%    77.5%
coffee mac.. | 0       297   | nan%     0.0%     nan%   | 1337..   0.00     1337.. | 0.0%     97.3%    48.7%    97.3%
furniture .. | 0       613   | nan%     0.0%     nan%   | 2760..   0.00     2760.. | 0.0%     94.5%    47.3%    94.5%
car          | 0       2584  | nan%     0.0%     nan%   | 1163..   0.00     1163.. | 0.0%     76.9%    38.4%    76.9%
metro appr.. | 0       1784  | nan%     0.0%     nan%   | 8034..   0.00     8034.. | 0.0%     84.1%    42.0%    84.1%
large_vehi.. | 0       649   | nan%     0.0%     nan%   | 2922..   0.00     2922.. | 0.0%     94.2%    47.1%    94.2%
Dishes       | 754     726   | 73.6%    75.1%    72.3%  | 0.52     0.28     0.24   | 72.3%    98.3%    85.3%    96.5%
Cat          | 728     783   | 86.6%    83.5%    89.8%  | 0.28     0.10     0.18   | 89.8%    98.8%    94.3%    98.2%
Vacuum_cle.. | 801     827   | 90.9%    89.5%    92.4%  | 0.18     0.08     0.11   | 92.4%    99.2%    95.8%    98.7%
Speech       | 3745    3781  | 93.7%    93.3%    94.2%  | 0.13     0.06     0.07   | 94.2%    96.6%    95.4%    95.8%
Electric_s.. | 522     645   | 86.4%    78.1%    96.6%  | 0.30     0.03     0.27   | 96.6%    98.7%    97.6%    98.6%
people tal.. | 0       5667  | nan%     0.0%     nan%   | 2552..   0.00     2552.. | 0.0%     49.3%    24.7%    49.3%
brakes_squ.. | 0       565   | nan%     0.0%     nan%   | 2544..   0.00     2544.. | 0.0%     94.9%    47.5%    94.9%
Running_wa.. | 1385    1486  | 88.2%    85.2%    91.4%  | 0.24     0.09     0.16   | 91.4%    97.8%    94.6%    97.0%
wind_blowing | 0       457   | nan%     0.0%     nan%   | 2058..   0.00     2058.. | 0.0%     95.9%    48.0%    95.9%
door opens.. | 0       462   | nan%     0.0%     nan%   | 2080..   0.00     2080.. | 0.0%     95.9%    47.9%    95.9%
shopping c.. | 0       642   | nan%     0.0%     nan%   | 2891..   0.00     2891.. | 0.0%     94.3%    47.1%    94.3%
footsteps    | 0       1390  | nan%     0.0%     nan%   | 6260..   0.00     6260.. | 0.0%     87.6%    43.8%    87.6%
cutlery an.. | 0       798   | nan%     0.0%     nan%   | 3593..   0.00     3593.. | 0.0%     92.9%    46.4%    92.9%
Blender      | 538     565   | 83.4%    81.4%    85.5%  | 0.34     0.14     0.20   | 85.5%    99.0%    92.3%    98.4%
Frying       | 794     835   | 90.0%    87.8%    92.3%  | 0.21     0.08     0.13   | 92.3%    99.0%    95.7%    98.5%
children v.. | 0       3464  | nan%     0.0%     nan%   | 1560..   0.00     1560.. | 0.0%     69.0%    34.5%    69.0%
Dog          | 1131    1096  | 86.8%    88.2%    85.5%  | 0.26     0.15     0.11   | 85.5%    98.7%    92.1%    97.4%
announcement | 0       493   | nan%     0.0%     nan%   | 2220..   0.00     2220.. | 0.0%     95.6%    47.8%    95.6%
Alarm_bell.. | 1060    1113  | 88.9%    86.8%    91.1%  | 0.23     0.09     0.14   | 91.1%    98.5%    94.8%    97.8%
cash regis.. | 0       413   | nan%     0.0%     nan%   | 1859..   0.00     1859.. | 0.0%     96.3%    48.2%    96.3%

like this， Could you please answer the reason? Thank you!


this region has quota of 0 instances for your subscription while create azure app service

this region has quota of 0 instances for your subscription while create azure app service.

This is the error i' m now need your support to use free trail to create azure app service


Question re: newline behaviour

Hi there! Thanks a lot for Bling, it looks awesome :-)
I'm busy evaluating the possibility of either making it easier to use Bling from Telemere, or at least including an example of usage.
What I have so far is this gist (not important to follow if you're unfamiliar with Telemere, just included for reference).
I have a question!
Am I correct in understanding that the (Clj) output from (bling/callout {:data? true} ...) always begins with a newline character?
If so, may I ask what the motivation for that is?
I would expect the {:data? true} mode to not include any leading or trailing newlines.
Thanks! Cheers :-)

Hi @ptaoussanis !
Happy to hear that you are looking into using Bling from Telemere.
The {:data? true} option is intended to provide a string with the exact same formatting as the printed output that you would get from calling callout with (optionally) supplied options. There is a table of available options in this section of the readme, just below the example images.
Currently, by default, callout prints a callout section with a leading newline.
For your use case (assuming you do not want a leading newline), I think you might want something like this?
(callout {:data? true :margin-top 0} "foo")
To provide another example:
If, for some reason, you wanted more breathing room above and below the callout block:
(callout {:data? true :margin-top 2 :margin-bottom 2} "foo")
Similarly, you can control the padding within the callout block using :padding-top, :padding-bottom, and :padding-left.
Let me know if that helps :-)

For your use case (assuming you do not want a leading newline), I think you might want something like this?
(callout {:data? true :margin-top 0} "foo")

That's perfect, thank you @paintparty 🙏
Apologies for missing the clearly documented margin options!
I'd looked through the callout docstring, but my mental model somehow wasn't registering margins as newlines in this context ^^
Much appreciated, cheers!

I'd looked through the callout docstring, but my mental model somehow wasn't registering margins as newlines in this context ^^

Ah yes good callout on the callout docstring. I just made some changes to that docstring and readme to hopefully make things more explicit. Also found some related inaccuracies in there and fixed those too.
I'm checking out the Bling gist from the telemere wiki and it looks like there is a function defined called signal->callout-opts, then lower down within the tel/add-handler! call there is (signal->bling-callout signal). Should that be (signal->callout-opts signal), or am i looking at it wrong? I wish there was kondo for github gists!
Kudos on Telemere it looks awesome - definitely planning on using it in the future. That being said I'm not yet familiar with it but I wonder if the pretty-printing functionality from Fireworks might provide some utility for certain Telemere use cases. The formatting is designed for ephemeral display and speed of comprehension when you are observing values during development, so it probably would not be suitable for structured logs that are written to disk etc.
You can call the print-and-return macro fireworks.core/? with the :data flag to just get the formatted string:

(def sample-map
  (array-map
   :string
   "string"
   :regex
   #"myregex"
   :uuid
   #uuid "4fe5d828-6444-11e8-8222-720007e40350"
   :symbol
   'mysym
   :symbol+meta
   (with-meta 'mysym {:foo "bar"})
   :boolean
   true
   :keyword
   :keyword
   :nil
   nil
   :##Nan
   ##NaN
   :##Inf
   ##Inf
   :##-Inf
   ##-Inf
   :map
   {:a 1
    :b 2
    :c "three"}
   :vector
   [1 2 3]
   :vector+meta
   ^{:meta-on-coll 1}
   ['foo
    (with-meta 'bar {:meta-on-sym 2})
    'baz]
   :list
   '(1 2 3)
   :lazy-seq
   (range 10)
   :rainbow
   [[[[[[]]]]]]
   :set
   #{1 :2 "three"}))

(-> (? :data {:theme "Universal Neutral"} sample-map)
    :formatted
    :string)

The "Universal Neutral" theme works on both light and dark terminal backgrounds, so it is best to explicitly set that at the call site if you don't already have an environmental variable set that points to a Fireworks config.edn. If you setup that config you can specify one of several stock colorized themes, in a light or dark variant.

Should that be (signal->callout-opts signal), or am i looking at it wrong?

Thanks for the catch! 🙏 Fixed 👍

I wonder if the pretty-printing functionality from Fireworks might provide some utility for certain Telemere use cases.

Thanks for the suggestion! I'd not heard of it, will take a look.
Happy (almost) new year! Cheers :-)


On r/programming

I've added a few not participating subreddits, adding the ones where I've seen at least one mod post saying they will not be closing or restricting the subreddit, not adding the ones where there's just been silence.
There is one exception I'd like to ask about; r/programming features u/spez on the mod team, and so I suspect it's not participating, but there's been no formal post. I'm holding off on adding it now, but just wanted to open an issue to ask what the criteria for the list should be / for discussion.
(Also, some more subreddits have joined in! Although you're probably asleep right now. I hope you're getting some good rest!)

It seems like the general consensus is that pointing out which subs have decided to not participate would be harassment so I don't think I'll add a list of not participating subreddits.
Also, r/programming has decided to join! I'm so glad because I thought the same. Having an admin as the lead mod and the CEO as the second mod, I thought for sure they were not going to participate.

I've gone ahead and deleted the wiki page. (I've saved a copy on my own system, just in case, but I'm not putting it back up unless requested.)


fix: breaking change in core

What:

Additional issues:

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

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


tsdb/wlog.Checkpoint: Fix counting of histogram samples

I realized that histogram samples are wrongly counted in tsdb/wlog.Checkpoint, in that float samples are counted against stats.TotalSamples and stats.DroppedSamples respectively instead.
This PR rectifies the bug, and augments TestCheckpoint to verify that stats.TotalSamples and stats.DroppedSamples are correctly updated.
That said, I don't think any callers of Checkpoint use the stats return value. Should it be dropped?

Good catch!
It wasn't used even in the PR that introduced it https://github.com/prometheus-junkyard/tsdb/pull/332, maybe it was meant for debugging/dev?
Maybe some external clients could be relying on it, it has been around for a long time.

Good question, I'm not familiar with that part of the code, I'll need to take a look.

I approve the fix, but let's hold back merging this until we have an idea if the stats can be ripped out entirely.

Big picture, I want more stats about checkpoint.  Quite often when I look at big memory usage, especially in Agent mode, it seems associated with the TSDB checkpoint, but it's hard to see what happened.  Checkpoints only happen every 2 hours, and usually it takes days for the data to build up.
I guess I should try to write a PR that adds the information I would find useful.

also we need float histograms indeed

@bwplotka I can open another PR to count also float histograms then.

Totally

Made PR to make Checkpoint handle float histograms @bwplotka.


SWR: Duplicate identifier 'query'

i have an api that request as parameter query
since query in the generated useSwr already exist as constant it's conflicting
export const getResponsesControllerSearchResponsesKey = (query: string,) => [/api/v1/responses/search/${query}];
export const useResponsesControllerSearchResponses = <TError = unknown>(
 query: string, options?: { swr?:SWRConfiguration<Awaited<ReturnType<typeof responsesControllerSearchResponses>>, TError> & { swrKey?: Key, enabled?: boolean }, request?: SecondParameter<typeof customInstance> }

  ) => {

  const {swr: swrOptions, request: requestOptions} = options ?? {}

  const isEnabled = swrOptions?.enabled !== false && !!(query)
    const swrKey = swrOptions?.swrKey ?? (() => isEnabled ? getResponsesControllerSearchResponsesKey(query) : null);
  const swrFn = () => responsesControllerSearchResponses(query, requestOptions);

  const query = useSwr<Awaited<ReturnType<typeof swrFn>>, TError>(swrKey, swrFn, swrOptions)

  return {
    swrKey,
    ...query
  }
}

I'm having the exact same problem. I've tried renaming the parameter in the output.override.transformer part of the config, but it's really wonky and doesn't work properly. Unsure how to solve this correctly?

I "solved" it by doing a find-and-replace using a different package that is ran in the generated files containing the hooks:
from: /const query = useSwr<Awaited<ReturnType<typeof swrFn>>, TError>(.+)\s+return {\s+swrKey,\s+\.\.\.query,\s+}/g,
to: "const _query = useSwr<Awaited<ReturnType<typeof swrFn>>, TError>$1\n\nreturn {\nswrKey,\n..._query,\n}",

Not ideal, but works for now. Best would be if the generated variable names that are not exposed outside the file would get a more distinct name than query. Maybe something like ___query  would be good enough?

I have considered several ways to deal with this problem:

Define variable names used in generated functions as reserved words and perform input validate before generating source code.
Providing an input check will increase the overhead in executing the source code generation process.

If you do not want to change the name of the parameter used in the OpenAPI definition, change the name of the function argument output by transformer.
Although it can be used as is, it will be inconvenient as users will have to understand this problem before implementing the function.

As suggested, add a _ prefix to all variable names in functions so that they do not affect the input OpenAPI definition.
All variable names in automatically generated functions must be updated. The scope of impact is large, but it is possible. Users who encounter this problem will be saved

@melloware
Hi, Please check the above countermeasures.
3 is the most effective, but you will have to be careful about variable names in functions in all future developments. Also, in the first place, if an unintended name such as query is given to a parameter name, I think it would be a good idea to ask the user to make their own judgment and avoid it.
I think you can either deal with 3 based on these, or close this issue if it is unnecessary.
What do you think?

I think 3 makes the most sense. If they are param values.

@melloware
Ok, I'll handle this, so could you assign this issue to me?

fix by https://github.com/anymaniax/orval/pull/1130

Excellent I assigned you the ticket and made one code review comment.


Adding Support for Fiat Chrysler Infotainment

A case required the use of VLEAPP for a Jeep Cherokee infotainment system. We created two artifacts for use with the diagnostic data as well as the bluetooth device logs. Please ignore the updated requirements file

Ignore like not merge the requirements.txt file?

Correct.

Think you could share a image of the process data with any sensitive data redacted? Would like to let everyone in digital forensics social media of the new VLEAPP artifact. Also please provide the twitter, linkedin, blogpost or any other handle you would like me to credit for the artifact.
Thank you so much!!!!!

Yes. Give me a day or two to go through the image and remove sensitive data. Where should I send the image?

Run the tool and take a couple of screenshots. Edit the screenshots. No
need to send the actual source data. 👍
<EMAIL_ADDRESS>On Sun, Jun 4, 2023, 11:53 PM Joe Dinsmoor @.***> wrote:

Yes. Give me a day or two to go through the image and remove sensitive
data. Where should I send the image?
—
Reply to this email directly, view it on GitHub
https://github.com/abrignoni/VLEAPP/pull/29#issuecomment-1575998112, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AG3DPC7DXGTS2XGI2JSEB4DXJVJ25ANCNFSM6AAAAAAYYPNOPE
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Run the tool and take a couple of screenshots. Edit the screenshots. No need to send the actual source data. 👍<EMAIL_ADDRESS>…
On Sun, Jun 4, 2023, 11:53 PM Joe Dinsmoor @.> wrote: Yes. Give me a day or two to go through the image and remove sensitive data. Where should I send the image? — Reply to this email directly, view it on GitHub <#29 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AG3DPC7DXGTS2XGI2JSEB4DXJVJ25ANCNFSM6AAAAAAYYPNOPE . You are receiving this because you modified the open/close state.Message ID: @.>

I'll get that to you later today.


FileNode: checking for vers ctrl on each node seems very laggy

the highlighting of nodes that are not under VC is very cool, but opening the tree view seems very laggy, especially in larger projects (e.g., when I opened the golang std library tree which I often do).
probably need to have a separate process that does the checking, only once?  UpdateNode is called frequently, so not great to have it there.  Also you definitely want to cache the result of "UsesGit" in the root instead of searching every time!!  that would speed things up a lot.
also I just looked at this code for the first time - would be better to have a more generalized framework that isn't just git or svn -- there are various other VCS's that people use.. we may not support immediately but want to have a generalizable framework..
Ideally make an interface that does all the relevant VC functions, and define that for the relevant instances, and then cache the relevant instance once you figure out (one time only, in the root node) which vc it is using.  Then you just call those interface methods and it is very nice :)
I just did a quick search and there is a similar approach here: https://github.com/Masterminds/vcs -- not sure if it has all the relevant functions but if not, maybe better to add to it and see if they'll take a PR and if not, fork from there..
they also reference: https://godoc.org/golang.org/x/tools/go/vcs which might be relevant.

Mastermind has a lot of api for high level vcs stuff that we don't have and it has a generic function for executing a command that is similar to what I wrote for doing add, delete, move etc. I think a separate interface for those actions along with the interface from mastermind will work well and I'll cache the vcs type in root. Not sure why they didn't include the basic add, delete, move in the api and went with the general exec.cmd but I think that is fine and you need the general function anyway. Thanks for reviewing the code.

The new implementation sets the flag on the file node when the directory is opened. After that the flag is simply checked. If you call Add on the repo the flag is also set then and if you do a remove from repo while keeping a local copy of file the flag is set to false. Seems to be pretty quick.
I threw away all of the prior vcs code and rewrote using mastermind vcs and an interface that includes funcs for add, remove, move, etc that we can continue to add to. I've only implemented the Git calls but adding svn or any other is a trivial matter now that we have the interface.


Readonly on worlds outside of the default one causes issues

When readonly is enabled, joining a secondary world causes issues, in the corner of the map it seems that blocks from the default world are overlapping but they aren't really there, when you break them the right blocks show
This only happens when ReadOnly is enabled
https://user-images.githubusercontent.com/13991048/181633706-ec5e3ee6-7598-494c-a1ab-a46ea230fe72.mov

I noticed something else that may be related, I previously have loaded this world as my default world and the name of it is the same as the default one ("My World"), but now that it's not the default world that may be why this is happening

Bigger part of the other world being loaded alongside it, also ReadOnly seems to have no effect now?

Update: it is now happening to the default world aswell