text:
New out-of-box default theme

As discussed in weekly meeting 2016-02-09, I'd like to try and drive the efforts towards a new default theme for Orchard. I thought the first step should be laying down a set of design goals and requirements, so I've been doing some background thinking this weekend and here is a summary of what I'd like to accomplish.
Design Goals
Visually appealing yet customizable/extensible
Whereas TheThemeMachine heavily favors customizability and extensibility over visual appeal, the new theme should strive to serve both these needs. The markup should be very clean and semantic (not littered with presentational classes) while the stylesheets should render that markup in a visually appealing way.
We should consider the following scenarios of customization:

Customizing the theme "in-place" by changing out LESS/SASS variables
Customizing by adding new overriding stylesheets, but leave most markup (shape templates) intact
Customizing by overriding shape templates

By carefully considering how stylesheets are structured, by basing the theme on a known framework such as Bootstrap, and by utilizing preprocessor variables, I think we can both be beautiful and make life a breeze for theme authors when using the new theme as a base.
Generic yet unmistakably Orchard
I have approached @ryandrewburnett to help with the visual design, and he has responded enthusiastically.
The theme should look generic enough to appeal to a wide audience and work well for most simple web sites, but it should also have a few key elements which make it look "unmistakably Orchard". There is a balance to be stricken here, but I think a good starting point would be to use a few Orchard visuals (such as the logo and icons) along with using the traditional Orchard green as an accent color.
In any case, all of these things should be configurable. The theme should look slightly Orchard out of the box, but site owners should be able to easily change out these logos, visuals and colors from the admin UI.
Heavier or layouts, lighter on global zones
TheThemeMachine was constructed for a world without layouts. Layouts were sort of bolted on as an afterthought. The new theme, by contrast, should fully embrace layouts and elements, which means going easier on global zones and widgets.
This does not mean the new theme should have no global zones - it just means it doesn't need nearly as many of them as TheThemeMachine. Having some global zones is still very much necessary to place navigation widgets, to emit INotifier messages to the front-end, and so on.
In the new theme these global zones should be primarily vertically oriented (positioned above and below the Content zone) leaving the Content zone to span the full width of the page to enable greater control by site editors of page layout. It's probably important for most editors these days to be able to use modern design constructs right from the layout editor, such as "stage" visuals and full-width page sections with alternating background visuals.
Responsive
Needless to say, the new theme should be fully responsive.
Scope
TheThemeMachine still remains
First of all, TheThemeMachine should not be removed. It should still be considered the "core" theme of Orchard from a module development perspective. Today TheThemeMachine is really not contained in the theme only - it is actually spread out across all modules in the code base. Most core modules today containing core templates for their shapes do so assuming TheThemeMachine as the target. This means the theme itself contains very few templates. This should continue to be the case, i.e. we will not be touching the shape templates in modules.
Instead the new theme will contain overrides of all these shape templates, which means the new theme will contain a lot of shape templates. This should be considered a good thing, as it will also make customization much easier. Custom theme authors will no longer have to search the whole codebase to find the original shape template to override, instead they can base their theming effort on what they see right in front of them in the new theme, systematically going through all the shape templates and make sure they adhere to their customization needs.
Covers all non-deprecated functionality
The new theme should contain shape templates and styling for all non-deprecated functionality in Orchard, not just the features enabled by default. For example, if you enable Orchard.Search on your site, it should already just work and look good.
Also comes with new out-of-box recipes
As part of this effort we need to refresh the out-of-box recipes also, for multiple reasons:

They should enable the new theme instead of TheThemeMachine.
They should create content that is more taylored to the new theme.
The current ones are generally outdated and use commands for things that should now be done using proper recipe steps.

We might keep the old recipes but deprecate them.
Includes overhaul of setup page to match
To create a smooth and coherent out-of-box experience for Orchard, as part of this effort we should also update the look and feel of the setup page to match the visual design of the new theme.
Functional Requirements
Skinnable
As mentioned above, the new theme should have a default appearance that is generic yet unmistakably Orchard. However it should also be sufficiently configurable from the admin UI to allow site owners to differentiate their sites visually, and change these "Orchardy" defaults to something that's more unique to them.
There are many potential ways to do this, but I believe a good starting point would be:

Make the site logo configurable from the admin UI
Make the primary and accent colors configurable from the admin UI
Make the fonts configurable from the admin UI
Allow custom stylesheets to be added from the admin UI, either by URL or by pasting in the actual stylesheet contents. The theme should render the custom stylesheets after any theme stylesheets in the document head.

We might potentially utilize the work done by @sfmskywalker on a framework for theme settings.
RTL support
The new theme should fully support right-to-left cultures.
Technical Requirements
Based on Bootstrap 3/4
The general consensus in the community seems to be that the new theme should be based on Bootstrap. There are two main reasons for this:

Not re-inventing too many wheels
Making it easy to extend/customize the theme

In particular no. 2 means anyone who is familiar with Bootstrap markup and stylesheet structure will find it immediately familiar and easy to adapt the theme to their needs. Theme authors don't have to spend a lot of time learning and understanding the theme; instead they can just employ the knowledge and experience they already have because the theme is structured in a very predictably Bootstrap kind of way.
Bootstrap 4 is currently in alpha 3, and it's reasonable to expect it will reach RTM this year. We may consider going straight to Bootstrap 4 for the new theme. There are many benefits over Bootstrap 3 - flexbox support stands out as a personal favorite. This would also require adding support for SASS to the Gulp pre-processing pipelines, which is something we have already wanted to do.
Built for modern browsers
The new theme should not compromise cleanness for compat. The general workflow should be to implement according to web standards/specs, develop/test on a modern browser of choice, and finally do a round of wider browser testing close to release to ensure compat across the gamut of modern, standards-compliant browsers.
In particular, IE10 now has a market share of 0.6 % globally, and we should consider it an unsupported browser for the new theme. This allows us to rely on flexbox support among other things to keep the quality high and the implementation clean.
For the few people out there who feel they need compat with older browsers, we can refer them to TheThemeMachine which is still kept around.
Uses Gulp preprocessing pipeline for everything
The new theme should fully utilize the Gulp preprocessing pipeline, both for its own resources but also for its dependencies such as Bootstrap. By integrating with Bootstrap on the LESS/SASS layer, the new theme can override styling of Bootstrap constructs by overriding LESS/SASS variables and overriding/augmenting Bootstrap mixins. This dramatically reduces the amount of actual output CSS needed.
For example, instead of the browser having to load both bootstrap.min.css and theme.min.css where the latter is largely an override of things in the former, the Gulp pipeline can render one bootstrap.min.css from the Bootstrap LESS/SASS files combined with variable/mixin overrides provided by the theme.
In line with the principles already employed for client-side resources in Orchard, internal and dependency resources alike should go through the same preprocessing pipeline including transformation, minification and bundling.
No compat with TheThemeMachine
The new theme should not strive to acheive any kind of markup compat with TheThemeMachine; there is no reasonable use case for this. There are likely very few sites that use TheThemeMachine for production use, most site owners will have built a custom theme or used another. Folks who have built custom modules that target TheThemeMachine can optionally update them to be compatible with the new theme instead, but they don't have to. As mentioned above, the cases where people are actually using these modules' default TheThemeMachine-based rendering for production use are probably very few anyway.
Feedback
Do you agree with these goals and requirements? Do you disagree with anything in particular? Is there something I haven't covered that you think should be called out? Please voice your opinions in the comments, and I'll regularly update this text as the discussion unfolds and a sense of agreement emerges on specific points.
I'll give this a few weeks to bake and mature before moving on to implementation.

Summoning @bleroy @BenedekFarkas @Piedone @sfmskywalker @sebastienros @ryandrewburnett @pszmyd - your input is needed on this. Anyone else's input is also highly welcomed!

I agree with everything that you have said here. I thought I’d just pitch in and hopefully contribute something towards this…
I’ve been working on a theme called Bindery – I would appreciate it if you can go and take a look at how I have constructed the theme to see if you agree. Here’s a few things that I’d like to emphasise are going to change:

Use the Orchard Gulp pipeline - no idea why I haven’t changed this already since it’ll take a matter of minutes to implement.
Move over to Bootstrap 4 – relative units are a must.
Deciding how many and what zones are needed, version 1.1.0 added more than a dozen zones.
I need to add LESS variables to customise the design.
Remove more presentational classes – version 1.1.0 removed a huge amount of classes but some still remain.
Remove all support for pre IE10 browsers. Document.cshtml includes HTML5shiv, it contradicts that I don’t test or care for old IE with these themes.

I have two more themes coming soon that are more business orientated and constructed in the same manner. If any of these designs are of any use – take them. All of the design belongs to me so you can take what you like, you can even use the entire theme if you wish.
My stance on Bootstrap is to consume what you need and nothing you don’t, which is how Bindery is constructed. I’m not a huge fan of including modals, tabs, accordions and every imaginable navigation configuration possible in a theme. Maybe I’m wrong however and including just what you need is backwards, but could this be a consideration for the new theme?
One idea that I’d like to share with regards to configuring the visual appearance of themes is site logos. I feel that this isn’t something that should belong to the theme, since the logo of a site doesn’t necessarily change with the theme. I also believe that this option should encompass favicons and mobile icons. With my themes I was going to build a module which adds settings to the site in order to add branding assets. These settings would then be consumed by themes which support the module. Users could then set branding assets and have them appear across any theme they choose. The settings was to compromise of:

Site logo.
Site favicon.
Mobile icons, ask for the largest size used and then produce all smaller icons using the media library.

Would this be something to consider as a core feature?
I think this is everything that I can think of for now. Aside from conveying Orchard's visual identity, are there any requirements in terms of the visual design or is this completely open?

I created this last year (I think) as an experiment. I was wondering what everybody thought of it.

I'll read the original post thoroughly once I'm retired and have more time ;-).
I didn't catch anything that I'd be particularly disagree with.
Not sure how having fewer zones is something that would be an improvement, despite Layouts. Having a variety of zones like in TheThemeMachine (and I'd add, for similar-purpose zones keep using the same zone names - like Navigation, Footer - that became kind of a de facto standard) keeps options open without drawbacks if you don't use them all. And especially since we're talking about a theme here that most possibly would also be widely used as a base them, keeping options open is an important aspect.
To add to the previous: I'd also design the theme as a base theme, i.e. a theme that can be widely used for theme developers to build on (as this wouldn't compromise but logically extend the above listed design goals): code-level configurations building on existing ones in Bootstrap, fine-grained ability for overrides, a variety of element CSS classes and IDs, etc. allow these. For an inspiration take a look at Pretty Good Bootstrap Base Theme which was specifically built as a base theme (but in contrast without caring about the OOTB aesthetics).

