SSL

Hello, quick question, does your library have ssl support? I've been using the same to do my http requests but in this app am undertaking i will be required to implement using https to enhance security. So does the library support secure requests? am using ssl.

Yes, this "library", is actually a port of official httpclient library from Apache, and it does support SSL in the same way as the official library does.


Use more descriptive dimension/axis labels for ResultSet logs storage now that AxisKeys is in use

https://github.com/open-AIMS/ADRIA.jl/blob/de4399c1ec5127c9835857aaef21e6e7acd6df8d/src/io/ResultSet.jl#L66-L70
For example, the above uses indices to name axes (such as interventions = (1,2)). More descriptive names such as interventions = ("seed","shade") are more understandable and consistent with other parts of ADRIA.

This issue to be delayed until #528 is in, then reassessed.

@ConnectedSystems  @Rosejoycrocker  Does this issue still make sense?

@Zapiano we need to add relevant metadata to the Zarr data store, and then load it into the ResultSet type on load_results().
If this is already done, then I think this issue is resolved and can be closed.


Loading images from app bundle on iOS still broken in 0.1.175

Description
@wcandillon @chrfalch  Unfortunately https://github.com/Shopify/react-native-skia/commit/8046939e15ffc755d0193086b69ef5f756ccc16d doesn't appear to have fixed loading images from the app bundle on iOS. After upgrading to 0.1.175 useImage still errors with [Error: Could not load data].
See https://github.com/Shopify/react-native-skia/issues/861
Perhaps the test case isn't testing exactly what it's supposed to?
Version
0.1.175
Steps to reproduce
Install 0.1.175
Load an image from the app xcassets on iOS (specify filename with no extension)
Observe error in callback and no rendered image
Snack, code example, screenshot, or link to a repository
Reopens https://github.com/Shopify/react-native-skia/issues/861

To double check I have verified that the image is indeed in the bundle and can be loaded by the normal react-native Image component. If it helps, the Contents.json I generate for each image looks like this
{
  "images" : [
    {
      "idiom" : "universal",
      "filename" : "hands4.png",
      "scale" : "1x"
    },
    {
      "idiom" : "universal",
      "scale" : "2x"
    },
    {
      "idiom" : "universal",
      "scale" : "3x"
    }
  ],
  "info" : {
    "version" : 1,
    "author" : "xcode"
  }
}

just to be sure because you are not providing us with a code snippet, the signature is different from RN Image: https://shopify.github.io/react-native-skia/docs/images#loading-images
Can you provide us with a code snippet and/or a small repo maybe?

Sorry, I was mistaken, none of my assets are getting copied into my app bundle since I upgraded a couple of other packages. I'm working to figure out why that is now. Once I've resolved that I'll test skia again and it will likely work fine and I'll close this issue. Sorry for the issue noise. If something is still wrong I'll provide a more detailed reproduction here.

OK everything works fine, the issue was a silent failure in my build process causing the images to be copied but to the wrong folder. Sorry again for the error noise and thanks for the quick fix on bundled assets!


New openwechat org

Reopen from #20,
I still think it is a good idea to create a new openwechat GH organization, put openwechat under it, and collect all different sample/demo projects there as well.
So the next person who comes along, can just pick and choose which sample/demo projects to start with, or know which demo projects to turn to troubleshoot (without the need to hunt for it), like having more insight into the login handshaking.

My owc-insight, OpenWeChat Insight, was meant for that.
The reason I now think it is necessary is partly because,
In my Emacs lsp-log buffer, I saw the error message of
imports fixes: AllImportsFixes: /home/me/l/gg/suntong/owc-insight/main.go:15:16: expected 'STRING', found string (and 20 more errors)
	file="/home/me/l/gg/suntong/owc-insight/main.go"

which is pointing to (15:16):
	"github.com/eatMoreApple/openwechat"
	 -------------^

I.e., my Emacs lsp thinks something wrong with the name of eatMoreApple,
Don't know how valid it is ,and if the unusual uppercase package name has anything to do with the problem.

FYI, from https://github.com/xo/xo/issues/281#issuecomment-881071374

I would like to point out that idiomatically, Go package names should be all lower case.

这样吗？..... 确实我这个名字取的不太好，在go  cache文件里面都有符号出现..

这样吗？..... 确实我这个名字取的不太好，在go  cache文件夹里面都有符号出现..

Let's do it sooner than later! thx!

I would like to point out that idiomatically, Go package names should be all lower case.

哈哈哈, 确实, 我就是应该这原因把 username 全小写了

@eatmoreapple
老大对这个建议怎么看？
近期内会做吗？
需要我帮什么忙吗？

包名已经都转小写了

@eatmoreapple
老大对这个建议怎么看？
近期内会做吗？
需要我帮什么忙吗？

这个我不太会玩，该怎么做呢

Oh, OK. See
Creating a new organization from scratch
https://help.github.com/articles/creating-a-new-organization-from-scratch/
But I've done that for you and invited you as the owner.
The next step is important -- Transferring a repository. Do

git pull locally, as local backup
follow Transferring a repository @ https://help.github.com/articles/transferring-a-repository/
fix git remote or do a brand new git clone from new repo

This is how I'm transferring mine FYI:

BTW, GH will redirect all old request (http / git) to new place. E.g., https://github.com/suntong/owc-insight/ still works, but now redirected to https://github.com/go-openwechat/owc-insight.


No processor running or created

What did you do?
I created a simple changefeed and try to query processor but seem like there is no processor and nothing is running.
cdc cli changefeed create --sink-uri=local://testdir
cdc cli processor query -c cc62858d-3abb-4018-b14a-af09a675cb8c -p 26833d6e-43cb-4bcd-a101-938897f658bb
The output of processor query is:
[CDC:ErrTaskPositionNotExists]task position not exists, key: /tidb/cdc/task/position/26833d6e-43cb-4bcd-a101-938897f658bb/cc62858d-3abb-4018-b14a-af09a675cb8c
I tried to check in PD and there is no any keys under /tidb/cdc/task/position/
What did you expect to see?
Changefeed is running and tso property is updated realtime.
What did you see instead?
changefeed list respond a stable tso property and replication lag time is keep increasing until it's over gc-ttl value.
Versions of the cluster
TiDB version: 5.2.1
TiCDC version: 5.2.1

This bug is fixed in PR https://github.com/pingcap/tiflow/pull/4052

@truong-hua , Is the changefeed list abnormality related to this bug as well?

thank @zhaoxinyu , I found out that the issue is related to high workload of our nodes so that seem ike TiCDC take a longer time to create a new processor. After the workload is reduced, TiCDC is working well as new processor is running.


WP3 Validation of process metadata: test_process_metadata_functional() should ignore non-functional metadata in parameter schema

test_process_metadata_functions() from src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py, check values within functional and non-functional parameters. For example, this function also tests for description, which is present in the schema parameter. Like"id": "array_append", "parameters": [     {           "description": "Value to append to the array.",           "name": "value",           "schema": {             "description": "Any data type is allowed."     }     }

This should not happen if -m "not optional" is added to the command.

non-functional parameters are skipped with -m "not optional". The longrunning marker has nothing to do with process metadata.
See the docs in readme about "WP3 Validation of process metadata":

Non-functional tests concern descriptions and other metadata of processes that have no impact on the actual behavior of the process, failures in these tests should be taken as warnings, but don't necessarily need to be fixed. These can be skipped by adding -m "not optional" to the pytest command.

There's was a mistake in last sentence. I have made the edit.

ok, I understand now, you are talking about non-functional fields in the schema of process parameters. The parameter's schema  is indeed being compared as a whole currently:
https://github.com/Open-EO/openeo-test-suite/blob/5b9727d6b6b8a05672bcdd1aafd0a289f32a472a/src/openeo_test_suite/tests/processes/metadata/test_process_metadata.py#L79-L80
Do you have some concrete examples of differing parameter schema's?

A couple of examples where even schemas are meant to be updated by implementations:

https://processes.openeo.org/#resample_spatial (method, more specifically the enum and description)
https://processes.openeo.org/#ard_normalized_radar_backscatter and https://processes.openeo.org/#sar_backscatter (options parameter)
https://processes.openeo.org/#ard_surface_reflectance (atmospheric_correction_options and cloud_detection_options)
...


Add URL copy/paster to left sidebar

What's this PR do?
Adds a URL container to the left sidebar that displays the URL of the active organization and copies it to the clipboard automatically.
Entering a URL into the container makes the app check if the domain is already saved and then switch to the relevant tab if that's the case.
Any background context you want to provide?
Check out #578 for the same.
Screenshots?

Possible improvements
#578 shows a suggestion for a copy button. I couldn't design it as intended (inside the input field), and I think it could make for a nice improvement.
You have tested this PR on:

[x] Windows
[ ] Linux/Ubuntu
[ ] macOS

Hello, just checking in to ask if any changes are required here. :)

@kanishk98 Is the copying limited to just the server name or does it also show the topic or stream part?
While pasting does it go to the the narrow view if we paste a link of a narrow or just focuses on the correct org?

Is the copying limited to just the server name or does it also show the topic or stream part?

It's limited to the server URL only.

While pasting does it go to the the narrow view if we paste a link of a narrow or just focuses on the correct org?

There's no web-based stuff involved here. So it'll simply change tabs to another server if the URL of an already saved URL is pasted into the field.
Currently, if a URL belonging to a server that has not been saved is pasted into the field, the app doesn't do anything. I didn't want to add an indication without a discussion.

It's limited to the server URL only.

Okay, understood. I am not sure if that servers us much purpose here, I mean the chances of someone pasting chat.zulip.org in a toolbar to open the issue would be a very rare case I suppose, unless someone has like 20-30 added organizations (again a very very rare case, max I have seen is about 12).
Typically the use case would be as mentioned in the issue would be to narrow into a view after pasting an url, since it would help people directly opening links from browser or emails (this needs to be done very very carefully as can lead to attacks).

if a URL belonging to a server that has not been saved is pasted into the field, the app doesn't do anything.

This can simple like showing a red exclamation icon or a red boundary - something that websites do to show incorrect passwords dynamically.

Typically the use case would be as mentioned in the issue would be to narrow into a view after pasting an url, since it would help people directly opening links from browser or emails (this needs to be done very very carefully as can lead to attacks).

Alright, I understand. I'm going to get back to #470 after submitting my proposal. Fixing that would solve this issue too.

This can simple like showing a red exclamation icon or a red boundary - something that websites do to show incorrect passwords dynamically.

Easy enough. I'll do this as soon as I can.
Thanks for the review.

This can simple like showing a red exclamation icon or a red boundary - something that websites do to show incorrect passwords dynamically.

Done and pushed. Works as shown below.

I've already implemented the desired redirection in #716. I think I should wait for a proper review on that before using the same logic here. We can just merge both of them then.


