Refreshing the VS Code product icon

The Icon Journey...Version 2
The 2017 icon change showed how much passion and interest there in the iconography for VS Code, and we thank you for that feedback. There are still a few outstanding issues with current icon, and we’ve been spending time over the past few weeks looking at ways to resolve them. We wanted to share where we are and get your thoughts.
The current icon is hard to see on some customers taskbars as well as in some parts of the Windows UI like the file chooser dialog. The size of the VS Code shape itself, when wrapped within the Visual Studio Family ribbon (the “wall” on the right) makes the difference between Visual Studio and Visual Studio Code hard to spot, especially for some customers with color vision deficiency. Finally, some commented that the macOS version of the product icon looks out of place amongst other apps in the dock.
An opportunity to learn
As well as your feedback, there was also efforts going on inside Visual Studio and Visual Studio for Mac on aligning with iconography across Microsoft, being led by Windows and Office. You’ll have seen some of this in the latest product icons for Visual Studio (Windows) and Visual Studio for Mac as well as some of the recent Office icon updates. While this was not our main driver of change, it made sense to learn from the other work and leverage a similar style to solve some of the issues we were seeing.
The proposed icons

VS Code's current Windows icon (above left) and the proposed icon (above right)
Making it easier to find
We are dropping the thick ribbon on the right side of the icon. This allows us to increase the size of the VS Code shape (the key identifier of difference) to a size where it’s now a lot simpler to glance across the taskbar and spot your favorite code editor.

The proposed icons for the stable and Insiders builds of VS Code as well as Visual Studio 2019
To make the icon more legible on a variety of backgrounds (from the desktop to the file chooser), we have added depth to the icon. This allows us to using lighting and shadows to create an overlapped effect, but also has the added advantage of lifting the icon up and off many flat colors it might encounter.

An example of the proposed icon on some of the blues and greens that you can choose in Windows10.
Improving accessibility
To improve accessibility, we needed a something that is more than color, so taking inspiration from the other Visual Studio Preview builds, we have brought a “stencil” look to the Insiders version VS Code while keeping the familiar green.

VS Code's current Insiders build icon (above left) and the proposed version (above right)
Keeping a native macOS style icon

VS Code's current macOS icon (above left) and the proposed icon (above right)
We’ve kept a macOS style icon for Visual Studio Code on the Mac. We considered having the same icon across all three operating systems but decided to follow the native Mac style. What we also wanted to add to the macOS version was a stronger connection with the Windows icon which would strengthen the recognition between the two versions. Using the same shape, as well as stencil look to the Insiders build, allowed us to do that easily.

Whilst keeping the shape of the background the same for our macOS icons, we were conscious on making sure that VS Code was easy to identify next to Visual Studio for Mac so we’ve adopted a darker look for the shape. This lets you easily spot the difference if you have both installed (and next to each other) in your dock.
Let us know what you think
We would love to hear your feedback on these proposals So let us know what you think!

Love this idea!

I think a color change is enough to differentiate Insider from Retail, does not have to be a different shape as well. Did you guys explore going into the same direction as the Office guys then? I thought everything across Microsoft has to follow the same scheme now?

I think having the Insider icon have those cutouts opposed to the stable build makes it look too much like an X, especially a green X, i. e. Excel.

Really nice icons. Its a good idea.

A green X is Excel - the Excel logo never looked like that, but the Mandela Effect will be a thing. How about Orange for the insiders build?
That said, I like the shape, it's in-line with Visual Studio 2019 just like the current icon is like the VS 2017 one. Just no Green X please.

I like the proposed look for both stable & insiders build specifically the macos one's.
I love the 3d look of the icons.
However in the insider build one the stencil dark band or border can be reduced in thickness, after all only an effect.

I love blue icon of #code and the proposed one with blue, I think is good

Nice ....👍

Love the idea. Both look great but I'm a lil bit biased towards the stencil look. It will make code icon standout from a pile of icons in a glimpse. Time to spot the stencil icon is seemingly less compared to the other new icon.

it's great, good job

I like what you’ve done here overall. That being said, have you considered drawing from the new Microsoft Office, Skype, etc. logos? The brand consistency might be nice.

The macOS icons are fire! I want them shipped in the next build. Tyvm

I like the blue ones for Mac and PC

I like the second proposal. 👌

I've always wondered why the thick ribbon was there, made it look weird, these look a lot better, great idea!

Most likely an oversight, but the Insiders icons in the Proposed and Windows 10 background presentations aren't rounded at the bottom part while they appear rounded in the mockups of the Win 10 taskbar and the macOS dock.

macOS one looks super dope. Maybe thinner border but the proposed one still looks sweet.

I love it

Love the depth of the proposed icon! Just the right level of shadows and rounded corners.
However, I'd prefer the macOS icon without the outline. The shape looks weird to me and doesn't seem to match the typical macOS icon style. I think the "inner" icon would stand beautifully on its own.

Nice! I wouldn't mind having the Windows one on macOS as well — it's so beautiful! 😍

I love the proposed blue icon!

Looking good. I guess. Especially the blue ("stable") one. 😍

Get rid of the cutout on green icon, make it same shape as the blue icon.

I like the new icons, however, o do like the old macOS icon background. If you could find some way to incorporate it, that'd be nice it better fits with the system in that's sense

Growing on me the more I look at them, really like the Mac icons!

Get rid of the cutout on green icon, make it same shape as the blue icon.

@avatsaev The icons shouldn’t only differ in color for accessibility reasons. It’s easier to discern them if the shape is slightly different.

Its nice

Loving them ♥

Loving the new icon, but i would keep the same shape among normal and insider builds

loving the new icon, specially the windows one

The new icon in macOS like no better than the current one, somebody agree?

The new macOS icons look like coffins to me 😢

As a lot of folks already mentioned here and on Twitter, the green one with cutouts reminds Excel. Not a good choice.
@misolori Would love to know why VS Code's infinity is incomplete. To stress that VS Code is not as feature-rich as VS? Or is it a fish and not an infinity?

what about to bing back the orange one for insiders?

The green one looks like Excel, i prefere the blue ones

It's a good idea, like the new ones!! 🤙🏻

These are great looking logos. However, I beg to differ that they should be accepted.
Take any logo design pundit and ask them basic principles. Everyone of them would, among other things, say "A great logo should be distinct and should work equally great in grayscale."
Proposed logos are too similar to Visual Studio. Also, they have somewhat similarity with old Excel's logo.
On a regular workday, it is very much possible to click the wrong icon. And for color-blind, they would look exactly the same throughout.
I am sure that people are working hard, looking at every aspect of impact of this change and would never be hiding behind (very) subtle distinctions sans the color in current versions.
PS: Here is what WCAG2.1 say about the use of Color.

Remember that complaint about VS Code and VS icons looking too similar?
You're walking right back into that issue with the new VS Code and VS icons. It would help if there was a bit more difference between the two than just the tiny left edge being connected in one of them.

As mentioned before, the Insider logo bottom right corner seems very off compared to the rest of the logo. I would suggest to round the corner of the hollow side, to be consistent with other corners but also with Visual Studio 2019 Preview

About the Mac version, and since the icon has a dark background, it would be consistent if a dark color theme is loaded by default.
And, at the same time, I am not supporting having different icons for different platforms

cause you need to have statistics that lots of users use VisualStudio + VSCode on their Mac (as far as I know, most use VSCode only).
will make Mac users see two VSCode icons most of the time (marketplace, official and other websites as well).

I really like the proposal here, it enters in an uniformisation of the brand visual studio, with colours you know which one you are using, even on macOS. Keep going team !

I really dislike this new icon proposal which exists only to align with the release of VS 2019 (which is also ugly). This icon feel the warm up of older draft which have been put away.
What's make the current icon much more better, is the fact that it's monochrome in opposition of your proposal. And if you want to add to redesign the Mac icon, you don't need to rework the windows versions too.
Next point, if you really need to change the icon because of visual deficiency why don't you change completely the icon instead of only the shape of it ?
Having two REAL different icons between VS Code and VS19 will be much more appropriate instead of only make subtle changes that nobody take care about.

I like them. The slight differences in shape are important for accessibility. Differing colour only is not enough.

Hey @rudyhuyn & @rjt-rockx thanks for your eagle-eyed feedback! The issue actually came from my deft resizing of the icons for this GitHub post (you can see the corner is rounded in the VS Mac version) 🙄 I've updated the images in the main issue now. Keep the feedback coming! 👍

The original VS icon is like an infinity sign, or a ribbon.
When the new green icon is evaluated on its own, I am not sure how to interpret it because it loses its 3d form. It does not really have a metaphor. It relies on HSL values that vary by 10% lightness to imply that this object is a truncated or modified version of some other 3d object. Is it a flat object? Is it a fish? You have to be looking at the original icon to understand the reason for the shading.
The place where the ribbons are cut has been rounded off. But the shading does not work because the angles used to cut the ribbons makes the object inexplicably flat. The angles at the cuts do not imply the 3d form of the original object and so it rotates the perspective to make a warped effect.

The original VS icon is like an infinity sign, or a ribbon.
When the new green icon is evaluated on its own, I am not sure how to interpret it because it loses its 3d form. It does not really have a metaphor. It relies on HSL values that vary by 10% lightness to imply that this object is a truncated or modified version of some other 3d object. Is it a flat object? Is it a fish? You have to be looking at the original different icon to understand the reason behind the shading.
The place where the ribbons are cut has been rounded off. But the shading does not work because the angles used to cut the ribbons makes the object inexplicably flat. The angles at the cuts do not imply the 3d form of the original object and so it rotates the perspective to make a warped effect.

