Android enhancements - Cascade

Hey @mpiannucci
Would like to preface this with saying that this is an amazing library, works really neat for my use cases!
Since the iOS side basically hooks up into the iOS' native components, I find that the native components are developed really nicely, with e.g. submenus and stuff like that. However, since the Android implementation is using PopUpMenu, and PopUpMenu is pretty plain in comparison to iOS implementation, the Android side is pretty barebones and causes a feature disparity of sorts between platforms. Recently I found this native Android library which has great features and which are pretty similar to iOS implementation in that regard, e.g. with respect to nested menus. I think making use of that library is something this library could benefit from. What are your thoughts on this? Are you open to integrating something like this?

I am definitely open to it, bonus points if it can be optional for people since it requires a third party lib.

@fobos531
Im add Cascade to this library and testing it now.

Add background color change
Add android system icons
Add text color change

I'm also going to add a submenu
https://gitlab.com/getgain-public/libs/react-native-context-menu

@fobos531 Im add Cascade to this library and testing it now.

Add background color change
Add android system icons
Add text color change

I'm also going to add a submenu
gitlab.com/getgain-public/libs/react-native-context-menu

@VladlenKaveev
That's awesome! Do you plan to contribute this to this repository?

@fobos531
Yeah, i do some tests and add submenus. And its be ready to PR)

@VladlenKaveev   thanks you bro, did u work as expected? I waiting this page from it's created

@fukemy
I create Pull Request, but im not have time to add submenus support now. I add a little bit later!
#61

@mpiannucci plz update this, we waiting it's too long times

hi @VladlenKaveev , can u help my error when run debug android:

e: /Users/thehe/.gradle/caches/transforms-3/155d90119e1ea8ce9426eb8c5edb0bed/transformed/jetified-kotlin-stdlib-common-1.7.0.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/META-INF/kotlin-stdlib.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/thehe/.gradle/caches/transforms-3/748dc90b8badbb0240fef9d70296b9b0/transformed/jetified-kotlin-stdlib-jdk7-1.7.0.jar!/META-INF/kotlin-stdlib-jdk7.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (52, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (53, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (57, 21): Unresolved reference: until
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (82, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (86, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (90, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (99, 34): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (107, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (108, 15): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (109, 22): Not enough information to infer type variable T
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (109, 57): Unresolved reference: java
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (114, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (115, 26): Unresolved reference: apply
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (116, 24): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (116, 47): Type mismatch: inferred type is ContextMenuView but Menu! was expected
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (118, 21): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (119, 9): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (123, 33): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/ContextMenuView.kt: (130, 33): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class
e: /Users/thehe/Desktop/VedaxLink/node_modules/react-native-context-menu-view/android/src/main/java/com/mpiannucci/reactnativecontextmenu/RoundedRectDrawable.kt: (7, 5): Class 'kotlin.Unit' was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.7.1, expected version is 1.5.1.
The class is loaded from /Users/thehe/.gradle/caches/transforms-3/1b41006eaf97cd4ef46181975839521c/transformed/jetified-kotlin-stdlib-1.7.0.jar!/kotlin/Unit.class

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-context-menu-view:compileDebugKotlin'.
> Compilation error. See log for more details

@fukemy i think you need update your kotlin version in build.gradle

thanks bro, i downgrade kotlin version to 1.3.50 and it's worked

@VladlenKaveev Are system icons already displayed under Android?

Android now supports icons and nested menus. Closing this.


Add versioning for Mobiledoc renderer, parser

Introduces versioning for the Mobiledoc parsers and renderers.
Each of now have a directory with files representing their versions:
src/js/renderers/mobiledoc/0-2.js
src/js/renderers/mobiledoc/index.js
src/js/parsers/mobiledoc/0-2.js
src/js/parsers/mobiledoc/index.js
tests/unit/renderers/mobiledoc/0-2-test.js
tests/unit/renderers/mobiledoc-test.js
tests/unit/parsers/mobiledoc/0-2-test.js
tests/unit/parsers/mobiledoc-test.js

Normal library code should nearly always use the render and parse methods on the index files:
import mobiledocRenderers from 'mobiledoc-kit/renderers/mobiledoc';
let mobiledoc = mobiledocRenderers.render(post /*, version */);

import mobiledocParsers from 'mobiledoc-kit/parsers/mobiledoc';
let post = mobiledocParsers.parse(builder, mobiledoc);

version for the renderer is supported but does not seem like it will be needed. Parsers pick a version based on the mobiledoc.
The mobiledoc.build helper now accepts a version string:
import Helpers from '../../test-helpers';
let mobiledoc = Helpers.mobiledoc.build(({post, markupSection, marker}) => {
  return post([markupSection('p', [
    marker('Howdy')
  ])]);
}, '0.3');

However it is strongly recommended that you always access version numbers via a constant exported from the renderer. This is done the 0.2 code in this PR.
/cc @rlivsey @bantic

Is there a reason we are using only major-minor version numbers? Can we switch to major-minor-patch semVer style, '0.2.0', '0.3.0' ?

Aye they are really just strings, for now at least.
Mergin'


Virtual displays now use serial number as preferences ID appendix.

There was an issue regarding virtual displays (DisplayLink, Sidecar etc) - the app uses CGDirectDisplayID as a preference ID suffix alongside the display name and vendor/model number. Since on every connect this id is changing for these displays, MonitorControl could not track preferences associated to these displays (+ the preferences store was polluted with dead items as well). This is now fixed, we now use the system generated, permanent serial number as suffix for virtual displays. For real displays we continue to use CGDirectDisplayID as the serial number is often the same for identical displays which causes issues in multi-display configs with similar physical displays.

An other day, an other fix. Approve this one please. :) This is an addition to the bugfix release 4.0.2. Thanks!


Some early jun are not reviewed

I've seen a few times when for the first few jun when Akochan thinks an honor tile should be discarded, no analysis is given even if the player didn't discard said tile.
Here's an example from a Suphx game
akochan-reviewer.exe --no-open -n 0.4 --pt 75,30,0,-105 "https://tenhou.net/4/?log=2019031218gm-0029-0000-d756d03c&tw=1"

This behavior is intended.
Akochan runs in rule-based mode under certain conditions, like if the game is at an early stage, and our shanten number is high, and we are not folding currently. In such mode, akochan will choose the most efficient tile to discard and doesn't bother calculating any deal-in rate or EV, so only one choice without any EV info will be produced. It is not that akochan can't run with normal mode instead of rule-based mode under such circumstance, but the cost will be much higher making the review slower.
If the reviewer sees akochan running in such mode, it is not sure how to compare the discards akochan and the player made due to the lack of information, so it simply gives up doing that, leaving it as an accepted entry even if the choices are different.

So if we want that information using normal node we'll have to modify akochan? I'm confused by early round choices very often so it would be great if we have a switch.

Yes you'll need to modify akochan.
In ai_src/selector.cpp:Selector::set_selector
-const bool rule_base_flag = tehai_analyzer.rule_base_decision(my_pid);
+const bool rule_base_flag = false;

Thanks! Since I'll not be able to test in the very near term let me close the issue.


Voxel h5 format

Thanks for the great work!
Generating voxels from the v2e sim produces dictionaries with x,y,t,p keys. How should i save them in the h5 format so it can be loaded to model.

added the code just now


Update Blog “first-blog-post-and-how-to-create-a-blog-website”

Automatically generated by Netlify CMS

👷 Deploy Preview for cool-toffee-ab3b21 processing.

Name
Link

🔨 Latest commit
b13908d2a21aba32f28682d67090a9bfcb442e97

🔍 Latest deploy log
https://app.netlify.com/sites/cool-toffee-ab3b21/deploys/63eb16d75cbfe80008791b30


'PyPDF3.utils.PdfReadError: file has not been decrypted' when encryption is set

When creating an encrypted PDF, following the official guide(https://xhtml2pdf.readthedocs.io/en/latest/encryption_and_signatures.html), it will raise an exception 'PyPDF3.utils.PdfReadError: file has not been decrypted'.
Solve it by using the PyPDF3 to encrypt the PDF just before returning from pisaDocument function, instead of creating an encrypted PmlBaseDoc object.

Sorry the encrypt functionality it does by pyhanko an not by PyPDF3, also PyPDF3 will replace by pypdf in next version.


Explain keys purpose in yaml file clearly in documentation

Indeed, this is very important and not clearly explicited in the wiki.
I guess it should be explained in this page :
https://github.com/codalab/codabench/wiki/Yaml-Structure
I don't know if there is also a page about scoring program.
Basically, the keys need to match the keys of the scores.txt file output by the scoring program.


Would it possible to update for Godot 4.3？

Hi narredev,
Thanks for your great work, this addon is better than using GirdMap.
As we can see, Godot will be more powerfull, but the TileMap node is deprecated in 4.3.
By the way, I noticed the Scene Preview always use the fall_tex at res://maps/map_XX.tscn.
Would it possible to update for Godot 4.3？
Thanks and best regards.

Hi, thanks for checking out my addon!
I think updating the addon is possible, since most of the stuff in TileMapLayers is the same, but it would be necessary to change how it's structured due to layers now being nodes.
Sadly right now I'm occupied with other projects, so I can't work on it. But I'll try updating it in the future!
I think the next version of Godot will introduce some changes to the gridmap, so maybe that could fill the gap.


feat(edc 0.7.0): integrated the latest edc in the backend + e2e bugs solved

Why we create this PR?
Integrate the new EDC v0.7.0 is a requirement for the next release and solve e2e bugs found.
What we want to achieve with this PR?
Be able to use the functionality from the EDC 0.7.0 in the backend.
What is new?
Added

EDC v0.7.0 models
Optimization in the catalog query using bpn
Updated EDR structure
Added lombok dependency to speed the development

Updated

Updated EDR structure to match new EDC 0.7.0 one

Issues Fixed

Fixed issue with multiple contract and policies parsing
Optimized data sovereignty checks removing spotted bugs
Fixed issue when policy is selected in the frontend
Fixed issue when backend is not available in the fronted

PR Related
Closes #302
Closes #265
Closes #275
Closes #273

No IP issue found


build: fix

Description
Todos

[ ] Unit tests
[ ] Manual tests
[ ] Documentation
[ ] Connect epics/issues
[ ] Tag type of change
[ ] Upgrade handler

Steps to Test
Expected Behaviour
Other Notes

Seems previous build script only works on mac. Some minor fix to make it work on linux systems(e.g:ubuntu21).
find this video about onboarding a new chain
https://www.youtube.com/watch?v=iZgqneh7s88&ab_channel=Axelar
would like to know is there any wrapping script for the onboarding flow, then maybe I can help to test/verify it.


Remove azr enabled from cns

Reason for Change:
Remove azr enabled from cns

Issue Fixed:

Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

In the PR description please indicate that the change is to remove the config flag from CNS. The config flag is unnecessary

lgtm but want a review from @ashvindeodhar since it's changed a bit since the approval


add requirements, add region param, explicit param passing

Issue #, if available:
Description of changes:
Script improvements around parameters
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@meduncan - Some changes that I think will benefit the script, mostly recommended by PsScriptAnalyzer. The requirements I'm calling out explicitly since I didn't see where else that dependency gets added.


Thread interruption on timeout doesn't work (Testet with Hystrix 1.5.2 and 1.5.3)

i'm currently testing a command against a service that will never answer. This results in a thread pool with all threads active. In the thread dump I can see, that all these threads are stuck at "java.net.SocketInputStream.socketRead0".
I don't have any additional configuration in my project. That means the default values for "execution.isolation.thread.timeoutInMilliseconds", "execution.timeout.enabled" and "execution.isolation.thread.interruptOnTimeout" should result in interrupted threads after 1 second. but it doesn't work.
Hystrix is also unable to provide metrics about these thread pool. Spring's actuator endpoint "/metrics" contains no information about it and the Hystrix Stream / Hystrix dashboard also hasn't any information about this thread pool.

For thread interruption, Hystrix can't guarantee that the interruption actually happens.  Like all other code that runs on the JVM, you can only throw an InterruptedException, you can't force the wrapped code to catch it.  This is one of the reasons that Hystrix exists - we would much rather that a Hystrix thread gets stuck in this state than an application thread.
For the metrics issue, it's hard to debug your issue with this info.  If you add some breakpoints/printlns, you should be able to loop over the HystrixThreadPoolMetrics.getInstances values and see what instances of metrics are in your code.  You should also be able to take a thread dump and see what threads are actually getting setup.  Those may help you understand more about what's happening.

@carlmoser - a question: when this happens, is the circuit breaker then perhaps stuck in an open state? I am hunting a problem where a specific circuit breaker trips (goes OPEN) and then stays open (as far as I could test this persists until I restart the container).
This circuit breaker in question is protecting a remote resource that may respond very slowly (or infrequently, but often enough might just hang or throw a socket exception).
Currently I have increased this circuit breaker's thread pool to a core size that I consider insanely large (60), and I'm monitoring it - this is how I noticed a slowly climbing "active" count (for the thread pool), that so far shows no sign of going down again. I am waiting to see if my symptoms kick in when the active count == core size.

@demaniak Circuit breakers only observe the flow of outcomes (Success/Failure/Timeout/etc).  The only way that circuit breakers remain open is:

They trip in the first place by reaching the minimum volume threshold and minimum error threshold
A subsequent attempt on that circuit does not succeed.

By default, after 5 seconds of the circuit being open, 1 single command is attempted.  If it succeeds, the circuit goes back to CLOSED and is subject to re-opening as above.  If it fails, it stays OPEN for another 5 seconds.
Can you check what's happening on requests through your circuit breaker after it's already been OPENed?

Thanks for the reply @mattrjacobs .
I agree completely with all the theory you mention.
So in order to get to the bottom of this, I have dropped the log levels to DEBUG to see if anything "obvious" jumps out.
After that  I started watching the Hystrix dashaboard, and noticed the active thread count slowly climbing.
And now I have hit the issue again: the circuit breaker is open (and is STAYING open), and the active thread count == pool size.
I have trawled through the (very noisy) logs as it stands, but nothing springs out - in fact it is suspiciously devoid of any hystrix loggers. All I can say for certain is that the fallback methods get called immediately when we attempt to call the @HystrixCommand annotated methods (for that specific thread pool).
Any specific logback config I can add to force more info out of the circuit breaker libs?
Thanks in advance.
PS: I am not sure if my problem actually relates to this particular issue (but it is the closest I could find after a lot of searching), should I perhaps rather open a new issue?

Ok, I have manged to duplicate this situation on my local machine with a core thread size of 5.
So, first of all, I noticed that every now and then, I would get a SocketException when contacting the remote service.
So once I hit this persistent OPEN state on the CB, I poked a round with jvisualvm a bit, and after installing he "Thread Inspector"  plugin for jvisualvm, I could observe this stack trace in the relevant hystrix thread pool threads (after they got stuck in the active state):
java.lang.Thread.State: RUNNABLE
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	at java.net.SocketInputStream.read(SocketInputStream.java:170)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
	at sun.security.ssl.InputRecord.read(InputRecord.java:503)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:973)
	- locked <beec12d> (a java.lang.Object)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
	- locked <72c6dcee> (a java.lang.Object)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
	at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
	at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:559)
	at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185)
	at sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(HttpsURLConnectionImpl.java:153)
	at org.springframework.http.client.SimpleBufferingClientHttpRequest.executeInternal(SimpleBufferingClientHttpRequest.java:80)
	at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48)
	at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:53)
	at org.springframework.http.client.InterceptingClientHttpRequest$InterceptingRequestExecution.execute(InterceptingClientHttpRequest.java:93)
	at org.springframework.cloud.netflix.metrics.MetricsClientHttpRequestInterceptor.intercept(MetricsClientHttpRequestInterceptor.java:65)
	at org.springframework.http.client.InterceptingClientHttpRequest$InterceptingRequestExecution.execute(InterceptingClientHttpRequest.java:85)
	at org.springframework.http.client.InterceptingClientHttpRequest.executeInternal(InterceptingClientHttpRequest.java:69)
	at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48)
	at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:53)
	at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:596)
	at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:557)
	at org.springframework.web.client.RestTemplate.exchange(RestTemplate.java:503)
	at org.springframework.web.client.RestTemplate$$FastClassBySpringCGLIB$$aa4e9ed0.invoke(<generated>)
	at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	at org.springframework.aop.aspectj.MethodInvocationProceedingJoinPoint.proceed(MethodInvocationProceedingJoinPoint.java:85)
	at org.springframework.cloud.netflix.metrics.RestTemplateUrlTemplateCapturingAspect.captureUrlTemplate(RestTemplateUrlTemplateCapturingAspect.java:33)
	at sun.reflect.GeneratedMethodAccessor132.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethodWithGivenArgs(AbstractAspectJAdvice.java:620)
	at org.springframework.aop.aspectj.AbstractAspectJAdvice.invokeAdviceMethod(AbstractAspectJAdvice.java:609)
	at org.springframework.aop.aspectj.AspectJAroundAdvice.invoke(AspectJAroundAdvice.java:68)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:92)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
	at org.springframework.web.client.RestTemplate$$EnhancerBySpringCGLIB$$d910d584.exchange(<generated>)
	at com.somecompany.someclient.remote.service.impl.QxyzRestCommsServiceImpl.doAuthenticatedPost(QxyzRestCommsServiceImpl.java:96)
	at com.somecompany.someclient.remote.service.impl.BasicThingServiceImpl.create(BasicThingServiceImpl.java:76)
	at com.somecompany.someclient.remote.service.impl.CachingThingServiceImpl.create(CachingThingServiceImpl.java:36)
	at com.somecompany.someclient.remote.service.impl.CachingThingServiceImpl$$FastClassBySpringCGLIB$$35d03493.invoke(<generated>)
	at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
	at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
	at org.springframework.cache.interceptor.CacheInterceptor$1.invoke(CacheInterceptor.java:52)
	at org.springframework.cache.interceptor.CacheAspectSupport.invokeOperation(CacheAspectSupport.java:320)
	at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:353)
	at org.springframework.cache.interceptor.CacheAspectSupport.execute(CacheAspectSupport.java:302)
	at org.springframework.cache.interceptor.CacheInterceptor.invoke(CacheInterceptor.java:61)
	at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
	at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:655)
	at com.somecompany.someclient.remote.service.impl.CachingThingServiceImpl$$EnhancerBySpringCGLIB$$39ef00a6.create(<generated>)
	at com.somecompany.someclient.remote.service.impl.AaToBbThingService.create(AaToBbThingService.java:45)
	at com.somecompany.someclient.remote.service.impl.CircuitBreakingThingServiceImpl.create(CircuitBreakingThingServiceImpl.java:66)
	at sun.reflect.GeneratedMethodAccessor166.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.netflix.hystrix.contrib.javanica.command.MethodExecutionAction.execute(MethodExecutionAction.java:116)
	at com.netflix.hystrix.contrib.javanica.command.MethodExecutionAction.executeWithArgs(MethodExecutionAction.java:93)
	at com.netflix.hystrix.contrib.javanica.command.MethodExecutionAction.execute(MethodExecutionAction.java:78)
	at com.netflix.hystrix.contrib.javanica.command.GenericCommand$1.execute(GenericCommand.java:47)
	at com.netflix.hystrix.contrib.javanica.command.AbstractHystrixCommand.process(AbstractHystrixCommand.java:146)
	at com.netflix.hystrix.contrib.javanica.command.GenericCommand.run(GenericCommand.java:44)
	at com.netflix.hystrix.HystrixCommand$1.call(HystrixCommand.java:293)
	at com.netflix.hystrix.HystrixCommand$1.call(HystrixCommand.java:289)
	at rx.internal.operators.OnSubscribeDefer.call(OnSubscribeDefer.java:46)
	at rx.internal.operators.OnSubscribeDefer.call(OnSubscribeDefer.java:35)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.Observable.unsafeSubscribe(Observable.java:8460)
	at rx.internal.operators.OnSubscribeDefer.call(OnSubscribeDefer.java:51)
	at rx.internal.operators.OnSubscribeDefer.call(OnSubscribeDefer.java:35)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:50)
	at rx.internal.operators.OnSubscribeLift.call(OnSubscribeLift.java:30)
	at rx.Observable.unsafeSubscribe(Observable.java:8460)
	at rx.internal.operators.OperatorSubscribeOn$1.call(OperatorSubscribeOn.java:94)
	at com.netflix.hystrix.strategy.concurrency.HystrixContexSchedulerAction$1.call(HystrixContexSchedulerAction.java:56)
	at com.netflix.hystrix.strategy.concurrency.HystrixContexSchedulerAction$1.call(HystrixContexSchedulerAction.java:47)
	at com.netflix.hystrix.strategy.concurrency.HystrixContexSchedulerAction.call(HystrixContexSchedulerAction.java:69)
	at rx.internal.schedulers.ScheduledAction.run(ScheduledAction.java:55)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)

   Locked ownable synchronizers:
	- locked <5c11f33b> (a java.util.concurrent.ThreadPoolExecutor$Worker)