Implement distribution_type for probablisitic measures

#124

Codecov Report

Merging #134 into dev will decrease coverage by 1.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##              dev     #134      +/-   ##
==========================================
- Coverage   76.22%   75.06%   -1.16%
==========================================
  Files          21       21
  Lines        1106     1099       -7
==========================================
- Hits          843      825      -18
- Misses        263      274      +11

Impacted Files
Coverage Δ

src/measures/measures.jl
72.5% <ø> (-0.68%)
:arrow_down:

src/measures/continuous.jl
100% <ø> (ø)
:arrow_up:

src/metadata_utilities.jl
100% <100%> (ø)
:arrow_up:

src/measures/finite.jl
96.57% <100%> (-2.86%)
:arrow_down:

src/MLJBase.jl
50% <0%> (-25%)
:arrow_down:

src/datasets.jl
87.5% <0%> (-6.25%)
:arrow_down:

src/measures/loss_functions_interface.jl
94.73% <0%> (-5.27%)
:arrow_down:

src/equality.jl
50% <0%> (-5%)
:arrow_down:

src/data.jl
94.49% <0%> (-0.1%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

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


Simple list of WebCams

Tomáš Borov says:
The new function, that replace the real thumbnails with the nice material images is not so "cool" ;-) Please add only the simple listview if the real thumbnails are disabled.

If the title is long, then collide with options button. Need to be fixed before final release!

Fixed, now!


MD024/no-duplicate-heading regression in 0.11.0

Configuration file .markdownlint-cli2.jsonc with
		//MD024
		"no-duplicate-header": {
			"allow_different_nesting": true
		},

When using version 0.10.0, no errors are found.
When using new version 0.11.0, errors with following are found docs/diagnostika_a_statistiky/sp_monitoring_a_statistiky/konfigurace.md:49 MD024/no-duplicate-heading Multiple headings with the same content [Context: "##### COM port"]
I don't expect these errors to be found, when MD024 should be ignored.

The “header” aliases for rules like MD024/no-duplicate-heading have been deprecated since v0.9.0 of the markdownlint library released in May of 2018. (The change was made to fix https://github.com/DavidAnson/markdownlint/issues/113 which pointed out the correct term is “heading”.) Version v0.32.0 of the markdownlint library removed the deprecated “header” aliases. Therefore, rules like this need to referred to by their “heading” alias or by rule name. Please update your configuration to resolve the issue. Thank you!

@DavidAnson thank you for explanation. Would it be possible to implement some sort of configuration validation ? I mean, if linter would told me, this configuration item is deprecated, I would try to search for reason why.

I don't know how big of a problem this will be yet. I have a few ideas if it becomes prominent.
FYI, there is already a schema that can be used to validate configuration: https://github.com/DavidAnson/markdownlint-cli2/tree/main/schema. And it is applied automatically when using the VS Code extension for markdownlint.


Source maps are broken for user's ServerSession subclasses

Occurs for all files with a @remote decorator (those are modified in the restfuncs-transformer stage).
I think, there won't be an easy fix for this soon, or we need someone who's really familiar with the tsc compiler internals.
See this discussion.

I think, the precise problem is in: transformer/index.ts:
compilerHost.fileCache.set(sourceFile.fileName, updatedSourceFile);
from there on, the compiler takes this as the original file and i think, there's no way, you could provide a (let's say:) originalSourceFile.ts -> updatedSourceFile.ts source map there. So you'd kind of have the grab the generated code (either from the generated AST, during visiting, or by a diff afterwards) and squeeze all that code into one line inside the original file content at the correct position. Not quiet easy...

/reward 200

Bugfix was released in restfuncs-transformer 1.1.0


[Foundation Future] CSS Grids - Answer to two dimensional layouts

https://github.com/zurb/foundation-sites/wiki/Project-Roadmap#other-things-to-investigateschedule

Other Things to Investigate/Schedule

CSS Grid - Not sure what the timeline is on this but we should target this, perhaps similar to flexbox mode?

CSS Grids has landed a week back first in firefox, and then in chrome, safari and opera
I am opening this thread for the discussion on this awesome layout monster!
( This might be very soon, but better to be early than late! )

Quick Overview => https://www.slideshare.net/rachelandrew/talk-web-design-css-grid-layout

Complete Guide => https://webkit.org/blog/7434/css-grid-layout-a-new-layout-module-for-the-web/

Grid by example => http://gridbyexample.com/

What mozilla says => https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Grid_Layout/CSS_Grid_and_Progressive_Enhancement

Yes or no to IE and its old spec => https://rachelandrew.co.uk/archives/2016/11/26/should-i-try-to-use-the-ie-implementation-of-css-grid-layout/

Feature Queries => https://hacks.mozilla.org/2016/08/using-feature-queries-in-css/

Update: Well its so co-incidental ..... that when i posted this thread,
Zurb was already working on this on a youtube video :smiling_imp:  => https://youtu.be/bI1wNuvuFxo
Maybe its because both zurb and community wants the advancements! Right ??

https://rachelandrew.co.uk/archives/2016/03/30/should-i-use-grid-or-flexbox/

This is how flexbox works. However, most of the flexbox problems I am asked about are due to developers trying to make flexbox do layout in two dimensions. This is where you need Grid Layout.

The prevailing advice seems to be to not co-opt CSS Grid into frameworks like this (emphasis mine):

I know a lot of people will think the “best” way to use CSS Grid will be to download the new version of Bootstrap (version 5! now with Grid!), or to use any one of a number of CSS Grid layout frameworks that people are inevitably going to make later this year (despite Rachel Andrew and I begging everyone not to). But I don’t. The more I use CSS Grid, the more convinced I am that there is no benefit to be had by adding a layer of abstraction over it. CSS Grid is the layout framework. Baked right into the browser.

— http://jensimmons.com/post/feb-28-2017/benefits-learning-how-code-layouts-css

@orangedaisy very good point. Grid should really be used as the base layout for a page and inside this grid rows and columns from foundation can work very nice. Even with flexbox I'm not sure if there is any need for grids anymore. There are a lot of flexbox features that are very hard to put into css-classes by using foundation-flexbox grid it's only possible to use a very small part of flexbox.
The most important thing is, that flexbox and css-grid solve different layout needs. So they should be used in combination not like flexbox mode at the moment.

The most important thing is, that flexbox and css-grid solve different layout needs. So they should be used in combination not like flexbox mode at the moment

@DaSchTour :+1: :+1: :+1: :+1: ....... A trillion :+1:
One dimensional Layout => Flexbox
Two dimensional Layout => CSS Grids

Grid is way more intricate – it would be more difficult to create a class-based system than just advising users to use Grid itself.

@orangedaisy  =We are talking advanced layouts here, we should not create classes, Infact there are so many properties, there is no way we can create classes,
I feels Sass Mixins are the best way to go about.
For example,
@include grid-wrapper (
  $row : 100px 1fr auto,
  $column : 1fr 200px,
  $gap: 10px 20px,
  $align: center,
  $justify: space-evenly,
  $areas: "header  header"
          "content aside "
          "footer  aside ",
)
@include grid-box (
 $row : 1/3,
 $column: 2/4
)

Tagging you @corysimmons because Looking at this Feature Queries example by mozilla,
I have got one deep question in mind,
Can there be a combo of something like { Calc Grids + Feature Queries + CSS Grids }

@IamManchanda Creating mixins like this is, I'm sorry to say, a fool's errand. You're just recreating the browser's built-in functionality. How is that helpful?

@orangedaisy ohk so what's best way out according to you ?

@IamManchanda Not doing it at all? It doesn't matter what you do – classes, mixins, functions, etc – you're just going to be increasing complexity and recreating something the browser already does. It's like that gradient mixin from a couple of weeks ago: the browser already does this. There's no need to make it more complicated.

ohk @orangedaisy
But i have my two cents on it!
Deep down in my head, I have a thing that coming to my mind

Calc Grids + Feature Queries + CSS Grids Spec

So, I will wait for @corysimmons comment for the same
Reason:
https://github.com/corysimmons/postcss-ant#what-about-grid-spec

Fun Fact: Grid Spec's API was developed independently of postcss-ant's. Any similarities with how size setting works (e.g. fixed takes precedence over fr) is completely by coincidence and a testament to how good of an idea these new ideas about sizing are.

You should not be trying to recreate the Grid spec. I don't understand what any of this has to do with Cory's postcss plugin.

@orangedaisy coz i have followed his work!!!
https://corysimmons.com/

This site was designed with a golden ratio grid using a PostCSS layout plugin I made that mimics much of CSS Grid Spec but works seamlessly in IE9

If you want I can do a grid with a setting so developers serving different audiences can pick and choose based on their needs. For instance, if you don't need centering or equal height, you should use float just for browser support.
$grid-type could take:

float
inline-block
flexbox
grid-layout

I think something that makes my postcss-ant project different is that it makes working with real ratios incredibly easy.
I think it'd be interesting if Foundation migrated to PostCSS. You guys are missing out on so much power vs JavaScript. PostCSS projects also work with any CSS preprocessor, or just vanilla CSS, and compile much faster than other preprocessors.
🍕 for thought.

Yes excited and two version 7

Game of Thrones Season 7
Foundation for sites 7

If you want I can do a grid with a setting so developers serving different audiences can pick and choose based on their needs. For instance, if you don't need centering or equal height, you should use float just for browser support.

@corysimmons To let you know, we are dropping IE9  ...
My 2 cents
What maybe great as a fallback to CSS Grids i feel would be Calc combined with feature queries because both have almost similar browser support. Calc | Feature Queries. I feel that these two have good browser support specially considering foundation 7 will be around there about end 2017/early 2018.
Flexbox ofcourse will be there in there about as its FLEXBOX
Yes opera mini and UC browser is a concern though as far as browser support is concerned!

I think it'd be interesting if Foundation migrated to PostCSS. You guys are missing out on so much power vs JavaScript. PostCSS projects also work with any CSS preprocessor, or just vanilla CSS, and compile much faster than other preprocessors.

I don't know ... to be advanced is very important but i love sass so its hard and emotional for me to comment on.... will tag @kball on answering this !

I should be explicit. When I say "IE9+", I don't mean "We need to support IE9 guys!"
Flexbox is full of bugs and no one seems to care about an old browser user (0.5%?) here and there. But those small percentages of users missing support add up quick and you end up with a broken site for something like 5% of users.
So when I say "IE9+", I'm just pointing out that it'd work in 99.9% of browsers seamlessly.

Flexbox is full of bugs and no one seems to care about an old browser user (0.5%?) here and there. But those small percentages of users missing support add up quick and you end up with a broken site for something like 5% of users.

You nailed it but most bugs are only there in flexbox because people wanna use flexbox for two dimensional layouts.

