weighted random selector/sequence

Description
To better encapsulate the random manipulation logic for composites, I created a RandomizedComposite node that should never be used as is; it is only so that logic can be shared for SelectorRandom and SequenceRandom (or else, I would have to copy and paste a hundred lines on both scripts)
This new class contains the seed settings, option to specify weights for each child and the shuffle logic.

⚠ Thorough testing needed
The editor for weights works fine but I noticed it is sometimes finicky. I had to reopen the scene for it to work again. Maybe this happened because I was constantly changing the code but I would like to be sure that it is all working properly.

Addressed issues

Closes #194

Screenshots
Weights editor:

Proof of concept
I made a little test to make sure that the weights are actually affecting the random sampling by recording all of the times a node was picked as the first child.
After 36698 times:

Action "First" with weight 40 was picked 39.69% of the times
Action "Second" with weight 30 was picked 30.03% of the times
Action "Third" with weight 15 was picked 15.12% of the times
Action "Forth" with weight 15 was picked 15.16% of the times

Looking great - don't forget to also add some tests for this.

Github actions tests failed 😢

Could this be the cause?

@lostptr a couple of findings:

renaming a child node affected by a weight resets the weight
If I set the weight of Node A to 50 but the weight of node B to 10, currently node B gets invoked more often which is rather confusing - is this intentional? As your description suggestes that a higher weight equals more likelihood to be executed. e.g. if I set weight of Node A to 30 and of node B to 70, A is called way more often which seems to be wrong

weight-issue.zip

renaming a child node affected by a weight resets the weight

Yeah I noticed that too but I had no ideia how to deal with that  and thought it wasn't such I big deal.  However, I can see how that can be annoying and cause a bunch of silly bugs because people would not notice. I found a way to fix that, albeit not very elegant 😆.

If I set the weight of Node A to 50 but the weight of node B to 10, currently node B gets invoked more often which is rather confusing - is this intentional? As your description suggestes that a higher weight equals more likelihood to be executed. e.g. if I set weight of Node A to 30 and of node B to 70, A is called way more often which seems to be wrong

Oops!
I made a little change in the SequenceRandomComposite and forgot to do the same with the SelectorRandomComposite. The weights were having the exact opposite effect, it should work now.

renaming a child node affected by a weight resets the weight

Yeah I noticed that too but I had no ideia how to deal with that and thought it wasn't such I big deal. However, I can see how that can be annoying and cause a bunch of silly bugs because people would not notice. I found a way to fix that, albeit not very elegant 😆.

If I set the weight of Node A to 50 but the weight of node B to 10, currently node B gets invoked more often which is rather confusing - is this intentional? As your description suggestes that a higher weight equals more likelihood to be executed. e.g. if I set weight of Node A to 30 and of node B to 70, A is called way more often which seems to be wrong

Oops! I made a little change in the SequenceRandomComposite and forgot to do the same with the SelectorRandomComposite. The weights were having the exact opposite effect, it should work now.

@lostptr Why didn't the test fail? Or was the test broken too?

@lostptr Why didn't the test fail? Or was the test broken too?
There where no tests for the selector thats why. I have added them in the latest commit.


Add more options for different series types

Currently, visual mode supports basic series options for Line. More options should be supported for other series

This is long-term task, which is already partially implemented in separate PR.
Additional series types will be added in the future releases as requested.


Python has stopped working

Win7Pro SP1 64-bit
new Anaconda3-2019.07 install
Every time I try to start Spyder it fails with the error message: Python has stopped working.
I've tried restarting, rebooting, and deinstalling/reinstalling Anaconda.
Does anybody have any idea what might be causing this, or how I might resolve the issue?
--
Jerry J. Anderson, CCIE #5000

This is probably related to you antivirus and/or firewall. Please deactivate them and try again.

I deinstalled all virus/firewall software and rebooted.  I then deinstalled Anaconda.  I removed the C:\Users<userid>\Anaconda3 directory.  I rebooted again.  Finally I reinstalled Anaconda.  I tried running Spyder, and got the same "Python has stopped working" error message.

I'm very sorry about that, but that's the only advice we have for this kind of problem without more details about the issue.
There's probably another software in your computer causing this, but it's impossible to know for us which one.

I have the exact same issue.  Windows 7 64 bit.  Have done everything you have done and still get the same Python has stopped working.  Very frustrating.  Have checked to make sure python is in the path and no other versions of Anaconda or .anaconda files were on my computer when I installed Anaconda 3.7 64 bit.  Spyder was working fine in the old version I had Anaconda 2.0.


(feat) validate partitions along row axis, add warning

Feature or Bugfix

Feature

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 0967ac67c59ab63b158ff0ee9b4b2636e86c2514
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-s6u9F3qN9oFy
Commit ID: 0967ac67c59ab63b158ff0ee9b4b2636e86c2514
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 0967ac67c59ab63b158ff0ee9b4b2636e86c2514
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-s6u9F3qN9oFy
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 4325e50a5c6976ca9c6d1f2efbd779d28f52cca8
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 669bd20928a06c6688e2339c66e451fbbea007a3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-s6u9F3qN9oFy
Commit ID: 669bd20928a06c6688e2339c66e451fbbea007a3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: 669bd20928a06c6688e2339c66e451fbbea007a3
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: c5f7229818a6ef015251a43451a57ff326a8c508
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubLoadTests5656BB24-s6u9F3qN9oFy
Commit ID: c5f7229818a6ef015251a43451a57ff326a8c508
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubStandardCodeBuild8C06-llutOAimTATs
Commit ID: c5f7229818a6ef015251a43451a57ff326a8c508
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Fix tag_suffix for accounting service

The Helm chart generates a kubernetes manifest that expects the suffix of the account service's image to be accountingservice.
https://github.com/open-telemetry/opentelemetry-demo/blob/fa7847efb691e323236955c6126d486cf2c1b558/kubernetes/opentelemetry-demo.yaml#L9533-L9535
Few options to fix this:

This PR
Fix the Helm chart to use the new name
Others?

I'd be happy to follow up on whatever solution people would prefer.
If people like the solution in this PR, I think it would also make sense to change the directory name and all contained files back to accountingservice for consistency - e.g., /src/accounting becomes /src/accountingservice. Thoughts?
I see now that there is an effort to remove the term service from the names of the services in #1788. I recommend leaving the tag_suffix for services untouched for now.

Closing this as the nightly releases are not part of anything we would deploy on Kubernetes or do with a fresh repo clone + make a start. The Kubernetes deployments that we support are fixed to the last good release, which is 1.12.0 right now. The nighlies will carry the new names for services as we change and we need to continue to do that for development reasons.


Flash of unstyled content

After building, in Safari and Firefox I see a FOUC when I change slides. The text is unstyled for a split second.
Theme is:
import { aspect } from '@mdx-deck/themes'
import highlight from '@mdx-deck/themes/syntax-highlighter-prism'

export const themes = [ aspect, highlight ]

No problem in Chrome.

I believe this is an issue with the aspect ratio component. Can you see if this still occurs without the aspect theme?

Absolutely fine without the aspect theme.

Yeah, since the aspect ratio (currently) uses ResizeObserver, I think that's causing the styling to change after initial load – if anyone wants to work on a better solution, I'd be happy to look at a PR

Closing this since I think this is related to how ResizeObserver works in general


Support dynamic device type validation on API calls

Describe the bug
I just chased down a bug where the i2c_write function was passed a device binding which was not an I2C device. There was no indication that this was an error (no compiler warning/errors, no runtime assertion failures) but there really should be something to prevent this.
To Reproduce
struct device *dev;
uint8_t dummy[1] = {0};

dev = device_get_binding(LED_PORT); // this is a GPIO, not I2C
gpio_pin_configure(dev, LED, GPIO_DIR_OUT);

i2c_write(dev, dummy, 1, 0x23); // this runs fine, and even returns success (== 0)!

Expected behavior
Some sort of error or assertion failure should occur
Impact

Can cause bugs which are difficult to track down as it fails unsafe (it returns success despite being an incorrect driver)
Makes spelling errors in variable names easy to miss

Environment

OS: Ubuntu 18.04
Toolchain: gnuarmemb
Commit: ff214d637e
Board: nrf52840_pca10056

This issue is not specific to i2c_write.
Zephyr does not use device-specific type, so obviously no static type checking is done.
As for dynamic type checking, since there is no "device type" value in struct device, so there is currently no straight-forward method for API functions to validate the specified device instance type (which, I believe, is a deliberate decision made to reduce memory footprint and checking overhead).
If we are really concerned about this, we could potentially add a build option to enable dynamic device type validation (cc @pabigot @carlescufi).
This sounds more like an enhancement request than a bug.

I see your point, but having i2c_write return the success error code when it didn’t actually succeed seems like a bug to me.

I see your point, but having i2c_write return the success error code when it didn’t actually succeed seems like a bug to me.

The result of providing a non-I2C device instance to the I2C API functions, when there is no safeguard against it, is "unpredictable", and "returning success" just happens to be one of such unpredictable cases.
That is not a bug, but rather an inherent (and deliberate) limitation of the current Zephyr device API implementation.

Yes, I think you are right then.
Was the plan to have some sort of polymorphism for drivers, or is it purely to save RAM?

A system call from usermode would have validated that the device passed was an I2C device, but in privileged mode (which is the default) no such validation is performed.

This could be added but as a debug feature only.

Just an extra thought about this ,  an assert would be nice to detect at compile time. Metadata could be added about the type of node (uart-controller, gpio-controller,spi-controller,etc) type and only used as mentioned only in debug mode #ifndef NDEBUG.