If I'm reading this right, it looks like we hit a deadlock or infinite waiting state while negotiating the SSL connection to the remote service...and then for some reason the raised exception does not free the hystrix thread?

When using a thread-isolated command, Hystrix defaults to interrupting the thread upon timeout.  As with all code that runs on the JVM, this is best-effort and Hystrix can't make any guarantees about how the code respects/does not respect the interrupt.

Noted, thanks @mattrjacobs .
So potentially ill-behaving servers/connections that get stuck in a dead read-loop, must always be handled specially (by setting a reasonable SO_TIMEOUT at the connection handler.)
This is the honestly the only issue I have picked up with Hystrix so far (and to be fair, not really a Hystrix issue, as explained above).
Can't speak for @carlmoser , but I can live with this issue being closed.

Yeah, there's really nothing that Hystrix can do - just isolate this misbehaving I/O in a non-application thread (which was one of the prime reasons for creating Hystrix).  Closing.

@carlmoser Try to invoke HttpUriRequest.abort() in getFallback() to close the connection

@mattrjacobs

For thread interruption, Hystrix can't guarantee that the interruption actually happens. Like all other code that runs on the JVM, you can only throw an InterruptedException,
after timeout, can we not interrupt the hystrix thread which is blocking on socket waiting for the response ? this way not only user thread, but also hystrix thread is freed to take up other requests

@vimalk78 the problem (in my case), was that there never was a timeout.  The IO-bound thread was hung by the low-level socket read loop that never completed.
And the main thing was - NOT always. The problem creeped in gradually over time, or faster under load.
Once I explicitly got a SO_TIMEOUT set, the socket read timed-out, and Hystrix performed correctly.
In my case, I was using Spring RestTemplate, and had to configure a custom HttpComponentsClientHttpRequestFactory, with appropriate configuration to get the SO_TIMEOUT in there.

For thread interruption, Hystrix can't guarantee that the interruption actually happens. Like all other code that runs on the JVM, you can only throw an InterruptedException, you can't force the wrapped code to catch it. This is one of the reasons that Hystrix exists - we would much rather that a Hystrix thread gets stuck in this state than an application thread.
For the metrics issue, it's hard to debug your issue with this info. If you add some breakpoints/printlns, you should be able to loop over the HystrixThreadPoolMetrics.getInstances values and see what instances of metrics are in your code. You should also be able to take a thread dump and see what threads are actually getting setup. Those may help you understand more about what's happening.

Does it mean if there is an exception in some different thread like Rabbit Listener, then it might lead to HystrixRuntime Exception during command.queue().


Tortoise ORM backend

Dear @arthurio , Is there any intention of having Tortoise ORM as backend for fastapi filter?
KR!

Hi @TatanParker,
Thanks for your question, I'm not familiar with Tortoise ORM so I don't plan on implementing it anytime soon. That said, if someone makes a PR for it It'd be more than happy to help and review it.

Nice, I like your branch, I will create a backend for my system and I will add it to a PR, thanks man

@TatanParker do you have any update about support for tortoise-orm?

@TatanParker i want use too!

I can try my luck with this next week 🌷


No module named 'openai'