People use flexbox for everything. It'd work if there weren't so many bugs, but the bugs are there, and they get worse as you nest and the more things you try to do with it.
I'm speaking from real-world experience walking into a dozen sites that were about to launch. The client reviewed them on Safari (version was less than a year old) and opened dozens of requests to fix various things. As I fixed them, they introduced other bugs in other browsers. This dance took forever.
Flexbox has its place, but the bugs make it nearly unusable for me.
I suspect grid layout will suffer the same fate. Only time will tell.
Hence I'd suggest making what type of grid you're using a setting, and preferably defaulting to float-based (e.g. bulletproof) layouts.

Poke @kball @rafibomb!

Update: When i created this thread ... browser support was mere 6% ( including that ms grid )
22 days and now its 37% .... Now that's a real push!!!!!
( Expect it soon to go 20 more aka when people update Chrome 56)
Concern: IE/Edge, Mobile browsers (Android webview, Opera mini, UC, Samsung)
Source: http://caniuse.com/#feat=css-grid

@IamManchanda Microsoft have started work on updating their implementation. (source)

Vendors promise they'll implement a semi-complicated spec correctly before universe heat death. 👍 💯

👋

I tend to agree that CSS grid will need to be opt-in for a while, however I think we should make it easy to adopt... We've got a draft of a CSS-grid based version of the base Foundation grid in progress that we'll use as a stopgap for 6.4, but we really should be discussion not if to use grid bot rather what the world will look like when grid is widely enough supported.
Broadly speaking, I think what this is hinting towards is a world where our "grids" are less architectural choices but more componentized, able to be picked and chosen... but I could be wrong.
I think @corysimmons makes a great point that grids (and technology standards such as flexbox, css grid, and some the other new hotness) should be configurable on/off... Our current binary float/flex approach is pretty cludgy, but works well enough for 2 systems. If we imagine 4, 5, or 6 different grid options, what do y'all think this should this look like moving forward?

If we imagine 4, 5, or 6 different grid options, what do y'all think this should this look like moving forward?

In one word => Bloat

@IamManchanda possibly... but the question I'd ask is... do grid systems need to be as complex and encompassing as they tend to be today, or should we be thinking of grids more like components that can be contained and mixed and matched?

Output wouldn't be bloat, but asking people to memorize more settings is just cruel.
I still think you guys are in the unique position to force grid layout on vendors so everyone can be done with layout obfuscations forever. I'll rename my 1st born to "Zurb".

Sorry but its too early .... for me best solution would be to delay foundation 7 to  early-mid 2018 so that the grid gets good browser support and we can implement one solution grid system!
What do you guys think ??

Honestly at this point, I'd just make a simple flexbox grid. Maybe spice it up with some ratio-sizing mixin.

I actually tend to agree for the base case... @brettsmason is working on a simple flexbox grid... Brett  is http://codepen.io/brettsmason/pen/RKMbZG the latest example of what you've been playing with?

That's the one...
 Adding bg color to a row: row > cell-with-bg > row > cells
@IamManchanda Can you give me a thumbs up on this comment?

@kball @brettsmason I'll make you guys a ratio-sizing mixin thing if I get a chance. Or I could pseudo-code it and you could implement it however you'd like. It'd make your grid unique without ruffling feathers.

@kball Sorry for the delay,  I'm away at the moment. So to be honest I haven't progressed anything with the grid, mainly due to lack of feedback on stuff so not knowing what direction to take.
I agree with @corysimmons on a lot of what he said. I've been looking into margin based grids recently and like the idea, but not sure how it would go down with users who have been using padding for so long? I think an option to switch between padding or margin would be good, but might make things too complicated. Whatever is the cleanest and easiest for the end user to implement would be my choice.
Id love to properly discuss it and get a feature list agreed so we can move it forward.

I think a good test of how complicated/hard-to-use a grid is, is to apply various background colors to things—specifically rows.
Here's how I'd do margin: https://codepen.io/corysimmons/pen/eWpVBN
Let me know how you'd do it with padding.

@corysimmons Yeah that's a lot like a simple CodePen I put together when experimenting with ideas, and I agree is nice. What are your thoughts on including the margin on one side (left)? eg: https://codepen.io/brettsmason/pen/jmWVNe
The main reason being there is no overflow then if the grid is the full width of the browser window.
I'd really like the grid to be based on a simple selection of mixins (current mixins aren't the best in my opinion) that are easy and intuitive to use but flexible too. I came from using Susy, so I guess that would be my inspiration.
You know far more about it though so I'd value your opinion.

Single-side margins are less flexible than double side, but, yes, they are really clean.
You need to know how many elements are going to go in a row. Here's an example: https://codepen.io/corysimmons/pen/GmoWGr?editors=1100
I've fought to use the single-side gutter for a long time (Jeet, Lost) because it made more sense than doing some weird overhanging negative-margin stuff. But it has a lot of fringe cases (masonry, breaking if you need to change a one-off item, etc.).
With double-sided gutters you can plop anything anywhere and it'll JustWork™. In Lost and postcss-ant—which really is the pinnacle of losing everything to my obsession with this stuff—I offered both approaches.
But honestly, I think it adds too much stuff for people to remember, especially for a framework like Foundation, so I'd simplify and just keep negative-margin/double-gutter grids in all cases.

I'm still interested in a CodePen of how you'd apply a background color to a row, and a different background color to columns, using a padding approach though.

Thanks, that's helpful and I hadn't thought about things like Masonry use etc. Sounds like double-sided should be what we stick with on that front.
In terms of background colour for rows/columns - the only way is with extra markup as far as I know, eg https://codepen.io/brettsmason/pen/ZKQKEZ
What would you say are the negatives of using a margin based approach? I'm sold on it, but just want to make sure everything is covered.

Add body { padding: 30px; }. Notice the springgreen overhanging (i.e. not flush with cells as expected).

