[Identity] Security Analysis

Identity Security Analysis
In this issue I will go through the Security Analysis of our Identity library @azure/identity.
The goal is to highlight where we need to invest time studying and writing testing.
I will go over two main topics: Threat Modeling and Static Analysis. For each one of these topics, I will be presenting first what we know, then the tasks we know we have to invest time in moving forward.
Threat Modeling
We will be basing our Threat Modeling work on the work already done for the Java SDK (link).
Our Identity library offers the following credentials:

DefaultAzureCredential.
ManagedIdentityCredential.
EnvironmentCredential.
ClientSecretCredential.
ClientCertificateCredential.
DeviceCodeCredential.
AuthorizationCodeCredential.
InteractiveBrowserCredential.
UsernamePasswordCredential.

First we will explore what the Threat Modeling analysis represents, before we list the tasks that we need to do:
How to do the Threat Modeling
We'll be analyzing the inputs and outputs, how the inputs are validated, where the data is stored, and how it is sent to the server. Specifically, we will need to analyse:

That all of the inputs are validated.
That the valid form of the inputs are as secure as they can be (HTTPS endpoints instead of HTTP ones).
That all of the inputs have clear limitations in size.
That all of the possible exceptions don't leak sensitive information, like accessing cache files, intermediate tokens, etc.
That no sensitive information can be extracted from an attacker in the same computer, analyzing the memory usage of our client.
That none of our dependencies have known unfixed vulnerabilities.
That any known vulnerability about the platforms where our Identity library will run are mitigated (possible vulnerabilities in NodeJS and the browsers).

After doing that analysis, new issues should be made for each found vulnerability.
Threat Modeling tasks
Tasks:

[ ] Do the Threat Modeling of DefaultAzureCredential #XXXX
[ ] Do the Threat Modeling of ManagedIdentityCredential #XXXX
[ ] Do the Threat Modeling of EnvironmentCredential #XXXX
[ ] Do the Threat Modeling of ClientSecretCredential #XXXX
[ ] Do the Threat Modeling of ClientCertificateCredential #XXXX
[ ] Do the Threat Modeling of DeviceCodeCredential #XXXX
[ ] Do the Threat Modeling of AuthorizationCodeCredential #XXXX
[ ] Do the Threat Modeling of InteractiveBrowserCredential #XXXX
[ ] Do the Threat Modeling of UsernamePasswordCredential #XXXX

Static Analysis
For static validation of our TypeScript libraries, we mainly use ESLint.
Through enforcing a common set of TypeScript and ESLint rules, we are already able to minimize possible vulnerabilities from known software anti-patterns.
TypeScript and ESLint are not all we can do to secure ourselves. We should invest some time studying what recommendations exist from other TypeScript and ESLint users and communities.
A preemptive investigation of the available TypeScript and ESLint security plugins, done prior to this issue, can show us that, besides the evaluations that we already do, we must be able to ensure:

Having safe regular expressions (more information here).
To prevent calls to buffer with the noAssert flag set.
To prevent our code from having literal values stored in-code.
To avoid having requires() outside of the global scope.
To avoid using the square bracket notation (more information here).
To detect possible timing attacks (more information here).
To avoid using insecure standard methods, like pseudoRandomBytes().

For that purpose, we must discuss whether it makes sense to include the following dependencies to our packages:

https://github.com/mozfreddyb/eslint-config-scanjs
https://github.com/Microsoft/tslint-microsoft-contrib
https://github.com/mozfreddyb/eslint-plugin-scanjs-rules/
https://github.com/mozilla/eslint-plugin-no-unsanitized/
https://github.com/mozfreddyb/eslint-plugin-no-wildcard-postmessage/

Having said that, the concrete set of action items is:

[ ] Ensure that Identity has ESLint enforced.
[ ] Define a list of new ESLint dependencies to use.
[ ] Define a list of new ESLint rules to implement (if any).
[ ] Move the new ESLint requirements to the rest of the TypeScript SDK.

Once those tasks are completed, we will be able to consider a first security analysis of Identity to be fulfilled.
Feedback appreciated.

A first scoped review can have a cost of 3. It will spawn work that will be done in other previews.

After studying these and other plugins, we decided to not move through with them. Instead, we will make sure ESLint is enforced for identity: https://github.com/Azure/azure-sdk-for-js/pull/10257/files


New frame

I tried to add a new frame, this created a plane black frame - fine, however what it also did was turn my original frame plain black as well.

I can't reproduce this issue - did it happen after deleting frames @crocodile54 ?


HTYI: iPad page zooms in whenever loading/refreshing page

When first joining the game, the formatting is correct. After entering a name and room code and hitting submit, the screen zooms in so that the text-entry field fills the entire page. It's impossible to zoom back out. Refreshing the page won't zoom it out either, but makes the background appear to continue to zoom in over and over.

Once the session has been disconnected, it is possible to zoom back out again.

Started a new lobby, page only zooms in on refreshes.

This is ipad specific and ONLY for HTYI? or is this a global issue?

My guess is this is a global issue. I am looking into it.

I've not been able to reproduce under a few tests on locker iPad no. 26

Unable to reproduce


[Stdlib] Eliminate the UnicodeEncoding protocol.

This protocol was only used to fake recursive protocol conformances;
collapse it into _UnicodeEncoding.

This builds more on top of https://github.com/apple/swift/pull/11751.

@swift-ci please test Linux

@swift-ci please smoke test macOS

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 7e00eff714dcd192ce81da6ca41233e12441f742

Yippee! I'm going to fold this into https://github.com/apple/swift/pull/11852, because I have too many interrelated PRs going on and this isolated standard library change isn't a user-visible thing anyway.


Add 'copying' CacheConfigurationBuilder factory method to support inline modification of configuration

In order to support programatic tweaking of CacheConfiguration objects (and indirectly Configurations) we should add the ability to seed a CacheConfigurationBuilder with an existing Configuration object.  This would then allow us to build a cache configuration that is derived from a proposed configuration in some sensible way.

Funny, I had the same thought earlier this week - so I am for it!


Extra page b/t Table 21 and 22

Adding row for 2019 may have pushed this table to be too large.   Just flagging this to remember to fix.

Saw that - I can try now just to get it done before lunch....

Foolish me for thinking it'd be a quick fix. Not succeeded yet. Will chat with Chris at some point, but we'll get it done......

I tried commenting out the \clearpage, adding one in beforehand, and messing with the margins. Alas...
Table 22 doesn't add a page but is very similar (has longer caption).

Getting a lot of entries in those tables, needed to make the font smaller to fit it on the page.


Convert event list to tab layout

Is it a ?

[ ] Bug Report

[x] Feature Request

[ ] Chore

Feature Request
Feature Description

[ ] Similar to the Eventbrite app, we need to have a tab layout for the event list.
[ ] The event list item should also show general statistics like date, the percentage of tickets sold, number of attendees Checked In, and revenue generated

Would you like to work on the issue?
Yes

@iamareebjamal this is from #152

The thing with tabs is that it again requires you to nest fragments and then each of them will have adapters, meaning 3 different views attaching 3 presenters and the ViewPager is really buggy and causes memory leaks. I don't think someone will have that many events to manage to require tabs. Furthermore, it really won't fit in the tablet mode. With tabs on 1/3rd screen and detail on remaining

In the last meeting we were directed to convert events list into tab layouts.
Since the lists in the 3 tabs are identical, can we not reuse the same presenter, adapter and view by passing parameters to select different list each time?


Add Consistency Checks

Every now and then, the help channel cog will desync (mostly due to unavoidable issues from the discord API). This desync takes many forms, most prominent being:

Decrease in number of help channels available
Desync of dynamic help message in #how-to-get-help
Pins not being removed after a channel is closed Fixed
Cooldown roles not being removed after a session ends

These happen often enough that I think we should spend some effort to get them to automatically figure themselves out. I've divided this issue into three separate sub-problems, one for (mostly) each of the points above.
Pins
This one is relatively straightforward. We should get all pins when a channel is moved into dormant, and unpin them. I've checked the rate limit for that endpoint, and it appears to be 1 request / 5s / channel, so I think we're fine.
Cooldown roles
We already keep a list of which authors currently have a channel open, and I believe that does not desync in line with the cooldown roles (though it can be difficult to test). I think that means we can compare the list of people with the role, against the list of channel claimants, and remove any outliers. We should probably run this in some sort of periodic task, possibly every hour? That implementation detail can be left up to the author.
Channels & Channel Names
For the two desync patterns not mentioned yet, a simple cog reload seems to mostly do the trick. It's the go-to method for staff whenever we see a desync, and I estimate we run it bi-weekly right now. It only takes a few seconds (5 according to Akarys), so we should be fine to periodically just reload. Perhaps every hour as well.
@Akarys42 has brought up concerns about redis race conditions, we can discuss those here.
Closing Remarks
None of the mentioned fixes depend on each other, so we tackle each in separate PRs asynchronously.
I'm going to say that if no one has concerns within the next couple days, I'll be approving this issue for the cooldown role and pin fixes. I'll hold off on the last one till we figure out the race issue, but I'll update the issue once it's approved.

The pins issue is solved by #1909 and #1936.


Include classes for larger icon font sizes

Could do something like this and be used for icon sizing or whatever else.
.font-size-2x {
font-size: 2em;
}
.font-size-3x {
font-size: 3em;
}
etc...

Like http://fortawesome.github.io/Font-Awesome/examples/#larger
I don't have class name preferences.
Possibly related: #864

Something like this adds considerable bloat for niche cases. If you need to resize things, just do it in your own CSS.

Sounds good. Just didn't want to duplicate if it'd be added to MDL core.


correct that GrapheneOS is not a company

Hi @D3SOX, I noticed that you mention GrapheneOS is a "company", but it's actually a non-profit open source project and it will never become a company or collect profit in any way. It would be helpful if it was clarified that it's a non-profit open source project :)
https://grapheneos.org/faq#company
https://github.com/GrapheneOS

No, GrapheneOS will remain a non-profit open source project / organization. It will remain an independent organization not strongly associated with any specific company.

I was unsure about that part anyway, thanks for the improvement!

Thank you!!


Following symbolic link directory junctions on Windows

I'm not able to get ag to search inside directories that are windows directory junctions.  I tried passing in the '-f' option but this didn't work.  Is there a way to do this?

On further investigation, I've found that ag does enter windows junctions by default.  The only reason it wasn't entering windows junction in my case was because I had those junctions in gitignore.  Passing in '-u' solved the problem for me.
However, it still seems that the '-f' doesn't do anything on windows, so I'll leave this item open

There is a difference between junctions and symbolic links (to which the -f option refers)


Custom Map Point Icons

User should be able to select from various pre-defined map icons or should be able to upload their own icon.

done


Feature request: Option to strip process number argument

