Standardize indentation for (co)inductive types

The coding conventions said that we should have 1 space of indentation for constructors of inductives, but most code (and all new code) used zero spaces, whereas some old code used two spaces. I chose to follow the new code and use zero spaces everywhere and update the coding conventions accordingly.
In case you don't like my choice this can be changed to whatever other convention, I just wanted to make things consistent.

@bmmoore
I don't think this is that important and so can be left out. I think I indeed use something like ABC_name, but while working on these changes I think I saw a lot of cases (mostly by Traian, I guess) where the abbreviations were all lowercase. The only commonality is _ as the separator between the abbreviation and the name proper.

I also don't think it's too important to specify. But having existing code use several different styles is exactly what you might dislike and want to fix with another "Standardize ..." PR.


Broken on Windows 10

I don't have a copy of an earlier version of Windows handy to test at the moment. When I run the example app, the tray icon appears. When I click on the icon to open the menu, right click does nothing and left click causes a taskbar icon to briefly appear and then disappear, and no window is shown. The console logs:
master= ~/dev/src/menubar/example
11:31> electron .
[10804:0804/113130:INFO:CONSOLE(0)] app is ready
[10804:0804/113134:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113134:WARNING:browser_accessibility_manager_win.cc(94)] Not firing AX event because of no hwnd
[10968:0804/113134:INFO:renderer_main.cc(200)] Renderer process started
[10804:0804/113137:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113137:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113138:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113138:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113138:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113139:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd
[10804:0804/113139:WARNING:browser_accessibility_manager_win.cc(193)] Not firing AX event because of no root_delegate or hwnd

Opening this issue for the sake of documenting this as a known bug and as a starting point for when I have time in the future to dig in further.
using<EMAIL_ADDRESS><EMAIL_ADDRESS>

Not extremely helpful, but it seems to be working fine on Windows 7, I'll try it on my 8.1 machine at home tonight.

@skiant thanks for the report :) I had menubar working on my windows 8.1 machine prior to the upgrade; after upgrading to windows 10 I get what I described above. FWIW official Atom releases continue to work in w10, so it's something in between.

Seems to be working fine for me when running Windows 10 in a virtual machine.


Create Wireframes

All user-facing portions of our feature. See issue #11 for feature description

[ ] Determine what will need to be added where visually
[ ] Determine best wire framing tool to use
[ ] Comment below with wireframe screenshots for reference and/or slack channel pin
[ ] Link wireframes to readme

Wireframe: https://miro.com/welcomeonboard/TpeXnyUPLyRgqyiIGT1Zsoz9RyOd1SnV7DfRYZ9iE0VMR3b3PqqYe7xpBGcMFLjf


Put visibility logic in the useTimeFocus() hook.

I think we're better off having the logic for whether the focus is visible reside with the hook that defines it from the context, rather than in the display logic in TimeScrollView. This just makes that change.

sounds good to me.


Make _check_available() function public.

Hi chainer team,
its a good idea to check if the serializer works before starting training, this information should be exposed to the user.
I didn't change the __init__.py file though.
BR, Max

Good, thank you. Would you write a docstring and add it to the reference document?


Messages can't be synced from a new account after several posts

Generic information

OS name and version: iOS 13.6
Application build code: 4012
Network type (mobile/Wi-Fi):  WiFi

Bug description

Can't post new messages from a new account after posting several messags.
The last message sent from this account is
https://morpheus.desmos.network/transactions/3ECC1061CEE22924E2205D1F8F9ECFE8844DC28F0ECAA125CCDBBAB69DF8C328
which is the poll I have tested at #33
After that the posts can't be synced

Steps to reproduce

Expected behavior

@kwunyeung What error message do you get after long pressing the post?

It was signature verification error. I can't load that error again as there is no red background in that post now. I keep seeing the app trying to syncing every 30 seconds but the tx is not on chain.

@kwunyeung Is this still showing up?

No. This issue can be closed.


Expose VolumeService functionality via HTTP API

This is tracking issue; will be broken up later.

List all volumes - #904
Get a specific volume - #905
Create a volume. - #903
Destroy a volume - #907 (pending #906)
Push a volume to another node - #908
Handoff a volume to another node? Or do we want the lower-level release and acquire?
Clone a volume to a new volume.

We are moving our development planning to JIRA. This is issue is now being tracked at https://clusterhq.atlassian.net/browse/FLOC-889. You are welcome to file additional issues in GitHub if that's easier for you.


Adding prefix and suffix functionality for BitNumericTextField

We need to show the unit of the item in BitNumericTextFieldexactly what we have in BitTextField https://components.bitplatform.dev/components/textfield#example6
Also BitNumericTextField already has the suffix but it is not as like as the suffix in BitTextField

Thanks for contacting us. We're investigating this issue.
We'll let you know if it's possible to work on this issue.

This issue has been resolved and it will be available in the next pre-release version. It will be announced when the pre-release becomes ready.


wsl.exe as default terminal, crashes with exit code 1

VSCode Version:

Version: 1.49.0 (system setup)
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T13:22:08.892Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041

OS Version: Windows 10.19041

Steps to Reproduce:
1.Set Windows Subsytem for Linux 2 as default
2. Open up New Terminal Window, see crash details:
The terminal process "C:\Windows\System32\wsl.exe" failed to launch (exit code: 1).
 Yes
settings.json:
{
    "editor.suggestSelection": "first",
    "vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
    "window.zoomLevel": 0,
    "terminal.integrated.shell.windows": "C:\\Windows\\System32\\wsl.exe",
    "terminal.integrated.automationShell.linux": ""
}

I did search, but there are a massive amount of issues, and I don't see one specific to this, besides much older issues.

Realized my issue when looking back through this. Because I installed Docker first when configuring my machine, it made that the default when running wsl standalone with no arguments resulting in the crashing terminal window.
Running wsl --set-default Ubuntu resolved this issue.
Coincidentally, this seems like a minor oversight due to docker not dropping into a wsl compatible shell, and vscode/wsl not defaulting to an environment that has a compatible shell.
Who or where should I go to reach out to on the wsl side for that?

You could follow this up with https://github.com/microsoft/WSL/issues
From VS Code's perspective, we assume WSL is set up correctly and just run wsl.exe.

If you have a specific version of wsl which you want to have setup as the default THEN MAKE SURE TO DO THAT :)
Here is the way i ran it

get a list of different distros on your systemPS C:\Users\Superman> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
Legacy
docker-desktop-data
docker-desktop
Ubuntu-20.04

pick the one you want to usewsl --set-default Ubutnu-20.04

@LeeRuns are you running wsl through PS, as that behaves quite a bit differently to if you launched wsl directly as everything runs through a bunch of emulation (conpty) and PS may remove the sequences if it doesn't support them for example. If you run wsl directly as the default shell conpty runs in a special mode that skips the Windows console API emulation that is one of the things that could mess with this.
You can change the default shell in this dropdown:

I'd expect any WSL distro to work when launched as the default.


fix duplicated index issue

issue :
using relation with multiple same related model (in morph relations  ) will cause an issue with "record-id"
1

2 :

fix
using random ID:

I think this causes the records to be deleted and recreated every time the repeater is saved because Filament is not able to recognise the random ID as the ID of an existing record in the database? Am I correct?
If so, I think this is not the solution, and we will need to close the PR unfortunately

I think this causes the records to be deleted and recreated every time the repeater is saved because Filament is not able to recognize the random ID as the ID of an existing record in the database? Am I correct?
If so, I think this is not the solution, and we will need to close the PR unfortunately

no, this not the issue
I have a relation table, which is morph table, (many to many)

Here I have (one to many) relations, each item can be related more than once
The items were retrieved in the old case as follows:
record-$id,there are multiple record with the same $id , so the indexes cancel each other except last one, which is logical.
so the fix was to add a random unique string to the indexes

I understand the problem, I was explaining a new problem that this PR has introduced

I understand the problem, I was explaining a new problem that this PR has introduced

Hmmmm Oh, I understand now.. i will try to fix this

Hi, I'm going to close this since the fix doesn't work. Feel free to open a new PR with a working fix.


#544 Replace references to global Matter in Composite.bounds()

Replaces stray Matter.{module} with in-scope required equivalents.

Looks like this was resolved at some point before seeing this PR, but thanks again for raising it!

Looks like this was resolved at some point before seeing this PR, but thanks again for raising it!


Deploy Crossplane to all CAPA MCs

Following deployment of Crossplane to golem as well as successful PoC which was followed by the implementation of needed components we would like to deploy Crossplane AWS providers with restriction to S3, SQS and IAM providers to all CAPA MCs.

cc @mproffitt

Deployment of crossplane to all CAPA MCs is a relatively straightforward process and golem is now a pretty decent template for how this can be done as enablement is simply copying these files across locations.
@T-Kukawka Would this be expected to include customer CAPA MCs at this time or do you just require the test MCs?
As mentioned yesterday, we would prefer to upgrade crossplane to version 1.15.x ahead of rolling out

do u have an ETA for the rollout in general? after upgrade? so we can see how we can schedule Karpenter part?

We will discuss this in our planning session this afternoon and have an answer by EOD
Crossplane upgrade is currently being worked on.

Crossplane upgrade is being worked on and should be complete within the next few days.
Deploying crossplane to all CAPA MCs is a copy / paste of the structure that's on golem
I would advise:

Upgrade crossplane
Deploy upgrade to golem  only to verify the existing providers work with the current crossplane version
deploy other capa MCs to unblock you
Upgrade providers later

I can try prep the PRs for rolling crossplane before COP tomorrow then once crossplane is upgraded it can roll

We may want the EC2 provider for Cilium ENI mode https://github.com/giantswarm/roadmap/issues/2563 so we can create a SecurityGroup CR instead of putting its creation into some operator (since CAPA doesn't support creating custom AWS security groups). As discussed in chat, I'm adding this provider to golem for now, to develop and test that feature. We can consider later whether we want to extend our pre-installation to include the EC2 provider or not.

hey @mproffitt, is the crossplane upgrade done?

Crossplane upgrade is prepared but hasn't been deployed anywhere yet - I will pick this up in the morning to test and once verified will plan to roll core.

hey @mproffitt, as we want to make Crossplane and Karpenter( and other crossplane provider) available everywhere, how is it going?

@T-Kukawka Giantswarm clusters will roll in the morning. The PR is approved for this but honeybadger approvals came in late. I'll start prepping PRs for customer clusters tomorrow.

is that done?

@mproffitt do we by default enable the crossplane providers for AWS needed for Karpenter as on the test installation?

@T-Kukawka Crossplane is now rolled to all MCs across the board

do we by default enable the crossplane providers for AWS

No. This needs to be handled as part of the Karpenter rollout to installations to ensure its required providers are reflected in the <customer>-management-clusters/management-clusters/MC/crossplane/providers directory.
An example of this is https://github.com/giantswarm/giantswarm-management-clusters/tree/main/management-clusters/golem/crossplane/providers and is probably mostly a copy-paste and updating account IDs where IRSA is used

Karpenter configuration with Crossplane:
GS:

[x] golem
[ ] gazelle
[ ] goat
[ ] goten
[ ] grizzly

Customer:

[ ] alba
[ ] velvet

done


Fix d3.selectAll(HTMLCollection)

Using a selection created via e.g. var sel = d3.selectAll(someElement.children) used to work, but in https://github.com/mbostock/d3/commit/9c3df31216aa28d8252b216b558cbb5907480b5b#diff-d93c7c1ccac09d19287c11d2d115758aL61 a critical conversion to d3_array was factored out of that path. This resulted in such selections exploding when certain array-dependent methods were used, such as sel.sort().
Simple fix, plus now a test for this code path. (The existing test had only been exercising sel.selectAll but not d3.selectAll!)

Merged into #2591.


Remove the sentences about the project being beta

Koalas 1.0.0 will be released very soon.

LGTM, but how about merge this right after 1.0.0 will be actually released ??

No the changes here should be involved in the 1.0.0 documentation

Got it!

I am merging this to unblock the release.


Bump to version 1.1.1

Signed-off-by: Alex Co<EMAIL_ADDRESS>
Summary

Ticket:
What's Changed

Changed

Bump to version 1.1.1.
Update to latest dependencies.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: onimsha
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


feature branch validation of names

Today it's possible to hang a entire gitops promotion due to some developer writing a bad branch that only includes app-frontend-
Since gitops promotion knows the name when creating the feature it should be able to check if it ends with -. If so we should do an exit 1.
And write a log to the user that it's unable to apply due to naming.

I take it you mean we should validate the input to new? Since we read the PR desc for input when doing promote, we should prolly validate input here https://github.com/XenitAB/gitops-promotion/blob/f46a66dde2eb83b651962f3deaf34aaa71999eee/pkg/command/promote.go#L54 .


Empty state of field description/hint

Issue/opportunity
The empty state of question descriptions shows the question type by default. Is this expected?
For example a single choice bloc will display radio button in the form builder part of the platform.
Screenshots

Test case

4.01 (Build + share a form)
Surface Tablet
Microsoft Edge
In French

@connorscarolyns can you confirm if this is expected behaviour?


How to show on the carousel a piece of the previous and next slide?

How to show on the carousel a piece of the  next slide?

I have been using this for a long time, and it works.
I only saw some issues on Tablets... Make sure to take a look
        <Carousel
          ref={ref => (this.carousel = ref)}
          mode="parallax"
          loop={false}
          scrollAnimationDuration={200}
          width={WIDTH}
          height={HEIGHT}
          data={spots}
          renderItem={SpotPreviewWrapper}
          windowSize={2}
          onSnapToItem={this.onIndexChange}
          modeConfig={{
            parallaxScrollingScale: 0.75,
            parallaxAdjacentItemScale: 0.75,
            parallaxScrollingOffset: 80,
          }}
        />


