Add document instructions of how to build and run integration tests

Create a document with instructions of how to build and run integration tests. From Discord conversation:
For the Android build with 3.3.4 there is no need to upgrade gradle plugin.

1 - In the folder that you installed the Flutter SDK (the Flutter, not ours) in your computer, run git checkout 3.3.4.

2- Go to TIKI SDK Flutter root and run flutter clean. It will remove the auto generated files.

3- The TIKI SDK Fluter is a Flutter Module. These kind of packages auto generates their build files. We need to update those files, instead of changing the gradle in our project. Run flutter pub get to regenerate the build files.

4- In .android/build.gradle lines 16-30 change the compileSdkVersion and minSdkVersion
android {
    compileSdkVersion 33
    defaultConfig {
        minSdkVersion 21
    }
}

5 - In .android/app/build.gradle lines  5-19 change compileSdkVersion, and minSdkVersion

android {
    compileSdkVersion 33

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }

    defaultConfig {
        applicationId "com.mytiki.tiki_sdk_flutter.host"
        minSdkVersion 21
        targetSdkVersion 31
        versionCode 1
        versionName "1.0"
    }

6 - In .android/Flutter/build.gradle change the compileSdkVersion from flutter.compileSdkVersion to 33.

7 - Run flutter test integration_test and the tests will work correctly

Readme file added to integration_tests directory


dem_coreg.py fails: wrong shape for reference and to be aligned DEM

Running 'python DemUtils/coreg.py' fails with error:

File "DemUtils/coreg.py", line 196, in icp_coregistration
assert reference_dem.shape == dem_to_be_aligned.shape
AssertionError

This is because of several issues. Be aware that rasterio ds shapes will be (nbands, height, width), so even for single band raster, shape will be of length 3. Hence the following issues:

https://github.com/GlacioHack/DemUtils/blob/95cf00be26499b09830e300f273d25ceef4a3b57/DemUtils/coreg.py#L630
shape[1] should be shape[2]
https://github.com/GlacioHack/DemUtils/blob/95cf00be26499b09830e300f273d25ceef4a3b57/DemUtils/coreg.py#L197
a shape of length 3 is compared with a shape of length 2

Also, at https://github.com/GlacioHack/DemUtils/blob/95cf00be26499b09830e300f273d25ceef4a3b57/DemUtils/coreg.py#L629 (and after), I would suggest to:

use rasterio's format for bounding box: https://rasterio.readthedocs.io/en/latest/api/rasterio.coords.html?highlight=bounding box#rasterio.coords.BoundingBox
use georaster reproject method: https://github.com/GlacioHack/GeoUtils/blob/6874974de061613786dff0679f7c2769c7236a08/geoutils/georaster.py#L339

Related shape issue at line https://github.com/GlacioHack/DemUtils/blob/95cf00be26499b09830e300f273d25ceef4a3b57/DemUtils/coreg.py#L207

Here is a quick fix, but I believe the issue should be analyzed more in depth:
diff --git a/DemUtils/coreg.py b/DemUtils/coreg.py
index acb58ea..8a18852 100644
--- a/DemUtils/coreg.py
+++ b/DemUtils/coreg.py
@@ -626,7 +626,7 @@ class Coregistration:

         intersection = reference_raster.intersection(to_be_aligned_raster)
         bounds = dict(zip(["west", "south", "east", "north"], intersection))
-        resolution = (bounds["east"] - bounds["west"]) / reference_raster.data.shape[1]
+        resolution = (bounds["east"] - bounds["west"]) / reference_raster.data.shape[2]

         # TODO: Read the to_be_aligned_dem from the actual to_be_aligned_raster and not its filename
         # TODO: The above leads to highly surprising results sometimes if the raster had been modified from its file.