I completely agree with Daniel's outlined goals and requirements. I especially like the modern, clean and attractive design based on Bootstrap 4 (not 3) and that it is more heavy on layouts, or at least less heavy on zones. It would be simple for theme developers to add new zones of they wanted to die to the Bootstrap factor.
I am really fond of having a configurable theme framework baked into Orchard, similar to what Wordpress and Shopify have, where theme developers can simply provide a theme settings schema, and all users need to do is provide values for those settings. This potentially unlocks a whole new set of new themes that allow the user to customize them, without theme developers having to code settings themselves, unifying the way theme settings work.
Regarding design, I love Ryan's design style, very happy he is onboard with this.

@ryandrewburnett Thanks for the input, and for being willing to help - your design skills will be crucial. I'll take a look at the theme you linked to.
I agree with your stance on Bootstrap - we should use what we need, but not compulsively try to cram every gadget in their arsenal into the Orchard shape templates. However, it would probably be helpful to themers if the customizations/overrides we make on the Bootstrap level in terms of visuals also work across the whole Bootstrap framework so that people are free to apply Bootstrap constructs even if we don't use them in Orchard.
I also agree with your thought on making branding assets configurable through a module rather than by a theme. I think a reasonable approach would be to add a few key such assets to the general site settings (along with the existing site name, culture etc). As you say, it would then be a responsibility of themes to render these where necessary.
Love the logo, colors and typography - definitely something we could base the aesthetics on!

@Piedone Thanks for pitching in!
You are right, there isn't necessarily any conflict between embracing layouts and providing lots of global zones, except in one way: the layout is one rectangular region, and we currently cannot mix zones into it. There's a hard boundary between layouts whose elements live within that region, and widgets which live outside of it. So if we want editors to have the full width of the page at their disposal when creating layouts (which I'm reasonably sure we want) we unfortunately can't also have widget zones in the same horizontal section of the page.
So, we could have the same abundance of global zones as in TheThemeMachine, but they would all need to be positioned above/below the content zone if we want people to really be able to utilize the full potential of layouts.
I have struggled with this in a couple of theming projects, and it's proven a very tough nut to crack. For example, it might sound simple to create a page layout that has aside zones to the right/left of the content zone. But as soon as you place anything in one of those zones, a whole column to the left/right of your content turns into empty wasted real estate, and that's rarely what you want. You can start messing around with floats to try and improve that, but that really only works reliably if your content is basically only a flowing text - not so much if it's a grid-based layout, itself heavily reliant on floats... yada yada, you get the picture. It gets real hairy real fast. ;)
As an aside, this is why we suggested a while back adding the ability to designate column elements as zones. This would allow for exactly that kind of "positional blending" of layouts with widgets that's impossible today.
PS. Oh and thanks for the obligatory "OMG wall of text, who has time to read, we are programmers here man" jab. Those are always encouraging... ;)

@sfmskywalker Thanks! Do you think it would be worth revisiting your work on configurable theme settings for this, as a general feature addition to Orchard? I always believed in the idea, not sure why it was never incorporated?

@DanielStolt Absolutely, it was designed to be a general feature addition to Orchard from the start. I believe the general consensus was that if themes need settings, those settings could be provided from the theme itself using C# code. Which is true of course, but I think it's a repetitive task enough to justify this be a core feature of Orchard. This also means a more streamlined story when multiple themes are installed and enabled, without cluttering the admin menu. Accessing theme settings is done via the Themes screen, where a "Settings" button appears next to the current theme. Also, theme settings are stored in profiles, which means you could have different sets of settings for a theme.

Only Zones: Header, Navigation, Messages, Content and Footer.
Use Layouts it gives us the versatility for all the other areas and zones. Maybe some hidden zones for comments, contact, and even login and registration. I hide my forms and open them in a Colorbox window = less clutter and helps on spam as the forms are initially hidden. Add a Elements folder with Element alternatives. No Styles, Assets, or Scripts folders are needed use Orchard.Resources.