Describe the bug
I have uninstalled openai and reinstalled it with pip and pip3,
I have checked that pip and openai are installed in the same folder
and various other internet solutions but nothing has worked
please help
I know its not a bug but i can't figure out how to log a normal issue :'(
To Reproduce
all i say is import openai
Code snippets
No response
OS
Windows
Python version
3.1.1
Library version
0.28.1

You need to make sure that the Python interpreter your IDE is selecting to run the files has the necessary library installed.
Assuming you are using VS Code you can use SHIFT+CTRL+P and then type Python: Select Interpreter to view a list of the interpreters and check which one you are using.
Sometimes when you work with virtual environments you have separate interpreters each with different libraries downloaded.

I'm having the same problem.  How was this resolved?
I've tried reinstalling openai and get "requirement already satisfied". When I attempt to import it responds with "No module named 'openai'"

So i was coding a plugin for unreal and i had to install open ai through unreal's python terminal with the following commands:
import sys
import pip
pip,main(['install', 'openai'])
subprocess.check_call(["pip", "install", "openai"])
check_call(["pip", "install", "openai"])
pip install openai


How can I start the challenges ?

The README file does not explain how to start the challenges and where to submit them.

@AymanProjects All challenge details exist in CHALLENGE.md file in the root directory. For easy access click here

A direct link to the challenge has been added in challenge readme file for better experience.


About GPS103 protocol implementation

Hello why in GPS103 protocol the traccar command are send with keyword as letters but in documentation say we need send keyword as number, I.E. the command to overspeed is 107 in documentation but traccar send this like H and if I send this with 107 not work... I have other question: where i can find the command to change ip and port in letters format to gps103 protocol? I already browse this in Internet and traccar documentation but i can´t find this to send as custom command and this is important for me, if you can help me i will be a very grateful

There seems to be two versions of GPS103 commands. One set is with numbers, the other one is with letters. Possibly they are for two different devices. I think letter-based commands came from some Traccar users. You can try to find them on GitHub.

But i have like 950 devices with GPS103 and in all work the letter command, i see this in your protocol documentation (an documentation in letters and other in numbers)

So, what is the question/problem?

i'm browsing for the command in letter to change ip massively of the devices connected in my server because the vps hosting provider have a 1000 tcp connections limit and currently it is almost the limit to collapse... I know how to send this command massively using custom command and some script

I got an update to gps103 documentation:
If you purchased the device after February 2015, it supports 2 different protocols, other wise, it can only use "in" protocol, and "in" protocol is the default protocol.
SMS command to change to "in" protocol: protocol123456 12 in
SMS command to change to "out" protocol: protocol123456 12 out
I used protocol+password+space+12+space+out to get the numbers in the protocol documentation.
Anton how do I send you a copy of the document to update gps103 protocol documentation?

You can send it by email. Address is in profile.


Full mode/any command option

Could it be good to have a special/secret option (0 or sth else) for being able to enter any Git command?

This can be changed in https://github.com/anneferger/lama/blob/c151d0f3d14a90854058f6539568552c18c11cd5/LAMA-3.0.sh#L214 by allowing commands to run when something other than one of the menu numbers is added. Maybe check if command is longer than 1 char or at least not a number to allow for mistyping

And probably don't allow rm operations for people with bad luck :D

@anneferger maybe you can have a look at the proposed solution in 6ed81c...


[DO NOT MERGE] Update to CMSIS 5.5.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Firebase Authentication - Proxy support

Is your feature request related to a problem? Please describe.
Firebase Auth does not work within countries that restrict access to google.com such as China.
Describe the solution you'd like
Ability to add proxy support within the GoogleServices-info.plist to redirect traffic to a non-blocked proxy which could forward traffic onto the Google service.
Additional context
N/A

Hello - this issue is out of the hands of these plugins. Please create a ticket over at https://firebase.google.com/support/ where Firebase can help.


Implement the clojure.test protocol

This is migrated from #70 which went off-topic.
@bbatsov created the issue originally:
Basically this would allow tools like cider-test to run expectations tests, which would benefit a lot of Clojure developers. More details - https://github.com/clojure-emacs/cider#using-cider-test-with-alternative-test-libraries and clojure-emacs/cider#1606

I have a very rough proof of concept working locally but there are some nasty gotchas:
The main issue is that (expect e a) produces a "random" symbol name (based on a hash of the form itself): if you change the test namespace and reload it, old definitions hang around (and the changed tests get new symbol names). Expectations mitigates this by not running expectations that have ::run metadata (which is added as each expectation completes, using Expectations custom report function). The "downside" is that you have to reload the test namespace, or re-evaluate the forms, to get those symbols back in play. The Emacs / REPL workflow we've adopted with Expectations is to evaluate either a single test or the whole namespace whenever we want to run them: this is kind of nice for working with tests as you write them but isn't an entirely smooth workflow overall.
If I make the CIDER integration follow that behavior, C-c C-t r doesn't work and neither do repeated C-c C-t n runs. You have to go back to the test namespace and reload it. If it doesn't follow that behavior, old tests just hang around and get re-run every time.
The other issue is that Expectations assumes a lot of context: when you run tests, you generally do it at the namespace level and it loads an expectations-options namespace, sets up before-run and in-context fixtures, watches for state changes etc, runs a set of tests and then tears it all down. As far as I can tell, working with CIDER test, there's no effective way to make this happen -- short of running test-vars for each expect form (i.e., for the :test function attached to the symbol it generates -- which will do all of the set up and tear down for each expectation).
My first approach was to do exactly that -- generate a function that ran test-vars and attach it as :test metadata but that is problematic due to setup/teardown (and it would need to rebind how the expectation reported its result which gets ugly pretty fast).
My second approach was to generate a function for :test that called a variant of doexpect that in turn called into clojure.test/do-report after mapping Expectations' compare-expr result data structure. This was much easier but loses expectations-options etc and still falls foul of the "random" symbol names.
I'm open to other suggestions but I think at this point the only option is to look into a syntax variant that provides fixed symbol names for expectations. This will alleviate the "random" symbol problem (and would make the existing Emacs / REPL workflow a lot smoother since expectations would no longer be "removed" as they are run, so you wouldn't need to reload the tests all the time).
If clojure.test compatibility -- and therefore CIDER test compatibility -- is handled via a separate namespace that relies on named expectations, then much of this becomes much more tractable. Running test-vars on a per-symbol basis becomes much easier (even tho' it's still really the wrong way to do things) since the defined expectation function could call the clojure.test/do-report function instead of expectations/report and so on. This is going to be the path I go down next.

(copied from #70)
Regarding this particular issue of CIDER integration, I'm just not sure it can be made to work effectively without moving to a "named symbol" approach since so much of what CIDER (and the clojure.test infrastructure) assumes, is based around being able to run individual tests, so "the same syntax" would have to move a little, at least for folks who want that integration (and, FWIW, I do find naming tests, or groups of tests, to be useful from a documentation p.o.v.).
It could be as minimal as a wrapper that assigns a symbol name to one or more expectations:
(defx my-tests
  (expect e1 (some-expression v1))
  (expect e2 (some-expression v2)))

That would be the easiest syntax to migrate to (since you could wrap a whole namespace of expectations in a single defx to start with). Or it could be an additional expect form like this:
(expect-named my-test1 e1 (some-expression v1))
(expect-named my-test2 e2 (some-expression v2))

(the disadvantage is you'd need to explicitly edit and name every expect form in your current test suite for this).

A requirement from #85 is that we should be able to add (arbitrary) metadata to the named symbol that identifies the test, to better support the needs of tooling.

clojure.test tooling compatibility has now become a priority at World Singles so this is going to get worked on, starting this week. My current thinking is a new expectations.clojure.test namespace offering defexpect as a named expectation -- the key thing needed for clojure.test "compatibility":
(defexpect my-test1 e1 (some-expression v1))
(defexpect my-test2 (more-of {:key [a b]} true a coll? b) (some-expression v2)))

In other words, exactly like expect but introducing a fixed name for the underlying function.
The current expectations namespace will continue to function exactly as-is. Wherever I need to change the behavior to satisfy tooling's expectations(!) of clojure.test-like behavior, I will duplicate code into the new namespace and modify its behavior (most likely around the clojure.test reporting logic) but I'm hoping to reuse most of the comparison machinery. defexpect will create functions the same way clojure.test/deftest does: with the actual test attached as :test metadata and a body that calls clojure.test/test-var on itself.
I'll update this ticket with any issues I run into or any questions about changes in behavior that may be required for this approach.

clojure.test tooling compatibility has now become a priority at World Singles so this is going to get worked on, starting this week.

Great news!

The current expectations namespace will continue to function exactly as-is. Wherever I need to change the behavior to satisfy tooling's expectations(!) of clojure.test-like behavior, I will duplicate code into the new namespace and modify its behavior (most likely around the clojure.test reporting logic) but I'm hoping to reuse most of the comparison machinery. defexpect will create functions the same way clojure.test/deftest does: with the actual test attached as :test metadata and a body that calls clojure.test/test-var on itself.

Sounds like a pretty reasonable approach to me.

I have a "first cut" of this but in order to push a build to Clojars, I need to be added to the expectations group on clojars.org @jaycfields

If anyone wants to play with this locally, the only addition is expectations.clojure.test/defexpect which is a macro that names expectations.
You can either wrap a group of existing expectations:
(ns my-example
  (:require [expectations :refer :all]
            [expectations.clojure.test :refer [defexpect]]))

(defexpect my-tests
  (expect e1 (some-expression v1))
  (expect (more-of {:keys [a b]} true a coll? b) (some-expression v2)))

or you can just give names to existing expectations by replacing expect with defexpect some-name:
(ns my-example
  (:require [expectations :refer :all]
            [expectations.clojure.test :refer [defexpect]]))

(defexpect my-test1 e1 (some-expression v1))
(defexpect my-test2 (more-of {:keys [a b]} true a coll? b) (some-expression v2)))

This creates a deftest behind the scenes (and turns off run-on-shutdown!) so, in theory, all clojure.test tooling and functionality should work with it exactly "as-is".
What you lose is some of the fancier aspects of failure reporting (and if you wrap defexpect around a large block of existing expectations, any failures will be reported again the line that defexpect is on), but it "works" as a starting point.

Note: wrapping existing expectations that have only (expect (some-expression v3)) -- i.e., the implicit "expect true" -- doesn't work (and probably fails in a bad way).
Also, as an artifact of how the defexpect macro works, you can also do this:
(ns my-example
  (:require [expectations :refer :all]
            [expectations.clojure.test :refer [defexpect]]))

(defexpect my-tests
  e1 (some-expression v1)
  (more-of {:keys [a b]} true a coll? b) (some-expression v2))

and you can mix and match that style with (expect e a) but I don't think I'd recommend either of those... and it may be worth preventing that for release.

I think you're good to go @seancorfield. I added you to the clojars group.

Thanks @jaycfields -- I published a 2.2.0-SNAPSHOT to Clojars and updated the docs with an experimental clojure.test page added.

Verified lein test and boot test (via adzerk/boot-test) both work. Also verified the "run tests" functionality in ProtoREPL (Atom) works.
Note: the new style tests run only under clojure.test tooling; the old style tests run only under Expectations tooling. In order to migrate piecemeal, you'd need to run lein do expectations, test or boot expectations test (or run a watcher for each type of test).
At this stage, I'll consider this issue resolved and any bugs or enhancement requests can be raised as new issues. I'll continue to flesh out the documentation over the next week or so.


deno_options: config spacer issue

Issue Type

[x] Bug Report
[ ] Feature Request
[ ] Other

Expected

src/tsconfig.app.json

{
  "compilerOptions": {
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  }
}

deno-workspace.yml

scripts:
  # deno run --allow-net --allow-read --config ./src/tsconfig.app.json app.ts
  # deno run --allow-net --allow-read --config=./src/tsconfig.app.json app.ts
  start:
    file: app.ts
    deno_options:
      allow-net: true
      allow-read: true
      config: ./src/tsconfig.app.json
  develop:
    file: main.ts
  globals:
    deno_options:
      allow-read: true

