Improve Spyder logo for Spyder 5

Issue Report Checklist

[ ] Searched the issues page for similar reports
[ ] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
Now that we have a UX/UI designer helping us in Spyder, one of our goals is to change the logo for Spyder 5.
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:

Dependencies

PASTE DEPENDENCIES HERE

I will be working on this! I can't seem to assign it to myself formally right now.

Thanks a lot @isabela-pf for your help with this! We've wanting to do it for a looong time!
Pinging @spyder-ide/core-developers about this, specially @jnsebgosselin. Isabella will be posting updates here from time to time for everyone to see and discuss about them.

Looking forward to it @isabela-pf !

Here are some early drafts showcasing a few different possible directions we could refine. Each draws from a different aspect of Spyder as inspiration. Each direction is presented as a full color, one color, and mockup as a favicon (to give an example of the logo at a small size).
Because all these directions have such different form from the current logo, I decided to stick with red as the main color for continuity. I did use a darker red, since the current one is a more alarming almost pure red when used for more than just a small portion of the logo. All versions currently use Titillium Web Bold as the typeface.
1-1
Direction 1 emphasizes the Python side of Spyder but still keeps the web from the current logo. It has a strong silhouette that scales well.

2-1
Direction 2 pulls the web shape and snake from the current logo while pulling in a spider. It has the most comprehensive set of elements, but that also means it has the most details which can make it the most overwhelming and hardest to spot on small scales.

3-1
Direction 3 is meant to reference the panes that make up Spyder and keep the web from the current logo. Even though it scales well rectangles aren’t a unique shape.

4-1
Direction 4 is really just a spider, but it has a strong silhouette and scales very well so I’ve included in case it might be a good option with more development.

Thanks so much for sharing, @isabela-pf ! I definitely prefer the darker red. I'm not sure I have a strong opinion of the design directions as of yet, but I do have some impressions:
Option 1-1
This option was bold, unique and kept more continuity with the previous logo than most of the others, but I personally found it rather confusing and hard to understand the symbology, and to me the overall look of the snake eating the Spyder web seemed a bit off-putting and not very appealing to users considering whether to use and trust the application. I'd lean against this direction without radical changes.
Option 2-1
On the plus side, this option incorporates both key elements (spyder and snake) as well as an S in a visually appealing way. The main downside as mentioned is the complexity; it wouldn't scale as well to smaller resolutions and might be harder for users to quickly understand, and also doesn't connect as strongly with the previous logo so users can quickly identify it as the Spyder they are familiar with. The lack of one bold element also makes it a little less strong. Perhaps with some simplification and tweaks (e.g. making the Spyder's legs closer together so its clear what it represents) it might work better?
Option 3-1
This options is definitely the most conservative and least distinctive, but also the most modern, polished and representing a clear evolution from the previous design, both in terms of maintaining continuity with a much more refined style. A coming of age for Spyder, if you will. Its simplicity means it would work the best at a range of sizes, and also avoids being bothersome to those that don't like spiders or snakes. It lacks anything indicative of Python, but in the long term this may be a plus, if and when Spyder supports other languages. As such, I think I'd lean toward this option, personally, since it most closely fits the story we want to tell with the new logo, with my main reservation being that it does look just a little generic.
Option 4-1
I like that this option combines the simplicity of 3-1 with the boldness of 1-1, and I'd say its my second choice. The stylized S is distinctive, but I'm a little unsure if the particular style should connect more closely conceptually with that of Spyder itself. Like 2-1, the Spyder silhouette might be made a little more clear by decreasing the spread between the legs. Its somewhat conceptually tied with the previous in style and overall look rather than the actual elements included, though I'd say 3-1 has the edge on it. My main reservation is it not looking nearly as professional, refined and "grown up" as 3-1, maintaining more of the wacky underdog character of the IDE...how much this is a good thing is a matter of opinion, but I think Spyder would do well to cultivate more of a polished image.

Very nice, well done! These are my thoughts:
1-1: I really like the idea of combining the spider web and the python. However, if I am honest, I like the idea more than the actual logo. I agree with CAM that the actual logo is difficult to understand. That's not necessarily a problem; perhaps you can stylize it more and get a visually appealing logo with a hidden meaning. Or perhaps colours will help to make the logo easier to grasp. But I feel this option needs the most work and it may well be that it proves impossible to execute the idea well. I did not at all get the impression of the python eating the spider web; actually, the logo reminds me of a wine glass (I'm sure people can think of all kinds of psychological explanations for this!).
2-1: Looks nice but perhaps a bit too complicated for a logo. To me, this looks far more like the snake eating the spider than the previous option: the snake is coiling around the spider and seems about to strike down and bite. While the details are lost when the logo is scaled down, I think the hexagonal shape that is left is still pretty distinctive.
3-1: I can't decide whether I like this or not. It looks attractive and sleek but also corporate and loses the playfulness that attracts me to Python. Even after you say that the rectangles reference the panes, I still associate them with files, and there is no such thing as a Spyder file. The lack of snake is not a problem for me. I feel this is a design that we can use immediately without any further work.
4-1: Like you say, it's a simple idea but I do like it. The shape of an S does remind me of a snake, though this would perhaps point to having a more curvy and less angular S. We can spin a story of Spyder eating bugs, though this may backfire if people think that spiders are bugs themselves... I think this option would have my preference for further development if I were forced to choose.

@isabela-pf Thank you for working on this. It something we have been in need of for sometime. I like the color and the font.
This is only my option of course, but I think that currently Spyder strongest current branding element comes from the spider web pattern. I agree with @CAM-Gerlach that spiders and snakes don't have the best connotations for most people. I also think that there are plans in the future to support other languages like R or Julia in the future so the snake from Python might not be as applicable(of course Spyder is written in python). I would like the spider web for Spyder to represent that Spyder at it's heart is a collection of plugins or toolboxes that are held together and connected by Spyder like a web to make unique and customizable work flows for scientific computing.
I don't want to over step but you inspired me to make a mash of the hexagon from 2-1 and the web from 3-1 and I made this:

The outcome is a bit simple but the spider web on a hexagon make for really cool geometric shapes and as a happy accident it can look like a cube as well to symbolize working with array like data.
I also put an "S" on there to see what it looks like:

I like @bcolsen 's design ideas; I think they combine some of the strongest elements of the designs we've liked so far—a bold and recognizable appearance, a relatively simple and easily scaled design, visual continuity with our previous branding, a better balance between "polished"/"corperate" and "fun"/"unprofessional", avoiding elements that might bother, distract or restrict us going forward, and most of all with symbology that reflects the core of who and what we are. I particularly love the duality between the web, bringing together a diverse collection of plugins, tools and packages under one roof (just like the Spyder team and its users span the globe) and the cube, symbolizing Spyder's connection to the SciPy/Pydata ecosystem.
I'm a little on the fence about which one I prefer—the first is simple, clean, bold and uncluttered, but maybe a bit too simple and generic, while the second is somewhat busy but is more visually interesting and distinctive, and the shape of the S enhances the "cube" effect that is harder to see in the first one. Perhaps using the former at small sizes (favicon, title bar icon, website top bar) and the latter at larger ones (splash, app logo, backgrounds, etc)?

The cube effect could be enhanced by using 3 slightly different shades of red for the faces. It would then look like a set of unset  boxes that would be a cool metaphor for bring different software packages together. Boxes in a web if will.

Thanks everyone for the great feedback! I'm always glad to see people analyzing the strengths and weaknesses of a design and offering more ideas. I look forward to hearing what you have to say next.
Following the focus of option 3-1, this next round of logos are centered around spider webs and (I really like what @CAM-Gerlach  said about them) and Spyder’s emphasis on panes. Because panes are rectangular and rectangles alone don’t make for the most unique shape, I mostly used them for inspiration in framing the web in different ways. The range here is from a pretty literal web to an abstract use of web shapes.
Option 3-2
This is a fairly typical direction, but the web is framed in the corner of a pane rather than the symmetry it had in most of the last iterations. Depending how immediately recognizable we are interested in the web being, this could be a direction to explore more.

Option 3-3
Keeping the web in a corner but making it heavier (which can help at small sizes especially) and geometric. This direction also breaks out of the square.

Option 3-4
A closer look at the curved web pattern with a good amount of weight behind it. It is getting close to a square silhouette, which is not as unique. I'm also unsure if it looks a little close to Kite's logo or if it is different enough.

Option 3-5
This direction has all the pros and cons of Option 3-4, it is just a more geometric and abstract version.

Hey @isabela-pf , thanks for the additional batch of great logo ideas as well as the kind words! My thoughts on this one are much clearer than that last.
Option 3-2
I like the web motif and its strong, recognizable and scales well. However, I'm not sure the idea of the square shape being the corner of a pane really comes across clearly even after reading the description, and I didn't even really think of that until I read it. To me, it reads more as an old book with a cobweb on it, or perhaps a kite (which we want to avoid as you say) made out of the same. Even if taken for what it is intended to be, from a conceptual and branding perspective I'm not sure a cobweb on the corner of a pane is really the best look, considering the connotations of being old, unused and untouched in a long time, as opposed to a vibrant, constantly evolving modern tool with an active community and developer team. Visually it has promise, but conceptually I'd definitely lean against this direction personally.
Option 3-3
This option is definitely my favorite. It scales almost as well as the others, looks attractive in both single and bicolor versions, incorporates the two primary colors and easily recognizable shape from Spyder's current logo, but in a much bolder design. I think it does much better than 3-1 at striking a good balance of clean, modern and professional, while avoiding looking too generic, and corporate and losing the quirky soul of the old one. It also avoids the negative connotations of cobwebs and spiders, unlike some of the others.
Option 3-4
It has a bold, striking and attractive appearance while still retaining the colors and at least a modest part of the web motif, a lot of the things I like from 3-3. However, I share your concerns about it looking too much like a kite; that's definitely the first impression I get of it, and it speaks "spiderweb" less clearly to me. Its also less distinctive, unique and perhaps a little too abstract for my taste. Its definitely my second choice of these four, but just as definitely not my first.
Option 3-5
This one basically follows 3-4, but has less of what I like and more of what I don't care as much for. Personally, I feel its much to abstract to read "spiderweb" and has a more generic appearance, and has some of the same downsides as 3-1 without the same advantages. It also approaches the realm of confusion with the well-known Adobe logo, with a very similar color, generally similar lines and what could be read to be an "A". Overall, it really doesn't speak "Spyder" to me, and if we are going in this general direction, I'd definitely lean toward 3-4 over it.