Negatives of dub-guts (what I'm calling them now because it sounds like a cool zombie name) are  it does some negative-margin stuff which can cause overhang issues, but the worst thing is nesting.
I've found people don't do a ton of nesting so it's less of an issue than I've made it out to be, but it still sucks when single-gut grids can nest w/o extra markup like so:

1

2

    3

Pros and cons to everything, which is why I threw my hands up and just began offering everything.

Ah OK great - I see the problem with that now 👍
My main aim would be to get rid of the madness that is the current nested, overly specific classes, and get away from things like this: https://github.com/zurb/foundation-sites/issues/995
@kball @rafibomb what do you think? I guess it could potentially be a breaking change, but we have never shied away from moving things forward.
I'd propose that for 6.4 we completely rework the flex grid to be a margin based grid and ditch padding. I've already done a lot of the work, but I'd need a decision on if this would be OK?
Grid layout looks great, but unfortunately for people like me who wont be able to use it in my every day work, it wont really solve anything for now.

Grid layout looks great, but unfortunately for people like me who wont be able to use it in my every day work, it wont really solve anything for now.

Fair enough, and tbh, Foundation probably shouldn't even abstract Grid Layout's API.

To do the margin stuff, you'd need some control over gutter on a global, and per-row basis, via a mixin.

Yeah agreed - I think people should be encouraged to learn the API, no need to get involved 👍
I'll get together what I've done so far and get it online somewhere for you to see, assuming its given the go ahead.

@brettsmason I'm down with breaking change, but prefer we go through a deprecation cycle to do it, so that we don't completely block folks who want to upgrade but need more time.
A tentative proposal would look something like this:

We create the new margin-based flex grid as an independent mixin using a 'zf-' namespace (we want to move all of our SCSS to namespacing anyway)
We make the new grid the default (we want to make Flex the default anyway, this would really jump us forward)
We write a migration guide (how to move from old flex grid to the new grid)
We provide a way for someone to opt back to the old flex grid with a deprecation warning that it will be dropped in 6.5.

Thoughts?

@kball ok thanks, I think that makes sense.
And what about the margin based approach? Foundation has always used padding so it would be a fairly big shift.

Yes fairly big shift but that's ohk with an Avanced and bold framework like foundation!

As mentioned above - big shifts are fine with me if they move us in the right direction and we give folks a path and adjustment period.
That said, I'd be interested in some of the opinions of more SCSS & design focused folks like @gakimball @tdhartwick @jnemeth @andycochran @ncoden

Question for everyone. Is there still value in the responsive gutter stuff? I've never used it myself so interested if its worth keeping. It adds a lot of bloat and (in my opinion) not needed complexity.
I'm busy working on putting something together at the moment for this!

I think responsive gutters are definitely useful.
Off the top of my head, the syntax could look like:
$zf-col-gutter: 60px;
$zf-row-gutter: 30px;

.default-grid {
  @include zf-grid(1/4);

  @media (min-width: 800px) {
      @include zf-grid(1/4, $col-gutter: 10px); // should usually only need to be applied to the container
  }

  .big-cell {
    @include zf-cell(1/2);
  }
}

.one-off-size {
  @include zf-cell(1/2, $col-gutter: 30px); // allow this mixin to get custom sizes
}

I don't think responsive gutters should be the default dist. But the generator should offer this kind of functionality in a dynamic way.
I've made a billion PoC of this kind of stuff, so implementation won't be a problem once we settle on an API. Maybe we should shift the discussion to designing the API first and not worry about complexity?

Thanks @corysimmons. I think part of the problem is the current grid is just so unnecessarily complicated, where I don't think it needs to be (its hurting my head reading through it all!).
Another issue I've come across with using margin based grids plus calc() is if we include a .collapse class like the current grid to remove margins from columns within a row.
That's maybe more to do with the spaghetti of mixins/functions at the moment though maybe, but I'm not sure how to structure everything to offer a great set of clear functions/mixins to do all we need...

I completely get that. The overwhelming amount of settings/spaghetti involved with these big CSS frameworks is the reason I, and a lot of other devs, avoid them.
How integrated is the grid stuff with components? If it is, it shouldn't be, and components should be scoped using vanilla flexbox.
The concept of a "grid" has always worked best as a structure/overall-layout thing imo.
If it's not coupled, then just delete all the grid stuff and focus on making a couple really flexible/powerful mixins (zf-grid and zf-cell).

zf-grid would be applied to a container.
zf-cell applied to any one-off sizes.

Write a loop for your base grid classes:
loop over breakpoints
  loop over number of columns

Then just write additional loops for things like .collapse:
// base grid
loop over breakpoints
  loop over number of columns

// .collapse
loop over breakpoints
  loop over number of columns using $gutter: 0

// additional stuff
loop over breakpoints
  loop over number of columns + whatever

This will modularize these loops a bit so they can be switched on/off (for things like the generator), or an internal generator like @include zf-generate-grid($breakpoints-map, $number-of-columns, $include-collapsed, etc.).

Keep in mind, margin-based grids cause the body to scroll horizontally unless its padding is greater than the negative margin-right of the row. If you want your grid flush with the edges of the page, you need a padding-based grid (or a left side only, single-sided, margin-based grid).

Or body { overflow-x: hidden }

@corysimmons Thanks that really helped clear things in my mind.
I wanted to pick your brains on single sided margin grids again if you don't mind, as I like the fact it doesn't cause overflow etc.
I forked a Masonry demo and edited it to use a single sided margin: http://codepen.io/brettsmason/pen/JNXwVq - as far as I can see it works OK, though I will admit I haven't had to use Masonry or an alternative in years.
By the way really interesting reading looking at your other projects (Lost especially)!
@andycochran What do you think of padding vs margin? I'd value your opinion too. I like the fact that with a margin grid, the grid classes could be applied directly to cards for example.

I wanted to pick your brains on single sided margin grids again if you don't mind, as I like the fact it doesn't cause overflow etc.

Again, I really think you should avoid single-sided grids. I know how sexy the markup is, but even if you aren't using masonry, users should have an option to plop one-off cells within a container.

By the way really interesting reading looking at your other projects (Lost especially)!

Lost is nice. It ended the need for the "context" stuff that Susy and Jeet have. It's maintained really well by Peter nowadays. That said, postcss-ant is probably the most interesting thing I've done in the layout space.
What's the team's thoughts about migrating from Sass to PostCSS? Bootstrap is considering it for v5.
It'd make Foundation available to users of any preprocessor, or vanilla CSS, and it's insanely powerful (all the power of JS vs. the subset of functions preprocessors handle).

Again, I really think you should avoid single-sided grids. I know how sexy the markup is, but even if you aren't using masonry, users should have an option to plop one-off cells within a container.

Stupid question, but what do you mean by the bit in bold? Just want to understand what you mean (example might help), but I totally take on board what your saying so we will go with split, especially as its what users are used to anyway.
In terms of moving to PostCSS - I think it might of been discussed very briefly but not in any detail. I'd be interested to know more about it, as I'll confess to having never used it. From what I understand its more modular in its approach though with additional plugins to handle things that Sass does natively for example.
The Zurb guys like to keep as cutting edge/up to date with advancements as is possible, so I'm sure they would be open to at least discussing what the benefits would be, and what would be involved (I definitely would).

Bootstrap is considering it for v5.

First they release there v4.0.0-beta! (2 yrs of development)

@andycochran What do you think of padding vs margin? I'd value your opinion too. I like the fact that with a margin grid, the grid classes could be applied directly to cards for example.

Well I see use cases for each method being "better." But it seems to me like most designs need both.
Margin for spacing multiple things inside containers:

And padding for defining containers that divide space:

Using margin for grid column layout doesn't preclude us from also using padding on those columns. The second example above could be done with margin:0.

@brettsmason

Stupid question, but what do you mean by the bit in bold? Just want to understand what you mean (example might help)
https://codepen.io/corysimmons/pen/GmoWGr

Basically, single-side grids (or "nth-grids" as I call them) need the CSS to define the number of elements in each row. With double-sided (or "negative-margin", "masonry" grids) you don't need to care about how many elements are in a row as long as they add up to 100% width.

From what I understand its more modular in its approach though with additional plugins to handle things that Sass does natively for example.

Regardless of whatever memes people are spewing about PostCSS, it's biggest benefits are:

Works with ANY preprocessor, OR just vanilla CSS.
All the power of JS whereas preprocessors only give you a handful of functions/logic.

The downsides of PostCSS:

Docs are auto-generated and confusing as hell.
CLI is lacking (i.e. needs a more flexible API).
SugarSS (PostCSS' attempt at replicating the niceties of preprocessors—nestings, vars, etc.—is buggy/lacking.

The best combination, imo, is PostCSS for libs, Sass (Stylus really, but Sass is more popular) for syntactic sugar.
If PostCSS libs are written with preprocessors in mind, you can layer them.
in.scss -> out.css -> PostCSS -> out.posted.css
This gives you the best of both worlds (power of PostCSS, bug-free sugar of Sass), but might be a lot to ask of users. You guys can be the call of that.

@andycochran

Using margin for grid column layout doesn't preclude us from also using padding on those columns. The second example above could be done with margin:0.

This is an important note which makes the argument for padding grids moot.
https://codepen.io/corysimmons/pen/aWZbNB?editors=1100

in.scss -> out.css -> PostCSS -> out.posted.css
Love it!

I think we should move PostCSS discussion to another issue, but I think it is definitely worth pursuing - have some ideas related to it as well, but lets move to an independent thread. @corysimmons do you want to start it?

So based on all the feedback and comments as well as a discussion with @kball, I've been working on a sort of proof of concept. You can view it here: http://codepen.io/brettsmason/pen/GmZaxv
Basically I think it would be good to be able to offer the choice between a margin or padding grid (with margin as default imo). The code is a bit on the messy side at the moment, but I'd really appreciate everyones thoughts!
If this goes down well I'll try and turn it into a full working example with a complete set of mixins, and any help would be great!

@kball https://github.com/zurb/foundation-sites/issues/9980
@brettsmason Pen is broke. I guess you're working on it right now. If you share a pen, care to fork off it immediately after to guarantee the shared one works, and for posterity's sake?

Sorry fixed now and yes was tinkering, will fork instead!

Thanks. :)
Also, can you start putting body { padding: 30px } so we can see where overhangs are happening?

Done!
At the moment most of the demos have a .grid-container which limits the width to 1200px - would you prefer I got rid of that?

This max-width is fine, but not necessary for testing purposes.
It looks like you're on the right track now. It seems like you're having fun with it. Do I smell another grid enthusiast?!
A couple things to solidify an approach (and some docs) on:

Setting background color to a flush container. (just a single cell within a container—it'll produce a lot of markup, but should be a good approach to document)
It seems like you've already addressed this, but I'd add an element or two to your demos to ensure widow elements don't go awry (as flex-grow: 1 will do). Basically, don't have your demos have a perfect number of columns per row.

Now, where :poop: gets tricky... Thoughts on vertical sizing? :)

It looks like you're on the right track now. It seems like you're having fun with it. Do I smell another grid enthusiast?!

Yep! - as @kball will tell you I tend to get pretty heavy into whatever I work on (off canvas was the last thing). I like working on things that I feel could be made a lot better.
Not sure what you mean with 1. - do you just mean add a
 within the cells and colour those instead?
Re vertical sizing - do you mean eg setting the grid to flex-direction: column and how that would work? Almost like the Foundation for Apps grid? So basically the widths become heights...

do you just mean add a  within the cells and colour those instead or have I misunderstood

Sure. Experiment with a couple ways to do this and see which one is the easiest to convey to potential users.

Re vertical sizing - do you mean eg setting the grid to flex-direction: column and how that would work? Almost like the Foundation for Apps grid? So basically the widths become heights...

Something like that. I'm not sure of the implementation, but just thinking about sizing vertically as well—like, if I wanted a 500px tall container, and wanted 3 elements in it that were 1/3 with a gutter between them.
It might be silly to implement since Grid Layout will crush whatever we come up with, but it's worth thinking about.

So I've been working on putting together the mixins this afternoon and it bought up a few questions.
What should a single .column class behave like? For the live flex grid they take up available space and dont stack like the float grid does. My gut feeling is this should be changed so its 100% width without sizing classes applied. We can then offer some .auto classes or something that add the automatic sizing behaviour.
How do you think the vertical grid should work? I interpreted it as something like this: https://codepen.io/brettsmason/pen/wdzmLO
Basically set a modifier class on the grid/row to make the columns go the other way around, so the sizing is applied to the height instead. Does that sound correct/useful/what you had in mind? I think this could basically incorporate the App grid, but I need to investigate that a little more.

Sorry @brettsmason
I'd like to keep nerding out on this but no one is paying me to. Going to go study some in-demand tech instead.
You seem to be on the right track with all this stuff so I'm not sure how much more help I could be at this point. Try bouncing these ideas off some html/css-centric co-workers to see how they feel about using your solutions.
I wouldn't worry too much about the vertical stuff if there isn't an elegant solution.
Best of luck. 👍

@brettsmason I agree with your assessment on 100% width and then having auto sizing be explicitly applied... the behavior in the current flex grid (and its difference from the float grid) is a constant source of confusion.
On the vertical front, that seems like a reasonable approach. Do gutters then apply vertically rather than horizontally as well?

@corysimmons no problem and thanks for all your help with this :thumbsup:
@kball cool thanks for confirming, I'll go with 100% then.
Not sure on gutters. My initial thought was yes to apply vertical gutters, but not sure - I never used Apps so not sure on layouts that would typically be created. I know it has other uses though other than app style layouts.
Is there any way to get some of the Apps templates uploaded as working examples somewhere for me to check?

Your example showed horizontal grid nested within vertical
Flexbox should be either used horizontal or vertical... but not in combination
For Two dimensional grid system => CSS Grids is the correct approach and flexbox shouldnt be used!

@brettsmason with regards to app grid, check out the work in this WIP PR: https://github.com/zurb/foundation-sites/pull/9487
@IamManchanda in 2018 CSS Grid is the correct approach... hopefully by late 2017 even... but the target with this grid is something that moves us forward and is actually usable for production projects today.

@IamManchanda not everyone has the luxury of being able to use css grid, including me :smile:

I am not saying to use CSS grids right now
Check my above comment.... infact I am requesting to delay f7 to early 2018
I am just saying that....just meant that lets not look for a combination and keep it simple
Aka One way traffic!! @kball

Same here @brettsmason... even I dont have :D

@kball i was actually referring to these: http://foundation.zurb.com/apps/page-templates.html it would be nice to see them working so I have a better understanding of how everything fits together (the docs in the PR don't really give me an idea of the layouts it's for).
There's bound be a lot of overlap between the grids, just wondered how much and if they needed to be separate or not.

@brettsmason I think the grid is looking good! One thing that people have asked for and Flexbox can do well is a Block Grid - but with various width columns like: http://bulma.io/documentation/grid/columns/#multiline
I can add this in - where would be the best place to collaborate with you on the flex grid code?

@rafibomb I'm in the process of putting together mixins so I can put everything together correctly.
Once that's done I'll stick a branch online for you to take a look at.
I'm not sure I fully understand the difference with the multiline thing - isn't it just a row with flex-wrap: wrap on it?

@brettsmason Basically! I think a lot of it will be documenting the cool use cases which is where I can help as well.

@brettsmason => http://codepen.io/IamManchanda/pen/NjwKJO?editors=1100
@corysimmons => Can't this be a possibility .row>.columns>.columns>.columns>* and so on ??
PS: I am looking at this as a user of the grid!

space-around/between will never work with margins. I fought with this for a month with every hack in the book.

.row could be thought of as .apply-a-negative-margin, and .column as .put-a-margin-on-each-side.
I really think Brett's simple flexbox mixin (I'd stick with horizontal-only to avoid confusion/pain) is the correct solution until grid spec is widely used.
Just make sure you expose a mixin to get gutter-aware sizes for fringe cases.