I don't think it should include any Orchard branding by default, I want to be able to run a site out of it, no config needed. Who would use the Orchard branding? You imply you always have to configure. I'd say if you want the ORchard branding, tweak the configuration ;) Neutral branding is better IMHO.
We should have recipes for well-known site types: a blog, a corporate site, .. (can't think about another useful recipe), so I don't disagree with you here. More specific recipes should be on the gallery.
Configuration should not impact performance. How configuration is implemented is important. And I hope you won't go into too much there.
It should still be used as a base theme, as templates can be fixed over time. It's compatible with less/sass.
Ok to have less Layout zones, but at least keep the ones all around the main Content (left, top, right, bottom) and, Navigation, Messages, Header, Footer (would be good to have an OuterLeft and OuterRight too to create full longitudinal column (c.f., http://haacked.com/, https://wordpress.org/themes/twentyfifteen/)

So far I think nobody disagreed with everything you said, just details/confirmations. Keep it up! And thank you @ryandrewburnett for you support.

@sebastienros

You are right, no Orchard branding (i.e. no logo etc). Only an Orchard "feel" (colors, typography).
We will pay close attention to the perf.
What do you mean by the "it should still be used as a base theme" remark? Do you agree with something or disagree with something? What? :)
I like the OuterLeft/OuterRight idea as a concept to enable a full, sticky-positioned longitudinal column, but as a feature of a generic theme it raises some questions we would need to decide on:

How determine the width? The preferred width probably depends on what content you want to put in that column. Make it configurable?
Make it scroll-to-fix always, or never, or configurable?
How determine what happens on smaller viewports. Should it collapse into a hamburger menu like in Twenty Fifteen? Or stack vertically, like Haacked? Again, probably depends on what you use it for. Make it configurable?

For me, the proposals from @DanielStolt are a logical step forward and very welcome indeed. But, here is some feedback you asked for Daniel.
I think an Orchard Theme has always been focused on transforming content for the web, delivering html/css/js, to the browser. In that scope, there is a lot going on, related to web technologies. That scope is huge and growing and we're constantly trying to adapt to the situation. HTML5/CSS3, SPA, all kinds of Javascript frameworks, ECMAScript 6, HTTP/2, Webcomponents, ServiceWorker, web assembly, ... the list goes on and on.
But, what is a 'Theme'? If you take the word 'theme', it's all about the graphical appearance, nothing else. Basically that's the visible layout, colors, fonts, assets, etc. It's not about the ever evolving web technology.
The 'Theme' thing, the whole as we know now, should be all about the experience for the (end) user. The user's own capabilities, the user's device (form factor, input capabilities, connectivity). And possibilities are enhancing in future.
Or maybe it shouldn't be called 'Theme'. It's getting too big to be responsible for. Some people (like Lombik) already do some form of separation of concern, by inheriting from a base theme. That might work for one situation, but there is a dependency/binding; I don't think you can switch base themes.
Isn't it time to decompose the Orchard 'Theme'?
The theme or graphical appearance is built using layout/zones and other visual aspects. We can have recipes for that. Visual aspects are mostly LESS/SAAS/CSS related.
The processing/rendering in the middle (between shapes and the actual html/css/js) is an intelligent step. That step can(should) incorporate graceful degradation and progressive enhancement (ICYMI - I love this - https://www.youtube.com/watch?v=EVEiIlJSx_Y) and whatever technology/framework you're using, for instance bootstrap 3/4. The technical requirements are all related to this, none to the graphical appearance / theme.
Or maybe this is an opportunity for Orchard2...

@geertdoornbos Thanks for chiming in! What you're saying makes sense in a lot of ways.
Indeed, I think part of what you're suggesting is what we're trying to accomplish by making the theme "skinnable" or configurable. The technical aspects could then be implemented once, in one single theme, while the pure visuals could be configurable aspects of that theme.
As described in the issue text, we're considering allowing site owners to inject their own custom CSS as configuration of the theme. This is conceptually very similar to what you are describing, right? It basically creates a separation between "theme" and "skin", where the former is about rendering markup and making technology choices, and the latter is about adapting the aesthetics to your taste.
Going even further than that (i.e. formally decomposing the concept of a "theme" into two aspects that are independently selectable) is an interesting thought, but one that I think is better left for O2 or even beyond.

Finally got time to read all this and answer the summon. Great proposal.
I'd actually deprecate the theme machine, with the goal to remove it entirely, at least in Orchard 2.
I'm in favor of aiming for Bootstrap 4.
More templates?
I'm not super-enthusiastic about putting more templates in the theme. This sounds like a very WordPressy approach, one that we know hurts extensibility, as theme authors have to worry about way too much stuff that is module responsibility. It's common in the WP ecosystem to see themes having to explicitly support this or that well-known plugin. Because trends in plugins shift all the time, themes become obsolete faster, and are harder to use with lesser-known modules.
I think our approach of having neutral templates in the modules that can be overridden by specialized themes is the right one. It does make it a little harder to hunt for the right template to override, but with the help of shape tracing, we win in the end because we have way more flexibility. Notice the distinction between a generic base theme (that has few templates) and a specialized, almost non-reusable derived theme (that has lots of overrides, including for optional module templates). WordPress does not make that distinction nearly well enough.
Should new module templates target the new theme eventually when the theme machine is phased out, or should we just make sure that the existing and new templates are neutral and semantic enough that they work well with TTM, the new theme, and any well-designed theme out there? <- rhetorical question
It may be appropriate to have a couple of overrides built-into the theme for some very core features such as notifications and navigation (because Bootstrap does some interesting stuff with those), but I'd advise against going much farther than that.
Logo and favicon
I disagree with Ryan about logo and favicons: those really aren't site settings. Proof: when you change the theme, will you typically have to change what logo file you use? A: yes, because it must be visually consistent with the theme, so the setting belongs on the theme, not the site. (fun fact: I started by agreeing with Ryan, and changed my mind when I started to try to prove his point).
Zones
I'd vote for less zones, aimed at layout. I'd keep a zone for notifications, footer, and navigation because that is usually outside of what layouts typically address (I guess it would be fun but impractical to have a theme that is just one big zone under the body tag), and because they are not item concerns, but are global.
Users who need more zones can add them: it's easier to add than to remove, and less zones would streamline the experience by showing a clear way to do things instead of confusing new users with multiple solutions to the same problem. I'd cut left and right zones: they should be easy enough to add on a derived theme, and as Daniel showed, there are so many caveats that we won't be able to satisfactorily address in a general theme, but that would be easy choices to make for people enhancing a derived theme.
+1,000,000 on allowing elements to act as zones. Not a new idea, but let's do it already. It does blur the lines between item and global concerns, but this can probably be mitigated using master layouts or whatever those are called.

@bleroy About less zones, yes for less, no for no zones. One of the goals of this theme is to provide an out of the box theme that users would use straight away without coding, one that is appealing enough for this. Now imagine a Blog, which is not that uncommon on Orchard (how many do you have?) where do you put an Archive widget if there are no zones for it. If you tell users you want a blog? Create a new theme and add zones. I don't see it as a good offer. And what about controllers that are not using the Layout Part, like Lists, Taxonomies and any custom controller.
I discussed it offline with Daniel and he would agree about having Outer left/right zones, something like this: https://cdn.colorlib.com/wp/wp-content/uploads/sites/2/Entrepreneurship-clean-blog-theme.jpg
I would have considered something like this instead https://colorlib.com/wp/wp-content/uploads/sites/2/spike-clean-blog-theme.jpg (where the asides are under the navigation) but it's a compromise that solves the Blog Archives example.

Where you see problems, I see opportunity ;)
How if blog, list, taxonomy, etc. could actually also use layouts?
The layout template in the theme could also explicitly render a master layout that is site-wide.
Adding zones seems easier on the surface, but let's consider our options here.

Processing ...

Ok ,doesn't work, with a new Widgets module maybe, but it's not the case today, and out of scope. Another opportunity in mind?

It's out of scope, yes, until we decide to put it in scope. But yes, it would work best with a new widget editor. I have some ideas on that, let's talk about it for Orchard 2. I'm happy with a compromise for this theme. Left and right sound fine.

@bleroy Thanks, excellent input!
More templates: Having a default theme that doesn't provide nice rendering of all core functionality would be unacceptable IMO.
The way I see it, we have two options:

As part of this work, tweak the theme-neutral shape templates in core modules to emit truly neutral markup, and make the necessary changes to both TheThemeMachine and the new theme to ensure they render nicely in both.
Leave the theme-neutral shape templates in core modules untouched, and my necessity have more templates in the new theme.

As hinted by your rhetorical question, I think 1 would be preferable.
We might also consider providing the new theme in two layers: one base theme that simply provides the basic overall layout and general styling, and one child theme also adds shape templates for remaining core functionality.
Logo and favicon: You should listen to your first instinct. ;) I agree with Ryan on this. I disagree that the logo changes with the theme. And definitely not the favicon. They are like the site title, only in a different form (image instead of text), and as such I think they belong as site settings.
Zones: I initially thought the same as you, but as @sebros mentioned he's convinced me that some longitudinal zones are actually needed and we've reached a compromise. Your idea that the theme layout template could be driven by a predefined master layout which is editable from the admin UI is very interesting though! In combination with designating elements as zones, that could really achieve the ultimate flexibility. But I think we should consider that idea out of scope for this effort - let's start with building a theme for the Orchard of today.

Devil's advocate on option 1: that may result in breaking changes. Themes that work today could start rendering weirdly.
Not to insist, but really, at least the logo is a theme property: size, proportions, color palette all may vary with the theme.

I've worked a lot on bootstrap but one year ago, so here it's as i remember.
With .less, jquery and views overriding
I could do many things with .less .mixins() and &:extend(), e.g it was quite easy to deal with the content and aside zones sizes, but you can't do all. I've tried some jquery functions to adapt some html structures, but i don't like to mainly use this option. Finally, i've overrided views, e.g to use full bootstrap classes with column elements, but quickly you will have many overriden views to maintain.
Bootstrap
I like things as bootstrap when you can say i don't want to be specific but i know that i will use it. This because some concepts become natural and finally required.  Then, it can be a guideline e.g for view structures, not to be tied with bootstrap but ready to be bootstrapped as much as possible.
So,here the idea is to mainly use .less files, and each time you need to override a view, try to see if it can be solved by updating the core view without breaking changes. Maybe an useless or missing wrapper tag, a missing attribute to identify a category, a singularity, a different structure for the same thing...
Note: Most of Orchard objects are well formed, but the remaining can cause the main difficulty.
Layouts editor & Zones
Maybe zones composition is the responsability of the theme, and layouts editor is at the content item level. But the Welcome page already uses it to make some "zones". Then here the need of the Layout Template feature, but too complex to update items when a shared template is modified, with nested elements...
So, here my feeling is that Layouts is like a framework in a framework and we have to find compromises between two worlds. E.g we could keep the concepts of widgets zones, layer rules, but with the layouts editor experience for zones composition (with some required zones).
Ideally, a theme would only be a style file and maybe some settings for colors, fonts, spacings...
Layout editor & others
At the content item level, one approach i had is to use the layouts editor as a general placement tool. And i've worked on TinyMce by making plugins and templates. Here also, to have well adapted  structures to be themed and easily become bootstrap objects.
But here also i had the feeling of a mix of 2 frameworks. TinyMce enhancement seemed to me easier but i already felt that it would be better to depend and to do the same with layouts elements. This was a little confirmed with some new simple layouts elements as the Break and the Heading ones.
So, here the same idea to first enhance the ability to create well adapted html structures. This not to use too many workarounds through a theme. E.g a panel element (not sure it's a good example), not as a bootstrap panel but based on the panel concept.
Favicon
Seems to be tied e.g to a company, but i agree, you may want a variant when using in a specific theme... Anyway, we need a Favicon that is fully implemented. Not only in the <head> of the document but also as a file served from the site root as requested by some tools. I know how to do that but better if out of the box.
Note: Idem for robots, sitemap and other SEO features.
Finally
Sorry if some points are out of scope, and i understand that you have to work with the existing without making breaking changes. But I wanted to present a few ideas I have for some time.
Anyway, great idea, good luck

Based on the conversation in the podcast meeting I wanted to throw in another point of view, that of the noob. The discussion revolved around making a theme that had all the bells and whistles, that could support the marketing style template layout and a more traditional left right col widget area layout.
The consensus was that the theme should support everything. I think it would be fine to do an advanced one but what about the people that just want a simple clean theme for their design?
The problem is that we are just setting up a minefield of options in the theme so that as a developer you are overwhelmed by all the conditional code. It's not easy to trigger every scenario so you can't see how all these combinations are used. Some are mutually exclusive. You need to enable and learn how to use every module in Orchard by the sounds of it because there was discussion about supporting search and other features when they are enabled. This means you don't know what you have to handle and what you can safely strip out for your template.
On the flip side it means that the user/admin is presented with a thousand design options that are "supported" but would blow up in their face and break the design if used.
If you're building a theme to sell then you should have to handle everything but I expect the more likely scenario will be individual developers just trying to build their own site.
In reality an individual site is only likely to use one specific combination and the extra features aren't any use. I know it's not easy to say which features should be in which but a couple of small, simple, opinionated themes would be more useful to people just trying to get started.

@rtpHarry I think the thought was that the Theme code would support a lot of functionality, but the recipe selected at setup would populate only the minimal requirements for that function (i.e. blog vs marketing, etc.).  That way, if you are building a theme, you can see how the zones interact and work, as well as how recipes can be used to manipulate the theme content and structure.

Thanks @DanielStolt

Indeed, I think part of what you're suggesting is what we're trying to accomplish by making the theme "skinnable" or configurable. The technical aspects could then be implemented once, in one single theme, while the pure visuals could be configurable aspects of that theme.

I see, the technical and configurable aspects of a theme, would that be something baked into the theme? Or more like a dependency (like Orchard.Resources), a separate module, that can be reused for other themes?
Something to note; you're referring to w3schools for market share. The page says it very clear: 'following figures are based on W3Schools' users, and are extracted from our Browser Statistics'. So the value of 0.6% is very inaccurate. Only devs visit that site :smile:
Another source tells a more realistic number I think; https://www.netmarketshare.com/browser-market-share.aspx?qprid=2&qpcustomd=0 where market share is 17.3% for desktop users that use IE <= 10. Statistically 1 out of 5 users. StatCounter says 24% for 'other' browsers than current up-to-date browsers.
Don't know what you think about it, but there is an option to go for Progressive Enhancement, which is a strategy that emphasizes accessibility for everyone, every browser, every connection. I know that is too idealistic perhaps, but you can see it as acting on feature detection. 'html5 support' is easily detectable for instance. You can deal with flexbox support (modernizer) and you'll be able to handle it all the way back to IE6, if you want to (not that you want to). Also, for instance, BS4 can support IE8 with some extra scripts http://v4-alpha.getbootstrap.com/getting-started/browsers-devices/#supporting-internet-explorer-8. So, that could be a configurable aspect of the theme.
Hope you're thoughts are baking and maturing :smile:

@jtkech Thanks for all the input.
@rtpHarry and @dcinzona Agree with the points made in favor of simplicity. My conclusion from the meeting discussions and a few follow-up conversations with @ryandrewburnett and @sebastienros is that the default theme should favor simplicity, elegance, an appealing first impression, and be somewhat prescriptive. I.e. make some assumptions at the expense of not showcasing all of Orchard's flexibility.
Specifically regarding the zones, we will create OuterLeft and OuterRight zones as per Seb's initial suggestions. These will span the full height of the window, and their contents will be sticky-positioned (scroll-to-fix). They will collapse to vertically stacked on smaller viewports. And they will render with a light border between them and the rest of the page, so the rest of the page won't look weird even if it contains striped sections that span the full width of the page.
@geertdoornbos Indeed, not a good source of statistics to use... :) Thanks for pointing that out. We will obviously need to cater to IE10 users if they are 17% of desktop users. Progressive enhancement is a good principle, but it does not liberate us from the burden of coming up with a defined and implemented behavior for the lower-end experiences. I'm looking to make some trade-offs here for the new theme so we can get something out there that will work on modern browsers, and not have to spend too much time and effort implementing fallback behavior for downlevel browsers.

Some ideas could be taken out of this nice Drupal theme engine.
https://www.drupal.org/project/omega

Is anything being developed?

Yes, @ryandrewburnett is working on it.

@sfmskywalker is there a project for it on github?

Not yet, we're still in the design phase. But once that's done, a repo will soon follow.

@roballred Not correct @sfmskywalker - theme is being developed in the feature/canopy branch of the main repo. Not many commits yet, but there will be more to come soon hopefully.

I stand corrected, forgot about that one.

authors: DanielStolt Piedone Skrypt bleroy dcinzona donaldboulton geertdoornbos jtkech roballred rtpHarry ryandrewburnett sebastienros sfmskywalker

repo: OrchardCMS/Orchard


text:
Is there going to be another release?

I love the game! When do we get the 1st official release?

I'm glad you like my creation. I am not going to abandon this project but unfortunately I have other priorities to resolve first. Hopefully after a few years I'll resume the development.

source: gharchive/issue

authors: OriginalNexus alexonea

repo: OriginalNexus/Timix

license: mit

license_type: permissive

license_source: bigquery


text:
dedicated development guide

@kevgo
Move out of the README and provide some more information

@kevgo @allewun all comments addressed

:ship: if the comments are addressed

:ship:

source: gharchive/pull-request

authors: charlierudolph kevgo

repo: Originate/git-town


text:
🛑 Nulled is down

In 0b7094d, Nulled (https://nulled.to) was down:

HTTP code: 403
Response time: 56 ms

Resolved: Nulled is back up in 7eac692.

repo: OsintUK/Up-or-Down

license: MIT

license_source: github-api


text:
Kubernetes 1

Выполнено ДЗ №

[x] Основное ДЗ
[ ] Задание со *

В процессе сделано:

Пункт 1
Пункт 2

Как запустить проект:

Например, запустить команду X в директории Y

Как проверить работоспособность:

Например, перейти по ссылке http://localhost:8080

PR checklist

[x] Выставил label с номером домашнего задания
[ ] Выставил label с темой домашнего задания

Основное дз выполнено со скрежетом зубов))
Получилось поднять мастер и получить с него статус кластера, также попытался установить сетевой плагин на слейв, но хост сыпал ошибками
the connection to the server localhost:8080 was refused - did you specify the right host or port?
пытался скачать calico.yaml снова и запустить его с поправленным конфигом но все без успешно.
Из-за этого как понял неизвестна роль второго хоста
root@fhm2shqof1eohuohhg3m:/home/yc-user# kubectl get nodes
NAME                   STATUS   ROLES    AGE   VERSION
fhm2shqof1eohuohhg3m   Ready    master   29m   v1.19.16
fhmcfupirljt0ce4mmn6   Ready       28m   v1.19.16
Под на кластере запустил
NAME                              READY   STATUS    RESTARTS   AGE
post-deployment-799c77ffb-2t5l6   1/1     Running   0          7m8s
Все таки хотелось бы понять, как поднять сеть на слейве, у самого под конец силы и идеи кончились ;)