Can someone explain the idea behind this software being “Visual Studio Code”? They’re not really similar under he hood, right? And their target purpose isn’t necessarily the same, especially since Visual Studio is now available for Mac. That being the case, why play homage to the Visual Studio logo at all? Why even play homage to the name? Why not an entirely new direction with the logo, or even going as far as changing the name to “Microsoft Code”?

@gwardwell this is probably going to go tangent to the issue, but I think you are right. The "visual" aspect was in visual studio where devs could drop and drag and create stuff. vscode is more of an editor than that, so yes dropping the word "visual" makes sense 😄

Stellar work 👏

I once suggested to drop "studio" and rename it to "Visual Code" which was rejected- #3611

Hey @Stanzilla & @gwardwell thanks for the feedback on the alignment with other Microsoft products like Office 😃 We have actually been working with both Office and Windows on aligning across Microsoft on an icon style. Given the breadth of different products that need work together we have more guiding principles rather than trying to match each other exactly. The depth (and the subsequent lighting and shadows) we've introduced with this icon refresh is a step towards this alignment. I've updated the taskbar image with some new Office icons so you can see this more clearly.

I like the asymmetry of the Mac icons 👍

Overall, I get what you're going for, and I think, in terms of consistency with Visual Studio, you're on the right track.
However, I agree with other comments here about the Preview icon style/color.
I think it's too much to have both a different style and color. If you want to denote the difference between the regular version and the insiders version, you should use either a different color or a different style.
While I personally like having a green icon for insiders, I would also be ok with the stenciled look which is blue. This is in keeping with the Visual Studio Preview vs. Release icons. But whatever you do, you should probably choose either color or style to differentiate the "flavors", but not both.

The colors are nice and they pop out well, but I'm not a fan of these rounded edges MS trying to sneak in with the office icons and some parts of the settings app/start menu recently. I like the more angular style of Win10.
Leave the rounded edges to Apple.

I really like the blue one.  A lot.  It kind of looks like a space ship, and as we all know, working with VSCode is... out of this world.

This is still really bad for the color blind. They have to identify tiny difference in a tiny icon.

Can somebody explain why am I getting downvoted? This thread is supposed to be about discussion and feedback. Negative feedback is feedback too. Or the Apple comment is what made you think I'm just "trolling"?
Let me explain: I used Apple here as an example. They have a working ecosystem, and a consistent design language all across their products. Rounded corners are common and It looks good. (Another good example would be Bootstrap, or Primer)
But let's open VS Code. Or any other modern MS application, and what do we see?
Sharp corners everywhere.
Is that a problem? Hell no. It's another design direction and it's really good too. But please stay consistent. (The only rounded corners I could find in VS Code is the new search widget in the explorer sidebar.)
The icon should reflect the application. The previous icon did that. This one is not.
And this is true for the new office icons too, but that's another topic.

Nice one

Really good idea!

Please consider changing the icon so it looks different than Visual Studio 2019.  It makes it very difficult to tell them apart, specially if you are color blind.

I really like it

I imagined it like this:

@AlexAegis The angles you used at the cuts imply the meaning of the object, good work

@AlexAgeis Could you please make a version of that with the alpha edge stroke?

@AlexAegis Could you please make a version of that with the alpha edge stroke?

Same icon every single OS, why make them different, why

I like the new icon for Windoes, but I definitely don't like the new one for MacOS.

The current macOS seems to have native Mac style. But the proposed one...

I wonder if some added textural elements might help to further distinguish the “Insiders” icon. For example, the Firefox Developer Edition icon adds a polygonal pattern to the globe. A textural treatment such as this for the Insiders icon might accentuate the “stencil” motif as well.

Here's a quick hack with changed angles and inverted.

The shape is important as much as the color to differentiate with visual studio
Really I like the new shape
.

I really like the new concept

New proposed design looks pretty awesome.
However, for me, icon for macOS, especially that big background don't fit very well.

Nice，very good-looking (except mac icon)

Can Linux users get the regular icon instead of the Mac OS one, please?

right

Not a fan of the macos icons at all

Hi @fourpastmidnight When we looked at the Insiders and Stable build icons together we knew we needed to use more than just colour to differentiate between them. This is so that the icons are more accessible for customers with color vision deficiency. We started with just the stencil approach but then added the green back from the current Insiders icon for familiarity. The combination of the colour and the stencil has created a bit of feedback around the similarity to the old Excel icon though 😉

Hey @AlexAegis I wanted to address some of the valuable feedback you've been adding to this thread, you're correct in saying this is a open forum for discussion and feedback, both negative and positive.
I think your point around how a product icon should reflect the ui of the product (or even the OS) is interesting but maybe limiting? Where I agree that Apple 'owned' the rounded corner for a long time, I'm not sure that's the case anymore (and I'm not sure that's how they'd like to be remembered either 😉) Similarly for Windows, I see many examples of less than sharp corners across all of our major products and I think that's okay too.
We try to design our products with the most appropriate ui for the task you're trying to complete as well as follow the platform we're designing for. How you round the edge in a ui can have a huge impact to the cohesive look of an application (or even OS) but we shouldn't limit ourselves, as that could limit what we deliver to you 😃

Looks cool! Can't wait to see it in my dock.
Reminded Taxi in Detroit game a bit

@jamiedawsonyoung Ah, I see. Well, it was just a thought that color and style might be too much. Either way, I do like the new logo design for Windows.
However, I also find the mock-up designs by @AlexAegis and @Yzrsah very nice, too. I actually like them better than the current flat design. Nice work.

Really love the logos! Would love the Mac one to match the Windows one though. Not a fan of the border.

Can't we just make the style consistent across every platform? Purple for Visual Studio, blue for Visual Studio Code and green for Insiders if fine, but please don't use a different icon style in macOS!
I would love to see something like this (as @mariusschulz already proposed)

Take a look at the Visual Studio 2019 icon in my dock: It looks very unnatural there...

@robinmanuelthiel So you say Sketch icon looks natural for example? Still it's nice and I love to have it in the dock :)

Great icons.  I like the colour and the differentiation (colour and style) between regular and insiders.  However I agree with the feedback that the icon should be consistent across platforms, which seems the route that other MS products (namely Office) are taking.  I would prefer to see the "Windows-style" icon used everywhere; no macOS-specific icon.

Great icons. I like the colour and the differentiation (colour and style) between regular and insiders. However I agree with the feedback that the icon should be consistent across platforms, which seems the route that other MS products (namely Office) are taking. I would prefer to see the "Windows-style" icon used everywhere; no macOS-specific icon. It's unfortunate that Visual Studio 2019 did not already go this route.

I think having the Insider icon have those cutouts opposed to the stable build makes it look too much like an X, especially a green X, i. e. Excel.

I think so too!!!
looks like Excel Icon...

Amazing.

Nice. When is this shipped?

I think having the Insider icon have those cutouts opposed to the stable build makes it look too much like an X, especially a green X, i. e. Excel.

But it follows the Visual Studio style, so it's correct.
I prefer seeing an X than having two software of the same family (Visual Studio) with different icon styles.

Really love the icons.

awesome

Can Linux get the same icon as Windows, please?

awesome!!
but ,I like more short width edge line.
Of course I think it is a very nice design.

Love the new icons overall! Just a small detail on the edges of the insider icon that is bothering me a little. Maybe it would be better to have them rounded instead of (crooked)?

Great work! Really love the new logos and can't wait for them to be released! As many people have said above, I would also love for the Mac icon to match the Windows icon. Not a fan of the border!

Love the proposals!

I think a round icon for Mac os will look better, like the Safari icon since it looks more standardised.

I'm not so sure that the whole Excel X thing would be much of a problem considering that the vast majority of VS Code insider users are highly computer literate? Then again I don't have much experience.
But these new icons overall are just 🔥🔥🔥

I really like these icons :) This is not merged in April iteration?

https://daedtech.com/bike-sheds-ducks-and-nuclear-reactors/

The new design looks nice, but it has me confused about something:
I always assumed that the icon was supposed to represent "infinity".  At least, the Visual Studio ("Not Code") icon is clearly an infinity, and the VSCode icon appears to be based on the same idea.  Although the leftmost fold of the infinity is hidden in the VSCode icon, I mentally pictured this as being "still there, just the same colour as the background", like it is camouflaged by reflecting light or something.
  Because of the rounded edges on the left side of the two crossing lines, it is much harder to imagine that fourth hidden side.  The rounding ends say "this line stops here", it doesn't make sense to imagine them as "folded over" anymore
So I have to ask -- was it it ever supposed to represent infinity?  I don't find any mention of infinity in this page at all.  The 2017 redesign page says that "We iterated on the infinity logo for some time...until we landed on the current fish".  So is it a fish, or infinity?

Looks good

Can't we just make the style consistent across every platform? Purple for Visual Studio, blue for Visual Studio Code and green for Insiders if fine, but please don't use a different icon style in macOS!
I would love to see something like this (as @mariusschulz already proposed)

You are writing, that you thought about using the same icons but decided against it to follow the native Mac style:

We’ve kept a macOS style icon for Visual Studio Code on the Mac. We considered having the same icon across all three operating systems but decided to follow the native Mac style.

I would argue, that the newly proposed Mac icon does not follow the native Mac style. It looks very unnatural in comparison to most other apps. The new Windows icon you proposed also fits perfectly to the Mac style. Without any macOS specific modifications
Take a look at the Visual Studio 2019 icon in my dock: It looks very unnatural there...

Agree, it is also can be shaped inside a circle like the App Store icon.