I came across another use case for dynamic validation. Many of the shell interfaces use device_get_binding with an argument parsed from the shell console (e.g., pwm, gpio, i2c among others). Without any kind of validation, it's pretty easy to enter the wrong device and crash Zephyr or corrupt random state.
It would be good if there was some way to do typed device lookups to allow the shell to return an error instead of just using an invalid device.
(I realize this is a bit of an old issue at this point, but as far as I can tell there still doesn't seem to be any convenient method to do this kind of validation).


[ConstraintSystem] Implement sendability inference for key path expressions

Gated by InferSendableFromCaptures experimental flag.
Swift forums pitch - https://forums.swift.org/t/pitch-inferring-sendable-for-methods-and-key-path-literals/68011
Sendability of key path expressions is expressed by means of protocol composition
between key path type and Sendable protocol i.e. KeyPath<String, Int> & Sendable.
Augment the key path capability inference to include sendability checking based
on whether subscript component arguments captured by a key path are sendable
or not or, if there are subscript components a key path expression is always sendable.
Resolves: rdar://75861003

@swift-ci please test

@swift-ci please test source compatibility

@swift-ci please test Linux platform

@swift-ci please test

@swift-ci please test Linux platform


add EXTERNAL_PATH env

#22

🆕 generate-version-file added the EXTERNAL_PATH environment variable, which supports passing in the path of a file. It is recommended to use it when a large amount of additional information needs to be written into version.json. When EXTERNAL and EXTERNAL_PATH are set at the same time, the priority is lower than that of EXTERNAL
💄 更新 README.md 和 README.zh-CN.md 文档

Codecov Report

Merging #24 (ccc98a0) into main (30d7143) will not change coverage.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #24   +/-   ##
=======================================
  Coverage   97.56%   97.56%
=======================================
  Files           2        2
  Lines          82       82
  Branches       17       17
=======================================
  Hits           80       80
  Misses          2        2

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Debian 9 os detection fails

Debian 9 returns "Linux" instead of "linux" in PHP_OS so it makes sense to use strtolower in os detector

Shouldn't this be fine because the only place where PHP_OS is directly in use is in ...
https://github.com/vaimo/webdriver-binary-downloader/blob/master/src/Analysers/PlatformAnalyser.php#L10
... where case-insensitivity is in action?

Indeed, this might be a lbaey/chromedriver issue that was cached before


Care team detailed performer

Detailed info is added for performer in Care team

Hello @okurt59 is this something you want to present on our next calls - 7/21 or 7/28?

No progress 7/28/2022 -- Please bring if interested!


Fix wildcard matching in lv_drivers.mk

233860e introduced wildcard matching for sources in lv_drivers.mk,
but also introduced a typo, so gtkdrv/ directory was ignored and
non-existent gtk/ was searched. This resulted in linking error for
all programs using GTK as their display driver because gtkdrv/gtkdrv.c
wasn't compiled, which means that important symbols like gtkdrv_init
and gtkdrv_flush_cb weren't created.

Thanks, the make file was really outdated. But the directory has gtkdrv name, not gtkdev.

Thanks, the make file was really outdated. But the directory has gtkdrv name, not gtkdev.

Fixed.

Looks fine; thanks for the fix.


External resources are not in the classpath

Hi!
I forked the project (https://github.com/pandrez/building-java-9-modules) and modified the last step to include log4j2 as a dependency of the fairy module. I created a src/main/resources folder and added a log4j2.xml into it.
If I run ./gradlew run, the first output line states that log4j2.xml cannot be found.
It seems that this file is not added to the module path.
Am I doing something wrong or is there an issue here?

The issue is that the run task is using the exploded output folder (build/classes/java/main), not the libs/fairy.jar output from the jar task.
The contents of src/main/resources will included in libs/fairy.jar, so if you ran that, everything would be fine.
The original plugin adds build/resources/main to the --module-path. That, however, is useless since that directory does not itself contain a module, and isn't associated with any module by being in --module-path.
Instead, src/main/resources should be removed from --module-path, and it should be in:
--patch-module org.gradle.fairy.app=build/resources/main

I'll fix this in my fork.

Gradle 6.4 now supports Java Modules directly. There we use the Jar instead of folders in many places to mitigate this issue.


In front matter of task topics, change approvers to reviewers.

Partially addresses #7432.

This change is

/hold

/assign @heckj

/cc @Bradamant3

/hold cancel

/lgtm


cancel button in 'new example' modal does not work

steps to reproduce:

click 'create new example'
click 'cancel'

expected behaviour: modal quits
observed behaviour: no change

It was working for me but it's possible that it was buggy with certain antd versions.
I added a possible fix https://github.com/golastmile/rasa-nlu-trainer/commit/4ece3c18f5bb1ac7bc7734d30b4e2778491160ed
Can check if it is working for you too? (i updated the demo here https://golastmile.github.io/rasa-nlu-trainer/ :) )

yep works now! thanks :)


[Feature] Use disruptor

Figure 1. Latency histogram comparing Disruptor to ArrayBlockingQueue

Superseded by https://github.com/apache/eventmesh/issues/4788 and https://github.com/apache/eventmesh/issues/4816


How to add multiple source to deepstream.py?

In DeepStream-Yolo, I can add changes to deepstream_app_config.txt to add more sources. I don't know the same way to do it in python.

You will need to add the code for it. Take a look on https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master/apps/deepstream-test3

You will need to add the code for it. Take a look on https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master/apps/deepstream-test3

I successfully modify it. However, when it inference on two stream, FPS from 28Fps to 15Fps. Is there a method that can improve multistream inference performance？

It's the expected result. If the board can process only 28 fps with one source, it will be around 15 fps for 2 sources. You can try the FP16 to have more performance (1.5x +).

You will need to add the code for it. Take a look on https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master/apps/deepstream-test3

I successfully modify it. However, when it inference on two stream, FPS from 28Fps to 15Fps. Is there a method that can improve multistream inference performance？

Could you please share the modified code?

You will need to add the code for it. Take a look on https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master/apps/deepstream-test3

I successfully modify it. However, when it inference on two stream, FPS from 28Fps to 15Fps. Is there a method that can improve multistream inference performance？

Could you please share the modified code?

well,
1.change SOURCE = '' to SOURCE = []
2.change source_bin = create_uridecode_bin(0, SOURCE, streammux) to
for i in range(len(SOURCE)):
print(SOURCE[i])
source_bin = create_uridecode_bin(i, SOURCE[i], streammux)
3.change if 'file://' in SOURCE: to  if 'file://' in SOURCE[0]:
4.change parser.add_argument('-s', '--source', required=True, help='Source stream/file')
to
parser.add_argument('-s', '--source', nargs='+',required=True,help='Source stream/file')
5.Then add tiler display to it:
import math
tiler = Gst.ElementFactory.make('nvmultistreamtiler','nvtiler')
if not tiler:
sys.stderr.write('Unable to create tiler')
sys.exit(1)
tiler_rows = int(math.sqrt(len(SOURCE)))
tiler_columns = int(math.ceil(1.0* len(SOURCE)/tiler_rows))
tiler.set_property('rows',2)
tiler.set_property('columns',1)
tiler.set_property('width',1280)
tiler.set_property('height',720)
tiler.set_property('show-source',1)
pipeline.add(tiler)
converter.link(tiler)
tiler.link(osd)
osd.link(sink)

You will need to add the code for it. Take a look on https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master/apps/deepstream-test3

I successfully modify it. However, when it inference on two stream, FPS from 28Fps to 15Fps. Is there a method that can improve multistream inference performance？

Could you please share the modified code?

well, 1.change SOURCE = '' to SOURCE = [] 2.change source_bin = create_uridecode_bin(0, SOURCE, streammux) to for i in range(len(SOURCE)): print(SOURCE[i]) source_bin = create_uridecode_bin(i, SOURCE[i], streammux) 3.change if 'file://' in SOURCE: to if 'file://' in SOURCE[0]: 4.change parser.add_argument('-s', '--source', required=True, help='Source stream/file') to parser.add_argument('-s', '--source', nargs='+',required=True,help='Source stream/file') 5.Then add tiler display to it: import math tiler = Gst.ElementFactory.make('nvmultistreamtiler','nvtiler') if not tiler: sys.stderr.write('Unable to create tiler') sys.exit(1) tiler_rows = int(math.sqrt(len(SOURCE))) tiler_columns = int(math.ceil(1.0* len(SOURCE)/tiler_rows)) tiler.set_property('rows',2) tiler.set_property('columns',1) tiler.set_property('width',1280) tiler.set_property('height',720) tiler.set_property('show-source',1) pipeline.add(tiler) converter.link(tiler) tiler.link(osd) osd.link(sink)

After following your instructions, I've successfully modified the code to handle multiple sources with DeepStream. However, I encountered an issue where the application can process multiple streams but fails to display multiple video feeds simultaneously. Could you please share the deepstream.py file or provide guidance on how to resolve this issue?

@ng-fukgin did you successfully make it? seems to me using nvmultitiler can only make 1 inference on 1 of the tiles at each frame. When switching to default sample with exact same code, the detection is fine.

It's the expected result. If the board can process only 28 fps with one source, it will be around 15 fps for 2 sources. You can try the FP16 to have more performance (1.5x +).

@marcoslucianops , When I try batch size = 4 in tile, the fps is 30/4 = ~7.x, is the reduce of speed results from the computation, or the synchronizatio between tiles?


New method of counting slow queries

Fix: #1406
/cc @mm4tt
Need to test it first
/hold

Please ping me when it's ready for review

/lgtm
/approve
Thanks!


Game crashes when using a custom Aura Potion

I'm testing a modpack with a lot of mods, so I won't bore you with the details (you can find them in the full crash report), but I think it's only a few of them causing the issue.
I'm using Potion Blender to combine potions. It doesn't support Aura potions the same way it does with regular and splash potions, so I'm editing the NBT data (it could be done basically vanilla with an external text editor or a command, but I'm using a mod that does the same thing for convenience).
I was trying to create a custom potion with this data:
{CustomPotionColor:10533516,CustomPotionEffects:[{Ambient:0b,Amplifier:1b,Duration:9600,Id:50,ShowIcon:1b,ShowParticles:1b},{Ambient:0b,Amplifier:0b,Duration:9600,Id:67,ShowIcon:1b,ShowParticles:1b},{Ambient:0b,Amplifier:1b,Duration:9600,Id:28,ShowIcon:1b,ShowParticles:1b},{Ambient:0b,Amplifier:0b,Duration:9600,Id:2,ShowIcon:1b,ShowParticles:1b},{Ambient:0b,Amplifier:1b,Duration:9600,Id:8,ShowIcon:1b,ShowParticles:1b},{Ambient:0b,Amplifier:1b,Duration:9600,Id:24,ShowIcon:1b,ShowParticles:1b}],Potion:"potionblender:combined_potion",display:{Name:'{"extra":[{"italic":false,"color":"#ABCDEF","text":"Moonwalker Aura"}],"text":""}'}}
It has slow falling, jump boost, glowing, and slowness vanilla effects, and also "End Veil" (prevents endermen from getting mad when you look at them. There weren't any endermen nearby, so I don't think it was that) and a Decreased Gravity effect from quoteall's fork of the Gravity API.
I think the crash is either related to Aura potions not liking me stuffing them with NBT data for a custom potion, or something to do with the Gravity API. Here's the relevant bit from the crashlog:
[13:46:13] [Server thread/ERROR]: Encountered an unexpected exception
--
3184 | net.minecraft.class_148: Ticking player
3185 | at net.minecraft.server.ServerNetworkIo.tick(ServerNetworkIo.java:175) ~[client-intermediary.jar:?]
3186 | at net.minecraft.server.MinecraftServer.tickWorlds(MinecraftServer.java:908) ~[client-intermediary.jar:?]
3187 | at net.minecraft.server.MinecraftServer.tick(MinecraftServer.java:824) ~[client-intermediary.jar:?]
3188 | at net.minecraft.server.integrated.IntegratedServer.tick(IntegratedServer.java:105) ~[client-intermediary.jar:?]
3189 | at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:671) ~[client-intermediary.jar:?]
3190 | at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:265) ~[client-intermediary.jar:?]
3191 | at java.lang.Thread.run(Thread.java:833) ~[?:?]
3192 | Caused by: java.util.ConcurrentModificationException
3193 | at java.util.HashMap$HashIterator.nextNode(HashMap.java:1597) ~[?:?]
3194 | at java.util.HashMap$KeyIterator.next(HashMap.java:1620) ~[?:?]
3195 | at net.minecraft.entity.attribute.EntityAttributeInstance.computeValue(EntityAttributeInstance.java:135) ~[client-intermediary.jar:?]
3196 | at net.minecraft.entity.attribute.EntityAttributeInstance.getValue(EntityAttributeInstance.java:125) ~[client-intermediary.jar:?]
3197 | at net.minecraft.entity.LivingEntity.localvar$cie000$creo$lib_modifyGravityVariable(LivingEntity.java:15199) ~[client-intermediary.jar:?]
3198 | at net.minecraft.entity.LivingEntity.travel(LivingEntity.java:2090) ~[client-intermediary.jar:?]
3199 | at net.minecraft.entity.player.PlayerEntity.travel(PlayerEntity.java:1614) ~[client-intermediary.jar:?]
3200 | at net.minecraft.entity.LivingEntity.tickMovement(LivingEntity.java:2719) ~[client-intermediary.jar:?]
3201 | at net.minecraft.entity.player.PlayerEntity.tickMovement(PlayerEntity.java:571) ~[client-intermediary.jar:?]
3202 | at net.minecraft.entity.LivingEntity.tick(LivingEntity.java:2419) ~[client-intermediary.jar:?]
3203 | at net.minecraft.entity.player.PlayerEntity.tick(PlayerEntity.java:283) ~[client-intermediary.jar:?]
3204 | at net.minecraft.server.network.ServerPlayerEntity.playerTick(ServerPlayerEntity.java:510) ~[client-intermediary.jar:?]
3205 | at net.minecraft.server.network.ServerPlayNetworkHandler.tick(ServerPlayNetworkHandler.java:269) ~[client-intermediary.jar:?]
3206 | at net.minecraft.network.ClientConnection.tick(ClientConnection.java:259) ~[client-intermediary.jar:?]
3207 | at net.minecraft.server.ServerNetworkIo.tick(ServerNetworkIo.java:172) ~[client-intermediary.jar:?]
3208 | ... 6 more
3209 | [13:46:13] [Server thread/ERROR]: This crash report has been saved to: /Users/********/Library/Application Support/com.modrinth.theseus/profiles/Dev-Fabricly Adventurous! 0.0.1/crash-reports/crash-2023-11-28_13.46.13-server.txt