Fix of incorrect using of set_difference in updateConnectionGraph function

Public-Facing Changes
Correct calculation of removed topics and services while updating connection graph.
Description
Now in websocket_server.hpp we have:
https://github.com/foxglove/ws-protocol/blob/5cdda39d9ed4e8287a5d27406f5e4f368bd0e1fc/cpp/foxglove-websocket/include/foxglove/websocket/websocket_server.hpp#L1158-L1159
And to find difference between them function set_difference is used:
https://github.com/foxglove/ws-protocol/blob/5cdda39d9ed4e8287a5d27406f5e4f368bd0e1fc/cpp/foxglove-websocket/include/foxglove/websocket/websocket_server.hpp#L1203-L1206
According to documentation of std::set_difference it can be used only for sorted ranges (which is not a case when we use unorderd_set).
To have O(1) complexity for insert and search operations on unordered_set, I suggest to use std::copy_if function to find difference between two unordered sets.

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


Created a scrollpane ui test

The purpose of this test is to debug input for effects like highlight.

Looks good, I'll merge and see what wacky stuff is going on with positions this time...


[SPARK-49927][SS][PYTHON][TESTS][FOLLOW-UP] Fixes q.lastProgress.batchId to q.lastProgress.progress.batchId

What changes were proposed in this pull request?
This PR is a followup of https://github.com/apache/spark/pull/48414 that fixes q.lastProgress.batchId -> q.lastProgress.progress.batchId to fix the test.
Why are the changes needed?
q.lastProgress does not have progress. We should fix it to fix up the broken build.
Does this PR introduce any user-facing change?
No, test-only.
How was this patch tested?
Manually
Was this patch authored or co-authored using generative AI tooling?
No.

I am going to merge this to fix up the build.
Merged to master.


When are you going to release v2.1.0 ?

Hi @tomturner,
I see the latest devel version supports Django 2.1.2 which is what I have already. Just wondering when are you planning to release a new version ?
Are there any particular blockers for a new release? If yes, which ones, maybe I can help with a poull request.
Thanks.

Not sure if it is a blocker, but static file handling appears to be broken for Django > 2.0. See: #197.

it would be great to see this release on pypi, looks the #197 was solved.

Would love to see this as well.
+1

+1

Done


Integration with focus.nvim

Have you RTFM'd?

[X] I have done proper research

Feature Request
It could be great to have a new native actions that leverage focus.nvim for opening files in new split.
I.e. instead of relying on vim split defaults or declaring hotkeys for vertical\horizonal split, the plugin can provide a new action that calls FocusSplitNicely functionality, so plugin users could set it as a default actuon for opening a file.
Currently, I am integrating it like this.
local focus = require("focus")
local fzf_path = require "fzf-lua.path"
require("fzf-lua").setup({
	actions = {
		files = {
			["default"] = function(selected, opts)
				local e = fzf_path.entry_to_file(selected[1], opts)
                                focus.split_nicely(e.path)
                                vim.api.nvim_win_set_cursor(0, {e.line, e.col - 1})
			end,
		},
	},
})

Never heads about this plugin before but it looks great.
Unfortunately, this is an endless rabbit hole, I cannot maintain an endless amount of plug-in integrations, that’s why the API exists as you so nicely demonstrated :)


place containers inside containers

That is infeasible; would require a complete rewriting of how containers are implemented.


Incorrect Log Resource Type for GAE Logs

Scenario:

otel collector w/ GoogeCloud exporter
app running in Google App Engine exporting OTEL data to otel collector

Desired Behavior: Correctly forward the GAE labels into GCP Cloud Logging.

Error - Blocks all log export:
It appears the logs export is using the wrong resource.type value for App Engine. It using gae_instance when the correct value appears to be gae_app.
Here is the error itself:

error	exporterhelper/queued_retry.go:367	Exporting failed. Try enabling retry_on_failure config option to retry on retryable errors	{"kind": "exporter", "data_type": "logs", "name": "googlecloud", "error": "rpc error: code = InvalidArgument desc = Resource type not supported: gae_instance\nerror details: name = Unknown  desc = log_entry_errors:{key:0 value:{code:3 message:"Resource type not supported: gae_instance"}}"}

Logs Explorer prefilled label filter:

Digging into the source, it looks like the issue might be this constant value here - resourcemapping.go#L46... which is then passed into the createMonitoredResource(..) function.

Thanks for reporting this.  I'll make sure it gets fixed.

@dashpole Do you have any guesstimate as to when that PR might get merged and released?

It should be fixed this week.  Its been 3 weeks since our last release, so it is probably appropriate to cut a release after that as well.


Avoid re-advertising existing channels when advertising new channels

Public-Facing Changes

Avoid re-advertising existing channels when advertising new channels

Description
When new channels are advertised, we broadcast all available channels to clients rather than just the newly added ones. This PR fixes it.
Fixes #146
Fixes FG-1793

Pinging for review @jhurliman @jtbandes

Can you port this change to ws-protocol repo too?

Already done. I have ported the version of this PR


Connect to Ppl chain to get the identity of delegates

Identity of delegates may give us some information to show to users such as twitter, website, email etc.
We should connect to the ppl chain, get the identity and somehow display these info, maybe only in "expanded mode" when the large description is shown.
BTW the ppl chain WS endpoints should be added in the network.json, and we should either export a pplApi from the NetworkContext, or even created an IdentityContext that only connects to the ppl chain and gets all the info.

Easy peasy - I'll take that task. Have done it in the Fellowship dashboard - would be a piece of cake

Completed with #124


Connect trace level verbose to symbol.exe parameter

currently symbol.exe always runs with verbose as parameter,
with this change, the tracelevel is set to verbose only if verbosity is checked, else runs with info level

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


[stable/redis] Add PodSecurityPolicy

Signed-off-by: juan131<EMAIL_ADDRESS>Is this a new chart
No
What this PR does / why we need it:
This PR adds the possibility to create a PSP for Redis.
Which issue this PR fixes

fixes https://github.com/helm/charts/issues/18368

Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm


Create shared library for psabpf

If we want psabpf to operate as a shared library, we need to change it's build structure to do just this. Commit 8b247a3 attempted to do this, but it modified the libbpf build to be shared, which we would rather avoid. A better approach would be to first modify libbpf to add -fPIC to the non-shared library build, so we can then link the static library into the shared psabpf library, as 8b247a3 tried to do.

Putting a link in to the comments @tatry made: https://github.com/P4-Research/psabpf/pull/31#issuecomment-1120805216


Can't use [folder]-[name] on symbolId

