The TypeScript language service died unexpectedly 5 times in the last 5 Minutes.

Issue Type: Bug
Potential duplicate of #20446. I could have created the issue under TypeScript project, but the "Report on Github" button lead me here, and TypeScript service did not show as an option in the bug report form. Feel free to contact me about more information on my settings.
This happens all the time regardless of what I am doing. Crash notification keeps showing up over and over again.
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:57:51.166Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
6, 5, 4

Memory (System)
8.00GB (0.50GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

vscode-eslint
dba
2.0.11

gitlens
eam
10.2.0

mssql
ms-
1.8.0

vsliveshare
ms-
1.0.1404

trailing-spaces
sha
0.3.1

js-jsx-snippets
sky
10.0.0

JavaScriptSnippets
xab
1.7.2

ReactSnippets
xab
2.4.0

I just found more details on that... I went to *Help > Toggle Developer Tools"  and noticed that every few seconds this error message goes to error console:
Error: <semantic> TypeScript Server Error (3.7.3)
Debug Failure. False expression.
Error: Debug Failure. False expression.
    at declareSymbol (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29212)
    at declareSymbolAndAddToSymbolTable (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30497)
    at bindThisPropertyAssignment (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:31369)
    at bindWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:31020)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30902)
    at bindExpressionStatement (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30106)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29568)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30913)
    at /Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29495
    at bindEach (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29511)
    at bindEachFunctionsFirst (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29495)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29611)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30913)
    at visitNode (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17622)
    at Object.forEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17752)
    at bindEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29519)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29614)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bindContainer (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29435)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30916)
    at visitNode (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17622)
    at Object.forEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17709)
    at bindEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29519)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29614)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30913)
    at bindEach (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29511)
    at visitNodes (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17627)
    at Object.forEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17801)
    at bindEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29519)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29614)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bindContainer (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29470)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30916)
    at visitNode (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17622)
    at Object.forEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:17996)
    at bindEachChild (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29519)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29614)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30913)
    at /Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29495
    at bindEach (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29511)
    at bindEachFunctionsFirst (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29495)
    at bindChildrenWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29605)
    at bindChildren (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29489)
    at bindContainer (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29435)
    at bind (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:30916)
    at bindSourceFile (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29068)
    at Object.bindSourceFile (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:29005)
    at initializeTypeChecker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:64384)
    at Object.createTypeChecker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:33622)
    at Object.getTypeChecker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:95612)
    at synchronizeHostData (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:130645)
    at Object.getProgram (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:130727)
    at ConfiguredProject.Project.updateGraphWorker (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:135078)
    at ConfiguredProject.Project.updateGraph (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:135021)
    at ConfiguredProject.updateGraph (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:135869)
    at ProjectService.createLoadAndUpdateConfiguredProject (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:137362)
    at ProjectService.assignProjectToOpenedScriptInfo (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:138186)
    at /Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:138417
    at Object.mapDefined (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:565)
    at ProjectService.applyChangesInOpenFiles (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:138417)
    at Session.handlers.ts.createMapFromTemplate._a.<computed> (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:139271)
    at /Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:140929
    at IOSession.Session.executeWithRequestId (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:140920)
    at IOSession.Session.executeCommand (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:140929)
    at IOSession.Session.onMessage (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:140952)
    at Interface.<anonymous> (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/tsserver.js:142267)
    at Interface.emit (events.js:200)
    at Interface._onLine (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/readline.js:314)
    at Interface._normalWrite (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/readline.js:459)
    at Socket.ondata (/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/workbench/readline.js:170)
    at Socket.emit (events.js:200)
    at addChunk (_stream_readable.js:294)
    at readableAddChunk (_stream_readable.js:275)
    at Socket.Readable.push (_stream_readable.js:210)
    at Pipe.onStreamRead (internal/stream_base_commons.js:166)
	at Function.create (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1)
	at h.dispatchResponse (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1)
	at h.dispatchMessage (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1)
	at /Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1
	at l.fire (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:46)
	at t.Reader.onLengthData (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1)
	at Socket.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/app/extensions/typescript-language-features/dist/extension.js:1)
	at Socket.emit (events.js:200)
	at addChunk (_stream_readable.js:294)
	at readableAddChunk (_stream_readable.js:275)
	at Socket.Readable.push (_stream_readable.js:210)
	at Pipe.onStreamRead (internal/stream_base_commons.js:166)

Also tried with no extensions running. Same issue.
Issue Type: Bug
Updated
VS Code version: Code 1.41.1 (26076a4de974ead31f97692a0d32f90d735645c0, 2019-12-18T14:57:51.166Z)
OS version: Darwin x64 19.2.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz (4 x 2300)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_offsurface_control: disabled_offsurface_synchronization: enabled_onvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
7, 6, 5

Memory (System)
8.00GB (0.13GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions: none

Please try upgrading your workspace to use typescript@next by installing this extension. Does that fix the issue?

Yea! That solved the problem!

Closing as fixed in TS 3.8. We will be picking that version of TS up for the February release of VS Code. Until then, use the extension


Update autofill to latest version

Automated autofill dependency update

This PR updates the autofill dependency to the latest available version.
You have to manually create a task for this PR before merging it.
This PR only updates to the latest version and installs it, no code changes in the client are done in this PR.

test


Coordinate based county determination?

Could state county be identified through public geodata and coordinates of the camera?

OpenStreetMap provides a free API, but the rate limit is 1 request per second:
https://operations.osmfoundation.org/policies/nominatim/
Example:
https://nominatim.openstreetmap.org/reverse?format=json&lat=37.027055&lon=-88.61358&zoom=18&addressdetails=1
It would take about half a day to get the details 30k+ camera locations.

Yeaa, that's not ideal.  It should be possible to download the county shapes and compute it locally


docs: Update location of async_query_manager.py

SUMMARY

This PR updates the documentation for the location of the async_query_manager.py which was moved in PR #25346.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thanks for fixing this!


⚠ Bofrost.com has degraded performance

In ec1f5ad, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 2008 ms

Resolved: Bofrost.com performance has improved in 5e8e857.


Create ur.json

Maintainer of archived urdu translation repo

@Touseef-ahmad any progress ? did you update the PR?

I'm going to close for now, but please feel free to reopen if you find at least one other person who'd like to maintain the translation. Thanks!


Update from v3.19.3 to v3.19.6 didn't work

Version of the custom_component
v3.19.3 to v3.19.6
Describe the bug
I try to update from v3.19.3 to v3.19.6 but HA didn't want to finish the update.
Is just stay there and try to update.
I don't know where to see a LOG of the errors.
Debug log
In the Log Viewer I don't see anything about HACS or Tesla plugin
Thanks in advance

3.19.6 is a beta release. Choose a non beta.

And how can i choose please ?
I have only one UPDATE button
Thanks again

Disable beta versions in options.

Whoauuu greate :-)
Now it's work.
Thanks a lot


tensorflow-lite as shared(dynamic) lib for C/C++ & linux/ubuntu

Hello
is there a way to build shared (dynamic) lib for TensorFlow-lite? If so, please share the steps to do so and possibly some simple example with it.
Thank you.

You can build a shared library with the following command.
bazel build -c opt //tensorflow/lite:tensorflowlite

This will output the resulting shared library (.dll, .so, or .dylib), which you could dynamically link into your own project. You could also provide the tensorflow repository root as an include path so that you could include the tensorflow/lite/... headers.

I need that lib for ARM64 target.

Can you try adding --config=elinux_aarch64 flag to the build command above?
bazel build -c opt --config=elinux_aarch64 //tensorflow/lite:tensorflowlite

Tried this on a Linux machine and it seems to work for me.
$ file bazel-bin/tensorflow/lite/libtensorflowlite.so
bazel-bin/tensorflow/lite/libtensorflowlite.so: ELF 64-bit LSB shared object, ARM aarch64, version 1 (GNU/Linux), dynamically linked, BuildID[md5/uuid]=d9af18419c9973a6b552eba0d4f44721, stripped

