Invalid string length + Unknown actor MainThreadTerminal Service

Issue Type: Bug
I keep getting these errors, seems to only be with one workspace and extentions enabled.
I see these errors in logs:
[2022-06-02 14:41:37.170] [renderer5] [error] RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at r (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:7126)
    at Function.serializeRequestArguments (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:17746)
    at v._remoteCall (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:13422)
    at Proxy.L.<computed>.M.charCodeAt.L.<computed> (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:9649)
    at new o (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1712:64318)
    at S._createInstance (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:591:1332)
    at S.createInstance (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:591:773)
    at Br._createExtensionHostCustomers (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1968:7761)
    at vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1968:5199
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

2022-06-02 14:41:37.242] [renderer5] [error] Unknown actor MainThreadTerminalService: Error: Unknown actor MainThreadTerminalService
    at v._doInvokeHandler (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:12971)
    at v._invokeHandler (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:12851)
    at v._receiveRequest (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:11513)
    at v._receiveOneMessage (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:10191)
    at vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:1719:8300
    at m.invoke (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:145)
    at r.deliver (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:2265)
    at o.fire (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:67:1843)
    at u._deliverMessages (vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:19435)
    at vscode-file://vscode-app/usr/share/code/resources/app/out/vs/workbench/workbench.desktop.main.js:83:19180
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:23:40.286Z)
OS version: Linux x64 5.17.5-76051705-generic
Restricted Mode: No

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 3119)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onrasterization: disabled_softwareraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
31.08GB (11.10GB free)

Process Argv
. --crash-reporter-id 1ab019cd-013c-4781-90d0-5dd4d6953623

Screen Reader
no

VM
0%

DESKTOP_SESSION
pop

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
pop

XDG_SESSION_TYPE
x11

Extensions (28)

Extension
Author (truncated)
Version

vscode-django
bat
1.10.0

vscode-svgviewer
css
2.0.0

vscode-eslint
dba
2.2.2

gitlens
eam
12.0.7

EditorConfig
Edi
0.16.4

prettier-vscode
esb
9.5.0

pythonsnippets
frh
1.0.2

unibeautify-vscode
Gla
0.8.2

pytest-snippets
jai
1.0.0

vscode-graphviz
joa
0.0.6

pretty-formatter
mbl
0.2.2

theme-monokai-pro-vscode
mon
1.1.20

vscode-docker
ms-
1.22.0

python
ms-
2022.6.3

vscode-pylance
ms-
2022.6.0

jupyter-keymap
ms-
1.0.0

remote-containers
ms-
0.234.0

test-adapter-converter
ms-
0.1.6

autodocstring
njp
0.6.1

jinjahtml
sam
0.17.0

django-intellisense
sha
0.0.2

code-settings-sync
Sha
3.4.3

code-spell-checker
str
2.2.0

graphviz-interactive-preview
tin
0.3.0

errorlens
use
3.5.1

intellicode-api-usage-examples
Vis
0.1.1

vscodeintellicode
Vis
1.2.21

jinja
who
0.0.8

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vscaat:30438848
vsclangdf:30486550

Looking at those locations in the bundled product, here are where the exceptions are throw.
[2022-06-02 14:41:37.170] [renderer5] [error] RangeError: Invalid string length

JSON.stringify: r (stringify) https://github.com/Microsoft/vscode/blob/bd50a9b0751d4708e0a7b9c78b2a13c34ec6e681/src/vs/workbench/services/extensions/common/rpcProtocol.ts#L82
serializeRequestArguments https://github.com/Microsoft/vscode/blob/bd50a9b0751d4708e0a7b9c78b2a13c34ec6e681/src/vs/workbench/services/extensions/common/rpcProtocol.ts#L755
2022-06-02 14:41:37.242] [renderer5] [error] Unknown actor MainThreadTerminalService: Error: Unknown actor MainThreadTerminalService
https://github.com/Microsoft/vscode/blob/bd50a9b0751d4708e0a7b9c78b2a13c34ec6e681/src/vs/workbench/services/extensions/common/rpcProtocol.ts#L467
@jrieken any idea what could be causing this/hints where to look? AFAIK we're registering MainThreadTerminalService in every extension host type.

/cc @alexdima but AFAIK something when bootstrapping the extension host must go wrong.

Deminified using https://github.com/alexdima/vscode-stack-beautifier
RangeError: Invalid string length  at ./workbench/services/extensions/common/rpcProtocol.ts:82:13  at ./workbench/services/extensions/common/rpcProtocol.ts:755:9  at ./workbench/services/extensions/common/rpcProtocol.ts:490:47  at ./workbench/services/extensions/common/rpcProtocol.ts:253:18  at ./workbench/api/browser/mainThreadTesting.ts:45:14  at ./platform/instantiation/common/instantiationService.ts:110:12  at ./platform/instantiation/common/instantiationService.ts:76:17  at ./workbench/services/extensions/common/extensionHostManager.ts:295:47  at ./workbench/services/extensions/common/extensionHostManager.ts:145:16

The root cause is that MainThreadTesting  tries to send a message to the extension host which is so large that it cannot be represented as a JavaScript string. According to this StackOverflow post, JavaScript strings can be up to 1GB in length, so MainThreadTesting must be trying to send more than 1GB of data in its ctor.
The ctor for MainThreadTesting throws, so that terminates abruptly this loop where extension host named customers are instantiated. I think this then causes the error Unknown actor MainThreadTerminalService.
I will look into wrapping all instantiations with a try/catch such that other named customers are not affected by one failing, but this is a critical error, the extension host can't be in a good state even if one named customer is missing.

1GB feels like an above-average string length.
@easherma-truth what kind of tests do you have in your workspace? I see you have the test-adapter-converter extension, but don't recognize anything that would plug into that.

@connor4312 most of the time I'm on a python/django stack, so mostly pytest. I have test-adapter-converter currently disabled, I think at some point I was playing around with using https://marketplace.visualstudio.com/items?itemName=hbenl.vscode-test-explorer but that is also disabled at the moment.

Am experiencing the same problem on
Mac OS Monterey 12.3.1
VS Code: 1.69.1; also on 1.68.0
Also tried different versions of Node
Bisect shows "This might be a problem with Code"
When VS Code is started, this is printed in the Output terminal:
[2022-07-12 12:10:36.274] [renderer1] [critical] Cannot instantiate named customer: 'MainThreadTesting'
[2022-07-12 12:10:36.274] [renderer1] [critical] {}
[2022-07-12 12:10:36.275] [renderer1] [error] Invalid string length: RangeError: Invalid string length
    at JSON.stringify (<anonymous>)
    at r (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:7166)
    at Function.serializeRequestArguments (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:17633)
    at v._remoteCall (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:13331)
    at Proxy.x.<computed>.M.charCodeAt.x.<computed> (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:9691)
    at new o (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1698:64098)
    at m._createInstance (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:599:1346)
    at m.createInstance (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:599:779)
    at Is._createExtensionHostCustomers (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:7767)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:5199
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2022-07-12 12:10:36.310] [renderer1] [error] Error: Missing proxy instance MainThreadTesting
    at v.assertRegistered (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:9901)
    at Is._createExtensionHostCustomers (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:8265)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:5199
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[2022-07-12 12:10:36.310] [renderer1] [warning] Settings Sync: Accounts are not initialized
[2022-07-12 12:10:36.315] [renderer1] [error] Missing proxy instance MainThreadTesting: Error: Missing proxy instance MainThreadTesting
    at v.assertRegistered (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1705:9901)
    at Is._createExtensionHostCustomers (vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:8265)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1956:5199
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

FWIW, when I open from a workspace I don't get this error, even when working on the same repo. Very odd.

I think this was mitigated, so moving to August.

@connor4312 Any steps to verify this?

No steps really, but in the code the lines that caused this error no longer exist: https://github.com/microsoft/vscode/pull/156834/files#diff-86e89d2d87ac27d3efa349c72b84b0130a5e01592563e6555d68a368beffec0d

marking as verified from code review.


Pin Weasyprint version

Currently, Travis will download the latest version of the Weasyprint Docker image.
This makes builds non-reproducible.
Pin the version used for the Weasyprint Docker image.

Not possible, because latest is the only tag deployed.


feat: max_damage and item_name components support

Two changes added with 1.20.5/6:

max_damage allows to set the maximum durability of an item. Already existing items should keep their durability. Vanilla Mending and repairing with an anvil or a grindstone works, but not merging 2 items in a crafting table.
item_name set the default name of the item, so custom ones can be renamed without losing their default name when resetting it.

This is great, much simpler now that it is supported by upstream. I think we can live with inventory item repair not working.


Add new record types in batch change

Fixes #1248 and #1255.
Changes in this pull request:

Add NAPTR, SRV and NS record types in batch change.
Add support for the above record types through csv.

Tested out locally and the functionality looks good. Just one thing: for NAPTR records, the only validation we have on the Flags input is that it should be less than two characters. I am able to submit flags other than U, S, A, or P (such as "F" or "1"), but when I do, the record change fails with no message. I think if those flags are the only valid ones, we should validate the input to make sure the flag is one of those

Added validation for NAPTR flags in api and converted the text box to dropdown in portal with U, S, A, and P values.

Another thing I noticed is that if you enter a string in the regex field and the string does not begin and end with an "!", the record change passes validation but fails, so I think we should add some input validation for the regex field

Another thing I noticed is that if you enter a string in the regex field and the string does not begin and end with an "!", the record change passes validation but fails, so I think we should add some input validation for the regex field

Looks like regexp should begin and end with '!' or can be empty. Added the validation now.

Could we also enforce the input validation when creating NAPTR records from the zone view? Unless you think that would be better in another PR since this PR is about batch changes

Could we also enforce the input validation when creating NAPTR records from the zone view? Unless you think that would be better in another PR since this PR is about batch changes

I think it would be better to open a separate PR, incase we need to refer that individually in the future. I'll open one soon with the changes.


docs/add deploy on Zeabur tutorial in README file

Zeabur is a platform for deploying services with one click. We can deploy chatgpt-web in Zeabur easily.
Here is a demo: https://chatgpt-web-demo.zeabur.app