Expected to execute like: deno run --allow-net --allow-read --config ./src/tsconfig.app.json app.ts
> denox run start
Compile<EMAIL_ADDRESS>register Controller:  HomeController
register route:  /home/text
register route:  /home/json
Server start in :8000

Actual

Actual to execute like: deno run --allow-net --allow-read "--config ./src/tsconfig.app.json" app.ts
> denox run start
error: Found argument '--config ./src/tsconfig.app.json' which wasn't expected, or isn't valid in this context
        Did you mean --config?

USAGE:
    deno run <SCRIPT_ARG>... --allow-net=<allow-net> --allow-read=<allow-read> --config <FILE>

For more information try --help

Possible Solutions

I tried to revise the spacer of the config from " " to "=", it seems could be a workaround. I tested it, it seems working fine. But I am not sure is there is another way to let the --config argument not to combine with --config as a string.
https://github.com/yihua1218/denox/commit/c9e36860f16ceb5331d7ab95a7c801a9144cdb4c
Info

DenoX version: denox/0.3.0 darwin-x86_64 deno-1.0.0

Thank you @yihua1218 for catching this bug, could you make a PR with your commit yihua1218@c9e3686
After seeing your issue I'm adding more tests to be sure to catch those errors in the future


Weekly Newsletter

I'm adding some placeholder weekly images until we have an official one from Agata.

@johnnymatthews fyi I updated your text about auto-applying the weekly image (since it doesn't seem to be correct)


Deep session interest network for CTR

Do you have a plan to implement Deep session interest network for CTR paper (https://arxiv.org/abs/1905.06482)?

@minarastgar  Sorry, we don't have this plan yet. I'll consider it and thank you for your proposal.


don't broadcast abrousse's joins and parts

there's a member in the darwin chat with a broken computer, connection, something like that. he's a cool guy, so it'd be nice to see what he says but our chat is full of annoying JOIN and PART messages from him. irccloud doesn't support filtering out JOIN and PART messages from one particular user, and i suspect other users either don't have clients that support this, or don't have the know-how to set it up themselves. this change will make the chat and improved experience for everyone.
primary reviewer: @slingamn
tested locally:

Shipit from me! Sorry for the spam! I'm going to stop traveling around end of January, so we can safely revert this then ;)

This change is unsuitable for merge into oragono's master branch; I'll consider temporarily cherry-picking it for irc.darwin.network's deploy tree.

Hmmmmmm. This sort of functionality (filtering out joins/parts) does exist in some other servers with more general implementations based on channel modes, so might be worth looking into down the road at least. Thanks for the contribution either way @ArnaudBrousseau, always appreciate it :)

@sumeet I "fixed" this by installing ZNC on a box of mine:

My hopping around South-East Asian wifis shouldn't cause joins/parts messages anymore ;)


use the GLAD-S2 dataset

we are currently using the glad-L dataset we should allow user to use the glad-S2 one as well. Note that I don't know where they are

https://glad.earthengine.app/view/s2-forest-alerts#lon=-64.29861048809664;lat=-9.85129363173061;zoom=13;

The code is nearly ready but the covered area is super small (only north part of south america). Let's come back to it once it become a worldwide dataset:
https://code.earthengine.google.com/a3ec0d5e3ef12ecf0a2b1a8beaead2a6


mapping for gain-channels?

Would it be good to define the mapping for the gain channels in waveforms?
I.e. something like {'low-gain': 0, 'high-gain': 1} ?

@kosack proposed using an enum here:
https://github.com/cta-observatory/ctapipe/pull/683/files#diff-722d37cc1260e3557284e9056a2d9f3cR18

Solved by #1093


Charging Power not plausible for ZE50

Hello,
the values the system reports for the charging power is not plausible.
The ZE50 is able to charge with a maximum at 50KW when using DC and a maximum at 22KW when using AC.

The first 3 spikes are DC charging the last is AC charging.

Hi @rdu,
Please read this page: https://github.com/hacf-fr/renault-api/wiki/Data-endpoint:-battery-status.
The data comes directly from the Renault servers, and is known to be reliable on ZE40 (in Watts), but unreliable on ZE50 (seemingly in KiloWatts). As far as I am aware, no-one has managed to figure out a formula for converting the Renault Server values into reasonable values.
If you find a formula for getting valid values, then I encourage you to open a PR on https://github.com/hacf-fr/renault-api

Been following this value during charging (Have ZE50) this value seems not to be actual charging power but the "Max allowed charging power that the battery can take" .. Is this also true for ZE40? It seems to be correct for ZE50 in that aspect...

Been following this value during charging (Have ZE50) this value seems not to be actual charging power but the "Max allowed charging power that the battery can take" .. Is this also true for ZE40? It seems to be correct for ZE50 in that aspect...

That sounds plausible.
That would mean: if value > than "max station power" then value = "max station power", if value < "max station power" then value is valid.
Too bad we do not know the "max station power"

That sounds plausible.
That would mean: if value > than "max station power" then value = "max station power", if value < "max station power" then value is valid.
Too bad we do not know the "max station power"

@rdu If you have a charging station with an API that exposes these values you could theoretically make your own template sensor. This would only work when charging at home unfortunately. Just and idea.

@rdu If you have a charging station with an API that exposes these values you could theoretically make your own template sensor. This would only work when charging at home unfortunately. Just and idea.

I close the issue due to cause of the underlying library.

I close the issue due to cause of the underlying library.


[Question/Suggestion] Pre-compiled ab-av1.exe

I see that ab-av1 is built from source, and the executable ab-av1.exe is put under .cargo directory.
Just asking, if devs can offer a pre-built ab-av1.exe in your Release, cause building from source require installation of rustup and Visual Studio + cpp development, which costs ~8GB in installation size. RIP my mobile data, and storage.

It should be possible to add a windows compiled version via github actions ci on each tag.

ab-av1.exe builds will be available on new releases, e.g. https://github.com/alexheretic/ab-av1/releases/tag/v0.5.0


Updater: unclosed file object

file_object  in Updater._get_metadata_file() is left unclosed whenever an exception is raised (when the metadata fails a check of any kind). There are loads of examples in the test suite, e.g.
python3 test_updater.py TestUpdater.test_3__update_metadata

will complain "ResourceWarning: unclosed file"
This is not very dangerous but makes it hard to find actual issues in test output (try running all test_updater.py tests). There may be other sources of this warning but the vast number of warnings from this one make it difficult to find them.

Seems like a good place to use finally as a clean up handler.

Fixed in #1147


iOS No such module as "Flutter" error when trying to build with a Siri Intent extension target

Steps to Reproduce

Create Siri Intent extension target
Set target membership of Siri Intents extension target to include Runner
Set target membership of Runner to include Siri intents extension target
Attempt to build application observe the build error No such module as "Flutter" from AppDelegate.swift

I have set the configurations for the Siri Intents extension target to match debug and release respectively the same for runner but still get this issue.

PodFile
# Uncomment this line to define a global platform for your project
# platform :ios, '9.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!

  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
  pod 'SimplePing'
end

post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
  end
end

Error

Flutter Doctor
[✓] Flutter (Channel master, 1.25.0-5.0.pre.34, on macOS 11.2.1 20D74 darwin-x64, locale en-GB)
    • Flutter version 1.25.0-5.0.pre.34 at /Users/jack/Library/Google/flutter
    • Framework revision ff9d9fc2b6 (4 months ago), 2020-12-02 21:13:02 +0530
    • Engine revision 20caf54969
    • Dart version 2.12.0 (build 2.12.0-76.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/jack/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Users/jack/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7199119/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.4)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Users/jack/Library/Application Support/JetBrains/Toolbox/apps/AndroidStudio/ch-0/201.7199119/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] IntelliJ IDEA Ultimate Edition (version 2021.1)
    • IntelliJ at /Users/jack/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.55.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • macOS (desktop)  • macos      • darwin-x64     • macOS 11.2.1 20D74 darwin-x64
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 89.0.4389.114

• No issues found!

@Jack-Overflow
I am assuming this is for macOS desktop ? If so, I tried to add the Siri Intent extension target, but couldn't find it. Can you provide step by step details on how to add it ?

@Jack-Overflow
I am assuming this is for macOS desktop ? If so, I tried to add the Siri Intent extension target, but couldn't find it. Can you provide step by step details on how to add it ?

No this is for iOS, I can get the intent to build until I try and reference code within the original app Runner target and then I get those cannot find module errors.

Thanks for the details @Jack-Overflow.
I don't see the specific intent extension, unless I am missing something.

I am on Catalina with Xcode 12.3, not sure if that matters.
Also, I see that you are on old version of Master. Can you try to upgrade to latest and see if issue persists or not ?

The intents extension you have highlighted in that screenshot is the correct one. I will also try and upgrade Flutter and see if it helps the issue.

I've updated flutter to the latest version and I still end up with similar errors just for different modules now:

This seems like a bigger issue with the target membership settings between different XCode targets but I have no idea on how to resolve these errors.

@Jack-Overflow
I added the UI Intent Extensions target and then ran product -> Build which succeeded properly, unless I missed some steps to properly replicate it. If so, can you elaborate on them ?