In Platypus 4.9 on Mac OS 10.10.3, when I create a droplet and run it, the first argument my script is getting is now something like -psn_0_6292992 (the number varies.) This appears to be a Carbon thing indicating the process ID. I don't really care about this and would like to keep the complexity of my droplets low so they can simply iterate over the file arguments and process them.
For now, I found a workaround (assuming this argument is always present when the final app runs on any version of Mac OS, which I'm not certain of.) For shell scripts at least, add a line at the top of the script that says:
shift

This is odd, now I can't reproduce the issue.

Now it's happening again. Possibly related to opening a saved profile and building the app bundle again. The profile happens to be outside the normal Profiles directory as I keep my Platypus scripts in separate git repos.
I whipped up a workaround in bash. It's verbose but it ignores the -p flag if it's present, and then the rest of the arguments can be used normally:
#!/bin/bash

# Parse out unwanted -p flag that may get sent by Platypus/Carbon
while getopts "p::" Option
do
  case $Option in
    p     ) echo "Scenario #4: option -p-\
                  with argument \"$OPTARG\"   [OPTIND=${OPTIND}]";;
    #  Note that option 'p' must have an associated argument,
    #+ otherwise it falls through to the default.
    *     ) echo "Unimplemented option chosen.";;   # Default.
  esac
done

#  Decrements the argument pointer so it points to next argument.
#  $1 now references the first non-option item supplied on the command-line
#+ if one exists.
shift $(($OPTIND - 1))

echo "File arguments: $@"

This is fixed in master and will be released as part of 5.0


ci(lint): add shell linter - Differential ShellCheck

Differential ShellCheck is a GitHub action that performs differential ShellCheck scans on shell scripts changed via PR and reports results directly in PR.
I saw that your scripts are in great shape, but I think that you might find differential-shellcheck action useful. It is able to produce reports in SARIF format. GitHub understands this format and is able to display it nicely as a PR comment, and on the Files Changed tab, please see below.

Documentation is available at @redhat-plumbers-in-action/differential-shellcheck. Let me know If you are missing some feature or setting. I'm always happy to extend functionality.

Note: I have also added Dependabot to keep your workflows up to date

/cc @zdohnal

Oh, never mind, I just noticed that you already have a shellcheck that uses SARIF. And since you don't have any shellcheck warnings in your current code base, you probably don't need differential scans. But I think you still might be interested in Dependabot.


Download a folder

Provide environment information
/opt/conda/bin/python
Python 3.7.10
gdown                   4.5.1
What OS are you using?
Ubuntu 20.04
Describe the Bug
Retrieving folder list
Traceback (most recent call last):
  File "/opt/conda/bin/gdown", line 8, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.7/site-packages/gdown/cli.py", line 152, in main
    remaining_ok=args.remaining_ok,
  File "/opt/conda/lib/python3.7/site-packages/gdown/download_folder.py", line 321, in download_folder
    remaining_ok=remaining_ok,
  File "/opt/conda/lib/python3.7/site-packages/gdown/download_folder.py", line 180, in download_and_parse_google_drive_link
    folder_page.text,
  File "/opt/conda/lib/python3.7/site-packages/gdown/download_folder.py", line 129, in parse_google_drive_file
    name=name,
UnboundLocalError: local variable 'name' referenced before assignment

Expected Behavior
All data should be downloaded like
Retrieving folder list
Processing file 1ZTwihF6t0jFNpwULPiLzhzEVrz9IpDL6 instance_mask.zip
Processing file 1BlSptrSE6ymRyHS2RPw-Dy2kBA7yHGm9 points.zip
Processing file 1IUVetmihs3NOAYN-PtFns5zkxsMMOcJ4 scannet_infos_0000_00.pkl
Processing file 141-rqz0uu0VLfFjqQoZJtjV5RjgtGjEE scannet_infos_test.pkl
Processing file 1Y3Tnv6ecD1EwwByza97vTsYdmyfrLQUZ scannet_infos_train.pkl
Processing file 1WkrJooM60x3HERAviH-dN2vseZNhGvvp scannet_infos_val.pkl
Processing file 12ERGYI7MLQwOZ22NvtD-Oqk2gemYVk9i seg_info.zip
Processing file 1Q7Kdk4vdVbeDe9BY0EhIH6ULxA2PMBs3 semantic_mask.zip
Retrieving folder list completed
Building directory structure
Building directory structure completed
Downloading...

If decrease the version to 4.4.0 by
pip install gdown==4.4.0

all data will be processed without errors
To Reproduce
gdown https://drive.google.com/drive/folders/1KuChuT4nsplD8APReFYkDEqW4FV6F14e -O data/ --folder

It looks working for me
% gdown https://drive.google.com/drive/folders/1KuChuT4nsplD8APReFYkDEqW4FV6F14e -O data/ --folder
Retrieving folder list
Processing file 1ZTwihF6t0jFNpwULPiLzhzEVrz9IpDL6 instance_mask.zip
Processing file 1BlSptrSE6ymRyHS2RPw-Dy2kBA7yHGm9 points.zip
Processing file 1IUVetmihs3NOAYN-PtFns5zkxsMMOcJ4 scannet_infos_0000_00.pkl
Processing file 141-rqz0uu0VLfFjqQoZJtjV5RjgtGjEE scannet_infos_test.pkl
Processing file 1Y3Tnv6ecD1EwwByza97vTsYdmyfrLQUZ scannet_infos_train.pkl
Processing file 1WkrJooM60x3HERAviH-dN2vseZNhGvvp scannet_infos_val.pkl
Processing file 12ERGYI7MLQwOZ22NvtD-Oqk2gemYVk9i seg_info.zip
Processing file 1Q7Kdk4vdVbeDe9BY0EhIH6ULxA2PMBs3 semantic_mask.zip
Retrieving folder list completed
Building directory structure
Building directory structure completed
Downloading...
From: https://drive.google.com/uc?id=1ZTwihF6t0jFNpwULPiLzhzEVrz9IpDL6
To: /Users/wkentaro/Documents/gdown/data/scannet/instance_mask.zip
100%|████████████████████████████████████████████████████████████| 56.1M/56.1M [00:59<00:00, 936kB/s]
Downloading...
From: https://drive.google.com/uc?id=1BlSptrSE6ymRyHS2RPw-Dy2kBA7yHGm9
To: /Users/wkentaro/Documents/gdown/data/scannet/points.zip
  1%|▋                                                          | 43.0M/3.70G [00:44<59:56, 1.02MB/s]

@wkentaro ok, but it did not work for me. Strange

it could have something to do with the region/language, as HTML's title can change in different regions.

I can confirm this bug happens to me on 4.5.1 but not on 4.4.0. My file is https://drive.google.com/drive/folders/1Qx_2_ePIqf_Z6SnpPkocUiPgFeCfePQh?usp=sharing it was tested on a machine located in France.

bug fix here : https://github.com/wkentaro/gdown/pull/210

@wkentaro please see this PR #210


change header 'tf grid marketplace' into Threfold NOW

change header 'tf grid marketplace' into Threfold NOW

it's called "TF Grid Demo" now. is this okay?


Unable to set pod.strategy.type

Hey Folks,
I have a small instalation of authelia that uses a PVC for persistence (ReadWriteOnce).
That means that RollingUpdate will not work for mu authelia instalation (since you cannot start another job before removing the previous).
I've been trying to set .Values.pod.strategy.type but I was unsucessful. Helm complains with:
  Type    Reason  Age                From             Message
  ----    ------  ----               ----             -------
  Normal  info    46m (x2 over 46m)  helm-controller  HelmChart 'flux-system/networking-authelia' is not ready
  Normal  error   37m (x2 over 46m)  helm-controller  Helm install failed: template: authelia/templates/deployment.yaml:22:13: executing "authelia/templates/deployment.yaml" at <include "authelia.deploymentStrategy" .>: error calling include: template: authelia/templates/_helpers.tpl:460:18: executing "authelia.deploymentStrategy" at <.Values.pod.strategy>: nil pointer evaluating interface {}.pod

It seems to be related to https://github.com/helm/helm/issues/8026
Reference to my deployment: https://github.com/fernandopn/swarm

https://github.com/authelia/chartrepo/pull/99 could be a solution to it, but I have no clue how to make those checks pass.

closed by #101

Thanks James for working on it. My setup works like a charm!
https://github.com/fernandopn/swarm/blob/main/cluster/apps/networking/authelia/helm-release.yaml


[Feat]: Add Selenium

What feature?
Primarily it is for automating web applications for testing purposes, but is certainly not limited to just that.
Boring web-based administration tasks can also be automated as well.
Add screenshots

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The template you used is incorrect. Please use the correct template and create a new issue.


Update docs with LiveConnectModes.

The changes here are showing how to build the LiveIntentID module in two different ways.

released with 4.21

released with 4.21


Reloader daemon destroys wp-includes contents

While using the local development with Vagrant, whenever I save a file inside public/ or support/, the internal vagrant daemon removes all the contents from public.built/wp-includes/ folder.
The daemon usually gets completely lost when I make too many changes on the filesystem at once (such as building my production assets with gulp).
What can I do to prevent this issue?

I also have this problem.
I found I was able to restore the folders by visiting /app/tmp, where a public.old folder was hanging around. I tried to delete that and was told that the folders in it (wp-admin, wp-content and wp-includes) were not empty. That was odd, because there was nothing inside them.
Renaming the folders allowed me to delete them. I then ran composer install in /app to rebuild the slug.

Thanks for the workaround @duncanjbrown this will get me through till it's fixed

I'm having this issue as well. Is there a log for errors from the rebuild process to check?

I've disabled the built-in daemon that rebuilds everything when any file inside the project is updated and created a gulp watch task which detects any file from public and throws it on public.built.
gulp.task('watch', function () {
    return watch('public/**/*', { ignoreInitial: false })
        .pipe(gulp.dest('public.built'));
});

This way, I only use ./support/app_slug_compile.sh when I use a composer update.
It works, at least. haha

@vinerz Can you post the change you made in a branch or something? I'd love to do the same.


Error: react-native-image-picker: NativeModule.ImagePickerManager is null.

I have been trying to figure out how to fix this error for several hours but I have not found a working solution yet. I have tried all the following steps listed in the error message, as well as running these lines of code that were suggested by other people in the issues thread:

npm uninstall react-native-image-picker
npm install<EMAIL_ADDRESS>--save
react-native link react-native-image-picker

However, none of these methods worked for me. The more I try pod install, react-native link, and other commands in my react native project, the more I feel like my code is breaking. I am now even unable to run yarn ios, equivalent to react-native run-ios.
A brief context and description of how to reproduce this error:

In my package.json, it says that I am using the version"react-native-image-picker": "^2.3.1",

I did the following in order to clean my react native project and re-eject my expo app:

Deleted both the ios and android directories in my root folder
expo eject
yarn ios