文档中引用的图片都无法查看


add "OTA Approval" UIP

add a UIP for letting the user approve updates to apps, rather than auto-merging everything

As a draft, it looks good to me.

the template comment says

Note that an UIP number will be assigned by an editor. When opening a pull request to submit your UIP, please use an abbreviated title in the filename, eip-draft_title_abbrev.md.


Test openrewrite

This PR is to test the OpenRewrite.
Refer to https://docs.openrewrite.org/reference/rewrite-maven-plugin for the maven plugin configurations.
Refer to https://docs.openrewrite.org/reference/recipes/java/spring/ for the Spring rules.
Run mvn rewrite:run to see the rewrite results. Refer to https://docs.openrewrite.org/reference/rewrite-maven-plugin for the goals.

Closing this PR for it's only for demo.


i can't run it

i open this project in intellij and i can't run the program, can you help me please

This is not an intellij project kindly search for solutions on how to migrate netbeans project to intellij project. Thanks.


Exercises in groups have different permissions than other group resou…

…rces

Coverage decreased (-0.03%) to 73.398% when pulling 371e2b7b9e1161c7d0afcef106d391b3002d910e on exercise-permissions into 5d33ced7f56ba63929ada2a133507868b19c3141 on master.


Better Punish Late, Reward Early validationMethod

I found out this closed issue and I really think it should be shipped out-of-the-box (punish on submit or blur, reward on change). Let me explain.
@ciscoheat, this article you reference as the validation method that brings the highest user satisfaction is from 8 years ago, and while the idea is IMO still the best one (reward early, punish late), its implementation is not the best.

If the user is entering the data in the field that was in a valid state, perform the validation after the data entry
If the user is entering the data in the field that was in an invalid state, perform the validation during the data entry

The problem with the validationMethod: 'auto' implementation is that it validates late but doesn't reward early enough.

Validating after the data entry avoids distracting the user with annoying error messages while they're typing (because we assume they know what they're doing and that they're going to type it right).
Once the error message has been shown, why should we keep that error message until the field is completely validated? Why don't we assume that the user has seen the typo/error and as soon as they start correcting the data they know what they're doing just as the previous point?
In case the error is repeated or there's another error, we validate again.

IMO, error messages are annoying. I don't want to get them as soon as I start typing in an empty field because I want the validator to assume I'm smart enough to understand the requirement (punish late).
If I made a typo or misunderstood the requirement, I want to get a clear error message that points to my mistake.
But as soon as I understood my mistake and know how I'm going to correct it, I don't want to see that error message. The validator should assume that I know what I'm doing now and I'm going to type it right (reward early).
Currently, validationMethod: 'auto' is holding my hand until I reach validation in an erroneous field and it's annoying because in my mind the error has already been corrected.
This is used at Google and Apple:
Google: https://workspace.google.com/business/signup/welcome
Apple: https://appstoreconnect.apple.com/login

Hello, I'm sorry for the late response. I see what you mean, but my main design principles are:

Make sure that: (1) the user can figure out what to do, and (2) the user can tell what is going on.
-- Don Norman, "The Design of Everyday Things"

Rule 2 is why they are kept, to avoid problems after a "sequence break", for example if you step away from the computer and come back, you are put back into context.
Not all users are adept at computers, they need hand-holding until things really work (that is, all the errors are actually fixed). The mental model for live feedback cannot be cheated, then users stop trusting it.


[BUGFIX] finally kill self-fulfillment

[x] works
[x] tests
[ ] 4.0, so fork 3.x stable branch?
[ ] 3.x deprecations?

@rwjblue nothing in ember does this anymore, I high doubt users use it. But I can easily make it a warning in 3.x, does that seem good?

Yes, this seems good to me.  I'm ok with a shorter deprecation period also (through the next LTS release)...


MQTT Benchmark

MQTT benchmark should be made to estimate state of NodeJS MQTT broker and it's integration in Mainflux.
Some of the tools:

https://github.com/takanorig/mqtt-bench
https://github.com/hareeqi/mqtt-benchmark
https://github.com/krylovsk/mqtt-benchmark

It would be interesting to follow free RAM on the instance and it's behavior in dependance of connected clients.
Two thing to take care about:

Messages per second
Number of simultaneously connected clients

Various strategies can be tried, as brokers do not behave the same if there is many publishers and one subscriber (all messages go on one topic, firehose) and when there are many publishers and many subscribers (messages spread over several topics).
Some ideas:

https://github.com/surgemq/surgemq#performance
https://github.com/surgemq/surgemq/tree/master/benchmark

I'd like to suggest going away from the notion of "messages per second" and using the idea of PUBLISH messages (a specific meaning in MQTT ) per second.
Also related is the number of SUBSCRIBE messages per second.  I have seen brokers perform poorly in this area as the complexity of the subscription topics requested went up.

Depends on #378 and new MQTT broker.

Back when I was doing load testing I found this article:
https://dzone.com/articles/load-testing-of-mqtt-servers-using-java-maven-and
They created a Gatling MQTT plugin that I felt like was sufficient. It seemed to cover both points Messages per second and Number of simultaneously connected clients.
If you wanted to keep using Gatling, this might be an option!
Link to plugin: https://github.com/thingsboard/gatling-mqtt

@mfinley3 yes - Gatlig would be great choice!
Our load tests fro HTTP and WS are already using Gatling: https://github.com/mainflux/mainflux/tree/master/load-test - so you can add them there.
I think @nmarcetic used so far Malaria and mqtt-stresser for stress tests and had over 100k mps on a single instance of MQTT broker on his PC.

@drasko Can this one be closed, due to #817 ?

I propose that we keep it until VerneMQ is fully deployed and all measurents are done on typical Kubernetes setup and published here and on our web site.

Closed via https://github.com/mainflux/benchmark/pull/6


Issues with peer dependencies with NextJS 14.0.4

[x] I have searched the Issues to see if this bug has already been reported
[x] I have tested the latest version

Steps to reproduce

Install flowbite-react (0.7.2) and nextjs (14.0.4).
The warning Issues with peer dependencies found appears.

Current behavior
This Is not a problem, but it would be good if someone could update the flowbite-react dependencies to avoid the unmet peer dependency warning.
Expected behavior
To not get the unmet peer dependency warning.
Context
This is the terminal warning:

We're aware of this but it isn't really pertinent to the library


Google Hybrid Map tiles won't load in OpenLayers when centered on certain position

Since the Google Maps API update to V3.19 (also doesn't work in V3.20) our maps have not been loading to their initial state, centered over the Gulf of Mexico.
When the center location is: center: new OpenLayers.LonLat(-90, 25) it doesn't render, but OpenLayers.LonLat(-91, 25) works fine. Any 90 lon or 0 lat fails.
Example:

var map;
$(document).ready(function () {
    map = new OpenLayers.Map('olmap', {
        projection: 'EPSG:3857',
        layers: [
        new OpenLayers.Layer.Google(
            "Google Hybrid", {
            type: google.maps.MapTypeId.HYBRID,
            numZoomLevels: 20
        })],
        center: new OpenLayers.LonLat(-90, 25) //change to -91 and it works.
            .transform('EPSG:4326', 'EPSG:3857'),
        zoom: 4
    });
});

See http://jsfiddle.net/mickel1138/cuz00fg9/ for your experimenting pleasure.

A latitude of -90 cannot be transformed to Web Mercator, because that lies in I finite space. For Web Mercator, you cannot use latitudes beyond 85 or 86 degrees reliably.
Closing because this is an application/configuration issue. If this configuration worked in the past, it worked by chance only.

Also note that OpenLayers.LonLat takes the longitude as first and the latitude as 2nd argument.

I agree that a latitude of near 90 can be problematic, but the latitude in the example is 25, and the longitude is 90.

Reopening. You wrote latitude of 90, but meant longitude.
If you can provide a pull request with a fix, we'll gladly merge. But supporting the ever changing Google Maps API has been a pain so it's very unlikely that this will be fixed by one of the core devs.

Sorry, yes, I mixed them up earlier (corrected now) although, the example was correct.

I do believe this is a major bug, using 0 or 90 for either lon or lat causes the map not to render. Moving the map will make it render however.


Cayo Good Counter Feedback

Couple call outs:

Your Gold Bag states it fills up 0.7 of a bag when the true number is 0.66
Same with Cash, instead of 0.3 it should be 0.25.  If it's just a display issue, then change the displayed decimal value to show 2 decimal points so the user can see an accurate value
Some of the math doesn't add up correctly.  Here's one case:
No Hard Mode
Pink Diamond = $1,300,000
Gold Stacks 3 (Two full bags) = $1,000,000 ($500,000 x 2)
Total should be = $2,300,000 Max Possible Loot Value
Also you should incorporate a simple line that deducts the consistent 12% in fees so players know what they are truly getting
If you want to get fancy, you can add another line asking the user if it is their first time doing the heist as there is no "Fencing Fee" the first time the user completes the Heist

Your Gold Bag states it fills up 0.7 of a bag when the true number is 0.66

yes, it is to simplify everything, 0.66 may be confusing for ppl because in-game bar has accuracy 0.05 % of the bag.

Same with Cash, instead of 0.3 it should be 0.25.

Cash is exactly 0.25 https://michald96.github.io/Perico-heist-goods-counter/data/targets.json
and it is good idea to change display to 2 decimal points

Some of the math doesn't add up correctly.

The difference is less than 4K $ and it is because i use average value of the items. Evey item has minimum and maximum price:
Gold = $333k to $329k
Coke = $225k to $220k
Arts = $200k to $175k
Weed = $150k to $145k
Cash = $95k to $90k

Also you should incorporate a simple line that deducts the consistent 12% in fees so players know what they are truly getting

I have that in plans!

If you want to get fancy, you can add another line asking the user if it is their first time doing the heist as there is no "Fencing Fee" the first time the user completes the Heist

I will show it as "potential take" then "fencing fee" and "max possible final cut"

Added / fixed most things from your suggestions 😉


Add clean-up accounts procedure

Description of changes:  There is no API to clean up created accounts in AWS Organization. Users have to follow several steps manually. I add these steps in README.md so users know all steps and where to find detailed documentation.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Close as it's preferred to be in the example repo.
Created PR https://github.com/aws-samples/aws-bootstrap-kit-examples/pull/18 that has addressed the comment from @flochaz  .


[MRG] Add info where certain BV headers might come from

Based on https://github.com/mne-tools/mne-python/issues/8432#issuecomment-720903265

would it make sense to cover this with a test?

would it make sense to cover this with a test?

It's already covered, this was added via https://github.com/mne-tools/mne-python/pull/8434
We just weren't sure where those weird files would actually come from, but now @arthurlgk told us that they used PyCorder to obtain these headers.
So this PR is really just a small clarification to remind us in the future which software might produce files that require special handling.

thx @hoechenberger
I had read too quickly...


test-azure-win2012r2-x64-1 workspace needs cleanup

See: https://ci.adoptopenjdk.net/job/Test_openjdk8_j9_sanity.openjdk_x86-32_windows/295/console
[Pipeline] checkout
No credentials specified
Cloning the remote Git repository
Cloning repository https://github.com/AdoptOpenJDK/openjdk-tests.git
ERROR: Failed to clean the workspace
jenkins.util.io.CompositeIOException: Unable to delete 'C:\Users\jenkins\workspace\Test_openjdk8_j9_sanity.openjdk_x86-32_windows\openjdk-tests'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.
	at jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:90)
	at hudson.Util.deleteContentsRecursive(Util.java:261)
	at hudson.Util.deleteContentsRecursive(Util.java:250)
	at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:742)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)
	at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)
	at hudson.remoting.UserRequest.perform(UserRequest.java:211)
	at hudson.remoting.UserRequest.perform(UserRequest.java:54)
	at hudson.remoting.Request$2.run(Request.java:369)