Hi @kisenka ,
Congratz for the changes :D I'm trying to setup the version<EMAIL_ADDRESS>with for example that config:
{
  test: /\.svg(\?v=\d+\.\d+\.\d+)?$/,
  include,
  exclude,
  use: {
    loader: 'svg-sprite-loader',
    options: {
      symbolId: '[folder]-[name]',
    }
  },
},

However the symbol only get named as '-exampleIcon' because [folder] has no effect. Is this a bug?

Hi @mistic!
If your image is in root build directory - yes, because there is no [folder] in this case.

Thanks for the answer @kisenka.  This is my current folder layout:
rootProjectFolder
-assets
-svg
-home
-warning.svg
-warning2.svg
So [folder] should return home right? However it isn't...

@mistic it's a bug, just published 2.1.0-2 with fix, please check

It's working now 👍


onSelectionContextMenu doesn't work with selectionOnDrag

Describe the Bug
The onSelectionContextMenu handler doesn't work when right-clicking a selection created with selectionOnDrag set to true, even though it does work when selectionOnDrag is set to false (or not set).
Your Example Website or App
https://codesandbox.io/s/brave-firefly-d5zjbf?file=/src/Flow.js
Steps to Reproduce the Bug or Issue
See the CodeSandbox. I have a (rudimentary, stripped version of my) custom context menu implemented that should show up when a user right-clicks a selection.
When selectionOnDrag is false, it works (Shift+select then right-click on the selection); when selectionOnDrag is true, it doesn't work and the browser context menu shows.
Expected behavior
onSelectionContextMenu should work regardless of how a selection came to be.
Screenshots or Videos
No response
Platform

OS: Windows 11
Browser: Chrome
Version: 108
React Flow 11.4.0

Additional context
No response

Your sandbox works fine for me (aside from a missing position: absolute on the ctx menu element, so it actually uses the top, left values).
When selectionOnDrag is true, the onSelectionContextMenu event is still fired and the context menu shown.
Did I miss something? :)