Do not like the outline on the Mac version. It looks way out of place and garish. The Windows version is fine, and should be the same version used across all 3 platforms.

Mac Os icon looks the best, color and shape.

quite disappointing this didn't go into april update
https://user-images.githubusercontent.com/6909617/55654227-b871b680-57e8-11e9-8728-62be20609813.png

My first reaction was, "here we go again". But instead, I really like the new icons! 👍

I really love the blue icon, but i'd prefer the insider icon shape to be the same as the stable, i feel it ugly with that space.

Responding to your feedback
Whilst a lot of you like the proposals for the new VS Code icon (thanks!), we did see some signals amongst the comments and tweets that we wanted to address, namely that the green Insiders icon looked like an old Excel icon, and that there were requests to have the same icon across Windows, Mac, and Linux.
Addressing the Excel feedback
The cutouts of the Insider build icon are there to allow you to easily distinguish between the Stable and Insiders builds if you have color vision deficiency. However, the strength of the vertical cuts we’ve made in the icon accentuates the “X” that is formed by the rest of the icon. To reduce this effect but hold onto our accessibility, we’ve reduced this space by 1px at its smallest size.
The green of the Insiders build icon is also a very similar hue to the Office Excel green, so we’ve shifted the hue away to make sure the combination of the green and the X don’t send the wrong signals when you’re looking for VS Code in your taskbar/dock.

An example of the new thinner cuts to the Insiders build as well as a hue that isn't similar to Excel's green
One icon for all platforms
In our initial proposition, we spoke about aligning with other macOS products in the Visual Studio family such as Visual Studio for Mac. While the need for a separate icon for Visual Studio for Mac is clear given the difference in the two products (Visual Studio and Visual Studio for Mac). Visual Studio Code is the same product across all the platforms so the need for this is less clear.

The new VS Code Stable and Insiders builds in the Windows 10 taskbar

The new VS Code Stable and Insiders builds in the macOS dock

The new VS Code Stable and Insiders builds in the Ubuntu 18.04 dock
Given this, we’ve decided to use the same product icons for VS Code across all the platforms.
Rollout Plan
We plan to update the icons next week. Insiders will be immediately available, and Stable will be available in early June. Thanks again for all the feedback, we really hope you like the new icons.

The new insiders icon looks much better IMO, the new hue of green is a huge improvement over the former and is very nice indeed. I think you've really nailed it this time. Also great to hear that the VSCode icons will be made identical across platforms!
I also think the Visual Studio for Mac icon fits the application beautifully, in terms of it being 'more complete', I think the icon conveys this nicely with its 'fuller' representation. Good work 👍🏼

Both new icons are absolutely gorgeous! Thank you for reaching out to the community, asking for feedback, and taking it into consideration. It really is much appreciated. 🙂

Are the cutouts of the Visual Studio Preview icon also being updated? Otherwise, this would be inconsistent.

@Studio384 the Visual Studio Preview icons will also be updated

I LOVE THEM SO MUCH. So much that all caps was required.

I really like the change. I haven't had the Excel mix-up issue, but I think the new icon is an improvement.

Great. Never thought I'd love change this much,

I like this change a lot as well.  Looksreally good!

I really like new Insiders version with reduced gap, however would prefer darker color.
Would be great to have two colors of Insiders icon bundled into .exe file.
Never had problem to distinguish Excel and VS Code and darker color looks better for me.

Will this be included in the next update?

It's a nice change... and it makes all the difference. Great work.

@vinayakkulkarni yes, the next stable version will have the updated icon and insiders will get it sooner (either tomorrow or Monday).

I like the new style but maybe we have to talk about the green of the insiders icon

@misolori I'm on an Exploration build, because of color compatibility issues that are resolved in Electron 4.x. Since the Exploration builds are orange, will you be producing an orange-tinted version of these for those builds?

@jdsimcoe yes, we will be updating our exploration build icon as well.

@misolori You guys rock. Love the new direction. Send my best to the whole design team.

IMO proposed form is better than the current one, but color should not be blue. A color different from Visual Studio's icon color would be much better.

I know this is a long shot but in terms of accessibility wouldn't be recommended to add a little bit more of distinction between insiders and stable? I am thinking about the colour blind people.

This looks good. Blue one

@Nepomuceno for improving accessibility we did add the "cut outs" and changed the hue so it's more noticeable for users who are color blind. Here's what that looks like in Deuteranopia:

Hello there,
Just wanted to throw this in there for consideration. The top and bottom corners seemed a bit inconsistent with the implied edge.

Just wanted to say that this icon is a major improvement over the icon we have now.
The simple shape carries it and reads well outside the Microsoft ecosystem.
Icon styling
I think this icon feels a lot more at home, and on macOS particularly, though that does bring up other questions in my mind.
The app itself has very rectangular flat design with no rounded edges or shadows (excepting the command palette and dropdown menus), yet the icon is moving towards a more rounded-rectangle / Apple look with subtle 3d shading / depth cues.
If this is a signal that the design language of the app is now allowed to soften, I'm all for it. I think vscode in a way is much bigger than just being a reflection on Microsoft, but is the future of how many people will experience code & work in general.
I think the best "flat design" is actually a compromise between completely flat color and the fully-rendered design from the Steve Jobs era.
Insiders icon
The cuts seem strangely 2d to me in the context of an icon that has 3d styling. I sketched a version where it was a darker band painted on the ribbon, but it didn't look great either. I understand it's about accessibility, I just hope over time a more aesthetic compromise can be found.  @andrewmundy I'm a little confused that your "before" doesn't match the mocks above.
Shading on corners
I think additional subtle lighting cues at the top and bottom of the ribbon's fold radius would help sell the 3d curve of the new icon. Maybe a dash of bounce lighting in the fold where the two sides are close together? A subtle bevel on the edges? There is a slight physical impossibility implied with the ends and perspective as well, not sure if intentional.
This is all just about subtle refinements, the design you have is good.

There is a meta-point here about design critique in the open. I appreciate you @misolori braving the comments sections and listening… there are a lot of sometimes conflicting perspectives but the design seems to be getting better as a result. (also continued conversation on twitter)
p.s. VSCode is the only Microsoft product I use but it's been amazing and really changed my opinion about y'all

Where can I get an icls file to have a bite on this new cake? 😋

I really need the ico format of this new logo so I can change my local visual studio code program and enjoy it.

Love the proposed icon, it's way more modern and fresh than the current one (still like it though)!

For exploratory builds perhaps the icon can stay the same but instead of fill use the zig-zag pattern like in https://github.com/microsoft/vscode/issues/71827#issuecomment-495306980  (as in, instead of solid shape, the shape is filled with zig-zag lines as it's a "sketch").
Really like the new icons 👍

I like the first design for macOS icon ( Keeping a native macOS style icon ) in the latest release of VS Code insiders you made the icon like the icon for windows, please change it to the first design you choose for the macOS.
I mean this icon:

I love the “one icon” you landed on. I was never a fan on the border and background on the original Mac icon you proposed, and I’m really happy you chose to abandon that version for an icon that matches across all platforms.

All good, but a very little more hue to both main and insiders are welcome

IMO the icons are a bit too large. This is how it looks in my dock; it seems weird compared with the above and below icons. I also agree a bit more hue would look nicer.

@albireox I think the color is great, but the size gets too close to the edge of the macOS dock.

@albireox we’ve already got a fix for that, should be updated in the next insiders release.

I like the VS icon, but please don't bring back the inset shadows of Windows 8.

I really appreciate the design thinking that went into this new icon, and I know some people will just never get behind a new thing no matter how good it is. That said, here's a few critiques:
The inconsistent use of inset shadows is discordant:

I find the rounded corners to have a more childish feel, the sharp corners of the previous icon felt more crisp and professional.

Just throwing in my opinion - as @macgyver said, some people will always like the 'old', and I might be one of them.
I just find the icon a little too big (which I know is being fixed), but I'm constantly mixing it up with Excel now to the point of frustration. Perhaps it's muscle (eye?) memory but boy-oh-boy I'd rather a setting somewhere to keep the old one.
Is this a possibility?

After weekend with new Insiders icon there are two observations:

On W10 with dark OS theme gaps on insiders icon don't feel like intentional gaps to denote deconstructed logo but more like hard shadows on pseudo-3D shape.
May be bigger gaps will look more in place.

Would be great to check how icon would look like in old hue. Current one looks really pale, desaturated, and doesn't feel like VS Code icon (insiders/stable) or other MS products.

Earlier I commented that that reduced gaps looks better, however checking on actual task bar on SP3 - doesn't look that good.
My concern regarding hue of Insiders icon was confirmed and I'd prefer at least to check how new shape with old hue would look like.

like an ugly fish, hmm... but i love it.

The new icons looks great. However, on macOS something about the insider icon just makes it look... blurry? (for the lack of a better word) on the dock especially with lighter backgrounds.

I think it's missing some contrasting outlines and drop shadow

It's great that the icon doesn't look oversized anymore!

As much as I mentioned that I love the new icon colour earlier in this thread, I have to admit that it doesn't look as great when it is on a semi-transparent background, whether light or dark.
I think it looks great on solid light or dark backgrounds, but defo needs some adjusting for better definition on transparent backgrounds.

The new icons looks great. However, on macOS something about the insider icon just makes it look... blurry? (for the lack of a better word) on the dock especially with lighter backgrounds.

I think it's missing some contrasting outlines and drop shadow

Agreeing with @weijiangan and @dalDevelo, the new icons for Insiders just don't look good against a light background (in this case, the default MacOS Mohave background:

I think that the insider icon lack contrast (at least on MacOS), as far as I can tell there is not a shadow that can make the icon "pop" as other icons especially in the application switcher (cmd+tab), it is also noticeable in the drawer as pointed by @weijiangan
For me personally I can't find the icon visually when put side by side other app icons when is over a white background. I am talking about speed in recognizing the icon.

Thanks everyone for the feedback so far, we'll work on addressing the contrast issues for the Mac and Linux icons.

@misolori there are contrast problems on W10 (especially when VS Code icon is active) too.

@IllusionMH can you post a screenshot?

does't look very contrast when window is active and task bar icon is highlighted.
Not as bad as transparent Mac OS, but worse than before.

This shade of green seems to be a mistake in general. I preferred the original green version.

This looks great! But I prefer the original green as it seemed more saturated :D

If the logo had a white circle (or maybe hexagon) background, accessibility problem could be solved once and for all.

The blue version looks like better and comfortable :)
Of course, if the current version could be reserved for alternative icons, it would be better more 👍

I like this one more.
👇

The other one doesn't look great.

To be honest. Yesterday I made some updates on my system and got a shock when I saw the new icon. I first didnt know what application that was (I am using elementaryOS 5 with a custom icon set that is basicly the macOS icons in nicer).
I LOVE the new icon I got with the update (VSCode overwrote the cron of my icon set).
I did some google searches but didnt find a high quality version of the green icon in blue.
Does someone have that? (PNG, Transparent, 1024x1024)
I also extracted the blue logo from the latest windows stable build to replace the out of place macOS like icon. (Extracted the exe, copied the icon and selected it in the .desktop file)

As you see in the image above, I would like to have the same new icon in blue as it would make it fit.

Please make this change happen, the new logo is SO COOL. (And keep that seperaction between the front and back of the icon like it is now, it makes it 40% better)

If I can, I want to use a round icon on my Mac, for example:

Uhh.. did they revert the icons in a recent insiders build? I launched Code this morning, and the icon switched back to the original:

code-insiders --version
1.35.0-insider
6964233e81c68f5a5f34e7eb1da0836e1d539f14
x64

What do you think about keeping the tilted style on macOS together with the new icon?

You sometimes may encounter icon cache issue with the old one showing up on the Mac, @jtsom's link is a good alternate to clear the cache. You can also right-click on the application (in finder) > Get Info > and drag the preview image into the icon in the top left.
@AtjonTV the stable version will be updated in the next release (hopefully next week).
@fwcd we originally proposed a mac styled icon but after seeing the feedback we decided to use one icon across all platforms (see this update for more info).

@misolori Did you consider something like @wyfang's proposal? It looks great IMO and it also follows the macOS icon guidelines.

@nblagoev yes we did, that was one of our original concepts but felt the circle did not occupy the space efficiently with our logo. That's what lead us to the original proposed mac icon. In the end, after much discussions internally and from feedback from the community we decided to use a single icon on all platforms.

@nblagoev not all people like when all icons in the system have same shape, as they are difficult to read when they look same.
This one is sleek, modern and distinctive.

Not sure what happened, but someone just had this happen when their Insiders updated:

That's not a very helpful icon!

Not sure what happened, but someone just had this happen when their Insiders updated:

That's not a very helpful icon!

I didn't like the new outlook, so I went to find the old one, (the edgy one), had dropped it off in the vscode fodler, the new updated wiped it out of existence too... now I have to go find it again..

Why doesn't macOS use the same icon as Windows? I think the borders are too ugly!!!

@longforus please see our updated response, we will be using one icon on all platforms.

Not sure what happened, but someone just had this happen when their Insiders updated:

That's not a very helpful icon!

I didn't like the new outlook, so I went to find the old one, (the edgy one), had dropped it off in the vscode fodler, the new updated wiped it out of existence too... now I have to go find it again..

reboot the in safe mode

