Visual Studio Code v1.82.1 Rendering Issue on Fedora Linux 38

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.1

Steps to Reproduce:

Install Visual Studio Code version 1.82.1 on Fedora Linux 38.
Launch Visual Studio Code.

Issue Description
I have encountered a rendering issue with Visual Studio Code (VS Code) version 1.82.1 on my Fedora Linux 38 workstation. The graphical interface does not render correctly, as shown in the attached video. However, when I revert to version 1.81.1, everything works as expected.
Video Attachment
https://github.com/microsoft/vscode/assets/100360644/1f8bf056-26db-4d0b-b9da-86c3d4c82e1b
System Information

OS: Fedora Linux 38 (Workstation Edition) x86_64
Kernel: 6.4.15-200.fc38.x86_64
Resolution: 1920x1080
DE: GNOME 44.4
WM: Mutter
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8)
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile

Expected Behavior:
Visual Studio Code should render the graphical interface correctly without any rendering issues, as it does in version 1.81.1.
Actual Behavior:
Visual Studio Code version 1.82.1 exhibits rendering issues, as demonstrated in the attached video.
Additional Information:

The issue is specific to version 1.82.1, as version 1.81.1 works correctly.
I have attached a video that demonstrates the issue for better clarity.
The issue persists after reinstalling Visual Studio Code or after a system reboot.
The issue persists even after extensions are disabled.
No error messages or logs are generated when encountering this issue.

Workaround:
Currently, I am using version 1.81.1 as a workaround to avoid the rendering issue.

@anfreire I am having the same problem.

OS: Fedora 38
DE: KDE Plasma 5.27.7
Kernel: 6.4.11-200.fc38.x86_64
Graphic platform: Wayland
CPU: 8 x AMD FX(tm)-8300

the same, had to downgrade to 1.81.1

Same for me.

So there are errors when you run it with --verbose:
// Fragment GLSL
#version 300 es
#extension GL_NV_shader_noperspective_interpolation : require
precision mediump float;
precision mediump sampler2D;
out mediump vec4 sk_FragColor;
noperspective in highp vec4 vinCircleEdge_S0;
noperspective in mediump vec4 vinColor_S0;
void main() {
highp vec4 circleEdge;
circleEdge = vinCircleEdge_S0;
mediump vec4 outputColor_S0;
outputColor_S0 = vinColor_S0;
highp float d = length(circleEdge.xy);
mediump float distanceToOuterEdge = circleEdge.z * (1.0 - d);
mediump float edgeAlpha = clamp(distanceToOuterEdge, 0.0, 1.0);
mediump vec4 outputCoverage_S0 = vec4(edgeAlpha);
{
sk_FragColor = outputColor_S0 * outputCoverage_S0;
}
}
Errors:
link failed but did not provide an info log
[10906:0914/132638.588032:WARNING:angle_platform_impl.cc(48)] ProgramGL.cpp:989 (checkLinkStatus): Program link or binary loading failed with no info log.
[10906:0914/132638.588100:ERROR:shared_context_state.cc(81)] Skia shader compilation error
`
also when disabling GPU, everything is fine
`

Hello everyone,
I'm thrilled to report that the rendering issue with Visual Studio Code (VS Code) has been successfully resolved with the release of version 1.82.2. Many thanks to the VS Code development team for their quick response and diligent efforts in addressing this problem.
For those who might not be aware, the issue was related to the graphical interface not rendering correctly, as demonstrated in the attached video. This issue was particularly affecting Fedora Linux 38 users.
After testing the new version, 1.82.2, I can confirm that everything is now working as expected, and the rendering issue is no longer present. This demonstrates the commitment of the VS Code team to provide a stable and reliable development environment for users across various platforms.
If you haven't already, I highly recommend updating your VS Code installation to the latest version, 1.82.2, to benefit from the improvements and to ensure a seamless coding experience.
Happy coding with VS Code 1.82.2!
Best regards,
André Ferreira

nope, the problem is still there:
[25630:0914/140800.844519:WARNING:angle_platform_impl.cc(48)] ProgramGL.cpp:989 (checkLinkStatus): Program link or binary loading failed with no info log.
[25630:0914/140800.844616:ERROR:shared_context_state.cc(81)] Skia shader compilation error
➜  ~ code --version
1.82.2 (abd2f3db4bdb28f9e95536dfa84d8479f1eb312d)
Linux 6.4.15-200.fc38.x86_64

@lukatendai I've reopened the issue for additional investigation, noting that the problem appears to be resolved on my end with VS Code version 1.82.2.
$ code --verbose
[29420:0914/191439.383061:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
[main 2023-09-14T18:14:39.495Z] [File Watcher (node.js)] Request to start watching: /home/anfreire/.config/Code/User (excludes: <none>, includes: <all>),/home/anfreire/.config/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2023-09-14T18:14:39.505Z] [File Watcher (node.js)] Started watching: '/home/anfreire/.config/Code/User'
[main 2023-09-14T18:14:39.507Z] Sending env to running instance...
[main 2023-09-14T18:14:39.508Z] [File Watcher (node.js)] Started watching: '/home/anfreire/.config/Code/User/settings.json'
[main 2023-09-14T18:14:39.571Z] Sent env to running instance. Terminating...
[main 2023-09-14T18:14:39.571Z] Lifecycle#kill()
[main 2023-09-14T18:14:39.571Z] Lifecycle#onWillShutdown.fire()

$ uname -r
6.4.14-200.fc38.x86_64

$ code -v
1.82.2
abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
x64

I was having the same issue, to solve that I've removed the GPUCache as mentioned in https://code.visualstudio.com/updates/v1_82#_update-highlights-for-chromium

I was having the same issue, to solve that I've removed the GPUCache as mentioned in https://code.visualstudio.com/updates/v1_82#_update-highlights-for-chromium

This works, thank you.

Merging to https://github.com/microsoft/vscode/issues/190437
Please follow the workaround mentioned in the release notes https://code.visualstudio.com/updates/v1_82#_update-highlights-for-chromium

Can whoever is in charge of the release notes delete the mention that this issue has anything to do with Mesa? It has nothing to do with this issue, this is 100% a pure upstream Chromium issue bug. Mesa makes no guarantees that compiled shader objects should be compatible across updates to mesalib, libdrm, xorg libraries, llvm etc. There's nothing wrong with keeping a cache of those things, but the correct behavior is to discard it upon obvious errors and compile new objects to replace them.
Source, I help maintain a popular Linux distro and have seen this issue dozens of times across multiple Chromium applications. The following commands are our recommended first troubleshooting step whenever a user complains about rendering issues with Chrome(ium) or an Electron app:
find ~/.config -name GPUCache -exec rm -rv {} +
find ~/.cache -name GPUCache -exec rm -rv {} +


Add rv64 support

Based on guide in #207.
Tests successfully pass:
[----------] Global test environment tear-down
[==========] 316 tests from 5 test suites ran. (64964 ms total)
[  PASSED  ] 316 tests.

However the AllocatorTest.Guards test currently produces an unhandled signal:
[----------] 3 tests from AllocatorTest
[ RUN      ] AllocatorTest.AlignedAllocate
[       OK ] AllocatorTest.AlignedAllocate (39 ms)
[ RUN      ] AllocatorTest.Create
[       OK ] AllocatorTest.Create (0 ms)
[ RUN      ] AllocatorTest.Guards
[115975.450455] marl-unittests[37537]: unhandled signal 11 code 0x2 at 0x0000003fa12eefff in marl-unittests[2aae64b000+2ea000]
[115975.450927] CPU: 0 PID: 37537 Comm: marl-unittests Tainted: G            E     5.15.0-2-riscv64 #1  Debian 5.15.5-1
[115975.451204] Hardware name: riscv-virtio,qemu (DT)
[115975.451337] epc : 0000002aae7f67e4 ra : 0000002aae7f67d8 sp : 0000003fd7c37530
[115975.451504]  gp : 0000002aae93eb10 tp : 0000003fa0f497b0 t0 : 0000003fa1248f36
[115975.451666]  t1 : 0000002aae7a3f3c t2 :<PHONE_NUMBER>000000 s0 : 0000003fd7c37670
[115975.451835]  s1 :<PHONE_NUMBER>000000 a0 :<PHONE_NUMBER>000001 a1 : 0000002ac3aa24b0
[115975.451994]  a2 :<PHONE_NUMBER>000000 a3 :<PHONE_NUMBER>000000 a4 :<PHONE_NUMBER>000001
[115975.452168]  a5 : 0000003fa12eefff a6 : 0000003fa0f49118 a7 :<PHONE_NUMBER>000039
[115975.452367]  s2 : 0000002b1a125f60 s3 :<PHONE_NUMBER>000000 s4 : 0000002b1a126850
[115975.452552]  s5 : 0000003f9f5242c8 s6 : 0000002b1a11f260 s7 : 0000002b1a1264d0
[115975.453570]  s8 : 0000002b1a126770 s9 : 0000002b1a126850 s10: 0000002ae4ad5858
[115975.454008]  s11: 0000002ae4ad57c8 t3 : 0000003fa1197356 t4 : 00183e66ac000000
[115975.454226]  t5 : ffffffffffffffff t6 : 0000010e0b5f240b
[115975.454605] status:<PHONE_NUMBER>004020 badaddr: 0000003fa12eefff cause:<PHONE_NUMBER>00000f
[115975.499495] marl-unittests[37538]: unhandled signal 11 code 0x2 at 0x0000003fa12f0000 in marl-unittests[2aae64b000+2ea000]
[115975.500182] CPU: 0 PID: 37538 Comm: marl-unittests Tainted: G            E     5.15.0-2-riscv64 #1  Debian 5.15.5-1
[115975.500488] Hardware name: riscv-virtio,qemu (DT)
[115975.501073] epc : 0000002aae7f6970 ra : 0000002aae7f6966 sp : 0000003fd7c37530
[115975.501291]  gp : 0000002aae93eb10 tp : 0000003fa0f497b0 t0 :<PHONE_NUMBER>000001
[115975.501522]  t1 : 0000002aae7a3f3c t2 :<PHONE_NUMBER>0003ff s0 : 0000003fd7c37670
[115975.501768]  s1 :<PHONE_NUMBER>000000 a0 :<PHONE_NUMBER>001000 a1 : 0000002ac3abcd60
[115975.501997]  a2 :<PHONE_NUMBER>000000 a3 :<PHONE_NUMBER>000000 a4 :<PHONE_NUMBER>000001
[115975.502238]  a5 : 0000003fa12f0000 a6 : 0000003fa0f49118 a7 :<PHONE_NUMBER>000039
[115975.502475]  s2 : 0000002aae8354dc s3 :<PHONE_NUMBER>000000 s4 : 0000002b1a126850
[115975.502718]  s5 : 0000003f9f5242c8 s6 : 0000002b1a11f260 s7 : 0000002b1a1264d0
[115975.502996]  s8 : 0000002b1a126770 s9 : 0000002b1a126850 s10: 0000002ae4ad5858
[115975.503256]  s11: 0000002ae4ad57c8 t3 : 0000003fa1197356 t4 : 001aa0c0ac000000
[115975.503465]  t5 : ffffffffffffffff t6 : 0000010e0b653e8b
[115975.503638] status:<PHONE_NUMBER>004020 badaddr: 0000003fa12f0000 cause:<PHONE_NUMBER>00000f
[       OK ] AllocatorTest.Guards (75 ms)
[----------] 3 tests from AllocatorTest (117 ms total)