Everything worked fine up to this point. The app was running smoothly in the iOS simulator.

However, I wanted to test my react native app on my real iOS device as well, so I ran expo start, navigated to my browser to see the expo CLI, changed the Connection from LAN to Tunnel, opened the Expo Client app on my iPhone, clicked on the project to run it, and as soon as the JavaScript bundle was done loading, the error showed up in red below.

Is this an inherent problem with react-native-image-picker? I want to be able to build and run my app on my personal iOS device, but this error is blocking me. Should I be switching to a different react native module entirely?
Error: react-native-image-picker: NativeModule.ImagePickerManager is null. To fix this issue try these steps:
• Run `react-native link react-native-image-picker` in the project root.
• Rebuild and re-run the app.
• If you are using CocoaPods on iOS, run `pod install` in the `ios` directory and then rebuild and re-run the app. You may also need to re-open Xcode to get the new pods.
• Check that the library was linked correctly when you used the link command by running through the manual installation instructions in the README.
* If you are getting this error while unit testing you need to mock the native module. Follow the guide in the README.
If none of these fix the issue, please open an issue on the Github repository: https://github.com/react-native-community/react-native-image-picker

<unknown>
    AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:179783:20
loadModuleImplementation
    require.js:322:6
<unknown>
    AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:179691:60
loadModuleImplementation
    require.js:322:6
<global>
    New.js:20
loadModuleImplementation
    require.js:322:6
<global>
    BottomTabNavigator.js:17
loadModuleImplementation
    require.js:322:6
<unknown>
    AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:123951:63
loadModuleImplementation
    require.js:322:6
<unknown>
    AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:123855:49
loadModuleImplementation
    require.js:322:6
<global>
    AppEntry.js:3
loadModuleImplementation
    require.js:322:6
guardedLoadModule
    require.js:201:45
global code
    AppEntry.bundle?platform=ios&dev=true&minify=false&hot=false:220633:4

The issue is still there

Yep. Still there.

I still have this error


remove edge browser text

Fix for openreview/openreview#12

Tests are passing on my local.

Looks good, but I don't particularly like having just the link without any other text. I remember ARR complaining about this before and we changed the text to Reviewer Browser: https://openreview.net/group?id=aclweb.org/ACL/ARR/2021/October/Area_Chairs
If you think this is still not clear enough we can remove all text before the link

I think it works, but yes, Reviewer Browser does make it more clear than Edge Browser. The only issue I can think of is if we do change it to Reviewer Browser, we should make sure we do it everywhere else someone will come up with another issue.

What about "Reviewer Assignment Browser"?

@purujitgoyal instead of removing "Edge Browser" could you replace it with "Reviewer Assignment Browser"?


Change nodeset to ubuntu-xenial-arm64-openlab

The old nodeset is unstable and apt source is unavailable, we change the nodeset from ubuntu-xenial-arm64 to ubuntu-xenial-arm64-openlab to enable stable new nodeset.

We should merge this first, and I will sync this config to OpenLab team to enable the configure.

The commit needs to have a Signed-Off-By added, e..g, commit --amend --no-edit --signoff.

recheck