@jtsom @simdimdim sorry, this appears to be a weird bug on Mojave (https://github.com/microsoft/vscode/issues/63068). Restarting the dock in terminal via killall Dock seems to fix it.

@jtsom @simdimdim sorry, this appears to be a weird bug on Mojave (#63068). Restarting the dock in terminal via killall Dock seems to fix it.

I had to reboot in safe mode.

@longforus please see our updated response, we will be using one icon on all platforms.

@misolori  oh, I didn't notice it,  one on all is very good. 👍

Clearing Icon Cache for Stable icons
Depending on your platform, you may still see the earlier logo due to operating system caching of the application icon. Here are a few methods for the Mac that you can attempt to use to clear the cache:

Restart your dock via killall Dock in the terminal

Run these scripts in your terminal (which updates the timestamp of the icons):

sudo touch /Applications/Visual\ Studio\ Code.app;
sudo touch /Applications/Visual\ Studio\ Code.app/Contents/Info.plist;
sudo touch /Applications/Visual\ Studio\ Code.app/Contents/Resources/Code.icns;
killall Dock Finder

Note: For Insiders and Explorations, simply append \ -\ Insiders or \ -\ Exploration to each version name reference.

Force the IconService cache to be rebuilt using these steps

🚀  We're shipping our Stable icons in the next release (later this week) and Insiders/Exploration builds are already using the icons. Closing this issue, 👏 thanks again to everyone who provided input!

@misolori so there will be no changes to Insiders icon (on Windows)?
Could you please provide provide .ico file for new Insiders icon shape with old hue?
Change in hue just to distinguish Stable and Insiders looks overkill for me (I doubt that both stable and insiders are often used simultaneously + used by people who really need different hue) and I'd be glad to set up icon with old hue manually if you really think that this colors are must have.

@IllusionMH we'll be shipping what's in Insiders today, please see our comment about why we changed the hue (in case you missed it). One of the original goals of this re-design was to address the accessibility issues we had with the Insiders icon (we can't use color alone to distinguish meaning). Here's an example of how that was improved.

@misolori I've followed this thread and know reasons, but I hoped that feedback after live Insiders icon release will be addressed too.
Anyway, I'm asking if you could share files with old hue, so users who would prefer old color with new shape will be able to set it only for themselves.
I don't have proper tools or skills, but I guess that this won't be hard for you with existing sources.

Could the proposed macOS icon be uploaded somewhere, I would much prefer that over the cross-platform design

Are these logos on Linux Mint as well?
I still see the old one.

The difference between VSC and VS still seems minimal.. what about picking something completely different?
https://user-images.githubusercontent.com/6909617/55719383-08719880-59f6-11e9-9a2a-537441767e4b.png

Hi @angelov-a!
I'm using Ubuntu and had the same problem (seeing the old icon after update), executing following command:
sudo update-icon-caches /usr/share/icons/*

and restarting the session after that (maybe just logout/login would also work) fixed my problem.

Oof, I didn't see this until I updated my app to find a new icon on my Dock. I urge you to reconsider removing the old document-style tilt treatment. It's fine without the swoosh on the right side, but losing the tilt and document rectangle is a step backwards. It reminds me of this line from a recent post by the IconFactory, who have been designing super-high-quality icons for the Mac and others for decades:

[...] a Mac desktop icon, which should be similar to, but not the same as, your iOS icon. Utility applications typically get a round icon, while document-based applications get a perspective treatment.

The icon shouldn't be the same across platforms, it should be similar and recognizable but tailored to the platform. And as a "document-based application", VSCode should keep the "perspective" tilt. When I started using VSCode, that was one of the little touches that made me like the app! The new icon feels much less native.

Hi @misolori!
i think adding my solution is helpful for Linux users (maybe only Ubuntu-ers!).
thank you

@xeptore,
Thanks for the reply.
Unfortunately it doesn't work on Mint.

The issue, for me at least, on the Mac, with the Insiders icon isn't so much the shape, as it is the color/contrast. On the default Mojave desktop picture, the icon all but disappears:

The issue, for me at least, on the Mac, with the Insiders icon isn't so much the shape, as it is the color/contrast. On the default Mojave desktop picture, the icon all but disappears:

Windows 9x Background? 😄

Hahaha... no silly...

Hahaha, I was joking.
I think this problem will occur with almost any icon. It will depend the user os theme configuration. In your case when using the stable version with the blue icon, I think will be worse.
To avoid this kind of problem, all my backgrounds nowadays are black at the bottom. I had problem in the past with Spotify, Sublime (with gray background) and a bunch of other apps.

Can someone please explain to me why the stencil feature is applied to every part of the insiders icon except this one part? like, what is going on here, how is my brain supposed to parse this shape

That's a good question. I didn't see it at first either. I think it looks more parsable on a dark background that the cutout seems to be imply a edge facing the viewer.

@macgyver @fivetwelve the insiders icon is intended to match the preview icon for Visual Studio (Windows), where it's in a 3d space:

I have the same issue as @jtsom . Most icons on macOS are "fuller". The new VS Code icon has too much transparent areas and it kind of gets lost... See my dock as an example (and this is irrespective of the background image)

I see my dock icon got updated but not in my launchpad where it still shoed the old one 😬

I'm using Manjaro Deepin, how am I supposed to clear my cache icon?

Is there a way to switch back to the old logo on Mac? I love vscode but I get used to the old logo

the new icon seems a bit too large on Windows.

@HaoyangFan96
you can write a quick script to replace /Applications/Visual\ Studio\ Code.app/Contents/Resources/Code.icns or copy paste the icon in info view (⌘ + i) in the top left corner. Note that updates will reset this.

@impulse
Thanks!

If I use "small taskbar buttons" and pinned the app, the icon changes back to old one.

Previous one looked much better.

beauty

Beautiful! Where can I buy stickers! :)

@infinnie
Well, for me the size is ideal. It's probably an optical effect to you when looking side by side with vs2017. vs2019 has same design. And then, it's system icons that are very small. Especially Start Menu icon. Had to change it to a bit larger.

@regs01 the Start Menu icon used to be a lot larger and didn’t look good.

@macgyver @fivetwelve the insiders icon is intended to match the preview icon for Visual Studio (Windows), where it's in a 3d space:

oh interesting.. it makes sense visually on the Studio icon, but the VS Code one still doesn't mentally make a complete shape for me. Maybe because of the way the corners round off on the ends of the ribbon? the round edges make sense when the idea is that it represents a flat ribbon or tape that is wrapped around a circlular edge, but not as much sense as the ends of a flat ribbon with round corners.. I guess it's just weird to me that someone would carefully cut round corners onto this ribbon, but oh well!

@angelov-a, what about this?
sudo gtk-update-icon-cache --force /usr/share/icons/*

hope helps :)

@mbehboodian,
I've tried this as well to no avail.
On Thu, Jun 6, 2019 at 4:57 PM mbehboodian<EMAIL_ADDRESS>wrote:

@angelov-a https://github.com/angelov-a, what about this?
sudo gtk-update-icon-cache --force /usr/share/icons/*
hope helps :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/71827?email_source=notifications&email_token=AH5ED7FUSVYJ3NQ3YBXA7G3PZEJWFA5CNFSM4HD7G7SKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXC5E7A#issuecomment-499503740,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH5ED7HWE3HMRFWURKF3253PZEJWFANCNFSM4HD7G7SA
.

--
Alex

I have the same issue as @jtsom . Most icons on macOS are "fuller". The new VS Code icon has too much transparent areas and it kind of gets lost... See my dock as an example (and this is irrespective of the background image)

Agreed, but I thought the new icon was supposed to have a more "osx style" as stated by OP in the "Keeping a native macOS style icon" section.

This is lovely work!  Even nicer than the original imo, which I greatly missed when it was replaced a few years ago:

@RandomPiche please see our updated response where we took the feedback from the community and used the same icon across all platforms.

Slick new icon.

Icon for Mac is not good...

Nice job !!! Could someone please tell me where to download the icon for Windows in high resolution?

Ico file in the commit https://github.com/rogeraabbccdd/vscode/commit/f2e4f31667dbe2e43256e9e2a23a159caf7876ef seems to have only one resolution: 64x64. I wonder it that might be an issue. I'm not sure these are the actual files vscode is shipped with now. The previous icon I have - had multiple resolutions inside.
Why I found that:
I wanted to make an orange icon for myself. Single color blue was just bad, but now I just want to keep seeing the orange icon in my taskbar.
So I applied the hue from the old icon to the new one:

Ico file in the commit rogeraabbccdd@f2e4f31 seems to have only one resolution: 64x64. I wonder it that might be an issue. I'm not sure these are the actual files vscode is shipped with now. The previous icon I have - had multiple resolutions inside.
Why I found that:
I wanted to make an orange icon for myself. Single color blue was just bad, but now I just want to keep seeing the orange icon in my taskbar.
So I applied the hue from the old icon to the new one:

Thanks anyway for your answer :-)

Lol. @B777-300, it's a pure coincidence my comment looks like an answer to yours.
The linked commit contains svg file(s). So it should be possible to make any resolution images for an icon, if needed.

Clearing Icon Cache for Stable icons
Depending on your platform, you may still see the earlier logo due to operating system caching of the application icon. Here are a few methods for the Mac that you can attempt to use to clear the cache:

Restart your dock via killall Dock in the terminal
Run these scripts in your terminal (which updates the timestamp of the icons):

sudo touch /Applications/Visual\ Studio\ Code.app;
sudo touch /Applications/Visual\ Studio\ Code.app/Contents/Info.plist;
sudo touch /Applications/Visual\ Studio\ Code.app/Contents/Resources/Code.icns;
killall Dock Finder

Note: For Insiders and Explorations, simply append \ -\ Insiders or \ -\ Exploration to each version name reference.

Force the IconService cache to be rebuilt using these steps

Unsure if this works for Mojave, but I have Sierra and the only steps needed (no command/scripts, etc):

right click on the Icon in Dock -> Options ->Show in Finder

Done

Hth...

Is there a way to switch back to the old logo on Mac? I love vscode but I get used to the old logo

Yep. https://github.com/ashrafhadden/vscode-icons

Unsure if this works for Mojave, but I have Sierra and the only steps needed (no command/scripts, etc):

right click on the Icon in Dock -> Options ->Show in Finder

Done

Yes works for Mojave as well. I just dragged it out of my doc and then added it back in and that updated it.

I hope the Windows icon can be released as a file, so I can replace the Mac version with the Windows version.. I like the Windows version.

@Leedehai not sure if you missed the updated response, but we're using the same icon across all platforms.

I hope Visual Studio for Mac icon also get a new icon to match Visual Studio Code, so it is truly the same icon across all platforms. Any plan on this?

@tsunheang at this moment Visual Studio and Visual Studio for Mac different...

While the need for a separate icon for Visual Studio for Mac is clear given the difference in the two products (Visual Studio and Visual Studio for Mac). Visual Studio Code is the same product across all the platforms so the need for this is less clear. -- full comment

@xeptore, I've tried this as well to no avail.

I had success just doing (might just be a catch of having "Keep in dock" on):

close vscode
uncheck "Keep in dock"

open vscode
check "Keep in dock"

With a darker background the contrast is acceptable, with a lighter one it's not so visible.

That malplaced black crooked square you used on the icon in ubuntu was a real eyesore. I'm glad you came to your senses and fixed the icon!

I had an issue after installing the latest update that only my Start Menu tile wasn't updating on Windows with the new icon. Similar to the recommended fix for macOS, I employed a similar technique to "touch" the lnk file in PowerShell.
(Get-Item "$env:APPDATA\Microsoft\Windows\Start Menu\Programs\Visual Studio Code\Visual Studio Code.lnk").LastWriteTime = Get-Date

Love the new icon!

Goodjob, new icons are so cool! I have a problem, background of startup icon of vs code in win 10 is always dark  just like vs' one. How can I set personal background for app without source code?

Yeah, I am also currently seeing the global logo on Mac:

Don't get me wrong, I like it. Just not sure if that is the intended appearance or if there is an issue...

@SanduRajapakse please the updated response, we're using the same icon across all platforms.

@misolori Must have missed that. Great! Thanks for the update!

How to show new icon in ubuntu?

nice update....!

Nice new Icon, just dont like it in my macOS hotbar, it looks off compared to all my other programms. Liked the old one way more :/

The new icon looks off centered. When navigating to vscode, I find my eyes drawn to the smaller "x" then having to make the conscious decision to move it to the right (where the icon is bigger) before clicking.
Could we work on making the icon more centered or have the choice to switch to the older icon? Having a smaller surface area towards the middle of the icon is off-putting. Pls +1 if you experience the same.
Or maybe rotating the icon to look like a flask might help :)

@HolyChen Perhaps you could edit Code.VisualElementsManifest.xml in the same folder as Code.exe.

@infinnie Thanks. I modified the background color in xml and reboot and switch the theme, But it does not work.
I find this in official docs :

BackgroundColor
Specifies the background color of the app tile. See the Remarks section for color names.
Note that the background color specified here also applies to these items:

The button color in any app-owned dialog boxes
The App Description page in the Microsoft Store
Applies to Windows Phone: Choosing "transparent" causes the system accent color to be used.

It's seem that the file has nothing to do with background color in startup menu.

MacOS: you can just remove VS Code from the dock and re-add it to get the updated icon if you haev dock icon caching issues...no need to to sudo commands 😄

I love how fellow devs are (just as) passionate about their icons. I think designers sometimes underestimate how discerning we are about aesthetics. 😄

The new logo reminds me my old Word logo haha!

@fivetwelve I hope this thread speaks for how much we value everyone's input and how passionate the community is around our design changes (you can also poke into this thread to see more). We're extremely thankful for the feedback, good or bad. 😄
@alexmngn please see this comment (and original post) regarding why Insiders needs to be different. We can't solely use color to differentiate otherwise color blind users won't be able see the difference.

Not a great fan of the new Mac icon. The stubby "arms" lack the dynamism of the old icon and it gets  lost in the dock being somewhat empty and imbalanced. The original proposal for the Mac icon has more weight to it so works better here.

I got upset with the design of the new icon and I just wanted the design for the proposed icon.
So I made this from a random SVG of the Visual Studio for Mac icon and an SVG of the Visual Studio Code icon. I tried my best to re-create the proposed icon

The new VSCode stable icon didn't get updated on my dell laptop running Fedora 30 (GNOME 3.32). I've restarted this laptop atleast twice since the vscode update but that didn't help. Like someone above said, I've tried clearing and force-rebuilding the icon cache but that didn't work either. Here's what I see:

Is anyone else facing this issue?

@adryd325 Could you add a screenshot, it's easier to see the proposal directly in the comment, than having to download a icon file and open it in a image viewer.


[ACS] Update SSH tunnel docs for DC/OS and Swarm.

In particular, remove the need for sudo with DC/OS by suggesting a different local port. Also some clean up of commands and editorial fixes to be more succinct.

Hi @joshgav, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Josh Gavant). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@joshgav : Thanks for your contribution to the Azure documentation! The author, @rgardler, has been notified to review your proposed change.

@joshgav - can you rebase, and also fix the change suggestions from Ross so that we can sign this off?

@joshgav - Thanks for the contribution and your patience, Josh. I will close this and incorp your suggested changes (and accompanying comments from Ross) into the article in a separate PR.
#please-close

Thanks @dlepow!


False-Positive ( APT_Backdoor_Win_DShell_2.yar )

It looks like this rule matches with D compiler. Some vendors started flagging with relying on this yara rule;
https://www.virustotal.com/gui/file/a022820a62198fa3e3b89749b38db1cc3a09136524682fb99a3ce36652725065/details
https://github.com/fireeye/red_team_tool_countermeasures/blob/ac479ae150e1541445023952f569b7ca0d190b7b/rules/DSHELL/supplemental/yara/APT_Backdoor_Win_DShell_2.yar

to save people a click:

Despite the Tencent detection, I don't think this rule matches the file:

The rule should not flag rdmd thanks to these ignores:

Unfortunately, I don't have any insight into why Tencent flags this file nor how they've derived detections from this repository.
I'm going to close this issue because I think that the rule works as intended. If I misunderstood something, please reopen and I'm happy to discuss further.

This does have a FP matching the open source project https://github.com/CyberShadow/dhcptest

APT_Backdoor_Win_DShell_2 ../c32514711f72002e9a540c2434dee7b239485d01a95a7530b939fed43f277f6d
0x8295:$dlang6: ....\src\phobos\std\utf.d
0x606d:$dlang8: ....\src\phobos\std\format.d
0x67c1:$dlang8: ....\src\phobos\std\format.d
0x10e71:$dlang10: ....\src\phobos\std\stdio.d
<snipped all the $s* matches>

https://www.virustotal.com/gui/file/c32514711f72002e9a540c2434dee7b239485d01a95a7530b939fed43f277f6d/behavior/
Confirmed hash match with compiled binary linked from the github project page: http://files.thecybershadow.net/dhcptest/old/dhcptest-0.6-win32.exe
I have not analyzed the dhcptest program to determine how the rule may be modified, but wanted to make you aware.

a022820a62198fa3e3b89749b38db1cc3a09136524682fb99a3ce36652725065 is listed in https://github.com/fireeye/red_team_tool_countermeasures/blob/master/all-hashes.csv - Is that a mistake?


Adding plots for dates attribuets

Man what you have done with pandas-profiling is amazing it saves me hours a week !!
I think it would be great to have an additional plot for date attributes .
thx

There already is a histogram for dates in the newest version. What additional plot would you like to see?

I was on old version of the package , sorry


impute non-genotyped individuals

Dear author:
I am very interested in this software. I want to impute individuals non-genotyped but have phenotype and pedigree. Does this software support this function? Because this aspect is not covered in your instruction manual, if it is supported, how should it work? Thank you very much.

Phenotypes play no role in imputation (at least in AlphaIute2 or other major imputation tools).
If an individual has genotyped relatives (connected via pedigree) then you can impute expected genotypes, but note that this is obviously less accurate than if you would have some low density genotype on that individual.

Phenotypes play no role in imputation (at least in AlphaIute2 or other major imputation tools).
If an individual has genotyped relatives (connected via pedigree) then you can impute expected genotypes, but note that this is obviously less accurate than if you would have some low density genotype on that individual.


Fix Linux folders are case sensitive lead failed to upload file problem

Fix Linux folders are case sensitive lead failed to upload file problem
修复 Linux文件夹区分大小写导致上传文件失败的问题。

Thanks a lot, nice to see Linux version is actually used :)


Dealing with LocalData and a lot of columns

At https://github.com/Hydrospheredata/mist/blob/master/docs/use-cases/ml-realtime.md you demo how to use LocalData for real-time scoring.
My pipeline (loaded via spark pipeline persistence) tries to join the input record with additional data. This is not possible, as the only operation supported is  withColumn. Would you suggest to start a long running local spark context here?
Do you have plans to add this in the future?

@geoHeil I'm not sure what do you mean by "tries to join the input record with additional data"
Could you please attach a test ML pipeline you are trying to serve?
Thanks

@spushkarev For example, an input form on a website has 10 parameters. These will be part of the input for my ml model. One of these parameters is transaction time. Before running the model additional parameters need to be joined based on this and other parameters (preprocessing) I.e. weather at transaction time, type of holiday for transaction date, ....

@geoHeil Ok, I believe you don't need Spark and Mist to pre-calculate additional parameters like weather, holiday, etc. So, you'll need to build a complete parameters set and then serve the model like a pure function without any side effects and side lookups.
Does it make sense?

yes and no. But as an end 2 end ML pipeline I want to take the input parameters, apply preprocessing (i.e. add more data, data cleaning, feature engineering), learn the model and serve the result as an API.

Ok, so model training should be done in Spark context (batch or streaming) and it's not a realtime process by design.
After that the model could be served in Mist. So, only transform() pipeline has to be realtime.

That's right. But for a new and incoming record, it will require being preprocessed in the same way as the training data i.e enriched with other features (joined with some data). This is where I am not sure if the same pipeline code i.e. spark join will work with your local dataframe.

Stateless operations like Hashing, Tokenizing have to be supported in serving pipeline.
But mocking side affects like joins and additional lookups is overkill I think. So, the serving code should be designed not to hit external dependencies.

Why do you think that a "lookup table" is overkill?

@geoHeil I assume your data pre-processing & enrichment steps are not included into MLlib Pipeline? So, it could not be executed with PipelineModel.transform()?
This is unmanageable code where you can do big slow and distributed joins and use Spark capabilities. So, it's not a use case for local serving in realtime.
BUT your suggestion makes sense if pre-processing operations are lightweight and stateless. E.g. you map city to country using static dictionary. I think there are 2 options:

Implement custom Transformer, so the dictionary itself and all the transformation will be included and later serialized in ML Pipeline. So, you'll reuse a Transformer in training and serving context.
Re-implement pre-processing logic for single row serving without Spark, just in Scala or Python and then pass an output of this into Mist API.

I would be happy to brainstorm further if you have other suggestions.

@spushkarev these steps are not included in the default pipeline. But I created a custom Estimator and Transformer which implement mlibs API.
Most of the code should already collect and persist the data i.e. be compatible with a local code. Some of these substitutions were very convenient using sparks join. But these could be reimplemented using a hashmap lookup.

Ok, now I finally got your use case. So, you already took an option (1) I have mentioned. We'll not intercept Spark joins, no magic here. Please implement local hashmap lookup, so it will be a part of your ML model.

@spushkarev To understand you correct: only the transform step of the estimator should be built in a way that it supports in-memory execution?

only the transform step of the estimator

You mean Transformer , not Estimator?

No estimator as transformer is stateless.
But you are correct that probably the transform method of both should use
local data structures to be considered for real time scoring
spushkarev<EMAIL_ADDRESS>schrieb am Mi. 1. Feb. 2017 um 18:35:

only the transform step of the estimator
You mean Transformer , not Estimator?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Hydrospheredata/mist/issues/133#issuecomment-276724107,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABnc9GivnoU66GpPoaL5Mr0Q-HsofQyMks5rYMGugaJpZM4Lu1rP
.

local model features were moved to spark-ml-serving


fix typo in docs queryable-projections.mdx

Fixes a typo in the docs

Thanks for the contribution 😊


test: update Firefox screenshots

What changed to require an update to the Firefox screenshots?

I'm guessing this is to fix the test failures on #2830.

@kevinbarabash The Firefox version was updated in https://github.com/KaTeX/KaTeX/pull/2841, but it seems GitHub no longer runs the workflow updated in the pull request.


New IFS Browser restructuring in 0.7.0 and behavior and also removal of shortcut link

With the new restructured IFS browser functionality it appears that I can add an IFS shortcut with the "+" icon from the IFS Browser or by right-clicking a directory link that's already there and selecting "Add IFS Shortcut".  Is that correct ? Just want to confirm.
Also my user home directory shows in the IFS browser. I like that as a default shortcut, but just wanted to confirm the intent that home dir should always show in the list.
Overall the functionality seems to work nicely.
Now for the question/issue:
If I want to delete an IFS shortcut, there appears to be no option to delete it from the list once added.  I tried "Delete Object' and it deleted my IFS folder and all its contents instead of removing the link. Owwww. There should probably be a Delete IFS Shortcut option. Hope this makes sense.

or by right-clicking a directory link that's already there and selecting "Add IFS Shortcut"

You can right-click
on any directory and use the 'Add IFS Shortcut', include the existing shortcut.

confirm the intent that home dir should always show in the list.

That is the default one, but you can add and remove shortcuts as you wish.

If I want to delete an IFS shortcut, there appears to be no option to delete it from the list once added.

Correct. Right now there is no way to right-click on a shortcut to remove it. Instead, there is a minus button you can use in the view which will let you select which shortcut you want to remove.

Ah got it. Tool tips weren't working last night for some reason.
Since you do have a right-click Add Shortcut it might be worth having the right-click remove IFS shortcut as well.
Food for thought.


Publish to WebApp Bot with LUIS fails with error - "Failed to parse azure account information object object"

Tried many options to deploy my Bot through Bot composer publish feature. Getting below error in publish log.
Bot is configured with LUIS and works locally. Trying to deploy with publish script as per new bot composer update i received.
Not sure where its going wrong tried using new way of MS login option in during publish and tried using az token json format also. Same errorr. Cross checked all keys and all in same region and under same resource group.
Errors:

"Failed to parse azure account information object object"
"SyntaxError - Unexpected token o in JSON at position 1"

Screenshots:
Error:

Publish profile:

duplicate of #5344

@sriget, If you didn't provision your luis resources through composer,  you need to add a luisResource to point to you luis prediction resource.
Here is an example:
{
  "name": "Luhan0603AF",
  "environment": "dev",
  "hostname": "Luhan0603AF-dev",   ------------------> This is the name of your webapp.
  "luisResource": "Luhan0603AF-dev-luis",   ----------------> This is the name of your luis prediction service.
  "settings": {
    "applicationInsights": {
      "InstrumentationKey": "26c2cebc-cb5e-4732-af5b-e816f7c0ef79"
    },
    "luis": {
      "endpointKey": ""
      "authoringKey": "",
      "region": "westus"
    },
    "MicrosoftAppId": "9de821a0-f856-4655-a9ac-3fb9a39c293f",
    "MicrosoftAppPassword": "qwert12345!@#$%^"
  }
}

Thanks @luhan2017 . it works fine now !!!

@luhan2017 Can you make sure to update the template in the Publishing Profile create to incl. this setting? Current nightly does not have this properly set:
{
"name": "",
"environment": "dev",
"runtimeIdentifier": "win-x64",
"settings": {
"applicationInsights": {
"InstrumentationKey": ""
},
"cosmosDb": {
"cosmosDBEndpoint": "",
"authKey": "",
"databaseId": "botstate-db",
"containerId": "botstate-container"
},
"blobStorage": {
"connectionString": "",
"container": ""
},
"luis": {
"authoringKey": "",
"authoringEndpoint": "",
"endpointKey": "",
"endpoint": "",
"region": "westus"
},
"MicrosoftAppId": "",
"MicrosoftAppPassword": ""
}
}

sure, will follow up in the next release.

Please can I get some urgent assistance.
Since moving to v1.3.1 of Composer I get the following issue when trying to publish.
"Error  - Required field accessToken is missing from publishing profile"
My redacted publishing profile as follows:
{
"name": "REDACTED",
"environment": "composer",
"runtimeIdentifier": "win-x64",
"settings": {
"applicationInsights": {
"InstrumentationKey": ""
},
"cosmosDb": {
"cosmosDBEndpoint": "",
"authKey": "",
"databaseId": "botstate-db",
"containerId": "botstate-container"
},
"blobStorage": {
"connectionString": "",
"container": ""
},
"luis": {
"authoringKey": "REDACTED",
"authoringEndpoint": "https://westeurope.api.cognitive.microsoft.com/",
"endpointKey": "REDACTED",
"endpoint": "https://westeurope.api.cognitive.microsoft.com/",
"region": "westeurope"
},
"MicrosoftAppId": "REDACTED",
"MicrosoftAppPassword": "REDACTED"
},
"accessToken": "REDACTED",
"qna": {
"endpoint": "REDACTED",
"subscriptionKey": "REDACTED"
},
"hostname": "REDACTED",
"luisResource": "REDACTED"
}

Apologies but I have since raised the above as #6081

Hi I am getting the same issue here. It's working fine previously and just today, I got this error. I added the luisResource to both settings and publish profile, still the same error. Is that something related to LUIS portal? I found the LUIS server is not stable.

I have the same experience . Worked fine one day, failed the next. Admittedly a lot of changes to dialog in between but no changes to the settings or publish settings. I can prove that the LUIS model is updated (eg a new intent is added) but the bot does not get published.

I am reporting the same issue. Have followed all of the advice in all the threads. I'm on 1.3.1. Was working the other day after working around it, now I can get past the dreaded "SyntaxError - Unexpected token o in JSON at position 1"
All resources created in westus.
Using a work account.
Publish Profile as follows:
{
"name": "REDACTED",
"environment": "dev",
"runtimeIdentifier": "win-x64",
"settings": {
"applicationInsights": {
"InstrumentationKey": "REDACTED"
},
"cosmosDb": {
"cosmosDBEndpoint": "REDACTED",
"authKey": "REDACTED",
"databaseId": "botstate-db",
"containerId": "botstate-container",
"collectionId": "botstate-collection"
},
"blobStorage": {
"connectionString": "REDACTED",
"container": "transcripts"
},
"luis": {
"authoringKey": "REDACTED",
"authoringEndpoint": "https://westus.api.cognitive.microsoft.com/",
"endpointKey": "REDACTED",
"endpoint": "https://westus.api.cognitive.microsoft.com/",
"region": "westus"
},
"MicrosoftAppId": "REDACTED",
"MicrosoftAppPassword": "REDACTED",
"qna": {
"endpoint": "https://REDACTED-qnahost.azurewebsites.net",
"subscriptionKey": "REDACTED"
}
},
"accessToken": "REDACTED",
"hostname": "REDACTED",
"luisResource": "REDACTED"
}
Debug...
2021-03-05T01:19:07.665Z composer:extensions:azurePublish { status: 'DEPLOY_INFO', message: 'Build succeeded!' }
2021-03-05T01:19:07.704Z composer:extensions:azurePublish { status: 'DEPLOY_INFO', message: 'start publish luis' }
2021-03-05T01:19:09.041Z composer:extensions:azurePublish {
status: 'DEPLOY_INFO',
message: 'Assigning to luis app id: a3171f17-a364-4e5a-b7b9-9d9809d0519f'
}
2021-03-05T01:19:10.473Z composer:extensions:azurePublish {
status: 'LUIS_PUBLISH_ERROR',
message: '{"name":"StatusCodeError","statusCode":400,"message":"400 - {\"error\":{\"code\":\"BadArgument\",\"message\":\"Failed to parse azure account information object object.\"}}","error":{"error":{"message":"Failed to parse azure account information object object."}},"options":{},"response":{"statusCode":400},"stack":"StatusCodeError: 400 - {\"error\":{\"code\":\"BadArgument\",\"message\":\"Failed to parse azure account information object object.\"}}\n    at new i (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:338:110597)\n    at F.callback (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:338:109440)\n    at F.e.callback.t.callback [as _callback] (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:338:108488)\n    at F.t._callback.t.callback.t.callback (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:368:4017)\n    at F.emit (events.js:210:5)\n    at F. (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:368:16714)\n    at F.emit (events.js:210:5)\n    at IncomingMessage. (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:368:15546)\n    at Object.onceWrapper (events.js:299:28)\n    at IncomingMessage.emit (events.js:215:7)\n    at endReadableNT (_stream_readable.js:1183:12)\n    at processTicksAndRejections (internal/process/task_queues.js:80:21)"}'
}
2021-03-05T01:19:11.684Z composer:extensions:azurePublish {
status: 'DEPLOY_ERROR',
message: '{"stack":"SyntaxError: Unexpected token o in JSON at position 1\n    at JSON.parse ()\n    at Object. (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:392:115579)\n    at C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:392:112703\n    at Object.throw (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:392:112808)\n    at s (C:\\Users\\dtall\\AppData\\Local\\Programs\\Bot Framework Composer\\resources\\app.asar.unpacked\\extensions\\azurePublish\\lib\\node\\index.js:392:111573)","message":"Unexpected token o in JSON at position 1"}'
}
2021-03-05T01:19:11.687Z composer:extensions:azurePublish SyntaxError: Unexpected token o in JSON at position 1
at JSON.parse ()
at Object. (C:\Users\dtall\AppData\Local\Programs\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\lib\node\index.js:392:115579)
at C:\Users\dtall\AppData\Local\Programs\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\lib\node\index.js:392:112703
at Object.throw (C:\Users\dtall\AppData\Local\Programs\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\lib\node\index.js:392:112808)
at s (C:\Users\dtall\AppData\Local\Programs\Bot Framework Composer\resources\app.asar.unpacked\extensions\azurePublish\lib\node\index.js:392:111573)
2021-03-05T01:19:12.863Z composer:bot-project No schemas directory found.
GET /api/publish/56237.44182596713/status/Test4 500 1794.387 ms - -

By the way, contacted with the microsoft support team and turns out it's LUIS portal UI issue. Now it's all working as it before.

Hi Jenny, please can you elaborate on your comment. Do you have an example redacted publishing profile you can share please? Thank you

@Jenny0932 is this issue resolved or not? I got the same error. The region is westus.

I am getting this error:
Error - Failed to bind luis prediction resource to luis applications.
Please check if your luisResource is set to luis prediction service name in your publish profile.

Can someone help me or give some pointer here?

@praful-dhone @damlaalkan see my comments here: https://github.com/microsoft/BotFramework-Composer/issues/5354#issuecomment-747150353

@luhan2017

I have added those keys in the json. You can see it in attachment, still getting same error.

Is there anything that I am missing here? Also MicrosoftAppId and Password is compulsory to pass here in JSON?

@luhan2017
I have added those keys in JSON

Still getting the same error.

Is it compulsory to pass MicrosoftAppId and MicrosoftAppPassword in the JSON? How do I get it?

@luhan2017
I have added those keys in JSON

Still getting the same error.

Is it compulsory to pass MicrosoftAppId and MicrosoftAppPassword in the JSON? How do I get it?

Hello @luhan2017 I have connected the LUIS in bot composer and when I start publish with "Create new resources" not "Import existing resources" how can we integrate the existing luis model?

@damlaalkan @praful-dhone sorry for the late responses, are you OK to have a live debug session with me?

Hello Luhan, in nightly version the problem has solved for me thank you!

Hi @luhan2017  - I am having the same issue, even after following your tips above ensuring that the hostname, luisResource, etc are correct.  I would love a live session to help solve the issue if thats at all possible?

Sure, are you OK to have a live session with me today? I am in Beijing UTC+8. I will be on vacation from 4/30 to 5/5. Or we can talk after I am back.

You have this in extensions.js/Line 183600 ( more or less):
async function publishLuisToPrediction(name, environment, accessToken, luisSettings, luisResource, path4, logger, runtime)
{
...
...
...
const response = await rp.post(getAccountUri, options)
...
...
...
}
you have to change post to get :
const response = await rp.get(getAccountUri, options)

Hi All, sorry i did fix this in the end.  I did the following actions:

Ensured i was not going through my companies Proxy (direct internet connection)
Updated the Bot Composer to the latest (nightly - 2.0+) build
I also deleted the Luis.AI apps (to allow the Bot composer to recreate them), which probably wasnt required because of the below action
Created a new publishing profile in Bot Framework, which created an entirely new set of Azure resources

After these actions I've been having ZERO issues with additional changes.
ALSO...
I later found out not to modify/train the bot in Luis.AI directly... this causes issues with additional play/publish from the Bot Composer. This causes an issue "Error: Cannot read property 'utterances' of undefined".  To fix this I deleted the Luis.AI apps (to allow the Bot composer to recreate them) in the next play/publish

I don't understand, if we need LUIS.AI to help training the bot, why after using it the Bot stops working on Framework Composer? This needs to be fixed, I've just ran into this problem and it's sad to hear that I'll have to lose all my work LUIS to this point..

Thanks @luhan2017 . it works fine now !!!

I am having an issue when publishing a profile from the Bot composer
Issue: unexpected token u in JSON at position 0
one more thing I want to ask:
What is the authoring key and endpoint key, where to get these keys in Azure?
Luis": {
"authoringKey": "",
"authoringEndpoint": "",
"endpointKey": "",
"endpoint": "",
"region": "westus"
},
please help me I'm stuck at this point...Thanks


Use file listing in promotion to narrow scope of NFC clear-out

I'll check back in on this tonight, and start a release if the build passes. We can review after the fact and I can always run another build / release if there's a problem. If not, then we'll have a release we can push either overnight my time, or else tomorrow first thing.
@ligangty if I can get my release out tonight and things look ok, I'd like you to work with the PNC folks / sysops to push this into prod.

@ruhan1 I'm going to try to release this tonight in about an hour if I can get all the kinks worked out. I'm happy to incorporate another change if necessary, but this is the place where regressions can get injected if we get too greedy...so I'll have to be careful to understand the ramifications for anything else I do. :grinning:

@ruhan1 I understand now that I've looked at the code again. I forgot to refactor the clear process for the target store itself. I've added another commit to change that.


NERDTreeCopyPath printing path instead of copying path on ubuntu

Before creating an issue, take some time to search these resources. It's possible that someone else has already asked your question and gotten an answer.

old NERDTree issues
NERDTree documentation - :h NERDTree
NERDTree Wiki
Other resource: https://stackoverflow.com, https://vi.stackexchange.com, etc.

State Your Question
I use the following to use yy to copy the path of a file from NERDTree. It works fine on my MacBook but it won't copy but print the path on ubuntu. Why is it the case? Is it possible to copy into the clipboard on ubuntu?
  autocmd VimEnter * call NERDTreeAddKeyMap({
      ┆   \ 'key': 'yy',
      ┆   \ 'callback': 'NERDTreeCopyPath',
      ┆   \ 'quickhelpText': 'put full path of current node into the default register' })

@hwijeen You have a version of Vim installed without the clipboard feature. If you are on Ubuntu you can install either gvim or vim-gtk3 if you want to have a full feature build of vim.
write :version in the vim or use vim --version in the terminal to find out about features that are enabled in your vim build.
You can also obviously rebuild Vim for yourself with +clipboard but I personally advise you to keep a full-featured Vim upstream in your package manager so you get seamless updates without the need for rebuilds by yourself


bug(yaml): Cannot access nested yml entry (not array)

When it works
When trying to use this command on a regular system, it works:
yq '.scaling.zoom' "$1"  ("$1" is the recipe yml file)
When it does not work
When trying to run this command through container, it does not work & complains with this error:
Error: open {"type":"wallpapers","default":{"wallpaper-light-dark":["grasssky-bb-light.jxl + grasssky-bb-dark.jxl"]}}: no such file or directory

For some reason, it tries to open recipe .yml content as a file.
But when manually specifying the recipe.yml location, it works:
yq '.scaling.zoom' "/tmp/config/recipe.yml"
This should not be the solution, as the recipe file is generated dynamically based on "$1" variable.
Affected .yml recipe file
type: wallpapers
default:
  wallpaper:
    - my-default-wallpaper.jpg
  wallpaper-light-dark:
    - my-default-wallpaper-bb-light.jpg + my-default-wallpaper-bb-dark.jpg
scaling:
  zoom: all
  centered:
    - my-default-wallpaper.jpg
  scaled:
    - my-wallpaper.jpg
  stretched:
    - my-default-wallpaper-bb-light.jpg + my-default-wallpaper-bb-dark.jpg

Is the yq version on your local system different than the one in the container? Our container builds use the latest version from https://hub.docker.com/r/mikefarah/yq

cat "$1" | yq '.scaling.zoom' does not work either

cat expects a file, try with echo

That is expected, as I'm passing the recipe file into yq.
That means that it's also expected that your echo suggestion does not work in both build-time & booted-system scenario.
I just tried it.

That is expected, as I'm passing the recipe file into yq.

Why? By default the modules are provided the JSON string, you're not supposed to read module configuration from the file directly. What are you trying to accomplish?

That is expected, as I'm passing the recipe file into yq.

Why? By default the modules are provided the JSON string, you're not supposed to read module configuration from the file directly. What are you trying to accomplish?

I was just a bit confused with $1 recipe variable, so I tried cat & echo stuff.
Adding -I=0 flag solved this & now I don't get any build errors related to this.
echo "$1" | yq -I=0 '.scaling.zoom'

This page should have the proper information about this: https://blue-build.org/how-to/making-modules/#coding-your-module


Be able to execute rspec for each file

In order to be able to execute rspec for each file, I made sure that all spec files require rspec_helper.
Because we did not require rspec_helper, some files could not be executed by itself (eg bundle execp rspec spec/generic/client_stub_spec.rb).

C# server failed in cloud to cloud interop tests with https://github.com/grpc/grpc/issues/15557


use IO.console to get terminal width

This zaps some TODOs in the Progressbar class, relying on the IO library to get the current console width.
Tested on OS X 10.11.

assuming this repo is abandoned


Lindalu fix build errors

Docs Build status updates of commit 5ac9a63:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b0ceb23:
:warning: Validation status: warnings

File
Status
Preview URL
Details

project-xml-data-interchange/assignment-elements-and-xml-structure.md
:warning:Warning

Details

project-xml-data-interchange/resource-elements-and-xml-structure.md
:warning:Warning

Details

project-xml-data-interchange/alphabetical-list-of-elements-and-types.md
:bulb:Suggestion

Details

project-xml-data-interchange/summary-element.md
:bulb:Suggestion

Details

project-xml-data-interchange/project-data-interchange-elements.md
:white_check_mark:Succeeded

project-xml-data-interchange/assignment-elements-and-xml-structure.md

Line 37, Column 86: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2003/aa220056(v=office.11)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 219, Column 1: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb968479(v=office.12)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37, Column 86: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2003/aa220056(v=office.11)' will be broken in isolated environments. Replace with a relative link.
Line 219, Column 1: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/previous-versions/office/developer/office-2007/bb968479(v=office.12)' will be broken in isolated environments. Replace with a relative link.

project-xml-data-interchange/resource-elements-and-xml-structure.md

Line 38, Column 95: [Warning: hard-coded-locale - See documentation] Link 'https://msdn.microsoft.com/en-us/library/317823-7111-4dfd-ae38-50a06c6cb70f(v=office.12)' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 289, Column 1: [Suggestion: preserve-view-not-set - See documentation] You've pinned this link to a specific version of content with the view parameter. It's recommended not to pin a version unless that version is A) not the default view and B) the context is about that version specifically. To proceed with pinning a version add the &preserve-view=true to the URL.  Otherwise, remove the view parameter. URL: /office-project/xml-data-interchange/timephaseddatatype-elements-and-xml-structure?view=project-client-2016

project-xml-data-interchange/alphabetical-list-of-elements-and-types.md

Line 22, Column 8: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'table' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 24, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 25, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 26, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 27, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 28, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 29, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

project-xml-data-interchange/summary-element.md

Line 30, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 43, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 59, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 60, Column 6: [Suggestion: disallowed-html-attribute - See documentation] HTML attribute 'style' on tag 'col' isn't allowed. Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


force_drag() is not working

Godot version:
2.1
Issue description (what happened, and what was expected):
force_drag() method from Control is not working can't drop data on Control
Here is sample project.
Link to minimal example project :
Force_drag_test.zip

closed via db9335f4c1247d950b4858b56d653975bb3058ff

Thanks xD


Bug？

Hi I'm new here so I'm not sure whether this is the right place to say that I caught a  bug in ur code...In line 10 and in line 54 'RT3' might be 'RT2' ? Thx for share code it really helps me a lot!!

Yes, absolutely! I just saw it too. It arose from when I was relabelling my servos with the naming convention so as to make it easier to follow by the general public.
I'm currently running the edits now. It wasn't just lines 10 and 54, though.
What I initially did was a 'Find and Replace' operation which accidentally converted all "Right Tibia 2" servos to "Right Tibia 3", but I'm sorting out the issues now.
Thank you so much for your observation xoxo.

This is the naming convention I came up with

It's been sorted out now. Thanks, once again, for the observation.