@@ -639,7 +639,7 @@ class Coregistration:

         # Align the raster using the selected method. This returns a numpy array and the corresponding error
         aligned_dem, error = self.method(  # type: ignore
-            reference_dem=reference_raster.data,
+            reference_dem=reference_raster.data.squeeze(),
             dem_to_be_aligned=to_be_aligned_dem,
             bounds=bounds,
             crs=reference_raster.crs

All suggestions have been taken into account for as of commit 36dbf5bae0f576cdde2e6c3ded82b57d54c69ec9


Add test case for shorthand and overriding styles

Test case to better reproduce #441
Summary :
As per https://developer.mozilla.org/en-US/docs/Web/CSS/padding#Syntax

When three values are specified, the first padding applies to the top, the second to the left and right, the third to the bottom.

Working scenario : ✅
Given ➡  "padding : 10px 20px 40px"
Expected ➡  "paddingTop: 10px, paddingLeft: 20px, paddingRight: 20px, paddingBottom: 40px"
Actual ➡  "paddingTop: 10px, paddingLeft: 20px, paddingRight: 20px, paddingBottom: 40px

Failing scenario : ❌
Given ➡  "padding : 10px 20px 40px; paddingRight: 30px"
Expected ➡  "paddingTop: 10px, paddingLeft: 20px, paddingRight: 30px, paddingBottom: 40px"
Actual ➡  "paddingTop: 10px, paddingLeft: 20px, paddingRight: '', paddingBottom: 40px"

paddingRight is getting cleared

I am more than willing to provide a fix for that but I am not able to figure where to make code changes.
My guess is I need to make changes in this function https://github.com/snabbdom/snabbdom/blob/1f399d6ddef480d33d0da01907a85d2c2a6427e0/src/modules/style.ts#L34 but somehow when I am adding logs in this function it's not reflecting in output.
I am a beginner for node.js so any help will be much appreciated.

Thank you, @umr55766. #815 is not desired. So I'll close this PR.


Exploit/bug with Inventory Pets mod

AquaAcrobatics-1.14.4
inventorypets-1.12-2.0.15
Using the "Squid pet" will get you a swim boost, but when you swim (with AquaAcrobatics) you get an insane speed underwater, its even easy to get out of the loaded chunks zone (with 32 chunks render distance)

As Inventory Pets is closed-source, it's difficult for me to determine what needs to be changed on my end to fix this. Please report the issue on their end as well.


markdown previews in notebooks should use markdown.preview.lineHeight config

How do I control the line height of Markdown cells in Jupyter in VS Code? The editor cell line height is fine. However, when I click the check mark to see the formatted text, the lines are very close to one another and quite hard to read. By contrast, regular VS Code (non-Jupyter) Markdown Preview line height is fine. Also, the same notebooks shown in (non-VS Code) Juypter are fine.
I'm using the latest VS Code and Jupyter extension, latest Linux Mint OS.
There is a markdown.preview.lineHeight setting in VS code, however that does not appear to apply to Jupyter.
Is there some other setting somewhere that will solve the issue?
Originally posted by @paul-rogers in https://github.com/microsoft/vscode-jupyter/discussions/14306

It seems the problem may be that the notebook extension is missing a Markdown output line height that would parallel the setting for Markdown preview.
The following works for Markdown preview (for .md files):
"markdown.preview.lineHeight": 1.6

Changing the value to, say, 3, causes the expected result in Markdown preview. However, the above does not affect the markdown output in notebooks. Perhaps this makes sense as Markdown preview is a separate extension from notebooks?
The following correctly adjusts the font size for Markdown output in notebooks:
"notebook.markup.fontSize": 18

The following correctly adjusts the output line height, where "output" means the output of a Python cell:
"notebook.output.lineHeight": 3

The above has no effect on Markdown output.
Conclusion: the notebook extension is missing a "markdown line height" setting that works like the one for Markdown preview.

To make clear the issue, here is a sample of notebook Markdown output. Note how the lines are a bit too close together:

Here is the same text after exporting the notebook to HTML and opening it in Firefox:

Note that the line spacing is different in the two renders. I fiddled with the various line settings: none change the line spacing in the exported HTML. Instead, it seems formatting is controlled by Jupyter-provided style sheets inlined into the HTML file.
The Markdown line height in the exported HTML file is controlled by this CSS:
.jp-RenderedHTMLCommon {
 ...
  line-height: var(--jp-content-line-height);
  ...
}

Which is set as:
--jp-content-line-height: 1.6;

Debugging question: the above note located the style sheet information by exporting to HTML. However, it is appears that the HTML output is a bit different than the HTML used within VS Code. For example, none of the VS Code settings I fiddled with seemed to change the format of the exported HTML.
Is there a way to see the HTML source or the VS Code notebook view? Searched around and could not see anything. Seeing the source might let us track down how the Markdown line height is supposed to be set.

I believe you're looking for "Developer: Toggle developer tools "

This should be a new setting like notebook.markup.fontSize. markdown.preview.lineHeight config is specially for the markdown preview

I would like to work on this.

I would really like this too. The current output is too dense and looks really ugly.

@lifez Are you still working on this?

@DatN99 I didn't

Would be great if someone could pick this one up. Might be a good starter issue for someone who wants to work out the plumbing behind the scenes. A good first step would be to identify if there is some CSS file that use users could modify as a workaround.

Sounds good! I can pick this one up

Thanks for the fix above! I just noticed another odd discrepancy: if one uses even trivial Latex in a Markdown element within a notebook, one gets very nice spacing. See below, which uses the trivial $k$ Latex element.

verification:

use the "notebook.markdown.lineHeight" to change the displayed line height in the markdown preview within a notebook.
ensure the setting does not affect markdown preview outside of notebooks

@DatN99, thanks for the fix!
Confirmed that, on my system, setting the notebook.markdown.lineHeight value to 20 produces much more readable text in Markdown cells in notebooks.
The value is in pixels. This means it is dependent on the value set for the font, which is a bit fiddly. Elsewhere in VS code we can use the value of "1.6" which means "1.6 times the font height."That is, the software, not a human, works out the math to figure out the line height in pixels.
If I try to use 1.6 as the value for notebook.markdown.lineHeight, I get lines which horribly overlap, so the setting apparently must be in pixels, forcing me to do the math based on the font size selected elsewhere.
I wonder, as a future enhancement, can we apply that trick to Notebook markdown cells to avoid the awkward explicit dependency of lineHeight on the selection of font size?

to add to @paul-rogers points : lineheight in pixels doesn't work with variable font size within the same notebook. For instance section titles :

Thanks, @DatN99, I had noticed the same problem: As you showed, a multi-line title section (Markdown "#") has overlapping text. (Workaround: use only single-line titles.)
I very much appreciate the partial fix: regular text is now much easier to read. Would be great if we can add the bells and whistles before too many other folks start using the feature.

@paul-rogers @gwbx Great catch! Working with multiple lines with titles involved may be a bit complicated, because even though titles may have different font sizes, I'm not sure how I can access their exact value to do appropriate calculations. For example, if notebook.markup.fontSize was set to 20, the title and body paragraph would each size up to 20, but the title would appear much bigger. Therefore, if I were to set notebook.markdown.lineHeight to 2, the overall calculated value would be (20 * 2)px for both the title and the body paragraph.

While the calculated line-height for both the title and body paragraph is both 40px, the title still appears crammed because its font value will be larger as a result of its title tag. If  you have any suggestions, I'd love to discuss them!

@DatN99, I'm afraid I've not taken the time to understand the details of how VS Code or Jupyter handle fonts.
Maybe we can make progress by starting with CSS. Let us hope that the layout is controlled by a CSS style sheet, using the line-height attribute. If so, then the value can be specified in a variety of formats. Perhaps the current fix uses pixels: 10px. It is also possible to use percent: 160%. Or using a "number" (such as 1.6).
We can also see how other bits of VS Code handle line height:

Terminal › Integrated: Line Height
Controls the line height of the terminal. This number is multiplied by the terminal font size to get the actual line-height in pixels.
Editor: Line Height
Controls the line height.
Use 0 to automatically compute the line height from the font size.
Values between 0 and 8 will be used as a multiplier with the font size.
Values greater than or equal to 8 will be used as effective values.
Markdown › Preview: Line Height
Controls the line height used in the Markdown preview. This number is relative to the font size.

For the last one, Markdown preview, I use a value of 1.6 (as suggested in a post somewhere) to get a pleasant spacing. One can imagine that the CSS value is str(int(line_height * 100)) + '%'. Perhaps a search of the code would reveal the actual logic.
Now, given all that, what options might you have for the Notebook Markdown output line height?
Given that the feature already exists and uses the pixel (px) units, perhaps a bit of parsing could allow the CSS syntax. Something like:

160% (for height in percent)
10px (for height in pixels)
16pt (for height in points)
< 8, e.g. 1.6, for the "number" form of CSS `line-height
>= 8 for pixels (for backward compatibility with the current functionality)

At a bare minimum, maybe just do the last two which may be what Editor: Line Height does. If so, you can just grab that code.  The others would be useful if someone wants to control the explicit size.
Also, if the VS Code config line-height property is blank (which should be the default), don't override the notebook line-height CSS property.
Might something like this work here?


Distill posts does not obey site wide max_width

Acknowledge the following

[x] I carefully read and followed the Getting Started guide.
[x] I read through FAQ and searched through the past issues, none of which addressed my issue.
[x] The issue I am raising is a potential bug in al-folio and not just a usage question.  [For usage questions, please post in the Discussions instead of raising an issue.]

Describe the bug
Distill blog posts do not obey the max_width in the _config.yml file.
Screenshots

good observation. however, I don't think this is fixable without having to re-write and/or deeply integrate distill.pub styles into al-folio. currently, distill-style posts directly use native distill.pub styles (+ night mode overrides in _sass/_distill.scss), which are not controlled by _config.yml variables.
if you are using distill-style posts now, the easiest workaround is to make max_width match the max width of distill posts. not sure how many folks are actively using distill-style posts, but if there's a lot of interest, would be awesome to start looking into tighter integration! :)

Yes, this feature would be great ..


Record the SMT input size for each split

Changes
Record the SMT input string size for each split, which can be used to detect regressions in encoding performance
Testing
Updated existing test xml.bpl

Currently sometimes (declare-fun ControlFlow (Int Int) Int) gets put into common and sometimes it is not, which can change the numbers. Should find a way so it's always included


Update the build and release documentation

The build and release documentation is out of date and references the Fastlane release process. We should update it to reflect the newer build and release process.

Done.


Release highlights for the week ending 2021-12-03

Please remember to

[x] Give the PR a meaningful title -- it will be shown in the release notes
[x] Add (or remove) user questions associated with any updated docs

restored the content from the slack announcement, @marians could you please approve so we can merge this :)


reboot redis cluster in aws integration to test resilience of apps

Context
As part of an incident review (more details), the resilience of apps with respect to the reboot of the redis cluster should be tested by rebooting the redis cluster in AWS migration daily.
Decisions

create python script to get redis clusters and restarting them
create a cron job to run the python script in 1 daily at 11 00

Additional PR where db_admin are given iam policy to describe and restart elasticache.

How do you know boto is on the machine? Should there be another include to ensure it's present rather than have it there by coincidence?

Well boto3 is in the base class for govuk_node_list to work. I can add a require.


Add a JS Blazor Hybrid static file example

Per https://github.com/dotnet/AspNetCore.Docs/pull/27854#discussion_r1042669154.

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 1b14a096-b1a3-2270-e57f-8238a25601cd
Version Independent ID: 1b14a096-b1a3-2270-e57f-8238a25601cd
Content: ASP.NET Core Blazor Hybrid static files
Content Source: aspnetcore/blazor/hybrid/static-files.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

@danroth27 ... WRT ...

... we should be showing how to load some JavaScript as a static web asset.

Cross-ref: https://github.com/dotnet/AspNetCore.Docs/pull/27854#discussion_r1042669154
I didn't find anything tricky about it for an example/demonstration. I dropped a JS file into wwwroot and was able to load a module with the expected use of ./ notation ...
module = await JS.InvokeAsync<IJSObjectReference>("import", "./scripts.js");

... along the lines of our existing JavaScript isolation in JavaScript modules coverage.
Cross-ref: https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/call-javascript-from-dotnet?view=aspnetcore-7.0#javascript-isolation-in-javascript-modules
I focused on that for my test because loading JS module/lib seems like it would be a common scenario (i.e., a dev needs to use a 3rd party JS lib in their Hybrid app's Razor components).
1. Is that what you'd like the Hybrid static files article to call out (in the form of a fully-working example)? 👂
Or, what would you like to show for "some JavaScript"?
Side Note: There's no problem using collocated JS either. My app was quite happy 😄 with the following for some Counter component-based JS ...
module = await JS.InvokeAsync<IJSObjectReference>("import", "./Pages/Counter.razor.js");

2. That's not directly related to your original ask, but should I mention it in passing (probably a one-liner) with a cross-link to the appropriate Blazor section? 👂
Cross-ref: https://learn.microsoft.com/en-us/aspnet/core/blazor/javascript-interoperability/?view=aspnetcore-7.0#load-a-script-from-an-external-javascript-file-js-collocated-with-a-component

Is that what you'd like the Hybrid static files article to call out (in the form of a fully-working example)? Or, what would you like to show for "some JavaScript"?

Yup. My comment was in the context of https://github.com/dotnet/AspNetCore.Docs/issues/27819.  If you put your host page in the root, then everything should work fine.

Should I mention it in passing (probably a one-liner) with a cross-link to the Blazor section that describes it?

Yeah, I think that would be helpful. From your example, it looks like we also treat the paths to collocated JS files as logical subpaths of wwwroot, which isn't immediately obvious and is worth calling out.


test: Add support for running multiple post-install Metering tests.

/retest

Link to the test output: https://storage.googleapis.com/origin-ci-test/pr-logs/pull/kube-reporting_metering-operator/1288/pull-ci-kube-reporting-metering-operator-master-metering-e2e-aws/1277971104706596864/artifacts/metering-e2e-aws/metering_test_output/e2e/tests/e2e-tests.log

That test run took ~15m to complete, but that a decent improvement from the ~30-35m average we were seeing before these types of changes.

So in parallel (pun intended) I was doing this bit where I lifted the context up out of the sub-test itself. I think it allows the sub-tests to be run in parallel as well.
https://github.com/kube-reporting/metering-operator/pull/1289

/retest


Update Start Page (Issue #227)

What does this PR do?
Modified the Start page for issue #227, using designs by Chris Carlozzi.
Where should the reviewer start?
https://grommet.github.io/docs/start/
What testing has been done on this PR?
in-browser testing
How should this be manually tested?
Go to the Start page and look at new content. Click on links and buttons.
Any background context you want to provide?
Differences from the original design, since we don't have new setup pages:

2nd button is labeled Get Started (instead of Install with CLI)
no links to install pages below the 2nd button

What are the relevant issues?
Screenshots (if appropriate)

Thanks for your contribution. welcome to team!!!

Issue #227


[Feature] Be able to create albums

I have pictures of the same trip scattered around different folders in my server. It happens when I have media exported from different devices or that have been sent from different persons. I want to keep them that way so they don't mix up.
A nice solution would be having another tab beside "Gallery" named "Albums" that when clicked, displays all the albums saved on the server. I don't think I have to explain how the user would be able to create albums as it is a common feature you can find on a media server software. Some settings could be accessible to decide which account role can create, view or edit albums and if the albums are accessible from all accounts.

Hi,
this is related to: #104, #38 and #45.
In general I don't mind adding logical folders that collect for example certain tags or other properties of photos, but I don't want to add full album support. The aim of this app is to follow the directory structure instead of using albums. There are many other libraries that do the other way around like lychee, piwigo, etc.

Hi @bpatrik, What Pigallery does better than any of the other is the amazing speed :)
I discovered that you can search for any tag, just not faces. This is really great and i haven't seen this in Piwigo. With Pigallery i can tag my photos in Digikam and they becomes searchable right away!

Rereading this, it seems to be a duplicate of #45, so closing this one.


bug with cordova: view not updating after browser back

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[X] 3.x
I'm submitting a ...  (check one with "x")
[X] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
An IonicPage A contains buttons, which - when clicked - update a property in the component. This property itself is used in an *ngIf in the template of the page. Long story short: Clicking a button should change something in the view.
Bug: When the user navigates from this Page A to an IonicPage B via the navController push method, and then uses the browser back button to get back to Page A, the view is not updated properly anymore. The page looks like before, and you can click the buttons, and the properties will be set, but the view does not get rerendered (at least not until the window is resized).
This only happens when I use the cordova browser build, it's fine with the ionic dev server.
Expected behavior:
Like described above, if I go back to Page A, it should have the same behaviour like on the first visit: When a property in the component is updated, and that property somehow affects something on the template via *ngIf,, the view should be rerendered immediately.
Steps to reproduce:
I created a little example project based on the blank template, you can get it here: https://github.com/christophenne/ionic3-ngIf-problem .
To reproduce, run npm install, followed by ionic cordova run browser. As soon as you see the app in your browser window, click the select buttons a few times to verify that the view gets updated.
Then click the link to go to "page 2". And then use the browser back button, to get back to the home page.
Clicking the buttons again, you should see that the view is not updated anymore.
Also have a look into the browser console when you try it. You will see, that the click Method gets called and the property in the component does get updated. It's only that the template is not updated after a new value is set. As soon as you resize the browser window, the view gets updated also.
Related code:
Please have a look at the example I created in https://github.com/christophenne/ionic3-ngIf-problem . An interesting finding, is that it works when I manually call detectChanges() like this:
click(val : number){
    console.log("click(" + val + ")");
    this.selected = val;
    console.log("this.selected = " + this.selected);
    this.cdr.detectChanges();   //this should not be necessary
}

where this.cdr is a ChangeDetectorRef injected like this:
constructor(public navCtrl: NavController,
    private cdr : ChangeDetectorRef) {
}

I had to use this workaround to get the project I am working on into production for now, but it definetly is not a permanent fix for this kind of issue.
Other information:
I have already created the exact same issue here a few days ago, but it seems that it was closed by accident and then never looked into - and now it probably never will be answered again: https://github.com/ionic-team/ionic/issues/12512
I also tried to get help in the ionic forum: https://forum.ionicframework.com/t/problem-with-ionic-cordova-browser-build-ngif-browser-back/100090 .
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
global packages:

    @ionic/cli-utils : 1.4.0
    Cordova CLI      : 6.5.0
    Ionic CLI        : 3.4.0

local packages:

    @ionic/app-scripts : 2.1.3
    Cordova Platforms  : browser 4.1.0
    Ionic Framework    : ionic-angular 3.6.0

System:

    Node       : v6.11.0
    OS         : Linux 3.13
    Xcode      : not installed
    ios-deploy : not installed
    ios-sim    : not installed
    npm        : 3.10.10

Hello, thanks for using Ionic! At this time we do not recommend using the cordova browser platform as it is experimental and very buggy (as you can see from the issue your seeing haha). If you would like to deploy your ionic app to the web you can run npm run ionic:build --prod and then your www folder will be what you want to deploy to your web server/hosting service.


Graceful shutdown does not work on Win7

For graceful shutdown, ANCM sends ctrl-C signal to backend Kestrel process. The later should do cleanup  and terminate after receiving the signal. When debugging other issues, I found this graceful shutdown failed on Win7 but worked on Win10, while ANCM did send the ctrl-C  signal successfully.

Issue has been resolved, an Windows API behaves slightly differently on Win7. Fix will be in ANCM. Thanks @pan-wang for investigating!


Slim down rippled.cfg and move comments/docs into separate file

As suggested by @alloyxrp. Our current rippled.cfg which is installed by packages is mostly comments/docs about the config, which makes it a pain to navigate. What's more, future doc-only changes in the file WILL NOT be installed if the admin has local mods (because configs cannot be overwritten by packages).
For this reason, would be better to move the comments/docs to a separate file (config.README) in the same directory.

That's not how a lot of software packages work... having documentation ore README files in /etc sounds like an antipattern.
Maybe you could move the description to the developer page and ship a manpage instead?

fair enough - a man page sounds interesting, and I'm just dying to write some groff code or whatever it is these days ;)   Feel free to suggest other ideas as they come to you, but I'm definitely inclined toward installed docs of some kind for this use-case, as opposed to relying solely on the developer portal.

That could work too, if a man rippled could give this information.

Just for consideration, I'm not sure where a man rippled would leave Windows developers.

Since Windows isn't a recommended or supported platform as of now, I suspect they would have to look up developer docs extensively, in any case. However, this is a very valid point and requires that the developer docs contain the same information.

@mDuo13 - any thoughts on if/how default rippled.cfg could be slimmed-down? I'd be willing to build/install manpages, but perhaps we just leave the file as-is for windows and only trim it when installing a package (with a manpage)?

Closing due to inactivity.


Two albedo in a simulation

I am just learning bifacial_radiance, and need to do analysis for two different albedo on ground. The simulation is for tracker, the area under tracker and aisle between tracker have different albedo. Is it possible to do analysis with bifacial_radiance?

Yes, Tutorial 14 has a good exxample for this, or also tutorial 11


Unquoted attributes in HTML [help]

What problem are you trying to solve?
I am using nokogiri to check whether a text is a well-formed HTML document. To do so I'm using
Nokogiri::HTML::Document.parse(html)

I want to check all tags are properly closed, and the function above does not do that, so I used
Nokogiri::XML.parse(html){|config|config.strict}

However, this function does not allow some syntax that HTML allows: unquoted attribute values. For instance, I could have this tag:

...

which would be a correct HTML tag but not a correct XML tag.
The question is, how can I check the correctness of the HTML code without being so XML-strict?
Environment
I'm using ruby 1.9.3 so I cannot use the latest version.
# Nokogiri (1.6.7)
    ---
    warnings: []
    nokogiri: 1.6.7
    ruby:
      version: 1.9.3
      platform: x86_64-linux
      description: ruby 1.9.3p551 (2014-11-13 revision 48407) [x86_64-linux]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path<EMAIL_ADDRESS>      libxslt_path<EMAIL_ADDRESS>      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      - 0003-Stop-parsing-on-entities-boundaries-errors.patch
      - 0004-Cleanup-conditional-section-error-handling.patch
      - 0005-CVE-2015-1819-Enforce-the-reader-to-run-in-constant-.patch
      - 0006-Another-variation-of-overflow-in-Conditional-section.patch
      - 0007-Fix-an-error-in-previous-Conditional-section-patch.patch
      - '0008-CVE-2015-8035-Fix-XZ-compression-support-loop.patch'
      - '0009-Updated-config.guess.patch'
      - 0010-Fix-parsering-short-unclosed-comment-uninitialized-access.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - '0008-Fix-direct-pattern-matching.patch'
      - '0009-Fix-certain-patterns-with-predicates.patch'
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      - 0016-Fix-for-type-confusion-in-preprocessing-attributes.patch
      - 0017-Updated-config.guess.patch
      compiled: 2.9.2
      loaded: 2.9.2

PD: I realized I am not the only one who's had this problem
Thanks

Hi @raquelhortab,
I'm not entirely sure that Nokogiri has the functionality you're looking for.
One thing to keep in mind is that HTML does not require every HTML element to have a closing tag. In fact, some elements may not have an end tag. For example
 and
 are treated identically by the standard (except that the latter causes an error).
In other cases, the end tag is not required. Paragraph elements are a good example:

A
B
C
 is legal even though none of the paragraph elements have end tags.
Some elements don't require any start or end tags at all and are inserted by the parser. Here's one example
<!DOCTYPE html>
<title>Title</title>

Heading

This well-formed HTML produces exactly the same DOM as
<!DOCTYPE html>
<title>Title</title>

Heading

The tbody element in tables is another one that requires neither a start nor an end tag.
I know you said you had to use Ruby 1.9.3, but you should be aware that Ruby 1.9.3 reached its end of life in 2015 and has not received any security fixes in seven years. If there's any way you can avoid it, I'd recommend it. The oldest version of Ruby still receiving security updates is Ruby 2.7.
If you can use a newer Ruby, then I recommend using the most recent Nokogiri release and its HTML5 parser with a nonzero maximum number of errors and check if any errors were produced during parse. This will let you know if the document is syntactically well-formed, but it won't detect any errors like violating the content model of an element.

@raquelhortab, thanks for asking this question.
I don't have much to add to @stevecheckoway's comment above. The behavior you're seeing comes from the underlying parser, libxml2. Because Nokogiri is a thin wrapper around the underlying parsers, there isn't anything we can easily do to change this.
Can you share a bit more context on why you want to check that all start tags have matching end tags?

Hi, thanks for answering! I'm a developer at a programming academy. I'm using nokogiri to check student's html code. While we know browsers will "eat" anything, we felt it would be nice for students to at least learn to correctly format the code (while the browser might be OK with an unclosed div, for instance, it is not usually very nice). Anyhow, seeing how it is I might just skip the part where we check the tags if there is no easy way to do so.
I am well aware ruby 1.9.3 is very old, believe me! but it is not up to me... company things
I really appreciate your answers, thank you!

@raquelhortab Ah, I see. That use case totally makes sense to me! But unfortunately, libxml2 is not going to do what you want it to do. Even the SAX parser will implicitly add closing tags and send an event:
#! /usr/bin/env ruby

require "nokogiri"

class MatchingTagTester < Nokogiri::XML::SAX::Document
  attr_reader :unclosed_tags, :errors

  def initialize
    @unclosed_tags = []
    @errors = []
  end

  def start_element(name, *args)
    puts "START: #{name}"
    @unclosed_tags.push(name)
  end

  def end_element(name)
    puts "END: #{name}"
    if @unclosed_tags.last == name
      @unclosed_tags.pop
    else
      @errors.push("expected a matching end tag for '#{name}' but got<EMAIL_ADDRESS>    end
  end

  def ok?
    @errors.empty? && @unclosed_tags.empty?
  end
end

html = STDIN.read
tester = MatchingTagTester.new
parser = Nokogiri::HTML::SAX::Parser.new(tester)
parser.parse(html)

if tester.ok?
  puts "OK"
else
  puts "FAIL"
  puts tester.errors
  puts tester.unclosed_tags
end

$ echo "
" | ./matching-tags.rb
START: html
START: body
START: div
START: span
END: span
END: div
END: body
END: html
OK

(see the end_element event is triggered for implicit span and div close tags).

I understand, thanks anyway!


support to airflow 2.4

Checks

[X] I have checked for existing issues.
[X] This report is about the User-Community Airflow Helm Chart.

Motivation
https://airflow.apache.org/blog/airflow-2.4.0/
New Features and bug fix
Implementation
No response
Are you willing & able to help?

[ ] I am able to submit a PR!
[X] I can help test the feature!

@yossisht9876 chart version 8.6.1 already supports Airflow 2.4 as far as I know (see the support matrix).
Are you having a specific issue?

hi @thesuperzapper
i tried to deploy 2.4.0-python3.8 and 2.4.3-python3.8 with no luck
ImportError: cannot import name 'escape' from 'jinja2' (/home/airflow/.local/lib/python3.8/site-packages/jinja2/__init__.py)

@yossisht9876 are you still having an issue?
If so, please provide any custom values.

@thesuperzapper still have the same issue
im upgrading packages according to the error log but its never end...
what do you mean by "please provide any custom values" ? config values ?
thanks

@thesuperzapper still have the same issue im upgrading packages according to the error log but its never end... what do you mean by "please provide any custom values" ? config values ? thanks

I mean your custom-values.yaml that sets any non-default helm values.

@thesuperzapper still have the same issue im upgrading packages according to the error log but its never end... what do you mean by "please provide any custom values" ? config values ? thanks

@yossisht9876 I mean your custom-values.yaml that sets any non-default helm values.

we dont use custom-value.yaml file
we have for example config values that we added :
 AIRFLOW__EMAIL__EMAIL_BACKEND: "airflow_mailgunxxxxxxxxail_mailgun"      AIRFLOW__EMAIL__EMAIL_CONN_ID: "mailgun_default"     AIRFLOW__SMTP__SMTP_STARTTLS: "True"     AIRFLOW__MAILGUN__DOMAIN_NAME: "haxxx.co"     AIRFLOW__MAILGUN__API_PASSWORD: "key-xxxxxxxxxxx     AIRFLOW__API__AUTH_BACKEND: "airflow.api.auth.backend.basic_auth"
and :
 `connectionsTemplates:
DdsdsdsdKS_TOKEN:
  kind: secret
  name: ddsdsdsen
  key: token
ADsddsdsdsdsORD:
  kind: secret
  name: adddsdsdsdspassword
  key: AdssdsdSSWORD`

  or extra env :

  `extraEnv:
- name: AIRFLOW__CORE__FERNET_KEY
  valueFrom:
    secretKeyRef:
      name: accccct-key
      key: FERNET_KEY
- name: LcccccNV
  value: "dev"
- name: AIRFLOW__SCHEDULER__MAX_DAGRUNS_PER_LOOP_TO_SCHEDULE
  value: "60"
- name: AIRFLOW__CORE__MAX_ACTIVE_RUNS_PER_DAG
  value: "48"
- name: AIRFLOW__METRICS__STATSD_DATADOG_ENABLED
  value: "true"
- name: AIRFLOW__METRICS__STATSD_ON
  value: "True"
- name: AIRFLOW__METRICS__STATSD_PORT
  value: "8125"
- name: AIRFLOW__METRICS__STATSD_PREFIX
  value: airflow
- name: AIRFLOW__METRICS__STATSD_HOST
  valueFrom:
    fieldRef:
      fieldPath: status.hostIP`

@thesuperzapper
i removed some pip packages from my requirements file and everything is working now
thanks


TypeError: ('Keyword argument not understood:', 'input')

tensorflow 2.1.0
keras 2.3.1
2020-05-07 10:45:39.914860: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-05-07 10:45:39.927182: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x147d15a70 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-05-07 10:45:39.927205: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
Traceback (most recent call last):
  File "main.py", line 16, in <module>
    model = unet()
  File "/Users/qihang/.Trash/unet-master/model.py", line 55, in unet
    model = Model(input = inputs, output = conv10)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/training.py", line 146, in __init__
    super(Model, self).__init__(*args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/network.py", line 172, in __init__
    self._init_subclassed_network(**kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/training/tracking/base.py", line 457, in _method_wrapper
    result = method(self, *args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/network.py", line 383, in _init_subclassed_network
    self._base_init(name=name, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/training/tracking/base.py", line 457, in _method_wrapper
    result = method(self, *args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/keras/engine/network.py", line 199, in _base_init
    'autocast'})
  File "/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/tensorflow_core/python/keras/utils/generic_utils.py", line 718, in validate_kwargs
    raise TypeError(error_message, kwarg)
TypeError: ('Keyword argument not understood:', 'input')

Did you find a solution for this problem?

Did you find a solution for this problem?

Try to replace this
 model = Model(input = inputs, output = conv10)
to
 model = Model(inputs, conv10)
in file model.py line 55

cool  thedeoxen. helped me.

can replace like that:
model = Model(inputs, outputs = conv10)

i'm working on windows 10 with tensorflow 2.3.0 and keras 2.4.3 but none of those fixes worked for me I've even tried to make them a list i.e. model=Model(inpus=[net_inputs], outputs=[conv10]) but none of it worked. curiously it worked on colab with the same tf and keras version (some linux dist).

model = Model(inputs=inputs, outputs= conv10) works as well

model = Model(inputs=inputs, outputs= conv10) works as well

can replace like that:
model = Model(inputs = inputs, outputs = conv10)


More screenshots!

Up to 10 on the product page now! 😱
https://developer.apple.com/news/?id=02212018a

Now you can introduce more typos 😂😬

Closing because of #2419 😄


Suspected false-positive Genexus on google apps

Platform
Which platform does the bug apply to?

WebExtension (Mozilla Firefox)

Describe the bug
Genexus is detected Google Drive, Gmail. I don't believe google uses this low-code platform for their core applications, they are not listed on genexus'  Success Stories, and genexus was only recently added on wappalyzer so I'm a bit skeptical that this inference is working correctly.
To Reproduce
Go to gmail.com and log it. Genexus is detected
Expected behavior
Probably should not be detected (correct me if I'm wrong)
Additional context
I haven't looked too deeply on how inferencing works, but the function gx() in the minified code might be triggering this? https://github.com/AliasIO/wappalyzer/pull/2944/commits/00f1e011d526843efde4f00668e13b793f27ea22#diff-557d7d60c04092a680ce152f367618c0R4027

This has been fixed in today's update.

Ditto, I'm using the version 5.9.4 of the extension on Firefox


Update index.markdown: misconception 💩

I prefer to keep a rather serious style.

I'm insisting on adding a symbol indicating misconception (e.g. 0x1F6AB or 0x1F53B). Otherwise, the sole subtitles look like endorsement of the misconceptions at first sight.

@piratebiscuit your opinion ?

I'm against this change, let's keep the page serious. I do not believe that this change would help someone who's trying to make a decision better judge the situation. It can also be seen as childish and doesn't bring much.
Let's present things and arguments as they are and let users decide by themselves if this is 💩 or 🤩.
NACK for me, but I would welcome and support future changes that would help better present the situation.


[BUG]: Contributors list in readme not getting updated

Description
The contributors list in bottom of README file not getting updated dynamically when new contributors come.
Motivation
This should be fixed as contributors are sole backbone of this cool project
Issue Type
Documentation
Are you taking this fetaure implementaion
No, This is up for grabs

Original count of contributors:

but in readme

@jsvigneshkanna
I believe the image pasted in the readme is a static image, which was generated one time. When it was generated, it had just 3 contributors, and then it was pasted. the static image does not update dynamically.
It must have been created using this
https://contrib.rocks/preview?repo=angular%2Fangular-ja

Good findings @akshayrs3
If you can fix this, can i assign this issue under your name?

@jsvigneshkanna I believe it should sync automatically. they must have built the app in that way.
https://dev.to/lacolaco/introducing-contributors-img-keep-contributors-in-readme-md-gci
let's check tomorrow and see if it updates.

Sure @akshayrs3 ,
Will assign this issue to your name, please check tomorrow whether the list is getting updated tomorrow. If not please fix this


Add namespace through Code snippet in Visual Studio Code

I want to give the code snippet extension support for my custom blazor controls to add my codes in the Visual Studio Code editor (.razor files) for my customers. So, I have used the below link to implement this.
https://code.visualstudio.com/api/language-extensions/snippet-guide
Now, my custom code snippets have been added as I expected when to click the ENTER key after typing my prefix value. But, I want to add the namespace also for my controls which are added from the code snippet at the same time of code snippet added. In the above link that gives the options prefix, body and description only. There is no namespace option available. Could you please suggest to me how can I add the Namespace in the razor at the time of add the code snippets?
Also, I want to add the required assemblies at the same time to run my controls to reduce the manual work. Could you please suggest to me this also?
Thanks,
Ganesan R.

Maybe it's duplicate of #95026


Avatar is not loading

This avatar fail to load:
http://img.busy.org/@johurulbot
The original image is https://scontent.fdac3-1.fna.fbcdn.net/v/t1.0-0/p206x206/10262275_506829752761083_8537410738252795849_n.jpg?_nc_eui2=v1%3AAeHhPvYceQG4Dp61qcJ1h5yd6ASDrDjf-GR8dcmojxDLDuN-aE5xKPPNLoCE1h-p-GNm5aSDo4R_qXlhoW7aKx-C-gNWOVHfkIb-u8KImZ2P-w&oh=40f7cea3024bf63ac89045c7464cb5fa&oe=5A6CEF00 and loading fine.

Isn't it related to the max length of URL on cloudinary?

Looks like it might be problem with image URL length:
https://support.cloudinary.com/hc/en-us/articles/207746165-Why-do-I-get-a-public-ID-too-long-error-when-trying-to-fetch-from-a-remote-URL-
as this image URL is 280 characters long (which is above 256 characters limit from Cloudinary).

Yes there is a limitation for URL lenght. That must be the issue.

@bonustrack I have added Google URL Shortener for cases of images longer than 256 characters. I don't think there is much more we can do about it.

Cool working fine now, i'm closing this issue.


rc fix + gp sink

Description:
Fixed logic for runecrafting and added another GP sink.
Changes:
Changed some logic so that runes that don't require stamina potions are not defaulting to true.
Also added a trillion GP sink in the form of runners, which is a common training form for specifically runecrafting (40m gp/h, 2x ingame prices). Resulting in around 40B gp drained per 200M rc xp.
Discussion:
A lot of discussion about runners was brought up, both positive and negative. Which I try to summarize here.
Pros:
It's a massive GP sink. 200M rc would cost 40B gp (2.7B gp for lvl 99) . Only 6 ppl in OSB have the cash on hand for 200M xp.  Making it a substantial sink if used both for 99 and 200M.
It could be a direct sink or go towards other ppl, the down side with other ppl is the convenience factor, where ppl wouldn't bother spending more gp for increased xp if it also result in them having to find other ppl.
It is one of few skills in bot that doesn't have have EHP method implemented yet which goes in line with previous Skilling updates.
It also goes well with other contents where we decided to use none real minions to assist in various activities from raids, shooting star, volcanic mine and guardians of the rift.
Cons:
Concerns regarding relating none real minions with alts, which could open up possibilities of alt methods.
People who already did 200M xp feel like it's unfair if others get faster methods, This is something that happens in osrs all the time.
A few people raised that it's against the spirit of the bot, which might be related to the concerns that they relate none real minions with alts.
Concerns regarding the actual gp sink amount was brought up, both ppl thinking it is too cheap with 40B and others thinking it's too expensive to the point where none would use it or afford it.
Other checks:

[x] I have tested all my changes thoroughly.

my man

If you want to add runners, we will need to discuss it in a #osb-discussion thread first. Put your arguments/justification for it. I personally don't know if it's a good idea, unless you're paying other actual (non-alt-account) players' minions to run for you.

Information added in the discussion section

I'm taking the review label off this until we've reached a consensus agreement in discord. Currently, I don't think there is one other person who supported the idea. So it needs to be changed or you need to more work on convincing.

Closing unless we reach some consensus decision in discord, and since there's no chance this will be merged as is without more information/discussion/etc.


[System Tests] Adding cluster dumps for Vault and LocalStack Kms in case they fail

Type of change

Enhancement / new feature

Description
Because some failures occurred with Vault running on Openshift, we need to add some cluster dumps to be able to see what is happening before removing the pod.
Additional Context
Checklist

[ ] Write tests
[ ] Update documentation
[ ] Make sure all unit/integration tests pass
[ ] Make sure all Sonarcloud warnings are addressed or are justifiably ignored.
[ ] If applicable to the change, trigger the system test suite.  Make sure tests pass.
[ ] If applicable to the change, trigger the performance test suite. Ensure that any degradations to performance numbers are understood and justified.
[ ] Ensure the PR references relevant issue(s) so they are closed on merging.
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

NOTE:  You must be a member of @kroxylicious/developers to trigger the system test and performance test suites.  If you are not part of this group, comment on the PR requesting a trigger, tagging @kroxylicious/developers.

@strimzi-ci run system tests

:heavy_check_mark: Test Summary :heavy_check_mark:
BUILD NUMBER: 119
KAFKA VERSION: 3.8.0
TOTAL: 27
PASS: 21
FAIL: 0
SKIP: 6


publish go version requirements

updated to latest version of go for this to compile properly (was on 1.9.1)
this worked: go version go1.15.2 linux/amd64

Updated the readme, thanks for the feedback!


Documentation: Translater to Translator

I use the version 1.1 and I used the information on the website http://getquill.io/#contexts-cassandra-contexts to implement it. One point is not correct anymore.
ctx.session.addressTranslater=com.datastax.driver.core.policies.IdentityTranslater
needs to changed to
ctx.session.addressTranslator=com.datastax.driver.core.policies.IdentityTranslator

@Citrullin thanks for reporting this issue! These kind of small documentation fixes can be done from the github ui you if you'd like to: open the file and click on "edit" (top right).
I've created #757

@fwbrasil This was my first plan. Fork it, make a pull request and let you check it. But I only used your website documentation. So, I couldn't found the website in the sources. Is the website simply the Readme?

@Citrullin I see :) Yes, the website is just a rendering of the readme


Adding new sub project stubs

Basic mismi subproject's for the amazon services currently in use with separate amazonka exports. This should allow us to transition all of our amazonka dependent code upstream back to mismi, and at a minimum remove all direct amazonka dependencies upstream.

:+1:


PIZ2: Add screens to list, edit and add beverages

Ticket:
PIZ2 - Add a beverage model, manager and service
Activities done:

Added beverage option in the menu
Added options to list, edit and add beverages
Added a screen to edit a beverage
Added a screen to add a beverage
Modify order screen to include beverage options
Modified the total to pay including the beverage price
Added beverage fixture

Changed files:

app/beverage/add-beverage.html
app/beverage/beverages.html
app/beverage/update-beverage.html
app/ingredient/add-ingredient.html
app/ingredient/ingredients.html
app/ingredient/update-ingredient.html
app/order/order-detail.html
app/order/orders.html
app/size/add-size.html
app/size/sizes.html
css/styles.css
index.html
js/beverage/add-beverage.js
js/beverage/beverage.js
js/beverage/update-beverage.js
js/index.js
js/ingredient/add-ingredient.js
js/ingredient/ingredient.js
js/ingredient/update-ingredient.js
js/order/order-detail.js
js/size/add-size.js
js/size/size.js

Link to backend PR:
PIZ2 - Add a beverage model, manager and service
Captures:

Added beverage option in the menu

Added options to list, edit and add beverages

Added a screen to edit a beverage

Added a screen to add a beverage

Modify screen to include beverage options

Modified the total to pay including the beverage price

 PIZ2 - Add a beverage model, manager and service


[release-1.3] Bug fixes in EnvoyFilter

This is an automated cherry-pick of #16395

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-local-presubmit-tests-release-1.3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-lint-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-lint-release-1.3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-lint-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-lint-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-lint-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-lint-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

istio-codecov-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-codecov-release-1.3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

integ-pilot-local-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-local-presubmit-tests-release-1.3

istio-lint-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-lint-release-1.3

integ-new-install-k8s-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-new-install-k8s-presubmit-tests-release-1.3

istio-codecov-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test istio-codecov-release-1.3

integ-pilot-k8s-presubmit-tests-release-1.3
f0bc940e2c5370f28bb786e4c647cc7efac11c65
link
/test integ-pilot-k8s-presubmit-tests-release-1.3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

Yes because other dependent prs have not been cherry picked or are probably still waiting.

I think you / release team need to track all the dependencies (code changes that others did, including refactoring etc.) and cherry pick.

I think you / release team need to track all the dependencies (code changes that others did, including refactoring etc.) and cherry pick.

No, the release maintainers don't do the developers' job.

/retest

/retest


[SPARK-45927][PYTHON] Update path handling in Python data source

What changes were proposed in this pull request?

This PR updates how to handle path values from the load() method.
It changes the DataSource class constructor and add path as a key-value pair in the options field.
Also, this PR blocks loading multiple paths.
Why are the changes needed?

To make the behavior consistent with the existing data source APIs.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing unit tests.
Was this patch authored or co-authored using generative AI tooling?

No

cc @HyukjinKwon @cloud-fan

Merged to master for Apache Spark 4.0.0. Thank you, @allisonwang-db and all.


Feature Request: Adding issue forms for the repo

I want to add a few issue forms so that it will be convenient for new contributors to open issues. There are already issue templates for this project but they are deprecated now, issue forms instead work way better. I plan to create  Bug Report and Feature Request forms.
The Bug Report issue form will have the following fields

Description of the bug
How to Reproduce
Expected behavior
Urgency indicator
Desktop Info (OS, Version, Browser, etc):

The Feature Request issue form will have the following fields

Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered

Hey @MonarchGitHub 👋,
It's a great idea, I was also thinking of making some issue forms as they will be more convenient 😅.
Now since you are here, you can go ahead 🚀
One suggestion:

In the Feature request issue form, instead of Describe alternatives you've considered create Additional context (if any).
Just like it is in the current Feature request issue template.
Similarly, for the Bug report issue form, add an Additional context (if any).

Also just make sure to thoroughly check the forms on some demo repository 👍

Yeah, that sounds great, I'll start right away.


Add Log Entry / Calendar Symptom Shark Components

Overview
This is a start to hopefully enable new MyDataHelps projects to incorporate Symptom Logging (Symptom Shark) more easily.  Much of this has been copied from Symptom Shark and re-worked a bit to generalize it (and of course stories were added)
I organized these in storybook under a "SymptomShark" section that has presentation/container/view subsections.  Stuff that felt functionally specific to Symptom Shark was put there (which is most of this) but some stuff (like NotesInput) was general enough that it was placed outside that library.
For basic reverse chronological logging and editing of logs there is:

"LogToday" to display the current day's log (or prompt the user to log) for a "home" screen
"LogEntryEdit" is the component for editing your symptom log
"LogEntryList" is the reverse chronological list of symptom log entries

For visualization, I brought in all the functionality of the Symptom Shark "Calendar" view, including:

The Symptom / Treatment Filters
The Calendar itself
The Symptom / Treatment Histograms
The "Overall Experience Chart"
The Symptom Severity Chart

I wanted these components to be easily drag/drop reorderable via the upcoming view builder.  However, it doesn't really work from an efficiency/perf perspective for these components to fetch their own data - that would be very redundant since there could be a lot of these components on the page.
So I followed the "DateRangeCoordinator" pattern and created a "SymptomSharkVisualizationCoordinator" for the overall experience chart, symptom severity chart, calendar, and histograms to sit inside.  SymptomSharkVisualizationCoordinator has a flag for "AllowFilters" which will show/hide the filters at the top as well.
SymptomSharkVisualizationCoordinator does the data fetching and renders it's child viz components when the data has been fetched.  The visualization components get the data from the context.
Notable pieces of Symptom Shark not yet included (future PR):

The "Setup Step" for setting up your symptoms / treatments (biggest blocker to self-service setting this up right now I think)
The Report Builder for generating the PDF report of your symptoms / treatments
The Device Activity View (this is not very symptom shark specific overall)
"Questions for Doctor"

All the strings here are localized.
Some other notable tweaks / additions:

I tweaked the default card border radius and dropshadow to match new designs @kyledehovitz-ce has been producing
Cards have a couple new variants for "highlighted" and "subtle" to support some of the log entry stuff
There is a new "NotesInput" component which supports automatic timestamping when you focus the input
Segmented control supports 2 new variants "OptionsVertical" and "OptionsHorizontal", for a slightly more concise/condensed segmented control
There is a new "Title" component for wrapping the H1, H2, H3 etc. (I used "order" of 1-6 to denote which one to render, following pattern from mantine)

TODO:

[ ] Add view for SymptomDetail
[ ] Add view for LogEntryEdit

Security
REMINDER: All file contents are public.

[x] I have ensured no secure credentials or sensitive information remain in code, metadata, comments, etc.

[x] Please verify that you double checked that .storybook/preview.js does not contain your participant access key details.
[x] There are no temporary testing changes committed such as API base URLs, access tokens, print/log statements, etc.

[x] These changes do not introduce any security risks, or any such risks have been properly mitigated.

Describe briefly what security risks you considered, why they don't apply, or how they've been mitigated.
Checklist
Testing

[ ] MyDataHelps iOS app
[ ] MyDataHelps Android app
[ ] MyDataHelps website

Documentation

[x] I have added relevant Storybook updates to this PR as well.
[ ] If this feature requires a developer doc update, tag @CareEvolution/api-docs.

Consider "Squash and merge" as needed to keep the commit history reasonable on main.
Reviewers
Assign to the appropriate reviewer(s). Minimally, a second set of eyes is needed ensure no non-public information is published. Consider also including:

Subject-matter experts
Style/editing reviewers
Others requested by the content owner

Thanks @greinard !


DEV-DOCS 1.1 Directory names  and the doc unit test are in accordance to the new automated side bar

Signed-off-by: krishna katyal<EMAIL_ADDRESS>

Codecov Report

Merging #1127 (d3800f5) into main (50239fc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1127   +/-   ##
=======================================
  Coverage   61.42%   61.42%
=======================================
  Files         224      224
  Lines       10110    10110
  Branches     1695     1695
=======================================
  Hits         6210     6210
  Misses       3476     3476
  Partials      424      424

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 50239fc...d3800f5. Read the comment docs.

/lgtm
/approve


How to use this ?

How to use this ?

Hi @afoysal.
First you need to install it using Package Control.
To use just type one of the snippets, hit tab and it will autocomplete to you, e.g:

Type v-for
Hit tab ⇥
It will expand to:

<div v-for="item in items">
</div>


startApp - howTo?

Hi,
i just installed the Adapter on my ioBroker. Unfortunately, it doesn't work the way I think...
Emulate "home"-click inside a blockly-code works, but i dont know how to start / stop a app. Please, can you explain me how?
Second question. 3 of my firetv´s are in a different network-Segment, so the iobroker is behind a firewall. Which ports do i need to open?
Kind Regards
Matze

it seems that you need to know the exact name off the class to start.. i just got the tagesschau to work with that entry in the StartApp
de.cellular.tagesschau/de.ndr.tagesschau.firetv.activities.HomeActivity
i got that from connecting via adb to the stick
adb connect xx.xx.xx.xx:5555
to get the package name:
adb shell pm list packages -f tages
to get some idea about what the class may be named:
adb shell pm dump /data/app/de.cellular.tagesschau-1/base.apk | grep tages

if you just enter de.cellular.tagesschau
the adapter tries to open "MainActivity" which doesn't seem to exist...
i need a beer now

using this string
com.plexapp.android/com.plexapp.plex.activities.SplashActivity
in the field StartApp started the PLEX client on my FireTV

Hello,
I just figured out how to use startApp for any apps.

download and install "package browser" from fire tv apps
start and filter for your app name. For example "magenta"
Open the packed if found and write down the app name on the first entry. For example tv.accedo.xdk.dtag.production
go to Activities.. and clock on the first entry (public enabled activity ...
write down the name value i(name="...") for example "t.accedo.xdk.dtag.MainActivity"
combine your notes from 3) and 5) with a "/" in between. For example:
tv.accedo.xdk.dtag.production/tv.accedo.xdk.dtag.MainActivity
enter the whole string into appStart


int64 Index in 0.17 typcasts '0' string to integer

Here's what I got. Is this expected behavior? I could not find a reference for this functionality in the release notes.
0.16
conda create -n pd pandas=0.16 python=3.4 ipython
In 0.16 the dtype of the index changes to object when adding a row with '0'.
In [1]: import pandas as pd
In [2]: import numpy as np
In [3]: data = np.random.random(10)
In [4]: m=pd.Series(data)
In [5]: m[0]=0.4444
In [6]: m.index
Out[6]: Int64Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9], dtype='int64')
In [7]: m['0']=0.5555
In [8]: m.index
Out[8]: Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, '0'], dtype='object')

0.17.1
conda create -n pd pandas=0.17 python=3.4 ipython
In 0.17.1 The index dtype does not change, but typecasts to the integer 0. Repeated assignment at the integer 0 index appends more 0s to the index.
In [1]: import pandas as pd
In [2]: import numpy as np
In [3]: data = np.random.random(10)
In [4]: m=pd.Series(data)
In [5]: m[0]=0.4444
In [6]: m.index
Out[6]: Int64Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9], dtype='int64')
In [7]: m['0']=0.5555
In [8]: m.index
Out [8]: Int64Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0], dtype='int64')
In [9]: m['0']=0.6666
In [10]: m.index
Out[10]: Int64Index([0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 0, 0], dtype='int64')
In [11]: m[0]
Out[11]:
0    0.4444
0    0.5555
0    0.6666
dtype: float64

I suppose this should work to be consistent. Might be a bit tricky. This is a failing of Index.insert where the dtype of the inserted element is inferred using the dtype of the current index, which is a tricky thing; you almost alway want to do this because it will raise if its not a compatible element, except when it happens that a string version is DIRECTLY convertible (in this case to a numpy array).

It's worse still though, because m[0]=123 will modify an existing row, but m["0"]=123 will add more rows. So even in the crazy world of PHP-style type casting, the behavior is different depending on the type of the thing that gets cast.


block_journal: if a save journal is present, append to it as well

Otherwise, blocks that were put after the save but before the next MD
flush would never be GC'd.
Issue: KBFS-1692

lgtm


send zerolog to opentelemetry

send zerolog to opentelemetry
wip
properly stop otelwriter

[!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

#145  👈 (View in Graphite)
#144
main

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

Merge activity

Dec 24, 12:00 AM EST: A user started a stack merge that includes this pull request via Graphite.


Added Missing Identifiers to miq_product_features

Added missing identifiers to prevent error in ui when trying to select a button/button group in Automation->Automate->Generic Objects

@Fryguy

This issue has since been fixed in another pr. Closing.


pretrained model for PoseEstimationWithMobileNet

Hi.
Regarding human pose estimation, besides the pretrained model for multiperson pose estimation (PoseEstimationWithMobileNet), would there be a pretrained model for single person pose estimaiton (SinglePersonPoseEstimationWithMobileNet) as well?
Thanks.

@Daniil-Osokin

Hi,
We are going to add support of MS COCO dataset for the single-person pose estimation and release pre-trained model. Stay tuned and don't forget to star this repo =).

Hi, the model and demo are going to be merged, check https://github.com/opencv/open_model_zoo/pull/621.


Add symfony support to makeRelease, exclude theme from release

@thijskh @arothuis questions, remarks?

I'm wondering if there aren't cases where having the theme files available for a local update would be convenient.

I don't have any issue with keeping them. However the theme is dumped and the dumped files are in the source tree as well, editing the source tree within a release to me makes more sense than editing the theme and then dumping it to overwrite the actual files being used. Thoughts?

Because of minification I think editing something like css is then a bit harder..

Keeping themes dir now, any other thoughts/objections/comments?

Fine!


Interrupting Transfers Mid-way

This PR interrupts transfers mid-way by catching KeyboardInterrupt Exception.
When a KeyboardInterrupt is raised, it will exit the current task and deprovision (if gateway is not being reused). For handling parallel tasks, we send an exception to the thread, where the thread will handle the KeyboardInterrupt when it gets scheduled to run.
Since multiple threads can be scheduled and take time to run, it may take few seconds to notify all the threads and all the threads to finish cleaning up their current task, so a few seconds delay in the CLI can occur.

There is a bug where if you halt midway through provisioning, it will not deprovision the gateway that has been provisioned already. This is due to the fact that we wait for all the nodes to finish provisioning before we add it to the list of provisioned nodes, and that is why deprovisioning is not happening.

@HaileyJang @ShishirPatil We should have a whiteboard walkthrough to understand different failure points for a transfer. Ideally, we should understand how to minimize exit locations via better API usage. I don't think multithreading should create too much of an issue with regards to passing the KeyboardInterrupt. W/r to interrupting a transfer during provisioning, I added a pointer to store temporarily allocated nodes but I'm not sure how reliable that functionality is.

@abiswal2001 @JasonDing0401 Can you comment on how we could simplify this VM cleanup issue via the api's skyplane.autoterminate() manager? Would that improve the situation here?

@parasj,  @HaileyJang  and I had a discussion and this is my thought process:
An user might choose to interrupt the transfer due to any of the following reasons:

Forgot to use the right flags
Wants to modify the src/dst bucket
Realized transfer is no longer required
Parts of the transfer are taking too long
etc

A transfer can be interrupted during any of the steps. Here, I list out the state-machine once an interrupt is called.
a) Just after starting the transfer when we are in the VM provisioning phase. An interrupt here should add the list of VM(s) if we have the id's to a list and fall back to deprovisioning those VMs. If we are in posession of no VM ID's to deprovision then, we just exit. For more context refer (d)
b) While applying firewall rules, etc : We stop all ongoing tasks, and call deprovision on all the VM IDs (and associated resources like resource-groups).
c) When the transfers have started : Do NOT wait till the chunks in flight arrive. Start deprovisioning VMs as above.
d) While de-provisioning VMs. This is an interesting case. My argument is that if a user wants to interrupt the deprovisioning task - we need to immediately SIGKILL whatever process skyplane has and return to the user. (Even in the case if we tried to interrupt a deprovisioing that was invoked due to a,b or c above.) The rationale behind this is that perhaps the user believes that the deprovisioning is taking too long, or there might be a bug in the system, and wants to regain control. Now this leaves the undesirable state of a malformed VMs (and malformed resource-groups, and networking interfaces in the worst case), but that is OK, since we want to have skyplane deprovision as the tool to clean it up. This is better than the worst case scenario - where the user is trying to interrupt skyplane, but skyplane is stuck in deprovisoning for 20+ minutes, as we sometimes observe.
Thoughts?

I recommend closing this issue as we migrate from the API to the CLI. Failure points should be minimal with the interruption logic. I would very much like to avoid the problem of leaked VMs and therefore do not like allowing users to support exiting during a deprovision option. I'm augmenting #548 with a note about a proposed confirmation dialog during KeyboardInterrupt when an existing deprovision operation is going on.


Test stories in YAML format can now have user uterances

Fixes #6732
Proposed changes:

Fixed existing bug with YAML test stories
Added one more NLU training example for the initial project

Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

great work with test btw 👍