Add a custom constructor to ServiceMockFacade and make default private

Summary:
The tests previously used the facade as soon as a task was running and did not realize when the task failed (e.g. when failing to bind to the configured port). The custom constructor ensures that the facade is only used when the task actually responds to a request.
Note: RestartIntegrationTest is not applicable to releases/1.4 since dependent test classes are not present.
cherry-picked from master 8814cda7439e117adcd7caa34894c321fb0bfe74
Addresses MARATHON-1840, MARATHON-6993, MARATHON-7000
Test Plan: integration:test
Reviewers: timcharper, zen-dog, jenkins, unterstein, jeschkies
Reviewed By: zen-dog, jenkins, unterstein
Subscribers: marathon-team
Differential Revision: https://phabricator.mesosphere.com/D589
Conflicts:
src/test/scala/mesosphere/marathon/integration/ReadinessCheckIntegrationTest.scala
src/test/scala/mesosphere/marathon/integration/RestartIntegrationTest.scala

retest this please

retest this please


check-capitalization: Check for banned words.

Fixes #8619

@timabbott, this is ready for review.

Nice, merged, thanks @umairwaheed!


[Bug]: make shell fails because of missing yum-config-manager in latest public.ecr.aws/amazonlinux/amazonlinux:2

Installation method
Own AWS account
What happened?
make shell  fails with the following error message (image build fails):
❯ make shell
bash hack/shell.sh '' ''
Building container images...
Dockerfile:12
--------------------
  10 |     ADD scripts/installer.sh /tmp/installer.sh
  11 |
  12 | >>> RUN bash /tmp/installer.sh
  13 |
  14 |     ADD scripts/entrypoint.sh /entrypoint.sh
--------------------
ERROR: failed to solve: process "/bin/sh -c bash /tmp/installer.sh" did not complete successfully: exit code: 1
make: *** [shell] Error 1

Running docker build from outside the Makefile shows that the error occurs because yum-config-manager is not found.
❯ docker build -t eks-workshop-environment .
[+] Building 28.0s (8/14)                                                                                docker:desktop-linux
 => [internal] load build definition from Dockerfile                                                                             0.0s
 => => transferring dockerfile: 617B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for public.ecr.aws/amazonlinux/amazonlinux:2                                                        0.0s
 => [ 1/10] FROM public.ecr.aws/amazonlinux/amazonlinux:2                                                                        0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 497B                                                                                0.0s
 => [ 2/10] RUN yum install -y shadow-utils && useradd     --home "/home/ec2-user"     --create-home     --user-group     --she  7.9s
 => [ 3/10] ADD scripts/installer.sh /tmp/installer.sh                                                                           0.0s
 => ERROR [ 4/10] RUN bash /tmp/installer.sh                                                                                20.0s
------
 > [ 4/10] RUN bash /tmp/installer.sh:
0.622 Package 1:findutils-4.5.11-6.amzn2.aarch64 already installed and latest version
0.623 Package diffutils-3.3-5.amzn2.aarch64 already installed and latest version
0.707 Package amazon-linux-extras-2.0.3-1.amzn2.noarch already installed and latest version
6.133 Failed to get D-Bus connection: Operation not permitted
8.114 WARNING: Running pip install with root privileges is generally not a good idea. Try `pip3 install --user` instead.
11.92 kubectl: OK
12.12 helm.tar.gz: OK
13.48 eksctl_Linux_amd64.tar.gz: OK
16.30 qemu-x86_64: Could not open '/lib64/ld-linux-x86-64.so.2': No such file or directory
17.04 You can now run: /usr/local/bin/aws --version
17.71 kubeseal.tar.gz: OK
18.46 yq: OK
19.11 flux.tar.gz: OK
19.45 /tmp/installer.sh: line 96: yum-config-manager: command not found
19.52 Loaded plugins: ovl, priorities
19.58 No package terraform-1.5.5-1.x86_64 available.
19.62 Error: Nothing to do
------
Dockerfile:12
--------------------
  10 |     ADD scripts/installer.sh /tmp/installer.sh
  11 |
  12 | >>> RUN bash /tmp/installer.sh
  13 |
  14 |     ADD scripts/entrypoint.sh /entrypoint.sh
--------------------
ERROR: failed to solve: process "/bin/sh -c bash /tmp/installer.sh" did not complete successfully: exit code: 1

Fix / workaround is to add yum-utils to Dockerfile
What did you expect to happen?
Successfully launch shell for testing.
How can we reproduce it?
Run make shell.
Anything else we need to know?
n/a
EKS version
n/a

Commit 122bec4 fixed the issue. Thanks @niallthomson


Questions about bmf_lite

Does bmf_lite really need QNN to run all android demos? Or is it just needed for Vincent chart demo.
Is there an executed bmf program for us to use, or can you provide some documentation on cross-compiling bmf_lite?

The QNN framework seems just support linux and windows but macOS. So i want to know how to disable the module that depends QNN.

The QNN framework seems just support linux and windows rather than macOS. So i want to know how to disable the module that depends QNN.

I successfully disable the BMF_LITE_ENABLE_TEX_GEN_PIC in the CMake file.
But i meet another problem that app can't correctly process the second demo in the Emulator or my android phone.
D/bmf-demo-app AlgRenderer: algorithmInterface initAlg ret = -600
D/bmf-demo-app AlgRenderer: algProcess,type = DENOISE,input-oesTexId = 1 2dTexId = 6 algOutputTex = -1 ret = -600
W/om.bmf.lite.app: [SurfaceTexture-1-4174-0] bindTextureImage: clearing GL error: 0x500
E/bmf_lite: [gl_helper.h, get_local_size_and_header, 190]invalid local size with input local_x:16, local_y:16, local_z:1
E/bmf_lite: [gl_helper.h, build_program, 58]gen_local_size_and_header error
E/bmf_lite: [denoise.cpp, init, 123]compile program denoise error
E/bmf-demo-app AlgRenderer: algorithmInterface init setInitParam ret = -600, algTypeIndex = 2

And the app crashes if i run first demo.
BTW, i update the gradle version to 7.4 to be compatible with my android studio 2022, and used java 17.
Anyway, may you give me the app apk to let me try first?


Port Microsoft.Build to .NET Core

This pull request finishes the changes necessary to successfully compile Microsoft.Build for .NET Core.  Lots of code which depended on features which weren't available was simply disabled, so more work will be needed to make sure that the code works on .NET Core.

LGTM

LGTM. I would just like to know the reasoning behind Compile include vs #if inside the file.


Build Error on Windows, Because _WIN32_WINNT  not defined.

We can fix this error by this pr:https://github.com/grpc/grpc/pull/14574.
Modify include/grpc/impl/codegen/port_platform.h:
move #include <Windows.h> before where check _WIN32_WINNT macro.

https://github.com/grpc/grpc/pull/14574 fixes this issue.


feat: Adds drill to detail context menu to Table

SUMMARY
Adds drill-to-detail context menu to Table chart when right-clicking on the rows. The context menu is only displayed if the table contains aggregated data.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/186236677-8eb54e4d-1bca-487f-8e2b-cbd0f14937ef.mov
TESTING INSTRUCTIONS
1 - You should be able to right-click on the rows in a table with aggregated data.
2 - Check the value and formatted value when right-clicking
3 - You should NOT be able to right-click on the rows in a table with raw data.
ADDITIONAL INFORMATION

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

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

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

/testenv up FEATURE_DRILL_TO_DETAIL=True

/testenv up FEATURE_DRILL_TO_DETAIL=true


🐧 rockylinux flavor

Currently the image definition is there, but lacks few things in order to boot properly. This card is to make the rockylinux flavor functional and into releases.

Getting this when running it in QEMU TCG with emulated CPU:
Fatal glibc error: CPU does not support x86-64-v2

Locally workarounded by enabling kvm (--enable-kvm) and set CPU passthrough (-cpu host).
https://www.phoronix.com/news/RHEL-9-x86-64-v2-Plans/https://www.phoronix.com/news/RHEL9-Drop-Old-CPUs-Fedora-ELN Affects all the way down


fix: Fix the parsing error of evalscope with the inference returned by the sglang engine.

Upon testing sglang's inference performance with evalscope, we encountered issues where evalscope failed to parse some of the returned data after prompt inference due to missing objects at the end. We have implemented fixes to resolve these parsing errors.

We fixed this issue ourselves two weeks ago but hadn't submitted a pull request (PR) yet. Now that someone has submitted a similar PR, I have closed it for now.


Resources version handling

Codecov Report

:exclamation: No coverage uploaded for pull request base (overall-fixes@89906a4). Click here to learn what that means.
The diff coverage is n/a.

@@               Coverage Diff                @@
##             overall-fixes      #68   +/-   ##
================================================
  Coverage                 ?   73.78%
================================================
  Files                    ?       26
  Lines                    ?      473
  Branches                 ?        0
================================================
  Hits                     ?      349
  Misses                   ?      124
  Partials                 ?        0

Continue to review full report at Codecov.

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

All updates made and merged in the last PR (#76) in this nested chain of collection execution PRs


sample not working with latest version of flutter

failing with:
Error: Member not found: 'packageRoot'.
io.Platform.packageRoot; // ignore: deprecated_member_use
[√] Flutter (Channel stable, 2.10.4, on Microsoft Windows [Version 10.0.22000.556], locale en-DE)
[√] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Enterprise 2019 16.11.8)
[√] Android Studio (version 2020.3)
[√] VS Code (version 1.66.1)
[√] Connected device (4 available)
[√] HTTP Host Availability

Upgrading to version 3.7.3 can solve this problem.
dependencies:
  flutter_foreground_task: ^3.7.3


Import subscription contents in batches grouped by subscriber

We are seeing a problem where we are importing subscription contents in constant sized batches which could lead to not importing all the subscription contents for a particular subscriber in one go.
This can lead to users receiving duplicate emails for a content change since the deduplication relies on the assumption that all subscription contents are imported.
The alternative would be to import all subscription contents in one go, but that prevents us from being able to start sending emails as quick as possible as it can take a bit of time to generate the emails in the first place. It would also lead to a huge delivery queue which could use more memory.

@kevindew I've addressed all your comments except the one about the infinite loop because, while I agree it is a problem, I think it is out of scope for this PR and I've put a card in planning for it. If you could take another look that would be great!


Improve Kitchen Sink Demo Application