since mclogs deletes logs after 90 days here's a backup with the actual crashlog file just in case.
log.txt


Added Visual Studio Code to pkg installer

I added a Visual Studio Code to the pkg installer, its not clean but it should install it correctly on all the Jetson devices and its a much better editor than Gedit or other arm based editors.

Thank you @Rafcin I'm checking!

Awesome! The gist files if they correctly install will replace the ones in VS and compile with Electron, if they do then all is good 👍. Also VSCode hopefully will be useful to people because of it's customization features + workspace and git control.

I have only fixed the size of the window and add an extra comment on the patch menu about the wifi fix.

Awesome!

I'm going to add some more stuff over the weekend regarding ROS Melodic, there's a lot of bugs I've found over time that probably should be looked at. Also have you considered switching the catkin_make to Catkin build?

Also one thing that I think will be useful is adding RTABMAP and having it compile from scratch becuase it allows you to also use the Zed SDK vs when you install it through apt it doesn't have that enabled/pathway set.


Where is the ability to add pixel-wise padding?

I'm attempting to pad all pixels in an image as seen below to perform a proper Conv2DTranspose with padding...
[
[1, 4],
[7, 9]
]
->
[
[0,0,0,0,0],
[0,1,0,4,0],
[0,0,0,0,0],
[0,7,0,9,0],
[0,0,0,0,0],
]

But I can't seem to find any function in keras to do this. Any assistance is appreciated.