@corysimmons I added space-around for styling purpose ....
Here it is with flex-start => http://codepen.io/IamManchanda/pen/ybPORw?editors=1100
I am not a coding geek like you
but can't gutters be calculated (maybe calc) to make it work ??
PS: Again i am looking on it as a user!

.row {
  // ...
  width: initial;
  margin: 0 -15px;
}

.column {
  // ...
  width: calc(100% * 1/3 - 30px);
  margin: 0 15px;
}

Notice the inner columns aren't aligned flush with the original grid.
This is why you need to do: .row > .column every time you nest.
This extra markup is the price you must pay in exchange for not having to count columns per row.

Oh these gutters... Damn!
Ohk just for my personal knowledge
When I don't need gutters... Is this a good way to go about?

Sure, but I think you'd better serve yourself, and your team, by agreeing to use 1 technique rather than mixing-and-matching—especially when the payoff is as minimal as a few less
s.
Terse markup seems thrown out the window with React, and React is curbstomping everything, so maybe terse markup doesn't matter after all.
Honestly, Brett has this already.

This is exactly why i cant wait for css grids to take over because it has gutters grid-gap inbuilt in them
https://codepen.io/enxaneta/pen/YZjJaW?editors=1100

This is exactly why i cant wait for css grids to take over because it has gutters grid-gap inbuilt in them

Yeah, it took them a while to figure out this was a huge problem, but in the next few years markup will become really logical and terse.
Until it hits 90% global I won't use it.
Alright, I'm outta here again. Good luck team. Ping me if you have a direct question.

@corysimmons Sorry to bother you, I'm trying to get my head around a question with margin grids.
I've mainly used padding grids in the past, so struggling with the way to handle this.
A typical use case would be a solid coloured, full width background container, within this is our grid container, centred and contained to a max width. Then within that would be our columns etc.
Currently with a padding grid we would write:

Logo

Nav

However the above doesn't work with a margin based grid. We can't use margin: auto as we have a negative margin on the .row with a margin based grid.
What would be the best way of tackling this scenario in your opinion? Do we simply need to add an extra wrapper around the .row for this to work? Something like .row-container.
Also on smaller screens we have left/right padding currently that stops content from hitting the edges. Would adding padding to this .row-container work? Trouble with that is it wouldn't then line up to the rest of the grid elements.
Would appreciate your input as I'm keep to keep the new grid a margin grid!

I don't see a way to use max-width with margin-auto on margin-based grids without an extra container. Yuck. But if you only need one background color for the whole row, there's no reason to use a margin-based grid.
Again, I'd advise against letting the "gutter" interchangeably be margin OR padding. Define them both explicitly. Then, for this use case, you create a grid with x padding, 0 margin, and a max-width.
The caveat is, if you want a row like this…

…to have a max-width, you have to use an extra container. Which isn't so bad. Because with a padding-based grid, you'd have to use 4 extra containers (1 inside each of the columns).

@andycochran After discussion with @kball I was planning on making the gutter margin only.
However I'm experimenting with real world situations/layouts and see how it would work.
So what you are suggesting is a way for a grid to have no gutter, margin and/or padding?
The complication is no gutters and padding don't need calc(), but margin does. Struggling to understand fully how that could work.
Would definitely like to discuss to get it nailed down though as the idea is interesting. I just don't want to end up with the mess of specificity like the current grid 😄

@andycochran Actually, I think: http://brettmason.co.uk/grid/ nearly does what you described. All I need to do is remove the .padding-gutters > [size]-[number] specificity and keep it on the margin option, as those widths are overwriting the margin based widths.
I'll put a demo together tonight and see what you think.

Can I get a CodePen for the background problem?

@corysimmons Sorry for the delay. Here's a quick CodePen: https://codepen.io/brettsmason/pen/ybRONQ
Basically with the margin grid we need an extra div in order to contain the width of elements within. I guess that's going to be the one main downside of margin grid compared to padding, but it also has a lot of positives.

If its just about adding a container ... Man i dont see it as a big issue !

Yeah I think a wrapping element to an entire set of blocks is cheaper than what you'd have to do with current solutions.
https://codepen.io/corysimmons/pen/MmPyvd?editors=1100
Pretty much every padding grid does this thing where they assume no one wants actual margins between elements, and it's all faux. So when situations like this pop up, you can't just say "Just wrap the whole thing in a .bg element", but rather the user has to figure out a lot of markup bloat to make it work.
This is just one of the inherit problems with the negative-margin technique, and CSS layout in general. Hence I went with nth grids for like... ever.

@brettsmason @corysimmons not quite css guru like you guys
But what's the problem with margin: 0 -1rem; instead of margin: 0 auto;
https://codepen.io/IamManchanda/pen/bWmpax?editors=1100

@IamManchanda the auto centres the element in the viewport. In your example everything is left aligned.

@brettsmason Not sure why he asked that, but just to be clear, .container should be its own class, right?

@corysimmons Yes definately its own class. At the moment with the live grid its built into the .row class, which is a mistake.

It's better to correct mistakes
Instead of creating more mistakes due to an old created mistakes


Use selectors instead of AllowedList for IngressClasses, StorageClasses, PriorityClasses

We are using a specific struct, AllowedListSpec:
type AllowedListSpec struct {
	Exact []string `json:"allowed,omitempty"`
	Regex string   `json:"allowedRegex,omitempty"`
}

to allow tenant users to use only specific IngressClasses, StorageClasses or PriorityClasses.
While it allows additional fine-grained configuration, that is not a kubernetes way of specifying resources.
Much better will be to use label selectors (the same way, as it is in nodeSelector option for tenant).
With this, tenant spec will look like:
apiVersion: capsule.clastix.io/v1beta1
kind: Tenant
metadata:
  name: oil
spec:
  owners:
  - name: alice
    kind: User
  storageClasses:
    selector:
       foo: bar