@Jack-Overflow
I added the UI Intent Extensions target and then ran product -> Build which succeeded properly, unless I missed some steps to properly replicate it. If so, can you elaborate on them ?

You have to set the target membership of the intent handler to both Runner and the extension target and set the target membership of the app delegate to Runner and the extension target. The the errors occur.

I see. Thanks for the details.
I see the same behavior and was able to replicate the issue.

flutter doctor -v
[✓] Flutter (Channel master, 2.2.0-11.0.pre.274, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 2.2.0-11.0.pre.274 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d1f73a1065 (2 days ago), 2021-04-24 00:44:02 -0400
    • Engine revision eba9efd1c3
    • Dart version 2.14.0 (build 2.14.0-37.0.dev)

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • Mac OS X 10.15.4 19E2269
      darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 90.0.4430.85

! Doctor found issues in 1 category.

@jmagman for priority

set the target membership of the app delegate to Runner and the extension target. The the errors occur.

You added the AppDelegate.swift to the extension target (you want your Siri extension to use Flutter and register all its plugins?) which is importing Flutter:
import UIKit
import Flutter

But you didn't set up the extension target to add the Flutter framework and its targets to its search paths.  The extension is a dependency of the app, so it builds first, but doesn't also doesn't have any of the scripts set up to compile your dart code or move the Flutter framework to the right place.
So did you intend for your Siri extension to use Flutter?  If so, there's more set up to add the right script build phases, but if not, then you should not build the AppDelegate into both targets...

This may be a duplicate of https://github.com/flutter/flutter/issues/16092 if you want to use Flutter in your extension.

The problem I've got is I want to use code and classes that are within the main app target in the Siri extension so I set the target membership so I can access it but then I have to also set the same target membership for the AppDeletgate as this file is also dependent on this class. Is there a way to set it so my extension isn't dependant on Flutter but is dependant on the other classes within the main app?

@Jack-Overflow Usually the pattern is to move common code into a framework to be imported by both target executables.

Thanks for the information. I've only just started writing Swift really so the whole native iOS platform I'm still trying to get my head around it. I made a Common framework and it builds and I have shortcuts working. No issue with Flutter. Thanks 👍.


Helm agent secrets (new)

moved from #388, using new branch "feature/helm-agent-secrets".
Move acapy seed to k8s secret (Created and annotated to be kept on uninstall)
add release.name to ingress path for easier multiple deployments.
improving that to generate with suffix, or overridden with full yaml block

@Jsyro , I had to move the branch again. Yours was write-protected (Maybe only branches prefixed with "feature/" are not write protected, I have in mind...)

@Jsyro  , I did not find time to test some scenarios ( with different values).
Feel free to merge the PR if it fits to your needs or add comments which I can fix tomorrow .
P.S. Somehow the time difference from Canada and Germany is cool - we can work on the features one after the other :-)