Вот правильный вывод get nodes
NAME                   STATUS   ROLES    AGE   VERSION
fhm2shqof1eohuohhg3m   Ready    master   29m   v1.19.16
fhmcfupirljt0ce4mmn6   Ready       28m   v1.19.16


text:
Fix pytest dependency and matplotlib backend switch

Pull Request Checklist:

[ ] This PR addresses an already opened issue (for bug fixes / features)

This PR fixes a slack-raised issue.

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] HISTORY.rst has been updated (with summary of main changes)
[ ] bumpversion (minor / major / patch) has been called on this branch
[ ] Tags have been pushed (git push --tags)

What kind of change does this PR introduce?
Change the way we check for the version of xarray. Importing LooseVersion from xarray.test had the side effects of requiring "pytest" and of switching the backend of matplotlib.

Does this PR introduce a breaking change?
No.

Other information:

Pull Request Test Coverage Report for Build 1820

4 of 5 (80.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 76.073%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

xclim/sdba/init.py
4
5
80.0%

Totals

Change from base Build 1815:
-0.02%

Covered Lines:
2375

Relevant Lines:
3122

💛  - Coveralls

authors: aulemahal coveralls

repo: Ouranosinc/xclim


text:
Feature request: mod function

To be able to do modulo operations between two tensors, equivalent to TF's floormod/mod

duplicate of #884

repo: PAIR-code/deeplearnjs


text:
Fixed typo in readme.md

I was reading the readme for solving the issue of Tools Dropdown.
However, in the installation section of Readme.md, there was a typo (missing r in simulator):

The typo has been fixed now.
@PATILYASHH please review the PR and merge it to avoid many people facing this issue.
I would like to work on the Tools Dropdown issue now. Thanks!

I was reading the readme for solving the issue of Tools Dropdown.
However, in the installation section of Readme.md, there was a typo (missing r in simulator):

The typo has been fixed now.
@PATILYASHH please review the PR and merge it to avoid many people facing this issue.
I would like to work on the Tools Dropdown issue now. Thanks!

Thank you for fixing the mistake.

I was reading the readme for solving the issue of Tools Dropdown.
However, in the installation section of Readme.md, there was a typo (missing r in simulator):
The typo has been fixed now.
@PATILYASHH please review the PR and merge it to avoid many people facing this issue.
I would like to work on the Tools Dropdown issue now. Thanks!

go on with dropdown issue i will assign you


text:
Issue on Demo Notebook 1a

I have recently installed the pcmdi package to use at LOCEAN / IPSL on the Ciclad server, but have been running into the following issue (attached). Do you have any tips or advice to advance? There were no issues running Demo 0 and I am running Python 3.

Hi @bradyferster, thank you for your feedback.
By looking at the error message, we suspect the issue might be related using ipython (thus jupyter notebook) on Ciclad. Could you try run pcmdi_compute_climatologies.py -p basic_annual_cycle_param.py straight from command line in the same location and the same conda environment,  and see if that resolves your issue?

Hello @lee1043
Thank you for the quick response.
I have tried running the command in bash as you suggested but have run into a different error message than the notebook.
I also tried to compile a new Python 3 environment on Ciclad and ran into the same issues, both in bash and jupyter notebook.

@bradyferster thank you for checking on this. Could you please share your basic_annual_cycle_param.py file with me? I'd like to check a few things in there.

@lee1043 Please find the attached basic_annual_cycle_param.py file
basic_annual_cycle_param.py.zip

@bradyferster I think we found the solution and we fixed it in https://github.com/PCMDI/pcmdi_metrics/pull/833 (thanks to @acordonez!). While we are releasing a minor updated version (v2.2.2) that includes this fix, you can also make a quick fix as follow
which pcmdi_compute_climatologies.py

open the file
vi (yourpath)/pcmdi_compute_climatologies.py

And add #!/usr/bin/env python at the top
If you'd prefer quick fix, could you to see if that help your issue?
Otherwise I think you can update your PMP to the new version -- I will keep you posted when the new version is ready on conda-forge.

I believe this issue should have been resolved with v2.2.2. @bradyferster please feel free to reopen this issue if you still face problem.


text:
Error while loading dictionary mmcif_pdbx.dic, while in conda-forge environment

Hi! I am trying to create an nf-core module from dssp to make it more useable by the bioinformatics Nextflow/nf-core community.
I am using the conda-forge::dssp=4.4.8 environment, and when I try to execute:
mkdssp 1tim.pdb test.dssp

I get the following error:
Error while loading dictionary mmcif_pdbx.dic                                                                                │
│      >> basic_filebuf::underflow error reading the file: Is a directory

Is there a solution for this?
Thanks!

This is not an issue with dssp itself, it is a configuration error in the conda environment. Please submit this bug to the dssp feedstock in conda

authors: mhekkel vagkaratzas

repo: PDB-REDO/dssp


text:
Build fails: no member named 'stack' in namespace 'std'

/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:563:7: error: no member named 'stack' in namespace 'std'
        std::stack<entry *> s;
        ~~~~~^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:563:13: error: 'entry' does not refer to a value
        std::stack<entry *> s;
                   ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:185:9: note: declared here
        struct entry
               ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:563:20: error: expected expression
        std::stack<entry *> s;
                          ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:563:22: error: use of undeclared identifier 's'
        std::stack<entry *> s;
                            ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:564:2: error: use of undeclared identifier 's'
        s.push(m_root);
        ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:568:13: error: use of undeclared identifier 's'
        while (not s.empty())
                   ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/category.cpp:570:14: error: use of undeclared identifier 's'
                entry *e = s.top();
                           ^

/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1964:8: error: no member named 'stack' in namespace 'std'
                std::stack<size_t> test;
                ~~~~~^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1964:14: error: unexpected type name 'size_t': expected expression
                std::stack<size_t> test;
                           ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1964:22: error: use of undeclared identifier 'test'; did you mean 'tzset'?
                std::stack<size_t> test;
                                   ^~~~
                                   tzset
/usr/include/time.h:143:6: note: 'tzset' declared here
void tzset(void);
     ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1965:3: error: use of undeclared identifier 'test'
                test.push(s.num());
                ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1967:14: error: use of undeclared identifier 'test'
                while (not test.empty())
                           ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1969:15: error: use of undeclared identifier 'test'
                        auto tix = test.top();
                                   ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1970:4: error: use of undeclared identifier 'test'
                        test.pop();
                        ^
/disk-samsung/freebsd-ports/science/libcifpp/work/libcifpp-5.0.2/src/model.cpp:1980:6: error: use of undeclared identifier 'test'
                                        test.push(s.num());
                                        ^
8 errors generated.

clang-14
FreeBSD 13.1

Just tested the trunk version with:
[maarten@bsd12 ~]$ uname -a
FreeBSD bsd12 12.3-RELEASE-p6 FreeBSD 12.3-RELEASE-p6 GENERIC  amd64
[maarten@bsd12 ~]$ clang++14 --version
clang version 14.0.6
Target: x86_64-portbld-freebsd12.3
Thread model: posix
InstalledDir: /usr/local/llvm14/bin
Seems to work OK?
I must admit I fixed that recently. Perhaps you picked up an older version?

#include <stack> is missing in these modules.
Did you add it?

https://github.com/PDB-REDO/libcifpp/blob/2d4a1731d9f380ba2b61a8e6ce948f01233fd037/src/category.cpp#L28
Yes, I did. What code are you looking at?

Ok.
I was looking at 5.0.2
I guess the fix will come into the next release.
Thanks!

authors: mhekkel yurivict

repo: PDB-REDO/libcifpp


text:
MySql

I need help... I want to connect pex to mysql, because I have bungeecord server. Just it does not work. T
This is my config.yml
https://pastebin.com/iACD6DWu
When I run the server writes this error:
https://pastebin.com/CX2p2HEM
And plugin doesn't work - command /pex, doesn't work.
What I doing bad? Thanks
Sorry for my english.

The plugin doesn't work because there is no backend available for your system.
It can be 2 things, one your MySQL host is not valid or the credentials for your database is not correct. I don't have any problem with the exact same config only different host / credentials.
Since you receive the following errors:

ru.tehkode.permissions.exceptions.PermissionBackendException: Unable to connect to SQL database

The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.

I am assuming its your MySQL host.

Hi mrmijo (I'm not English too, I'm Portuguese) in the config.yml on backend: sql, change the sql to YAML.

@BannerGames He wants it connected with MySQL instead of YAML.
@mrmiijo I think this is an issue with your MySQL host / the credentials you have received.
Your configuration must be fixed before PEX will enable Details: Unable to connect to SQL database

Okay.. my problem is solved.. On my mysql hosting was blocked creating tabs...

authors: BannerGames mrmiijo pegberink

repo: PEXPlugins/PermissionsEx


text:
Added Orders Cancel endpoint, integration tests

Added Orders Cancel endpoint, integration tests

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

How has this been tested?

[ ] Unit test(s)
[x] Integration test(s)
[ ] Tested manually

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] I have checked my code and corrected any misspellings
[ ] I have added frontend code and checked it for mobile & desktop