This change will simplify webhook code, make it works much faster (no regexp check), and will simplify the code of a capsule-proxy (as we won't need to get all resources first and then perform regexp validation or array probing).
The downside of this change is that it is completely backward incompatible and there will be no way to automatically upgrade tenant spec to this new version.
@bsctl, @prometherion need your opinion on this.

@MaxFedotov sounds good to me since more Kubernetes like. What about labelSelector ?
For backward compatibility same concerns. Let’s see @prometherion point of view

@bsctl

What about labelSelector ?

Can you please explain in more details?

Can you please explain in more details?

just this:
apiVersion: capsule.clastix.io/v1beta1
kind: Tenant
metadata:
  name: oil
spec:
  owners:
  - name: alice
    kind: User
  storageClasses:
    labelSelector:
       foo: bar

@MaxFedotov sounds good to me since more Kubernetes like. What about labelSelector ?

Couldn't agree more on this.

For backward compatibility same concerns. Let’s see @prometherion point of view

This change is absolutely breaking and not portable using a conversion. The unique way to use it would be adding labelSelector a third option in the AllowedList spec.
https://github.com/clastix/capsule/blob/d3e3b8a881b4ce25332e8d1a6904ff178b11242d/api/v1beta1/allowed_list.go#L12-L15
However, this would make things even more complicated on capsule-proxy side since we would need to add additional checks in the selection.
I got a plan:

introducing this feature for v1beta1 as annotation
plan landing on v1beta2
switch entirely towards selection for v1 API version that will be Capsule v1.0.0

Do you think this could be feasible?

@prometherion as we're approaching new API version for Tenant resource, what about to introduce this enhancement? To avoid breaking changes, we can just add another method of specifying Classes to make the transition smooth:
apiVersion: capsule.clastix.io/v1beta1
kind: Tenant
metadata:
  name: oil
spec:
  owners:
  - name: alice
    kind: User
  storageClasses:
    labelSelector:                           # <<< new way in v1beta2
       foo: bar
    allowed:                                    # <<< old way deprecated but still supported in v1beta2, removed in v1
    - default
    allowedRegex: "^tier-.*$"

@bsctl you're right, @MaxFedotov agreed on working on this.


[clkmgr] D2(S) Signoff

Description
Ensure D2(S) signoff criteria are still maintained (this is not a focus area block).

@msfschaffner here are all changes with a brief description
0d14dd693f [docs] Fix repetitions of the definite article: no impact
f95c9805b6 [lint,clkmgr] Clean lint for verible: no impact - formatting only
7c97490c24 [clkmgr] Insert hookup buffers on all root clock inputs: design impact - insert OCC hook points
ab4b36f6b9 [ipgen,rstmgr] Fix paths to rstmgr in md files: no impact - doc only
c721c51c13 [rtl, prim] Add 'commit' functionality to prim_count: design impact - minimal, since commit_i is set to 1, and cnt_next_o was unused
61a237e197 [util/reggen] reverse order of substruct generation: no impact - it only changes the unused clkmgr_reg_plkg.sv in ip/clkmgr
ce648ca68e [ipgen.pwrmgr] Change core files to vlnv naming and label as virtual: no impact - core file only, change dependency to ip_interfaces:pwrmgr_pkg
de31bdf1c2 [reggen] Remove the devmode input: minimal impact - devmode_i was unused
af22161547 [sival,chip_testplans] Handle alert_handler enables tests: dv impact minimal - add missing hjson feature label
3f88a55120 [pwrmgr,ipgen] Generate pwrmgr ip_autogen files with topgen: no impact - doc only
20c6550756 [dv/clkmgr] Fix clkmgr_env.core dependencies: no impact - fixes missing dependency in core file
897b51edc4 [sival,clkgr] Add features in clkmgr.hjson.tpl: dv impact minimal - adds hjson features labels
1b16ca2122 [reggen] Add mubi support SWAccess that sets/clears a reg: no impact - prim_subregs add explicit .Mubi (1'b0) for non-mubi subregs
088eee0df0 [clkmgr,dv] Avoid passing a mubi4_t as a uvm_reg_data_t output arg: no impact - fixes xcelium typing warnings
59f8142826 [doc] Moved badges over to using hosted images: no impact - doc only
182f51b528 [dv/clkmgr] Ignore coverage crosses that are unrealistic: dv no impact - only removes obvious coverage holes
a005c96cc3 [doc] clkmgr registers and interfaces now use CMDGEN: no impact - doc only
7d0117c19f [dv/clkmgr] Add test for regwen functionality: dv impact minimal - adds a new test
e8c303fafb [dv/clkmgr] Fix occasional clkmgr_peri test failure: dv impact minimal - fixes occasional test failure
0d8b4d4851 [dv/clkmgr] Improve handling of clock measure control CSRs: dv impact minimal - test code refactoring
8ff4837913 [dv/clkmgr] Increase wait cycles in clkmgr_lost_calib_ctrl_en_sva_if: dv impact minimal - fixes test failures
bdf5e83386 [clkmgr,dv] Fix type in clkmgr_extclk_vseq: no impact - lint cleaning
7688e714e8 [reggen] Add initial support for version and cip_id hjson fields: no impact - collateral data only
fbd888eea8 Revert "[reggen] Add CIP_IDs and bump all major versions": no impact - reverts the change below
0ba10b3cd3 [reggen] Add CIP_IDs and bump all major versions: no impact - this was reverted
e47df29f3e [misc] Use lc_tx_t testing functions at endpoints: no impact - code change with no functional impact
The only design change that has non-trivial impact is
7c97490c24 [clkmgr] Insert hookup buffers on all root clock inputs: design impact - insert OCC hook points
and then I think this is transparent for our code.

Thanks a lot for the analysis @matutem, this is really helpful.
The OCC hook points should be transparent from a functional perspective, since it just inserts buffers.
No adverse impact from a DV point has been observed, afaik, and Nuvoton/Rivos are already using these in their flows.
I think this looks good and we can sign this block off.
Looks like no further PR is needed since the hjson still shows D2S:
https://github.com/lowRISC/opentitan/blob/6f251215344949e9dcc596c67860defcba856d34/hw/top_earlgrey/ip_autogen/clkmgr/data/clkmgr.hjson#L24-L32


Jrock/llm tech report [section 3.3]

Problem description
We need a tech report
What's changed
Added section multi devices to llm tech report.

Can you close this PR and send it again? I will approve it, you cannot push this one because of Miguel's request.


Build images on PRs from community users

WHY
Contributors should be able tests their images on their clusters
User Story
AS A OSS contributor
I WANT TO the Build and publish Docker pipeline to be trigger on PR from my fork
SO I can see results of smoke  tests and test my changes in runtime
Acceptance criteria
GIVEN OSS contributor
WHEN PR to the main branch is opened
THEN Build and publish Docker pushes it to Github cache registry (not  to dockerhub)
Definition of done

[ ] Relevant PRs are merged
[ ] Tested by peer
[ ] Updated documentation reviewed by peer
[ ] Short demo video recorded and stored on google drive (if applicable)

Hey team! Please add your planning poker estimate with Zenhub @Ani1357 @dennisvankekem @ElderMatt @ferruhcihan @srodenhuis @staticvoid255


hyprland 0.36.0 fails to compile musl

Hyprland Version
0.36.0
Bug or Regression?
Bug
Description
hyprland fails to compile
How to reproduce
compile hyprland against musl
Crash reports, logs, images, videos
build.log.txt

Theres a pull request open https://github.com/hyprwm/Hyprland/pull/4805

please test, should be fixed now


Add support to select kit components while rejecting kit item

Current behavior
Currently user can only reject kit without caring about it's component and the same inventory adjustments are done for the kit component as well.
Expected behavior
If cases the kit components are also sold individually, do not  adjust their inventory based on the kit rejection and instead apply inventory adjustments only to the selected kit components. Add support in UI for the same. Default behaviour would to reject all the components.
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[ ] NO

Environment details

Browser:
OS:
Code Version:

Additional information

Changes can only be verified on dev-oms and on dev-oms there is no kit product available. Therefore, marking this ticket on-hold.

Any room for movement here? When will se QA this?


why dashboard doesn't get any response

Hi,
I don't see any response data in dashboard. Also, I don't see any request data in my server.
I try many time, but still same error
pls help

This sample does not directly interact with your server. It uses the Home Graph APIs to read the data that you've sent with report state.

I encountered the same situation.
this response code 500
http://myproject****.appspot.com/refresh?agentUserId=1749a8******************1845
{
error: "Internal Server Error"
exception: "java.lang.NullPointerException"
message: "No message available"
path: "/refresh"
status: 500
timestamp:<PHONE_NUMBER>510
}
and other more  reponse code 403 Forbidden
GET http://api.giphy.com/v1/gifs/search?api_key=api-key&limit=1&rating=g&q=mydevice
this dashboard created in last year and successfully used, but can not be used now

If you're getting a NPE in the backend, you should take a look at server logs to see what's going on, as that's unexpected.
The Giphy issue seems to be stemming from the fact that you're using api-key, which is a dummy value. But there should probably be a better way to present icons than using Giphy anyway.

If you're getting a NPE in the backend, you should take a look at server logs to see what's going on, as that's unexpected.
The Giphy issue seems to be stemming from the fact that you're using api-key, which is a dummy value. But there should probably be a better way to present icons than using Giphy anyway.

I'm getting the same thing as @LIULi-VVET. I don't know how to decipher the error message I'm seeing in the AppEngine logs, apart from the fact that its getting a 500 error.
`[f~smart-home-action-reportstate/20190709t180141.419473170289254651].: 2019-07-09 08:12:16.018 ERROR 1 --- [Request31AFF798] o.s.boot.web.support.ErrorPageFilter     : Forwarding to error page from request [/refresh] due to exception [null]
java.lang.NullPointerException: null
at com.google.api.client.repackaged.com.google.common.base.Preconditions.checkNotNull(Preconditions.java:191) ~[google-http-client-1.19.0.jar:1.19.0]
at com.google.api.client.util.Preconditions.checkNotNull(Preconditions.java:127) ~[google-http-client-1.19.0.jar:1.19.0]
at com.google.auth.oauth2.GoogleCredentials.fromStream(GoogleCredentials.java:158) ~[google-auth-library-oauth2-http-0.9.0.jar:na]
at com.google.auth.oauth2.GoogleCredentials.fromStream(GoogleCredentials.java:141) ~[google-auth-library-oauth2-http-0.9.0.jar:na]
at com.google.homegraph.dashboard.controller.HomeGraphController.createConnection(HomeGraphController.java:97) ~[classes/:na]
at com.google.homegraph.dashboard.controller.HomeGraphController.refresh(HomeGraphController.java:132) ~[classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_171-google-v7]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_171-google-v7]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_171-google-v7]
at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_171-google-v7]
at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133) ~[spring-web-4.3.14.RELEASE.jar:4.3.14.RELEASE]
at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97) ~[spring-webmvc-4.3.14.RELEASE.jar:4.3.14.RELEASE]`

I have solved this problem.
The reason is that I used a mismatched Project dashboard to query status.
Another reason for the mistake is that I uploaded the incorrect Json file.

I have solved this problem.
The reason is that I used a mismatched Project dashboard to query status.
Another reason for the mistake is that I uploaded the incorrect Json file.

Thanks for the response. What do you mean mismatched project? I've only uploaded one instance of the smart home dashboard on appengine and it used to work so I don't think I got it wrong. I'll perhaps try download the json file again and see. I wonder what I'm doing wrong.

I have many different projects.
I think of the dashboard of another project as this


target-templates-update Script does not copy resource tags or KMS keys

target-templates-update Script does not copy resource tags or KMS keys

Spoke internally with<EMAIL_ADDRESS>Please reach out if you have any questions!


Adding v0.8.1 Changelog

What type of PR is this?
/kind documentation
What this PR does / why we need it:
This adds the changelog for v0.8.1. By approving this changelog you approve the release of v0.8.1.
Does this PR introduce a user-facing change?:
NONE

/hold for consensus

/lgtm

/hold cancel


gaea content

transfer all or most of all Gaea content

Completely agree about the need for refinement and greatly appreciate you
moving this forward.
On Tue, Apr 16, 2024 at 11:11 AM Seth Underwood @.***>
wrote:

@.**** approved this pull request.
There are more changes to the gaea page needed. I'll accept these as-is
now, but knowing that there will be major changes coming soon.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-RDHPCS/noaa-rdhpcs.github.io/pull/62#pullrequestreview-2003935831,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4T5JW6D7KZGVC3RMXODGOTY5U5QZAVCNFSM6AAAAABFZZEYTSVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMBTHEZTKOBTGE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Add AAF plot output to PlotACNVResults.

As requested by @dlivitz et al.

Issue moved to broadinstitute/gatk #2957 via ZenHub


Rules - allow using only known fields

The API should return failed when I try to use unknown field in a rule.
Eg.
{
"rules": [
["name", "==", "John"]
]
}
The 'name' is not a field, it should be use as property: $.name.

fixed in v3.5.2


[SPARK-7320] [SQL] Add Cube / Rollup for dataframe

This is a follow up for #6257, which broke the maven test.
Add cube & rollup for DataFrame
For example:
testData.rollup($"a" + $"b", $"b").agg(sum($"a" - $"b"))
testData.cube($"a" + $"b", $"b").agg(sum($"a" - $"b"))

Merged build triggered.

Merged build started.

Test build #33191 has started for   PR 6304 at commit 04bb1de.

/cc @yhuai @liancheng
Thanks for the suggestion to move the table registration into beforeAll in test suite.
Let's see what jenkins will say.

I manually tested HiveDataFrameAnalyticsSuite. It is good.

Test build #33191 has finished for   PR 6304 at commit 04bb1de.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class GroupedData protected[sql](
public class TaskMemoryManager

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33191/
Test PASSed.

Thanks for fixing the test! I am merging it to master and branch 1.4.

Ok, yes, I will update that.


FadeOut is not Working with Transformed text

I was trying to remove the transformed text from the scene, I tried Fading Out the transformed text and then adding a new one.
i.e.
text1 --> text2
text2 --> fadeout
text3 (ShowCreation)
But apparently, FadeOut is not working for transformed text (text2).
I have added the sample code below:
from big_ol_pile_of_manim_imports import *

class TestFadeOut(Scene):
	def construct(self):
		sentence1 = TextMobject(r"$Some Random Equation: e^{i\pi}=-1$")
		sentence2 = TextMobject("This is a tranformed text")
		sentence3 = TextMobject("Third Text")
		self.play(Transform(sentence1, sentence2))
		self.wait(2)
		self.play(FadeOut(sentence2))
		self.wait(2)
		self.play(ShowCreation(sentence3))

I am not particular about FadeOut I just want to remove the transformed text so that I can place another text in the same position. I even tried shifting it out of the scene but it seems as if most of the TextMobject functions are not working on the transformed text.
from big_ol_pile_of_manim_imports import *
class TestFadeOut(Scene):
	def construct(self):
		sentence1 = TextMobject(r"$Some Random Equation: e^{i\pi}=-1$")
		sentence2 = TextMobject("This is a tranformed text")
		sentence3 = TextMobject("Third Text")
		self.play(Transform(sentence1, sentence2))
		self.wait(2)
		sentence2.move_to(sentence2, 50*LEFT)
		self.wait(2)
		self.play(ShowCreation(sentence3))

Call FadeOut on sentence1 rather than sentence2.

But why dosen't it work with sentence2? And is there a better way to do remove the transformed text?

This should works:
from big_ol_pile_of_manim_imports import *

class TestFadeOut2(Scene):
	def construct(self):
		sentence1 = TextMobject(r"$Some Random Equation: e^{i\pi}=-1$")
		sentence2 = TextMobject("This is a tranformed text")
		sentence3 = TextMobject("Third Text")
		self.play(ReplacementTransform(sentence1, sentence2)) # <- Use ReplacementTransform
		self.wait(2)
		self.play(FadeOut(sentence2))
		self.wait(2)
		self.play(ShowCreation(sentence3))

The difference between Transform (s1, s2) and ReplacementTransform (s1, s2) is that, Transform keeps the value intact of s2, while ReplacementTransform makes s1 = s2. I leave you a couple of animations to make it clearer.
class WhatIsTransform(Scene):
	def construct(self):
		sentence1 = TextMobject("A")
		sentence2 = TextMobject("B")
		sentence3 = TextMobject("C")
		sentence4 = TextMobject("D")
		self.add(sentence1)
		self.wait()

		self.play(Transform(sentence1,sentence2))
		self.wait()

		self.play(Transform(sentence1,sentence3))
		self.wait()

		self.play(Transform(sentence1,sentence4))
		self.wait()

		self.play(FadeOut(sentence1))

class WhatIsReplacementTransform(Scene):
	def construct(self):
		sentence1 = TextMobject("A")
		sentence2 = TextMobject("B")
		sentence3 = TextMobject("C")
		sentence4 = TextMobject("D")
		self.add(sentence1)
		self.wait()

		self.play(Transform(sentence1,sentence2))
		self.wait()

		self.play(Transform(sentence2,sentence3))
		self.wait()

		self.play(Transform(sentence3,sentence4))
		self.wait()

		self.play(FadeOut(sentence4))

This should be included in the doc


revC2: incorrect part number for U2

BOM and schematics of revC2 have the following part number for U2: CAT24M01XI-T2
That part number corresponds to SOIC-8 package, however the footprint used on board is TSSOP-8.
The correct part number should be either:
CAT24M01YI−GT3 (-40..+85 deg C) or CAT24M01YE−GT3 (-40..+125 deg C)

It should be CAT24M01YI−GT3.


Local video shows black screen on android

Current behavior
When I am rendering a Video from my local system it shows a black screen only when my device is unplugged, I have also tried bundling my JS code but it still shows black screen, but when I am connected to my laptop eveything runs fine, its pretty weird problem
Reproduction steps
My simple code snippet
        <View style={styles.container}>
            <Video source={require('./welcomescr.mp4')}   // Can be a URL or a local file.
                ref={(ref) => {
                    this.player = ref
                }}
                hideShutterView = {true}
                style={styles.backgroundVideo} />
        </View>

Expected behavior
Video should play when I am unplugged
Platform
Which player are you experiencing the problem on:

Android ExoPlayer

👍  same here , Did you find any solution?
and when I use rate props it crashes on android.
`renderVideo() {
return(
<Video
source={('./Measurements.mp4')}
ref={(ref) => {
this.player = ref
}}
controls = {false}
fullscreen = {false}
onLoadStart={() => {console.log("loading started")}}
onLoad={() => {console.log("loading done")}}
			style = {[styles.video]}
		/>
 )

}`

I have the same problem

Any updates on this? Im having the same issue. Online video content is fine but local videos produce a black screen.

Having the same problems on IOS and simulator

I've come here to express the same as OP.
I've tested my app on the following 3 devices after building out the app and loading them onto the phones (ie. not executing react-native run-ios or react-native run-android). iPhone X, Samsung Galaxy S8+, Motorola moto e5 play. The phone I'm getting a black screen is the Motorola.
What's weird is that the app utilizes RNV in two separate sections of my app. The first section has no issue, even for the Motorola. It's the second section that's the problem.

Same issue android 8.1

In my case I fixed it by using the old Android Media Player, replacing:
include ':react-native-video'
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android-exoplayer')

with
include ':react-native-video'
project(':react-native-video').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-video/android')

I used to run into stucked black screen all the time. The most strange one I experience is https://github.com/react-native-community/react-native-video/issues/1538
My feeling is this project manage the native video player instances very poorly (especially on Android). The project frequently mess things up when you have multiple native video player instances. In our project, we had to do a lot of difficult and hard things to ensure that we only have one instance of a screen that have the  tag, thus only one native video player instance, then it won't stuck.

Please test with 4.4.4.
If still not works I will reopen the issue

Still getting  black screen  issue in 4.4.5 as well, any update on this?

any update? sam issue

Had the same issue.
Everything worked fine but suddenly all videos became black on Xiaomi Poco M3. No any "onError" and "onLoad" calls, no errors in logcat.
I've tried "gradlew clean", restarted everything, even made a fresh simple app only with single video screen. Nothing helped. But when I tried to install the same app on my old Nexus 5 - everything worked perfectly.
I guess that there is Xiaomi MIUI optimization problem. After uninstalling app, switching off all MIUI optimization and unnecessary settings in developer menu, clearing build cache everything works fine.


Avoid read docs twice when filtered _changes is triggered

Overview

When filered _changes is triggered, open_revs() will increment stats.
If request parameter has include_docs=true, then doc_member() will
also increase stats.
Since filter/3 is used in couch_changse.erl, this function is not modified.
Add filter/4 to avoid the above behavior.
Testing recommendations
make eunit apps=chttpd suites=chttpd_changes_test
make eunit apps=couch suites=couch_changes_tests

Related Issues or Pull Requests

Checklist

[ ] Code is written and works correctly
[x] Changes are covered by tests
[ ] Any new configurable parameters are documented in rel/overlay/etc/default.ini
[ ] Documentation changes were made in the src/docs folder
[ ] Documentation changes were backported (separated PR) to affected branches

When filered _changes is triggered, open_rev() will increment stats. If query has include_docs=true, then doc_member() will also increase stats.
In that code path it sounds like the document is being read twice, so incrementing database_reads twice sounds correct. Of course if we could avoid the second read that would be great.
Did I misunderstand the problem?

In that code path it sounds like the document is being read twice, so incrementing database_reads twice sounds correct. Of course if we could avoid the second read that would be great.

I'll try to avoid the second read, thanks for the review.

To reduce the size of the PR, wonder if it would make sense to extract the enhanced tests into a separate PR. We don't intend to change the behavior of _changes endpoint to tests could be updated first then optimize the doc loading separately.

To reduce the size of the PR, wonder if it would make sense to extract the enhanced tests into a separate PR. We don't intend to change the behavior of _changes endpoint to tests could be updated first then optimize the doc loading separately.

Sure, dropped the first commit.


Ketaros Classes Improved shows Squaddie ranks on Corporal

i"m testing Ketaros Classes Improved, the ranks here are extended to brigadier, the problem is that initial perks given at squaddie rank are repeated on corporal

(c) Baldemon
This issue doesn't appear in NPSBD.

Could not replicate this bug in isolated testing, assumed conflict with something else, closing.


Supports rack v2.2.2.

rack v2.2.2対応をお願い致します。
gem 'rack', '2.2.2'
なアプリにて動作確認致しました。

Coverage remained the same at 90.323% when pulling eefb6aa110aeebb12c9b6b0ed5ed199e1ee46cb5 on maedadev:master into 4cbe77023e2a9602ab35d6f27416ab0de93aa9ef on dtaniwaki:master.

Coverage remained the same at 90.323% when pulling eefb6aa110aeebb12c9b6b0ed5ed199e1ee46cb5 on maedadev:master into 4cbe77023e2a9602ab35d6f27416ab0de93aa9ef on dtaniwaki:master.

Thank you for the review.
Corrected the issues pointed out.
Please review again.

Can you resolve the conflicts?

Resolved the conflict.

Thank you!

When will the latest version be released?

@dtaniwaki Could you please release a new version that includes this fix?
Recently, rack released security patch, but that security patch only supported rack above v2.1. So without this fix, can't use that release.
Ref: https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2020-8184.yml

I made a new release.
https://github.com/dtaniwaki/rack-dev-mark/releases/tag/v0.7.9

Thank you so much!


NPT disconnect/closes durin Filezilla SFTP session.

Describe the bug
The npt session on macOS Sequoia 15.0.1 with an M1 processor, disconnects during a SFTP session when using Filezilla. I not have done any testing on my old MacBook Pro with the Intel processor.
Steps to reproduce
I used Filezilla and sftp - ssh file transfer protocol over port 65229 when I see the failure.  Port 65229 is the local port and the remote port is 22.  Also, a normal ssh session to localhost port 65229  and a command line scp works fine. Also, cyberduck worked fine.
If I run the following npt commands with the verbose flag I can not reproduce the failure.
Command line entris used to reproduct the failure plus the quiet flag.
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device cos9 --remote-port 22 --local-port 65229 --timeout 1h --quiet & ; /Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device t420s --remote-port 3389 --local-port 33894 --timeout 1h --quiet &
Command line entrie used to reproduct the failure plus the quiet flag removed.
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device cos9 --remote-port 22 --local-port 65229 --timeout 1h & ; /Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device t420s --remote-port 3389 --local-port 33894 --timeout 1h &
----npt test using a different rvs "rv_am and rv_eu" plus quiet flag removed----
Command line for the npt connection on localport 65229 for host cos9 and rv "rv_am".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device cos9 --remote-port 22 --local-port 65229 --timeout 1h
Command line for the npt connection on localport 33894 for host t420s and rv "rv_eu".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_eu --device t420s --remote-port 3389 --local-port 33894 --timeout 1h
----npt test using a different rvs "rv_am and rv_eu"----
Command line for the npt connection on localport 65229 for host cos9 and rv "rv_eu".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_eu --device cos9 --remote-port 22 --local-port 65229 --timeout 1h
Command line for the npt connection on localport 33894 for host t420s and rv "rv_am".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device t420s --remote-port 3389 --local-port 33894 --timeout 1h
Note there were no errors reported in the terminal windows. the session just disconnected.
----npt test using the rv "rv_am" and adding the verbose flag----
Command line for the npt connection on localport 65229 for host cos9 and rv "rv_eu".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device cos9 --remote-port 22 --local-port 65229 --timeout 1h --verbose
Command line for the npt connection on localport 33894 for host t420s and rv "rv_am".
/Users/kdimick/.local/bin/npt --from @intense56 --to @55commercial --srvd @rv_am --device t420s --remote-port 3389 --local-port 33894 --timeout 1h --verbose
I was able to get a sshnpd log file that displayed an error. none of the other log files displayed any error message like the log file srv.18183.log.
Expected behavior
Not to disconnect during the SFTP sessions.
Screenshots

Smartphones

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Were you using an atApplication when the bug was found?
I waas using NPT.
Additional context
The log file srv.18183.log that displaued some error information.
srv.18183.log

May be resolved by #1509 ... once that PR has been merged we will publish another noports release candidate against which this ticket can be retested

@kimdimick Can you retest this using latest alpha release https://github.com/atsign-foundation/noports/releases/tag/v5.7.0-alpha-8 please?

PS use @stream as relay, and you will need to use the newer versions of both your sshnpd and your npt binaries

I have run a few tests using FileZilla to transfer 26.34 GB of data or approximately 1527 files of various sizes without a disconnect.
The Filezilla issue looks to be fixed in the 5.7.0-alpha-8 release.

Great! Thank you @kimdimick


Wire up privy login to backend

Wire up privy login to backend
a

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#385  👈
#376
#371
#369
#367
#366
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jvmi7 and the rest of your teammates on  Graphite


Allow nil receiver on Properties

Summary
Since all the providers that do not explicitly implement properties
interface return nil, nil, it might be a good idea to implement a nil
receiver for Properties.
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
make test
Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[x] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 53.892% (-0.007%) from 53.899%
when pulling 0c995bf24ba63c6a47c9983caf02e5076766100f on jhrozek:properties_nil_receive
into 02a42be4f78605ac1a5f6b61dd843c70296efaa0 on stacklok:main.


feat: add image picker component

Description
This PR add image picker component. There are 2 ways of using the component.
The first one is wrapping uninteractive element as a child, whenever the element is pressed, it will trigger image picker.
<ImagePicker
  launchType="camera"
  preview={imagePickerResponse =>
    imagePickerResponse && (
      <Preview imagePickerResponse={imagePickerResponse} />
    )
  }
  options={{
    mediaType: 'photo',
  }}>
  <Text style={style.text}>Pick as Text</Text>
</ImagePicker>

The next one is wrapping interactive as a child function, it receives a parameter openPicker that can be called to trigger image picker:
<ImagePicker
  launchType="camera"
  preview={imagePickerResponse =>
    imagePickerResponse && (
      <Preview imagePickerResponse={imagePickerResponse} />
    )
  }
  options={{
    mediaType: 'photo',
  }}>
  {({openPicker}) => (
    <View style={style.button}>
      <Button onPress={openPicker} title="Pick as Button" />
    </View>
  )}
</ImagePicker>

Loom
https://user-images.githubusercontent.com/20434351/150628966-987d203d-d4f8-4d3e-b237-4ddc557c4166.mp4
Issue
Close: https://github.com/Jitera/jitera-frontend/issues/505

@jefrydco it should use default render input if user don't want to customize.
image picker should have props: (for form implement)

onChange trigger when selected a image
value show when user already choose a image
Error message to show error validation in this field

@sieuhuflit @zrg-team I've fixed the image picker, please kindly help recheck. I also fixed several bugs:

[x] onPress callback on Button isn't triggered
[x] Can't render icon component

https://user-images.githubusercontent.com/20434351/151185088-f04d4ab0-c03c-48fb-a42c-caefec931352.mp4

@jefrydco please remove react-native-image-picker if we don't use it


How to make it work with Puppeteer ?

Hi.
Thanks for this awesome project.
I have trouble making it work with Puppeteer.
I'm trying to access a https website. I'm able to detect when i'm blacklisted.
But i can't get the proxyname to kill it. Because the website that i'm reaching is in https right ?
How can i work around that ? How can i know the proxyname anyway ?
Thanks !

mitm params (https://scrapoxy.readthedocs.io/en/master/standard/config/index.html#options-proxy) are missing for the docker version #134

added in 4.0.0

Hey there! 🌟 Exciting news! Scrapoxy 4 is ready to rock 🚀. Check it out at Scrapoxy.io (explore the "get started" guide, deployment documentation, and more 📚).
I can't wait to hear your feedback on this new version! Send me your coolest screenshots with as many proxies as possible! 📸💻
Join the Discord community if you have any questions or just want to chat. You can also open a GitHub issue for any bug or feature request 🐞✨.
See you soon!  😎
Fabien


DeviceElement.Parent Id

I've changed DeviceElement.DeviceParentId to ParentId with an explanation as to the conditionality of the type of parent (Device Model/Device Element)

Correction:   DeviceElement.ParentId refers only to parents of the same type (DeviceElement).   An empty parent signifies the root of a hierarchy.   Per 8/17/22 meeting discussion, Device Model Id is now optional, following the pattern of Series, Manufacturer, etc.   A DeviceElement need not refer to a Model.

Superseded by #76


Cleanup function factories:

Switch to std::function to allow more complex creator logic
Cleanup headers

Can one of the admins verify this patch?

Can one of the admins verify this patch?


npm run bundle throws error

When running the bundle script, an error is thrown.  The same thing happens when running npm run bundle:prod.
`PS C:\Projects\Test\Angular2-JumpStart> npm run bundle

<EMAIL_ADDRESS>bundle C:\Projects\Test\Angular2-JumpStart
node bundle.js

Unhandled rejection Error on fetch for app/main.js at file:///C:/Projects/Test/Angular2-JumpStart/app/main.js
Error: ENOENT, open 'C:\Projects\Test\Angular2-JumpStart\app\main.js'
at Error (native)`

+1

+1
As per the error message, the path to main.js file that is been referred is wrong. It is supposed to look into '/src/app/main.js' instead of '/app/main.js'

Hi all.,
I have fixed this defect. The project is getting bundled successfully now. !!
In src/system.config.js file, change the app path in map attribute.
var map = {
    'app':                        'src/app', // 'dist',    <---- change to 'src/app' instead of 'app'
    'rxjs':                       'node_modules/rxjs',     [ no change ]
    '@angular':                   'node_modules/@angular'  [ no change ]
  };

Currently out on a business trip but will look at this when I get time. In the meantime, if you get it going please submit a pull request - I'd appreciate it.

Hi, I change also the path from 'app' to 'src/app' and prd bundle working now and local server also works correctly.

I'm also having this issue. The "src/app" workaround is not working for me. I get an error illegal operation on a directory, which seems to be SystemJS trying to read a directory as a file. The same happens whether I suffix the path with a / or not.
If I change it to "src/app/main.js", and I get an issue with the following paths:
no such file or directory, open '/Users/Meligy/Code/github/DanWahlin/Angular2-JumpStart/src/app/app.component'
Which seems like it doesn't append the ".js" as per the default extension in the config.
I think "app" is right though, matching the package name in the config file. But I'm getting errors on it as if it's the path.

OK, the following code creates a bundle for me:
var SystemBuilder = require('systemjs-builder');
var argv = require('yargs').argv;

var sourceDirName = 'src';
var sourcePath = './' + sourceDirName;

var builder = new SystemBuilder(sourcePath, sourcePath +  "/systemjs.config.js");

var outputFile = argv.prod ? './dist/bundle.min.js' : './dist/bundle.js';

builder.bundle('node_modules/*', {
	fetch: function (load, fetch) {
		load.address =
			load.address.replace(sourceDirName + "/node_modules", "node_modules");

		return fetch(load);
	}
});

builder.buildStatic('app', outputFile, {
	minify: argv.prod,
	mangle: argv.prod,
	rollup: argv.prod
});

But for some reason, the HTML files requested from components' `templateUrl have the same paths unmodified.
For example, the browser tries to load /customers.component.html, instead of /app/customers/customers.component.html(note the /app/customers prefix).

I got it fully working!
In src/systemjs.config/js:
Changed:
    'app':                        { main: 'main.js',  defaultExtension: 'js' },

to:
    'app':                        { main: 'main.js',  defaultExtension: 'js', encodeNames: false },


Allow default widget priority

Allow passing default widget priority to both Tree & Property Grid item providers.

For now, these are the only two (really only the Tree provider is necessary).  This is for UI 1.0.  For 2.0, we will probably have to revisit the remaining providers, some of them, Design Review is currently not using.


Make Burnex an optional dependency

Hi 👋  and thanks for the great library!
This PR makes Burnex an optional dependency.  The reasoning behind this is that for users who don't use burner and check_mx_record checks or even email validator at all, it doesn't make much sense to have burnex in their deps. In fact, it may even cause some headache as it pins dns package to "~> 2.2.0" with latest version being 2.4.0. Burnex was last updated 3 years ago and normally that would be ok, but for a library that depends on regularly updated upstream list of bad emails, it's concerning.

In light of the xz issue, limiting deps would be welcome indeed. Thanks @achedeuzot for maintaining this project btw!


OOM when replicating big tables

Fixes #26

Pull Request Test Coverage Report for Build 352

7 of 8 (87.5%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 76.34%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/com/hotels/bdp/circustrain/bigquery/util/SchemaExtractor.java
7
8
87.5%

Totals

Change from base Build 347:
0.03%

Covered Lines:
655

Relevant Lines:
858

💛  - Coveralls


Add Django books

I update free-programming-books-zh.md, but i can't use others language to update others files, Please forgive me.

No problem. Note that we won't accept share links from baidu (or facebook, for that matter).

eshellman<EMAIL_ADDRESS>周日06:55写道：

Closed #2733
https://github.com/EbookFoundation/free-programming-books/pull/2733.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EbookFoundation/free-programming-books/pull/2733#event-1490611149,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATr3qBAye_qgxeGHBVS5j6_LQwROaHq3ks5tYJNngaJpZM4SR87F
.

thanks, next time i will notice.


The footer.html customization isn't being applied in the Sphinx PyData theme

There's extra information about the license, privacy notice, and terms of use that isn't being applied to the compiled HTML in the PyData theme. It appears others have hit this issue and identified a fix here: https://github.com/pydata/pydata-sphinx-theme/issues/1284

Good news and bad news -- I fixed it, but it looks awful! Much as I love div-wrangling, I could use help from an HTML person here!

Fixed -- not beautiful, but not embarrassing :)


Support qwik

Description
Now it perfectly supports qwik ~ 🚀~

Linked Issues
https://github.com/antfu/unplugin-icons/issues/224
Additional context
demo
import { component$ } from<EMAIL_ADDRESS>import RiFlashlightLine from '~icons/ri/flashlight-line'

export default component$(() => {
  return (<h1> <RiFlashlightLine style="font-size: 2em; color: red"/> Welcome To Qwik With Icons </h1>)
})

I actually don‘t want to use  qwik-city to build demos, but qwik init does not provide other methods without it.
The complexity of the project initialized by qwik is terrible.
thx ur suggestion. I will modify the project structure in the example.
By the way, I wish you happy new year to you😘

@antfu The example has been modified to the smallest feasible qwik version.
~麻烦安师傅来瞅瞅🥰~


Update EVP_VerifyInit.pod

Method name correction.
CLA: trivial

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

Merged. Than you @sambitdash for your contribution!
3c9a8d4a51 Update EVP_VerifyInit.pod [master]
8d5c80539d Update EVP_VerifyInit.pod [1.1.1]