there is one thing to be fixed ( couldn't finish it because of the problems with the branch and now I have to leave)
This is missing in both ingress definitions ( acapy and bpa) in the second part
            backend:
              serviceName: {{ $fullName }}
              servicePort: {{ $svcPort }}

duplicate of #391


[Feature request] Maintain aspect ratio of pre rendered cutscenes and videos on ultrawide and beyond

Describe the feature you'd like to see added
As the title suggests, there should be an option to disable the stretching of pre rendered cutscenes and other videos in ultrawide and wider resolutions. I think the game already letterbox the videos on 16:10 and 4:3 aspect ratios, so it looks fine there.
On the other hand, that is not the case with 21:9, 48:9 [or basically anything wider than 16:9] resolutions. Having proper pillarboxed videos in this case would be nice.
However, I emphasize the word "option" because stretching can still be of use. If someone manages to somehow make ultrawide prerendered cutscenes and videos, then this current stretching of the videos will be required. Thus, having option to disable the stretch and maintain aspect ratio should be optional.

Added the option as part of a complete rework I'm doing on Ultrawide support:

Stretching video is now disabled by default, which is the better option IMO.
The "background" color is being set by the game, btw, which is why it isn't black. Doesn't seem like a big deal to me, but if I stumble across what is changing it, I'll change it to black.

Well I noticed there seems to an issue with this feature when I started playing Separate Ways. Something may have been broken recently, pre-rendered videos are still a bit stretched here. At least they don't have such wide black bars as the above example.
Here's how it looks at 2560x1080 with UltraWideAspectSupport enabled and WITHOUT enabling StretchVideos:

And here's how it looks at 1920x1080:

Hmm, that's with the HD project, correct? I'm thinking Albert may have changed the video's aspect ratio. I tested this feature with the vanilla game and it seemed to work correctly.
I don't have a copy of the HD project at the moment, so this may have to wait a bit.

Yep, I'm running the HD mod, sorry. Should have clarified.
Take your time, this isn't anything close to game-breaking, really. :)

And, actually, you may be right. Taking a look at some unused video files, vanilla seems to use a (very low) resolution of 512x336 and a weird pixel aspect ratio of 39:28 (which renders it at 468x336).
Albert remastered his videos to 1920x1080 with a 1:1 aspect ratio.


[ENGDOCS-894] Remove out-dated samples

Proposed changes

Removed samples for Docker Labs repo because the repo is no longer actively maintained.
Removed loosely connected "Library references" section.
Fixed typo in description frontmatter
Updated TOC

Related issues (optional)
ENGDOCS-894

Wondering if it's also worth adding a link to https://github.com/dockersamples?q=&type=all&language=&sort=stargazers?


Improve docs site to have the same look and feel of the primary weave.works website

Problem
Currently, our docs and weave.works sites do not have the same look and feel.  We want to have a seamless user experience, where the user starts on the main site and then can dive 'deeper' into our docs, without noticing.
Solution
Through css or other methods provided by Docusaurus the same look and feel of the company main website.   Current css is located here, https://github.com/weaveworks/weave-gitops/blob/main/website/src/css/custom.css
Bonus would be to add link back to the weave.works main site in the nav bar, and so that customers can work back towards the main site if needed.

Which docs page is our main
this
https://www.weave.works/docs/
or this
https://docs.gitops.weave.works/
and what's the difference

It should be the first link, to the docs site.    The second link should be removed once the company website (that covers the marketing of the product) is ready.
Martin Stadler
SVP Customer Experience
www.weave.works

On 04/09/2023 at 08:33, Ahmed Faris  @.***>  wrote:
Which docs page is our main
this
https://www.weave.works/docs/
or this
https://docs.gitops.weave.works/
and what's the difference
—
Reply to this email directly,   view it on GitHub, or   unsubscribe.
You are receiving this because you authored the thread.Message ID:  @.***>

Hello,
@mestadler @MostafaMegahid @LappleApple
I've made our first iterations for enhancing and matching the docs with our website
you could see the 3 options on the screenshots below

also you could see the full design on Figma through the following link
https://www.figma.com/file/IVHnM9iyeFWpd11evtY8ux/Weave-GitOps?type=design&node-id=19485-1454&mode=design&t=yKYxQZWSStaMTJfZ-4
Let me know your feedback

Overall looking good, thank you @alfaris. A few super-quick things:

I get that GitOps Run is a "main feature" in that it's available across WGE/OSS, but it's not a main draw of WeGO overall.
What's up with the wintry striped scarf? :)

I used the same content on the landing page right now (https://docs.gitops.weave.works/) but we can improve it and change whatever will add value to the user browsing this page
The wintry striped scarf - I thought of something that will give personality to Weave as Example GitHub uses a character in the space or space items but also we can iterate on it to come up with better fictional representation

I like the format of the last one the most, really nicely done.
Professional, polished, worth the $200k to $750k annual subscription our
customers pay for our product.
I like the isometric icons, we should collect these.  Assuming MJ?
Note to Lauri, I think that's the Weave flying carpet 😊
On Thu, 7 Sept 2023, 12:15 pm Ahmed Faris, @.***> wrote:

I used the same content on the landing page right now (
https://docs.gitops.weave.works/) but we can improve it and change
whatever will add value to the user browsing this page
The wintry striped scarf - I thought of something that will give
personality to Weave as Example GitHub uses a character in the space or
space items but also we can iterate on it to come up with better fictional
representation

—
Reply to this email directly, view it on GitHub
https://github.com/weaveworks/weave-gitops/issues/3910#issuecomment-1709967840,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBDNHMYHZ5FYZOT6BAOOUDXZGUG3ANCNFSM6AAAAAA3CUPICY
.
You are receiving this because you were mentioned.Message ID:
@.***>

💡 Extra note for FE Engineers
the used font in Docs are "system-ui, -apple-system, "Segoe UI"
but in our website are "proxima-nova, sans-serif, "Helvetica Neue", Helvetica, Arial, sans-serif"


[NCL-8340] Update Node to v20.10.0 and NPM to v10.2.5

package-lock.json was deleted and re-generated by npm i.

Hi @DnsZhou can you please review this one? (the same changes were applied on other projects too)


v2 - member portal - no email sent to contributor when added/removed from Approved list

When a user is added or removed from an approved list, the user should receive an email notification.
User added and removed by email<EMAIL_ADDRESS>The user has no LF Account.
No email sent to the user as evidenced by the logs:

Pranab had tried with github user name and the contributor received an email.
Pranab to try with github email & Heather to try with email address.


Version of tensorflow

May I ask you which version is your tensorflow?

This was using TF 1.3, if I remember correctly

I ran the command:python run_mnist.py --combine_train_val True
and I got the error:
Traceback (most recent call last):
File "run_mnist.py", line 234, in
main(parser.parse_args())
File "run_mnist.py", line 136, in main
pred = deep_mnist(args, x, train_phase)
File "/home/v_zhizuo_zhang/projects/Harmonic_network/harmonicConvolutions/MNIST-rot/mnist_model.py", line 39, in deep_mnist
cv2 = hn_lite.batch_norm(cv2, train_phase, name='bn1')
File "../harmonic_network_lite.py", line 46, in batch_norm
return h_batch_norm(x, fnc, train_phase, decay=decay, eps=eps, name=name)
File "../harmonic_network_ops.py", line 149, in h_batch_norm
Rb = bn(magnitude, train_phase, decay=decay, name=name)
File "../harmonic_network_ops.py", line 176, in bn
batch_mean, batch_var = tf.nn.moments(X, np.arange(len(Xsh)-3), name=name+'moments')
File "/home/v_zhizuo_zhang/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/nn_impl.py", line 650, in moments
mean = array_ops.squeeze(mean, axes)
File "/home/v_zhizuo_zhang/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/array_ops.py", line 2281, in squeeze
return gen_array_ops._squeeze(input, axis, name)
File "/home/v_zhizuo_zhang/anaconda2/lib/python2.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 3329, in _squeeze
squeeze_dims=squeeze_dims, name=name)
File "/home/v_zhizuo_zhang/anaconda2/lib/python2.7/site-packages/tensorflow/python/framework/op_def_library.py", line 655, in apply_op
raise TypeError("Expected list for attr " + key)
TypeError: Expected list for attr squeeze_dims


Preview in Azure Sentinel links

The links for Azure Sentinel on this page https://docs.microsoft.com/en-us/azure/security/ still show preview in them.

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

@kilasuit
Since you created a PR to update the documentation and it's currently waiting for the author to review, I'll go ahead and close out this thread.
Adding @TerryLanfear for visibility on this.

No problem thought the PR is set up so it would have Auto closed this when merged anyway :-)


Use the appium:deviceName capability to find the specific browser

Use the appium:deviceName capability to find the specific browser as well. New Appium clients do not send the non-W3C deviceName capability.

@BorisOsipov thank you for contribution!


Add Service Notification on recent Android versions

After changing to services (https://github.com/sebsto/maxi-80-android-exoplayer2/issues/3), the app should now use Notification to inform customer about running service in background
https://www.youtube.com/watch?v=FbpD5RZtbCc
https://stackoverflow.com/questions/44658923/android-foreground-service-notification-not-showing

added in https://github.com/sebsto/maxi-80-android-exoplayer2/commit/5f82f38cd6c0c325dbc26c9b146ce1d6998ecf32


Comment history is loading slowly + has an offByOne error

Gitea Version
1.16.0+dev-519-g3be156f66
Operating System
Linux
Browser Version
Firefox 94.0
Can you reproduce the bug on the Gitea demo site?
Yes
Description
Gitea now supports the comment history.
However, loading the history seems to be way too slow:
For normal comments, the history will automatically be loaded once the page is reloaded.
Fine so far. Still with a hefty delay (~3 seconds, so you definitely notice when the history suddenly appears), but it loads.
The issue bodies (the description of the issue) are way worse:
According to my tests on try.gitea.io, there seems to be an index error for those, as they only load once a second edit has been made. Once the second edit has been made, it behaves like a normal comment.
So, two things should be done:

the offByOne error should be fixed.
the history should be loaded faster, at best to the point that it is unnoticeable that it has been loaded afterwards.

Screenshots

This is an issue description where one edit has been made and the page has been force-reloaded. As you see, the history is not getting displayed.

I think the offByOne happens when editing old issues/comments (created before there was support for edit history).

I think the offByOne happens when editing old issues/comments (created before there was support for edit history).

👍 Yep, the history menu won't be shown if there is only one history revision (that's by design).
For old comments, there was no history revision before, so the first editing would save the first history revision, and the menu would only be shown for the second editing.

And I haven't noticed any performance problem on my Gitea instance. The menu is always shown within 1 second.
If you believe there is a performance problem, please make sure your network is fast enough and help to find which function/sql causes the laggy.

To support edit history for existing comments: maybe the issue_content_history can be initialized with the initial (is_first_created) content when editing a comment that does not have such an entry yet?

To support edit history for existing comments: maybe the issue_content_history can be initialized with the initial (is_first_created) content when editing a comment that does not have such an entry yet?

Agree, it would work.

Or the issue_content_history could only be populated with the previous value when actually making an edit?
Because with the current implementation all issue contents and comments are unnecessarily saved twice in the database.

Or the issue_content_history could only be populated with the previous value when actually making an edit? Because with the current implementation all issue contents and comments are unnecessarily saved twice in the database.

I have thought about it, but it would make the algorithm more complex (eg: list/diff), usually I prefer a simple and clear solution. And issue contents are much smaller than git repositories, saving the contents won't cost too much in modern days.

I think this issue can be closed by #17746
The "performance" problem may not be related. If there is really a performance problem, we need more details (and a separate issue)


Add a new messaging-clustered module (#111)

This is a first pass at getting basic messaging clustering
working. Right now lots of things are hardcoded, including the cluster
password, so it's not yet suitable for production usage. Once we get
the config-api working with messaging then all these values can be
configured.
To enable clustering, just use wildfly-swarm-messaging-clustered as
a dependency instead of wildfly-swarm-messaging.
As part of this change, I've added a priority with a default value of
0 to ServerConfiguration. This priority is used when more than one
ServerConfiguration implementation have the same Fraction type T. The
ServerConfiguration with the higher priority is the only one that gets
used.

Closing this pull request to re-evaluate the implementation.


make it possible not to start xvfb in Splash-Jupyter Docker image

Fixed by https://github.com/scrapinghub/splash/pull/378


Use this issue to update the list of Contributors

@all-contributors please add @naru200 for maintenance

@all-contributors please add @eunsukimme for maintenance

@all-contributors please add @14km for code

@all-contributors please add @suyeon96 for code

@all-contributors please add @roeniss for code

@all-contributors please add @sudosubin for code

@all-contributors please add @mokhs00  for code


Gelu operator is not supported

More details in: https://github.com/ROCm/AMDMIGraphX/issues/2758
Gelu spec: https://onnx.ai/onnx/operators/onnx__Gelu.html or https://github.com/onnx/onnx/blob/main/docs/Operators.md#Gelu

https://github.com/ROCm/AMDMIGraphX/pull/2801


Autocomplete track by problem

My solution is to change track function of autocomplete directive to:
scope.track = function(item) {
if(attrs.trackProperty) {
return item[attrs.trackProperty];
} else {
return getItem(item);
}
};
that way you can have different property for display and track.
usage: track-property="_id"

Sorry for not replying sooner.
This has been requested before. It's in the project backlog already. :)

Can this issue be closed?

Closing due to inactivity.

Was there ever a solution to this problem, or was it just closed due to inactivity.
I am seeing this error.


Running the examples/application

Hi @smicyk,
What would I be expecting when running the examples/application?
I would be expecting some jmeter (or any test script) execution logs showing up, but I've been waiting for over 10 minutes, but didn't see anything, except that, after it is up for a while, I got:
testserver-app  | WARNING: An illegal reflective access operation has occurred
testserver-app  | WARNING: Illegal reflective access by org.codehaus.groovy.vmplugin.v9.Java9 (file:/opt/groovy/lib/groovy-3.0.7.jar) to method sun.nio.fs.UnixFileSystem.getPath(java.lang.String,java.lang.String[])
testserver-app  | WARNING: Please consider reporting this to the maintainers of org.codehaus.groovy.vmplugin.v9.Java9
testserver-app  | WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
testserver-app  | WARNING: All illegal access operations will be denied in a future release
testserver-app  | Caught: java.nio.file.AccessDeniedException: jmeter.properties
testserver-app  | java.nio.file.AccessDeniedException: jmeter.properties
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
testserver-app  |       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase$_updateJMeterPropertiesLocation_closure7.doCall(TestScriptBase.groovy:123)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
testserver-app  |       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase.updateJMeterPropertiesLocation(TestScriptBase.groovy:122)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
testserver-app  |       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase.start(TestScriptBase.groovy:44)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase$start$0.callCurrent(Unknown Source)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase.start(TestScriptBase.groovy:40)
testserver-app  |       at net.simonix.dsl.jmeter.TestScriptBase$start.callCurrent(Unknown Source)
testserver-app  |       at script.executeScript(script.groovy:6)
testserver-app  |       at net.simonix.dsl.jmeter.TestScript.run(TestScript.groovy:133)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
testserver-app  |       at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
testserver-app  |       at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
testserver-app exited with code 1

Will there be test script execution logs normally? Or the problem is caused entirely by the testserver-app exited? thx

Scrap that, for the moment -- might be my own issue.

might be my own issue

Nope, tried on two of my machines and both are the same.
Find the culprit as well -- While the whole thing is up, I got:
$ curl -L localhost:1080/
curl: (7) Failed to connect to localhost port 1080: Connection refused

In my browswer it shows "This site can’t be reached".
Please advice. thx!

mockserver problem resolved. I think the remaining problems are related with #52

So it this still an issue for you?

I'll be coming to it eventually, currently trying to make the first example working at my side now...
will report back.

I'm having problem getting the whole thing working, but that's only problem on my side.
As long as my #53 is working, I'm fine as I now have a working environment to test the sample code. That's really what I was after when trying this, to have a working environment. So I'm closing it now.


Plugin ignores versions declared with "strictly"

VersionCatalogParser doesn't handle strict versions. For example
kotlin = { strictly = "1.7.21" }

However com.github.ben-manes.versions takes such versions into account and writes them to output.

Can you elaborate and provide a sample project?
For versions like this I think there should be a message logged, but no upgrades will be performed, since you've specified that you want to use this exact version.
So if you don't see that message, this might be a bug.

OK I checked and the warning that is in place for libraries is not implemented for plugins (because it's slightly more complicated 😅 ) so I assume that is what this issue is about.


Feature/toggle api proxy url

Closes #1381
Changes

Pass ProxyBackend settings to API Details page
construct API Base URL from ProxyBackend, when available
show API URL when Proxy Backend is not available
Add missing i18n texts
disable Base URL field when data not available

TODO: update API Umbrella sync function to always set API URL field

Reviewing

Good work.


Try for or force Django's native JSONField

django-jsonfield conflicts with Django's native JSONField, and instead of converting the codebase I'd like actstream to use it if possible.
Should we maybe create a JSONFIELD_IMPLEMENTATION setting to force which JSONField the module will use, since we cannot check for sure if the user is running its database(s) on PostgreSQL? And defaults to django-jsonfield's implementation.
# settings.py

from django.contrib.postgres.fields import JSONField

ACTSTREAM_SETTINGS = {
    # ...
    'JSONFIELD_IMPLEMENTATION': JSONField
    # ...
}

My bad, seems already implemented but the doc is not updated is that right?

... and that's because it's a django-jsonfield-compat setting. Question, answer :)


Cannot install it

I cannot install it as a plugin to Logitech options. Following your guidelines it makes the logioptions crash. Please add more details to the installation guide as this project is very futureproof!

Can you give more details on the crash? What OS are you using?
FYI, soon you will hopefully not have to follow all the manual build and install steps in the dev guide, as I'd like to publish the extensions more officially.

@nntantidakis Please take another look at the README now - the extension is officially published

Hello. Im really sorry i havent replied to your previous comment, but i thought that i had replied.
I will try again and will inform you about it. Thanks a lot

Works fine now, and its extremely useful! Thanks a lot! Just edit your plugin on vscode and remove the default action for crown release, its very confusing when you touch the crown and you see that it jumps 2 tabs in the beginning.

 So, crown touch/release is exactly what it sounds like: when you simply touch the crown it triggers. It's not when you push the crown (it seems like there is no event sent over the socket when pressed, unfortunately, although maybe it's possible to get it with a change in the tool config JSON for the Options plugin).
If you want to determine the difference between touching the crown just to trigger an action vs touching it to perform a rotation, we would have to modify the plugin slightly.
What about a "longTouch" event? This event would fire if you touch and hold the crown for 1 second (and thus if you quickly release or turn the crown then it won't trigger the longTouch event).
Here is a PR for you to review: https://github.com/idolize/logitech-craft-plugin/pull/1

Maybe both of them will serve everyone nicely. If it's easy make the mod as customizable you want in order to serve more people. Personally, the longTouch event will not help me if i set it to be formatDocument. But i am not asking this modification for me only because i have already solved the problem by mapping another button and disabling the touch-release, im just mentioning some options in order to make it more usable.

Thanks for the feedback - I'll add both options to the plugin once I get a chance to test it and make sure it works.


[v1.2] Documentation update

Pull Request Test Coverage Report for Build 82

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 92.175%

Totals

Change from base Build 72:
0.0%

Covered Lines:
1602

Relevant Lines:
1738

💛  - Coveralls

Please fix these errors:

In DeveloperGuide.adoc: Re-format kbd:[Enter] in section 4.2. Multiple lines input support.
In DeveloperGuide.adoc: Re-number Appendix D: Use Cases (Use case: Add a video to recipe should be numbered with D.1 and so on).


update choco package openjdk11 to microsoft-openjdk11

according to the choco openjdk11 is deprecated
which leads to the problem of unrecognizing android-studio with react-native

solution
https://github.com/facebook/react-native-website/blame/main/docs/_getting-started-windows-android.md#L20
- choco install openjdk11
+ choco install microsoft-openjdk11

see choco packges for openjdk11

according to the choco openjdk11 is deprecated

I'd love to have someone from Microsoft cross-check this before we land it.

@cortinico, I have been using Microsoft builds of OpenJDK 11 for RN android builds for a while now, but I use winget instead of choco.
winget install Microsoft.OpenJDK.11
Choco distribution of Microsoft.openjdk11 looks good and trusted too .. If @khali70 has already tried and works well, I'd back this PR.

Great! @khali70 don't you mind sending a PR over to update the website?


how can i unload wavesure  as quickly as possible ?

Hi,
how can i unload wavesure  as quickly as possible ?    i use google,  i want to free memory , i have only 2G memory,  cloud you help me ?
@berio  @rikrd  @tf

@thijstriemstra

hey @15838028035 can you stop cc-ing random people, fck that, we're not some sort of helpdesk.

Okay, I do not know who can help me
发自我的 iPhone

在 2019年1月2日，20:12，Thijs Triemstra<EMAIL_ADDRESS>写道：
hey @15838028035 can you stop cc-ing random people, fck that, we're not some sort of helpdesk.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@15838028035 use wavesurfer.destroy().


Downloading from easyEDA unreliable

Sometimes JLC2KiCad_lib works great for me sometimes, however often it hangs after displaying a line like:
2022-10-09 09:57:00,231 - INFO - creating library for component C2325
It looks like it is this line of code that is responsible:
https://github.com/TousstNicolas/JLC2KiCad_lib/blob/730473a6b0b2fa6d19cbaa105857d608ba1b85b6/JLC2KiCadLib/JLC2KiCadLib.py#L14
It tries to download a url like "https://easyeda.com/api/products/C23255/svgs"

If I try using the request library in a python REPL to fetch this url it hangs.
If I try using wget to fetch the url it hangs.
If I try use my browser (firefox on mac) it works fine!

Does JLCPCB not like this script, are they trying to block it?

ARRRGH!, actually it was my work VPN causing problems!


fix: add support for reading Bigtable key value of zero

Although it's possible to write a row key of value "0" to Bigtable, the PHP Bigtable client currently doesn't support reading such rows. The reason is because there is currently a validation check that uses the ! operator, and the boolean value of "0" in PHP happens to be false.
This change would instead use a strict value check for an empty row key string.

Hi @wsung-asong, thanks for the pull request! The change looks great, but we will need to add a unit test for it! Would you be able to take a look, or do you need help with that?

Hi @wsung-asong, thanks for the pull request! The change looks great, but we will need to add a unit test for it! Would you be able to take a look, or do you need help with that?

friendly ping @wsung-asong. Are you able to add a unit test to this?

friendly ping @wsung-asong. Are you able to add a unit test to this?

ah sorry missed your first message! yes i can add a unit test for this!

@jdpedrie let me know how the unit test looks! Mainly just copied a similar test

Looks great! Thanks @wsung-asong!


#15: move to main page after save/update Quiz

move to main page after save

Redirect to the main page after saving, or add a button to go there. Which one is better??


Add new volunteer ibukunoluwanap

Updated as requested

Thanks for volunteering @ibukunoluwanap :)
Added some comments

thanks. check https://github.com/codewithvoid/AskDevs/pull/57/


CUPS doesn't return toner level for printer Brother-MFC-7860DN when it's empty during printing

when a print job was sent to a network printer with an empty toner, the "marker-level" turned out not to be 0, and attribute "printer-state-rason" of subscription was "none"...
os: ubuntu
cups version:1.7.2

What is the device URI for the printer? (lpstat -v will show you)
What driver are you using?

The device-uri is "dnssd://Brother%20MFC-7860DN._pdl-datastream._tcp.local/".
I use a PPD file for driver for the printer.
<EMAIL_ADDRESS>From: Michael R Sweet
Date: 2016-04-09 02:06
To: apple/cups
CC: yyikaka
Subject: Re: [apple/cups] CUPS doesn't return toner level for printer Brother-MFC-7860DN when it's empty during printing (#4802)
What is the device URI for the printer? (lpstat -v will show you)
What driver are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

OK, for this type of connection we depend on either the driver reporting supply levels or the printer supporting SNMP. It sounds like neither of these things are the case...