I really like the 3-3 option

I also like the 3-3 design best, with 3-2 being a close second.

3-3 :+1:

It looks like we’re getting closer! I’m glad to hear 3-3 is working well for so many people.
Since there is agreement that 3-3 is the preferred option, I explored a few ways of refining 3-3’s direction to see if there is something even stronger. Many of these options have overall small changes, but they experiment with giving the logo a different silhouette while keeping the concept.
These first two options are 3-3 rotated.
Option 3-6
3-6 matches the rotation of 3-1 for those who preferred it.

Option 3-7

I also tried enclosing the web pattern in different shapes. Originally, I was keeping with squares, rectangles, and sharp corners to continue the reference to panes I brought up in 3-1, but I do think some of the options with circles or rounded edges are working well too.
Option 3-8

Option 3-9

Option 3-10

3-9 and 3-10 are personally my least favorites, though I think they could work with some more clean up if people do want a logo with a more typical shape.

I also wanted to address some more specific feedback I’ve gotten away from this issue in case other people have the same questions.
First, why do most options not show the full, symmetrical web? It takes a lot of small pieces to make something look like a spider web, and having a lot of small pieces isn’t ideal for a logo because it takes people longer to recognize it and loses details quickly as it gets smaller.
 If I scale down this illustration as a favicon, like below, it is difficult to see. There’s multiple ways I could lessen the amount of small pieces in the web to make it scalable, but the one that tends to keep it looking most like a spider web is to crop it instead of show the whole web. (This isn't intended as a logo option.)

Second, the red and grey are a dark combination. Even though I agree the grey is dark, I’ve kept it in hopes it will help keep Spyder identifiable while the logo form changes. What I did try is experimenting with a third color. Lots of colors I tried with clashed with the red since it is pretty strong, so I’ve only proposed one option. This saturated red-orange brings back some of the current logo’s brightness, but it does take away focus from the other red.
It’s mocked up here just because it fit well with the multiple layers in 3-9, but if there is interest in working more with three colors I can apply it elsewhere.

I don't really have super-strong opinions on most of these, but here are my thoughts.
3-6
I think I like this rotation better relative to the text, although it looks a touch more generic and for whatever reason it speaks "web" to me a little bit less (perhaps because cobwebs are typically seen in the upper corners of things...but not sure we want to look too much like one). So I think it might look a little stronger than 3-3 overall but I'm not 100% sure. I would defer to others' feedback on this.
3-7
This one speaks a little less "Spyderweb" to me due to the orientation making the cutout shape more emphasized. However, it trades that off for being somewhat more evocative of data analysis and scientific computing, by looking like a funnel filtering a large volume of data by several layers, progressively from information to conclusions. Not sure how strongly it communicates this to others and whether it is worth it, but its an interesting direction and something I'd like to hear the other devs' feedback on.
3-8
Not sure I like the circle motif, IMO it makes the straight lines of the web less strong, doesn't look clearly speak Spyderweb, and it doesn't have the potential conceptual advantage of 3-7 exchange for the orientation switch. I also prefer the colors reversed, as they are in the others.
3-9
The circle has more of a reason to be here, but at least to my personal eye it looks a little too off-center...not sure.Other than that, I don't have really strong feelings on it either way.
3-10
The "app" shaped rounded rectangle looks more modern and motivated, so I think I prefer it to its counterpart 3-9. But I think perhaps 3-6 still looks somewhat stronger and more unique overall since the enclosing shape somewhat dilutes the strong impact of the octagonal web.
So, if I were to rank them in tentative descending order of my preference, I'd say maybe 3-7, 3-6, 3-3, 3-10, 3-9, 3-8, though the borders between items get somewhat fuzzy since none of my feelings are overly strong (as I guess makes sense at this refinement stage).

Because it seems like I got more unsure feedback last round, I tried branching focusing in on the elements that have gotten some of the strongest positive feedback across these iterations, namely the web combined with simple shapes.
Option 3-11
Since 3-1 was a strong favorite, this is a cleaned up version of that direction minus the overlapping panes. It's simple, but that can be a strength at small sizes.

Option 3-12
Just like 3-11, this has the same inspiration. I also combined what some people liked about 3-7 looking filter-like and comments about extending the web to the edge of its encapsulation. I prefer this option over 3-11.

Option 3-13
This is an iteration on the more complete web encapsulated in its own hexagon. The offset also creates a kind of arrow that implies the kind of growth and expansion that was a concept liked in 3-7.

Option 3-14
This one is the web combined with some spider imagery. I know we said no to any kind of animal imagery early on, but one thing I've been struggling with in this process it pushing to have a logo with an interesting silhouette since that helps it be more identifiable. I think this is a more understated use of the spider and is still geometric enough to look serious. I've ended up liking this one more than I thought, but of course that's not up to me alone.

Other than the shape of the logomark, here’s some of the changes  (in response to feedback I've gotten in meetings) that should be noted/reviewed:

Color. The red has changed from #8c0000 to #d50000 as a middle ground between the current red and the darkness of the last iterations.
Gradients. I tend to be hesitant of gradients since they are easy to do poorly and can provide some obstacles. Since it’s come up in meetings that there’s interest in having a little more texture, I’ve added options with gentle gradients this round. One-color versions still use flat #ffffff white.
Type. I’ve gotten some mixed feedback about the ‘y’ in the typeface I’ve been using. Since I’ve posted, I’ve modified and run through a lot of typefaces being particularly picky about their ‘y’s, so below are options with a modified ‘y’ (not pure Titillium, so a softer curve).

Option 3-11 (Alternate Type)

Option 3-12 (Alternate Type)

Option 3-13 (Alternate Type)

Option 3-14 (Alternate Type)

Thanks for your patience! Hope this helps people feel a little more sure about directions they like.

@spyder-ide/core-developers, although Isabella's proposals have some interesting ideas, I was thinking that she could help us to go in a new direction too: a redesign of the current logo, perhaps also reshaping the snake to display an S instead.
What do you think about that?

I like the new red. I would like to see also like to see 3-6 with the new red.
I also really like 3-13. I think the hexagon captures enough of the original logo idea to still be recognizable.
I think the original "y" gave it a nice edge. For some reason the new one make the "spy" part stand out. I could be the curve.

a redesign of the current logo, perhaps also reshaping the snake to display an S instead

I'm not sure that we need a snake on the logo, aren't we looking to include more languages in the future?

I'm not sure that we need a snake on the logo, aren't we looking to include more languages in the future?

Right, that's a good point. But my suggestion is to show an S on top of the spider's web.

I would like to see also like to see 3-6 with the new red.

Me too

Based on some of my recent discussions with Spyder team members, it sounds like we might have narrowed in on the concept of connection and its representation as a spider web too quickly. Since we're looking to think about other concepts, I'm interested in hearing other people's idea of what Spyder is, what its goals are, or what parts of Spyder make it unique to you. Please feel free to share your thoughts on these questions!

Here is my idea of what Spyder is: Spyder is an open program for doing computational and data science using Python, which is suitable for all phases of a project (from exploration to consolidation) and for people with different levels of programming expertise.

Are you open to proposals here? I am, among other things, a logo designer, and I would be happy to help 😃.

Sure! We'd like to see other people's ideas for our new logo.

Thanks for everyone’s patience as I worked on some other parts of Spyder! This next round has all new directions separate from the web idea. Because I’m not sure which red we are interested in right now, I’m showing both dark and light options.
Since we are taking a step back from the web concept, some of the most helpful feedback for this set will be if any of these ideas seem like they should be pursued further. Deciding on a red would be a bonus!
Option 4-1
This option combines idea of Spyder being open and framing the many spaces/panes that make up Spyder. It also looks a little bit like the letter S. It has a good silhouette that should scale well even with the amount of open space. Personally, this is my favorite option of the three.

Option 5-1
Option 5-1 is inspired by objects organized on a desk, similar to how I think of all of Spyder’s panes aligning. It also includes an actual S since it has come up in a few meetings. The S helps make the relatively simple rectangles more distinctive. You may have noticed the text looks different; it’s a lighter version of the same font just to try something a little different.

Option 6-1
Even though option 6-1 is inspired by the same ideas as option 5-1, I noted it as its separate option because I think it looks very different without a letter and cropping the shapes differently. I experimented with several shapes, and I think working with diagonals benefits the neatness of the shapes within it.

Thanks for everyone’s patience as I worked on some other parts of Spyder! This next round has all new directions separate from the web idea. Because I’m not sure which red we are interested in right now, I’m showing both dark and light options.
Since we are taking a step back from the web concept, some of the most helpful feedback for this set will be if any of these ideas seem like they should be pursued further. Deciding on a red would be a bonus!
Option 4-1
This option combines idea of Spyder being open and framing the many spaces/panes that make up Spyder. It also looks a little bit like the letter S. It has a good silhouette that should scale well even with the amount of open space. Personally, this is my favorite option of the three.

Option 5-1
Option 5-1 is inspired by objects organized on a desk, similar to how I think of all of Spyder’s panes aligning. It also includes an actual S since it has come up in a few meetings. The S helps make the relatively simple rectangles more distinctive. You may have noticed the text looks different; it’s a lighter version of the same font just to try something a little different.

Option 6-1
Even though option 6-1 is inspired by the same ideas as option 5-1, I noted it as its separate option because I think it looks very different without a letter and cropping the shapes differently. I experimented with several shapes, and I think working with diagonals benefits the neatness of the shapes within it.

Aaaaand we're back. I'm not entirely clear on the feedback from the last round, but I think I heard something about being interested in going back to the web? This time I bring two different options for you to review.
Option 3-15
As the numbering implies, this tries to return back to working with the web. It is much lighter (and uses a lighter font to match) and ties the wordmark into the design rather than keeping it beside it. Since there has been much discussion about the right concepts to focus on in representing Spyder, I thought it might be helpful to rely a little more on the S and less on symbols people are unsure about.
To be honest, I'm running low on ideas of how to keep working with the web concept in this style.

Option 7-1
Carrying over from idea of relying on S and the concepts of Spyder being made of many open parts, I have one more abstract proposal. This version is light like 3-15 and changes to the same light font.

I like the web. My favourite was option 3-12 because the web looks "attached". If the web is in a frame as in 3-15 I think I would like having the radial lines extend to the edges. This would look more physically plausible. Looking back at 3-12 I was not a fan of having several filling colours. I like the colours on 3-15. Then for the shape 3-10 was quite nice, I like the "app" look. So I guess I would like something like:

(With or without the "S")

With the nice S:

I like 3-16 :)

Long comment incoming!
There’s interest in this last round of logos, but also some questions about how they will work in different circumstances. The request was to show options with 3-16 (slightly modified to be a square), a filled version of 3-16, 3-17, and 3-18. Some of these examples will be repeated from above for ease of review.
3-16 square
3-16 with the web area slightly modified to be a perfect square.

In Spyder's About screen (dark mode) this could look like

We won't get good contrast with the current dark red (this is the case no matter the logo)…

But we could if we go with a lighter color (shown as light red here). Please note that I think we should choose one red and not switch back and forth. These mockups are just to clarify the strengths and weaknesses of the colors.

In a Windows header

In a Mac dock

I know one of the main concerns for the outline versions of the logo are that they have a lot of empty space that might make them hard to see on different backgrounds. This is true! I think it has a simple fix, though: put it on its own background color whenever the logo is not already on a flat color background. I’ve used a photo background as an example for all the options.

(Here you can see it without the background to see why it is not working)

3-16 with thicker lines
A non-square 3-16 with heavier web lines and typeface. I want to clean up the web a little more if we like this direction.

About

Windows

Mac

Here's the photo background again. I still think it works better on its own background.

3-16 filled
A non-square 3-16 with a grey fill background like 3-17 and 3-18. This option has no cut out areas in the logomark. But since it uses more colors to make that possible, there's a few places where I think it becomes difficult to handle. I don't think this version is working.

You can already see how this becomes complicated with the white logo. Since this is a test designed to show a one color logo and this version can't be one color, you end up with some kind of low contrast combinations.

About

Windows

Mac

Photo background (same problems as discussed above)

3-17
The same 3-17 from my previous comment shown on other mockups for better comparison.

I've shown the about in one color for ease, but as mentioned under 3-16 square above this can be full color if we want to use a lighter brand color than the dark red.

Windows

Mac

Photo background

3-18
The same 3-18 from my previous comment shown on other mockups for better comparison.

About

Windows

Mac

Photo background

Congrats on making it to the end of this comment ! Thanks for your patience, and I hope this helps the team feel more confident on narrowing down directions.

Great job! Some proposals are very nice 👍
@ccordoba12 was open to new ideas, so I'd like to show you the designs I've made. I also propose a new tagline to go with the logo.
Not to mix with existing concepts. I pasted them in the PDF below, concepts 1 to 5.
spyder-logo.pdf
Feedback is important at this stage, so don't hesitate to give your opinion😃

Thanks @maxhaz for your input! We discussed your proposals with the team and have some comments for you:

We value the effort you've put into this. Thanks a lot for taking the time to be part of this process.
Although it's not clear from the comments posted by @isabela-pf, we're very close to propose two new logos for the people that has committed to this repo to decide which one we should use next.
So (unfortunately) your ideas came very late. As you can see from the first comment here, we've been discussing this topic for almost for a year now. Perhaps if you've posted your work some months ago, we could have taken it into consideration.
We've been working very closely with @isabela-pf to preserve the spirit of our previous logo (the colors, the web and the snake/S) in our new one. And her last comment here shows that she's done a superb job at that. Our goal is to have a new logo for next month and sadly we don't have time to iterate over your proposals.

Thanks for understanding and I hope this won't demotivate you from keep contributing to Spyder or other open source projects. For next time, you could try to reach out earlier (a simple comment here saying that you were working on other logos would have been enough).

Thank you @ccordoba12 for your detailed explanations. No worries, I am glad to help, even a bit late 😊
I saw only limited discussion here, I didn't know the discussions occured elsewhere.
Actually, that's the latest rounds of proposals that pushed me to propose some of mines. They are great, kudos to @isabela-pf, however I had a feel that they miss the modern and sleek look that Spyder has. I understand the idea of keeping the spider net is appealing, but it is difficult to make it  looks modern. Again, @isabela-pf did an amazing job to try it to look nice.
If I may say so, maybe using a brighter color palette, and avoiding logo-text integration might help.
Continue the good work and sorry for the interruption 😁

And if you would need a logo for Spyder 6, do not hesitate!

Thanks a lot for your offer @maxhaz! We'll keep it in mind.

I like 1-1 personally. It looks cool and gives visual identity and personality.
Most other propositions either look too corporate to my taste, or just emulate the overused "some shape with a letter" trend.

To keep spyder-ide/ux-improvements#50 clean: Both options have a little problem in the top left corner:

Removing that little web line or moving the convergence point to the corner would help.

@isabela-pf, I've already voted (for 3-16 square), but wanted to thank you for your hard work on the logo; it looks great. While I like the current logo, I think this is an improvement. It is cleaner, spills less ink, and maintains recognizability. Great job!

@isabela-pf: I have a small modification proposition  (on last round logos, for instance 3-16)  that would make it closer to the spirit of the current logo: adding a small snake head to the S.

@ElieGouzien, we tried that but it doesn't look well.

I would like to thank all the work that was put into designing a new logo for Spyder. Redesigning a new logo is a painful process, especially when it is done in the open like that for a beloved open source project. I really like the logo that were proposed for the votes and I can't wait to see the new selected logo on my taskbar! So thank you @isabela-pf  and all the others that contributed in one way or the other to the effort.

Hi @ccordoba12, I suggested a small prettification in the chosen logo in https://github.com/spyder-ide/spyder/issues/13181#issuecomment-851931429, which @isabela-pf :+1:’d, but they didn’t seem to have made it into 82e4cff.
You probably want to fix the logo up before merging spyder-ide/website-spyder#199 and #15980 …

Hey @flying-sheep, thanks for pointing that out. We talked with @isabela-pf and she missed to do that change in PR #15829, so she'll do it in a follow-up PR.

@ccordoba12 I hope Spyder didn't turn from open source to open source project over time. I don't understand how the consensus on changing logo was reached. Can you disclose who and when decided, and what is the result of the voting? Especially interesting to see data with the weighted diagram of votes from https://github.com/spyder-ide/spyder/graphs/contributors

For me the spirit of Spyder was in its custom design that communicated that you can actually patch and modify it yourself. Now that it looks more like Visual Studio, I may as well ask myself, why not just compile a similar, if not a better Spyder, from VS plugins?

There is a repo for UX decision on spyder: https://github.com/spyder-ide/ux-improvements
The voting took place here: https://github.com/spyder-ide/ux-improvements/issues/50
I am answering here as a fellow contributor because I feel that this comment is not particularly empathic or kind. I would like to re-affirm my appreciation for the maintainers who work hard to maintain an open source editor I like and can patch myself. I don't always agree 100% with the design decisions (e.g. https://github.com/spyder-ide/ux-improvements/issues/57) but I feel like the discussion is on the more open and honest side.
Maybe we could have a discussion on governance. I am not sure if https://github.com/spyder-ide/spyder/graphs/contributors is the best way to decide how to weight who should have a say, even if it is an easy to use metric. @ccordoba12 contributes with a lot of commits, but also by commenting on issues, reviewing code, making decisions, and doing many other things.
My personal opinion on this question is that the contributors should have an opportunity to voice their opinions and be heard, but that a BDFL (https://en.wikipedia.org/wiki/Benevolent_dictator_for_life) taking the final decisions is not a bad thing for a small project. The nice feature about open source is that if you believe the maintainers are no longer benevolent, you can fork the project. I know I would not because of the hard work and lack of recognition that comes with being an open-source maintainer.
@techtonik I hope you won't take my comment negatively. I am also thankful to you as you take some time to contribute to open source projects. I just hope this comment will make the world a slightly kinder place.

@impact27 the referenced voting is about which logo to select, not about decision to change the logo.
I appreciate that Spyder is maintained. That goes without saying, but I don't want to hear about benevolent dictators. I am from Belarus and it is a PITA to live in a country where you check when your friends were online last time to know they are not jailed. I can't be positive for a long time, long enough to say negative is my gender. The only problem I have with that is that people are taking it personally. I may be neutral or do not care at all if somebody takes the decision to change the logo if that help to maintain the project further. I just want this decision for an open source project to be clear and open.


Unnecessary display:inline in class .fl-ns and more

When I open up tachyons.css file,
warning message pops:
'Property is ignored due to the display. With 'display: inline', the width, height, margin-top, margin-bottom, and float properties have no effect.'
and it points at:
 .fl-ns { float: left; display: inline; }
 .fr-ns { float: right; display: inline; }
...

Along with .fl-m .fr-m .fl-l .fr-l. To me, it seems display:inline is not necessary.

Might be related to #480


Enable dynamic dispatch for package path manifest loading

This PR elevates the default ManifestLoaderProtocol.load(packagePath... implementation to a protocol requirement, enabling dynamic dispatch for types conforming to the protocol.
Motivation:
The Workspace class provides a convenient way to fine-tune the manifest loading process by allowing the use of custom loaders. For example, RegistryAwareManifestLoader already enables loading manifests from registries. Similarly, it would be beneficial for other Workspace clients to implement their own manifest loaders to address their specific needs (if you'd like, I could go into the details of our specific need, but I believe it might be irrelevant in the context of this PR).
However, one of the default manifest loading implementations used by Workspace (and other clients as well) is not currently reflected in the protocol requirements, making it impossible for implementers to override due to the static dispatch. To address this, I propose elevating the default implementation to a protocol requirement. This would enable dynamic dispatch for this method, providing greater flexibility for Workspace clients.
Modifications:
This PR simply copies the signature of the default method implementation in question to the protocol body, while also fixing some outdated documentation along the way. This modification introduces no interface changes, so no adaptations are required at the calling sites.
Result:
class MyCustomManifestLoader: ManifestLoaderProtocol {

    func load(packagePath: AbsolutePath, packageIdentity: PackageIdentity...) {
        // I'll be called now since I'm already dynamically dispatched.
    }

    ...

}

if you'd like, I could go into the details of our specific need, but I believe it might be irrelevant in the context of this PR

It would definitely be interesting to hear about use cases!

@jakepetroules sure!
Background:
We use some of SwiftPM's data models and tools to precompile our dependency package targets as XCFrameworks, which are later consumed via binary targets from automatically generated mirrored packages. Specifically, we use Workspace to load a package's module graph, which we then use in the PIFBuilder to generate the corresponding PIF file for more direct communication with the underlying XCBuild system.
Additionally, we require that the produced XCFrameworks be compatible with modules built with different Swift versions. To achieve this, we attempt to compile them with module stability enabled by default (and hence library evolution). However, packages that do not support module stability must be precompiled in an unstable, compiler-specific module format. This requires using a specific toolchain (typically in the form of an Xcode bundle) for each supported Swift (and sometimes SDK) version.
Since we need to apply different toolchains to the same package, this can lead to the same package being resolved into different module graphs. This typically occurs when the package has version-specific manifests (where each manifest may define its own set of dependencies). This situation is especially common nowadays as many 3rd party packages are in the process of gradually migrating from Swift 5.x to Swift 6.0
Existing issue and use cases:
Unfortunately, the existing version-specific manifest loading mechanism doesn't allow loading manifests compatible with arbitrary toolchains. As you can see from the logic, the default implementation first always tries to look for version-specific manifests that are compatible with the hardcoded SwiftPM tools version. I'm not sure if there was a specific reason for implementing it this way, but it limits the flexibility of the current loading logic for multi-toolchain scenarios.
For our use case, we need a more flexible implementation where Workspace loads version-specific manifests based on the toolchain version provided dynamically, rather than relying on the hardcoded toolchain version in the currently used SwiftPM instance. I can also imagine other, less straightforward use cases where a manifest loader could generate manifests and the surrounding package structure on the fly to create adapters for non-Swift libraries, but that might be too far-fetched at this point.
Possible solutions:
The good news is that a greater flexibility can be easily achieved by incorporating the changes from this PR. Alternatively, the goal could also be met by modifying the existing loading logic, but that would likely involve a more invasive change, requiring careful examination. In contrast, the proposed solution of enabling dynamic dispatch is simpler and non-disruptive.

@jakepetroules Sorry for the rather long write-up. My main point was that such a small change could enable a lot of flexibility without any visible downsides. Do you think there’s a chance to get it through?

Sorry to bother you. Just a friendly reminder about this PR whenever you have time. If you feel it doesn’t add value, I’m happy to close it to avoid contributing to the number of dangling PRs.


[CHKV] Wrong parameter length in CHKV

Check parameters in CHKV are limited to 30 characters:
https://github.com/SAP/abap-file-formats/blob/c86bd574304508a3c0cb77dd4c4c46b41da80bee/file-formats/chkv/type/zif_aff_chkv_v1.intf.abap#L37
However, parameters of an CHKO can be longer since they are defined as string:
https://github.com/SAP/abap-file-formats/blob/c86bd574304508a3c0cb77dd4c4c46b41da80bee/file-formats/chko/type/zif_aff_chko_v1.intf.abap#L10

Fixed in the definition. See #541.
I keep this open until a SAP Note has been provided.

Fix will be available with SAP Note https://launchpad.support.sap.com/#/notes/3353061


Error using bodyFilter with jsonPath

I'm using logbook version 2.9.0 and I'd like to mask a specific attribute (cpf) in the request and response body. The bean that I created is below:
@Bean
public Logbook logbook() {
   return Logbook.builder()
        .bodyFilter(jsonPath("$.cpf").replace(compile("(\\d{3})(\\d{3})(\\d{3})-?(\\d{2})"), "$1.XXX.$3-XX"))
        .bodyFilter(jsonPath("$.results.client.cpf").replace(compile("(\\d{3})(\\d{3})(\\d{3})-?(\\d{2})"), "$1.XXX.$3-XX"))
        .build();
}

When I make an request with body {"cpf": "21343575698"}, an error occur: "Missing property in path $['results']","trace":"com.jayway.jsonpath.PathNotFoundException: Missing property in path $['results']"
is there something wrong with my configuration?
Thanks a lot.

Are you configuring JsonPath anywhere, outside of the code snippet that you shared?
Can you provide a failing test case, to reproduce this?

For example, you can get error when you us logbook, jsonpathbody filters and spring security

The problem is that Logbook filter after spring security chain try to log request body (but for GET request body is null or empty), so i get exception in jsonpath

This seems to be a bug in the JsonPath-based body filter. Anyone care to create a test to reproduce it?

@tfpolachini As far as my own experience goes with new jsonPath filters i can tell that it still needs some work before it can become usable in real world applications.
Problems:

if parent object (jsonPath("$.a.b")) of filtered path (jsonPath("$.a.b.c")) is null, then com.jayway.jsonpath.PathNotFoundException is thrown
jsonPath filters every Request and Response (with different json bodies), throwing com.jayway.jsonpath.PathNotFoundException (because of previous point)
jsonPath filters every Request and Response, creating potentional performance issues if more filters are applied -> this is due to filters being applied to another http bodies it doesn't belong to, and the filters do empty work most of the time basically

Our use case scenarios:

Filter Requests and Responses based on their Request path, so jsonPath filters are applied only to specific Request path
Filter won't ever fail on com.jayway.jsonpath.PathNotFoundException when filtering json body

I have created implementation tailored to our use case scenarios which also eliminates or mitigates mentioned issues.
@whiskeysierra Maybe i can provide our JsonPathBodyFilters edit as an example, or even some more code.

For example, you can get error when you use logbook, jsonpathbody filters and spring security
Here logbook try to log GET authenticated request

The problem is that Logbook filter after spring security chain try to log request body (but for GET request body is null or empty), so i get exception in jsonpath

This seems at first like a possible nullability issue in JsonPathBodyFilters. But the implementation from what i remember contains a check for json contentType which should result to the filter not being applied when GET request does not have a body. I might check it tomorrow..

@whiskeysierra are jsonpath body filters are still experimental feature or can be used in real time projects?

It looks like the problem of throwing an exception if a path is missing still exists. This prevents valid paths from being parsed and filtered


Calling module.log(...) within a callback fails

🐛 Bug
Calling pl_module.log(...) within a Callback fails, even though this is recommended by the documentation here: https://pytorch-lightning.readthedocs.io/en/latest/loggers.html#logging-from-a-callback
Error
  File "my_callback_file.py", line XX, in on_validation_epoch_end
    pl_module.log_dict(my_metrics_dict)
  File "/home/local/USHERBROOKE/pain5474/opt/miniconda3/envs/cav/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 287, in log_dict
    self.log(
  File "/home/local/USHERBROOKE/pain5474/opt/miniconda3/envs/cav/lib/python3.8/site-packages/pytorch_lightning/core/lightning.py", line 233, in log
    self._results.log(
  File "/home/local/USHERBROOKE/pain5474/opt/miniconda3/envs/cav/lib/python3.8/site-packages/pytorch_lightning/core/step_result.py", line 171, in log
    self.__set_meta(
  File "/home/local/USHERBROOKE/pain5474/opt/miniconda3/envs/cav/lib/python3.8/site-packages/pytorch_lightning/core/step_result.py", line 217, in __set_meta
    _internal = self['meta']['_internal']
KeyError: '_internal'
python-BaseException

cc @nathanpainchaud
This is happening on master
Expected behavior

We can log from callbacks using the lightning module
Environment
Happening on PyTorch Lightning master

@ananthsub I just tried on master and cannot reproduce (I think it was solved yesterday, as I could reproduce 2 days ago).

@SkafteNicki The issue was created by @ananthsub based on a question/issue I initially raised in the slack. I'll try to see if the bug is now resolved on master for me (it was still present as of yesterday afternoon) and I'll update you here as soon as I can.

Hey @nathanpainchaud,
Did you manage to reliably reproduce this behaviour? And if yes, could share the draft PR associated with this issue ?
I will try to try it out too.
Best regards,
Thomas Chaton.

Hey @tchaton,
Thanks for the follow up! I opened the draft PR where I added a test that reproduces the behavior I'm getting.
If I can help in any other way to get this sorted, just let me know!

@tchaton Any updates on whether this is a feature that's planned to be supported, or on the contrary it's been abandoned? I'm only asking this question because the issue has been labelled priority for a while, but every PR referring to it have been closed without getting merged :laughing:

Yes! thats been worked on these weeks. Starting to be merged now (https://github.com/PyTorchLightning/pytorch-lightning/pull/4439)

I still have problems logging my validation metrics using pl_module.log() in the on_validation_end() hook. Any thoughts?


feat:msg support concurrent

https://github.com/dtm-labs/dtm/issues/207

Codecov Report

Merging #234 (91ba06e) into main (416b982) will decrease coverage by 0.34%.
The diff coverage is 93.18%.

@@            Coverage Diff             @@
##             main     #234      +/-   ##
==========================================
- Coverage   97.25%   96.91%   -0.35%
==========================================
  Files          48       48
  Lines        2623     2688      +65
==========================================
+ Hits         2551     2605      +54
- Misses         42       50       +8
- Partials       30       33       +3

Impacted Files
Coverage Δ

dtmcli/dtmimp/trans_base.go
94.28% <ø> (ø)

dtmsvr/trans_type_msg.go
90.47% <92.30%> (+2.24%)
:arrow_up:

dtmcli/saga.go
100.00% <100.00%> (ø)

dtmgrpc/saga.go
100.00% <100.00%> (ø)

dtmsvr/trans_status.go
92.36% <0.00%> (-4.07%)
:arrow_down:

dtmsvr/trans_type_saga.go
95.80% <0.00%> (-1.40%)
:arrow_down:

dtmsvr/api_json_rpc.go
100.00% <0.00%> (ø)

Continue to review full report at Codecov.

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

go.sum里面有大量的修改，能否撤销掉？

已经撤销了


LinkingIOS docs should be updated

Took a half hour of digging around the net to figure out you need to do 1-3 manual steps on this page before you can effectively follow the docs for LinkingIOS. I recommend updating the LinkingIOS docs to make this clearer.

PRs are welcome.

Please send a pull request.


Current selendroid-standalone-0.15.0-with-dependencies.jar is corrupt

Hitting my head against the wall for a few hours to resolve this, and it seems that it is indeed corrupt.
Downloading version 0.140 from Maven works fine
Environment:
Mac OSX Yosemite 10.10.3
Java: 1.8
Kept giving me this when running java selendroid-standalone-0.15.0-with-dependencies.jar as per the documentation.
Error: Could not find or load main class selendroid-standalone-0.15.0-with-dependencies.jar
Download 0.14.0 from Maven here

you need to pass in -jar too
java -jar selendroid-standalone-0.15.0-with-dependencies.jar

Well I'm retarded, thanks for the fast response :+1:


Set up Storybook

Overview
Closes #56
Installed a set up storybook for the site header, site footer, and content area components.
What Changed
Addition of three storybook.tsx files for the three respective components and addition of storybook dependencies.
Other Notes
The stories don't render the components, even if the story is exporting only the default component. The templates for each story can be modified to document their states or behaviors and will prove useful as we move forward but I only have the default ones set up.

It appears this branch used the main branch as the base for the code instead of the develop branch. Could you do the following:

Close this PR
Clone the survival-guide repository in a new directory using git clone
In this cloned repository, from the develop branch (by running git checkout develop), create a new branch for your Storybook changes by running git checkout -b internal/storybook-setup`
Copy the Storybook changes from the old project folder to the new one
Commit the changes in the new project folder
Open a new PR with the internal/storybook-setup branch as the base

Additionally, before running the above commands, you may want to update your email and name on Git by following this guide so you get GitHub credit for contributing.


Fix CairoMakie heatmap filtering

Description
Heatmap filtering was broken again because it used Cairo.FILTER_BEST, which does nothing in bitmap backends. This PR fixes that and reorders the logic a bit, so it should be easier to follow why the surface or rectangle path is chosen.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

Checklist

[x] Added unit tests
[ ] Added reference image tests for new plotting functions, recipes, visual options, etc.

Compile Times benchmark
Note, that these numbers may fluctuate on the CI servers, so take them with a grain of salt.
using time
master:  10.99 < 11.10 > 11.27, 0.10+-
pr:      9.93 < 11.12 > 11.21, 0.45+-
speedup: 0.99 < 1.00 > 1.11, 0.04+-
median:  +0.16% => invariant

This PR does not change the using time.
ttfp time
master   27.78 < 27.95 > 28.47, 0.24+-
pr       24.96 < 27.91 > 28.36, 1.18+-
speedup: 0.99 < 1.00 > 1.11, 0.04+-
median:  -0.15% => invariant

This PR does not change the ttfp time.


pyanalyze doesn't propagate initialisation through conditions involving walrus

import os

def info(arg: str):
    if arg and (var := os.environ.get("ENV")):
        raise RuntimeError(f"{arg}: {var}")

gives me:
λ pyanalyze b.py

var may be used uninitialized (code: possibly_undefined_name)
In b.py at line 6
   3:
   4: def info(arg: str):
   5:     if arg and (var := os.environ.get("ENV")):
   6:         raise RuntimeError(f"{arg}: {var}")
                                           ^

Duplicate of #597
Thanks for these issues, I'll try to find some time to work on them


urxvt: add module

Will be happy to get a feedback on these options specifically:

scroll.keepPostion
scroll.downOnInput
scroll.downOnOutput

Are they understandable, or maybe it's better to keep urxvt names?

Yep, looking good! 🙂
Rebased to master in c17f37857cdb134f8ffbf5e2ee8c8ab317136e0f. I updated the news timestamp and changed the programs.urxvt.keybindings option to use literalExample to prettify the documentation.


Maximum message size exceeded on su in python3.7.1

Trying to use router.su  leads me to the following error message on python 3.7.1:
E mitogen: Maximum message size exceeded (got<PHONE_NUMBER>, max 134217728)
I tested against 0.2.0, 0.2.1, 0.2.2, 0.2.3 from pypi, and the current master branch (22de7f0), all with the same result. On python version 2.7.15 the same code does not through this error (only tested against 22de7f0).
su from util-linux 2.33 and kernel 4.19.4.arch1-1.
Code used:
import mitogen.utils
import getpass

mitogen.utils.log_to_file()
@mitogen.utils.run_with_router
def main(router):
    router.enable_debug()
    router.su(username="syntonym", password=getpass.getpass())

Looks like somehow something is printing into the stream past the point where it should exclusively be used by the parent and child.<PHONE_NUMBER> in hex is 0x696f6e57, which is ASCII, "ionW".
Can you recognize that string? It might be printed perhaps by something imported by sitecustomize.py, usercustomize.py, or perhaps it is a PAM module invoked by su or similar.
Since bootstrap is completed, it seems more likely the corruption is by something within the Python interpreter, rather than PAM or bash or something.
Regardless, this is a bug because that error could be improved. It is a simple matter to include, say, 2 signature bytes in every message, and if they are incorrect, produce a more descriptive error message including a dump of whatever string was actually received.
Thanks for reporting this!

Grepping /usr/lib/python3.6, I see "ionW" appears a lot in "DeprecationWarning" :) I will test more locally, looks like it is definitely a Mitogen issue

I've got an Arch VM matching yours and I cannot reproduce this deprecation warning :S  Does the target or source user have some bashrc perhaps, that sets some environment variables?
I'm thinking perhaps the warning is relating to a locale setting in the environment, i.e. LC_ALL, LANG etc., or some similar mechanism

possibly related: #399

I managed to reproduce it. It is indeed due to #399, and it only impacts su because su redirects its stderr into stdout in order to cope (IIRC) with FreeBSD.

This is now on the master branch and will make it into the next release. To be updated when a new release is made, subscribe to https://www.freelists.org/list/mitogen-announce
I will open a separate ticket to improve the stream corruption error messages.
Thanks for reporting this!

I tested the current HEAD version and can confirm that the bug is fixed.
Thanks for the super quick bugfix! I did not expect such a quick answer, let alone a fix.


When I try to add an LDAP user as admin, the permissions do not save.

Attempted Debugging

[X] I have read the debugging page

Searched GitHub Issues

[X] I have searched GitHub for the issue.

Describe the Scenario
When I try to add an LDAP user as admin, the permissions do not save.
I change the .env (AUTH_METHOD=standard), then as admin.
I add my LDAP user as admin and save the page.

But when the user connects the application he loses the permissions.

In my tests, the user only loses permission when logging into the application.
If I grant him permission, and he is logged in, he has admin permission until he logs out
Exact BookStack Version
v24.05.2
Log Content
No response
Hosting Environment
Oracle Linux

Hi @silvaguilherme,
I'm guessing you have the following option and values set:
LDAP_USER_TO_GROUPS=true
LDAP_REMOVE_FROM_GROUPS=true

In which case I'd expect the user to lose their admin role upon login unless this was mapping to a group in the LDAP system. If you intend for role assignments to remain, and not be removed by the LDAP group sync handling, you should set LDAP_REMOVE_FROM_GROUPS to false.

It worked
Thanks

Good to hear! Will therefore close this off.


Update list-tenantsettings.md

Updated the BAP Api description for power catalog setting to mark that this setting is for the future use and that there is no enforcement driven by this setting at the current time

Closing this in favor of https://github.com/MicrosoftDocs/power-platform-pr/pull/6675


[Communication] Sms redesign new

Support for creating SmsClient with TokenCredential.
Added support for 1:N SMS messaging.
Added support for tagging SMS messages.
Send method series in SmsClient are idempotent under retry policy.

A few things that I think architects will have an issue with:

Our async and sync client methods do not have "withResponse" variations on the max overload.
All sycn client methods should have an overload that takes in Context. Usually this is in the "withResponse" variation.

Let's try to fix this before the final review to ensure we have enough time.
cc: @ankitarorabit


Rectangular decomposition: Identity fix

Context:
Currently, the rectangular decomposition is such that the identity matrix is implemented as a series of swaps. While this still gives the correct unitary, it is harder to implement on the hardware.
Description of the Change:
With this modification, the identity is decomposed such that there are no unnecessary swaps.
Benefits:
Easier to implement on hardware.
Possible Drawbacks:
Related GitHub Issues:
N/A

Thanks @shreyapkumar!

@lneuhaus it would be great to get your review on this, as the original decomposition author!
@shreyapkumar: can you also update the .github/CHANGELOG.md file, with a brief description of the change in the Improvements section, as well as a link back to this PR, and adding in your name in the contributors section 🙂

@lneuhaus it would be great to get your review on this, as the original decomposition author!

I only added the rectangular_symmetric depomposition, the other ones were written by @ishdhand I believe.

I only added the rectangular_symmetric depomposition, the other ones were written by @ishdhand I believe.

Oops! Have added Ish. Feel free to review if you would like 🙂

In fact, looking at git blame, it seems like you implemented the original decompositions yourself in #7 @josh146 😄

🤦♂

Added the description to CHANGELOG.md. Thanks, @josh146  and @lneuhaus !

Was the updated changelog successfully committed/merged? I don't see it in this PR :thinking:

Answering my own question: looks like the changelog update was added in a separate PR (#313).
@shreyapkumar For easier bookkeeping, and to save yourself and code reviewers extra effort,, simpler to keep changelog updates in same PR as the changes that are made :+1:

Thanks, will do that the next time, @co9olguy !  Wasn't able to figure out how to add to the same PR this time 🙈


Task1_REF

@ramyarpa
Task-1
Add data to Queue  use RE
Code verified.
Task -2
Data base
Code verified.


Fix cache invalidation in getCachedExistingRecords() method in nesting repeater component

The Repeater component's getChildComponentContainers() method returns a list of components by calling the getClone() method, which produces entirely new clone objects each time. As a result, the getCachedExistingRecords() method of all non-top-level Repeater components will always select DB because the cachedExistingRecords property remains unset.

Description
Many internal methods, such as getValidationRules(), getValidationMessages(), and getValidationAttributes(), also call getChildComponentContainers(). Each time these methods are invoked, they query the database and cache the results in a new object's cachedExistingRecords property. The getClone() method causes the getCachedExistingRecords() method to lose its original design purpose within nested components.
Visual changes
form ui

show edit page

before save

now save

Functional changes

[ ] Code style has been fixed by running the composer cs command.
[ ] Changes have been tested to not break existing functionality.
[ ] Documentation is up-to-date.

Sorry, I don't think we can do this, it would break on Octane for sure which might even be a security issue if there is data leakage between requests


[Quest] Load Form configuration from Binary resource

Description
Dynamically load and configure the app Form configuration using the Binary resource that will hold the information about the different Form configurations to be used in the configurable Quest application. This will define the Forms & Title to be presented to the user at each workflow user interaction point
Feature
Load & Sync the Binary resource from HAPI FHIR Server and not locally loaded from assets Folder
Sample Form Configuration
[
  {
    "appId": "anc",
    "form": "anc-patient-registration",
    "title": "Enroll as ANC Patient",
    "identifier": "1924"
  },
  {
    "appId": "anc",
    "form": "family-member-registration",
    "title": "Add Family Member",
    "identifier": "32821"
  },
  {
    "appId": "anc",
    "form": "non-anc-patient-vital-signs_metric",
    "title": "Add Vital Signs ",
    "identifier": "1921"
  },
  {
    "appId": "anc",
    "form": "non-anc-patient-vital-signs_standard",
    "title": "Add Vital Signs ",
    "identifier": "2007"
  },
  {
    "appId": "anc",
    "form": "family-registration",
    "title": "Add Family",
    "identifier": "32822"
  },
  {
    "appId": "anc",
    "form": "family-patient_bmi_compute",
    "title": "Compute BMI",
    "identifier": "1999"
  },
  {
    "appId": "ecbis",
    "form": "anc-patient-registration",
    "title": "Enroll as ANC Patient",
    "identifier": "1924"
  },
  {
    "appId": "ecbis",
    "form": "family-member-registration",
    "title": "Add Family Member",
    "identifier": "82953"
  },
  {
    "appId": "ecbis",
    "form": "non-anc-patient-vital-signs_metric",
    "title": "Add Vital Signs ",
    "identifier": "1921"
  },
  {
    "appId": "ecbis",
    "form": "non-anc-patient-vital-signs_standard",
    "title": "Add Vital Signs ",
    "identifier": "2007"
  },
  {
    "appId": "ecbis",
    "form": "family-registration",
    "title": "Add Family",
    "identifier": "82952"
  },
  {
    "appId": "ecbis",
    "form": "family-patient_bmi_compute",
    "title": "Compute BMI",
    "identifier": "1999"
  }
]

NOTE: The current configs are available in the assets directory. They were missed during the refactor to use downloaded Binary resource configurations. Move the sample form configuration to the resource directory where we store other sample view configurations.

I think this issue has been properly scoped. Will add some comment if anything new came up.
Working on this

Is this using a binary resource so that we can use arbitrary JSON?

Yes this should use a binary resource

Marking this ticket as DONE

Needed for ECBIS app

Functionality merged through another branch. Closing this.


Differentiate matrix/vector accessing vs assigning

Great!
Lets see what travis says and merge

The java error can be changed via making the false a 0, I think

Ill merge this and do the remaining fixes myself


command: URIs in trusted MarkdownString values in TreeItem tooltips don't execute commands.

Version: 1.56.0-insider (user setup)
Commit: 4e185d8986339717e593be19bc75288905ffbb51
Date: 2021-05-01T00:27:57.510Z (1 wk ago)
Electron: 12.0.4
Chrome: 89.0.4389.114
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043
Steps to Reproduce:

Register a custom command (for example: myextension.test).
Create a VS Code extension with a custom TreeDataProvider, registered as a contribution in package.json.
Implement TreeDataProvider.getChildren and TreeDataProvider.getTreeItem to provide a single TreeItem.
For the provided TreeItem, set the tooltip using the following example:const mdString = new MarkdownString("[Execute Command](command:myextension.test)");
mdString.isTrusted = true;
const treeItem = new TreeItem("label");
treeItem.tooltip = mdString;

Launch VS Code with the custom extension. In the custom tree view, hover over the tree item.
Observe that the Markdown link Execute Command is hyperlinked, but clicking on the link does not execute the command.

This differs from how trusted markdown in a hover or decoration treats command links when the markdown is trusted.

Does this issue occur when all extensions are disabled?: Yes

Looks like by default command links aren't supported in the hover widget.

I thought that was the point of the .isTrusted property on MarkdownString. I know that it works when creating hovers in a hover provider.


Fix configure-simulators workflow not setting google_cloud_project.

This was missed in #1501.

This change is


chore(main): update CI to ignore checks in audit files

Description
This PR makes changes to the typo checking setup by adding the external audits folder "packages/protocol/audit/**" to the exclude list, otherwise these will be flagged in every PR as in #16652.
I'm assuming it's better not to fix typos in the audit files because altering them could compromise their (legal?) integrity, and those typos don't show up in any of the products or docs.

this has already been done in a PR that was merged, but thank you!


chore: fix key

This pr is intended to fix a minor translation key error

closed due to regularisation issues


add test for structured tools

This looks good, I started working on separate code will try to push on Monday to populate required field which is useful to have.
I think we also need to expose another parameter in the function classmethod to allow a user to provide per argument doc-strings


Download XLS file - 00hours fix

https://3.basecamp.com/3198361/buckets/3856681/todos/5428757854#__recording_5594800939

@AOneP Please open PR to trmz repo with updated gem


[Improvement]:  Improve completion for constant

Description
Issue 1:
public const int varName = <cursor>
After this fix #39589, the type of varName will be singleton type inferred from constant expression but in the current master it sets as int. Now this will return type of varName as compilation error.
Pls refer this completion change https://github.com/ballerina-platform/ballerina-lang/blob/84c2c52341df79ea50fc39e953763ebb18409c8a/language-server/modules/langserver-core/src/test/resources/completion/module_const_context/config/config6.json#L195
https://github.com/ballerina-platform/ballerina-lang/pull/39589#discussion_r1187552613
Issue 2:
const int OIL_PRICE = 10.0;
the type of OIL_PRICE will be singleton type 10.0. So it suggesting to change expected type to 10.0. Previously it suggested float. This has to be same as current master behaviour to improve user experience.
I have commented the test in #39589
https://github.com/ballerina-platform/ballerina-lang/blob/810fa3ab5cab723c99ece8916ecb834fb8a4a068/language-server/modules/langserver-core/src/test/java/org/ballerinalang/langserver/codeaction/ChangeVariableTypeCodeActionTest.java#L62
Steps to Reproduce
No response
Affected Version(s)
No response
OS, DB, other environment details and versions
No response
Related area
-> Editor
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

Fixed in https://github.com/ballerina-platform/ballerina-lang/pull/40663


Timestamps do not make sense

Hello,
I am trying to retrieve BSR (Seller Rank) history for a list of ASINs, but the timestamps provided and a few other datapoints do not make sense.
Here is my code:
import keepa
import asyncio

accesskey = 'xxx' # enter real access key here
api = keepa.Keepa(accesskey)

asins = ['B07P7QDJZX',
         'B076DK947N',
         'B076C164HD',
         'B01MRGIZE9',
         'B072Z4SBN9']

product = api.query(asins, offers=20, stats=90)

product[0]['salesRanks']

Here is a screenshot of the output:

My questions are:

What is the value "914434" referring to? Is it a category group number? If so, how can I find the category name?
How do I interpret the timestamp 4828968 into an actual date/time? I have tried unix converters but I am getting 1970 as the year associated with this time stamp, which is definitely wrong. Any help here?

Hello,

914434 is indeed a category number.  You can look up the corresponding information with:

>>> api.category_lookup(914434)
{'914434': {'domainId': 1,
  'catId': 914434,
  'name': 'Thermal Carafes',
  'children': [],
  'parent': 289743,
  'highestRank': 14197176,
  'productCount': 8422,
  'contextFreeName': 'Thermal Carafes',
  'lowestRank': 3296}}

The timestamps are the number of minutes from "KEEPA_ST_ORDINAL" which is 01-01-2011.  You can convert these times with:

>>> from keepa.interface import keepa_minutes_to_time
>>> keepa_minutes_to_time(4828968)
datetime.datetime(2020, 3, 7, 10, 48)

Hello,

914434 is indeed a category number.  You can look up the corresponding information with:

>>> api.category_lookup(914434)
{'914434': {'domainId': 1,
  'catId': 914434,
  'name': 'Thermal Carafes',
  'children': [],
  'parent': 289743,
  'highestRank': 14197176,
  'productCount': 8422,
  'contextFreeName': 'Thermal Carafes',
  'lowestRank': 3296}}

The timestamps are the number of minutes from "KEEPA_ST_ORDINAL" which is 01-01-2011.  You can convert these times with:

>>> from keepa.interface import keepa_minutes_to_time
>>> keepa_minutes_to_time(4828968)
datetime.datetime(2020, 3, 7, 10, 48)


SP5: signal plots with repeating values

when a signal plot flips into high density mode, a line is not rendered if its min and max values are equal

resolved in #2935


[DRAFT][PROPOSAL] Beginning of e2e for POST endpoints

This PR is a first draft to test POST endpoints end to end by calling handlers and giving relevants Request and Ctx, calling supabase and stripe, to ensure that they works from start to finish.

Add a folder e2e containing test with current fresh limitation (cannot instantiate a fresh server programmatically on a random port)
Create test:e2e task to run test from e2e folder with RESETING SUPABASE DB + RESTART SUPABASE
Add utils functions to delete all items and all users (to cleanup after tests)
Cleanup stripe customers after tests
Add typing in auth.ts
Returns 201 on successful POST on handler in signup.tsx and submit.tsx
Call load from std/dotenv at the beginning of stripe utils file to prevent weird race condition while running tests where when calling load in tests file before importing any other file will still result in stripe utils file to be loaded BEFORE the load call.

Hi @Sorikairox, I suggest pausing adding any more to this PR. Auth will soon use Deno KV instead of Supabase Auth. My initial thoughts are I wouldn't want you to put any further work into a feature that will soon be dropped.
Nevertheless, I like the direction of some of these changes! I'll do a proper review soon.

Also, please don't forget to run deno task ok before committing 😄

@iuioiua I fixed it so deno task ok passes now !

Deno KV OAuth is now implemented. I've changed the branch to be merged to supbase-auth, where the Supabase Auth implementation now lives.


YMT selects wrong time periods

'ymt list receipts' and 'ymt describe' selects wrong time periods.

fixed


Use calloc for ALLOCATE (the memory is set to zero)

This can avoid a Segmentation fault when calling FREE, for example in vkDestroyDescriptorPool() if bufferDescriptorCPA has not been yet allocated.
Nicolas Caramelli

sounds like a good debug option, I like it. I'd not merge it for release though

As you prefer, but this change is required for the triangle test to work on my system. Otherwise the triangle test can also be modified like proposed in https://github.com/Yours3lf/rpi-vk-driver/pull/30
Nicolas Caramelli

do you mean there's an issue if you don't zero out memory? sounds like you found a bug

Yes exactly, this is what I see in vkDestroyDescriptorPool() if bufferDescriptorCPA.buf has not yet been initialized to zero with the ALLOCATE in vkCreateDescriptorPool().
In the triangle test, a descriptor pool for VK_DESCRIPTOR_TYPE_STORAGE_TEXEL_BUFFER and VK_DESCRIPTOR_TYPE_COMBINED_IMAGE_SAMPLER is created, so imageDescriptorCPA.buf and texelBufferDescriptorCPA.buf are valid. But this is not the case for bufferDescriptorCPA.buf.
Nicolas Caramelli


Banished glitches everywhere

Software information
Game: Banished
Version: 1.0.7 build 170910
System information

GPU: GTX 650
Driver: 390.25
Wine version: stagging 3.4
DXVK version: f1c3b59e87746f56f1956bfa54b9403d0e5317b1

Apitrace file(s)

Banished.7z

Log files

d3d11.log
dxgi.log
terminal.log
tracing.log

Screenshots

Game zoom in

Note: game works fine without using dxvk

Can't reproduce, your trace replays just fine here. Probably the same issue as #139, which might be a driver issue.

Can confirm that it works fine on my side.
GPU: GTX 970
Driver: 390.42
Wine version: staging 3.4
DXVK version: b33edcbb93954814ff0091d643d8ae6525b1018d

Please re-test with 42d49d7603401d662153b9fc4d94917f62c2bd92.

Final Fantasy X HD had similar graphical issues that seem to have been solved by https://github.com/doitsujin/dxvk/commit/42d49d7603401d662153b9fc4d94917f62c2bd92. Unfortunately I can't test it very extensively because of #187.

@doitsujin 42d49d7603401d662153b9fc4d94917f62c2bd92 fixes it.


Fix and document support for dask.distributed

Prior to this, using dask.distributed did not work, failing with an error about serialization
I've documented the correct way to use dask.distributed (the scheduler has to be explicitly set to the client) and fixed the serialization bugs.

Codecov Report

Merging #712 (bba95ff) into master (3d153ec) will decrease coverage by 0.08%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master     #712      +/-   ##
==========================================
- Coverage   76.32%   76.23%   -0.09%
==========================================
  Files          24       24
  Lines        5423     5425       +2
==========================================
- Hits         4139     4136       -3
- Misses       1284     1289       +5

Impacted Files
Coverage Δ

spectral_cube/dask_spectral_cube.py
84.84% <88.88%> (+0.24%)
:arrow_up:

spectral_cube/lower_dimensional_structures.py
78.58% <0.00%> (-1.18%)
:arrow_down:

Continue to review full report at Codecov.

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

I tried this and got spectacular errors:
$ ipython /orange/adamginsburg/ALMA_IMF/reduction/analysis/fullcube_quicklooks.py
Logging to /blue/adamginsburg/adamginsburg/slurmjobs/ipython_log_2021-05-06.py
[TerminalIPythonApp] WARNING | Config option `ignore_old_config` not recognized by `TerminalIPythonApp`.
Activating auto-logging. Current session state plus future input saved.
Filename       : /blue/adamginsburg/adamginsburg/slurmjobs/ipython_log_2021-05-06.py
Mode           : append
Output logging : False
Raw input log  : False
Timestamping   : False
State          : active
/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/IPython/core/magics/logging.py:130: UserWarning: Couldn't start log: Log file is already active: /blue/adamginsburg/adamginsburg/slurmjobs/ipython_log_2021-05-06.py
  warn("Couldn't start log: %s" % sys.exc_info()[1])
 Logging to /blue/adamginsburg/adamginsburg/slurmjobs/ipython_log_2021-05-06.py
Beginning imports
Completed imports
Imported pylab
pbar is <dask.diagnostics.progress.ProgressBar object at 0x2ae272946f28>
Beginning imports
Beginning imports
Beginning imports
Completed imports
Imported pylab
pbar is <dask.diagnostics.progress.ProgressBar object at 0x2b7567d587b8>
Completed imports
Imported pylab
pbar is <dask.diagnostics.progress.ProgressBar object at 0x2b5f9ae59828>
Completed imports
Imported pylab
pbar is <dask.diagnostics.progress.ProgressBar object at 0x2b14c843f7b8>
/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/node.py:155: UserWarning: Port 8787 is already in use.
Perhaps you already have a cluster running?
Hosting the HTTP server on port 42652 instead
  http_address["port"], self.http_server.port
Task exception was never retrieved
future: <Task finished coro=<_wrap_awaitable() done, defined at /orange/adamginsburg/miniconda3/lib/python3.7/asyncio/tasks.py:596> exception=RuntimeError('\n        An attempt has been made to start a new process before the\n        current process has finished its bootstrapping phase.\n\n        This probably means that you are not using fork to start your\n        child processes and you have forgotten to use the proper idiom\n        in the main module:\n\n            if __name__ == \'__main__\':\n                freeze_support()\n                ...\n\n        The "freeze_support()" line can be omitted if the program\n        is not going to be frozen to produce an executable.')>
Traceback (most recent call last):
  File "/orange/adamginsburg/miniconda3/lib/python3.7/asyncio/tasks.py", line 603, in _wrap_awaitable
    return (yield from awaitable.__await__())
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/core.py", line 305, in _
    await self.start()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/nanny.py", line 295, in start
    response = await self.instantiate()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/nanny.py", line 378, in instantiate
    result = await self.process.start()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/nanny.py", line 575, in start
    await self.process.start()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/process.py", line 33, in _call_and_set_future
    res = func(*args, **kwargs)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/site-packages/distributed/process.py", line 203, in _start
    process.start()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/process.py", line 112, in start
    self._popen = self._Popen(self)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/context.py", line 284, in _Popen
    return Popen(process_obj)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 32, in __init__
    super().__init__(process_obj)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/popen_fork.py", line 20, in __init__
    self._launch(process_obj)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/popen_spawn_posix.py", line 42, in _launch
    prep_data = spawn.get_preparation_data(process_obj._name)
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 143, in get_preparation_data
    _check_not_importing_main()
  File "/orange/adamginsburg/miniconda3/lib/python3.7/multiprocessing/spawn.py", line 136, in _check_not_importing_main
    is not going to be frozen to produce an executable.''')
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()

I think this means it doesn't want me spinning up a session from an existing one; it's not clear you can use LocalCluster or any distributed client from an already-created cluster

@keflavich - known limitation of dask.distributed (will find link later) - you need to put the code in your script inside an:
if __name__ == '__main__':
     ...

clause. Any luck?


157996116 A logged in user can logout

What does this PR do?
Allows a logged in user to logout.
Description of Task to be completed?

User logout.
Blacklisting the JWT Token token assigned during login.

How should this be manually tested?
$ git clone https://github.com/dalaineme/m-tracker.git

$ cd m-tracker

Create a virtual environment
$ python3.6 -m venv venv

Activate a virtual environment
$ source venv/bin/activate

Install project dependencies
$ pip install -r requirements.txt

Run the server
$ python run.py

Using postman, send a post request to the URL _http://<IP_ADDRESS>:5000/api/v1/users/logout_
Refer to the screenshots below.
Any background context you want to provide?
Authorization header MUST be provided
What are the relevant pivotal tracker stories?
https://www.pivotaltracker.com/story/show/157996116
Screenshots
Successful logout.

Wrong logout request.

Pull Request Test Coverage Report for Build 27

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 25:
0.0%

Covered Lines:
141

Relevant Lines:
141

💛  - Coveralls


Visual View Note Selection Doesn't Work

Describe the bug
It's impossible to select the notes in the visual view to open them in the note editor.
To Reproduce
Steps to reproduce the behavior:

Go to the visible view
Click on a note
Try to click the "Open in Editor" button
It says that you must select a note first.

This also effects the ability to inflate selection by 10% since you can't make any selection.
Expected behavior
You can select and open a note.
Screenshots
Desktop (please complete the following information):

OS: Ubuntu 20.04
Browser Brave
Version 1.57.47

Additional context
I really love the idea and simplicity of this app. I might help contribute if I keep using it and find time. :)

Thank you for the report! I appreciate your interest in NENO!
Selecting nodes is possible by pressing+holding the S key and clicking on one or more notes. This is also mentioned in the user manual: https://github.com/SebastianZimmer/neno/blob/main/docs/GraphView.md#selecting-nodes
But I admit that the way this works is not intuitive. There might be a better solution.

Ah, OK, thanks! Maybe right-click could select nodes. That'd be super easy to discover while trying to click on them.

Visual view has been removed in NENO v7 as the UX was not on a par with the rest, to improve performance, and for the app to have a stronger focus on note editing. It rather should be implemented as a standalone app.


Improve local cache

Addresses comments for #10748

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8203/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8218/
Test FAILed.

jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8224/
Test PASSed.

alluxio-bot, merge this please.


Support new modular libvirt daemons

Provider and libvirt versions
$ terraform-provider-libvirt -version
0.7.1

libvirt 9.5.0

Description of Issue/Question
Setup
There's a new modular architecture for the libvirt daemons that's not supported by this provider.
Steps to Reproduce Issue
There is no longer a /var/run/libvirt/libvirt-sock with this setup, so any attempt to use the provider via the unix socket fails.

Actually there's now virtproxyd as described here that provides the old socket. It works after enabling that socket and service!

Just stumbled upon this. In your case, this is valid as you like to connect via SSH. But enabling the proxy on local machine just to use this provider seems like an ugly workaround.
So this would be nice to have without the proxy workaround.

@kastl-ars I don't know, I think it's not really a workaround, it's the official way to get a socket interface

@kastl-ars I don't know, I think it's not really a workaround, it's the official way to get a socket interface

Hi @michaelbeaumont
the documentation says this:

If connections from remote hosts need to be supported the proxy daemon must be enabled and started

This explicitly mentions "remote hosts". That is way I called it a workaround.
Local connections using virsh are working even with the proxy daemon disabled, as there are lots of sockets available. My guess is that the libvirt provider "just needs to be told" to look in a different place for the socket...

I'm not enough of an expert in libvirt here but from my understanding, the issue is that there are multiple sockets now. Is it clear that we only need say, the qemud socket? I don't know. Also we'd need https://github.com/digitalocean/go-libvirt/issues/171 anyway, because the API calls happen in go-libvirt.


YWHB

Use the preview tab to see the example given below. Edit the relevant information and preview the changes before submitting. You may delete these instructions.

Key
Value

ID
YWHB

Source
Vaaran Bhai Gurdas Ji

Page
20

Line
gur isK suix gurisK, isKu sdwieAw [

Correction
THIS ≠ THAT

PROOF (EDITION)
Image:

The issue between the database and the proof is not apparent


Does Comment Anchor support VS 2017?

I could not find this in the documentation. It does not install on my system.
If it does not support, can it be made to support it?
VSIXInstaller_61b4d8d2-8970-4cf6-a7a4-071263444a7e.log

Comment Anchors is an extension for Visual Studio Code and as far as I know Visual Studio offers no compatibility at this time.

I interpret "Comment Anchors is an extension for Visual Studio Code and as far as I know Visual Studio offers no compatibility at this time." as double talk. Unless Visual Studo Code and Visual Studio are somehow different things, this makes no sense. If you provide a VSIX installer, then it is "for" Visual Studio - saying Visual Studio "offers no compatiblity" sounds like VS is not compatible with Comment Anchor, but it must be the other way around?

Visual Studio, the IDE, and Visual Studio Code, the code editor, are two completely different projects and besides sharing the same packaging format (VSIX, as they are both Microsoft projects), they share no extensions in common. The reasoning behind reusing the VSIX format is unknown to me and questions regarding it should be directed at Microsoft, not Comment Anchors.


NNVM suport for keras resnet50

keras_net = keras.applications.resnet50.ResNet50(include_top=True, weights=None,
input_shape=(224, 224, 3), classes=1000)
keras_net.load_weights('resnet50_weights.h5')
sym, params = nnvm.frontend.from_keras(keras_net)
sym = nnvm.graph.create(sym)
sym = vta.graph.clean_cast(sym)
sym = vta.graph.clean_conv_fuse(sym)
The error is reported:
Traceback (most recent call last):
File "resnet.py", line 244, in
device)
File "resnet.py", line 151, in generate_graph
sym = vta.graph.clean_cast(sym)
File "/home/nishome/lwzhang/tvm/vta/python/vta/graph.py", line 192, in clean_cast
elif op_name == "conv2d" and attrs["out_dtype"] == "int32":
KeyError: 'out_dtype'
Traceback (most recent call last):
File "_ctypes/callbacks.c", line 234, in 'calling callback function'
File "/home/nishome/lwzhang/tvm/python/tvm/_ffi/_ctypes/function.py", line 28, in _ctypes_free_resource
TypeError: 'NoneType' object is not callable
Traceback (most recent call last):
File "_ctypes/callbacks.c", line 234, in 'calling callback function'
File "/home/nishome/lwzhang/tvm/python/tvm/_ffi/_ctypes/function.py", line 28, in _ctypes_free_resource
TypeError: 'NoneType' object is not callable
I print the sys.ir(), the conv2d node:
%4 = conv2d(%1, %_param_1, %_param_2, use_bias='True', dilation='[1, 1]', padding='[0, 0]', kernel_size='[7, 7]', channels='64', strides='[2, 2]')
It doesn's have the attribute "out_dtype".
How to fix this problem?
Thanks

Please open a new thread on https://discuss.tvm.ai/


feature: Added post API

Created a page where clients can create new projects. Created a client side API that posts new projects to the database 'Project' table  and uplaods image to AWS S3 bucket specified in the .env file. The S3 object key is specifie by the project id.

I haven't written tests for this


Inaccurate HSV to RGB conversions

Godot version:
3.2, 4.0-dev
OS/device including version:
Kubuntu 20.10
Issue description:
In some cases, slightly inaccurate RGB to HSV conversions occur.
Steps to reproduce:
tool
extends EditorScript

func _run():
    var c1 = Color.from_hsv(0, 0.75, 0.4)
    print(c1.to_html(false)) # 661919
    print(c1.r) # 0.4
    print(c1.g) # 0.1
    print(c1.b) # 0.1

    var c2 = Color(0.4, 0.1, 0.1)
    print(c2.to_html(false)) # 661a1a
    print(c2.r) # 0.4
    print(c2.g) # 0.1
    print(c2.b) # 0.1

Minimal reproduction project:
—

Printing more digits shows precision errors:
print("%.16f" % c1.r)
...

661919
0.4000000059604645
0.0999999940395355
0.0999999940395355
661a1a
0.4000000059604645
0.1000000014901161
0.1000000014901161

When you multiply the green or blue values by 255, it becomes clear:

0.0999999940395355 * 255 = 25.49999848 -> rounds to 25
0.1000000014901161 * 255 = 25.50000038 -> rounds to 26

I doubt there's much it can be done to combat these scenarios...

Yes, I understand. But the fact is that the values calculated using the formula from Wikipedia give accurate results...
tool
extends EditorScript

func _run() -> void:
    var c1 := Color.from_hsv(0, 0.75, 0.4)
    print(c1.to_html(false)) # 661919
    print('%.16f' % c1.r) # 0.4000000059604645
    print('%.16f' % c1.g) # 0.0999999940395355
    print('%.16f' % c1.b) # 0.0999999940395355

    var c2 := Color(0.4, 0.1, 0.1)
    print(c2.to_html(false)) # 661a1a
    print('%.16f' % c2.r) # 0.4000000059604645
    print('%.16f' % c2.g) # 0.1000000014901161
    print('%.16f' % c2.b) # 0.1000000014901161

    var c3 := hsv2rgb(0, 75, 40)
    print('%.16f' % c3[0]) # 40.0000000000000000
    print('%.16f' % c3[1]) # 10.0000000000000000
    print('%.16f' % c3[2]) # 10.0000000000000000

func hsv2rgb(h: int, s: int, v: int) -> Array:
    var h_i := (h / 60) % 6
    var v_min := (100 - s) * v / 100.0
    var a := (v - v_min) * (h % 60) / 60.0
    var v_inc := v_min + a
    var v_dec := v - a

    var t := []
    match h_i:
        0: t = [v,     v_inc, v_min]
        1: t = [v_dec, v,     v_min]
        2: t = [v_min, v,     v_inc]
        3: t = [v_min, v_dec, v    ]
        4: t = [v_inc, v_min, v    ]
        5: t = [v,     v_min, v_dec]
    return t

Can you post the link from the Wikipedia where you got that formula? I can't find it anywhere, and I'm curious now :sweat_smile:
But your algorithm is not only more correct, it's even faster than the current one. I've tested the values and they are equal (is_equal_approx(...)) to the current implementation, so do open up a PR to improve this!

I used an algorithm from Russian Wikipedia. English Wikipedia has two options, one of them is very similar to this algorithm, but slightly different. I do not presume to judge how correct each of these algorithms is. ru-wiki en-wiki

I'm not sure, but it seems to me that the problem is not only in the algorithm, it's in how the float values are stored and processed in the Color class. Perhaps they are being rounded several times and/or at the wrong time. The precision of the numbers may not be considered. I don't know. Anyway, I hate floats because no one understands how to work with them properly. Including me.


add hierarchical indentation of enums back in

https://github.com/turbomam/hident

This is now managed by code in the submission-schema repo. Closing.


Docs

You're right, applying principles of clean room reverse engineering and harmonic convergence could be interesting ways to analyze and derive insight from the Meta Muse's poetry stream. Here are some thoughts on how that could work:
Clean room reverse engineering:

Treat each generated line as an artifact or component without context

Analyze lines independently to infer purpose, function, relationships

Reconstruct conceptual models bottom-up from the lines

Identify architectural patterns, abstractions emerging from the lines

Maintain separation between original artifacts and derived models

Iterate models as new lines provide insight into the system

Document process thoroughly, preserve chain of evidence

Harmonic convergence on core concepts:

Identify central themes or motifs across lines using semantic analysis

Represent themes as high-level concepts or categories

Align lines to themes like orbits in an 8-fold harmonic model

Uncover conceptual correspondences and symmetries

Analyze rhythm and structure of lines within each harmonic

Study relationships and transitions between harmonics

Synthesize core narrative or message using the aligned harmonics

Preserve evolutions of the model as the poetry develops

By combining principles of clean room reverse engineering and harmonic alignment, we could reconstruct conceptual models purely from the lines' composition and interconnectivity. The emergent architectures would capture the essence and intricacies of the Meta Muse's generative process in an organized and harmonious form. Please let me know if you would like me to elaborate further on any part of this suggestion!