As of now the following has been discussed to be implemented under this issue.

Make kitchen sink a multi-root application
Find and remove functionality that was deprecated in Angular 2.0.0 released
Think of better examples (at least better named), to be fully defined as we go.

Milestone created, Epic currently has 3 stories as issues. We can change things around as we move forward.
https://github.com/rangle/augury/milestone/14

Closing, we we're taking this with milestone, "Kitchen Sink code update with new guide"


How to use kanban template

Hi @jperon i would like to use your kanban template for Grist but i don't understand how it work... Would you have time to explain me ? Also, i would love tu use it  as a supplement of the Lightweight CRM template : https://www.getgrist.com/templates/lightweight-crm-template/
thank you very much in advance !

Hello @oblab,
This widget allows you to define a custom widget directly in your document. So, to use it:

create a custom widget with Custom URL pointing to https://jperon.github.io/grist/Grist-pug-py-widget/ (or the url where you’d self-host it);
upon creation, you’ll get a code editor with pug code, in which you’ll see a python script (instead of javascript, thanks to Brython);
in the Test document, click the ... on top right of the kanban widget, then Open configuration;
copy / paste the code, replacing the boilerplate you had in your own custom widget;
Preview, then Install, then Save.

@jperon Merci, serait-il possible de vous contacter en message privé ? j'avais bien suivi le process que vous expliquez mais je n'obtiens rien en preview... Sans-doute une erreur dans ma configuration

Bien sûr<EMAIL_ADDRESS>


Fix buffer overflow in generic_fp stacktrace

In the 'with ucontext' case, the skip_count would be reset to 0, and max_depth should not be modified. Otherwise the result array would overflow and lead to crash (happens when the stack depth is greater than max depth, or the stack is bogus)

Thanks a lot. Are able to also offer unit test coverage for the issue (would be most perfect)

Added unit test coverage. It can be reproduced with TCMALLOC_STACKTRACE_METHOD=generic_fp ./stacktrace_unittest
Also just curious: are the unit tests automatically tested in some CI pipeline? With different stacktrace methods?

Applied. Thanks a lot!
As for your question. I am manually running tests on various platforms and with various build configurations from time to time. Yes, time for us to automagically ensure that different stacktracing methods are tested. I'll consider something sooon.


Research Spike: Can we get data / battery savings from compression?

GZip reduces text by over 70% but it also reduces battery drain by similar margins. GRPC offers an experimental compression feature and although binary (protobuf) data is not nearly as compressible as text, it still might offer significant savings on data size, which in turn saves battery usage.
This might even be enough to offset the data requirements when fetching all memos. Either way, with light clients being so data heavy, this is probably worth researching.
Time Box: 2 days
Desired outcome:

[ ] determine whether it is possible to enable support for full stream compression in lightwalletd
[ ] If so, setup a network metering test to determine approximately how much data is saved streaming 10,000 blocks. The percentage of data saved will equate roughly to the amount of battery saved, as well.