Thank you @developandplay !
A skim over the change and it looks great. I may double check the register saving with the spec - do you have a link to the rv64 ABI spec you used?
For the AllocatorTest.Guards issue - I'm not too sure what's going on here. The test is clearly causing segfaults (which is what we want!), but I don't know why the EXPECT_DEATH isn't working as expected. I'd be happy with this test being disabled with a GTEST_SKIP() when on this architecture, along with a comment linking to this PR comment.
Final thing - the CLA bot has detected that you haven't signed Google's CLA. Are you able to sign this?
Thank you again,
Ben

Hi Ben,
Thanks for the quick response!
I was following the calling convention layed out in chapter 25 of the riscv spec.
Regarding the AllocatorTest.Guards issue I'd lean towards leaving it in there since it's just the console output that's more detailed than expected and the test itself is passing as you can see in the log above.
[       OK ] AllocatorTest.Guards (75 ms)

Unless of course that console log feeds into any other system that could get cofused by the additional output.
I signed the CLA now...
Wish you a merry christmas.
Martin

I was following the calling convention layed out in chapter 25 of the riscv spec.

Yup, looks good. Thank you!

Regarding the AllocatorTest.Guards issue I'd lean towards leaving it in there since it's just the console output that's more detailed than expected and the test itself is passing as you can see in the log above.

Ah okay. No problem then, let's land as-is.

I signed the CLA now...

Perfect, thank you.
Our presubmit bots were recently updated, which introduced some regressions. This was fixed with https://github.com/google/marl/pull/209 which has now landed. Would it be possible to rebase your change on to latest main, so we can run the presubmits?

Wish you a merry christmas.

And you too!

@ben-clayton Perfect! Rebased it on #209 now.

Fantastic job!
Thank you very much for this PR!


The sdk dependency manager error refers to Helm CLI

Output of helm version: v3.4.0 development and previous v3 releases
The download manager within the SDK notes... https://github.com/helm/helm/blob/6a536661fcf1dc0315798ece70bbf193e725945c/pkg/downloader/manager.go#L414
The SDK should have an error that's general and the CLI code in the cmd directory should detect it and decorate with any CLI related elements. Separation of concerns and all.

/assign

/assign


lru-native fails to compile on Win7

The last commit added - besides the mongo stuff - lru-native. This fails to compile since sys/time.h cannot be found (see LRUCache.cc).
Has anybody observed the same issue? I should have installed the necessary prerequisites. If you need to know specifics, just ask. (Well, maybe I could try installing cygwin, looks like windows-build-tools only installed a mingw environment)
As a sidenote, that dependency's repository has not seen a commit in two years, and other people have similar issues with it (see e.g. that one pull request open for a year).

Ah, then I'll switch to a different cache implementation.

Replaced with lru-cache. Let me know if there are any concerns with using this package instead.


Use new Dask docs theme

Bumping the minimum docs theme to use the new version. This isn't strictly necessary but I wanted to raise a PR to trigger the rtd preview and check everything looks ok.
xref dask/dask-sphinx-theme#54

Preview looks good. Merging.


Remove remaining usages of _Bool from generated error code.

All other previous usages of _Bool were already removed in PR #268.
These seem to be the last two left.
This patch is actually necessary in some compiler scenarios using Musl.