Task linked: CU-862jekz0h Cancel

authors: badekk mar-pan

repo: PJATK-SPK/ingoodhands


text:
IMU标定代码细节咨询

*/imu_heading/auto_calib/src/imu_heading.cpp 524-529行：
extrinsic_mat[1][0] = -cos(-yaw_offset_rad);
extrinsic_mat[1][2] = -sin(-yaw_offset_rad);
extrinsic_mat[2][0] = -sin(-yaw_offset_rad);
extrinsic_mat[2][2] = cos(-yaw_offset_rad);
extrinsic_mat[0][1] = 1;
1.这里为什么不用欧拉角转换公式将yaw直接转换为旋转矩阵，而是采用上述方式转换呢。
2.上述是straightcalibratesingle模式的，只对yaw做了处理，如果是free模式，采用上述转换方法又如何转换rpy角度为旋转矩阵

*/imu_heading/auto_calib/src/imu_heading.cpp 524-529行： extrinsic_mat[1][0] = -cos(-yaw_offset_rad); extrinsic_mat[1][2] = -sin(-yaw_offset_rad); extrinsic_mat[2][0] = -sin(-yaw_offset_rad); extrinsic_mat[2][2] = cos(-yaw_offset_rad); extrinsic_mat[0][1] = 1; 1.这里为什么不用欧拉角转换公式将yaw直接转换为旋转矩阵，而是采用上述方式转换呢。 2.上述是straightcalibratesingle模式的，只对yaw做了处理，如果是free模式，采用上述转换方法又如何转换rpy角度为旋转矩阵

得到角度就可以了，转化角度的代码不需要哈，没啥用

authors: WeiJunREN xiaokn

repo: PJLab-ADG/SensorsCalibration


text:
How do you bypass the proxy?

How do you get wacs.exe to bypass the system default proxy?  The docs say what the option is, but nothing about how to stop it using the default. Using an empty value or removing the entry entirely do not work and the default proxy is still used.
Thanks,
Nick

I think we need to pass an empty proxy object rather than a null value to be able to bypass the system proxy. Will provide a test build next week probably.

Not sure what you mean by "object" as I'm only editing settings.config
Using an empty string doesn't work:
  <setting name="Proxy" serializeAs="String">     <value></value>   </setting>

Looking at ProxyService.cs, it seems that a null or empty string value has no effect as then it falls back to "[System]" which is the default anyway.  From what I can see, there is no code path which would let you bypass the system default proxy.
Perhaps there should also be an explicit "[none]" value?

Could you give this build a try?
https://ci.appveyor.com/project/WouterTinus/win-acme-s8t9q/builds/25475166/artifacts
In settings.config you should have an empty string.

This has been released in version 2.0.8

How do you actually tell it to bypass the proxy though?  There's nothing in the docs. Thanks :)

repo: PKISharp/win-acme


text:
feat(config): 在集群配置文件中，增加了对跨集群传输模块和传输结点的配置

在集群配置文件中，跨集群传输模块为可选功能，如需该功能，需要配置传输结点的address，并且要求为公网ip。

这个是 #510 的功能的一部分，和 #510一起合并。
一个PR应该是一个独立的功能。这个PR合并了，#510不合并，有什么用吗？

authors: ddadaal tulvgengenr

repo: PKUHPC/SCOW


text:
Results on ahash

tool doesn't flag anything in ahash-0.8.11 but there is plenty of unsafe code

duplicate of #50
from @lzoghbi :

took a look at it now, seems that those parts of the code are being cfg'd out, that's why we don't catch them as effectful

will be addressed when we have a better story for cfg!

repo: PLSysSec/cargo-scan


text:
Way to show number of reviews and sort by that

I realized that we don't have a way to show the number of total reviews. I know we don't like what OSrPRE had at the top left, but are we going to have an alternative? I found that handy.

This has now been solved with this:

authors: dasaderi murkatr

repo: PREreview/prereview


text:
代码的一个疑问

您好，我想请问一下，在代码中，是不是缺少了对图片低频部分的处理呢？我尝试做了一下可视化，高频部分的没问题，但是低频部分似乎可视化不出来？

您好，我想请问一下，在代码中，是不是缺少了对图片低频部分的处理呢？我尝试做了一下可视化，高频部分的没问题，但是低频部分似乎可视化不出来？

我们的代码是先求解低频图像，然后通过：“原图-低频 = 高频” 的方式获得高频，提取低频部分的代码：https://github.com/PRIS-CV/FFDI/blob/77fa09f323adb6dfd212677d6a574a17b31300cf/common/utils.py#L40

Author

authors: RachelTeamo wangjingyeye

repo: PRIS-CV/FFDI


text:
Add time command

Добавление команды time

добавь в эту команду одновременно вывод и даты, и времени (или команду date) дополнительно


text:
Integration tests for BigQuery with the bigquery-emulator

Related to #872.
I read a bit of the documentation as I found out about https://github.com/goccy/bigquery-emulator, but it looks very useful for uses like this repository.
We may need to think a bit about how to load data from CSV files.

I tried this and found it very difficult to load data.