Seems a regular problem, we need to try to understand why the cleanup does not occur? or perhaps make the above cleanup first before trying to clone maybe?

ref: #1396
Done - This is a known issue (see the referenced one) - there's a leftover java.exe process running within the openjdk-tests folder, so it can't be deleted. I propose we run SXA-ProcessCheck after each test run, for the machine the tests have run on. This would theoretically stop any non-Jenkins-Agent processes, allowed the next test run to cleanup the workspace properly. (ping @sxa )


chore: added plugins to root babel.config.js

Overview
PR Checklist

~[ ] Related to designs:~
[x] Related to JIRA ticket: GM-121
[x] I have run this code to verify it works
[x] This PR includes unit tests for the code change

Description
Split off from #1070: lets us use Emotion features in our Storybook components such as interpolated component names.

🚀 Styleguide deploy preview ready!https://5f96e8a29614992924c77760--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://5f984f6e5f4479bc0742d16f--gamut-preview.netlify.appDeploy Logs


Emissive blocks don't work properly under Godot 4.1.2

Not sure if this worked before or not but I'm just creating an issue to document it

Here's how it looks in magicavoxel btw
(and yes, I've reloaded the scene a number of times too)

If that is a MagicaVoxel Render, it is simply impossible to port those materials anywhere else. Just the way MagicaVoxel works.


Parallelize deterministic WolframModel on GPU

The problem
This is similar to #155, but for GPUs rather than CPUs. We need both because some users might not have access to a GPU, especially if we don't support all of them.
This issue specifically is for a parallelization supporting a specific "EventOrderingFunction", i.e., it should not change the output of WolframModel in any way. There is another issue (TODO: add issue) for parallelizing undefined-order evolution.
Additional context
Feel free to create subtasks for different GPU frameworks.

If this is C++, it maybe possible to turn this to CUDA code.  Could you kick towards the right place in the codebase?

I can see a few "EventOrderingFunction" in the .wlt and in .m. but not in C++.  And then there is libSetReplace, which seem like a candidate to turn to CUDA.  But it is not clear what exactly needs parallelization / GPU.

@dchichkov, yes, libSetReplace is the "LowLevel" C++ implementation of the Wolfram model evolution. "EventOrderingFunction" corresponds to the OrderingSpec in the C++ code. Although I think it will probably be easier to start with #354, which does not put any constraints on the event order.
The question is whether we can run the entire Wolfram model evolution on a GPU. This starts with Set::replace,  and the heaviest code is in the Matcher class. The basic algorithm is briefly discussed here.
There is a lot to explain though (and I don't know much about GPU programming myself, so I'm not quite sure what's possible). If you'd like to help, it would be great if you join our Discord server. We are also hosting a Q&A at 10 AM Pacific Time tomorrow (10/10). If you can join, we can discuss it there (or any other time after that).
And thanks for your interest!

@maxitg  Nice.  Thank you for kicking me towards this code.  I'll look.
Just in case, if you are interested in skimming over GPU programming -
https://developer.nvidia.com/blog/even-easier-introduction-cuda/
There's also a higher level GPU library that supports some graph operations, is open source and has C++ and Python APIs  -
https://github.com/rapidsai/cugraph
Maybe it could be used as a framework?  The "Subgraph Extraction" might be a good starting point?  Its code is here - https://github.com/rapidsai/cugraph/blob/branch-0.16/cpp/src/community/extract_subgraph_by_vertex.cu
There is also layout/visualization there -  "Force Atlas 2".


tests: do not test dependent formulae with :all bottles on Linux

See:
https://github.com/Homebrew/homebrew-core/pull/80242
This prevents endless builds, and tests on formulae that are
not yet ready for Linux

I think you would have hit the same issue with ARM bottling, but as all: bottles were introduced later, this was not an issue.

Imma test this in:
https://github.com/Homebrew/homebrew-core/pull/80354/

Thanks. I retriggered the ncurses build, and will dispatch a job for alsa-lib, which is the formula which was impacted too.

Nothing really changed:
https://github.com/Homebrew/homebrew-core/runs/2959377767?check_suite_focus=true
Huh

Weird. I tested the change locally in a docker container and it worked.
I think I ran something like this to test it:
docker run -it ghcr.io/homebrew/ubuntu16.04:master
git remote set-url origin https://github.com/Homebrew/homebrew-core
brew update
export HOMEBREW_FORCE_HOMEBREW_ON_LINUX=1
export HOMEBREW_SKIP_UNBOTTLED_LINUX_TESTS=1
brew test-bot --only-formulae alsa-lib

@dawidd6 for typescript we need to add the same check somewhere else: https://github.com/Homebrew/homebrew-test-bot/blob/master/lib/tests/formulae.rb#L618-L627
I disabled all builds for dependents, but not for the main tested formula.
I am still trying to understand what is going on with the other builds on CI, as my fix seems to have no effect.


Crashing after running second query in a row.

I'm using the following code to query a mysql table and it works on the first api call using express but as soon as I try another call it crashes. I'm running the latest mysqljs version from this repository.
app.get('/tracks', function (req, res) {
    connection.connect();

    connection.query('SELECT * FROM tracks_posted LIMIT 0, 10', function (error, results, fields) {
      if (error) throw error;
      res.send(results)
    });

    connection.end();
});

This is the error code I'm getting:
events.js:167
[0]       throw er; // Unhandled 'error' event
[0]       ^
[0]
[0] Error: Cannot enqueue Handshake after invoking quit.
[0]     at Protocol._validateEnqueue (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:203:16)
[0]     at Protocol._enqueue (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:138:13)
[0]     at Protocol.handshake (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:51:23)
[0]     at Connection.connect (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/Connection.js:118:18)
[0]     at /Users/alexanderhoerl/Developer/react-soundcloud-clone/server.js:18:16
[0]     at Layer.handle [as handle_request] (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/express/lib/router/layer.js:95:5)
[0]     at next (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/express/lib/router/route.js:137:13)
[0]     at Route.dispatch (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/express/lib/router/route.js:112:3)
[0]     at Layer.handle [as handle_request] (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/express/lib/router/layer.js:95:5)
[0]     at /Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/express/lib/router/index.js:281:22
[0] Emitted 'error' event at:
[0]     at Connection._handleProtocolError (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/Connection.js:425:8)
[0]     at Protocol.emit (events.js:182:13)
[0]     at Protocol._delegateError (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:390:10)
[0]     at Handshake.<anonymous> (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:220:10)
[0]     at Handshake.emit (events.js:182:13)
[0]     at Handshake.Sequence.end (/Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/sequences/Sequence.js:78:12)
[0]     at /Users/alexanderhoerl/Developer/react-soundcloud-clone/node_modules/mysql/lib/protocol/Protocol.js:224:14
[0]     at process._tickCallback (internal/process/next_tick.js:61:11)

Hi @AlexanderProd based on the provided code and error, you're trying to .connect() on a connection object that has already been ended. You cannot re-open a connection once it is closed. You need to create a new connection object.
Simplified example:
app.get('/tracks', function (req, res) {
    var connection = mysql.createConnection(/* your config */);

    connection.query('SELECT * FROM tracks_posted LIMIT 0, 10', function (error, results, fields) {
      if (error) throw error;
      res.send(results)
    });

    connection.end();
});


Rename Knob to CircularKnob

In Xcode, running the preview fails because type alias Knob references itself.
In Xcode 11.4 beta running the preview fails because of a circular reference.
Renaming the project to CircularKnob instead of Knob resolves this issue.

Still an issue with Xcode Version 11.4 (11E146) GM

Thank you! For some reason the preview still doesn't work on my machine, but this doesn't seem to make things worse 🙃.
I'll merge it and look into this further at another time.


Error 0x8007007b installing Debian package <IP_ADDRESS>

Please fill out the below information:

Your Windows build number:  Version 10.0.17763.503

What you're doing and what's happening:  Installing the Debian <IP_ADDRESS> package with WSL enabled

Downloaded the installation package from https://aka.ms/wsl-debian-gnulinux as per https://docs.microsoft.com/en-us/windows/wsl/install-manual
In powershell, start .\DebianGNULinux_1-1-3-0_x64__76v4gfsz19hv4.Appx
Get pretty window with "Launch" button and click that.
Get a command window with this in it:

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8007007b
Error: 0x8007007b The filename, directory name, or volume label syntax is incorrect.

Press any key to continue...

What's wrong / what should be happening instead: It should install.

For WSL launch issues, here are the detailed logs: logs.zip

WSL is enabled:
PS C:\WINDOWS\system32> Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Windows-Subsystem-Linux

FeatureName      : Microsoft-Windows-Subsystem-Linux
DisplayName      : Windows Subsystem for Linux
Description      : Provides services and environments for running native user-mode Linux shells and tools on Windows.
RestartRequired  : Possible
State            : Enabled
CustomProperties :
                   ServerComponent\Description : Provides services and environments for running native user-mode Linux
                   shells and tools on Windows.
                   ServerComponent\DisplayName : Windows Subsystem for Linux
                   ServerComponent\Id : 1033
                   ServerComponent\Type : Feature
                   ServerComponent\UniqueName : Microsoft-Windows-Subsystem-Linux
                   ServerComponent\Deploys\Update\Name : Microsoft-Windows-Subsystem-Linux

I used the Windows Store to install it (after uninstalling whatever I had with powershell) and that just worked.

I have encountered the same problem when I installed it in D: drive by using Windows Store.By looking at Microsoft's installation instructions, I found that WSL and Linux must be installed on the same drive. After changing the installation location to C, the initialization is successful. Hope useful to you.


Change the command Prompt from $ to ₿

just change the $ in the Bash to ₿ for obvious reasons.

lol yeah.
$ is the Linux convention and not related to the USD and also the sign to reference variables in bash.
Here is how to modify manually: https://stadicus.github.io/RaspiBolt/raspibolt_62_commandline.html
I guess a PR to implement would be welcome.

Hey @rootzoll !
Shouldn't this PR be closed?

Closing as solved on v1.7.2.


git guardian github action bug

Environment

ggshield version: latest
Operating system (Linux, macOS, Windows): windows
Python version: 3.9

Describe the bug
Getting this error when I run git guardian in github action workflow
Permission denied: '/github/home/.cache'
Steps to reproduce:

copy this github action code at https://dashboard.gitguardian.com/workspace/335609/settings/workspace/integrations/github_actions into github action workflow yml file
Commit/push to dev branch
observe github action

Actual result:
Permission denied: '/github/home/.cache'
Expected result:
result showing scan and pass/fail for any vulnerability
If applicable, add logs or screenshots to help explain your problem.

@CharlesB2 @agateau-gg

Hello @karkir0003,
Thank you for reporting this behavior. In order for us to move forward, could you provide us with :

A link to the failing action run ? (If your repo is public)
Alternatively, an extract from the logs of the GitHub action ?
Do you know which ggshield Docker image was used ? Would you have a tag in the logs ?

Thanks for your answer.
From what I can see, the action runs correctly.
The message you see is a log message that warns about insufficient rights to cache the latest version of ggshield available. This is used to warn the user if they use an old version of ggshield, but it does not affect the run.
Note that following #450 : we re-introduce the success message when no secrets are found. This should make the output more explicit.

I am closing this issue as we improved the logs and re-introduced an explicit success message.
Thanks for your feedbacks.


NOS News, new extension.

NOS News, new extension.
Description

Added an new extension to display content from the biggest Dutch news site. Which can be found here: https://nos.nl/. Looking to improve this in future versions with more news categories than only the latest news.
Type of change

New extension

Screencast
Screencast can be found here: https://youtu.be/8RkD-vOKlpU
Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast

Small note, I used Dutch for some properties as it made more sense to me as the content from the news website is also in Dutch. For example, the time when the article was added.
If this needs to be changed I am happy to do so.

@RSO great! Thanks, I will just quickly update the naming on the action panel.


Make sure emitter values are emitted within the ngZone

This resolves an issue where changes to an inspected app that are a result of events emitted from Augury (as opposed to the same events emitted naturally through the app), do not result in the component tree being updated.
resolves #752
@vanessayuenn FYI.

resolves #752

@igor-ka Please approve. Release incoming.

Will do.
On Oct 25, 2016, 4:06 PM +0200, Igor Kamenetsky<EMAIL_ADDRESS>wrote:

@igor-ka commented on this pull request.
@stevenkampen (https://github.com/stevenkampen) the code makes perfect sense.
Please create a github issues describing the problem we are addressing, and link it to this PR for everyone's reference. I will give it the approval after.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub (https://github.com/rangle/augury/pull/751#pullrequestreview-5657418), or mute the thread (https://github.com/notifications/unsubscribe-auth/AA22yxCYmX6Ng9FiJ53u2QyI8xE9ZNPlks5q3gz6gaJpZM4KfuTw).


Optionally export JUnit reports

Add JUnit export from ReTestItems to RAITest
Beef up ConcurrentTestSet with a bit more generic and powerful RAITestSet
Fix precompilation if no default RAI config

Test PR: https://github.com/RelationalAI/raicode/pull/13703
To Do:

[x] Decide on/implement how to name/place files and whether to just use the ReTestItems envs there (probably not?)
[x] Contribute the junit_record! method back to ReTestItems
[x] Confirm this actually works (the guts are here, but haven't gotten it fully running yet)

There's still some trailing debug code here (the failures), and a couple minor mysteries left, but I think it's overall ready for review


Dev/xdoctest

Builds on #493
Adds declaration of xdoctest as a test dependency and adds the flags to tox. I also added a second simple doctest  to spatial_search_params.

I've got xdoctest installed and running alongside pytests, but currently it is unable to find the doctests. The reason is because the tox entry for [testenv:test-rgd-client] does a changedir to changedir = rgd-client/tests, so when pytest does its discovery for tests it only looks in that CWD and never sees the source directory. For xdoctest to discover the doctests the source for the module needs to either be in the CWD pytest is run in, or passed to pytest.
Often I just run pytest in the root of the my repo, so this isn't a problem, but there are instances where I'm testing wheels where it is more desireable to run pytest in a sandboxed directory (e.g. I do this in kwimage).
I have a semi-hacky way of handling this case at the moment: https://gitlab.kitware.com/computer-vision/kwimage/-/blob/master/.gitlab-ci.yml#L183 At a high level, the CI has already built the wheel and pip installed the wheel, so I don't want to run pytest in the root, because I want it to pick up the contents of the installed wheel, not the source. So I cd into an empty sandbox directory, and run pytest and point at ../tests (because the test dir is also in the root). Then to give it the path to the installed source I want to test (because it needs to parse the doctests from that). I use $(python -c "import ubelt; print(ubelt.modname_to_modpath('kwimage'))"), which returns the path to where the wheel is installed.
I'm not sure how this is best handled in this case. If the commands in the "commands" section of the tox file are just run in a bash shell, then the path to the installed version of "rgd_client" could be obtaine via:
$(python -c "import rgd_client, os; print(os.path.dirname(rgd_client.__file__))")

which has the side effect of importing the module we want to test, or which is able to obtain the path statically without importing the module
$(python -c "import ubelt; print(ubelt.modname_to_modpath('rgd_client'))")

which works via pathlib and is roughly equivalent to this code:
$(python -c "import pkgutil, os; print(os.path.dirname(pkgutil.find_loader('rgd_client').get_filename()))")

It also might be fine to pass it "../rgd_client", but I believe xdoctest will attempt to import that module from that location in order to test it (I would have to double check on that to be sure), so that might cause issues --- especially with coverage --- if we are really trying to test the installed version.

Just realized my changes weren't added here. Heres the diff:
diff --git a/requirements.txt b/requirements.txt
index c52e36d..ad965c3 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -6,6 +6,5 @@ pytest-factoryboy
 pytest-mock
 pytest-cov
 pytest-memprof
-xdoctest >= 0.15.6
 -e ./django-rgd
 -e ./testing-utils
diff --git a/tox.ini b/tox.ini
index e2c8df9..4fbea6d 100644
--- a/tox.ini
+++ b/tox.ini
@@ -125,6 +125,7 @@ commands =
 changedir = rgd-client/tests
 deps =
     -r requirements.txt
+    xdoctest>=0.15.6
     -e ./django-rgd
     -e ./django-rgd-3d[worker]
     -e ./django-rgd-fmv[worker]
@@ -133,6 +134,7 @@ deps =
     -e ./rgd-client[dev]
 commands =
     pytest {posargs}
+    python -m xdoctest ../rgd_client
     # coverage html -d {toxworkdir}/htmlcov/django-rgd-client
     # coverage xml -o {toxworkdir}/coverage.xml

@@ -171,7 +173,7 @@ ignore =

 [pytest]
 DJANGO_SETTINGS_MODULE = test_project.settings
-addopts = --strict-markers --showlocals --verbose --durations=0 --xdoctest
+addopts = --strict-markers --showlocals --verbose --durations=0
 filterwarnings =
     ignore:.*default_app_config*.:django.utils.deprecation.RemovedInDjango41Warning
     ignore::DeprecationWarning:minio

It very well could be the case that it does not make sense here. Hence why I put it in this PR instead of the previous one.

the point of doctstrings like these are to make sure the API itself is tested in a way in which the user might use it

That is a point of docstrings / doctests, another is reducing the overhead of writing tests, so devs actually write them. Pytest with all the fixtures and magic can be a real pain. Personally, just switching between files (let alone files in different directories) is enough overhead to inhibit me from writing a test, especially a small one like the one that could have prevented the error in #493.  Coupling the test with the code means that its easier to change the tests for pieces that are subject to change.
That being said, not everything is suitable for a doctest, but its usually eaiser to migrate an existing doctest to a separate unit test than it is to deal with projects that don't have tests. My main philosophy on the subject is to lower the barrier to entry for tests as much as possible.
On the topic of fixtures: Where does live_server come from? in rgd-client/tests/conftest.py? I greped for it but found no other instance. If there was a way to make a "demo" or "dummy" RgdcSession, then doctests would start making a more sense.

another is reducing the overhead of writing tests, so devs actually write them.

Fair point... considering the fact that we have all of 3 tests, we could use as much help as we can get writing more.
I'll have to continue giving this some thought so that we do this in a way that makes the most sense for this project. Though I still feel strongly that we shouldn't fragment our tests across pytest modules and docstrings in this case.

Where does live_server come from?

live_server is a fixture from pytest-django: https://pytest-django.readthedocs.io/en/latest/helpers.html#live-server
Spinning this up more than once (once for our pytest modules and once for xdoctest) would be too expensive (I'm assuming this would have to happen a second time in a new context for xdoctest)

Ugg, fixtures are such a rabbit hole. Is it so wrong to want to just open up IPython and have the ability to create an instance of one?
I looked up the definition for "live_server", which has it's own argument request, which has absolutely no way to easilly see where that is coming from or what it's attributes might be.
If I haven't mentioned, I really don't like fixtures.
I'm not advocating for this approach, more just putting it out there as a dicussion point, but if I was testing this, my inclination would be to have a "demo.py" file that could prop up a demo "live_server". The function would be memoized so it wouldn't be executed more than once, and then instead of using magic fixtures, I would call the function to get the instance. That way a new dev could trace back where everything came from. The atexit module could be used for handling shutdown logic. This doesn't quite work, but this is the idea:
import ubelt as ub

@ub.memoize
def demo_live_server():
    from pytest_django import live_server_helper
    import os
    # Source code contains no indication of what request is, ignoring it
    # request.config.getvalue("liveserver")

    # HACKS:
    # probably need to setup some background database?
    # information in rgd_testing_utils/settings.py seems important
    import sys
    sys.path.append('/home/joncrall/code/ResonantGeoData/testing-utils/')
    sys.path.append('/home/joncrall/code/ResonantGeoData/rgd-client/tests/')
    os.environ['DJANGO_SETTINGS_MODULE'] = 'test_project.settings'
    # from django.core.management import execute_from_command_line
    # Need to do some sort of execute_from_command_line?

    addr = os.getenv(
        "DJANGO_LIVE_TEST_SERVER_ADDRESS"
    ) or "localhost"

    server = live_server_helper.LiveServer(addr)
    import atexit
    atexit.register(server.stop)

Of course it's possible that I'm not considering all the complexities of network programming, and in that case fixtures are really great once you get used to them. Still, I wish they were easier to trace.

@Erotemic pytest is a pretty popular test framework for Python (7.7k stars on GitHub). There is some magic to be learned, and I'd suggest reviewing some of the basic docs ( https://docs.pytest.org/en/latest/explanation/fixtures.html ) and trying to contribute some RGD functionality using the existing test infrastructure (using pytest-django, etc.). In particular, note that running pytest --fixtures lists all of the available fixtures for a given test environment.
If it truly looks like pytest is not a good fit for RGD, then perhaps it's worth opening a separate issue to discuss. However, I'm concerned that this PR is the start of a schism, where some developers will write tests with pytest and others write them with xdoctest. That seems unhealthy for RGD as a collaborative effort.

I don't like the idea of splitting our tests across both pytest and xdoctest. It's somewhat confusing to have them split up, and how/where to write tests could become ambiguous. I don't see a compelling reason not to just use pytest for any unit tests. It's a little more effort to write pytest tests, but it allows for much more comprehensive tests, sometimes without much boiler plate code thanks to fixtures, parametrization, etc. At the end of the day, it's our responsibility to ensure that tests are added alongside any code that we think needs them, and I think pytest provides a reasonably low barrier to entry.

I think doctest makes sense if you were wanting to write example code in your docstrings anyway. It should not be viewed as an alternative unit testing library to pytest, but rather as something that validates correctness of docstrings.
Judging by the "Documentation" section of the current README in this repository, it seems like the documentation plan for RGD isn't even fleshed out yet. If that's the case, I think this addition is premature.

@brianhelba I'm familiar with pytest. XDoctest itself is a pytest plugin, and is the main way in which it is used. I didn't mean to suggest that pytest isn't a good fit. Pytest is the de-facto Python tester for good reason. My only gripe with it is that fixtures are too opaque and magical. Specifically: (1) using the name of an argument to define how things are connected is far too implicit for my taste (2) there is no good way to instantiate one in a standalone way, it requires that you are already running a pytest session, which is really my main problem with it.
I don't think there is any risk of a schism. I'm more than happy to let this PR die, but I do think the discussion is intersting, and I'd like to continue it.
@AlmightyYakob

I don't see a compelling reason not to just use pytest for any unit tests. It's a little more effort to write pytest tests

Yet, developer's don't make that effort. Consider the example of order_datetimes. It is a non-public facing function that
may get refactored away. If a small test is coupled with the function, you detect or prevent bugs like the one in #493 and if you refactor it, you don't have to worry about finding and deleting the associated unit test somewhere else. It's generally code you would write anyway as you are developing the function, so as long as it's not too cumbersome, I don't see any reason to not just stick it in the docstring as a doctest and get a bit of extra coverage "for free".
That being said, you could also just stick it in a unit test as well, but I do think having _some tests coupled with the function is a more powerful idea than people give it credit for. It makes it much easier to move functions between libraries/projects and ensure they are tested.
Again, it's not a replacement for pytest, but it is supplemental.

It's somewhat confusing to have them split up, and how/where to write tests could become ambiguous.

As long as you are executing both, it doesn't really matter at the end of the day, and it becomes a question of style and opinion. My opinion is that you should try to show a developer how to use your function in the function itself, and that should be done by giving them code that is easy to copy/paste into IPython and have it execute. Once they have executing code, they can play with it.
When it comes to writing robust tests cases with parameterization (a fixture that doesn't bother me because it's clear how things are connected in the code itself), then separate unit tests and system tests should live in a sepaarate file, if only for the reason that they would bring too much clutter into the code itself.
For instance in ubelt, every public function has a doctest, but that is not enough to achieve 100% coverage. There is an additional "tests" folder containing unit tests for pytest. While I can be somewhat lax with just how much clutter I'll allow in a doctest, the full comprehensive test suite does belong in a seperate unit test file. Often times, I'll start out writing the unit test in a doctest, but if it grows to large I can move it out of the file. This pattern lowers the barrier to writing the most minimal test, and once you have a minimal test, it's a lot easier to write the comprehensive one. (But even if you don't you at least you know there is some path through your code that doesn't error).
@zachmullen

It should not be viewed as an alternative unit testing library to pytest,

Yes. You generally want to make unit tests more robust than something you would put in a doctest.

but rather as something that validates correctness of docstrings

I disagree there. Doctests sever as an example that demonstrates how to execute the code. One of the things I like most about them is that they provide an entrypoint into the code. They define all of the inputs needed to call a function, so among other things - that allows a developer to drop into IPython, copy over the demo data, and start playing with the internal logic of the function.
Again, in the context of this project requiring that a server be available to interact with, it might not make sense to execute doctests in a CI Suite, but if you had some rgd_client.demo module that could stand up a backend test server, you could add something like this to the public facing API
class Rgdc:
    """
    Example:
        >>> from rgd_client
        >>> api_url = rgd_client.demo.ensure_demo_server()
        >>> self = Rgdc(api_url)
        >>> query = {
        >>>     "type": "Polygon",
        >>>     "coordinates": [
        >>>         [
        >>>             [-81.7745, 33.1346],
        >>>             [-81.7746, 33.1437],
        >>>             [-81.7744, 33.1437],
        >>>             [-81.7666, 33.1436],
        >>>             [-81.7745, 33.1346]
        >>>         ]
        >>>     ]
        >>> }
        >>> predicate = 'intersects'
        >>> acquired = (
        >>>     datetime.fromisoformat('2101-01-01T00:10:00'),
        >>>     datetime.fromisoformat('2101-01-01T00:23:00')
        >>> )
        >>> results = self.search(query=query, predicate=predicate, acquired=acquired)
        >>> for result in results:
        >>>     print('result = {!r}'.format(result))
    """

So then the API docs would provide users with an executable example that demonstrates how to use the code. And if you have these, you should execute them in your test suite (as you said to validate the correctness of the example in your docstring). But even though it is not a robust unit test, just blindly executing a code path and not seeing (or seeing) a crash is useful  diagnostic information that I would argue you should consider as part of your test suite.
(I also wonder if hesitence towards doctests has to do with how github and some editors don't higlight them: https://github.com/rouge-ruby/rouge/issues/920)

is this PR stalled @Erotemic @banesullivan

It is my opinion that the introduction of doctest/xdoctest adds too much complexity and fragmentation to our tests. Additionally, because we are working with Django and the burden of spinning up the app/web server during testing, it would be too much of an obligation to maintain a separate testing infrastructure for xdoctest when we have a great solution from pytest-django.
Further, it is not (yet) our goal to provide meaningful docstrings as most of what we are providing here is a web API and not a Python API intended for direct use (IMO, doctests in our Django models/utils are frivolous). We are still working out what kinds of documentation we will offer, and unfortunately, the timing isn't good for this. With that said, there could be a place for this specifically for the Python client down the road (where docstrings do make sense).
For these reasons, I am closing the PR until further notice. Thank you, @Erotemic, for provoking this discussion. There's still a lot left unaddressed here; hopefully, we can take on some of these challenges later on when the app is more stable, and we have a clear roadmap for our documentation/testing.


docs: Table on installation page badly formatted

https://pebbletemplates.io/wiki/guide/installation/

Not sure what's the problem. Feel free to submit a PR if needed. Installation guide page is here https://github.com/PebbleTemplates/pebble/blob/master/docs/src/orchid/resources/wiki/guide/installation.md

https://pebbletemplates.io/wiki/guide/installation/ looks fine now.


[Performance Optimization] The huge performance drop due to the method of getBlockIdsByPartitionId

Background
I found when getting shuffle result, the flame graph show the method of getBlockIdsByPartitionId occupy too much time.

But i found the default bitmapNum is 1, and the conf of spark.rss.client.bitmap.splitNum looks abandoned in future.

@colinmjj

The performance problem of getBlockIdsByPartitionId is a known issue.
With current design, blockId should be stored in shuffle server to support features like block filter, data validation, etc.
Here is the challenge about how to store blockId in shuffle server, and we need consider how to reduce memory cost & have better performance.
The current implementation is target to reduce memory cost in Shuffle Server, but have poor performance when get blockIds, otherwise, GC will be another problem.
I think there should be a lot of works to improve this issue, maybe new design about how to do the data validation & how to store blockIds.

Got it. If we have the better design on this, i think it will achieve better performance.


Configuring Closed Federation and Hybrid

Can additional documentation be included to show how to configure hybrid but leave closed federation and manage through allowed/blocked lists? The above command enables partner discovery, which will open a previously closed federation environment to an open federation. Having the closed federation with hybrid scenario documented would be great.

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

ID: 18231e84-6544-85f9-802e-195f5272aeab
Version Independent ID: 7d3161d7-9e00-c8f0-4ee7-acce85f469d8
Content: Configure Skype for Business hybrid
Content Source: Skype/SfbHybrid/hybrid/configure-federation-with-skype-for-business-online.md
Product: skype-for-business-itpro
GitHub Login: @CarolynRowe
Microsoft Alias: crowe

@officedocsbot assign @scanum

Hi @JeffBrownTech
Would you be so kind to elaborate more on this? It would help us to understand your concern and take the appropriate steps to address it. Thank you.

This article gives an overview of the issue:
https://mikeparker365.co.uk/2016/11/14/skype-for-business-hybrid-with-closed-federation/
The documentation for enabling hybrid also enables partner discovery, which not all organizations have enabled. Disabling partner discovery allows organizations to only allow communication with domains listed in Allowed Domains. If these same companies want to enabled hybrid, then the documentation only states they have to enable partner discovery, therefore enable open federation. Additional documentation on if leaving partner discovery disabled is supported would be great.

@JeffBrownTech Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.

@officedocsbot close


manage close window event

Hi,
I want to manage the close event (click on red button on the top left).
in the app delegate I catch the function
func applicationShouldTerminateAfterLastWindowClosed(_ sender: NSApplication) -> Bool
in this event I want to call a function in the panels.
Is there a way to manage this?
Thanks

This question is not really related specifically to Preferences. You would handle it exactly how you would handle it with a normal window. I would recommend asking on Stack Overflow instead. It's your NSWindowController. You can listen to the close event and do something then.

no, the problem is in the preferences case.
I mean, In app delegate I can catch the event, I want to undestand how I can call a method inside the panel of the preferences.
Thank you very much

There's no difference from calling a method inside your panel as there is to call a method inside your own window or view. A preference pane is just a normal view. You could use NotificationCenter, a delegate, a callback, a weak reference, etc.

sorry if I ask you, I'm new in swift in general
for example in your example I want to call a method test inside GeneralPreferenceViewController when the main window catch  applicationShouldTerminateAfterLastWindowClosed event.
how can I manage it?
Thank you for your help

import Cocoa
import Preferences

@NSApplicationMain
final class AppDelegate: NSObject, NSApplicationDelegate {
	lazy var generalPreferencesViewController = GeneralPreferenceViewController()

	lazy var preferencesWindowController = PreferencesWindowController(
		preferencePanes: [
			generalPreferencesViewController,
			AdvancedPreferenceViewController()
		]
	)
}

You can then call generalPreferencesViewController.someMethod() where you need to.


Release Google.Cloud.Notebooks.V2 version 1.0.0-beta02

Changes in this release:
No API surface changes; just dependency updates.

Created release for Google.Cloud.Notebooks.V2-1.0.0-beta02


feat: add nested mel.obj support

Description
Melange support nested mel.obj.
Example:

 OCaml   Reasonml

let person = [%mel.obj { data = ([%mel.obj { name = "Pedro" }]) }]

let person = {
  "data": {
    "name": "Pedro",
  },
};

We can see it working in the Playground
So this PR adds the same support to native mel.obj, as if you try to use it, it breaks:

How to test

Access any reasonml/ocaml file in the demo
Add a nested Js.t object, like the example above
See that no error is shown

Build on the demo is failing, but tests are passing. Merging and will fix macos failure on #main
Thanks for this PR


Update sources.json

The new url of kolnovel

you should add versionIncrements to make it updatable from app

How should I do that

like this
  {
    "id": "arnovel",
    "sourceSite": "https://ar-novel.com/",
    "sourceName": "ArNovel",
    "options": {
      "useNewChapterEndpoint": true,
      "lang": "Arabic",
      "versionIncrements": 1
    }
  },

When I do this reverse chapters becomes messed up

Nvrm done

Why did you create a new PR?

Because I couldn't make it in the same one

done in https://github.com/LNReader/lnreader-plugins/pull/1019


Fix #217: remove outside-click from pop-up date range picker and use the modal backdrop way to close it

Please check issue https://github.com/Teleopti/styleguide/issues/217 and test it in wfm requests and gamification leaderboard.


Creating SNS subscription fails 1.6.0

$ pulumi version
v1.3.4
$ pulumi plugin ls
NAME   KIND      VERSION  SIZE    INSTALLED  LAST USED
aws    resource  1.6.0    220 MB  n/a        11 minutes ago

Using code:
const success_topic_name = `success2`
const success_topic = new aws.sns.Topic(success_topic_name, {
    name: success_topic_name
});

const success_topic_subscription_name = `success-email2`
const success_topic_subscription = new aws.sns.TopicSubscription(success_topic_subscription_name, {
    endpoint: "https://global.sns-api.chatbot.amazonaws.com",
    protocol: "HTTPS",
    topic: success_topic
});

Gives an error when ran:  https://pastebin.com/HARi8ZSN
Also, trying to pass in a full ARN as string, or using success_topic.arn as the input, both throw errors on autocomplete and update saying you can't use a string there, but the docs show you can:
https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/sns/#example-usage-4
example from docs:
You can directly supply a topic and ARN by hand in the topicArn property along with the queue ARN:

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const userUpdatesSqsTarget = new aws.sns.TopicSubscription("userUpdatesSqsTarget", {
    endpoint: "arn:aws:sqs:us-west-2:432981146916:queue-too",
    protocol: "sqs",
    topic: "arn:aws:sns:us-west-2:432981146916:user-updates-topic",
});

Alternatively you can use the ARN properties of a managed SNS topic and SQS queue:

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";

const userUpdates = new aws.sns.Topic("userUpdates", {});
const userUpdatesQueue = new aws.sqs.Queue("userUpdatesQueue", {});
const userUpdatesSqsTarget = new aws.sns.TopicSubscription("userUpdatesSqsTarget", {
    endpoint: userUpdatesQueue.arn,
    protocol: "sqs",
    topic: userUpdates.arn,
});

Neither of these is working, both error out with:
`    error: Running program '/data/pulumi/infra/aws/company/company-step-functions' failed with an unhandled exception:
    TSError: ⨯ Unable to compile TypeScript:
    index.ts(48,5): error TS2322: Type 'Output<string>' is not assignable to type 'Input<Topic>'.
      Type 'Output<string>' is not assignable to type 'OutputInstance<Topic>'.
        Types of property 'apply' are incompatible.
          Type '{ <U>(func: (t: string) => Promise<U>): Output<U>; <U>(func: (t: string) => OutputInstance<U>): Output<U>; <U>(func: (t: string) => U): Output<U>; }' is not assignable to type '{ <U>(func: (t: Topic) => Promise<U>): Output<U>; <U>(func: (t: Topic) => OutputInstance<U>): Output<U>; <U>(func: (t: Topic) => U): Output<U>; }'.
            Types of parameters 'func' and 'func' are incompatible.
              Types of parameters 't' and 't' are incompatible.
                Type 'string' is not assignable to type 'Topic'.

@stack72 can you verify that the content of resources.go is correct here?

I am not sure this is still an issue - I just tried the following (I didn't have a HTTPS endpoint to test this with) and it worked:
▶ pulumi up
Previewing update (dev):

     Type                          Name                        Plan
 +   pulumi:pulumi:Stack           sns-topic-subscription-dev  create
 +   ├─ aws:sns:Topic              success_topic_name          create
 +   ├─ aws:sqs:Queue              my-queue                    create
 +   └─ aws:sns:TopicSubscription  success-email2              create

Resources:
    + 4 to create

Do you want to perform this update? yes
Updating (dev):

     Type                          Name                        Status
 +   pulumi:pulumi:Stack           sns-topic-subscription-dev  created
 +   ├─ aws:sns:Topic              success_topic_name          created
 +   ├─ aws:sqs:Queue              my-queue                    created
 +   └─ aws:sns:TopicSubscription  success-email2              created

Resources:
    + 4 created

Duration: 20s

The code looks as follows:
import * as aws from "@pulumi/aws";

const success_topic = new aws.sns.Topic("success_topic_name", {
    name: "success2"
});

const queue = new aws.sqs.Queue("my-queue");

const success_topic_subscription = new aws.sns.TopicSubscription("success-email2", {
    endpoint: queue.arn,
    protocol: "sqs",
    topic: success_topic
});

Notice, I am still passing the topic to the TopicSubscription and it hasn't given the same panic
@dbilleci-lightstream I know we are coming back to you super late on this but is there any way you are still getting the same error as before using the latest version of the codebase?

@stack72 He's no longer at our company and his GH emails come to me. Just coming to this thread to close this loop.

Ok thanks for that @samirageb
Going to close this out as not able to reproduce


Where are the annotation txt files corresponding to the images in the project or task?

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Is your feature request related to a problem? Please describe.
I want to be able to directly find the corresponding txt file for each image after annotating on the CVAT platform, so that I don't have to use the export dataset feature in tasks.thanks
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Annotations are stored in database. There are not any .txt files with them.

thanks。 When I select a task or a project, I want to know where the process of exporting the dataset is implemented when I click the “Export Dataset” button. I would like to take a look at the source code of this export feature to see if I can make some modifications.

I would recommend starting investigations from this file: cvat/cvat/apps/engine/views.py.

ok，i find it， and change it， how to rebuild the docker images


Updates to rekor verification

Verify logId matches supplied public key for verification
Clean up some error messages
Use json canonicalizer instead of custom logic

Signed-off-by: Appu Goundan<EMAIL_ADDRESS>

fixes #34

I think this could become problematic once we have multiple tuf roots configurable, but we can tackle that once it's added. I'm still working out how it's supposed to work.

I think this could become problematic once we have multiple tuf roots configurable, but we can tackle that once it's added. I'm still working out how it's supposed to work.

Yeah I think it's a bit hard to visualize this now. The other thing we need to think about is signing multiple artifacts -- should help with the maven work.


XML files inside assets/first-spirit-xml must also be deleted when deleting a post file.

When Jekyll2Cms pulls changes from the configured repository and copies the xml files to the specified first-spirit-xml directory, it does not regard deleted files.
The application must also recognize deleted files and delete the xml equivalents to those files from the first-spirit-xml directory as well.

Created a second push-Method to handel deleted Files.


Token not gets expired when we generate directline token  using microsoft directline api.

I have used POST https://directline.botframework.com/v3/directline/tokens/generate this api to generate the token but it not expiring after 30  minutes  is i am making correct api to generate token or should we have another api to generate token which will expire certain period of time.

@stevkan could you help triage this bug to ABS?


SpeedRatio is not working

First of all I am aware that there is a similar thread about this problem: https://github.com/Sascha-L/WPF-MediaKit/issues/34
I try to change the SpeedRatio after the mediaUriElement is loaded and open, I am using H.264 videos with K-Lite-Codec-Pack 995 and LAV, but the video goes always at the same speed (I have tried from 0.25 to 4).
Any solution?

@miguelgomezmunoz are you use LAV filter is used? MediaUriPlayer tries to open the video with LAV filters (OpenSource()) and if it fails it opens it with the default graph (oldOpenSource()).

@miguelgomezmunoz are you use LAV filter is used? MediaUriPlayer tries to open the video with LAV filters (OpenSource()) and if it fails it opens it with the default graph (oldOpenSource()).

I checked it again, it never uses the oldOpenSource() method and a new LAV filter icon appears in the taskbar for every video I open.

Can you test it with the Test Application frm this git repo and post your code changes or make a fork and then post a link to your fork and branch?

Yes, it would be some codec thing. Firts try to check the graph used, e.g. use MediaUriElement.DumpGraphInfo(). Then check the used filter, for which video file types it supports the speed ratio.


FEATURE: pok show -> also show the players stacks

Currently 'show' shows the players, the current player, the pot and if a player is all in or button. We need to add more data that the players might want like what's the current bet of everyone that is in this round and also the community cards:

current bet next to the player name,
community card

Also, we can take into  consideration moving the show message itself to the DM after a player called pok show in a group- since it's a long message. Another possiblity is deleting the show message after minute or so

Added. The Hebrew (or other languages) name flipping was fixed by adding 'I' (i in CAPS) after the name so whatsapp will parse it as English


0.5.5 is missing build files

<EMAIL_ADDRESS>Maybe add a prepublishOnly or something?

Ups.. Just fixed it and published v0.5.6.


Issuing credits to Michele

Issue 150000 credits to @michelezanini.

 Follow up
On Sunday, 10-Mar-24 22:21:44 UTC by Gov4Git dev
Issued 150000 credits to member @michelezanini.


serving standalone projects with customized url

Why not add a router for serving standalone projects with customized url?
router.GET("/*projectpath", projectHandler)

at the end of all other routers, just like handling 404.

Hi rainyear,
I see what you want to do in #19 and I think it's a great idea!
A few points:

I'm assuming you'd like to host html + css + js sites this way?
This definitely needs Documentation in the Wiki.
Should we call them "projects"? That sounds so big and important. How about "pages" (like "GitHub Pages")?
Since this is user-provided data, it should be saved in the content folder, not built-in (e.g. journey/content/pages).
Will journey/content/pages/mytest/index.html be automatically served by http.ServeFile when you call blog.url/mytest?
It would be great if you could submit the pull request against the development branch. Less hassle for me ;)

This will probably clash with the way posts are served:

router.GET("/:slug/", postHandler)

So automatically serving journey/content/pages/mytest/index.html when you call blog.url/mytest is off the table as Journey would want to open the post with the slug "mytest".

Exactly what I was trying to say!
If I want to create a customized page like blog.url/mytest, I think I should avoid using the same slug mytest.
Also,
router.GET("/blog/:slug/", postHandler)

might be another option, or just make it customizable?

I'd like to keep Ghost compatibility even with urls. So a post should always be reachable at blog.url/postslug.
We could first try to find a post at that url and if there is none with that slug, try to load a custom page. But frankly, I find that unclean.
Cleaner would be a subpath for pages, e.g. /pages/ (so the mytest page would be reachable under blog.url/pages/mytest.

Added support for custom pages in #27


How does this work

It is a little unclear to me from the README what this plugin does.
I think it scopes the search of telescope to a given folder right?
If so, I'll try to look into how to get it to work with the LazyVim distro as currently it doesn't seem to do anything

If you could give me some guidance on how this works, I would love to get this to work with Telescope's git_files as well as neo-tree`

Unfortunately doesn't work with LazyVim at the moment. See: https://github.com/imNel/monorepo.nvim/issues/10#issuecomment-1943437286


[Bug] AvatarView display no image from StreamImage source

Description
AvatarView display no image from StreamImage source.
Steps to Reproduce
Bind the SteamImage as source to the AvatarView
Expected Behavior
Image will be displayed
Actual Behavior
Display no image
Basic Information
Version with issue: 1.1.0
Last known good version: 1.0.3
IDE: VS19
Platform Target Frameworks: .net 5.0.5
iOS: 14.4
Android: 11
UWP:
Android Support Library Version:
Nuget Packages:
Affected Devices:
Workaround
Stuck on XCT version 1.0.3
Reproduction imagery
Reproduction Link
https://github.com/webapps-rvcits/AvatarViewStreamImageSource.git

Could you please add some code or a reproduction project so we know how you are actually assigning the image? Also, you did try 1.2.0-pre2, right? And it still occurs there?

Hi @webapps-rvcits doesn't it work both on android and iOS?
Also, as Gerald mentioned, can you please try latest pre-release version?

@webapps-rvcits I hope this issue should be resolved in the last pre-release version.

Could you please add some code or a reproduction project so we know how you are actually assigning the image? Also, you did try 1.2.0-pre2, right? And it still occurs there?

Good day Mr. Gerald. I'm Roberto Jr Cantos, one of your YouTube subscriber for Xamarin Community Toolkit. I've already tried it on the latest release of XCT 1.2.0 -pre but still problem exist. I can't post my app repository since it is met for business but I can make an another project and post it here just give me an ample of time because I'm always busy on my business and at the same time I'm also an employee in a tertiary level hospital, COVID-19 referral center here in the Philippines.

Hi @webapps-rvcits doesn't it work both on android and iOS?
Also, as Gerald mentioned, can you please try latest pre-release version?

Good day Mr. Andrei. I've already tried it on XCT 1.2.0 -pre release.

Good day Mr. Gerald and Mr. Andrei. Here the link of my repo
https://github.com/webapps-rvcits/AvatarViewStreamImageSource.git
The installed Xamarin Community Toolkit is version 1.0.3 where AvatarView display the Image from the StreamImage Source. I hope and pray that you could help me regarding this matter. Thank you

I will try to find some time over weekend to check this out

Good day Mr. Andrei,
Thank you for the help. I'm counting on you.
Yours truly,
Roberto V. Cantos Jr
webapps-rvcits
On Fri, May 21, 2021 at 6:41 AM Andrei @.***> wrote:

I will try to find some time over weekend to check this out
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xamarin/XamarinCommunityToolkit/issues/1310#issuecomment-845527975,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXU4AOH7Z3PQRJSWU5WUM3TOWF2RANCNFSM45AUJXAA
.

--
Yours truly,
Roberto V. Cantos Jr
WebApps Developer
Mobile No:<PHONE_NUMBER>9

I ran your code sample and works on my end.

cc: @AndreiMisiukevich

Good day Mr. Pedro Jesus,
Yes it will work because the XCT of my repo is version 1.0.3. Try to update
the XCT to version 1.1.0 and 1.2.0 -pre. You will see the difference. Thank
you
Yours truly,
Roberto V. Cantos Jr
webapps-rvcits
On Fri, May 21, 2021 at 10:49 AM Pedro Jesus @.***>
wrote:

cc: @AndreiMisiukevich https://github.com/AndreiMisiukevich
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/xamarin/XamarinCommunityToolkit/issues/1310#issuecomment-845613157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APXU4AMMZG3WMFWJOSDZCT3TOXC2JANCNFSM45AUJXAA
.

--
Yours truly,
Roberto V. Cantos Jr
WebApps Developer
Mobile No:<PHONE_NUMBER>9

Hey @webapps-rvcits I've just taken your repository, updated it to 1.2.0-pre2 and it seems to work perfectly

Thanks @pictos and @jfversluis for checking.
@webapps-rvcits please make sure your update the code to 1.2.0-pre2 (pre-release number 2)

Thanks @pictos and @jfversluis for checking.
@webapps-rvcits please make sure your update the package to 1.2.0-pre2 (pre-release number 2)

Good day everyone,
My remorse for not making an urgent response on your comments. I tried to set the target and min version to Windows 10, version 2004 (10.0, Build19041) and AvatarView display image from StreamImage source. I tried it also to set the target framework to Android 11.0 (R) and it work. It seems XCT version 1.1.0 and up only support the latest version of the OS. Thank you guys helping me. Please see the attached file/s for your reference/s.


CSS fixes: Mobile

Please review, test, and fix for Mobile Safari, iOS Chrome, and Android Chrome (if they differ)

!important

Changing the viewport size in c71a798 seems to have improved the look of the site on mobile.  There are still problems, so this issue remains open.

@nickfrostatx please describe the changes you had in mind in the comments here

Take a look at the white line above the "Our mission is" paragraph. It's two dark grey boxes right next to each other on a white background, and the white shows on mobile. One possible solution would be to have the two boxes slightly overlap.

Not sure if this is for this issue or another one, but MobileSafari on my phone won't show the calendar?


json_serializable dev dependency is redundant

It seems that json_serializable dev dependency, which points to add in the first step of installation, is redundant.
I just didn't add it and everything compiled without any issue on Android and iOS.

Thanks a lot for flagging! I'm about to release a new version that doesn't depend on json_serializable / build_runner at all anyway, and I'll update the docs.

It sounds great.
But I am curious, do you have some issue with json_serializable so that you decided to get rid of it?

I initially used it to avoid boilerplate, but there are a lot of things it doesn't do, like toString(), operator==, hashCode, and types Uint8List and a few other things for which you need custom logic anyway.


Update to pre-release of CosmWasm 0.15.0

A pre-release of CosmWasm 0.15.0 is expected this week. We should update wasmvm.

[x] Update dependencies (see https://github.com/CosmWasm/wasmvm/wiki/Releasing) and make Rust code compile
[x] Add events field to type Response struct in Go
[x] Adapt Go code to messages/submessages merge (https://github.com/CosmWasm/cosmwasm/issues/953 and https://github.com/CosmWasm/cosmwasm/issues/948)
[x] Rename send to funds in Go code (https://github.com/CosmWasm/cosmwasm/issues/916)
[x] Add tests to ensure we get the event in the hackatom contract
[x] Add message type for voting on governance proposal (https://github.com/CosmWasm/cosmwasm/issues/933)

0.15.0-alpha3 is out and contains this IBC structure change: https://github.com/CosmWasm/cosmwasm/compare/v0.15.0-alpha2...v0.15.0-alpha3. @uint could you update the PR accordingly? Then this is good to be released as wasmvm 0.15.0-alpha1.


Update PolylineCommon.glsl

   sinAngle should not be computed using the Window Coordinates of the points,
    which leads to the variation of offset when the position of camera changes.
    We should use the Earth Coordinates.

Welcome to the Cesium community @JimPlayboy!
Can you please send in a Contributor License Agreement (CLA) so that we can review and merge this pull request?
:warning: I noticed that CHANGES.md has not been updated. If this change updates the public API in any way, fixes a bug, or makes any non-trivial update, please add a bullet point to CHANGES.md and comment on this pull request so we know it was updated. For more info, see the Pull Request Guidelines.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Thanks @JimPlayboy, we also received your CLA.  We'll find someone to review.

Hi @JimPlayboy, can you explain a little bit more about what this change fixes?

Polyline with fixed position arrays in 3D world should not change its shape with the movement of camera. The original code computes the sinAngle using the projected points in 2D window coordinates. The window coordinate changes with the movement of camera. This lead to unwanted stretching from certain perspectives. Here is an example which uses polyline to draw a circle.

It looks OK from above the horizon. But the graph is obviously stretched from a horizontal perspective. We can justify this problem by computing the sinAngle with the original 3D Earth Coordinates. Here is the outcome after changing the code.

Thanks @JimPlayboy!
@bagnell can you review?

Hi, @hpinkos .I want to commit CONTRIBUTORS.md to this pull request. But I am new to GitHub. How can I make it?

Hi @jimmyangel, you just need to make sure you edit the file on the fix-polyline-bug-JimPlayboy branch.
You can edit the file directly on GitHub here: https://github.com/JimPlayboy/cesium/blob/fix-polyline-bug-JimPlayboy/CONTRIBUTORS.md

thanks @hpinkos

Hi,@bagnell. Sorry to interrupt you, but I really want to know if my commit will be accepted. Is it a desired suggestion?

@lilleyse could you review?

/cc @jasonbeverage

Thanks for the cc @emackey .  Everything is computed in window space b/c this was meant to replicate the screen space stippling that OpenGL does when applied to Cesium's polygonized lines.  So the stippling changing with a changing camera orientation is to be expected, and I'd also argue desired :)

Thanks for opening this @JimPlayboy, but it sounds like we want to keep the current behavior.  We're happy to look at any other PRs if you have ideas for improving things in the future!


multiconfig: add additional type support

This PR adds new support for the following new types:

int64
[]int
time.Duration

These types are now successfully parsed from all known loaders.

:100:


Combine all device quirks into one workaround.sh

We currently have device specific quirks in various branches.
Combine all quirks into one workarounds script that is called by build.sh

merged #21 to address most of the workarounds. Just the odroid-c1 workaround left.
Need to use jessie to build modules for that board. It runs a 3.10 kernel and needs old gcc or something.
Should make a Dockerfile.odriod-c1 next.


[BUG] Convert-PnPFolderToSiteTemplate rename source folders like 'Shared Documents' to 'Shared_Documents' breaking the import

Reporting an Issue
Convert-PnPFolderToSiteTemplate renames source folders having a space in their name, which break the xml template included in the pnp file (see https://github.com/pnp/powershell/blob/8df54e351875d70881b193578a58bb64c7d9910d/src/Commands/Provisioning/Site/ConvertFolderToSiteTemplate.cs#L108)
Expected behavior
Executing Invoke-PnPSiteTemplate with the newly created package upload all files correctly as if using template XML instead of template PNP file.
Actual behavior
Executing Invoke-PnPSiteTemplate throw an exception when it tries to upload one of the documents

when TraceLog are activated, we can found this:
pwsh Error: 0 : 2022-02-02 14:57:26.6095	[PnP.Framework]	[0]	[Error]	File Wikipedia.docx not found in directory Shared Documents. Exception = Unable to find the specified file.	0ms
Steps to reproduce behavior

Create new Communication site
Upload a document to the 'Shared Documents' library
Edit home page and add a 'Link' WebPart targetting the newly added document
Open Powershell console
Connect to the newly created site
Execute following code

Get-PnPSiteTemplate -Out export.xml -IncludeAllPages -PersistBrandingFiles
Convert-PnPFolderToSiteTemplate -Out export.pnp
Invoke-PnPSiteTemplate -Path .\export.pnp

Error will be thrown when the engine tries to load the file uploaded in the 'Shared Document'
What is the version of the Cmdlet module you are running?
PnP.PowerShell 1.9.0
Which operating system/environment are you running PnP PowerShell on?

[x ] Windows

Error still present with PnP.Powershell 1.10

@Nathaire - Can you please update to the latest release 2.1.x however you will need PS 7.2 or later to benefit from all the bug fixes and improvements.
PS5 support has been dropped in the new release.
Feel free to reopen if the issue persists. Thanks.


For key-vault-jca, investigate what is KeyVaultTrustManager used for.

If azure.keyvault.jca.overrideTrustManagerFactory=true, then KeyVaultTrustManager will take effect.
Investigate why it's related to Spring Cloud Gateway.
Refs: https://github.com/Azure/azure-sdk-for-java/tree/azure-security-keyvault-jca_1.0.0-beta.1/sdk/spring/azure-spring-boot-starter-keyvault-certificates#configuring-spring-cloud-gateway

It configures the trust store used for outbound connections initiated by the Spring Cloud Gateway.


Support Javascript/Typescript semantic highlighting

With the VSCode February 2020 update (v1.43), semantic highlighting was introduced. It is enabled by default (or with "editor.semanticHighlighting.enabled": true).
With semantic highlighting enabled, a lot of the unique context colors have been reduced to a single color, causing the overall highlighting to look much worse.
With semantic highlighting enabled:

Without semantic highlighting:

I am aware of this issue and working on the situation right now ...  This feature help fixin' a lot of problems I had to fix by clever workarounds ... wich are broken now if using that feature ...

https://github.com/microsoft/vscode/pull/92737 fixed it
more Infos: https://github.com/microsoft/vscode/pull/92737#issue-388820821


broken when upgrade to latest vs code

the generated TOC cannot be recognized after upgrading vs code to the latest version

maybe issues 67 can help you

是的

Damn thats a shame, noticed it this morning.

Duplicate of #65


Fix error handling when connection closed by peer

We checked for zero read when reading the packet but not when reading the header, so we tried to read zero bytes from the closed socket (which succeeds), and then tried to write zero length packet to vmnet, which fails with VMNET_INVALID_ARGUMENT:
Example logs (from my logging branch):
ERROR| accept: Interrupted system call
ERROR| vmnet_write: [1003] VMNET_INVALID_ARGUMENT
INFO | Closing a connection (fd 5)
ERROR| writev: Bad file descriptor
ERROR| writev: Bad file descriptor
ERROR| vmnet_write: [1003] VMNET_INVALID_ARGUMENT
INFO | Closing a connection (fd 6)

Now we check for zero read and log a clear message:
Connection closed by peer (fd 5)

For OCD reasons I would prefer the 2 checks (< 0 and == 0) to be in the same order in both cases, but I know it makes no difference. 😄

Right, will fix in the next version.


[BUG]: KafkaSourceStage doesn't stop reading until the queue is empty

Version
23.03
Which installation method(s) does this occur on?
Docker, Conda, Source
Describe the bug.
For a large queue this means that the system will always run out of memory before it emits a meessage.
It really should emit a MessageMeta every time it reaches the pipeline_batch_size.
Minimum reproducible example
No response
Relevant log output
No response
Full env printout
No response
Other/Misc.
No response
Code of Conduct

[X] I agree to follow Morpheus' Code of Conduct
[X] I have searched the open bugs and have found no duplicates for this bug report

Bug doesn't exist. The Kafka source already chunks according to the pipeline_batch_size


local subtitle with tomp4 won't show.

Hello,
I've just managed to read an avi file using the tomp4 flag and having ffmpeg installed.
I've tried specifying a subtitle in .srt forrmat but no luck (the video is playing but without subtitles).
Ubuntu 14.10

I'm able to reproduce the issue. I think it has todo something with the live transcoding and that the video player running on chromecast "forgets" it's current playback position and then isn't able to map the subtitles correctly anymore. I'll experiment if subtitles work together with HLS (we may be using HLS within v0.5).

On Mac the first few lines show up, but that's it. Video keeps going, but subtitles drop out.
I think this pretty much confirms that the problem is in encoding.