cc/ @terryheo

OK. I'll try it but why --config=elinux_aarch64?
I did before --cpu=arm64, --cpu=aarch64 or --cpu=arm64-v8a ..

seem unsuccessful
/tensorflow$ bazel build -c opt --config=elinux_aarch64 //tensorflow/lite:tensorflowlite
Starting local Bazel server and connecting to it...
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=192
INFO: Reading rc options for 'build' from /media/nxa18908/work/work/tensorflow/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /media/nxa18908/work/work/tensorflow/.bazelrc:
  'build' options: --apple_platform_type=macos --define framework_shared_object=true --define open_source_build=true --java_toolchain=//third_party/toolchains/java:tf_java_toolchain --host_java_toolchain=//third_party/toolchains/java:tf_java_toolchain --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --noincompatible_prohibit_aapt1 --enable_platform_specific_config --config=v2
INFO: Found applicable config definition build:v2 in file /work/tensorflow/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
ERROR: Config value elinux_aarch64 is not defined in any .rc file
(base) /work/tensorflow$

The build config is defined here, and it was added recently.
https://github.com/tensorflow/tensorflow/blob/master/.bazelrc#L76-L79
Which version of tensorflow repository are you using?

I use ver.2.2

I've switched to the latest (master) - now it seems building now - where is toolchain taken from (defined).
It looks it uses arm-gcc-8.3 and how could I change to the latest GCC 9.3.1?

Please refer to this commit 4961f18733ca3967198393abf419e14476b4a85c to see more details on how the toolchain was configured.
I think you'll need to update the toolchain archive url under tensorflow/workspace.bzl.

Thanks a lot for great help!