This should be possible using tensorflow (I don't think there is a native keras solution). One implementation I can think of are SparseTensors. Considering the example you gave:
import tensorflow as tf

inputs = tf.SparseTensor(indices=[[1, 1], [3, 1], [1, 3], [3, 3]], values=[1, 4, 7, 9], dense_shape=[5, 5])
padded = tf.sparse_tensor_to_dense(inputs, validate_indices=False)

[[0 0 0 0 0]
 [0 1 0 7 0]
 [0 0 0 0 0]
 [0 4 0 9 0]
 [0 0 0 0 0]]

@alxy Thanks for the suggestion, but that's assuming you know the size of the incoming tensor. In this case for a typical convolution, you do not know the size.
@fchollet any thoughts?


Task/adapt identity api module

Closes #47

This change is

Codecov Report

:exclamation: No coverage uploaded for pull request head (task/adapt-identity-api-module@163a51e). Click here to learn what that means.
The diff coverage is n/a.


studio: Use ls-remote --get-url as default.

In CI scenarios the previous logic was not reliable. Feels reasonable to just use this simpler logic as default for all scenarios.

Codecov Report
Base: 96.72% // Head: 96.72% // Decreases project coverage by -0.00% :warning:

Coverage data is based on head (3816d78) compared to base (b1e04bf).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #407      +/-   ##
==========================================
- Coverage   96.72%   96.72%   -0.01%
==========================================
  Files          37       37
  Lines        2169     2168       -1
  Branches      204      204
==========================================
- Hits         2098     2097       -1
  Misses         41       41
  Partials       30       30

Impacted Files
Coverage Δ

src/dvclive/studio.py
93.58% <100.00%> (-0.09%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks, let's see how it'll work.

It worked for me in example repo and Studio prod


BLE advertising scanning not reporting after a period of time (IDFGH-6473)

I have an application that listens for BLE advertisements running on an ESP32C3.  After a period of time, the scan stops reporting new results.  I have verified that I'm not running out of memory and that other tasks continue to run.
I noticed that v4.3.2 has this entry:
Fixed no ADV report after scan for a while

I updated to v4.3.2 and I see the same issues as I did before the upgrade.  It looks like that fix may not have carried through.
This code (hacked up from ble50_security_client example) will demonstrate the problem--after a period of time, callbacks to esp_gap_cb stop:
    // Initialize NVS.
    esp_err_t ret = nvs_flash_init();
    if (ret == ESP_ERR_NVS_NO_FREE_PAGES || ret == ESP_ERR_NVS_NEW_VERSION_FOUND) {
        ESP_ERROR_CHECK(nvs_flash_erase());
        ret = nvs_flash_init();
    }
    ESP_ERROR_CHECK( ret );

    ESP_ERROR_CHECK(esp_bt_controller_mem_release(ESP_BT_MODE_CLASSIC_BT));

    esp_bt_controller_config_t bt_cfg = BT_CONTROLLER_INIT_CONFIG_DEFAULT();
    ret = esp_bt_controller_init(&bt_cfg);
    if (ret) {
        ESP_LOGE(TAG, "%s initialize controller failed: %s\n", __func__, esp_err_to_name(ret));
        return;
    }

    ret = esp_bt_controller_enable(ESP_BT_MODE_BLE);
    if (ret) {
        ESP_LOGE(TAG, "%s enable controller failed: %s\n", __func__, esp_err_to_name(ret));
        return;
    }

    ret = esp_bluedroid_init();
    if (ret) {
        ESP_LOGE(TAG, "%s init bluetooth failed: %s\n", __func__, esp_err_to_name(ret));
        return;
    }

    ret = esp_bluedroid_enable();
    if (ret) {
        ESP_LOGE(TAG, "%s enable bluetooth failed: %s\n", __func__, esp_err_to_name(ret));
        return;
    }

    //register the  callback function to the gap module
    ret = esp_ble_gap_register_callback(esp_gap_cb);
    if (ret){
        ESP_LOGE(TAG, "%s gap register error, error code = %x\n", __func__, ret);
        return;
    }

    esp_ble_gap_set_ext_scan_params(&ext_scan_params);
    ESP_ERROR_CHECK(esp_ble_gap_start_ext_scan(UINT32_MAX,0));

Thanks.

Note: using 0 (zero) instead of UINT32_MAX for duration appears to solve for this problem.  It is still likely a bug as the failure reliably occurs in less than 10 minutes in my tests.

@cmsedore
If the Duration parameter is non-zero and the period parameter is zero, it shall continue scanning until the duration has expired.
The time range of duration is 10ms~655.35s

Thanks for reporting, will close due to short of feedback, feel free to reopen with more updates.


⚠ Bofrost.be has degraded performance

In b22b9c0, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1846 ms

Resolved: Bofrost.be performance has improved in 2ec7a52.


[SPARK-12113][SQL] Add some timing metrics for blocking pipelines

What changes were proposed in this pull request?
This is rework based  on #10116
How was this patch tested?
Manually checked

Test build #60708 has started for PR 13736 at commit 9d2d40d.

Test build #60708 has finished for PR 13736 at commit 9d2d40d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class SQLDiffMetric(metricType: String, startTime: Long = 0L, initValue: Long = 0L)

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60708/
Test FAILed.

I'm looking into this to fix bugs...

Jenkins, retest this please.

Test build #60798 has started for PR 13736 at commit 0c99ccf.

Test build #60801 has started for PR 13736 at commit 505c05b.

Test build #60796 has started for PR 13736 at commit 505c05b.

Test build #60796 has finished for PR 13736 at commit 505c05b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60796/
Test FAILed.

Merged build finished. Test FAILed.

Test build #60801 has finished for PR 13736 at commit 505c05b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60801/
Test PASSed.

Test build #60798 has finished for PR 13736 at commit 0c99ccf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

@rxin okay, ready to review. After the v2.0 release, plz check this.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/60798/
Test PASSed.

Merged build finished. Test PASSed.

Test build #64051 has started for PR 13736 at commit 7ccd981.

Test build #64051 has finished for PR 13736 at commit 7ccd981.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/64051/
Test PASSed.

Merged build finished. Test PASSed.

Test build #68862 has started for PR 13736 at commit 10dca0e.

Test build #68862 has finished for PR 13736 at commit 10dca0e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/68862/
Test PASSed.

I think this pr got stale, so I'll close this, thanks.


beforeAll function doesn't work as it should

Hey,
I found a bug with the beforeAll() function :
fdescribe('Test', function () {

    beforeAll(function () {
        console.log('Hey there !');
    });

    it('number #1', function () {
        expect(true).toBe(true);
    });

    it('number #2', function () {
        expect(true).toBe(true);
    });

    it('number #3', function () {
        expect(true).toBe(true);
    });

    it('number #4', function () {
        expect(true).toBe(true);
    });
});

This will output Hey there ! 5 times (which is weird considering there are only 4 tests) instead of one as expected. Using beforeEach() outputs the message 4 times, as it should.
I'm not sure if it's an issue with meteor-jasmine or if this happens with vanilla Jasmine as well.

Thanks for reporting. I think this is a Jasmine issue that may already be fixed in the latest version. I will test.

Coworker tested Jasmine 2.3 with Node, says it works fine, you may want to look for something wrong in this package.

Ok. sanjo:jasmine still uses Jasmine 2.1.

This has been fixed in Jasmine 2.3. I will upgrade now. https://github.com/jasmine/jasmine/issues/773

While you're at it, looks like afterAll() has the exact same behavior :p

Should be fixed with 0.17.0. https://github.com/Sanjo/meteor-jasmine/commit/2f5b3d02ed2dbd029fa39bfb2b2b5c48e8cb3685


 This is confusing since the dataset name only makes sense in the context of the collection (such as All Cells, this doesn't make sense unless you know it is Tabula Sapiens - All Cells). This ticket encompasses the work to incorporate the collection name into the filter.
Value: Without this work, users will not be able to use the Dataset filter and filter to the datasets they are interested in.
Figma

Reference source data information

If the filters are using SDS, there's a caption prop available.

SDS DropdownMenu has a storybook example of adding caption to the menu item!


Failed to update stats for container "%s": ... /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod{uuid}.slice/cpuacct.stat: no such file or directory, continuing to push stats

Rancher versions:
rancher/server or rancher/rancher: v1.6.15
rancher/agent or rancher/rancher-agent: v1.2.10
Infrastructure Stack versions:
healthcheck: v0.3.6
ipsec: v0.13.11
network-services: metadata:v0.10.2, network-manager:v0.7.20
scheduler:
kubernetes (if applicable): v1.9.5-rancher1-1
Docker version: (docker version,docker info preferred)
$ docker info
Containers: 26
 Running: 25
 Paused: 0
 Stopped: 1
Images: 28
Server Version: 1.12.6
Storage Driver: overlay2
 Backing Filesystem: xfs
 Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
 Volume: local
 Network: bridge null host overlay
Swarm: inactive
Runtimes: docker-runc runc
Default Runtime: docker-runc
Security Options: seccomp
Kernel Version: 3.10.0-693.17.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
Number of Docker Hooks: 3
CPUs: 4
Total Memory: 23.55 GiB
Name: be-ai07.wisers.com
ID: YC5G:TVF2:6HNT:COZT:JBEU:O4Y4:J2PP:AKWY:KTHN:M5BD:DYKB:ADVZ
Docker Root Dir: /d01/godbk/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Registries: docker.io (secure)

Operating system and kernel: (cat /etc/os-release, uname -r preferred)
$ uname -r
3.10.0-693.17.1.el7.x86_64

Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal

Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
single node rancher、internal DB

Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes

Steps to Reproduce:
Results:
Docker log increase massive below messages  on every nodes.
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.949966     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod28adb619_523b_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod28adb619_523b_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.950008     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2ad4197b_4c41_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod2ad4197b_4c41_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.956926     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-poda12dcaea_4dcd_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-poda12dcaea_4dcd_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.962373     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod1f3f8086_4b14_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod1f3f8086_4b14_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.962412     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod0ebdb2ff_4b8f_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod0ebdb2ff_4b8f_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.962417     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod0442152a_4b5f_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod0442152a_4b5f_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.964016     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-poda4837312_4bd3_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-poda4837312_4bd3_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.970741     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-podfc506680_4b78_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-podfc506680_4b78_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.976382     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod3349acd4_4a19_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod3349acd4_4a19_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:05 be-ai07 dockerd-current[27376]: W0514 04:50:05.985041     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod8235d8d2_43cf_11e8_991c_0226f04bebe2.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod8235d8d2_43cf_11e8_991c_0226f04bebe2.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:06 be-ai07 dockerd-current[27376]: W0514 04:50:06.005668     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod039cae17_4fd3_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod039cae17_4fd3_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:06 be-ai07 dockerd-current[27376]: W0514 04:50:06.006325     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod9ea4cd2a_414c_11e8_991c_0226f04bebe2.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod9ea4cd2a_414c_11e8_991c_0226f04bebe2.slice/cpuacct.stat: no such file or directory, continuing to push stats
May 14 12:50:06 be-ai07 dockerd-current[27376]: W0514 04:50:06.010756     386 container.go:507] Failed to update stats for container "%s": %s/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod20843c7f_4b1a_11e8_bf07_0226f0b58360.sliceopen /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod20843c7f_4b1a_11e8_bf07_0226f0b58360.slice/cpuacct.stat: no such file or directory, continuing to push stats

There are a lot /sys/fs/cgroup/cpuacct,cpu/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pod{uuid}.slice/ folders but empty(not check every folder).
Could anyone help, thanks.

This was fixed in v1.9.5-rancher1-3: https://github.com/rancher/rancher/issues/12640


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 1219 ms

Resolved: Bofrost.lu performance has improved in 3657719 after 9 minutes.


Notifications center background is blue in high contrast theme

VS Code version: Code - Insiders 1.21.0-insider (1a84a882737184488d965426747a05474f54a759, 2018-02-27T06:17:53.785Z)
OS version: Linux x64 4.13.0-36-generic

#44319

I don't think this background is used elsewhere?

@Tyriar we do, it is the editor widget background color that is e.g. also used for find widget:

The idea is to pick a background color that has some contrast to the editor because that is typically where notifications will appear on top of.


Add spire-1.7 and go-1.19

Upgrade spire to the latest version - 1.7.0
This requires go-1.19. I got it working using a configuration similar to 1.17. We can switch to upstream 1.19 when we upgrade to newer versions of nixpkgs.

Could you backport these two and add spire separately please?

https://github.com/NixOS/nixpkgs/pull/181797
https://github.com/NixOS/nixpkgs/pull/190037

Opened #123 for go-1.19 and changed this PR to only upgrade spire.

Opened #123 for go-1.19 and changed this PR to only upgrade spire.

Thank you!


Typescript aborts on shebang.

The compiler should allow shebangs to pass through.
http://stackoverflow.com/questions/23298295/how-to-make-a-shell-executable-node-file-using-typescript

I'm confused.  Why would this be part of the typescript compiler?  As your link shows, the more appropriate thing to do would be to add the script directive as part of the compilation pipeline with another tool.

cause ppl like to write their shell scripts in ts :)

Two reasons:

Even though shebangs may not be official Javascript spec, I'd expect Typescript to support Node.js Javascript fully, since Typescript is a Javascript superset and Node.js is popular Javascript platform.  The following is parsed by node, but not Typescript.

#!/usr/bin/env node
console.log('Hello world.');

Is it not easier to ignore the shebang in the Typescript compiler (only one in existence), than it is to add kludge compilation step that prepends the shebang (for N projects that use Typescript for node.js CLIs)?  ...  I guess you could counter argue N is small, but I'd think it was actually big.

cause ppl like to write their shell scripts in ts :)

+1 : )

+1 it be nice to build fully functioning shell scripts written in Typescript like I do with Python or Bash or Javascript, without involving an additional build step.

+1
I would very much like not having to type "node ..." in front of every TS CLI util / 'shell script', or having to create an almost-empty .js wrapper for them.
@CyrusNajmabadi: arguments for handling it in the compiler:

compile-on-save tools like Visual Studio, Atom Typescript or Sublimetext cannot be used on these files
it's not as easy as simply catting a line in front of it: it also e.g. involves updating the sourcemap
it either requires some kind of naming convention, or a manually maintained list of files that would need this transformation in the 'makefile'. I find such lists to be cumbersome, typically leading to unnecessary merge conflicts (like a Visual Studio project, or tsconfig's files property).

I filed this on codeplex quite a while back, and apparently so did this user.
As noted in my codeplex issue though, there are some things to take into consideration:

it's a bit dubious whether having #!/bin/env node at the top of a .ts file actually makes sense (because Node cannot run the .ts file directly). This is in contrast to e.g. Javascript or Python files, which can actually be directly run by their respective interpreter. Still, I'd rather have this than doing it 'manually' as a build step :)
the line-ending of such a line must be a Unix line-ending (even on Windows), as otherwise the shell will not correctly parse it (it will include the \r in the command's filename). This in turn will probably force all other line-endings in that file to be Unix too, to prevent messages when opening the file in an editor, source-code-control messages, etc.
on Linux, the file still won't be executable if the +x bit isn't set, so the compiler should probably do that automatically for such files.

Passing through only the first line this way seems plausible?

@RyanCavanaugh yes, but that first line must end with (just) a line-feed, and the emitted file needs to have the executable bit set on *nix.

We do not modify file properties usually. would not that be something you do in your build script?

@mhegazy yes, but then the script is still not executable (on non-Windows), so it won't help for the compile-on-save scenario.

We could extend the TS language to call "#..." another form of trivia.  We'd could then preserve it in the same way that we preserve copyright comments at the top of the file.

That would be a useful part of the solution yes.
For reference, our use-case at work is that we have quite a few handy little utils in our codebase, to restart services, initialize databases, etc. Often these very tools are used and developed in your typical edit-compile-run cycle while working on the main library that the tool interacts with.
For that scenario, it would be great not having to run the build system over-and-over again, as it takes at least a few seconds to run (even though we try to skip compilation for unmodified files etc).
At >100k lines of TS code, it takes quite some time just to 'initialize' gulp, and at this moment, the compile pipeline (TS, browserify, uglify, copyright, sourcemaps, etc.) is deemed too complex to 'fork' the pipeline to have a separate watch-version.
Visual Studio's compile-on-save produces almost instantaneous results, and we typically don't need more than that for most of these edit-compile-run cycles.
We develop and test on Windows, but use MSysGit's Bash as commandline. We also run all tests on a Linux machine.
So, our source files are stored with CRLF, and the emitted .js file contains CRLF. Having a simple passthrough, or 'exactly preserved' trivia will thus lead to that shebang line ending in CRLF. This doesn't work when trying to run the script in (MSysGit) Bash; many projects seem to have run into this.
On Windows, having the file output just LF would fix it: MSysGit can't use an executable bit, so it appears to read the first line of a file to see if it's a shebang, and if so, effectively assumes it's an executable.
On Linux, it's the other way around: the file would already be output with LF, but it still wouldn't be executable due to the missing +x bit. It's not that weird for compilers to set an executable bit though, that's basically what every C-compiler does too ;)
Not sure how hard this would be to add to the compiler though. I'd gladly give this up for solid CommonJS module support, to be honest ;)
TL;DR I think this would be the ingredients:

Detect the "#!..." (note the "!" too, just "#" is invalid) at the start of a file (only then), and store it as trivia
When emitting the file and it starts with that type of trivia:

Force line-endings to LF (to make it work on Windows)
Output that trivia as the first bytes of the file (e.g. no BOM)
Set the executable bit (on *nix)

:+1:

There seem to be two independent questions here:

how should tsc handle files with a shebang line?

should tsc explicitly write shebang lines if requested?

To the first question, the node interpreter can handle files with leading shebang lines:
$ cat q.js
#!/usr/bin/env node
console.log("hello world");
$ chmod +x q.js
$ node q.js
hello world
$ ./q.js
hello world

To the second question, a simple compiler flag (--shebang) that adds the line would be sufficient.  We already have options that control the output, like the --module option, so this isn't totally crazy

We got confused over which of two scenarios (or maybe both) people wanted here.
Someone might have a tool that compiles and runs a TypeScript file:
#/usr/bin/env run-ts
var x: string = 'hello world';
console.log(x);

In this case, you wouldn't want #/usr/bin/env run-ts emitted into the output JS.
Or, someone might want to compile their TS and then run the JS separately:
#/usr/bin/env node
var x: string = 'hello world';
console.log(x);
``
In this case, you *would* want `#/usr/bin/env node` emitted into the output JS.

Is one of these much more common than the other?

I use typescript to write command line node programs. e.g.
https://github.com/firebase/blaze_compiler
So the latter is more common for me (I want  #/usr/bin/env node emitted
into the JS file)
On Tue, May 19, 2015 at 9:49 AM, Ryan Cavanaugh<EMAIL_ADDRESS>wrote:

We got confused over which of two scenarios (or maybe both) people wanted
here.
Someone might have a tool that compiles and runs a TypeScript file:
#/usr/bin/env run-tsvar x: string = 'hello world';console.log(x);
In this case, you wouldn't want #/usr/bin/env run-ts emitted into the
output JS.
Or, someone might want to compile their TS and then run the JS separately:
#/usr/bin/env nodevar x: string = 'hello world';console.log(x);
``
In this case, you would want #/usr/bin/env node emitted into the output JS.
Is one of these much more common than the other?
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/2749#issuecomment-103588482
.

It seems like we could address this with a general facility to add something to the top of the file we emit.  i.e. you should be able to reference some sort of file containing preamble text that you'd like at the top of the emitted file.  This would be good for things like copyright headers, shebangs, etc.  And it would be nice be cause it would mean that TS wouldn't have to know about things like how people on unix want to execute files.

@RyanCavanaugh I think in the first scenario you mention, the "run-ts" tool would need to strip the shebang.  My gut tells me the second scenario is more common, but that may due to a personal bias.
@CyrusNajmabadi that could work, but my initial impression is that just allowing shebang lines to pass through is the all-around simpler solution.  Aside from leaking Unix-isms into Windows, is there any other issues you see with this approach?  I'd like to point out that node.js handles shebangs on Windows without problem and that the npm package.json expects them to be present in files specified in bin, otherwise it won't work as mentioned in this SO response.
I know, my point is node.js & npm specific, but I still think it's important.

@RyanCavanaugh yes, but that first line must end with (just) a line-feed, and the emitted file needs to have the executable bit set on *nix.

@poelstra It seems like the appropriate solution here is for you to set the executable bit on your TS file, and TSC should set the same bits on the output file.  I think even though it's related to the issue I opened (this one), I think that topic belongs it's own separate issue and shouldn't be discussed in detail here.

@RyanCavanaugh Like @tomlarkworthy, I would use it in your second way (run the .js, not .ts). For your first scenario, this 'feature' wouldn't be necessary at all, because run-ts could strip the shebang.
Nitpick: the line should start with #!, not just #.

@jdfreder Technically, the .ts file should not have its executable bit set, because that file cannot executed.
Given TSC's default behavior to put compiled .js files next to the .ts, this will help with tab-completion on the shell too: it will just find the .js when I would ./he<TAB> for ./helloworld.js.
Let's see where this goes, if needed I'll file a separate issue for the executable bit. It will already help on Windows if we have the shebang passthrough by itself, so I certainly wouldn't want to block 'your' topic on it :)

so I certainly wouldn't want to block 'your' topic on it :)

Ah thanks :) Exactly why I brought it up.

I have a Node.js project which I converted to TypeScript but now I have to manually add #!/usr/bin/env node to the top of the .js file after every change (which probably breaks the source map). It is not easy for me to arrange to have the .js file executed as node file.js rather than just file.js, so it would be handy if tsc just let the #!... pass through.

I have a Node.js project which I converted to TypeScript but now I have to manually add #!/usr/bin/env node to the top of the .js file

@jesseschalken hopefully its just .js file. In that case you can do what I describe here  https://github.com/npm/npm/issues/6674#issuecomment-108132800 Duplicated below:

See https://github.com/Microsoft/TypeScript/blob/master/bin/tsc for an example. Basically have a dummy file without the .js extension and just require the actual .js file. Also point the bin in package.json to this dummy file.
In file named tsc:
#!/usr/bin/env node
require('./tsc.js')

@basarat Yeah, I have a few things which assume that the repo contains only a single .js file which can be deployed on it's own. I can go to the effort to fix those assumptions, but it would be handy if I didn't have to, that's all.