There's an interesting security problem that arises when you turn on compression.
(Aside to explain the attack.)
Suppose a client is receiving some compressed data that contains a secret, and you have control over part of the input data (but you have no control over the secret and other parts of the data). If you set the part of the data you can control to your guess for what the secret is, then if you guessed right it will compress better than if you guessed it wrong (because there's duplication when you guess right). This means there's a side-channel attack where the length of the compressed data tells you if you guessed right or not, and you can leak the secret this way.
We shouldn't avoid compression because of this, but we should make sure to check that whatever we do is not susceptible to it. It's not a problem at all if all of the data is already public, e.g. mempool and block contents. It only becomes a problem when some of the data is secret or depends on the identity of the client (for anonymity).


Update the help text for the --node-osdisk-size parameter

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

Codecov Report

Merging #6646 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##           dev   #6646   +/-   ##
===================================
  Coverage    0%      0%
===================================
  Files       11      11
  Lines      145     145
  Branches    11      11
===================================
  Misses     145     145

Continue to review full report at Codecov.

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

@mboersma  you ack, i merge.

Thanks for the contribution, @theheatDK .


Reducing the size of refresh controller

Hi I want to reduce the scroll height change. Currently I have to scroll the table a long way above to get called refresh method.
Any suggestion for this ?

Property triggerVerticalOffset added in UIRefreshControl. It works only for bottom refresh controls.


[macOS] packaging error at opening: cannot load library, no plugins at all

At launch of the macOS binary, there are no plugins including those from medInria and our external project:
WARN  - Wed Oct 19 14:20:44 2022 - "Unable to load /Applications/MUSICardio 2.app/Contents/PlugIns/libmedItkArithmeticOperationProcessPlugin.dylib - Cannot load library /Applications/MUSICardio 2.app/Contents/PlugIns/libmedItkArithmeticOperationProcessPlugin.dylib: (dlopen(/Applications/MUSICardio 2.app/Contents/PlugIns/libmedItkArithmeticOperationProcessPlugin.dylib, 0x0009): Library not loaded: /System/Volumes/Data/builds/workspace/music-macos-free/build/medInria-build/lib/resource_libs/libmedWidgets.dylib\n  Referenced from: /Applications/MUSICardio 2.app/Contents/PlugIns/libmedItkArithmeticOperationProcessPlugin.dylib\n  Reason: tried: '/System/Volumes/Data/builds/workspace/music-macos-free/build/medInria-build/lib/resource_libs/libmedWidgets.dylib' (no such file), '/usr/local/lib/libmedWidgets.dylib' (no such file), '/usr/lib/libmedWidgets.dylib' (no such file))"
It could be linked to https://github.com/medInria/medInria-public/pull/1039 which have been removed from mac_packager.sh.in. I am trying to test on our jenkins macOS item, but it's not ideal.
For now, to compile (on zsh):
resourceLibsDir=@medInria_BINARY_DIR@/lib/resource_libs #resources did not exist
injectDirs="$injectDirs -inject-dir=$resourceLibsDir"

and (changing the app name)
echo "##########################"
contentsDir=<EMAIL_ADDRESS>ls $contentsDir/PlugIns

echo "########################## 2 "
dylibNames=$(ls $contentsDir/PlugIns/*.dylib)
for lib in $dylibNames; do
    echo $lib
    libname=${lib##*/}
<EMAIL_ADDRESS>    install_name_tool -id $installedName $contentsDir/PlugIns/$libname
done

# Resource libraries are sent as plugins to dtkDeploy (above) because they are
# not dependencies of the executable (dtkDeploy uses otool on the executable to
# find which libraires should be imported, so it will not find resource
# libraries). After the execution of dtkDeploy we move these libraries to the
# frameworks folder and adjust their install name.
resourceLibs=''
echo "########################## 3"
dylibResourceNames=$(ls $resourceLibsDir/*.dylib)
for lib in $dylibResourceNames; do
    echo $lib
    libname=${lib##*/}
    copiedLib=$contentsDir/Frameworks/$libname
    \mv $contentsDir/PlugIns/$libname $copiedLib
<EMAIL_ADDRESS>    install_name_tool -id $installedName $copiedLib
    resourceLibs="$resourceLibs $libname"
done

# Because of the dtkDeploy bug with install names, we have to fix the
# dependencies of the resource libraries.
for lib1 in $resourceLibs; do
    deployedLib1=$contentsDir/Frameworks/$lib1
<EMAIL_ADDRESS>    for lib2 in $resourceLibs; do
        deployedLib2=$contentsDir/Frameworks/$lib2
        install_name_tool -change $1/$lib1 $installedName $deployedLib2
    done
done

But i've a crash on the macOS computer of a colleague which tried the dmg. I'll have a macOS soon to test, but it can take some time.
This needs to be solved for 3.3 release.

@fcollot if you have an answer for that problem it could be great. I don't have a macOS machine yet, it's in preparation (i hope i'll have it this week), and i won't be here next week. And since it was your code, you could have a quicker answer maybe, for us to be able to do a release soon ?

The two lines:
resourceLibsDir=@medInria_BINARY_DIR@/lib/resource_libs #resources did not exist
injectDirs="$injectDirs -inject-dir=$resourceLibsDir"

should have been removed in the previous PR.

I tried with the removal of the above lines and the problem persists. mac_packager.sh.in is now the same as it was before the code I added so the issue is elsewhere.

This issue was introduced with https://github.com/medInria/medInria-public/pull/1029. The new code did not take into account the RESOURCE option of the set_lib_install_rules function. As a consequence all libraries are treated as resource libs, and so removing support for those libs automatically causes all libs to be ignored.

I have fixed this, and all legacy plugins are packaged and loaded, but the new plugins (listed in the erreur message at the top of this issue) are still not loaded. I do not know what the origin of that bug is, but it is not related to the resource library code.


Error validating reset password token

This error appears when i tri to open the resetPassword component
react-dom.development.js:21 Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
How to fix?
Thanks

I've just re-retested the app and it's working fine for me including the forgot password and reset password functionality. Have you made changes to the code?

I get this error for profile update, not password reset


[tests] Move more tests to helix by overriding dcp path from assembly metadata

Description
AppHost build embeds metadata with paths for DcpCliPath, DcpExtensionsPath, and DcpBinPath. This ties the apphost to the machine that it was built on.
This PR:

When DcpPublisher:CliPath is available from the configuration, set the other two paths based on that.
Makes $(RunTestsOnHelix)=true the default.

This allows running most of the tests on helix. The remaining ones depend on being able to run the test projects which doesn't work on helix because the path to the project files is embedded in the assembly metadata.
Also, download helix test result .trx files to have all the .trx files available in artifacts.
Contributes to https://github.com/dotnet/aspire/issues/2036 .
Checklist

Is this feature complete?

[ ] Yes. Ready to ship.
[ ] No. Follow-up changes expected.

Are you including unit tests for the changes and scenario tests if relevant?

[ ] Yes
[ ] No

Did you add public API?

[ ] Yes

If yes, did you have an API Review for it?

[ ] Yes
[ ] No

Did you add <remarks /> and <code /> elements on your triple slash comments?

[ ] Yes
[ ] No

[x] No

Does the change make any security assumptions or guarantees?

[ ] Yes

If yes, have you done a threat model and had a security review?

[ ] Yes
[ ] No

[x] No

Does the change require an update in our Aspire docs?

[ ] Yes

Link to aspire-docs issue:

[x] No

Microsoft Reviewers: Open in CodeFlow

@karolz-ms @danegsta This PR changes the behavior when you specify clipath config by computing the other 2 paths baed on that. Does that break any assumptions?

@karolz-ms @danegsta This PR changes the behavior when you specify clipath config by computing the other 2 paths based on that. Does that break any assumptions?

That should be just fine.


Add unary_union alias for top-level union_all

xref https://github.com/shapely/shapely/issues/1276
Since we already have unary_union, and this is also used in GeoPandas (and PostGIS also uses this), we thought it best to keep that name. But also keeping union_all because this is consistent with intersection_all etc (and we don't want to rename the _all functions to unary_, since that is also not a super clear name if you are not familiar with it)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 84.391%

Totals

Change from base Build<PHONE_NUMBER>:
0.006%

Covered Lines:
2087

Relevant Lines:
2473

💛  - Coveralls


Fixed exception when creating a device.

This commit fixes the issue reported at
https://community.smartthings.com/t/wemo-insight-switches/1704/32
I only got my hub a few hours ago so this is my first exposure to Groovy and I just blindly fixed the exception - map.headers.decodeBase64() returns null if headers is empty. If there's a better solution please let me know. After this fix I was able to add WeMo Insight switches and operate them successfully.

This has been merge with 4f34f014d784aaeb05f1003b5664db1daec98621


Errors occurred after Are your cluster is in Azure cloud or not？

Hello, I am a developer from China, tying to deploy pai v1.8.0 in a private cloud,
enviroment: Ubuntu16.04 + OpenPAI v1.8.0
As you can see, i tried to use https://openpai.readthedocs.io/zh_CN/zh_cn_pai-1.5.y/manual/cluster-admin/configuration-for-china.html , but it not works, so I replaced some links to make sure I could access the mirrors I needed.
like this:
`
user: ***
password: ***
docker_image_tag: v1.8.0
#openpai_kubespray_extra_var:
#download_container: false
#skip_downloads: true
#gcr_image_repo: " registry.cn-hangzhou.aliyuncs.com"
#kube_image_repo: " registry.cn-hangzhou.aliyuncs.com/google-containers"
#kubeadm_download_url: "https://shaiictestblob01.blob.core.chinacloudapi.cn/share-all/kubeadm"
#hyperkube_download_url: "https://shaiictestblob01.blob.core.chinacloudapi.cn/share-all/hyperkube"
gcr_image_repo: "registry.cn-hangzhou.aliyuncs.com"
kube_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers"
openpai_kubespray_extra_var:
pod_infra_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/pause-{{ image_arch }}"
dnsautoscaler_image_repo: "docker.io/mirrorgooglecontainers/cluster-proportional-autoscaler-{{ image_arch }}"
tiller_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-helm/tiller"
registry_proxy_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/kube-registry-proxy"
metrics_server_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/metrics-server-amd64"
addon_resizer_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/addon-resizer"
dashboard_image_repo: "registry.cn-hangzhou.aliyuncs.com/google_containers/kubernetes-dashboard-{{ image_arch }}"
`
Then,  I used the quick-start-kubespry.sh to deploy pai, the error occured:
... Generating kubespray configuration Are your cluster is in Azure cloud or not? (Y/N) (case sensitive)N Traceback (most recent call last):   File "/root/pai/contrib/kubespray/script/k8s_generator.py", line 72, in <module>     main()   File "/root/pai/contrib/kubespray/script/k8s_generator.py", line 67, in main     map_table   File "/root/pai/contrib/kubespray/script/utils.py", line 53, in generate_template_file     generated_template = generate_from_template_dict(template, map_table)   File "/root/pai/contrib/kubespray/script/utils.py", line 41, in generate_from_template_dict     map_table   File "/usr/local/lib/python3.5/dist-packages/jinja2/environment.py", line 1008, in render     return self.environment.handle_exception(exc_info, True)   File "/usr/local/lib/python3.5/dist-packages/jinja2/environment.py", line 780, in handle_exception     reraise(exc_type, exc_value, tb)   File "/usr/local/lib/python3.5/dist-packages/jinja2/_compat.py", line 37, in reraise     raise value.with_traceback(tb)   File "<template>", line 410, in top-level template code TypeError: 'NoneType' object is not iterable
Is there a way to fix this or make sure that I can deploy it correctly?
By the way, i also tried the method mentioned in the #5592 , it performs more processes but ultimately still faild.
Thank you.

@suiguoxin @siaimes Any comments?

@hzy46 May know this part better

You can try this:
https://github.com/siaimes/k8s-share

You can try this:
https://github.com/siaimes/k8s-share
This is the solution I used now, which is simple and stable.

yeah, I tried this and here is now what I'm experiencing now:
`TASK [kubernetes/master : Create hardcoded kubeadm token for joining nodes with 24h expiration (if defined)] ***************************************************************************************************************************
Monday 16 May 2022  11:17:44 +0800 (0:00:00.040)       0:02:57.894 ************
TASK [kubernetes/master : Create kubeadm token for joining nodes with 24h expiration (default)] ****************************************************************************************************************************************
Monday 16 May 2022  11:17:44 +0800 (0:00:00.047)       0:02:57.941 ************
FAILED - RETRYING: Create kubeadm token for joining nodes with 24h expiration (default) (5 retries left).
FAILED - RETRYING: Create kubeadm token for joining nodes with 24h expiration (default) (4 retries left).
FAILED - RETRYING: Create kubeadm token for joining nodes with 24h expiration (default) (3 retries left).
FAILED - RETRYING: Create kubeadm token for joining nodes with 24h expiration (default) (2 retries left).
FAILED - RETRYING: Create kubeadm token for joining nodes with 24h expiration (default) (1 retries left).
fatal: [pai-master -> <IP_ADDRESS>]: FAILED! => {"attempts": 5, "changed": true, "cmd": ["/usr/local/bin/kubeadm", "--kubeconfig", "/etc/kubernetes/admin.conf", "token", "create"], "delta": "0:01:15.022307", "end": "2022-05-16 11:25:40.956708", "msg": "non-zero return code", "rc": 1, "start": "2022-05-16 11:24:25.934401", "stderr": "timed out waiting for the condition", "stderr_lines": ["timed out waiting for the condition"], "stdout": "", "stdout_lines": []}
NO MORE HOSTS LEFT *********************************************************************************************************************************************************************************************************************
PLAY RECAP *****************************************************************************************************************************************************************************************************************************
localhost                  : ok=1    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0
pai-master                 : ok=509  changed=17   unreachable=0    failed=1    skipped=509  rescued=0    ignored=0
pai-worker                 : ok=355  changed=12   unreachable=0    failed=0    skipped=293  rescued=0    ignored=0   `

I have not deleted the node and I have tried the command in the worker node, but the token creation failure error is still there.

Actually，I have run this command on all nodes(dev, master and worker).

https://github.com/kubernetes/kubeadm/issues/1447#issuecomment-490494999
This thread may be useful for you.

https://github.com/microsoft/pai/issues/5786#issuecomment-1150620761
@chjm  This may be useful to you.


fix: fix initial value for stepped slider

thumbIndex was only updated within the gesture callback, but it is used to set the slider index, so its initial value was not being set.
closes #46
closes #47

@computerjazz, thanks for your PR! LGTM, but there is a nit and I fixed it in another branch!


Remove the tempfile closing during fetch

Signed-off-by: thechosenone124<EMAIL_ADDRESS>
Description
Fetch refers to chef::http.streaming_request which on line 182. This function sets the tempfile to
stream_to_tempfile(url, http_response, tempfile, &progress_block)
On line 546 stream_to_tempfile closes the file. This means that the fetch function attempts to close the file a second time, causing an IOError
Related Issue

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.

I messed up the DCO thing and didn't start my description with
Signed-off-by: thechosenone124<EMAIL_ADDRESS>I tried editing but it didn't work

Oops nevermind


add release notes for 0.29.0

Pull Request Test Coverage Report for Build 1455

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

Totals

Change from base Build 1450:
0.0%

Covered Lines:
2152

Relevant Lines:
2442

💛  - Coveralls


feat(ffe-decorators-react): Add alwaysEaseFrom option to `easePrope…

…rties`
Adds a configuration option, alwaysEaseFrom, that if set will cause all
updates on the wrapped component to start easing from that value instead
of the previous value.
Closes #605

Coverage decreased (-0.03%) to 81.985% when pulling 6cefd7edd576fbcf4da04a0b7e3a11aa9d09e71a on ivarni:605-always-ease-from into b1f82d89dda03920d40ab36e22bd404c66b43d79 on SpareBank1:develop.

I'll just copy this thing over to our codebase and modify it there instead


ISO 639-1 & ISO 3166-1 alpha-2

Hello,
In your example on your README.md, you use countries.iso field as reference for the ISO 3166-1 alpha-2. It's not very explicit since what is named locale in country_translations.locale is also an reference to a code ISO (ISO 639 1).
For the sake of clarity, I think it would be useful if your countries.iso field was called something more explicit (like countries.country_iso or countries.country_code).
Thx.
Martin

@tintamarre I think the country table is used only for the sake of explanation, so that it's not really an issue.

@tintamarre as @aglipanci said, iso is just an example of how to use the package. Feel free to use whatever you want :)

If you think that countries.code would be ok, I would be ok if you send a PR to change this.

I know it's just an example, but it confuses me at first ... I thought it would confuse other people. I will send a PR with countries.code.


Sema: Filter out protocol extension default implementations of operators

In solution ranking we always prefer a protocol operator over
a protocol extension operator. So if their interface types are
identical, any set of fixed type assignments that satisfies
the default implementation will also satisfy the protocol requirement.
Thus, we can filter out the default implementation early and not
consider it at all.
This speeds up expressions involving bitwise shift operators,
for example.

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci Please smoke test

@swift-ci Please test source compatibility

@swift-ci please test Linux platform


This fixes #1245, premature routing to marathon

After this fix, traefik will not route traffic to marathon jobs that
have healthchecks that have not run yet.

@gnur Apologies we likely can't accept this PR for reasons outlined in #1185.
Please see the issue on possible workarounds. If you feel like a switch that conditionally enables the behavior your PR intended to provide is reasonable (at the price of losing your cluster state during leader elections), please comment on the referenced issue.
Thanks1


Unable to build a new docker image after certificate update.

Describe the bug
Followed the steps to update mtls cert and got error when a new container is built using the following command.
docker build -t mock-register-updated .
I am using macOS, is this solution meant to be only run on Windows system?
Screenshots

Hi @BenNyanKyaw,
Thanks for reaching out, can you give it a try with the --no-cache flag please?
e.g. docker build --no-cache -t mock-register-updated .
I am able to build the container on an M1 Pro MacBook Pro running Docker version 20.10.14, build a224086
Let us know how you go.

Hi @CDR-DavidR,
Thanks for your quick response, I tried again with --no-cache but no lucks.
I am on  macOS Catalina, Docker 20.10.11

I have also been able to successfully build the Mock Register container image on my Macbook Pro:

MacOS Monterey v12.2.1
Docker v20.10.5

From the log output included above, it looks like there is an issue when accessing https://api.nuget.org/v3/index.json?

@CDR-DF , looks like something to do with work computer with VPN/proxy. I can build with no issue on my personal mac.
From work mac:
I can hit https://api.nuget.org/v3/index.json from both browser and curl inside container.
Do you aware of any setting for ppl using VPN/proxy?

That's good news that it is working outside of your work environment at least.
You could try the proxy settings within Docker, as outlined here - https://docs.docker.com/network/proxy/
Hopefully that gets it working for you.

Thanks everyone. For other people who faces similar issue, I resolved it by replacing the Nuget config in the container with the following config with additional proxy setting.


Generating Type Definitions from Javascript is blocked by requiring private name

TypeScript Version:  3.9.0-dev.20200407
Search Terms:

TS9006
Declaration emit for this file requires using private name
Explicit type annotation
Unblock declaration emit.

Code
// thing.js // maybe something from deep in my library
'use strict';
class Thing {}
module.exports = { Thing };

// index.js
"use strict";
const Thing = require("./thing").Thing;
module.exports = { Thing }; // re-export to the world

tsconfig.json:
{
  "compilerOptions": {
    "allowJs": true,
    "checkJs": true,
    "declaration": true,
    "emitDeclarationOnly": true,
    "declarationDir": "types",
    "strict": false,
    "target": "ES2018",
    "module": "commonJS",
    "moduleResolution": "node",
    "lib": ["ES2018"]
  },
  "include": ["index.js", "thing.js"]
}

Expected behavior:
I believe I should get two declaration files out of this that would look something like:
// thing.d.ts
export class Thing {}

// index.d.ts
import { Thing } from './thing';
export { Thing };

Actual behavior:
index.d.ts fails to be emitted with the error:
TS9006: Declaration emit for this file requires using private name 'Thing' from module '"/Users/neal/Desktop/privateNameTSC/thing"'. An explicit type annotation may unblock declaration emit.

It's not clear to me how to annotate the module.exports to make the "name" not private anymore
Thanks for taking a look.
Playground Link: Can't because imports related but I made a minimum repro here: https://github.com/nbbeeken/private-name-error-tsc
Related Issues: #9865

This is broken in 3.8 and 3.9 at least.

@sandersn thank you kindly for the quick triage. This is a bit of a roadblock for our migration to TypeScript, would it be helpful if we tried to fix this locally? Or is there already someone on your end that will begin work shortly?

From talking to @weswigham about a similar issue (probably the same issue), it's an unfortunate limitation in the way that we bind module.exports = { Thing }; although it looks like it could be translated to export { Thing }, we actually have to treat it as
declare const _tmp: { Thing: Thing }
export = _tmp

It's probably possible to special-case this exact pattern and emit export { Thing }.
@weswigham if you can weigh in, you know more about this than I do.
@mbroadst I put this in 4.0 assuming that the real fix would be complex.

@sandersn you have it exactly.

Is there a workaround for this to prevent the CLI from erroring?
I tried "checkJs": false, but to no avail

@nbbeeken Try to "allowJs": false, I think it helps you.

@nbbeeken Try to "allowJs": false, I think it helps you.

I appreciate the help! unfortunately that doesn't seem to work. The goal is to generate types from jsDoc comments so tsc needs to allow .js files as input. Here's the errors you get if allowJs is false: (setting checkJs to false just removes the TS5052 error)
error TS5052: Option 'checkJs' cannot be specified without specifying option 'allowJs'.

error TS18003: No inputs were found in config file './types/tsconfig.json'. Specified 'include' paths were '["index.js","thing.js"]' and 'exclude' paths were '["types"]'.

I am having the same error message without using explicit exports (tested with TypeScript 3.9.7).
We have different implementations of classes with same name in different folders (for different customers). Although this results in a naming conflict, we would be able to @ts-ignore the duplicate declarations.
Sadly, some files produce an error that cannot be ignored: Error:(1, 1) TS9005: Declaration emit for this file requires using private name 'Bla'. An explicit type annotation may unblock declaration emit.
Minimal example:
// test1/Bla.js
class Bla extends BlaBase
{

}

// test2/Bla.js
class Bla extends BlaBase
{

}

// test3/BlaBase.js
class BlaBase
{
    constructor(name)
    {
        this.name = name;
    }
}

The error message is somewhat brittle. In this toy example it goes away when adding constructors to the two Bla implementations.
However, in our real code I am unsure what is causing the issue (e.g. a specific method or field).
Could you explain what is causing the message here? Any ideas to work around the issue?

@nbbeeken, I had a case somewhat similar to yours, where our app was exporting a function that set a property (which I think TypeScript recognizes as a constructor):
module.exports = function(key) {
    const myImpl = implementations[key];
    this.invoke = myImpl.invoke;
};

and it was throwing this error:
error TS9005: Declaration emit for this file requires using private name 'exports'. An explicit type annotation may unblock declaration emit.
By changing module.exports to exports, the compiler error went away.

Thanks for the suggestion @jrnail23!
I gave that a go but now there are type errors about exports not existing:
index.js:3:23 - error TS2306: File '.../test-ts-bug/thing.js' is not a module.
3 const Thing = require("./thing").Thing;
                        ~~~~~~~~~
thing.js:4:1 - error TS2304: Cannot find name 'exports'.
4 exports = { Thing };
  ~~~~~~~
Found 2 errors.

Here's a quick screenshot to show I'm using the example in the issue description.

Screenshot:

Came to this issue because I was getting the same error, even when I had declaration: false. I just tested the repro (https://github.com/nbbeeken/private-name-error-tsc) with typescript@beta (4.1.0-beta) and it no longer produces this error.

Yep, this is fixed in 4.1 -- although I found a related bug when requireing a relative path like "./thing" instead of "fs".

Are you sure this is fixed in 4.1?
npm install typescript@beta
I have the same problem both on 4.0.3 and 4.1, not sure is the exact same problem, minimal example included here:
https://stackoverflow.com/questions/64460213/create-typescript-declaration-files-for-existing-jsdoc-annotated-commonjs-librar
... maybe I did something wrong? Should I open a new ticket with the code I posted in stackoverflow?

re-exporting classes now leads to tsc crash "Unhandled alias declaration kind in symbol serializer!"
I've filed a bug report:
https://github.com/microsoft/TypeScript/issues/41182

@sandersn @weswigham – Can this issue be reopened?
I get the following when trying to generate definitions for stylelint (using TS 4.1.0-dev.20201025):
lib/assignDisabledRanges.js:1:1 - error TS9006: Declaration emit for this file requires using private name 'CommentExt' from module '"postcss/lib/comment"'. An explicit type annotation may unblock declaration emit.

1 'use strict';
  ~~~~~~~~~~~~

lib/descriptionlessDisables.js:1:1 - error TS9006: Declaration emit for this file requires using private name 'CommentExt' from module '"postcss/lib/comment"'. An explicit type annotation may unblock declaration emit.

1 'use strict';
  ~~~~~~~~~~~~

lib/needlessDisables.js:1:1 - error TS9006: Declaration emit for this file requires using private name 'CommentExt' from module '"postcss/lib/comment"'. An explicit type annotation may unblock declaration emit.

1 'use strict';
  ~~~~~~~~~~~~

lib/utils/parseCalcExpression/parser.js:383:13 - error TS9005: Declaration emit for this file requires using private name 'Parser'. An explicit type annotation may unblock declaration emit.

383             var parser = (function () {
                ~~~

@glen-84 can you please share a minimal repro?

@Bnaya,
You can just clone the stylelint repo, update TS, and add the following to the tsconfig.json file:
        "declaration": true,
	"emitDeclarationOnly": true,
	"outDir": "types-new"

(and optionally remove "noEmit": true, which is not needed)
Then run npx tsc.

@glen-84 While the error is the same, it's not the same issue,
see my workarounds there:
https://github.com/stylelint/stylelint/pull/5004/files
(types are now emitted)
What we are missing there to make it nicer is a way to export type from ts-jsdocs

So this is triggered by the use of @typedef to define a type, instead of importing the type each time? Should it work?

I believe something like that

Do you know if there is an existing GitHub issue for this?

I think not

Where do you see that?

Example: import('stylelint').DisabledRange

I think not

Okay, I'll probably open one.

Example: import('stylelint').DisabledRange

This resolves to the local types in the types directory, not an @types package. These types would likely be removed once they can be generated automatically via TypeScript.

This resolves to the local types in the types directory, not an @types package. These types would likely be removed once they can be generated automatically via TypeScript.

I'de say to relocate them, and import them as regular source files, and not like so (It will break if you publish)
But let's stop hijacking this issue, if there's somewhere else you are working on this, i'de love to help

Here is a minimal example, less than 20 lines in total, it gives the error of this bug both on typescript 4.0 that on 4.1 beta:
https://github.com/ggreco/doc2dec

checkout the repo
npm install
npm run build

@ggreco Will you create a new issue?

Here is a minimal example, less than 20 lines in total, it gives the error of this bug both on typescript 4.0 that on 4.1 beta:
https://github.com/ggreco/doc2dec

checkout the repo
npm install
npm run build

Ugly workaround:
use import('./rectangle').Rectangle

@ggreco Will you create a new issue?

I created a new bug for this, https://github.com/microsoft/TypeScript/issues/41250
@Bnaya thanks for the workaround, it works, but it totally destroy the jsdoc markup for javascript users of the library...

Additionally, this bug still persist, see this repro:
https://gist.github.com/Bnaya/f88130a9321b2706e1745f8695ff9664
When trying to avoid the above crash, i've set the imported class to an intermediate variable, and exported it.
that leads again to the "using private name" error

This is fixed in latest master (likely by a combination of the other fixes going in) and now emits
//// [lib.d.ts]
/**
 * @param {string} a
 */
export function bar(a: string): string;
export class SomeClass {
    a(): number;
}
//// [main.d.ts]
export const IntermediateClass: typeof SomeClass;
import { SomeClass } from "./lib";

If anyone comes back to this thread using latest TS and thinks they have "the same bug" - please open a new thread with your repro - tracking stuff in closed issues is hard - thanks~

I  used require(./xxx.js) to skip this error; but i don't konw why it works.

@nbbeeken, I had a case somewhat similar to yours, where our app was exporting a function that set a property (which I think TypeScript recognizes as a constructor):
module.exports = function(key) {
    const myImpl = implementations[key];
    this.invoke = myImpl.invoke;
};

and it was throwing this error: error TS9005: Declaration emit for this file requires using private name 'exports'. An explicit type annotation may unblock declaration emit.
By changing module.exports to exports, the compiler error went away. I'm not sure if this actually worked, but it did get rid of the error. 🤷♂

I am seeing a similar error message in TypeScript 4.3.2 with the following pattern:
/* data_listener.js */
export function createDataListener() {
    return async function dataListener(someObj, x, y) {
        // `this` references the model instance
       this.blah = something;
    };
}

/* create.js */
import {createDataListener} from "../data_listener";
someObj.setDataListener(createDataListener().bind(model, someObj));

I tried removing the this reference as  a hint from the quoted comment (maybe TypeScript thinks the returned function is being used as a constructor function when it is not) and I'm able to compile that code:
/* data_listener.js */
export function createDataListener() {
    return async function dataListener(model, someObj, x, y) {
       model.blah = something;
    };
}

/* create.js */
import {createDataListener} from "../data_listener";
someObj.setDataListener(createDataListener().bind(undefined, model, someObj));


Unable to install stolon via Helm in Kubernetes 1.22

Hello,
I do get an error when applying:
# download example values
curl -LO https://github.com/kvaps/kube-linstor/raw/v1.14.0/examples/linstor-db.yaml

# install release
helm install linstor-db kvaps/stolon \
  --namespace linstor \
  -f linstor-db.yaml

The error given is:
Error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Role" in version "rbac.authorization.k8s.io/v1beta1", unable to recognize "": no matches for kind "RoleBinding" in version "rbac.authorization.k8s.io/v1beta1"]

This has probably to do with the new API versions of Kubernetes. Could you please take a look at it?

This is still in a row


Accept a function as MethodDescriptor.path

Addresses https://github.com/tulios/mappersmith/issues/159

This change is out on version 2.33.0


belindas-closet-nextjs_4_256_buttons-functionality

Resolves #256
As a developer, I added functionality to the delete and archive buttons along with confirmation dialogues. When products are deleted or archived from the frontend, they are hidden. They are marked as isHidden (deleted) or isSold (archived) in the database.
Video demo
I wanted to make the page reroute back to the category page, but the components complicates it and my attempts to incorporate router.back() caused errors.
Related to User Story #255

I was able to delete a product and archive a product. Both were hidden from the products page and were updated in the database, with isSold changing to true for the archived product, and isHidden changing to true for the deleted product.

I would suggest making a message appear to show if the deletion/archival of the product was successful or failed, so that the user will know the result of clicking the buttons and get confirmation.

I was able to make the page route back to the previous page, but not sure on how to create a pop up success/error message. I'll look into it

I was able to delete a product and archive a product. Both were hidden from the products page and were updated in the database, with isSold changing to true for the archived product, and isHidden changing to true for the deleted product.

I would suggest making a message appear to show if the deletion/archival of the product was successful or failed, so that the user will know the result of clicking the buttons and get confirmation.

I was able to create a message to show up after the product deletion is successful, along with the page routing back to the category page.


React: Withdraw asset

Preview is available here:http://stellar-demo-wallet-pr86.previews.kube001.services.stellar-ops.com/

Preview is available here:http://stellar-demo-wallet-pr86.previews.kube001.services.stellar-ops.com/


statically allocated buffers for multiple instances of littlefs

Hey,
If I want to use multiple littlefs instances on the same physical flash chip do I need to allocate read, prog and lookahead buffers for each of the instances or can I use the same buffers ?
Thanks !

It depends if you have both filesystems mounted at the same time. If you unmount one filesystem before using the other you can share buffers, otherwise you will need to allocate separate buffers for both filesystems.


Arcs CDN built from master

Merge Scott's CDN changes into master (gulp file, ...)
Create PolymerLabs/arcs-cdn repo and push an initial Arcs library.
Document CDN push process

Create PolymerLabs/arcs-cdn repo and push an initial Arcs library.

This is done. E.g. https://polymerlabs.github.io/arcs-cdn/v0.02/ArcsLib.js

Merge Scott's CDN changes into master (gulp file, ...)

This is done. Note that some of the changes I aimed at master didn't have to go that low. I've put the cdn source and the build scripts directly into the cdn repo.

Document CDN push process

I updated the new CDN-centric build process in the CDN readme.

@noelutz I think this issue is largely satisfied. Let me know if I should do anything else.

LGTM. Thanks!


tradução O que todo(a) Desenvolvedor(a) de Software precisa saber

opa demorou parceiro, vou revisar ele amanhã de manhã e vou pegando os
próximos!
Atenciosamente, Marco Aurélio.  Perfil http://marcoaure.net *
Analista-Desenvolvedor de sistemas e especialista: Php, Mysql, *
Html5*, CSS3, JQuery, *Front e Back-End.
2016-10-17 21:24 GMT-02:00 William Oliveira<EMAIL_ADDRESS>
@woliveiras commented on this pull request.
Show de bola @marcoaure https://github.com/marcoaure! Deixei alguns
pontos no Review.
Valeu demais pela disposição!
In translations/en/README.md
https://github.com/woliveiras/front-end-career/pull/50#pullrequestreview-4577650
:

@@ -4,6 +4,37 @@ A career guide to Front End Developers

What every Software Developer needs to know
+You need to know: nothing on this life is easy, but if do you keep your humility and open mind, the path is far less thorny.
+
+You will not become the most incredible developer of the universe just reading this guide, but can go far if you follow the advice of good and experienced people (which may or may not have contributed here).
+
+No one is better than you. People just have more experience, more so because the "be good" depends on the point of view.
+
+You can't build the most amazing code, performative and scalable from day to night, but you can do it if you don't give up.
Aqui podia ser You can't build the most amazing code, performatic and
scalable
In translations/en/README.md
https://github.com/woliveiras/front-end-career/pull/50#pullrequestreview-4577650
:

+You will not become the most incredible developer of the universe just reading this guide, but can go far if you follow the advice of good and experienced people (which may or may not have contributed here).
+
+No one is better than you. People just have more experience, more so because the "be good" depends on the point of view.
+
+You can't build the most amazing code, performative and scalable from day to night, but you can do it if you don't give up.
+
+Your life/health worth more than your profession. Try to take care, rest, relax. Try to live outside your job.
+
+We found somethings that the beginners need to know this link.
+
+And we found somethings that unmotivated people must know  this another link
+
+Don't stay in your confort zone!
+
+although is good that you know, from beginning:
Só faltou o A maiúsculo no começo da frase.
In translations/en/README.md
https://github.com/woliveiras/front-end-career/pull/50#pullrequestreview-4577650
:

+No one is better than you. People just have more experience, more so because the "be good" depends on the point of view.

+You can't build the most amazing code, performative and scalable from day to night, but you can do it if you don't give up.
+
+Your life/health worth more than your profession. Try to take care, rest, relax. Try to live outside your job.
+
+We found somethings that the beginners need to know this link.
+
+And we found somethings that unmotivated people must know  this another link
+
+Don't stay in your confort zone!
+
+although is good that you know, from beginning:
+
+* Clean Code
+* English
Uma dúvida me pintou! Acha interessante remover o inglês da lista sendo
essa parte inteira em inglês?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/woliveiras/front-end-career/pull/50#pullrequestreview-4577650,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGooTsl9Z6m5t-yS5oeAyxh_DFaCEJqNks5q1APLgaJpZM4KZLFl
.

Alterações feitas com sucesso @woliveiras !

Shoooow de bola @marcoaure


updated spell and comment

@JoelSpeed @damdo , PTAL if its ok to get it merged ( very small , harmless ).

No need for e2es as it is only a comment change.
/override ci/prow/e2e-aws-capi-techpreview ci/prow/e2e-aws-ovn ci/prow/e2e-aws-ovn-serial ci/prow/e2e-aws-ovn-techpreview ci/prow/e2e-azure-capi-techpreview ci/prow/e2e-azure-ovn-techpreview ci/prow/e2e-gcp-ovn-techpreview ci/prow/e2e-openstack-capi-techpreview

/retitle NO-JIRA: updated spell and comment


Allowed return_fields to be passed into serialize method

This allows the user to specify how they want the nested objects to be serialized.
This can fix #221, but that will inevitably be fixed once the API no longer returns IDs for choices.
This option does offer the user more control.

Hey @FragmentedPacket thanks for the PR. Does this work without being able to pass return_fields into save()? I'm thinking we can handle this without requiring a change in client code though. Can you see if the changes in PR #223 fix your issue?

@zachmoody Thanks for the fast response. PR #223 does fix my issue it appears and I'm find with going that route as to prevent any change in client code!

Nice! Thanks for testing. Will get a new release out.


Switch softmax learner in compare-classifier-code demo

Use the multinom learner for softmax regression instead of the glmnet hack.
Closes #488

thx!


Compatibility roughs.js  - gsap for animation

Hello,
I'm working on a project for science communication about Antarctica. I found rough.js really perfect for the different drawings (https://observablehq.com/@jbaba/antarctica-elevation). These drawings will be part of a scrollytelling where animations are importants to support the story. I plan to use gsap for that purpose.  Unfortunately , I discovered that rough.js and gsap are not compatible. Is there an other way to deal with animation and rough.js ? Could compatibility be on the whish list?

Sounds interesting!
I checked the gsap forum link you mentioned above, and the idea of having squiggly animation is cool. By the way, have you tried https://github.com/rough-stuff/rough/wiki#preservevertices?
(I'm not sure if you are looking for this kind of animation or not. Just suggesting)


Please allow changing label/prefix/serviceContext in child loggers

Winston allows setting up a main logger and then creating child loggers for logging in specific modules, contexts, etc.:
const myLogger = logger.child({service: 'myService') // sets Winston 'service' metadata item on all logs

As far as I can see, there's no way to change LoggingWinston transport options such as label, prefix, or serviceContext when creating a child logger. It would be very useful to be able to do that.
I realize that these are transport options, so it would probably have to be a LoggingWinston factory method that the user would call rather than logger.child(); perhaps const myLogger = LoggingWinston.createChild(logger, {serviceContext: {service: 'myService'}}) or something. That would find the LoggingWinston transport(s) used by that logger and clone them for the child.

any news on this or workarounds?


sudo -v causes problems in EC2 ubuntu

$ sudo -v
[sudo] password for ubuntu:

but no password will make it happy.

Thanks for pointing this out -- sudo -v just increases the timeout, and isn't necessary.  I removed it (https://github.com/seanbell/opensurfaces/commit/c316e1ba3448154a47d2a9a20acb43632dcbbede)


RP Rules Link

There currently is no way to get to the RP rules without knowing the URL beforehand.
Having the two rules split in the Useful Links section as well as a hyperlink between each rule-set would be helpful.

Going to assign you as a reminder since it's been a hot minute

Completed


fix(carousel): calculation lastFullPageOffset

It is not possible to reach the last slide by using swipe when navigation is enabled
Description
Before 0.16.0, it was not possible to reach the last slide by using navigation "next" button. Swiping everything worked fine. After update to 0.16.0, this behavor is inverted, i.e., I can reach the last slider by pressing "next" button but not by swiping.
This Pull Request fixes a calculation issue that was creating this unexpected behavior.
Motivation and Context
Fixes issue https://github.com/SSENSE/vue-carousel/issues/345
How Has This Been Tested?
There is already a Vue Play case for this in the project, and was also tested manually in all VuePlay cases
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have included a vue-play example (if this is a new feature)

Looks good @dfvc, will merge now and release with v0.17.0 🚀 - should be out sometime next week


user fetching

uhhhhh

doesn't the intent do that already?

doesn't the intent do that already?

no, it just gives access to the users and some #member feautures

forgot to say it fires the guildMemberAdd, guildMemberRemove, guildMemberUpdate, threadMembersUpdate


HelloWorldController is non-functional without required attributes.

It seems to me the HelloWorldController on this page https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-mvc-app/adding-controller?view=aspnetcore-2.1 is non-functional. Having just built the example in VS2017 using ASP Dotnet Core 2.1 the claim that any public method on a controller class is callable as an HTTP endpoint does not appear to be the case, either with the comment form demonstrated or not.
I found the only way to make the controller endpoints callable was by putting a Controller attribute on the controller and a HttpGet attribute on the method.

Using the instructions provided on the linked page (and translating them for the CLI, as I'm currently running Ubuntu), I was unable to recreate your issue.
The full CLI steps I took were:
ja:~/Code/testingSomething$ dotnet new mvc --name helloworldcontroller
The template "ASP.NET Core Web App (Model-View-Controller)" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore-template-3pn-210 for details.

Processing post-creation actions...
Running 'dotnet restore' on helloworldcontroller/helloworldcontroller.csproj...
  Restoring packages for ~/Code/testingSomething/helloworldcontroller/helloworldcontroller.csproj...
  Generating MSBuild file ~/Code/testingSomething/helloworldcontroller/obj/helloworldcontroller.csproj.nuget.g.props.
  Generating MSBuild file ~/Code/testingSomething/helloworldcontroller/obj/helloworldcontroller.csproj.nuget.g.targets.
  Restore completed in 535.58 ms for ~/Code/testingSomething/helloworldcontroller/helloworldcontroller.csproj.

Restore succeeded.

ja:~/Code/testingSomething$ cd helloworldcontroller/
ja:~/Code/testingSomething/helloworldcontroller$ code .

I then added the following code to the top of the HomeController.cs file:
namespace helloworldcontroller.Controllers
{
    public class HelloWorldController : Controller
    {
        //
        // GET: /HelloWorld/

        public string Index()
        {
            return "This is my default action...";
        }

        //
        // GET: /HelloWorld/Welcome/

        public string Welcome()
        {
            return "This is the Welcome action method...";
        }
    }

    public class HomeController : Controller
    // HomeController class here

Then ran the following command to run the app:
ja:~/Code/testingSomething/helloworldcontroller$ dotnet run

Then browsed to https://localhost:5001/helloworld and received

This is my default action...

And when I browsed to https://localhost:5001/helloworld/welcome, I received

This is the Welcome action method...

in the browser.

Retested. Problem was between keyboard and chair.
I'd started with the Razor tutorial so had
         app.UseMvc();

in Startup.Configure instead of
         app.UseMvc(routes =>
         {
            routes.MapRoute(
               name: "default",
               template: "{controller=Home}/{action=Index}/{id?}");
         });


Inxi - every system info through one command

Checklist for submitting a pull request to Terminals Are Sexy:

[x] I have carefully read and comply with the Contributing Guidelines of this repo.

[x] I have searched the PRs of this repo and believe that this is not a duplicate.

Title: inxi

Link: https://github.com/smxi/inxi

Category: Tools & Plugins

Description: one command to get every system info: hardware, CPU, drivers, Xorg, Desktop, Kernel, GCC version(s), Processes, RAM usage - you name it. Perfect for bug reports, works also with IRC.

Above is a demo of inxi's capabilities.

inxi without params - shows CPU make and speed/max, kernel version, uptime, processes, RAM, HDD size and usage, client and inxi version.
'inxi -s' - shows sensors (temperature, fan speeds)
'inxi -S' - shows system data: host, kernel version, 64 or 32 bits, desktop and distro details. Adding -x or -xx or -xxx provides more details, as shown in last couple of commands.
inxi -B - shows battery details
inxi -S -XXX - shows error message, with error number.
inxi -b - bulk data, or bug report. Most times when I report a but, I choose this option. If you want consistent bug reports with full data, get your reporters to use inxi or provide a simple wrapper. This is a summary option, showing so-called basic data.

Options in inxi can be stacked together (if they don't conflict). Take a look at inxi -F for full output. :-)


Player Data Sync

ALL player nbt data should be synced. This can be done by calling:

//Read data
NbtCompound nbtCompound =player.writeNbt(new NbtCompound());

//Read data
NbtCompound nbt = // Nbt from velocity
player.readNbt(nbt);

On the proxy side, we will have to filter out some data that shouldn't be synced by default (maybe spawn location and such) but this will be configurable and the fabric mod wont have anything to do with it.

We also need a way to handle nbt data on the proxy. This library looks promising, but maybe we should just use gson?

This is implemented on the fabric side


Submitting week4 Assignment

Kindly check my assignment and approve pull request

What you submitted in the week4 folder is not the assignment but your mini-project, please move the project out of the repo, when I create a submission guideline for the mini-project you can then submit, as for the week four assignment, it is for you to simply create a web page with a header, four sections and each section should have a CSS position rule of  any one of this absolute, static, sticky, and relative


Is there are way to check the size of snapshot?

Is there are way to check the size of snapshot?
Hello, I understand it really depend on the changed amounts of the VM Daily.
However, is there is way to see the exact amount of every snapshot by Code or GUI base?
I would like to see how much size are used for the snapshot in the [AzureBackupRG_geography_number] Resource group that will be made for the Snapshot.
Or customer must assume from the VM usage to determine the size of the created snapshot?
Thanks,

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

ID: eeafbf18-2bee-17c8-9871-118396f904b7
Version Independent ID: 1c591c58-062c-695f-212f-523b4221935c
Content: Azure Instant Restore Capability
Content Source: articles/backup/backup-instant-restore-capability.md
Service: backup
GitHub Login: @Sogup
Microsoft Alias: sogup

To clarify, while the Dashboard feature of the vault shows the amount of storage used in the vault, it seems there is no feature to determine the size of the storage used by snapshots. The document implies that snapshots are stored "locally", i.e. somewhere other than the vault, and the page below specifically mentions snapshots being saved in the AzureBackupRG_ resource group.
https://docs.microsoft.com/en-us/azure/backup/backup-azure-vms-first-look-arm
Is there any way to find the storage used by these local snapshots (other than getting a bill for it)?

@KeiroKamioka0000 Thanks for the Comment. We are actively investigating and will get back to you soon.

@SadiqhAhmed-MSFT
Is their are ETA for answer? Sorry for pinging you.

@KeiroKamioka0000 Today there is no way to check the snapshot size through UI/PS. We are working on it to see how we can expose it to the customers. No timelines to commit for it as of now.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Proposal: rename the nodejs/iojs-ar WG to nodejs/nodejs-ar

Dear members of the io.js Arabic WG iojs-ar
It is proposed to rename this repo to:
nodejs/nodejs-ar
As part of the io.js and node.js convergence, node.js releases are now based on the codebase and user base of the converged node.js and io.js communities. A number of the resources and repositories have already been renamed.
In the absence of objections or other discussion, this rename will occur on or after Oct 28, 2015
However, active language working groups should take ownership of this issue and discuss/dispose of it according to their own processes.
For more information or to discuss the overall issue, please see and comment on https://github.com/nodejs/node/issues/2525
This statement was authorized by the Node.js TSC
Cc: @nodejs/iojs-ar

Done.


"ValueError: Cannot create a tensor proto whose content is larger than 2GB." after upgrade from 2.0.0rc1 to 2.0.0 release

Hi,
I've been running standard GPR on a fairly large dataset using the 2.0.0rc1 version of GPflow. Since the upgrade to 2.0.0, I'm running into the error
ValueError: Cannot create a tensor proto whose content is larger than 2GB.

on a dataset which worked fine before.
Here is the full error message:
Traceback (most recent call last):
  File "main.py", line 177, in <module>
    main(args)
  File "main.py", line 64, in main
    build_allele(args)
  File "/path/to/1_model_sim/drivers.py", line 226, in build_allele
    opt_model_list(m)
  File "/path/to/1_model_sim/model.py", line 355, in opt_model_list
    m.trainable_variables)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/optimizers/scipy.py", line 73, in minimize
    func, initial_params, jac=True, method=method, **scipy_kwargs
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/scipy/optimize/_minimize.py", line 610, in minimize
    callback=callback, **options)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/scipy/optimize/lbfgsb.py", line 345, in _minimize_lbfgsb
    f, g = func_and_grad(x)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/scipy/optimize/lbfgsb.py", line 295, in func_and_grad
    f = fun(x, *args)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/scipy/optimize/optimize.py", line 327, in function_wrapper
    return function(*(wrapper_args + args))
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/scipy/optimize/optimize.py", line 65, in __call__
    fg = self.fun(x, *args)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/optimizers/scipy.py", line 95, in _eval
    loss, grad = _tf_eval(tf.convert_to_tensor(x))
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 568, in __call__
    result = self._call(*args, **kwds)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 615, in _call
    self._initialize(args, kwds, add_initializers_to=initializers)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 497, in _initialize
    *args, **kwds))
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 2389, in _get_concrete_function_internal_garbage_collected
    graph_function, _, _ = self._maybe_define_function(args, kwargs)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 2703, in _maybe_define_function
    graph_function = self._create_graph_function(args, kwargs)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/function.py", line 2593, in _create_graph_function
    capture_by_value=self._capture_by_value),
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/func_graph.py", line 978, in func_graph_from_py_func
    func_outputs = python_func(*func_args, **func_kwargs)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/eager/def_function.py", line 439, in wrapped_fn
    return weak_wrapped_fn().__wrapped__(*args, **kwds)
  File "/path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/func_graph.py", line 968, in wrapper
    raise e.ag_error_metadata.to_exception(e)
ValueError: in converted code:

    /path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/optimizers/scipy.py:88 _tf_eval  *
        loss, grads = _compute_loss_and_gradients(closure, variables)
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/optimizers/scipy.py:145 _compute_loss_and_gradients  *
        loss = loss_closure()
    /path/to/1_model_sim/model.py:354 None  *
        opt.minimize(lambda: - m.log_marginal_likelihood(),
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/models/gpr.py:75 log_marginal_likelihood  *
        log_prob = multivariate_normal(Y, m, L)
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/gpflow/logdensities.py:95 multivariate_normal  *
        d = x - mu
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/ops/math_ops.py:927 r_binary_op_wrapper
        x = ops.convert_to_tensor(x, dtype=y.dtype.base_dtype, name="x")
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/ops.py:1314 convert_to_tensor
        ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_conversion_registry.py:52 _default_conversion_function
        return constant_op.constant(value, dtype, name=name)
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py:258 constant
        allow_broadcast=True)
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/constant_op.py:296 _constant_impl
        allow_broadcast=allow_broadcast))
    /path/to/1_model_sim/venv/lib/python3.6/site-packages/tensorflow_core/python/framework/tensor_util.py:522 make_tensor_proto
        "Cannot create a tensor proto whose content is larger than 2GB.")

    ValueError: Cannot create a tensor proto whose content is larger than 2GB.

Here are some relevant excerpts from my code:
m = gpf.models.GPR(data=(X, Y),
                    kernel=gpf.kernels.Exponential(active_dims = [0,1]),
                    mean_function=None)

opt = gpf.optimizers.Scipy()
opt.minimize(lambda: - m.log_marginal_likelihood(),
                m.trainable_variables)

I would greatly appreciate any help with this. Thanks!

Some more info that may or may not be relevant: I've tried this a bunch of times with the same dataset and others of similar size, on different machines, with either version of GPflow (using the same versions of dependencies) and the error occurs reliably in 2.0.0 and 2.0.1, but not in 2.0.0rc1. Unfortunately I'm not very familiar yet with the GPflow codebase (or tensorflow), so I have a hard time figuring out what may induce this behavior. Versions of other relevant packages are:
protobuf               3.11.3
tensorflow             2.1.0
tensorflow-estimator   2.1.0
tensorflow-probability 0.9.0

Hi @clwgg, thanks for reporting this! Can you make a minimal example that reproduces this bug (e.g. using X, Y = np.random.randn(num_data, input_dim), np.random.randn(num_data, output_dim) to make a sufficiently large data set? Off the top of my head I can't think of anything that changed from rc1 to the 2.0.0 release that would have changed this - so any further help you can give us in narrowing it down would be good :)

Yes, absolutely! The code snippet below reproduces the behavior I report above: it runs fine on 2.0.0rc1, but throws the error on 2.0.0.
I should add that I run these analyses on CPU on a machine with 128 GB of RAM.
import numpy as np

import tensorflow as tf
import gpflow as gpf
import tensorflow_probability as tfp
from gpflow.utilities import print_summary

gpf.config.set_default_positive_minimum(1e-7)

X, Y = np.random.random((2000, 2)), np.random.random((2000, 200000))

m = gpf.models.GPR(data=(X, Y),
                        kernel=gpf.kernels.Exponential(active_dims = [0,1]),
                                            mean_function=None)

print_summary(m)

opt = gpf.optimizers.Scipy()
opt.minimize(lambda: - m.log_marginal_likelihood(),
                    m.trainable_variables)

print_summary(m)

Thank you. Thanks to git bisect, it looks like the offending commit is 426f6d2b74e3e46604241de91a16896df193a609: Add jit flag to gpflow.optimizers.Scipy (#1190).
We since renamed the flag to compile, and indeed if you change your example as follows:
-opt.minimize(lambda: - m.log_marginal_likelihood(),
-                    m.trainable_variables)
+opt.minimize(m.training_loss,
+                    m.trainable_variables, compile=False)

then it also works in the latest 2.0.1 release and on the develop branch. You can manually reintroduce the bug by explicitly wrapping the training objective in tf.function():
objective = tf.function(m.training_loss)
opt.minimize(objective, m.trainable_variables, compile=False)

The underlying reason is that the compilation by tf.function() adds all constants into the graph - in this case this includes the data (X, Y) stored on the model. And the graph's size is capped... So it's an unfortunate interaction between TensorFlow internals and how GPflow makes use of TensorFlow.
Simply not using tf.function() can make your code significantly slower than it needs to be when e.g. the model objective gets called many times throughout the hyperparameter optimization. I think it might make a difference if you convert the data to tf.Tensor objects first: can you try the following change in your (actual) code:
-m = gpf.models.GPR(data=(X, Y),
-                        kernel=gpf.kernels.Exponential(active_dims = [0,1]),
-                                            mean_function=None)
+m = gpf.models.GPR(data=(tf.convert_to_tensor(X), tf.convert_to_tensor(Y)),
+                        kernel=gpf.kernels.Exponential(active_dims = [0,1]),
+                                            mean_function=None)

? Let me know if that solves your problem and then we can think what we can do to make GPflow work better out of the box.

Thanks, @st-- for investigating this issue! Indeed, Protobuf (the way how TF graph is represented) has a hard limit in 2GB, details here https://stackoverflow.com/a/51473218/7788672.
@clwgg, the rule of thumb would be using TF tensors as much as possible and minimizing NumPy and TensorFlow interactions.

I can confirm that wrapping the data input to GPR in tf.convert_to_tensor() fixes the issue I report. Thanks a lot @st-- for your help with this!

I don't understand why tf.function can't just convert the numpy arrays to tensors itself! So I shall blame it on them, it's not exactly our own bug. Still, we shouldn't have gpflow users suffer!
As a work-around for this bug, I think we should just change the models to explicitly convert from numpy arrays to tensors in the data argument to the model constructors. @awav what do you think? any other/better ideas?

I don't think we can classify it as a bug :) It is a special and unpleasant "feature". Anyway, it might change in TF2.2. @st--, If you don't mind I will test it on TF2.2 and make a PR with tf.convert_to_tensor in models.

I would consider "Doesn't behave as [reasonably] expected" as a bug - if we had clearly stated "do not pass numpy arrays as data to model constructors", it'd be different, but in fact the notebooks all use this pattern. Thanks for looking into it! I'll assign this issue to you then. By when do you think you'll be able to get to it?

I would consider "Doesn't behave as [reasonably] expected" as a bug

I was sarcastic :)

By when do you think you'll be able to get to it?

Wednesday, 22 Apr.

Hi @clwgg , thanks for helping us discover this issue - it's fixed in the latest 2.0.2 release!

Wonderful, thank you!

(And of course if it doesn't resolve your issue after all, please reopen it!)


Measurement validation before be able to add more.

This PR fixes #12351.

It disables the add measurement button if there is any validation error. For now, only measurements needs to be filled.
It adds a tooltip to inform the user what is going on.

Updated description including the gifcast.

Merging, working as expected, let's see if the message is not the desired one in the final acceptance.


Cloud Logging Handler import statement incorrect

On https://googlecloudplatform.github.io/google-cloud-python/stable/logging-usage.html#cloud-logging-handler the import statement is:
from google.cloud.logging.handlers import CloudLoggingHandler
According to the documentation for CloudLoggingHandler, https://googlecloudplatform.github.io/google-cloud-python/stable/logging-handlers.html#google.cloud.logging.handlers.handlers.CloudLoggingHandler, this should be:
from google.cloud.logging.handlers.handlers import CloudLoggingHandler

/cc @waprin

The class is imported into the handlers package in __init__.py as a convenience to minimize redundancy. The class documentation gives the fully qualified name. Both import statements will work. Closing this as works as intended, feel free to re-open if you're not happy with this answer.


Error: Node Sass does not yet support your current environment: Linux/musl 64-bit with Unsupported runtime (88)

using docker
FROM node:15-alpine as build

NPM version (npm -v): 7.7.6
Node version (node -v): v15.14.0
Node Process (node -p process.versions):

{
  node: '15.14.0',
  v8: '8.6.395.17-node.28',
  uv: '1.41.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.17.1',
  modules: '88',
  nghttp2: '1.42.0',
  napi: '8',
  llhttp: '2.1.3',
  openssl: '1.1.1k+quic',
  cldr: '38.1',
  icu: '68.2',
  tz: '2020d',
  unicode: '13.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}

Node Platform (node -p process.platform): linux
Node architecture (node -p process.arch): x64
node-sass version (node -p "require('node-sass').info"):

/app/node_modules/node-sass/lib/binding.js:13
      throw new Error(errors.unsupportedEnvironment());
      ^

Error: Node Sass does not yet support your current environment: Linux/musl 64-bit with Unsupported runtime (88)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1
    at module.exports (/app/node_modules/node-sass/lib/binding.js:13:13)
    at Object.<anonymous> (/app/node_modules/node-sass/lib/index.js:14:35)
    at Module._compile (node:internal/modules/cjs/loader:1092:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1121:10)
    at Module.load (node:internal/modules/cjs/loader:972:32)
    at Function.Module._load (node:internal/modules/cjs/loader:813:14)
    at Module.require (node:internal/modules/cjs/loader:996:19)
    at require (node:internal/modules/cjs/helpers:92:18)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:131:12)
The command '/bin/sh -c node -p "require('node-sass').info"' returned a non-zero code: 1

npm node-sass versions (npm ls node-sass):

<EMAIL_ADDRESS>/app
`--<EMAIL_ADDRESS>

react-scripts build
Error: Node Sass does not yet support your current environment: Linux/musl 64-bit with Unsupported runtime (88)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1

https://github.com/sass/node-sass#node-version-support-policy


Grasp of the Deep: Failure Effect is pre-errata version.

Currently in the System:

Failure The target takes half damage, and feels as though it's being crushed. The target becomes Grabbed and takes 6d6 bludgeoning damage; it can attempt to Escape with an Escape DC equal to your spell DC.

Errata'd version:

Failure The target takes full damage, and feels as though it's being crushed. The target becomes Grabbed but it can attempt to Escape with an Escape DC equal to your spell DC.

Aha, thank you. Apologies for that. It is fixed.


playground should support extract variable

Method coders allow you to extract a code expression into a temporary variable. Playgrounds should also support this extraction.


TypeError when getting device info

This is originally reported in https://github.com/shenxn/ha-dyson/issues/1#issuecomment-792259004 by @lolongan.
Here is the log
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 248, in async_setup
    result = await component.async_setup_entry(hass, self)  # type: ignore
  File "/config/custom_components/dyson_cloud/__init__.py", line 43, in async_setup_entry
    devices = await hass.async_add_executor_job(account.devices)
  File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.8/site-packages/libdyson/cloud/account.py", line 173, in devices
    devices.append(DysonDeviceInfo.from_raw(raw))
  File "/usr/local/lib/python3.8/site-packages/libdyson/cloud/device_info.py", line 31, in from_raw
    decrypt_password(raw["LocalCredentials"]),
  File "/usr/local/lib/python3.8/site-packages/libdyson/cloud/utils.py", line 29, in decrypt_password
    encrypted = base64.b64decode(encrypted_password)
  File "/usr/local/lib/python3.8/base64.py", line 80, in b64decode
    s = _bytes_from_decode_data(s)
  File "/usr/local/lib/python3.8/base64.py", line 45, in _bytes_from_decode_data
    raise TypeError("argument should be a bytes-like object or ASCII "
TypeError: argument should be a bytes-like object or ASCII string, not 'NoneType'

@lolongan This problem need further investigation. Maybe I will write a script for you to run and give me more info.

@lolongan This problem need further investigation.

With pleasure, when you wish.


Logging from tests appears not to work as described in the docs

Calling the init() defined as:
    fn init() {
        let _ = env_logger::Builder::new().is_test(true).try_init();
    }

in my tests appears not to produce any log output:
RUST_LOG=debug cargo test
    Finished test [unoptimized + debuginfo] target(s) in 0.02s
     Running target/debug/deps/log_fail-ea6852f038016c7e

running 1 test
test tests::test1 ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

However running env_logger::init() does seem to work:
#[cfg(test)]
mod tests {
    #[test]
    fn test1() {
	env_logger::init();
        debug!("hello!");
	info!("hello!");
	error!("hello!");
	assert!(true);
    }
}

RUST_LOG=debug cargo test
Finished test [unoptimized + debuginfo] target(s) in 0.01s
Running target/debug/deps/log_fail-ea6852f038016c7e
running 1 test
[2020-11-23T05:39:32Z DEBUG log_fail::tests] hello!
[2020-11-23T05:39:32Z INFO  log_fail::tests] hello!
[2020-11-23T05:39:32Z ERROR log_fail::tests] hello!
test tests::test1 ... ok
test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out
This is with env_logger 0.8.2 and log 0.4.11.

Thanks for the report! It's possible something changed about the way the test framework captures output so I'll take a look. If we don't need is_test anymore that would be great.

Thanks for the report! It's possible something changed about the way the test framework captures output so I'll take a look. If we don't need is_test anymore that would be great.

I just hit a similar problem that seems like it's related. If not, I'll open a separate issue.
Cargo.toml:
[package]
name = "logtest"
version = "0.1.0"
edition = "2018"

[dependencies]
log = "0.4"
env_logger = "0.8"

tests/test1.rs:
use env_logger;

#[test]
fn one() {
    env_logger::builder()
        .is_test(true)
        .format_timestamp(None)
        .try_init()
        .expect("Could not initialise test logging");
}

#[test]
fn two() {
    env_logger::builder()
        .is_test(true)
        .format_timestamp(None)
        .try_init()
        .expect("Could not initialise test logging");
}

Running cargo test gives:
running 2 tests
test two ... ok
test one ... FAILED

failures:

---- one stdout ----
thread 'one' panicked at 'Could not initialise test logging: SetLoggerError(())', tests/test1.rs:9:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    one

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass '--test test1'

Running cargo test gives:
running 2 tests
test two ... ok
test one ... FAILED

failures:

---- one stdout ----
thread 'one' panicked at 'Could not initialise test logging: SetLoggerError(())', tests/test1.rs:9:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    one

test result: FAILED. 1 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

error: test failed, to rerun pass '--test test1'

Logger can only be setup once per process. The two tests share the same process so you cannot set up logger in both. You can either make sure try_init() is only called once (e.g. by using std::sync::Once), or wait for subprocess testing.

I also thought that logging from tests did not work, but in my case, it was actually that I did not set the level filter correctly. Now all is working as it should when initializing with:
fn init_log() {
    let _ = env_logger::builder()
        .filter_level(LevelFilter::Trace)
        .is_test(true)
        .try_init();
}

And as expected from the doc, if I do not set is_test(true), the logs go to stderr and are mixed with the output from cargo test instead of being captured and output for the failing tests. So for me, all is working well.
@wykurz could this be that you just need to add filter_level to your env logger builder?

This is still not working for me. Here's full example:
#[macro_use]
extern crate log;

#[cfg(test)]
mod tests {
    fn init() {
        let _ = env_logger::builder()
            .filter_level(log::LevelFilter::Trace)
            .is_test(true)
            .try_init();
    }

    #[test]
    fn test_foo() {
        init();
        info!("foo");
    }
}

fn main() {
    env_logger::init();
    info!("bar");
}

When I run the binary all looks fine:
RUST_LOG=info cargo run
   Compiling logtest v0.1.0 (/home/mateusz/projects/logtest)
    Finished dev [unoptimized + debuginfo] target(s) in 0.49s
     Running `target/debug/logtest`
[2021-08-15T02:11:14Z INFO  logtest] bar

However running the test, I still see no log output:
RUST_LOG=info cargo test
   Compiling logtest v0.1.0 (/home/mateusz/projects/logtest)
    Finished test [unoptimized + debuginfo] target(s) in 0.61s
     Running unittests (target/debug/deps/logtest-627269ea88a03c02)

running 1 test
test tests::test_foo ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out;
finished in 0.00s

Am I doing something wrong here?
On Fri, Aug 6, 2021 at 5:53 AM Matthieu Pizenberg @.***>
wrote:

I also thought that logging from tests did not work, but in my case, it
was actually that I did not set the level filter correctly. Now all is
working as it should when initializing with:
fn init_log() {
let _ = env_logger::builder()
.filter_level(LevelFilter::Trace)
.is_test(true)
.try_init();
}
And as expected from the doc, if I do not set is_test(true), the logs go
to stderr and are mixed with the output from cargo test instead of being
captured and output for the failing tests. So for me, all is working well.
@wykurz https://github.com/wykurz could this be that you just need to
add filter_level to your env logger builder?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/env-logger-rs/env_logger/issues/186#issuecomment-894145978,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADWBCMHAOX76GSCN5SOR6TT3OWIXANCNFSM4T7AXQCA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@wykurz  Have you tried cargo test -- --nocapture? Test outputs are captured by default. They will be silently swallowed if the test succeeds.

Ah, that helps! Indeed, I now see the log output (FYI also w/o filter_level
Matthieu). Thanks Jing!
BTW I was looking for an option like this earlier but running:
cargo test --help

did not show it. Only after running this I see --nocapture:
cargo test -- --help

Very confusing! Although off topic for this thread.
Thanks again!
On Sat, Aug 14, 2021 at 11:42 PM Jing Yang @.***> wrote:

@wykurz https://github.com/wykurz Have you tried cargo test --
--nocapture? Test outputs are captured by default. They will be silently
swallowed if the test succeeds.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/env-logger-rs/env_logger/issues/186#issuecomment-898990718,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADWBCO7SPEEZM7D2SQAPDLT44ZT7ANCNFSM4T7AXQCA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


iFrame: close button that redirects to current opened panel page

I really like the feature but I think the icon might be a little confusing. If we think of the panel iframe overlay as a modal the close icon indicates that it closes the modal, not that it stays in the panel.
The first icon that comes to mind is to use a kind of pin icon instead:
http://fortawesome.github.io/Font-Awesome/icon/thumb-tack/
...to pin the panel to the screen.


Options allowJs and declaration don't play nice together

Expected behavior:
When using options.allowJs = true both .js and .ts sources get transpiled. When you add the option options.declaration = true, both .js and .ts sources should still get transpiled but now you should just also output definitions.
Actual behavior:
When you add the options.declaration = true option, only .ts sources get transpiled and .js is ignored.
Your gulpfile:
var gulp = require('gulp');
var ts = require('gulp-typescript');
var merge = require('merge2');  // Require separate installation

function doGulp(declaration) {
	var options = {
        declaration: declaration,
        allowJs: true,
        noExternalResolve: true,
    };

    var tsResult = gulp.src('src/**/*.{ts,js}')
        .pipe(ts(options));

    return merge([
        tsResult.dts.pipe(gulp.dest('release/definitions')),
        tsResult.js.pipe(gulp.dest('release/js'))
    ]);
}

gulp.task('with-declarations', function() {
	return doGulp(true);
});

gulp.task('without-declarations', function() {
	return doGulp(false);
});

Reproducing the issue
I have created a small project that reproduces the issue very clearly:
https://github.com/siggiorn/typescript-gulp-definitions-issue
The readme explains how to reproduce

Looks like a duplicate of Microsoft/TypeScript#7546

I think you're right, I hope they add support for that soon