You must have, because it really doesn't work for me. What browser are you on? If you're also on Chrome I'll make a screen recording.
(I updated the Codesandbox with position: absolute on the menu (thanks, it's still early here) and an onPaneClick handler to hide the menu when clicking anywhere.)

I tried it in FF and Chrome, both worked fine, here's a quick clip.
https://user-images.githubusercontent.com/78412429/211290964-a9995df8-fd77-40b5-ac35-ef2cb76cfdff.mov

And what were your values for panOnDrag and selectionOnDrag there? Because it works for me if they are set to true and false, respectively (and you drag using Shift), but not when set to false and true (in that order).

https://user-images.githubusercontent.com/24462089/211293809-42f6d2a9-c41b-4629-b0e5-d140bc99e73d.mp4
Can't seem to get the context menu to actually show up on the Windows screen recording (it does appear for me) but at least this shows the custom menu isn't appearing. Last guess - are you on macOS?

Yeah, I'm using a Mac.
Have you tried logging if the event ever fires?

Then I'm guessing there's some difference in how (Chrome on) Windows and macOS implement the context menu? I couldn't see what else would cause this.
(Yes, I verified with logging that the event never fires, and edited down the Codesandbox to remove some of my custom context menu code as just the logging shows the problem as well. Now in the sandbox with panOnDrag=false and selectOnDrag=true the message "hi!" does not appear on selection context click, but with the reverse settings it does appear.)

Could you try to install the latest version 11.4.2 and add event.preventDefault() in your event handler?

That worked, thanks so much for the two quick fixes!


chore: update projen project type

The upgrade-main workflow is currently failing since we introduced a new projen project type for CDK8s recently.
Updating here for the workflow to resume. This is breaking for branch: 1.x as well and would be backporting there.
Part of https://github.com/cdk8s-team/cdk8s/issues/1185

💔 All backports failed

Status
Branch
Result

❌
1.x
Backport failed because of merge conflicts

Manual backport
To create the backport manually run:
backport --pr 821

Questions ?
Please refer to the Backport tool documentation

💚 All backports created successfully

Status
Branch
Result

✅
1.x

Questions ?
Please refer to the Backport tool documentation


Update New-SPUserSolutionAllowList.md

Filled in placeholder text.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sharepoint/sharepoint-ps/sharepoint-server/New-SPUserSolutionAllowList.md
:white_check_mark:Succeeded
View (sharepoint-ps)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[BUG] [unresolved dependency: io.delta#delta-core_2.12;1.2.1: not found]

This dependency package cannot be downloaded online because we are a private cloud environment
Can this dependency package be downloaded in advance and put in the docker image? We are Spark on K8S

This is not a bug. You don't have dependency you use in your code, so you have to add it.
You can build you own docker image on top of pure Spark image with all dependencies you need.
Which exactly docker image do you use?

thank u @dnskr
Now I have downloaded them in advance and put them under $SPARK_HOME/jars . It will work
But I added an $SPARK_HOME/extjar directory and it didn't work
"${SPARK_HOME}/conf/spark-env.sh"
"SPARK_CLASSPATH=${SPARK_CLASSPATH}:${SPARK_HOME}/jars/*:${SPARK_HOME}/extjars/*" >>

I need to add deltalake and S3 to the PySpark image


Add GitHub based dependencies key to deploy and undeploy

This is a first cut at adding dependencies to a manifest.yml file.  This adds a dependencies key where the dependency is a GitHub repo.
package:
  name: opentest
  dependencies:
      hellowhisk:
          url: https://github.com/paulcastro/hellowhisk
          version: 1.0.1
      myCloudant:
           source: /whisk.system/cloudant
           inputs:
                  dbname: MyGreatDB
  sequences:
    mySequence:
      actions: hellowhisk/greeting, hellowhisk/httpGet
  triggers:
    myTrigger:
  rules:
    myRule:
      trigger: myTrigger

This manifest references a GitHub project aliased as "hellowhisk", version 1.0.1 at the given URL.  If version is not specified, it will pull from master.
Dependencies that specify a source are interpreted as bindings, and we do a package bind.  url specifies a GitHub dependency and is treated as an independent deployment.  For example, the root package opentest refers to entities in the hellowhisk package using the package name format.  The following happens on deploy

wskdeploy downloads and unpacks a zip file of the gihub repo in $ProjectPath/Packages/<dependencyname>
Deploys dependencies first
Deploys root package

This PR does not include dependency graph management so use at your own risk.
There is a use case in tests/usescases/deptest that illustrates a project that has no local source code, just a manifest that combines the entities in a dependency.

@paulcastro Paul This PR should pass.
The only critical change is to change if params.ManifestPath != "" { to if params.ManifestPath == "" {

@houshengbo , can you update this PR, there are two commits inside. Also could you please add some CI code for this PR? It would help people under what this PR trying to do, if it resolves the dependency or Package binding issue, I think we're very close to wskdeploy version 1.0, right? Any comments? @mrutkows @paulcastro

@lzbj I think @paulcastro will take care of this PR, which is a derivative from one of his PRs.
I have already made sure this PR is able to pass all the CI tests.
I am not sure what you mean by CI code. Do you mean adding more tests for the code change?

@houshengbo , ok, got it, thank you. I think this patch is very important, so the corresponding use case and test code could help people know how to use it.

@lzbj if you approve, could you merge this?  I con't think I should merge my own code.  I can add comment, etc. in a separate PR.

@paulcastro Did we ever talk about supporting this in the spec.?

@mrutkows  Issue #41?

I'll close this and open a new PR -- I'm making changes to the manifest.


refactor(eddsa-poseidon)!: restrict message types

Description
The type supported for the EdDSA message has been reduced to BigNumber (either bigint or string which  must still be a stringified bigint))

Related Issue(s)

Closes #230
Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have run yarn style without getting any errors
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

awesome!! thanks @artwyman for your feedback. I am going to work through your comments right away.

Hi @f3r10, are you still going to work on this?

My apologies, @cedoor. I started a new job and have been really busy. I hope to contribute once I settle into it.


How to start on a new hardware platform to support  connectedhomeip?

Problem
As topic said, I want to run connectedhomeip on a new WIFI/BLE based platform which has its own WiFi/BLE API lib. I know matter is still at discussion stage and some commercial product will be coming end of 2021. Our product is not in the hardware certification list but we plan to join in near future.
What I want to investigate is software support/effort to run it with our SDK/platform. Is there any group or start-guide to refer? Besides, I don't find how to certificate new hardware platform for matter -- only find some steps for zigbee on your website.
Any comments are welcome. Thanks.
Proposed Solution

Please reach out to myself or @andy31415 and we can get you started. There is no guide sadly, but you can use an example platform in ~/.github/workflows for the workflows to build, and how they work. Thanks!


display of

example of code:

Regarding the nature of this document and the translation recorded in it, J. Wisseman Christie has offered the following summary:
<cit><quote rend="block">
The Kurungan inscription of 885 A.D. (Appendix A.2) is not principally a debt-clearance document. It records the purchase of wet rice land for 1 <foreign>kati</foreign> or 768 grams of silver by a religious personage, <hi rend="bold">for the purpose of presentation as a meritorious gift to a religious community</hi>. Part of the statutory gifts presented to the community from which the land was purchased took the form of the writing off of 7 <foreign>dhāraṇa</foreign> or 268.8 grams of silver, the sum of the interest on the community's debt. This apparently completed the repayment ot that debt, the sale of the land presumably having furnished the community with the funds needed to repay the principal, and perhaps a portion of the interest as weII. Although the document states that the aim of the transaction was the repayment of the community's debt, no hint is given as to how the debt was incurred, the exact amounts owed as principal and interest, and the person or institution to whom the debt was owed.</quote><bibl><ptr target="bib:WissemanChristie2009_01"/><citedRange>44</citedRange></bibl></cit>
The words I have quoted in bold require further consideration, as the text does not actually mention any religious community nor any meritorious gift, although both notions may be implied.

The status expressed by the compound <foreign>savaḥ karamān</foreign> clearly stands in opposition to the new status expressed, in line 9, by the compound <foreign>savaḥ śīma</foreign>.

current display:

the transformation does not yet yield the block quote I was hoping to get, in line with EGD §10.4.4

<hi rend="bold"> does not seem to implemented yet either

@danbalogh : could you formulate what display we expect here so that @ajaniak can implement it?

I have no set views on how block quotes should be displayed. I think that they should be shown as a separate HTML paragraph, set in at some distance from the left margin. I have not looked into the intricacies of how that display can be implemented given that a block quote in our system is part of a
 element and will often have text belonging to that
 both before and after the block quote. (This concern is why the I initially said in the EGD that a block quote should be on the same level as a
 rather than inside one. Back then, I was told - I don't remember by whom - that it would be preferable to have them as part of a
 and display would not be a problem.) So anyway, display as a block indented in every line. The contents of the <bibl> element should, I think be displayed in this case in parentheses, at the end of the citation. But again, whatever you decide on is acceptable to me.

OK, let me then make the following basic suggestion.

current display

desired type of display

@ajaniak : is that enough for you to work with?

Fine with me!

done, close the issue if you are satisfied. Nota that I had to change the CSS, so it can take until 2 hours for the current addition to work.

Yes, it looks good now. See screenshot attached. Thanks. Closing this issue.


Improvement of app

some refactor code and bug fixes
performance improved in initial load

Thanks, but I can't see the real changes from the formatting changes, so I just pushed a big reformat change to all of XmlNotepad so that you can merge that and then I will be able to see any real changes you made here.

I did merge that sir.

Thanks, but I can't see the real changes from the formatting changes, so I just pushed a big reformat change to all of XmlNotepad so that you can merge that and then I will be able to see any real changes you made here.

I did merge that sir.

Thanks, but I can't see the real changes from the formatting changes, so I just pushed a big reformat change to all of XmlNotepad so that you can merge that and then I will be able to see any real changes you made here.

I did merge that sir.

some of additional white spaces is just because of my vs configs
but the others are code


Need to seed database for tests

I got the testing piece pretty close with the new preheating.
One blocker was the script running in the GitHub action: https://github.com/themisterholliday/website/actions/runs/7160073049/job/19494041782
I'm unsure about the script, so I can't debug further.


lcdproc: pull upstream fix for fno-common toolchains

Without the change build fails on upstream gcc-10 as:
ld: iface.o:(.bss+0x0): multiple definition of `iface'; main.o:(.bss+0x60): first defined here

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 173161 run on x86_64-linux 1

1 package built:

lcdproc


[Feature-3189][client] Optimize cdcsource and lineage

Purpose of the pull request

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

close #3189


Swift Version CI badge sorting 5.10 last instead of first

Please describe the bug
Swift Version badge's descended sorting is sorting 5.10 last (alphabetically) instead of first (numerically).
Explain the steps needed to reproduce the bug
Navigate to a package that supports at least 5.10 and any other swift version. (Example: https://swiftpackageindex.com/swift-kipple/Core)
What was the expected behaviour?
Versions should sort descending numerically.
Screenshots

Love and Appreciation
Swift Package Index is the best, please keep up the amazing work. ❤

Good catch, thanks for the report and the kind words, @bdrelling !
Fix will be deployed shortly but it'll take a while to take effect due to badge caching.


prototype augmentation in libraries

More of a question than an issue. If I was to make a custom RxJS operator, that lived in a separate library and augments the prototype...what would the definition file for that look like? I've tried various ways of augmenting existing def with no luck.

I have the same question. I'm trying to add a polyfill into Array, and flow throws me an error.
if (!Array.prototype.find) {
    Array.prototype.find = function(predicate) { ... }
}

Error:
inconsistent use of library definitions
  4:     Array.prototype.find = function(predicate) {
                         ^^^^ property `find`. Covariant property `find` incompatible with contravariant use in. See lib: animate/lib/Array.jsfl:4
  4:     Array.prototype.find = function(predicate) {
         ^^^^^^^^^^^^^^^^^^^^ assignment of property `find`. See lib: animate/lib/Array.jsfl:4


Fix when case when node-labeller doesn't have access to kvm

What this PR does / why we need it:
fix when case when node-labeller doesn't have access to kvm device
Which issue(s) this PR fixes:
Fixes https://github.com/kubevirt/kubevirt/issues/5364
Special notes for your reviewer:
Release note:
NONE

Signed-off-by: Karel Šimon<EMAIL_ADDRESS>

/hold cancel

/cc @rmohr @davidvossel

/retest

/release-blocker release-0.40

/lgtm

/lgtm

/hold
I want to make sure there's not a more efficient way of doing this before we merge. If we detect that the node labeller will never be useful for some reason at startup, and that situation has no chance of improving throughout the lifecycle of the virt-handler pid, then we should consider not running the node labeller reconcile loop when that condition is hit.

when kvm is not presented, previous version of labeller just ends and never checks if kvm is available. I am not sure if kvm can be installed during lifecycle of virt-handler?

@davidvossel I created new commit, which disables labeller, when kvm is not available. Now you can choose, which behaviour is better.

/retest

There's a lot going on here, and I'm uncertain why. Is there a reason why this can't be as simple as...
make kvmPath exported as KvmPath in the nodelabeller package
then in cmd/virt-handler/virt-handler.go
deviceController := &devicemanager.DeviceController{}
if device.Controller.NodeHasDevice(nodelabeller.KvmPath)
        nodeLabellerController, err := nodelabeller.NewNodeLabeller(deviceController, app.clusterConfig, app.virtCli, app.HostOverride, app.namespace)
        if err != nil {
                panic(err)
        }

        go nodeLabellerController.Run(10, stop)
} else {
      n.logger.Warningf("node-labeller is disabled, cannot work without KVM device.")
}

Updated

/test pull-kubevirt-e2e-k8s-1.19-sig-network

@davidvossel  If you are ok with this PR, could you please remove the hold?

/hold cancel
removing hold to unblock HCO

@davidvossel If you are ok with this PR, could you please remove the hold?

oops, sorry about that. Yes this is good to go, good judgement call @ksimon1, thanks for removing the hold for me :+1:

/cherrypick release-0.40


Ads have started coming from version 12.0.0 onwards

Question / Problem
Summary
We are using the version 12.0.0 and have observed that ads are coming while playing the videos. Is this change of showing ads introduced from version 12.0.0 onwards? Can downgrading the version help us in blocking the ads? If yes, on which version to downgrade to stop seeing the ads? Also, on what basis does YouTube decide to show ads before the video? Does that depend on if the channel has enabled ads on a particular video or YouTube plays ads even when the channel has not enabled ads on that video?
@PierfrancescoSoffritti @Serkali-sudo Please help on this. Facing this issue on production environment post app release.

Ads showing up is not related to version 12. YouTube decides when to show them.


Feature Request:  Attach instance store on g2.2xlarge instances

g2.xlarge supports 1x 60GB SSD instance store at no extra cost;  while it obviously won't fit most AAA titles and all data written to it will disappear once instances shutdown/terminate, for the casual cloud gamer it's pretty useful.
The following seems to work - I'll try pack this into a PR if I get a chance.

Add instance store to ec2.runInstances()

ec2.runInstances(
    {
        BlockDeviceMappings: [{
            "DeviceName": "/dev/xvdca",
            "VirtualName": "ephemeral0"
        }],
        ...

Run InitizlizeDisks.ps1 on each launch, or InitizlizeDisks.ps1 -Schedule (doco)  while creating a new rig from the base image

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

That's great! Does it appear as a separate drive, and detach/delete when you shut down?
Part of the reason the default instance storage is so low is so that the snapshot speed is quick for saving the state.

Merged into dev

Instance storage != Root device storage
I agree, keeping the boot/root volume small for quick snapshots and lower costs are both good things!
From a users perspective the instance storage volume is more comparable to a "ramdisk" but backed by SSD hardware.  While it's possible to attach multiple 50GB instance stores for extra storage, only one is provided free-of-charge with g2.2xlarge instances.
I've not tried customising what drive letter it appears as;  while the EC2-Launch doco mentions it's possible, InitializeDisks.ps1 seems to always assign it Z:\ after formatting which is good enough for me.  It also creates a text file in the root of the drive explaining that any data stored on it will be lost whenever the instance stops/terminates.  If this script doesn't run or fails, the instance store still appears in Disk Management but will need to be formatted and assigned a drive letter manually.
No need to detach/delete;  AWS won't snapshot instance stores, and specifying them at launch seems to be more reliable than specifying them in an AMI (plus I didn't want to mess with the Lambda scripts :p)
I'm currently using this setup to:

Start cloudRIG using the cli app
Turn on the kettle
Defy Blizzard's EULA and install D3 to Z:\
Make a tea
Play D3

10~20 minutes from start to gaming (when things go well).

Thanks for explaining, and the new feature :) I've merged it into dev.
It's really cool to hear how people use cloudRIG. 10 - 20mins seems like a long time, but I'm not sure how much more can be done to speed it up. Any ideas?


PostgreSQL bug fixes

added a fix for earlier versions of PostgreSQL on Windows in
CMakeLists.txt
fixed a bug in Code/PgSQL/rdkit/rdkit_gist.c which did not cause
issues with PostgreSQL 9.5 on Windows, but does with earlier PostgreSQL
versions
removed an unnecessary conditional compilation clause from
Code/PgSQL/rdkit/rdkit.h as PostgreSQL 8.x is not supported anymore

Hi Greg, sorry for the delay in replying, but I extensively tested multiple PostgreSQL versions on both Linux and Windows, and as a consequence here's a small pull request.
One observation: even though the README claims that PostgreSQL 9.1 is supported, it fails a test on Linux with the following diff:
*** /build/rdkit-Release_2015_09_2/Code/PgSQL/rdkit/expected/reaction.out       2015-11-14 03:47:39.000000000 +0000
--- /build/rdkit-Release_2015_09_2/Code/PgSQL/rdkit/results/reaction.out        2016-03-31 00:42:59.296264070 +0100

*** 1,10 ****
--- 1,17 ----
SET rdkit.ignore_reaction_agents=false;

ERROR:  unrecognized configuration parameter "rdkit.ignore_reaction_agents"
SET rdkit.agent_FP_bit_ratio=0.2;
ERROR:  unrecognized configuration parameter "rdkit.agent_fp_bit_ratio"
SET rdkit.difference_FP_weight_agents=1;
ERROR:  unrecognized configuration parameter "rdkit.difference_fp_weight_agents"
SET rdkit.difference_FP_weight_nonagents=10;
ERROR:  unrecognized configuration parameter "rdkit.difference_fp_weight_nonagents"
SET rdkit.move_unmmapped_reactants_to_agents=true;
ERROR:  unrecognized configuration parameter "rdkit.move_unmmapped_reactants_to_agents"
SET rdkit.threshold_unmapped_reactant_atoms=0.2;
ERROR:  unrecognized configuration parameter "rdkit.threshold_unmapped_reactant_atoms"
SET rdkit.init_reaction=true;

ERROR:  unrecognized configuration parameter "rdkit.init_reaction"
SELECT reaction_from_smiles('c1ccccc1>>c1cccnc1');
reaction_from_smiles

======================================================================
Please note that the same test fails on PostgreSQL 9.1 using the released RDKit version compiled and tested in the traditional way with make && make install && make installcheck, so the failure does not depend on the CMake-based compilation.
A few more tests fail on Windows, again because of unrecongnized configuration parameters. All tests pass on PostgreSQL >= 9.2 on both Linux and Windows.
Shall I modify the docs mentioning support for PostgreSQL >=9.2 rather than >=9.1?
Thanks,
p.

Thanks for doing such an extensive set of tests and catching this.
Off the top of my head, I can't think of any reason why those functions shouldn't work on 9.1 too. I'll investigate.

Ok, I confirmed that. It's now issue #836

I think I have fixed issue #836 now. I fixed the failing test on Windows by adding a PGDLLEXPORT to _PG_init(), while I have added a cartridge function before any parameter is referenced to avoid errors on PostgreSQL 9.1.

Unfortunately the Travis build fails because SourceForge is in disaster recovery mode, so the AvalonTools cannot be downloaded.

Thanks Paolo. I just restarted the travis build

Looks good. Merging.
Thanks for doing the fix!


LightGBMClassifier on OSX

I believe that the mmlspark jar pushed for spark packages (version 0.12) has C libraries inside, and perhaps are just .so files for Linux.
Therefore, when using LightGBMClassifier on spark on OS X, the following error is raised:
18/04/19 12:21:34 WARN TaskSetManager: Lost task 2.0 in stage 4.0 (TID 41, localhost,
executor driver):
java.lang.UnsatisfiedLinkError: Could not load the native libraries
because we encountered the following problems: no _lightgbm in java.library.path and
Could not find resource /com/microsoft/ml/lightgbm/osx/x86_64/lib_lightgbm.dylib in jar

Given that IMO the best idea is that every user builds is own LightGBM with the SWIG wrapper (just to avoid creating multiple jars for every mmlspark version and OS), wouldn't it be a better idea to put LightGBM on Apache Spark on a separate repo and add it to mmlspark as such?
That way LightGBM on Apache Spark could be built with less dependencies on any OS, while still being part of mmlspark for those that need the whole project
Either that or I am doing something wrong somewhere :)

@julioasotodv sorry, we only test running spark on linux right now (windows and OS X are currently not tested).  I added the SWIG Java wrappers to LightGBM, the logic to construct the jar file, and built and uploaded the jar to maven central.  Prior to uploading to maven I should probably build lightGBM on OS X and add the related osx/x86_64/lib_lightgbm.dylib files to the jar.

@julioasotodv Sorry, could you please elaborate more on:
"Perhaps it is better idea to add com.microsoft.ml.lightgbm as a "by hand" requirement before installation, and remove it from mmlspark dependencies?"
Sorry, I'm not sure what you mean by a by-hand requirement?  It needs to be a dependency because the lightGBM classifier and regressor depend on the package.

closing as mac OS support has been added to latest master


16UC1 is treated as signed rather than unsigned

From what I gather 16UC1 stands for 16 bit unsigned single channel integer. Yet looking at the image.py 16UC1 converts to signed. Seems like an error?

Sounds like an error. Want to make a patch?

Fixed in #14


chore(ci): fix the verify manifest error on AWS Linux 2

Just simply skip the libsimdjson.so check.
KAG-5070

Summary

Checklist

[ ] The Pull Request has tests
[ ] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Fix #[issue number]

full matrix:
https://github.com/Kong/kong/actions/runs/10245887174?pr=13450
https://github.com/Kong/kong/actions/runs/10245887212?pr=13450


Check undirected graph creation

flash-graph/tools/el2al -u -v -w flash-graph/data/wiki-Vote-adj flash-graph/data/wiki-Vote-index flash-graph/data/wiki-Vote.txt
test_algs: vertex_compute.cpp:252: virtual void fg::merged_undirected_vertex_compute::run(safs::page_byte_array&): Assertion `pg_v.get_id() == id' failed.
Aborted (core dumped)

FlashGraph assumes that there is at most one edge between two vertices in an undirected graph. When el2al treats a directed graph as an undirected graph, there might be two edges between two vertices. el2al should check if duplicated edges exist when converting an edge list to the FlashGraph format.


CF205 error filling in template for nfs/0

I am deploying cf205 (manifest attached) with bosh-stemcell-3169-openstack-kvm-ubuntu-trusty-go_agent-raw.tgz
Director task 16
Started preparing deployment > Preparing deployment. Done (00:00:02)
Started preparing package compilation > Finding packages to compile. Done (00:00:01)
Error 100: Error filling in template syslog_forwarder.conf.erb' for nfs/0' (line 44: undefined method `strip' for nil:NilClass)
In googling I read that this could be a problem with nfs getting an IP. The problem is that this deployment works with bosh-stemcell-3008-openstack-kvm-ubuntu-trusty-go_agent-raw.tgz. I changed the stemcell to a later version (to get security updates) but using the same manifest.yml to deploy cf. Any suggestions on how to proceed further will be much appreciated!
cf-vmsdev1control.yml.txt

Looks like the error comes from this file.
There may be a few more people on the #general slack channel who have run into this CF issue before.

@sdheepa This seems to be cf-release specific issue. I would recommend filing this against cf-release repo.


DefaultAzureCredential not working with Managed Identity (aka "Service Principal")

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
DefaultAzureCredential cannot login with credentials of managed identity after logging it in.
To Reproduce
COMMANDS:
az login --identity -u "<managed identity attached to machine learning compute cluster>"
dvc pull #needs DefaultAzureCredential class

ERROR MESSAGE:
2021-12-06 17:14:49,273 ERROR: unexpected error - DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
	AzureCliCredential: strptime() argument 1 must be str, not None
To mitigate this issue, please refer to the troubleshooting guidelines here at https://aka.ms/azsdk/python/identity/defaultazurecredential/troubleshoot.
------------------------------------------------------------
Traceback (most recent call last):
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/main.py", line 55, in main
    ret = cmd.do_run()
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/command/base.py", line 45, in do_run
    return self.run()
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/command/data_sync.py", line 30, in run
    stats = self.repo.pull(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/repo/__init__.py", line 50, in wrapper
    return f(repo, *args, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/repo/pull.py", line 29, in pull
    processed_files_count = self.fetch(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/repo/__init__.py", line 50, in wrapper
    return f(repo, *args, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/repo/fetch.py", line 67, in fetch
    d, f = _fetch(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/repo/fetch.py", line 87, in _fetch
    downloaded += repo.cloud.pull(obj_ids, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/data_cloud.py", line 114, in pull
    return transfer(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/transfer.py", line 153, in transfer
    status = compare_status(src, dest, obj_ids, check_deleted=False, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/status.py", line 166, in compare_status
    src_exists, src_missing = status(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/status.py", line 132, in status
    odb.hashes_exist(hashes, name=str(odb.path_info), **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/db/base.py", line 472, in hashes_exist
    remote_size, remote_hashes = self._estimate_remote_size(hashes, name)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/db/base.py", line 274, in _estimate_remote_size
    remote_hashes = set(hashes)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/db/base.py", line 228, in _hashes_with_limit
    for hash_ in self.list_hashes(prefix, progress_callback):
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/db/base.py", line 218, in list_hashes
    for path in self._list_paths(prefix, progress_callback):
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/objects/db/base.py", line 198, in _list_paths
    for file_info in self.fs.walk_files(path_info, prefix=prefix):
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/fs/fsspec_wrapper.py", line 181, in walk_files
    for file in self.find(path_info, **kwargs):
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/dvc/fs/fsspec_wrapper.py", line 276, in find
    files = self.fs.find(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/adlfs/spec.py", line 965, in find
    return sync(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/fsspec/asyn.py", line 71, in sync
    raise return_result
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/fsspec/asyn.py", line 25, in _runner
    result[0] = await coro
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/adlfs/spec.py", line 999, in _find
    infos = await self._details([b async for b in blobs])
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/adlfs/spec.py", line 999, in <listcomp>
    infos = await self._details([b async for b in blobs])
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/async_paging.py", line 154, in __anext__
    return await self.__anext__()
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/async_paging.py", line 157, in __anext__
    self._page = await self._page_iterator.__anext__()
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/async_paging.py", line 99, in __anext__
    self._response = await self._get_next(self.continuation_token)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/storage/blob/aio/_list_blobs_helper.py", line 78, in _get_next_cb
    process_storage_error(error)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/storage/blob/_shared/response_handlers.py", line 89, in process_storage_error
    raise storage_error
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/storage/blob/aio/_list_blobs_helper.py", line 71, in _get_next_cb
    return await self._command(
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/storage/blob/_generated/aio/operations/_container_operations.py", line 1456, in list_blob_flat_segment
    pipeline_response = await self._client._pipeline.run(request, stream=False, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_base_async.py", line 215, in run
    return await first_node.send(pipeline_request)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_base_async.py", line 83, in send
    response = await self.next.send(request)  # type: ignore
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_base_async.py", line 83, in send
    response = await self.next.send(request)  # type: ignore
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_base_async.py", line 83, in send
    response = await self.next.send(request)  # type: ignore
  [Previous line repeated 3 more times]
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_base_async.py", line 81, in send
    await _await_result(self._policy.on_request, request)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/_tools_async.py", line 32, in await_result
    return await result  # type: ignore
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/core/pipeline/policies/_authentication_async.py", line 37, in on_request
    self._token = await self._credential.get_token(*self._scopes)  # type: ignore
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/identity/aio/_credentials/default.py", line 143, in get_token
    return await super().get_token(*scopes, **kwargs)
  File "/azureml-envs/azureml_634aebf1e3b2ee06023cf87c0fb077a8/lib/python3.8/site-packages/azure/identity/aio/_credentials/chained.py", line 84, in get_token
    raise ClientAuthenticationError(message=message)
azure.core.exceptions.ClientAuthenticationError: DefaultAzureCredential failed to retrieve a token from the included credentials.
Attempted credentials:
	AzureCliCredential: strptime() argument 1 must be str, not None
To mitigate this issue, please refer to the troubleshooting guidelines here at https://aka.ms/azsdk/python/identity/defaultazurecredential/troubleshoot.
------------------------------------------------------------
2021-12-06 17:14:49,354 DEBUG: Version info for developers:
DVC version: 2.8.3 (conda)
---------------------------------
Platform: Python 3.8.12 on Linux-5.0.0-1036-azure-x86_64-with-glibc2.17
Supports:
	azure (adlfs = 2021.10.0, knack = 0.6.3, azure-identity = 1.7.1),
	webhdfs (fsspec = 2021.10.1),
	http (aiohttp = 3.8.1, aiohttp-retry = 2.4.6),
	https (aiohttp = 3.8.1, aiohttp-retry = 2.4.6)
Cache types: <https://error.dvc.org/no-dvc-cache>
Caches: local
Remotes: azure
Workspace directory: ext4 on /dev/sdb1
Repo: dvc, git

Expected behavior
Successful authentication
Environment summary
Commands are executed on Azure Machine Learning Compute Cluster.
az version: 2.30.0 (LATEST)
dvc: 2.8.3
Operating System: Ubuntu Bionic (18.04)
Image: "mcr.microsoft.com/azureml/openmpi3.1.2-ubuntu18.04"
Environment:
name: "<envname>"
dependencies:
  - python=3.8.*
  - pandas=1.3.*
  - pyaml=20.4.*
  - ipykernel=6.4.*
  - requests=2.26.*
  - pylint=2.11.*
  - conda-forge::papermill=2.3.*
  - conda-forge::scikit-learn=1.0.*
  - conda-forge::dvc-azure=2.8.*
  - conda-forge::aiohttp=3.8.*
  - conda-forge::cchardet=2.1.*

Additional context

This issue is fixed by https://github.com/Azure/azure-cli/pull/20219 in 2.31.0. Please update to the latest Azure CLI.


Edge glow color in sessions listed from Tracks

Actual Behaviour
Edge colour is not matching the UI colour, it takes it from the accent colour
Expected Behaviour
Use their distinctive session colour
Steps to reproduce it
Change the edge glow colour of views in it.
Screenshots of the issue

Would you like to work on the issue?
Yes
Target Milestone to solve the issue
Milestone 4

Please convert all instances this time @heysadboy

@iamareebjamal There is other issue related to colour in the UI not related edge glow colour should I also create separate issues for that or fix them in this.

Which color in UI to be specific?

Like in sessions from Locations, the title bar is red all the time, it's small but yeah.

OK, change this too

But which color will you set here?
There is no single track color in Location Activity

In some there is only single colour and in some there are multiple colours. Same ambiguity is for edge glow colour. Should it be red or anything else?
If not I think I will be changing the edge glow colour of sessions from tracks only.

In location activity, there can be multiple tracks, and hence the toolbar should remain red.

@heysadboy Any updates?

@iamareebjamal I am working on this, I will do it by today evening.