@RyanCavanaugh I missed why your run-ts example required that tsc didn't emit the #!... line in it's output. I assume the theoretical run-ts command would be running the file through tsc and then to node, in which case it would be fine if the #!... was kept because node ignores it.
It seems me, after reading this thread, that the original request still stands: That tsc should tolerate a #!... line at the start of an input file and maintain it in the output file.
Regarding line endings: tsc apparently has the --newLine option to specify line endings (#1693), so you can just use that on Windows.
If you need the file to be executable, then you can chmod +x the .js file after the first compile and tsc will apparently keep it after subsequent compiles (according to my testing), and if you commit the .js file Git will also remember that it's executable.

@mhegazy I can implement this quite easily. Basically do it the same we parse out reference comments and store it in SourceFile, and then write it out on emit as is.
This is very similar to how babel does it as well (calls [parseShebang at the start] (https://github.com/babel/babel/blob/b91b4a4dc03eff8647b669c8935b18f0c6d7ed81/packages/babel/src/transformation/file/index.js#L636), and if the first line matches the regex stores it in a shebang property on what is effectively its sourceFile and then writes it out on emit). Would you be okay with a PR?

@basarat I think the problem is that there's no consensus yet on what should be done with a shebang.
@jesseschalken If a shebang is meant to be preserved, it implies that the .ts file is not run - the resultant .js is. But clearly there is a use case for other tools to run the .ts file directly with no resultant .js file.
One could imagine us omitting shebangs on output, but also allowing a prelude as @CyrusNajmabadi suggested.

I think the problem is that there's no consensus yet on what should be done with a shebang

Which is why I brought up babel to present a precedence. It just preserves it :rose:

@basarat we should do that. let me get back to you tomorrow, i will bring it up in the design meeting.

@DanielRosenwasser "But clearly there is a use case for other tools to run the .ts file directly with no resultant .js file."
I must be missing something. The only two ways some tool could "run" a .ts file would be:

Convert the TS into JS using tsc and pipe that into a JS interpreter such as node. node ignores a #! line in it's input, so it's fine if tsc kept it in its output. If the tool is using some other JS interpreter that doesn't support a #! line, then the tool can remove it.
Somehow run the TS without converting it to JS, in which case it won't be using tsc in the first place.

@basarat feel free to send a PR for this

@basarat

This is very similar to how babel does it as well (calls parseShebang at the start, and if the first line matches the regex stores it in a shebang property on what is effectively its sourceFile and then writes it out on emit). Would you be okay with a PR?

Sounds good.  However, i would prefer you parse it out as trivia instead of adding it as a special field on sourceFile.  As an example of where we have specialized trivia parsing, see the code i added so we can detect and handle git merge markers (i.e. "<<<<<< HEAD").   Then we can even do nice stuff like classify this guy properly in the editor and not barf on it while formatting.  yadda yadda yadda.

Then we can even do nice stuff like classify this guy properly in the editor and not barf on it while formatting

:+1: :rose: SyntaxKind.ShebangTrivia

If you wanted to send me the shebang syntax (it's just #!  right?), then i'd be happy to whip this up myself.

@CyrusNajmabadi Yup. I have some work on the scanner based on your suggestion that might be helpful https://github.com/Microsoft/TypeScript/compare/master...basarat:feat/shebang?expand=1
Looking forward to your work :rose:

I just PRed it

Awesome, thanks for moving forward with this everyone!

thanks @basarat

🌹

[image: Office dance]
On Tue, Aug 4, 2015 at 2:42 PM, Basarat Ali Syed<EMAIL_ADDRESS>wrote:

🌹
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/TypeScript/issues/2749#issuecomment-127770910
.

Thank you for fixing this!

I came up with a simple solution, described here.
<EMAIL_ADDRESS>

@woodie nice. As a heads up, check out our wiki's editor support page to get some vim plugins and more updated sytnax files.


Fix upload of crashlytics symbols for tvOS apps

cc @mihai8804858 https://github.com/fastlane/fastlane/pull/8588#issuecomment-318093214

Fixed.


[wiki] Typo

On https://github.com/microsoft/TypeScript/wiki/Performance
to be more compact than anonymous types (which the compiler might infer), which reduces the amount of time spend reading and writing declaration files (e.g. for incremental builds). Type inference is very convenient, so there's no need to do this

spend -> spent

Moved to https://github.com/microsoft/TypeScript-wiki/pull/264


Enhance Logging/Audit for key creation and purging.

Audit Events
Expose details logged below as internal Audit Event as well.
Meta to expose in API

Created Date

Info to log on creation
Info to log on purge

Username (currently shows user ID, internal long)
Key Type
Created Date

Although audit events are supported for repos and projects, the related SshKeyAccessGrantedEvent does not seem to include any details on which repo/project it was granted.
We've added the logging details of user and key details for creation and purge, but wil need to defer repo level audit logging.

Closed with paired delivery @jdesulme


fix(website): youtube embed component mobile sizing

Please describe the changes this PR makes and why it should be merged:
The YouTube embed on the "Back in Block" blog post looks broken on mobile:

This is actually already fixed on the /ai page. This PR brings that fix over to this blog post.

It also uses the aspect-ratio CSS property, which is now supported in all major browsers.
Status

[x] Code changes have been tested against prettier, or there are no code changes
[x] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[x] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[x] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

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

very epic matthew, thank you


phpmetrics will generate violations xml report

From the phpmetrics docs: PhpMetrics can export results in the PhpMessDetector violations output format.
This adds the flag to create the violations xml.

What's the difference between phpmetrics violations and phpmd violations? phpmd is well documented and ruleset can be overriden. I can't find anything about violations in phpmetrics.

I believe it's just outputting it's own collected data in the phpmd violations xml format, not specifically outputting phpmd data (and I could be wrong about that as the docs aren't specific either way). Here's where I found the info: http://www.phpmetrics.org/documentation/jenkins.html
In any case, users can choose to utilize the outputted file or not. I'm still experimenting with it to see if it is especially better or different than the output from the real phpmd.

I don't want to generate some file, just because tool can generate it. I wrote about that in https://github.com/EdgedesignCZ/phpqa/pull/17#issuecomment-214136398
Users can define phpmd' ruleset. Why should we confuse them with two pmd xml files? For example Jenkins can parse violations only from one file:

Isn't possible to define custom ruleset for phpmd with phpmetrics' rules? I would rather add notice to readme about phpmetrics ruleset than generate two pmd files

Sure, makes sense. I'll let you know if I find any additional details that would warrant including this. Thanks!


Extends spfx doctor command with support for SPFx v1.15.0. Closes #3432

Extends spfx doctor command with support for SPFx v1.15.0. Closes #3432
Comments
Noticed that in spfx doctor command past versions just specify a major version of Node.js. However for SPFx v1.15.0 this is not strict enough. This is why I specified a minor version.

Noticed that in spfx doctor command past versions just specify a major version of Node.js. However for SPFx v1.15.0 this is not strict enough. This is why I specified a minor version.

Good catch! 👏

Merged manually. Thank you! 🚀


Variable/Adam not found in checkpoint error when trying to restore the pre-trained model and finetune the network

I am trying to restore the pre-trained model and finetune the network. However it raised an error as follows when restoring the pre-trained model:

Key Variable/Adam not found in checkpoint
	 [[Node: save/RestoreV2 = RestoreV2[dtypes=[DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, ..., DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT, DT_FLOAT], _device="/job:localhost/replica:0/task:0/device:CPU:0"](_arg_save/Const_0_0, save/RestoreV2/tensor_names, save/RestoreV2/shape_and_slices)]]

If I put the code G_opt = tf.train.AdamOptimizer(learning_rate=lr).minimize(G_loss) after saver = tf.train.Saver() and saver.restore(sess, ckpt.model_checkpoint_path), the model could be restored succefully, though it raised another error when running _, G_current, output = sess.run([G_opt, G_loss, out_image], feed_dict={in_image: input_patch, gt_image: gt_patch, lr: learning_rate}) as follows:
FailedPreconditionError (see above for traceback): Attempting to use uninitialized value beta1_power
	 [[Node: beta1_power/read = Identity[T=DT_FLOAT, _class=["loc:@Adam/Assign_1"], _device="/job:localhost/replica:0/task:0/device:CPU:0"](beta1_power)]]

Seems like the error is related to the variables within the AdamOptimizer. Any suggestions about it?

I do not have a machine to run the code now. Can you try to remove Adam variables from the saver?
For example,
saver = tf.train.Saver(t_vars)
Let me know if the problem is solved.

Hi, thanks for the reply. I tried to remove Adam variables from the saver and it's not raising any errors now. However I printed out all the variables saved in the checkpoint file, and they are listed as follows:
('Variable', [2, 2, 256, 512])
('Variable_1', [2, 2, 128, 256])
('Variable_2', [2, 2, 64, 128])
('Variable_3', [2, 2, 32, 64])
('beta1_power', [])
('beta2_power', [])
('g_conv10/biases', [12])
('g_conv10/biases/Adam', [12])
('g_conv10/biases/Adam_1', [12])
('g_conv10/weights', [1, 1, 32, 12])
('g_conv10/weights/Adam', [1, 1, 32, 12])
('g_conv10/weights/Adam_1', [1, 1, 32, 12])
('g_conv1_1/biases', [32])
('g_conv1_1/biases/Adam', [32])
('g_conv1_1/biases/Adam_1', [32])
('g_conv1_1/weights', [3, 3, 4, 32])
('g_conv1_1/weights/Adam', [3, 3, 4, 32])
('g_conv1_1/weights/Adam_1', [3, 3, 4, 32])
('g_conv1_2/biases', [32])
('g_conv1_2/biases/Adam', [32])
('g_conv1_2/biases/Adam_1', [32])
('g_conv1_2/weights', [3, 3, 32, 32])
('g_conv1_2/weights/Adam', [3, 3, 32, 32])
('g_conv1_2/weights/Adam_1', [3, 3, 32, 32])
('g_conv2_1/biases', [64])
('g_conv2_1/biases/Adam', [64])
('g_conv2_1/biases/Adam_1', [64])
('g_conv2_1/weights', [3, 3, 32, 64])
('g_conv2_1/weights/Adam', [3, 3, 32, 64])
('g_conv2_1/weights/Adam_1', [3, 3, 32, 64])
('g_conv2_2/biases', [64])
('g_conv2_2/biases/Adam', [64])
('g_conv2_2/biases/Adam_1', [64])
('g_conv2_2/weights', [3, 3, 64, 64])
('g_conv2_2/weights/Adam', [3, 3, 64, 64])
('g_conv2_2/weights/Adam_1', [3, 3, 64, 64])
('g_conv3_1/biases', [128])
('g_conv3_1/biases/Adam', [128])
('g_conv3_1/biases/Adam_1', [128])
('g_conv3_1/weights', [3, 3, 64, 128])
('g_conv3_1/weights/Adam', [3, 3, 64, 128])
('g_conv3_1/weights/Adam_1', [3, 3, 64, 128])
('g_conv3_2/biases', [128])
('g_conv3_2/biases/Adam', [128])
('g_conv3_2/biases/Adam_1', [128])
('g_conv3_2/weights', [3, 3, 128, 128])
('g_conv3_2/weights/Adam', [3, 3, 128, 128])
('g_conv3_2/weights/Adam_1', [3, 3, 128, 128])
('g_conv4_1/biases', [256])
('g_conv4_1/biases/Adam', [256])
('g_conv4_1/biases/Adam_1', [256])
('g_conv4_1/weights', [3, 3, 128, 256])
('g_conv4_1/weights/Adam', [3, 3, 128, 256])
('g_conv4_1/weights/Adam_1', [3, 3, 128, 256])
('g_conv4_2/biases', [256])
('g_conv4_2/biases/Adam', [256])
('g_conv4_2/biases/Adam_1', [256])
('g_conv4_2/weights', [3, 3, 256, 256])
('g_conv4_2/weights/Adam', [3, 3, 256, 256])
('g_conv4_2/weights/Adam_1', [3, 3, 256, 256])
('g_conv5_1/biases', [512])
('g_conv5_1/biases/Adam', [512])
('g_conv5_1/biases/Adam_1', [512])
('g_conv5_1/weights', [3, 3, 256, 512])
('g_conv5_1/weights/Adam', [3, 3, 256, 512])
('g_conv5_1/weights/Adam_1', [3, 3, 256, 512])
('g_conv5_2/biases', [512])
('g_conv5_2/biases/Adam', [512])
('g_conv5_2/biases/Adam_1', [512])
('g_conv5_2/weights', [3, 3, 512, 512])
('g_conv5_2/weights/Adam', [3, 3, 512, 512])
('g_conv5_2/weights/Adam_1', [3, 3, 512, 512])
('g_conv6_1/biases', [256])
('g_conv6_1/biases/Adam', [256])
('g_conv6_1/biases/Adam_1', [256])
('g_conv6_1/weights', [3, 3, 512, 256])
('g_conv6_1/weights/Adam', [3, 3, 512, 256])
('g_conv6_1/weights/Adam_1', [3, 3, 512, 256])
('g_conv6_2/biases', [256])
('g_conv6_2/biases/Adam', [256])
('g_conv6_2/biases/Adam_1', [256])
('g_conv6_2/weights', [3, 3, 256, 256])
('g_conv6_2/weights/Adam', [3, 3, 256, 256])
('g_conv6_2/weights/Adam_1', [3, 3, 256, 256])
('g_conv7_1/biases', [128])
('g_conv7_1/biases/Adam', [128])
('g_conv7_1/biases/Adam_1', [128])
('g_conv7_1/weights', [3, 3, 256, 128])
('g_conv7_1/weights/Adam', [3, 3, 256, 128])
('g_conv7_1/weights/Adam_1', [3, 3, 256, 128])
('g_conv7_2/biases', [128])
('g_conv7_2/biases/Adam', [128])
('g_conv7_2/biases/Adam_1', [128])
('g_conv7_2/weights', [3, 3, 128, 128])
('g_conv7_2/weights/Adam', [3, 3, 128, 128])
('g_conv7_2/weights/Adam_1', [3, 3, 128, 128])
('g_conv8_1/biases', [64])
('g_conv8_1/biases/Adam', [64])
('g_conv8_1/biases/Adam_1', [64])
('g_conv8_1/weights', [3, 3, 128, 64])
('g_conv8_1/weights/Adam', [3, 3, 128, 64])
('g_conv8_1/weights/Adam_1', [3, 3, 128, 64])
('g_conv8_2/biases', [64])
('g_conv8_2/biases/Adam', [64])
('g_conv8_2/biases/Adam_1', [64])
('g_conv8_2/weights', [3, 3, 64, 64])
('g_conv8_2/weights/Adam', [3, 3, 64, 64])
('g_conv8_2/weights/Adam_1', [3, 3, 64, 64])
('g_conv9_1/biases', [32])
('g_conv9_1/biases/Adam', [32])
('g_conv9_1/biases/Adam_1', [32])
('g_conv9_1/weights', [3, 3, 64, 32])
('g_conv9_1/weights/Adam', [3, 3, 64, 32])
('g_conv9_1/weights/Adam_1', [3, 3, 64, 32])
('g_conv9_2/biases', [32])
('g_conv9_2/biases/Adam', [32])
('g_conv9_2/biases/Adam_1', [32])
('g_conv9_2/weights', [3, 3, 32, 32])
('g_conv9_2/weights/Adam', [3, 3, 32, 32])
('g_conv9_2/weights/Adam_1', [3, 3, 32, 32])

I observed that there are only four variables which are ('Variable') ('Variable_1') ('Variable_2') ('Variable_3') that don't have corresponding /Adam and /Adam_1. So I am thinking is it because this checkpoint is saved without these transposed convolution weights being updated with Adam optimizer? And I am not sure if I just remove the Adam variables from the saver, would that lead to a not very well weights point as it was originally pre-trained?
Also I have another question about the usage of GPU. Do I need to modify the code and specify the usage of GPU device in order to use it? I basically just downloaded the code and ran it, and it's taking a long time up to over 40 hours. And I am not quite sure if I am actually using GPU or not...? Thanks!


fix(plugins/plugin-kubectl): kubectl watchers stop receiving push notifications when context is changed

Fixes #7747

Description of what you did:

My PR is a:

[ ] 💥 Breaking change
[x] 🐛 Bug fix
[ ] 💅 Enhancement
[ ] 🚀 New feature

Please confirm that your PR fulfills these requirements

[x] Multiple commits are squashed into one commit.
[x] The commit message follows Conventional Commits, which allows us to autogenerate release notes; e.g. fix(plugins/plugin-k8s): fixed annoying bugs
[x] All npm dependencies are pinned.

/lgtm


Could add the ruby version for bundle config path?

$ bundle config path /Users/whirlwind/.bundle/vendor

$ rvm use 2.5.0  # ruby 2.5
$ bundle install
Installing psych 2.2.2 with native extensions
Bundled gems are installed into `/Users/whirlwind/.bundle/vendor`

$ rvm use system # ruby 2.6
$ bundle install
Ignoring psych-2.2.2 because its extensions are not built. Try: gem pristine psych --version 2.2.2
Installing psych 2.2.2 with native extensions
Bundled gems are installed into `/Users/whirlwind/.bundle/vendor`

$ rvm use 2.5.0  # ruby 2.5
$ bundle install
Using psych 2.2.2    <- Will not reinstall psych!!!!!!!
Bundled gems are installed into `/Users/whirlwind/.bundle/vendor`

$ pod --help
/Users/whirlwind/.rvm/rubies/ruby-2.5.0/lib/ruby/2.5.0/yaml.rb:5: warning: It seems your ruby installation is missing psych (for YAML output).
To eliminate this warning, please install libyaml and reinstall your ruby.

I want to use bundle config path to custom a path to install all gems. But they will be installed in a path without any ruby version information.
If I use the $GEM_HOME or $GEM_PATHS, the rubygem will append the ruby/2.5.0 to the path.
I think the gems should be installed at /Users/whirlwind/.bundle/vendor/ruby/VERSION. Right?

I found that:
If I use the bundle config path --global, I get the ~/.bundle/config:
---
BUNDLE_PATH: "/Users/whirlwind/.bundle/vendor"

The gems will be installed into `/Users/whirlwind/.bundle/vendor/gems/".
If I use the bundle install --path=.bundle/vendor, I get the .bundle/config:
---
BUNDLE_PATH: ".bundle/vendor"

The gems will be installed into .bundle/vendor/ruby/2.6.0/gems. It has the ruby version !!
It is different between the global and local configuration.

This should be fixed in bundler 2.1.0.pre.2, I think. Can you try with that version?

It works for bundler 2.1.0.pre.2 !

Thanks for confirming. Closing as fixed by https://github.com/bundler/bundler/pull/7163.


Add 18Kami

Closes #3375
Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[ ] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[ ] Have not changed source names
[ ] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[x] Have removed web_hi_res_512.png when adding a new extension

Hey, looks like the extension is up!! Just tested it, but it's not loading images in any selection.


LUCENE-10002: Replace simple usages of TotalHitCountCollector with IndexSearcher#count

This is one of the many steps required to resolve LUCENE-10002
In case only number of documents are collected, IndexSearcher#search(Query, Collector) is commonly used, which does not use the executor that's been eventually set to the searcher. Calling IndexSearcher#count(Query) makes the code more concise and is also more correct as it honours the executor that's been set to the searcher instance.

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[ ] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[ ] I have added tests for my changes. (refactoring, not needed)

I pushed an update that address your comments @jpountz , thanks for your review!

Thanks @jpountz it should be ready for now, for real this time ;)


ImportError: cannot import name 'Literal' from 'typing' (/opt/conda/lib/python3.7/typing.py)

For python version <3.8, Literal import is creating and issue in text_splitter.py

ImportError                               Traceback (most recent call last)
/tmp/ipykernel_23/446338945.py in
----> 1 from xturing.datasets.instruction_dataset import InstructionDataset
2 from xturing.models import BaseModel
3
/opt/conda/lib/python3.7/site-packages/xturing/init.py in
3 configure_external_loggers()
4
----> 5 from .datasets import BaseDataset, InstructionDataset, TextDataset
6 from .engines import (
7     BaseEngine,
/opt/conda/lib/python3.7/site-packages/xturing/datasets/init.py in
1 from .base import BaseDataset
----> 2 from .instruction_dataset import InstructionDataset, InstructionDatasetMeta
3 from .text2image_dataset import Text2ImageDataset
4 from .text_dataset import TextDataset, TextDatasetMeta
5
/opt/conda/lib/python3.7/site-packages/xturing/datasets/instruction_dataset.py in
11 from xturing.datasets.base import BaseDataset
12 from xturing.model_apis import TextGenerationAPI
---> 13 from xturing.self_instruct import (
14     bootstrap_instructions,
15     generate_instances,
/opt/conda/lib/python3.7/site-packages/xturing/self_instruct/prepare_seed_tasks.py in
7
8 from xturing.model_apis import TextGenerationAPI
----> 9 from xturing.utils.text_splitter import RecursiveCharacterTextSplitter
10
11
/opt/conda/lib/python3.7/site-packages/xturing/utils/text_splitter.py in
6 import logging
7 from abc import ABC, abstractmethod
----> 8 from typing import (
9     AbstractSet,
10     Any,

Hi @jatintyagi7,
Thank you for rasing it. In the meantime, could you upgrade Python to 3.8 or 3.9 and try again? xTuring should work with python>=3.8.

Hi I am trying this in kaggle notebook, not sure whether the python upgrade is feasible there or not

@Toan-Do there is one solution which will make it work:
please replace the
from typing import Literal
with
try:
from typing import Literal
except ImportError:
from typing_extensions import Literal


image_patcher.sh: Relies on crossystem being present on the system, will not work as bootstrap from a non-ChromeOS system

image_patcher.sh, line 399: readarray -t csys_lines <<<"$(csys)"
csys is defined earlier (line 73):
csys() {
    if [ "$COMPAT" == "1" ]; then
        crossystem "$@"
    elif test -f "$ROOT/usr/bin/crossystem.old"; then
        "$ROOT/usr/bin/crossystem.old" "$@"
    else
        "$ROOT/usr/bin/crossystem" "$@"
    fi
}

Perhaps a default output to use would be the best route to go? crossystem contains some device-specific outputs, so we'll have to see.

 FML


SOS emoji to request assistance from bounty creator not working

Describe the bug
Once user has claimed a bounty and is working on it, they may want to reach out to the bounty creator via the SOS (help) emoji. Pressing this should send a DM to the creator, but currently this button does not do this.
To Reproduce
Steps to reproduce the behavior:

Go to '/bounty create' and fill in title, reward, then in DMs, supply description and completion criteria, then press publish.
Back in the BBBS server, cheese-bounty-board channel Click on black flag to claim bounty.
After claiming, three new emojis appear, submit, refresh and help, press SOS button for help.
See no activity.

Expected behavior
Upon clicking SOS, should receive DM from bounty creator to answer any questions regarding bounty.
Screenshots
Bot not responding after this:

Desktop (please complete the following information):

OS: macOS version 11.4
Browser: Chrome
Version: Version 96.0.4664.55 (Official Build) (x86_64)

Additional context
Add any other context about the problem here.

This is a bountybot issue, closing


Tests in tests/ cannot be run in Linux

name: Bug report
about: Create a report to help us improve
title: '' Tests in tests/ cannot be run in Linux #10 "
labels: ''"
assignees: ''"

Describe the bug
tests don't run in Linux when the command coverage run -m pytest tests/ is run.
To Reproduce
Steps to reproduce the behavior:

Go to root directory
Run coverage run -m pytest tests/

Expected behavior
Tests should be run

Absolutely approved. I've invited you as a collaborator as well, and feel free to submit the PR.


Fixed a bug that causing gap to appear in products using team sidebar…

Summary
Fixed a bug that caused a gap to appear in products using team sidebar when user had only 1 team
Ticket Link
https://github.com/mattermost/mattermost-server/issues/19309
Related Pull Requests
None
Screenshots
Before:

After:

Release Note
Fixed a bug that caused a gap to appear on the left in products using the team sidebar.

@hmhealey can you review this one? I found a way simpler fix for the issue.

Awesome, that looks a lot cleaner. It also works in all the problem cases we ran into with the announcement bar and mobile view.


Runtime: Handle synthesized decl "related entity" tags.

Clang-importer-synthesized declarations get an extra tag character included in their mangling, which was not being preserved in type context descriptors. This caused runtime lookup for these synthesized types to fail. Fix this by adding the tag information to type context descriptors and teaching the runtime to match it up when fetching metadata by mangled name. Fixes rdar://problem/40878715.

@swift-ci Please test

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - e3776801e84bb9db712c38dd7ef57d95c783a22f

Build failed
Swift Test OS X Platform
Git Sha - e3776801e84bb9db712c38dd7ef57d95c783a22f

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - c82550c01f48bf1df490fd7e6776b86a1bd5dc9e

Build failed
Swift Test Linux Platform
Git Sha - c82550c01f48bf1df490fd7e6776b86a1bd5dc9e

@DougGregor Thanks! The existing RemoteAST tests exercise this behavior; now that we correctly include the related entity tag when we _buildDemanglingForMetadata, the MetadataReader now has to interpret it correctly.

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 58fa6f925ab26bcbcaf3a6ab241f599e6d087b1e

Build failed
Swift Test Linux Platform
Git Sha - 58fa6f925ab26bcbcaf3a6ab241f599e6d087b1e

@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - bbb1e917794de7f38a116b0ae68aaf13f5186509

Build failed
Swift Test OS X Platform
Git Sha - bbb1e917794de7f38a116b0ae68aaf13f5186509


Azure SendGrid signup broken

Expected content
Hi, I have tried everywhere to get support for this.  I am trying to sign up for SendGrid on Azure but it won't load the legal terms and therefore won't allow me to sign up.  I have tried Azure support, SendGrid support, no-one will even allow me to open a ticket.
The error SendGrid Create a new SendGrid Account in azure is initially:

We were unable to get information for your resources.

Then it says:

Part's onInputsSet promise failed.(id: Microsoft_Azure_Marketplace-fx-010-00b) Error: message: LegalTermsGrid.onLegalTermsAccepted() must not be called before the legal terms have finished loading. stack: Error: LegalTermsGrid.onLegalTermsAccepted() must not be called before the legal terms have finished loading. at n.onLegalTermsAccepted (https://afd.hosting.portal.azure.net/marketplace/Content/Dynamic/8GSLuiIynVbf.js:4:30103) at Object.mapOutgoingDataForCollector (https://afd.hosting.portal.azure.net/marketplace/Content/Dynamic/8GSLuiIynVbf.js:6:2803) at f._discardEditScopeAndSendResult (https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:300:2689) at i (https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:300:2257) at https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:300:2352 at https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:70:565 at Array.map () at Object.triggerCallbacks (https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:70:537) at r.n.updatePartInputValues (https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:68:1674) at r.updatePartInputValues (https://portal.azure.com/Content/Dynamic/adaluICNCNBe.js:72:2088)
Reload tile
Summary
Session ID
60819f992d3f49e888fdfe5be85b5cc9
Resource ID
Not available
Extension
Microsoft_Azure_Marketplace
Content
LegalTermsV2Part
Error code
500

Link to page:
https://portal.azure.com/#

Hey I noticed your post and I am getting a similar error for an Azure subscription. There is something wrong with the Azure portal controls - definitely a Microsoft bug. I am seeing something like this for the integration account and logic app controls. I have not seen many people with this kind of error. I know some Microsoft people and will be contacting them directly and will definitely mention your issue too.

Hey Ian, we identified the issue is related to permissions. Try getting your admin to grant you owner rights for SendGrid and see if your error goes away.

Thanks @clineer for addressing this! Once I get confirmation that @IanElsinga is successful I will close this issue.

Thanks @Whatthefoxsays

Hi @clineer thanks very much for addressing this, but it still doesn't work.  Same message when creating a sendgrid account:  "We were unable to get information for your resources" and then the same error message as above.
I am not sure what you mean by granting owner rights for SendGrid - I am the admin, and I am trying to add a SendGrid resource so I can't even create the resource.
Very much appreciate anything you can do - it's frustrating that I can't report azure bugs as our subscription as a Microsoft Partner does not allow that.

I found if you private message @AzureAupport on Twitter they give you some support there. I did mention your issue to them already. I can reply back to them too. Do you have a Twitter handle?

Oh ok, you can use @ianelsinga
Thanks!

I get the exact same error as Global Admin:

When clicking OK, I get:

And now it suddenly worked ...

I just tried a couple of times, refreshing the page, exact same error as @Agazoth pasted above...

I have a similar error happening again and it continues failing in IE Edge and not in Chrome so the browser has something to do with it but I am just not sure why.

All my attempts were in Chrome...

Did this issue get resolved? I got same problem now.

Never resolved.  I had to give up on it.   It's been about 3 months and the bug is still there.  I'm very wary of putting anything mission-critical on Azure as a result of this experience!

I found there is an error, "BadRequest".
It seems Azure API returned this.
I tried another mail service, MailJet got the same result.

I am having a similar issue. I am not getting any errors during setup. However, once setup in Azure is complete and I click on the Manage link, I cannot log in with the username and password I provided during setup. I have also not received a validation email from SendGrid, which is why I think I can't log in yet. SendGrid site says you cannot log in until you have validated your email.

I got the MS response, SendGrid service is not available in China.

Well its July 29th and I have this exact issue. Created an account, unable to access it through the send-grid website. Unable to delete it from azure, unable to create a new one.. I am hosed

I tried changing first/last name and other contact details 10+ times throughout a few days, and it finally went through. So might be some validation issue from the SendGrid side.

I had a similar issue and my user was already owner of the subscription and resource group where SendGrid was created. After adding the owner role explicitly to the SendGrid service, everything works.
It seems that role inheritance is broken.

Was this even investigated before it was closed?

Yeah I agree it seemed like it wasn't solved
Get Outlook for iOShttps://aka.ms/o0ukef

From: Lloyd Atkinson @.>
Sent: Tuesday, May 25, 2021 3:33:12 PM
To: sendgrid/docs @.>
Cc: Ben Cline @.Integrators.com>; Mention @.>
Subject: Re: [sendgrid/docs] Azure SendGrid signup broken (#5474)
Was this even investigated before it was closed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/sendgrid/docs/issues/5474#issuecomment-848204817, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJ2OIRIW4ASULVZRVTXHT73TPP3PRANCNFSM4IKXREQQ.


Remove double 'v' in built file header

Are there any rules for package.json version field tha we should be following? Quick look suggst that the v would be stripped by semver, but is that all we need to account for?

Looks like this is incorrect. The version field should never start with a v according to https://docs.npmjs.com/creating-a-package-json-file#required-name-and-version-fields

Since VERSION is set from github.event.release.tag_name we can just make sure the tag has no v in it and everything should be good

I would not remove the v in the tag name since it's a very common (good?) practice in most projects to name the release tag v{version-number}. For example, when drafting a new release, GitHub suggests the following:

Tagging suggestions: It’s common practice to prefix your version names with the letter v. Some good tag names might be v1.0 or v2.3.4. If the tag isn’t meant for production use, add a pre-release version after the version name. Some good pre-release versions might be v0.2-alpha or v5.9-beta.3.

Also, all Chart.js release tags are now prefixed with v and I'm not sure it's a good idea to get rid of it without having to technically need to do it.
I would suggest to rename the 3.0.0-beta.6 tag to v3.0.0-beta.6.


preprocessing is now too aggressively disabled

In cyassimp 1.0.0 we import unique verticies per triangle, which is a break in expected behavior.

i cry evertim

This has turned into a big mess that is just too low priority to sort right now (the high priority being getting everything to menpo 0.6 and preparing for ICCV)
I'm going to pull the 1.0.0 release, as it does not provide the functionality we wanted. At some time in new year (or nearer if needed by someone) we will take the time to properly address this bug. For now, we will press forward with a bump in the version of numpy only.


Use ghcup to install GHC on linux and remove docs and profiling libs

See https://github.com/actions/virtual-environments/pull/4016 for discussion and reasoning

/azp run ubuntu1804, ubuntu2004

@hasufell it looks like we don't need these
https://github.com/actions/virtual-environments/blob/3a8831b648dc326403ca2b02da9f98db7154bc7b/images/linux/scripts/installers/haskell.sh#L17-L22
and these lines anymore
https://github.com/actions/virtual-environments/blob/3a8831b648dc326403ca2b02da9f98db7154bc7b/images/linux/scripts/installers/haskell.sh#L51-L54

@miketimofeev fixed

/azp run ubuntu1804, ubuntu2004

https://github.visualstudio.com/virtual-environments/_build/results?buildId=116192&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=5431112d-2b61-5a5f-7042-ef698f761043&l=6504
We don't install into /opt/ghc anymore.

https://github.visualstudio.com/virtual-environments/_build/results?buildId=116192&view=logs&j=011e1ec8-6569-5e69-4f06-baf193d1351e&t=5431112d-2b61-5a5f-7042-ef698f761043&l=6504
We don't install into /opt/ghc anymore.

yeah, could you please fix the test?
https://github.com/actions/virtual-environments/blob/main/images/linux/scripts/tests/Haskell.Tests.ps1

I removed the directory tests.

/azp run ubuntu1804, ubuntu2004

@hasufell sorry, forgot about one more place to change
https://github.com/actions/virtual-environments/blob/baabb70137a0d37b80d833010c4c3bb9ba84d207/images/linux/scripts/SoftwareReport/SoftwareReport.Common.psm1#L278-L279
we don't need $aptSourceRepo and  (apt source repository: $aptSourceRepo) anymore

Fixed

/azp run ubuntu1804, ubuntu2004

Should be done

/azp run ubuntu1804, ubuntu2004

@hasufell thanks for your contribution! The changes will be available next week.


#39 Update for Senzing Python SDK package

Pull request questions
Which issue does this address
Issue number: #39

#38

#38


[CSL-273] Make shortcut for MonadDialog

@martoon
Currently, MonadDialog BinaryP is placed all over the code, need to extract it to separate value (as well as BinaryP), so that changing packing type on need would be simplier

@martoon
Status: Got rid of BinaryP everywhere, except of DHT code


Create new content for Apps Lifecycle topic

Summary
The following topics in the Apps section will have new content created:

[x] Lifecycle

[x] Callbacks

Support for MermaidJS diagrams was also added.

Hello @neflyte,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@levb - Your feedback has been incorporated into this PR, and this PR is now ready for your review. Thanks!