Since I am not bazel expert :( it seems defined here within tensorflow/workspace.bzl
    tf_http_archive(
        name = "aarch64_linux_toolchain",
        build_file = clean_dep("//third_party/toolchains/embedded/arm-linux:aarch64-linux-toolchain.BUILD"),
        sha256 = "8ce3e7688a47d8cd2d8e8323f147104ae1c8139520eca50ccf8a7fa933002731",
        strip_prefix = "gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu",
        urls = [
            "https://storage.googleapis.com/mirror.tensorflow.org/developer.arm.com/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz",
            "https://developer.arm.com/-/media/Files/downloads/gnu-a/8.3-2019.03/binrel/gcc-arm-8.3-2019.03-x86_64-aarch64-linux-gnu.tar.xz",
        ],
    )

Can be applied this similarly for label_image example project label_image?

Do you have a reason to use a specific version of GCC? I'd suggest sticking to the provided GCC version.

For fixing the label_image build, you could try editing the tensorflow/lite/examples/label_image/BUILD file.

diff --git a/tensorflow/lite/examples/label_image/BUILD b/tensorflow/lite/examples/label_image/BUILD
index 92bb503e6d..3f4d10cc57 100644
--- a/tensorflow/lite/examples/label_image/BUILD
+++ b/tensorflow/lite/examples/label_image/BUILD
@@ -38,6 +38,8 @@ cc_binary(
         "//tensorflow/lite/profiling:profiler",
         "//tensorflow/lite/tools/evaluation:utils",
         "@com_google_absl//absl/memory",
+        "@com_google_absl//absl/base",
+        "@com_google_absl//absl/strings",
     ] + select({
         "//tensorflow:android": [
             "//tensorflow/lite/delegates/gpu:delegate",

nope - I'd like to know where to change it :)
need to exercise built lib with tflite (static, dynamic)

Sure. Could this issue be considered resolved then? Or are you still blocked on something?


Check code style of all PHP files

Q
A

Type
improvement

BC Break
no

Summary
Check code style of all PHP files

Thanks!

You're welcome.


Revisit a way to automate and/or verify the rpc docs

What problem does your feature solve?
We might forget to update the docs to match as we change soroban-rpc.
What would you like to see?
Automatic generation or at least verification that the docs match the API as expected. This is an "eventually" wishlist item following on from https://github.com/stellar/soroban-docs/issues/247, where there is some previous work linked.
What alternatives are there?
Do it manually

Closing because Platform team will open docs ticket when API changes to inform that there are upcoming changes to the API


Added a new greeting

I have commited a pull request against issue #6

I have more ideas for greetings and would love to contribute to other issues as well.

Hi! This project was intended as a workshop we could run in-person and this is the template for that workshop. Thanks so much for your interest but we'd like to keep these opportunities open for people attending those workshops.


Validation: Invalid Entities return a 422 WebDAV status code

Unprocessable Entity (422) is part of the WebDAV protocol/extension, from what I can tell (http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml), and not technically an HTTP status code.
I believe this should simply be a 400 (Bad Request) -- http://www.w3.org/Protocols/rfc2616/rfc2616-sec6.html#sec6.1.1

What are the disadvantages of returning a WebDAV protocol/extension? The convention has been to return 422 when the request body may contain syntactically valid data, but semantically invalid data.
On the flip-side, as a comparison, Jersey only returns a 400 or 500 if an error happens. If we went with this approach, there is the potential to break clients who became accustomed to the 422 status code.

I'm not sure how to put it besides one is valid HTTP, and the other is not -- at the very least this needs to be configurable. Many front-end libraries and HTTP clients aren't prepared to handle 422, considering the wider HTTP ecosystem.
For instance, many JavaScript developers who'd consume this API often refer to https://developer.mozilla.org/en-US/docs/Web/HTTP/Response_codes, http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html, etc... At least for me, all the top google hits for HTTP status codes don't even mention 422.
We're attempting to transition to a HTTP Hypermedia API, being compliant with HTTP is that much harder.
Fundamentally, this issue far broader than Dropwizard. Any other client (JavaScript library/framework, whatever), that does conform now may need tweaking because of non-compliance.
As for migrating old clients, simply providing migration notes, and a configurable fallback to old behaviour (to be remove in the next major version) should be sufficient.

Good points. I would also like to raise a couple of more things I've found:

A fairly lucid stackoverflow answer pointing out our exact discussion, pointing out that the spec defines a 400 to mean syntactically invalid data whereas.
Some of the largest Hypermedia APIs (Github, Twitter, Facebook (iirc, can't check now)) use status code 422 for invalid entities.

However, I found some evidence supporting the move to 400:

HTTPbis defines 400 Bad Request as :

indicates that the server cannot or will not process the request due to something which is perceived to be a client error

Thus, in this instance, an invalid entity would be a 400 response

I think I just talked myself into a circle and this has been inconclusive, but informative :smile:

This is the worst, and now I'm in a circle too.

I think 422 is wrong, because it's not HTTP
I think 400 isn't quite right because it's referring to syntax

Also this is the latest version of the RFC you linked earlier, in which case they made it less semantics.
In regards to the SO post, Kristian quoted the WebDAV Protocol intro
While the status codes provided by HTTP/1.1 are sufficient to describe most error
conditions encountered by WebDAV methods, there are some errors that do not
fall neatly into the existing categories. This specification defines extra status
codes developed for WebDAV methods (Section 11)

As it says, "WebDAV methods", and as per the first sentence makes a clear delineation between it and HTTP 1.1.
I'm leaning towards 400, but not by much. I think it makes the most amount of sense making it a configurable thing, I have no clue what the default should be, the two things I'd be thinking about:

Leave it as 422 for compatibility -- and might become a defacto standard
Move to 400 for HTTP 1.1 compliance, and let people consciously break it

Very informative discussion. I would lean towards 400 for the reasons listed above

I personally more lean to 422. Despite that it's not defined in RFC 7231, it's widely used and adopted by many clients and intermediaries. Also it's more specific then a fairly general 400 error. If I get 422 error, I know that the server comprehended my request, but rejected it.

My $0.02 CDN would be to preserve the current behavior (return 422) and
provide a configuration flag for strict spec conformance (return 400). That
way we keep doing what we've always done so we don't break our existing
consumers (preserve backwards compatibility) but we also provide the
ability for people to deal with less flexible clients/consumers. Just a
thought.
On Tue, Jun 23, 2015 at 3:27 AM Artem Prigoda<EMAIL_ADDRESS>wrote:

I personally more lean to 422. Despite that it's not defined in RFC 7231,
it's widely used and adopted by many clients and intermediaries. Also it's
more specific then a fairly general 400 error. If I get 422 error, I know
that the server comprehended my request, but rejected it.
—
Reply to this email directly or view it on GitHub
https://github.com/dropwizard/dropwizard/issues/1117#issuecomment-114389740
.

I agree with @glennmcallister.  Preserve the current behavior (422) and use a config flag for a 400.

Are there any real-world problems with the 422 status code that would justify breaking backwards-compatibility with older versions or add a maintenance-"tax" to Dropwizard?

That's a fair question. Saem's point is that there are clients out there
that aren't necessarily going to be able to deal with 422.

Many front-end libraries and HTTP clients aren't prepared to handle 422,
considering the wider HTTP ecosystem.

That being said, this is the first issue (to my knowledge) we've received
about this specific point. And the first google hit it got on 'http 422'
was a stackoverflow question on this very subject, and the accepted answer
said (in short) "use 422, not 400".
#shrug
Actually, I'm starting to take issue with saying 422 isn't a valid HTTP
code:
http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml
Section 11 of RFC4918 clearly states they are added to the complete set of
valid HTTP codes:
The following status codes are added to those defined in HTTP/1.1
[RFC2616 http://tools.ietf.org/html/rfc2616].
So... what's the problem?
On Tue, Jun 23, 2015 at 12:55 PM Jochen Schalanda<EMAIL_ADDRESS>wrote:

Are there any real-world problems with the 422 status code that would
justify breaking backwards-compatibility with older versions or add a
maintenance-"tax" to Dropwizard?
—
Reply to this email directly or view it on GitHub
https://github.com/dropwizard/dropwizard/issues/1117#issuecomment-114571788
.

Even if 422 remains the dropwizard default, and there is a configuration to go the other way that's workable.
@glennmcallister
In regards to the Stack Overflow post. One person, who didn't know the answer in the first place, hitting accept on a SO post hardly constitutes a strong argument, if at all a data point. As for the answer itself, as @nickbabcock points out it's not out right unreasonable. That being said, if you look at the part of the WebDAV spec (not HTTP) he quotes, it clearly states "While the status codes provided by HTTP/1.1 are sufficient to describe most error conditions encountered by WebDAV methods, there are some errors that do not fall neatly into the existing categories. This specification defines extra status codes developed for WebDAV methods (Section 11)". Emphasis added is my own, but to be clear that entire RFC is not the protocol most are working with. I would ask that we stop referencing a non-HTTP RFC as if it is.
422 is not valid HTTP, you're pointing to a list of registered codes, I believe the intention is to avoid collisions across protocols that are a super set of HTTP, the same as say internet socket port number registration done by IANA.
Specifically, in regards to Section 11 of RFC4918, what you are quoting is out of context:
11.  Status Code Extensions to HTTP/1.1

   The following status codes are added to those defined in HTTP/1.1
   [RFC2616].

The title clearly states that these are extensions, within a document that clearly states it's for a different protocol (WebDAV).
As I pointed out earlier, except for Google not knowing the difference, and an apocryphal answer on SO, can we not reference an RFC for a protocol (WebDAV) that the vast majority aren't concerned with, and stick to HTTP?

Respectfully, WebDAV is an extension to the HTTP protocol. You are trying
to make out that WebDAV is something other than HTTP. It's not. It's an
accepted RFC by the IETF.
At this point, I'm bowing out of the discussion.
On Tue, Jun 23, 2015 at 2:20 PM Saem Ghani<EMAIL_ADDRESS>wrote:

Even if 422 remains the dropwizard default, and there is a configuration
to go the other way that's workable.
@glennmcallister https://github.com/glennmcallister
In regards to the Stack Overflow post
http://stackoverflow.com/questions/16133923/400-vs-422-response-to-post-of-data/20215807#20215807.
One person, who didn't know the answer in the first place, hitting accept
on a SO post hardly constitutes a strong argument, if at all a data point.
As for the answer itself, as @nickbabcock https://github.com/nickbabcock
points out it's not out right unreasonable. That being said, if you look at
the part of the WebDAV spec (not HTTP) he quotes, it clearly states "While
the status codes provided by HTTP/1.1 are sufficient to describe most error
conditions encountered by WebDAV methods, there are some errors that do
not fall neatly into the existing categories. This specification defines
extra status codes developed for WebDAV methods (Section 11)". Emphasis
added is my own, but to be clear that entire RFC is not the protocol most
are working with. I would ask that we stop referenc ing a non-HTTP RFC as
if it is.
422 is not valid HTTP, you're pointing to a list of registered codes, I
believe the intention is to avoid collisions across protocols that are a
super set of HTTP, the same as say internet socket port number registration
done by IANA.
Specifically, in regards to Section 11 of RFC4918, what you are quoting is
out of context:

Status Code Extensions to HTTP/1.1

The following status codes are added to those defined in HTTP/1.1
[RFC2616].
The title clearly states that these are extensions, within a document that
clearly states it's for a different protocol (WebDAV).
As I pointed out earlier, except for Google not knowing the difference,
and an apocryphal answer on SO, can we not reference an RFC for a protocol
(WebDAV) that the vast majority aren't concerned with, and stick to HTTP?
—
Reply to this email directly or view it on GitHub
https://github.com/dropwizard/dropwizard/issues/1117#issuecomment-114597013
.

Even if 422 remains the dropwizard default, and there is a configuration to go the other way that's workable.

But we would still need to implement, test, and maintain that code.
The question I have is if there are any actual problems with the 422 status code or if it is just a theoretical problem that never happens in the real world (as any sane HTTP client should handle the whole 4xx range and not just some specific/hand-picked status codes).
I haven't seen any client having problems with the 422 status code yet. So I'm voting for closing this issue as "won't fix".

As a user I vote "won't fix" as well. It's been the default behavior for years now. I could make an argument that any client that doesn't support 422 should.

@joschi @JonMR I think this got lost in the discussion but this is a bit forward looking, specifically at hypermedia. I agree, within the context of an "old school" API where the client has to know much more about how the server behaves and has lots of specialized logic then yeah, no big deal.
In our particular scenario we were going to have 400 return a response entity with a "remediation" rel, that would allow the client to fix say a missing pre-requisite. For example, it tries to send a pre-formatted email, but the specific template for that doesn't exist, the system can return a 400, and a body containing an error code, and remediation rel allowing you to create the required template. My concern is that yeah, currently the http library (angular) we're using is workable, I'm concerned that as we deal with other clients that aren't so forgiving, we'll be stuck. That will be an awkward migration.

Since there hasn't been any new argument for this change within 2 weeks, I'm closing this issue now.


fix missing Mongodb servermap icon for UI v2

NO_IMAGE_FOUND.png is used for MongoDB when UI v2 is used.

Codecov Report

Merging #6070 into 1.8.x will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            1.8.x   #6070      +/-   ##
=========================================
- Coverage   40.62%   40.6%   -0.02%
=========================================
  Files        2673    2673
  Lines       80441   80441
  Branches    10901   10901
=========================================
- Hits        32680   32666      -14
- Misses      44789   44808      +19
+ Partials     2972    2967       -5

Impacted Files
Coverage Δ

...rp/pinpoint/rpc/control/ControlMessageDecoder.java
64.28% <0%> (-14.29%)
:arrow_down:

...pc/server/LoggingServerMessageListenerFactory.java
90% <0%> (-10%)
:arrow_down:

...rp/pinpoint/web/mapper/stat/AgentStatMapperV2.java
60.97% <0%> (-7.32%)
:arrow_down:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
60% <0%> (-5%)
:arrow_down:

...ofiler/sender/StandbySpanStreamDataSendWorker.java
80.59% <0%> (-2.99%)
:arrow_down:

...om/navercorp/pinpoint/rpc/codec/PacketDecoder.java
61.7% <0%> (-2.13%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
77.77% <0%> (-1.05%)
:arrow_down:

...point/rpc/client/DefaultPinpointClientHandler.java
71.83% <0%> (+0.94%)
:arrow_up:

...corp/pinpoint/rpc/stream/StreamChannelManager.java
72.41% <0%> (+1.72%)
:arrow_up:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
85.36% <0%> (+2.43%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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

Thank you for your contribution


feat: add card product

I thought it would be interesting to add a product card.

Great component, Otoniel!


Error: Unsupported system library

I get the following error when installing the repository in the project:

What should I do to fix it and be able to use the repository?

Hi @sourcer18, I haven't develop anything for Android yet, maybe you are getting the error because you have that platform installed when installing the plugin. If you are developing for Android, we have plans of adding support to Android in the coming months, but not sure when.


[BUG] My issue is a fastflag that is affecting my game by make every mesh that is like a tree or shrubbery it becomes squished or small and i am trying to find the certain fastflags

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
So the trees and the shrubbery is all broken and i need to find the root of the issue i dont know if its a fast flag or a bug
Bloxstrap Log

The picture right there is supposed to be a palm tree in the game southwest Florida

Can you attach your flag list?

This is an issue with your flag configuration. We clearly and specifically tell you to not blindly paste in flags if you're not fully aware of what they do.

Yeah its understandabe it doesnt make the game unplayable i have a lot of flast flags because  i cant run some roblox games with this pc


[Bug] Metadata colliding with Angular 2

When using this library with angular 2 and webpack the metadata get's messed up, for example we have 1 service which we use the @type decorator and it works before putting it, however the instant we add the decorator the app breaks in a weird way, the error yells for another unrelated component that just happens to use the service:

Here's the line in question, when we comment this the app works again:

It's breaking with the native Date class of Javascript.

Sorry about this, we were using the old package serializer.ts.


Cannot define new/existing Attribute Literal in info.json v1.1

There's currently no way to define a new or existing attribute literal column in the info.json v1.1 structure. We need to add this functionality in.
Perhaps we could allow the user to specify a new property isLiteral against existing/new attribute column definitions? Once this kind of functionality has been added, we need to update the documentation done in #118 to reflect this.
Relevant location to help whoever takes this ticket: https://github.com/GSS-Cogs/gss-utils/blob/csvwlib-integration/gssutils/csvqbintegration/configloaders/infojson1point1/columnschema.py#L121

Hey team! Please add your planning poker estimate with ZenHub @robons @santhosh-thangavel


Feature: Standalone DB check if exists

Is your feature request related to a problem? Please describe.
No issue, just a nice to have
Describe the solution you'd like
Something to check if the DB exists and create if it doesn't but a standalone function. Currently calling the createDatabase function where the ifNotExist option is true but would be nice to skip calling the create DB if it already exists.
Describe alternatives you've considered
None
Additional context
Just something that would be nice.

@Divaaan so you are thinking of a seperate function like checkDatabase to verify if the database is created or not ?


Train/test & metrics interpretation

Hi,
I'm new to time series prediction, so please excuse my limited knowledge and quite basal questions.
In GluonTS, following the tutorial, we create a train and test dataset, where the test dataset is the full dataset and the train dataset is the full dataset minus prediction_length values off the tail.
I'd like to compare my results to non-GluonTS solutions, for example LGBM (quantile regression), but I'm not sure how to. I've always learned to use a 80/20 split or something of the likes to split my train and test data due to overfitting etc. Are they simply not comparable?
Secondly, are the metrics calculated for the full test set or the last prediction_length values? Looking at the figure in the quick start tutorial, I notice that the median prediction is within the 90% confidence interval at each prediction, but the Coverage[0.9] value is ~88.7%. How do I interpret these?

Hello
I can just answer your one query
" I notice that the median prediction is within the 90% confidence interval at each prediction, but the Coverage[0.9] value is ~88.7%"
Median prediction is always at p(50)(50% prediction interval ) and p(90) means 90% confidence interval.Moreover,if your model is learning good from data ,then its p(90) will be equal or greater than 90%,for less than 90% ,you need to tune the hyper-parameters.


The custom toolbar is missing the following icons.

Feature Description:
Hello friend!
The custom toolbar is missing the following icons.

Theia 1.53.200
Windows 10

I've transferred the discussion to the theia-blueprint repo, since the request seems to be to support these toolbar buttons as a default (if I understand @zhouxinghong correctly).
Note that the codicons for that are available, the commands are just not implemented.

I think I am confused by the screenshots. Do I assume correctly, that the screenshots you uploaded are Wireframes how the tool should look like and that you do not find these icons in Theia to be used on the toolbar? (probably because our codicon version is outdated)?

The function commands corresponding to each button seem to be nowhere to be found.

@zhouxinghong It seems you have a good unerstanding of the underlying issue, as you mentioned that the icons can be integrated into the Theia platform. Are you up for a contribution to fix this?

@zhouxinghong It seems you have a good unerstanding of the underlying issue, as you mentioned that the icons can be integrated into the Theia platform.

Thank you so much for trusting me! 😜
How can I help solve this problem?

Are you building your own tool based on Theia or are you just using the Theia IDE as is?
I am still not 100% sure if I understand your reported issue correctly. Could you describe from a user point of view what exactly the user wants to do?
Also: the screenshots you posted, are they from Theia, another tool or are these Wireframes?


Improve code coverage

Improve the code coverage by adding:

Custom Lambda Test
Decode APIGatewayV2Request in the example

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


doc: documentation updates for v4.0.0

Gah, my git branches were messed up, and I initially thought there was more to change here than there really is. The residual changes are not worth doing.


Unable to detect magic __get properties correctly registered with __isset

Description
This was specifically found when working with the column(...) method in the AbstractCollection implementation. The issue is that PHP's magic getter functionality is not supported.
Steps to reproduce

Write a class Example that defines no properties with a __get($key) and __isset($key) method to return "value" and true when the $key is "key", respectively
Make a new Collection of Examples, e.g. new Collection([new Example()])
Call $collection->column('key')
A ValueExtractionException is thrown

Expected behavior
An array is returned: ["value"]
Screenshots or output

Environment details

version of this package: 1.3.0
PHP version: 8.1
OS: macOS

Additional context

Maybe I can get to a PR on this- but no current capacity for it

I think you just need to add
        if (method_exists($element, '__get')) {
            return $element->$propertyOrMethod;
        }

here to support it.

@SimoTod I may be wrong, but I understood best practice was to utilize both __isset as a way to dictate when __get would return a value. This feels safer to me than making all classes with __get return a value. I had thrown together a patch for this and could push a PR shortly with testing.

@SimoTod I may be wrong, but I understood best practice was to utilize both __isset as a way to dictate when __get would return a value. This feels safer to me than making all classes with __get return a value. I had thrown together a patch for this and could push a PR shortly with testing.

Sure, that's best practice but you need to document it in this case because it's not required.
You can have a magic __get in a standard php class and that would work when you call an arbitrary non existing property.
All class with __get, would call the magic getter if defined and __get, depending on the implementation, may as well throw an exception if not trying to access something not expected.
Slightly related, in theory, you could make the same reasoning for __call and methods.

Definitely could do a similar check for __call as well.
I'm not sure where this would best be documented; for example, the behavior today of not supporting magic methods isn't documented.

I opened that PR to do the checks with isset to support __get and __isset classes. We can discuss which path would be preferred going forward. I'd be interested in hearing more from @ramsey on it as well 🙏

Just to clarify the expected behaviour: With a fairly standard implementation (taken from the php documentation) you would not be able to access something set to null since isset is meant to return false in that case so __isset is usually (or at least often) implemented in that way. See https://onlinephp.io/c/408a9

Yes the standard behavior of isset will return false when a value is null, but when implementing the __isset magic method behavior it's up to the code owner.
That method signature is public __isset(string $name): bool, and doesn't inherently rely on isset, it overrides it.
At the point in the code where we've already checked for explicit properties, and explicit methods, the case for properties accessible via __get is not defined- and the only consistent manner to dictate that it is accessible is via isset and the __isset magic method. Otherwise, like you given an example of, it will always return something, even if it's a bunch of nulls.

Not really, it's up to the code owner in the same way. Generally a magic __get will contain some ifs, return the value if those conditions are satisfied or throw if not (same as the extractor class, just a different type of error but we could catch it and let the code throw the correct exception if we are concerned about consistency). The only defect that I can see is that you have to run __get to know if it will error (and because you don't know about the implementation, you don't know what side effects it could have even if it shouldn't have any) so yeah, not ideal either and maybe the isset approach makes more sense.
However, we mentioned best practices above but then we are suggesting the code owner should implement it in a way that doesn't follow the original purpose of the method. If it's a third party library implemented in a canonical way (could be part of a dependency imported with composer), you won't have much control on it as well. https://www.php.net/manual/en/language.oop5.overloading.php
It feels like we really need a __property_exists magic (someone did try to ask for it at some point https://bugs.php.net/bug.php?id=44857 :)).


Update combat-logger to v1.1.0

Add a built-in damage meter
Log Damage messages from Party
All logs now go in a queue with a 2 tick delay before they are written so that previously unknown hitsplat sources can now be matched up with a Party members hitsplat
Create a death log for end of Verzik P1

on shutdown, you are missing EventBus#unregister for LogQueueManager

on shutdown, you are missing EventBus#unregister for LogQueueManager

I just pushed a fix for this. Thanks!


Tablename in Create Table Dialog (Oracle)

DBeaver <IP_ADDRESS>810282259  (EA)
When creating a new table in Oracle I encountered that the table name is reversed (cursor is jumping at the beginning of the field after each keystroke) when while typing.

Actually this happens not only with Oracle tables but with all objects which name is transformed on edit (e.g. Oracle object names are uppercased).
Thanks for the bug report. See fix in the next version.


Let plugins add options to .mdformat.toml file

Context
Currently, mdformat plugins are allowed to implement a add_cli_options function to add arguments to the mdformat ArgumentParser, but there is no way to allow those options to be added to the .mdformat.toml file without monkey patching the mdformat._conf module to add the new options to the DEFAULT_OPTS dictionary or _validate_keys and _validate_values functions.
Proposal
Add a way for plugins to declare acceptable options and values for the mdformat.toml file.
Along the way, maybe also slightly reformat how the options are declared, so that they are not hard-coded in two different places (_conf and _cli) independently. An option for this would be to have them declared only inside _conf, with a way for plugins to alter them, and then have both the _cli.ArgumentParser and the _conf validation functions read and use them.
Tasks and updates
No response

Thanks for the issue!
Would https://github.com/executablebooks/mdformat/pull/461 work for you? I didn't write any docs yet, but I think the feature is pretty well described by the docstring of the added plugin interface:
def add_cli_argument_group(group: argparse._ArgumentGroup) -> None:
        """Add an argument group to mdformat CLI and add arguments to it.

        Call `group.add_argument()` to add CLI arguments (signature is
        the same as argparse.ArgumentParser.add_argument). Values will be
        stored in a mapping under mdit.options["mdformat"]["plugin"][<plugin_id>]
        where <plugin_id> equals entry point name of the plugin.

        The mapping will be merged with values read from TOML config file
        section [plugin.<plugin_id>].

        (optional)
        """

So with the new endpoint

plugins' CLI options go to a plugin specific group
plugins have access to[plugin.<plugin_id>]
some_key = "some value"

namespace in TOML
core mdformat merges the CLI values with TOML config

I plan to deprecate the old add_cli_options endpoint as I haven't seen any use case where access to a argparse._ArgumentGroup is not sufficient, and I want to encourage plugins to move their CLI options under a group.
Would these changes break your pyproject plugin?

Thanks @hukkin I believe the proposed solution would cover the original request.
WRT to the plugin, I believe that the API change should not break it, but I am not sure if plugin options will be properly picked from the pyproject.toml. I suppose they will, but I will have to test it.
I will give this is a try against your branch to confirm it, and if it breaks I will let you know and try to adapt to it before it you release it. Do you have any timeline in mind, to avoid slowing you down?

I will give this is a try against your branch to confirm it, and if it breaks I will let you know and try to adapt to it before you release it.

That'd be great, thanks!

Do you have any timeline in mind, to avoid slowing you down?

No rush, this can easily wait a month if you're busy.

I've merged the PR but won't release until you've had the chance to test it, or after a month or so.

Friendly reminder: I'll make the release some day next week.


Feature : Added Promote referral program messaging to OptionsSelector component

Details

This PR is to add refferal program messaging to OptionsSelector component
Fixed Issues

$ https://github.com/Expensify/App/issues/29881
Tests

Start Chat Flow

Go to FAB > 'Start Chat'

[ ] Observe that there is a Call-to-Action (CTA) button.

Click on the CTA button.

[ ] Verify that you were taken to the new referral page

Request Money Flow

Go to FAB > 'Request Money'
Select the desired amount.

[ ] Once again, observe the presence of a CTA button.

Click on the CTA button.

[ ] Verify that you were taken to the new referral page

Send Money Flow

Go to FAB > 'Send Money'
Select the desired amount.

[ ] Observe that there is a CTA button.

Click on the CTA button.

[ ] Verify that you were taken to the new referral page

Search Flow

Click on the magnifying glass (search button).

[ ] Observe that there is a CTA button.

Click on the 'Referral' CTA button.

[ ] Verify that you were taken to the new referral page

[x] Verify that no errors appear in the JS console

Offline tests

Same as tests
QA Steps

Same as tests

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[x] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Web
Video:
https://github.com/Expensify/App/assets/39777589/5a3b335d-be32-4f92-9d25-154488095c94
Request:

Start chat:

Send money:

Click the magnifying glass:

Shaping up nicely! A few things:

[ ] Info icon should be 20x20 as per Figma (it looks a bit too big in the screenshots above):

[ ] The green text should also be bolded

Would also be great if we could get a screen recording so we can see how the interaction works together :)

Updated code and text

Added video as well!

@cubuspl42 think we can get a review of this tomorrow (friday)?

@puneetlath Yes, I'll review it in the next hour or so. Sorry for the delay.

I'd suggest to add some structure to the testing steps:

Start Chat Flow

Go to FAB > 'Start Chat'

[ ] Observe that there is a Call-to-Action (CTA) button.

Click on the CTA button.

[ ] Verify that you were taken to the new referral page

Request Money Flow

Go to FAB > 'Request Money'
Select the desired amount.

[ ] Once again, observe the presence of a CTA button.

Click on the CTA button.

[ ] Verify that you were taken to the new referral page

Send Money Flow

Go to FAB > 'Request Money'
Select the desired amount.

[ ] Observe that there is a CTA button.

Click on the  CTA button.

[ ] Verify that you were taken to the new referral page

Search Flow

Click on the magnifying glass (search button).

[ ] Observe that there is a CTA button.

Click on the 'Referral' CTA button.

[ ] Verify that you were taken to the new referral page

@waterim

@cubuspl42 What is wrong regarding refer a friend?

I can observe a literal %linkUrl% placeholder

Updated @cubuspl42 @puneetlath

Yes, that was from the design, probably feature for the future cc @puneetlath

But this isn't a functionality behind any beta flag... We're merging to main, it can be deployed to staging and then prod in this state. Maybe I'm missing something.

But this isn't a functionality behind any beta flag... We're merging to main, it can be deployed to staging and then prod in this state. Maybe I'm missing something.

Agree with you, lets wait for @puneetlath answer, I don't have any knowledge of this promote link which was provided, unfortunately

The link should be:
https://join.my.expensify.com/?thanks=<primaryLogin>
For example:

phone number<EMAIL_ADDRESS>email<EMAIL_ADDRESS>

But that is pretty long and is going to look bad. So maybe we should do linked text. Like

Refer a friend, get $250
Send your Expensify referral link to a friend:
Referral link
When they start an annual subscription, you'll get $250.
Learn More

Refer a friend, get $250
Send your [Expensify referral link] to a friend, get $250 when they start an annual subscription. [Learn more.]

So here's an idea above. When you click "Expensify referral link" it automatically copies the link to your clipboard and tells you that's what it did. And of course when you click "Learn more." it takes you to the help page. Thoughts?

I don't think we want to change the way hyperlinks behave. But we could add the copy to clipboard button next to it.

Got it - so what you're suggesting is this still, but also adding the copy icon w/copy functionality next to the "Referral link" line?

Yeah. Just so we don't change the behavior of clicking a link in different places.

Cool, I'm down with that! What happens when you click directly on "Referral link" though?

@jamesdeanexpensify It would open it like any other link.
@waterim what do you think of that approach?

We have a component to copy, something like this:
<CopyTextToClipboard
       text={CONST.EMAIL.RECEIPTS}
       textStyles={[styles.textBlue]}
/>
```, but this component doesnt accept child(link or something)
Do I need to create a new component or update this one to accept links, to be able to click on this and copy this?
cc @puneetlath

Ah interesting I see. An alternate approach would be to make it a button. So like:

Refer a friend, get $250
Send your Expensify referral link to a friend:
Copy referral link (button)
When they start an annual subscription, you'll get $250.
Learn more.

Not just a link, but a button? How should it look like?

What button should do?
just to redirect or something else?

@dubielzyk-expensify we're working on one of the referral program modals, and this idea needs a button mockup. Would you be able to help with that? I think if "Copy referral link" is too long for button text, we can just use "Copy link" since the lead-in line makes it clear what link you're copying. Thanks!

Potential UI inspiration for a link meant for copying:

Here's two mocks. I'm a bit unsure which copy to use, but the left one is similar to what suggested above. The right one is my take on making the copy and layout even more simple.

I prefer second one
What do you think @puneetlath?

Yeah, let's just do the one on the right. Thanks!

@puneetlath @jamesdeanexpensify @dubielzyk-expensify Hey guys, just one question, can we do the "learn more" button under the copy referral?
Because on all other pages we have it like this and Im not sure do I need to change it conditionally only for this page
Like this:

I'm fine with that! Also, for the first line, can we see how this edit looks?
"Send your Expensify referral link to a friend or anyone else you know who spends too much time on expenses."

I'm also fine with that. Let's make the layout on all of these pages consistent.

@jamesdeanexpensify

@jamesdeanexpensify Do I need to change the text for all pages?
Because I don't see any updated in the issue

Sorry @waterim I meant can you make the whole thing:

Send your Expensify referral link to a friend or anyone else you know who spends too much time on expenses. When they start an annual subscription, you'll get $250. Yep, it's that easy.
[Copy referral link]
Learn more

@jamesdeanexpensify Ahh, sure, here it is

@waterim two things:

For this, can you remove "Yep, it's that easy." just to shorten it more.
I will go back today and update the copy for the four flows here based on our discussions to date. A lot has changed and thank you for being flexible. (Note: I think the others should follow this format and I'll note that in the updated comment).

@jamesdeanexpensify Thank you!
You will update together with Spanish translations, right?

Yep, will do.

OK @waterim the updated Spanish translations should be ready at the top here!

Ok great. @cubuspl42 if you could give us another review when you have a chance please 😄

@puneetlath I'm on it!

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/2590174/ccc3534e-8410-4918-ae34-e4363e51265c

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Can I see a mobile recording of how the keyboard slides away when you click the referral banner?
Love the change to a check when you click copy code. Well done!

https://github.com/Expensify/App/assets/39777589/71fd6ff0-00e9-4900-abb0-760b8d5b3b8e
@dubielzyk-expensify

Sorry for my bad explanation. Can you add a recording of where you click the "Refer a friend, get $250" banner? Basically what you have in the video, just tap the banner as well so I can see how the keyboard hides. Then if you can click back from the screen you go to so we can see how that works as well.

Also, can you add a period to the end "Refer a friend, get $250." to see how it looks? Thank you!

@dubielzyk-expensify Here is a video, sorry for a bid delay in response
https://github.com/Expensify/App/assets/39777589/55368025-4f52-4d6d-8ff6-e90d7d12350a

@puneetlath Updated all your comments

Watching this video, I wonder if it's worth a discussion in Slack @dubielzyk-expensify @puneetlath on how much space the "Refer a friend, get $250" text takes up when you click into the search field. Any strong opinions there?

I think it looks good. @dubielzyk-expensify feel free to merge if you are good with the video.
@jamesdeanexpensify I say we try it and we can update the behavior if we think it's a problem after experiencing it for a bit.

Sounds good to me!

I'm good with the video (looks great), but I'll let someone else merge it 😂

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/luacmartins in version: 1.4.1-13 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Just FYI that this PR had this issue. We didn't add a fallback route to Navigation.goBack as mentioned in the navigation guidelines so both deeplinking and refreshing the page broke navigation for RHP

Since you can deeplink to different pages inside the RHP navigator, it is important to provide the possibility for the user to properly navigate back from any page with UP press (HeaderWithBackButton component).

An example can be deeplinking to /settings/profile/personal-details. From there, when pressing the UP button, you should navigate to /settings/profile, so in order for it to work, you should provide the correct route in onBackButtonPress prop of HeaderWithBackButton (Navigation.goBack(ROUTES.SETTINGS_PROFILE) in this example).


change of primary tag

@MichaelCzcz Is the primary tag now correct and changes will get applied properly to the tutorial?


payments received 3 days ago still show 'receiving'

hi all payments received since about 3 days ago still show 'receiving' instead of 'received' like the ones before that show.what could be the cause of that? thanks

If it is still 'Receiving' then that means it hasn't been put in a block yet.
Most likely this will be because of a low fee.
If you double click on the transaction you see a 'Transaction Details' wizard. If you click Next a couple of times there is a button to open up the transaction in blockchain.info.
Have a look at it in there.


Fix "Document or section may not begin with a transition" from sphinx-check [wip]

What does this PR do?
Fixes #490.
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

It seems there is no way to disable Unchanged files with check annotations (Beta) as the issue https://github.com/actions/toolkit/issues/457 is still open, so I'll try to resolve those warnings from sphinx-check in this PR instead of turning off the feature Unchanged files with check annotations (Beta).

It seems there is no way to disable Unchanged files with check annotations (Beta) as the issue https://github.com/actions/toolkit/issues/457 is still open, so I'll try to resolve those warnings from sphinx-check in this PR instead of turning off the feature Unchanged files with check annotations (Beta).

yeah, I was thinking rather fix the warnings then suppress them from PRs :]

yeah, I was thinking rather fix the warnings then suppress them from PRs :]

mind check the two failing test for make and test docs seem like we need to mock the packages...

mind check the two failing test for make and test docs seem like we need to mock the packages...

@Borda Would you mind checking the changes again?

@Borda Would you mind checking the changes again?


Workloads re

https://github.com/Azure/sdk-release-request/issues/3686

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-arm-workloads


Search option in schedule builder

I am picturing a simple search bar that would allow you to search for a show that  you know might have episodes or other content you don't want.
An example could be Pokemon, in which I have the movies in the "Specials" folder in the TV Library. Currently I have to go through manually and remove any files that say "Pokemon S00EXX, but the search bar could allow me to narrow the schedule down to what I need by typing "Pokemon S00" in the search field, with a remove all button.

add to this one a bit...
removing/deleting things from a channel...
It would be nice to have a separate list of shows/seasons for items already in the channel (grouped if tv/season) and a remove/delete button.
or add a delete button from the adding show selection (right now, it shows the '+' to add, but if that entry is already added, show a '-' button to remove it.
I only use this for TV so far, but the concept should work well for movies as well.
Love this so far! =)

An example could be Pokemon, in which I have the movies in the "Specials" folder in the TV Library. Currently I have to go through manually and remove any files that say "Pokemon S00EXX, but the search bar could allow me to narrow the schedule down to what I need by typing "Pokemon S00" in the search field, with a remove all button.

Since we are talking about Schedule Builder functionality as it relates to Specials, rather than create a new Enhancement Request, I thought I'd add to this one:
When adding a series, at the series level, it would be great to have an option next to the "+" for "Add All Except Specials".  This would save time in not having to remove the Specials after adding the series (or would prevent having to add each Season individually to avoid adding the Specials).

When adding a series, at the series level, it would be great to have an option next to the "+" for "Add All Except Specials". This would save time in not having to remove the Specials after adding the series (or would prevent having to add each Season individually to avoid adding the Specials).

Yeah, the specials can be a bit annoying and I have had to recreate a few channels already after seeing they where there... need to be more careful when creating. This would be a great feature (and the ability to delete stuff in bulk without having to recreate would rock too).
j

@spicerackk @psybertech There are now Tools buttons for Remove Duplicates, Remove Flex, Remove Specials and Remove All.  Do you feel this request is handled by the mentioned buttons?  If not, please clarify what part of the request remains and include a detailed use case.
Anything that hasn't already been mentioned should be added to a New Issue.

Love the new remove specials button!
Works for me!

@spicerackk How about you?

I would like a search option in the schedule builder, if I want to add particular episodes or shows that share a name but aren't the same (scooby-doo, stargate, star trek, etc).

I would like a search option in the schedule builder, if I want to add particular episodes or shows that share a name but aren't the same (scooby-doo, stargate, star trek, etc).


To give @sofiemeeus full access to this repository

@teodorgeorgiev could you give @sofiemeeus full access to this repository

done


Hire A Bitcoin Fraud Recovery Hacker review at Linux Cyber Security Company.

It began with a serendipitous encounter—a testimonial shared by Britney, a fellow traveler on the winding road of digital assets. Her words spoke of a miraculous recovery the Linux Cyber Security Company orchestrated. Intrigued and desperate for a lifeline in my crypto conundrum, I embarked on a journey that would redefine my perception of trust in the digital realm. Upon reaching out to Linux Cyber Security Company, my heart raced with anticipation, hoping they could work their magic on my blocked crypto recovery. With bated breath, I shared my plight, providing evidence of my dilemma and praying for a solution. To my astonishment, a prompt response came—a beacon of reassurance in the sea of uncertainty.  Linux Cyber Security Company wasted no time in assessing my situation, guiding me through the process with patience and expertise. Like a celestial conductor orchestrating a symphony of redemption, Linux Cyber Security Company navigated the complexities of my predicament with finesse and precision. And then, like a ray of sunshine breaking through the clouds, came the news I had longed for—a new private key had been generated, restoring my precious bitcoins. It was a moment of jubilation, a triumph over adversity that filled me with newfound hope. But Linux Cyber Security Company capabilities transcended the mere retrieval of lost assets. Delving deeper into their expertise, I discovered a wealth of knowledge in reclaiming lost or stolen cryptocurrency, and even exposing fraudulent investment schemes. Their dedication to unraveling the intricacies of online fraud is not merely a profession, but a calling—a commitment to safeguarding the integrity of the digital landscape. Through their unwavering support and commitment to integrity, Linux Cyber Security Company has become more than just skilled technicians—they are guardians of trust in the digital realm. With their assistance, I reclaimed what was rightfully mine, turning despair into determination and paving the way for a brighter future. Take heart to all those who find themselves entangled in the web of online fraud. With the guidance of Linux Cyber Security Company, there is a path to redemption—light amidst the shadows of uncertainty. Trust their expertise, and let them illuminate the financial restoration and digital resilience path. Linux Cyber Security Company is a testament to the power of perseverance and knowledge in an ever-evolving digital landscape. With their unwavering commitment to integrity and unparalleled skill in navigating the complexities of cryptocurrency recovery, they have earned my deepest gratitude and highest recommendation.
Website: [ www.linuxcybersecurity.com ]
Email<EMAIL_ADDRESS>]

While browsing through Instagram, I came across a post from one of my friends about their successful Bitcoin investment and substantial profits. Intrigued by their claims, I decided to visit the website mentioned in the post. After creating an account, I contacted the support chat and was provided with a Telegram contact for further assistance. I connected with a person on Telegram who instructed me to install the MetaMask app and informed me that they would receive my money transfers. I was asked to make four bank transfers, totaling $158,000. Throughout this process, my friend, whose post had initially caught my attention, was also aware of the investment opportunity. However, I later discovered that his account had been hacked, and the hacker was using his page to promote false information about the company, leading me to believe it was legitimate. After noticing the scam, I was devastated and felt completely lost. I couldn't believe I had fallen for such an elaborate scheme, and the thought of losing such a significant amount of money was overwhelming. I didn't know where to turn or who to trust. Fortunately, a close friend recommended it. I seek help from TRUST GEEKS HACK EXPERT. Desperate and hopeful, I contacted them, explaining my situation in detail. From the very first interaction, I was impressed with TRUST GEEKS HACK EXPERT  professionalism and empathy. They quickly reassured me that I was not alone and that they had successfully handled numerous cases similar to mine. Their confidence and expertise provided me with a glimmer of hope in an otherwise bleak situation. TRUST GEEKS HACK EXPERT immediately began working on my case. Their team of experts meticulously analyzed the fraudulent website and the transactions I had made. They kept me informed throughout the entire process, explaining each step they were taking and why it was necessary. This transparency helped rebuild my trust, which the scam had shattered. One of the most impressive aspects of TRUST GEEKS HACK EXPERT service was their thorough understanding of cryptocurrency and online scams. They knew exactly where to look and how to gather the necessary evidence to build a strong case against the perpetrators. Their technical skills and knowledge of the digital landscape were evident in the speed and efficiency with which they operated. Within a 2 day short TRUST GEEKS HACK EXPERT was able to expose the entire operation. They identified the fraudulent website's operators and worked tirelessly to shut it down. Their efforts were relentless, and their determination to recover my funds was unwavering. Despite the complexity of the situation, they never wavered in their commitment to helping me. The moment I received the notification that my funds had been successfully recovered was one of immense relief and joy. I couldn't believe that the nightmare was finally over and that I had regained the money I thought was lost forever. TRUST GEEKS HACK EXPERT not only restored my financial stability but also my faith in the possibility of justice in the digital world. I am writing this review with immense joy and gratitude for the exceptional assistance provided by TRUST GEEKS HACK EXPERT. Their dedication, expertise, and compassion were instrumental in navigating a very difficult period in my life. If you find yourself in a similar situation, I recommend reaching out to TRUST GEEKS HACK EXPERT. They are a beacon of hope in the often world of online investments, and their ability to recover lost funds is nothing short of miraculous. Trust in their capabilities, and you will not be disappointed.
Web-site. h-t-t-p-s-://trustgeekshackexpert.com/
E-m-a-i-l<EMAIL_ADDRESS>W-h-a-t-s-A-p-p   +1-7-1-9-4-9-2-2-6-9-3
Tele-Gram: Trust-Geeks-Hack-Expert

I am truly grateful to have come across Daniel Meuli Web Recovery during a time when I was feeling hopeless and lost after falling victim to a Ponzi scheme. It seemed like all hope was lost, and I had resigned myself to the fact that I would never be able to recover the 213,000 pounds I had invested in BTC. The scammers had left me in a state of despair, with my money locked away in an improper profile that prevented me from making any withdrawals. However, everything changed when I stumbled upon a testimonial from someone who had successfully recovered their BTC with the help of  Daniel Meuli Web Recovery. Reading about their positive experience gave me hope, and I decided to reach out to  Daniel Meuli  Web Recovery for assistance. I was amazed by the professionalism and efficiency of their team from the very beginning. They were responsive, and understanding, and most importantly, they were able to deliver results. I was so relieved when  Daniel Meuli Web Recovery informed me that they had successfully recovered a significant amount from the scammers. It was a huge weight off my shoulders, and I felt like a huge burden had been lifted off my chest. The fact that they could recover much more than I had expected was truly a blessing, and I couldn't be more grateful for their services.  Daniel Meuli Web Recovery is truly a trustworthy and reliable hacking service that I would recommend to anyone in need of recovery assistance. Their expertise and dedication to helping victims of scams are truly commendable, and I am so thankful that I found them when I needed help the most. They have restored my faith in humanity and have shown me that there are still honest and trustworthy individuals out there who are willing to help others in need. I want to thank God for guiding me to  Daniel Meuli Web Recovery and for allowing me to share my experience with others. If you ever find yourself in a similar situation or need assistance recovering your funds from scammers, do not hesitate to contact  Daniel Meuli Web Recovery. They are the best in the business, and I am living proof of their exceptional services. They gave me the tools and support to reclaim my life.  WhatsApp>  +393 512 013 528   Website>  https://danielmeulirecoverywizard.online    Telegram>  @ Danielmeuli


Fixed Menu Bug

This change fixes a bug where previously, if you entered a large number into the text box, the box would expand but the other menu items would remain stationary, creating overlapping buttons. This fixes that bug by shifting the other buttons accordingly.

It looks good. Thanks for contributting!


Making some small clarification changes to the Okta doc section

Two small tweaks to ensure that people are aware of what values to enter in the custom resource, primarily focused on clarifying what the appId is.

@michaelryanmcneill Any chance you would be able to take a look at the requested changes?

Sorry, for some reason I didn't see notifications for this one. Fixing and will push changes.

This should be taken care of now @sabre1041 and ready to merge. Sorry again for the delay!

Thanks @michaelryanmcneill for following through on the changes


Password PDF

Password PDF are not asking,  for password to enter.
07-08 15:21:57.020 13331-13331/com.jagdiv.android.gogleapplication E/PDFView: load pdf error
07-08 15:21:57.020 13331-13331/com.jagdiv.android.gogleapplication E/PDFView: java.io.IOException: cannot create document: Incorrect password.
07-08 15:21:57.020 13331-13331/com.jagdiv.android.gogleapplication E/PDFView:     at com.shockwave.pdfium.PdfiumCore.nativeOpenDocument(Native Method)
07-08 15:21:57.020 13331-13331/com.jagdiv.android.gogleapplication E/PDFView:     at com.shockwave.pdfium.PdfiumCore.newDocument(PdfiumCore.java:87)
07-08 15:21:57.020 13331-13331/com.jagdiv.android.gogleapplication E/PDFView:     at com.github.barteksc.pdfviewer.DecodingAsyncTask.doInBackground(DecodingAsyncTask.java:59)

There is no support for documents with password. I will add this in next release.

Support for documents with password added in version 1.2.0

where do I enter the password in the code


kll: check for NaN on update with floating point types

Should fix #133

A very simple test for NaN of floating point types could be:
template<typename T, typename C, typename S, typename A>
void kll_sketch<T, C, S, A>::update(const T& value) {
  if ( value != value ) { return; }
  ...
}

This should work for all types even non-numeric types.  Only NaNs are not equal to themselves.
This should eliminate the overhead of testing whether it is a floating-point type and the separation of floating versus non-floating point type methods.
If you look into the source of the built-in libraries that implement isNaN(value) methods, the above is exactly how it is done.

The template metaprogramming is applied at compile time. This way we only eat the runtime cost of that comparison if the type requires it.


[docs] forms.cson needs documenting

There is a wiki page for making and editing forms, but it is empty. As soon as possible, it should be explained in plain language so that LifeTracker is still accessible to non-programmers.

Added to the wiki: https://github.com/cranndarach/lifetracker/wiki/Creating-and-editing-forms


Add separate ha-compute jobs for cloud 6 and 7 with  linuxbridge vxlan.

LGTM +1

the way I understood the card is that the request was not about compute-ha but just a normal ha cluster with vxlan

@dirkmueller thanks , i will change and update PR.


Upgrade gradle, deps and jvm target

Upgrade gradle, deps and jvm target

Sorry Phil, I cant review this - theres too much I'm not familiar with


Add trailing comma when single parameter doesn't fit

Summary
Ensures that the formatter inserts a trailing comma if a single-parameter signature doesn't fit on the line
def f(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa) -> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:
    ...

# Before
def f(
    aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
) -> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:
    ...

# After / Black
def f(
    aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa,
) -> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:
    ...

Open questions
It's unclear if this is the desired behavior. It makes adding new arguments easier, but seems somewhat inconsistent with multiple arguments when they fit on a line when breaking after the ( because we don't add trailing comments in that case (only when it is necessary to put each argument on its own line)
def f(aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, a) -> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:
    ...

# Formatted (without a trailing comma)
def f(
	   aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa, a
) -> aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa:
    ...

Test Plan
cargo test
Interestingly, this seems to reduce the Black compatibility.

zulip: similarity index 0.99702 -> 0.99689
django: similarity index 0.99784 -> 0.99784
warehouse: similarity index 0.99585 -> 0.99584
build: similarity index 0.75623 - >0.75623
transformers: similarity index 0.99470 -> 0.99470
cpython: similarity index 0.75988 -> 0.75988
typeshed: similarity index 0.74853 -> 0.74852

Current dependencies on/for this PR:

main

PR #6410

PR #6439   👈

This comment was auto-generated by Graphite.

Okay, I don't think there's a delibrate logic behind it and I prefer our current solution:
def generate_codepoint_to_names_map(
    emoji_name_maps: Dict[str, Dict[str, Any]]
) -> Dict[str, List[str]]:
    pass

def generate_codepoint_to_names_map(
    emoji_name_maaaaaaaaaaaaaaaaaps: int
) -> Dict[str, List[str]]:
    pass

Black omits the trailing comma for the first case, but not the second?

Oh, how interesting... Thanks for looking into this and including those test cases. I'm getting at least one of those would be considered a bug in Black then. I'm cool with our current solution too.


When catching exceptions in node, attempt to find source map.

I use webpack to generate server.js. If NodeServices catches an error from there, attempt to locate server.js.map and generate a stack trace from it.
This will help with debugging issues.

I found out how to back this directly into the generate webpack file!
http://jlongster.com/Backend-Apps-with-Webpack--Part-I
I essentially just added this into my webpack.config for my server.js file.
module.exports = {
  ...
  plugins: [
    new webpack.BannerPlugin('require("source-map-support").install();', { raw: true, entryOnly: false })
  ],
  devtool: 'source-map'
};

Worked perfectly!

This is great, definitely something worth adding !


Comment out broken link for now

can we do this ?
I saw the failing builds recently

I created the branch day11. So, now the link is ok and build will be ok too :slightly_smiling_face:

sure!
At least I know how to make a comment in markdown : )
On Tue, 14 Aug 2018 at 23:27, Vlad Gregurco<EMAIL_ADDRESS>wrote:

I created the branch day11. So, now the link is ok and build will be ok
too 🙂
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/gregurco/jobeet-tutorial/pull/16#issuecomment-413004514,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADHjxcT_XNM6SJV6PfGd0Fp5vBrjmEgXks5uQzKWgaJpZM4Vy63h
.