Yup, looks like it's using a different mirror now. The old builder hasn't been updated though (https://github.com/containerd/containerd/pull/4395#issuecomment-666866257).


🐛: Handover: Wrong CommPk status in garden

Old handover app in JC is showing correct (left), the new handover app (middle) seems to be showing "dynamicCommissioningStatus"
but should be showing "CommPkStatus"

@aman-riaz @BenSvend need to update Custom_CommissioningPackageV3

https://github.com/equinor/cc-components/pull/703


Add support for symbolic tensors to convert_to_tensor.

convert_to_tensor(x, sparse=False) is the API to densify sparse tensors. When used in that manner, the input is already a backend tensor. For this scenario, it makes sense to support symbolic tensors so that one can build a functional model using convert_to_tensor.
Also improved the documentation of convert_to_tensor.

Codecov Report
Attention: Patch coverage is 92.85714% with 1 line in your changes missing coverage. Please review.

Project coverage is 60.09%. Comparing base (5d36ee1) to head (93957f8).

Files with missing lines
Patch %
Lines

keras/src/ops/core.py
92.85%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (5d36ee1) and HEAD (93957f8). Click for more details.
HEAD has 6 uploads less than BASE

Flag
BASE (5d36ee1)
HEAD (93957f8)

keras
4
1

keras-torch
1
0

keras-tensorflow
1
0

keras-jax
1
0

Additional details and impacted files
@@             Coverage Diff             @@
##           master   #20539       +/-   ##
===========================================
- Coverage   82.15%   60.09%   -22.06%
===========================================
  Files         515      515
  Lines       47859    47872       +13
  Branches     7494     7495        +1
===========================================
- Hits        39317    28768    -10549
- Misses       6730    17348    +10618
+ Partials     1812     1756       -56

Flag
Coverage Δ

keras
60.09% <92.85%> (-21.91%)
:arrow_down:

keras-jax
?

keras-numpy
60.09% <92.85%> (+<0.01%)
:arrow_up:

keras-tensorflow
?

keras-torch
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Try to avoid ../../../Foo/Bar import mess

As an alternative to #76, we could leverage the following:

[ ] baseUrl, rootDirs and paths properties in tsconfig.json (planned for TS 2.0, requires nightly build for now: https://github.com/Microsoft/TypeScript/issues/5039)
[ ] resolve.root array in webpack config: should have helpers.root("src") in it

With those two, both TS & Webpack should be happy and let us write import statements relatively from src

I tested the above successfully, so that's a viable alternative and does not require an additional dependency as #76 requires and no specific syntax.

Cleanest alternative: barrels
index.ts files in each folder re-exporting classes, constants, etc
up to the root level where the whole app's API gets re-exported


rustflags and rustdocflags in config.toml can be string or list

The current code assumes rustflags can only be a list of strings not a single string. This apparently causes some projects to fail to build correctly.

I think this needs to be reopened.
Having this in config.toml works:
rustflags = ["-Ctarget-cpu=native"]

But this fails:
rustflags = "-Ctarget-cpu=native"

# RUST_BACKTRACE=1 cargo tarpaulin -v
Aug 20 14:17:35.660 DEBUG cargo_tarpaulin: set up logging
Aug 20 14:17:35.758  INFO cargo_tarpaulin: Running Tarpaulin
Aug 20 14:17:35.758  INFO cargo_tarpaulin: Building project
Aug 20 14:17:35.758  INFO cargo_tarpaulin::cargo: Cleaning project
thread 'main' panicked at 'called Option::unwrap() on a None value', /home/whirm/.cargo/registry/src/github.com-1ecc6299db9ec823/cargo-tarpaulin-0.18.0/src/cargo.rs:582:14
stack backtrace:
0: rust_begin_unwind
at /rustc/3d0774d0dc98084d25d95cc1909a8051ebbd9cb1/library/std/src/panicking.rs:517:5
1: core::panicking::panic_fmt
at /rustc/3d0774d0dc98084d25d95cc1909a8051ebbd9cb1/library/core/src/panicking.rs:93:14
2: core::panicking::panic
at /rustc/3d0774d0dc98084d25d95cc1909a8051ebbd9cb1/library/core/src/panicking.rs:50:5
3: core::ops::function::impls::<impl core::ops::function::FnOnce for &mut F>::call_once
4: <alloc::vec::Vec as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
5: cargo_tarpaulin::cargo::look_for_rustflags_in_file
6: cargo_tarpaulin::cargo::look_for_rustflags_in
7: cargo_tarpaulin::cargo::rust_flags
8: cargo_tarpaulin::cargo::run_cargo
9: cargo_tarpaulin::cargo::get_tests
10: cargo_tarpaulin::launch_tarpaulin
11: cargo_tarpaulin::trace
12: cargo_tarpaulin::run
13: cargo_tarpaulin::main
note: Some details are omitted, run with RUST_BACKTRACE=full for a verbose backtrace.

Thanks!

@whirm since I merged that PR there hasn't been a new release. Try installing the version on the develop branch and see if the issue persists

Oh, my bad. I didn't think about checking for that. Thanks!


Style support for size and symbol

These used to be supported, but now seem not to work. Here is what should be supported:

element symbol (for points only): circle, rect
element size, width, height
element border-radius (rects only)

size should work as "px", no-units and percents at a minimum

Fixed; supports standard web size units: px, pc, pt, in, cm, mm, %


Catch name collisions between types

See discussion in #57.

Ebert has finished reviewing this Pull Request and has found:

6 fixed issues! 🎉

But beware that this branch is 5 commits behind the pinterest:thrift_tng branch, and a review of an up to date branch would produce more accurate results.
You can see more details about this review at https://ebertapp.io/github/pinterest/elixir-thrift/pulls/185.

Rebased and modified it to handle a merge conflict.

@pguillory, would you still like to move forward with this?


Release

I'd like to do a release soon, ideally before SciPy.
Any objections?

I don't think so. The 0.6.0 release wasn't long ago (only 18 days ago on June 18th), but there has been significant stability improvements since and some API changes.

And releases are (usually) fairly cheap to do. We could easily do a release
just with hyperband, if we want to get that in user's hands as quickly as
possible once it's in master.
On Fri, Jul 6, 2018 at 11:31 AM, Scott Sievert<EMAIL_ADDRESS>wrote:

I don't think so. The 0.6.0 release wasn't long ago (only 18 days ago on
June 18th), but there has been significant stability improvements since and
some API changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403084019, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQHIjFbJZ8WcmGZH-YqgJVAeibT60aYks5uD5D_gaJpZM4VESzq
.

I think that we should not block a release on hyperband
On Fri, Jul 6, 2018 at 12:36 PM, Tom Augspurger<EMAIL_ADDRESS>wrote:

And releases are (usually) fairly cheap to do. We could easily do a release
just with hyperband, if we want to get that in user's hands as quickly as
possible once it's in master.
On Fri, Jul 6, 2018 at 11:31 AM, Scott Sievert<EMAIL_ADDRESS>wrote:

I don't think so. The 0.6.0 release wasn't long ago (only 18 days ago on
June 18th), but there has been significant stability improvements since
and
some API changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403084019, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIjFbJZ8WcmGZH-
YqgJVAeibT60aYks5uD5D_gaJpZM4VESzq>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403085205, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AASszM1ec7PNGne-mYHlal_poc7jO59hks5uD5IagaJpZM4VESzq
.

https://github.com/dask/dask-ml/pull/276 and
https://github.com/dask/dask-ml/pull/280 look somewhat close, if others
want to push on those today and tomorrow.
cc @jrbourbeau https://github.com/jrbourbeau
I'll plan on doing a release on Sunday.
On Fri, Jul 6, 2018 at 11:40 AM, Matthew Rocklin<EMAIL_ADDRESS>wrote:

I think that we should not block a release on hyperband
On Fri, Jul 6, 2018 at 12:36 PM, Tom Augspurger<EMAIL_ADDRESS>wrote:

And releases are (usually) fairly cheap to do. We could easily do a
release
just with hyperband, if we want to get that in user's hands as quickly as
possible once it's in master.
On Fri, Jul 6, 2018 at 11:31 AM, Scott Sievert<EMAIL_ADDRESS>wrote:

I don't think so. The 0.6.0 release wasn't long ago (only 18 days ago
on
June 18th), but there has been significant stability improvements since
and
some API changes.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403084019,
or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIjFbJZ8WcmGZH-
YqgJVAeibT60aYks5uD5D_gaJpZM4VESzq>
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403085205, or
mute
the thread
<https://github.com/notifications/unsubscribe-
auth/AASszM1ec7PNGne-mYHlal_poc7jO59hks5uD5IagaJpZM4VESzq>

.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-ml/issues/284#issuecomment-403086219, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABQHIr5sHzh-29_nEmG1VsQ2jmyF_CeXks5uD5MEgaJpZM4VESzq
.

I think that we should not block a release on hyperband

Agreed.

Did a 0.7.0 release today.


Unnecessary access request to drive root

Having an Asp.Net 5 application hosted on Windows Server 2012 R2 (possibly others?) requires one to assign read access to drive root C:\ in some cases.
The issue occurs when the IIS application pool is set to use a custom user. ApplicationPoolIdentity does not have such a problem.
Assigning full access to approot, wwwroot and logs folders does not fix the issue.
The IIS Platform Handler running has version 1.2.
The stdout file contains an error stating that the access was denied but does not provide any details on to which path.
A screenshot showing access request to the drive root C:\ can be seen below:

There seems to be other people having the same issue which we have been discussing on issue https://github.com/aspnet/Hosting/issues/449

Hmm, I'm not reproducing this on Win10. Can you give more details about your custom app pool identity setup?

Oh, and what version of DNX and tooling you're using?

I'm also getting this is on 2012 R2 with custom app pool identity using beta8 x64 and tooling. I also have an application setup in a virtual directory using the .Configure1(..) workaround (not sure if that has anything to do with it.)
@tratcher, make sure the I'd you use is not an admin.

The build is using runtime version dnx-clr-win-x<IP_ADDRESS>-rc1-15838
The tooling I have on my build computer is Beta 8. However, the web server does not have any tooling installed.
This is how I prepared my server:

Install HttpPlatformHandler 1.2.
Publish the website on file system.
Deploy it to the server.
Create a website on IIS and set its path to the wwwroot of the publish output (*** see below).
Set the application pool's CLR version to "No managed code"
I made sure that the website has HttpPlatformHandler module enabled on IIS.

Unfortunately I cannot give any specific information about the custom identity; it is created automatically using Plesk. However, I might try to answer your questions if you would like me to check and report some specific info about the user.
By the way, the website I am trying to run is at https://github.com/csunali/WebApplication2ForKestrel

Additionally, I don't have any virtual directories or Configure1 methods as @recalde mentions. Just, pure Web Application template (beta 8) and just a regular IIS website, with No managed code option chosen.

As @recalde stated, please make sure that the identity you use is not an administrator on your Windows 10 setup.
In addition to administrators, having it as a regular user would also allow him to access C:\, afaik.
So, please setup a user that has minimum access rights and does not have permission to any other folder than wwwroot, approot and logs.
That is how we setup our users, since we provide hosting services and we don't want people to access folders outside their websites.

@csunali, @recalde did you tried updating to rc1? Does the issue still reproduce?

Closing this, if this issue still exists please ping me.

@pakrym, I am having the same problem as @csunali  in a similar configuration: Windows 2012 Server using dnx-clr-win-x<IP_ADDRESS>-rc1-final with Plesk and a custom identity.
Running web.cmd directly starts kestrel without problems. Running under the custom identity fails unless I give it write permissions to the root folder where the application is located (in my case D:\).

@pakrym, I can confirm the same problem (Windows 2012 R2 Server, plesk, custom identity) using dnx-clr-win-x<IP_ADDRESS>-rc1-update1. It works If I change the Identity of the pool to an administrator account which has access to C:\

@pakrym, Sorry, was not able to respond to you earlier.
Yes, as other people also stated, the problem still occurs.
It is also very easy for you to test it. Forget about Plesk and just use a custom identity in your IIS application pool. Make sure that the custom identity does not have access to drive C and is not in Administrators role.

I was able to reproduce the issue and have some details.
Access denied. comes from running cmd, even if current user has access to file that is being executed by cmd /c list access is required all the way up to drive root by interpreter itself.
This problem will go away after switching to 'dotnet'

@pakrym, Please excuse my ignorance. What do you mean by switching to dotnet? Are you talking about the target framework monikers? E.g.: dotnet5.4.
P.S.: Are those monikers changing again with the RC2?

I mean dnx to dotnet cli (http://dotnet.github.io/) migration, the way applications would be built and packaged would eliminate cmd along with access issue.

Sounds great. Do you have an idea when should we expect that change? I mean, I guess you are already working on it but is it expected to be released along with the RC2 release?

Yep, RC2 is exactly when the switch happens.

Thanks for the confirmation (and the information)!
I have one last question. I am currently already using RC2 dev bits to build non-production test applications. Does it actually mean that I am already using that "dotnet" thing instead of the dnx thing? I guess no because of the VS ASP.NET Tooling being RC1, right?

No, you are still using dnx/dnu bits if you're not specifically use console and dotnet * commands.

Thank you again. Very much looking forward for the final RC2 release.
Cheers!

@pakrym Is there an issue where I can follow up with the new implementation? E.g. dotnet * commands, how to use them, etc.

Not an issue per-se but there is a repo https://github.com/dotnet/cli/


Overview page of source data

Similar to what we did for RIPARIAS early alert.
At the very least, the timestamp of the last occurrence import should be visible to visitors.

The timestamp of last import is now shown.

Similar to https://alert.riparias.be/about-data

Probably sufficient to provide a link to the GBIF download that is currently used by the dashboard.

Discussed with @EmmaCartuyvels1:
Provide a separate page that lists the (catch) GBIF datasets that are currently in the used GBIF download. Provide per dataset the title and latest publication date.

This is a nice to have, please focus on the other issues first @niconoe ;)


"IsDone" attribute not saving to .tasks file

The "IsDone" attribute does not get recorded into the solution .tasks file so when you reopen the project you dont know which tasks have already been done.

I will look into this when I get home tonight.
Could you please tell me which version of the extension and Visual Studio are you using?


how to use meshlap generate uv texture map?

Hi, I'm appreciate to your great work!
I converted lego_lowres.ply to lego_lowres.obj, then import lego_lowres.obj to ue4. The color of the model cannot be seen in ue4, so a uv texture map needs to be generated. I try to generate texture map using meshlab by Converting color point cloud to textured mesh. I refer to this tutorial：https://www.youtube.com/watch?v=6wP_e37t7PI  and https://stackoverflow.com/questions/47693251/how-to-convert-a-colored-point-cloud-into-a-textured-mesh. But what I get is not good. Open the lego_lowres.ply file with meshlab as shown below.

and then I generate the texture map through the above method as shown in the figure below:

Then I linked the texture map to ue4 as shown below.

There is a big gap between the effect after linking the texture map and the opening with meshlab. Do you have any suggestions? Thank you very much!!

I did some experiments. For example, I followed the steps below to generate a texture map as shown in the figure below：
“If you want a texture, you first need UV coordinates - the easiest and messiest way for an arbitrary mesh is to do Filters -> Texture -> Parameterization: Trivial per triangle, then use Filters -> Texture -> Transfer: Vertex Attributes to Texture. This can cause seams to appear. For my messy meshes I use the Smart UV in Blender and export it out as a .obj, then import it into meshlab and use the aforementioned Transfer: Vertex Attributes to Texture filter.” from https://stackoverflow.com/questions/47693251/how-to-convert-a-colored-point-cloud-into-a-textured-mesh.

When I link this texture map to ue4, the effect is as shown below


Undefined --build-arg FOO masks default value ARG FOO=1 in Dockerfile

docker build --build-arg FOO when FOO is not defined in environment variables of docker build is the same as --build-arg FOO=, which overrides potential default value for FOO in the Dockerfile:
$ cat Dockerfile
FROM alpine
ARG FOO=1
RUN ["sh", "-c", "echo '>>>' FOO=${FOO?NotSet} '<<<'"]

# Test 1
$ docker build --no-cache .
Sending build context to Docker daemon 3.072 kB
Step 1 : FROM alpine
 ---> 4e38e38c8ce0
Step 2 : ARG FOO=1
 ---> Running in 233c7eed414b
 ---> 57769cdb8cd7
Removing intermediate container 233c7eed414b
Step 3 : RUN sh -c echo '>>>' FOO=${FOO?NotSet} '<<<'
 ---> Running in e60f94a576ab
>>> FOO=1 <<<
 ---> dbb6171809d4
Removing intermediate container e60f94a576ab
Successfully built dbb6171809d4

# Test 2
$ docker build --build-arg FOO=2 --no-cache .
Sending build context to Docker daemon 3.072 kB
Step 1 : FROM alpine
 ---> 4e38e38c8ce0
Step 2 : ARG FOO=1
 ---> Running in 3b4cd1fb6856
 ---><PHONE_NUMBER>fb
Removing intermediate container 3b4cd1fb6856
Step 3 : RUN sh -c echo '>>>' FOO=${FOO?NotSet} '<<<'
 ---> Running in beee47a05904
>>> FOO=2 <<<
 ---> fc431d9ed6d7
Removing intermediate container beee47a05904
Successfully built fc431d9ed6d7

# Test 3
$ FOO=3 docker build --build-arg FOO --no-cache .
Sending build context to Docker daemon 3.072 kB
Step 1 : FROM alpine
 ---> 4e38e38c8ce0
Step 2 : ARG FOO=1
 ---> Running in 9a3a9e3a4e3e
 ---> 09f8df99bbf9
Removing intermediate container 9a3a9e3a4e3e
Step 3 : RUN sh -c echo '>>>' FOO=${FOO?NotSet} '<<<'
 ---> Running in 0e437a932631
>>> FOO=3 <<<
 ---> 5e3652eacd23
Removing intermediate container 0e437a932631
Successfully built 5e3652eacd23

# Test 4
$ docker build --build-arg FOO --no-cache .
Sending build context to Docker daemon 3.072 kB
Step 1 : FROM alpine
 ---> 4e38e38c8ce0
Step 2 : ARG FOO=1
 ---> Running in 2d807e3cc158
 ---> e126e82707ce
Removing intermediate container 2d807e3cc158
Step 3 : RUN sh -c echo '>>>' FOO=${FOO?NotSet} '<<<'
 ---> Running in 158ce7c7c673
>>> FOO= <<<
 ---> 3d6bdfbe1c02
Removing intermediate container 158ce7c7c673
Successfully built 3d6bdfbe1c02

Test 3 shows an undocumented feature where just setting the environment variable name with no =value to --build-arg makes docker build take the value from its own environment variables.
(Not documented in https://docs.docker.com/engine/reference/commandline/build/, or in https://docs.docker.com/engine/reference/builder/).
This is a useful feature that should be documented; it's also mimicked in docker-compose.
However, the corner case where the variable is not defined either in the docker build own environment could be improved:
Currently, an empty string is used in such case, which is fine except that it masks the potential default value defined in the Dockerfile, see test 4.
I think it would be better in this case to let the default value in Dockerfile apply: if the docker build command-line says to take the value of FOO from the environment variables of the process, and this environment variable is not set, then it makes more sense to me to do as if no --build-arg was passed, because none was set.
This would result in not masking the default value from the Dockerfile, which I believe is a good thing.
If this behavior change is accepted in docker engine, then it could be mirrored in docker compose where there is a second level of default values (.env) and a similar issue. See docker/compose#3608.

$ FOO= docker run -e FOO ubuntu env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=53e66508d17a
FOO=
HOME=/root

$ docker run -e FOO ubuntu env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=cd3bf89a71c0
HOME=/root

For consistency it does make sense to treat a missing build-arg env as not having specified --build-arg at all.


Add int16 support to RELU

RELU should support int16 for int16x8 models

#2727 is still open

#2727 is still open


Entry points require setuptools at runtime

Consider the following setup.py (silly minimal reproducer):
import setuptools

setuptools.setup(
    name = 'print-nl',
    version = '1.0',
    entry_points = {
        'console_scripts': ['print-nl=builtins:print'],
    }
)

This generates a command that requires setuptools, yet doesn't declare the dependency:
$ print-nl
Traceback (most recent call last):
  File ".../bin/print-nl", line 6, in <module>
    from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'

It isn't clear at all that a fix/workaround for the error about missing pkg_resources is to add setuptools to install_requires. The entry script is, IMO, an implementation detail the user shouldn't care about.

I'm not entirely clear what is being flagged here, but note that if the project is installed from a wheel using pip, the resulting entry point script does not depend on pkg_resources, and in that case a runtime dependency on pkg_resources would be wrong.

Using pip wheel to build the wheel (ensure you have setuptools) and pip install to install the wheel (no need for setuptools here) results in a functioning entry point.
If instead using wheel unpack I do not get any entry point, but that is expected. How did you obtain this entry point?

I'm assuming either setup.py install or pip install from source, which uses a non-PEP 517 build and so runs setup.py install behind the scenes.
The point (as best I can understand it) of this ticket is that it's difficult to know what to do to handle an installer that adds a runtime dependency to a project (that the project can't know about).
Of course, if you do setup.py install then you by definition have setuptools already present on the target system. But I think that the RPM build process does something like install to a temporary location, then copy the installed files into the RPM for later deployment on a different environment. That's a special case that may need to be handled by the RPM build process (as "copy an installation somewhere else" isn't a typical use case).

Indeed, this uses setup.py install or pip install which then adds a runtime dependency on pkg_resources in case an entry point is used.
In this case I think setuptools should not be added to install_requires because the import pkg_resources is generated and is indeed an implementation detail of the build system.

Relevant discussion that led to this ticket https://discuss.python.org/t/build-system-and-undeclared-dependency-on-it-during-runtime

Avoiding the dependency is best for setup.py install due to the very bad performance of pkg_resources which does not scale -- its performance gets worse as the size of site-packages increases.  A hack (https://pypi.org/project/fastentrypoints/) to avoid it was noted at https://github.com/pypa/setuptools/issues/510

I see. It looks like we are indeed using an unsupported combination tools (which we'll try to improve by moving to pip directly), and the bug isn't in setuptools.
Thanks for your patience here, and sorry for the noise!


Hide top meu in SPFx Personal apps

Ability to hide the top menu in a SPFx personal app.
I am developing an enterprise application using SPFx, I have a lot of functionality so I use navigation in my app (react routing) but the tab at the top of the page interferes with it and makes it less usable.
I would like to have the ability to hide that and have the full screen real-estate to display my app and my custom navigation.

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

ID: bac71237-d078-e29e-4115-5efbbbebd3ec
Version Independent ID: 5af01d79-5f92-b256-2872-34266ea14d9f
Content: Building Microsoft Teams Tabs using SharePoint Framework
Content Source: docs/spfx/integrate-with-teams-introduction.md
Product: sharepoint
Technology: sharepoint-framework
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

That isn't possible at this time.


[feature-request] Global Application menu

I would like to request a feature. Can you guys add a global application menu if it possible just like the macos one or kde global menu

No, this is a status bar and not an application launcher. If you want something similar to Mac OS, you can probably customize wofi to behave similar enough to it.


Priorities

First priorities:

[x] Simple lit mesh rendering
[x] Mesh slices, volume slices with parametric plane as uniform
[x] Text rendering (via gui toolkit)
[x] Offscreen rendering
[x] (collections / instancing)
[x] Solidify scene graph and updates
[x] Camera controls

[x] orbit: up stays up, as in https://threejs.org/examples/?q=control#misc_controls_transform
[x] pan/zoom (orthographic): zoom to point!

[ ] Docs: getting started, guide, reference
[x] Picking #51
[ ] Clipping planes?
[ ] Simple volume rendering (MIP, surface)
[ ] glTF file format?

Things to solve to start calling the API "stable":

Refactor the linalg system to be more Pythonic? Maybe consider #10
alpha blending
Be consistent in function arguments w.r.t. x, y (z) vs tuple vs Vector3.

The remaining tasks are now represented as issues or part of a checklist in another issue. Closing this.


Multiline Comments

Moved from https://github.com/tsubasaogawa/tfmodblock-vscode-extension/issues/5

NOTE
variable "baz" {
  type        = map(number)
  description = <<EOD
    this is heredoc
    description
  EOD
}

↓
module "tfmodblock" {
    source = "."

    //     this is heredoc
      description

    baz   = {}
}

released


Set Start Pos / Rot And Make Client Quieter

Before this component comes alive, the parent object is instantiated, with or without a position / rotation.  Even without, the prefab may have a default location defined.  Added the Start() method to get this component in sync.
Made client quieter by checking for change in crouching.  Without this check, client standing still spams server with the same message.

Looks good, thank you.


"docker-compose down" using the version 2 file format kills weave containers

Using weave v 1.4.5, docker v1.10.2, docker-compose v1.6.2
I am not sure if this is an issue with weave or with docker-compose, but I can only reproduce the problem when using weave.
I have reproduced the case using the docker-compose.yml file from the weave-and-docker-platform guide's app directory using a local docker instance running under Linux.

Change the docker-compose.yml file to be in the version 2 format
Run docker-compose up -d
Run docker-compose down

Following these steps will

successfully start the containers on docker-compose up
kill the weave and weaveexec containers on docker-compose down
leave the started containers runing as docker can no longer communicate with the docker daemon

You should be able to restore communication with Docker by running eval $(weave env --restore)
@roverwolf could you post the output of docker logs weaveproxy please?

@bboreham Yes, restoring communication with Docker is not an issue.
I posted the log to https://gist.github.com/roverwolf/a78578bd24f667ded4fa which was obtained just after the error.  A few seconds later the weaveproxy container goes away completely and does not show up in the list of docker ps -a (nor do the weave and weaveplugin containers).

I followed our guide, running Docker 1.10.3 and
$ docker-machine version
docker-machine version 0.6.0, build e27fb87
$ docker-compose version
docker-compose version 1.6.2, build 4d72027
docker-py version: 1.7.2
CPython version: 2.7.9
OpenSSL version: OpenSSL 1.0.1e 11 Feb 2013

After ./1-machine-create.sh I checked what docker version was being used:
$ docker $(docker-machine config weave-1) version
Client:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 15:54:52 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.10.3
 API version:  1.22
 Go version:   go1.5.3
 Git commit:   20f81dd
 Built:        Thu Mar 10 21:49:11 2016
 OS/Arch:      linux/amd64

When running ./2-weave-launch.sh I noticed that it was launching weave 1.4.1, which I confirmed with
$ DOCKER_CLIENT_ARGS=$(docker-machine config weave-1) ./weave version
weave script 1.4.1
weave router 1.4.1
weave proxy  1.4.1
weave plugin 1.4.1

I stopped weave on the three machines with
$ for i in $(seq 3) ; do echo "## weave-$i" ; DOCKER_CLIENT_ARGS=$(docker-machine config weave-$i) ./weave stop ; done
## weave-1
## weave-2
## weave-3

and then replaced the weave script with
curl -L https://github.com/weaveworks/weave/releases/download/v1.4.5/weave -o weave

I then re-ran ./2-weave-launch.sh and confirmed the weave version with
$ DOCKER_CLIENT_ARGS=$(docker-machine config weave-1) ./weave version
weave script 1.4.5
weave router 1.4.5
weave proxy  1.4.5
weave plugin 1.4.5

I then moved on to ./3-replace-swarm-agents.sh followed, as per the instructions, by
cd ../app
./build.sh
eval "$(docker-machine env --swarm weave-1)"
docker-compose up -d
docker-compose ps

That all worked well.
And so did this...
$ docker-compose down
Stopping app_redis_1 ... done
Stopping app_web_1 ... done
Removing app_redis_1 ... done
Removing app_web_1 ... done
$ docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS               NAMES
44e6b0cbc7c8        weaveworks/plugin:1.4.5      "/home/weave/plugin"     27 minutes ago      Up 27 minutes                           weave-3/weaveplugin
9e4af267b3f7        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   27 minutes ago      Up 27 minutes                           weave-3/weaveproxy
dd20d78f1af2        weaveworks/weave:1.4.5       "/home/weave/weaver -"   27 minutes ago      Up 27 minutes                           weave-3/weave
691deea33734        weaveworks/plugin:1.4.5      "/home/weave/plugin"     28 minutes ago      Up 27 minutes                           weave-2/weaveplugin
3490a8af30f5        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   28 minutes ago      Up 27 minutes                           weave-2/weaveproxy
7716ee9a9214        weaveworks/weave:1.4.5       "/home/weave/weaver -"   28 minutes ago      Up 27 minutes                           weave-2/weave
a7a1182d5e4a        weaveworks/plugin:1.4.5      "/home/weave/plugin"     28 minutes ago      Up 28 minutes                           weave-1/weaveplugin
88aa34abd3ea        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   28 minutes ago      Up 28 minutes                           weave-1/weaveproxy
c69aefe2fcc5        weaveworks/weave:1.4.5       "/home/weave/weaver -"   28 minutes ago      Up 28 minutes                           weave-1/weave

I then changed the docker-compose.yml to the v2 format:
$ cat docker-compose.yml
version: '2'
services:
  web:
    build: .
    command: python app.py
    ports:
       - "80:5000"
    hostname: hello.weave.local
    environment:
       - "affinity:container!=app_web_*"
  redis:
    image: redis
    hostname: redis.weave.local

$ docker-compose up -d
Creating network "app_default" with the default driver
ERROR: 500 Internal Server Error: failed to parse pool request for address space "GlobalDefault" pool "" subpool "": cannot find address space GlobalDefault (most likely the backing datastore is not configured)

Based on the compose networking docs I added the following to the end of the the docker-compose.yml:
networks:
  default:
    driver: weavemesh

This allowed me to start the app...
$ docker-compose up -d
Creating network "app_default" with driver "weavemesh"
Creating app_web_1
Creating app_redis_1
$ docker-compose ps   Name                  Command               State              Ports
----------------------------------------------------------------------------------
app_redis_1   /w/w /entrypoint.sh redis- ...   Up      6379/tcp
app_web_1     /w/w python app.py               Up      <IP_ADDRESS>:80->5000/tcp

I then ran...
$ docker-compose down
Stopping app_redis_1 ... error
Stopping app_web_1 ... error

ERROR: for app_redis_1  Could not make request to target: unexpected EOF
ERROR: for app_web_1  Could not make request to target: unexpected EOF
Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "compose/cli/main.py", line 56, in main
  File "compose/cli/docopt_command.py", line 23, in sys_dispatch
  File "compose/cli/docopt_command.py", line 26, in dispatch
  File "compose/cli/main.py", line 191, in perform_command
  File "compose/cli/main.py", line 273, in down
  File "compose/project.py", line 228, in down
  File "compose/project.py", line 224, in remove_stopped
  File "compose/project.py", line 368, in containers
  File "compose/project.py", line 366, in matches_service_names
  File "compose/container.py", line 108, in labels
  File "compose/container.py", line 181, in get
  File "compose/container.py", line 230, in inspect_if_not_inspected
  File "compose/container.py", line 239, in inspect
  File ".tox/py27/lib/python2.7/site-packages/docker/utils/decorators.py", line 21, in wrapped
  File ".tox/py27/lib/python2.7/site-packages/docker/api/container.py", line 181, in inspect_container
  File ".tox/py27/lib/python2.7/site-packages/docker/client.py", line 153, in _result
  File ".tox/py27/lib/python2.7/site-packages/requests/models.py", line 812, in json
  File "json/__init__.py", line 338, in loads
  File "json/decoder.py", line 366, in decode
  File "json/decoder.py", line 384, in raw_decode
ValueError: No JSON object could be decoded
docker-compose returned -1

So that's not so good. Alas  docker ps still works just fine:
$ docker ps
CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS                         NAMES
fd099ecbc55f        redis                        "/w/w /entrypoint.sh "   3 minutes ago       Up 3 minutes        6379/tcp                      weave-3/app_redis_1
ee0a4acbe086        app_web                      "/w/w python app.py"     3 minutes ago       Up 3 minutes        <IP_ADDRESS>:80->5000/tcp   weave-3/app_web_1
44e6b0cbc7c8        weaveworks/plugin:1.4.5      "/home/weave/plugin"     38 minutes ago      Up 38 minutes                                     weave-3/weaveplugin
9e4af267b3f7        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   38 minutes ago      Up 38 minutes                                     weave-3/weaveproxy
dd20d78f1af2        weaveworks/weave:1.4.5       "/home/weave/weaver -"   38 minutes ago      Up 38 minutes                                     weave-3/weave
691deea33734        weaveworks/plugin:1.4.5      "/home/weave/plugin"     39 minutes ago      Up 38 minutes                                     weave-2/weaveplugin
3490a8af30f5        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   39 minutes ago      Up 39 minutes                                     weave-2/weaveproxy
7716ee9a9214        weaveworks/weave:1.4.5       "/home/weave/weaver -"   39 minutes ago      Up 39 minutes                                     weave-2/weave
a7a1182d5e4a        weaveworks/plugin:1.4.5      "/home/weave/plugin"     39 minutes ago      Up 39 minutes                                     weave-1/weaveplugin
88aa34abd3ea        weaveworks/weaveexec:1.4.5   "/home/weave/weavepro"   39 minutes ago      Up 39 minutes                                     weave-1/weaveproxy
c69aefe2fcc5        weaveworks/weave:1.4.5       "/home/weave/weaver -"   39 minutes ago      Up 39 minutes                                     weave-1/weave

But for some reason swarm is having trouble talking to weave-3:
$ docker logs weave-1/weaveplugin
INFO: 2016/03/20 16:37:51.945993 Weave plugin 1.4.5 Command line options: []
INFO: 2016/03/20 16:37:51.946875 Docker API on unix:///var/run/docker.sock: &[Os=linux Arch=amd64 KernelVersion=4.1.19-boot2docker BuildTime=2016-03-10T21:49:11.235199091+00:00 Version=1.10.3 ApiVersion=1.22 GitCommit=20f81dd GoVersion=go1.5.3]
INFO: 2016/03/20 16:37:51.946973 Listening on /run/docker/plugins/weave.sock for global scope
INFO: 2016/03/20 16:37:51.947041 Listening on /run/docker/plugins/weavemesh.sock for local scope
INFO: 2016/03/20 16:37:51.964901 Create network<PHONE_NUMBER>3a187bbce279886ac5b45a02460a2068245d45177e0928fe0db62e
$ docker logs weave-3/weaveplugin
invalid character 'C' looking for beginning of value

and so does machine...
$ docker $(docker-machine config weave-3) logs weaveplugin
Error running connection boilerplate: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": dial tcp <IP_ADDRESS>:2376: getsockopt: connection refused
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

Error: No such container: weaveplugin

but the machine is alive and I can ssh into it with docker-machine ssh weave-3. Looking at the docker logs in /var/log/docker.log shows that the docker daemon died:
time="2016-03-20T17:16:27.482365463Z" level=debug msg="GET /v1.15/containers/json?all=1&size=0&filters={\"id\":[\"fd099ecbc55f6a33a2352c68196d6d05bcb573944c9f69723ae5c23ee99a1710\"]}"
time="2016-03-20T17:16:27.491800040Z" level=debug msg="Remove interface vethwgfa30c failed: Link not found"
panic: runtime error: index out of range

goroutine 5355 [running]:
github.com/docker/libnetwork/etchosts.Delete(0xc82078ecb0, 0x6a, 0xc821906e00, 0x5, 0x8, 0x0, 0x0)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/etchosts/etchosts.go:154 +0x543
github.com/docker/libnetwork.(*sandbox).deleteHostsEntries(0xc821545180, 0xc821906e00, 0x5, 0x8)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/sandbox.go:815 +0x6c
github.com/docker/libnetwork.(*endpoint).sbLeave(0xc821906900, 0x7f9152764fb8, 0xc821545180, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/endpoint.go:599 +0xb35
github.com/docker/libnetwork.(*endpoint).Leave(0xc8213a2500, 0x7f9152764fb8, 0xc821545180, 0x0, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/endpoint.go:536 +0x1bf
github.com/docker/libnetwork.(*sandbox).delete(0xc821545180, 0xc82122be00, 0x0, 0x0)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/sandbox.go:199 +0xad4
github.com/docker/libnetwork.(*sandbox).Delete(0xc821545180, 0x0, 0x0)
	/go/src/github.com/docker/docker/vendor/src/github.com/docker/libnetwork/sandbox.go:166 +0x32
github.com/docker/docker/daemon.(*Daemon).releaseNetwork(0xc820001c80, 0xc821544e00)
	/go/src/github.com/docker/docker/daemon/container_operations_unix.go:1013 +0x4f1
github.com/docker/docker/daemon.(*Daemon).Cleanup(0xc820001c80, 0xc821544e00)
	/go/src/github.com/docker/docker/daemon/start.go:159 +0x3d
github.com/docker/docker/container.(*containerMonitor).Close(0xc820b87e00, 0x0, 0x0)
	/go/src/github.com/docker/docker/container/monitor.go:127 +0x68
github.com/docker/docker/container.(*containerMonitor).start.func1(0xc8212e9d5f, 0xc820b87e00, 0xc8212e9d60)
	/go/src/github.com/docker/docker/container/monitor.go:158 +0xaa
github.com/docker/docker/container.(*containerMonitor).start(0xc820b87e00, 0x0, 0x0)
	/go/src/github.com/docker/docker/container/monitor.go:239 +0xbc5
github.com/docker/docker/container.(*containerMonitor).(github.com/docker/docker/container.start)-fm(0x0, 0x0)
	/go/src/github.com/docker/docker/container/monitor.go:101 +0x2e
github.com/docker/docker/pkg/promise.Go.func1(0xc820fbfaa0, 0xc82087d0a0)
	/go/src/github.com/docker/docker/pkg/promise/promise.go:8 +0x1d
created by github.com/docker/docker/pkg/promise.Go
	/go/src/github.com/docker/docker/pkg/promise/promise.go:9 +0x5d
...

That is caused by a docker bug.
If that bug had hit weave-1 instead of weave-3, then swarm would have broken completely, which would result in the symptoms the OP saw.
It is a pity that the fix for the bug was not included in Docker 1.10.3, so I guess we will all have to wait until 1.11.


Bump version of language-css

Identify the Bug
https://github.com/atom/atom/issues/21954
Description of the Change
Bumping version of language-css from 0.44.4 to 0.44.5
Alternate Designs

Possible Drawbacks

Verification Process
All tests passed in language-css
Release Notes
N/A

I have a commit (https://github.com/DeeDeeG/atom/commit/99afd50d2dae61805142ab94ba75c0ec8b56e556) that fixes the package-lock.json. But there is now a failing test, so there is some work left beyond that.
@cssinate I can make my own PR here at the main Atom repo to continue working on this, or I can open a PR at your fork to add just my commit to this PR's branch. I'll lean toward making my own PR here if no response.

Either is fine with me. Whichever your preference is.
On Sun., Feb. 14, 2021, 3:45 p.m. DeeDeeG<EMAIL_ADDRESS>wrote:

I have a commit (DeeDeeG@99afd50
https://github.com/DeeDeeG/atom/commit/99afd50d2dae61805142ab94ba75c0ec8b56e556)
that fixes the package-lock.json. But there is now a failing test
https://dev.azure.com/DeeDeeG/b/_build/results?buildId=1099&view=logs&j=c5d9a21a-e43e-5eaa-4a5a-044feacfb7bd&t=1bdeab21-3bba-5fef-2971-1d9f5fd6fff7&l=144,
so there is some work left beyond that.
@cssinate https://github.com/cssinate I can make my own PR here at the
main Atom repo to continue working on this, or I can open a PR at your fork
to add just my commit to this PR's branch. I'll lean toward making my own
PR here if no response.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/pull/21955#issuecomment-778839150, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AGAOZVFLGDE6X22ZBIEBTGTS7AY6TANCNFSM4XPQFUKQ
.

I opened https://github.com/atom/atom/pull/21963. You can subscribe on the sidebar of that issue if you want notifications of any updates with that. (Or you can deliberately not do that to keep your inbox clean!!)
I do hope the failing test can be figured out and this can land land to fix the code highlighting. Thanks for getting the ball rolling!

I'm going to close this since there is a similar PR to bump language-css package. As @DeeDeeG suggested you can subscribe to changes on  #21963.


[camera] Seems to camera is zoomer than the native camera

I use plugin camera to take pictures. The picture I take with this plugin seems zoomer than the native camera.
How can I get the result is the same as the native?

Sorry


Add DCO App

I don't have permissions to add this: https://github.com/dcoapp
Probably should add verbiage in developer guide about it though.

Added.

I'll work on getting a repo in opensearch-project shortly, so we can close the POC.


Add rubocop

Thought it would be helpful if we'd add rubocop to the project to improve the code styles.
The current configuration uses the default configuration of Rubocop. It also includes two extra extensions:

rubocop-minitest to enforce best practices for the tests
rubocop-performance to enforce best practices for performance

I've ran rubocop --autocorrect-all already. It adds some noise, but I think it's doable. I've also generated a .rubocop_todo.yml to address non-autocorrectable notifications in a follow-up PR.

Hmm, rubocop doesn't support Ruby 2.4 and 2.5 anymore. Which I guess is fair as these are EOL Ruby versions.
I guess we've got two options here:

We install rubocop (and other gems) in the CI actions itself and don't depend on the gemspec as that will install rubocop (and others) also when we want to run the tests.
We drop support for EOL Ruby versions 2.4 and 2.5.

We currently don't use newer Ruby language features (newer as in 2.4+), so I guess it's more non-invasive to install Rubocop in the CI actions themselves. However, Ruby 2.4 and 2.5 are EOL, so we might as well not support them anymore.
Thoughts?

LOL.
I just argued we're not using any Ruby language features that were not implemented in < 2.6. However, as you can see in this failing CI action we could be using new language features.
Apparently, a non-explicit begin/rescue/ensure block isn't supported in Ruby < 2.6. Maybe we have a compelling reason to drop support for lower Ruby versions.
We might want to consider dropping support after all.


Sink undefined on emitting points to table

From @bkutil:
juttle> emit -points [{"key":"val"},{"key2":"val2"}] | view table
┌────────────────────────────────────┬──────────┐
│ time                               │ key      │
├────────────────────────────────────┼──────────┤
│ 2015-12-23T18:17:51.195Z           │ val      │
undefined 'Sink undefined: Ignoring new point key(s) "key2"'
├────────────────────────────────────┼──────────┤
│ 2015-12-23T18:17:52.195Z           │          │
└────────────────────────────────────┴──────────┘

The problem here is that 2nd point has a different key than 1st point, and our table does not accommodate that by default. The workaround is
juttle> emit -points [{"key":"val"},{"key2":"val2"}] | view table -progressive false
┌──────────────────────────┬─────┬──────┐
│ time                     │ key │ key2 │
├──────────────────────────┼─────┼──────┤
│ 2015-12-23T18:18:47.958Z │ val │      │
├──────────────────────────┼─────┼──────┤
│ 2015-12-23T18:18:48.958Z │     │ val2 │
└──────────────────────────┴─────┴──────┘

This is similar to https://github.com/juttle/juttle/issues/33 in that making -progressive false the default (for historical programs) would remove the error, and allow the user to see all data in the output.

The changes in #91 are a first step towards addressing this, but as I mentioned in the comment on #33, we'd need to add a bit more logic to delay the initial table rendering in order for more than one batch of points to arrive.

There's also the other obvious issue that we shouldn't be printing undefined in the error messages.

Both referenced issues #91 and #33 are closed, and we no longer emit "undefined" in this case, but the main issue of not seeing all fields remains:
juttle> emit -points [{"key":"val"},{"key2":"val2"}] | view table
┌──────────┐
│ key      │
├──────────┤
│ val      │
Warning: view table: Ignoring new point key(s) "key2"
├──────────┤
│          │
└──────────┘

@demmer were your recommendations to look at the whole batch not implemented? or did not cover emit -points?

This is fixed now.


The memory consumed by WSO2 APIM increases over time

Description
I have an instance of WSO2 APIM version 4.2.0 installed on an Oracle Linux 8 server which has 16gb of ram. The problem noticed is that the more time passes, the more the consumption of physical memory increases even if no request is sent to wso2 APIM. This behavior manages to consume all the available memory to the point of making wso2 APIM unavailable and even the server on which it is installed.
What could be the reasons for this behavior and how can I resolve it please?
I tried to reinstall the product, but nothing changed, the same behavior returns
Affected Component
APIM
Version
4.2.0
Environment Details (with versions)
Oracle Linux 8
Related Issues
No response
Suggested Labels
No response

We have analyzed this but couldn't observe the behaviour. It seems like this is local to your environment. I suggest getting a few heap dumps and analysing what object retains memory. This will help to identify the root cause for this.
Please feel free to reopen this issue if you find any clues.


cilium 1.9.2 ARP errors

After update to cilium 1.9.2 I started to observe these errors in my ARP tables on k8s masters:
kube-5.prod.xxx: arp -a|grep "xx:xx:8c:ae:ef:43"
kube-3.prod.xxx (xxx.xxx.173.56) at xx:xx:8c:ae:ef:43 [ether] PERM on eth0

kube-3.prod.xxx: arp -a|grep "xx:xx:8c:ae:ef:43"
kube-2.prod.xxx (xxx.xxx.173.55) at xx:xx:8c:ae:ef:43 [ether] PERM on eth0

As you can see on different nodes the same MAC address is bound to different IPv4 addresses.
Bare-metal K8s:
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.5", GitCommit:"e338cf2c6d297aa603b50ad3a301f761b4173aa6", GitTreeState:"clean", BuildDate:"2020-12-09T11:18:51Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.5", GitCommit:"e338cf2c6d297aa603b50ad3a301f761b4173aa6", GitTreeState:"clean", BuildDate:"2020-12-09T11:10:32Z", GoVersion:"go1.15.2", Compiler:"gc", Platform:"linux/amd64"}

P.S. Just noticed that my kube-proxy DS was up and running. Maybe related.

Thanks for the opening issue. Which node mac addr is this?

Thanks for the opening issue. Which node mac addr is this?

@brb It's actually kube-2.prod.xxx eth0 mac address.
kube-5 ip route:
ip route
default via xx.xx.173.62 dev eth0 proto static metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
xx.xx.173.0/26 dev eth0 proto kernel scope link src xx.xx.173.58 metric 100
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth1 proto kernel scope link src <IP_ADDRESS> metric 101

kube-3 ip route:
ip route
default via xx.xx.173.62 dev eth0 proto static metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
xx.xx.173.0/26 dev eth0 proto kernel scope link src xx.xx.173.56 metric 100
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth1 proto kernel scope link src <IP_ADDRESS> metric 101

@brb It's actually kube-2.prod.xxx eth0 mac address.
kube-5 ip route:
ip route
default via xx.xx.173.62 dev eth0 proto static metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
xx.xx.173.0/26 dev eth0 proto kernel scope link src xx.xx.173.58 metric 100
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth1 proto kernel scope link src <IP_ADDRESS> metric 101

kube-3 ip route:
ip route
default via xx.xx.173.62 dev eth0 proto static metric 100
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS> dev cilium_host scope link
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
<IP_ADDRESS>/24 via <IP_ADDRESS> dev cilium_host src <IP_ADDRESS> mtu 1450
xx.xx.173.0/26 dev eth0 proto kernel scope link src xx.xx.173.56 metric 100
<IP_ADDRESS>/16 dev docker0 proto kernel scope link src <IP_ADDRESS> linkdown
<IP_ADDRESS>/24 dev eth1 proto kernel scope link src <IP_ADDRESS> metric 101

kube-proxy sudden resurrection

Could you elaborate more on this?

kube-proxy sudden resurrection

Could you elaborate more on this?

@brb - My kubernetes is mangad via Puppet kubernetes module. So when any node is added to the cluster or reinstalled - the whole kube-proxy daemonset is reinstalled and this cannot be configured. I even have an issue related to this: https://github.com/puppetlabs/puppetlabs-kubernetes/issues/450#issuecomment-765367366

@brb - My kubernetes is mangad via Puppet kubernetes module. So when any node is added to the cluster or reinstalled - the whole kube-proxy daemonset is reinstalled and this cannot be configured. I even have an issue related to this: https://github.com/puppetlabs/puppetlabs-kubernetes/issues/450#issuecomment-765367366

Thanks. I don't see how running kube-proxy could have lead to this problem. Was it a fresh cluster? Would it be possible for you to try to reproduce it? If yes, could you run tcpdump -i any -w arp-$(hostname).pcap 'arp' on each node?

Thanks. I don't see how running kube-proxy could have lead to this problem. Was it a fresh cluster? Would it be possible for you to try to reproduce it? If yes, could you run tcpdump -i any -w arp-$(hostname).pcap 'arp' on each node?

@Antiarchitect No need to reproduce. The arping library is not thread-safe. Under the hood, it uses a raw socket which might mix responses. This explains the behavior you saw.

@Antiarchitect No need to reproduce. The arping library is not thread-safe. Under the hood, it uses a raw socket which might mix responses. This explains the behavior you saw.

Ok, closing. For two days all seems stable. Thank you so much @brb

Ok, closing. For two days all seems stable. Thank you so much @brb

Let's close it once https://github.com/cilium/cilium/pull/14709 which contains the fix has been merged.

Let's close it once https://github.com/cilium/cilium/pull/14709 which contains the fix has been merged.

@brb Hmmmm. Seems like it's not kube-proxy related because I've just caught this error and kube-proxy was completely disabled this time

@brb Hmmmm. Seems like it's not kube-proxy related because I've just caught this error and kube-proxy was completely disabled this time

Yes, as I said that it's not related. Please see https://github.com/cilium/arping/pull/7 for more details why it happened in your case.

Yes, as I said that it's not related. Please see https://github.com/cilium/arping/pull/7 for more details why it happened in your case.


Idris doesn't have Builtins or Prelude packages available

Issue description
When I run idris I get the following message:
 Can't find import Builtins
 Can't find import Prelude
     ____    __     _
    /  _/___/ /____(_)____
    / // __  / ___/ / ___/     Version 1.2.0
  _/ // /_/ / /  / (__  )      http://www.idris-lang.org/
 /___/\__,_/_/  /_/____/       Type :? for help

Idris is free software with ABSOLUTELY NO WARRANTY.
For details type :warranty.

The crucial part is the first two lines, which means that I don't have the ability to actually use any of standard library (e.g. 1 + 1 fails out).
This appears to be something akin to #7014 popping up again.
It also looks like asking Idris to list the available libraries blows up.
idris --listlibs
Uncaught error: /nix/store/y75ay6zfi5l20zkqnld1q81zw0arsfbg-idris-1.2.0-data/share/ghc-8.2.2/x86_64-linux-ghc-8.2.2/idris-1.2.0/libs/: getDirectoryContents:openDirStream: does not exist (No such file or directory)

Steps to reproduce
Install the haskellPackages.idris package. Then run idris from the command line. You should see the Can't find import Builtins... message.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.
 - system: `"x86_64-linux"`
 - host os: `Linux 4.9.75, NixOS, 18.03.git.3a763b9 (Impala)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 1.11.16`
 - channels(root): `""`
 - nixpkgs: `/etc/nixos/nixpkgs`

Note that version of nixpkgs being used is in the host os name, 3a763b91963ef747b188e7062d7a02119d2ef6d3

This is a me-too

I can confirm this as well. Anybody got an idea how we could go and fix this?

I had this issue too. Just installing idris as a haskell package doesn't add the libraries - strace shows it checking for a lib which doesn't exist. I reinstalled my haskell packages without idris and then ran
nix-env -f "<nixpkgs>" -i idris

and it now works (it no longer gives that error message and I can see functions from the prelude in the repl). My nixpkgs is at 26db7314.
I noticed there were some commits related to refactoring idris modules earlier this year, which may be related.

Oh that's interesting... so idris is now a top-level package? Yeah If just install idris instead of haskellPackages.idris everything works fine. I don't know if it's a priority to make haskellPackages.idris actually work, but just installing idris is fine for me, so I'm willing to close this issue if this is a known way of how haskellPackages is supposed to work.

install idris instead of haskellPackages.idris
Works for me, thanks!


Enable kindless upgrade management feature for baremetal

Description of changes:
Enable kindless upgrade management test for baremetal provider.
Testing (if applicable):
Documentation added/planned (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/lgtm


AssetManager load empty AssetBundle when register wrong namespace bundle.

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Issue
https://github.com/yiisoft/assets/issues/123

Looks good. Need CHANGELOG.

done.

Need fix AssetLoaderInterface description, because is work for non-exist classes also.
https://github.com/yiisoft/assets/blob/5e7084495c121ec02ef8cf7b376d2cbbaf7c9eef/src/AssetLoaderInterface.php#LL30C8-L30C44

The interface description is correct, it loads the AssetBundle by class name, since AssetUtil if the class does not exist, creates an AssetBundle which is explained in the interface.

Need fix AssetLoaderInterface description, because is work for non-exist classes also.
https://github.com/yiisoft/assets/blob/5e7084495c121ec02ef8cf7b376d2cbbaf7c9eef/src/AssetLoaderInterface.php#LL30C8-L30C44

The interface description is correct, it loads the AssetBundle by class name, since AssetUtil if the class does not exist, creates an AssetBundle which is explained in the interface.
https://github.com/yiisoft/assets/blob/369cd8d5a521669b7e4c16f5ad67ddd3bf3f6b9d/src/AssetUtil.php#L41

Loads an asset bundle class by name. is not correct.
Class may be non-exist. $name may be any string value.

Need fix AssetLoaderInterface description, because is work for non-exist classes also.
https://github.com/yiisoft/assets/blob/5e7084495c121ec02ef8cf7b376d2cbbaf7c9eef/src/AssetLoaderInterface.php#LL30C8-L30C44

The interface description is correct, it loads the AssetBundle by class name, since AssetUtil if the class does not exist, creates an AssetBundle which is explained in the interface.
https://github.com/yiisoft/assets/blob/369cd8d5a521669b7e4c16f5ad67ddd3bf3f6b9d/src/AssetUtil.php#L41

Loads an asset bundle class by name. is not correct.
Class may be non-exist. $name may be any string value.

That doesn't matter, AssetUtil::create(), creates a dummy class.

That doesn't matter, AssetUtil::create(), creates a dummy class.

It's matter for AssetLoaderInterface description. It's incorrect. AssetUtil has nothing to do with the interface.


Instance location map in case of missing data

Example:
https://mnm.eliotberriot.com/dashboard/db/instance-detail?refresh=30m&orgId=1
The upper left map shows lon|lat 0|0: https://dump.jemu.name/2017-04-crll5z7ffu42qkw.png
Wich isn't clearly visible as "no location data available", so I propose that in cases where there's no reliable location data, the map element should be hidden, as it's basically just a generic map with no information on it at that point.

The map is always pointing to 0/0 by default, because it's not actually focusing on the given instance location (I have no way to do this in Grafana at the moment). For the same reason, I cannot hide a widget automatically if it has no data, it's not supported either by Grafana.
However, in the current case, there was, indeed, a location for the oulipo.social instance. It was just not visible because the default zoom level of the map was too important. I tweaked that and now, the default zoom level should make any instance location visible immediatly.
Thank you for reporting this, can you confirm this now works?


Fix debug message

Fix debug message for dns resolver

Good catch, looks like this fix works as expected.
Thanks!


fix for #32612 : load saved custom Loss class

Attempt to fix https://github.com/tensorflow/tensorflow/issues/32612
Here's an example with a custom Loss class, including config to ensure it's properly reloaded:
class HuberLoss(keras.losses.Loss):
    def __init__(self, threshold=1.0, **kwargs):
        super().__init__(**kwargs)
        self.threshold = threshold

    @tf.function
    def call(self, y_true, y_pred):
        error = tf.abs(y_true - y_pred)
        is_small_error = error <= self.threshold
        squared_loss = tf.square(error) / 2
        linear_loss = error * self.threshold - 0.5 * self.threshold**2
        return tf.where(is_small_error, squared_loss, linear_loss)

    def get_config(self):
        cfg = super().get_config()
        cfg['threshold'] = self.threshold
        return cfg

The class can be used for a regression task this way:
model = keras.Sequential([
  keras.layers.Dense(30, activation='relu', input_shape=X_train.shape[1:]),
  keras.layers.Dense(1)
])

model.compile(loss=HuberLoss(2.0), optimizer="sgd")
model.fit(X_train, y_train, epochs=1, validation_data=(X_valid, y_valid))

# save and reload
model.save('model_with_huber_loss_class.h5')
model = keras.models.load_model('model_with_huber_loss_class.h5', custom_objects={'HuberLoss': HuberLoss})

# continue training
model.fit(X_train, y_train, epochs=1, validation_data=(X_valid, y_valid))

The problem was that saving_util.compile_args_from_training_config(training_config, custom_objects=None) supports custom_objects but custom_objects was not propagated to losses.get().
losses.get() later called deserialize(identifier) without specifying custom_objects while the custom_objects argument is supported by deserialize(): the default None was used and the custom class load failed.

@googlebot I signed it!

closing that PR. Wrong email address preventing CLA validation


runWeb()] [E] Fail to start server: listen tcp <IP_ADDRESS>:80: bind: permission denied

it show me "runWeb()] [E] Fail to start server: listen tcp <IP_ADDRESS>:80: bind: permission denied" when  run gogs container
docker-compose.yml
igogs:
  image: gogs/gogs
  ports:
    - "10022:22"
    - "10080:3000"
  volumes:
    - /opt/gogs:/data

modify gogs/conf/app.ini 中 HTTP_PORT 节点为 3000（为映射端口） 即可

+1 我也遇到了，填写的时候概念有点不清晰就混了

What? Could you guys speak some english here?

what do you want to know? @vityafx

whats the solution in english

The solution ist to change your Port to 3000 or any other port that is not being used already.

the ssh_port to 3001?

Any port that is not being used by any other process. Default gogs port is
3000. Trying won't hurt, so just try running gogs Witz another port.
atussec<EMAIL_ADDRESS>schrieb am Mo., 13. März 2017, 14:24:

the ssh_port to 3001?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gogits/gogs/issues/3503#issuecomment-286105619, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAWs6FX_Eh0Yg43m9a_0_Ugj7ycps7w2ks5rlUOngaJpZM4JqgTA
.

@atussec change your Port to 3000 in your gogs/conf/app.ini will work fine. Here are my settings
[server]
DOMAIN = localhost
HTTP_PORT = 3000
ROOT_URL = http://gogs.xxx.com/
DISABLE_SSH = true
OFFLINE_MODE = false

And I use Nginx-proxy to provide an reverse proxy.


Add metallb binaries + images build

Add MetalLB images build.
This PR adds two MetalLB images, speaker and controller. Both are part of normal MetalLB deployments (1 deployment for controller, 1 daemonset for speaker). The helm chart build will be pushed in a future PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Oh you know what, we need the new prow job and to make sure the cdk change has been made to add the new image repos. Adding a hold until those are done, but feel free to remove the hold when they are.
/hold

/unhold

Updated the checksums to match the new Go version from yesterday.

/lgtm

/approve

Not strictly necessary but including it in 0.10 branch for consistency.
/cherrypick release-0.10


[BUG]The harvester status appears to be setting up on the original host after restarting the host

Describe the bug
The harvester status appears to be setting up on the original host after restarting the host
To Reproduce
Steps to reproduce the behavior:

Install harvester via ISO installation. (node01)
Add two more nodes to the environment(node02 and node03)
Shut down node01, then bring it up again
Check the Harvester status on every node

Result:
The harvester status appears to be setting up on the original host but the other hosts are presenting running, however, the Harvester is running expectedly

Environment:

Harvester ISO version: master (716900d)
Installation Mode: ISO/app-mode
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Validated on master-head
When finishing restarting the host, the status on that host will be setting up, eventually, it will turn to be running


No matching distribution found for behavex

Cant install this
pip install behavex results in
ERROR: Could not find a version that satisfies the requirement behavex (from versions: none)
ERROR: No matching distribution found for behavex

make sure you running the cmd prompt as an admin

Hi @ed-sparkes , I was trying to reproduce this issue, but I could not generate the conditions to do it. Are you still having this issue? I think it might be due to the supported python versions, but just guessing.


Add offline Mode

If a request comes in which does not have a matching record in the current tape Betamax will talk to the real server, and subsequently fail (if the tape mode does not permit writing, e.g. READ_ONLY, READ_SEQUENTIAL).
IMHO it would be good to have an offline mode where Betamax is guaranteed not to talk to the real server but to fail immediately. The question is if this should be via a TapeMode or via a separate switch.
This would also help to prevent unintended potentially dangerous request to the real server, while refactoring.

Totally agree with offline mode, I want to test using tape in the machine that dont have connection to webservice. Is that possible???