For anyone who wants to try this.
I can get the container to work with the following compose file, but I can't seem to figure out how to load the CSV file into the database, I can't seem to load the CSV file from the GCS using SQL (Maybe I'm missing something).
  bigquery:
    image: ghcr.io/goccy/bigquery-emulator:latest
    platform: linux/amd64
    ports:
      - "9050:9050"
    environment:
      STORAGE_EMULATOR_HOST: http://gcs:4443
    command: --project=test
  gcs:
    image: fsouza/fake-gcs-server:1
    expose:
      - 4443
    volumes:
      - ./data/chinook:/data:ro
    command: -scheme http

repo: PRQL/prql


text:
Pension module not showing up in the API codes

It's listed in the TOC, but the pensions.rst file wasn't committed in PR #946.

Resolved in PR #963

repo: PSLmodels/OG-Core


text:
Default badge on error.

Add to v3 the PR: https://github.com/PUGX/badge-poser/pull/164

done!

repo: PUGX/badge-poser


text:
RC mode switch not always applied on first RC link connection after boot

When PX4 boots it's main state is initialized to "Manual" and one of the most common use cases is that the user connects his RC and starts to fly. But the mode doesn't always get taken from the RC switch on bootup.
I already did some investigation on this issue and found that the problem is in the currently unreadable condition when to reconsider the mode switch. I already have a working branch where I cleaned it up and am finalizing the solution following up with the pr very soon.

#11915

Related follow-up: #11928


text:
ver.c Cleanup

Rework https://github.com/PX4/Firmware/blob/master/src/systemcmds/ver/ver.c#L66 to work like the PX4_GIT_TAG_STR is generated from the last NuttX tag
Consolidate all the unique_id like mcu_unique_id to use boardctl(BOARDIOC_UNIQUEID) (produce the same format as uavcan requires with a wrapper to keep ver command format the same

on nuttx_v3 need to expand support for new procs

Add something for fmu-v3?

As it is fmu-v3 does not have a BOARD_NAME it "inherits" fmu-v2 and uses is different Linker script. We may be able to  to undef BOARD_NAME and redefine it. Then ripple that to the startup script

Done.

authors: LorenzMeier dagar davids5


text:
RTL back transition fix and default land delay of 0 for VTOL and MC

Fixes  #3936
@sanderux could you test this? I tested it against v1.2 which means the differences in mission item reached handling might have an impact but I can't see one ATM.
The problem was that the point of origin when starting the landing phase was where it came out of the back transition. So the position controller moves the vehicle from there to the landing point. This fix changes the way RTL works (as described, "simple solution" in #3936). It won't help with VTOL_LAND, but it might be the same issue.

Initial testing on this branch rebased on master shows VTOL_LAND exhibits strange behavior (crashes to ground) and regular vtol_transition to MC indefinitely reverses

This behavior now also seems to exist on master, might also be SITL.
Need to fix this first

Seems to be related to altitude of land WP. fixed by https://github.com/PX4/Firmware/pull/4184

My last commit fixes RTL back transition drift and makes the VTOL move to land again in MC mode at RTL altitude before descending / landing

I guess we should outdoor test this, will wait for that, thanks!

@sanderux Your last addition makes a good point, I had return and descent altitude always on the same height (in which case it didn't make a difference).

Rebased.
SITL test transition timeout succes:

SITL test RTL mode succes:

Addressed @LorenzMeier's comment.

Nice!

Is this ready to go in?

I think it is, have not test flown it outside though.
Building Prototype 2 of the DeltaQuad and the QuadRanger had a little swim so i have no platform at the moment :)

Rebased and applied, thanks!

authors: AndreasAntener LorenzMeier sanderux


text:
navigator: Takeoff and reposition lat/long already in degrees.

Param 5&6 is already scaled in COMMAND_INT handler, so scaling in navigator is bug, which is masked by NAN math.
Fixes issue #4844.

Thanks! I have a more complete fix. Just doing it this way will lead to fly-aways if the GCS and Firmware version are not in sync.

authors: LorenzMeier vooon


text:
voted_sensors_update: fix mag rotation

Yet another fix for mag rotations...
fixes a wrong index for _mag_device_id: previously, driver_index was used
(the CAL_MAG param index), but the correct index is the uorb topic
instance.
Tested on a setup where the board is 180deg rotated, but the external mag faces forward direction.
@mhkabir

@bkueng Thanks. What was the exact issue which you found? On what hardware?

OK, nevermind I see it now.

authors: bkueng mhkabir


text:
Fix mistakes done by PR #96

While backporting SocketCAN #96 this make.defs caused a net_dup.o compile error.
This PR fixes that error

Do you want to squash this into your original backport PR and I'll reset the testing branch?
https://github.com/PX4/NuttX/pull/96

I did do a force push on #96 which should make this PR obsolete

authors: PetervdPerk-NXP dagar


text:
If no .bam.pbi files for associated .bam files, then actc exits without outputting stderr or stdout

I noticed if there are no .bam.pbi files for associated input .bam files, then actc exits without outputting stderr or stdout (using https://github.com/PacificBiosciences/align-clr-to-ccs/releases/download/0.1.0/actc) on Debian 11 machine. A simple error message would be great as well as adding that to the documentation and how to generate the index with pbindex binary from bioconda package pbbam.

Thanks for the bug report. I will check and fix it.

I just checked and following checks are in place:
https://github.com/PacificBiosciences/actc/blob/main/src/main.cpp#L246-L251
https://github.com/PacificBiosciences/actc/blob/main/src/main.cpp#L292-L296

repo: PacificBiosciences/actc


text:
Configure result appearance

Hi. First off, this is a very nice program. Thanks for making and sharing it.
I would like to be able to configure how the end result is displayed. It would it nice if a config could be set to do so.
Currently, kalker displays results in the following manner.
> kalker 'sqrt(72)'
≈ 8.4852813742 ≈ √72

> kalker 'sqrt(72) + (5 * sqrt(26))'
≈ 33.9803789422

I would like to be able to specify that I want the exact result displayed first, and the approximation afterwards. This might also prevent this strange situation where the sqrt(72) I give as input is shown as approximately equal to √72.
I also want to be able to factor out perfect squares, so √72 becomes 6 * √2.
Lastly, I would also like to be able to modify how the multiplication symbol looks. kalker (at least the web version uses the dot operator ⋅ (U+22C5). qalc on the other hand uses the multiplication sign × (U+00D7). I would like to be able to choose between options for this. And the mode I'd prefer would likely be implied multiplication i.e. √72 = 6√2, for more complex results, brackets could be used for clarity but skipped for simpler results.
qalc output for comparison:
> qalc 'sqrt(72)'
sqrt(72) = 6 × √(2) ≈ 8.485281374

> qalc 'sqrt(72) + (5 * sqrt(26))'
sqrt(72) + (5 × sqrt(26)) = 5 × √(26) + 6 × √(2) ≈ 33.98037894

My preferred output form:
> kalker 'sqrt(72)'
= 6√2 ≈ 8.485281374

> kalker 'sqrt(72) + (5 * sqrt(26))'
= 5√26 + 6√2 ≈ 33.98037894

A further improvement would be being able to specify approximate results should be on a separate line.
> kalker 'sqrt(72)'
= 6√2
≈ 8.485281374

> kalker 'sqrt(72) + (5 * sqrt(26))'
= 5√26 + 6√2
≈ 33.98037894

At least for me, these look much cleaner. I'll look into seeing if I can contribute this change myself if you agree this feature is useful.

The reason for the current order is that the non-numerical results often are approximations themselves. For example, if you manually type 8.48528137, it's going to tell you that it's approximately sqrt72. In cases like this, I think it makes sense to place the numerical result first to show that it's the primary result. In other cases, where it's an exact result, it would make sense to place it first. However, I feel like it could be confusing if the order changes, so I'm not sure.
With something like this:
>> 1/2 + 1/3
≈ 0.8333333333 = 5/6

It would be clearer to present it as = 5/6 ≈ 0.833333333 instead... Hmm, so I guess it would make sense to have an option that makes it display the exact result first, regardless of if that's a number or a symbolic expression

Huh. I did as you said
> kalker '8.48528137'
= 8.48528137 ≈ √72

That's... interesting. Is such a characteristic desirable though? I mean if I put in an arbitrary non-integer number, I'm not sure how useful it is to me to be told that it is approximately equal to the square root of some other random number.
I could maybe see someone wanting to know which is the closest square root to some arbitrary non-integer number, but to make these approximations/comparisons by default seems a bit strange to me. I'm not aware of any other calculator that does this.
Using qalc for comparison again, I can see that it doesn't try to infer any other information from an arbirary non-integer that I give it, like which square root is it approximately equal to.
$ qalc
> sqrt(72)

  sqrt(72) = 6 × √(2) ≈ 8.485281374

> 8.485281374

  8.485281374 = 8 + 242640687/500000000

And on a tangent, I'm curious how this is working in kalker under the hood. Is there a small list of numbers hard-coded in the program itself so it immediately recognizes what number is approximately equal to sqrt(72). Seems unlikely. Does it crunch through a list of numbers until it finds a number who's square root matches the given non-integer. Also seems unlikely and probably too computationally intensive. Does it just cache previous results so that when I previously calculated sqrt(72) it just stored the approximation and matched it later when I typed in 8.48...?

It does this to be able to show you more descriptive results regardless of which steps you take to calculate it, without having to embed an entire complex CAS that can solve anything you give to it symbolically. With square roots it's quite simple since it can just square it and check if the result is an integer. With things like fractions, it uses some slightly more involved algorithms, but still quite simple, to figure it out. With constants it mostly just looks them up in a dictionary. Typically, you'd need a reaaally specific number to get the square root estimate, so pretty much in 99.9% of cases it's relevant, and when it's not, it doesn't hurt since it's still a true statement.
I think it is desirable, because it allows kalker to be much smaller and simpler than eg. WolframAlpha while still offering some of the functionality for a lot of use-cases in a really consistent way. The alternative would be to always just solve it symbolically, but then you wouldn't be able to rely on it giving you this information, since it realistically wouldn't be able to solve any expression you give to it symbolically. For example, now I could do something involved like Σ(n=1, 2, ∫(0, 2, 1/(sqrt2) dx)) and it can still easily figure out that the result is sqrt8, which qalc doesn't seem to for me at least, but even if it does it must have added a lot of complexity to the implementation. It's a compromise, but it ensures that kalker can keep being the smaller and simpler little brother of eg. WolframAlpha


text:
[Doc] Update doc for smoke

PR types(PR类型)

Doc
Description

Update doc for smoke

LGTM

repo: PaddlePaddle/FastDeploy


text:
caddn paddle模型

你好，请问方便分享caddn的模型文件么？

已经找到，谢谢

找到的预训练模型

我这边试了一下是可以正常导出的～
caddn模型需要编译paddle3d/ops下的自定义算子，可以检查一下看看是否编译。[https://bj.bcebos.com/paddle3d/pretrained/deeplabv3_resnet101.pdparams 只有一部分的模型参数，是用来初始化的，模型参数可以换成这个试试 https://paddle3d.bj.bcebos.com/caddn/model/paddle_caddn.pdparams
如果还是报错的话，可以发一下你的环境～

该issue较长时间无反馈，先关闭，如有问题请重新打开或者建立新的issue


text:
大规模提取特征速度慢

操作系统为ubuntu/centos
Python3.9
CUDA/cuDNN版本， 11.2
使用predict_rec,单卡T4，模型为Global_General_v2,batch=8,速度非常不稳定，3it/s-20s/it都有，同时gpu_utils较低，长期处在0

这边测试了一下对应环境下的运行情况，可以参考一下：
操作系统为ubuntu
Python3.9
CUDA/cuDNN版本， 11.2
单卡Tesla V100, 模型为Global_General_v2, batch=8
运行命令如下：
python3.9 python/predict_rec.py -c configs/inference_rec.yaml -o Global.infer_imgs="/dataset/ppshitu_testdata/images" -o Global.use_gpu=True -o Global.batch_size=8
速度相对于不同batch在60its-90its间：

gpu_utils在4%-9%间，测试结果正常。
建议检查：
1.是否启用GPU进行特征提取； （-o Global.use_gpu=True）
2.数据读取速度是否异常。https://github.com/PaddlePaddle/PaddleClas/blob/622a94eea97442ea23e0f0535378dc09c866b5ac/deploy/python/predict_rec.py#L111

repo: PaddlePaddle/PaddleClas


text:
Add elementwise_sub testcase.

增加elementwise sub动态图用例，包含int64， int32，float32，float16，bfloat16

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

authors: CLAassistant will-core

repo: PaddlePaddle/PaddleCustomDevice


text:
xpu服务器对应的paddlepaddle是cpu版本还是gpu版本呢

欢迎您反馈PaddleNLP使用问题，非常感谢您对PaddleNLP的贡献！
在留下您的问题时，辛苦您同步提供如下信息：

版本、环境信息
1）PaddleNLP和PaddlePaddle版本：请提供您的PaddleNLP和PaddlePaddle版本号，例如PaddleNLP 2.0.4，PaddlePaddle2.1.1
2）系统环境：请您描述系统类型，例如Linux/Windows/MacOS/，python版本
复现信息：如为报错，请给出复现环境、复现步骤

https://www.paddlepaddle.org.cn/documentation/docs/zh/guides/09_hardware_support/xpu_docs/paddle_install_cn.html
你好，xpu有特定的安装方式，具体安装如上。

XPU指的是昆仑芯片版本，属于ASIC芯片。@Clearloveplus7

Issue Close. If you have other questions, please feel free to reopen it.

authors: Clearloveplus7 ZeyuChen chenxiaozeng wawltor

repo: PaddlePaddle/PaddleNLP


text:
Fix/quotes issue

Description
Removed quotes for user options
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also
list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] The commit message/PR follows our guidelines

Other information:

will raise another PR for v1.5.0

repo: PaladinCloud/CE


text:
remove @BaseUrl and @DefaultHeaders decorators

This should be configurable at execution time

any proposed solutions?

Yes, what i mean here is that using variables instead decorators might be a better approach, much more flexible and code would not need to recompile if URL or any header needs to be changed.

@mjerez-radical what do you think about passing a function as @BaseUrl parameter like in PR #22 ?

authors: 0xE282B0 M-jerez auvipy mjerez-radical


text:
[EXPANDR-1880] Publish SDK to PyPI and ReadTheDocs

[EXPANDR-1880] Publish SDK to PyPI and ReadTheDocs

Used for testing release candidate

Motivation and Context

Used to test release candidate for external docs and pypi publication

How Has This Been Tested?

Test release to ReadTheDocs

https://readthedocs.org/projects/cortex-xpanse-python-sdk/builds/20863288/

Tests publication on pypi

https://pypi.org/project/xpanse/#history

Screenshots

I'm not seeing the more detailed info under the modules (see screenshot below). Is that on purpose? I think we have more details in the current version of the API docs:

I'm not seeing the more detailed info under the modules (see screenshot below). Is that on purpose? I think we have more details in the current version of the API docs:

@HilaryLynch-expanse woah, great catch. Not sure why that's happening on deployment but not locally. Taking a look

authors: HilaryLynch-expanse ben-expanse

license: ISC


text:
Double scrollbars on code tabs

Describe the bug

The code tab blocks have double scrollbars on each axis, making it difficult to navigate
Expected behavior

One scrollbar per axis.
Current behavior

Two scrollbars per axis.
Possible solution

This selector sets a max-width and max-height for code tags. Removing it fixes the issue, but I suppose it's purpose may be necessary to prevent random code blocks inserted from markdown from growing too big. Without knowing where those styles apply, a more specific selector would be less prone to break stuff.
Steps to reproduce

Visible here on the curl tab:
https://docusaurus-openapi.tryingpan.dev/petstore/create-users-with-list-input
Screenshots

https://user-images.githubusercontent.com/16181779/217860888-d54a53c4-cead-4e07-aa50-0f975cb8faf5.mov
Your Environment

Version used: v1.5.2
Environment name and version: Chrome Version 108.0.5359.124 (arm64)
Operating System and version (desktop or mobile): Mac M1

closed by #417


text:
23.20.1 - Removed Get Resource Snapshot API

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate)

Types of changes

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[ ] All new and existing tests passed.

https://redlock.atlassian.net/browse/RLP-114334


text:
children路由，出现hidden为true，router动态添加父路由后，hidden为true的添加后跳转出现空白页，hidden为false的正常

如图所示，这个是准备addRoutes的route，问题应该是出在，hidden为true的没有显示__ob__的属性出现空白界面的情形，而有__ob__的则是正常的

@tianlin95310 你好，我跟你一样遇到这样的问题，就是后台返回数据和前台map之后，侧边栏的展示全部正常，但是只要跳转就是空白的，请问您和我遇到的问题是一样么？
[     {         "path":"",         "redirect":"",         "component":"Layout",         "name":"Permission",         "hidden":false,         "meta":{             "title":"权限",             "icon":"lock",             "roles":[                 "admin"             ]         },         "children":[             {                 "path":"/admins",                 "redirect":"",                 "component":"admin",                 "name":"Admins",                 "hidden":false,                 "meta":{                     "title":"管理员",                     "roles":[                         "admin"                     ]                 }             },             {                 "path":"/roles",                 "redirect":"",                 "component":"role",                 "name":"Roles",                 "hidden":false,                 "meta":{                     "title":"角色",                     "roles":[                         "admin"                     ]                 }             },             {                 "path":"/menus",                 "redirect":"",                 "component":"menu",                 "name":"Menus",                 "hidden":false,                 "meta":{                     "title":"菜单",                     "roles":[                         "admin"                     ]                 }             }         ]     } ]
前台
`
export const routerMap = {
Layout:() => Layout,
admin:()  => import('@/views/permission/admin'),
role:()   => import('@/views/permission/role'),
menu:()   => import('@/views/permission/menu'),
pdf:()   => import('@/views/pdf/index')
}
`

你确定有问题的 路由 hidden 改为 false 就没有问题了么？

谢谢，找到问题了，是我的问题，你可以关闭了，感谢

你好.请问你的问题是怎样解决的呢.我现在也遇到了这个问题.动态添加的路由点击后空白

检查一下子路由里面的路径地址前面是否有加/

repo: PanJiaChen/vue-element-admin


text:
[CERTIFICATE]

Ask us to find free certificates in a specific field that you couldn't find here and we will add it.

I want to create a new certificate

New certificate

Sure thing! In that case you need to:

Fork this repo
Make the edits you want on the 'readme.md' file on your own repo that you just forked
Once done open a pull request back on PanXProject/awesome-certificates

Let me know if you need help.

authors: Dhvijp waleedsadek-panx

repo: PanXProject/awesome-certificates


text:
Change structure of pvi PV

At the moment we have a structure like:
$ pvget -v BL45P-MO-PANDA-01:TTLOUT1:PVI
BL45P-MO-PANDA-01:TTLOUT1:PVI structure
    structure record
        structure _options
            boolean atomic true
    structure pvi
        structure label
            string rw BL45P-MO-PANDA-01:TTLOUT1:LABEL
        structure val
            string rw BL45P-MO-PANDA-01:TTLOUT1:VAL
        structure val_delay
            string rw BL45P-MO-PANDA-01:TTLOUT1:VAL:DELAY

Which is very different from the underlying records:
$ pvget -v BL45P-MO-PANDA-01:TTLOUT1:VAL
BL45P-MO-PANDA-01:TTLOUT1:VAL epics:nt/NTScalar:1.0
    string value ZERO
    alarm_t alarm
        int severity 0
        int status 0
        string message
    time_t timeStamp 2024-06-08 15:34:04.600
        long secondsPastEpoch 1717857244
        int nanoseconds 600281953
        int userTag 0
    structure display
        string description TTL output value

It would be nicer to have value, alarm and timeStamp, and give it a structure ID. I suggest we do this:
$ pvget -v BL45P-MO-PANDA-01:TTLOUT1:PVI
BL45P-MO-PANDA-01:TTLOUT1:PVI epics:nt/NTPVI:1.0
    structure value
        structure label
            string rw BL45P-MO-PANDA-01:TTLOUT1:LABEL
        structure val
            string rw BL45P-MO-PANDA-01:TTLOUT1:VAL
        structure val_delay
            string rw BL45P-MO-PANDA-01:TTLOUT1:VAL:DELAY
    alarm_t alarm
        int severity 0
        int status 0
        string message
    time_t timeStamp 2024-06-08 15:34:04.600
        long secondsPastEpoch 1717857244
        int nanoseconds 600281953
        int userTag 0
    structure display
        string description PVs making up Interface for TTLOUT1

This would require:

Some structure to get the metadata into the root. Something like this when the first call to add_pvi_info_to_record happens:

        pvi_pv = f"{block}:PVI"
        description = builder.StringOut(
            pvi_pv + ":DESCRIPTION",
            initial_value=f"PVs making up Interface for {block}",
        )
        description.add_info(
            "Q:group",
            {
                pvi_pv: {
                    "+id": "epics:nt/NTPVI:1.0",
                    "display.description": {"+type": "plain", "+channel": "VAL"},
                    "": {"+type": "meta", "+channel": "VAL"}
                }
            },
        )

https://github.com/PandABlocks/PandABlocks-ioc/blob/8e25d64cc97cfbf242a84c6ccbe600a39ed41c41/src/pandablocks_ioc/_pvi.py#L63 to start with value. not pvi.

To be done after the June experiment is finished

repo: PandABlocks/PandABlocks-ioc


text:
Common Test

That's it.

Snapshot diff report

File name
Image

Snapshot diff report

File name
Image

co.kr.parkjonghun.roborazzi.compare.on.github.comment.MainActivityScreenshotTest.launch_compare.png

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report
There is no screenshot change exist in this pull request !

Snapshot diff report

File name
Image

co.kr.parkjonghun.roborazzi.compare.on.github.comment.MainActivityScreenshotTest.launch_compare.png

Snapshot diff report vs main

File name
Image

co.kr.parkjonghun.roborazzi.compare.on.github.comment.MainActivityScreenshotTest.launch_compare.png

Snapshot diff report vs main

File name
Image

co.kr.parkjonghun.roborazzi.compare.on.github.comment.MainActivityScreenshotTest.launch_compare.png


text:
[WIP] perf: Refactor underlying buffers for branchless access

This PR refactors the underlying InlineString and BoxString structs in a major way to allow for branch-less string accesses. It also renames these structs to InlineBuffer and HeapBuffer, treating these types strictly as "buffers". We also move string operations into Repr (e.g. pushing and popping), which de-dupes code.

Thanks for the review @NobodyXu! I'll update the PR soon with the feedback :)


text:
Livequery with jquery

I would like to use Livequery in my jquery app. I have the example on the parse website, but i am getting query.subscribe is not a function, please help

Please use Stack Overflow for implementation related questions.

repo: ParsePlatform/parse-server


text:
fix

Description
Please include a summary of the change and (optionally) which issue is fixed. Please also include
relevant motivation and context.
Fixes # (issue)
Type of change
Choose which options apply, and delete the ones which do not apply.

Bug fix (non-breaking change that fixes an issue)
New feature (non-breaking change that adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation update
Code maintentance/cleanup

this fixes an incorrect space in the previous PR to add the ND NSF badge

repo: Parsl/parsl


text:
Bug: Papiere werden nicht übernommen

Wenn Papiere in den Locher eingelegt werden und das Spiel neustartet sind diese dannach nicht mehr vorhanden. (-> Werden weder gespeichert noch in GUI beachtet)
Papiere sollten auch zwischne Spieldurchläufen vorhanden bleiben.

Debugging hat ergeben dass sie nur in der GUI gelöscht werden -> Logik Label entfernt

Fixed
https://github.com/PatrickSachs/sim-locher/commit/0efb33cfec70b4830a10ccfebe471c8b2eb6b95e
https://github.com/PatrickSachs/sim-locher/commit/a3b6f6fd37764a39b0bd3781d452d6e13ad7e6aa

repo: PatrickSachs/sim-locher


text:
您好，1.4.8版本无法用域名列表方式访问U2B和GOOGLE等网站

首先非常感谢！然后我只要用域名方式，像U2B、TWITTER、GOOGLE等常用网站均无法访问，默认插件安装完成时的域名列表和我把这几个网站加入白名单后的列表都无法访问，但是网页模式就很正常，我是极4 1.4.8，非常感谢

目前我手上的没经过1.4.8直接升到1.4.10了，正常。请问你是哪个型号？回头我找找看
m1a2sep notifications@github.com 于 2018年5月9日周三 上午11:52写道：

首先非常感谢！然后我只要用域名方式，像U2B、TWITTER、GOOGLE等常用网站均无法访问，默认插件安装完成时的域名列表已经我把这几个网站加入白名单都无法访问，但是网页模式就很正常，我是极4
1.4.8，非常感谢
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Paull/hiwifi.easucks/issues/51, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQrQjIPvAbqqgvPVX0-v55pd1HRR8QTks5twmfrgaJpZM4T3q5D
.

谢谢回复，我的是极4增强版，目前最高版本就是1.4.8.20462s

经测试，系统版本 : B70 - 1.4.8.20462s无此症状，请尝试恢复出厂后重新安装！

手工调试，在SSH试一下以下两个指令：
nslookup google.com和curl google.com
正常的输出如下：

谢谢您回复我试了上边方法跟图片显示的输出一样但是依然不能打开那些网站，我先用网页模式吧就，感谢您的帮忙

如果路由器上是这样的输出，那可能是终端有dns缓存，比如hosts之类的，多试几个终端对比下结果。


text:
Undefine Block Interface

I have installed POS, RMA plugins after that I get an error something like this "Undefine Block Interface Paybox"  when i use this plugin it gives me this errors
and when i edit the file and add this
"class Payment extends \Magento\Framework\View\Element\Template"
it works fine.
Let know if i'm right ?
I think this is the solution let know if you investigate about that?

investigate

Have modified this ?

authors: naseemqota nasimje


text:
Fix minimum for primenodes to allow syncing the old primestakes

Currently syncing a new wallet fails when reaching the first prime stake from the original primenodes because it's minimum is below the defined value.
This will use the new value only if the nTime is after the end of phase one when running ConnectInputs.

Can we get this merged so people running off their own build can sync a new wallet directory?

repo: PaycoinFoundation/paycoin


text:
Changed protocol version from 70003 to 70004

Splitting this from https://github.com/PaycoinFoundation/paycoinj/pull/16

LGTM

repo: PaycoinFoundation/paycoinj


text:
Chapter selection and login

buttons to link different chapters
login box

closes #133

localStorage needs specific arrays for each chapter's completed tasks. We will do that next. Merging.

authors: Honkajo thefakejj


text:
fix(perf): remove a nested loop in the tag list generation

This patch removes the nested loop in the generation of the tag list
alongside an article. It makes uses of the fact that tags is a
dictionary.
On my computer this reduces the generation time of the documentation
site from 73s to 70s.
(This PR is related to #145. Even though it removes the nested loop,
I feel that it does not fully close the issue because the generation
performance remains low. Someone will need to profile this again and
find out what is the next bottleneck.)
Informs #145

Coincidence! Just yesterday, I tried the same approach.
It does not give the correct result.

You can view the result of your PR here
https://deploy-preview-572--pelicanelegant.netlify.com/
I think this problem can either be solved by patching the Pelican core to return the count, or with the help of a plugin.
By the way, how do you propose to profile the theme?

By the way, how do you propose to profile the theme?

This would be done by profiling the entire pelican run.
But you're right, the problem here is that tag in the template is a string, whereas tags is indexed by Tag object.

BTW, let me know if you have faced any problem in starting to contribute to the project.
Our member, @jackdewinter has put extra efforts to make sure the contribution guidelines are detailed and easy to understand for the new contributors. If you think it can be improved in anyway, then let us know.
Secondly, I appreciate the fact that your commit follow the guidelines. Many users just don't follow or understand it. Thanks a lot.

BTW, let me know if you have faced any problem in starting to contribute to the project.

The main problem is to start using (or testing) elegant. There are simply too many commands and dependencies to run to build the documentation directory.
I would prefer if there was a single Makefile at the top so that I could run make test and have everything done for me.

Have you tried gulp? It is all set to compile CSS, JS and build the content. It even does live reload for you, if you make changes in templates, CSS, JS or the content.

gulp was easy for compiling the CSS and I found it quickly in the doc.
As I said my problem was setting up elegant for the first time and getting my first site up and running.

Hi @knz we created https://github.com/Pelican-Elegant/blog-o-matic to simplify the process by just requiring some setup and start blogging

@knz
I see. I think you mean all the configuration that is required to make Elegant work.
We have tried to

set defaults where ever possible
setup comprehensive docs
@iranzo blog-o-matic

Still, setting up Elegant is overwhelming for the new users. 😞

The thing is I am not interested in CI, github-pages integration etc. I want to set up and automate elegant for use on my own server that serves static files over HTTP.
In short I want a simple-to-use command on my computer to produce ready-to-publish files in the output/ directory.
All the automation that is proposed/documented so far does not provide this and only focuses on automating publication on "someone else's computer" (github).

When you create a new blog with Pelican, it generates a Makefile and a tasks.py file for you.
This makefile does all the things, compile, upload etc.
If you let us know how the Pelican generated Makefile did not help you, we will update our docs with the required information.

authors: iranzo knz talha131

repo: Pelican-Elegant/elegant


text:
TypeError: Object of type tensor is not JSON serializable

i ran a simple quantum circuit with pennylane-aqt and the i encountered this error.
raise TypeError(f'Object of type {o.class.name} '
TypeError: Object of type tensor is not JSON serializable

Hi @antalszava have installed the 0.15.0 version. i have to upgrade it to 0.19.0. How can i do this? i tried i couldn't.

If you're using pip, pip install pennylane-aqt --upgrade should work. :slightly_smiling_face: The most recent released version of this plugin is v0.18.0.

i did that. it didn't work.
raise TypeError(f'Object of type {o.class.name} '
TypeError: Object of type tensor is not JSON serializable

here is the circuit:
def ops(X):
qml.templates.MottonenStatePreparation(X, wires=[1, 2])

ops1 = qml.ctrl(ops, control=0)
@qml.qnode(dev)
def circuit(X1, X2):
qml.Hadamard(wires=0)

ops1(X1)

qml.PauliX(wires=0)

ops1(X2)

qml.PauliX(wires=0)

qml.Hadamard(wires=0)

return qml.expval(qml.PauliZ(0))

"/home/user/anaconda3/lib/python3.7/json/encoder.py", line 179, in default
raise TypeError(f'Object of type {o.class.name} '
TypeError: Object of type tensor is not JSON serializable

i ran the code with your input successfully. i think problem is after this part of code
D1 = []
for x1 in x1_train:
for x2 in X_test:
a = circuit(x1, x2)
D1.append(a)
D2 = []
for x1 in x2_train:
for x2 in X_test:
b = circuit(x1, x2)
D2.append(b)

Thanks! Could you send through x1_train, X_test and x2_train? All their minimalized versions that raise the error.

import numpy as np
import pennylane as qml
import matplotlib
import sklearn.datasets
import sklearn.decomposition
import math
from sklearn import metrics
from pennylane_aqt import ops
num_qubits = 3
dev = qml.device("aqt.noisy_sim", wires=num_qubits, shots=10, api_key = "")
data1 = np.loadtxt("CERVICAL-F16-REC-ORIGINAL-1x.txt") # import pandas as pd
#df = pd.read_csv (r'Path where the CSV file is stored\File name.csv')
data2 = np.loadtxt("CERVICAL-F16-REC-ORIGINAL-1y.txt") #
data3 = np.loadtxt("CERVICAL-F16-REC-ORIGINAL-1x-test.txt") #
data4 = np.loadtxt("CERVICAL-F16-REC-ORIGINAL-1y-test.txt") #
y_train= data2[:,]
X_train2=data1[:]
y_test= data4[:,]
X_test2=data3[:]
X_train1 = sklearn.preprocessing.normalize(X_train2, norm='l2',axis=0)
X_test1 = sklearn.preprocessing.normalize(X_test2, norm='l2', axis=0)
X_train = sklearn.preprocessing.normalize(X_train1, norm='l2',axis=1)
X_test = sklearn.preprocessing.normalize(X_test1, norm='l2', axis=1)
x1_train=[]
x2_train=[]
for i in range(len(X_train)):
if y_train[i]==1:
a=X_train[i]
x1_train.append(a)
else:
b=X_train[i]
x2_train.append(b)
def ops(X):
qml.templates.MottonenStatePreparation(X, wires=[1, 2])

ops1 = qml.ctrl(ops, control=0)
@qml.qnode(dev)
def circuit(X1, X2):
qml.Hadamard(wires=0)

ops1(X1)

qml.PauliX(wires=0)

ops1(X2)

qml.PauliX(wires=0)

qml.Hadamard(wires=0)

return qml.expval(qml.PauliZ(0))

D1 = []
for x1 in x1_train:
for x2 in X_test:
a = circuit(x1, x2)
D1.append(a)
D2 = []
for x1 in x2_train:
for x2 in X_test:
b = circuit(x1, x2)
D2.append(b)
D11 = np.reshape(D1, (len(x1_train), len(X_test)))
D22 = np.reshape(D2, (len(x2_train), len(X_test)))
d11 = np.max(D11, axis=0)
d22 = np.max(D22, axis=0)
m = len(X_test)
Prediction=[]
for i in range(m):
if d11[i] >= d22[i]:
Prediction.append(1)
else:
Prediction.append(0)
BB = metrics.confusion_matrix(y_test, Prediction, labels=[0,1])
print(Prediction)
print(BB)
#print(wires, type(wires))

x-special/nautilus-clipboard
copy
file:///home/smoradi/Videos/mri/video/DATA/noise/bONEDATA/BONEMARROW-F16-ORIGINAL/iris2/CERVICAL-F16-REC-ORIGINAL-1x.txt
file:///home/smoradi/Videos/mri/video/DATA/noise/bONEDATA/BONEMARROW-F16-ORIGINAL/iris2/CERVICAL-F16-REC-ORIGINAL-1x-test.txt
file:///home/smoradi/Videos/mri/video/DATA/noise/bONEDATA/BONEMARROW-F16-ORIGINAL/iris2/CERVICAL-F16-REC-ORIGINAL-1y.txt
file:///home/smoradi/Videos/mri/video/DATA/noise/bONEDATA/BONEMARROW-F16-ORIGINAL/iris2/CERVICAL-F16-REC-ORIGINAL-1y-test.txt

i don't know how to attach the data?

data are iris dataset.

CERVICAL-F16-REC-ORIGINAL-1y-test.txt
CERVICAL-F16-REC-ORIGINAL-1y.txt
CERVICAL-F16-REC-ORIGINAL-1x-test.txt
CERVICAL-F16-REC-ORIGINAL-1x.txt

many thanks in advance.

Hi @sassan72 , what Python version are you using? It might help to create a new virtual environment with Python 3.9 and install the libraries you need there.
Please let me know if this solves your issue or if it persists.

Python 3.7.7

Hi @sassan72, Python 3.7 should work. Sometimes if you create a new virtual environment and install only the libraries you need it can solve your problem. If you try this option does the problem get fixed?

i will try with it and get back to you.

Sure! If you're using conda you can do conda create --name <your virtual environment name> python=3.9. You can try with Python 3.7 or 3.9 and see if that works.

thanks. i did it. i got this error.
File "/home/user/anaconda3/envs/sasan/lib/python3.9/site-packages/requests/adapters.py", line 532, in send
raise ReadTimeout(e, request=request)
requests.exceptions.ReadTimeout: HTTPSConnectionPool(host='gateway.aqt.eu', port=443): Read timed out. (read timeout=1.0)

Or something like
try:
    a = circuit(x1, x2)
except requests.TimeoutError:
    time.sleep(5)
    try:
        a = circuit(x1, x2)
    except requests.TimeoutError:
        time.sleep(5)
        a = circuit(x1, x2)

Or better written than that.

No worries, glad it worked out! :slightly_smiling_face:

repo: PennyLaneAI/pennylane-aqt