PRs from forks currently fail in pr pipeline that will be addressed later, so I cherry-picked into the following branch so we can run the pr pipeline on it:
https://github.com/Azure/iot-hub-device-update/tree/user/jw-msft/neongenbool
The results are running here (unfortunately failure details would not be accessible externally but I can relay any, although I don't expect it for these):
https://dev.azure.com/azure-device-update/adu-linux-client/_build/results?buildId=11921&view=results

PRs from forks currently fail in pr pipeline that will be addressed later, so I cherry-picked into the following branch so we can run the pr pipeline on it: https://github.com/Azure/iot-hub-device-update/tree/user/jw-msft/neongenbool
The results are running here (unfortunately failure details would not be accessible externally but I can relay any, although I don't expect it for these): https://dev.azure.com/azure-device-update/adu-linux-client/_build/results?buildId=11921&view=results

and it succeeded as expected.


#34: Update to Separate Client and Webhooks Secrets

Description
According to the doc, you should not use your Client Secret as the secret for your EventSub subscriptions. This needed to be changed.
Changes

there are now two separate options for secrets in config

identity.secret and listener.secret

Testing
Updated unit tests, all passing.  Blackbox tested to verify functionality as well.

Still want to do a little bit of manual testing before merging this just in case


Support installing deps with --frozen-lockfile

In CI it would be helpful to install package dependencies with a frozen lockfile so we can catch when package.json or lock files are out of step with what yarn installs.
Maybe a oao bootstrap --frozen flag, or proxy any unrecognized flag directly to yarn, e.g. yarn bootstrap --frozen-lockfile?

Supported in v0.8.3, along with --pure-lockfile and `--no-lockfile".


How to use tf.data API with multiple inputs of different shapes

Click to expand!
Issue Type
Support
Source
binary
Tensorflow Version
2.9.1
Custom Code
Yes
OS Platform and Distribution
No response
Mobile device
No response
Python version
3.10
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
I am trying to make a tensorflow model with two different inputs, one will have shape [9,10], the other will just have shape [8].
I am furthermore trying to use tf.dataset to iterate over my inputs. However, whenever I try to do so it fails with the following error:
tensorflow.python.framework.errors_impl.InvalidArgumentError: Shapes of all inputs must match: values[0].shape = [9,10] != values[1].shape = [8]
     [[{{node packed}}]] [Op:IteratorGetNext]

But surely it is possible to have differently shaped inputs into different branches! This is exactly the case in the example in tensorflow's functional API guide, however they do not use tf.dataset so I can't simply follow their example.
To give a little more specifics into the problem I am trying to solve and why I am using the tf.dataset api:
I am doing a time-series problem over multiple sites where my inputs are of two types: those that vary with time, and those that do not but do vary by site. For the time being, I'm just trying to estimate the next time step.
First, I get my dynamic covariates and targets in a sliding window using the timeseries_dataset_from_array util.
    train_ds = tf.keras.preprocessing.timeseries_dataset_from_array(
        input_data, targets, sequence_length=window_size, batch_size=256)

This works perfectly and I can train models using this dataset as is.
However, I want to also use the static covariates from the specific site that the time series data is coming from. The site id is included in the window input data in its own column, though it gets removed before training. Thus, what I am trying to do is grab the static covariates for the site and attach it as a separate input to my dataset.
    train_ds = train_ds.map(lambda x, y: (tf.py_function(attach_static_covariates, [x, idindex, colnames], [tf.float64, tf.float64]), y))

    train_ds = train_ds.map(lambda x, y: ({'dynamic': x[0], 'static': x[1]}, y))

The code for the attach_static_covariates method is:
def attach_static_covariates(x, idindex, colnames):
    id = x[0, idindex].numpy()
    static_cov = static_df.iloc[int(id)]
    #This just filters out the id column, now that it has served its purpose
    x = tf.gather(x, [i for i in range(len(colnames)) if i != idindex])

    return (x, static_cov)

I've confirmed that my code can run and train on multiple inputs provided by the above method provided they are the same size (e.g. if I return (x, x) I can run my model on two copies of the dynamic covariates inputted into two different branches of my model). The problem is not due to a mismatch or a bad model definition because I get the same error from the following code:
    for feature_batch, label_batch in train_ds.take(1):
        print(feature_batch)

I've looked everywhere on google and the tensorflow git and I can't find anyone else with this problem, except for https://github.com/tensorflow/tensorflow/issues/48003, which points to ragged tensors which I don't believe is what I am looking for.  The ragged tensor use case seems to be for variable length entries, but I'm just trying to input two different, but fixed, shapes. And yet it surely MUST be possible to have differently shaped inputs using tf.dataset! I can't imagine that such an incredibly common use case would be completely unsupported. However, I can't find any examples online where someone has multiple inputs of different shapes and uses tf.dataset api. Any help or links to such examples would be greatly appreciated.

EDIT: I did find a workaround, which is in the colab, where you embed the py_function step into another mapped function returning the dictionaries, so that no step ever produces a dataset with two different shaped inputs instead of a dict.  Still, I'd be interested in knowing if there is some other canonical way to get past this.

### Standalone code to reproduce the issue

https://colab.research.google.com/drive/1EnaJoUULl-fyAwlcG_5tcWfsRFVCOMtv#scrollTo=PHvsIOx6-Uux

Relevant log output
No response

@chunduriv I was able to replicate the issue on colab using, please find the gist here for reference. Thank you!

@winthropharvey As mentioned here, try using tf.data.Dataset.from_generator() or try to zip the dataset to combine various inputs using tf.data.Dataset.zip.

The link you included doesn't seem related
On Wed, Jul 13, 2022, 9:29 AM gowthamkpr @.***> wrote:

@winthropharvey https://github.com/winthropharvey As mentioned here
https://github.com/llvm/llvm-project/issues/55386, try using
tf.data.Dataset.from_generator() or try to zip the dataset to combine
various inputs using tf.data.Dataset.zip.
—
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/56343#issuecomment-1183298686,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALUU6YVSUJ2YTQVL4CIVYILVT3HFHANCNFSM5XXLSZSQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm sorry. Just edited it. PTAL. Thanks!


[FLINK-6769] Replace usage of deprecated FileSystem#create(Path, boolean)

Is there another usage in DistCp.java:132: outputStream = targetFs.create(outPath, true)?

Yes, thanks for spotting it. It is now replaced as well.

+1

merging.


Support generic in json (aka typed json)

Right now, if you want to ensure you pass the correct data to json when returning a response in a loader/action you need to do something like this:
type LoaderData = { ... }

export let loader: LoaderFunction = async ({ request }) => {
  // variable created just to ensure the object passed to json match the type
  let data: LoaderData = { ... }
  return json(data);
}

export default function Screen() {
  let data = useLoaderData<LoaderData>()
  // ...
}

With this super small change, you don't need that extra variable for type safety anymore
type LoaderData = { ... }

export let loader: LoaderFunction = async ({ request }) => {
  // no more variables, just pass the generic to json, TS will check if data match the type
  return json<LoaderData>(data);
}

export default function Screen() {
  let data = useLoaderData<LoaderData>()
  // ...
}

Super simple change, a little less boilerplate, and if you don't pass the generic it will infer it from the data object.
This makes https://github.com/sergiodxa/remix-utils#typed-json useless.

Alternatives: https://github.com/remix-run/remix/issues/97


Pub & Polymer build: need special support for packaged Chrome apps

This issue was originally filed by<EMAIL_ADDRESS>
It's very desirable that Pub had added a special support for packaged Chrome app development. Specifically, the following would achieve what we need:

Whitelist app/ subdirectory under a package and process it just like web/ except for #2 below.
When running 'pub install/update/upgrade/...', packages content should be copied to app/packages, instead of creating a symlink app/packages->../packages. This is because Chrome apps implement a strict CSP support and can't work with symlinks extending beyond the app's root directory, which is app/.
Optional: given the #2 above, <package>/packages subdirectory becomes unneeded, so strictly speaking, it can be eliminated. This may not play well with the entire Pub philosophy, so we could live with it.
Polymer build could also take these optimizations into account and skip copying packages into out/packages: out/app/packages is all that's needed.

--Spark team

This issue has been moved to dart-lang/pub#678.


Please count just the active ones

Hey, and thank you for the great app!
For lower heartrate, i would appreciate, to just count the actives services.
Historically i have 33 services, but just 15 active ones.
The other one are paused/deactivated, until i need them again (for example 6 security cameras).
Would it be possible to implement? :)
Best regards

Hey,
thank you :-)
Great idea.
I can make another complication to choose from, which shows only the active ones.
Which complication you currently use the most?
Would you still like the number to turn red, when not all services are online or just a plain number?
Regards,
Christoph

Stupid question: does somebody need monitoring disabled services?
To your question: you have placed a colored symbol, maybe this is enough? :)
I like the white number, too, but maybe try one comlication with colored numbers :)
But i dont know which one, started today with your app, doesnt have placed any complication for now. This is the next step.

Ah, i know what you mean.
I will check within the next week, if I get figure out paused services and add an option to exclude them.
Will update this issue, when I have something to show 🙂

Maybe there is not that much to do.
There is somewhere already a counter for active and disabled ones.
Hopefully you can work with already defined $VARs.

A new app version is on the way.
I added an option to show or exclude paused monitors in the list.
Complications will only count active monitors.
This change will also require to pull the latest docker image.
I will merge the changes to the backend, when the app is approved for the App Store.
Thanks for the input and feel free to test the changes and let me know if there are any issues.

Done with commit 671630a6c744712208996bfca26479feae0ccc5b
Please reopen a new issue in case of any problems.


error - could not access resources for this tennant

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.26.0
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
No response
Bug Description
cant access storage account in the storage explorer app, but i can see it in the browser
here is the error details
{
"message": ""{\n  \"name\": \"Error\",\n  \"message\": \"self signed certificate in certificate chain\",\n  \"stack\": \"Error: self signed certificate in certificate chain\\n    at TLSSocket.onConnectSecure (node:_tls_wrap:1530:34)\\n    at TLSSocket.emit (node:events:526:28)\\n    at TLSSocket._finishInit (node:_tls_wrap:944:8)\\n    at ssl.onhandshakedone (node:_tls_wrap:725:12)\",\n  \"code\": \"SELF_SIGNED_CERT_IN_CHAIN\"\n}""
}
Steps to Reproduce
launch storage explorer
cant see the storage here
Actual Experience
cant access storage account in the storage explorer app, but i can see it in the browser
Expected Experience
shoul be able to access the storage account
Additional Context
No response

even Reuathenticate now doesnt work

even Reauthenticate now does not help

Can you give using system proxy setting a try? You can read more about it here: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network#use-system-proxy-preview

Closing due to lack of response. If you are still encountering this issue, we recommend opening an Azure support ticket via the portal. Alternatively you can open a new issue here.


BVAL-498 Mandating retrieval of parameter names from class files if p…

…resent
A simple one as it's Friday :)

Force-pushed an update to fix the typo.

I see. If there is any way to add the list contents to the assertion,
please feel free to change it :)

Fixed a remaining typo and merged! Thanks. I'll work on the TCK adjustments this afternoon.


luajit_2_1: 2.1.1693350652 -> 2.1.1713773202

Description of changes
I wanted to update luajit because neovim was updated to 0.10.0. Tested basic functionality of neovim.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

I tried this a bit.  Looks OK.


R zsolver

Description
fixed bugs with RZ solver (and 3D solver), added element erosion to rz, and added volfrac.
Type of change
Please select all relevant options

[X] New feature (non-breaking change which adds functionality)
[X] Bug fix (non-breaking change which fixes an issue)
[ ] Formatting and/or style fixes
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Ran test problems, but some element erosion tests need updating

[X] Test A :  2D and 3D test cases

Test Configuration:

OS version: Mac OS
Hardware: x86 cpu
Compiler: clang

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] The code builds from scratch with my new changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

That makes much more sense.  Ill push a bug fix in the morning if you dont
beat me to it.   Thanks!
On Tue, Aug 27, 2024, 5:06 PM Nathaniel Morgan @.***>
wrote:

@.**** commented on this pull request.
In single-node-refactor/src/Solvers/SGH_solver_rz/src/position_rz.cpp
https://github.com/lanl/Fierro/pull/222#discussion_r1733576929:

@@ -59,6 +59,8 @@ void SGHRZ::update_position_rz(double rk_alpha,
for (int dim = 0; dim < num_dims; dim++) {
double half_vel = (node_vel(1, node_gid, dim) + node_vel(0, node_gid, dim)) * 0.5;
node_coords(1, node_gid, dim) = node_coords(0, node_gid, dim) + rk_alpha * dt * half_vel;

       node_coords(1, node_gid, dim) = fmax(0.0, node_coords(1, node_gid, dim));

I see that there is a bug in the coding, the max should only operate on
the radius, dim=1.
—
Reply to this email directly, view it on GitHub
https://github.com/lanl/Fierro/pull/222#discussion_r1733576929, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A74YLYSKE4NWPNEU7VYQWPTZTTZ43AVCNFSM6AAAAABNAPP44WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENRUGU2DSOBSGY
.
You are receiving this because your review was requested.Message ID:
@.***>


🐛 [cloud_functions]: Deadline Exceeded

Bug report
I'm calling a http cloud function from my Flutter App and it doesn't everything correct in the backend, but my Flutter app throws a "deadline-exceeded" error.
This happens only on the first time I call the function in the session. Every other call runs without an exception.
Does anybody has an idea?

@niklasbartsch
Can you provide flutter doctor -v, plugin version, a minimal code sample along with complete error log ?
Thanks.


Support for Systemic Functional Grammar annotations

Excerpted from @costezki email.
Describe the solution you'd like

A special constituency annotation structure specific to Systemic Functional Grammar with a UI.
The annotation structure corresponds to a constituency tree with labelled edges, and where nodes, hold a class and a set of "arbitrary" features (key-value pairs). There is a need for multiple layers as well, and so multiple parallel trees are possible (each corresponding to a type of analysis, e.g. syntactic, thematic, semantic, etc.). I need to be able to design a scheme of edge labels, and of unit classes. Moreover, I would need to constraint the unit class to allow children of only specific classes, connected via specific edges. That means that there is a range of valid children edge labels and node classes for a given parent unit class.

Requirements:

[ ] Constituency trees: Possible in Salt, possible in the graph editor.
[ ] Labelled edges: Possible in Salt, possible in the graph editor.
[ ] Nodes hold a class: Salt knows node classes Structure (hierarchical node), Span (spanning tokens), Token. If other classes are needed, they could be implemented as (1) annotations on the nodes, (2) meta annotations on the nodes, (3) implicitly via layers.
[ ] Nodes can hold sets of arbitrary key-value pairs: Possible in Salt, possible in the graph editor.
[ ] Multiple layers possible: Possible in Salt (SLayer), currently not explicitly possible in editors, can be implemented as (1) explicit layer assignment, (2) layer annotations on nodes (retrievable via search).
[ ] "Scheme" of edge labels: Is this a "tagset" for edge labels? Could be supported in Hexatomic as generic tagset support.
[ ] "Scheme of unit classes": Depending on how classes are solved, can be supported simply via annotations, or explicitly via tagset support.
[ ] Constraints on children classes depending on parent class, and specific edges: Possible to implement via the UI, not the data model. Depending on how unit classes are identified, this could be support for a specific annotation scheme with the respective constraints on children & edge labels.

Describe alternatives you've considered
~A clear and concise description of any alternative solutions or features you've considered.~
Additional context
Could be interesting features for this specific use case, but also other use cases, especially the restrictions on children nodes and edge labels, i.e., "annotation scheme support".

@costezki I have excerpted this from your emails. Please check if this is correct, and let me know where I didn't understand things correctly.
Note that we will not depart from the generic data model Salt, i.e., will and can not extend it for specific use cases such as yours, but that it is possible to implement your model with Salt via different strategies (annotations, meta annotations, layers), and that it would generally be possible to implement annotation scheme support, and tagset support via the UI.
One clear constraint is that we do not have resources to implement this before we have hit our project target, although it could be implemented right now I think. If there is enough interest in this (you mentioned the systemic functional linguistics community), perhaps the interested group can find funding for an implementation.
@thomaskrause Please check for false assessments above & let us know if you have other ideas how this could be implemented.
Thanks!

Thank you for this analysis. This looks like a reasonable start capturing the main structural aspects.
To help making this less abstract, I provide (A) the syntactic overview for the Cardiff Grammar and (B) a poster containing an example of SFG analysis (instantiating a mixture of the Cardiff and Sydney Grammars).
A. In these pictures, the section headings (e.g. Clause, Nominal Group, Quality group) signify unit classes, while the "elements" separated by pipe ( | ) signify syntactic functions and represent slots that can be filled by a child unit ( i.e. the edge labels in a constituency tree).
So indeed, some additional constraints may need to be specified of what functions a unit may accommodate, i.e.what child edge labels are permitted (eventually in which relative order and the probability of occurrence).

B. This is an old poster (2014) with an illustration of how a merged multi-stratal SFG analysis may look like.
poster publisher 1.1.pdf


[B001273] Rep. Diane Black

Rep. Diane Black:
http://black.house.gov
Likely contact form URL to start with:
http://black.house.gov/contact-me/email-me

YMAL file not found. I am working on it.


fix(chat): fix loaders for prompt publishing change path dialog (Issue #1667)

Description:
fix loaders for prompt publishing change path dialog
Issues:

#1667

Checklist:

[x] the pull request name complies with Conventional Commits
[x] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[x] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[x] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

/deploy-review

/deploy-review


Continuous CPU usage on Raspberry Pi 3 Model B

Bug report
System info: InfluxDB 1.4.3 (latest Docker image on arm)
Steps to reproduce:
Hello, I am seeing a continous high CPU usage running this container on a Raspberry Pi 3

Also, the memory usage is a bit odd
I am hosting grafana, influxdb and home-assistant here. I have noticed this when I started to get monitoring from this containers using telegraf.

I have tried to stop grafana and home-assistant, and the spikes of CPU usage continue. What can I do?
Expected behavior: Normal CPU usage, and some CPU spikes.
Actual behavior: High CPU usage.
Additional info: [Include gist of relevant config, logs, etc.]
I've discovered now this debug commands, so in a few hours I'll post the result of some of this commands.
Also, if this is an issue of for performance, locking, etc the following commands are useful to create debug information for the team.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=true"

curl -o vars.txt "http://localhost:8086/debug/vars"
iostat -xd 1 30 > iostat.txt

vars.txt
profiles.tar.gz
I have no iostat installed in the Raspberry Pi, but I can install it if needed.

@alexdrl could you retest this with the latest 1.5.1?

I am using the 1.5.1 version, coming from the influxdb:latest docker image, and I am seeing the same behaviour... Do you want me to reupload some logs?

@alexdrl I checked internally and we have at least one person running 1.4.2 on an RPi 3 and seeing ~6% cpu usage but he's not running in docker. Could you test InfluxDB outside of docker?

@dgnorton this weekend I'll check that. I'll install the .deb package. Thanks!

@alexdrl two other ideas brought up during our internal discussion were:

Building influxd with Go 1.10 might help. One of the team looked at the profile you posted (thanks for that by the way) and noticed it was spending a lot of time in HLL Count. Go 1.10 added support for more ARM instructions, which may improve perf on the RPi.
Another idea was to disable the internal monitor because that appears, from the profile, to be creating a lot of load. The monitor can be disabled in the config:

[monitor]
   store-enabled = false

Another idea was to disable the internal monitor because that appears, from the profile, to be creating a lot of load. The monitor can be disabled in the config:

Wow, this has changed the stable at 100% CPU usage to a stable 0% CPU with usage spikes :D
What does that component do? I'll post another graph of the CPU and memory utilisation with more hours of logging with telegraf.
PD: Improving the general speed of some ARM instructions using go 1.10 also seem like a good idea.

Wow, this has changed the stable at 100% CPU usage to a stable 0% CPU with usage spikes :D

That's great news!

What does that component do?

Monitoring keeps track of InfluxDB's internal stats like number of points written, estimate of number of series, etc. Useful for diagnosing problems sometimes. Some of these internal stats can be expensive to compute with 100% accuracy. However, that level of accuracy isn't always needed. E.g., if influxd were OOMing, it might be helpful to know about how many series have been written. If the estimate says there are 200M series but there's really only 195M, that's close enough. Either of those is likely to cause a problem with an in-memory index. As mentioned in my earlier comment, InfluxDB uses HLL to compute that estimate. It's efficient on Intel hardware but hasn't had much testing on ARM. Will be interesting to see if building influxd with Go 1.10 improves ARM performance for internal monitoring.
Thanks for reporting. I'm going to close this issue since that config change seems to have fixed your problem. If you feel there's still an issue with this, we can reopen the issue.

Thank for you for looking and solving the issue, and for the complete explanation. Ping me if you want me to test a Go 1.10 compiled version with that option enabled.

Not sure if the bug should be re-opened, but I experienced the same behaviour on a Raspberry Pi Zero. I am running an instance of Influxdb with only 2 writes each 11 seconds. I saw lots of empty values so I started investigating. Turns out influxdb was running on close to full cpu most of the time.
The above config change seems to have fixed my problems partly. I am seeing 4-6% cpu utilization on writes, rather than 97% continously.
I am not a developer but this smells buggy to me? Thanks a lot for the solution though! =)

For some strange reason my solution was to stop service, start influxd by hand, let it run for a while, and high cpu load went. :D


Refactor type panel

This is almost a pure refactor building on the GUI overhaul branch
Refactor
Moved event handlers for radio buttons
Moved event handlers for menu-shortcuts related to radio buttons
Moved extract_task
Moved setup_parameters
Changes
Added a TypePanel class
Converted some static strings that were used to manipulate the GUI into named variables
Cleaned extract_task

It is worth to not 2 things:
C++ allows the implementation of any declared function to be place anywhere. Which is why TypePanel.cpp can implement cMain's functions.
The line friend TypePanel; added in #0810c7e allows TypePanel to access variables from cMain eventhough they are protected.


Pavantest

@sigadamvenkata

@PavanKumarN8 can you attach locale run report aswell?

All Test Cases are passed in local run

Hi, @JackySun9 @sigadamvenkata I have pushed the modified code.

Hi @sigadamvenkata @JackySun9 I have added some of the test cases for HomePageSanity and updated the feds.config.js file as suggested.

Hi @sigadamvenkata @JackySun9 I have added Home Page Test Cases for all 91 locales
Local run report


OpenDAP router

An initial pass at creating an OpenDAP router. It's not happy with datetime dimensions yet.
Works on #20

Well this is awesome

And by using the encoded dtype rather than the interperted one, it seems to work, or at least give xarray enough to load a ds...haven't tried slicing around yet.

Time is not being encoded, but it's still, it's loading.

In the spirit of this repo being a playground, I'm gonna merge this and keep digging into the issues with other datasets.

Yes!!! I think that's the right way to treat these PRs, open for posterity and visibility, but greedily merge to main


Initial change

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@331a219). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master     #1   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      1
  Lines             ?     67
  Branches          ?      0
=======================================
  Hits              ?     67
  Misses            ?      0
  Partials          ?      0

Flag
Coverage Δ

#est
100% <100%> (?)

Impacted Files
Coverage Δ

file.go
100% <100%> (ø)

Continue to review full report at Codecov.

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


[Go] [arrow/ipc/writer] voffsets are not updated when Binary-like arrays get truncated

Describe the bug, including details regarding any error messages, version, and platform.
I've stumbled upon this bug while playing around with the results returned from datafusion. It seems that in certain scenarios multiple arrays from different record batches, representing the same column, might share their value buffer.  The problem arises when trying to write those records using an ipc.Writer: If one of the columns which has a single shared buffer happens to be of a binary type the written value is invalid.
This happens because each array's value buffer gets truncated to only the part referred to by its offsets but the offsets are never updated, so now they potentially point to memory outside of the truncated values. When trying to read the binary-like array via the ipc.Reader an error gets returned: string offsets out of bounds of data buffer.
How to reproduce:
func main() {
	var buf bytes.Buffer
	buf.WriteString("apple")
	buf.WriteString("pear")
	buf.WriteString("banana")
	values := buf.Bytes()

	offsets := []int32{5, 9, 15} // <-- only "pear" and "banana"
	voffsets := arrow.Int32Traits.CastToBytes(offsets)

	validity := []byte{0}
	bitutil.SetBit(validity, 0)
	bitutil.SetBit(validity, 1)

	data := array.NewData(
		arrow.BinaryTypes.String,
		2, // <-- only "pear" and "banana"
		[]*memory.Buffer{
			memory.NewBufferBytes(validity),
			memory.NewBufferBytes(voffsets),
			memory.NewBufferBytes(values),
		},
		nil,
		0,
		0,
	)

	str := array.NewStringData(data)
	fmt.Println(str) // outputs: ["pear" "banana"]

	schema := arrow.NewSchema([]arrow.Field{
		{
			Name:     "string",
			Type:     arrow.BinaryTypes.String,
			Nullable: true,
		},
	}, nil)
	record := array.NewRecord(schema, []arrow.Array{str}, 2)

	var output bytes.Buffer
	writer := ipc.NewWriter(&output, ipc.WithSchema(schema))

	err := writer.Write(record)
	if err != nil {
		log.Fatal(err)
	}

	err = writer.Close()
	if err != nil {
		log.Fatal(err)
	}

	reader, err := ipc.NewReader(bytes.NewReader(output.Bytes()), ipc.WithSchema(schema))
	if err != nil {
		log.Fatal(err)
	}

	reader.Next()
	if reader.Err() != nil {
		log.Fatal(reader.Err()) // string offsets out of bounds of data buffer
	}
}

Component(s)
Go

Sorry for the long delay here, I was at a conference and then things have been a bit busy. I can't promise when i'll be able to get to this, but I'll add it to my todo list. If you feel up to trying to fix it yourself, I'd be happy to review any PRs if you end up getting to it before me.

I would be happy to open a fix PR but I first wanted to make sure this wasn't expected behaviour. The Arrow spec says that:

When serializing this layout, we recommend normalizing the offsets to start at 0.

Which opens the possibility for this kind of issue to arise.
Also when comparing the code of the Go and C++ implementation, the IPC writer seems to have 1:1 behaviour match between the two languages, so I would assume that issue also exists there.

You're correct that this isn't expected behavior, likely due to this scenario being uncommon and nearly all cases I'm aware of normalize the offsets at 0. But in the general case your code should work, and it would make sense to update the C++ implementation to fix this too.

Thanks @notfilippo for the clear example. I've been able to adapt the code to a unit test that indeed fails with the error you indicated. The reproduction can be found in this draft PR: #43176.
I'll likely have time over the next week to get into the issue and will update that PR when the fix is added.

Issue resolved by pull request 43176
https://github.com/apache/arrow/pull/43176


Fix article link

Seems like something went funny with the markdown for the link back to the article.
This should address it. Thanks for your work!

great thanks for fixing!


Add method for external storage

Android supports accessing the "external" storage medium. Support
finding this path in flutter with a method call in path_provider
I am interested in writing a flutter app that will access some files a user may have put on their device manually (android). This necessitates looking up the path for the external storage. Though I could do the same thing in my own package, I figured it would be more useful to have this functionality in the path provider package so it can be more broadly used. Sadly this functionality is restricted to android only, as iOS does not let you escape the app sandbox. If there is some other mechanism you would prefer me to go through instead of just creating a pull request, please let me know.

I signed it!

I have added to the example to make use of this new function, but I unfortunately could not test the example, as it seems to be broken by a change in flutter itself (most likely due to moving this stuff out to stand alone). I followed the structure of the existing example, so I don't expect any issues. I would be happy to look into fixing the example as a new small project.
I appreciate you considering this pull request. I am quite new to mobile app development. (I am coming from a background of python/c++ for high performance computing in astrophysics). Flutter is the first framework that has gotten my genuinely interested in the mobile ecosystem. I really like the design choices and am enjoying Dart as a language. I appreciate the opportunity to contribute to this project.

Also, I don't know the etiquette on this project in regards to cleaning up commits, and commit history in general. Is it advisable to squash the commits down like I did?

I have addressed the issues mentioned above (except updating the final date), and rebased my fork onto master. I must say I am actually quite embarrassed at some of the mistakes I had. Previously I had assumed the build failures I was seeing in the platform specific libraries were related to API changes, but it was my own silly bugs causing it to fail. I must spend more time looking over things in the future. You have been quite patient in working with me, and I thank you for that. I am sorry that this has caused so much work for you. I have two commits related to the changes requested, which can be squashed prior to merging in whatever manor you prefer. Please let me know if there is anything else to be done.

Yup, we will handle the merge. Thanks so much for contributing to Flutter, @natelust !

Any update on adding support for external Storage (like Sd Card, External Drive)?


stats counters for chunked items

I should probably just do this myself, and I can't remember why I didn't before (thread context not available? don't want to use global stats counter?), but the chunked item system needs a few counters:

when they're made
when they're freed (maybe?)
when they OOM during upload
anything else?

had a few really hard to track down bugs lately where the workload was described as "always just a few hundred bytes" but the problem turned out to be an edge case with chunked items (sigh) but it wasn't obvious they were ever there.

@dormando still want help? I'm trying to work on a good first issue, this was posted in your 'good first issues' page

@TylerJGabb go for it! If you end up struggling there should be quite a few help wanted ones too.
I can also help clarify anything if need be.


[zero-copy] Add state combinators

Adds two simple combinators for accessing the parse state

Thanks!


Simple rule for components/AbcXyz not working

Describe the bug
I'm testing a simple structure
#ls -la
.
app
public
components
- AbcXyz
   - Aaa
     - aa.tsx
   - Abc.tsx

But i keep getting the eslint error at AbcXyz

To Reproduce
Expected behavior
AbcXyz should be correct structure
Add your projectStructure file
{
  "$schema": "node_modules/eslint-plugin-project-structure/projectStructure.schema.json",
  "structure": {
    "children": [
      {
        "name": "public",
        "children": []
      },
      {
        "name": "app",
        "children": [
          {
            "name": "globals",
            "extension": "css"
          },
          {
            "name": "/^(layout|page)$/",
            "extension": "tsx"
          },
          {
            "name": "favicon",
            "extension": "ico"
          }
        ]
      },
      {
        "name": "components",
        "children": [
          {
            "ruleId": "component_folder"
          }
        ]
      },
      {
        "extension": "*"
      }
    ]
  },
  "rules": {
    "component_folder": {
      "name": "/^${{PascalCase}}$/"
    }
  }
}

** Operating system, Node.js an npm versions, and eslint version (please complete the following information):**

OS: macOS
Node.js: v18.17.1
npm: 9.6.7
ESLint<EMAIL_ADDRESS>
Additional context
Add any other context about the problem here.

Everything works fine for me locally.
I see that the error is not from the console but from the file. Have you tried closing and opening the file?
Sometimes when changing the structure, eslint may show the previous state.
Please show me the whole structure including root like this:

I was able to reproduce your problem on 1.4.3. You are using the configuration from 1.4.4 which adds support for validating multiple structure folders/files. Upgrade your version to the latest. https://github.com/Igorkowalski94/eslint-plugin-project-structure/releases/tag/v1.4.4


Scaffolder Timeout using fetch:cookiecutter action

Seen this reported a lot over the past few days but been unable to reproduce, seems ok on current master for which now I believe is probably down to the yarn.lock.
Created a new npx @backstage/create-app and after everything is running looks like Docker interface is throwingnull as the error, which gets caught in our handler when we do } catch (error) { log(error.stack) { so that handler also breaks which means that the message doesn't get propagated to the frontend correctly that the job has broken.
This just leaves the frontend in a state where it looks like it's still doing things for hours and never completing in the frontend.
This is solved when docker is not used, and installing cookiecutter with pip locally, so that leads me to believe there's something going on with the docker deps side.
Possible Solution
Track down why docker client is throwing null.
Lock down dockerode dependency to the one in master
Fix the handling of errors in the backend + frontend to prapogate these errors better.

Wonder if this is caused by https://github.com/backstage/backstage/pull/6115

Confirmed, the cause has been fixed in #6115. The new library used to throw errors which caused fetch:cookiecutter to fail when cookiecutter was not installed locally. Will be released tomorrow.

As a workaround for this, ensure that you use pip to install cookiecutter locally to stop this library from throwing when cookiecutter is not installed.

Fixed with the latest release. Running yarn backstage-cli versions:bump should get you up and running! Closing!


[Outlook] (manifest) updating API overview to account for JSON manifest

Docs Build status updates of commit c77edee:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/apis.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9ef802e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/apis.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Update l4-load-balancing.md

have to use v1beta1 instead of v1alpha1

@shashankbarsin
Can you help us resolve this aging public-repo PR? Should the changes be made or discarded?
Thanks, PR review team

#sign-off


Add Junctions

[x] New feature (non-breaking change which adds functionality)

Proposed changes
This PR introduces a new built-in node type - 'junction'. This special type of node that can be used to help route wires in a flow.

A Junction does not (currently) have any properties. It does not have an edit dialog - double-clicking on a junction does nothing.
You can drag a wire from a node to a junction in the normal manner
To move a junction it can be click-dragged as nodes can. This means you cannot click-drag a wire from a junction. But you can Ctrl-Click to add a wire from a junction in the quick-add mode you can use with nodes as well
Junctions do not appear in the Info sidebar outline view.
They appear like this in the Import/Export dialog (remember, they don't have properties like name, so all appear as just 'junction')

To add a junction in an existing wire, Shift-RightClick-Drag across the wire(s).

ToDo

NLS (there's one place junction is hardcoded text that needs to be pulled into catalog)
Add Junction to the quick-add node dialog (Ctrl-Click) as an alternative to the click-drag approach

Checklist

[x] I have read the contribution guidelines
[x] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[x] I have run grunt to verify the unit tests pass
[x] I have added suitable unit tests to cover the new/changed functionality

Coverage increased (+0.006%) to 67.329% when pulling 42a51ea88e8136c1fb8a9347fd34c7091968349d on junctions into 0533c0843820ee7e0f1f72d4144eade353cdf621 on dev.


Create dependabot.yaml

Introduce a bot monitoring the versions of github actions

See https://github.com/twosigma/memento/pull/11

@markroth8 and @daniel-shields. This bot will be active once merged into main. It will create pull requests updating the github actions


Configure Azure Pipelines

This pipeline configuration builds the application and produces a build for the Release configuration.

@microsoft-github-policy-service agree [company="Biocartis"]

@microsoft-github-policy-service agree
From: microsoft-github-policy-service[bot] @.>
Sent: vrijdag 23 december 2022 16:37
To: MicrosoftDocs/mslearn-tailspin-spacegame-web @.>
Cc: Nikolas Naert @.>; Mention @.>
Subject: Re: [MicrosoftDocs/mslearn-tailspin-spacegame-web] Configure Azure Pipelines (PR #6922)
ENG CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
NL OPGELET: Deze e-mail is afkomstig van buiten de organisatie. Klik niet op koppelingen of open geen bijlagen tenzij u de afzender herkent en weet dat de inhoud veilig is.
@BIOCnnhttps://github.com/BIOCnn the command you issued was incorrect. Please try again.
Examples are:
@microsoft-github-policy-service agree
and
@microsoft-github-policy-service agree company="your company"
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/mslearn-tailspin-spacegame-web/pull/6922#issuecomment-1364050386, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A43QROG7YTY5C7756JYNMTTWOXBITANCNFSM6AAAAAATH3OAWQ.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
This entire email thread and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. This message contains confidential information and is intended only for the individual named. If you are not the named addressee, you should not disseminate, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.


Is the torchsparse.nn.Conv3d equivalent to the sparse 3D Conv or the submanifold sparse 3D Conv?

Hi, is the torchsparse.nn.Conv3d equivalent to the sparse 3D Conv or the submanifold sparse 3D Conv?

Hi,
It depends on the stride. Stride=1 version is the submanifold convolution and stride=2 version should be the sparse convolution version.
Best,
Haotian

I'm closing this issue due to the inactivity. Please feel free to reopen it if the problem has not been resolved.

I'm closing this issue due to the inactivity. Please feel free to reopen it if the problem has not been resolved.


Fix/cordex 4

Changes for CORDEX for notebook 4

Mostly good. I can't see where JOBIDS is defined, I am guessing it should be GCMIDS?
pedantic things to think about for the future:
* use on tm for temperature, I think we should stick to official naming e.g. tas, tasmin, tasmax

I have opened #120 for this


Repo description: extraneous dot, lack of homepage

This is inconsistent with other org repos.

You've created the same issue on multiple repositories so it cannot be inconsistent.


search is empty while query is not for

Version: 2.8.1 (latest as per filing this issue).
Behaviour: search is empty while query is not for <Redirect/>
Expected behaviour: search corresponding to the query.
On this line:
https://github.com/ReactTraining/react-router/blob/c3cd9675bd8a31368f87da74ac588981cbd6eae7/modules/createTransitionManager.js#L100
redirectInfo { pathname: '/', query: { a: 'b' }, state: null }

No search parameter in redirectInfo

I don't understand. What does your <Redirect/> look like?

The Redirect is a generic one
<Redirect from="/foo" to="/bar"/>

It's not the point of whether the <Redirect/> is unusual.
The point is that redirectInfo contains query parameter with URL parameters yet it doesn't contain the corresponding search parameter. In this case it should have been:
redirectInfo { pathname: '/', query: { a: 'b' }, search: '?a=b', state: null }

is search included in other location objects across router v2?

I guess it is since
{JSON.stringify(this.props.location)}

Gives me
{"pathname":"/","search":"?a=b","hash":"","state":null,"action":"POP","key":"9govif","query":{"a":"b"},"$searchBase":{"search":"?a=b","searchBase":""}}

On a react-routered page.

Our limited time is being spent on 4.0, but if you need this fixed, we will happily merge a pull request.

Ok, I think I'll pass

@halt-hammerzeit I just ran into this and had an exciting time debugging how the history library works.
Make sure you import createMemoryHistory etc from 'react-router' rather than directly from 'history'

@Lexicality Oh wow, what do you know...


Runner: periodically check if there's a new version available on Github and offer a visit

Summary of the Pull Request

add a worker thread which periodically (currently once per 24h) checks if there's a new release available on GitHub
it checks if the current version string, obtained with get_product_version(), isn't equal to the tag_name (the actual git tag) from the latest release obtained using GitHub API, so we must be VERY CAREFUL when submitting stuff on /releases pages, because users will always be getting a notification if the tag doesn't match
if a new version is found, we offer a user to go to its download page, e.g. for v0.14.1
the last time we've checked for updates or showed a user the update dialog is tracked in a separate file at %localappdata%\Microsoft\PowerToys\update_state.json to not mix it with general settings and be able to save/load it safely anytime
VERSION_BUILD isn't used in get_product_version anymore, also it now returns a version prepended with 'v' to much with git tags notation we have so far (e.g. v0.14.1). We still have another zero in PRODUCTVERSION/FILEVERSION macros to make WinAPI happy

Once we've added support for toast notifications in non-packaged applications, we can use a toast instead.

PR Checklist

[x] Applies to #696

Validation Steps Performed

launched (non-)packaged PTs and played w/ values from update_state.json file

Screenshot

We may consider do some parsing when the current version doesn't match the github latest release, to do a more reliable comparison.
We need to verify if creating a draft release triggers the notification.

I really wouldn't want a message box popping up in the middle of a game

Have we verified that would happen with the type of msg box we are using?

@crutkas @ivan100sic
we are replacing the message box with a toast notification. The work to support toast notification in "MSI mode" is in progress.

Description of the work done in the recently pushed commits
Notifications library improvements

added support for toasts in MSI version of PT (thanks @stefansjfw for initial work)
added support for links in toasts
refactored COM activation libraries
XML input is now escaped
improved XML handling

Also, background-activated toasts for MSI version use the same dispatcher (see handler_functions.cpp) as the MSIX to allow code-sharing. For that, we must use PowerToys.exe as an initial local COM server and load the Notifications.dll separately. However, doing this work I've found that it's actually impossible to launch a URI from a background task, so I've added protocol activation type support.
Screenshot

@PrzemyslawTusinski we should add unit tests for VersionHelper.cpp.

MSI:

MSIX (Experimental):

We have only a minor issue when clicking on the "Visit" button: if the default browser is already open and not in the foreground, it will remain not in the foreground.
I guess we can live with that for this release, and investigate if we can workaround it in 0.16.

Rebasing changes to get a sensible commit history.

How about ... "An update to PowerToys is available.  Visit our GitHub page to get vXXXXX.".  The current one is very verbose.

@crutkas done 🙂


Add nugetconfigpath CLI argument across all commands

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
New feature
:arrow_heading_down: What is the current behavior?
Individual sources can be specified on the command line.
:new: What is the new behavior (if this is a feature change)?
Individual sources can be specified via file.
NuGet config files can be specified on the command line and via file.
:boom: Does this PR introduce a breaking change?
No.
:bug: Recommendations for testing
Combinations of sources, nuget configs in file and on command line.
:memo: Links to relevant issues/docs
This implements feature https://github.com/NuKeeperDotNet/NuKeeper/issues/817
:thinking: Checklist before submitting

[x] All projects build
[ ] Relevant documentation was updated

Thanks for this PR!
I'm curious to why you would need this. NuKeeper automatically detects Nuget.Config files, didn't it detect yours? Or do you have a custom file name?

Sorry @MarcBruins, I hadn't noticed you'd commented. This PR relates to https://github.com/NuKeeperDotNet/NuKeeper/issues/817.
I'm having trouble coming up with a workflow to update dependencies in Azure DevOps repos that contain references to NuGet packages in Azure DevOps Artifacts. Specifically, the need to authenticate the NuGet feed.
This was an attempt to dockerise nukeeper and generate a nuget.config within the docker container using the token generated by the build.


Can't fire and scope.

Rage bot doesnt fire. When I turn it off I can't fire and scope.

Issue not valid, take a look at the format required.


Setting for Sublime Merge path

Hi and thank you for making this extension!
I would like to add the possibility of changing the Sublime Merge's path. I'm keen to create the PR for it if you're ok with it?
The reason is that Sublime Merge loses all you open tabs if you open it with parameters. It's a pain and it makes me waste time reopening my 15 tabs.
So the possibility of changing the path in the extension will allow me to direct the command to this file, which I use when starting Sublime Merge through the command line; it checks that Sublime Merge is running before running its command:
#!/bin/bash

set -e

if pgrep sublime_merge; then
	if [[ -d $1 ]]; then
		/opt/sublime_merge/sublime_merge "$1"
	else
		/opt/sublime_merge/sublime_merge "$(dirname "$1")"
	fi
else
	xmessage "Start Sublime Merge before to prevent losing all open tabs."
fi

Are you ok with that? If yes, I'll prepare the PR adding this setting to the extension.

Hey sure, happy to have a look at a PR

Thanks! PR opened here: https://github.com/adhamu/history-in-sublime-merge/pull/16


Is there any possibility to use both 'checkbox' plugin and additional checkboxes inside an item?

Is there any possibility to use both 'checkbox' plugin and additional checkboxes inside an item?
When I try to do so, additional checkboxes are checked or unchecked if checkboxes before an  item are checkbed or unchecked.
I am trying to get them work independently, but looks like this is impossible. Am I wrong?

There is no such built-in functionality, but you can build a simple plugin that adds this functionality - look at src/misc.js for example plugins.
Best regards,
Ivan


Use systemjs-builder?

Currently karma-systemjs uses systemjs and compile files on the fly in browsers. I wonder if it makes sense to use https://github.com/systemjs/builder instead? Which will bundle the test script and run the bundled code in browsers, much like how karma-browserify works.
The karma config will probably look something like this:
module.exports = function(config) {
  preprocessors: [
    'test/*.js': ['systemjs']
  ],
  systemjs: {
     configFile: 'config.js' // if omitted, this is the default value
  }
};

And that's it. karma-systemjs will leverage systemjs builder to compile the test files into self-contained bundled code.
It should have the following benefits:

Easier to specify the files in the conf file. Users only need to specify which test files to include, no need to make app code available to karma server.
Slightly faster. Since browsers won't need to request all imported module and compile them, which are done in one step when karma is started.
Less config options. No need to explicitly tell karma which transpiler to use, only where the systemjs config file is.

Not sure if you are interested in this direction.

Couldn't hurt to give it a shot and see how it goes.
It might also remove the pain from dealing with Karma's web server (ie. The whole prefixing the baseURL with '/base/' stuff).
Only thing is how to start the tests.  In a normal app, you have a single "main" module that you call, so you just set that as the self-executing module in systemjs-builder, and away you go.
Would devs need to do the same thing with tests?

Would devs need to do the same thing with tests?

IMO, every test file should be treated as an entry point (i.e., the main module you mentioned). The good news is that systemjs builder support bundling multiple entry points. jspm uses this features.
So karma-systemjs could pass all files users specified (that should be preprocessed by systemjs) to systemjs builder as entry points. And the final bundled code will execute these files one by one.

There's 2 main challenges I've run into so far:

Bundling all the test files together at once.
I can create 1 bundle per test file as the preprocessor runs over each, but there's no built in hooks in Karma to let you run something once all the preprocessors have finished.
I could copy what karma-browserify has done, but it's convoluted as hell.  It involves creating a second preprocessor to run once the first has finished to generate the single bundle file.
The tricky part of that equation is the "once the first has finished" part - making sure the bundle file is accessed last.

Handling 'autoWatch' mode.
With the proposed config, the only files being watched are the test files.
We need a way to either add all the dependencies from each test to the list of files that Karma watches, or create our own watchers - which is what karma-browserify does using watchify.

These are solvable problems, but it's going to take me some time to work on it.

Firstly, thank you for your efforts to implement this. :)

Bundling all the test files together at once.

I guess we can create 1 bundle per test file as you said. Systemjs builder supports bundling a file without including the runtime code (es6 helper code, es6 polyfill code, etc). I know this because jspm supports a no-runtime option when bundling files. We can then serve the multiple bundled files to the server, along with the runtime code as an extra file.

Handling 'autoWatch' mode.

Ideally, systemjs builder should provides a list of dependencies when an entry point is bundled, that way we can add that list to the watched files (is it as simple as adding to config.files?)
Maybe @guybedford can offer a little help? Can systemjs builder output a list of dependencies like https://github.com/substack/module-deps does?

You can use the builder API here in jspm to get a trace -
var builder = new require('systemjs-builder')();
builder.trace('test/*').then(function(tree) {
  // tree contains keys for all modules in the tree
  // tree can also be built directly:
  return builder.buildTree(tree, 'outfile.js');
});

Watchman is a good watcher I'd recommend (https://facebook.github.io/watchman/)
It might even be quite nice to do this work as a separate project (systemjs-watcher or something), and then just call into that.

@guybedford Thanks for the heads up.
If I'm not wrong, karma already uses chokidar for watching, and if we can get the list of dependencies, it should be as simple as add the list to the watching file list if I'm not too naive.
But I agree a separate systemjs watcher is pretty nice to have.

Thanks all.  This gives me plenty of stuff to go on.
Now I just need some spare time :)

@rolaveric yes it is quite a bit to consider, no pressure! Thanks for your amazing work on this project.

@rolaveric Really appreciate your efforts.
However, I do realize the downsize of bundling each test file individually just now. The common dependencies of these files are now repeated:
bar.js
import "foo"

assert.ok(true);

baz.js
import "foo"

assert.ok(false);

Bundling the two files individually is going to serve two copies of foo to the browser.
But since the files are served locally, I guess it's an acceptable trade off?

Acceptable for a first version at least.
Get the systemjs-builder process and watchers going first, then worry about bundling everything in one hit.
If the performance degrades in the meantime, well... that's what semver ranges and branches are for :)

:+1: , sounds like a plan. :)

Got some progress 45d5c23e8ccea7d180aebb09307925b16b18dab9
I made use of the arithmetic features in systemjs-builder so that each subsequent test suite is bundled without anything from the previous test suites.
It's not as fast as doing everything in one hit, but it's better than the errors I was getting when 2 bundles tried to run their own copies of Angular.
I've got an example of it running on the angular-phonecat tutorial:
https://github.com/rolaveric/angular-phonecat/commit/88244d2bb0dc5b244d91136f14d0133b090d7db5
You can see how much simpler the karma.conf.js becomes.
Next step will be getting the watchers going.

Thank you! Looks great. Will check it out tonight.

Just tried it but encountered a few hiccups:
It should use user's system config.js file, which also contains package dependencies info. Currently it doesn't recognize any of my dependencies.
systemjs-builder should be listed under dependencies  in package.json. Otherwise after installing karma-systemjs, starting karma complains that it can't find it. I'm not sure if es6-module-loader and systemjs are still needed.

It should use user's system config.js file
It does though.
You specify where the user's system.config.js is under systemjs.configFile in the karma config, which is then added to the list of files that karma includes:
https://github.com/rolaveric/karma-systemjs/blob/builder/lib/framework.js#L83
The config specified at systemjs.config in the karma config is entirely optional - a convenience for things like adding modules for testing or changing the baseURL, if you needed to.
karma-systemjs needs to know what the config is so that it can get the baseURL, and use it to map file paths (eg. /home/rolaveric/WebStormProjects/angular-phonecat/test/unit/controllerSpec.js) to module names (test/unit/controllerSpec).
It also needs to pass the config onto systemjs-builder.
systemjs-builder should be listed under dependencies in package.json
Good point.
I've been reluctant to specify dependencies where I can get away with it because I'm afraid I won't notice that a new version has been released, and suddenly people are using SystemJS v0.20.0 in their apps while karma-systemjs tests using v0.16.0.
But I suppose that's no excuse.
I'm not sure if es6-module-loader and systemjs are still needed.
You're right about es6-module-loader, but I think systemjs is still required because karma-systemjs still needs to call System.import(testSuiteModuleName).
Unless systemjs-builder already includes System.import() in bundles.
If I can get everything included in a single bundle, I can make that bundle self-executing, meaning System.import() isn't required.

It does though.

Ah, sorry for missing it.
Currently the preprocess reads config.systemjs.config directly, this can fail if user didn't define systemjs in the karma config file, and they get a cryptic Can not load "systemjs"! error.

suddenly people are using SystemJS v0.20.0

You can lock the version down by simply specifying the version (with nothing prefixed) in package.json.

Unless systemjs-builder already includes System.import() in bundles.

I believe builder.buildSFX does.

they get a cryptic error
Well spotted.  I'll add some checks to make sure the user includes either a config.systemjs.configFile or a config.systemjs.config (maybe they want to completely override the config...), and raise an error if they're not.
I believe builder.buildSFX does.
Trouble there is build.SFX() won't let you use this testSuite2 - testSuite1 as the module expression.  It'll let you add, but not subtract.
So I need to get the "all in one bundle" process going.

I just found karma-jspm.
It seems to work in a similar fashion to karma-systemjs (eg. Serve but not include each file and use System.import() to load them), except that it makes use of the JSPM structure.
eg. Looks in package.json to find the SystemJS config file (default to config.js) and packages folder (default to jspm_packages/).
Another caveat with the bundles approach is that it's not possible (or at least not practical) to use other preprocessors.  eg. karma-coverage
Combine that with custom watchers and the hoop jumping required to get everything in a single bundle, I'm starting to question if this is worth the trouble.
So far the only thing we're gaining, from a user perspective, is only having to specify the test files in the karma config.

I think you have good point concerning bundling files.
But if I'm not wrong, the current master branch architecture doesn't supporting using karma-coverage for an imported jsx file for example?
What about we define a systemjs preprocessor, but only transpile each individual file:
module.exports = function(config) {
  frameworks: ['mocha', 'systemjs'],
  files: [
    "app/*.jsx",
    "test/*.js"
  ],
  preprocessors: [
    "app/*.jsx": ['systemjs', 'coverage']
  ]
};

Making this plugin works much like karma-commonjs
Not totally sure, but does it work like this: transpile each file using es6-module-loader and serve them along with systemjs to the browser?

Transpiling files individually into System.register is the most efficient workflow.
I've created https://github.com/systemjs/builder/issues/126 if it would make this easier.
For now this can be done for ES6 only though via Babel or Traceur directly.

Thank you @guybedford, if systemjs builder can directly support it, it will make things much easier.

Good idea.
Ideally we'd want to run coverage first, so the reports show the source code.
But with ES6 coverage support still sketchy, and the plethora of "compile down to Javascript" languages out there, that's not really practical.

Systemjs builder should be able to generate an inline source map, and hopefully coverage will pick it up and generate a new one accordingly.

I'm going to close this issue off as stale.
I don't think the possible benefits would outweigh the complexities.


Add split-embed helper func

Add the ability for embeds to be split into multiple embeds if they're too large (e.g. help commands)

Added helper func to split the first embed field.


Made screen not blurry when stretched.

For some reason Firefox and Chrome blur a stretched canvas by default. It can now be turned off with CSS. Funny thing is the blurring actually slows things down a bit. So it is faster, and looks better(IMHO) to not blur.
Left: Default blurring, Right: No blurring

Do you like this?

Woohoo thanks! Yes I have tried several times to make this work over the past few years. Last time I looked this wasn't supported.
BTW all new development for JSNES is happening in this branch and separate repo:
https://github.com/bfirsh/jsnes/tree/split-out-ui
https://github.com/bfirsh/jsnes-web
I have already implemented this in jsnes-web.

Okay cool. I had seen the ui split repo, but not the jsnes-web one.

Will merge for the time being so it works in the old version, at least. :)
Thank you! 💖


Upgrade Closure compiler/library to latest

Draft Requirements:

[ ] Merge ngageoint/opensphere-build-closure-helper/pull/27
[ ] Merge ngageoint/opensphere-build-resolver/pull/78
[ ] Update versions in package.json

This PR upgrades the Closure compiler to 20210406.0.0 (via opensphere-build-closure-helper) and the library to 20210302.0.0.
Changes

Updated jQuery externs to 3.3, provided by Closure.
Updated Angular externs to 1.6, provided by Closure with our local edits merged in.
Refactored use of the goog.log API to reflect changes in the Closure library.
Refactored goog.Uri.QueryData API to reflect changes in the Closure library.
Refactored goog.net.Cookies API to reflect changes in the Closure library.
Replace uses of goog.base in tests. This has been deprecated and removed since the last library update.
Fixed additional build errors identified by the updated compiler.

Rebased to get up to date and trigger a build. The build failed once because it's using Node stable, which is now 16.0.0 and<EMAIL_ADDRESS>is not supported with Node 16. I switched the Travis build to use Node LTS, which will be 14.x until October. Second build failure seemed to be an infrequent timing issue with our Job tests.

goog.nullFunction has been deprecated. They recommend replacing with an inline empty function, but we already have os.fn.noop so I replaced instances with that.

goog.bind has also been deprecated, and should be replaced with the native bind. goog.partial is still fine to use if you don't need to change the this binding. Updated all goog.bind references to resolve those warnings.


Add a datatype_inference module for inferring coders and schema from data

For now, the idea is that these datatype_inference functions would only be used for tests, so that we don't have to write out the coder, the avro schema, the fastavro schema, and the parquet schema for every PCollection that we are testing.
Ultimately, it may be nice to make these functions more robust such that they can be used by default in Beam pipelines when the user does not explicitly provide a schema.
For example use-cases of where these functions are used, see: apache/beam#8884.
CC: @ivant @ananvay
R: @udim

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

This PR broke windows testing. Please fix: https://issues.apache.org/jira/browse/BEAM-8170


Updated from Swift 2.0 to 5.0 and cleaned up the code

Notes

Updated the code from Swift 2.0 to 5.0
Updated code to match modern day Swift standards (at least more so than it was)
Updated demo project files to work with the latest devices
Updated README to reflect changes

Merging. If anyone finds any issues just let me know.


Question about logger

I see that slog have the With method, which returns a new logger with some appended attributes. But in the logger package you haven't implemented this one. I wonder about the reason of this dicision, is it an anti pattern or you just dont need this method.
Thank you.

I customized slog to meet some of me personal choices. The things I need are hardcoded in the implementation details. If I was look to extend slog, but still keep it available for others to use and customize, I would have done things differently.


BUGFIX: Fix loading of resources with spaces in filenames

Encode filenames loaded from S3 to prevent problems with browsers that
don't fully support spaces in URIs.
We encountered an error when using this package. When you have a file like "Screenshot 17 of 2015-09-21.png" it works great if you use it in a src-Attribute of an HTML img element.
Problem is when you use the srcset-Attribute. It has a format like this:
<EMAIL_ADDRESS>2x, Image.jpg 1x"
So the image names are not delimited by quotes or something like that.
With the filename from the example it would look like that:
"Screenshot 17 of<EMAIL_ADDRESS>2x, Screenshot 17 of 2015-09-21.png 1x"
So Safari now thinks that the image is named "Screenshot" and it is not found, obviously.
My simple solution is to rawurlencode the filename so that it does not cause problems with the srcset.
What do you think?

According to the HTML spec, the src attribute of the img tag () needs to be a "valid non-empty URL potentially surrounded by spaces" so the fix makes sense in general. But IMO it should not be the filename that is encoded but rather the URL that is returned. So probably we should rather encode it in getPublicPersistentResourceUri() or maybe even in the ResourceManager itself if possible.

@bwaidelich if we did that, couldn't that end up in double encoding? Because, we don't know for sure what a custom resource storage / publishing target will return, or?

@robertlemke sorry, didn't see your response earlier. If all implementations do it correctly (don't change the filename, but encode the URIs) there should be no risk

:+1: by reading (and Sebastian tested this)

I already tried earlier to enforce uri encoding at a low level in the framework, it's the only responsible place really....

@kitsunet I'm not sure whether I got you. it is the only responsible place to do it in the framework (and if yes, where exactly?)  or like sebastian did in this PR? So is it a +1 or a -1?

Ping…

Hey @bwaidelich – @kitsunet – @robertlemke – any news on this one?

no news from me, I still stick to what I wrote in Sept 2015 ;)

Fellow contributors… how do we proceed here?

TBH I don't know if this actually still is an issue, but this change is really old by now. Feel free to re-open and resolve conflicts, if you like! 🎄


Feature Request / Question: IP-Cam object detection (How-to)

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No, I've followed a tutorial and haven't touched the base setup of it. https://github.com/EdjeElectronics/TensorFlow-Object-Detection-API-Tutorial-Train-Multiple-Objects-Windows-10
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 1.5.0
Python version:  3.6
Bazel version (if compiling from source):  Couldn't get the capture script to return this
GCC/Compiler version (if compiling from source): b'unknown'
CUDA/cuDNN version: 9.0 / 7.05
GPU model and memory: Nvidia GeForce GTX 960M / 2Gb?
Exact command to reproduce: No idea

Describe the problem
Hello Tensorflow, my question is pretty straightforward and maybe was already answered somewhere, but I'm not finding the answer : )).. Hence, I turn to you. If there is already a clear guide out there on how to do it, could you point me in the right direction?
Given this script that launches the object detection with a webcam, how do I modify it to launch the detector by giving an IP address as input and receiving that video feed (and bounding boxes) as output? (Source in the last section).
I am aware we can always set an IP cam to be a webcam in the machine's webcam list, but I'd like to access the IP address directly. Can this be done? Is this already implemented?
Thanks in advance!
Source code / logs
import os
import cv2
import numpy as np
import tensorflow as tf
import sys
sys.path.append("..")
from utils import label_map_util
from utils import visualization_utils as vis_util
MODEL_NAME = 'inference_graph'
CWD_PATH = os.getcwd()
PATH_TO_CKPT = os.path.join(CWD_PATH,MODEL_NAME,'frozen_inference_graph.pb')
PATH_TO_LABELS = os.path.join(CWD_PATH,'training','labelmap.pbtxt')
NUM_CLASSES = 6
label_map = label_map_util.load_labelmap(PATH_TO_LABELS)
categories = label_map_util.convert_label_map_to_categories(label_map, max_num_classes=NUM_CLASSES, use_display_name=True)
category_index = label_map_util.create_category_index(categories)
detection_graph = tf.Graph()
with detection_graph.as_default():
od_graph_def = tf.GraphDef()
with tf.gfile.GFile(PATH_TO_CKPT, 'rb') as fid:
serialized_graph = fid.read()
od_graph_def.ParseFromString(serialized_graph)
tf.import_graph_def(od_graph_def, name='')
sess = tf.Session(graph=detection_graph)

image_tensor = detection_graph.get_tensor_by_name('image_tensor:0')
detection_boxes = detection_graph.get_tensor_by_name('detection_boxes:0')
detection_scores = detection_graph.get_tensor_by_name('detection_scores:0')
detection_classes = detection_graph.get_tensor_by_name('detection_classes:0')
num_detections = detection_graph.get_tensor_by_name('num_detections:0')
video = cv2.VideoCapture(0)
ret = video.set(3,1280)
ret = video.set(4,720)
while(True):
ret, frame = video.read()
frame_expanded = np.expand_dims(frame, axis=0)

(boxes, scores, classes, num) = sess.run(
    [detection_boxes, detection_scores, detection_classes, num_detections],
    feed_dict={image_tensor: frame_expanded})

vis_util.visualize_boxes_and_labels_on_image_array(
    frame,
    np.squeeze(boxes),
    np.squeeze(classes).astype(np.int32),
    np.squeeze(scores),
    category_index,
    use_normalized_coordinates=True,
    line_thickness=8,
    min_score_thresh=0.85)

cv2.imshow('Object detector', frame)

if cv2.waitKey(1) == ord('q'):
    break

video.release()
cv2.destroyAllWindows()

I just got it to work, as soon as I entered the IP address in video = cv2.VideoCapture(), so you can safely ignore this : )

Good to hear you got it working!

@SJRogue
Sorry I also wanted this method to work with Tensorflow object detection. I wanted to get a video of an IP cam, I did it in the following way but it came out wrong :(
cap = cv2.VideoCapture ()
cap.open ("rtsp: // utpl<EMAIL_ADDRESS>554 / Streaming / Channels / 2")
Could you help me please?


Fix a potential issue in CodedBufferWriter

Currently CodedBufferWriter, when serializing a field, manually masks
the "repeated", "required", and "packed" bits to get the "base type" of
the field.
However it also needs to mask the "map" bit as the function to map the
"base type" to an array index (_valueTypeIndex) only works for values
that are a power of 2, i.e. there needs to be at most one bit set.
This code still works today because of the special case when the map bit
set, after getting the base type incorrectly.
In other words, when the map bit is set we compute the wire type
incorrectly, but we don't use the incorrect value.
Changed in this PR:

_valueTypeIndex now has an assertion checking that the argument is
really a power of 2.

valueType is now computed using PbFieldType._baseType, which
correctly masks the "map" bit.

wireFormat is moved after the special case that checks for the map
bit.

With (1) tests in protoc_compiler start to fail. Either one of (2) or
(3) fixes the issue, but I think both are improvements.
JSON serializers correctly use the PbFieldType._baseType function to
get the base type so no changes needed.

One of the CI jobs failed when fetching SDK:
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to storage.googleapis.com:443

I restarted the CI jobs now.


Attack OwnMod Issue

First, thank you for these macros.  This is exactly what I needed right now.
I do see an issue with OwnMod however as our group determined that if you combine the text of unarmed attack (If your unarmed attack bonus is higher, you can use that instead) with Wild Shape's "When you choose to use your own attack modifier while polymorphed, you gain a +2 status bonus" to say that occurs before the comparison.  In other words, if your own unarmed attack modifier is +9 and the form's attack modifier is +9, adding the +2 would make your own modifier +11 and thus you can use that.

Thanks for catching that! It should be fixed now, so the attack modifier that will used is either the Form's Bonus, or your base mod + 2 if that is higher. This also accounts for if your mod if just 1 lower than the Form's Bonus, but you can choose to use it and gain +2, making it 1 greater than the Form's.
Also added support for Handwraps of Mighty Blows. Let me know if things work better now!


Experiment with force-directed graph layout

Check if force-directed graph layout would be an improvement for rendering objects in the heap. Such a layout may use the screen space more efficiently and place objects that reference each other closer together, but it could also result in objects jumping around when navigating between frames. Animation might alleviate this jumping behavior.

Here's an example where the original layout engine of the Python Tutor has no optimal placement for nested data structures:

Example: https://dodona.be/nl/courses/3355/series/36011/activities/1918665684/


Support for multiple arguments per RFC per user

Depending on a user's reputation, they should be able to make multiple arguments per RFC. Every user starts with 1 argument though.

[ ] Show argument counter when a user has more than one argument available
[ ] Notify users somehow when they've passed a reputation threshold and have multiple arguments
[ ] Creating additional arguments is done in the same way: by pressing the vote bar and writing an argument. There should be an explanatory text to let users know they are making another argument

I'm actually not sure whether it's worth investing time in this one:

Allowing multiple arguments for the same RFC requires a major UI refactor
I don't think many people would want to make several arguments

Maybe someone has good input here. Feel free to share your thoughts.

Not doing it for now


IPFS Storage Provider for decentralized storage

🚀 🚀 Pull Request
Checklist:

[ ]  My code follows the style guidelines of this project and the Contributing document
[ ]  I have commented my code, particularly in hard-to-understand areas
[ ]  I have kept the coverage-rate up
[ ]  I have performed a self-review of my own code and resolved any problems
[ ]  I have checked to ensure there aren't any other open Pull Requests for the same change
[ ]  I have described and made corresponding changes to the relevant documentation
[ ]  New and existing unit tests pass locally with my changes

Changes
Added the IPFSProvider to integrate decetralized storage (IPFS) into Activeloop Hub. Currently able to hub.load datasets stored on IPFS.

Hey @smejak! Thanks for the PR, it is definitely a great feature. From a cursory glance, the code looks good, the team and I will review it properly in the next few days.

Hey @AbhinavTuli! Thanks a lot! I am still working on the final implementation of copy and delete functions & their corresponding unit tests. I will push the updates to this PR once it's ready.

HI @smejak, thanks for your contribution. Would you mind signing our CLA while we review your PR.

Hi @tatevikh. I signed the CLA but then I accidentally pushed a commit with incorrect credentials. I tried to git rebase that commit but it seems it hasn't been updated here.

Closing due to many conflicts. Will add the new PR link as soon as we open it.


Fix errcheck and golint issues

Hi @zwopir,
I fixed many trivial linter issues. See above the remaining ones,
$ gometalinter --deadline 6m --vendor  ./...
collector/nodes_test.go:15::warning: cyclomatic complexity 26 of function TestNodesStats() is high (> 10) (gocyclo)
logger.go:12::warning: cyclomatic complexity 12 of function getLogger() is high (> 10) (gocyclo)
collector/nodes.go:1401::warning: cyclomatic complexity 12 of function (*Nodes).Collect() is high (> 10) (gocyclo)
collector/cluster_health_test.go:13::warning: cyclomatic complexity 11 of function TestClusterHealth() is high (> 10) (gocyclo)
tls.go:14::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:36::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:41::warning: Potential file inclusion via variable,MEDIUM,HIGH (gosec)
tls.go:14::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:36::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:41::warning: Potential file inclusion via variable,MEDIUM,HIGH (gosec)
tls.go:14::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:36::warning: TLS InsecureSkipVerify set true.,HIGH,HIGH (gosec)
tls.go:41::warning: Potential file inclusion via variable,MEDIUM,HIGH (gosec)

I think this check, with a configuration file excluding those false positives should be added as a Makefile target, and runned at TravisCI. This would prevent new commits introducing new issues in a future. Should I do a PR about this?

thanks for the PR. A makefile target for further checking would be great!


AutoComplete Algorithm for Search Bar

AutoComplete Algorithm for https://www.30secondsofcode.org/ search bar

I can provide an algorithm, which would be able to give users related search suggestions based on the words that they typed on the search field. It would be pretty helpful for users, as they can see what kind of result they can get before they searched.
It would be similar to this: https://ingredient-d4129.firebaseapp.com/ 's search suggestions.
But I think my algorithm will run faster.
What'd you think

Thanks for the interest. However, due to certain implementation constraints, we have decided against this feature as it will significantly impact client-side performance across the website.